diff --git a/marked/Rel-11/43_series/43013/raw.md b/marked/Rel-11/43_series/43013/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..17ca4a5cc48355d63a1a7242172cec1f3246633b --- /dev/null +++ b/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 3rd 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 | \ No newline at end of file diff --git a/marked/Rel-11/43_series/43022/a3472689858b068ef469213682965325_img.jpg b/marked/Rel-11/43_series/43022/a3472689858b068ef469213682965325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3638acc166dadb66008ec34aca5bb98fe569f6b --- /dev/null +++ b/marked/Rel-11/43_series/43022/a3472689858b068ef469213682965325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a52c8cb697d7897abcc535d09947a6b9965645f750e153b00a045c0564f03b17 +size 124221 diff --git a/marked/Rel-11/43_series/43022/raw.md b/marked/Rel-11/43_series/43022/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..8b856e8077ef44d4bbb7fac75e96d37822dc74d1 --- /dev/null +++ b/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 3rd 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. + +| | | +|--------------------------------|----------------------------------------------------------------------------------------------------------| +| Selected PLMN | This is the PLMN that has been selected according to subclause 3.1, either manually or automatically. | +| Available PLMN | This is a PLMN where the MS has found a cell that satisfies conditions (ii) and (iv) of subclause 3.2.1. | +| Home PLMN (HPLMN) | See 3GPP TS 23.122. | +| Registered PLMN (RPLMN) | This is the PLMN on which certain LR outcomes have occurred (see 3GPP TS 23.122). | + +| | | +|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Equivalent PLMN | 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). | +| Registration | This is the process of camping on a cell of the PLMN and doing any necessary LRs. | +| Camped on a cell | 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. | +| Current serving cell | This is the cell on which the MS is camped. | +| Suitable Cell | 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. | +| Acceptable Cell | 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. | +| Group call | 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). | +| Broadcast call | 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). | +| Group receive mode | State of the MS when it is engaged in a voice group or voice broadcast call as a listener. | +| GPRS MS | An MS capable of GPRS services is a GPRS MS. | +| CTS MS | An MS capable of CTS services is a CTS MS. | +| Location Registration (LR) | 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). | +| Localised Service Area (LSA) | A localised service area consists of a cell or a number of cells. The cells constituting a LSA may not necessarily provide contiguous coverage. | +| SoLSA exclusive access | Cells on which normal camping is allowed only for MS with Localised Service Area (LSA) subscription. | +| Registration Area | 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
E
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 | +| GERAN# | | | | | | 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 | + +| Change history | | | | | | | | | +|-----------------------|-------------------|-----------------|-----------|------------|--------------------------------------------------------------------------------|------------|------------|--| +| Date | TSG GERAN# | TSG Doc. | CR | Rev | Subject/Comment | Old | New | | +| 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 | | \ No newline at end of file diff --git a/marked/Rel-11/43_series/43030/0fa5b60804100c3aead10404f9f226f9_img.jpg b/marked/Rel-11/43_series/43030/0fa5b60804100c3aead10404f9f226f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..383c65bf8c4a8c09c05566f4a01f1de1f518e864 --- /dev/null +++ b/marked/Rel-11/43_series/43030/0fa5b60804100c3aead10404f9f226f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5ec644023ce17eb72fa5ec1c6a2562d9928a5e7941258e300c0f4fc9fe8ae99 +size 32023 diff --git a/marked/Rel-11/43_series/43030/1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg b/marked/Rel-11/43_series/43030/1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..722edca00f42bc54f1dcb691046a626d6df364c4 --- /dev/null +++ b/marked/Rel-11/43_series/43030/1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c29f77ecee8e231173dce7de2a1ed7e071b074742c90e7bdba35050a7dccf92 +size 162791 diff --git a/marked/Rel-11/43_series/43030/20e597e389dfd8d131e05ad6e1617dcd_img.jpg b/marked/Rel-11/43_series/43030/20e597e389dfd8d131e05ad6e1617dcd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5cefc176b9e7b400c11e961c47e4e3b44e96564d --- /dev/null +++ b/marked/Rel-11/43_series/43030/20e597e389dfd8d131e05ad6e1617dcd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dafea5ec25e25587cba034aedc26f00ced7b65315cb484a268c859e53a670c86 +size 168539 diff --git a/marked/Rel-11/43_series/43030/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-11/43_series/43030/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ee0348b92f19666030119ffaf0ac3b4044473f4 --- /dev/null +++ b/marked/Rel-11/43_series/43030/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:525aff6768194b4cb3a69b649eee4d46a026012e8e1700e52f6c8d16d09f896e +size 39098 diff --git a/marked/Rel-11/43_series/43030/6fc99b56d4021cf515d190c3a0da183f_img.jpg b/marked/Rel-11/43_series/43030/6fc99b56d4021cf515d190c3a0da183f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..657ab944f62f19d3d2c7558ea2d913f276a1eef9 --- /dev/null +++ b/marked/Rel-11/43_series/43030/6fc99b56d4021cf515d190c3a0da183f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:919044281d9cbda0791805db85e2f6d4bb2adf027bab83a00ac69ee3267bacd3 +size 153753 diff --git a/marked/Rel-11/43_series/43030/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-11/43_series/43030/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ac9f4d92f2b85a1e46776686907cf4904b26583 --- /dev/null +++ b/marked/Rel-11/43_series/43030/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69ed66502304cb4e1586c335a141dfb6087a1b6b79c3f9c70089dde93da6c343 +size 40097 diff --git a/marked/Rel-11/43_series/43030/939b79420df0cf962959ccef56f3371f_img.jpg b/marked/Rel-11/43_series/43030/939b79420df0cf962959ccef56f3371f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..acca37ed1bfc62758fc9912aef4ef9833087f42d --- /dev/null +++ b/marked/Rel-11/43_series/43030/939b79420df0cf962959ccef56f3371f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:420016dd920a2433d640b7d51d1372bdb08d6e895494e851ba2bb8eccceadc7e +size 154383 diff --git a/marked/Rel-11/43_series/43030/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-11/43_series/43030/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb16901fc3434a5e2e4816cdc237d6220e202051 --- /dev/null +++ b/marked/Rel-11/43_series/43030/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b6b2b81ef872188952009dc6add4952b41b0c7e375bd1edec2411fbc2662d70c +size 42480 diff --git a/marked/Rel-11/43_series/43030/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-11/43_series/43030/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a0094c3fbcc55c8a751186430c08fa5ecbbc4ae --- /dev/null +++ b/marked/Rel-11/43_series/43030/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a365589adb1aa95f67898eb43e4461bf2d46a290f9cd5274d5d20df8da34cb84 +size 32813 diff --git a/marked/Rel-11/43_series/43030/eb450c92214e8409c1e0f0846e30d876_img.jpg b/marked/Rel-11/43_series/43030/eb450c92214e8409c1e0f0846e30d876_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64143b8e7b740832fa1e1ab2d039fd5dc4e6c4be --- /dev/null +++ b/marked/Rel-11/43_series/43030/eb450c92214e8409c1e0f0846e30d876_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78dd2e12a9bba54c948b9651b27e81484752a2a745a900e8250156965bf9fc5d +size 32168 diff --git a/marked/Rel-11/43_series/43030/f64e1e0997695248c0cd4122c5b1a170_img.jpg b/marked/Rel-11/43_series/43030/f64e1e0997695248c0cd4122c5b1a170_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13595f86d3543ceac6f3c86b1fb128a619b8b54c --- /dev/null +++ b/marked/Rel-11/43_series/43030/f64e1e0997695248c0cd4122c5b1a170_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c36ee6186e252f3ff978a943f104ff0437b359be818dd3380d5aa93d6bef7dd +size 22851 diff --git a/marked/Rel-11/43_series/43030/raw.md b/marked/Rel-11/43_series/43030/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..95d526eaf7aa220f723aa81027e96bb5e0de1663 --- /dev/null +++ b/marked/Rel-11/43_series/43030/raw.md @@ -0,0 +1,1339 @@ + + + + + + +# Contents + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 1.1 References ..... | 6 | +| 1.2 Abbreviations ..... | 6 | +| 2 Traffic distributions..... | 6 | +| 2.1 Uniform ..... | 6 | +| 2.2 Non-uniform..... | 6 | +| 3 Cell coverage..... | 7 | +| 3.1 Location probability ..... | 7 | +| 3.2 Ec/No threshold..... | 7 | +| 3.3 RF-budgets ..... | 7 | +| 3.4 Cell ranges..... | 8 | +| 3.4.1 Large cells ..... | 8 | +| 3.4.2 Small cells ..... | 9 | +| 3.4.3 Microcells ..... | 10 | +| 4 Channel re-use..... | 10 | +| 4.1 C/Ic threshold ..... | 10 | +| 4.2 Trade-off between Ec/No and C/Ic ..... | 10 | +| 4.3 Adjacent channel suppressions..... | 11 | +| 4.4 Antenna patterns..... | 11 | +| 4.5 Antenna heights..... | 11 | +| 4.6 Path loss balance ..... | 11 | +| 4.7 Cell dimensioning ..... | 11 | +| 4.8 Channel allocation..... | 12 | +| 4.9 Frequency hopping..... | 12 | +| 4.10 Cells with extra long propagation delay..... | 12 | +| 5 Propagation models..... | 13 | +| 5.1 Terrain obstacles ..... | 13 | +| 5.2 Environment factors ..... | 13 | +| 5.3 Field strength measurements..... | 13 | +| 5.4 Cell adjustments ..... | 13 | +| 6 Glossary ..... | 13 | +| 7 Bibliography..... | 14 | +| Annex A.1: (GSM 900 class 4) Example of RF-budget for GSM 900 MS handheld RF-output peak power 2 W ..... | 15 | +| Annex A.2: (class 2) Example of RF-budget for GSM MS RF-output peak power 8 W ..... | 17 | +| Annex A.3: (DCS1800 classes 1&2) Example of RF-budget for DCS 1800 MS RF-output peak power 1 W & 250 mW..... | 18 | +| Annex A.4: Example of RF-budget for GSM 900 Class4 (peak power 2 W) in a small cell..... | 19 | +| Annex A.5: Example of RF-budget for GSM 400 Class4 (peak power 2 W) in a (small) cell .... | 20 | +| Annex A.6: Example of RF-budget for GSM 700 Class4 MS handheld (peak power 2 W) ..... | 21 | +| Annex A.7: (DCS1800 class 1) Example of RF link budget for DCS 1800 MS RF-output peak power 1 W Handheld with External Low Noise Amplifier (LNA) connected to BTS ..... | 22 | +| Annex B: Propagation loss formulas for mobile radiocommunications..... | 24 | +| B.1 Hata Model [4], [8] ..... | 24 | +| B.1.1 Urban..... | 24 | + +| | | | +|-----------------|-------------------------------------------------------------------------|-----------| +| B.1.2 | Suburban..... | 24 | +| B.1.3 | Rural (Quasi-open)..... | 24 | +| B.1.4 | Rural (Open Area)..... | 24 | +| B.2 | COST 231-Hata Model [7] ..... | 24 | +| B.3 | COST 231 Walfish-Ikegami Model [7] ..... | 25 | +| B.3.1 | Without free line-of-sight between base and mobile (small cells)..... | 25 | +| B.3.1.1 | Lo free-space loss ..... | 25 | +| B.3.1.2 | Lrts roof-top-to-street diffraction and scatter loss ..... | 25 | +| B.3.1.3 | Lmsd multiscreen diffraction loss ..... | 25 | +| B.3.2 | With a free line-of-sight between base and mobile (Street Canyon) ..... | 26 | +| Annex C: | Path Loss vs Cell Radius..... | 27 | +| Annex D: | Planning Guidelines for Repeaters ..... | 31 | +| D.1 | Introduction..... | 31 | +| D.2 | Definition of Terms..... | 31 | +| D.3 | Gain Requirements..... | 32 | +| D.4 | Spurious/Intermodulation Products..... | 32 | +| D.5 | Output Power/Automatic Level Control (ALC) ..... | 33 | +| D.6 | Local oscillator sideband noise attenuation ..... | 33 | +| D.7 | Delay Requirements..... | 33 | +| D.8 | Wideband Noise ..... | 34 | +| D.9 | Outdoor Rural Repeater Example ..... | 34 | +| D.9.1 | Rural repeater example for GSM 900 ..... | 34 | +| D.9.1.1 | Intermodulation products/ALC setting..... | 34 | +| D.9.1.2 | Wideband noise ..... | 35 | +| D.10 | Indoor Low Power Repeater Example ..... | 35 | +| D.10.1 | Indoor repeater example for DCS 1800 ..... | 35 | +| D.10.1.1 | Intermodulation products/ALC setting..... | 35 | +| D.10.1.2 | Wideband noise ..... | 36 | +| D.11 | Example for a Repeater System using Frequency Shift..... | 36 | +| D.11.1 | Example for GSM 900 ..... | 36 | +| D.11.1.1 | Intermodulation products/ALC setting and levelling criteria..... | 37 | +| D.11.1.2 | Wideband noise ..... | 38 | +| D.11.1.3 | Multipath environment ..... | 38 | +| D.12 | Repeaters and Location Services (LCS) ..... | 38 | +| D.12.1 | Uplink–TOA positioning method ..... | 38 | +| D.12.2 | Enhanced Observed Time Difference positioning method ..... | 39 | +| D.12.3 | Radio Interface Timing measurements ..... | 40 | +| Annex E: | Change history ..... | 42 | + +# --- Foreword + +This Technical Report has been produced by the 3rd 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 is a descriptive recommendation to be helpful in cell planning. + +## 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. +- [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". +- [2] 3GPP TS 45.002: "Digital cellular telecommunications system (Phase 2+); Multiplexing and multiple access on the radio path". +- [3] 3GPP TS 45.005: "Digital cellular telecommunications system (Phase 2+); Radio transmission and reception". +- [4] 3GPP TS 45.008: "Digital cellular telecommunications system (Phase 2+); Radio subsystem link control". +- [5] CCIR Recommendation 370-5: "VHF and UHF propagation curves for the frequency range from 30 MHz to 1000 MHz". +- [6] CCIR Report 567-3: "Methods and statistics for estimating field strength values in the land mobile services using the frequency range 30 MHz to 1 GHz". +- [7] CCIR Report 842: "Spectrum-conserving terrestrial frequency assignments for given frequency-distance separations". +- [8] CCIR Report 740: "General aspects of cellular systems". + +## 1.2 Abbreviations + +Abbreviations used in the present document are given clause 6 (Glossary) and in GSM 01.04 [1]. + +# --- 2 Traffic distributions + +## 2.1 Uniform + +A uniform traffic distribution can be considered to start with in large cells as an average over the cell area, especially in the country side. + +## 2.2 Non-uniform + +A non-uniform traffic distribution is the usual case, especially for urban areas. The traffic peak is usually in the city centre with local peaks in the suburban centres and motorway junctions. + +A bell-shaped area traffic distribution is a good traffic density macro model for cities like London and Stockholm. The exponential decay constant is on average 15 km and 7,5 km respectively. However, the exponent varies in different directions depending on how the city is built up. Increasing handheld traffic will sharpen the peak. + +Line coverage along communication routes as motorways and streets is a good micro model for car mobile traffic. For a maturing system an efficient way to increase capacity and quality is to build cells especially for covering these line concentrations with the old area covering cells working as umbrella cells. + +Point coverage of shopping centres and traffic terminals is a good micro model for personal handheld traffic. For a maturing system an efficient way to increase capacity and quality is to build cells on these points as a complement to the old umbrella cells and the new line covering cells for car mobile traffic. + +# --- 3 Cell coverage + +## 3.1 Location probability + +Location probability is a quality criterion for cell coverage. Due to shadowing and fading a cell edge is defined by adding margins so that the minimum service quality is fulfilled with a certain probability. + +For car mobile traffic a usual measure is 90 % area coverage per cell, taking into account the minimum signal-to-noise ratio $E_c/N_0$ under multipath fading conditions. For lognormal shadowing an area coverage can be translated into a location probability on cell edge (Jakes, 1974). + +For the normal case of urban propagation with a standard deviation of 7 dB and a distance exponential of 3.5, 90 % area coverage corresponds to about 75 % location probability at the cell edge. Furthermore, the lognormal shadow margin in this case will be 5 dB, as described in CEPT Recommendation T/R 25-03 and CCIR Report 740. + +## 3.2 $E_c/N_0$ threshold + +The mobile radio channel is characterized by wideband multipath propagation effects such as delay spread and Doppler shift as defined in 3GPP TS 45.005 annex C. The reference signal-to-noise ratio in the modulating bit rate bandwidth (271 kHz) is $E_c/N_0 = 8$ dB including 2 dB implementation margin for the GSM system at the minimum service quality without interference. The $E_c/N_0$ quality threshold is different for various logical channels and propagation conditions as described in 3GPP TS 45.005. + +## 3.3 RF-budgets + +The RF-link between a Base Transceiver Station (BTS) and a Mobile Station (MS) including handheld is best described by an RF-budget. Annex A consists of 7 such budgets; A.1 for GSM 900 MS class 4; A.2 for GSM 900 MS class 2, A.3 for DCS 1800 MS classes 1 and 2, A.4 for GSM 900 class 4 in small cells, A.5 for GSM 400 class 4 in small cells, A.6 for GSM 700 class 4 and A.7 for DCS 1800 MS class 1. GSM 900 RF-budgets should be used for 850 band. + +The Mean Effective Gain (MEG) of handheld MS in scattered field representing the cell range taking into consideration absorption, detuning and mismatch of the handheld antenna by the human body (MEG = -antenna/body loss) of -13 dBi for GSM 400, -10dBi for GSM 700, -9 dBi for GSM 900 and -6 dBi for DCS 1800 is incorporated in annex A.1, A.3, A.4 and A.5 as shown from measurements in Tdoc SMG2 1075/99. + +At 900 MHz, the indoor loss is the field strength decrease when moving into a house on the bottom floor on 1.5 m height from the street. The indoor loss near windows ( $< 1$ m) is typically 12 dB. However, the building loss has been measured by the Finnish PTT to vary between 37 dB and -8 dB with an average of 18 dB taken over all floors and buildings (Kajamaa, 1985). See also CCIR Report 567. + +At 1800 MHz, the indoor loss for large concrete buildings was reported in COST 231 TD(90)117 and values in the range 12 - 17 dB were measured. Since these buildings are typical of urban areas a value of 15 dB is assumed in annex A.3. In rural areas the buildings tend to be smaller and a 10 dB indoor loss is assumed. + +The isotropic power is defined as the RMS value at the terminal of an antenna with 0 dBi gain. A quarter-wave monopole mounted on a suitable earth-plane (car roof) without losses has antenna gain 2 dBi. An isotropic power of -113 dBm corresponds to a field strength of 23.5 dBuV/m for 925 MHz and 29.3 dBuV/m at 1795 MHz, see CEPT Recommendation T/R 25-03 and 3GPP TS 45.005 section 5 for formulas. GSM900 BTS can be connected to the same feeders and antennas as analog 900 MHz BTS by diplexers with less than 0.5 dB loss. + +## 3.4 Cell ranges + +### 3.4.1 Large cells + +In large cells the base station antenna is installed above the maximum height of the surrounding roof tops; the path loss is determined mainly by diffraction and scattering at roof tops in the vicinity of the mobile i.e. the main rays propagate above the roof tops; the cell radius is minimally 1 km and normally exceeds 3 km. Hata's model and its extension up to 2000 MHz (COST 231-Hata model) can be used to calculate the path loss in such cells (see COST 231 TD (90) 119 Rev 2 and annex B). + +The field strength on 1.5 m reference height outdoor for MS including handheld is a value which inserted in the curves of CCIR Report 567-3 Figure 2 (Okumura) together with the BTS antenna height and effective radiated power (ERP) yields the range and re-use distance for urban areas (section 5.2). + +The cell range can also be calculated by putting the maximum allowed path loss between isotropic antennas into the Figures 1 to 3 of annex C. The same path loss can be found in the RF-budgets in annex A. The figures 1 and 2 (GSM 900) in annex C are based on Hata's propagation model which fits Okumura's experimental curves up to 1500 MHz and figure 3 (DCS 1800) is based on COST 231-Hata model according to COST 231 TD (90) 119 Rev 2. GSM 900 models should be used for 850 band range calculation. + +The example RF-budget shown in annex A.1 for a GSM900 MS handheld output power 2 W yields about double the range outdoors compared with indoors. This means that if the cells are dimensioned for handhelds with indoor loss 10 dB, the outdoor coverage for MS will be interference limited, see section 4.2. Still more extreme coverage can be found over open flat land of 12 km as compared with 3 km in urban areas outdoor to the same cell site. + +For GSM 900 the Max EIRP of 50 W matches MS class 2 of max peak output power 8 W, see annex A.2. + +An example RF budget for DCS 1800 is shown in annex A.3. Range predictions are given for 1 W and 250 mW DCS 1800 MS with BTS powers which balance the up- and down- links. + +The propagation assumptions used in annex A1, A2, A3 are shown in the tables below: + +For GSM 900: + +| | Rural
(Open Area) | Rural
(Quasi-open) | Urban | +|-------------------------------|------------------------------|-------------------------------|---------------------| +| Base station height (m) | 100 | 100 | 50 | +| Mobile height (m) | 1.5 | 1.5 | 1.5 | +| Hata's loss formula (d in km) | $90.7+31.8\log(d)$ | $95.7+31.8\log(d)$ | $123.3+33.7\log(d)$ | +| Indoor Loss (dB) | 10 | 10 | 15 | + +For DCS 1800: + +| | Rural
(Open Area) | Rural
(Quasi-Open) | Urban (*) | +|----------------------------------------|------------------------------|-------------------------------|------------------------| +| Base station height (m) | 60 | 60 | 50 | +| Mobile height (m) | 1.5 | 1.5 | 1.5 | +| COST 231 Hata's loss formula (d in km) | $100.1 + 33.3 \log(d)$ | $105.1 + 33.3 \log(d)$ | $133.2 + 33.8 \log(d)$ | +| Indoor Loss (dB) | 10 | 10 | 15 | + +(\*) medium sized city and suburban centres (see COST 231 TD (90) 119 Rev2). For metropolitan centres add 3 dB to the path loss. + +NOTE 1: The rural (Open Area) model is useful for desert areas and the rural (Quasi-Open) for countryside. + +NOTE 2: The correction factors for Quasi-open and Open areas are applicable in the frequency range 100-2000 MHz (Okumura, 1968). + +### 3.4.2 Small cells + +For small cell coverage the antenna is sited above the median but below the maximum height of the surrounding roof tops and so therefore the path loss is determined by the same mechanisms as stated in section 3.4.1. However large and small cells differ in terms of maximum range and for small cells the maximum range is typically less than 1-3 km. In the case of small cells with a radius of less than 1 km the Hata model cannot be used. + +The COST 231-Walfish-Ikegami model (see annex B) gives the best approximation to the path loss experienced when small cells with a radius of less than 5 km are implemented in urban environments. It can therefore be used to estimate the BTS ERP required in order to provide a particular cell radius (typically in the range 200 m - 3 km). + +The cell radius can be calculated by putting the maximum allowed path loss between the isotropic antennas into figure 4 of annex C. + +The following parameters have been used to derive figure 4: + +Width of the road, $w = 20$ m + Height of building roof tops, $H_{roof} = 15$ m + Height of base station antenna, $H_b = 17$ m + Height of mobile station antenna, $H_m = 1.5$ m + Road orientation to direct radio path, $\Phi = 90^\circ$ + Building separation, $b = 40$ m + +For GSM 900 the corresponding propagation loss is given by: + +$$\text{Loss (dB)} = 132.8 + 38 \log(d/\text{km})$$ + +For DCS 1800 the corresponding propagation loss is given by: + +$$\begin{aligned} \text{Loss (dB)} &= 142,9 + 38 \log(d/\text{km}) \text{ for medium sized cities and suburban centres} \\ \text{Loss (dB)} &= 145,3 + 38 \log(d/\text{km}) \text{ for metropolitan centres} \end{aligned}$$ + +An example of RF budget for a GSM 900 Class 4 MS in a small cell is shown in annex A.4. + +### 3.4.3 Microcells + +COST 231 defines a microcell as being a cell in which the base station antenna is mounted generally below roof top level. Wave propagation is determined by diffraction and scattering around buildings i.e. the main rays propagate in + +street canyons. COST 231 proposes the following experimental model for microcell propagation when a free line of sight exists in a street canyon: + +Path loss in dB (GSM 900) = $101,7 + 26\log(d/\text{km})$ $d > 20 \text{ m}$ + +Path loss in dB (DCS 1800) = $107,7 + 26\log(d/\text{km})$ $d > 20 \text{ m}$ + +The propagation loss in microcells increases sharply as the receiver moves out of line of sight, for example, around a street corner. This can be taken into account by adding 20 dB to the propagation loss per corner, up to two or three corners (the propagation being more of a guided type in this case). Beyond, the complete COST231-Walfish-Ikegami model as presented in annex B should be used. + +Microcells have a radius in the region of 200 to 300 metres and therefore exhibit different usage patterns from large and small cells. They can be supported by generally smaller and cheaper BTS's. Since there will be many different microcell environments, a number of microcell BTS classes are defined in 3GPP TS 45.005. This allows the most appropriate microcell BTS to be chosen based upon the Minimum Coupling Loss expected between MS and the microcell BTS. The MCL dictates the close proximity working in a microcell environment and depends on the relative BTS/MS antenna heights, gains and the positioning of the BTS antenna. + +In order to aid cell planning, the micro-BTS class for a particular installation should be chosen by matching the measured or predicted MCL at the chosen site with the following table. + +The microcell specifications have been based on a frequency spacing of 6 MHz between the microcell channels and the channels used by any other cell in the vicinity. However, for smaller frequency spacings (down to 1.8 MHz) a larger MCL must be maintained in order to guarantee successful close proximity operation. This is due to an increase in wideband noise and a decrease in the MS blocking requirement from mobiles closer to the carrier. + +| Micro-BTS class | Recommended MCL (GSM 900) | | Recommended MCL (DCS 1800) | | +|-----------------|---------------------------|---------------------|----------------------------|---------------------| +| | Normal | Small freq. spacing | Normal | Small freq. spacing | +| M1 | 60 | 64 | 60 | 68 | +| M2 | 55 | 59 | 55 | 63 | +| M3 | 50 | 54 | 50 | 58 | + +Operators should note that when using the smaller frequency spacing and hence larger MCL the blocking and wideband noise performance of the micro-BTS will be better than necessary. + +Operators should exercise caution in choosing the microcell BTS class and transmit power. If they depart from the recommended parameters in 45.005 they risk compromising the performance of the networks operating in the same frequency band and same geographical area. + +# 4 Channel re-use + +## 4.1 C/Ic threshold + +The C/Ic threshold is the minimum co-channel carrier-to-interference ratio in the active part of the timeslot at the minimum service quality when interference limited. The reference threshold $C/Ic = 9 \text{ dB}$ includes 2 dB implementation margin on the simulated residual BER threshold. The threshold quality varies with logical channels and propagation conditions, see 3GPP TS 45.005. + +## 4.2 Trade-off between Ec/No and C/Ic + +For planning large cells the service range can be noise limited as defined by Ec/No plus a degradation margin of 3 dB protected by 3 dB increase of C/Ic, see annex A. + +For planning small cells it can be more feasible to increase Ec/No by 6 dB corresponding to an increase of C/Ic by 1 dB to cover shadowed areas better. $C/(I+N) = 9 \text{ dB}$ represents the GSM limit performance. + +To permit handheld coverage with 10 dB indoor loss, the Ec/No has to be increased by 10 dB outdoors corresponding to a negligible increase of C/Ic outdoors permitting about the same interference limited coverage for MS including handhelds. The range outdoors can also be noise limited like the range indoors as shown in section 3.4 and annex A.1. + +## 4.3 Adjacent channel suppressions + +Adjacent channel suppression (ACS) is the gain ( $I_a/I_c$ ) in $C/I$ when wanted and unwanted GSM RF-signals co-exist on adjacent RF channels whilst maintaining the same quality as in the co-channel case, i.e. $ACS = C/I_c - C/I_a$ . Taking into account frequency errors and fading conditions in the product of spectrum and filter of wanted and unwanted GSM RF-signals, $ACS = 18$ dB is typical as can be found in 3GPP TS 45.005. + +1st $ACS \geq 18$ dB, i.e. $C/I_{a1} \leq -9$ dB for $C/I_c = 9$ dB in 3GPP TS 45.005, imposes constraints of excluding the 1st adjacent channel in the same cell. However, the 1st adjacent channel can be used in the 1st adjacent cell, as $C/I_c \leq 12$ dB and $ACS \geq 18$ dB gives an acceptable handover- margin of $\geq 6$ dB for signalling back to the old BTS as shown in 3GPP TS 45.008. An exception might be adjacent cells using the same site due to uplink interference risks. + +2nd $ACS \geq 50$ dB, i.e. $C/I_{a2} \leq -41$ dB for $C/I_c = 9$ dB in 3GPP TS 45.005, implies that due to MS power control in the uplink, as well as intra-cell handover, it is possible that the 2nd adjacent channel can be used in the same cell. Switching transients are not interfering due to synchronized transmission and reception of bursts at co-located BTS. + +## 4.4 Antenna patterns + +Antenna patterns including surrounding masts, buildings, and terrain measured on ca 1 km distance will always look directional, even if the original antenna was non-directional. In order to achieve a front-to-back ratio F/B of greater than 20 dB from an antenna with an ideal F/B $> 25$ dB, backscattering from the main lobe must be suppressed by using an antenna height of at least 10 m above forward obstacles in ca 0.5 km. In order to achieve an omni-directional pattern with as few nulls as possible, the ideal non-directional antenna must be isolated from the mast by a suitable reflector. The nulls from mast scattering are usually in different angles for the duplex frequencies and should be avoided because of creating path loss imbalance. + +The main lobe antenna gains are typically 12-18 dBi for BTS, and 2-5 dBi for MS. Note that a dipole has the gain 0 dBd = 2 dBi. + +## 4.5 Antenna heights + +The height gain under Rayleigh fading conditions is approximately 6 dB by doubling the BTS antenna height. The same height gain for MS and handheld from reference height 1.5 m to 10 m is about 9 dB, which is the correction needed for using CCIR Recommendation 370. + +## 4.6 Path loss balance + +Path loss balance on uplink and downlink is important for two-way communication near the cell edge. Speech as well as data transmission is dimensioned for equal quality in both directions. Balance is only achieved for a certain power class (section 3.4). + +Path loss imbalance is taken care of in cell selection in idle mode and in the handover decision algorithms as found in 3GPP TS 45.008. However, a cell dimensioned for 8 W MS (GSM 900 class 2) can more or less gain balance for 2 W MS handheld (GSM 900 class 4) by implementing antenna diversity reception on the BTS. + +## 4.7 Cell dimensioning + +Cell dimensioning for uniform traffic distribution is optimized by at any time using the same number of channels and the same coverage area per cell. + +Cell dimensioning for non-uniform traffic distribution is optimized by at any time using the same number of channels but changing the cell coverage area so that the traffic carried per cell is kept constant with the traffic density. Keeping the path loss balance by directional antennas pointing outwards from the traffic peaks the effective radiated power (ERP) per BTS can be increased rapidly out-wards. In order to make the inner cells really small the height gain can be decreased and the antenna gain can be made smaller or even negative in dB by increasing the feeder loss but keeping the antenna front-to-back ratio constant (section 4.4). + +## 4.8 Channel allocation + +Channel allocation is normally made on an FDMA basis. However, in synchronized networks channel allocation can be made on a TDMA basis. Note that a BCCH RF channel must always be fully allocated to one cell. In case of EGPRS Compact, CPBCCH must be allocated to one cell. + +Channel allocation for uniform traffic distribution preferably follows one of the well known re-use clusters depending on C/I-distribution, e.g. a 9-cell cluster (3-cell 3-site repeat pattern) using 9 RF channel groups or cell allocations (CAs), (Stjernvall, 1985). + +Channel allocation for non-uniform traffic distribution preferably follows a vortex from a BTS concentration on the traffic centre, if a bell-shaped area traffic model holds. In real life the traffic distribution is more complicated with also line and point traffic. In this case the cell areas will be rather different for various BTS locations from city centre. The channel allocation can be optimized by using graph colouring heuristics as described in CCIR Report 842. + +Base transceiver station identity code (BSIC) allocation is done so that maximum re-use distance per carrier is achieved in order to exclude co-channel ambiguity. + +Frequency co-ordination between countries is a matter of negotiations between countries as described in CEPT Recommendation T/R 25-04. Co-channel and 200 kHz adjacent channels need to be considered between PLMNs and other services as stated in 3GPP TS 45.005. + +Frequency sharing between GSM countries is regulated in CEPT Recommendation T/R 20-08 concerning frequency planning and frequency co-ordination for the GSM service. + +## 4.9 Frequency hopping + +Frequency hopping (FH) can easily be implemented if the re-use is based on RF channel groups (CAs). It is also possible to change allocation by demand as described in 3GPP TS 45.002. + +In synchronized networks the synchronization bursts (SB) on the BCCH will occur at the same time on different BTS. This will increase the time to decode the BSIC of adjacent BTS, see 3GPP TS 45.008. The SACCH on the TCH or SDCCH will also occur at the same time on different BTS. This will decrease the advantage of discontinuous transmission (DTX). In order to avoid this an offset in the time base (FN) between BTS may be used. + +If channel allocation is made on a TDMA basis and frequency hopping is used, the same hop sequence must be used on all BTS. Therefore the same time base and the same hopping sequence number (HSN) shall be used. + +## 4.10 Cells with extra long propagation delay + +Cells with anticipated traffic with ranges more than 35 km corresponding to maximum MS timing advance of 63 can work properly if the timeslot after the CCCH and the timeslot after the allocated timeslot are not used by the BTS corresponding to a maximum total range of 120 km. + +GSM 400 MSs support extended timing advance with a maximum value of 219 corresponding to a maximum total range of 120 km. + +GSM 400 cells with anticipated traffic with ranges more than 35 km may implement extended timing advance. This works properly if timeslots following the transmission of access bursts are not used for transmission by other MSs. This applies both for circuit switched (random access and handover access) and packet switched (random access, polling response and PTCCH) services. + +# --- 5 Propagation models + +## 5.1 Terrain obstacles + +Terrain obstacles introduce diffraction loss, which can be estimated from the path profile between transmitter and receiver antennas. The profile can preferably be derived from a digital topographic data bank delivered from the national map survey or from a land resource satellite system, e.g. Spot. The resolution is usually 500\*500 m2 down to 50\*50 m2 in side and 20 m down to 5 m in height. This resolution is not sufficient to describe the situation in cities for microcells, where streets and buildings must be recognized. + +## 5.2 Environment factors + +Environment factors for the nearest 200 m radius from the mobile play an important role in both the 900 MHz and 1800 MHz bands. For the Nordic cellular planning for NMT there is taken into account 10 categories for land, urban and wood. Further studies are done within COST 231. + +Coarse estimations of cell coverage can be done on pocket computers with programs adding these environment factors to propagation curves of CCIR Recommendation 370-5 figure 9 and CCIR Report 567-3 figure 2 (Okumura, 1968). + +## 5.3 Field strength measurements + +Field strength measurements of the local mean of the lognormal distribution are preferably done by digital averaging over the typical Rayleigh fading. It can be shown that the local average power can be estimated over 20 to 40 wavelengths with at least 36 uncorrelated samples within 1 dB error for 90 % confidence (Lee, 1985). + +## 5.4 Cell adjustments + +Cell adjustments from field strength measurements of coverage and re-use are recommended after coarse predictions have been done. Field strength measurements of rms values can be performed with an uncertainty of 3.5 dB due to sampling and different propagation between Rayleigh fading and line-of-sight. Predictions can reasonably be done with an uncertainty of about 10 dB. Therefore cell adjustments are preferably done from field strength measurements by changing BTS output power, ERP, and antenna pattern in direction and shape. + +# --- 6 Glossary + +| | | +|-------|-------------------------------------------------------------------------| +| ACS | Adjacent Channel Suppression (section 4.3) | +| BCCH | Broadcast Control Channel (section 4.8) | +| BTS | Base Transceiver Station (section 3.3) | +| BSIC | Base Transceiver Station Identity Code (section 4.8) | +| CA | Cell Allocation of radio frequency channels (section 4.8) | +| CCCH | Common Control Channel (section 4.10) | +| COST | European Co-operation in the field of Scientific and Technical Research | +| DTX | Discontinuous Transmission (section 4.9) | +| Ec/No | Signal-to-Noise ratio in modulating bit rate bandwidth (section 3.2) | +| FH | Frequency Hopping (section 4.9) | +| FN | TDMA Frame Number (section 4.9) | +| F/B | Front-to-Back ratio (section 4.4) | +| HSN | Hopping Sequence Number (section 4.9) | +| MS | Mobile Station (section 3.3) | +| PLMN | Public Land Mobile Network | +| Ps | Location (site) Probability (section 3.1) | +| SACCH | Slow Associated Control Channel (section 4.9) | +| SB | Synchronization Burst (section 4.9) | +| SDCCH | Stand-alone Dedicated Control Channel (section 4.9) | +| TCH | Traffic Channel (section 4.9) | + +# --- 7 Bibliography + +CEPT Recommendation T/R 20-08 Frequency planning and frequency co-ordination for the GSM service; + +CEPT Recommendation T/R 25-03 Co-ordination of frequencies for the land mobile service in the 80, 160 and 460 MHz bands and the methods to be used for assessing interference; + +CEPT Recommendation T/R 25-04 Co-ordination in frontier regions of frequencies for the land mobile service in the bands between 862 and 960 MHz; + +CEPT Liaison office, P.O. Box 1283, CH-3001 Berne. + +- 1 Jakes, W.C., Jr.(Ed.) (1974) Microwave mobile communications. John Wiley, New York, NY, USA. +- 2 Kajamaa, Timo (1985) 900 MHz propagation measurements in Finland in 1983-85 (PTT Report 27.8.1985.) Proc NRS 86, Nordic Radio Symposium, ISBN 91-7056-072-2. +- 3 Lee, W.C.Y. (Feb., 1985) Estimate of local average power of a mobile radio signal. IEEE Trans. Vehic. Tech., Vol. VT-34, 1. +- 4 Okumura, Y. et al (Sep.-Oct., 1968) Field strength and its variability in VHF and UHF land-mobile radio service. Rev. Elec. Comm. Lab., NTT, Vol. 16, 9-10. +- 5 Stjernvall, J-E (Feb. 1985) Calculation of capacity and co-channel interference in a cellular system. Nordic Seminar on Digital Land Mobile Radio Communication (DMR I), Espoo, Finland. +- 6 A.M.D. Turkmani, J.D. Parsons and A.F. de Toledo "Radio Propagation into Buildings at 1.8 GHz". COST 231 TD (90) 117 +- 7 COST 231 "Urban transmission loss models for mobile radio in the 900- and 1800- MHz bands (Revision 2)" COST 231 TD (90) 119 Rev 2. +- 8 Hata, M. (1980) Empirical Formula for Propagation Loss in Land Mobile Radio Services, IEEE Trans. on Vehicular Technology VT-29. + +# Annex A.1: (GSM 900 class 4) Example of RF-budget for GSM 900 MS handheld RF-output peak power 2 W + +| Propagation over land in urban and rural areas | | | | | +|------------------------------------------------|---------|--------|--------|---------------| +| Receiving end: | | BTS | MS | Eq. | +| TX: | | MS | BTS | (dB) | +| Noise figure (multicoupl.input) | dB | 8 | 10 | A | +| Multipath profile 1) | | TU50 | TU50 | (no FH) | +| Ec/No min. fading 1) | dB | 8 | 8 | B | +| RX RF-input sensitivity | dBm | -104 | -102 | $C=A+B+W-174$ | +| Interference degrad. margin | dB | 3 | 3 | D | +| RX-antenna cable type | | 1-5/8" | 0 | | +| Specific cable loss | dB/100m | 2 | 0 | | +| Antenna cable length | m | 120 | 0 | | +| Cable loss + connector | dB | 4 | 0 | E | +| RX-antenna gain | dBi | 12 | 0 | F | +| Isotropic power, 50 % Ps | dBm | -109 | -99 | $G=C+D+E-F$ | +| Lognormal margin 50 % -> 75 % Ps | dB | 5 | 5 | H | +| Isotropic power, 75 % Ps | dBm | -104 | -94 | $I=G+H$ | +| Field strength, 75 % Ps | dBuV/m | 33 | 43 | $J=I+137$ | +| C/Ic min.fading, 50 % Ps 1) | dB | 9 | 9 | | +| C/Ic prot. at 3 dB degrad. | dB | 12 | 12 | | +| C/Ic protection, 75 % Ps 2) | dB | 19 | 19 | | +| Transmitting end: | | MS | BTS | Eq. | +| RX: | | BTS | MS | (dB) | +| TX RF-output peak power | W | 2 | 6 | | +| (mean power over burst) | dBm | 33 | 38 | K | +| Isolator + combiner + filter | dB | 0 | 3 | L | +| RF peak power, combiner output | dBm | 33 | 35 | $M=K-L$ | +| TX-antenna cable type | | 0 | 1-5/8" | | +| Specific cable loss | dB/100m | 0 | 2 | | +| Antenna cable length | m | 0 | 120 | | +| Cable loss + connector | dB | 0 | 4 | N | +| TX-antenna gain | dBi | 0 | 12 | O | + +continued + +| | | | | | | +|------------------------------|----|-----|-----|-----|-----------| +| Peak EIRP | | W | 2 | 20 | | +| (EIRP = ERP + 2 dB) | | dBm | 33 | 43 | $P=M-N+O$ | +| Isotropic path loss, 50 % Ps | 3) | dB | 133 | 133 | $Q=P-G-9$ | +| Isotropic path loss, 75 % Ps | | dB | 128 | 128 | $R=P-I-9$ | +| Range, outdoor, 75 % Ps | 4) | km | 1.3 | 1.3 | | +| Range, indoor, 75 % Ps | 4) | km | 0.5 | 0.5 | | + +- 1) $E_c/N_0$ and $C/I_c$ for residual BER = 0.4 %, TCH/FS (class Ib) and multi-path profiles as defined in 3GPP TS 45.005 annex 3. Bandwidth $W = 54$ dBHz. +- 2) Uncorrelated C and I with 75 % location probability (Ps). lognormal distribution of shadowing with standard deviation 7 dB. Ps = 75 % corresponds to ca 90 % area coverage, see Jakes, pp.126-127. +- 3) 9 dB of path loss is assumed to be due to the handheld MEG (-antenna/body loss) of -9 dBi. +- 4) Max. range based on Hata. Antenna heights for BTS = 50 m and MS = 1.5 m. Indoor loss = 15 dB. + +# Annex A.2: (class 2) Example of RF-budget for GSM MS RF-output peak power 8 W + +| Propagation over land in urban and rural areas | | | | | +|------------------------------------------------|---------|--------|--------|---------------| +| Receiving end: | | BTS | MS | Eq. | +| TX: | | MS | BTS | (dB) | +| Noise figure (multicoupl.input) | dB | 8 | 8 | A | +| Multipath profile 1) | | RA250 | RA250 | (no FH) | +| Ec/No min. fading 1) | dB | 8 | 8 | B | +| RX RF-input sensitivity | dBm | -104 | -104 | $C=A+B+W-174$ | +| Interference degrad. margin | dB | 3 | 3 | D | +| | | | | | +| RX-antenna cable type | | 1-5/8" | RG-58 | | +| Specific cable loss | dB/100m | 2 | 50 | | +| Antenna cable length | m | 120 | 4 | | +| Cable loss + connector | dB | 4 | 2 | E | +| RX-antenna gain | dBi | 12 | 2 | F | +| Isotropic power, 50 % Ps | dBm | -109 | -101 | $G=C+D+E-F$ | +| Lognormal margin 50 % -> 75 % Ps | dB | 5 | 5 | H | +| Isotropic power, 75 % Ps | dBm | -104 | -96 | $I=G+H$ | +| Field strength, 75 % Ps | dBuV/m | 33 | 41 | $J=I+137$ | +| C/Ic min.fading, 50 % Ps 1) | dB | 9 | 9 | | +| C/Ic prot. at 3 dB degrad. | dB | 12 | 12 | | +| C/Ic protection, 75 % Ps 2) | dB | 19 | 19 | | +| | | | | | +| Transmitting end: | | MS | BTS | Eq. | +| RX: | | BTS | MS | (dB) | +| TX RF-output peak power | W | 8 | 16 | | +| (mean power over burst) | dBm | 39 | 42 | K | +| Isolator + combiner + filter | dB | 0 | 3 | L | +| RF peak power, combiner output | dBm | 39 | 39 | $M=K-L$ | +| | | | | | +| TX-antenna cable type | | RG-58 | 1-5/8" | | +| Specific cable loss | dB/100m | 50 | 2 | | +| Antenna cable length | m | 4 | 120 | | +| Cable loss + connector | dB | 2 | 4 | N | +| TX-antenna gain | dBi | 2 | 12 | O | +| Peak EIRP | W | 20 | 50 | | +| (EIRP = ERP + 2 dB) | dBm | 39 | 47 | $P=M-N+O$ | +| Isotropic path loss, 50 % Ps | dB | 148 | 148 | $Q=P-G$ | +| Isotropic path loss, 75 % Ps | dB | 143 | 143 | $R=P-I$ | +| Range, outdoor, 75 % Ps 3) | km | 30.7 | 30.7 | | + +1) Ec/No and C/Ic for residual BER = 0.2 %, TCH/FS (class Ib) and multi-path profiles as defined in 3GPP TS 45.005 annex 3. Bandwidth W = 54 dBHz. + +2) Uncorrelated C and I with 75 % location probability (Ps). Lognormal distribution of shadowing with standard deviation 7 dB. Ps = 75 % corresponds to ca 90 % area coverage, see Jakes, pp.126-127. + +3) Max. range in quasi-open areas based on Hata. Antenna heights for BTS = 100 m and MS = 1.5 m. + +## Annex A.3: (DCS1800 classes 1&2) Example of RF-budget for DCS 1800 MS RF-output peak power 1 W & 250 mW + +| Propagation over land in urban and rural areas | | | | | +|------------------------------------------------|-----|-----------|-----------|---------------------------| +| Receiving end: | | BTS | MS | Eq. | +| TX: | | MS | BTS | (dB) | +| Noise figure(multicoupl.input) | dB | 8 | 12 | A | +| Multipath profile | | TU50 or | RA130 | | +| Ec/No min. fading | dB | 8 | 8 | B | +| RX RF-input sensitivity | dBm | -104 | -100 | $C=A+B+W-174$ | +| Interference degrad. margin | dB | 3 | 3 | D (W=54.3 dBHz) | +| Cable loss + connector | dB | 2 | 0 | E | +| RX-antenna gain | dBi | 18 | 0 | F | +| Diversity gain | dB | 5 | 0 | F1 | +| Isotropic power, 50 % Ps | dBm | -122 | -97 | $G=C+D+E-F-F1$ | +| Lognormal margin 50 % ->75 % Ps | dB | 6 | 6 | H | +| Isotropic power, 75 % Ps | dBm | -116 | -91 | $I=G+H$ | +| Field Strength 75 % Ps | | 27 | 51 | $J=I+142.4$
at 1.8 GHz | +| Transmitting end: | | MS | BTS | Eq. | +| RX: | | BTS | MS | (dB) | +| TX PA output peak power | W | - | 15.8/3.98 | | +| (mean power over burst) | dBm | - | 42/36 | K | +| Isolator + combiner + filter | dB | - | 3 | L | +| RF Peak power,(ant.connector) | dBm | 30/24 | 39/33 | $M=K-L$ | +| 1) | W | 1.0/0.25 | 7.9/2.0 | | +| Cable loss + connector | dB | 0 | 2 | N | +| TX-antenna gain | dBi | 0 | 18 | O | +| Peak EIRP | W | 1.0/0.25 | 316/79.4 | | +| | dBm | 30/24 | 55/49 | $P=M-N+O$ | +| Isotropic path loss, 50 % Ps 2) | dB | 146/140 | 146/140 | $Q=P-G-6$ | +| Isotropic path loss, 75 % Ps | dB | 140/134 | 140/134 | $R=P-I-6$ | +| Range km - 75 % Ps | | | | | +| Urban, out of doors | | 1.6/1.0 | | | +| Urban, indoors | | 0.56/0.37 | | | +| Rural (Open area), out of doors | | 15.0/10.0 | | | +| Rural (Open area), indoors | | 7.7/5.1 | | | + +1) The MS peak power is defined as: + +- If the radio has an antenna connector, it shall be measured into a 50 Ohm resistive load. +- If the radio has an integral antenna, a reference antenna with 0 dBi gain shall be assumed. + +2) 6 dB of the path loss is assumed to be due to the handheld MEG (-antenna/body loss) of -6 dBi. + +## Annex A.4: Example of RF-budget for GSM 900 Class4 (peak power 2 W) in a small cell + +| Propagation over land in urban and rural areas | | | | | +|------------------------------------------------|-----|------|------|----------------------| +| Receiving end: | | BTS | MS | Eq. | +| TX: | | MS | BTS | (dB) | +| Noise figure(multicoupl.input) | dB | 8 | 10 | A | +| Multipath profile | | TU50 | TU50 | | +| Ec/No min. fading | dB | 8 | 8 | B | +| RX RF-input sensitivity | dBm | -104 | -102 | $C=A+B+W-174$ | +| Interference degrad. margin | dB | 3 | 3 | D ( $W=54.3$ dBHz) | +| Cable loss + connector | dB | 2 | 0 | E | +| RX-antenna gain | dBi | 16 | 0 | F | +| Diversity gain | dB | 3 | 0 | F1 | +| Isotropic power, 50 % Ps | dBm | -118 | -99 | $G=C+D+E-F-F1$ | +| Lognormal margin 50 % ->75 % Ps | dB | 5 | 5 | H | +| Isotropic power, 75 % Ps | dBm | -113 | -94 | $I=G+H$ | +| Field Strength 75 % Ps | | 24 | 43 | $J=I+137$ at 900 MHz | +| Transmitting end: | | MS | BTS | Eq. | +| RX: | | BTS | MS | (dB) | +| TX PA output peak power | W | - | 12.6 | | +| (mean power over burst) | dBm | - | 41 | K | +| Isolator + combiner + filter | dB | - | 3 | L | +| RF Peak power,(ant.connector) | dBm | 33 | 38 | $M=K-L$ | +| 1) | W | 2 | 6.3 | | +| Cable loss + connector | dB | 0 | 2 | N | +| TX-antenna gain | dBi | 0 | 16 | O | +| Peak EIRP | W | 2 | 158 | | +| | dBm | 33 | 52 | $P=M-N+O$ | +| Isotropic path loss,50 % Ps 2) | dB | 142 | 142 | $Q=P-G-9$ | +| Isotropic path loss, 75 % Ps | dB | 137 | 137 | $R=P-I-9$ | +| Range km - 75 % Ps | | | | | +| Urban, out of doors | | 1.3 | | | +| Urban, indoors | | 0.52 | | | + +1) The MS peak power is defined as: + +- If the radio has an antenna connector, it shall be measured into a 50 Ohm resistive load. +- If the radio has an integral antenna, a reference antenna with 0 dBi gain shall be assumed. + +2) 9 dB of the path loss is assumed to be due to the handheld MEG (-antenna/body loss) of -9 dBi. + +# Annex A.5: Example of RF-budget for GSM 400 Class4 (peak power 2 W) in a (small) cell + +| | | | | | +|------------------------------------------------|-----|--------|--------|----------------------| +| Propagation over land in urban and rural areas | | | | | +| Receiving end: | | BTS | MS | Eq. | +| TX: | | MS | BTS | (dB) | +| Noise figure(multicoupl.input) | dB | 8 | 8 | A | +| Multipath profile | | TU100 | TU100 | | +| Ec/No min. fading | dB | 8 | 8 | B | +| RX RF-input sensitivity | dBm | -104 | -102 | $C=A+B+W-174$ | +| Interference degrad. margin | dB | 3 | 3 | D (W=54.3 dBHz) | +| Cable loss + connector | dB | 4 | 0 | E | +| RX-antenna gain | dBi | 12 | 0 | F | +| Diversity gain | dB | - | 0 | F1 | +| Isotropic power, 50 % Ps | dBm | -109 | -99 | $G=C+D+E-F-F1$ | +| Lognormal margin 50 % ->75 % Ps | dB | 5 | 5 | H | +| Isotropic power, 75 % Ps | dBm | -104 | -94 | $I=G+H$ | +| Field Strength 75 % Ps | | 27 | 37 | $J=I+131$ at 450 MHz | +| Transmitting end: | | MS | BTS | Eq. | +| RX: | | BTS | MS | (dB) | +| TX PA output peak power | W | 2 | 6.32 | | +| (mean power over burst) | dBm | 33.01 | 38.01 | K | +| Isolator + combiner + filter | dB | 0 | 3 | L | +| RF Peak power,(ant.connector) | dBm | 33.01 | 35.01 | $M=K-L$ | +| 1) | W | 2 | 6.3 | | +| Cable loss + connector | dB | 0 | 4 | N | +| TX-antenna gain | dBi | 0 | 12 | O | +| Peak EIRP | W | 2 | 20 | | +| | dBm | 33.01 | 43.01 | $P=M-N+O$ | +| Isotropic path loss,50 % Ps 2) | dB | 129.01 | 129.01 | $Q=P-G-13$ | +| Isotropic path loss, 75 % Ps | dB | 124.01 | 124.01 | $R=P-I-13$ | +| Range km - 75 % Ps | | | | | +| Urban, out of doors | | 1.9 | | | +| Urban, indoors | | | | | + +1) The MS peak power is defined as: + +- If the radio has an antenna connector, it shall be measured into a 50 Ohm resistive load. +- If the radio has an integral antenna, a reference antenna with 0 dBi gain shall be assumed. + +2) 13 dB of the path loss is assumed to be due to the handheld MEG (-antenna/body loss) of -13 dBi. + +## Annex A.6: Example of RF-budget for GSM 700 Class4 MS handheld (peak power 2 W) + +| Propagation over land in urban and rural areas | | | | | +|------------------------------------------------|-----|------|-------|-----------------------| +| Receiving end: | | BTS | MS | Eq. | +| TX: | | MS | BTS | (dB) | +| Noise figure(multicoupl.input) | dB | 8 | 10 | A | +| Multipath profile | | TU60 | TU60 | | +| Ec/No min. fading | dB | 8 | 8 | B | +| RX RF-input sensitivity | dBm | -104 | -102 | C=A+B+W-174 | +| Interference degrad. margin | dB | 3 | 3 | D (W=54.3
DBHz) | +| Cable loss + connector | dB | 2 | 0 | E | +| RX-antenna gain | dBi | 16 | 0 | F | +| Diversity gain | dB | 3 | 0 | F1 | +| Isotropic power, 50 % Ps | dBm | -118 | -99 | G=C+D+E-F-F1 | +| Lognormal margin 50 % ->75 % Ps | dB | 5 | 5 | H | +| Isotropic power, 75 % Ps | dBm | -113 | -94 | I=G+H | +| Field Strength 75 % Ps | | 22 | 41 | J=I+135 at
770 MHz | +| Transmitting end: | | MS | BTS | Eq. | +| RX: | | BTS | MS | (dB) | +| TX PA output peak power | W | 2 | 12.6 | | +| (mean power over burst) | dBm | 33 | 41 | K | +| Isolator + combiner + filter | dB | 0 | 3 | L | +| RF Peak power,(ant.connector) | dBm | 33 | 38 | M=K-L | +| 1) | W | 2 | 6.3 | | +| Cable loss + connector | dB | 0 | 2 | N | +| TX-antenna gain | dBi | 0 | 16 | O | +| Peak EIRP | W | 2 | 158.5 | | +| | dBm | 33 | 52 | P=M-N+O | +| Isotropic path loss,50 % Ps 2) | dB | 141 | 141 | Q=P-G-10 | +| Isotropic path loss, 75 % Ps | dB | 136 | 136 | R=P-I-10 | +| Range km - 75 % Ps | | | | | +| Urban, out of doors | | 1.37 | | | +| Urban, indoors | | 0.55 | | | + +1) The MS peak power is defined as: + +- a) If the radio has an antenna connector, it shall be measured into a 50 Ohm resistive load. +- b) If the radio has an integral antenna, a reference antenna with 0 dBi gain shall be assumed. + +2) 10 dB of the path loss is assumed to be due to the handheld MEG (-antenna/body loss) of -10dBi. + +# Annex A.7: + +## (DCS1800 class 1) Example of RF link budget for DCS 1800 MS RF-output peak power 1 W Handheld with External Low Noise Amplifier (LNA) connected to BTS + +| Propagation over land in urban and rural areas | | | | +|------------------------------------------------|---------|-------|-------------------------------| +| Receiving end: | BTS | MS | Eq. | +| TX: | MS | BTS | (dB) | +| Noise figure (multicoupler input) | dB | 5 | 7 A | +| Low Noise Amplifier - noise figure | dB | 2 - | X | +| Low Noise Amplifier - gain | dB | 12 - | Y | +| Multipath profile | TU50 or | RA130 | | +| Noise bandwidth | kHz | 200 | 200 [TR 45.050 Annex X] | +| C/N = C/I min. at fading | dB | 9 | 9 B | +| Noise figure at antenna | dB | 4 | 7 Z = Friis(A, X, Y, E) | +| RX RF-input sensitivity at antenna | dBm | -108 | -105 C=Z+B+10log(200 kHz)-174 | +| Interference degradation margin | dB | 3 | 3 D | +| Cable loss + connector | dB | 3 | 0 E | +| RX-antenna gain | dBi | 18 | 0 F | +| Diversity gain | dB | 3 | 0 F1 | +| Isotropic power, 50 % Ps | dBm | -126 | -102 G=C+D-F-F1 | +| Lognormal margin, 50 % ->75 % Ps | dB | 6 | 6 H | +| Isotropic power, 75 % Ps | dBm | -120 | -96 I=G+H | +| Field Strength, 75 % Ps | dBuV/m | 22 | 46 J=I+142 at 1.8 GHz | +| Transmitting end: | MS | BTS | Eq. | +| RX: | BTS | MS | (dB) | +| TX PA output peak power | W | - | 30 | +| (mean power over burst) | dBm | - | 45 K | +| Isolator + combiner + filter | dB | - | 5 L | +| RF Peak power, TOC (top of cabinet) | dBm | 31 | 40 M=K-L | +| 1) | W | 1.2 | 10 | +| Cable loss + connector | dB | 0 | 3 N | +| TX-antenna gain | dBi | 0 | 18 O | +| Peak EIRP | W | 1.2 | 300 | +| | dBm | 31 | 55 P=M-N+O | +| Isotropic path loss, 50 % Ps 2) | dB | 151 | 151 Q=P-G-6 | +| Isotropic path loss, 75 % Ps | dB | 145 | 145 R=P-I-6 | + +$$\text{Friis}(A,X,Y,E) = 10 * \text{LOG10}(10^{(X/10)} + (10^{(E/10)} - 1) / 10^{(Y/10)} + (10^{(A/10)} - 1) / 10^{((Y-E)/10)})$$ + +- 1) The MS peak power is defined as: + - a) If the radio has an antenna connector, it shall be measured into a 50 Ohm resistive load. + - b) If the radio has an integral antenna, a reference antenna with 0 dBi gain shall be assumed. +- 2) 6 dB of the path loss is assumed to be due to the handheld MEG (-antenna/body loss) of -6 dBi. + +# --- Annex B: Propagation loss formulas for mobile radiocommunications + +## B.1 Hata Model [4], [8] + +Frequency f: 150 - 1000 MHz + +Base station height Hb: 30 - 200 m + +Mobile height Hm: 1 - 10 m + +Distance d: 1 - 20 km + +Large and small cells (i.e. base station antenna heights above roof-top levels of buildings adjacent to the base station) + +### B.1.1 Urban + +$$L_u \text{ (dB)} = 69.55 + 26.16 \cdot \log(f) - 13.82 \cdot \log(H_b) - a(H_m) + [44.9 - 6.55 \cdot \log(H_b)] \cdot \log(d)$$ + +$a(H_m)$ correction factor for vehicular station antenna height. + +For a medium-small city: + +$$a(H_m) = [1.1 \cdot \log(f) - 0.7] \cdot H_m - [1.56 \cdot \log(f) - 0.8]$$ + +For a large city: + +$$a(H_m) = 8.29 \cdot [\log(1.54 \cdot H_m)]^2 - 1.1 \quad \text{for } f \leq 200 \text{ MHz}$$ + +$$a(H_m) = 3.2 \cdot [\log(11.75 \cdot H_m)]^2 - 4.97 \quad \text{for } f \geq 400 \text{ MHz}$$ + +### B.1.2 Suburban + +$$L_{su} \text{ (dB)} = L_u - 2 \cdot [\log(f/28)]^2 - 5.4$$ + +### B.1.3 Rural (Quasi-open) + +$$L_{rq} \text{ (dB)} = L_u - 4.78 \cdot [\log(f)]^2 + 18.33 \cdot \log(f) - 35.94$$ + +### B.1.4 Rural (Open Area) + +$$L_{ro} \text{ (dB)} = L_u - 4.78 \cdot [\log(f)]^2 + 18.33 \cdot \log(f) - 40.94$$ + +## --- B.2 COST 231-Hata Model [7] + +Frequency f: 1500 - 2000 MHz + +Base station height Hb: 30 - 200 m + +Mobile height Hm: 1 - 10 m + +Distance d: 1 - 20 km + +Large and small cells (i.e. base station antenna heights above roof-top levels of buildings adjacent to the base station). + +Urban areas (for rural areas the correction factors given in subparagraph 1.3 and 1.4 can be used up to 2000 MHz). + +$$L_u \text{ (dB)} = 46.3 + 33.9 \cdot \log(f) - 13.82 \cdot \log(H_b) - a(H_m) + [44.9 - 6.55 \cdot \log(H_b)] \cdot \log(d) + C_m$$ + +with: + +$$a(H_m) = [1.1 \cdot \log(f) - 0.7] \cdot H_m - [1.56 \cdot \log(f) - 0.8]$$ + +$C_m = 0$ dB for medium sized city and suburban centres with moderate tree density + +$C_m = 3$ dB for metropolitan centres + +## B.3 COST 231 Walfish-Ikegami Model [7] + +Frequency $f$ : 800 - 2000 MHz + +Base station height $H_b$ : 4 - 50 m + +Mobile height $H_m$ : 1 - 3 m + +Distance $d$ : 0.02 - 5 km + +Height of buildings $H_{\text{roof}}$ (m) + +Width of road $w$ (m) + +Building separation $b$ (m) + +Road orientation with respect to the direct radio path $\Phi$ ( $^\circ$ ) + +Urban areas + +### B.3.1 Without free line-of-sight between base and mobile (small cells) + +$$L_b = L_o + L_{\text{rts}} + L_{\text{msd}} \text{ (or } L_b = L_o \text{ for } L_{\text{rts}} + L_{\text{msd}} \leq 0)$$ + +with: + +#### B.3.1.1 $L_o$ free-space loss + +$$L_o = 32.4 + 20 \cdot \log(d) + 20 \cdot \log(f)$$ + +#### B.3.1.2 $L_{\text{rts}}$ roof-top-to-street diffraction and scatter loss + +$$L_{\text{rts}} = -16.9 - 10 \cdot \log(w) + 10 \cdot \log(f) + 20 \cdot \log(H_r - H_m) + L_{\text{cri}}$$ + +with $L_{\text{cri}} = -10 + 0.354 \cdot \Phi$ for $0 \leq \Phi < 35^\circ$ + +$L_{\text{cri}} = 2.5 + 0.075 \cdot (\Phi - 35)$ for $35 \leq \Phi < 55^\circ$ + +$L_{\text{cri}} = 4.0 - 0.114 \cdot (\Phi - 55)$ for $55 \leq \Phi < 90^\circ$ + +#### B.3.1.3 $L_{\text{msd}}$ multiscreen diffraction loss + +$$L_{\text{msd}} = L_{\text{bsh}} + k_a + k_d \cdot \log(d) + k_f \cdot \log(f) - 9 \cdot \log(b)$$ + +with $L_{\text{bsh}} = -18 \cdot \log(1 + H_b - H_{\text{roof}})$ for $H_b > H_{\text{roof}}$ + $= 0$ for $H_b \leq H_{\text{roof}}$ + +$k_a = 54$ for $H_b > H_{\text{roof}}$ + $= 54 - 0.8 \cdot (H_b - H_{\text{roof}})$ for $d \geq 0.5$ and $H_b \leq H_{\text{roof}}$ + +$$= 54 - 0.8 \cdot (H_b - H_{roof}) \cdot (d/0.5) \text{ for } d < 0.5 \text{ and } H_b \leq H_{roof}$$ + +$$\begin{aligned} k_d &= 18 && \text{for } H_b > H_{roof} \\ &= 18 - 15 \cdot (H_b - H_{roof})/H_{roof} && \text{for } H_b \leq H_{roof} \end{aligned}$$ + +$$\begin{aligned} k_f &= -4 + 0.7 \cdot (f/925 - 1) && \text{for medium sized cities and} \\ & && \text{suburban centres with moderate} \\ & && \text{tree density} \\ &= -4 + 1.5 \cdot (f/925 - 1) && \text{for metropolitan centres} \end{aligned}$$ + +### B.3.2 With a free line-of-sight between base and mobile (Street Canyon) + +Microcells (Base station antennas below roof top level) + +$$L_b = 42.6 + 26 \cdot \log(d) + 20 \cdot \log(f) \text{ for } d \geq 0.020 \text{ km}$$ + +# Annex C: Path Loss vs Cell Radius + +![A line graph showing path loss (dB) on the y-axis (90 to 220) versus cell radius (km) on a logarithmic x-axis (1 to 100). Five lines represent different environments: Urban Indoor, Urban, Suburban, Rural (open), and Rural (quasi open). All lines show a positive correlation between cell radius and path loss.](939b79420df0cf962959ccef56f3371f_img.jpg) + +The graph illustrates the relationship between path loss in dB and cell radius in km for various environments. The y-axis represents path loss (dB) from 90 to 220 in increments of 10. The x-axis represents cell radius (km) on a logarithmic scale from 1 to 100. Five lines are plotted, each representing a different environment: Urban Indoor, Urban, Suburban, Rural (open), and Rural (quasi open). All lines show a positive correlation between cell radius and path loss. The Rural (open) environment has the lowest path loss, while the Urban Indoor environment has the highest path loss for a given cell radius. + +| Cell radius (km) | Urban Indoor (dB) | Urban (dB) | Suburban (dB) | Rural (quasi open) (dB) | Rural (open) (dB) | +|------------------|-------------------|------------|---------------|-------------------------|-------------------| +| 1 | 139 | 124 | 114 | 100 | 95 | +| 10 | 172 | 157 | 147 | 133 | 128 | +| 100 | 205 | 190 | 180 | 166 | 161 | + +A line graph showing path loss (dB) on the y-axis (90 to 220) versus cell radius (km) on a logarithmic x-axis (1 to 100). Five lines represent different environments: Urban Indoor, Urban, Suburban, Rural (open), and Rural (quasi open). All lines show a positive correlation between cell radius and path loss. + +Figure1: Path loss vs Cell Radius, BS height = 50 m, MS height = 1.5 m (GSM 900) + +Fig 2. Path loss vs cell radius, BS height =100m, MS height =1,5m (GSM900) + +![A line graph showing Path loss (dB) on the y-axis (90 to 220) versus Cell radius (km) on a logarithmic x-axis (1 to 100). Five lines represent different environments: Urban indoor, Urban, Suburban, Rural (quasi open), and Rural (open). Path loss increases with cell radius and is higher for more densely populated areas.](6fc99b56d4021cf515d190c3a0da183f_img.jpg) + +| Cell radius (km) | Urban indoor (dB) | Urban (dB) | Suburban (dB) | Rural (quasi open) (dB) | Rural (open) (dB) | +|------------------|-------------------|------------|---------------|-------------------------|-------------------| +| 1 | 134 | 120 | 110 | 96 | 90 | +| 10 | 166 | 152 | 142 | 128 | 122 | +| 100 | 198 | 184 | 174 | 160 | 154 | + +A line graph showing Path loss (dB) on the y-axis (90 to 220) versus Cell radius (km) on a logarithmic x-axis (1 to 100). Five lines represent different environments: Urban indoor, Urban, Suburban, Rural (quasi open), and Rural (open). Path loss increases with cell radius and is higher for more densely populated areas. + +Figure 2: Path loss vs Cell Radius, BS height = 100 m, MS height = 1.5 m (GSM 900) + +![Line graph showing Path Loss (dB) vs Cell Radius (km) for various environments: Urban indoor, Urban, Rural indoor (quasi open), Rural (quasi open), and Rural (open). The x-axis is logarithmic from 1 to 100 km, and the y-axis is linear from 90 to 220 dB.](1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg) + +The graph illustrates the relationship between Path Loss (dB) and Cell Radius (km) for five different propagation environments. The x-axis is logarithmic, ranging from 1 km to 100 km, with major ticks at 1, 10, and 100. The y-axis is linear, ranging from 90 dB to 220 dB, with major ticks every 10 dB. The five curves represent different scenarios: Urban indoor, Urban, Rural indoor (quasi open), Rural (quasi open), and Rural (open). All curves show a positive correlation between cell radius and path loss. The 'Urban indoor' scenario results in the highest path loss, while the 'Rural (open)' scenario results in the lowest path loss for any given cell radius. + +| Cell Radius (km) | Urban indoor (dB) | Urban (dB) | Rural indoor (quasi open) (dB) | Rural (quasi open) (dB) | Rural (open) (dB) | +|------------------|-------------------|------------|--------------------------------|-------------------------|-------------------| +| 1 | 148 | 133 | 115 | 105 | 100 | +| 10 | 180 | 165 | 147 | 137 | 132 | +| 100 | 212 | 200 | 179 | 169 | 164 | + +Line graph showing Path Loss (dB) vs Cell Radius (km) for various environments: Urban indoor, Urban, Rural indoor (quasi open), Rural (quasi open), and Rural (open). The x-axis is logarithmic from 1 to 100 km, and the y-axis is linear from 90 to 220 dB. + +Figure 3: Path loss vs Cell Radius, Urban BS height = 50 m, Rural BS height = 60 m, MS height = 1.5 m (DCS 1800) + +![A line graph showing Path loss (dB) on the y-axis (100.0 to 170.0) versus Cell Radius (km) on the x-axis (0.1 to 3.0). Three lines represent different scenarios: DCS 1800 (metropolitan centres), DCS 1800 (medium sized cities and suburban centres), and GSM 900. The DCS 1800 (metropolitan centres) line has a negative slope, while the others have positive slopes.](20e597e389dfd8d131e05ad6e1617dcd_img.jpg) + +The graph illustrates the relationship between Path loss (dB) and Cell Radius (km) for small cells. The y-axis represents Path loss in dB, ranging from 100.0 to 170.0 in increments of 10.0. The x-axis represents Cell Radius in km, on a logarithmic scale with major ticks at 0.1, 0.5, 1.0, and 3.0. Three lines are plotted: +1. **DCS 1800 (metropolitan centres)**: A line with a negative slope, starting at approximately (0.2, 155) and ending at (0.8, 115). +2. **DCS 1800 (medium sized cities and suburban centres)**: A line with a positive slope, starting at approximately (0.2, 118) and ending at (3.0, 163). +3. **GSM 900**: A line with a positive slope, starting at approximately (0.2, 116) and ending at (3.0, 161). +4. An unlabeled line with a positive slope, starting at approximately (0.2, 106) and ending at (3.0, 151). +Arrows point from the text labels to their respective lines. + +| Cell Radius (km) | DCS 1800 (metropolitan centres) (dB) | DCS 1800 (medium sized cities and suburban centres) (dB) | GSM 900 (dB) | Unlabeled (dB) | +|------------------|--------------------------------------|----------------------------------------------------------|--------------|----------------| +| 0.1 | - | - | - | - | +| 0.2 | 155 | 118 | 116 | 106 | +| 0.5 | 135 | 135 | 133 | 123 | +| 1.0 | 125 | 145 | 143 | 133 | +| 3.0 | 115 | 163 | 161 | 151 | + +A line graph showing Path loss (dB) on the y-axis (100.0 to 170.0) versus Cell Radius (km) on the x-axis (0.1 to 3.0). Three lines represent different scenarios: DCS 1800 (metropolitan centres), DCS 1800 (medium sized cities and suburban centres), and GSM 900. The DCS 1800 (metropolitan centres) line has a negative slope, while the others have positive slopes. + +Figure 4: Path loss vs Cell Radius for small cells (see section 3.4.2) + +# Annex D: Planning Guidelines for Repeaters + +## D.1 Introduction + +Repeaters can be used to enhance network coverage in certain locations. This annex provides guidelines for the design and installation of repeaters as network infrastructure elements. It covers both in building and outdoor applications. The principles within it may also form a basis for the design of repeaters for other applications within the system. + +## D.2 Definition of Terms + +The situation where two BTSs and two MSs are in the vicinity of a repeater is shown in figure 5 below. BTSA and MSA belong to operator A and BTSB and MSB belong to a different operator, operator B. + +When planning repeaters, operators should consider the effects of the installation on both co-ordinated and uncoordinated operators. In the following sections, it is assumed that in the uncoordinated scenario, the repeater is planned and installed only for the benefit of operator A. Operator A is therefore, co-ordinated and operator B uncoordinated. + +In certain situations, operators may agree to share repeaters. Under these conditions, the repeater is planned and installed to provide benefit to all co-ordinated operators. If all operators within the GSM or DCS bands share a repeater, only the co-ordinated scenario exists. + +![Figure 5: Repeater Scenario for two BTSs and two MSs. The diagram shows a central 'Repeater' box connected by dashed double-headed arrows to four surrounding boxes: 'BTS_A' (top-left), 'MA_A' (top-right), 'BTS_B' (bottom-left), and 'MS_B' (bottom-right).](f64e1e0997695248c0cd4122c5b1a170_img.jpg) + +``` + +graph TD + BTS_A[BTS_A] <--> Repeater[Repeater] + MA_A[MA_A] <--> Repeater + BTS_B[BTS_B] <--> Repeater + MS_B[MS_B] <--> Repeater + +``` + +Figure 5: Repeater Scenario for two BTSs and two MSs. The diagram shows a central 'Repeater' box connected by dashed double-headed arrows to four surrounding boxes: 'BTS\_A' (top-left), 'MA\_A' (top-right), 'BTS\_B' (bottom-left), and 'MS\_B' (bottom-right). + +**Figure 5: Repeater Scenario for two BTSs and two MSs** + +The following abbreviations are used in this annex: + +| | | +|--------|------------------------------------------------------------------------------------------------------------------------------------------| +| G | Repeater Gain | +| PBTS | BTS Output Power (in dBm) | +| PMS | MS Output Power (in dBm) | +| PmaxDL | Maximum Repeater Downlink Output Power (in dBm) | +| PmaxUL | Maximum Repeater Uplink Output Power (in dBm) | +| NDL | Repeater Downlink Noise Output in RX bandwidth (in dBm) | +| NUL | Repeater Uplink Noise Output in RX bandwidth (in dBm) | +| SMS | MS Reference Sensitivity (in dBm) | +| SBTS | BTS Reference Sensitivity (in dBm) | +| C/Ic | Carrier to Interference ratio for cochannel interference | +| CL1 | BTS to Repeater Coupling Loss (terminal to terminal) | +| CL2 | Repeater to MS Coupling Loss (terminal to terminal) | +| CL3 | The measured or estimated out of band coupling loss between a close coupled communication system and the repeater (terminal to terminal) | +| M | Number of carriers amplified by repeater | +| Gsys | The out of band repeater gain plus the gain of the external repeater antenna less the cable loss to that antenna. | +| Gcom_3 | The antenna gain of a close coupled communications system. | + +Ms A safety margin for equipment used inside public buildings which should include the height gain of the external repeater antenna plus, if appropriate, the out of band building penetration loss. + +## D.3 Gain Requirements + +The uplink and downlink gains should be such as to maintain a balanced link. The loss of diversity gain in the uplink direction may need to be considered. + +The gain of the repeater within its operating band should be as flat as possible to ensure that calls set up on a BCCH at one frequency can be maintained when the TCH is on a different frequency. + +The gain should be at least 15 dB smaller than the isolation between the antenna directed towards the BTS and the antenna directed towards the MSs, in order to prevent self oscillation. It is recommended to measure the isolation before installation of the repeater. + +Within the GSM/DCS1800 bands, but outside of the repeater operating range of frequencies, the installation of the repeater should not significantly alter the cellular design of uncoordinated operators. In the uncoordinated scenario, the repeater should not: + +- i) amplify downlink signals from another operator such that MSs of that operator within a reasonable distance of the repeater select a remote cell amplified by the repeater as opposed to the local cell of that operator. +- ii) amplify uplink signals from other operators' MSs within a reasonable distance of that repeater and transmit them in such a direction as to cause more interference to other BTSs of that operator than other MSs in the area. + +For equipment used in public buildings where other communications systems could operate in very close vicinity (less than [5]m) of the repeater antennas, special care must be taken such that out of band signals are not re-radiated from within the building to the outside via the repeater system and vice versa. When using repeaters with an antenna mounted on the outside of the building, the effect of any additional height should be considered. If the close coupled communication system is usually constrained within the building, it may be necessary to consider the negation of building penetration loss when planning the installation. It is the operators responsibility to ensure that the out of band gain of the repeater does not cause disruption to other existing and future co-located radio communication equipment. This can be done by careful choice of the repeater antennas and siting or if necessary, the inclusion of in-line filters to attenuate the out of band signals from other systems operating in the close vicinity of the repeater. + +The following equation can be used to ensure an adequate safety margin in these cases: + +$$G_{sys} < G_{com\_3} + CL3 - Ms \quad (D.3.1)$$ + +Where $G_{com\_3}$ is not known, a value of 2 dBi should be used. + +Where Ms is not known a value of 15 dB should be used. + +## D.4 Spurious/Intermodulation Products + +When planning repeaters, operators should ensure that during operation, the spurious and intermodulation products generated by the repeater at uncoordinated frequencies are less than the limits specified in 3GPP TS 45.005. + +At co-ordinated frequencies, the intermodulation attenuation of the repeater in the GSM/DCS bands should be greater than the following limits: + +$$IM3 \text{ attenuation}_{DL} \geq C/Ic + \text{BTS power control range} \quad (D.4.1)$$ + +$$IM3 \text{ attenuation}_{UL} \geq Pmax_{UL} - SBTS + C/Ic - CL1 \quad (D.4.2)$$ + +These limits apply in all cases except for initial random access bursts amplified by a repeater. + +## --- D.5 Output Power/Automatic Level Control (ALC) + +The maximum repeater output power per carrier will be limited by the number of carriers to be enhanced and the third order intermodulation performance of the repeater. Operators should ensure that the requirements of section D.4 are met for the planned number of active carriers, the output power per carrier, and the repeater implementation. + +The number of simultaneously active carriers to be enhanced may be different in the uplink and downlink directions. + +When designing ALC systems, the following should be considered: + +- i) When the ALC is active because of the close proximity of a particular MS, the gain is reduced for all MSs being served by the repeater, thereby leading to a possible loss of service for some of them. The operating region of the ALC needs to be minimized to reduce the probability of this occurrence. +- ii) The response of the ALC loop needs careful design. The ALC should not result in a significant distortion of the power/time profile of multiple bursts. +- iii) The ALC design should handle the TDMA nature of GSM signal so that it shall be effective for SDCCH and TCH transmissions with and without DTX. +- iv) The ALC may not operate quickly enough to cover the initial random access bursts sent by MSs. The intermodulation product requirement listed in section D.4 need not apply for these transient bursts. +- v) The ALC must have sufficient dynamic range to ensure that it maintains an undistorted output at the specified maximum power level when a fully powered-up MS is at the CL2min coupling loss. +- vi) In a non-channelized repeater the ALC will limit the total output power (i.e. peak of the sum of powers in each carrier). In most cases, the maximum ALC limit should be 3 dB above the power per carrier for two carriers whose third order intermodulation products just meet the requirements of section 4. When more than two carriers are simultaneously amplified, a higher limit may be employed provided the operator ensures that worst case intermodulation products meet the requirements of section D.4. + +## --- D.6 Local oscillator sideband noise attenuation + +A local oscillator of a heterodyne type repeater with high sideband noise can cause a problem in uncoordinated scenarios. If the receive level from an uncoordinated MS is significantly higher than the receive level from the co-ordinated MS, both signals can be mixed with approximately the same level into the same IF, degrading the performance of the wanted signal. + +To avoid this, an IF type repeater equipped with a local oscillator should have a sideband noise attenuation at an offset of 600 kHz from the local oscillator frequency given by the equation: + +$$\text{Sideband noise attenuation} = \text{CL2max} - \text{CL2min} + \text{C/Ic} \quad (\text{D.6.1})$$ + +## --- D.7 Delay Requirements + +The ability of the MS to handle step changes in the time of arrival of the wanted signal is specified in 3GPP TS 45.005. When planning repeaters for contiguous coverage with other infrastructure elements, it is recommended that the additional delay through the repeater does not exceed the performance of the MS. + +The additional delay through the repeater should not cause a problem except in extreme multipath propagation conditions. + +The delay of the repeater will reduce the range of the cell in the area enhanced by the repeater. A delay of 8 microseconds is equivalent to a range reduction of 2.4 km. + +## --- D.8 Wideband Noise + +Wideband noise is a problem for uncoordinated scenarios. The noise level at the uncoordinated operators' frequencies needs to be such that an uncoordinated MS or BTS in the vicinity of the repeater is not desensitized as a result. The + +following equations provide the maximum noise output by the repeater in the receiver bandwidth for the downlink and uplink: + +$$\text{NDL} \leq \text{SMS} - \text{C/Ic} + \text{CL2Bmin} \quad (\text{D.8.1})$$ + +$$\text{NUL} \leq \text{SBTS} - \text{C/Ic} + \text{CL1Bmin} \quad (\text{D.8.2})$$ + +In co-ordinated scenarios, the maximum noise output by the repeater in the receiver bandwidth for the downlink direction is: + +$$\text{NDL} \leq \text{PmaxDL} - \text{BTS power control range} - \text{C/Ic} \quad (\text{D.8.3})$$ + +## D.9 Outdoor Rural Repeater Example + +### D.9.1 Rural repeater example for GSM 900 + +Rural repeaters are used to enhance areas of poor coverage due to terrain limitations. The repeater is located where a suitable signal strength can be received from the donor BTS. Typical signal levels received from the BTS at the input port to the repeater are in the range -50 to -70 dBm. This figure includes the height advantage and the gain of the antenna directed towards the BTS. The received signal is amplified and retransmitted towards the area of poor coverage. + +Figure 6 shows typical signal levels in the uplink and downlink directions. Two limiting cases for the MS to repeater coupling loss are shown. A diversity gain of 3 dB is assumed at the BTS making the effective reference sensitivity level -107 dBm. + +![Figure 6: Uplink and downlink signal levels for a rural repeater. The diagram shows a BTS on the left, a Repeater in the center, and two MSs on the right. Signal levels are shown in dBm at various points. Uplink (left to right): BTS output +43 dBm, Repeater input -57 dBm (100 dB loss), Repeater output +13 dBm, MS1 input -57 dBm (70 dB loss), MS1 output +39 dBm, MS2 input -103 dBm (116 dB loss), MS2 output +39 dBm. Downlink (right to left): MS1 output +39 dBm, MS1 input -31 dBm (70 dB loss), Repeater input +24 dBm, Repeater output -76 dBm, BTS input -107 dBm (100 dB loss).](0fa5b60804100c3aead10404f9f226f9_img.jpg) + +Figure 6: Uplink and downlink signal levels for a rural repeater. The diagram shows a BTS on the left, a Repeater in the center, and two MSs on the right. Signal levels are shown in dBm at various points. Uplink (left to right): BTS output +43 dBm, Repeater input -57 dBm (100 dB loss), Repeater output +13 dBm, MS1 input -57 dBm (70 dB loss), MS1 output +39 dBm, MS2 input -103 dBm (116 dB loss), MS2 output +39 dBm. Downlink (right to left): MS1 output +39 dBm, MS1 input -31 dBm (70 dB loss), Repeater input +24 dBm, Repeater output -76 dBm, BTS input -107 dBm (100 dB loss). + +**Figure 6: Uplink and downlink signal levels for a rural repeater** + +The minimum coupling loss between the MS and the repeater is assumed to be 70 dB. + +#### D.9.1.1 Intermodulation products/ALC setting + +In this example an amplifier with a third order intercept ( $P_{\text{TOI}}$ ) of +50 dBm is assumed. + +The setting of the ALC for the two tone case is governed by the following equation (in dB): + +$$P_{\text{ALC}} = (2 P_{\text{TOI}} + \text{IM}_3)/3 + 3 \quad (\text{D.9.1.1})$$ + +where $\text{IM}_3$ is the limit specified in 3GPP TS 45.005. The inclusion of factor of 3 dB is described in section D.5. + +$$P_{\text{ALC}} = 24.3 \text{ dBm.}$$ + +Dependent on manufacturer guide-lines, the ALC setting may need to be reduced if many carriers are passing through the repeater. + +In this example, the ALC is unlikely to be activated on the downlink. It could do so in applications with smaller BTS to repeater coupling loss. + +On the uplink, the ALC is activated when the MS is transmitting at full power, at the minimum coupling loss. The repeater gain is reduced so that the output power is limited to 24 dBm. This gain reduction may degrade the service given to other MSs served by the repeater until the BTS power control algorithm has reduced the MS output power. + +#### D.9.1.2 Wideband noise + +Wideband noise needs to be considered for both the uplink and the downlink for uncoordinated scenarios. + +A 70 dB coupling loss is assumed between the repeater and the uncoordinated MS and the repeater and the uncoordinated BTS. Then, using equations D.8.1 and D.8.2, the maximum noise power output is given by: + +$$N_{DL} = N_{UL} = -104 - 9 + 70 = -43 \text{ dBm}$$ + +The maximum noise figure required to achieve this noise level in both the uplink and down link directions is given by the following equation: + +$$\begin{aligned} F &\leq N - G - kT - B \\ &\leq -43 - 70 - (-174) - 53 \\ &\leq 8 \text{ dB} \end{aligned}$$ + +where F is the noise figure, N is the maximum noise level, G is the gain, kT is equal -174 dBm/Hz and B is the bandwidth conversion factor equal to 53 dB. + +## D.10 Indoor Low Power Repeater Example + +### D.10.1 Indoor repeater example for DCS 1800 + +Indoor repeaters are used to compensate for the losses associated with building attenuation. + +The signal level received from the BTS at the input port to the repeater is typically in the range -60 to -80 dBm. This figure includes the height advantage of placing an antenna on the roof of the building and the gain of the antenna directed towards the BTS. + +Figure 7 shows typical signal levels in the uplink and downlink directions. Two limiting cases for the MS to repeater coupling losses are shown. + +![Figure 7: Uplink and downlink signal levels for indoor repeater. The diagram shows a BTS, a Repeater (45dB gain), and two MS units. Signal levels are shown in dBm at various points, with coupling losses of 110 dB, 40 dB, and 72 dB indicated.](eb450c92214e8409c1e0f0846e30d876_img.jpg) + +The diagram illustrates signal levels for an indoor repeater system. It consists of a BTS, a Repeater (45dB gain), and two MS units. The signal levels are shown in dBm at various points, with coupling losses of 110 dB, 40 dB, and 72 dB indicated. + +| Component | Uplink Signal Level (dBm) | Downlink Signal Level (dBm) | +|-----------------|---------------------------|-----------------------------| +| BTS | -91 | -107 | +| Repeater Input | -71 | +19 | +| Repeater Output | -26 | -10 | +| MS 1 | -56 | +30 | +| MS 2 | -98 | +30 | + +Figure 7: Uplink and downlink signal levels for indoor repeater. The diagram shows a BTS, a Repeater (45dB gain), and two MS units. Signal levels are shown in dBm at various points, with coupling losses of 110 dB, 40 dB, and 72 dB indicated. + +Figure 7: Uplink and downlink signal levels for indoor repeater + +The minimum coupling loss between the MS and the repeater is assumed to be 40 dB. + +#### D.10.1.1 Intermodulation products/ALC setting. + +Indoor repeaters are likely to be small low cost devices. Consequently, for indoor repeaters, the intermodulation performance is not as good as a rural repeater. In this example, an amplifier with a third order intercept ( $P_{TOI}$ ) of +40 dBm is assumed. + +For $P_{TOI}$ equal to 40 dBm and $IM_3$ equal to -30 dBm, then using equation D.9.1.1: + +$$P_{ALC} = 19.7 \text{ dBm}.$$ + +On the uplink, the ALC is activated when the MS is transmitting at full power, at the minimum coupling loss. The repeater gain is reduced so that the output power is limited to 19 dBm. The received signal level at the BTS of -91 dBm is likely to be below the desired level which the MS power control algorithm seeks to maintain. Therefore, the MS is + +likely to remain powered up and the ALC will remain in operation continuously. Since, there is likely to be only one simultaneous user of this type of repeater, this is normally acceptable. + +#### D.10.1.2 Wideband noise + +Assuming a minimum coupling loss between the repeater and an unco-ordinated BTS of 65 dB, and between the repeater and an uncoordinated MS of 40 dBm, the following maximum noise levels are obtained using equations D.8.1 and D.8.2. + +$$N_{DL} = -100 - 9 + 40 = -69 \text{ dBm}$$ + +$$N_{UL} = -104 - 9 + 65 = -48 \text{ dBm}$$ + +The uplink noise level is easy to achieve in view of the low gain. The maximum noise figure required to achieve this noise level in down link directions is given by the following equation: + +$$F \leq N - G - kT - B$$ + +$$\leq -69 - 40 - (-174) - 53$$ + +$$\leq 12 \text{ dB}$$ + +where F is the noise figure, N is the maximum noise level, G is the gain, kT is equal -174 dBm/Hz and B is the bandwidth conversion factor equal to 53 dB. + +## D.11 Example for a Repeater System using Frequency Shift + +### D.11.1 Example for GSM 900 + +Repeaters are used to enhance areas of poor coverage due to terrain limitations. The useable gain in an installation with a normal repeater is in generally limited in order to keep the repeater gain with a margin of 15 dB below the coupling of donor antenna and coverage antenna. Repeater systems using frequency shift relax the limitation in the usable gain of a normal repeater, due to different frequencies of the output signal and input signal. + +The repeater system consist of a master unit close to the BTS and at least one remote unit close to the area to be covered. The master unit amplifies the signals from the BTS and shifts them to other GSM channels called link channels in the allocated band of the operator. In the remote unit the link channels will be transferred to the original channels and amplified. A mobile station in the coverage area of the remote unit will detect the signals having passed the repeater system without any difference to a signal directly received from a BTS but the additional delay. The uplink channel settings of the repeater system follow exactly the settings of the downlink channels for the link path. Thus an uplink signal from a mobile in the coverage area of the repeater system will be received on its expected frequency by the BTS. Through application of sideband inversion technique on the downlink signals the BCCH cannot be decoded by a MS located between the master unit and the remote unit. + +The master unit of the repeater system is located in the vicinity of a donor BTS with a relatively low coupling path loss of typically 30 dB to 60 dB. The downlink amplification is adjusted to the lowest necessary value in order to reduce the transmitted signal strength on the link channels of the master unit output. + +As a consequence of the high gain of the remote unit of the repeater system the distance to the master unit can be relatively high while the desired output power level is still maintained. The link path loss may vary up to 90 dB depending on the maximum gain of the remote unit. Oscillation of the repeater units is suppressed due to the shift between input and output frequencies and the decoupling between coverage antenna and link antenna can be lower than the actual gain set in the remote unit. Therefore the effort for the installation at the remote unit location does not exceed the normal level. + +Figure 8 shows typical signal levels in the uplink and downlink directions. Two cases with maximum coupling loss of 135 dB and an assumed minimum coupling loss of 70 dB for the MS to repeater path are shown. + +![Figure 8: Uplink and downlink signal levels for a repeater system using frequency shift. The diagram shows a BTS connected to a Repeater System (Master Unit) via a Coupling Path (-50 dB). The Master Unit is connected to a Repeater System (Remote Unit) via a Link Path (-90 dB). The Remote Unit is connected to an MS via a Coverage Path (-70 dB). The MS is connected to another MS via a Coupling Path (-135 dB). Signal levels are shown in dBm for DL and UL paths at various points.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +Figure 8 illustrates the signal levels for a repeater system using frequency shift. The diagram shows the following components and signal levels: + +- DL (Downlink) Signal Levels:** + - BTS output: 43 dBm + - After Coupling Path (-50 dB): -7 dBm + - Master Unit output (G = 35 dB): 28 dBm + - After Link Path (-90 dB): -62 dBm + - Remote Unit output (G = 95 dB): 33 dBm + - After Coverage Path (-70 dB): -37 dBm + - MS output: -102 dBm +- UL (Uplink) Signal Levels:** + - MS output: -57 dBm + - After Coverage Path (-70 dB): -57 dBm + - Remote Unit output (G = 88 dB): 33 dBm + - After Link Path (-90 dB): -37 dBm + - Master Unit output (G = 50 dB): 33 dBm + - After Coupling Path (-50 dB): -104 dBm + - BTS input: -104 dBm + +Figure 8: Uplink and downlink signal levels for a repeater system using frequency shift. The diagram shows a BTS connected to a Repeater System (Master Unit) via a Coupling Path (-50 dB). The Master Unit is connected to a Repeater System (Remote Unit) via a Link Path (-90 dB). The Remote Unit is connected to an MS via a Coverage Path (-70 dB). The MS is connected to another MS via a Coupling Path (-135 dB). Signal levels are shown in dBm for DL and UL paths at various points. + +**Figure 8: Uplink and downlink signal levels for a repeater system using frequency shift** + +#### D.11.1.1 Intermodulation products/ALC setting and levelling criteria + +In this example a repeater system with separate amplifier chain for each GSM channel is used. Thus a multiple carrier operation does not have an impact on the ALC settings in order to keep intermodulation products low as described in subchapter D.9.1.1. + +On the uplink, the ALC will be activated when the MS is transmitting at full power, at the minimum coupling loss of 70 dB. The repeater gain is reduced in this example by the ALC setting which is assumed to an output power of 33 dBm. This gain reduction may degrade the service given to other MSs served by the repeater until the BTS power control algorithm has reduced the MS output power. + +In addition to the definitions in subchapter D.2 the following term are used: + +| | | +|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GMU(DL,UL) | Gain of master unit of repeater system in the downlink or uplink path | +| GRU(DL,UL) | Gain of remote unit of repeater system in the downlink or uplink path | +| GTOT(DL,UL) | Gain of the complete repeater system in one path calculated from BTS to remote unit repeater in the downlink or uplink path | +| FTOT(UL) | Noise figure of the complete repeater system including link path in the uplink path | +| FMU(UL) | Noise figure of the master unit of the repeater system in the uplink path | +| FRU(UL) | Noise figure of the remote unit of the repeater system in the uplink path | +| CL2max | Maximum Coupling loss between MS and repeater system | +| CL(MU<->RU) | Coupling loss between master unit and remote unit | +| PRUmax(DL) | Maximum output power of the remote unit in the downlink | +| Mn | Margin between repeater system output noise level at the BTS and equivalent input noise level of the BTS. This is a positive value if the repeater noise is lower. | +| NTOT | Noise level of repeater system at BTS input. | + +As an example for the leveling of a repeater system using frequency shift see figure 8. + +Downlink levelling: + +In the downlink path it is intended to have a certain signal level retransmitted from the remote unit for coverage purposes. Thus the leveling of the repeater system is determined by the formula: + +$$GRU(DL) = PRUmax(DL) + CL(MU<->RU) + CL1 - PBTS - GMU(DL)$$ + +In an installation the values for the coupling losses have to be measured. The remaining variable GMU(DL) has to be adjusted such, that the output power of the downlink signals of the master unit is as low as possible without danger of being interfered at the remote unit location. + +Uplink levelling: + +The adjustment of the uplink path gain is determined by the two demands: first the downlink and uplink path have to be balanced. Second, the receiver input shall not be desensitised by the repeater noise. The uplink gain between remote unit input and BTS input is + +$$GTOT(UL) = SBTS - PMS + CL2max = GRU(UL) + GMU(UL) - CL(MU<->RU) - CL1,$$ + +which can be transformed to + +$$\text{GRU(UL)} = \text{SBTS} + \text{CL1} + \text{CL(MU<->RU)} + \text{CL2max} - \text{PMS} - \text{GMU(UL)}.$$ + +This gives a relation for the gain setting of the remote unit with respect to the gain setting of the master unit when all coupling losses are determined. A further criteria for the leveling of the uplink is the total noise figure of the repeater system. In order to obtain a value close to the remote unit noise figure, the gain setting of the single repeater unit shall not be much lower than the path loss its output signal has to bridge. + +A desensitization of the BTS will be prevented by keeping the uplink gain of the single repeater units close to the value of the path loss to be bridged. The noise at the BTS receiver input can be calculated from the total noise figure of the repeater system: + +$$\text{FTOT(lin)} = \text{FRU(UL,lin)} + ( \text{FMU(UL,lin)} - 1 ) / ( \text{GRU(UL,lin)} * \text{CL(MU<->RU, lin)} ).$$ + +The variables marked by lin are linear and thus not logarithmic values. The noise at the BTS receiver input at room temperature for a given bandwidth of a GSM channel results in: + +$$\text{NTOT} = \text{FTOT} + \text{GTOT(UL)} + kT + B = \text{FTOT} + \text{GTOT(UL)} + (-174) + 53$$ + +This noise level has to be smaller than the equivalent noise at the receiver input: + +$$\text{NTOT} \leq \text{SBTS} - C/Ic - Mn = \text{SBTS} - 9\text{dB} - 3\text{dB}$$ + +A noise margin Mn equal to 3 dB is assumed. With a sensitivity of SBTS = -104 dBm the noise level of NTOT = -116 dBm should not be exceeded. + +#### D.11.1.2 Wideband noise + +The repeater system using frequency shift is supposed to operate with dedicated channelised amplifiers. Therefore the uncoordinated scenario does not apply. + +#### D.11.1.3 Multipath environment + +Regions with strong multipath signals of direct signals from the BTS and delayed signals from the repeater system of nearly equal level should be avoided. One method to achieve this can be a coupling of the master unit of the repeater system to the BTS sector directed to the counterside of the area to be covered by the repeater system. Furthermore the geographic situation may prevent as well the occurrence of such strong multipath areas, so that as well omnidirectional cells as donor cells can be possible. + +## D.12 Repeaters and Location Services (LCS) + +### D.12.1 Uplink–TOA positioning method + +Figure 9 illustrates the potential problem which can occur when a MS near the service area of a wireless repeater should be located with the Uplink–TOA positioning method (see GSM 03.71 for details about the Uplink–TOA positioning method). It is assumed that a TOA Location Measurement Unit (LMU) is deployed at each BTS site. The LMUs colocated at BTS 1 and 2 will report TOA measurements $\tau_1$ and $\tau_2$ , which correspond to the propagation path length between the MS and BTS 1 and 2, respectively. An ambiguity will exist, when the RF path between the MS and BTS 3 can either be a direct path ( $\tau_3$ ) or a path via the repeater ( $\tau_R + \tau_d + \tau_{RB}$ ), where $\tau_d$ is the delay of the repeater. + +![Figure 9: Repeater Scenario for Uplink-TOA. The diagram shows a central Mobile Station (MS) connected to three Base Transceiver Stations (BTS). BTS 1 is connected to LMU 1 with a propagation delay labeled τ1. BTS 2 is connected to LMU 2 with a propagation delay labeled τ2. BTS 3 is connected to LMU 3 with a propagation delay labeled τ3. Additionally, there is a 'Repeater for BTS 3' connected to LMU R. The MS has a direct path to the repeater with a propagation delay labeled τR. The repeater has a delay labeled τd and a path back to BTS 3 labeled τRB. Arrows indicate the signal flow from the MS to each LMU.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +Figure 9: Repeater Scenario for Uplink-TOA. The diagram shows a central Mobile Station (MS) connected to three Base Transceiver Stations (BTS). BTS 1 is connected to LMU 1 with a propagation delay labeled τ1. BTS 2 is connected to LMU 2 with a propagation delay labeled τ2. BTS 3 is connected to LMU 3 with a propagation delay labeled τ3. Additionally, there is a 'Repeater for BTS 3' connected to LMU R. The MS has a direct path to the repeater with a propagation delay labeled τR. The repeater has a delay labeled τd and a path back to BTS 3 labeled τRB. Arrows indicate the signal flow from the MS to each LMU. + +**Figure 9: Repeater Scenario for Uplink-TOA.** + +An ambiguity free location solution can be obtained, if a TOA LMU is deployed at the repeater site. The LMUs which should participate in the position measurement procedure are selected by the Serving Mobile Location Centre (SMLC) (GSM 03.71). If a BTS has an associated repeater, then the SMLC should select the LMU colocated at the BTS site as well as the LMU colocated at its repeater site for TOA measurements. When a RF path exists between the MS and the repeater, the LMU R will report the TOA measurement $\tau_R$ , which corresponds to the propagation path length between the MS and the repeater. If LMU 3 and LMU R are reporting TOA measurements, then the SMLC should neglect the TOA measurement from LMU 3, since this TOA measurement can be based on $(\tau_R + \tau_d + \tau_{RB})$ and will therefore result in a wrong location estimate. If the TOA LMU co-located at the repeater will not report a TOA measurement, it is obvious that no RF path between the MS and repeater exists. In that case, the TOA measurement from BTS 3 should be used. Other more intelligent processing can also be performed at the SMLC. + +To guarantee, that the Uplink-TOA positioning method works properly in radio environments with repeaters, a TOA LMU needs to be co located at the repeater site. + +If no LMU is co located at the repeater site, the SMLC should avoid selecting LMUs co located at a BTS which has an associated repeater. This requires that enough BTSs (LMUs) without repeaters are available in the vicinity of the MS and may therefore depend on the network. + +### D.12.2 Enhanced Observed Time Difference positioning method + +Figure 10 illustrates the potential problem which can occur when a MS near the service area of a wireless repeater should be located with the Enhanced Observed Time Difference (E-OTD) positioning method (see GSM 03.71 for details about the E-OTD positioning method). + +Assuming for simplicity that BTSs transmit at the moment 0, the MS will receive signals from BTSs 1, 2 and 4 at moments $\tau_1$ , $\tau_2$ , and $\tau_4$ , which correspond to the delays due to propagation paths between the MS and BTSs 1, 2 and 4, respectively. An ambiguity will exist, when the RF path between the BTS 3 and MS can either be a direct path ( $\tau_3$ ) or a path via the repeater ( $\tau_{RB} + \tau_d + \tau_R$ ), where $\tau_d$ is the delay of the repeater. + +![Diagram illustrating a Repeater Scenario for E-OTD. A central Mobile Station (MS) is shown receiving signals from four Base Transceiver Stations (BTS 1, BTS 2, BTS 3, and BTS 4). The signals from BTS 1, BTS 2, and BTS 4 are direct, with propagation delays labeled as tau_1, tau_2, and tau_4 respectively. The signal from BTS 3 is received via a Repeater for BTS 3, with propagation delays labeled as tau_3 (from BTS 3 to Repeater), tau_RB (from Repeater to MS), and tau_R (from Repeater to MS). The Repeater is also labeled with tau_d.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +Diagram illustrating a Repeater Scenario for E-OTD. A central Mobile Station (MS) is shown receiving signals from four Base Transceiver Stations (BTS 1, BTS 2, BTS 3, and BTS 4). The signals from BTS 1, BTS 2, and BTS 4 are direct, with propagation delays labeled as tau\_1, tau\_2, and tau\_4 respectively. The signal from BTS 3 is received via a Repeater for BTS 3, with propagation delays labeled as tau\_3 (from BTS 3 to Repeater), tau\_RB (from Repeater to MS), and tau\_R (from Repeater to MS). The Repeater is also labeled with tau\_d. + +**Figure 10: Repeater Scenario for E-OTD.** + +An ambiguity free location solution can be obtained, if the MS measures sufficient number of BTSs so that the measurements concerning the BTS 3 (which can be direct measurements or via the repeater) can be dropped off. In the situation in Fig. 10, there are three other BTSs received by the MS, and the measurements from the BTS 3 can be omitted. Another possibility for ambiguity free location solution is to use other available information to judge whether the signal from the repeater or the direct signal from the BTS has been measured. For example the initial location estimate based on CI and TA information can be used to estimate whether the BTS or the repeater is more likely to be received by the MS. There can be also other implementation specific solutions in the SMLC. + +### D.12.3 Radio Interface Timing measurements + +Figure 11 illustrates the potential problem which can occur when a LMU near the service area of a wireless repeater performs Radio Interface Timing (RIT) measurements (see GSM 03.71 for details about the RIT measurements). + +![Diagram of a Repeater Scenario for RIT measurements. A central LMU (Location Measuring Unit) is shown receiving signals from three Base Transceiver Stations (BTS). BTS 1 and BTS 2 send direct signals to the LMU, labeled with propagation delays tau_1 and tau_2 respectively. BTS 3 sends a signal that can take two paths: a direct path labeled tau_3, or an indirect path via a 'Repeater for BTS 3'. The indirect path consists of three segments: tau_RB from BTS 3 to the repeater, tau_d from the repeater's input to its output, and tau_R from the repeater to the LMU. The repeater is depicted as a circle with an L-shaped antenna.](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +Diagram of a Repeater Scenario for RIT measurements. A central LMU (Location Measuring Unit) is shown receiving signals from three Base Transceiver Stations (BTS). BTS 1 and BTS 2 send direct signals to the LMU, labeled with propagation delays tau\_1 and tau\_2 respectively. BTS 3 sends a signal that can take two paths: a direct path labeled tau\_3, or an indirect path via a 'Repeater for BTS 3'. The indirect path consists of three segments: tau\_RB from BTS 3 to the repeater, tau\_d from the repeater's input to its output, and tau\_R from the repeater to the LMU. The repeater is depicted as a circle with an L-shaped antenna. + +**Figure 11: Repeater Scenario for RIT measurements.** + +The ambiguity problem applies also to LMUs that measure RIT information for E-OTD and Uplink-TOA methods, as well as for certain assisted GPS variants. In Figure 11 the LMU measures directly signals from BTSs 1 and 2 (BTS serving the LMU). However the RF path between the BTS 3 and LMU can either be a direct path ( $\tau_3$ ) or a path via the repeater ( $\tau_{RB} + \tau_d + \tau_R$ ). The solution is that the operator selects such LMU sites that can only hear only the BTS or the repeater (e.g. based on network planning information). This can be enhanced by using directional antenna for the LMU, so that the antenna points towards e.g. the repeater, not the BTS, or vice versa. + +# Annex E: Change history + +| SMG# | SPEC | CR | CAT | PHASE | VERS | NEW_VERS | SUBJECT | +|---------------|--------|------|-----|--------|-------|----------|--------------------------------------------------------------------------------------| +| s25 | 03.30 | A003 | | R97 | 5.0.0 | | Repeater Systems using Frequency Shift | +| s26 | 03.30 | A003 | | R97 | 5.0.0 | 6.0.0 | Repeater systems using Frequency Shift | +| s29 | 03.30 | | | R98 | 6.0.1 | 7.0.0 | Version 7.0.0 for Release '98 | +| s29 | 03.30 | A005 | | R99 | 6.0.1 | 8.0.0 | GSM 400 cell sizes and RF budgets | +| s30 | 03.30 | A006 | | R99 | 8.0.0 | 8.1.0 | 850 link budgets | +| s30b | 03.30 | A007 | | R99 | 8.1.0 | 8.2.0 | GSM RF budgets updated with actual handheld Mean Effective Gain (-antenna/body loss) | +| s30b | 03.30 | A008 | | R99 | 8.1.0 | 8.2.0 | Operation with extended TA IE added in 03.30 | +| s31 | 03.30 | A010 | | R99 | 8.2.0 | 8.3.0 | LCS operation with repeaters | +| | | | | | | | | +| GERAN# | | | | | | | September 2000 - 3G Release 4 | +| G01 | 03.30 | A011 | B | R00 | 8.3.0 | 4.0.0 | CR 03.30-A011 GSM 700 cell sizes and RF budgets (Release 4) | +| October 2000 | 43.030 | | | Rel-4 | 4.0.0 | 4.0.1 | GSM references revert to pre-Release-4 spec number format. | +| June 2002 | | | | | | | | +| G10 | 43.030 | | | Rel-5 | | 5.0.0 | Version for Release 5 | +| August 2002 | | | | | | | | +| G11 | 43.030 | 003 | | Rel-5 | 5.0.0 | 5.1.0 | Correction of Mean Effective Gain for GSM 400 | +| January 2005 | | | | | | | | +| G23 | | | | Rel-6 | | 6.0.0 | Version for Release 6 | +| G25 | 43.030 | 004 | A | Rel-6 | | 6.1.0 | Example of RF link budget for DCS 1800 MS 1 W Handheld with External LNA | +| G35 | | | | Rel-7 | | 7.0.0 | Version for Release 7 | +| G40 | | | | Rel-8 | | 8.0.0 | Version for Release 8 | +| G44 | | | | Rel-9 | | 9.0.0 | Version for Release 9 | +| G49 | | | | Rel-10 | | 10.0.0 | Version for Release 10 | +| G55 | | | | Rel-11 | | 11.0.0 | Version for Release 11 | \ No newline at end of file diff --git a/marked/Rel-11/43_series/43050/088921fa3f5a44c8551815122517eefd_img.jpg b/marked/Rel-11/43_series/43050/088921fa3f5a44c8551815122517eefd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d65cea69233e4cb92e25969957469045cd27ffeb --- /dev/null +++ b/marked/Rel-11/43_series/43050/088921fa3f5a44c8551815122517eefd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9d3a77aa385ec7320452dcf4144fed8f0cb5f903ad6397f0b4c78e0069e07d4 +size 27465 diff --git a/marked/Rel-11/43_series/43050/20136850feb70fd71c7d41cdae203ebb_img.jpg b/marked/Rel-11/43_series/43050/20136850feb70fd71c7d41cdae203ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28fb2cdb07333e982064c8a6f719d68897f5b9df --- /dev/null +++ b/marked/Rel-11/43_series/43050/20136850feb70fd71c7d41cdae203ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8dcd0a9a1fcd1ecf8f4460482e491d4203ac05737eed5c3e3a5aaa083841b3e +size 26170 diff --git a/marked/Rel-11/43_series/43050/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg b/marked/Rel-11/43_series/43050/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2d0befafa9eecc490745c2a7c77341d715741b1 --- /dev/null +++ b/marked/Rel-11/43_series/43050/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5ea677b365b3635819ad4c09ecd96da427cb22c9e64522ab01e81375a225794 +size 19151 diff --git a/marked/Rel-11/43_series/43050/42984972f322f3db6c384a0b630d1947_img.jpg b/marked/Rel-11/43_series/43050/42984972f322f3db6c384a0b630d1947_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af60bd33470a4b1bfe5b672f973cf2394f201435 --- /dev/null +++ b/marked/Rel-11/43_series/43050/42984972f322f3db6c384a0b630d1947_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6baa0b0c523c1dfbd0ecc0ae90dbf230ed44ae99683fa9becf25ecc62737be88 +size 1751 diff --git a/marked/Rel-11/43_series/43050/474a819357587e34949a3e110ff19b30_img.jpg b/marked/Rel-11/43_series/43050/474a819357587e34949a3e110ff19b30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66c7b155457fb21b8ace5635b08345bee8822cd7 --- /dev/null +++ b/marked/Rel-11/43_series/43050/474a819357587e34949a3e110ff19b30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c63addd660144aef10c3d8aacae1f2f8c4ce860c76a0d33d56a192e0e8f1c663 +size 62450 diff --git a/marked/Rel-11/43_series/43050/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg b/marked/Rel-11/43_series/43050/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66603deaebb6397aa6761daaae5d450d541fa832 --- /dev/null +++ b/marked/Rel-11/43_series/43050/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:607547868dd84b6e51b786dfeff8c8753c74cbc592f8cba313f44bb1a9464ef4 +size 19238 diff --git a/marked/Rel-11/43_series/43050/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg b/marked/Rel-11/43_series/43050/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..debef16e68b627a09692bf2197afa5d09084640b --- /dev/null +++ b/marked/Rel-11/43_series/43050/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62d8902d6bcf950fe1e743b00004f722d5682ddb47d2cafbefaae8d44d088d8b +size 18501 diff --git a/marked/Rel-11/43_series/43050/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg b/marked/Rel-11/43_series/43050/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..73d06f0aff815c22314b10a2e59ba285a989c38f --- /dev/null +++ b/marked/Rel-11/43_series/43050/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e2845dd8171f81bd7feab56e8f16164e7ff658c907ff7f82c4ea2af3caf64b8 +size 22880 diff --git a/marked/Rel-11/43_series/43050/9681f7b385905132ecfb6a8aa66d1f58_img.jpg b/marked/Rel-11/43_series/43050/9681f7b385905132ecfb6a8aa66d1f58_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38ae8b74b812bea5c5100fc8edbd86879345634e --- /dev/null +++ b/marked/Rel-11/43_series/43050/9681f7b385905132ecfb6a8aa66d1f58_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2bef51c0150cc4a696c33eca968c484bae3928fc083b2525e5d368f9bb73aca6 +size 1621 diff --git a/marked/Rel-11/43_series/43050/9d4bac4111fe96f0d6f746b95343cbd8_img.jpg b/marked/Rel-11/43_series/43050/9d4bac4111fe96f0d6f746b95343cbd8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e38d5ff9f97e3a5f0c2e539570d5b7dda4faff94 --- /dev/null +++ b/marked/Rel-11/43_series/43050/9d4bac4111fe96f0d6f746b95343cbd8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36c085e33fcf5cebe23c51554828f5df1d37c0a2eb71a5f67a0edd48ae4b4c16 +size 971 diff --git a/marked/Rel-11/43_series/43050/a3953dce8dbd7ef15d61a314dbef2cf9_img.jpg b/marked/Rel-11/43_series/43050/a3953dce8dbd7ef15d61a314dbef2cf9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e8d4f2e437972a01aea418dfabbd2c3b9947156 --- /dev/null +++ b/marked/Rel-11/43_series/43050/a3953dce8dbd7ef15d61a314dbef2cf9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8fa94ea05e3dde34bcec649488f16d468219cdb1a7da63b22968d9037714ccdb +size 24569 diff --git a/marked/Rel-11/43_series/43050/bb3354f497635d15bef873577125c48d_img.jpg b/marked/Rel-11/43_series/43050/bb3354f497635d15bef873577125c48d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5256acc39b3e223b2b883a3ea9ef2200becd0820 --- /dev/null +++ b/marked/Rel-11/43_series/43050/bb3354f497635d15bef873577125c48d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c53d647cb514cbcc9260513f756bbdeaa11222d5d3c4501d589cd7903c3f4e3f +size 32165 diff --git a/marked/Rel-11/43_series/43050/c42e926097d01653b793c04b49e764b2_img.jpg b/marked/Rel-11/43_series/43050/c42e926097d01653b793c04b49e764b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4026a50519d6ad019fd19f00adc8169d14a1d011 --- /dev/null +++ b/marked/Rel-11/43_series/43050/c42e926097d01653b793c04b49e764b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:288d8749c2a4275881e7a64251744d644bfec30bd704fad88ba70ce0d7ae3bbc +size 42734 diff --git a/marked/Rel-11/43_series/43050/d63dcf9b188f03572093f2f604d7b8ed_img.jpg b/marked/Rel-11/43_series/43050/d63dcf9b188f03572093f2f604d7b8ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..040eec33416749ffe833e9ba3691becd7bcae285 --- /dev/null +++ b/marked/Rel-11/43_series/43050/d63dcf9b188f03572093f2f604d7b8ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7bba54ece1e02799b350c63e8bfc630c74f85c5ab7c02d06d5a7d87dd40b27ae +size 1057 diff --git a/marked/Rel-11/43_series/43050/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-11/43_series/43050/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b988ea17f7c88398bf02dc64b46e0093a10e7b1 --- /dev/null +++ b/marked/Rel-11/43_series/43050/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c462062e9ae513a5e6b5a0ad5938b392835194a93599101c1af2b6d3118dbed +size 87943 diff --git a/marked/Rel-11/43_series/43050/e354b57563dae469c00b412b2abdf765_img.jpg b/marked/Rel-11/43_series/43050/e354b57563dae469c00b412b2abdf765_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06537f73bea77d73ed28deedf0018ba9d6dffcae --- /dev/null +++ b/marked/Rel-11/43_series/43050/e354b57563dae469c00b412b2abdf765_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42a668441a714de000ee47d491317561e29db11d2a24b17b4c618183c121918f +size 19507 diff --git a/marked/Rel-11/43_series/43050/e3c1d325b828c44049a7ac37e5b34603_img.jpg b/marked/Rel-11/43_series/43050/e3c1d325b828c44049a7ac37e5b34603_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..202210870bad4e3f1dfaed65f90800e680ef6f4e --- /dev/null +++ b/marked/Rel-11/43_series/43050/e3c1d325b828c44049a7ac37e5b34603_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8f791d8ab85bb0c88448a49c6c3489d6cae9f09431dcad345a6c518fc7f4d48 +size 1461 diff --git a/marked/Rel-11/43_series/43050/e7c6a6e4c3047dac05a3b92e396e9794_img.jpg b/marked/Rel-11/43_series/43050/e7c6a6e4c3047dac05a3b92e396e9794_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b685206bcebc50d7c242df7b9ea39fcde54b39f --- /dev/null +++ b/marked/Rel-11/43_series/43050/e7c6a6e4c3047dac05a3b92e396e9794_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ad618dd413b0862bb747fabb6807d69565130f83c996b63c7e7232666330106 +size 17831 diff --git a/marked/Rel-11/43_series/43050/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/marked/Rel-11/43_series/43050/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c07648dce5eb64181155f6757324ec8de6baefc --- /dev/null +++ b/marked/Rel-11/43_series/43050/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8da118dd2914453f8a3cdfb7a8c618c68cb111055ef91230140ba0786c88d8fc +size 25058 diff --git a/marked/Rel-11/43_series/43050/e90987faabad6a6665cd8ed1151dc474_img.jpg b/marked/Rel-11/43_series/43050/e90987faabad6a6665cd8ed1151dc474_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c22f0cedad27f136391a2cab29473d71ebefa86 --- /dev/null +++ b/marked/Rel-11/43_series/43050/e90987faabad6a6665cd8ed1151dc474_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a034982324e0eece14f80e403281d52a4a1a4839cd23f13aa155c7e02789e51 +size 27820 diff --git a/marked/Rel-11/43_series/43050/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-11/43_series/43050/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a419e26204992b00894d734a26308aca9f8c22aa --- /dev/null +++ b/marked/Rel-11/43_series/43050/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e323c0ecd2cab18e218553c329ff2d0e9100600d04e812cfb4867df94d89d2a +size 92691 diff --git a/marked/Rel-11/43_series/43050/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg b/marked/Rel-11/43_series/43050/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..618b08b791d023fa50ccfd47d2657520871e336a --- /dev/null +++ b/marked/Rel-11/43_series/43050/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:86f781364468e989a17dc0097b5cf8fd87a3143fb812ed3a2599da04950c0e0c +size 160811 diff --git a/marked/Rel-11/43_series/43050/f0a97d0d3818a253c1d2a009966081b1_img.jpg b/marked/Rel-11/43_series/43050/f0a97d0d3818a253c1d2a009966081b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7dd868c0c93014421ca1c9546470b3957d6ffa99 --- /dev/null +++ b/marked/Rel-11/43_series/43050/f0a97d0d3818a253c1d2a009966081b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bef18c629f9bcea0a23d24558743e301ec4d02f2bbc7ad2358e24357f020a61c +size 73926 diff --git a/marked/Rel-11/43_series/43050/fb29be0f9d67f05cd4c69fd091e93ebb_img.jpg b/marked/Rel-11/43_series/43050/fb29be0f9d67f05cd4c69fd091e93ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..65738f25734384f130f4d3092e3649a63d8bc38f --- /dev/null +++ b/marked/Rel-11/43_series/43050/fb29be0f9d67f05cd4c69fd091e93ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:938f6dc2745e1ad5e0e3ec796a2ee14052befe23bc25cefe5c1b5f418bf05f1d +size 1070 diff --git a/marked/Rel-11/43_series/43050/raw.md b/marked/Rel-11/43_series/43050/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c5510dd3ada4d211eec18e93c714e07ece44af21 --- /dev/null +++ b/marked/Rel-11/43_series/43050/raw.md @@ -0,0 +1,1246 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 1.1 References ..... | 7 | +| 1.2 Abbreviations ..... | 9 | +| 1.3 Introduction ..... | 10 | +| 2 Network configurations..... | 10 | +| 2.1 General ..... | 10 | +| 2.2 Model of the PLMN ..... | 10 | +| 2.3 Interfaces ..... | 10 | +| 2.4 Configurations of connections ..... | 11 | +| 2.4.1 General configurations of connections ..... | 11 | +| 2.4.2 Reference configurations to illustrate delay and echo control issues..... | 11 | +| 2.5 4-wire circuits in the PLMN..... | 12 | +| 3 Transmission performance ..... | 12 | +| 3.1 Overall Loss/Loudness ratings..... | 13 | +| 3.1.1 Connections with handset MSs ..... | 13 | +| 3.1.2 Connections with handsfree MSs ..... | 13 | +| 3.1.3 Connections with headset MSs..... | 13 | +| 3.2 Stability Loss..... | 14 | +| 3.3 Delay ..... | 14 | +| 3.3.1 General ..... | 14 | +| 3.3.2 Sources of delay ..... | 14 | +| 3.3.2.1 Elements of the PLMN that cause delay..... | 14 | +| 3.3.2.2 Elements of the PSTN that cause delay ..... | 14 | +| 3.3.3 Effects of delay ..... | 14 | +| 3.3.4 Allocation of delay to the PLMN ..... | 15 | +| 3.3.4.1 Allocation of delay to the PLMN when using a full rate system..... | 15 | +| 3.3.4.2 Allocation of delay to the PLMN when using a half rate system ..... | 15 | +| 3.3.5 Delay of various network configurations ..... | 15 | +| 3.3.5.1 National and international connections with no echo control in the PSTN (reference configurations A)..... | 15 | +| 3.3.5.2 National and international connections with echo control in the PSTN (reference configurations B) ..... | 15 | +| 3.3.5.3 Connections where re-routing leads to a significant increase in transmission path length (reference configurations C)..... | 16 | +| 3.3.6 Delay related requirements on the MS ..... | 16 | +| 3.3.6.1 Full rate MS ..... | 16 | +| 3.3.6.2 Half rate MS..... | 16 | +| 3.3.6.3 Handsfree MS ..... | 16 | +| 3.4 Echo..... | 16 | +| 3.4.1 General ..... | 16 | +| 3.4.2 Electrical echo control in the PLMN (Reference configurations A) ..... | 17 | +| 3.4.3 Acoustic echo control in the PLMN ..... | 17 | +| 3.4.4 Interaction between tandem echo control devices (reference configurations B & C)..... | 17 | +| 3.5 Clipping..... | 17 | +| 3.5.1 General ..... | 17 | +| 3.5.2 Properties of voice switches in the PLMN ..... | 18 | +| 3.5.3 Problems of tandem voice switching..... | 18 | +| 3.6 Idle channel noise (handset and headset MS) ..... | 18 | +| 3.6.1 Sending ..... | 18 | +| 3.6.2 Receiving..... | 18 | +| 3.7 Noise contrast..... | 18 | +| 3.7.1 General ..... | 18 | +| 3.7.2 Elements of a PLMN which can cause noise contrast impairment ..... | 19 | +| 3.7.3 Reduction of noise contrast ..... | 19 | +| 3.7.3.1 Reduction of noise contrast by limiting the noise received by the microphone ..... | 19 | +| 3.7.3.1.1 Headset MS ..... | 19 | + +| | | | +|-------------------------------|----------------------------------------------------------------------------------------------------|-----------| +| 3.7.3.1.2 | Handset MS..... | 19 | +| 3.7.3.1.3 | Handsfree MS..... | 20 | +| 3.7.3.2 | Reduction of noise contrast by insertion of comfort noise ..... | 20 | +| 3.7.4 | Consequence of the introduction of high comfort noise levels on other voice-operated devices ..... | 20 | +| 3.8 | Sensitivity/frequency characteristics..... | 20 | +| 3.8.1 | Headset and Handset MSs ..... | 20 | +| 3.8.1.1 | Sending ..... | 20 | +| 3.8.1.2 | Receiving ..... | 20 | +| 3.8.2 | Handsfree MS..... | 21 | +| 3.8.2.1 | Sending ..... | 21 | +| 3.8.2.2 | Receiving ..... | 21 | +| 3.9 | Distortion (handset and headset MS)..... | 21 | +| 3.9.1 | Gain variation, sending..... | 21 | +| 3.9.2 | Gain variation, receiving ..... | 21 | +| 3.10 | Sidetone (handset and headset MS) ..... | 22 | +| 3.10.1 | Sidetone loss ..... | 22 | +| 3.10.1.1 | LSTR..... | 22 | +| 3.10.1.2 | STMR..... | 22 | +| 3.10.2 | Sidetone distortion..... | 22 | +| 3.11 | Not used..... | 22 | +| 3.12 | Requirements for information tones..... | 22 | +| 3.13 | Crosstalk..... | 23 | +| 3.13.1 | Near and far end crosstalk ..... | 23 | +| 3.13.2 | Go/return crosstalk ..... | 23 | +| 3.14 | MS Ambient Noise Rejection ..... | 23 | +| Annex A (informative): | Considerations on the Acoustic Interface of the Mobile Station ..... | 32 | +| A.1 | Handsfree MS ..... | 32 | +| A.2 | Handset MS..... | 32 | +| A.3 | Headset MS..... | 32 | +| A.4 | Inter-reaction with DTX..... | 32 | +| Annex B (normative): | Test considerations..... | 33 | +| Annex C (normative): | Transmission requirements testing..... | 34 | +| C.1 | Not used | | +| C.2 | Not used | | +| C.3 | Not used | | +| C.4 | Not used | | +| C.5 | Variation of gain with input level ..... | 34 | +| C.5.1 | Sending..... | 34 | +| C.5.2 | Receiving..... | 34 | +| C.6 | Not used ..... | 34 | +| C.7 | Not used ..... | 34 | +| C.8 | Not used ..... | 34 | +| C.9 | Not used ..... | 34 | +| C.10 | Delay for handsfree MS ..... | 34 | +| C.10.1 | Uplink..... | 34 | +| C.10.2 | Downlink..... | 35 | +| C.10.3 | Result..... | 35 | +| Annex D (normative): | MS delay requirement definition ..... | 36 | +| D.1 | Full rate MS delay requirement definition ..... | 36 | +| D.2 | Half rate MS delay requirement definition ..... | 37 | +| Annex E (informative): | Adaptive gain control..... | 38 | +| Annex F (informative): | Change History..... | 39 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document describes the transmission planning aspects pertaining to the speech service in the GSM PLMN system. Due to technical and economic factors, there cannot be full compliance with the general characteristics of international telephone connections and circuits recommended by the ITU-T. + +The present document gives guidance as to the precautions, measures and minimum requirements needed for successful interworking of the PLMN with the national and international PSTN. The present document identifies a number of routeing and network configurations. The objective is to reach a quality as close as possible to ITU-T standards in order to safeguard the performance seen by PSTN customers. + +The requirements stated for acoustics in dual mode GSM/3GPP handsets shall be interpreted as requirement on acoustics in the GSM 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 TR 41.004: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". +- [2] 3GPP TS 43.004: "Digital cellular telecommunications system (Phase 2+); Signalling requirements relating to routeing of calls to mobile subscribers". +- [3] 3GPP TS 46.001: "Digital cellular telecommunications system (Phase 2+); Full rate speech processing functions". +- [4] 3GPP TS 46.010: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Transcoding". +- [5] 3GPP TS 46.011: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Substitution and muting of lost frames for full rate speech channels". +- [6] 3GPP TS 46.012: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Comfort noise aspect for full rate speech traffic channels". +- [7] 3GPP TS 46.031: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Discontinuous Transmission (DTX) for full rate speech traffic channels". +- [8] 3GPP TS 46.032: "Digital cellular telecommunications system (Phase 2+); Voice Activity Detection (VAD)". +- [9] 3GPP TS 46.002: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech processing functions". +- [10] 3GPP TS 46.020: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding". +- [11] 3GPP TS 46.021: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Substitution and muting of lost frames for half rate speech traffic channels". +- [12] 3GPP TS 46.022: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels". + +- [13] 3GPP TS 46.041: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels". +- [14] 3GPP TS 46.042: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Voice Activity Detection (VAD) for half rate speech traffic channels". +- [15] I-ETS 300 245-2: "Integrated Services Digital Network (ISDN): Technical characteristics of telephony terminals: Part 2: PCM A-Law handset telephony". +- [16] ITU-T Recommendation G.103 (1998): "Hypothetical reference connections". +- [17] ITU-T Recommendation G.111 (1993): "Loudness ratings (LRs) in an international connection". +- [18] ITU-T Recommendation G.113 (1996): "Transmission impairments". +- [19] ITU-T Recommendation G.114 (2000): "Mean one-way propagation time". +- [20] ITU-T Recommendation G.121 (1993): "Loudness ratings (LRs) of national systems". +- [21] ITU-T Recommendation G.122 (1993): "Influence of national systems on stability, talker echo, and listener echo in international connections". +- [22] ITU-T Recommendation G.131 (1996): "Control of talker echo". +- [23] ITU-T Recommendation G.168 (2000): "Digital network echo cancellers". +- [24] ITU-T Recommendation G.223 (1988): "Assumptions for the calculation of noise on hypothetical reference circuits for telephony". +- [25] ITU-T Recommendation G.703 (1998): "Physical/electrical characteristics of hierarchical digital interfaces". +- [26] ITU-T Recommendation G.711 (1988): "Pulse code modulation (PCM) of voice frequencies". +- [27] ITU-T Recommendation G.712 (1996): "Transmission performance characteristics of pulse code modulation". +- [28] ITU-T Recommendation G.167 (1993): "Acoustic Echo Controllers". +- [29] ITU-T Recommendation M.1020 (1993): "Characteristics of special quality international leased circuits with special bandwidth conditions". +- [30] ITU-T Recommendation M.1025 (1993): "Characteristics of special quality international leased circuits with basic bandwidth conditioning". +- [31] ITU-T Recommendation M.1030 (1988): "Characteristics of ordinary quality international leased circuits forming part of private switched telephone networks". +- [32] ITU-T Recommendations M.1040 (1988): "Characteristics of ordinary quality international leased circuits". +- [33] ITU-T Recommendation O.132 (1988): "Specification for a quantizing distortion measuring apparatus using a sinusoidal test signal". +- [34] ITU-T Recommendation P.11 (1993): "Effect of transmission impairments". +- [35] ITU-T Recommendation P.340(2000): "Transmission characteristics of hands-free telephones". +- [36] ITU-T Recommendation P.38 (1993): "Transmission characteristics of operator telephone systems (OTS)". +- [37] ITU-T Recommendation P.50 (1999): "Artificial voices". +- [38] ITU-T Recommendation P.51 (1996): "Artificial mouths". +- [39] ITU-T Recommendation P.64 (1999): "Determination of sensitivity/frequency characteristics of local telephone systems". + +- [40] ITU-T Recommendation P.76 (1988): "Determination of loudness ratings; fundamental principles". +- [41] ITU-T Recommendation P.79 (1999): "Calculation of loudness ratings". +- [42] ITU-T Recommendation Q.35/E180 (1998): "Technical characteristics of tones for the telephone service". +- [43] ITU-T Recommendation Q.551 (1996): "Transmission characteristics of digital exchanges". +- [44] ITU-T Blue Book (1988): "Volume V, Supplement 13: Noise spectra". +- [45] ISO 3 (1973): "Preferred numbers – series of preferred numbers". +- [46] ITU-T Recommendation P.57 (1996): "Artificial Ears". +- [47] ITU-T Recommendation P.58 (1996): "Head and Torso Simulator for Telephonometry". +- [48] I-ETS 300 245-3: "Integrated Services Digital Network (ISDN): Technical characteristics of telephony terminal: Part 3: PCM A-law loudspeaking and handsfree telephony". +- [49] 3GPP TS 26.131: "Terminal Acoustic Characteristics for Telephony; Requirements" +- [50] 3GPP TS 26.132: "Speech and video telephony terminal acoustic test specification" +- [51] 3GPP TS 51.010: "Digital cellular telecommunications system (Phase 2+); Mobile Station (MS) conformance specification" + +## 1.2 Abbreviations + +In addition to those below, the abbreviations used in the present document are listed in GSM 01.04. + +| | | +|-------|-----------------------------------------------------------| +| ADC | Analogue to Digital Converter | +| ADPCM | Adaptive Differential Pulse Code Modulation | +| AEC | Acoustic Echo Control | +| BSC | Base Station Controller (excluding transmission systems) | +| BTS | Base Transceiver Station (excluding transmission systems) | +| DAC | Digital to Analogue Converter | +| DMR | Digital Mobile Radio | +| DSI | Digital Speech Interpolation | +| EEC | Electric Echo Control | +| EL | Echo Loss | +| ERP | Ear Reference Point | +| FDM | Frequency Division Multiplex | +| ISC | International Switching | +| LE | Local Exchange | +| LSTR | Listener Sidetone Rating | +| MRP | Mouth Reference Point | +| OLR | Overall Loudness Rating | +| PCM | Pulse Code Modulation | +| POI | Point of Interconnection (with PSTN) | +| RLR | Receiver Loudness Rating | +| SLR | Send Loudness Rating | +| STMR | Sidetone Masking Rating | +| UPCMI | 13-bit Uniform PCM Interface | + +## 1.3 Introduction + +Since the transmission quality and the conversational quality of the PLMN will in general be lower than the quality of the PSTN connection due to coding distortion, delay, etc., only some transmission aspects can be brought in line with ITU-T Recommendations. It is therefore necessary to improve the overall quality as much as possible by implementing proper routing and network configurations. + +It should be recognized that the transmission plan for the GSM PLMN cannot lead to major changes in the PSTN. However, it is important to use the improvements in the evolving PSTN (e.g. digitalization, introduction of echo cancellers) in an effective way. + +The transmission requirements are in the first place based on international connections. When the quality is sufficient for international connections, it can be assumed that the national connections will have the same or better quality. + +In order to obtain a sufficient quality in the connection, it is preferable to have digital connectivity between the Base Station System (BSS) and the international exchange. The PLMN requirements are based on this assumption. When this situation cannot be provided, a lower quality must temporarily be accepted. + +The present document consists of two parts: one will deal with network configurations, the other with transmission performance. + +The part about network configurations gives information about the reference connections, on which the transmission plan is based. Furthermore, some guidelines are presented for improvement of the transmission quality in the evolving (digital) PSTN. + +The part about transmission performance gives mainly characteristics of the transmission between MS acoustic interface (MRP/ERP) and the interface between the PLMN and the PSTN (POI). For transmission aspects where it is impossible to give overall characteristics, it is in some cases necessary to make recommendations for individual parts of the equipment. + +Annex A considers the effects of the type of acoustic interfaces of the MS. + +# --- 2 Network configurations + +## 2.1 General + +The basic configuration for the interworking with the PSTN is shown in figure 1. + +## 2.2 Model of the PLMN + +A more detailed model of the PLMN used for the consideration of transmission planning issues for speech is shown in figure 2. This model represents the main functions required and does not necessarily imply any particular physical realization. Routeing of calls is given in GSM 03.04. + +Any acoustic echo control is not specifically shown as it will be provided by analogue processing or digital processing or a combination of both techniques. + +## 2.3 Interfaces + +The main interfaces identified within the GSM specifications are shown in figure 1. For the purposes of the present document, the Air Interface and the Point of Interconnect (POI) are identified along with two other interfaces, Interface Z and a 13-bit Uniform PCM Interface (UPCMI). These interfaces are needed to define the PLMN transmission characteristics and the overall system requirements. + +The Air Interface is specified by GSM 05 series specifications and is required to achieve MS transportability. Analogue measurements can be made at this point by using the appropriate radio terminal equipment and speech transcoder. The losses and gains introduced by the test speech transcoder will need to be specified. + +The POI with the PSTN will generally be at the 2 048 kbits/s level at an interface, in accordance with ITU-T Recommendation G.703. At the point, which is considered to have a relative level of 0 dBr, the analogue signals will be represented by 8-bit A-law, according to ITU-T Recommendation G.711. Analogue measurements may be made at this point using a standard send and receive side, as defined in ITU-T Recommendations. + +Interface Z might be used in the case of direct MSC to MSC connections. Interface Z is of the same nature as the POI. + +The UPCMI is introduced for design purposes in order to separate the speech transcoder impairments from the basic audio impairments of the MS. + +## 2.4 Configurations of connections + +### 2.4.1 General configurations of connections + +Figure 3 shows a variety of configurations of connections. There are a number of PSTN features which should be avoided from such connections. These include: + +- 1) echo control devices in the international network. If present, and not disabled, these devices will be in tandem with PLMN echo cancellers and may introduce degradation; +- 2) satellite routeings. The delay inherent in the connections when added to the PLMN delay, may result in conversational difficulties. Double satellite links are likely to cause severe difficulties and special precautions should be taken to avoid this situation under call forwarding arrangements; +- 3) Digital Speech Interpolation systems (DSI). There is likely to be an adverse interaction between DSI and DTX; +- 4) ADPCM. The distortion introduced by ADPCM on routes where PSTN echo control is not provided is likely to reduce the echo cancellation provided by the PLMN electric echo canceller; +- 5) significant differences in clock rates on non-synchronized digital network components. The resulting phase roll and slips are likely to degrade the performance of the PLMN echo canceller; +- 6) those analogue FDM routeings which exhibit phase roll. Any phase roll due to the absence of synchronization between the carrier frequencies on the two directions of transmission is likely to degrade the performance of the PLMN echo canceller; +- 7) tandem connections of sources of quantization distortion. The PLMN speech transcoder is estimated to be equivalent to 7 QDUs between uniform PCM interfaces (see ITU-T Recommendation G.113). + +It is recognized that on some connections it may not be feasible to avoid these features, but in many cases, especially if taken into account at the planning stage, this should be possible. + +### 2.4.2 Reference configurations to illustrate delay and echo control issues + +Three basic reference configuration types shown in figures 4 to 6 are defined to illustrate delay and echo control issues. Intermediate echo control devices as shown in the figures are disabled by appropriate signalling between the MSC and ISC or MSC and MSC. + +Reference configurations A (see figure 4) represent national or international connections where there is no echo control device in the PSTN. These reference configurations include re-routeing configurations where the overall delay of the transmission path has not been extended. + +Reference configurations B (see figure 5) represent national or international connections where echo control is provided in the PSTN. These reference configurations include re-routeing configurations where the overall delay of the transmission path has not been extended. + +Reference configurations C (see figure 6) represent national or international connections where re-routeing has lead to an increase in the overall delay of the transmission path beyond recommended limits. + +## 2.5 4-wire circuits in the PLMN + +As shown in figure 2, the PLMN will usually contain transmission systems. Where present, they should provide 4-wire circuits. + +In the case of digital circuits which do not include any speech processing devices, the overall system requirements of the PLMN will not be affected by the presence of the link. + +In the case of analogue links, the transmission characteristics (e.g. attenuation, attenuation distortion, noise) will affect the overall system requirements of the PLMN. ITU-T Recommendations M.1020, M.1025, M.1030 and M.1040 describe several transmission characteristics for leased circuits. In cases where the analogue link introduces loss, provision will have to be made at the interface to restore the loss. + +# 3 Transmission performance + +The overall transmission performance of connections in alternate conversation mode can be considered as a summation of the effects of: + +- 1) the audio part between the MRP/ERP and the UPCMI interface; +- 2) the speech transcoder part including the effects of radio transmission, and speech processing between the UPCMI and the POI; +- 3) the overall characteristics of the connection between POI and the other user. + +There is not only a linear addition of these effects but there is also an influence from different parts of the connection on the performance of the speech transcoder and other speech processing devices. + +Where possible, the transmission performance is specified between the MRP/ERP and the POI. Where this is not possible, the transmission aspects of the audio part mentioned above have been specified. The transmission aspects of the speech transcoder are specified in GSM 06 series specifications. In the following paragraphs, requirements are specified for the UPCMI, the Air Interface or the POI as appropriate. + +The transmission requirements of the MS have been derived from the requirements of digital telephones stated in I-ETS 300 245-2 and 3. + +MSs will have to work in a variety of environments ranging from quiet office locations to very noisy environments as found in moving cars. In noisy conditions, different values for the sending and receiving sensitivities relative to the nominal values can increase the performance of the terminal. Some guidance is given in annex E. + +The overall transmission performance in full duplex conversation mode will also greatly depend on the performance of the echo control devices which may be included in the connection. + +The handsfree requirements in the present document are designed to provide a basic level of performance and to avoid adverse interactions with other networks. Testing is carried out in one configuration in a vehicle, whilst this gives some confidence that the system can work in a typical environment, the testing is by no means complete. It is assumed that the manufacturer submits the handsfree system with the transducers fitted in reasonable locations within the vehicle (the transducers should not impede the normal operation of the vehicle or its fittings). Unusual installations should be agreed for suitability with the relevant Type Approval Authority before testing. + +In a real vehicle installation, care should be taken to allow for the acoustic properties of that vehicle and the likely acoustic environment. It is important that the best possible coupling between the microphone and the MS user is achieved. Hence the microphone should be directional and mounted as close to the user's mouth as practical. The loudspeakers should be mounted in such a way that the maximum receive signal is directed at the user, rather than dissipated by the various obstacles in that vehicle, such as the seats. + +Proper consideration for the noise environment and the direct coupling between the microphone and loudspeakers is necessary. Excessive noise coupled into the microphone can mask the MS user's send speech and potentially affect the operation of DTX. The vehicle noise environment can potentially mask the received speech, unless sufficient volume is provided. However, direct coupling between the transducers can cause annoying echo to be heard by the far end user. + +Primary factors affecting the coupling between the loudspeaker(s) and microphone(s) include: + +- 1) directionality of the microphone(s); +- 2) directionality of the loudspeaker(s); +- 3) location of the transducers in relation to each other and reflecting surfaces such as the windows and windscreen. + +## 3.1 Overall Loss/Loudness ratings + +The overall international connection involving PLMNs and the PSTN should meet the overall loudness rating (OLR) limits in ITU-T Recommendation G.111. The national parts of the connection should therefore meet the send and receive loudness rating (SLR, RLR) limits in ITU-T Recommendation G.121. + +For the case where digital routeings are used to connect the PLMN to the international chain of circuits, the SLR and RLR of the national extension will be largely determined by the SLR and RLR of the PLMN. The limits given below are consistent with the national extension limits and long term objectives in CCITT Recommendation G.121. + +The SLR and RLR values for the PLMN apply up to the POI. However, the main determining factors are the characteristics of the MS, including the analogue to digital conversion (ADC) and digital to analogue conversion (DAC). Hence, in practice, it will be convenient to specify loudness ratings to the Air Interface. For the normal case, where the PLMN introduces no additional loss between the Air Interface and the POI, the loudness ratings to the PSTN boundary (POI) will be the same as the loudness ratings measured at the Air Interface. However, in some cases loss adjustment may be needed for interworking situations in individual countries. + +These values are directly applicable to the case of an MS operating in a conventional non-mobile noise environment. Studies have shown that under the PLMN noise environment, speech levels are likely to be higher. Hence, in order to avoid clipping in the speech transcoder, the value of SLR may need to be increased. + +NOTE: In [51] 3GPP TS 51.010, measurement of SLR and RLR for handset MS is specified using sinusoidal test frequencies. This may not be the optimum method of measuring the loudness ratings because of the adaptive characteristics of the GSM speech transcoders. However the actual measurement is only performed over the linear portion of the MS. When developing the subsequent test methods for handsfree MS, in annex B and annex C, it was decided to use the artificial voice described in ITU-T Recommendation P.50, to measure send and receive sensitivities. + +### 3.1.1 Connections with handset MSs + +Overall Loss/Loudness ratings shall be as specified in [49], 3GPP TS 26.131. + +For a dual mode GSM/3GPP telephone compliance shall be checked according to the procedures described in [50], 3GPP TS 26.132. + +For a single mode GSM MS conformance shall be checked according to either the procedures described in [51] 3GPP TS 51.010 or the procedures described in [50] 3GPP TS 26.132. + +### 3.1.2 Connections with handsfree MSs + +Overall Loss/Loudness ratings shall be as specified in [49], 3GPP TS 26.131. + +For a dual mode GSM/3GPP telephone as well as a single mode GSM MS compliance shall be checked according to the procedures described in [50], 3GPP TS 26.132. + +### 3.1.3 Connections with headset MSs + +Overall Loss/Loudness ratings shall be as specified in [49], 3GPP TS 26.131. + +For a dual mode GSM/3GPP telephone as well as a single mode GSM MS compliance shall be checked according to the procedures described in [50], 3GPP TS 26.132. + +## 3.2 Stability Loss + +The stability loss presented to the PSTN by the PLMN at the POI shall be as specified for the stability loss presented to the PSTN by the 3GPP network in [49], 3GPP TS 26.131. + +For a dual mode GSM/3GPP telephone as well as a single mode GSM MS compliance shall be checked according to the procedures described in [50], 3GPP TS 26.132. + +## 3.3 Delay + +### 3.3.1 General + +A significant propagation time between the two ends of a connection causes difficulties in conversation over the connection. This arises from two causes. Firstly, the signal is reflected back from the distant end causing an echo to the talker (this is considered in subclause 3.4). Secondly, even if ideal echo control were achieved, the delay between a user talking and receiving a reply from the user at the distant end of the connection could cause conversational difficulty. + +PLMNs will be connected to the PSTN at a point where present planning rules allow for a delay of less than 18 ms (see ITU-T Recommendation G.114 subclause A.2 a). The delay within the PLMN will greatly exceed this. If unacceptable circuit delays are not to be experienced by users, action will have to be taken when planning routes or during call set-up. + +### 3.3.2 Sources of delay + +#### 3.3.2.1 Elements of the PLMN that cause delay + +The delay of the PLMN is made up of the following elements: + +- 1) speech transcoding delay; +- 2) radio channel coding delay; +- 3) PLMN network delay (i.e. fixed elements such as multiplexing, propagation, switching, echo control); +- 4) speech processing for echo cancelling and noise reduction in Handsfree Mode. + +#### 3.3.2.2 Elements of the PSTN that cause delay + +ITU-T recommendation G.114 identifies various elements present in some PSTN connections which cause delay. These include: + +- 1) coaxial, radio and optical fibre terrestrial transmission systems; +- 2) geostationary satellites; +- 3) digital speech interpolators; +- 4) digital exchanges (see also ITU-T recommendation Q.551); +- 5) echo cancellers. + +### 3.3.3 Effects of delay + +Some recent studies have suggested that under ideal conditions, i.e.: + +- 1) effective control of all echoes without clipping by the use of good echo cancellers; +- 2) low background noise leading to an absence of perceptible noise contrast; +- 3) low distortion of transmitted signals; +- 4) ideal loudness ratings. + +Users can tolerate a circuit delay well in excess of 400 ms (currently the maximum delay recommended in ITU-T Recommendation G.114). Other studies indicate that the difficulty caused by circuit delay increases when impairments, such as imperfect echo control caused by echo suppressors, clipping and noise contrast, are present. + +However, the mobile environment is very harsh, with high background noise levels and distortion from the speech transcoder. In particular, the use of acoustic echo suppression could give rise to severe speech clipping and noise contrast. Also the operation of the voice switching used with DTX will give impairments similar to those caused by echo suppression. All subjective tests performed with echo suppressors indicate that, because of the increased effect of clipping with increased delay, the difficulty experienced by users increases rapidly with delay. According to curve 2 of figure A.1 of ITU-T Recommendation G.114, the percentage of users experiencing difficulties with echo suppressors reaches 20 % with a delay of 150 ms rising to 40 % with a delay of 300 ms. ITU-T Recommendation G.114 annex A details the test conditions under which this curve was derived and it concludes that connections with more than 300 ms can only be used by very disciplined users who are aware of the problems involved in such a connection. However, recent work has indicated that delays of up to 500 ms can be used satisfactorily, provided that effective echo cancellation is incorporated in the link. + +### 3.3.4 Allocation of delay to the PLMN + +#### 3.3.4.1 Allocation of delay to the PLMN when using a full rate system + +Taking account of Recommendations on the separate factors described in subclause 3.3.2.1, the maximum both-way in the PLMN between the MRP/ERP and the Point of Interconnection (see figure 1) will be 180 ms. In the case that the transcoder is positioned outside the BTS, the maximum distance between the POI and the furthest border of the cell controlled by the BTS is limited by a one-way propagation delay of 1,5 ms (approximately 300 km). If the transcoder is positioned at the BTS, the limit is 6,5 ms (approximately 1 300 km). These limits may be subject to increase resulting from savings made in the overall network. + +#### 3.3.4.2 Allocation of delay to the PLMN when using a half rate system + +If it is assumed that the speech quality associated with the half rate system is the same as the full rate system (considering both the speech transcoder and the radio sub-system), then in order to achieve the same overall transmission quality, the maximum delay within the PLMN should be maintained at 180 ms. + +### 3.3.5 Delay of various network configurations + +#### 3.3.5.1 National and international connections with no echo control in the PSTN (reference configurations A) + +Reference configurations A (see figure 4) contain no echo control in the PSTN because present planning rules require the use of echo control devices only when the PSTN delay between two fixed PSTN users exceeds 25 ms. This leads to a maximum PSTN delay of 22 ms from the point of interconnection to the PLMN (see subclause 3.4.2). + +#### 3.3.5.2 National and international connections with echo control in the PSTN (reference configurations B) + +Reference configurations B (see figure 5) contain echo control in the PSTN because present planning rules require their use when the PSTN delay between PSTN users exceeds 25 ms. However, action may have to be taken by administrations when planning routes or at call set-up to limit the maximum delay. + +Subclause 3.3.3 describes how the impairments from the harsh mobile environment when coupled with delay can give rise to difficulty. If very good cancellation of both electrical and acoustic echo can be achieved and there are no sources of speech clipping or noise contrast either in the PLMN or the PSTN part of the connection, the circuit delay should be kept below 400 ms. This means that every attempt should be made to avoid mobile to mobile calls via satellite (expected delay > 440 ms). + +If acoustic echo suppression is used or DTX is enabled, or there is any other source of clipping or noise contrast present in the PSTN, the additional distortion introduced makes it desirable to avoid any satellite routeing whenever possible in order to keep the delay below 300 ms. + +#### 3.3.5.3 Connections where re-routeing leads to a significant increase in transmission path length (reference configurations C) + +A number of possible combinations of re-routeing are described by reference configurations C (see figure 6), all of which increase the path length and hence the delay and some of which increase the number of impairments in the network. + +These routeings are likely to cause severe degradation to the quality of the connection and may result in significant difficulty, particularly when the connection contains one or maybe more satellite links. + +These connections should be avoided in network planning and, if this is not possible, then the facilities of Signalling System No. 7 should be used to control the routeing of the call at call set-up to minimize the effects. + +### 3.3.6 Delay related requirements on the MS + +#### 3.3.6.1 Full rate MS + +In accordance with the outline of transmission delays in various GSM system elements contained in GSM 03.05, the round trip delay in the MS shall not exceed 143,9 ms as defined in annex D. + +#### 3.3.6.2 Half rate MS + +The round trip delay in the MS shall not exceed 143,9 ms as defined in annex D. + +#### 3.3.6.3 Handsfree MS + +The round trip delay in the MS, including the handsfree processing stages, shall not exceed 143,9 ms + 39 ms. The 143,9 ms is as defined in annex D, the 39 ms is to allow for additional processing for handsfree. + +The method of measurement is defined in annex C, subclause C.10. + +## 3.4 Echo + +### 3.4.1 General + +There are two main sources of echo: + +- 1) acoustic echo caused by the acoustic path between receive and transmit transducers; +- 2) electrical echo caused by coupling between the transmit and receive directions of transmission. The primary source of this form of echo is a two-to-four wire converter. + +Electrical echo can be eliminated by the use of end-to-end four-wire transmission. Acoustic echo will be generated in all telephone instruments with the exception of carefully designed headsets. + +In general, electrical echo is characterized by a short reverberation time and low dispersion while acoustic echo is likely to have a longer reverberation time and greater dispersion. The case of the acoustic echo may be further complicated by the time variant nature of acoustic echo which may be more severe in the mobile environment. + +Curves showing the tolerance to echo, taking account of the relationship between the delay and the level of the echo, are given in ITU-T Recommendation G.131 figure 1/G.131. In practice, it has been found that for any connection with a delay of greater than 25 ms, some form of echo control will be required to reduce the level of the echo (ITU-T Recommendation G.131 Rule M). + +With the expected maximum one-way delay in the PLMN of 90 ms, acoustic echo control will be required in the MS to reduce the echo returned to the distant end and electrical echo control will be required at the POI to reduce the echo returned to the PLMN user from the PSTN. The design of these echo control devices should be such as to provide operation in full duplex mode (as opposed to alternate mode). + +The echo loss (EL) presented by the PLMN at the POI shall be as specified in the 3GPP Network in [49], 3GPP TS 26.131. + +For a dual mode GSM/3GPP telephone as well as a single mode GSM MS compliance shall be checked according to the procedures described in [50], 3GPP TS 26.132. + +### 3.4.2 Electrical echo control in the PLMN (Reference configurations A) + +The electrical echo control device at the interface with the PSTN should meet the requirements given in ITU-T Recommendation G.168, but with an end delay of 60 ms. This refers to $t_d$ in subclause 1.3.10 of ITU-T + +Recommendation G.168. The 60 ms is calculated as follows. ITU-T Recommendation G.131 states that the maximum length of connection which need not have echo control has a mean one-way propagation time of 25 ms. However, this figure is the sum of the delays of the international connection and the maximum national delays at each end of the connection. Since the interconnection of the PLMN to the PSTN is unlikely to be at a point where the PSTN delay is $> 22$ ms, and the dispersion may be up to 8 ms, the maximum expected end delay which the echo canceller in the MSC should expect is: + +$$(22 + 8) \times 2 = 60 \text{ ms} \quad (\text{see figure 7}).$$ + +Certain countries on the geographical limits of a continent may need to increase this limit as there may be a proportion of connections which do not comply with ITU-T Recommendation G.131 having a mean one-way delay of greater than 25 ms and yet are not provided with echo control. + +### 3.4.3 Acoustic echo control in the PLMN + +Acoustic echo control in the PLMN shall be as specified in the 3GPP Network in [49], 3GPP TS 26.131. + +For a dual mode GSM/3GPP telephone as well as a single mode GSM MS compliance shall be checked according to the procedures described in [50], 3GPP TS 26.132. + +### 3.4.4 Interaction between tandem echo control devices (reference configurations B & C) + +On long international routes or routes containing a satellite path, network echo control devices will be present in accordance with ITU-T Recommendation G.131 Rule M. These devices will be echo suppressors or echo cancellers generally with centre clippers. The tandem connection of such devices can lead to increased clipping and, if echo suppressors are used, additional loss. It is recommended that signalling or routing means be used to avoid the tandem connections of echo control devices whenever possible (see figure 7). + +## 3.5 Clipping + +### 3.5.1 General + +The loss of the start or the end of a speech burst is known as clipping, the main cause of which is voice switching controlled by voice activity detection. Voice switching occurs in devices within the network or within terminal devices. The following devices employ voice switching: + +- 1) echo suppressors. These are generally located at an ISC at either end of a long international connection or connections using satellites; +- 2) echo cancellers with centre clippers. These are located as for the echo suppressors above. In addition, it is recommended that they be used in the MSC at the interface with the PSTN. Clipping in these devices arises from the action of the centre clipper only; +- 3) digital speech interpolators (DSI). These devices are used in circuit multiplication equipment's which are often employed on international connections; +- 4) discontinuous transmission (DTX) devices. These are located in the PLMN; +- 5) loudspeaking telephones. These are used in the PSTN and in the PLMN. It should be noted that regulations in certain countries prohibit the use of handheld MSs by drivers of moving vehicles. + +### 3.5.2 Properties of voice switches in the PLMN + +GSM 06.32 specifies the requirements for the voice activity detector used for DTX and the total clipping allowed in the MS. Any voice switching used for acoustic echo control should not exceed these limits. Information on recommended characteristics of handsfree telephones is given in clause 4 of ITU-T Recommendation P.340. + +### 3.5.3 Problems of tandem voice switching + +The effect of tandem voice switches which are not under one common control will be an increase in clipping. Moreover, under conditions of high or rapidly changing ambient noise, false detection of speech is likely to occur in the voice activity detectors in DSI equipment or network echo control devices. These devices are generally designed for constant and low levels of noise. + +In order to minimize clipping, the following action should be taken: + +- 1) intermediate tandem voice switching devices in the network should be either disabled by signalling means or avoided by routing means; +- 2) the voice switching for the MS for acoustic control and for DTX should be under one common control. + +However, it should be noted that, in many cases, it will not be possible to exclude DSI equipment or loudspeaking telephones from the connection. + +## 3.6 Idle channel noise (handset and headset MS) + +### 3.6.1 Sending + +The maximum noise level produced by the apparatus at the UPCMI under silent conditions in the sending direction shall be as specified in [49] 3GPP TS 26.131. + +For a dual mode GSM/3GPP telephone compliance shall be checked according to the procedures described in [50] , 3GPP TS 26.132. For a single mode GSM MS conformance shall be checked according to the procedures described in [51] 3GPP TS 51.010. + +### 3.6.2 Receiving + +The maximum (acoustic) noise level at the handset and headset MS when no signal (O-level) is received from the speech transcoder shall be as specified in [49] 3GPP TS 26.131. + +For a dual mode GSM/3GPP telephone compliance shall be checked according to the procedures described in [50] , 3GPP TS 26.132. + +For a single mode GSM MS conformance shall be checked according to the procedures described in [51] 3GPP TS 51.010. + +## 3.7 Noise contrast + +### 3.7.1 General + +On any PLMN call there is likely to be continuous background noise which is present regardless of whether the users are talking or not. There may also be one or more voice-operated devices; these effectively break the circuit when there is no speech on it. + +Noise contrast problems are caused by the background noise being interrupted when the circuit is broken so that the user listening on the circuit hears the background noise being continually switched on and off. This is particularly disturbing for a user talking to a PLMN user in a moving vehicle because the background noise being modulated in this way is at a very high level. In this situation, it has been found that speech intelligibility can be impaired. + +The main sources of background noise are: + +- 1) background acoustic noise picked up by the microphone. For a loudspeaking telephone in a moving vehicle the speech/noise ratio can be as low as 0 dB; +- 2) idle channel noise. This includes noise generated in the transmission system (thermal noise and crosstalk) the switching system and in speech transcoders. + +### 3.7.2 Elements of a PLMN which can cause noise contrast impairment + +The following elements can cause noise contrast impairments: + +- 1) the acoustic echo control device in the MS. A moving vehicle presents a very difficult environment for an echo canceller, so an echo suppressor is likely to be used (possibly in conjunction with an echo canceller). Echo suppressors contain voice-operated switches; +- 2) DTX. The transmitter switching will cause a PSTN user talking to a PLMN user to hear modulation of the mobile background noise. It will also cause the PLMN user to hear modulation of the PSTN noise. The PSTN noise will vary from connection to connection and should decrease in the future with increasing network digitalization; +- 3) the electric echo control devices protecting the PLMN user against echo returned from the PSTN. The centre clipper in this echo canceller will cause some noise modulation. + +### 3.7.3 Reduction of noise contrast + +A reduction in noise contrast: + +- 1) reduces conversational difficulty, particularly for long conversations; +- 2) allows a greater tolerance on the matching of the level and spectrum of the comfort noise to the ambient noise. + +NOTE: Preliminary tests in vehicles indicate that, in a constant noise environment with a handsfree MS and a signal-to-noise ratio of approximately 10 dB, a maximum level mismatch of 2 dB can be tolerated. The comfort noise spectrum was a reconstruction of the averaged medium term ambient noise spectrum. + +#### 3.7.3.1 Reduction of noise contrast by limiting the noise received by the microphone + +The characteristics of the ambient noise (spectrum and level) depend on the environment in which the MS is used. As a microphone is characterized by its sensitivity and directivity, only part of this noise will enter the microphone. + +A general principle for reducing noise contrast is to maximize the signal-to-noise ratio at the microphone input. This can be achieved by simultaneously increasing directivity, reducing sensitivity, and placing the microphone close to the mouth of the talker. Consequently, the implementation of the acoustic terminal will significantly affect the dynamic range of the noise contrast. + +##### 3.7.3.1.1 Headset MS + +In the case of a headset and if DTX is disabled, then noise contrast will not be present since acoustic echo control (with centre clipping) is not required. If DTX is enabled, then only a small amount of noise contrast might result since the microphone would be close to the talker's mouth and would follow the movement of the talker's head, thus fulfilling the general principle described above. In the worst case, the headset is likely to give a minimum of 15 dB signal-to-noise ratio (this value is for further study). + +##### 3.7.3.1.2 Handset MS + +In the case of a handset, and if DTX is disabled, then noise contrast will not be present if optimized echo cancelling techniques (without residual echo clipping) are used to control the acoustic echo (providing 46 dB EL). If DTX is enabled or acoustic echo control with centre clipping is used, then only a small amount of noise contrast might result since the microphone would be close to the talker's mouth and would follow the movement of the talker's head, thus fulfilling the general principle described above. In the worst case, the handset is likely to give a minimum of 15 dB signal-to-noise ratio (this value is for further study). + +##### 3.7.3.1.3 Handsfree MS + +In the case of a handsfree telephone and even if DTX is disabled, noise contrast will be introduced unless 46 dB EL can be provided without the use of centre clipping. This is unlikely to be achievable. As the microphone is distant from the talker's mouth, and as the talker may be moving during the conversation, the sensitivity of the microphone has to be high and directivity low. This could result in a worse case signal-to-noise ratio of 0 dB. (This value is for further study.) + +The following is given as interim guidelines. In the case of a vehicle mounted handsfree MS, the characteristics of the microphone should be such as to limit the change in speech level to 5 dB for all positions of the talker while sitting. + +#### 3.7.3.2 Reduction of noise contrast by insertion of comfort noise + +GSM 06.12 specifies comfort noise to be used both for acoustic echo control with centre clipping and DTX. + +### 3.7.4 Consequence of the introduction of high comfort noise levels on other voice-operated devices + +Two problems associated with other voice switching devices (e.g. DSI) may result from the introduction of high levels of comfort noise: + +- 1) the high comfort noise level may be interpreted as a voice signal; +- 2) if the high level of comfort noise is detected as noise, then another source of comfort noise at a different level may be introduced downstream, thus increasing the noise contrast. + +## 3.8 Sensitivity/frequency characteristics + +### 3.8.1 Headset and Handset MSs + +#### 3.8.1.1 Sending + +For a dual mode GSM/3GPP telephone as well as single mode GSM MS sending Sensivity/frequency characteristics shall be as specified in [49] 3GPP TS 26.131. + +For a dual mode GSM/3GPP telephone compliance shall be checked according to the procedures described in [50] , 3GPP TS 26.132. + +For a single mode GSM MS conformance shall be checked according to either the procedures described in [51] 3GPP TS 51.010 or the procedures described in 3GPP TS 26.132. + +#### 3.8.1.2 Receiving + +For a dual mode GSM/3GPP telephone as well as a single mode GSM MS receiving Sensivity/frequency characteristics shall be as specified in [49] 3GPP TS 26.131. + +For a dual mode GSM/3GPP telephone compliance shall be checked according to the procedures described in [50] , 3GPP TS 26.132. + +For a single mode GSM MS conformance shall be checked according to either the procedures described in [51] 3GPP TS 51.010 or the procedures described in 3GPP TS 26.132. + +### 3.8.2 Handsfree MS + +#### 3.8.2.1 Sending + +For a dual mode GSM/3GPP telephone as well as single mode GSM MS sending Sensivity/frequency characteristics shall be as specified in [49] 3GPP TS 26.131. + +For a dual mode GSM/3GPP telephone as well as a single mode GSM MS compliance shall be checked according to the procedures described in [50] , 3GPP TS 26.132. + +#### 3.8.2.2 Receiving + +For a dual mode GSM/3GPP telephone as well as single mode GSM MS receiving Sensivity/frequency characteristics shall be as specified in [49] 3GPP TS 26.131. + +For a dual mode GSM/3GPP telephone compliance shall be checked according to the procedures described in [50] , 3GPP TS 26.132. + +## 3.9 Distortion (handset and headset MS) + +The requirements for sending and receiving distortion shall be as specified in [49] 3GPP TS 26.131. + +For a dual mode GSM/3GPP telephone compliance shall be checked according to the procedures described in [50], 3GPP TS 26.132. + +For a single mode GSM MS conformance to the requirement on receiving distortion shall be checked according to the procedures described in [51] 3GPP TS 51.010. Conformance to the requirement on sending distortion shall be checked according to either the procedure described in [51] 3GPP TS 51.010 or the procedure described in [50] 3GPP TS 26.132. + +### 3.9.1 Gain variation, sending + +The requirement on gain variation, sending is applicable to single mode GSM MS only. + +The gain variation relative to the gain for ARL shall remain within the limits given in table 6. For intermediate levels, the same limits for gain variation apply. + +**Table 6: Variation of gain with input level, sending** + +| Sending level dB relative to ARL | Upper limit (dB) | Lower limit (dB) | +|-----------------------------------------|-------------------------|-------------------------| +| 13 | 0,5 | -0,5 | +| 0 | 0,5 | -0,5 | +| -20 | 0,5 | -0,5 | +| -20 | 0,5 | -2 | +| -30 | 0,5 | -2 | +| -30 | 1 | - | +| -40 | 1 | - | +| -40 | 2 | - | +| -45 | 2 | - | + +Compliance of the gain variation in the sending direction shall be checked by the test described in annex C, subclause C.5.1. + +### 3.9.2 Gain variation, receiving + +The requirement on gain variation, sending is applicable to single mode GSM MS only. + +The gain variation relative to the gain at an input level of -10 dBm0, shall be within the limits given in table 8. For intermediate levels, the same limits for gain variation apply. The requirement is valid for sound pressures up to +10 dBPa. For sound pressures exceeding +10 dBPa at the ERP there is no lower limit requirement. + +**Table 8: Variation of gain with input level, receiving** + +| Receiving level at the digital interface (dBm0) | Upper limit (dB) | Lower limit (dB) | +|--------------------------------------------------------|-------------------------|-------------------------| +| +3 | 0,5 | -0,5 | +| -10 | 0,5 | -0,5 | +| -40 | 0,5 | -0,5 | +| -40 | 1 | -1 | +| -50 | 1 | -1 | +| -50 | 2 | -2 | + +Compliance of the gain variation in the receiving direction shall be checked by the test described in annex C, subclause C.5.2. + +## 3.10 Sidetone (handset and headset MS) + +### 3.10.1 Sidetone loss + +A sidetone requirement is appropriate for MSs using handsets and headsets. There are separate requirements for listener sidetone (LSTR) and talker sidetone (STMR). The listener sidetone performance is considered as the major parameter affecting the user perception of the system. Though talker sidetone is important to give the user some comfort in using the equipment. + +#### 3.10.1.1 LSTR + +There is no explicit requirement on LSTR, since the requirements on ambient noise rejection in combination with the requirement on STMR should suffice to ensure acceptable LSTR. + +#### 3.10.1.2 STMR + +For a dual mode GSM/3GPP telephone as well as for a single mode GSM MS the Side Tone Masking Rate (STMR) shall be as specified in [49] 3GPP TS 26.131. + +Where a user-controlled receiving volume control is provided, the STMR shall meet the requirement given above at the setting where the RLR is equal to the nominal value. + +It is recommended that the STMR is independent of the volume control. + +For a dual mode GSM/3GPP telephone compliance shall be checked according to the procedures described in [50] 3GPP TS 26.132. + +For a single mode GSM MS conformance shall be checked according to the procedures described in [51] 3GPP TS 51.010. + +### 3.10.2 Sidetone distortion + +The requirement on sidetone distortion is applicable to single mode GSM MS only. + +The third harmonic distortion generated by the terminal equipment shall not be greater than 10 %. Compliance shall be checked by the relevant procedures in [51] 3GPP TS 51.010. + +## 3.11 Not used + +## 3.12 Requirements for information tones + +The PLMN should be capable of transmitting information tones generated by the PSTN conforming to I-ETS 300 245-7. + +## 3.13 Crosstalk + +### 3.13.1 Near and far end crosstalk + +The near end or far end crosstalk ratio between two complete PLMN connections should not be less than 65 dB. + +### 3.13.2 Go/return crosstalk + +The crosstalk ratio between the go and return channels of a single PLMN connection should not be less than 55 dB. This is to avoid nullifying the effect of the electrical echo canceller at the MSC. The requirement applies for an acoustic input signal at the MRP with a measurement being made at the UPCMI in the opposite direction of transmission. + +## 3.14 MS Ambient Noise Rejection + +For a dual mode GSM/3GPP telephone as well as for a single mode GSM MS ambient noise rejection ANR shall be as specified for narrowband telephony transmission in [49] TS 26.131. Compliance shall be checked according to the procedures described in [50] 3GPP TS 26.132. + +![Figure 1: Basic Configuration for Interworking with the PSTN. The diagram shows a Mobile Station (MS) connected via an Air interface to a Base Station (BTS). The BTS is part of a Base Station Subsystem (BSS) which also includes a Base Station Controller (BSC). The BTS is connected to the BSC via the A bis interface. The BSC is connected to a Mobile Switching Center (MSC) via the A interface. The MSC contains an Exchange Equipment (EEC) and an Electrical Echo Canceller (EEC). The MSC is connected to the PSTN at a point of interconnection. A legend indicates that 'TS' (Transmission System) is an Optional Transmission System, shown as a box with 'TS' inside.](c42e926097d01653b793c04b49e764b2_img.jpg) + +Figure 1: Basic Configuration for Interworking with the PSTN. The diagram shows a Mobile Station (MS) connected via an Air interface to a Base Station (BTS). The BTS is part of a Base Station Subsystem (BSS) which also includes a Base Station Controller (BSC). The BTS is connected to the BSC via the A bis interface. The BSC is connected to a Mobile Switching Center (MSC) via the A interface. The MSC contains an Exchange Equipment (EEC) and an Electrical Echo Canceller (EEC). The MSC is connected to the PSTN at a point of interconnection. A legend indicates that 'TS' (Transmission System) is an Optional Transmission System, shown as a box with 'TS' inside. + +NOTE 1: For transmission planning purposes. Interfaces A and A bis are not required. + +NOTE 2: The speech transcoder may be at either the BTS or the BSC. + +**Figure 1: Basic Configuration for Interworking with the PSTN** + +![Figure 2: PLMN System Model Used for Consideration of Transmission Planning Issues. The diagram shows three input paths (HEADSET, HANDSET, HANDSFREE) connected to a central processing block. The HEADSET path includes 'analogue processing' (Note 2). The HANDSET and HANDSFREE paths include 'analogue processing' and connect to a '13-bit uniform PCM interface (UPCMI)' (Note 5). The UPCMI connects to a 'Speech transcoder and detector' (Note 1) which also includes 'DTX' (Note 1). This block connects to an 'air interface'. The air interface connects to a '4-wire digital transmission system' (Note 6). This system connects to another 'Speech transcoder and detector' (Note 1) with 'DTX' (Note 1). This block connects to a '4-wire analogue or digital transmission system' (Note 6). This system connects to an 'electric echo control device' (Note 4) at 'Interface Z' (Note 4). The electric echo control device connects to the 'point of interconnection (POI)'. Below the diagram, a horizontal line with arrows at both ends is labeled 'MS' on the left, 'BSS' in the middle, and 'MSC' on the right.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +Figure 2: PLMN System Model Used for Consideration of Transmission Planning Issues. The diagram shows three input paths (HEADSET, HANDSET, HANDSFREE) connected to a central processing block. The HEADSET path includes 'analogue processing' (Note 2). The HANDSET and HANDSFREE paths include 'analogue processing' and connect to a '13-bit uniform PCM interface (UPCMI)' (Note 5). The UPCMI connects to a 'Speech transcoder and detector' (Note 1) which also includes 'DTX' (Note 1). This block connects to an 'air interface'. The air interface connects to a '4-wire digital transmission system' (Note 6). This system connects to another 'Speech transcoder and detector' (Note 1) with 'DTX' (Note 1). This block connects to a '4-wire analogue or digital transmission system' (Note 6). This system connects to an 'electric echo control device' (Note 4) at 'Interface Z' (Note 4). The electric echo control device connects to the 'point of interconnection (POI)'. Below the diagram, a horizontal line with arrows at both ends is labeled 'MS' on the left, 'BSS' in the middle, and 'MSC' on the right. + +NOTE 1: Speech detection is incorporated in the speech transcoder. Speech detection is needed to provide the function of DTX and, if required, acoustic echo control (see note 2). + +NOTE 2: Acoustic echo control may not be provided in the case of the headset. + +NOTE 3: Includes filtering. + +NOTE 4: In the case of direct MSC to MSC connections, the EEC function should not be active. The EEC device should be either disabled or not inserted in the circuit. + +NOTE 5: In single talk and in double talk, when no centre clipper is used, and in double talk only if a centre clipper is used, the level of quantizing noise introduced by the speech transcoding will effect the level of residual acoustic echo when echo cancellation techniques are used for AEC. + +NOTE 6: The transmission system need not be present. + +**Figure 2: PLMN System Model Used for Consideration of Transmission Planning Issues** + +![Diagram of PLMN to PSTN Interconnection Configurations showing two PLMNs (no 1 and no 2) connected to a PSTN via MSCs and EECs, with various interconnections and notes.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +The diagram illustrates the interconnection of two Public Land Mobile Networks (PLMN no 1 and PLMN no 2) to a Public Switched Telephone Network (PSTN). A dashed line represents the international boundary between the two PLMN regions. + +- PLMN no 1:** Contains an MS connected to a BSS, which connects to an MSC. The MSC is paired with an EEC. The EEC connects to a Nat. PSTN. A direct link (labeled Note 1) connects the MSC to an ISC. The ISC connects to the Nat. PSTN and has links to other national PSTNs. The Nat. PSTN is connected to an LE (Local Exchange) represented by a triangle and box. +- PLMN no 2:** Contains two sets of MS/BSS/MSC/EEC configurations. + - The upper configuration's EEC connects to a Nat. PSTN. A direct link (Note 1) connects its MSC to an ISC. This ISC connects to the Nat. PSTN and other national PSTNs. + - The lower configuration's EEC also connects to a Nat. PSTN. + - A direct link (Note 3) connects the MSC of the lower configuration to the MSC of the upper configuration. + - The Nat. PSTN in this section is also connected to an LE. +- Inter-PLMN Connections:** There are vertical links between the MSCs of PLMN no 1 and PLMN no 2, labeled with Note 3 and Note 4. There is also a link between the ISCs across the international boundary. + +Diagram of PLMN to PSTN Interconnection Configurations showing two PLMNs (no 1 and no 2) connected to a PSTN via MSCs and EECs, with various interconnections and notes. + +NOTE 1: A direct link between MSC and ISC may be used in cases where Signalling System No. 7 is not provided in the PSTN or where a link via the PSTN would have excessive delay. + +NOTE 2: An echo canceller should be provided at every POI to cancel any echo returning to the PLMN from the PSTN. This is necessary because the one-way echo path back to the MS greatly exceeds 25 ms (see ITU-T Recommendation G.131). + +NOTE 3: A direct link between MSCs reduces the number of echo control devices that need to be provided and avoids the tandem connection of such devices. These direct links may be expected to have less delay than PSTN connections. + +NOTE 4: This arrangement may be provided. + +**Figure 3: PLMN to PSTN Interconnection Configurations** + +Direct routeing and re-routeing where the overall delay of the transmission path has not been extended and no echo control in the PSTN. + +Normal configurations. + +Call from PSTN to PLMN + +![Diagram of a call from PSTN to PLMN. A PSTN triangle connects to an EEC, which is part of an MSC. The MSC connects to a BSS, which connects to a mobile station (MS) with AEC. A double-headed arrow between the PSTN triangle and the EEC is labeled < 22 ms.](7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg) + +Diagram of a call from PSTN to PLMN. A PSTN triangle connects to an EEC, which is part of an MSC. The MSC connects to a BSS, which connects to a mobile station (MS) with AEC. A double-headed arrow between the PSTN triangle and the EEC is labeled < 22 ms. + +Call from PLMN to PSTN + +![Diagram of a call from PLMN to PSTN. A mobile station (MS) with AEC connects to a BSS, which connects to an MSC. The MSC connects to an EEC, which connects to a PSTN triangle. A double-headed arrow between the EEC and the PSTN triangle is labeled < 22 ms.](5132b3a97ac70fe4765c1e07e66b72b3_img.jpg) + +Diagram of a call from PLMN to PSTN. A mobile station (MS) with AEC connects to a BSS, which connects to an MSC. The MSC connects to an EEC, which connects to a PSTN triangle. A double-headed arrow between the EEC and the PSTN triangle is labeled < 22 ms. + +Call from PLMN to PLMN + +![Diagram of a call from PLMN to PLMN. A mobile station (MS) with AEC connects to a BSS, which connects to an MSC. The MSC connects to an EEC, which is crossed out with an 'X'. The signal then goes through a PSTN section to another EEC, which is also crossed out with an 'X', and then to another MSC. This MSC connects to a BSS, which connects to another mobile station (MS) with AEC.](9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg) + +Diagram of a call from PLMN to PLMN. A mobile station (MS) with AEC connects to a BSS, which connects to an MSC. The MSC connects to an EEC, which is crossed out with an 'X'. The signal then goes through a PSTN section to another EEC, which is also crossed out with an 'X', and then to another MSC. This MSC connects to a BSS, which connects to another mobile station (MS) with AEC. + +Call from PSTN to PLMN with re-route at MSC and via PSTN + +![Diagram of a call from PSTN to PLMN with re-route. A PSTN triangle connects to an EEC, which is part of an MSC. The MSC connects to an EEC, which is crossed out with an 'X'. The signal is then re-routed through a PSTN section to another EEC, which is also crossed out with an 'X', and then to another MSC. This MSC connects to a BSS, which connects to a mobile station (MS) with AEC. A double-headed arrow between the PSTN triangle and the first EEC is labeled < 22 ms.](a3953dce8dbd7ef15d61a314dbef2cf9_img.jpg) + +Diagram of a call from PSTN to PLMN with re-route. A PSTN triangle connects to an EEC, which is part of an MSC. The MSC connects to an EEC, which is crossed out with an 'X'. The signal is then re-routed through a PSTN section to another EEC, which is also crossed out with an 'X', and then to another MSC. This MSC connects to a BSS, which connects to a mobile station (MS) with AEC. A double-headed arrow between the PSTN triangle and the first EEC is labeled < 22 ms. + +Direction of signalling is left to right + +![Symbol for echo control disabled: a crossed-out arrow.](42984972f322f3db6c384a0b630d1947_img.jpg) + +Symbol for echo control disabled: a crossed-out arrow. + +echo control disabled + +![Symbol for direction of arrow indicates the echo loop: a solid arrow pointing right.](d63dcf9b188f03572093f2f604d7b8ed_img.jpg) + +Symbol for direction of arrow indicates the echo loop: a solid arrow pointing right. + +direction of arrow indicates the echo loop + +Other configurations may exist if a call from PLMN to PLMN is re-routed at an MSC via the PSTN + +Figure 4: (continued) Reference Configurations A + +Where direct MSC-MSC connections exist, these configurations may apply. + +Call from PSTN to PLMN with re-route via PLMN + +![Diagram showing a call from PSTN to PLMN with re-route via PLMN. The path starts at a PSTN switch, goes through an EEC and MSC, then another MSC, then a BSS, and finally to an MS with AEC. A double-headed arrow labeled < 22 ms is shown between the PSTN switch and the first MSC. A single-headed arrow points from the second MSC back towards the first MSC, indicating the echo loop direction.](e354b57563dae469c00b412b2abdf765_img.jpg) + +Diagram showing a call from PSTN to PLMN with re-route via PLMN. The path starts at a PSTN switch, goes through an EEC and MSC, then another MSC, then a BSS, and finally to an MS with AEC. A double-headed arrow labeled < 22 ms is shown between the PSTN switch and the first MSC. A single-headed arrow points from the second MSC back towards the first MSC, indicating the echo loop direction. + +Call from PLMN to PSTN with long routing in PLMN + +![Diagram showing a call from PLMN to PSTN with long routing in PLMN. The path starts at an MS with AEC, goes through a BSS, then an MSC, then another MSC and EEC, then enters the PSTN to a PSTN switch. A double-headed arrow labeled < 22 ms is shown between the PSTN switch and the EEC. A single-headed arrow points from the EEC back towards the first MSC, indicating the echo loop direction.](2734e7f9be3e1dc046f14be2e6c9a085_img.jpg) + +Diagram showing a call from PLMN to PSTN with long routing in PLMN. The path starts at an MS with AEC, goes through a BSS, then an MSC, then another MSC and EEC, then enters the PSTN to a PSTN switch. A double-headed arrow labeled < 22 ms is shown between the PSTN switch and the EEC. A single-headed arrow points from the EEC back towards the first MSC, indicating the echo loop direction. + +Call from PLMN to PLMN not involving PSTN + +![Diagram showing a call from PLMN to PLMN not involving PSTN. The path starts at an MS with AEC, goes through a BSS, then an MSC, then another MSC, then another BSS, and finally to another MS with AEC.](e7c6a6e4c3047dac05a3b92e396e9794_img.jpg) + +Diagram showing a call from PLMN to PLMN not involving PSTN. The path starts at an MS with AEC, goes through a BSS, then an MSC, then another MSC, then another BSS, and finally to another MS with AEC. + +Direction of signalling is left to right + +→ direction of arrow indicates the echo loop + +Figure 4: (concluded) + +Direct routing and re-routings where the overall delay of the transmission path has not been extended and with echo control in the PSTN. + +Normal configurations. + +Call from PSTN to PLMN + +![Diagram of a call from PSTN to PLMN showing signal flow and echo loop.](e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg) + +This diagram illustrates a call from the PSTN to a PLMN. On the left, a PSTN switch connects to an interface consisting of an ISC and an EEC. An arrow points from the EEC back to the ISC, indicating the echo loop. This interface connects to another interface with an EEC and an ISC, where an arrow points from the ISC to the EEC. A vertical line separates the PSTN side from the PLMN side. On the PLMN side, the signal flows from the second ISC through an EEC and an MSC, then through a BSS to a mobile station (MS) equipped with an AEC. A long double-headed arrow at the bottom, spanning from the first PSTN switch to the MS, is labeled '< 400 ms' and '(1)'. + +Diagram of a call from PSTN to PLMN showing signal flow and echo loop. + +Call from PLMN to PSTN + +![Diagram of a call from PLMN to PSTN showing signal flow and echo loop.](20136850feb70fd71c7d41cdae203ebb_img.jpg) + +This diagram illustrates a call from a PLMN to the PSTN. It starts with a mobile station (MS) with an AEC connected to a BSS, which is connected to an MSC. The MSC connects to an interface with an EEC and an ISC, where an arrow points from the ISC to the EEC. A vertical line separates the PLMN side from the PSTN side. On the PSTN side, the signal flows from the first ISC through an EEC and an ISC, where an arrow points from the EEC back to the ISC. This second interface then connects to a PSTN switch. A long double-headed arrow at the bottom, spanning from the MS to the PSTN switch, is labeled '(1)' and '< 400 ms'. + +Diagram of a call from PLMN to PSTN showing signal flow and echo loop. + +Call from PLMN to PLMN + +![Diagram of a call from PLMN to PLMN showing signal flow and echo loop.](bb3354f497635d15bef873577125c48d_img.jpg) + +This diagram illustrates a call between two PLMNs. It begins with an MS with an AEC connected to a BSS, which connects to an MSC. The MSC connects to an interface with an EEC and an ISC, where an arrow points from the ISC to the EEC. A vertical line separates this PLMN from the PSTN. On the PSTN side, the signal flows from the first ISC through an EEC and an ISC, where an arrow points from the EEC back to the ISC. Another vertical line separates the PSTN from the second PLMN. On the second PLMN side, the signal flows from the second ISC through an EEC and an MSC, then through a BSS to another MS with an AEC. A long double-headed arrow at the bottom, spanning from the first MS to the second MS, is labeled '(1)' and '< 400 ms'. + +Diagram of a call from PLMN to PLMN showing signal flow and echo loop. + +(1) see subclause 3.3.5.2 + +Direction of signalling is left to right + +![Symbol for echo control disabled: a box with an X inside.](9681f7b385905132ecfb6a8aa66d1f58_img.jpg) + +Symbol for echo control disabled: a box with an X inside. + +echo control disabled + +![Symbol for echo loop direction: an arrow pointing right.](fb29be0f9d67f05cd4c69fd091e93ebb_img.jpg) + +Symbol for echo loop direction: an arrow pointing right. + +direction of arrow indicates the echo loop + +Other configurations may exist if a call from PLMN to PLMN is re-routed at an MSC via the PSTN + +**Figure 5: (continued) Reference Configurations B** + +Where direct MSC – MSC connections exist, these configurations may apply. + +Call from PSTN to PLMN with re-route via PLMN + +![Diagram of a call from PSTN to PLMN with re-route via PLMN. The diagram shows a signal path from a PSTN triangle through an ISC/EEC pair, then a crossed-out EEC/ISC pair, then a crossed-out EEC/MSC pair, then an MSC, then a BSS, and finally to an MS/AEC triangle. A long double-headed arrow at the bottom is labeled '< 400 ms' and '(1)'.](e90987faabad6a6665cd8ed1151dc474_img.jpg) + +The diagram illustrates a call path from the PSTN to the PLMN. It starts with a PSTN triangle on the left, followed by an ISC/EEC pair. A signal arrow points left from the EEC. This is followed by a crossed-out EEC/ISC pair. A signal arrow points right from the ISC. This is followed by a crossed-out EEC/MSC pair. A signal arrow points left from the MSC. This is followed by an MSC, then a BSS, and finally an MS/AEC triangle on the right. A long double-headed arrow at the bottom spans the entire path and is labeled '< 400 ms' and '(1)'. + +Diagram of a call from PSTN to PLMN with re-route via PLMN. The diagram shows a signal path from a PSTN triangle through an ISC/EEC pair, then a crossed-out EEC/ISC pair, then a crossed-out EEC/MSC pair, then an MSC, then a BSS, and finally to an MS/AEC triangle. A long double-headed arrow at the bottom is labeled '< 400 ms' and '(1)'. + +Call from PLMN to PSTN with long routing in PLMN + +![Diagram of a call from PLMN to PSTN with long routing in PLMN. The diagram shows a signal path from an MS/AEC triangle through a BSS, then an MSC, then a crossed-out MSC/EEC pair, then a crossed-out ISC/EEC pair, then an EEC/ISC pair, and finally to a PSTN triangle. A long double-headed arrow at the bottom is labeled '(1)' and '< 400 ms'.](088921fa3f5a44c8551815122517eefd_img.jpg) + +The diagram illustrates a call path from the PLMN to the PSTN. It starts with an MS/AEC triangle on the left, followed by a BSS, then an MSC. A signal arrow points right from the MSC. This is followed by a crossed-out MSC/EEC pair. A signal arrow points right from the EEC. This is followed by a crossed-out ISC/EEC pair. A signal arrow points left from the ISC. This is followed by an EEC/ISC pair. A signal arrow points right from the ISC. This is followed by a PSTN triangle on the right. A long double-headed arrow at the bottom spans the entire path and is labeled '(1)' and '< 400 ms'. + +Diagram of a call from PLMN to PSTN with long routing in PLMN. The diagram shows a signal path from an MS/AEC triangle through a BSS, then an MSC, then a crossed-out MSC/EEC pair, then a crossed-out ISC/EEC pair, then an EEC/ISC pair, and finally to a PSTN triangle. A long double-headed arrow at the bottom is labeled '(1)' and '< 400 ms'. + +(1) see subclause 3.3.5.2 + +Direction of signalling is left to right + +- Image: crossed out X + + echo control disabled +- Image: arrow pointing right + + direction of arrow indicates the echo loop + +Figure 5: (concluded) + +Re-routings where the overall delay of the transmission path has been extended beyond transmission planning limits. + +![Figure 6: Reference Configuration C. Five network diagrams showing call paths between PSTN and PLMN with various re-routings and echo control configurations. Each diagram shows components like MSC, BSS, and MS/AEC, with arrows indicating signalling and echo loops. Delay thresholds like > 22 ms and > 400 ms are indicated.](eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg) + +Call from PSTN to PLMN with re-route in PSTN + +Call from PSTN to PLMN with re-route at MSC and via PSTN + +Call from PSTN to PLMN with re-route at MSC and via PSTN + +Call from PSTN to PLMN with re-route at MSC and via PSTN + +Call from PLMN to PLMN + +Figure 6: Reference Configuration C. Five network diagrams showing call paths between PSTN and PLMN with various re-routings and echo control configurations. Each diagram shows components like MSC, BSS, and MS/AEC, with arrows indicating signalling and echo loops. Delay thresholds like > 22 ms and > 400 ms are indicated. + +(1) see subclause 3.3.5.2 + +Direction of signalling is left to right + +![Symbol for echo control disabled: a box with an 'X' inside.](e3c1d325b828c44049a7ac37e5b34603_img.jpg) + +Symbol for echo control disabled: a box with an 'X' inside. + +echo control disabled + +![Symbol for direction of echo loop: a right-pointing arrow.](9d4bac4111fe96f0d6f746b95343cbd8_img.jpg) + +Symbol for direction of echo loop: a right-pointing arrow. + +direction of arrow indicates the echo loop + +Other configurations may exist if a call from PLMN to PLMN is re-routed at an MSC via the PSTN + +Figure 6: Reference Configuration C + +No echo control in PSTN. + +![Diagrams showing end delay requirements for 'No echo control in PSTN' for both PSTN to PSTN and PLMN to PSTN connections.](474a819357587e34949a3e110ff19b30_img.jpg) + +**PSTN to PSTN connection** + +The diagram shows a PSTN Country 1 connected via an ISC to an international link, which is then connected via another ISC to PSTN C2. A double-headed arrow indicates a delay of $< 25 \text{ ms}$ . + +**PLMN to PSTN connection** + +The diagram shows a PLMN (containing MS/AEC and BSS) connected to an MSC/EEC, which is then connected via an ISC to PSTN C1, and another ISC to PSTN C2. A double-headed arrow indicates a delay of $< 22 \text{ ms}$ . A note at the bottom right specifies $\text{end delay } t_d < 60 \text{ ms}$ . + +Diagrams showing end delay requirements for 'No echo control in PSTN' for both PSTN to PSTN and PLMN to PSTN connections. + +Echo control in PSTN. + +![Diagrams showing end delay requirements for 'Echo control in PSTN' for both PSTN to PSTN and PLMN to PSTN connections, including a legend for echo control status.](f0a97d0d3818a253c1d2a009966081b1_img.jpg) + +**PSTN to PSTN connection** + +The diagram shows a PSTN C1 connected via an ISC/EEC to an international link, which is then connected via an EEC/ISC to PSTN C2. A double-headed arrow indicates a delay of $> 25 \text{ ms}$ . + +**PLMN to PSTN connection** + +The diagram shows a PLMN (containing MS/AEC and BSS) connected to an MSC/EEC, which is then connected via an ISC/EEC to PSTN C1, and an EEC/ISC to PSTN C2. A double-headed arrow indicates a delay of $> 22 \text{ ms}$ . A note at the bottom right specifies $\text{end delay } t_d > 60 \text{ ms}$ . + +**Legend:** + +- ~~ISC~~ echo control disabled +- direction of arrow indicates the echo loop + +Diagrams showing end delay requirements for 'Echo control in PSTN' for both PSTN to PSTN and PLMN to PSTN connections, including a legend for echo control status. + +Figure 7: End Delay Requirements for PLMN EEC + +# --- Annex A (informative): Considerations on the Acoustic Interface of the Mobile Station + +## A.1 Handsfree MS + +The handsfree MS will almost certainly require the use of non-linear processing for the acoustic echo control, the extraction of the speech from high levels of ambient noise. The implementation of these functions may well cause degradation to the overall transmission quality and cause difficulty to the distant end user especially during duplex conversation. + +## --- A.2 Handset MS + +The handset MS, depending on the detailed implementation, might not require the use of non-linear processing for the acoustic echo control. Also, the position of the microphone should give a significantly improved signal-to-noise ratio, compared with a handsfree MS especially in noisy environments. This is likely to result in significantly improved transmission quality compared with the handsfree MS and easier duplex conversation. + +## --- A.3 Headset MS + +The headset MS is likely to be the simplest, since with careful design, it might not require acoustic echo control. As with the handset case, the signal-to-noise ratio should be significantly improved compared with the handsfree MS especially in noisy environments. Consequently, the headset MS is likely to give the best transmission quality and easiest duplex conversation. + +## --- A.4 Inter-reaction with DTX + +Because of the improved signal-to-noise ratio, both the headset MS and the handset MS are likely to give better transmission quality when DTX is enabled than that of handsfree MS. + +# --- Annex B (normative): Test considerations + +Test setups for terminal acoustics shall be as specified in [50] 3GPP TS 26.132. + +When DAI is used for testing of single mode GSM MS, the measurement signals shall be as specified in the relevant test-cases in [51] 3GPP TS 51.010. + +# --- Annex C (normative): Transmission requirements testing + +Unless otherwise stated, testing shall be performed according to [50] 3GPP TS 26.132. + +--- + +## C.1 Not used C.2 Not used C.3 Not used C.4 Not used C.5 Variation of gain with input level + +### C.5.1 Sending + +The handset is mounted at LRGP and the earpiece is sealed to the knife-edge of the artificial ear. + +A sine-wave signal with a frequency in the range 1 004 Hz to 1 025 Hz is applied at the MRP. The level of this signal is adjusted until the output of the terminal is $-10$ dBm0. The level of the signal at the MRP is then the ARL. + +The test signal shall be applied at the following levels: $-45, -40, -35, -30, -25, -20, -15, -10, -5, 0, 5, 10, 13$ dB relative to ARL. + +The variation of gain relative to the gain for ARL is measured. + +NOTE: Selective measurement may be used to avoid the effects of ambient noise. + +### C.5.2 Receiving + +The handset is mounted at LRGP and the earpiece is sealed to the knife-edge of the artificial ear. + +A digitally simulated sine-wave signal with a frequency in the range 1 004 Hz to 1 025 Hz shall be applied at the digital interface at the following levels: $-50, -45, -40, -35, -30, -25, -20, -15, -10, -5, 0, 3$ dBm0. + +The variation of gain relative to the gain at an input level of $-10$ dBm0 shall be measured at the ERP. + +NOTE: Selective measurement may be used to avoid the effects of ambient noise. + +## --- C.6 Not used + +## C.7 Not used + +## C.8 Not used + +## C.9 Not used + +## C.10 Delay for handsfree MS + +### C.10.1 Uplink + +#### Configuration + +The handsfree microphone is mounted physically close to the loudspeaker producing the test signal. The RF of the MS is connected to the System Simulator. + +NOTE 1: For handsfree equipment fitted with multiple microphones, there must be sufficient sensitivity for one of the microphones for this test to be performed. + +#### Procedure + +The SS sets up a handsfree speech call to the MS. The SS sends a known speech like test signal (delytest.pcm) to the loudspeaker of the test system and monitors the received RF bursts. + +The SS performs a correlation of the stimulus file with the received, decoded information and calculates the delay. + +NOTE 2: The timing of the stimulus signal has to be related to the frame timing and the timing of the received signal has to be related to the frame in which it is received to be able to calculate the delay in the MS. + +### C.10.2 Downlink + +#### Configuration + +The handsfree loudspeaker is mounted physically close to the measuring microphone of the SS. The RF of the MS is connected to the System Simulator. + +#### Procedure + +The SS sets up a handsfree speech call to the MS. The SS sends a known speech like test signal (delytest.cod which is the speech coder processed version of delytest.pcm) to the MS and monitors the audio received at the loudspeaker. + +The SS performs a correlation of the stimulus file with the received audio and calculates the delay. + +NOTE: The timing of the received audio signal has to be related to the frame timing and the timing of the transmitted speech test signal has to be related to the frame in which it is sent to be able to calculate the delay in the MS. + +### C.10.3 Result + +The round trip delay attributable to the MS is the sum of the delay values measured in C.10.1 and C.10.2 less the calibrated delay in the test system. + +As the timing of all signals is related to air interface frame timing, the delay in the test system will only be due to operations between the timing system and the acoustic interface. This can be calibrated by running a correlation test, similar to the above, but sending the pcm file to the SS loudspeaker and measuring with the SS microphone. The delay measured by this correlation will be the sum of all the SS delays. Care should be taken in the SS to ensure that this delay is not subject to unnecessary variation. + +# Annex D (normative): MS delay requirement definition + +## D.1 Full rate MS delay requirement definition + +The symbol definitions for the calculations in this clause are: + +| | | +|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Trftx: | The time required for transmission of a TCH radio interface frame over the air interface due to the interleaving and de-interleaving (system dependent). | +| Ttransc: | The speech encoder processing time, from input of the last PCM sample to output of the final encoded bit (implementation dependent). | +| Tsample: | The duration of the segment of PCM speech operated on by the speech transcoder. | +| Tencode: | The time required for the channel encoder to perform channel encoding (implementation dependent). | +| Trxproc: | The time required after reception over the air interface to perform equalization, channel decoding and SID frame detection (implementation dependent). | +| Tproc: | The time required after reception of the first RPE-sample to process the speech encoded data for the full rate speech decoder and to produce the first PCM output sample (implementation dependent). | +| Ta/d: | Delay in the analogue to digital converter in the downlink. | +| Tmargin: | An allowance for system entities that are implementation dependent. | +| Td/a: | Delay in the digital to analogue converter in the uplink. | +| Tpcm: | The duration of a segment of PCM speech for the downlink processing delay. | + +The full rate MS speech delay in the uplink direction is the delay between an acoustic event at the MRP to the last bit of the corresponding speech frame at the antenna connector and shall not exceed: + +$$\begin{aligned} + \text{MS uplink delay} &= \text{Ta/d} + \text{Tmargin} + \text{Tsample} + \text{Ttransc} + \text{Tencode} + \text{Trftx} \\ + &= 2,0 + 3,0 + 20,0 + 8,0 + 1,6 + 37,5 \text{ ms} \\ + &= 72,1 \text{ ms} + \end{aligned}$$ + +The full rate MS speech delay in the downlink direction is the delay between the first bit of a speech frame at the antenna connector and the last acoustic event at the ERP corresponding to that speech frame and shall not exceed: + +$$\begin{aligned} + \text{MS downlink delay} &= \text{Tpcm} + \text{Trftx} + \text{Trxproc} + \text{T proc} + \text{Tmargin} + \text{Td/a} \\ + &= 20,0 + 37,5 + 8,8 + 1,5 + 3,0 + 1,0 \text{ ms} \\ + &= 71,8 \text{ ms} + \end{aligned}$$ + +The round trip delay shall therefore not exceed: + +$$72,1 \text{ ms} + 71,8 \text{ ms} = 143,9 \text{ ms}.$$ + +## D.2 Half rate MS delay requirement definition + +The symbol definitions for the calculations in this clause are: + +| | | +|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Trftx: | The time required for transmission of a TCH radio interface frame over the air interface due to the interleaving and de-interleaving (system dependent). | +| Ttransc: | The speech encoder processing time, from input of the last PCM sample to output of the final encoded bit (implementation dependent). | +| Tsample: | The duration of the segment of PCM speech operated on by the speech transcoder. | +| Tencode: | The time required for the channel encoder to perform channel encoding (implementation dependent). | +| Trxproc: | The time required after reception over the air interface to perform equalization, channel decoding and SID frame detection (implementation dependent). | +| Tproc: | The time required after reception of the first gain vector (GSPO) to process the speech encoded data for the half rate speech decoder and to produce the first PCM output sample (implementation dependent). | +| Ta/d: | Delay in the analogue to digital converter in the downlink. | +| Tmargin: | An allowance for system entities that are implementation dependent. | +| Td/a: | Delay in the digital to analogue converter in the uplink. | +| Tpcm: | The duration of a segment of PCM speech for the downlink processing delay. | + +The half rate MS speech delay in the uplink direction is the delay between an acoustic event at the MRP to the last bit of the corresponding speech frame at the antenna connector and shall not exceed: + +$$\begin{aligned} + \text{MS uplink delay} &= \text{Ta/d} + \text{Tmargin} + \text{Tsample} + \text{Ttransc} + \text{Tencode} + \text{Trftx} \\ + &= 1,0 + 1,9 + 24,4 + 12,1 + 1,2 + 32,9 \text{ ms} \\ + &= 73,5 \text{ ms} + \end{aligned}$$ + +The half rate MS speech delay in the downlink direction is the delay between the first bit of a speech frame at the antenna connector and the last acoustic event at the ERP corresponding to that speech frame and shall not exceed: + +$$\begin{aligned} + \text{MS downlink delay} &= \text{Tpcm} + \text{Trftx} + \text{Trxproc} + \text{T proc} + \text{Tmargin} + \text{Td/a} \\ + &= 24,4 + 32,9 + 8,8 + 1,9 + 1,9 + 0,5 \text{ ms} \\ + &= 70,4 \text{ ms} + \end{aligned}$$ + +The round trip delay shall therefore not exceed: + +143,9 ms (see subclause 3.3.6.2). + +# Annex E (informative): Adaptive gain control + +In noisy surroundings the speaker automatically raises his voice to compensate for the noise. The sending sensitivity can therefore be reduced, giving the same voice output to the line as under quiet conditions and at the same time reducing the output line noise level. + +On the other hand the receiving sensitivity has to be increased under noisy conditions to give a better perceived sound quality. + +The Sending and receiving sensitivities may be modified automatically by implementing an Adaptive gain control. The gain variation in the set corresponds to a gain in the receiving path and to a symmetrical attenuation in the sending path for increased ambient noise level. + +The following table presents, for guidance and illustration only, three examples of gain variation characteristics. + +**Table E.1: Gain variation characteristics** + +| | Ambient noise level | Relative Gain variation | +|-----------------------------|-----------------------------|-------------------------| +| Single threshold | between -44 and -39 dBPa(A) | 8 dB | +| Double threshold | -44 dBPa(A) | 5 dB | +| | -34 dBPa(A) | 10 dB | +| Continuous variation | from -64 to -44 dBPa(A) | 3 dB | +| | from -44 to -24 dBPa(A) | 8 dB | + +# Annex F (informative): Change History + +| SMG# | SPEC | CR | PHASE | VERS | NEW_VERS | SUBJECT | +|------|-------|------|-------|-------|----------|-----------------------------------------------------------------------------| +| S17 | 03.50 | A005 | 2+ | | 5.0.0 | New specification for handsfree performance | +| S17 | 03.50 | A006 | 2+ | | 5.0.0 | Noise reduction Specification for the GSM MS. | +| S17 | 03.50 | A007 | 2+ | | 5.0.0 | Inclusion of the possibility to use a type 3.2 leaky ear for handset tests. | +| S17 | 03.50 | A008 | 2+ | | 5.0.0 | Update of references | +| s24 | 03.50 | A011 | R96 | 5.0.2 | 5.0.3 | CR to 03.50 Correction of wrong reference to ITU-T Recommendation | +| s25 | 03.50 | A013 | R96 | 5.0.3 | 5.1.0 | Removal of inconsistency in RLR for Handset and Headset MS | +| s27 | 03.50 | A014 | R96 | 5.1.0 | 5.2.0 | Correction of reference in Section 1.1 | +| s27 | 03.50 | | | | 6.0.0 | Release 1997 version | +| s28 | 03.50 | A018 | R97 | 6.0.0 | 6.1.0 | Acoustic testing of MS over the air interface | +| s29 | 03.50 | | | | 7.0.0 | Upgrade to Release 1998 version 7.0.0 | +| | 03.50 | | | 7.0.0 | 7.0.1 | Update to version 7.0.1 for Publication | +| s31 | 03.50 | | | 7.0.1 | 8.0.0 | Release 1999 version 8.0.0 | +| s32 | 03.50 | A022 | R99 | 8.0.0 | 8.1.0 | Addition of a new optional artificial ear Type for acoustic tests | + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-----|-------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 03-2001 | 11 | SP-010099 | A029 | 2 | Harmonisation of requirements on terminal acoustics in GSM and 3G | 8.1.1 | 4.0.0 | +| 03-2001 | 11 | SP-010099 | A030 | 2 | Harmonisation of requirements on terminal acoustics in GSM and 3G | 4.0.0 | 5.0.0 | +| 12-2004 | 26 | | | | Version for Release 6 | 5.0.0 | 6.0.0 | +| 06-2007 | 36 | | | | Version for Release 7 | 6.0.0 | 7.0.0 | +| 03-2008 | 39 | SP-080011 | 0001 | 1 | Correction of wrong references | 7.0.0 | 7.1.0 | +| 12-2008 | 42 | | | | Version for Release 8 | 7.1.0 | 8.0.0 | +| 12-2009 | 46 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | +| 03-2011 | 51 | | | | Version for Release 10 | 9.0.0 | 10.0.0 | +| 09-2012 | 57 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | \ No newline at end of file diff --git a/marked/Rel-11/43_series/43052/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-11/43_series/43052/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c346ae42683123a43b7655ff66f6f90e5a0fcda4 --- /dev/null +++ b/marked/Rel-11/43_series/43052/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b5509ba534c74ce1e9888a14374e71fdbd8cc903f6f02f2e7c48a38f0e77d56 +size 39343 diff --git a/marked/Rel-11/43_series/43052/a7c51c18111139f9aca2805114108565_img.jpg b/marked/Rel-11/43_series/43052/a7c51c18111139f9aca2805114108565_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b081e55bedc0c0cbaa48351f91049526c298464 --- /dev/null +++ b/marked/Rel-11/43_series/43052/a7c51c18111139f9aca2805114108565_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8e57788e173ca002798f4f65af6a17d31585ac60bc9f73930ee4d0f097f1e26 +size 30871 diff --git a/marked/Rel-11/43_series/43052/bffdddb47fced140f8d17fdc2a29f592_img.jpg b/marked/Rel-11/43_series/43052/bffdddb47fced140f8d17fdc2a29f592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92dc207243696810539d8be505486b17b8a82b20 --- /dev/null +++ b/marked/Rel-11/43_series/43052/bffdddb47fced140f8d17fdc2a29f592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1fd787a85ddf2c03b90f39f920a8a563a9a6e5f1da761780b826526ffe76fe36 +size 21097 diff --git a/marked/Rel-11/43_series/43052/raw.md b/marked/Rel-11/43_series/43052/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b582b25d2bc18ca528476e20107fb10f01f791e2 --- /dev/null +++ b/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 | +| Annex A (informative): | GSM backwards compatibility issues..... | 23 | +| 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 3rd 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
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 | \ No newline at end of file diff --git a/marked/Rel-11/43_series/43055/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-11/43_series/43055/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..943e39a26a0de0740f993fc36562d5094dd327e1 --- /dev/null +++ b/marked/Rel-11/43_series/43055/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:290c32e506d2b64edbe9c7cad9accf2af3ff3e4cd1726592693c102617aa3bd4 +size 81790 diff --git a/marked/Rel-11/43_series/43055/124c6108c63173818afb8ed49521e22d_img.jpg b/marked/Rel-11/43_series/43055/124c6108c63173818afb8ed49521e22d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1df87cf35119609db5c648fb31c5ff06bc07bab5 --- /dev/null +++ b/marked/Rel-11/43_series/43055/124c6108c63173818afb8ed49521e22d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43a79bf3b306361d2192e1c0d8080e4271068dccdb6f86c0606feb92a5c86cf7 +size 33383 diff --git a/marked/Rel-11/43_series/43055/1d27fed9c01eb99f6535283f35fe3bbf_img.jpg b/marked/Rel-11/43_series/43055/1d27fed9c01eb99f6535283f35fe3bbf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed60abed3def01aab46fcf6a87a968032d37321e --- /dev/null +++ b/marked/Rel-11/43_series/43055/1d27fed9c01eb99f6535283f35fe3bbf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f3551fd6b586789e0b7150d2bba505662b5ca5943cfaaac9e8ec75239520cf3 +size 36973 diff --git a/marked/Rel-11/43_series/43055/21ad58fee90f2be50708ff541d225507_img.jpg b/marked/Rel-11/43_series/43055/21ad58fee90f2be50708ff541d225507_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e3b531ff3b37bda32287bc54a101c171e332045e --- /dev/null +++ b/marked/Rel-11/43_series/43055/21ad58fee90f2be50708ff541d225507_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:303524aa6c1429891baaf6ddb27f9e5bb77c6a8228aa1c9bb7dbdc186d187b6e +size 25212 diff --git a/marked/Rel-11/43_series/43055/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-11/43_series/43055/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e2b95360e711c8fec4c98999f466cee1cf3b8d7 --- /dev/null +++ b/marked/Rel-11/43_series/43055/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:44a74ac0c10a606d3be67b98ea1d60d57724007168f9285adb368fb70f894cc2 +size 98679 diff --git a/marked/Rel-11/43_series/43055/29f586959675cafdf81cf934954908eb_img.jpg b/marked/Rel-11/43_series/43055/29f586959675cafdf81cf934954908eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e16d055ffeda8c5926ac311cc42ffdf075857ad6 --- /dev/null +++ b/marked/Rel-11/43_series/43055/29f586959675cafdf81cf934954908eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5034af86a977e71b87dae1c0a467698c8ec8db95dda14187b712c932fa78e4b9 +size 20242 diff --git a/marked/Rel-11/43_series/43055/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-11/43_series/43055/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..faa29c7177f7a92126918d3dd74e39d653b57b95 --- /dev/null +++ b/marked/Rel-11/43_series/43055/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fbde79429618a4c98a7b62bf6ed4a468dd6cae20db261b713c740b2a37b20a1f +size 96312 diff --git a/marked/Rel-11/43_series/43055/2de714cedbbdd36f901f71bafa78f75a_img.jpg b/marked/Rel-11/43_series/43055/2de714cedbbdd36f901f71bafa78f75a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2d52f534eaf36117633f20337aedddc20b0cfd3 --- /dev/null +++ b/marked/Rel-11/43_series/43055/2de714cedbbdd36f901f71bafa78f75a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:072b41ad52756c90d9a45979676a485b166c33dbbdd51007dc94ea08b510f850 +size 31071 diff --git a/marked/Rel-11/43_series/43055/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-11/43_series/43055/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..873913a1bfc47c55e971093c5b2aa2effff49de0 --- /dev/null +++ b/marked/Rel-11/43_series/43055/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92a3de26bfb9c3a564c728816b114024617bf856be23c681f7dfe5061ae79817 +size 19739 diff --git a/marked/Rel-11/43_series/43055/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg b/marked/Rel-11/43_series/43055/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e014130852bfa9d47b92551cf1858e88e0e1461 --- /dev/null +++ b/marked/Rel-11/43_series/43055/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56bfe304e0783499b2c5ed436f67b4c640a724538b74b2f167168ab0e8291074 +size 38207 diff --git a/marked/Rel-11/43_series/43055/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-11/43_series/43055/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2774193b6cfea5053a52a16f2063ba8bf2125a75 --- /dev/null +++ b/marked/Rel-11/43_series/43055/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:026c63b720526346f09a7873de0722be02756eadf53b9176aacf9f2794e146fd +size 23860 diff --git a/marked/Rel-11/43_series/43055/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-11/43_series/43055/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..925cbad4aec575d97994d3af75263a2b19fc86bd --- /dev/null +++ b/marked/Rel-11/43_series/43055/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16584a17dd0445e72acd9a22c8f27023e35f2e4a734cd9f753b4bca3d49f5024 +size 77551 diff --git a/marked/Rel-11/43_series/43055/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg b/marked/Rel-11/43_series/43055/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f704dcbf6884634589e185176ce84c5cbcdf0ee --- /dev/null +++ b/marked/Rel-11/43_series/43055/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d5bb0cc32ec5b4d608ae4314ae8fb50ac7b6f2dcab082b8cfed52e1e59caa5e +size 126028 diff --git a/marked/Rel-11/43_series/43055/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-11/43_series/43055/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a908c173cb044c507bc67e37aca5281c1111296a --- /dev/null +++ b/marked/Rel-11/43_series/43055/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f54e7305cd0cb4323b8d220fc0829677e56c629407491c80f3cef7a9ebe3578b +size 30885 diff --git a/marked/Rel-11/43_series/43055/898fb89a50d9ec1dfb4e425c816976a7_img.jpg b/marked/Rel-11/43_series/43055/898fb89a50d9ec1dfb4e425c816976a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..acb85cc034678bc92933e7788cc29f93af71e5c5 --- /dev/null +++ b/marked/Rel-11/43_series/43055/898fb89a50d9ec1dfb4e425c816976a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1cefba0bafc3c4a5319eb094b4ef2e13fb3cac9108429e825d521f348e19b59 +size 111731 diff --git a/marked/Rel-11/43_series/43055/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-11/43_series/43055/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f74cf30baf005d775a12f462922e0416c2d92a2c --- /dev/null +++ b/marked/Rel-11/43_series/43055/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c444b33be19fe8beecb23567088edfe449ae077544f408ca6f53d43b8c242071 +size 101287 diff --git a/marked/Rel-11/43_series/43055/96bfe678265c45ada94af2d97be9d002_img.jpg b/marked/Rel-11/43_series/43055/96bfe678265c45ada94af2d97be9d002_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ddf9f57c6e10fd36a0b187b8e1d6985bcb88284 --- /dev/null +++ b/marked/Rel-11/43_series/43055/96bfe678265c45ada94af2d97be9d002_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19422a673b9dd8b67686a8cce5bb9399884868c8f846e2f9c88b477222107a27 +size 19402 diff --git a/marked/Rel-11/43_series/43055/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-11/43_series/43055/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50b6fa7a1fd4c57c2fa3b6ed08b5ad866adea162 --- /dev/null +++ b/marked/Rel-11/43_series/43055/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12571954d4d6e3a4e5133c749091b15a50888bafd7c9141a43cddb41480347a8 +size 115478 diff --git a/marked/Rel-11/43_series/43055/a3083eec2a883ee8327b3c24174df6a9_img.jpg b/marked/Rel-11/43_series/43055/a3083eec2a883ee8327b3c24174df6a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f695046b27f04ab2792ba7f39729afc0ec4243f5 --- /dev/null +++ b/marked/Rel-11/43_series/43055/a3083eec2a883ee8327b3c24174df6a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64cf186f0901559b66717b249a938ef9107881001823aa324e29ef05667e9b1e +size 65911 diff --git a/marked/Rel-11/43_series/43055/b2ea162a0f53d5e0504b7d28346e0754_img.jpg b/marked/Rel-11/43_series/43055/b2ea162a0f53d5e0504b7d28346e0754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79c339115e13a491e2585f190725735afb6a8248 --- /dev/null +++ b/marked/Rel-11/43_series/43055/b2ea162a0f53d5e0504b7d28346e0754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49f1b23f6fb8a9fcc34ae54ff1d6bd6a9122cd8f1ed975ce08d8876946b1c1f9 +size 82722 diff --git a/marked/Rel-11/43_series/43055/b904ac2472cab80892d1e783e6230d6e_img.jpg b/marked/Rel-11/43_series/43055/b904ac2472cab80892d1e783e6230d6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5bfe84e3eb66a7dfd1d1d07bf1b3f09e2d18c92 --- /dev/null +++ b/marked/Rel-11/43_series/43055/b904ac2472cab80892d1e783e6230d6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8b6bc378f0ac4334156b4e14c00d87c31392fe6a2ad3be473227518ce3b82ec +size 85810 diff --git a/marked/Rel-11/43_series/43055/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-11/43_series/43055/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dafed16702c588ad72b51739bb62eea6e6bcf797 --- /dev/null +++ b/marked/Rel-11/43_series/43055/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f641735699eda47723fd48f399c79e3c4a0542749e77a8854c9d89a8ea06817d +size 56595 diff --git a/marked/Rel-11/43_series/43055/cad89c017c9e7c1785bcd104fde4e737_img.jpg b/marked/Rel-11/43_series/43055/cad89c017c9e7c1785bcd104fde4e737_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..650d2f1c868b95cf0f60e8c34c0174846db92159 --- /dev/null +++ b/marked/Rel-11/43_series/43055/cad89c017c9e7c1785bcd104fde4e737_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53165cd291077fbacbb7c409ba93c205174eeb96b5e149d5d32d882d2e33bbe3 +size 84200 diff --git a/marked/Rel-11/43_series/43055/d79d33da852cb7bca3e87b400a15c3e8_img.jpg b/marked/Rel-11/43_series/43055/d79d33da852cb7bca3e87b400a15c3e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..293ef67c132d6c4b2898b32d12b0e4aca7ab5cf2 --- /dev/null +++ b/marked/Rel-11/43_series/43055/d79d33da852cb7bca3e87b400a15c3e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:594a9f01cc153d812d5d9c1834f36c68dd5b9eb7e5c935a9d0f59fdb1c0ee2d5 +size 32660 diff --git a/marked/Rel-11/43_series/43055/d8698aacaeead6dfed9a1e448670a2e4_img.jpg b/marked/Rel-11/43_series/43055/d8698aacaeead6dfed9a1e448670a2e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a99166836cc2cb83a1cda1e86a5e217f2319d623 --- /dev/null +++ b/marked/Rel-11/43_series/43055/d8698aacaeead6dfed9a1e448670a2e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:89c4c209856b288424e6e69857dee061d0bf61f49c6f831db99a9ce6d4bc4cc4 +size 40048 diff --git a/marked/Rel-11/43_series/43055/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-11/43_series/43055/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f76ce6cae0c27101352762a04e9495c3fed5250 --- /dev/null +++ b/marked/Rel-11/43_series/43055/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa884b1439fd708feed11e5a785e8f7d6cef3d64ebbfb286dc803d976a791e95 +size 49674 diff --git a/marked/Rel-11/43_series/43055/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/marked/Rel-11/43_series/43055/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa849039a1d234527e391c8ed0d7d1ee4f4f87f8 --- /dev/null +++ b/marked/Rel-11/43_series/43055/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c407a5c082594d4e64f2a0ece7d449fac026d395c82066c4efd44dc7eeb04353 +size 65578 diff --git a/marked/Rel-11/43_series/43055/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg b/marked/Rel-11/43_series/43055/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..741ae2e6ddc57bca690e4d3e0991c0a8be452884 --- /dev/null +++ b/marked/Rel-11/43_series/43055/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af55031de0c80051f300bfaa1ce82481a9b1291d6d8bd88098afe28e7ee3c936 +size 45445 diff --git a/marked/Rel-11/43_series/43055/f0a97d0d3818a253c1d2a009966081b1_img.jpg b/marked/Rel-11/43_series/43055/f0a97d0d3818a253c1d2a009966081b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b353da612406f85b8c1ee897a9654da4ff44a1b --- /dev/null +++ b/marked/Rel-11/43_series/43055/f0a97d0d3818a253c1d2a009966081b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa0e9f0df276de073a8165456069e8679cd6fe42d40b9e8c46007faa9e8e1a5e +size 87326 diff --git a/marked/Rel-11/43_series/43055/f5deee2f3301ee351c4008283ffafbb3_img.jpg b/marked/Rel-11/43_series/43055/f5deee2f3301ee351c4008283ffafbb3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a95b90a6eafcb1e083117e88b797863179bb94ca --- /dev/null +++ b/marked/Rel-11/43_series/43055/f5deee2f3301ee351c4008283ffafbb3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aac5e1283c1cd599648b0c8e0d34a54f3af890606d1419834c6923253c140cb4 +size 48122 diff --git a/marked/Rel-11/43_series/43055/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-11/43_series/43055/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1f33e968a7b141c30a8f6342ecec90a8943b705 --- /dev/null +++ b/marked/Rel-11/43_series/43055/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2306dfe8e45cd9c96444253584402d1cc3cd9d9b58ce2d2ea01a3ea9254b921e +size 34079 diff --git a/marked/Rel-11/43_series/43055/raw.md b/marked/Rel-11/43_series/43055/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9c7b0ce0757ee8a266fb056914ba964183dd8866 --- /dev/null +++ b/marked/Rel-11/43_series/43055/raw.md @@ -0,0 +1,1904 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| Introduction ..... | 5 | +| Motivation ..... | 5 | +| Concept basis ..... | 5 | +| Class A mode of operation ..... | 6 | +| 1 Scope ..... | 7 | +| 2 References ..... | 7 | +| 3 Definitions and abbreviations ..... | 8 | +| 3.1 Definitions ..... | 8 | +| 3.2 Abbreviations ..... | 8 | +| 4 Class A capabilities ..... | 9 | +| 4.1 Main DCCH with SAPI=0 ..... | 9 | +| 4.1.1 General ..... | 9 | +| 4.1.2 MS-SGSN tunnelling ..... | 9 | +| 4.2 Single slot operation ..... | 10 | +| 4.2.1 General ..... | 10 | +| 4.2.2 TCH/H + PDCH/H ..... | 10 | +| 4.3 Multislot operation ..... | 11 | +| 4.3.1 General ..... | 11 | +| 4.3.2 Shared PDCH ..... | 11 | +| 4.3.3 Exclusive use of PDCH/H ..... | 11 | +| 4.3.4 TCH/H + PDCH/F ..... | 11 | +| 4.3.5 Dual Carrier in the Downlink ..... | 11 | +| 4.4 Bearer capability ..... | 11 | +| 4.5 Indication of the DTM capabilities supported by the MS ..... | 12 | +| 4.5.1 Definition of MS DTM classes ..... | 12 | +| 4.5.1.1 MS DTM classes ..... | 12 | +| 4.5.1.2 Use of full and half rate ..... | 12 | +| 4.5.1.3 Incremental support ..... | 12 | +| 4.5.2 Options ..... | 13 | +| 4.6 Indication of the capabilities ..... | 13 | +| 4.7 Compatibility issues ..... | 14 | +| 5 Layer 1 ..... | 14 | +| 5.1 Timing advance ..... | 14 | +| 5.2 Measurement reporting ..... | 14 | +| 5.3 Power control in multislot operation ..... | 15 | +| 5.3.1 General ..... | 15 | +| 5.3.2 Uplink multislot power control ..... | 15 | +| 5.3.3 Downlink multislot power control ..... | 15 | +| 6 Signalling procedures ..... | 15 | +| 6.1 Establishment ..... | 15 | +| 6.1.1 General ..... | 15 | +| 6.1.2 PS establishment while in dedicated mode ..... | 16 | +| 6.1.2.1 Principles ..... | 16 | +| 6.1.2.2 MO session: packet request procedure ..... | 16 | +| 6.1.2.3 MT session ..... | 18 | +| 6.1.2.3.1 Ready state: packet downlink assignment ..... | 18 | +| 6.1.2.3.2 Standby state: packet notification ..... | 18 | +| 6.1.3 CS establishment while in packet transfer mode ..... | 19 | +| 6.1.4 PS establishment while in dual transfer mode ..... | 22 | +| 6.2 Release ..... | 22 | +| 6.2.1 Release of packet resources ..... | 22 | +| 6.2.2 Release of CS resources ..... | 22 | +| 6.3 Handover ..... | 23 | + +| | | | +|-------------------------------|-------------------------------------------------------------------------------------------|-----------| +| 6.3.1 | General ..... | 23 | +| 6.3.1a | DTM Handover – General..... | 24 | +| 6.3.2 | Internal handover..... | 24 | +| 6.3.2a | Intra-BSS DTM Handover ..... | 25 | +| 6.3.2a.1 | General..... | 25 | +| 6.3.2a.2 | Preparation Phase – using Optimized PS Handover procedure and without MSC involved ..... | 26 | +| 6.3.2a.3 | Preparation Phase – using Non-Optimized PS Handover procedure and with MSC involved ..... | 26 | +| 6.3.2a.4 | Execution Phase..... | 26 | +| 6.3.3 | External handover..... | 28 | +| 6.3.3a | Inter-BSS DTM Handover ..... | 29 | +| 6.3.3a.1 | General..... | 29 | +| 6.3.3a.2 | Preparation Phase..... | 29 | +| 6.3.3a.3 | Execution Phase..... | 30 | +| 6.3.4 | Inter-RAT DTM Handover..... | 32 | +| 6.3.4.1 | General..... | 32 | +| 6.3.4.2 | Inter-RAT DTM Handover from GERAN A/Gb mode to UTRAN ..... | 34 | +| 6.3.4.3 | Inter-RAT DTM Handover from UTRAN to GERAN A/Gb mode ..... | 36 | +| 6.4 | Location management ..... | 37 | +| 6.4.1 | General ..... | 37 | +| 6.4.2 | Cell update..... | 38 | +| 6.4.3 | Routeing Area update..... | 39 | +| 6.4.4 | Location update ..... | 40 | +| 6.4.4.1 | Change of Location Area in dedicated mode..... | 40 | +| 6.4.4.2 | Simultaneous Location Area and Routeing Area update procedures ..... | 41 | +| 6.5 | Provision of the IMSI to the BSC ..... | 42 | +| 6.5.1 | General ..... | 42 | +| 6.5.2 | Call establishment ..... | 42 | +| 6.5.3 | Session establishment..... | 42 | +| 6.5.3.1 | Downlink session establishment..... | 42 | +| 6.5.3.2 | Uplink session establishment..... | 43 | +| 6.5.4 | External handover..... | 43 | +| 6.6 | In-band parameters..... | 43 | +| 6.7 | MS behaviour in heterogeneous networks..... | 44 | +| 6.7.1 | General ..... | 44 | +| 6.7.1 | Suspension procedure..... | 45 | +| 6.7.2 | Resume procedure ..... | 45 | +| 7 | DTM operation..... | 46 | +| 8 | GPRS attach procedure while in dedicated mode and packet idle mode..... | 46 | +| 9 | Security ..... | 46 | +| 10 | Header and Data Compression..... | 46 | +| Annex A (informative): | Possible improvements for future releases..... | 47 | +| Annex B (normative): | Incremental support of extended DTM multislot classes ..... | 48 | +| Annex C (informative): | Change history..... | 49 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- Introduction + +# Motivation + +The definition of GPRS class A mode of operation in Release 97 assumes a total independence between the CS and PS domains. Thus the direct implementation of the existent standards for class A would result in mobile stations that are required to operate in two different frequencies either in the same timeslot, in timeslots $n$ and $n + 3$ or their adjacent ones. This complicates enormously the internal architecture of the ME, resulting in a very high development cost, which both operators and manufacturers would prefer to avoid. + +Nevertheless, operators have expressed their need for this type of mobiles, since they want to offer services that demand the simultaneous existence of a CS connection and a PS session. This is particularly important during the coexistence of GSM/GPRS with UMTS, as these capabilities will exist in UMTS. However, UMTS coverage may not be available in some areas where there is GSM/GPRS coverage (e.g. deep inside buildings or when roaming to a 2G network). As coverage is a vital service, in order for an operator to be able to sell "UMTS class A services" it is necessary to be able to imitate class A services in areas of only GSM coverage. On the other hand, the provision of class A services with GERAN technology is also essential for operators without UMTS coverage. + +# Concept basis + +A constant aim throughout this document is to reuse the existing functionality when possible, in order to minimise the impact on current implementations. In general, the changes proposed have little impact on the core network elements (i.e. MSC and SGSN) and 3G TS 24.008 [11]. + +The solution outlined in this document overcomes the restrictions mentioned above and makes possible to have simultaneous CS and PS active connections. This is achieved by sending PS data (signalling and user data) + +- on the timeslot use by the CS connection +- on timeslot(s) not used by the CS connection + +The possible timeslot configurations are based on two restrictions in Release 99: + +- the number of timeslots allocated to the CS connection is limited to one; +- the timeslots allocated in each direction are contiguous. + +More flexible proposals are left for further study. In addition, for the definition of DTM multislots classes, the restrictions in 3G TS 45.002 [6] for multislots capabilities shall apply. + +Figure 1 shows an example of a multislots configuration (2 uplink, 3 downlink). + +![Figure 1: Example of multislots configuration of a GPRS simple class A mobile station in dual transfer mode. The diagram shows four horizontal rows representing timeslots: Rx (downlink), Tx (uplink), f1 (first frequency), and f2 (second frequency). The Rx row has 8 timeslots (0-7) repeated three times. The Tx row has 8 timeslots (0-7) repeated three times. The f1 and f2 rows show the active timeslots for each frequency. A legend at the bottom indicates: Red square = CS (Circuit Switched), Blue square = PS (Packet Switched), Green square = Measurements. Arrows show the mapping of timeslots between the Rx/Tx rows and the f1/f2 rows. In the first frequency (f1), timeslots 2 and 3 are used for CS (red), and timeslots 1 and 2 are used for PS (blue). In the second frequency (f2), timeslot 2 is used for Measurements (green).](1d27fed9c01eb99f6535283f35fe3bbf_img.jpg) + +Figure 1: Example of multislots configuration of a GPRS simple class A mobile station in dual transfer mode. The diagram shows four horizontal rows representing timeslots: Rx (downlink), Tx (uplink), f1 (first frequency), and f2 (second frequency). The Rx row has 8 timeslots (0-7) repeated three times. The Tx row has 8 timeslots (0-7) repeated three times. The f1 and f2 rows show the active timeslots for each frequency. A legend at the bottom indicates: Red square = CS (Circuit Switched), Blue square = PS (Packet Switched), Green square = Measurements. Arrows show the mapping of timeslots between the Rx/Tx rows and the f1/f2 rows. In the first frequency (f1), timeslots 2 and 3 are used for CS (red), and timeslots 1 and 2 are used for PS (blue). In the second frequency (f2), timeslot 2 is used for Measurements (green). + +**Figure 1: Example of multislots configuration of a GPRS simple class A mobile station in dual transfer mode.** + +In a similar manner to UMTS, the A interface is modified so that the BSC knows the IMSI associated with each SCCP connection to the MSC. This means that the BSC is able to ensure that 'packet paging' messages can be delivered to mobile stations which have a connection to the MSC. The same functionality can be reused to deliver MSC originated pages to mobiles in packet transfer mode while the network is in mode of operation II (i.e. no Gs interface). + +Mobility management is basically the same as is specified in 3GPP TS 23.060 [9] for class A mobiles, but using the same techniques as UMTS for control of "in connection" cell, routeing area and location area updates (e.g. System Information 6 message is extended to contain the Routing Area Code). + +If GPRS signalling needs to be sent during a standalone voice call, then it is proposed that these LLC frames can be sent on the main DCCH (FACCH or SDCCH) with layer 2 SAPI 0. This uses a new Protocol Discriminator in 3GPP TS 24.007 for LLC: GTTP (GPRS Transparent Transport Protocol). The use of the main DCCH for GPRS signalling is subject to certain restrictions to reduce the harm to the speech quality. + +Inter-BSC handover is planned to be controlled by A interface signalling. The *Old BSS to New BSS* information element is used to indicate to the target BSC that the mobile station is in DTM. + +DTM Handover procedure is realized by utilizing in parallel the handover procedures that are defined in 3GPP TS43.129 [13] for the PS domain and in 3GPP TS 23.009 [14] for the CS domain. + +# Class A mode of operation + +For paging, the behaviour of the mobile station is as in class B mode of operation: the PCH takes priority to PPCH, and both to CBCH. + +The implementation described in this document also applies the restriction that the mobile station shall not be required to operate in two different frequencies in the same moment in time. However, GSM CS and GSM GPRS services will be still supported simultaneously. Thus, the feature here described is a subset of the GPRS class A capabilities. + +The mentioned subset will be referred as DTM. + +The specification of an *unrestricted* class A mode of operation that requires the mobile station to operate in different frequencies simultaneously shall not be forbidden. + +# --- 1 Scope + +The present document is a description of the practical implementation of GSM-GPRS class A mobiles and a basis for discussion on the changes and additions to the current specifications. + +This work is part of the Release 99 Work Item "BSS co-ordination of Radio Resource allocation for class A GPRS services - GSM Radio Access (R99)" for which M Mouly of Nortel Networks is rapporteur. This work item was supported by Nortel, Motorola, Vodafone and Lucent. + +In the following, GPRS refers to EGPRS, EGPRS2 and GPRS unless explicitly stated otherwise. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.060: "General Packet Radio Service (GPRS); Service description; Stage 1". +- [3] 3GPP TS 44.013: "Performance requirements on the mobile radio interface". +- [4] 3GPP TS 44.018: "Mobile radio interface layer 3 specification, Radio Resource Control Protocol". +- [5] 3GPP TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control/ Medium Access Control (RLC/MAC) protocol". +- [6] 3GPP TS 45.002: "Multiplexing and multiple access on the radio path". +- [7] 3GPP TS 45.008: "Radio subsystem link control". +- [8] 3GPP TS 45.010: "Radio subsystem synchronization". +- [9] 3GPP TS 23.060: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS); Service description; Stage 2". +- [10] 3GPP TS 23.121: "3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; Architectural Requirements for Release 1999". +- [11] 3GPP TS 24.007: "3rd Generation Partnership Project; Technical Specification Group Core Network; Mobile radio interface signalling layer 3; General aspects". +- [12] 3GPP TS 24.008: "3rd Generation Partnership Project; Universal Mobile Telecommunications System; Mobile radio interface layer 3 specification, Core Network Protocols - Stage 3". +- [13] 3GPP TS 43.129: "3rd Generation Partnership Project; Packet-switched handover for GERAN A/Gb mode; Stage 2". +- [14] 3GPP TS 23.009: "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Handover procedures; Stage 2". +- [15] 3GPP TS 25.331: "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Radio Resource Control (RRC); Protocol Specification". + +- [16] 3GPP TS 25.413: "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iu interface RANAP signaling". +- [17] 3GPP TS 48.008: "3rd Generation Partnership Project; Technical Specification Group GSM/EDGE Radio Access Network; Mobile Switching Centre - Base Station System (MSC-BSS) interface; Layer 3 specification". +- [18] 3GPP TS 48.018: "3rd Generation Partnership Project; Technical Specification Group GSM/EDGE Radio Access Network; General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN); BSS GPRS Protocol (BSSGP)". +- [19] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC);Stage 2" +- [20] 3GPP TS 23.251: "Network Sharing; Architecture and functional description". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**Dual transfer mode:** It is only applicable for a mobile station that supports GPRS. A mobile station in dual transfer mode has resources for an RR connection and is simultaneously1 allocated resources for one or more TBFs, provided that the BSS co-ordinates its allocation of radio resources. DTM is optional both for the mobile station and the network. A DTM mobile is a class A mobile. Hence all specifications/requirements for class A apply to this mobile unless specifically altered by the present document. The procedures specified for dedicated and packet transfer modes apply to a mobile station in dual transfer mode unless specifically altered by the present document. + +**Class A/class B:** In the present document "class A" and "class B" is used as a short form of "class A mode of operation" and "class B mode of operation", respectively. + +**DTM Handover:** DTM handover is introduced in order to support the parallel handover of circuit-switched and packet-switched domains of a mobile station in dual transfer mode or RRC connected mode, from a source cell to a target cell. The procedures specified for circuit-switched handover (see 3GPP TS 23.009 [14]) and packet-switched handover (see 3GPP TS 43.129 [13]) apply to DTM handover unless specifically altered by the present document. + +**Network sharing:** network sharing is an optional feature that allows different core network operators to connect to the same shared radio access network (see 3GPP TS 23.251 [20]). When network sharing is in use within a given cell, the network broadcasts within system information the PLMN identities of the PLMNs sharing the cell. A mobile station supporting network sharing uses this information for its PLMN (re)selection processes and indicates the selected PLMN to the BSS. When GERAN specifications have statements referring to network sharing support/non-support, this refers to whether or not the MS supports GERAN network sharing and (unless specified otherwise) are not related to support of network sharing on other RATs. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-----|-------------------------| +| CS | Circuit Switched | +| CN | Core Network | +| DTM | Dual Transfer Mode | +| PS | Packet Switched | +| RAT | Radio Access Technology | + +--- + +1 The term "simultaneous" is used in the present document with the same meaning as in 22.060. Different services or connections may happen *simultaneously* and be multiplexed at lower layers so that they e.g. different TDMA time slots in the same carrier. + +# 4 Class A capabilities + +## 4.1 Main DCCH with SAPI=0 + +### 4.1.1 General + +The main DCCH (with layer 2 SAPI=0) is used for GSM signalling. GPRS signalling shall be able to use this resource. User data shall not be sent on the main DCCH. + +The use of the main DCCH is only allowed when the mobile station is in dedicated mode. In dual transfer mode (i.e. the mobile station has resources allocated for an RR connection and for one or more TBFs), the main DCCH shall not be used and the current procedures described in 3GPP TS 44.060 [5] apply. + +When upper layers request to send a message uplink, the mobile station shall send the message on the main DCCH if: + +- the mobile station is in dedicated mode; +- the information contained in the message is signalling; and +- the number of LAPDm frames is smaller than a certain value specified by the network. When the parameter defining the maximum number of LAPDm frames has not been received by the MS in the serving cell (e.g. immediately after a handover), the MS assumes the default value defined in 3GPP TS 44.018 + +Otherwise, the mobile station shall request an uplink TBF as specified in 3GPP TS 44.018 [4]. Even though the mobile station shall not send messages on the main DCCH in dual transfer mode, the network shall not reject the received messages. + +NOTE: This is needed to prevent erroneous cases caused by race conditions (e.g. if an uplink message sent on the main DCCH is not completely acknowledged on layer 2 level by the network before the mobile station leaves the dedicated mode and enters the dual transfer mode, the network would reject the message). + +On the other hand, the network should not use the main DCCH to send messages that exceed the maximum length specified for the uplink. The mobile station, however, shall not reject messages that exceed the maximum length. Similarly, the network should not use the main DCCH when the mobile station is in dual transfer mode, although the mobile station shall not reject the received messages. + +NOTE: This is needed to prevent erroneous cases caused by race conditions (e.g. if the mobile station leaves the dedicated mode and enters the dual transfer mode at the same time as the network sends a downlink message on the main DCCH, the mobile station would reject the message). + +### 4.1.2 MS-SGSN tunnelling + +The GPRS information from upper layers (i.e. GMM or SM) is always sent inside an LLC frame. This LLC frame can now be passed down: + +- to RLC and transmitted on a TBF; or +- to RR, if the MS is in dedicated mode, and transmitted on the main DCCH. + +The procedures for the transmission of an LLC frame via RLC are defined in 3GPP TS 44.060 [5]. The procedures for the transmission of an LLC frame on the main DCCH are defined in 3GPP TS 44.018 [4]. The new tunnelling mechanism for the transmission of the LLC frame is shown graphically in figure 2. + +![Figure 2: Transmission of an LLC PDU on the main DCCH. The diagram shows the protocol stack for MS, BSS, and SGSN. In the MS, a 'Msg' contains an 'LLC PDU', which is encapsulated in a 'GTTP PDU' (RR/GTTP layer), then into two 'L2' blocks, and finally to the 'GSM RF' layer. The BSS acts as a 'Relay', receiving the 'L2' blocks and re-encapsulating the 'LLC PDU' into a 'BSSGP PDU' (BSSGP layer), which is then sent to the SGSN. The SGSN receives the 'BSSGP PDU', decapsulates it to get the 'LLC PDU', which is then passed up to the 'GMM/SM' layer. The diagram also shows the layers for the BSS: 'GSM RF', 'L1 bis', 'NS', 'L2', 'RR/GTTP'/'BSSGP', 'LLC', and 'GMM/SM'.](e6df2733626a85205c1db682e6259c46_img.jpg) + +Figure 2: Transmission of an LLC PDU on the main DCCH. The diagram shows the protocol stack for MS, BSS, and SGSN. In the MS, a 'Msg' contains an 'LLC PDU', which is encapsulated in a 'GTTP PDU' (RR/GTTP layer), then into two 'L2' blocks, and finally to the 'GSM RF' layer. The BSS acts as a 'Relay', receiving the 'L2' blocks and re-encapsulating the 'LLC PDU' into a 'BSSGP PDU' (BSSGP layer), which is then sent to the SGSN. The SGSN receives the 'BSSGP PDU', decapsulates it to get the 'LLC PDU', which is then passed up to the 'GMM/SM' layer. The diagram also shows the layers for the BSS: 'GSM RF', 'L1 bis', 'NS', 'L2', 'RR/GTTP'/'BSSGP', 'LLC', and 'GMM/SM'. + +**Figure 2: Transmission of an LLC PDU on the main DCCH** + +In the uplink, the LLC PDU is inserted in a new Layer 3 message2. This Layer 3 message is sent to the BSC on the main DCCH, with the existing Layer 2 mechanisms. The BTS re-assembles the Layer 3 message and sends it to the BSC. The BSC extracts the TLLI and the LLC PDU, which are then put into a BSSGP UL-UNITDATA. + +In the downlink, when the BSS receives a downlink BSSGP PDU, it can identify: + +- if the PDU contains signalling information ("T bit" in the QoS profile IE); +- if the length of the LLC PDU meets the requirements; and +- if it has an RR connection to the addressed MS (with the IMSI); + +in which case, it sends the LLC using the same procedure as described above. If any of the conditions above is not met, the BSC sends the information on a downlink TBF. + +## 4.2 Single slot operation + +### 4.2.1 General + +A mobile station in dual transfer mode has one timeslot allocated for the CS services. It is possible to reuse the same timeslot for the transmission of GPRS signalling and user data. + +It is desirable to be able to use the same timeslot as the CS connection for GPRS data, due to the impossibility for the network to allocate a TBF in some circumstances (e.g. congested cell, multislot capabilities not supported in the serving cell). + +The proposed solution for single timeslot operation is the "TCH/H + PDCH/H" configuration (see 3GPP TS 45.002 [6]). + +### 4.2.2 TCH/H + PDCH/H + +A "TCH/H + PDCH/H" configuration implies the multiplexing of CS information and RLC/MAC blocks in the same timeslot of the TDMA frame. Which domain uses each half shall be flexible and indicated in the assignment command. + +On the 'TCH/H' part, the support of AMR as the speech codec is mandatory. Support of other circuit switched half rate traffic channels are indicated in the bearer capability IE (see 3GPP TS 24.008). + +The PDCH/H is a resource dedicated to the mobile station in both directions. For instance, if an uplink TBF is established, the network may send a control message in any of the downlink blocks. No downlink data, however, shall be sent without a previous downlink assignment. + +The existent RLC/MAC block format is used. In the downlink, the mobile station shall only pass to upper layers those blocks with the TFI indicated in the assignment message. In the uplink, the mobile station may transmit in any of the blocks of the PDCH/H, irrespective of the USF in the previous blocks in the dynamic allocation case, if the USF was + +2 This message is sent with a new Protocol Discriminator (GTTP) so that the BSC identifies the tunnelling mechanism without the need to analyse the Message Type. This helps reduce the processor load in the BSC. + +present in the (uplink) assignment message. The mobile station, however, stores the USF for possible multislot configurations where dynamic allocation is supported. + +The PDCH/H can be used for both GPRS signalling and user data. A PDCH/H shall not be assigned to a DTM capable mobile station in packet transfer mode. + +Apart from the different mapping onto physical resources, the PDCH/H has the same characteristics as a PDCH/F. A PDCH/H is always used in exclusive allocation. + +If a mobile station and the network support multiple TBF procedures (see 3GPP TS 44.060) and the mobile station is DTM capable, the network may establish multiple downlink TBFs using the PDCH/H. Only one uplink TBF may be established on a PDCH/H since exclusive allocation is used. + +## 4.3 Multislot operation + +### 4.3.1 General + +In multislot operation, the packet data is sent on one or more PDCHs. The number of timeslots (i.e. PDCHs) used to carry packet data is decided by the network after taking into account the DTM multislot capabilities supported by the mobile station. + +### 4.3.2 Shared PDCH + +The PDCH/F may be shared with other GPRS mobile stations. The existent procedures in 3GPP TS 44.060 [5] apply. In the case of GPRS, EGPRS and EGPRS2 MSs multiplexed on the same PDCH, the same restrictions as described in 3GPP TS 44.060 [5] shall apply. + +If a mobile station and the network support multiple TBF procedures (see 3GPP TS 44.060) and the mobile station is DTM capable, the network may establish multiple downlink TBFs for that mobile station using one or more shared PDCHs. In this case the mobile station may request the establishment of multiple uplink TBFs and the network may allocate uplink TBF resources on one or more shared PDCHs. + +### 4.3.3 Exclusive use of PDCH/H + +The PDCH/H shall not be shared with other GPRS mobile stations. An uplink PDCH/H shall be assigned in exclusive mode, where the correspondent mobile station is always granted the right to transmit. The existent RLC/MAC block structure shall be kept. The procedures specified in 3GPP TS 44.060 [5] shall apply. + +Despite the dedicated characteristics of the uplink PDCH/H, the network shall allocate and use a valid USF, in order to satisfy the signalling requirements defined in 3GPP TS 44.060 [5]. + +### 4.3.4 TCH/H + PDCH/F + +For this configuration, on the 'TCH/H' part the support of AMR as the speech codec is mandatory. Support of other circuit switched half rate traffic channels is indicated in the Bearer Capability IE (see 3GPP TS 24.008). + +### 4.3.5 Dual Carrier in the Downlink + +DTM configurations which use two radio frequency channels in the downlink shall obey the following restrictions: + +- Uplink PDCHs shall be assigned on the same radio frequency channel as the uplink CS timeslot. +- Only EGPRS or EGPRS2 TBFs shall be assigned to the packet resources. + +## 4.4 Bearer capability + +The decision of which of the class A capabilities shall be used shall be always made by the network after considering: + +- the supported capabilities (by both the network and the mobile station); +- the type of data to be sent; +- the length of the data; and + +- the requested QoS parameters; + +shows the GPRS data supported by the different class A capabilities. + +**Table 1: Support of GPRS data by the different class A capabilities** + +| Bearer | | Main DCCH with SAPI 0 | Single slot operation | Multislot operation | +|-----------------|--------------|-----------------------|-----------------------|---------------------| +| GPRS data | | | | | +| GPRS signalling | Short frames | Yes | Yes | Yes | +| | Long frames | No | | | +| User data | | No | | | + +NOTE: The use of the main DCCH with SAPI 0 has the following properties: + +- it delays RR commands; +- it harms speech quality; +- it places load onto the A-bis LAPD signalling links; +- it has a maximum length of 251 bytes. + +## 4.5 Indication of the DTM capabilities supported by the MS + +### 4.5.1 Definition of MS DTM classes + +#### 4.5.1.1 MS DTM classes + +Different mobile stations may support different DTM capabilities and thus they need to be communicated to the network so that they can be taken into account for the allocation of radio resources. The DTM multislot capabilities are independent from the currently defined 3GPP TS 45.002 multislot capabilities. When EGPRS is supported, DTM multislot capability for EGPRS operation (applicable also to EGPRS2 operation if supported) is indicated independently from DTM multislot capability for GPRS operation. + +DTM multislot classes 5, 6, 9, 10, 11, 31 to 33, 36 to 38 and 41 to 44 are defined in this release (see 3GPP TS 45.002 [6]). Classes 31 to 33, 36 to 38 and 41 to 44 are supported only by mobile stations supporting DTM High Multislot Class capability. + +#### 4.5.1.2 Use of full and half rate + +The mix of full and half rate packet data channels is not allowed in the uplink. This mix is only defined for the downlink direction and only supported by mobile stations indicating support for Extended GPRS DTM Multi Slot Class or Extended EGPRS DTM Multi Slot Class respectively (See 3GPP TS 24.008). The half rate packet data channel is only allowed on the same time slot as the circuit switched channel. Due to the different rate of the full and half rate channels used for GPRS during DTM, the network shall take care that the RLC/MAC blocks are sent in such an order that the reception is in sequence when using RLC unacknowledged mode. + +#### 4.5.1.3 Incremental support + +In order to reduce the number of possibilities and the length of the coding, incremental support shall be used; that is, a mobile station that supports a certain level of capabilities shall support the capabilities of the less restrictive DTM classes. Annex B defines the incremental support for mobile stations supporting Extended DTM GPRS Multi Slot Class or Extended DTM EGPRS Multi Slot Class. For other mobile stations supporting DTM, the implicit support of the less restrictive DTM classes shall be as indicated in Figure 2a; for these mobile stations the single slot DTM operation is optional and supported if indicated by Single Slot DTM capability bit in the MS Classmark 3 and MS Radio Access Capability IEs. + +![Figure 2a – Incremental support of DTM multislot classes. The diagram shows a hierarchy of DTM classes based on the sum of Rx and Tx slots. Classes are represented in boxes with 'Class' and 'Rx+Tx=Sum'.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` + +graph TD + C44[Class 44 +6+5=7] --> C43[Class 43 +6+4=7] + C43 --> C33_38[Class 33 or 38 +5+4=6] + C43 --> C42[Class 42 +6+3=7] + C33_38 --> C32_37[Class 32 or 37 +5+3=6] + C32_37 --> C31_36[Class 31 or 36 +5+2=6] + C42 --> C41[Class 41 +6+2=7] + C31_36 --> C9[Class 9 +3+2=5] + C41 --> C5[Class 5 +2+2=4] + C9 --> C11[Class 11 +4+3=5] + C11 --> C5 + +``` + +Figure 2a – Incremental support of DTM multislot classes. The diagram shows a hierarchy of DTM classes based on the sum of Rx and Tx slots. Classes are represented in boxes with 'Class' and 'Rx+Tx=Sum'. + +Figure 2a – Incremental support of DTM multislot classes + +### 4.5.2 Options + +The support of the following four capabilities has to be indicated independently from the DTM class: + +- **Single Slot DTM:** single slot DTM operation supported or not; +- **E-GPRS:** supported or not; +- **Enhanced CS establishment and release:** supported or not; +- **DTM Handover:** supported or not. + +The mobile station also indicates support of the following capabilities which, if supported, require the indication of an additional DTM class: + +- **Extended DTM:** supported or not. If supported, the Extended DTM multislot class shall also be indicated; a separate indication is provided for GPRS and EGPRS; +- **DTM High Multislot Class:** supported or not. If supported, the DTM high multislot class shall also be indicated; a separate indication is provided for GPRS and EGPRS. + +In addition the following rules apply: + +- exclusive allocation in the PDCH/H shall always be used; a mobile station supporting E-GPRS shall support GPRS. + +## 4.6 Indication of the capabilities + +The mobile station DTM class is indicated in the MS Classmark 3 IE and MS Radio Access Capability IE. The absence of this information shall indicate that the mobile station does not support simple class A (i.e. either it supports *unrestricted* class A or it cannot operate in mode of operation A at all). The support of enhanced CS establishment and release is indicated in the MS Classmark 3 and MS Radio Access Capability IEs. For mobile stations supporting DTM High Multislot Class capability, the mobile station DTM high multislot class is indicated in the MS Classmark 3 and MS Radio Access Capability IEs. The support of DTM handover is indicated in the MS Radio Access Capability and MS Classmark 3 IEs. + +## 4.7 Compatibility issues + +The mobile station shall indicate in its capabilities whether it is DTM capable or not and if so whether it supports enhanced CS establishment and release or not. The mobile station shall indicate in the MS Radio Access Capability and MS Classmark 3 IEs whether or not it supports DTM Handover. The network shall not allocate resources for DTM operation unless the mobile is DTM capable. The network shall not use enhanced CS establishment (respectively + +release) unless the mobile supports it. The network shall not use DTM Handover procedures unless the mobile station also supports it. The resources allocated by the network shall meet the requirements imposed by the classmark. + +The network indicates on the BCCH or PBCCH whether or not the cell supports DTM and if so whether or not it supports enhanced CS establishment and release. It shall also indicate it on the SACCH for DTM capable mobile stations in dedicated mode or dual transfer mode. It may also indicate it on the PACCH for DTM capable mobile stations in packet transfer mode. A cell level indication is needed because adjacent BTSs may be in the same RA and LA but may be parented by different BSCs (from different vendors or different releases). The indication in the SACCH is needed to enable/suppress the transmission of packet resource requests when the mobile is in dedicated mode and cannot read the BCCH data. A mobile station shall not attempt to enter the DTM unless DTM is supported in the cell. + +The network shall allocate resources taking into account the capabilities commonly supported with the mobile station. In order to avoid situations where both the mobile station and the network are DTM capable but no class A capabilities are shared, a *core set* of capabilities has been defined and shall be supported by the mobile station and the network, consisting of: + +- the main DCCH with SAPI 0 for GPRS signalling, with a length restriction controlled by the network; +- the TCH/F + PDCH/F configuration (DTM multislot class 5). + +In addition, the mobile station supporting DTM shall support TCH/H + PDCH/F configuration with AMR-HR. + +# --- 5 Layer 1 + +Some modifications or extra requirements affect layer 1 areas: + +1. Timing advance; +2. Measurement reporting; +3. Power control. + +These issues are dealt with in the following clauses. + +## 5.1 Timing advance + +A mobile station in DTM shall disable the timing advance features for the GPRS side: + +- the mobile station shall inhibit the transmission of timing advance access bursts; +- the mobile station shall ignore the reception of GPRS timing advance messages, if any. + +The reporting period and the SACCH message block shall be the same as though the mobile station was in dedicated mode. + +## 5.2 Measurement reporting + +The mobile station shall continue to send measurement reports for the circuit switched part, but GPRS measurement reports shall not be sent. The mobile station shall be able to send extended measurement reports when commanded by the network. + +## 5.3 Power control in multislot operation + +### 5.3.1 General + +The difference of C/I requirements and the possibility of using different coding schemes in both domains may result in a difference in the power used in adjacent timeslots. This difference in power needs further consideration, which it is done in the following clauses. + +### 5.3.2 Uplink multislot power control + +On the network side, there is no restriction for the difference of power received in adjacent timeslots. + +On the mobile station side, the power control in different timeslots shall be independent and with no restriction for the difference of power transmitted in adjacent timeslots. + +The MS shall measure the signal strength of each radio block monitored by the MS. The C value used for the uplink power control is achieved by filtering the signal strength with a running average filter. Upon the change from one RR mode to another, the filtering shall be restarted if there is no valid C value available. In case the mobile station and the network support enhanced DTM CS establishment procedure, when entering DTM from packet transfer mode, the filtering shall continue from the C value obtained during packet transfer mode (see 3GPP TS 45.008[7]). + +In single timeslot operation, the power control for both domains is performed on the SACCH. + +### 5.3.3 Downlink multislot power control + +On the network side, there is no restriction for the difference of power transmitted in adjacent timeslots. + +As in normal GPRS power control and in addition to the cells present in SI5, the mobile station shall also perform measurements of the serving cell if the FH sequence does not include the BCCH carrier. + +In DTM multislot configurations, if the BTS output power for the CS timeslot is not within the range from the maximum downlink power allowed for the MS on the PS timeslot(s) to a power level 10 dB lower, the MS is not required to fulfil the requirements in 3GPP TS 45.005 on the CS timeslot and/or the PS timeslot(s). + +# 6 Signalling procedures + +## 6.1 Establishment + +### 6.1.1 General + +The existent establishment procedures for class A mode of operation rely on the capability of the mobile station to be able to operate in different frequencies in the same timeslot, e.g. to listen to the (P)BCCH while in dedicated mode. New procedures need to be added to the specifications to allow mobile stations without such capabilities to be able to enter the dual transfer mode. + +The new cases are marked with "✓" in table 1 and explained in detail in this clause. + +**Table 2: Summary of establishment cases** + +| | | Requested | | | | +|--------|---------|----------------------|---------------|---------------|----------------| +| | | CS | PS | | | +| | | | MO | MT | | +| | | | | Ready state | Standby state | +| Active | Nothing | Normal establishment | | | | +| | CS | Engaged | ✓ | ✓ | ✓ | +| | PS | MO | Same TBF | Normal: PACCH | Not applicable | +| | | MT | Normal: PACCH | Same TBF | | + +### 6.1.2 PS establishment while in dedicated mode + +#### 6.1.2.1 Principles + +The mobile station may request packet resources while in dedicated mode by sending the **DTM Request** message to enter the dual transfer mode. + +Two DTM assignment messages are defined: + +- the **DTM Assignment Command** message: this message shall describe both the CS and packet resources when a reallocation of the CS resource is needed, e.g. when a multislot configuration cannot be accommodated or when an "TCH/H + PDCH/H" configuration is to be used. +- the **Packet Assignment** message: this message describes the allocated packet resources when no reallocation of the CS resource is necessary, e.g. on an adjacent timeslot. + +A mobile station that supports multiple TBF procedures can determine whether or not the network supports multiple TBF procedures by reading the *GPRS Cell Options* IE included within the DTM Assignment Command and the Packet Assignment messages. + +When there is reallocation of the CS timeslot: + +- if the mobile station successfully establishes the new CS connection, it shall send an **Assignment Complete** message on the new main DCCH. +- if the mobile station fails to establish the new CS connection, it shall go back to the old timeslot, send a DTM **Assignment Failure** message on the (old) main DCCH and continue the CS operation. The mobile station shall assume that the old PS resources were released and attempt its re-establishment. + +If the network wants to move the mobile station to another cell, it shall send a **Handover Command** message on the main DCCH. After the handover procedure is completed, the network supporting DTM shall send the **DTM Information** message on the main DCCH in order to speed up the resumption of the dual transfer mode of operation by the mobile station. + +As described above, the main DCCH can be used in either direction with no prior assignment provided that the required conditions are met. Otherwise, the procedures here described apply. + +#### 6.1.2.2 MO session: packet request procedure + +If the serving cell of the CS connection indicates that supports DTM, the mobile station may request the establishment of a PS session by sending a DTM Request message on the main DCCH. + +The network may answer the request with one of the two defined DTM assignment messages, sent on the main DCCH. If the network cannot allocate the packet resources, it shall answer with a **DTM Reject** message on the main DCCH. The DTM Reject message shall indicate a waiting time after which the mobile station is allowed to reattempt the packet establishment in the same cell. + +Figure 3 shows the successful case of the allocation of an uplink TBF when the reallocation of the CS timeslot is needed. The mobile station informs the network about the correct seizure of the new CS resource by sending an Assignment Complete message on the main DCCH of the new resource. + +![Sequence diagram illustrating the establishment of a MO PS session while in dedicated mode with reallocation of the CS resource; successful case. The diagram shows four entities: MS (Mobile Station), BSS (Base Station System), MSC (Mobile Switching Center), and SGSN (Serving GPRS Support Node). The process starts with the MS in 'CS dedicated mode' with the MSC. The MS sends a 'DTM Request' on the '[Old main DCCH]' to the BSS. The BSS responds with a 'DTM Assignment Command' on the '[Old main DCCH]'. The MS then sends an 'Assignment Complete' on the '[New main DCCH]' to the BSS. Finally, the MS sends 'RLC block(s)' on the '[Uplink TBF]' to the BSS, which then forwards them as 'UL-Unitdata' to the SGSN.](2de714cedbbdd36f901f71bafa78f75a_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC + participant SGSN + Note over MS, MSC: CS dedicated mode + MS->>BSS: DTM Request (Old main DCCH) + BSS-->>MS: DTM Assignment Command (Old main DCCH) + MS->>BSS: Assignment Complete (New main DCCH) + MS->>BSS: RLC block(s) (Uplink TBF) + BSS->>SGSN: UL-Unitdata + +``` + +Sequence diagram illustrating the establishment of a MO PS session while in dedicated mode with reallocation of the CS resource; successful case. The diagram shows four entities: MS (Mobile Station), BSS (Base Station System), MSC (Mobile Switching Center), and SGSN (Serving GPRS Support Node). The process starts with the MS in 'CS dedicated mode' with the MSC. The MS sends a 'DTM Request' on the '[Old main DCCH]' to the BSS. The BSS responds with a 'DTM Assignment Command' on the '[Old main DCCH]'. The MS then sends an 'Assignment Complete' on the '[New main DCCH]' to the BSS. Finally, the MS sends 'RLC block(s)' on the '[Uplink TBF]' to the BSS, which then forwards them as 'UL-Unitdata' to the SGSN. + +**Figure 3: Establishment of a MO PS session while in dedicated mode with reallocation of the CS resource; successful case** + +Figure 4 shows one failure case. If there is an error when establishing the main signalling link in the new timeslot, the mobile station shall send a DTM **Assignment Failure** message on the old main DCCH and then it may re-attempt the establishment of the packet session. The timers in the assignment procedure are reused. + +![Sequence diagram for Figure 4: Establishment of a MO PS session while in dedicated mode with reallocation of the CS resource; failure case.](8307f6b04df072c9332f9987e034272c_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC + participant SGSN + Note over MS, MSC: CS dedicated mode + Note left of MS: [Old main DCCH] + MS->>BSS: DTM Request + Note left of MS: [Old main DCCH] + BSS->>MS: DTM Assignment Command + Note left of MS: [Old main DCCH] + MS->>BSS: DTM Assignment Failure + Note left of MS: [Old main DCCH] + MS-->>BSS: DTM Request + +``` + +Sequence diagram for Figure 4: Establishment of a MO PS session while in dedicated mode with reallocation of the CS resource; failure case. + +**Figure 4: Establishment of a MO PS session while in dedicated mode +with reallocation of the CS resource; failure case** + +In figure 5, the packet resource is mapped onto adjacent timeslot(s) and thus the Packet Assignment message is used. There is no release/re-establishment of the main signalling link, successful and failure messages are not needed. The successful and failure cases for the establishment of the TBF are determined as in normal GPRS (see 3G TS 04.60 [5]). + +![Sequence diagram for Figure 5: Establishment of a MO PS session in multislot configuration while in dedicated mode; successful case.](21ad58fee90f2be50708ff541d225507_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC + participant SGSN + Note over MS, MSC: CS dedicated mode + Note left of MS: [Old main DCCH] + MS->>BSS: DTM Request + Note left of MS: [Old main DCCH] + BSS->>MS: Packet Assignment + Note left of MS: [Uplink TBF] + MS->>BSS: RLC block(s) + BSS->>SGSN: UL-Unitdata + +``` + +Sequence diagram for Figure 5: Establishment of a MO PS session in multislot configuration while in dedicated mode; successful case. + +**Figure 5: Establishment of a MO PS session in multislot configuration +while in dedicated mode; successful case** + +Figure 6 shows the case of the main DCCH being used as the uplink resource. + +![Sequence diagram for Figure 6: Use of the main DCCH for GPRS information while in dedicated mode.](29f586959675cafdf81cf934954908eb_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC + participant SGSN + Note over MS, MSC: CS dedicated mode + Note left of MS: [Main DCCH] + MS->>BSS: GTTP Information (LLC PDU) + BSS->>SGSN: UL-UNITDATA (LLC PDU) + +``` + +Sequence diagram for Figure 6: Use of the main DCCH for GPRS information while in dedicated mode. + +**Figure 6: Use of the main DCCH for GPRS information while in dedicated mode** + +#### 6.1.2.3 MT session + +##### 6.1.2.3.1 Ready state: packet downlink assignment + +If the mobile station is in the Ready state, the SGSN may send an LLC frame to the BSS parenting the mobile station's serving cell. The downlink LLC PDU shall include the IMSI if it is known. As the IMSI of the mobile station was previously stored, the BSS is able to identify that the mobile station to which the data is sent is in dedicated mode. The BSS shall use the main signalling link to send the downlink assignment command instead of the (P)CCCH. Note that a mobile station in dedicated mode does not listen to the (P)CCCH unless it is "unrestricted class A" capable. + +Editor's note : the consequences on the procedures currently defined for the DTM feature shall be analysed if the IMSI can not be provided in the BSSGP DL-UNITDATA PDU. + +The assignment is done with one of the DTM assignment messages, sent on the main DCCH. + +Figure 7 shows the successful case, when a downlink TBF is assigned without reallocation of the CS resource. + +![Figure 7: Example of a successful establishment of a PS MT session while in dedicated mode, packet idle mode and Ready state](4356776ca004ecba5d599667a155d7d4_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC + participant SGSN + Note over MS,MSC: CS dedicated mode + SGSN->>BSS: DL-Unitdata + BSS->>MS: Packet Assignment + BSS->>MS: RLC block(s) + +``` + +Figure 7: Example of a successful establishment of a PS MT session while in dedicated mode, packet idle mode and Ready state + +**Figure 7: Example of a successful establishment of a PS MT session while in dedicated mode, packet idle mode and Ready state** + +##### 6.1.2.3.2 Standby state: packet notification + +If the mobile station is in the Stand-by state and the SGSN has something to send, it shall send a page to the BSS(s) parenting the RA where the mobile station is, in order to find out the actual serving cell/BVCI. As the mobile station has an established signalling connection with the BSS, the BSS shall not page the mobile station. Instead, the BSS shall inform the mobile station that it is being paged for packet services. This is done by sending the Packet Notification message on the main DCCH. The mobile station shall answer the notification with a Cell Update procedure: sending an LLC frame to act as a "Packet Paging Response". + +For that purpose, the GMM layer shall request the establishment of uplink resources. If the LLC frame is *dummy* (i.e. does not convey user data information) and it is short enough, the mobile station shall send it on the main DCCH. Otherwise, an uplink TBF is needed and its establishment shall be done. + +Once the LLC frame is sent, the mobile station moves to the GMM Ready state. The SGSN understands the LLC frame as a valid page response and starts sending the downlink information. In order to forward this information to the mobile station, the BSS shall send a (second) assignment message as soon as it receives the data from the SGSN. + +The procedure is shown in figure 8. + +![Figure 8: Example of a successful establishment of a PS MT session while in dedicated mode, packet idle mode and Standby state](124c6108c63173818afb8ed49521e22d_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC + participant SGSN + Note over MS,MSC: CS dedicated mode + SGSN->>BSS: Paging PS + BSS->>MS: Packet Notification + MS-->BSS: DTM Request + BSS-->MS: Packet Assignment + MS->>SGSN: LLC frame + SGSN->>BSS: DL-Unitdata + BSS->>MS: Packet Assignment + BSS->>MS: RLC block(s) + +``` + +Figure 8: Example of a successful establishment of a PS MT session while in dedicated mode, packet idle mode and Standby state + +**Figure 8: Example of a successful establishment of a PS MT session while in dedicated mode, packet idle mode and Standby state** + +### 6.1.3 CS establishment while in packet transfer mode + +When in packet transfer mode, either the mobile station or the network may initiate a CS connection establishment. In both cases, the packet session may be aborted and the establishment of the CS connection is initiated. + +When the establishment of the CS connection is initiated by the network, the CS paging message may come directly from the MSC or via the SGSN if the Gs interface is present. The BSS shall be able to verify in both cases if the paged mobile station is in packet transfer mode and shall send the CS page on the PACCH. + +NOTE 1: This paging co-ordination can be reused for GPRS mobile stations in mode of operation B, so that the mobile station does not need to listen to the PCH. + +NOTE 2: This feature breaks the link between the presence of the Gs interface and the network capability to perform paging co-ordination. Alignment of 3G TS 23.060 is needed. + +Once on the DCCH, the mobile station may request the re-establishment of the packet resources by sending a DTM Request message. The procedure to re-establish an aborted uplink TBF shall be identical to the MO session request. The procedure to re-establish an aborted downlink TBF shall be identical to the MT session request. + +Figure 9 shows this procedure graphically. + +![Sequence diagram showing the successful establishment of a CS connection while in packet transfer mode. The diagram involves four main entities: MS (Mobile Station), BSS (Base Station System), SGSN (Serving GPRS Support Node), and MSC (Mobile Switching Center). The process starts with a 'PS session in progress' between MS and SGSN. A 'Packet Paging Request' is sent from SGSN to MS (labeled 'MT only'). The MS sends an 'Abort PS session' message. The BSS sends a 'Channel Request' to the MS, which responds with 'Immediate Assignment'. The MS then sends a 'Paging Response (MT) or CM Service Request (MO)' to the BSS. The BSS sends an 'SCCP Connection Request' to the MSC, which responds with 'SCCP Connection Confirm()'. The BSS also sends 'Classmark Change', 'Classmark Update', and 'Common ID (IMSI)' messages to the MSC. The MS sends a 'DTM Request' to the BSS, which triggers 'Authentication, Security and Call Control Procedures' in the MSC. The MSC sends a 'DTM Assignment Command' to the BSS, which in turn sends an 'Assignment Complete' to the MS. The MS sends a 'Channel Mode Modify' message to the BSS, which sends an 'Assignment Request' to the MSC. The MSC responds with 'Assignment Complete' to the BSS, which sends a 'Channel Mode Modify Ack.' to the MS. The diagram ends with a 'Dedicated mode (speech + signalling)' state between MS and MSC.](898fb89a50d9ec1dfb4e425c816976a7_img.jpg) + +Sequence diagram showing the successful establishment of a CS connection while in packet transfer mode. The diagram involves four main entities: MS (Mobile Station), BSS (Base Station System), SGSN (Serving GPRS Support Node), and MSC (Mobile Switching Center). The process starts with a 'PS session in progress' between MS and SGSN. A 'Packet Paging Request' is sent from SGSN to MS (labeled 'MT only'). The MS sends an 'Abort PS session' message. The BSS sends a 'Channel Request' to the MS, which responds with 'Immediate Assignment'. The MS then sends a 'Paging Response (MT) or CM Service Request (MO)' to the BSS. The BSS sends an 'SCCP Connection Request' to the MSC, which responds with 'SCCP Connection Confirm()'. The BSS also sends 'Classmark Change', 'Classmark Update', and 'Common ID (IMSI)' messages to the MSC. The MS sends a 'DTM Request' to the BSS, which triggers 'Authentication, Security and Call Control Procedures' in the MSC. The MSC sends a 'DTM Assignment Command' to the BSS, which in turn sends an 'Assignment Complete' to the MS. The MS sends a 'Channel Mode Modify' message to the BSS, which sends an 'Assignment Request' to the MSC. The MSC responds with 'Assignment Complete' to the BSS, which sends a 'Channel Mode Modify Ack.' to the MS. The diagram ends with a 'Dedicated mode (speech + signalling)' state between MS and MSC. + +NOTE: The IMSI is sent when available at the MSC and if the BSS supports the DTM feature. + +**Figure 9: Successful establishment of a CS connection while in packet transfer mode** + +Upon receiving the ASSIGNMENT REQUEST message from the MSC, the BSS may send one of the following messages to the MS: + +- CHANNEL MODE MODIFY message to modify the existing CS channel's mode, as shown in Figure 9. +- DTM ASSIGNMENT COMMAND message to reallocate the CS resource and maintain some PS resources. +- ASSIGNMENT COMMAND message to reallocate the CS resource and drop the PS resources. + +**Figure 10: void (deleted)** + +If the mobile station and the network support enhanced CS establishment a CS connection may be established while in packet transfer mode, without release of the packet resources. + +A mobile station that supports enhanced CS establishment can determine whether or not the network supports enhanced CS establishment by reading the *GPRS Cell Options* IE included within system information messages (see 3GPP TS 44.018 and 44.060). + +In the mobile-originated case, the MS requests a CS connection by sending the PACKET CS REQUEST message on PACCH to the network. + +If the contention resolution is not solved, the mobile station shall delay the transmission of the PACKET CS REQUEST message until contention resolution is solved. + +If the countdown procedure has been started on all the ongoing uplink TBFs, none of those TBFs is operating in extended uplink TBF mode and there is no downlink TBF in progress, the mobile station may either send the PACKET CS REQUEST message, or may immediately release the ongoing TBF(s) and start an RR connection establishment as specified in 3GPP TS 44.018. + +Upon receipt of the PACKET CS REQUEST message, the network replies to the MS with a PACKET CS COMMAND message on PACCH that encapsulates one of (RR) DTM ASSIGNMENT COMMAND, IMMEDIATE ASSIGNMENT, IMMEDIATE ASSIGNMENT REJECT messages as defined below: + +- The network may allocate both PS and CS resources to the MS by sending a (RR) DTM ASSIGNMENT COMMAND message. When the MS receives this message it starts CS connection establishment and enters dual transfer mode. The network may also reallocate PS resources in the DTM ASSIGNMENT COMMAND message. In this case the resulting channel combination must be TCH + PDTCH, SDCCH + PDTCH is not allowed. By omitting the PS resource description in the DTM ASSIGNMENT COMMAND, the network indicates that the current PS Resources are maintained. +- The network allocates only CS resources to the MS and orders the release of PS resources by sending an (RR) IMMEDIATE ASSIGNMENT message. When the MS receives this message it releases the PS connection and establishes the CS connection. When in dedicated mode the MS may request PS resources by using the procedures specified in 3GPP TS 44.018. +- The network rejects the CS request by sending an (RR) IMMEDIATE ASSIGNMENT REJECT message. When the MS receives this message it continues in packet transfer mode normally. The mobile station may later reinitiate the CS connection request. +- If the PS resources have been dropped before the network has a chance to respond to the PACKET CS REQUEST, the network shall abort the current DTM procedure. If the mobile station does not receive a PACKET CS COMMAND message after it has sent a corresponding PACKET CS REQUEST message, the mobile station will drop any PS resources and start CS access procedures on the RACH. + +If the network and mobile both support the extended RLC/MAC control message segmentation, the network may send the PACKET CS COMMAND message in more than two radio blocks, see 3GPP TS 44.060. If not, the network is responsible for ensuring that the PACKET CS COMMAND does not exceed two radio blocks in length. + +Figure 10a illustrates successful MS originated RR connection request procedure. + +![Sequence diagram of MS originated RR connection request procedure. The diagram shows four entities: MS, BSS, SGSN, and MSC. The MS sends a 'Packet CS request' on the PACCH to the BSS. The BSS sends a 'Packet CS command' on the PACCH back to the MS. Above the request, a 'PS session in progress' is indicated between the MS and the SGSN. Below the command, a 'CS dedicated mode' is indicated between the MS and the MSC.](d79d33da852cb7bca3e87b400a15c3e8_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant SGSN + participant MSC + + Note left of MS: PS session in progress + MS->>BSS: Packet CS request (PACCH) + BSS-->>MS: Packet CS command (PACCH) + Note right of MSC: CS dedicated mode + +``` + +Sequence diagram of MS originated RR connection request procedure. The diagram shows four entities: MS, BSS, SGSN, and MSC. The MS sends a 'Packet CS request' on the PACCH to the BSS. The BSS sends a 'Packet CS command' on the PACCH back to the MS. Above the request, a 'PS session in progress' is indicated between the MS and the SGSN. Below the command, a 'CS dedicated mode' is indicated between the MS and the MSC. + +**Figure 10a: MS originated RR connection request procedure** + +In the mobile-terminated case the BSS sends to the mobile station a PACKET CS COMMAND message on PACCH when receiving a CS paging message from the core network. The PACKET CS COMMAND message encapsulates one of (RR) DTM ASSIGNMENT COMMAND, IMMEDIATE ASSIGNMENT messages as defined below: + +- The network may allocate both PS and CS resources to the MS by sending a (RR) DTM ASSIGNMENT COMMAND message. The network may also reallocate PS resources in the DTM ASSIGNMENT COMMAND message. In this case the resulting channel combination must be TCH + PDTCH, SDCCH + PDTCH is not allowed. By omitting the PS resource description in the DTM ASSIGNMENT COMMAND, the network indicates that the current PS Resources are maintained. +- The network allocates only CS resources to the MS and orders the release of PS resources by sending an (RR) IMMEDIATE ASSIGNMENT message. When the MS receives this message it releases the PS connection and establishes the CS connection. When in dedicated mode the MS may request PS resources by using the procedures specified in 3GPP TS 44.018. + +Figure 10b illustrates successful MS terminated RR connection establishment. + +![Sequence diagram of MS terminated RR connection establishment. The diagram shows four entities: MS, BSS, SGSN, and MSC. The sequence starts with a 'PS session in progress' between MS and SGSN. The MSC sends a 'Paging' message to the SGSN. The SGSN sends a 'BSSAP + Paging request' to the BSS. The BSS sends a 'Paging CS PDU' to the MS. The MS responds with a 'Packet CS command' on the PACCH. Finally, a 'CS dedicated mode' is established between the MS and the MSC.](4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant SGSN + participant MSC + Note left of MS: [PACCH] + MS->>SGSN: PS session in progress + MSC->>SGSN: Paging + SGSN->>BSS: BSSAP + Paging request + BSS->>MS: Paging CS PDU + MS->>BSS: Packet CS command + MS->>MSC: CS dedicated mode + +``` + +Sequence diagram of MS terminated RR connection establishment. The diagram shows four entities: MS, BSS, SGSN, and MSC. The sequence starts with a 'PS session in progress' between MS and SGSN. The MSC sends a 'Paging' message to the SGSN. The SGSN sends a 'BSSAP + Paging request' to the BSS. The BSS sends a 'Paging CS PDU' to the MS. The MS responds with a 'Packet CS command' on the PACCH. Finally, a 'CS dedicated mode' is established between the MS and the MSC. + +Figure 10b: MS terminated RR connection establishment + +### 6.1.4 PS establishment while in dual transfer mode + +Once the mobile station is in dual transfer mode, the establishment of any further packet sessions shall be done with the existent mechanisms (see 3GPP TS44.060 [5]). + +The network may send the DTM Assignment Command message to the mobile station at any time to reallocate one or more ongoing TBFs and the resources required for the RR connection. If the MS receives a DTM Assignment Command message after sending a request for one or more uplink TBFs but before receiving any uplink allocation in response to its request, it shall act on the DTM Assignment Command message and after successful reallocation of resources wait for the response from the network to the uplink TBF request on the newly allocated resources. All ongoing TBFs not addressed by the DTM Assignment Command message are released. + +## 6.2 Release + +### 6.2.1 Release of packet resources + +The release of a TBF shall follow the current procedures in 3GPP TS 44.060 [5]. The use of the main DCCH as a packet resource is stopped when the signalling connection is cleared (during a handover or assignment procedure) or when the mobile station enters the dual transfer mode. + +### 6.2.2 Release of CS resources + +In the case of the release of the CS connection while in dual transfer mode, the mobile station may abandon the packet resources. + +Before the re-establishment of the packet resources, the mobile station may need to read all the relevant information contained in the SI messages that was not sent in the SACCH or the PACCH while in DTM. In order to reduce the + +interruption of the GPRS session at call release, the network sends a new message (PSI 14) on the PACCH when the mobile station is in dual transfer mode. This message contains + +- most of the information in SI 13, if the PBCCH is not allocated; or +- the location of the PBCCH, if this is present. + +If both the mobile station and the network support enhanced CS release, the network may delay the release of the CS connection until the mobile station has received the needed system information, in order to maintain the packet resources after release of the CS connection. The network shall initiate enhanced CS release by sending PACKET CS RELEASE INDICATION message. System information is provided to the mobile station with PACKET SERVING CELL SI message on the PACCH. Packet system information messages can also be sent as such on PACCH. The MS shall use PACKET SI STATUS or PACKET PSI STATUS message to indicate which messages have been received correctly. When the mobile station has received the required set of a system information it informs the network which in turn sends a CS connection release message to the mobile station. Upon release of the CS connection the mobile station enters packet transfer mode. + +If the network is not able to use enhanced CS release (e.g. due to scarce radio resources, no support for enhanced CS release or no possibility to send missing system information) it shall send a CS connection release message to the mobile station indicating the mobile station shall abandon the packet resources after the release of the CS connection. + +Figure 10c shows the exchange of messages when a CS connection is released and the MS maintains PS resources. + +![Sequence diagram showing the release of a CS connection and maintaining PS resources. The diagram involves four entities: MS, BSS, SGSN, and MSC. The sequence starts with 'CS dedicated mode' and 'PS session in progress'. The MSC sends a 'Clear command' to the BSS. The BSS sends a 'Packet CS release indication' to the MS. The MS responds with 'Packet Control acknowledgement', 'Packet (P)SI status', 'Packet serving cell SI', 'PSI messages *', and 'Packet (P)SI status' on the PACCH. Finally, the MS sends a 'Channel release' on the Main DCCH, and the PS session continues. A note indicates that the final step is optional if a packet control channel is supported.](b2ea162a0f53d5e0504b7d28346e0754_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant SGSN + participant MSC + + Note left of MS: CS dedicated mode + Note left of MS: PS session in progress + MSC->>BSS: Clear command + BSS->>MS: Packet CS release indication + MS->>BSS: Packet Control acknowledgement + MS->>BSS: Packet (P)SI status + MS->>BSS: Packet serving cell SI + MS->>BSS: PSI messages * + MS->>BSS: Packet (P)SI status + MS->>BSS: Channel release + Note right of MSC: Optional. If packet control channel is supported. + Note left of MS: PS session in progress + +``` + +Sequence diagram showing the release of a CS connection and maintaining PS resources. The diagram involves four entities: MS, BSS, SGSN, and MSC. The sequence starts with 'CS dedicated mode' and 'PS session in progress'. The MSC sends a 'Clear command' to the BSS. The BSS sends a 'Packet CS release indication' to the MS. The MS responds with 'Packet Control acknowledgement', 'Packet (P)SI status', 'Packet serving cell SI', 'PSI messages \*', and 'Packet (P)SI status' on the PACCH. Finally, the MS sends a 'Channel release' on the Main DCCH, and the PS session continues. A note indicates that the final step is optional if a packet control channel is supported. + +Figure 10c: Release of CS connection and maintaining PS resources + +## 6.3 Handover + +### 6.3.1 General + +Another group of procedures that are affected by the definition a new GPRS class A mode of operation are those related to the change of the serving cell when the mobile station is in dual transfer mode. The term *handover* in this document refers to the network initiated change of serving cell for both domains, unless explicit reference to the CS domain is made. The handover and the cell change of the CS and PS domains respectively need to be performed at the same time. As 3GPP TS 45.008 [7] states, the serving cell for a class A mobile station while it is in dedicated mode "is determined + +by the network according to the handover procedures", irrespective of the Network Control measuring report mode (NC). + +The Handover Command message sent from the network to the mobile station shall describe the CS resources in the target cell. + +The RAI, Cell Identity and information whether DTM is allowed or not shall be sent to a DTM capable mobile station after handover in SI6 and/or the DTM Information message. The RAI needs also to be included in the SI 6 message sent to a DTM capable mobile station that is not in DTM so that it can detect a change of the RA. + +Handover failure cases are determined only from the CS timeslot. In the event of a handover failure, the mobile station shall return to the CS resource in the old cell and send a Handover Failure message on the main DCCH. If the mobile station is in GMM Ready state, it shall then perform the Cell Update procedure in order to notify the SGSN that downlink data flows can be continued in the source cell. The mobile station shall assume that all the packet resources were released during the handover and it shall try to re-establish the uplink resources if there is uplink data ready to be sent. + +Once the main DCCH is established in the cell, the network sends the DTM Information message. This message contains: + +- the RAI and Cell Identity of the new cell: to detect changes of RA or cell without waiting for the SI 6 message; +- the length limitation for the use of the main DCCH. + +Then the mobile station or the network may re-establish the packet resource(s). + +### 6.3.1a DTM Handover – General + +The term *DTM Handover* in this document always refers to the network initiated change of serving cell for both CS and PS domains, using DTM Handover procedures. + +The source and target cells may be managed by either the same BSS (Intra-BSS) or different BSSs (Inter-BSS) within the same MSC (Intra-MSC) and the same SGSN (Intra SGSN) or different SGSNs (Inter SGSN) or different MSCs (Inter-MSC) and the same or different SGSNs. The DTM Handover in *A/Gb mode* makes use of existing CS handover procedures and PS Handover procedures. Unless explicitly stated in the present document, the behaviour of the core network entities is as specified for the respective handover procedures. The DTM Handover procedure is controlled by the RR protocol. + +The DTM Handover procedure is divided into: + +- a preparation phase including the allocation of CS and PS resources in the target cell, consisting of parallel CS handover preparation phase as described in 3GPP TS 23.009 [14] and PS handover preparation phase as described in 3GPP TS 43.129 [13]; and +- an execution phase which includes the sending of the (RR) DTM HANDOVER COMMAND message from the network to the mobile station on PACCH. The (RR) DTM HANDOVER COMMAND message shall describe both the CS and the PS resources in the target cell. + +In the case of a DTM Handover into a network sharing supporting target cell by a MS supporting network sharing, the DTM HANDOVER COMMAND shall include PLMN index information which, upon arriving in the target cell, the MS uses as described in 3GPP TS 44.018 [5]. + +### 6.3.2 Internal handover + +The network may send a Handover Command message requesting the mobile station to switch to a different cell parented by the same BSC. Prior to that, the BSC shall activate the channels in the target cell. At the receipt of the Handover Command message the mobile station shall abandon the packet session and initiate the access on the target cell, obeying the handover time requirements of 3GPP TS 45.010 [8] clause 6 and 3GPP TS 44.013 [3] clause 5.2.6. + +The re-establishment of the CS connection shall continue as a CS only handover. When concluded, the BSC shall release the channels in the old cell. + +The network immediately sends the DTM Information message, with information needed to resume the GPRS operation in the new cell. Once the mobile station has the necessary information, it shall perform a cell update or RA update procedure. + +If the mobile station also needs to (re-)establish an uplink packet session in the new cell, the GMM signalling procedure shall take precedence and shall be performed first. Once the update procedure is performed, the (re-)establishment of the packet session may continue. + +Figure 11 shows the exchange of messages in a successful internal handover. + +![Sequence diagram of a successful internal, dual handover procedure involving MS, Old BTS, New BTS, BSC, MSC, and SGSN.](7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg) + +The sequence diagram illustrates the message exchange for a successful internal, dual handover procedure. The participants are MS (Mobile Station), Old BTS (Base Transceiver Station), New BTS, BSC (Base Station Controller), MSC (Mobile Switching Center), and SGSN (Serving GPRS Support Node). + +The sequence of messages is as follows: + +- CS Call**: A horizontal bar indicating an active circuit-switched call between the MS and the MSC. +- PS Session**: A horizontal bar indicating an active packet-switched session between the MS and the SGSN. +- Channel Activation**: The New BTS sends a message to the BSC. +- Channel Activation Ack**: The BSC responds to the New BTS. +- Channel Activation**: The New BTS sends another message to the BSC. +- Channel Activation Ack**: The BSC responds again. +- Handover Command**: The BSC sends a command to the MS. +- Handover Access**: The MS responds to the BSC. +- Physical Information**: The MS sends information to the BSC. +- Signalling link establishment**: A sub-procedure between the MS and the New BTS. +- Handover Complete**: The MS sends a completion message to the BSC. +- Handover Complete**: The BSC sends a completion message to the Old BTS. +- Handover Performed**: The BSC sends a confirmation to the MSC. +- RF Channel Release**: The Old BTS sends a release message to the BSC. +- RF Channel Release Ack**: The BSC responds. +- RF Channel Release**: The Old BTS sends another release message. +- RF Channel Release Ack**: The BSC responds again. +- CS Call**: A horizontal bar indicating the continued CS call between the MS and the MSC. +- SI 6 / DTM Information**: The MSC sends information to the BSC. +- DTM Request**: The BSC sends a request to the MS. +- Packet Assignment**: The MS responds to the BSC. +- Cell Update or RA Update procedure**: A sub-procedure between the MS and the SGSN. +- PS Session**: A horizontal bar indicating the continued PS session between the MS and the SGSN. + +Sequence diagram of a successful internal, dual handover procedure involving MS, Old BTS, New BTS, BSC, MSC, and SGSN. + +Figure 11: Successful internal, dual handover procedure + +### 6.3.2a Intra-BSS DTM Handover + +#### 6.3.2a.1 General + +The Intra-BSS DTM Handover procedure covers the scenarios where the source and target cells are managed by the same BSS, the same MSC and the same SGSN. The Intra-BSS with MSC involved or MSC not involved DTM Handover procedures may use the optimized PS Handover procedure (see 3GPP TS 43.129) if allowed. + +The Intra-BSS inter-cell DTM Handover using optimized PS Handover procedure and MSC non-involved case and Intra-BSS inter-cell DTM Handover using non-optimized PS Handover procedure and MSC involved case are described in sub-clauses 6.3.2a.2, 6.3.2a.3 and 6.3.2a.4. + +The Intra-BSS inter-cell DTM Handover using optimized PS Handover procedure and MSC involved case and Intra-BSS inter-cell DTM Handover using non-optimized PS Handover procedure and MSC not involved case are not explicitly described in the current document as they are considered to be implicitly covered by the cases that are described. + +#### 6.3.2a.2 Preparation Phase – using Optimized PS Handover procedure and without MSC involved + +The preparation phase consists of the BSS allocating CS and PS resources in the target cell. The BSS shall select the same unique target cell for both the CS and the PS domains. The BSS shall activate the DTM channel configurations (CS channel and PS resources) in the target cell. + +#### 6.3.2a.3 Preparation Phase – using Non-Optimized PS Handover procedure and with MSC involved + +The preparation phase consists of the BSS sending a (BSSMAP) HANDOVER REQUIRED message to the MSC and a (BSSGP) PS HANDOVER REQUIRED PDU to the SGSN and allocating CS and PS resources in the target cell upon receiving a (BSSMAP) HANDOVER REQUEST message from the MSC and a (BSSGP) PS HANDOVER REQUEST PDU from the SGSN. The BSS shall select the same unique target cell for both the CS and the PS domains. The handling of the messages between BSS and CN is largely based on the Inter-BSS DTM Handover as described in section 6.3.3a. + +#### 6.3.2a.4 Execution Phase + +In case of Intra-BSS DTM Handover using the optimised PS Handover procedure and without the MSC involved, the BSS may start the execution phase by sending a (RLC/MAC) DTM HANDOVER COMMAND message to the mobile station on the PACCH requesting it to perform a DTM Handover and switch to a different cell managed by the same BSS. + +In case of Intra-BSS DTM Handover using the non-optimised PS Handover procedure and with the MSC involved, the BSS may start the execution phase after receiving the (BSSMAP) HANDOVER COMMAND message from the MSC and the (BSSGP) PS HANDOVER REQUIRED ACK PDU from the SGSN. + +At the receipt of the (RLC/MAC) DTM HANDOVER COMMAND message the mobile station switches to the new configuration and initiates the access on the target cell using the existing CS handover access procedures. + +After successful establishment of the main signalling link in the target cell, the mobile station sends the (RR) HANDOVER COMPLETE message to the BSS which in turns sends either a (BSSMAP) HANDOVER PERFORMED message (in case of MSC not involved) or a (BSSMAP) HANDOVER COMPLETE message (in case of MSC involved) to the MSC and a (BSSGP) PS HANDOVER COMPLETE PDU to the SGSN (regardless of whether or not optimised PS Handover was used) to indicate the completion of the Intra-BSS DTM Handover. Upon successful completion of the Intra-BSS DTM Handover, the BSS releases the DTM channel configurations (i.e. CS channel and PS resources) in the old cell. + +During Intra-BSS with MSC involved DTM Handover using non-optimized PS Handover procedures, the mobile station shall start the Cell/RA Update procedure immediately after sending the (RR) HANDOVER COMPLETE message to the network. + +If the mobile station is not able to act on or decode the (RLC/MAC) DTM HANDOVER COMMAND message, it sends a (RR) HANDOVER FAILURE message to the network on the main DCCH of the source cell. + +If the mobile station acts on the (RLC/MAC) DTM HANDOVER COMMAND message but fails to establish the main signalling link in the target cell, the MS returns to the old channels in the source cell and sends a (RR) HANDOVER FAILURE message to the network on the main DCCH. + +In case the responses received by the BSS do not consist of the combination of both a (BSSMAP) HANDOVER COMMAND message and a (BSSGP) PS HANDOVER REQUIRED ACK PDU, the Intra-BSS DTM Handover using non-optimized PS handover and with MSC involved fails and the BSS and the mobile station proceed as per the Inter-BSS DTM Handover described in section 6.3.3a.3 + +Figure 11a shows the exchange of messages in a successful inter-cell Intra-BSS DTM Handover using optimized PS Handover procedure and MSC not involved case. + +Figure 11b and Figure 11c show the exchange of messages in a successful inter-cell Intra-BSS DTM Handover using non-optimized PS Handover procedure and MSC involved scenario. + +![Sequence diagram for Figure 11a: Intra-BSS with MSC not involved DTM Handover using optimized PS Handover procedures. The diagram shows the interaction between MS, Old BTS, New BTS, BSC, MSC, and SGSN. The process starts with CS Call and PS Session. The BSS determines if the new cell is part of the same NSE and same RA. CS and PS resources are allocated. Channel Activation is performed. DTm HANDOVER COMMAND is sent to the MS. Access in the target cell and Signaling link establishment are performed. HANDOVER COMPLETE is sent to the BSC. HANDOVER PERFORMED is sent to the MSC. PS HANDOVER COMPLETE is sent to the SGSN. First RLC/MAC data block is sent. Channel Release is performed. CS and PS Sessions continue.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +``` + +sequenceDiagram + participant MS + participant OldBTS as Old BTS + participant NewBTS as New BTS + participant BSC + participant MSC + participant SGSN + + Note left of MS: CS Call + Note left of MS: PS Session + Note right of NewBTS: BSS determines if the new cell is part of the same NSE and same RA + Note right of NewBTS: CS and PS resources allocation + Note right of NewBTS: Channel Activation + BSC->>MS: DTm HANDOVER COMMAND + Note left of MS: Access in the target cell + Note left of MS: Signaling link establishment + MS->>BSC: HANDOVER COMPLETE + BSC->>MSC: HANDOVER PERFORMED + BSC->>SGSN: PS HANDOVER COMPLETE + Note left of MS: First RLC/MAC data block + Note right of OldBTS: Channel Release + Note left of MS: CS and PS Sessions continue + +``` + +Sequence diagram for Figure 11a: Intra-BSS with MSC not involved DTM Handover using optimized PS Handover procedures. The diagram shows the interaction between MS, Old BTS, New BTS, BSC, MSC, and SGSN. The process starts with CS Call and PS Session. The BSS determines if the new cell is part of the same NSE and same RA. CS and PS resources are allocated. Channel Activation is performed. DTm HANDOVER COMMAND is sent to the MS. Access in the target cell and Signaling link establishment are performed. HANDOVER COMPLETE is sent to the BSC. HANDOVER PERFORMED is sent to the MSC. PS HANDOVER COMPLETE is sent to the SGSN. First RLC/MAC data block is sent. Channel Release is performed. CS and PS Sessions continue. + +Figure 11a: Intra-BSS with MSC not involved DTm Handover using optimized PS Handover procedures + +![Sequence diagram for Figure 11b: Intra-BSS with MSC involved DTm Handover using non-optimized PS Handover procedures, preparation phase. The diagram shows the interaction between MS, Old BTS, New BTS, BSC, MSC, and SGSN. The process starts with CS Call and PS Session. The BSC sends HANDOVER REQUIRED to the MSC. The MSC sends PS HANDOVER REQUIRED to the SGSN. The MSC sends HANDOVER REQUEST to the BSC. The BSC sends PS HANDOVER REQUEST to the SGSN. CS and PS resources are allocated. Channel Activation is performed. The BSC sends HANDOVER REQUEST ACKNOWLEDGE to the MSC. The MSC sends PS HANDOVER REQUEST ACK to the SGSN.](e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg) + +``` + +sequenceDiagram + participant MS + participant OldBTS as Old BTS + participant NewBTS as New BTS + participant BSC + participant MSC + participant SGSN + + Note left of MS: CS Call + Note left of MS: PS Session + BSC->>MSC: HANDOVER REQUIRED + MSC->>SGSN: PS HANDOVER REQUIRED + MSC->>BSC: HANDOVER REQUEST + BSC->>SGSN: PS HANDOVER REQUEST + Note right of NewBTS: CS and PS resources allocation + Note right of NewBTS: Channel Activation + BSC->>MSC: HANDOVER REQUEST ACKNOWLEDGE + MSC->>SGSN: PS HANDOVER REQUEST ACK + +``` + +Sequence diagram for Figure 11b: Intra-BSS with MSC involved DTm Handover using non-optimized PS Handover procedures, preparation phase. The diagram shows the interaction between MS, Old BTS, New BTS, BSC, MSC, and SGSN. The process starts with CS Call and PS Session. The BSC sends HANDOVER REQUIRED to the MSC. The MSC sends PS HANDOVER REQUIRED to the SGSN. The MSC sends HANDOVER REQUEST to the BSC. The BSC sends PS HANDOVER REQUEST to the SGSN. CS and PS resources are allocated. Channel Activation is performed. The BSC sends HANDOVER REQUEST ACKNOWLEDGE to the MSC. The MSC sends PS HANDOVER REQUEST ACK to the SGSN. + +Figure 11b: Intra-BSS with MSC involved DTm Handover using non-optimized PS Handover procedures, preparation phase + +![Sequence diagram for Intra-BSS with MSC involved DTM Handover using non-optimized PS Handover procedures, execution phase. The diagram shows the interaction between MS, Old BTS, New BTS, BSC, MSC, and SGSN. It starts with CS Call and PS Session. The BSC sends a HANDOVER COMMAND to the MS. The MS responds with DT M HANDOVER COMMAND. The MS then performs 'Access in the target cell' and 'Signaling link establishment'. The MS sends a HANDOVER COMPLETE message to the BSC. The BSC sends a HANDOVER COMPLETE message to the MSC. The MSC sends a Cell/RA Update to the MS. The MS sends a First RLC/MAC data block to the BSC. The BSC sends a PS HANDOVER COMPLETE message to the SGSN. The BSC sends a Channel Release message to the MS. Finally, the MS sends a CS and PS Sessions continue message to the BSC.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +``` + +sequenceDiagram + participant MS + participant OldBTS as Old BTS + participant NewBTS as New BTS + participant BSC + participant MSC + participant SGSN + + Note left of MS: CS Call + Note left of MS: PS Session + BSC->>MS: HANDOVER COMMAND + MS->>OldBTS: DT M HANDOVER COMMAND + Note left of MS: Access in the target cell + Note left of MS: Signaling link establishment + MS->>BSC: HANDOVER COMPLETE + BSC->>MSC: HANDOVER COMPLETE + MSC->>MS: Cell/RA Update + MS->>BSC: First RLC/MAC data block + BSC->>SGSN: PS HANDOVER COMPLETE + BSC->>MS: Channel Release + Note left of MS: CS and PS Sessions continue + +``` + +Sequence diagram for Intra-BSS with MSC involved DTM Handover using non-optimized PS Handover procedures, execution phase. The diagram shows the interaction between MS, Old BTS, New BTS, BSC, MSC, and SGSN. It starts with CS Call and PS Session. The BSC sends a HANDOVER COMMAND to the MS. The MS responds with DT M HANDOVER COMMAND. The MS then performs 'Access in the target cell' and 'Signaling link establishment'. The MS sends a HANDOVER COMPLETE message to the BSC. The BSC sends a HANDOVER COMPLETE message to the MSC. The MSC sends a Cell/RA Update to the MS. The MS sends a First RLC/MAC data block to the BSC. The BSC sends a PS HANDOVER COMPLETE message to the SGSN. The BSC sends a Channel Release message to the MS. Finally, the MS sends a CS and PS Sessions continue message to the BSC. + +**Figure 11c: Intra-BSS with MSC involved DTM Handover using non-optimized PS Handover procedures, execution phase** + +### 6.3.3 External handover + +In the case of an external handover, the target BSS: + +- shall be provided with the IMSI of the mobile station; +- shall be provided with information about the nature of the packet resources in the serving cell, so that the CS resource is compatible with the packet resources that are going to be requested in the new cell (e.g. transceiver supporting AMR or EDGE, timeslot with a free, adjacent one). This information is conveyed in the Old BSS to New BSS Information IE. + +**NOTE:** This indication that the MS is in DTM in the source cell is also included in the handover to GERAN from another RAT when the MS has resources in the source cell allocated towards the CS and PS domains simultaneously. + +No changes are foreseen for an inter-MSC handover. Current implementations are expected to be able to carry the extended Old BSS to New BSS Information IE without modifications to 3GPP TS 49.008. + +No changes are foreseen for an inter-SGSN handover. The mobile shall perform a Routing Area Update procedure in the new cell. This may be as a result of the SI 6 contents (RAC is now added) or caused by information contained in the DTM INFORMATION message. + +### 6.3.3a Inter-BSS DTM Handover + +#### 6.3.3a.1 General + +The Inter-BSS DTM Handover procedure covers the scenarios where the source and target cells are managed by different BSSs. All four cases of Intra-/Inter-MSC and Intra-/Inter-SGSN handovers use these procedures. + +The Inter-BSS DTM Handover is initiated by the source BSS sending a (BSSMAP) HANDOVER REQUIRED message and a (BSSGP) PS HANDOVER REQUIRED PDU to the MSC and the SGSN respectively. The Inter-BSS DTM Handover requires synchronization of the handovers in the CS and the PS domains in both the source BSS and the target BSS through: + +- Selection of the same unique target cell for both the CS and the PS domains. In the preparation phase the source BSS selects the same target cell ID for both the CS and the PS domains and indicates it to the MSC and the SGSN in the (BSSMAP) HANDOVER REQUIRED message and (BSSGP) PS HANDOVER REQUIRED PDU respectively. +- Indications to the target BSS that the CS (respectively PS) handover is ongoing at the same time as the PS (respectively CS) handover for the same mobile station (see Figure 11d). These indications require the target BSS to wait for both the (BSSMAP) HANDOVER REQUEST message and (BSSGP) PS HANDOVER REQUEST PDU. +- *PS Indication IE* is sent in the (BSSMAP) HANDOVER REQUIRED message and (BSSMAP) HANDOVER REQUEST message within the Old BSS to New BSS information. +- *CS Indication IE* is sent in the (BSSGP) PS HANDOVER REQUIRED PDU and (BSSGP) PS HANDOVER REQUEST PDU within the Source BSS to Target BSS transparent container. +- Management of synchronization timers in both the source BSS and the target BSS that ensure the target receives both PS and CS domain resource allocation requests and the source BSS receives both PS and CS domain resource allocation responses from the target BSS before proceeding with the Inter-BSS DTM Handover. + +#### 6.3.3a.2 Preparation Phase + +The Inter-BSS DTM Handover is initiated by the source BSS by sending a (BSSMAP) HANDOVER REQUIRED message and a (BSSGP) PS HANDOVER REQUIRED PDU to the MSC and the SGSN respectively. + +The target BSS, upon reception of a (BSSMAP) HANDOVER REQUEST message (respectively (BSSGP) PS HANDOVER REQUEST PDU) containing an indication of an ongoing PS handover (respectively CS handover) as described in sub-clause 6.3.3a.1, waits for reception of the corresponding (BSSGP) PS HANDOVER REQUEST PDU (respectively (BSSMAP) HANDOVER REQUEST message). + +If the target BSS receives a (BSSMAP) HANDOVER REQUEST message containing an indication of an ongoing PS handover, but does not receive a corresponding (BSSGP) PS HANDOVER REQUEST PDU within the expected time frame, the target BSS may proceed with allocating a CS resource only, in which case it returns a (BSSMAP) HANDOVER REQUEST ACKNOWLEDGE message containing a (RR) HANDOVER COMMAND message (within the L3 Information IE). Otherwise, if target BSS decides not to continue with the handover of a CS resource it returns a (BSSMAP) HANDOVER FAILURE message to the MSC. If the target BSS receives the corresponding (BSSGP) PS HANDOVER REQUEST PDU containing an indication of an ongoing CS handover after the expected time frame, it shall return a (BSSGP) PS HANDOVER REQUEST NACK PDU to the SGSN. + +If the target BSS receives a (BSSGP) PS HANDOVER REQUEST PDU containing an indication of an ongoing CS handover, but does not receive a corresponding (BSSMAP) HANDOVER REQUEST message within the expected time frame, it shall return a (BSSGP) PS HANDOVER REQUEST NACK PDU to the SGSN and abort the DTM Handover. If the target BSS receives the corresponding (BSSMAP) HANDOVER REQUEST message containing an indication of an ongoing PS handover after the expected time frame, it shall return a (BSSMAP) HANDOVER FAILURE message to the MSC. + +If the target BSS receives both a (BSSGP) PS HANDOVER REQUEST PDU and a (BSSMAP) HANDOVER REQUEST message within the expected time frame and is able to allocate both the CS and PS resources, it returns a (BSSMAP) HANDOVER REQUEST ACKNOWLEDGE message to the MSC and a (BSSGP) PS HANDOVER REQUEST ACK PDU to the SGSN. Both these messages contain the same (RLC/MAC) DTM HANDOVER COMMAND message. + +If the target BSS receives both a (BSSGP) PS HANDOVER REQUEST PDU and a (BSSMAP) HANDOVER REQUEST message within the expected time frame and allocates a CS resource but is unable to or chooses not to allocate any of the corresponding PS resources, it returns a (BSSGP) PS HANDOVER REQUEST NACK PDU to the SGSN. The target BSS may continue with the CS handover in which case it returns a (BSSMAP) HANDOVER REQUEST ACKNOWLEDGE message containing a (RR) HANDOVER COMMAND message (within the L3 Information IE). Otherwise, if the target BSS decides not to continue with the CS handover it returns a (BSSMAP) HANDOVER FAILURE message to the MSC. + +If the target BSS receives both a (BSSGP) PS HANDOVER REQUEST PDU and a (BSSMAP) HANDOVER REQUEST message within the expected time frame but is unable to or chooses not to allocate a CS resource, it shall not allocate the corresponding PS resources. The target BSS returns a (BSSMAP) HANDOVER FAILURE message and a (BSSGP) PS HANDOVER REQUEST NACK PDU to the MSC and the SGSN respectively. + +Figure 11d shows the exchange of messages in a successful Inter-BSS Intra-MSC Intra-SGSN DTM Handover, preparation phase. The same procedures are also used for an Inter-BSS Inter-MSC handover and/or Inter-SGSN DTM Handover. + +![Sequence diagram for Figure 11d: Inter-BSS DTM Handover, preparation phase. The diagram shows the interaction between S-BSS, T-BSS, MSC, and SGSN. It starts with CS Call and PS Session messages. The handover process begins with HANDOVER REQUIRED from S-BSS to MSC, followed by PS HANDOVER REQUIRED from S-BSS to SGSN. The MSC sends HANDOVER REQUEST to T-BSS, which responds with HANDOVER REQUEST ACKNOWLEDGE and Layer 3 Information (DTM HANDOVER COMMAND). The MSC then sends PS HANDOVER REQUEST to SGSN, which responds with PS HANDOVER REQUEST ACK and Target BSS to Source BSS Transparent Container (DTM HANDOVER COMMAND). A note indicates that T-BSS allocates CS and PS resources.](f0a97d0d3818a253c1d2a009966081b1_img.jpg) + +``` + +sequenceDiagram + participant S-BSS + participant T-BSS + participant MSC + participant SGSN + + Note left of S-BSS: CS Call + Note left of S-BSS: PS Session + + S-BSS->>MSC: HANDOVER REQUIRED +Old BSS to New BSS Information ( PS Indication IE ) + S-BSS->>SGSN: PS HANDOVER REQUIRED + MSC->>T-BSS: HANDOVER REQUEST +Container ( CS Indication IE ) + T-BSS-->>MSC: HANDOVER REQUEST ACKNOWLEDGE +Layer 3 Information ( DTM HANDOVER COMMAND ) + MSC->>SGSN: PS HANDOVER REQUEST +Source BSS to Target BSS Transparent Container ( CS Indication IE ) + SGSN-->>MSC: PS HANDOVER REQUEST ACK +Target BSS to Source BSS Transparent Container ( DTM HANDOVER COMMAND ) + + Note right of T-BSS: T-BSS allocates CS and PS resources + +``` + +Sequence diagram for Figure 11d: Inter-BSS DTM Handover, preparation phase. The diagram shows the interaction between S-BSS, T-BSS, MSC, and SGSN. It starts with CS Call and PS Session messages. The handover process begins with HANDOVER REQUIRED from S-BSS to MSC, followed by PS HANDOVER REQUIRED from S-BSS to SGSN. The MSC sends HANDOVER REQUEST to T-BSS, which responds with HANDOVER REQUEST ACKNOWLEDGE and Layer 3 Information (DTM HANDOVER COMMAND). The MSC then sends PS HANDOVER REQUEST to SGSN, which responds with PS HANDOVER REQUEST ACK and Target BSS to Source BSS Transparent Container (DTM HANDOVER COMMAND). A note indicates that T-BSS allocates CS and PS resources. + +**Figure 11d: Inter-BSS DTM Handover, preparation phase** + +#### 6.3.3a.3 Execution Phase + +If the source BSS receives both a (BSSGP) PS HANDOVER REQUIRED ACK PDU and a (BSSMAP) HANDOVER COMMAND message within the expected time frame, it sends the (RLC/MAC) DTM HANDOVER COMMAND message to the mobile station. + +The source BSS may instead send the (RLC/MAC) DTM HANDOVER COMMAND message to the mobile station as soon as it has received a (BSSMAP) HANDOVER COMMAND message which contains the (RLC/MAC) DTM HANDOVER COMMAND message. + +**NOTE:** In this case, it is possible that the PS resources in the target cell which are described in the (RLC/MAC) DTM HANDOVER COMMAND message will not be valid when the MS performs access in the target cell. + +If the source BSS receives from the MSC a (BSSMAP) HANDOVER COMMAND message containing a (RR) HANDOVER COMMAND message it may choose to proceed with the CS handover immediately by stopping the synchronisation timer and sending the contents of the L3 Information IE (i.e. the (RR) HANDOVER COMMAND message) to the mobile station. If the source BSS chooses not to proceed with the CS handover, it sends a (BSSMAP) HANDOVER FAILURE message to the MSC and nothing is sent to the mobile station. + +If the source BSS receives a (BSSMAP) HANDOVER COMMAND message containing a (RLC/MAC) DTM HANDOVER COMMAND message and a (BSSGP) PS HANDOVER REQUIRED NACK PDU within the expected time frame, and the failure cause in (BSSGP) PS HANDOVER REQUIRED NACK PDU indicates an SGSN failure, the source BSS shall abort both the CS and PS handovers and send a (BSSMAP) HANDOVER FAILURE message to the MSC and nothing is sent to the mobile station. + +If the source BSS receives a (BSSMAP) HANDOVER REQUIRED REJECT message and a (BSSGP) PS HANDOVER REQUIRED ACK PDU within the expected time frame, it shall abort the PS handover by sending a (BSSGP) PS HANDOVER CANCEL PDU to the SGSN and nothing is sent to the mobile station. + +If the source BSS receives both a (BSSMAP) HANDOVER REQUIRED REJECT message and a (BSSGP) PS HANDOVER REQUIRED NACK PDU then the DTM Handover fails and nothing is sent to the mobile station. + +On the receipt of the (RLC/MAC) DTM HANDOVER COMMAND message the mobile station switches to the new configuration and initiates the access on the target cell using the existing CS handover access procedures. After successful establishment of the main signalling link in the target cell, the mobile station sends the (RR) HANDOVER COMPLETE message to the target BSS which in turns sends both a (BSSMAP) HANDOVER COMPLETE message to the MSC and a (BSSGP) PS HANDOVER COMPLETE PDU to the SGSN to indicate the completion of the handover. Thereafter the release of the old DTM channel configurations (CS channel and PS resources) is initiated by the MSC and the SGSN respectively. + +The mobile station shall start the Cell/RA Update procedure immediately after sending the (RR) HANDOVER COMPLETE message to the network. + +If the mobile station is not able to act on or decode the (RLC/MAC) DTM HANDOVER COMMAND message, it sends a (RR) HANDOVER FAILURE message to the network on the main DCCH of the source cell. + +If the mobile station fails to establish the main signalling link in the target cell, the MS returns to the old channels in the source cell and sends a (RR) HANDOVER FAILURE message to the network on the main DCCH. + +If the source BSS receives a (RR) HANDOVER FAILURE message from the mobile station, it cancels the current DTM Handover by sending a (BSSMAP) HANDOVER FAILURE message and a (BSSGP) PS HANDOVER CANCEL PDU to the MSC and SGSN respectively. + +Figure 11e shows the exchange of messages in a successful Inter-BSS Intra-MSC Intra-SGSN DTM Handover, execution phase. The same procedures are also used for an inter-MSC handover and/or inter-SGSN DTM Handover. + +![Sequence diagram of Inter-BSS DTM Handover, execution phase. Lifelines: MS, S-BSS, T-BSS, MSC, SGSN. The sequence shows the flow of messages including HANDOVER COMMAND, L3 Information, PS HANDOVER REQUIRED ACK, DTM HANDOVER COMMAND, Access in the target cell, Signaling link establishment, HANDOVER COMPLETE, Cell / RA Update, PS HANDOVER COMPLETE, First valid RLC / MAC block, and CS and PS sessions continue.](cad89c017c9e7c1785bcd104fde4e737_img.jpg) + +``` + +sequenceDiagram + participant MS + participant S-BSS + participant T-BSS + participant MSC + participant SGSN + + MSC->>S-BSS: HANDOVER COMMAND + S-BSS->>MS: L3 Information (DTM HANDOVER COMMAND) + MSC->>SGSN: PS HANDOVER REQUIRED ACK + SGSN-->>MSC: (DTM HANDOVER COMMAND) + MSC->>S-BSS: Target BSS to Source BSS Transparent Container + S-BSS->>MS: DTM HANDOVER COMMAND + Note right of MS: Access in the target cell + Note right of MS: Signaling link establishment + MS->>T-BSS: HANDOVER COMPLETE + T-BSS->>MSC: HANDOVER COMPLETE + Note right of MSC: Cell / RA Update + T-BSS->>SGSN: PS HANDOVER COMPLETE + T-BSS->>MS: First valid RLC / MAC block + Note right of MS: CS and PS sessions continue + +``` + +Sequence diagram of Inter-BSS DTM Handover, execution phase. Lifelines: MS, S-BSS, T-BSS, MSC, SGSN. The sequence shows the flow of messages including HANDOVER COMMAND, L3 Information, PS HANDOVER REQUIRED ACK, DTM HANDOVER COMMAND, Access in the target cell, Signaling link establishment, HANDOVER COMPLETE, Cell / RA Update, PS HANDOVER COMPLETE, First valid RLC / MAC block, and CS and PS sessions continue. + +**Figure 11e: Inter-BSS DTM Handover, execution phase** + +### 6.3.4 Inter-RAT DTM Handover + +#### 6.3.4.1 General + +The Inter-RAT DTM Handover refers only to the DTM Handover performed between GERAN A/Gb mode and UTRAN. The inter-RAT DTM handover from GERAN A/Gb mode to E-UTRAN according to the DTM handover principles is not feasible as there is no CS domain support in E-UTRAN. The handover from E-UTRAN to GERAN DTM is described in 3GPP TS23.216 [19]. + +The source and target cells may be managed by either the GERAN BSS or the UTRAN RNC. The BSS and RNC may be within the same MSC (Intra-MSC) and the same SGSN (Intra SGSN) or different SGSNs (Inter SGSN) or different MSCs (Inter-MSC). + +The Inter-RAT DTM Handover between GERAN *A/Gb mode* and UTRAN makes use of existing Inter-RAT CS Handover procedures and Inter-RAT PS Handover procedures. Unless explicitly stated in the present document, the behaviour of the core network entities is as specified for the respective handover procedures. The Inter-RAT DTM Handover procedure is controlled by the RR protocol in GERAN *A/Gb mode* and the RRC protocol in UTRAN. + +The Inter-RAT DTM Handover procedure is divided into: + +- a preparation phase including the allocation of CS and PS resources in the target cell, consisting of parallel Inter-RAT CS handover preparation phase as described in 3GPP TS 23.009 [14] and Inter-RAT PS handover preparation phase as described in 3GPP TS 43.129 [13]; and +- an execution phase which includes the sending of a (RRC) HANDOVER FROM UTRAN COMMAND message containing a (RLC/MAC) DTM HANDOVER COMMAND message from the network to the mobile station for Inter-RAT DTM Handover procedure from UTRAN to GERAN *A/Gb mode* or the sending of a (RLC/MAC) DTM HANDOVER COMMAND message containing a (RRC) HANDOVER TO UTRAN COMMAND message for the Inter-RAT DTM Handover from GERAN *A/Gb mode* to UTRAN. The (RLC/MAC) DTM HANDOVER COMMAND message and the (RRC) HANDOVER TO UTRAN COMMAND message shall describe both the CS and PS resources in the target cell. + +Unless explicitly stated otherwise in the present document, the Inter-RAT DTM Handover procedure follows the Inter BSS DTM Handover procedure defined in sub-clause 6.3.3a and the UTRAN-UTRAN SRNS Relocation procedure (for two signaling connections) as defined in 3GPP TS 25.413 [16]. The correspondence between the messages/PDUs/IEs used over RANA P [16] and BSSMAP [17]/BSSGP [18] is described in Tables 2a, 2b, 2c and 2d. + +**Table 2a. Messages/PDUs/IEs exchanged between network nodes in the direction from the source BSS/RNC to the target BSS/RNC** + +| → | | Target BSS | Target RNC | MSC | SGSN | +|-------------------|----|----------------------------------------------------------------|-------------------------------------------------------------|---------------------|----------------------| +| Source BSS | CS | Old BSS to New BSS Information IE (see Note 1) | Source RNC to Target RNC Transparent Container (see Note 1) | Handover Required | N/A | +| | PS | Source BSS to Target BSS Transparent Container IE (see Note 1) | | N/A | PS Handover Required | +| MSC | CS | Handover Request | Relocation Request | N/A | N/A | +| SGSN | PS | PS Handover Request | Relocation Request | N/A | N/A | +| Source RNC | CS | Old BSS to New BSS Information IE (see Note 1) | Source RNC to Target RNC Transparent Container (See Note 1) | Relocation Required | N/A | +| | PS | Source BSS to Target BSS Transparent Container IE (see Note 1) | | N/A | Relocation Required | + +NOTE 1: This is an Information Element exchanged between a source BSS/RNC and a target BSS/RNC through the Core Network + +**Table 2b. Messages/PDUs/IEs exchanged between network nodes in the direction from the target BSS/RNC to the source BSS/RNC** + +| → | | Source BSS | Source RNC | MSC | SGSN | +|-------------------|----|-----------------------------------------------------------------------|------------------------------------------------------|---------------------------------------------------------|---------------------------------------------------------| +| Target BSS | CS | Layer 3 Information IE (see Note 1)
N/A | | Handover Request
Acknowledge
Handover Failure | N/A | +| | PS | Target BSS to Source BSS Transparent Container IE (see Note 1)
N/A | | N/A | PS Handover Request ACK
PS Handover Request NACK | +| MSC | CS | Handover Command
Handover Required Reject | Relocation Command
Relocation Preparation Failure | N/A | N/A | +| SGSN | PS | PS Handover Required ACK
PS Handover Required NACK | Relocation Command
Relocation Preparation Failure | N/A | N/A | +| Target RNC | CS | Target RNC to Source RNC Transparent Container IE (see Note 1)
N/A | | Relocation Request
Acknowledge
Relocation Failure | N/A | +| | PS | Target RNC to Source RNC Transparent Container IE (see Note 1)
N/A | | N/A | Relocation Request
Acknowledge
Relocation Failure | + +NOTE 1: This is an Information Element exchanged between a target BSS/RNC and a source BSS/RNC through the Core Network + +**Table 2c. Messages/PDUs exchanged between the target BSS/RNC and the core network upon successful handover** + +| → | MSC | SGSN | +|-------------------|---------------------|----------------------| +| Target BSS | Handover Complete | PS Handover Complete | +| Target RNC | Relocation Complete | Relocation Complete | + +**Table 2d. Messages/PDUs exchanged between the source BSS/RNC and the core network upon unsuccessful handovers** + +| → | MSC | SGSN | +|-------------------|-------------------|--------------------| +| Source BSS | Handover Failure | PS Handover Cancel | +| Source RNC | Relocation Cancel | Relocation Cancel | + +#### 6.3.4.2 Inter-RAT DTM Handover from GERAN *A/Gb mode* to UTRAN + +For the Inter-RAT DTM handover from GERAN *A/Gb mode* to UTRAN procedure, the behaviour of the source BSS (and the MS in the source cell) is as specified for the Inter-BSS DTM Handover procedure described in sub-clause 6.3.3a and the behaviour of the target RNC is as specified for the UTRAN-UTRAN SRNS Relocation procedure (with two signaling connections) as defined in 3GPP TS 25.413 [16], using the messages/IEs/PDUs defined in tables 2a-2d above, with the following exceptions: + +- *Number of lu instances* IE (set equal to 2) is used to indicate to the target RNC that the CS (respectively PS) handover is ongoing at the same time as the PS (respectively CS) handover for the same mobile station. +- The (RLC/MAC) DTM HANDOVER COMMAND message sent to the MS containing the (RRC) HANDOVER TO UTRAN COMMAND message. +- If the mobile station fails to access the target cell, the MS shall return to the old channel in the source cell and send a (RR) HANDOVER FAILURE message to the network. + +Figure 11f shows the exchange of messages in a successful Inter-RAT Intra-MSC Intra-SGSN DTM Handover from GERAN *A/Gb mode* to UTRAN, preparation phase. The same procedures are also used for an Inter-RAT Inter-MSC or Inter-SGSN DTM Handover from GERAN *A/Gb mode* to UTRAN. + +![Sequence diagram of Inter-RAT DTM Handover preparation phase from GERAN A/Gb mode to UTRAN. Lifelines: S-BSS, 2G/3G MSC, 2G/3G SGSN, T-RNC. The diagram shows the exchange of messages for CS Call, PS Session, HANDOVER REQUIRED, RELOCATION REQUEST, and RELOCATION REQUEST ACKNOWLEDGE.](b904ac2472cab80892d1e783e6230d6e_img.jpg) + +``` + +sequenceDiagram + participant S-BSS + participant 2G/3G MSC + participant 2G/3G SGSN + participant T-RNC + + Note left of S-BSS: CS Call + S-BSS->>2G/3G MSC: + Note left of S-BSS: PS Session + S-BSS->>2G/3G SGSN: + S-BSS->>2G/3G MSC: HANDOVER REQUIRED + Note right of S-BSS: Source RNC to Target RNC +Transparent Container +( Number of lu Instances =2 ) + 2G/3G MSC->>T-RNC: RELOCATION REQUEST + Note right of 2G/3G MSC: Source RNC to Target RNC +Transparent Container +( Number of lu Instances =2 ) + 2G/3G MSC->>2G/3G SGSN: PS HANDOVER REQUIRED + Note right of 2G/3G MSC: Source RNC to Target RNC +Transparent Container +( Number of lu Instances =2 ) + 2G/3G SGSN->>T-RNC: RELOCATION REQUEST + Note right of 2G/3G SGSN: Source RNC to Target RNC +Transparent Container +( Number of lu Instances =2 ) + T-RNC->>2G/3G SGSN: RELOCATION REQUEST ACKNOWLEDGE + T-RNC->>2G/3G MSC: Target RNC to Source RNC Transparent Container +(HANDOVER TO UTRAN COMMAND) + 2G/3G SGSN->>T-RNC: RELOCATION REQUEST +ACKNOWLEDGE + T-RNC->>2G/3G MSC: Target RNC to Source RNC Transparent Container +(HANDOVER TO UTRAN COMMAND) + +``` + +Sequence diagram of Inter-RAT DTM Handover preparation phase from GERAN A/Gb mode to UTRAN. Lifelines: S-BSS, 2G/3G MSC, 2G/3G SGSN, T-RNC. The diagram shows the exchange of messages for CS Call, PS Session, HANDOVER REQUIRED, RELOCATION REQUEST, and RELOCATION REQUEST ACKNOWLEDGE. + +**Figure 11f: Inter-RAT DTM Handover from GERAN *A/Gb mode* to UTRAN, preparation phase** + +Figure 11g shows the exchange of messages in a successful Inter-RAT Intra-MSC Intra-SGSN DTM Handover from GERAN *A/Gb mode* to UTRAN, execution phase. The same procedures are also used for an Inter-RAT Inter-MSC or Inter-SGSN DTM Handover from GERAN *A/Gb mode* to UTRAN. + +![Sequence diagram for Inter-RAT DTM Handover from GERAN A/Gb mode to UTRAN, execution phase. The diagram shows the interaction between MS, S-BSS, 2G/3G MSC, 2G/3G SGSN, and T-RNC. The process involves a HANDOVER COMMAND from 2G/3G MSC to S-BSS, followed by a Target RNC to Source RNC (HANDOVER TO UTRAN COMMAND) from 2G/3G MSC to S-BSS. The S-BSS then sends a PS HANDOVER REQUIRED ACK to 2G/3G MSC, which in turn sends a Target RNC to Source RNC (HANDOVER TO UTRAN COMMAND) to 2G/3G SGSN. The 2G/3G SGSN sends a DTM HANDOVER COMMAND (HANDOVER TO UTRAN COMMAND) to the MS. The MS then performs 'Access in the target cell'. Upon successful access, the MS sends a HANDOVER TO UTRAN COMPLETE message to the S-BSS. The S-BSS then sends a RELOCATION COMPLETE message to the 2G/3G MSC, which in turn sends a RELOCATION COMPLETE message to the 2G/3G SGSN. Finally, the 2G/3G SGSN sends a message to the T-RNC, and a box indicates 'Procedures to release the resources in the source cell'. A long double-headed arrow at the bottom indicates that 'CS and PS sessions continue'.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +``` + +sequenceDiagram + participant MS + participant S-BSS + participant 2G/3G MSC + participant 2G/3G SGSN + participant T-RNC + + Note right of 2G/3G MSC: 34 + 2G/3G MSC->>S-BSS: HANDOVER COMMAND + S-BSS->>2G/3G MSC: Target RNC to Source RNC ( HANDOVER TO UTRAN COMMAND) + 2G/3G MSC->>2G/3G SGSN: PS HANDOVER REQUIRED ACK + 2G/3G SGSN->>S-BSS: Target RNC to Source RNC ( HANDOVER TO UTRAN COMMAND) + S-BSS->>MS: DTM HANDOVER COMMAND (HANDOVER TO UTRAN COMMAND) + Note over MS, T-RNC: Access in the target cell + MS->>S-BSS: HANDOVER TO UTRAN COMPLETE + S-BSS->>2G/3G MSC: RELOCATION COMPLETE + 2G/3G MSC->>2G/3G SGSN: RELOCATION COMPLETE + 2G/3G SGSN->>T-RNC: + Note over S-BSS, 2G/3G MSC: Procedures to release the resources in the source cell + Note over MS, T-RNC: CS and PS sessions continue + +``` + +Sequence diagram for Inter-RAT DTM Handover from GERAN A/Gb mode to UTRAN, execution phase. The diagram shows the interaction between MS, S-BSS, 2G/3G MSC, 2G/3G SGSN, and T-RNC. The process involves a HANDOVER COMMAND from 2G/3G MSC to S-BSS, followed by a Target RNC to Source RNC (HANDOVER TO UTRAN COMMAND) from 2G/3G MSC to S-BSS. The S-BSS then sends a PS HANDOVER REQUIRED ACK to 2G/3G MSC, which in turn sends a Target RNC to Source RNC (HANDOVER TO UTRAN COMMAND) to 2G/3G SGSN. The 2G/3G SGSN sends a DTM HANDOVER COMMAND (HANDOVER TO UTRAN COMMAND) to the MS. The MS then performs 'Access in the target cell'. Upon successful access, the MS sends a HANDOVER TO UTRAN COMPLETE message to the S-BSS. The S-BSS then sends a RELOCATION COMPLETE message to the 2G/3G MSC, which in turn sends a RELOCATION COMPLETE message to the 2G/3G SGSN. Finally, the 2G/3G SGSN sends a message to the T-RNC, and a box indicates 'Procedures to release the resources in the source cell'. A long double-headed arrow at the bottom indicates that 'CS and PS sessions continue'. + +**Figure 11g: Inter-RAT DTM Handover from GERAN A/Gb mode to UTRAN, execution phase** + +#### 6.3.4.3 Inter-RAT DTM Handover from UTRAN to GERAN A/Gb mode + +For the Inter-RAT DTM handover from UTRAN to GERAN A/Gb mode, the behaviour of the source RNC is as specified for the UTRAN-UTRAN SRNS Relocation procedure (with two signaling connections) as defined in 3GPP TS 25.413 [16], and the behaviour of the target BSS (and MS on performing access in the target cell) is as specified for the Inter-BSS DTM Handover procedure described in sub-clause 6.3.3a, using the messages/IEs/PDUs defined in tables 2a-2d above, with the following exception: + +- The (RRC) HANDOVER FROM UTRAN COMMAND message sent to the MS contains the (RLC/MAC) DTM HANDOVER COMMAND message. +- If the mobile station fails to access the target cell, the MS shall return to the old channel in the source cell and send a (RRC) HANDOVER FROM UTRAN FAILURE message to the network. + +Figure 11h shows the exchange of messages in a successful Inter-RAT Intra-MSC Intra-SGSN DTM Handover, preparation phase. The same procedures are also used for an Inter-RAT Inter-MSC or Inter-SGSN DTM Handover from UTRAN to GERAN A/Gb mode. + +![Sequence diagram for Inter-RAT DTM Handover preparation phase from UTRAN to GERAN A/Gb mode. Lifelines: S-RNC, 3G/2G MSC, 3G/2G SGSN, T-BSS. The diagram shows the exchange of messages for CS Call and PS Session preparation, including RELOCATION REQUIRED, HANDOVER REQUEST, and various information containers.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +``` +sequenceDiagram + participant S-RNC + participant 3G/2G MSC + participant 3G/2G SGSN + participant T-BSS + + Note left of S-RNC: CS Call + Note left of S-RNC: PS Session + S-RNC->>3G/2G MSC: RELOCATION REQUIRED + S-RNC->>3G/2G MSC: Old BSS to New BSS Information ( PS Indication IE) + 3G/2G MSC->>T-BSS: HANDOVER REQUEST + 3G/2G MSC->>T-BSS: Old BSS to New BSS Information ( PS Indication IE) + S-RNC->>3G/2G MSC: RELOCATION REQUIRED + S-RNC->>3G/2G MSC: Source BSS to Target BSS Transparent Container (CS Indication IE) + 3G/2G MSC->>3G/2G SGSN: PS HANDOVER REQUEST + 3G/2G MSC->>T-BSS: Source BSS to Target BSS Transparent Container (CS Indication IE) + T-BSS->>3G/2G MSC: HANDOVER REQUESTACKNOWLEDGE + 3G/2G MSC->>3G/2G SGSN: Layer3 Information (DTM HANDOVER COMMAND) + 3G/2G MSC->>T-BSS: PS HANDOVER REQUEST + T-BSS->>3G/2G MSC: ACKNOWLEDGE + T-BSS->>3G/2G MSC: Target BSS to Source BSS Transparent Container (DTM HANDOVER COMMAND) +``` + +Sequence diagram for Inter-RAT DTM Handover preparation phase from UTRAN to GERAN A/Gb mode. Lifelines: S-RNC, 3G/2G MSC, 3G/2G SGSN, T-BSS. The diagram shows the exchange of messages for CS Call and PS Session preparation, including RELOCATION REQUIRED, HANDOVER REQUEST, and various information containers. + +**Figure 11h: Inter-RAT DTM Handover from UTRAN to GERAN A/Gb mode, preparation phase** + +Figure 11i shows the exchange of messages in a successful Inter-RAT Intra-MSC Intra-SGSN DTM Handover from UTRAN to GERAN A/Gb mode, execution phase. The same procedures are also used for an Inter-RAT Inter-MSC or Inter-SGSN DTM Handover from UTRAN to GERAN A/Gb mode. + +![Sequence diagram for Inter-RAT DTM Handover from UTRAN to GERAN A/Gb mode, execution phase. Lifelines: MS, S-RNC, 3G/2G MSC, 3G/2G SGSN, T-BSS. The diagram shows the flow of commands and responses between these entities during the handover process.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +``` + +sequenceDiagram + participant MS + participant S-RNC + participant 3G/2G MSC + participant 3G/2G SGSN + participant T-BSS + + Note left of MS: HANDOVER FROM UTRAN (DTM HANDOVER COMMAND) + MS->>S-RNC: + S-RNC->>3G/2G MSC: RELOCATION COMMAND + 3G/2G MSC-->>S-RNC: L3 Information (DTM HANDOVER COMMAND) + 3G/2G MSC->>3G/2G SGSN: RELOCATION COMMAND + 3G/2G SGSN-->>3G/2G MSC: Target BSS to Source BSS Transparent Container (DTM HANDOVER COMMAND) + Note right of MS: Access in the target cell + Note right of MS: Signaling link establishment + T-BSS->>MS: HANDOVER COMPLETE + T-BSS->>3G/2G SGSN: PS HANDOVER COMPLETE + 3G/2G SGSN->>3G/2G MSC: HANDOVER COMPLETE + Note right of MS: Iu Release Procedures for both PS and CS domains in the source cell + Note right of MS: RAU Procedures + Note right of MS: CS and PS sessions continue + +``` + +Sequence diagram for Inter-RAT DTM Handover from UTRAN to GERAN A/Gb mode, execution phase. Lifelines: MS, S-RNC, 3G/2G MSC, 3G/2G SGSN, T-BSS. The diagram shows the flow of commands and responses between these entities during the handover process. + +Figure 11i: Inter-RAT DTM Handover from UTRAN to GERAN A/Gb mode, execution phase + +## 6.4 Location management + +### 6.4.1 General + +The behaviour of a mobile station in idle mode shall be the same as when operating in class B, except that a GPRS simple class A mobile in idle mode can perform the RA update procedure in a DCCH. When the mobile station is in dedicated mode, the change of serving cell may trigger location procedures that require both domains of the mobile station to become active. + +In dedicated mode the mobile station shall check the roaming restrictions (i.e. the LAI or the PLMN identity of the current cell is not contained in any of the lists of "forbidden LAs for roaming", "forbidden LAs for regional provision of service", "forbidden PLMNs for GPRS service" or "forbidden PLMNs" respectively, see 3GPP TS 23.122 and 3GPP TS 24.008). + +Table 3 contains a summary of the procedures to be carried out by a GPRS mobile station operating in Class A when crossing a boundary. + +**Table 3: Location update procedures for a GPRS mobile station operating in class A** + +| Mode
Boundary | | | CS idle | | CS dedicated | | +|----------------------|------------|----------------|----------------------------|----------|-----------------------------------------------------------------------------------------------------------------------------------|----------| +| | | | PS stand-by | PS ready | PS stand-by | PS ready | +| Cell; same RA | | | Nothing | | Nothing | | +| RA; same LA | NMO | I | Combined RA/LA update | | RA update. When the CS connection ends in a RA different than the original, a combined RA/LA update with IMSI attach is performed | | +| | | II, III | RA Update | | | | +| LA | NMO | I | Combined RA/LA update | | RA update. When the CS connection ends in a LA different than the original, a combined RA/LA update with IMSI attach is performed | | +| | | II, III | Parallel RA and LA updates | | RA update. When the CS connection ends in a LA different than the original an LA update is performed. | | + +The request from GMM to perform a location management procedure may trigger the request of packet resources, as described above. The contents of the request message (e.g. DTM Request) should help the BSS decide the resources to be allocated. + +RA update and LA update procedures shall be supported in parallel in the main DCCH with SAPI 0. This helps reduce the congestion caused by GPRS signalling on GPRS TCHs that naturally exists in cells on the border of a RA or RA/LA without noticeably affecting the QoS of the CS connection. + +In addition to crossing cell boundaries, a DTM capable mobile station in GMM Ready state shall perform a Cell Update procedure each time that it enters dedicated mode from packet idle mode in a cell that supports dual transfer mode. + +The following clauses clarify how the mobile station performs the cell update and location/routing area update procedures while in dedicated mode. As previously indicated, the request of the establishment of dual transfer mode may trigger a change of the RR resources in the cell or a change of the serving cell. To simplify the diagrams below, possible assignment or handover procedures are ignored. + +The following diagrams consider the *worst* case (no packet resources allocated) as it requires the establishment of uplink and -for RA Update- downlink TBFs. If an uplink TBF already exists, the initial steps leading to the uplink TBF establishment are not necessary. If a downlink TBF already exists, the uplink TBF can also be established as currently by sending the Channel Request Description information element in the Packet Downlink Ack/Nack message on the PACCH; see 3GPP TS 44.060 [5]. + +In case of DTM Handover the cell update or (non-combined, as a CS connection exists) RA update procedure is defined as in 3GPP TS 43.129 [13] and 3GPP TS 23.009 [14]. + +### 6.4.2 Cell update + +Figure 12 and figure 13 show the exchange of messages involved in a Cell Update procedure when the mobile station is in dedicated mode, packet idle mode and Ready state. The mobile station shall request uplink resources, indicating "Cell Update". Typically, the BSS will command the MS to perform the Cell Update procedure in single timeslot operation (figure 12), although it may allocate an uplink TBF on a different time slot (figure 13) if the LLC frame contains user data. In the latter case, a change of the radio resources as was described in the previous clauses may happen before the MS sends the LLC frame on the TBF. + +![Sequence diagram of the Cell Update procedure in dedicated mode, packet idle mode and Ready state. The diagram shows four entities: MS, BSS, MSC, and SGSN. The MS sends a GTTP Information (LLC PDU) to the BSS. The BSS sends a CS dedicated mode message to the MSC. The MSC sends a UL-UNITDATA (LLC PDU) to the SGSN. The MS also sends a UL-UNITDATA (LLC PDU) to the BSS.](96bfe678265c45ada94af2d97be9d002_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC + participant SGSN + Note left of MS: [Main DCCH] + MS->>BSS: GTTP Information (LLC PDU) + BSS->>MSC: CS dedicated mode + MSC->>SGSN: UL-UNITDATA (LLC PDU) + MS->>BSS: UL-UNITDATA (LLC PDU) + +``` + +Sequence diagram of the Cell Update procedure in dedicated mode, packet idle mode and Ready state. The diagram shows four entities: MS, BSS, MSC, and SGSN. The MS sends a GTTP Information (LLC PDU) to the BSS. The BSS sends a CS dedicated mode message to the MSC. The MSC sends a UL-UNITDATA (LLC PDU) to the SGSN. The MS also sends a UL-UNITDATA (LLC PDU) to the BSS. + +**Figure 12: Cell Update procedure in dedicated mode, packet idle mode and Ready state; performed on the main DCCH** + +![Sequence diagram for Figure 13: Cell Update procedure in dedicated mode, packet idle mode and Ready state; performed on a TBF. The diagram shows four entities: MS, BSS, MSC, and SGSN. The MS sends a DTM Request to the BSS. The BSS sends a Packet Assignment to the MS. The MS sends RLC/MAC block(s) to the BSS. The BSS sends UL-Unitdata to the SGSN. A bracket labeled 'CS dedicated mode' spans from the MS to the MSC.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC + participant SGSN + Note left of MS: [Uplink TBF] + MS->>BSS: DTM Request + BSS-->>MS: Packet Assignment + MS->>BSS: RLC/MAC block(s) + BSS->>SGSN: UL-Unitdata + Note over MS, MSC: CS dedicated mode + +``` + +Sequence diagram for Figure 13: Cell Update procedure in dedicated mode, packet idle mode and Ready state; performed on a TBF. The diagram shows four entities: MS, BSS, MSC, and SGSN. The MS sends a DTM Request to the BSS. The BSS sends a Packet Assignment to the MS. The MS sends RLC/MAC block(s) to the BSS. The BSS sends UL-Unitdata to the SGSN. A bracket labeled 'CS dedicated mode' spans from the MS to the MSC. + +**Figure 13: Cell Update procedure in dedicated mode, packet idle mode and Ready state; performed on a TBF** + +### 6.4.3 Routeing Area update + +Figure 14 and figure 15 show the message flow during the Routeing Area Update procedure under the same conditions (the MS in CS dedicated mode, packet idle mode and Ready state). Figure 14 shows the procedures when the main DCCH is allowed, whereas two TBFs are used in figure 15. In this case, the uplink TBF is created to send the Routeing Area Update Request. The Routeing Area Update Accept from the SGSN needs the previous establishment of a downlink TBF. + +It should be noted that the steps performed after the RA Update Complete message in Figure 15 are optional since it is not a requirement to move the TCH/F back to its original position. + +![Sequence diagram for Figure 14: Routeing Area Update procedure in dedicated mode, packet idle mode and Ready state; performed on the main DCCH. The diagram shows five entities: MS, BTS, BSC, MSC, and SGSN. The MS sends a GTTP(RA Update Request) to the BSC. The BSC sends a BSSGP (RA Update Request) to the SGSN. The SGSN sends a BSSGP (RA Update Accept) to the BSC. The BSC sends a GTTP(RA Update Accept) to the MS. The MS sends a GTTP(RA Update Complete) to the BSC. A bracket labeled 'CS dedicated mode (TCH/F)' spans from the MS to the MSC.](d8698aacaeead6dfed9a1e448670a2e4_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + participant MSC + participant SGSN + Note over MS, MSC: CS dedicated mode (TCH/F) + MS->>BSC: GTTP(RA Update Request) + BSC->>SGSN: BSSGP (RA Update Request) + SGSN-->>BSC: BSSGP (RA Update Accept) + BSC-->>MS: GTTP(RA Update Accept) + MS-->>BSC: GTTP(RA Update Complete) + Note left of MS: [Main DCCH] + Note left of MS: [Main DCCH] + Note left of MS: [Main DCCH] + +``` + +Sequence diagram for Figure 14: Routeing Area Update procedure in dedicated mode, packet idle mode and Ready state; performed on the main DCCH. The diagram shows five entities: MS, BTS, BSC, MSC, and SGSN. The MS sends a GTTP(RA Update Request) to the BSC. The BSC sends a BSSGP (RA Update Request) to the SGSN. The SGSN sends a BSSGP (RA Update Accept) to the BSC. The BSC sends a GTTP(RA Update Accept) to the MS. The MS sends a GTTP(RA Update Complete) to the BSC. A bracket labeled 'CS dedicated mode (TCH/F)' spans from the MS to the MSC. + +**Figure 14: Routeing Area Update procedure in dedicated mode, packet idle mode and Ready state; performed on the main DCCH** + +![Sequence diagram of Routeing Area Update procedure in dedicated mode, packet idle mode and Ready state; performed on TBFs. The diagram shows interactions between MS, BTS, BSC, MSC, and SGSN. The procedure involves CS dedicated mode activation, DTM Request, Channel Activation, DTM Assignment Command, SABM, UA, Assignment Complete, RF Channel Release, RA Update Request, Packet Assignment, RA Update Accept, RA Update Complete, and BSSGP PDUs.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BTS + participant BSC + participant MSC + participant SGSN + + Note left of MS: CS dedicated mode (TCH/F) + MS->>BSC: [Main DCCH] DTM Request + BSC->>BTS: Channel Activation + BTS->>BSC: Channel Activation Ack + BSC->>MS: [Main DCCH] DTM Assignment Command + MS->>BTS: SABM + BTS->>MS: UA + MS->>BSC: [Main DCCH] Assignment Complete + BSC->>BTS: RF Channel Release + BTS->>BSC: RF Channel Release Ack + MS->>BSC: [Uplink TBF] RA Update Request + BSC->>SGSN: BSSGP PDU(RA Update Request) + BSC->>MS: [Main DCCH] Packet Assignment + SGSN->>BSC: BSSGP PDU(RA Update Accept) + BSC->>MS: [Downlink TBF] RA Update Accept + MS-->>BSC: [Main DCCH] DTM Request + MS-->>BSC: [Main DCCH] Packet Assignment + MS->>BSC: [Uplink TBF] RA Update Complete + BSC-->>SGSN: BSSGP PDU(RA Update Complete) + BSC->>BTS: Channel Activation + BTS->>BSC: Channel Activation Ack + BSC->>MS: [Main DCCH] Assignment Command + MS->>BTS: SABM + BTS->>MS: UA + MS->>BSC: [Main DCCH] Assignment Complete + BSC->>BTS: RF Channel Release + BTS->>BSC: RF Channel Release Ack + +``` + +Sequence diagram of Routeing Area Update procedure in dedicated mode, packet idle mode and Ready state; performed on TBFs. The diagram shows interactions between MS, BTS, BSC, MSC, and SGSN. The procedure involves CS dedicated mode activation, DTM Request, Channel Activation, DTM Assignment Command, SABM, UA, Assignment Complete, RF Channel Release, RA Update Request, Packet Assignment, RA Update Accept, RA Update Complete, and BSSGP PDUs. + +**Figure 15: Routeing Area Update procedure in dedicated mode, packet idle mode and Ready state; performed on TBFs** + +### 6.4.4 Location update + +#### 6.4.4.1 Change of Location Area in dedicated mode + +Figure 16 shows the exchange of messages when changing location area while in dedicated mode. It is identical to the Routeing Area Update procedure except for the final group of messages. As the CS domain is not updated in the MSC while the MS is in a CS connection, a Location Area Update procedure is initiated when the CS connection ends to align the MM contexts in the MSC and the SGSN. This procedure consists of a Combined RA/LA Update with IMSI attach when the network is in mode I or a Location Area Update for modes II and III. + +If the MS and the network in mode I support enhanced DTM CS release procedure and the location area of the MS has changed while in dual transfer mode, the MS shall send an indication to the network that in this case the enhanced DTM CS release procedure shall not be used. This indication is sent in the PACKET SI STATUS or PACKET PSI STATUS message. After the receipt of the indication the network shall release the RR connection and PS resources. Upon receipt of a CHANNEL RELEASE message the MS shall initiate the Combined RA/LA Update procedure with update type combined RA/LA updating with IMSI attach. + +If the MS and the network in mode II or III support enhanced DTM CS release procedure and the location area of the MS has changed while in dual transfer mode, the MS may perform the enhanced DTM CS release procedure and, after + +the release of the RR connection, request CS resources via the enhanced DTM CS Establishment procedure for performing the Location Area Update procedure. + +![Sequence diagram showing LA Update and RA Update procedures in CS dedicated mode, packet idle mode and Ready state. The diagram involves four entities: MS, BSS, MSC, and SGSN. The sequence starts with 'CS dedicated mode' from MS to MSC. This is followed by 'RAU procedure while CS dedicated mode' (dashed line) from MS to SGSN. Then 'CS Connection ends' (dashed line) from MSC to BSS. Next, 'Combined RA/LA Update procedure' (dashed line) from MS to SGSN, labeled 'a)'. Finally, 'LAU procedure' (dashed line) from MS to MSC, labeled 'b)'.](f5deee2f3301ee351c4008283ffafbb3_img.jpg) + +Sequence diagram showing LA Update and RA Update procedures in CS dedicated mode, packet idle mode and Ready state. The diagram involves four entities: MS, BSS, MSC, and SGSN. The sequence starts with 'CS dedicated mode' from MS to MSC. This is followed by 'RAU procedure while CS dedicated mode' (dashed line) from MS to SGSN. Then 'CS Connection ends' (dashed line) from MSC to BSS. Next, 'Combined RA/LA Update procedure' (dashed line) from MS to SGSN, labeled 'a)'. Finally, 'LAU procedure' (dashed line) from MS to MSC, labeled 'b)'. + +- a) for Network Mode of Operation I; +- b) for Network Mode of Operation II and III. + +**Figure 16: LA Update and RA Update procedures in CS dedicated mode, packet idle mode and Ready state** + +#### 6.4.4.2 Simultaneous Location Area and Routeing Area update procedures + +When the mobile station is in idle mode and crosses a LA boundary, and hence an RA boundary, the mobile station can perform both location procedures (LA and RA update) on the main DCCH. Figure 17 shows the case of the RAU procedure finishing before the LAU. If the LAU procedure finishes before the RAU procedure does, the SDCCH is released and the RAU is completed on standalone TBF(s), as shown in figure 18. + +NOTE: Alternatively, the BSC may hold the DCCH for a few seconds until the RAU is finished. This is an improvement of the implementation and has not been standardised. + +![Sequence diagram showing parallel LA and RA Update procedures where the RAU finishes first. The diagram involves four entities: MS, BSC, MSC, and SGSN. The sequence starts with 'Channel Request' from MS to BSC on [RACH]. Then 'Immediate Assignment' from BSC to MS on [AGCH]. Next, 'Location Updating Request' from MS to MSC on [Main DCCH]. Simultaneously, 'GTTP(RAU Request)' from MS to BSC and 'BSSGP PDU(RA Update Request)' from BSC to SGSN are shown on [Main DCCH]. The 'GTTP(RAU Accept)' from BSC to MS and 'BSSGP PDU(RA Update Accept)' from SGSN to BSC are shown on [Main DCCH]. Then 'Location Updating Accept' from MSC to MS on [Main DCCH]. Finally, 'Channel Release' from MSC to MS and 'Clear Command' from MSC to BSC are shown on [Main DCCH].](eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg) + +Sequence diagram showing parallel LA and RA Update procedures where the RAU finishes first. The diagram involves four entities: MS, BSC, MSC, and SGSN. The sequence starts with 'Channel Request' from MS to BSC on [RACH]. Then 'Immediate Assignment' from BSC to MS on [AGCH]. Next, 'Location Updating Request' from MS to MSC on [Main DCCH]. Simultaneously, 'GTTP(RAU Request)' from MS to BSC and 'BSSGP PDU(RA Update Request)' from BSC to SGSN are shown on [Main DCCH]. The 'GTTP(RAU Accept)' from BSC to MS and 'BSSGP PDU(RA Update Accept)' from SGSN to BSC are shown on [Main DCCH]. Then 'Location Updating Accept' from MSC to MS on [Main DCCH]. Finally, 'Channel Release' from MSC to MS and 'Clear Command' from MSC to BSC are shown on [Main DCCH]. + +**Figure 17: Parallel LA and RA Update procedures: the RAU finishes first** + +![Sequence diagram showing Parallel LA and RA Update procedures: the LAU finishes first. The diagram involves four entities: MS, BSC, MSC, and SGSN. The sequence of messages is: 1. MS to BSC: Channel Request (RACH); 2. BSC to MS: Immediate Assignment (AGCH); 3. MS to MSC: Location Updating Request (Main DCCH); 4. MSC to SGSN: BSSGP PDU (RA Update Request) (Main DCCH); 5. MSC to MS: Location Updating Accept (Main DCCH); 6. MSC to BSC: Clear Command (Main DCCH); 7. BSC to MS: Immediate Assignment (AGCH); 8. BSC to MS: RLC/MAC block (PDTCH); 9. BSC to MS: RLC/MAC block (PDTCH); 10. BSC to MS: RLC/MAC block (PDTCH).](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSC + participant MSC + participant SGSN + Note left of MS: [RACH] + MS->>BSC: Channel Request + Note left of BSC: [AGCH] + BSC->>MS: Immediate Assignment + Note left of MS: [Main DCCH] + MS->>MSC: Location Updating Request + Note left of MSC: [Main DCCH] + MSC->>SGSN: BSSGP PDU (RA Update Request) + Note left of MSC: [Main DCCH] + MSC->>MS: Location Updating Accept + Note left of MSC: [Main DCCH] + MSC->>BSC: Clear Command + Note left of BSC: [AGCH] + BSC->>MS: Immediate Assignment + Note left of BSC: [PDTCH] + BSC->>MS: RLC/MAC block + Note left of BSC: [PDTCH] + BSC->>MS: RLC/MAC block + Note left of BSC: [PDTCH] + BSC->>MS: RLC/MAC block + +``` + +Sequence diagram showing Parallel LA and RA Update procedures: the LAU finishes first. The diagram involves four entities: MS, BSC, MSC, and SGSN. The sequence of messages is: 1. MS to BSC: Channel Request (RACH); 2. BSC to MS: Immediate Assignment (AGCH); 3. MS to MSC: Location Updating Request (Main DCCH); 4. MSC to SGSN: BSSGP PDU (RA Update Request) (Main DCCH); 5. MSC to MS: Location Updating Accept (Main DCCH); 6. MSC to BSC: Clear Command (Main DCCH); 7. BSC to MS: Immediate Assignment (AGCH); 8. BSC to MS: RLC/MAC block (PDTCH); 9. BSC to MS: RLC/MAC block (PDTCH); 10. BSC to MS: RLC/MAC block (PDTCH). + +Figure 18: Parallel LA and RA Update procedures: the LAU finishes first + +## 6.5 Provision of the IMSI to the BSC + +### 6.5.1 General + +To enable the described implementation of the GPRS class A mode of operation, the BSS and the PCU are required to perform the co-ordination of the allocation of radio resources for both domains. That co-ordination is performed with the IMSI as it is described in the following clauses. + +The IMSI shall be provided to the BSC during: + +1. call establishment; +2. session establishment; and +3. external handover. + +### 6.5.2 Call establishment + +The BSC triggers the establishment of the SCCP connection with the MSC. The MSC shall provide the IMSI to the BSC in a new message: Common ID message. This message can be sent either on the SCCP Connection Confirm message or immediately after, once the connection is already established. + +### 6.5.3 Session establishment + +#### 6.5.3.1 Downlink session establishment + +Both in the READY and the STANDBY states: + +- the IMSI is sent from the SGSN in the PS PAGING BSSGP PDUs; +- the IMSI and the TLLI are sent from the SGSN in the DL-UNITDATA. + +#### 6.5.3.2 Uplink session establishment + +At the establishment of an uplink TBF, the BSC can identify whether it knows the IMSI of a mobile station for which it has its TLLI. If the IMSI is not known, the BSC can initiate the RA-Capability-Update procedure and request the IMSI (and the RA capabilities) of the mobile to the SGSN. + +- If there is a change of cell and the mobile station was in packet transfer mode, it performs a cell update procedure, which can be done with user data and therefore hold for a long time, possibly with no downlink message. During this time the mobile station may not be able to monitor the broadcast channels and miss paging messages. This error situation is prevented by the BSS initiating the RA-Capability-Update procedure. +- The RA-Capability-Update procedure may fail if the SGSN does not have the IMSI (or the RA Capabilities) of the mobile station. This may happen when there is a change of SGSN (hence also of RA). In this case, the mobile station sends the RAU Request message on the uplink TBF and then goes back to (packet) idle mode, where it can receive possible paging messages. When the SGSN answers with the RAU Accept message (after retrieving the PDP and MM contexts from the old SGSN), the DL-UNITDATA message contains the IMSI and the TLLI. + +### 6.5.4 External handover + +During CS handover procedure, the IMSI is included in the (BSSMAP) HANDOVER REQUEST message from the MSC to the target BSC. The identifiers included in the (BSSGP) PS HANDOVER REQUEST message from the SGSN to the target BSC during the PS Handover procedure are defined in 3GPP TS 43.129 [13]. + +## 6.6 In-band parameters + +When the mobile station is in dedicated mode, packet transfer mode or both, some information may need to be passed to the mobile station so that it can enter or maintain the dual transfer mode. Most of that information consists of parameters that are broadcast in the (P)BCCH, but that cannot be read by the mobile station. Some new parameters are added. + +Table 4 lists those parameters and indicates whether they have to be sent while in dedicated mode, packet transfer mode or both. When the mobile station is in idle mode, the parameters are sent on the BCCH. When the mobile station is in dedicated mode, the parameters are sent on the SACCH. When the mobile station is in packet transfer mode, they are sent on the PACCH. + +While in dual transfer mode, the MS shall assume that the SGSN Release is "Release '99 onwards" and shall ignore the SGSNR information provided in PSI 14. + +**Table 4: List of parameters to be passed in-band to the mobile station** + +| (P)BCCH | FACCH | SACCH | PACCH | Parameter | Description | +|---------|-------|-------|-------|-----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ✓ | ✓ | ✓ | | DTM: bit(1) | DTM support in the cell.
(P)BCCH : to enable a quick resumption of the GPRS session in the transition from dual transfer mode to packet transfer mode; to enable the LA and RA Update procedures to be performed in parallel on an SDCCH.
FACCH : immediately after a handover procedure when the MS was in DTM, in order to enable the packet session to be resume without long interruptions. [DTM Information]
SACCH : to enable the packet request procedures while in dedicated mode. [SI 6] | +| | ✓ | ✓ | | RAI : bit(48) | Routeing Area Identity. It is needed to enable the MS to detect changes of routeing area during a handover in dedicated mode [DTM Information, SI6] | +| | ✓ | ✓ | | Cell Identity : bit(16) | Cell Identity. It is needed to enable the MS to detect changes of cell after a handover in dedicated mode [DTM Information, SI 6] | +| | ✓ | ✓ | | MAX_LAPDm : bit(3) | Maximum number of LAPDm frames. To limit the use of the main DCCH when the MS in dedicated mode
FACCH : immediately after a handover procedure when the MS was in DTM, in order to enable the packet session to be resume without long interruptions. [DTM Information]
SACCH : to enable the packet request procedures while in dedicated mode. [SI 6] | +| | ✓ | | | GPRS Cell Options | GPRS Cell Options. Sent on the DTM assignment message (DTM ASSIGNMENT COMMAND or PACKET ASSIGNMENT) | +| | ✓ | | | GPRS Power Control Parameters | GPRS Power Control Parameters. Sent on the DTM assignment message (DTM ASSIGNMENT COMMAND or PACKET ASSIGNMENT) | +| | | | ✓ | (P)SI 13 Information | (P)SI 13 Information: this information is sent so that the mobile station needs not read SI 13 at call release during dual transfer mode | +| | ✓ | ✓ | | Dedicated Mode MBMS Notification Support Indication | Dedicated Mode MBMS Notification Support Indication. to enable the mobile station to participate in MBMS procedures while in dedicated mode (DTM ASSIGNMENT COMMAND, PACKET ASSIGNMENT or DTM INFORMATION, SI 6) | +| | | | | | | + +## 6.7 MS behaviour in *heterogeneous* networks + +### 6.7.1 General + +The support of DTM in a network is not likely to be homogeneous. Network operators normally have more than one infrastructure supplier and different manufacturers will support DTM with different time scales. In addition, the rollout of a product release from a certain manufacturer is not performed simultaneously across the network. + +It is therefore difficult to avoid the fact that some cells in a network support DTM whereas others do not, making necessary to ensure a consistent behaviour of a DTM mobile station in such scenario. The existing GPRS Suspension and Resume procedures are reused for this purpose. + +Table 5 contains the four possible combinations when the mobile station is handed over between two cells, where each of them may or not support DTM. + +**Table 5: Modification to CS handover to ensure a correct DTM behaviour when DTM is not always supported** + +| | | Support of DTM in new cell | | +|----------------------------|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | No | Yes | +| Support of DTM in old cell | No |

The MS waits for the reception of the SI 6 message indicating whether the cell supports DTM. If DTM is supported, the same message contains the RAC.

Normal CS handover.

|

When the SI6 message is received, the MS performs the Resume procedure: it performs the RR Packet Request procedure for the GMM RA Update procedure.

| +| | Yes |

The MS waits until the reception of the SI 6 message indicating that the cell does not support DTM. Then, if GPRS is supported, the MS performs the GPRS suspension procedure.

|

The MS waits for the reception of the SI 6 message indicating that the cell supports DTM and containing the RAC. When the SI6 message is received, the MS performs the Cell Update (MS in READY), the RA Update procedure (change of RA) or none of both (MS in STANDBY and both cells in the same RA).

| +| | | |

The network sends the DTM Information message (implicitly implying the support of DTM) containing the RAC and any other information needed to perform the Packet Request procedure.

| + +### 6.7.1 Suspension procedure + +The GPRS Suspension procedure is defined in the standards to be used when a mobile station in mode of operation B and in packet transfer mode is paged for circuit switched services. + +The GPRS Suspension procedure can be used without modifications when: + +- a DTM mobile in dedicated or dual transfer mode is handed over from a cell that supports DTM to one that does not; or +- a DTM mobile in packet transfer mode on a cell that does not support DTM is paged for circuit switched services. + +The GPRS Suspension procedure is initiated by the mobile station by sending a GPRS SUSPENSION REQUEST message to the BSS after it has entered dedicated mode. + +### 6.7.2 Resume procedure + +The Resume procedure is used for the resumption of GPRS service when the conditions for suspension have disappeared (e.g. a suspended class B mobile station has cleared the resources allocated for the circuit switched service). The procedure is initiated: + +- a) by the **BSS**, when it detects the change of conditions: the BSS indicates the resumption to the SGSN and then the mobile station; +- b) by the **mobile station**, when it detects the change of conditions and the BSS has not resumed GPRS: the mobile station performs a RA Update procedure that resumes GPRS with the SGSN. + +For the two new causes for GPRS suspension, there is no message from the BSS to the mobile station and, thus, the Resume procedure is initiated by the mobile station (b). + +# 7 DTM operation + +Once the mobile station enters the DTM, the existent RLC/MAC procedures apply, with the exception of the case of an exclusive allocation of an uplink PDCH (including the PDCH/H of a "TCH/H + PDCH/H" configuration). In that case, the mobile station is always granted the transmission of uplink RLC/MAC blocks, which keep the current format. Thus, the mobile station shall ignore the USF mechanism for dynamic allocation. + +Other exceptions to the existent RLC/MAC procedures are: + +- The mobile station shall not accept a packet assignment command (addressed to it on the PACCH) that changes the frequency definition of the PDCH. Such change shall be done by means of a DTM Assignment Command message on the main DCCH (changing both TCH and PDCH configurations). A modification of the timeslot allocation may occur by means of a Packet Assignment message. Any violation of the frequency restrictions or the multislot class of the mobile station (taking both TCH and PDCH resources into account) shall be treated as an abnormal case and the TBF(s) shall then be aborted. + +NOTE 1: the PCU should know that the mobile station is in dual transfer mode and therefore format the messages correctly. + +- When all TBFs have been released (or aborted), the mobile station returns to dedicated mode. +- When the mobile station is in dual transfer mode, it shall ignore a Packet Cell Change Order or a RR-Cell Change Order message and shall remain in dual transfer mode. + +NOTE 2: the PCU should know that the mobile station is in dual transfer mode and therefore not send these messages. + +- When a mobile station in dual transfer mode receives a valid RRBP field in a downlink RLC/MAC block, if it has been assigned PDCH/H, where the *exclusive allocation is required*, the mobile station shall use normal bursts and not access bursts, irrespective of the value of the CONTROL\_ACK\_TYPE field received in the DTM Assignment Command message or Packet Assignment message. If the mobile station has not been assigned PDCH/H, it shall either use normal bursts or access bursts to transmit the Packet Control Acknowledgement message depending on the value of CONTROL\_ACK\_TYPE received in the DTM Assignment Command message or Packet Assignment message. + +The mobile station remains in DTM until the CS connection or all the TBFs are released. + +# 8 GPRS attach procedure while in dedicated mode and packet idle mode + +In this procedure, the mobile station sends a (non-combined) GPRS Attach Request message to the SGSN. The sequence of messages is very similar to the Routeing Area Update procedure, shown in figure 14 and figure 15. + +# 9 Security + +The current procedures apply. + +NOTE: LLC frames containing GPRS signalling messages and sent on the main DCCH are therefore ciphered twice, but that has been confirmed by SMG10 not to be a security problem. In "TCH/H + PDCH/H" and other multislot configurations, current GPRS ciphering is kept. + +# 10 Header and Data Compression + +Because this is done at SNDPCP layer, there is assumed to be no impact. + +# --- Annex A (informative): Possible improvements for future releases + +| No. | Description | +|-----|--------------------------------------------------------------------------------------------------------------------------------| +| 1 | New 3G TS 04.60 procedure for the establishment of a CS connection without interruption of the packet services | +| 2 | Support of multislot operation comprising single timeslot operation and additional PDCH(s) in the same direction in the uplink | +| 3 | Multislot configurations where the CS connection is using more than one timeslot | +| 4 | Multislot configurations where the timeslots allocated to the PS session are not contiguous | +| 5 | Power control for EGPRS while in DTM | + +# Annex B (normative): Incremental support of extended DTM multislot classes + +As for other DTM multislot classes, for extended DTM multislot classes incremental support (see subclause 4.5.1.3) shall apply: the MS only indicates the support of one multislot class and the support of less restrictive classes is also assumed by the network. This is depicted for mobile stations supporting Extended DTM GPRS Multi Slot Class or Extended DTM EGPRS Multi Slot Class, in Figure 19. + +Mobile stations not supporting high multislot classes may indicate support only for the Extended DTM GPRS Multi Slot Classes or Extended DTM EGPRS Multi Slot Classes 5, 6, 9, 10 and 11 (indicated by solid boxes on the left of the dashed line in Figure 19). + +NOTE: High multislot classes are multislot classes 30-45 (see 3GPP TS 45.002 [6]). + +For mobile stations supporting high multislot classes, the Extended DTM GPRS Multi Slot Class shall always be the same as the DTM GPRS Multi Slot Class and the Extended DTM EGPRS Multi Slot Class shall always be the same as the DTM EGPRS Multi Slot Class (indicated by solid boxes on the right of the dashed line in Figure 19). The support of the mix of full and half rate packet data channels is indicated by the presence of the Extended DTM GPRS Multi Slot Class field and, where applicable, the Extended DTM EGPRS Multi Slot Class field in the MS Classmark 3 and MS Radio Access Capability IEs, regardless of the value of these fields. + +![Figure 19: Incremental support of extended DTM multislot classes. The diagram shows various multislot classes (Class 1 to Class 44) and their relationships based on Rx+Tx=Sum. A dashed vertical line separates 'low' multislot classes (1-12) from 'high' multislot classes (30-44). Solid boxes on the left of the dashed line represent classes 5, 6, 9, 10, and 11. Solid boxes on the right of the dashed line represent classes 30-44. Arrows indicate incremental support relationships between classes.](a3083eec2a883ee8327b3c24174df6a9_img.jpg) + +The diagram illustrates the incremental support of extended DTM multislot classes. It is divided into two main groups by a vertical dashed line. The left group contains classes 1 through 12, and the right group contains classes 30 through 44. Each class is represented by a box containing its number and the sum of Rx and Tx (e.g., Class 1: 1+1=2). Arrows indicate that if a mobile station supports a specific class, it also supports all classes indicated by the arrows (less restrictive classes). Classes 5, 6, 9, 10, and 11 are highlighted with solid boxes on the left of the dashed line. Classes 30, 31 or 36, 32 or 37, 33 or 38, 40, 41, 42, 43, and 44 are highlighted with solid boxes on the right of the dashed line. The legend indicates that Class is represented by a box with Rx+Tx=Sum. + +Figure 19: Incremental support of extended DTM multislot classes. The diagram shows various multislot classes (Class 1 to Class 44) and their relationships based on Rx+Tx=Sum. A dashed vertical line separates 'low' multislot classes (1-12) from 'high' multislot classes (30-44). Solid boxes on the left of the dashed line represent classes 5, 6, 9, 10, and 11. Solid boxes on the right of the dashed line represent classes 30-44. Arrows indicate incremental support relationships between classes. + +Figure 19 – Incremental support of extended DTM multislot classes. + +# Annex C (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-----|---------------------------------------------------------------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 10 Nov 00 | G02 | GP-000705 | | | New specification approved by TSG-GERAN | 2.0.0 | 8.0.0 | +| 2001-04 | G04 | | | | Version for Release 4 | | 4.0.0 | +| 2001-06 | G05 | GP-011311 | 001 | 1 | Definition of new DTM multislot classes | 4.0.0 | 4.1.0 | +| 2002-06 | G10 | | | | Version for Release 5 | | 5.0.0 | +| 2003-02 | G13 | GP-030268 | 002 | | Clarification of the inclusion of DTM information in handover from 3G to 2G | 5.0.0 | 6.0.0 | +| 2003-02 | G13 | GP-030405 | 003 | 2 | Clarification on the use of basic HR in DTM single slot configuration | 5.0.0 | 6.0.0 | +| 2003-02 | G13 | GP-030406 | 004 | 2 | Clarification on the default value of MAX_LAPDm parameter | 5.0.0 | 6.0.0 | +| 2003-04 | G14 | GP-030974 | 007 | 1 | Corrections for DTM multislot configurations and DTM capability indication | 6.0.0 | 6.1.0 | +| 2003-08 | G16 | GP-032133 | 010 | 4 | Change of DTM core capability | 6.1.0 | 6.2.0 | +| 2003-11 | G17 | GP-032697 | 011 | 1 | Introducing MTBF Support | 6.2.0 | 6.3.0 | +| 2004-02 | G18 | GP-040429 | 014 | 1 | Clarifications and corrections to the DTM procedures | 6.3.0 | 6.4.0 | +| 2004-06 | G20 | GP-041680 | 016 | 1 | Addition of DTM enhancements | 6.4.0 | 6.5.0 | +| 2004-06 | G20 | GP-041696 | 017 | 2 | Conditions for the NAS registration procedures | 6.4.0 | 6.5.0 | +| 2004-06 | G20 | GP-041474 | 018 | | Usage of main DCCH in DTM | 6.4.0 | 6.5.0 | +| 2004-08 | G21 | GP-042113 | 024 | 1 | Correction of the possible burst format used for PACKET CONTROL ACKNOWLEDGEMENT in DTM mode | 6.5.0 | 6.6.0 | +| 2004-08 | G21 | GP-042204 | 025 | 1 | Handling of Assignment Request in BSS | 6.5.0 | 6.6.0 | +| 2004-08 | G21 | GP-042278 | 027 | 2 | Addition of combined RAU or LAU procedure pending indication | 6.5.0 | 6.6.0 | +| 2004-11 | G22 | GP-042450 | 019 | 5 | Correction to downlink power control for DTM | 6.6.0 | 6.7.0 | +| 2004-11 | G22 | GP-042363 | 026 | 3 | Alignment of stage 2 with stage 3 for DTM | 6.6.0 | 6.7.0 | +| 2004-11 | G22 | GP-042446 | 028 | | Clarification on speech codec for TCH/H in case of multislot configurations | 6.6.0 | 6.7.0 | +| 2005-01 | G23 | GP-050583 | 034 | 2 | Missing cell identity in DTM Information message | 6.7.0 | 6.8.0 | +| 2005-01 | G23 | GP-050449 | 035 | 1 | PS roaming while in DTM | 6.7.0 | 6.8.0 | +| 2005-04 | G24 | GP-050625 | 031 | 3 | Extension of DTM to higher multislot classes | 6.8.0 | 6.9.0 | +| 2005-04 | G24 | GP-050632 | 036 | | Corrections due to removal of fixed allocation | 6.8.0 | 6.9.0 | +| 2005-04 | G24 | GP-050950 | 037 | | Cell Update for DTM capable MS when moving from Packet Idle to Dedicated Mode whilst in GMM Ready and in case of DTM Handover Failure | 6.8.0 | 6.9.0 | +| 2005-06 | G25 | GP-051702 | 038 | 1 | Clarifications on DTM high multislot class capability | 6.9.0 | 6.10.0 | +| 2005-06 | G25 | GP-051703 | 039 | 1 | Miscellaneous corrections | 6.9.0 | 6.10.0 | +| 2005-09 | G26 | GP-052315 | 0041 | 2 | Alignment of DTM stage 2 with stage 3 | 6.10.0 | 6.11.0 | +| 2005-11 | G27 | GP-052843 | 0043 | 1 | Provision of MBMS parameters in "GPRS cell options" inband to CS connected DTM capable MS | 6.11.0 | 6.12.0 | +| 2005-11 | G27 | GP-052528 | 0044 | | RR connection establishment using enhanced DTM CS establishment in response to an encapsulated DTM ASSIGNMENT message | 6.11.0 | 6.12.0 | +| 2005-11 | G27 | GP-052636 | 0046 | | Sending DTM Information after Handover | 6.11.0 | 6.12.0 | +| 2005-11 | G27 | GP-052804 | 0042 | 1 | DTM stage 2 alignments with stage 3 | 6.12.0 | 7.0.0 | +| 2005-11 | G27 | GP-052818 | 0047 | 1 | SGSNR during DTM | 6.12.0 | 7.0.0 | +| 2006-01 | G28 | GP-060402 | 0045 | 3 | Introduction of the DTM HANDOVER | 7.0.0 | 7.1.0 | +| 2006-04 | G29 | GP-060718 | 0048 | | Corrections to DTM Handover procedures | 7.1.0 | 7.2.0 | +| 2006-06 | G30 | GP-061511 | 0051 | 4 | C value calculation in case there is a transition of the mode | 7.2.0 | 7.3.0 | +| 2006-06 | G30 | GP-061458 | 0052 | 3 | Introduction of Inter-RAT DTM Handover | 7.2.0 | 7.3.0 | +| 2006-06 | G30 | GP-061180 | 0054 | 1 | Alignment of DTM Handover procedures | 7.2.0 | 7.3.0 | +| 2006-09 | G31 | GP-061778 | 0056 | 1 | Conditions for the transmission of the Packet CS Request message | 7.3.0 | 7.4.0 | +| 2006-09 | G31 | GP-061913 | 0057 | 3 | Introduction of Downlink Dual Carrier for DTM | 7.3.0 | 7.4.0 | +| 2007-02 | G33 | GP-070438 | 0054 | 3 | Fast sending of DTM Handover Command | 7.4.0 | 7.5.0 | +| 2007-02 | G33 | GP-070254 | 0061 | | Enhanced DTM CS Release | 7.4.0 | 7.5.0 | +| 2007-08 | G35 | GP-071144 | 0062 | | Indication of a waiting time in DTM REJECT message | 7.5.0 | 7.6.0 | +| 2007-08 | G35 | GP-071551 | 0063 | | Introduction of EGPRS2 | 7.5.0 | 7.6.0 | +| 2008-08 | G39 | GP-081184 | 0064 | | Introduction of inter-RAT DTM handover with E-UTRAN | 7.6.0 | 8.0.0 | +| 2009-02 | G41 | GP-090354 | 0067 | 1 | Correction to Routing Area Updating type | 8.0.0 | 8.1.0 | +| 2009-12 | G44 | | | | Version for Release 9 | 8.1.0 | 9.0.0 | +| 2011-03 | G49 | | | | Version for Release 10 | 9.0.0 | 10.0.0 | +| 2012-09 | G55 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | +| 2013-03 | G57 | GP-130251 | 0068 | 2 | PLMN Index in the DTM handover procedure into shared GERAN | 11.0.0 | 11.1.0 | \ No newline at end of file diff --git a/marked/Rel-11/43_series/43059/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-11/43_series/43059/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0810fd5f394dad2003ab77714c97eb3bc695e1f --- /dev/null +++ b/marked/Rel-11/43_series/43059/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56186acb94239074f2b2c2d5c414c2f3193229b35de116f89222fcaea9edd0ba +size 16832 diff --git a/marked/Rel-11/43_series/43059/0c80c383f76034e117adf5e5eaadaaf3_img.jpg b/marked/Rel-11/43_series/43059/0c80c383f76034e117adf5e5eaadaaf3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ab3b02cbd026285e275b0f0c5f31c2053f34d85 --- /dev/null +++ b/marked/Rel-11/43_series/43059/0c80c383f76034e117adf5e5eaadaaf3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19183ef5e3c72453ec31669eeacb5a1bd496cc99b8b07e8e8f9e8507c542c5c2 +size 27349 diff --git a/marked/Rel-11/43_series/43059/1033dc9fde75540d224c907681b1b7aa_img.jpg b/marked/Rel-11/43_series/43059/1033dc9fde75540d224c907681b1b7aa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ebba38f67edadbe052e4fd7ce595155fbe40263 --- /dev/null +++ b/marked/Rel-11/43_series/43059/1033dc9fde75540d224c907681b1b7aa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59145e6762036ef891d9e88fb4d5e0e066e16b7a66878e90f29b64d1a71c91e6 +size 119833 diff --git a/marked/Rel-11/43_series/43059/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg b/marked/Rel-11/43_series/43059/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c57c0371f8a56df65e145405043c65db6151877 --- /dev/null +++ b/marked/Rel-11/43_series/43059/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:905d6d7ac927ec41949930aee7c87a6e5a7fae600981e87e337453b27625f9aa +size 32789 diff --git a/marked/Rel-11/43_series/43059/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg b/marked/Rel-11/43_series/43059/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4a9eada5c5ee968f412c3e71a06317eeda52226 --- /dev/null +++ b/marked/Rel-11/43_series/43059/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1547a428a85adae1ff60addf3a2b1d2f7fd68842d76e130b0e1d7567ecaae999 +size 47603 diff --git a/marked/Rel-11/43_series/43059/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg b/marked/Rel-11/43_series/43059/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd126fcbe3a08801146ce31a31d8105e2ff9f42c --- /dev/null +++ b/marked/Rel-11/43_series/43059/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14958bda10eebbd1a7d98fb1ddd20aa4b2bdfa78b96935d82f9e82267f1a2582 +size 14433 diff --git a/marked/Rel-11/43_series/43059/6470d350326789d5306eabcb76533951_img.jpg b/marked/Rel-11/43_series/43059/6470d350326789d5306eabcb76533951_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb08d5dba413e2c5bbf57676a5db22ae7f00ee83 --- /dev/null +++ b/marked/Rel-11/43_series/43059/6470d350326789d5306eabcb76533951_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d57f84b43d8b33cfe7c220071609c84b6bde14608c4254b2b9e10cd860b1753c +size 54213 diff --git a/marked/Rel-11/43_series/43059/6ca05954842b17f14dfd52f26b9d43d2_img.jpg b/marked/Rel-11/43_series/43059/6ca05954842b17f14dfd52f26b9d43d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b386e86451c701b349178421b0f87a5d41bce46 --- /dev/null +++ b/marked/Rel-11/43_series/43059/6ca05954842b17f14dfd52f26b9d43d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42efc057ab3ebeb63a7dee532d7b83db584e7bd885c8b6335769db557ac38417 +size 40608 diff --git a/marked/Rel-11/43_series/43059/7dfd8dd318dcfc36eaf4c967ddfb94c1_img.jpg b/marked/Rel-11/43_series/43059/7dfd8dd318dcfc36eaf4c967ddfb94c1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a29b6038257914e631a689e332cb26411e0db5f --- /dev/null +++ b/marked/Rel-11/43_series/43059/7dfd8dd318dcfc36eaf4c967ddfb94c1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0d6d1da871a80c49f60b611a48c236a48136886dc8918392d362850fac28ddb +size 112135 diff --git a/marked/Rel-11/43_series/43059/805c475f0859e607af0530ba43194bf1_img.jpg b/marked/Rel-11/43_series/43059/805c475f0859e607af0530ba43194bf1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9816d1ddaabe0b5ee6fa5b329916fe68d8107216 --- /dev/null +++ b/marked/Rel-11/43_series/43059/805c475f0859e607af0530ba43194bf1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83f67ee8670342b960a2e4a01392237ca2ae8ceb1ff6e688aefbebdb00accdd8 +size 18430 diff --git a/marked/Rel-11/43_series/43059/82b40cb8b2a5ac361973859400fa128a_img.jpg b/marked/Rel-11/43_series/43059/82b40cb8b2a5ac361973859400fa128a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..304486f453915cd0e9ef79a7896efed16e353c30 --- /dev/null +++ b/marked/Rel-11/43_series/43059/82b40cb8b2a5ac361973859400fa128a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2e44c4c81e4eec054d2442aaeab3cc694ff3cf76f490c05466830ccd7b117b0 +size 108741 diff --git a/marked/Rel-11/43_series/43059/981668c6be5792b778cccb1af38477e2_img.jpg b/marked/Rel-11/43_series/43059/981668c6be5792b778cccb1af38477e2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ff0cc4a3953e0957d49635cb1d44a2f0d4b2fbc --- /dev/null +++ b/marked/Rel-11/43_series/43059/981668c6be5792b778cccb1af38477e2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f0c308d40e559abdefeb42a2756435a3dc5545059f41af9e1317bf31f6e4c68 +size 40630 diff --git a/marked/Rel-11/43_series/43059/9b686adccf125267a013fa25721231a3_img.jpg b/marked/Rel-11/43_series/43059/9b686adccf125267a013fa25721231a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b89386b329f66ada7a1472fcc14b90fece72329 --- /dev/null +++ b/marked/Rel-11/43_series/43059/9b686adccf125267a013fa25721231a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:afc22b79d73522f2740f04bd80b229088eee250f405d634f95ad22b5723cf2f3 +size 100066 diff --git a/marked/Rel-11/43_series/43059/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-11/43_series/43059/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..009429158bcc8c266159626a17828139ec7ba2ec --- /dev/null +++ b/marked/Rel-11/43_series/43059/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:324fd6e5d2c2514c47d15083ced6b569538b24bdb6619af07a7bc2d1ed03ec24 +size 45435 diff --git a/marked/Rel-11/43_series/43059/bccc028d0e75bc30c41528056f581545_img.jpg b/marked/Rel-11/43_series/43059/bccc028d0e75bc30c41528056f581545_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91d80473134ce48a07682cc65eb6b10b8e687644 --- /dev/null +++ b/marked/Rel-11/43_series/43059/bccc028d0e75bc30c41528056f581545_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ddddbc65ba05725cac60494c4581e27201d808acf2ede67d762ccb6ec8ab43c +size 29947 diff --git a/marked/Rel-11/43_series/43059/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-11/43_series/43059/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df872daf7299509fb5e225348f6edfe7fdc8b080 --- /dev/null +++ b/marked/Rel-11/43_series/43059/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08389c3dc4951215a0ef6c59291999850a87ab3e4fe43a88a14ba3608dd6036c +size 33935 diff --git a/marked/Rel-11/43_series/43059/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-11/43_series/43059/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50c5a4ce0496f297e3c31fa47c7b6b0df4fd426c --- /dev/null +++ b/marked/Rel-11/43_series/43059/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0ddb9355265c580d6543dea41828a810b6884cc43c9a553ccbffc0c17b79af0 +size 79103 diff --git a/marked/Rel-11/43_series/43059/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg b/marked/Rel-11/43_series/43059/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a3f4f0dbad36f0d00944bdbb0bb84c0065ee6dc --- /dev/null +++ b/marked/Rel-11/43_series/43059/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b2fc126fc916cf1e79cb03d39a02ec17eb6588c0a510a9800b84b34fd6aa808d +size 16330 diff --git a/marked/Rel-11/43_series/43059/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg b/marked/Rel-11/43_series/43059/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d64d5156ce5610b3ab825fb7e5bddbb9a863fe2 --- /dev/null +++ b/marked/Rel-11/43_series/43059/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7790aec993133a168acd77b35966a8196f90516814772a3c3f0803e7789c6016 +size 26691 diff --git a/marked/Rel-11/43_series/43059/fe7304192caf64cda93b580c5e7e5c06_img.jpg b/marked/Rel-11/43_series/43059/fe7304192caf64cda93b580c5e7e5c06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..96e1c8a3c1c34dae8acdad4d99b22b538aca794b --- /dev/null +++ b/marked/Rel-11/43_series/43059/fe7304192caf64cda93b580c5e7e5c06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf986bee22e08ed314b2701977c9e31720eae47b6246f7efc3f8d0dbbf336cb8 +size 98636 diff --git a/marked/Rel-11/43_series/43064/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg b/marked/Rel-11/43_series/43064/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3f59742dd4459e285b4a1e822f805ba69b8f428 --- /dev/null +++ b/marked/Rel-11/43_series/43064/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca2a3697d208139840f641d1fa909139a84d67303a9f7201d986dc21d9888c6d +size 69539 diff --git a/marked/Rel-11/43_series/43064/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-11/43_series/43064/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c4222dc17e3495350ee63362d31409efd1c35dd --- /dev/null +++ b/marked/Rel-11/43_series/43064/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06a0ed23097aa40c45d85385eaeebd279149ed44ce9253ee7934a23ef76f6153 +size 105553 diff --git a/marked/Rel-11/43_series/43064/080a7af02bc47cf21ebfae4e0be39745_img.jpg b/marked/Rel-11/43_series/43064/080a7af02bc47cf21ebfae4e0be39745_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ee18790010ae14a41473d47252c32ab972db32f9 --- /dev/null +++ b/marked/Rel-11/43_series/43064/080a7af02bc47cf21ebfae4e0be39745_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa770a0958e4077baadca7a80e1db778c518125bf97f450164c99550a3c59dbf +size 85404 diff --git a/marked/Rel-11/43_series/43064/0931f3e098bd4539041de11c50cec2d2_img.jpg b/marked/Rel-11/43_series/43064/0931f3e098bd4539041de11c50cec2d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e80384164d7b6355a057613da950c13465ab631e --- /dev/null +++ b/marked/Rel-11/43_series/43064/0931f3e098bd4539041de11c50cec2d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:071162ca8390388f20ecb194f150f3f37a5c532c5a222dfe9796e818cd33ae74 +size 57573 diff --git a/marked/Rel-11/43_series/43064/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Rel-11/43_series/43064/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..96ee961680c8abe32971b1281b99af555d739f38 --- /dev/null +++ b/marked/Rel-11/43_series/43064/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6b32da461f4dba0ac9e640b641a1dbe7fa2a531217e44b17ac946d22232fa43 +size 84950 diff --git a/marked/Rel-11/43_series/43064/0cc154cbdde7cc6c39f394597c7aca0c_img.jpg b/marked/Rel-11/43_series/43064/0cc154cbdde7cc6c39f394597c7aca0c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d6a0bef204458f4b8812d4476adda12f98fe92f --- /dev/null +++ b/marked/Rel-11/43_series/43064/0cc154cbdde7cc6c39f394597c7aca0c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67713190853d6e25b8df6db46f476d66c0e79b348a68c4c4dde2cbde945b76de +size 62311 diff --git a/marked/Rel-11/43_series/43064/0ee9d674085524d589646a6c3fb21ec3_img.jpg b/marked/Rel-11/43_series/43064/0ee9d674085524d589646a6c3fb21ec3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3685726e278aebba45a77780be7eb97cf969b35f --- /dev/null +++ b/marked/Rel-11/43_series/43064/0ee9d674085524d589646a6c3fb21ec3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a67bdf879dc4c5233bb23d6f6f15c9b58abe310f46e99e27bc1c02c57ffa7fb4 +size 75225 diff --git a/marked/Rel-11/43_series/43064/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-11/43_series/43064/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40f543e365d98d2f2a26da3f7db9471d504e7270 --- /dev/null +++ b/marked/Rel-11/43_series/43064/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98628f0c114cbb155154885dfa95b25536857365a9cd9a24a7addd75bf9f6721 +size 87484 diff --git a/marked/Rel-11/43_series/43064/18e519d1f91133e080347562f681dfb5_img.jpg b/marked/Rel-11/43_series/43064/18e519d1f91133e080347562f681dfb5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..472c77cbb09ab11492f100afcd97030869a07c48 --- /dev/null +++ b/marked/Rel-11/43_series/43064/18e519d1f91133e080347562f681dfb5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:574b4784fed9f9d36a573bd99bcb8d9dd90c47c32901ef3cbdf12c375f35a578 +size 102066 diff --git a/marked/Rel-11/43_series/43064/1ce027dfd26183da52137cf990213724_img.jpg b/marked/Rel-11/43_series/43064/1ce027dfd26183da52137cf990213724_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1297b37f44b9d7a372a30cb0aa3d1ce48590587 --- /dev/null +++ b/marked/Rel-11/43_series/43064/1ce027dfd26183da52137cf990213724_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6aaf1eb02d883f6f518f82c952b42cf21adb6706003cac5d492495156568e4b3 +size 96945 diff --git a/marked/Rel-11/43_series/43064/20136850feb70fd71c7d41cdae203ebb_img.jpg b/marked/Rel-11/43_series/43064/20136850feb70fd71c7d41cdae203ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da5017247d92f5f6138ce69f33824e7baebc7f05 --- /dev/null +++ b/marked/Rel-11/43_series/43064/20136850feb70fd71c7d41cdae203ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef652765846bc99e427fbee5cca737da367bac0dc1a80d3a1fb4dc76c5c330b9 +size 22725 diff --git a/marked/Rel-11/43_series/43064/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-11/43_series/43064/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a548f8a24efb2d734ae28b5693c4e3cda9d5414 --- /dev/null +++ b/marked/Rel-11/43_series/43064/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33a147487914cb5c64ae0731c4c61a29b153bb0c2dee3d2ffb9558468937ea5c +size 59714 diff --git a/marked/Rel-11/43_series/43064/28f2f470a7b2446ae5f525123534383c_img.jpg b/marked/Rel-11/43_series/43064/28f2f470a7b2446ae5f525123534383c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51220115569e3740ba831c07085b9f4d355d4201 --- /dev/null +++ b/marked/Rel-11/43_series/43064/28f2f470a7b2446ae5f525123534383c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a426aea6ee555ebb7cecff5d1d5ac27bbdb67eeb7e2f3b18314d40f9ad37abba +size 107214 diff --git a/marked/Rel-11/43_series/43064/2a476a0b3dbc3429436246db4784ff9f_img.jpg b/marked/Rel-11/43_series/43064/2a476a0b3dbc3429436246db4784ff9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..108d2bbfb34554d1c15573047c2207d5862a5f42 --- /dev/null +++ b/marked/Rel-11/43_series/43064/2a476a0b3dbc3429436246db4784ff9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12ff84f895ba8a5faf3965a8b9d7cf1fdf7e257d1d82b7dfa5d9268e176fa813 +size 67682 diff --git a/marked/Rel-11/43_series/43064/2a9f9c6f1dc9e5b232d69c43882c83ab_img.jpg b/marked/Rel-11/43_series/43064/2a9f9c6f1dc9e5b232d69c43882c83ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..65ba61fadc7d505bf46fe8dfbd132a002f2ebb3d --- /dev/null +++ b/marked/Rel-11/43_series/43064/2a9f9c6f1dc9e5b232d69c43882c83ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec6c90184a5fc4c993ea82a0a7a8af991e355cf2e0dbb2b1a65d6b7f7246b757 +size 37601 diff --git a/marked/Rel-11/43_series/43064/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-11/43_series/43064/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f59f7bc396cddea13f1946e4b17c9dccf15aa52 --- /dev/null +++ b/marked/Rel-11/43_series/43064/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:165d12f843c4727ff95fa947aeab6e03673799a0055d3d79b4a8d6d4e7ace263 +size 77493 diff --git a/marked/Rel-11/43_series/43064/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-11/43_series/43064/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9922890d21cda14c11d13b9ac7711720658a5a6e --- /dev/null +++ b/marked/Rel-11/43_series/43064/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ee9f575c13db0065eda062b8a574936331213aaf14cadf8d5ab69ddbafc74a1 +size 91022 diff --git a/marked/Rel-11/43_series/43064/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-11/43_series/43064/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46023480fb895cf7452186103e073e6f69f5e255 --- /dev/null +++ b/marked/Rel-11/43_series/43064/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41135d9f3a54e4e834db893843bb77b8b545c9a61bb4710d8dfb7d2d51ca16a6 +size 92250 diff --git a/marked/Rel-11/43_series/43064/3337af75dfee8af7687b4f49914d6c93_img.jpg b/marked/Rel-11/43_series/43064/3337af75dfee8af7687b4f49914d6c93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ebb9d6bed59bd8e3e1942f6790adf19baececb6 --- /dev/null +++ b/marked/Rel-11/43_series/43064/3337af75dfee8af7687b4f49914d6c93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9573e2b70dde748aa149d15606757b7b89887dd70d2b028e8799fecd1083798 +size 61776 diff --git a/marked/Rel-11/43_series/43064/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg b/marked/Rel-11/43_series/43064/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f00edfbb5f7f5309cc92579a8aac52e69c23a160 --- /dev/null +++ b/marked/Rel-11/43_series/43064/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1f20e8ff72a6859962ff85bdc5c3a856169ee613020bf5e72dc56bec6c4a801 +size 20860 diff --git a/marked/Rel-11/43_series/43064/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-11/43_series/43064/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d755af401406827fcf474bbca0b5a3f7f4cf7402 --- /dev/null +++ b/marked/Rel-11/43_series/43064/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4cb5395cae01b6b4adeb089bd549a0fa62e65e8cbdcf99a26f3b1900d790bbc +size 89537 diff --git a/marked/Rel-11/43_series/43064/382a9c9e4816bd229191ab4591424dd8_img.jpg b/marked/Rel-11/43_series/43064/382a9c9e4816bd229191ab4591424dd8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72f544d71891b2b4cb76b2b60e618d40c612ae87 --- /dev/null +++ b/marked/Rel-11/43_series/43064/382a9c9e4816bd229191ab4591424dd8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e84ed5e043039217ac0f97e68d39840d782696506a49bb32ab389cd6d4afa3c0 +size 75693 diff --git a/marked/Rel-11/43_series/43064/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg b/marked/Rel-11/43_series/43064/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ddc27b4b3cc20ab741edbb7b5810bb4e3317b7c --- /dev/null +++ b/marked/Rel-11/43_series/43064/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a56bbd58797458ef70942a5ca823c6e0d59e092fc2d2575a294669d535f8e82c +size 91523 diff --git a/marked/Rel-11/43_series/43064/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/Rel-11/43_series/43064/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a4b3b383a3b8bdeb9a844438a3547da814bccc4 --- /dev/null +++ b/marked/Rel-11/43_series/43064/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe9aa9bbac8bff1a3f57c7459a5ebe8be9d850fda8dd9ceb29195fefd19d4fec +size 63827 diff --git a/marked/Rel-11/43_series/43064/421fc75480c21e7ebb25756826652367_img.jpg b/marked/Rel-11/43_series/43064/421fc75480c21e7ebb25756826652367_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af824ef59d5380bc137e2dcda3b9e1bfd8b89139 --- /dev/null +++ b/marked/Rel-11/43_series/43064/421fc75480c21e7ebb25756826652367_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64e915a1dd4aa27c2677465cdc4e5cc45e542aa3f50ddf4a83a8f4d43e2a46d3 +size 54405 diff --git a/marked/Rel-11/43_series/43064/4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg b/marked/Rel-11/43_series/43064/4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e81e2499cc5da1f07e69b7515e14d580243d71f5 --- /dev/null +++ b/marked/Rel-11/43_series/43064/4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:639f85ee69a42569f144b0efe3a07b05fd0122509d3d3c7a767cc19244cc53df +size 103578 diff --git a/marked/Rel-11/43_series/43064/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Rel-11/43_series/43064/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7d53737419ef0aec2633410f3689e505ec70d49 --- /dev/null +++ b/marked/Rel-11/43_series/43064/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce000cb83f9e7809bebfed21ec2635a1d7e7fcec52b26ed26c74b4697d6e46fa +size 87505 diff --git a/marked/Rel-11/43_series/43064/508bc574df81fa8d3027a374f6d155fc_img.jpg b/marked/Rel-11/43_series/43064/508bc574df81fa8d3027a374f6d155fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa11489f5942bd5ecd9f3982dd871a3407ecc681 --- /dev/null +++ b/marked/Rel-11/43_series/43064/508bc574df81fa8d3027a374f6d155fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d5d1b941caeb4cf32bb11b691b0ba5823f1e912a0cf0542f1d7d969933d6b4f +size 85108 diff --git a/marked/Rel-11/43_series/43064/57939c16065211317c5442cf2a4009e0_img.jpg b/marked/Rel-11/43_series/43064/57939c16065211317c5442cf2a4009e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43fdbc1637a5a0b85c40f2b4faf596bc42ba208e --- /dev/null +++ b/marked/Rel-11/43_series/43064/57939c16065211317c5442cf2a4009e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:668c8b0280cc0da13918bf46388dd9a6cb2db1d6acf460953e4c88a6313d9a06 +size 54857 diff --git a/marked/Rel-11/43_series/43064/6078636a87fbe0e699aab4a6fddd15d7_img.jpg b/marked/Rel-11/43_series/43064/6078636a87fbe0e699aab4a6fddd15d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7754f48125585c295b786b6f2bcee1507c456e49 --- /dev/null +++ b/marked/Rel-11/43_series/43064/6078636a87fbe0e699aab4a6fddd15d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2459a9698197edddb8c1e18bec08439358ef563da336ca423ca4d0f1c8e7d783 +size 14708 diff --git a/marked/Rel-11/43_series/43064/60a40901e77feeb97ab6cf9c6d9418c3_img.jpg b/marked/Rel-11/43_series/43064/60a40901e77feeb97ab6cf9c6d9418c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba91b81cfcb4cf5026b8b46b1485a1cf6555f81b --- /dev/null +++ b/marked/Rel-11/43_series/43064/60a40901e77feeb97ab6cf9c6d9418c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43fe1c108b92c9295ba9f308ae0301ec8527ec1db45cdf9fdc975f09b0535338 +size 55250 diff --git a/marked/Rel-11/43_series/43064/6231ba981d3d1ab7ce0cae71abd08c17_img.jpg b/marked/Rel-11/43_series/43064/6231ba981d3d1ab7ce0cae71abd08c17_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00bff821f0b06e9b16ee03d80c857cde04191673 --- /dev/null +++ b/marked/Rel-11/43_series/43064/6231ba981d3d1ab7ce0cae71abd08c17_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:164ef05a23585929c7ad31f28e86e64e5a556ba4ebbc0c2adcdb6e5e53243f9a +size 60769 diff --git a/marked/Rel-11/43_series/43064/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-11/43_series/43064/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3fd63a8f012a7f5e1b87261edb3a8aab05a28161 --- /dev/null +++ b/marked/Rel-11/43_series/43064/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b392e3fe1f92ec03010dcc2cf771ab92d53f8c43b051d63f20df80215cefd070 +size 76002 diff --git a/marked/Rel-11/43_series/43064/694df81535f89c7bfb9ef0df6f130dc0_img.jpg b/marked/Rel-11/43_series/43064/694df81535f89c7bfb9ef0df6f130dc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11603cf51df8c8deb7c39901ce5edb06d466bcdb --- /dev/null +++ b/marked/Rel-11/43_series/43064/694df81535f89c7bfb9ef0df6f130dc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:532a5b1916b39ebf7441eee12379ab82ad6ba07e1cb68febbf9725cf220a2f1a +size 74257 diff --git a/marked/Rel-11/43_series/43064/69e5f1993021af230d08c08aac97d9df_img.jpg b/marked/Rel-11/43_series/43064/69e5f1993021af230d08c08aac97d9df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e37dbc9489377057834999c2942a3f2d3064604e --- /dev/null +++ b/marked/Rel-11/43_series/43064/69e5f1993021af230d08c08aac97d9df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9230f137b63aeaa7c6a0030d8a3fc34caa27b97110d5e173341bf833ac0da94f +size 65214 diff --git a/marked/Rel-11/43_series/43064/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-11/43_series/43064/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..784eecccf7582c8d39aad4f0a068fe066d0f4806 --- /dev/null +++ b/marked/Rel-11/43_series/43064/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e93d89794b18db11b867f6aff14e7f5369ac2d6b9a03bf35ffc4728f4987e662 +size 76860 diff --git a/marked/Rel-11/43_series/43064/719ef0f734259484038b2434e5dc3f24_img.jpg b/marked/Rel-11/43_series/43064/719ef0f734259484038b2434e5dc3f24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a3743e5bdf110a6b5fb1809bcedf0843e955562f --- /dev/null +++ b/marked/Rel-11/43_series/43064/719ef0f734259484038b2434e5dc3f24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d207bb0059a29c6fdedc97427b8cb298a7b151d123caa166cab34e122f8deb4 +size 58139 diff --git a/marked/Rel-11/43_series/43064/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg b/marked/Rel-11/43_series/43064/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40a089eaf107ec36785f199d44650e865fd7d79f --- /dev/null +++ b/marked/Rel-11/43_series/43064/73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:320d3b13cd73dcac0913087af27a11080eb7e98866971f5342581b1ac53ecf89 +size 66187 diff --git a/marked/Rel-11/43_series/43064/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-11/43_series/43064/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b06b9a00106e29e1cb20f27977b1dcba41251524 --- /dev/null +++ b/marked/Rel-11/43_series/43064/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7fa62689fe86b2d3f6850f21e1adb6828373a943104a719ef6bc1d2bb95d6b62 +size 95484 diff --git a/marked/Rel-11/43_series/43064/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-11/43_series/43064/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c01046d146f36028d1abb87ad88dcbba0be7e50d --- /dev/null +++ b/marked/Rel-11/43_series/43064/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75827b3728a6c16003cd581687a3b3b24c143146fc5bd2864d444cc2e96f2fdf +size 71672 diff --git a/marked/Rel-11/43_series/43064/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/Rel-11/43_series/43064/7ed5d5770331f31ade15439a21c31425_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85a709823f56f82efff0fa2737ae5c385799ea2c --- /dev/null +++ b/marked/Rel-11/43_series/43064/7ed5d5770331f31ade15439a21c31425_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6caf28afd3268923c0787a42f543c4cd1efb21ce1343ecd521349189ca9d247d +size 78616 diff --git a/marked/Rel-11/43_series/43064/8269648391c59363ea61243864a2adf7_img.jpg b/marked/Rel-11/43_series/43064/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b335af54e76c85890c6c7f458a87d1137c25d3c --- /dev/null +++ b/marked/Rel-11/43_series/43064/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b894ccdf7ad0ca2af20fd551629dbd638f00fd8ee707e564f64e6e2ae218dae +size 86483 diff --git a/marked/Rel-11/43_series/43064/86bd357c573c9696393f5bde4d4cce4f_img.jpg b/marked/Rel-11/43_series/43064/86bd357c573c9696393f5bde4d4cce4f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4395e0da069024eb1191cbf5773a7701f52a98e1 --- /dev/null +++ b/marked/Rel-11/43_series/43064/86bd357c573c9696393f5bde4d4cce4f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a8d7e41baa4647a143bd6c4d51bee33c150907e5fafd292d23735f0272eb13e +size 80716 diff --git a/marked/Rel-11/43_series/43064/88a6d9692a52989caa6b208a1ba70dc0_img.jpg b/marked/Rel-11/43_series/43064/88a6d9692a52989caa6b208a1ba70dc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e605013c966f317fae9d9568cc3b1cffd8ae45e --- /dev/null +++ b/marked/Rel-11/43_series/43064/88a6d9692a52989caa6b208a1ba70dc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b88b18a6091f3a44506955b63723956c6692141f5b79d2814f8b5ef7ce4f79ab +size 19844 diff --git a/marked/Rel-11/43_series/43064/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-11/43_series/43064/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b6aff991ceb03e4ab4bb915ab928b158d588581 --- /dev/null +++ b/marked/Rel-11/43_series/43064/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4833019cb918cc3660f53cff063bcfec26c2528500349d02e0077c6e4561b0d +size 98396 diff --git a/marked/Rel-11/43_series/43064/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-11/43_series/43064/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04e59b1eeedccfea529629965536852308150004 --- /dev/null +++ b/marked/Rel-11/43_series/43064/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de1b42ce3f7d4783de636c942fe613e643967c2fbf01ae9a6bcb144a72888040 +size 26907 diff --git a/marked/Rel-11/43_series/43064/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-11/43_series/43064/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1d5f30405fa65b5af677b61f080c631b47c493a --- /dev/null +++ b/marked/Rel-11/43_series/43064/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15c5ee7a58218e8249b86cee0f17d5d3cd5c157e41fef894f1b84099b9c28710 +size 94067 diff --git a/marked/Rel-11/43_series/43064/9c05ae298f897f405d4f0c72d98cb2c7_img.jpg b/marked/Rel-11/43_series/43064/9c05ae298f897f405d4f0c72d98cb2c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f124bf91922d7ecebae0e9a8155b4992ba7bb2fb --- /dev/null +++ b/marked/Rel-11/43_series/43064/9c05ae298f897f405d4f0c72d98cb2c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77e4d45dc914efd71eb64df40094ab5c681ce163357fa3e23791d1ad16df5e60 +size 20673 diff --git a/marked/Rel-11/43_series/43064/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg b/marked/Rel-11/43_series/43064/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22e7d5881bdfa2a81863d1e69e236087b8b4b017 --- /dev/null +++ b/marked/Rel-11/43_series/43064/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7728c7737470a98f9936230e2d6c3aee330e29774a20650c6a946d0b7870f799 +size 88978 diff --git a/marked/Rel-11/43_series/43064/9d1df8fe4616b242b4846c78ea8970f5_img.jpg b/marked/Rel-11/43_series/43064/9d1df8fe4616b242b4846c78ea8970f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85c26360e69c9ccd8a45d67f875aa283f28f87f9 --- /dev/null +++ b/marked/Rel-11/43_series/43064/9d1df8fe4616b242b4846c78ea8970f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f9c89d98b502e824c6ea6f22ab65f648b739d6a085362588a9f5331df802d36 +size 41999 diff --git a/marked/Rel-11/43_series/43064/9e26cd5584f423e1b2155fb341db579f_img.jpg b/marked/Rel-11/43_series/43064/9e26cd5584f423e1b2155fb341db579f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d16ae7c6c2d414eb5a68c4c7d2facaa6e3186a04 --- /dev/null +++ b/marked/Rel-11/43_series/43064/9e26cd5584f423e1b2155fb341db579f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b46e619ddb6a7a0bb5aa266a242853ae0f6cbb997252f93021a0a7d358808274 +size 20927 diff --git a/marked/Rel-11/43_series/43064/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-11/43_series/43064/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55f542f2496a6e139547c8abd229df26521f6c0c --- /dev/null +++ b/marked/Rel-11/43_series/43064/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d3132e6975f5c5dc162fcd6363b1618898400ff1fe79ac5c5de194923340e2e +size 100016 diff --git a/marked/Rel-11/43_series/43064/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-11/43_series/43064/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad2466fd289e2b7a201b8de051afdb1c5ed96fbd --- /dev/null +++ b/marked/Rel-11/43_series/43064/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e466801444805504736439755a2a7d923aae1cf7f67a58b374e06530c95c487 +size 77324 diff --git a/marked/Rel-11/43_series/43064/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/Rel-11/43_series/43064/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dba9516f4799c7499206ac961a22d5a3bdac8f42 --- /dev/null +++ b/marked/Rel-11/43_series/43064/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a88e7e1d1b71b2af4c3652fcec767f3d3322067d5dbf2bbef64e31a0bd762fd8 +size 64748 diff --git a/marked/Rel-11/43_series/43064/a02b188a5fd52c99f84255322873bf29_img.jpg b/marked/Rel-11/43_series/43064/a02b188a5fd52c99f84255322873bf29_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61b4b8c6782074a49d833d7ed3bca2ca00487b9a --- /dev/null +++ b/marked/Rel-11/43_series/43064/a02b188a5fd52c99f84255322873bf29_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d455a620e28967602187bf27894d8103c77761bd05f43b87103a1b2d870acfa +size 22879 diff --git a/marked/Rel-11/43_series/43064/a04291a026e9ac4a7b644e556a0672b4_img.jpg b/marked/Rel-11/43_series/43064/a04291a026e9ac4a7b644e556a0672b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e90cfcd65c13baee73296441dd5064b442bebfe --- /dev/null +++ b/marked/Rel-11/43_series/43064/a04291a026e9ac4a7b644e556a0672b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1180a2bef2440a5aed9461b34ed40eb8ae13f919e02c4b5e9ad3a3d7324303b +size 20746 diff --git a/marked/Rel-11/43_series/43064/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-11/43_series/43064/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67a46b3fe427524d004506a6b91e2a7612836b0f --- /dev/null +++ b/marked/Rel-11/43_series/43064/a0e8fe7862a6d7341faf5dac275277cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b82d0b2c39669f4952cb6a4f43d7e1417004af3bac70a9e74c1b6d8297222ef5 +size 91805 diff --git a/marked/Rel-11/43_series/43064/a175bdeacb50b8a60869f6c68c5d0a07_img.jpg b/marked/Rel-11/43_series/43064/a175bdeacb50b8a60869f6c68c5d0a07_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed52d6fcc56a10dfffa7eb862bf3bc2369c73bd8 --- /dev/null +++ b/marked/Rel-11/43_series/43064/a175bdeacb50b8a60869f6c68c5d0a07_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c853022d13c6de5bef8507b78e4bfa0ee3a7ada89cda186a6d0b58447f099864 +size 49862 diff --git a/marked/Rel-11/43_series/43064/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg b/marked/Rel-11/43_series/43064/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc639739c9b4e7cf3ac2107cae5aa4ae1e0f7a8f --- /dev/null +++ b/marked/Rel-11/43_series/43064/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5e1d8917ea35a5189d42d507369af555d928d7b7bad8bd8a85d00196c8aec0d +size 89571 diff --git a/marked/Rel-11/43_series/43064/a3c1310e720178d2450a3748c7c75422_img.jpg b/marked/Rel-11/43_series/43064/a3c1310e720178d2450a3748c7c75422_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d11f225f9963196f5f9ad2f8d11b863fcefba80c --- /dev/null +++ b/marked/Rel-11/43_series/43064/a3c1310e720178d2450a3748c7c75422_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1f65978feea354338ce337f0acc400c8e7eb09d448fb8477f11d67d8071e7e8 +size 23591 diff --git a/marked/Rel-11/43_series/43064/a97518a839da75f8379c578562b01bc2_img.jpg b/marked/Rel-11/43_series/43064/a97518a839da75f8379c578562b01bc2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8398781fba3bf6c0e56a8af7a916617037cb0d0 --- /dev/null +++ b/marked/Rel-11/43_series/43064/a97518a839da75f8379c578562b01bc2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:80659f1add4487dee781e02587654a3d60092486ac9e440a6c561d6142534c8f +size 96971 diff --git a/marked/Rel-11/43_series/43064/aeb2a26a07219661191294dba528067a_img.jpg b/marked/Rel-11/43_series/43064/aeb2a26a07219661191294dba528067a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53462a3b45682c407269a249918304ad17ffe884 --- /dev/null +++ b/marked/Rel-11/43_series/43064/aeb2a26a07219661191294dba528067a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12e859a6f14061aae707d7c3b6125baa03ab5bceb95fd474b3c829220d996f7f +size 97472 diff --git a/marked/Rel-11/43_series/43064/b2f5606b9c7184c1c6070a290080a3e3_img.jpg b/marked/Rel-11/43_series/43064/b2f5606b9c7184c1c6070a290080a3e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e97bbe93fc00da79c9e2f6a9764b1c03d535636 --- /dev/null +++ b/marked/Rel-11/43_series/43064/b2f5606b9c7184c1c6070a290080a3e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8d58d861a09d4e50a80fc58b93936842c6b8fd20e295cccbae930779d904204 +size 86794 diff --git a/marked/Rel-11/43_series/43064/b44f89b176c971c7dd264c07bfef2c2a_img.jpg b/marked/Rel-11/43_series/43064/b44f89b176c971c7dd264c07bfef2c2a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aca4942a62f5b59e9cc4b31b48c6339c917e3dc7 --- /dev/null +++ b/marked/Rel-11/43_series/43064/b44f89b176c971c7dd264c07bfef2c2a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be24ce4851d4b086e74c8f492fe7632a3ecc0ec693ba4dd1c85cd419b77a15fa +size 92811 diff --git a/marked/Rel-11/43_series/43064/b63f41ca262d8ce9ef8affb62607f32b_img.jpg b/marked/Rel-11/43_series/43064/b63f41ca262d8ce9ef8affb62607f32b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02fe3d4ea39569b6bc17d2c6f284d4b0c80de7be --- /dev/null +++ b/marked/Rel-11/43_series/43064/b63f41ca262d8ce9ef8affb62607f32b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a85e677b58a0226d049582bdd7623cbf72383dc28a59511a3e2f380f11a77e22 +size 63001 diff --git a/marked/Rel-11/43_series/43064/bdb44cc8120caccddc2adf0c3db54261_img.jpg b/marked/Rel-11/43_series/43064/bdb44cc8120caccddc2adf0c3db54261_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..243db71d5807c62864ab69377710bc4e25517dcb --- /dev/null +++ b/marked/Rel-11/43_series/43064/bdb44cc8120caccddc2adf0c3db54261_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f6cd85b8458fe066dbfced339982af0d9f7f601ee15cf74f62984c66da3acf6 +size 20708 diff --git a/marked/Rel-11/43_series/43064/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Rel-11/43_series/43064/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dfefef77884bf77cf97ddfc84486d3eb223d6202 --- /dev/null +++ b/marked/Rel-11/43_series/43064/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4c5192d09ccc20d3e81b26d2e4616b8b387888e08dbfd6a973c3bbb40dabfaa +size 88024 diff --git a/marked/Rel-11/43_series/43064/c2f36c545b190860d04e1d84e58d22cc_img.jpg b/marked/Rel-11/43_series/43064/c2f36c545b190860d04e1d84e58d22cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ec2bfcfaa4678c77c33e3ee315d9358a5748f1d --- /dev/null +++ b/marked/Rel-11/43_series/43064/c2f36c545b190860d04e1d84e58d22cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b2b42075213a901adeb898870e7da3fddbf8ea1c9b1c38901a2e82d2d391aab +size 33177 diff --git a/marked/Rel-11/43_series/43064/c419b566d720267c499087add1506018_img.jpg b/marked/Rel-11/43_series/43064/c419b566d720267c499087add1506018_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5264c932b9701d28e2cd1c6042ace0e9b00a0ee8 --- /dev/null +++ b/marked/Rel-11/43_series/43064/c419b566d720267c499087add1506018_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9345f23b1ab4aacf4b096f88498d9e15a8b101db119ad0dcc033c599635ee1f6 +size 60250 diff --git a/marked/Rel-11/43_series/43064/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-11/43_series/43064/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1b80db64714d081a7ed67ffb09b31c456464c06 --- /dev/null +++ b/marked/Rel-11/43_series/43064/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cec34d70bc92bdc18dbf4fbec2ae61708571457ec634a226debcf16ee8abe9c7 +size 88513 diff --git a/marked/Rel-11/43_series/43064/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg b/marked/Rel-11/43_series/43064/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c70c797686702ab8ca3837e95ca82c9687dc1061 --- /dev/null +++ b/marked/Rel-11/43_series/43064/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70ec15fea1cafb878552f3c99b642e4291096dd172f1287d3e8a98a4ec7c0e3b +size 77875 diff --git a/marked/Rel-11/43_series/43064/cc893412ff9ca2426705e878c75548ba_img.jpg b/marked/Rel-11/43_series/43064/cc893412ff9ca2426705e878c75548ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb080896ea1d78fedffeba81e19ce269db1d7524 --- /dev/null +++ b/marked/Rel-11/43_series/43064/cc893412ff9ca2426705e878c75548ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:308578e6fc2c917083b10619707dc2e619b83afeb38453fd4d645b8d80233c76 +size 56028 diff --git a/marked/Rel-11/43_series/43064/da6000b1371b5528262d4f9cb2f2707c_img.jpg b/marked/Rel-11/43_series/43064/da6000b1371b5528262d4f9cb2f2707c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4f2cbf10718672c6f83d710b616d1bad81c9383 --- /dev/null +++ b/marked/Rel-11/43_series/43064/da6000b1371b5528262d4f9cb2f2707c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7d51881f0c7d764f6d6061d991f96172b2390667394276313f81ac230724608 +size 76462 diff --git a/marked/Rel-11/43_series/43064/df1966d80c74bc127f159a48f38b13ee_img.jpg b/marked/Rel-11/43_series/43064/df1966d80c74bc127f159a48f38b13ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..819a4afaf2d732a75a540046fa2293c37f64a815 --- /dev/null +++ b/marked/Rel-11/43_series/43064/df1966d80c74bc127f159a48f38b13ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7adff270ecb5f080056ce2212a587b2e3e57578920afb97bc46c5db8f3c51aa6 +size 94110 diff --git a/marked/Rel-11/43_series/43064/dfafe39c233a62ec8ebd71e42992c14d_img.jpg b/marked/Rel-11/43_series/43064/dfafe39c233a62ec8ebd71e42992c14d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0f212b4334679e4dd744760d8cdcb9e198fab56 --- /dev/null +++ b/marked/Rel-11/43_series/43064/dfafe39c233a62ec8ebd71e42992c14d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ad215a6d96ba6a7491562d09ba8f725126bc8f0fbf0dce75071b49510331a21 +size 22392 diff --git a/marked/Rel-11/43_series/43064/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-11/43_series/43064/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18768fdf2817dd3e1f4a1453ead20a91778bfd8c --- /dev/null +++ b/marked/Rel-11/43_series/43064/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40bfa26e66c47e73d9dd3ed7bf1687f2e35a6238c52f927a77257e416cb67c0a +size 45939 diff --git a/marked/Rel-11/43_series/43064/fcbc3c31776721edc98ceb1944ec438f_img.jpg b/marked/Rel-11/43_series/43064/fcbc3c31776721edc98ceb1944ec438f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5fa8cbfc48b2cf248e115207e7e68f92b30b37c6 --- /dev/null +++ b/marked/Rel-11/43_series/43064/fcbc3c31776721edc98ceb1944ec438f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61812d6b3054ce86482562f2a9a97e04291b277dd969f7be50c98e4652eb64f1 +size 57568 diff --git a/marked/Rel-11/43_series/43064/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/marked/Rel-11/43_series/43064/fd3cbb53e991f8209ba17b398f426e13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..690b9672175ddc55264577f4376093a40db9823a --- /dev/null +++ b/marked/Rel-11/43_series/43064/fd3cbb53e991f8209ba17b398f426e13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:925f9f0848f571f1cfc095f72a729d4e2d5aa41762c3a6dc542a03123451cc80 +size 66776 diff --git a/marked/Rel-11/43_series/43064/ffb6acd27b8e3a54392840948a75869f_img.jpg b/marked/Rel-11/43_series/43064/ffb6acd27b8e3a54392840948a75869f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..484a3bd18e77bb404386cf09052eb8ea23952b2b --- /dev/null +++ b/marked/Rel-11/43_series/43064/ffb6acd27b8e3a54392840948a75869f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4c652acdd93dbc8d53d9d1db4fd0bc39480448feda61011f518736856dc005f +size 54551 diff --git a/marked/Rel-11/43_series/43064/raw.md b/marked/Rel-11/43_series/43064/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0a6c4c7a7f27cc8414bdce531b6c90f2017dea2d --- /dev/null +++ b/marked/Rel-11/43_series/43064/raw.md @@ -0,0 +1,3344 @@ + + + + + + +# Contents + +| | | +|-------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 9 | +| 3 Abbreviations, symbols and definitions..... | 9 | +| 3.1 Abbreviations ..... | 9 | +| 3.2 Symbols..... | 11 | +| 3.2a Restrictions..... | 11 | +| 3.3 Definitions..... | 11 | +| 3.3.1 General ..... | 11 | +| 3.3.2 EGPRS mobile station..... | 11 | +| 3.3.3 Dual Transfer Mode ..... | 11 | +| 3.3.4 Downlink dual carrier configuration ..... | 11 | +| 3.3.5 Reduced Latency TBF..... | 12 | +| 3.3.5.1 Fast Ack/Nack Reporting procedure..... | 12 | +| 3.3.5.2 RTTI configuration..... | 12 | +| 3.3.6 EGPRS2 mobile station ..... | 13 | +| 3.3.6.1 EGPRS2 in the downlink..... | 13 | +| 3.3.6.1.1 EGPRS2-A and EGPRS2-B in the downlink..... | 13 | +| 3.3.6.2 EGPRS2 in the uplink..... | 13 | +| 3.3.6.2.1 EGPRS2-A and EGPRS2-B in the uplink..... | 14 | +| 4 Packet data logical channels ..... | 14 | +| 4.1 General ..... | 14 | +| 4.2 Packet Common Control Channel (PCCCH) and Compact (CPCCCH) ..... | 14 | +| 4.2.1 Packet Random Access Channel (PRACH) and Compact Packet Random Access Channel (CPRACH) - uplink only..... | 14 | +| 4.2.2 Packet Paging Channel (PPCH) and Compact Packet Paging Channel (CPPCH) - downlink only ..... | 14 | +| 4.2.3 Packet Access Grant Channel (PAGCH) and Compact Packet Access Grant Channel (CPAGCH) - downlink only..... | 14 | +| 4.3 Packet Broadcast Control Channel (PBCCH) and Compact Packet Broadcast Control Channel (CPBCCH) - downlink only..... | 14 | +| 4.4 Packet Traffic Channels ..... | 15 | +| 4.4.1 Packet Data Traffic Channel (PDTCH)..... | 15 | +| 4.5 Packet Dedicated Control Channels..... | 15 | +| 4.5.1 Packet Associated Control Channel (PACCH) ..... | 15 | +| 4.5.2 Packet Timing advance Control Channel, uplink (PTCCH/U) ..... | 15 | +| 4.5.3 Packet Timing advance Control Channel, downlink (PTCCH/D) ..... | 15 | +| 4.6 MBMS Common Control Channels..... | 15 | +| 4.6.1 MBMS Packet Random Access Channel (MPRACH) - uplink only ..... | 15 | +| 5 Mapping of packet data logical channels onto physical channels ..... | 15 | +| 5.1 General ..... | 15 | +| 5.2 Packet Common Control Channels (PCCCH and CPCCCH)..... | 16 | +| 5.2.1 Packet Random Access Channel (PRACH and CPRACH) ..... | 16 | +| 5.2.2 Packet Paging Channel (PPCH and CPPCH)..... | 16 | +| 5.2.3 Packet Access Grant Channel (PAGCH and CPAGCH) ..... | 17 | +| 5.2.4 Void ..... | 17 | +| 5.2a MBMS Common Control Channels (MPRACH) ..... | 17 | +| 5.3 Packet Broadcast Control Channel (PBCCH and CPBCCH) ..... | 17 | +| 5.3a Compact Frequency Correction Channel (CFCCH) ..... | 17 | +| 5.3b Compact Synchronization Channel (CSCH)..... | 17 | +| 5.4 Packet Timing advance Control Channel (PTCCH) ..... | 17 | +| 5.5 Packet Traffic Channels ..... | 18 | +| 5.5.1 Packet Data Traffic Channel (PDTCH)..... | 18 | +| 5.5.2 Packet Associated Control Channel (PACCH) ..... | 18 | +| 5.6 Downlink resource sharing..... | 18 | +| 5.7 Uplink resource sharing ..... | 19 | + +| | | | +|-----------|-------------------------------------------------------------------------------------------|----| +| 6 | Radio Interface (Um) ..... | 19 | +| 6.1 | Radio Resource management principles ..... | 19 | +| 6.1.1 | Allocation of resources for the GPRS ..... | 19 | +| 6.1.1.1 | Master-Slave concept..... | 19 | +| 6.1.1.2 | Capacity on demand concept..... | 20 | +| 6.1.1.3 | Procedures to support capacity on demand..... | 20 | +| 6.1.1.4 | Release of PDCH not carrying PCCCH ..... | 20 | +| 6.1.2 | Multiframe structure for PDCH..... | 21 | +| 6.1.2a | Multiframe structure for Compact PDCH ..... | 22 | +| 6.1.2b | Multiframe structure for PDCH/H..... | 23 | +| 6.1.3 | Scheduling of PBCCH information..... | 23 | +| 6.1.4 | SMS cell broadcast ..... | 23 | +| 6.1.5 | MS Multislot Capability ..... | 23 | +| 6.2 | Radio Resource operating modes..... | 24 | +| 6.2.1 | Packet idle mode..... | 24 | +| 6.2.2 | Packet transfer mode ..... | 24 | +| 6.2.3 | Dual transfer mode ..... | 24 | +| 6.2.3a | Broadcast/Multicast receive mode..... | 25 | +| 6.2.4 | Correspondence between Radio Resource operating modes and Mobility Management States..... | 25 | +| 6.2.5 | Transitions between RR operating modes ..... | 26 | +| 6.3 | Layered overview of radio interface ..... | 27 | +| 6.4 | Physical RF Layer ..... | 28 | +| 6.5 | Physical Link Layer ..... | 28 | +| 6.5.1 | Layer Services ..... | 28 | +| 6.5.2 | Layer Functions ..... | 28 | +| 6.5.3 | Service Primitives..... | 29 | +| 6.5.4 | Radio Block Structure ..... | 29 | +| 6.5.4.1 | Radio Block structure for data transfer for GPRS ..... | 29 | +| 6.5.4.2 | Radio Block structure for data transfer for EGPRS with FANR not activated ..... | 29 | +| 6.5.4.3 | Radio Block structure for data transfer for EGPRS with FANR activated or for EGPRS2 ..... | 30 | +| 6.5.4.4 | Radio Block structure for control message transfer..... | 31 | +| 6.5.4.4.1 | General format (CS-1)..... | 31 | +| 6.5.4.4.2 | Format for downlink control message for RTTI configuration (MCS-0) ..... | 31 | +| 6.5.5 | Channel Coding ..... | 31 | +| 6.5.5.1 | Channel coding for PDTCH ..... | 32 | +| 6.5.5.1.1 | Channel coding for GPRS PDTCH ..... | 32 | +| 6.5.5.1.2 | Channel coding for EGPRS PDTCH ..... | 34 | +| 6.5.5.1.3 | Channel coding for EGPRS2 PDTCH ..... | 41 | +| 6.5.5.2 | Channel coding for PACCH, PBCCH, PAGCH, PPCH and PTCCH..... | 63 | +| 6.5.5.2a | Channel coding for CPBCCH, CPAGCH, CPPCH and CSCH..... | 64 | +| 6.5.5.3 | Channel Coding for the PRACH, CPRACH and MPRACH..... | 64 | +| 6.5.5.3.1 | Coding of the 8 data bit Packet Access Burst ..... | 64 | +| 6.5.5.3.2 | Coding of the 11 data bit Packet Access Burst ..... | 64 | +| 6.5.6 | Cell Re-selection ..... | 64 | +| 6.5.6.1 | Measurements for Cell Re-selection..... | 65 | +| 6.5.6.2 | Broadcast Information ..... | 65 | +| 6.5.6.3 | Optional measurement reports and network controlled cell re-selection ..... | 65 | +| 6.5.6.4 | Network Assisted Cell Change ..... | 65 | +| 6.5.7 | Timing Advance ..... | 66 | +| 6.5.7.1 | Initial timing advance estimation..... | 66 | +| 6.5.7.2 | Continuous timing advance update..... | 67 | +| 6.5.7.2.1 | Mapping on the multiframe structure..... | 67 | +| 6.5.8 | Power control procedure..... | 69 | +| 6.5.8.0 | General ..... | 69 | +| 6.5.8.1 | MS output power ..... | 69 | +| 6.5.8.2 | BTS output power..... | 70 | +| 6.5.8.3 | Measurements at MS side..... | 70 | +| 6.5.8.3.1 | Deriving the C value ..... | 70 | +| 6.5.8.3.2 | Derivation of Channel Quality Report ..... | 70 | +| 6.5.8.4 | Measurements at BSS side..... | 71 | +| 6.5.9 | Scheduling the MS activities during the PTCCH and idle frames ..... | 71 | +| 6.5.10 | Discontinuous Reception (DRX)..... | 71 | + +| | | | +|-------------------------------|----------------------------------------------------------|-----------| +| 6.6 | Medium Access Control and Radio Link Control Layer ..... | 72 | +| 6.6.1 | Layer Services ..... | 73 | +| 6.6.2 | Layer Functions ..... | 73 | +| 6.6.3 | Service Primitives..... | 73 | +| 6.6.4 | Model of Operation ..... | 74 | +| 6.6.4.1 | Multiplexing MSs on the same PDCH ..... | 79 | +| 6.6.4.1.1 | Uplink State Flag: Dynamic Allocation ..... | 79 | +| 6.6.4.1.1.1 | Multiplexing of GPRS, EGPRS or EGPRS2 MSs ..... | 79 | +| 6.6.4.1.1.2 | Multiplexing of GPRS, EGPRS and EGPRS2 MSs..... | 80 | +| 6.6.4.1.2 | Void..... | 80 | +| 6.6.4.1.3 | Exclusive Allocation ..... | 80 | +| 6.6.4.2 | Temporary Block Flow ..... | 80 | +| 6.6.4.3 | Temporary Flow Identity ..... | 80 | +| 6.6.4.4 | Medium Access modes ..... | 81 | +| 6.6.4.5 | Acknowledged mode for RLC/MAC operation..... | 81 | +| 6.6.4.5.1 | GPRS ..... | 81 | +| 6.6.4.5.2 | EGPRS and EGPRS2 ..... | 81 | +| 6.6.4.6 | Unacknowledged mode for RLC/MAC operation..... | 82 | +| 6.6.4.6a | Non-persistent mode for RLC/MAC operation ..... | 82 | +| 6.6.4.7 | Mobile Originated Packet Transfer..... | 82 | +| 6.6.4.7.1 | Uplink Access ..... | 82 | +| 6.6.4.7.1.1 | On the (P)RACH ..... | 82 | +| 6.6.4.7.1.2 | On the main DCCH ..... | 84 | +| 6.6.4.7.2 | Dynamic/Extended Dynamic allocation..... | 85 | +| 6.6.4.7.2.1 | Uplink Packet Transfer..... | 85 | +| 6.6.4.7.2.2 | Release of the Resources ..... | 87 | +| 6.6.4.7.3 | Void..... | 88 | +| 6.6.4.7.4 | Exclusive Allocation ..... | 88 | +| 6.6.4.7.5 | Contention Resolution..... | 88 | +| 6.6.4.8 | Mobile Terminated Packet Transfer ..... | 89 | +| 6.6.4.8.1 | Packet Paging ..... | 89 | +| 6.6.4.8.2 | Downlink Packet Transfer..... | 89 | +| 6.6.4.8.3 | Release of the Resources..... | 91 | +| 6.6.4.8.4 | Packet Paging Notification..... | 91 | +| 6.6.4.9 | Simultaneous Uplink and Downlink Packet Transfer..... | 92 | +| 6.6.4.9.1 | MS Does Not Support Multiple TBF Procedures ..... | 92 | +| 6.6.4.9.2 | MS Supports Multiple TBF Procedures ..... | 92 | +| 6.7 | Abnormal cases in GPRS MS Ready State ..... | 93 | +| 6.8 | Void..... | 93 | +| 6.9 | MBMS Data Transfer..... | 93 | +| Annex A (informative): | Bibliography ..... | 94 | +| Annex B (informative): | Multiple TBF Feature ..... | 95 | +| B.1 | General..... | 95 | +| B.2 | Multiple TBF capability ..... | 95 | +| B.3 | Multiple TBF procedures ..... | 96 | +| B.3.1 | Data multiplexing options ..... | 96 | +| B.3.1.1 | Single TBF per upper layer flow ..... | 96 | +| B.3.1.2 | DL TBF sharing ..... | 96 | +| B.3.1.3 | Explicit UL TBF switching..... | 96 | +| B.3.2 | RLC/MAC Signalling..... | 96 | +| B.3.3 | TBF establishment..... | 96 | +| B.3.3.1 | TFI allocation..... | 96 | +| B.3.3.2 | Single TBF request / establishment ..... | 97 | +| B.3.3.3 | Multiple TBF establishment / reconfiguration..... | 97 | +| B.3.3.3.1 | Multiple uplink TBF request / establishment..... | 97 | +| B.3.3.3.2 | Multiple downlink TBF establishment..... | 98 | +| B.3.3.3.3 | Usage of multiple TBF assignment messages..... | 98 | +| B.4 | RLC/MAC Timers..... | 99 | +| B.4.1 | TBF timers..... | 99 | +| B.4.2 | Contention resolution timer ..... | 99 | + +B.5 CSN.1 coding of multiple TBF messages..... 99 +B.5.1 MULTIPLE TBF UPLINK ASSIGNMENT message ..... 99 +B.5.2 MULTIPLE TBF DOWNLINK ASSIGNMENT message..... 100 +B.5.3 MULTIPLE TBF TIMESLOT RECONFIGURE message..... 101 +Annex C (informative): Change history..... 102 + +# --- Foreword + +This Technical Specification has been produced by the 3rd 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 the overall description for lower-layer functions of the General Packet Radio Service (GPRS and EGPRS)) radio interface (Um). ). Within this TS the term GPRS refers to GPRS and EGPRS unless explicitly stated otherwise. + +The overall description provides the following information: + +- The services offered to higher-layer functions, +- The distribution of required functions into functional groups, +- A definition of the capabilities of each functional group, +- Service primitives for each functional group, including a description of what services and information flows are to be provided, and +- A model of operation for information flows within and between the functions. + +The present document is applicable to the following GPRS Um functional layers: + +- Radio Link Control functions, +- Medium Access Control functions, and +- Physical Link Control functions. + +The present document describes the information transfer and control functions to be used across the radio (Um) interface for communication between the MS and the Network, see Figure 1. + +3GPP TS 23.060 [3] describes the overall GPRS logical architecture and the GPRS functional layers above the Radio Link Control and Medium Access Control layer. + +3GPP TS 24.007 [5] contains a description in general terms of the structured functions and procedures of this protocol and the relationship of this protocol with other layers and entities. + +3GPP TS 44.018 [6] contains the definition of GPRS RLC/MAC procedures when operating on the Common Control Channel (CCCH). + +3GPP TS 44.060 [7] contains the definition of RLC/MAC functions when operating on a Packet Data Channel (PDCH). + +3GPP TS 44.064 [8] contains functional procedures for the Logical Link Control (LLC) layer above the RLC/MAC. + +3GPP TS 45 series defines the Physical Link layer and Physical RF layer. + +![Figure 1: Scope of GPRS Logical Radio Interface Architecture. The diagram shows a layered model of the GPRS logical architecture. At the top, there are two rows of boxes representing various network entities: 'User', 'LLC', 'RLC', 'MAC', 'PDCH', 'CCCH', 'PCH', 'AGCH', 'SDCCH', 'SACCH', 'BCCH', 'PCH', 'SDCCH', 'SACCH', 'BCCH', 'PDCH', 'RLC', 'LLC', and 'User'. Below these, a central section shows the 'Um' interface with 'Data in' and 'Data out' labels. The bottom section consists of four boxes labeled 'Physical Layer', 'Physical Layer', 'Physical Layer', and 'Physical Layer', which are connected to the 'Um' interface via lines representing data flows.](6078636a87fbe0e699aab4a6fddd15d7_img.jpg) + +Figure 1: Scope of GPRS Logical Radio Interface Architecture. The diagram shows a layered model of the GPRS logical architecture. At the top, there are two rows of boxes representing various network entities: 'User', 'LLC', 'RLC', 'MAC', 'PDCH', 'CCCH', 'PCH', 'AGCH', 'SDCCH', 'SACCH', 'BCCH', 'PCH', 'SDCCH', 'SACCH', 'BCCH', 'PDCH', 'RLC', 'LLC', and 'User'. Below these, a central section shows the 'Um' interface with 'Data in' and 'Data out' labels. The bottom section consists of four boxes labeled 'Physical Layer', 'Physical Layer', 'Physical Layer', and 'Physical Layer', which are connected to the 'Um' interface via lines representing data flows. + +**Figure 1: Scope of GPRS Logical Radio Interface Architecture** + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.060: "General Packet Radio Service (GPRS); Stage 2". +- [3] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [4] 3GPP TS 44.004: "Digital cellular telecommunications system; Layer 1; General requirements". +- [5] 3GPP TS 24.007: "Mobile radio interface signalling layer 3 General aspects" +- [6] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol" +- [7] 3GPP TS 44.060: "Radio Link Control/Medium Access Control (RLC/MAC) protocol". +- [8] 3GPP TS 44.064: "General Packet Radio Service (GPRS); Logical Link Control (LLC)". +- [9] 3GPP TS 44.065: "General Packet Radio Service (GPRS); Subnetwork Dependent Convergence Protocol (SNDPCP)". +- [10] 3GPP TS 45.001: "Physical layer on the radio path, General description". +- [11] 3GPP TS 45.002: "Multiplexing and multiple access on the radio path". +- [12] 3GPP TS 45.003: "Channel coding". +- [13] 3GPP TS 45.004: "Modulation". +- [14] 3GPP TS 45.005: "Radio transmission and reception". +- [15] 3GPP TS 45.008: "Radio subsystem link control". +- [16] 3GPP TS 45.010: "Radio subsystem synchronisation". +- [17] 3GPP TS 43.246: "Multimedia Broadcast Multicast Service (MBMS) in the GERAN; Stage 2". + +# --- 3 Abbreviations, symbols and definitions + +## 3.1 Abbreviations + +In addition to abbreviations in 3GPP TR 21.905 [1] and 3GPP TS 22.060 [2] the following abbreviations apply: + +| | | +|--------|--------------------------------------| +| ARQ | Automatic Repeat reQuest | +| BCS | Block Check Sequence | +| BEC | Backward Error Correction | +| BH | Block Header | +| BTTI | Basic Transmission Time Interval | +| CCN | Cell Change Notification | +| CFCCH | Compact Frequency Correction Channel | +| CPAGCH | Compact Packet Access Grant Channel | + +| | | +|---------------|---------------------------------------------------------------| +| CPBCCH | Compact Packet Broadcast Control Channel | +| CPCCCH | Compact Packet Common Control Channel | +| CPPCH | Compact Packet Paging Channel | +| CPRACH | Compact Packet Random Access Channel | +| CSCH | Compact Synchronization Channel | +| CS- i | GPRS Coding Scheme i | +| CU | Cell Update | +| DAS- i | EGPRS2 Downlink level A modulation and coding Scheme i | +| DBS- i | EGPRS2 Downlink level B modulation and coding Scheme i | +| DTM | Dual Transfer Mode | +| EGPRS | Enhanced GPRS | +| EGPRS2 | Enhanced GPRS phase 2 | +| FANR | Fast Ack/Nack Reporting | +| FBI | Final Block Indicator | +| FH | Frame Header | +| GGSN | Gateway GPRS Support Node | +| HCS | Header Check Sequence | +| HSR | Higher Symbol Rate | +| IR | Incremental Redundancy | +| LLC | Logical Link Control | +| MAC | Medium Access Control | +| MBMS | Multimedia Broadcast/Multicast Service | +| MCS- i | EGPRS Modulation and Coding Scheme i | +| MPRACH | MBMS Packet Random Access Channel | +| NSS | Network and Switching Subsystem | +| PACCH | Packet Associate Control Channel | +| PAGCH | Packet Access Grant Channel | +| PAN | Piggy-backed Ack/Nack | +| PBCCH | Packet Broadcast Control Channel | +| PC | Power Control | +| PCCCH | Packet Common Control Channel | +| PCS | PAN Check Sequence | +| PDCH | Packet Data Channel | +| PDTCH | Packet Data Traffic Channel | +| PDU | Protocol Data Unit | +| PFC | Packet Flow Context | +| PFI | Packet Flow Identifier | +| PL | Physical Link | +| PPCH | Packet Paging Channel | +| PRACH | Packet Random Access Channel | +| PSI | Packet System Information | +| PTCCH | Packet Timing Advance Control Channel | +| p-t-m | point-to-multipoint | +| RLC | Radio Link Control | +| RTTI | Reduced Transmission Time Interval | +| SGSN | Serving GPRS Support Node | +| SNDC | Subnetwork Dependent Convergence | +| TA | Timing Advance | +| TBF | Temporary Block Flow | +| TFI | Temporary Frame Identity | +| TTI | Transmission Time Interval | +| UAS- i | EGPRS2 Uplink level A modulation and coding Scheme i | +| UBS- i | EGPRS2 Uplink level B modulation and coding Scheme i | +| USF | Uplink State Flag | + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Gb | Interface between an SGSN and a BSC. | +| Um | Interface between MS and GPRS fixed network part. The Um interface is the GPRS network interface for providing packet data services over the radio to the MS. | + +## 3.2a Restrictions + +Independently of what is stated elsewhere in this and other 3GPP specifications, mobile station support for PBCCH and PCCCH is optional for A/Gb-mode of operation. The network shall never enable PBCCH and PCCCH. + +## 3.3 Definitions + +### 3.3.1 General + +In addition to GPRS specific definitions which can be found in 3GPP TS 22.060 [2] and 3GPP TS 23.060 [3] the following apply. + +When referring to radio resources (i.e. physical channels) provided by the network to the mobile station, the term "assignment" refers to granting of resources on a semi-static basis, whereas "allocation" refers to the dynamically changing permission to use those resources that have been "assigned" to it and are shared with other users. + +Multislot Capability: the capability of the mobile station to support Multislot Configurations. + +Multislot Class: a value which implicitly determines the Multislot Capability of the mobile station. + +Multislot Configuration: the set of receive and transmit timeslots assigned to the MS. + +### 3.3.2 EGPRS mobile station + +An EGPRS mobile station is a GPRS mobile station with additional capabilities for new radio access protocol features and new modulation and coding schemes. An EGPRS mobile station shall comply with GPRS requirements and the additional requirements defined for an EGPRS mobile station. The support of EGPRS is optional for the mobile station and the network. + +An EGPRS mobile station may additionally indicate support for EGPRS2 in uplink and/or downlink direction. In this case an EGPRS mobile station supports additional modulation and coding schemes, and may also support higher symbol rate, see sub-clause 3.3.6. The support of EGPRS2 is optional for the mobile station and the network. + +An EGPRS mobile station may additionally indicate the support of Reduced Latency. In this case an EGPRS mobile station may be assigned a TBF with FANR activated either in BTTI configuration or in RTTI configuration, see sub-clause 3.3.5. The support of Reduced Latency is optional for the mobile station and the network. + +### 3.3.3 Dual Transfer Mode + +In dual transfer mode, the mobile station is assigned resources providing an RR connection and one or more Temporary Block Flows on one or more physical channels. This feature is optional for the mobile station and the network. It is only applicable for a mobile station supporting GPRS, EGPRS or EGPRS2. Dual transfer mode is a subset of class A mode of operation, which is only possible if there is radio resource assignment co-ordination in the network. + +### 3.3.4 Downlink dual carrier configuration + +In a downlink dual carrier configuration, one or more PDCHs are assigned to a single MS on each of two different radio frequency channels on either the uplink or downlink, or both. On the downlink, radio blocks may be allocated on both radio frequency channels in any radio block period. On the uplink, radio blocks shall not be allocated on both radio frequency channels in any given radio block period. + +NOTE: A radio frequency channel in this context is defined by the frequency parameter(s) ARFCN for a non-hopping radio frequency channel or MA, MAIO and HSN for a hopping radio frequency channel. + +A downlink dual carrier configuration shall support multislot configurations either for packet switched connections or dual transfer mode. For a Dual Transfer Mode capable MS which supports Downlink Dual Carrier, support of Downlink Dual Carrier configurations for Dual Transfer Mode is optional. + +Downlink dual carrier is not supported in GPRS mode. + +### 3.3.5 Reduced Latency TBF + +A TBF applying Reduced Latency shall operate according to all EGPRS/EGPRS2 requirements, unless otherwise stated, with the Fast Ack/Nack Reporting procedure (see sub-clause 3.3.5.1). In addition, a TBF applying Reduced Latency is characterized by either RTTI configuration or BTTI configuration (see sub-clause 3.3.5.2). + +#### 3.3.5.1 Fast Ack/Nack Reporting procedure + +The Fast Ack/Nack reporting procedure (FANR) refers to the possibility to include, in a radio block for data transfer sent in one direction, piggy-backed ack/nack information relative to a TBF with FANR activated in the other direction. + +This is achieved by inserting a fixed-size piggy-backed ack/nack (PAN) field in the radio block. When a PAN field is inserted, a suitable Puncturing Scheme variant for the modulation and coding schemes in use is chosen, so that the RLC data field and the PAN field fit together in the radio block along with the RLC/MAC header. The presence of the PAN field, is signalled by the PAN indicator bit in the RLC/MAC header. When this bit is set the receiver shall use the corresponding Puncturing Scheme variant of the CPS indicated in the RLC/MAC header to decode the RLC data field. + +If a mobile station is assigned a TBF with FANR activated, all concurrent TBFs assigned to the mobile station shall have FANR activated irrespective of the RLC/MAC mode of each TBF (acknowledged mode, non-persistent mode or unacknowledged mode). + +Fast Ack/Nack reporting is not supported in GPRS TBF mode. + +#### 3.3.5.2 RTTI configuration + +In RTTI configuration, a radio block consisting of four bursts is sent using two PDCHs, i.e. a PDCH-pair, in each of two consecutive TDMA frames. In RTTI configuration, the time to transmit a radio block is half of a basic radio block period. + +NOTE: The term “basic radio block period” refers the time needed to transmit a radio block on one PDCH using BTTI configuration i.e. four TDMA frames, while the term “reduced radio block period” refers the time needed to transmit a radio block on a PDCH-pair using RTTI configuration, i.e. two TDMA frames. + +In RTTI configuration, a downlink TBF assignment consists of a number of PDCH-pairs, each PDCH-pair comprising two PDCHs. In a downlink dual carrier configuration (see sub-clause 3.3.4), up to 8 PDCH-pairs may be assigned per TBF. In a single carrier configuration up to 4 PDCH-pairs may be assigned per TBF. Two PDCHs constituting a downlink PDCH-pair need not be contiguous. + +In RTTI configuration, an uplink TBF assignment consists of up to four PDCH-pairs. The two PDCHs constituting an uplink PDCH-pair need not be contiguous. + +The PACCH shall have the same TTI configuration as the TBF with which it is associated. + +In each direction PDCH-pairs cannot be assigned so that they are partially overlapped, i.e. two different PDCH-pairs cannot have one PDCH in common. + +For an uplink TBF in RTTI configuration USFs can be sent in one of two ways: + +- RTTI USFs: a USF is sent in one reduced radio block period, i.e. a USF is mapped on four bursts transmitted on a downlink PDCH-pair during two consecutive TDMA frames. The USF allocates resources for one or four uplink radio blocks in the next reduced radio block period(s), depending on the value of USF\_GRANULARITY. +- BTTI USFs: two USFs are sent in a basic radio block period. One USF is mapped on four bursts transmitted on the first PDCH of a downlink PDCH-pair during four consecutive TDMA frames. This USF allocates resources for one or four uplink radio blocks in the first 2 TDMA frames of the next basic radio block period(s), depending on the value of USF\_GRANULARITY. A second USF is mapped on four bursts transmitted on the second PDCH of a downlink PDCH-pair during four consecutive TDMA frames. This USF allocates resources for one or four uplink radio blocks in the second 2 TDMA frames of the next basic radio block period(s), depending on the value of USF\_GRANULARITY. + +For each TBF, the network signals the corresponding TTI configuration (i.e. either basic or reduced) at TBF establishment/ reconfiguration. In case of RTTI configuration, the network also signals at uplink TBF establishment/reconfiguration the USF mode (i.e. either RTTI or BTTI) to be used for that TBF. + +For each assigned uplink PDCH-pair, the network may signal at TBF establishment/reconfiguration the “corresponding downlink PDCH-pair”, i.e. the DL PDCH-pair where USFs and PACCH/D are monitored. The timeslot numbers of the PDCHs constituting an uplink PDCH-pair may be different from those of the PDCHs constituting the corresponding downlink PDCH-pair. If no indication is provided, the corresponding downlink PDCH-pair will be the one with the same timeslot numbers as the uplink PDCH-pair. + +On a given downlink PDCH-pair all USFs shall be sent with the same USF mode. + +For a given mobile station, in each direction, the same TTI configuration shall be used for all TBFs (and PACCHs) assigned with one or more PDCH(s) in common in that direction. If a TBF is assigned on completely different PDCH(s) the TTI used may be different. + +For a given mobile station, different uplink TBFs may use different USF modes if assigned on completely different PDCH(s). + +A PDCH may be shared between RTTI TBF and BTTI TBF (assigned to different mobile stations). Alternatively, both PDCHs forming a PDCH-pair may be assigned to only support RTTI TBFs. + +RTTI configuration is not supported in GPRS TBF mode. + +### 3.3.6 EGPRS2 mobile station + +An EGPRS2 mobile station is an EGPRS mobile station supporting additional modulation and coding schemes on the downlink and/or the uplink. An EGPRS2 mobile station shall comply with GPRS requirements and the additional requirements defined for an EGPRS mobile station. The support of EGPRS2 is optional for the mobile station and the network. + +EGPRS2 features can be supported independently in the downlink and in the uplink. + +An EGPRS2 mobile station may additionally indicate the support of Reduced Latency. In this case an EGPRS2 mobile station may be assigned a TBF applying Reduced Latency, see sub-clause 3.3.5. The support of Reduced Latency is optional for the mobile station and the network. + +#### 3.3.6.1 EGPRS2 in the downlink + +A mobile station supporting EGPRS2 in the downlink supports additional modulation and coding schemes on the downlink. + +##### 3.3.6.1.1 EGPRS2-A and EGPRS2-B in the downlink. + +Two levels of support are defined for the EGPRS2 feature in the downlink: EGPRS2-A and EGPRS2-B. EGPRS2-A includes additional modulation and coding schemes. EGPRS2-B includes additional modulation and coding schemes as well as a higher symbol rate. For a MS, support of EGPRS2-B in the downlink implies support of EGPRS2-A in the downlink. + +#### 3.3.6.2 EGPRS2 in the uplink + +A mobile station supporting EGPRS2 in the uplink supports additional modulation and coding schemes on the uplink. + +##### 3.3.6.2.1 EGPRS2-A and EGPRS2-B in the uplink + +Two levels of support are defined for the EGPRS2 feature in the uplink: EGPRS2-A and EGPRS2-B. EGPRS2-A includes additional modulation and coding schemes. EGPRS2-B includes additional modulation and coding schemes as well as a higher symbol rate. For a MS, support of EGPRS2-B in the uplink implies support of EGPRS2-A in the uplink. + +# --- 4 Packet data logical channels + +NOTE: The text in this clause is informative. The normative text is in 3GPP TS 45.002 [11]. Where there is a conflict between these descriptions, the normative text has precedence. + +## 4.1 General + +This subclause describes the packet data logical channels that are supported by the radio subsystem. The packet data logical channels are mapped onto the physical channels that are dedicated to packet data. + +The physical channel dedicated to packet data traffic is called a Packet Data Channel (PDCH). + +## 4.2 Packet Common Control Channel (PCCCH) and Compact (CPCCCH) + +PCCCH and CPCCCH comprises logical channels for common control signalling used for packet data as described in the following subclauses. (See sub-clause 3.2a). + +### 4.2.1 Packet Random Access Channel (PRACH) and Compact Packet Random Access Channel (CPRACH) - uplink only + +PRACH and CPRACH are used by MS to initiate uplink transfer for sending data or signalling information. Packet Access burst and Extended Packet Access burst are used on PRACH. Extended Packet Access burst is used on CPRACH. + +### 4.2.2 Packet Paging Channel (PPCH) and Compact Packet Paging Channel (CPPCH) - downlink only + +PPCH and CPPCH are used to page an MS prior to downlink packet transfer. PPCH and CPPCH use paging groups in order to allow usage of DRX mode. PPCH can be used for paging of both circuit switched and packet data services. The paging for circuit switched services on PPCH is applicable for class A and B GPRS MSs in Network operation mode I, see 3GPP TS 23.060 [3]. + +### 4.2.3 Packet Access Grant Channel (PAGCH) and Compact Packet Access Grant Channel (CPAGCH) - downlink only + +PAGCH and CPAGCH are used in the packet transfer establishment phase to send resource assignment to an MS prior to packet transfer. + +## 4.3 Packet Broadcast Control Channel (PBCCH) and Compact Packet Broadcast Control Channel (CPBCCH) - downlink only + +PBCCH and CPBCCH broadcast packet data specific System Information. If PBCCH is not allocated, the packet data specific system information is broadcast on BCCH. For Compact, CPBCCH shall be allocated. CPBCCH and BCCH are mutually exclusive. (See sub-clause 3.2a). + +## 4.4 Packet Traffic Channels + +### 4.4.1 Packet Data Traffic Channel (PDTCH) + +PDTCH is a channel allocated for data transfer. It is temporarily dedicated to one MS or to a group of MSs in the case of p-t-m transmission. In the multislot operation, one MS or a group of MSs may use multiple PDTCHs in parallel for individual packet transfer. + +All packet data traffic channels are uni-directional, either uplink (PDTCH/U), for a mobile originated packet transfer or downlink (PDTCH/D) for a mobile terminated packet transfer. + +## 4.5 Packet Dedicated Control Channels + +### 4.5.1 Packet Associated Control Channel (PACCH) + +PACCH conveys signalling information related to a given MS. The signalling information includes e.g. acknowledgements and power control information. PACCH carries also resource assignment and reassignment + +messages, comprising the assignment of a capacity for PDTCH(s) and for further occurrences of PACCH. The PACCH shares resources with PDTCHs, that are currently assigned to one MS. Additionally, an MS that is currently involved in packet transfer, can be paged for circuit switched services on PACCH. + +### 4.5.2 Packet Timing advance Control Channel, uplink (PTCCH/U) + +PTCCH/U is used to transmit random access burst to allow estimation of the timing advance for one MS in packet transfer mode. + +PTCCH/U shall not be used for DTM. + +### 4.5.3 Packet Timing advance Control Channel, downlink (PTCCH/D) + +PTCCH/D is used to transmit timing advance information updates to several MS. One PTCCH/D is paired with several PTCCH/U's. + +PTCCH/D shall be ignored by MS operating in DTM. + +## 4.6 MBMS Common Control Channels + +### 4.6.1 MBMS Packet Random Access Channel (MPRACH) - uplink only + +The MPRACH is used by the MS during the initial counting procedure for MBMS (see 3GPP TS 44.060). Packet Access burst and Extended Packet Access burst are used on MPRACH. + +# --- 5 Mapping of packet data logical channels onto physical channels + +NOTE: The text in this clause is informative. The normative text is in 3GPP TS 45.002 [11]. Where there is a conflict between these descriptions, the normative text has precedence. + +## 5.1 General + +Different packet data logical channels can occur on the same physical channel (i.e. PDCH). The sharing of the physical channel is based on blocks of 4 consecutive bursts of one specific PDCH in 4 consecutive TDMA frames (for basic TTI configuration) or 2 bursts on each PDCH within a PDCH pair in 2 consecutive TDMA frames (for a reduced TTI configuration), except for PTCCH. The TBFs using reduced TTI and the TBFs using basic TTI sharing the same physical channel need to coexist within the overall block structure specified for the basic TTI. As such, for each assigned PDCH pair corresponding to a reduced TTI TBF, two consecutive reduced TTI radio blocks must be allocated within the time period spanned by a single radio block sent using the basic TTI. Each of the two reduced TTI radio blocks in this block structure could be allocated to different MSs or one of the reduced TTI blocks could be empty if not needed. The mapping in frequency of PDCH on to the physical channel shall be as defined in 3GPP TS 45.002 [11]. + +A PDCH may be either full-rate (PDCH/F) or half-rate (PDCH/H). PDCH/H is only applicable to DTM. See 3GPP TS 45.002 [11]. PDCH/H is not applicable for a reduced TTI configuration. + +GPRS, EGPRS and EGPRS2 employ the same physical layer, except for the PDTCH. + +On PRACH, CPRACH, MPRACH and PTCCH/U, access bursts are used. On all other packet data logical channels, radio blocks comprising 4 normal bursts are used. The only exception is some messages on uplink PACCH which comprise 4 consecutive access bursts (to increase robustness). + +## 5.2 Packet Common Control Channels (PCCCH and CPCCCH) + +At a given time, the logical channels of the PCCCH are mapped on different physical resources than the logical channels of the CCCH. + +The PCCCH and CPCCCH do not have to be allocated permanently in the cell. Whenever the PCCCH is not allocated, the CCCH shall be used to initiate a packet transfer. For Compact, CPCCCH shall be allocated. + +One given MS may use only a subset of the PCCCH and CPCCCH, the subset being mapped onto one physical channel (i.e. PDCH). + +The PCCCH, when it exists: + +- is mapped on one or several physical channels according to a 52-multiframe, In that case the PCCCH, PBCCH and PDTCH share same physical channels (PDCHs). + +The existence and location of the PCCCH shall be broadcast on the cell. (See sub-clause 3.2a). + +Since GSM phase 1 and phase 2 MS can only see and use the CCCH, the use on the PCCCH can be optimised for GPRS e.g. a PRACH of 11 bits can be used on uplink. + +For Compact, one radio frequency channel of the cell allocation shall be used to carry synchronization information and the CPBCCH, this shall be known as the primary Compact carrier. All other radio frequency channels of the cell allocation shall be known as secondary Compact carriers. + +For primary and secondary Compact carriers, CPCCCHs shall be allocated on only one timeslot (which is associated with a time group as defined in 3GPP TS 45.002 [11]). This time group is known as the serving time group and rotates over odd timeslot numbers as follows: 7, 5, 3, 1, 7, 5, .... The CPCCCH is mapped according to a Compact 52-multiframe and the serving time group rotation occurs between frame numbers (FN) mod 52 = 3 and 4. + +### 5.2.1 Packet Random Access Channel (PRACH and CPRACH) + +The PRACH and CPRACH are mapped on one or several physical channels. The physical channels on which the PRACH is mapped are derived by the MS from information broadcast on the PBCCH or BCCH. The physical channels on which the CPRACH is mapped are derived by the MS from information broadcast on the CPBCCH. + +PRACH and CPRACH are determined by the Uplink State Flag marked as free that is broadcast continuously on the corresponding downlink (see subclause 6.6.4.1). Additionally, a predefined fixed part of the multiframe structure for PDCH can be used as PRACH or CPRACH only and the information about the mapping on the physical channel is broadcast on PBCCH or CPBCCH. During those time periods an MS does not have to monitor the USF that is simultaneously broadcast on the downlink. + +### 5.2.2 Packet Paging Channel (PPCH and CPPCH) + +The PPCH and CPPCH are mapped on one or several physical channels. The exact mapping on each physical channel follows a predefined rule (see subclause 6.1.2), as it is done for the PCH. + +The physical channels on which the PPCH or CPPCH are mapped, as well as the rule that is followed on the physical channels, are derived by the MS from information broadcast on the PBCCH or CPBCCH. + +### 5.2.3 Packet Access Grant Channel (PAGCH and CPAGCH) + +The PAGCH and CPAGCH are mapped on one or several physical channels. The exact mapping on each physical channel follows a predefined rule (see subclause 6.1.2). + +The physical channels on which the PAGCH or CPAGCH are mapped, as well as the rule that is followed on the physical channels, are derived by the MS from information broadcast on the PBCCH or CPBCCH. + +### 5.2.4 Void + +### 5.2a MBMS Common Control Channels (MPRACH) + +The MPRACH is mapped on one physical channel. The physical channel on which the MPRACH is mapped is indicated to the MS by the network. + +The network indicates the value of the USF associated with the MPRACH on a particular PDCH in the notification message. The MPRACH is determined by the Uplink State Flag, which is broadcast on the corresponding downlink (see subclause 6.6.4.1), marked as the value indicated by the network. + +## 5.3 Packet Broadcast Control Channel (PBCCH and CPBCCH) + +The PBCCH and CPBCCH shall be mapped on one or several physical channels. The exact mapping on each physical channel follows a predefined rule (see subclause 6.1.2), as it is done for the BCCH. For Compact, CPBCCH shall be allocated. CPBCCH and BCCH are mutually exclusive. + +The existence of the PCCCH, and consequently the existence of the PBCCH, is indicated on the BCCH. (See sub-clause 3.2a). + +For Compact, one radio frequency channel of the cell allocation shall be used to carry synchronization information and the CPBCCH, this shall be known as the primary Compact carrier. All other radio frequency channels of the cell allocation shall be known as secondary Compact carriers. + +The CPBCCH shall be mapped on only one timeslot (which is associated with a time group as defined in 3GPP TS 45.002 [11]). This time group is known as the serving time group and rotates over odd timeslot numbers as follows: 7, 5, 3, 1, 7, 5, .... The CPBCCH is mapped according to a Compact 52-multiframe and the serving time group rotation occurs between frame numbers (FN) mod 52 = 3 and 4. The exact mapping follows a predefined rule (see subclause 6.1.2). + +## 5.3a Compact Frequency Correction Channel (CFCCH) + +The CFCCH is the same as the FCCH with one exception — the FCCH is mapped onto a 51-multiframe as defined in 3GPP TS 45.002 [11]. + +## 5.3b Compact Synchronization Channel (CSCH) + +The CSCH is similar to the SCH. The major difference is that the SCH is mapped onto a 51-multiframe as defined in 3GPP TS 45.002 [11]. This results in a different layout for the reduced TDMA frame number (RFN). + +## 5.4 Packet Timing advance Control Channel (PTCCH) + +Two defined frames of multiframe are used to carry PTCCH (see subclause 6.1.2). The exact mapping of PTCCH/U sub-channels and PTCCH/D shall be as defined in 3GPP TS 45.002 [11]. + +On PTCCH/U, access bursts are used. On PTCCH/D, four normal bursts comprising a radio block are used. + +In a downlink dual carrier configuration, an MS shall be assigned a PTCCH/D channel and a PTCCH/U sub-channel on one radio frequency channel only. + +## 5.5 Packet Traffic Channels + +### 5.5.1 Packet Data Traffic Channel (PDTCH) + +A PDTCH is mapped onto one physical channel (PDCH) or, in the case of RTTI configurations (see subclause 3.3.5), two physical channels (PDCH-pair). + +For one TBF, up to eight PDCHs or four PDCH-pairs, with different timeslot numbers but with the same frequency parameters, may be assigned to one MS at the same time. In the case of p-t-m transmission for MBMS, up to five downlink PDCH/Fs, with different timeslot numbers but with the same frequency parameters, may be assigned for one broadcast or multicast session. + +In the case of a downlink dual carrier configuration, up to 16 PDCHs or eight PDCH-pairs may be assigned to one TBF at the same time. + +### 5.5.2 Packet Associated Control Channel (PACCH) + +PACCH is dynamically allocated on a radio block basis on the same physical channel(s) used for carrying PDTCHs. However, one block PACCH allocation is also used on the physical channel carrying only PCCCH, when the MS is polled to acknowledge the initial assignment message. + +PACCH is of a bi-directional nature, i.e. it can dynamically be allocated both on the uplink and on the downlink regardless on whether the corresponding PDCH assignment is for uplink or downlink. + +The PACCH shall have the same TTI configuration as the TBF with which it is associated. + +If an MS is assigned one or more PDCH(s) /PDCH pair(s) on the uplink then, in the case of dynamic allocation (see subclause 6.6.4.4) the corresponding downlink timeslots/PDCH pair(s) have to be continuously monitored by the MS for possible occurrences of PACCH; in the case of extended dynamic allocation (see subclause 6.6.4.4), only the downlink timeslot/PDCH pair(s) corresponding to the lowest numbered assigned uplink timeslot has to be continuously monitored by the MS for possible occurrences of PACCH. The MS can use an uplink allocation for sending PACCH blocks whenever needed. + +In case of a downlink dual carrier configuration, PACCH blocks may be sent on the downlink on both radio frequency channels simultaneously. + +If an MS is assigned one or more PDCH(s) /PDCH pair(s) on the downlink, every occurrence of an uplink PACCH block is determined by polling in one of the preceding downlink blocks (transferred on the same PDCH(s)). The network can use the downlink assignment for sending PACCH blocks whenever needed. + +NOTE: Further requirements on PACCH operation are contained in 3GPP TS 44.060. + +## 5.6 Downlink resource sharing + +Different packet data logical channels can be multiplexed on the downlink on the same physical channel (i.e. PDCH). See details in 3GPP TS 45.002 [11]. The type of message which is indicated in the radio block header allows differentiation between the logical channels. Additionally, the MS identity allows differentiation between PDTCHs and PACCHs assigned to different MSs. The MS identity also allows differentiation between TBFs and p-t-m MBMS bearers. + +In addition, in dual transfer mode the network may dedicate a PDCH exclusively to an MS (i.e. the only PDTCH mapped onto that PDCH will be the one assigned to that MS). Even in the case of exclusive allocation, the network shall use the MS identity and the type of message in the radio block header. + +## 5.7 Uplink resource sharing + +Different packet data logical channels can be multiplexed on the uplink of the same physical channel (i.e. PDCH). See details in 3GPP TS 45.002 [11]. The type of message which is indicated in the radio block header, allows differentiation between the logical channels. Additionally, the MS identity allows differentiation between PDTCHs and PACCHs assigned to different MSs. + +In addition, in dual transfer mode the network may dedicate a PDCH exclusively to one MS. + +# --- 6 Radio Interface (Um) + +The logical architecture of the GPRS Um interface can be described using a reference model consisting of functional layers as shown in Figure 3. Layering provides a mechanism for partitioning communications functions into manageable subsets. + +Communication between the MS and the Network occurs at the Physical RF, Physical Link, Radio Link Control/Medium Access Control (RLC/MAC), Logical Link Control (LLC) and Subnetwork Dependent Convergence layers. + +## 6.1 Radio Resource management principles + +### 6.1.1 Allocation of resources for the GPRS + +A cell supporting GPRS may allocate resources on one or several physical channels in order to support the GPRS traffic. Those physical channels (i.e. PDCHs), shared by the GPRS MSs, are taken from the common pool of physical channels available in the cell. The allocation of physical channels to circuit switched services and GPRS is done dynamically according to the "capacity on demand" principles described below. + +Common control signalling required by GPRS in the initial phase of the packet transfer is conveyed on PCCCH, when allocated, or on CCCH. This allows the operator to have capacity allocated specifically to GPRS in the cell only when a packet is to be transferred. + +For Compact, common control signaling required by the mobile station in the initial phase of the packet transfer is conveyed on CPCCCH. + +#### 6.1.1.1 Master-Slave concept + +At least one PDCH, acting as a master, accommodates packet common control channels that carry all the necessary control signalling for initiating packet transfer (i.e. PCCCH), whenever that signalling is not carried by the existing CCCH, as well as user data and dedicated signalling (i.e. PDTCH and PACCH). Other PDCHs, acting as slaves, are used for user data transfer and for dedicated signalling. + +For Compact, one radio frequency channel of the cell allocation shall be used to carry synchronization information and the CPBCCH, this shall be known as the primary Compact carrier. All other radio frequency channels of the cell allocation shall be known as secondary Compact carriers. + +For the primary Compact carrier, timeslot numbers (TN) 1, 3, 5, and 7, acting as a master, accommodate packet common control channels that carry all necessary control signalling for initiating packet transfer as well as user data and dedicated signalling (i.e., PDTCH and PACCH). TNs 0, 2, 4, and 6, acting as slaves, are used for user data transfer and for dedicated signalling. + +For the secondary Compact carrier(s) carrying CPCCCH, timeslot numbers (TN) 1, 3, 5, and 7, acting as a master, accommodate packet common control channels that carry all necessary control signalling for initiating packet transfer as well as user data and dedicated signalling. TNs 0, 2, 4, and 6, acting as slaves, are used for user data transfer and for dedicated signalling. + +For the secondary Compact carrier(s) not carrying CPCCCH, timeslot numbers (TN) 0 through 7, acting as slaves, are used for user data transfer and for dedicated signalling. + +#### 6.1.1.2 Capacity on demand concept + +The GPRS does not require permanently allocated PDCHs. The allocation of capacity for GPRS can be based on the needs for actual packet transfers which is here referred to as the "capacity on demand" principle. The operator can, as well, decide to dedicate permanently or temporarily some physical resources (i.e. PDCHs) for the GPRS traffic. + +When the PDCHs are congested due to the GPRS traffic load and more resources are available in the cell, the Network can allocate more physical channels as PDCHs. + +However, the existence of PDCH(s) does not imply the existence of PCCCH. + +When no PCCCH is allocated in a cell, all GPRS attached MSs camp on the CCCH. + +In response to a Packet Channel Request sent on CCCH from the MS that wants to transmit GPRS packets, the network can assign resources on PDCH(s) for the uplink transfer.. After the transfer, the MS returns to CCCH. + +When PCCCH is allocated in a cell, all GPRS attached MSs camp on it. PCCCH can be allocated either as the result of the increased demand for packet data transfers or whenever there is enough available physical channels in a cell (to increase the quality of service). The information about PCCCH is broadcast on BCCH. When the PCCCH capacity is inadequate, it is possible to allocate additional PCCCH resources on one or several PDCHs. If the network releases the last PCCCH, the MS performs cell re-selection. + +For Compact, CPBCCH shall be allocated. CPBCCH is a stand-alone packet control channel for Compact. CPCCCH shall be allocated. The information about CPCCCH is broadcast on CPBCCH. When CPCCCH capacity is inadequate, it is possible to allocate additional CPCCCH resources on primary and secondary Compact carriers. + +#### 6.1.1.3 Procedures to support capacity on demand + +The number of allocated PDCHs in a cell can be increased or decreased according to demand. The following principles can be used for the allocation: + +- Load supervision: + +A load supervision function may monitor the load of the PDCHs and the number of allocated PDCHs in a cell can be increased or decreased according to demand. Load supervision function may be implemented as a part of the Medium Access Control (MAC) functionality. The common channel allocation function located in BSC is used for the GSM services. + +- Dynamic allocation of PDCHs: + +Unused channels can be allocated as PDCHs to increase the overall quality of service for GPRS. + +Upon resource demand for other services with higher priority, de-allocation of PDCHs can take place. + +#### 6.1.1.4 Release of PDCH not carrying PCCCH + +The fast release of PDCH is an important feature for possibility to dynamically share the same pool of radio resources for packet and circuit-switched services. + +There are following possibilities: + +- **Wait for all the assignments to terminate on that PDCH** +- **Individually notify all the users that have assignment on that PDCH** + +Packet Uplink Assignment and Packet Downlink Assignment messages can be used for that purpose. The network side has to send such notifications on PACCH(s) individually to each affected MS. + +- **Broadcast the notification about de-allocation** + +Simple and fast method to broadcast the Packet PDCH Release on all the PDCHs lying on the same carrier as the PDCH to be released. All MSs monitor the possible occurrences of PACCH on one channel and should capture such notification. + +In practice, a combination of all the methods can be used. + +There may occur the case where an MS remains unaware of the released PDCH. In that case, such MS may cause some interference when wrongly assuming that the decoded Uplink State Flag (see Subclause 6.6.4.1.) denotes the following uplink block period reserved to it. After not getting proper response from the network, the MS would self break the RLC connection. + +### 6.1.2 Multiframe structure for PDCH + +NOTE: The text in this clause is informative. The normative text is in 3GPP TS 45.002 [11]. Where there is a conflict between these descriptions, the normative text has precedence. + +The mapping in time of the logical channels is defined by a multiframe structure. The multiframe structure for PDCH in a basic TTI configuration consists of 52 TDMA frames, divided into 12 blocks (of 4 frames), 2 idle frames and 2 frames used for the PTCCH according to Figure 2. + +![Diagram of the multiframe structure for PDCH showing 52 TDMA frames divided into blocks. The diagram shows a sequence of frames with labels like 'X', 'T', 'B0', 'B1', 'B2', 'B3', 'B4', 'B5', 'B6', 'B7', 'B8', 'B9', 'B10', 'B11'. Below the frames, there are labels for 'PTCCH', 'PACCH', and 'PDCH'. A legend at the bottom defines X as Idle frame, T as Frame used for PTCCH, and B0 - B11 as Radio blocks.](2a9f9c6f1dc9e5b232d69c43882c83ab_img.jpg) + +**52 TDMA Frames** + +X = Idle frame +T = Frame used for PTCCH +B0 - B11 = Radio blocks + +Diagram of the multiframe structure for PDCH showing 52 TDMA frames divided into blocks. The diagram shows a sequence of frames with labels like 'X', 'T', 'B0', 'B1', 'B2', 'B3', 'B4', 'B5', 'B6', 'B7', 'B8', 'B9', 'B10', 'B11'. Below the frames, there are labels for 'PTCCH', 'PACCH', and 'PDCH'. A legend at the bottom defines X as Idle frame, T as Frame used for PTCCH, and B0 - B11 as Radio blocks. + +**Figure 2: Multiframe structure for PDCH** + +The multiframe structure for a reduced TTI configuration (2 PDCHs) is shown in Figure 2a. It follows the same multiframe structure for PDCH in a basic TTI configuration. + +![Figure 2a: Multiframe structure when a reduced TTI configuration is used. Two PDCHs are used. The diagram shows the mapping of logical channels (USF, RLC/MAC Hdr, HCS, E, FBI, Data, BCS, PAN, PCS) onto radio blocks (SB=8) across four Normal Bursts. The top row shows logical channel bit lengths: USF (3 bits), RLC/MAC Hdr (46 bits), HCS (558 bits), E (558 bits), FBI (30 bits), Data = x bits, BCS, E, FBI, Data = x bits, BCS, PAN (opt), PCS (opt). The middle row shows the mapping to radio blocks: 48 bits, 136 bits, 1686 bits (puncturing), 1686 bits (puncturing), 78 bits (opt). The bottom row shows the mapping to SB=8 blocks: 48 bits, 136 bits, 793/832 bits (P1), 793/832 bits (P2), 793/832 bits (P3), 793/832 bits (P1), 793/832 bits (P2), 793/832 bits (P3), 78 bits (opt). Arrows indicate the flow from logical channels to radio blocks and then to SB=8 blocks, with 'Rate 1/3 Turbo coding' and 'puncturing' indicated.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +Figure 2a: Multiframe structure when a reduced TTI configuration is used. Two PDCHs are used. The diagram shows the mapping of logical channels (USF, RLC/MAC Hdr, HCS, E, FBI, Data, BCS, PAN, PCS) onto radio blocks (SB=8) across four Normal Bursts. The top row shows logical channel bit lengths: USF (3 bits), RLC/MAC Hdr (46 bits), HCS (558 bits), E (558 bits), FBI (30 bits), Data = x bits, BCS, E, FBI, Data = x bits, BCS, PAN (opt), PCS (opt). The middle row shows the mapping to radio blocks: 48 bits, 136 bits, 1686 bits (puncturing), 1686 bits (puncturing), 78 bits (opt). The bottom row shows the mapping to SB=8 blocks: 48 bits, 136 bits, 793/832 bits (P1), 793/832 bits (P2), 793/832 bits (P3), 793/832 bits (P1), 793/832 bits (P2), 793/832 bits (P3), 78 bits (opt). Arrows indicate the flow from logical channels to radio blocks and then to SB=8 blocks, with 'Rate 1/3 Turbo coding' and 'puncturing' indicated. + +**Figure 2a: Multiframe structure when a reduced TTI configuration is used. Two PDCHs are used.** + +The mapping of logical channels onto the radio blocks is defined in the rest of this subclause by means of the ordered list of blocks (B0, B6, B3, B9, B1, B7, B4, B10, B2, B8, B5, B11). + +One PDCH that contains PCCCH (if any) is indicated on BCCH. That PDCH is the only one that contains PBCCH blocks. On the downlink of this PDCH, the first block (B0) in the ordered list of blocks is used as PBCCH. If required, up to 3 more blocks on the same PDCH can be used as additional PBCCH. Any additional PDCH containing PCCCH is indicated on PBCCH. + +On any PDCH with PCCCH (with or without PBCCH), the next up to 12 blocks in the ordered list of blocks are used for PAGCH, PDTCH or PACCH in the downlink. The remaining blocks in the ordered list are used for PPCH, PAGCH, PDTCH or PACCH in the downlink. In all cases, the actual usage of the blocks is indicated by the message type. On an uplink PDCH that contains PCCCH, all blocks in the multiframe can be used as PRACH, PDTCH or PACCH. Optionally, the first blocks in the ordered list of blocks can only be used as PRACH. The MS may choose to either ignore the USF (consider it as FREE) or use the USF to determine the PRACH in the same way as for the other blocks. + +The mapping of channels on multiframes are controlled by several parameters broadcast on PBCCH. + +On a PDCH that does not contain PCCCH, all blocks can be used as PDTCH or PACCH. The actual usage is indicated by the message type. + +Two frames are used for PTCCH (see 3GPP TS 45.002 [11]) and the two idle frames as well as the PTCCH frames can be used by the MS for signal measurements and BSIC identification. + +#### 6.1.2a Multiframe structure for Compact PDCH + +NOTE: The text in this clause is informative. The normative text is in 3GPP TS45.002 [11]. Where there is a conflict between these descriptions, the normative text has precedence. + +For Compact, one radio frequency channel of the cell allocation shall be used to carry synchronization information and the CPBCCH, this shall be known as the primary Compact carrier. All other radio frequency channels of the cell allocation shall be known as secondary Compact carriers. + +For the primary Compact carrier, timeslot numbers (TN) 1, 3, 5, and 7 accommodate packet common control channels (i.e., CPBCCH and CPCCCH) as well as user data and dedicated signalling (i.e., PDTCH and PACCH). TNs 0, 2, 4, and 6 are used for user data transfer and for dedicated signalling. + +For the secondary Compact carrier(s) carrying CPCCCH, timeslot numbers (TN) 1, 3, 5, and 7 accommodate packet common control channels as well as user data and dedicated signalling. TNs 0, 2, 4, and 6 are used for user data transfer and for dedicated signalling. + +For the secondary Compact carrier(s) not carrying CPCCCH, timeslot numbers (TN) 0 through 7 are used for user data transfer and for dedicated signalling. + +For Compact, a base station is typically assigned at least 3 frequencies (one per cell which translates into one primary Compact carrier per cell allocation) using a 1/3 frequency re-use pattern. Each cell is assigned one time group based + +upon which timeslot number is allocated for control (see 3GPP TS 45.002 [11]). This is known as the serving time group. + +Timeslot mapping and rotation of the control channels is used such that control channels belonging to a serving time group are rotated over odd timeslot numbers as follows: 7, 5, 3, 1, 7, 5 ... . The rotation occurs between frame numbers (FN) mod 52 = 3 and 4. Packet switched logical channels PDTCH, PACCH, and PTCCH are never rotated. + +For Compact, packet switched logical channels are mapped onto a Compact 52-multiframe. A Compact 52-multiframe consists of 12 blocks of 4 consecutive frames, 2 idle frames (which can be used for CFCCH and CSCH), and 2 frames used for PTCCH (see 3GPP TS 45.002 [11] and 3GPP TS 45.010 [16]) as shown in Figure 2. A block allocated to a given logical channel comprises one radio block or, in uplink only, 4 random access bursts. The type of channel may vary on a block by block basis. + +The mapping of CPBCCH onto the radio blocks is defined by means of the ordered list of blocks (B0, B6, B3, B9, B1, B7, B4, B10, B2, B8, B5, B11). On the downlink of the primary Compact carrier, the first block (B0) shall be used as CPBCCH. If required, up to 3 more blocks on the primary Compact carrier can be used as additional CPBCCH. The next up to 12 blocks in the ordered list of blocks are used for CPAGCH, PDTCH, and PACCH in the downlink. The remaining blocks in the ordered list are used for CPPCH and CPAGCH in the downlink. In all cases, the actual usage of the blocks is indicated by the message type. The same applies to secondary Compact carriers. + +In the uplink of the primary Compact carrier and secondary Compact carrier(s), all blocks in the multiframe can be used as CPRACH. However, a prioritization scheme is recommended (see 3GPP TS 45.002 [11]). The MS may choose to either ignore the USF (consider it as FREE) or use the USF to determine the CPRACH in the same way as for the other blocks. Optionally, the first blocks in the ordered list of blocks can only be used as CPRACH. + +The mapping of channels on multiframes are controlled by several parameters broadcast on CPBCCH. + +#### 6.1.2b Multiframe structure for PDCH/H + +NOTE: The text in this clause is informative. The normative text is in 3GPP TS 45.002 [11]. Where there is a conflict between these descriptions, the normative text has precedence. + +The mapping in time of the logical channels is defined by a multiframe structure. The multiframe structure for PDCH/H consists of 52 TDMA frames, divided into 6 blocks (of 4 frames) and 2 idle frames according to Figure 3. No frames are used for PTCCH (see 3GPP TS 45.002 [11]) and the two idle frames can be used by the MS for signal measurements and BSIC identification. + +![Figure 3: Multiframe structure for PDCH/H. The diagram shows the bit structure of a multiframe across four Normal Bursts. The top row shows the bit fields: USF (3 bits), RLC/MAC Hdr (46 bits), HCS (1 bit), E (1 bit), FBI (1 bit), Data = x bits (462 bits), BCS (1 bit), E (1 bit), FBI (1 bit), Data = x bits (462 bits), BCS (1 bit), PAN (opt) (3 bits), and PCS (opt) (3 bits). The second row shows the bit fields after Rate 1/3 Turbo coding and puncturing: 60 bits (USF), 136 bits (RLC/MAC Hdr), 1398 bits (Data), 1398 bits (Data), and 78 bits (opt) (PAN/PCS). The third row shows the bit fields for each Normal Burst: SB=8, 60 bits, 136 bits, 793/832 bits (P1), 793/832 bits (P2), 793/832 bits (P1), 793/832 bits (P2), and 78 bits (opt) (PAN/PCS).](421fc75480c21e7ebb25756826652367_img.jpg) + +Figure 3: Multiframe structure for PDCH/H. The diagram shows the bit structure of a multiframe across four Normal Bursts. The top row shows the bit fields: USF (3 bits), RLC/MAC Hdr (46 bits), HCS (1 bit), E (1 bit), FBI (1 bit), Data = x bits (462 bits), BCS (1 bit), E (1 bit), FBI (1 bit), Data = x bits (462 bits), BCS (1 bit), PAN (opt) (3 bits), and PCS (opt) (3 bits). The second row shows the bit fields after Rate 1/3 Turbo coding and puncturing: 60 bits (USF), 136 bits (RLC/MAC Hdr), 1398 bits (Data), 1398 bits (Data), and 78 bits (opt) (PAN/PCS). The third row shows the bit fields for each Normal Burst: SB=8, 60 bits, 136 bits, 793/832 bits (P1), 793/832 bits (P2), 793/832 bits (P1), 793/832 bits (P2), and 78 bits (opt) (PAN/PCS). + +Figure 3: Multiframe structure for PDCH/H + +A PDCH/H cannot be used as a PCCCH. On a PDCH/H all blocks can be used as PDTCH or PACCH. The actual usage is indicated by the message type. The PDCH/H shall only be assigned to a mobile station in conjunction with a TCH/H in the other subchannel of the physical channel. + +### 6.1.3 Scheduling of PBCCH information. + +An MS attached to GPRS shall not be required to monitor BCCH if a PBCCH exists. All system information relevant for GPRS and some information relevant for circuit switched services (e.g. the access classes) shall in this case be broadcast on PBCCH. For Compact, CPBCCH shall be allocated. CPBCCH and BCCH are mutually exclusive. + +In order to facilitate the MS operation, the network is required to transmit certain types of Packet System Information (PSI) messages in specific multiframes and specific PBCCH or CPBCCH blocks within the multiframes. The exact scheduling is in 3GPP TS 45.002 [11]. + +When no PCCCH is allocated, the MS camps on CCCH and receives all system information on BCCH. Any necessary GPRS specific system information shall in that case be broadcast on BCCH. For Compact, CPCCCH shall be allocated. + +### 6.1.4 SMS cell broadcast + +The MS reading of the primary and extended CBCH is occasionally interrupted by MS idle mode procedures when the MS is GPRS attached and in packet idle mode. + +### 6.1.5 MS Multislot Capability + +The mobile station informs the network of its multislot capability by declaring its multislot class. This implicitly determines a set of parameters that together define (see 3GPP TS 45.002 [11]): + +- The minimum time the network should allow the MS between a transmit and receive operations for purposes of re-tuning and/or monitoring. +- Limits on the number of timeslots that the mobile station is capable of receiving and/or transmitting in a TDMA frame. + +The MS declares a multislot class for GPRS and, if supported, EGPRS. If EGPRS2 is supported, the multislot class for EGPRS2 is the same as for EGPRS. + +In downlink dual carrier configurations: + +- The DTM EGPRS multislot class applies when Dual Transfer Mode is used, otherwise the EGPRS multislot class applies +- The maximum number of timeslots in a TDMA frame that the MS can receive is implicitly specified by the applicable multislot class, according to 3GPP TS 45.002 [11]. +- The MS signals to the network whether it supports some reduced value relative to this maximum. + +## 6.2 Radio Resource operating modes + +Radio Resource (RR) management procedures are characterised by two different RR operating modes. Each mode describes a certain amount of functionality and information allocated. RR procedures and RR operating modes are specified in 3GPP TS 24.007 [5]. + +### 6.2.1 Packet idle mode + +Packet idle mode is not applicable to an MS supporting DTM that has an ongoing RR connection. An MS that supports DTM, that has an ongoing RR connection and that has no assigned packet resource is in dedicated mode. + +In packet idle mode no Temporary Block Flow (see subclause 6.6.4.2) exists. Upper layers can require the transfer of LLC PDUs which, implicitly, may trigger the establishment of one or more TBFs and transition to packet transfer mode. + +In packet idle mode, an MS capable of multiple TBF operation may request the establishment of one or more uplink TBFs during a two-phase access. + +In packet idle mode, the MS listens to the PBCCH and to the paging sub-channel for the paging group the MS belongs to in idle mode. If PCCCH is not present in the cell, the mobile station listens to the BCCH and to the relevant paging sub-channels. + +While operating in packet idle mode, a mobile station belonging to GPRS MS class A may simultaneously enter the different RR service modes defined in 3GPP TS 44.018 [6]. A mobile station belonging to either of GPRS MS class B or C leaves both packet idle mode and packet transfer modes before entering dedicated mode, group receive mode or group transmit mode. + +### 6.2.2 Packet transfer mode + +Packet transfer mode is not applicable to a mobile station supporting DTM that has an ongoing RR connection. A DTM mobile station with an ongoing RR connection and with packet resources assigned is in dual transfer mode (see 6.2.3). + +In packet transfer mode, the mobile station is assigned radio resources providing one or more Temporary Block Flows where each TBF may operate on one or more physical channels. Continuous transfer of one or more LLC PDUs is possible. Concurrent TBFs (i.e. one uplink TBF and one downlink TBF) may be established in opposite directions when a mobile station does not support multiple TBF procedures. Multiple concurrent uplink and downlink TBFs may be established when a mobile station does support multiple TBF procedures. Transfer of LLC PDUs in RLC acknowledged, RLC unacknowledged or RLC non-persistent mode is provided. If a mobile station supports multiple TBF procedures and has two or more ongoing TBFs they shall use either GPRS TBF mode or EGPRS TBF mode (i.e. mixing of GPRS and EGPRS TBF modes shall not be supported). + +When selecting a new cell, a mobile station leaves the packet transfer mode, enters the packet idle mode where it switches to the new cell, reads the system information and may then resume to packet transfer mode in the new cell. + +While operating in packet transfer mode, a mobile station belonging to GPRS MS class A may simultaneously enter the different RR service modes defined in 3GPP TS 44.018. A mobile station belonging to either of GPRS MS class B or C leaves both packet idle mode and packet transfer modes before entering dedicated mode, group receive mode or group transmit mode. + +### 6.2.3 Dual transfer mode + +In dual transfer mode, the MS has an ongoing RR connection and is assigned radio resource providing one or more Temporary Block Flows where each TBF may operate on one or more physical channels. Continuous transfer of one or more LLC PDUs is possible. Concurrent TBFs (i.e. one uplink TBF and one downlink TBF) may be established in opposite directions. Multiple concurrent uplink and downlink TBFs may be established for a mobile station that supports multiple TBF procedures. Transfer of LLC PDUs in RLC acknowledged, RLC unacknowledged or RLC non-persistent mode is provided. + +While in dual transfer mode the MS performs all the tasks of dedicated mode. In addition, upper layers can require: + +- the release of all the packet resources, which triggers the transition to dedicated mode. +- the release of the RR resources, which triggers the transition to idle mode and packet idle mode. + +When handed over to a new cell, the MS leaves the dual transfer mode, enters the dedicated mode where it switches to the new cell, may read the system information messages sent on the SACCH and may then enter dual transfer mode in the new cell. + +### 6.2.3a Broadcast/Multicast receive mode + +In broadcast/multicast receive mode, the mobile station is assigned radio resources providing one or more p-t-m radio bearers for the reception of MBMS sessions; each p-t-m bearer may operate on one or more physical channels. Transfer of upper layer PDUs in RLC non-persistent mode is provided. + +In broadcast/multicast receive mode, the MS listens to the PBCCH and to the paging sub-channel on the PCCH for the paging group the MS belongs to in packet idle mode. If PBCCH is not present in the cell, the mobile station listens to the BCCH and to the relevant paging sub-channels on the CCCH for the paging group the MS belongs to. However, if the mobile station listens to an MBMS p-t-m bearer for which the network has indicated that system information and paging messages are sent on the PACCH, the MS does not have to listen to the (P)BCCH and, if the MS has an MS\_ID on that MBMS p-t-m bearer as well, to the paging sub-channels. + +When selecting a new cell, a mobile station leaves the broadcast/multicast receive mode and enters the packet idle mode. After switching to the new cell, the MS may resume the reception of the MBMS session before completing the acquisition of the system information if the location of the p-t-m bearer in the target cell has been provided by the network in the source cell. + +A mobile station belonging to either of GPRS MS class A, B or C leaves broadcast/multicast receive mode before entering dedicated mode, group receive mode, group transmit mode, packet transfer mode or dual transfer mode. + +### 6.2.4 Correspondence between Radio Resource operating modes and Mobility Management States + +The Mobility Management states are defined in 3GPP TS 23.060 [3]. Table 1 provides the correspondence between Radio Resource states and Mobility Management states: + +**Table 1a: Correspondence between RR operating modes and MM states (non-DTM capable MS)** + +| | | | | | +|------------------------|----------------------|------------------------------|----------|------------------| +| RR BSS | Packet transfer mode | Measurement report reception | No state | No state | +| RR MS | Packet transfer mode | Packet idle mode | | Packet idle mode | +| MM (NSS and MS) | Ready | | | Standby | + +**Table 1b: Correspondence between RR operating modes and MM states (DTM capable MS)** + +| | | | | | | | | +|-------------------------|--------------------|----------------|----------------------|------------------------------|----------|----------------|-------------------------| +| RR BSS | Dual transfer mode | Dedicated mode | Packet transfer mode | Measurement report reception | No state | Dedicated mode | No state | +| RR MS | | | | CS idle and packet idle | | | CS idle and packet idle | +| GMM (NSS and MS) | Ready | | | | | Standby | | + +Each state is protected by a timer. The timers run in the MS and the network. + +Packet transfer mode is guarded by RLC protocol timers. + +### 6.2.5 Transitions between RR operating modes + +The RR modes, and therefore the transitions between them, are different for each mode of operation (see 23.060). + +Figure 3a shows the four RR states for an MS in mode of operation A that does not support DTM. The four states can be regarded as the combination of two state machines with two RR states each: + +- on the circuit switched part, idle mode and dedicated mode +- on the GPRS part, packet idle mode and packet transfer mode + +![Figure 3a: RR operating modes and transitions for class A (DTM not supported). The diagram shows a burst structure with fields: USF (3 bits), RLC MAC Hdr (33 bits), HCS, E, FBI, Data = x bits (670 bits), BCS, PAN (opt), and PCS (opt) (30 bits). Below this, a table shows the mapping to physical bursts: USF (36 bits), RLC MAC Hdr (100 bits), Data (2022 bits with puncturing), and BCS (78 bits (opt)). These are further mapped to SB/8 units: 36 bits, 100 bits, 1170/1248 bits (P1), 1170/1248 bits (P2), and 78 bits (opt). The final output shows four 'Normal Burst' blocks.](88a6d9692a52989caa6b208a1ba70dc0_img.jpg) + +Figure 3a: RR operating modes and transitions for class A (DTM not supported). The diagram shows a burst structure with fields: USF (3 bits), RLC MAC Hdr (33 bits), HCS, E, FBI, Data = x bits (670 bits), BCS, PAN (opt), and PCS (opt) (30 bits). Below this, a table shows the mapping to physical bursts: USF (36 bits), RLC MAC Hdr (100 bits), Data (2022 bits with puncturing), and BCS (78 bits (opt)). These are further mapped to SB/8 units: 36 bits, 100 bits, 1170/1248 bits (P1), 1170/1248 bits (P2), and 78 bits (opt). The final output shows four 'Normal Burst' blocks. + +**Figure 3a: RR operating modes and transitions for class A (DTM not supported)** + +Figure 3b shows the RR modes and transitions for an MS in modes of operation A (when it supports DTM) and B. In the mode of operation B there are three RR modes: + +- (Packet) idle mode +- Packet transfer mode +- Dedicated mode (see 3GPP TS 44.018) + +For a mobile station that supports DTM class A mode of operation, there is an additional RR mode: dual transfer mode. This mode can be entered via a packet request procedure while in dedicated mode or RR connection establishment procedure while in packet transfer mode (see 3GPP TS 44.018 and 44.060). + +![Figure 3b: RR operating modes and transitions for classes A (DTM supported) and B. The diagram shows the mapping of data fields to physical bursts. At the top, fields are USF (3 bits), RLC/MAC Hdr (33 bits), HCS, E, FBI, Data = x bits (558 bits), BCS, PAN (opt) (30 bits), and PCS (opt). These are processed through Rate 1/3 Turbo coding. The resulting bits are mapped to four 'Normal Burst' slots. The mapping shows: USF (36 bits) and RLC/MAC Hdr (100 bits) are mapped to the first burst. Data bits are split: 1170/1248 bits go to the second burst (P1), and 1170/1248 bits go to the third burst (P2). The fourth burst contains 78 bits (opt) from PCS/PAN. A 'puncturing' step is indicated between the Turbo coding and the burst mapping.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +Figure 3b: RR operating modes and transitions for classes A (DTM supported) and B. The diagram shows the mapping of data fields to physical bursts. At the top, fields are USF (3 bits), RLC/MAC Hdr (33 bits), HCS, E, FBI, Data = x bits (558 bits), BCS, PAN (opt) (30 bits), and PCS (opt). These are processed through Rate 1/3 Turbo coding. The resulting bits are mapped to four 'Normal Burst' slots. The mapping shows: USF (36 bits) and RLC/MAC Hdr (100 bits) are mapped to the first burst. Data bits are split: 1170/1248 bits go to the second burst (P1), and 1170/1248 bits go to the third burst (P2). The fourth burst contains 78 bits (opt) from PCS/PAN. A 'puncturing' step is indicated between the Turbo coding and the burst mapping. + +**Figure 3b: RR operating modes and transitions for classes A (DTM supported) and B** + +Figure 3c shows the RR modes and transitions for an MS in mode of operation C. The MS can only be attached to either GSM or GPRS: + +- when it is GSM attached (and GPRS detached), there are two RR modes: idle mode and dedicated mode +- when it is GPRS attached (and GSM detached), there are two RR modes: packet idle mode and packet transfer mode. + +![Figure 3c: RR operating modes and transitions for class C. This diagram is similar to Figure 3b but with a different data field size. The top fields are USF (3 bits), RLC/MAC Hdr (33 bits), HCS, E, FBI, Data = x bits (462 bits), BCS, PAN (opt) (30 bits), and PCS (opt). These are processed through Rate 1/3 Turbo coding. The mapping to four 'Normal Burst' slots is: USF (36 bits) and RLC/MAC Hdr (100 bits) to the first burst. Data bits are split: 1170/1248 bits go to the second burst (P1), and 1170/1248 bits go to the third burst (P2). The fourth burst contains 78 bits (opt) from PCS/PAN. A 'puncturing' step is also indicated.](20136850feb70fd71c7d41cdae203ebb_img.jpg) + +Figure 3c: RR operating modes and transitions for class C. This diagram is similar to Figure 3b but with a different data field size. The top fields are USF (3 bits), RLC/MAC Hdr (33 bits), HCS, E, FBI, Data = x bits (462 bits), BCS, PAN (opt) (30 bits), and PCS (opt). These are processed through Rate 1/3 Turbo coding. The mapping to four 'Normal Burst' slots is: USF (36 bits) and RLC/MAC Hdr (100 bits) to the first burst. Data bits are split: 1170/1248 bits go to the second burst (P1), and 1170/1248 bits go to the third burst (P2). The fourth burst contains 78 bits (opt) from PCS/PAN. A 'puncturing' step is also indicated. + +**Figure 3c: RR operating modes and transitions for class C** + +## 6.3 Layered overview of radio interface + +The GPRS radio interface can be modelled as a hierarchy of logical layers with specific functions. An example of such layering is shown in Figure 3d. The various layers are briefly described in the following subclauses. + +The physical layer has been separated into two distinct sub-layers defined by their functions: + +- Physical RF layer performs the modulation of the physical waveforms based on the sequence of bits received from the Physical Link layer. The Physical RF layer also demodulates received waveforms into a sequence of bits which are transferred to the Physical Link layer for interpretation. +- Physical Link layer provides services for information transfer over a physical channel between the MS and the Network. These functions include data unit framing, data coding, and the detection and correction of physical medium transmission errors. The Physical Link layer uses the services of the Physical RF layer. + +The lower part of the data link layer is defined by following functions: + +- The RLC/MAC layer provides services for information transfer over the physical layer of the GPRS radio interface. These functions include backward error correction procedures enabled by the selective retransmission of erroneous blocks. The MAC function arbitrates access to the shared medium between a multitude of MSs and the Network. The RLC/MAC layer uses the services of the Physical Link layer. The layer above RLC/MAC (i.e., LLC described in 3GPP TS 23.060 [3] and defined in 3GPP TS 44.064 [8]) uses the services of the RLC/MAC layer on the Um interface. + +![Figure 3d: GPRS MS – Network Reference Model. This diagram illustrates the data flow and processing stages in a GPRS Mobile Station (MS). At the top, data units are shown with fields: USF (3 bits), RLC/MAC Hdr (58 bits), HCS, E, FBI, Data = x bits, BCS, E, FBI, Data = x bits, BCS, E, FBI, Data = x bits, BCS, E, FBI, Data = x bits, BCS, PAN (opt) (30 bits), and PCS (opt). These are grouped into four 606-bit blocks, each labeled 'Rate 1/3 Turbo coding'. Below this, the data is shown after turbo decoding: 60 bits, 152 bits, and four 1830-bit blocks. Each 1830-bit block undergoes 'puncturing' to produce four 'HSR Burst' units. Each HSR Burst contains 606/620 bits, subdivided into P1, P2, and P3. A 'SB=8' label is present on the left side of the HSR bursts.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +Figure 3d: GPRS MS – Network Reference Model. This diagram illustrates the data flow and processing stages in a GPRS Mobile Station (MS). At the top, data units are shown with fields: USF (3 bits), RLC/MAC Hdr (58 bits), HCS, E, FBI, Data = x bits, BCS, E, FBI, Data = x bits, BCS, E, FBI, Data = x bits, BCS, E, FBI, Data = x bits, BCS, PAN (opt) (30 bits), and PCS (opt). These are grouped into four 606-bit blocks, each labeled 'Rate 1/3 Turbo coding'. Below this, the data is shown after turbo decoding: 60 bits, 152 bits, and four 1830-bit blocks. Each 1830-bit block undergoes 'puncturing' to produce four 'HSR Burst' units. Each HSR Burst contains 606/620 bits, subdivided into P1, P2, and P3. A 'SB=8' label is present on the left side of the HSR bursts. + +**Figure 3d: GPRS MS – Network Reference Model** + +## 6.4 Physical RF Layer + +The GSM Physical RF layer is defined in 3GPP TS 45.0xx series recommendations, which specify among other things: + +- The carrier frequencies characteristics and GSM radio channel structures (3GPP TS 45.002 [11]); +- The modulation of the transmitted wave forms and the raw data rates of GSM channels (3GPP TS 45.004 [13]); and +- The transmitter and receiver characteristics and performance requirements (3GPP TS 45.005 [14]). + +In the case of EGPRS and EGPRS2 the modulation format is inherently signalled by the rotation factor of the training sequences as specified in 3GPP TS 45.004 [13] and 3GPP TS 45.002 [11], enabling blind detection in the receiver. + +## 6.5 Physical Link Layer + +The Physical Link layer operates above the physical RF layer to provide a physical channel between the MS and the Network. + +### 6.5.1 Layer Services + +The purpose of the Physical Link layer is to convey information across the GSM radio interface, including RLC/MAC information. The Physical Link layer supports multiple MSs sharing a single physical channel. + +The Physical Link layer provides communication between MSs and the Network. + +The Physical Link layer control functions provide the services necessary to maintain communications capability over the physical radio channel between the Network and MSs. Radio subsystem link control procedures are currently specified in 3GPP TS 45.008 [15]. Network controlled handovers are not used in the GPRS service. MS performed cell-reselection is used, see subclause 6.5.6. + +### 6.5.2 Layer Functions + +The Physical Link layer is responsible for: + +- Forward Error Correction (FEC) coding, allowing the detection and correction of transmitted code words and the indication of uncorrectable code words. The coding schemes are described in subclause 6.5.5. +- Interleaving of one Radio Block over four bursts in consecutive TDMA frames, as specified in 3GPP TS 45.003 [12]. +- Procedures for detecting physical link congestion. + +The Physical Link layer control functions include: + +- Synchronisation procedures, including means for determining and adjusting the MS Timing Advance to correct for variances in propagation delay , 3GPP TS 45.010 [16]; +- Monitoring and evaluation procedures for radio link signal quality; +- Cell (re-)selection procedures; +- Transmitter power control procedures; and +- Battery power conservation procedures, e.g. Discontinuous Reception (DRX) procedures. + +### 6.5.3 Service Primitives + +Table 2 lists the service primitives provided by the Physical Link layer to RLC/MAC layer. More detailed description is given in 3GPP TS 44.004 [4]. + +**Table 2: Service primitives provided by the Physical link layer** + +| Name | Request | indication | response | confirm | Comments | +|------------------|---------|------------|----------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PH-DATA | X | X | | | Used to pass message units containing frames used for RLC/MAC layer respective peer-to-peer communications to and from the physical layer. | +| PH-RANDOM ACCESS | X | X | | X | Used to request and confirm (in the MS) the sending of a random access frame and to indicate (in the network) the arrival of a random access frame. | +| PH-CONNECT | | X | | | Used to indicate that the physical connection on the packet data physical channel has been established. | +| PH-READY-TO-SEND | X | | | | Used by the physical layer to trigger, if applicable, piggy backing, the start of timer for the RLC/MAC layer and the forwarding a data unit to the physical layer | +| PH-EMPTY-FRAME | X | | | | Used by the RLC/MAC layer to indicate that no frame has to be transmitted after receiving the PH-READY-TO-SEND primitive | + +### 6.5.4 Radio Block Structure + +#### 6.5.4.1 Radio Block structure for data transfer for GPRS + +Different Radio Block structures for data transfer and control message transfer purposes are defined. The same Radio Block structure is used for control messages for all TBFs, with the exception of downlink control blocks for TBFs in RTTI configuration, where two Radio Block structures are possible. For detailed definition of radio block structure, see 3GPP TS 44.060 [7]. + +For GPRS, a Radio Block for data transfer consists of one MAC Header, one RLC header and one RLC data block. It is always carried by four normal bursts. + +| Radio Block | | | | +|-------------|------------|----------|-----| +| MAC header | RLC header | RLC data | BCS | + +**Figure 4: Radio Block structure for data transfer for GPRS** + +The MAC header contains control fields which are different for uplink and downlink directions. The MAC header has constant length, 8 bits. + +The RLC header contains control fields which are different for uplink and downlink directions. The RLC header has variable length. + +The RLC data field contains octets from one or more LLC PDUs. + +The Block Check Sequence (BCS) is used for error detection. + +#### 6.5.4.2 Radio Block structure for data transfer for EGPRS with FANR not activated + +For EGPRS, a Radio Block for data transfer consists of one RLC/MAC header and one or two RLC data blocks. It is always carried by four normal bursts. The interleaving depends on the MCS used. + +| Radio Block | | | | | +|----------------|-----|----------|--|-----| +| RLC/MAC header | HCS | RLC data | | BCS | + +**Figure 5: Radio Block structure for data transfer for EGPRS with FANR not activated** + +The RLC/MAC header contains control fields which are different for uplink and downlink directions. The RLC/MAC header has variable length. + +The RLC data field contains octets from one or more LLC PDUs. + +The Block Check Sequence (BCS) is used for error detection of the data part. + +The RLC data field and BCS are repeated per the number of RLC data blocks in the radio block. + +The Header Check Sequence (HCS) is used for error detection of the header part. + +The header part is independently coded from the data part and has its own check sequence. Tail biting (i.e. no explicit tail bits are appended before encoding. The encoder is initialised with the last information bits enabling tail biting decoding in the receiver) is used to reduce the size of the header. + +#### 6.5.4.3 Radio Block structure for data transfer for EGPRS with FANR activated or for EGPRS2 + +For an EGPRS TBF with FANR activated, a Radio Block for data transfer consists of one RLC/MAC header, one or two RLC data block(s) and, optionally, one PAN field. It is always carried by four normal bursts. The interleaving depends on the MCS used. + +For an EGPRS2 TBF, a Radio Block for data transfer consists of one RLC/MAC header, one up to four RLC data block(s) and optionally one PAN field. It is always carried by four normal bursts, or by four higher symbol rate bursts. The interleaving depends on the modulation and coding scheme used. + +| Radio Block | | | | | +|----------------|-----|----------|-----|------------------------| +| RLC/MAC header | HCS | RLC data | BCS | PAN and PCS (optional) | + +**Figure 5a: Radio Block structure for data transfer for EGPRS with FANR activated or EGPRS2** + +The RLC/MAC header contains control fields which are different for uplink and downlink directions. The RLC/MAC header has variable length. The RLC/MAC header indicates whether a PAN field and associated PCS field are included or not in the radio block. + +The PAN field contains piggy-backed ack/nack information sent in one direction to provide acknowledgement for a TBF with FANR activated in the other direction. + +The RLC data field contains octets from one or more LLC PDUs. + +The Block Check Sequence (BCS) is used for error detection of the data part. + +The Header Check Sequence (HCS) is used for error detection of the header part. + +The PAN Check Sequence (PCS) is used for error detection of the PAN field. + +The header part, the data part and the PAN field are all coded independently and each has its own check sequence. Tail biting (i.e. no explicit tail bits are appended before encoding. The encoder is initialised with the last information bits enabling tail biting decoding in the receiver) is used for the encoding of the header. + +#### 6.5.4.4 Radio Block structure for control message transfer + +##### 6.5.4.4.1 General format (CS-1) + +The general format of the Radio Block structure for control message transfer is applicable to any control message except on downlink PDCH pairs supporting TBFs in RTTI configuration using the BTTI USF mode. It may optionally be used on downlink PDCH pairs supporting TBFs in RTTI configuration using the RTTI USF mode. + +This format, based on CS-1 encoding, consists of one MAC header, one RLC/MAC Control Block and one Block Check Sequence. It is always carried by four normal bursts. + +| Radio Block | | | +|-------------|-------------------------|-----| +| MAC header | RLC/MAC Control Message | BCS | + +**Figure 6: Radio Block structure for control message - general format** + +The MAC header contains control fields which are different for uplink and downlink directions. The MAC header has constant length, 8 bits. + +The Block Check Sequence (BCS) is used for error detection. + +The RLC/MAC Control message field contains one RLC/MAC control message. + +##### 6.5.4.4.2 Format for downlink control message for RTTI configuration (MCS-0) + +This format shall be used on downlink PDCH pairs supporting TBFs in RTTI configuration using the BTTI USF mode, and may optionally be used on downlink PDCH pairs supporting TBFs in RTTI configuration using the RTTI USF mode. + +This format, based on MCS-0 encoding, consists of one RLC/MAC header, one Header Check Sequence, one RLC/MAC Control Block and one Block Check Sequence. It is always carried by four normal bursts. + +| Radio Block | | | +|----------------------|-----|-------------------------| +| RLC/MAC header + BCS | HCS | RLC/MAC control message | + +**Figure 6a: Radio Block structure for downlink control message for RTTI configuration** + +The RLC/MAC header together with the BCS has a constant length of 31 bits. + +The Header Check Sequence (HCS) is used for error detection of the header part. + +The RLC/MAC Control message field contains one RLC/MAC control message. + +The Block Check Sequence (BCS) is used for error detection of the RLC/MAC control message. + +### 6.5.5 Channel Coding + +NOTE: The text in this subclause is informative. The normative text is in 3GPP TS 45.003 [12]. Where there is a conflict between these descriptions, the normative text has precedence. + +Four coding schemes, CS-1 to CS-4, are defined for the GPRS packet data traffic channels. For all other GPRS packet control channels than Packet Random Access Channel (PRACH) and Packet Timing Advance Control Channel on Uplink (PTCCH/U), coding scheme CS-1 is always used. For access bursts on PRACH, two coding schemes are specified. + +All coding schemes (CS-1 to CS-4) are mandatory for MSs supporting GPRS. CS-1 is mandatory for a network supporting GPRS. + +Nine modulation and coding schemes, MCS-1 to MCS-9, are defined for the EGPRS packet data traffic channels. For all EGPRS packet control channels the corresponding GPRS packet control channel coding is used. MSs supporting EGPRS shall support MCS-1 to MCS-9 in downlink and MCS-1 to MCS-4 in uplink. In case an MS supporting EGPRS is 8-PSK capable in uplink, it shall also support MCS-5 to MCS-9 in uplink. A network supporting EGPRS may support only some of the MCSs. + +Eight modulation and coding schemes, DAS-5 to DAS-12, are defined for the EGPRS2-A packet data traffic channels for the downlink. Eight modulation and coding schemes, DBS-5 to DBS-12, are defined for the EGPRS2-B packet data traffic channels for the downlink. Four EGPRS modulation and coding schemes, MCS-1 to MCS-4, are also used for downlink EGPRS2. + +Five modulation and coding schemes, UAS-7 to UAS-11, are defined for the EGPRS2-A packet data traffic channels for the uplink. Six EGPRS modulation and coding schemes, MCS-1 to MCS-6, are also used for uplink EGPRS2-A. Eight modulation and coding schemes, UBS-5 to UBS-12, are defined for the EGPRS2-B packet data traffic channels for the uplink. Four EGPRS modulation and coding schemes, MCS-1 to MCS-4, are also used for uplink EGPRS2-B. + +MSs supporting EGPRS2-A in the downlink shall support all of DAS-5 to DAS-12. MSs supporting EGPRS2-B in the downlink shall support all of DBS-5 to DBS-12, in addition to DAS-5 to DAS-12. MSs supporting EGPRS2-A in the uplink shall support all of UAS-7 to UAS-11. MSs supporting EGPRS2-B in the uplink shall support all of UBS-5 to UBS-12, in addition to UAS-7 to UAS-11. For all EGPRS2 packet control channels, the corresponding GPRS control channel coding is used. MSs supporting EGPRS2 in the downlink and/or the uplink shall support EGPRS. + +A network supporting EGPRS2 may support only some of the modulation and coding schemes, DAS-5 to DAS-12, DBS-5 to DBS-12, UAS-7 to UAS-11, and UBS-5 to UBS-12. + +For all EGPRS2 packet control channels in BTTI configuration, the corresponding GPRS packet control channel coding is used. + +In RTTI configuration, the PACCH in the uplink shall be always encoded using CS-1 and the PACCH in the downlink may be encoded using MCS-0 or CS-1. MCS-0 shall be used for PACCH in the downlink associated with TBF using RTTI configuration which shares PDCH(s) with TBF(s) using BTTI configuration. + +#### 6.5.5.1 Channel coding for PDTCH + +##### 6.5.5.1.1 Channel coding for GPRS PDTCH + +Four different coding schemes, CS-1 to CS-4, are defined for the GPRS Radio Blocks carrying RLC data blocks. The block structures of the coding schemes are shown in Figure 7 and Figure 8. + +![Figure 7: Radio Block structure for CS-1 to CS-3. The diagram shows the internal structure of a radio block, starting with fields like USF, RLC/MAC Hdr, HCS, E, FBI, Data = x bits, BCS, E, FBI, Data = x bits, BCS, E, FBI, Data = x bits, BCS, E, FBI, Data = x bits, BCS, PAN (opt), PCS (opt). It details the bit distribution (3 bits, 70 bits, 558 bits, 558 bits, 558 bits, 558 bits, 30 bits) and the application of Rate 1/3 Turbo coding and puncturing to generate HSR Bursts.](da6000b1371b5528262d4f9cb2f2707c_img.jpg) + +The diagram illustrates the bit structure of a radio block for CS-1 to CS-3. At the top, the fields and their bit counts are listed: USF (3 bits), RLC/MAC Hdr (70 bits), HCS (1 bit), E (1 bit), FBI (1 bit), Data = x bits (558 bits), BCS (1 bit), E (1 bit), FBI (1 bit), Data = x bits (558 bits), BCS (1 bit), E (1 bit), FBI (1 bit), Data = x bits (558 bits), BCS (1 bit), E (1 bit), FBI (1 bit), Data = x bits (558 bits), BCS (1 bit), PAN (opt) (30 bits), and PCS (opt) (30 bits). Below this, the total bit counts for each field are shown: 80 bits for USF, 188 bits for RLC/MAC Hdr, 1686 bits for the first Data block, 1686 bits for the second Data block, 1686 bits for the third Data block, 1830 bits for the fourth Data block, and 80 bits (opt) for PAN and PCS. The middle section shows the application of 'puncturing' to the Data blocks, resulting in 600/620 bits per block. The bottom section shows the final HSR Burst structure, which consists of four bursts, each containing 600/620 bits from the punctured Data blocks, along with the USF and RLC/MAC Hdr fields. + +Figure 7: Radio Block structure for CS-1 to CS-3. The diagram shows the internal structure of a radio block, starting with fields like USF, RLC/MAC Hdr, HCS, E, FBI, Data = x bits, BCS, E, FBI, Data = x bits, BCS, E, FBI, Data = x bits, BCS, E, FBI, Data = x bits, BCS, PAN (opt), PCS (opt). It details the bit distribution (3 bits, 70 bits, 558 bits, 558 bits, 558 bits, 558 bits, 30 bits) and the application of Rate 1/3 Turbo coding and puncturing to generate HSR Bursts. + +Figure 7: Radio Block structure for CS-1 to CS-3 + +![Figure 8: Radio Block structure for CS-4. The diagram shows the bit structure of a radio block. At the top, fields are defined: USF (3 bits), RLC/MAC Hdr (58 bits), HCS (1 bit), E (1 bit), FBI (1 bit), Data = x bits (606 bits), BCS (16 bits), E (1 bit), FBI (1 bit), Data = x bits (606 bits), BCS (16 bits), E (1 bit), FBI (1 bit), Data = x bits (606 bits), BCS (16 bits), PAN (1 bit), and PCS (1 bit). Below this, the structure is shown in bits: SB-8 (8 bits), USF (8 bits), RLC/MAC Hdr (168 bits), followed by three blocks of 1830 bits each. Each 1830-bit block is the result of Rate 1/3 Turbo coding on the 606-bit data block plus 16-bit BCS, with puncturing applied to achieve the desired rate. The punctured bits are labeled P1, P2, and P3. The final part of the block is 78 bits (opt). At the bottom, four 'HSR Burst' labels are shown, each corresponding to one of the four 1830-bit coded blocks.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +Figure 8: Radio Block structure for CS-4. The diagram shows the bit structure of a radio block. At the top, fields are defined: USF (3 bits), RLC/MAC Hdr (58 bits), HCS (1 bit), E (1 bit), FBI (1 bit), Data = x bits (606 bits), BCS (16 bits), E (1 bit), FBI (1 bit), Data = x bits (606 bits), BCS (16 bits), E (1 bit), FBI (1 bit), Data = x bits (606 bits), BCS (16 bits), PAN (1 bit), and PCS (1 bit). Below this, the structure is shown in bits: SB-8 (8 bits), USF (8 bits), RLC/MAC Hdr (168 bits), followed by three blocks of 1830 bits each. Each 1830-bit block is the result of Rate 1/3 Turbo coding on the 606-bit data block plus 16-bit BCS, with puncturing applied to achieve the desired rate. The punctured bits are labeled P1, P2, and P3. The final part of the block is 78 bits (opt). At the bottom, four 'HSR Burst' labels are shown, each corresponding to one of the four 1830-bit coded blocks. + +**Figure 8: Radio Block structure for CS-4** + +The first step of the coding procedure is to add a Block Check Sequence (BCS) for error detection. + +For CS-1 - CS-3, the second step consists of pre-coding USF (except for CS-1), adding four tail bits and a half rate convolutional coding for error correction that is punctured to give the desired coding rate. + +For CS-4 there is no coding for error correction. + +The details of the codes are shown in table 3, including: + +- the length of each field; +- the number of coded bits (after adding tail bits and convolutional coding); +- the number of punctured bits; +- the data rate. + +**Table 3: Coding parameters for the GPRS coding schemes.** + +| Scheme | Code rate | USF | Pre-coded USF | Radio Block excl. USF and BCS | BCS | Tail | Coded bits | Punctured bits | Data rate kb/s (Note 1) | Data rate kb/s (Note 2) | +|--------|-----------|-----|---------------|-------------------------------|-----|------|------------|----------------|-------------------------|-------------------------| +| CS-1 | 1/2 | 3 | 3 | 181 | 40 | 4 | 456 | 0 | 9.05 | 8.0 | +| CS-2 | ≈2/3 | 3 | 6 | 268 | 16 | 4 | 588 | 132 | 13.4 | 12.0 | +| CS-3 | ≈3/4 | 3 | 6 | 312 | 16 | 4 | 676 | 220 | 15.6 | 14.4 | +| CS-4 | 1 | 3 | 12 | 428 | 16 | - | 456 | - | 21.4 | 20.0 | + +NOTE 1: This value includes the RLC header, the MAC header (excluding the USF), the spare bits and RLC information. +NOTE 2: This value includes only RLC information. + +CS-1 is the same coding scheme as specified for SACCH in 3GPP TS 45.003 [12]. It consists of a half rate convolutional code for FEC and a 40 bit FIRE code for BCS (and optionally FEC). + +CS-2 and CS-3 are punctured versions of the same half rate convolutional code as CS-1 for FEC. + +CS-4 has no FEC. + +CS-2 to CS-4 use the same 16 bit CRC for BCS. The CRC is calculated over the whole uncoded RLC data block including MAC Header. + +The USF has 8 states, which are represented by a binary 3 bit field in the MAC Header. + +For CS-1, the whole Radio Block is convolutionally coded and USF needs to be decoded as part of the data. + +All other coding schemes generate the same 12 bit code for USF. The USF can be decoded either as a block code or as part of the data. + +In order to simplify the decoding, the stealing bits (defined in 3GPP TS 45.003 [12] ) of the block are used to indicate the actual coding scheme. + +##### 6.5.5.1.2 Channel coding for EGPRS PDTCH + +Nine different modulation and coding schemes, MCS-1 to MCS-9, are defined for the EGPRS Radio Blocks carrying RLC data blocks. The block structures of the coding schemes are shown from Figure 10 to Figure 18 and in Table 4. A general description of the MCSs is given in Figure 9. + +The MCSs are divided into different families A, B and C. Each family has a different basic unit of payload: 37 (and 34), 28 and 22 octets respectively. Different code rates within a family are achieved by transmitting a different number of payload units within one Radio Block. For families A and B, 1, 2 or 4 payload units are transmitted, for family C, only 1 or 2 payload units are transmitted. + +When 4 payload units are transmitted (MCS-7, MCS-8 and MCS-9), these are split into two separate RLC blocks (i.e. with separate sequence numbers and BCSs). These blocks in turn are interleaved over two bursts only, for MCS-8 and MCS-9. For MCS-7, these blocks are interleaved over four bursts. All the other MCSs carry one RLC block which is interleaved over four bursts. When switching to MCS-3 or MCS-6 from MCS-8, 6 padding octets are added to the data octets. + +![Diagram showing the modulation and coding schemes for EGPRS. It details the bit structure of a Radio Block (USF, RLCMAC Hdr, HCS, E, FBI, Data, BCS, E, FBI, Data, BCS, E, FBI, Data, BCS, PAN, PCS) and how it is mapped to four HSR Bursts (P1, P2, P3, P1, P2, P3, P1, P2, P3) through Rate 1/3 Turbo coding and puncturing. The diagram includes bit counts for various fields and burst segments.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +The diagram illustrates the mapping of a Radio Block to four HSR Bursts. The Radio Block structure is as follows: + +- USF: 3 bits +- RLCMAC Hdr: 58 bits +- HCS: 1 bit +- E: 1 bit +- FBI: 1 bit +- Data = x bits: 462 bits +- BCS: 1 bit +- E: 1 bit +- FBI: 1 bit +- Data = x bits: 462 bits +- BCS: 1 bit +- E: 1 bit +- FBI: 1 bit +- Data = x bits: 462 bits +- BCS: 1 bit +- PAN (opt): 1 bit +- PCS (opt): 1 bit + +The data fields are processed by Rate 1/3 Turbo coding, resulting in 1398 bits per data block. The header fields (USF, RLCMAC Hdr, HCS, E, FBI, BCS, E, FBI, BCS) are also processed by Rate 1/3 Turbo coding, resulting in 64 bits and 168 bits. Puncturing is applied to the coded data to fit into the burst structure. + +The resulting burst structure for four HSR Bursts is: + +- Burst 1: SB=0 (64 bits), Header (168 bits), Data (630/656 bits) +- Burst 2: Data (630/656 bits) +- Burst 3: Data (630/656 bits) +- Burst 4: Data (630/656 bits), Optional (78 bits) + +Diagram showing the modulation and coding schemes for EGPRS. It details the bit structure of a Radio Block (USF, RLCMAC Hdr, HCS, E, FBI, Data, BCS, E, FBI, Data, BCS, E, FBI, Data, BCS, PAN, PCS) and how it is mapped to four HSR Bursts (P1, P2, P3, P1, P2, P3, P1, P2, P3) through Rate 1/3 Turbo coding and puncturing. The diagram includes bit counts for various fields and burst segments. + +**Figure 9: General description of the Modulation and Coding Schemes for EGPRS** + +To ensure strong header protection, the header part of the Radio Block is independently coded from the data part of the Radio Block (8 bit CRC calculated over the header -excl. USF- for error detection, followed by rate 1/3 convolutional coding –and eventually puncturing- for error correction). Three different header formats are used, one for MCS-7, MCS-8 and MCS-9, one for MCS-5 and MCS-6 and one for MCS-1 to MCS-4. The two first formats are for 8PSK modes, the difference being in the number of Sequence Numbers carried (2 for MCS-7, -8 and -9, 1 for MCS-5 and -6). The third format is common to all GMSK modes. The header is always interleaved over four bursts. See 3GPP TS 44.060 [7] for more details. + +The following figures show the coding and puncturing for all the Modulation and Coding Schemes, for downlink traffic. For TBFs with FANR activated, the figures refer to the case when no PAN field is included. + +NOTE: The USF and SB fields shown in Figures 10 to 18 may be mapped in another way when RTTI configuration is used with BTTI USFs, see 3GPP TS 45.002 for details. + +![Figure 10: Coding and puncturing for MCS-9; uncoded 8PSK, two RLC blocks per radio block. The diagram shows the mapping of bits from various fields (USF, RLC/MAC Hdr, HCS, E, FBI, Data, BCS, PAN, PCS) through Rate 1/3 Turbo coding and puncturing to form HSR Bursts. Bit counts are provided for each field and the resulting bursts.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +The diagram illustrates the bit mapping for MCS-9. The top row shows the input bit fields: USF (3 bits), RLC/MAC Hdr (46 bits), HCS (1 bit), E (1 bit), FBI (1 bit), Data = x bits (606 bits), BCS (1 bit), E (1 bit), FBI (1 bit), Data = x bits (606 bits), BCS (1 bit), PAN (opt) (30 bits), and PCS (opt) (30 bits). These are grouped into two Rate 1/3 Turbo coding blocks. The middle row shows the intermediate bit counts: 64 bits (USF), 144 bits (RLC/MAC Hdr), 1830 bits (Data + BCS + E + FBI), 1830 bits (Data + BCS + E + FBI), and 80 bits (opt) (PAN + PCS). The bottom row shows the final bit counts after puncturing: SB=8 (64 bits), 144 bits, 956/996 bits (P1), 956/996 bits (P2), 956/996 bits (P1), 956/996 bits (P2), and 80 bits (opt). These are then mapped to four HSR Bursts. + +Figure 10: Coding and puncturing for MCS-9; uncoded 8PSK, two RLC blocks per radio block. The diagram shows the mapping of bits from various fields (USF, RLC/MAC Hdr, HCS, E, FBI, Data, BCS, PAN, PCS) through Rate 1/3 Turbo coding and puncturing to form HSR Bursts. Bit counts are provided for each field and the resulting bursts. + +Figure 10: Coding and puncturing for MCS-9; uncoded 8PSK, two RLC blocks per radio block + +![Figure 11: Coding and puncturing for MCS-8; rate 0.92 8PSK, two RLC blocks per radio block. The diagram shows the mapping of bits from various fields (USF, RLC/MAC Hdr, HCS, E, FBI, Data, BCS, PAN, PCS) through Rate 1/3 Turbo coding and puncturing to form HSR Bursts. Bit counts are provided for each field and the resulting bursts.](0ee9d674085524d589646a6c3fb21ec3_img.jpg) + +The diagram illustrates the bit mapping for MCS-8. The top row shows the input bit fields: USF (3 bits), RLC/MAC Hdr (46 bits), HCS (1 bit), E (1 bit), FBI (1 bit), Data = x bits (462 bits), BCS (1 bit), E (1 bit), FBI (1 bit), Data = x bits (462 bits), BCS (1 bit), PAN (opt) (30 bits), and PCS (opt) (30 bits). These are grouped into two Rate 1/3 Turbo coding blocks. The middle row shows the intermediate bit counts: 64 bits (USF), 144 bits (RLC/MAC Hdr), 1398 bits (Data + BCS + E + FBI), 1398 bits (Data + BCS + E + FBI), and 80 bits (opt) (PAN + PCS). The bottom row shows the final bit counts after puncturing: SB=8 (64 bits), 144 bits, 956/996 bits (P1), 956/996 bits (P2), 956/996 bits (P1), 956/996 bits (P2), and 80 bits (opt). These are then mapped to four HSR Bursts. + +Figure 11: Coding and puncturing for MCS-8; rate 0.92 8PSK, two RLC blocks per radio block. The diagram shows the mapping of bits from various fields (USF, RLC/MAC Hdr, HCS, E, FBI, Data, BCS, PAN, PCS) through Rate 1/3 Turbo coding and puncturing to form HSR Bursts. Bit counts are provided for each field and the resulting bursts. + +Figure 11: Coding and puncturing for MCS-8; rate 0.92 8PSK, two RLC blocks per radio block + +![Diagram of coding and puncturing for MCS-7. It shows the mapping of USF, RLC/MAC Hdr, HCS, E, FBI, Data, BCS, PAN, and PCS fields into HSR Bursts via Rate 1/3 Turbo coding and puncturing.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +The diagram illustrates the coding and puncturing process for MCS-7. At the top, the input fields and their bit lengths are shown: USF (3 bits), RLC/MAC Hdr (35 bits), HCS (1 bit), E (1 bit), FBI (1 bit), Data = x bits (606 bits), BCS (1 bit), PAN (opt) (30 bits), and PCS (opt) (30 bits). These are processed through Rate 1/3 Turbo coding. The resulting coded bits are mapped to a middle row of blocks: 32 bits (USF), 108 bits (RLC/MAC Hdr), 1830 bits (Data), and 80 bits (opt) (PAN/PCS). Below this, a 'puncturing' step is indicated. The final mapping to HSR Bursts (SB=8) shows: 32 bits (USF), 108 bits (RLC/MAC Hdr), two segments of 876/956 bits (P1 and P2, corresponding to the punctured Data), and 80 bits (opt) (PAN/PCS). These are then distributed across four HSR Bursts. + +Diagram of coding and puncturing for MCS-7. It shows the mapping of USF, RLC/MAC Hdr, HCS, E, FBI, Data, BCS, PAN, and PCS fields into HSR Bursts via Rate 1/3 Turbo coding and puncturing. + +Figure 12: Coding and puncturing for MCS-7; rate 0.76 8PSK, two RLC blocks per radio block + +![Diagram of coding and puncturing for MCS-6. It shows the mapping of USF, RLC/MAC Hdr, HCS, E, FBI, Data, BCS, PAN, and PCS fields into HSR Bursts via Rate 1/3 Turbo coding and puncturing.](fcbc3c31776721edc98ceb1944ec438f_img.jpg) + +The diagram illustrates the coding and puncturing process for MCS-6. At the top, the input fields and their bit lengths are shown: USF (3 bits), RLC/MAC Hdr (35 bits), HCS (1 bit), E (1 bit), FBI (1 bit), Data = x bits (462 bits), BCS (1 bit), PAN (opt) (30 bits), and PCS (opt) (30 bits). These are processed through Rate 1/3 Turbo coding. The resulting coded bits are mapped to a middle row of blocks: 32 bits (USF), 108 bits (RLC/MAC Hdr), 1398 bits (Data), and 80 bits (opt) (PAN/PCS). Below this, a 'puncturing' step is indicated. The final mapping to HSR Bursts (SB=8) shows: 32 bits (USF), 108 bits (RLC/MAC Hdr), two segments of 876/956 bits (P1 and P2, corresponding to the punctured Data), and 80 bits (opt) (PAN/PCS). These are then distributed across four HSR Bursts. + +Diagram of coding and puncturing for MCS-6. It shows the mapping of USF, RLC/MAC Hdr, HCS, E, FBI, Data, BCS, PAN, and PCS fields into HSR Bursts via Rate 1/3 Turbo coding and puncturing. + +Figure 13: Coding and puncturing for MCS-6; rate 0.49 8PSK, one RLC block per radio block + +![Figure 14: Coding and puncturing for MCS-5; rate 0.37 8PSK, one RLC block per radio block. The diagram shows the flow of bits from an RLC/MAC Hdr and Data segments through Rate 1/3 Convolutional coding and puncturing to form four Normal Bursts.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +The diagram illustrates the bit processing flow for MCS-5. At the top, the input is divided into segments: 60 bits (RLC/MAC Hdr), three 532-bit segments (each containing HCS, E, FBI, Data = x bits, BCS, T, B), and 26 bits (PAN (opt), PCS (opt)). The 532-bit segments are processed by Rate 1/3 Convolutional coding to produce 1596 bits each. All segments are then punctured. The resulting bits are mapped to four Normal Bursts (SB=8). Each burst contains the 168-bit RLC/MAC Hdr, three 534/560-bit segments (P1, P2, P3) derived from the coded data, and 78 optional bits (opt). + +Figure 14: Coding and puncturing for MCS-5; rate 0.37 8PSK, one RLC block per radio block. The diagram shows the flow of bits from an RLC/MAC Hdr and Data segments through Rate 1/3 Convolutional coding and puncturing to form four Normal Bursts. + +Figure 14: Coding and puncturing for MCS-5; rate 0.37 8PSK, one RLC block per radio block + +![Figure 15: Coding and puncturing for MCS-4; uncoded GMSK, one RLC block per radio block. The diagram shows the flow of bits from an RLC/MAC Hdr and Data segments through Rate 1/3 Convolutional coding and puncturing to form four Normal Bursts.](b2f5606b9c7184c1c6070a290080a3e3_img.jpg) + +The diagram illustrates the bit processing flow for MCS-4. At the top, the input is divided into segments: 60 bits (RLC/MAC Hdr), three 468-bit segments (each containing HCS, E, FBI, Data = x bits, BCS, T, B), and 26 bits (PAN (opt), PCS (opt)). The 468-bit segments are processed by Rate 1/3 Convolutional coding to produce 1404 bits each. All segments are then punctured. The resulting bits are mapped to four Normal Bursts (SB=8). Each burst contains the 168-bit RLC/MAC Hdr, three 534/560-bit segments (P1, P2, P3) derived from the coded data, and 78 optional bits (opt). + +Figure 15: Coding and puncturing for MCS-4; uncoded GMSK, one RLC block per radio block. The diagram shows the flow of bits from an RLC/MAC Hdr and Data segments through Rate 1/3 Convolutional coding and puncturing to form four Normal Bursts. + +Figure 15: Coding and puncturing for MCS-4; uncoded GMSK, one RLC block per radio block + +![Diagram of coding and puncturing for MCS-3. It shows the mapping of RLC/MAC Hdr, HCS, E, FBI, Data, BCS, T, B, PAN (opt), and PCS (opt) fields into four Normal Bursts. The first two bursts are 49 bits + 612 bits, and the last two are 612 bits + 26 bits. The diagram details the Rate 1/3 Convolutional coding and puncturing process, resulting in 136 bits for the header, 817/856 bits for data (P1, P2, P3), and 78 bits (opt) for the trailer.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +The diagram illustrates the coding and puncturing process for MCS-3. The input data is divided into four Normal Bursts. The first two bursts consist of 49 bits (RLC/MAC Hdr, HCS, E, FBI) and 612 bits (Data, BCS, T, B). The last two bursts consist of 612 bits (Data, BCS, T, B) and 26 bits (PAN (opt), PCS (opt)). The data is processed through Rate 1/3 Convolutional coding and puncturing. The resulting output is 136 bits for the header, 817/856 bits for data (P1, P2, P3), and 78 bits (opt) for the trailer. + +Diagram of coding and puncturing for MCS-3. It shows the mapping of RLC/MAC Hdr, HCS, E, FBI, Data, BCS, T, B, PAN (opt), and PCS (opt) fields into four Normal Bursts. The first two bursts are 49 bits + 612 bits, and the last two are 612 bits + 26 bits. The diagram details the Rate 1/3 Convolutional coding and puncturing process, resulting in 136 bits for the header, 817/856 bits for data (P1, P2, P3), and 78 bits (opt) for the trailer. + +Figure 16: Coding and puncturing for MCS-3; rate 0.85 GMSK, one RLC block per radio block + +![Diagram of coding and puncturing for MCS-2. It shows the mapping of RLC/MAC Hdr, HCS, E, FBI, Data, BCS, T, B, PAN (opt), and PCS (opt) fields into four Normal Bursts. The first two bursts are 49 bits + 532 bits, and the last two are 532 bits + 26 bits. The diagram details the Rate 1/3 Convolutional coding and puncturing process, resulting in 136 bits for the header, 817/856 bits for data (P1, P2), and 78 bits (opt) for the trailer.](382a9c9e4816bd229191ab4591424dd8_img.jpg) + +The diagram illustrates the coding and puncturing process for MCS-2. The input data is divided into four Normal Bursts. The first two bursts consist of 49 bits (RLC/MAC Hdr, HCS, E, FBI) and 532 bits (Data, BCS, T, B). The last two bursts consist of 532 bits (Data, BCS, T, B) and 26 bits (PAN (opt), PCS (opt)). The data is processed through Rate 1/3 Convolutional coding and puncturing. The resulting output is 136 bits for the header, 817/856 bits for data (P1, P2), and 78 bits (opt) for the trailer. + +Diagram of coding and puncturing for MCS-2. It shows the mapping of RLC/MAC Hdr, HCS, E, FBI, Data, BCS, T, B, PAN (opt), and PCS (opt) fields into four Normal Bursts. The first two bursts are 49 bits + 532 bits, and the last two are 532 bits + 26 bits. The diagram details the Rate 1/3 Convolutional coding and puncturing process, resulting in 136 bits for the header, 817/856 bits for data (P1, P2), and 78 bits (opt) for the trailer. + +Figure 17: Coding and puncturing for MCS-2; rate 0.66 GMSK, one RLC block per radio block + +![Figure 18: Coding and puncturing for MCS-1; rate 0.53 GMSK, one RLC block per radio block. The diagram shows the mapping of an RLC block into four Normal Bursts. The RLC block structure includes fields: RLC/MAC Hdr (49 bits), HCS, E, FBI, Data = x bits, BCS, T, B, E, FBI, Data = x bits, BCS, T, B, PAN (opt), and PCS (opt). The first part (RLC/MAC Hdr to BCS) is encoded with Rate 1/3 Convolutional coding, resulting in 1404 bits. The second part (T, B, E, FBI, Data = x bits, BCS) is also encoded with Rate 1/3 Convolutional coding, resulting in 1404 bits. Puncturing is applied to these 1404 bits to produce 817/856 bits for each of the four Normal Bursts. The SB=8 field (26 bits) is mapped to the first burst. The PAN (opt) and PCS (opt) fields (26 bits) are mapped to the fourth burst. The mapping is as follows: Burst 1: SB=8 (136 bits), P1 (817/856 bits); Burst 2: P2 (817/856 bits); Burst 3: P1 (817/856 bits); Burst 4: P2 (817/856 bits), PAN (opt) (78 bits), PCS (opt) (78 bits).](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +Figure 18: Coding and puncturing for MCS-1; rate 0.53 GMSK, one RLC block per radio block. The diagram shows the mapping of an RLC block into four Normal Bursts. The RLC block structure includes fields: RLC/MAC Hdr (49 bits), HCS, E, FBI, Data = x bits, BCS, T, B, E, FBI, Data = x bits, BCS, T, B, PAN (opt), and PCS (opt). The first part (RLC/MAC Hdr to BCS) is encoded with Rate 1/3 Convolutional coding, resulting in 1404 bits. The second part (T, B, E, FBI, Data = x bits, BCS) is also encoded with Rate 1/3 Convolutional coding, resulting in 1404 bits. Puncturing is applied to these 1404 bits to produce 817/856 bits for each of the four Normal Bursts. The SB=8 field (26 bits) is mapped to the first burst. The PAN (opt) and PCS (opt) fields (26 bits) are mapped to the fourth burst. The mapping is as follows: Burst 1: SB=8 (136 bits), P1 (817/856 bits); Burst 2: P2 (817/856 bits); Burst 3: P1 (817/856 bits); Burst 4: P2 (817/856 bits), PAN (opt) (78 bits), PCS (opt) (78 bits). + +**Figure 18: Coding and puncturing for MCS-1; rate 0.53 GMSK, one RLC block per radio block** + +The USF has 8 states, which are represented by a binary 3 bit field in the MAC Header. The USF is encoded to 12 symbols similarly to GPRS, (i.e., 12 bits for GMSK modes and 36 bits for 8PSK modes). + +The FBI (Final Block Indicator) bit and the E (Extension) bit defined in 3GPP TS 44.060 [7] do not require extra protection: they are encoded along with the data part. + +The first step of the coding procedure is to add a Block Check Sequence (BCS) for error detection. + +The second step consists of adding six tail bits (TB) and a 1/3 rate convolutional coding for error correction that is punctured to give the desired coding rate. The Pi for each MCS correspond to different puncturing schemes achieving the same coding rate. The bits indicating the MCS used are in the coded header. In both 8PSK and GMSK modes the stealing bits (SB) of the block are used to indicate the header formats. There are eight SB for 8PSK mode which allow to indicate four header formats. There are twelve SB for GMSK mode which allow to indicate two header formats: the first eight of the twelve SB indicate CS-4. + +Note that the mapping of USFs and SB bits onto PDCHs/bursts in RTTI configuration may be different than shown in Figures 10-18 when BTTI USFs are used. In RTTI configuration, two bursts of a radio block are mapped on one PDCH while the other two bursts are mapped onto the second PDCH of a PDCH pair. On the other hand, a BTTI USF belongs to one PDCH and is mapped on four consecutive bursts transmitted on that PDCH, i.e. two bursts belongs to one RTTI radio block while the other two bursts belong to another RTTI radio block. The detailed mapping is defined in 3GPP TS 45.002. + +The details of the EGPRS coding schemes are shown in table 4. The data rates exclude the RLC/MAC header(s). + +**Table 4: Coding parameters for the EGPRS coding schemes** + +| Scheme | Code rate (Note 2) | Header Code rate | PAN Code rate (if present) | Modulation | RLC blocks per Radio Block | Raw Data within one Radio Block (Note 1) | Family | BCS | Tail payload | HCS | PCS (if present) | Data rate per PDCH kb/s | +|--------|--------------------|------------------|----------------------------|------------|----------------------------|------------------------------------------|--------|------|--------------|-----|------------------|-------------------------| +| MCS-9 | 1.0 | 0.36 | n/a | 8PSK | 2 | 2x592 | A | 2x12 | 2x6 | 8 | 10 | 59.2 | +| MCS-8 | 0.92 (0.98) | 0.36 | 0.42 | | 2 | 2x544 | A | | | | | 54.4 | +| MCS-7 | 0.76 (0.81) | 0.36 | 0.42 | | 2 | 2x448 | B | | | | | 44.8 | +| MCS-6 | 0.49 (0.52) | 1/3 | 0.39 | | 1 | 592
48+544 | A | | | | | 29.6
27.2 | +| MCS-5 | 0.37 (0.40) | 1/3 | 0.39 | GMSK | 1 | 448 | B | 12 | 6 | | | 22.4 | +| MCS-4 | 1.0 | 0.53 | n/a | | 1 | 352 | C | | | | | 17.6 | +| MCS-3 | 0.85 (0.96) | 0.53 | 0.63 | | 1 | 296
48+248 and 296 | A | | | | | 14.8
13.6 | +| MCS-2 | 0.66 (0.75) | 0.53 | 0.63 | | 1 | 224 | B | | | | | 11.2 | +| MCS-1 | 0.53 (0.60) | 0.53 | 0.63 | | 1 | 176 | C | | | | | 8.8 | + +NOTE 1: The italic captions indicate the 6 octets of padding when retransmitting an MCS-8 block with MCS-3 or MCS-6. For MCS-3, the 6 octets of padding are sent every second block (see 3GPP TS 44.060). + +NOTE 2: The numbers in brackets indicate the coding rate for transmission using Fast Ack/Nack Reporting, when the PAN field is present. + +##### 6.5.5.1.3 Channel coding for EGPRS2 PDTCH + +Eight different modulation and coding schemes, DAS-5 to DAS-12, are defined for the EGPRS2-A Radio Blocks carrying RLC data blocks on the downlink; additionally MCS-1 to MCS-4 are included within EGPRS2-A in the downlink in order to enable complete family structure. In addition, MCS-7 and MCS-8 are included within EGPRS2-A and may be used when either the USF or the PAN or both are addressed to one or more EGPRS mobile stations. Eight different modulation and coding schemes, DBS-5 to DBS-12, are defined for the EGPRS2-B Radio Blocks carrying RLC data blocks on the downlink; additionally MCS-1 to MCS-4 are included within EGPRS2-B in the downlink in order to enable complete family structure. Furthermore, MCS-6 to MCS-9, DAS-5, DAS-6, DAS-8, DAS-9, DAS-10 pad, DAS-11, and DAS-12 pad are also included within EGPRS2-B and may be used when either the USF or the PAN or both are addressed to one or more EGPRS2-A mobile stations. Similarly, MCS-6 to MCS-9, DAS-5 and DAS-6 may be used when either the USF or the PAN or both are addressed to one or more EGPRS mobile stations. + +Five different modulation and coding schemes, UAS-7 to UAS-11, are defined for the EGPRS2-A Radio Blocks carrying RLC data blocks on the uplink; additionally MCS-1 to MCS-6 are included within EGPRS2-A in the uplink in order to enable complete family structure. Eight different modulation and coding schemes, UBS-5 to UBS-12, are defined for the EGPRS2-B Radio Blocks carrying RLC data blocks on the uplink; additionally MCS-1 to MCS-4 are included within EGPRS2-B in the uplink in order to enable complete family structure. + +The block structures of the coding schemes are shown in Figure 18e.1 to Figure 18e.8, Figure 18f.1 to Figure 18f.8, Figure 18g.1 to Figure 18g.5, and Figure 18h.1 to Figure 18h.8, and in Table 4a, 4b, 4c and 4d. A general description of the modulation and coding scheme families is given in Figure 18a, 18b, 18c and 18d. + +The EGPRS2 modulation and coding schemes are divided into different families A, B and C. Each family has a different basic unit of payload: 37 (and 34), 28 and 22 octets respectively. Different code rates within a family are achieved by transmitting a different number of payload units within one Radio Block. See Figure 18a, 18b, 18c, 18d for information of the number of payload units used in each family. + +When 4 payload units are transmitted (UBS-11 and UBS-12), these are split into four separate RLC blocks (i.e. with separate sequence numbers and BCSs). These blocks in turn are interleaved over one burst only. + +![Diagram showing modulation and coding schemes for EGPRS2-A downlink, categorized into Family A, Family A Padding6, Family B, and Family C. Each family shows MCS levels, UBS levels, and corresponding octet counts.](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +The diagram illustrates the relationship between Modulation and Coding Schemes (MCS) and Uplink Block Size (UBS) for different families in EGPRS2-A downlink. + +- Family A:** + - MCS-3: Two blocks of 37 octets each. + - UBS-6, UBS-8, UBS-10, UBS-12: Correspond to four blocks of 74 octets each. +- Family A Padding6:** + - MCS-3: First part (6 + 31 octets), Second part (37 octets). + - UBS-6, UBS-8, UBS-10: Correspond to three blocks of 6 + 68 octets each. + - UBS-11: Corresponds to four blocks of 68 octets each. +- Family B:** + - MCS-2: Two blocks of 28 octets each. + - UBS-5, UBS-7, UBS-9: Correspond to three blocks of 56 octets each. +- Family C:** + - MCS-1: Two blocks of 22 octets each. + - MCS-4: One block of 44 octets. + +Diagram showing modulation and coding schemes for EGPRS2-A downlink, categorized into Family A, Family A Padding6, Family B, and Family C. Each family shows MCS levels, UBS levels, and corresponding octet counts. + +Figure 18a: General description of the Modulation and Coding Schemes for EGPRS2-A in the downlink + +![Diagram showing modulation and coding schemes for EGPRS2-B downlink, categorized into Family A, Family A Padding6, Family B, and Family C. Each family shows MCS and UBS configurations with corresponding octet counts.](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +The diagram illustrates the modulation and coding schemes for EGPRS2-B in the downlink, organized into four families: + +- Family A:** + - MCS-3: Two blocks of 37 octets each. + - UBS-6, UBS-8, UBS-10, UBS-12: Indicated by horizontal lines spanning across four blocks of 74 octets each. +- Family A Padding6:** + - MCS-3: First part (6 + 31 octets), Second part (37 octets). + - UBS-6, UBS-8, UBS-10: Indicated by horizontal lines spanning across three blocks of 6 + 68 octets each. + - UBS-11: Indicated by a horizontal line spanning across four blocks of 68 octets each. +- Family B:** + - MCS-2: Two blocks of 28 octets each. + - UBS-5, UBS-7, UBS-9: Indicated by horizontal lines spanning across three blocks of 56 octets each. +- Family C:** + - MCS-1: Two blocks of 22 octets each. + - MCS-4: One block of 44 octets. + +Diagram showing modulation and coding schemes for EGPRS2-B downlink, categorized into Family A, Family A Padding6, Family B, and Family C. Each family shows MCS and UBS configurations with corresponding octet counts. + +Figure 18b: General description of the Modulation and Coding Schemes for EGPRS2-B in the downlink + +![Diagram showing modulation and coding schemes for EGPRS2-A in the uplink, categorized into Family A, Family B, and Family C. Each family shows MCS levels, UBS levels, and corresponding octet counts.](8269648391c59363ea61243864a2adf7_img.jpg) + +The diagram illustrates the relationship between Modulation and Coding Schemes (MCS) and Uplink Block Size (UBS) for EGPRS2-A in the uplink, organized into three families: + +- Family A:** + - MCS-3: Consists of two parts, each 37 octets long. + - UBS-6, UBS-8, UBS-10, UBS-12: Each corresponds to four blocks of 74 octets. +- Family A Padding6:** + - MCS-3: Divided into a 1st part (6 + 31 octets) and a 2nd part (37 octets). + - UBS-6, UBS-8, UBS-10: Each corresponds to three blocks of 6 + 68 octets. + - UBS-11: Corresponds to four blocks of 68 octets. +- Family B:** + - MCS-2: Consists of two parts, each 28 octets long. + - UBS-5, UBS-7, UBS-9: Each corresponds to three blocks of 56 octets. +- Family C:** + - MCS-1: Consists of two parts, each 22 octets long. + - MCS-4: Consists of one part, 44 octets long. + +Diagram showing modulation and coding schemes for EGPRS2-A in the uplink, categorized into Family A, Family B, and Family C. Each family shows MCS levels, UBS levels, and corresponding octet counts. + +Figure 18c: General description of the Modulation and Coding Schemes for EGPRS2-A in the uplink + +![Diagram showing modulation and coding schemes for EGPRS2-B in the uplink, categorized into Family A, Family A Padding6, Family B, and Family C. Each family shows MCS levels, UBS levels, and corresponding octet counts.](32ff77da4286b58c4778033acaa10836_img.jpg) + +The diagram illustrates the Modulation and Coding Schemes (MCS) for EGPRS2-B in the uplink, organized into four families: + +- Family A:** + - MCS-3: Two blocks of 37 octets each. + - UBS-6, UBS-8, UBS-10, UBS-12: Indicated by horizontal arrows spanning across four blocks of 74 octets each. +- Family A Padding6:** + - MCS-3: First part (6 + 31 octets), Second part (37 octets). + - UBS-6, UBS-8, UBS-10: Indicated by horizontal arrows spanning across three blocks of 6 + 68 octets each. + - UBS-11: Indicated by a horizontal arrow spanning across four blocks of 68 octets each. +- Family B:** + - MCS-2: Two blocks of 28 octets each. + - UBS-5, UBS-7, UBS-9: Indicated by horizontal arrows spanning across three blocks of 56 octets each. +- Family C:** + - MCS-1: Two blocks of 22 octets each. + - MCS-4: One block of 44 octets. + +Diagram showing modulation and coding schemes for EGPRS2-B in the uplink, categorized into Family A, Family A Padding6, Family B, and Family C. Each family shows MCS levels, UBS levels, and corresponding octet counts. + +Figure 18d: General description of the Modulation and Coding Schemes for EGPRS2-B in the uplink + +To ensure strong header protection, the header part of the Radio Block is independently coded from the data part of the Radio Block (8 bit CRC calculated over the header -excl. USF- for error detection, followed by rate 1/3 convolutional coding and eventually puncturing for error correction). + +For EGPRS2-A in the downlink, 4 different header formats are used, one for DAS-5 to DAS-7, one for DAS-8 and DAS-9, one for DAS-10, and one for DAS-11 and DAS-12, in addition to the header format for MCS-1 to MCS-4. For EGPRS2-B in the downlink, 4 different header formats are used, one for DBS-5 and DBS-6, one for DBS-7 and DBS-8, one for DBS-9 and DBS-10, and one for DBS-11 and DBS-12, in addition to the header format for MCS-1 to MCS-4. + +For EGPRS2-A in the uplink, 2 different header formats are used, one for UAS-7 to UAS-9, and one for UAS-10 and UAS-11, in addition to the header format for MCS-1 to MCS-4, and the header format for MCS-5 and MCS-6. For EGPRS2-B in the uplink, 4 different header formats are used, one for UBS-5 and UBS-6, one for UBS-7 and UBS-8, one for UBS-9 and UBS-10, and one for UBS-11 and UBS-12, in addition to the header format for MCS-1 to MCS-4. See 3GPP TS 44.060 [7] for more details. + +The following figures show the coding and puncturing for all the modulation and coding schemes, for downlink traffic. + +NOTE: The USF and SB fields shown in Figure 18e.1 to Figure 18e.8, Figure 18f.1 to Figure 18f.8, Figure 18g.1 to Figure 18g.5, and Figure 18h.1 to Figure 18h.8 may be mapped in another way when RTTI configuration is used with BTTI USFs, see 3GPP TS 45.002 for details. Unless otherwise marked, all fields shown in Figure 18e.1 to Figure 18e.8 and Figure 18g.1 to Figure 18g.5 are interleaved over 4 normal bursts; all fields shown in Figure 18f.1 to Figure 18f.8 and Figure 18h.1 to Figure 18h.8 are interleaved over 4 HSR bursts. + +![Figure 18e.1: Coding and puncturing for DAS-12; rate 1.00/0.96 32QAM, three RLC blocks per radio block.](a97518a839da75f8379c578562b01bc2_img.jpg) + +The diagram illustrates the coding and puncturing process for DAS-12. At the top, the radio block structure is shown with bit counts: 3 bits for USF, 58 bits for RLC/MAC Hdr + HCS + E + FBI, three segments of 670 bits each for Data + BCS + E + FBI, and 30 bits for PAN (opt) + PCS (opt) + BCS. The data segments undergo Rate 1/3 Turbo coding, resulting in three blocks of 2022 bits. These are then punctured into segments of 674/700 bits (labeled P1, P2, P3). The final stage shows these bits, along with the USF (60 bits), RLC/MAC Hdr (152 bits), and optional PAN/PCS (78 bits), being mapped across four Normal Bursts. A Stealing Bit (SB=8) is also indicated. + +Figure 18e.1: Coding and puncturing for DAS-12; rate 1.00/0.96 32QAM, three RLC blocks per radio block. + +**Figure 18e.1: Coding and puncturing for DAS-12; rate 1.00/0.96 32QAM, three RLC blocks per radio block** + +![Figure 18e.2: Coding and puncturing for DAS-11; rate 0.84/0.80 32QAM, three RLC blocks per radio block.](080a7af02bc47cf21ebfae4e0be39745_img.jpg) + +This diagram illustrates the coding and puncturing process for DAS-11. It follows the same structure as Figure 18e.1 but with different bit counts. The three data segments are 558 bits each. After Rate 1/3 Turbo coding, each block is 1686 bits. These are punctured into segments of 674/700 bits (P1, P2, P3) and mapped across four Normal Bursts. The USF, RLC/MAC Hdr, and optional PAN/PCS fields have the same bit counts as in DAS-12 (60, 152, and 78 bits respectively). + +Figure 18e.2: Coding and puncturing for DAS-11; rate 0.84/0.80 32QAM, three RLC blocks per radio block. + +**Figure 18e.2: Coding and puncturing for DAS-11; rate 0.84/0.80 32QAM, three RLC blocks per radio block** + +![Diagram of coding and puncturing for DAS-10. It shows the flow from input fields (USF, RLC/MAC Hdr, HC S, E, FBI, Data) through Rate 1/3 Turbo coding and puncturing to produce four 'Normal Burst' outputs. Bit counts are provided for each stage: input (3, 44, 670, 670, 30 bits), intermediate (60, 132, 2022, 2022, 78 bits), and output (60, 132, 1021/1060, 1021/1060, 1021/1060, 1021/1060, 78 bits).](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +The diagram illustrates the coding and puncturing process for DAS-10. The input is divided into fields: USF (3 bits), RLC/MAC Hdr (44 bits), HC S, E, FBI, and Data (x bits). These are processed through Rate 1/3 Turbo coding. The resulting bits are then punctured to form four 'Normal Burst' outputs. The bit counts for each stage are: Input (3, 44, 670, 670, 30 bits), Intermediate (60, 132, 2022, 2022, 78 bits), and Output (60, 132, 1021/1060, 1021/1060, 1021/1060, 1021/1060, 78 bits). The output fields are labeled P1, P2, P1, P2, and the final burst includes PA, PC, N (opt), and S (opt) fields. + +Diagram of coding and puncturing for DAS-10. It shows the flow from input fields (USF, RLC/MAC Hdr, HC S, E, FBI, Data) through Rate 1/3 Turbo coding and puncturing to produce four 'Normal Burst' outputs. Bit counts are provided for each stage: input (3, 44, 670, 670, 30 bits), intermediate (60, 132, 2022, 2022, 78 bits), and output (60, 132, 1021/1060, 1021/1060, 1021/1060, 1021/1060, 78 bits). + +Figure 18e.3: Coding and puncturing for DAS-10; rate 0.66/0.64 32QAM, two RLC blocks per radio block + +![Diagram of coding and puncturing for DAS-9. It shows the flow from input fields (USF, RLC/MAC Hdr, HC S, E, FBI, Data) through Rate 1/3 Turbo coding and puncturing to produce four 'Normal Burst' outputs. Bit counts are provided for each stage: input (3, 46, 558, 558, 30 bits), intermediate (48, 136, 1686, 1686, 78 bits), and output (48, 136, 793/832, 793/832, 793/832, 793/832, 793/832, 793/832, 78 bits).](b44f89b176c971c7dd264c07bfef2c2a_img.jpg) + +The diagram illustrates the coding and puncturing process for DAS-9. The input is divided into fields: USF (3 bits), RLC/MAC Hdr (46 bits), HC S, E, FBI, and Data (x bits). These are processed through Rate 1/3 Turbo coding. The resulting bits are then punctured to form four 'Normal Burst' outputs. The bit counts for each stage are: Input (3, 46, 558, 558, 30 bits), Intermediate (48, 136, 1686, 1686, 78 bits), and Output (48, 136, 793/832, 793/832, 793/832, 793/832, 793/832, 793/832, 78 bits). The output fields are labeled P1, P2, P3, P1, P2, P3, and the final burst includes PA, PC, N (opt), and S (opt) fields. + +Diagram of coding and puncturing for DAS-9. It shows the flow from input fields (USF, RLC/MAC Hdr, HC S, E, FBI, Data) through Rate 1/3 Turbo coding and puncturing to produce four 'Normal Burst' outputs. Bit counts are provided for each stage: input (3, 46, 558, 558, 30 bits), intermediate (48, 136, 1686, 1686, 78 bits), and output (48, 136, 793/832, 793/832, 793/832, 793/832, 793/832, 793/832, 78 bits). + +Figure 18e.4: Coding and puncturing for DAS-9; rate 0.71/0.68 16QAM, two RLC blocks per radio block + +![Figure 18e.5: Coding and puncturing for DAS-8; rate 0.59/0.56 16QAM, two RLC blocks per radio block. The diagram shows the mapping of bits from RLC blocks to bursts. Top row: 3 bits (USF), 46 bits (RLC/MAC Hdr), 462 bits (Data = x bits), 462 bits (Data = x bits), 30 bits (N (opt), S (opt)). Middle row: 60 bits, 136 bits, 1398 bits (puncturing g), 1398 bits (puncturing g), 78 bits (opt). Bottom row: SB=8, 60 bits, 136 bits, 793/832 bits (P1), 793/832 bits (P2), 793/832 bits (P1), 793/832 bits (P2), 78 bits (opt). Four 'Normal Burst' boxes are at the bottom.](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +| 3 bits | 46 bits | 462 bits | | | | | | 462 bits | | | | | | 30 bits | | +|-----------------------|-------------|------------------------|-----------------|-----------------|-----------------|------------------------|---------------|----------|---------------|------|---------------|------------|--|---------|--| +| USF | RLC/MAC Hdr | HC S | E | FBI | Data = x bits | BC S | E | FBI | Data = x bits | BC S | PA N (opt) | PC S (opt) | | | | +| Rate 1/3 Turbo coding | | | | | | | | | | | | | | | | +| 60 bits | 136 bits | 1398 bits puncturing g | | | | 1398 bits puncturing g | | | | | 78 bits (opt) | | | | | +| SB=8 | 60 bits | 136 bits | 793/832 bits P1 | 793/832 bits P2 | 793/832 bits P1 | 793/832 bits P2 | 78 bits (opt) | | | | | | | | | + +Normal Burst | Normal Burst | Normal Burst | Normal Burst + +Figure 18e.5: Coding and puncturing for DAS-8; rate 0.59/0.56 16QAM, two RLC blocks per radio block. The diagram shows the mapping of bits from RLC blocks to bursts. Top row: 3 bits (USF), 46 bits (RLC/MAC Hdr), 462 bits (Data = x bits), 462 bits (Data = x bits), 30 bits (N (opt), S (opt)). Middle row: 60 bits, 136 bits, 1398 bits (puncturing g), 1398 bits (puncturing g), 78 bits (opt). Bottom row: SB=8, 60 bits, 136 bits, 793/832 bits (P1), 793/832 bits (P2), 793/832 bits (P1), 793/832 bits (P2), 78 bits (opt). Four 'Normal Burst' boxes are at the bottom. + +Figure 18e.5: Coding and puncturing for DAS-8; rate 0.59/0.56 16QAM, two RLC blocks per radio block + +![Figure 18e.6: Coding and puncturing for DAS-7; rate 0.58/0.54 8PSK, one RLC blocks per radio block. The diagram shows the mapping of bits from RLC blocks to bursts. Top row: 3 bits (USF), 33 bits (RLC/MAC Hdr), 670 bits (Data = x bits), 30 bits (N (opt), S (opt)). Middle row: 36 bits, 100 bits, 2022 bits (puncturing g), 78 bits (opt). Bottom row: SB=8, 36 bits, 100 bits, 1170/1248 bits (P1), 1170/1248 bits (P2), 78 bits (opt). Four 'Normal Burst' boxes are at the bottom.](69e5f1993021af230d08c08aac97d9df_img.jpg) + +| 3 bits | 33 bits | 670 bits | | | | 30 bits | | | +|-----------------------|-------------|------------------------|-------------------|-----|-------------------|---------------|---------------|------------| +| USF | RLC/MAC Hdr | HC S | E | FBI | Data = x bits | BC S | PA N (opt) | PC S (opt) | +| Rate 1/3 Turbo coding | | | | | | | | | +| 36 bits | 100 bits | 2022 bits puncturing g | | | | 78 bits (opt) | | | +| SB=8 | 36 bits | 100 bits | 1170/1248 bits P1 | | 1170/1248 bits P2 | | 78 bits (opt) | | + +Normal Burst | Normal Burst | Normal Burst | Normal Burst + +Figure 18e.6: Coding and puncturing for DAS-7; rate 0.58/0.54 8PSK, one RLC blocks per radio block. The diagram shows the mapping of bits from RLC blocks to bursts. Top row: 3 bits (USF), 33 bits (RLC/MAC Hdr), 670 bits (Data = x bits), 30 bits (N (opt), S (opt)). Middle row: 36 bits, 100 bits, 2022 bits (puncturing g), 78 bits (opt). Bottom row: SB=8, 36 bits, 100 bits, 1170/1248 bits (P1), 1170/1248 bits (P2), 78 bits (opt). Four 'Normal Burst' boxes are at the bottom. + +Figure 18e.6: Coding and puncturing for DAS-7; rate 0.58/0.54 8PSK, one RLC blocks per radio block + +![Diagram of coding and puncturing for DAS-6. It shows the mapping of fields (USF, RLC/MAC Hdr, HC S, E, FBI, Data, BC S, N, S) to burst segments (SB=8, P1, P2). The top row shows bit counts: 3 bits (USF), 33 bits (RLC/MAC Hdr), 558 bits (Data = x bits), and 30 bits (N, S). The middle row shows the turbo coding process: 36 bits (USF), 100 bits (RLC/MAC Hdr), 1686 bits (Data after coding), and 78 bits (N, S). The bottom row shows the final burst segments: SB=8 (36 bits), P1 (100 bits), P2 (1170/1248 bits), and 78 bits (N, S). Below the segments are four 'Normal Burst' boxes.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +3 bits      33 bits      558 bits      30 bits + PA PC + USF RLC/MAC Hdr HC S E FBI Data = x bits BC S N (opt) S (opt) + Rate 1/3 Turbo coding + 36 bits      100 bits      1686 bits      78 bits (opt) + puncturing + g + SB=8 36 bits      100 bits      1170/1248 bits      1170/1248 bits      78 bits (opt) + P1      P2 + Normal Burst      Normal Burst      Normal Burst      Normal Burst + +Diagram of coding and puncturing for DAS-6. It shows the mapping of fields (USF, RLC/MAC Hdr, HC S, E, FBI, Data, BC S, N, S) to burst segments (SB=8, P1, P2). The top row shows bit counts: 3 bits (USF), 33 bits (RLC/MAC Hdr), 558 bits (Data = x bits), and 30 bits (N, S). The middle row shows the turbo coding process: 36 bits (USF), 100 bits (RLC/MAC Hdr), 1686 bits (Data after coding), and 78 bits (N, S). The bottom row shows the final burst segments: SB=8 (36 bits), P1 (100 bits), P2 (1170/1248 bits), and 78 bits (N, S). Below the segments are four 'Normal Burst' boxes. + +Figure 18e.7: Coding and puncturing for DAS-6; rate 0.48/0.45 8PSK, one RLC blocks per radio block + +![Diagram of coding and puncturing for DAS-5. It shows the mapping of fields (USF, RLC/MAC Hdr, HC S, E, FBI, Data, BC S, N, S) to burst segments (SB=8, P1, P2). The top row shows bit counts: 3 bits (USF), 33 bits (RLC/MAC Hdr), 462 bits (Data = x bits), and 30 bits (N, S). The middle row shows the turbo coding process: 36 bits (USF), 100 bits (RLC/MAC Hdr), 1398 bits (Data after coding), and 78 bits (N, S). The bottom row shows the final burst segments: SB=8 (36 bits), P1 (100 bits), P2 (1170/1248 bits), and 78 bits (N, S). Below the segments are four 'Normal Burst' boxes.](73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg) + +3 bits      33 bits      462 bits      30 bits + PA PC + USF RLC/MAC Hdr HC S E FBI Data = x bits BC S N (opt) S (opt) + Rate 1/3 Turbo coding + 36 bits      100 bits      1398 bits      78 bits (opt) + puncturing + g + SB=8 36 bits      100 bits      1170/1248 bits      1170/1248 bits      78 bits (opt) + P1      P2 + Normal Burst      Normal Burst      Normal Burst      Normal Burst + +Diagram of coding and puncturing for DAS-5. It shows the mapping of fields (USF, RLC/MAC Hdr, HC S, E, FBI, Data, BC S, N, S) to burst segments (SB=8, P1, P2). The top row shows bit counts: 3 bits (USF), 33 bits (RLC/MAC Hdr), 462 bits (Data = x bits), and 30 bits (N, S). The middle row shows the turbo coding process: 36 bits (USF), 100 bits (RLC/MAC Hdr), 1398 bits (Data after coding), and 78 bits (N, S). The bottom row shows the final burst segments: SB=8 (36 bits), P1 (100 bits), P2 (1170/1248 bits), and 78 bits (N, S). Below the segments are four 'Normal Burst' boxes. + +Figure 18e.8: Coding and puncturing for DAS-5; rate 0.40/0.37 8PSK, one RLC blocks per radio block + +![Figure 18f.1: Coding and puncturing for DBS-12; rate 1.00/0.98 32QAM, four RLC blocks per radio block. The diagram shows the mapping of bits from RLC blocks to HSR Bursts. It includes fields like USF (3 bits), RLC/MAC Hdr (58 bits), HC S (6 bits), E (1 bit), FBI (1 bit), Data (606 bits), BC S (6 bits), and PA/PC (30 bits). The data is processed through Rate 1/3 Turbo coding, resulting in 1830 bits per block, which are then punctured to 620 bits per stream (P1, P2, P3) for four HSR Bursts.](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +Figure 18f.1: Coding and puncturing for DBS-12; rate 1.00/0.98 32QAM, four RLC blocks per radio block. The diagram shows the mapping of bits from RLC blocks to HSR Bursts. It includes fields like USF (3 bits), RLC/MAC Hdr (58 bits), HC S (6 bits), E (1 bit), FBI (1 bit), Data (606 bits), BC S (6 bits), and PA/PC (30 bits). The data is processed through Rate 1/3 Turbo coding, resulting in 1830 bits per block, which are then punctured to 620 bits per stream (P1, P2, P3) for four HSR Bursts. + +Figure 18f.1: Coding and puncturing for DBS-12; rate 1.00/0.98 32QAM, four RLC blocks per radio block + +![Figure 18f.2: Coding and puncturing for DBS-11; rate 0.94/0.91 32QAM, four RLC blocks per radio block. This diagram is similar to Figure 18f.1 but with different bit counts: USF (3 bits), RLC/MAC Hdr (70 bits), HC S (6 bits), E (1 bit), FBI (1 bit), Data (558 bits), BC S (6 bits), and PA/PC (30 bits). The data is processed through Rate 1/3 Turbo coding, resulting in 1686 bits per block, which are then punctured to 600 bits per stream (P1, P2, P3) for four HSR Bursts.](1ce027dfd26183da52137cf990213724_img.jpg) + +Figure 18f.2: Coding and puncturing for DBS-11; rate 0.94/0.91 32QAM, four RLC blocks per radio block. This diagram is similar to Figure 18f.1 but with different bit counts: USF (3 bits), RLC/MAC Hdr (70 bits), HC S (6 bits), E (1 bit), FBI (1 bit), Data (558 bits), BC S (6 bits), and PA/PC (30 bits). The data is processed through Rate 1/3 Turbo coding, resulting in 1686 bits per block, which are then punctured to 600 bits per stream (P1, P2, P3) for four HSR Bursts. + +Figure 18f.2: Coding and puncturing for DBS-11; rate 0.94/0.91 32QAM, four RLC blocks per radio block + +![Figure 18f.3: Coding and puncturing for DBS-10; rate 0.75/0.72 32QAM, three RLC blocks per radio block. The diagram shows the mapping of bits from RLC blocks to HSR Bursts. It includes fields like USF (3 bits), RLC/MAC Hdr (58 bits), HC S (6 bits), E (1 bit), FBI (1 bit), Data (606 bits), BC S (6 bits), and PA/PC (30 bits). The data is processed through Rate 1/3 Turbo coding, resulting in 1830 bits per block, which are then punctured to 807 bits per stream (P1, P2, P3) for three HSR Bursts.](a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg) + +Figure 18f.3: Coding and puncturing for DBS-10; rate 0.75/0.72 32QAM, three RLC blocks per radio block. The diagram shows the mapping of bits from RLC blocks to HSR Bursts. It includes fields like USF (3 bits), RLC/MAC Hdr (58 bits), HC S (6 bits), E (1 bit), FBI (1 bit), Data (606 bits), BC S (6 bits), and PA/PC (30 bits). The data is processed through Rate 1/3 Turbo coding, resulting in 1830 bits per block, which are then punctured to 807 bits per stream (P1, P2, P3) for three HSR Bursts. + +Figure 18f.3: Coding and puncturing for DBS-10; rate 0.75/0.72 32QAM, three RLC blocks per radio block + +![Figure 18f.4: Coding and puncturing for DBS-9; rate 0.74/0.71 16QAM, three RLC blocks per radio block. The diagram shows the bit flow from input fields (USF, RLC/MAC Hdr, HC S, E, FBI, Data, BC S) through Rate 1/3 Turbo coding and puncturing to form HSR Bursts. Input bit counts are: USF (3), RLC/MAC Hdr (58), HC S (462), E (462), FBI (462), Data = x bits (462), BC S (30). Turbo coding produces 1398 bits per block, which are punctured (g) to 630/656 bits (P1, P2, P3). Final output includes 64 bits (SB=8), 168 bits, and 78 bits (opt).](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +Figure 18f.4: Coding and puncturing for DBS-9; rate 0.74/0.71 16QAM, three RLC blocks per radio block. The diagram shows the bit flow from input fields (USF, RLC/MAC Hdr, HC S, E, FBI, Data, BC S) through Rate 1/3 Turbo coding and puncturing to form HSR Bursts. Input bit counts are: USF (3), RLC/MAC Hdr (58), HC S (462), E (462), FBI (462), Data = x bits (462), BC S (30). Turbo coding produces 1398 bits per block, which are punctured (g) to 630/656 bits (P1, P2, P3). Final output includes 64 bits (SB=8), 168 bits, and 78 bits (opt). + +Figure 18f.4: Coding and puncturing for DBS-9; rate 0.74/0.71 16QAM, three RLC blocks per radio block + +![Figure 18f.5: Coding and puncturing for DBS-8; rate 0.63/0.60 16QAM, two RLC blocks per radio block. The diagram shows the bit flow from input fields (USF, RLC/MAC Hdr, HC S, E, FBI, Data, BC S) through Rate 1/3 Turbo coding and puncturing to form HSR Bursts. Input bit counts are: USF (3), RLC/MAC Hdr (46), HC S (606), E (606), FBI (30), Data = x bits (606), BC S (30). Turbo coding produces 1830 bits per block, which are punctured (g) to 956/996 bits (P1, P2). Final output includes 64 bits (SB=8), 144 bits, 956/996 bits, and 80 bits (opt).](9cbc1ebd80813fc36e499f7d70ed6881_img.jpg) + +Figure 18f.5: Coding and puncturing for DBS-8; rate 0.63/0.60 16QAM, two RLC blocks per radio block. The diagram shows the bit flow from input fields (USF, RLC/MAC Hdr, HC S, E, FBI, Data, BC S) through Rate 1/3 Turbo coding and puncturing to form HSR Bursts. Input bit counts are: USF (3), RLC/MAC Hdr (46), HC S (606), E (606), FBI (30), Data = x bits (606), BC S (30). Turbo coding produces 1830 bits per block, which are punctured (g) to 956/996 bits (P1, P2). Final output includes 64 bits (SB=8), 144 bits, 956/996 bits, and 80 bits (opt). + +Figure 18f.5: Coding and puncturing for DBS-8; rate 0.63/0.60 16QAM, two RLC blocks per radio block + +![Figure 18f.6: Coding and puncturing for DBS-7; rate 0.49/0.47 16QAM, two RLC blocks per radio block. The diagram shows the mapping of bits from RLC blocks to HSR bursts. Top row: 3 bits (USF), 46 bits (RLC/MAC Hdr), 462 bits (Data = x bits, BC S, E, FBI), 462 bits (Data = x bits, BC S, E, FBI), 30 bits (PA, PC). Middle row: 64 bits, 144 bits, 1398 bits (puncturing g), 1398 bits (puncturing g), 80 bits (opt). Bottom row: SB=8, 64 bits, 144 bits, 956/996 bits (P1), 956/996 bits (P2), 956/996 bits (P1), 956/996 bits (P2), 80 bits (opt). Four HSR Bursts are shown at the bottom.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +Figure 18f.6: Coding and puncturing for DBS-7; rate 0.49/0.47 16QAM, two RLC blocks per radio block. The diagram shows the mapping of bits from RLC blocks to HSR bursts. Top row: 3 bits (USF), 46 bits (RLC/MAC Hdr), 462 bits (Data = x bits, BC S, E, FBI), 462 bits (Data = x bits, BC S, E, FBI), 30 bits (PA, PC). Middle row: 64 bits, 144 bits, 1398 bits (puncturing g), 1398 bits (puncturing g), 80 bits (opt). Bottom row: SB=8, 64 bits, 144 bits, 956/996 bits (P1), 956/996 bits (P2), 956/996 bits (P1), 956/996 bits (P2), 80 bits (opt). Four HSR Bursts are shown at the bottom. + +Figure 18f.6: Coding and puncturing for DBS-7; rate 0.49/0.47 16QAM, two RLC blocks per radio block + +![Figure 18f.7: Coding and puncturing for DBS-6; rate 0.69/0.63 QPSK, one RLC blocks per radio block. The diagram shows the mapping of bits from RLC blocks to HSR bursts. Top row: 3 bits (USF), 35 bits (RLC/MAC Hdr), 606 bits (Data = x bits, BC S, E, FBI), 30 bits (PA, PC). Middle row: 32 bits, 108 bits, 1830 bits (puncturing g), 80 bits (opt). Bottom row: SB=8, 32 bits, 108 bits, 876/956 bits (P1), 876/956 bits (P2), 80 bits (opt). Four HSR Bursts are shown at the bottom.](036c200da9b64c3eb5aae2d67bb53e1f_img.jpg) + +Figure 18f.7: Coding and puncturing for DBS-6; rate 0.69/0.63 QPSK, one RLC blocks per radio block. The diagram shows the mapping of bits from RLC blocks to HSR bursts. Top row: 3 bits (USF), 35 bits (RLC/MAC Hdr), 606 bits (Data = x bits, BC S, E, FBI), 30 bits (PA, PC). Middle row: 32 bits, 108 bits, 1830 bits (puncturing g), 80 bits (opt). Bottom row: SB=8, 32 bits, 108 bits, 876/956 bits (P1), 876/956 bits (P2), 80 bits (opt). Four HSR Bursts are shown at the bottom. + +Figure 18f.7: Coding and puncturing for DBS-6; rate 0.69/0.63 QPSK, one RLC blocks per radio block + +![Diagram of coding and puncturing for DBS-5. It shows the mapping of fields (USF, RLC/MAC Hdr, HCS, E, FBI, Data, BCS, N, S) through Rate 1/3 Turbo coding and puncturing to form HSR Bursts. Bit counts are provided for each field and the resulting bursts.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +The diagram illustrates the coding and puncturing process for DBS-5. At the top, input fields are shown with their bit lengths: USF (3 bits), RLC/MAC Hdr (35 bits), HCS (1 bit), E (1 bit), FBI (1 bit), Data = x bits (462 bits), BCS (1 bit), N (opt) (30 bits), and S (opt) (30 bits). These are processed through Rate 1/3 Turbo coding. Below this, the intermediate bit counts are: 32 bits (USF), 108 bits (RLC/MAC Hdr), 1398 bits (Data after coding), and 80 bits (opt) (N and S). A puncturing stage 'g' is applied. The final bit counts for SB=8 are: 32 bits (USF), 108 bits (RLC/MAC Hdr), 876/956 bits (Data after puncturing), and 80 bits (opt) (N and S). These are then mapped to four HSR Bursts, labeled P1 and P2. + +Diagram of coding and puncturing for DBS-5. It shows the mapping of fields (USF, RLC/MAC Hdr, HCS, E, FBI, Data, BCS, N, S) through Rate 1/3 Turbo coding and puncturing to form HSR Bursts. Bit counts are provided for each field and the resulting bursts. + +Figure 18f.8: Coding and puncturing for DBS-5; rate 0.53/0.49 QPSK, one RLC blocks per radio block + +![Diagram of coding and puncturing for UAS-11. It shows the mapping of fields (RLC/MAC Hdr, HCS, E, FBI, Data, BCS, T, B, PAN, PCS) through Rate 1/3 Convolutional coding and puncturing to form Normal Bursts. Bit counts are provided for each field and the resulting bursts.](aeb2a26a07219661191294dba528067a_img.jpg) + +The diagram illustrates the coding and puncturing process for UAS-11. At the top, input fields are shown with their bit lengths: RLC/MAC Hdr (60 bits), HCS (1 bit), E (1 bit), FBI (1 bit), Data = x bits (532 bits), BCS (1 bit), T (1 bit), B (1 bit), E (1 bit), FBI (1 bit), Data = x bits (532 bits), BCS (1 bit), T (1 bit), B (1 bit), E (1 bit), FBI (1 bit), Data = x bits (532 bits), BCS (1 bit), T (1 bit), B (1 bit), PAN (opt) (26 bits), and PCS (opt) (26 bits). These are processed through Rate 1/3 Convolutional coding. Below this, the intermediate bit counts are: 168 bits (RLC/MAC Hdr), 1596 bits (Data after coding), and 78 bits (opt) (PAN and PCS). A puncturing stage is applied. The final bit counts for SB=8 are: 168 bits (RLC/MAC Hdr), 534/560 bits (Data after puncturing), and 78 bits (opt) (PAN and PCS). These are then mapped to four Normal Bursts, labeled P1, P2, and P3. + +Diagram of coding and puncturing for UAS-11. It shows the mapping of fields (RLC/MAC Hdr, HCS, E, FBI, Data, BCS, T, B, PAN, PCS) through Rate 1/3 Convolutional coding and puncturing to form Normal Bursts. Bit counts are provided for each field and the resulting bursts. + +Figure 18g.1: Coding and puncturing for UAS-11; rate 1.00/0.95 16QAM, three RLC blocks per radio block + +![Diagram of coding and puncturing for UAS-10. It shows the mapping of RLC/MAC Hdr, HCS, E, FBI, Data, BCS, T, B, PAN (opt), and PCS (opt) fields into four 'Normal Burst' blocks. The first field is 60 bits, followed by three 468-bit blocks, and a 26-bit tail. Each 468-bit block undergoes Rate 1/3 Convolutional coding to become 1404 bits, which is then punctured into three sub-bursts (P1, P2, P3) of 534/560 bits each. The 60-bit header is split into a 168-bit part and a 78-bit (opt) part. The 26-bit tail is also split into a 78-bit (opt) part. The SB=8 indicator is shown for the first sub-burst.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +Diagram of coding and puncturing for UAS-10. It shows the mapping of RLC/MAC Hdr, HCS, E, FBI, Data, BCS, T, B, PAN (opt), and PCS (opt) fields into four 'Normal Burst' blocks. The first field is 60 bits, followed by three 468-bit blocks, and a 26-bit tail. Each 468-bit block undergoes Rate 1/3 Convolutional coding to become 1404 bits, which is then punctured into three sub-bursts (P1, P2, P3) of 534/560 bits each. The 60-bit header is split into a 168-bit part and a 78-bit (opt) part. The 26-bit tail is also split into a 78-bit (opt) part. The SB=8 indicator is shown for the first sub-burst. + +Figure 18g.2: Coding and puncturing for UAS-10; rate 0.88/0.84 16QAM, three RLC blocks per radio block + +![Diagram of coding and puncturing for UAS-9. It shows the mapping of RLC/MAC Hdr, HCS, E, FBI, Data, BCS, T, B, PAN (opt), and PCS (opt) fields into four 'Normal Burst' blocks. The first field is 49 bits, followed by two 612-bit blocks, and a 26-bit tail. Each 612-bit block undergoes Rate 1/3 Convolutional coding to become 1836 bits, which is then punctured into three sub-bursts (P1, P2, P3) of 817/856 bits each. The 49-bit header is split into a 136-bit part and a 78-bit (opt) part. The 26-bit tail is also split into a 78-bit (opt) part. The SB=8 indicator is shown for the first sub-burst.](df1966d80c74bc127f159a48f38b13ee_img.jpg) + +Diagram of coding and puncturing for UAS-9. It shows the mapping of RLC/MAC Hdr, HCS, E, FBI, Data, BCS, T, B, PAN (opt), and PCS (opt) fields into four 'Normal Burst' blocks. The first field is 49 bits, followed by two 612-bit blocks, and a 26-bit tail. Each 612-bit block undergoes Rate 1/3 Convolutional coding to become 1836 bits, which is then punctured into three sub-bursts (P1, P2, P3) of 817/856 bits each. The 49-bit header is split into a 136-bit part and a 78-bit (opt) part. The 26-bit tail is also split into a 78-bit (opt) part. The SB=8 indicator is shown for the first sub-burst. + +Figure 18g.3: Coding and puncturing for UAS-9; rate 0.75/0.71 16QAM, three RLC blocks per radio block + +![Diagram of coding and puncturing for UAS-8. It shows the mapping of RLC/MAC Hdr, HCS, E, FBI, Data, BCS, T, B, PAN (opt), and PCS (opt) fields into four 'Normal Burst' blocks. The diagram includes bit counts for each field and the resulting burst structure after Rate 1/3 Convolutional coding and puncturing.](0a73b03fba21af142d619a9a662e6490_img.jpg) + +The diagram illustrates the coding and puncturing process for UAS-8. The input fields and their bit counts are: RLC/MAC Hdr (49 bits), HCS (13 bits), E (1 bit), FBI (3 bits), Data = x bits (532 bits), BCS (6 bits), T (1 bit), B (1 bit), PAN (opt) (13 bits), and PCS (opt) (13 bits). These are mapped into four 'Normal Burst' blocks. The first and last bursts contain 136 bits and 78 bits (opt) respectively. The middle two bursts contain 817/856 bits each, labeled P1 and P2. The diagram shows 'Rate 1/3 Convolutional coding' and 'puncturing' applied to the data segments. + +Diagram of coding and puncturing for UAS-8. It shows the mapping of RLC/MAC Hdr, HCS, E, FBI, Data, BCS, T, B, PAN (opt), and PCS (opt) fields into four 'Normal Burst' blocks. The diagram includes bit counts for each field and the resulting burst structure after Rate 1/3 Convolutional coding and puncturing. + +Figure 18g.4: Coding and puncturing for UAS-8; rate 0.65/0.62 16QAM, two RLC blocks per radio block + +![Diagram of coding and puncturing for UAS-7. It shows the mapping of RLC/MAC Hdr, HCS, E, FBI, Data, BCS, T, B, PAN (opt), and PCS (opt) fields into four 'Normal Burst' blocks. The diagram includes bit counts for each field and the resulting burst structure after Rate 1/3 Convolutional coding and puncturing.](508bc574df81fa8d3027a374f6d155fc_img.jpg) + +The diagram illustrates the coding and puncturing process for UAS-7. The input fields and their bit counts are: RLC/MAC Hdr (49 bits), HCS (13 bits), E (1 bit), FBI (3 bits), Data = x bits (468 bits), BCS (6 bits), T (1 bit), B (1 bit), PAN (opt) (13 bits), and PCS (opt) (13 bits). These are mapped into four 'Normal Burst' blocks. The first and last bursts contain 136 bits and 78 bits (opt) respectively. The middle two bursts contain 817/856 bits each, labeled P1 and P2. The diagram shows 'Rate 1/3 Convolutional coding' and 'puncturing' applied to the data segments. + +Diagram of coding and puncturing for UAS-7. It shows the mapping of RLC/MAC Hdr, HCS, E, FBI, Data, BCS, T, B, PAN (opt), and PCS (opt) fields into four 'Normal Burst' blocks. The diagram includes bit counts for each field and the resulting burst structure after Rate 1/3 Convolutional coding and puncturing. + +Figure 18g.5: Coding and puncturing for UAS-7; rate 0.57/0.55 16QAM, two RLC blocks per radio block + +![Figure 18h.1: Coding and puncturing for UBS-12; rate 1.00/0.96 32QAM, four RLC blocks per radio block. The diagram shows the flow of bits from RLC/MAC Hdr, HCS, E, FBI, Data, BCS, T, B, E, FBI, Data, BCS, T, B, E, FBI, Data, BCS, T, B, E, FBI, Data, BCS, T, B, PAN (opt), PCS (opt) through Rate 1/3 Convolutional coding and puncturing to form HSR Bursts.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +The diagram illustrates the bit flow for UBS-12. At the top, bit segments are shown: 72 bits (RLC/MAC Hdr), followed by four 618-bit segments (each containing HCS, E, FBI, Data=x bits, BCS, T, B), and a final 26-bit segment (PAN (opt), PCS (opt)). These are processed through Rate 1/3 Convolutional coding. The resulting bit blocks are: 208 bits (from RLC/MAC Hdr), four 1836-bit blocks (from the 618-bit segments), and 80 bits (opt) (from PAN/PCS). Below this, 'puncturing' is applied. The 1836-bit blocks are split into three parts: P1 (635/615 bits), P2 (635/615 bits), and P3 (635/615 bits). These are then mapped to four 'HSR Burst' blocks. The SB=8 row shows the final bit distribution: 208 bits, followed by four sets of (P1, P2, P3) which are 832/860 bits each, and 80 bits (opt). + +Figure 18h.1: Coding and puncturing for UBS-12; rate 1.00/0.96 32QAM, four RLC blocks per radio block. The diagram shows the flow of bits from RLC/MAC Hdr, HCS, E, FBI, Data, BCS, T, B, E, FBI, Data, BCS, T, B, E, FBI, Data, BCS, T, B, E, FBI, Data, BCS, T, B, PAN (opt), PCS (opt) through Rate 1/3 Convolutional coding and puncturing to form HSR Bursts. + +Figure 18h.1: Coding and puncturing for UBS-12; rate 1.00/0.96 32QAM, four RLC blocks per radio block + +![Figure 18h.2: Coding and puncturing for UBS-11; rate 0.92/0.89 32QAM, four RLC blocks per radio block. The diagram shows the flow of bits from RLC/MAC Hdr, HCS, E, FBI, Data, BCS, T, B, E, FBI, Data, BCS, T, B, E, FBI, Data, BCS, T, B, E, FBI, Data, BCS, T, B, PAN (opt), PCS (opt) through Rate 1/3 Convolutional coding and puncturing to form HSR Bursts.](18e519d1f91133e080347562f681dfb5_img.jpg) + +The diagram illustrates the bit flow for UBS-11. At the top, bit segments are shown: 72 bits (RLC/MAC Hdr), followed by four 580-bit segments (each containing HCS, E, FBI, Data=x bits, BCS, T, B), and a final 26-bit segment (PAN (opt), PCS (opt)). These are processed through Rate 1/3 Convolutional coding. The resulting bit blocks are: 208 bits (from RLC/MAC Hdr), four 1692-bit blocks (from the 580-bit segments), and 80 bits (opt) (from PAN/PCS). Below this, 'puncturing' is applied. The 1692-bit blocks are split into three parts: P1 (635/615 bits), P2 (635/615 bits), and P3 (635/615 bits). These are then mapped to four 'HSR Burst' blocks. The SB=8 row shows the final bit distribution: 208 bits, followed by four sets of (P1, P2, P3) which are 832/860 bits each, and 80 bits (opt). + +Figure 18h.2: Coding and puncturing for UBS-11; rate 0.92/0.89 32QAM, four RLC blocks per radio block. The diagram shows the flow of bits from RLC/MAC Hdr, HCS, E, FBI, Data, BCS, T, B, E, FBI, Data, BCS, T, B, E, FBI, Data, BCS, T, B, E, FBI, Data, BCS, T, B, PAN (opt), PCS (opt) through Rate 1/3 Convolutional coding and puncturing to form HSR Bursts. + +Figure 18h.2: Coding and puncturing for UBS-11; rate 0.92/0.89 32QAM, four RLC blocks per radio block + +![Figure 18h.3: Coding and puncturing for UBS-10; rate 0.74/0.71 32QAM, three RLC blocks per radio block. The diagram shows the flow of bits from RLC/MAC Hdr, HCS, E, FBI, Data, BCS, T, B, E, FBI, Data, BCS, T, B, E, FBI, Data, BCS, T, B, PAN (opt), PCS (opt) through Rate 1/3 Convolutional coding and puncturing to form HSR Bursts.](3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg) + +The diagram illustrates the bit flow for UBS-10. At the top, bit segments are shown: 60 bits (RLC/MAC Hdr), followed by three 618-bit segments (each containing HCS, E, FBI, Data=x bits, BCS, T, B), and a final 26-bit segment (PAN (opt), PCS (opt)). These are processed through Rate 1/3 Convolutional coding. The resulting bit blocks are: 168 bits (from RLC/MAC Hdr), three 1836-bit blocks (from the 618-bit segments), and 84 bits (opt) (from PAN/PCS). Below this, 'puncturing' is applied. The 1836-bit blocks are split into three parts: P1 (832/860 bits), P2 (832/860 bits), and P3 (832/860 bits). These are then mapped to four 'HSR Burst' blocks. The SB=8 row shows the final bit distribution: 168 bits, followed by four sets of (P1, P2, P3) which are 832/860 bits each, and 84 bits (opt). + +Figure 18h.3: Coding and puncturing for UBS-10; rate 0.74/0.71 32QAM, three RLC blocks per radio block. The diagram shows the flow of bits from RLC/MAC Hdr, HCS, E, FBI, Data, BCS, T, B, E, FBI, Data, BCS, T, B, E, FBI, Data, BCS, T, B, PAN (opt), PCS (opt) through Rate 1/3 Convolutional coding and puncturing to form HSR Bursts. + +Figure 18h.3: Coding and puncturing for UBS-10; rate 0.74/0.71 32QAM, three RLC blocks per radio block + +![Figure 18h.4: Coding and puncturing for UBS-9; rate 0.73/0.70 16QAM, three RLC blocks per radio block. The diagram shows the flow of bits from RLC/MAC Hdr, HCS, E, FBI, Data, BCS, T, B, PAN (opt), and PCS (opt) through Rate 1/3 Convolutional coding and puncturing to form HSR Bursts.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +The diagram illustrates the bit flow for UBS-9. At the top, bit segments are defined: 60 bits (RLC/MAC Hdr), three 474-bit segments (each containing HCS, E, FBI, Data = x bits, BCS, T, B), and 26 bits (PAN (opt), PCS (opt)). These are processed through Rate 1/3 Convolutional coding. The first 60 bits become 184 bits. The three 474-bit segments become three 1404-bit blocks. The 26 bits become 84 bits (opt). Below this, 'puncturing' is applied. The 184 bits are split into two HSR Bursts. Each 1404-bit block is split into three HSR Bursts (P1, P2, P3). The 84 bits (opt) are also split into two HSR Bursts. The bottom row shows the resulting bit counts per HSR Burst: 184 bits, followed by three groups of (644/672 bits P1, 644/672 bits P2, 644/672 bits P3), and ending with 84 bits (opt). A label 'SB=8' is present on the left. + +Figure 18h.4: Coding and puncturing for UBS-9; rate 0.73/0.70 16QAM, three RLC blocks per radio block. The diagram shows the flow of bits from RLC/MAC Hdr, HCS, E, FBI, Data, BCS, T, B, PAN (opt), and PCS (opt) through Rate 1/3 Convolutional coding and puncturing to form HSR Bursts. + +Figure 18h.4: Coding and puncturing for UBS-9; rate 0.73/0.70 16QAM, three RLC blocks per radio block + +![Figure 18h.5: Coding and puncturing for UBS-8; rate 0.62/0.60 16QAM, two RLC blocks per radio block. The diagram shows the flow of bits from RLC/MAC Hdr, HCS, E, FBI, Data, BCS, T, B, PAN (opt), and PCS (opt) through Rate 1/3 Convolutional coding and puncturing to form HSR Bursts.](cc6f9dbfc36aa5821d9749ca84861f93_img.jpg) + +The diagram illustrates the bit flow for UBS-8. At the top, bit segments are defined: 48 bits (RLC/MAC Hdr), two 618-bit segments (each containing HCS, E, FBI, Data = x bits, BCS, T, B), and 26 bits (PAN (opt), PCS (opt)). These are processed through Rate 1/3 Convolutional coding. The 48 bits become 144 bits. The two 618-bit segments become two 1836-bit blocks. The 26 bits become 80 bits (opt). Below this, 'puncturing' is applied. The 144 bits are split into two HSR Bursts. Each 1836-bit block is split into two HSR Bursts (P1, P2). The 80 bits (opt) are also split into two HSR Bursts. The bottom row shows the resulting bit counts per HSR Burst: 144 bits, followed by two groups of (988/1028 bits P1, 988/1028 bits P2), and ending with 80 bits (opt). A label 'SB=8' is present on the left. + +Figure 18h.5: Coding and puncturing for UBS-8; rate 0.62/0.60 16QAM, two RLC blocks per radio block. The diagram shows the flow of bits from RLC/MAC Hdr, HCS, E, FBI, Data, BCS, T, B, PAN (opt), and PCS (opt) through Rate 1/3 Convolutional coding and puncturing to form HSR Bursts. + +Figure 18h.5: Coding and puncturing for UBS-8; rate 0.62/0.60 16QAM, two RLC blocks per radio block + +![Figure 18h.6: Coding and puncturing for UBS-7; rate 0.47/0.46 16QAM, two RLC blocks per radio block. The diagram shows the mapping of bits from RLC/MAC headers and data to HSR bursts via Rate 1/3 Convolutional coding and puncturing.](7ed5d5770331f31ade15439a21c31425_img.jpg) + +The diagram illustrates the bit mapping for UBS-7. At the top, bit segments are defined: 48 bits for RLC/MAC Hdr, 474 bits for HCS, E, FBI, Data = x bits, BCS, and T B, and 26 bits for PAN (opt) and PCS (opt). Below this, the mapping for two RLC blocks is shown. For each block, 144 bits from the header and 1404 bits from the data are input to a Rate 1/3 Convolutional coding block. Puncturing is applied to these coded bits. The resulting bits are mapped to HSR bursts: the 144 header bits go to the first HSR Burst, and the 1404 data bits are split into four HSR Bursts (P1, P2, P1, P2), with each receiving 988/1028 bits. The 80 bits (opt) from PAN and PCS are mapped to the fourth HSR Burst. + +Figure 18h.6: Coding and puncturing for UBS-7; rate 0.47/0.46 16QAM, two RLC blocks per radio block. The diagram shows the mapping of bits from RLC/MAC headers and data to HSR bursts via Rate 1/3 Convolutional coding and puncturing. + +Figure 18h.6: Coding and puncturing for UBS-7; rate 0.47/0.46 16QAM, two RLC blocks per radio block + +![Figure 18h.7: Coding and puncturing for UBS-6; rate 0.67/0.62 QPSK, one RLC blocks per radio block. The diagram shows the mapping of bits from RLC/MAC headers and data to HSR bursts via Rate 1/3 Turbo coding and puncturing.](c419b566d720267c499087add1506018_img.jpg) + +The diagram illustrates the bit mapping for UBS-6. At the top, bit segments are defined: 37 bits for RLC/MAC Hdr, 618 bits for HCS, E, FBI, Data = x bits, BCS, and T B, and 26 bits for PAN (opt) and PCS (opt). Below this, the mapping for one RLC block is shown. The 37 header bits and 618 data bits are input to a Rate 1/3 Turbo coding block. Puncturing is applied to these coded bits. The resulting bits are mapped to HSR bursts: the 108 header bits go to the first HSR Burst, and the 1836 data bits are split into four HSR Bursts (P1, P2, P1, P2), with each receiving 908/988 bits. The 80 bits (opt) from PAN and PCS are mapped to the fourth HSR Burst. + +Figure 18h.7: Coding and puncturing for UBS-6; rate 0.67/0.62 QPSK, one RLC blocks per radio block. The diagram shows the mapping of bits from RLC/MAC headers and data to HSR bursts via Rate 1/3 Turbo coding and puncturing. + +Figure 18h.7: Coding and puncturing for UBS-6; rate 0.67/0.62 QPSK, one RLC blocks per radio block + +![Diagram showing the coding and puncturing process for UBS-5. It details the input bit structure (RLC/MAC Hdr, HCS, E, FBI, Data, BCS, T, B, PAN, PCS), the Rate 1/3 Convolutional coding stage, the puncturing stage, and the final output structure (SB=8, 108 bits, 908/988 bits, 908/988 bits, 80 bits (opt)) which are then mapped to four HSR Bursts.](3337af75dfee8af7687b4f49914d6c93_img.jpg) + +The diagram illustrates the bit processing flow for UBS-5. At the top, the input bit structure is shown with segments for RLC/MAC Hdr (37 bits), HCS, E, FBI, Data = x bits (474 bits), BCS, T, B, PAN (opt), and PCS (opt) (26 bits). These bits are processed through a 'Rate 1/3 Convolutional coding' stage. Below this, the intermediate bit structure shows 108 bits, 1404 bits, and 80 bits (opt). A 'puncturing' stage follows, indicated by dashed lines. The final output structure consists of SB=8, 108 bits, 908/988 bits (labeled P1), 908/988 bits (labeled P2), and 80 bits (opt). These are then mapped to four 'HSR Burst' blocks. + +Diagram showing the coding and puncturing process for UBS-5. It details the input bit structure (RLC/MAC Hdr, HCS, E, FBI, Data, BCS, T, B, PAN, PCS), the Rate 1/3 Convolutional coding stage, the puncturing stage, and the final output structure (SB=8, 108 bits, 908/988 bits, 908/988 bits, 80 bits (opt)) which are then mapped to four HSR Bursts. + +Figure 18h.8: Coding and puncturing for UBS-5; rate 0.52/0.47 QPSK, one RLC blocks per radio block + +The USF has 8 states, which are represented by a binary 3 bit field in the MAC Header. The USF encoding for GMSK and 8-PSK modulation schemes is as for EGPRS (see subclause 6.5.5.1.2). For 16QAM and 32QAM modulation schemes at normal symbol rate the USF is encoded to 12 symbols , (i.e., 48 bits for 16QAM and 60 bits for 32QAM). For QPSK, 16QAM and 32QAM modulation schemes at higher symbol rate, the USF is encoded to 16 symbols (i.e. 32 bits for QPSK, 64 bits for 16QAM and 80 bits for 32QAM). + +The FBI (Final Block Indicator) bit and the E (Extension) bit defined in 3GPP TS 44.060 [7] do not require extra protection: they are encoded along with the data part. + +The first step of the coding procedure is to add a Block Check Sequence (BCS) for error detection. + +For EGPRS2 in the downlink, the second step consists of 1/3 rate turbo coding for error correction that is punctured to give the desired coding rate. The $P_i$ for each modulation and coding scheme corresponds to different puncturing schemes achieving the same coding rate. The bits indicating the modulation and coding scheme used are in the coded header. In 8PSK, 16QAM and 32QAM at normal symbol rate and QPSK, 16QAM and 32QAM at higher symbol rate, the stealing bits (SB) of the block are used to indicate the header formats. + +For EGPRS2 in the uplink, the second step consists of adding six tail bits (TB) and a 1/3 rate convolutional coding for error correction that is punctured to give the desired coding rate. The $P_i$ for each modulation and coding scheme corresponds to different puncturing schemes achieving the same coding rate. The bits indicating the modulation and coding scheme used are in the coded header. In 16QAM and 32QAM at normal symbol rate and QPSK, 16QAM and 32QAM at higher symbol rate, the stealing bits (SB) of the block are used to indicate the header formats. + +The mapping of USFs and SB bits onto PDCHs/bursts in RTTI configuration may be different from that shown in Figure 18e.1 to Figure 18e.8, Figure 18f.1 to Figure 18f.8, Figure 18g.1 to Figure 18g.5, and Figure 18h.1 to Figure 18h.8 when BTTI USFs are used. In RTTI configuration, two bursts of a radio block are mapped on one PDCH while the other two bursts are mapped onto the second PDCH of a PDCH pair. On the other hand, a BTTI USF belongs to one PDCH and is mapped on four consecutive bursts transmitted on that PDCH, i.e. two bursts belongs to one RTTI radio block while the other two bursts belong to another RTTI radio block. The detailed mapping is defined in 3GPP TS 45.002. + +The details of the EGPRS2 modulation and coding schemes are shown in tables 4a, 4b, 4c and 4d. The data rates exclude the RLC/MAC header(s). + +**Table 4a: Coding parameters for the EGPRS2-A modulation and coding schemes in the downlink** + +| Scheme | Code rate (Note 1) | Header Code rate | Modulation | RLC blocks per Radio Block | Raw Data within one Radio Block | Family | BCS | Tail payload | HCS | Data rate per PDCH kb/s | +|--------|--------------------|------------------|------------|----------------------------|---------------------------------|-------------|------|--------------|------|-------------------------| +| DAS-12 | 0.96 (1.00) | 0.38 | 32QAM | 3 | 1968 | B padding 2 | 3x12 | 3X12 | 8 | 98.4 | +| DAS-11 | 0.80 (0.84) | 0.38 | | 3 | 1632 | A padding 6 | | | | 81.6 | +| DAS-10 | 0.64 (0.66) | 0.33 | | 2 | 1312 | B padding 2 | 2x12 | 2x12 | | 65.6 | +| DAS-9 | 0.68 (0.71) | 0.34 | 16QAM | 2 | 1088 | A padding 6 | | 8 | 54.4 | | +| DAS-8 | 0.56 (0.59) | 0.34 | | 2 | 896 | B | 12 | | 1x12 | | +| DAS-7 | 0.54 (0.58) | 0.33 | 8-PSK | 1 | 656 | B padding 2 | | | | | +| DAS-6 | 0.45 (0.48) | 0.33 | | 1 | 544 | A padding 6 | | 8 | 27.2 | | +| DAS-5 | 0.37 (0.4) | 0.33 | | 1 | 448 | B | | | 22.4 | | + +DAS-5 to DAS-12 are used with normal symbol rate + +NOTE 1: The numbers in brackets indicate the coding rate for transmission using Fast Ack/Nack Reporting, when the PAN field is present. + +**Table 4b: Coding parameters for the EGPRS2-B modulation and coding schemes in the downlink** + +| Scheme | Code rate (N
ote 1) | Header
Code rate | Modulation | RLC blocks
per Radio
Block | Raw Data
within one
Radio
Block | Family | BCS | Tail
payload | HCS | Data rate
per PDCH
kb/s | +|--------|------------------------|---------------------|------------|----------------------------------|------------------------------------------|-------------------|------|-----------------|-----|-------------------------------| +| DBS-12 | 0.98
(1.00) | 0.37 | 32QAM | 4 | 2368 | A | 4x12 | 4X12 | 8 | 118.4 | +| DBS-11 | 0.91
(0.94) | 0.37 | | 4 | 2176 | A
padding
6 | | | | 108.8 | +| DBS-10 | 0.72
(0.75) | 0.34 | | 3 | 1776 | A | 3x12 | 3x12 | | 88.8 | +| DBS-9 | 0.71
(0.74) | 0.34 | 16QAM | 3 | 1344 | B | | | | 67.2 | +| DBS-8 | 0.60
(0.63) | 0.31 | | 2 | 1184 | A | 2x12 | 2x12 | | 59.2 | +| DBS-7 | 0.47
(0.49) | 0.31 | | 2 | 896 | B | | | | 44.8 | +| DBS-6 | 0.63
(0.69) | 0.31 | QPSK | 1 | 592 | A | 1x12 | 1x12 | | 29.6 | +| DBS-5 | 0.49
(0.53) | 0.31 | | 1 | 448 | B | | | | 22.4 | + +DBS-5 to DBS-12 are used with higher symbol rate + +NOTE 1: The numbers in brackets indicate the coding rate for transmission using Fast Ack/Nack Reporting, when the PAN field is present. + +**Table 4c: Coding parameters for the EGPRS2-A modulation and coding schemes in the uplink** + +| Scheme | Code rate
(Note 1) | Header
Code rate | Modulation | RLC blocks
per Radio
Block | Raw Data
within one
Radio
Block | Family | BCS | Tail
payload | HCS | Data rate
per PDCH
kb/s | +|--------|-----------------------|---------------------|------------|----------------------------------|------------------------------------------|--------------------|------|-----------------|-----|-------------------------------| +| UAS-11 | 0.95
(1.00) | 0.36 | 16QAM | 3 | 1536 | A
padding
10 | 3x12 | 3x6 | 8 | 76.8 | +| UAS-10 | 0.84
(0.88) | 0.36 | | 3 | 1344 | B | | | | 67.2 | +| UAS-9 | 0.71
(0.75) | 0.36 | | 2 | 1184 | A | 2x12 | 2x6 | | 59.2 | +| UAS-8 | 0.62
(0.65) | 0.36 | | 2 | 1024 | A
padding
10 | | | | 51.2 | +| UAS-7 | 0.55
(0.57) | 0.36 | | 2 | 896 | B | | | | 44.8 | + +UAS-7 to UAS-11 are used with normal symbol rate + +NOTE 1: The numbers in brackets indicate the coding rate for transmission using Fast Ack/Nack Reporting, when the PAN field is present. + +**Table 4d: Coding parameters for the EGPRS2-B modulation and coding schemes in the uplink** + +| Scheme | Code rate (Note 1) | Header Code rate | Modulation | RLC blocks per Radio Block | Raw Data within one Radio Block | Family | BCS | Tail payload | HCS | Data rate per PDCH kb/s | +|--------|--------------------|------------------|------------|----------------------------|---------------------------------|-----------------|------|--------------|-----|-------------------------| +| UBS-12 | 0.96 (1.00) | 0.35 | 32QAM | 4 | 2368 | A | 4x12 | 4X6 | 8 | 118.4 | +| UBS-11 | 0.89 (0.92) | 0.35 | | 4 | 2176 | A padding 6 | | | | 108.8 | +| UBS-10 | 0.71 (0.74) | 0.35 | | 3 | 1776 | A / A padding 6 | 3x12 | 3x6 | | 88.8 | +| UBS-9 | 0.70 (0.73) | 0.32 | 16QAM | 3 | 1344 | B | | | | 67.2 | +| UBS-8 | 0.60 (0.62) | 0.33 | | 2 | 1184 | A / A padding 6 | 2x12 | 2x6 | | 59.2 | +| UBS-7 | 0.46 (0.47) | 0.33 | | 2 | 896 | B | | | | 44.8 | +| UBS-6 | 0.62 (0.67) | 0.35 | QPSK | 1 | 592 | A / A padding 6 | 1x12 | 6 | | 29.6 | +| UBS-5 | 0.47 (0.52) | 0.35 | | 1 | 448 | B | | | | 22.4 | + +UBS-5 to UBS-12 are used with higher symbol rate +NOTE 1: The numbers in brackets indicate the coding rate for transmission using Fast Ack/Nack Reporting, when the PAN field is present. + +#### 6.5.5.2 Channel coding for PACCH, PBCCH, PAGCH, PPCH and PTCCH + +The channel coding for the PACCH, PBCCH, PAGCH, PPCH and downlink PTCCH is the same as the coding scheme CS-1 presented in subclause 6.5.5.1. + +The coding scheme used for uplink PTCCH is the same as for PRACH. + +For TBFs in RTTI configuration with BTTI USF mode, the channel coding for the downlink PACCH shall be the one defined for coding scheme MCS-0, see Table 4e. + +For TBF in RTTI configuration with RTTI USF mode, the channel coding for downlink PACCH may be the one defined either for MCS-0 described in Table 4e or for CS-1 described in subclause 6.5.5.1. An MS can know whether CS-1 or MCS-0 is used for downlink PACCH by examining the stealing bits. + +**Table 4e: Coding parameters for the MCS-0 coding scheme** + +| Scheme | Code rate (Note 2) | Header Code rate | Modulation | RLC blocks per Radio Block | Raw Data within one Radio Block | Family | BCS (Note 1) | Tail payload | HCS | Data rate kb/s | +|--------|--------------------|------------------|------------|----------------------------|---------------------------------|--------|--------------|--------------|-----|----------------| +| MCS-0 | 0.49 | 0.53 | GMSK | 1 | 176 | n/a | 18 | 6 | 8 | 17.6 | + +NOTE 1: The BCS is not encoded with the payload but is included in the header. +NOTE 2: A PAN cannot be transmitted with a block encoded using MCS-0. + +![Diagram illustrating the coding and puncturing process for MCS-0. The top row shows the input data: USF (3 bits), RLC/MAC Hdr (36 bits, Note 1), HCS, Control block (182 bits, 22 octets), and TB. This is followed by a 'Rate 1/3 convolutional coding' step. The next row shows the output of the coding: 12 bits, 108 bits, and 546 bits. Below this, 'puncturing' is applied to the 108 bits and 546 bits. The next row shows the result of puncturing: 12 bits, 68 bits, and 372 bits. A 'SB = 12' label is present. The final row shows the output of the puncturing process, which is a 464-bit burst, represented by four boxes.](fd3cbb53e991f8209ba17b398f426e13_img.jpg) + +The diagram illustrates the channel coding and puncturing process for MCS-0. At the top, the input data is shown as a sequence of fields: USF (3 bits), RLC/MAC Hdr (36 bits, Note 1), HCS, Control block (182 bits, 22 octets), and TB. This input is processed by a 'Rate 1/3 convolutional coding' block. The output of this block is shown in the next row as three segments: 12 bits, 108 bits, and 546 bits. Below this, a 'puncturing' step is applied to the 108 bits and 546 bits segments. The result of puncturing is shown in the next row as 12 bits, 68 bits, and 372 bits. A label 'SB = 12' is present. The final output is a 464-bit burst, represented by four boxes at the bottom. + +Diagram illustrating the coding and puncturing process for MCS-0. The top row shows the input data: USF (3 bits), RLC/MAC Hdr (36 bits, Note 1), HCS, Control block (182 bits, 22 octets), and TB. This is followed by a 'Rate 1/3 convolutional coding' step. The next row shows the output of the coding: 12 bits, 108 bits, and 546 bits. Below this, 'puncturing' is applied to the 108 bits and 546 bits. The next row shows the result of puncturing: 12 bits, 68 bits, and 372 bits. A 'SB = 12' label is present. The final row shows the output of the puncturing process, which is a 464-bit burst, represented by four boxes. + +NOTE 1: Includes the BCS for the control block + +**Figure 18i: Coding and puncturing for MCS-0** + +#### 6.5.5.2a Channel coding for CPBCCH, CPAGCH, CPPCH and CSCH + +The channel coding for the CPBCCH, CPAGCH and CPPCH is the same as the coding scheme CS-1 presented in subclause 6.5.5.1. The channel coding for the CSCH is identical to SCH. + +#### 6.5.5.3 Channel Coding for the PRACH, CPRACH and MPRACH + +Two types of packet access burst may be transmitted on the PRACH and MPRACH: an 8 information bits access burst or an 11 information bits access burst called the extended packet access burst. The mobile shall support both access bursts. The channel coding for both burst formats is indicated in the following subclauses. Only the 11 information bits access burst may be transmitted on the CPRACH. + +##### 6.5.5.3.1 Coding of the 8 data bit Packet Access Burst + +The channel coding used for the burst carrying the 8 data bit packet access uplink message is identical to the coding of the access burst as defined for random access channel in 3GPP TS 45.003 [12]. + +##### 6.5.5.3.2 Coding of the 11 data bit Packet Access Burst + +The channel coding for 11 bit access burst is the punctured version of the same coding as used for 8 bit access burst. + +### 6.5.6 Cell Re-selection + +NOTE: The text in this subclause is informative. The normative text is in 3GPP TS 43.022 and 3GPP TS 45.008 [15]. Where there is a conflict between these descriptions, the normative text has precedence. + +In GPRS Packet Idle and Packet Transfer modes, cell re-selection is performed by the MS, except for + +- a class A MS (see 3GPP TS 22.060 [2] ) while in dedicated mode in which case the cell is determined by the network according to the handover procedures; +- when the MS has been set in network control mode NC2 by the network or +- when the MS is in Cell Change Notification (CCN) mode (see subclause 6.5.6.4). + +The new cell re-selection criteria C31 and C32 are provided as a complement to the current GSM cell re-selection criteria. This provides a more general tool to make cell planning for GPRS as similar to existing planning in GSM as + +possible. C31 is a signal strength criterion used to decide whether prioritised cell re-selection shall be used. For cells that fulfil the C31 criterion, the cell with highest priority class shall be selected. If more than one cell has the highest priority, the one of those with the highest C32 value shall be selected. If no cell fulfils the C31 criterion, the one among all cells with the highest C32 value shall be selected. + +C32 is an improvement of C2. It applies an individual offset and hysteresis value to each pair of cells, as well as the same temporary offsets as for C2. Additional hysteresis values apply for a cell re-selection that requires cell or routing area update. + +Cell re-selection procedure apply to the MSs attached to GPRS if a PBCCH exists in the serving cell. If the PBCCH is not allocated, then the MS shall perform cell re-selection according to the C2 criteria. + +In addition, the network may control the cell re-selection as described in subclause 6.5.6.3 and/or assist the MS in the cell re-selection procedure as described in subclause 6.5.6.4. + +#### 6.5.6.1 Measurements for Cell Re-selection + +The MS shall measure the received RF signal strength on the BCCH frequencies of the serving cell and the neighbour cells as indicated in the BA-GPRS list, and calculate the received level average (RLA) for each frequency, as specified in 3GPP TS 45.008 [15]. In addition the MS shall verify the BSIC of the cells. Only channels with the same BSIC as broadcast together with BA-GPRS on PBCCH shall be considered for re-selection. + +A COMPACT capable MS shall in addition perform the above tasks for any CPBCCH, either transmitted in the serving cell or indicated, by way of frequency and time group in the BA-GPRS list. + +Any cell having a CPBCCH indicated in the BA-GPRS list shall be time synchronized to that cell, as specified in 3GPP TS 45.010 [16]. + +When the number of downlink PDCHs assigned to certain types of multislot MS (see 3GPP TS 45.002 [11], annex B) does not allow them to perform measurements within the TDMA frame, the network shall provide measurement windows to ensure that the MS can perform a required number of measurements. + +#### 6.5.6.2 Broadcast Information + +The PBCCH broadcasts GPRS specific cell re-selection parameters for serving and neighbour cells, including the BA (GPRS) list. A BA (GPRS) identifies the neighbour cells, including BSIC, that shall be considered for GPRS cell (re-selection (not necessary the same as for GSM in Idle or circuit switched mode)). + +#### 6.5.6.3 Optional measurement reports and network controlled cell re-selection + +It shall be possible for the network to order the mobile stations to send measurement reports to the network and to suspend its normal cell re-selection, and instead to accept decisions from the network. This applies to both Packet idle mode and Packet transfer mode. + +The degree to which the mobile station shall resign its radio network control shall be variable, and be ordered in detail by the parameter NETWORK\_CONTROL\_ORDER. + +Two sets of parameters are broadcast on PBCCH and are valid in Packet transfer and Packet idle modes respectively. NETWORK\_CONTROL\_ORDER can also be sent individually to an MS on PACCH, in which case it overrides the broadcast parameter. + +When a class A mobile station is simultaneously involved in a circuit switched service and in a GPRS transfer, the network controlled cell re-selection procedures (NC1 or NC2 modes of operation) should not be used. + +In this case, handover for the circuit switched service has precedence over GPRS network controlled cell re-selection, and the MS shall stop sending measurement reports and ignore cell change orders. + +#### 6.5.6.4 Network Assisted Cell Change + +The Network Assisted Cell Change option adds a possibility to + +- minimize the service outage time for an MS in the cell re-selection process, +- delay the cell re-selection until complete RLC-SDUs have been transferred. + +This is achieved without forcing the MS into either mode NC1 or NC2 and consequently eliminates the need to load the radio path with measurement reports (see subclause 6.5.6.3). + +The procedures related to Network Assisted Cell Change are optional for the network and mandatory for an MS. + +Network Assisted Cell Change consists mainly of two parts + +- One part that can assist an MS in packet transfer mode with neighbour cell system information required for initial packet access after a cell change; +- One part in which the mobile station notifies the network when the cell change criteria is fulfilled and delays the cell re-selection a short time to let the network respond with neighbour cell system information (CCN mode procedures). + +A mobile station in Packet Transfer mode may receive neighbour cell system information on PACCH. The neighbour cell information may consist of PSI1, PSI2 and PSI4 if a PBCCH is allocated in the target cell, or SI3, SI13 and SI1 (if available) if no PBCCH is allocated. The information shall be stored by the mobile station and is valid for 30 seconds. During that period the MS may use the information for initial access when entering the addressed neighbour cell. + +The neighbour cell system information is contained in the Packet Neighbour Cell Data message. + +The network indicates use of CCN on BCCH and PBCCH. If indicated or individually ordered by the network and when the MS is in packet transfer mode and in NC0 or NC1 mode but not in dedicated mode or in dual transfer mode, the MS shall enable CCN. When enabled, and when the criteria for cell re-selection are fulfilled, the MS shall enter CCN mode and notify the network. While in CCN mode the MS shall not change cell. + +In the notification to the network, the MS shall report a proposed cell identity and measurement results for the proposed and for other neighbour cells if available. The MS shall leave the CCN mode when either + +- The network responds with a Packet Cell Change Continue or a Packet Cell Change Order message or +- A certain time has elapsed or +- The MS enters Packet Idle Mode or +- The criteria for camping on the old cell is no longer fulfilled (see 3GPP TS 45.008). + +If the MS is in NC2 mode, dedicated mode or in dual transfer mode, the CCN mode is not applicable. + +### 6.5.7 Timing Advance + +NOTE: The text in this subclause is informative. The normative text is in 3GPP TS 44.060 [7] and 3GPP TS 45.010 [16]. Where there is a conflict between these descriptions, the normative text has precedence. + +The timing advance procedure is used to derive the correct value for timing advance that the MS has to use for the uplink transmission of radio blocks. This procedure is not used in dual transfer mode, in which case the timing advance procedures for dedicated mode are used. + +The timing advance procedure comprises two parts: + +- initial timing advance estimation; +- continuous timing advance update. + +#### 6.5.7.1 Initial timing advance estimation + +The initial timing advance estimation is based on the single access burst carrying the Packet Channel Request. The Packet Uplink Assignment or Packet Downlink Assignment then carries the estimated timing advance value to the MS. This value shall be used by the MS for the uplink transmissions until the continuous timing advance update provides a new value (see subclause 6.5.7.2.). Two special cases exist: + +- when Packet Queuing Notification is used the initial estimated timing advance may become too old to be sent in the Packet Downlink (/Uplink) Assignment +- when Packet Downlink (/Uplink) Assignment is to be sent without prior paging (i.e., in the Ready state), no valid timing advance value may be available. + +Then the network has three options: + +- Packet Polling Request can then be used to trigger the transmission of Packet Control Acknowledgement. This message can be formatted as four access burst from which the timing advance can be estimated. +- Packet Downlink (/Uplink) Assignment can be sent without timing advance information. In that case it is indicated to the MS that it can only start the uplink transmission after the timing advance is obtained by the continuous timing advance update procedure. +- The poll bit in the Packet Downlink (/Uplink) Assignment message can be set to trigger the transmission of Packet Control Acknowledgement. This can be used if System information indicates that acknowledgement is access bursts. + +For the case where timing advance information is not provided in the assignment message, the mobile is not allowed to send normal bursts on the uplink until it receives a valid timing advance either in Packet Timing Advance/Power Control message or through the continuous timing advance procedure. + +#### 6.5.7.2 Continuous timing advance update + +MS in Packet transfer mode shall use the continuous timing advance update procedure. The continuous timing advance update procedure is carried on the PTCCH assigned to the MS. + +For uplink packet transfer, within the Packet Uplink Assignment, the MS is assigned Timing Advance Index (TAI) and the PTCCH. + +For downlink packet transfer, within the Packet Downlink Assignment, the MS is assigned Timing Advance Index (TAI) and the PTCCH. + +The TAI specifies the PTCCH sub-channel used by the MS. + +On the uplink, the MS shall send in the assigned PTCCH access burst, which is used by the network to derive the timing advance. + +The network analyses the received access burst and determines new timing advance values for all MSs performing the continuous timing advance update procedure on that PDCH. The new timing advance values shall be sent via a downlink signalling message (TA-message) on PTCCH/D. Network can send timing advance information also in Packet Timing Advance/Power Control and Packet Uplink Ack/Nack messages on PACCH. + +##### 6.5.7.2.1 Mapping on the multiframe structure + +Figure 19 shows the mapping of the uplink access bursts and downlink TA-messages on groups of eight 52-multiframes: + +- the TAI value shows the position where a slot is reserved for a MS to send an access burst (e.g. T1 means 52-multiframe number n and idle slot number 2). TAI value defines the used PTCCH sub-channel. +- every second PDCH multiframe starts a downlink TA-message. + +###### 52-multiframe number n: + +![](dfafe39c233a62ec8ebd71e42992c14d_img.jpg) + +| | | | | | | | | | | | | | | | | | +|----------|--------------|----|----|---|----|----|----|--------------|----|----|----|---|----|-----|-----|---| +| uplink | TAI=0 | | | | | | | TAI=1 | | | | | | | | | +| | B0 | B1 | B2 | 0 | B3 | B4 | B5 | 1 | B6 | B7 | B8 | 2 | B9 | B10 | B11 | 3 | +| downlink | TA_message 1 | | | | | | | TA message 1 | | | | | | | | | + +###### 52-multiframe number n + 1: + +![](9e26cd5584f423e1b2155fb341db579f_img.jpg) + +| | | | | | | | | | | | | | | | | | +|----------|--------------|----|----|---|----|----|----|--------------|----|----|----|---|----|-----|-----|---| +| uplink | TAI=2 | | | | | | | TAI=3 | | | | | | | | | +| | B0 | B1 | B2 | 4 | B3 | B4 | B5 | 5 | B6 | B7 | B8 | 6 | B9 | B10 | B11 | 7 | +| downlink | TA message 1 | | | | | | | TA message 1 | | | | | | | | | + +###### 52-multiframe number n + 2: + +![](9c05ae298f897f405d4f0c72d98cb2c7_img.jpg) + +| | | | | | | | | | | | | | | | | | +|----------|--------------|----|----|---|----|----|----|--------------|----|----|----|----|----|-----|-----|----| +| uplink | TAI=4 | | | | | | | TAI=5 | | | | | | | | | +| | B0 | B1 | B2 | 8 | B3 | B4 | B5 | 9 | B6 | B7 | B8 | 10 | B9 | B10 | B11 | 11 | +| downlink | TA message 2 | | | | | | | TA message 2 | | | | | | | | | + +###### 52-multiframe number n + 3: + +![](a04291a026e9ac4a7b644e556a0672b4_img.jpg) + +| | | | | | | | | | | | | | | | | | +|----------|--------------|----|----|----|----|----|----|--------------|----|----|----|----|----|-----|-----|----| +| uplink | TAI=6 | | | | | | | TAI=7 | | | | | | | | | +| | B0 | B1 | B2 | 12 | B3 | B4 | B5 | 13 | B6 | B7 | B8 | 14 | B9 | B10 | B11 | 15 | +| downlink | TA message 2 | | | | | | | TA message 2 | | | | | | | | | + +###### 52-multiframe number n + 4: + +![](a02b188a5fd52c99f84255322873bf29_img.jpg) + +| | | | | | | | | | | | | | | | | | +|----------|--------------|----|----|----|----|----|----|--------------|----|----|----|----|----|-----|-----|----| +| uplink | TAI=8 | | | | | | | TAI=9 | | | | | | | | | +| | B0 | B1 | B2 | 16 | B3 | B4 | B5 | 17 | B6 | B7 | B8 | 18 | B9 | B10 | B11 | 19 | +| downlink | TA message 3 | | | | | | | TA message 3 | | | | | | | | | + +##### 52-multiframe number n + 5: + +![](a3c1310e720178d2450a3748c7c75422_img.jpg) + +| | | | | | | | | | | | | | | | | | +|----------|--------------|----|----|----|----|----|----|--------------|----|----|----|----|----|-----|-----|----| +| uplink | TAI=10 | | | | | | | TAI=11 | | | | | | | | | +| | B0 | B1 | B2 | 20 | B3 | B4 | B5 | 21 | B6 | B7 | B8 | 22 | B9 | B10 | B11 | 23 | +| downlink | TA message 3 | | | | | | | TA message 3 | | | | | | | | | + +###### 52-multiframe number n + 6: + +![](bdb44cc8120caccddc2adf0c3db54261_img.jpg) + +| | | | | | | | | | | | | | | | | | +|----------|--------------|----|----|----|----|----|----|--------------|----|----|----|----|----|-----|-----|----| +| uplink | TAI=12 | | | | | | | TAI=13 | | | | | | | | | +| | B0 | B1 | B2 | 24 | B3 | B4 | B5 | 25 | B6 | B7 | B8 | 26 | B9 | B10 | B11 | 27 | +| downlink | TA message 4 | | | | | | | TA message 4 | | | | | | | | | + +###### 52-multiframe number $n + 7$ : + +![Diagram showing the mapping of uplink access bursts and downlink timing advance signalling messages. The diagram consists of two rows of 32 frames. The top row is labeled 'uplink' and shows frames B0 through B11, followed by frames 28, 29, 30, and 31. Above frame 28 is 'TAI=14' and above frame 30 is 'TAI=15'. The bottom row is labeled 'downlink' and shows 'TA message 4' under frame 28 and 'TA message 4' under frame 30.](343e05a9fd8a8c8743428fa4ae6e2736_img.jpg) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------|----|----|----|----|----|----|----|----|----|----|----|--------------|-----|-----|----|--|--|--|--|--|--|--|--|--------------|--|--|--|--|--|--|--|--|--|--|--| +| uplink | | | | | | | | | | | | TAI=14 | | | | | | | | | | | | TAI=15 | | | | | | | | | | | | +| B0 | B1 | B2 | 28 | B3 | B4 | B5 | 29 | B6 | B7 | B8 | 30 | B9 | B10 | B11 | 31 | | | | | | | | | | | | | | | | | | | | | +| downlink | | | | | | | | | | | | TA message 4 | | | | | | | | | | | | TA message 4 | | | | | | | | | | | | + +Diagram showing the mapping of uplink access bursts and downlink timing advance signalling messages. The diagram consists of two rows of 32 frames. The top row is labeled 'uplink' and shows frames B0 through B11, followed by frames 28, 29, 30, and 31. Above frame 28 is 'TAI=14' and above frame 30 is 'TAI=15'. The bottom row is labeled 'downlink' and shows 'TA message 4' under frame 28 and 'TA message 4' under frame 30. + +B0 - B11 = Radio blocks + +Idle frames are numbered from 1 to 31 [odd numbers] + +PTCCH frames are numbered from 0 to 30 [even numbers] + +**Figure 19: Mapping of the uplink access bursts and downlink timing advance signalling messages (the figure applies also for the reduced TTI since the same 52-multiframe allocation of PTCCH and idle frames applies also for the reduced TTI configuration)** + +The BTS shall update the timing advance values in the next TA-message following the access burst. To illustrate this, an MS that transmits an access burst in frames numbered 0, 2, 4, or 6 receives its updated timing advance value in TA message 2. This MS can also find this updated timing advance value in subsequent TA messages 3, 4, and 1, but only has to read these if TA message 2 was not received correctly. + +An MS entering the Transfer state shall ignore the TA-messages until the MS has sent its first access burst. This is to avoid the use of timing advance values, derived from access bursts sent by the MS that previously used the same TAI. + +### 6.5.8 Power control procedure + +#### 6.5.8.0 General + +Power control shall be supported in order to improve the spectrum efficiency and to reduce the power consumption in the MS. + +For the uplink, the MS shall follow a flexible power control algorithm, which the network can optimise through a set of parameters. It can be used for both open loop and closed loop power control. + +For the downlink, the power control is performed in the BTS. Therefore, there is no need to specify the actual algorithms, but information about the downlink performance is needed. Therefore the MSs have to transfer Channel Quality Reports to the BTS. + +For the detailed specification of power control see 3GPP TS 45.008 [15]. + +In a downlink dual carrier configuration, power control shall be applied on the uplink, to each radio frequency channel independently. + +#### 6.5.8.1 MS output power + +The MS shall calculate the RF output power value, $P_{CH}$ , to be used on each individual uplink PDCH assigned to the MS: + +$$P_{CH} = \min((\Gamma_0 - \Gamma_{CH} - \alpha * (C + 48), P_{MAX})$$ + +where + +$\Gamma_{CH}$ is an MS and channel specific power control parameter. It is sent to the MS in any resource assigning message. Further, the network can, at any time during a packet transfer, send new $\Gamma_{CH}$ values to the MS on the downlink PACCH. + +$\Gamma_0$ is a frequency band dependent constant. + +$\alpha \in [0,1]$ is a system parameter. Its default value is broadcast on the PBCCH. Further, MS and channel specific values can be sent to the MS together with $\Gamma_{CH}$ . + +$C$ is the received signal level at the MS. + +$P_{MAX}$ is the maximum allowed output power in the cell. + +All power values are expressed in dBm. + +$P_{CH}$ is not used to determine the output power when accessing the cell on PRACH or RACH, in which case $P_{MAX}$ shall be used. + +#### 6.5.8.2 BTS output power + +The BTS shall use constant power on those PDCH radio blocks which contain PBCCH or which may contain PPCH. This power may be lower than the output power used on BCCH. The difference shall be broadcast on PBCCH. + +On the other PDCH radio blocks, downlink power control may be used. Thus, a procedure may be implemented in the network to control the power of the downlink transmission based on the Channel Quality Reports. + +The network shall ensure that the output power is sufficient for the MS for which the RLC block is intended as well as the MS(s) for which the USF is intended, and that for each MS in packet transfer mode, at least one downlink RLC block per multiframe is transmitted with an output power that is sufficient for that MS, on a block monitored by that MS. + +#### 6.5.8.3 Measurements at MS side + +A procedure shall be implemented in the MS to monitor periodically the downlink Rx signal level and quality from its serving cell. + +##### 6.5.8.3.1 Deriving the C value + +This subclause comprises information about how the MS shall derive the C value in the power control equation. + +The MS shall periodically measure the received signal strength. + +In packet idle mode, the MS shall measure the signal strength of the PCCCH or, if PCCCH is not existing, the BCCH. + +In packet transfer mode, the MS shall measure the signal strength on BCCH. The same measurements as for cell re-selection are used (see 6.5.6.1.). Alternatively, if indicated by a broadcast parameter, the MS shall measure the signal strength on one of the PDCHs in BTTI configuration or on one of the PDCH-pairs in RTTI configuration where the MS receives PACCH. This method is suitable in the case where BCCH is in another frequency band than the used PDCHs. It requires that constant output power is used on all downlink PDCH blocks. + +The MS shall measure the signal strength of each radio block monitored by the MS. The C value is achieved by filtering the signal strength with a running average filter. The filtering shall normally be continuous between the RR modes. In case there is a transition of the RR mode, the filtering shall be restarted if there is no valid C value during the previous RR mode (see 3GPP TS 45.008 [15]). The different filter parameters for the packet modes are broadcast on PBCCH or, if PBCCH does not exist, on BCCH. + +The variance of the received signal level within each block shall also be calculated. The filtered value $SIGN\_VAR$ shall be included in the channel quality report. + +##### 6.5.8.3.2 Derivation of Channel Quality Report + +The channel quality is measured as the interference signal level during the idle frames of the multiframe, when the serving cell is not transmitting. + +In packet transfer mode, the MS shall measure the interference signal strength of all eight channels (slots) on the same carrier as the assigned PDCHs. + +Some of the idle frames and PTCCH frames shall be used for this, while the others are required for BSIC identification and the timing advance procedure, see subclause 6.5.9. + +The MS may not be capable of measuring all eight channels when allocated some configurations of channels. The MS shall measure as many channels as its allocation allows considering its multislot capability. + +The slots that the MS measures on can be either idle or used by SACCH or PTCCH, depending on the channel type (TCH or PDCH). The MS shall therefore, for each slot, take the minimum signal strength of one idle frame and one PTCCH frame. Thus the SACCH frames are avoided (except for a TCH/H with two MSs) and only the interference is measured. + +The interference, $\gamma_{CH}$ , is achieved by filtering the measured interference in a running average filter. The filter parameters are broadcast on PBCCH or, if PBCCH does not exist, on BCCH. + +In packet transfer mode the MS shall transfer the 8 $\gamma_{CH}$ values and the RXQUAL, SIGN\_VAR and C values (see subclause 6.5.8.3.1) to the network in the Channel Quality Report included in the (EGPRS) PACKET DOWNLINK ACK/NACK message. + +In a downlink dual carrier configuration, channel quality measurements shall be performed for each radio frequency channel independently. Depending on the amount of information requested by the network (e.g. whether or not per-timeslot information is required) the MS may not be able to include channel quality measurements for both radio frequency channels within the EGPRS PACKET DOWNLINK ACK/NACK message. In this case, the MS shall include channel quality measurements for the radio frequency channel on which the poll was received. + +The channel quality measurements shall be performed based on radio blocks (see 3GPP TS 45.008 [15]). + +In BTTI configuration, if ordered by the network, the MS shall report the measurements performed on BTTI channel (PDCH, i.e. timeslot) in the EGPRS PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK Type 2 message (see 3GPP TS 44.060 [7]). + +In RTTI configuration, if ordered by the network, the MS shall report the measurements performed on RTTI channel (PDCH-pair, i.e. timeslot pair) in the EGPRS PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK Type 2 message (see 3GPP TS 44.060 [7]). + +#### 6.5.8.4 Measurements at BSS side + +A procedure shall be implemented in the BSS to monitor the uplink Rx signal level and quality on each uplink PDCH, active as well as inactive. + +The BSS shall also measure the Rx signal level and the quality of a specific MS packet transfer. + +### 6.5.9 Scheduling the MS activities during the PTCCH and idle frames + +The MS shall use the PTCCH and idle frames of the PDCH multiframe for the following tasks: + +- BSIC identification for cell re-selection (6.5.6.1) +- Continuous timing advance procedures (6.5.7.2) +- Interference measurements for power control (6.5.8.3.2) + +It is not necessary to exactly specify the scheduling of these tasks. + +The PTCCH frames used for timing advance signalling is stated in 6.5.7.2.1. During the frames when the MS receives TA-messages it can also make interference measurements. During the frames when the MS transmits access bursts it may also be possible to make measurements on some channels. + +The MS shall schedule the BSIC identification as efficiently as possible, using the remaining PTCCH frames and the idle frames and also considering the requirements for interference measurements. When the MS is synchronised to a BTS, it knows the timing of the SCH. Therefore, only a few certain frames are required for BSIC identification. In those frames it may also be possible to make measurements on some channels. When the MS shall synchronise to a new BTS, it has to prioritise that task. It may then use half of the PTCCH and idle frames, i.e. the same amount as available for circuit switched connections. + +The remaining PTCCH and idle frames shall be used for interference measurements. + +### 6.5.10 Discontinuous Reception (DRX) + +NOTE: The text in this subclause is informative. The normative text is in 3GPP TS 45.002 [11]. Where there is a conflict between these descriptions, the normative text has precedence. + +DRX (sleep mode) shall be supported when the MS is in Packet Idle mode. DRX is independent from MM states Ready and Standby. + +Negotiation of DRX parameters is per MS. An MS may choose to use DRX or not together with some operating parameters. The following parameters are established: + +- **DRX/non-DRX indicator** +It indicates whether the MS uses DRX or not. + +#### - **DRX period** + +A conditional parameter for MSs using DRX to determine the right paging group. The DRX period is defined by the parameter SPLIT\_PG\_CYCLE. + +#### - **Non-DRX timer** + +A conditional parameter for MSs using DRX to determine the time period within which the non-DRX mode is kept after leaving the Transfer state. The support for this feature is optional on the network side and the information about the maximum supported value for the timer in the cell is broadcast on PBCCH. + +An MS in DRX mode is only required to monitor the radio blocks defined by its paging group as defined in 3GPP TS 45.002 [11]. + +Paging group definition based on SPLIT\_PG\_CYCLE is optional on CCCH for both BTS and MS. If not supported, the definition based on BS\_PA\_MFRMS shall be used. The parameters used to define the paging group for GPRS are shown in the Table 5, together with the corresponding GSM parameters. BS\_PCC\_CHANS is the number of PDCHs containing PCCCH. For Compact, BS\_PCC\_CHANS is the number of radio frequency channels per cell carrying CPCCCHs including the radio frequency channel carrying the CPBCCH. + +An MS in non-DRX mode is required to monitor all the radio blocks where PCCCH or (for Compact) CPCCCH may be mapped on the PDCH defined by its paging group. + +When page for circuit-switched services is conveyed on PPCH, it follows the same scheduling principles as the page for packet data. The same is valid for scheduling of resource assignments for downlink packet transfers for MSs in Ready State (i.e. where no paging is performed). + +NOTE: Paging reorganisation may be supported in the same way as for circuit switched GSM. + +**Table 5: Parameters for DRX operation** + +| Parameter | GPRS | | Corresponding GSM parameters | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|--------------------------------------|------------------------------| +| | PCCCH | CCCH | CCCH | +| DRX period | SPLIT_PG_CYCLE | BS_PA_MFRMS *)
SPLIT_PG_CYCLE **) | BS_PA_MFRMS | +| Blocks not available for PPCH or CPPCH per multiframe | BS_PAG_BLKS_RES +
BS_PBCCH_BLKS | BS_AG_BLKS_RES | BS_AG_BLKS_RES | +| Number of physical channels containing paging;
or
for Compact, number of radio frequency channels per cell carrying CPCCCHs including the radio frequency channel carrying the CPBCCH. | BS_PCC_CHANS | BS_CC_CHANS | BS_CC_CHANS | + +\*) Only when DRX period split is not supported. + +\*\*) Only when DRX period split is supported. + +## 6.6 Medium Access Control and Radio Link Control Layer + +The Medium Access Control (MAC) and Radio Link Control (RLC) layer operates above the Physical Link layer in the reference architecture. MAC/RLC layer messages and signalling procedures are defined in 3GPP TS 44.060 [7] and 3GPP TS 44.018 [6]. + +### 6.6.1 Layer Services + +The MAC function defines the procedures that enable multiple MSs to share a common transmission medium, which may consist of several physical channels. The MAC function provides arbitration between multiple MSs attempting to transmit simultaneously and provides collision avoidance, detection and recovery procedures. The operations of the MAC function may allow a single MS to use several physical channels in parallel. + +The RLC function defines the procedures for a bitmap selective retransmission of unsuccessfully delivered RLC data blocks. + +The RLC/MAC function provides three modes of operation: + +- unacknowledged operation; +- acknowledged operation; and +- non-persistent operation + +### 6.6.2 Layer Functions + +The GPRS MAC function is responsible for: + +- Providing efficient multiplexing of data and control signalling on both uplink and downlink, the control of which resides on the Network side. On the downlink, multiplexing is controlled by a scheduling mechanism. On the uplink, multiplexing is controlled by medium allocation to individual users (e.g., in response to service request). +- For mobile originated channel access, contention resolution between channel access attempts, including collision detection and recovery. +- For mobile terminated channel access, scheduling of access attempts, including queuing of packet accesses. +- Priority handling. + +The GPRS RLC function is responsible for: + +- Interface primitives allowing the transfer of Logical Link Control layer PDUs (LLC-PDU) between the LLC layer and the MAC function. +- Segmentation and re-assembly of LLC-PDUs into RLC data blocks. +- Backward Error Correction (BEC) procedures enabling the selective retransmission of uncorrectable code words. +- Transmission of code words according to the channel conditions, i.e. link adaptation. + +NOTE: The Block Check Sequence for error detection is provided by the Physical Link Layer. + +In EGPRS incremental redundancy (IR) mode, RLC function is also responsible for: + +- Storing soft values of the erroneous RLC data blocks and combining them with the retransmitted RLC data blocks. + +### 6.6.3 Service Primitives + +Table 6 lists the service primitives provided by the RLC/MAC layer to the upper layers: + +**Table 6: Service primitives provided by the RLC/MAC layer to the upper layers** + +| Name | request | indication | response | confirm | comments | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|------------|----------|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RLC/MAC-DATA | x | x | | | used for the transfer of upper layer PDUs. Acknowledged mode of operation in RLC is used (Note). The upper layer shall be able to request high transmission quality via a primitive parameter. | +| RLC/MAC-UNITDATA | x | x | | | used for the transfer of upper layer PDUs. Unacknowledged mode or non-persistent mode of operation in RLC is used (Note). | +| RLC/MAC-PTM_DATA | [?] | [?] | [?] | [?] | used for the transfer of upper layer PDUs over point-to-multipoint bearers. Non-persistent mode of operation in RLC is used. | +| RLC/MAC-STATUS | | x | | | used to indicate that an error has occurred on the radio interface. The cause for the failure is indicated. | +| NOTE: The RLC/MAC layer in the network may decide to use a different RLC mode than requested by the upper layers, in any case for downlink TBFs and, for uplink TBFs, when both the mobile station and the network support multiple TBFs procedures. If the mobile station supports RLC non-persistent mode, the RLC/MAC layer in the network may decide to allocate an EGPRS TBF that uses this RLC mode. | | | | | | + +### 6.6.4 Model of Operation + +Each PDCH is a shared medium between multiple MSs and the Network except in dual transfer mode, in which a PDCH may be dedicated to one MS. Direct communication is possible only between an MS and the network. + +The GPRS radio interface consists of asymmetric and independent uplink and downlink channels. The downlink carries transmissions from the network to multiple MSs and does not require contention arbitration. The uplink is shared among multiple MSs and requires contention control procedures. + +The allocation of radio resources by the PLMN and the use of these resources by the MSs can be broken down into two parts: + +- The PLMN allocates radio resources for the GPRS (uplink and downlink) in a symmetric manner. +- The allocated uplink and downlink radio resources for point-to-point or point-to-multipoint services are used independently of each other. Dependent allocation of uplink and downlink shall be possible, in order to allow simple MSs to transfer data simultaneously in both directions. Allocation of several PDTCHs for one MS is possible. + +The access to the GPRS uplink uses a Slotted-Aloha based reservation protocol. + +The Network Protocol Data Units (N-PDU) are segmented into the Subnetwork Protocol Data Units (SN-PDU) by the Subnetwork Dependent Convergence (SNDC) protocol and SN-PDUs are encapsulated into one or several LLC frames. See 3GPP TS 23.060 [3] for information on SNDC and LLC. The details on SNDC can be found in 3GPP TS 44.065 [9] and the details on LLC can be found in 3GPP TS 44.064 [8]. LLC frames are segmented into RLC data blocks. At the RLC/MAC layer, a selective ARQ protocol (including block numbering) between the MS and the Network provides retransmission of erroneous RLC data blocks. When a complete LLC frame is successfully transferred across the RLC layer, it is forwarded to the LLC layer. + +![Figure 20: Transmission and reception data flow for GPRS and EGPRS. The diagram shows the mapping of an LLC frame to RLC blocks and then to four normal bursts across three layers: LLC layer, RLC/MAC layer, and Physical layer. The LLC frame consists of a Frame Header (FH), an Information field, and a Frame Check Sequence (FCS). The Information field is mapped into three RLC blocks: one Primary block and two Following blocks. Each RLC block contains a Block Header (BH), an Info field, and a Block Check Sequence (BCS). Each RLC block is then mapped to a Normal burst in the Physical layer. Vertical double-headed arrows on the right indicate the boundaries between the layers.](694df81535f89c7bfb9ef0df6f130dc0_img.jpg) + +LLC frame + +FH | Information field | FCS + +RLC blocks + +BH | Info field | BCS | BH | Info field | BCS | BH | Info field | BCS + +Primary block      Following block + +Normal burst | Normal burst | Normal burst | Normal burst + +LLC layer + +RLC/MAC layer + +Physical layer + +FH = Frame Header +FCS = Frame Check Sequence +BH = Block Header +BCS = Block Check Sequence + +Figure 20: Transmission and reception data flow for GPRS and EGPRS. The diagram shows the mapping of an LLC frame to RLC blocks and then to four normal bursts across three layers: LLC layer, RLC/MAC layer, and Physical layer. The LLC frame consists of a Frame Header (FH), an Information field, and a Frame Check Sequence (FCS). The Information field is mapped into three RLC blocks: one Primary block and two Following blocks. Each RLC block contains a Block Header (BH), an Info field, and a Block Check Sequence (BCS). Each RLC block is then mapped to a Normal burst in the Physical layer. Vertical double-headed arrows on the right indicate the boundaries between the layers. + +Figure 20: Transmission and reception data flow for GPRS and EGPRS + +Transmission and reception data flows are same for GPRS and EGPRS, except for EGPRS MCS-9, MCS-8 and MCS-7, where four normal bursts carry two RLC blocks (one RLC block within two bursts for MCS-9 and MCS-8), as shown on Figures 21 and 22. + +![Figure 21: Transmission and reception data flow for EGPRS MCS-7. This diagram is similar to Figure 20 but shows a different mapping for the EGPRS MCS-7 mode. The LLC frame's Information field is mapped into two RLC blocks: one Primary block and one Following block. Each RLC block is then mapped to two Normal bursts in the Physical layer, for a total of four Normal bursts. The RLC block structure (BH, Info field, BCS) remains the same. Vertical double-headed arrows on the right indicate the boundaries between the layers.](6231ba981d3d1ab7ce0cae71abd08c17_img.jpg) + +LLC frame + +FH | Information field | FCS + +RLC blocks + +BH | Info field | BCS | BH | Info field | BCS | BH | Info field | BCS + +Primary block      Following blocks + +Normal burst | Normal burst | Normal burst | Normal burst + +LLC layer + +RLC/MAC layer + +Physical layer + +Figure 21: Transmission and reception data flow for EGPRS MCS-7. This diagram is similar to Figure 20 but shows a different mapping for the EGPRS MCS-7 mode. The LLC frame's Information field is mapped into two RLC blocks: one Primary block and one Following block. Each RLC block is then mapped to two Normal bursts in the Physical layer, for a total of four Normal bursts. The RLC block structure (BH, Info field, BCS) remains the same. Vertical double-headed arrows on the right indicate the boundaries between the layers. + +Figure 21: Transmission and reception data flow for EGPRS MCS-7 + +![Diagram of data flow for EGPRS MCS-9 and MCS-8 showing LLC frame, RLC blocks, and Physical layer mapping.](2a476a0b3dbc3429436246db4784ff9f_img.jpg) + +This diagram illustrates the transmission and reception data flow for EGPRS MCS-9 and MCS-8 across three layers: + +- LLC frame:** Consists of a Header (FH), an Information field, and a Frame Check Sequence (FCS). The Information field is shown being segmented into multiple RLC blocks. +- RLC blocks:** Each block contains a Header (BH), an Info field, and a Block Check Sequence (BCS). The first block is designated as the **Primary block**, and the subsequent blocks are **Following blocks**. +- Physical layer:** Each RLC block is mapped to a **Normal burst**. There are four Normal bursts shown, corresponding to the four RLC blocks. + +On the right side, three horizontal lines with double-headed arrows represent the interfaces between the **LLC layer**, the **RLC/MAC layer**, and the **Physical layer**. + +Diagram of data flow for EGPRS MCS-9 and MCS-8 showing LLC frame, RLC blocks, and Physical layer mapping. + +Figure 22: Transmission and reception data flow for EGPRS MCS-9 and MCS-8 + +![Diagram of data flow for EGPRS2 DAS-7, DAS-6 and DAS-5 showing LLC Frame, RLC Blocks, and Physical Layer mapping.](60a40901e77feeb97ab6cf9c6d9418c3_img.jpg) + +This diagram illustrates the transmission and reception data flow for EGPRS2 DAS-7, DAS-6 and DAS-5 across three layers: + +- LLC Frame:** Consists of a Header (FH), an Information Field, and a Frame Check Sequence (FCS). The Information Field is shown being segmented into multiple RLC Blocks. +- RLC Blocks:** Each block contains a Header (BH), an Info Field, and a Block Check Sequence (BCS). The first block is designated as the **Primary Block**, and the subsequent blocks are **Following Block**. +- Physical Layer:** Each RLC Block is mapped to a **Normal Burst**. There are four Normal Bursts shown, corresponding to the four RLC Blocks. + +On the right side, three horizontal lines with double-headed arrows represent the interfaces between the **LLC Layer**, the **RLC/MAC Layer**, and the **Physical Layer**. + +Diagram of data flow for EGPRS2 DAS-7, DAS-6 and DAS-5 showing LLC Frame, RLC Blocks, and Physical Layer mapping. + +Figure 22a: Transmission and reception data flow for EGPRS2 DAS-7, DAS-6 and DAS-5 + +![Diagram of data flow for EGPRS2 DAS-10, DAS-9, DAS-8, UAS-9, UAS-8 and UAS-7. It shows the mapping of an LLC Frame to RLC Blocks and then to Normal Bursts across three layers: LLC Layer, RLC/MAC Layer, and Physical Layer.](0931f3e098bd4539041de11c50cec2d2_img.jpg) + +The diagram illustrates the data flow for EGPRS2 DAS-10, DAS-9, DAS-8, UAS-9, UAS-8 and UAS-7. It consists of three layers: LLC Layer, RLC/MAC Layer, and Physical Layer. + +- LLC Layer:** Contains an **LLC Frame** with fields: **FH**, **Information Field**, and **FCS**. +- RLC/MAC Layer:** Contains **RLC Blocks**. The **Information Field** of the LLC frame is mapped to the **Info Field** of the RLC blocks. The **FH** is mapped to the **BH** (Header) of the RLC blocks. The **FCS** is mapped to the **BCS** (Trailer) of the RLC blocks. The RLC blocks are organized into a **Primary Block** (BH, Info Field, BCS) and **Following Blocks** (BH, Info Field, BCS). There are 4 RLC blocks in total. +- Physical Layer:** Contains **Normal Bursts**. Each RLC block is mapped to one **Normal Burst**. There are 4 Normal Bursts in total. + +Vertical double-headed arrows on the right indicate the boundaries between the **LLC Layer**, **RLC/MAC Layer**, and **Physical Layer**. + +Diagram of data flow for EGPRS2 DAS-10, DAS-9, DAS-8, UAS-9, UAS-8 and UAS-7. It shows the mapping of an LLC Frame to RLC Blocks and then to Normal Bursts across three layers: LLC Layer, RLC/MAC Layer, and Physical Layer. + +Figure 22b: Transmission and reception data flow for EGPRS2 DAS-10, DAS-9, DAS-8, UAS-9, UAS-8 and UAS-7 + +![Diagram of data flow for EGPRS2 DAS-12, DAS-11, UAS-11 and UAS-10. It shows the mapping of an LLC Frame to RLC Blocks and then to Normal Bursts across three layers: LLC Layer, RLC/MAC Layer, and Physical Layer.](57939c16065211317c5442cf2a4009e0_img.jpg) + +The diagram illustrates the data flow for EGPRS2 DAS-12, DAS-11, UAS-11 and UAS-10. It consists of three layers: LLC Layer, RLC/MAC Layer, and Physical Layer. + +- LLC Layer:** Contains an **LLC Frame** with fields: **FH**, **Information Field**, and **FCS**. +- RLC/MAC Layer:** Contains **RLC Blocks**. The **Information Field** of the LLC frame is mapped to the **Info Field** of the RLC blocks. The **FH** is mapped to the **BH** (Header) of the RLC blocks. The **FCS** is mapped to the **BCS** (Trailer) of the RLC blocks. The RLC blocks are organized into a **Primary Block** (BH, Info Field, BCS) and **Following Blocks** (BH, Info Field, BCS). There are 8 RLC blocks in total. +- Physical Layer:** Contains **Normal Bursts**. Each RLC block is mapped to one **Normal Burst**. There are 8 Normal Bursts in total. + +Vertical double-headed arrows on the right indicate the boundaries between the **LLC Layer**, **RLC/MAC Layer**, and **Physical Layer**. + +Diagram of data flow for EGPRS2 DAS-12, DAS-11, UAS-11 and UAS-10. It shows the mapping of an LLC Frame to RLC Blocks and then to Normal Bursts across three layers: LLC Layer, RLC/MAC Layer, and Physical Layer. + +Figure 22c: Transmission and reception data flow for EGPRS2 DAS-12, DAS-11, UAS-11 and UAS-10 + +![Diagram of data flow for EGPRS2 DBS-6, DBS-5, UBS-6 and UBS-5. It shows the mapping of an LLC Frame (FH, Information Field, FCS) into RLC Blocks (BH, Info Field, BCS). The RLC blocks are categorized into a Primary Block and Following Blocks. These are then mapped to four HSR Bursts at the Physical Layer. The layers shown are LLC Layer, RLC/MAC Layer, and Physical Layer.](ffb6acd27b8e3a54392840948a75869f_img.jpg) + +**LLC Frame** + +FH | Information Field | FCS + +**RLC Blocks** + +BH | Info Field | BCS | BH | Info Field | BCS | BH | Info Field | BCS + +**Primary Block** | **Following Block** + +HSR Burst | HSR Burst | HSR Burst | HSR Burst + +**LLC Layer** + +**RLC/MAC Layer** + +**Physical Layer** + +Diagram of data flow for EGPRS2 DBS-6, DBS-5, UBS-6 and UBS-5. It shows the mapping of an LLC Frame (FH, Information Field, FCS) into RLC Blocks (BH, Info Field, BCS). The RLC blocks are categorized into a Primary Block and Following Blocks. These are then mapped to four HSR Bursts at the Physical Layer. The layers shown are LLC Layer, RLC/MAC Layer, and Physical Layer. + +HSR = Higher Symbol Rate + +Figure 22d: Transmission and reception data flow for EGPRS2 DBS-6, DBS-5, UBS-6 and UBS-5 + +![Diagram of data flow for EGPRS2 DBS-8, DBS-7, UBS-8 and UBS-7. It shows the mapping of an LLC Frame (FH, Information Field, FCS) into RLC Blocks (BH, Info Field, BCS). The RLC blocks are categorized into a Primary Block and Following Blocks. These are then mapped to four HSR Bursts at the Physical Layer. The layers shown are LLC Layer, RLC/MAC Layer, and Physical Layer.](cc893412ff9ca2426705e878c75548ba_img.jpg) + +**LLC Frame** + +FH | Information Field | FCS + +**RLC Blocks** + +BH | Info Field | BCS | BH | Info Field | BCS | BH | Info Field | BCS | BH | Info Field | BCS + +**Primary Block** | **Following Block** + +HSR Burst | HSR Burst | HSR Burst | HSR Burst + +**LLC Layer** + +**RLC/MAC Layer** + +**Physical Layer** + +Diagram of data flow for EGPRS2 DBS-8, DBS-7, UBS-8 and UBS-7. It shows the mapping of an LLC Frame (FH, Information Field, FCS) into RLC Blocks (BH, Info Field, BCS). The RLC blocks are categorized into a Primary Block and Following Blocks. These are then mapped to four HSR Bursts at the Physical Layer. The layers shown are LLC Layer, RLC/MAC Layer, and Physical Layer. + +Figure 22e: Transmission and reception data flow for EGPRS2 DBS-8, DBS-7, UBS-8 and UBS-7 + +![Figure 22f: Transmission and reception data flow for EGPRS2 DBS-10, DBS-9, UBS-10 and UBS-9. The diagram shows data flow from the LLC Layer down to the Physical Layer. At the LLC Layer, an LLC Frame is shown with fields FH, Information Field, and FCS. The Information Field is segmented into RLC Blocks, each containing BH, Info Field, and BCS. These are grouped into a Primary Block and Following Blocks. The Primary Block and Following Blocks are mapped to HSR Bursts at the Physical Layer. The RLC/MAC Layer and Physical Layer are indicated by horizontal lines with double-headed arrows.](719ef0f734259484038b2434e5dc3f24_img.jpg) + +The diagram illustrates the data flow for EGPRS2 DBS-10, DBS-9, UBS-10 and UBS-9. It shows the mapping of LLC frames to RLC blocks and then to HSR bursts. The LLC frame consists of a Header (FH), an Information Field, and a Footer (FCS). The Information Field is divided into RLC blocks, each with a Header (BH), an Information Field, and a Footer (BCS). These RLC blocks are grouped into a Primary Block and Following Blocks. The Primary Block and Following Blocks are then mapped to HSR bursts at the Physical Layer. The RLC/MAC Layer and Physical Layer are shown as horizontal lines with double-headed arrows, indicating bidirectional data flow. + +Figure 22f: Transmission and reception data flow for EGPRS2 DBS-10, DBS-9, UBS-10 and UBS-9. The diagram shows data flow from the LLC Layer down to the Physical Layer. At the LLC Layer, an LLC Frame is shown with fields FH, Information Field, and FCS. The Information Field is segmented into RLC Blocks, each containing BH, Info Field, and BCS. These are grouped into a Primary Block and Following Blocks. The Primary Block and Following Blocks are mapped to HSR Bursts at the Physical Layer. The RLC/MAC Layer and Physical Layer are indicated by horizontal lines with double-headed arrows. + +**Figure 22f: Transmission and reception data flow for EGPRS2 DBS-10, DBS-9, UBS-10 and UBS-9** + +![Figure 22g: Transmission and reception data flow for EGPRS2 DBS-12, DBS-11, UBS-12 and UBS-11. This diagram is similar to Figure 22f but shows a different mapping of RLC blocks to HSR bursts. The LLC frame and RLC block structure are the same. The RLC blocks are grouped into a Primary Block and Following Blocks. The Primary Block and Following Blocks are mapped to HSR bursts at the Physical Layer. The RLC/MAC Layer and Physical Layer are indicated by horizontal lines with double-headed arrows.](b63f41ca262d8ce9ef8affb62607f32b_img.jpg) + +The diagram illustrates the data flow for EGPRS2 DBS-12, DBS-11, UBS-12 and UBS-11. It shows the mapping of LLC frames to RLC blocks and then to HSR bursts. The LLC frame consists of a Header (FH), an Information Field, and a Footer (FCS). The Information Field is divided into RLC blocks, each with a Header (BH), an Information Field, and a Footer (BCS). These RLC blocks are grouped into a Primary Block and Following Blocks. The Primary Block and Following Blocks are then mapped to HSR bursts at the Physical Layer. The RLC/MAC Layer and Physical Layer are shown as horizontal lines with double-headed arrows, indicating bidirectional data flow. + +Figure 22g: Transmission and reception data flow for EGPRS2 DBS-12, DBS-11, UBS-12 and UBS-11. This diagram is similar to Figure 22f but shows a different mapping of RLC blocks to HSR bursts. The LLC frame and RLC block structure are the same. The RLC blocks are grouped into a Primary Block and Following Blocks. The Primary Block and Following Blocks are mapped to HSR bursts at the Physical Layer. The RLC/MAC Layer and Physical Layer are indicated by horizontal lines with double-headed arrows. + +**Figure 22g: Transmission and reception data flow for EGPRS2 DBS-12, DBS-11, UBS-12 and UBS-11** + +#### 6.6.4.1 Multiplexing MSs on the same PDCH + +##### 6.6.4.1.1 Uplink State Flag: Dynamic Allocation + +###### 6.6.4.1.1.1 Multiplexing of GPRS, EGPRS or EGPRS2 MSs + +The Uplink State Flag (USF) is used on PDCH to allow multiplexing of Radio blocks from a number of MSs. USF is used in dynamic and extended dynamic medium access modes. USF is used only in downlink direction. + +The USF comprises 3 bits at the beginning of each Radio Block that is sent on the downlink. It enables the coding of 8 different USF states which are used to multiplex the uplink traffic. + +On PCCCH, one USF value is used to denote PRACH. The other USF values are used to reserve the uplink for different MSs. On PDCHs not carrying PCCCH, the eight USF values are used to reserve the uplink for different MSs. On a PDCH carrying MPRACH (whether it carries PCCCH or not), one USF value is used to denote MPRACH; this value is indicated by the network in the notification message (see 3GPP TS 44.060). One USF value shall be used to prevent collision on uplink channel, when MS without USF is using uplink channel. The USF points either to the next uplink Radio Block or the sequence of 4 uplink Radio Blocks starting with the next uplink Radio Block. + +###### 6.6.4.1.1.2 Multiplexing of GPRS, EGPRS and EGPRS2 MSs + +The GPRS, EGPRS and EGPRS2 MSs can be multiplexed dynamically on the same PDCH by utilising the USF. When uplink resources are assigned to a GPRS mobile station or an EGPRS/EGPRS2 mobile station using a multislot configuration only compatible with its GPRS multislot class, the network must use GMSK, i.e. CS-1 to CS-4, MCS-0, or MCS-1 to MCS-4, and the USF must point to the sequence of four uplink Radio Blocks starting with the next uplink Radio Block. + +The dynamic allocation using USF granularity requires that a GPRS MS can read the USF in an EGPRS GMSK block. This is enabled by setting the stealing bits in the EGPRS GMSK blocks to indicate CS-4. The coding and interleaving of the USF is done as defined for CS-4. This leads to: + +1. A standard GPRS MS will be able to detect the USF in EGPRS GMSK blocks. The risk that the rest of the block will be misinterpreted as valid information is assumed to be low. +2. An EGPRS MS can not differentiate CS-4 blocks and EGPRS GMSK blocks by only looking at the stealing bits. This is however not needed for USF detection, since the USF is signalled in the same way. Further, assuming that the EGPRS MS knows if it is in EGPRS or standard GPRS mode, it will only have to try to decode the remainder of the GMSK blocks in one way in order to determine if they were aimed for it. + +An EGPRS mobile station shall be able to decode the USF that allocates the uplink to that mobile station irrespective of which of the modulation and coding schemes CS-1 to CS-4, MCS-0, MCS-1 to MCS-9, or DAS-5 to DAS-7 that is used. + +A mobile station supporting EGPRS2-A in the downlink shall be able to decode the USF that allocates the uplink to that mobile station irrespective of which of the modulation and coding schemes CS-1 to CS-4, MCS-0, MCS-1 to MCS-9, or DAS-5 to DAS-12 that is used. + +A mobile station supporting EGPRS2-B in the downlink shall be able to decode the USF that allocates the uplink to that mobile station irrespective of which of the modulation and coding schemes CS-1 to CS-4, MCS-0, MCS-1 to MCS-9, DAS-5 to DAS-12, or DBS-5 to DBS-12 that is used. + +For mobile station synchronization reasons, if GPRS, EGPRS or EGPRS2 mobile stations using a multislot configuration only compatible with their GPRS multislot class are multiplexed on the PDCH, at least one downlink radio block every 360ms shall be transmitted to each MS with a coding scheme and a modulation that can be decoded by that MS. + +##### 6.6.4.1.2 Void + +##### 6.6.4.1.3 Exclusive Allocation + +Exclusive allocation is used to reserve the uplink part of the PDCH for only one MS during the life of the Temporary Block Flow. In exclusive allocation, all the uplink blocks of the uplink part of the PDCH are available to the MS for transmission. + +#### 6.6.4.2 Temporary Block Flow + +A Temporary Block Flow (TBF) is a physical connection used by the two RR entities to support the unidirectional transfer of LLC PDUs on packet data physical channels. The TBF is assigned radio resource on one or more PDCHs and comprise a number of RLC/MAC blocks carrying one or more LLC PDUs. A TBF is temporary and is maintained only for the duration of the data transfer. + +#### 6.6.4.3 Temporary Flow Identity + +Each TBF is assigned a Temporary Flow Identity (TFI) by the network. The assigned TFI is unique among concurrent TBFs in each directions and is used instead of the MS identity in the RLC/MAC layer. The same TFI value may be used concurrently for TBFs in opposite directions. The TFI is assigned in a resource assignment message that precedes the transfer of LLC frames belonging to one TBF to/from the MS. The same TFI is included in every RLC header belonging to a particular TBF as well as in the control messages associated to the LLC frame transfer (e.g. acknowledgements) in order to address the peer RLC entities. + +#### 6.6.4.4 Medium Access modes + +Three medium access modes are supported: + +- Dynamic allocation, +- Extended Dynamic allocation, and +- Exclusive allocation. + +The Dynamic allocation medium access mode shall be supported by all networks that support GPRS. The support of Extended Dynamic allocation and Exclusive allocation medium access modes is optional. + +The Dynamic allocation shall be supported in all mobile stations. The support for Exclusive allocation is optional for mobile stations supporting DTM. + +#### 6.6.4.5 Acknowledged mode for RLC/MAC operation + +##### 6.6.4.5.1 GPRS + +The transfer of RLC data blocks in the RLC acknowledged mode is controlled by a selective ARQ mechanism coupled with the numbering of the RLC data blocks within one Temporary Block Flow. The sending side (the MS or the network) transmits blocks within a window and the receiving side sends Packet Uplink Ack/Nack or Packet Downlink Ack/Nack message when needed. Every such message acknowledges all correctly received RLC data blocks up to an indicated block sequence number (BSN), thus “moving” the beginning of the sending window on the sending side. Additionally, the bitmap that starts at the same RLC data block is used to selectively request erroneously received RLC data blocks for retransmission. The sending side then retransmits the erroneous RLC data blocks, eventually resulting in further sliding the sending window. + +The Packet Ack/Nack message does not include any change in the current assignment (and thus does not have to be acknowledged when sent on downlink). A missing Packet Ack/Nack is not critical and a new one can be issued whenever. In Packet Downlink Ack/Nack message, the MS may optionally initiate an uplink TBF. + +When receiving uplink data from an MS the network shall, based on erroneous blocks received from MS, allocate additional resources for retransmission. + +The acknowledgement procedure of the LLC layer is not combined with the acknowledgement procedure on the underlying RLC/MAC layer. + +##### 6.6.4.5.2 EGPRS and EGPRS2 + +The transfer of RLC data blocks in the RLC acknowledged mode can be controlled by a selective type I ARQ mechanism, or by type II hybrid ARQ (incremental redundancy: IR) mechanism, coupled with the numbering of the RLC data blocks within one Temporary Block Flow. The sending side (the MS or the network) transmits blocks within a window and the receiving side sends Packet Uplink Ack/Nack or Packet Downlink Ack/Nack message when needed. + +For a TBF with FANR activated, the receiving side may also send ack/nack information piggy-backed in radio blocks for data transfer sent in the other direction. + +According to the link quality, an initial modulation and coding scheme is selected for an RLC block. For the retransmissions, the same or another modulation and coding scheme from the same family of the modulation and coding schemes can be selected. E.g. if MCS-7 is selected for the first transmission of an RLC block, any modulation and coding scheme of the family B can be used for the retransmissions. The selection of modulation and coding scheme is controlled by the network. + +In the EGPRS/EGPRS2 type II Hybrid ARQ scheme, the information is first sent with one of the initial code rates (i.e., the rate 1/3 encoded data is punctured with the puncturing scheme (PS) 1 of the selected modulation and coding scheme). If the RLC data block is received in error, additional coded bits (i.e., the output of the rate 1/3 encoded data which is punctured with PS 2 of the prevailing modulation and coding scheme) are sent and decoded together with the already received codewords until decoding succeeds. If all the codewords (different punctured versions of the encoded data block) have been sent, the first codeword (which is punctured with PS 1) is sent. Alternatively, for EGPRS it is possible to use incremental redundancy modes called MCS-5-7 and MCS-6-9, in which the initial transmissions are sent with either MCS-5 or MCS-6 (respectively) and the retransmissions are sent with MCS-7 or MCS-9 (respectively). Header part is robustly coded so that the receiver is able to determine the block identities for all transmissions, even if the payload cannot be decoded. + +In the EGPRS/EGPRS2 type I ARQ, the operation is similar to the one of the EGPRS/EGPRS2 type II hybrid ARQ, except that the decoding of an RLC data block is solely based on the prevailing transmission (i.e., erroneous blocks are not stored). + +Type II hybrid ARQ is mandatory in EGPRS MS and EGPRS2 MS receivers and the associated performance requirements are specified in 3GPP TS 45.005 [14]. + +#### 6.6.4.6 Unacknowledged mode for RLC/MAC operation + +The transfer of RLC data blocks in the unacknowledged RLC/MAC mode is controlled by the numbering of the RLC data blocks within one Temporary Block Flow and does not include any retransmissions. The receiving side extracts user data from the received RLC data blocks and attempts to preserve the user information length by replacing missing RLC data blocks by dummy information bits. + +The same mechanism and message format for sending temporary acknowledgement messages is used as for acknowledged mode in order to convey the necessary control signalling (e.g. monitoring of channel quality for downlink channel or timing advance correction for uplink transfers). The fields for denoting the erroneous RLC blocks may be used as an additional measure for channel quality (i.e. parameter for link adaptation). The sending side (the MS or the network) transmits a number of radio blocks and then polls the receiving side to send an acknowledgement message. The Packet Uplink Ack/Nack and Packet Downlink Ack/Nack message does not include any change in the current assignment. A missing acknowledgement message is not critical and a new one can be obtained whenever. In Packet Downlink Ack/Nack message, the MS may optionally initiate an uplink TBF. + +#### 6.6.4.6a Non-persistent mode for RLC/MAC operation + +The non-persistent RLC/MAC mode may be used for the transmission of RLC data blocks over an EGPRS TBF and an EGPRS2 TBF and is always used for the transmission of RLC data blocks over an MBMS bearer. + +The transfer of RLC data blocks in non-persistent RLC/MAC mode is controlled by the numbering of the RLC data blocks within one Temporary Block Flow and may include retransmissions. Selective type I ARQ or type II hybrid ARQ mechanisms may be used. It is not expected that every RLC data block is correctly received at receiving RLC endpoint (see TS 44.060). If some RLC data blocks are not received, the receiving side attempts to preserve the user information length by replacing missing RLC data blocks by dummy information bits. + +Packet Uplink Ack/Nack, EGPRS Packet Downlink Ack/Nack, and MBMS Downlink Ack/Nack messages (for MBMS bearers) are used for sending temporary acknowledgement messages and for conveying the necessary control signalling (e.g. monitoring of channel quality for downlink channel or timing advance correction for uplink transfers). + +For a TBF with FANR activated, the receiving side may also send ack/nack information piggy-backed in radio blocks for data transfer sent in the other direction. + +#### 6.6.4.7 Mobile Originated Packet Transfer + +##### 6.6.4.7.1 Uplink Access + +###### 6.6.4.7.1.1 On the (P)RACH + +This sub-clause applies to all mobile stations in packet idle mode. It also applies to class A mobile stations in dedicated mode if they are not DTM capable. + +![Sequence diagram showing the access and assignment for uplink packet transfer between an MS and a Network. The diagram illustrates two possible methods: one-phase and two-phase packet access.](9d1df8fe4616b242b4846c78ea8970f5_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Network + Note left of MS: (Optional) + MS->>Network: Packet Channel Request + Network-->>MS: Packet Uplink Assignment (PRACH (or RACH)) + Note left of MS: (Optional) + MS->>Network: Packet Resource Request + Network-->>MS: Packet Uplink Assignment (PACCH) + +``` + +The diagram illustrates the interaction between a Mobile Station (MS) and a Network for uplink packet transfer. It shows two possible methods: one-phase and two-phase packet access. In the one-phase method, the MS sends a Packet Channel Request on the PRACH (or RACH), and the Network responds with a Packet Uplink Assignment on the PAGCH (or AGCH). In the two-phase method, the MS sends a Packet Channel Request on the PRACH (or RACH), and the Network responds with a Packet Resource Request on the PACCH. The MS then sends a Packet Uplink Assignment on the PACCH. The first two steps are optional, and the last two steps are also optional. + +Sequence diagram showing the access and assignment for uplink packet transfer between an MS and a Network. The diagram illustrates two possible methods: one-phase and two-phase packet access. + +**Figure 23: Access and assignment for the one or two phase packet access, uplink packet transfer** + +An MS initiates a packet transfer by making a Packet Channel Request on PRACH or RACH. The network responds on PAGCH or AGCH respectively. It is possible to use one or two phase packet access method (see Figure 23). + +In the one phase access, the Packet Channel Request is responded by the network with the Packet Uplink Assignment reserving the resources on PDCH(s) for uplink transfer of a number of Radio blocks. The reservation is done accordingly to the information about the requested resources that is comprised in the Packet Channel Request. On RACH, there is only two cause values available for denoting GPRS, which can be used to request limited resources or two phase access. On PRACH, the Packet Channel Request may contain more adequate information about the requested resources and, consequently, uplink resources on one or several PDCHs can be assigned by using the Packet Uplink Assignment message. + +In the two phase access, the Packet Channel Request is responded with the Packet Uplink Assignment which reserves the uplink resources for transmitting the Packet Resource Request. A two phase access can be initiated by the network or a mobile station. The network can order the MS to send Packet Resource Request message by setting parameter in Packet Uplink Assignment message. Mobile station can request two phase access in Packet Channel Request message. In this case, the network orders MS to send Packet Resource Request message. + +The Packet Resource Request message carries the complete description of the requested resources for the uplink transfer. The MS can indicate the medium access method, it prefers to be used during the TBF. The network responds with the Packet Uplink Assignment reserving resources for the uplink transfer and defining the actual parameters for data transfer (e.g. medium access mode). + +When the network supports multiple TBF procedures a mobile station that supports multiple TBF procedures may request multiple uplink TBFs by sending a Packet Resource Request message during a two-phase access. In this case the Packet Resource Request message carries the PFI and channel request description for each requested uplink TBF. The network may respond with one or more instances of a MULTIPLE TBF UPLINK ASSIGNMENT message. These assignment messages always include an indication of the PFI associated with each uplink TBF for which resources are being allocated. + +If there is no response to the Packet Channel Request within predefined time period, the MS makes a retry after a random backoff time. + +On PRACH there is used a 2-step approach including a long-term and a short-term estimation of the persistence (see Figure 24). The optimal persistence of the mobile stations is calculated at the network side. + +![Figure 24a: Basic principle of random access traffic control. The diagram shows the interaction between a mobile station and the network side. On the mobile station side, there are three stacked boxes: 'decoding of parameters', 'persistence control', and 'access control'. Arrows show a downward flow from 'decoding of parameters' to 'persistence control' to 'access control'. On the network side, there are three stacked boxes: 'long-term estimation', 'short-term estimation', and 'access analysis'. Arrows show an upward flow from 'access analysis' to 'short-term estimation' to 'long-term estimation'. Between the two sides, three horizontal arrows connect corresponding boxes: 'set P' (persistence instruction) from network to mobile, 'contention levels P(i)' from mobile to network, and 'access (priority i)' from mobile to network.](a175bdeacb50b8a60869f6c68c5d0a07_img.jpg) + +Figure 24a: Basic principle of random access traffic control. The diagram shows the interaction between a mobile station and the network side. On the mobile station side, there are three stacked boxes: 'decoding of parameters', 'persistence control', and 'access control'. Arrows show a downward flow from 'decoding of parameters' to 'persistence control' to 'access control'. On the network side, there are three stacked boxes: 'long-term estimation', 'short-term estimation', and 'access analysis'. Arrows show an upward flow from 'access analysis' to 'short-term estimation' to 'long-term estimation'. Between the two sides, three horizontal arrows connect corresponding boxes: 'set P' (persistence instruction) from network to mobile, 'contention levels P(i)' from mobile to network, and 'access (priority i)' from mobile to network. + +**Figure 24a: Basic principle of random access traffic control** + +The actual persistence values depend on: + +- the priority $i$ of the packet to be transmitted; +- the amount of traffic within higher priority classes; +- the amount of traffic within the own priority class. + +Optionally, the existing backoff algorithm on RACH can be used on PRACH. + +On RACH, the existing backoff algorithm shall be used. + +Occasionally, more Packet Channel Requests can be received than can be served. To handle this, a Packet Queuing Notification is transmitted to the sender of the Packet Channel Request. The notification includes information that the Packet Channel Request message is correctly received and Packet Uplink Assignment may be transmitted later. If the Timing Advance information becomes inaccurate for an MS, the network can send Packet Polling Request to trigger the MS to send four random access bursts. This can be used to estimate the new Timing Advance before issuing the Packet Uplink Assignment. + +###### 6.6.4.7.1.2 On the main DCCH + +This clause only applies to mobile stations in dedicated mode that support DTM. This procedure moves the mobile station from dedicated mode to dual transfer mode. + +![Sequence diagram showing the access and assignment for the packet request procedure, uplink packet transfer. The diagram illustrates the interaction between the MS (Mobile Station) and the Network. The MS sends a DTM Request message to the Network on the Main DCCH. The Network responds with either a DTM Assignment Command or a Packet Assignment message, both sent on the Main DCCH. Finally, the MS sends an Assignment Complete message to the Network on the Main DCCH.](c2f36c545b190860d04e1d84e58d22cc_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Network + Note right of Network: Main DCCH + MS->>Network: DTM Request + Note right of Network: Main DCCH + Network-->>MS: DTM Assignment Command + Note right of Network: or + Note right of Network: Main DCCH + Network-->>MS: Packet Assignment + Note right of Network: Main DCCH + MS-->>Network: Assignment Complete + +``` + +Sequence diagram showing the access and assignment for the packet request procedure, uplink packet transfer. The diagram illustrates the interaction between the MS (Mobile Station) and the Network. The MS sends a DTM Request message to the Network on the Main DCCH. The Network responds with either a DTM Assignment Command or a Packet Assignment message, both sent on the Main DCCH. Finally, the MS sends an Assignment Complete message to the Network on the Main DCCH. + +**Figure 24b: Access and assignment for the packet request procedure, uplink packet transfer** + +A DTM mobile station initiates a packet transfer while in dedicated mode by sending a DTM Request message on the main DCCH. + +The DTM Request message carries a description of the requested resources for the uplink transfer and shall only be used to request one uplink TBF. The DTM Request message is responded by the network with one of the following DTM assignment messages: + +- DTM Assignment Command: sent when the network assigns a TBF and reassignment of the resource of the RR connection is needed. +- Packet Assignment: sent when the network allocates a TBF and no reallocation of the resource of the RR connection is needed. + +The DTM Assignment Command may be sent during DTM if the mobile station and network support multiple TBF procedures, reallocation of a combination of one or more ongoing uplink and downlink TBFs is needed and the resource of the RR connection is needed (i.e. the DTM Assignment Command shall not be used to provide resource assignments for new uplink TBFs when there are ongoing TBFs). In this case, any ongoing TBFs not addressed by the DTM Assignment Command are released. + +If there is reallocation of the resource of the RR connection (through a DTM Assignment Command message), the MS sends an Assignment Complete message on the new main DCCH after it is established. + +When a mobile station that supports multiple TBF procedures has entered dual transfer mode as described above where an uplink TBF is operating in exclusive allocation mode then no additional uplink TBFs may be established. If exclusive allocation is not used in dual transfer mode the mobile station may request one or more additional uplink TBFs by sending a Packet Resource Request message on the PACCH: + +- The Packet Resource Request message carries the PFI and channel request description for each requested uplink TBF. +- The network may respond with a Packet Uplink Assignment message, a Multiple TBF Uplink Assignment message or a Multiple TBF Timeslot Reconfigure message reserving resources for the requested uplink data transfers and defining the actual parameters for each uplink data transfer (e.g. medium access mode). + +If the uplink TBFs requested in the Packet Resource Request require re-allocation of the RR connection then the network sends a DTM Assignment Command which re-allocates the RR connection and a combination of one or more ongoing uplink and downlink TBFs (i.e. any ongoing TBFs not addressed by the DTM Assignment Command are + +released). Any outstanding uplink TBF requests received on the old resources will be responded to by the network on the newly allocated resources. + +##### 6.6.4.7.2 Dynamic/Extended Dynamic allocation + +###### 6.6.4.7.2.1 Uplink Packet Transfer + +The Packet Uplink Assignment, the Multiple TBF Uplink Assignment, Packet Timeslot Reconfigure and the Multiple TBF Timeslot Reconfigure messages include the list of PDCHs and the corresponding USF value per PDCH for each uplink TBF they assign resources for. A unique TFI is allocated and is thereafter included in each RLC Data and Control Block related to that Temporary Block Flow. The MS monitors the USFs on the downlink PDCHs corresponding to (i.e. with the same timeslot number as) the uplink PDCHs assigned for each TBF and transmits Radio blocks on those PDCHs which currently bear the USF value reserved for the usage of the MS on each TBF. + +For a TBF with FANR activated, the MS additionally monitors the downlink PDCHs (respectively PDCH pairs) corresponding to the uplink PDCHs (respectively PDCH pairs) assigned for each TBF to detect the presence of PAN fields containing ack/nack information for that mobile station. + +In a downlink dual carrier configuration, the MS shall respond in the radio block indicated by the USF on the same radio frequency channel as the one where the USF was received. The network shall not indicate a combination of USFs which would lead to the allocation to an MS of uplink radio blocks on both radio channels in any given radio block period. + +If the resource allocated by the network in the case of extended dynamic allocation does not allow the multislot MS (see 3GPP TS 45.002 [11]) to monitor the USF on all the downlink PDCHs corresponding to the assigned uplink PDCHs, the following rules shall apply: + +- Whenever the MS receives its USF on one downlink PDCH (e.g. on timeslot 0 while timeslots 0, 2 and 3 were assigned), it shall consider the corresponding uplink block and all subsequent ones from the list of assigned PDCHs as allocated (e.g. on 0, 2 and 3). Hence, if the network allocates a block to this MS on an assigned PDCH, it shall also allocate blocks to this MS on all subsequent PDCHs in the list. For each allocated block, the network shall set the USF to the value reserved for the usage of that MS. These rules apply on a block period basis. +- During block periods where it is transmitting, the MS shall monitor the USF on each downlink PDCH in the list of PDCHs corresponding to the assigned uplink PDCHs, up to and including the last PDCH that the MS is capable of receiving, according to the current uplink timeslot allocation and the switching requirements of its multislot class (see 3GPP TS 45.002 [11]). This rule applies on a block period basis. For example, if timeslots 0, 2 and 3 have been assigned and blocks are currently allocated on timeslots 2 and 3, then during this block period a MS for which $T_{ta}=1$ or $T_{tb}=1$ monitors USF on timeslots 0, 2 and 3. If the reserved value of USF is found on timeslot 0, then the next allocated blocks shall be on timeslots 0, 2 and 3 (thus increasing the timeslot allocation); if the reserved value of USF is found on timeslot 2, then the next allocated blocks shall be on timeslots 2 and 3 (thus maintaining the timeslot allocation unchanged); if the reserved value of USF is found on timeslot 3, then the next allocated block shall be on timeslot 3 (thus reducing the timeslot allocation by one timeslot). And so on for the subsequent block periods. MSs for which $T_{ta}>1$ or $T_{tb}>1$ are unable to monitor the USF on timeslot 3; for these MSs, in order to reduce the timeslot allocation, the network needs to leave at least one block period with no blocks allocated to the MS. Because each Radio Block includes an identifier (TFI), all received Radio blocks are correctly associated with a particular LLC frame and a particular MS, thus making the protocol highly robust. By altering the state of USF, different PDCHs can be "opened" and "closed" dynamically for certain MSs thus providing a flexible reservation mechanism. Additionally, packets with higher priority and pending control messages can temporarily interrupt a data transmission from one MS. +- In the case of dual transfer mode, if the mobile station supports DTM high multislot class capability, the network may assign uplink PDCHs whose corresponding downlink PDCH can never be monitored by the mobile station because of the presence of the uplink dedicated channel. In this case, the mobile station shall monitor only those downlink PDCHs that are feasible when taking into account the position of the uplink dedicated channel and the switching requirements of its multislot class (see 3GPP TS 45.002 [11]). + +The channel reservation algorithm can also be implemented on assignment basis. This allows individual MSs to transmit a predetermined amount of time without interruptions. + +The MS may be allowed to use the uplink resources as long as there is queued data on the RLC/MAC layer to be sent from the MS. It can comprise a number of LLC frames. In that sense the radio resources are assigned on the initially + +“unlimited” time basis. Alternatively, the uplink assignment for each assignment may be limited to a number of radio blocks (e.g. in order to offer more fair access to the medium at higher loads). + +The selective ARQ operation for the acknowledged RLC/MAC mode is described in Subclause 6.6.4.5. The unacknowledged RLC/MAC mode operation is described in Subclause 6.6.4.6. The non-persistent RLC/MAC mode operation is described in Subclause 6.6.4.6a. + +Figure 25 shows an example of message sequence for the (multislot) uplink data transfer with one resource reallocation and possible RLC data block re-transmissions. + +![Sequence diagram showing dynamic allocation uplink data transfer between MS and Network.](86bd357c573c9696393f5bde4d4cce4f_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Network + Note over MS, Network: Access and Assignment + MS->>Network: Data Block (PDTC) + MS->>Network: Data Block (PDTC) + MS->>Network: Data Block (PDTC) + MS->>Network: Data Block (last in send window) (PDTC) + Network->>MS: Packet Uplink Ack/Nack (PACCH) + MS->>Network: Data Block (PDTC) + MS->>Network: Data Block (PDTC) + MS->>Network: Data Block (PDTC) + Network->>MS: Packet Uplink Assignment (PACCH) + Network->>MS: Packet Control Acknowledgement (PACCH) + MS->>Network: Data Block (PDTC) + MS->>Network: Data Block (last) (PDTC) + Network->>MS: Packet Uplink Ack/Nack (final) (PACCH) + +``` + +The diagram illustrates a sequence of messages between a Mobile Station (MS) and a Network. It begins with an 'Access and Assignment' phase. The MS then transmits a series of 'Data Block' messages over 'PDTC' channels. The fourth block is labeled 'last in send window'. The Network responds with a 'Packet Uplink Ack/Nack' over a 'PACCH' channel. The MS continues with three more 'Data Block' messages. The Network then sends a 'Packet Uplink Assignment' and a 'Packet Control Acknowledgement' over 'PACCH'. The MS sends two final 'Data Block' messages, the last one labeled '(last)'. The Network concludes the sequence with a 'Packet Uplink Ack/Nack (final)' over 'PACCH'. + +Sequence diagram showing dynamic allocation uplink data transfer between MS and Network. + +**Figure 25: An example of dynamic allocation uplink data transfer** + +###### 6.6.4.7.2.2 Release of the Resources + +The release of the resources allocated for a TBF is normally initiated from the MS by counting down the last couple of blocks sent for that TBF. + +For the normal release of resources for RLC connection carrying a mobile originated packet transfer, the mechanism based on acknowledged final Packet Uplink Ack/Nack combined with timers is used. + +After the MS has sent its last RLC data block (indicated by the countdown field), the acknowledgement is expected from the network side. By sending the last block, the MS may no longer use the same assignment unless a negative acknowledgement arrives. It also means that the network side may reassign the same USF(s) to some other user as soon as all the RLC data blocks belonging to that Temporary Block Flow are correctly received; that regardless of the possible later errors in the acknowledgements. + +The next step, in the case of all RLC data blocks being correctly received, is that the network sends Packet Uplink Ack/Nack which is to be immediately acknowledged by the MS in the reserved uplink block period. It must be possible for the network not to use the mechanism of acknowledgement for Packet Ack/Nack in which case the release of the resources procedure relies only on timers. The TFI can be reused for another assignment either upon the reception of the acknowledgement for Packet Ack/Nack or after expiry of the guard timer. + +Further, the premature release or change of assignment for one MS may be initiated: + +- by the network with an explicit message +- in dual transfer mode, by the release of the RR connection (i.e. handover, assignment and channel release procedures) or +- by the establishment of an RR connection. + +In the case of release, the MS is ordered to interrupt the Temporary Block Flow for the TBF being released. The MS shall then reorganise the uplink buffer and issue a new Packet Channel Request to continue the uplink transfer with the RLC data blocks containing untransferred (i.e. on the RLC/MAC layer unacknowledged) LLC frames. + +A change in assignment may also be initiated by the network, in which case the Packet Uplink Assignment, Packet Timeslot Reconfigure, Multiple TBF Uplink Assignment, Multiple TBF Timeslot Reconfigure, DTM Assignment Command or Packet Assignment message is issued. + +##### 6.6.4.7.3 Void + +##### 6.6.4.7.4 Exclusive Allocation + +Exclusive allocation uses the Packet Uplink Assignment, Packet Timeslot Reconfigure, DTM Assignment Command or Packet Assignment messages to communicate a exclusive uplink resource allocation to the MS. The exclusive allocation consists of a start frame and a slot assignment. The MS waits until the start frame indicated and then starts transmitting the radio blocks. The exclusive allocation includes neither the USF nor the block assignment bitmap. The MS is free to transmit on the uplink without monitoring the downlink for the USF. Unused USF values may be used to prevent other mobiles from transmitting. A unique TFI is assigned and is thereafter included in each RLC data and downlink control block related to that Temporary Block Flow. Because each Radio Block includes an identifier (TFI or TLLI), all received Radio blocks are correctly associated with a particular LLC frame and a particular MS. + +When a mobile station that supports multiple TBF procedures is in dual transfer mode where exclusive allocation is used, only one uplink TBF can be established. If exclusive allocation is not used in dual transfer mode then a mobile station that supports multiple TBF procedures may request the establishment of multiple uplink TBFs (i.e. in this case the mobile station must support a DTM multislot class that allows for more than one uplink timeslot). In this case the mobile station shall always indicate the PFI associated with each uplink TBF that it requests and all uplink TBFs shall operate using dynamic allocation or extended dynamic allocation. + +The selective ARQ operation for the acknowledged RLC/MAC mode is described in Subclause 6.6.4.5. The unacknowledged RLC/MAC mode operation is described in Subclause 6.6.4.6. The non-persistent RLC/MAC mode operation is described in Subclause 6.6.4.6a. + +Figure 25 shows an example of message sequence for the (multislot) uplink data transfer with one resource reallocation and possible RLC data block re-transmissions. + +##### 6.6.4.7.5 Contention Resolution + +Contention resolution is an important part of RLC/MAC protocol operation, especially because one channel allocation can be used to transfer a number of LLC frames. Contention resolution does not apply to the packet request procedures while in dedicated mode for an MS supporting DTM. + +There are two basic access possibilities, one phase and two phase access as defined in Subclause 6.6.4.7.1. + +The two phase access is inherently immune for possibility that two MSs can perceive the same channel assignment as their own. Namely the second access phase, the Packet Resource Request, uniquely identifies the MS by its TLLI. The same TLLI is included in the Packet Uplink Assignment/Packet Downlink Assignment and no mistake is possible. + +The one phase access is somewhat insecure and an efficient contention resolution mechanism has to be introduced. + +The first part of the solution is the identification of the MS. The identification of transmitting MS on the RLC/MAC level is necessary not only for contention resolution but also to be able to establish RLC protocol entity for that Temporary Block Flow on the network side. Additionally, the TLLI is necessary to be able to match simultaneous uplink and downlink packet transfers by taking into consideration multislot capability of that MS. + +In order to uniquely identify the MS when sending on uplink, the RLC Header for all the RLC data blocks on uplink is extended to include the TLLI until the contention resolution is completed on the MS side. + +The second part of the solution is the notification from the network side about who owns the allocation. That is solved by the inclusion of the TLLI in the Packet Uplink Ack/Nack/Packet Downlink Ack/Nack. This message shall be sent in an early stage, even before the receive window for RLC/MAC protocol operation is full. By doing so, the contention is resolved after the first occurrence of Packet Ack/Nack. The possibility of RLC data blocks being captured from “wrong” MS, thus destroying the LLC frame, shall be covered for by retransmissions on the LLC layer. + +#### 6.6.4.8 Mobile Terminated Packet Transfer + +##### 6.6.4.8.1 Packet Paging + +The network initiates a packet transfer to an MS that is in the Standby state by sending one or more packet paging request messages on the downlink PPCH or PCH. The MS responds to one packet paging request message by initiating a mobile originated packet transfer, as described in section 6.6.4.7. This mobile originated packet transfer allows the MS to send a packet paging response to the network. The packet paging response is one or more RLC/MAC data blocks containing an arbitrary LLC frame. The message sequence described in Figure 26 below is conveyed either on PCCCH or on CCCH. After the packet paging response is sent by the MS and received by the network, the mobility management state of the MS is Ready. + +The network can then assign some radio resources to the MS and perform the downlink data transfer as described in section 6.6.4.8.2. + +![Figure 26: Paging message sequence for Paging, downlink packet transfer. The diagram shows a sequence of messages between an MS and a Network. The Network sends a 'Packet Paging Request (or Paging Request)' on PPCH (or PCH) to the MS. The MS responds with a 'Packet Channel Request (or Channel Request)' on PRACH (or RACH) to the Network. The Network replies with a 'Packet Uplink Assignment (or Immediate Assignment)' on PCCCH (or CCCH) to the MS. The MS then sends an optional 'Packet Resource Request' on PACCH to the Network. The Network responds with an optional 'Packet Uplink Assignment' on PACCH to the MS. Finally, the Network sends a 'Packet Paging Response (LLC frame)' on PDTCH to the MS. The sequence ends with ellipses.](0cc154cbdde7cc6c39f394597c7aca0c_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Network + Note right of Network: PPCH (or PCH) + Network->>MS: Packet Paging Request (or Paging Request) + Note right of MS: PRACH (or RACH) + MS->>Network: Packet Channel Request (or Channel Request) + Note right of Network: PCCCH (or CCCH) + Network->>MS: Packet Uplink Assignment (or Immediate Assignment) + Note right of MS: (Optional) PACCH + MS->>Network: Packet Resource Request + Note right of Network: PACCH + Network->>MS: Packet Uplink Assignment + Note right of Network: PDTCH + Network->>MS: Packet Paging Response (LLC frame) + Note right of MS: ... + +``` + +Figure 26: Paging message sequence for Paging, downlink packet transfer. The diagram shows a sequence of messages between an MS and a Network. The Network sends a 'Packet Paging Request (or Paging Request)' on PPCH (or PCH) to the MS. The MS responds with a 'Packet Channel Request (or Channel Request)' on PRACH (or RACH) to the Network. The Network replies with a 'Packet Uplink Assignment (or Immediate Assignment)' on PCCCH (or CCCH) to the MS. The MS then sends an optional 'Packet Resource Request' on PACCH to the Network. The Network responds with an optional 'Packet Uplink Assignment' on PACCH to the MS. Finally, the Network sends a 'Packet Paging Response (LLC frame)' on PDTCH to the MS. The sequence ends with ellipses. + +Figure 26: Paging message sequence for Paging, downlink packet transfer + +##### 6.6.4.8.2 Downlink Packet Transfer + +The transmission of a packet to an MS in the Ready state is initiated by the network using a packet downlink assignment message. In case there is an uplink packet transfer in progress, the packet downlink assignment message (Packet Downlink Assignment, Multiple TBF Downlink Assignment, Packet Timeslot Reconfigure or a Multiple TBF Timeslot Reconfigure) is transmitted on PACCH. Else, in case there is no uplink or downlink transfer in progress and if there is a PCCCH allocated in the cell, the Packet Downlink Assignment or Multiple TBF Uplink Assignment message is transmitted on PCCCH. If there is no PCCCH allocated in the cell the Immediate Assignment message is transmitted on CCCH. For a DTM MS in dedicated mode, the assignment message is transmitted on the main DCCH. The packet downlink assignment messages include the list of PDCH(s) that will be used for downlink transfer. The Timing Advance and Power Control information is also included, if available. Otherwise, the MS may be requested to respond with a Packet Control Acknowledgement (see also Subclause 6.5.7 on timing advance procedures). The MS multislot capability needs to be considered. + +The network sends the RLC/MAC blocks belonging to one Temporary Block Flow on downlink on the assigned downlink channels. + +Multiplexing the RLC/MAC blocks destined for different MSs on the same PDCH downlink is enabled with an identifier, e.g. TFI, included in each RLC/MAC block. The interruption of data transmission to one MS is possible. + +The acknowledged (i.e. selective ARQ operation) RLC/MAC mode operation is described in subclause 6.6.4.5; the unacknowledged RLC/MAC mode operation is described in subclause 6.6.4.6; the non-persistent RLC/MAC mode operation is described in subclause 6.6.4.6a. The sending of the Packet Downlink Ack/Nack message is obtained by the occasional network initiated polling of the MS. The MS sends the Packet Downlink Ack/Nack message in a reserved radio block which is allocated together with polling. Unassigned USF value is used in the downlink radio block which corresponds to the reserved uplink radio blocks. Further, if the MS wants to send some additional signalling or uplink data, it may be indicated in the Packet Downlink Ack/Nack message. + +For a TBF with FANR activated, the network may poll the mobile station to trigger the FANR procedure. In case the mobile station has at least one concurrent TBF in the uplink, the mobile station transmits, in a reserved radio block which is allocated together with polling, a radio block for data transfer including a PAN field with ack/nack information. Additionally, if enabled at TBF establishment/reconfiguration, the mobile station may initiate the FANR procedure in an event-based manner. Whenever an out-of-sequence condition is detected, or the RLC/MAC header of a radio block for data transfer is correctly received but the RLC data part is corrupted, the mobile station piggy-backs a PAN field with ack/nack information in a radio block for data transfer sent in (one of) the mobile station's concurrent TBF(s) with FANR activated in the uplink. + +In a downlink dual carrier configuration, the MS shall respond in the radio block indicated by the RRBP field on the same radio frequency channel as the one where the poll was received unless otherwise indicated by the network at channel assignment (this will be required in DTM e.g. when no downlink TBF exists on the same radio frequency channel as the CS timeslot). The network shall not indicate a combination of RRBP fields which would lead to the allocation to an MS of uplink radio blocks on both radio channels in any given radio block period. + +Figure 27 shows an example of message sequence for (multislot) downlink data transfer with one resource reassignment and possible RLC data block re-transmissions. + +![Sequence diagram showing downlink data transfer between MS and Network. The diagram illustrates the flow of Packet Downlink Assignments, Packet Control Acknowledgements, Data Blocks, and Packet Downlink Ack/Nack messages over time. The Network sends assignments and data blocks to the MS. The MS responds with acknowledgements and ack/nack information. The sequence includes optional steps and polling mechanisms.](4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Network + Note left of MS: (Optional) + Network->>MS: Packet Downlink Assignment + MS-->>Network: Packet Control Acknowledgement + Network->>MS: Data Block + Network->>MS: Data Block + Network->>MS: Data Block (polling) + MS-->>Network: Packet Downlink Ack/Nack + Network->>MS: Data Block + Network->>MS: Data Block + Network->>MS: Data Block + Network->>MS: Packet Downlink Assignment (polling) + MS-->>Network: Packet Control Acknowledgement + Network->>MS: Data Block + Network->>MS: Data Block + Network->>MS: Data Block (last, polling) + MS-->>Network: Packet Downlink Ack/Nack (final) + +``` + +Sequence diagram showing downlink data transfer between MS and Network. The diagram illustrates the flow of Packet Downlink Assignments, Packet Control Acknowledgements, Data Blocks, and Packet Downlink Ack/Nack messages over time. The Network sends assignments and data blocks to the MS. The MS responds with acknowledgements and ack/nack information. The sequence includes optional steps and polling mechanisms. + +Figure 27: An example of downlink data transfer + +Figure 28 shows an example of a message sequence for allocating two downlink TBFs to a mobile station that supports multiple TBF procedures (and multislot) with possible RLC data block re-transmissions. + +![Sequence diagram showing downlink data transfer between MS and Network with two TBFs.](28f2f470a7b2446ae5f525123534383c_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Network + Note left of MS: (Optional) + Network->>MS: Multiple TBF Downlink Assignment (PACCH, (P)CCCH) + MS-->>Network: Packet Control Acknowledgement (PACCH (TBF1, TBI)) + Note right of Network: Data Block (PDTCH (TBF1)) + Note right of Network: Data Block (PDTCH (TBF2)) + Note right of Network: Data Block (polling) (PDTCH (TBF1)) + Note right of Network: Data Block (PDTCH (TBF2)) + Network->>MS: Packet Downlink Ack/Nack (PACCH (TBF1)) + Note right of Network: Data Block (PDTCH (TBF1)) + Note right of Network: Data Block (polling) (PDTCH (TBF2)) + Network->>MS: Packet Downlink Ack/Nack (PACCH (TBF2)) + Note right of Network: Data Block (PDTCH (TBF1)) + Note right of Network: Data Block (PDTCH (TBF2)) + Note right of Network: . + Note right of Network: . + Note right of Network: . + Note right of Network: . + +``` + +The diagram illustrates a message sequence between a Mobile Station (MS) and a Network. It begins with the Network sending a 'Multiple TBF Downlink Assignment' message on the PACCH, (P)CCCH channel to the MS. The MS responds with an 'Optional' 'Packet Control Acknowledgement' on the PACCH (TBF1, TBI) channel. The Network then transmits a series of data blocks: 'Data Block' on PDTCH (TBF1), 'Data Block' on PDTCH (TBF2), 'Data Block (polling)' on PDTCH (TBF1), and 'Data Block' on PDTCH (TBF2). The MS sends a 'Packet Downlink Ack/Nack' on the PACCH (TBF1) channel. The Network continues with 'Data Block' on PDTCH (TBF1), 'Data Block (polling)' on PDTCH (TBF2), and another 'Packet Downlink Ack/Nack' on the PACCH (TBF2) channel. Finally, the Network sends 'Data Block' on PDTCH (TBF1) and 'Data Block' on PDTCH (TBF2). The sequence concludes with four vertical dots, indicating further messages. + +Sequence diagram showing downlink data transfer between MS and Network with two TBFs. + +Figure 28: An example of downlink data transfer with two TBFs + +##### 6.6.4.8.3 Release of the Resources + +The release of the resources is initiated by the network by terminating the downlink transfer and polling the MS for a final Packet Downlink Ack/Nack message. + +A mobile station in dual transfer mode shall abandon the packet resources when the RR connection is released. + +It is possible for the network to change the current downlink assignment by using the Packet Downlink Assignment, Packet Timeslot Reconfigure, Multiple TBF Downlink Assignment or Multiple TBF Timeslot Reconfigure message, which then has to be acknowledged by the MS in a reserved radio block on the uplink. + +The handling of TFI is steered with the same timer that runs on both the MS and the network side after the last RLC data block is sent to the MS. When it expires, the current assignment becomes invalid for the MS and TFI can be reused by the network. Further, upon the reception of the final Packet Downlink Ack/Nack from the MS, another timer is started on network side. When it expires, the current assignment becomes invalid for the MS and TFI can be reused by the network. + +##### 6.6.4.8.4 Packet Paging Notification + +The network initiates a packet transfer to a DTM MS that is in the Standby state and in dedicated mode by sending one or more packet paging notification messages on the downlink main DCCH. The MS responds to one packet paging notification message by initiating a mobile originated packet request, as described in section 6.6.4.7. This mobile originated packet transfer allows the MS to send a packet paging response to the network. The packet paging response is one or more RLC/MAC data blocks containing an arbitrary LLC frame. After the packet paging response is sent by the MS and received by the network, the mobility management state of the MS is Ready. + +The network can then assign some radio resources to the MS and perform the downlink data transfer as described in section 6.6.4.8.2. + +#### 6.6.4.9 Simultaneous Uplink and Downlink Packet Transfer + +##### 6.6.4.9.1 MS Does Not Support Multiple TBF Procedures + +During the ongoing uplink Temporary Block Flow, the MS continuously monitors one downlink PDCH for possible occurrences of Packet Downlink Assignment or Packet Timeslot Reconfigure messages on PACCH (see Figure 25). The MS is therefore reachable for downlink packet transfers that can then be conveyed simultaneously on the PDCH(s) that respect the MS multislot capability. + +If the MS wants to send packets to the network during the ongoing downlink Temporary Block Flow, it can be indicated in the acknowledgement that is sent from the MS. By doing so, no explicit Packet Channel Requests have to be sent to the network. Further, the network already has the knowledge of which PDCH(s) that particular MS is currently using so that the uplink resources can be assigned on the PDCH(s) that respect the MS multislot capability. This method may introduce an extra delay when initiating the uplink packet transfer but only for the first LLC frame in a sequence. + +In a downlink dual carrier configuration, the network shall not indicate a combination of USF and/or RRBG fields which would lead to the allocation to an MS of uplink radio blocks on both radio channels in any given radio block period. + +##### 6.6.4.9.2 MS Supports Multiple TBF Procedures + +Mobile station support of multiple TBF procedures is optional. A mobile station that supports multiple TBF procedures may operate multiple uplink and downlink TBFs concurrently. The maximum number of TBFs that a mobile station that supports multiple TBF procedures can support concurrently is not specified. Mobile station implementations are expected to ensure that the mobile station can support the number of TBFs sufficient to operate all the PDP contexts it has activated. As such, a mobile station may choose to release, modify or activate one or more PDP contexts when prioritizing the services it wants to operate concurrently. The network is not required to consider any potential complexity limitations regarding the number of concurrent TBFs when establishing an uplink or downlink TBF for a mobile station that supports multiple TBF procedures. + +When any given PDP Context is activated, it is allocated a Packet Flow Context by the network and the payload associated with the corresponding PFI will be sent using one TBF (for a unidirectional service) or one uplink and one downlink TBF (for a bidirectional service). As such, each activated PDP Context has an implicit number of TBFs required to support it. However, the total number of TBFs required to support a given set of active PDP Contexts associated with a mobile station that supports multiple TBF procedures may be reduced as a result of TBF sharing as follows: + +- Any given PDP Context that a mobile station attempts to activate for a unidirectional service may be aggregated by the SGSN so that the same PFI is associated with multiple PDP Contexts (see clause 12.6.3.5 of 3GPP TS 23.060). When this occurs a single TBF is used to deliver user plane payload associated with any of the aggregated PDP Contexts. +- Bandwidth from a TBF allocated to send user plane payload for an active PDP Context is stolen to send control plane messages (e.g. GMM or SM). + +Network support of packet flow context (PFC) procedures is indicated by the PFC\_FEATURE\_MODE parameter that is broadcast on either the BCCH or PBCCH. If the PFC\_FEATURE\_MODE bit is not present then the network does not support PFC procedures or multiple TBF procedures. If the network supports PFC procedures then a mobile station may indicate a PFI value during uplink TBF establishment. + +Network support of multiple TBF procedures is indicated using the MTBF\_CAPABILITY parameter that is broadcast on either the BCCH and PBCCH. If the network indicates it supports multiple TBF procedures then it shall also indicate + +support for PFC procedures. When the network and the mobile station both support multiple TBF procedures then the mobile station shall indicate the PFI value associated with each uplink TBF it attempts to establish + +During one or more ongoing TBFs, the mobile station continuously monitors its assigned downlink PDCHs for possible occurrences of downlink TBF allocations from the network. The network has knowledge of which uplink PDCH(s) the mobile station is already using and can therefore assign downlink PDCH(s) that respect the multislot capability of the MS. + +During one or more ongoing TBFs, a mobile station can request the establishment of one or more uplink TBFs by sending a Packet Downlink Ack/Nack or a Packet Resource Request message to the network. The network has knowledge of which downlink PDCH(s) the mobile station is already using and can therefore assign uplink PDCH(s) that respect the multislot capability of the MS. Using a Packet Downlink Ack/Nack to make an uplink TBF request may introduce an extra delay when initiating the corresponding uplink packet transfer(s) but only for the first LLC frame in a sequence. + +In a downlink dual carrier configuration, the network shall not indicate a combination of USF and/or RRBPs which would lead to the allocation to an MS of uplink radio blocks on both radio channels in any given radio block period. + +## 6.7 Abnormal cases in GPRS MS Ready State + +The RLC/MAC error causes and procedures to handle these can be found in 3GPP TS 44.018 [6], 3GPP TS 44.060 [7] and 3GPP TS 45.008 [15]. + +## 6.8 Void + +## 6.9 MBMS Data Transfer + +MBMS data, in the form of individual upper layer frames, is mapped into RLC/MAC-PTM\_DATA primitive and distributed from SGSN to the BSS representing the cells that belong to the Service Area. In the case of *A/Gb mode*, upper layer frames are LLC frames. + +The procedures for notification, user counting and addressing, channel assignment and data transfer are specified in 3GPP TS 43.246. + +# --- Annex A (informative): Bibliography + +- 1) ITU-T I.130, Method for the Characterization of Telecommunication Services Supported by an ISDN +- 2) ITU-T Q.65, Stage 2 of the Method for Characterization of the Services Supported by an ISDN +- 3) DIS 8886, OSI Data Link Service Definition +- 4) DIS 10022, OSI Physical Service Definition +- 5) ISO 10039, Medium Access Control Service Definition +- 6) ISO 4335, HDLC Procedures +- 7) ISO 7478, Multilink Procedures +- 8) ISO 7498, OSI Basic Reference Model and Layer Service Conventions + +# Annex B (informative): Multiple TBF Feature + +## B.1 General + +The multiple TBF feature has been optionally introduced for mobile stations and networks operating in A/Gb mode, this feature is described in TS 43.064 and TS 44.060, and in TS 43.055 and TS 44.018 for DTM procedures. + +A mobile station that supports multiple TBF procedures may operate multiple uplink and downlink TBFs concurrently. The maximum number of TBFs that a mobile station can support in either direction concurrently is not specified. + +In order to support multiple TBFs, both the network and the mobile station must support: + +- i) Packet flow procedures. The PFI (packet flow identifier) is used in the equivalent manner to the RB Id (radio bearer identifier in *Iu mode*) in RLC/MAC control messages +- ii) Multiple TBF assignment messages (i.e. MULTIPLE TBF UPLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT and MULTIPLE TBF TIMESLOT RECONFIGURE messages) + +There are no minimum multislot class requirements defined in relation to the support of the multiple TBF feature. + +Mobile station implementations are expected to ensure that the mobile station can support the number of TBFs sufficient to operate all the PDP contexts it has activated. As such, a mobile station may choose to release, modify or activate one or more PDP contexts when prioritising the services it wants to operate concurrently. The network is not required to consider any potential complexity limitations regarding the number of concurrent TBFs when establishing an uplink or downlink TBF for a mobile station that supports multiple TBF procedures. + +## B.2 Multiple TBF capability + +The mobile station indicates its support of multiple TBFs in the “Multiple TBF Capability” field in the *MS Radio Access Capabilities 2* Information Element which is included in the first PACKET RESOURCE REQUEST message sent to the network (e.g. in a two-phase access if multiple TBFs are requested directly from packet idle mode, or as part of the first PACKET RESOURCE REQUEST message on the PACCH if the initial TBF has been established using a one-phase access). The *MS Radio Access Capabilities 2* Information Element is also included in the GMM ATTACH REQUEST and ROUTING AREA UPDATE REQUEST message. + +The network indicates whether it supports multiple TBFs in the “Multiple TBF Capability” field in the *GPRS Cell Options* IE contained in the system broadcast information (i.e. PSI1, PSI13 and SI13). The network also includes the *GPRS Cell Options* IE in the DTM ASSIGNMENT COMMAND message and the PACKET ASSIGNMENT message during DTM procedures. + +A mobile station cannot request multiple uplink TBFs in a DTM REQUEST message, but it includes and sets a new bit called “Multiple TBF Capability” in the *Channel Request Description 2* information element in that message. Once it has moved into dual transfer mode through the establishment of a CS channel and a single TBF on a PS channel it may request multiple TBFs using the PACKET RESOURCE REQUEST message on the PACCH of the PDTCH in the same way as for packet transfer mode. + +The network may assign multiple downlink TBFs to a mobile station which is already in dual transfer mode using the MULTIPLE TBF DOWNLINK ASSIGNMENT or MULTIPLE TBF TIMESLOT RECONFIGURE message on the PACCH of an existing TBF. For the case where there are no ongoing TBFs for a given MS, the network determines the mobile station’s multiple TBF capabilities from the *MS RAC* IE which is provided by the SGSN with the downlink LLC PDUs. + +The network may reconfigure the mobile station’s TBFs during a CS channel reconfiguration which does not involve a cell change. On CS handover, all PS resources are dropped and have to be re-established in the new cell. + +## B.3 Multiple TBF procedures + +### B.3.1 Data multiplexing options + +#### B.3.1.1 Single TBF per upper layer flow + +If the mobile station has user data to send for two or more PFCs, it requests one uplink TBF for each PFC. In the downlink, the network may assign a separate TBF to the mobile station for each PFC for which there is user data to send or it may decide to perform downlink (DL) TBF sharing, see B.3.1.2. + +If a single TBF per upper layer flow is established, the network assigns one RLC instance and one TBF for user data from one PFC. The QoS parameter settings for the TBF relate directly to the QoS requirements for the PFC. + +#### B.3.1.2 DL TBF sharing + +In the downlink the network may decide to perform DL TBF sharing for PFCs with similar QoS requirements which do not have strict delay requirements (i.e. background and interactive services). Multiplexing of user data from these different PFCs onto a single TBF is done on an LLC PDU basis and the PFC to which the user data belongs is only identifiable at the LLC layer using SAPI (i.e. the SGSN indicates a PFI associated with one user data flow when sending an LLC PDU associated with another user data flow to the BSS on the Gb interface). As a single RLC instance is used for all LLC PDUs delivered on that TBF, the different PFCs must use the same RLC mode. + +#### B.3.1.3 Explicit UL TBF switching + +The network allocates the new PFC ownership of the ongoing uplink TBF on which the PACKET RESOURCE REQUEST message was sent using the PACKET UPLINK ASSIGNMENT message. + +### B.3.2 RLC/MAC Signalling + +In the single TBF configuration, RLC/MAC control messages relating to a particular TBF are sent to the network on the PACCH of a timeslot on which the TFI of that TBF is valid. For example, the (EGPRS) PACKET DOWNLINK ACK/NACK message is sent on the PACCH/U of an uplink timeslot on which the downlink TFI is valid. + +The network may choose not to assign to a mobile station with multiple active TBFs any resources on any of the uplink timeslots corresponding to the downlink timeslots on which the downlink TFI is valid (e.g. when an MS has been assigned more downlink timeslots than uplink timeslots). In this case the network must assign an “uplink control timeslot” to the mobile station for those downlink TBFs assigned one or more timeslots for which no corresponding uplink timeslot has been assigned. The mobile station then sends the RLC/MAC control message on the assigned uplink control timeslot (where the downlink TFI is not a unique identifier) and adds the downlink timeslot number into the message in order for the network to identify the relevant TBF. + +If the mobile station receives more than one assignment message, then the mobile station uses the uplink control timeslot given in the most recently received assignment message. It is the responsibility of the network to assign resources to a mobile station without violating its multislot capabilities. + +Note that a “downlink control timeslot” concept is not needed, as for the case where an MS has been assigned more uplink timeslots than downlink timeslots each uplink TBF will always have at least one uplink timeslot for which there is a corresponding downlink timeslot. This is possible through the use of extended dynamic allocation where MS permission to transmit on a given uplink timeslot may be provided on a downlink timeslot that does not directly correspond to that uplink timeslot. + +### B.3.3 TBF establishment + +#### B.3.3.1 TFI allocation + +A TBF is assigned one TFI value which is valid on all of the timeslots on which data for this TBF may be sent. The network assigns the TFI value and all the valid timeslots for the TBF in the assignment message. A multislot mobile may therefore have some TBFs with TFI values which are valid for fewer than all of the timeslots assigned to the mobile station. These timeslot restrictions are specified by the network at the TBF assignment. Similarly the network will only assign a USF value to an uplink TBF for those timeslots on which data for this TBF may be sent. + +The result of this is that although no TFI values are wasted, the uplink control timeslot concept is needed to allow RLC/MAC control messages relating to a downlink TBF to be sent on an uplink timeslot where this TFI is not valid, see B.3.2. + +Data for one PFC is assigned a single TBF at the TBF establishment, thus creating a one-to-one relationship between PFI and TFI. + +#### B.3.3.2 Single TBF request / establishment + +A mobile station in packet idle mode supporting multiple TBF procedures may request a single uplink TBF according to existing procedures, using either one-phase or two-phase access. The mobile station must include the PFI to be associated with each TBF. The network may respond with either a PACKET UPLINK ASSIGNMENT or a PACKET TIMESLOT RECONFIGURE message (see section 7 of TS 44.060). + +The network may send a PACKET DOWNLINK ASSIGNMENT message to a mobile station in packet idle mode to assign a downlink TBF to the mobile station. + +The network may send a PACKET UPLINK/DOWNLINK ASSIGNMENT or a PACKET TIMESLOT RECONFIGURE message to a mobile station in packet transfer mode. All ongoing uplink (respectively downlink) TBFs which are not included in the PACKET UPLINK ASSIGNMENT (respectively PACKET DOWNLINK ASSIGNMENT) message are released and the explicitly addressed TBFs are either reconfigured (if already active) or established (if not active beforehand). + +When assigning a single uplink TBF and/or a single downlink TBF in a PACKET UPLINK ASSIGNMENT, PACKET DOWNLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message to a mobile station which supports multiple TBF procedures, the network must indicate a PFI to be associated with each TBF. This ensures that if the mobile station requests additional TBFs, the PFI can be used as a flow identifier in accordance with multiple TBF procedures. + +#### B.3.3.3 Multiple TBF establishment / reconfiguration + +##### B.3.3.3.1 Multiple uplink TBF request / establishment + +The mobile station in packet idle mode may request multiple TBFs by performing a two-phase access according to existing procedures (on CCCH or PCCCH) and including the multiple TBF request information in the *Extended Channel Request Description* IE of the PACKET RESOURCE REQUEST message. + +The mobile station may request multiple TBFs from packet transfer mode or dual transfer mode by including the multiple TBF request information in the *Extended Channel Request Description* IE of the PACKET RESOURCE REQUEST message. + +In response to a PACKET RESOURCE REQUEST message requesting multiple uplink TBFs, the network may send one of the following messages: + +- PACKET ACCESS REJECT message rejecting the whole request (the mobile station may retry after T3172 expires). +- PACKET UPLINK ASSIGNMENT message assigning an uplink TBF to the PFC in the multiple TBF request having the highest priority (See note 1). On reception of this message the mobile station shall release all ongoing uplink TBFs. The mobile station cannot have more than one uplink TBF ongoing as a result of receiving this message. +- PACKET UPLINK ASSIGNMENT message indicating the PFI of the PFC using an ongoing uplink TBF to indicate that the corresponding ongoing uplink TBF is being reconfigured. The mobile station interprets this as not being the response to the multiple TBF resource request (See note 2). However any other previously assigned uplink TBFs are implicitly released upon reception of the PUA message. The mobile station cannot have more than one uplink TBF ongoing as a result of receiving this message. +- PACKET TIMESLOT RECONFIGURE message to indicate that an ongoing uplink TBF is being reconfigured and that also an ongoing downlink TBF is being reconfigured. The mobile station interprets this as not being the response to the multiple TBF resource request (See note 2). The mobile station cannot have more than one uplink and one downlink TBF ongoing as a result of receiving this message. + +*Note 1:* If the PFI is one of the PFIs included in the multiple TBF request the mobile station interprets the PACKET UPLINK ASSIGNMENT as the response to the multiple TBF resource request and therefore an MTUA/MTTR response is not going to be sent (See explicit TBF sharing). + +*Note 2:* If the PFI addresses a PFC using an ongoing TBF, this indicates to the mobile station that the mTBF request is still outstanding, so it should wait for a MTUA/MTTR response. + +Alternatively, the network may send one or more of the following messages (according to multiple TBF procedures): + +- PACKET ACCESS REJECT message rejecting part of the multiple TBF request indicated by a list of PFIs (the mobile station may retry for the rejected TBFs after T3172 expires). In the case of a partial rejection the network assigns resources for one or more of the TBFs requested by the mobile station, as a partial reject of a resource request is not treated as an abnormal case. +- MULTIPLE TBF UPLINK ASSIGNMENT message to assign one or more uplink TBFs. +- MULTIPLE TBF TIMESLOT RECONFIGURE message to reassign the ongoing resources at the same time as assigning new resources. + +##### B.3.3.3.2 Multiple downlink TBF establishment + +The network cannot assign multiple downlink TBFs to the mobile station straight from packet idle mode, it must first assign a single downlink TBF using the (P)CCCH procedures and then send the MULTIPLE TBF DOWNLINK ASSIGNMENT or MULTIPLE TBF TIMESLOT RECONFIGURE message to the mobile station on the PACCH. + +If the mobile station already has one or more uplink TBFs, the network may assign one or more downlink TBFs by sending a MULTIPLE TBF DOWNLINK ASSIGNMENT or MULTIPLE TBF TIMESLOT RECONFIGURE message to the mobile station on the PACCH. + +If the mobile station has more than one uplink or downlink TBF ongoing and receives a PACKET TIMESLOT RECONFIGURE message, it shall only keep the uplink TBF and downlink TBF specified in that message. The mobile station cannot have more than one uplink and one downlink TBF ongoing as a result of receiving this message. + +On reception of a PACKET DOWNLINK ASSIGNMENT message, it shall release all ongoing downlink TBFs. The mobile station cannot have more than one downlink TBF ongoing as a result of receiving this message. + +##### B.3.3.3.3 Usage of multiple TBF assignment messages + +The MULTIPLE TBF UPLINK/DOWNLINK ASSIGNMENT messages do not have any impact on ongoing TBFs which are not explicitly addressed in the message. However the MULTIPLE TBF TIMESLOT RECONFIGURE message is used to implicitly release all ongoing TBFs which are not explicitly addressed in the message. + +The MULTIPLE TBF TIMESLOT RECONFIGURE message should only be used by the network if more than one TBF is currently assigned or if the resulting configuration after reception of the message consists of more than one TBF in one direction. Even if these rules are violated the mobile station should always act on the message. + +**Table 1 – Message Usage Rules** + +| Assignment messages used | | Number of downlink TBFs (after assignment) | | | +|---------------------------------------------|-----------|--------------------------------------------|--------------------|--------------------| +| | | 0 | 1 | 2 or more | +| Number of uplink TBFs
(after assignment) | 0 | - | PDA / MTTR (1) | MTDA / MTTR (3) | +| | 1 | PUA / MTTR (1) | PTR / MTTR (1) | MTUA / MTDA / MTTR | +| | 2 or more | MTUA / MTTR (2) | MTUA / MTDA / MTTR | MTUA / MTDA / MTTR | + +- (1) If the mobile station had multiple active TBFs prior to the assignment. +- (2) If the mobile station had downlink active TBFs prior to the assignment. +- (3) If the mobile station had uplink active TBFs prior to the assignment. + +Example 1: In the case of the MTTR, this message is used to reconfigure a mobile station which has more than one TBF in either direction prior to the reconfiguration. Thus it may be that the network reassigns only a single TBF in either or each direction as a result, but the MTTR message still is used (as this indicates to the mobile station that all other TBFs are to be released). + +Example 2: If a mobile station has multiple uplink TBFs, but no downlink TBFs, the network sends an MTDA message to the mobile station even if it is only for a single DL TBF assignment. + +## B.4 RLC/MAC Timers + +### B.4.1 TBF timers + +On the mobile side the timers T3164, T3168, T3172, T3180, T3182, T3184, T3190, T3192 and T3194 are related to a TBF instance. The new mobile station timer T3188 is not related to a TBF instance, as it supervises the contention resolution (see B.4.2). + +On the network side the timers T3169, T3191, T3193 and T3195 are related to one TBF instance, as the action on expiry of these timers is the release of the TBF resources. + +### B.4.2 Contention resolution timer + +T3188 has been introduced to control the time within which contention resolution should be completed. It is started in the mobile station when a PACKET RESOURCE REQUEST message requesting two or more uplink TBFs is sent to the network in the second phase of a two-phase access requesting multiple TBFs and is stopped upon receipt of the MULTIPLE TBF UPLINK ASSIGNMENT message or a PACKET UPLINK ASSIGNMENT message. + +T3188 runs in parallel to the T3168 timers which are started for each resource request, and may have the same value as T3168. There is only one instance of this timer in the mobile station, and the expiry of this timer indicates the failure of the mobile station's access rather than of an individual TBF establishment attempt. + +## B.5 CSN.1 coding of multiple TBF messages + +### B.5.1 MULTIPLE TBF UPLINK ASSIGNMENT message + +Ongoing TBFs that are not explicitly addressed in this message are left unchanged. In the main body of the MULTIPLE TBF UPLINK ASSIGNMENT message is the following: + +{ 0 | 1 < Uplink TBF Assignment : < Uplink Assignment struct > > } + +``` +< Uplink Assignment struct > ::= + < EXTENDED_DYNAMIC_ALLOCATION : bit (1) > + { 0 | 1 < Uplink Control Timeslot : bit (3) > } + { 0 | 1 < P0 : bit (4) > + < PR_MODE : bit(1) > } + { 0 | 1 < TBF Starting Time : < Starting Frame Number Description IE > > } + { 0 | 1 < Global Timeslot description : < Timeslot description struct > > + { 1 < Uplink TBF Assignment : < Uplink TBF Assignment struct > > } ** 0 }; +``` + +This struct gives all the information that is only given once per assignment message, including: + +- whether extended dynamic allocation is used (if it is, it will be used over the set of timeslots indicated in the Timeslot Description), +- whether an Uplink Control Timeslot has been assigned to the mobile station, +- whether the assignments contained in this message are not immediately valid (TBF starting time delays the validity of the assignments until this time) and +- which uplink timeslots which have been assigned to the mobile station in this message. Note that this is a bit field (ignoring USF assignment) which indicates all of the uplink timeslots assigned resources in this message (e.g. 00111000 means that at least one TBF is assigned to each of timeslots 2, 3, 4). It is NOT required for all TBFs to be valid on ALL these timeslots (see the TBF Timeslot Allocation field). + +``` + +< Uplink TBF Assignment struct > ::= +{ 0 < RB Id : bit (5) > | 1 < PFI : bit (7) > } +< TFI Assignment : bit (5) > +{ 0 | 1 < CHANNEL_CODING_COMMAND : bit (2) > } +{ 0 | 1 < EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE > > } +{ 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } +{ 0 + | 1 < TBF_TIMESLOT_ALLOCATION : bit (N) > } +{ 0 + | 1 < USF_ALLOCATION : bit (3) > + | 1 < USF_ALLOCATION : bit (3) > + { 0 | 1 < USF_ALLOCATION : bit (3) > } * (M-1) } ; + +``` + +*-- Recursive for multiple TBFs* +*-- The timeslots assigned to the TBF are all the timeslots assigned* +*-- in the Global Timeslot description* +*-- The timeslots assigned to the TBF are a subset of all the* +*-- timeslots assigned in the Global Timeslot description. Where* +*-- N is the amount of timeslots assigned to the MS in the Global* +*-- Timeslot description* +*-- The same USF is valid on all timeslots assigned to the TBF* +*-- Different USF(s) assigned* +*-- USF assignment on the lowest numbered timeslot* +*-- assigned to the TBF* +*-- USFs on subsequent timeslots assigned to the TBF:* +*-- A '0' (respectively a '1' followed by a USF value)* +*-- means same (respectively different) USF value as the* +*-- USF on the next lower numbered timeslot assigned to* +*-- the TBF. Where M is the amount of timeslots assigned* +*-- to the TBF in the TBF\_TIMESLOT\_ALLOCATION if* +*-- present, else in the Global Timeslot description* + +The length of the TBF\_TIMESLOT\_ALLOCATION field is equal to the number of timeslots marked as being assigned to the mobile station in the Global Timeslot description struct in the Uplink Assignment struct. It allows multiple TBFs to have different timeslot allocations, if it is not included then all TBFs assigned in this message share the timeslot allocation as described in the Global Timeslot description. + +This coding allows the network to assign different parameters (timeslots, USFs) for each TBF in the message but is optimized for the cases where: + +- The TBF is assigned on all timeslots in the Global Timeslot Description; or +- The TBF is assigned on a subset of the timeslots indicated in the Global Timeslot Description; and +- the same USF is used on all timeslots of the TBF; or +- there are different USFs for the TBF, but the same USF is used on consecutive timeslots of the TBF. + +### B.5.2 MULTIPLE TBF DOWNLINK ASSIGNMENT message + +Ongoing TBFs that are not explicitly addressed in this message are left unchanged. In the main body of the MULTIPLE TBF DOWNLINK ASSIGNMENT message is the following: + +``` +{ 1 < Multiple Downlink TBF Assignment : < Multiple Downlink TBF Assignment struct > > } ** 0 +``` + +which indicates that the following struct may be repeated. + +``` + +< Multiple Downlink TBF Assignment struct > ::= +< TIMESLOT_ALLOCATION : bit (8) > +{ 1 < Downlink TBF assignment : < Downlink TBF assignment struct > > } ** 0 ; + +``` + +This struct is repeated for each set of TBFs that share a common downlink timeslot allocation. For example, if the mobile station is assigned two downlink TBFs where each operates on timeslots 4 and 5, plus another downlink TBF that is only assigned on timeslot 5, this would require two instances of the Multiple Downlink TBF Assignment struct in this message. + +This approach is used because it is more likely for different downlink TBFs to share a common timeslot allocation than it is for uplink TBFs. Hence this coding is optimised for the case where all downlink TBFs allocated to a given mobile station are valid on all timeslots (leaving the network to perform the scheduling as necessary). + +``` + +< Downlink TBF assignment struct > ::= = +{ 0 < RB Id : bit (5) > +| 1 < PFI : bit (7) > < RLC_mode : bit (1) > } +< TFI Assignment : bit (5) > +< CONTROL_ACK : bit (1) > +{ 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE >> } +{ 0 | 1 < HFN_LSB : bit (1) > } ; -- HFN_LSB field used in Iu mode only + +``` + +This struct is repeated for each TBF that is assigned resources in the message. Each of these repeats may be associated with the same instance of the “Multiple Downlink TBF Assignment struct” (i.e. when multiple downlink TBFs share the same downlink timeslot allocation) or with different instances of the “Multiple Downlink TBF Assignment struct” (i.e. when the downlink TBFs do not share the same downlink timeslot allocation). + +### B.5.3 MULTIPLE TBF TIMESLOT RECONFIGURE message + +The MULTIPLE TBF TIMESLOT RECONFIGURE message implicitly releases any TBFs which are not described in the message. It may be used to assign new resources as well as reconfigure existing resources and is needed when a mobile station is to be reconfigured onto a different carrier and all resources must be moved. + +The MULTIPLE TBF TIMESLOT RECONFIGURE message is a combination of all the fields given in the MULTIPLE TBF DOWNLINK ASSIGNMENT and MULTIPLE TBF UPLINK ASSIGNMENT messages except for the uplink control timeslot field, which may be defined per TBF according to the coding, but this is only used for *Iu mode*. Hence the coding of this message in A/Gb mode should ensure that the uplink control timeslot is defined only once per message. + +The length of this message has been shown to fit into two radio blocks in the majority of scenarios, assuming up to 4 TBFs are assigned in each direction. + +# Annex C (informative): Change history + +| SPEC | SMG# | CR | PHA | VERS | NEW_VER | SUBJECT | +|-------|--------|--------|-----|-------|---------|----------------------------------------------------------------------------------| +| 03.64 | s22 | NEW | 2+ | 2.1.1 | 5.0.0 | GSM 03.64 GPRS Stage 2 Radio | +| 03.64 | s23 | A022 | R97 | 5.0.0 | 5.1.0 | Unacknowledged mode of RLC/MAC operation | +| 03.64 | s23 | A023 | R97 | 5.0.0 | 5.1.0 | Improved RLC Service Primitives | +| 03.64 | s23 | A024 | R97 | 5.0.0 | 5.1.0 | Enhancements to dynamic allocation | +| 03.64 | s23 | A025 | R97 | 5.0.0 | 5.1.0 | Clarifications to DRX | +| 03.64 | s23 | A026 | R97 | 5.0.0 | 5.1.0 | Optimisation for network control cell reselection | +| 03.64 | s23 | A027 | R97 | 5.0.0 | 5.1.0 | Abnormal Cases in GPRS MS Ready State: Leaky Bucket Procedure | +| 03.64 | s23 | A029 | R97 | 5.0.0 | 5.1.0 | Multiframe structure (details) (revision of SMG2 GPRS 301/97) | +| 03.64 | s23 | A030 | R97 | 5.0.0 | 5.1.0 | Abnormal Cases in GPRS MS Ready State | +| 03.64 | s23 | A031 | R97 | 5.0.0 | 5.1.0 | Cell Re-Selection in GPRS | +| 03.64 | s23 | A032 | R97 | 5.0.0 | 5.1.0 | Definition of PACCH | +| 03.64 | s23 | A033 | R97 | 5.0.0 | 5.1.0 | Clarifications on Timing advance procedure | +| 03.64 | s23 | A035 | R97 | 5.0.0 | 5.1.0 | Bit order for USF coding in GPRS | +| 03.64 | s23 | A036 | R97 | 5.0.0 | 5.1.0 | PTM-M | +| 03.64 | s23 | A037 | R97 | 5.0.0 | 5.1.0 | Contention resolution | +| 03.64 | s23 | A039 | R97 | 5.0.0 | 5.1.0 | Deleting parameter XHYST | +| 03.64 | s24 | A031 | R97 | 5.1.0 | 5.2.0 | Clarification on the use of hysteresis for cell re-selection | +| 03.64 | s25 | A043 | R97 | 5.2.0 | 6.0.0 | Clarification of the use of TAI | +| 03.64 | s25 | A049 | R97 | 5.2.0 | 6.0.0 | USF granularity for dynamic allocation | +| 03.64 | s26 | | R97 | 6.0.0 | 6.0.1 | Editorial changes for Publication | +| 03.64 | s27 | A050 | R97 | 6.0.1 | 6.1.0 | Changes on all chapters to align the spec. with other GPRS specifications. | +| 03.64 | s27 | A044 | R97 | 6.0.1 | 6.1.0 | Clarification on PACCH allocation for fixed assignment | +| 03.64 | s28 | A052 | R97 | 6.1.0 | 6.2.0 | PBCCH scheduling and editorial corrections | +| 03.64 | s28 | A051 | R97 | 6.1.0 | 6.2.0 | Interference measurements on network control | +| 03.64 | s28 | A053 | R97 | 6.1.0 | 6.2.0 | 51-multiframe PBCCH | +| 03.64 | s29 | A055 | R97 | 6.2.0 | 6.3.0 | Miscellaneous corrections | +| 03.64 | s29 | A056 | R97 | 6.2.0 | 6.3.0 | Clarification of polling response | +| 03.64 | s29 | A057 | R97 | 6.2.0 | 6.3.0 | Correction to 1 phase access contention resolution | +| 03.64 | s29 | A054 | R99 | 6.2.0 | 8.0.0 | Introduction of Enhanced GPRS (EGPRS) | +| 03.64 | s30 | A066 | 2 | 8.0.0 | 8.1.0 | MT packet transfer | +| 03.64 | s30 | A058 | | 8.0.0 | 8.1.0 | EGPRS fine tuning | +| 03.64 | s30 | A059 | 1 | 8.0.0 | 8.1.0 | EDGE Compact Cell Reselection | +| 03.64 | s30 | A060 | 1 | 8.0.0 | 8.1.0 | EDGE Compact logical channels | +| 03.64 | s30bis | A067 | | 8.1.0 | 8.2.0 | Correction for EGPRS | +| 03.64 | s30bis | A068 | | 8.1.0 | 8.2.0 | Introduction of Incremental Redundancy between different coding schemes in EGPRS | +| 03.64 | s31 | A069 | | 8.2.0 | 8.3.0 | GPRS & SMS-CB interworking | +| 03.64 | s31bis | A070 | R99 | 8.3.0 | 8.4.0 | 8-PSK support in UL | +| 03.64 | s32 | A072r2 | R99 | 8.4.0 | 8.5.0 | DTM: Stage 2 Description | +| | | | | | | September 2000 TSG-GERAN | + +| | | | | | | | +|-----------------|-----|------|---|-------|-------|---------------------------------------------------------------------------------| +| 03.64 | G01 | A073 | 1 | 8.5.0 | 8.6.0 | CR 03.64-A073 rev 1 DTM (R99) | +| 03.64 | G01 | A074 | | 8.5.0 | 8.6.0 | CR 03.64-A074 DTM+EGPRS (R99) | +| 03.64 | G01 | A075 | 1 | 8.5.0 | 8.6.0 | CR 03.64-A075 rev 1 DTM: alignments (R99) | +| 03.64 | G03 | A077 | | 8.6.0 | 8.7.0 | Removal of Anonymous Access | +| 03.64 | G03 | A078 | 1 | 8.6.0 | 8.7.0 | Correction to the ordering of E/FBI bits | +| 03.64
43.064 | G03 | A076 | 4 | 8.7.0 | 4.0.0 | Introduction of Network Assisted Cell Change feature in the stage 2 description | + + + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-----|-----------------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2001-04 | 04 | GP-010962 | 001 | | Modulation based multislot class | 4.0.0 | 4.1.0 | +| 2001-04 | 04 | GP-010951 | 002 | | Applicability of GPRS requirements to EGPRS | 4.0.0 | 4.1.0 | +| 2001-11 | 07 | GP-012506 | 004 | | Coding rate of MCS3 | 4.1.0 | 4.2.0 | +| 2001-11 | 07 | GP-012525 | 005 | | Clarification of EGPRS MS USF decoding | 4.1.0 | 4.2.0 | +| 2002-02 | 08 | GP-020427 | 006 | 1 | Network requirements for MS synchronisation | 4.2.0 | 4.3.0 | +| 2002-04 | 09 | GP-020654 | 007 | | Removal of Fixed Allocation | 4.3.0 | 5.0.0 | +| 2003-04 | 14 | GP-030982 | 009 | 1 | Padding for MCS-8 retransmissions | 5.0.0 | 5.1.0 | +| 2003-05 | | | | | Make figures 20 & 25 legible again. | 5.1.0 | 5.1.1 | +| 2003-06 | 15 | GP-031382 | 014 | | Editorial correction of references | 5.1.1 | 6.0.0 | +| 2003-08 | 16 | GP-031945 | 011 | 1 | Removal of the close-ended TBF feature | 6.0.0 | 6.1.0 | +| 2003-08 | 16 | GP-032277 | 016 | 4 | Multiple TBFs Stage 2 | 6.0.0 | 6.1.0 | +| 2004-04 | 19 | GP-041194 | 020 | 2 | Change of DTM core capability | 6.1.0 | 6.2.0 | +| 2004-04 | 19 | GP-040815 | 021 | | Removal of GPRS Extended Measurement reporting | 6.1.0 | 6.2.0 | +| 2004-04 | 19 | GP-040817 | 022 | | Removal of GPRS Idle Interference Measurements | 6.1.0 | 6.2.0 | +| 2004-06 | 20 | GP-041489 | 023 | | Addition of DTM enhancements | 6.2.0 | 6.3.0 | +| 2004-08 | 21 | GP-042016 | 024 | | Data rates for GPRS | 6.3.0 | 6.4.0 | +| 2004-11 | 22 | GP-042662 | 017 | 3 | Annex on multiple TBF procedures | 6.4.0 | 6.5.0 | +| 2004-11 | 22 | GP-042364 | 025 | | MS behaviour in DTM resource reallocation during uplink TBF establishment | 6.4.0 | 6.5.0 | +| 2004-11 | 22 | GP-042882 | 026 | 2 | Removal of PTM-M | 6.4.0 | 6.5.0 | +| 2004-11 | 22 | GP-042885 | 027 | 2 | Introduction of MBMS | 6.4.0 | 6.5.0 | +| 2005-04 | 24 | GP-051131 | 029 | 2 | Extension of DTM to high multislot classes | 6.5.0 | 6.6.0 | +| 2005-06 | 25 | GP-051782 | 030 | 2 | BSS controlled RLC mode selection | 6.6.0 | 6.7.0 | +| 2005-09 | 26 | GP-052316 | 031 | 1 | GPRS stage 2 alignment with stage 3 for 2 phase access procedure | 6.7.0 | 6.8.0 | +| 2005-09 | 26 | GP-052237 | 032 | 1 | Correction to Rules for Monitoring USF in Extended Dynamic Allocation | 6.7.0 | 6.8.0 | +| 2005-11 | 27 | GP-052844 | 0033 | 1 | MBMS transfer mode | 6.8.0 | 6.9.0 | +| 2006-01 | 28 | GP-060204 | 0035 | | Correction to the introduction of MBMS transfer mode | 6.9.0 | 6.10.0 | +| 2006-04 | 29 | GP-060838 | 0036 | 1 | Editorial correction | 6.10.0 | 7.0.0 | +| 2006-06 | 30 | GP-061474 | 0038 | 3 | Introduction of Downlink Dual Carrier | 7.0.0 | 7.1.0 | +| 2006-06 | 30 | GP-061513 | 0040 | 4 | C value calculation in case there is a transition of the mode | 7.0.0 | 7.1.0 | +| 2006-06 | 30 | GP-061439 | 0041 | 1 | Correction of terminology: "allocation" vs. "assignment" | 7.0.0 | 7.1.0 | +| 2006-06 | 30 | GP-061440 | 0042 | 1 | Corrections to PACCH description | 7.0.0 | 7.1.0 | +| 2006-09 | 31 | GP-061925 | 0043 | 4 | Measurement reporting and allocation procedures for downlink dual carrier | 7.1.0 | 7.2.0 | +| 2006-09 | 31 | GP-061759 | 0045 | 1 | Dual downlink carrier multislot capabilities | 7.1.0 | 7.2.0 | +| 2006-09 | 31 | GP-061920 | 0046 | 1 | Downlink dual carrier DTM support | 7.1.0 | 7.2.0 | +| 2006-11 | 32 | GP-062483 | 0044 | 5 | Introduction of Reduced TTI | 7.2.0 | 7.3.0 | +| 2006-11 | 32 | GP-062451 | 0047 | 2 | Dual downlink carrier multislot class support for DTM | 7.2.0 | 7.3.0 | +| 2006-11 | 32 | GP-062468 | 0049 | 2 | Introduction RLC non-persistent mode | 7.2.0 | 7.3.0 | +| 2007-02 | 33 | GP-070467 | 0048 | 2 | Corrections and clarifications for downlink dual carrier | 7.3.0 | 7.4.0 | +| 2007-02 | 33 | GP-070192 | 0050 | | Clarification of release of TBFs on receipt of assignment messages | 7.3.0 | 7.4.0 | +| 2007-05 | 34 | GP-071047 | 0051 | 5 | Introduction of Fast Ack/Nack Reporting | 7.4.0 | 7.5.0 | +| 2007-05 | 34 | GP-070712 | 0052 | | Derivation of Channel Quality Report in a Dual carrier Configuration | 7.4.0 | 7.5.0 | +| 2007-05 | 34 | GP-070986 | 0053 | 1 | Correction to the RTTI description | 7.4.0 | 7.5.0 | +| 2007-08 | 35 | GP-071550 | 0054 | 2 | Introduction of RED HOT and HUGE | 7.5.0 | 7.6.0 | +| 2007-08 | 35 | GP-071436 | 0055 | 1 | RLC/MAC control messages for Latency Reduction | 7.5.0 | 7.6.0 | +| 2007-08 | 35 | GP-071530 | 0056 | 4 | Corrections for Latency Reduction | 7.5.0 | 7.6.0 | +| 2007-11 | 36 | GP-071976 | 0057 | 2 | Removal of RL TBF mode in FANR procedures | 7.6.0 | 7.7.0 | +| 2007-11 | 36 | GP-071734 | 0058 | | Introduction of RED HOT and HUGE | 7.6.0 | 7.7.0 | +| 2008-02 | 37 | GP-080366 | 0060 | 2 | Differentiate CS-1 and MCS-0 by stealing flags in RTTI configuration with RTTI USF mode | 7.7.0 | 7.8.0 | +| 2008-02 | 37 | GP-080361 | 0061 | 1 | Clarification on the modulation and coding schemes used for EGPRS2 | 7.7.0 | 7.8.0 | +| 2008-02 | 37 | GP-080342 | 0063 | 1 | Correcting the use of MCSs for RLC/MAC block for control message transfer | 7.7.0 | 7.8.0 | +| 2008-02 | 37 | GP-080337 | 0065 | 1 | Clarifications to FANR | 7.7.0 | 7.8.0 | +| 2008-05 | 38 | GP-080796 | 0066 | 1 | Clarification on USF mode for LATRED | 7.8.0 | 7.9.0 | + +| | | | | | | | | +|---------|----|------------|------|---|------------------------------------------------------------------------------------------------------------------------------------|--------|--------| +| 2008-05 | 38 | GP-080781 | 0069 | 1 | Correction to EGPRS2 | 7.8.0 | 7.9.0 | +| 2008-05 | 38 | GP-080819 | 0070 | 1 | Reduced Latency terminology alignments | 7.8.0 | 7.9.0 | +| 2008-05 | 38 | GP-080948 | 0071 | 4 | Modifications of the EGPRS2-A and EGPRS2-B Downlink Modulation and Coding Families in Support of Improved USF and PAN Multiplexing | 7.8.0 | 7.9.0 | +| 2008-08 | 39 | GP-081374 | 0059 | 4 | Channel Quality Measurement in RTTI configuration | 7.9.0 | 7.10.0 | +| 2008-08 | 39 | GP-081428 | 0072 | 2 | Clarifying FANR behavior for aligning with stage 3 | 7.9.0 | 7.10.0 | +| 2008-11 | 40 | GP-08 1463 | 0073 | | Corrections linked to USF decoding in case of GPRS, EGPRS and EGPRS2 multiplexing | 7.10.0 | 7.11.0 | +| 2008-11 | 40 | GP-08 1754 | 0074 | 1 | Symbol rate correction to DBS-5-6 | 7.10.0 | 7.11.0 | +| 2008-12 | 40 | | | | Version for Release 8 | 7.11.0 | 8.0.0 | +| 2009-02 | 41 | GP-090420 | 0076 | 1 | Corrections to EGPRS2 modulation and coding schemes usage and description | 8.0.0 | 8.1.0 | +| 2009-05 | 42 | GP-090957 | 0078 | 1 | Correction of UBS coded bit sizes | 8.1.0 | 8.2.0 | +| 2009-09 | 43 | GP-091690 | 0080 | 1 | Removal of PNCH and CPNCH channels | 8.2.0 | 8.3.0 | +| 2009-11 | 44 | GP-092346 | 0083 | 1 | Removal of mandatory support for P-channels by mobile stations in A/Gb mode | 8.3.0 | 9.0.0 | +| 2010-09 | 47 | GP-101449 | 0084 | | Exclusive allocation support | 9.0.0 | 10.0.0 | +| 2012-09 | 55 | | | | Version for Release 11 | 10.0.0 | 11.0.0 | \ No newline at end of file diff --git a/marked/Rel-11/43_series/43068/030c758fd425016b03290c8f11bef69d_img.jpg b/marked/Rel-11/43_series/43068/030c758fd425016b03290c8f11bef69d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c20d048e2167cdc65628d895f51a976b9a8ad9b3 --- /dev/null +++ b/marked/Rel-11/43_series/43068/030c758fd425016b03290c8f11bef69d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8d30d2f9996f21757bf3468fc771f95e25e4671bf224f1e9070fa196eee7a1f +size 49049 diff --git a/marked/Rel-11/43_series/43068/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg b/marked/Rel-11/43_series/43068/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ae656e78145afe97c64dcf1ea57f0cca3593b09 --- /dev/null +++ b/marked/Rel-11/43_series/43068/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f4f3201f9db9360eaf7a062fd5acbc7afcace8ce7df916ce5d87e2c51a7fcb9 +size 74262 diff --git a/marked/Rel-11/43_series/43068/04cfca33e3fc26513abe649d7474f733_img.jpg b/marked/Rel-11/43_series/43068/04cfca33e3fc26513abe649d7474f733_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56b148b320fbb9c1e0d7a5d153f69c9361f6df9c --- /dev/null +++ b/marked/Rel-11/43_series/43068/04cfca33e3fc26513abe649d7474f733_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46758c41dc49b62681fc904408e06bd765fd891a4cca97dd9bfd5dd6eba5e0b4 +size 49377 diff --git a/marked/Rel-11/43_series/43068/07b17a620c75522d53916a11e12d1bff_img.jpg b/marked/Rel-11/43_series/43068/07b17a620c75522d53916a11e12d1bff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75bb7bf780bcd3373625ac1bcaad8c0e59aeb84a --- /dev/null +++ b/marked/Rel-11/43_series/43068/07b17a620c75522d53916a11e12d1bff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af065554bcbe61bc2c397f33a71a2c8ea205fa7f42bc5852887d6fc7a481098d +size 113397 diff --git a/marked/Rel-11/43_series/43068/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Rel-11/43_series/43068/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67e3d54b2b8801b238b8c5d8b17c29a4b2ed120b --- /dev/null +++ b/marked/Rel-11/43_series/43068/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7825c34523bdb9958521d0241f653a49104435918ed6677f77e9e1d047d87e97 +size 82644 diff --git a/marked/Rel-11/43_series/43068/0b452c5334567cbdc22ee9817e1246f5_img.jpg b/marked/Rel-11/43_series/43068/0b452c5334567cbdc22ee9817e1246f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98609acd322cef0a0502969051648877ceae0ec2 --- /dev/null +++ b/marked/Rel-11/43_series/43068/0b452c5334567cbdc22ee9817e1246f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81f230d09e93c43d172794612a5c9159ab02553ae20ca7b96c71cf6d30187bf3 +size 30137 diff --git a/marked/Rel-11/43_series/43068/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg b/marked/Rel-11/43_series/43068/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a4362b427f804508cd3a6e904fa47b6568f23e9 --- /dev/null +++ b/marked/Rel-11/43_series/43068/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b86db546a099250c6f1b55e5417c9e2aa9f8531b04c4f6250fd777d3a92f50c +size 54049 diff --git a/marked/Rel-11/43_series/43068/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg b/marked/Rel-11/43_series/43068/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ec9f679979e64df56173be49513d83e7e4ce7e3 --- /dev/null +++ b/marked/Rel-11/43_series/43068/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5bd54eb5ccfbe79771d5d268f1f2e3c8ee853d1a7dbf5869f3d41162d2f24ace +size 109882 diff --git a/marked/Rel-11/43_series/43068/114902bbeea56bda01b64b43fad41920_img.jpg b/marked/Rel-11/43_series/43068/114902bbeea56bda01b64b43fad41920_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20d37351b63bb232a29f9417373e25dabe0c8d49 --- /dev/null +++ b/marked/Rel-11/43_series/43068/114902bbeea56bda01b64b43fad41920_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e197af5c6e288e96fc18e007fc6a3578c03435bf73f90b8b45ddd8c72a52452 +size 84538 diff --git a/marked/Rel-11/43_series/43068/18003425d0e8638dde4acc9c5c468c5c_img.jpg b/marked/Rel-11/43_series/43068/18003425d0e8638dde4acc9c5c468c5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5242f35196f7ec2faa0befcf25c690f2f3e151a0 --- /dev/null +++ b/marked/Rel-11/43_series/43068/18003425d0e8638dde4acc9c5c468c5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b75dbf593710530c4de1b793e3b5ebbbfc839344adff8ccf715db260ec0481c +size 59322 diff --git a/marked/Rel-11/43_series/43068/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-11/43_series/43068/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67832216e0ee453dc74ede70a8e15fa8cb5a48bd --- /dev/null +++ b/marked/Rel-11/43_series/43068/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d3c01198dca0dbe285a43022b50a3da1795d822808b668a28fb297506643d05 +size 35765 diff --git a/marked/Rel-11/43_series/43068/18bb06865e2dada3656ea3d57f290f7f_img.jpg b/marked/Rel-11/43_series/43068/18bb06865e2dada3656ea3d57f290f7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9854d43976bc8c2c6a84ef89aef710738d4b6f72 --- /dev/null +++ b/marked/Rel-11/43_series/43068/18bb06865e2dada3656ea3d57f290f7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:afcdb72393f10548dc69649a44f3ab6228f30d0257ffdfbb58cf6a3de0d070e2 +size 44953 diff --git a/marked/Rel-11/43_series/43068/199a8b4c5c620006757a17e930769566_img.jpg b/marked/Rel-11/43_series/43068/199a8b4c5c620006757a17e930769566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..526dde0cebdee6ba36e795734bc41faa3484b17f --- /dev/null +++ b/marked/Rel-11/43_series/43068/199a8b4c5c620006757a17e930769566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aaa6950580b742a47c21a98e5c40f68055d03a9cd2ca09ddb75f0061ff947a6e +size 102355 diff --git a/marked/Rel-11/43_series/43068/1b670c6eaa5f106cd82f1c676c2cabd7_img.jpg b/marked/Rel-11/43_series/43068/1b670c6eaa5f106cd82f1c676c2cabd7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4130a7bb86f9a5cd19df3d1fcb9023e163a4751 --- /dev/null +++ b/marked/Rel-11/43_series/43068/1b670c6eaa5f106cd82f1c676c2cabd7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12cc37548e8d8e44013287dc92ea965935e738b2816df0c9e4e503c414cab33a +size 26126 diff --git a/marked/Rel-11/43_series/43068/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg b/marked/Rel-11/43_series/43068/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5bdd97545a0d47505a4d15f17b9453f1921e0b6e --- /dev/null +++ b/marked/Rel-11/43_series/43068/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55da77e3367cd2d2861e8b0825a0039eeb4ced67ca3f1b73a83a408de57d9dc1 +size 51532 diff --git a/marked/Rel-11/43_series/43068/1d27fed9c01eb99f6535283f35fe3bbf_img.jpg b/marked/Rel-11/43_series/43068/1d27fed9c01eb99f6535283f35fe3bbf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dffc3fae8332d72bb6e676ca3f5eaffdf6d43adb --- /dev/null +++ b/marked/Rel-11/43_series/43068/1d27fed9c01eb99f6535283f35fe3bbf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dfdaa87f1f886eeee34cfb11cb647564e1a8c46f6618fe7995cdb8f1f38050c7 +size 110069 diff --git a/marked/Rel-11/43_series/43068/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-11/43_series/43068/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82b543e26bc03889a304a9abec20187d6bf6cca3 --- /dev/null +++ b/marked/Rel-11/43_series/43068/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b59db4eed7d8af6c6bc3a25b07fa0f61f95b919b17d6b94b1b30d0163ccc57b +size 124149 diff --git a/marked/Rel-11/43_series/43068/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-11/43_series/43068/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ddd60adc3c8c56949bcbf1bf0ad4cf395605f1c --- /dev/null +++ b/marked/Rel-11/43_series/43068/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:caa8a23323ba60a517a6cf41689d5211dda2867595c760df9aa550956196af20 +size 49771 diff --git a/marked/Rel-11/43_series/43068/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-11/43_series/43068/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42b63d604c0ab6a17fd97f21e6dffe7d305e3ebc --- /dev/null +++ b/marked/Rel-11/43_series/43068/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:39e6cb9e56e000ea6d2b356122cae547ca03bdf396a4080d1030cc5de6627fdc +size 151143 diff --git a/marked/Rel-11/43_series/43068/2a476a0b3dbc3429436246db4784ff9f_img.jpg b/marked/Rel-11/43_series/43068/2a476a0b3dbc3429436246db4784ff9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a151ab5159e5297de40f3e6a4434a6e6c38b8a2 --- /dev/null +++ b/marked/Rel-11/43_series/43068/2a476a0b3dbc3429436246db4784ff9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4572e1ebe0024f3015aaceacdf683a6111b48089a430ad2de8831724fe72abe +size 39814 diff --git a/marked/Rel-11/43_series/43068/2f587210e4f97c32758c5972e2e83d20_img.jpg b/marked/Rel-11/43_series/43068/2f587210e4f97c32758c5972e2e83d20_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7372a8f1ef66f7b8b9cf9d7fc707434bcca2d4a --- /dev/null +++ b/marked/Rel-11/43_series/43068/2f587210e4f97c32758c5972e2e83d20_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3407991bf3f9911a44a1b386211bbe026d085eaf7c376565728a1306424e8e9e +size 37146 diff --git a/marked/Rel-11/43_series/43068/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg b/marked/Rel-11/43_series/43068/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..657d8888baf624e3165d177298e9d5f80e8c5ea7 --- /dev/null +++ b/marked/Rel-11/43_series/43068/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dbc8b919845506c6100c5ed85b76f2e66bcd60bb169adcdea58f63d9dc8cd856 +size 43087 diff --git a/marked/Rel-11/43_series/43068/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-11/43_series/43068/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1da5aad60542a561356393d552a4116596beec2b --- /dev/null +++ b/marked/Rel-11/43_series/43068/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd1bc66a2633ce7b4f69771b3b28ee138b2b847466d034f5456b3a152c77d68e +size 164777 diff --git a/marked/Rel-11/43_series/43068/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-11/43_series/43068/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b102041d19cd65f11714621d83dc08d5012822fe --- /dev/null +++ b/marked/Rel-11/43_series/43068/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94afc7285c98de7e883df91dfe3b41e15154d185a77bed0a8dd27c84e7d5226c +size 36613 diff --git a/marked/Rel-11/43_series/43068/3337af75dfee8af7687b4f49914d6c93_img.jpg b/marked/Rel-11/43_series/43068/3337af75dfee8af7687b4f49914d6c93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4e3a468a0c6537a16be772c87845c0f83e577e1 --- /dev/null +++ b/marked/Rel-11/43_series/43068/3337af75dfee8af7687b4f49914d6c93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3cafd6ce37c646d6a9b5609f821c49ded171a3d742a3d3dbb0bca625e9077269 +size 178498 diff --git a/marked/Rel-11/43_series/43068/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-11/43_series/43068/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4ddb604bcc1abfc264809267683e97ccae20274 --- /dev/null +++ b/marked/Rel-11/43_series/43068/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ffe2e14acc5e9b6d8af70ddd0e31e5976904b0ca4c47daafb4fb4e5f8face88 +size 32574 diff --git a/marked/Rel-11/43_series/43068/38d82ffe820e339811b396206f40a201_img.jpg b/marked/Rel-11/43_series/43068/38d82ffe820e339811b396206f40a201_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c36b62d94c299f48391b8dc7f2554c50d42ebf9 --- /dev/null +++ b/marked/Rel-11/43_series/43068/38d82ffe820e339811b396206f40a201_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7193fa5060c2bb2604a25ced97e7603a370acace245c37c17dd82aaa06679244 +size 81593 diff --git a/marked/Rel-11/43_series/43068/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/Rel-11/43_series/43068/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf8c7065e44b2dc3ccc26b2b6f8f6576e7421406 --- /dev/null +++ b/marked/Rel-11/43_series/43068/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3904c426f432d7520d91af1773a9dd4cc559fe11d6177687f08c030004af5e01 +size 34460 diff --git a/marked/Rel-11/43_series/43068/4806f9f95fff13a30d6523bd6ffeac63_img.jpg b/marked/Rel-11/43_series/43068/4806f9f95fff13a30d6523bd6ffeac63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..856d7c8308deedbc3bd0d2bf36c7f0c1a2775ce9 --- /dev/null +++ b/marked/Rel-11/43_series/43068/4806f9f95fff13a30d6523bd6ffeac63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5890114e918a3c4259fc65eac18bc50c053eb3db07e2a4448e02e757b1769eb5 +size 34624 diff --git a/marked/Rel-11/43_series/43068/49fe8fe978c0f7e73112d231feb377eb_img.jpg b/marked/Rel-11/43_series/43068/49fe8fe978c0f7e73112d231feb377eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f079a36cfbbd675f0d16d390160408fac6d89d74 --- /dev/null +++ b/marked/Rel-11/43_series/43068/49fe8fe978c0f7e73112d231feb377eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee8a6191871d3321425617e490fe3d051f34a25457e3dd7c0d91f14d1cde39f5 +size 52348 diff --git a/marked/Rel-11/43_series/43068/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-11/43_series/43068/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a03e6f223fd7aae0b1595df56a22269904c4da77 --- /dev/null +++ b/marked/Rel-11/43_series/43068/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37c84fc4da5cd0c4cd1135ec84e80d587c69c08bb93076730e4e1d3a41c9a7dc +size 32517 diff --git a/marked/Rel-11/43_series/43068/575d7d345b3ec04393bb2ec720ebabca_img.jpg b/marked/Rel-11/43_series/43068/575d7d345b3ec04393bb2ec720ebabca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37102d84f6e833c02b8a528d6cb538e8ddbd51d4 --- /dev/null +++ b/marked/Rel-11/43_series/43068/575d7d345b3ec04393bb2ec720ebabca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1925358e7193d577aa5985b61590d32a0226ecc30750f50f0b98f9f7457e6e3c +size 29706 diff --git a/marked/Rel-11/43_series/43068/5801c19431e76330430e92a598cc7a16_img.jpg b/marked/Rel-11/43_series/43068/5801c19431e76330430e92a598cc7a16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9689afb69922b02e9a99ec2fdd6827419ccc00d5 --- /dev/null +++ b/marked/Rel-11/43_series/43068/5801c19431e76330430e92a598cc7a16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23ae1c55aa8ed95071b02eb5cc2ac84cb8e84e8cc6a7377840095332506d74b4 +size 45560 diff --git a/marked/Rel-11/43_series/43068/5cf80bac69830ea773ac17c87e0ae24d_img.jpg b/marked/Rel-11/43_series/43068/5cf80bac69830ea773ac17c87e0ae24d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..784c0313daa095730cc43ff14917e9e0b9ecd480 --- /dev/null +++ b/marked/Rel-11/43_series/43068/5cf80bac69830ea773ac17c87e0ae24d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:200bdbe59dfcefcc32de308a086d87a24491835c407d79a0ebdcede6be4e2a2c +size 81144 diff --git a/marked/Rel-11/43_series/43068/5e9af8986a5845504f251d3079da8078_img.jpg b/marked/Rel-11/43_series/43068/5e9af8986a5845504f251d3079da8078_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4226b63af69018fc15f3a48c82a210024c6c4c20 --- /dev/null +++ b/marked/Rel-11/43_series/43068/5e9af8986a5845504f251d3079da8078_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e74726640e3af9a5eeed5247a68eac7d7a7c30a9465a4fa1cdba3ca991acc028 +size 73551 diff --git a/marked/Rel-11/43_series/43068/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/marked/Rel-11/43_series/43068/61a7f401eb46fe99a71f27bc37493f04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..baa4259112249bbb9b66d35a5bca204837d15246 --- /dev/null +++ b/marked/Rel-11/43_series/43068/61a7f401eb46fe99a71f27bc37493f04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d45d39941c55858e110f4662fc38866d32291bd041f645b8efea42f4e0deb082 +size 48278 diff --git a/marked/Rel-11/43_series/43068/6be06b7dc72bb42afcb3465394667c3b_img.jpg b/marked/Rel-11/43_series/43068/6be06b7dc72bb42afcb3465394667c3b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e342db05ac9f30cbf887f65065de17d8ff8f6ee --- /dev/null +++ b/marked/Rel-11/43_series/43068/6be06b7dc72bb42afcb3465394667c3b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df1a36eb6ac43d9841f6a61a807982038829bfe35e17abd331370440e9bde3d0 +size 41264 diff --git a/marked/Rel-11/43_series/43068/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-11/43_series/43068/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f56745dd49211c2a9de52ebb0fb1b6128f4048c --- /dev/null +++ b/marked/Rel-11/43_series/43068/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:359964da6b9bcc173ad39dfb67a39bfc2eb5faf36f53e39132051cb3b6b1e1de +size 72229 diff --git a/marked/Rel-11/43_series/43068/719ef0f734259484038b2434e5dc3f24_img.jpg b/marked/Rel-11/43_series/43068/719ef0f734259484038b2434e5dc3f24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4bc7eec293d09bc1da5c1b92451e397f620b75d2 --- /dev/null +++ b/marked/Rel-11/43_series/43068/719ef0f734259484038b2434e5dc3f24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:471bc656aa88c07201d2038532be94567dc23172ab171a4f9d959c91c30f8071 +size 48809 diff --git a/marked/Rel-11/43_series/43068/750b1652a4f4791b84c02aa755a1dedd_img.jpg b/marked/Rel-11/43_series/43068/750b1652a4f4791b84c02aa755a1dedd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22a4dbbaef068e7d3bc360ec20d37237afda2429 --- /dev/null +++ b/marked/Rel-11/43_series/43068/750b1652a4f4791b84c02aa755a1dedd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2348b9133e7b128ac1e9f47aa27c9e90126bf89c8483aef46935801e4bea4e6c +size 58329 diff --git a/marked/Rel-11/43_series/43068/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-11/43_series/43068/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eee1cb039b19b55763a228c468a42857a49eda72 --- /dev/null +++ b/marked/Rel-11/43_series/43068/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6fc94b2015b49407b2f1ca5db73ac0c4a1dd18d4e941595b9a1972f364848546 +size 61061 diff --git a/marked/Rel-11/43_series/43068/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-11/43_series/43068/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..94e8f52436150871b0ad4b988a95fc1705907c79 --- /dev/null +++ b/marked/Rel-11/43_series/43068/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5777614e7120fa8db937ebbdf20acc9a1f544ed78291547de56df917a5353229 +size 7480 diff --git a/marked/Rel-11/43_series/43068/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/Rel-11/43_series/43068/7ed5d5770331f31ade15439a21c31425_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1e05c4e367a36bbf0d4e8a6642f56119d10873a --- /dev/null +++ b/marked/Rel-11/43_series/43068/7ed5d5770331f31ade15439a21c31425_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e284ed6d696502ac0b96f784936297e5f8aebd63a22688703529da77b9c2cbce +size 72289 diff --git a/marked/Rel-11/43_series/43068/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-11/43_series/43068/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9cd13279068d86db6d73f2189f5ba54f5a53d897 --- /dev/null +++ b/marked/Rel-11/43_series/43068/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:792c73dad1c9bb7432178b59f43d48558d822d8b72d832bd60e8ac20aeecbbc0 +size 9898 diff --git a/marked/Rel-11/43_series/43068/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg b/marked/Rel-11/43_series/43068/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7abe31b1d793542767d1a5d44b2997fa929df6f --- /dev/null +++ b/marked/Rel-11/43_series/43068/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36cce82eca6446a334ca2db8bb94d49f4f5cc694e0da17d57150381f3ddc8b5d +size 27614 diff --git a/marked/Rel-11/43_series/43068/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-11/43_series/43068/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7078ada902b2484bfa157397a32d40b92faec76c --- /dev/null +++ b/marked/Rel-11/43_series/43068/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c661f476fe359df6ce1799c67076490281e0f6a450874bc1ebe5ce5f44b7a3ce +size 151249 diff --git a/marked/Rel-11/43_series/43068/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-11/43_series/43068/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf947fd88e7e62039be1367f92bc5a2dbba32392 --- /dev/null +++ b/marked/Rel-11/43_series/43068/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:611d83889a6f59b400b9bc2cb9c8372539aaf18410cec6ebe47d9f2ce058c0bb +size 107861 diff --git a/marked/Rel-11/43_series/43068/90df9788d66ecf65abf861caf76be5ca_img.jpg b/marked/Rel-11/43_series/43068/90df9788d66ecf65abf861caf76be5ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3e9dd8c2143edad4539aaeb0e9f58b581cfbf7a --- /dev/null +++ b/marked/Rel-11/43_series/43068/90df9788d66ecf65abf861caf76be5ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7b857975abc83552060e8e8ae8ede1bce43fce8fa7038f182d8e40b4d9a037a +size 128620 diff --git a/marked/Rel-11/43_series/43068/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-11/43_series/43068/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38f27574b1a3daf4d3bdfcc9bc570a5b8250f7da --- /dev/null +++ b/marked/Rel-11/43_series/43068/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:39626223676a1d4d81d58aa3b578f3e94807a0eb41e610505635eb49d32fee3a +size 115149 diff --git a/marked/Rel-11/43_series/43068/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-11/43_series/43068/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b3b35ae3bbe6c76626eba0cbd63eaf76941b5f3 --- /dev/null +++ b/marked/Rel-11/43_series/43068/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5aceae0617ec728a15747f7ce5afb03c7005983e96c20311fb6a0244b9d2e0d +size 31933 diff --git a/marked/Rel-11/43_series/43068/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-11/43_series/43068/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a3978ebc623fb0637ed3939264420b5bbb5afebd --- /dev/null +++ b/marked/Rel-11/43_series/43068/a0e8fe7862a6d7341faf5dac275277cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:044a1242cc01dfc4a5589e4fd5a86d9a015e6f2fb7165bbb6ebd0bfda7e67108 +size 91776 diff --git a/marked/Rel-11/43_series/43068/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-11/43_series/43068/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6c324d61ec6d38475a5e87409d26fabf2859506 --- /dev/null +++ b/marked/Rel-11/43_series/43068/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c30ef264fa0c54b484e41e2f69c047524a01389b31a8455ccebecc74b27a58b +size 191157 diff --git a/marked/Rel-11/43_series/43068/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg b/marked/Rel-11/43_series/43068/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c25d67f6194855e6337b859cb209a6ca377a1225 --- /dev/null +++ b/marked/Rel-11/43_series/43068/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e00bff3303fc5d8cc185874dd4cd584fed2c7f501372e1c061257ae118b3101e +size 66497 diff --git a/marked/Rel-11/43_series/43068/a963ca41bde1669b18a4b783616f228b_img.jpg b/marked/Rel-11/43_series/43068/a963ca41bde1669b18a4b783616f228b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a51dbaeb5e207d2b06c028a1f1159f938d32205 --- /dev/null +++ b/marked/Rel-11/43_series/43068/a963ca41bde1669b18a4b783616f228b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b0acc1539a8ce62d4461a208dbd224585af1665e70ad9c43392af179bc24bd2 +size 30789 diff --git a/marked/Rel-11/43_series/43068/acd4783cdd6f72b4687bfff877f71e43_img.jpg b/marked/Rel-11/43_series/43068/acd4783cdd6f72b4687bfff877f71e43_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af18556ecdc4e5b36e829fb95a3c25d821370835 --- /dev/null +++ b/marked/Rel-11/43_series/43068/acd4783cdd6f72b4687bfff877f71e43_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ce01cd34f33bb9d315eab84ce8b7cdad9adce8ba3062f9932fb59ae8f82159f +size 21417 diff --git a/marked/Rel-11/43_series/43068/b51423b6c049f5b5fcde42e50b58f18b_img.jpg b/marked/Rel-11/43_series/43068/b51423b6c049f5b5fcde42e50b58f18b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f08378ac6edd3ba7945d6025b77d14eb1bbc05a --- /dev/null +++ b/marked/Rel-11/43_series/43068/b51423b6c049f5b5fcde42e50b58f18b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13ebf5051b29d3de3c10c2f42a964ec06aa12358fb54d9b2368820daa6de4ffe +size 36763 diff --git a/marked/Rel-11/43_series/43068/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-11/43_series/43068/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a6c48ce0566db54de4c00395168f1385e39ffcb --- /dev/null +++ b/marked/Rel-11/43_series/43068/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3954ef7314a019e2e2f822d1fb6a63fea91361314a489a460a754850003755c +size 49485 diff --git a/marked/Rel-11/43_series/43068/bc9d0c0b02cbe628b1b6548cc1107734_img.jpg b/marked/Rel-11/43_series/43068/bc9d0c0b02cbe628b1b6548cc1107734_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8735c976afd8745bf6a806983f4dc0eb785a24a8 --- /dev/null +++ b/marked/Rel-11/43_series/43068/bc9d0c0b02cbe628b1b6548cc1107734_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1285b3346142a59afa1a23b6f5f85c858d926ac1081f11e124f95842dbcfa75 +size 48834 diff --git a/marked/Rel-11/43_series/43068/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Rel-11/43_series/43068/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c24c59a04500094702dc1e177c023aad9bcbe31 --- /dev/null +++ b/marked/Rel-11/43_series/43068/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:74853a3e2e9416741be38f7113cbd468c16c9d693edfb24d073ac39d2e268f4c +size 22062 diff --git a/marked/Rel-11/43_series/43068/c07e21a8d65991db04263322f859c94f_img.jpg b/marked/Rel-11/43_series/43068/c07e21a8d65991db04263322f859c94f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47daf6a8402cf11f2c736b9d29e1a7bcd92a5781 --- /dev/null +++ b/marked/Rel-11/43_series/43068/c07e21a8d65991db04263322f859c94f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e0efa8c60f38449a3670002c54e0073d3b451a215fec13288dbe75cb729f537 +size 45612 diff --git a/marked/Rel-11/43_series/43068/c0ca823603794512478906b302176bca_img.jpg b/marked/Rel-11/43_series/43068/c0ca823603794512478906b302176bca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f79175ea0da9065ae3b5b6fc10bbe9ef2a677f2 --- /dev/null +++ b/marked/Rel-11/43_series/43068/c0ca823603794512478906b302176bca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:254e5a78ce78cdb787f46cd59df150d8b8f7e1fb75e857930ed82cb40ed814fc +size 38438 diff --git a/marked/Rel-11/43_series/43068/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg b/marked/Rel-11/43_series/43068/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47631cce1358242d151f15e49b8b020d9058bb66 --- /dev/null +++ b/marked/Rel-11/43_series/43068/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26cda7c09e45318123dfb5acd8789cfa168ed728b8452115618b80ff283e24ed +size 52692 diff --git a/marked/Rel-11/43_series/43068/cdd4dfacab004e9979caed3fffea69e5_img.jpg b/marked/Rel-11/43_series/43068/cdd4dfacab004e9979caed3fffea69e5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8dcbdadc3cb772788c8c598ba99d5facf09cfe14 --- /dev/null +++ b/marked/Rel-11/43_series/43068/cdd4dfacab004e9979caed3fffea69e5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14829ae8f042102854edd1770df7eb4ccae9a16eb9e6b3b437a8aad2bba88019 +size 52215 diff --git a/marked/Rel-11/43_series/43068/d04c50badc78d5ba47bf4e352af4a754_img.jpg b/marked/Rel-11/43_series/43068/d04c50badc78d5ba47bf4e352af4a754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e83f8a90fd53f7b583a932ba5c53e2c3e90ca882 --- /dev/null +++ b/marked/Rel-11/43_series/43068/d04c50badc78d5ba47bf4e352af4a754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8bf84b212f2360a1df1cca91b494a412fc53a608bb206dcd30cd81e9fa094fb4 +size 84689 diff --git a/marked/Rel-11/43_series/43068/d3ca266c298aeb34b019960c6c36f187_img.jpg b/marked/Rel-11/43_series/43068/d3ca266c298aeb34b019960c6c36f187_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79cc99b538cceee1d061027bdf38eec4b14c5764 --- /dev/null +++ b/marked/Rel-11/43_series/43068/d3ca266c298aeb34b019960c6c36f187_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d7f0dcb375c6b19316248557f82cb2793c5f58d4041c7098467014da69a1c15 +size 108456 diff --git a/marked/Rel-11/43_series/43068/d8698aacaeead6dfed9a1e448670a2e4_img.jpg b/marked/Rel-11/43_series/43068/d8698aacaeead6dfed9a1e448670a2e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bbe0e01223fcdc1fa17b0c0395cc38bb37dd6276 --- /dev/null +++ b/marked/Rel-11/43_series/43068/d8698aacaeead6dfed9a1e448670a2e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34bc9fc3fcc71dfa14d3ebd9c3ee3db77c6f27489fdd7d5df55458b2cea1cef6 +size 19194 diff --git a/marked/Rel-11/43_series/43068/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/Rel-11/43_series/43068/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2793d80e327924d49429b64da30168d52abe388a --- /dev/null +++ b/marked/Rel-11/43_series/43068/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae8723ae25f2b8918838c27d3d9fbc842cbd34d181a2f6f035f022617df8bd70 +size 161171 diff --git a/marked/Rel-11/43_series/43068/db39acbd11df5eb7e79ab84562fb8f74_img.jpg b/marked/Rel-11/43_series/43068/db39acbd11df5eb7e79ab84562fb8f74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29370512bfc550c5a29e4fe6b1d31d32d6f3d2c2 --- /dev/null +++ b/marked/Rel-11/43_series/43068/db39acbd11df5eb7e79ab84562fb8f74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f4a9f20aeabcf558a76df3050dba707e23332041156a38118efc76c01f4a317 +size 52370 diff --git a/marked/Rel-11/43_series/43068/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-11/43_series/43068/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a3ec544617efc9fdb19096653a64e5f708032c9 --- /dev/null +++ b/marked/Rel-11/43_series/43068/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34fc52b6d54b5c1a9270977f382a107966c2f5790c3244bd59814b112542b84c +size 18673 diff --git a/marked/Rel-11/43_series/43068/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg b/marked/Rel-11/43_series/43068/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b33195329fa461e49c8ecfcea87b8e8ccf6e7e9 --- /dev/null +++ b/marked/Rel-11/43_series/43068/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6738ccc6f98bd1f21f36d1f16a774236191aa96fa6b8afd68f835acb79b2993f +size 49280 diff --git a/marked/Rel-11/43_series/43068/e16bfa31d748f4d99ec4ae3d16656926_img.jpg b/marked/Rel-11/43_series/43068/e16bfa31d748f4d99ec4ae3d16656926_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd68b1b71b07e4f4a6e4e142f7af5947f583f7b3 --- /dev/null +++ b/marked/Rel-11/43_series/43068/e16bfa31d748f4d99ec4ae3d16656926_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c1caa5f8dfdf3ca7c3c7afc5d9c6eb09861316ccc217722f52646cd1b2ccebc0 +size 41071 diff --git a/marked/Rel-11/43_series/43068/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/marked/Rel-11/43_series/43068/e2c120be98ede6deb60dd341f5a9803b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55ff83a56201e6c5c1f71341ce9b574f5f93d1fe --- /dev/null +++ b/marked/Rel-11/43_series/43068/e2c120be98ede6deb60dd341f5a9803b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0928ce3e4765b3cebe8d2a35c959228d8ec0cb1d5f025a80ff3b201330b279e +size 108977 diff --git a/marked/Rel-11/43_series/43068/e7010c66da16316c2935dfbbef5056b3_img.jpg b/marked/Rel-11/43_series/43068/e7010c66da16316c2935dfbbef5056b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..220c609553463e4e406ae5323bf51ddd081d2ffd --- /dev/null +++ b/marked/Rel-11/43_series/43068/e7010c66da16316c2935dfbbef5056b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2710dc1fd128dbe03fc5ac2413017327b0a2a34c0b9f7845230d5c66cbb13125 +size 53871 diff --git a/marked/Rel-11/43_series/43068/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-11/43_series/43068/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ca1fa87e8c77df460d7878ab249b43136d74664 --- /dev/null +++ b/marked/Rel-11/43_series/43068/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a71e02e5cd509113c7fe509c6cebd2fe38c51428cd34356c6f40952066e78007 +size 118900 diff --git a/marked/Rel-11/43_series/43068/f324fbc5d5af1e4da9cd932389f0064c_img.jpg b/marked/Rel-11/43_series/43068/f324fbc5d5af1e4da9cd932389f0064c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6506036624a023a21d8475662c42a20968b273da --- /dev/null +++ b/marked/Rel-11/43_series/43068/f324fbc5d5af1e4da9cd932389f0064c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:756f2626b76c349a32ca8ef22677a24466162a6a50133cfbdadd28f0b2d5cf41 +size 25163 diff --git a/marked/Rel-11/43_series/43068/f61d0925551545b5938b3a4d1bbf63c3_img.jpg b/marked/Rel-11/43_series/43068/f61d0925551545b5938b3a4d1bbf63c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61c87e31623116d7d9854c330e09ad65797760ea --- /dev/null +++ b/marked/Rel-11/43_series/43068/f61d0925551545b5938b3a4d1bbf63c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88eda6555d46c3c1e9ab1ed8f6d6e4997be3f710ef7bbd39ad14b70df7ff1556 +size 73509 diff --git a/marked/Rel-11/43_series/43068/fcbc3c31776721edc98ceb1944ec438f_img.jpg b/marked/Rel-11/43_series/43068/fcbc3c31776721edc98ceb1944ec438f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..abef5e43cfe4ebc7179169404b702e763210a933 --- /dev/null +++ b/marked/Rel-11/43_series/43068/fcbc3c31776721edc98ceb1944ec438f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6dd4c28f2276793136f593db5584f2ae192c4ee614f89e0f067f52fa38e9fec +size 46905 diff --git a/marked/Rel-11/43_series/43068/fcc757566216206ceddbd6c775e8db02_img.jpg b/marked/Rel-11/43_series/43068/fcc757566216206ceddbd6c775e8db02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a195de78b0c12fbb27dd9f782a0bd0d65db33f8d --- /dev/null +++ b/marked/Rel-11/43_series/43068/fcc757566216206ceddbd6c775e8db02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c86716f5086c1d602ec61bc52284df1f0c99d4cc94d2a3fed60a1b232d99fe3 +size 66085 diff --git a/marked/Rel-11/43_series/43068/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/marked/Rel-11/43_series/43068/fd3cbb53e991f8209ba17b398f426e13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3551f5a27d2c7badd2fbc518b33993c4823ca06 --- /dev/null +++ b/marked/Rel-11/43_series/43068/fd3cbb53e991f8209ba17b398f426e13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:caa8a086bbfc829a33c8d84036dc053644b1e6e71fea5e415de46917f5f1fed7 +size 27074 diff --git a/marked/Rel-11/43_series/43068/fd76efce549d3713543bb5ed9b023c2e_img.jpg b/marked/Rel-11/43_series/43068/fd76efce549d3713543bb5ed9b023c2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62050344c40a8fd0e81d2b1e8f7ba710d11c1af9 --- /dev/null +++ b/marked/Rel-11/43_series/43068/fd76efce549d3713543bb5ed9b023c2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:887bc05928d13a554ad23f5677fff74a84abfd03bbd92ef596446336d32dbdc5 +size 92916 diff --git a/marked/Rel-11/43_series/43068/ffb6acd27b8e3a54392840948a75869f_img.jpg b/marked/Rel-11/43_series/43068/ffb6acd27b8e3a54392840948a75869f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..267b629079764d76e451918d3b8c60914dbe74df --- /dev/null +++ b/marked/Rel-11/43_series/43068/ffb6acd27b8e3a54392840948a75869f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62c2ab07b5bb025d26ccfb38f59d7e1f5f1d4d2318d4e2e7f61a4626ec178e74 +size 42505 diff --git a/marked/Rel-11/43_series/43068/ffe0fef452a0ae9a20253c319c54e13c_img.jpg b/marked/Rel-11/43_series/43068/ffe0fef452a0ae9a20253c319c54e13c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08cb90d898473264ef99cfef3e62f305781d44b1 --- /dev/null +++ b/marked/Rel-11/43_series/43068/ffe0fef452a0ae9a20253c319c54e13c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a04932aa3492d89b1f820272b010b99eabd3b9db1f0315e149a9293d47d9c76 +size 51061 diff --git a/marked/Rel-11/43_series/43068/raw.md b/marked/Rel-11/43_series/43068/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3fbe4846e2b4d9968d4f40c0f5a1b5f526cc4202 --- /dev/null +++ b/marked/Rel-11/43_series/43068/raw.md @@ -0,0 +1,5923 @@ +# Contents + +| | | +|--------------------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions and abbreviations ..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Abbreviations ..... | 9 | +| 4 Main concepts ..... | 10 | +| 4.1 Group definition ..... | 10 | +| 4.2 Group conversations..... | 10 | +| 4.2.1 Group call initiation..... | 10 | +| 4.2.1.1 Normal operation with successful outcome..... | 10 | +| 4.2.1.2 Exceptional procedures..... | 12 | +| 4.2.2 On-going group calls ..... | 12 | +| 4.2.2.1 Normal operation with successful outcome..... | 12 | +| 4.2.2.2 Exceptional procedures..... | 15 | +| 4.2.3 Leaving of a group call without termination ..... | 15 | +| 4.2.4 Group call termination..... | 15 | +| 4.2.5 Acknowledgements ..... | 16 | +| 4.2.6 Transactions between the mobile station and the network..... | 16 | +| 4.2.7 Processing of originator-to-dispatcher information..... | 16 | +| 4.2.8 Transfer of application-specific data to group call members ..... | 16 | +| 4.2.8.1 General..... | 16 | +| 4.2.8.2 Sending of application-specific data..... | 17 | +| 4.2.8.2.1 By the talking service subscriber ..... | 17 | +| 4.2.8.2.2 By a listener..... | 17 | +| 4.2.8.3 Sending a confirmation of receipt of application-specific data ..... | 18 | +| 4.2.8.4 Distributing application-specific data to a voice group call ..... | 18 | +| 4.2.8.4.1 Distribution via the MSC ..... | 18 | +| 4.2.8.4.2 Immediate distribution by the BSC..... | 19 | +| 5 General architecture ..... | 19 | +| 5.1 Group Call Register (GCR)..... | 19 | +| 5.2 Voice group call responsibility ..... | 24 | +| 5.3 RANflex configuration with group call redundancy..... | 24 | +| 5.3.1 MSC selection in a RANflex configuration with group call redundancy ..... | 24 | +| 5.3.2 GCR synchronization in a RANflex configuration with group call redundancy ..... | 25 | +| 5.3.3 GCR Restoration in a RANflex configuration with group call redundancy ..... | 25 | +| 6 Compatibility issues..... | 26 | +| 7 Transmission ..... | 26 | +| 7.1 Transmission architecture ..... | 26 | +| 7.1a Transmission architecture – A interface circuit sharing..... | 27 | +| 7.1a.1 Transmission architecture – General..... | 27 | +| 7.1a.2 Transmission architecture – Control Plane..... | 27 | +| 7.1a.3 Transmission architecture – User Plane ..... | 27 | +| 7.1b Transmission architecture – A interface link sharing..... | 28 | +| 7.1b.1 Transmission architecture – General..... | 28 | +| 7.1b.2 Transmission architecture – Control Plane..... | 28 | +| 7.1b.3 Transmission architecture – User Plane ..... | 28 | +| 7.2 Radio channels ..... | 28 | +| 7.3 Data confidentiality ..... | 30 | +| 8 Information storage ..... | 32 | +| 8.1 Information stored in the GCR..... | 32 | +| 8.1.1 Information used for routing of service subscriber originated voice group calls..... | 32 | +| 8.1.2 Static Group call attributes ..... | 33 | +| 8.1.2.1 Group call area..... | 34 | + +| | | | +|------------|---------------------------------------------------------------------------------------------------|-----| +| 8.1.2.2 | Dispatcher identities ..... | 34 | +| 8.1.2.3 | No activity time ..... | 34 | +| 8.1.2.4 | Priorities ..... | 35 | +| 8.1.3 | Transient Group Call Attributes ..... | 35 | +| 8.1.3.0 | General ..... | 35 | +| 8.1.3.1 | Group Call Status Information ..... | 35 | +| 8.1.3.2 | Initial Talker Information ..... | 35 | +| 8.2 | Information managed per subscriber ..... | 35 | +| 8.2.1 | Stored in the HLR ..... | 35 | +| 8.2.2 | Stored in the VLR ..... | 36 | +| 8.2.3 | Stored in the SIM ..... | 36 | +| 8.2.3a | Stored in the USIM ..... | 36 | +| 8.3 | Information used for routing of dispatcher originated voice group calls ..... | 36 | +| 9 | Identities ..... | 36 | +| 9.1 | Elementary identities for group calls ..... | 36 | +| 9.2 | Use of identities in the network ..... | 38 | +| 10 | Operation and maintenance aspects ..... | 40 | +| 11 | Function and information flows ..... | 40 | +| 11.1 | Group management ..... | 40 | +| 11.2 | Group membership management ..... | 40 | +| 11.3 | Call management ..... | 40 | +| 11.3.1 | Call establishment ..... | 40 | +| 11.3.1.1 | Service subscriber call establishment ..... | 40 | +| 11.3.1.1.1 | Initial stage ..... | 40 | +| 11.3.1.1.2 | Establishment of the transmission means ..... | 42 | +| 11.3.1.1.3 | Release of the dedicated transmission means of the calling service subscriber ..... | 44 | +| 11.3.1.1.4 | Release of the dedicated transmission means of mobile stations responding to a notification ..... | 44 | +| 11.3.1.1.5 | void ..... | 44 | +| 11.3.1.1.6 | void ..... | 44 | +| 11.3.1.2 | Dispatcher call establishment ..... | 44 | +| 11.3.1.3 | Notification procedures ..... | 45 | +| 11.3.1.4 | Destination service subscribers ..... | 47 | +| 11.3.1.5 | Destination dispatchers ..... | 47 | +| 11.3.2 | Call release ..... | 47 | +| 11.3.2.1 | Call termination by the calling subscriber ..... | 47 | +| 11.3.2.2 | Call termination by dispatchers ..... | 48 | +| 11.3.2.3 | Call termination on expiry of no activity timer ..... | 48 | +| 11.3.3 | Leaving of a dispatcher ..... | 48 | +| 11.3.4 | Leaving and returning to a voice group call ..... | 48 | +| 11.3.5 | Cell change ..... | 49 | +| 11.3.5.1 | Listening subscriber ..... | 49 | +| 11.3.5.2 | Talking subscriber ..... | 49 | +| 11.3.5.3 | Dispatcher ..... | 49 | +| 11.3.6 | New calls ..... | 49 | +| 11.3.7 | Uplink and Downlink management ..... | 50 | +| 11.3.7.1 | Uplink transmission management ..... | 50 | +| 11.3.7.1a | Transfer of a talking service subscriber to a dedicated connection ..... | 51 | +| 11.3.7.1b | Release of the dedicated transmission means of a talking service subscriber ..... | 51 | +| 11.3.7.2 | Mute/Unmute downlink of the talker ..... | 52 | +| 11.3.7a | Signalling procedures for the user plane ..... | 57 | +| 11.3.7a.1 | Group call re-establishment by the BSS ..... | 57 | +| 11.3.8 | Overview of signalling ..... | 57 | +| 11.3.9 | Short Message Service (SMS) ..... | 123 | +| 11.3.9.1 | Delivering SMS to the voice group call ..... | 123 | +| 11.3.9.2 | Point-to-point short message during an ongoing voice group call ..... | 125 | +| 11.4 | Functional requirement of Anchor MSC ..... | 126 | +| 11.5 | Functional requirement of Relay MSC ..... | 140 | +| 11.5A | Functional requirement of group call serving MSC (within a RANflex pool) ..... | 153 | +| 11.5B | Functional requirement of VMSC (within a RANflex pool) ..... | 161 | +| 11.6 | Functional requirement of GCR ..... | 164 | + +| | | | +|------------------------|----------------------------------------------------|-----| +| 11.7 | Functional requirement of VLR ..... | 174 | +| 12 | Content of messages..... | 178 | +| 12.1 | Messages on the B-interface (MSC-VLR)..... | 179 | +| 12.1.1 | Allocate Group Call Number..... | 179 | +| 12.1.2 | Allocate Group Call Number ack ..... | 179 | +| 12.1.3 | Allocate Group Call Number negative response ..... | 179 | +| 12.1.4 | Release Group Call Number..... | 179 | +| 12.1.5 | Send Group Call Info..... | 179 | +| 12.1.6 | Send Group Call Info ack ..... | 179 | +| 12.1.7 | Send Group Call Info negative response ..... | 180 | +| 12.2 | Messages on the E-interface (MSC-MSC)..... | 180 | +| 12.2.1 | Prepare Group Call ..... | 180 | +| 12.2.2 | Prepare Group Call ack ..... | 180 | +| 12.2.3 | Prepare Group Call negative response..... | 180 | +| 12.2.4 | Send Group Call End Signal..... | 181 | +| 12.2.5 | Forward Group Call Signalling ..... | 182 | +| 12.2.6 | Process Group Call Signalling..... | 182 | +| 12.2.7 | MT Forward Short Message for VGCS Request..... | 183 | +| 12.2.8 | MT Forward Short Message for VGCS Response ..... | 183 | +| 12.2.9 | Send Group Call Info..... | 184 | +| 12.2.10 | Send Group Call Info ack ..... | 184 | +| 12.2.11 | Send Group Call Info negative response ..... | 185 | +| 12.3 | Messages on the I-interface (MSC-GCR) ..... | 185 | +| 12.3.1 | GCR Interrogation ..... | 185 | +| 12.3.2 | GCR Interrogation ack ..... | 187 | +| 12.3.3 | GCR interrogation negative response..... | 187 | +| 12.3.4 | Call released ..... | 188 | +| 12.3.5 | GCR SMS Interrogation ..... | 188 | +| 12.3.6 | GCR SMS Interrogation Response..... | 188 | +| 12.4 | Messages on the GCR - GCR interface..... | 189 | +| 12.4.1 | Sync GCR ..... | 189 | +| 12.4.2 | Sync GCR ack ..... | 189 | +| 12.4.3 | Sync GCR negative response ..... | 189 | +| 13 | List of system parameters ..... | 189 | +| 13.1 | Timers..... | 189 | +| 13.1.1 | Txx..... | 189 | +| 13.1.2 | T1..... | 190 | +| 13.1.3 | T2..... | 190 | +| 13.1.4 | Tbb..... | 190 | +| 13.1.5 | Ttv..... | 190 | +| 13.1.6 | Tast..... | 190 | +| 13.1.7 | T3..... | 190 | +| Annex A (informative): | Change History..... | 192 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the stage two description of the Voice Group Call Service (VGCS) which allows speech conversation of a predefined group of service subscribers in half duplex mode on the radio link taking into account multiple subscribers involved in the group call per cell. + +# --- 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] Void. +- [1a] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 42.068: "Voice Group Call Service (VGCS); Stage 1". +- [3] 3GPP TS 43.022: "Functions related to Mobile Station (MS) in idle mode". +- [4] 3GPP TS 23.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 2". +- [5] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol". +- [6] 3GPP TS 45.008: "Radio subsystem link control". +- [7] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3". +- [8] ITU-T Recommendation E.164: "The international public telecommunication numbering plan". +- [9] 3GPP TS 42.009(Rel-4): "Security aspects". +- [10] 3GPP TS 43.020: "Security related network functions". +- [11] 3GPP TS 44.068: "Group Call Control (GCC) protocol". +- [12] 3GPP TS 22.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 1". +- [13] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [14] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)". +- [15] 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface". +- [16] 3GPP TS 28.062: "Inband Tandem Free Operation (TFO) of Speech Codecs; Service Description; Stage 3". +- [17] 3GPP TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes". +- [18] 3GPP TS 23.018: "Basic call handling; Technical realization". + +# 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TS 42.068 and the following apply: + +**group call anchor MSC:** the MSC responsible for managing and maintaining a particular voice group call. The group call anchor MSC is determined as the one controlling the cells of the group call area (see also group call relay MSC). For a voice group call where the group call area exceeds one MSC area, the group call anchor MSC is predefined in the network. In a RANflex configuration with group call redundancy, the group call anchor MSC redundancy pool (instead of a group call anchor MSC) is predefined in a network for a given voice group call. + +**Group Call Attributes (GCA):** group call area, dispatcher identities, and the non-activity time which results in the release of the voice group call by the network + +**group call relay MSC:** the MSC controlling cells of a group call area which are not under control of the group call anchor MSC for those voice group call services where the group call area exceeds one MSC area. For a voice group call where the group area exceeds one MSC area, the address of the group call relay MSC is pre-configured in the anchor MSC's GCR. In a RANflex configuration with group call redundancy this preconfigured address identifies a group call relay MSC redundancy pool (instead of a group call relay MSC). + +**Group Call Register (GCR):** functionality in the network containing the group call attributes + +**group call serving MSC:** In a RANflex configuration the group call serving MSC of a location area is a group call anchor MSC or a group call relay MSC that controls the group call signalling for this location area. A location area within the pool area has a unique group call serving MSC, or - in a RANflex configuration with group call redundancy - a unique group call serving MSC redundancy pool. For a given group call at any location, the group call serving MSC is either the anchor MSC or one of the relay MSCs controlling the group call. For a service subscriber located in this location area the visited MSC may be different from the location area's group call serving MSC. + +In a RANflex configuration all location areas within a BSC service area are assigned to the same group call serving MSC. + +In a RANflex configuration with group call redundancy all location areas within a BSC service area are assigned to the same group call serving MSC redundancy pool. + +**group call serving MSC redundancy pool:** A pool of group call serving MSCs each of which can take the same role for a given group call (anchor /relay) and serve the same location areas within a RANflex pool area with group call services. For a given voice group call a location area's group call serving MSC redundancy pool is either the group call anchor MSC redundancy pool or one of the group call relay MSC redundancy pools. + +**group call anchor MSC redundancy pool:** A group call serving MSC redundancy pool. Each MSC within the group call anchor MSC redundancy pool can take the role of the group call anchor MSC for a given group call. For a given instance of a voice group call one group call anchor MSC is selected from the group call anchor MSC redundancy pool. + +**group call relay MSC redundancy pool:** A group call serving MSC redundancy pool. Each MSC within the group call relay MSC redundancy pool can take the role of the group call relay MSC for a given group call. For a given instance of a voice group call one group call relay MSC is selected from every relevant group call relay MSC redundancy pool. + +**group members:** service subscribers entitled to belong to a particular group classified by a certain group identification (group ID) + +**group mode dedicated channel:** In this mode, a mobile station participating in an ongoing voice group call is allocated at least two dedicated channels, only one of them being a SACCH + +**notification:** notifications are given on common control channels or dedicated channels in order to inform group members which are either in idle mode or in dedicated mode or participating in a voice group call or voice broadcast call on the existence of voice group calls + +**Notification CHannel (NCH):** common control channel on which the notifications are sent by the network (equivalent to a paging channel) + +**originator-to-dispatcher information:** information sent by the service subscriber originating a voice group call to the network during call setup for distribution to the dispatchers to be attached to the group call during call setup + +**RANflex configuration:** A network configuration that allows a location area to be served by multiple MSCs in parallel. For details see 3GPP TS 23.236 [17]. In a RANflex configuration a given location area is associated with a single group call serving MSC. There is no support of group call redundancy. + +**RANflex configuration with group call redundancy:** A RANflex configuration where a given location area is associated with a group call serving MSC redundancy pool (instead of with a single group call serving MSC). For a given voice group call a location area's group call serving MSC redundancy pool may be a group call anchor MSC redundancy pool or a group call relay MSC redundancy pool. + +**voice group call channel:** combined uplink/downlink to be allocated in a cell of the group call area for a particular voice group call + +The uplink can be used by the presently talking service subscriber only. All mobile stations of the listening service subscribers in one cell shall listen to the common downlink. + +**voice group call member:** any group member or dispatcher participating in an on going voice group call + +**point-to-point short message:** information that may be transferred between a mobile station and a Service Center + +**time-critical application-specific data:** application-specific data which shall be transferred within the time limitation specified in 3GPP TS 42.068. + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 24.008 [7] apply. + +**dedicated mode** + +**group receive mode** + +**group transmit mode** + +## 3.2 Abbreviations + +For the purpose of the present document, the abbreviations given in 3GPP TR 21.905 [1a] and the following apply: + +| | | +|-------|-------------------------------------------------| +| AMR | Adaptive Multi-Rate | +| CC | Country Code | +| D-ATT | Downlink Attach | +| DA | Downlink Attach | +| DRX | Discontinuous reception | +| DTMF | Dual Tone Multi Frequency | +| EFR | Enhanced Full Rate | +| eMLPP | enhanced Multi-Level Precedence and Pre-emption | +| GCA | Group Call Attributes | +| GCR | Group Call Register | +| NCH | Notification Channel | +| NDC | National Destination Code | +| SN | Subscriber Number | +| UA | Uplink Attach | +| VBS | Voice Broadcast Service | +| VGCS | Voice Group Call Service | + +# --- 4 Main concepts + +## 4.1 Group definition + +Service subscribers can become group members on a PLMN wide basis to one or more groups pre-defined in the network by a corresponding group identification (group ID). The membership enables them to initiate or receive voice group calls associated with that group ID. Certain dispatchers connected to external networks also require the capability to initiate or receive voice group calls. + +A prefix can be used together with the group ID to define a subset of the group members and to restrict the group of service subscribers able to receive a voice group call to this subset. + +In addition to subscriber details in the HLR, it is necessary for the mobile station to be aware of its group membership by storing details on the SIM/USIM. This is required because it shall respond to notification messages which include only the group ID (i.e. no IMSI or TMSI details). + +Having become a group member, each service subscriber can set to active state or deactivate state the group ID or any one out of his several group IDs on the SIM/USIM. In active state the subscriber can initiate voice group calls to that group. When in deactivate state the subscriber can not make voice group calls to the group and the mobile station ignores any notification for that group. + +If no NCH is defined in the cell, mobiles shall assume VGCS service is not available on that cell. + +## 4.2 Group conversations + +### 4.2.1 Group call initiation + +#### 4.2.1.1 Normal operation with successful outcome + +A group call area can be restricted to a single MSC area or can exceed one MSC area. In a RANflex configuration (with or without group call redundancy) a group call area can be restricted to a single pool area or can exceed one pool area. + +A voice group call shall be initiated by a calling service subscriber by a related input function, e.g. via MMI, specifying the selected service and the group ID dialled or by a calling dispatcher by the MSISDN address (see subclause 9.2). As an option, a calling service subscriber may add a prefix to the group ID. As an option, the request of the calling service subscriber to set up a voice group call may specify information to be sent as originator-to-dispatcher information to the network; in this case the originator-to-dispatcher information is included in the signalling for call setup from the mobile station to the network. It is the responsibility of the input function to ensure that the originator-to-dispatcher information has a correct format (in particular, an allowed length). + +As a further option, the request of the calling subscriber may indicate one of the following talker priorities, listed in ascending order of talker priority: + +- normal subscriber; +- privileged subscriber; +- emergency subscriber. + +A mobile station supporting the use of talker priorities shall check with the SIM/USIM whether the subscriber is allowed to use the requested talker priority for the respective group ID before signalling the talker priority to the network. + +On reception of a VGCS setup request with a talker priority different from "normal subscriber", the MSC shall check with the VLR whether the subscriber has a subscription to use this talker priority. If the subscriber is not allowed to use the requested talker priority, the MSC shall reduce the talker priority to a value the subscriber is allowed to use. In any case the talker priority used by the MSC shall be signalled back to the calling service subscriber in the Connect message. + +If a VGCS setup request with talker priority "emergency subscriber" is received by the network and the subscription check is successful, the network shall set the emergency mode for this voice group call. The emergency mode may be reset during the voice group call (see subclause 4.2.2.1). + +If a prefix is added to the group ID, the MSC shall ignore the prefix when performing the subscription check. + +The MSC in which a voice group call is initiated obtains the group call attributes by requesting the Group Call Register (GCR, see clause 5). Without a RANflex configuration or in a RANflex configuration (with or without group call redundancy), if visited MSC and group call serving MSC are identical, the MSC performs a local GCR interrogation. + +The local GCR interrogation after call initiation also determines whether the MSC shall act as anchor or as relay MSC. If the MSC is not the anchor MSC then the call will be "forwarded" from the relay to the respective anchor MSC (information also delivered by GCR) and further "call-establishment" is done by the anchor MSC as described in the following. + +In a RANflex configuration the VMSC in which a voice group call is initiated may be different from the group call serving MSC of the voice group call initiating subscriber's location area. In this case the VMSC derives the identity of + +the group call serving MSC from the initiating subscriber's LAC and requests the group call anchor MSC address from the group call serving MSC by means of the SEND\_GROUP\_CALL\_INFO MAP service. The call is then "forwarded" from the VMSC to the anchor MSC and further "call-establishment" is done by the anchor MSC as described in the following. + +In a RANflex configuration with group call redundancy the VMSC in which a voice group call is initiated may not belong to the group call serving MSC redundancy pool of the voice group call initiating subscriber's location area. In this case the VMSC derives the identity of the group call serving MSC redundancy pool from the initiating subscriber's LAC and requests the group call anchor MSC redundancy pool address from the group call serving MSC by means of the SEND\_GROUP\_CALL\_INFO MAP service. The call is then "forwarded" from the VMSC to the anchor MSC redundancy pool and further "call-establishment" is done by the selected anchor MSC as described in the following. + +When a calling service subscriber or calling dispatcher initiates a voice group call, one voice group call channel shall be established in each cell of the group call area and notifications for that call shall be sent in each of these cells. As an alternative, voice group call channels may only be established in cells in reaction to responses received from mobile stations on the notifications using notification response procedure. At the same time standard connections to dispatchers in the mobile network or in an external network shall be established. If originator-to-dispatcher information has been received in the signalling for call setup from the mobile station to the network and if the originating MSC supports processing of originator-to-dispatcher information, this information is transformed into user-to-user information and sent to the dispatchers as UUS1 when setting up the standard connections. + +A voice group call channel shall consist of a combined uplink/downlink. The uplink will be used exclusively by the presently talking service subscriber. All mobile stations of the listening service subscribers in one cell shall only listen to the same common downlink. + +During call establishment there are different options for the network to allocate a speech channel for the calling service subscriber: + +In the first option, the calling service subscriber shall have its dedicated standard connection during call establishment and for the first period when he will be the talking service subscriber up to the time when the network decides that he shall join the voice group call channel. The mobile station of the calling service subscriber shall then go to the voice group call channel and the dedicated standard connection shall be released. + +In the second option, the network shall allocate a dedicated signalling channel (e.g. SDCCH) to be used by the mobile station up to the time when the voice group call channel in the originating cell is established and the network decides that the mobile station shall join the voice group call channel. + +Only one voice group call channel shall be established in each cell for any given voice group call, although there may be a number of simultaneous voice group calls within the same cell. + +Destination service subscribers shall be notified on the voice group call in each cell. These voice group call notification messages shall be broadcast on the Notification CHannel (NCH). + +The notification messages use the group ID rather than individual TMSIs/IMSIs. If the length of the group ID is less than 8 decimal digits, then the group call area ID is used in order to enable a resolution in the case of overlapping group call areas. A service subscriber's mobile station needs to be able to recognise notification messages for those group IDs subscribed to and presently activated. If the mobile station supports the use of prefixes with group IDs and has stored prefixes for a group ID, it shall take these prefixes into account following detection of a match of the group ID. + +The network may also send messages on appropriate voice group call channel FACCHs, in order to notify group call members who may participate in other voice group calls. In addition, also paging information messages for standard calls may be sent in order to inform group call members on actually paged point-to-point calls. + +Further the network may provide notification on the voice group call to service subscribers who have subscribed to the paged group ID and which are in dedicated mode. The process of broadcasting messages on NCHs is to be carried out throughout the call in order to provide the "late entry" facility whereby group members entering the area can join the call. + +If the emergency mode is set for a voice group call, the network shall include an emergency mode indication in the voice group call notification messages sent on the NCH, the group call channel FACCHs of all other ongoing voice group calls, voice broadcast calls, and the FACCHs associated with dedicated channels. + +On receiving notification of a voice group call a group call member's mobile station shall adjust to the nominated channel to receive the voice group call if this channel was described in the notification message and receive the information on the downlink. Whilst receiving, the mobile station shall not transmit on the uplink SACCH. This group receive mode is different to the normal idle mode or dedicated mode. If no channel description was provided in the notification message, the mobile station shall establish a dedicated connection by use of the notification response procedure in order to respond to the notification. The network may then provide the mobile station with a channel description for the voice group call. + +As a further mobile station option, the mobile station may read its paging subchannel in the current cell while in group receive mode or in group transmit mode in order to receive paging messages for mobile terminated calls. + +#### 4.2.1.2 Exceptional procedures + +Completion of links into congested cells where pre-emption did not occur is required. + +On receiving details of a voice group call the user may choose to move to the notified call or the mobile station may automatically move to the notified call if the new call is of higher priority than the existing call and automatic acceptance applies for this priority level. + +### 4.2.2 On-going group calls + +#### 4.2.2.1 Normal operation with successful outcome + +Within each voice group call starting from the instant where the calling service subscriber first becomes a listening service subscriber, one service subscriber has the access at any one time to the uplink of the voice group call channel and his speech is then broadcast on all voice group call channel downlinks accordingly. The mobile station of the talking service subscriber who uses the uplink of the voice group call channel can be commanded by the network to mute or unmute the downlink of the voice group channel when needed. The mobile station is commanded: + +- to mute the downlink in order to avoid non intelligible echoes (in this case, the talking service subscriber can not hear dispatcher's voice); and +- to unmute the downlink in order to hear dispatcher's voice . + +DTMF shall be used by dispatchers to trigger network signalling to mute and un-mute the downlink of a talking service subscriber as described in subclause 11.3.7.2. + +If more than one service subscriber applies for the uplink, contention resolution shall be performed in the network. Contention resolution shall be performed in the group call anchor MSC. + +Additionally, in order to speed up the uplink access procedure, the BSS may grant the uplink prior to contention resolution being performed by the group call anchor MSC. This would mean that more than one service subscriber may access to the uplink and the respective speech may be combined in the group call bridge and broadcast onto all voice group call downlink channels during a transitional period. The anchor MSC shall then select one of the talking subscribers and pre-empt the uplink use of the other talking subscribers. + +Dispatchers' voice involved shall be broadcast on the voice group call channel downlink at any time. Mobile dispatchers are provided with a standard link and thus with a dedicated permanent uplink different from the voice group call channel. + +All non-dispatcher group call members are provided with an indication on the voice group call channel of whether the uplink is in use. If a network supports the use of talker priorities, it shall indicate the talker priority of the current talking service subscriber together with this uplink busy indication, and repeat the uplink busy indication periodically. When the uplink is not in use, any non-dispatcher group call member can request access to the uplink. Any speech from dispatchers is combined with any speech from a talking service subscriber. + +The talker priorities specified in subclause 4.2.1.1 can be included by the mobile station in the uplink access message or priority uplink request message and used by the network to prioritize between different uplink requests or between an uplink request and the priority of the current talker. A mobile station shall not include a talker priority different from + +"normal subscriber" in the uplink access message and shall not send a priority uplink request message, if the network has indicated in the uplink busy message that talker priorities are not supported. + +An uplink request with talker priority "normal subscriber" is signalled as an uplink request without talker priority. + +If a subscriber requests for the uplink while the uplink is in use, a mobile station supporting the use of talker priorities shall signal the request to the network only if: + +- the subscriber is allowed to use the requested talker priority for the respective group ID; +- the network supports the use of talker priorities. The mobile station shall assume that the network supports talker priorities, until the mobile station receives an uplink busy indication containing no talker priority information; and +- the requested talker priority is higher than the talker priority of the current talking service subscriber. The mobile station shall consider the talker priority of the current talking service subscriber to be "normal subscriber", until it receives an uplink busy indication indicating the actual talker priority. + +If the BSS receives an uplink access message with a talker priority different from "normal subscriber", a BSS supporting the use of talker priorities shall delay the sending of the uplink request message to the MSC, until the MS identity, IMSI or TMSI, is received from the MS with the subsequent layer 3 message talker indication. The BSS shall then include in the uplink request message the layer 3 message, the requested talker priority, and the cell identity of the cell where the uplink access message was received. + +If the BSS receives a layer 3 message priority uplink request, it shall include the MS identity received from the MS in the uplink request message. The BSS shall also include, in the uplink request message, the requested talker priority and the cell identity of the cell where the priority uplink request message was received. + +The BSS shall send the uplink request message to the MSC only if the uplink is free or if the talker priority included in the uplink access is higher than the talker priority of the current talking service subscriber. If the layer 3 message is transmitted in the uplink request message, the BSS may omit the sending of the uplink request confirm message. + +In a RANflex configuration (with or without group call redundancy), if the group call serving MSC receives an uplink request message it shall check by analysing the NRI of the requesting subscriber's TMSI whether it is the requesting subscriber's VMSC. If it is not, the group call serving MSC shall retrieve the IMSI and information about subscribed talker priorities from the VLR of the VMSC by means of the MAP service SEND\_GROUP\_CALL\_INFO. During this MAP operation the VMSC shall check the subscription for the group ID. + +In any configuration, if the MSC receives a talker request with a talker priority different from "normal subscriber" from the BSS, the MSC shall check whether the subscriber has a subscription to use this priority: + +- if the subscriber is allowed to use the requested priority, the network shall disconnect the uplink allocated to the current talking service subscriber and assign the uplink to the requesting service subscriber; +- otherwise, the network shall reject the uplink request with cause value "requested option not authorized". + +If a talker request with talker priority "emergency subscriber" is received from a subscriber who has a subscription to use this priority, the network shall additionally set the emergency mode and signal the emergency mode indication + +- to the listeners of the group call, and +- to the other group members in the group call area with the group ID active, regardless whether they are in idle mode or dedicated mode, or participate in a different group call, + +until the emergency mode is reset by a subscriber with a specific subscription to do this. If the uplink is busy then the indication to the listeners shall be given periodically every T1 seconds. The emergency mode indication has no influence on the talker priority handling. + +If a subscriber requests to reset of the emergency mode, a mobile station supporting the use of talker priorities shall send an uplink access message or priority uplink request message indicating "emergency mode reset request" only if + +- the subscriber has a subscription for this request for the respective group ID; and +- the network indicates that the emergency mode is set. + +If the BSS receives an uplink access message with an "emergency mode reset request", a BSS supporting the use of talker priorities shall wait until the MS provides the MS identity, IMSI or TMSI, with the subsequent layer 3 message talker indication. Then the BSS shall send an emergency reset indication to the MSC including the layer 3 message and the cell identity of the cell where the uplink access message was received. + +If the BSS receives a layer 3 message priority uplink request, it shall include the MS identity received from the MS in the emergency reset indication. The BSS shall also include, in the emergency reset indication message, the cell identity of the cell where the priority uplink request message was received. + +If the MSC receives an emergency reset indication from the BSS, the MSC shall check whether the subscriber has a subscription for this request. If so, the network shall: + +- stop sending the emergency mode indication; and +- set the talker priority to "normal subscriber", if the uplink status is uplink busy with talker priority "emergency subscriber". + +If the subscriber has no subscription for the request or if the emergency mode is not set, then the MSC shall discard the request. + +The receipt of an "emergency mode reset request" does not trigger a talker change. + +If more than one service subscriber applies for the uplink, the one with the highest talker priority shall be accepted. An uplink access message or priority uplink request message with an "emergency mode reset request" shall be treated with higher priority than any uplink request with talker priority "normal subscriber", "privileged subscriber" or "emergency subscriber". If several requests with the same highest priority are received, contention resolution between these requests shall be performed in the network. For the ranking of uplink access messages by the BSC, if the network additionally supports the transfer of time-critical application-specific data, see subclause 4.2.8.2.2 a. + +Contention resolution shall be performed by the BSC, relay MSC or anchor MSC which is the first to detect that more than one request with the same highest priority was received. An MSC performing contention resolution shall select the service subscriber whose request was received first by the MSC and pre-empt the uplink use of the other service subscribers. For contention resolution performed by the BSC see subclause 11.3.7.1. + +Mobile stations shall support the reception of additional information related to the current talking service subscriber. The transmission of additional information is optional for the network. If additional information is provided, then it is periodically repeated by the network as long as the current talking service subscriber keeps the uplink. The additional information consists of a string of up to 17 octets and is stored in the HLR as part of the subscription data of the subscriber. The contents and the encoding of the additional information is operator specific. + +The release of the uplink is triggered by the user and indicated by the mobile station to the network. The network shall then indicate to the listening mobile stations that the uplink is free. + +Mobile stations in group receive mode use the group receive mode procedure (see 3GPP TS 43.022) to "camp-on" in a new cell to be able to listen to the group call channel. The mobile station may find the voice group call channel details of a new cell on the related NCH. + +A network may decide not to establish voice group call channels in all cells. Instead, notifications containing no channel description may be provided. If a mobile station moves to such a cell, it must establish a dedicated connection and respond to the notification by use of the notification response procedure in order to receive the voice group call. The network may then establish a voice group call channel and inform the mobile station on the channel position. + +If the uplink reply procedure is applicable for the voice group call, the network may obtain knowledge on whether mobile stations are listening in a cell by sending an uplink access request (perform uplink reply procedure) in an uplink free message on the voice group call channel downlink when no talking service subscriber is present in the cell. Mobile stations receiving such a request shall use uplink reply procedure and send uplink access bursts on the voice group call channel uplink with the establishment cause "reply on uplink access request". If no uplink access bursts are received by the network, the network may decide to release the voice group call channel in that cell and then provide notifications containing no channel description. + +**NOTE:** Concerning security aspects, whilst authentication and membership checking of mobile call originators and of mobile uplink users can be carried out, it is not possible to authenticate service subscribers in group receive mode if they have not before established a dedicated connection to respond to a notification. No equivalent of a group "TMSI" is provided to protect the "identity" of established voice group calls. + +The network may decide to reconfigure an existing voice group call's physical channel configuration, frequencies and/or hopping sequences as well as the cell channel description. For the cell in which the group call is being reconfigured, the network informs any listeners in group receive mode and any talker in group transmit mode of the change in VGCS channel description by using the VGCS reconfiguration procedure (see 3GPP TS 44.018 [5]). Mobile stations on receipt of the VBS/VGCS reconfiguration messages shall remain on the existing group channel until indicated starting time and then apply the new configuration to the VGCS call that the mobile station is currently involved in. + +#### 4.2.2.2 Exceptional procedures + +When a talking subscriber's mobile station loses contact with the network, the network must detect this loss and set the uplink free so that other mobile stations may access the uplink. The talking subscriber's mobile station which has lost the contact with the network shall return immediately to the group receive mode. + +If a mobile station in group receive mode indicates a failure due to radio link time-out, the mobile station shall behave as specified in 3GPP TS 45.008 and go back to idle mode, possibly in another cell, as determined by the cell re-selection algorithm. If a notification is received for the same call, the mobile station shall try to reconnect. + +### 4.2.3 Leaving of a group call without termination + +A service subscriber can leave the voice group call at any point by "deselecting" it via an MMI function. Having deselected the voice group call the mobile station returns to idle mode and "ignores" any further notification messages related to that voice group call. + +NOTE: If a service subscriber does not wish to participate in calls to a particular group ID for long periods of time, the group ID shall be switched to deactive state by the subscriber. + +The service subscriber shall have the capability to reselect the voice group call. The mobile station shall not ignore notification messages to that call any more. + +The dispatcher shall be able to leave a voice group call without terminating it. + +### 4.2.4 Group call termination + +A voice group call can only be terminated by the calling service subscriber, by calling dispatcher, by an entitled dispatcher or due to no activity timer expiry (see subclauses 8.1.2.3 and 11.3.2.3). + +The calling service subscriber can terminate the call only if he has access to the uplink. He shall remain the calling service subscriber during the length of the particular voice group call even if he leaves the call and then returns to it later. + +An entitled dispatcher can terminate the call at any time by using a network defined user operation (via DTMF). + +### 4.2.5 Acknowledgements + +The acknowledgement is an application option. + +For voice group calls which are identified by an acknowledgement flag mobile stations which have acknowledgement facilities have to return an acknowledgement message with a predefined content in a predefined manner. + +The acknowledgement shall be sent using an appropriate data service, to a predefined address or with a predefined short code stored on the SIM/USIM card. The network may apply geographical routing to a predefined acknowledgement service centre. + +### 4.2.6 Transactions between the mobile station and the network + +Mobile stations which are in group receive mode may support the reception of short messages to voice group calls, but shall not perform any other transactions with the network while adjusted to the voice group call channel. They shall leave the group receive mode and act in a standard way to perform any transaction if necessary and return to the voice group call afterwards. + +Mobile stations which have access to the voice group call channel uplink shall not perform any transactions for supplementary services, but may support the transmission and reception of short messages as specified in subclause 11.3.9. + +### 4.2.7 Processing of originator-to-dispatcher information + +The calling service subscriber may include originator-to-dispatcher information during call setup. If the originating MSC supports processing of originator-to-dispatcher information, it transforms the received originator-to-dispatcher information into UUS1, and sends it: + +- if the originating MSC is not the voice group call anchor MSC: to the voice group call anchor MSC; +- if the originating MSC is the voice group call anchor MSC: to the dispatchers to be attached to the group call during call setup of the connections to these dispatchers. + +The anchor MSC receiving UUS1 in a voice group call setup from an originating relay MSC forwards this UUS1 to the dispatchers to be attached to the group call during call setup of the connections to these dispatchers. + +**Transformation of originator-to-dispatcher information:** Originator-to-dispatcher information can be compressed or uncompressed. + +- Decompression of compressed originator-to-dispatcher information is specified in 3GPP TS 44.068. +- The transformation of uncompressed originator-to-dispatcher information into UUS1 is the UUS1 containing the same user-user IE as the originator-to-dispatcher information. +- The transformation of compressed originator-to-dispatcher information into UUS1 is the UUS1 resulting from transforming the decompressed originator-to-dispatcher information into UUS1. + +### 4.2.8 Transfer of application-specific data to group call members + +#### 4.2.8.1 General + +Mobile stations may support the transmission of application-specific data to other group call members or VGCS applications in the network, and the reception of application-specific data from other group call members or VGCS applications in the network during an ongoing voice group call, in parallel to the voice conversation. + +Service subscribers can request the transmission of application-specific data while they are talker or listener. + +**Editor's note:** The transmission and reception of application-specific data by dispatchers is ffs. + +A mobile station supporting the transmission of application-specific data shall check with the USIM whether the subscriber is allowed to transmit application-specific data for the respective group ID before starting the signalling procedures specified in subclause 4.2.8. + +The procedure specified in the following subclauses supports the transfer of application-specific data. + +The same procedure can also be used by the receiver of application-specific data to confirm the reception of application-specific data. + +**NOTE:** For the exact upper limit of application-specific data that can be sent in a single transmission see 3GPP TS 44.018 [5]. The upper limit will be chosen so that the application-specific data together with the necessary control information fit into a single SABM frame. + +The support of the transfer of application-specific data by the network is an operator option. + +The exact format of the application-specific data is out of scope of the 3GPP specifications. If roaming service subscribers from other PLMNs are to be supported or if a group call area includes cells from more than one PLMN, the use of application-specific data requires coordination between the operators. + +#### 4.2.8.2 Sending of application-specific data + +##### 4.2.8.2.1 By the talking service subscriber + +When application-specific data is to be sent and the talking subscriber is allowed to transmit application-specific data for the respective group ID, the mobile station of the talking service subscriber shall send a DATA INDICATION (Application\_Data) message to the network on the uplink of the dedicated channel or group call channel. On receipt of the application-specific data, the network shall transmit these data to the other group call members as specified in subclause 4.2.8.4. + +NOTE: If the talker has to release the uplink before sending application-specific data, the MS follows the procedures specified in subclause 4.2.8.2.2. + +##### 4.2.8.2.2 By a listener + +When application-specific data is to be sent and the network indicates the uplink as free, the listener shall use the group call channel uplink for the signalling as specified in item a) below. + +Otherwise, when the network does not indicate the uplink as free, the channel to be used by the listener is indicated by the network in the "uplink access indication" IE sent in periodic transmissions of the UPLINK BUSY message. If the talking service subscriber uses the group call channel uplink in the current cell, the RACH shall be used, see item b) below; otherwise the group call channel uplink shall be used, see item a) below. + +###### a) Sending application-specific data via the group call channel uplink + +When application-specific data is to be sent and the listener is allowed to transmit application-specific data for the respective group ID, the mobile station of the listener shall send an UPLINK ACCESS message with an appropriate establishment cause ("UL request for sending application-specific data") on the group call channel uplink to the BSS. + +It is an operator option whether the BSS treats an UPLINK ACCESS message with establishment cause "UL request for sending application-specific data" with higher or lower priority than UPLINK ACCESS messages with any other establishment cause. The same order of priorities applies to all voice group calls in a network. If the BSS grants the uplink of the group call channel, then the MS sends a SABM (DATA INDICATION) message with its mobile identity and the application data to the network. The serving BSS responds with a UA (DATA INDICATION) message and releases the group call channel uplink. The MS returns to group receive mode. + +On receipt of the DATA INDICATION message, the BSC shall add the cell identifier of the cell where the application data were sent from and passes the L3 information by sending the UPLINK APPLICATION DATA message to the MSC. + +On receipt the UPLINK APPLICATION DATA message, the MSC shall distribute the data to all members of the group call (see subclause 4.2.8.4). + +NOTE 1: Procedure a) is used to achieve the transfer time target for time-critical data. If all MSCs and BSCs involved in the voice group call support the feature "talker channel parameter", the "talker channel parameter" can be used to ensure that the voice group call channel uplink is available for the uplink access and the transmission of time-critical application-specific data. + +NOTE 2: In a network that is intended to support the transfer of time-critical data, the BSS will usually be configured to treat an uplink request for sending application-specific data with higher priority than any other uplink requests. + +###### b) Sending application-specific data via the RACH + +When application-specific data is to be sent and the listener is allowed to transmit application-specific data for the respective group ID, the mobile station of the listener shall leave the group call and send a CHANNEL REQUEST message with an appropriate establishment cause on the RACH to the BSS in order to request an SDCCH. When a new layer 2 connection is established on a SDCCH channel the data can be sent by the mobile station to the network with the DATA INDICATION 2 message on the main DCCH (figure 7j). + +In order to indicate to the network which group call the application-specific data is addressed to, the DATA INDICATION 2 message shall include the group call reference. + +On receipt of the DATA INDICATION 2 message the BSC shall add the cell identifier of the cell from which the application data was sent and pass the L3 information in the UPLINK APPLICATION DATA message to the MSC. + +On receipt of the UPLINK APPLICATION DATA message, the MSC shall distribute the data to all members of the group call (see subclause 4.2.8.4). + +#### 4.2.8.3 Sending a confirmation of receipt of application-specific data + +On receiving application-specific data, any service subscriber can send a confirmation to the network which will send the confirmation to the ongoing group call. + +For the purpose of identifying the received data, the confirmation shall include the data\_id which was received in the message that contained the application data that is being confirmed. + +The further proceeding is as described in 4.2.8.2.1 and 4.2.8.2.2 (see also figure 7i). + +#### 4.2.8.4 Distributing application-specific data to a voice group call + +##### 4.2.8.4.1 Distribution via the MSC + +On receipt of the UPLINK APPLICATION DATA, the MSC shall check if the sending subscriber has a subscription to the group ID. If yes, the MSC shall distribute the application-specific data dependent on the distribution parameter included in the DATA INDICATION or DATA INDICATION 2 message; otherwise the MSC shall discard the UPLINK APPLICATION DATA message. + +Without a RANflex configuration, the MSC can perform this check locally with its own VLR. In a RANflex configuration with or without group call redundancy, if the group call serving MSC receives an UPLINK APPLICATION DATA message it shall check by analysing the NRI of the requesting subscriber's IMSI whether it is the requesting subscriber's VMSC. If it is not, the group call serving MSC shall retrieve the IMSI and information about subscribed talker priorities from the VLR of the VMSC by means of the MAP service SEND\_GROUP\_CALL\_INFO. During this MAP operation the VMSC shall check the subscription for the group ID. + +If the application-specific data are to be sent to the listeners and the talking service subscriber, the MSC shall proceed as follows: + +If the MSC is the anchor MSC, it shall put the application data and optionally the mobile subscriber's MSISDN into the BSSMAP message NOTIFICATION DATA and distribute the message towards all relay MSCs and all BSSs in its MSC area involved in the group call (figure 7f). If the MSC receives an indication from the originating BSC that the application-specific data were immediately distributed to the originating BSS area (see subclause 4.2.8.4.2), the MSC shall not send the BSSMAP message NOTIFICATION DATA to the originating BSS. + +If the MSC is a relay MSC, it shall put the application data and optionally the mobile subscriber's MSISDN into the BSSMAP message NOTIFICATION DATA and distribute the message to the anchor MSC and all BSSs of the relay MSC area. If the MSC receives an indication from the originating BSC that the application-specific data were immediately distributed to the originating BSS area (see subclause 4.2.8.4.2), the MSC shall not send the BSSMAP message NOTIFICATION DATA to the originating BSS. On receiving the NOTIFICATION DATA message from the relay MSC, the anchor MSC shall send the message towards all BSSs in its MSC area involved in the group call and to all relay MSCs except the relay MSC from which the NOTIFICATION DATA was received (figure 7h). The BSS shall broadcast the notification data to all listeners and talking service subscriber in the NOTIFICATION APPLICATION DATA message on the FACCH. + +The network may repeat the NOTIFY APPLICATION DATA message for application-specific data on the group call channel downlink. If a mobile station receives the NOTIFY APPLICATION DATA message more than once, it shall deliver only the first received message to its local application and discard any received repetitions of the message. + +The mechanism how the mobile station detects a repetition of the NOTIFY APPLICATION DATA message is application-specific. + +**Editor's note: The sending of application-specific data to other destinations (e.g. dispatchers or applications) is ffs.** + +##### 4.2.8.4.2 Immediate distribution by the BSC + +As a network option, on receipt of application-specific data from the MS, the BSS may distribute the application-specific data immediately to the cells within the BSC area belonging to the group call area, if the distribution parameter included in the DATA INDICATION message or DATA INDICATION 2 message indicates that the application-specific data are to be sent to the service subscribers. In addition, the BSC shall send the application-specific data to the MSC with an indication that the application-specific data were already distributed to the originating BSC area. + +When this network option is used, the BSS cannot include the mobile subscriber's MSISDN in the NOTIFY APPLICATION DATA message broadcast immediately to the cells within the BSC area. Furthermore, the BSS cannot check if the sending subscriber has a subscription for the group ID. + +If the network option of immediate distribution of application-specific data by the BSS is activated, then during the establishment phase of the voice group call the BSC shall store the cell identities of the cells belonging to the group call area and served by the BSC. + +NOTE: If this option is activated no subscription check by the MSC is possible. It is also not possible to include the mobile subscriber's MSISDN in the NOTIFY APPLICATION DATA message. + +# 5 General architecture + +## 5.1 Group Call Register (GCR) + +The general architecture of GSM is maintained. In addition, a network function is required which is used for registration of the group call attributes, the Group Call Register (GCR). + +The GCR function is mainly a database function, holding information about voice group calls. + +NOTE 1: The GCR implementation is not specified. It may be realized e.g. as a new network node, in a PABX directly attached to an MSC, inside an MSC or as an HLR. The interface between the GCR function and other functions is not specified in the GSM technical specifications. As a consequence, the functional split between MSC and GCR as developed in the present document is only indicative, and other functional splits can be implemented. + +The GCR data for a specific voice group call is set at the creation of the group call attributes, and can be subsequently modified. No support for these functions is specified in the GSM technical specifications. + +In a RANflex configuration with group call redundancy GCRs associated to MSCs belonging to the same redundancy pool need to communicate with each other by means of SYNC\_GCR messages. + +![Functional architecture diagram with a Group Call Register (GCR).](cdd4dfacab004e9979caed3fffea69e5_img.jpg) + +The diagram illustrates the functional architecture of a mobile network with a Group Call Register (GCR). At the top, an 'External' connection points to three boxes: 'HLR', 'SMS-GMSC', and 'GMSC'. Below these, the architecture consists of three levels of mobile switching centers (MSCs) and their associated visitor location registers (VLRs). +- The first level features an 'Anchor MSC' connected to a 'VLR' on its left and a 'GCR' on its right. The 'HLR' and 'SMS-GMSC' have dashed lines connecting to this 'Anchor MSC'. +- The second level features a 'Relay MSC' connected to a 'VLR' on its left and a 'GCR' on its right. This 'Relay MSC' is connected to the 'Anchor MSC' above it. The 'HLR' has a dashed line connecting to this 'Relay MSC'. +- The third level features another 'Relay MSC' connected to a 'VLR' on its left and a 'GCR' on its right. This 'Relay MSC' is connected to the 'Relay MSC' above it. The 'HLR' has a dashed line connecting to this 'Relay MSC'. +- Additionally, the 'GMSC' is connected to the 'Anchor MSC', and there is a dashed line connecting the 'GMSC' to the bottom 'Relay MSC'. +- Solid lines represent functional interfaces between VLRs and MSCs, and between MSCs and GCRs. Dashed lines represent signaling or data paths to the HLR and SMS-GMSC. + +Functional architecture diagram with a Group Call Register (GCR). + +Figure 1: Functional architecture with a Group Call Register + +![Functional architecture diagram with a Group Call Register in a RANflex configuration. The diagram shows external components (HLR, SMS-GMSC, GMSC) and internal components (Anchor MSC, Group Call Serving MSC, Relay MSC, V-MSC, GCRs) within a RANflex MSC pool. Connections include dashed lines for HLR and VLR, and solid lines for other components. A red circle encloses the internal components and is labeled 'RANflex MSC pool' at the bottom right.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +The diagram illustrates the functional architecture for a Group Call Register (GCR) in a RANflex configuration. At the top, three external components are shown: HLR, SMS-GMSC, and GMSC. Below them, a large red circle labeled "RANflex MSC pool" contains several internal components. Inside the pool, there is an Anchor MSC, a Group Call Serving MSC, a Relay MSC, and three GCRs. The Anchor MSC is connected to the GMSC and has a "Dedicated link for initial talker" to the Group Call Serving MSC. The Group Call Serving MSC is connected to the Anchor MSC and one GCR. The Relay MSC is connected to the Group Call Serving MSC and another GCR. A V-MSC is connected to the Anchor MSC and a VLR. The VLR is connected to the HLR. The HLR is connected to the SMS-GMSC. The SMS-GMSC is connected to the Anchor MSC. The GCRs are connected to the Anchor MSC, the Group Call Serving MSC, and the Relay MSC. + +Functional architecture diagram with a Group Call Register in a RANflex configuration. The diagram shows external components (HLR, SMS-GMSC, GMSC) and internal components (Anchor MSC, Group Call Serving MSC, Relay MSC, V-MSC, GCRs) within a RANflex MSC pool. Connections include dashed lines for HLR and VLR, and solid lines for other components. A red circle encloses the internal components and is labeled 'RANflex MSC pool' at the bottom right. + +Note: Figure 1a shows the configuration with only one RANflex MSC pool. Other configurations with more than one RANflex MSC pool are possible. + +**Figure 1a: Functional architecture with a Group Call Register in a RANflex configuration** + +![Functional architecture diagram showing various MSC pools (Anchor, Serving, Relay) within a RANflex MSC pool, connected to external systems like HLR, VLR, and GMSC.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +The diagram illustrates the functional architecture for group call redundancy in a RANflex configuration. At the top, an 'External' connection leads to a 'GMSC' and an 'SMS-GMSC'. Below this, a large red oval labeled 'RANflex MSC pool' contains three distinct redundancy pools: + +- Anchor MSC Redundancy Pool** (blue oval): Contains multiple 'Anchor MSC' units, each connected to a 'GCR' (Group Call Register). The 'GCR's are interconnected by dashed lines (MAP interfaces). +- Serving MSC Redundancy Pool** (green oval): Contains multiple 'Group Call Serving MSC' units, each connected to a 'GCR'. These 'GCR's are also interconnected by dashed lines. +- Relay MSC Redundancy Pool** (yellow oval): Contains multiple 'Relay MSC' units, each connected to a 'GCR'. These 'GCR's are interconnected by dashed lines. + +External connections and internal links include: + +- A dashed line (MAP interface) from the 'SMS-GMSC' to the 'Anchor MSC Redundancy Pool'. +- A thin solid line (ISUP interface) from the 'GMSC' to the 'Anchor MSC Redundancy Pool'. +- A dashed line (MAP interface) from the 'HLR' to the 'VLR'. +- A bold solid line (non-standardized protocol) between the 'VLR' and the 'V-MSC'. +- A thin solid line (ISUP interface) from the 'V-MSC' to the 'Anchor MSC Redundancy Pool', labeled 'Dedicated link for initial talker'. +- A dashed line (MAP interface) from the 'V-MSC' to the 'Serving MSC Redundancy Pool'. +- A dashed line (MAP interface) from the 'V-MSC' to the 'Relay MSC Redundancy Pool'. + +Functional architecture diagram showing various MSC pools (Anchor, Serving, Relay) within a RANflex MSC pool, connected to external systems like HLR, VLR, and GMSC. + +Note: Figure 1b shows the configuration with only one RANflex MSC pool. Other configurations with more than one RANflex MSC pool are possible. + +**Figure 1b: Functional architecture with a Group Call Register in a RANflex configuration with group call redundancy** + +Dashed lines in figure 1, figure 1a and figure 1b indicate MAP interfaces, thin solid lines indicate ISUP interfaces, bold solid lines indicate interfaces without standardized protocol. + +Lines in figure 1b ending at an MSC Redundancy Pool actually connect to the selected MSC within the redundancy pool. For MSC selection see subclause 5.3.1. + +The signalling between the entities shown in figure 1, figure 1a and figure 1b, for the two cases of service subscriber and dispatcher originated calls, shall be as defined in the following. + +**Service subscriber originated:** The service subscriber's VMSC shall perform subscription checking against VLR records. In a RANflex configuration it shall then derive from the service subscriber's current location area the address of the group call serving MSC which may be different from the VMSC. In a RANflex configuration with group call redundancy this address identifies a group call serving MSC redundancy pool. + +If one of the following configurations applies: + +- a) no RANflex configuration; +- b) in a RANflex configuration, if the VMSC is the group call serving MSC; or +- c) in a RANflex configuration with group call redundancy, if the VMSC belongs to the group call serving MSC redundancy pool, + +the VMSC shall consult its GCR to determine the group call attributes related to its MSC area and whether it is the group call anchor MSC for that voice group call. If it is not, the GCR shall provide with the group call attributes the routing information identifying the group call anchor MSC (the group call anchor MSC redundancy pool in a RANflex configuration with group call redundancy) to the originating VMSC. The originating VMSC shall then route the voice group call to the anchor MSC. + +If one of the following configurations applies: + +- d) in a RANflex configuration, if the VMSC is not the group call serving MSC; or +- e) in a RANflex configuration with group call redundancy, if the VMSC does not belong to the group call serving MSC redundancy pool, + +the VMSC shall consult the group call serving MSC by means of the MAP service SEND\_GROUP\_CALL\_INFO and retrieve the group call anchor MSC address. The originating VMSC shall then route the voice group call to the anchor MSC or the anchor MSC pool. + +If the initiation of the voice group call had specified originator-to-dispatcher information and processing of originator-to-dispatcher information is supported by the originating VMSC, the originator-to-dispatcher information is transformed by the originating VMSC into UUS1 and sent to the anchor MSC or the anchor MSC pool. If the originating VMSC is the group call anchor MSC (or belongs to the group call anchor MSC redundancy pool), along with the group call attributes, the GCR shall provide information on all group call relay MSCs or group call relay MSC pools to be involved. + +The group call anchor MSC shall set up links to all group call relay MSCs or relay MSC pools. It shall also initiate setup of point-to-point connections to the dispatchers associated to the voice group call (see subclause 8.1.2.2); if UUS1 information has been received in the signalling for call setup from the originating VMSC, this UUS1 information is included in the setup of point-to-point connections to the dispatchers. Each MSC involved in a voice group call obtains its own group call attributes from the GCR related to the MSC. + +The IMSI of the calling service subscriber must be provided to and stored in the anchor MSC and each relay MSC in order to allow the calling service subscriber to clear the group call later on. + +**Dispatcher originated:** In the case of dispatchers calling from an external network, the call request, in the form of an ISDN number, shall be received at a GMSC. The number shall be analysed and the call shall be directly routed to the group call anchor MSC or anchor MSC pool by the GMSC based on the called identity without requesting an HLR. The group call anchor MSC shall interrogate the GCR and obtain the group call attributes. If an identical voice group call is currently in progress, the dispatcher shall be connected to this call and no new call shall be initiated. When interrogating the GCR, the identity of the calling dispatcher is compared with the list of dispatchers which are allowed to initiate the call. If the dispatcher is not in the list, or an identity is not provided, the network shall reject the call. + +NOTE 2: A dispatcher may be a user of the GSM network in which the VGCS service is provided or may be connected to a PABX which is connected to the MSC containing the GCR. A dispatcher which is registered in the GCR for a certain voice group call and which also has a subscription for VGCS with the same group ID as the voice group call for which he is dispatcher shall deactivate this group ID when he is located in the corresponding group call area in order to avoid conflicts between paging for the dispatcher and notifications for the group ID. + +## 5.2 Voice group call responsibility + +The MSC responsible for the voice group call is the one nominated within the GCR or the one to which the call is routed from the GMSC in the case of a dispatcher originated call. This MSC is termed the group call anchor MSC. + +If the group call area extends beyond one MSC area then any MSCs controlling cells in the area outside of the group call anchor MSC are referred to as group call relay MSCs. + +In a RANflex configuration a given location area within the pool area is served (with group call services) by a single predefined group call serving MSC which for a specific group call is either anchor or relay MSC. + +In a RANflex configuration with group call redundancy a given location area within the pool area is served (with group call services) by predefined group call serving MSCs which form up the location area's group call serving MSC redundancy pool. One MSC shall not belong to more than one group call MSC redundancy pool. For a specific ongoing group call the group call serving redundancy pool is either an anchor or a relay redundancy pool. + +## 5.3 RANflex configuration with group call redundancy + +### 5.3.1 MSC selection in a RANflex configuration with group call redundancy + +In a RANflex configuration with group call redundancy, messages routed towards a group call MSC redundancy pool eventually need to be processed by a selected MSC out of the redundancy pool. MSC selection is done with appropriate routing mechanisms at call setup time. + +Mixed configurations where e.g. the anchor MSC belongs to an anchor MSC redundancy pool but the relay MSC does not belong to a Relay MSC redundancy pool may be considered a RANflex configuration with group call redundancy where e.g. the relay MSC redundancy pool is formed up by just one relay MSC. + +In a RANflex configuration with group call redundancy the following messages sent to an MSC do not address an individual MSC but an MSC redundancy pool: + +- IAM (from dispatcher to Anchor MSC); +- IAM (from VMSC to Anchor MSC); +- SEND\_GROUP\_CALL\_INFO (from VMSC to Group Call Serving MSC); +- PREPARE\_GROUP\_CALL (from Anchor MSC to Relay MSC); and +- MT\_FORWARD\_SM\_FOR\_VGCS (from SMS-GMSC to Anchor MSC). + +Network routing ensures that these messages are routed to one of the available (i.e. not out of service) MSCs within the redundancy pool. MSC selection by network routing can be based e.g. on a predefined prioritization mechanism or a load distribution mechanism but the exact mechanism is out of scope of this specification. + +Once the message is received by one of the available MSCs, the receiving MSC shall check whether there is the need to forward the message to another specific MSC within the redundancy pool (for detailed behaviour of the MSC see subclauses 11.4, 11.5, and 11.5A). Network routing ensures that the forwarded message is routed to the specific MSC. Specific MSC routing may be done e.g. with address prefixes and is out of scope of this specification. + +If the message forwarding MSC detects that the specific target MSC is out of service, it shall handle the request locally and repeat the GCR interrogation with an override indication. + +In a RANflex configuration with group call redundancy the following messages sent to an MSC address an individual MSC and not an MSC redundancy pool: + +- IAM (dispatcher originated) when forwarded within the group call anchor MSC redundancy pool from selected Anchor MSC to the Anchor MSC where the group call is on-going; +- IAM (VMSC originated) when forwarded within the group call anchor MSC redundancy pool from selected Anchor MSC to the Anchor MSC where the group call is on-going; +- IAM (from Anchor MSC to Relay MSC) routed with the temporary group call number allocated by the Relay MSC; +- SEND\_GROUP\_CALL\_INFO (VMSC originated) when forwarded within the group call serving MSC redundancy pool from selected group call serving MSC to the group call serving MSC where the group call is on-going; +- Subsequent messages within a dialogue opened by a PREPARE\_GROUP\_CALL message (PREPARE\_GROUP\_CALL\_ACK, SEND\_GROUP\_CALL\_END\_SIGNAL, FORWARD\_GROUP\_CALL\_SIGNALLING; PROCESS\_GROUP\_CALL\_SIGNALLING). MAP dialogue handling ensures that messages are exchanged between origin and selected destination of the dialogue; and +- MT\_FORWARD\_SM\_FOR\_VGCS (SMS-GMSC originated) when forwarded within the group call anchor MSC redundancy pool from selected Anchor MSC to the Anchor MSC where the group call is on-going. + +Network routing ensures that these messages are routed to the individual MSC within the redundancy pool. + +### 5.3.2 GCR synchronization in a RANflex configuration with group call redundancy + +GCRs associated to MSCs which belong to the same redundancy pool need to synchronize their transient data. This is done by means of SYNC\_GCR messages. As soon as transient data are modified in a GCR as a result of GCR interrogation from the associated MSC, the modification is propagated to the other GCRs. + +This mechanism prevents the establishment of two simultaneous group calls with the same group call reference controlled by two different anchor MSCs. + +### 5.3.3 GCR Restoration in a RANflex configuration with group call redundancy + +When a GCR (and its associated MSC) restarts after planned or unplanned outage, its transient data may be lost or may be out of sync due to lost SYNC\_GCR messages. To restore the transient data, the GCR shall after restart + +- stop all T3 timers; +- delete all stored initial talker information; and +- mark all GCR records with "transient data not reliable". + +When transient data are read while processing a GCR interrogation, the GCR shall check whether the record is marked "transient data not reliable". If so, the GCR shall retrieve transient data from the other GCR(s) within the redundancy pool by means of a SYNC\_GCR message with request indication, store it and reset the mark "transient data not reliable" before processing the GCR interrogation. If the retrieval of transient data is unsuccessful, the GCR shall assume that the call is not on-going, reset the mark "transient data not reliable" and process the GCR interrogation. + +When processing a received SYNC\_GCR message without request indication while the record is marked "transient data not reliable", the GCR shall accept the request and reset the "transient data not reliable" mark. + +When processing a received SYNC\_GCR message with request indication while the record is marked "transient data not reliable", the GCR shall return a negative response (failure) and keep the "transient data not reliable" mark. + +# --- 6 Compatibility issues + +VGCS can not be used with standard Phase 1 or Phase 2 mobile stations. A dedicated mobile station with VGCS capability is required. + +A mobile station with VGCS capability shall also provide the complete functionality in order to allow the use of Phase 2 services. + +Standard Phase 1 and Phase 2 mobile stations in a network shall not be impacted by the presence of VGCS services in that network due to VGCS signalling, also if the mobile station is operated with a SIM/USIM of a VGCS service subscriber. + +# --- 7 Transmission + +## 7.1 Transmission architecture + +A conference bridge is required to connect the transmission paths of the nominated cells. The bridge is to be located within the group call anchor MSC. + +Without a RANflex configuration: The group call anchor MSC is responsible for setting up all connections, both to the nominated cells (voice group call channels) in the group call anchor MSC and to any related group call relay MSC, and to the dispatchers. Except when a calling service subscriber, served by a relay MSC, is on the initial dedicated link, there shall be one link towards every relay MSC and a distribution function in the relay MSCs and from there one link per cell within the group call relay MSC which is involved in the voice group call. + +In a RANflex configuration: The group call anchor MSC is responsible for setting up all connections, both to those cells of the group call area that belong to a location area for which the group call anchor MSC is the group call serving MSC and to any related group call relay MSC, and to the dispatchers. Except when a calling service subscriber, served by a relay MSC, is on the initial dedicated link, there shall be one link towards every relay MSC and a distribution function in the relay MSCs and from there one link per cell of the group call area that belongs to a location area for which the group call relay MSC is the group call serving MSC which is involved in the voice group call. + +In a RANflex configuration with group call redundancy: The group call anchor MSC selected from the anchor MSC redundancy pool is responsible for setting up all connections, both to those cells of the group call area that belong to a location area for which the group call anchor MSC is the group call serving MSC and to any related group call relay MSC pool, and to the dispatchers. Except when a calling service subscriber, served by a relay MSC, is on the initial dedicated link, there shall be one link towards every relay MSC redundancy pool and a distribution function in the selected relay MSCs and from there one link per cell of the group call area that belongs to a location area for which the group call relay MSC is the group call serving MSC which is involved in the voice group call. + +For all configurations the following applies: + +While the calling service subscriber is on a dedicated link served by his VMSC, there is an additional link from the anchor MSC to the VMSC serving the calling service subscriber and an additional link from the VMSC serving the calling service subscriber to the cell serving the calling service subscriber. There shall be no secondary bridges in BSCs. + +While a talker served by a relay MSC is on any other dedicated or group channel than the initial dedicated channel, the following applies: The distribution function shall be implemented using a secondary conference bridge at the relay MSC so that VGCS talker speech sent on the current channel uplink is transmitted to local relay cells as well as being transmitted over the link back to the anchor MSC, for distribution to the rest of the network, dispatchers and nominated cells at other relay MSCs. + +The conference bridge shall not mute the uplink speech. + +### 7.1a Transmission architecture – A interface circuit sharing + +#### 7.1a.1 Transmission architecture – General + +The MSC and BSC shall negotiate during the setup of a voice group call whether A-interface circuit sharing is supported by both entities. When this optional feature is supported by both entities, the same A-interface circuit can be shared for all cells belonging to a BSC for a given voice group call. + +A conference bridge is required to connect the transmission paths of the nominated cells. The bridge is to be located within the group call anchor MSC. The group call anchor MSC is responsible for setting up all connections, both to the nominated cells (voice group call channels) in the group call anchor MSC and in any related group call relay MSC, and to the dispatchers + +The BSC contains a distribution function that distributes speech sent from the MSC to each of the nominated cells. + +#### 7.1a.2 Transmission architecture – Control Plane + +The control plane signalling shall be the same as in sub-clause 7.1. + +#### 7.1a.3 Transmission architecture – User Plane + +In the case of an originator that is not on the initial dedicated link, there shall be one link from the anchor MSC towards every relay MSC. There will be one link from each of these relay MSCs and the group call anchor MSC to each BSC controlled by the respective MSC and involved in the voice group call. Each of these BSCs contains a distribution function that distributes speech received from the MSC to each cell involved in the group call. + +When an originator, served by a relay MSC, is on the initial dedicated link, there is an additional link from the anchor MSC to the relay MSC serving the originator and an additional link from the relay MSC serving the originator to the cell serving the originator. + +When an originator, served by an anchor MSC, is on the initial dedicated link, there shall be one link from the anchor MSC towards every relay MSC. There will be one link from each of these MSCs and the group call anchor MSC to each BSC controlled by the respective MSC and involved in the voice group call. Each of these BSCs contains a distribution function, with one link to each cell and involved in the group call. There is an additional link from the anchor MSC to the cell serving the originator. + +While a talker served by an anchor MSC is on any other dedicated or group channel than the initial dedicated channel, the following distribution functions shall be implemented: + +- conference bridge at the anchor MSC so that VGCS talker speech sent on the current channel uplink is transmitted to local cells as well as being transmitted over the links to the relay MSCs, for distribution to the rest of the network, dispatchers and nominated cells at other relay MSCs; +- distribution point at the BSC so that speech sent from the MSC is distributed to each of the nominated cells. + +While a talker served by a relay MSC is on any other dedicated or group channel than the initial dedicated channel, the following distribution functions shall be implemented: + +- secondary conference bridge at the relay MSC so that VGCS talker speech sent on the current channel uplink is transmitted to local cells as well as being transmitted over the link back to the anchor MSC, for distribution to the rest of the network, dispatchers and nominated cells at other relay MSCs; +- distribution point at the BSC so that speech sent from the MSC is distributed to each of the nominated cells. + +The conference bridge shall not mute the uplink speech. + +### 7.1b Transmission architecture – A interface link sharing + +#### 7.1b.1 Transmission architecture – General + +The MSC and BSC shall negotiate during the setup of a voice group call whether A-interface link sharing is supported by both entities. When this optional feature is supported by both entities, the same A-interface link (user and control plane) can be shared for all cells belonging to a BSC for a given voice group call. + +A conference bridge is required to connect the transmission paths of the nominated cells. The bridge is to be located within the group call anchor MSC. The group call anchor MSC is responsible for setting up a single A-interface link (i.e. A-interface circuit and resource controlling SCCP connection) to each BSC containing nominated cells in the group call anchor MSC and links to any group call relay MSCs and to the dispatchers. + +Each BSC is responsible for setting up a speech and signalling connection (voice group call channel) to each nominated cell in the group call area served by this BSC. The BSC contains a distribution function that distributes speech and resource control related signalling from the MSC to each of the nominated cells. + +#### 7.1b.2 Transmission architecture – Control Plane + +The MSC shall inform the BSC of the cells required to be setup for the group call in the VGCS ASSIGNMENT REQUEST. This message shall contain the list of group call area cells served by this BSC. If the entire list of cell identifiers does not fit into the message or if different methods of radio resource allocation (e.g. "immediate allocation" or "delay allowed") are to be used for different cells controlled by the BSC, the MSC shall send one or more VGCS AREA CELL INFO messages containing the remaining cell identifiers or the cell identifiers of cells using a different method of radio resource allocation. Once a channel could be established to the cell of origin or, if the cell of origin is not served by this BSC, to any other cell, the VGCS ASSIGNMENT RESULT shall be sent to the MSC and timer Tast shall be started. Timer Tast is used to measure the duration between periodic reports from the BSC to the MSC of group call area cells for which channels have been assigned or released since the last periodic report. When timer Tast expires, if new cells in the group call area have been established or existing ones have been released, pre-empted or failed, the MSC shall be informed of the changes. If no changes have taken place nothing shall be sent. Timer Tast shall be started again to measure the period of time until the next report. The timer shall be stopped when the call is released. + +Once all cells for a given group call area served by a BSC are established this BSC shall immediately send a VGCS ASSIGNMENT\_STATUS message to the MSC indicating this and restart timer Tast. This information shall be used by the MSC to determine the conditions for call set up as described in subclause 11.3.1.1.2. + +The BSS is responsible to establish the channel to the different cells and manage the signalling accordingly (e.g. HO decisions, pre-emption, re-establishment of cells, priority uplink decision). The A-interface link (user and control plane) between MSC and BSC shall only be released when the call is released. + +When the network supports uplink access option (i) as defined in subclause 7.2 (i.e. indication in uplink busy instructs the MS to use the group call channel to send the uplink access message if the talker on the group call channel is not in the same cell as the MS) the network shall include talker priority information in all relevant A-interface messages on the resource controlling SCCP connection, to distinguish between messages related to the current talker and messages related to the subscriber requesting the uplink. + +#### 7.1b.3 Transmission architecture – User Plane + +The transmission architecture of the user plane as specified in subclause 7.1a.3 applies. + +## 7.2 Radio channels + +In each cell of the group call area one voice group call channel may be established consisting of a downlink received by all service subscribers' mobile stations and an uplink which shall be used by the talking subscriber's mobile station only. + +If the network allocates a dedicated traffic channel for the calling service subscriber, his mobile station shall use the dedicated standard uplink/downlink which is connected to the conference bridge up to the instant where the network decides that the mobile station shall join the voice group call channel and the dedicated connection is released. + +The network may decide to switch a talking subscriber's mobile station from the voice group call channel to a dedicated standard uplink/downlink at any time. The talking subscriber's voice group call channel and the dedicated channel may belong to different cells within the group call area, i.e. the network may request the talker to perform a handover. The dedicated connection shall then be maintained up to the instance where the network decides that the mobile station shall join the voice group call channel again and the dedicated connection is released. + +When the network indicates the uplink as free, the mobile station uses the group call channel uplink to signal an uplink request, "emergency mode reset request" or uplink request for sending application-specific data. + +When the network does not indicate the uplink as free, there are two options for the mobile station how to signal an uplink request with talker priority higher than "normal subscriber", an "emergency mode reset request" or an uplink request for sending application-specific data: + +- i) if the priority uplink access parameter broadcast on the NCH indicates "RACH access" but the latest UPLINK BUSY message received in the cell indicates that the group call channel uplink shall be used, the mobile station sends an uplink access message on the group call channel uplink; otherwise, the mobile station temporarily leaves the group receive mode and sends a channel request message on the RACH. Once a dedicated connection has been established by the network, the mobile station sends a layer 3 message PRIORITY UPLINK REQUEST or DATA INDICATION 2. The PRIORITY UPLINK REQUEST message contains the MS identity + +(IMSI or TMSI), the group call reference, random reference, the type of request and the token broadcast by the BSS, if the BSS broadcasts a token. On receipt of this information, the network shall release the dedicated connection, and the mobile station shall return to the group receive mode and continue to listen on the downlink of the group call channel for further instructions from the network. + +NOTE 1: The indication in uplink busy instructs the MS to use the group call channel uplink to send the uplink access message if the talker on the group call channel is not in the same cell as the MS. + +If the mobile station releases the uplink on request of the subscriber, it shall use the group call channel uplink for signalling subsequent uplink requests, until it performs a cell change or receives either an UPLINK BUSY message indicating that RACH shall be used or a VGCS UPLINK GRANT message destined for a different mobile station. + +- ii) If the priority uplink access parameter broadcast on the NCH indicates "group call channel uplink access" then the mobile station always sends an uplink access message on the group call channel uplink. If this option is used, the network shall always establish and maintain a dedicated channel for the talking service subscriber. + +NOTE 2: Otherwise, with option (ii) the BSC would not be able to detect the requests of higher privileged talkers in the cell where the current talking service subscriber is located. + +Support of both options is mandatory for a mobile station supporting the use of talker priorities or transfer of application-specific data and optional for the network. A network supporting the use of talker priorities or transfer of time-critical application-specific data shall indicate the default procedure to be used on the NCH (i.e. either "RACH access" or "group call channel uplink access"). The indication shall have the same value throughout the network. If the "talker channel parameter" is used in a network, then the value of the indication shall be set to "RACH access". + +A listening subscriber's mobile station which responds to a notification because no description of the voice group call channel was provided in the notification may be assigned a dedicated standard uplink/downlink up to the instant where the radio access network decides that the mobile station shall join the voice group call channel and the dedicated connection is released. + +Voice group call channels shall be standard full rate or half rate speech channels, EFR speech channels, full rate AMR speech or half rate AMR speech channels. The support of voice group call channels other than full rate speech is a network option. A specific voice group call can use either the same speech codec type in all cells of the group call area or different speech codec types in different cells of the group call area. Those implementations are optional for the network operator. + +When establishing an AMR half rate or AMR full rate speech channel, the BSC shall select a suitable AMR codec configuration: + +- for a dedicated channel used by a talking service subscriber, the BSC may select any configuration permitted for a point-to-point call; +- for a voice group call channel the BSC shall select one of the preferred configurations as defined in 3GPP TS 28.062 [16], Table 7.11.3.1.3-2. For the downlink the BSC shall disable the rate adaptation mechanism and apply a single codec mode until the channel is released. If the talking service subscriber uses the voice group call channel uplink and the BSC selected a multi-mode configuration, the BSC shall apply the rate adaptation mechanism for the uplink. + +Within a cell the BSC shall select the same codec configuration for all voice group and voice broadcast calls using the same AMR codec type, AMR FR or AMR HR, respectively. The selected configuration shall be broadcast on the NCH, as long as at least one voice group or voice broadcast call using the respective AMR codec type is active. + +When A-interface circuit sharing or A-interface link sharing applies there is one A-interface circuit allocated for the group call per BSC. Therefore the same speech codec is applied for all voice group channels in the part of the group call area served by one BSC if the TRAÜ is located between the MSC and the BSC-internal distribution function for speech (see subclause 7.1a.1 and 7.1b.1). + +Mobile station using the uplink are in group transmit mode. Signalling for this RR mode is specified in 3GPP TS 44.018. Mobile stations not using the uplink and not in dedicated mode shall ignore any signalling concerned only with uplink usage. + +Full standard duplex channels shall be provided to all dispatchers listed in the GCR. These may be provided either via GSM, or via an external network. The links to the dispatchers are connected to the conference bridge. + +If the mobile station of the talking service subscriber joins the voice group call channel, it will transmit on the uplink of the voice group call channel. + +## 7.3 Data confidentiality + +Data confidentiality on the radio can be provided as a network option. + +If data confidentiality is provided, both the uplink and the downlink of the voice group call channel within a cell of the group call area shall be ciphered using voice group ciphering keys derived from the same group key, see 3GPP TS 43.020 [10]. + +The group key is related to the group ID. For each group ID, there is a number of group keys stored on the USIM which are identified by a group key number. The group key number identifying the group key to be used for a particular voice group call is provided with the notification to the mobile stations. Mobile stations which have a dedicated connection shall be informed of the group key number before they join the voice group call channel. + +USIM based VGCS ciphering uses a concept of short term keys where the short term key is derived by the GCR and the USIM from the group key and a RAND (random number) parameter. The actual voice group ciphering key is then derived by the BSS and the ME from the short term key, the cell global identifier, and a Cell Global Count parameter. + +To include a subscriber into a voice group the required group data (including the 2 master group keys) shall be stored on the USIM, e.g. during the personalisation process or via OTA (over-the-air). To exclude a subscriber from a voice group the group data shall be deleted from the USIM. If a USIM is lost or stolen, all USIMs of the remaining members of the voice groups that this USIM is a member of need to be changed (e.g. via OTA or manual provisioning). + +Details on data confidentiality for voice group calls are provided in 3GPP TS 42.009 [9] and 3GPP TS 43.020 [10]. + +NOTE 1: USIM based VGCS ciphering is not compatible with SIM based VGCS ciphering which has not been completely specified. The SIM specifications contain no support for the storage of the group keys. A pre-Rel-6 VGCS capable mobile station will be able to participate in an un-ciphered group call, if it is part of that group. + +If data confidentiality is provided, then for a mobile station in group mode dedicated channel the uplink and the downlink of the dedicated channel shall be ciphered using the individual ciphering key of the service subscriber. + +NOTE 2: The individual ciphering key is the key generated during a previous authentication procedure. + +In order to start the ciphering for the calling service subscriber, the MSC serving the mobile station shall initiate a cipher mode control procedure during call setup, while the mobile station is in group mode dedicated channel. When ciphering was started successfully, the mobile station shall apply the individual ciphering key until it leaves group mode dedicated channel or a new cipher mode control procedure is performed successfully. + +In order to start the ciphering on the dedicated channel, if the network decides to move a talking subscriber's mobile station from group transmit mode to group mode dedicated channel, the network shall include cipher mode setting information in the assignment command or handover command message (see 3GPP TS 43.020 [10], Annex F 3.2). On the dedicated channel the mobile station shall apply the individual ciphering key until it leaves group mode dedicated channel or a new cipher mode control procedure is performed successfully. + +If data confidentiality is provided, then for a mobile dispatcher the uplink and the downlink of the dedicated channel shall be ciphered using the individual ciphering key of the dispatcher. + +If data confidentiality is provided, the priority uplink request procedure can be validated by a handshake between the requesting MS and the BSS. A 32 bit token is generated randomly and broadcast by the BSS on the ciphered downlink of the voice group call channel and stored in the MS. When the MS sends a priority uplink request it includes the token as a parameter and the BSS checks this against its stored value. If it matches the request is processed further. If it does not match, the request is ignored. A new token is broadcast on the ciphered downlink of the voice group call channel each time a match occurs and each time a periodic UPLINK\_BUSY message is sent (i.e. every T1 seconds) (refer to Figure 7e in section 11.3.8). + +If data confidentiality is provided for point-to-point SMS over the CS domain, the network shall broadcast an SMS data confidentiality indication in NOTIFICATION/ NCH messages, NOTIFICATION/ FACCH messages and in the Connect message sent to the calling service subscriber of a voice group call. + +If guaranteed privacy is provided for SMS over the CS domain (see 3GPP TS 42.068 [2]), the network shall broadcast an SMS guaranteed privacy indication in NOTIFICATION/ NCH messages, NOTIFICATION/ FACCH messages and in the Connect message sent to the calling service subscriber of a voice group call. + +NOTE 3: For backward compatibility with legacy networks the coding of these indications in NOTIFICATION messages is chosen so that the default settings are SMS data confidentiality = "on" and SMS guaranteed privacy = "on". + +# --- 8 Information storage + +## 8.1 Information stored in the GCR + +### 8.1.1 Information used for routing of service subscriber originated voice group calls + +Without a RANflex configuration, the GCR shall hold for a related MSC area for each group ID and cell from which voice group calls can be established by service subscribers the group call reference to be used for a voice group call to be established and an indication whether the originating MSC is the group call anchor MSC. + +In a RANflex configuration, the GCR shall hold for a related MSC area (i.e. for those location areas for which the related MSC is the group call serving MSC) for each group ID and cell (within those location areas for which the related MSC is the group call serving MSC) from which voice group calls can be established by service subscribers the group call reference to be used for a voice group call to be established and an indication whether the group call serving MSC is the group call anchor MSC. + +In a RANflex configuration with group call redundancy, the GCR shall hold for a related MSC area (i.e. for those location areas for which the related MSC belongs to the group call serving MSC redundancy pool) for each group ID and cell (within those location areas for which the related MSC can act as the group call serving MSC) from which voice group calls can be established by service subscribers the group call reference to be used for a voice group call to be established and an indication whether the group call serving MSC belongs to the group call anchor MSC redundancy pool. + +If one of the following configurations applies: + +- a) without a RANflex configuration; +- b) in a RANflex configuration, if the VMSC is the group call serving MSC; or +- c) in a RANflex configuration with group call redundancy, if the VMSC belongs to the group call serving MSC redundancy pool: + +If the VMSC is the group call anchor MSC or belongs to the group call anchor MSC redundancy pool, the GCR shall provide the group call attributes related to that group call reference as defined in subclause 8.1.2 and 8.1.3 to the VMSC and the VMSC shall establish the voice group call. + +If the VMSC is not the anchor MSC or does not belong to the group call anchor MSC redundancy pool, the GCR shall provide the group call reference plus the routing information identifying the anchor MSC or anchor MSC redundancy pool to the VMSC and the VMSC shall route the voice group call to the anchor MSC or anchor MSC redundancy pool. + +If the following configuration applies: + +- d) in a RANflex configuration, if the VMSC is different from the group call serving MSC: + +If the group call serving MSC is a relay MSC for the group call, the GCR shall provide the group call reference plus the routing information identifying the anchor MSC to the group call serving MSC which passes this information to the VMSC. + +If the group call serving MSC is the anchor MSC for the group call, the GCR shall provide the group call reference to the group call serving MSC which adds the routing information identifying the anchor MSC (i.e. its own MSC address) and passes the information to the VMSC. + +Then the VMSC shall route the voice group call to the anchor MSC. + +If the following configuration applies: + +- e) in a RANflex configuration with group call redundancy, if the VMSC does not belong to the group call serving MSC redundancy pool: + +If the group call serving MSC redundancy pool is a group call relay MSC redundancy pool for the group call, the GCR shall provide the group call reference plus the routing information identifying the anchor MSC redundancy pool to the requesting group call serving MSC which passes this information to the VMSC. + +If the group call serving MSC redundancy pool is the group call anchor MSC redundancy pool for the group call, the GCR shall provide the group call reference to the requesting group call serving MSC which adds the routing information identifying the anchor MSC redundancy pool and passes the information to the VMSC. + +Then the VMSC shall route the voice group call to the anchor MSC redundancy pool. + +In a RANflex configuration with group call redundancy, the GCR shall provide the requesting MSC with "group call ongoing information". If the group call is ongoing at another MSC within the redundancy pool, the requesting MSC shall forward the actual request to that MSC. + +NOTE: In case the GCR function is distributed over different physical entities, each may hold only the information needed to treat requests coming from the MSCs connected to the physical GCR entity. + +### 8.1.2 Static Group call attributes + +The GCR stores a list of static Group Call Attributes for a given group call reference. These lists shall be programmed by the service provider at registration of the network specific service configuration. In RANflex configurations with group call redundancy these lists shall be identical in GCRs which are associated to MSCs belonging to the same redundancy pool. + +The contents of each list related to requests of the group call anchor MSC is as follows: + +- a list of cells inside the MSC area of the group call anchor MSC (in a RANflex configuration with or without group call redundancy, the cells belonging to a location area for which the group call anchor MSC is the group call serving MSC) into which the call is to be sent (part of the group call area), see subclause 8.1.2.1; +- a list of group call relay MSCs (or group call relay MSC redundancy pools) into which the call is to be sent; +- information on the cipher algorithm and the group key to be used for this voice group call; +- information on the codecs allowed for this voice group call. As an operator option, the EFR codec, standard half rate codec, AMR half rate codec, and AMR full rate codec can be supported; + +NOTE: A pre-Rel-7 VGCS capable mobile station will not be able to participate in a group call using the EFR codec, AMR half rate codec or AMR full rate codec, if the mobile station is part of that group + +- a list of identities of dispatchers to which a dedicated link is to be established, see subclause 8.1.2.2; +- a list of identities of dispatchers which are allowed to initiate the voice group call, see subclause 8.1.2.2; +- a list of identities of dispatchers which are allowed to terminate the voice group call, see subclause 8.1.2.2; +- the length of time over which no activity is detected before the voice group call is automatically terminated, see subclause 8.1.2.3; +- the default priority level related to the voice group call if eMLPP applies, see subclause 8.1.2.4; +- a talker channel parameter indicating if the network shall always establish and maintain a dedicated channel for the talking service subscriber; +- an indication whether the uplink reply procedure is applicable for this voice group call. +- in a RANflex configuration with group call redundancy: A list of GCR addresses identifying GCRs associated to MSCs within the redundancy pool. + +The contents of each list related to requests of a group call relay MSC is as follows: + +- a list of cells inside the MSC area of the group call relay MSC (in a RANflex configuration with or without group call redundancy, cells belonging to a location area for which the requesting MSC is the group call serving MSC) into which the call is to be sent (part of the group call area), see subclause 8.1.2.1; +- identity of the group call anchor MSC (or group call anchor MSC redundancy pool); +- in a RANflex configuration with group call redundancy: A list of GCR addresses identifying GCRs associated to MSCs within the redundancy pool. + +#### 8.1.2.1 Group call area + +The group call area is defined as a list of cells. The cells shall be defined by their cell identification consisting of the Location Area Code and the Cell Identity as defined in 3GPP TS 24.008 and are therefore uniquely identified in the network. + +In the case the group call area extends over several MSCs, only the cells belonging to the requesting MSC (in a RANflex configuration and in a RANflex configuration with group call redundancy, cells belonging to location areas for which the requesting MSC is the group call serving MSC) are included in the group call attributes. + +#### 8.1.2.2 Dispatcher identities + +Dispatcher identities shall be ISDN numbers or MSISDN numbers with the structure according to ITU-T Recommendation E.164. They shall correspond both to the number to be used to establish a call toward the dispatcher and the number provided as calling line identification when the call is originated by a dispatcher. + +The list of dispatcher identities is used by the anchor MSC to establish dedicated communication paths to each dispatcher and connect them to the conference bridge of the call. + +The list of dispatcher identities which are allowed to initiate voice group calls is used by the anchor MSC for verification for a voice group call establishment by a dispatcher. + +The list of dispatcher identities which are allowed to terminate voice group calls is used by the anchor MSC for verification for a voice group call release by a dispatcher. + +#### 8.1.2.3 No activity time + +A timer in the anchor MSC used to release the voice group call because of "no activity" can be set to a fixed value or can be set to a value defined for each voice group call. + +A group call is defined to be in the state of "no activity" in the anchor MSC, if the following conditions are all fulfilled: + +- the uplink is free; +- no dispatcher is connected; +- no short message is waiting in the anchor MSC to be sent to the voice group call; and +- no application-specific data are waiting in the anchor MSC to be relayed. + +The anchor MSC shall check for the state of "no activity" if any of the following events occur: + +- an uplink release is indicated to the anchor MSC; +- a dispatcher leaves the ongoing group call; +- the anchor MSC has completed the distribution of a short message to the voice group call; or +- the anchor MSC has completed the relay of application-specific data. + +The anchor MSC has to start the "no activity" timer, when the conditions for "no activity" are all fulfilled. + +The timer shall be stopped and reset each time any of the following events occurs: + +- an uplink request is indicated to the anchor MSC; + +- a dispatcher joins the ongoing group call; +- a short message to the voice group call is received by the anchor MSC; or +- application-specific data are received by the anchor MSC. + +When a variable timer is provided, there shall be sufficient timers such that one can be associated with each on-going group call. The corresponding time shall be stored in the GCR. + +The length of the timer is not specified in the GSM technical specifications. + +#### 8.1.2.4 Priorities + +If the eMLPP supplementary service is applied to a voice group call, the priority level shall be stored in the GCR. For further details see 3GPP TS 23.067. + +### 8.1.3 Transient Group Call Attributes + +#### 8.1.3.0 General + +The GCR stores transient data for a given group call reference. These data are maintained by the GCR to reflect the current status of the corresponding group call. + +In a RANflex configuration with group call redundancy Transient GCR Data needs to be synchronized between all GCRs associated to MSCs belonging to the same redundancy pool. + +#### 8.1.3.1 Group Call Status Information + +- a status flag indicating if a voice group call with the related group call reference is on-going, see subclause 11.3.1.1.1; +- in a RANflex configuration with group call redundancy: Address of the MSC within the redundancy pool, where the group call is ongoing (if so). + +#### 8.1.3.2 Initial Talker Information + +The relay MSC, and in a RANflex configuration (with or without group call redundancy) the group call serving MSC of the initiating service subscriber's current LAC, if this MSC is different from the VMSC, interrogate the GCR twice when setting up the voice group call: The first GCR interrogation is triggered in the relay MSC by the service subscriber or in a RANflex configuration (with or without group call redundancy) in the group call serving MSC by the MAP service SEND\_GROUP\_CALL\_INFO received from the VMSC. The second GCR interrogation is triggered in the relay MSC by the MAP service Prepare Group Call or in a RANflex configuration (with or without group call redundancy), if the anchor MSC is the group call serving MSC, by receiving the IAM from the VMSC. + +At the first GCR interrogation the GCR shall store transient data in the GCR which are retrieved with the second GCR interrogation. These data are: + +- the initiating service subscriber's IMSI; +- the initiating service subscriber's talker priority; +- the initiating service subscriber's additional information; and +- the originating cell id. + +## 8.2 Information managed per subscriber + +### 8.2.1 Stored in the HLR + +The following additional information shall be stored in the HLR: + +- the subscription option for voice group calls which can be made in the HPLMN only or also in case of roaming; +- a list of all the group IDs a service subscriber is entitled to use. + +- optionally, for each group ID a list of the talker priorities the service subscriber is allowed to use. The permission to use talker priority "normal subscriber" is implied by the subscription for the group ID and does not need to be stored explicitly; + +**Editor's note : Whether the HLR additionally stores for each group ID if the subscriber is allowed to transmit application-specific data is ffs.** + +- optionally, an information element containing operator specific additional information about the subscriber. + +The group IDs are defined in subclause 9.1. + +A service subscriber shall not be provided with more than 50 group IDs. + +### 8.2.2 Stored in the VLR + +The list of all the group IDs and related subscription data a service subscriber is entitled to use shall be brought forward to a VLR at the same time as other subscriber information is copied, and VLR entries shall be modified when corresponding HLR records are changed. + +### 8.2.3 Stored in the SIM + +The information detailed in subclause 8.2.1, except for the operator specific additional information about the subscriber, also needs to be stored on the SIM. The service subscriber shall be able to deactivate or reactivate a group ID by MMI interaction so that the mobile station ignores notification messages to this group ID, when the group ID is deactivated. + +If prefixes are used together with group IDs, these prefixes are not stored on the SIM. Moreover the group IDs on the SIM are stored without any prefix. + +#### 8.2.3a Stored in the USIM + +The information detailed in subclause 8.2.1, except for the operator specific additional information about the subscriber, also needs to be stored on the USIM. The service subscriber shall be able to deactivate or reactivate a group ID by MMI interaction so that the mobile station ignores notification messages to this group ID, when the group ID is deactivated. + +For each group ID where data confidentiality may be applied, the USIM needs to store the cipher algorithm to be used and the possible group keys. + +For each group ID the USIM needs to store indications whether the service subscriber is allowed to transmit application-specific data. + +If prefixes are used together with group IDs, these prefixes are not stored on the USIM. Moreover the group IDs on the USIM are stored without any prefix. + +## 8.3 Information used for routing of dispatcher originated voice group calls + +Routing of dispatcher originated calls shall be performed on the MSISDN number received at a GMSC in the `Initial_Address_Message`. + +- Because the group call reference is included in the called MSISDN number as defined in subclause 9.2d the routing information can be derived by the routing function of the GMSC. The GMSC afterwards directly routes the call request to the group call anchor MSC without requesting an HLR. + +# --- 9 Identities + +## 9.1 Elementary identities for group calls + +### a) Group ID + +The group ID is a sequence of decimal digits with a maximum length depending on the composition of the group call reference defined under c). The length of Group ID shall be in a range of 1 to 8 digits. + +The mobile station derives the group ID from the group call reference by identifying the longest group ID amongst those stored in the SIM/USIM and matching the least significant digits of the group call reference. If no group ID is stored in the SIM that matches the least significant digits of the group call reference, the mobile station is not able to derive the group ID from the group call reference. + +NOTE 1: The network should use Group IDs matching an initial part of other group IDs with greatest care, if at all. + +EXAMPLE: A mobile station storing the group IDs 678, 2 678 and 42 678 (and only those) in the SIM will derive group ID 2 678 from group call reference 13 452 678. + +For definition of Group ID on the radio interface, A interface and Abis interface, see 3GPP TS 44.068 [11]. + +For definition of Group ID coding on MAP protocol interfaces, see 3GPP TS 29.002 [13]. + +### b) Group call area ID + +The group call area ID is a sequence of decimal digits uniquely assigned to a group call area in one network and with a maximum length depending on the composition of the group call reference defined under c). + +### c) Group call reference + +Each voice group call in one network is uniquely identified by its Group call reference. The group call reference is a concatenated sequence of the group ID (as the least significant part) and the group call area ID (as the most significant part). The group call reference shall have a maximum length of 8 decimal digits. The composition of the group call area ID and the group ID can be specific for each network operator. + +| | | +|--------------------|----------| +| Group call area ID | Group ID | +|--------------------|----------| + +The group call reference is equal to the group ID when the group ID has a length of 8 decimal digits. + +For definition of Group Call Reference (with leading zeros inserted as necessary) on the radio interface, A interface and Abis interface, see 3GPP TS 24.008 [7], 3GPP TS 44.018[5] and 3GPP TS 44.068 [11]. + +For definition of Group Call Reference coding (also known as ASCII Call Reference, Voice Group Call Reference or Voice Broadcast Call Reference) on MAP protocol interfaces, see 3GPP TS 29.002 [13]. + +NOTE 2: If prefixes are used together with group IDs, the least significant digit of the group call area ID contains the prefix. + +## 9.2 Use of identities in the network + +For each voice group call the identifications as defined in the following shall be used within the network for the related purpose mentioned. + +For voice group call services which are to operate in more than one PLMN, group identities have to be co-ordinated between the network operators involved. + +### a) Identities used for GCR requests for service subscriber originated voice group calls + +For a service subscriber originated call, the identity of the call used by the MSC in which the call is originated to interrogate the GCR shall consist of the originating serving cell identity as defined in 3GPP TS 48.008 and the group ID as defined in subclause 9.1. In a RANflex configuration (with or without group call redundancy) the same identity is used by the group call serving MSC to interrogate the GCR when it receives the MAP Send Group Call Info service. + +| | | +|---------------------|----------| +| Originating cell ID | Group ID | +|---------------------|----------| + +A service subscriber initiating a voice group call has to call the wanted group ID. The MSC in which the call is originated shall accumulate from the BSS the called group ID and the originating cell ID. + +If the group call area exceeds one MSC area, the identity used to interrogate the GCR by an MSC in which the call was not originated shall consist of the group call reference as defined in subclause 9.1, except for the case in a RANflex configuration (with or without group call redundancy) where the GCR interrogation in the group call serving MSC is triggered by receipt of the MAP Send Group Call Info service. + +Without a RANflex configuration: If the group call area exceeds one MSC area and the call was originated + +- in a relay MSC, + +this relay MSC will perform a second GCR interrogation when the anchor MSC sets up the link to the relay MSC (see subclause 11.5). + +In a RANflex configuration: If the group call area exceeds one MSC area and the call was originated + +- in a relay MSC; or +- in a location area for which a relay MSC is the group call serving MSC, + +this relay MSC will perform a second GCR interrogation when the anchor MSC sets up the link to the relay MSC (see subclause 11.5). + +In a RANflex configuration with group call redundancy: If the group call area exceeds one MSC area and the call was originated + +- in a relay MSC; or +- in a location area for which a relay MSC (belonging to a redundancy pool) is the group call serving MSC, + +this relay MSC or another relay MSC belonging to the same redundancy pool will perform a second GCR interrogation when the anchor MSC sets up the link to the relay MSC (see subclause 11.5). + +Independent of the configuration for the second GCR interrogation the relay MSC shall use the group call reference as defined in subclause 9.1 as the identity. + +### **b) Identities used for GCR requests for dispatcher originated voice group calls** + +In case of dispatcher originated call the identity used by the MSC to interrogate the GCR shall consist of the group call reference as defined in subclause 9.1. + +### **c) Identities used for notifications to service subscribers** + +Identities used for notification messages shall consist of the group call reference as defined in subclause 9.1. + +### **d) Identities used by dispatchers for voice group call establishment** + +For dispatcher originated calls an MSISDN is dialled. The Country Code (CC) and National Destination Code (NDC) are used as normal for routing purposes. The CC and NDC may be omitted for internal calls. The numbering scheme is based on ITU-T Recommendation E.164. The Subscriber Number (SN) is used to indicate: + +- the request of a group call by use of a prefix. The length of the prefix shall be 1 to 2 digits; +- the wanted group call reference as defined in subclause 9.1. + +| CC | NDC | Prefix | Group call reference | +|-----------|------------|---------------|-----------------------------| +|-----------|------------|---------------|-----------------------------| + +### **e) Identities used for VLR requests for service subscriber originated group calls** + +The group ID shall be used on the B-Interface for VLR requests. + +### **f) Anchor MSC address for routing of service subscriber originated calls from originating MSC to anchor MSC** + +For service subscriber originated calls an anchor MSC address is used as called party address to route the call from the originating MSC to the anchor MSC. The anchor MSC address structure is the same as for dispatcher originated calls (see subclause d)). The Country Code (CC) and National Destination Code (NDC) are used as normal for routing purposes. The numbering scheme is based on ITU-T Recommendation E.164. The Subscriber Number (SN) is used to indicate: + +- the request of a group call by use of a prefix. The length of the prefix shall be 1 to 2 digits; the actual value of the prefix may be different than the one dialled by dispatchers. +- the wanted group call reference as defined in subclause 9.1. + +| CC | NDC | Prefix | Group call reference | +|-----------|------------|---------------|-----------------------------| +|-----------|------------|---------------|-----------------------------| + +### **g) Identities used for notifications to dispatchers** + +Identities used for notification messages to dispatchers shall be identical to those used by dispatchers to initiate calls as described in subclause d)). + +A notification identity is presented to a dispatcher terminal by making use of CLIP. Between the anchor MSC and MSC to which the dispatcher is attached, the information may be carried using the Calling Party Number parameter or Generic Number Parameter as agreed between the network operators. The Country Code (CC) and National Destination Code (NDC) are used as normal for routing purposes. The numbering scheme is based on ITU-T Recommendation E.164. The Subscriber Number (SN) is used to indicate: + +- the indication of a group call by use of a prefix. The length of the prefix shall be 1 to 2 digits; the actual value of the prefix shall be the same as the one dialled by dispatchers +- the group call reference as defined in subclause 9.1. + +| CC | NDC | Prefix | Group call reference | +|-----------|------------|---------------|-----------------------------| +|-----------|------------|---------------|-----------------------------| + +The Screening Indicator shall be set to “Network Provided” + +The Type of Number shall be set to “International” + +# 10 Operation and maintenance aspects + +NOTE: A list and short description of the operation and maintenance aspects will be given. This includes the options and parameters which can be set by the operator: + +- handling of timers; +- registration aspects; etc. + +# 11 Function and information flows + +## 11.1 Group management + +The group call attributes, as given in subclause 8.1 shall be entered and modified by the service provider. A list providing information on necessary Operation and Maintenance actions is given in clause 10. + +## 11.2 Group membership management + +Once the membership is established, the individual membership of the group can be placed in an active or deactive state on the SIM/USIM by the user. If a subscriber has a group ID in an active state, the subscriber is able to establish voice group calls corresponding to that group ID. + +In a deactive state the mobile station prevents the service subscriber from establishing calls using the group ID and the corresponding notifications need to be "ignored" by the mobile station. + +The active state and deactive state entries may be password protected as an implementation option. + +Group IDs are listed in the subscription data within the network and on the SIM/USIM. The SIM/USIM must be returned to the network operator or service provider for updating if the subscription is to be changed. + +NOTE 1: Updating of subscription data over the radio interface is not considered. However, this shall not preclude future applications if corresponding mechanisms may be implemented. + +Users can interrogate their mobile stations to determine to which groups they are members and which subscriptions are currently in an active state. + +NOTE 2: Distribution and management of group ID prefixes is outside the scope of this specification. + +## 11.3 Call management + +### 11.3.1 Call establishment + +A voice group call can be established by either a service subscriber or by a dispatcher. + +#### 11.3.1.1 Service subscriber call establishment + +##### 11.3.1.1.1 Initial stage + +The initial signalling from the calling service subscriber informs the network that a voice group call is required and details the group ID; it may specify originator-to-dispatcher information. No information relative to the group call area is given by the calling service subscriber. As an option the calling service subscriber may add a prefix to the group ID, which is taken into account by the network when selecting the area. + +The network shall perform a number of checks in order to determine how to handle the call: + +- check of the ability of the subscriber to establish the call; +- check whether the call can be initiated from the cell; +- check of the existence of an on-going call of the same group call reference. + +The originating MSC shall check the VLR records for the ability of the subscriber to start the call. If the service subscriber has no subscription for the voice group call service with the indicated group ID, the call shall be released. In addition, the VLR shall return barring and identity presentation restriction checks to the MSC. + +In a RANflex configuration the originating MSC shall then derive the group call serving MSC address from the originating location area. If the group call serving MSC is different from the originating MSC (or in a RANflex configuration with group call redundancy if the originating MSC does not belong to the group call serving MSC redundancy pool) then the group call serving MSC is interrogated by means of the MAP service SEND\_GROUP\_CALL\_INFO. The interrogation request contains the originating Cell Id and the Group Id. It also contains the initiating service subscriber's IMSI, the actual talker priority, and subscribed additional information. If the group call serving MSC is a relay MSC for the group call, then its GCR shall derive the anchor MSC address and the group call reference from the originating Cell Id and Group Id, and return it to the VMSC. If the group call serving MSC is the anchor MSC for the group call, then its GCR shall derive the group call reference from the originating Cell Id and Group Id, and return it to the VMSC. + +Without RANflex configuration or if in a RANflex configuration with or without group call redundancy the originating MSC is the group call serving MSC (derived from the originating location area) it shall then request information from the GCR by giving the group ID and the originating cell ID as defined in subclause 9.2. + +If the group ID has a length of 8 decimal digits, the operator can define for this group ID only one group call and one group call area within his network. If the length of the group ID is less than 8 decimal digits, the operator can define more than one group call using the same group ID, but different group call areas. Because of the possibility of overlapping group call areas, each call requires a unique reference, assigned by the GCR related to the originating MSC or the group call serving MSC (in a RANflex configuration with or without group call redundancy). The group call reference shall be composed of the group ID and a group call area ID (see clause 9). + +If the length of the group ID is less than 8 decimal digits, the GCR first derives the group call area ID from the group ID and the originating cell ID. If no group call area ID is related to the group ID and originating cell ID, the call shall be released. If a group call area ID is related to the group ID and originating cell ID, the GCR shall transfer the corresponding group call attributes to the MSC. + +In a network supporting prefixes together with group IDs, the operator can define more than one group call area for a specific combination of group ID and originating cell ID. In such a network, if the calling service subscriber has added a prefix to the group ID, the GCR shall derive the group call area ID from the prefix. The last digit of the group call area ID shall match the prefix. If the prefix is not provided or does not match the last digit of the group call area IDs to be considered, the network shall select a default value for the prefix and derive the group call area ID from this default prefix. The default value for the prefix is dependent on the network of the originating MSC. + +NOTE 1: Typically, the group call area ID derived from the default prefix value will select a complete group call membership, not a subset, and the group call area will include the group call areas derived from the other prefix values. + +NOTE 2: A mobile station not supporting the use of prefixes with group IDs can only set up voice group calls to the group defined by the default prefix. + +If the group ID has a length of 8 decimal digits, the group call reference is equal to the group ID. The GCR shall check whether the call was initiated within the group call area stored in the GCR. If not, the call shall be released; otherwise, the GCR shall transfer the corresponding group call attributes to the MSC. + +When the GCR has transferred the group call attributes to the MSC, the call shall be considered as on-going by the GCR, unless the GCR's associated MSC acts as group call relay MSC in a RANflex configuration with or without group call redundancy. + +The GCR of the relay MSC and in a RANflex configuration with or without group call redundancy, if the group call serving MSC of the initiating service subscriber's current LAC is different from the VMSC, the GCR of this group call serving MSC shall store the initiating service subscriber's IMSI, talker priority, additional information and originating cell id for later processing. + +If the originating MSC is not the group call anchor MSC for the voice group call as indicated in the GCR, then the voice group call request shall be passed to the group call anchor MSC; in that case, if the initiation of the voice group call had specified originator-to-dispatcher information and processing of originator-to-dispatcher information is supported by the MSC, the originator-to-dispatcher information is transformed by the originating MSC into UUS1 and sent to the anchor MSC. + +When passing the call request to the anchor MSC the originating MSC shall include the VGCS prefix plus group call reference in the calling party number of the IAM. If in a RANflex configuration the originating MSC is not the group call serving MSC, it shall in addition include the address of the group call serving MSC in the generic number parameter of the IAM, with the number qualifier indicator set to "additional calling party number". Without RANflex configuration or if in a RANflex configuration with or without group call redundancy the originating MSC is the group call serving MSC, it shall additionally include the address of the originating relay MSC in the generic number parameter of the IAM, with the number qualifier indicator set to "additional calling party number", when passing the call request to the anchor MSC. + +If the group call reference is composed of Group ID and group call area ID, it is possible that two service subscribers or a service subscriber and a dispatcher or two dispatchers may attempt to establish a call using the same group ID and corresponding to the same group call area ID. If the two voice group calls are established with the same group ID but for different group call areas then separate voice group calls shall be established. If the group call areas overlap, it is up to receiving mobile station to determine which call to participate in. If more than one call is made to identical group ID and group call area, the network shall reject all but one of the call attempts. + +If the group ID has a length of 8 decimal digits, if more than one call attempt is made to the same group ID, the network shall reject all but one of the call attempts. + +A service subscriber which is entitled by his subscription to establish voice group calls while roaming shall only be able to use supra-PLMN group IDs as defined in subclause 9.1 in case of roaming. In case of roaming, the mobile station shall only react on notifications for supra-PLMN group IDs. + +If the GCR receives a new interrogation related to a group call reference where the call is indicated as on-going in the GCR, the GCR shall provide the on-going status together with the group call reference and - in a RANflex configuration with group call redundancy - together with the address of the MSC within the redundancy pool where the group call is ongoing back to the MSC. The MSC shall then + +- a) in a configuration without RANflex; +- b) in a RANflex configuration; and +- c) in a RANflex configuration with group call redundancy, if the group call is ongoing at the requesting MSC: + +release the call with a cause user busy in case of a service subscriber originated call request. The mobile station of the service subscriber shall then look for notifications of the respective group ID on the NCH and join the voice group call. + +In case of a dispatcher originated voice group call request, the MSC shall join the dispatcher to the conference bridge of the voice group call, or + +- d) in a RANflex configuration with group call redundancy, if the group call is ongoing at another MSC within the redundancy pool: + +forward the original request to the MSC within the redundancy pool where the group call is ongoing. + +Authentication of the calling service subscriber can be performed by the network as for normal calls. + +##### 11.3.1.1.2 Establishment of the transmission means + +A voice group call channel shall be established in all the cells throughout the identified group call area using physical channels selected by the BSCs as appropriate. The downlink channels shall be established without any return signalling from mobile stations. Whilst the downlink channel is being established, the MSC shall form a conference bridge containing the appropriate channels to all BTSs in the group call area or in case of A-interface link sharing to all BSCs in the group call area. The MSC is responsible for adding dispatchers to the conference bridge. + +Alternatively, the network may establish voice group call channels in a cell on demand, i.e. if mobile stations respond to the notifications as defined in subclause 4.2.2.1 (see "uplink reply procedure"). As a network option the applicability of the uplink reply procedure for a voice group call can be controlled by the GCR of the anchor MSC. If the anchor MSC supports this feature, it shall allow all affected BSCs to establish voice group call channels on demand only if the GCR indicates that the uplink reply procedure is applicable. If the relay MSC supports this feature, it shall allow all affected BSCs to establish voice group call channels on demand only if the anchor MSC indicates during the establishment of the voice group call that the uplink reply procedure is applicable. + +In parallel, a dedicated suitable traffic channel may be allocated to the calling service subscriber if not already the case. + +If the "talker channel parameter" is used and indicates that the network shall always establish and maintain a dedicated channel for the talking service subscriber, a dedicated suitable traffic channel shall be allocated to the calling service subscriber. If there are not sufficient radio resources in the originating cell to allocate a dedicated channel and a group call channel, the group call establishment fails and the voice group shall be released. + +The call will be considered established provided that at least the downlink channel in the originating cell, in the case of a service subscriber originated voice group call, or the downlink channel in any one cell within the group call area, in the case of a dispatcher originated voice group call, is established. The MSC shall signal to the calling service + +subscriber that this has occurred so that he knows when to start speaking. If a voice group call does not meet the above conditions in a pre-set time (Txx) then the call shall be released. + +The mobile station shall indicate connection to the subscriber. If channels could not be established in particular cells because of congestion, channels are allocated to these cells as soon as possible. + +The MSC may retry the VGCS Assignment procedure to establish channels in cells where they are missing. If supported, the procedure may be initiated when: + +- i) congestion (i.e. a lack of A-interface circuits) prevented the VGCS ASSIGNMENT REQUEST message from being sent to the BSS; +- ii) a VGCS ASSIGNMENT FAILURE message is received and the cause value indicates an acceptable reason for retry (e.g. no radio resource available); +- iii) the radio and terrestrial resources for the group call channel are cleared (group call on-going) and the cause value indicates an acceptable reason for retry (e.g. pre-emption); +- iv) no response to the VGCS ASSIGNMENT REQUEST message is received (this is determined by the MSC in an implementation-dependent manner such as expiry of a timer); or +- v) no response is received following receipt of a VGCS QUEUING INDICATION (this is determined by the MSC in an implementation-dependent manner such as expiry of a timer). + +NOTE: If A-interface link sharing or group call re-establishment by the BSS apply, the BSC is responsible for establishing/re-establishing channels in cells and scenario (ii) and (iii) do not apply, unless A-interface resources also need to be re-established (e.g. when the PCM system serving the A-interface circuit fails (equipment failure)). Scenario (v) does not apply to A-interface link sharing and group call re-establishment by the BSS. + +The MSC may repeat the VGCS assignment procedure until a VGCS ASSIGNMENT RESULT message is received, the call is released or an unacceptable reason for retry (e.g. protocol error between BSS and MSC) is received by the MSC. The time between subsequent retries is implementation-dependent. The MSC shall send each retry of the VGCS ASSIGNMENT REQUEST over a new resource-controlling SCCP connection. + +If a message is received with an unacceptable reason for retry then existing procedures apply. I.e. the MSC shall initiate the clearing of the radio and terrestrial resources, if necessary, and no further attempts to establish a group call channel in the cell are made. + +While using the retry procedure the MSC shall maintain the call controlling SCCP connection to a BSS until the call is released or until the MSC decides to stop any further attempts to establish group call channels for the call on a BSS where no cells are established. + +##### 11.3.1.1.3 Release of the dedicated transmission means of the calling service subscriber + +The calling service subscriber shall be given a dedicated connection up to the time where the network requests him to join the voice group call channel. If the calling service subscriber is not talking, the network requests him to join the voice group call channel as a listener by use of a channel release procedure. Otherwise, the network shall request him to join the voice group call channel as a talker by either a channel assignment procedure or a handover procedure or a channel mode modify procedure. + +If the "talker channel parameter" is used and indicates that the network shall always establish and maintain a dedicated channel for the talking service subscriber, then the network shall not request the calling service subscriber to join the group call channel as long as he is talking. + +For the time when the voice group call is established until the calling service subscriber becomes a listening service subscriber for the first time, the "uplink busy" flag is set (see subclause 11.3.8). Mobile stations shall be programmed such that if they originate the call, they indicate to the user that it is required that an indication of the desire to speak should be made if he wants to speak. If this is not done within a certain time, the mobile station sends an UPLINK\_REL message to the network and the uplink shall become free. + +##### 11.3.1.1.4 Release of the dedicated transmission means of mobile stations responding to a notification + +Mobile stations which respond to a notification for which no description of the voice group call channel was given in the notification message may be given a dedicated connection up to the time where the network requests the mobile station to join the voice group call channel. If the service subscriber is not talking, the network requests him to join the voice group call channel as a listener by use of a channel release procedure. Otherwise, the network shall request him to join the voice group call channel as a talker by either a channel assignment procedure or a handover procedure or a channel mode modify procedure. + +11.3.1.1.5 void + +11.3.1.1.6 void + +#### 11.3.1.2 Dispatcher call establishment + +In the case of dispatchers originated calls the call request, in the form of an MSISDN number, shall be received at a GMSC. Such a call can be treated by the GMSC as a normal mobile terminated call. In this case, the GMSC shall interrogate an HLR, determined on the basis of the MSISDN number. The HLR in turn may either interrogate the appropriate MSC/VLR to obtain an MSRN, or may supply an MSRN predefined in the HLR and related to the respective group call reference in the MSC/VLR. If the HLR interrogates the MSC/VLR for the MSRN, the HLR shall provide this MSC/VLR with the related IMSI including the group call reference as defined in clause 9. + +Alternatively, the call request can be forwarded directly to the related group call anchor MSC on basis of the GMSC's internal routing table. In this case, the group call reference shall already be included in the requested MSISDN number as defined in clause 9. + +When interrogated by the group call anchor MSC, the GCR shall check if the calling line identity is within the list of dispatcher identities allowed to establish the voice group call. If not the case, the call shall be rejected. + +After reception of the call request, the group call anchor MSC checks whether an on-going call of the same group call reference exists, in which case for the following configurations + +- a) for configurations with or without RANflex; +- b) for RANflex configurations; and +- c) for RANflex configurations with group call redundancy where the group call is ongoing at the call request receiving MSC: + +the group call anchor MSC shall add the dispatcher to the call, and for the following configuration + +- d) for RANflex configurations with group call redundancy where the group call is ongoing at another MSC within the redundancy pool: + +the call request receiving MSC shall forward the call request to the MSC where the group call is ongoing. + +At the point at which notification messages are sent to mobile stations, a tone is relayed to the calling dispatcher to inform the dispatcher that the message can commence. + +#### 11.3.1.3 Notification procedures + +Different notification procedures shall be applied in relation to the mode of the mobile station as presented in Table 1 and Table 2 and defined in the following sections. + +**Table 1: Overview on different information messages for new or on-going calls** + +| Incoming call type: | VBS or VGCS call | point-to-point call | +|--------------------------------------------|---------------------------------------------------------------------------------------|--------------------------------| +| MS states: | | | +| Idle mode | (section a) | (standard paging) | +| Group mode, dedicated channel | (section b) | (section c) | +| group receive mode and group transmit mode | (section b) | (section c) | +| dedicated mode | (section b) | (standard Call Waiting) (note) | +| NOTE: | only for point to point calls with certain restrictions as defined in 3GPP TS 22.083. | | + +**Table 2: Overview on different information messages for incoming point-to-point short messages** + +| MS states: | Incoming point-to-point short messages | +|-------------------------------|---------------------------------------------| +| Idle mode | (standard paging) | +| group mode, dedicated channel | (standard SMS delivery) (note) | +| group receive mode | (section c) | +| group transmit mode | (standard SMS delivery or section c) (note) | +| dedicated mode | (standard SMS delivery) (note) | +| NOTE: | see subclause 11.3.9.2. | + +##### a) Notification for mobile stations in idle mode + +Once the voice group call channel has been established in a cell or the network is waiting to receive notification responses to establish a voice group call channel, notifications shall be broadcast on the NCH in that cell. + +The position of the NCH is derived from the system information of the BCCH. + +The notification messages shall include the group call reference and possibly the description of the voice group call channel, the call priority if eMLPP is applied, the group cipher key number, and the emergency mode indication, if applicable. + +A notification message can contain no, one or more notifications. + +The notification process needs to continue throughout the duration of the group call, in order to permit the "late entry" of other mobile stations. Mobile stations moving into the group call area which are in idle mode shall be directed to the voice group call channel by the notification messages, possibly by means of the notification response procedure. + +The scheduling of the notification messages in a cell shall be managed by the BSS. Information can be added in the messages to limit the required reception of NCH messages. The following constraints shall be met: + +- the three first initial notifications (i.e. the first for a given group call) shall have priority over subsequent notifications (i.e. the messages for an on-going group call) and must be sent as soon as possible; + +NOTE 1: In addition initial notification messages for calls with or above an operator defined priority level can be sent on all possible paging or access grant channels to reduce the delay for those mobile stations which are not using Discontinuous reception (DRX). + +- afterwards, an on-going group call in the cell shall be periodically notified on the NCH. + +Since the information for the establishment of a voice group call is sent onto the NCH rather than on the PCH as for normal point-to-point calls, the mobile station must listen to the PCH as well as to the NCH. A "reduced NCH monitoring" mechanism can be used to save power in the mobile station when listening to the NCH. + +A mobile station able to receive voice group calls either, depending on the implementation: + +- can use the "reduced NCH monitoring" mechanism. When entering a cell, the mobile station shall listen to the NCH to get the notifications of the voice group calls on-going in the cell. Afterwards, the mobile station needs to listen to the NCH only if it is informed on the availability of a notification for a new voice group call. This shall be based on the NCH status information provided, as indicated in 3GPP TS 44.018; +- do not apply the "reduced NCH monitoring" mechanism and read all possible paging or access grant channels. + +##### **b) Notifications for mobile stations in group mode dedicated channel, group receive, group transmit or dedicated mode** + +In addition to sending initial notification messages on the NCH for the voice group call, the BSS can provide initial notification into on-going voice broadcast, group calls and point to point calls informing mobile stations partaking in these calls of new voice group calls that are being set-up in the cell. + +NOTE 2: The additional notification into on-going voice broadcast and group calls and point to point calls should be provided by the BSS if the priority level of the new call is equal or higher than the O&M defined priority level. + +In order to do this the BSS sends initial notification messages on FACCH to all other ongoing voice broadcast, group calls, and point to point calls in the cell. The initial notification message on FACCH shall contain the group call reference, the priority level if eMLPP applies, possibly the TCH description which allows the mobile station to connect directly to the new call without reading the NCH, and the emergency mode indication, if applicable. + +An indication of change of notifications in the current cell may be provided on SACCH by the BSS. + +When the emergency mode is set or reset for a voice group call ongoing in a cell, the BSS shall send additional notifications on FACCH to all on-going voice broadcast, group calls, and point-to-point calls in the respective cell. + +As a mobile station option, the mobile station may read the NCH of the current cell while in group mode dedicated channel, group receive, group transmit or dedicated mode in order to be notified on other voice group calls. + +NOTE 3: Mobile stations may require an additional receiver to read the NCH in order to ensure a higher probability of receiving notifications for all present voice group calls without degradation of the received speech quality. + +Late entry of mobile stations into ongoing high priority group calls and voice group calls in emergency mode is covered by the following mechanisms: + +- Late entrance in dedicated mode + +If a mobile station in dedicated mode is moving into an area where a group call (VGCS or VBS) with priority level equal or higher to an operator specific setting or a voice group call in emergency mode is ongoing, the BSS shall resend the notification message to the mobile station on FACCH, if the mobile station has ASCII capabilities. This notification shall be triggered by completion of the dedicated channel assignment. + +Sending periodical notification on FACCH to the mobile station in dedicated mode is optional, and is done as long as the group call (VGCS or VBS) with priority level equal or higher to an operator specific setting, is ongoing or as long as the emergency mode is set for the voice group call, with a repetition period given by an operator specific setting. + +- Late entrance in group receive or group transmit mode + +When a group call (VGCS or VBS) with priority level equal or higher to an operator specific setting, is established, or when the emergency mode is set for a voice group call, the BSS shall send periodical notification on FACCH to all ongoing voice broadcast and group calls in the cell, except on the FACCH of the group call (VGCS or VBS) which has initiated this periodical notification. By this method the mobile station in group receive or group transmit mode moving into this cell is notified. Periodical notification on FACCH is done as long as the group call (VGCS or VBS) with priority level equal or higher to an operator specific setting, is ongoing, or as long as the emergency mode is set for the voice group call, with a repetition period given by an operator specific setting. + +NOTE 3a: The operator determined Periodical FACCH notification period shall be a BSS specific operator setting and be a minimum of 1s and maximum of 5s. + +##### c) Paging into on-going voice group calls + +Paging into on-going voice group calls shall be provided as an implementation option. + +In addition to establishing the links for the voice group call, the network can provide paging information into on-going voice group calls informing mobile stations partaking in a voice group call of new incoming point-to-point calls. The network can also provide paging information into ongoing voice group calls informing mobile stations in group receive mode or group transmit mode of incoming point-to-point short messages. + +The mobile station shall be ready to receive a paging message on the FACCH containing the mobile subscriber identity and the priority level if eMLPP applies. + +In the event of a reorganisation of the PCH the BSS shall inform the mobile stations via the SACCH that paging reorganisation has occurred. A mobile station receiving this indication shall decode the BCCH in order to obtain the new paging configuration. + +As a mobile station option, the mobile station may read its paging subchannel in the current cell in group receive mode or group transmit mode in order to receive paging messages. + +NOTE 4: Mobile stations may require an additional receiver to read its PCH subchannel in order to ensure a higher probability of receiving all relevant paging messages without degradation of the received speech quality. The additional receiver may be the same as used for reception of the NCH described under b) above. + +#### 11.3.1.4 Destination service subscribers + +Mobile stations of destination service subscribers which are in idle mode shall listen to notification messages on the NCH and move to the voice group call channel or respond to the notification. + +Mobile stations which are busy shall either pre-empt the current call (if eMLPP is applied and the new call is of a sufficient priority), or shall provide the service subscriber with an indication similar to call waiting, when applicable. + +If the mobile station supports group IDs with prefixes and has stored prefixes for the group ID in the notification, the mobile station shall only react as described previously in this subclause if the last digit of the group call area ID included in the group call reference matches the default prefix or one of the prefixes stored for the group ID. If the last digit of the group call area ID does not match then the mobile station shall not react as described previously in this subclause, but may still react by making an acknowledgement as defined in subclause 4.2.5. + +NOTE: In a network supporting the use of prefixes together with the group ID, a mobile station not supporting the use of prefixes will react to notification messages and can participate in any voice group call for a group ID for which it has a subscription, regardless of any prefix used for setting up the voice group call. + +#### 11.3.1.5 Destination dispatchers + +Destination dispatchers are connected into the voice group call as a standard point-to-point call. The notification of the identity of the received group call shall be supplied in the Calling Line Identity, formatted according to sub-clause 9.2. + +### 11.3.2 Call release + +The voice group call can be terminated by the calling service subscriber or the calling dispatcher clearing it down, or by any dispatcher nominated in the GCR allowed to terminate the call. + +#### 11.3.2.1 Call termination by the calling subscriber + +The calling service subscriber will need to gain the uplink before he can issue a termination request. + +If the mobile station uses the uplink with a talker priority different from "normal subscriber" it shall include this talker priority in the termination request message. If the network supports uplink access option (i) as defined in subclause 7.2 and A-interface link sharing applies, the MSC shall compare the talker priority included in the termination request message with the talker priority stored for the current talker. If they are equal, the termination request is processed further; otherwise the MSC discards the termination request message. + +The MSC has to store the identity of the calling service subscriber and to check it against the identity of the service subscriber which sends the voice group call termination request. If they are equal, the MSC shall accept the termination request and release all resources. On the radio interface a channel release message shall be sent on the FACCH of all cells in the group call area and then all resources are freed. + +#### 11.3.2.2 Call termination by dispatchers + +A dispatcher entitled to terminate the call can be a mobile subscriber or a fixed line subscriber. The dispatcher may use out-of-band DTMF messages as a means for the control of the call termination, if it is a mobile dispatcher, or DTMF tones, if it is a fixed line dispatcher. + +If the call is terminated by a mobile dispatcher using DTMF, the out-of-band messages START\_DTMF(X) and STOP\_DTMF are sent via the radio interface towards the network. If the out-of-band DTMF messages are sent by a mobile dispatcher who is not controlled by the anchor MSC, the DTMF messages will be converted by the controlling MSC (e.g. relay MSC or visited MSC) into DTMF tones and these DTMF tones will be sent through the network to the anchor MSC. + +If a fixed dispatcher initiates DTMF tones, the DTMF tones will be sent through the network to the anchor MSC. + +Both in case of a mobile and a fixed line dispatcher the anchor MSC is responsible for the detection and collection of the out-of-band or in-band DTMF signals. After the evaluation of the DTMF signals, the anchor MSC shall trigger the appropriate function (see the figures 7b to 7d in 11.3.8). + +In order to avoid the erroneous detection of the specific DTMF tone sequence for call termination by the MSC, this sequence shall consist of at least three DTMF digits. + +#### 11.3.2.3 Call termination on expiry of no activity timer + +A time-out mechanism is required such that, if the anchor MSC does not detect any activity (as specified in subclause 8.1.2.3) within a pre-set time, the call is terminated by the anchor MSC. For this a timer shall be provided with a length as defined in the group call attributes in the GCR. + +The network may provide an in-band indication, e.g. a tone, to inform the participants of the group call about the forthcoming expiry of the "no activity" timer. + +### 11.3.3 Leaving of a dispatcher + +A dispatcher can disconnect from the call at any time without terminating the call. In order to terminate the call a dispatcher who is entitled to do this must use the explicit signalling described in subclause 11.3.2.2. + +### 11.3.4 Leaving and returning to a voice group call + +A service subscriber shall automatically disconnect from the call when leaving the group call area. + +A service subscriber shall be able to disconnect from the voice group call by a de-selection/re-selection process. + +A mobile station shall leave the voice group call by no longer listening to the voice group call downlink and returning to idle mode. A voice group call is returned to by listening to the periodic notification messages for that call, and reacting on them appropriately. + +### 11.3.5 Cell change + +#### 11.3.5.1 Listening subscriber + +In all cases change of cell shall be initiated and performed by the service subscriber's mobile station. In order for the service subscribers changing from one cell to another within the group call area a cell list for the neighbouring cells belonging to this group call area is periodically broadcast on the downlink SACCH of the voice group call. In this case, mobile stations entering a new cell shall perform cell change according to the algorithm C2, see 3GPP TS 45.008 and 3GPP TS 43.022. + +Mobile stations which want to enter a cell shall listen to the BCCH and to the NCH to determine which channel they shall retune to so that they can continue with the voice group call if available in that cell. + +NOTE: Mobile stations may require an additional receiver to read the BCCH and NCH of the neighbour cells in order to ensure a higher probability of receiving the relevant messages without degradation of the received speech quality. The additional receiver may be the same as used in subclause 11.3.1.3. + +Mobile stations entering a new location area shall perform location updating as normal. + +#### 11.3.5.2 Talking subscriber + +Standard mobile station assisted handover shall be used for the cell change of the talking service subscriber as defined in 3GPP TS 45.008. + +If the "talker channel parameter" indicates that the network shall always establish and maintain a dedicated channel for the talking service subscriber, the channel allocated by the network in the target cell shall always be a dedicated channel. + +If the network supports uplink access option (i) as defined in subclause 7.2, collision cases between a handover of the talking service subscriber to a voice group call channel and an uplink access message on the same group call channel uplink shall be treated in the following way: + +- when the BSS allocates the handover resources for the talking service subscriber, the BSS shall send an updated UPLINK BUSY message in the target cell and no longer accept uplink access messages on this group call channel uplink ; +- when the BSS already granted the uplink to another subscriber , the BSS shall delay the resource allocation for the handover of the current talker to the same cell. If the MSC accepts the uplink request for the new talker , the BSS shall cancel the handover resource allocation . Additionally, if the current talker is served by the BSS, the BSS shall release the current talker. Otherwise, if the MSC does not accept the uplink request for the new talker, the BSS shall release the new talker and proceed with the handover of the current talker. + +If the talking subscriber leaves the group call area or enters a BSC area not belonging to the service area, the uplink shall not be maintained by the network. + +If the BSS does not know if one or more of the target cells are outside the group call area, the BSS shall use the MSC controlled handover procedure. The MSC shall reject the handover in the case that all target cells are outside the GCA and as an option release the uplink. + +In a RANflex configuration with or without group call redundancy, if the target cell belongs to a location area for which the group call serving MSC is not the old cell's serving MSC, an inter MSC handover shall be performed. + +#### 11.3.5.3 Dispatcher + +Dispatchers which are mobile subscribers shall change the cell by standard handover procedures. + +### 11.3.6 New calls + +Any service subscriber originated new voice group calls which have identical group ID and group call area to on-going voice group calls shall be rejected by the network with cause busy. The mobile station shall then read the notifications for the corresponding group ID on the NCH. + +For any dispatcher originated new voice group calls which are identical to on-going voice group calls as described above the network shall include the dispatcher in the on-going call. + +Otherwise, new calls are treated as detailed in subclause 11.3.8. In the case of congestion, voice group calls are treated according to their priority with each BSC treating each downlink depending on the situation in each cell to which the call is sent. Therefore, it is possible that a voice group call might be established only in a subset of the required cells. + +In the case where there are no conference bridges free, and pre-emption is not performed, then the call request shall be rejected. + +In the case of group members involved in group or point-to-point calls who have been informed of a new voice group call, the mobile station shall make a decision as to which to monitor as if both the on-going call and new call were point-to-point calls, and follow the procedure defined in 3GPP TS 23.067. + +### 11.3.7 Uplink and Downlink management + +#### 11.3.7.1 Uplink transmission management + +The downlink FACCH channel shall be used to indicate whether the uplink is in use. + +If a request to talk is made by the user and the uplink has been free the mobile station shall start to transmit UPLINK\_ACCESS messages as defined in the 3GPP TS 44.018. + +If the network supports the use of talker priorities, a mobile station supporting the use of talker priorities may + +- send a request to talk even if an uplink busy indication is received, if the talker priority of the new request is higher than the talker priority of the current talking service subscriber; or +- send an emergency mode reset request, if the emergency mode indication is signalled by the network. + +If a VGCS\_UPLINK\_GRANT message is received by the mobile station with a different request reference than that of the access made by the mobile station, the mobile station shall not signal for a further 1 s. + +If in this time the uplink becomes busy, and the network does not support the use of talker priorities, the mobile station shall indicate to the user that the access has been denied. + +If in this time the uplink becomes busy, and the network indicates in the UPLINK\_BUSY message a talker priority equal or higher than the talker priority used by the mobile station in the UPLINK\_ACCESS message or PRIORITY\_UPLINK\_REQUEST message, the mobile station shall indicate to the user that the access has been denied; otherwise, it shall resend the UPLINK\_ACCESS message or PRIORITY\_UPLINK\_REQUEST message, respectively. + +The user shall be provided with a short indication immediately after the reception of the VGCS\_UPLINK\_GRANT which indicates that he can speak. Contention caused by simultaneous access messages on the uplink of the voice group call channel shall be resolved as for standard random access procedures. If the uplink access is rejected a further indication shall be provided to the user to inform him that his access attempt was not successful. + +The network then shall send an UPLINK\_BUSY message on the FACCH of the voice group call channel downlink in all cells involved in the group call. + +Signalling messages for call establishment and termination on the voice group call channel shall then only apply for the mobile station currently using the uplink. All other mobile stations shall not respond to this downlink signalling. Once the request to talk is over, this shall be indicated to the network by the mobile station, an UPLINK\_FREE message is broadcast on all FACCHs in the group call area. + +If the network supports the use of talker priorities, the BSS shall include the priority of the current talker in the UPLINK\_BUSY message and shall repeat the message on the FACCH every T1 seconds. + +If the network supports uplink access option (i) as defined in subclause 7.2, the BSS shall indicate in the UPLINK\_BUSY message which channel shall be used by service subscribers for an uplink request in the current cell. The UPLINK\_BUSY message can contain two different indications. The mobile station of the service subscriber shall act: + +- according to the "uplink access indication for talker priority" when signalling an uplink request with talker priority higher than "normal subscriber" or an "emergency mode reset request"; or +- according to the "uplink access indication for data" when signalling an uplink request for sending application-specific data. + +If both indications are included in the UPLINK\_BUSY message, they should be set to the same value. + +If the "talker channel parameter" is used and indicates that the network shall always establish and maintain a dedicated channel for the talking service subscriber, then the BSS shall set any uplink access indication included in the uplink busy message (i.e. "uplink access indication for data", "uplink access indication for talker priority", or both) to "group call channel uplink access". + +Otherwise, the BSS shall apply the following procedures: + +If the talking service subscriber uses the group call channel uplink in the current cell, the BSS shall indicate in the UPLINK\_BUSY message that the RACH shall be used; otherwise it shall indicate that the group call channel uplink shall be used. The BSS shall immediately send an updated UPLINK\_BUSY message: + +- in the handover target cell when the BSS allocates the resources for a handover of the talking service subscriber to the voice group call channel in the target cell; +- in the handover target cell when BSS releases the resources allocated for the handover of the talking service subscriber to the voice group call channel in the target cell, because handover failed; +- in the handover source cell after reception of a HANDOVER SUCCEEDED message; + +- in the current cell after the talking service subscriber has been switched within the cell from the group call channel to a dedicated channel or vice versa. + +When the BSS receives an indication from the MSC that the emergency mode is set in the network, the BSS shall immediately send an UPLINK\_BUSY message on the FACCH and include also the "emergency mode indication". + +If the BSS receives a VGCS Additional Info message from the MSC, an ADDITIONAL\_INFO message is broadcasted on the FACCHs of the voice group call channel downlink in all cells involved in the current group call. If the BSS receives the additional information in the UPLINK\_SEIZED\_CMD, UPLINK\_REQUEST\_ACKNOWLEDGE or UPLINK\_REJECT\_CMD message then the BSS may include the information in the UPLINK\_BUSY message instead of sending it in a separate ADDITIONAL\_INFO message on the group call channel downlink. The BSS shall repeat the ADDITIONAL\_INFO message on the SACCHs of the respective voice group call channels every T2 seconds, until the uplink is released, or the BSS receives an Uplink Release Command message or Uplink Seized Command message for the respective voice group call from the MSC. + +If the BSS receives a VGCS Additional Info message from the MSC and the current talker on a dedicated channel is pre-empted by another service subscriber with a higher talker priority, the BSS shall transmit the additional information about the new talker also to the current talker when releasing his dedicated channel. + +##### 11.3.7.1a Transfer of a talking service subscriber to a dedicated connection + +The network may decide to switch a talking service subscriber's mobile station from the voice group call channel to a dedicated standard uplink/downlink at any time. The talking subscriber's voice group call channel and the dedicated channel may belong to different cells within the group call area, i.e. the network may request the talker to perform a handover. The dedicated connection shall then be maintained up to the instance where the network decides that the mobile station shall join the voice group call channel again. + +If the "talker channel parameter" is used and indicates that the network shall always establish and maintain a dedicated channel for the talking service subscriber, a dedicated traffic channel shall be allocated to the talking service subscriber. If there are not sufficient radio resources to allocate a suitable dedicated channel in a cell within the group call area, the MSC shall release the uplink of the voice group call channel used by the talking service subscriber. + +##### 11.3.7.1b Release of the dedicated transmission means of a talking service subscriber + +For the release of the dedicated transmission means of a talking service subscriber the procedures specified in subclause 11.3.1.1.3 apply accordingly. + +#### 11.3.7.2 Mute/Unmute downlink of the talker + +This subclause applies to networks where the talking service subscriber may use the voice group call channel. The handling of the Mute/Unmute requests by the anchor MSC is shown in Figure 1a. + +The mobile station of the talking service subscriber shall mute the downlink to avoid non intelligible echoes when it is commanded by the network to mute the downlink. On request of the dispatcher, the network can command the mobile station of talking service subscriber to mute or unmute the downlink. + +If a dispatcher originates a VGCS call, he is allowed to talk immediately when the VGCS call is established. If a dispatcher joins or re-joins an ongoing VGCS call, he is allowed to talk to the ongoing VGCS call at any time without need to indicate this by any kind of signalling. If there is a talking service subscriber using the uplink of the group call channel, he will not be able to hear the dispatcher's voice. + +If a dispatcher wishes to talk to the talking service subscriber and all members of the ongoing group call, he shall indicate his wish by means of an operator-defined operation (via DTMF). If the dispatcher has finished speaking, he shall indicate this by means of another operator defined operation (via DTMF). These operations will trigger the network to command the talking service subscriber's MS to mute or unmute the downlink of voice group call channel. + +When the network has detected a valid unmute request from a dispatcher it may optionally indicate the recognition of this request by playing a "grant tone" to be received by the requesting dispatcher only. The grant tone will be sent in-band. The attributes of the grant tone (e.g. frequency and duration) are network operator specific. + +A dispatcher can be a mobile subscriber or a fixed line subscriber. The dispatcher uses out-of-band DTMF messages if it is a mobile dispatcher, or DTMF tones, if it is a fixed line dispatcher. In case of a mobile dispatcher, the out-of-band messages START\_DTMF(X) and STOP\_DTMF are sent via the radio interface towards the network. If the out-of-band DTMF messages are sent by a mobile dispatcher who is not controlled by the anchor MSC, the DTMF messages will be + +converted by the controlling MSC (e.g. visited MSC) into DTMF tones and these DTMF tones will be sent through the network to the anchor MSC. If a fixed line dispatcher initiates DTMF tones, the DTMF tones will be sent through the network to the anchor MSC. + +NOTE: The transport of DTMF tones within the network is detailed in figures 7b, 7c and 7d. + +Both for mobile and fixed line dispatchers the anchor MSC is responsible for the detection and collection of the out-of-band or in-band DTMF signals. After the evaluation of the DTMF signals, the anchor MSC shall trigger the appropriate action (i.e. send/not send the SET\_PARAMETER message according to previous paragraphs, playing of the optional grant tone). + +The DTMF sequences used for signalling are implementation specific. These two DTMF sequences shall not be the same. + +![State transition diagram for process Mute_Unmute. It starts with 'No VGCS' leading to two initial states: 'SS Initiates VGCS' and 'DT Initiates VGCS', both setting 'no_of_talkers:=0'. The 'SS Initiates VGCS' path leads to 'No DT Talking SS First Talker Dedicated Channel', which has transitions for 'DT Leaves Call', 'DT Stops Talking', 'SS Releases Uplink', 'DT Starts Talking' (leading to 'Play Grant Tone' and 'no_of_talkers:=1'), and 'DT Joins Call'. The 'DT Initiates VGCS' path leads to 'A DT Talking SS First Talker Dedicated Channel', which has transitions for 'SS Releases Uplink', 'Talking DT Stops Talking', 'Non-talking DT Stops Talking', 'Non-talking DT Leaves Call', 'Talking DT Starts Talking', 'Play Grant Tone' (leading to 'increment no_of_talkers'), and 'DT Joins Call'. Both paths lead to a decision 'no_of_talkers = 0?'. If 'Yes', it leads to 'No DT Talking No SS Talking'. If 'No', it leads to 'A DT Talking No SS Talking'.](fd76efce549d3713543bb5ed9b023c2e_img.jpg) + +process Mute\_Unmute 1(3) + +In the states on the following diagrams: + A DT is a Dispatcher Terminal. + SS is Service Subscriber. + "A DT Talking" should be interpreted as meaning that one or more DTs are talking. + "Talking" for a dispatcher means that it has sent the Start Talking request, but not yet sent the Stop Talking request. + "no\_of\_talkers" only relates to the number of DTs currently talking and does not include the SS + +The input signal + "xxx DT Starts Talking" + where "xxx" is either "Talking" or "Non-Talking" is a shorthand to represent a signal + "xxx DT sends Start to Talk sequence" + +The input signal + "xxx DT Stops Talking" + where "xxx" is either "Talking" or "Non-Talking" is a shorthand to represent a signal + "xxx DT sends Stop Talking sequence" + +``` + +stateDiagram-v2 + [*] --> NoVGCS: No VGCS + NoVGCS --> SSInitiatesVGCS: SS Initiates VGCS + NoVGCS --> DTInitiatesVGCS: DT Initiates VGCS + SSInitiatesVGCS --> no_of_talkers0_1: no_of_talkers:=0 + DTInitiatesVGCS --> no_of_talkers0_2: no_of_talkers:=0 + no_of_talkers0_1 --> NoDTTalkingSSFirstTalker: No DT Talking SS First Talker Dedicated Channel + no_of_talkers0_2 --> ADTTalkingSSFirstTalker: A DT Talking SS First Talker Dedicated Channel + NoDTTalkingSSFirstTalker --> DTLeavesCall: DT Leaves Call + NoDTTalkingSSFirstTalker --> DTStopsTalking: DT Stops Talking + NoDTTalkingSSFirstTalker --> SSReleasesUplink: SS Releases Uplink + NoDTTalkingSSFirstTalker --> DTStartsTalking: DT Starts Talking + NoDTTalkingSSFirstTalker --> DTJoinsCall: DT Joins Call + DTStartsTalking --> PlayGrantTone1: Play Grant Tone + PlayGrantTone1 --> no_of_talkers1: no_of_talkers:=1 + no_of_talkers1 --> no_of_talkers0_1 + ADTTalkingSSFirstTalker --> SSReleasesUplink2: SS Releases Uplink + ADTTalkingSSFirstTalker --> TalkingDTStopsTalking: Talking DT Stops Talking + ADTTalkingSSFirstTalker --> NonTalkingDTStopsTalking: Non-talking DT Stops Talking + ADTTalkingSSFirstTalker --> NonTalkingDTLeavesCall: Non-talking DT Leaves Call + ADTTalkingSSFirstTalker --> TalkingDTStartsTalking: Talking DT Starts Talking + ADTTalkingSSFirstTalker --> PlayGrantTone2: Play Grant Tone + ADTTalkingSSFirstTalker --> DTJoinsCall2: DT Joins Call + PlayGrantTone2 --> increment_no_of_talkers: increment no_of_talkers + increment_no_of_talkers --> no_of_talkers0_2 + no_of_talkers1 --> no_of_talkers_eq_0_1{no_of_talkers = 0?} + increment_no_of_talkers --> no_of_talkers_eq_0_2{no_of_talkers = 0?} + no_of_talkers_eq_0_1 --> NoDTTalkingNoSSTalking1: No DT Talking No SS Talking + no_of_talkers_eq_0_1 --> ADTTalkingNoSSTalking1: A DT Talking No SS Talking + no_of_talkers_eq_0_2 --> NoDTTalkingNoSSTalking2: No DT Talking No SS Talking + no_of_talkers_eq_0_2 --> ADTTalkingNoSSTalking2: A DT Talking No SS Talking + +``` + +State transition diagram for process Mute\_Unmute. It starts with 'No VGCS' leading to two initial states: 'SS Initiates VGCS' and 'DT Initiates VGCS', both setting 'no\_of\_talkers:=0'. The 'SS Initiates VGCS' path leads to 'No DT Talking SS First Talker Dedicated Channel', which has transitions for 'DT Leaves Call', 'DT Stops Talking', 'SS Releases Uplink', 'DT Starts Talking' (leading to 'Play Grant Tone' and 'no\_of\_talkers:=1'), and 'DT Joins Call'. The 'DT Initiates VGCS' path leads to 'A DT Talking SS First Talker Dedicated Channel', which has transitions for 'SS Releases Uplink', 'Talking DT Stops Talking', 'Non-talking DT Stops Talking', 'Non-talking DT Leaves Call', 'Talking DT Starts Talking', 'Play Grant Tone' (leading to 'increment no\_of\_talkers'), and 'DT Joins Call'. Both paths lead to a decision 'no\_of\_talkers = 0?'. If 'Yes', it leads to 'No DT Talking No SS Talking'. If 'No', it leads to 'A DT Talking No SS Talking'. + +Figure 1a: Handling of Mute/Unmute Requests in Anchor MSC (Sheet 1 of 3) + +![State transition diagram for process Mute_Unmute (Sheet 2 of 3).](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +process Mute\_Unmute + +2(3) + +The diagram shows two main states: 'No DT Talking SS Talking Downlink Muted' and 'A DT Talking No SS Talking'. Transitions from the first state include 'DT Stops Talking', 'DT Leaves Call', 'DT Joins Call', 'DT Starts Talking', and 'SS Releases Uplink'. 'DT Joins Call', 'DT Starts Talking', and 'SS Releases Uplink' lead to 'Play Grant Tone', which then leads to 'no\_of\_talkers:=1' and 'Unmute Downlink', resulting in state 'A DT Talking SS Talking Downlink Unmuted'. 'DT Stops Talking' and 'DT Leaves Call' lead back to the initial state. Transitions from the second state include 'SS Requests Uplink', 'Talking DT Stops Talking', 'Talking DT Leaves Call', 'Non-talking DT Stops Talking', 'Non-talking DT Leaves Call', 'Talking DT Starts Talking', 'Non-talking DT Starts Talking', and 'DT Joins Call'. 'Talking DT Stops Talking' and 'Talking DT Leaves Call' lead to 'decrement no\_of\_talkers', which then leads to a decision 'no\_of\_talkers = 0?'. If 'Yes', it leads to 'No DT Talking No SS Talking'. If 'No', it loops back to the second state. 'SS Requests Uplink', 'Non-talking DT Stops Talking', 'Non-talking DT Leaves Call', 'Talking DT Starts Talking', 'Non-talking DT Starts Talking', and 'DT Joins Call' lead to 'Play Grant Tone', which then leads to 'increment no\_of\_talkers', resulting back in the second state. + +The input signal "xxx DT Starts Talking" where "xxx" is either "Talking" or "Non-Talking" is a shorthand to represent a signal "xxx DT sends Start to Talk sequence" + +The input signal "xxx DT Stops Talking" where "xxx" is either "Talking" or "Non-Talking" is a shorthand to represent a signal "xxx DT sends Stop Talking sequence" + +State transition diagram for process Mute\_Unmute (Sheet 2 of 3). + +Figure 1a: Handling of Mute/Unmute Requests in Anchor MSC (Sheet 2 of 3) + +![State transition diagram for process Mute_Unmute (Sheet 3 of 3).](036c200da9b64c3eb5aae2d67bb53e1f_img.jpg) + +process Mute\_Unmute + +3(3) + +The diagram shows two main states: 'No DT Talking No SS Talking' and 'A DT Talking SS Talking Downlink Unmuted'. Transitions from the first state include 'DT Stops Talking', 'DT Leaves Call', 'DT Joins Call', 'DT Starts Talking', and 'SS Requests Uplink'. 'DT Joins Call', 'DT Starts Talking', and 'SS Requests Uplink' lead to 'Play Grant Tone', which then leads to 'no\_of\_talkers:=1' and 'A DT Talking No SS Talking'. 'DT Stops Talking' and 'DT Leaves Call' lead back to the initial state. Transitions from the second state include 'SS Releases Uplink', 'Talking DT Stops Talking', 'Talking DT Leaves Call', 'Non-talking DT Stops Talking', 'Non-talking DT Leaves Call', 'Talking DT Starts Talking', 'Non-talking DT Starts Talking', and 'DT Joins Call'. 'Talking DT Stops Talking' and 'Talking DT Leaves Call' lead to 'decrement no\_of\_talkers', which then leads to a decision 'no\_of\_talkers = 0?'. If 'Yes', it leads to 'Mute Downlink', resulting in state 'No DT Talking SS Talking Downlink Muted'. If 'No', it loops back to the second state. 'SS Releases Uplink', 'Non-talking DT Stops Talking', 'Non-talking DT Leaves Call', 'Talking DT Starts Talking', 'Non-talking DT Starts Talking', and 'DT Joins Call' lead to 'Play Grant Tone', which then leads to 'increment no\_of\_talkers', resulting back in the second state. + +The input signal "xxx DT Starts Talking" where "xxx" is either "Talking" or "Non-Talking" is a shorthand to represent a signal "xxx DT sends Start to Talk sequence" + +The input signal "xxx DT Stops Talking" where "xxx" is either "Talking" or "Non-Talking" is a shorthand to represent a signal "xxx DT sends Stop Talking sequence" + +State transition diagram for process Mute\_Unmute (Sheet 3 of 3). + +Figure 1a: Handling of Mute/Unmute Requests in Anchor MSC (Sheet 3 of 3) + +![SDL process diagram for Mute_Unmute_handling_Relay_MSC showing state transitions for handling uplink and downlink muting in a relay MSC.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +**process Mute\_Unmute\_handling\_Relay\_MSC** 1(2) + +In the states on the following diagrams: + A DT is a Dispatcher Terminal. + SS is Service Subscriber. + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> NoVGCS: No VGCS + NoVGCS --> Idle + + Idle --> SS_Initiates_VGCS + state SS_Initiates_VGCS <> + note left of SS_Initiates_VGCS: SS first talker +Dedicated channel + SS_Initiates_VGCS --> VGCS_GC_Established_Dedicated + + state VGCS_GC_Established_Dedicated { + direction TB + note left: no muting needed + VGCS_GC_established_Talking_SS_on_dedicated_Ch: VGCS GC established. +Talking SS on dedicated Ch. + } + + VGCS_GC_established_Talking_SS_on_dedicated_Ch --> SS_Releases_Uplink + state SS_Releases_Uplink <> + SS_Releases_Uplink --> no_SS_talker_VGCS_ongoing + + VGCS_GC_established_Talking_SS_on_dedicated_Ch --> change_talking_SS_on_VG_ch + state change_talking_SS_on_VG_ch <> + change_talking_SS_on_VG_ch --> Network_decides + Network_decides --> SS_requests_Uplink_from_RMSC_area + + Idle --> VGCS_setup_from_AMSC + state VGCS_setup_from_AMSC <> + note right of VGCS_setup_from_AMSC: calling SS initiates GC +from A-MSC area or DT +initiates GC. + VGCS_setup_from_AMSC --> VGCS_GC_established + + VGCS_GC_established --> Forward_GCS_from_AMSC_1 + state Forward_GCS_from_AMSC_1 <> + Forward_GCS_from_AMSC_1 --> Uplink_free_1 + state Uplink_free_1 <> + Uplink_free_1 --> no_SS_talker_VGCS_ongoing + + VGCS_GC_established --> Release_from_AMSC_1 + state Release_from_AMSC_1 <> + note right of Release_from_AMSC_1: Release from A-MSC +(SS or DT initiated or +no activity time out) + Release_from_AMSC_1 --> REL_1 + REL_1 --> Idle + + VGCS_GC_established --> Forward_GCS_from_AMSC_2 + state Forward_GCS_from_AMSC_2 <> + Forward_GCS_from_AMSC_2 --> Uplink_busy_1 + state Uplink_busy_1 <> + Uplink_busy_1 --> SS_Talker_in_AMSC_area_1 + + no_SS_talker_VGCS_ongoing --> SS_requests_Uplink_from_RMSC_area + state SS_requests_Uplink_from_RMSC_area <> + SS_requests_Uplink_from_RMSC_area --> Decision_Mute + + Decision_Mute --> Talking_SS_unmuted: no + Decision_Mute --> Mute_Downlink: yes + state Mute_Downlink { + direction TB + Mute_Downlink_Task: Mute Downlink + } + + Mute_Downlink_Task --> Talking_SS_muted + + no_SS_talker_VGCS_ongoing --> acknowledged_by_AMSC + state acknowledged_by_AMSC <> + acknowledged_by_AMSC --> SS_requests_Uplink_from_RMSC_area + + no_SS_talker_VGCS_ongoing --> Release_from_AMSC_2 + state Release_from_AMSC_2 <> + Release_from_AMSC_2 --> REL_2 + REL_2 --> Idle + + no_SS_talker_VGCS_ongoing --> Forward_GCS_from_AMSC_3 + state Forward_GCS_from_AMSC_3 <> + Forward_GCS_from_AMSC_3 --> Uplink_busy_2 + state Uplink_busy_2 <> + Uplink_busy_2 --> SS_Talker_in_AMSC_area_2 + + Mute_Downlink_Task --> mute_downlink_indication_received + state mute_downlink_indication_received <> + note right: mute downlink indication +received from A-MSC +with UplinkRequestAck + mute_downlink_indication_received --> Forward_GCS_from_AMSC_4 + state Forward_GCS_from_AMSC_4 <> + Forward_GCS_from_AMSC_4 --> Uplink_free_2 + state Uplink_free_2 <> + Uplink_free_2 --> no_SS_talker_VGCS_ongoing_2 + + Mute_Downlink_Task --> Release_from_AMSC_3 + state Release_from_AMSC_3 <> + Release_from_AMSC_3 --> REL_3 + REL_3 --> Idle + +``` + +SDL process diagram for Mute\_Unmute\_handling\_Relay\_MSC showing state transitions for handling uplink and downlink muting in a relay MSC. + +Figure 1b: Handling of Mute/Unmute Requests in Relay MSC (Sheet 1 of 2) + +![State transition diagram for Mute/Unmute handling in Relay MSC. The diagram shows two main processes: Mute Downlink and Unmute Downlink. Both start from a 'Talking SS on Voice Group ch in R-MSC area downlink unmuted' state. The Mute Downlink process involves 'command talking SS to mute downlink', 'A-MSC sends Forward_GC_signal', and 'Mute Downlink' action, leading to 'Talking SS on Voice Group ch in R-MSC area downlink muted'. The Unmute Downlink process involves 'command talking SS to unmute downlink', 'A-MSC sends Forward_GC_signal', and 'Unmute Downlink' action, leading back to 'Talking SS on Voice Group ch in R-MSC area downlink unmuted'. Both processes have 'SS Releases Uplink' and 'REL' (Release) options leading to 'no SS talker VGCS onging' and 'Idle' states respectively.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +process Mute\_Unmute\_handling\_Relay\_MSC 2(2) + +``` +stateDiagram-v2 + [*] --> S0: Talking SS on Voice Group ch in R-MSC area downlink unmuted + S0 --> S1: SS Releases Uplink + S0 --> S2: command talking SS to mute downlink + S0 --> S3: A-MSC sends Forward_GC_signal + S0 --> S4: REL + S2 --> S5: Mute Downlink + S5 --> S6: Talking SS on Voice Group ch in R-MSC area downlink muted + S6 --> S7: SS Releases Uplink + S6 --> S8: command talking SS to unmute downlink + S6 --> S9: A-MSC sends Forward_GC_signal + S6 --> S10: REL + S8 --> S11: Unmute Downlink + S11 --> S0 + S1 --> S12: no SS talker VGCS onging + S4 --> S13: Idle + S10 --> S13: Idle +``` + +State transition diagram for Mute/Unmute handling in Relay MSC. The diagram shows two main processes: Mute Downlink and Unmute Downlink. Both start from a 'Talking SS on Voice Group ch in R-MSC area downlink unmuted' state. The Mute Downlink process involves 'command talking SS to mute downlink', 'A-MSC sends Forward\_GC\_signal', and 'Mute Downlink' action, leading to 'Talking SS on Voice Group ch in R-MSC area downlink muted'. The Unmute Downlink process involves 'command talking SS to unmute downlink', 'A-MSC sends Forward\_GC\_signal', and 'Unmute Downlink' action, leading back to 'Talking SS on Voice Group ch in R-MSC area downlink unmuted'. Both processes have 'SS Releases Uplink' and 'REL' (Release) options leading to 'no SS talker VGCS onging' and 'Idle' states respectively. + +Figure 1b: Handling of Mute/Unmute Requests in Relay MSC (Sheet 2 of 2) + +### 11.3.7a Signalling procedures for the user plane + +##### 11.3.7a.1 Group call re-establishment by the BSS + +The MSC and BSC negotiate during the setup of a voice group call whether "group call re-establishment by the BSS" is supported by both entities. + +If "group call re-establishment by the BSS" is supported by both entities or the network uses a transmission architecture with A-interface link sharing, the following procedures apply: + +- i) If the BSS needs to release the group call channel in a cell due to an equipment failure or another BSS-generated reason (e.g. preemption), the BSS shall inform the MSC of the failure with either: + - Uplink Release Indication and VGCS Assignment Status message if the group call channel is serving the current talker; or + - VGCS Assignment Status message if the group call channel is not serving the current talker. + +The terrestrial resource for the group call channel is not released by the MSC. + +- ii) When the condition that caused the failure is subsequently removed, the BSS shall re-allocate a radio resource for the group call channel and inform the MSC of the recovery with a VGCS Assignment Status message. +- iii) If A-interface link sharing is used, each of the VGCS ASSIGNMENT STATUS messages in item (i) and (ii) shall be sent after expiry of timer Tast. + +Otherwise, if "group call re-establishment by the BSS" is not supported by both entities and the network does not use a transmission architecture with A-interface link sharing, the following procedures apply: + +- i) If the BSS needs to release the group call channel in a cell due to an equipment failure or another BSS-generated reason (e.g. preemption), the BSS shall inform the MSC of the failure with either: + - Uplink Release Indication if the group call channel is serving the current talker; or + - Clear Request if the group call channel is not serving the current talker. +- ii) The MSC shall then initiate the clearing of the radio and terrestrial resources for the group call channel. If supported, the MSC may retry the VGCS Assignment procedure for the cell, depending on the reason for release. + +Group call re-establishment by the BSS does not apply to the dedicated link of the talker. If the BSS needs to release the dedicated channel of the talker due to an equipment failure or another BSS-generated reason (e.g. preemption), the BSS shall inform the MSC of the failure with an Uplink Release Indication. The MSC shall then initiate the clearing of the radio and terrestrial resources for the dedicated channel. + +### 11.3.8 Overview of signalling + +In this overview, the messages required to implement the specified concept are identified, and brief details are given of each message. + +A diagrammatic representation of the voice group call message structure proposed and actions required are given in figures 2 to 7j. + +In order to simplify the message flows for voice group call establishment and call termination, the interaction between the MSC and the GCR is only shown for the MSC where the originator of the group call is located or, for the case of a group call originated by a dispatcher, only for the anchor MSC. In all cases, a similar interaction also takes place between the other MSC(s) and associated GCR(s) involved in the group call. + +Summary of figures in this subclause: + +Figure 2: voice group call establishment by a service subscriber roaming in the anchor MSC area; + +Figure 3: voice group call establishment by a service subscriber roaming in the relay MSC area; + +Figure 3a: voice group call establishment by a service subscriber in a RANflex configuration; + +Figure 3b: voice group call establishment by a mobile dispatcher or fixed line dispatcher; + +Figure 3c: Signalling information required for establishing voice group calls by a service subscriber in a RANflex configuration with group call redundancy + +Figure 4: uplink access request in the anchor MSC area without talker priority (uplink free); + +Figure 4a: uplink access request in the anchor MSC area with talker priority "privileged subscriber" (uplink free, subsequent talker on dedicated channel); + +Figure 4b: uplink access request in the anchor MSC area with talker priority "emergency subscriber" (uplink busy, access via group call channel uplink, subsequent talker on dedicated channel); + +Figure 4c: uplink access in the anchor MSC area with "emergency mode reset request" (uplink busy, access via group call channel uplink); + +Figure 4d: uplink access request in the anchor MSC area with talker priority "privileged subscriber" (uplink busy, access via RACH, subsequent talker on group call channel uplink); + +Figure 4e: uplink access in the anchor MSC area with "emergency mode reset request" (uplink busy, access via RACH); + +Figure 5: uplink access request in the relay MSC area without talker priority (uplink free); + +Figure 5a: uplink access request in the relay MSC area with talker priority "privileged subscriber" (uplink busy, access via RACH, subsequent talker on group call channel uplink); + +Figure 5b: dispatcher indicates wish to speak, talker attached to the anchor MSC; + +Figure 5c: dispatcher indicates wish to speak, talker attached to the relay MSC; + +Figure 5d: mobile dispatcher roaming in a non-Anchor MSC area indicates wish to speak, talker attached to the anchor MSC; + +Figure 6: uplink release requested by the network; + +Figure 6a: uplink release requested by the network; preemption of the current talker by a privileged talker; + +Figure 6b: uplink release, talker on a dedicated link (normal case); + +Figure 6c: uplink release, talker on a dedicated link (loss of radio contact or equipment failure (TRX, PCM, ...)); + +Figure 6d: uplink release, talker on group call channel (normal case); + +Figure 6e: uplink release, talker on group call channel (loss of radio contact); + +Figure 6f: uplink release, talker on group call channel (equipment failure (TRX, PCM, ...)), group call re-establishment by the BSS not supported; + +Figure 6g: release after equipment failure (TRX, PCM, ...) concerning a cell not serving the talker, group call re-establishment by the BSS not supported; + +Figure 6h: A-interface link sharing used or group call re-establishment by the BSS supported: Uplink release for the talker on group call channel after equipment failure (TRX, PCM ...) + +Figure 6i: A-interface link sharing used or group call re-establishment by the BSS supported: Release after equipment failure (TRX, PCM, ...) concerning a cell not serving the talker; + +Figure 6j: A-interface link sharing used or group call re-establishment by the BSS supported: Release after equipment failure concerning the link between MSC and BSS; + +Figure 7: termination of the group call by the calling service subscriber; + +Figure 7a: voice group call establishment by a service subscriber using immediate setup; + +Figure 7b: signalling for DTMF digit entry by an entitled mobile dispatcher controlled by the anchor MSC; + +Figure 7c: signalling for DTMF digit entry by an entitled mobile dispatcher controlled by a visited MSC; + +Figure 7d: signalling for DTMF digit entry by an entitled fixed line dispatcher; + +Figure 7e: Validation of Priority Uplink Requests for a ciphered group call; + +Figure 7f: A listener in the anchor MSC area sends application-specific data to the other group call members, while the group call channel uplink in the cell is free; + +Figure 7g: A talker in the anchor MSC area sends application-specific data to the other group call members; + +Figure 7h: A listener in a relay MSC area sends application-specific data to the other group call members, while the group call channel uplink in the cell is free; + +Figure 7i: After receiving application-specific data, a service subscriber in the anchor MSC area sends a confirmation for the received data to the other group call members, while the group call channel uplink in the cell is free; + +Figure 7j: A listener in the anchor MSC area sends application-specific data that is not time-critical via RACH to the other group call members, while the talker is using the group call channel uplink in the same cell. + +![Sequence diagram showing the interaction between MS', MSs, BSS, MSC-A, VLR, GCR, FNT, and MSC-R for a group call setup and modification procedure.](90df9788d66ecf65abf861caf76be5ca_img.jpg) + +``` + +sequenceDiagram + participant MS_prime as MS' + participant MSs as MSs + participant BSS as BSS + participant MSC_A as MSC-A + participant VLR as VLR + participant GCR as GCR + participant FNT as FNT + participant MSC_R as MSC-R + + Note over MS_prime, BSS: [SYS_INFO (NCH allocated)] + BSS-->>MS_prime: + MS_prime->>BSS: RACH (CHAN_REQ) + BSS->>MS_prime: IMM_ASS + MS_prime->>BSS: SABM (SERV_REQ) + BSS->>MSC_A: COM_L3_INFO + MSC_A->>VLR: PROC_ACC_REQ + BSS->>MS_prime: UA (SERVICE_REQ) + VLR->>MSC_A: PROC_ACC_ACK + Note over MS_prime, MSC_A: Authentication & Ciphering + Note over MS_prime, MSC_A: SETUP + Note right of MSC_A: Txx + MSC_A->>GCR: SEND_INFO_OUT + GCR->>MSC_A: COMPLETE_CALL + MSC_A->>GCR: GCR_INT + GCR->>MSC_A: GCR_INT_ACK + MSC_A->>BSS: ASS_REQ + BSS->>MS_prime: CH_MOD_MODFY + MS_prime->>BSS: CH_MOD_MODFY_ACK + BSS->>MSC_A: ASS_COMP + +``` + +Sequence diagram showing the interaction between MS', MSs, BSS, MSC-A, VLR, GCR, FNT, and MSC-R for a group call setup and modification procedure. + +![Sequence diagram showing message exchange for VGCS setup between multiple network entities.](7ed5d5770331f31ade15439a21c31425_img.jpg) + +``` + +sequenceDiagram + participant A as + participant B as + participant C as + participant D as + participant E as + participant F as + participant G as + participant H as + participant I as + participant J as + + Note over A,D: Left Section + Note over E,J: Right Section + + C->>D: VGCS_SETUP + E->>H: SETUP (to FN) + D-->>C: VGCS_SETUP_ACK + E->>I: PREPARE_GROUP_CALL + C->>D: VGCS_ASS_REQUEST + I-->>E: PREPARE_GROUP_CALL_ACK + D-->>C: VGCS_AREA_CELL_INFO + E->>I: SETUP (to MSC-R) + I-->>E: CONNECT (from MSC-R) + +``` + +Sequence diagram showing message exchange for VGCS setup between multiple network entities. + +![Sequence diagram showing network signaling between MS', MSs, BSS, MSC-A, VLR, GCR, FNT, and MSC-R. The diagram illustrates call setup and release procedures including VGCS assignment, notifications, uplink management, and channel release.](3337af75dfee8af7687b4f49914d6c93_img.jpg) + +``` + +sequenceDiagram + participant MS_prime as MS' + participant MSs as MSs + participant BSS as BSS + participant MSC_A as MSC-A + participant VLR as VLR + participant GCR as GCR + participant FNT as FNT + participant MSC_R as MSC-R + + BSS->>MSC_A: VGCS_ASS_RESULT + MSC_A->>FNT: SEND GROUP CALL END SIGNAL + Note over BSS, MSC_A: Tast + MSC_A-->>BSS: + FNT->>MSC_A: FORWARD_GROUP_CALL_SIGNALLING (IMSI, add info) + BSS->>MSC_A: VGCS_ASS_STATUS + MSC_A-->>FNT: + BSS->>MSs: NOTIFY_REQ (NCH) + FNT->>MSC_A: CONNECT (from FN) + BSS->>MSs: NOTIFY_REQ (FACCH) + MSC_A-->>FNT: + MSC_A->>BSS: UPLINK_SEIZED_CMD + BSS->>MSs: UPLINK_BUSY + BSS->>MS_prime: CONNECT + MSC_A->>BSS: VGCS_ADD_INFO + BSS->>MSs: ADD_INFO + BSS->>MSs: Periodic ADD_INFO (SACCH) + BSS->>MSs: PERIODIC NOTIF_REQ (NCH) + BSS->>MSs: Periodic SACCH Info + + Note over MS_prime, MSC_R: -------------------------------------------------------------------------------- + + MSs->>BSS: UPLINK_RELEASE (NOTE 4a) + BSS->>MSC_A: UPLINK_RELEASE_IND + MSC_A->>FNT: FORW._GROUP CALL_SIGNAL. (uplink rel ind) + FNT-->>MSC_A: + BSS->>MSs: CHAN_RELEASE + MSC_A->>BSS: CLR_CMD + BSS->>MSs: DISC + BSS->>MSC_A: CLR_COMP + +``` + +Sequence diagram showing network signaling between MS', MSs, BSS, MSC-A, VLR, GCR, FNT, and MSC-R. The diagram illustrates call setup and release procedures including VGCS assignment, notifications, uplink management, and channel release. + +NOTE: MS' = calling service subscriber mobile station; +MSs = destination service subscriber mobile stations; +FNT = fixed network user terminal; +MSC-A = anchor MSC; +MSC-R = relay MSC. + +**Figure 2: Signalling information required for establishing voice group calls by a service subscriber roaming in the anchor MSC area** + +**SYS\_INFO (NCH allocated):** Message used to indicate if the NCH is allocated on the CCCH in the cell. + +**Initial RACH CHAN\_REQ:** Standard message. + +**IMM\_ASS:** Standard message sent on the AGCH. + +**SERV\_REQ (voice group call):** Modified form of the current call request message L3-MM CM SERVICE REQUEST sent on the allocated channel. Teleservice Voice group call is indicated. + +**UA (SERV\_REQ):** This message is used to acknowledge the layer 2 link and provide contention resolution of the service request. + +**COM\_L3\_INFO:** The MSC is provided with initial information about the voice group call. + +NOTE 1: Messages flows for authentication and ciphering are not represented although performed as normal. + +**PROC\_ACC\_REQ:** The MAP\_PROCESS\_ACC\_REQ message is sent to the VLR to check the requested VGCS teleservice against the subscription data. + +**PROC\_ACC\_ACK:** The MAP\_PROCESS\_ACC\_ACK message acknowledges the requested service. + +**Authentication and Ciphering:** Authentication and Ciphering may be performed. Acknowledgement of the service request can also be performed by sending the CM SERVICE ACCEPT. + +**SETUP:** The MSC is provided with details about the voice group call. Optionally this message may contain a talker priority. + +NOTE 2: Alternatively, an IMMEDIATE\_SETUP may have been sent as the initial message including all details of the voice group call. In this case no SETUP message must be sent. + +**SEND\_INFO\_OUT:** The requested group ID is transferred to the VLR in the MAP\_SEND\_INFO\_FOR\_OUTGOING\_CALL message. + +**COMPLETE\_CALL:** The VLR returns the MAP\_COMPLETE\_CALL message confirming the use of the requested group ID. The VLR also returns additional information about the calling service subscriber, if available. + +**GCR\_INT:** The group call attributes are requested from the GCR through the GCR Interrogation message sent by the MSC. + +**GCR\_INT\_ACK:** The requested information is returned from the GCR in the GCR Interrogation Ack message. + +**ASSIGNMENT\_REQUEST:** Standard message. + +**CHAN\_MOD\_MODFY:** Standard message to modify the channel mode in case of very early assignment. + +**CHAN\_MOD\_MODFY\_ACK:** Standard message to acknowledge the modification of the channel mode. + +**ASSIGNMENT\_COMPLETE:** Standard message. + +NOTE 3: Alternatively, early assignment or OACSU procedures might be applied with the corresponding assignment messages not presented in figure 2. + +**VGCS\_SETUP:** This message is sent from the MSC to all affected BSCs, [one dedicated message for each BSC,] including the group call reference with the eMLPP priority, and optionally the call priority. + +**VGCS\_SETUP\_ACK:** Acknowledgement message from the affected BSC in answer to the VGCS\_SETUP message. If the setup is not successful, a VGCS\_SETUP\_REFUSE message shall be sent instead. + +**VGCS\_ASSIGNMENT\_REQ:** This message is sent from the MSC to all affected BSCs, [one dedicated message for every requested channel in a cell] including the group call reference, the channel type and possibly the call priority and details on the ciphering. + +NOTE 4: As an operator option the voice group call channels, the links to them and optionally also the links to dispatchers can already be established and permanently reserved in order to speed up the call set-up for emergency voice group calls. + +In case of A-interface link sharing this message shall contain a list of all cells in the group call area served by this BSC. If the entire list of cell identifiers does not fit into the message, one or more VGCS AREA CELL INFO messages with additional cell identifier lists shall be sent. If the cell of origin is served by this BSC, the cell shall be included in the VGCS ASSIGNMENT REQUEST message. + +**VGCS\_AREA\_CELL\_INFO:** This message shall contain the cell IDs that did not fit into the VGCS ASSIGNMENT REQUEST message in case of A-interface link sharing. + +**VGCS\_ASSIGNMENT RESULT:** Acknowledgement message from the affected BSC in answer to the assignment requests. If the assignment is not successful, a VGCS\_ASSIGNMENT\_FAILURE message shall be sent instead. + +In case of A-interface link sharing this message shall be sent as soon as a channel could be established to the cell of origin or, if the cell of origin is not served by this BSC, to any other cell. Then timer Tast shall be started. + +**Tast:** In a network supporting A-interface link sharing timer Tast shall be used to measure the duration between periodic reports from the BSC to the MSC of Group Call Area cells for which channels have been assigned or released since the last periodic report. When timer Tast expires, if new cells in the Group Call Area have been established or existing ones have been released, pre-empted or failed, the MSC shall be informed of the changes (see subclause 7.1b). Timer Tast shall be started again to measure the period of time until the next report. The timer shall be stopped when the call is released. + +**VGCS\_ASSIGNMENT\_STATUS:** This message shall be sent in case of A-interface link sharing from the BSC to inform the MSC about the status of the channel establishment to the cells of a given VGCS call. This message shall be sent after timer Tast expires and new channels are established or existing channels were released, pre-empted or failed. This message shall also be immediately sent, and Tast restarted, when all cells for a given group call area served by the BSC are established, indicating this. + +**SETUP to fixed network users:** Based on the information determined about the users of external networks to be involved in the call, the MSC shall initiate calls to these users in the normal manner, depending on their mode of connection into the MSC, and shall connect them into the conference bridge. Alternatively normal calls to GSM subscribers may be established for dispatchers being GSM subscribers which are not presented in the diagram. + +**PREPARE\_GROUP\_CALL:** The group call attributes are sent to every relay MSC and a Group Call number for call set-up to is requested. + +**PREPARE\_GROUP\_CALL\_ACK:** The Group Call number for call set-up is returned to the anchor MSC. + +**SETUP to MSC-R:** The ISUP connection is set-up to the relay MSC. + +**CONNECT from MSC-R:** Set-up of the ISUP connection to the relay MSC is confirmed. + +**SEND\_GROUP\_CALL\_END\_SIGNAL:** Indicates to the anchor MSC that at least one voice group call channel has been established in the relay MSC area. + +**FORWARD\_GROUP\_CALL\_SIGNALLING (IMSI, additional info):** The IMSI of the service subscriber who has established the voice group call and who is allowed to terminate the call is sent to every relay MSC. If the network supports the use of talker priorities, the message includes also the talker priority. Furthermore, the message provides additional information about the current talking service subscriber, if available. + +**Txx:** Timer implemented in the MSC which is started with receipt of the SETUP message from the calling service subscriber. If the timer expires before the conditions for establishment have been met, as per subclause 11.3.1.1.2, then the call shall be released. + +**NOTIF\_REQ (NCH):** Messages for notification which contain the group call reference, the priority of the call if eMLPP is applied, and possibly the channel description of the voice group call channel to which the mobile stations shall listen and the number of the group key used for ciphering. + +**NOTIF\_REQ (FACCH):** Message for notification sent on the FACCH to the mobile stations currently involved in other calls. The notification on the FACCH shall include the group call reference, and the priority level and may also include the channel description and the group ciphering key numbers. + +**UPLINK\_SEIZED\_CMD:** If the network supports the use of talker priorities, this message informs the BSS about the talker priority of the current talking service subscriber and about the status of the emergency mode. The MSC may also include additional information about the current talking service subscriber, if the information is available when sending this message. + +**UPLINK\_BUSY:** If the network supports the use of talker priorities, this connectionless RR message is sent on the downlink FACCH to inform all mobile stations about the talker priority of the current talking service subscriber and about the status of the emergency mode. The network may also include additional information about the current talking service subscriber, if the information is available when sending this message and there is sufficient space available in the message. The message is repeated on the FACCH every T1 seconds. + +**VGCS\_ADD\_INFO:** The MSC sends additional information about the current talking service subscriber to all BSCs, unless the information was already included in the UPLINK\_SEIZED\_CMD message. + +**ADD\_INFO:** The BSCs broadcast the additional information on the FACCH to all listeners. , unless the information was already included in the UPLINK\_BUSY message + +**Periodic ADD\_INFO (SACCH):** The message is repeated on the SACCH every T2 seconds. + +**Periodic NOTIF\_REQ (NCH):** The notifications are sent periodically so that mobile stations moving into the area can join the voice group call. + +**Periodic SACCH Info:** Periodic messages sent on SACCH. This message may include: + +- information of changes of notifications; +- information used for cell re-selection. + +**CONNECT:** Information to the mobile station of the calling service subscriber that the VGCS is established with the related group call reference as the connected number. The CONNECT message is sent as soon as conditions for establishment are met, as per subclause 11.3.1.1.2. If the SETUP message from the calling subscriber contained a talker priority, the MSC returns the talker priority used by the network. This will be lower than the requested talker priority, if the subscription check for the requested talker priority was unsuccessful. + +**UPLINK\_RELEASE:** When the calling service subscriber wants to become a listening service subscriber for the first time, a message indicating release of the uplink is required to be sent from the MS to the BSS in order to set the uplink free. + +NOTE 4a: For different cases of uplink release and the related message flows refer to Figure 6.b to 6.g. + +**UPLINK\_RELEASE\_INDICATION:** The BSS informs the MSC on the uplink release. + +**FORWARD\_GROUP\_CALL\_SIGNALLING (uplink release indication):** This message is sent to every relay MSC to indicate that the uplink is free. + +**CLEAR COMMAND :** The MSC requests the BSS to clear radio and terrestrial resources associated with originator dedicated link if not already done. + +**CHAN\_RELEASE:** The BSS sends a channel release message to the calling service subscriber's mobile station including the channel description of the voice group call channel to which the mobile station shall tune to. + +NOTE 5: Alternatively, if no UPLINK\_RELEASE has been sent to the network by the mobile station, the network may transfer the mobile station to the voice group call channel by the channel mode modify procedure or by an assignment procedure or by a handover procedure. + +**DISC:** Two layer 2 disconnect messages shall be sent by the mobile station to the network. + +![Sequence diagram showing network signaling between MS', MSs, BSS, MSC-R, VLR, GCR, and MSC-A. The diagram includes messages such as SYS_INFO, RACH, IMM_ASS, SABM, COM_L3_INFO, UA, Authentication & Ciphering, SETUP, PROCEDURE_ACC_REQUIREMENT, PROC_ACC_ACK, SEND_INFO_OUT, COMPLETE_CALL, GCR_INT, GCR_INT_ACK, ASS_REQ, CH_MOD_MODFY, CH_MOD_MODFY_ACK, ASS_COMP, SETUP (to MSC-A), PREPARE_GROUP_CALL, ALLOCATE GROUP CALL NUMBER, and PREPARE_GROUP_CALL_ACK.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +``` + +sequenceDiagram + participant MS_prime as MS' + participant MSs as MSs + participant BSS as BSS + participant MSC_R as MSC-R + participant VLR as VLR + participant GCR as GCR + participant MSC_A as MSC-A + + Note left of MS_prime: [SYS_INFO (NCH allocated)] + MSs->>MS_prime: + MS_prime->>BSS: RACH (CHAN_REQ) + BSS->>MS_prime: IMM_ASS + MS_prime->>BSS: SABM (SERV_REQ) + BSS->>MSC_R: COM_L3_INFO + MSC_R->>VLR: PROCEDURE_ACC_REQUIREMENT + VLR->>MSC_R: PROC_ACC_ACK + Note left of MS_prime: Authentication & Ciphering + MSs->>MS_prime: + MS_prime->>BSS: SETUP + BSS->>MSC_R: + MSC_R->>VLR: SEND_INFO_OUT + VLR->>MSC_R: COMPLETE_CALL + MSC_R->>GCR: GCR_INT + GCR->>MSC_R: GCR_INT_ACK + Note right of GCR: + BSS->>MSC_R: ASS_REQ + MSC_R->>BSS: CH_MOD_MODFY + BSS->>MSC_R: CH_MOD_MODFY_ACK + MSC_R->>BSS: ASS_COMP + MSC_R->>MSC_A: SETUP (to MSC-A) + Note right of MSC_A: Txx + MSC_A->>MSC_R: PREPARE_GROUP_CALL + MSC_R->>GCR: GCR_INT + GCR->>MSC_R: GCR_INT_ACK + MSC_R->>GCR: ALLOCATE GROUP CALL NUMBER + GCR->>MSC_R: ALLOCATE GROUP CALL NUMBER ACK + MSC_R->>MSC_A: PREPARE_GROUP_CALL_ACK + +``` + +Sequence diagram showing network signaling between MS', MSs, BSS, MSC-R, VLR, GCR, and MSC-A. The diagram includes messages such as SYS\_INFO, RACH, IMM\_ASS, SABM, COM\_L3\_INFO, UA, Authentication & Ciphering, SETUP, PROCEDURE\_ACC\_REQUIREMENT, PROC\_ACC\_ACK, SEND\_INFO\_OUT, COMPLETE\_CALL, GCR\_INT, GCR\_INT\_ACK, ASS\_REQ, CH\_MOD\_MODFY, CH\_MOD\_MODFY\_ACK, ASS\_COMP, SETUP (to MSC-A), PREPARE\_GROUP\_CALL, ALLOCATE GROUP CALL NUMBER, and PREPARE\_GROUP\_CALL\_ACK. + + + +![](575d7d345b3ec04393bb2ec720ebabca_img.jpg) + +Sequence diagram illustrating the interaction between MS', MSs, BSS, MSC-R, VLR, GCR, and MSC-A. + +``` + +sequenceDiagram + participant MSs + participant BSS + participant MSC-R + participant VLR + participant GCR + participant MSC-A + + Note left of MSs: MS' + MSC-A->>MSC-R: SETUP (from MSC-A) + MSC-R-->>MSC-A: RELEASE GROUP CALL NUMBER + BSS->>MSC-R: VGCS_SETUP + MSC-R-->>BSS: VGCS_SETUP_ACK + BSS->>MSC-R: VGCS_ASS_REQ + MSC-R-->>BSS: VGCS_AREA_CELL_INFO + BSS->>MSC-R: VGCS_ASS_RESULT + Note right of BSS: Tast + BSS->>MSC-R: CONNECT (to MSC-A) + MSC-R-->>BSS: VGCS_ASS_STATUS + BSS->>MSC-R: NOTIFY_REQ (NCH) + MSC-R-->>BSS: NOTIFY_REQ (FACCH) + MSC-R-->>MSC-A: SEND_GROUP CALL_END_SIGNAL (IMSI, add info) + BSS->>MSC-R: UPLINK_SEIZED_CMD + MSC-R-->>BSS: UPLINK_BUSY + MSC-R-->>MSC-A: CONNECT (from MSC-A) + MSC-A-->>BSS: PERIODIC NOTIF_REQ (NCH) + BSS->>MSC-R: Periodic SACCH Info + BSS->>MSC-R: VGCS_ADD_INFO + MSC-R-->>BSS: ADD_INFO + BSS->>MSC-R: Periodic ADD_INFO (SACCH) + BSS->>MSC-R: UPLINK_RELEASE (NOTE 9a) + BSS->>MSC-R: UPLINK_RELEASE_IND + MSC-R-->>MSC-A: PROCESS_GROUP_CALL_SIGNAL. (uplink rel ind) + MSC-A-->>MSC-R: RELEASE (from MSC-A) + MSs->>BSS: CHAN_RELEASE + BSS->>MSC-R: CLR_CMD + +``` + +![Diagram illustrating signalling information required for establishing voice group calls. It shows a sequence of messages: DISC and CLR_COMP. The DISC message is shown with two dashed lines between two vertical bars (representing mobile stations). The CLR_COMP message is shown with a dashed arrow pointing from a vertical bar to another vertical bar. There are also several empty vertical bars representing other mobile stations or network elements.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +Diagram illustrating signalling information required for establishing voice group calls. It shows a sequence of messages: DISC and CLR\_COMP. The DISC message is shown with two dashed lines between two vertical bars (representing mobile stations). The CLR\_COMP message is shown with a dashed arrow pointing from a vertical bar to another vertical bar. There are also several empty vertical bars representing other mobile stations or network elements. + +NOTE: MS' = calling service subscriber mobile station; + MSs = destination service subscriber mobile stations; + MSC-A = anchor MSC; + MSC-R = relay MSC + +**Figure 3: Signalling information required for establishing voice group calls by a service subscriber roaming in the relay MSC area** + +**SYS\_INFO (NCH allocated):** Message used to indicate if the NCH is allocated on the CCCH in the cell. + +**Initial RACH CHAN\_REQ:** Standard message. + +**IMM\_ASS:** Standard message sent on the AGCH. + +**SERV\_REQ (voice group call):** Modified form of the current call request message L3-MM CM SERVICE REQUEST sent on the allocated channel. Teleservice Voice group call is indicated. + +**UA (SERV\_REQ):** This message is used to acknowledge the layer 2 link and provide contention resolution of the service request. + +**COM\_L3\_INFO:** The MSC is provided with initial information about the voice group call. + +NOTE 6: Messages flows for authentication and ciphering are not represented although performed as normal. + +**PROC\_ACC\_REQ:** The MAP\_PROCESS\_ACC\_REQ message is sent to the VLR to check the requested VGCS teleservice against the subscription data. + +**PROC\_ACC\_ACK:** The MAP\_PROCESS\_ACC\_ACK message acknowledges the requested service. + +**Authentication & Ciphering:** Authentication and Ciphering may be performed. Acknowledgement of the service request can also be performed by sending the CM SERVICE ACCEPT. + +**SETUP:** The MSC is provided with details about the voice group call. Optionally this message may contain a talker priority. + +NOTE 7: Alternatively, an IMMEDIATE\_SETUP may have been sent as the initial message including all details of the voice group call. In this case no SETUP message must be sent. + +**SEND\_INFO\_OUT:** The requested group ID is transferred to the VLR in the MAP\_SEND\_INFO\_FOR\_OUTGOING\_CALL message. + +**COMPLETE\_CALL:** The VLR returns the MAP\_COMPLETE\_CALL message confirming the use of the requested group ID. The VLR also returns additional information about the calling service subscriber, if available. + +**GCR\_INT:** The group call attributes are requested from the GCR through the GCR Interrogation message sent by the MSC. + +**GCR\_INT\_ACK:** The requested information (MSC-A address) is returned from the GCR in the GCR Interrogation Ack message. + +**ASSIGNMENT\_REQUEST:** Standard message. + +**CHAN\_MOD\_MODFY:** Standard message to modify the channel mode in case of very early assignment. + +**CHAN\_MOD\_MODFY\_ACK:** Standard message to acknowledge the modification of the channel mode. + +**ASSIGNMENT\_COMPLETE:** Standard message. + +NOTE 8: Alternatively, early assignment or OACSU procedures might be applied with the corresponding assignment messages not presented in figure 3. + +**SETUP to MSC-A:** Based on information received from the GCR the relay MSC shall set-up a dedicated connection for the calling service subscriber to the anchor MSC. The VGCS prefix plus group call reference shall be sent as calling party number, and the address of the calling service subscriber's relay MSC shall be sent as generic number parameter, with the number qualifier indicator set to "additional calling party number". + +**PREPARE\_GROUP\_CALL:** The group call attributes (parts) are received from the anchor MSC. + +**GCR\_INT:** The group call attributes are requested from the GCR through the GCR Interrogation message sent by the MSC. + +**GCR\_INT\_ACK:** The requested information (cell list) is returned from the GCR in the GCR Interrogation Ack message. + +**ALLOCATE GROUP CALL NUMBER:** The Group Call number is requested from the VLR. + +**ALLOCATE GROUP CALL NUMBER ACK:** The Group Call number is returned from the VLR. + +**PREPARE\_GROUP\_CALL\_ACK:** The Group Call number is sent to MSC-A. + +**SETUP from MSC-A:** The ISUP connection is set-up between MSC-A and MSC-R. + +**RELEASE GROUP CALL NUMBER:** The VLR is requested to release the Group Call number. + +**VGCS\_SETUP:** This message is sent from the MSC to all affected BSCs, [one dedicated message for each BSC,] including the group call reference with the eMLPP priority, and optionally the call priority. + +**VGCS\_SETUP\_ACK:** Acknowledgement message from the affected BSC in answer to the VGCS\_SETUP setup message. If the setup is not successful, a VGCS\_SETUP\_REFUSE message shall be sent instead. + +**VGCS\_ASSIGNMENT\_REQ:** This message is sent from the MSC to all affected BSCs, [one dedicated message for every requested channel in a cell,] including the group call reference, the channel type and possibly the call priority and details on the ciphering. + +NOTE 9: As an operator option the voice group call channels, the links to them and optionally also the links to dispatchers can already be established and permanently reserved in order to speed up the call set-up for emergency voice group calls. + +In case of A-interface link sharing this message shall contain a list of all cells in the group call area served by this BSC. If the entire list of cell identifiers does not fit into the message, one or more VGCS AREA CELL INFO messages with additional cell identifier lists shall be sent. If the cell of origin is served by this BSC, the cell shall be included in the VGCS ASSIGNMENT REQUEST message. + +**VGCS\_AREA\_CELL\_INFO:** This message shall contain the cell IDs that did not fit into the VGCS ASSIGNMENT REQUEST message in case of A-interface link sharing. + +**VGCS\_ASSIGNMENT\_RESULT:** Acknowledgement message from the affected BSC in answer to the assignment requests. If the assignment is not successful, a VGCS\_ASSIGNMENT\_FAILURE message shall be sent instead. + +In case of A-interface link sharing this message shall be sent as soon as a channel could be established to the cell of origin or, if the cell of origin is not served by this BSC, to any other cell. Then timer Tast shall be started. + +**Tast:** In a network supporting A-interface link sharing timer Tast shall be used to measure the duration between periodic reports from the BSC to the MSC of Group Call Area cells for which channels have been assigned or released since the last periodic report. When timer Tast expires, if new cells in the Group Call Area have been established or existing ones have been released, pre-empted or failed the MSC shall be informed of the changes (see subclause 7.1b). Timer Tast shall be started again to measure the period of time until the next report. The timer shall be stopped when the call is released. + +**VGCS\_ASSIGNMENT\_STATUS:** This message shall be sent in case of A-interface link sharing from the BSC to inform the MSC about the status of the channel establishment to the cells of a given VGCS call. This message shall be sent after timer Tast expires and new channels are established or existing channels are released, pre-empted or failed. This message shall also be immediately sent, and Tast restarted, when all cells for a given group call area served by the BSC are established, indicating this. + +**CONNECT to MSC-A:** Set-up of the ISUP connection from the anchor MSC is confirmed. + +**SEND\_GROUP\_CALL\_END\_SIGNAL (IMSI, additional info):** Indicates to the anchor MSC that conversation can start. In addition the IMSI of calling service subscriber who has established the voice group call and who is allowed to terminate the call is included. If the network supports the use of talker priorities, the message includes also the talker priority. Furthermore, the message provides additional information about the current talking service subscriber, if available. + +**NOTIF\_REQ (NCH):** Messages for notification which contain the group call reference, the priority of the call if eMLPP is applied, and possibly the channel description of the voice group call channel to which the mobile stations shall listen and the number of the group key used for ciphering. + +**NOTIF\_REQ (FACCH):** Message for notification sent on the FACCH to the mobile stations currently involved in other calls. The notification on the FACCH shall include the group call reference, and the priority level and may include also the channel description and the group ciphering key numbers. + +**UPLINK\_SEIZED\_CMD:** If the network supports the use of talker priorities, this message informs the BSS about the talker priority of the current talking service subscriber and about the status of the emergency mode. The MSC may also include additional information about the current talking service subscriber, if the information is available when sending this message. + +**UPLINK\_BUSY:** If the network supports the use of talker priorities, this connectionless RR message is sent on the downlink FACCH to inform all mobile stations about the talker priority of the current talking service subscriber and about the status of the emergency mode. The network may also include additional information about the current talking service subscriber, if the information is available when sending this message and there is sufficient space available in the message. The message is repeated on the FACCH every T1 seconds. + +**VGCS\_ADD\_INFO:** The MSC sends additional information about the current talking service subscriber to all BSCs, unless the information was already included in the UPLINK\_SEIZED\_CMD message. + +**ADD\_INFO:** The BSCs broadcast the additional information on the FACCH to all listeners, unless the information was already included in the UPLINK\_BUSY message. + +**Periodic ADD\_INFO (SACCH):** The message is repeated on the SACCH every T2 seconds. + +**Periodic NOTIF\_REQ (NCH):** The notifications are sent periodically so that mobile stations moving into the area can join the voice group call. + +**Periodic SACCH Info:** Periodic messages sent on the downlink of the SACCH informing mobile stations of: + +- information of changes of notifications; +- information used for cell re-selection. + +**CONNECT (from MSC-A):** Call set-up of the dedicated connection for the calling service subscriber is confirmed. + +**CONNECT:** Information to the mobile station of the calling service subscriber that the VGCS is established with the related group call reference as the connected number. The CONNECT message is sent as soon as conditions for establishment are met, as per subclause 11.3.1.1.2. If the SETUP message from the calling subscriber contained a talker priority, the MSC returns the talker priority used by the network. This will be lower than the requested talker priority, if the subscription check for the requested talker priority was unsuccessful. + +**UPLINK\_RELEASE:** When the calling service subscriber wants to become a listening service subscriber for the first time, a message indicating release of the uplink is required to be sent from the MS to the BSS in order to set the uplink free. + +NOTE 9a: For different cases of uplink release and the related message flows refer to Figure 6.b to 6.g. + +**UPLINK\_RELEASE\_INDICATION:** The BSS informs the MSC on the uplink release. + +**PROCESS\_GROUP\_CALL\_SIGNALLING (uplink release indication):** To indicate to the anchor MSC that the uplink is free. + +**CLEAR\_COMMAND:** The MSC requests the BSS to clear radio and terrestrial resources associated with originator dedicated link if not already done. + +**CHAN\_RELEASE:** The BSS sends a channel release message to the calling service subscriber's mobile station including the channel description of the voice group call channel to which the mobile station shall tune to. + +NOTE 10: Alternatively, if no UPLINK\_RELEASE has been sent to the network by the mobile station, the network may transfer the mobile station to the voice group call channel by the channel mode modify procedure or by an assignment procedure or by a handover procedure. + +**DISC:** Two layer 2 disconnect messages shall be sent by the mobile station to the network. + +**RELEASE from MSC-A:** The dedicated connection for the calling service subscriber is released with cause 'normal, unspecified'. + +![Sequence diagram showing network signaling between MS', MSs, BSS, V-MSC, VLR, VGCS S-MSC = MSC-R, GCR, and MSC-A.](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +``` +sequenceDiagram + participant MS' + participant MSs + participant BSS + participant V-MSC + participant VLR + participant VGCS_S-MSC as VGCS S-MSC = MSC-R + participant GCR + participant MSC-A + + Note left of MS': [SYS_INFO (NCH allocated)] + MS'->>MSs: RACH (CHAN_REQ) + MSs->>BSS: IMM_ASS + BSS->>MS': SABM (SERV_REQ) + BSS->>V-MSC: COM_L3_INFO + V-MSC->>VLR: PROCESS_ACC_REQUEST + VLR->>MS': UA (SERV_REQ) + V-MSC->>VLR: PROC_ACC_ACK + V-MSC->>MS': AUTHENTICATION & Ciphering + MSs->>V-MSC: SETUP + V-MSC->>VLR: SEND_INFO_OUT + V-MSC->>MS': COMPLETE_CALL + V-MSC->>VGCS_S-MSC: SEND_GROUP_CALL_INFO + VGCS_S-MSC->>GCR: GCR_INT + GCR->>VGCS_S-MSC: GCR_INT_ACK + VGCS_S-MSC->>V-MSC: SEND_GROUP_CALL_INFO_ACK + Note right of VGCS_S-MSC: Start T3 + V-MSC->>BSS: ASS_REQ + BSS->>MS': CH_MOD_MODIFY + MS'->>BSS: CH_MOD_MODIFY_ACK + BSS->>V-MSC: ASS_COMP + V-MSC->>MSC-A: SETUP (to MSC-A) + Note right of VGCS_S-MSC: Stop T3 + VGCS_S-MSC->>MSC-A: PREPARE_GROUP_CALL +``` + +Sequence diagram showing network signaling between MS', MSs, BSS, V-MSC, VLR, VGCS S-MSC = MSC-R, GCR, and MSC-A. + +![Sequence diagram showing network interactions between MS', MSs, BSS, V-MSC, VLR, VGCS S-MSC = MSC-R, GCR, and MSC-A.](0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg) + +The sequence diagram illustrates the following interactions: + +- VGCS S-MSC = MSC-R** sends **GCR\_INT** to **GCR**. +- GCR** responds with **GCR\_INT\_ACK**. +- VGCS S-MSC = MSC-R** sends **PREPARE\_GROUP\_CALL\_ACK** to **MSC-A**. +- MSC-A** sends **SETUP (from MSC-A)** to **VGCS S-MSC = MSC-R**. +- VGCS S-MSC = MSC-R** sends **VGCS\_SETUP** to **BSS**. +- BSS** responds with **VGCS\_SETUP\_ACK**. +- VGCS S-MSC = MSC-R** sends **VGCS\_ASS\_REQ** to **VLR**. +- VLR** responds with **VGCS\_ASS\_RESULT**. +- VGCS S-MSC = MSC-R** sends **CONNECT (to MSC-A)** to **MSC-A**. +- VGCS S-MSC = MSC-R** sends **NOTIFY\_REQ (NCH)** and **NOTIFY\_REQ (FACCH)** to **MSs**. +- VGCS S-MSC = MSC-R** sends **SEND\_GROUP\_CALL\_END\_SIGNAL (IMSI, add Info)** to **MSC-A**. +- VGCS S-MSC = MSC-R** sends **UPLINK\_SEIZED\_CMD** to **VLR**. +- VLR** sends **UPLINK\_BUSY** to **BSS**. +- BSS** sends **CONNECT** to **MS'**. +- VGCS S-MSC = MSC-R** sends **CONNECT (from MSC-A)** to **MSC-A**. +- VGCS S-MSC = MSC-R** sends **PERIODIC NOTIF\_REQ (NCH)** to **MSs**. +- VGCS S-MSC = MSC-R** sends **ADD\_INFO** to **BSS**. +- BSS** sends **Periodic ADD\_INFO (SACCH)** to **MSs**. + +Sequence diagram showing network interactions between MS', MSs, BSS, V-MSC, VLR, VGCS S-MSC = MSC-R, GCR, and MSC-A. + +![Sequence diagram showing signalling information for establishing voice group calls. Lifelines: MS', MSs, BSS, V-MSC, VLR, VGCS S-MSC = MSC-R, GCR, MSC-A. The sequence starts with UPLINK_RELEASE from MS' to BSS, followed by UPLINK_RELEASE_IND from BSS to V-MSC. V-MSC sends PROCESS_GROUP_CALL_SIGNALLING (uplink rel ind) to MSC-A. MSC-A sends RELEASE (from MSC-A) to VGCS S-MSC = MSC-R. VGCS S-MSC = MSC-R sends CLR_CMD to V-MSC. V-MSC sends CHAN_RELEASE to MS'. MS' sends DISC to BSS. BSS sends CLR_COMP to V-MSC. MS' sends DISC to BSS again.](5e9af8986a5845504f251d3079da8078_img.jpg) + +``` + +sequenceDiagram + participant MS' + participant MSs + participant BSS + participant V-MSC + participant VLR + participant VGCS_S-MSC as VGCS S-MSC = MSC-R + participant GCR + participant MSC-A + + MS'->>BSS: UPLINK_RELEASE + BSS->>V-MSC: UPLINK_RELEASE_IND + V-MSC->>MSC-A: PROCESS_GROUP_CALL_SIGNALLING (uplink rel ind) + MSC-A->>VGCS_S-MSC: RELEASE (from MSC-A) + VGCS_S-MSC->>V-MSC: CLR_CMD + V-MSC->>MS': CHAN_RELEASE + MS'->>BSS: DISC + BSS->>V-MSC: CLR_COMP + MS'->>BSS: DISC + +``` + +Sequence diagram showing signalling information for establishing voice group calls. Lifelines: MS', MSs, BSS, V-MSC, VLR, VGCS S-MSC = MSC-R, GCR, MSC-A. The sequence starts with UPLINK\_RELEASE from MS' to BSS, followed by UPLINK\_RELEASE\_IND from BSS to V-MSC. V-MSC sends PROCESS\_GROUP\_CALL\_SIGNALLING (uplink rel ind) to MSC-A. MSC-A sends RELEASE (from MSC-A) to VGCS S-MSC = MSC-R. VGCS S-MSC = MSC-R sends CLR\_CMD to V-MSC. V-MSC sends CHAN\_RELEASE to MS'. MS' sends DISC to BSS. BSS sends CLR\_COMP to V-MSC. MS' sends DISC to BSS again. + +NOTE: MS' = calling service subscriber mobile station; + MSs = destination service subscriber mobile stations; + MSC-A = anchor MSC; + MSC-R = relay MSC; + V-MSC = visited MSC + +**Figure 3a: Signalling information required for establishing voice group calls by a service subscriber in a RANflex configuration** + +**SYS\_INFO (NCH allocated):** Message used to indicate if the NCH is allocated on the CCCH in the cell. + +**Initial RACH CHAN\_REQ:** Standard message. + +**IMM\_ASS:** Standard message sent on the AGCH. + +**SERV\_REQ (voice group call):** Modified form of the current call request message L3-MM CM SERVICE REQUEST sent on the allocated channel. Teleservice Voice group call is indicated. + +**UA (SERV\_REQ):** This message is used to acknowledge the layer 2 link and provide contention resolution of the service request. + +**COM\_L3\_INFO:** The MSC is provided with initial information about the voice group call. + +NOTE 10a: Messages flows for authentication and ciphering are not represented although performed as normal. + +**PROC\_ACC\_REQ:** The MAP\_PROCESS\_ACC\_REQ message is sent to the VLR to check the requested VGCS teleservice against the subscription data. + +**PROC\_ACC\_ACK:** The MAP\_PROCESS\_ACC\_ACK message acknowledges the requested service. + +**Authentication & Ciphering:** Authentication and Ciphering may be performed. Acknowledgement of the service request can also be performed by sending the CM SERVICE ACCEPT. + +**SETUP:** The MSC is provided with details about the voice group call. Optionally this message may contain a talker priority. + +NOTE 10b: Alternatively, an IMMEDIATE\_SETUP may have been sent as the initial message including all details of the voice group call. In this case no SETUP message must be sent. + +**SEND\_INFO\_OUT:** The requested group ID is transferred to the VLR in the MAP\_SEND\_INFO\_FOR\_OUTGOING\_CALL message. + +**COMPLETE\_CALL:** The VLR returns the MAP\_COMPLETE\_CALL message confirming the use of the requested group ID. The VLR also returns additional information about the calling service subscriber, if available. + +**SEND\_GROUP\_CALL\_INFO:** The MSC derives from the originating cell's LAC the address of the group call serving MSC and sends MAP\_SEND\_GROUP\_CALL\_INFO to it, to retrieve the MSC-A address. The message may also contain talker priority and additional info. + +**GCR\_INT:** The group call reference and MSC-A address are requested from the GCR through the GCR Interrogation message sent by the MSC. + +**GCR\_INT\_ACK:** The requested information (MSC-A address) is returned from the GCR in the GCR Interrogation Ack message. + +**SEND\_GROUP\_CALL\_INFO\_ACK:** The requested information is returned to the visited MSC. + +**ASSIGNMENT\_REQUEST:** Standard message. + +**CHAN\_MOD\_MODIFY:** Standard message to modify the channel mode in case of very early assignment. + +**CHAN\_MOD\_MODIFY\_ACK:** Standard message to acknowledge the modification of the channel mode. + +**ASSIGNMENT\_COMPLETE:** Standard message. + +NOTE 10c: Alternatively, early assignment or OACSU procedures might be applied with the corresponding assignment messages not presented in figure 3a. + +**SETUP to MSC-A:** Based on information received from the group call serving MSC the VMSC shall set-up a dedicated connection for the calling service subscriber to the anchor MSC. The VGCS prefix plus group call reference shall be sent as calling party number, and the address of the calling service subscriber's group call serving MSC shall be sent as generic number parameter, with the number qualifier indicator set to "additional calling party number". + +**PREPARE\_GROUP\_CALL:** The group call attributes (parts) are received from the anchor MSC. + +**GCR\_INT:** The group call attributes are requested from the GCR through the GCR Interrogation message sent by the MSC. + +**GCR\_INT\_ACK:** The requested information (cell list) is returned from the GCR in the GCR Interrogation Ack message. + +**ALLOCATE GROUP CALL NUMBER (not shown in figure 3a):** MSC-R requests the group call number from its associated VLR + +**ALLOCATE GROUP CALL NUMBER ACK (not shown in figure 3a):** The Group Call number is returned from the VLR. + +**PREPARE\_GROUP\_CALL\_ACK:** The Group Call number is sent to MSC-A. + +**SETUP from MSC-A:** The ISUP connection is set-up between MSC-A and MSC-R. + +**RELEASE GROUP CALL NUMBER (not shown in figure 3a):** The VLR is requested to release the Group Call number. + +**VGCS\_SETUP:** This message is sent from the MSC to all affected BSCs, [one dedicated message for each BSC,] including the group call reference with the eMLPP priority, and optionally the call priority. + +**VGCS\_SETUP\_ACK:** Acknowledgement message from the affected BSC in answer to the VGCS\_SETUP setup message. If the setup is not successful, a VGCS\_SETUP\_REFUSE message shall be sent instead. + +**VGCS\_ASSIGNMENT\_REQ:** This message is sent from the MSC to all affected BSCs, [one dedicated message for every requested channel in a cell,] including the group call reference, the channel type and possibly the call priority and details on the ciphering. + +NOTE 10d: As an operator option the voice group call channels, the links to them and optionally also the links to dispatchers can already be established and permanently reserved in order to speed up the call set-up for emergency voice group calls. + +**VGCS\_ASSIGNMENT RESULT:** Acknowledgement message from the affected BSC in answer to the assignment requests. If the assignment is not successful, a VGCS\_ASSIGNMENT\_FAILURE message shall be sent instead. + +**CONNECT to MSC-A:** Set-up of the ISUP connection from the anchor MSC is confirmed. + +**SEND\_GROUP CALL\_END\_SIGNAL (IMSI, additional info):** Indicates to the anchor MSC that conversation can start. In addition the IMSI of calling service subscriber who has established the voice group call and who is allowed to terminate the call is included. If the network supports the use of talker priorities, the message includes also the talker priority. Furthermore, the message provides additional information about the current talking service subscriber, if available. + +**NOTIF\_REQ (NCH):** Messages for notification which contain the group call reference, the priority of the call if eMLPP is applied, and possibly the channel description of the voice group call channel to which the mobile stations shall listen and the number of the group key used for ciphering. + +**NOTIF\_REQ (FACCH):** Message for notification sent on the FACCH to the mobile stations currently involved in other calls. The notification on the FACCH shall include the group call reference, and the priority level and may include also the channel description and the group ciphering key numbers. + +**UPLINK\_SEIZED\_CMD:** If the network supports the use of talker priorities, this message informs the BSS about the talker priority of the current talking service subscriber and about the status of the emergency mode. + +**UPLINK\_BUSY:** If the network supports the use of talker priorities, this connectionless RR message is sent on the downlink FACCH to inform all mobile stations about the talker priority of the current talking service subscriber and about the status of the emergency mode. The message is repeated on the FACCH every T1 seconds. + +**VGCS\_ADD\_INFO:** The MSC sends additional information about the current talking service subscriber to all BSCs. + +**ADD\_INFO:** The BSCs broadcast the additional information on the FACCH to all listeners. + +**Periodic ADD\_INFO (SACCH):** The message is repeated on the SACCH every T2 seconds. + +**Periodic NOTIF\_REQ (NCH):** The notifications are sent periodically so that mobile stations moving into the area can join the voice group call. + +**Periodic SACCH Info:** Periodic messages sent on the downlink of the SACCH informing mobile stations of: + +- information of changes of notifications; +- information used for cell re-selection. + +**CONNECT (from MSC-A):** Call set-up of the dedicated connection for the calling service subscriber is confirmed. + +**CONNECT:** Information to the mobile station of the calling service subscriber that the VGCS is established with the related group call reference as the connected number. If the SETUP message from the calling subscriber contained a talker priority, the MSC returns the talker priority used by the network. This will be lower than the requested talker priority, if the subscription check for the requested talker priority was unsuccessful. + +**UPLINK\_RELEASE:** When the calling service subscriber wants to become a listening service subscriber for the first time, a message indicating release of the uplink is required to be sent from the MS to the BSS in order to set the uplink free. + +NOTE 10e: For different cases of uplink release and the related message flows refer to Figure 6.b to 6.g. + +**UPLINK\_RELEASE\_INDICATION:** The BSS informs the MSC of the uplink release. + +**PROCESS\_GROUP CALL\_SIGNALLING (uplink release indication):** To indicate to the anchor MSC that the uplink is free. + +**CLEAR COMMAND:** The MSC requests the BSS to clear radio and terrestrial resources associated with originator dedicated link if not already done. + +**CHAN\_RELEASE:** The BSS sends a channel release message to the calling service subscriber's mobile station including the channel description of the voice group call channel to which the mobile station shall tune to. + +NOTE 10f: Alternatively, if no UPLINK\_RELEASE has been sent to the network by the mobile station, the network may transfer the mobile station to the voice group call channel by the channel mode modify procedure or by an assignment procedure or by a handover procedure. + +**DISC:** Two layer 2 disconnect messages shall be sent by the mobile station to the network. + +**RELEASE from MSC-A:** The dedicated connection for the calling service subscriber is released. + +![Sequence diagram showing signalling information required for establishing voice group calls. Lifelines: fixed DP, mobile or V-MSC, GMSC, MSs, BSSs, MSC-A, VLR, GCR, MSC-R, BSSs. The diagram shows the flow of messages like SETUP, VGCS_SETUP, VGCS_ASS_REQ, CONNECT, and UPLINK_REL_CMD between these entities. A callout box indicates that a mobile service subscriber can seize the uplink.](d3ca266c298aeb34b019960c6c36f187_img.jpg) + +The sequence diagram illustrates the signalling process for establishing a voice group call. The lifelines are: fixed DP, mobile or V-MSC, GMSC, MSs, BSSs, MSC-A, VLR, GCR, MSC-R, and BSSs. The process begins with a SETUP message from the fixed DP to the mobile or V-MSC. The mobile or V-MSC then sends a SETUP (IAM) message to the MSC-A. A dashed line indicates a SETUP message from the mobile dispatcher in the anchor MSC area to the MSC-A. The MSC-A sends a SEND\_INFO\_OUT message to the VLR, which responds with COMPLETE\_CALL. The MSC-A then sends a GCR\_INT message to the GCR, which responds with GCR\_INT\_ACK. The MSC-A sends a VGCS\_SETUP message to the BSSs, which respond with VGCS\_SETUP\_ACK. The MSC-A then sends a PREP\_RE\_GROUP\_CALL message to the MSC-R, which responds with PREP\_RE\_GROUP\_CALL\_ACK. The MSC-A sends a VGCS\_SETUP message to the BSSs, which respond with VGCS\_SETUP\_ACK. The MSC-A then sends a VGCS\_ASS\_REQ message to the BSSs, which respond with VGCS\_ASS\_REQ. The MSC-A sends a CONNECT (from MSC-R) message to the BSSs, which respond with VGCS\_ASS\_RESUL. The MSC-A then sends a SEND\_GROUP\_CALL\_END\_SIGNAL message to the BSSs. The MSC-A sends a FOR RD\_GROUP\_CALL\_SIGNALLING (uplink\_rel\_indication) message to the BSSs. The MSC-A sends a UPLINK\_REL\_CMD message to the BSSs, which respond with UPLINK\_REL\_CMD. The mobile service subscriber can seize the uplink. The MSs send a NOTIFY\_REQ (NCH) message to the BSSs, which respond with NOTIFY\_REQ (FCH). The MSs send a CONNECT message to the BSSs, which respond with Periodic NOTIFY\_REQ (NCH). The MSs send a Periodic SACCH info message to the BSSs. + +Sequence diagram showing signalling information required for establishing voice group calls. Lifelines: fixed DP, mobile or V-MSC, GMSC, MSs, BSSs, MSC-A, VLR, GCR, MSC-R, BSSs. The diagram shows the flow of messages like SETUP, VGCS\_SETUP, VGCS\_ASS\_REQ, CONNECT, and UPLINK\_REL\_CMD between these entities. A callout box indicates that a mobile service subscriber can seize the uplink. + +NOTE: DP = dispatcher; + MSs = destination subscriber mobile stations; + MSC-A = anchor MSC; + MSC-R = relay MSC; + V-MSC = visited MSC; + GMSC = Gateway MSC + +**Figure 3b: Signalling information required for establishing voice group calls by a mobile dispatcher or fixed line dispatcher** + +**SETUP:** Mobile dispatcher or fixed line dispatcher sets up a VGCS call. The visited MSC or the Gateway MSC receives the SETUP message with details about the voice group call including the Group Call Reference within the MSISDN dialled by the originating dispatcher. + +**SETUP (IAM):** The visited MSC or the Gateway MSC sends an IAM message to the anchor MSC of the group call based on the called party MSISDN number. + +**SETUP (Mobile dispatcher in anchor MSC area):** If the originating mobile dispatcher is located in the anchor MSC area, the SETUP message with details about the voice group call including the Group Call Reference within the + +MSISDN dialled by the originating dispatcher is received directly by the anchor MSC (further messages regarding the standard SETUP procedure are not drawn in the Fig.) + +**SEND\_INFO\_OUT:** The requested group ID is transferred to the VLR in the internal MAP\_SEND\_INFO\_FOR\_OUTGOING\_CALL message. + +**COMPLETE\_CALL:** The VLR returns the MAP\_COMPLETE\_CALL message confirming the use of the requested group ID. + +**GCR\_INT:** The group call attributes are requested from the GCR through the GCR Interrogation message sent by the MSC. + +**GCR\_INT\_ACK:** The requested information is returned from the GCR in the GCR Interrogation Ack message. + +**VGCS\_SETUP:** Anchor MSC sends to BSS's a VGCS SETUP message across VGCS call controlling SCCP connection to initiate a VGCS call set-up procedures. + +**VGCS\_SETUP\_ACK:** After receiving the VGCS\_SETUP message, BSS will allocate resources to the call and returns VGCS\_SETUP\_ACK message to the MSC. This connection is established for the lifetime of the VGCS call. + +**VGCS\_ASSIGNMENT\_REQ:** This message is sent from the MSC to all affected BSCs, [ including the group call reference, the channel type and possibly the call priority and details on the ciphering. + +**PREPARE\_GROUP\_CALL:** The group call attributes are sent to every relay MSC and a Group Call number for call set-up to is requested. + +**PREPARE\_GROUP\_CALL\_ACK:** The Group Call number for call set-up is returned to the anchor MSC. + +**SETUP to MSC-R:** The ISUP connection is set-up to the relay MSC. + +**VGCS\_SETUP:** Relay MSC sends to BSS's a VGCS SETUP message to initiate a VGCS call set-up procedures. + +**VGCS\_SETUP\_ACK:** After receiving the VGCS\_SETUP message, BSS will allocate resources to the call and returns VGCS\_SETUP\_ACK message to the MSC. This connection is established for the lifetime of the VGCS call. + +**VGCS\_ASSIGNMENT\_REQ:** This message is sent from the relay MSC to all affected BSCs, [ including the group call reference, the channel type and possibly the call priority and details on the ciphering. + +**CONNECT from MSC-R:** Set-up of the ISUP connection to the relay MSC is confirmed. + +**VGCS\_ASSIGNMENT\_RESULT:** Acknowledgement message from the affected BSC in answer to the assignment requests. If the assignment is not successful, a VGCS\_ASSIGNMENT\_FAILURE message shall be sent instead. + +**SEND\_GROUP\_CALL\_END\_SIGNAL:** Indicates to the anchor MSC that at least one voice group call channel has been established in the relay MSC area. + +**Txx:** Timer implemented in the anchor MSC which is started with receipt of the SETUP message from the dispatcher. If the timer expires before the conditions for establishment have been met, as per subclause 11.3.1.1.2, then the call shall be released. + +**FORWARD\_GROUP\_CALL\_SIGNALLING (uplink release indication):** The anchor MSC indicates to all relay MSCs that the uplink is free. On receipt of the uplink free indication the relay MSC shall send an UPLINK RELEASE message to every BSS of the group call area to indicate that the uplink free. + +**UPLINK\_REL\_CMD and UPLINK\_FREE:** After having received the VGCS\_SETUP\_ACK, the MSC sends to BSCs the UPLINK RELEASE CMD in order to indicate that the call has been initiated by a dispatcher. As a consequence, UPLINK\_FREE is sent on the common channel(s). Then a service subscriber can request the uplink by using Uplink Request procedure. + +**NOTIF\_REQ (NCH):** Messages for notification which contain the group call reference, the priority of the call if eMLPP is applied, and possibly the channel description of the voice group call channel to which the mobile stations shall listen and the number of the group key used for ciphering. + +**NOTIF\_REQ (FACCH):** Message for notification sent on the FACCH to the mobile stations currently involved in other calls. The notification on the FACCH shall include the group call reference; and the priority level and may also include the channel description and the group ciphering key numbers. + +**CONNECT:** Information to the originating that the VGCS is established with the related group call reference as the connected number. + +**Periodic NOTIF\_REQ (NCH):** The notifications are sent periodically so that mobile stations moving into the area can join the voice group call. + +**Periodic SACCH Info:** Periodic messages sent on SACCH. This message may include: + +- information of changes of notifications; +- information used for cell re-selection. + +![Sequence diagram illustrating the signalling information required for establishing voice group calls in a RANflex configuration with group call redundancy. The diagram shows interactions between a V-MSC, two Redundancy Pools (Pool 1 and Pool 2), and four Group Call References (GCR 1, 2, 3, 4).](1d27fed9c01eb99f6535283f35fe3bbf_img.jpg) + +``` + +sequenceDiagram + participant V-MSC + subgraph Redundancy Pool 1 + MSC-R-1[MSC-R 1] + MSC-R-2[MSC-R 2] + end + subgraph Redundancy Pool 2 + MSC-A-1[MSC-A 1] + MSC-A-2[MSC-A 2] + end + GCR-1[GCR 1] + GCR-2[GCR 2] + GCR-3[GCR 3] + GCR-4[GCR 4] + + Note right of MSC-R-1: Start 3 + Note right of MSC-R-2: Start 3 + Note right of GCR-3: Stop 3 + Note right of GCR-2: Stop 3 + + V-MSC->>MSC-R-1: 1. SEND_GROUP_CALL_INFO + MSC-R-1->>GCR-1: 2. GCR_INT + GCR-1->>MSC-R-2: 3a. SYNC_GCR + MSC-R-2->>GCR-2: 3b. GCR_INT_ACK + MSC-R-1->>V-MSC: 4. SEND_GROUP_CALL_INFO_ACK + Note right of MSC-R-1: Start 3 + Note right of MSC-R-2: Start 3 + MSC-R-2->>GCR-2: 5. SYNC_GCR_ACK + Note right of GCR-2: Start 3 + MSC-R-2->>MSC-A-1: 6. SETUP (to MSC-A Pool) + MSC-A-1->>GCR-3: 7. GCR_INT + GCR-3->>MSC-A-2: 8a. SYNC_GCR + MSC-A-2->>GCR-3: 8b. GCR_INT_ACK + Note right of GCR-3: Stop 3 + MSC-A-1->>GCR-3: 9. SYNC_GCR_ACK + Note right of GCR-3: Stop 3 + MSC-A-1->>MSC-R-2: 10. PREP_RE_GROUP_CALL + MSC-R-2->>GCR-2: 11. GCR_INT + GCR-2->>MSC-R-1: 12a. SYNC_GCR + MSC-R-1->>GCR-2: 12b. GCR_INT_ACK + Note right of GCR-2: Stop 3 + MSC-R-1->>GCR-2: 13. SYNC_GCR_ACK + Note right of GCR-2: Stop 3 + MSC-R-2->>MSC-A-1: 14. PREP_RE_GROUP_CALL_ACK + MSC-A-1->>MSC-R-2: 15. SETUP (from MSC-A 1) + MSC-R-2->>MSC-A-1: 16a. CONNECT (to MSC-A 1) + MSC-R-2->>MSC-A-1: 16b. SEND_GROUP_CALL_END_SIGNAL + MSC-A-1->>V-MSC: 17a. CONNECT (from MSC-A 1) + MSC-A-1->>MSC-R-2: 17b. FOR_RD_GROUP_CALL_SIGNALLING + +``` + +Sequence diagram illustrating the signalling information required for establishing voice group calls in a RANflex configuration with group call redundancy. The diagram shows interactions between a V-MSC, two Redundancy Pools (Pool 1 and Pool 2), and four Group Call References (GCR 1, 2, 3, 4). + +**Figure 3c: Signalling information required for establishing voice group calls by a service subscriber in a RANflex configuration with group call redundancy** + +###### **See also figure 3a** + +**1. SEND\_GROUP\_CALL\_INFO:** The V-MSC derives from the originating cell's LAC the address of the group call serving MSC redundancy pool and sends MAP\_SEND\_GROUP\_CALL\_INFO to it, to retrieve the group call anchor MSC redundancy pool address. Network routing shall be configured so that the message is routed to one of the available MSCs within the redundancy pool. In this example MSC-R1 is selected. The message includes initial talker information. + +**2. GCR\_INT:** MSC-R 1 requests from its associated GCR the group call reference and group call anchor MSC redundancy pool address. The message may contain initial talker information. + +**3a. SYNC\_GCR:** Initial Talker Information is propagated to all GCRs associated to MSCs within the redundancy pool. + +**3b. GCR\_INT\_ACK:** The requested information is returned from the GCR in the GCR Interrogation Ack message. To avoid glare cases GCR 1 may need to wait for message 5 before sending message 3b. + +**4. SEND\_GROUP\_CALL\_INFO\_ACK:** The requested information is returned to the visited MSC. + +**5. SYNC\_GCR\_ACK:** Successful GCR synchronization is acknowledged. + +**6. SETUP to MSC-A:** Based on information received from the group call serving MSC the VMSC shall set-up a dedicated connection for the calling service subscriber to the group call anchor MSC redundancy pool. Network routing shall be configured so that the message is routed to one of the available MSCs within the redundancy pool. In this example MSC-A1 is selected. The VGCS prefix plus group call reference shall be sent as calling party number. The address of the calling service subscriber's group call serving MSC pool shall be sent as generic number parameter, with the number qualifier indicator set to "additional calling party number"; this shall be the same address as used to route message 1. + +**7. GCR\_INT:** MSC-A 1 requests from its associated GCR the group call attributes and marks the group call "on-going". + +**8a. SYNC\_GCR:** The "on-going" indication is propagated to all GCRs associated to MSCs within the redundancy pool. + +**8b. GCR\_INT\_ACK:** The requested information is returned from the GCR in the GCR Interrogation Ack message. To avoid glare cases GCR 3 may need to wait for message 9 before sending message 8b. + +**9. SYNC\_GCR\_ACK:** Successful GCR synchronization is acknowledged. + +**10. PREPARE\_GROUP\_CALL:** MSC-A 1 sends PREPARE\_GROUP\_CALL to the group call relay MSC redundancy pool. Network routing shall be configured so that the message is routed to one of the available MSCs within the redundancy pool. In this example MSC-R2 is selected. + +**11. GCR\_INT:** MSC-R 2 interrogates its associated GCR to retrieve the group call attributes and initial talker information and to mark the group call "on-going" and to delete the initial talker information. + +**12a. SYNC\_GCR:** The "on-going" indication is propagated to all GCRs associated to MSCs within the redundancy pool. + +**12b. GCR\_INT\_ACK:** The requested information is returned from the GCR in the GCR Interrogation Ack message. + +**13. SYNC\_GCR\_ACK:** Successful GCR synchronization is acknowledged. + +**ALLOCATE GROUP CALL NUMBER (not shown in figure 8a):** MSC-R2 requests the Group Call number from its associated VLR + +**ALLOCATE GROUP CALL NUMBER ACK (not shown in figure 8a):** The Group Call number is returned from the VLR. + +**14. PREPARE\_GROUP\_CALL\_ACK:** The Group Call number is sent to MSC-A1. + +**15. SETUP from MSC-A1:** The ISUP connection is set-up between MSC-A1 and MSC-R2 using the Group Call number received in step 14. + +**RELEASE GROUP CALL NUMBER (not shown in figure 8a):** The VLR is requested to release the Group Call number. + +**16a. CONNECT to MSC-A:** Set-up of the ISUP connection from the anchor MSC is confirmed. + +**16b. SEND\_GROUP CALL\_END\_SIGNAL (IMSI, additional info):** Indicates to the anchor MSC that conversation can start. In addition the IMSI of calling service subscriber who has established the voice group call and who is allowed to terminate the call is included. If the network supports the use of talker priorities, the message includes also the talker priority. Furthermore, the message provides additional information about the current talking service subscriber, if available. After sending message 16b MSC-R2 deletes initial talker information (if any) as it may be invalid due to a lost race condition. Valid initial talker information (if any) may be received with message 17b. + +**17a. CONNECT (from MSC-A):** Call set-up of the dedicated connection for the calling service subscriber is confirmed. + +**17b. FORWARD\_GROUP\_CALL\_SIGNALLING:** Initial Talker Information is propagated from MSC-A to MSC-R. + +![Sequence diagram showing signalling information for voice group call uplink access between MS, BSS, MSC-A, and MSC-R.](07b17a620c75522d53916a11e12d1bff_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC-A + participant MSC-R + + BSS-->>MS: UPLINK_FREE + MS->>BSS: UPLINK_ACCESS + BSS->>MSC-A: UPLINK_REQUEST + BSS-->>MS: VGCS_UPLINK_GRANT + BSS-->>MS: UPLINK_BUSY + MS->>BSS: SABM(L3msg) + BSS-->>MS: UA (L3msg) + MSC-A-->>BSS: UPLINK_REQ_ACK + BSS->>MSC-R: FORW._GROUP CALL_SIGN. +(uplink seized command) + BSS->>MSC-A: UPLINK_REQ_CONF (L3msg) + Note over MSC-A: Retrieve additional info +from the VLR (NOTE12a) + MSC-A-->>BSS: VGCS_ADD_INFO + BSS->>MSC-R: FORW._GROUP CALL_SIGN. +(add_info) + BSS->>MS: Conversation proceeds + MS->>BSS: UPLINK_RELEASE (NOTE 12b) + BSS->>MSC-A: UPLINK_RELEASE_I + MSC-A->>MSC-R: FORW._GROUP CALL_SIGN. +(uplink release indication) + BSS-->>MS: UPLINK_FREE + +``` + +The sequence diagram illustrates the signaling flow for voice group call uplink access between four entities: MS (Mobile Station), BSS (Base Station System), MSC-A (Anchor MSC), and MSC-R (Relay MSC). The flow starts with BSS sending UPLINK\_FREE to MS. MS responds with UPLINK\_ACCESS. BSS then sends UPLINK\_REQUEST to MSC-A. BSS sends VGCS\_UPLINK\_GRANT and UPLINK\_BUSY to MS. MS sends SABM(L3msg) to BSS, which responds with UA (L3msg). MSC-A sends UPLINK\_REQ\_ACK to BSS. BSS sends FORW.\_GROUP CALL\_SIGN. (uplink seized command) to MSC-R. BSS sends UPLINK\_REQ\_CONF (L3msg) to MSC-A. MSC-A retrieves additional info from the VLR (NOTE12a) and sends VGCS\_ADD\_INFO to BSS. BSS sends FORW.\_GROUP CALL\_SIGN. (add\_info) to MSC-R. Conversation proceeds between MS and BSS. Later, MS sends UPLINK\_RELEASE (NOTE 12b) to BSS, which sends UPLINK\_RELEASE\_I to MSC-A. MSC-A sends FORW.\_GROUP CALL\_SIGN. (uplink release indication) to MSC-R. Finally, BSS sends UPLINK\_FREE to MS. + +Sequence diagram showing signalling information for voice group call uplink access between MS, BSS, MSC-A, and MSC-R. + +**Figure 4: Signalling information required for the voice group call uplink access in the anchor MSC without talker priority (normal case, without contention resolution)** + +**UPLINK\_FREE:** This connectionless RR message is repeatedly sent by the BSS on the main signalling link (FACCH) to inform all mobile stations of the voice group call members that the uplink is free. + +**UPLINK\_ACCESS:** This is sent on the uplink of the voice group call channel using random access procedures. The UPLINK\_ACCESS message is similar to a channel request but sent on the group call channel uplink. The establishment cause for subsequent talker uplink request as defined in 3GPP TS 44.018 shall be used for this purpose. The mobile station may send repeated UPLINK\_ACCESS messages (see 3GPP TS 44.018). + +**UPLINK\_REQUEST:** The request for the uplink is indicated to the MSC. Only one request per BSC shall be forwarded. + +**VGCS\_UPLINK\_GRANT:** The reply to the uplink request sent on the voice group channel downlink containing information for synchronisation of the mobile station to the network and uplink access contention resolution. The VGCS\_UPLINK\_GRANT message shall therefore include a request reference (reflecting the UPLINK\_ACCESS) and the physical information required for transmission on the voice group call channel uplink. On receipt of a VGCS\_UPLINK\_GRANT, the related mobile station can start to send speech directly. + +NOTE 11: UPLINK\_FREE messages are stopped immediately. + +**UPLINK\_BUSY:** This connectionless RR message is sent on the downlink FACCH to inform all mobile stations that the uplink is now busy. + +NOTE 12: The order of UPLINK\_BUSY and SABM message is independent. + +**SABM(L3msg):** The layer 2 link is set up and layer 3 information on classmark and mobile station identity included. + +**UA(L3msg):** The layer 2 link is acknowledged and the layer 3 information reflected for contention resolution. + +**UPLINK\_REQUEST\_ACKNOWLEDGE:** The anchor MSC acknowledges the uplink to one BSC. If uplink requests have been made by more than one BSC or MSC-R, all remaining uplink requests shall be rejected by an UPLINK\_REJECT\_CMD which is not presented in figure 4. On reception of an UPLINK\_REJECT\_CMD the BSS shall send an UPLINK\_REL to the related mobile station, followed by an UPLINK\_BUSY to indicate to the mobile stations that the uplink is in use. The MSC shall send to other BSCs which did not send an uplink request an UPLINK\_SEIZED\_CMD message which is not presented in figure 4. On reception of an UPLINK\_SEIZED\_CMD the BSS shall send an UPLINK\_BUSY to indicate to the mobile stations that the uplink is in use. + +**FORWARD\_GROUP\_CALL\_SIGNALLING (uplink seized command):** This message is sent to all relay MSCs, to inform all mobile stations roaming in parts of the group call area which are controlled by relay MSCs, that the uplink is now busy. + +**UPLINK\_REQUEST\_CONFIRM:** The BSS confirms the uplink use to the MSC together with the mobile station identity. + +NOTE 12a: In a RANflex configuration (with or without group call redundancy) the uplink requesting subscriber's VMSC may be different from his current location area's group call serving MSC. In this case the retrieval of info from the (distant) VLR is done by means of the MAP service SEND\_GROUP\_CALL\_INFO. + +**VGCS\_ADD\_INFO:** The MSC sends additional information about the new talking service subscriber to all BSCs. The BSCs broadcast ADD\_INFO messages containing the additional information to all listeners (not shown in figure 4). + +**FORWARD\_GROUP\_CALL\_SIGNALLING (additional info):** This message is sent to all relay MSCs to provide information about the new talking service subscriber. + +**Conversation proceeds:** Once the mobile station has control of the uplink, it shall be able to communicate directly. The two-way nature of the conference bridge will ensure that they are already connected to all appropriate downlink channels. + +**UPLINK\_RELEASE:** When the service subscriber who has access to the uplink wants to release the channel, then a message indicating release of the uplink is required to be sent from the MS to the BSS on the FACCH. + +NOTE 12b: For different cases of uplink release and the related message flows refer to Figure 6.b to 6.g. + +**UPLINK\_RELEASE\_INDICATION:** The BSS informs the MSC on the uplink release. + +**FORWARD\_GROUP CALL\_SIGNALLING (uplink release indication):** The anchor MSC indicates to all relay MSCs that the uplink is free. On receipt of the uplink free indication the relay MSC shall send an UPLINK RELEASE message to every BSS of the group call area to indicate that the uplink free. + +![Sequence diagram showing signaling between MS, BSS, MSC-A, and MSC-R for FORWARD_GROUP CALL_SIGNALLING (uplink release indication).](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC-A + participant MSC-R + + Note left of MS: UPLINK_FREE + MS->>BSS: UPLINK_ACCESS (privileged subscriber request) + BSS->>MSC-A: UPLINK_REQUEST (L3msg, privileged subscriber) (NOTE 16) + Note right of MSC-A: MSC-A checks subscription for group ID and talker priority and retrieves additional info from VLR (NOTE 16a) + MSC-A->>MSC-R: FORW_GROUP CALL_SIGN. (uplink seized command, privileged subscriber, add info) + MSC-A->>BSS: UPLINK_REQ_ACK (privileged subscriber) + BSS->>MSC-A: VGCS_ADD_INFO + Note right of BSS: Conversation proceeds with talker priority "privileged subscriber" + BSS->>MSC-A: ASS_REQ + Note right of MSC-A: Dedicated channel Assignment + MSC-A->>BSS: ASS_COMP + BSS->>MS: ASSIGNMENT_CMD + MS->>BSS: ASSIGNMENT_COMP + Note left of MS: UPLINK_RELEASE (NOTE 18) (privileged subscriber) + BSS->>MSC-A: UPLINK_RELEASE_I (privileged subscriber) + Note right of MSC-A: FORW_GROUP CALL_SIGN. (uplink release indication) + MSC-A->>MSC-R: FORW_GROUP CALL_SIGN. (uplink release indication) + MS->>BSS: UPLINK_FREE + +``` + +The sequence diagram illustrates the signaling process for **FORWARD\_GROUP CALL\_SIGNALLING (uplink release indication)** between four entities: **MS**, **BSS**, **MSC-A**, and **MSC-R**. + +- The **MS** sends a **UPLINK\_FREE** message to the **BSS**. +- The **MS** sends a **UPLINK\_ACCESS (privileged subscriber request)** message to the **BSS**. +- The **BSS** sends a **UPLINK\_REQUEST (L3msg, privileged subscriber) (NOTE 16)** message to the **MSC-A**. +- The **MSC-A** checks subscription for group ID and talker priority and retrieves additional info from VLR (NOTE 16a). +- The **MSC-A** sends a **FORW\_GROUP CALL\_SIGN. (uplink seized command, privileged subscriber, add info)** message to the **MSC-R**. +- The **MSC-A** sends a **UPLINK\_REQ\_ACK (privileged subscriber)** message to the **BSS**. +- The **BSS** sends a **VGCS\_ADD\_INFO** message to the **MSC-A**. +- A note indicates: **Conversation proceeds with talker priority "privileged subscriber"**. +- The **BSS** sends an **ASS\_REQ** message to the **MSC-A**. +- The **MSC-A** performs a **Dedicated channel Assignment**. +- The **MSC-A** sends an **ASS\_COMP** message to the **BSS**. +- The **BSS** sends an **ASSIGNMENT\_CMD** message to the **MS**. +- The **MS** sends an **ASSIGNMENT\_COMP** message to the **BSS**. +- The **MS** sends a **UPLINK\_RELEASE (NOTE 18) (privileged subscriber)** message to the **BSS**. +- The **BSS** sends a **UPLINK\_RELEASE\_I (privileged subscriber)** message to the **MSC-A**. +- The **MSC-A** performs a **FORW\_GROUP CALL\_SIGN. (uplink release indication)**. +- The **MSC-A** sends a **FORW\_GROUP CALL\_SIGN. (uplink release indication)** message to the **MSC-R**. +- The **MS** sends a **UPLINK\_FREE** message to the **BSS**. + +Sequence diagram showing signaling between MS, BSS, MSC-A, and MSC-R for FORWARD\_GROUP CALL\_SIGNALLING (uplink release indication). + +NOTE: The figure describes the handling, if MSC decides to have a subsequent talker on a dedicated channel. + +###### **Figure 4a: Signalling information required for the voice group call uplink access in the anchor MSC with talker priority "privileged subscriber" (normal case, without contention resolution, subsequent talker on dedicated channel)** + +**UPLINK\_FREE:** This connectionless RR message is repeatedly sent by the BSS on the main signalling link (FACCH) to inform all mobile stations of the voice group call members that the uplink is free. + +**UPLINK\_ACCESS:** This is sent on the uplink of the voice group call channel using random access procedures. The UPLINK\_ACCESS message is similar to a channel request but sent on the group call channel uplink. The establishment cause for a privileged subscriber request as defined in 3GPP TS 44.018 shall be used for this purpose. The mobile station may send repeated UPLINK\_ACCESS messages (see 3GPP TS 44.018). + +**VGCS\_UPLINK\_GRANT:** The reply to the uplink request sent on the voice group channel downlink containing information for synchronisation of the mobile station to the network and uplink access contention resolution. The VGCS\_UPLINK\_GRANT message shall therefore include a request reference (reflecting the UPLINK\_ACCESS) and the physical information required for transmission on the voice group call channel uplink. On receipt of a VGCS\_UPLINK\_GRANT, the related mobile station can start to send speech directly. + +NOTE 13: UPLINK\_FREE messages are stopped immediately. + +**UPLINK\_BUSY:** This connectionless RR message is sent on the downlink FACCH to inform all mobile stations that the uplink is now busy. If the network supports talker priorities, then the UPLINK\_BUSY indicates the talker priority of the current talking service subscriber to all listening service subscribers and additionally, if the emergency mode is set in the network, the emergency mode indication. The message is repeated on the FACCH every T1 seconds. + +NOTE 14: The order of UPLINK\_BUSY and SABM message is independent. + +**SABM(L3msg):** The layer 2 link is set up and layer 3 information on classmark and mobile station identity included. + +**UA(L3msg):** The layer 2 link is acknowledged and the layer 3 information reflected for contention resolution. + +NOTE 15: Dedicated signalling connection on the main DCCH needs to be established. + +**UPLINK\_REQUEST:** The request for the uplink containing the MS identity and the talker priority is indicated to the MSC. Only one request per BSS shall be forwarded. + +NOTE 16: As the BSS supports the use of talker priorities and receives from the MS a talker priority different from "normal subscriber", the BSS delays the sending of the UPLINK\_REQUEST message to the MSC, until SABM(L3msg) with the MS identity is received from the MS. Then the BSS includes the layer 3 message, the talker priority, and the cell identity of the cell where the UPLINK\_ACCESS message was received in the UPLINK\_REQUEST message. In this case the UPLINK\_REQUEST\_CONFIRM message may be omitted by the BSS. + +NOTE 16a: In a RANflex configuration (with or without group call redundancy) the uplink requesting subscriber's VMSC may be different from his current location area's group call serving MSC. In this case the retrieval of info from the (distant) VLR is done by means of the MAP service SEND\_GROUP\_CALL\_INFO. + +**UPLINK\_REQUEST\_ACKNOWLEDGE:** The anchor MSC acknowledges the uplink to one BSC. If uplink requests have been made by more than one BSC or MSC-R, all remaining uplink requests shall be rejected by an UPLINK\_REJECT\_CMD which is not presented in figure 4a. On reception of an UPLINK\_REJECT\_CMD the BSS shall send an UPLINK\_REL to the related mobile station, followed by an UPLINK\_BUSY to indicate to the mobile stations that the uplink is in use. The MSC shall send to other BSCs which did not send an uplink request an UPLINK\_SEIZED\_CMD message which is not presented in figure 4a. On reception of an UPLINK\_SEIZED\_CMD the BSS shall send an UPLINK\_BUSY to indicate to the mobile stations that the uplink is in use. + +The anchor MSC may also include additional information about the new talking service subscriber in the UPLINK\_REQUEST\_ACKNOWLEDGE, UPLINK\_REJECT\_CMD and UPLINK\_SEIZED\_CMD messages, if the information is available when sending these messages. The BSS may include the additional information in the UPLINK\_BUSY messages, if the information is available when sending these messages and there is sufficient space available in the messages. + +**FORWARD\_GROUP CALL\_SIGNALLING (uplink seized command, privileged subscriber, additional info):** This message is sent to all relay MSCs, to inform all mobile stations roaming in parts of the group call area which are + +controlled by relay MSCs that the uplink is now busy for a talker with talker priority "privileged subscriber". Furthermore, the message provides additional information about the new talking service subscriber, if available. + +**UPLINK\_REQUEST\_CONFIRM:** The BSS confirms the uplink use to the MSC together with the mobile station identity. + +**ASS\_REQ:** This message contains details of the resource(s) required for the dedicated connection. + +**ASSIGNMENT\_CMD:** This message contains details of the resource(s) required and triggers the assignment procedure of the dedicated channel at the MS. + +**ASSIGNMENT\_COMP:** Standard message. + +**ASS\_COMP:** Standard message. + +**VGCS\_ADD\_INFO:** The MSC sends additional information about the new talking service subscriber to all BSCs, unless the information was already included in the UPLINK\_REQUEST\_ACKNOWLEDGE, UPLINK\_REJECT\_CMD and UPLINK\_SEIZED\_CMD messages. The BSCs broadcast ADD\_INFO messages containing the additional information to all listeners (not shown in figure 4a) , unless the information was already included in the UPLINK\_BUSY messages. + +**Conversation proceeds:** Once the mobile station has control of the uplink, it shall be able to communicate directly. The two-way nature of the conference bridge will ensure that they are already connected to all appropriate downlink channels. + +**UPLINK\_RELEASE:** When the service subscriber who has access to the uplink wants to release the channel, then a message indicating release of the uplink is required to be sent from the MS to the BSS on the FACCH. + +NOTE 17: For different cases of uplink release and the related message flows refer to Figure 6b to 6g. + +**UPLINK\_RELEASE\_INDICATION:** The BSS informs the MSC of the uplink release. + +**FORWARD\_GROUP\_CALL\_SIGNALLING (uplink release indication):** The anchor MSC indicates to all relay MSCs that the uplink is free. On receipt of the uplink free indication the relay MSC shall send an UPLINK RELEASE message to every BSS of the group call area to indicate that the uplink free. + + + +![](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +Sequence diagram illustrating the interaction between MS, BSS, MSC-A, and MSC-R. + +**Participants:** MS, BSS, MSC-A, MSC-R + +**Sequence of Messages:** + +- Conversation proceeds with talker priority "normal subscriber" (MS to MSC-A) +- UPLINK\_ACCESS (emergency subscriber request) (MS to BSS) +- VGCS\_UPLINK\_GRANT (BSS to MS) +- UPLINK\_BUSY (emergency subscriber) (MS to BSS) +- SABM(L3msg) (MS to BSS) +- UA (L3msg) (BSS to MS) +- UPLINK\_REQUEST (L3msg, emergency subscriber) (NOTE 20) (BSS to MSC-A) +- UPLINK\_REQ\_ACK (emergency subscriber, emergency mode indication) (MSC-A to BSS) +- UPLINK\_BUSY (emergency subscriber, emergency mode indication) (MS to BSS) +- FORW\_GROUP CALL\_SIGN. (uplink seized command, emergency subscriber, add info) (MSC-A to MSC-R) +- Distribution of the additional info to the listeners and to the previous talker (MSC-A to BSS) +- VGCS\_ADD\_INFO (BSS to MSC-A) +- VGCS\_ADD\_INFO (MSC-A to BSS) +- Conversation proceeds with talker priority "emergency subscriber" (MS to MSC-A) +- ASS\_REQ (BSS to MSC-A) +- ASSIGNMENT\_CMD (MSC-A to BSS) +- ASSIGNMENT\_COMP (BSS to MSC-A) +- ASS\_COMP (MSC-A to BSS) +- CHAN\_RELEASE (emergency subscriber, emergency mode Indication, add info) (BSS to MSC-A) +- CLR\_CMD (MSC-A to BSS) +- CLR\_COMP (BSS to MSC-A) +- DISC (MSC-A to BSS) +- SCCP\_RLSD (BSS to MSC-A) + +![Diagram showing signaling information flow between an anchor MSC and a BSC. The anchor MSC is represented by a rectangle on the left. To its right is a BSC, also represented by a rectangle. Between them are two horizontal dashed arrows labeled 'SCCP_RLC', one pointing left and one pointing right. To the far right is another rectangle representing a mobile station.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +Diagram showing signaling information flow between an anchor MSC and a BSC. The anchor MSC is represented by a rectangle on the left. To its right is a BSC, also represented by a rectangle. Between them are two horizontal dashed arrows labeled 'SCCP\_RLC', one pointing left and one pointing right. To the far right is another rectangle representing a mobile station. + +NOTE: The figure describes the handling, if the MSC decides to have a subsequent talker on a dedicated channel. + +**Figure 4b: Signalling information required for the voice group call uplink access in the anchor MSC with talker priority "emergency subscriber" and pre-emption of the current talker (normal case, subsequent talker on dedicated channel, without contention resolution)** + +**UPLINK\_ACCESS:** This is sent on the uplink of the voice group call channel using random access procedures. The UPLINK\_ACCESS message is similar to a channel request but sent on the group call channel uplink. The establishment cause for an emergency subscriber request as defined in 3GPP TS 44.018 shall be used for this purpose. The mobile station may send repeated UPLINK\_ACCESS messages (see 3GPP TS 44.018). + +**VGCS\_UPLINK\_GRANT:** The reply to the uplink request sent on the voice group channel downlink containing information for synchronisation of the mobile station to the network and uplink access contention resolution. The VGCS\_UPLINK\_GRANT message shall therefore include a request reference (reflecting the UPLINK\_ACCESS) and the physical information required for transmission on the voice group call channel uplink. On receipt of a VGCS\_UPLINK\_GRANT, the related mobile station can start to send speech directly. + +**UPLINK\_BUSY:** This connectionless RR message is sent on the downlink FACCH to inform all mobile stations that the uplink is now busy. UPLINK\_BUSY indicates the talker priority "emergency subscriber" of the new talking service subscriber to all listening service subscribers. + +NOTE 18: The order of UPLINK\_BUSY and SABM message is independent. + +**SABM(L3msg):** The layer 2 link is set up and layer 3 information on classmark and mobile station identity included. + +**UA(L3msg):** The layer 2 link is acknowledged and the layer 3 information reflected for contention resolution. + +NOTE 19: Dedicated signalling connection on the main DCCH needs to be established. + +**UPLINK\_REQUEST:** The request for the uplink containing the MS identity and the talker priority is indicated to the MSC. Only one request per BSS shall be forwarded. + +NOTE 20: As the BSS supports the use of talker priorities and receives from the MS a talker priority different from "normal subscriber", the BSS delays the sending of the UPLINK\_REQUEST message to the MSC, until SABM(L3msg) with the MS identity is received from the MS. Then the BSS includes the layer 3 message, the talker priority, and the cell identity of the cell where the UPLINK\_ACCESS message was received in the UPLINK\_REQUEST message. In this case the UPLINK\_REQUEST\_CONFIRM message may be omitted by the BSS. + +NOTE 20a: In a RANflex configuration (with or without group call redundancy) the uplink requesting subscriber's VMSC may be different from his current location area's group call serving MSC. In this case the retrieval of info from the (distant) VLR is done by means of the MAP service SEND\_GROUP\_CALL\_INFO. + +**UPLINK\_REQUEST\_ACKNOWLEDGE:** The anchor MSC acknowledges the uplink to one BSC, including the talker priority and the emergency mode indication. If uplink requests have been made by more than one BSC or MSC-R, all remaining uplink requests shall be rejected by an UPLINK\_REJECT\_CMD with an emergency mode indication (not presented in figure 4b). On reception of an UPLINK\_REJECT\_CMD the BSS shall send an UPLINK\_REL to the related mobile station, followed by an UPLINK\_BUSY to indicate to the mobile stations that the uplink is in use. The MSC shall send to other BSCs which did not send an uplink request an UPLINK\_SEIZED\_CMD message with an emergency mode indication (not presented in figure 4b). On reception of an UPLINK\_SEIZED\_CMD the BSS shall send an UPLINK\_BUSY to indicate to the mobile stations that the uplink is in use. + +The anchor MSC may also include additional information about the new talking service subscriber in the UPLINK\_REQUEST\_ACKNOWLEDGE, UPLINK\_REJECT\_CMD and UPLINK\_SEIZED\_CMD messages, if the information is available when sending these messages. The BSS may include the additional information in the UPLINK\_BUSY messages, if the information is available when sending these messages and there is sufficient space available in the messages. + +**UPLINK\_BUSY:** This connectionless RR message is sent on the downlink FACCH to inform all mobile stations that the uplink is now busy with talker priority "emergency subscriber" and that the emergency mode is set in the network. The message is repeated on the FACCH every T1 seconds. + +**FORWARD\_GROUP\_CALL\_SIGNALLING (uplink seized command, emergency subscriber, add info):** This message is sent to all relay MSCs, to inform all mobile stations roaming in parts of the group call area which are controlled by relay MSCs, that the uplink is now busy for a talker with talker priority "emergency subscriber" and that the emergency mode indication shall be signalled. Furthermore, the message provides additional information about the new talking service subscriber, if available. + +**ASS\_REQ:** This message contains details of the resource(s) required for the dedicated connection. + +**ASSIGNMENT\_CMD:** This message contains details of the resource(s) required and triggers the assignment procedure of the dedicated channel at the MS. + +**ASSIGNMENT\_COMP:** Standard message. + +**ASS\_COMP:** Standard message. + +**VGCS\_ADD\_INFO:** The MSC sends additional information about the new talking service subscriber to all BSCs, unless the information was already included in the UPLINK\_REQUEST\_ACKNOWLEDGE, UPLINK\_REJECT\_CMD and UPLINK\_SEIZED\_CMD messages. The BSCs broadcast ADD\_INFO messages containing the additional information to all listeners (not shown in figure 4b), unless the information was already included in the UPLINK\_BUSY messages. Additionally, the MSC sends the additional information on the dedicated connection for the previous talker, before this connection is released. + +**CLEAR COMMAND:** The MSC requests the BSS to clear radio and terrestrial resources associated with previous talker. + +**CLEAR\_COMP:** Standard message. + +**CHAN\_RELEASE:** The BSS sends a channel release message to the previous talker's mobile station including the channel description of the voice group call channel to which the mobile station shall tune to. Additionally the BSS includes the talker priority of the new talker and the additional information, if available, and the emergency mode indication, if applicable. + +**DISC:** Two layer 2 disconnect messages shall be sent by the mobile station to the network. + +**SCCP\_RLSD:** Standard message. + +**SCCP\_RLC:** Standard message. + +**Conversation proceeds:** Once the mobile station has control of the uplink, it shall be able to communicate directly. The two-way nature of the conference bridge will ensure that they are already connected to all appropriate downlink channels. + +![Sequence diagram showing signalling information for voice group call uplink access. Lifelines: MS, BSS, MSC-A, MSC-R. The diagram shows the flow of messages between MS and BSS, BSS and MSC-A, and MSC-A and MSC-R. It starts with a conversation in emergency mode, followed by an UPLINK_ACCESS request, VGCS_UPLINK_GRANT, SABM(L3msg), UA(L3msg), EMERGENCY_RESET_IND, EMERGENCY_RESET_COMMAND, DISC, UPLINK_RELEASE, UPLINK_BUSY, and finally a conversation in normal mode.](8307f6b04df072c9332f9987e034272c_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC-A + participant MSC-R + + Note over MS, MSC-A: Conversation proceeds with talker priority +"emergency subscriber", +"emergency mode" is set + MS-->>MSC-A: + Note over MS, BSS: UPLINK_ACCESS +(emergency mode reset +request) + MS->>BSS: + Note over MS, BSS: VGCS_UPLINK_GRANT + BSS-->>MS: + Note over MS, BSS: SABM(L3msg) + MS->>BSS: + Note over MS, BSS: UA (L3msg) + BSS-->>MS: + Note over BSS, MSC-A: EMERGENCY_ +RESET_IND +(L3msg) + BSS->>MSC-A: + Note over MSC-A: MSC-A checks +subscription for group ID +and talker priority (NOTE +21a) + Note over MSC-A, MSC-R: FORW._GROUP CALL_SIGN +(emergency mode reset command) + MSC-A->>MSC-R: + Note over BSS, MSC-A: EMERGENCY_ +RESET_COMMAND + MSC-A-->>BSS: + Note over MS, BSS: UPLINK_RELEASE + BSS-->>MS: + Note over MS, BSS: DISC + MS->>BSS: + Note over MS, BSS: UPLINK_BUSY +(normal subscriber) + BSS-->>MS: + Note over MS, MSC-A: Conversation proceeds with talker priority +"normal subscriber" + MS-->>MSC-A: + +``` + +Sequence diagram showing signalling information for voice group call uplink access. Lifelines: MS, BSS, MSC-A, MSC-R. The diagram shows the flow of messages between MS and BSS, BSS and MSC-A, and MSC-A and MSC-R. It starts with a conversation in emergency mode, followed by an UPLINK\_ACCESS request, VGCS\_UPLINK\_GRANT, SABM(L3msg), UA(L3msg), EMERGENCY\_RESET\_IND, EMERGENCY\_RESET\_COMMAND, DISC, UPLINK\_RELEASE, UPLINK\_BUSY, and finally a conversation in normal mode. + +**Figure 4c: Signalling information required for the voice group call uplink access in the anchor MSC with "emergency mode reset request"** + +**UPLINK\_ACCESS:** This is sent on the uplink of the voice group call channel using random access procedures. The UPLINK\_ACCESS message is similar to a channel request but sent on the group call channel uplink. The establishment cause for emergency mode reset request as defined in 3GPP TS 44.018 shall be used for this purpose. + +**EMERGENCY\_RESET\_IND:** The reception of an emergency mode reset request is indicated to the MSC. Only one request per BSC shall be forwarded. + +NOTE 21: The BSS delays the sending of the EMERGENCY\_RESET\_IND message to the MSC, until SABM(L3msg) with the MS identity is received from the MS. Then the BSS includes the layer 3 message and the cell identity of the cell where the UPLINK\_ACCESS message was received in the EMERGENCY\_RESET\_IND message. + +NOTE 21a: In a RANflex configuration (with or without group call redundancy) the uplink requesting subscriber's VMSC may be different from his current location area's group call serving MSC. In this case the retrieval of info from the (distant) VLR is done by means of the MAP service SEND\_GROUP\_CALL\_INFO. + +**VGCS\_UPLINK\_GRANT:** The reply to the uplink request sent on the voice group channel downlink containing information for synchronisation of the mobile station to the network and uplink access contention resolution. The VGCS\_UPLINK\_GRANT message shall therefore include a request reference (reflecting the UPLINK\_ACCESS) and the physical information required for transmission on the voice group call channel uplink. + +**SABM(L3msg):** The layer 2 link is set up and layer 3 information on classmark and mobile station identity included. + +**UA(L3msg):** The layer 2 link is acknowledged and the layer 3 information reflected for contention resolution. + +**UPLINK\_RELEASE:** When the BSS has forwarded the emergency mode reset request it releases the layer 2 link. A message indicating release of the uplink is required to be sent from the BSS to the MS on the FACCH. + +**EMERGENCY\_RESET\_COMMAND:** The anchor MSC commands all BSCs involved in the voice group call to reset the emergency mode. If the BSC receives an EMERGENCY\_RESET\_COMMAND message, it changes the content of the NCH to indicate "no emergency mode" and the talker priority of the current talking service subscriber to "normal subscriber", if the previous uplink status was uplink busy with talker priority "emergency subscriber". + +**FORWARD\_GROUP\_CALL\_SIGNALLING (emergency mode reset command):** This message is sent to all relay MSCs, to inform all BSCs controlled by relay MSCs that the emergency mode indication shall not be sent any longer and that the talker priority of the current talking service subscriber is changed to "normal subscriber", if the previous uplink status was uplink busy with talker priority "emergency subscriber". + +**UPLINK\_BUSY:** This connectionless RR message is sent on the downlink FACCH to inform all mobile stations that the voice group call is no longer in emergency mode and that the talker priority was changed to "normal subscriber", if the previous uplink status was uplink busy with talker priority "emergency subscriber". The message is repeated on the FACCH every T1 seconds. + +**Conversation proceeds:** The conversation of the current talker is not interrupted. + + + +![](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +Sequence diagram illustrating the interaction between MS, BSS, MSC-A, and MSC-R. + +The sequence of messages is as follows: + +- Conversation proceeds with talker priority "normal subscriber" (MS to MSC-A) +- MS leaves the group call +- MS sends RACH(CHAN\_REQ) to BSS +- BSS sends IMM\_ASS to MS +- MS sends SABM(Priority Uplink Request) to BSS +- BSS sends UPLINK\_REQUEST (privileged subscriber) to MSC-A +- MSC-A sends UA(Priority Uplink Req) to BSS +- BSS sends CHAN\_RELEASE to MS +- MS sends DISC to BSS +- BSS sends UA to MS +- MS rejoins the group call +- BSS sends UPLINK\_REQ\_ACK (privileged subscriber) to MSC-A +- MSC-A performs internal actions: Retrieve additional info From the VLR (NOTE 21b) and Current Talker Released: +- MSC-A sends FORW. GROUP CALL SIGNAL (uplink seized command, privileged subscriber, add info) to MSC-R +- MS sends UPLINK\_RELEASE to BSS +- MS sends DISC to BSS +- BSS sends UA to MS +- MS sends VGCS\_UPLINK\_GRANT to BSS +- BSS sends UPLINK\_BUSY to MS +- MS sends SABM(L3msg) to BSS +- BSS sends UA (L3msg) to MS +- BSS sends UPLINK\_REQ\_CONF (L3msg) to MSC-A +- MSC-A sends VGCS ADD INFO to BSS +- Conversation proceeds with talker priority "privileged subscriber" (MSC-A to BSS) + +![Diagram showing four rectangular boxes representing network entities. A dashed arrow points from the first box on the left to the third box. The second and fourth boxes are positioned below the first and third boxes respectively.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +Diagram showing four rectangular boxes representing network entities. A dashed arrow points from the first box on the left to the third box. The second and fourth boxes are positioned below the first and third boxes respectively. + +**Figure 4d: Signalling information required for the voice group call uplink request via RACH with talker priority "privileged subscriber" in the anchor MSC and pre-emption of the current talker (normal case, without contention resolution)** + +**RACH(CHAN\_REQ):** Standard message to request an SDCCH. + +**IMM\_ASS:** Standard message sent on the AGCH. + +**SABM (PRIORITY\_UPLINK\_REQ):** L3 message PRIORITY\_UPLINK\_REQ sent on the allocated channel. + +**UA (PRIORITY\_UPLINK\_REQ):** This message is used to acknowledge the layer 2 link and provide contention resolution of the priority uplink request. + +**UPLINK\_BUSY** (not presented in figure 4d): If validation of Priority Uplink Requests applies for the group call, the BSS, on receipt of a valid Priority Uplink Request, shall send an UPLINK\_BUSY on the downlink FACCH to inform all mobile stations that a priority request has been made and to provide a new token. The message is sent on Tbb expiry. + +**CHAN\_RELEASE:** The BSS sends a channel release message to the service subscriber's mobile station. + +**DISC:** Standard message to release the layer 2 link. + +**UA:** Standard message to acknowledge release of the layer 2 link. + +**UPLINK\_REQUEST:** The request for the uplink containing the MS identity and the talker priority is indicated to the MSC. Only one request per BSS shall be forwarded. + +**UPLINK\_REQUEST\_ACKNOWLEDGE (privileged subscriber):** The anchor MSC acknowledges the uplink to one BSC. If uplink requests have been made by more than one BSC or MSC-R, all remaining uplink requests shall be rejected by an UPLINK\_REJECT\_CMD which is not presented in figure 4d. On reception of an UPLINK\_REJECT\_CMD the BSS shall send an UPLINK\_REL to the related mobile station, followed by an UPLINK\_BUSY to indicate to the mobile stations that the uplink is in use. The MSC shall send to other BSCs which did not send an uplink request an UPLINK\_SEIZED\_CMD message which is not presented in figure 4d. On reception of an UPLINK\_SEIZED\_CMD the BSS shall send an UPLINK\_BUSY to indicate to the mobile stations that the uplink is in use. + +The anchor MSC may also include additional information about the new talking service subscriber in the UPLINK\_REQUEST\_ACKNOWLEDGE, UPLINK\_REJECT\_CMD and UPLINK\_SEIZED\_CMD messages, if the information is available when sending these messages. The BSS may include the additional information in the UPLINK\_BUSY messages, if the information is available when sending these messages and there is sufficient space available in the messages. + +**UPLINK\_RELEASE:** Upon receipt of an UPLINK\_REQUEST\_ACKNOWLEDGE, UPLINK\_REJ or UPLINK\_SEIZED\_CMD indicating the talker priority of the new talker, the BSC releases the current talker from the uplink by sending a message requesting release of the uplink to the mobile station on the FACCH. + +**DISC:** Standard message to release the layer 2 link. + +**UA:** Standard message to acknowledge release of the layer 2 link. + +NOTE 21b: In a RANflex configuration (with or without group call redundancy) the uplink requesting subscriber's VMSC may be different from his current location area's group call serving MSC. In this case the retrieval of info from the (distant) VLR is done by means of the MAP service SEND\_GROUP\_CALL\_INFO. + +**FORWARD\_GROUP\_CALL\_SIGNALLING (uplink seized command, privileged subscriber, add info):** This message is sent to all relay MSCs, to inform all mobile stations roaming in parts of the group call area which are controlled by relay MSCs, that the uplink is now busy for a talker with talker priority "privileged subscriber". Furthermore, the message provides additional information about the new talking service subscriber, if available. + +**VGCS\_UPLINK\_GRANT:** The reply to the priority uplink request sent on the voice group channel downlink containing information for synchronisation of the mobile station to the network and uplink access contention resolution. The VGCS\_UPLINK\_GRANT message shall therefore include a request reference (reflecting the + +PRIORITY\_UPLINK\_REQUEST) and the physical information required for transmission on the voice group call channel uplink. On receipt of a VGCS\_UPLINK\_GRANT, the related mobile station can start to send speech directly. + +**UPLINK\_BUSY:** This connectionless RR message is sent on the downlink FACCH to inform all mobile stations that the uplink is now busy. If the network supports talker priorities, then the UPLINK\_BUSY indicates the talker priority of the current talking service subscriber to all listening service subscribers and additionally, if the emergency mode is set in the network, the emergency mode indication. The message is repeated on the FACCH every T1 seconds. If validation of Priority Uplink Requests applies each periodic UPLINK\_BUSY message shall include a new token (i.e. a new token is broadcast every T1 seconds). + +NOTE: The order of UPLINK\_BUSY and SABM message is independent. + +**SABM(L3msg):** The layer 2 link is set up and layer 3 information on classmark and mobile station identity included. + +**UA(L3msg):** The layer 2 link is acknowledged and the layer 3 information reflected for contention resolution. + +**UPLINK\_REQUEST\_CONFIRM:** The BSS confirms the uplink use to the MSC together with the mobile station identity, classmark information and optionally the CKSN. + +**VGCS\_ADD\_INFO:** The MSC sends additional information about the new talking service subscriber to all BSCs, unless the information was already included in the UPLINK\_REQUEST\_ACKNOWLEDGE, UPLINK\_REJECT\_CMD and UPLINK\_SEIZED\_CMD messages. The BSCs broadcast ADD\_INFO messages containing the additional information to all listeners (not shown in figure 4d), unless the information was already included in the UPLINK\_BUSY messages. + +**Conversation proceeds:** Once the mobile station has control of the uplink, it shall be able to communicate directly. The two-way nature of the conference bridge will ensure that they are already connected to all appropriate downlink channels. + +![Sequence diagram showing signalling information for a voice group call uplink request via RACH with 'emergency mode reset request' in the anchor MSC. The diagram involves four lifelines: MS, BSS, MSC-A, and MSC-R. The process starts with a conversation as an 'emergency subscriber', followed by the MS leaving the group call, requesting a channel (RACH), receiving immediate assignment (IMM_ASS), sending a priority uplink request (SABM), receiving an emergency reset indication (EMERGENCY_RESET_IND) from MSC-A, acknowledging (UA), releasing the channel (CHAN_RELEASE), discarding (DISC), and then rejoining the group call as a 'normal subscriber' after receiving an emergency reset command (EMERGENCY_RESET_COMMAND) and a forward group call signal (FORW. GROUP CALL SIGNAL) from MSC-A.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC-A + participant MSC-R + + Note right of MS: Conversation proceeds with talker priority "emergency subscriber" + MS->>MSC-A: + Note left of MS: MS leaves the group call + MS->>BSS: RACH(CHAN_REQ) + BSS-->>MS: IMM_ASS + MS->>BSS: SABM(Priority Uplink Request) + BSS->>MSC-A: EMERGENCY_RESET_IND + MSC-A-->>MSC-A: MSC-A checks subscription for group ID and talker priority (NOTE 21c) + MSC-A->>BSS: EMERGENCY_RESET_COMMAND + MSC-A->>MSC-R: FORW. GROUP CALL SIGNAL (emergency mode reset command) + Note left of MS: MS rejoins the group call + MS->>BSS: UA(Priority Uplink Req) + BSS-->>MS: CHAN_RELEASE + MS->>BSS: DISC + BSS-->>MS: UA + Note right of MS: Conversation proceeds with talker priority "normal subscriber" + MS->>MSC-A: + +``` + +Sequence diagram showing signalling information for a voice group call uplink request via RACH with 'emergency mode reset request' in the anchor MSC. The diagram involves four lifelines: MS, BSS, MSC-A, and MSC-R. The process starts with a conversation as an 'emergency subscriber', followed by the MS leaving the group call, requesting a channel (RACH), receiving immediate assignment (IMM\_ASS), sending a priority uplink request (SABM), receiving an emergency reset indication (EMERGENCY\_RESET\_IND) from MSC-A, acknowledging (UA), releasing the channel (CHAN\_RELEASE), discarding (DISC), and then rejoining the group call as a 'normal subscriber' after receiving an emergency reset command (EMERGENCY\_RESET\_COMMAND) and a forward group call signal (FORW. GROUP CALL SIGNAL) from MSC-A. + +**Figure 4e: Signalling information required for the voice group call uplink request via RACH with "emergency mode reset request" in the anchor MSC (normal case, without contention resolution)** + +**RACH(CHAN\_REQ):** Standard message to request an SDCCH. + +**IMM\_ASS:** Standard message sent on the AGCH. + +**SABM (PRIORITY\_UPLINK\_REQ):** L3 message PRIORITY\_UPLINK\_REQ sent on the allocated channel. + +**UA (PRIORITY\_UPLINK\_REQ):** This message is used to acknowledge the layer 2 link and provide contention resolution of the priority uplink request. + +**CHAN\_RELEASE:** The BSS sends a channel release message to the service subscriber's mobile station. + +**DISC:** Standard message to release the layer 2 link. + +**UA:** Standard message to acknowledge release of the layer 2 link. + +**UPLINK\_BUSY** (not presented in figure 4e): If validation of Priority Uplink Requests applies for the group call, the BSS, on receipt of a valid Priority Uplink Request, shall send an UPLINK\_BUSY on the downlink FACCH to inform all mobile stations that a priority request has been made and to provide a new token. The message is sent on Tbb expiry. + +**EMERGENCY\_RESET\_IND:** The reception of an emergency mode reset request is indicated to the MSC. Only one request per BSS shall be forwarded. + +**EMERGENCY\_RESET\_COMMAND:** The anchor MSC commands all BSCs involved in the voice group call to reset the emergency mode. If the BSC receives an EMERGENCY\_RESET\_COMMAND message, it changes the content of the NCH to indicate "no emergency mode" and the talker priority of the current talking service subscriber to "normal subscriber", if the previous uplink status was uplink busy with talker priority "emergency subscriber". + +NOTE 21c: In a RANflex configuration (with or without group call redundancy) the uplink requesting subscriber's VMSC may be different from his current location area's group call serving MSC. In this case the retrieval of info from the (distant) VLR is done by means of the MAP service SEND\_GROUP\_CALL\_INFO. + +**FORWARD\_GROUP\_CALL\_SIGNALLING (emergency mode reset command):** This message is sent to all relay MSCs, to inform all BSCs controlled by relay MSCs that the emergency mode indication shall not be sent any longer and that the talker priority of the current talking service subscriber is changed to "normal subscriber", if the previous uplink status was uplink busy with talker priority "emergency subscriber". + +**UPLINK\_BUSY:** This connectionless RR message is sent on the downlink FACCH to inform all mobile stations that the voice group call is no longer in emergency mode and that the talker priority was changed to "normal subscriber", if the previous uplink status was uplink busy with talker priority "emergency subscriber". The message is repeated on the FACCH every T1 seconds. . If validation of Priority Uplink Requests applies each periodic UPLINK\_BUSY message shall include a new token (i.e. a new token is broadcast every T1 seconds). + +**Conversation proceeds:** The conversation of the current talker is not interrupted. + +![Sequence diagram showing signalling information for voice group call uplink access. Lifelines: MS, BSS, MSC-R, MSC-A. The sequence starts with UPLINK_FREE from MS to BSS, followed by UPLINK_ACCESS from MS to BSS. BSS sends UPLINK_REQUEST (NOTE 22) to MSC-R. MSC-R sends PROCESS GROUP CALL_SIGN. (uplink request) to MSC-A. MSC-A sends FORWARD GROUP CALL_SIGN. (uplink request ack) to MSC-R. MSC-R sends UPLINK_REQ_ACK to BSS. BSS sends UPLINK_REQ_CONF (L3msg) (NOTE 26) to MSC-R. MSC-R sends Retrieve additional info from VLR (NOTE 26a) to MSC-A. MSC-A sends PROCESS GROUP CALL_SIGN. (add_info) to MSC-R. MSC-R sends VGCS_ADD_INFO to BSS. BSS sends Conversation proceeds to MSC-R. MSC-R sends UPLINK_RELEASE_I to BSS. BSS sends UPLINK_RELEASE (NOTE 28) to MS. MS sends UPLINK_FREE to BSS. BSS sends PROCESS_GROUP CALL_SIGN. (uplink release indication) to MSC-R.](26d664119ad25250780f554633444e54_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC-R + participant MSC-A + + Note left of MS: UPLINK_FREE + MS-->>BSS: UPLINK_FREE + Note left of MS: UPLINK_ACCESS + MS-->>BSS: UPLINK_ACCESS + BSS-->>MSC-R: UPLINK_REQUEST (NOTE 22) + MSC-R-->>MSC-A: PROCESS GROUP CALL_SIGN. (uplink request) + MSC-A-->>MSC-R: FORWARD GROUP CALL_SIGN. (uplink request ack) + MSC-R-->>BSS: UPLINK_REQ_ACK + BSS-->>MSC-R: UPLINK_REQ_CONF (L3msg) (NOTE 26) + MSC-R-->>MSC-A: Retrieve additional info from VLR (NOTE 26a) + MSC-A-->>MSC-R: PROCESS GROUP CALL_SIGN. (add_info) + MSC-R-->>BSS: VGCS_ADD_INFO + BSS-->>MSC-R: Conversation proceeds + MSC-R-->>BSS: UPLINK_RELEASE_I + BSS-->>MS: UPLINK_RELEASE (NOTE 28) + Note left of MS: UPLINK_FREE + MS-->>BSS: UPLINK_FREE + BSS-->>MSC-R: PROCESS_GROUP CALL_SIGN. (uplink release indication) + +``` + +Sequence diagram showing signalling information for voice group call uplink access. Lifelines: MS, BSS, MSC-R, MSC-A. The sequence starts with UPLINK\_FREE from MS to BSS, followed by UPLINK\_ACCESS from MS to BSS. BSS sends UPLINK\_REQUEST (NOTE 22) to MSC-R. MSC-R sends PROCESS GROUP CALL\_SIGN. (uplink request) to MSC-A. MSC-A sends FORWARD GROUP CALL\_SIGN. (uplink request ack) to MSC-R. MSC-R sends UPLINK\_REQ\_ACK to BSS. BSS sends UPLINK\_REQ\_CONF (L3msg) (NOTE 26) to MSC-R. MSC-R sends Retrieve additional info from VLR (NOTE 26a) to MSC-A. MSC-A sends PROCESS GROUP CALL\_SIGN. (add\_info) to MSC-R. MSC-R sends VGCS\_ADD\_INFO to BSS. BSS sends Conversation proceeds to MSC-R. MSC-R sends UPLINK\_RELEASE\_I to BSS. BSS sends UPLINK\_RELEASE (NOTE 28) to MS. MS sends UPLINK\_FREE to BSS. BSS sends PROCESS\_GROUP CALL\_SIGN. (uplink release indication) to MSC-R. + +**Figure 5: Signalling information required for the voice group call uplink access in the relay MSC without talker priority (normal case, without contention resolution)** + +**UPLINK\_FREE:** This connectionless RR message is repeatedly sent by the BSS on the main signalling link (FACCH) to inform all mobile stations of the voice group call members that the uplink is free. + +**UPLINK\_ACCESS:** This is sent on the uplink of the voice group call channel using random access procedures. The UPLINK\_ACCESS message is similar to a channel request but sent on the group call channel uplink. The establishment cause for subsequent talker uplink request as defined in 3GPP TS 44.018 shall be used for this purpose. The mobile station may send repeated UPLINK\_ACCESS messages (see 3GPP TS 44.018). + +**UPLINK\_REQUEST:** The request for the uplink is indicated to the MSC. Only one request per BSC shall be forwarded. + +NOTE 22: If the BSS supports the use of talker priorities and receives from the MS a talker priority different from "normal subscriber", the BSS delays the sending of the UPLINK\_REQUEST message to the MSC, until SABM(L3msg) is received from the MS. Then the BSS includes the layer 3 message, the talker priority, and the cell identity of the cell where the UPLINK\_ACCESS message was received in the UPLINK\_REQUEST message. In this case the UPLINK\_REQUEST\_CONFIRM message may be omitted by the BSS. + +**VGCS\_UPLINK\_GRANT:** The reply to the uplink request sent on the voice group channel downlink containing information for synchronisation of the mobile station to the network and uplink access contention resolution. The VGCS\_UPLINK\_GRANT message shall therefore include a request reference (reflecting the UPLINK\_ACCESS) and the physical information required for transmission on the voice group call channel uplink. On receipt of a VGCS\_UPLINK\_GRANT, the related mobile station can start to send speech directly. + +NOTE 23: UPLINK\_FREE messages are stopped immediately. + +**UPLINK\_BUSY:** This connectionless RR message is sent on the downlink FACCH to inform all mobile stations that the uplink is now busy. + +NOTE 24: If the BSS supports the use of talker priorities, then it indicates the talker priority of the current talking service subscriber and the status of the emergency mode in the UPLINK\_BUSY message and repeats the message on the FACCH every T1 seconds. + +NOTE 25: The order of UPLINK\_BUSY and SABM message is independent. + +**SABM (L3msg):** The layer 2 link is set up and layer 3 information on classmark and mobile station identity included. + +**UA (L3msg):** The layer 2 link is acknowledged and the layer 3 information reflected for contention resolution. + +**PROCESS\_GROUP\_CALL\_SIGNALLING (uplink request):** This message is sent to the anchor MSC, to indicate that the uplink is requested by a subscriber roaming in the relay MSC area. + +NOTE 26: If the UPLINK\_REQUEST message contained the layer 3 message, the message provides additional information about the new talking service subscriber, if available. + +**FORWARD\_GROUP\_CALL\_SIGNALLING (uplink request ack):** This message is sent to the relay MSC, to indicate that the uplink is granted to the mobile station roaming in parts of the group call area which are controlled by relay MSC. + +**UPLINK\_REQUEST\_ACKNOWLEDGE:** The relay MSC acknowledges the uplink to one BSC. If uplink requests have been made by more than one BSC, all remaining uplink requests shall be rejected by an UPLINK\_REJECT\_CMD which is not presented in figure 5. On reception of an UPLINK\_REJECT\_CMD the BSS shall send an UPLINK\_REL to the related mobile station, followed by an UPLINK\_BUSY to indicate to the mobile stations that the uplink is in use. The MSC shall send to other BSCs which did not send an uplink request an UPLINK\_SEIZED\_CMD message which is not presented in figure 5. On reception of an UPLINK\_SEIZED\_CMD the BSS shall send an UPLINK\_BUSY to indicate to the mobile stations that the uplink is in use. If the BSS supports the use of talker priorities, then it indicates the talker priority of the current talking service subscriber and the status of the emergency mode in the UPLINK\_BUSY message and repeats the message on the FACCH every T1 seconds. + +**UPLINK\_REQUEST\_CONFIRM :** The BSS confirms the uplink use to the MSC together with the mobile station identity. + +NOTE 26a: In a RANflex configuration (with or without group call redundancy) the uplink requesting subscriber's VMSC may be different from his current location area's group call serving MSC. In this case the retrieval of info from the (distant) VLR is done by means of the MAP service SEND\_GROUP\_CALL\_INFO. + +**VGCS\_ADD\_INFO:** The MSC sends additional information about the new talking service subscriber to all BSCs. The BSCs broadcast ADD\_INFO messages containing the additional information to all listeners (not shown in figure 5). + +**PROCESS\_GROUP\_CALL\_SIGNALLING (additional info):** This message is sent to the anchor MSC to provide information about the new talking service subscriber. The anchor MSC forwards the message to all other relay MSCs. + +NOTE 27: This message is omitted, if the additional info was already included in the PROCESS\_GROUP\_CALL\_SIGNALLING (uplink request) message. + +**Conversation proceeds:** Once the mobile station has control of the uplink, it shall be able to communicate directly. The two-way nature of the conference bridge will ensure that they are already connected to all appropriate downlink channels. + +**UPLINK\_RELEASE:** When the service subscriber who has access to the uplink wants to release the channel, then a message indicating release of the uplink is required to be sent from the MS to the BSS on the FACCH. + +NOTE 28: For different cases of uplink release and the related message flows refer to Figure 6.b to 6.g. + +**UPLINK\_RELEASE\_INDICATION:** The BSS informs the MSC on the uplink release. + +**PROCESS\_GROUP\_CALL\_SIGNALLING (uplink release indication):** The relay MSC indicates to the anchor MSC that the uplink is free. + + + +![Sequence diagram showing communication between MS, BSS, MSC-R, and MSC-A. The diagram illustrates a group call process involving uplink requests, channel releases, and rejoining the call.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC-R + participant MSC-A + + Note right of MS: Conversation proceeds with talker priority "normal subscriber" + MS->>MSC-R: + Note left of MS: MS leaves the group call + MS->>BSS: RACH(CHAN_REQ) + BSS-->>MS: IMM_ASS + MS->>BSS: SABM(Priority Uplink Request) + BSS->>MSC-R: UPLINK_REQUEST (privileged subscriber) + MSC-R-->>BSS: Retrieve additional From the VLR (NOTE 28a) + MSC-R->>MSC-A: PROCESS GROUP CALL SIGNAL (uplink request, privileged subscriber, add info) + MS->>BSS: CHAN_RELEASE + BSS-->>MS: DISC + MS->>BSS: UA + Note left of MS: MS rejoins the group call + MSC-A->>MSC-R: FORWARD GROUP CALL SIGNAL (uplink request ack) + MSC-R-->>BSS: UPLINK_REQ_ACK + MS->>BSS: UPLINK_RELEASE + BSS-->>MS: DISC + MS->>BSS: UA + MS->>BSS: VGCS_UPLINK_GRANT + MS->>BSS: UPLINK_BUSY + MS->>BSS: SABM(L3msg) + BSS-->>MS: UA(L3msg) + BSS->>MSC-R: UPLINK_REQ_CONF (L3msg) + MSC-R-->>BSS: VGCS ADD INFO + +``` + +Sequence diagram showing communication between MS, BSS, MSC-R, and MSC-A. The diagram illustrates a group call process involving uplink requests, channel releases, and rejoining the call. + +![Diagram showing a conversation proceeding with talker priority 'privileged subscriber' between two mobile stations (MS) via a relay MSC. The diagram consists of four vertical rectangles representing the MS, BSS, relay MSC, and anchor MSC. A dashed double-headed arrow points from the first MS to the third rectangle (relay MSC), with the text 'Conversation proceeds with talker priority "privileged subscriber"' above it.](dd5771673aececa53d42ece89218299d_img.jpg) + +Diagram showing a conversation proceeding with talker priority 'privileged subscriber' between two mobile stations (MS) via a relay MSC. The diagram consists of four vertical rectangles representing the MS, BSS, relay MSC, and anchor MSC. A dashed double-headed arrow points from the first MS to the third rectangle (relay MSC), with the text 'Conversation proceeds with talker priority "privileged subscriber"' above it. + +**Figure 5a: Signalling information required for the voice group call uplink request via RACH with talker priority "privileged subscriber" in the relay MSC (normal case, without contention resolution)** + +**RACH(CHAN\_REQ):** Standard message to request an SDCCH. + +**IMM\_ASS:** Standard message sent on the AGCH. + +**SABM (PRIORITY\_UPLINK\_REQ):** L3 message PRIORITY\_UPLINK\_REQ sent on the allocated channel. + +**UA (PRIORITY\_UPLINK\_REQ):** This message is used to acknowledge the layer 2 link and provide contention resolution of the service request. + +**CHAN\_RELEASE:** The BSS sends a channel release message to the service subscriber's mobile station. + +**DISC:** Standard message to release the layer 2 link. + +**UA:** Standard message to acknowledge release of the layer 2 link. + +**UPLINK\_BUSY** (not presented in figure 5a): If validation of Priority Uplink Requests applies for the group call, the BSS, on receipt of a valid Priority Uplink Request, shall send an UPLINK\_BUSY on the downlink FACCH to inform all mobile stations that a priority request has been made and to provide a new token. The message is sent on Tbb expiry. + +**UPLINK\_REQUEST:** The request for the uplink is indicated to the MSC. Only one request per BSS shall be forwarded. + +NOTE 28a: In a RANflex configuration (with or without group call redundancy) the uplink requesting subscriber's VMSC may be different from his current location area's group call serving MSC. In this case the retrieval of info from the (distant) VLR is done by means of the MAP service SEND\_GROUP\_CALL\_INFO. + +**PROCESS\_GROUP\_CALL\_SIGNALLING (uplink request, privileged subscriber, add info):** This message is sent to the anchor MSC, to indicate that the uplink is requested by a subscriber with talker priority "privileged subscriber" roaming in the relay MSC area. Furthermore, the message provides additional information about the service subscriber requesting the uplink, if additional information is available. + +**FORWARD\_GROUP\_CALL\_SIGNALLING (uplink request ack):** This message is sent to the relay MSC, to indicate that the uplink is granted to the mobile station roaming in parts of the group call area which are controlled by the relay MSC. + +**UPLINK\_REQUEST\_ACKNOWLEDGE:** The relay MSC acknowledges the uplink to one BSC. If uplink requests have been made by more than one BSC, all remaining uplink requests shall be rejected by an UPLINK\_REJECT\_CMD which is not presented in figure 5a. On reception of an UPLINK\_REJECT\_CMD the BSS shall send an UPLINK\_REL to the related mobile station, followed by an UPLINK\_BUSY to indicate to the mobile stations that the uplink is in use. The MSC shall send to other BSCs which did not send an uplink request an UPLINK\_SEIZED\_CMD message which is not presented in figure 5a. On reception of an UPLINK\_SEIZED\_CMD the BSS shall send an UPLINK\_BUSY to indicate to the mobile stations that the uplink is in use. + +The anchor MSC may also include additional information about the new talking service subscriber in the UPLINK\_REQUEST\_ACKNOWLEDGE, UPLINK\_REJECT\_CMD and UPLINK\_SEIZED\_CMD messages, if the information is available when sending these messages. + +**UPLINK\_RELEASE:** Upon receipt of an UPLINK\_REQUEST\_ACKNOWLEDGE, UPLINK\_REJECT\_CMD or UPLINK\_SEIZED\_CMD indicating the talker priority of the new talker, the BSC releases the current talker from the uplink by sending a message requesting release of the uplink to the mobile station on the FACCH. + +**DISC:** Standard message to release the layer 2 link. + +**UA:** Standard message to acknowledge release of the layer 2 link. + +**VGCS\_UPLINK\_GRANT:** The reply to the priority uplink request sent on the voice group channel downlink containing information for synchronisation of the mobile station to the network and uplink access contention resolution. The VGCS\_UPLINK\_GRANT message shall therefore include a request reference (reflecting the PRIORITY\_UPLINK\_REQUEST) and the physical information required for transmission on the voice group call channel uplink. On receipt of a VGCS\_UPLINK\_GRANT, the related mobile station can start to send speech directly. + +**UPLINK\_BUSY:** This connectionless RR message is sent on the downlink FACCH to inform all mobile stations that the uplink is now busy. If the network supports talker priorities, then the UPLINK\_BUSY indicates the talker priority of the current talking service subscriber to all listening service subscribers and additionally, if the emergency mode is set in the network, the emergency mode indication. The message is repeated on the FACCH every T1 seconds. If validation of Priority Uplink Requests applies each periodic UPLINK\_BUSY message shall include a new token (i.e. a new token is broadcast every T1 seconds). The BSS may include the additional information about the new talking service subscriber in the UPLINK\_BUSY message, if the information is available when sending this message and there is sufficient space available in the message. + +NOTE: The order of UPLINK\_BUSY and SABM message is independent. + +**SABM (L3msg):** The layer 2 link is set up and layer 3 information on classmark and mobile station identity included. + +**UA (L3msg):** The layer 2 link is acknowledged and the layer 3 information reflected for contention resolution. + +**UPLINK\_REQUEST\_CONFIRM:** The BSS confirms the uplink use to the MSC together with the mobile station identity, classmark information and optionally the CKSN. + +**VGCS\_ADD\_INFO:** The MSC sends additional information about the new talking service subscriber to all BSCs, unless the information was already included in the UPLINK\_REQUEST\_ACKNOWLEDGE, UPLINK\_REJECT\_CMD and UPLINK\_SEIZED\_CMD messages. The BSCs broadcast ADD\_INFO messages containing the additional information to all listeners (not shown in figure 5a), unless the information was already included in the UPLINK\_BUSY messages. + +**Conversation proceeds:** Once the mobile station has control of the uplink, it shall be able to communicate directly. The two-way nature of the conference bridge will ensure that they are already connected to all appropriate downlink channels. + +![Sequence diagram showing signalling information between MS, MSC-A, and Disp. The diagram illustrates the flow of messages for conversation control, including 'Conversation Proceeds', 'DTMF Tones (start_talking) or DTMF message (start_talking)', 'Grant tone', 'Set Parameter (D-ATT = TRUE)', 'DTMF Tones (end_talking) or DTMF message (end_talking)', and 'Set Parameter (D-ATT = FALSE)'.](ca5dc5fde2061d0ca2051ef7840fc842_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC-A + participant Disp. + Note right of MS: Conversation Proceeds + MS->>MSC-A: + MSC-A->>Disp.: DTMF Tones (start_talking) or DTMF message (start_talking) + Note right of Disp.: Grant tone + Disp.->>MSC-A: + MSC-A->>MS: Set Parameter (D-ATT = TRUE) + Note right of MSC-A: + MSC-A->>Disp.: DTMF Tones (end_talking) or DTMF message (end_talking) + Note right of Disp.: + MSC-A->>MS: Set Parameter (D-ATT = FALSE) + +``` + +Sequence diagram showing signalling information between MS, MSC-A, and Disp. The diagram illustrates the flow of messages for conversation control, including 'Conversation Proceeds', 'DTMF Tones (start\_talking) or DTMF message (start\_talking)', 'Grant tone', 'Set Parameter (D-ATT = TRUE)', 'DTMF Tones (end\_talking) or DTMF message (end\_talking)', and 'Set Parameter (D-ATT = FALSE)'. + +**Figure 5b: Signalling information required when the talker is attached to the Anchor MSC and a dispatcher sends DTMF signals** + +**Conversation proceeds:** The talker is in control of the uplink (see figure 4) and is attached to the Anchor MSC. The mobile station's downlink is muted to prevent any distracting echo being heard by the mobile station user. + +**DTMF Tones (start\_talking) or DTMF message (start\_talking):** This signalling indicates the dispatcher's unmute request to the MSC. DTMF Tones are used by a fixed line dispatcher while the DTMF message is used by a mobile dispatcher. + +**Grant Tone:** The Anchor MSC may optionally play an in-band tone to the dispatcher to indicate that the dispatcher's request is recognized and that the downlink of the talking service subscriber will be unmuted. The attributes of the grant tone (e.g. frequency and duration) are network operator specific.. + +**Set Parameter (D-ATT = TRUE):** The Anchor MSC sends this message to the mobile station to unmute the downlink so that the user can hear what the dispatcher says. + +NOTE 29: This message is sent only when the downlink of the talker is muted. + +**DTMF Tones (end\_talking) or DTMF message (end\_talking):** This signalling indicates the dispatcher's mute request to the MSC. DTMF Tones are used by a fixed line dispatcher while the DTMF message is used by a mobile dispatcher. + +**Set Parameter (D-ATT = FALSE):** Once the dispatcher indicates that he has finished speaking, the Anchor MSC mutes the talker's downlink. + +NOTE 30: This message is only sent when all dispatchers who have sent the unmuting request have finished their talk. + +![Sequence diagram showing signalling information required when the talker is attached to a Relay MSC and a dispatcher sends DTMF signals. The diagram involves four lifelines: MS, MSC-R, MSC-A, and DISP. The sequence starts with 'Conversation Proceeds' from MSC-R to MS. Then, MSC-A sends 'DTMF Tones (start_talking) or DTMF message (start_talking)' to DISP, followed by 'Grant tone' from MSC-A to DISP. Next, MSC-A sends 'FORWARD_GROUP_CALL_SIGNAL' to MSC-R, which in turn sends 'Set Parameter (D-ATT = TRUE)' to MS. Finally, MSC-A sends another 'FORWARD_GROUP_CALL_SIGNAL' to MSC-R, which sends 'Set Parameter (D-ATT = FALSE)' to MS.](1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC-R + participant MSC-A + participant DISP + Note right of MSC-R: Conversation Proceeds + MSC-A->>DISP: DTMF Tones (start_talking) or DTMF message (start_talking) + MSC-A->>DISP: Grant tone + MSC-A->>MSC-R: FORWARD_GROUP_CALL_SIGNAL + MSC-R->>MS: Set Parameter (D-ATT = TRUE) + MSC-A->>MSC-R: FORWARD_GROUP_CALL_SIGNAL + MSC-R->>MS: Set Parameter (D-ATT = FALSE) + +``` + +Sequence diagram showing signalling information required when the talker is attached to a Relay MSC and a dispatcher sends DTMF signals. The diagram involves four lifelines: MS, MSC-R, MSC-A, and DISP. The sequence starts with 'Conversation Proceeds' from MSC-R to MS. Then, MSC-A sends 'DTMF Tones (start\_talking) or DTMF message (start\_talking)' to DISP, followed by 'Grant tone' from MSC-A to DISP. Next, MSC-A sends 'FORWARD\_GROUP\_CALL\_SIGNAL' to MSC-R, which in turn sends 'Set Parameter (D-ATT = TRUE)' to MS. Finally, MSC-A sends another 'FORWARD\_GROUP\_CALL\_SIGNAL' to MSC-R, which sends 'Set Parameter (D-ATT = FALSE)' to MS. + +**Figure 5c: Signalling information required when the talker is attached to a Relay MSC and a dispatcher sends DTMF signals** + +**Conversation proceeds:** The talker is in control of the uplink (see figure 4) and is attached to a Relay MSC. The mobile station's downlink is muted to prevent any distracting echo being heard by the mobile station user. + +**DTMF Tones (start\_talking) or DTMF message (start\_talking):** This signalling indicates the dispatcher's unmute request to the MSC. DTMF Tones are used by a fixed line dispatcher while the DTMF message is used by a mobile dispatcher. + +**Grant Tone:** The Anchor MSC may optionally play an in-band tone to the dispatcher to indicate that the dispatcher's request is recognized and that the downlink of the talking service subscriber will be unmuted. The attributes of the grant tone (e.g. frequency and duration) are network operator specific. + +**FORWARD\_GROUP\_CALL\_SIGNAL:** This message is sent to the Relay MSC when anchor MSC wants to change the mute/unmute status of the talking service subscriber. In this case **stateAttributes::DA = TRUE**, is set. + +**Set Parameter (D-ATT = TRUE/FALSE):** The Relay MSC sends this message to the talker when a FORWARD GROUP CALL SIGNAL containing a STATE\_ATTRIBUTES information element is received. The D-ATT field is set as received in STATE\_ATTRIBUTES element. + +**DTMF Tones (end\_talking) or DTMF message (end\_talking):** This signalling indicates the dispatcher's mute request to the MSC. DTMF Tones are used by a fixed line dispatcher while the DTMF message is used by a mobile dispatcher. + +**FORWARD\_GROUP\_CALL\_SIGNAL:** This message is sent to the Relay MSC when the anchor MSC wants to change the mute/unmute status of the talking service subscriber. In this case **stateAttributes::DA = FALSE** is set. + +**Set Parameter (D-ATT = FALSE):** Once the dispatcher indicates that he has finished speaking, the MSC mutes the talker's downlink again. + +![Sequence diagram for Figure 5d showing signalling between MS, MSC-A, V-MSC, and Mobile Disp.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC-A + participant V-MSC + participant Mobile Disp. + Note right of MSC-A: Conversation Proceeds + MSC-A->>V-MSC: DTMF Tones (start_talking) + V-MSC->>Mobile Disp.: DTMF message (start_talking) + V-MSC->>MSC-A: Grant tone + MSC-A->>MS: Set Parameter (D-ATT = TRUE) + Mobile Disp.->>V-MSC: DTMF message (end_talking) + V-MSC->>MSC-A: DTMF Tones (end_talking) + MSC-A->>MS: Set Parameter (D-ATT = FALSE) + +``` + +Sequence diagram for Figure 5d showing signalling between MS, MSC-A, V-MSC, and Mobile Disp. + +**Figure 5d: Signalling information required when the talker is attached to the Anchor MSC and a mobile dispatcher who is roaming in a non-Anchor MSC area sends DTMF signals** + +**Conversation proceeds:** The talker is in control of the uplink (see figure 4) and is attached to the Anchor MSC. The mobile station's downlink is muted to prevent any distracting echo being heard by the mobile station user. + +**DTMF message (start\_talking):** This signalling indicates the mobile dispatcher's unmute request to visited MSC. On reception of the DTMF message, the visited MSC will convert it into DTMF tones and send these DTMF tones through the network to the anchor MSC. + +**Grant Tone:** The Anchor MSC may optionally play an in-band tone to the dispatcher to indicate that the dispatcher's request is interpreted as a request to talk and that the downlink of the talking service subscriber will be unmuted. The attributes of the grant tone (e.g. frequency and duration) are network operator specific. + +**Set Parameter (D-ATT = TRUE):** The Anchor MSC sends this message to the talker to force his mobile station to unmute its downlink so that the user can hear what the dispatcher says. + +**DTMF message (end\_talking):** This signalling indicates the mobile dispatcher's mute request to the MSC. + +**Set Parameter (D-ATT = FALSE):** Once the dispatcher indicates that he has finished speaking, the Anchor MSC mutes the talker's downlink. + +![Sequence diagram for Figure 6 showing signalling between MS, BSS, and MSC.](f324fbc5d5af1e4da9cd932389f0064c_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC + Note right of BSS: Conversation proceeds + BSS->>MSC: UPLINK_REL_CMD + MSC->>BSS: UPLINK_RELEASE + BSS->>MS: UPLINK_RELEASE + BSS->>MSC: UPLINK_FREE + +``` + +Sequence diagram for Figure 6 showing signalling between MS, BSS, and MSC. + +**Figure 6: Signalling information required for the voice group call uplink release requested by the network** + +**UPLINK\_REL\_CMD:** When the network wants to release the uplink for any reason, except when a service subscriber with a higher priority has seized the uplink, then a message requesting release of the uplink is required to be sent from the network to the mobile station on the FACCH. + +![Sequence diagram showing signalling information for voice group call uplink release. Lifelines: MS, BSS, MSC. The diagram shows a 'normal subscriber' conversation, followed by a 'privileged subscriber' sending an UPLINK_SEIZED_CMD to the MSC, which then triggers UPLINK_RELEASE and UPLINK_BUSY messages back to the MS via the BSS.](b51423b6c049f5b5fcde42e50b58f18b_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC + Note over MS, MSC: Conversation proceeds with talker priority "normal subscriber" + MS-->MSC: + Note over MS, MSC: UPLINK_SEIZED_CMD (privileged subscriber) + MSC-->BSS: + BSS-->MS: UPLINK_RELEASE + BSS-->MS: UPLINK_BUSY (privileged subscriber) + +``` + +Sequence diagram showing signalling information for voice group call uplink release. Lifelines: MS, BSS, MSC. The diagram shows a 'normal subscriber' conversation, followed by a 'privileged subscriber' sending an UPLINK\_SEIZED\_CMD to the MSC, which then triggers UPLINK\_RELEASE and UPLINK\_BUSY messages back to the MS via the BSS. + +**Figure 6a: Signalling information required for the voice group call uplink release requested by the network; preemption of the current talker by a privileged service subscriber** + +**UPLINK\_SEIZED\_CMD:** When the network wants to release the uplink because a service subscriber with a higher priority has seized the uplink in another BSS area, an UPLINK\_SEIZED\_CMD indicating the talker priority of the new talking service subscriber is sent by the MSC. If the BSS has sent an UPLINK\_REQUEST to the MSC, the MSC will either send UPLINK\_REQUEST\_ACKNOWLEDGE or UPLINK\_REJECT instead of the UPLINK\_SEIZED\_CMD. + +The following figures 6.b to 6.g show the message flows applicable for the uplink release in normal and error cases, dependent on whether the talker is + +- on a dedicated link (e.g. the talker is the originator); or +- on the group call channel (e.g. the talker is a subsequent talker). + +![Sequence diagram for Figure 6.b: Uplink release for the talker on a dedicated link: normal case. The diagram shows the interaction between MS, BSS, MSC, and BSSs. The sequence starts with MS sending 'Uplink release' to BSS. BSS sends 'Uplink Rel Indication (cause = call control)' to MSC. MSC sends 'Uplink rel command' to BSSs. A note indicates that 'Upl_Rel_cmd' is sent to all BSSs of the GC area except the BSC that sent the 'Upl_rel_ind.'. BSSs send 'Uplink free' to MS. BSS sends 'Clear Command' to MSC. MSC sends 'Clear complete' to BSS. BSS sends 'SCCP_RLSD' to MSC. MSC sends 'SCCP_RLC' to BSS. BSS sends 'Channel release' to MS. MS sends 'DISC' to BSS.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC + participant BSSs + MS->>BSS: Uplink release + BSS->>MSC: Uplink Rel Indication (cause = call control) + MSC->>BSSs: Uplink rel command + Note right of MSC: Upl_Rel_cmd is sent +to all BSSs of the GC +area except that BSC +which sent the +Upl_rel_ind. + BSS->>MS: Uplink free + BSS->>MSC: Clear Command + MSC->>BSS: Clear complete + BSS->>MSC: SCCP_RLSD + MSC->>BSS: SCCP_RLC + BSS->>MS: Channel release + MS->>BSS: DISC + +``` + +Sequence diagram for Figure 6.b: Uplink release for the talker on a dedicated link: normal case. The diagram shows the interaction between MS, BSS, MSC, and BSSs. The sequence starts with MS sending 'Uplink release' to BSS. BSS sends 'Uplink Rel Indication (cause = call control)' to MSC. MSC sends 'Uplink rel command' to BSSs. A note indicates that 'Upl\_Rel\_cmd' is sent to all BSSs of the GC area except the BSC that sent the 'Upl\_rel\_ind.'. BSSs send 'Uplink free' to MS. BSS sends 'Clear Command' to MSC. MSC sends 'Clear complete' to BSS. BSS sends 'SCCP\_RLSD' to MSC. MSC sends 'SCCP\_RLC' to BSS. BSS sends 'Channel release' to MS. MS sends 'DISC' to BSS. + +NOTE: The messages CLEAR CMD, CLEAR COM, etc., are used to release the dedicated connection of the talker. + +**Figure 6.b: Uplink release for the talker on a dedicated link: normal case** + +![Sequence diagram for Figure 6.c: Uplink release for the talker on a dedicated link: loss of radio contact or equipment failure (TRX, PCM ...). The diagram shows the interaction between MS, BSS, MSC, and BSSs. The sequence starts with BSS sending 'Uplink Rel Indication (cause = radio interface failure / equipment failure)' to MSC. MSC sends 'Uplink rel command' to BSSs. A note indicates that 'Upl_Rel_cmd' is sent to all BSSs of the GC area except the BSC that sent the 'Upl_rel_ind.'. BSSs send 'Uplink free' to MS. BSS sends 'Clear Command' to MSC. MSC sends 'Clear complete' to BSS. BSS sends 'SCCP_RLSD' to MSC. MSC sends 'SCCP_RLC' to BSS.](a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC + participant BSSs + BSS->>MSC: Uplink Rel Indication +(cause = radio interface +failure / equipment +failure) + MSC->>BSSs: Uplink rel command + Note right of MSC: Upl_Rel_cmd is sent +to all BSSs of the GC +area except that BSC +which sent the +Upl_rel_ind. + BSS->>MS: Uplink free + BSS->>MSC: Clear Command + MSC->>BSS: Clear complete + BSS->>MSC: SCCP_RLSD + MSC->>BSS: SCCP_RLC + +``` + +Sequence diagram for Figure 6.c: Uplink release for the talker on a dedicated link: loss of radio contact or equipment failure (TRX, PCM ...). The diagram shows the interaction between MS, BSS, MSC, and BSSs. The sequence starts with BSS sending 'Uplink Rel Indication (cause = radio interface failure / equipment failure)' to MSC. MSC sends 'Uplink rel command' to BSSs. A note indicates that 'Upl\_Rel\_cmd' is sent to all BSSs of the GC area except the BSC that sent the 'Upl\_rel\_ind.'. BSSs send 'Uplink free' to MS. BSS sends 'Clear Command' to MSC. MSC sends 'Clear complete' to BSS. BSS sends 'SCCP\_RLSD' to MSC. MSC sends 'SCCP\_RLC' to BSS. + +NOTE: The messages CLEAR CMD, CLEAR COM, etc., are used to release the dedicated connection of the talker. The same message flow applies for all cause values different from "call control". + +**Figure 6.c: Uplink release for the talker on a dedicated link: loss of radio contact or equipment failure (TRX, PCM ...)** + +![Sequence diagram for Figure 6.d: Uplink release for the talker on group call channel: normal case. Lifelines: MS, BSS, MSC, BSSs. The MS sends an 'Uplink release' message to the BSS. The BSS sends an 'Uplink Rel Indication (cause = call control)' to the MSC. The MSC sends an 'Uplink rel command' to the BSSs. A note indicates that the command is sent to all BSSs of the GC area except the BSC that sent the indication. Finally, the BSS sends an 'Uplink free' message to the MS.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +``` +sequenceDiagram + participant MS + participant BSS + participant MSC + participant BSSs + Note right of MS: Uplink release + MS->>BSS: + Note right of BSS: Uplink Rel Indication (cause = call control) + BSS->>MSC: + Note right of MSC: Uplink rel command + MSC->>BSSs: + Note right of BSSs: Upl_Rel_cmd is sent to all BSSs of the GC area except that BSC which sent the Upl_rel_ind. + Note right of BSS: Uplink free + BSS->>MS: +``` + +Sequence diagram for Figure 6.d: Uplink release for the talker on group call channel: normal case. Lifelines: MS, BSS, MSC, BSSs. The MS sends an 'Uplink release' message to the BSS. The BSS sends an 'Uplink Rel Indication (cause = call control)' to the MSC. The MSC sends an 'Uplink rel command' to the BSSs. A note indicates that the command is sent to all BSSs of the GC area except the BSC that sent the indication. Finally, the BSS sends an 'Uplink free' message to the MS. + +Figure 6.d: Uplink release for the talker on group call channel: normal case + +![Sequence diagram for Figure 6.e: Uplink release for the talker on group call channel: loss of radio contact. Lifelines: MS, BSS, MSC, BSSs. The BSS sends an 'Uplink Rel Indication (cause = radio interface failure)' to the MSC. The MSC sends an 'Uplink rel command' to the BSSs. A note indicates that the command is sent to all BSSs of the GC area except the BSC that sent the indication. Finally, the BSS sends an 'Uplink free' message to the MS.](fcbc3c31776721edc98ceb1944ec438f_img.jpg) + +``` +sequenceDiagram + participant MS + participant BSS + participant MSC + participant BSSs + Note right of BSS: Uplink Rel Indication (cause = radio interface failure) + BSS->>MSC: + Note right of MSC: Uplink rel command + MSC->>BSSs: + Note right of BSSs: Upl_Rel_cmd is sent to all BSSs of the GC area except that BSC which sent the Upl_rel_ind. + Note right of BSS: Uplink free + BSS->>MS: +``` + +Sequence diagram for Figure 6.e: Uplink release for the talker on group call channel: loss of radio contact. Lifelines: MS, BSS, MSC, BSSs. The BSS sends an 'Uplink Rel Indication (cause = radio interface failure)' to the MSC. The MSC sends an 'Uplink rel command' to the BSSs. A note indicates that the command is sent to all BSSs of the GC area except the BSC that sent the indication. Finally, the BSS sends an 'Uplink free' message to the MS. + +Figure 6.e: Uplink release for the talker on group call channel: loss of radio contact + +![Sequence diagram for Figure 6.f: Uplink release for the talker on group call channel after equipment failure (TRX, PCM ...), group call re-establishment by the BSS not supported. The diagram shows four lifelines: MS, BSS, MSC, and BSSs. The sequence of messages is: 1. BSS sends 'Uplink Rel Indication (cause = equipment failure)' to MSC. 2. MSC sends 'Uplink rel command' to BSSs. A note indicates that 'Upl_Rel_cmd' is sent to all BSSs of the GC area except that BSC which sent the 'Upl_rel_ind.'. 3. BSS sends 'Uplink free' to MS. 4. MSC sends 'Clear Command' to BSS. 5. BSS sends 'Clear complete' to MSC. 6. MSC sends 'SCCP_RLSD' to BSS. 7. BSS sends 'SCCP_RLC' to MSC.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC + participant BSSs + Note right of MSC: Upl_Rel_cmd is sent to all BSSs of the GC area except that BSC which sent the Upl_rel_ind. + BSS->>MSC: Uplink Rel Indication (cause = equipment failure) + MSC->>BSSs: Uplink rel command + BSS->>MS: Uplink free + MSC->>BSS: Clear Command + BSS->>MSC: Clear complete + MSC->>BSS: SCCP_RLSD + BSS->>MSC: SCCP_RLC + +``` + +Sequence diagram for Figure 6.f: Uplink release for the talker on group call channel after equipment failure (TRX, PCM ...), group call re-establishment by the BSS not supported. The diagram shows four lifelines: MS, BSS, MSC, and BSSs. The sequence of messages is: 1. BSS sends 'Uplink Rel Indication (cause = equipment failure)' to MSC. 2. MSC sends 'Uplink rel command' to BSSs. A note indicates that 'Upl\_Rel\_cmd' is sent to all BSSs of the GC area except that BSC which sent the 'Upl\_rel\_ind.'. 3. BSS sends 'Uplink free' to MS. 4. MSC sends 'Clear Command' to BSS. 5. BSS sends 'Clear complete' to MSC. 6. MSC sends 'SCCP\_RLSD' to BSS. 7. BSS sends 'SCCP\_RLC' to MSC. + +NOTE: The messages CLEAR CMD, CLEAR COM, etc., are used to release the radio and terrestrial resources for the cell serving the talker. The same message flow applies for all cause values different from "call control", and "radio interface failure". + +**Figure 6.f: Uplink release for the talker on group call channel after equipment failure (TRX, PCM ...), group call re-establishment by the BSS not supported** + +The BSC shall send the message UPLINK RELEASE INDICATION with cause value "equipment failure" or another appropriate cause value, if a failure concerning the cell that is serving the talker was detected and the radio and terrestrial resources related to this cell shall be released (see figure 6.5). After receipt of the UPLINK RELEASE INDICATION message the MSC shall send a CLEAR COMMAND message for the respective cell. The BSC does not send CLEAR REQUEST in addition to UPLINK RELEASE INDICATION in order to avoid conflicts. + +![Sequence diagram for Figure 6.g: Release after equipment failure (TRX, PCM ...) concerning a cell that is not serving the talker, group call re-establishment by the BSS not supported. The diagram shows four lifelines: MS, BSS, MSC, and BSSs. The sequence of messages is: 1. BSS sends 'Clear Request (cause = equipment failure)' to MSC. 2. MSC sends 'Clear Command' to BSS. 3. BSS sends 'Clear complete' to MSC. 4. MSC sends 'SCCP_RLSD' to BSS. 5. BSS sends 'SCCP_RLC' to MSC.](6be06b7dc72bb42afcb3465394667c3b_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC + participant BSSs + BSS->>MSC: Clear Request (cause = equipment failure) + MSC->>BSS: Clear Command + BSS->>MSC: Clear complete + MSC->>BSS: SCCP_RLSD + BSS->>MSC: SCCP_RLC + +``` + +Sequence diagram for Figure 6.g: Release after equipment failure (TRX, PCM ...) concerning a cell that is not serving the talker, group call re-establishment by the BSS not supported. The diagram shows four lifelines: MS, BSS, MSC, and BSSs. The sequence of messages is: 1. BSS sends 'Clear Request (cause = equipment failure)' to MSC. 2. MSC sends 'Clear Command' to BSS. 3. BSS sends 'Clear complete' to MSC. 4. MSC sends 'SCCP\_RLSD' to BSS. 5. BSS sends 'SCCP\_RLC' to MSC. + +NOTE: The messages CLEAR CMD, CLEAR COM, etc., are used to release the radio and terrestrial resources for the cell not serving the talker. The same message flow applies also for all other cause values. + +**Figure 6.g: Release after equipment failure (TRX, PCM ...) concerning a cell that is not serving the talker, group call re-establishment by the BSS not supported** + +The BSC shall send the message CLEAR REQUEST with cause value "equipment failure" or another appropriate cause value, if a failure concerning a cell not serving the talker was detected and the resources related to this cell shall be released (see figure 6.g). After receipt of the CLEAR REQUEST message the MSC shall send a CLEAR COMMAND message for the respective cell. + +![Sequence diagram for Figure 6.h showing uplink release for the talker on a group call channel after equipment failure.](04cfca33e3fc26513abe649d7474f733_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC + participant BSSs + BSS->>MSC: Uplink Rel Indication (cause = equipment failure) + MSC->>BSSs: Uplink rel command + BSS->>MS: Uplink free + BSS->>MSC: VGCS ASSIGNMENT STATUS + Note over BSSs: Upl_Rel_cmd is sent to all BSSs of the GC area except that BSC which sent the Upl_rel_ind. + +``` + +Sequence diagram for Figure 6.h showing uplink release for the talker on a group call channel after equipment failure. + +NOTE: The terrestrial resource for the group call channel is not released. + +**Figure 6.h: A-interface link sharing used or group call re-establishment by the BSS supported: +Uplink release for the talker on group call channel after equipment failure (TRX, PCM ...)** + +If A-interface link sharing is used or group call re-establishment by the BSS is supported, the BSC shall send the message UPLINK RELEASE INDICATION with cause value "equipment failure" or another appropriate cause value, if a failure concerning the cell that is serving the talker was detected. In addition the BSC shall send the VGCS ASSIGNMENT STATUS message indicating that the connection to this cell is no longer established (see figure 6.h). If A-interface link sharing is used, the VGCS ASSIGNMENT STATUS message shall be sent on expiry of timer Tast. + +![Sequence diagram for Figure 6.i showing release after equipment failure concerning a cell that is not serving the talker.](d8698aacaeead6dfed9a1e448670a2e4_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant MSC + participant BSSs + BSS->>MSC: VGCS ASSIGNMENT STATUS + +``` + +Sequence diagram for Figure 6.i showing release after equipment failure concerning a cell that is not serving the talker. + +NOTE: The terrestrial resource for the group call channel is not released. + +**Figure 6.i: A-interface link sharing used or group call re-establishment by the BSS supported: +Release after equipment failure (TRX, PCM ...) concerning a cell that is not serving the talker** + +If A-interface link sharing is used or group call re-establishment by the BSS is supported, and a failure concerning a cell that is not serving the talker was detected, the BSS shall send the VGCS ASSIGNMENT STATUS message indicating that the connection to this cell is no longer established (see figure 6.i). If A-interface link sharing is used, the VGCS ASSIGNMENT STATUS message shall be sent on expiry of timer Tast. + +![Sequence diagram showing the release of an A-interface link after an equipment failure. The diagram involves four lifelines: MS, BSS, MSC, and BSSs. The BSS sends a 'Clear Request (cause = equipment failure)' to the MSC. The MSC responds with a 'Clear Command' to the BSS. Finally, the BSS sends a 'Clear complete' message to the MSC.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +``` +sequenceDiagram + participant MS + participant BSS + participant MSC + participant BSSs + Note right of BSS: Clear Request +(cause = equipment failure) + BSS->>MSC: Clear Request (cause = equipment failure) + Note right of MSC: Clear Command + MSC->>BSS: Clear Command + Note right of BSS: Clear complete + BSS->>MSC: Clear complete +``` + +Sequence diagram showing the release of an A-interface link after an equipment failure. The diagram involves four lifelines: MS, BSS, MSC, and BSSs. The BSS sends a 'Clear Request (cause = equipment failure)' to the MSC. The MSC responds with a 'Clear Command' to the BSS. Finally, the BSS sends a 'Clear complete' message to the MSC. + +**Figure 6.j: A-interface link sharing used or group call re-establishment by the BSS supported: +Release after equipment failure concerning the link between MSC and BSS** + +If A-interface link sharing is used or group call re-establishment by the BSS is supported, the BSC shall send the message CLEAR REQUEST with cause value "equipment failure" or another appropriate cause value, if a failure concerning the link between MSC and BSS was detected and the resources related to this connection shall be released (see figure 6.h). After receipt of the CLEAR REQUEST message the MSC shall send a CLEAR COMMAND message for the respective connection and try to establish a new connection. + +![Sequence diagram showing the signalling required to disconnect a group call. The diagram involves seven lifelines: MS', MSs, BSS, MSC-A, GCR, FNT, and MSC-R. The process starts with a TERMINATION REQUEST from MS' to MSC-A. MSC-A responds with a Release (NOTE 31) message. MS' then sends a specific DTMF message sequence (NOTE 32) to MSC-A. MSC-A responds with a specific DTMF tone sequence (NOTE 33) to FNT, which then sends another specific DTMF tone sequence (NOTE 34) to GCR. GCR sends a TERMINATION message to BSS. BSS sends a CLEAR CMD to MSC-A. MSC-A sends a PROCESS_GROUP CALL_SIGN. (release call) (NOTE 35) message to FNT. FNT sends a Release (normal call clearing)(NOTE 35) message to GCR. GCR sends a Dispatcher release message to FNT. FNT sends a VGCS_TERMIN message to MSC-A. MSC-A sends a Release message to FNT. FNT sends a SEND_GROUP CALL_END_SIGNAL_ACK message to GCR. GCR sends a CLEAR COM message to MSC-A. MSC-A sends an SCCP_RLSD message to GCR. GCR sends an SCCP_RLC message to MSC-A. MSC-A sends a CLEAR CMD message to GCR. GCR sends a CLEAR COM message to MSC-A. MSC-A sends an SCCP_RLSD message to GCR. GCR sends an SCCP_RLC message to MSC-A. MSC-A sends a CHANNEL RELEASE message to MS'. MS' sends a CHANNEL RELEASE message to BSS.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +``` + +sequenceDiagram + participant MS_prime as MS' + participant MSs as MSs + participant BSS as BSS + participant MSC_A as MSC-A + participant GCR as GCR + participant FNT as FNT + participant MSC_R as MSC-R + + Note left of MS_prime: TERMINATION REQUEST + MS_prime->>MSC_A: TERMINATION REQUEST + MSC_A-->>FNT: Release (NOTE 31) + Note left of MS_prime: (Specific DTMF messages sequence for call termination (NOTE 32)) + MS_prime->>MSC_A: (Specific DTMF messages sequence for call termination (NOTE 32)) + MSC_A-->>FNT: (Specific DTMF tone sequence for call termination (NOTE 33)) + FNT-->>GCR: (Specific DTMF tone sequence for call termination (NOTE 34)) + GCR-->>BSS: TERMINATION + BSS-->>MSC_A: CLEAR CMD + MSC_A-->>FNT: PROCESS_GROUP CALL_SIGN. (release call) (NOTE 35) + FNT-->>GCR: Release (normal call clearing)(NOTE 35) + GCR-->>FNT: Dispatcher release + FNT-->>MSC_A: VGCS_TERMIN + MSC_A-->>FNT: Release + FNT-->>GCR: SEND_GROUP CALL_END_SIGNAL_ACK + GCR-->>MSC_A: CLEAR COM + MSC_A-->>GCR: SCCP_RLSD + GCR-->>MSC_A: SCCP_RLC + MSC_A-->>GCR: CLEAR CMD + GCR-->>MSC_A: CLEAR COM + MSC_A-->>GCR: SCCP_RLSD + GCR-->>MSC_A: SCCP_RLC + MSC_A-->>MS_prime: CHANNEL RELEASE + MS_prime-->>BSS: CHANNEL RELEASE + +``` + +Sequence diagram showing the signalling required to disconnect a group call. The diagram involves seven lifelines: MS', MSs, BSS, MSC-A, GCR, FNT, and MSC-R. The process starts with a TERMINATION REQUEST from MS' to MSC-A. MSC-A responds with a Release (NOTE 31) message. MS' then sends a specific DTMF message sequence (NOTE 32) to MSC-A. MSC-A responds with a specific DTMF tone sequence (NOTE 33) to FNT, which then sends another specific DTMF tone sequence (NOTE 34) to GCR. GCR sends a TERMINATION message to BSS. BSS sends a CLEAR CMD to MSC-A. MSC-A sends a PROCESS\_GROUP CALL\_SIGN. (release call) (NOTE 35) message to FNT. FNT sends a Release (normal call clearing)(NOTE 35) message to GCR. GCR sends a Dispatcher release message to FNT. FNT sends a VGCS\_TERMIN message to MSC-A. MSC-A sends a Release message to FNT. FNT sends a SEND\_GROUP CALL\_END\_SIGNAL\_ACK message to GCR. GCR sends a CLEAR COM message to MSC-A. MSC-A sends an SCCP\_RLSD message to GCR. GCR sends an SCCP\_RLC message to MSC-A. MSC-A sends a CLEAR CMD message to GCR. GCR sends a CLEAR COM message to MSC-A. MSC-A sends an SCCP\_RLSD message to GCR. GCR sends an SCCP\_RLC message to MSC-A. MSC-A sends a CHANNEL RELEASE message to MS'. MS' sends a CHANNEL RELEASE message to BSS. + +**Figure 7: Signalling required to disconnect the group call** + +**TERMINATION REQUEST:** An authorized mobile station can send a TERMINATION REQUEST message to clear down the entire voice group call. To do this, the mobile station must have access to the uplink. The network has to check the IMSI to verify the calling service subscriber. If the IMSI of the mobile station which has uplink access is presently not known to the network, the network shall send an identity request to the mobile station + +NOTE 31: Alternatively an authorized dispatcher can terminate the voice group call in which case a release message is received from the external network. + +NOTE 32: Alternatively an authorized mobile dispatcher can terminate the voice group call by using a specific DTMF message sequence. If the mobile dispatcher is controlled by the anchor MSC, the specific DTMF message sequence is received by the anchor MSC (see figure 7b). + +NOTE 33: If the mobile dispatcher is controlled by a relay MSC, the specific DTMF message sequence is received by the relay MSC. The relay MSC converts the DTMF messages into DTMF tones and sends them towards the anchor MSC (see figure 7c). + +NOTE 34: Alternatively an authorized fixed line dispatcher can terminate the voice group call by using a specific DTMF tone sequence. In this case, the specific DTMF tone sequence is received by the anchor MSC (see figure 7d). + +NOTE 35: Alternatively an authorized mobile station currently served by a relay MSC can clear down the entire group call in which case either a Release (normal call clearing) is received from the relay MSC (for the case when the calling service subscriber still has the initial dedicated connection to MSC-A) or a PROCESS\_GROUP\_CALL\_SIGNALLING message indicating call release is received from the relay MSC (when the calling service subscriber is on the group call channel or has a dedicated connection to the relay MSC). + +**CLEAR CMD:** This message is sent from the MSC to the BSS via each Resource Controlling SCCP connection to clear radio and terrestrial resources. + +**VGCS\_TERMIN:** The MSC informs the GCR that the voice group call with the related group call reference is terminated. + +**CHANNEL RELEASE:** CHANNEL RELEASE messages are sent on all downlink FACCH to the service subscribers. The CHANNEL RELEASE messages shall be repeated for a predefined period in order to provide a high probability that the listening mobile stations receive the message. + +- CHANNEL RELEASE message is sent using I frame for the talker. +- CHANNEL RELEASE messages are sent using UI frames for listeners. + +In addition, release messages are sent to all related dispatchers and relay MSCs. If the group call termination is initiated by an entitled dispatcher, and there is a dedicated connection for the calling service subscriber between the anchor MSC and the relay MSC, the anchor MSC shall release this connection with cause 'normal call clearing'. + +**SEND\_GROUP CALL\_END\_SIGNAL\_ACK:** The dialogues to all relay MSCs are closed. + +**CLEAR COMPLETE:** standard message. + +**SCCP\_RLSD:** standard message sent via resource controlling SCCP connection. + +**SCCP\_RLC:** standard message. + +**CLEAR CMD:** This message is sent from the MSC to the BSS via the Call Controlling SCCP connection, after all the terrestrial resources associated with the BSS for this group call have been released. + +**CLEAR COMPLETE:** standard message. + +**SCCP\_RLSD:** standard message sent via call controlling SCCP connection. + +**SCCP\_RLC:** standard message. + +![Sequence diagram showing signaling flow for VGCS call setup. Messages flow between MS, BTS, BSC, and MSC. Key steps include SYS_INFO, Channel_request, channel_required, channel_activate(SDCCH), imm_assignment_command, Imm_assignment, SABM, est_ind, UA, SCCP_CR, SCCP_CC, assignment_req, channel_activate(TCH), assignment_command, SABM, est_ind, UA, assignment_comp, and RF_channel_release.](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +**MS**                                      **BTS**                                      **BSC**                                      **MSC** + +*From the VGCS call originator* + +**For each BSC in the Group** + +Same as Standard case + +**For each cell in the Group** + +Same as Standard case + +Sequence diagram showing signaling flow for VGCS call setup. Messages flow between MS, BTS, BSC, and MSC. Key steps include SYS\_INFO, Channel\_request, channel\_required, channel\_activate(SDCCH), imm\_assignment\_command, Imm\_assignment, SABM, est\_ind, UA, SCCP\_CR, SCCP\_CC, assignment\_req, channel\_activate(TCH), assignment\_command, SABM, est\_ind, UA, assignment\_comp, and RF\_channel\_release. + +**Figure 7a: Signalling information required for establishing voice group calls +by a service subscriber using immediate setup** + +**SYS\_INFO (NCH allocated):** Message used to indicate if the NCH is allocated on the CCCH in the cell. + +**Initial RACH CHAN\_REQ:** Standard message. + +**IMM\_ASSIGNMENT:** Standard message sent on the AGCH. + +**IMMEDIATE\_SETUP:** This message including all details of the voice group call is sent by the MS to the network in order to set-up a group call immediately, i.e. without previous establishment of an MM connection. + +**UA (IMMEDIATE\_SETUP):** This message is used to acknowledge the layer 2 link and provide contention resolution of the immediate setup. + +NOTE 36: Authentication and/ or activation of Ciphering may be performed before or after sending a CONNECT message. If ciphering has not been activated before sending a CONNECT message, a CM\_SERVICE ACCEPT may be sent before the CONNECT message by the MSC, however sending of the CM\_SERVICE\_ACCEPT is not mandatory. + +![Sequence diagram for DTMF digit entry when the mobile dispatcher is controlled by the anchor MSC (MSC-A).](030c758fd425016b03290c8f11bef69d_img.jpg) + +This sequence diagram illustrates the signaling for a DTMF digit entry when the mobile dispatcher is controlled by the anchor MSC (MSC-A). The participants are MS (originator), MSC-A, and MS (dispatcher). The process begins with a bar labeled "VGCS call established, speech conversation active". The MS (dispatcher) sends a `start_DTMF (x)` message to MSC-A, which is annotated with "Dispatcher initiates DTMF signal". MSC-A responds with `start_DTMF_ack (x)`. The MS (dispatcher) then sends a `stop_DTMF` message, and MSC-A responds with `stop_DTMF_ack`. A bracket on the right side of the diagram groups the `stop_DTMF` and `stop_DTMF_ack` messages as "One digit". On the left side, a label "MSC detects the DTMF signal" points to the timeline between MSC-A and MS (originator). + +Sequence diagram for DTMF digit entry when the mobile dispatcher is controlled by the anchor MSC (MSC-A). + +**Figure 7b: Signalling required for communication of DTMF digit entry by an entitled mobile dispatcher, if the mobile dispatcher is controlled by the anchor MSC of the group call.** + +![Sequence diagram for DTMF digit entry when the mobile dispatcher is controlled by a visited MSC (VMSC).](bc9d0c0b02cbe628b1b6548cc1107734_img.jpg) + +This sequence diagram illustrates the signaling for a DTMF digit entry when the mobile dispatcher is controlled by a visited MSC (VMSC). The participants are MS (originator), MSC-A, VMSC, and MS (dispatcher). The process begins with a bar labeled "VGCS call established, speech conversation active". The MS (dispatcher) sends a `start_DTMF (x)` message to VMSC, annotated with "Dispatcher initiates DTMF signal". VMSC responds with `start_DTMF_ack (x)`. The MS (dispatcher) then sends a `stop_DTMF` message, and VMSC responds with `stop_DTMF_ack`. A bracket on the right side of the diagram groups the `stop_DTMF` and `stop_DTMF_ack` messages as "One digit". VMSC then sends a "DTMF tone" (represented by a dotted arrow) to MSC-A. A label "MSC detects the DTMF tone" points to the timeline between VMSC and MSC-A. + +Sequence diagram for DTMF digit entry when the mobile dispatcher is controlled by a visited MSC (VMSC). + +**Figure 7c: Signalling required for communication of DTMF digit entry by an entitled mobile dispatcher, if the mobile dispatcher is controlled by a visited MSC (could be a relay MSC) of the group call.** + +![Sequence diagram showing DTMF tone transmission from FNT to MSC-A via GMSC. Lifelines: MS (originator), MSC-A, GMSC, FNT. A horizontal bar indicates 'VGCS call established, speech conversation active'. Arrows show 'DTMF tone' messages from FNT to GMSC and then to MSC-A, with a detection box at MSC-A. A note on the right says 'Dispatcher initiates DTMF tone'.](32ff77da4286b58c4778033acaa10836_img.jpg) + +The diagram illustrates the signaling process for DTMF digit entry. It features four lifelines: MS (originator), MSC-A, GMSC, and FNT. A horizontal bar across the lifelines indicates the state 'VGCS call established, speech conversation active'. The sequence of events is as follows: a note on the FNT lifeline states 'Dispatcher initiates DTMF tone'; a dotted arrow labeled 'DTMF tone' points from FNT to GMSC; another dotted arrow labeled 'DTMF tone' points from GMSC to MSC-A; and a box on the MSC-A lifeline states 'MSC detects the DTMF tone'. + +Sequence diagram showing DTMF tone transmission from FNT to MSC-A via GMSC. Lifelines: MS (originator), MSC-A, GMSC, FNT. A horizontal bar indicates 'VGCS call established, speech conversation active'. Arrows show 'DTMF tone' messages from FNT to GMSC and then to MSC-A, with a detection box at MSC-A. A note on the right says 'Dispatcher initiates DTMF tone'. + +Figure 7d: Signalling required for communication of DTMF digit entry by an entitled fixed line dispatcher. + +Error: + +45 + +Error: Reference source not + +| MS | Unciphered SDCCH | MSSs | Ciphered Group Channel | | BSS | MSC | +|----|----------------------------------------------------------------|------|----------------------------------|-----------------|---------------------|-----| +| | | | | Token | Timers | | +| 1. | | | UPLINK BUSY (Token = A) | A | Start T1 | | +| | | | <----- | A | | | +| | | | | : | | | +| | | | | A | T1 Expires | | +| | | | Periodic UPLINK BUSY (Token = B) | A,B | Start T1, Start Ttv | | +| | | | ----- | A,B | Ttv Expires | | +| | Priority Uplink Request ('Emergency', GCRef, Token=B) | | | B | Stop T1 | | +| | -----> | | | ✓ | Run Tbb | | +| | | | UPLINK BUSY (Token = C) | C | Reset & Restart T1 | | +| | | | <----- | C | | | +| | | | | C | | | +| | | | | C | | | +| 2. | Priority Uplink Request ('Emergency', GCRef, Token=C) | | | C | Stop T1 | | +| | -----> | | | ✓ | Run Tbb | | +| | | | UPLINK BUSY (Token = D) | D | Reset & Restart T1 | | +| | | | <----- | D | | | +| | | | | D | | | +| | | | | D | | | +| | | | | D | | | +| 3. | Priority Uplink Request(Emergency Reset, GCRef, Token=D) | | | D | Stop T1 | | +| | -----> | | | ✓ | Run Tbb | | +| | | | UPLINK BUSY (Token = E) | E | Reset & Restart T1 | | +| | | | <----- | E | | | +| | | | | E | | | +| 4. | Priority Uplink Request ('Privilege', GCRef, Token =P ) | | | E | | | +| | -----> | | | X – discard msg | | | +| | | | | E | | | +| | | | Periodic | E | T1 Expires | | +| | | | UPLINK BUSY (Token = F) | E,F | Start T1, Start Ttv | | +| | | | <----- | E,F | Ttv Expires | | +| | | | | F | | | +| 5. | Priority Uplink Request ('Privilege', GCRef,) | | | F | | | +| | -----> | | | X – discard msg | | | +| | | | | F | | | +| | | | Periodic | F | T1 Expires | | +| | | | UPLINK BUSY (Token = G) | F,G | Start T1, Start Ttv | | +| | | | <----- | F,G | Ttv Expires | | +| | | | | G | | | +| 6. | Priority Uplink Request ('Privilege', GCRef, Token=G) | | | G | Stop T1 | | +| | -----> | | | ✓ | Run Tbb | | +| | | | UPLINK BUSY (Token = H) | H | Reset & Restart T1 | | +| | | | <----- | H | | | +| | Priority Uplink Request ('Emergency', GCRef, Token=G) | | | H | | | +| | -----> | | | X – discard msg | | | +| | Priority Uplink Request ('Emergency', GCRef, Token=H) | | | H | Stop T1 | | +| | -----> | | | ✓ | Run Tbb | | +| | | | UPLINK BUSY (ID Value = I) | I | Reset & Restart T1 | | +| | | | <----- | I | | | +| | | | | I | | | +| | | | | I | | | +| 7. | Uplink Release | | | I | | | +| | -----< | | | I | Stop T1 | | +| | | | | | | | +| | | | UPLINK FREE | | | | +| | | | <----- | | | | +| | | | | | | | +| | | | UPLINK ACCESS | | | | + +![Sequence diagram for Figure 7e. The diagram shows a 'VGCS UPLINK GRANT' message from the BSS to the MS. This is followed by a series of 'UPLINK BUSY (Token = J)' messages from the BSS to the MS. To the right of these messages, the text 'J Reset and Restart T1' appears, with vertical ellipsis below it, indicating a periodic message.](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +8. + +Sequence diagram for Figure 7e. The diagram shows a 'VGCS UPLINK GRANT' message from the BSS to the MS. This is followed by a series of 'UPLINK BUSY (Token = J)' messages from the BSS to the MS. To the right of these messages, the text 'J Reset and Restart T1' appears, with vertical ellipsis below it, indicating a periodic message. + +**Figure 7e: Validation of Priority Uplink Requests for ciphered group calls** + +###### **NOTE:** + +MS = service subscriber requesting priority access to the uplink + +MSs = all service subscribers in the group, in this BSS area + +Token (A, B...J) = 32bit random number, generated by the BSS. Broadcast in UPLINK BUSY messages on the ciphered group channel downlink (FACCH) + +###### **Figure 7e Scenarios:** + +1. For a service subscriber originated group call, if the call is ciphered, the BSS includes a token in the first UPLINK BUSY message sent on the group channel downlink. For a dispatcher originated group call, if the call is ciphered, the BSS includes a token in the first UPLINK BUSY message sent after the first successful uplink access by a service subscriber. A new token is sent in each periodic UPLINK BUSY message, every T1 seconds. If the old token has not been used it remains valid for a further Ttv seconds along with the new token. Once Ttv expires only the new token is valid. (If, within Ttv seconds, a Priority Uplink Request is received with the old token, the request is accepted, the old and new tokens are invalidated and an UPLINK BUSY, with another new token and the priority of the accepted request, is sent after Tbb ms on the group channel downlink.) +2. Subscriber on the group call with 'Privilege' or 'Emergency' subscription requests the uplink. Token matches in BSS. A new token, and the priority of the accepted request, are sent after Tbb ms in an UPLINK BUSY on the group channel downlink to ensure higher priority requests can still be made in the cells covered by this BSS. Timer T1 is reset and restarted. +3. Subscriber on the group call with 'Emergency Mode Reset' subscription requests an 'Emergency Mode Reset'. Token matches in BSS. A new token is sent after Tbb ms in an UPLINK BUSY on the group channel downlink. Timer T1 is reset and restarted. +4. User not on the group call makes fraudulent uplink request. Token does not match in BSS. BSS discards message. BSS continues to broadcast tokens in periodic UPLINK BUSY messages. +5. Subscriber on the group call with a 'Privilege', 'Emergency' or 'Emergency Mode Reset' subscription requests the uplink. No token included in the request. BSS discards message. BSS continues to broadcast tokens in periodic UPLINK BUSY messages. +6. Subscriber with a 'Privilege' subscription requests the uplink. Token matches in BSS. A new token, and the priority of the accepted request (i.e. 'Privilege'), are sent after Tbb ms in an UPLINK BUSY on the group channel downlink, however a subscriber with an 'Emergency' subscription requests the uplink before the new token has been received by the MS (use of the old token, causes the message to be discarded by BSS). On receipt of the UPLINK BUSY with new token and priority 'Privilege', the MS resends the Priority Uplink Request ('Emergency') with the new token. +7. When a subscriber releases the uplink, timer T1 is stopped and the BSS broadcasts UPLINK FREE. A token is not broadcast while the uplink is free. +8. A subscriber requests the uplink by sending an UPLINK ACCESS on the group channel uplink. The BSS grants the uplink and a UPLINK BUSY including a new token, and the current talker priority, is sent on the group channel downlink. A new token and the current talker priority is also sent in UPLINK BUSY on the + +group channel downlink if the uplink becomes busy because it is granted in another BSS or MSC area and an UPLINK\_REJECT\_CMD or UPLINK\_SEIZED\_CMD is received by the BSS. + +![Sequence diagram showing a listener in the anchor MSC area sending application-specific data to other group call members. The diagram consists of six vertical lifelines. A horizontal arrow originates from the fourth lifeline and points to the fifth lifeline, representing the transmission of data.](7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg) + +Sequence diagram showing a listener in the anchor MSC area sending application-specific data to other group call members. The diagram consists of six vertical lifelines. A horizontal arrow originates from the fourth lifeline and points to the fifth lifeline, representing the transmission of data. + +**Figure 7f: A listener in the anchor MSC area sends application-specific data to the other group call members, while the group call channel uplink in the cell is free** + +**UPLINK\_ACCESS (Establishment\_cause=UL Request for sending application-specific data):** This message is sent on the uplink of the voice group call channel using random access procedures. The UPLINK ACCESS message is similar to a channel request but sent on the group call channel uplink. + +**VGCS\_UPLINK\_GRANT:** The BSS grants the uplink of its group call channel immediately. The reply to the uplink request sent on the voice group channel downlink containing information for synchronisation of the mobile station to the network and uplink access contention resolution. The VGCS\_UPLINK\_GRANT message shall therefore include a request reference (reflecting the UPLINK\_ACCESS) and the physical information required for transmission on the voice group call channel uplink. + +**SABM (DATA\_INDICATION (Application\_data)):** The MS sends a SABM message with its mobile station identity and the Application data to the BSS. + +**UA(DATA\_INDICATION (Application\_data)):** This message is used to acknowledge the layer 2 link and provide contention resolution of the data indication. + +**NOTIFY\_APPLICATION\_DATA (Application\_data):** If the network option of immediate distribution of application-specific data by the BSS is activated, on receiving the application data sent from the MS, the BSS broadcasts the application data immediately to the cells within the BSC area in a notification message on the FACCH. Optionally, the NOTIFY\_APPLICATION\_DATA message for application-specific data is repeated on the group call channel downlink. As a prerequisite for the immediate distribution, during the establishment phase of the voice group call the BSC stored the cell identities of the cells belonging to the group call area and served by the BSC. + +**UPLINK\_APPLICATION\_DATA (CID, IDI, DATA\_INDICATION):** The BSS adds the sender's cell identifier (CID) and passes the L3 information (DATA\_INDICATION) via the UPLINK\_APPLICATION\_DATA message to the + +MSC. If the BSC has immediately distributed the application data to its BSC area, the BSC shall additionally include the Immediate Distribution Indicator (IDI). + +**UPLINK\_RELEASE:** The BSS immediately releases the uplink by sending this message to the MS on the FACCH. + +**DISC:** Standard message to release the layer 2 link. + +**UA:** Standard message to acknowledge release of the layer 2 link. The mobile station returns to group receive mode. + +**FORWARD\_GROUP\_CALL\_SIGNALLING (NOTIFICATION\_DATA):** On receipt of the **UPLINK\_APPLICATION\_DATA** message, the anchor MSC shall put the application data and optionally the mobile subscriber's MSISDN into the BSSMAP message **NOTIFICATION\_DATA** and distribute the message towards all relay MSCs. + +**Editor's note:** The condition for including the MSISDN in the BSSMAP message **NOTIFICATION\_DATA** is ffs. + +**NOTIFICATION\_DATA:** The MSC sends **NOTIFICATION\_DATA** messages with the application data to all BSSs in their MSC area involved in the group call. If the originating BSC has immediately distributed the application data to its BSC area, the MSC shall not send the **NOTIFICATION\_DATA** message to the originating BSC. + +**NOTIFY\_APPLICATION\_DATA (Application\_data):** The BSS broadcasts the application data to all listeners and the talker, if any, in a notification message on the FACCH. Optionally the **NOTIFY\_APPLICATION\_DATA** message for application-specific data is repeated on the group call channel downlink. (The broadcast of the application data by the other BSSs is not shown in figure 7f.) + +![Sequence diagram for Figure 7g showing a talker in the anchor MSC area sending application-specific data to other group call members. The diagram consists of five vertical lifelines. The first lifeline (talker) sends a message to the second lifeline (anchor MSC). The anchor MSC then sends a message to the third lifeline (relay MSC). The relay MSC then sends a message to the fourth lifeline (BSS). The BSS then sends a message to the fifth lifeline (MS).](0b452c5334567cbdc22ee9817e1246f5_img.jpg) + +Sequence diagram for Figure 7g showing a talker in the anchor MSC area sending application-specific data to other group call members. The diagram consists of five vertical lifelines. The first lifeline (talker) sends a message to the second lifeline (anchor MSC). The anchor MSC then sends a message to the third lifeline (relay MSC). The relay MSC then sends a message to the fourth lifeline (BSS). The BSS then sends a message to the fifth lifeline (MS). + +**Figure 7g: A talker in the anchor MSC area sends application-specific data to the other group call members.** + +**DATA\_INDICATION (Application\_data):** Since the talker has the uplink and a layer 2 link is established, the MS can send the application data to the BSS. + +For the meaning of the other messages see figure 7f. The option of immediate distribution of the application-specific data by the BSC can be applied also in figure 7g, although it is not shown in the message flow (for details see figure 7f). + +![Sequence diagram for Figure 7h showing a message flow between two lifelines. A horizontal arrow points from the fourth lifeline to the fifth lifeline, representing the NOTIFICATION_DATA message.](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +The diagram is a sequence diagram with six vertical lifelines. A horizontal bar with arrowheads at both ends spans across the top of all lifelines. A single horizontal arrow originates from the fourth lifeline and points to the fifth lifeline, positioned approximately halfway down the diagram. + +Sequence diagram for Figure 7h showing a message flow between two lifelines. A horizontal arrow points from the fourth lifeline to the fifth lifeline, representing the NOTIFICATION\_DATA message. + +**Figure 7h: A listener in a relay MSC area sends application-specific data to the other group call members, while the group call channel uplink in the cell is free.** + +In the following only the messages different from figure 7f are explained: + +**PROCESS\_GROUP\_CALL\_SIGNALLING (NOTIFICATION\_DATA):** On receipt of the UPLINK\_APPLICATION\_DATA message the relay MSC shall put the application data and optionally the mobile subscriber's MSISDN into the BSSMAP message NOTIFICATION\_DATA and send the message to the anchor MSC. + +*Editor's note: The condition for including the MSISDN in the BSSMAP message NOTIFICATION\_DATA is for FFS.* + +**FORWARD\_GROUP\_CALL\_SIGNALLING (NOTIFICATION\_DATA):** On receipt of the NOTIFICATION\_DATA, the anchor MSC shall forward the message to all relay MSCs except the relay MSC from which the NOTIFICATION\_DATA was received. The relay MSCs shall send the NOTIFICATION\_DATA messages with the application data to all BSSs in their MSC area involved in the group call. The BSSs shall broadcast the data to all listeners. + +For the meaning of the other messages see figure 7f. The option of immediate distribution of the application-specific data by the BSC can be applied also in figure 7h, although it is not shown in the message flow (for details see figure 7f). + +![Sequence diagram for Figure 7i showing message flows between an anchor MSC and other group call members.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +The diagram is a sequence diagram with five vertical lifelines. The first lifeline on the left is highlighted with a thick black rectangle at the top. A horizontal arrow points from the second lifeline to the first. Another horizontal arrow points from the third lifeline to the fourth. At the bottom, a wide, light-grey arrow points from left to right across all lifelines. + +Sequence diagram for Figure 7i showing message flows between an anchor MSC and other group call members. + +**Figure 7i: After receiving application-specific data, a service subscriber in the anchor MSC area sends a confirmation for the received data to the other group call members, while the group call channel uplink in the cell is free.** + +**UPLINK\_ACCESS (Establishment\_cause=UL Request for sending application-specific data):** This message is sent on the uplink of the voice group call channel using random access procedures. The UPLINK\_ACCESS message is similar to a channel request but sent on the group call channel uplink. + +**VGCS\_UPLINK\_GRANT:** The BSS grants the Uplink of its group call channel immediately. The reply to the uplink request sent on the voice group channel downlink containing information for synchronisation of the mobile station to the network and uplink access contention resolution. The VGCS\_UPLINK\_GRANT message shall therefore include a request reference (reflecting the UPLINK\_ACCESS) and the physical information required for transmission on the voice group call channel uplink. + +**SABM (DATA\_INDICATION (Application\_data)):** The MS sends a SABM message with its mobile station identity and the Application\_data to the BSS. For the purpose of identifying the received data, the data\_id which was received in the message that contained the application data that is being confirmed shall be included in the message. + +For the meaning of the other messages see figure 7f. The option of immediate distribution of the application-specific data by the BSC can be applied also in figure 7i, although it is not shown in the message flow (for details see figure 7f). + +![Diagram illustrating a listener in the anchor MSC area sending application-specific data via RACH to other group call members while the talker is using the group call channel uplink in the same cell.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +The diagram (partially obscured in the source image) illustrates a signaling flow between a Mobile Station (MS) and the Base Station Subsystem (BSS). It shows a listener in the anchor MSC area sending application-specific data via RACH. The sequence involves a CHANNEL\_REQUEST from the MS to the BSS, followed by an Immediate Assignment (IMM\_ASS), a Set Asynchronous Balanced Mode (SABM) containing application data, and an Unnumbered Acknowledgement (UA). The BSS then distributes this data via a NOTIFY\_APPLICATION\_DATA message. + +Diagram illustrating a listener in the anchor MSC area sending application-specific data via RACH to other group call members while the talker is using the group call channel uplink in the same cell. + +**Figure 7j: A listener in the anchor MSC area sends application-specific data that are not time-critical via RACH to the other group call members, while the talker is using the group call channel uplink in the same cell.** + +**RACH (CHAN\_REQ):** The network supports uplink access option (i) as defined in subclause 7.2, and the talker is on the group call channel in the same cell as the mobile station of the listener; therefore, the "uplink access indication for data" in the uplink busy message instructs the mobile station to use the RACH when application-specific data is to be sent. + +The mobile station leaves the group receive mode and sends the CHANNEL\_REQUEST message with an appropriate establishment cause via the RACH to request an SDCCH. + +**IMM\_ASS:** Standard message sent on the AGCH. + +**SABM (DATA\_INDICATION\_2 (Application\_data)):** The MS sends a SABM message with its mobile station identity and the Application\_data to the BSS on SDCCH. The network determines from the group call reference included in the message which group call is addressed by this message. + +**UA (DATA\_INDICATION\_2 (Application\_data)):** This message is used to acknowledge the layer 2 link and provide contention resolution of the data indication 2. + +NOTE 1: Optionally, on receipt of the UA (DATA\_INDICATION\_2 (Application\_data)) the mobile station performs a local release of the layer 2 link, i.e. without exchange of DISC/UA, and returns to group receive mode. + +**NOTIFY\_APPLICATION\_DATA (Application\_data):** If the network option of immediate distribution of application-specific data by the BSC is activated, on receiving the application data sent from the MS, the BSS broadcasts the application data immediately to the cells within the BSC area in a notification message on the FACCH. Optionally, the NOTIFY\_APPLICATION\_DATA message for application-specific data is repeated on the group call + +channel downlink. As a prerequisite for the immediate distribution, during the establishment phase of the voice group call the BSC stored the cell identities of the cells belonging to the group call area and served by the BSC. + +**UPLINK\_APPLICATION\_DATA (CID, IDI, DATA\_INDICATION\_2):** The BSS adds the sender's cell identifier (CID) and passes the L3 information (DATA\_INDICATION\_2) via the UPLINK\_APPLICATION\_DATA message to the MSC. If the BSC has immediately distributed the application data to its BSC area, the BSC shall additionally include the Immediate Distribution Indicator (IDI). + +**CHANNEL\_RELEASE:** The BSS immediately releases the uplink by sending this message to the MS on the SDCCH including the channel description of the voice group call channel to which the mobile station shall tune to. The mobile station returns to group receive mode. + +NOTE 2: If the mobile station performed a local release of the layer 2 link, the following two messages will not be exchanged. Instead T3109 in the BSS will expire and the BSS will release the channel. + +**DISC:** Standard message to release the layer 2 link. + +**UA:** Standard message to acknowledge release of the layer 2 link. The mobile station returns to group receive mode. + +**NOTIFICATION\_DATA:** The MSC sends NOTIFICATION\_DATA messages with the application data to all BSSs in their MSC area involved in the group call. If the originating BSC has immediately distributed the application data to its BSC area, the MSC shall not send the NOTIFICATION\_DATA message to the originating BSC. + +**NOTIFY\_APPLICATION\_DATA (Application\_data):** The BSS broadcasts the application data to all listeners and the talker, if any, in a notification message on the FACCH. Optionally the NOTIFY\_APPLICATION\_DATA message for application-specific data is repeated on the group call channel downlink. (The broadcast of the application data by the other BSSs is not shown in figure 7j.) + +For the meaning of the other messages see figure 7f. + +### 11.3.9 Short Message Service (SMS) + +#### 11.3.9.1 Delivering SMS to the voice group call + +If the talking service subscriber, the listening service subscriber, the dispatcher in a voice group call, or any initiator of short messages who is not part of the voice group call wants to send a short message to the voice group call, it shall use the numbering scheme based on ITU-T Recommendation E.164 as the destination address illustrated below. + +| CC | NDC | Prefix | Group call reference | +|----|-----|--------|----------------------| +|----|-----|--------|----------------------| + +The Country Code (CC) and National Destination Code (NDC) are used as normal for routing purposes. The CC and NDC may be omitted for internal SMS. The Subscriber Number (SN) is used to indicate: + +- the request of an SMS to a voice group call by use of a prefix. The length of the prefix shall be 1 to 2 digits. The value of the prefix shall be the same as the value used by a dispatcher when originating the voice group call (see subclause 9.2 d); +- the wanted group call reference as defined in subclause 9.1. + +When receiving the short message, the SC may send Delivery Report message containing the received group call reference of the voice group to the sender of the short message, and furthermore the SC shall attempt to deliver the short message to the voice group call addressed by the group call reference. Figure 7k shows the MT SMS delivery procedure. + +![Sequence diagram showing a successful MT short message transfer attempt to a voice group call. The diagram involves six lifelines: SC, SMS-GMSC, A-MSC, GCR, R-MSC, and MS. The sequence of messages is: 1. Message Transfer (SC to SMS-GMSC), 2. MT_ForwardSM_For_VGCS_REQ (SMS-GMSC to A-MSC), 3. GCR_SMS_Interrogation (A-MSC to GCR), 4. GCR_SMS_Interrogation_Res (GCR to A-MSC), 5. MT_ForwardSM_For_VGCS_Res (A-MSC to SMS-GMSC), 6. FORWARD_GROUP_CALL_SIGNALLING (A-MSC to R-MSC), 7. Message Transfer (A-MSC to MS), and 8. Message Transfer (R-MSC to MS).](0a73b03fba21af142d619a9a662e6490_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-GMSC + participant A-MSC + participant GCR + participant R-MSC + participant MS + + Note right of SC: Error: Reference source not + SC->>SMS-GMSC: 1. Message Transfer + SMS-GMSC->>A-MSC: 2. MT_ForwardSM_For_VGCS_REQ + A-MSC->>GCR: 3. GCR_SMS_Interrogation + GCR->>A-MSC: 4. GCR_SMS_Interrogation_Res + A-MSC->>SMS-GMSC: 5. MT_ForwardSM_For_VGCS_Res + A-MSC->>R-MSC: 6. FORWARD_GROUP_CALL_SIGNALLING + A-MSC->>MS: 7. Message Transfer + R-MSC->>MS: 8. Message Transfer + +``` + +Sequence diagram showing a successful MT short message transfer attempt to a voice group call. The diagram involves six lifelines: SC, SMS-GMSC, A-MSC, GCR, R-MSC, and MS. The sequence of messages is: 1. Message Transfer (SC to SMS-GMSC), 2. MT\_ForwardSM\_For\_VGCS\_REQ (SMS-GMSC to A-MSC), 3. GCR\_SMS\_Interrogation (A-MSC to GCR), 4. GCR\_SMS\_Interrogation\_Res (GCR to A-MSC), 5. MT\_ForwardSM\_For\_VGCS\_Res (A-MSC to SMS-GMSC), 6. FORWARD\_GROUP\_CALL\_SIGNALLING (A-MSC to R-MSC), 7. Message Transfer (A-MSC to MS), and 8. Message Transfer (R-MSC to MS). + +**Figure 7k: Successful MT short message transfer attempt to a voice group call** + +- 1) The SC sends a Message Transfer message to forward a short message to the SMS-GMSC. +- 2) The SMS-GMSC sends the MT\_ForwardSM\_For\_VGCS\_REQ message to transfer the received short message to the anchor MSC using the routing information derived from the group call reference. +- 3) The anchor MSC sends the GCR\_SMS\_Interrogation message to the GCR to retrieve the voice group call attributes for short message transfer. +- 4) The GCR sends the GCR\_SMS\_Interrogation\_Res message to the anchor MSC containing the voice group call status and optionally the list of identities of dispatchers. +In RANflex configuration with Group Call redundancy message 4 may indicate that the group call is ongoing at another anchor MSC within the redundancy pool. If so, message 2 is relayed to that anchor MSC (not shown in figure 7k). +- 5) The anchor MSC sends the MT\_ForwardSM\_For\_VGCS\_RES message to the SMS-GMSC containing the status of the voice group call and optionally a list of identities of dispatchers if received from the GCR. Optionally, if the voice group call is currently ongoing, the SMS-GMSC may initiate point to point short message transfer attempts to the dispatchers of the voice group call. + +- 6) If the voice group call is established, the anchor MSC sends the FORWARD\_GROUP CALL\_SIGNALLING message to deliver the short message to all related relay MSCs in the voice group call. +- 7) If the voice group call is established, the anchor MSC sends Message Transfer message to deliver the short message to the MSs participating in the voice group call within its MSC area. +- 8) If the voice group call is established, the relay MSCs sends Message Transfer message to deliver the short message to the MSs participating in the voice group call within its MSC area. + +#### 11.3.9.2 Point-to-point short message during an ongoing voice group call + +In this subclause the term point-to-point short message is used for mobile terminating short messages destined to a single subscriber and for mobile originating short messages, regardless whether their final destination is a single subscriber or a voice group call. + +For the transmission and reception of point-to-point short messages via CS domain during an ongoing voice group call, an MS and a network supporting this functionality shall apply the procedures specified in 3GPP TS 23.040 [14] and 3GPP TS 24.011 [15] as follows: + +- a) When the talking service subscriber is on a dedicated channel, point-to-point short messages to be sent or received via the CS domain shall be transmitted on the SACCH of the dedicated channel. If the talking service subscriber requests to release the uplink while a short message transfer is ongoing, the MS shall initiate the release of the uplink and abort the transfer of the short message. +- b) When the talking service subscriber is on a voice group call channel, the MS shall send mobile originating short messages via the CS domain on the SACCH of the voice group call channel, if at least one of the following conditions is fulfilled: + - the short message is destined to the ongoing voice group call of the talker; + - the network broadcasts neither an SMS data confidentiality indication nor an SMS guaranteed privacy indication on the NCH; or + - the network broadcasts an SMS data confidentiality indication, but no SMS guaranteed privacy indication on the NCH, and the voice group call channel is ciphered. + +Otherwise the MS shall leave the voice group call, send the short message as specified in 3GPP TS 24.011 [15] and return to the group call in group receive mode afterwards, if possible. + +If the talking service subscriber requests to release the uplink while a short message transfer on the voice group call channel is ongoing, the MS shall initiate the release of the uplink and abort the transfer of the short message. + +- c) When the talking service subscriber is on a voice group call channel, the network may deliver mobile terminating point-to-point short messages via the CS domain on the SACCH of the voice group call channel, if at least one of the following conditions is fulfilled: + - the network does not broadcast an SMS data confidentiality indication on the NCH; or + - the network broadcasts an SMS data confidentiality indication on the NCH, and the voice group call channel is ciphered. + +Otherwise the network shall perform paging into the ongoing voice group call as described in subclause 11.3.1.3 c. The paging information on the FACCH of the voice group call channel shall indicate explicitly that the paging is for a short message. When the paging is received in group transmit mode, the reception of the paging shall be indicated to the subscriber. It is then up to the subscriber to respond to the paging or not. On request of the subscriber to respond to the paging, the MS in group transmit mode shall release the uplink, leave the voice group call, receive the short message as specified in 3GPP TS 24.011 [15], and return to the group call in group receive mode afterwards, if possible. + +If the talking service subscriber requests to release the uplink while a short message transfer on the voice group call channel is ongoing, the MS shall initiate the release of the uplink and abort the transfer of the short message. + +- d) If an MS on a voice group call channel is not the endpoint of the layer 2 link for acknowledged message transfer, it shall ignore point-to-point short messages received on the SACCH of the voice group call channel. +- e) On request of a listening service subscriber to send a point-to-point short message, the MS in group receive mode shall leave the voice group call, send the short message as specified in 3GPP TS 24.011 [15], and return to the group call in group receive mode afterwards, if possible. + +For the delivery of a point-to-point short message to a listening service subscriber, the network shall perform paging into ongoing voice group calls by means of the notification procedure as described in subclause 11.3.1.3. The notification messages on the FACCH of the voice group call channel shall indicate explicitly that the paging is for a short message. When the paging is received in group receive mode, the reception of the paging shall be indicated to the subscriber. It is then up to the subscriber to respond to the paging or not. On request of the subscriber to respond to the paging, the MS in group receive mode shall leave the voice group call, receive the short message as specified in 3GPP TS 24.011 [15], and return to the group call in group receive mode afterwards, if possible. + +For the transmission and reception of point-to-point short messages via PS domain during an ongoing voice group call, class A mobile stations supporting this functionality shall apply the procedures specified in 3GPP TS 23.040 [14] and 3GPP TS 24.011 [15]. + +**Editor's note:** For DTM mobile stations the transmission and reception of point-to-point short messages via PS domain during an ongoing voice group call is ffs. + +## 11.4 Functional requirement of Anchor MSC + +The VGCS handling process in the anchor MSC is shown in figure 8. + +### Successful call set-up + +When the VGCS handling process in the anchor MSC receives a VGCS call set-up request from either a dispatcher or a service subscriber currently located in the anchor MSC's area or a service subscriber currently located in a relay MSC's area, or - in a RANflex configuration or in a RANflex configuration with group call redundancy - from a service subscriber currently registered in a VMSC, it interrogates its associated GCR to retrieve the group call attributes, and waits for a response. + +If the GCR returns a positive response containing the group call attributes, the anchor MSC + +sets up the downlinks to the cells inside the MSC area of the group call anchor MSC into which the call is to be sent.; If the "talker channel parameter" is used, the anchor MSC shall additionally send the parameter to the affected BSCs; + +sets up the connections to the dispatchers to which a dedicated link is to be established; + +sets up the connections to the relay MSCs or relay MSC redundancy pools into which the call is to be sent; + +starts the No Activity Timer; + +sends Forward Group Call Signalling messages to all selected relay MSCs if the call was not initiated by a dispatcher (however in a non-RANflex configuration not to the relay MSC from which the IMSI was received within the Send Group Call End Signal message if the call was initiated by a service subscriber located in the relay MSC area). The Forward Group Call Signalling messages shall contain the IMSI, talker priority and additional information of the service subscriber who has initiated the call. In a RANflex configuration and in a RANflex configuration with group call redundancy, simultaneous group call setup of two service subscribers may result in two Send Group Call End Signal messages being received by the anchor MSC from two different relay MSCs, with both messages containing an IMSI. In this situation the anchor MSC shall discard the IMSI received from the relay MSC whose MSC address does not match the generic number with the number qualifier indicator set to "additional calling party number" from the IAM received and accepted from the originating MSC. + +**NOTE:** In a network configuration involving also pre-Rel-7 relay MSCs, the IAM sent by such a relay MSC as originating MSC will not include a generic number parameter. If the anchor MSC accepts the IAM from the pre-Rel-7 relay MSC and receives further IAM(s) including a generic number with number qualifier indicator set to "additional calling party number", the anchor MSC can store these additional calling party numbers in a list and discard the IMSI received with a Send Group Call End Signal message from a relay MSC whose MSC address matches any of the numbers in the list. + +If the network supports talker priorities, the anchor MSC includes the talker priority of the service subscriber who has initiated the call in the Forward Group Call Signalling messages; and + +waits for uplink management messages. + +### Procedure Set-up Connections to Relay MSCs and BSCs + +The procedure is shown in figure 9. + +The procedure + +- sets up the downlinks to the cells inside the MSC area of the group call anchor MSC into which the call is to be sent. If the network supports talker priorities, the anchor MSC additionally sends the talker priority of the service subscriber who has initiated the call and, if applicable, the "emergency mode indication" with Uplink Seized Command messages" to the affected BSCs; +- sends PREPARE\_GROUP\_CALL messages to all relay MSCs (in a RANflex configuration with group call redundancy: to all group call relay MSC redundancy pools) and waits for the responses. If the "talker channel parameter" is used, the anchor MSC shall include this parameter in the PREPARE\_GROUP\_CALL messages. + +If a positive response containing a Group Call number is received from a relay MSC, the anchor MSC constructs an IAM using the Group Call number as called party address, sends it to the relay MSC and waits for the SEND\_GROUP\_CALL\_END\_SIGNAL message. + +If a SEND\_GROUP\_CALL\_END\_SIGNAL message without IMSI is received from a relay MSC, this indicates to the anchor MSC that at least one downlink to a cell has been successfully connected in the relay MSC area. + +If the call was originated by a service subscriber in a relay MSC area and a SEND\_GROUP\_CALL\_END\_SIGNAL message with the IMSI of the originator is received from this relay MSC, this indicates to the anchor MSC that the downlink to the originating cell has been successfully connected. If the negative response on the PREPARE\_GROUP\_CALL message is received from originating relay MSC, the call shall be released. + +Relay MSCs (in a RANflex configuration with group call redundancy: relay MSC redundancy pools) that do not send positive responses to the PREPARE\_GROUP\_CALL message are no longer considered to belong to the list of relay MSCs (or relay MSC redundancy pools) for this VGCS call. + +If, after receipt of a positive response containing a Group Call number from a relay MSC, the anchor MSC receives an ABORT from the relay MSC, the relay MSC or relay MSC redundancy pool will no longer be considered to belong to the list of relay MSCs or relay MSC redundancy pools for this VGCS call. + +Optionally in both cases the anchor MSC may retry to establish the connection to the relay MSC or relay MSC redundancy pool, instead of no longer considering the relay MSC or relay MSC redundancy pool to belong to the list of relay MSCs or relay MSC redundancy pools. + +If an ABORT message is received from the relay MSC or relay MSC redundancy pool the anchor MSC releases the connection, established with the Group Call number, to the relay MSC or relay MSC redundancy pool and the relay MSC or relay MSC redundancy pool is no longer considered to belong to the list of relay MSCs or relay MSC redundancy pools for this VGCS call. + +If a Release message for the connection established with the Group Call number is received from a relay MSC or relay MSC redundancy pool, then the anchor MSC sends an ABORT message to that relay MSC or relay MSC redundancy pool and the relay MSC or relay MSC redundancy pool is no longer considered to belong to the list of relay MSCs or relay MSC redundancy pools for this VGCS call. + +### Unsuccessful call set-up + +If the call set-up is unsuccessful (i.e. conditions for call establishment have not been met as per subclause 11.3.1.1.2) the anchor MSC sends a SEND\_GROUP\_CALL\_END\_SIGNAL\_ACK message or ABORT (depending on the state of the MAP dialogue) to all relay MSCs, releases the connections to the relay MSCs, releases all connections to dispatchers, all downlinks to cells inside the anchor MSC area are released, the GCR is informed that the call is no longer on-going and the process returns to the idle state. + +### Negative response received from the GCR + +If the GCR returns a negative response to the anchor MSC indicating that the call is already on-going locally i.e. at the associated MSC, the anchor MSC checks whether the new call was initiated by a dispatcher. If so, the dispatcher is connected to the on-going call and the process returns to the idle state. If the new call was initiated by a service subscriber, a Release message indicating "user busy" is returned in order to force the mobile station of the service subscriber to look for notifications of the respective group ID on the NCH and join the group call. + +If (in a RANflex configuration with group call redundancy) the GCR returns a negative response to the selected anchor MSC indicating that the call is already on-going at another MSC within the group call anchor MSC redundancy pool, the selected anchor MSC checks whether the new call was initiated by a dispatcher or a service subscriber served by another VMSC. If so, the selected anchor MSC forwards the call setup request to the anchor MSC where the group call is ongoing (possibly using a special prefix for the called party number). The selected anchor MSC then acts as a transit node unless it recognizes that the anchor MSC where the group call is ongoing is out of service. In the latter case the selected anchor MSC repeats the GCR interrogation including "ongoing call override indication". If the call was initiated by a service subscriber served by the selected anchor MSC, the selected anchor MSC interrogates the anchor MSC where the group call is ongoing by means of the MAP service SEND\_GROUP\_CALL\_INFO and waits for a response. If the selected anchor MSC recognizes that the anchor MSC where the group call is ongoing is out of service or if that anchor MSC responds with a positive SEND\_GROUP\_CALL\_INFO response (i.e. the GCRs are out of synch and the group call at the other anchor MSC is not ongoing), then the selected anchor MSC repeats the GCR interrogation including "ongoing call override indication". If the anchor MSC where the group call is ongoing responds with a negative SEND\_GROUP\_CALL\_INFO response (ongoing call), then the selected anchor MSC returns a Release message indicating "user busy" in order to force the mobile station of the service subscriber to look for notifications of the respective group ID on the NCH and join the group call. + +If the negative response from the GCR indicates any other reason than "on-going call" the VGCS call set-up request is rejected by sending a release message back to the initiator and the process returns to the idle state. + +### Uplink management + +If an anchor MSC not supporting talker priorities receives an Uplink Release Indication message from a BSC, the anchor MSC marks the uplink as free, sends Forward Group Call Signalling messages indicating "uplink release indication" to all relay MSCs, sends Uplink Release command messages to all other BSCs, restarts the No Activity Timer and waits for further uplink management messages. + +If an anchor MSC supporting talker priorities receives an Uplink Release Indication message from a BSC, the anchor MSC compares the talker priority included in the Uplink Release Indication with the stored talker priority. If they are equal, the anchor MSC proceeds as specified above for the anchor MSC not supporting talker priorities; otherwise the anchor MSC discards the Uplink Release Indication. + +If the anchor MSC receives an Uplink Request message without talker priority or with talker priority "normal subscriber" from a BSC, it checks whether the uplink is marked as free. If so, an Uplink Request Acknowledge message is returned to the BSC, Forward Group Call Signalling messages indicating that the uplink is no longer free are sent to all relay MSCs, Uplink Seized Command messages are sent to all other BSCs, the uplink is marked busy and the process waits for further uplink management messages. If the uplink was not free when receiving the Uplink Request message, the request is rejected. + +If an anchor MSC supporting talker priorities receives an Uplink Request message with a talker priority higher than "normal subscriber" from a BSC, and the uplink is free or it was seized by the current talker with a lower talker priority, the anchor MSC checks whether the subscriber has the subscription for the requested talker priority for this group ID. In a RANflex configuration (with or without group call redundancy) this check may require retrieval of information from the visited MSC/VLR by means of the MAP service SEND\_GROUP\_CALL\_INFO. If so, the anchor MSC: + +- stores the received data; +- sends Forward Group Call Signalling messages indicating "uplink seized command" with the requested talker priority to the relay MSCs; +- returns an Uplink Request Acknowledge message with the requested talker priority to the BSC which has requested the uplink; +- sends Uplink Seized Command messages with the requested talker priority to all other BSCs; +- releases the current talker by sending a Clear Command message, if the talker is on a dedicated channel and is located in the anchor MSC; + +- marks the uplink busy; and +- waits for further uplink management messages. + +Additionally, + +- if the requested talker priority is "emergency subscriber", the anchor MSC sets the emergency mode and includes the "emergency mode indication" in the Uplink Request Acknowledge message and the Uplink Seized Command messages; furthermore the anchor MSC alerts all active dispatchers with an appropriate emergency indication (e.g. in-band tone or announcement); furthermore the anchor MSC alerts all inactive dispatchers by setting up dedicated connections with an appropriate emergency indication (e.g. special CLI prefix or postfix, and in-band tone or announcement) and connects the dispatchers to the voice group call. +- if the anchor MSC supports the transmission of additional subscriber-related information, it interrogates the VLR to get the "additional information" assigned to the new talker. In a RANflex configuration (with or without group call redundancy) this may require retrieval of information from the visited MSC/VLR by means of the MAP service SEND\_GROUP\_CALL\_INFO. If "additional information" is available, the anchor MSC includes the "additional information" in the Forward Group Call Signalling messages indicating "uplink seized command" to all relay MSCs and sends VGCS Additional Info messages to all BSCs involved in the call and connected to the anchor MSC. Furthermore, the anchor MSC sends a VGCS Additional Info message on the dedicated connection to the BSC serving the current talker, before it releases the current talker. + +If an anchor MSC supporting talker priorities receives an Uplink Request message with a talker priority higher than "normal subscriber" from a BSC, and the uplink was seized by the current talker with the same or a higher talker priority, then the anchor MSC sends an Uplink Reject Command message with the current talker priority to the BSC. + +If the anchor MSC receives an Uplink Request Confirm message from a BSC, it stores the received data and waits for further uplink management messages. Additionally, if the anchor MSC supports the transmission of additional subscriber-related information, it interrogates the VLR to get the "additional information" assigned to the subscriber. In a RANflex configuration (with or without group call redundancy) this interrogation may require retrieval of information from the visited MSC/VLR by means of the MAP service SEND\_GROUP\_CALL\_INFO. If "additional information" is available, the relay MSC sends VGCS Additional Info messages to all BSCs involved in the call and connected to this relay MSC, and Forward Group Call Signalling messages with the additional info to all relay MSCs. + +If an anchor MSC supporting talker priorities receives an Emergency Reset Indication from a BSC and the subscription check is successful, the anchor MSC resets the emergency mode, sends Emergency Reset Command messages to all BSCs involved in the call and connected to the anchor MSC, and Forward Group Call Signalling messages indicating "emergency reset command" to all relay MSCs. If the talker priority at receipt of the Emergency Reset Indication is "emergency subscriber", then it is changed in the anchor MSC to "normal subscriber"; furthermore the anchor MSC alerts all active dispatchers with an appropriate emergency indication (e.g. in-band tone or announcement); furthermore the anchor MSC alerts all inactive dispatchers by setting up dedicated connections with an appropriate emergency indication (e.g. special CLI prefix or postfix, and in-band tone or announcement) and connects the dispatchers to the voice group call. + +If an anchor MSC not supporting talker priorities receives a Process Group Call Signalling message indicating "uplink release indication" from a relay MSC, the anchor MSC marks the uplink as free, sends Forward Group Call Signalling messages indicating "uplink release indication" to all other relay MSCs, sends Uplink Release command messages to all BSCs, restarts the No Activity Timer and waits for further uplink management messages. If there is a dedicated connection for the talking service subscriber between the relay MSC and the anchor MSC, the anchor MSC shall release this connection with cause 'normal, unspecified'. + +If an anchor MSC supporting talker priorities receives a Process Group Call Signalling message indicating "uplink release indication" from a relay MSC, the anchor MSC compares the talker priority included in the Process Group Call Signalling message with the stored talker priority. If they are equal, the anchor MSC proceeds as specified above for the anchor MSC not supporting talker priorities; otherwise the anchor MSC discards the Process Group Call Signalling message. + +If the anchor MSC receives a Process Group Call Signalling message from a relay MSC indicating "uplink request" without talker priority or with talker priority "normal subscriber", it checks whether the uplink is marked as free. If so, a Forward Group Call Signalling message indicating "uplink request acknowledgement" is returned to the relay MSC, Forward Group Call Signalling messages indicating that the uplink is no longer free are sent to all other relay MSCs, Uplink Seized Command messages are sent to all BSCs, the uplink is marked busy and the process waits for further uplink management messages. If the uplink was not free when receiving the Process Group Call Signalling message (Uplink Request), the request is rejected. + +If an anchor MSC supporting talker priorities receives a Process Group Call Signalling message from a relay MSC indicating "uplink request" with a talker priority higher than "normal subscriber", and the uplink is free or it was seized by the current talker with a lower talker priority, then the anchor MSC: + +- returns a Forward Group Call Signalling message indicating "uplink request acknowledgement" with the requested talker priority to the relay MSC; +- sends Forward Group Call Signalling messages indicating "uplink seized command" and the requested talker priority to all other relay MSCs; +- sends Uplink Seized Command messages with the requested talker priority to all BSSs involved in the call; +- releases the current talker by sending a Clear Command message, if the talker is on a dedicated channel and is located in the anchor MSC; +- marks the uplink as busy; and +- waits for further uplink management messages. + +Additionally, + +- if the requested talker priority in the Process Group Call Signalling message from the relay MSC is "emergency subscriber", the anchor MSC sets the emergency mode and includes the "emergency mode indication" in the Uplink Seized Command messages; furthermore the anchor MSC alerts all active dispatchers with an appropriate emergency indication (e.g. in-band tone or announcement); furthermore the anchor MSC alerts all inactive dispatchers by setting up dedicated connections with an appropriate emergency indication (e.g. special CLI prefix or postfix, and in-band tone or announcement) and connects the dispatchers to the voice group call. +- if "additional information" about the new talker was included in the Process Group Call Signalling message from the relay MSC, the anchor MSC includes the "additional information" in the Forward Group Call Signalling messages indicating "uplink seized command" to all other relay MSCs and sends VGCS Additional Info messages to all BSCs involved in the call and connected to the anchor MSC. Furthermore, the anchor MSC sends a VGCS Additional Info message on the dedicated connection to the BSC serving the current talker, before it releases the current talker. + +If an anchor MSC supporting talker priorities receives a Process Group Call Signalling message from a relay MSC indicating "uplink request" with a talker priority higher than "normal subscriber", and the uplink was seized by the current talker with the same or a higher talker priority, then the anchor MSC returns a Forward Group Call Signalling message indicating "uplink reject command" with the current talker priority to the relay MSC. + +If the anchor MSC receives a Process Group Call Signalling message with "additional info" from a relay MSC, the anchor MSC sends VGCS Additional Info messages to all BSCs involved in the group call and connected to the anchor MSC, and Forward Group Call Signalling messages with "additional info" to all other relay MSCs. + +If an anchor MSC supporting talker priorities receives a Process Group Call Signalling message with "emergency mode reset command" from a relay MSC, the anchor MSC resets the emergency mode, sends Forward Group Call Signalling messages with "emergency mode reset command" to all other relay MSCs, and sends Emergency Reset Command messages to all BSCs involved in the call and connected to the anchor MSC. If the talker priority at receipt of the "emergency mode reset command" is "emergency subscriber", then it is changed in the anchor MSC to "normal subscriber"; furthermore the anchor MSC alerts all active dispatchers with an appropriate emergency indication (e.g. in-band tone or announcement); furthermore the anchor MSC alerts all inactive dispatchers by setting up dedicated connections with an appropriate emergency indication (e.g. special CLI prefix or postfix, and in-band tone or announcement) and connects the dispatchers to the voice group call. + +If the anchor MSC receives an ABORT message from a relay MSC, the connection to the relay MSC is released and the relay MSC is no longer considered to be part of the call. + +### Call release + +If the anchor MSC receives the specific DTMF message sequence or the specific DTMF tone sequence for call termination from an entitled dispatcher (see figures 7b to 7d) or a Termination Request message from the initiating service subscriber who currently has access to the uplink, it sends Send Group Call End Signal ACK messages to all relay MSCs, sends Release messages to all relay MSCs, sends Release messages to all dispatchers and BSCs, informs the GCR that the call is no longer on-going and the process returns to the idle state. If the group call termination is + +initiated by an entitled dispatcher, and there is a dedicated connection for the talking service subscriber between the anchor MSC and the relay MSC, the anchor MSC shall release this connection with cause 'normal call clearing'. + +If the anchor MSC receives a Process Group Call Signalling message from a relay MSC indicating "release group call" or an ISUP Release message from a relay MSC indicating "Normal call clearing" for the calling service subscriber's dedicated connection to the anchor MSC, then the anchor MSC sends Send Group Call End Signal ACK messages to all relay MSCs, sends Release messages to all relay MSCs, sends Release messages to all dispatchers and BSCs, informs the GCR that the call is no longer on-going and the process returns to the idle state. + +If the anchor MSC receives an ISUP Release message from a relay MSC with cause value other than "Normal call clearing" for the calling service subscribers dedicated connection to the anchor MSC, then the anchor MSC shall send Uplink Release Command messages to all BSCs and Forward Group Call Signalling messages with Uplink Release Indication parameter to all relay MSCs. + +If the no activity time in the anchor MSC expires, i.e. "no activity" (as specified in subclause 8.1.2.3) has been detected for the time specified in the GCR, the anchor MSC sends Send Group Call End Signal ACK messages to all relay MSCs, sends Release messages to all relay MSCs, sends Release messages to all dispatchers and BSCs, informs the GCR that the call is no longer on-going and the process returns to the idle state. + +### **SM MT delivery** + +When the VGCS handling process in the anchor MSC receives an MT\_ForwardSM\_for\_VGCS\_REQ message from a SMS-GMSC, the anchor MSC shall interrogate the GCR to retrieve the group call attributes for short message transfer. The anchor MSC shall deliver to the SMS-GMSC the status of the voice group call and optionally a list of identities of dispatchers within the MT\_ForwardSM\_for\_VGCS\_RES message. + +If the voice group call is established, the anchor MSC shall distribute the short message TPDU to all connected relay MSCs using the FORWARD\_GROUP CALL\_SIGNALLING message and shall deliver the short message to the relevant cells using the already established downlink channel for the voice group call. + +If the voice group call is not established, the anchor MSC shall discard the short message TPDU. + +![A flowchart diagram representing the VGCS handling process in the anchor MSC. The diagram is partially obscured by a large black rectangle. The visible portion shows three vertical flow paths. The left path starts with a decision diamond, followed by a process block (rectangle with a right-pointing arrow), and then a data store (cylinder). A loop back from the data store to the process block is shown. The middle path consists of two process blocks (rectangles with right-pointing arrows) and a data store (cylinder) below them. The right path shows a single data store (cylinder). All shapes are light orange with black outlines.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +A flowchart diagram representing the VGCS handling process in the anchor MSC. The diagram is partially obscured by a large black rectangle. The visible portion shows three vertical flow paths. The left path starts with a decision diamond, followed by a process block (rectangle with a right-pointing arrow), and then a data store (cylinder). A loop back from the data store to the process block is shown. The middle path consists of two process blocks (rectangles with right-pointing arrows) and a data store (cylinder) below them. The right path shows a single data store (cylinder). All shapes are light orange with black outlines. + +Figure 8: The VGCS handling process in the anchor MSC (sheet 1 of 7) + +![A diagram showing a black header bar at the top, a small document icon in the top-left corner, and a hexagon in the lower-right area.](fd3cbb53e991f8209ba17b398f426e13_img.jpg) + +The diagram consists of a solid black horizontal bar at the top. Below this bar, in the top-left corner, is a small icon representing a document or a piece of paper with a folded corner. In the lower-right quadrant of the diagram area, there is a simple hexagonal outline. + +A diagram showing a black header bar at the top, a small document icon in the top-left corner, and a hexagon in the lower-right area. + +Figure 8: The VGCS handling process in the anchor MSC (sheet 2 of 7) + +![A process flow diagram for VGCS handling in the anchor MSC, sheet 3 of 7. Most of the top half is obscured by a black rectangle. Visible elements include a white arrow pointing right within the black area, a dashed line leading from the bottom of the black area to a rounded rectangle, and a solid line with an arrow pointing from the black area to the same rounded rectangle.](575d7d345b3ec04393bb2ec720ebabca_img.jpg) + +The diagram illustrates the VGCS handling process in the anchor MSC. A large portion of the upper section is obscured by a black rectangular block. Within this black block, a white horizontal arrow points to the right. Below the black block, a dashed line originates from a point on the left and connects to a rounded rectangular box. A solid line with an arrowhead also points from the right side of the upper section down to the top of the same rounded rectangular box. + +A process flow diagram for VGCS handling in the anchor MSC, sheet 3 of 7. Most of the top half is obscured by a black rectangle. Visible elements include a white arrow pointing right within the black area, a dashed line leading from the bottom of the black area to a rounded rectangle, and a solid line with an arrow pointing from the black area to the same rounded rectangle. + +**Figure 8: The VGCS handling process in the anchor MSC (sheet 3 of 7)** + +![A partially redacted SDL diagram showing the VGCS handling process in the anchor MSC.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +The diagram is a Specification and Description Language (SDL) flowchart, mostly obscured by a large black redaction box. The visible bottom portion shows several process paths ending in various states or connectors. From left to right: + +- A path leading from an obscured area through a task box to a state symbol (rounded rectangle). +- A path leading to a decision diamond, with one branch leading to a connector circle. +- Two separate paths leading to state symbols (rounded rectangles). +- A final path on the right leading to a state symbol (rounded rectangle). + +A partially redacted SDL diagram showing the VGCS handling process in the anchor MSC. + +**Figure 8: The VGCS handling process in the anchor MSC (sheet 4 of 7)** + +![A flowchart diagram representing the VGCS handling process in the anchor MSC. The diagram is split into two sections by a large black rectangular redaction. The top section shows the initial part of the process, starting with a document icon and a cylinder, leading to a decision diamond. The bottom section resumes the process with multiple decision diamonds, process rectangles, and flow arrows, ending with a circle connector. The shapes are light orange with black outlines.](fcc757566216206ceddbd6c775e8db02_img.jpg) + +A flowchart diagram representing the VGCS handling process in the anchor MSC. The diagram is split into two sections by a large black rectangular redaction. The top section shows the initial part of the process, starting with a document icon and a cylinder, leading to a decision diamond. The bottom section resumes the process with multiple decision diamonds, process rectangles, and flow arrows, ending with a circle connector. The shapes are light orange with black outlines. + +Figure 8: The VGCS handling process in the anchor MSC (sheet 5 of 7) + +![A flowchart diagram representing the VGCS handling process in the anchor MSC. The diagram is partially obscured by a large black rectangle at the top. Below the redaction, the flowchart consists of four main shapes connected vertically: a right-pointing arrow, a left-pointing arrow, another right-pointing arrow, and a rounded rectangle. Each of the first three shapes is connected to a rectangular box on its right side. The flow starts from the top, proceeds down through the right-pointing arrow, then the left-pointing arrow, then the second right-pointing arrow, and finally ends in the rounded rectangle. The boxes on the right are empty.](5801c19431e76330430e92a598cc7a16_img.jpg) + +A flowchart diagram representing the VGCS handling process in the anchor MSC. The diagram is partially obscured by a large black rectangle at the top. Below the redaction, the flowchart consists of four main shapes connected vertically: a right-pointing arrow, a left-pointing arrow, another right-pointing arrow, and a rounded rectangle. Each of the first three shapes is connected to a rectangular box on its right side. The flow starts from the top, proceeds down through the right-pointing arrow, then the left-pointing arrow, then the second right-pointing arrow, and finally ends in the rounded rectangle. The boxes on the right are empty. + +Figure 8: The VGCS handling process in the anchor MSC (sheet 6 of 7) + +![A sequence diagram illustrating the VGCS handling process in the anchor MSC. The diagram features several lifelines and message exchanges. At the top, there is a large black rectangular redaction box. Below it, a sequence of messages is shown: a rectangular message block, followed by a right-pointing arrow, and then another right-pointing arrow. A second large black rectangular redaction box separates the top and bottom parts of the diagram. Below this, there is a left-pointing arrow, followed by a right-pointing arrow, and finally a downward-pointing arrow leading to a rounded rectangular block. Vertical lines extend from these elements down towards the bottom of the diagram area.](db39acbd11df5eb7e79ab84562fb8f74_img.jpg) + +A sequence diagram illustrating the VGCS handling process in the anchor MSC. The diagram features several lifelines and message exchanges. At the top, there is a large black rectangular redaction box. Below it, a sequence of messages is shown: a rectangular message block, followed by a right-pointing arrow, and then another right-pointing arrow. A second large black rectangular redaction box separates the top and bottom parts of the diagram. Below this, there is a left-pointing arrow, followed by a right-pointing arrow, and finally a downward-pointing arrow leading to a rounded rectangular block. Vertical lines extend from these elements down towards the bottom of the diagram area. + +Figure 8: The VGCS handling process in the anchor MSC (sheet 7 of 7) + +![Flowchart for VGCS_Setup_Connections_to_relay_MSCs_and_BSCs procedure. It starts with a connector, followed by A_VGCS_Assignment_Request to all BSCs. A decision 'Relay MSC included' leads to 'Prepare Group Call' to all relay MSCs if yes, or 'Wait for response' from relay MSCs and BSCs if no. The 'Wait for response' leads to a horizontal line with multiple paths: 'Prepare Group Call ACK' (leading to IAM to relay MSC), 'Prepare Group Call negative rsp', 'Abort' (leading to a decision 'IAM sent to relay MSC?' which leads to REL to relay MSC if yes, or another 'Wait for response' if no), 'Send Group Call End Signal' (leading to A_VGCS_Assignment Result), 'A_VGCS_Assignment Result', and 'Txx expired' (leading to a circle with an X). All paths eventually lead to a final 'Wait for response' from relay MSCs and BSCs, which then leads to a circle with an X. A decision 'conditions for setup met?' is also shown between REL and the final wait.](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +procedure VGCS\_Setup\_Connections\_to\_relay\_MSCs\_and\_BSCs 1(1) + +``` +graph TD; Start([ ]) --> A_VGCS_Assignment_Request[A_VGCS_Assignment_Request]; A_VGCS_Assignment_Request -.-> to_all_BSCs[to all BSCs]; A_VGCS_Assignment_Request --> Relay_MSC_included{Relay MSC included}; Relay_MSC_included -- no --> Wait_response_1((Wait for response)); Wait_response_1 -.-> from_relay_MSCs_and_BSCs_1[from relay MSCs and BSCs]; Relay_MSC_included -- yes --> Prepare_Group_Call[Prepare Group Call]; Prepare_Group_Call -.-> to_all_relay_MSCs[to all relay MSCs]; Prepare_Group_Call --> Wait_response_1; Wait_response_1 --> HorizontalLine(( )); subgraph HorizontalLine; direction LR; P1[/Prepare Group Call ACK/] --> IAM[IAM]; IAM -.-> to_relay_MSC_1[to relay MSC]; P2[/Prepare Group Call negative rsp/]; P3[/Abort/] --> IAM_sent{IAM sent to relay MSC?}; IAM_sent -- yes --> REL[REL]; REL -.-> to_relay_MSC_2[to relay MSC]; IAM_sent -- no --> Wait_response_2((Wait for response)); Wait_response_2 -.-> from_relay_MSCs_and_BSCs_2[from relay MSCs and BSCs]; P4[/Send Group Call End Signal/]; P5[/A_VGCS_Assignment Result/]; P6[/Txx expired/]; end; P1 --> Final_Wait((Wait for response)); P2 --> Final_Wait; P3 --> Final_Wait; P4 --> Final_Wait; P5 --> Final_Wait; P6 --> End((X)); Final_Wait -.-> from_relay_MSCs_and_BSCs_final[from relay MSCs and BSCs]; Final_Wait --> End; conditions_met{conditions for setup met?}; REL --> conditions_met; conditions_met -- yes --> End; conditions_met -- no --> Final_Wait; +``` + +Flowchart for VGCS\_Setup\_Connections\_to\_relay\_MSCs\_and\_BSCs procedure. It starts with a connector, followed by A\_VGCS\_Assignment\_Request to all BSCs. A decision 'Relay MSC included' leads to 'Prepare Group Call' to all relay MSCs if yes, or 'Wait for response' from relay MSCs and BSCs if no. The 'Wait for response' leads to a horizontal line with multiple paths: 'Prepare Group Call ACK' (leading to IAM to relay MSC), 'Prepare Group Call negative rsp', 'Abort' (leading to a decision 'IAM sent to relay MSC?' which leads to REL to relay MSC if yes, or another 'Wait for response' if no), 'Send Group Call End Signal' (leading to A\_VGCS\_Assignment Result), 'A\_VGCS\_Assignment Result', and 'Txx expired' (leading to a circle with an X). All paths eventually lead to a final 'Wait for response' from relay MSCs and BSCs, which then leads to a circle with an X. A decision 'conditions for setup met?' is also shown between REL and the final wait. + +Figure 9: Procedure Set-up Connections to Relay MSCs and BSCs (sheet 1 of 1) + +## 11.5 Functional requirement of Relay MSC + +The VGCS handling process in the relay MSC is shown in figure 10. + +### Successful call set-up initiated by a service subscriber + +When the VGCS handling process in the relay MSC receives a VGCS call set-up request from a service subscriber currently located in a relay MSC's area, it interrogates its associated GCR to retrieve the anchor MSC address and waits for a response. + +If the GCR returns a positive response containing the anchor MSC address, the relay MSC sets up a dedicated connection for the initiating service subscriber to the anchor MSC by constructing an IAM with calling party number set to VGCS prefix plus group call reference, and with a generic number parameter with the number qualifier indicator set to "additional calling party number" and address signal set to the address of this relay MSC, sending it to the anchor MSC, and waits for call release. + +### Negative response received from the GCR + +If the GCR returns a negative response to the relay MSC indicating that the call is already on-going locally, i.e. at the associated MSC, the relay MSC sends a Release message indicating "user busy" to the service subscriber in order to force the mobile station of the service subscriber to look for notifications of the respective group ID on the NCH and join the group call. + +If (in a RANflex configuration with group call redundancy) the GCR returns a negative response to the relay MSC indicating that the call is already on-going at another MSC within the group call relay MSC redundancy pool, the selected relay MSC interrogates the relay MSC where the group call is ongoing by means of the MAP service SEND\_GROUP\_CALL\_INFO and waits for a response. If the selected relay MSC recognizes that the relay MSC where the group call is ongoing is out of service or if that relay MSC responds with a positive SEND\_GROUP\_CALL\_INFO response (i.e. the GCRs are out of synch and the group call at the other relay MSC is not ongoing), then the selected relay MSC repeats the GCR interrogation including "ongoing call override indication". If the relay MSC where the group call is ongoing responds with a negative SEND\_GROUP\_CALL\_INFO response (ongoing call), then the selected relay MSC returns a Release message indicating "user busy" in order to force the mobile station of the service subscriber to look for notifications of the respective group ID on the NCH and join the group call. + +If the negative response from the GCR indicates any other reason than "on-going call" the VGCS call set-up request is rejected by sending a release message back to the initiator and the process returns to the idle state. + +### Successful call set-up initiated by the anchor MSC + +When the VGCS handling process in the relay MSC receives a PREPARE\_GROUP\_CALL message from the anchor MSC, it interrogates its associated GCR to retrieve the list of cells inside the relay MSC area into which the call is to be sent. + +If the GCR returns a positive response, the relay MSC requests a Group Call number from its VLR. + +If the VLR returns a Group Call number, a PREPARE\_GROUP\_CALL acknowledgement containing the Group Call number is returned to the anchor MSC and the relay MSC waits for the incoming call. + +If the incoming call identified by the Group Call number is received, the relay MSC releases the Group Call number and sets up the downlinks to the cells inside the relay MSC area into which the call is to be sent. + +If the "talker channel parameter" is used, the relay MSC shall additionally send the parameter to the affected BSCs + +If the network supports talker priorities and the group call was initiated by a service subscriber currently located in the relay MSC's area, then the relay MSC additionally sends the talker priority of the service subscriber who has initiated the call and, if applicable, the "emergency mode indication" with Uplink Seized Command messages to the affected BSCs. + +If the group call was initiated by a service subscriber currently located in the relay MSC's area, then the relay MSC shall send a SEND\_GROUP\_CALL\_END\_SIGNAL message, including the IMSI and additional information of the service subscriber, to the anchor MSC when the downlink has been set up successfully to the originating cell. Additionally, if the network supports talker priorities, the relay MSC includes the talker priority of the service subscriber in the SEND\_GROUP\_CALL\_END\_SIGNAL message. + +In a RANflex configuration, the IMSI, talker priority and additional information (initial talker information) shall be deleted by the relay MSC after sending SEND\_GROUP\_CALL\_END\_SIGNAL. If initial talker information is received in a subsequent FORWARD\_GROUP\_CALL\_SIGNALLING message, the relay MSC shall use this information for the voice group call. + +NOTE: The initial talker information sent within SEND\_GROUP\_CALL\_END\_SIGNAL can be invalid, e.g. due to a race condition, if the voice group call is simultaneously set up by a dispatcher or another service subscriber. + +If the call was not originated by a service subscriber from the relay MSC area, the relay MSC shall send a SEND\_GROUP\_CALL\_END\_SIGNAL message without IMSI information element to the anchor MSC as soon as a downlink has been set up successfully to any cell. + +Then the relay MSC waits for uplink management messages. + +### **Negative response received from the GCR II** + +If the GCR returns a negative response to the relay MSC, the relay MSC returns a PREPARE\_GROUP\_CALL negative response to the anchor MSC and returns to the idle state. + +### **No Group Call number received from VLR** + +If the VLR could not allocate a Group Call number, the relay MSC returns a PREPARE\_GROUP\_CALL negative response to the anchor MSC, informs the GCR that the call is no longer on-going and returns to the idle state. + +### **Abort received from VLR** + +If the VLR indicates that the Group Call number supervision timer has expired, the relay MSC sends an ABORT message to the anchor MSC, informs the GCR that the call is no longer on-going and returns to the idle state. + +### **Abort received from Anchor MSC** + +If, after returning a PREPARE\_GROUP\_CALL acknowledgement containing the Group Call number, an ABORT is received from the anchor MSC the relay MSC releases the Group Call number, informs the GCR that the call is no longer on-going and returns to the idle state. + +### **Abort initiated by Relay MSC** + +The relay MSC may Abort the dialogue by sending an ABORT message to the anchor MSC (e.g. if the relay MSC fails to establish any downlinks in its area). The relay MSC also releases any resources, informs the GCR that the call is no longer on-going and returns to the idle state. + +### **Unsuccessful call set-up** + +Unsuccessful call set-up is determined in the anchor MSC (as per subclause 11.3.1.1.2). The relay MSC follows the procedures specified for "Abort received from Anchor MSC" and "Call release". + +#### **Uplink management** + +If a relay MSC not supporting talker priorities receives an Uplink Release Indication message from a BSC, the relay MSC marks the uplink as free, sends a Process Group Call Signalling message indicating "uplink release indication" to the anchor MSC, sends Uplink Release Command messages to all other BSCs, and waits for further uplink management messages. + +NOTE: If there is a dedicated connection for the talking service subscriber between the relay MSC and the anchor MSC, the anchor MSC will release this connection with cause 'normal, unspecified'. + +If a relay MSC supporting talker priorities receives an Uplink Release Indication message from a BSC, the relay MSC compares the talker priority included in the Uplink Release Indication with the stored talker priority. If they are equal, the relay MSC proceeds as specified above for the relay MSC not supporting talker priorities, except that it includes the talker priority in the Process Group Call Signalling message to the anchor MSC; otherwise the relay MSC discards the Uplink Release Indication. + +If the relay MSC receives an Uplink Request message without talker priority or with talker priority "normal subscriber" from a BSC, the relay MSC checks whether the uplink is marked as free. If so, a Process Group Call Signalling message indicating "uplink request" is sent to the anchor MSC, Uplink Seized Command messages are sent to all other BSCs, the + +uplink is marked busy and the process waits for further uplink management messages. If the uplink was not free when receiving the Uplink Request, the request is rejected. + +If a relay MSC supporting talker priorities receives an Uplink Request message with a talker priority higher than "normal subscriber" from a BSC and the uplink is free or it was seized by the current talker with a lower talker priority, the relay MSC checks whether the subscriber has the subscription for the requested talker priority for that group ID. In a RANflex configuration and in a RANflex configuration with group call redundancy this check may require retrieval of information from the visited MSC/VLR by means of the MAP service SEND\_GROUP\_CALL\_INFO. If so, the relay MSC: + +- stores the received data; +- sends a Process Group Call Signalling message indicating "uplink request" and the requested talker priority to the anchor MSC; +- sends Uplink Seized Command messages with the requested talker priority to all other BSCs involved in the call and connected to this relay MSC; +- releases the current talker by sending a Clear Command message, if the talker is on a dedicated channel and is located in this relay MSC; +- marks the uplink as busy; and +- waits for further uplink management messages. + +Additionally, + +- if the requested talker priority is "emergency subscriber", the relay MSC sets the emergency mode and includes the "emergency mode indication" in the Uplink Seized Command messages; +- if the relay MSC supports the transmission of additional subscriber-related information, it interrogates the VLR to get the "additional information" assigned to the new talker. In a RANflex configuration and in a RANflex configuration with group call redundancy this may require retrieval of information from the visited MSC/VLR by means of the MAP service SEND\_GROUP\_CALL\_INFO. If "additional information" is available, the relay MSC includes the "additional information" in the Process Group Call Signalling message indicating "uplink request" to the anchor MSC. + +If a relay MSC supporting talker priorities receives an Uplink Request message with a talker priority higher than "normal subscriber" from a BSC, and the uplink was seized by the current talker with the same or a higher talker priority, then the relay MSC sends an Uplink Reject Command message with the current talker priority to the BSC. + +If the relay MSC receives an Uplink Request Confirm message from a BSC, it stores the data and waits for further uplink management messages. Additionally, if the relay MSC supports the transmission of additional subscriber-related information, it interrogates the VLR to get the "additional information" assigned to the subscriber. In a RANflex configuration and in a RANflex configuration with group call redundancy this interrogation may require retrieval of information from the visited MSC/VLR by means of the MAP service SEND\_GROUP\_CALL\_INFO. If "additional information" is available, the relay MSC sends VGCS Additional Info messages to all BSCs involved in the call and connected to this relay MSC, and a Forward Group Call Signalling message with the additional info to the anchor MSC. + +If a relay MSC supporting talker priorities receives an Emergency Reset Indication from a BSC and the subscription check is successful, the relay MSC sends a Progress Group Call Signalling message with "emergency mode reset command" to the anchor MSC and Emergency Reset Command messages to all BSCs involved in the call and connected to this relay MSC, and waits for further uplink management messages. If the talker priority at receipt of the Emergency Reset Indication is "emergency subscriber", then it is changed in the relay MSC to "normal subscriber". + +If the relay MSC receives a Forward Group Call Signalling message from a anchor MSC indicating "uplink release indication", it marks the uplink as free, sends Uplink Release command messages to all BSCs and waits for further uplink management messages. + +If the relay MSC receives a Forward Group Call Signalling message from a anchor MSC indicating "uplink seized command" with or without talker priority, then the relay MSC + +marks the uplink as busy, + +sends Uplink Seized Command messages with the requested talker priority to all BSCs involved in the call and connected to this relay MSC; + +- releases the current talker by sending a Clear Command message, if the talker is on a dedicated channel and is located in this relay MSC; and +- waits for further uplink management messages. + +Additionally, + +- if the Forward Group Call Signalling message from the anchor MSC contained the talker priority "emergency subscriber", the relay MSC sets the emergency mode and includes the "emergency mode indication" in the Uplink Seized Command messages; +- if "additional information" about the new talker was included in the Forward Group Call Signalling message from the anchor MSC, the relay MSC sends VGCS Additional Info messages to all BSCs involved in the call and connected to the relay MSC. Furthermore, the relay MSC sends a VGCS Additional Info message on the dedicated connection to the BSC serving the current talker, before it releases the current talker. + +If the relay MSC receives a Forward Group Call Signalling message with the "additional info", the relay MSC sends VGCS Additional Info message to all BSCs involved in the group call and connected to this relay MSC, and waits for further uplink management messages. + +If the relay MSC receives a Forward Group Call Signalling message from an anchor MSC indicating "uplink reject command" with or without talker priority, it returns an Uplink Reject message to the BSC which has requested the uplink and waits for further uplink management messages. If the "uplink reject command" included a talker priority, the relay MSC includes the talker priority in the Uplink Reject Command message + +If the relay MSC receives a Forward Group Call Signalling message from an anchor MSC indicating "uplink request acknowledgement" with or without talker priority, then the relay MSC + +- returns an Uplink Request Acknowledge message with the requested talker priority to the BSC which has requested the uplink; +- sets up a dedicated connection for the new talker to the anchor MSC (implementation option); +- releases the current talker by sending a Clear Command message, if the talker is on a dedicated channel and is located in this relay MSC; and +- waits for further uplink management messages. + +Additionally, + +- if the requested talker priority is "emergency subscriber", the relay MSC includes the "emergency mode indication" in the Uplink Request Acknowledge messages; +- if "additional information" about the new talker is available, the relay MSC sends VGCS Additional Info messages to all BSCs involved in the call and connected to the relay MSC. Furthermore, the relay MSC sends a VGCS Additional Info message on the dedicated connection to the BSC serving the current talker, before it releases the current talker. + +If a relay MSC supporting talker priorities receives a Forward Group Call Signalling message with "emergency mode reset command" from the anchor MSC, the relay MSC resets the emergency mode, sends Emergency Reset Command messages to all BSCs involved in the call and connected to this relay MSC, and waits for further uplink management messages. If the talker priority at receipt of the "emergency mode reset command" is "emergency subscriber", then it is changed in the relay MSC to "normal subscriber". + +If the relay MSC receives a Forward Group Call Signalling message from an anchor MSC indicating "uplink release command", it sends an Uplink Release Command message to the BSC which currently has access to the uplink and waits for further uplink management messages. + +If the relay MSC receives an ABORT message from an anchor MSC, it sends release messages to all BSCs, informs the GCR that the call is no longer on-going and the process returns to the idle state. + +#### Call release + +When receiving a release message, with cause 'normal call clearing' from the anchor MSC for the dedicated connection which was set-up for the initiating service subscriber located in the relay MSC area, the relay MSC releases the connection to the service subscriber and the process returns to the idle state. + +When the initiating service subscriber releases the call while a dedicated connection to the anchor MSC is established, the relay MSC sends a release message with cause 'normal call clearing' for the dedicated connection to the anchor MSC and the process returns to the idle state. + +When the initiating service subscriber releases the call, while on a group call channel or a dedicated connection to the relay MSC, the relay MSC sends a Process Group Call Signalling message to the anchor MSC indicating "release group call" and waits for the Release message and the Send Group Call End Signal Acknowledgement from the anchor MSC. + +When receiving a Send Group Call End Signal Acknowledgement or ABORT from the anchor MSC, or a release message for the connection that was set up using the Group Call number, the relay MSC releases all downlinks to cells inside the relay MSC area, informs the GCR that the call is no longer on-going and the process returns to the idle state. + +#### **SM MT delivery** + +When the VGCS handling process in the relay MSC receives a FORWARD\_GROUP CALL\_SIGNALLING message containing a short message TPDU from the anchor MSC, the R-MSC shall deliver the short message to the relevant cells using the already established downlink channel for the voice group call. + +![A sequence diagram illustrating the VGCS handling process in the relay MSC. The diagram is partially obscured by a large black rectangle at the top. Below the redaction, the diagram shows several light orange shapes representing lifelines and messages. At the top, two vertical lines descend from the redacted area. Below them are two rounded rectangular shapes. Further down, there are two chevron-like shapes (pointing right and left) with associated rectangular blocks. At the bottom, there is another rounded rectangular shape. Arrows indicate the flow of messages between these elements.](2a476a0b3dbc3429436246db4784ff9f_img.jpg) + +A sequence diagram illustrating the VGCS handling process in the relay MSC. The diagram is partially obscured by a large black rectangle at the top. Below the redaction, the diagram shows several light orange shapes representing lifelines and messages. At the top, two vertical lines descend from the redacted area. Below them are two rounded rectangular shapes. Further down, there are two chevron-like shapes (pointing right and left) with associated rectangular blocks. At the bottom, there is another rounded rectangular shape. Arrows indicate the flow of messages between these elements. + +Figure 10: The VGCS handling process in the relay MSC (sheet 1 of 8) + +![A large empty rectangular box with a small document icon in the top-left corner, representing a missing diagram.](acd4783cdd6f72b4687bfff877f71e43_img.jpg) + +A large, empty rectangular box with a thin black border. In the top-left corner of the box, there is a small icon of a document with a folded top-right corner. This box is a placeholder for a diagram that is missing from the document. + +A large empty rectangular box with a small document icon in the top-left corner, representing a missing diagram. + +**Figure 10: The VGCS handling process in the relay MSC (sheet 2 of 8)** + +![A diagram showing the VGCS handling process in the relay MSC. The top portion is a large black rectangle obscuring the main flow. Below it, a partial flowchart is visible, showing three orange shapes (two ovals and one arrow) connected by lines, indicating a sequence of steps that is incomplete due to the redaction.](ffb6acd27b8e3a54392840948a75869f_img.jpg) + +The diagram illustrates a process flow that is partially obscured by a large black redaction box. Below the redaction, three orange shapes are visible: a vertical oval on the left, a horizontal arrow pointing right in the center, and another vertical oval on the right. Arrows indicate a flow from the left oval, through the central arrow, to the right oval. There are also faint horizontal lines extending from the top of the redaction box to these shapes, suggesting they are part of a larger sequence of steps. + +A diagram showing the VGCS handling process in the relay MSC. The top portion is a large black rectangle obscuring the main flow. Below it, a partial flowchart is visible, showing three orange shapes (two ovals and one arrow) connected by lines, indicating a sequence of steps that is incomplete due to the redaction. + +Figure 10: The VGCS handling process in the relay MSC (sheet 3 of 8) + +![A flowchart diagram representing the VGCS handling process in a relay MSC. The diagram is partially obscured by two large black rectangular redaction boxes. The visible parts show various flow symbols: rectangles for processes, diamonds for decision points, and chevron-like shapes for connectors or data stores. Arrows indicate the flow between these elements. The layout suggests a sequential process with some branching logic.](719ef0f734259484038b2434e5dc3f24_img.jpg) + +The diagram illustrates the VGCS handling process in a relay MSC. It begins with a series of rectangular process blocks at the top, followed by a decision diamond. Below the first redaction box, the flow continues through another decision diamond, leading to two separate rectangular process blocks. The diagram concludes with two oval-shaped end symbols at the bottom. The flow is generally from top to bottom, with some horizontal branching between the decision points. + +A flowchart diagram representing the VGCS handling process in a relay MSC. The diagram is partially obscured by two large black rectangular redaction boxes. The visible parts show various flow symbols: rectangles for processes, diamonds for decision points, and chevron-like shapes for connectors or data stores. Arrows indicate the flow between these elements. The layout suggests a sequential process with some branching logic. + +Figure 10: The VGCS handling process in the relay MSC (sheet 4 of 8) + +![A diagram showing the VGCS handling process in the relay MSC. The top portion is a large black rectangle. Below it, a flowchart shows five boxes (four rectangles and one circle) with arrows pointing to them from above. The boxes are arranged horizontally, with the second one being a circle.](3198cdf0dbe501c46fe0e4073c7d8451_img.jpg) + +``` + + graph TD + subgraph "Sheet 5 of 8" + A1[ ] --> B1[ ] + A2[ ] --> B2(( )) + A3[ ] --> B3[ ] + A4[ ] --> B4[ ] + A5[ ] --> B5[ ] + end + +``` + +The diagram illustrates the VGCS handling process in the relay MSC. It features a large black rectangular area at the top, likely representing a redacted portion of the original flowchart. Below this area, a partial flowchart is visible. It consists of five boxes arranged horizontally: a rectangle, a circle (connector), a rectangle, a rectangle, and a rectangle. Arrows point from above each box down to it, indicating the flow of the process from the previous sheet or section. The boxes are light gray with black outlines. + +A diagram showing the VGCS handling process in the relay MSC. The top portion is a large black rectangle. Below it, a flowchart shows five boxes (four rectangles and one circle) with arrows pointing to them from above. The boxes are arranged horizontally, with the second one being a circle. + +**Figure 10: The VGCS handling process in the relay MSC (sheet 5 of 8)** + +![A flowchart diagram representing the VGCS handling process in a relay MSC. The diagram is partially obscured by two large black rectangular redaction boxes. The visible parts include: at the top, a small portion of a process block; in the middle, a decision diamond; and at the bottom, several process blocks and connectors. Arrows indicate the flow of the process, generally moving from top to bottom and then branching out towards the bottom right.](18bb06865e2dada3656ea3d57f290f7f_img.jpg) + +A flowchart diagram representing the VGCS handling process in a relay MSC. The diagram is partially obscured by two large black rectangular redaction boxes. The visible parts include: at the top, a small portion of a process block; in the middle, a decision diamond; and at the bottom, several process blocks and connectors. Arrows indicate the flow of the process, generally moving from top to bottom and then branching out towards the bottom right. + +Figure 10: The VGCS handling process in the relay MSC (sheet 6 of 8) + +![A partially visible flowchart diagram showing the VGCS handling process in the relay MSC. The diagram is cut off by a large black rectangle at the top. Below the rectangle, several orange rectangular boxes and arrows are visible, indicating a sequence of steps. The visible part includes three vertical paths: the left path has a box pointing to a cylinder; the middle path has a box pointing to a cylinder; the right path has a box pointing to a cylinder. There are also horizontal connections between these paths.](2f587210e4f97c32758c5972e2e83d20_img.jpg) + +The diagram illustrates a process flow, likely a sequence diagram or flowchart, representing the VGCS handling process in a relay MSC. It is divided into three main vertical lanes. The left lane contains a rectangular process box followed by a downward arrow leading to a cylindrical data store. The middle lane also features a rectangular process box with a downward arrow to a cylindrical data store. The right lane shows a rectangular process box pointing to a cylindrical data store. Horizontal lines connect elements between these lanes, indicating interactions or data flow. A large black rectangle obscures the top portion of the diagram. + +A partially visible flowchart diagram showing the VGCS handling process in the relay MSC. The diagram is cut off by a large black rectangle at the top. Below the rectangle, several orange rectangular boxes and arrows are visible, indicating a sequence of steps. The visible part includes three vertical paths: the left path has a box pointing to a cylinder; the middle path has a box pointing to a cylinder; the right path has a box pointing to a cylinder. There are also horizontal connections between these paths. + +Figure 10: The VGCS handling process in the relay MSC (sheet 7 of 8) + +![A flowchart diagram representing the VGCS handling process in a relay MSC. The diagram is partially obscured by a large black rectangle. The visible portion shows several orange shapes: diamonds representing decision nodes, pentagons representing input/output operations, rectangles representing process steps, and ovals representing start/end points. Arrows indicate the flow between these elements. The layout suggests a complex decision tree or process flow that has been cut off.](e7010c66da16316c2935dfbbef5056b3_img.jpg) + +A flowchart diagram representing the VGCS handling process in a relay MSC. The diagram is partially obscured by a large black rectangle. The visible portion shows several orange shapes: diamonds representing decision nodes, pentagons representing input/output operations, rectangles representing process steps, and ovals representing start/end points. Arrows indicate the flow between these elements. The layout suggests a complex decision tree or process flow that has been cut off. + +Figure 10: The VGCS handling process in the relay MSC (sheet 8 of 8) + +## 11.5A Functional requirement of group call serving MSC (within a RANflex pool) + +The process in the group call serving MSC is shown in figure 10A1. + +The group call serving MSC is either the anchor MSC or a relay MSC. + +### Successful call set-up initiated by a service subscriber + +When receiving a SEND\_GROUP\_CALL\_INFO interrogation request from a VMSC, the group call serving MSC (in a RANflex configuration with group call redundancy: the selected group call serving MSC) interrogates its associated GCR to retrieve the Group Call Reference and the Anchor MSC address from the given cell Id / Group Id pair and return this information to the VMSC. The group call serving MSC shall temporarily store in its associated GCR the initiating subscriber's talker priority, his subscribed additional information, his IMSI as received in the interrogation request from the VMSC and the originating cell id. The group call serving MSC shall then wait for the group call being set up: + +If the group call serving MSC is the anchor MSC, it waits for an IAM from the VMSC; if the group call serving MSC is a relay MSC, it waits for a PREPARE\_GROUP\_CALL from the anchor MSC. + +Waiting for the group call being set up shall be supervised by a timer T3. + +When receiving IAM from the visited MSC, timer T3 is stopped and processing continues in the process VGCS\_Handling\_Anchor\_MSC after reception of the VGCS call setup request in Idle state. + +When receiving PREPARE\_GROUP\_CALL from the anchor MSC, timer T3 is stopped and processing continues in the process VGCS\_Handling\_Relay\_MSC after reception of PREPARE GROUP CALL in Idle state. + +### Unsuccessful call set-up + +In a RANflex configuration: If the group call reference could not be retrieved or the GCR returns a negative response indicating "on-going call" to the group call serving MSC, an error indication is returned to the VMSC and the process returns to the idle state. + +In a RANflex configuration with group call redundancy: If the GCR returns a negative response indicating "on-going call" to the group call serving MSC, the group call serving MSC forwards the SEND\_GROUP\_CALL\_INFO message within the same redundancy pool to the group call serving MSC where the group call is ongoing. + +If the selected group call serving MSC recognizes that the group call serving MSC where the group call is ongoing is out of service or if that group call serving MSC responds with a positive SEND\_GROUP\_CALL\_INFO response (i.e. the GCRs are out of synch and the group call at the other group call serving MSC is not ongoing), then the selected group call serving MSC repeats the GCR interrogation including "ongoing call override indication". If the group call serving MSC where the group call is ongoing responds with a negative SEND\_GROUP\_CALL\_INFO response (ongoing call), then the selected group call serving MSC returns a negative SEND\_GROUP\_CALL\_INFO response indicating "ongoingGroupCall" to the VMSC in order to force the mobile station of the service subscriber to look for notifications of the respective group ID on the NCH and join the group call. + +At timeout of timer T3 the temporarily stored initiating subscriber's talker priority, his subscribed additional information and his IMSI shall be deleted from the GCR. + +![A diagram showing the start of a flowchart with two orange rounded rectangles and a dashed box, but the main content is obscured by a large black rectangle.](4806f9f95fff13a30d6523bd6ffeac63_img.jpg) + +The diagram is a flowchart enclosed in a rectangular frame. At the top left, there is a dashed rectangular box. To its right, there is an orange rounded rectangle with a downward-pointing arrow leading to another identical orange rounded rectangle. The central portion of the diagram is completely obscured by a large, solid black rectangle. Below the black rectangle, at the bottom of the frame, there are two small, horizontal, orange-outlined rectangular boxes. + +A diagram showing the start of a flowchart with two orange rounded rectangles and a dashed box, but the main content is obscured by a large black rectangle. + +Figure 10A1: The VGCS handling process in the group call serving MSC (sheet 1 of 2) + +![Figure 10A1: The VGCS handling process in the group call serving MSC (sheet 2 of 2). The diagram is a sequence diagram showing interactions between various network elements. At the top, there are two rectangular boxes representing external entities. Below them, a circle represents a User Equipment (UE). A large black horizontal bar obscures the top portion of the diagram. Below the bar, the diagram shows a hierarchy of network elements: two ovals (likely VLRs) connected to a central rectangular box (MSC). This MSC is connected to three rectangular boxes (likely RANs or other MSCs). Below these, there are more rectangular boxes and ovals, with one circle at the bottom left. Arrows indicate the flow of messages between these elements, representing the VGCS handling process.](c07e21a8d65991db04263322f859c94f_img.jpg) + +Figure 10A1: The VGCS handling process in the group call serving MSC (sheet 2 of 2). The diagram is a sequence diagram showing interactions between various network elements. At the top, there are two rectangular boxes representing external entities. Below them, a circle represents a User Equipment (UE). A large black horizontal bar obscures the top portion of the diagram. Below the bar, the diagram shows a hierarchy of network elements: two ovals (likely VLRs) connected to a central rectangular box (MSC). This MSC is connected to three rectangular boxes (likely RANs or other MSCs). Below these, there are more rectangular boxes and ovals, with one circle at the bottom left. Arrows indicate the flow of messages between these elements, representing the VGCS handling process. + +**Figure 10A1: The VGCS handling process in the group call serving MSC (sheet 2 of 2)** + +#### **Retrieval of VGCS subscription data** + +The procedure in the group call serving MSC to retrieve subscription information from the VMSC is shown in figure 10A2. + +In a RANflex configuration with or without group call redundancy, if the group call serving MSC receives an uplink request or a request to transmit application-specific data, it determines from the NRI in the requesting subscriber's TMSI whether it is the requesting subscriber's VMSC. + +If it is not, then the group call serving MSC retrieves the IMSI and information about subscribed talker priorities from the VLR of the VMSC by means of the MAP service SEND\_GROUP\_CALL\_INFO. + +- If a response is received from the VMSC, the procedure ends. + +As an implementation option the group call serving MSC may initiate a MAP Update\_Location\_Area procedure towards its VLR in order to retrieve the subscriber data from the HLR. During this procedure the VLR allocates a new TMSI including an NRI referring to the group call serving MSC. + +As an alternative implementation option the group call serving MSC may store the TMSI temporarily together with the IMSI and the other information received from the VLR of the VMSC and use these data for subscription checks during subsequent talker requests. Use of the temporary subscriber data may be limited e.g. to an + +implementation dependent time or for an implementation dependent number of subsequent talker requests. The group call serving MSC shall delete the temporary subscriber data when the group call is released. + +- If no response is received or if the VMSC is out of service, the group call serving MSC should initiate a MAP Update\_Location\_Area procedure towards its VLR. During this procedure the MSC requests the MS to provide its IMSI and the VLR allocates a new TMSI including an NRI referring to the group call serving MSC. The group call serving MSC checks whether the MS has the necessary subscription for the requested action when the Update\_Location\_Area procedure is completed. + +NOTE: As an operator option, for this case of a network internal failure, the group call serving MSC can skip the MAP Update\_Location\_Area procedure and perform the subscription check using a backup subscription profile. + +As an operator option, the group call serving MSC may proceed with the handling of the request received from the MS, assuming that the MS has the necessary subscription, and perform the Update\_Location\_Area procedure in parallel. If the result of the subscription check after completion of the Update\_Location\_Area procedure is negative and the MS still has the uplink seized, the group call serving MSC shall initiate an uplink release procedure. + +#### **Implicit location update procedure** + +The procedure for the implicit location update in the group call serving MSC is shown in figure 10A3. + +Sheet 1: The procedures Check\_IMEI\_MSC, Obtain\_IMEI\_MSC, Obtain\_IMSI\_MSC and Authenticate\_MSC are specified in 3GPP TS 23.018 [18]. + +![Flowchart of the VGCS subscription info retrieval procedure.](49fe8fe978c0f7e73112d231feb377eb_img.jpg) + +``` + + graph TD + Start[Blacked out area] --> Triangle((Triangle)) + Triangle --> Hexagon{Hexagon Node} + Hexagon -->|Left| Rect1[Rectangular Node Left] + Hexagon -->|Right| Rect2[Rectangular Node Right] + Rect1 --> Join(( )) + Rect2 --> Join + Hexagon --> Join + Join --> End((X)) + +``` + +The diagram illustrates a network procedure flowchart. The top half is obscured by a large black rectangle. Below this, a white triangle points upwards. The visible logic involves a central hexagonal decision node. To its left is a rectangular process block, and to its right is another rectangular process block. Lines connect these blocks to a central vertical path that terminates in a circular node containing an 'X'. Arrows indicate a flow from the left rectangle back to the central path and from the central hexagon downwards. + +Flowchart of the VGCS subscription info retrieval procedure. + +**Figure 10A2: The VGCS subscription info retrieval procedure in the group call serving MSC (sheet 1 of 1)** + +![SDL flowchart for implicit location update procedure in the group call serving MSC. The top part is obscured by a black rectangle. Below it, the flow starts at a state oval, branches into five parallel paths starting with input symbols. Four paths involve sub-processes (rectangles with double side bars) that merge into a decision hexagon. One path leads to a separate state oval which then branches into four more paths. The diagram includes process rectangles, input/output parallelograms, and termination symbols (circles with X).](5cf80bac69830ea773ac17c87e0ae24d_img.jpg) + +``` + + graph TD + Start([State]) --> Branch1{ } + Branch1 --> In1[/Input 1/] + Branch1 --> In2[/Input 2/] + Branch1 --> In3[/Input 3/] + Branch1 --> In4[/Input 4/] + Branch1 --> In5[/Input 5/] + + In1 --> Proc1[Process 1] + In2 --> SubProc2[[Sub-process 2]] + In3 --> SubProc3[[Sub-process 3]] + In4 --> SubProc4[[Sub-process 4]] + In5 --> SubProc5[[Sub-process 5]] + + SubProc2 --> Merge1 + SubProc3 --> Merge1 + SubProc4 --> Merge1 + SubProc5 --> Merge1 + + Merge1 --> Decision{Decision} + Decision --> Proc6[Process 6] + Proc6 --> Term1((X)) + + Decision -- Left --> State2([State 2]) + Proc1 --> State2 + + State2 --> Branch2{ } + Branch2 --> In6[/Input 6/] + Branch2 --> In7[/Input 7/] + Branch2 --> In8[/Input 8/] + Branch2 --> In9[/Input 9/] + + In6 --> Proc7[Process 7] + In7 --> Term2((X)) + In8 --> Proc8[Process 8] + In9 --> Term3((X)) + + Proc7 --> State3([State 3]) + Proc8 --> Term4((X)) + + style Term1 fill:none + style Term2 fill:none + style Term3 fill:none + style Term4 fill:none + +``` + +SDL flowchart for implicit location update procedure in the group call serving MSC. The top part is obscured by a black rectangle. Below it, the flow starts at a state oval, branches into five parallel paths starting with input symbols. Four paths involve sub-processes (rectangles with double side bars) that merge into a decision hexagon. One path leads to a separate state oval which then branches into four more paths. The diagram includes process rectangles, input/output parallelograms, and termination symbols (circles with X). + +Figure 10A3: The implicit location update procedure in the group call serving MSC (sheet 1 of 3) + +![A sequence diagram illustrating the implicit location update procedure in the group call serving MSC. The diagram features three lifelines. The first lifeline on the left consists of a parallelogram, a rectangle, a circle with an 'X', a parallelogram, and a rectangle. The second lifeline in the center consists of a parallelogram, a rectangle, an oval, a parallelogram, a rectangle, and a circle with an 'X'. The third lifeline on the right consists of a parallelogram, a rectangle, and an oval. Arrows indicate the flow of messages between these elements, including a horizontal arrow from the first lifeline's parallelogram to the second lifeline's oval, and a vertical arrow from the first lifeline's rectangle to the second lifeline's rectangle. A large black rectangular area obscures the top portion of the diagram, with a white rounded rectangle and a parallelogram visible within it.](750b1652a4f4791b84c02aa755a1dedd_img.jpg) + +A sequence diagram illustrating the implicit location update procedure in the group call serving MSC. The diagram features three lifelines. The first lifeline on the left consists of a parallelogram, a rectangle, a circle with an 'X', a parallelogram, and a rectangle. The second lifeline in the center consists of a parallelogram, a rectangle, an oval, a parallelogram, a rectangle, and a circle with an 'X'. The third lifeline on the right consists of a parallelogram, a rectangle, and an oval. Arrows indicate the flow of messages between these elements, including a horizontal arrow from the first lifeline's parallelogram to the second lifeline's oval, and a vertical arrow from the first lifeline's rectangle to the second lifeline's rectangle. A large black rectangular area obscures the top portion of the diagram, with a white rounded rectangle and a parallelogram visible within it. + +Figure 10A3: The implicit location update procedure in the group call serving MSC (sheet 2 of 3) + +![Sequence diagram showing the implicit location update procedure in the group call serving MSC. The diagram includes lifelines for a User Equipment (UE), a Radio Network Controller (RNC), five Base Station Controllers (BSCs), and three MSCs. The sequence starts with a message from the UE to the RNC, which then branches to the five BSCs. The first BSC sends a message to the first MSC. The other four BSCs send messages to a second MSC, which then sends a message to a third MSC. The third MSC sends a response back to the second MSC, which then branches back to the four BSCs. Finally, the first BSC sends a message to the first MSC, which then sends a response back to the UE.](f61d0925551545b5938b3a4d1bbf63c3_img.jpg) + +The diagram illustrates a sequence of messages between network elements. At the top, a dashed box with a folded corner is present. Below it, the sequence begins with a message from a UE (represented by a rounded rectangle) to an RNC (represented by a parallelogram). The RNC then sends a message to a horizontal bus connecting five BSCs (represented by parallelograms). The first BSC sends a message to a first MSC (represented by a rounded rectangle). The other four BSCs send messages to a second MSC (represented by a rectangle). The second MSC sends a message to a third MSC (represented by a circle with an 'X'). The third MSC sends a response back to the second MSC, which then branches back to the four BSCs. Finally, the first BSC sends a message to the first MSC, which then sends a response back to the UE. + +Sequence diagram showing the implicit location update procedure in the group call serving MSC. The diagram includes lifelines for a User Equipment (UE), a Radio Network Controller (RNC), five Base Station Controllers (BSCs), and three MSCs. The sequence starts with a message from the UE to the RNC, which then branches to the five BSCs. The first BSC sends a message to the first MSC. The other four BSCs send messages to a second MSC, which then sends a message to a third MSC. The third MSC sends a response back to the second MSC, which then branches back to the four BSCs. Finally, the first BSC sends a message to the first MSC, which then sends a response back to the UE. + +Figure 10A3: The implicit location update procedure in the group call serving MSC (sheet 3 of 3) + +## 11.5B Functional requirement of VMSC (within a RANflex pool) + +The process in the visited MSC is shown in figure 10B. + +### Successful call set-up initiated by a service subscriber + +When the VGCS handling process in the originating MSC receives a VGCS call set-up request from a service subscriber, the VMSC derives the address of the group call serving MSC or group call serving MSC redundancy pool from the requesting subscriber's current LAC. If the VMSC is the group call serving MSC or belongs to the group call serving MSC redundancy pool of the requesting subscriber's current LAC, processing continues in the process VGCS\_Handling\_Anchor\_MSC or VGCS\_Handling\_Relay\_MSC after reception of the VGCS call setup request in Idle state. Otherwise, the visited MSC interrogates the group call serving MSC by means of the MAP service SEND\_GROUP\_CALL\_INFO to retrieve the anchor MSC address and Group Call Reference and waits for a response. + +If the group call serving MSC returns a positive response containing the address of the anchor MSC or anchor MSC redundancy pool and the address is different from the visited MSC's address, the originating MSC sets up a dedicated connection for the initiating service subscriber to the anchor MSC by constructing an IAM with calling party number set to VGCS prefix plus group call reference, and with a generic number parameter with the number qualifier indicator set to "additional calling party number" and address signal set to the address of the group call serving MSC (in a RANflex configuration with group call redundancy this shall be the same address as used to route the SEND\_GROUP\_CALL\_INFO message, i.e. identifying the redundancy pool), sending it to the anchor MSC, and waits for call release. If the VMSC is the anchor MSC or belongs to the anchor MSC redundancy pool, processing continues in the process VGCS\_Handling\_Anchor\_MSC after reception of the VGCS call setup request in Idle state. + +### Negative response received from the group call serving MSC + +If the group call serving MSC returns a negative response to the originating MSC indicating that the call is already on-going, the originating MSC sends a Release message indicating "user busy" to the service subscriber in order to force the mobile station of the service subscriber to look for notifications of the respective group ID on the NCH and join the group call. + +If the negative response from the group call serving MSC indicates any other reason than "on-going call" the VGCS call set-up request is rejected by sending a release message back to the initiator and the process returns to the idle state. + +![A complex flowchart diagram with various orange-outlined shapes connected by arrows, partially obscured by two large black horizontal bars.](38d82ffe820e339811b396206f40a201_img.jpg) + +``` + + graph TD + Start([Start Oval]) --> Step1[Rectangle] + Step1 --> Step2{{Chevron Right}} + Step2 --> Step3[Rectangle] + Step3 --> Decision1{Diamond} + Decision1 -- Left --> Step4[Rectangle] + Decision1 -- Down --> Step5[Rectangle] + Decision1 -- Right --> Step6[Rectangle] + + subgraph Obscured_Section_1 + direction TB + BlackBar1[Black Bar Area] + end + + Step5 --> BlackBar1 + + BlackBar1 --> Step7[Rectangle] + Step7 --> Step8{{Chevron Right}} + Step8 --> Decision2{Diamond} + Decision2 --> Step9[Rectangle] + Step9 --> Step10{{Chevron Left}} + Step10 --> Step11[Rectangle] + + subgraph Obscured_Section_2 + direction TB + BlackBar2[Black Bar Area] + end + + Step11 --> BlackBar2 + + BlackBar2 --> Step12[Rectangle] + Step12 --> Step13{{Chevron Right}} + Step13 --> Step14[Rectangle] + Step14 --> Step15{{Chevron Right}} + Step15 --> End([End Oval]) + +``` + +The diagram is a flowchart consisting of orange-outlined shapes connected by arrows. It begins with an oval at the top, followed by a sequence of rectangles, chevrons, and a diamond decision point. The flow is interrupted by two large black horizontal bars. Between the bars, the flow continues through more rectangles, chevrons, and diamonds. Below the second bar, the sequence concludes with further processing steps and a final oval shape. A dashed document icon is present in the top-left corner of the diagram area. + +A complex flowchart diagram with various orange-outlined shapes connected by arrows, partially obscured by two large black horizontal bars. + +Figure 10B: The VGCS handling process in the VMSC (sheet 1 of 2) + +![Flowchart of the VGCS handling process in the VMSC (sheet 1 of 2).](114902bbeea56bda01b64b43fad41920_img.jpg) + +process VGCS\_Handling\_VMSC 2(2) + +``` +graph TD; Idle1([Idle]) --> SendGCI1{{Send Group Call Info}}; SendGCI1 -.-> fromGCSMSC[from group call serving MSC]; SendGCI1 --> SendGCI2{{Send Group Call Info}}; SendGCI2 -.-> toVLR[to local VLR]; SendGCI2 --> Wait[Wait for response]; Wait --> PosResp{{positive response}}; Wait --> NegResp{{negative response}}; PosResp -.-> fromVLR[from VLR]; PosResp --> SendGCIAck{{Send Group Call Info Ack}}; NegResp --> SendGCIError{{Send Group Call Info Error}}; SendGCIAck -.-> toGCSMSC[to group call serving MSC]; SendGCIAck --> Idle2([Idle]); SendGCIError --> Idle2; +``` + +The flowchart illustrates the VGCS handling process in the VMSC. It begins with an 'Idle' state, followed by 'Send Group Call Info' (receiving from group call serving MSC), 'Send Group Call Info' (sending to local VLR), 'Wait for response', a decision point for 'positive response' (receiving from VLR) or 'negative response', 'Send Group Call Info Ack' (sending to group call serving MSC) or 'Send Group Call Info Error', and finally returning to an 'Idle' state. + +Flowchart of the VGCS handling process in the VMSC (sheet 1 of 2). + +Figure 10B: The VGCS handling process in the VMSC (sheet 2 of 2) + +## 11.6 Functional requirement of GCR + +The process in the GCR for RANflex and without RANflex configurations is shown in figure 11. + +The process in the GCR for RANflex configuration with group call redundancy is shown in figure 11A. Figure 11A does not show details on GCR restoration (see subclause 5.3.3). + +### Service subscriber initiated call + +If the GCR receives an interrogation request for a call initiated by a service subscriber who is located in the MSC area of the associated MSC, the GCR calculates the group call reference from the Group ID and the originating cell ID. + +If the group call reference was successfully calculated, the GCR checks whether a VGCS call with that group call reference is already on-going. + +If the call is not marked as on-going, the GCR checks whether an anchor MSC address is stored in its group call reference record. If this is the case and initial talker information is not yet stored, a positive response including the anchor MSC address is returned to the MSC, the initial talker information (IMSI, talker priority, originating cell id and additional info) of the initiating service subscriber is stored in the GCR and the process returns to the idle state. If anchor MSC address and initial talker information are stored (this is the case where the associated MSC is relay MSC, and timer T3 is running, i.e. group call setup is in progress but the call is not yet fully established), a negative response indicating "on-going call" is returned to the MSC and the process returns to the idle state. If no anchor MSC address is stored (i.e. the associated MSC is anchor MSC with respect to this group call reference) the GCR marks its group call reference record with "on-going call" and returns a positive response including the group call attributes to the MSC and the process returns to the idle state. + +If the group call reference could not be successfully calculated from the Group ID and the originating cell ID, the GCR returns a negative response indicating "failure" to the MSC and the process returns to the idle state. + +If the call was marked as on-going, the GCR returns a negative response indicating "on-going call" to the MSC and the process returns to the idle state. + +### IAM initiated call + +If the GCR receives an interrogation request for a call initiated by a dispatcher or by a service subscriber who is not located in the MSC area of the associated MSC, the GCR checks the calling party number of the initiator against the list of identities of dispatchers which are allowed to initiate the voice group call and against the VGCS prefix plus group call reference in order to determine whether the initiator is allowed to set-up the call. If the check is successful the GCR checks whether a VGCS call with the same group call reference is already on-going. + +If the call is not marked as on-going, the GCR marks its group call reference record with "on-going call" and returns a positive response including the group call attributes to the MSC and the process returns to the idle state. In addition the GCR shall delete stored initial talker information (if any). + +If the calling party number check was not successful, the GCR returns a negative response indicating "failure" to the MSC and the process returns to the idle state. + +If the call was marked as on-going, the GCR returns a negative response indicating "on-going call" to the MSC and the process returns to the idle state. + +### Anchor MSC triggered call + +If the GCR (associated to a relay MSC) receives an interrogation request for a call triggered by the anchor MSC, the GCR returns a positive response to the MSC including: + +- the list of cells inside the MSC area of the requesting MSC in which the call is to be sent + - the stored initial talker information (if any) +- and +- marks its group call reference with "on-going call", + - deletes the stored initial talker information (if any) +- and the process returns to the idle state. + +### VMS C triggered call (in a RANflex configuration) + +If the GCR (associated to a group call serving MSC) receives an interrogation request for a call triggered by the VMS C, the GCR + +- calculates the group call reference from the Group ID and the originating cell ID. + +If for the calculated group call reference the record is marked with "on-going call" or initial talker information is already stored, a negative response indicating "on-going call" is returned to the GCSSMSC and the process returns to the idle state. Otherwise the GCR + +- stores the initial talker information (IMSI, talker priority, originating cell id and additional information received with the request); and +- returns a positive response including group call reference and , if the group call serving MSC is a relay MSC, the anchor MSC address. + +### **Call release** + +If the GCR receives a call released indication from the MSC, the "on-going call" indicator in the group call reference record is reset, the initial talker information is deleted (if any) and the process returns to the idle state. + +### **SM MT delivery** + +When receiving an interrogation request from the anchorMSC, the GCR shall check if the voice group call is established or not and shall send a response containing the voice group call attributes for short message transfer to the anchor MSC. + +![A partial flowchart diagram showing various shapes like diamonds, rectangles, and chevrons connected by arrows. A large black rectangle obscures the top portion of the diagram.](18003425d0e8638dde4acc9c5c468c5c_img.jpg) + +The diagram is a partial flowchart. At the top, a large black rectangle obscures the upper portion of the flow. Below this, the visible part of the flowchart includes: + +- A diamond shape at the top left with an arrow pointing down to a rectangle. +- To the right of this rectangle is a dashed rectangle. +- Below the first rectangle is another diamond shape. +- Below that diamond is a third diamond shape. +- To the left of the third diamond is a rectangle, which points down to a left-pointing chevron. +- The third diamond has two outgoing arrows: one pointing right to a right-pointing chevron, and another pointing down to a bottom-pointing chevron. +- There are three right-pointing chevrons in total, arranged horizontally. The leftmost one is from the rectangle on the left. The middle one is from the third diamond. The rightmost one is from a vertical line originating from the top right. +- All three right-pointing chevrons point to a single horizontal line that leads to a bottom-pointing chevron at the bottom left. +- On the far right, there is a vertical stack of three shapes: a rectangle, another rectangle, and a bottom-pointing chevron, connected by arrows. + +A partial flowchart diagram showing various shapes like diamonds, rectangles, and chevrons connected by arrows. A large black rectangle obscures the top portion of the diagram. + +Figure 11: The process in the GCR (sheet 1 of 3) + +![A flowchart diagram showing a process flow with various shapes including rectangles, diamonds, and ovals, connected by arrows. The diagram is mostly empty with placeholder shapes.](0dfdff10c725fe9c332b07ade9d23a5e_img.jpg) + +The diagram is a flowchart with the following structure: + +- At the top left, there is a small rectangle with a folded corner icon. +- Below it, a vertical line descends to a rectangle. +- To the right of this rectangle is a larger, empty rectangle. +- Below the first rectangle, a vertical line leads to a diamond (decision node). +- From the left side of this diamond, a vertical line descends to a right-pointing chevron shape. +- Below the chevron, a vertical line leads to an oval (end node). +- From the right side of the first diamond, a horizontal line extends to the right, leading to a second diamond. +- From the bottom of the second diamond, a vertical line descends to another right-pointing chevron shape. +- Below this chevron, a vertical line leads to another oval (end node). +- From the right side of the second diamond, a horizontal line extends to the right, leading to a third diamond. +- From the bottom of the third diamond, a vertical line descends to a rectangle. +- Below this rectangle, a vertical line descends to a right-pointing chevron shape. +- Below this chevron, a vertical line descends to an oval (end node). +- From the left side of the third diamond, a vertical line descends to a rectangle. +- Below this rectangle, a vertical line descends to a right-pointing chevron shape. +- Below this chevron, a vertical line descends to an oval (end node). + +A flowchart diagram showing a process flow with various shapes including rectangles, diamonds, and ovals, connected by arrows. The diagram is mostly empty with placeholder shapes. + +Figure 11: The process in the GCR (sheet 2 of 3) + +![A flowchart diagram showing a process flow with various shapes like rectangles, diamonds, and cylinders, but with no text labels.](ffe0fef452a0ae9a20253c319c54e13c_img.jpg) + +The diagram is a flowchart with the following structure: It begins with a small rectangle at the top left, with a line extending downwards from its bottom. This line connects to a larger rectangle. To the right of this rectangle is another, wider rectangle, connected by a horizontal line. Below the first rectangle is a diamond shape. From the right side of this diamond, a line extends horizontally to the right, ending in another diamond shape. From the bottom of the second diamond, a line extends downwards. From the bottom of the first diamond, a line extends downwards, passing through a pentagonal shape (pointing right) to a cylinder shape. The line from the second diamond also passes through a pentagonal shape (pointing right) to a cylinder shape. To the right of these, there is a third pentagonal shape (pointing right) above a third cylinder shape, with a line connecting them. Above the third pentagonal shape is a rectangle, which is not connected to any other part of the flow. In the top left corner of the diagram area, there is a small icon of a document with a folded corner. + +A flowchart diagram showing a process flow with various shapes like rectangles, diamonds, and cylinders, but with no text labels. + +Figure 11: The process in the GCR (sheet 3 of 3) + +![A diagram showing a large black rectangle with four small white rectangles on its right side and three white circles at its bottom center, positioned above a large white rectangular area.](a963ca41bde1669b18a4b783616f228b_img.jpg) + +The diagram consists of a large black rectangle at the top. On its right side, there are four small white rectangles stacked vertically. At the bottom center of the black rectangle, there are three white circles. Below the black rectangle is a large white rectangular area. A dashed line is visible on the left side of the white area, and a solid line forms its right boundary. + +A diagram showing a large black rectangle with four small white rectangles on its right side and three white circles at its bottom center, positioned above a large white rectangular area. + +Figure 11A: The Process in the GCR for RANflex with group call redundancy (sheet 1 of 4) + +![A sequence diagram illustrating a process in the GCR for RANflex with group call redundancy. The diagram features four lifelines. The first lifeline starts with a rectangle, followed by a hexagon, and ends with a parallelogram and an oval. The second lifeline starts with a rectangle, followed by two hexagons, a rectangle, a hexagon, and ends with a parallelogram and an oval. The third lifeline starts with a circle, followed by a hexagon, a rectangle, a rectangle, a parallelogram, and ends with an oval. The fourth lifeline starts with a circle, followed by a parallelogram, a rectangle, a rectangle, a parallelogram, and ends with an oval. Arrows indicate the flow of messages between these elements across the lifelines.](de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg) + +The diagram is a sequence diagram with four lifelines. At the top, there is a solid black horizontal bar. Below it, the lifelines are represented by vertical lines. Lifeline 1 (leftmost) has a rectangle at the top, followed by a hexagon, and at the bottom, a parallelogram and an oval. Lifeline 2 has a rectangle at the top, followed by two hexagons, a rectangle, a hexagon, and at the bottom, a parallelogram and an oval. Lifeline 3 has a circle at the top, followed by a hexagon, a rectangle, a rectangle, a parallelogram, and at the bottom, an oval. Lifeline 4 (rightmost) has a circle at the top, followed by a parallelogram, a rectangle, a rectangle, a parallelogram, and at the bottom, an oval. Arrows indicate the flow of messages between these elements across the lifelines. + +A sequence diagram illustrating a process in the GCR for RANflex with group call redundancy. The diagram features four lifelines. The first lifeline starts with a rectangle, followed by a hexagon, and ends with a parallelogram and an oval. The second lifeline starts with a rectangle, followed by two hexagons, a rectangle, a hexagon, and ends with a parallelogram and an oval. The third lifeline starts with a circle, followed by a hexagon, a rectangle, a rectangle, a parallelogram, and ends with an oval. The fourth lifeline starts with a circle, followed by a parallelogram, a rectangle, a rectangle, a parallelogram, and ends with an oval. Arrows indicate the flow of messages between these elements across the lifelines. + +Figure 11A: The Process in the GCR for RANflex with group call redundancy (sheet 2 of 4) + +![Flowchart diagram for GCR process in RANflex with group call redundancy. The diagram shows a start node leading to a process block, followed by a series of decision diamonds and process steps. There are three main vertical branches leading to terminal output symbols.](e16bfa31d748f4d99ec4ae3d16656926_img.jpg) + +``` + +graph TD + Start(( )) --> P1[ ] + P1 --> D1{ } + D1 --> |No| T1_1[ ] + T1_1 --> T1_2[ ] + D1 --> |Yes| D2{ } + D2 --> |No| D3{ } + D3 --> P2[ ] + P2 --> P3[ ] + P3 --> P4[ ] + P4 --> D2 + D2 --> |Yes| T2_1[ ] + T2_1 --> T2_2[ ] + D3 --> |Yes| P5[ ] + P5 --> P6[ ] + P6 --> P7[ ] + P7 --> P8[ ] + P8 --> T3_1[ ] + T3_1 --> T3_2[ ] + +``` + +Flowchart diagram for GCR process in RANflex with group call redundancy. The diagram shows a start node leading to a process block, followed by a series of decision diamonds and process steps. There are three main vertical branches leading to terminal output symbols. + +**Figure 11A: The Process in the GCR for RANflex with group call redundancy (sheet 3 of 4)** + +![A flowchart diagram showing a process flow with three vertical paths. Path 1 (left) starts with a circle, followed by a rectangle, then a hexagon, leading down to a left-pointing arrow and a cylinder. Path 2 (middle) starts from the first hexagon, goes right to another hexagon, then down to another hexagon, then down to a left-pointing arrow and a cylinder. Path 3 (right) starts from the second hexagon, goes right, then down through three rectangles, then down to a right-pointing arrow, a left-pointing arrow, and a cylinder. A horizontal line with an arrow points from the third hexagon of Path 2 to the third rectangle of Path 3. There are also small boxes in the top corners of the diagram frame.](c0ca823603794512478906b302176bca_img.jpg) + +A flowchart diagram showing a process flow with three vertical paths. Path 1 (left) starts with a circle, followed by a rectangle, then a hexagon, leading down to a left-pointing arrow and a cylinder. Path 2 (middle) starts from the first hexagon, goes right to another hexagon, then down to another hexagon, then down to a left-pointing arrow and a cylinder. Path 3 (right) starts from the second hexagon, goes right, then down through three rectangles, then down to a right-pointing arrow, a left-pointing arrow, and a cylinder. A horizontal line with an arrow points from the third hexagon of Path 2 to the third rectangle of Path 3. There are also small boxes in the top corners of the diagram frame. + +Figure 11A: The Process in the GCR for RANflex with group call redundancy (sheet 4 of 4) + +![A large empty rectangular box, likely a placeholder for a diagram or figure.](1b670c6eaa5f106cd82f1c676c2cabd7_img.jpg) + +A large, empty rectangular box with a thin black border, occupying the upper half of the page. It appears to be a placeholder for a figure or diagram that is missing from the document. + +A large empty rectangular box, likely a placeholder for a diagram or figure. + +**Figure 11B: Procedure Synchronize Transient Data** + +## 11.7 Functional requirement of VLR + +The Group Call number allocation process in the VLR is shown in figure 12. + +### Successful procedure + +When receiving a request from the relay MSC to allocate a Group Call number, the VLR checks if a Group Call number is available. If so it selects a Group Call number, marks the number as allocated, returns a positive response including the Group Call number to the MSC, starts a supervision timer and waits for removal of the Group Call number. If the VLR receives a request to release the Group Call number, the VLR marks the Group Call number as free and the process returns to the idle state. + +### No Group Call number available + +If no Group Call number is available, the VLR returns a negative response indicating "no Group Call number available" to the MSC and the process returns to the idle state. + +### Supervision timer expires + +If the supervision timer expires, the VLR indicates to the relay MSC that the dialogue has to be aborted. + +![Flowchart of the Group Call number allocation process in the VLR. The process starts with an oval connector, leading to an 'Idle' state. It then enters an 'Allocate Group Call number' process, followed by a decision 'Group Call number available'. If 'no', it goes to 'error: No Group Call number available' and then to a 'negative response' state, returning to 'Idle'. If 'yes', it proceeds to 'select Group Call number', 'mark number as allocated', and 'positive response' state. From 'positive response', it goes to 'start supervision timer' and 'wait for removal'. From 'wait for removal', it can either 'Release Group Call number' (leading to 'stop timer' and 'mark number as free') or encounter a 'time out' (leading to 'ABORT' and 'to relay MSC'). Both 'stop timer' and 'mark number as free' lead to the final 'Idle' state.](d04c50badc78d5ba47bf4e352af4a754_img.jpg) + +Process VLR 1(1) + +``` +graph TD; Start([ ]) --> Idle1([Idle]); Idle1 --> Allocate{Allocate Group Call number}; Allocate --> Decision{Group Call number available}; Decision -- no --> Error[error: No Group Call number available]; Error --> NegativeResponse{negative response}; NegativeResponse --> Idle2([Idle]); Decision -- yes --> Select[select Group Call number]; Select --> MarkAllocated[mark number as allocated]; MarkAllocated --> PositiveResponse{positive response}; PositiveResponse --> StartTimer[start supervision timer]; StartTimer --> WaitRemoval[wait for removal]; WaitRemoval --> Release{Release Group Call number}; WaitRemoval --> Timeout{time out}; Release --> StopTimer[stop timer]; StopTimer --> MarkFree[mark number as free]; MarkFree --> Idle3([Idle]); Timeout --> Abort{ABORT}; Abort -.-> ToRelayMSC[to relay MSC]; Abort --> MarkFree; +``` + +Flowchart of the Group Call number allocation process in the VLR. The process starts with an oval connector, leading to an 'Idle' state. It then enters an 'Allocate Group Call number' process, followed by a decision 'Group Call number available'. If 'no', it goes to 'error: No Group Call number available' and then to a 'negative response' state, returning to 'Idle'. If 'yes', it proceeds to 'select Group Call number', 'mark number as allocated', and 'positive response' state. From 'positive response', it goes to 'start supervision timer' and 'wait for removal'. From 'wait for removal', it can either 'Release Group Call number' (leading to 'stop timer' and 'mark number as free') or encounter a 'time out' (leading to 'ABORT' and 'to relay MSC'). Both 'stop timer' and 'mark number as free' lead to the final 'Idle' state. + +Figure 12: The Group Call number allocation process in the VLR + +## 11.8 Functional requirement of SMS Gateway MSC + +### SM MT delivery + +When receiving a short message TPDU from the SC, the SMS-GMSC shall inspect the parameters and identify the group call reference. + +NOTE: The SMS-GMSC may be identical to the MSC. + +If the parameters are incorrect then the SMS-GMSC shall return the appropriate error information to the SC in a failure report (see clauses 9 and 10 of 3GPP TS23.040 [14]). + +If no errors are found within the parameters the SMS-GMSC shall send the MT\_ForwardSM\_For\_VGCS\_REQ message to transfer the received short message to the anchor MSC or anchor MSC redundancy pool using the routing information derived from the group call reference. + +If the SMS-GMSC receives the MT\_ForwardSM\_For\_VGCS\_RES message indicating the voice group call is established and including a list of identities of dispatchers, it may optionally initiate point-to-point short message transfer attempts to the dispatchers who are connected to the voice group call. + +If the SMS-GMSC receives the MT\_ForwardSM\_For\_VGCS\_RES message indicating the voice group call is not established, it shall either + +- i) discard the short message and return the appropriate error information to the SC, or +- ii) initiate point to point short message transfer attempts to the members of the group. + +NOTE: How the routing information of the voice group call subscribers for the point to point SMS transfer can be derived from the group call reference is out of scope of this specification and implementation dependent. This can be achieved e.g. by an internal or external database. + +![Flowchart of the process in the SMS-GMSC. It starts with an initial state, goes to Idle, receives an SMS to group, forwards it to AMSC, waits for a response, receives an acknowledgment, checks for dispatcher identities, and then either interrogates the HLR or goes Idle based on whether it's a mobile or fixed line dispatcher.](199a8b4c5c620006757a17e930769566_img.jpg) + +**Process SMS\_to\_VGCS\_in\_SMS\_GMSC** 1(1) + +``` +graph TD; Start([ ]) --> Idle1([Idle]); Idle1 --> SMS_Received{SMS to group received}; SMS_Received --> Forward_SMS[Forward SMS to AMSC]; Forward_SMS -.-> Send_MT_Forward_SMS[Send MT_Forward_SMS_for_VGCS]; Forward_SMS --> Wait_Response[Wait for A-MSC response]; Wait_Response --> MT_Forward_SMS_Res{MT_Forward_SMS_for_VGCS_Res}; MT_Forward_SMS_Res -.-> Receive_AMSC[Receive AMSC acknowledge and dispatcher identities]; MT_Forward_SMS_Res --> Dispatcher_Received{Dispatcher identities received}; Dispatcher_Received -- no --> Idle2([Idle]); Dispatcher_Received -- yes --> Mobile_Dispatcher{Mobile dispatcher}; Mobile_Dispatcher -- no --> Fixed_Line[Fixed line dispatcher out of scope of 3GPP]; Mobile_Dispatcher -- yes --> Interrogate_HLR[Interrogate HLR and send SMS]; Interrogate_HLR -.-> According_to_3GPP[according to 3GPP TS23.040]; Interrogate_HLR --> Idle3([Idle]); Fixed_Line --> Idle4([Idle]); +``` + +Flowchart of the process in the SMS-GMSC. It starts with an initial state, goes to Idle, receives an SMS to group, forwards it to AMSC, waits for a response, receives an acknowledgment, checks for dispatcher identities, and then either interrogates the HLR or goes Idle based on whether it's a mobile or fixed line dispatcher. + +Figure 13: The process in the SMS-GMSC (sheet 1 of 1) + +# 12 Content of messages + +This clause specifies the content of the following messages: + +On the B-interface (MSC-VLR): + +- Allocate Group Call Number; +- Allocate Group Call Number ack; +- Allocate Group Call Number negative response; +- Release Group Call Number; +- Send Group Call Info; +- Send Group Call Info ack; +- Send Group Call Info negative response. + +On the E-interface (MSC-MSC): + +- Prepare Group Call; +- Prepare Group Call ack; +- Prepare Group Call negative response; +- Send Group Call End Signal; +- Forward Group Call Signalling; +- Process Group Call Signalling; +- Send Group Call Info; +- Send Group Call Info ack; +- Send Group Call Info negative response. + +On the I-interface (MSC-GCR): + +- GCR Interrogation; +- GCR Interrogation ack; +- GCR Interrogation negative response; +- Call Released. + +On the GCR-GCR-interface: + +- Sync GCR ; +- Sync GCR ack; +- Sync GCR negative response. + +In the tables which follow, information elements are shown as mandatory (M), conditional (C) or optional (O). A mandatory information element shall always be present. A conditional information element shall be present if certain conditions are fulfilled; if those conditions are not fulfilled it shall be absent. An optional element may be present or absent, at the discretion of the application at the sending entity. + +## 12.1 Messages on the B-interface (MSC-VLR) + +### 12.1.1 Allocate Group Call Number + +No information element is required. + +### 12.1.2 Allocate Group Call Number ack + +The following information element is required. + +| Information element name | Required | Description | +|--------------------------|----------|------------------------------------------------------------------------------| +| Group Call number | M | E.164 number required to route the call from the anchor MSC to the relay MSC | + +### 12.1.3 Allocate Group Call Number negative response + +The negative response information element can takes the following value: + +- No Group Call number available. + +### 12.1.4 Release Group Call Number + +The following information element is required. + +| Information element name | Required | Description | +|--------------------------|----------|------------------------------------------------------------------------------| +| Group Call number | M | E.164 number required to route the call from the anchor MSC to the relay MSC | + +### 12.1.5 Send Group Call Info + +The following information elements are required. + +| Information element name | Required | Description | +|--------------------------|----------|-------------------------------------------------------------------------| +| TMSI | M | TMSI of the service subscriber for whom the request is sent | +| Group ID | M | see clause 9. | +| Teleservice | M | The teleservice Voice Group Call indicates that the request is for VGCS | + +### 12.1.6 Send Group Call Info ack + +The following information elements are required. + +| Information element name | Required | Description | +|--------------------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | M | IMSI of the service subscriber for whom the request is sent | +| Additional info | C | Must be present if VGCS additional info is supported and additional info is assigned to the subscriber. | +| Additional subscriptions | C | Must be present if privilegedUplinkRequest , emergencyUplinkRequest or emergencyReset is subscribed by the service subscriber for whom the message is sent | + +### 12.1.7 Send Group Call Info negative response + +The negative response information element can take the following value: + +- group Id not subscribed; +- unknown subscriber. + +## 12.2 Messages on the E-interface (MSC-MSC) + +### 12.2.1 Prepare Group Call + +The following information elements are required. + +| Information element name | Required | Description | +|----------------------------------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| Teleservice | M | The teleservice Voice Group Call indicates that a VGCS call has to be prepared | +| Group call reference | M | see clause 9 | +| Cipher Algorithm, Group Key and Number | M | Information on the cipher algorithm and group key to be used | +| Priority | C | The default priority level must be present if eMLPP applies | +| Codec Info | M | Information on the codecs allowed for the VGCS call | +| Talker channel parameter | O | Indicates whether the network shall always establish and maintain a dedicated channel for the talking service subscriber | +| Uplink Reply Indicator | O | Indicates that the uplink reply procedure is applicable for the voice group call. Must be present if the GCR provides the corresponding information. | + +### 12.2.2 Prepare Group Call ack + +The following information element is required. + +| Information element name | Required | Description | +|--------------------------|----------|------------------------------------------------------------------------------| +| Group Call number | M | E.164 number required to route the call from the anchor MSC to the relay MSC | + +### 12.2.3 Prepare Group Call negative response + +The negative response information element can take the following value: + +- No Group Call number available. + +### 12.2.4 Send Group Call End Signal + +The following information element is required. + +| Information element name | Required | Description | +|--------------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | C | The IMSI of the service subscriber who has initiated the call. Must be present if the call was initiated by a service subscriber in the relay MSC area | +| Talker priority | C | Must be present if the call was set up by a service subscriber in the relay MSC area with a talker priority higher than "normal subscriber" | +| Additional info | C | Must be present if VGCS additional info is supported and additional info is assigned to the currently talking service subscriber in the relay MSC area. | + +### 12.2.5 Forward Group Call Signalling + +The following information elements are required. + +| Information element name | Required | Description | +|-------------------------------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | C | IMSI of the service subscriber who has initiated the call. Must be present if the message is used to transfer the IMSI to the relay MSC | +| Uplink Request Acknowledgement flag | C | Must be present if the message is used as positive acknowledgement of an uplink request | +| Uplink Release Indication flag | C | Must be present if the message is used to indicate to the relay MSC that the uplink is no longer busy | +| Uplink Reject Command flag | C | Must be present if the message is used as negative acknowledgement of an uplink request | +| Uplink Seized Command flag | C | Must be present if the message is used to indicate to the relay MSC that the uplink has become busy | +| Uplink Release Command flag | C | Must be present if the message is used to indicate to the relay MSC that the uplink which is currently under control of the relay MSC has to be released | +| State Attributes | C | Must be present if the message is used to indicate to the relay MSC that the downlink for a talker served by the relay MSC has to be muted or unmuted. | +| Talker priority | C | Must be present in the same message as the Uplink Request Acknowledgement flag or Uplink Seized Command flag and is set to the talker priority of the new talking service subscriber, if this talker priority is higher than "normal subscriber".
Must be present in the same message as the Uplink Reject Command flag and is set to the talker priority of the currently talking service subscriber, if this talker priority is higher than "normal subscriber". | +| Additional info | C | Must be present if VGCS additional info is supported and the message is used to transfer additional info assigned to the currently talking service subscriber to the relay MSC.

Must be present in the same message as the Uplink Request Acknowledgement flag, Uplink Reject Command flag, or Uplink Seized Command flag, if a talker priority is included in the same message. | +| Emergency Mode Reset Command flag | C | Must be present if the message is used to indicate to the relay MSC that the emergency mode indication shall no longer be signalled | +| SM TPDU | C | The short message transfer protocol data unit received from the Service Centre. Must be present if the message is used to transfer the short message TPDU received from the SC. | +| Notification Data | C | Must be present if the message is used to indicate to the relay MSC that application-specific data shall be distributed in its area | + +### 12.2.6 Process Group Call Signalling + +The following information elements are required. + +| Information element name | Required | Description | +|-----------------------------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Uplink Request flag | C | Must be present if the message is used to request uplink control from the anchor MSC | +| Uplink Release Indication flag | C | Must be present if the message is used to indicate to the anchor MSC that the uplink has become free | +| Talker priority | C | Must be present in the same message as the Uplink Request flag or Uplink Release Indication flag and is set to the talker priority of the service subscriber requesting or releasing the uplink, if this talker priority is higher than "normal subscriber" | +| Additional info | C | Must be present if VGCS additional info is supported and the message is used to transfer additional info assigned to the currently talking service subscriber to the anchor MSC.

Must be present in the same message as the Uplink Request flag, if the flag applies to a subscriber with a talker priority higher than "normal subscriber" | +| Emergency Mode Reset Command flag | C | Must be present if the message is used to indicate to the anchor MSC that the emergency mode indication shall no longer be signalled | +| Release Group Call flag | C | Must be present if the message is used to indicate to the anchor MSC that the VGCS call shall be released | +| Notification Data | C | Must be present if the message is used to indicate to the anchor MSC that application-specific data shall be distributed | + +### 12.2.7 MT Forward Short Message for VGCS Request + +The following information elements are required. + +| Information element name | Required | Description | +|--------------------------|----------|-------------------------------------------------------------------------------------| +| Group call reference | M | see clause 9 | +| SM Originating Address | M | The originating address used by the short message service relay sub-layer protocol. | +| SM TPDU | M | The short message transfer protocol data unit received from the Service Centre. | + +### 12.2.8 MT Forward Short Message for VGCS Response + +The following information elements are required. + +| Information element name | Required | Description | +|--------------------------------|----------|----------------------------------------------------------------| +| Status of the voice group call | M | Indicating whether the voice group call is established or not. | +| Dispatcher List | O | A list of dispatcher identities received from the GCR. | + +### 12.2.9 Send Group Call Info + +The following information elements are required. + +| Information element name | Required | Description | +|--------------------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Teleservice | M | The teleservice Voice Group Call indicates that the request is for VGCS | +| Requested Info | M | Indicates whether
a) IMSI, Additional Info, and Additional Subscriptions or
b)Anchor MSC Address and Group CallReference
are requested | +| TMSI | C | TMSI of the service subscriber for whom the request is sent.
Shall be present if IMSI, Additional Info and Additional Subscriptions are requested. | +| Group ID | M | see clause 9. | +| Cell Id | C | Identification of the cell where the group call initiating service subscriber is located.
Shall be present if Anchor MSC Address and Group Call Reference are requested | +| IMSI | C | IMSI of the service subscriber for whom the request is sent.
Shall be present if Anchor MSC Address and Group Call Reference are requested | +| Additional info | C | Shall be present if subscribed and if Anchor MSC Address and Group Call Reference are requested | +| Talker priority | C | Shall be present if Anchor MSC Address and Group Call Reference are requested and the talker priority is higher than "normal subscriber" | + +### 12.2.10 Send Group Call Info ack + +The following information elements are required. + +| Information element name | Required | Description | +|--------------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | C | IMSI of the service subscriber for whom the request is sent.
Shall be present if it was requested. | +| Additional info | C | Shall be present if requested and VGCS additional info is supported and additional info is assigned to the subscriber. | +| Additional subscriptions | C | Shall be present if requested and privilegedUplinkRequest , emergencyUplinkRequest or emergencyReset is subscribed by the service subscriber for whom the message is sent | +| Anchor MSC Address | C | E.164 number required to route the call from the VMSC to the anchor MSC. Shall be present if requested | +| Group call reference | C | see clause 9. Shall be present if requested. | + +### 12.2.11 Send Group Call Info negative response + +The negative response information element can take the following value: + +- group Id not subscribed; +- unknown subscriber; +- ongoing call; +- failure. + +## 12.3 Messages on the I-interface (MSC-GCR) + +### 12.3.1 GCR Interrogation + +The following information elements are required. + +| Information element name | Required | Description | +|----------------------------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Group call reference | C | see clause 9. Must be present if the VGCS call was initiated by a dispatcher or by a service subscriber in the relay MSC area and the receiving GCR is associated to the anchor MSC, or if the receiving GCR is associated to a relay MSC and the GCR interrogation was triggered by a Prepare Group Call message received from the anchor MSC. | +| Group ID | C | see clause 9. Must be present if one of the following conditions is fulfilled:
1) the MSC is the visited MSC of the service subscriber initiating the VGCS call, except if the MSC is a relay MSC and the GCR interrogation was triggered by a Prepare Group Call message received from the anchor MSC;
2) the GCR interrogation was triggered by a Send Group Call Info message received from the VMSC. | +| Originating Cell ID | C | see clause 9. Must be present if one of the following conditions is fulfilled:
1) the MSC is the visited MSC of the service subscriber initiating the VGCS call, except if the MSC is a relay MSC and the GCR interrogation was triggered by a Prepare Group Call message received from the anchor MSC;
2) the GCR interrogation was triggered by a Send Group Call Info message received from the VMSC. | +| CLI | C | Calling Line Identity of the initiating dispatcher, or VGCS prefix plus group call reference in case of service subscriber originated VGCS call in the relay MSC, . Must be present if the MSC is not the visited MSC of the service subscriber initiating the VGCS call. | +| Relay MSC indicator | M | A flag indicating whether the GCR interrogation was triggered from a Prepare Group Call message received from the anchor MSC | +| Group Call Serving MSC indicator | C | A flag indicating whether the GCR interrogation was triggered from a Send Group Call Info message received from the VMSC. May be set to "yes" in a RANflex configuration (with or without group call redundancy) only. | +| IMSI | C | IMSI of the service subscriber who has initiated the VGCS call. Must be present if the MSC is the visited MSC of the service subscriber initiating the VGCS call, or the GCR interrogation was triggered by a Send Group Call Info message received from the VMSC | +| Talker priority | C | Talker priority of the service subscriber who has initiated the VGCS call. Must be present if the MSC is the visited MSC of the service subscriber initiating the VGCS call, or the GCR interrogation was triggered by a Send Group Call Info message containing a talker priority received from the VMSC | +| Additional info | C | Additional info of the service subscriber who has initiated the VGCS call. Must be present if the MSC is the visited MSC of the service subscriber initiating the VGCS call, or the GCR interrogation was triggered by a Send Group Call Info message containing additional info received from the VMSC | +| Uplink Reply Indicator | O | Indicates that the uplink reply procedure is applicable for the voice group call. Must be present if the MSC is the anchor MSC and the related flag exists and is set in the GCR | +| Ongoing Call Override Indication | C | Indicates that the GCR shall delete any ongoing call information before processing the request. May be set to "yes" in a RANflex configuration with group call redundancy only. | + +### 12.3.2 GCR Interrogation ack + +The following information elements are required. + +| Information element name | Required | Description | +|------------------------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Group call reference | C | Must be present if the GCR receives an interrogation request containing a Group ID and an Originating Cell ID. | +| Cell List | C | A list of cells inside the MSC area into which the call is to be sent. Must be present if a) no anchor MSC address is present in the group call reference record and the GCR interrogation was not triggered by a Send Group Call Info message, or b) the relay MSC indicator was set in the GCR Interrogation message | +| Anchor MSC Address | C | E.164 number required to route the call from the relay MSC and in a RANflex configuration (with or without group call redundancy) from the VMSC to the anchor MSC. Must be present if the anchor MSC Address is present in the group call reference record | +| Relay MSC List | C | A list of relay MSCs into which the call is to be sent. Must be present if a relay MSC list is present in the group call reference record and the GCR interrogation was not triggered by a Send Group Call Info message | +| Group Key and Number | C | Information on the cipher algorithm and the group key to be used. Must be present if Group Key and Number is present in the group call reference record and the GCR interrogation was not triggered by a Send Group Call Info message | +| Codec Information | C | Information on the codecs allowed for the voice broadcast call. Must be present if Codec Info is present in the group call reference record and the GCR interrogation was not triggered by a Send Group Call Info message | +| Establish to Dispatcher List | C | A list of identities of dispatchers to which a dedicated link is to be established. Must be present if included in the group call reference record. Note that the CLI possibly received with the GCR interrogation message must not be included | +| Release from Dispatcher List | C | A list of identities of dispatchers which are allowed to terminate the voice group call. Must be present if included in the group call reference record and the GCR interrogation was not triggered by a Send Group Call Info message | +| Priority | C | The default priority level related to the voice group call if eMLPP applies. Must be present if included in the group call reference record and the GCR interrogation was not triggered by a Send Group Call Info message | +| IMSI | C | IMSI of the service subscriber who has initiated the VGCS call. Must be present if the Relay MSC Indicator was set in the GCR interrogation message and the IMSI is present in the group call reference record | +| No Activity Time | C | The length of the time over which no activity is detected before the voice group call is automatically terminated | +| Talker priority | C | Talker priority of the service subscriber who has initiated the VGCS call. Must be present if talker priority is present in the group call reference record | +| Additional info | C | Additional Info of the service subscriber who has initiated the VGCS call. Must be present if additional info is present in the group call reference record | +| Originating Cell ID | C | Must be present if originating cell id is present in the group call reference record | +| Talker channel parameter | O | Indicates whether the network shall always establish and maintain a dedicated channel for the talking service subscriber | + +### 12.3.3 GCR interrogation negative response + +The negative response information element can take the following values: + +- on-going call. In a RANflex configuration with group call redundancy the MSC address of the MSC within the redundancy pool at which the group call is ongoing shall be present in the negative response; and +- failure. + +### 12.3.4 Call released + +The following information element is required. + +| Information element name | Required | Description | +|--------------------------|----------|--------------| +| Group call reference | M | see clause 9 | + +### 12.3.5 GCR SMS Interrogation + +The following information element is required. + +| Information element name | Required | Description | +|--------------------------|----------|--------------| +| Group call reference | M | see clause 9 | + +### 12.3.6 GCR SMS Interrogation Response + +The following information elements are required. + +| Information element name | Required | Description | +|--------------------------------|----------|------------------------------------------------------------------------------------------------------------------------------------------| +| Status of the voice group call | M | Indicating whether the voice group call is established or not. | +| MSC Address | C | In a RANflex configuration with group call redundancy: Address of the MSC within the redundancy pool at which the group call is ongoing. | +| Dispatcher List | O | A list of identities of dispatchers connected to an established voice group call. | + +## 12.4 Messages on the GCR - GCR interface + +### 12.4.1 Sync GCR + +The following information elements are required. + +| Information element name | Required | Description | +|----------------------------|----------|--------------------------------------------------------------------------------------------------------------------| +| Teleservice | M | The teleservice Voice Group Call indicates that a VGCS call has to be prepared | +| Group call reference | M | see clause 9 | +| Initial Talker Information | C | see subclause 8.1.3.2 | +| on-going indication | C | indicates by its presence that the group call is ongoing | +| MSC Address | C | Address of the sending GCR's associated MSC, at which the group call is ongoing. | +| call released indication | C | indicates by its presence that the group call is no longer ongoing. | +| override indication | C | indicates by its presence that the receiving GCR shall replace the stored MSC-Address with the received value. | +| request indication | C | indicated by its presence that the sending GCR requests ongoing information and MSC Address from the receiving GCR | + +### 12.4.2 Sync GCR ack + +The following information elements are required. + +| Information element name | Required | Description | +|--------------------------------|----------|----------------------------------------------------------------| +| Status of the voice group call | C | Indicating whether the voice group call is established or not. | +| MSC Address | C | Address of the MSC, at which the group call is ongoing. | +| Initial Talker Information | C | see subclause 8.1.3.2 | + +### 12.4.3 Sync GCR negative response + +The negative response information element can take the following values: + +- on-going call. The MSC address of the MSC within the redundancy pool at which the group call is ongoing shall be present in the negative response; +- initial talker information; and +- failure. + +# 13 List of system parameters + +## 13.1 Timers + +### 13.1.1 Txx + +This is a supervision timer on the anchor MSC for the setup of the voice group call. It is started on receipt of a SETUP message from the calling subscriber when the calling subscriber is in the anchor MSC area and on receipt of an ISUP IAM from the relay MSC when the calling subscriber is in the relay MSC area. Refer to subclause 11.3.1.1.2 for procedures on expiry. + +The value of timer Txx is operator specific. + +### 13.1.2 T1 + +In a network supporting talker priorities or uplink access option (i) as defined in subclause 7.2, the uplink busy message on the FACCH of the voice group call channel downlink is repeated by the BSS every T1 seconds (see subclause 11.3.7.1). + +The value of timer T1 is operator specific. Its default value is 5 seconds. + +### 13.1.3 T2 + +In a network supporting the transmission of additional subscriber-related information, the additional info message on the SACCH of the voice group call channel downlink is repeated by the BSS every T2 seconds, until the current talker releases the uplink or is released by the network (see subclause 11.3.7.1). + +The value of timer T2 is operator specific. Its default value is 5 seconds. + +### 13.1.4 Tbb + +In a network supporting validation of Priority Uplink Requests, the timer Tbb supervises the broadcast of a new token (Y) after a valid Priority Uplink Request has been received. + +If a Priority Uplink Request is received, and the token matches the token in the BSS (X) then the request is accepted, token X is invalidated and Tbb is started. On Tbb expiry a new token (Y), and the priority of the accepted request, is sent in the uplink busy message on the FACCH of the voice group call channels. The Tbb timer should be set to a value + +that allows other service subscribers who sent a Priority Uplink Request with token X, at the same time as the one accepted by the network, to be back on the voice group call channel in order to receive the new token (Y). + +The default value for Tbb is 500ms.. + +### 13.1.5 Ttv + +In a network supporting validation of Priority Uplink Requests, the timer Ttv supervises an additional validity period for an unused token (A). When T1 (supervising the periodic uplink busy) expires a new token (B) is sent in the uplink busy message on the FACCH of the voice group call channels and timer Ttv is started. If a Priority Uplink Request is received before Ttv expires and the token matches either token in the BSS (A or B), the request is considered to be valid, both tokens (A and B) in the BSS are invalidated and Ttv is stopped. If Ttv expires (i.e. no valid Priority Uplink Request has been received within Ttv seconds) the unused token (A) is invalidated. + +The value of timer Ttv is operator specific. The value chosen should allow for the reception of requests from service subscribers who have left the group call channel before receipt of the UPLINK\_BUSY with new token (B). Its default value is 1s. + +### 13.1.6 Tast + +In a network supporting A-interface link sharing timer Tast shall be used to measure the duration between periodic reports from the BSC to the MSC of Group Call Area cells for which channels have been assigned or released, pre-empted or failed since the last periodic report. When timer Tast expires, if new cells in the Group Call Area have been established or existing ones have been released, pre-empted or failed, the MSC shall be informed of the changes (see subclause 7.1b). If no changes have occurred nothing shall be sent. Timer Tast shall be restarted to measure the period of time until the next report. The timer shall be stopped when the call is released. + +The value of timer Tast is operator specific. Its default value is 5 seconds. + +### 13.1.7 T3 + +In a RANflex configuration the group call serving MSC when receiving Send Group Call Info from the VMSC shall supervise the setup of the group call by timer T3. T3 is started when a positive Send Group Call Info result is returned to the VMSC and it is stopped when the group call is set up. At timeout the temporarily stored transient data are deleted from the GCR. + +In a RANflex configuration with group call redundancy T3 shall be implemented in the GCR instead of in the MSC. T3 is started when initial talker information is stored and stopped when initial talker information is deleted. At timeout initial talker information is deleted from the GCR. + +The value of timer T3 is operator specific. Its default value is 5 seconds. + +## --- Annex A (informative): Change History + +| TSG# | TSG doc | WG doc | Spec | CR | R ev | Ph | C at | Old vers | New vers | Title | WI | +|-----------|---------------------|-----------|----------------|------|------|-------|------|--------------|---------------|--------------------------------------------------------------------------------------------------------------------------------------|------------| +| S#31 | | Feb 2000 | 03.68 | | | | | | 8.0.0 | Specification version upgrade to Release 1999 version 8.0.0 | | +| CN#7 | email before SMG#32 | Apr 2000 | 03.68 | A017 | | R99 | | 8.0.0 | 8.1.0 | VGCS Signalling Flows | ASCI | +| CN#7 | email before SMG#32 | Apr 2000 | 03.68 | A019 | | R99 | | 8.0.0 | 8.1.0 | Data Flow for Fast Call setup | ASCI | +| CN#7 | email before SMG#32 | Apr 2000 | 03.68 | A022 | | R99 | | 8.0.0 | 8.1.0 | Recommendation to use DTMF tones for VGCS talking subscriber downlink un-muting | ASCI | +| S#32C N#8 | NP-000275 | N1-000738 | 03.68 | A024 | | R99 | F | 8.1.0 | 8.2.0 | Call Release clarification at the Relay MSC | ASCI | +| S#32C N#8 | NP-000275 | N1-000739 | 03.68 | A025 | | R99 | F | 8.1.0 | 8.2.0 | Speech transmission architecture clarification | ASCI | +| S#32C N#8 | NP-000275 | N1-000740 | 03.68 | A026 | | R99 | D | 8.1.0 | 8.2.0 | Clarification of anchor MSC address format | ASCI | +| S#32C N#8 | NP-000276 | N1-000676 | 03.68 | A023 | | R4 | B | 8.2.0 | 9.0.0 | Introduction of Originator-to-dispatcher information into VGCS | ASCI | +| S#32C N#8 | NP-000276 | N1-000767 | 03.68 | A027 | | R4 | F | 8.2.0 | 9.0.0 | VGCS service accessibility | ASCI | +| S#32C N#8 | NP-000276 | N1-000769 | 03.68 | A028 | | R4 | C | 8.2.0 | 9.0.0 | talker outside Group Call Area | ASCI | +| S#32C N#8 | NP-000276 | N1-000771 | 03.68 | A029 | | R4 | F | 8.2.0 | 9.0.0 | Notification response & uplink reply procedure definition | ASCI | +| S#32C N#8 | NP-000276 | N1-000773 | 03.68 | A030 | | R4 | F | 8.2.0 | 9.0.0 | Release dataFlow correction | ASCI | +| | | | 03.68 / 43.068 | | | | | 03.68 v9.0.0 | 43.068 v4.0.0 | Conversion to 3GPP TS format | - | +| CN#9 | NP-000449 | N1-000873 | 43.068 | 001 | | R4 | F | 4.0.0 | 4.1.0 | Uplink Release dataFlow correction | ASCI | +| CN#9 | NP-000449 | N1-000915 | 43.068 | 002 | | R4 | F | 4.0.0 | 4.1.0 | Correction in the Notification procedure | ASCI | +| CN#9 | NP-000449 | N1-000918 | 43.068 | 003 | | R4 | B | 4.0.0 | 4.1.0 | Identification of Group ID - The longest GID has to be matched | ASCI | +| Oct 2000 | | | | | | | | 4.1.0 | 4.1.1 | GSM references revert to pre-Release-4 spec number format. | | +| NP-10 | NP-000667 | N1-001171 | 43.068 | 004 | | Rel-4 | F | 4.1.1 | 4.2.0 | Call Waiting is not applicable to an originator/talker in dedicated mode | ASCI | +| NP-10 | NP-000667 | N1-001181 | 43.068 | 005 | | REL-4 | F | 4.1.1 | 4.2.0 | Wrong Field Name for OTDI | ASCI | +| NP-10 | NP-000667 | N1-001401 | 43.068 | 006 | 1 | REL-4 | F | 4.1.1 | 4.2.0 | DTMF precision | ASCI | +| | | | 43.068 | | | Rel-4 | | 4.2.0 | 4.2.1 | ETSI/MCC cleanup on references and editorials (version 4.2.1 was never issued in 2000-12, but 4.2.0 was the correct from the DBase). | 05.05.2002 | +| NP-16 | | | 43.068 | | | Rel-5 | | 4.2.1 | 5.0.0 | CN plenary decision to make this TS also for Release 5. | June 2002 | +| | | | 43.068 | | | Rel-5 | | 5.0.0 | 5.0.1 | Editorial correction, changing Note 1 to 15 and Note 2 to 16 in fig. 7, subclause 11.3.8. | 27.06.2002 | +| NP-17 | NP-020383 | N1-021687 | 43.068 | 007 | | Rel-5 | F | 5.0.1 | 5.1.0 | ASCI VGCS call termination by dispatchers using DTMF | Sept 2002 | +| NP-18 | NP-020675 | | 43.068 | 008 | 4 | Rel-5 | F | 5.1.0 | 5.2.0 | MS late entry notification | Dec 2002 | +| NP-21 | NP-030408 | N1-031204 | 43.068 | 010 | 1 | Rel-5 | A | 5.2.0 | 5.3.0 | Correction of uplink release management | Sept 2003 | +| NP-21 | NP-030407 | N1-031210 | 43.068 | 012 | 1 | Rel-5 | A | 5.2.0 | 5.3.0 | Correction to definition of Group-ID, Group call area ID and Group Call Reference | Sept 2003 | +| NP-21 | NP-030409 | N1-031217 | 43.068 | 013 | 1 | Rel-5 | F | 5.2.0 | 5.3.0 | Correction to MS Late Entry description | Sept 2003 | + +| | | | | | | | | | | | | +|-------|-----------|-----------|--------|------|---|-------|---|-------|-------|-----------------------------------------------------------------------------------------------------------------------------|------------| +| NP-21 | NP-030410 | N1-031332 | 43.068 | 014 | 2 | Rel-6 | F | 5.3.0 | 6.0.0 | Dispatcher signalled mute/unmute of talkers downlink and correction and update of incorrect implementation of CR 03.68 A022 | Sept 2003 | +| NP-24 | NP-040203 | N1-041073 | 43.068 | 016 | 1 | Rel-6 | F | 6.0.0 | 6.1.0 | Correction of PCH re-organization notification | June 2004 | +| NP-25 | NP-040373 | N1-041527 | 43.068 | 019 | 1 | Rel-6 | A | 6.1.0 | 6.2.0 | Correction on notification for first talker of VGCS call | Sept 2004 | +| NP-25 | NP-040329 | N1-041547 | 43.068 | 020 | 1 | Rel-6 | B | 6.1.0 | 6.2.0 | Introduction of USIM based ciphering for VGCS | Sept 2004 | +| NP-26 | NP-040515 | N1-042061 | 43.068 | 021 | 1 | Rel-6 | C | 6.2.0 | 6.3.0 | Addition of VGCS reconfiguration procedure | Dec 2004 | +| NP-26 | NP-040515 | N1-042075 | 43.068 | 022 | 2 | Rel-6 | F | 6.2.0 | 6.3.0 | Group Call Reference handling by the MSC during VGCS call establishment | Dec 2004 | +| NP-26 | NP-040515 | N1-041768 | 43.068 | 023 | | Rel-6 | D | 6.2.0 | 6.3.0 | Notification Response procedure | Dec 2004 | +| NP-26 | NP-040515 | N1-041769 | 43.068 | 024 | | Rel-6 | D | 6.2.0 | 6.3.0 | Clarification on Immediate Setup procedure | Dec 2004 | +| NP-26 | NP-040515 | N1-041803 | 43.068 | 027 | | Rel-6 | B | 6.2.0 | 6.3.0 | USIM based ciphering on dedicated channels | Dec 2004 | +| NP-27 | NP-050067 | N1-050043 | 43.068 | 031 | | Rel-6 | A | 6.3.0 | 6.4.0 | Correction of the conditions for establishment of a voice group call | March 2005 | +| NP-27 | NP-050076 | N1-050281 | 43.068 | 036 | 1 | Rel-6 | F | 6.3.0 | 6.4.0 | EPRT Inter-PLMN Group Call notification for dispatchers | March 2005 | +| CP-28 | CP-050057 | C1-050469 | 43.068 | 041 | | Rel-6 | A | 6.4.0 | 6.5.0 | Correction on the use of calling subscriber and destination subscriber | June 2005 | +| CP-28 | CP-050073 | C1-050722 | 43.068 | 028 | 3 | Rel-7 | B | 6.5.0 | 7.0.0 | Support of talker priorities and talker identity presentation | June 2005 | +| CP-28 | CP-050073 | C1-050742 | 43.068 | 043 | 2 | Rel-7 | B | 6.5.0 | 7.0.0 | VGCS Broadcast Point in the BSS | June 2005 | +| CP-29 | CP-050361 | C1-051117 | 43.068 | 047 | 1 | Rel-7 | A | 7.0.0 | 7.1.0 | Error correction | Sept 2005 | +| CP-29 | CP-050361 | C1-050903 | 43.068 | 051 | | Rel-7 | A | 7.0.0 | 7.1.0 | Correction of USIM based ciphering on dedicated channels | Sept 2005 | +| CP-29 | CP-050365 | C1-051112 | 43.068 | 048 | 2 | Rel-7 | B | 7.0.0 | 7.1.0 | EFR for VGCS | Sept 2005 | +| CP-29 | CP-050365 | C1-050901 | 43.068 | 049 | | Rel-7 | B | 7.0.0 | 7.1.0 | Delivery of information about the subsequent talker to the previous talker | Sept 2005 | +| CP-29 | CP-050365 | C1-051118 | 43.068 | 054 | 1 | Rel-7 | F | 7.0.0 | 7.1.0 | Correction on the uplink transmission management | Sept 2005 | +| CP-29 | CP-050365 | C1-050945 | 43.068 | 055 | | Rel-7 | F | 7.0.0 | 7.1.0 | Enhancement on the dedicated channel Assignment procedure | Sept 2005 | +| CP-29 | CP-050365 | C1-051120 | 43.068 | 058 | 1 | Rel-7 | B | 7.0.0 | 7.1.0 | Delivery of short message to voice group call | Sept 2005 | +| CP-30 | CP-050549 | C1-051580 | 43.068 | 060 | 1 | Rel-7 | B | 7.1.0 | 7.2.0 | VGCS A-interface link sharing | Dec 2005 | +| CP-30 | CP-050549 | C1-051583 | 43.068 | 063 | 1 | Rel-7 | B | 7.1.0 | 7.2.0 | AMR for VGCS | Dec 2005 | +| CP-30 | CP-050549 | C1-051692 | 43.068 | 059 | 2 | Rel-7 | B | 7.1.0 | 7.2.0 | Talker priority: Priority Uplink Request validation mechanism | Dec 2005 | +| CP-30 | CP-050549 | C1-051693 | 43.068 | 064 | 3 | Rel-7 | B | 7.1.0 | 7.2.0 | Point to point short message during an ongoing voice group call | Dec 2005 | +| CP-30 | CP-050549 | C1-051449 | 43.068 | 068 | | Rel-7 | D | 7.1.0 | 7.2.0 | Editorial corrections | Dec 2005 | +| CP-31 | CP-060123 | C1-060243 | 43.068 | 0069 | 1 | Rel-7 | F | 7.2.0 | 7.3.0 | Data confidentiality for p-t-p SMS in an active voice group call | March 2006 | +| CP-31 | CP-060122 | C1-060058 | 43.068 | 0070 | - | Rel-7 | B | 7.2.0 | 7.3.0 | Clarification of prefix for an SMS to an active voice group call | March 2006 | +| CP-31 | CP-060122 | C1-060108 | 43.068 | 0071 | 1 | Rel-7 | B | 7.2.0 | 7.3.0 | Enhanced support of AMR for VGCS | March 2006 | + +| | | | | | | | | | | | | +|-------|-----------|-----------|--------|------|---|-------|---|-------|-------|----------------------------------------------------------------------------------------------------------------------------------------------|------------| +| CP-31 | CP-060113 | C1-060496 | 43.068 | 0073 | 2 | Rel-7 | A | 7.2.0 | 7.3.0 | Correction of muting/un-muting procedure | March 2006 | +| CP-31 | CP-060122 | C1-060242 | 43.068 | 0074 | - | Rel-7 | B | 7.2.0 | 7.3.0 | Correction of the distribution of emergency indications | March 2006 | +| CP-31 | CP-060122 | C1-060545 | 43.068 | 0076 | 1 | Rel-7 | C | 7.2.0 | 7.3.0 | Modification of conditions for VGCS call establishment | March 2006 | +| CP-31 | CP-060122 | C1-060547 | 43.068 | 0078 | 1 | Rel-7 | F | 7.2.0 | 7.3.0 | Addition to group call SM procedures | March 2006 | +| CP-31 | CP-060122 | C1-060549 | 43.068 | 0080 | 1 | Rel-7 | F | 7.2.0 | 7.3.0 | EPRT - Corrections and clarifications to the procedures for releasing the calling service subscribers dedicated connection to the anchor MSC | March 2006 | +| CP-31 | CP-060122 | C1-060550 | 43.068 | 0081 | 1 | Rel-7 | F | 7.2.0 | 7.3.0 | EPRT - Correction/ clarification of voice group call termination procedures | March 2006 | +| CP-31 | CP-060122 | C1-060570 | 43.068 | 0082 | 2 | Rel-7 | F | 7.2.0 | 7.3.0 | Clarification of the no activity time | March 2006 | +| CP-31 | CP-060122 | C1-060566 | 43.068 | 0083 | 2 | Rel-7 | B | 7.2.0 | 7.3.0 | Indication of the channel to be used for uplink requests | March 2006 | +| | | | 43.068 | | | Rel-7 | | 7.3.0 | 7.3.1 | SDL source files updated | April 2006 | +| CP-32 | CP-060273 | C1-061101 | 43.068 | 0075 | 2 | Rel-7 | B | 7.3.1 | 7.4.0 | Addition of interoperability with RANflex | June 2006 | +| CP-32 | CP-060272 | C1-061103 | 43.068 | 0084 | 2 | Rel-7 | C | 7.3.1 | 7.4.0 | Optimized delivery of the additional information | June 2006 | +| CP-32 | CP-060272 | C1-060728 | 43.068 | 0085 | | Rel-7 | F | 7.3.1 | 7.4.0 | EPRT: Add signalling flow for a dispatcher originated VGCS | June 2006 | +| CP-32 | CP-060272 | C1-061100 | 43.068 | 0086 | 1 | Rel-7 | F | 7.3.1 | 7.4.0 | Group Call Re-establishment by the BSS | June 2006 | +| CP-32 | CP-060276 | C1-060982 | 43.068 | 0088 | 1 | Rel-7 | F | 7.3.1 | 7.4.0 | TC-RT Clarification on use of the Uplink Reply Procedure | June 2006 | +| CP-32 | CP-060272 | C1-060983 | 43.068 | 0089 | 1 | Rel-7 | B | 7.3.1 | 7.4.0 | Talker priority and A-interface link sharing interaction | June 2006 | +| CP-32 | CP-060276 | C1-060861 | 43.068 | 0094 | | Rel-7 | F | 7.3.1 | 7.4.0 | Correction of Figure 6 | June 2006 | +| CP-32 | CP-060272 | C1-060862 | 43.068 | 0095 | | Rel-7 | F | 7.3.1 | 7.4.0 | Correction of Figure 6a | June 2006 | +| CP-33 | CP-060464 | C1-061910 | 43.068 | 0097 | | Rel-7 | | 7.4.0 | 7.5.0 | Failure cases during VGCS call establishment | Sept 2006 | +| CP-33 | CP-060464 | C1-061503 | 43.068 | 0098 | | Rel-7 | | 7.4.0 | 7.5.0 | Common AMR configurations for VGCS and VBS | Sept 2006 | +| CP-33 | CP-060464 | C1-061819 | 43.068 | 0100 | | Rel-7 | | 7.4.0 | 7.5.0 | EVGCS-Remove the limitation of speech version in A interface sharing | Sept 2006 | +| CP-33 | CP-060464 | C1-061556 | 43.068 | 0103 | | Rel-7 | | 7.4.0 | 7.5.0 | Indicate the originating relay MSC address to anchor MSC | Sept 2006 | +| CP-33 | CP-060464 | C1-061908 | 43.068 | 0105 | | Rel-7 | | 7.4.0 | 7.5.0 | Extension of Group ID | Sept 2006 | +| CP-33 | CP-060464 | C1-061916 | 43.068 | 0110 | | Rel-7 | | 7.4.0 | 7.5.0 | Correction for radio resource assignment | Sept 2006 | +| CP-33 | CP-060470 | C1-061816 | 43.068 | 0096 | | Rel-7 | | 7.4.0 | 7.5.0 | Corrections to interoperability with RANflex | Sept 2006 | +| CP-34 | CP-060664 | C1-062423 | 43.068 | 0117 | 1 | Rel-7 | | 7.5.0 | 7.6.0 | Emergency set/reset alert to dispatchers | Dec 2006 | +| CP-34 | CP-060664 | C1-062420 | 43.068 | 0112 | 2 | Rel-7 | | 7.5.0 | 7.6.0 | Corrections to SMS procedures during ongoing voice group call | Dec 2006 | +| CP-34 | CP-060664 | C1-062424 | 43.068 | 0119 | 1 | Rel-7 | | 7.5.0 | 7.6.0 | Optimized channel allocation of the calling subscriber | Dec 2006 | +| CP-34 | CP-060664 | C1-062422 | 43.068 | 0116 | 1 | Rel-7 | | 7.5.0 | 7.6.0 | Clarifications to the case when a group ID with 8 digits is used | Dec 2006 | +| CP-34 | CP-060665 | C1-062111 | 43.068 | 0114 | - | Rel-7 | | 7.5.0 | 7.6.0 | Condition for the inclusion of parameters in the GCR interrogation message | Dec 2006 | +| CP-34 | CP-060665 | C1-062113 | 43.068 | 0115 | - | Rel-7 | | 7.5.0 | 7.6.0 | Addition of Teleservice Code to SendGroupCallInfo | Dec 2006 | +| CP-34 | CP-060672 | C1-062509 | 43.068 | 0118 | 1 | Rel-8 | | 7.6.0 | 8.0.0 | Introduction of sending application-specific data to group call members | Dec 2006 | +| CP-36 | CP-070371 | C1-070684 | 43.068 | 0133 | - | Rel-8 | A | 8.0.0 | 8.1.0 | TCRT: Definition of BSSAP procedure for release of VGCS call controlling connections | June 2007 | + +| | | | | | | | | | | | | +|-------|-----------|-----------|--------|------|---|--------|---|--------|--------|--------------------------------------------------------------------------------------------|----------------| +| CP-36 | | | | | | Rel-8 | | 8.0.0 | 8.1.0 | TCRT: Silent (re-)joining dispatcher, immediately talking dispatcher | June 2007 | +| | CP-070376 | C1-070973 | 43.068 | 0132 | 1 | | A | | | | | +| CP-36 | CP-070376 | C1-070975 | 43.068 | 0130 | 2 | Rel-8 | A | 8.0.0 | 8.1.0 | Retry of the VGCS Assignment procedure | June 2007 | +| CP-36 | CP-070387 | C1-070686 | 43.068 | 0135 | - | Rel-8 | A | 8.0.0 | 8.1.0 | Correction of condition for cell specific speech version | June 2007 | +| CP-36 | CP-070387 | C1-070685 | 43.068 | 0134 | - | Rel-8 | A | 8.0.0 | 8.1.0 | Alignment of SDLs with condition for successful call setup | June 2007 | +| CP-36 | | | | | | Rel-8 | | 8.0.0 | 8.1.0 | TCRT: Distribution of time-critical application data by BSC to its broadcast area | June 2007 | +| | CP-070394 | C1-071380 | 43.068 | 0140 | 3 | | B | | | | | +| CP-36 | CP-070394 | C1-071374 | 43.068 | 0138 | 3 | Rel-8 | C | 8.0.0 | 8.1.0 | Talker channel parameter | June 2007 | +| CP-36 | CP-070394 | C1-070755 | 43.068 | 0136 | - | Rel-8 | D | 8.0.0 | 8.1.0 | Correction of place of message flows for EVA | June 2007 | +| CP-37 | | | | | | Rel-8 | | 8.1.0 | 8.2.0 | Correction to the talker channel parameter | Sept 2007 | +| | CP-070602 | C1-072114 | 43.068 | 0142 | 2 | | F | | | | | +| CP-37 | CP-070604 | C1-071620 | 43.068 | 0141 | - | Rel-8 | F | 8.1.0 | 8.2.0 | TCRT: Correction to process VGCS_Handling_Relay_MSC | Sept 2007 | +| CP-38 | CP-070793 | C1-072829 | 43.068 | 0143 | - | Rel-8 | F | 8.2.0 | 8.3.0 | TCRT: Removal of the support of long application-specific data | Dec 2007 | +| CP-38 | | | | | | Rel-8 | | 8.2.0 | 8.3.0 | TCRT: Paging for incoming p-t-p transaction to service subscriber in an ongoing group call | Dec 2007 | +| | CP-070815 | C1-072830 | 43.068 | 0144 | - | | F | | | | | +| CP-39 | | | | | | Rel-8 | | 8.3.0 | 8.4.0 | TCRT: Warning tone for call termination due to time out of voice inactivity time | March 2008 | +| | CP-080136 | C1-080453 | 43.068 | 0148 | 1 | | C | | | | | +| CP-39 | CP-080129 | C1-080452 | 43.068 | 0147 | 1 | Rel-8 | F | 8.3.0 | 8.4.0 | TCRT: Clarification of the channel to be used for uplink access | March 2008 | +| CP-39 | | | | | | Rel-8 | | 8.3.0 | 8.4.0 | TCRT: Clean up of the requirement of sending SMS to non established group calls | March 2008 | +| | CP-080123 | C1-080536 | 43.068 | 0146 | 1 | | A | | | | | +| CP-40 | | | | | | Rel-8 | | 8.4.0 | 8.5.0 | TCRT: Closing some open issues concerning the transmission of application-specific data | June 2008 | +| | CP-080351 | C1-081646 | 43.068 | 0149 | - | | B | | | | | +| CP-40 | | | | | | Rel-8 | | 8.4.0 | 8.5.0 | TCRT: Clarification of conditions for start and stop of voice inactivity timer | June 2008 | +| | CP-080361 | C1-081648 | 43.068 | 0150 | - | | F | | | | | +| CP-46 | | | | | | Rel-9 | | 8.5.0 | 9.0.0 | Upgrade to Rel-9 | Dec 2009 | +| CP-47 | | | | | | Rel-9 | | 9.0.0 | 9.1.0 | | March 2010 | +| | CP-100135 | C1-100476 | 43.068 | 0151 | - | | C | | | TCRT: Uplink reply procedure | | +| CP-49 | | | | | | Rel-9 | | 9.1.0 | 9.2.0 | TC-RT: Use of application data for group calls involving more than one PLMN | September 2010 | +| | CP-100501 | C1-102316 | 43.068 | 0152 | - | | F | | | | | +| CP-50 | | | | | | Rel-10 | | 9.2.0 | 10.0.0 | TC-RT: Introduction of group IDs with prefix | December 2010 | +| | CP-100763 | C1-104237 | 43.068 | 0153 | 1 | | B | | | | | +| CP-54 | | | | | | Rel-11 | | 10.0.0 | 11.0.0 | TC-RT: Initial Talker Information handling (solving race conditions) | December 2011 | +| | CP-110882 | C1-114666 | 43.068 | 0154 | - | | F | | | | | +| CP-54 | | | | | | Rel-11 | | 10.0.0 | 11.0.0 | TC-RT: GCR Transient Data | December 2011 | +| | CP-110882 | C1-114668 | 43.068 | 0155 | - | | F | | | | | +| CP-55 | | | | | | Rel-11 | | 11.0.0 | 11.1.0 | | March 2012 | +| | CP-120121 | C1-120521 | 43.068 | 0156 | 1 | | B | | | TC-RT: Group Call Redundancy | | +| CP-55 | | | | | | Rel-11 | | 11.0.0 | 11.1.0 | TC-RT: Additional Calling Party Number | March 2012 | +| | CP-120099 | C1-120626 | 43.068 | 0161 | 1 | | A | | | | | +| CP-55 | | | | | | Rel-11 | | 11.1.0 | 11.1.1 | Minor editorial fixes | March 2012 | +| | | | 43.068 | | | | | | | | | +| CP-56 | | | | | | Rel-11 | | 11.1.1 | 11.2.0 | Cleanup corrections to group call redundancy | June 2012 | +| | CP-120319 | C1-121128 | 43.068 | 0162 | - | | F | | | | | +| CP-56 | | | | | | Rel-11 | | 11.1.1 | 11.2.0 | TC-RT: VGCSflex - interoperability with pre-Rel-7 relay MSCs | June 2012 | +| | CP-120319 | C1-121774 | 43.068 | 0163 | - | | B | | | | | +| CP-56 | | | | | | Rel-11 | | 11.1.1 | 11.2.0 | TC-RT: Correction of subscription check for VGCSflex | June 2012 | +| | CP-120319 | C1-121775 | 43.068 | 0164 | - | | B | | | | | +| CP-57 | | | | | | Rel-11 | | 11.2.0 | 11.3.0 | TC-RT: Corrections to group call redundancy | Sept 2012 | +| | CP-120596 | C1-122634 | 43.068 | 0165 | - | | F | | | | | +| CP-57 | | | | | | Rel-11 | | 11.2.0 | 11.3.0 | TC-RT: Cleanup of editorial or textual defects | Sept 2012 | +| | CP-120584 | C1-122636 | 43.068 | 0166 | - | | F | | | | | +| CP-58 | | | | | | Rel-11 | | 11.3.0 | 11.4.0 | TC-RT: Additional Calling Party Number | Dec 2012 | +| | CP-120808 | C1-124498 | 43.068 | 0167 | - | | F | | | | | \ No newline at end of file diff --git a/marked/Rel-11/43_series/43129/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg b/marked/Rel-11/43_series/43129/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b94834b2d7e2e178cf21a2207aeefdac8037b63e --- /dev/null +++ b/marked/Rel-11/43_series/43129/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e5e3be649d12fa4246f49d3b1ac4140bc761ad7b2adaaa2bf55f99b1c5e1c60 +size 66605 diff --git a/marked/Rel-11/43_series/43129/05d8710f69c476939295486ab1440350_img.jpg b/marked/Rel-11/43_series/43129/05d8710f69c476939295486ab1440350_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa08ce2b63914b8cad41862699573ff5fe5c6ee3 --- /dev/null +++ b/marked/Rel-11/43_series/43129/05d8710f69c476939295486ab1440350_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ba1eede3a5df86f2293cbfc03326a1ab6dd38c6b7809d4bea3fbff84a2f7b07 +size 27588 diff --git a/marked/Rel-11/43_series/43129/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg b/marked/Rel-11/43_series/43129/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10146417cc3f2ca4575185989397a6fb953fc18e --- /dev/null +++ b/marked/Rel-11/43_series/43129/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:802d5340ce84fb68962cde5e8d32f5d7237449b92c69fd7e032b8ed0447968b2 +size 111041 diff --git a/marked/Rel-11/43_series/43129/09955ff8214ffb6947951fc0f60eb6ab_img.jpg b/marked/Rel-11/43_series/43129/09955ff8214ffb6947951fc0f60eb6ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..271e76339fbc0250f3871903c9a3ccd2604b6391 --- /dev/null +++ b/marked/Rel-11/43_series/43129/09955ff8214ffb6947951fc0f60eb6ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f7701e25ab52c0fdddf9aec968f72328b754e110012184ac005e3a826445166 +size 18023 diff --git a/marked/Rel-11/43_series/43129/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg b/marked/Rel-11/43_series/43129/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..139309fbb742aa418bb6a7cbea1ce9d1568b4e0d --- /dev/null +++ b/marked/Rel-11/43_series/43129/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:613f3c707aa2c3deda1f750e6a946747da7c255ac61598458b832a232ae9890a +size 41453 diff --git a/marked/Rel-11/43_series/43129/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg b/marked/Rel-11/43_series/43129/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63fd3aab56e67060f6634940d47ba04889579609 --- /dev/null +++ b/marked/Rel-11/43_series/43129/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9fd6cc4dccb453c42c4e955a1ec91eaaa7c7bce7f38b27d0f443104a8468a0bd +size 51908 diff --git a/marked/Rel-11/43_series/43129/145fb9b19dc6513e7bf84c9ba7f083f2_img.jpg b/marked/Rel-11/43_series/43129/145fb9b19dc6513e7bf84c9ba7f083f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bce4c0bb053bbdef519f90ca544fae3725a71eba --- /dev/null +++ b/marked/Rel-11/43_series/43129/145fb9b19dc6513e7bf84c9ba7f083f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e6d763ad6efb0257c0d3a19064d4a88be713b3f088937ac5e6bca8d05cbd60f +size 148982 diff --git a/marked/Rel-11/43_series/43129/28f2f470a7b2446ae5f525123534383c_img.jpg b/marked/Rel-11/43_series/43129/28f2f470a7b2446ae5f525123534383c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5304752c333d4f36a7792974d1a41fbb922330eb --- /dev/null +++ b/marked/Rel-11/43_series/43129/28f2f470a7b2446ae5f525123534383c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:39952043fd0ea539b3d4c1423c7f268d7c2590224209260615721d1d26dac3a6 +size 103210 diff --git a/marked/Rel-11/43_series/43129/314da473d582c4327e1e3d56fcba19dd_img.jpg b/marked/Rel-11/43_series/43129/314da473d582c4327e1e3d56fcba19dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0912b9f1e6e98fec80e6033fb06f0bf26f3ace3b --- /dev/null +++ b/marked/Rel-11/43_series/43129/314da473d582c4327e1e3d56fcba19dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e8c2ba65d61bd4efff0733c40464a75cb58b19c110876fb5e561530066317ea +size 48837 diff --git a/marked/Rel-11/43_series/43129/4b398c5e8c4fd656d5b7a61806400650_img.jpg b/marked/Rel-11/43_series/43129/4b398c5e8c4fd656d5b7a61806400650_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa43187893426a16198e994192733b76dcf1d85d --- /dev/null +++ b/marked/Rel-11/43_series/43129/4b398c5e8c4fd656d5b7a61806400650_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1e79aa44eb52e42ae3d49731fbbba306fa063428efb1d1b8874e54ff9a2e019 +size 49213 diff --git a/marked/Rel-11/43_series/43129/4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg b/marked/Rel-11/43_series/43129/4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..462a3b9bc53868b8cc98aab184beb987260dee2a --- /dev/null +++ b/marked/Rel-11/43_series/43129/4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f0691784c8888500c9cf4cf2731b88896e481f71a5f3a76c96ef2577e58fd01 +size 70738 diff --git a/marked/Rel-11/43_series/43129/4f148853ae68fdcf5e43f7604cab457d_img.jpg b/marked/Rel-11/43_series/43129/4f148853ae68fdcf5e43f7604cab457d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8358e7f96a2b1356e104294a87e45be1920fe42d --- /dev/null +++ b/marked/Rel-11/43_series/43129/4f148853ae68fdcf5e43f7604cab457d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f7b11a3f00147a5156821bd5b9f7411f2121b99603036aa151c4d7bdf6fa93f +size 201476 diff --git a/marked/Rel-11/43_series/43129/57939c16065211317c5442cf2a4009e0_img.jpg b/marked/Rel-11/43_series/43129/57939c16065211317c5442cf2a4009e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f4b44f02dc06633ecf038dedbd99ed7b7f68f32 --- /dev/null +++ b/marked/Rel-11/43_series/43129/57939c16065211317c5442cf2a4009e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97fe719686e26a348e5529dec29d02ef5d73a814be72b41f8cf9e9a7a836f712 +size 18931 diff --git a/marked/Rel-11/43_series/43129/5e9af8986a5845504f251d3079da8078_img.jpg b/marked/Rel-11/43_series/43129/5e9af8986a5845504f251d3079da8078_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7b4c54159f0de972e66cf60fca7112552f3eb72 --- /dev/null +++ b/marked/Rel-11/43_series/43129/5e9af8986a5845504f251d3079da8078_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bdd836646a02e5718f42c9fec0836dc468103babc2dc480758db5d8467ecabd4 +size 45997 diff --git a/marked/Rel-11/43_series/43129/64cda8ce20067bc360ce2f3a5c9352b7_img.jpg b/marked/Rel-11/43_series/43129/64cda8ce20067bc360ce2f3a5c9352b7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0076ab405e610b823555df73c5115661777dc96 --- /dev/null +++ b/marked/Rel-11/43_series/43129/64cda8ce20067bc360ce2f3a5c9352b7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ea01ef217448a4b2129cfbdc389923c40ab2102791c041dd91eb01441da2473 +size 43201 diff --git a/marked/Rel-11/43_series/43129/66c2bf11a8f117cddf67eff92d4c736c_img.jpg b/marked/Rel-11/43_series/43129/66c2bf11a8f117cddf67eff92d4c736c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ff37f69eec145745cb684213ab3b0eb58901db3 --- /dev/null +++ b/marked/Rel-11/43_series/43129/66c2bf11a8f117cddf67eff92d4c736c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34eb974cddbebaf546d4ffa6b12099932b31db8d1eb417be68a7509b2b051fec +size 54888 diff --git a/marked/Rel-11/43_series/43129/720d082148a35c2d5537a04ed5268d8b_img.jpg b/marked/Rel-11/43_series/43129/720d082148a35c2d5537a04ed5268d8b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5220b3436513d1c2410db9e878ccbcfd8bf89622 --- /dev/null +++ b/marked/Rel-11/43_series/43129/720d082148a35c2d5537a04ed5268d8b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ccaa7234989189201520268bad56f67aab0928a1220f8c6b3cd2bcaa785d6bd3 +size 51135 diff --git a/marked/Rel-11/43_series/43129/747516f5861a0ddf31e3851da8e34b95_img.jpg b/marked/Rel-11/43_series/43129/747516f5861a0ddf31e3851da8e34b95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c43d293b82896e77211e87123c8897b29fc5cd4f --- /dev/null +++ b/marked/Rel-11/43_series/43129/747516f5861a0ddf31e3851da8e34b95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02f8124af8ac3c064d6f7efcc5c68ee6e75782cd83873344abedf9fff6569ec6 +size 54066 diff --git a/marked/Rel-11/43_series/43129/7b2d685b805535c1e94aee1365753b92_img.jpg b/marked/Rel-11/43_series/43129/7b2d685b805535c1e94aee1365753b92_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..151c2bb9f1e4551d92f464f6f7051f19a36ac85e --- /dev/null +++ b/marked/Rel-11/43_series/43129/7b2d685b805535c1e94aee1365753b92_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07d3e37b123336203dfbfe62b2203194aa8dc3b1fc3bad3f024eac734e45563e +size 41017 diff --git a/marked/Rel-11/43_series/43129/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-11/43_series/43129/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef3e0dca044f0ed54a03c61783847bd575fb7353 --- /dev/null +++ b/marked/Rel-11/43_series/43129/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:297eec29b5e651a17477151d62ab15432df6cca29e043fc3569e21f9b161a437 +size 45611 diff --git a/marked/Rel-11/43_series/43129/7f17c430b9598e4d748a8041457810b3_img.jpg b/marked/Rel-11/43_series/43129/7f17c430b9598e4d748a8041457810b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ba667f0b807924e28da751aae6379f64c010c4d --- /dev/null +++ b/marked/Rel-11/43_series/43129/7f17c430b9598e4d748a8041457810b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:392604062f811da4b459a7e1c41560820f29dec1a38cd376cf805a008c68ed78 +size 127344 diff --git a/marked/Rel-11/43_series/43129/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg b/marked/Rel-11/43_series/43129/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2cbd2e9760d631bfae4637602cebf9862476a38f --- /dev/null +++ b/marked/Rel-11/43_series/43129/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3b3de4d323253a0277c789e571dc5ee03af837eefdab75140be117627d99287 +size 115924 diff --git a/marked/Rel-11/43_series/43129/805c475f0859e607af0530ba43194bf1_img.jpg b/marked/Rel-11/43_series/43129/805c475f0859e607af0530ba43194bf1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5aa30f9db7d806b180ad8e4eed66749976b45890 --- /dev/null +++ b/marked/Rel-11/43_series/43129/805c475f0859e607af0530ba43194bf1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:706f618a7cd516edc0e567836ebd144462b9037f2829e0bfefab2d9ba147572a +size 69412 diff --git a/marked/Rel-11/43_series/43129/818a57b74294582a480f23f82d95815f_img.jpg b/marked/Rel-11/43_series/43129/818a57b74294582a480f23f82d95815f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52536e5da59e941dea08a497287a0c0e5af2a93f --- /dev/null +++ b/marked/Rel-11/43_series/43129/818a57b74294582a480f23f82d95815f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:625a8b11eebf1e3aa3c427fca97e0fb1d6506de869467647cf17b3710d180160 +size 50738 diff --git a/marked/Rel-11/43_series/43129/82fbb97c1145cac89ac72dd080fad17a_img.jpg b/marked/Rel-11/43_series/43129/82fbb97c1145cac89ac72dd080fad17a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8049dfcdc629b3b0b0d964791f70b746cfbbdb2d --- /dev/null +++ b/marked/Rel-11/43_series/43129/82fbb97c1145cac89ac72dd080fad17a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1df9d2d7f52b8fd35c74e57766f347d15270aef964beb5a37ba6a42c576d13e +size 118215 diff --git a/marked/Rel-11/43_series/43129/848073118eebfdbfdb9a60e3923fe0b3_img.jpg b/marked/Rel-11/43_series/43129/848073118eebfdbfdb9a60e3923fe0b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac12bf90b23cdf51f1d36f511f18de06b2ed0cb2 --- /dev/null +++ b/marked/Rel-11/43_series/43129/848073118eebfdbfdb9a60e3923fe0b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43e2e48b7ed65a2fc31e2b0019ad4b398d1368339ed280a22359e09095b5cb41 +size 50799 diff --git a/marked/Rel-11/43_series/43129/91b12db3c85bbf466ad27eb3665a1b06_img.jpg b/marked/Rel-11/43_series/43129/91b12db3c85bbf466ad27eb3665a1b06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..68fedc925f2b0a9371659d07e979efa01af7b897 --- /dev/null +++ b/marked/Rel-11/43_series/43129/91b12db3c85bbf466ad27eb3665a1b06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:981d886b8c9c549678b60e6d910a1ceeb1aa6fd7b65a59590df199297647d618 +size 55442 diff --git a/marked/Rel-11/43_series/43129/9f51a76cae7309a296cbc6997941eb3f_img.jpg b/marked/Rel-11/43_series/43129/9f51a76cae7309a296cbc6997941eb3f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3efcfb1ff6c0d94df8fb8f6ec024f69795c42116 --- /dev/null +++ b/marked/Rel-11/43_series/43129/9f51a76cae7309a296cbc6997941eb3f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8bcfc990ac4d4c7ede9f22440c9d3b3c72a7f42a6ed1ec96996f12d0dc3246e7 +size 43810 diff --git a/marked/Rel-11/43_series/43129/a2bbc82e5c6132b0870bd70f6657f919_img.jpg b/marked/Rel-11/43_series/43129/a2bbc82e5c6132b0870bd70f6657f919_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3507f9657d282bc0306da1c44aa0915fbaf5dba5 --- /dev/null +++ b/marked/Rel-11/43_series/43129/a2bbc82e5c6132b0870bd70f6657f919_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84759fa434474a04cc1fb6b7dbb8772128259fe3218d5edcf345689fc2c1ef86 +size 97910 diff --git a/marked/Rel-11/43_series/43129/a3472689858b068ef469213682965325_img.jpg b/marked/Rel-11/43_series/43129/a3472689858b068ef469213682965325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a8210fb5e88d8f4c35cd9ebc43fe44f302876f4 --- /dev/null +++ b/marked/Rel-11/43_series/43129/a3472689858b068ef469213682965325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef3b1950f5acf87fb032ce2978ba6417a5f3673202f91da40a7ec0b9dee2c51e +size 37723 diff --git a/marked/Rel-11/43_series/43129/a7721892ae499a78173ff3dfdc4e65a9_img.jpg b/marked/Rel-11/43_series/43129/a7721892ae499a78173ff3dfdc4e65a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e41320ce067261b65d9f305af1239178d099c5cc --- /dev/null +++ b/marked/Rel-11/43_series/43129/a7721892ae499a78173ff3dfdc4e65a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be96ea66ef772d9bf0ee82a9712ad58c2cb14d40348e8bafb2a749b191f06502 +size 18492 diff --git a/marked/Rel-11/43_series/43129/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-11/43_series/43129/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aec4b683b53cccbe3b87a66daa9eabd7fb83787c --- /dev/null +++ b/marked/Rel-11/43_series/43129/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5a1fa82fe5b0c23f276b4f3f459048d9706ec12ae55283401463380e79e1f20 +size 49984 diff --git a/marked/Rel-11/43_series/43129/bccc028d0e75bc30c41528056f581545_img.jpg b/marked/Rel-11/43_series/43129/bccc028d0e75bc30c41528056f581545_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f5032bb558a56862fc3ebfb02ddcd1aee0d30b9 --- /dev/null +++ b/marked/Rel-11/43_series/43129/bccc028d0e75bc30c41528056f581545_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd57a2af7a0812727a79d0fef63ae19342545f377980ed87779f392b4c1d57cd +size 196960 diff --git a/marked/Rel-11/43_series/43129/c1278da91cbcabe32628e589ebc47418_img.jpg b/marked/Rel-11/43_series/43129/c1278da91cbcabe32628e589ebc47418_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67e6b56eca9bc2bd96759c2cdc67038b7999987d --- /dev/null +++ b/marked/Rel-11/43_series/43129/c1278da91cbcabe32628e589ebc47418_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f23443666f30e9f570beae691a19dd497e2d71c539b12c37f32b99659e759f43 +size 58034 diff --git a/marked/Rel-11/43_series/43129/dd380ccd5aca1151074fede04826f1a4_img.jpg b/marked/Rel-11/43_series/43129/dd380ccd5aca1151074fede04826f1a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e69cb4ef107a5abcafbcbc5af9ba9fb295f2926d --- /dev/null +++ b/marked/Rel-11/43_series/43129/dd380ccd5aca1151074fede04826f1a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f28c980c23cc66597e7e50e74c4e18718bce56e45cf7fb698e027a7bd3b4bdff +size 41954 diff --git a/marked/Rel-11/43_series/43129/f1fbb1287d999c7034742de35bdab836_img.jpg b/marked/Rel-11/43_series/43129/f1fbb1287d999c7034742de35bdab836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..737d071f8fb7ff94016fe60417d03d9f26f019f8 --- /dev/null +++ b/marked/Rel-11/43_series/43129/f1fbb1287d999c7034742de35bdab836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f059cad2c9e223b2289fe572b3f9316f6e48e8aa678b1f1d5461770f9974fead +size 54250 diff --git a/marked/Rel-11/43_series/43129/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg b/marked/Rel-11/43_series/43129/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c16e55bd6e133a4113f34159c27ea8a28c0119d --- /dev/null +++ b/marked/Rel-11/43_series/43129/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a1d36a9ca66bf28cc7658b2dc88df594b8f417ef9d0d3e5bf5bf262fe04f81e +size 72076 diff --git a/marked/Rel-11/43_series/43129/raw.md b/marked/Rel-11/43_series/43129/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6fbdd951d3e875e54a4c918de07509b4f43eeb77 --- /dev/null +++ b/marked/Rel-11/43_series/43129/raw.md @@ -0,0 +1,3370 @@ + + + + + + +# Contents + +| | | +|--------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 7 | +| Introduction ..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Definitions and abbreviations ..... | 9 | +| 3.1 Definitions..... | 9 | +| 3.2 Void..... | 10 | +| 3.3 Abbreviations ..... | 10 | +| 4 Architecture and principles..... | 12 | +| 4.1 Reference architecture..... | 12 | +| 4.2 Handover principles ..... | 12 | +| 4.2.1 General ..... | 12 | +| 4.2.2 PS Handover preparation phase..... | 13 | +| 4.2.3 PS Handover execution phase ..... | 14 | +| 4.2.4 PS Handover Network Node Responsibilities..... | 14 | +| 4.3 Protocol architecture ..... | 14 | +| 4.3.1 User plane overview ..... | 14 | +| 4.3.2 Control plane overview ..... | 14 | +| 4.3.3 Physical Layer ..... | 15 | +| 4.3.3.1 Shared Channels ..... | 15 | +| 4.3.3.1.1 General ..... | 15 | +| 4.3.4 RLC/MAC ..... | 15 | +| 4.3.5 Radio Resource (RR)..... | 16 | +| 4.3.6 BSSGP ..... | 16 | +| 4.3.7 Overview of PS Handover Signalling Messages..... | 16 | +| 4.3.7.1 PS handover signalling messages on the Um interface ..... | 16 | +| 4.3.7.2 PS handover signalling messages on the Gb interface ..... | 16 | +| 4.3.7.3 PS handover signalling messages on the Gn interface ..... | 17 | +| 4.3.7.4 PS handover signalling messages on the Up interface ..... | 18 | +| 4.4 Identifiers ..... | 18 | +| 4.4.1 NSAPI, PFI, RAB ID relation during inter-RAT, inter-mode UTRAN/GERAN Iu PS handover ..... | 19 | +| 4.4.2 NSAPI, PFI, EPS Bearer ID relation during inter-RAT GERAN / E-UTRAN PS handover..... | 20 | +| 5 Signalling procedures..... | 20 | +| 5.1 GERAN (A/Gb mode ) → GERAN (A/Gb mode ) handover ..... | 20 | +| 5.1.1 Intra Cell..... | 20 | +| 5.1.2 Intra BSS ..... | 21 | +| 5.1.2.1 General..... | 21 | +| 5.1.2.2 Intra BSS HO; Preparation phase ..... | 21 | +| 5.1.2.3 Intra BSS HO; Execution phase..... | 22 | +| 5.1.2.4 Intra BSS Handover - Optimised..... | 23 | +| 5.1.3 Intra SGSN ..... | 25 | +| 5.1.3.1 Intra SGSN/Inter BSS HO, Preparation phase..... | 25 | +| 5.1.3.2 Intra SGSN/Inter BSS HO, Execution phase..... | 26 | +| 5.1.4 Inter SGSN ..... | 28 | +| 5.1.4.1 Inter SGSN HO, Preparation phase ..... | 28 | +| 5.1.4.2 Inter SGSN HO, Execution phase..... | 31 | +| 5.2 Inter-RAT/mode handover (GERAN A/Gb mode → UTRAN/ GERAN Iu mode )..... | 35 | +| 5.2.1 Intra SGSN ..... | 35 | +| 5.2.1.1 Intra-SGSN GERAN A/Gb mode to UTRAN/GERAN Iu mode HO; Preparation phase..... | 35 | +| 5.2.1.2 Intra-SGSN GERAN A/Gb mode to UTRAN/GERAN Iu mode HO; Execution phase ..... | 37 | +| 5.2.2 Inter SGSN ..... | 40 | +| 5.2.2.1 Inter-SGSN GERAN A/Gb mode to UTRAN/GERAN Iu mode HO; Preparation phase..... | 40 | +| 5.2.2.2 Inter-SGSN GERAN A/Gb mode to UTRAN/GERAN Iu mode HO; Execution phase ..... | 42 | +| 5.3 Inter-RAT/mode Handover (UTRAN/GERAN Iu mode → GERAN A/Gb mode )..... | 46 | +| 5.3.1 Intra SGSN ..... | 46 | + +| | | | +|-----------|-----------------------------------------------------------------------------------------------------------------|----| +| 5.3.1.1 | Inter RAT/mode UTRAN/GERAN Iu mode to GERAN A/Gb mode PS HO; Preparation phase ..... | 46 | +| 5.3.1.2 | Inter RAT/mode UTRAN/GERAN Iu mode to GERAN A/Gb mode PS HO; Execution phase ..... | 48 | +| 5.3.2 | Inter SGSN ..... | 51 | +| 5.3.2.1 | Inter RAT/mode UTRAN/GERAN Iu mode to GERAN A/Gb mode PS HO; Preparation phase ..... | 51 | +| 5.3.2.2 | Inter RAT UTRAN/GERAN Iu mode to GERAN A/Gb mode PS HO; Execution phase ..... | 53 | +| 5.3a | Inter-RAT Handover (GERAN A/Gb mode to E-UTRAN) ..... | 56 | +| 5.3a.1 | General ..... | 56 | +| 5.3a.2 | Preparation phase ..... | 56 | +| 5.3a.3 | Execution phase ..... | 57 | +| 5.3b | Inter-RAT Handover (E-UTRAN to GERAN A/Gb mode ) ..... | 57 | +| 5.3b.1 | General ..... | 57 | +| 5.3b.2 | Preparation phase ..... | 57 | +| 5.3b.3 | Execution phase ..... | 57 | +| 5.4 | Handover reject ..... | 58 | +| 5.4.1 | General ..... | 58 | +| 5.4.2 | Inter-SGSN HO Reject; Signalling procedure ..... | 58 | +| 5.5 | Handover cancel ..... | 58 | +| 5.5.1 | General ..... | 58 | +| 5.5.2 | Signalling procedures ..... | 59 | +| 5.5.2.1 | Inter-SGSN case, GERAN A/Gb mode → GERAN A/Gb mode ..... | 59 | +| 5.5.2.2 | Inter-SGSN case, GERAN A/Gb mode → UTRAN/GERAN Iu mode ..... | 60 | +| 5.5.2.3 | Inter-SGSN case, UTRAN/GERAN Iu mode → GERAN A/Gb mode ..... | 61 | +| 5.5.2.4 | Inter-SGSN, GERAN A/Gb mode → E-UTRAN ..... | 61 | +| 5.5.2.5 | Inter-SGSN case, E - UTRAN → GERAN A/Gb mode ..... | 61 | +| 5.6 | Container handling ..... | 61 | +| 5.6.1 | Contents of the containers ..... | 63 | +| 5.6.1.1 | Contents of the GERAN A/Gb mode or GAN mode → GERAN A/Gb mode Transparent Containers ..... | 64 | +| 5.6.1.1.1 | Source BSS to Target BSS Transparent Container ..... | 64 | +| 5.6.1.1.2 | Target BSS to Source BSS Transparent Container ..... | 64 | +| 5.6.1.2 | Contents of the GERAN A/Gb mode or GAN mode → UTRAN Transparent Containers ..... | 64 | +| 5.6.1.2.1 | Source to Target Transparent Container ..... | 64 | +| 5.6.1.2.2 | Target to Source Transparent Container ..... | 65 | +| 5.6.1.3 | Contents of the UTRAN → GERAN A/Gb Mode or GAN mode Transparent Containers ..... | 65 | +| 5.6.1.3.1 | Source BSS to Target BSS Transparent Container ..... | 65 | +| 5.6.1.3.2 | Target BSS to Source BSS Transparent Container ..... | 65 | +| 5.6.1.4 | Contents of the GERAN A/Gb mode → GERAN Iu mode Transparent Containers ..... | 66 | +| 5.6.1.4.1 | Source to Target Transparent Container ..... | 66 | +| 5.6.1.4.2 | Target to Source Transparent Container ..... | 66 | +| 5.6.1.5 | Content of GERAN Iu mode → GERAN A/Gb mode Transparent Containers ..... | 66 | +| 5.6.1.5.1 | Source BSS to Target BSS Transparent Container ..... | 66 | +| 5.6.1.5.2 | Target BSS to Source BSS Transparent Container ..... | 66 | +| 5.6.1.6 | Contents of the GERAN A/Gb mode → GAN mode Transparent Containers ..... | 67 | +| 5.6.1.6.1 | Source BSS to Target BSS Transparent Container ..... | 67 | +| 5.6.1.6.2 | Target BSS to Source BSS Transparent Container ..... | 67 | +| 5.6.1.7 | Contents of the GERAN A/Gb mode → E-UTRAN Transparent Containers ..... | 67 | +| 5.6.1.7.1 | Source to Target Transparent Container ..... | 67 | +| 5.6.1.7.2 | Target to Source Transparent Container ..... | 67 | +| 5.6.1.8 | Contents of the E-UTRAN → GERAN A/Gb mode Transparent Containers ..... | 68 | +| 5.6.1.8.1 | Source BSS to Target BSS Transparent Container ..... | 68 | +| 5.6.1.8.2 | Target BSS to Source BSS Transparent Container ..... | 68 | +| 5.7 | PS Handover Failure ..... | 68 | +| 5.7.1 | Preparations Phase Failure Scenarios ..... | 69 | +| 5.7.1.1 | PS Handover preparation phase failure scenarios on the Um interface ..... | 69 | +| 5.7.1.2 | PS Handover preparation phase failure scenarios on the Gb interface ..... | 69 | +| 5.7.1.3 | PS Handover preparation phase failure scenarios on the Gn interface ..... | 69 | +| 5.7.1.4 | PS Handover preparation phase failure scenarios on the Up interface ..... | 69 | +| 5.7.2 | Execution Phase Failure Scenarios ..... | 70 | +| 5.7.2.1 | Execution phase failures on the Um interface ..... | 70 | +| 5.7.2.1.1 | Initial Access Failure in the Target Cell during PS handover ..... | 70 | +| 5.7.2.1.2 | Radio contact with the MS is lost: ..... | 71 | +| 5.7.2.2 | Execution phase failures on the Gb interface ..... | 73 | + +| | | | +|-------------------------------|------------------------------------------------------------------------------------------------------|-----------| +| 5.7.2.3 | Execution phase failures on the Gn interface ..... | 74 | +| 5.8 | GAN Handover ..... | 74 | +| 5.8.1 | Intra-SGSN Handover (GERAN A/Gb mode → GAN mode handover)..... | 74 | +| 5.8.1.1 | Intra SGSN PS Handover, Preparation phase..... | 74 | +| 5.8.1.2 | Intra SGSN PS Handover, Execution phase ..... | 75 | +| 5.8.2 | Intra-SGSN Handover (GAN mode → GERAN A/Gb mode handover)..... | 75 | +| 5.8.2.1 | Intra SGSN PS Handover, Preparation phase..... | 75 | +| 5.8.2.2 | Intra SGSN PS Handover, Execution phase ..... | 76 | +| 5.8.3 | Inter-SGSN Handover (GERAN A/Gb mode → GAN mode handover)..... | 76 | +| 5.8.3.1 | Inter SGSN PS Handover, Preparation phase..... | 76 | +| 5.8.3.2 | Inter SGSN PS Handover, Execution phase ..... | 76 | +| 5.8.4 | Inter-SGSN Handover (GAN mode → GERAN A/Gb mode handover)..... | 76 | +| 5.8.4.1 | Inter SGSN PS Handover, Preparation phase..... | 76 | +| 5.8.4.2 | Inter SGSN, Execution phase ..... | 77 | +| 5.8.5 | Inter RAT Handover; Intra SGSN (UTRAN → GAN mode handover) ..... | 77 | +| 5.8.5.1 | Intra SGSN PS Handover, Preparation phase..... | 77 | +| 5.8.5.2 | Intra SGSN PS Handover, Execution phase ..... | 78 | +| 5.8.6 | Inter RAT Handover; Intra SGSN (GAN mode →UTRAN handover) ..... | 78 | +| 5.8.6.1 | Intra SGSN PS Handover, Preparation phase..... | 78 | +| 5.8.6.2 | Intra SGSN, Execution phase ..... | 78 | +| 5.8.7 | Inter RAT Handover; Inter SGSN (UTRAN → GAN mode handover) ..... | 79 | +| 5.8.7.1 | Inter SGSN PS Handover, Preparation phase..... | 79 | +| 5.8.7.2 | Inter SGSN PS Handover, Execution phase ..... | 79 | +| 5.8.8 | Inter RAT Handover; Inter SGSN (GAN mode → UTRAN handover) ..... | 79 | +| 5.8.8.1 | Inter SGSN PS Handover, Preparation phase..... | 79 | +| 5.8.8.2 | Inter SGSN PS Handover, Execution phase ..... | 79 | +| 6 | Radio interface Signalling..... | 79 | +| 6.1 | PS Handover Signalling (Um)..... | 79 | +| 6.1.1 | General ..... | 79 | +| 6.1.2 | Overview of PS Handover messages..... | 80 | +| 6.1.2.1 | GERAN A/Gb mode/GAN mode to GERAN A/Gb mode PS Handover ..... | 80 | +| 6.1.2.2 | UTRAN/GERAN Iu mode to GERAN A/Gb mode/GAN mode PS Handover ..... | 80 | +| 6.1.2.3 | GERAN A/Gb mode to GERAN Iu mode PS Handover..... | 81 | +| 6.1.2.4 | GERAN A/Gb mode/GAN mode to UTRAN mode PS Handover ..... | 82 | +| 6.1.2.5 | GERAN A/Gb mode to GAN mode PS Handover ..... | 82 | +| 6.1.2.6 | GERAN A/Gb mode to E-UTRAN PS Handover ..... | 82 | +| 6.1.2.7 | E-UTRAN to GERAN A/Gb mode PS Handover ..... | 83 | +| 6.1.3 | RLC/MAC segmentation..... | 83 | +| 6.1.4 | Inter RAT/mode PS Handover to GERAN A/Gb..... | 83 | +| 6.1.5 | Inter RAT/mode PS Handover from GERAN A/Gb ..... | 83 | +| 6.2 | Mechanisms for Initial Access in the Target Cell..... | 83 | +| 6.2.1 | General ..... | 83 | +| 6.2.2 | Synchronisation of handovers ..... | 84 | +| 6.2.3 | Option 1 - Downlink Data sent after performing access in the target cell ..... | 84 | +| 6.2.3.1 | Unsynchronised Networks Call Flow ..... | 84 | +| 6.2.3.2 | Synchronised Networks Call Flow ..... | 85 | +| 6.2.4 | Option 2 - Downlink Data sent before performing access in the target cell (Blind Transmission) ..... | 85 | +| 6.2.4.1 | Unsynchronised Networks Call Flow ..... | 86 | +| 6.2.4.2 | Synchronised Network Call Flow..... | 86 | +| 6.3 | Methods for triggering PS Handover ..... | 87 | +| Annex A (normative): | Agreed handover principles ..... | 88 | +| A.1 | Agreed handover principles ..... | 88 | +| Annex B (informative): | PS Handover Primitives..... | 90 | +| B.1 | Overview..... | 90 | +| B.2 | Primitives in Source BSS..... | 90 | +| B.3 | Primitives in Old SGSN ..... | 91 | + +B.5 Primitives in Target BSS..... 93 + +B.6 Primitives in MS ..... 93 + +Annex C (informative): Change history..... 94 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- Introduction + +Packet Switched (PS) handover is introduced in order to support real-time packet-switched with strict QoS requirements on low latency and packet loss. Packet switched handover reduces the service interruption of the user plane information at cell change compared to the cell-reselection and enables methods to improve buffer handling of user plane data in order to reduce packet loss at cell-change. + +# --- 1 Scope + +The present document defines the stage-2 service description for packet switched handover in GERAN *A/Gb mode* and GAN mode. ITU-T Recommendation I.130 [8] describes a three-stage method for characterisation of telecommunication services, and ITU-T Recommendation Q.65 [9] defines stage 2 of the method. The present document refers to packet switched handover in GERAN *A/Gb mode/GAN mode*, and therefore focuses on the corresponding radio protocol enhancements to the packet switched domain only i.e. when services are provided through the Gb interface. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.105: "Services and service capabilities". +- [3] 3GPP TS 22.060: "General Packet Radio Service (GPRS); Service description; Stage 1". +- [4] 3GPP TS 43.064: "Overall description of the GPRS radio interface; Stage 2". +- [5] 3GPP TS 25.922: "Radio Resource Management strategies". +- [6] 3GPP TS 23.107: "Quality of Service (QoS) concept and architecture". +- [7] 3GPP TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol". +- [8] ITU-T Recommendations I.130: "Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN". +- [9] ITU-T Recommendation Q.65: "The unified functional methodology for the characterization of services and network capabilities". +- [10] 3GPP TS 48.018: "General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN); BSS GPRS Protocol". +- [11] 3GPP TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface". +- [12] 3GPP TS 23.003: "Numbering, addressing and identification". +- [13] 3GPP TS 25.401: "UTRAN overall description". +- [14] 3GPP TS 43.051: "GSM/EDGE Radio Access Network (GERAN) overall description; Stage 2". +- [15] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3". +- [16] 3GPP TS 44.118: "Mobile radio interface layer 3 specification, Radio Resource Control (RRC) protocol; Iu mode". +- [17] 3GPP TS 25.331: "Radio Resource Control (RRC) protocol specification". +- [18] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General Aspects". + +- [19] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [20] 3GPP TS 23.108: "Mobile radio interface layer 3 specification core network protocols; Stage 2 (structured procedures)". +- [21] 3GPP TS 44.064: "Mobile Station - Serving GPRS Support Node (MS-SGSN) Logical Link Control (LLC) Layer Specification". +- [22] 3GPP TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes". +- [23] 3GPP TS 25.413: "UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling". +- [24] Void. +- [25] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol". +- [26] 3GPP TS 45.010: "Radio subsystem synchronization". +- [27] 3GPP TS 33.102: "Security architecture". +- [28] 3GPP TS 44.318: "Generic access to the A/Gb interface; Mobile GA interface layer 3 specification". +- [29] 3GPP TS 43.318: "Generic access to the A/Gb interface; Stage 2". +- [30] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRAN); Overall description; Stage 2". +- [31] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". +- [32] 3GPP TS 36.401: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Architecture description". +- [33] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". +- [34] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access (E-UTRA); S1 Application Protocol (SIAP)". +- [35] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3". +- [36] 3GPP TS 22.220: "Service requirements for Home NodeBs and Home eNodeBs". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply: + +**Active PFCs:** that subset of the PFCs to be handed over, for which the source BSS has determined that resources should be allocated in the target cell during the PS Handover preparation phase. + +**A/Gb mode:** MS mode operation where the MS is connected to the Core Network via GERAN and the A and/or Gb interfaces. + +**Blind Transmission:** refers to the decision made by the SGSN to start the transmission of downlink N-PDUs or by the target BSS/GANC to start the transmission of downlink LLC PDUs for a given mobile station before receiving confirmation that the PS handover procedure has been successfully completed. + +**GAN Mode:** MS mode of operation where the MS is connected to the Core Network via a GANC and the A and/or Gb interfaces. + +**PFC subject to handover:** refers to an MS's PFC for which the packet switched handover procedure is to be initiated when a cell change is required. Whether a PFC needs handover or not is decided by the BSS. This decision criteria is not standardized. + +**Source to Target Transparent Container:** This container is encoded as "Source RNC to Target RNC transparent container" in case of PS handover to UTRAN and as "Source eNB to Target eNB transparent container" in case of PS handover to E-UTRAN. It replaces the "Source RNC to Target RNC Transparent container" used in previous releases. + +**Target to Source Transparent Container:** This container is encoded as "Target RNC to Source RNC transparent container" in case of PS handover to UTRAN and as "Target eNB to Source eNB transparent container" in case of PS handover to E-UTRAN. It replaces the "Target RNC to Source RNC Transparent container" used in previous releases. + +**CSG Cell:** A UTRAN or E-UTRAN cell for which the reported access mode indicates "Closed access mode" (see [36]). + +**Hybrid Cell:** A UTRAN or E-UTRAN cell for which the reported access mode indicates "Hybrid access mode" (see [36]). + +## 3.2 Void + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|---------|---------------------------------------------| +| ATM | Asynchronous Transfer Mode | +| BSC | Base Station Controller | +| BSS | Base Station Sub-system | +| BSSGP | Base Station Subsystem GPRS Protocol | +| BTS | Base Transceiver Station | +| CN part | Core Network part | +| CN | Core Network | +| CS | Circuit Switched | +| CSG | Closed Subscriber Group | +| DTI | Direct Tunnel Indicator | +| DTM | Dual Transfer Mode | +| EDGE | Enhanced Data rates for GSM Evolution | +| eNB | E-UTRAN NodeB | +| EPC | Evolved Packet Core | +| EPS | Evolved Packet System | +| E-UTRA | Evolved UTRA | +| E-UTRAN | Evolved UTRAN | +| FLO | Flexible Layer One | +| GAN | Generic Access Network | +| GANC | Generic Access Network Controller | +| GboIP | Gb over IP | +| GCSI | GPRS CAMEL Subscriber information indicator | +| GERAN | GSM/EDGE Radio Access Network | +| GPRS | General Packet Radio Service | +| GSM | Global System for Mobile communications | +| GTP | GPRS Tunnelling Protocol | +| IMS | IP Multimedia Subsystem | +| IP | Internet Protocol | +| LLC | Logical Link Control | +| MAC | Medium Access Control | +| MME | Mobility Management Entity | +| MS | Mobile Station | +| MSC | Mobile Switching Centre | +| MTU | Maximum Transfer Unit | +| PDP | Packet Data Protocol | +| PDTCH | Packet Data Traffic CHannel | + +| | | +|---------|--------------------------------------------| +| PFC | Packet Flow Context | +| PFM | Packet Flow Management | +| PS | Packet Switched | +| PTCCH | Packet Timing advance Control CHannel | +| QoS | Quality of Service | +| RAB | Radio Access Bearer | +| RAN | Radio Access Network | +| RAT | Radio Access Technology | +| RAU | Routeing Area Update | +| RLC | Radio Link Control | +| RN part | Radio Network part | +| RNC | Radio Network Controller | +| RNS | Radio Network Subsystem | +| ROHC | RObust Header Compression | +| RRM | Radio Resource Management | +| RTP | Real Time Protocol | +| SABM | Set Asynchronous Balanced Mode | +| SACCH | Standalone Associated Control CHannel | +| SAPI | Service Access Point Identifier | +| SGSN | Serving GPRS Support Node | +| S-GW | Serving Gateway | +| SIP | Session Initiated Protocol | +| SNDPC | Sub-Network Dependent Convergence Protocol | +| TBF | Temporary Block Flow | +| TF | Transport Format | +| TFC | Transport Format Combination | +| TFCI | Transport Format Combination Indicator | +| TR | Technical Report | +| TS | Technical Specification | +| UA | Unnumbered Acknowledgement | +| UDP | User Datagram Protocol | +| UE | User Equipment | +| UMTS | Universal Mobile Telephony System | +| UTRAN | UMTS Terrestrial Radio Access Network | +| VoIP | Voice over IP | +| XID | eXchange IDentification | + +# 4 Architecture and principles + +## 4.1 Reference architecture + +![Reference Architecture for PS handover in GERAN A/Gb mode diagram](7f17c430b9598e4d748a8041457810b3_img.jpg) + +The diagram illustrates the reference architecture for PS handover in GERAN A/Gb mode. It shows the following components and interfaces: + +- Core Network (CN):** Contains the MSC, SGSN, S-GW, and MME. + - MSC is connected to PSTN and BSC (A interface). + - MSC is connected to SGSN via Gs interface. + - SGSN (left) is connected to MSC (Gs), BSC (Gb), GANC (Gb), and S-GW (S4). + - SGSN (right) is connected to S-GW (S4), MME (S3), and RNC (or BSC) (IuPS). + - S-GW is connected to SGSN (S4), MME (S11), and CN (S5/S8). + - MME is connected to S-GW (S11), SGSN (S3), and eNB (S1-MME). +- Access Networks:** + - BSS/GERAN:** Contains BSC and two BTSs. BSC is connected to MSC (A) and SGSN (Gb). BTSs are connected to BSC (Abis). + - UTRAN:** Contains RNC (or BSC) and two Node B cells. RNC is connected to SGSN (IuPS) and eNB (Iubis). + - E-UTRAN:** Contains eNB, which is connected to MME (S1-MME). + - GANC:** A separate box connected to SGSN (Gb) and MS (Up). +- External Entities:** + - PSTN:** Connected to MSC. + - MS:** Mobile Station, connected to BSS/GERAN (Um), GANC (Up), UTRAN (Uu), and E-UTRAN (Uu). + +**Legend:** + +- Bold lines: interfaces supporting user traffic; +- Thin lines: interfaces supporting signalling. + +Reference Architecture for PS handover in GERAN A/Gb mode diagram + +NOTE 1: The Iu interface is also supported by a GERAN BSS supporting Iu mode. + +NOTE 2: If both SGSNs support S4 interface then it is S16 otherwise Gn + +**Figure 1: Reference Architecture for PS handover in GERAN A/Gb mode** + +## 4.2 Handover principles + +### 4.2.1 General + +The PS Handover procedure is used to handover an MS with one or more packet flows from a source cell to a target cell. The source and target cells can be located within either the same BSS (Intra BSS HO), different BSSs within the same SGSN (Intra SGSN HO) or belonging to different SGSNs (Inter SGSN HO), or systems with different radio access types (Inter RAT HO, Inter mode HO). In addition, PS handover may occur between a GAN cell and a GERAN A/Gb mode cell or between a GAN cell and a UTRAN cell. + +While the MS is still in the source cell: + +- Radio resources in the target cell are allocated and signalled to the MS. +- System information of the target cell needed for access in the target cell is signalled to the MS. + +For each scenario (Intra BSS HO, Intra SGSN HO, Inter SGSN HO, Inter RAT HO/Inter mode HO) the PS handover procedure is divided into: + +- a preparation phase; and +- an execution phase. + +By using the Gs interface (together with NMO1) the interruption time for the PS Handover procedure would be shortened since using a combined LAU/RAU procedure would be possible. + +The scenarios described in the remainder of sub-clause 4.2 are limited to the case where an MS is being served by a BSS in GERAN A/Gb mode when a PS handover becomes necessary. + +### 4.2.2 PS Handover preparation phase + +The PS handover preparation phase consists of the following consecutive steps: + +- the decision by the source BSS to request a PS handover for an MS with one or more PFCs subject to handover: + - the request from the source BSS to the old SGSN for the PS handover; + - if the target BSS/GANC is not connected to the same SGSN the request from the old SGSN to the new SGSN to reserve resources; +- the reservation of resources in the target network nodes prior to ordering the MS to move to the target cell. This involves: + - in case of Inter SGSN handover, the new SGSN reserving SNDPCP/LLC resources and establishing Packet Flow Contexts; + - in case of RA change the SGSN (which belongs to the RA) allocates a new P-TMSI and derives a new Local TLLI from this P-TMSI; + - the target BSS/GANC reserving/allocating radio resources and Packet Flow Contexts in the target cell or the target RNS reserving/allocating radio resources and RABs in the target cell; + - in case of Inter-SGSN handover, the definition of security related parameters for the new SGSN, e.g. ciphering algorithm, to be used in the target cell immediately in both uplink and downlink directions. + +When PS handover has to be performed for an MS with multiple active PFCs, the SGSN requests the target BSS/GANC to create one or more PFCs or the target RNS to create one or more RABs corresponding to the active PFCs: + +- The target BSS/GANC may or may not establish radio resources for the created PFCs and the target RNS may or may not allocate resources for all the requested RABs. If no radio resources at all are established the handover shall be rejected (see Section 5.4.2). +- If not all the PFCs can be created successfully the target BSS/GANC indicates this to the new SGSN, which then informs the old SGSN/source BSS on the accepted and failed BSS PFCs. +- If not all the RABs can be allocated the target RNS indicates this to the new SGSN, which then informs the old SGSN/source BSS on the accepted and failed BSS PFCs. +- PFCs for which no radio resources were reserved in the target BSS or for which no RABs were allocated in the target RNS will result in the establishment of the necessary radio resources upon MS arrival in the target cell. For the case of PS handover to GAN the target GANC shall either create all requested PFCs or none. + +### 4.2.3 PS Handover execution phase + +The PS Handover execution phase consists of the following consecutive steps: + +- packet forwarding by the old SGSN of the received DL packets both to the source BSS, new SGSN (if the PS handover involves a new SGSN) and the target BSS/GANC/RNS as soon as radio resources are reserved in the target BSS/GANC/RNS; +- the optional "blind" transmission by the target BSS/GANC of the DL RLC/MAC blocks/LLC PDUs over the reserved radio resources in the target cell is only valid for lossy type of services where unacknowledged LLC and RLC protocol modes are used; +- the command generated by the target BSS/GANC/RNS sent via the source BSS to order the MS to handover to the target cell; +- the notification by the MS of its presence in the target cell on the allocated radio resources; +- the redirection by the SGSN of the DL packets to the target BSS/GANC/RNS alone; +- the release of the resources on the source side including PFCs and radio resources. + +### 4.2.4 PS Handover Network Node Responsibilities + +This clause would reflect the Agreed Handover principles from the clause A.1 by listing the specific node responsibilities during PS handover. + +## 4.3 Protocol architecture + +This clause will contain information on the services and functions provided and required by each layer. + +### 4.3.1 User plane overview + +The user plane protocol architecture for GERAN A/Gb mode is depicted in figure 2. See 3GPP TS 43.318 [29] for the user plane protocol architecture applicable for GAN mode. + +![Figure 2: User Plane protocol architecture in A/Gb mode. The diagram shows the protocol stack for the MS, BSS, SGSN, and GGSN. The MS stack includes Application, IP, SNDPCP, LLC, RLC, MAC, and GSM RF. The BSS stack includes RLC, MAC, GSM RF, BSSGP, Network Service, and L1bis. The SGSN stack includes Relay (SNDPCP, GTP-U), LLC, BSSGP, Network Service, L1bis, and L1. The GGSN stack includes IP, GTP-U, UDP, IP, L2, and L1. Interfaces are labeled Um, Gb, Gn, and Gi.](66c2bf11a8f117cddf67eff92d4c736c_img.jpg) + +| | | | | | | | +|-------------|----|--------|-----------------|------|----|-------| +| Application | | | | | | | +| IP | | | | | | IP | +| SNDPCP | | | Relay | | | GTP-U | +| LLC | | | SNDPCP | | | UDP | +| RLC | | RLC | LLC | | | IP | +| MAC | | MAC | BSSGP | | | L2 | +| GSM RF | | GSM RF | Network Service | | | L1 | +| | Um | | | Gb | | | +| | | | | | Gn | | +| | | | | | | Gi | +| MS | | BSS | | SGSN | | GGSN | + +Figure 2: User Plane protocol architecture in A/Gb mode. The diagram shows the protocol stack for the MS, BSS, SGSN, and GGSN. The MS stack includes Application, IP, SNDPCP, LLC, RLC, MAC, and GSM RF. The BSS stack includes RLC, MAC, GSM RF, BSSGP, Network Service, and L1bis. The SGSN stack includes Relay (SNDPCP, GTP-U), LLC, BSSGP, Network Service, L1bis, and L1. The GGSN stack includes IP, GTP-U, UDP, IP, L2, and L1. Interfaces are labeled Um, Gb, Gn, and Gi. + +Figure 2: User Plane protocol architecture in A/Gb mode + +### 4.3.2 Control plane overview + +Figure 3 shows the protocol architecture for the control plane required to support PS Handover in A/Gb mode. Protocol entities on the network side under BSSGP are not shown, as the architecture remains the same as for the legacy A/Gb mode. See 3GPP TS 43.318 [29] for the control plane protocol architecture applicable for GAN mode. + +![Figure 3: Control Plane Architecture in A/Gb mode. The diagram shows three main entities: MS (Mobile Station), BSS (Base Station System), and SGSN (Serving GPRS Support Node). The MS has a protocol stack: GMM/SM, LLC, RLC, MAC, and PHY. The BSS has a 'Relay' block at the top, followed by RLC, MAC, and PHY. The SGSN has a protocol stack: GMM/SM, LLC, BSSGP, Network Service, and L1bis. The MS PHY connects to the BSS PHY via the Um interface. The BSS RLC connects to the BSSGP, which connects to the Network Service, which connects to the L1bis. The BSS L1bis connects to the SGSN L1bis via the Gb interface.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +Figure 3: Control Plane Architecture in A/Gb mode. The diagram shows three main entities: MS (Mobile Station), BSS (Base Station System), and SGSN (Serving GPRS Support Node). The MS has a protocol stack: GMM/SM, LLC, RLC, MAC, and PHY. The BSS has a 'Relay' block at the top, followed by RLC, MAC, and PHY. The SGSN has a protocol stack: GMM/SM, LLC, BSSGP, Network Service, and L1bis. The MS PHY connects to the BSS PHY via the Um interface. The BSS RLC connects to the BSSGP, which connects to the Network Service, which connects to the L1bis. The BSS L1bis connects to the SGSN L1bis via the Gb interface. + +**Figure 3: Control Plane Architecture in A/Gb mode** + +### 4.3.3 Physical Layer + +#### 4.3.3.1 Shared Channels + +##### 4.3.3.1.1 General + +Radio resources on one or more shared channels may be assigned to an MS (according to its multislot capabilities) for exchange of user plane payload for any PFC between the BSS and the MS. The key characteristics of a service realized using a shared channel in A/Gb mode are as follows: + +- RLC/MAC control messages are used to allocate the required uplink and downlink TBFs where both TBFs are associated with the same PFC and therefore are identified using the same PFI. +- Handover initiation decisions are made by the BSS and may be based on measurement reports or cell change notification information sent by the mobile station on PACCH. +- If the mobile station is allocated one or more shared channels in support of a PFC that is subject to handover, then the BSS may prohibit this MS from making autonomous cell re-selection decisions while that PFC is active. +- After the MS has moved to the target cell, initial uplink access in this cell is controlled by USF scheduling. + +### 4.3.4 RLC/MAC + +The services required from the RLC/MAC layer in A/Gb mode are: + +- Data transfer in acknowledged mode. +- Data transfer in unacknowledged mode. +- Segmentation and reassembly. +- In-Sequence delivery of LLC PDUs (for a given PFC). +- Assignment, reconfiguration and release of TBFs and RLC instances (RLC/MAC control functions). +- Control of timing advance. +- Notification of unrecoverable errors to LLC. +- Handling of RLC/MAC control messages. + +RLC/MAC services are required by radio resource management functions in order to send and receive messages to/from the MS and BSS relating to radio resource management. + +RLC/MAC supports the following radio resource management features that are required for PS handover: + +- Establishment of a TBF on one or more physical channel(s) in a given direction, for a given PFC. +- Reconfiguration of the radio resources assigned to one or more TBFs in downlink and/or uplink within a cell. +- Release of TBFs and associated radio resources following the corresponding service deactivation. +- Release of all TBFs and associated radio resources in the source cell, as a result of handover to a target cell. + +### 4.3.5 Radio Resource (RR) + +This clause will contain information on any impacts on the RR protocol related to support of PS Handover. + +### 4.3.6 BSSGP + +BSSGP is expected to provide the signalling channel for PS Handover related signalling between the CN and the BSS/GANC. + +The services required from the BSSGP layer can therefore be summarised as: + +- Transmission and reception of PS Handover related messages (i.e. PFM messages) over the Gb interface. +- Routing of PS Handover related messages to the PFM entity. +- Handling of PS Handover related messages with the appropriate priority. + +### 4.3.7 Overview of PS Handover Signalling Messages + +The signalling messages used during PS handover are divided into four groups depending on the utilized interface: + +- PS handover signalling messages on the *Um* interface are RLC/MAC signalling blocks. +- PS handover signalling messages on the *Gb* interface are BSSGP signalling messages sent by the PFM entity. +- PS handover signalling messages on the *Gn* interface are GTP signalling messages. +- PS handover signalling messages on the *Up* interface are GA-PSR signalling messages. + +#### 4.3.7.1 PS handover signalling messages on the Um interface + +The signalling messages used on the *Um* interface are: + +- PS Handover Command (BSS -> MS). +- Packet Control Acknowledgement (MS -> BSS). +- PS Handover Access - Access Bursts (MS -> BSS). +- Packet Physical Information (BSS->MS). + +#### 4.3.7.2 PS handover signalling messages on the Gb interface + +The Gb interface signalling messages are new signalling messages carried by the BSSGP. These signalling messages are to be defined in 3GPP TS 48.018 [10]. + +The signalling messages used on the *Gb* interface are: + +- PS Handover Required (BSS->CN): + - This message is sent from the BSS controlling the source cell to the SGSN to indicate that for a given MS which already has radio resource(s) assigned, a PS handover is required. +- PS Handover Request (CN->BSS): + +- This message is sent from the SGSN to the BSS controlling the target cell to request this BSS to reserve resources for the MS subject to PS Handover. +- PS Handover Request Acknowledge (BSS->CN): + - This message is sent from the BSS controlling the target cell to the SGSN to report the outcome of the resource allocation for the requested BSS PFCs. This message indicates to the SGSN the successful resource allocation and the failure for one or more requested BSS PFCs. +- PS Handover Request Negative Acknowledge (BSS -> CN): + - This message is sent from the BSS controlling the target cell to the SGSN to report the failure of the resource allocation for all the requested BSS PFCs. +- PS Handover Complete (BSS->CN): + - This message is sent from the BSS controlling the target cell to the SGSN to notify the SGSN that the MS has made a successful access on the target cell. If the PS Handover to UTRAN is supported by the MS and the BSS, it will also be used by the BSS to request the INTER RAT HANDOVER INFO from the SGSN. +- PS Handover Complete Ack (CN->BSS): + - This message is sent from the SGSN to the BSS controlling the target cell to provide the MS inter-RAT terminal capabilities (INTER RAT HANDOVER INFO) if those were requested by this BSS in the **PS Handover Complete** message. +- PS Handover Required Acknowledge (CN->BSS): + - This message is sent from the SGSN to the BSS controlling the source cell to indicate that the MS can switch to the target cell. +- PS Handover Cancel (BSS->CN): + - This message is sent from the BSS controlling the source cell to the SGSN to inform the SGSN to cancel an ongoing handover. +- PS Handover Required Negative Acknowledge (CN->BSS): + - This message is sent from the SGSN to the BSS controlling the source cell to inform unsuccessful resource allocation or other PS handover failure in the target cell. + +#### 4.3.7.3 PS handover signalling messages on the Gn interface + +The Gn interface signalling messages are existing messages that will be used as described in 3GPP TS 29.060 [11]. + +The signalling messages used on the Gn interface between source SGSN and target SGSN are: + +- Forward Relocation Request: + - The old SGSN shall send a Forward Relocation Request message to the new SGSN to convey necessary information to perform the PS handover procedure between new SGSN and Target BSS. +- Forward Relocation Response: + - The new SGSN shall send a Forward Relocation Response message to the old SGSN as a response to a previous Forward Relocation Request message. +- Forward Relocation Complete: + - The new SGSN shall send a Forward Relocation Complete message to the old SGSN to indicate that the PS Handover procedure has been successfully finished. + +- Forward Relocation Complete Acknowledge: + - The old SGSN sends a Forward Relocation Complete Acknowledge message to the new SGSN as a response to Forward Relocation Complete message. +- Relocation Cancel Request: + - The Relocation Cancel Request message is sent from the old SGSN to the new SGSN when the old SGSN is requested to cancel the PS Handover procedure by the source BSS by means of BSSGP message. +- Relocation Cancel Response: + - The Relocation Cancel Response message is sent from the new SGSN to the old SGSN when the PS handover procedure has been cancelled in the old SGSN. This message is used as the response to the Relocation Cancel Request message. + +GTP messages need to be enhanced with additional IE to support PS Handover. + +#### 4.3.7.4 PS handover signalling messages on the Up interface + +The signalling messages used on the *Up* interface (see 3GPP TS 44.318 [28]) are: + +- GA-PSR HANDOVER COMMAND message (GANC → MS). + - This message is sent to trigger PS handover of an MS from a GAN cell to a GERAN A/Gb or UTRAN cell. +- GA-PSR UPLINK QUALITY INDICATION (GANC → MS) + - This message is sent to inform an MS of PS service related information as perceived by the GANC. +- GA-PSR HANDOVER INFORMATION message (MS → GANC) + - This message is sent by the MS to trigger the PS handover procedure in the GANC. +- GA-PSR ACTIVATE UTC REQ message (GANC → MS) + - This message is sent to allocate a GA-PSR Transport Channel to an MS. +- GA-PSR ACTIVATE UTC ACK message (MS → GANC) + - This message is sent to confirm the allocation of a GA-PSR Transport Channel to an MS. +- GA-PSR HANDOVER COMPLETE (MS → GANC) + - This message is sent to indicate the completion of PS handover to a GAN cell. + +## 4.4 Identifiers + +The identifiers used in PS handover for GERAN A/Gb mode are the identities used by the MS to connect via GERAN through the Gb interface as well as through the Iu and S1 interface to the Core Network. + +A large number of these identities for GERAN A/Gb mode will be utilized in the PS handover procedure in GERAN A/Gb mode in the same manner as specified currently. However in order to support PS handover procedure new identifiers will be defined as well. + +In order to enable data transmission and to address the resources allocated by the target system during the PS Handover procedure (i.e. for the case where the target cell belongs to another RA), before the MS moves to the target cell a new P-TMSI will be allocated by the SGSN associated with the RA the target cell belongs to. The new P-TMSI is a temporary and unique identifier in the new RA and is used to assign a local TLLI for the target cell. + +NOTE: Further in this TS the term "local TLLI" refers to the Local TLLI derived from new P-TMSI assigned by the new SGSN and utilized in the target cell, whereas the term "old TLLI" refers to the Local TLLI utilized in the source cell that is derived from the P-TMSI assigned by the old SGSN. + +In case of inter RAT PS Handover to/from UTRAN and inter-mode handover to/from GERAN Iu mode, existing UTRAN and GERAN Iu mode identifiers will be used. + +In case of inter RAT PS Handover to/from E-UTRAN, identifiers defined for E-UTRAN will be used. + +The existing as well as new identifiers utilized in PS handover procedure for GERAN A/Gb mode are listed in table 1. + +**Table 1: Identifiers utilized in PS handover in GERAN A/Gb mode** + +| Identifier | Specification reference | +|------------------------------------------------------|---------------------------------------------------------------| +| CI (Cell Identity) | 3GPP TS 23.003 [12], 3GPP TS 25.401 [13], 3GPP TS 43.051 [14] | +| RAI (Routing Area Identity) | 3GPP TS 23.003 [12] | +| LAI (Location Area Identity) | 3GPP TS 24.008 [15] | +| IMSI (International Mobile Subscriber Identity) | 3GPP TS 23.003 [12] | +| P-TMSI (Packet Temporary Mobile Subscriber Identity) | 3GPP TS 23.003 [12] | +| TLLI (Temporary Logical Link Identity) | 3GPP TS 23.003 [12] | +| RNTI(Radio Network Temporary Identity) | 3GPP TS 44.118 [16], 3GPP TS 25.401 [13] | +| GRNTI (GERAN Radio Network Temporary Identity) | 3GPP TS 25.401 [13] | +| U-RNTI (UTRAN-RNTI) | 3GPP TS 25.401 [13] | +| TEID (Tunnel Endpoint Identifier) | 3GPP TS 29.060 [11] | +| NSAPI (Network Service Access Point Identifier) | 3GPP TS 29.060 [11] | +| TI (Transaction Identifier) | 3GPP TS 24.007 [18] | +| SAPI (Service Access Point Identifier) | 3GPP TS 29.060 [11] | +| PFI (Packet Flow Identifier) | 3GPP TS 48.018 [10] | +| BVCI (BSSGP Virtual Connection Identifier) | 3GPP TS 48.018 [10] | +| RAB Id (Radio Access Bearer Identifier) | 3GPP TS 25.331 [17] | +| RB Id (Radio Bearer Identifier) | 3GPP TS 25.331 [17] and 3GPP TS36.331 [31] | +| TFI (Temporary Flow Identity) | 3GPP TS 44.060 [7] | +| USF (Uplink State Flag) | 3GPP TS 44.060 [7] | +| Handover Reference | 3GPP TS 44.018 [10] | +| Cell RNTI (C-RNTI) | 3GPP TS36.331 [31] | +| eNB Identity | 3GPP TS36.413 [34] | +| MME Identity | 3GPP TS23.003 [12] | +| Tracking Area identity (TAI) | 3GPP TS24.301 [33] | +| EPS Bearer ID | 3GPP TS24.007 [18] | + +### 4.4.1 NSAPI, PFI, RAB ID relation during inter-RAT, inter-mode UTRAN/GERAN *Iu* PS handover + +During the inter-RAT and inter-mode PS handover to/from UTRAN/GERAN *Iu* there is a need to associate the MSs active PDP context with the BSS PFC and RABs in the respective SGSN(s). + +As depicted in 3GPP TS 23.060 [19] NSAPI is a common identifier of the PDP context in all systems and as such it can be used by the MS to associate the active PDP contexts to the BSS PFC identified by the PFI and the RAB identified by the RAB Id during the inter-mode and inter-RAT PS handover. The MS has to associate the BSS PFC identified by the PFI utilized in a GERAN A/Gb mode cell or GAN mode cell with a RAB identified by RAB Id utilized in the UTRAN/GERAN *Iu* mode cell. This is done through the relation with the NSAPI, which is the common identifier in both systems. MS performs this association based on the identifiers received by the network. + +The information received by the MS/UE depends on the RAT of the target cell: + +- In case of the UTRAN/GERAN *Iu* mode target cell and GERAN A/Gb mode or GAN mode source cell, the MS shall receive the RAB Id and associate this with its existing PFIs based on the relation with NSAPI. +- In case of the GERAN A/Gb mode or GAN mode target cell, UTRAN/GERAN *Iu* mode source cell, the UE shall receive the PFI for each of the accepted NSAPIs and associate them with its existing RAB IDs based on the relation with NSAPI. An SGSN supporting PS Handover to GERAN *A/Gb mode* or GAN mode shall always assign a SAPI and it shall assign a valid PFI value if the UE has indicated the support of PS Handover procedures. The MS shall indicate in the MS network capability IE whether it supports "multiple TBFs". The SGSN may use this information when allocating the SAPI and PFI during PDP Context activation. During handover preparation the SAPI and PFI values shall be sent from the old SGSN to the new SGSN. +- If the old SGSN did not assign a valid PFI value for one or more PDP Contexts, the new SGSN shall after successful completion of the RAU initiate explicit SM procedure to allocate a PFI value according to its policy for each of the PDP Contexts for which no PFI is currently allocated. If none of the PDP Contexts + +forwarded from the old SGSN has a valid PFI allocated the new SGSN shall consider this as a failure case and the request for PS handover shall be rejected.. + +### 4.4.2 NSAPI, PFI, EPS Bearer ID relation during inter-RAT GERAN / E-UTRAN PS handover + +General principles for mapping between PDP contexts and EPS bearers are described in 3GPP TS23.060; the mapping of the QoS profiles is depicted in 3GPP TS 23.401. As specified in 3GPP TS 23.060 there is one to one mapping between a PDP Context and EPS bearer, and their respective identifiers NSAPI and EPS bearer ID. In E-UTRAN a radio bearer (RB) transports the packets of an EPS bearer between a UE and an eNodeB. As defined in 3GPP TS23.401, if a radio bearer exists, there is a one-to-one mapping between an EPS bearer and this radio bearer (RB). + +The mobile station has to associate the BSS PFC identified by the PFI utilized in a GERAN *A/Gb mode* cell with a E-UTRAN radio bearer identified by RB Id. This is done by the mobile station through the relation with the NSAPI and EPS Bearer ID identifiers received by the network. + +The MME supporting PS handover to/from GERAN performs similar functionality as the 3G SGSN such that it allocates a PFI for each active EPS bearer initiated in E-UTRAN: The new SGSN in GERAN then acts as follows: + +- If for a given PDP Context the new SGSN does not receive a PFI from the MME then it will not proceed with the PS handover for this flow i.e. it will not request the target BSS to allocate TBF resources corresponding to that PDP Context. +- If none of the PDP Contexts forwarded from the MME has a valid PFI allocated the new SGSN will consider this as a failure case and the request for PS handover shall be rejected. +- All PDP contexts for which no resources are allocated by the new SGSN or for which the new SGSN cannot support the same SAPI and PFI (i.e. the corresponding NSAPIs are not addressed in the response message of the target SGSN) will however be maintained and the related SAPIs and PFIs will be kept. These PDP contexts may be modified or deactivated by the new SGSN via explicit SM procedures upon RAU procedure. + +# --- 5 Signalling procedures + +## 5.1 GERAN (*A/Gb mode*) → GERAN (*A/Gb mode*) handover + +### 5.1.1 Intra Cell + +Intra Cell PS Handover will be needed in cases when a new channel is selected in the same cell to be used by the MS. This is handled by the BSS internally and if there are no changes in the new channel there is no need for BSS to notify the SGSN about the change of channel. + +BSS/SGSN signalling will be needed in case the new channel has limited resources and cannot support the same QoS, for the BSS PFC as the old channel. + +For these purpose existing modification procedures on the Um and Gb interface are used, e.g. PACKET TIMESLOT RECONFIGURE (3GPP TS 44.060 [7]) on the air interface and MODIFY BSS PFC (3GPP TS 48.018 [10]) procedure on the Gb interface. + +If the modification procedures fail BSS may cancel the intra cell PS handover procedure. + +### 5.1.2 Intra BSS + +#### 5.1.2.1 General + +This clause is further split into two clauses. The first describes an intra-BSS handover procedure based largely on the inter-BSS handover procedure. The second section describes an optional optimised intra-BSS handover procedure. When the source and target cells are within the same BSS the handover can be either executed by the BSS itself (optimised handover) or by involving the SGSN in the preparation phase. In the latter case although handover is performed within one BSS the roles of source BSS and target BSS are the same as in Inter BSS Handover. + +#### 5.1.2.2 Intra BSS HO; Preparation phase + +![Sequence diagram for Intra BSS HO Preparation phase showing interactions between MS, BSS, and SGSN.](a3472689858b068ef469213682965325_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant SGSN + Note right of BSS: 1. Decision to perform A/Gb PS Handover + BSS->>SGSN: 2. PS handover Required + SGSN->>BSS: 3. PS Handover Request + Note right of BSS: 4. BSS reserves radio resources and creates the Target BSS to Source BSS Transparent Container + BSS->>SGSN: 5. PS Handover Request Acknowledge + +``` + +Sequence diagram for Intra BSS HO Preparation phase showing interactions between MS, BSS, and SGSN. + +**Figure 4: PS Handover Preparation Phase; Intra-BSS case (GERAN A/Gb mode → GERAN A/Gb mode)** + +1. The BSS decides to initiate a PS handover. At this point both uplink and downlink user data is transmitted via the following: TBFs between the MS and BSS, BSSGP PFCs tunnel(s) between the BSS and SGSN, GTP tunnel(s) between the SGSN and GGSN. +2. The BSS sends a **PS Handover Required** (Old TLLI, Cause, Source Cell Identifier, Target Cell Identifier, Source BSS to Target BSS Transparent Container (RN part), Active PFCs List) message to the SGSN. +3. The SGSN determines from the Target Cell Identifier the type of handover, i.e. intra-SGSN, inter-SGSN or inter-RAT/mode handover and whether the routing area has changed. In case of no change of routing area, the SGSN sends a **PS Handover Request** (TLLI, Cause, IMSI, Source Cell Identifier, Target Cell Identifier, PFCs To Be Set Up List, Source BSS to Target BSS Transparent Container (RN part)) message to the BSS. In case when the routing area changes the SGSN allocates a new P-TMSI for this MS and derives a local TLLI from this P-TMSI prior to the sending of the **PS Handover Request** message. The SGSN shall only request resources for PFCs that are included in the Active PFCs List. + +NOTE: The BSS PFCs required to be set up are downloaded to the target BSS from the SGSN, i.e. all information required for PFC creation. + +4. Based upon the ABQP for each PFC the BSS makes a decision about which PFCs to assign radio resources. The algorithm by which the BSS decides which PFCs that need resources is implementation specific. Due to resource limitations not all downloaded PFCs will necessarily receive resource allocation. The BSS allocates TBFs for each PFC that can be accommodated. + +After allocating radio resources the target BSS shall prepare the Target BSS to Source BSS Transparent Container for the set up BSS PFCs. + +5. The BSS shall send the **PS Handover Request Acknowledge** (TLLI, List of Set Up PFCs, Target BSS to Source BSS Transparent Container (PS Handover Command with RN part)) message to the SGSN. Upon sending the **PS Handover Request Acknowledge** message the BSS shall be prepared to receive downlink LLC PDUs directed to the new cell and associated with the accepted PFCs. + +When the SGSN receives the **PS Handover Request Acknowledge** message and it decides to proceed with the handover, the preparation phase is finished and the execution phase will follow. + +#### 5.1.2.3 Intra BSS HO; Execution phase + +![Sequence diagram of Intra BSS HO Execution phase showing interactions between MS, BSS, SGSN, and GGSN.](09955ff8214ffb6947951fc0f60eb6ab_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant SGSN + participant GGSN + Note right of GGSN: 1. GTP Packets to SGSN + GGSN->>SGSN: + Note right of SGSN: 2. PS Handover Required Acknowledge + SGSN->>BSS: + Note right of BSS: 3. PS Handover Command + BSS->>MS: + Note right of MS: 4. PS Handover Access + MS->>BSS: + Note right of BSS: 5. Packet Physical Information + BSS->>SGSN: + Note right of SGSN: 6. RA/Cell Update + SGSN->>BSS: + Note right of BSS: 7. PS Handover Complete + BSS->>MS: + Note right of MS: Sending of uplink data possible + +``` + +Sequence diagram of Intra BSS HO Execution phase showing interactions between MS, BSS, SGSN, and GGSN. + +**Figure 5: PS Handover Execution Phase; Intra-BSS case (GERAN A/Gb mode → GERAN A/Gb mode)** + +1. The SGSN continues to receive GTP packets from the GGSN (via GTP) and forwards the associated PDU payload to the MS via the BSS. + +When receiving the **PS Handover Request Acknowledge** message the SGSN may, based on QoS, start duplication of LLC PDUs and forward those to the new cell in the BSS. If the SGSN forwards downlink packets to the new cell in the BSS, the BSS may start blind transmission of downlink user data towards the MS over the allocated radio channels. + +2. The SGSN continues the PS Handover by sending a **PS Handover Required Acknowledge** (Old TLLI, List of Set Up PFCs, Target BSS to Source BSS Transparent Container (PS Handover Command with RN part)) message to the BSS. + +Before sending the **PS Handover Required Acknowledge** message, the SGSN, based on QoS, may suspend downlink data transfer for any PDP contexts. + +Before sending the **PS Handover Command** message to the MS the BSS, based on QoS, may try to empty the downlink BSS buffer for any BSS PFCs. + +NOTE 1: Only PFI(s) for PFCs accepted by the target cell are included in the message. + +3. The BSS sends the **PS Handover Command** (RN part) message to the MS by interrupting the transmission of LLC PDUs on any of the downlink TBFs. Following the transmission of this signalling message the BSS may resume LLC PDU transmission until it either has no more LLC PDUs to send or the PFC is released. Upon reception of the **PS Handover Command** the MS is not required to continue data reception in the source cell. The MS shall suspend the uplink transmission of user plane data. MS management of uplink N-PDUs following the reception of the **PS Handover Command** message is as follows: + +- All uplink packets associated with a PFC receiving handover treatment that have not yet been fully transmitted might be buffered depending on the QoS class. +- Subsequent uplink packets that become available for transmission following the reception of the **PS Handover Command** message might also be buffered depending on the QoS class. +- The MS may discard uplink packets during the link interruption to preserve the real-time properties. + +4. The MS tunes to the radio channel and the timeslot allocated in the target cell by the BSS and may send the **PS Handover Access** (Handover Reference) message in the form of four handover access bursts to the BSS on the allocated channel. The **PS Handover Command** message indicates whether or not the MS shall send **PS Handover Access** messages. + +5. The BSS sends a **Packet Physical information** message to the MS containing update of the timing advance for the MS to synchronize. + +NOTE 2: In the case of pre-synchronised handover the MS may receive the timing advance information to use in uplink in the target cell in the **PS Handover Command** message (if no timing advance information is included, the mobile station uses a default timing advance in the target cell). In a pre-synchronised or synchronised handover, the **Packet Physical information** message is not sent in the target cell. + +6. The MS sends uplink LLC PDUs, e.g. a **Routing Area Update Request** message or uplink user data packets to the SGSN immediately after receiving the **Packet Physical Information** message or, in a synchronised or pre-synchronised handover, immediately if the **PS Handover Access** message is not required to be sent (see Section 6.2). + +The MS shall resume the user data transfer only for those NSAPIs for which radio resources are allocated in the target cell. For NSAPIs using LLC ADM for which radio resources were not allocated in the target cell the MS may request radio resources using the legacy procedures. + +7. Upon reception of the first correct RLC/MAC block (sent in normal burst format) from the MS the BSS sends a **PS Handover Complete** (TLLI, IMSI) message to inform the SGSN that the MS has arrived in the target cell. After the reception of the **PS Handover Complete** message the SGSN shall initiate the BSS PFC procedures to delete the BSS PFC in the BSS controlling the source cell and shall be prepared to receive data from the new cell. The source BSS initiates the release of the radio resources in the source cell after receiving the DELETE-BSS-PFC PDU from the SGSN. + +If Routing Area Update occurs after completion of the execution phase, then the CAMEL procedure calls shall be performed according to 3GPP TS 23.060. + +#### 5.1.2.4 Intra BSS Handover - Optimised + +This clause describes the optimised intra-BSS PS handover procedures applicable for the case where the source and target cells are associated with the same Network Service Entity (NSE) and the same Routing Area (RA). The optimisation involves the BSS providing the data forwarding function and does not require any explicit signalling with the SGSN except the sending of PS Handover Complete at the end of PS Handover. Support for this procedure is optional for the BSS. + +Supporting this procedure requires that the BSS be able to determine whether or not it manages PS resources for the target cell, whether or not the target cell is associated with the same NSE, that it can internally forward LLC PDUs from the source to the target cell and whether or not both cells are part of the same RA (i.e. the SGSN is not required to make this determination and relay this information). If the BSS cannot make these determinations it shall use the non-optimised intra-BSS PS handover procedures described in clauses 5.1.2.2 and 5.1.2.3. + +![Sequence diagram for Optimised Intra-BSS PS Handover (same NSE and same RA) involving MS, BSS, and SGSN.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant SGSN + + Note right of BSS: 1. BSS decides to initiate A/Gb mode PS handover + Note right of BSS: 2. BSS determines that it manages target cell and that it is part of same NSE and RA as the source cell + + BSS->>MS: 3. PS Handover Command + MS->>BSS: 4. PS Handover Access + BSS->>MS: 5. Packet Physical Information + MS->>BSS: 6. UL RLC/MAC data + BSS->>SGSN: 7. PS Handover Complete + SGSN->>MS: 8. Packet Uplink Ack/Nack + Note right of BSS: 9. DL LLC PDU (new BVCI) + +``` + +Sequence diagram for Optimised Intra-BSS PS Handover (same NSE and same RA) involving MS, BSS, and SGSN. + +**Figure 6: Optimised Intra-BSS PS Handover (same NSE and same RA)** + +1. The BSS decides that a handover is required based on e.g. received measurement reports. +2. The BSS determines that it manages resources for both cells and that they are associated with the same (NSE) and the same RA. The BSS applies data forwarding (from the old cell to the new cell) for PFCs that it determines are to receive PS handover treatment. + +NOTE 1: The MS does not know if optimised or non-optimised intra-BSS PS handover procedures are used. + +3. The BSS sends the **PS Handover Command** (RN part) message to the MS by interrupting the transmission of LLC PDUs on any of the downlink TBFs. Following the transmission of this signalling message the BSS may resume LLC PDU transmission until it either has no more LLC PDUs to send or the PFC is released. Upon reception of the **PS Handover Command** the MS is not required to continue data reception in the source cell. Upon reception of the **PS Handover Command** the MS shall suspend the uplink transmission of user plane data. MS management of uplink N-PDUs following the reception of the **PS Handover Command** message is as follows: + - All uplink packets associated with a PFC receiving handover treatment that have not yet been fully transmitted might be buffered depending on the QoS class. + - Subsequent uplink packets that become available for transmission following the reception of the **PS Handover Command** message might also be buffered depending on the QoS class. + - The MS may discard uplink packets during the link interruption to preserve the real-time properties. +4. The MS tunes to the radio channel and the timeslot allocated in the target cell by the BSS and if so required by the BSS (see sub-clause 6.2) sends the **PS Handover Access** (Handover Reference) message in the form of four handover access bursts to the BSS on the allocated channel. The **PS Handover Command** message indicates whether the **PS Handover Access** message shall be sent by the MS. +5. Upon receipt of the **PS Handover Access** message, based on the Handover Reference, the BSS sends the **Packet Physical Information** message, if needed (see sub-clause 6.2), with the timing advance to the MS for the MS to synchronise. + +NOTE 2: In the case of pre-synchronised handover the MS may receive the timing advance information to use in uplink in the target cell in the **PS Handover Command** message (if no timing advance information is included, the mobile station uses a default timing advance in the target cell). In a pre-synchronised or synchronized handover the **Packet Physical Information** message is not sent in the target cell. + +- The MS sends uplink LLC PDUs, e.g. uplink user data packets, in the allocated channel to the BSS. + +The MS shall resume the user data transfer only for those NSAPIs for which there are radio resources allocated in the target cell. For NSAPIs using LLC ADM for which radio resources were not allocated in the target cell the MS may request radio resources using the legacy procedures. + +- Upon reception of the first correct RLC/MAC block (sent in normal burst format) from the MS, the BSS releases the radio resources in the source cell and sends, on the target cell BVCI, the **PS Handover Complete** (TLLI, IMSI, Target Cell Identifier) message to the SGSN in order to indicate that the BSS has performed an internal handover. In this case, the target cell is indicated in the **PS Handover Complete** message. +- Once the BSS has correctly identified the MS, it sends a **Packet Uplink Ack/Nack** message (see 3GPP TS 44.060) indicating the status of the received RLC data blocks. +- The reception of the **PS Handover Complete** message at the SGSN triggers the sending of downlink data to the new cell using a new BVCI. The first DL PDU received by the BSS with the new-BVCI allows the BSS to clear the relationship to the old BVCI. + +The reception of the PS handover Complete message indicates to the SGSN that there is no need to wait for the Cell Update sent from the MS to the SGSN. + +NOTE 3: It is assumed here that downlink flow control is carried out on a per PFC basis and that the PFC specific flow control parameters remain the same upon MS arrival in the target cell. + +### 5.1.3 Intra SGSN + +#### 5.1.3.1 Intra SGSN/Inter BSS HO, Preparation phase + +![Sequence diagram for PS Handover Preparation Phase: Intra-SGSN/Inter-BSS case. The diagram shows four lifelines: MS, Source BSS, Target BSS, and SGSN. The process starts with a dashed box '1. Decision to perform A/Gb PS Handover' between MS and Source BSS. Step 2: Source BSS sends '2. PS handover Required' to SGSN. Step 3: SGSN sends '3. PS Handover Request' to Target BSS. Step 4: A dashed box '4. Target BSS reserves radio resources and creates the Target BSS to Source BSS Transparent Container' is shown between Target BSS and Source BSS. Step 5: Target BSS sends '5. PS Handover Request Acknowledge' to SGSN.](dd380ccd5aca1151074fede04826f1a4_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Source BSS + participant Target BSS + participant SGSN + Note left of Source BSS: 1. Decision to perform A/Gb PS Handover + Source BSS->>SGSN: 2. PS handover Required + SGSN->>Target BSS: 3. PS Handover Request + Note right of Target BSS: 4. Target BSS reserves radio resources and creates the Target BSS to Source BSS Transparent Container + Target BSS->>SGSN: 5. PS Handover Request Acknowledge + +``` + +Sequence diagram for PS Handover Preparation Phase: Intra-SGSN/Inter-BSS case. The diagram shows four lifelines: MS, Source BSS, Target BSS, and SGSN. The process starts with a dashed box '1. Decision to perform A/Gb PS Handover' between MS and Source BSS. Step 2: Source BSS sends '2. PS handover Required' to SGSN. Step 3: SGSN sends '3. PS Handover Request' to Target BSS. Step 4: A dashed box '4. Target BSS reserves radio resources and creates the Target BSS to Source BSS Transparent Container' is shown between Target BSS and Source BSS. Step 5: Target BSS sends '5. PS Handover Request Acknowledge' to SGSN. + +**Figure 7: PS Handover Preparation Phase; Intra-SGSN/Inter-BSS case (GERAN A/Gb mode → GERAN A/Gb mode)** + +- The source BSS decides to initiate a PS handover. At this point both uplink and downlink user data is transmitted via the following: TBFs between MS and source BSS, BSSGP PFCs tunnel(s) between the source BSS and SGSN, GTP tunnel(s) between the SGSN and GGSN. +- The source BSS sends a **PS Handover Required** (Old TLLI, Cause, Source Cell Identifier, Target Cell Identifier, Source BSS to Target BSS Transparent Container (RN part), Active PFCs List, Reliable INTER RAT HANDOVER INFO) message to the SGSN. + +The source BSS shall always include the 'Reliable INTER RAT HANDOVER INFO' indicator set to '1' in the **PS Handover Required** message if the INTER RAT HANDOVER INFO in the Source BSS to Target BSS Transparent Container was received from the SGSN in a **PS Handover Complete Ack** message or a **PS Handover Request** message with "Reliable INTER RAT HANDOVER INFO" set to "1" or a **CREATE-BSS-PFC** message. It shall be set to '0' otherwise. + +- The SGSN determines from the Target Cell Identifier the type of handover, i.e. intra-SGSN, inter-SGSN or inter-RAT/mode handover and whether the routing area has changed. In case of no change of routing area, the SGSN + +sends a **PS Handover Request** (TLLI, Cause, IMSI, Source Cell Identifier, Target Cell Identifier, PFCs To Be Set Up List, Source BSS to Target BSS Transparent Container (RN part), Reliable Inter RAT HANDOVER INFO) message to the target BSS. In case of Intra-SGSN PS handover when the routing area changes, the SGSN shall assign a new P-TMSI for the MS and derive a local TLLI prior to the sending of the **PS Handover Request** message. The SGSN shall only request resources for PFCs that are included in the Active PFCs List. If received in a **PS Handover Required** message, the SGSN shall forward the 'Reliable INTER RAT HANDOVER INFO' indicator to the target BSS. + +NOTE 1: The BSS PFCs required to be set up are downloaded to the target BSS from the SGSN, i.e. all information required for PFC creation. + +4. Based upon the ABQP for each PFC the target BSS makes a decision about which PFCs to assign radio resources. The algorithm by which the BSS decides which PFCs that need resources is implementation specific. Due to resource limitations not all downloaded PFCs will necessarily receive resource allocation. The target BSS allocates TBFs for each PFC that can be accommodated by the target BSS. + +After allocating radio resources the target BSS shall prepare the Target BSS to Source BSS Transparent Container for the set up BSS PFCs. + +5. The target BSS sends the **PS Handover Request Acknowledge** (TLLI, List of Set Up PFCs, Target BSS to Source BSS Transparent Container (PS Handover Command with RN part)) message to the SGSN. Upon sending the **PS Handover Request Acknowledge** message the target BSS shall be prepared to receive downlink LLC PDUs from the SGSN for the accepted PFCs. + +When the SGSN receives the **PS Handover Request Acknowledge** message and it decides to proceed with the handover, the preparation phase is finished and the execution phase will follow. + +#### 5.1.3.2 Intra SGSN/Inter BSS HO, Execution phase + +![Sequence diagram for PS Handover Execution Phase; Intra-SGSN/Inter-BSS case. It shows the message flow between MS, Source BSS, Target BSS, SGSN, and GGSN.](f1fbb1287d999c7034742de35bdab836_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Source BSS + participant Target BSS + participant SGSN + participant GGSN + + GGSN-->>SGSN: 1. GTP Packets to SGSN + SGSN-->>Source BSS: 2. Relay packets to target BSS + Source BSS-->>MS: + Target BSS-->>SGSN: 3. PS Handover Required Acknowledge + SGSN->>Source BSS: 4. PS Handover Command + Source BSS->>MS: + MS->>Target BSS: 5. PS Handover Access + Target BSS->>MS: 6. Packet Physical Information + Target BSS->>SGSN: 7. RA/Cell Update + Target BSS->>SGSN: 8. PS Handover Complete + Note over MS, Target BSS: Sending of uplink data possible + SGSN->>Target BSS: 9. PS Handover Complete Acknowledge + +``` + +Sequence diagram for PS Handover Execution Phase; Intra-SGSN/Inter-BSS case. It shows the message flow between MS, Source BSS, Target BSS, SGSN, and GGSN. + +**Figure 8: PS Handover Execution Phase; Intra-SGSN/Inter-BSS case +(GERAN A/Gb mode → GERAN A/Gb mode)** + +1. The SGSN continues to receive GTP packets from the GGSN (via GTP) and forwards the associated PDU payload to the MS via the source BSS. +2. When receiving the **PS Handover Request Acknowledge** message the SGSN may, based on QoS, start duplication of LLC PDUs and forward those to the target BSS. If the SGSN forwards downlink packets to the target BSS, the target BSS may start blind transmission of downlink user data towards the MS over the allocated radio channels. + +3. The SGSN continues the PS Handover by sending a **PS Handover Required Acknowledge** (Old TLLI, List of Set Up PFCs, Target BSS to Source BSS Transparent Container (PS Handover Command with RN part)) message to the source BSS. + +Before sending the **PS Handover Required Acknowledge** message, the SGSN, based on QoS, may suspend downlink data transfer for any PDP contexts. + +Before sending the **PS Handover Command** message to the MS the source BSS, based on QoS, may try to empty the downlink BSS buffer for any BSS PFCs. + +NOTE 1: Only PFI(s) for PFCs accepted by the target cell are included in the message. + +4. The source BSS sends the **PS Handover Command** (RN part) message to the MS by interrupting the transmission of LLC PDUs on any of the downlink TBFs. Following the transmission of this signalling message the source BSS may resume LLC PDU transmission until it either has no more LLC PDUs to send or the PFC is released. Upon reception of the **PS Handover Command** message the MS is not required to continue data reception in the source cell. Upon reception of the **PS Handover Command** message the MS shall suspend the uplink transmission of user plane data. MS management of uplink N-PDUs following the reception of the **PS Handover Command** message is as follows: + +- All uplink packets associated with a PFC receiving handover treatment that have not yet been fully transmitted might be buffered depending on the QoS class. +- Subsequent uplink packets that become available for transmission following the reception of the **PS Handover Command** message might also be buffered depending on the QoS class. +- The MS may discard uplink packets during the link interruption to preserve the real-time properties. + +5. The MS tunes to the radio channel and the timeslot allocated in the target cell by the BSS and may send the **PS Handover Access** (Handover Reference) message in the form of four handover access bursts to the BSS on the allocated channel. The **PS Handover Command** message indicates whether or not the MS shall send **PS Handover Access** messages. +6. The target BSS sends a **Packet Physical information** message to the MS containing the timing advance for the MS to synchronise. + +NOTE 2: In the case of pre-synchronised handover the MS may receive the timing advance information to use in uplink in the target cell in the **PS Handover Command** message (if no timing advance information is included, the mobile station uses a default timing advance in the target cell). In a pre-synchronised or synchronized handover, the **Packet Physical Information** message is not sent in the target cell. + +7. The MS sends uplink LLC PDUs, e.g. a **Routing Area Update Request** message or uplink user data packets to the SGSN immediately after receiving the **Packet Physical Information** message or, in a synchronised or pre-synchronised handover, immediately if the **PS Handover Access** message is not required to be sent (see Section 6.2). + +The MS shall resume the user data transfer only for those NSAPIs for which there are radio resources allocated in the target cell. For NSAPIs using LLC ADM for which radio resources were not allocated in the target cell the MS may request for radio resources using the legacy procedures. + +8. Upon reception of the first correct RLC/MAC block (sent in normal burst format) from the MS the target BSS sends a **PS Handover Complete** (TLLI, IMSI, Request for Inter RAT Handover Info) message to inform the SGSN that the MS has arrived in the target cell. After the reception of the **PS Handover Complete** message the SGSN shall initiate the BSS PFC procedures to delete the BSS PFC in the BSS controlling the source cell and shall be prepared to receive data from the new cell. The source BSS initiates the release of the radio resources in the source cell after receiving the DELETE-BSS-PFC PDU from the SGSN. The target BSS that supports inter-RAT PS handover to UTRAN shall request the INTER RAT HANDOVER INFO from the SGSN if the 'Reliable INTER RAT HANDOVER INFO' is missing or set to '0' in the **PS Handover Request** message or if it has not received the INTER RAT HANDOVER INFO as part of the Source BSS to Target BSS transparent container. +9. Upon reception of the **PS Handover Complete** message with the "Request for INTER RAT HANDOVER INFO" set to "1" for UTRAN, the SGSN shall send PS Handover Complete Acknowledge (TLLI, Inter RAT Handover Info) to the target BSS. + +10. The target BSS receiving the **PS Handover Complete Acknowledge** message shall set the 'Reliable INTER RAT HANDOVER' to '1' in the **PS Handover Required** message in any subsequent PS handover to GERAN *A/Gb mode*. The target BSS failing to receive the **PS Handover Complete Acknowledge** message shall set the 'Reliable INTER RAT HANDOVER' to '0' in the **PS Handover Required** message in any subsequent PS handover to GERAN *A/Gb mode*. The target BSS shall, upon receipt of the INTER RAT HANDOVER INFO in the **PS Handover Complete Acknowledge** message, discard the INTER RAT HANDOVER INFO received from the source BSS during the preparation phase. + +If Routing Area Update occurs after completion of the execution phase, then the CAMEL procedure calls shall be performed according to 3GPP TS 23.060. + +### 5.1.4 Inter SGSN + +#### 5.1.4.1 Inter SGSN HO, Preparation phase + +![Sequence diagram of the Inter SGSN HO Preparation phase. Lifelines: MS, Source BSS, Target BSS, Old SGSN, New SGSN, GGSN. The process starts with a decision to perform an A/Gb PS Handover at the Source BSS. The Source BSS sends a PS Handover Required message to the Old SGSN. The Old SGSN sends a Forward Relocation Request to the New SGSN. The New SGSN sends a PS Handover Request to the Target BSS. The Target BSS performs resource reservation and creates a transparent container. The Target BSS sends a PS Handover Request Acknowledge to the New SGSN. The New SGSN sends a Forward Relocation Response to the Old SGSN.](805c475f0859e607af0530ba43194bf1_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Source BSS + participant Target BSS + participant Old SGSN + participant New SGSN + participant GGSN + + Note right of Source BSS: 1. Decision to perform A/Gb PS Handover + Source BSS->>Old SGSN: 2. PS Handover Required + Old SGSN->>New SGSN: 3. Forward Relocation Request + New SGSN->>Target BSS: 4. PS Handover Request + Note right of Target BSS: 5. Reservation of Radio Resources in target BSS + Note right of Target BSS: 6. Target BSS creates the Target BSS to Source BSS Transparent Container + Target BSS->>New SGSN: 7. PS Handover Request Acknowledge + New SGSN->>Old SGSN: 8. Forward Relocation Response + +``` + +Sequence diagram of the Inter SGSN HO Preparation phase. Lifelines: MS, Source BSS, Target BSS, Old SGSN, New SGSN, GGSN. The process starts with a decision to perform an A/Gb PS Handover at the Source BSS. The Source BSS sends a PS Handover Required message to the Old SGSN. The Old SGSN sends a Forward Relocation Request to the New SGSN. The New SGSN sends a PS Handover Request to the Target BSS. The Target BSS performs resource reservation and creates a transparent container. The Target BSS sends a PS Handover Request Acknowledge to the New SGSN. The New SGSN sends a Forward Relocation Response to the Old SGSN. + +**Figure 9: PS Handover Preparation Phase; Inter-SGSN case (GERAN A/Gb mode → GERAN A/Gb mode)** + +1. The source BSS decides to initiate a PS handover. At this point both uplink and downlink user data is transmitted via the following: TBFs between MS and source BSS, BSSGP PFCs tunnel(s) between source BSS and old SGSN, GTP tunnel(s) between old SGSN and GGSN. +2. The source BSS sends a **PS Handover Required** (Old TLLI, Cause, Source Cell Identifier, Target Cell Identifier, Source BSS to Target BSS Transparent Container (RN part), Active PFCs List, Reliable Inter RAT HANDOVER INFO) message to the old SGSN. The source BSS shall always include the 'Reliable INTER RAT HANDOVER INFO' indicator set to '1' in the **PS Handover Required** message if the INTER RAT HANDOVER INFO in the Source BSS to Target BSS Transparent Container was received from the SGSN in a **PS Handover Complete Ack** message or a **PS Handover Request** message with "Reliable INTER RAT HANDOVER INFO" set to "1" or a **CREATE-BSS-PFC** message. It shall be set to '0' otherwise. +3. The old SGSN determines from the Target Cell Identifier that the type of handover is inter-SGSN. In case of inter-SGSN PS Handover, the old SGSN initiates the PS Handover resource allocation procedure by sending a **Forward Relocation Request** (IMSI, Cause, Source Cell Identifier, Target Cell Identifier, MM Context, PDP Contexts, Packet Flow ID, SNDPCP XID parameters, LLC XID parameters, Tunnel Endpoint Identifier for the Control Plane, SGSN Address for the control plane, Source BSS to Target BSS Transparent Container (RN part) in the BSS container, PDP Context Prioritisation, Reliable INTER RAT HANDOVER INFO) message to the new SGSN. The old SGSN sends all active PDP contexts to the new SGSN indicating the PFIs and the XID parameters related to those PDP contexts. Each PDP context contains the GGSN Address for the User Plane and the Uplink TEID for Data (to this GGSN Address and Uplink TEID for Data the old SGSN and the new SGSN send uplink packets). + +The MM context contains security related information, e.g. used ciphering algorithm and ciphering key as described in 3GPP TS 29.060 [11]. The relation between GSM and UMTS security parameters is defined in 3GPP TS 33.102 [27]. + +The Ciphering key used by the old SGSN is reused by the new SGSN until a new authentication procedure is performed (see clause 5.1.4.2, bullet 13). + +If the new SGSN does not support the indicated ciphering algorithm, the new SGSN has to select a new ciphering algorithm. This new algorithm will be sent transparently from the new SGSN to the MS. The IOV-UI parameter generated in the new SGSN and used as input to the ciphering procedure will also be transferred transparently from the new SGSN to the MS. + +When the new SGSN receives the **Forward Relocation Request** message it extracts from the PDP Contexts the associated NSAPIs, SAPIs and PFIs to be used in the new SGSN. In case when the new SGSN does not support the same SAPI and PFI indicated by the old SGSN for a certain NSAPI, the new SGSN shall continue the PS handover procedure only for those NSAPIs for which it can support the same PFI and SAPI as the old SGSN and for which it can allocate resources. All PDP contexts for which no resources are allocated by the new SGSN or for which it cannot support the same SAPI and PFI (i.e. the corresponding NSAPIs are not addressed in the **Forward Relocation Response** message of the target SGSN), are maintained in the new SGSN and the related SAPIs and PFIs are kept. When this occurs the packet data transfer corresponding to PDP Contexts for which new SAPI and PFI values are needed are suspended. These PDP contexts may be modified or deactivated by the new SGSN via explicit SM procedures upon the completion of the routing area update (RAU) procedure. When the required PDP, MM, SNDPCP and LLC contexts are established and the mapping between NSAPI, SAPI and PFI for each of these PDP Contexts is established, the corresponding packet data transfer can continue. + +If for a given PDP Context the new SGSN does not receive a PFI from the old SGSN, it shall not request the target BSS to allocate TBF resources corresponding to that PDP Context. + +If none of the PDP Contexts forwarded from the old SGSN has a valid PFI allocated the new SGSN shall consider this as a failure case and the request for PS handover shall be rejected. + +The old SGSN shall indicate the current XID parameter settings (i.e. those used at the old SGSN) to the new SGSN. If the new SGSN can accept all XID parameters as indicated by the old SGSN, the new SGSN shall create a NAS container for PS HO indicating 'Reset to the old XID parameters'. + +NOTE 1: 'Reset to the old XID parameters' means that the LLC and SNDPCP layer are reset, except for the LLC XID parameters and SNDPCP XID parameters which are re-initialized to the latest negotiated values, and the negotiated compression entities which are re-initialized. + +NOTE 2: void + +Otherwise the new SGSN shall create a NAS container for PS HO indicating Reset (i.e. reset to default parameters). + +If received in a **PS Handover Required** message, the old SGSN shall forward the 'Reliable INTER RAT HANDOVER INFO' indicator to the new SGSN in the **Forward Relocation Request** message. + +4. The new SGSN sends a **PS Handover Request** (Local TLLI, Cause, IMSI, Source Cell Identifier, Target Cell Identifier, Source BSS to Target BSS Transparent Container (RN part), PFCs To Be Set Up List, NAS container for PS HO, Reliable Inter RAT HANDOVER INFO) message to the target BSS. The new SGSN shall not request resources for PFCs associated with PDP contexts with a maximum bit rate for uplink and downlink of 0 kbit/s or for which the Activity Status Indicator within the PDP Context indicates that no active PFC exists on the source side. + +NOTE 3: The BSS PFCs required to be set up are downloaded to the target BSS from the new SGSN, i.e. all information required for PFC creation. + +5. Based upon the ABQP for each PFC the target BSS makes a decision about which PFCs to assign radio resources. The algorithm by which the BSS decides which PFCs that need resources is implementation specific. Due to resource limitations not all downloaded PFCs will necessarily receive resource allocation. The target BSS allocates TBFs for each PFC that can be accommodated by the target BSS. +6. The target BSS shall prepare the Target BSS to Source BSS Transparent Container which contains a PS Handover Command including the CN part (NAS container for PS HO) and the RN part (PS Handover Radio Resources). + +7. The target BSS shall send the **PS Handover Request Acknowledge** (Local TLLI, List of Set Up PFCs, Target BSS to Source BSS Transparent Container) message to the new SGSN. Upon sending the **PS Handover Request Acknowledge** message the target BSS shall be prepared to receive downlink LLC PDUs from the new SGSN for the accepted PFCs. +8. When the new SGSN receives the **PS Handover Request Acknowledge** message the **Forward Relocation Response** (Cause, List of Set Up PFCs, Target BSS to Source BSS Transparent Container in the BSS Container, Tunnel Endpoint Identifier Control Plane, SGSN Address for the control plane, Tunnel Endpoint Identifier Data II) message is sent from the new SGSN to the old SGSN. This message indicates that the new SGSN is ready to receive packets forwarded from the old SGSN. If the target BSS or the new SGSN failed to allocate resources this shall be indicated in the message. The Tunnel Endpoint Identifier Data II, one information for each PDP context, contains the tunnel endpoint of the new SGSN and the IP address of the new SGSN for data forwarding from the old to the new SGSN. + +The new SGSN activates the allocated LLC/SNDCP engines as specified in 3GPP TS 44.064 [21] for an SGSN originated Reset or 'Reset to the old XID parameters'. + +When the old SGSN receives the **Forward Relocation Response** message and it decides to proceed with the handover, the preparation phase is finished and the execution phase will follow. + +#### 5.1.4.2 Inter SGSN HO, Execution phase + +![Sequence diagram for Inter SGSN HO, Execution phase. Lifelines: MS, Source BSS, Target BSS, Old SGSN, New SGSN, GGSN, HLR. The diagram shows the flow of data and signaling messages during a handover from an old SGSN to a new SGSN.](4f148853ae68fdcf5e43f7604cab457d_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Source BSS + participant Target BSS + participant Old SGSN + participant New SGSN + participant GGSN + participant HLR + + Note right of GGSN: 1. GTP Packets to old SGSN + GGSN-->Old SGSN: 1. GTP Packets to old SGSN + Note right of Old SGSN: 2. Relay packets to new SGSN + Old SGSN-->New SGSN: 2. Relay packets to new SGSN + Note right of New SGSN: 3. Send the relayed packets over the allocated LLC and/RMAC entities (LLC ADM only) + New SGSN-->Target BSS: 3. Send the relayed packets over the allocated LLC and/RMAC entities (LLC ADM only) + Note right of Target BSS: 4. PS Handover Required Acknowledge + Target BSS-->Old SGSN: 4. PS Handover Required Acknowledge + Note right of Old SGSN: 4a. Forward SRNS Context + Old SGSN-->New SGSN: 4a. Forward SRNS Context + Note right of New SGSN: 4b. Forward SRNS Context Acknowledge + New SGSN-->Old SGSN: 4b. Forward SRNS Context Acknowledge + Note right of Source BSS: 5. PS Handover Command + Source BSS-->MS: 5. PS Handover Command + Note right of Target BSS: 6. PS Handover Access + Target BSS-->MS: 6. PS Handover Access + Note right of MS: 6. Physical Information + MS-->Target BSS: 6. Physical Information + Note right of Target BSS: 7. XID Response + Target BSS-->MS: 7. XID Response + Note right of Old SGSN: 8. PS Handover Complete + Old SGSN-->New SGSN: 8. PS Handover Complete + Note right of New SGSN: 9. Forward Relocation Complete + New SGSN-->Old SGSN: 9. Forward Relocation Complete + Note right of Old SGSN: 9. Forward Relocation Complete Acknowledge + Old SGSN-->New SGSN: 9. Forward Relocation Complete Acknowledge + Note right of Old SGSN: C1 + Old SGSN-->Source BSS: 11. BSS packet flow procedures + Note right of New SGSN: 10. Update PDP Context Request + New SGSN-->GGSN: 10. Update PDP Context Request + Note right of GGSN: GTP Packets to GGSN + GGSN-->New SGSN: GTP Packets to GGSN + Note right of New SGSN: 10. Update PDP Context Response + New SGSN-->GGSN: 10. Update PDP Context Response + Note right of GGSN: GTP Packets to new SGSN + GGSN-->New SGSN: GTP Packets to new SGSN + Note right of Old SGSN: Forwarded data + Old SGSN-->Source BSS: Forwarded data + Note right of Target BSS: Forwarded data + Target BSS-->MS: Forwarded data + Note right of New SGSN: 12. XID negotiation for LLC ADM + New SGSN-->MS: 12. XID negotiation for LLC ADM + Note right of New SGSN: 12a. SABM UA exchange (re-establishment and XID negotiation for LLC ABM) + New SGSN-->MS: 12a. SABM UA exchange (re-establishment and XID negotiation for LLC ABM) + Note right of New SGSN: 13. RAU Request + New SGSN-->MS: 13. RAU Request + Note right of New SGSN: 14. Security Functions + New SGSN-->HLR: 14. Security Functions + Note right of HLR: 15. Update Location + HLR-->New SGSN: 15. Update Location + Note right of New SGSN: 16. Cancel Location + New SGSN-->Old SGSN: 16. Cancel Location + Note right of Old SGSN: 16. Cancel Location Ack + Old SGSN-->New SGSN: 16. Cancel Location Ack + Note right of New SGSN: 17. Insert Subscriber Data + New SGSN-->HLR: 17. Insert Subscriber Data + Note right of HLR: 17. Insert Subscriber Data Ack + HLR-->New SGSN: 17. Insert Subscriber Data Ack + Note right of New SGSN: 18. Update Location Ack + New SGSN-->HLR: 18. Update Location Ack + Note right of New SGSN: C2 + New SGSN-->MS: 19. RAU Accept + Note right of New SGSN: C3 + New SGSN-->MS: 20. RAU Complete + Note right of Target BSS: 21. PS Handover Complete Acknowledge + Target BSS-->Old SGSN: 21. PS Handover Complete Acknowledge + +``` + +Sequence diagram for Inter SGSN HO, Execution phase. Lifelines: MS, Source BSS, Target BSS, Old SGSN, New SGSN, GGSN, HLR. The diagram shows the flow of data and signaling messages during a handover from an old SGSN to a new SGSN. + +Figure 10: PS Handover Execution Phase; Inter-SGSN case (GERAN A/Gb mode → GERAN A/Gb mode) + +1. The old SGSN continues to receive GTP packets from the GGSN (via GTP) and forwards the associated PDU payload to the MS via the source BSS. +2. If a Tunnel Endpoint is available the old SGSN may, based on QoS, start N-PDU relay and duplication to the new SGSN. + +- For PDP context which uses LLC ADM in the old SGSN all new downlink N-PDUs received after completion of the PS handover preparation phase are relayed to the new SGSN. All such N-PDUs are encapsulated in a GTP-PDU when transmitted to the new SGSN. + +NOTE 1: The order of steps, starting from step 2 onwards, does not necessarily reflect the order of events. For instance the old SGSN may start data forwarding (step 2), send the **PS Handover Required Acknowledge** message (step 4) and send the **Forward SRNS Context** message (step 4a) almost simultaneously. + +3. The new SGSN may, based on QoS, proceed with the packet handling as follows: + - For PDP context(s) which uses LLC ABM the new SGSN stores the N-PDUs associated with their number into the SNDPCP queue. Data transfer prior the exchange of N-PDU SNs is not possible. + - For PDP context(s) which uses LLC ADM the new SGSN either + - a. forwards the received downlink N-PDUs to the target BSS; + - b. stores the received data into the SNDPCP queue for e.g. the PDU lifetime; + - c. discards the received data until e.g. reception of the **PS Handover Complete** message. + +If the new SGSN forwards downlink packets to the target BSS, the target BSS may start a blind transmission of downlink user data towards the MS over the allocated radio channels. + +4. The old SGSN continues the PS Handover procedure by sending a **PS Handover Required Acknowledge** (Old TLLI, PFCs Set Up List, Target BSS to Source BSS Transparent Container (PS Handover Command with RN part and CN part)) message to the source BSS. + +Before sending the **PS Handover Required Acknowledge** message, the old SGSN, based on QoS, may suspend downlink data transfer for any PDP contexts. + +Before sending the **PS Handover Command** message to the MS the source BSS, based on QoS, may try to empty the downlink BSS buffer for any BSS PFCs. + +NOTE 2: Only PFI(s) for PFCs accepted by the target cell are included in the message. + +- 4a. The old SGSN shall send the **Forward SRNS Context** (NSAPI, DL GTP-U number, UL GTP-U number) message to the new SGSN if there is at least one PDP context which requires "delivery order" to be preserved. NSAPI identifies the PDP context to which the GTP-U numbers apply. The **Forward SRNS Context** message is then acknowledged by the **Forward SRNS Context Acknowledge** message. The **Forward SRNS Context** message contains the sequence numbers of the GTP-PDU next to be transmitted in the uplink and downlink direction. After the **Forward SRNS Context** message is sent, further uplink N-PDUs received by the old SGSN from the source BSS, relative to a PDP context which requires "delivery order" to be preserved, shall not be forwarded to the GGSN. + +The GTP-U sequence numbers are only sent by the old SGSN for PDP context(s) requiring delivery order (QoS profile) to be preserved. If delivery order is to be preserved (QoS profile), consecutive GTP-PDU sequence numbering shall be maintained through the lifetime of the PDP context(s). + +Therefore, during the entire PS Handover procedure for the PDP context(s) using delivery order required (QoS profile), the responsible GTP-U entities (SGSNs and GGSN) shall assign consecutive GTP-PDU sequence numbers to user packets belonging to the same PDP context uplink and downlink, respectively. + +5. The source BSS sends the **PS Handover Command** (RN part, CN part) message to the MS by interrupting the transmission of LLC PDUs on any of the downlink TBFs. The RN part and the CN part are transparent information to the BSS. Following the transmission of this signalling message the source BSS may resume LLC PDU transmission until it either has no more LLC PDUs to send or the PFC is released. Upon reception of the **PS Handover Command** message the MS is not required to continue data reception in the source cell. Upon reception of the **PS Handover Command** message the MS shall suspend the uplink transmission of user plane data. The MS management of uplink N-PDUs following the reception of the **PS Handover Command** message is as follows: + +- All uplink packets associated with a PFC receiving handover treatment that have not yet been fully transmitted may be buffered depending on the QoS class. If the buffered uplink packets are transmitted in the new cell, they need to be ciphered using the new IOV-UI after the handover. + - Subsequent uplink packets that become available for transmission following the reception of the **PS Handover Command** message might also be buffered depending on the QoS class. + - The MS may discard uplink packets during the link interruption to preserve the real-time properties. +6. The MS tunes to the radio channel and the timeslot allocated in the target cell by the target BSS and may send the **PS Handover Access** (Handover Reference) message in the form of four handover access bursts to the target BSS on the allocated channel. The **PS Handover Command** message indicates whether or not the MS shall send **PS Handover Access** message. The target BSS sends a **Packet Physical information** message to the MS containing the timing advance for the MS to synchronise. + +NOTE 3: In the case of pre-synchronised handover the MS may receive the timing advance information to use in uplink in the target cell in the **PS Handover Command** message (if no timing advance information is included, the mobile station uses a default timing advance in the target cell). In a pre-synchronised or synchronised handover the **Packet Physical Information** message is not sent in the target cell. + +- 7./7a. After accessing the cell using access bursts and receiving timing advance information from the BSS in step 6, the MS processes the NAS container and then sends one **XID Response** message to the new SGSN. The MS sends this message immediately after receiving the **Packet Physical Information** message or, in a synchronised or pre-synchronised handover, immediately if the **PS Handover Access** message is not required to be sent (see Section 6.2). + +Upon sending the XID Response message the MS shall resume the user data transfer only for those NSAPIs for which there are radio resources allocated in the target cell. For NSAPIs using LLC ADM for which radio resources were not allocated in the target cell, the MS may request for radio resources using the legacy procedures. + +NOTE 4: If the new SGSN indicated Reset (i.e. reset to default parameters) in the NAS container for PS HO included in the PS Handover Command, in order to avoid collision cases the mobile station may avoid triggering XID negotiation for any LLC SAPI used in LLC ADM, but wait for the SGSN to do so (see bullet 12). In any case the mobile station may avoid triggering XID negotiation for any LLC SAPI used in LLC ABM, but wait for the SGSN to do so (see bullet 12a). + +8. Upon reception of the first correct RLC/MAC block (sent in normal burst format) from the MS the target BSS sends a **PS Handover Complete** (Local TLLI, IMSI, Request for Inter RAT Handover Info) message to inform the new SGSN that the MS has arrived in the target cell. Each uplink N-PDU received by the new SGSN via the target BSS is then forwarded directly to the GGSN. The target BSS that supports inter-RAT PS handover to UTRAN shall request the INTER RAT HANDOVER INFO from the SGSN if the 'Reliable INTER RAT HANDOVER INFO' is missing or set to '0' in the **PS Handover Request** message or if it has not received the INTER RAT HANDOVER INFO as part of the Source BSS to Target BSS transparent container. +9. Upon receiving the **PS Handover Complete** message, the new SGSN sends a **Forward Relocation Complete** message to the old SGSN. The old SGSN responds with a **Forward Relocation Complete Acknowledge** message. Upon the reception of the **Forward Relocation Complete** message the old SGSN starts a packet forwarding timer. The old SGSN stops forwarding of data to the new SGSN after the packet forwarding timer expires. +10. The new SGSN sends an **Update PDP Context Request** (New SGSN Address, TEID, QoS Negotiated) message to the GGSN concerned. The GGSN updates the PDP context fields and returns an **Update PDP Context Response** (TEID) message. From now on the GGSN sends new incoming downlink IP packets to the new SGSN instead of to the old SGSN. +11. After the reception of the **Forward Relocation Complete** message the old SGSN deletes to BSS packet flow context towards the old cell. The source BSS initiates the release of the radio resources in the source cell. +12. If the new SGSN indicated Reset (i.e. reset to default parameters) in the NAS container for PS HO included in the PS Handover Command, then on receipt of the **PS Handover Complete** message the new SGSN initiates an LLC/SNDCP XID negotiation for each LLC SAPI used in LLC ADM. In this case if the SGSN wants to use the default parameters, it shall send an empty XID Command. If the new SGSN indicated 'Reset to the old XID + +parameters' in the NAS container for PS HO, no further XID negotiation is required for LLC SAPs used in LLC ADM only. + +- 12a. The new SGSN re-establishes LLC ABM for the PDP contexts which use acknowledged information transfer. During the exchange of SABM and UA the SGSN shall perform LLC/SNDCP XID negotiation. + 13. The MS sends a **Routing Area Update Request** message to the new SGSN informing it that the target cell belongs to a new routing area. The MS shall send this message immediately after message 7. The new SGSN knows that a handover has been performed for this MS and can therefore exclude the SGSN context procedures that normally are used within the RA Update procedure. + 14. At this point the new SGSN may optionally invoke MS authentication (security function). The security function can be deferred and performed at any later time as well. +- NOTE 5: During an authentication procedure the SGSN has to suspend the downlink transmission of user data. +15. The new SGSN informs the HLR of the change of SGSN by sending **Update Location** (SGSN Number, SGSN Address, IMSI) message to the HLR. + 16. The HLR sends **Cancel Location** (IMSI, Cancellation Type) message to the old SGSN with Cancellation Type set to Update Procedure. The old SGSN acknowledges with a **Cancel Location Acknowledge** (IMSI) message. This message allows the old SGSN to know when to release the inter-SGSN tunnel. + 17. The HLR sends **Insert Subscriber Data** (IMSI, GPRS subscription data) message to the new SGSN. The new SGSN validates the MS presence in the (new) RA. If all checks are successful then the new SGSN constructs an MM context for the MS and returns an **Insert Subscriber Data Acknowledge** (IMSI) message to the HLR. This message allows the new SGSN to know when to release the inter-SGSN tunnel. + 18. The HLR acknowledges the Update Location by sending an **Update Location Acknowledge** (IMSI) message to the new SGSN. + 19. The new SGSN validates the MS presence in the new RA. If the MS is allowed to be attached in this RA, the SGSN updates the MM context for and sends a **Routing Area Update Accept** (P-TMSI, TMSI, P-TMSI signature, Receive N-PDU number) message to the MS. The Receive N-PDU Number contains the acknowledgements for each acknowledged-mode NSAPI used by the SGSN, thereby confirming all mobile-originated N-PDUs successfully transferred before the start of the PS handover procedure. + 20. The MS confirms the re-allocation of the new P-TMSI by responding the SGSN with a **Routing Area Update Complete** (Receive N-PDU number) message. The MS derives a new local TLLI from the new P-TMSI using current MM procedures. The Receive N-PDU Number contains the acknowledgements for each acknowledged-mode NSAPI used by the MS, thereby confirming all mobile-terminated N-PDUs successfully transferred before the start of the handover procedure. If Receive N-PDU Number confirms reception of N-PDUs that were forwarded from the old SGSN, these N-PDUs shall be discarded by the new SGSN. + +The following CAMEL procedure calls shall be performed (see referenced procedures in TS 23.078 [8b]) + +- C1) CAMEL\_GPRS\_PDP\_Context\_Disconnection, CAMEL\_GPRS\_Detach and CAMEL\_PS\_Notification. + +They are called in the following order: + +- The CAMEL\_GPRS\_PDP\_Context\_Disconnection procedure is called several times: once per PDP context. The procedure returns as result "Continue". +- Then the CAMEL\_GPRS\_Detach procedure is called once. The procedure returns as result "Continue". +- Then the CAMEL\_PS\_Notification procedure is called once. The procedure returns as result "Continue". + +- C2) CAMEL\_GPRS\_Routeing\_Area\_Update\_Session and CAMEL\_PS\_Notification. + +They are called in the following order: + +- The CAMEL\_GPRS\_Routeing\_Area\_Update\_Session procedure is called. The procedure returns as result "Continue". +- Then, the CAMEL\_PS\_Notification procedure is called. The procedure returns as result "Continue". + +C3) CAMEL\_GPRS\_Routeing\_Area\_Update\_Context. + +This procedure is called several times: once per PDP context. It returns as result "Continue". + +For C2 and C3: refer to Routing Area Update procedure description in 3GPP TS 23.060. + +21. Upon reception of the **PS Handover Complete** message with the "Request for Inter RAT Handover Info" set to "1" for UTRAN, the SGSN shall send **PS Handover Complete Acknowledge** (TLLI, Inter RAT Handover Info) message to the target BSS. +22. The target BSS receiving the **PS Handover Complete Acknowledge** message shall set the 'Reliable INTER RAT HANDOVER' to '1' in the **PS Handover Required** message in any subsequent PS handover to GERAN *A/Gb mode*. The target BSS failing to receive the **PS Handover Complete Acknowledge** message shall set the 'Reliable INTER RAT HANDOVER' to '0' in the **PS Handover Required** message in any subsequent PS handover to GERAN *A/Gb mode*. The Target BSS shall, upon receipt of the INTER RAT HANDOVER INFO in the **PS Handover Complete Acknowledge** message, discard the INTER RAT HANDOVER INFO received from the source BSS during the preparation phase. + +## 5.2 Inter-RAT/mode handover (GERAN *A/Gb mode* → UTRAN/ GERAN *Iu mode*) + +### 5.2.1 Intra SGSN + +#### 5.2.1.1 Intra-SGSN GERAN *A/Gb mode* to UTRAN/GERAN *Iu mode* HO; Preparation phase + +![Sequence diagram of the PS Handover Preparation Phase for Intra-SGSN case. The diagram shows four entities: MS, Source BSS, Target RNC/BSS, and 3G/2G SGSN. The process starts with a '1. Handover decision' (dashed box) between MS and Source BSS. Then, the Source BSS sends a '2. PS Handover Required' message to the 3G/2G SGSN. The 3G/2G SGSN sends a '3. Relocation Request' to the Target RNC/BSS, which responds with a '4. Relocation Request Acknowledge'.](05d8710f69c476939295486ab1440350_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Source BSS + participant Target RNC/BSS + participant 3G/2G SGSN + Note left of Source BSS: 1. Handover decision + Source BSS->>3G/2G SGSN: 2. PS Handover Required + 3G/2G SGSN->>Target RNC/BSS: 3. Relocation Request + Target RNC/BSS-->>3G/2G SGSN: 4. Relocation Request Acknowledge + +``` + +Sequence diagram of the PS Handover Preparation Phase for Intra-SGSN case. The diagram shows four entities: MS, Source BSS, Target RNC/BSS, and 3G/2G SGSN. The process starts with a '1. Handover decision' (dashed box) between MS and Source BSS. Then, the Source BSS sends a '2. PS Handover Required' message to the 3G/2G SGSN. The 3G/2G SGSN sends a '3. Relocation Request' to the Target RNC/BSS, which responds with a '4. Relocation Request Acknowledge'. + +**Figure 11: PS Handover Preparation Phase; Inter-RAT/mode, +Intra-SGSN case (GERAN *A/Gb mode* → UTRAN, GERAN *Iu mode*)** + +1. The source BSS decides to initiate a PS handover. At this point both uplink and downlink user data is transmitted via the following: TBFs between MS and source BSS, BSSGP PFCs tunnel(s) between the source BSS and 3G/2G SGSN, GTP tunnel(s) between the 3G/2G SGSN and GGSN. +2. The source BSS sends a **PS Handover Required** (TLLI, Cause, Source Cell Identifier, Target RNC Identifier, Source to Target Transparent Container, Active PFCs List) message to the SGSN. + +If PS handover to a UTRAN CSG cell or Hybrid cell is required, the source BSS includes in addition to the Target RNC Identifier also the CSG Identifier in the **PS Handover Required** message to the SGSN. In case of PS handover to an UTRAN CSG cell the source BSS sets the Cell Access Mode field to "CSG Cell" in the CSG Identifier. In case of PS handover to an UTRAN hybrid cell the source BSS sets the Cell Access Mode field to "Hybrid Cell" in the CSG Identifier. + +Upon reception of the **PS Handover Required** message containing a CSG Identifier with the Cell Access Mode field set to "CSG cell", the 3G/2G SGSN performs the access control according to the CSG Subscription List of that MS. If the MS is allowed to access the target cell, the 3G/2G SGSN continues the PS handover to the target RNC. If the MS is not allowed to access the target cell, the 3G/2G SGSN sends the **PS Handover Required Negative Acknowledge** message with an appropriate cause value indicating invalid CSG cell to the source BSS. If the **PS Handover Required** message contains a CSG Identifier with the Cell Access Mode field set to + +“Hybrid Cell”, the 3G/2G SGSN provides the membership status of the MS and the CSG Id to the target RNC (see 3GPP TS25.413). + +3. The 3G/2G SGSN determines from the Target RNC Identifier that the type of handover is inter-RAT/mode handover. In case of Inter-RAT/Intra-SGSN PS handover, the 3G/2G SGSN constructs a **Relocation Request** (Permanent NAS Identity, Cause, CN Domain Indicator, Integrity protection information (i.e. IK and allowed Integrity Protection algorithms, Encryption information (i.e. CK and allowed Ciphering algorithms), RABs To Be Set Up List, Source to Target Transparent Container, Iu Signalling connection identifier, Global CN-ID, SNA Access Information, UESBI-Iu) message to the target RNC/BSS. + +For each RAB requested to be established, the RABs To Be Set Up List shall contain information such as RAB ID, RAB parameters, Transport Layer Address, and Iu Transport Association. The 3G/2G SGSN shall only request resources for RABs for which the corresponding PFC is included in the Active PFCs List. The RAB ID information element contains the NSAPI value, and the RAB parameters information element gives the QoS profile. The Transport Layer Address is the SGSN Address for user data, and the Iu Transport Association corresponds to the uplink Tunnel Endpoint Identifier Data. The SGSN may decide to establish a Direct Tunnel. In this case the SGSN provides to the target RNC the GGSN Address for User Plane and Uplink TEID for data. + +Ciphering and integrity protection keys are sent to the target RNC/BSS to allow data transfer to continue in the new RAT/mode target cell without requiring a new AKA (Authentication and Key Agreement) procedure. Information that is required to be sent to the MS (either in the **PS Handover Command** message or after the handover completion message) from RRC in the target RNC/BSS shall be included in the RRC message sent from the target RNC/BSS to the MS via the transparent container. + +In the target RNC/BSS radio and Iu user plane resources are reserved for the accepted RABs. + +In case of PS handover to a CSG cell, the 3G/2G SGSN includes also the CSG ID in the **Relocation Request** message to the target RNC. + +In case of PS handover to a Hybrid cell, the 3G/2G SGSN includes also the CSG ID and CSG Membership Status in the **Relocation Request** message to the target RNC. The target RNC may use the CSG Membership Status to perform differentiated treatment for CSG and non-CSG members (see 3GPP TS25.413). + +4. The target RNC/BSS sends the **Relocation Request Acknowledge** (Target to Source Transparent Container, RABs setup list, RABs failed to setup list) message to the 3G/2G SGSN. Upon sending the **Relocation Request Acknowledge** message the target RNC/BSS shall be prepared to receive downlink GTP PDUs from the 3G/2G SGSN for the accepted RABs. + +Each RAB to be setup is defined by a Transport Layer Address, which is the target RNC/BSS Address for user data, and the Iu Transport Association, which corresponds to the downlink Tunnel Endpoint Identifier for user data. + +NOTE: The information to be included in the containers differs for UTRAN and GERAN Iu mode. For UTRAN, the information included in the container is related to RAB setup and other IE similar to those in the **Handover to UTRAN** message defined in 3GPP TS 25.331 [17]. For GERAN Iu mode the **Radio Bearer Reconfiguration** message defined in 3GPP TS 44.118 [16] is the RRC message to be included. + +When the 3G/2G SGSN receives the **Relocation Request Acknowledge** message and it decides to proceed with the handover, the preparation phase is finished and the execution phase will follow. + +#### 5.2.1.2 Intra-SGSN GERAN A/Gb *mode* to UTRAN/GERAN Iu *mode* HO; Execution phase + +![Sequence diagram of PS Handover Execution Phase for Intra-SGSN GERAN A/Gb mode to UTRAN/GERAN Iu mode HO. The diagram shows interactions between MS, Source BSS, Target RNC/BSS, 3G/2G SGSN, and GGSN. The process involves IP packet forwarding, context transfer, handover commands, execution, and finalization steps including RAU procedures.](08c7a76a7786bd08b99dd4cb41583ef4_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Source BSS + participant Target RNC/BSS + participant 3G/2G SGSN + participant GGSN + + Note right of 3G/2G SGSN: Sending of uplink data possible + GGSN-->>3G/2G SGSN: 1. IP packets to source BSS + 3G/2G SGSN-->>Source BSS: 1. IP packets to source BSS + Source BSS-->>MS: 5. PS Handover Command + 3G/2G SGSN-->>Target RNC/BSS: 2. Send relayed N-PDUs over the allocated RABs + Target RNC/BSS-->>Source BSS: 3. PS Handover Required Acknowledge + Source BSS-->>MS: 6. UTRAN Handover Execution or GERAN Iu Access Bursts, Physical Info + Target RNC/BSS-->>3G/2G SGSN: 4. Forward SRNS Context + 3G/2G SGSN-->>Target RNC/BSS: 7. Relocation Detect + Target RNC/BSS-->>MS: 8. Handover to UTRAN Complete or Radio Bearer Reconfiguration Complete (GERAN Iu) (for GERAN Iu) + Target RNC/BSS-->>3G/2G SGSN: 9. Relocation Complete + 3G/2G SGSN-->>GGSN: 10. Update PDP Context Request + GGSN-->>3G/2G SGSN: 10. Update PDP Context Response + 3G/2G SGSN-->>Target RNC/BSS: 1a. IP packets to target RNC/BSS + Target RNC/BSS-->>MS: 1b. IP packets to target RNC (Direct Tunnel) + Target RNC/BSS-->>Source BSS: 11. BSS Packet Flow procedures + Target RNC/BSS-->>3G/2G SGSN: 12. RAU request + Note right of 3G/2G SGSN: C2 + 3G/2G SGSN-->>MS: 13. RAU accept + Note right of 3G/2G SGSN: C3 + 3G/2G SGSN-->>Target RNC/BSS: 14. RAU Complete + +``` + +Sequence diagram of PS Handover Execution Phase for Intra-SGSN GERAN A/Gb mode to UTRAN/GERAN Iu mode HO. The diagram shows interactions between MS, Source BSS, Target RNC/BSS, 3G/2G SGSN, and GGSN. The process involves IP packet forwarding, context transfer, handover commands, execution, and finalization steps including RAU procedures. + +**Figure 12: PS Handover Execution Phase; Inter-RAT/mode, Intra-SGSN case (GERAN A/Gb *mode* → UTRAN, GERAN Iu *mode*)** + +1. The 3G/2G SGSN continues to receive IP packets from the GGSN (via GTP) and forwards the associated PDU payload to the MS via the source BSS. +2. When receiving the **Relocation Request Acknowledge** message the 3G/2G SGSN may, based on QoS, start downlink N-PDU relay and duplication to the target RNC/BSS if a Tunnel Endpoint is available as follows: + +- For PDP context, which uses LLC ADM, all new downlink N-PDUs received after completion of the PS handover preparation phase are relayed to the target RNC. All such N-PDUs are encapsulated in a GTP-PDU when transmitted to the target RNC/BSS. + - If the 3G/2G SGSN forwards downlink packets to the target RNC/BSS, the target RNC/BSS may start blind transmission of downlink user data towards the MS over the allocated radio channels. +3. The 3G/2G SGSN continues the PS Handover by sending a **PS Handover Required Acknowledge** (TLLI, List of Set Up PFCs, Target to Source Transparent Container) message to the source BSS. + +Before sending the **PS Handover Required Acknowledge** message, the 3G/2G SGSN, based on QoS, may suspend downlink data transfer for any PDP contexts. + +Before sending the **PS Handover Command** message to the MS the source BSS, based on QoS, may try to empty the downlink BSS buffer for any BSS PFCs. + +4. The 3G/2G SGSN shall send the **Forward SRNS Context** (NSAPIDL GTP-U number, UL GTP-U number) message to the target RNC/BSS if there is at least one PDP context which requires "delivery order" to be preserved..NSAPI identifies the PDP context to which the GTP-U numbers apply The **Forward SRNS Context** message contains the sequence numbers of the GTP-PDU next to be transmitted in the uplink and downlink direction. After the **Forward SRNS Context** message is sent, further uplink N-PDUs received by the 3G/2G SGSN from the source BSS, relative to a PDP context which requires "delivery order" to be preserved, shall not be forwarded to the GGSN. + +The GTP-U numbers are only sent by the 3G/2G SGSN for PDP context(s) requiring delivery order (QoS profile) to be preserved. If delivery order is to be preserved (QoS) profile), consecutive GTP-PDU sequence numbering shall be maintained through the lifetime of the PDP context(s). + +Therefore, during the entire PS Handover procedure for the PDP context(s) using delivery order required (QoS profile), the responsible GTP-U entities (3G/2G SGSN, target RNC/BSS and GGSN) shall assign consecutive GTP-PDU sequence numbers to user packets belonging to the same PDP context uplink and downlink, respectively. + +The target RNC/BSS proceed as follows: + +- For RABs not requiring lossless PDCP the target RNC/BSS may, according the QoS profile of the PDP context, store the received data until it receives confirmation of MS presence in the target cell. + +The further target RNC/BSS behaviour is as specified in 3GPP TS 23.060 [19] (Combined Hard Handover and SRNS Relocation). + +5. The source BSS sends the **PS Handover Command** message containing the **Handover to UTRAN Command** message (as it is specified in 3GPP TS 25.331 [17]) or **Radio Bearer Reconfiguration** message (as it is specified in 3GPP TS 44.118 [16]) to the MS by interrupting the transmission of LLC PDUs on any of the downlink TBFs. Following the transmission of this signalling message the source BSS may resume LLC PDU transmission until it either has no more LLC PDUs to send or the PFC is released. Upon reception of the **PS Handover Command** the MS is not required to continue data reception in the source cell. Upon reception of the **PS Handover Command** the MS shall suspend the uplink transmission of user plane data. MS management of uplink N-PDUs following the reception of the **PS Handover Command** message is as follows: +- All N-PDUs associated with a PFC receiving handover treatment that have not yet been fully transmitted might be buffered depending on the QoS class. + - Subsequent uplink N-PDUs that become available for transmission following the reception of the **PS Handover Command** message might also be buffered depending on the QoS class. + - For real time services uplink N-PDUs may be discarded by the MS during the link interruption. + +NOTE: Any buffering should be performed before the data is passed to SNDPCP in order to avoid header compression on N-PDUs such that data delivery in the target cell may begin from the correct point in the sequence. + +6. MS is in the target cell and performs access to UTRAN as defined in 3GPP TS 25.331 [17] and to GERAN Iu mode as defined in 3GPP TS 44.118 [16]. + +7. The target RNC/BSS sends a **Relocation Detect** message to the 3G/2G SGSN to indicate that the MS is in the target cell. The message shall be sent when the relocation execution trigger is received. For SRNS relocation type "UE Involved", the relocation execution trigger may be received from the Uu interface; i.e. when the target RNC detects the MS on the lower layers. When the **Relocation Detect** message is sent, the target RNC shall start serving RNC operation. +8. In UTRAN, the MS sends **Handover to UTRAN Complete** {Message Type, UE Information elements (Start List, CN Domain Identity, Start), RB Information Elements (Count-C Activation Time)} message to the target RNC (see 3GPP TS 25.331 [17]). + +In GERAN Iu, the MS sends **Radio Bearer Reconfiguration Complete** {RRC Transaction Identifier, Integrity Check Info, Uplink Integrity Protection Activation Info, COUNT-C Activation Time, Radio Bearer Uplink Ciphering Activation Time Info, Mobile Observed Time Difference, Uplink Counter Synchronisation Info struct, START List, CN Domain Identity, START, RB with PDCP Information List, RB with PDCP Information} message to target BSS. + +9. When the new source RNC-ID + S-RNTI are successfully exchanged with the MS, the target RNC/BSS shall send the **Relocation Complete** message to the new SGSN. The purpose of the Relocation Complete procedure is to indicate by the target RNC/BSS the completion of the relocation of the source BSS to the CN. After the reception of the **Relocation Complete** message the 3G/2G SGSN shall be prepared to receive data from the target RNC/BSS. +10. If the SGSN has established Direct Tunnel, the SGSN sends an **Update PDP Context Request** (RNC Address, TEID, QoS Negotiated, DTI) message to the GGSN concerned. The SGSN provides to the GGSN the RNC address for the User Plane and TEID for downlink data and shall include the DTI to instruct the GGSN to apply Direct Tunnel specific error handling procedure as defined in 3GPP TS 23.060 [19]. The GGSN updates the PDP context fields and returns an **Update PDP Context Response** (TEID) message. From now on the GGSN sends new incoming downlink IP packets to the target RNC instead of the SGSN. +11. The 3G/2G SGSN shall initiate PFC Management procedures towards the source cell in order to trigger the release of resources in the source cell. +12. The MS sends a **Routing Area Update Request** (Old RAI, Old P-TMSI signature, Update Type) message to the 3G/2G SGSN. This is done even if the target cell belongs to the same routing area as the source cell. The MS shall send this message immediately after message 8. The 3G/2G SGSN knows that a handover has been performed for this MS and can therefore exclude the SGSN context procedures which normally are used within the RA Update procedure. +13. The 3G/2G SGSN validates the MS presence in the new RA. If the MS is allowed to be attached in this RA, the 3G/2G SGSN updates the MM context for and sends a **Routing Area Update Accept** message to the MS. +14. The MS may respond to the SGSN with a **Routing Area Update Complete** message. + +The following CAMEL procedure calls shall be performed (see referenced procedures in TS 23.078 [8b]): + +- C2) CAMEL\_GPRS\_Routeing\_Area\_Update\_Session and CAMEL\_PS\_Notification. + +They are called in the following order: + +- The CAMEL\_GPRS\_Routeing\_Area\_Update\_Session procedure is called. The procedure returns as result "Continue". +- Then, the CAMEL\_PS\_Notification procedure is called. The procedure returns as result "Continue". + +- C3) CAMEL\_GPRS\_Routeing\_Area\_Update\_Context. + +This procedure is called several times: once per PDP context. It returns as result "Continue". + +For C2 and C3: refer to Routing Area Update procedure description in 3GPP TS 23.060. + +### 5.2.2 Inter SGSN + +#### 5.2.2.1 Inter-SGSN GERAN A/Gb *mode* to UTRAN/GERAN Iu *mode* HO; Preparation phase + +![Sequence diagram of PS Handover Preparation Phase for Inter-RAT/mode, Inter-SGSN case (GERAN A/Gb mode to UTRAN, GERAN Iu mode). The diagram shows five lifelines: MS, Source BSS, Target RNC/BSS, 2G SGSN, and 3G SGSN. The sequence of messages is: 1. Handover decision (dashed box between MS and Source BSS); 2. PS Handover Required (Source BSS to 2G SGSN); 3. Forward Relocation Request (2G SGSN to 3G SGSN); 4. Relocation Request (3G SGSN to Target RNC/BSS); 5. Relocation Request Acknowledge (Target RNC/BSS to 3G SGSN); 6. Forward Relocation Response (3G SGSN to 2G SGSN).](0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Source BSS + participant Target RNC/BSS + participant 2G SGSN + participant 3G SGSN + Note left of Source BSS: 1. Handover decision + Source BSS->>2G SGSN: 2. PS Handover Required + 2G SGSN->>3G SGSN: 3. Forward Relocation Request + 3G SGSN->>Target RNC/BSS: 4. Relocation Request + Target RNC/BSS->>3G SGSN: 5. Relocation Request Acknowledge + 3G SGSN->>2G SGSN: 6. Forward Relocation Response + +``` + +Sequence diagram of PS Handover Preparation Phase for Inter-RAT/mode, Inter-SGSN case (GERAN A/Gb mode to UTRAN, GERAN Iu mode). The diagram shows five lifelines: MS, Source BSS, Target RNC/BSS, 2G SGSN, and 3G SGSN. The sequence of messages is: 1. Handover decision (dashed box between MS and Source BSS); 2. PS Handover Required (Source BSS to 2G SGSN); 3. Forward Relocation Request (2G SGSN to 3G SGSN); 4. Relocation Request (3G SGSN to Target RNC/BSS); 5. Relocation Request Acknowledge (Target RNC/BSS to 3G SGSN); 6. Forward Relocation Response (3G SGSN to 2G SGSN). + +**Figure 13: PS Handover Preparation Phase; Inter-RAT/mode, Inter-SGSN case (GERAN A/Gb *mode* → UTRAN, GERAN Iu *mode*)** + +1. The source BSS decides to initiate a PS handover. At this point both uplink and downlink user data is transmitted via the following: TBFs between MS and source BSS, BSSGP PFCs tunnel(s) between source BSS and old SGSN, GTP tunnel(s) between old SGSN and GGSN. +2. The source BSS sends a **PS Handover Required** (TLLI, Cause, Source Cell Identifier, Target RNC Identifier, Source to Target Transparent Container, Active PFCs List) message to the old SGSN. + +If PS handover to a UTRAN CSG or Hybrid cell is required, the source BSS includes in addition to Target RNC Identifier also the CSG Identifier in the **PS Handover Required** message to the SGSN. In case of PS handover to an UTRAN CSG cell the source BSS sets the Cell Access Mode field to “CSG Cell” in the CSG Identifier. In case of PS handover to an UTRAN hybrid cell the source BSS sets the Cell Access Mode field to “Hybrid Cell” in the CSG Identifier. + +Upon reception of the **PS Handover Required** message containing a CSG Identifier with the Cell Access Mode field set to “CSG cell”, the old SGSN performs the access control according to the CSG Subscription List of that MS. If the MS is allowed to access the target cell, the old SGSN continues the PS handover to the target side. If the MS is not allowed to access the target cell, the old SGSN sends the **PS Handover Required Negative Acknowledge** message with an appropriate cause value indicating invalid CSG cell to the source BSS. If the **PS Handover Required** message contains a CSG Identifier with the Cell Access Mode field set to “Hybrid Cell”, the old SGSN provides the membership status of the MS and the CSG Id to the target side (see 3GPP TS 25.413). + +3. The old SGSN determines from the Target RNC Identifier that the type of handover is inter-RAT/mode handover. In case of inter-SGSN inter-RAT/mode PS handover the old SGSN initiates the relocation resource allocation procedure by sending a **Forward Relocation Request** (IMSI, Target Identification, MM Context, PDP Context, PDP Context Prioritisation, Tunnel Endpoint Identifier Control Plane, SGSN Address for Control plane, Source to Target Transparent Container in the UTRAN Transparent Container, RANAP Cause, Packet Flow ID, SNDPCP XID parameters, LLC XID parameters, GCSI) message to the new SGSN. + +The old SGSN sends all active PDP Contexts to the new SGSN indicating the PFIs and the XID parameters related to those PDP Contexts. Each PDP context contains the GGSN Address for the User Plane and the Uplink TEID for Data (to this GGSN Address and Uplink TEID for Data the old SGSN and the new SGSN send uplink packets). + +The MM context contains security related information, e.g. supported ciphering algorithms as described in 3GPP TS 29.060 [11]. The relation between GSM and UMTS security parameters is defined in 3GPP TS 33.102 [27]. + +Optionally the old SGSN sets the GCSI flag if the MM context contains GPRS CAMEL Subscription Information. + +NOTE 1: For relocation to an area where Intra Domain Connection of RAN Nodes to Multiple CN Nodes is used, the old SGSN may - if it provides Intra Domain Connection of RAN Nodes to Multiple CN Nodes - have multiple new SGSNs for each handover target in a pool area, in which case the old SGSN will select one of them to become the new SGSN, as specified in 3GPP TS 23.236 [22]. + +Upon receipt of the message, the new SGSN establishes all MM and PDP contexts and initiates the RAB setup procedures for all PDP contexts received. + +4. The new SGSN sends a **Relocation Request** (Permanent NAS Identity, Cause, CN Domain Indicator, Integrity protection information (i.e. IK and allowed Integrity Protection algorithms), Encryption information (i.e. CK and allowed Ciphering algorithms), RABs to be setup list, Source to Target Transparent Container, Iu Signalling connection identifier, Global CN-ID, SNA Access Information, UESBI-Iu) message to the target RNC/BSS. + +For each RAB requested to be established, RABs To Be Setup shall contain information such as RAB ID, RAB parameters, Transport Layer Address, and Iu Transport Association. The new SGSN shall not request resources for RABs associated with PDP contexts with a maximum bit rate for uplink and downlink of 0 kbit/s or for which the Activity Status Indicator within the PDP Context indicates that no active PFC exists on the source side. The RAB ID information element contains the NSAPI value, and the RAB parameters information element gives the QoS profile. The Transport Layer Address is the SGSN Address for user data, and the Iu Transport Association corresponds to the uplink Tunnel Endpoint Identifier Data. The SGSN may decide to establish a Direct Tunnel unless it has received a 'set' GCSI flag from the old SGSN. If the new SGSN decides to establish Direct Tunnel, it provides to the target RNC the SGSN Address for User Plane and TEID for Uplink data. + +Ciphering and integrity protection keys are sent to the target RNC/BSS to allow data transfer to continue in the new RAT/mode target cell without requiring a new AKA (Authentication and Key Agreement) procedure. Information that is required to be sent to the MS (either in the **PS Handover Command** message or after the handover completion message) from RRC in the target RNC/BSS shall be included in the RRC message sent from the target RNC/BSS to the MS via the transparent container. + +In the target RNC/BSS radio and Iu user plane resources are reserved for the accepted RABs. + +In case of PS handover to a CSG cell, the 3G SGSN includes also the CSG ID in the **Relocation Request** message to the target RNC. + +In case of PS handover to a Hybrid cell, the 3G SGSN includes also the CSG ID and CSG Membership Status in the **Relocation Request** message to the target RNC. The target RNC may use the CSG Membership Status to perform differentiated treatment for CSG and non-CSG members (see 3GPP TS 25.413). + +5. The target RNC/BSS sends the **Relocation Request Acknowledge** (Source to Target Transparent Container, RABs setup list, RABs failed to setup list) message to the new SGSN. Upon sending the **Relocation Request Acknowledge** message the target RNC/BSS shall be prepared to receive downlink GTP PDUs from the new SGSN for the accepted RABs. + +Each RAB to be setup is defined by a Transport Layer Address, which is the target RNC/BSS Address for user data, and the Iu Transport Association, which corresponds to the downlink Tunnel Endpoint Identifier for user data. + +NOTE 2: The information to be included in the containers differs for UTRAN and GERAN Iu mode. For UTRAN, the information included in the container is related to RAB setup and other IE similar to those in the **Handover to UTRAN** message defined in 3GPP TS 25.331 [17]. For GERAN *Iu mode* the **Radio Bearer Reconfiguration** message defined in 3GPP TS 44.118 [16] is the RRC message to be included. + +6. When resources for the transmission of user data between target RNC/BSS and new SGSN have been allocated and the new SGSN is ready for the PS handover, the **Forward Relocation Response** (Cause, List of Set Up PFCs, Tunnel Endpoint Identifier Control Plane, SGSN Address for User Traffic, Tunnel Endpoint Identifier Data II, RANAP cause, SGSN Address for control plane, Source to Target Transparent Container in the UTRAN Transparent Container) message is sent from the new SGSN to the old SGSN. RANAP Cause contain information from the target RNC/BSS to be forwarded to the source BSS. + +The Tunnel Endpoint Identifier Data II, one information for each PDP context, is the tunnel endpoint of the new SGSN and is used for data forwarding from the old SGSN, via the new SGSN, to the target RNC. + +When the old SGSN receives the **Forward Relocation Response** message and it decides to proceed with the handover, the preparation phase is finished and the execution phase will follow. + +#### 5.2.2.2 + +##### Inter-SGSN GERAN A/Gb *mode* to UTRAN/GERAN Iu *mode* HO; Execution phase + +![Sequence diagram of PS Handover Execution Phase for Inter-RAT/mode, Inter-SGSN case (GERAN A/Gb mode to UTRAN/GERAN Iu mode).](82fbb97c1145cac89ac72dd080fad17a_img.jpg) + +The sequence diagram illustrates the execution phase of a PS handover between a GERAN A/Gb mode and a UTRAN/GERAN Iu mode. The participants are MS, Source BSS, Target RNC / BSS, Old 2G-SGSN, New 3G-SGSN, GGSN, and HLR. The process involves several steps: 1. IP packets are forwarded from GGSN to Old 2G-SGSN. 2. N-PDUs are relayed from Old 2G-SGSN to New 3G-SGSN and then to Target RNC/BSS. 3. PS Handover Required is sent from Old 2G-SGSN to Target RNC/BSS. 4. PS Handover Command is sent from Target RNC/BSS to MS. 4a. Forward SRNS Context is sent from Old 2G-SGSN to New 3G-SGSN. 5. UTRAN Handover Execution is initiated. 6. GERAN Iu Access Bursts Physical Info is sent from MS to Target RNC/BSS. 7. Relocation Detect is sent from New 3G-SGSN to Old 2G-SGSN. 8. Handover to UTRAN Complete is sent from Target RNC/BSS to MS. 8a. Radio Bearer Reconfiguration Complete is sent from Target RNC/BSS to MS. 9. Relocation Complete is sent from Target RNC/BSS to Old 2G-SGSN. 10. Forward Relocation Complete is sent from Old 2G-SGSN to New 3G-SGSN. 11. Update PDP Context Request is sent from New 3G-SGSN to GGSN. 12. BSS Packet Flow procedures are initiated. 13. RAU Request Security functions are sent from Target RNC/BSS to MS. 14. Update location is sent from New 3G-SGSN to HLR. 15. Cancel location is sent from HLR to Old 2G-SGSN. 16. Cancel location ack is sent from Old 2G-SGSN to HLR. 17. Insert subscriber data is sent from HLR to New 3G-SGSN. 18. Insert subscriber data ack is sent from New 3G-SGSN to HLR. 19. Update location ack is sent from HLR to New 3G-SGSN. 20. RAU accept is sent from MS to Target RNC/BSS. 21. RAU Complete is sent from Target RNC/BSS to MS. + +Sequence diagram of PS Handover Execution Phase for Inter-RAT/mode, Inter-SGSN case (GERAN A/Gb mode to UTRAN/GERAN Iu mode). + +**Figure 14: PS Handover Execution Phase; Inter-RAT/mode, Inter-SGSN case (GERAN A/Gb *mode* → UTRAN/GERAN Iu *mode*)** + +- The old SGSN continues to receive IP packets from the GGSN (via GTP) and forwards the associated PDU payload to the MS via the source BSS. +- When receiving the **Forward Relocation Response** message the old SGSN may, based on QoS, start downlink N-PDU relay and duplication to the target RNC/BSS via the new SGSN (if a Tunnel Endpoint is available) as follows: + - For PDP context, which uses LLC ADM in the old SGSN all new downlink N-PDUs received after completion of the PS handover preparation phase are relayed to the target RNC/BSS via the new SGSN. All such N-PDUs are encapsulated in a GTP-PDU when transmitted to the new SGSN. + +If the old SGSN forwards downlink packets to the target RNC/BSS via the new SGSN, the target RNC/BSS may start blind transmission of downlink user data towards the MS over the allocated radio channels. + +NOTE 1: The order of steps, starting from step 2 onwards, does not necessarily reflect the order of events. For instance the old SGSN may start data forwarding (step 2), send the **PS Handover Required Acknowledge** message (step 4) and send the Forward SRNS context message (step 4a) almost simultaneously. + +3. Void +4. The old SGSN continues the PS Handover by sending a **PS Handover Required Acknowledge** (TLLI, List of Set Up PFCs, Source to Target Transparent Container) message to the source BSS. + +Before sending the **PS Handover Required Acknowledge** message, the old SGSN, based on QoS, may suspend downlink data transfer for any PDP contexts. + +Before sending the **PS Handover Command** message to the MS the source BSS, based on QoS, may try to empty the downlink BSS buffer for any BSS PFCs. + +- 4a. The old SGSN shall send the **Forward SRNS Context** message (NSAPI, DL GTP-U number, UL GTP-U number) to the new SGSN if there is at least one PDP context which requires "delivery order" to be preserved. NSAPI identifies the PDP context to which the GTP-U numbers apply. The **Forward SRNS Context** message is then acknowledged by the **Forward SRNS Context Acknowledge** message. The **Forward SRNS Context** message contains the sequence numbers of the GTP-PDU next to be transmitted in the uplink and downlink direction. After the **Forward SRNS Context** message is sent, further uplink N-PDUs received by the old SGSN from the source BSS, relative to a PDP context which requires "delivery order" to be preserved, shall not be forwarded to the GGSN. + +The GTP-U numbers are only sent by the old SGSN for PDP context(s) requiring delivery order (QoS profile) to be preserved. If delivery order is to be preserved (QoS profile), consecutive GTP-PDU sequence numbering shall be maintained through the lifetime of the PDP context(s). + +Therefore, during the entire PS Handover procedure for the PDP context(s) using delivery order required (QoS profile), the responsible GTP-U entities (old SGSN, target RNC and GGSN) shall assign consecutive GTP-PDU sequence numbers to user packets belonging to the same PDP context uplink and downlink, respectively. + +The target RNC proceed as follows: + +- For RABs not requiring lossless PDCP the target RNC may, according the QoS profile of the PDP context, store the received data until it receives confirmation of MS presence in the target cell. + +The further target RNC/BSS behaviour is as specified in 3GPP TS 23.060 [19] (Combined Hard Handover and SRNS Relocation). + +5. The source BSS sends the **PS Handover Command** message containing the **Handover to UTRAN Command** message (as specified in 3GPP TS 25.331 [17]) or **Radio Bearer Reconfiguration** message (as specified in 3GPP TS 44.118 [16]) to the MS by interrupting the transmission of LLC PDUs on any of the downlink TBFs. Following the transmission of this signalling message the source BSS may resume LLC PDU transmission until it either has no more LLC PDUs to send or the PFC is released. Upon reception of the **PS Handover Command** message the MS is not required to continue data reception in the source cell. Upon reception of the **PS Handover Command** message the MS shall suspend the uplink transmission of user plane data. MS management of uplink N-PDUs following the reception of the **PS Handover Command** message is as follows: + - All N-PDUs associated with a PFC receiving handover treatment that have not yet been fully transmitted might be buffered depending on the QoS class. + - Subsequent uplink N-PDUs that become available for transmission following the reception of the **PS Handover Command** message might also be buffered depending on the QoS class. + - For real time services uplink N-PDUs may be discarded by the MS during the link interruption. + +NOTE 2: Any buffering should be performed before the data is passed to SNDPCP in order to avoid header compression on N-PDUs such that data delivery in the target cell may begin from the correct point in the sequence. + +6. MS is in the target cell and performs access to UTRAN as defined in 3GPP TS 25.331 [17] and to GERAN Iu mode as defined in 3GPP TS 44.118 [16]. +7. Target RNC/BSS sends a **Relocation Detect** message to the new SGSN to indicate that the MS is in the target cell. The message shall be sent when the relocation execution trigger is received. For SRNS relocation type "UE Involved", the relocation execution trigger may be received from the Uu interface; i.e. when the target RNC detects the MS on the lower layers. When the **Relocation Detect** message is sent, the target RNC shall start serving RNC operation. +8. In UTRAN, MS sends **Handover to UTRAN Complete** {Message Type, UE Information elements (Start List, CN Domain Identity, Start), RB Information Elements (Count-C Activation Time)} message to the target RNC (see 3GPP TS 25.331 [17]). + +In GERAN Iu, MS sends **Radio Bearer Reconfiguration Complete** {RRC Transaction Identifier, Integrity Check Info, Uplink Integrity Protection Activation Info, COUNT-C Activation Time, Radio Bearer Uplink Ciphering Activation Time Info, Mobile Observed Time Difference, Uplink Counter Synchronisation Info struct, START List, CN Domain Identity, START, RB with PDCP Information List, RB with PDCP Information} message to target BSS. + +9. When the new source RNC-ID + S-RNTI are successfully exchanged with the MS, the target RNC/BSS shall send the **Relocation Complete** message to the new SGSN. The purpose of the Relocation Complete procedure is to indicate by the target RNC/BSS the completion of the relocation of the source BSS to the CN. After the reception of the **Relocation Complete** message the new SGSN shall be prepared to receive data from the target RNC/BSS. Each uplink N-PDU received by the new SGSN is forwarded directly to the GGSN. +10. For inter-SGSN PS handover, the new SGSN sends a **Forward Relocation Complete** message to the old SGSN to indicate the success of the handover procedure. The old SGSN acknowledges this with a **Forward Relocation Complete Acknowledge** message. Upon the reception of the Forward Relocation Complete message the old SGSN starts a packet forwarding timer. The old SGSN stops forwarding of data to the new SGSN after the packet forwarding timer expires. +11. The new SGSN sends an **Update PDP Context Request** (new SGSN Address, TEID, QoS Negotiated) message to the GGSN concerned. If a Direct Tunnel is established the SGSN provides to the GGSN instead of the new SGSN Address and TEID, the RNC address for User Plane and TEID for Downlink data and shall include the DTI to instruct the GGSN to apply Direct Tunnel specific error handling procedure as defined in 3GPP TS 23.060 [19]. The GGSN updates the PDP context fields and returns an **Update PDP Context Response** (TEID) message. From now on the GGSN sends new incoming downlink IP packets to the new SGSN instead of to the old SGSN. +12. The old SGSN shall initiate PFC Management procedures towards the source cell in order to trigger the release of resources in the source cell. +13. The MS sends a **Routing Area Update Request** (Old RAI, Old P-TMSI signature, Update Type) message to the new SGSN informing it that the target cell belongs to a new routing area. The MS shall send this message immediately after message 7. The new SGSN knows that a handover has been performed for this MS and can therefore exclude the SGSN context procedures which normally are used within the RA Update procedure. +14. At this point the new SGSN may optionally invoke MS authentication (security function). The security function can be deferred and performed at any later time as well. + +NOTE 3: During an authentication procedure the SGSN has to suspend the downlink transmission of user data. + +15. The new SGSN informs the HLR of the change of SGSN by sending **Update Location** (SGSN Number, SGSN Address, IMSI) message to the HLR. +16. The HLR sends **Cancel Location** (IMSI, Cancellation Type) message to the old SGSN with Cancellation Type set to Update Procedure. +17. The old SGSN acknowledges with a **Cancel Location Acknowledge** (IMSI) message. This message allows the old SGSN to know when to release the inter-SGSN tunnel. +18. The HLR sends **Insert Subscriber Data** (IMSI, GPRS subscription data) message to the new SGSN. The new SGSN validates the MS presence in the (new) RA. + +19. If all checks are successful then the new SGSN constructs an MM context for the MS and returns an **Insert Subscriber Data Acknowledge** (IMSI) message to the HLR. This message allows the new SGSN to know when to release the inter-SGSN tunnel. +20. The HLR acknowledges the Update Location by sending an **Update Location Acknowledge** (IMSI) message to the new SGSN. +21. The new SGSN validates the MS presence in the new RA. If the MS is allowed to be attached in this RA, the SGSN updates the MM context for and sends a **Routing Area Update Accept** message to the MS. +22. The MS may respond to the SGSN with a **Routing Area Update Complete** message. + +The following CAMEL procedure calls shall be performed (see referenced procedures in TS 23.078 [8b]) + +- C1) CAMEL\_GPRS\_PDP\_Context\_Disconnection, CAMEL\_GPRS\_Detach and CAMEL\_PS\_Notification. + +They are called in the following order: + +- The CAMEL\_GPRS\_PDP\_Context\_Disconnection procedure is called several times: once per PDP context. The procedure returns as result "Continue". +- Then the CAMEL\_GPRS\_Detach procedure is called once. The procedure returns as result "Continue". +- Then the CAMEL\_PS\_Notification procedure is called once. The procedure returns as result "Continue". + +- C2) CAMEL\_GPRS\_Routeing\_Area\_Update\_Session and CAMEL\_PS\_Notification. + +They are called in the following order: + +- The CAMEL\_GPRS\_Routeing\_Area\_Update\_Session procedure is called. The procedure returns as result "Continue". +- Then, the CAMEL\_PS\_Notification procedure is called. The procedure returns as result "Continue". + +- C3) CAMEL\_GPRS\_Routeing\_Area\_Update\_Context. + +This procedure is called several times: once per PDP context. It returns as result "Continue". + +For C2 and C3: refer to Routing Area Update procedure description in 3GPP TS 23.060. + +## 5.3 Inter-RAT/mode Handover (UTRAN/GERAN Iu mode → GERAN A/Gb mode) + +### 5.3.1 Intra SGSN + +#### 5.3.1.1 Inter RAT/mode UTRAN/GERAN Iu mode to GERAN A/Gb mode PS HO; Preparation phase + +![Sequence diagram of the PS Handover Preparation Phase for Inter-RAT/mode UTRAN/GERAN Iu mode to GERAN A/Gb mode. The diagram shows five entities: MS, Source RNC/BSS, Target BSS, 3G/2G SGSN, and GGSN. The process starts with a '1. Handover decision' (dashed box) between MS and Source RNC/BSS. Then, '2. Relocation Required' is sent from Source RNC/BSS to 3G/2G SGSN. Next, '3. PS handover Request' is sent from 3G/2G SGSN to Target BSS. A dashed box '4. Reservation of radio resources in target BSS' is shown between Target BSS and 3G/2G SGSN. Another dashed box '5. Target BSS creates the Target BSS to Source BSS Transparent Container' is shown between Target BSS and Source RNC/BSS. Finally, '6. PS Handover Request Acknowledge' is sent from Target BSS to 3G/2G SGSN.](c1278da91cbcabe32628e589ebc47418_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Source RNC/BSS + participant Target BSS + participant 3G/2G SGSN + participant GGSN + + Note left of MS: 1. Handover decision + Source RNC/BSS->>3G/2G SGSN: 2. Relocation Required + 3G/2G SGSN->>Target BSS: 3. PS handover Request + Note right of Target BSS: 4. Reservation of radio resources in target BSS + Note right of Target BSS: 5. Target BSS creates the Target BSS to Source BSS Transparent Container + Target BSS->>3G/2G SGSN: 6. PS Handover Request Acknowledge + +``` + +Sequence diagram of the PS Handover Preparation Phase for Inter-RAT/mode UTRAN/GERAN Iu mode to GERAN A/Gb mode. The diagram shows five entities: MS, Source RNC/BSS, Target BSS, 3G/2G SGSN, and GGSN. The process starts with a '1. Handover decision' (dashed box) between MS and Source RNC/BSS. Then, '2. Relocation Required' is sent from Source RNC/BSS to 3G/2G SGSN. Next, '3. PS handover Request' is sent from 3G/2G SGSN to Target BSS. A dashed box '4. Reservation of radio resources in target BSS' is shown between Target BSS and 3G/2G SGSN. Another dashed box '5. Target BSS creates the Target BSS to Source BSS Transparent Container' is shown between Target BSS and Source RNC/BSS. Finally, '6. PS Handover Request Acknowledge' is sent from Target BSS to 3G/2G SGSN. + +**Figure 15: PS Handover Preparation Phase; Inter-RAT/mode, Intra-SGSN case (UTRAN/GERAN Iu mode → GERAN A/Gb mode)** + +1. Based on measurement results and knowledge of the RAN topology, the source RNC/BSS decides to initiate an inter RAT/mode PS handover towards the GERAN A/Gb mode. At this point both uplink and downlink user data flows via the tunnel(s): Radio Bearer between the MS and the source RNC/BSS; GTP-U tunnel(s) between the source RNC/BSS and the 3G/2G SGSN; GTP-U tunnel(s) between the 3G/2G SGSN and the GGSN. + +NOTE 1: The process leading to the handover decision is outside of the scope of this paper. + +2. The source RNC/BSS sends a **Relocation Required** (Relocation Type, Cause, Source ID, Target ID, Source BSS To Target BSS Transparent Container (RN part)) message to the 3G/2G SGSN. The source RNC/BSS shall set Relocation Type to "UE Involved in relocation of SRNS". + +Target ID contains the identity of the target cell. + +3. The 3G/2G SGSN determines from the Target Cell Identifier that the type of handover is inter-RAT/mode handover. The 3G/2G SGSN sends a **PS Handover Request** (Local TLLI, IMSI, Cause, Target Cell Identifier, Source BSS to Target BSS Transparent Container (RN part), PFCs To Be Set Up List, NAS container for PS HO) message to the target BSS. The 3G/2G SGSN shall only request resources for PFCs for which, based on source side information, resources should be allocated in the target cell during the PS Handover preparation phase. + +If the 3G/2G SGSN has negotiated XID parameters with the MS when the MS was in A/Gb mode before, or if the 3G/2G SGSN can accept all XID parameters as indicated by the old SGSN during a previous inter-SGSN PS handover, the 3G/2G SGSN shall create a NAS container for PS HO indicating 'Reset to the old XID parameters'. Otherwise the 3G/2G SGSN shall create a NAS container for PS HO indicating Reset (i.e. reset to default parameters). + +4. Based upon the ABQP for each PFC the target BSS makes a decision about which PFCs to assign radio resources. The algorithm by which the BSS decides which PFCs that need resources is implementation specific. Due to resource limitations not all downloaded PFCs will necessarily receive resource allocation. The target BSS allocates TBFs for each PFC that can be accommodated by the target BSS. + +After allocating radio resources the target BSS shall prepare the Target BSS to Source BSS Transparent Container for the set up BSS PFCs. + +5. The target BSS shall prepare the Target BSS to Source BSS Transparent Container which contains a PS Handover Command including the CN part (NAS container for PS HO) and the RN part (PS Handover Radio Resources). +6. The target BSS shall send the **PS Handover Request Acknowledge** message (Local TLLI, List of Set Up PFCs, Target BSS to Source BSS Transparent Container) message to the 3G/2G SGSN. Upon sending the **PS Handover Request Acknowledge** message the target BSS shall be prepared to receive downlink LLC PDUs from the 3G/2G SGSN for the accepted PFCs. + +Any PDP contexts for which a PFC was not established are maintained in the 3G/2G SGSN and the related SAPIs and PFIs are kept. These PDP contexts may be modified or deactivated by the 3G/2G SGSN via explicit SM procedures upon the completion of the routing area update (RAU) procedure. + +When the 3G/2G SGSN receives the **PS Handover Request Acknowledge** message and it decides to proceed with the handover, the preparation phase is finished and the execution phase will follow. + +#### 5.3.1.2 Inter RAT/mode UTRAN/GERAN *Iu mode* to GERAN *A/Gb mode* PS HO; Execution phase + +![Sequence diagram for PS Handover Execution Phase, Inter-RAT/mode, Intra-SGSN case (UTRAN/GERAN Iu mode to GERAN A/Gb mode).](7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Source RNC/BSS + participant Target BSS + participant 3G/2G SGSN + participant GGSN + participant HLR + + Note over GGSN, 3G/2G SGSN: 1a. IP Packets from GGSN + GGSN-->>3G/2G SGSN: + Note over 3G/2G SGSN, Source RNC/BSS: 1a IP Packets to source RNC/BSS + 3G/2G SGSN-->>Source RNC/BSS: + Note over 3G/2G SGSN, Source RNC/BSS: 1b. IP Packets to source RNC (Direct Tunnel) + GGSN-->>Source RNC/BSS: + 3G/2G SGSN->>Source RNC/BSS: 2. Relocation Command + Source RNC/BSS->>3G/2G SGSN: 3. Forward GTP PDUs + Source RNC/BSS->>3G/2G SGSN: 3. Forward Data + 3G/2G SGSN->>Target BSS: 3. Forward Data + Source RNC/BSS->>MS: 4. Handover from UTRAN Command or Handover from GERAN Iu Command + Source RNC/BSS->>3G/2G SGSN: 5. Forward SRNS Context + Note over MS, Target BSS: 6. GERAN A/Gb Access procedures + MS->>Target BSS: 7. XID Response + Target BSS->>3G/2G SGSN: 8. PS Handover Complete + Target BSS->>3G/2G SGSN: 7a. XID Response + 3G/2G SGSN->>GGSN: 9. Update PDP Context request + GGSN->>3G/2G SGSN: 9. Update PDP Context Response + Note over Target BSS, MS: IP Packets to target BSS + Target BSS-->>MS: + MS<->Target BSS: 10. XID negotiation for LLC ADM + MS<->Target BSS: 11. SABM-UA Exchange + Note over MS, Target BSS: (ABM establishment and XID negotiation) + 3G/2G SGSN->>Source RNC/BSS: 12. Iu release Command + Source RNC/BSS->>3G/2G SGSN: 12. Iu release Complete + + rect rgb(240, 240, 240) + Note right of Target BSS: RAU Procedure + Target BSS->>3G/2G SGSN: 13. RAU Request + 3G/2G SGSN->>Target BSS: 14. RAU Accept (C2) + Target BSS->>3G/2G SGSN: 15. RAU Complete (C3) + end + + 3G/2G SGSN->>Target BSS: 16. PS Handover Complete Acknowledge + +``` + +The sequence diagram illustrates the execution phase of a PS Handover from UTRAN/GERAN *Iu mode* to GERAN *A/Gb mode*. The participants involved are MS (Mobile Station), Source RNC/BSS, Target BSS, 3G/2G SGSN, GGSN, and HLR. The diagram shows the flow of IP packets, relocation commands, data forwarding, handover commands, access procedures, XID negotiation, PDP context updates, and the Routing Area Update (RAU) procedure. + +Sequence diagram for PS Handover Execution Phase, Inter-RAT/mode, Intra-SGSN case (UTRAN/GERAN Iu mode to GERAN A/Gb mode). + +**Figure 16: PS Handover Execution Phase; Inter-RAT/mode, Intra-SGSN case (UTRAN/GERAN *Iu mode* → GERAN *A/Gb mode*)** + +- The 3G/2G SGSN continues to receive IP packets from the GGSN (via GTP) and forwards the associated PDU payload to the MS via the source RNC/BSS. In case of Direct Tunnel, the GGSN sends IP packets directly to the source RNC. +- The 3G/2G SGSN continues the PS handover by sending a **Relocation Command** (Target BSS to Source BSS Transparent Container (PS Handover Command with RN part and CN part), RABs to be Released List, RABs Subject to Data Forwarding List) message to the source RNC/BSS. "RABs to be released list" will be the list of all NSAPIs (RAB Ids) for which a PFC was not established. "RABs Subject to Data forwarding list" will be the list of all NSAPIs (RAB Ids) for which a PFC was established. +- When receiving the **Relocation Command** message the source RNC may, based on QoS, begin the forwarding of data for the RABs subject to data forwarding to the 3G/2G SGSN according to the definition in 3GPP TS 23.060 [19]. The GTP-U sequence numbers are only sent by the source RNC for PDP context(s) requiring delivery order (QoS profile) to be preserved. If delivery order is to be preserved (QoS profile), consecutive GTP-PDU sequence numbering shall be maintained through the lifetime of the PDP context(s). + +The 3G/2G SGSN may, based on QoS, proceed with the packet handling as follows: + +- For PDP contexts which use LLC ADM the 3G/2G SGSN either: + +- a. forwards the received downlink N-PDUs to the target BSS; + - b. stores the received data into the SNDCP queue for e.g. the PDU lifetime; + - c. discards the received data until e.g. reception of the **PS Handover Complete** message. +- If the 3G/2G SGSN forwards packets to the target BSS, the target BSS may start a blind transmission of downlink user data towards the MS over the allocated radio channels. +4. The RNC/BSS sends the **Handover from UTRAN Command** message (UTRAN) or the **Handover from GERAN Iu Command** message to the MS where each message includes a PS Handover Command (RN part and CN part) message. Before sending the message the uplink and downlink data transfer shall be suspended in the source RNC for the RABs that require delivery order. + +Upon reception of the **Handover from UTRAN Command** message (UTRAN) or the **Handover from GERAN Iu Command** the MS shall suspend the uplink transmission of user plane data. + +5. The source RNC/BSS continues the handover by sending a **Forward SRNS Context** (RAB contexts) message to the 3G/2G SGSN. + +The source RNC/BSS behaviour is as specified in 3GPP TS 23.060 [19] (Combined Hard Handover and SRNS Relocation). + +6. The MS executes the handover according to the parameters provided in the message delivered in step 4. The procedure is the same as in step 6 in subclause 5.1.4.2. + +- 7./7a. After accessing the cell using access bursts and receiving timing advance information from the BSS in step 6, the MS processes the NAS container and then sends one **XID Response** message to the 3G/2G SGSN. The MS sends this message immediately after receiving the **Packet Physical Information** message containing the timing advance or, in the synchronised network case, immediately if the **PS Handover Access** message is not required to be sent (see Section 6.2). + +The MS shall resume the user data transfer only for those NSAPIs for which there are radio resources allocated in the target cell. For NSAPIs using LLC ADM for which radio resources were not allocated in the target cell the MS may request for radio resources using the legacy procedures. + +- NOTE: If the 3G/2G SGSN indicated Reset (i.e. reset to default parameters) in the NAS container for PS HO included in the **Handover from UTRAN Command** message (UTRAN) or the **Handover from GERAN Iu Command** message, in order to avoid collision cases the mobile station may avoid triggering XID negotiation for any LLC SAPI used in LLC ADM, but wait for the SGSN to do so (see bullet 9). In any case the mobile station may avoid triggering XID negotiation for any LLC SAPI used in LLC ABM, but wait for the SGSN to do so (see bullet 10). + +8. Upon reception of the first correct RLC/MAC block (sent in normal burst format) from the MS the target BSS sends a **PS Handover Complete** (Local TLLI, IMSI, Request for Inter RAT Handover Info) message to inform the 3G/2G SGSN that the MS has arrived in the target cell. Each uplink N-PDU received by the 3G/2G SGSN via the target BSS is then forwarded directly to the GGSN. The target BSS shall request the INTER RAT HANDOVER INFO from the SGSN by setting the “Request for INTER RAT HANDOVER INFO” to “1”. +9. If a Direct Tunnel was established for Iu mode, the SGSN sends an **Update PDP Context Request** (new SGSN Address, TEID, QoS Negotiated) message to the GGSN with the indication for not re-negotiating the QoS and to establish a tunnel between the SGSN and the GGSN. The GGSN updates the PDP context and returns an **Update PDP Context Response** (TEID) message. From now on the GGSN sends new incoming downlink IP packets to the SGSN. +10. If the 3G/2G SGSN indicated Reset (i.e. reset to default parameters) in the NAS container for PS HO included in the **Handover from UTRAN Command** message (UTRAN) or the **Handover from GERAN Iu Command** message, then on receipt of the **PS Handover Complete** message the SGSN initiates an LLC/SNDCP XID negotiation for each LLC SAPI used in LLC ADM. In this case if the SGSN wants to use the default parameters, it shall send an empty XID Command. If the SGSN indicated 'Reset to the old XID parameters' in the NAS container for PS HO, no further XID negotiation is required for LLC SAPIs used in LLC ADM only. + +11. The 3G/2G SGSN (re-)establishes LLC ABM for the PDP contexts which use acknowledged information transfer. During the exchange of SABM and UA the SGSN shall perform LLC/SNDPCP XID negotiation. +12. After the reception of the **PS Handover Complete** message the 3G/2G SGSN sends an **Iu Release Command** message to the source RNC/BSS commanding the source RNC/BSS to release all resources related to the Iu connection. When the RNC/BSS data forwarding timer has expired the source RNC/BSS responds with an **Iu Release Complete** (RAB Data Volume report list, RABs released list) message. +13. The MS sends a **Routing Area Update Request** (Old P-TMSI, Old RAI, Old P-TMSI signature, Update Type) message to the 3G/2G SGSN. This is done even if the target cell belongs to the same routing area as the source cell. The MS shall send this message immediately after message 7, see 3GPP TS 23.060 [19]. + +The 3G/2G SGSN knows that a handover has been performed for this MS and can therefore exclude the SGSN context procedures which normally are used within the RA Update procedure. + +14. The 3G/2G SGSN validates the MS presence in the new RA. If the MS is allowed to be attached in this RA, the 3G/2G SGSN updates the MM context for and sends a **Routing Area Update Accept** (P-TMSI, TMSI, P-TMSI signature, Receive N-PDU number) message to the MS. The Receive N-PDU Number contains the acknowledgements for each acknowledged-mode NSAPI used by the 3G/2G SGSN, thereby confirming all mobile originated N-PDUs successfully transferred before the start of the PS handover procedure. +15. The MS confirms the re-allocation of the new P-TMSI by responding to the 3G/2G SGSN with a **Routing Area Update Complete** (Receive N-PDU number). The MS derives the TLLI from the new P-TMSI using the current MM procedures. The Receive N-PDU Number contains the acknowledgements for each acknowledged mode NSAPI used by the MS, thereby confirming all mobile terminated N-PDUs successfully transferred before the start of the handover procedure. If Receive N-PDU Number confirms reception of N-PDUs that were forwarded from the 3G/2G SGSN, these N-PDUs shall be discarded by the 3G/2G SGSN. + +The following CAMEL procedure calls shall be performed (see referenced procedures in TS 23.078 [8b]): + +- C2) CAMEL\_GPRS\_Routeing\_Area\_Update\_Session and CAMEL\_PS\_Notification. + +They are called in the following order: + +- The CAMEL\_GPRS\_Routeing\_Area\_Update\_Session procedure is called. The procedure returns as result "Continue". +- Then, the CAMEL\_PS\_Notification procedure is called. The procedure returns as result "Continue". + +- C3) CAMEL\_GPRS\_Routeing\_Area\_Update\_Context. + +This procedure is called several times: once per PDP context. It returns as result "Continue". + +For C2 and C3: refer to Routing Area Update procedure description in 3GPP TS 23.060. + +16. Upon reception of the **PS Handover Complete** message with the "Request for Inter RAT Handover Info" set to "1" for UTRAN, the SGSN shall send **PS Handover Complete Acknowledge** (TLLI, Inter RAT Handover Info) message to the target BSS. +17. The target BSS receiving the **PS Handover Complete Acknowledge** message shall set the 'Reliable INTER RAT HANDOVER' to '1' in the **PS Handover Required** message in any subsequent PS handover to GERAN *A/Gb mode*. The target BSS failing to receive the **PS Handover Complete Acknowledge** message shall set the 'Reliable INTER RAT HANDOVER' to '0' in the **PS Handover Required** message in any subsequent PS handover to GERAN *A/Gb mode*. The Target BSS shall, upon receipt of the INTER RAT HANDOVER INFO in the **PS Handover Complete Acknowledge** message, discard the INTER RAT HANDOVER INFO received from the source RNC during the preparation phase. + +### 5.3.2 Inter SGSN + +#### 5.3.2.1 Inter RAT/mode UTRAN/GERAN lu mode to GERAN A/Gb mode PS HO; Preparation phase + +![Sequence diagram of PS Handover Preparation Phase for Inter-RAT/mode, Inter-SGSN case (UTRAN/GERAN lu mode to GERAN A/Gb mode).](036c200da9b64c3eb5aae2d67bb53e1f_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Source RNC/BSS + participant Target BSS + participant Old SGSN + participant New SGSN + participant GGSN + + Note left of MS: 1. Handover decision + Source RNC/BSS->>Old SGSN: 2. Relocation Required + Old SGSN->>New SGSN: 3. Forward Relocation Request + New SGSN->>Target BSS: 4. PS handover Request + Note right of Target BSS: 5. Reservation of radio resources in target BSS + Note right of Target BSS: 6. Target BSS creates the Target BSS to Source BSS Transparent Container + Target BSS->>New SGSN: 7. PS handover Request Acknowledge + New SGSN->>Old SGSN: 8. Forward Relocation Response + +``` + +Sequence diagram of PS Handover Preparation Phase for Inter-RAT/mode, Inter-SGSN case (UTRAN/GERAN lu mode to GERAN A/Gb mode). + +**Figure 17: PS Handover Preparation Phase; Inter-RAT/mode, Inter-SGSN case (UTRAN/GERAN lu mode → GERAN A/Gb mode)** + +1. Based on measurement results and knowledge of the RAN topology, the source RNC/BSS decides to initiate an inter RAT/mode PS handover towards the GERAN A/Gb mode. At this point both uplink and downlink user data flows via the tunnel(s): Radio Bearer between the MS and the source RNC/BSS; GTP-U tunnel(s) between the source RNC/BSS and the old SGSN; GTP-U tunnel(s) between the old SGSN and the GGSN. + +NOTE 1: The process leading to the handover decision is outside of the scope of this paper. + +2. The source RNC/BSS sends a **Relocation Required** (Relocation Type, Cause, Source ID, Target ID, Source BSS To Target BSS Transparent Container (RN part)) message to the old SGSN. The source RNC/BSS shall set Relocation Type to "UE Involved in relocation of SRNS". + +Target ID contains the identity of the target cell. + +3. The old SGSN determines from the Target Cell Identifier that the type of handover is inter-RAT/mode handover. In case of Inter-RAT/ mode Inter-SGSN PS handover, the old SGSN initiates the PS Handover resource allocation procedure by sending a **Forward Relocation Request** (IMSI, Tunnel Endpoint Identifier Control Plane, RANAP Cause, Target Cell Identifier, MM Context, PDP Contexts, Packet Flow ID, SNDPCP XID parameters, LLC XID parameters, PDP Context Prioritisation, Source BSS To Target BSS Transparent Container [RN part] in the BSS Container, Source RNC Id, SGSN Address for control plane) message to the new SGSN. If the old SGSN supports PS handover procedures then it has to allocate a valid PFI according to subclause 4.4.1 during the PDP Context activation procedure. Each PDP context contains the GGSN Address for User Plane and the Uplink TEID for Data (to this GGSN Address and Uplink TEID for Data the old SGSN and the new SGSN send uplink packets). + +The MM context contains security related information, e.g. supported ciphering algorithms as described in 3GPP TS 29.060 [11]. The relation between GSM and UMTS security parameters is defined in 3GPP TS 33.102 [27], + +The new SGSN selects the ciphering algorithm to use. This algorithm will be sent transparently from the new SGSN to the MS. The IOV-UI parameter generated in the new SGSN and used, as input to the ciphering procedure will also be transferred transparently from the new SGSN to the MS. + +When the new SGSN receives the **Forward Relocation Request** message the required PDP, MM, SNDPCP and LLC contexts are established and a new P-TMSI is allocated for the MS. When this message is received by the new SGSN it begins the process of establishing PFCs for all PDP contexts. + +When the new SGSN receives the **Forward Relocation Request** message it extracts from the PDP Contexts the NSAPIs and SAPIs and PFIs to be used in the new SGSN. If for a given PDP Context the new SGSN does not receive a PFI from the old SGSN, it shall not request the target BSS to allocate TBF resources corresponding to that PDP Context. If none of the PDP Contexts forwarded from the old SGSN has a valid PFI allocated the new SGSN shall consider this as a failure case and the request for PS handover shall be rejected. + +In case when an SAPI and PFI was available at the old SGSN but the new SGSN does not support the same SAPI and PFI for a certain NSAPI as the old SGSN, the new SGSN shall continue the PS handover procedure only for those NSAPIs for which it can support the same PFI and SAPI as the old SGSN. All PDP contexts for which no resources are allocated by the new SGSN or for which it cannot support the same SAPI and PFI (i.e. the corresponding NSAPIs are not addressed in the response message of the target SGSN), are maintained and the related SAPIs and PFIs are kept. These PDP contexts may be modified or deactivated by the new SGSN via explicit SM procedures upon RAU procedure. + +The old SGSN shall indicate the current XID parameter settings if available (i.e. those negotiated at the old SGSN when the MS was in A/Gb mode or received during a previous inter-SGSN PS handover) to the new SGSN. If the new SGSN can accept all XID parameters as indicated by the old SGSN, the new SGSN shall create a NAS container for PS HO indicating 'Reset to the old XID parameters'. Otherwise, if the new SGSN cannot accept all XID parameters indicated by the old SGSN or if no XID parameters were indicated by the old SGSN, the new SGSN shall create a NAS container for PS HO indicating Reset (i.e. reset to default parameters). + +4. The new SGSN sends a **PS Handover Request** (Local TLLI, IMSI, Cause, Target Cell Identifier, Source BSS to Target BSS Transparent Container (RN part), PFCs To Be Set Up List, NAS container for PS HO) message to the target BSS. The new SGSN shall not request resources for PFCs associated with PDP contexts with maximum bit rate for uplink and downlink of 0 kbit/s or for which the Activity Status Indicator within the PDP Context indicates that no active RAB exists on the source side. +5. Based upon the ABQP for each PFC the target BSS makes a decision about which PFCs to assign radio resources. The algorithm by which the BSS decides which PFCs that need resources is implementation specific. Due to resource limitations not all downloaded PFCs will necessarily receive resource allocation. The target BSS allocates TBFs for each PFC that it can accommodate. +6. The target BSS shall prepare the Target BSS to Source BSS Transparent Container which contains a PS Handover Command including the CN part (NAS container for PS HO) and the RN part (PS Handover Radio Resources). +7. Target BSS shall send the **PS Handover Request Acknowledge** message (Local TLLI, List of Set Up PFCs, Target BSS to Source BSS Transparent Container) message to the new SGSN. Upon sending the **PS Handover Request Acknowledge** message the target BSS shall be prepared to receive downlink LLC PDUs from the new SGSN for the accepted PFCs. + +Any PDP contexts for which a PFC was not established are maintained in the new SGSN and the related SAPIs and PFIs are kept. These PDP contexts may be modified or deactivated by the new SGSN via explicit SM procedures upon the completion of the routing area update (RAU) procedure. + +8. The new SGSN passes the assigned list of TEIDs for each PDP context for which a PFC was assigned in the RAB setup information IE in the **Forward Relocation Response** (Cause, List of Set Up PFCs, Target BSS to Source BSS Transparent Container) in the BSS Container, Tunnel Endpoint Identifier Control Plane, SGSN Address for User Traffic, Tunnel Endpoint Identifier Data II) message to the old SGSN. The NSAPIs of the active PDP Contexts received in the Forward Relocation Request message for which the PS handover continues, i.e. for which resources are allocated for the PFCs in the target BSS, are indicated in this message. + +The Tunnel Endpoint Identifier Data II, one information for each PDP context, is the tunnel endpoint of the new SGSN and is used for data forwarding from the old SGSN, via the new SGSN, to the target BSS. + +The new SGSN activates the allocated LLC/SNDPCP engines as specified in 3GPP TS 44.064 [21] for an SGSN originated Reset or 'Reset to the old XID parameters'. + +When the old SGSN receives the **Forward Relocation Response** message and it decides to proceed with the handover, the preparation phase is finished and the execution phase will follow. + +#### 5.3.2.2 Inter RAT UTRAN/GERAN Iu mode to GERAN A/Gb mode PS HO; Execution phase + +![Sequence diagram for PS Handover Execution Phase: Inter-RAT/mode, Inter-SGSN case (UTRAN/GERAN Iu mode -> GERAN A/Gb mode).](bccc028d0e75bc30c41528056f581545_img.jpg) + +The sequence diagram illustrates the execution phase of a PS Handover between UTRAN/GERAN Iu mode and GERAN A/Gb mode. The participants are MS, Source RNC/BSS, Target BSS, Old SGSN, New SGSN, GGSN, and HLR. + +Key steps in the sequence: + +- IP Packets are forwarded from GGSN to Old SGSN. +- Old SGSN sends a Relocation Command to Source RNC/BSS. +- Old SGSN forwards GTP PDUs and data to New SGSN. +- Source RNC/BSS sends a Handover command to MS. +- Old SGSN forwards SRNS Context to New SGSN. +- GERAN A/Gb Access procedures occur between Target BSS and New SGSN. +- Target BSS sends XID Response to Source RNC/BSS. +- Source RNC/BSS sends PS Handover Complete to Old SGSN. +- Old SGSN sends Forward Relocation Complete to New SGSN. +- New SGSN sends Update PDP Context Request to GGSN. +- GGSN sends IP Packets to New SGSN. +- New SGSN sends Update PDP Context Response to Old SGSN. +- Old SGSN sends Iu release Command to Source RNC/BSS. +- Source RNC/BSS sends Iu release Complete to Old SGSN. +- Forwarded data is sent from Old SGSN to MS via Source RNC/BSS. +- MS and New SGSN perform XID negotiation for LLC ADM. +- MS and New SGSN perform SABM/UA exchange. +- MS sends RAU Request to New SGSN. +- New SGSN performs Security functions. +- New SGSN sends Update Location to HLR. +- Old SGSN sends Cancel Location to HLR. +- HLR sends Insert Subscriber Data to New SGSN. +- New SGSN sends Update Location Ack to HLR. +- New SGSN sends RAU Accept to MS. +- MS sends RAU Complete to New SGSN. +- New SGSN sends PS Handover Complete Acknowledge to Old SGSN. + +Sequence diagram for PS Handover Execution Phase: Inter-RAT/mode, Inter-SGSN case (UTRAN/GERAN Iu mode -> GERAN A/Gb mode). + +**Figure 18: PS Handover Execution Phase; Inter-RAT/mode, Inter-SGSN case (UTRAN/GERAN Iu mode → GERAN A/Gb mode)** + +- The old SGSN continues to receive IP packets from the GGSN (via GTP) and forwards the associated PDU payload to the MS via the source RNC/BSS. +- The old SGSN continues the PS handover by sending a **Relocation Command** (Target BSS to Source BSS Transparent Container (PS Handover Command with RN part and CN part), RABs to be Released List, RABs Subject to Data Forwarding List) message to the source RNC/BSS. "RABs to be released list" will be the list of all NSAPIs (RAB Ids) for which a PFC was not established "RABs Subject to Data forwarding list" will be the list of all NSAPIs (RAB Ids) for which a PFC was established. + +3. When receiving the **Relocation Command** message the source RNC/BSS may, based on QoS, begin the forwarding of data for the RABs subject to data forwarding to the new SGSN via the old SGSN (if a Tunnel Endpoint is available) according to the definition in 3GPP TS 23.060 [19]. The GTP-U sequence numbers are only sent by the source RNC for PDP context(s) requiring delivery order (QoS profile) to be preserved. If delivery order is to be preserved (QoS) profile, consecutive GTP-PDU sequence numbering shall be maintained through the lifetime of the PDP context(s). + +The new SGSN may, based on QoS, proceed with the packet handling as follows: + +- For PDP contexts which use LLC ADM the new SGSN either: + - a. forwards the received downlink N-PDUs to the target BSS; + - b. stores the received data into the SNDPCP queue for e.g. the PDU lifetime; + - c. discards the received data until e.g. reception of the **PS Handover Complete** message. + +If the new SGSN forwards packets to the target BSS, the target BSS may start a blind transmission of downlink user data towards the MS over the allocated radio channels. + +NOTE 1: The order of steps, starting from step 3 onwards, does not necessarily reflect the order of events. For instance the source RNC may start data forwarding (step 3), send the RRC message (step 4) and send the **Forward SRNS Context** message (step 5) almost simultaneously. + +4. The source RNC/BSS sends the **Handover from UTRAN Command** message (UTRAN) or the **Handover from GERAN Iu Command** message to the MS where each message includes a PS Handover Command (RN part and CN part). Before sending the message the uplink and downlink data transfer shall be suspended in the source RNC for the RABs that require delivery order. + +Upon the reception of the **HANDOVER from UTRAN Command** message (UTRAN) or the **HANDOVER from GERAN Iu Command** message containing the PS Handover Command message, the MS shall associate its RAB IDs to the respective PFIs based on the relation with the NSAPI and shall suspend the uplink transmission of the user plane data. + +5. The source RNC continues the handover by sending a **Forward SRNS Context** (RAB contexts) message to the new SGSN, via the old SGSN. The **Forward SRNS Context** message is acknowledged by the new SGSN with the **Forward SRNS Context Acknowledge** message to the old SGSN. + +The source RNC/BSS behaviour is as specified in 3GPP TS 23.060 [19] (Combined Hard Handover and SRNS Relocation). + +6. The MS executes the handover according to the parameters provided in the message delivered in step 4. The procedure is the same as in step 6 in subclause 5.1.4.2 with the additional function of association of the received PFI and existing RAB Id related to the particular NSAPI as described in clause 4.4.1. + +- 7./7a. After accessing the cell using access bursts and receiving timing advance information from the BSS in step 6, the MS processes the NAS container and then sends one **XID Response** message to the new SGSN. The MS sends this message immediately after receiving the **Packet Physical Information** message containing the timing advance or, in the synchronised network case, immediately if the **PS Handover Access** message is not required to be sent (see Section 6.2). + +Upon sending the **XID Response message**, the MS shall resume the user data transfer only for those NSAPIs for which there are radio resources allocated in the target cell. For NSAPIs using LLC ADM for which radio resources were not allocated in the target cell the MS may request for radio resources using the legacy procedures. + +NOTE 2: If the new SGSN indicated Reset (i.e. reset to default parameters) in the NAS container for PS HO included in the the **Handover from UTRAN Command** message (UTRAN) or the **Handover from GERAN Iu Command** message, in order to avoid collision cases the mobile station may avoid triggering XID negotiation for any LLC SAPI used in LLC ADM, but wait for the SGSN to do so (see bullet 12). In any case the mobile station may avoid triggering XID negotiation for any LLC SAPI used in LLC ABM, but wait for the SGSN to do so (see bullet 12a). + +8. Upon reception of the first correct RLC/MAC block (sent in normal burst format) from the MS the target BSS sends a **PS Handover Complete** (Local TLLI, Handover Complete Status, Request for Inter RAT Handover + +Info) message to inform the new SGSN that the MS has arrived in the target cell. Each uplink N-PDU received by the new SGSN via the target BSS is then forwarded directly to the GGSN. The target BSS shall request the INTER RAT HANDOVER INFO from the SGSN by setting the 'Request for Inter RAT Handover Info' to '1'. + +9. Upon receiving the **PS Handover Complete** message, the new SGSN send a **Forward Relocation Complete** message to the old SGSN to indicate completion of the PS handover procedures. The old SGSN responds with a **Forward Relocation Complete Acknowledge** message. +10. The new SGSN sends an **Update PDP Context Request** (new SGSN Address, TEID, QoS Negotiated) message to the GGSN concerned. The GGSN updates the PDP context fields and returns an **Update PDP Context Response** (TEID) message. From now on the GGSN sends new incoming downlink IP packets to the new SGSN instead of to the old SGSN. +11. The old SGSN sends an **Iu Release Command** message to the source RNC/BSS commanding the source RNC/BSS to release all resources related to the Iu connection. When the RNC/BSS data forwarding timer has expired the source RNC/BSS responds with an **Iu Release Complete** (RAB Data Volume report list, RABs released list) message. +12. If the new SGSN indicated Reset (i.e. reset to default parameters) in the NAS container for PS HO included in the **Handover from UTRAN Command** message (UTRAN) or the **Handover from GERAN Iu Command** message, then on receipt of the PS Handover Complete the new SGSN initiates an LLC/SNDCP XID negotiation for each LLC SAPI used in LLC ADM. In this case if the SGSN wants to use the default parameters, it shall send an empty XID Command. If the new SGSN indicated 'Reset to the old XID parameters' in the NAS container for PS HO, no further XID negotiation is required for LLC SAPIs used in LLC ADM only. +- 12a. The new SGSN (re-)establishes LLC ABM for the PDP contexts which use acknowledged information transfer. During the exchange of SABM and UA the SGSN shall perform LLC/SNDCP XID negotiation. +13. The MS sends a **Routing Area Update Request** (Old P-TMSI, Old RAI, Old P-TMSI signature, Update Type) message to the new SGSN informing it that the source cell belongs to a new routing area. The MS shall send this message immediately after message 7, see 3GPP TS 23.060 [19]. + +The new SGSN knows that a handover has been performed for this MS and can therefore exclude the SGSN context procedures which normally are used within the RA Update procedure. + +14. At this point the new SGSN may optionally invoke MS authentication (security function). The security function can be deferred and performed at any later time as well. + +NOTE 3: During an authentication procedure the SGSN has to suspend the downlink transmission of user data. + +15. The new SGSN informs the HLR of the change of SGSN by sending **Update Location** (SGSN Number, SGSN Address, IMSI) message to the HLR. +16. The HLR sends a **Cancel Location** (IMSI, Cancellation Type) message to the old SGSN with Cancellation Type set to Update Procedure. The old SGSN acknowledges with a **Cancel Location Acknowledge** (IMSI) message. This message allows the old SGSN to know when to release the inter-SGSN tunnel. +17. The HLR sends **Insert Subscriber Data** (IMSI, GPRS subscription data) message to the new SGSN. The new SGSN validates the MS presence in the (new) RA. If all checks are successful then the new SGSN constructs an MM context for the MS and returns an **Insert Subscriber Data Acknowledge** (IMSI) message to the HLR. This message allows the new SGSN to know when to release the inter-SGSN tunnel. +18. The HLR acknowledges the Update Location by sending an **Update Location Acknowledge** (IMSI) message to the new SGSN. +19. The new SGSN validates the MS presence in the new RA. If the MS is allowed to be attached in this RA, the SGSN updates the MM context for and sends a **Routing Area Update Accept** (P-TMSI, TMSI, P-TMSI signature, Receive N-PDU number) message to the MS. The Receive N-PDU Number contains the acknowledgements for each acknowledged-mode NSAPI used by the SGSN, thereby confirming all mobile originated N-PDUs successfully transferred before the start of the PS handover procedure. +20. The MS confirms the re-allocation of the new P-TMSI by responding to the SGSN with a **Routing Area Update Complete** (Receive N-PDU number) message. The MS derives the Local TLLI from the new P-TMSI using the current MM procedures. The Receive N-PDU Number contains the acknowledgements for each + +acknowledged mode NSAPI used by the MS, thereby confirming all mobile terminated N-PDUs successfully transferred before the start of the handover procedure. If Receive N-PDU Number confirms reception of N-PDUs that were forwarded from the old SGSN, these N-PDUs shall be discarded by the new SGSN. + +The following CAMEL procedure calls shall be performed (see referenced procedures in TS 23.078 [8b]) + +C1) CAMEL\_GPRS\_PDP\_Context\_Disconnection, CAMEL\_GPRS\_Detach and CAMEL\_PS\_Notification. + +They are called in the following order: + +- The CAMEL\_GPRS\_PDP\_Context\_Disconnection procedure is called several times: once per PDP context. The procedure returns as result "Continue". +- Then the CAMEL\_GPRS\_Detach procedure is called once. The procedure returns as result "Continue" +- Then the CAMEL\_PS\_Notification procedure is called once. The procedure returns as result "Continue". + +C2) CAMEL\_GPRS\_Routeing\_Area\_Update\_Session and CAMEL\_PS\_Notification. + +They are called in the following order: + +- The CAMEL\_GPRS\_Routeing\_Area\_Update\_Session procedure is called. The procedure returns as result "Continue". +- Then, the CAMEL\_PS\_Notification procedure is called. The procedure returns as result "Continue". + +C3) CAMEL\_GPRS\_Routeing\_Area\_Update\_Context. + +This procedure is called several times: once per PDP context. It returns as result "Continue". + +For C2 and C3: refer to Routing Area Update procedure description in 3GPP TS 23.060. + +21. Upon reception of the **PS Handover Complete** message with the “Request for Inter RAT Handover Info” set to “1” for UTRAN, the SGSN shall send **PS Handover Complete Acknowledge** (TLLI, Inter RAT Handover Info) message to the target BSS. +22. The target BSS receiving the **PS Handover Complete Acknowledge** message shall set the ‘Reliable INTER RAT HANDOVER’ to ‘1’ in the **PS Handover Required** message in any subsequent PS handover to GERAN *A/Gb mode*. The target BSS failing to receive the **PS Handover Complete Acknowledge** message shall set the ‘Reliable INTER RAT HANDOVER’ to ‘0’ in the **PS Handover Required** message in any subsequent PS handover to GERAN *A/Gb mode*. The Target BSS shall, upon receipt of the INTER RAT HANDOVER INFO in the **PS Handover Complete Acknowledge** message, discard the INTER RAT HANDOVER INFO received from the source RNC during the preparation phase. + +## 5.3a Inter-RAT Handover (GERAN *A/Gb mode* to E-UTRAN) + +### 5.3a.1 General + +This procedure and the corresponding signalling flows are defined in 3GPP TS23.401 [33]. + +For performing the inter-RAT handover from GERAN *A/Gb mode* to E-UTRAN the pre-conditions are: + +- The MS is in packet transfer mode (GERAN *A/Gb mode*); +- The MS has at least one PDP Context established; +- The BSS supports PFM (Packet Flow Management) procedures. + +### 5.3a.2 Preparation phase + +The detailed signalling flows are specified in 3GPP TS 23.401 [33] in sub-clause 5.5.2.4.2. + +### 5.3a.3 Execution phase + +The detailed signalling flows are specified in 3GPP TS 23.401 [33] in sub-clause 5.5.2.4.3. + +## 5.3b Inter-RAT Handover (E-UTRAN to GERAN *A/Gb mode*) + +### 5.3b.1 General + +This procedure and the corresponding signalling flows are defined in 3GPP TS23.401 [33]. + +For performing the inter-RAT handover from E-UTRAN to GERAN *A/Gb mode* the pre-conditions are: + +- The UE is in ECM-CONNECTED state (E-UTRAN Active mode); +- The BSS supports PFM (Packet Flow Management) procedures. + +### 5.3b.2 Preparation phase + +The detailed signalling flows are specified in 3GPP TS 23.401 [33] in sub-clause 5.5.2.3.2. + +### 5.3b.3 Execution phase + +The detailed signalling flows are specified in 3GPP TS 23.401 [33] in sub-clause 5.5.2.3.2. + +## 5.4 Handover reject + +### 5.4.1 General + +The target BSS/GANC may reject the use of the PS Handover procedure in case none of the PFCs To Be Set Up in the **PS Handover Request** message could be granted the requested QoS, or, in case of a non-critical PS handover, if at least one of the PFCs To Be Set Up in the **PS Handover Request** message could not be granted the requested QoS. In this case no MS context will be established in the target BSS/GANC and no resources will be allocated. The target BSS/GANC will send a **PS Handover Request Negative Acknowledge** message to the new SGSN causing the new SGSN to release any allocated resources (e.g. P-TMSI, MS associated contexts) related to the specific MS. The signalling procedure for the Inter-SGSN HO Reject is shown in clause 5.4.2 for the case where PS handover is attempted to a target BSS/GANC. Similar procedures are used in the other handover cases. + +### 5.4.2 Inter-SGSN HO Reject; Signalling procedure + +![Sequence diagram for PS Handover Reject; Inter-SGSN case (GERAN A/Gb mode → GERAN A/Gb mode).](720d082148a35c2d5537a04ed5268d8b_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Source BSS + participant Target BSS/GANC + participant Old SGSN + participant New SGSN + participant GGSN + + Note right of Source BSS: 1. Decision to perform A/Gb PS Handover + Source BSS->>Old SGSN: 1. PS handover Required + Old SGSN->>New SGSN: 1. Forward Relocation Request + New SGSN->>Target BSS/GANC: 1. PS Handover Request + Target BSS/GANC->>New SGSN: 2. PS Handover Request Negative Acknowledge + New SGSN->>Old SGSN: 3. Forward Relocation Response (Reject) + Old SGSN->>Source BSS: 4. PS Handover Required Negative Acknowledge + +``` + +Sequence diagram for PS Handover Reject; Inter-SGSN case (GERAN A/Gb mode → GERAN A/Gb mode). + +**Figure 19: PS Handover Reject; Inter-SGSN case (GERAN *A/Gb mode* → GERAN *A/Gb mode*)** + +1. The first four steps in the flow are identical to the ones in clause 5.1.4.1. +2. In case the target BSS/GANC fails to allocate any resources for any of the requested PFCs it sends a **PS Handover Request Negative Acknowledge** (Cause, Source Cell Identifier, Target Cell Identifier) message to the new SGSN. + +3. When the new SGSN receives the **PS Handover Request Negative Acknowledge** message it clears any reserved resources (e.g. PDP context, P-TMSI) for this mobile and sends the **Forward Relocation Response** (Cause, SGSN Address for control plane) message to the old SGSN. +4. When the old SGSN receives the **Forward Relocation Response** message it sends a **PS Handover Required Negative Acknowledge** (Old TLLI, Cause, Source Cell Identifier, Target Cell Identifier) message to the source BSS. + +## 5.5 Handover cancel + +### 5.5.1 General + +Instead of performing the handover, the source BSS may at any time during the handover procedure, up to the time when the **PS Handover Command** message is sent to the mobile station cancel the handover. The reason for cancelling can be e.g. due to a timer expiration or due to other events within the source BSS and is initiated by sending a **PS Handover Cancel** PDU to the SGSN. + +A **PS Handover Cancel** PDU shall also be sent by the source BSS after the **PS Handover Command** message is sent to the mobile station for the case where the PS Handover fails and the MS returns to the old cell or radio contact with the MS is lost. This is done in order to release the resources reserved for the PS Handover in the target system. + +The radio contact with the MS is considered lost by the source BSS if, after transmission of the **PS Handover Command** message, for an implementation dependent period of time: + +- the BSS does not receive a **Packet Cell Change Failure** message (see sub-clause 5.7.2) or any other RLC/MAC block (other than a Packet Control Acknowledgement message which acknowledges the receipt of the PS Handover Command) from the MS in the source cell, and either + - the BSS does not receive any RLC/MAC block from the MS in the target cell, if the PS handover is an optimised intra-BSS handover, or + - the BSS does not receive a DELETE-BSS-PFC PDU (including the TLLI of the MS) from the SGSN, if the PS handover is an inter-BSS handover, inter-RAT/mode or non-optimised intra-BSS handover. + +The signalling procedures for the case when the handover is cancelled before the **PS Handover Command** message has been sent by the source BSS to the mobile station is shown in clause 5.5.2 below, as well as the case when the handover is cancelled in UTRAN/GERAN Iu mode by the source RNC/BSS. The signalling procedures for the cases that occur after the **PS Handover Command** message has been sent are shown in clause 5.7.2.1. + +### 5.5.2 Signalling procedures + +#### 5.5.2.1 Inter-SGSN case, GERAN A/Gb mode → GERAN A/Gb mode + +![Sequence diagram for PS Handover Cancel in an Inter-SGSN case, GERAN A/Gb mode. The diagram shows the interaction between MS, Source BSS, Target BSS, Old SGSN, New SGSN, and GGSN. A dashed box labeled '1' indicates the period from PS Handover Required to PS Handover Command. The sequence of messages is: 2. PS Handover Cancel (Source BSS to Old SGSN), 3. Relocation Cancel Request (Old SGSN to New SGSN), 4. Delete BSS PFC Procedure (New SGSN to Target BSS), and 5. Relocation Cancel Response (New SGSN to Old SGSN).](818a57b74294582a480f23f82d95815f_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Source BSS + participant Target BSS + participant Old SGSN + participant New SGSN + participant GGSN + + Note left of Source BSS: 1. Any phase from PS Handover Required has been sent but before PS Handover Command has been sent to the mobile. + Source BSS->>Old SGSN: 2. PS Handover Cancel + Old SGSN->>New SGSN: 3. Relocation Cancel Request + New SGSN->>Target BSS: 4. Delete BSS PFC Procedure + New SGSN->>Old SGSN: 5. Relocation Cancel Response + +``` + +Sequence diagram for PS Handover Cancel in an Inter-SGSN case, GERAN A/Gb mode. The diagram shows the interaction between MS, Source BSS, Target BSS, Old SGSN, New SGSN, and GGSN. A dashed box labeled '1' indicates the period from PS Handover Required to PS Handover Command. The sequence of messages is: 2. PS Handover Cancel (Source BSS to Old SGSN), 3. Relocation Cancel Request (Old SGSN to New SGSN), 4. Delete BSS PFC Procedure (New SGSN to Target BSS), and 5. Relocation Cancel Response (New SGSN to Old SGSN). + +Figure 20: PS Handover Cancel; Inter-SGSN case, GERAN A/Gb mode → GERAN A/Gb mode + +1. The source BSS decides to cancel the previously requested PS Handover. This may be due to initiation of a CS call during the preparation phase, not enough accepted PFCs, or any other reason. +2. The source BSS sends a **PS Handover Cancel** (TLLI, Cause, Source Cell Identifier, Target Cell Identifier) PDU to the old SGSN. +3. The old SGSN terminates the PS Handover to the target cell by sending a **Relocation Cancel Request** (IMSI) message to the new SGSN. The old SGSN also resumes operation on the resources in the source cell. + +NOTE 1: If one new SGSN was chosen among a pool, then the **Relocation Cancel Request** message is sent to this SGSN. + +4. The new SGSN triggers the release of resources in the target cell and also releases its own resources allocated for this handover. +5. The new SGSN acknowledges the release of all resources on the target side by returning a **Relocation Cancel Response** message to the old SGSN. + +NOTE 2: In the intra-SGSN case, the messages **Relocation Cancel Request** and **Relocation Cancel Response** are not exchanged since the old and new SGSN are then the same node. + +#### 5.5.2.2 Inter-SGSN case, GERAN A/Gb mode → UTRAN/GERAN Iu mode + +![Sequence diagram for PS Handover Cancel in the Inter-SGSN case. The diagram shows the interaction between MS, Source BSS, Target RNC, Old 2G SGSN, New 3G SGSN, and GGSN. A dashed box labeled '1' indicates the period from 'PS Handover Required' to 'PS Handover Command'. The sequence of messages is: 2. PS Handover Cancel (Source BSS to Old 2G SGSN), 3. Relocation Cancel Request (Old 2G SGSN to New 3G SGSN), 4. Iu Release Command (New 3G SGSN to Target RNC), 5. Iu Release Complete (Target RNC to New 3G SGSN), and 6. Relocation Cancel Response (New 3G SGSN to Old 2G SGSN).](91b12db3c85bbf466ad27eb3665a1b06_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Source BSS + participant Target RNC + participant Old 2G SGSN + participant New 3G SGSN + participant GGSN + + Note left of Source BSS: 1. Any phase from PS Handover Required has been sent but before PS Handover Command has been sent to the mobile. + Source BSS->>Old 2G SGSN: 2. PS Handover Cancel + Old 2G SGSN->>New 3G SGSN: 3. Relocation Cancel Request + New 3G SGSN->>Target RNC: 4. Iu Release Command + Target RNC->>New 3G SGSN: 5. Iu Release Complete + New 3G SGSN->>Old 2G SGSN: 6. Relocation Cancel Response + +``` + +Sequence diagram for PS Handover Cancel in the Inter-SGSN case. The diagram shows the interaction between MS, Source BSS, Target RNC, Old 2G SGSN, New 3G SGSN, and GGSN. A dashed box labeled '1' indicates the period from 'PS Handover Required' to 'PS Handover Command'. The sequence of messages is: 2. PS Handover Cancel (Source BSS to Old 2G SGSN), 3. Relocation Cancel Request (Old 2G SGSN to New 3G SGSN), 4. Iu Release Command (New 3G SGSN to Target RNC), 5. Iu Release Complete (Target RNC to New 3G SGSN), and 6. Relocation Cancel Response (New 3G SGSN to Old 2G SGSN). + +**Figure 20a: PS Handover Cancel; Inter-SGSN case, GERAN A/Gb mode → UTRAN/GERAN Iu mode** + +1. The source BSS decides to cancel the previously requested PS handover. This may be due to initiation of a CS call during the preparation phase, not enough accepted PFCs, or any other reason. +2. The source BSS sends a **PS Handover Cancel** (TLLI, Cause, Source Cell Identifier, Target Cell Identifier) PDU to the old SGSN. +3. The old SGSN terminates the PS Handover to the target cell by sending a **Relocation Cancel Request** (IMSI) message to the new SGSN. The old SGSN also resumes operation on the resources in the source cell. + +NOTE 1: If one new SGSN was chosen among a pool, then the **Relocation Cancel Request** message is sent to this SGSN. + +4. The new SGSN triggers the release of resources in the target cell by sending an **Iu Release Command** message to the target RNC +5. The target RNC releases all resources allocated for this handover and returns an **Iu Release Complete** message to the new SGSN. +6. The new SGSN releases its own resources allocated for this handover and acknowledges the release of all resources on the target side by returning a **Relocation Cancel Response** message to the old SGSN. + +NOTE 2: In the intra-SGSN case, the messages **Relocation Cancel Request** and **Relocation Cancel Response** are not exchanged since the old and new SGSN are then the same node. + +#### 5.5.2.3 Inter-SGSN case, UTRAN/GERAN Iu mode → GERAN A/Gb mode + +![Sequence diagram for Relocation Cancel in Inter-SGSN case, UTRAN/GERAN Iu mode → GERAN A/Gb mode. The diagram shows the interaction between MS, Source RNC, Target BSS, Old 3G SGSN, New 2G SGSN, and GGSN. The process starts with the Source RNC/BSS deciding to cancel the relocation (step 1). It then sends a Relocation Cancel message to the Old 3G SGSN (step 2). The Old 3G SGSN sends a Relocation Cancel Request to the New 2G SGSN (step 3). The New 2G SGSN triggers the release of resources in the target cell and releases its own resources (step 4). The New 2G SGSN returns a Relocation Cancel Response to the Old 3G SGSN (step 5). Finally, the Old 3G SGSN returns a Relocation Cancel Acknowledge to the Source RNC/BSS (step 6).](848073118eebfdbfdb9a60e3923fe0b3_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Source RNC + participant Target BSS + participant Old 3G SGSN + participant New 2G SGSN + participant GGSN + + Note left of Source RNC: 1. The source RNC/BSS decides to cancel the relocation.. + Source RNC->>Old 3G SGSN: 2. Relocation Cancel + Old 3G SGSN->>New 2G SGSN: 3. Relocation Cancel Request + New 2G SGSN->>Target BSS: 4. Delete BSS PFC Procedure + New 2G SGSN->>Old 3G SGSN: 5. Relocation Cancel Response + Old 3G SGSN->>Source RNC: 6. Relocation Cancel Acknowledge + +``` + +Sequence diagram for Relocation Cancel in Inter-SGSN case, UTRAN/GERAN Iu mode → GERAN A/Gb mode. The diagram shows the interaction between MS, Source RNC, Target BSS, Old 3G SGSN, New 2G SGSN, and GGSN. The process starts with the Source RNC/BSS deciding to cancel the relocation (step 1). It then sends a Relocation Cancel message to the Old 3G SGSN (step 2). The Old 3G SGSN sends a Relocation Cancel Request to the New 2G SGSN (step 3). The New 2G SGSN triggers the release of resources in the target cell and releases its own resources (step 4). The New 2G SGSN returns a Relocation Cancel Response to the Old 3G SGSN (step 5). Finally, the Old 3G SGSN returns a Relocation Cancel Acknowledge to the Source RNC/BSS (step 6). + +**Figure 20b: Relocation Cancel; Inter-SGSN case, UTRAN/GERAN Iu mode → GERAN A/Gb mode** + +1. The source RNC/BSS decides to cancel the previously requested relocation of PS resources. This may be due to initiation of a CS call during the preparation phase, not enough accepted RABs, UE returned to source cell or any other reason. +2. The source RNC/BSS sends a **Relocation Cancel** (Cause) message to the old SGSN. +3. The old SGSN terminates the relocation to the target cell by sending a **Relocation Cancel Request** (IMSI) message to the new SGSN. The old SGSN also resumes operation on the resources in the source cell. + +NOTE 1: If one new SGSN was chosen among a pool, then the **Relocation Cancel Request** message is sent to this SGSN. + +4. The new SGSN triggers the release of resources in the target cell and also releases its own resources allocated for this handover. +5. The new SGSN acknowledges the release of all resources on the target side by returning a **Relocation Cancel Response** (Cause) message to the old SGSN. +6. The old SGSN returns a Relocation Cancel message to the source RNC/BSS. + +NOTE 2: In the intra-SGSN case, the messages **Relocation Cancel Request** and **Relocation Cancel Response** are not exchanged since the old and new SGSN are then the same node. + +#### 5.5.2.4 Inter-SGSN, GERAN A/Gb mode → E-UTRAN + +The detailed signalling flows are specified in 3GPP TS 23.401 [33] in sub-clause 5.5.2.X.2. + +#### 5.5.2.5 Inter-SGSN case, E - UTRAN → GERAN A/Gb mode + +The detailed signalling flows are specified in 3GPP TS 23.401 [33] in sub-clause 5.5.2.X.2. + +## 5.6 Container handling + +There are two transparent containers defined for the PS handover in GERAN A/Gb mode and GAN mode: + +- Source BSS to Target BSS Transparent Container. +- Target BSS to Source BSS Transparent Container. + +The Source BSS to Target BSS Transparent Container will carry the information to be transported transparently between the source BSS and the target BSS/GANC and between the source GANC and the target BSS related to PS handover. + +The Target BSS to Source BSS Transparent Container will carry the information to be transported transparently between the target BSS and the source BSS/GANC and between the target GANC and the source BSS related to PS handover. + +The generic handling of the source cell (GERAN A/Gb mode or UTRAN/GERAN Iu mode or E-UTRAN) to target cell (GERAN A/Gb mode or UTRAN/GERAN Iu mode or E-UTRAN) radio-related container is as follows: + +- Created by the source BSS or RNC or eNB . +- Processed by the target BSS or RNC or eNB. +- Forwarded transparently by the SGSNs and MME . + +The generic handling of the target cell (GERAN A/Gb mode or UTRAN/GERAN Iu mode or E-UTRAN ) to source cell (GERAN A/Gb mode or UTRAN/GERAN Iu mode or E-UTRAN) radio-related container is as follows: + +- Created by the target BSS or RNC or eNB. +- Processed by the source BSS or RNC or eNB . +- Forwarded transparently by the SGSNs and MME . + +The generic handling of the source cell to target cell radio-related container for PS handover from GERAN A/Gb mode to GAN mode or vice versa is as follows: + +- Created by the source BSS or GANC. +- Processed by the target BSS for PS handover from a source GANC. +- Processed by the target GANC for PS handover from a source BSS. +- Forwarded transparently by the SGSNs. + +The generic handling of the source cell to target cell radio-related container for PS handover from UTRAN to GAN mode or vice versa is as follows: + +- Created by the source GANC or RNC. +- Processed by the target GANC for PS handover from a source RNC. +- Processed by the target RNC for PS handover from a source GANC. +- Forwarded transparently by the SGSNs. + +The generic handling of the target cell to source cell radio-related container for PS handover from GERAN A/Gb mode to GAN mode or vice versa is as follows: + +- Created by the target GANC or BSS. +- Processed by the source BSS for PS handover to a target GANC. +- Processed by the source GANC for PS handover to a target BSS. +- Forwarded transparently by the SGSNs. + +The generic handling of the target cell to source cell radio-related container for PS handover from UTRAN to GAN mode or vice versa is as follows: + +- Created by the target GANC or RNC. +- Processed by the source RNC for PS handover to a target GANC. + +- Processed by the source GANC for PS handover to a target RNC. +- Forwarded transparently by the SGSNs. + +### 5.6.1 Contents of the containers + +The transparent container will consist of two parts: + +- The **Radio Network part** (RN part) carrying radio interface related parameters relevant for the MS and the radio network (BSS/RNC/eNB) and sent transparently through the core network; This content is: + - Created by the source BSS/RNC/GANC/eNB and carried in the Source BSS to Target BSS / Source to Target transparent container (i.e. the forward container). + - Created by the target BSS/RNC/GANC/eNB and carried in the Target BSS to Source BSS / Target to Source transparent container (i.e. the reverse container). + - Processed by the target BSS/RNC/GANC/eNB (forward container only) + - Processed by the source BSS/RNC/GANC/eNB and MS (reverse container only). +- The **Core Network part** (CN part) carrying parameters relevant for the MS and the core network. This part is only needed from the new SGSN to send to the MS for PS handover to A/Gb mode and GAN mode and thus is only included in the Target BSS to Source BSS Transparent Container. This content is: + - Created by the new SGSN. + - Included in the Target BSS to Source BSS Transparent Container by the target BSS/GANC. + +NOTE 1: The target BSS/GANC does not process the Core Network part. + +- Forwarded transparently by the old SGSN and source BSS/RNC/GANC/eNB. +- Carried within the **PS Handover Command** message sent from the source BSS to the MS for PS handover from A/Gb mode to A/Gb mode or for PS handover from A/Gb mode to GAN mode. +- Carried within the **PS Handover Command** message included within a **GA-PSR Handover Command** message sent from the source GANC to the MS for PS handover from GAN mode to A/Gb mode. +- Carried within the **PS Handover Command** message included within a **Handover from UTRAN Command** message or the **Handover from GERAN Iu Command** message sent from the source RNC to the MS for PS handover from Iu mode to A/Gb mode. +- Carried within the **PS Handover Command** message included within a **Handover from UTRAN Command** message sent from the source RNC to the MS for PS handover from UTRAN to GAN mode. +- Carried within the **PS Handover Command** message included within a **MobilityFromEUTRACommand** message sent from the source eNB to the MS for PS handover from E-UTRAN to GERAN *A/Gb mode*. +- Processed by the MS. + +The contents of the Radio Network part will depend on: + +- Type of channels that are subject to PS handover, i.e. shared or dedicated. + +NOTE 2: Currently dedicated channels are not considered in the PS handover in GERAN A/Gb mode. + +- PS handover scenario, i.e. intra-mode or inter-RAT/mode. +- Whether it is sent in a forward container or a reverse container. + +The contents of the Core Network part will depend on the PS handover scenario, i.e. intra-mode or inter-RAT/mode. + +#### 5.6.1.1 Contents of the GERAN A/Gb mode or GAN mode → GERAN A/Gb mode Transparent Containers + +##### 5.6.1.1.1 Source BSS to Target BSS Transparent Container + +In GERAN A/Gb mode/GAN mode -> GERAN A/Gb mode the Source BSS to Target BSS Transparent Container is sent in the **PS Handover Required** message, the **Forward Relocation Request** message and the **PS Handover Request** message. + +The Radio Network part consists of the following: + +- MS RAC. +- INTER RAT HANDOVER INFO (defined in 3GPP TS 25.331) containing the START\_PS and UE RAC values, if available. +- E-UTRAN INTER RAT HANDOVER INFO (defined in 3GPP TS 48.018, see also 3GPP TS 36.331) if available + +NOTE 1: The START\_PS and UE RAC are needed to support PS Handover to UTRAN/GERAN Iu mode. + +NOTE 2: The way of transferring START\_PS and UE RAC from the mobile station to the BSS/GANC, is to piggyback the RRC container INTER RAT HANDOVER INFO, which includes START\_PS and UE RAC, to the Attach Complete and Routing Area Update Complete messages from the mobile station to the SGSN. The SGSN will then include this container in every CREATE-BSS-PFC message sent to the BSS/GANC and/or in the **PS Handover Complete Acknowledge** message. + +##### 5.6.1.1.2 Target BSS to Source BSS Transparent Container + +In GERAN A/Gb mode/GAN mode -> GERAN A/Gb mode the Target BSS to Source BSS Transparent Container is sent in the **PS Handover Request Acknowledge** message, **Forward Relocation Response** message and the **PS Handover Required Acknowledge** message. + +The Radio Network part consists of the required information for access in the target cell and the information on allocated radio resources, uplink and downlink TBF parameters, Handover reference and generic parameters for access in the target cell (i.e. GPRS cell options, target cell "Cell Selection struct", global power control parameters, reference frequency lists, cell allocation, GPRS mobile allocation). + +The Core Network part (i.e. NAS Container for PS HO) consists of the following parameters: + +- an XID Command indicating Reset or 'Reset to old XID parameters' and the new IOV-UI for the target cell; +- the GPRS ciphering algorithm to be used in the target cell, if it is different from the ciphering algorithm used in the source cell. + +#### 5.6.1.2 Contents of the GERAN A/Gb mode or GAN mode → UTRAN Transparent Containers + +##### 5.6.1.2.1 Source to Target Transparent Container + +In GERAN A/Gb mode/GAN mode -> UTRAN the Source to Target Transparent Container is encoded as the Source RNC to Target RNC Transparent Container. It is sent from the source BSS/GANC to the target RNC in the **PS Handover Required** message and the **Relocation Request** message. + +The Radio Network part consists of the following: + +- RRC Container as defined in 3GPP TS 25.331 [17] will contain Inter RAT Handover Info (UTRAN specific information including START\_PS/UE RAC) and Inter RAT UE radio access capability including MS RAC from BSS to RNC. +- Target Cell Id. +- Number of Iu instances IE. The value of this IE is set to 1 as defined in 3GPP TS 25.413 [23]. +- Relocation Type. The value of the IE is set to “UE involved”, as defined in 3GPP TS 25.413 [23]. + +##### 5.6.1.2.2 Target to Source Transparent Container + +In GERAN A/Gb mode/GAN mode -> UTRAN the Target to Source Transparent Container is encoded as the Target RNC to Source RNC Transparent Container. It is sent from the target RNC to the source BSS/GANC in the **Relocation Request Acknowledge** message, **Forward Relocation Response** message and the **PS Handover Required Acknowledge** message. + +The Radio Network part consists of the RRC message, i.e. the **Handover to UTRAN Command** message (as defined in 3GPP TS 25.331 [17]) used to perform handover from GERAN A/Gb mode/GAN mode to UTRAN. This message will be sent to the MS/UE within the **PS Handover Command** message (for PS handover from GERAN A/Gb mode) or within the **GA-PSR Handover Command** message (for PS handover from GAN mode). + +#### 5.6.1.3 Contents of the UTRAN → GERAN A/Gb Mode or GAN mode Transparent Containers + +##### 5.6.1.3.1 Source BSS to Target BSS Transparent Container + +In UTRAN -> GERAN A/Gb mode/GAN mode the Source BSS to Target BSS Transparent Container is sent from the source RNC to the target BSS/GANC in the **Relocation Required**, **Forward Relocation Request** message and the **PS Handover Request** message in order to support inter-RAT PS handover from UTRAN (CELL\_DCH state or CELL\_FACH state, only PS RABs established) to GERAN A/Gb mode/GAN mode. + +The Radio Network part consists of the following information: + +- MS RAC. +- INTER RAT HANDOVER INFO (defined in 3GPP TS 25.331) containing the START\_PS and UE RAC values. +- E-UTRAN INTER RAT HANDOVER INFO (defined in 3GPP TS 48.018, see also 3GPP TS 36.331) if available + +NOTE: The START\_PS value received in the INTER RAT HANDOVER INFO is not always aligned with the START\_PS value stored in the MS after it has attached to the GSM network. The target BSS shall replace the value received in the container received from the source RNC with the value received from the MS via the SGSN (i.e. within a **CREATE-BSS-PFC** message or a **PS Handover Complete Acknowledge** message). + +##### 5.6.1.3.2 Target BSS to Source BSS Transparent Container + +In UTRAN -> GERAN A/Gb mode/GAN mode the Target BSS to Source BSS Transparent Container is sent from the target BSS/GANC to the source RNC in the **PS Handover Request Acknowledge** message, **Forward Relocation Response** message and the **Relocation Command** message in order to support inter-RAT PS handover from UTRAN (CELL\_DCH state or CELL\_FACH state, only PS RABs established) to GERAN A/Gb mode/GAN mode. + +For PS handover from UTRAN to GERAN A/Gb mode the Radio Network part consists of the required information for access in the target cell and the information on allocated radio resources: uplink and downlink TBF parameters, PS Handover reference and generic parameters for access in the target cell (i.e. GPRS cell options, target cell "Cell Selection struct", global power control parameters, reference frequency lists, cell allocation, GPRS mobile allocation). Over the air interface this radio network container is sent within the **Handover from UTRAN Command** message. + +For PS handover from UTRAN to GAN mode the Radio Network part consists only of the mandatory fields within the PS Handover Radio Resources IE carried within the **PS Handover Command** message. + +The Core Network part (i.e. NAS Container for PS HO) consist of the following parameters: + +- an XID Command indicating Reset or 'Reset to old XID parameters' and the new IOV-UI for the target cell; +- the GPRS ciphering algorithm to be used in the target cell; + +#### 5.6.1.4 Contents of the GERAN A/Gb mode → GERAN Iu mode Transparent Containers + +##### 5.6.1.4.1 Source to Target Transparent Container + +In GERAN A/Gb mode -> GERAN Iu mode the Source to Target Transparent Container is encoded as the Source RNC to Target RNC Transparent Container. It is sent from the source BSS to the target BSS (Iu) in the **PS Handover Required** message, **Forward Relocation Request** message and the **Relocation Request** message. + +The Radio Network part consists of: + +- RRC Container as defined in 3GPP TS 44.118 [16] shall contain START\_PS /MS GERAN IU capabilities. +- Target Cell Id. +- Number of Iu instances. The value of the IE is set to 1 as defined in 3GPP TS 25.413 [23]. +- Relocation Type. The value of the IE is set to “UE involved”, as defined in 3GPP TS 25.413 [23]. + +##### 5.6.1.4.2 Target to Source Transparent Container + +In GERAN A/Gb mode -> GERAN Iu mode the Target to Source Transparent Container is encoded as the Target RNC to Source RNC Transparent Container. It is sent from the target BSS (Iu) to source BSS in the **Relocation Request Acknowledge** message, **Forward Relocation Response** message and the **PS Handover Required Acknowledge** message. + +The Radio Network Part consist of the RRC message used in GERAN Iu mode to perform handover, i.e. **Radio Bearer Reconfiguration** message as defined in 3GPP TS 44.118 [16]. This message will be sent to the MS in the **PS Handover Command** message. + +#### 5.6.1.5 Content of GERAN Iu mode → GERAN A/Gb mode Transparent Containers + +##### 5.6.1.5.1 Source BSS to Target BSS Transparent Container + +In GERAN Iu mode -> GERAN A/Gb mode the Source BSS to Target BSS Transparent Container is sent from the source BSS (Iu) to the target BSS in the **Relocation Required** message, **Forward Relocation Request** message and the **PS Handover Request** message. + +The Radio Network part consists of the following: + +- MS RAC. +- INTER RAT OR MODE HANDOVER INFO with MS capabilities as defined in 3GPP TS 44.118 [16]. + +NOTE: START\_PS and UE RAC shall be added to this IE. + +##### 5.6.1.5.2 Target BSS to Source BSS Transparent Container + +In GERAN Iu mode -> GERAN A/Gb mode the Target BSS to Source BSS Transparent Container is sent from the target BSS to the source BSS (Iu) in the **PS Handover Request Acknowledge** message, **Forward Relocation Response** message and the **Relocation Command** message in order to support PS handover to GERAN A/Gb mode from GERAN Iu mode (RRC Cell\_Dedicated state or RRC CELL\_Shared state, only PS RABs established). + +The Radio Network part consists of the required information for access in the target cell and the information on allocated radio resources: Uplink and downlink TBF parameters, PS Handover reference and generic parameters for access in the target cell (i.e. GPRS cell options, target cell "Cell Selection struct", global power control parameters, reference frequency lists, cell allocation, GPRS mobile allocation). Over the air interface this information is sent in the **Handover from GERAN Iu mode Command** message. + +The Core Network (i.e. NAS Container for PS HO) part consists of the following parameters: + +- an XID Command indicating Reset or 'Reset to old XID parameters' and the new IOV-UI for the target cell; +- the GPRS ciphering algorithm to be used in the target cell + +#### 5.6.1.6 Contents of the GERAN A/Gb mode → GAN mode Transparent Containers + +##### 5.6.1.6.1 Source BSS to Target BSS Transparent Container + +In GERAN A/Gb mode -> GAN mode the Source BSS to Target BSS Transparent Container is sent in the **PS Handover Required** message, the **Forward Relocation Request** message and the **PS Handover Request** message. + +The Radio Network part consists of the following: + +- MS RAC. +- START\_PS and UE RAC (for dual mode mobile stations). + +NOTE 1: The START\_PS and UE RAC are needed to support PS Handover to UTRAN/GERAN Iu mode. + +NOTE 2: The way of transferring START\_PS and UE RAC from the mobile station to the BSC, is to piggyback the RRC container INTER RAT HANDOVER INFO, which includes START\_PS and UE RAC, to the Attach Complete and Routing Area Update Complete messages from the mobile station to the SGSN. The SGSN will then include this container in every CREATE-BSS-PFC message sent to the BSC. + +##### 5.6.1.6.2 Target BSS to Source BSS Transparent Container + +In GERAN A/Gb mode -> GAN mode the Target BSS to Source BSS Transparent Container is sent in the **PS Handover Request Acknowledge** message, **Forward Relocation Response** message and the **PS Handover Required Acknowledge** message. + +The Radio Network part consists only of the mandatory fields within the PS Handover Radio Resources IE carried within the **PS Handover Command** message. + +The Core Network part (i.e. NAS Container for PS HO) consists of the following parameters: + +- an XID Command indicating Reset or 'Reset to old XID parameters' and the new IOV-UI for the target cell; +- the GPRS ciphering algorithm to be used in the target cell, if it is different from the ciphering algorithm used in the source cell. + +#### 5.6.1.7 Contents of the GERAN A/Gb mode → E-UTRAN Transparent Containers + +##### 5.6.1.7.1 Source to Target Transparent Container + +In GERAN *A/Gb mode* to E-UTRAN handover the Source to Target Transparent Container is encoded as the Source eNB to Target eNB Transparent Container. It is sent from the Source BSS to the target eNB in the **PS Handover Required** message, the **Forward Relocation Request** message and the **Handover Request** message. + +The Radio Network part consists of: + +- MS RAC +- INTER RAT HANDOVER INFO (defined in 3GPP TS 25.331) containing the START\_PS and UE RAC values, if available +- Target Cell Id. + +##### 5.6.1.7.2 Target to Source Transparent Container + +In GERAN *A/Gb mode* to E-UTRAN handover the Target to Source Transparent Container is encoded as the Target eNB to Source eNB Transparent Container. It is sent from the target eNB to source BSS in the **Handover Request Acknowledge** message, the **Forward Relocation Response** message and the **PS Handover Required Acknowledge** message. + +The Radio Network Part consists of the RRC message used in E-UTRAN to perform handover, i.e. (**RRR E-UTRA**) **HandoverCommand** message contains the entire **DL-DCCH-Message** including the **RRConnectionReconfiguration** message as defined in 3GPP TS 36.331 [31]. This message will be sent to the MS in the **PS Handover Command** message. + +#### 5.6.1.8 Contents of the E-UTRAN → GERAN *A/Gb mode* Transparent Containers + +##### 5.6.1.8.1 Source BSS to Target BSS Transparent Container + +In E-UTRAN to GERAN *A/Gb mode* handover the Source BSS to Target BSS Transparent Container is sent from the Source eNB to the Target BSS in the **Handover Required** message, the **Forward Relocation Request** message and the **PS Handover Request** message + +The Radio Network part consists of the following information: + +- MS RAC IE. +- INTER RAT HANDOVER INFO (defined in 3GPP TS 25.331) containing the START\_PS and UE RAC values, if available. +- E-UTRAN INTER RAT HANDOVER INFO (defined in 3GPP TS 48.018, see also 3GPP TS 36.331). + +##### 5.6.1.8.2 Target BSS to Source BSS Transparent Container + +In E-UTRAN to GERAN *A/Gb mode* handover the Target BSS to Source BSS Transparent Container is sent from the Target BSS to the Source eNB in the **PS Handover Request Acknowledge** message, the **Forward Relocation Response** message and the **Handover Command** message. + +For PS handover from E-UTRAN to GERAN *A/Gb mode* the Radio Network part consist of the required information for access in the target cell and the information on allocated radio resources: uplink and downlink TBF parameters, PS Handover reference and generic parameters for access in the target cell (i.e. GPRS cell options, target cell "Cell Selection struct", global power control parameters, reference frequency lists, cell allocation, GPRS mobile allocation). Over the air interface this radio network container is sent within the **MobilityFromEUTRACommand** message. + +The Core Network part (i.e. NAS Container for PS HO) consists of the following parameters: + +- an XID Command indicating Reset or 'Reset to old XID parameters' and the new IOV-UI for the target cell; +- the GPRS ciphering algorithm to be used in the target cell. + +## 5.7 PS Handover Failure + +During the PS handover procedure several types of failures can be identified. The PS handover failures may be typical network and signalling failure occurrences such as failures related to the loss of signalling messages, incorrect information element in the signalling messages or failures due to network nodes failures or specific to abnormal cases occurring during PS handover procedures. + +In general the PS handover failures can be divided into: + +- Preparation Phase Failure Scenarios on the Um, Gb, Gn and Up interface. +- Execution Phase Failure Scenarios on the Um, Gb and Gn interface. + +NOTE: RAU procedure failures will be handled as specified in 3GPP TS 24.008 [15]. + +A list of appropriate cause values should be chosen/defined to indicate to the source cell and target cell nodes the cause of the **PS Handover Request Negative Acknowledge** and the **PS handover Cancel** messages. + +### 5.7.1 Preparations Phase Failure Scenarios + +#### 5.7.1.1 PS Handover preparation phase failure scenarios on the Um interface + +- No Resource Reservation / Allocation: + - No radio resources available in the target cell. + +#### 5.7.1.2 PS Handover preparation phase failure scenarios on the Gb interface + +- No Resource Reservation / Allocation on the target system: + +- No radio resources available in the target cell (see clause 5.4). Appropriate cause values are needed in the **PS Handover Request Negative Acknowledge** message. +- Insufficient resource allocation by the target system: + - In case of insufficient resource allocation by the target side the source BSS may cancel the PS handover procedure (see clause 5.5). +- Feature "PS Handover" not supported: + - A new cause value is needed for the Gb interface if the target BSS/GANC does not support the PS Handover procedure. +- Target CSG cell is not allowed for this MS: + - A new cause value is needed for the Gb interface to inform the source BSS that the target CSG cell is invalid whenever access control performed according to the CSG Subscription List is unsuccessful. +- Generic Causes: + - Generic causes for the Gb interface failures are defined in 3GPP TS 48.018 [10]. The same cause values are applicable to the PS handover procedure on the Gb interface. + +#### 5.7.1.3 PS Handover preparation phase failure scenarios on the Gn interface + +- Context Transfer Failure: + - Context transfer failure may occur due to various causes defined in 3GPP TS 29.060 [11]. These cause values will be utilized during PS handover procedure. These values are to be utilized during PS handover procedure to indicate to the old SGSN the cause of the PS handover reject. Consequently an appropriate cause value should be chosen to allow the old SGSN to indicate to the source BSS the cause of failure. +- No Resource Reservation/ No Resource Allocation: + - Resource Reservation/Allocation failure occurs when no radio resources are available in the target cell. Consequently an appropriate cause value should be chosen to allow the old SGSN to indicate to the source BSS the cause of failure. +- Procedure "PS Handover" not supported: + - This occurs when the new SGSN does not support the PS Handover feature. +- Generic Causes: + - In 3GPP TS 29.060 [11] a set of cause values are defined. The same cause values are applicable to the PS handover procedure on the Gn interface. + +#### 5.7.1.4 PS Handover preparation phase failure scenarios on the Up interface + +- Failure to allocate a GA-PSR Transport Channel + - This occurs when the GANC sends the MS a GA-PSR ACTIVATE UTC REQ message (GANC → MS) but fails to receive a GA-PSR ACTIVATE UTC ACK back from the MS. +- Generic Causes: + - Handled as defined in 3GPP TS 44.060 [7] for the case where no radio resources are available in the target cell. + +### 5.7.2 Execution Phase Failure Scenarios + +#### 5.7.2.1 Execution phase failures on the Um interface + +##### 5.7.2.1.1 Initial Access Failure in the Target Cell during PS handover + +In case of initial access failure in the target cell, including the case where the MS fails to acquire time alignment information (for the unsynchronised network case), the MS is allowed to revert to the old cell. As is defined currently in 3GPP TS 44.060 [7], the MS shall return to the old cell and send a **Packet Cell Change Failure** message with the appropriate cause. + +If the MS was in packet transfer mode (or MAC-shared state) before the attempted handover it will, when going back to the old cell, send a **Packet Cell Change Failure** message and resume TBFs which were ongoing in the old cell. The source BSS will inform the old SGSN about this failure and consequently the old SGSN will inform the new SGSN about this failure, upon which the new SGSN will release the allocated resources and clear out any information and buffers related to this MS. + +The signalling flows for this procedure are depicted in figure 21 and 21a. + +![Sequence diagram showing the signalling flow for MS returning to old cell during PS handover failure. The diagram involves six entities: MS, Source BSS, Target BSS, Old SGSN, New SGSN, and GGSN. The sequence starts with an initial target cell access failure (dashed box). Step 1: MS sends 'Packet Cell Change Failure' to Source BSS. Step 2: Source BSS sends 'PS Handover Cancel' to Old SGSN. Step 3: Old SGSN sends 'Relocation Cancel Request' to New SGSN. Step 4: New SGSN sends 'Delete BSS PFC Procedure' to Target BSS. Step 5: New SGSN sends 'Relocation Cancel Response' to Old SGSN.](314da473d582c4327e1e3d56fcba19dd_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Source BSS + participant Target BSS + participant Old SGSN + participant New SGSN + participant GGSN + + Note left of MS: 1. Initial target cell access failure. MS returns to old cell. + MS->>Source BSS: 1. Packet Cell Change Failure + Source BSS->>Old SGSN: 2. PS Handover Cancel + Old SGSN->>New SGSN: 3. Relocation Cancel Request + New SGSN->>Target BSS: 4. Delete BSS PFC Procedure + New SGSN->>Old SGSN: 5. Relocation Cancel Response + +``` + +Sequence diagram showing the signalling flow for MS returning to old cell during PS handover failure. The diagram involves six entities: MS, Source BSS, Target BSS, Old SGSN, New SGSN, and GGSN. The sequence starts with an initial target cell access failure (dashed box). Step 1: MS sends 'Packet Cell Change Failure' to Source BSS. Step 2: Source BSS sends 'PS Handover Cancel' to Old SGSN. Step 3: Old SGSN sends 'Relocation Cancel Request' to New SGSN. Step 4: New SGSN sends 'Delete BSS PFC Procedure' to Target BSS. Step 5: New SGSN sends 'Relocation Cancel Response' to Old SGSN. + +**Figure 21: MS returns to old cell; Inter-SGSN case, GERAN A/Gb mode→ GERAN A/Gb mode** + +1. The MS returns to the old cell and sends a **Packet Cell Change Failure** message to the source BSS. +2. The source BSS sends a **PS Handover Cancel** (TLLI, Cause = MS Back on old Channel, Source Cell Identifier, Target Cell Identifier) PDU to the old SGSN. +3. The old SGSN terminates the PS Handover to the target cell by sending a **Relocation Cancel Request** (IMSI) message to the new SGSN. The old SGSN also resumes operation on the resources in the source cell, and resumes forwarding of uplink N-PDUs to the GGSN for those PDP contexts for which forwarding was previously stopped. + +NOTE 1: If one new SGSN was chosen among a pool, then the **Relocation Cancel Request** message is sent to this SGSN. + +4. The new SGSN triggers the release of resources in the target cell and also releases its own resources allocated for this handover. +5. The new SGSN acknowledges the release of all resources on the target side by returning a **Relocation Cancel Response** message to the old SGSN. + +NOTE 2: In the intra-SGSN case, the messages **Relocation Cancel Request** and **Relocation Cancel Response** are not exchanged since the old and new SGSN are then the same node. + +![Sequence diagram for Figure 21a: MS returns to old cell; Inter-SGSN case, GERAN A/Gb mode -> UTRAN/GERAN Iu mode. The diagram shows the interaction between MS, Source BSS, Target RNC, Old 2G SGSN, New 3G SGSN, and GGSN. The sequence starts with an initial target cell access failure (1.1) where the MS returns to the old cell. This is followed by a Packet Cell Change Failure (1) from the MS to the Source BSS. The Source BSS then sends a PS Handover Cancel (2) to the Old 2G SGSN. The Old 2G SGSN sends a Relocation Cancel Request (3) to the New 3G SGSN. The New 3G SGSN sends an Iu Release Command (4) to the Target RNC. The Target RNC sends an Iu Release Complete (5) to the New 3G SGSN. Finally, the New 3G SGSN sends a Relocation Cancel Response (6) to the Old 2G SGSN.](0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Source BSS + participant Target RNC + participant Old 2G SGSN + participant New 3G SGSN + participant GGSN + + Note left of MS: 1.1. Initial target cell access failure. MS returns to old cell. + MS->>Source BSS: 1. Packet Cell Change Failure + Source BSS->>Old 2G SGSN: 2. PS Handover Cancel + Old 2G SGSN->>New 3G SGSN: 3. Relocation Cancel Request + New 3G SGSN->>Target RNC: 4. Iu Release Command + Target RNC->>New 3G SGSN: 5. Iu Release Complete + New 3G SGSN->>Old 2G SGSN: 6. Relocation Cancel Response + +``` + +Sequence diagram for Figure 21a: MS returns to old cell; Inter-SGSN case, GERAN A/Gb mode -> UTRAN/GERAN Iu mode. The diagram shows the interaction between MS, Source BSS, Target RNC, Old 2G SGSN, New 3G SGSN, and GGSN. The sequence starts with an initial target cell access failure (1.1) where the MS returns to the old cell. This is followed by a Packet Cell Change Failure (1) from the MS to the Source BSS. The Source BSS then sends a PS Handover Cancel (2) to the Old 2G SGSN. The Old 2G SGSN sends a Relocation Cancel Request (3) to the New 3G SGSN. The New 3G SGSN sends an Iu Release Command (4) to the Target RNC. The Target RNC sends an Iu Release Complete (5) to the New 3G SGSN. Finally, the New 3G SGSN sends a Relocation Cancel Response (6) to the Old 2G SGSN. + +**Figure 21a: MS returns to old cell; Inter-SGSN case, GERAN A/Gb mode→ UTRAN/GERAN Iu mode** + +1. The MS returns to the old cell and sends a **Packet Cell Change Failure** message to the source BSS. +2. The source BSS sends a **PS Handover Cancel** (TLLI, Cause = MS Back on old Channel, Source Cell Identifier, Target Cell Identifier) PDU to the old SGSN. +3. The old SGSN terminates the PS Handover to the target cell by sending a **Relocation Cancel Request** (IMSI) message to the new SGSN. The old SGSN also resumes operation on the resources in the source cell, and resumes forwarding of uplink N-PDUs to the GGSN for those PDP contexts for which forwarding was previously stopped. + +NOTE 3: If one new SGSN was chosen among a pool, then the **Relocation Cancel Request** message is sent to this SGSN. + +4. The new SGSN triggers the release of resources in the target cell by sending an **Iu Release Command** message to the target RNC +5. The target RNC releases all resources allocated for this handover and returns an **Iu Release Complete** message to the new SGSN. +6. The new SGSN releases its own resources allocated for this handover and acknowledges the release of all resources on the target side by returning a **Relocation Cancel Response** message to the old SGSN. + +NOTE 4: In the intra-SGSN case, the messages **Relocation Cancel Request** and **Relocation Cancel Response** are not exchanged since the old and new SGSN are then the same node. + +##### 5.7.2.1.2 Radio contact with the MS is lost: + +After sending a **PS Handover Command** message to the MS, if the source BSS detects that radio contact with the MS has been lost (see sub-clause 5.5.1): + +- In case of optimised intra-BSS PS handover, the BSS shall release the assigned resource in both the source cell and target cell. +- In case of SGSN involved PS handover, the source BSS shall release the assigned resource in the source cell and initiate the PS Handover Cancel procedure to release the reserved resource in the target cell. + +The signalling flows for this procedure are depicted in figures 21b and 21c. + +![Sequence diagram for Figure 21b: Radio Contact lost with MS; Inter-SGSN case, GERAN A/Gb mode → GERAN A/Gb mode. The diagram shows the interaction between MS, Source BSS, Target BSS, Old SGSN, New SGSN, and GGSN. The sequence starts with the Source BSS sending a PS Handover Command to the MS. A dashed box labeled '2. Radio Contact lost with MS' indicates a timeout or loss of contact. The Source BSS then sends a PS Handover Cancel to the Old SGSN. The Old SGSN sends a Relocation Cancel Request to the New SGSN. The New SGSN sends a Delete BSS PFC Procedure to the Target BSS (dashed line). Finally, the New SGSN sends a Relocation Cancel Response to the Old SGSN.](5e9af8986a5845504f251d3079da8078_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Source BSS + participant Target BSS + participant Old SGSN + participant New SGSN + participant GGSN + + Note right of Source BSS: 2. Radio Contact lost with MS + Source BSS->>MS: 1. PS Handover Command + Note right of MS: Radio Contact lost with MS + Source BSS->>Old SGSN: 3. PS Handover Cancel + Old SGSN->>New SGSN: 4. Relocation Cancel Request + Note right of New SGSN: 5. Delete BSS PFC Procedure + New SGSN-->>Target BSS: 5. Delete BSS PFC Procedure + New SGSN->>Old SGSN: 6. Relocation Cancel Response + +``` + +Sequence diagram for Figure 21b: Radio Contact lost with MS; Inter-SGSN case, GERAN A/Gb mode → GERAN A/Gb mode. The diagram shows the interaction between MS, Source BSS, Target BSS, Old SGSN, New SGSN, and GGSN. The sequence starts with the Source BSS sending a PS Handover Command to the MS. A dashed box labeled '2. Radio Contact lost with MS' indicates a timeout or loss of contact. The Source BSS then sends a PS Handover Cancel to the Old SGSN. The Old SGSN sends a Relocation Cancel Request to the New SGSN. The New SGSN sends a Delete BSS PFC Procedure to the Target BSS (dashed line). Finally, the New SGSN sends a Relocation Cancel Response to the Old SGSN. + +**Figure 21b: Radio Contact lost with MS; Inter-SGSN case, GERAN A/Gb mode → GERAN A/Gb mode** + +1. The source BSS sends a **PS Handover Command** message to the MS. +2. The source BSS receives no indication that the MS has made access in the target cell, nor that it has returned to the source cell. +3. The source BSS sends a **PS Handover Cancel** (TLLI, Cause = Radio Contact Lost with MS, Source Cell Identifier, Target Cell Identifier) PDU to the old SGSN. + +NOTE 5: If the old SGSN has already received a **Forward Relocation Complete** message when the **PS Handover Cancel** PDU is received, the old SGSN ignores the **PS Handover Cancel** PDU. + +4. The old SGSN terminates the PS Handover to the target cell by sending a **Relocation Cancel Request** (IMSI) message to the new SGSN. + +NOTE 6: If one new SGSN was chosen among a pool, then the **Relocation Cancel Request** message is sent to this SGSN. + +NOTE 7: If the MS has successfully made access on the target side when the **Relocation Cancel Request** message is received by the new SGSN, the new SGSN does not release any resources on the target side, but instead goes directly to step 6 below. + +NOTE 8: If the resources on the target side have, due to some local decision on the target side, already been released when the **Relocation Cancel Request** message is received by the new SGSN, then the new SGSN goes directly to step 6 below. + +5. The new SGSN triggers the release of resources in the target cell and also releases its own resources allocated for this handover. +6. The new SGSN returns a **Relocation Cancel Response** message to the old SGSN which then releases all its resources for this connection. + +NOTE 9: In the intra-SGSN case, the messages **Relocation Cancel Request** and **Relocation Cancel Response** are not exchanged since the old and new SGSN are then the same node. + +![Sequence diagram for Figure 21c: Radio Contact lost with MS; Inter-SGSN case, GERAN A/Gb mode -> UTRAN/GERAN Iu mode. The diagram shows the interaction between MS, Source BSS, Target RNC, Old 2G SGSN, New 3G SGSN, and GGSN. The sequence starts with a PS Handover Command from Source BSS to MS. A dashed box labeled '2. Radio Contact lost with MS.' is shown between Source BSS and MS. The Source BSS then sends a PS Handover Cancel to the Old 2G SGSN. The Old 2G SGSN sends a Relocation Cancel Request to the New 3G SGSN. The New 3G SGSN sends an Iu Release Command to the Target RNC. The Target RNC sends an Iu Release Complete to the New 3G SGSN. Finally, the New 3G SGSN sends a Relocation Cancel Response to the Old 2G SGSN.](4b398c5e8c4fd656d5b7a61806400650_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Source BSS + participant Target RNC + participant Old 2G SGSN + participant New 3G SGSN + participant GGSN + + Note right of Source BSS: 2. Radio Contact lost with MS. + Source BSS->>MS: 1. PS Handover Command + Source BSS->>Old 2G SGSN: 3. PS Handover Cancel + Old 2G SGSN->>New 3G SGSN: 4. Relocation Cancel Request + New 3G SGSN->>Target RNC: 5. Iu Release Command + Target RNC-->>New 3G SGSN: 6. Iu Release Complete + New 3G SGSN->>Old 2G SGSN: 7. Relocation Cancel Response + +``` + +Sequence diagram for Figure 21c: Radio Contact lost with MS; Inter-SGSN case, GERAN A/Gb mode -> UTRAN/GERAN Iu mode. The diagram shows the interaction between MS, Source BSS, Target RNC, Old 2G SGSN, New 3G SGSN, and GGSN. The sequence starts with a PS Handover Command from Source BSS to MS. A dashed box labeled '2. Radio Contact lost with MS.' is shown between Source BSS and MS. The Source BSS then sends a PS Handover Cancel to the Old 2G SGSN. The Old 2G SGSN sends a Relocation Cancel Request to the New 3G SGSN. The New 3G SGSN sends an Iu Release Command to the Target RNC. The Target RNC sends an Iu Release Complete to the New 3G SGSN. Finally, the New 3G SGSN sends a Relocation Cancel Response to the Old 2G SGSN. + +**Figure 21c: Radio Contact lost with MS; Inter-SGSN case, GERAN A/Gb mode→ UTRAN/GERAN Iu mode** + +1. The source BSS sends a **PS Handover Command** message to the MS. +2. The source BSS receives no indication that the MS has made access in the target cell, nor that it has returned to the source cell. +3. The source BSS sends a **PS Handover Cancel** (TLLI, Cause = Radio Contact Lost with MS, Source Cell Identifier, Target Cell Identifier) PDU to the old SGSN. + +NOTE 10: If the old SGSN has already received a **Forward Relocation Complete** message when the **PS Handover Cancel** PDU is received, the old SGSN ignores the **PS Handover Cancel** PDU. + +4. The old SGSN terminates the PS Handover to the target cell by sending a **Relocation Cancel Request** (IMSI) message to the new SGSN. + +NOTE 11: If one new SGSN was chosen among a pool, then the **Relocation Cancel Request** message is sent to this SGSN. + +NOTE 12: If the MS has successfully made access on the target side when the **Relocation Cancel Request** message is received by the new SGSN, the new SGSN does not release any resources on the target side, but instead goes directly to step 7 below. + +NOTE 13: If the resources on the target side have, due to some local decision on the target side, already been released when the **Relocation Cancel Request** message is received by the new SGSN, then the new SGSN goes directly to step 7 below. + +5. The new SGSN triggers the release of resources in the target cell by sending an **Iu Release Command** message to the target RNC. +6. The target RNC releases all resources allocated for this handover and returns an **Iu Release Complete** message to the new SGSN which then releases its own resources allocated for this handover. +7. The new SGSN returns a **Relocation Cancel Response** message to the old SGSN which then releases all its resources for this connection. + +NOTE 14: In the intra-SGSN case, the messages **Relocation Cancel Request** and **Relocation Cancel Response** are not exchanged since the old and new SGSN are then the same node. + +#### 5.7.2.2 Execution phase failures on the Gb interface + +- Generic Causes: + +- Generic causes for the Gb interface failures are defined in 3GPP TS 48.018 [10]. The same cause values are applicable to the PS handover procedure. + +#### 5.7.2.3 Execution phase failures on the Gn interface + +- Update PDP Context failure: + - As specified in 3GPP TS 29.060 [11] if the new SGSN receives an **Update PDP Context Response** message from the GGSN with a cause value other than 'Request accepted', it shall abort the update of the PDP context. Such a PDP context may be modified or deactivated by the new SGSN via explicit SM procedures upon the completion of the routing area update (RAU) procedure. + +## 5.8 GAN Handover + +### 5.8.1 Intra-SGSN Handover (GERAN A/Gb mode → GAN mode handover) + +#### 5.8.1.1 Intra SGSN PS Handover, Preparation phase + +![Sequence diagram of PS Handover Preparation Phase for Intra-SGSN (GERAN A/Gb mode → GAN mode). The diagram shows four lifelines: MS, Source BSS, Target GANC, and SGSN. The sequence starts with the MS detecting GAN mode service. It then sends a GAN Registration message to the Target GANC. The Source BSS sends a PS Handover Required message to the SGSN. The SGSN sends a PS Handover Request to the Target GANC. The Target GANC sends a PS Handover Request Ack to the SGSN. The SGSN sends a GA-PSR Transport Channel Allocation message to the Source BSS. The Source BSS sends a PS Handover Command to the MS.](a7721892ae499a78173ff3dfdc4e65a9_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Source BSS + participant Target GANC + participant SGSN + + Note left of MS: GAN mode service detected + MS->>Target GANC: 2. GAN Registration + Note right of Target GANC: 3. Decision to perform PS Handover + Source BSS->>SGSN: 4. PS Handover Required + SGSN->>Target GANC: 5. PS Handover Request + Target GANC->>SGSN: 7. PS Handover Request Ack + SGSN->>Source BSS: 6. GA-PSR Transport Channel Allocation + Source BSS->>MS: PS Handover Command + +``` + +Sequence diagram of PS Handover Preparation Phase for Intra-SGSN (GERAN A/Gb mode → GAN mode). The diagram shows four lifelines: MS, Source BSS, Target GANC, and SGSN. The sequence starts with the MS detecting GAN mode service. It then sends a GAN Registration message to the Target GANC. The Source BSS sends a PS Handover Required message to the SGSN. The SGSN sends a PS Handover Request to the Target GANC. The Target GANC sends a PS Handover Request Ack to the SGSN. The SGSN sends a GA-PSR Transport Channel Allocation message to the Source BSS. The Source BSS sends a PS Handover Command to the MS. + +**Figure 5.8-1: PS Handover Preparation Phase; Intra-SGSN (GERAN A/Gb mode → GAN mode)** + +1. While in a GERAN cell with one or more active packet sessions an MS uses neighbour cell list information for measurement and reporting purposes and eventually detects the presence of GAN mode service. +2. The MS performs a successful GAN registration (see 3GPP TS 43.318) and receives the ARFCN/BSIC corresponding to the GANC on which it has registered. The MS may then at some point send a PACKET CELL CHANGE NOTIFICATION message that includes the ARFCN/BSIC received during GAN registration along with an RXLEV of 63 (either immediately if GAN mode is preferred or when the GERAN cell becomes sufficiently degraded if GERAN/UTRAN mode is preferred). +3. The source BSS decides to initiate a PS handover. At this point both uplink and downlink user data is transmitted via the following: TBFs between MS and source BSS, BSSGP PFCs tunnel(s) between the source BSS and SGSN, GTP tunnel(s) between the SGSN and GGSN. +4. The source BSS sends a **PS Handover Required** (Old TLLI, Cause, Source Cell Identifier, Target Cell Identifier, Source BSS to Target BSS Transparent Container (RN part)) message to the SGSN. +5. The SGSN determines from the Target Cell Identifier whether or not the routing area has changed and that an Intra-SGSN PS handover is required. In case of no change of routing area, the SGSN sends a **PS Handover Request** (TLLI, Cause, IMSI, Source Cell Identifier, Target Cell Identifier, PFCs To Be Set Up List, Source BSS to Target BSS Transparent Container (RN part)) message to the target GANC. In case the routing area changes, the SGSN shall assign a new P-TMSI for the MS and derive a local TLLI prior to the sending of the **PS Handover Request** message. All PFCs shall be included in this message regardless of whether or not they are active. + +NOTE 1: The BSS PFCs required to be set up are downloaded to the target GANC from the SGSN, i.e. all information required for PFC creation. + +6. Based upon the ABQP for each PFC the target GANC makes a decision about whether or not to activate a GA-PSR Transport Channel. If a GA-PSR Transport Channel is allocated it is used to support the packet data flow requirements of all requested PFCs. The details of this decision are implementation specific but could take into account the current GAN cell loading and the ABQP indicated for each requested PFC. The target GANC allocates a GA-PSR Transport Channel as described in 3GPP TS 43.318. After allocating the GA-PSR Transport Channel the target GANC shall prepare the Target BSS to Source BSS Transparent Container for the set up BSS PFCs. +7. The target GANC sends the **PS Handover Request Acknowledge** (TLLI, List of Set Up PFCs, Target BSS to Source BSS Transparent Container (RN part)) message to the SGSN. Upon sending the **PS Handover Request Acknowledge** message the target GANC shall be prepared to receive downlink LLC PDUs from the SGSN for all requested PFCs (i.e. the List of Set Up PFCs in this message shall always match the PFCs To Be Set Up List included in the corresponding **PS Handover Request** message since a GA-PSR Transport Channel is allocated with the intent of supporting all PFCs requested by the SGSN). + +When the SGSN receives the **PS Handover Request Acknowledge** message and it decides to proceed with the handover, the preparation phase is finished and the execution phase will follow. + +#### 5.8.1.2 Intra SGSN PS Handover, Execution phase + +The execution phase is the same as described for Intra SGSN, GERAN A/Gb mode to GERAN A/Gb mode PS handover except for the following: + +- The BSS sends the **PS Handover Command** message where the RN part does not include any of the optional information. +- After receiving the **PS Handover Command** message in the source cell the MS determines that the indicated ARFCN and BSIC match those of the GAN cell that it last registered on and therefore does not perform system synchronization in the GAN cell. Instead, the MS enables the transmission of uplink LLC PDUs on the allocated GA-PSR Transport Channel and sends a GA-PSR HANDOVER COMPLETE message to the target GANC. Note that the reception of downlink LLC PDUs is enabled in the MS upon allocation of the GA-PSR Transport Channel during the preparation phase. +- Upon reception of the GA-PSR HANDOVER COMPLETE message from the MS in the GAN cell the target GANC sends a PS Handover Complete (TLLI, IMSI, Target Cell Identifier) message to the SGSN. + +### 5.8.2 Intra-SGSN Handover (GAN mode → GERAN A/Gb mode handover) + +#### 5.8.2.1 Intra SGSN PS Handover, Preparation phase + +The preparation phase is the same as described for Intra SGSN, GERAN A/Gb mode to GERAN A/Gb mode PS handover except for the following: + +- While in a GAN cell an MS sends the **GA-PSR HANDOVER INFORMATION** message to the GANC indicating a list of target GERAN A/Gb mode cells, identified by CGI, in order of preference for PS handover, and includes the received signal strength for each identified GERAN A/Gb mode cell. The MS decision to send the **GA-PSR HANDOVER INFORMATION** may be based on local measurements in the MS (see 3GPP TS 44.318 [28]). This list is the most recent information available from the GSM RR subsystem. In addition, the **GA-PSR HANDOVER INFORMATION** message may include a list of target UTRAN cells ranked in order of preference for PS handover, and the received signal strength for each identified UTRAN cell. +- The source GANC selects a target GERAN A/Gb mode cell and triggers the PS handover preparation phase by signalling to the SGSN the need for PS handover (i.e. it sends the PS Handover Required message) and including the target GERAN A/Gb mode cell. +- When the source GANC decides to trigger a PS handover both uplink and downlink user data is transmitted via the GA-PSR Transport Channel between MS and source GANC, BSSGP PFCs tunnel(s) between the source GANC and SGSN, and GTP tunnel(s) between the SGSN and GGSN. + +#### 5.8.2.2 Intra SGSN PS Handover, Execution phase + +The execution phase is the same as described for Intra SGSN, GERAN A/Gb mode to GERAN A/Gb mode PS handover except for the following: + +- The SGSN sends a PS Handover Required Acknowledge (Old TLLI, List of Set Up PFCs, Target BSS to Source BSS Transparent Container (RN part)) message to the source GANC. +- Before sending the **GA-PSR HANDOVER COMMAND** message to the MS the source GANC, based on QoS, may try to empty the downlink GANC buffer for one or more PFCs. +- The source GANC interrupts the downlink transmission of LLC PDUs on the GA-PSR Transport Channel and sends the MS a **GA-PSR HANDOVER COMMAND** message that includes a **PS Handover Command** (RN part only) created by the target BSS. + +### 5.8.3 Inter-SGSN Handover (GERAN A/Gb mode → GAN mode handover) + +#### 5.8.3.1 Inter SGSN PS Handover, Preparation phase + +The preparation phase is the same as described for Intra SGSN, GERAN A/Gb mode to GAN mode PS handover except that Inter-SGSN communications are required and are as described for Inter-SGSN A/Gb mode to A/Gb mode PS handover. + +#### 5.8.3.2 Inter SGSN PS Handover, Execution phase + +The execution phase is the same as described for the Intra SGSN PS Handover, Execution phase in sub-clause 5.8.1.2. + +### 5.8.4 Inter-SGSN Handover (GAN mode → GERAN A/Gb mode handover) + +#### 5.8.4.1 Inter SGSN PS Handover, Preparation phase + +The preparation phase is the same as described for Inter SGSN, GERAN A/Gb mode to GERAN A/Gb mode PS handover except for the following: + +- While in a GAN cell an MS sends the **GA-PSR HANDOVER INFORMATION** message to the GANC indicating a list of target GERAN A/Gb mode cells, identified by CGI, in order of preference for PS handover, and includes the received signal strength for each identified GERAN A/Gb mode cell. The MS decision to send the **GA-PSR HANDOVER INFORMATION** message may be based on local measurements in the MS (see 3GPP TS 44.318 [28]). This list is the most recent information available from the GSM RR subsystem. In addition, the **GA-PSR HANDOVER INFORMATION** message may include a list of target UTRAN cells ranked in order of preference for PS handover, and the received signal strength for each identified UTRAN cell. +- The source GANC selects a target GERAN A/Gb mode cell and triggers the PS handover preparation phase by signalling to the SGSN the need for PS handover (i.e. it sends the PS Handover Required message) and including the GERAN A/Gb mode target cell. +- When the source GANC decides to trigger a PS handover both uplink and downlink user data is transmitted via the GA-PSR Transport Channel between MS and source GANC, BSSGP PFCs tunnel(s) between the source GANC and SGSN, GTP tunnel(s) between the SGSN and GGSN. + +#### 5.8.4.2 Inter SGSN, Execution phase + +The execution phase is the same as described for the Intra SGSN PS Handover, Execution phase in sub-clause 5.8.2.2. + +### 5.8.5 Inter RAT Handover; Intra SGSN (UTRAN → GAN mode handover) + +#### 5.8.5.1 Intra SGSN PS Handover, Preparation phase + +![Sequence diagram illustrating the PS Handover Preparation Phase for Intra-SGSN (UTRAN to GAN mode). The diagram shows four lifelines: MS, Source RNC/BSS, Target GANC, and 3G/2G SGSN. The sequence of messages is: 1. GAN mode service detected (MS to Source RNC/BSS); 2. GAN Registration (MS to Target GANC); 3. Decision to perform PS Handover (Source RNC/BSS to Target GANC); 4. Relocation Required (Source RNC/BSS to 3G/2G SGSN); 5. PS Handover Request (3G/2G SGSN to Target GANC); 6. GA-PSR Transport Channel Allocation (Target GANC to MS); 7. PS Handover Request Ack (Target GANC to 3G/2G SGSN).](57939c16065211317c5442cf2a4009e0_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Source RNC/BSS + participant Target GANC + participant 3G/2G SGSN + + Note left of MS: 1. GAN mode service detected + MS->>Source RNC/BSS: 2. GAN Registration + Note right of Source RNC/BSS: 3. Decision to perform PS Handover + Source RNC/BSS->>Target GANC: 4. Relocation Required + Source RNC/BSS->>3G/2G SGSN: 4. Relocation Required + 3G/2G SGSN->>Target GANC: 5. PS Handover Request + Target GANC->>MS: 6. GA-PSR Transport Channel Allocation + Target GANC->>3G/2G SGSN: 7. PS Handover Request Ack + +``` + +Sequence diagram illustrating the PS Handover Preparation Phase for Intra-SGSN (UTRAN to GAN mode). The diagram shows four lifelines: MS, Source RNC/BSS, Target GANC, and 3G/2G SGSN. The sequence of messages is: 1. GAN mode service detected (MS to Source RNC/BSS); 2. GAN Registration (MS to Target GANC); 3. Decision to perform PS Handover (Source RNC/BSS to Target GANC); 4. Relocation Required (Source RNC/BSS to 3G/2G SGSN); 5. PS Handover Request (3G/2G SGSN to Target GANC); 6. GA-PSR Transport Channel Allocation (Target GANC to MS); 7. PS Handover Request Ack (Target GANC to 3G/2G SGSN). + +**Figure 5.8-2: PS Handover Preparation Phase; Intra-SGSN (UTRAN → GAN mode)** + +1. While in a UTRAN cell with one or more active packet sessions an MS uses neighbour cell list information for measurement and reporting purposes and eventually detects the presence of GAN mode service. +2. The MS performs a successful GAN registration (see 3GPP TS 43.318) and receives the ARFCN/BSIC corresponding to the GANC on which it has registered. The MS may at some point begin sending measurement reports that include the ARFCN/BSIC received during GAN registration along with an RXLEV of 63 (either immediately if GAN mode is preferred or when the UTRAN cell becomes sufficiently degraded if GERAN/UTRAN mode is preferred) for the GAN cell and report an RXLEV of 63. +3. The source RNC/BSS decides to initiate a PS handover. +4. The source RNC/BSS sends a **Relocation Required** (Relocation Type, Cause, Source ID, Target ID, Source BSS To Target BSS Transparent Container (RN part)) message to the 3G/2G SGSN. The source RNC/BSS shall set Relocation Type to "UE Involved in relocation of SRNS". Target ID contains the identity of the target cell. +5. The SGSN determines from the Target ID whether or not the routing area has changed and that an Intra-SGSN PS handover is required. In case of no change of routing area, the SGSN sends a **PS Handover Request** (TLLI, Cause, IMSI, Source Cell Identifier, Target ID, PFCs To Be Set Up List, Source BSS to Target BSS Transparent Container (RN part)) message to the target GANC. In case the routing area changes, the SGSN shall assign a new P-TMSI for the MS and derive a local TLLI prior to the sending of the **PS Handover Request** message. All PFCs shall be included in this message regardless of whether or not they are active. + +NOTE 1: The BSS PFCs required to be set up are downloaded to the target GANC from the SGSN, i.e. all information required for PFC creation. + +6. Based upon the ABQP for each PFC the target GANC makes a decision about whether or not to activate a GA-PSR Transport Channel. If a GA-PSR Transport Channel is allocated it is used to support the packet data flow requirements of all requested PFCs. The details of this decision are implementation specific but could take into account the current GAN cell loading and the ABQP indicated for each requested PFC. The target GANC allocates a GA-PSR Transport Channel as described in 3GPP TS 43.318. After allocating the GA-PSR Transport Channel the target GANC shall prepare the Target BSS to Source BSS Transparent Container for the set up BSS PFCs. +7. The target GANC sends the **PS Handover Request Acknowledge** (TLLI, List of Set Up PFCs, Target BSS to Source BSS Transparent Container (RN part)) message to the SGSN. Upon sending the **PS Handover Request Acknowledge** message the target GANC shall be prepared to receive downlink LLC PDUs from the SGSN for all requested PFCs (i.e. the List of Set Up PFCs in this message shall always match the PFCs To Be Set Up List). + +included in the corresponding **PS Handover Request** message since a GA-PSR Transport Channel is allocated with the intent of supporting all PFCs requested by the SGSN). + +When the SGSN receives the **PS Handover Request Acknowledge** message and it decides to proceed with the handover, the preparation phase is finished and the execution phase will follow. + +#### 5.8.5.2 Intra SGSN PS Handover, Execution phase + +The execution phase is the same as described for Intra SGSN, UTRAN/GERAN Iu mode to GERAN A/Gb mode PS handover except for the following: + +- The RNC sends the **Handover from UTRAN Command** message to the MS where each message includes a **PS Handover Command** message where the RN part does not include any of the optional information. +- After receiving the **Handover from UTRAN Command** message in the source cell the MS determines that the indicated ARFCN and BSIC match those of the GAN cell that it last registered on and therefore does not perform system synchronization in the GAN cell. Instead, the MS enables the transmission of uplink LLC PDUs on the allocated GA-PSR Transport Channel and sends a GA-PSR HANDOVER COMPLETE message to the target GANC. Note that the reception of downlink LLC PDUs is enabled in the MS upon allocation of the GA-PSR Transport Channel during the preparation phase. +- Upon reception of the GA-PSR HANDOVER COMPLETE message from the MS in the GAN cell the target GANC sends a PS Handover Complete (TLLI, IMSI, Target Cell Identifier) message to the SGSN. + +### 5.8.6 Inter RAT Handover; Intra SGSN (GAN mode →UTRAN handover) + +#### 5.8.6.1 Intra SGSN PS Handover, Preparation phase + +The preparation phase is the same as described for Intra SGSN, GERAN A/Gb mode to UTRAN/GERAN Iu mode PS handover except for the following: + +- While in a GAN cell an MS sends the GA-PSR HANDOVER INFORMATION message to the GANC indicating a list of target UTRAN cells, identified by a combination of LAI and 3G Cell Identity/CGI, in order of preference for PS handover, and includes the received signal strength for each identified UTRAN cell. The MS decision to send the GA-PSR HANDOVER INFORMATION may be based on local measurements in the MS (see 3GPP TS 44.318 [28]). This list is the most recent information available from the UTRAN RRC/GSM RR subsystem. In addition, the GA-PSR HANDOVER INFORMATION message may include a list of target GERAN A/Gb mode cells ranked in order of preference for PS handover, and the received signal strength for each identified GERAN A/Gb mode cell. +- The source GANC selects a target UTRAN cell and triggers the PS handover preparation phase by signalling to the SGSN the need for PS handover (i.e. it sends the PS Handover Required message) and including the target UTRANcell. +- When the source GANC decides to trigger a PS handover both uplink and downlink user data is transmitted via the GA-PSR Transport Channel between MS and source GANC, BSSGP PFCs tunnel(s) between the source GANC and SGSN, GTP tunnel(s) between the SGSN and GGSN. + +#### 5.8.6.2 Intra SGSN, Execution phase + +The execution phase is the same as described for Intra SGSN, GERAN A/Gb mode to UTRAN/GERAN Iu mode PS handover except for the following: + +- The SGSN sends a **PS Handover Required Acknowledge** (Old TLLI, List of Set Up PFCs, Target BSS to Source BSS Transparent Container (RN part)) message to the source GANC. +- Before sending the **GA-PSR HANDOVER COMMAND** message to the MS the source GANC, based on QoS, may try to empty the downlink GANC buffer for one or more PFCs. + +- The source GANC interrupts the downlink transmission of LLC PDUs on the GA-PSR Transport Channel and sends the MS a **GA-PSR HANDOVER COMMAND** message that includes a **Handover to UTRAN Command** message (as specified in 3GPP TS 25.331 [17]) created by the target RNC. + +### 5.8.7 Inter RAT Handover; Inter SGSN (UTRAN → GAN mode handover) + +#### 5.8.7.1 Inter SGSN PS Handover, Preparation phase + +The preparation phase is the same as described for Intra SGSN, UTRAN to GAN mode PS handover except that Inter-SGSN communications are required and are as described for Inter-SGSN UTRAN to A/Gb mode PS handover. + +#### 5.8.7.2 Inter SGSN PS Handover, Execution phase + +The execution phase is the same as described for the Intra SGSN PS Handover, Execution phase in sub-clause 5.8.5.2. + +### 5.8.8 Inter RAT Handover; Inter SGSN (GAN mode → UTRAN handover) + +#### 5.8.8.1 Inter SGSN PS Handover, Preparation phase + +The preparation phase is the same as described for Inter SGSN, GERAN A/Gb mode to UTRAN/GERAN Iu mode PS handover except for the following: + +- While in a GAN cell an MS sends the **GA-PSR HANDOVER INFORMATION** message to the GANC indicating a list of target UTRAN cells, identified by a combination of LAI and 3G Cell Identity/CGI, in order of preference for PS handover, and includes the received signal strength for each identified UTRAN cell. The MS decision to send the **GA-PSR HANDOVER INFORMATION** message may be based on local measurements in the MS (see 3GPP TS 44.318 [28]). This list is the most recent information available from the UTRAN RRC/GSM RR subsystem. In addition, the **GA-PSR HANDOVER INFORMATION** message may include a list of target GERAN A/Gb mode cells ranked in order of preference for PS handover, and the received signal strength for each identified GERAN A/Gb mode cell. +- The source GANC selects a target UTRAN cell and triggers the PS handover preparation phase by signalling to the SGSN the need for PS handover (i.e. it sends the PS Handover Required message) and including the target UTRAN cell. +- When the source GANC decides to trigger a PS handover both uplink and downlink user data is transmitted via the GA-PSR Transport Channel between MS and source GANC, BSSGP PFCs tunnel(s) between the source GANC and SGSN, and GTP tunnel(s) between the SGSN and GGSN. + +#### 5.8.8.2 Inter SGSN PS Handover, Execution phase + +The execution phase is the same as described for the Intra SGSN, Execution phase in sub-clause 5.8.6.2. + +# --- 6 Radio interface Signalling + +## 6.1 PS Handover Signalling (Um) + +### 6.1.1 General + +PS Handover signalling includes the set of all air interface messages (Um signalling for A/Gb mode, Up signalling for GAN mode and Uu signalling for Iu mode) sent to or from the MS in the source and target cells during the PS handover procedure. + +### 6.1.2 Overview of PS Handover messages + +#### 6.1.2.1 GERAN A/Gb mode/GAN mode to GERAN A/Gb mode PS Handover + +When performing an inter-SGSN PS Handover from GERAN A/Gb mode/GAN mode to GERAN A/Gb mode the following information is sent over the Um and Up interfaces. + +- **PS Handover Command** message (for PS handover from GERAN A/Gb mode) or a **GA-PSR HANDOVER COMMAND** message including a **PS Handover Command** message (for PS handover from GAN mode) - sent to the MS in the source cell and includes the following: + - optionally, the NAS container for PS HO + - Indication of the radio resources for uplink and downlink TBFs to be used in the target cell for each PFC receiving PS handover treatment (i.e. the reverse path container created by target BSS/RNC). + - Indication of a PS handover reference number to be used when the MS arrives in the target cell. +- **PS Handover Access** message - the MS sends 4 handover access bursts in the target cell using an uplink TBF provided by the PS Handover Command. If multiple uplink TBFs are provided by the **PS Handover Command** message the MS sends access bursts using just one of these TBFs (i.e. at minimum one uplink TBF must be provided in the **PS Handover Command** message). The handover reference number is included within each access burst. This message is always sent for the case of non-synchronised handover and may still be sent for the case of synchronised or pre-synchronised handovers (determined by the target BSS during the PS handover preparation phase) to allow the target BSS to verify the accessing MS. +- **Packet Physical Information** message - sent by the target BSS to the MS in the target cell in response to the **PS Handover Access** message for the case of unsynchronised cells. Whether or not this message is sent in case of synchronised cells is indicated by the **PS Handover command** message (see 3GPP TS 44.018 [25]). It is sent using the downlink PACCH associated with the uplink TBF used to send the access bursts and provides the MS with physical layer information (i.e. Timing Advance). The time alignment information received in this message applies to all uplink TBFs allocated to the MS in the **PS Handover Command** message. The target BSS only sends this information if it receives the expected handover reference number in a **PS Handover Access** message. +- Uplink RLC Data Blocks - sent on uplink TBFs allocated by the **PS Handover Command** message after the MS receives **Packet Physical Information** message as follows: + - For inter-SGSN PS handover the MS, prior to sending any uplink user plane payload for any PFC, shall send an **XID Response** message . +- Downlink RLC Data Blocks - sent on downlink TBFs allocated by the **PS Handover Command** message as follows: + - For inter-SGSN PS handover for a given PFC the new SGSN may begin downlink N-PDU transmissions for that PFC prior to receiving a **PS Handover Complete** message (i.e. blind transmission may be used) or it may wait for a **PS Handover Complete** message before beginning downlink N-PDU transmissions for that PFC. +- **GA-PSR HANDOVER INFORMATION** message (for PS handover from GAN mode) – sent from the MS to the GANC to provide a list of target GERAN A/Gb mode cells, identified by CGI, in order of preference for PS handover, and includes the received signal strength for each identified GERAN A/Gb mode cell. +- **GA-PSR UPLINK QUALITY INDICATION** message (for PS handover from GAN mode) – sent from the GANC to the MS to provide it with PS service related information as perceived by the GANC which may result in the MS triggering the PS handover procedure (i.e. sending a **GA-PSR HANDOVER INFORMATION** message). + +#### 6.1.2.2 UTRAN/GERAN Iu mode to GERAN A/Gb mode/GAN mode PS Handover + +When performing a PS Handover from UTRAN/GERAN Iu mode to GERAN A/Gb mode or from UTRAN to GAN mode the following the following information is sent over the Uu, Up and Um interfaces: + +- RRC Message - sent to the MS in the source cell and includes the same information described for the PS Handover Command in clause 6.1.2.1. +- For PS handover from UTRAN to GERAN A/Gb mode/GAN mode the Handover from UTRAN Command (3GPP TS 25.331 [17]) message is used in CELL\_DCH and CELL\_FACH state when only PS RABs are established. + +- For PS handover from GERAN Iu mode to GERAN A/Gb mode the HANDOVER FROM GERAN IU COMMAND message is used in RRC-Cell\_Dedicated (MAC Dedicated or MAC DTM state) or RRC-Cell\_Shared state when only PS RABs are established. +- **PS Handover Access** message (for PS handover to GERAN A/Gb mode) - sent as described in clause 6.1.2.1. +- **Packet Physical Information** message (for PS handover to GERAN A/Gb mode) - sent as described in clause 6.1.2.1. +- Uplink RLC Data Blocks (for PS handover to GERAN A/Gb mode) - sent as described in clause 6.1.2.1. +- Downlink RLC Data Blocks (for PS handover to GERAN A/Gb mode) - sent as described in clause 6.1.2.1. +- The target BSS/GANC may begin downlink LLC PDU transmissions prior to confirming the successful completion of the PS handover procedure (i.e. blind transmission may be used) or it may wait for an uplink RLC data block (target BSS) or a GA-PSR HANDOVER COMPLETE message (GANC) before beginning downlink N-PDU transmissions. +- **GA-PSR ACTIVATE UTC REQ** message (for PS handover from UTRAN to GAN mode) – sent to the MS from the target GANC to activate the transport channel to be used in the GAN cell. +- **GA-PSR ACTIVATE UTC ACK** message (for PS handover from UTRAN to GAN mode) – sent from the MS to the target GANC to confirm allocation of the transport channel to be used in the GAN cell. +- **GA-PSR HANDOVER COMPLETE** message (for PS handover from UTRAN to GAN mode) – sent from the MS to the target GANC to indicate handover completion. + +#### 6.1.2.3 GERAN A/Gb mode to GERAN Iu mode PS Handover + +When performing a PS Handover from GERAN A/Gb mode to GERAN Iu mode the following information is sent over the Uu and Um interfaces: + +- **PS Handover Command** message - sent to the MS in the source cell and includes the following: + - System broadcast information applicable to the target cell. + - Indication of the radio resources for uplink and downlink TBFs to be used in the target cell for each RAB receiving PS handover treatment (i.e. the reverse path container created by target BSS). Note that the MS will map the N-SAPI associated with each of its active PDP Contexts directly to a RABid (i.e. N-SAPI = RABid). + - Indication of a PS handover reference number to be used when the MS arrives in the target cell. +- **PS Handover Access** message - sent as described in clause 6.1.2.1. +- **Packet Physical Information** message - sent as described in clause 6.1.2.1. +- RRC message (e.g. Physical Channel Reconfiguration Complete) - content is GERAN Iu mode specific. +- Uplink RLC Data Blocks - sent on uplink TBFs allocated by the PS Handover Command message after the MS receives Physical Layer Information (content is GERAN Iu mode specific). +- Downlink RLC Data Blocks - sent on downlink TBFs allocated by the PS Handover Command message (content is GERAN Iu mode specific). + +#### 6.1.2.4 GERAN A/Gb mode/GAN mode to UTRAN mode PS Handover + +When performing a PS Handover from GERAN A/Gb mode/GAN mode to UTRAN mode the following information is sent over the Uu, Up and Um interfaces: + +- **PS Handover Command** message (for PS handover from GERAN A/Gb mode) or **GA-PSR HANDOVER COMMAND** message (for PS handover from GAN mode) - sent to the MS in the source cell. It includes the reverse path container created by the target RNC that consists of the RRC message (i.e. the Handover to UTRAN Command) required to perform PS handover to UTRAN. +- MS Detected by Target RNC - exact procedure and information transfer is UTRAN specific. + +- RRC message (e.g. Physical Channel Reconfiguration Complete) - information content is UTRAN specific. +- **GA-PSR HANDOVER INFORMATION** message (for PS handover from GAN mode) – sent from the MS to the GANC to provide a list of target UTRAN cells, identified by a combination of LAI and 3G Cell Identity, in order of preference for PS handover, and includes the received signal strength for each identified UTRAN cell. +- **GA-PSR UPLINK QUALITY INDICATION** message (for PS handover from GAN mode) – sent from the GANC to the MS to provide it with PS service related information as perceived by the GANC which may result in the MS triggering the PS handover procedure (i.e. sending a **GA-PSR HANDOVER INFORMATION** message). + +# 6.1.2.5 GERAN A/Gb mode to GAN mode PS Handover + +When performing an inter-SGSN PS Handover from GERAN A/Gb mode to GAN mode the following information is sent over the Um and Up interfaces. + +- **PS Handover Command** message - sent to the MS in the source cell and includes the following: + - optionally, the NAS container for PS HO. + - RN information which consists only of the mandatory fields within the PS Handover Radio Resources IE carried within the PS Handover Command message. +- The target GANC may begin downlink LLC PDU transmissions prior to confirming the successful completion of the PS handover procedure (i.e. blind transmission may be used) or it may wait for a **GA-PSR HANDOVER COMPLETE** message before beginning downlink N-PDU transmissions. +- **GA-PSR ACTIVATE UTC REQ** message – sent to the MS from the target GANC to activate the transport channel to be used in the GAN cell. +- **GA-PSR ACTIVATE UTC ACK** message – sent from the MS to the target GANC to confirm allocation of the transport channel to be used in the GAN cell. +- **GA-PSR HANDOVER COMPLETE** message – sent from the MS to the target GANC to indicate handover completion. + +#### 6.1.2.6 GERAN A/Gb mode to E-UTRAN PS Handover + +When performing a PS Handover from GERAN *A/Gb mode* to E-UTRAN the following information is sent over the radio interface: + +- **PS Handover Command** message (for PS handover from GERAN *A/Gb mode*) to the MS in the source cell (on the Um interface). It includes the reverse path container created by the target eNB that consists of the RRC message (i.e. the *RRCConnectionReconfiguration* message) required to perform PS handover to E-UTRAN. +- MS Detected by Target eNB- the exact procedure and information transfer on the Uu interface is E-UTRAN specific 3GPP TS36.300 [30], 3GPP TS36.331 [31]. +- RRC message on the Uu interface - information content is E-UTRAN specific TS36.331 [31]. + +#### 6.1.2.7 E-UTRAN to GERAN A/Gb mode PS Handover + +When performing a PS Handover from E-UTRAN to GERAN *A/Gb mode* the following information is sent over the radio interface: + +- RRC Message - sent to the MS in the source cell (on the Uu interface). It includes the same information described for the PS Handover Command in sub-clause 6.1.2.1. +- The **MobilityFromEUTRACommand** (3GPP TS 36.331 [31]) message is sent to the UE (on the Uu interface). +- **PS Handover Access** message (for PS handover to GERAN A/Gb mode) – sent on the Um interface as described in sub-clause 6.1.2.1. +- **Packet Physical Information** message (for PS handover to GERAN A/Gb mode) – sent on the Um interface as described in sub-clause 6.1.2.1. + +- Uplink RLC Data Blocks (for PS handover to GERAN A/Gb mode) - sent on the Um interface as described in sub-clause 6.1.2.1. +- Downlink RLC Data Blocks (for PS handover to GERAN A/Gb mode) - sent on the Um interface as described in sub-clause 6.1.2.1. +- The target BSS may begin downlink LLC PDU transmissions prior to confirming the successful completion of the PS handover procedure (i.e. blind transmission may be used) or it may wait for an uplink RLC data block (target BSS). + +### 6.1.3 RLC/MAC segmentation + +RLC/MAC segmentation is a feature that provides an additional mechanism for sending control plane messages from the BSS to the MS. This feature can only be used after contention resolution is completed in the BSS and the BSS has to send an RLC/MAC control message that is from 3 to 9 radio blocks long. + +### 6.1.4 Inter RAT/mode PS Handover to GERAN A/Gb + +Void. + +### 6.1.5 Inter RAT/mode PS Handover from GERAN A/Gb + +Void. + +## 6.2 Mechanisms for Initial Access in the Target Cell + +### 6.2.1 General + +This clause describes two possible approaches to the MS making access in the target cell. Both basic approaches assume that a handover procedure similar to that for the CS domain (Handover Access followed by Physical Information messages) takes place. + +The effect of synchronised networks is examined for both approaches where the exchange of Handover Access and Physical Information is not required as the TA can be derived in advance. + +The main assumptions applicable to the call flows are: + +- USFs are required to schedule uplink data blocks. +- All identifiers and resources are known by the MS and target BSS before the MS makes the initial access in the target cell. + +### 6.2.2 Synchronisation of handovers + +The following synchronisation mechanisms are used for PS handover: + +- Non-synchronised. +- Synchronised. +- Pre-Synchronised. + +The non-synchronised cases are shown in figures 22 and 24 and are characterised by the requirement for the MS to obtain a valid uplink timing advance before it can transmit normal bursts. The MS shall notify its presence in the target cell through the transmission of access bursts to the BSS, and the BSS shall respond with a valid timing advance which in turn enables the MS to send normal bursts in uplink. + +The synchronised and pre-synchronised cases are shown in figures 23 and 25 and have different mechanisms for the provision of the timing advance that are described in 3GPP TS 45.010 [26]. + +NOTE: The pseudo-synchronised case is not supported by the PS handover feature. + +### 6.2.3 Option 1 - Downlink Data sent after performing access in the target cell + +In this approach, downlink data is not transmitted until the BSS has been made aware of the presence of the MS via the reception of a **PS Handover Access** message. + +#### 6.2.3.1 Unsynchronised Networks Call Flow + +The message flow for this option is shown in figure 22. The MS starts by sending **PS Handover Access** messages as four access bursts to the network (through USF allocation). As there is no contention, the network should receive at least one of the access bursts. A Handover Reference parameter is allocated by the target BSS in the **PS Handover Command** message and included in the **PS Handover Access** message to verify that the correct MS is accessing the resources. This is similar to the Handover Reference in the CS handover case. + +The BSS receives the **PS Handover Access** message and detects that the correct MS has now made access in the target cell. It sends a **Packet Physical Information** message to indicate that the MS has been detected. The main purpose of this message is to give the Timing Advance information to the MS. + +Once the MS has received the **Packet Physical Information** message it sends uplink LLC PDUs (user or signalling data, depending on the scenario). When correctly receiving the first RLC data block from the MS the target BSS verifies the mobile station, generates a **PS Handover Complete** message and sends it to the new SGSN. + +The MS can start sending uplink RLC/MAC data blocks on the pre-allocated resources when scheduled with its USF. When the **PS Handover Complete** message has been received by the new SGSN, it can start sending downlink data blocks. + +NOTE: The downlink RLC data blocks can be sent for any PFC receiving PS handover treatment after the target BSS has confirmed that the correct MS is present and after the **PS Handover Complete** message has been received by the new SGSN. + +![Sequence diagram showing the call flow for Option 1 - Downlink Data after MS contacts network. The diagram illustrates the interaction between the MS (Mobile Station) and the BSS (Base Station). The sequence of messages is: 1. MS sends 'Packet Handover Access' to BSS via UL PDCH. 2. BSS responds with 'Packet Physical Information (includes TA)' to MS via DL PDCH. 3. MS sends 'First correctly received RLC/MAC block (XID Resp., RAU req. or Cell Update)' to BSS via UL PDCH. 4. BSS sends 'DL Data Block' to MS via DL PDCH. At this point, the MS receives its first downlink data block. 5. MS sends 'UL Data Block' to BSS via UL PDCH. At this point, the MS sends its first uplink data block.](7b2d685b805535c1e94aee1365753b92_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + Note left of MS: First downlink data block received + Note left of MS: First uplink data block sent + MS->>BSS: 1 Packet Handover Access (UL PDCH) + BSS-->>MS: 2 Packet Physical Information (includes TA) (DL PDCH) + MS->>BSS: 3 First correctly received RLC/MAC block (XID Resp., RAU req. or Cell Update) (UL PDCH) + BSS-->>MS: 4 DL Data Block (DL PDCH) + MS->>BSS: 5 UL Data Block (UL PDCH) + +``` + +Sequence diagram showing the call flow for Option 1 - Downlink Data after MS contacts network. The diagram illustrates the interaction between the MS (Mobile Station) and the BSS (Base Station). The sequence of messages is: 1. MS sends 'Packet Handover Access' to BSS via UL PDCH. 2. BSS responds with 'Packet Physical Information (includes TA)' to MS via DL PDCH. 3. MS sends 'First correctly received RLC/MAC block (XID Resp., RAU req. or Cell Update)' to BSS via UL PDCH. 4. BSS sends 'DL Data Block' to MS via DL PDCH. At this point, the MS receives its first downlink data block. 5. MS sends 'UL Data Block' to BSS via UL PDCH. At this point, the MS sends its first uplink data block. + +Figure 22: Option 1 - Downlink Data after MS contacts network + +#### 6.2.3.2 Synchronised Networks Call Flow + +In the case of synchronous networks it is possible for the MS to calculate the TA of the target cell before it moves from the source cell. + +Figure 23 shows the call flow in the case of synchronous networks. In this case it is possible for the MS to start transmitting and receiving messages as soon as it switches to the target cell. + +As described in 3GPP TS 44.018 [25], handover access bursts may optionally be sent if indicated in the handover command message. If no access bursts are sent the MS begins sending uplink LLC PDUs. These PDUs are only sent to verify the MS's presence in the new cell but do not trigger the sending of **Packet Physical Information** message. As + +blind transmission in the downlink is not being used in this scenario, the BSS must wait until a first RLC/MAC block is received (through USF allocation) before transmitting data in the downlink. + +![Sequence diagram for Option 1: Downlink Data after MS contacts network, Synchronous Networks. The diagram shows the interaction between MS and BSS. 1. MS sends '1 PS Handover Access (optional)' to BSS. 2. BSS sends '2 DL Data Block' to MS. A note indicates the BSS waits for a UL message before sending DL data. 3. MS receives '3 First correctly received RLC/MAC block (XID Resp., RAU req. or Cell Update)' from BSS. A note indicates the first downlink data block is received. 4. MS sends '4 UL Data Block' to BSS. A note indicates the first uplink data block is sent. Channels [DL PDCH] and [UL PDCH] are indicated for the data blocks.](64cda8ce20067bc360ce2f3a5c9352b7_img.jpg) + +Sequence diagram for Option 1: Downlink Data after MS contacts network, Synchronous Networks. The diagram shows the interaction between MS and BSS. 1. MS sends '1 PS Handover Access (optional)' to BSS. 2. BSS sends '2 DL Data Block' to MS. A note indicates the BSS waits for a UL message before sending DL data. 3. MS receives '3 First correctly received RLC/MAC block (XID Resp., RAU req. or Cell Update)' from BSS. A note indicates the first downlink data block is received. 4. MS sends '4 UL Data Block' to BSS. A note indicates the first uplink data block is sent. Channels [DL PDCH] and [UL PDCH] are indicated for the data blocks. + +Figure 23: Option 1 - Downlink Data after MS contacts network, Synchronous Networks + +## 6.2.4 Option 2 - Downlink Data sent before performing access in the target cell (Blind Transmission) + +Blind transmission aims at minimising the interruption time on the downlink following handover. The target BSS starts transmitting downlink data on the newly reserved resources in the target cell before the MS has accessed this cell. The message flow for this scheme is shown in figure 24. + +### 6.2.4.1 Unsynchronised Networks Call Flow + +As the BSS must send the Packet Physical Information as an immediate response to the **Packet Handover Access** message, it is unable to send any downlink data at the same time. Therefore the BSS interrupts delivery of downlink data in order to send the Packet Physical Information to the MS. + +![Sequence diagram for Option 2: Blind Transmission in target cell. The diagram shows the interaction between MS and BSS. 1. BSS sends '1 DL Data Block' to MS. A note indicates the first downlink data block is received. 2. MS sends '2 Packet Handover Access' to BSS. 3. BSS sends '3 Packet Physical Information (includes TA)' to MS. 4. MS receives '4 First correctly received RLC/MAC block (XID Resp., RAU req. or Cell Update)' from BSS. 5. MS sends '5 UL Data Block' to BSS. A note indicates the first uplink data block is sent. Channels [DL PDCH] and [UL PDCH] are indicated for the data blocks.](747516f5861a0ddf31e3851da8e34b95_img.jpg) + +Sequence diagram for Option 2: Blind Transmission in target cell. The diagram shows the interaction between MS and BSS. 1. BSS sends '1 DL Data Block' to MS. A note indicates the first downlink data block is received. 2. MS sends '2 Packet Handover Access' to BSS. 3. BSS sends '3 Packet Physical Information (includes TA)' to MS. 4. MS receives '4 First correctly received RLC/MAC block (XID Resp., RAU req. or Cell Update)' from BSS. 5. MS sends '5 UL Data Block' to BSS. A note indicates the first uplink data block is sent. Channels [DL PDCH] and [UL PDCH] are indicated for the data blocks. + +Figure 24: Option 2 - Blind Transmission in target cell + +NOTE 1: DL data is shown as being sent before the Packet Handover Access, but it may be sent by the target BSS at any time in the sequence. The **PS Handover Access** message is sent when being scheduled with the USF. + +NOTE 2: Blind transmission assumes that the downlink data flow for a PFC receiving PS handover treatment may begin before the new SGSN receives the associated **PS Handover Complete** message from the target BSS and before the RAU procedure has started. + +### 6.2.4.2 Synchronised Network Call Flow + +In the case of blind transmission with synchronous networks, downlink data can be sent at the earliest opportunity. This is similar to the case for blind transmission without synchronous networks. However, uplink data transfer is also sped-up as shown in the call flow of figure 25. + +![Sequence diagram showing the call flow for Option 2 - Blind Transmission in target cell, Synchronous Networks. The diagram illustrates the interaction between the Mobile Station (MS) and the Base Station (BSS). The sequence of messages is: 1. DL Data Block (BSS to MS), 2. PS Handover Access (optional) (MS to BSS), 3. First correctly received RLC/MAC block (XID Resp., RAU req. or Cell Update) (MS to BSS), and 4. UL Data Block (MS to BSS). The first downlink data block is received by the MS at the [DL PDCH] channel. The first uplink data block is sent by the MS at the [UL PDCH] channel. Messages 2 and 3 are sent at the same time. The diagram also shows the [UL PDCH] channel for the uplink messages.](9f51a76cae7309a296cbc6997941eb3f_img.jpg) + +The diagram illustrates the call flow for Option 2 - Blind Transmission in target cell, Synchronous Networks. It shows the interaction between the Mobile Station (MS) and the Base Station (BSS). The sequence of messages is as follows: + +- 1 DL Data Block:** Sent from BSS to MS. The MS receives this at the [DL PDCH] channel. +- 2 PS Handover Access (optional):** Sent from MS to BSS. This message is sent at the same time as message 3. +- 3 First correctly received RLC/MAC block (XID Resp., RAU req. or Cell Update):** Sent from MS to BSS. This message is sent at the same time as message 2. +- 4 UL Data Block:** Sent from MS to BSS. The MS sends this at the [UL PDCH] channel. + +Labels on the left indicate key events: "First downlink data block received" and "First uplink data block sent". A note on the right indicates that messages 2 and 3 are sent at the same time. + +Sequence diagram showing the call flow for Option 2 - Blind Transmission in target cell, Synchronous Networks. The diagram illustrates the interaction between the Mobile Station (MS) and the Base Station (BSS). The sequence of messages is: 1. DL Data Block (BSS to MS), 2. PS Handover Access (optional) (MS to BSS), 3. First correctly received RLC/MAC block (XID Resp., RAU req. or Cell Update) (MS to BSS), and 4. UL Data Block (MS to BSS). The first downlink data block is received by the MS at the [DL PDCH] channel. The first uplink data block is sent by the MS at the [UL PDCH] channel. Messages 2 and 3 are sent at the same time. The diagram also shows the [UL PDCH] channel for the uplink messages. + +**Figure 25: Option 2 - Blind Transmission in target cell, Synchronous Networks** + +The **PS Handover Access** message is the first uplink message sent if indicated in the handover command message as described in 3GPP TS44.018. Otherwise one or more RLC/MAC blocks that contain the **XID Response** message will be sent. This case is therefore the best in terms of reduced service interruption time. + +**NOTE:** Blind transmission assumes that the flow of downlink data for a PFC receiving PS handover treatment may begin before the new SGSN receives the **PS Handover Complete** message from the target BSS and before the RAU procedure has started. + +## 6.3 Methods for triggering PS Handover + +A PS Handover is triggered by the BSS based on the received measurement reports or initiated by the reception of the **Packet Cell Change Notification** message from the mobile station. The BSS controls which of the two methods to use for initiating the PS Handover. + +A PS Handover is triggered by the GANC based on the measurement reports received in the **GA-PSR HANDOVER INFORMATION** message or by other trigger conditions (see 3GPP TS 44.318 [28]). + +When PS Handover is triggered by the BSS based on the measurement reports, the mobile station is in NC2 mode. The mobile station sends measurement reports to the network (BSS). When the network has found a new cell meeting the cell reselection criteria, and prepared for the PS Handover in that target cell, it sends the **PS Handover Command** message to the mobile station. + +If not in NC2 mode, the mobile station may, by transmitting a **Packet Cell Change Notification** message according to the Cell Change Notification procedure, make the BSS aware it has found a new cell meeting the cell reselection criteria. The network then prepares for the PS Handover in the indicated target cell and sends the **PS Handover Command** message to the mobile station. In order to avoid that the mobile station performs autonomous cell reselection due to timeout of T3208, the network can order the mobile station to enter NC2 mode by transmitting the **Packet Measurement Order** message in response to the PCCN message. This will keep the mobile station in the cell until the **PS Handover Command** message is sent by the network, thus making it possible for the network to perform all necessary PS handover signalling and set up the radio resources in the target cell. + +--- + +## Annex A (normative): Agreed handover principles + +### A.1 Agreed handover principles + +1. It is the mobile station that is handed over to a target cell when one or more of its PFCs are subject to handover. +2. The source BSS makes the decision to initiate the handover preparation phase when required for PFC(s) subject to handover. +3. Information pertaining to all PDP contexts and PFCs relating to the MS should be sent from the old SGSN to the target SGSN in the handover signalling regardless of their QoS. +4. The target BSS should make the final decision on which PFCs are subject to handover and to assign resources over the Um interface in the target cell. This decision is based on the target BSS being able to fulfil the QoS for these PFCs. +5. The old SGSN decides whether and when to forward data to the TEIDs provided by the new SGSN. +6. It is not required to have resources allocated in advance for bearers which themselves are not determined to be subject to handover by the target BSS. +7. How the target BSS decides which PFCs to accept and which to reject should be implementation specific. +8. For the PS Handover, forwarding of data is performed from the old SGSN either to the target BSS (intra BSS, intra SGSN-inter BSS) or to the new SGSN (inter SGSN); an optional optimisation for intra BSS handover will allow the BSS to decide how to handle the user data flow. +9. An explicit Routing Area Update procedure is performed (if required) when the handover procedure is terminated. +10. The explicit RAU may not contain the following message sequences that are performed already during the handover procedure: + - Transfer of contexts between SGSNs (inter SGSN case). + - Exchange of SNDPCP sequence numbers (inter SGSN case). + - Allocation of P-TMSI. +11. Uplink and downlink data transfer continues during the Routing Area Update procedure. This is possible because certain RAU centric functions are performed during the handover execution phase. +12. The PS Handover service shall support intra BSS, intra SGSN-inter BSS, inter SGSN and inter RAT scenarios. +13. Based on the quality of service parameters the MS or the network may throw away packets available for transmission in the uplink or downlink during the ongoing handover procedure. +14. The source BSS shall only request PS handover for one cell in each **PS Handover Required** message. +15. The PS handover procedure is only performed when the target BSS pre-allocates resource for at least one PFC. In case the target BSS cannot allocate resources for at least one PFC the target BSS shall reject the PS Handover request using the **PS Handover Request Negative Acknowledge** message. +16. In case the mobile fails to synchronize to the target cell within a timeout period after having received a PS Handover Command, shall revert to the source cell and the old "channels". +17. Optionally, in the case of Intra RAT/Mode PS handover, information pertaining to the radio resource realization of the PFCs subject to Handover can be transferred from the source BSS to the target BSS. +18. During the PS Handover preparation phase the new SGSN (assuming RA change) assigns a unique identifier (P-TMSI, Local TLLI) for data transmission in the target cell. This Local TLLI is used for data transfer + +between the target BSS and the new SGSN. This Local TLLI is not sent to the MS. After PS Handover Completion the MS triggers the RAU procedure. After P-TMSI reallocation, which is performed during Routing area update, a new Local TLLI will be derived from the P-TMSI using current MM procedures. + +19. An SGSN supporting PS handover to GERAN *A/Gb mode* shall always assign a valid SAPI and PFI upon PDP Context activation for a PS Handover capable MS. +20. An MME supporting PS handover to GERAN *A/Gb mode* shall always assign a valid SAPI and PFI upon EPS bearer activation for a PS Handover capable MS. + +## Annex B (informative): PS Handover Primitives + +### B.1 Overview + +The set of figures below indicate the primitive exchanges that could occur during a successful PS handover procedure. All numbered primitives shown using bold font are further specified in either 3GPP TS 48.018, 3GPP TS 44.064 or 3GPP TS 44.065 whereas those shown using normal font are only provided for reasons of conceptual completeness (i.e. they provide an example of a primitive that could be implemented in support of the PS handover feature). + +### B.2 Primitives in Source BSS + +![Sequence diagram showing PS Handover Primitives in Source BSS between RR, PFM, and BSSGP entities.](4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg) + +``` +sequenceDiagram + participant RR + participant PFM + participant BSSGP + Note left of RR: PS Handover Command + RR->>PFM: 1. PFMRR-PSHO-REQUIRED.req + PFM->>BSSGP: 2. PFM-PS-HANDOVER-REQUIRED.req + BSSGP->>PFM: PS-HANDOVER-REQUIRED PDU + PFM->>BSSGP: PS-HANDOVER-REQUIRED-ACK PDU + BSSGP->>PFM: 3. PFM-PS-HANDOVER-REQUIRED.cnf + PFM->>RR: 4. PFMRR-PSHO-REQUIRED.cnf + Note right of BSSGP: DELETE-BSS-PFC PDU + BSSGP->>PFM: 5. PFM-DELETE-BSS-PFC.ind + PFM->>BSSGP: 6. PFM-DELETE-BSS-PFC.res + BSSGP->>PFM: DELETE-BSS-PFC-ACK PDU +``` + +The sequence diagram illustrates the interaction between three entities: RR (Radio Resource), PFM (Packet Forwarding Management), and BSSGP (Base Station System Management Protocol) during a PS handover procedure in the Source BSS. The sequence of messages is as follows: + +- RR sends **1. PFMRR-PSHO-REQUIRED.req** to PFM. +- PFM sends **2. PFM-PS-HANDOVER-REQUIRED.req** to BSSGP. +- BSSGP sends PS-HANDOVER-REQUIRED PDU to PFM. +- PFM sends PS-HANDOVER-REQUIRED-ACK PDU to BSSGP. +- BSSGP sends **3. PFM-PS-HANDOVER-REQUIRED.cnf** to PFM. +- PFM sends **4. PFMRR-PSHO-REQUIRED.cnf** to RR. +- At this point, an external PS Handover Command is received by RR. +- BSSGP sends DELETE-BSS-PFC PDU to PFM. +- PFM sends **5. PFM-DELETE-BSS-PFC.ind** to BSSGP. +- BSSGP sends **6. PFM-DELETE-BSS-PFC.res** to PFM. +- PFM sends DELETE-BSS-PFC-ACK PDU to BSSGP. + +Sequence diagram showing PS Handover Primitives in Source BSS between RR, PFM, and BSSGP entities. + +## B.3 Primitives in Old SGSN + +![Sequence diagram showing primitives in Old SGSN between BSSGP, PFM, SM, and GTP entities.](28f2f470a7b2446ae5f525123534383c_img.jpg) + +``` +sequenceDiagram + participant BSSGP + participant PFM + participant SM + participant GTP + + Note left of BSSGP: PS-HANDOVER-REQUIRED PDU + BSSGP->>PFM: 1. PFM-PS-HANDOVER-REQUIRED.ind + PFM->>SM: 2. SMPFM-PSHO-REQUIRED.req + SM->>GTP: 3. GTPSM-PSHO-REQUIRED.req + GTP->>External: Forward Relocation Request + External-->>GTP: Forward Relocation Response + GTP->>SM: 4. GTPSM-PSHO-REQUIRED.cnf + SM->>PFM: 5. SMPFM-PSHO-REQUIRED.cnf + PFM->>BSSGP: 6. PFM-PS-HANDOVER-REQUIRED.res + Note left of BSSGP: PS-HANDOVER-REQUIRED-ACK PDU + GTP->>External: Forward Relocation Complete + External-->>GTP: Forward Relocation Complete Ack + PFM->>SM: 7. PFMGTP-PSHO-COMPLETE.ind + PFM->>BSSGP: 8. PFM-DELETE-BSS-PFC.req + Note left of BSSGP: DELETE-BSS-PFC PDU + BSSGP->>External: DELETE-BSS-PFC-ACK PDU + PFM->>SM: 9. PFM-DELETE-BSS-PFC.cnf +``` + +The sequence diagram illustrates the interaction between four entities: BSSGP, PFM, SM, and GTP. The process begins with an external PS-HANDOVER-REQUIRED PDU arriving at BSSGP. BSSGP sends a primitive 1. PFM-PS-HANDOVER-REQUIRED.ind to PFM. PFM then sends 2. SMPFM-PSHO-REQUIRED.req to SM. SM sends 3. GTPSM-PSHO-REQUIRED.req to GTP. GTP sends a Forward Relocation Request to an external entity. The external entity responds with a Forward Relocation Response to GTP. GTP sends 4. GTPSM-PSHO-REQUIRED.cnf to SM. SM sends 5. SMPFM-PSHO-REQUIRED.cnf to PFM. PFM sends 6. PFM-PS-HANDOVER-REQUIRED.res to BSSGP. BSSGP then sends a PS-HANDOVER-REQUIRED-ACK PDU externally. GTP sends a Forward Relocation Complete to the external entity, which responds with a Forward Relocation Complete Ack. PFM sends 7. PFMGTP-PSHO-COMPLETE.ind to SM. PFM sends 8. PFM-DELETE-BSS-PFC.req to BSSGP. BSSGP receives a DELETE-BSS-PFC PDU externally and sends a DELETE-BSS-PFC-ACK PDU. Finally, PFM sends 9. PFM-DELETE-BSS-PFC.cnf to SM. + +Sequence diagram showing primitives in Old SGSN between BSSGP, PFM, SM, and GTP entities. + +## B.4 Primitives in New SGSN + +![Sequence diagram showing primitives in New SGSN for Forward Relocation. Lifelines: GTP, SM, GMM, SNDPCP, PFM, LLC, BSSGP. The process involves context activation, PS handover request, and completion primitives between the network layers.](145fb9b19dc6513e7bf84c9ba7f083f2_img.jpg) + +``` +sequenceDiagram + participant External + participant GTP + participant SM + participant GMM + participant SNDPCP + participant PFM + participant LLC + participant BSSGP + + Note left of GTP: Forward Relocation Request + GTP->>SM: 1. SMGTP-CONTEXT-ACT.req + SM->>GMM: 2. GMMSM-PSHO.req + GMM->>LLC: 3. LLGMM-PSHO.req + LLC->>SNDPCP: 4. LL-RESET.ind + SNDPCP->>GMM: 5. LLGMM-PSHO.cnf + GMM->>SM: 6. GMMSM-PSHO.cnf + SM->>PFM: 7. PFMSM-PSHO.req + PFM->>BSSGP: 8. PFM-PS-HANDOVER-REQUEST.req + BSSGP->>External: PS-HANDOVER-REQUEST_PDU + External-->>BSSGP: PS-HANDOVER-REQUEST-ACK_PDU + BSSGP->>PFM: 9. PFM-PS-HANDOVER-REQUEST.cnf + PFM->>SM: 10. PFMSM-PSHO.cnf + SM->>GTP: 11. SMGTP-CONTEXT-ACT.cnf + Note left of GTP: Forward Relocation Response + BSSGP->>External: PS-HANDOVER-COMPLETE_PDU + External-->>BSSGP: PS-HANDOVER-COMPLETE_PDU + BSSGP->>PFM: 12. PFM-PS-HANDOVER-COMPLETE.ind + PFM->>SM: 13. SMPFM-PSHO-COMPLETE.ind + SM->>GTP: 14. GTPSM-PSHO-COMPLETE.ind + Note left of GTP: Forward Relocation Complete +``` + +Sequence diagram showing primitives in New SGSN for Forward Relocation. Lifelines: GTP, SM, GMM, SNDPCP, PFM, LLC, BSSGP. The process involves context activation, PS handover request, and completion primitives between the network layers. + +## B.5 Primitives in Target BSS + +![Sequence diagram for Primitives in Target BSS showing interactions between BSSGP, PFM, and RR.](f7b2cf9e1b71dc4f900f3810646d3903_img.jpg) + +``` + +sequenceDiagram + participant BSSGP + participant PFM + participant RR + + Note left of BSSGP: PS-HANDOVER-REQUEST PDU + BSSGP->>PFM: 1. PFM-PS-HANDOVER-REQUEST.ind + PFM->>RR: 2. RRPFM-PSHO.req + RR-->>PFM: 3. RRPFM-PSHO.cnf + PFM-->>BSSGP: 4. PFM-PS-HANDOVER-REQUEST.res + Note left of BSSGP: PS-HANDOVER-REQUEST-ACK PDU + Note right of RR: RLC Data Block + RR-->>PFM: 5. PFMRR-PSHO-COMPLETE.ind + PFM-->>BSSGP: 6. PFM-PS-HANDOVER-COMPLETE.req + Note left of BSSGP: PS-HANDOVER-COMPLETE PDU + +``` + +Sequence diagram for Primitives in Target BSS showing interactions between BSSGP, PFM, and RR. + +## B.6 Primitives in MS + +![Sequence diagram for Primitives in MS showing interactions between GMM, SNDCP, LLC, SM, and RR.](a2bbc82e5c6132b0870bd70f6657f919_img.jpg) + +``` + +sequenceDiagram + participant GMM + participant SNDCP + participant LLC + participant SM + participant RR + + Note right of RR: PS Handover Command + Note over GMM, RR: After the MS has arrived in the new cell it considers the PS handover procedure to be successfully completed as a result of one of the following: +• The MS requires timing advance information and has received the Physical Information Message. +• The MS has sent the requested Handover Reference information and does not require timing advance information. +• The MS does not need to send Handover Reference information and does not require timing advance information. + RR->>SM: 1. GRR-PSHO-SUCCESS.ind + SM->>LLC: 2. LLGMM-PSHO.ind + LLC->>SNDCP: 3. LL-RESET.ind + SNDCP->>GMM: 4. GRR-UNITDATA.req + Note right of RR: RLC Data Blocks + +``` + +Sequence diagram for Primitives in MS showing interactions between GMM, SNDCP, LLC, SM, and RR. + +--- + +## Annex C (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-----|------------------------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2004-11 | 22 | GP-042904 | - | - | Version for Release 6 | - | 6.0.0 | +| 2005-01 | 23 | GP-050450 | 001 | 1 | Correction of data forwarding in case of inter-RAT PS Handover | 6.0.0 | 6.1.0 | +| 2005-01 | 23 | GP-050323 | 002 | | "Layer 3 information" not used for PS Handover | 6.0.0 | 6.1.0 | +| 2005-01 | 23 | GP-050603 | 004 | 2 | Clarification of PDP Context Suspension During Inter-SGSN GERAN A/Gb to GERAN A/Gb PS Handover | 6.0.0 | 6.1.0 | +| 2005-01 | 23 | GP-050326 | 005 | | PS Handover Cancel after failed PS Handover | 6.0.0 | 6.1.0 | +| 2005-01 | 23 | GP-050327 | 006 | | Addition of the SABM-UA exchange procedure | 6.0.0 | 6.1.0 | +| 2005-04 | 24 | GP-050894 | 009 | | Routing Area Update at every Inter-RAT PS Handover | 6.1.0 | 6.2.0 | +| 2005-04 | 24 | GP-051136 | 013 | 2 | Introduction of the PS Handover Complete message in the intra-BSS optimised scenario | 6.1.0 | 6.2.0 | +| 2005-04 | 24 | GP-050940 | 015 | 2 | Various Updates/Clarifications to TS43.129 | 6.1.0 | 6.2.0 | +| 2005-06 | 25 | GP-051687 | 011 | 4 | Simplification of PS Handover procedure | 6.2.0 | 6.3.0 | +| 2005-06 | 25 | GP-051689 | 012 | 2 | Suspension of DL Data Transfer | 6.2.0 | 6.3.0 | +| 2005-06 | 25 | GP-051558 | 019 | | Updates to TS 43.129 | 6.2.0 | 6.3.0 | +| 2005-06 | 25 | GP-051795 | 020 | 2 | Removal of NSAPI/SAPI/PFI mapping in inter-RAT/inter-mode PS Handover to GERAN A/Gb mode | 6.2.0 | 6.3.0 | +| 2005-09 | 26 | GP-052311 | 0017 | 3 | Clarification on the sending of PS Handover Access messages | 6.3.0 | 6.4.0 | +| 2005-09 | 26 | GP-052030 | 0022 | | Alignment of PDU names with TS 48.018 | 6.3.0 | 6.4.0 | +| 2005-09 | 26 | GP-052218 | 0023 | 1 | Annex for PS Handover Primitives | 6.3.0 | 6.4.0 | +| 2005-09 | 26 | GP-052033 | 0024 | | Clarification of CN part and RN part | 6.3.0 | 6.4.0 | +| 2005-09 | 26 | GP-052221 | 0025 | 1 | Corrections to Forward SRNS Context procedures | 6.3.0 | 6.4.0 | +| 2005-11 | 27 | GP-052543 | 0008 | 4 | Transferring of UE RAC and START PS from the MS to the BSC | 6.4.0 | 6.5.0 | +| 2005-11 | 27 | GP-052541 | 0026 | | Removal of FFSe related to NAS container | 6.4.0 | 6.5.0 | +| 2005-11 | 27 | GP-052542 | 0027 | | Security clean-up | 6.4.0 | 6.5.0 | +| 2005-11 | 27 | GP-052800 | 0028 | 1 | Various corrections to TS 43.129 | 6.4.0 | 6.5.0 | +| 2005-11 | 27 | GP-052799 | 0029 | 1 | Corrections of Source RNC to Target RNC container | 6.4.0 | 6.5.0 | +| 2006-01 | 28 | GP-060226 | 0031 | | Various updates to TS 43.129 | 6.5.0 | 6.6.0 | +| 2006-01 | 28 | GP-060420 | 0033 | 2 | User-Plane Data Forwarding for Inter-RAT PS Handover | 6.5.0 | 6.6.0 | +| 2006-01 | 28 | GP-060342 | 0034 | 1 | Condition for UL data transfer | 6.5.0 | 6.6.0 | +| 2006-01 | 28 | GP-060459 | 0036 | 2 | Correction of XID negotiation | 6.5.0 | 6.6.0 | +| 2006-04 | 29 | GP-060938 | 0037 | 2 | Various editorial updates to PS Handover procedures | 6.6.0 | 6.7.0 | +| 2006-04 | 29 | GP-060828 | 0038 | 1 | Various updates | 6.6.0 | 6.7.0 | +| 2006-04 | 29 | GP-060742 | 0039 | | Various corrections | 6.6.0 | 6.7.0 | +| 2006-05 | | | | | Make figures editable | 6.7.0 | 6.7.1 | +| 2006-06 | 30 | GP-061350 | 0040 | 1 | Behaviour in case of failed Update PDP Context procedure | 6.7.1 | 6.8.0 | +| 2006-06 | 30 | GP-061258 | 0041 | | Behaviour in case of missing XID parameters | 6.7.1 | 6.8.0 | +| 2006-09 | 31 | GP-061871 | 0044 | 2 | Resource release during PS handover when no response from mobile station | 6.8.0 | 6.9.0 | +| 2006-11 | 32 | GP-062114 | 0043 | 4 | Introduction of CAMEL Trigger Points | 6.9.0 | 6.10.0 | +| 2006-11 | 32 | GP-062115 | 0047 | | Various updates to TS 43.129 | 6.9.0 | 6.10.0 | +| 2006-11 | 32 | GP-062365 | 0048 | 1 | Clarification of PS Handover Cancel behaviour | 6.9.0 | 6.10.0 | +| 2006-11 | 32 | GP-062415 | 0049 | 1 | Improved behaviour in case of inactive PFCs/RABs | 6.9.0 | 6.10.0 | +| 2006-11 | 32 | GP-062190 | 0050 | | Definition of Lost MS | 6.9.0 | 6.10.0 | +| 2006-11 | 32 | GP-062418 | 0051 | 2 | Non-critical PS handover reject | 6.9.0 | 6.10.0 | +| 2006-11 | 32 | GP-062373 | 0053 | 1 | Clarification on the PS HO execution phase | 6.9.0 | 6.10.0 | +| 2006-11 | 32 | GP-062470 | 0046 | 4 | PS Handover Support for GAN | 6.10.0 | 7.0.0 | +| 2007-02 | 33 | GP-070427 | 0057 | 1 | Various updates on PS Handover | 7.0.0 | 7.1.0 | +| 2007-02 | 33 | GP-070260 | 0058 | | Usage of Activity Status Indicator | 7.0.0 | 7.1.0 | +| 2007-02 | 33 | GP-070340 | 0061 | | Correction of conditions for PS handover reject | 7.0.0 | 7.1.0 | +| 2007-05 | 34 | GP-071021 | 0059 | 5 | Direct Tunnel Functionality | 7.1.0 | 7.2.0 | +| 2007-05 | 34 | GP-070714 | 0065 | | Erroneous implementation of CR 0033 to TS 43.129 | 7.1.0 | 7.2.0 | +| 2008-08 | 39 | GP-081350 | 0068 | 3 | Introduction of inter-RAT PS handover between GERAN and E-UTRAN | 7.2.0 | 8.0.0 | +| 2009-02 | 41 | GP-090177 | 0070 | | Introduction of generic transparent containers for inter-RAT PS handover | 8.0.0 | 8.1.0 | +| 2009-11 | 44 | GP-092331 | 0072 | 3 | Introduction of PS Handover Complete Acknowledge Message | 8.1.0 | 8.2.0 | + +| | | | | | | | | +|---------|----|-----------|------|---|-------------------------------------------------------------|--------|--------| +| 2009-12 | 44 | | | | Version for Release 9 | 8.2.0 | 9.0.0 | +| 2010-05 | 46 | GP-100818 | 0078 | 2 | Introduction of PS handover to CSG cells | 9.0.0 | 9.1.0 | +| 2011-03 | 49 | | | | Version for Release 10 | 9.1.0 | 10.0.0 | +| 2012-03 | 53 | GP-120428 | 0079 | 1 | Correction to the Target to Source Transparent Container | 10.0.0 | 10.1.0 | +| 2012-09 | 55 | | | | Version for Release 11 | 10.1.0 | 11.0.0 | +| 2013-11 | 60 | GP-131099 | 0082 | 2 | Request for E-UTRAN inter RAT handover information disabled | 11.0.0 | 11.1.0 | \ No newline at end of file diff --git a/marked/Rel-11/43_series/43318/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg b/marked/Rel-11/43_series/43318/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..352bcb5189affeede644b35ed77b0232d3d84059 --- /dev/null +++ b/marked/Rel-11/43_series/43318/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc3713410eec61609998a50f61639eb88e33ce94adc696d233af5ca1e5fb5930 +size 19460 diff --git a/marked/Rel-11/43_series/43318/06291c5328a7a4335d41a48850a3a207_img.jpg b/marked/Rel-11/43_series/43318/06291c5328a7a4335d41a48850a3a207_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d550d1f1a4026dfc37de3720f267d9b0dac563cc --- /dev/null +++ b/marked/Rel-11/43_series/43318/06291c5328a7a4335d41a48850a3a207_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:492bad3aa6d1bd46d4da48063102583eaa858e8cdbed4ed97c77e20e21520f82 +size 28816 diff --git a/marked/Rel-11/43_series/43318/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg b/marked/Rel-11/43_series/43318/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7000c1af8661181cd92621b871cf13f4df5ca674 --- /dev/null +++ b/marked/Rel-11/43_series/43318/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e1823a078f88db5eeb0eb0d4b7132eadad3d8140f30f5dae7f09d3683c6e1a3 +size 61313 diff --git a/marked/Rel-11/43_series/43318/1018d0db7bb02c169f646cb9cc244dc6_img.jpg b/marked/Rel-11/43_series/43318/1018d0db7bb02c169f646cb9cc244dc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ef54c2a76d548d4b9a058785fb664aa75bba063 --- /dev/null +++ b/marked/Rel-11/43_series/43318/1018d0db7bb02c169f646cb9cc244dc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a8822e079dcca6bffe4c2420a1d6b7816f0764c89eb462245e207a3ba62bf7d0 +size 16114 diff --git a/marked/Rel-11/43_series/43318/10cc1e74f2b71404f021bb8b3cec0ff0_img.jpg b/marked/Rel-11/43_series/43318/10cc1e74f2b71404f021bb8b3cec0ff0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82fd73b2fdc9dc107fd8c1f694652cb95f4ed1de --- /dev/null +++ b/marked/Rel-11/43_series/43318/10cc1e74f2b71404f021bb8b3cec0ff0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:136a5723416aa6d08a34e85cffe955bd3d347daa668c634ce5790624183576f8 +size 27899 diff --git a/marked/Rel-11/43_series/43318/11f18bf0233d812ad2604f88f3385d60_img.jpg b/marked/Rel-11/43_series/43318/11f18bf0233d812ad2604f88f3385d60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e5ecb12d443f4d8ef209b9d38511d05fa95574c --- /dev/null +++ b/marked/Rel-11/43_series/43318/11f18bf0233d812ad2604f88f3385d60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70398b8faa1c6f59f4c279005e39da8973bb48bb8a278295e9b70923469c39bf +size 94808 diff --git a/marked/Rel-11/43_series/43318/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg b/marked/Rel-11/43_series/43318/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2baed1b573f58f3ff06749e5b96ca3619847dfed --- /dev/null +++ b/marked/Rel-11/43_series/43318/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ba4401b8f48396566454948013c9f992234c9981a47287fbf322ed9cfcda7f3 +size 61848 diff --git a/marked/Rel-11/43_series/43318/18003425d0e8638dde4acc9c5c468c5c_img.jpg b/marked/Rel-11/43_series/43318/18003425d0e8638dde4acc9c5c468c5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8fdac509b42f6f44f22ab3663e3d2e7c9eb551a --- /dev/null +++ b/marked/Rel-11/43_series/43318/18003425d0e8638dde4acc9c5c468c5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18abdfa14f7ff5ab9d94eb9b03bd7cd57eb0bd0a650eafeb84d92ab791e8f208 +size 81188 diff --git a/marked/Rel-11/43_series/43318/1c79f31a718d63814feb28ab46f64f19_img.jpg b/marked/Rel-11/43_series/43318/1c79f31a718d63814feb28ab46f64f19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8b206a1d8d0d047d9025a213b271c3835b71a10 --- /dev/null +++ b/marked/Rel-11/43_series/43318/1c79f31a718d63814feb28ab46f64f19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba9c1012323e1b61630bc14bca698fe63393ba5ccce2c38c98d7526f927a231f +size 105476 diff --git a/marked/Rel-11/43_series/43318/20cb2d2cc18d663dc1b82453c67250bb_img.jpg b/marked/Rel-11/43_series/43318/20cb2d2cc18d663dc1b82453c67250bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b3ae7bbd9500bc28dea3378da724609a3b4d22f --- /dev/null +++ b/marked/Rel-11/43_series/43318/20cb2d2cc18d663dc1b82453c67250bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4aea736a9961defc2951376fdb532eadcc72d4348ff87572dc4b6a45b5a8bc2a +size 24871 diff --git a/marked/Rel-11/43_series/43318/22bc7139d3987c61ddefffa08036a923_img.jpg b/marked/Rel-11/43_series/43318/22bc7139d3987c61ddefffa08036a923_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c76f1471ddc1a7ef6e5ca17862d91cf14ef04b7 --- /dev/null +++ b/marked/Rel-11/43_series/43318/22bc7139d3987c61ddefffa08036a923_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37d7891d7efcbe0453051ed5b0572a62ac12bade51f1b5e73741a990905e61ee +size 23335 diff --git a/marked/Rel-11/43_series/43318/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg b/marked/Rel-11/43_series/43318/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d737d52b659e2899896a3c05b40baa51f192fecc --- /dev/null +++ b/marked/Rel-11/43_series/43318/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e260e305194dcb960fa56aa4e809b8211b115ab1dd3d2265896e88a5b037054c +size 68830 diff --git a/marked/Rel-11/43_series/43318/28085f681b9fff76a53c5b8b32338ee1_img.jpg b/marked/Rel-11/43_series/43318/28085f681b9fff76a53c5b8b32338ee1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3198c4854672d0a14b11215da1f22d12442864d8 --- /dev/null +++ b/marked/Rel-11/43_series/43318/28085f681b9fff76a53c5b8b32338ee1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df83e4fe73c18ed935d2293aa762bcfc684a51861ab49aef5ebd14ae2f51c88d +size 97545 diff --git a/marked/Rel-11/43_series/43318/28f2f470a7b2446ae5f525123534383c_img.jpg b/marked/Rel-11/43_series/43318/28f2f470a7b2446ae5f525123534383c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aaebd3d5d2aafa70c7ea243d96213d3135f1408e --- /dev/null +++ b/marked/Rel-11/43_series/43318/28f2f470a7b2446ae5f525123534383c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1066abb8e25247581b2eb69409ef276993d928c3f7e49c17c4aef617143f0a81 +size 103746 diff --git a/marked/Rel-11/43_series/43318/29f586959675cafdf81cf934954908eb_img.jpg b/marked/Rel-11/43_series/43318/29f586959675cafdf81cf934954908eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b219830edbd049bfb27c018f5e039041188c725f --- /dev/null +++ b/marked/Rel-11/43_series/43318/29f586959675cafdf81cf934954908eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:317a649244bc281d8af4f6f3c9bac4e6d0918de8c46ecdc3cf2620e878235588 +size 83540 diff --git a/marked/Rel-11/43_series/43318/2aa94b70ba3fadcba8420d9e3128253a_img.jpg b/marked/Rel-11/43_series/43318/2aa94b70ba3fadcba8420d9e3128253a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..902db3824ded98654ba8261abeceb3ec26c56723 --- /dev/null +++ b/marked/Rel-11/43_series/43318/2aa94b70ba3fadcba8420d9e3128253a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67263c7bd5a403593a1c3eda210de778da18f7310600fe6a0683463e11b012de +size 145822 diff --git a/marked/Rel-11/43_series/43318/2b00743506f6a3bbd17af764162dc76d_img.jpg b/marked/Rel-11/43_series/43318/2b00743506f6a3bbd17af764162dc76d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04bd433ad85381efb2707d0b97cb187e0f303ef9 --- /dev/null +++ b/marked/Rel-11/43_series/43318/2b00743506f6a3bbd17af764162dc76d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67a46495be51fb98ffc27c63652fa871db213af392d6b88b89083c31b722bc95 +size 112047 diff --git a/marked/Rel-11/43_series/43318/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-11/43_series/43318/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a519dd986fb64e30623653acf5557d07b661d4b --- /dev/null +++ b/marked/Rel-11/43_series/43318/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4a398c60a860c7d4dcb7b54953cf7961927443b14a88b31d3855df4a9e60726 +size 81146 diff --git a/marked/Rel-11/43_series/43318/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-11/43_series/43318/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93b461ffbbc78547aaad31725908653d01961e66 --- /dev/null +++ b/marked/Rel-11/43_series/43318/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d4e76d2690982a218f6a3c0147607dcfc087b6fc8079107fc05bfbbce6d9256 +size 86829 diff --git a/marked/Rel-11/43_series/43318/3750b0149a6380885998ab3ca6a8787c_img.jpg b/marked/Rel-11/43_series/43318/3750b0149a6380885998ab3ca6a8787c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cede7e163a421c59e557ca1176bf7551cd577c11 --- /dev/null +++ b/marked/Rel-11/43_series/43318/3750b0149a6380885998ab3ca6a8787c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:25152e1ef415c56e75961cdc4ac6239b26c57d5f0119241d8af844108f3d6aea +size 98209 diff --git a/marked/Rel-11/43_series/43318/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg b/marked/Rel-11/43_series/43318/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c00dbaefaf6fb1d8cb7ffa9baca799c4bef439a8 --- /dev/null +++ b/marked/Rel-11/43_series/43318/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e6db9b311979f9ce8f89e2888d797a62eb9ecfd43aecdb3d3337c613fcf76b1 +size 70694 diff --git a/marked/Rel-11/43_series/43318/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg b/marked/Rel-11/43_series/43318/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..825d06b2a4cd1c62a42f7bdbf255dee81fed0a29 --- /dev/null +++ b/marked/Rel-11/43_series/43318/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d40a09bf04801d6627bd08409fdb521b5b8f8247d4c89066356448d14c49394a +size 158093 diff --git a/marked/Rel-11/43_series/43318/48f209b7c0c1f91af40cfc3466dbd534_img.jpg b/marked/Rel-11/43_series/43318/48f209b7c0c1f91af40cfc3466dbd534_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51e1d27dc5fa1a9c9c90dfd8ffcb8bc303e8ddb1 --- /dev/null +++ b/marked/Rel-11/43_series/43318/48f209b7c0c1f91af40cfc3466dbd534_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:233b380aa458196a1084fcde6cf349b2ffb668e1a286ac98847f82ca7c2c22cd +size 11384 diff --git a/marked/Rel-11/43_series/43318/49806c5ac206335a657bc126f17d37e8_img.jpg b/marked/Rel-11/43_series/43318/49806c5ac206335a657bc126f17d37e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3868924df125996a99485e16da6482374464424b --- /dev/null +++ b/marked/Rel-11/43_series/43318/49806c5ac206335a657bc126f17d37e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc900fd3c2fc173641ee65588a33fd9f78533c153decbacf5bcac01d5cd4cc43 +size 65197 diff --git a/marked/Rel-11/43_series/43318/50214d232017279410e9c9db8eb75119_img.jpg b/marked/Rel-11/43_series/43318/50214d232017279410e9c9db8eb75119_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11c525ad996c0a5daaff5a450b2d6d4cca806441 --- /dev/null +++ b/marked/Rel-11/43_series/43318/50214d232017279410e9c9db8eb75119_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8cbc5570b16797aa8349cc1928115638a791eaccda18c27556b5f4fdd055ab22 +size 81593 diff --git a/marked/Rel-11/43_series/43318/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg b/marked/Rel-11/43_series/43318/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..304fa5d1c12745d05b1edb59849149a8ba1410b4 --- /dev/null +++ b/marked/Rel-11/43_series/43318/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8af11eff1fcdbea78aed470d5486e2f380a2e46e4c3f880f020098c7f1159512 +size 92955 diff --git a/marked/Rel-11/43_series/43318/53001b5ae3f65139f78db410bb41ae30_img.jpg b/marked/Rel-11/43_series/43318/53001b5ae3f65139f78db410bb41ae30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..176cf06027165c8b67788be6cb4e389be943c2b7 --- /dev/null +++ b/marked/Rel-11/43_series/43318/53001b5ae3f65139f78db410bb41ae30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae7ffaf6eaa0516db50fa5547f6b96374081eead2dc4e83468d5a358e6b18abb +size 37523 diff --git a/marked/Rel-11/43_series/43318/552328a9daaf3bc0069424b500025880_img.jpg b/marked/Rel-11/43_series/43318/552328a9daaf3bc0069424b500025880_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20f501aeee06de5ff1093ca952e5a46cff283623 --- /dev/null +++ b/marked/Rel-11/43_series/43318/552328a9daaf3bc0069424b500025880_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:753993f33f9d02be75097fa63aec9a86073c64a2a6bb4080da7d63e00a21bf07 +size 43221 diff --git a/marked/Rel-11/43_series/43318/575d7d345b3ec04393bb2ec720ebabca_img.jpg b/marked/Rel-11/43_series/43318/575d7d345b3ec04393bb2ec720ebabca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..101412cc15e06a30b4be7402728c5c2e2b445e8f --- /dev/null +++ b/marked/Rel-11/43_series/43318/575d7d345b3ec04393bb2ec720ebabca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d69857a54bea193e466ace4c6b2ec1f9047f3e9a56bd0128af8bc156da02979 +size 52299 diff --git a/marked/Rel-11/43_series/43318/57939c16065211317c5442cf2a4009e0_img.jpg b/marked/Rel-11/43_series/43318/57939c16065211317c5442cf2a4009e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..040e0341c86f446563cc892711566e272afd4ac0 --- /dev/null +++ b/marked/Rel-11/43_series/43318/57939c16065211317c5442cf2a4009e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4da3ebc8cc65684cd1c067f611a24c1283812c14a86befd249f307c728b2253 +size 22984 diff --git a/marked/Rel-11/43_series/43318/5801c19431e76330430e92a598cc7a16_img.jpg b/marked/Rel-11/43_series/43318/5801c19431e76330430e92a598cc7a16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ec935aa8329aa76fc64954bc6271421f0dfdcda --- /dev/null +++ b/marked/Rel-11/43_series/43318/5801c19431e76330430e92a598cc7a16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6f9d1257badce67c4eadddd52c1cec1280355a2d8ae58c4c9cd148482c0c81f +size 20625 diff --git a/marked/Rel-11/43_series/43318/5a01395925fc88802da68fb5ac0f31ff_img.jpg b/marked/Rel-11/43_series/43318/5a01395925fc88802da68fb5ac0f31ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a6e2353b0a4f75ceb2efe6969dd90172937115b --- /dev/null +++ b/marked/Rel-11/43_series/43318/5a01395925fc88802da68fb5ac0f31ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e81cfd91429e3209426964c484d279209522dbf8dde98e37d24be4a8c6a190fd +size 35231 diff --git a/marked/Rel-11/43_series/43318/5e3888db7cda1becbce099b7304a44fa_img.jpg b/marked/Rel-11/43_series/43318/5e3888db7cda1becbce099b7304a44fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7de8590062ba38ff05fada88a3b7304d987ee2c9 --- /dev/null +++ b/marked/Rel-11/43_series/43318/5e3888db7cda1becbce099b7304a44fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14798b75b72e8802aba3c6593ad83fc286536bdd53bbdc09630d8f5be7671a6f +size 39306 diff --git a/marked/Rel-11/43_series/43318/64544fbada794f3cdf4f78f5d83613e4_img.jpg b/marked/Rel-11/43_series/43318/64544fbada794f3cdf4f78f5d83613e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0da85a098d912d1c5f9fb17bf08025e668224489 --- /dev/null +++ b/marked/Rel-11/43_series/43318/64544fbada794f3cdf4f78f5d83613e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc3c0a81f1c50a08e19feadebfdb5099e982a8abbeba040dfca2fa9c5304ef82 +size 21391 diff --git a/marked/Rel-11/43_series/43318/64bec4cd45e47e1976245711f702aca2_img.jpg b/marked/Rel-11/43_series/43318/64bec4cd45e47e1976245711f702aca2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..751c75f1bdcad7570a8a3e06aa7b9d6a2a1b5b6f --- /dev/null +++ b/marked/Rel-11/43_series/43318/64bec4cd45e47e1976245711f702aca2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5026ae3170ecba376365424ae3e4e7997809f5df7985783a862027507586a79 +size 49938 diff --git a/marked/Rel-11/43_series/43318/64cda8ce20067bc360ce2f3a5c9352b7_img.jpg b/marked/Rel-11/43_series/43318/64cda8ce20067bc360ce2f3a5c9352b7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f98c6b00be20f1024e70ed920f3f50d57ecf8085 --- /dev/null +++ b/marked/Rel-11/43_series/43318/64cda8ce20067bc360ce2f3a5c9352b7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da9a459b375942ea518cb864a2534975495548834e430d9bc1ec00976ad639cc +size 91776 diff --git a/marked/Rel-11/43_series/43318/659a041a7997f9eea79f4e2f3ba265a5_img.jpg b/marked/Rel-11/43_series/43318/659a041a7997f9eea79f4e2f3ba265a5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa03a8576158c7481ef7194c9a91ade084fce7b7 --- /dev/null +++ b/marked/Rel-11/43_series/43318/659a041a7997f9eea79f4e2f3ba265a5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e5d95c07d4211bce59e583008505f12bbfa9897e694fc1f20ee469ed823e71e +size 10553 diff --git a/marked/Rel-11/43_series/43318/683f755e8456c884716de4fce48c7e63_img.jpg b/marked/Rel-11/43_series/43318/683f755e8456c884716de4fce48c7e63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ef4bc051dea92855c93909c8af01234fe0efb0f --- /dev/null +++ b/marked/Rel-11/43_series/43318/683f755e8456c884716de4fce48c7e63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7708d25af6b7017cc9210daf17147c1e03b43d55440d56c38f342eb87df755f9 +size 12630 diff --git a/marked/Rel-11/43_series/43318/69467ece0a576b4c2ec3e0c89ba61527_img.jpg b/marked/Rel-11/43_series/43318/69467ece0a576b4c2ec3e0c89ba61527_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..082a5845e1ce48ace4c97e1c2a4356721575cef9 --- /dev/null +++ b/marked/Rel-11/43_series/43318/69467ece0a576b4c2ec3e0c89ba61527_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:384c159ffbe5b90c4debb9fdc301934fad188422761d4662b16d838071e22288 +size 38237 diff --git a/marked/Rel-11/43_series/43318/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg b/marked/Rel-11/43_series/43318/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09fa3174b6c7973656708c5f8f9f01cea2190fcc --- /dev/null +++ b/marked/Rel-11/43_series/43318/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2764afa65895e4b6bcb85f2fa74ac61ffae6314294c22c421f2576c1f8539bdd +size 24266 diff --git a/marked/Rel-11/43_series/43318/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-11/43_series/43318/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58e29562ef99b91397852a295d863b327c52af7f --- /dev/null +++ b/marked/Rel-11/43_series/43318/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5fdc4104c28f637fa6cac80168afca7e04a9472467fda01dc50c4ed5e01e8516 +size 43786 diff --git a/marked/Rel-11/43_series/43318/719ef0f734259484038b2434e5dc3f24_img.jpg b/marked/Rel-11/43_series/43318/719ef0f734259484038b2434e5dc3f24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4ae0437817da18f0b9769c759a25b913672d93b --- /dev/null +++ b/marked/Rel-11/43_series/43318/719ef0f734259484038b2434e5dc3f24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c08469514072774c54022b1f1fbdacbc400f01f8217472ee007387d35acfd5f +size 15840 diff --git a/marked/Rel-11/43_series/43318/737abf1e655afd3324b6b3987945d913_img.jpg b/marked/Rel-11/43_series/43318/737abf1e655afd3324b6b3987945d913_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0b585b251fd1ba4081b446044aceaf26e0551a6 --- /dev/null +++ b/marked/Rel-11/43_series/43318/737abf1e655afd3324b6b3987945d913_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4786795dbcfd0868cf024c8a48fd813be246a5d4b1e9c582b5e4bced6c5460a0 +size 66981 diff --git a/marked/Rel-11/43_series/43318/759c7d62402f0b4651ddce292be5bdef_img.jpg b/marked/Rel-11/43_series/43318/759c7d62402f0b4651ddce292be5bdef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eba3d065389703e4d6b980f12b6c95aedd76bc05 --- /dev/null +++ b/marked/Rel-11/43_series/43318/759c7d62402f0b4651ddce292be5bdef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f83a20343d71221c4b272e9342f5a517857430cb0a55416f3d15068c833119c +size 56239 diff --git a/marked/Rel-11/43_series/43318/76d19e4271bf243b20d55a98efd51483_img.jpg b/marked/Rel-11/43_series/43318/76d19e4271bf243b20d55a98efd51483_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..460a327140384bc6bedd0b238899e1d65407b23a --- /dev/null +++ b/marked/Rel-11/43_series/43318/76d19e4271bf243b20d55a98efd51483_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32aa062155c6a1269f6914731ef53858a4ab350c284bc9231d501c928148e375 +size 41482 diff --git a/marked/Rel-11/43_series/43318/7722d62e33dcc894cc8555e9474c5606_img.jpg b/marked/Rel-11/43_series/43318/7722d62e33dcc894cc8555e9474c5606_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..149b5277f4ac33f0132391cf07ac127ed9b08933 --- /dev/null +++ b/marked/Rel-11/43_series/43318/7722d62e33dcc894cc8555e9474c5606_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:76550368d12f8af19d9a5349ed73188627351190ef9bd10b5aea39d4fc673913 +size 41752 diff --git a/marked/Rel-11/43_series/43318/7d2d1d3870cd224c4430d19334557716_img.jpg b/marked/Rel-11/43_series/43318/7d2d1d3870cd224c4430d19334557716_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e98ec422c675e8c9ac5cf9cf6420d3b8eebb70ae --- /dev/null +++ b/marked/Rel-11/43_series/43318/7d2d1d3870cd224c4430d19334557716_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98d924f616f7bfd8e1c702e5855745bc366951c0cba3a6ff4ffd88858256467d +size 42780 diff --git a/marked/Rel-11/43_series/43318/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg b/marked/Rel-11/43_series/43318/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aba7712042f0ae4d4c8bc7b86b1f539faa6ab1f2 --- /dev/null +++ b/marked/Rel-11/43_series/43318/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:209950a705aae5a13ab6faf19e25da11ae95c89b750016695f1971751c238348 +size 62182 diff --git a/marked/Rel-11/43_series/43318/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg b/marked/Rel-11/43_series/43318/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..794ec2e6a56043d1fc42fa3862b1ddf671b88cf4 --- /dev/null +++ b/marked/Rel-11/43_series/43318/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9bf5abd87f85424022f9336eb9f7b93e3584bdc886d245f40d47d2bc7602c079 +size 54197 diff --git a/marked/Rel-11/43_series/43318/7f16ae750ce9a533b0bd301dd986355e_img.jpg b/marked/Rel-11/43_series/43318/7f16ae750ce9a533b0bd301dd986355e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..820ac0bedab0c56b40b322d7ed17e9368925d695 --- /dev/null +++ b/marked/Rel-11/43_series/43318/7f16ae750ce9a533b0bd301dd986355e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b45c4dee490f48adcc12367110352c8b7ac277f6c85d7baaa49820bae5b3dc83 +size 35544 diff --git a/marked/Rel-11/43_series/43318/7f663b2f8632236c6e40ca16272d62df_img.jpg b/marked/Rel-11/43_series/43318/7f663b2f8632236c6e40ca16272d62df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19d1ea5de021e435eaa5f568ea7de811c1e79df1 --- /dev/null +++ b/marked/Rel-11/43_series/43318/7f663b2f8632236c6e40ca16272d62df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:287074ab98afb5cb06f0fd3aef165cc69d7d29fede120c6d2d6e32e97cff25bd +size 16814 diff --git a/marked/Rel-11/43_series/43318/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg b/marked/Rel-11/43_series/43318/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a96dcef7456bda01e102742df45ed9a7e88a267d --- /dev/null +++ b/marked/Rel-11/43_series/43318/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19398c145d151cd721885338b8e1e1082395b4816ea3ee8bf752fe26679e813b +size 55469 diff --git a/marked/Rel-11/43_series/43318/86b4670fc1a5a694821ee92b99c1209a_img.jpg b/marked/Rel-11/43_series/43318/86b4670fc1a5a694821ee92b99c1209a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5752280f14e2272f0ff84de0fd34bfd7f6492c68 --- /dev/null +++ b/marked/Rel-11/43_series/43318/86b4670fc1a5a694821ee92b99c1209a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c0a67cc37db9579157b96728e41a5299a21b086e26c72d4fd44fd7f21694d3f +size 75709 diff --git a/marked/Rel-11/43_series/43318/8f8caebe58364416a2eda21039d8c7bf_img.jpg b/marked/Rel-11/43_series/43318/8f8caebe58364416a2eda21039d8c7bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f98b6111ef722354104dd24d3bc0efed7776ce18 --- /dev/null +++ b/marked/Rel-11/43_series/43318/8f8caebe58364416a2eda21039d8c7bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd4dc4869c6cfd709997af6a1655f2804049c40f99a8dc6ba3aefe80c63403dd +size 90027 diff --git a/marked/Rel-11/43_series/43318/901800172164e0494762ffa57a09993f_img.jpg b/marked/Rel-11/43_series/43318/901800172164e0494762ffa57a09993f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b13a168a7201e780089f32d2b892f0c8de0e4369 --- /dev/null +++ b/marked/Rel-11/43_series/43318/901800172164e0494762ffa57a09993f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa7076b509a02863b5d109fcae3689a4673d555106a1bddeb800b150fc16b7f4 +size 27907 diff --git a/marked/Rel-11/43_series/43318/921458d4fc1b778c2450592ac9745b48_img.jpg b/marked/Rel-11/43_series/43318/921458d4fc1b778c2450592ac9745b48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53dfe2fcf917c8e44d3d5006231faf3d75c5a4d2 --- /dev/null +++ b/marked/Rel-11/43_series/43318/921458d4fc1b778c2450592ac9745b48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea7c554ffb16fc6a7dcbb1acac8ead4a23d2d2bee49211a6664c41419f6e797b +size 59995 diff --git a/marked/Rel-11/43_series/43318/981668c6be5792b778cccb1af38477e2_img.jpg b/marked/Rel-11/43_series/43318/981668c6be5792b778cccb1af38477e2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3b7737d1aea44eecac1194ba9f0e95614f745d04 --- /dev/null +++ b/marked/Rel-11/43_series/43318/981668c6be5792b778cccb1af38477e2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cca8633dfe830b0adcd27a17f74499cfec5b62cce571957570976441ea3aa3ba +size 20357 diff --git a/marked/Rel-11/43_series/43318/98d9a07b2cfa04ebea4e5a4b556d184a_img.jpg b/marked/Rel-11/43_series/43318/98d9a07b2cfa04ebea4e5a4b556d184a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3723945e107e5f31d83bc4a5867d647800c04250 --- /dev/null +++ b/marked/Rel-11/43_series/43318/98d9a07b2cfa04ebea4e5a4b556d184a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87e8ffe57bfcce46e41c66bd3b30c735c0c4f3e710a7adc760ec6eed8b4129d3 +size 52577 diff --git a/marked/Rel-11/43_series/43318/99a0eddf16e836f411661acee6facd17_img.jpg b/marked/Rel-11/43_series/43318/99a0eddf16e836f411661acee6facd17_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be3a008a70093dab14975f3dbd0b88d663a4b8c8 --- /dev/null +++ b/marked/Rel-11/43_series/43318/99a0eddf16e836f411661acee6facd17_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a2ca569b2aae508885195d43a3a17726dd585eb005b8e94a100a77b92f37950 +size 140777 diff --git a/marked/Rel-11/43_series/43318/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg b/marked/Rel-11/43_series/43318/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8ae86bcb73fdcfadfe450cd12a03739ae0237c3 --- /dev/null +++ b/marked/Rel-11/43_series/43318/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21d89140e5e34c168525f188ff181f1da66c9d18616181eae922ae0188e5f81e +size 62473 diff --git a/marked/Rel-11/43_series/43318/9c05ae298f897f405d4f0c72d98cb2c7_img.jpg b/marked/Rel-11/43_series/43318/9c05ae298f897f405d4f0c72d98cb2c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e3191021ff867679e4d94642ae3347af1abf5551 --- /dev/null +++ b/marked/Rel-11/43_series/43318/9c05ae298f897f405d4f0c72d98cb2c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49b96c9849127769f86767ccfa7f53af6e4b04177f146dde4331cc6aab308b93 +size 21034 diff --git a/marked/Rel-11/43_series/43318/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg b/marked/Rel-11/43_series/43318/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2745f9d0f14f0002c80da8890900be92c9cb68cf --- /dev/null +++ b/marked/Rel-11/43_series/43318/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d66b3207318c801a45723ecee835d93750fe1b3fd91059df8a24574eedb7e092 +size 90827 diff --git a/marked/Rel-11/43_series/43318/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/Rel-11/43_series/43318/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a73d39be3e90a6fb895c84191e743793c13d3c4b --- /dev/null +++ b/marked/Rel-11/43_series/43318/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8098ff413841779925204108a6ba4c8ed5a05bf8c8190bf2db7c72dcf811f3c +size 12379 diff --git a/marked/Rel-11/43_series/43318/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg b/marked/Rel-11/43_series/43318/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1bbe776606ec8615147ddf711d73b5330189c56a --- /dev/null +++ b/marked/Rel-11/43_series/43318/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38e5b8b629dae34b3d99371da8a0bbb6098a8c771cba8a6f7fa83b16f232eb11 +size 78161 diff --git a/marked/Rel-11/43_series/43318/a3c1310e720178d2450a3748c7c75422_img.jpg b/marked/Rel-11/43_series/43318/a3c1310e720178d2450a3748c7c75422_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5554d371a48ea9c2ea2fb15d991e8e49195794a8 --- /dev/null +++ b/marked/Rel-11/43_series/43318/a3c1310e720178d2450a3748c7c75422_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2b7de95fb17cd50c1456de03d331ea29a2a21f5b99128866457f47bd3bdc3d4 +size 27519 diff --git a/marked/Rel-11/43_series/43318/a66383962afcd0f0458f0d45c101fabf_img.jpg b/marked/Rel-11/43_series/43318/a66383962afcd0f0458f0d45c101fabf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bbceb3459f050f5e723b5f76613bdd02e174f518 --- /dev/null +++ b/marked/Rel-11/43_series/43318/a66383962afcd0f0458f0d45c101fabf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60f18bb4221b8d52ab015322b39ed75bdecc760bb8056abade7a2b4d283b3427 +size 61731 diff --git a/marked/Rel-11/43_series/43318/a734898ce18e972938949637c32a34f4_img.jpg b/marked/Rel-11/43_series/43318/a734898ce18e972938949637c32a34f4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..773b3b4fefaea6442b4b6839547d0d39d70a4818 --- /dev/null +++ b/marked/Rel-11/43_series/43318/a734898ce18e972938949637c32a34f4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:142babcf4e38bc99abe6f4beee8c241bd97f3855149e5b2fd92b62ef92029029 +size 64667 diff --git a/marked/Rel-11/43_series/43318/a963ca41bde1669b18a4b783616f228b_img.jpg b/marked/Rel-11/43_series/43318/a963ca41bde1669b18a4b783616f228b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..daa712aaa6bf2fa4ce0a2d7fe6da4afdcd7c618c --- /dev/null +++ b/marked/Rel-11/43_series/43318/a963ca41bde1669b18a4b783616f228b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7415859abd2b4433065d946d4dd7bb26101986ee17de652920c55814cc346e8 +size 49025 diff --git a/marked/Rel-11/43_series/43318/ada2aa7cce9cff9cf116d9ae2b8b7c27_img.jpg b/marked/Rel-11/43_series/43318/ada2aa7cce9cff9cf116d9ae2b8b7c27_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c71a914bc2734c65314da2fe2f6bd41670e47f04 --- /dev/null +++ b/marked/Rel-11/43_series/43318/ada2aa7cce9cff9cf116d9ae2b8b7c27_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ea14417638a2420df32352d1a311e15ec4441c839130af8fe8a7dd73f0ae2d5 +size 28721 diff --git a/marked/Rel-11/43_series/43318/b44f89b176c971c7dd264c07bfef2c2a_img.jpg b/marked/Rel-11/43_series/43318/b44f89b176c971c7dd264c07bfef2c2a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56a953b50bf9e79892156e90e846f7c5323cee31 --- /dev/null +++ b/marked/Rel-11/43_series/43318/b44f89b176c971c7dd264c07bfef2c2a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:535e491614c0dda72da9dca13784d02d1e874f74bb997fddebb6c26b21dff929 +size 11908 diff --git a/marked/Rel-11/43_series/43318/b4f6d3668f7e851eaff07ccf26001623_img.jpg b/marked/Rel-11/43_series/43318/b4f6d3668f7e851eaff07ccf26001623_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bf3375533fd3d1f38e01f80f1521583ce60cf33 --- /dev/null +++ b/marked/Rel-11/43_series/43318/b4f6d3668f7e851eaff07ccf26001623_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:667b23b8fdb0d898ec165f72925c6379b5b52eb8bd6c5161dae598b85c4c1cf4 +size 26162 diff --git a/marked/Rel-11/43_series/43318/b550cb515008f6bab9f295adcb28b5f6_img.jpg b/marked/Rel-11/43_series/43318/b550cb515008f6bab9f295adcb28b5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..432d486f51db72582cfca6720d724810ffde9872 --- /dev/null +++ b/marked/Rel-11/43_series/43318/b550cb515008f6bab9f295adcb28b5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:164a5a6d2e0b0731c63730bbae892e2d861c0651a19eb02c0aa1b1ba3894726a +size 73344 diff --git a/marked/Rel-11/43_series/43318/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Rel-11/43_series/43318/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..031d996fe10331176b81c3a125facd95216f2285 --- /dev/null +++ b/marked/Rel-11/43_series/43318/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4763f4a2b639e2d5bf770fef8248b2cecca3d9d7f0613336c2fa091159ccf5e6 +size 26957 diff --git a/marked/Rel-11/43_series/43318/ca5555bb37f54857199d243feff8479e_img.jpg b/marked/Rel-11/43_series/43318/ca5555bb37f54857199d243feff8479e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f0a8e979bbcaa0391cebca94ad6597aa9dcc922 --- /dev/null +++ b/marked/Rel-11/43_series/43318/ca5555bb37f54857199d243feff8479e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d8d5f508fff9cdff4145724ef0e7194740a8182d5cca22839a2b74682385b75 +size 60807 diff --git a/marked/Rel-11/43_series/43318/d6c377ae3e619ff992bd3647dbf43593_img.jpg b/marked/Rel-11/43_series/43318/d6c377ae3e619ff992bd3647dbf43593_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34ca276fdfa36ac1732581370d2e150c8c21a6f9 --- /dev/null +++ b/marked/Rel-11/43_series/43318/d6c377ae3e619ff992bd3647dbf43593_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:893ce70214c12a2cd9f5d7c8da19e2da7b19f7ddda6299c90c4d5ea373eec0db +size 41863 diff --git a/marked/Rel-11/43_series/43318/d9d09655eb4282168769ac97178db50c_img.jpg b/marked/Rel-11/43_series/43318/d9d09655eb4282168769ac97178db50c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32900b949bf87c99664ad7492e3245c9d1445e4f --- /dev/null +++ b/marked/Rel-11/43_series/43318/d9d09655eb4282168769ac97178db50c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88bc566bea5ef6fddfaae4fe45f87a5ba430a79d9082c790f6e199e8030e6b42 +size 69962 diff --git a/marked/Rel-11/43_series/43318/dbd4bab54b57e8d1abf80e3de6471130_img.jpg b/marked/Rel-11/43_series/43318/dbd4bab54b57e8d1abf80e3de6471130_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e494416afef8bbba5d8c9863a9813a3b1859961 --- /dev/null +++ b/marked/Rel-11/43_series/43318/dbd4bab54b57e8d1abf80e3de6471130_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:133f23bda1349376aecd7b357d93dbfa933a581e38f198ac606ecbf08dec7db0 +size 24759 diff --git a/marked/Rel-11/43_series/43318/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg b/marked/Rel-11/43_series/43318/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ece7d605184a05278b037c53270ed78074233e1 --- /dev/null +++ b/marked/Rel-11/43_series/43318/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:906b926476b6dc3989f2de870338e048d1fc272eb718cabe7a1b13c85e2c1ddd +size 62896 diff --git a/marked/Rel-11/43_series/43318/df1966d80c74bc127f159a48f38b13ee_img.jpg b/marked/Rel-11/43_series/43318/df1966d80c74bc127f159a48f38b13ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e5176b42107101b8f0665e310546cf4e20419b8 --- /dev/null +++ b/marked/Rel-11/43_series/43318/df1966d80c74bc127f159a48f38b13ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05dfc81fc0862bf85400ca3a04949866ab6abfc04cee2b84e9e10fc8e6efd620 +size 98812 diff --git a/marked/Rel-11/43_series/43318/dfe74512a9c9fb620f72c9dbc22874aa_img.jpg b/marked/Rel-11/43_series/43318/dfe74512a9c9fb620f72c9dbc22874aa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..550de8b4cfb8f50276e406fac72eba69f87dc40c --- /dev/null +++ b/marked/Rel-11/43_series/43318/dfe74512a9c9fb620f72c9dbc22874aa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f402758c2ae38cc76c695a23735cb3fe5f5f419a5d8322aab25d2317928af52 +size 119346 diff --git a/marked/Rel-11/43_series/43318/e16bfa31d748f4d99ec4ae3d16656926_img.jpg b/marked/Rel-11/43_series/43318/e16bfa31d748f4d99ec4ae3d16656926_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32618112d7827a3777a07e8e55aea82ea27e4bbc --- /dev/null +++ b/marked/Rel-11/43_series/43318/e16bfa31d748f4d99ec4ae3d16656926_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84e07d380f96ba463b7993445e7f44fc742da1e76eb4ecac52f36af2646e8326 +size 40056 diff --git a/marked/Rel-11/43_series/43318/e29665b8abcea967ef289c6aff07ae4c_img.jpg b/marked/Rel-11/43_series/43318/e29665b8abcea967ef289c6aff07ae4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10c9ecea2b89aede899e55faaef545a05080f3d9 --- /dev/null +++ b/marked/Rel-11/43_series/43318/e29665b8abcea967ef289c6aff07ae4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2198daa6d368f96337e8d2fd8a0515eeab048e3487fd953c34c977c82e7cbb77 +size 67531 diff --git a/marked/Rel-11/43_series/43318/e636d7ccca0ad14c6b95201404324823_img.jpg b/marked/Rel-11/43_series/43318/e636d7ccca0ad14c6b95201404324823_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83cf34e40a4ee79220e52ca561f90579f8f35201 --- /dev/null +++ b/marked/Rel-11/43_series/43318/e636d7ccca0ad14c6b95201404324823_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e196203f7dc78a18a11c2e1e92f4b5e889555b495004c3ab0206f5666cd936e +size 70654 diff --git a/marked/Rel-11/43_series/43318/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/marked/Rel-11/43_series/43318/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a46810c43cbdafc288e0187db39d35b302cf53a6 --- /dev/null +++ b/marked/Rel-11/43_series/43318/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd69acec98883eb2d98e122bd33de1fcc1a7b94dbca39dcf4a85a86fcb3fe961 +size 37753 diff --git a/marked/Rel-11/43_series/43318/eae05333c9188c830bd0ebe58c50453a_img.jpg b/marked/Rel-11/43_series/43318/eae05333c9188c830bd0ebe58c50453a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1cb917ee0eb19a9fb3592bf878d436e1321c268e --- /dev/null +++ b/marked/Rel-11/43_series/43318/eae05333c9188c830bd0ebe58c50453a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f92ec54137b0ab2a1440ccee54960bdf7d9614c26e688f40e8906604bd603d6d +size 21236 diff --git a/marked/Rel-11/43_series/43318/ef45b00396c293be0b18d32b97118bf4_img.jpg b/marked/Rel-11/43_series/43318/ef45b00396c293be0b18d32b97118bf4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82c8bf3acf85b20a7c75d88a7358759cbbe39a43 --- /dev/null +++ b/marked/Rel-11/43_series/43318/ef45b00396c293be0b18d32b97118bf4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b37d6832f9e17f717ed5ba603e0daeca7336da526b7a865e5087020f075a43ef +size 83747 diff --git a/marked/Rel-11/43_series/43318/ef5f5c6665b6ae13660ede412333ba45_img.jpg b/marked/Rel-11/43_series/43318/ef5f5c6665b6ae13660ede412333ba45_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba8851321db373f94deadaa0582c6f3ff4b4c265 --- /dev/null +++ b/marked/Rel-11/43_series/43318/ef5f5c6665b6ae13660ede412333ba45_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9cb59ffdfcddb7ebea2b5d6ee17678195dfec751891fdb782c305e3b4d7accd8 +size 83947 diff --git a/marked/Rel-11/43_series/43318/efb282bed9f06eef1987a14fb27bc599_img.jpg b/marked/Rel-11/43_series/43318/efb282bed9f06eef1987a14fb27bc599_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26163439b1612f046383137b86e53f77dff2fc38 --- /dev/null +++ b/marked/Rel-11/43_series/43318/efb282bed9f06eef1987a14fb27bc599_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:810795401c4b8e8b62f3bc5dfce55136f303164464e51dee5781a825a2da204d +size 91270 diff --git a/marked/Rel-11/43_series/43318/f0a97d0d3818a253c1d2a009966081b1_img.jpg b/marked/Rel-11/43_series/43318/f0a97d0d3818a253c1d2a009966081b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6cb17e628535d6c7e128d6cf3274587c3cc68383 --- /dev/null +++ b/marked/Rel-11/43_series/43318/f0a97d0d3818a253c1d2a009966081b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a661223b1288da404999abaad13a605c89e6338c7fd688e60d1d75cf14ef4de +size 68341 diff --git a/marked/Rel-11/43_series/43318/fcc757566216206ceddbd6c775e8db02_img.jpg b/marked/Rel-11/43_series/43318/fcc757566216206ceddbd6c775e8db02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..008645dc973dcc61d1cd735d081921b78e40ef57 --- /dev/null +++ b/marked/Rel-11/43_series/43318/fcc757566216206ceddbd6c775e8db02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81873573f0f1c4f12636ba15360e2577354f7a7cc2f92520d148a86522fb086d +size 70241 diff --git a/marked/Rel-11/43_series/43318/fe7304192caf64cda93b580c5e7e5c06_img.jpg b/marked/Rel-11/43_series/43318/fe7304192caf64cda93b580c5e7e5c06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c62aa53d8e3d39f6847460b9ff281007ffc8a29 --- /dev/null +++ b/marked/Rel-11/43_series/43318/fe7304192caf64cda93b580c5e7e5c06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1aba02f9d04c89e92b3811387a7d3ed81c56aab350514d1ed2edf8989635cee2 +size 32801 diff --git a/marked/Rel-11/43_series/43318/ffefa4f6eab4ce450aa5ecd3d3fd70bb_img.jpg b/marked/Rel-11/43_series/43318/ffefa4f6eab4ce450aa5ecd3d3fd70bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..737609d45e7d2d695c23cc299904ee358900e09b --- /dev/null +++ b/marked/Rel-11/43_series/43318/ffefa4f6eab4ce450aa5ecd3d3fd70bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:31d479ffe903923b6a2b2099221169bb2f005d2f5c84deb74be10a70f4e7d568 +size 37387 diff --git a/marked/Rel-11/43_series/43318/raw.md b/marked/Rel-11/43_series/43318/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f2ac01885603c13768e375f3730dce89d08d8be6 --- /dev/null +++ b/marked/Rel-11/43_series/43318/raw.md @@ -0,0 +1,4787 @@ + + + + + + +# Contents + +| | | +|--------------------------------------------------------------|----| +| Foreword ..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Definitions, symbols and abbreviations ..... | 10 | +| 3.1 Definitions..... | 10 | +| 3.2 Symbols..... | 11 | +| 3.3 Abbreviations ..... | 11 | +| 4 Architecture..... | 13 | +| 4.1 GAN A/Gb mode architecture..... | 13 | +| 4.2 GAN Iu mode architecture ..... | 14 | +| 5 Functional entities ..... | 16 | +| 5.1 Mobile Station (MS)..... | 16 | +| 5.2 Generic Access Network Controller (GANC) ..... | 16 | +| 5.2.1 GAN A/Gb mode..... | 16 | +| 5.2.2 GAN Iu mode ..... | 17 | +| 6 Control and User Plane Architecture ..... | 17 | +| 6.1 CS Domain (GAN A/Gb mode)..... | 17 | +| 6.1.1 CS Domain - Control Plane..... | 17 | +| 6.1.1.1 CS Domain - Control Plane - GAN Architecture ..... | 17 | +| 6.1.1.2 CS Domain - Control Plane - MS Architecture ..... | 19 | +| 6.1.2 CS Domain - User Plane..... | 20 | +| 6.1.2.1 CS Domain - User Plane - GAN Architecture ..... | 20 | +| 6.2 PS Domain (GAN A/Gb mode) ..... | 21 | +| 6.2.1 PS Domain - GAN Architecture..... | 21 | +| 6.2.1.1 PS Domain - Control Plane - GAN Architecture..... | 21 | +| 6.2.1.2 PS Domain - User Plane - GAN Architecture ..... | 22 | +| 6.2.2 PS Domain - MS Architecture..... | 23 | +| 6.3 CS Domain (GAN Iu mode)..... | 24 | +| 6.3.1 CS Domain - Control Plane..... | 24 | +| 6.3.1.1 CS Domain - Control Plane - GAN Architecture ..... | 24 | +| 6.3.1.2 CS Domain - Control Plane - MS Architecture ..... | 25 | +| 6.3.2 CS Domain - User Plane..... | 26 | +| 6.3.2.1 CS Domain - User Plane - GAN Architecture..... | 26 | +| 6.3.2.2 CS Domain - User Plane - MS Architecture..... | 27 | +| 6.4 PS Domain (GAN Iu mode)..... | 28 | +| 6.4.1 PS Domain - Control Plane ..... | 28 | +| 6.4.1.1 PS Domain - Control Plane - GAN Architecture..... | 28 | +| 6.4.1.2 PS Domain - Control Plane - MS Architecture..... | 29 | +| 6.4.2 PS Domain - User Plane..... | 30 | +| 6.4.2.1 PS Domain - User Plane - GAN Architecture ..... | 30 | +| 6.4.2.2 PS Domain - User Plane - MS Architecture ..... | 31 | +| 7 Management functionality ..... | 32 | +| 7.1 State diagram for Generic Access..... | 32 | +| 7.2 GA-RC (Generic Access Resource Control)..... | 33 | +| 7.2.1 General ..... | 33 | +| 7.2.2 States of the GA-RC sub-layer..... | 33 | +| 7.3 GA-CSR (Generic Access Circuit Switched Resources) ..... | 33 | +| 7.3.1 General ..... | 33 | +| 7.3.2 States of the GA-CSR sub-layer..... | 34 | +| 7.4 GA-PSR (Generic Access Packet Switched Resources)..... | 34 | +| 7.4.1 States of the GA-PSR sub-layer ..... | 34 | +| 7.4a GA-RRC..... | 35 | +| 7.4a.1 General ..... | 35 | +| 7.4a.2 States of the GA-RRC sub-layer ..... | 35 | + +| | | | +|-----------|--------------------------------------------------------------------------------------|----| +| 7.5 | Security Mechanisms ..... | 36 | +| 8 | High-Level Procedures for GAN A/Gb Mode ..... | 36 | +| 8.1 | Mechanism of Mode Selection in Multi-mode terminals..... | 36 | +| 8.2 | PLMN Selection..... | 37 | +| 8.3 | Re-selection between GERAN/UTRAN/E-UTRAN and GAN modes ..... | 38 | +| 8.3.1 | Rove-in (from GERAN/UTRAN/E-UTRAN mode to GAN mode)..... | 38 | +| 8.3.2 | Rove-out (from GAN mode to GERAN/UTRAN/E-UTRAN mode)..... | 39 | +| 8.4 | GAN Discovery and Registration related procedures ..... | 39 | +| 8.4.1 | Discovery and Registration for Generic Access..... | 39 | +| 8.4.1.1 | General..... | 39 | +| 8.4.1.2 | Security Gateway Identification ..... | 39 | +| 8.4.1.3 | GANC capabilities..... | 40 | +| 8.4.1.4 | MS capabilities ..... | 40 | +| 8.4.1.4a | Required GAN Services..... | 40 | +| 8.4.1.4b | GAN Mode Selection..... | 40 | +| 8.4.1.5 | Discovery Procedure..... | 43 | +| 8.4.1.5.1 | Normal Case..... | 43 | +| 8.4.1.6 | Registration procedure..... | 44 | +| 8.4.1.6.1 | Normal case..... | 44 | +| 8.4.1.6.2 | Abnormal cases ..... | 46 | +| 8.4.2 | De-Registration..... | 46 | +| 8.4.3 | Registration Update ..... | 47 | +| 8.4.4 | Keep Alive..... | 48 | +| 8.4.5 | Cell Broadcast Information ..... | 48 | +| 8.5 | Authentication ..... | 49 | +| 8.6 | Encryption ..... | 49 | +| 8.6.1 | Establishment of a Secure Association..... | 49 | +| 8.7 | GA-CSR Connection handling..... | 50 | +| 8.7.1 | GA-CSR Connection Establishment ..... | 50 | +| 8.7.2 | GA-CSR Connection Release..... | 50 | +| 8.8 | Ciphering Configuration ..... | 51 | +| 8.9 | GA-CSR Signalling and SMS Transport Procedures..... | 52 | +| 8.9.1 | Network initiated CS Signalling..... | 52 | +| 8.9.2 | MS initiated CS Signalling ..... | 52 | +| 8.10 | Mobile Originated Call Flow ..... | 53 | +| 8.11 | Mobile Terminated Call Flow ..... | 55 | +| 8.12 | Call Clearing ..... | 56 | +| 8.13 | Channel Modify..... | 56 | +| 8.14 | CS Handover between GAN A/Gb mode and GERAN/UTRAN mode ..... | 57 | +| 8.14.1 | CS Handover to GAN A/Gb mode ..... | 57 | +| 8.14.1.1 | GERAN to GAN CS Handover ..... | 57 | +| 8.14.1.2 | UTRAN to GAN CS Handover ..... | 59 | +| 8.14.2 | CS Handover from GAN A/Gb mode to GERAN ..... | 61 | +| 8.14.3 | CS Handover from GAN A/Gb mode to UTRAN ..... | 63 | +| 8.15 | Cell Change Order between GAN A/Gb mode and GERAN/UTRAN mode..... | 64 | +| 8.16 | GA-PSR Transport Channel Management Procedures ..... | 65 | +| 8.16.1 | MS initiated Activation of GA-PSR Transport Channel..... | 65 | +| 8.16.2 | MS initiated Deactivation of the GA-PSR Transport Channel ..... | 66 | +| 8.16.3 | Implicit Deactivation of the GA-PSR Transport Channel due to MS Deregistration ..... | 67 | +| 8.16.4 | Network initiated GA-PSR Transport Channel Activation ..... | 67 | +| 8.17 | GPRS Data, Signalling and SMS Transport..... | 68 | +| 8.17.1 | GA-PSR GPRS Data Transport Procedures ..... | 68 | +| 8.17.2 | GA-PSR GPRS Signalling and SMS Transport Procedures ..... | 68 | +| 8.17.2.1 | General ..... | 68 | +| 8.17.2.2 | Network initiated GPRS Signalling ..... | 69 | +| 8.17.2.3 | MS initiated GPRS Signalling ..... | 69 | +| 8.18 | GA-PSR Specific Signalling Procedures ..... | 69 | +| 8.18.1 | Packet Paging for GPRS Data Service ..... | 69 | +| 8.18.2 | Packet Paging for CS Domain Service ..... | 70 | +| 8.18.3 | GPRS Suspend Procedure ..... | 70 | +| 8.18.4 | GPRS Resume Procedure ..... | 71 | + +| | | | +|------------|-----------------------------------------------------------------|-----| +| 8.18.5 | MS Initiated Downlink Flow Control..... | 72 | +| 8.18.6 | Uplink Flow Control..... | 73 | +| 8.19 | Short Message Service ..... | 73 | +| 8.19.1 | GSM based SMS ..... | 73 | +| 8.19.2 | GPRS based SMS ..... | 74 | +| 8.20 | Supplementary Services ..... | 74 | +| 8.21 | Emergency Services ..... | 74 | +| 8.21.1 | General ..... | 74 | +| 8.21.2 | North American Emergency Calls..... | 74 | +| 8.21.2.1 | Phase 1 Solution..... | 74 | +| 8.21.2.1.1 | Phase 1 Requirements ..... | 74 | +| 8.21.2.1.2 | Phase 1 Mechanism..... | 75 | +| 8.21.2.2 | Phase 2 Solution..... | 75 | +| 8.21.2.2.1 | Phase 2 Requirements ..... | 75 | +| 8.21.2.2.2 | Phase 2 Mechanism..... | 75 | +| 8.22 | Location Services ..... | 75 | +| 8.23 | PS Handovers between GAN A/Gb mode and GERAN/UTRAN mode ..... | 76 | +| 9 | High-Level Procedures for GAN Iu Mode ..... | 76 | +| 9.1 | Mechanism of Mode Selection in Multi-mode terminals..... | 76 | +| 9.2 | PLMN Selection..... | 76 | +| 9.3 | Re-selection between GERAN/UTRAN/E-UTRAN and GAN modes ..... | 76 | +| 9.4 | GAN Discovery and Registration related procedures ..... | 76 | +| 9.5 | Authentication ..... | 76 | +| 9.6 | Encryption ..... | 76 | +| 9.7 | GA-RRC Connection handling ..... | 76 | +| 9.7.1 | GA-RRC Connection Establishment..... | 77 | +| 9.7.2 | GA-RRC Connection Release ..... | 77 | +| 9.7.3 | GA-RRC Connection Release Request ..... | 78 | +| 9.8 | Security Mode Control..... | 78 | +| 9.9 | NAS Signalling Procedures..... | 79 | +| 9.10 | Mobile Originated CS Call..... | 80 | +| 9.11 | Mobile Terminated CS Call ..... | 82 | +| 9.12 | CS Call Clearing..... | 84 | +| 9.12.1 | CS Call Release ..... | 84 | +| 9.12.2 | CS Channel Release ..... | 84 | +| 9.13 | CS Channel Modification..... | 85 | +| 9.14 | CS Handover between GAN Iu mode and GERAN/UTRAN mode..... | 86 | +| 9.14.1 | CS Handover from GERAN to GAN..... | 86 | +| 9.14.1.1 | Normal case: IMSI is present in Relocation Request message..... | 87 | +| 9.14.1.2 | Exception Case: No IMSI in Relocation Request..... | 89 | +| 9.14.2 | CS Handover from UTRAN to GAN ..... | 90 | +| 9.14.2.1 | Normal Case: IMSI is present in Relocation Request message..... | 91 | +| 9.14.2.2 | Exception Case: No IMSI in Relocation Request..... | 92 | +| 9.14.3 | CS Handover from GAN Iu mode to GERAN ..... | 93 | +| 9.14.4 | CS Handover from GAN Iu mode to UTRAN ..... | 95 | +| 9.15 | Cell Change Order between GAN Iu mode and GERAN mode ..... | 97 | +| 9.16 | GA-RRC Packet Transport Channel Management Procedures..... | 97 | +| 9.16.1 | States of the GA-RRC Packet Transport Channel..... | 98 | +| 9.16.2 | PTC Activation..... | 98 | +| 9.16.2.1 | PTC Activation when GANC receives RAB Assignment Request..... | 98 | +| 9.16.2.2 | PTC Activation when GANC receives Relocation Request..... | 100 | +| 9.16.3 | PTC Data transfer..... | 101 | +| 9.16.4 | MS initiated PTC De-activation..... | 101 | +| 9.16.5 | MS initiated PTC Re-activation ..... | 102 | +| 9.16.6 | Network initiated PTC De-activation..... | 103 | +| 9.16.7 | Network initiated PTC Re-activation..... | 104 | +| 9.16.7.1 | Active PDP Context, PS Signalling Connection Exists..... | 104 | +| 9.16.7.2 | Active PDP Context, No PS Signalling Connection..... | 105 | +| 9.16.8 | Implicit PTC De-activation due to MS De-registration..... | 106 | +| 9.16.9 | PTC Modification..... | 106 | +| 9.17 | (void)..... | 107 | + +| | | | +|-------------------------------|------------------------------------------------------------|------------| +| 9.18 | (void) ..... | 107 | +| 9.19 | Short Message Service ..... | 107 | +| 9.19.1 | SMS via the CS domain ..... | 107 | +| 9.19.2 | SMS via the PS domain ..... | 107 | +| 9.20 | Supplementary Services ..... | 108 | +| 9.21 | Emergency Services ..... | 108 | +| 9.22 | Location Services ..... | 108 | +| 9.23 | PS Handover between GAN Iu mode and GERAN/UTRAN mode ..... | 108 | +| 9.23.1 | PS Handover from GERAN to GAN ..... | 108 | +| 9.23.1.1 | Preparation Phase ..... | 108 | +| 9.23.1.2 | Execution Phase ..... | 109 | +| 9.23.2 | PS Handover from UTRAN to GAN ..... | 110 | +| 9.23.2.1 | Preparation Phase ..... | 110 | +| 9.23.2.2 | Execution Phase ..... | 112 | +| 9.23.3 | PS Handover from GAN to GERAN ..... | 113 | +| 9.23.3.1 | Preparation Phase ..... | 113 | +| 9.23.3.2 | Execution Phase ..... | 114 | +| 9.23.4 | PS handover from GAN to UTRAN ..... | 115 | +| 9.23.4.1 | Preparation Phase ..... | 115 | +| 9.23.4.2 | Execution Phase ..... | 116 | +| Annex A (normative): | Security mechanisms ..... | 117 | +| A.1 | EAP based Authentication ..... | 117 | +| A.1.1 | EAP-SIM Procedure for authentication ..... | 117 | +| A.1.2 | EAP-AKA Procedure for authentication ..... | 119 | +| A.1.3 | Fast Re-authentication ..... | 120 | +| A.1.3.1 | EAP-SIM Fast Re-authentication ..... | 121 | +| A.1.3.2 | EAP-AKA Fast Re-authentication ..... | 122 | +| A.2 | Profile of IKEv2 ..... | 123 | +| A.3 | Profile of IPsec ESP ..... | 123 | +| Annex B (informative): | Configuration Information ..... | 124 | +| B.1 | GAN A/Gb mode ARFCN/BSIC for handover-to-GAN ..... | 124 | +| B.2 | GAN Iu mode UARFCN/PSC for handover-to-GAN ..... | 124 | +| B.2.1 | Cell Measurement Quantities and Values ..... | 124 | +| Annex C (informative): | Identifiers in GAN ..... | 126 | +| C.1 | Identifiers for MSs and generic IP access network ..... | 126 | +| C.2 | Cell identifiers for GAN A/Gb mode ..... | 126 | +| C.2.1 | GAN Cell Id for Location Services & Billing ..... | 126 | +| C.2.1.1 | Assigning GAN Cell Id based on GSM location ..... | 126 | +| C.2.2 | GAN Cell Id for handover-to-GAN ..... | 127 | +| C.2.3 | GAN ARFCN/BSIC for handover-to-GAN ..... | 127 | +| C.3 | (void) ..... | 127 | +| Annex D (informative): | Change history ..... | 128 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document defines the stage 2 service description for a Generic Access Network (GAN) . It describes the GAN system concepts, documents the reference architecture, functional entities, network interfaces, and high-level procedures. + +GAN supports two modes of operation: + +- GAN A/Gb mode +- GAN Iu mode + +GAN A/Gb mode supports an extension of GSM/GPRS mobile services that is achieved by tunnelling Non Access Stratum (NAS) protocols between the MS and the Core Network over an IP network and the A and Gb interfaces to the MSC and SGSN, respectively. + +GAN Iu mode supports an extension of UMTS mobile services that is achieved by tunnelling Non Access Stratum (NAS) protocols between the user equipment (MS) and the Core Network over an IP network and the Iu-cs and Iu-ps interfaces to the MSC and SGSN, respectively. + +Both GAN modes are complements to traditional GERAN/UTRAN/E-UTRAN radio access network coverage. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TS 23.002: "Network architecture". +- [2] 3GPP TS 23.009: "Handover procedures". +- [3] 3GPP TS 23.271: "Location Services (LCS); Functional description; Stage 2". +- [4] 3GPP TS 23.122: "Non-Access-Stratum functions related to Mobile Station (MS) in idle mode". +- [5] 3GPP TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes". +- [6] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core network protocols; Stage 3". +- [7] 3GPP TS 26.071: "AMR speech codec; General description". +- [8] 3GPP TS 29.234: "3GPP system to Wireless Local Area Network (WLAN) interworking, Stage 3". +- [9] 3GPP TS 33.234: "3G security; Wireless Local Area Network (WLAN) interworking security". +- [10] 3GPP TS 43.020: "Security related network functions". +- [11] 3GPP TS 48.004: "Base Station System - Mobile-services Switching Centre (BSS-MSC) interface; Layer 1 specification". +- [12] 3GPP TS 48.006: "Signalling transport mechanism specification for the Base Station System - Mobile-services Switching Centre (BSS-MSC) interface". + +- [13] 3GPP TS 48.008: "Mobile Switching Centre - Base Station System (MSC-BSS) interface; Layer 3 specification". +- [14] 3GPP TS 48.014: "General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN) interface; Gb interface Layer 1". +- [15] 3GPP TS 48.016: "General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN) interface; Network Service". +- [16] 3GPP TS 48.018: "General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN) interface; BSS GPRS protocol". +- [17] 3GPP TS 43.059: "Functional stage 2 description of Location Services (LCS) in GERAN". +- [18] 3GPP TS 45.008: "Radio subsystem link control". +- [19] IETF RFC 793: "Transmission Control Protocol". +- [20] IETF RFC 3550: "RTP: A Transport Protocol for Real-Time Applications". +- [21] Void. +- [22] Void. +- [23] Void. +- [24] Void. +- [25] Void. +- [26] Void. +- [27] Void. +- [28] Void. +- [29] Void. +- [30] IETF RFC 4186: "Extensible Authentication Protocol Method for Global System for Mobile Communications (GSM) Subscriber Identity Modules (EAP-SIM)". +- [31] Void. +- [32] IETF RFC 5996: "Internet Key Exchange Protocol Version 2 (IKEv2)". +- [33] Void. +- [34] Void. +- [35] Void. +- [36] IETF RFC 2486: "The Network Access Identifier". +- [37] IETF RFC 768: "User Datagram Protocol". +- [38] IETF RFC 4187: "Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA)". +- [39] IETF RFC 791: "Internet Protocol". +- [40] 3GPP TS 25.331: "Radio Resource Control (RRC) protocol specification". +- [41] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)". +- [42] Void. +- [43] 3GPP TS 23.003: "Numbering, addressing and identification". + +- [44] 3GPP TS 43.129: "Packet-switched handover for GERAN A/Gb mode; Stage 2". +- [45] 3GPP TS 25.410: "UTRAN Iu Interface: general aspects and principles". +- [46] 3GPP TS 25.411: "UTRAN Iu interface layer 1". +- [47] 3GPP TS 25.412: "UTRAN Iu interface signalling transport". +- [48] 3GPP TS 25.413: "UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling". +- [49] 3GPP TS 25.414: "UTRAN Iu interface data transport & transport signalling". +- [50] 3GPP TS 25.415: "UTRAN Iu interface user plane protocols". +- [51] 3GPP TS 25.419: "UTRAN Iu-BC interface: Service Area Broadcast Protocol (SABP)". +- [52] 3GPP TS 25.450: "UTRAN Iupc interface general aspects and principles". +- [53] 3GPP TS 22.011: "Service accessibility". +- [54] IETF RFC 4867, April 2007: "RTP Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs". +- [55] 3GPP TS 33.210: "Network Domain Security (NDS); IP network layer security". +- [56] IETF RFC 4303: "IP Encapsulating Security Payload (ESP)". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**AP-ID:** The AP-ID (Access Point-ID) is the physical identity (e.g. MAC address) of the generic IP access network point through which the MS is accessing GAN service. This identifier is provided by the MS (obtained via broadcast from the AP) to the GANC via the Up interface, when it requests GAN service. The AP-ID may be used by the GANC to support location services. The AP-ID may also be used by the service provider to restrict GAN service access via only authorized APs. + +**GERAN/UTRAN Mode:** MS mode of operation where the NAS layers communicate through either the GERAN RR or the UTRAN RRC entities. + +**GERAN/UTRAN/E-UTRAN Mode:** MS mode of operation where the NAS layers communicate through either the GERAN RR, the UTRAN RRC or the E-UTRAN RRC entities. + +**GAN A/Gb Mode:** MS mode of operation where the NAS layers communicate through the GA-CSR and GA-PSR entities. + +**GAN Iu Mode:** MS mode of operation where the NAS layers communicate through the GA-RRC CS and GA-RRC PS entities. + +**GAN Mode:** This term is used when a procedure applies to both GAN A/Gb mode and GAN Iu mode (e.g., see clause 8.1, "Mechanism of Mode Selection in Multi-mode terminals"). + +**Generic Access Network:** access network providing access to A/Gb or Iu interfaces via an IP network + +**Generic Access Network Controller:** network node that connects to the MSC and SGSN via the A-interface and Gb interface (GAN A/Gb mode) or the Iu-cs interface and Iu-ps interface (GAN Iu mode) and enables access via a generic IP network. + +Three different logical roles for the GANC are defined in this specification: Provisioning GANC, Default GANC and Serving GANC. + +**default GANC:** logical role of a GANC in the HPLMN, which redirects an MS performing the GAN Registration Procedure to a preferred Serving GANC within the HPLMN or VPLMN. The Serving GANC and Default GANC may be the same entity, in which case no redirection is required. + +**discovery procedure:** process by which the MS discovers the Default GANC in the HPLMN. + +**CS handover:** mobile station engaged in a call (a CS domain service) moves between 3GPP access networks and GAN. + +**handover in:** mobile station moves from 3GPP access networks to GAN. + +**handover out:** mobile station moves from GAN to 3GPP access networks. + +**PS handover:** A mobile station with one or more ongoing PS domain services moves between a GAN cell and a GERAN/UTRAN cell. + +**provisioning GANC:** logical role of a GANC in the HPLMN of an MS. When an MS performs the Discovery Procedure to this GANC, the MS is provided the address of the Default GANC in the HPLMN. + +**redirection:** process by which a Default or Serving GANC redirects an MS to an alternative Serving GANC. This alternative GANC is likely to become the Serving GANC for the MS. + +**registration procedure:** process by which an MS requests the Generic Access Service from a GANC. + +**rove in:** mobile station reselects from 3GPP access networks to GAN. + +**rove out:** mobile station reselects from GAN to 3GPP access networks. + +**roving:** action of re-selection between 3GPP access technology and GAN for a mobile station in idle mode. + +**seamless:** free from noticeable transitions (i.e. no end-user action is required; speech interruptions are short; service interruptions are short; incoming calls are not missed; packet sessions are maintained; services work identically). + +**serving GANC:** logical role of the GANC in a PLMN which provides an MS with the Generic Access service. + +**suitable cell:** this is a cell on which an MS may camp. It must satisfy criteria which are defined for A/Gb mode in 3GPP TS 43.022 and for Iu mode in 3GPP TS 25.304. + +**user equipment:** generally referred to as “mobile station” in this document. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----|-------------------------------| +| Up | Interface between MS and GANC | +|----|-------------------------------| + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|--------|-------------------------------------------------| +| AAA | Authentication, Authorization and Accounting | +| AKA | Authentication and Key Agreement | +| AP | Access Point | +| AS | Access Stratum | +| BSC | Base Station Controller | +| BSS | Base Station Subsystem | +| BSSGP | Base Station System GPRS Protocol | +| BSSMAP | Base Station System Management Application Part | +| CC | Call Control | +| CGI | Cell Global Identification | +| CM | Connection Management | +| CN | Core Network | +| CS | Circuit Switched | +| CTM | Cellular Text Telephone Modem | +| DNS | Domain Name System | +| DTM | Dual Transfer Mode | + +| | | +|---------|-----------------------------------------------------------------------------| +| E-UTRAN | Evolved UTRAN | +| EAP | Extensible Authentication Protocol | +| ETSI | European Telecommunications Standards Institute | +| FCC | US Federal Communications Commission | +| FQDN | Fully Qualified Domain Name | +| GA-CSR | Generic Access - Circuit Switched Resources | +| GAD | Geographical Area Description | +| GAN | Generic Access Network | +| GANC | Generic Access Network Controller | +| GA-PSR | Generic Access - Packet Switched Resources | +| GA-RC | Generic Access - Resource Control | +| GA-RRC | Generic Access - Radio Resource Control | +| GERAN | GSM EDGE Radio Access Network | +| GGSN | Gateway GPRS Support Node | +| GMM/SM | GPRS Mobility Management and Session Management | +| GPRS | General Packet Radio Service | +| GSM | Global System for Mobile communications | +| GSN | GPRS Support Node | +| HLR | Home Location Register | +| HPLMN | Home PLMN | +| IETF | Internet Engineering Task Force | +| IKE | Internet Key Exchange | +| IMEISV | International Mobile station Equipment Identity and Software Version number | +| IMSI | International Mobile Subscriber Identity | +| IP | Internet Protocol | +| LA | Location Area | +| LAI | Location Area Identity | +| LLC | Logical Link Control | +| MAC | Medium Access Control | +| MAC | Message Authentication Code | +| MM | Mobility Management | +| MS | Mobile Station | +| MSC | Mobile Switching Center | +| MTP1 | Message Transfer Part layer 1 | +| MTP2 | Message Transfer Part layer 2 | +| MTP3 | Message Transfer Part layer 3 | +| NAS | Non-Access Stratum | +| PDP | Packet Data Protocol | +| PDU | Protocol Data Unit | +| PLMN | Public Land Mobile Network | +| PS | Packet Switched | +| PSAP | Public Safety Answering Point | + +NOTE: A PSAP is an emergency services network element that is responsible for answering emergency calls. + +| | | +|--------|------------------------------------| +| PSTN | Public Switched Telephone Network | +| P-TMSI | Packet - TMSI | +| QoS | Quality of Service | +| RA | Routing Area | +| RAC | Routing Area Code | +| RAI | Routing Area Identity | +| RAT | Radio Access Technology | +| RLC | Radio Link Control | +| RNC | Radio Network Controller | +| RTCP | Real Time Control Protocol | +| RTP | Real Time Protocol | +| SCCP | Signalling Connection Control Part | +| SEGW | SEcurity GateWay | +| SGSN | Serving GPRS Support Node | +| SIM | Subscriber Identity Module | +| SMLC | Serving Mobile Location Center | +| SMS | Short Message Service | + +| | | +|--------|--------------------------------------------| +| SNDPCP | Sub-Network Dependent Convergence Protocol | +| TAI | Tracking Area Identity | +| TBF | Temporary Block Flow | +| TC | Transport Channel | +| TCP | Transmission Control Protocol | +| TFO | Tandem Free Operation | +| TMSI | Temporary Mobile Subscriber Identity | +| TrFO | Transcoder Free Operation | +| TTY | Text Telephone or Teletypewriter | +| UDP | User Datagram Protocol | +| UE | User Equipment | +| UMTS | Universal Mobile Telecommunication System | +| UTRAN | UMTS Terrestrial Radio Access Network | +| VLR | Visited Location Register | +| VPLMN | Visited Public Land Mobile Network | + +# 4 Architecture + +## 4.1 GAN A/Gb mode architecture + +The Generic Access Network A/Gb mode functional architecture is illustrated in figure 1. + +![Figure 1: GAN A/Gb mode functional architecture diagram. The diagram shows the functional architecture of GAN A/Gb mode. On the left, a Mobile Station (MS) is connected via a Generic IP Access Network to the Generic Access Network Controller (GANC). The GANC contains a Security Gateway (SEGW). Above the GANC, there are two dashed boxes labeled SMLC and CBC, connected to the GANC via an Lb interface. To the right of the GANC, there is a dashed box labeled HPLMN/VPLMN. Inside this box, the GANC is connected to an MSC via an A interface, to an SGSN via a Gb interface, and to an AAA Proxy/Server via a Wm interface. The AAA Proxy/Server is connected to an HLR via a D'/Gr interface. Below the HPLMN/VPLMN box, there is a Wd interface. A legend at the bottom indicates that dashed lines represent 'Out of Scope' components. A note at the bottom right indicates 'HPLMN (roaming case)'.](3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg) + +MS Mobile Station +GANC GAN Controller +SEGW Security Gateway + +----- Out of Scope + +HPLMN (roaming case) + +Figure 1: GAN A/Gb mode functional architecture diagram. The diagram shows the functional architecture of GAN A/Gb mode. On the left, a Mobile Station (MS) is connected via a Generic IP Access Network to the Generic Access Network Controller (GANC). The GANC contains a Security Gateway (SEGW). Above the GANC, there are two dashed boxes labeled SMLC and CBC, connected to the GANC via an Lb interface. To the right of the GANC, there is a dashed box labeled HPLMN/VPLMN. Inside this box, the GANC is connected to an MSC via an A interface, to an SGSN via a Gb interface, and to an AAA Proxy/Server via a Wm interface. The AAA Proxy/Server is connected to an HLR via a D'/Gr interface. Below the HPLMN/VPLMN box, there is a Wd interface. A legend at the bottom indicates that dashed lines represent 'Out of Scope' components. A note at the bottom right indicates 'HPLMN (roaming case)'. + +Figure 1: GAN A/Gb mode functional architecture + +The main features of the GAN A/Gb mode architecture are: + +- New entities, and entities with enhanced functionality: + - Mobile Station (MS). + - Generic Access Network Controller (GANC). The GANC appears to the core network as a GERAN Base Station Subsystem (BSS). It includes a Security Gateway (SEGW) that terminates secure remote access tunnels from the MS, providing mutual authentication, encryption and data integrity for signalling, voice and data traffic. +- A Generic IP Access network provides connectivity between the MS and the GANC. The IP transport connection extends from the GANC to the MS. A single interface, the Up interface, is defined between the GANC and the MS. + +- Co-existence with the GSM/GPRS Radio Access Network (GERAN) and interconnection with the Core Network (CN) via the standardized interfaces defined for GERAN A/Gb mode: + - A-interface for circuit switched services as defined in 3GPP TS 48.008 [13]. + - Gb-interface for packet switched services as defined in 3GPP TS 48.018 [16]. + - Lb-interface for supporting location services as defined in 3GPP TS 43.059 [17]. + - CBC-BSC interface for supporting cell broadcast services as defined in 3GPP TS 23.041 +- Transaction control (e.g. CC, SM) and user services are provided by the core network (e.g. MSC/VLR and the SGSN/GGSN). +- Use of AAA server over the Wm interface as defined by 3GPP TS 29.234 [8]. The AAA server is used to authenticate the MS when it sets up a secure tunnel. Note that only a subset of the Wm functionalities is required for the GAN application. As a minimum the GANC-SEGW shall support the Wm authentication procedures. + +Indication of support for PS Services and of support for DTM is provided through appropriate signalling to the MS. + +## 4.2 GAN Iu mode architecture + +The Generic Access Network Iu mode functional architecture is illustrated in figure 1a. + +![Figure 1a: GAN Iu mode functional architecture diagram. The diagram shows the functional architecture of GAN Iu mode. On the left, a Mobile Station (MS) is connected via an 'Up' interface to a Generic IP Access Network. The Access Network is connected to a Generic Access Network Controller (GANC). The GANC contains a Security Gateway (SEGW). Above the GANC, there are two dashed boxes labeled SMLC and CBC, connected via 'Iu-pc' and 'Iu-bc' interfaces respectively. To the right of the GANC is a large box labeled HPLMN/VPLMN. Inside this box, there are three dashed boxes: MSC, SGSN, and AAA Proxy/Server. The GANC is connected to the MSC via 'Iu-cs', to the SGSN via 'Iu-ps', and to the AAA Proxy/Server via 'Wm'. The AAA Proxy/Server is connected to an HLR via 'D'/Gr' and to an external HPLMN (roaming case) via 'Wd'. A legend at the bottom left defines the abbreviations: MS (Mobile Station), SEGW (Security Gateway), GANC (Generic Access Network Controller), and a dashed line for 'Out of Scope'.](16c1175b5f05a4b55e6d396fc51b15b3_img.jpg) + +Figure 1a: GAN Iu mode functional architecture diagram. The diagram shows the functional architecture of GAN Iu mode. On the left, a Mobile Station (MS) is connected via an 'Up' interface to a Generic IP Access Network. The Access Network is connected to a Generic Access Network Controller (GANC). The GANC contains a Security Gateway (SEGW). Above the GANC, there are two dashed boxes labeled SMLC and CBC, connected via 'Iu-pc' and 'Iu-bc' interfaces respectively. To the right of the GANC is a large box labeled HPLMN/VPLMN. Inside this box, there are three dashed boxes: MSC, SGSN, and AAA Proxy/Server. The GANC is connected to the MSC via 'Iu-cs', to the SGSN via 'Iu-ps', and to the AAA Proxy/Server via 'Wm'. The AAA Proxy/Server is connected to an HLR via 'D'/Gr' and to an external HPLMN (roaming case) via 'Wd'. A legend at the bottom left defines the abbreviations: MS (Mobile Station), SEGW (Security Gateway), GANC (Generic Access Network Controller), and a dashed line for 'Out of Scope'. + +**Figure 1a: GAN Iu mode functional architecture** + +The main features of the GAN Iu mode architecture are: + +- Entities with enhanced functionality: + - Mobile Station (MS). The functionality of the MS defined for GAN A/Gb mode is modified to support GAN Iu mode operation. The MS may support GAN Iu mode operation, GAN A/Gb mode operation, or both. Mode selection is performed during registration. + - Generic Access Network Controller (GANC). The functionality of the GANC defined for GAN A/Gb mode is modified so as to appear to the core network as a UTRAN Radio Network Controller (RNC). As for GAN A/Gb mode, the GANC includes a Security Gateway (SEGW) that terminates secure remote access tunnels + +from the MS, providing mutual authentication, encryption and data integrity for signalling, voice and data traffic. + +- A generic IP access network provides connectivity between the MS and the GANC. The IP transport connection extends from the GANC to the MS. A single interface, the Up interface, is defined between the GANC and the MS. Functionality is added to this interface, over that defined for GAN A/Gb mode, to support the GAN Iu mode service. +- Co-existence with the UMTS Terrestrial Radio Access Network (UTRAN) and interconnection with the Core Network (CN) via the standardized interfaces defined for UTRAN: + - Iu-cs interface for circuit switched services as overviewed in 3GPP TS 25.410 [45]. + - Iu-ps interface for packet switched services as overviewed in 3GPP TS 25.410 [45]. + - Iu-pc interface for supporting location services as described in 3GPP TS 25.450 [52]. + - Iu-bc interface for supporting cell broadcast services as described in 3GPP TS 25.419 [51]. +- Transaction control (e.g. CC, SM) and user services are provided by the core network (e.g. MSC/VLR and the SGSN/GGSN). +- Use of AAA server over the Wm interface as defined by 3GPP TS 29.234 [8]. The AAA server is used to authenticate the MS when it sets up a secure tunnel. Note that only a subset of the Wm functionalities is required for GAN Iu mode. As a minimum the GANC-SEGW shall support the Wm authentication procedures. + +A GANC implementation may simultaneously support both GAN A/Gb mode and GAN Iu mode operation; the interfaces associated with both modes of operation are shown in the following figure. + +![Figure 1b: Simultaneous GAN A/Gb mode and GAN Iu mode functional architecture diagram. The diagram shows a Mobile Station (MS) connected via a Generic IP Access Network to a Generic Access Network Controller (GANC) through the Up interface. The GANC contains a Security Gateway (SEGW). Above the GANC, four dashed boxes represent external entities: SMLC, CBC, and two unlabeled boxes. Interfaces connect these to the GANC: Iu-pc (to SMLC), Lb (between two unlabeled boxes), and Iu-bc (to CBC). The GANC connects to a Core Network (HPLMN/VPLMN) via several interfaces: Iu-cs to an MSC, Iu-ps to an SGSN, Gb to an SGSN, and Wm to an AAA Proxy/Server. The AAA Proxy/Server connects to an HLR via D'/Gr' and to the HPLMN (roaming case) via Wd. A legend defines MS as Mobile Station, SEGW as Security Gateway, and GANC as Generic Access Network Controller. Dashed lines indicate components 'Out of Scope'.](9ae17964ddd9b814c7d905b1af2fddf2_img.jpg) + +MS Mobile Station +SEGW Security Gateway +GANC Generic Access Network Controller + +----- Out of Scope + +HPLMN (roaming case) + +Figure 1b: Simultaneous GAN A/Gb mode and GAN Iu mode functional architecture diagram. The diagram shows a Mobile Station (MS) connected via a Generic IP Access Network to a Generic Access Network Controller (GANC) through the Up interface. The GANC contains a Security Gateway (SEGW). Above the GANC, four dashed boxes represent external entities: SMLC, CBC, and two unlabeled boxes. Interfaces connect these to the GANC: Iu-pc (to SMLC), Lb (between two unlabeled boxes), and Iu-bc (to CBC). The GANC connects to a Core Network (HPLMN/VPLMN) via several interfaces: Iu-cs to an MSC, Iu-ps to an SGSN, Gb to an SGSN, and Wm to an AAA Proxy/Server. The AAA Proxy/Server connects to an HLR via D'/Gr' and to the HPLMN (roaming case) via Wd. A legend defines MS as Mobile Station, SEGW as Security Gateway, and GANC as Generic Access Network Controller. Dashed lines indicate components 'Out of Scope'. + +**Figure 1b: Simultaneous GAN A/Gb mode and GAN Iu mode functional architecture** + +# --- 5 Functional entities + +## 5.1 Mobile Station (MS) + +The MS contains a new functional block to access a Generic Access Network (GAN). + +## 5.2 Generic Access Network Controller (GANC) + +### 5.2.1 GAN A/Gb mode + +The core network interacts with the Generic Access Network Controller (GANC) as though it was an A/Gb mode BSS. The generic IP access network provides connectivity between the GANC and the MS. The GANC entity inter-works between the A/Gb interfaces and a generic IP access network, using the following functionality: + +- User plane circuit switched services: + - Reframing of AMR/RTP to AMR/(A-interface framing). + - If non-TrFO, transcoding voice to/from the MS to PCM voice from/to the MSC. + - If TrFO, transcoding maybe required if a common codec cannot be negotiated. +- User plane packet switched services: + - Inter-working data transport channels over Up interface to packet flows over Gb interface. +- Control plane functionality: + - Security Gateway (SEGW) for the set-up of a secure tunnel to MS for mutual authentication, encryption and data integrity. The SEGW provides a subset of the Wm functions, specifically the authentication procedures. + - Registration for GAN access and providing system information. + - Management of GAN bearer paths for CS and PS services, including the establishment, administration, and release of control and user plane bearers between the MS and the GANC. + - Functionality providing support for paging, handover and PS handover procedures. + - Transparent transfer of L3 messages (i.e. NAS protocols) between the MS and core network. + +### 5.2.2 GAN Iu mode + +The core network interacts with the Generic Access Network Controller (GANC) as though it was an RNC. The generic IP access network provides connectivity between the GANC and the MS. The GANC entity inter-works between the Iu interfaces and a generic IP access network, using the following functionality: + +- User plane circuit switched services: + - The interworking of circuit switched user data between the Up interface and the Iu-cs interface +- User plane packet switched services: + - The interworking of packet switched user data between the Up interface and the Iu-ps interface + +- Control plane functionality: + - Security Gateway (SEGW) for the set-up of a secure tunnel to the MS for mutual authentication, encryption and data integrity + - GAN Discovery support and Default GANC assignment + - GAN Registration support including provision of GAN system information to the MS and possible redirection to a different Serving GANC + - Management of GAN bearer paths for CS and PS services, including the establishment, administration, and release of control and user plane bearers between the MS and the GANC + - Functionality providing support for paging and relocation/handover procedures + - Transparent transfer of L3 messages (i.e., NAS protocols) between the MS and core network + +# 6 Control and User Plane Architecture + +## 6.1 CS Domain (GAN A/Gb mode) + +### 6.1.1 CS Domain - Control Plane + +#### 6.1.1.1 CS Domain - Control Plane - GAN Architecture + +The GAN architecture in support of CS Domain control plane is illustrated in figure 2. + +![Figure 2: Up CS Domain Control Plane Architecture. This diagram illustrates the protocol stack for the control plane between a Mobile Station (MS) and a Mobile Switching Center (MSC) via a Generic IP Network and a GANC. The MS stack includes CC/SS/SMS, MM, GA-CSR, GA-RC, TCP, Remote IP, IPSec ESP, Transport IP, and Access Layers. The GANC stack includes GA-CSR, GA-RC, TCP, Remote IP, IPSec ESP, Transport IP, and Access Layers, plus BSSAP, SCCP, MTP3, MTP2, and MTP1. The MSC stack includes CC/SS/SMS, MM, BSSAP, SCCP, MTP3, MTP2, and MTP1. The Up Interface is shown between the MS and the GANC, and the A interface is shown between the GANC and the MSC.](29f586959675cafdf81cf934954908eb_img.jpg) + +Figure 2: Up CS Domain Control Plane Architecture. This diagram illustrates the protocol stack for the control plane between a Mobile Station (MS) and a Mobile Switching Center (MSC) via a Generic IP Network and a GANC. The MS stack includes CC/SS/SMS, MM, GA-CSR, GA-RC, TCP, Remote IP, IPSec ESP, Transport IP, and Access Layers. The GANC stack includes GA-CSR, GA-RC, TCP, Remote IP, IPSec ESP, Transport IP, and Access Layers, plus BSSAP, SCCP, MTP3, MTP2, and MTP1. The MSC stack includes CC/SS/SMS, MM, BSSAP, SCCP, MTP3, MTP2, and MTP1. The Up Interface is shown between the MS and the GANC, and the A interface is shown between the GANC and the MSC. + +Figure 2: Up CS Domain Control Plane Architecture + +The main features of the Up interface for the CS domain control plane are as follows: + +- The underlying Access Layers and Transport IP layer provides the generic connectivity between the MS and the GANC. +- The IPsec layer provides encryption and data integrity. +- TCP provides reliable transport for the GA-RC between MS and GANC and is transported using the Remote IP layer. +- The GA-RC manages the IP connection, including the GAN registration procedures. + +- The GA-CSR protocol performs functionality equivalent to the GSM-RR protocol, using the underlying connection managed by the GA-RC. +- Protocols, such as MM and above, are carried transparently between the MS and MSC. +- The GANC terminates the GA-CSR protocol and inter-works it to the A-interface using BSSAP messaging. +- The Remote IP layer is the 'inner' IP layer for IPsec tunnel mode and is used by the MS to be addressed by the GANC. Remote IP layer is configured during the IPsec connection establishment. + +#### 6.1.1.2 CS Domain - Control Plane - MS Architecture + +The MS architecture for the CS domain control plane in the MS is illustrated in figure 3. + +![Figure 3: MS CS Domain Control plane Architecture diagram showing the stack of protocols and interfaces for a Mobile Station (MS).](8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg) + +The diagram illustrates the MS CS Domain Control plane Architecture. At the top, the Connection Management (CM) layer contains three sub-components: CC (Call Control), SS (Supplementary Services), and SMS (Short Message Service). These are connected to the Mobility Management (MM) layer via MMCC-SAP, MMSS-SAP, and MMSMS-SAP interfaces respectively. The MM layer is connected to the Access Mode switch via the RR-SAP interface. The Access Mode switch can direct traffic to either the GA-CSR (GPRS Control Plane) or the GSM RR (Radio Resource) layer via the GANGSM-SAP interface. The GA-CSR layer is connected to the GA-RC (GPRS Control Plane) layer, which in turn connects to a stack of IP-based layers: TCP, Remote IP, IPSec ESP, Transport IP, and Access Layers. The GSM RR layer is connected to the LAPDm layer, which is then connected to the GSM Baseband layer. The GA-CSR and GSM RR layers are also connected to each other via the GSMGAN-SAP interface. + +Figure 3: MS CS Domain Control plane Architecture diagram showing the stack of protocols and interfaces for a Mobile Station (MS). + +**Figure 3: MS CS Domain Control plane Architecture** + +Figure 3 illustrates the main features of the MS CS Domain Control Plane architecture, which are as follows: + +- The RR-SAP interface to the GSM-MM layer is preserved identically for both GSM and GAN access. +- An access mode switch is provided to switch between GERAN/UTRAN and GAN A/Gb modes. +- GA-CSR peers with GSM-RR to provide coordination for roving and handover. + +### 6.1.2 CS Domain - User Plane + +#### 6.1.2.1 CS Domain - User Plane - GAN Architecture + +The GAN protocol architecture in support of CS domain user plane is illustrated figure 4. + +![Figure 4: Up CS Domain User Plane Protocol Architecture diagram showing the protocol stack for MS, Generic IP Network, GANC, and MSC.](a734898ce18e972938949637c32a34f4_img.jpg) + +The diagram illustrates the Up CS Domain User Plane Protocol Architecture across four entities: MS (Mobile Station), Generic IP Network, GANC (GAN Controller), and MSC (Mobile Switching Center). The architecture is shown in layers, with data flow indicated by arrows. + +- MS (Mobile Station):** Contains layers: Codec/Rate Adaptation, RTP/UDP, Remote IP, IPSec ESP, Transport IP, and Access Layers. +- Generic IP Network:** Contains layers: Transport IP and Access Layers. +- GANC (GAN Controller):** Contains layers: Transcoding (if necessary), Codec/Rate Adaptation, RTP/UDP, Remote IP, IPSec ESP, Transport IP, Access Layers, Speech Bearer, and Physical Layers. +- MSC (Mobile Switching Center):** Contains layers: IWF (if necessary), Speech Bearer, and Physical Layers. + +The **Up Interface** is a vertical dashed line between the MS and the GANC. The **A** interface is a vertical dashed line between the GANC and the MSC. + +Connections: + +- MS layers connect to Generic IP Network layers. +- Generic IP Network layers connect to GANC layers. +- GANC layers connect to MSC layers via the A interface. + +Figure 4: Up CS Domain User Plane Protocol Architecture diagram showing the protocol stack for MS, Generic IP Network, GANC, and MSC. + +**Figure 4: Up CS Domain User Plane Protocol Architecture** + +The main features of the CS domain user plane of the Up interface are as follows: + +- The underlying Access Layers and Transport IP layer provides the generic connectivity between the MS and the GANC. +- The IPsec layer provides encryption and data integrity. +- CS domain user plane is transported over RTP/UDP between MS and GANC. +- Support for AMR FR codec, as specified in 3GPP TS 26.071 [7], is mandatory when operating in GAN A/Gb mode, with support for other codecs being optional. +- CS-data is transported over RTP/UDP, by defining a new RTP frame format to carry the TAF-TRAU (V.110-like) frames over RTP. +- TTY is transported using CTM over GSM codec over RTP/UDP. +- When using a TDM-based A-interface, the GANC re-frames and transcodes the CS domain user plane between RTP/UDP speech bearer and the speech bearers over the A-interface. Re-framing and transcoding is not required when the voice call uses AMR over an IP-based A-interface. + +NOTE: RTP redundancy is not used over the Up interface when the voice call uses an IP-based A-interface. + +## 6.2 PS Domain (GAN A/Gb mode) + +### 6.2.1 PS Domain - GAN Architecture + +#### 6.2.1.1 PS Domain - Control Plane - GAN Architecture + +The GAN architecture in support of PS Domain Control Plane is illustrated in figure 5. + +![Figure 5: Up PS Domain Control Plane Architecture diagram showing the protocol stack and interfaces between MS, Generic IP Network, GANC, and SGSN.](e636d7ccca0ad14c6b95201404324823_img.jpg) + +The diagram illustrates the Up PS Domain Control Plane Architecture. It shows the protocol stacks for the MS (Mobile Station), Generic IP Network, GANC (GAN Controller), and SGSN (Serving GPRS Support Node). The MS stack includes Upper Layers, LLC, GA-PSR, GA-RC, TCP, Remote IP, IPSec ESP, Transport IP, and Access Layers. The Generic IP Network contains Transport IP and Access Layers. The GANC stack includes Relay, GA-PSR, GA-RC, TCP, Remote IP, IPSec ESP, Transport IP, Access Layers, BSSGP, Network Service, and Physical. The SGSN stack includes Upper Layers, LLC, BSSGP, Network Service, and Physical. The Up Interface is shown between the MS and the Generic IP Network, and the Gb interface is shown between the GANC and the SGSN. + +Figure 5: Up PS Domain Control Plane Architecture diagram showing the protocol stack and interfaces between MS, Generic IP Network, GANC, and SGSN. + +**Figure 5: Up PS Domain Control Plane Architecture** + +The main features of the Up interface for the PS domain control plane are as follows: + +- The underlying Access Layers and Transport IP layer provides the generic connectivity between the MS and the GANC. +- The IPsec layer provides encryption and data integrity. +- TCP provides reliable transport for the GA-PSR between MS and GANC. +- The GA-RC manages the IP connection, including the GAN registration procedures. +- The GA-PSR protocol performs functionality equivalent to the GPRS-RLC protocol. The concept of a TBF is replaced by mechanisms to manage an IP connection between MS and GANC. + +NOTE: No QoS can be assured when utilizing the GA-PSR transport channel. + +- Protocols, such as LLC and above, are carried transparently between the MS and CN. +- The GANC terminates the GA-PSR protocol and inter-works it to the Gb-interface using BSSGP. + +#### 6.2.1.2 PS Domain - User Plane - GAN Architecture + +The GAN architecture for PS Domain User Plane is illustrated in figure 6. + +![Figure 6: Up PS Domain User Plane Protocol Architecture diagram showing the protocol stack across MS, Generic IP Network, GANC, and SGSN.](a24e89a6fe9bb70c83f8bf5202baba95_img.jpg) + +The diagram illustrates the Up PS Domain User Plane Protocol Architecture across four main entities: MS (Mobile Station), Generic IP Network, GANC (GAN Controller), and SGSN (Serving GPRS Support Node), with a connection 'To GGSN'. + +- MS Protocol Stack:** IP, SNDPCP, LLC, GA-PSR, UDP, Remote IP, IPSec ESP, Transport IP, Access Layers. +- Generic IP Network:** Contains Transport IP and Access Layers. +- GANC Protocol Stack:** + - Relay:** GA-PSR, UDP, Remote IP, IPSec ESP. + - Network Service:** Transport IP. + - Physical:** Access Layers. + - BSSGP:** Interconnects GA-PSR and Network Service. +- SGSN Protocol Stack:** SNDPCP, LLC, BSSGP, Network Service, Physical. + +**Interfaces:** + +- Up Interface:** Dashed vertical line between MS and Generic IP Network. +- Gb Interface:** Dashed vertical line between GANC and SGSN. + +**Data Flow:** + +- IP, SNDPCP, and LLC layers are carried transparently from MS to SGSN. +- GA-PSR is terminated at the GANC Relay. +- UDP, Remote IP, and IPSec ESP are carried through the GANC Relay. +- Transport IP is terminated at the GANC Network Service. +- Access Layers are terminated at the GANC Physical layer. +- BSSGP is used within the GANC to interwork GA-PSR and Network Service. + +Figure 6: Up PS Domain User Plane Protocol Architecture diagram showing the protocol stack across MS, Generic IP Network, GANC, and SGSN. + +**Figure 6: Up PS Domain User Plane Protocol Architecture** + +The main features of the Up interface for PS domain user plane are as follows: + +- The underlying Access Layers and Transport IP layer provides the generic connectivity between the MS and the GANC. +- The IPsec layer provides encryption and data integrity. +- The GA-PSR operates between the MS to the GANC transporting the upper layer payload (i.e. user plane data) across the Up interface. +- Protocols and data, such as LLC and above, are carried transparently between the MS and CN. +- The GANC terminates the GA-PSR protocol and inter-works it to the Gb-interface using BSSGP. + +### 6.2.2 PS Domain - MS Architecture + +The MS architecture for the PS domain is illustrated in more detail in figure 7. + +![Figure 7: MS PS Domain Architecture diagram showing the protocol stack and interfaces for a Mobile Station (MS) in the PS domain.](7d3d5fb5d09c0cd35a9d637be241651e_img.jpg) + +The diagram illustrates the MS PS Domain Architecture. At the top, three application blocks (App, IP, SNDPCP) and two management blocks (GMM, SMS) are shown. The App block is connected to IP, which is connected to SNDPCP. GMM and SMS are connected to a central Logical Link Control (LLC) block. The LLC block is connected to two Service Access Point (SAP) interfaces: GMMRR-SAP and GRR-SAP. These SAPs are connected to an Access Mode switch. The Access Mode switch is connected to a GPRS SAP (GANGPRS-SAP). Below the GANGPRS-SAP, the architecture splits into two paths. The left path consists of GA-PSR, GA-RC, TCP/UDP, Remote IP, IPSec ESP, Transport IP, and Access Layers. The right path consists of GPRS RLC, GPRSGAN-SAP, MAC, and GSM Baseband. There are also connections between GA-PSR and GPRS RLC, and between GA-RC and GPRSGAN-SAP. + +Figure 7: MS PS Domain Architecture diagram showing the protocol stack and interfaces for a Mobile Station (MS) in the PS domain. + +**Figure 7: MS PS Domain Architecture** + +Figure 7 illustrates the main features of the MS PS Domain architecture, which are as follows: + +- The GRR-SAP to the GPRS-LLC layer is preserved. +- The GMMRR-SAP interface to the GPRS-GMM layer is preserved. +- An access mode switch is provided to switch between GPRS and GAN A/Gb modes. +- GA-PSR peers with GPRS-RLC to provide coordination for roving and PS handover. + +## 6.3 CS Domain (GAN Iu mode) + +### 6.3.1 CS Domain - Control Plane + +#### 6.3.1.1 CS Domain - Control Plane - GAN Architecture + +The GAN Iu mode architecture in support of the CS Domain control plane is illustrated in figure 7a. + +![Figure 7a: CS Domain Control Plane Architecture diagram showing the protocol stack and interfaces between MS, Generic IP Network, GANC, and MSC.](86b4670fc1a5a694821ee92b99c1209a_img.jpg) + +The diagram illustrates the CS Domain Control Plane Architecture. It shows four main entities: MS (Mobile Station), Generic IP Network, GANC (GAN Controller), and MSC (Mobile Switching Center). The MS and GANC are connected via the Up interface through the Generic IP Network. The GANC and MSC are connected via the Iu-cs interface. The protocol stacks are as follows: + +- MS Stack:** CC/SS/SMS, MM, GA-RRC, GA-RC, TCP, Remote IP, IPsec ESP, Transport IP, Access Layers. +- Generic IP Network:** Transport IP, Access Layers. +- GANC Stack:** GA-RRC, GA-RC, TCP, Remote IP, IPsec ESP, Transport IP, Access Layers, Signalling Transport Layers (TS 25.412), RANAP. +- MSC Stack:** CC/SS/SMS, MM, RANAP, Signalling Transport Layers (TS 25.412). + +Arrows indicate the flow of signaling and data between the layers and across the interfaces. The Up interface connects the MS to the GANC via the Generic IP Network. The Iu-cs interface connects the GANC to the MSC. + +Figure 7a: CS Domain Control Plane Architecture diagram showing the protocol stack and interfaces between MS, Generic IP Network, GANC, and MSC. + +**Figure 7a: CS Domain Control Plane Architecture** + +The main features of the GAN Iu mode CS domain control plane architecture are as follows: + +- The underlying Access Layers and Transport IP layer provides the generic connectivity between the MS and the GANC. +- The IPsec layer provides encryption and data integrity between the MS and GANC. +- The Remote IP layer is the 'inner' IP layer for IPsec tunnel mode and is used by the MS to be addressed by the GANC. The Remote IP layer is configured during the IPsec connection establishment. +- A single TCP connection is used to provide reliable transport for both the GA-RC and GA-RRC signaling between the MS and GANC. The TCP connection is managed by GA-RC and is transported using the Remote IP layer. +- NAS protocols, such as MM and above, are carried transparently between the MS and MSC. +- The Generic Access Resource Control (GA-RC) protocol manages the Up session, including the GAN discovery and registration procedures. +- The Generic Access Radio Resource Control (GA-RRC) protocol performs functionality equivalent to the UTRAN RRC protocol, using the underlying Up session managed by the GA-RC. Note that GA-RRC includes both CS service and PS service-related signaling messages. +- The GANC terminates the CS-related GA-RRC protocol and inter-works it to the RANAP protocol over the Iu-cs interface. +- The Iu-cs signalling transport layer options (both ATM and IP-based) are defined in TS 25.412 [47]. + +#### 6.3.1.2 CS Domain - Control Plane - MS Architecture + +The MS architecture for the CS domain control plane is illustrated in figure 7b. The MS architecture illustrates support for both GAN A/Gb mode and GAN Iu mode. + +![Figure 7b: MS CS Domain Control Plane Architecture diagram. The diagram shows a layered architecture for the control plane. At the top, Connection Management (CM) contains CC, SS, and SMS. These connect to the MM layer via MMCC, MMSS, and MMSMS interfaces. The MM layer connects to an Access Mode Switch via RR (UTRAN) and RR (GERAN) interfaces. The Access Mode Switch connects to three RRC entities: UTRAN RRC, GA-RRC/GA-CSR/GA-RC, and GERAN RRC. The UTRAN RRC connects to UTRAN RLC/MAC and then to UTRAN Baseband. The GA-RRC/GA-CSR/GA-RC connects to TCP/IP, which connects to an IPSec Tunnel, which connects to Access Layers. The GERAN RRC connects to LAPDm and then to GERAN Baseband. External interfaces are shown: 'to/from GERAN RRC' for the UTRAN RRC and 'to/from UTRAN RRC' for the GERAN RRC.](7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg) + +Figure 7b: MS CS Domain Control Plane Architecture diagram. The diagram shows a layered architecture for the control plane. At the top, Connection Management (CM) contains CC, SS, and SMS. These connect to the MM layer via MMCC, MMSS, and MMSMS interfaces. The MM layer connects to an Access Mode Switch via RR (UTRAN) and RR (GERAN) interfaces. The Access Mode Switch connects to three RRC entities: UTRAN RRC, GA-RRC/GA-CSR/GA-RC, and GERAN RRC. The UTRAN RRC connects to UTRAN RLC/MAC and then to UTRAN Baseband. The GA-RRC/GA-CSR/GA-RC connects to TCP/IP, which connects to an IPSec Tunnel, which connects to Access Layers. The GERAN RRC connects to LAPDm and then to GERAN Baseband. External interfaces are shown: 'to/from GERAN RRC' for the UTRAN RRC and 'to/from UTRAN RRC' for the GERAN RRC. + +**Figure 7b: MS CS Domain Control Plane Architecture** + +Figure 7b illustrates the main features of the MS CS domain control plane architecture, which are as follows: + +- The UTRAN RR-SAP interface to the MM layer is preserved identically for both UTRAN and GAN Iu mode access. +- The GERAN RR-SAP interface to the MM layer is preserved identically for both GERAN and GAN A/Gb mode access. +- An access mode switch is provided to switch between GERAN/UTRAN and GAN modes. +- GA-RRC (GAN Iu mode) peers with UTRAN-RRC and GERAN-RRC to provide coordination for roving and handover. +- GA-CSR (GAN A/Gb mode) peers with UTRAN-RRC and GERAN-RRC to provide coordination for roving and handover. + +### 6.3.2 CS Domain - User Plane + +#### 6.3.2.1 CS Domain - User Plane - GAN Architecture + +The GAN Iu mode protocol architecture in support of the CS domain user plane is illustrated figure 7c. + +![Figure 7c: CS Domain User Plane Protocol Architecture diagram showing the protocol stack across MS, Generic IP Network, GANC, and MSC entities.](2734e7f9be3e1dc046f14be2e6c9a085_img.jpg) + +The diagram illustrates the CS Domain User Plane Protocol Architecture across four entities: MS (Mobile Station), Generic IP Network, GANC (GAN Controller), and MSC (Mobile Switching Center). The architecture is divided into two main interfaces: Up (between MS and GANC) and Iu-cs (between GANC and MSC). + +**MS Protocol Stack:** + +- CS User Data +- RTP +- UDP +- Remote IP +- IPSec ESP +- Transport IP +- Access Layers + +**Generic IP Network:** Contains nested boxes for Transport IP and Access Layers. + +**GANC Protocol Stack:** + +- Interworking +- RTP +- Iu UP +- UDP +- Remote IP +- IPSec ESP +- Transport IP +- Access Layers +- Transport Network Control and Data Transport Layers (TS 25.414) + +**MSC Protocol Stack:** + +- CS User Data +- Iu UP +- Transport Network Control and Data Transport Layers (TS 25.414) + +**Interfaces:** + +- Up:** The interface between MS and GANC, showing the flow of data through the Generic IP Network. +- Iu-cs:** The interface between GANC and MSC. + +Figure 7c: CS Domain User Plane Protocol Architecture diagram showing the protocol stack across MS, Generic IP Network, GANC, and MSC entities. + +**Figure 7c: CS Domain User Plane Protocol Architecture** + +The main features of the GAN CS domain user plane architecture are as follows: + +- The underlying Access Layers and Transport IP layer provides the generic connectivity between the MS and the GANC. +- The IPsec layer provides encryption and data integrity. +- CS domain user plane is transported over RTP/UDP between MS and GANC. +- Support for AMR FR codec, as specified in 3GPP TS 26.071 [7], is mandatory when operating in GAN Iu mode, with support for other codecs being optional. +- CS-data is transported over RTP/UDP, by defining a new RTP frame format to carry the TAF-TRAU (V.110-like) frames over RTP. +- TTY is transported using CTM over GSM codec over RTP/UDP. +- The GANC provides interworking between RTP/UDP and the circuit switched bearers over the Iu-cs interface. +- The GANC supports the Iu User Plane (Iu UP) protocol. Each Iu UP protocol instance may operate in either transparent or support modes, as described in 25.415 [50]; the mode choice is indicated to the GANC by the MSC using RANAP. +- The Iu-cs data transport layers (both ATM and IP-based) and associated transport network control options are defined in 25.414 [49]. + +#### 6.3.2.2 CS Domain - User Plane - MS Architecture + +The MS architecture for the CS domain user plane is illustrated in figure 7d. The MS architecture illustrates support for both GAN A/Gb mode and GAN Iu mode. + +![Block diagram of MS CS Domain User Plane Architecture showing Audio I/O, Filters/ADC/DAC, AMR Audio Processing, CS Data, CS Data Processing, Access Mode Switch, and various baseband and network layers.](e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg) + +The diagram illustrates the MS CS Domain User Plane Architecture. At the top, 'Audio I/O' is connected to 'Filters/ADC/DAC', which in turn connects to 'AMR Audio Processing'. To the right, 'CS Data' connects to 'CS Data Processing'. Both 'AMR Audio Processing' and 'CS Data Processing' connect to a central 'Access Mode Switch'. The 'Access Mode Switch' has three output paths: 1) The left path, labeled 'AMR' and 'CSD', connects to 'UTRAN RLC/MAC' and then to 'UTRAN Baseband'. 2) The middle path, also labeled 'AMR' and 'CSD', connects directly to 'GERAN Baseband'. 3) The right path, labeled 'AMR' and 'CSD', connects to 'RFC 3267 AMR Processing', which then connects to 'RTP/UDP/IP', 'IPSec Tunnel', and finally 'Access Layers'. + +Block diagram of MS CS Domain User Plane Architecture showing Audio I/O, Filters/ADC/DAC, AMR Audio Processing, CS Data, CS Data Processing, Access Mode Switch, and various baseband and network layers. + +**Figure 7d: MS CS Domain User Plane Architecture** + +Figure 7d illustrates the main features of the MS CS domain user plane architecture, which are as follows: + +- An access mode switch is provided to switch between GERAN/UTRAN and GAN modes; i.e., to route CS user plane data—either speech or circuit switched data—to the active access subsystem. + +## 6.4 PS Domain (GAN Iu mode) + +### 6.4.1 PS Domain - Control Plane + +#### 6.4.1.1 PS Domain - Control Plane - GAN Architecture + +The GAN Iu mode architecture in support of the PS Domain Control Plane is illustrated in figure 7e. + +![Figure 7e: PS Domain Control Plane Architecture diagram showing the protocol stack for MS, GANC, and SGSN across Up and Iu-ps interfaces.](e29665b8abcea967ef289c6aff07ae4c_img.jpg) + +The diagram illustrates the PS Domain Control Plane Architecture across three main entities: MS (Mobile Station), GANC (GAN Controller), and SGSN (Serving GPRS Support Node), separated by a Generic IP Network. + +- MS (Mobile Station):** Contains a protocol stack with layers: GMM/SM/SMS, GA-RRC, GA-RC (dashed line), TCP, Remote IP, IPSec ESP, Transport IP, and Access Layers. +- Generic IP Network:** Contains two boxes labeled 'Up' and 'Access Layers'. The 'Up' box is connected to the MS's Transport IP layer. The 'Access Layers' box is connected to the MS's Access Layers and the GANC's Access Layers. +- GANC (GAN Controller):** Contains a protocol stack with layers: GA-RRC, GA-RC (dashed line), TCP, Remote IP, IPSec ESP, Transport IP, and Access Layers. To the right of these layers is a large box labeled 'Signalling Transport Layers (TS 25.412)'. Above this box is the 'RANAP' layer. The GANC is connected to the MS via the 'Up' interface and to the SGSN via the 'Iu-ps' interface. +- SGSN (Serving GPRS Support Node):** Contains a protocol stack with layers: GMM/SM/SMS, RANAP, and Signalling Transport Layers (TS 25.412). The SGSN is connected to the GANC via the 'Iu-ps' interface. + +Arrows indicate the flow of data and signaling between the layers and interfaces. + +Figure 7e: PS Domain Control Plane Architecture diagram showing the protocol stack for MS, GANC, and SGSN across Up and Iu-ps interfaces. + +**Figure 7e: PS Domain Control Plane Architecture** + +The main features of the GAN PS domain control plane architecture are as follows: + +- The underlying Access Layers and Transport IP layer provides the generic connectivity between the MS and the GANC. +- The IPsec layer provides encryption and data integrity. +- TCP provides reliable transport for the GA-RRC between MS and GANC. +- The GA-RC manages the IP connection, including the GAN registration procedures. +- The Generic Access Radio Resource Control (GA-RRC) protocol performs functionality equivalent to the UTRAN RRC protocol, using the underlying Up session managed by the GA-RC. Note that GA-RRC includes both CS service and PS service-related signaling messages. +- The GANC terminates the GA-RRC protocol and inter-works it to the RANAP protocol over the Iu-ps interface. +- NAS protocols, such as for GMM, SM and SMS, are carried transparently between the MS and SGSN. +- The Iu-ps signalling transport layer options (both ATM and IP-based) are defined in 25.412 [47]. + +#### 6.4.1.2 PS Domain - Control Plane - MS Architecture + +The MS architecture for the PS domain control plane is illustrated in figure 7f. The MS architecture illustrates support for both GAN A/Gb mode and GAN Iu mode. + +![Figure 7f: MS PS Domain Control Plane Architecture diagram. The diagram shows a layered architecture for the Mobile Station (MS) control plane. At the top, three boxes represent RABM (UMTS), SM, and SMS. These connect to an MM (Mobility Management) layer via interfaces GMMRABM, GMMMSM, and PMMSMS respectively. The MM layer connects to an LLC (Logical Link Control) layer via LLGMM and LLSMS interfaces. The LLC layer connects to an Access Mode Switch via interfaces RABMAS, GMMAS, GRR, and GMMRR. The Access Mode Switch has three output paths: 1) UTRAN RRC, which connects to UTRAN RLC/MAC and then UTRAN Baseband; 2) GA-RRC/GA-PSR/GA-RC, which connects to TCP/IP, then an IPSec Tunnel, then Access Layers; 3) GERAN RRC, which connects to GERAN RLC/MAC and then GERAN Baseband. The UTRAN RRC and GA-RRC/GA-PSR/GA-RC interfaces are labeled with RABMAS and GMMAS. The GERAN RRC interfaces are labeled with GRR and GMMRR. There are also labels 'to/from GERAN RRC' and 'to/from UTRAN RRC' on the left and right sides of the Access Mode Switch respectively.](759c7d62402f0b4651ddce292be5bdef_img.jpg) + +Figure 7f: MS PS Domain Control Plane Architecture diagram. The diagram shows a layered architecture for the Mobile Station (MS) control plane. At the top, three boxes represent RABM (UMTS), SM, and SMS. These connect to an MM (Mobility Management) layer via interfaces GMMRABM, GMMMSM, and PMMSMS respectively. The MM layer connects to an LLC (Logical Link Control) layer via LLGMM and LLSMS interfaces. The LLC layer connects to an Access Mode Switch via interfaces RABMAS, GMMAS, GRR, and GMMRR. The Access Mode Switch has three output paths: 1) UTRAN RRC, which connects to UTRAN RLC/MAC and then UTRAN Baseband; 2) GA-RRC/GA-PSR/GA-RC, which connects to TCP/IP, then an IPSec Tunnel, then Access Layers; 3) GERAN RRC, which connects to GERAN RLC/MAC and then GERAN Baseband. The UTRAN RRC and GA-RRC/GA-PSR/GA-RC interfaces are labeled with RABMAS and GMMAS. The GERAN RRC interfaces are labeled with GRR and GMMRR. There are also labels 'to/from GERAN RRC' and 'to/from UTRAN RRC' on the left and right sides of the Access Mode Switch respectively. + +**Figure 7f: MS PS Domain Control Plane Architecture** + +Figure 7f illustrates the main features of the MS PS domain control plane architecture, which are as follows: + +- The UTRAN RABMAS-SAP and GMMAS-SAP interfaces to the MM layer are preserved identically for both UTRAN and GAN Iu mode access. +- The GERAN GRR-SAP and GMMRR-SAP interfaces to the MM layer are preserved identically for both GERAN and GAN A/Gb mode access. +- An access mode switch is provided to switch between GERAN/UTRAN and GAN modes. +- GA-RRC (GAN Iu mode) peers with UTRAN-RRC and GERAN-RRC to provide coordination for roving and handover. +- GA-PSR (GAN A/Gb mode) peers with UTRAN-RRC and GERAN-RRC to provide coordination for roving and handover. + +### 6.4.2 PS Domain - User Plane + +#### 6.4.2.1 PS Domain - User Plane - GAN Architecture + +The GAN Iu mode architecture for the PS Domain User Plane is illustrated in figure 7g. + +![Figure 7g: PS Domain User Plane Protocol Architecture diagram showing data flow from MS to SGSN via GANC across Up and Iu-ps interfaces.](f0a97d0d3818a253c1d2a009966081b1_img.jpg) + +The diagram illustrates the PS Domain User Plane Protocol Architecture. It shows the flow of data from the MS (Mobile Station) to the SGSN (Serving GPRS Support Node) via the GANC (GAN Controller) across two interfaces: Up and Iu-ps. + +**MS Protocol Stack (Left):** + +- PS User Data +- GA-RRC +- UDP +- Remote IP +- IPSec ESP +- Transport IP +- Access Layers + +**Generic IP Network (Middle):** + +- Transport IP +- Access Layers + +**GANC Protocol Stack (Right):** + +- GA-RRC +- UDP +- Remote IP +- IPSec ESP +- Transport IP +- Access Layers +- Data Transport Lower Layers (TS 25.414) + +**SGSN Protocol Stack (Far Right):** + +- GTP-U +- UDP +- IP +- Data Transport Lower Layers (TS 25.414) + +**Interfaces:** + +- Up:** The interface between the MS and the GANC. Data flows from the MS's GA-RRC layer through the Generic IP Network to the GANC's GA-RRC layer. +- Iu-ps:** The interface between the GANC and the SGSN. Data flows from the GANC's GTP-U layer through the SGSN's GTP-U layer to the To GGSN. + +Figure 7g: PS Domain User Plane Protocol Architecture diagram showing data flow from MS to SGSN via GANC across Up and Iu-ps interfaces. + +**Figure 7g: PS Domain User Plane Protocol Architecture** + +The main features of the GAN PS domain user plane architecture are as follows: + +- The underlying Access Layers and Transport IP layer provides the generic connectivity between the MS and the GANC. +- The IPsec layer provides encryption and data integrity. +- The GA-RRC protocol operates between the MS to the GANC transporting the upper layer payload (i.e. user plane data) across the Up interface. +- PS user data is carried transparently between the MS and CN. +- The GANC terminates the GA-RRC protocol and inter-works it to the Iu-ps interface using GTP-U. + +#### 6.4.2.2 PS Domain - User Plane - MS Architecture + +The MS architecture for the PS domain user plane is illustrated in figure 7h. + +![Diagram of MS PS Domain User Plane Architecture showing layers from IP down to UTRAN and GERAN basebands.](7d2d1d3870cd224c4430d19334557716_img.jpg) + +The diagram illustrates the MS PS Domain User Plane Architecture. At the top is the IP layer, which connects to the PS User Plane Routing Service. Below this service, the architecture branches into two main paths. The left path goes through a PDCP SAP to an Access Mode Switch. The right path goes through an SNDCP layer (which includes four QoS levels: QoS4, QoS3, QoS2, and QoS1), then an LLC layer, and then a GRR SAP to the same Access Mode Switch. From the Access Mode Switch, the architecture further branches into three paths: + 1) A UTRAN path consisting of a PDCP layer, a UTRAN RLC/MAC layer, and a UTRAN Baseband. + 2) A GAN path consisting of a PDCP SAP, a GA-RRC/GA-PSR layer, a UDP/IP layer, an IPSec Tunnel, Access Layers, and finally a GERAN Baseband. + 3) A GERAN path consisting of a GRR SAP, a GERAN RLC/MAC layer, and a GERAN Baseband. + +Diagram of MS PS Domain User Plane Architecture showing layers from IP down to UTRAN and GERAN basebands. + +**Figure 7h: MS PS Domain User Plane Architecture** + +Figure 7h illustrates the main features of the MS PS domain user plane architecture, which are as follows: + +- The UTRAN PDCP-SAP interface to the PS user plane upper layers is preserved identically for both UTRAN and GAN Iu mode access. +- The GERAN GRR-SAP interface to the PS user plane upper layers is preserved identically for both GERAN and GAN A/Gb mode access. +- An access mode switch is provided to switch between GERAN/UTRAN and GAN modes; i.e., to route PS user plane data to the active access subsystem. + +# 7 Management functionality + +## 7.1 State diagram for Generic Access + +![State diagram for Generic Access in the MS. The diagram shows three main modes: GERAN/UTRAN/E-UTRAN Mode, A/Gb Mode GAN (GA-RC REGISTERED), and Iu Mode GAN (GA-RC REGISTERED). GERAN/UTRAN/E-UTRAN Mode has two states: GA-RC DEREGISTERED and GA-RC REGISTERED. Transitions between them are 'Successful Registration' and 'Autonomous transition, Deregistration or Loss of IPSec connection'. A/Gb Mode GAN has two sub-states: GA-CSR (IDLE and DEDICATED) and GA-PSR (STANDBY and ACTIVE). Transitions between IDLE and DEDICATED are 'GA-CSR Connection Establishment' and 'GA-CSR Connection Release'. Transitions between STANDBY and ACTIVE are 'GA-PSR Transport Channel Activation' and 'GA-PSR Transport Channel De-Activation'. Iu Mode GAN has two sub-states: GA-RRc (CS Domain) (GA-RRc-IDLE and GA-RRc-CONNECTED) and GA-RRc (PS Domain) (GA-RRc-IDLE and GA-RRc-CONNECTED). Transitions between IDLE and CONNECTED are 'GA-RRc (Domain) Connection Establishment' and 'GA-RRc (Domain) Connection Release'. External transitions include 'Switch of serving RR from GERAN/UTRAN to GAN A/Gb mode', 'Switch of serving RR from GAN A/Gb mode to GERAN/UTRAN/E-UTRAN or Handover from GAN A/Gb mode to GERAN/UTRAN or PS Handover from GAN A/Gb mode to GERAN/UTRAN', 'Autonomous transition, Deregistration or Loss of IPSec connection', 'Switch serving RR from GERAN/UTRAN/E-UTRAN to GAN Iu mode (see Note 1)', and 'Switch serving RR from GAN Iu mode to GERAN/UTRAN/E-UTRAN (see Note 2)'.](3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg) + +State diagram for Generic Access in the MS. The diagram shows three main modes: GERAN/UTRAN/E-UTRAN Mode, A/Gb Mode GAN (GA-RC REGISTERED), and Iu Mode GAN (GA-RC REGISTERED). GERAN/UTRAN/E-UTRAN Mode has two states: GA-RC DEREGISTERED and GA-RC REGISTERED. Transitions between them are 'Successful Registration' and 'Autonomous transition, Deregistration or Loss of IPSec connection'. A/Gb Mode GAN has two sub-states: GA-CSR (IDLE and DEDICATED) and GA-PSR (STANDBY and ACTIVE). Transitions between IDLE and DEDICATED are 'GA-CSR Connection Establishment' and 'GA-CSR Connection Release'. Transitions between STANDBY and ACTIVE are 'GA-PSR Transport Channel Activation' and 'GA-PSR Transport Channel De-Activation'. Iu Mode GAN has two sub-states: GA-RRc (CS Domain) (GA-RRc-IDLE and GA-RRc-CONNECTED) and GA-RRc (PS Domain) (GA-RRc-IDLE and GA-RRc-CONNECTED). Transitions between IDLE and CONNECTED are 'GA-RRc (Domain) Connection Establishment' and 'GA-RRc (Domain) Connection Release'. External transitions include 'Switch of serving RR from GERAN/UTRAN to GAN A/Gb mode', 'Switch of serving RR from GAN A/Gb mode to GERAN/UTRAN/E-UTRAN or Handover from GAN A/Gb mode to GERAN/UTRAN or PS Handover from GAN A/Gb mode to GERAN/UTRAN', 'Autonomous transition, Deregistration or Loss of IPSec connection', 'Switch serving RR from GERAN/UTRAN/E-UTRAN to GAN Iu mode (see Note 1)', and 'Switch serving RR from GAN Iu mode to GERAN/UTRAN/E-UTRAN (see Note 2)'. + +**Figure 8: State diagram for Generic Access in the MS** + +Notes: + +1. The following cases are possible when switching the serving RR to GAN Iu mode: + - a. Transition to GA-RRc-IDLE for both CS and PS domains (i.e., idle mode transition from GERAN/UTRAN/E-UTRAN) + - b. Transition to GA-RRc-IDLE (PS domain) and GA-RRc-CONNECTED (CS domain) (i.e., due to CS handover from GERAN/UTRAN) + - c. Transition to GA-RRc-IDLE (CS domain) and GA-RRc-CONNECTED (PS domain) (i.e., due to PS handover from GERAN/UTRAN) + - d. Transition to GA-RRc-CONNECTED (CS domain) and GA-RRc-CONNECTED (PS domain) (i.e., due to combined CS handover and PS handover from GERAN/UTRAN) +2. The following cases are possible when switching the serving RR from GAN Iu mode: + - a. Transition from GA-RRc-IDLE for both CS and PS domains (i.e., idle mode transition to GERAN/UTRAN/E-UTRAN) + - b. Transition from GA-RRc-IDLE (PS domain) and GA-RRc-CONNECTED (CS domain) (i.e., due to CS handover to GERAN/UTRAN). + - c. Transition from GA-RRc-IDLE (CS domain) and GA-RRc-CONNECTED (PS domain) (i.e., due to PS handover to GERAN/UTRAN) + +- d. Transition from GA-RRC-CONNECTED (CS domain) and GA-RRC-CONNECTED (PS domain) (i.e., due to combined CS handover and PS handover to GERAN/UTRAN) +3. There is no requirement for the MS to support both GAN Iu mode and GAN A/Gb mode. + +## 7.2 GA-RC (Generic Access Resource Control) + +### 7.2.1 General + +The GA-RC protocol provides a resource management layer, with the following functions: + +- discovery and Registration with GANC, including GAN mode selection (GAN A/Gb mode or GAN Iu mode); +- registration Update with GANC; +- application level keep-alive with GANC; and +- support for identification of the AP being used for GAN access. + +### 7.2.2 States of the GA-RC sub-layer + +The GA-RC sub-layer in the MS can be in one of two states - GA-RC-DEREGISTERED or GA-RC-REGISTERED - as illustrated in figure 8. + +In the GA-RC-DEREGISTERED state, the MS may be in a GAN coverage area; however, the MS has not registered successfully with the GANC and cannot exchange GA-CSR and GA-PSR signalling messages (GAN A/Gb mode) or GA-RRC messages (GAN Iu mode) with the GANC. The MS may initiate the GAN Registration procedure when in the GA-RC-DEREGISTERED state. The MS returns to GA-RC-DEREGISTERED state on loss of TCP or IPsec connection. + +In the GAN A/Gb mode GA-RC-REGISTERED state, the MS is registered with a GANC, has an IPsec and an TCP connection established to the Serving GANC, through which the MS may exchange GA-CSR or GA-PSR signaling messages with the GANC, and the SAP between the GA-CSR and MM entity and the GA-PSR and the GMM entity are not active. In the GA-RC-REGISTERED state, the MS may be camped on GERAN or UTRAN, active in GERAN or UTRAN (e.g. a GSM RR or a UTRAN RRC connection may be established) or may have no GERAN or UTRAN service while still maintaining the registration in the GAN. + +In the GAN Iu mode GA-RC-REGISTERED state, the MS is registered with the Serving GANC. The MS has an IPsec tunnel and a TCP connection established to the Serving GANC through which the MS may exchange GA-RC or GA-RRC signaling messages with the GANC. The SAP between the GA-RRC and MM entity and the GA-RRC and the GMM entity are not active. In the GA-RC-REGISTERED state, the MS may be camped on GERAN or UTRAN, active in GERAN or UTRAN (e.g. a GSM RR or a UTRAN RRC connection may be established) or may have no GERAN or UTRAN service while still maintaining the registration in the GAN. + +## 7.3 GA-CSR (Generic Access Circuit Switched Resources) + +### 7.3.1 General + +The GA-CSR protocol provides a resource management layer, which is equivalent to the GSM-RR and provides the following functions: + +- setup of bearer for CS traffic between the MS and GANC; +- handover support between GERAN and GAN; and +- functions such as GPRS suspension, paging, ciphering configuration, classmark change. + +### 7.3.2 States of the GA-CSR sub-layer + +The GA-CSR sub-layer in the MS can be in two states -GA-CSR-IDLE or GA-CSR-DEDICATED as illustrated in figure 8. + +The MS enters GA-CSR-IDLE state from GA-RC-REGISTERED state, when the MS switches the serving RR entity to GA-CSR and the SAP between the MM and the GA-CSR is activated. Simultaneously, the GA-PSR acquires the control of the RLC GRR and GMMRR SAPs and transitions to GA-PSR- STANDBY state. While the MS remains in GAN A/Gb mode it performs registration Update and application level keep-alive with the GANC as per the GA-RC-REGISTERED state. + +The MS moves from the GA-CSR-IDLE state to the GA-CSR-DEDICATED state when the GA-CSR connection is established and returns to GA-CSR-IDLE state when the GA-CSR connection is released. Upon GA-CSR connection release an indication that no dedicated resources exist is passed to the upper layers. + +The MS may also enter GA-CSR-DEDICATED state from GA-RC-REGISTERED state of GERAN/UTRAN mode when Handover to GAN is being performed. In the same way, the MS enters GA-RC-REGISTERED state of GERAN/UTRAN mode from GA-CSR-DEDICATED when Handover from GAN is being performed. + +## 7.4 GA-PSR (Generic Access Packet Switched Resources) + +The GA-PSR protocol provides the following services: + +- delivery of GPRS signalling, SMS messages over the secure tunnel; +- paging, flow control, GPRS transport channel management; +- PS handover support between GERAN/UTRAN mode and GAN A/Gb mode; and +- transfer of GPRS user plane data. + +The GA-PSR Transport Channel (GA-PSR TC) provides the association between the MS and GANC for the transport of GPRS user data over the Up interface. Given that the GAN user data transport is UDP based, the GA-PSR Transport Channel is associated with corresponding MS and GANC IP addresses and UDP ports used for GPRS user data transfer. The MS and GANC manage the GA-PSR Transport Channel based on the requests for data transfer and the configurable GA-PSR Channel Timer. + +### 7.4.1 States of the GA-PSR sub-layer + +The GA-PSR sub-layer in the MS can be in two states - GA-PSR-STANDBY or GA-PSR-ACTIVE - as illustrated in figure 8. + +- **GA-PSR-STANDBY:** This is the initial/default state of the mobile station in GAN A/Gb mode. The MS is not able to send or receive GPRS user data to and from the GANC. The GA-PSR Transport Channel does not exist when the MS is in GA-PSR-STANDBY state. The GANC or the MS needs to activate the GA-PSR Transport Channel before sending any GPRS user data. When the MS GA-PSR successfully establishes a GA-PSR Transport Channel, it transitions to the GA-PSR-ACTIVE state. +- **GA-PSR-ACTIVE:** The MS is able to send and receive GPRS user data to and from the GANC. The corresponding GA-PSR Transport Channel exists. + +Upon a successful switch to GAN A/Gb mode as a result of move-in, the MS GA-PSR acquires the control of the RLC GRR and GMMRR SAPs, and transitions to GA-PSR-STANDBY state and GA-PSR TC activation may then be triggered. + +After successful GA-PSR TC activation when in GAN A/Gb mode, the MS GA-PSR transitions to GA-PSR-ACTIVE state. The following are the possible triggers for GA-PSR TC activation when the MS is in the GA-PSR-STANDBY state in GAN A/Gb mode: + +- The MS LLC entity initiates the uplink data transfer using LLC SAPI 3, 5, 9 or 11 and the GA-PSR sub-layer is in the GA-PSR-STANDBY state. +- The GANC initiates GA-PSR TC activation; i.e. the MS receives a GA-PSR-ACTIVATE UTC REQ message from the GANC (see sub-clause 8.16.4). + +As described in 3GPP TS 43.129 [44], the MS and GANC establish a GA-PSR TC during the PS handover preparation phase which results in MS enabling the reception of downlink LLC PDUs. Upon a successful switch to GAN A/Gb mode as a result of receiving the PS Handover Command, the MS transitions to GA-PSR-ACTIVE state, the MS GA-PSR acquires the control of the RLC GRR and GMMRR SAPs and enables the transmission of uplink LLC PDUs on the allocated GA-PSR TC. + +Upon the successful GA-PSR TC activation and in parallel with transition to GA-PSR-ACTIVE state, the MS GA-PSR starts the GA-PSR Channel Timer. When the GA-PSR Channel Timer expires, the MS sends a message to the GANC to initiate GA-PSR TC deactivation. Upon successful GA-PSR TC deactivation, the MS GA-PSR transitions to GA-PSR-STANDBY state. + +At any time, while in GAN A/Gb mode, if the serving RR entity is switched to GERAN-RR, UTRAN RRC or E-UTRAN RRC, the GA-PSR is disconnected from GPRS SAPs and the MS enters GERAN/UTRAN/E-UTRAN mode. Simultaneously, the MS will release the associated GA-PSR TC regardless of the GA-PSR Channel Timer status. + +The MS GA-PSR maintains one GA-PSR TC for all active user data flows; i.e. if the GA-PSR is in GA-PSR-ACTIVE state, any uplink user data packet is transferred using the active GA-PSR TC regardless of the associated PFC and LLC SAP. The GA-PSR Channel Timer is restarted whenever any uplink user data packet is sent or downlink user data packet received regardless of the associated PFC and LLC SAP. + +## 7.4a GA-RRC + +### 7.4a.1 General + +The GA-RRC protocol provides a resource management layer which is equivalent to UTRAN-RRC and supports the following functions: + +- setup of transport channels for CS and PS traffic between the MS and GANC; +- CS and PS handover support between GERAN/UTRAN and GAN; +- direct transfer of NAS messages between the MS and the core network; and +- other functions such as CS and PS paging and security configuration. + +### 7.4a.2 States of the GA-RRC sub-layer + +The GA-RRC sub-layer in the MS contains two entities, the CS domain GA-RRC sublayer entity and the PS domain GA-RRC sublayer entity (as illustrated in Figure 8). These entities operate independently and in parallel; e.g., two GA-RRC connections are established in the case of simultaneous CS and PS services, one GA-RRC connection for each domain. + +Each GA-RRC sub-layer entity in the MS can be in one of two states, GA-RRC-IDLE or GA-RRC-CONNECTED as illustrated in figure 8. + +Both the CS GA-RRC sub-layer entity and the PS GA-RRC sublayer entity in the MS enters the GA-RRC-IDLE state when the MS switches the serving RR entity to GA-RRC and the SAP between the NAS and the GA-RRC is activated. This switch may occur only when the GA-RC is in the GA-RC-REGISTERED state. + +The CS/PS GA-RRC sublayer entity in the MS moves from the GA-RRC-IDLE state to the GA-RRC-CONNECTED state when the CS/PS GA-RRC connection is established and returns to the GA-RRC-IDLE state when the CS/PS GA-RRC connection is released. Upon CS/PS GA-RRC connection release, an indication that no dedicated resources exist for the domain is passed to the upper layers. + +The CS/PS GA-RRC sublayer entity in the MS may also enter the GA-RRC-CONNECTED state while in the GA-RC-REGISTERED state in GERAN/UTRAN mode when CS/PS handover to GAN is being performed. + +## 7.5 Security Mechanisms + +GAN supports security mechanisms at different levels and interfaces as depicted in figure 9. + +![Diagram of GAN Security Mechanisms showing the flow of traffic from MS to Application Server through various security layers.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +The diagram illustrates the network architecture and security mechanisms for GAN. The components are: MS (Mobile Station), Generic IP Network, GANC (GAN Controller), Core Network, IP Network, and Application Server. The GANC is connected to the Core Network via RAN<->CN Interfaces. Three security mechanisms are shown as dashed arrows: + +- 1. Up Interface Security: Between MS and GANC. +- 2. MS <-> CN Security: Between MS and Core Network. +- 3. Data Application Security (e.g., HTTPS): Between MS and Application Server. + +Diagram of GAN Security Mechanisms showing the flow of traffic from MS to Application Server through various security layers. + +**Figure 9: GAN Security Mechanisms** + +1. The security mechanisms over the Up interface protect signalling, voice and data traffic flows between the MS and the GANC from unauthorized use, data manipulation and eavesdropping; i.e. authentication, encryption and data integrity mechanisms are supported. +2. Authentication of the subscriber by the core network occurs between the MSC/VLR or SGSN and the MS and is transparent to the GANC - however, there is a cryptographic binding between the MS-CN authentication and the MS-GANC authentication to prevent man in the middle attacks. GPRS ciphering is the standard LLC layer ciphering that operates between the MS and the SGSN (not applicable to GAN Iu mode). These mechanisms are out of scope of the present document. +3. Additional application level security mechanisms may be employed in the PS domain to secure the end-to-end communication between the MS and the application server. For example, the MS may run the HTTP protocol over an SSL session for secure web access. These mechanisms are out of scope of the present document. + +All signalling traffic and user-plane traffic sent between MS and GANC over the Up interface is protected by an IPsec tunnel between the MS and GANC-SEGW, that provides mutual authentication (using SIM credentials), encryption and data integrity using the same mechanisms as specified in 3GPP TS 33.234 [9]. + +# 8 High-Level Procedures for GAN A/Gb Mode + +## 8.1 Mechanism of Mode Selection in Multi-mode terminals + +A Generic Access capable terminal may support any IP access technology in addition to the GERAN and possibly UTRAN radio interfaces. The MS may be either in the GERAN/UTRAN/E-UTRAN mode or in GAN mode of operation. + +The MS can be configured to operate in one of the above two modes at any given time. There may be preferred mode of operation that can be configured by the user, or by the operator through various mechanisms, e.g. device management. + +On power up, the MS always starts in GERAN/UTRAN/E-UTRAN mode and executes the normal power-up sequence as specified in 3GPP TS 23.122 [4]. Following this, the MS may switch into GAN mode based on mode selection preference determined by user preferences or operator configuration. + +The various preferences for the MS that are possible are as follows: + +- GERAN/UTRAN/E-UTRAN-only: + - The MS RR entity remains in GERAN/UTRAN/E-UTRAN mode and does not switch to GAN mode. +- GERAN/UTRAN/E-UTRAN-preferred: + - The MS RR entity is in GERAN/UTRAN/E-UTRAN mode as long as there is a suitable GERAN, UTRAN or E-UTRAN cell available. If the MS cannot find a suitable GERAN, UTRAN or E-UTRAN cell to camp on, and MS has successfully registered with a GANC over the generic IP access network, then the MS switches to GAN mode. When the MS in GAN mode is able to find a suitable GERAN, UTRAN or E-UTRAN cell to camp on, or the MS has de-registered or loses connectivity with the GANC over the generic IP access network, the MS returns to GERAN/UTRAN/E-UTRAN mode. + +- GAN-preferred: + - When the MS has successfully registered with the GAN over the generic IP access network, the MS switches to GAN mode and stays in this mode as long as the GAN is available. When the MS deregisters, or otherwise loses connectivity with the GAN over the generic IP access network, the MS switches to GERAN/UTRAN/E-UTRAN mode. +- GAN-only: + - The MS switches to GAN mode (after initial power up sequence in GERAN/UTRAN/E-UTRAN mode to obtain cellular network information, but excluding (G)MM procedures with the core network) and does not switch to GERAN/UTRAN/E-UTRAN mode. During the initial power up sequence in GERAN/UTRAN/E-UTRAN mode the MS shall ignore paging message received through GERAN/UTRAN/E-UTRAN network. + +## 8.2 PLMN Selection + +There shall be no change from the PLMN selection procedures in the NAS layers (MM and above) in the MS, with the exception that in GAN mode the “in VPLMN background scan” shall be disabled. + +A GANC can be only connected to one PLMN. + +The PLMN selection in the NAS layers shall not lead to change of mode between GERAN/UTRAN/E-UTRAN mode and GAN mode. For a specific instance of PLMN selection only PLMNs available via GAN or only PLMNs available via GERAN/UTRAN/E-UTRAN are provided to the NAS layer (i.e. no combination of the PLMNs available via GERAN/UTRAN/E-UTRAN and GAN). + +In the case of a GAN capable MS, a GANC selection process also may be required as part of the process of establishing the connectivity between the MS and the GANC. This takes place when, during GAN registration, a GAN capable MS has a choice among two or more GANC-PLMN pairs indicated by the Default GANC (i.e. in the GA-RC REGISTER REDIRECT message). The GANC selection process takes place while the MS is still in GERAN/UTRAN/E-UTRAN mode (i.e. before the MS roves into GAN mode) as follows: + +- While a mobile station is attempting to become GAN registered, the GANC selection process shall attempt GAN registration with the currently registered PLMN if the currently registered PLMN is contained in the list of GAN PLMN pairs indicated by the Default GANC. +- If GAN registration with the currently registered PLMN is not possible and there are one or more remaining GANC-PLMN pairs that were received in the GAN PLMN list within a GA-RC REGISTER REDIRECT message, they shall all be treated as having sufficient received signal quality and PLMN selection should be performed according to the PLMN selection rules of 3GPP TS 22.011 [53] where the PLMN selected is in the GAN PLMN list. + +If the MS does not have any stored information related to the Serving GANC for the cell ID or AP to which the MS is currently connected, the MS attempts to register with the Default GANC (always located in the HPLMN) stored in MS. The MS includes an indication, identifying the GANC as the Default GANC in the GA-RC REGISTER REQUEST message. + +When an MS attempts to register on the Default GANC including an indication that it is in automatic PLMN selection mode: + +- If the Default GANC wishes to serve the MS, the Default GANC responds with a GA-RC REGISTER ACCEPT message. +- If the Default GANC wishes to redirect the MS to another GANC within the HPLMN, the Default GANC responds with a GA-RC REGISTER REDIRECT message, not including a list of PLMN identities. +- If the Default GANC wishes to redirect the MS to a PLMN that is not the HPLMN, the Default GANC responds with a GA-RC REGISTER REDIRECT message and includes a list of PLMNs that may provide GAN service to the MS in its current location. The list contains one or more PLMN identities along with the identities of their associated GANC and SEGW nodes (either in IP address or FQDN format). Following the GANC selection process, the GA-RC shall attempt to register on the associated GANC. + +If at any time the user wishes to perform manual PLMN selection or a "User reselection" irrespective of whether the MS is in manual or automatic PLMN selection mode, the MS sends a GA-RC REGISTER REQUEST message to the Default GANC, including an indication that it is in manual PLMN selection mode. The Default GANC is not allowed to + +accept the registration and responds with a GA-RC REGISTER REDIRECT message and includes a list of PLMNs that may provide GAN service to the MS in its current location. + +If the MS includes the identity of the current serving network in the GA-RC REGISTER REQUEST message, the Default GANC uses this to identify the list of PLMNs to send to the MS in the response message. + +The GA-RC REGISTER REDIRECT message may inform a mobile station that GAN A/Gb mode, GAN Iu mode or both GAN A/Gb mode and GAN Iu mode are supported for each PLMN indicated by this message. + +After successful registration with a serving GANC, the MS shall not store the PLMN list. The MS shall not use the PLMN list, provided to the MS during the registration procedure, for background scanning. + +NOTE: An MS cannot use Generic Access in a VPLMN unless the HPLMN supports and authorises Generic Access. + +After entering GAN A/Gb mode, a mobile station may trigger handover back to GERAN/UTRAN mode by sending a GA-CSR HANDOVER INFORMATION message or GA-PSR HANDOVER INFORMATION message to the GANC and including an ordered list of preferred GERAN/UTRAN cells. After entering GAN Iu mode, a mobile station may trigger handover back to GERAN/UTRAN mode by sending a GA-RRC RELOCATION INFORMATION message to the GANC and including an ordered list of preferred GERAN/UTRAN cells. In each case, the list of preferred GERAN/UTRAN cells shall include cells having the same PLMN as the currently registered PLMN (if at least one such cell is known to the MS). + +## 8.3 Re-selection between GERAN/UTRAN/E-UTRAN and GAN modes + +### 8.3.1 Rove-in (from GERAN/UTRAN/E-UTRAN mode to GAN mode) + +This procedure is applicable only if GAN service is available, a MS is not in NC2 mode (as defined in 3GPP TS 45.008 [18]) and has an MS preference for: + +- GAN-only; +- GAN-preferred or; +- GERAN/UTRAN/E-UTRAN-preferred and the MS cannot find a suitable GERAN, UTRAN or E-UTRAN cell to camp on. + +Following successful GAN registration, the Access mode in the MS is switched to GAN mode. GA-CSR or GA-RRC entity in the MS reports to the NAS, the NAS-related system information received in the GAN Registration Procedure. The NAS considers the GANC allocated cell ID, as the current serving cell. + +While in GAN mode, an MS in GERAN/UTRAN, UTRAN or E-UTRAN-preferred mode may perform GERAN/UTRAN, UTRAN or E-UTRAN cells monitoring according to 3GPP TS 45.008 and follow the behaviours according to 3GPP TS 23.122. + +While in GAN mode, the GERAN-RR, UTRAN RRC and E-UTRAN RRC entities are detached from the RR-SAP in the MS, as a result the entities do not: + +- inform NAS about any GERAN/UTRAN/E-UTRAN cell re-selection and/or the change of system information of the current camping cell; +- inform NAS about any newly found PLMN over GERAN, UTRAN or E-UTRAN; and +- act on any paging request message received over GERAN, UTRAN or E-UTRAN. + +Rove-in may be applied to support CS call re-establishment following the loss of an RR connection in GSM or to support packet service re-establishment following abnormal TBF release with cell reselection in GPRS. The support for call re-establishment is indicated to the MS in the GAN system information. + +### 8.3.2 Rove-out (from GAN mode to GERAN/UTRAN/E-UTRAN mode) + +This procedure is applicable when MS detaches from the generic IP access network, and its mode selection is GAN-preferred or when MS finds a suitable GERAN/UTRAN/E-UTRAN cell for camping on, and its mode selection is GERAN/UTRAN/E-UTRAN-preferred. + +When the MS detaches from the generic IP access network, depending on prevailing circumstances the MS may be able to deregister first with the GANC. + +For the GAN-preferred and GERAN/UTRAN/E-UTRAN-preferred mode selections, the MS detaches GA-CSR or GA-RRC from the RR-SAP and re-attaches GERAN-RR, UTRAN RRC or E-UTRAN RRC to RR-SAP and restores normal GERAN-RR, UTRAN RRC or E-UTRAN RRC functionality. + +For the GAN-only mode selection, GA-CSR or GA-RRC remains attached to NAS and the MS stays in GAN mode (in "No Service" condition). + +## 8.4 GAN Discovery and Registration related procedures + +### 8.4.1 Discovery and Registration for Generic Access + +#### 8.4.1.1 General + +The Discovery and Registration procedures are applicable only if the MS preference is operating in GAN-only, GAN-preferred or, if no allowable PLMN is available through GERAN/UTRAN/E-UTRAN, in GERAN/UTRAN/E-UTRAN-preferred mode. + +Once the MS has established a connection to the generic IP access network, the mobile determines the appropriate GANC-SEGW to connect to, by completing the Discovery Procedure to the Provisioning GANC in the HPLMN of the MS. The Provisioning GANC provides the address of the Default GANC in the HPLMN of the MS, to which the mobile can register. + +The MS attempts to register on the Default GANC provided by the Provisioning GANC during the Discovery procedure, by completing the Registration Procedure. The Default GANC may accept the Registration; redirect the MS to another GANC; or Reject the Registration. + +#### 8.4.1.2 Security Gateway Identification + +The (U)SIM of the MS contains the FQDN (or IP address) of the Provisioning GANC and the associated SEGW or the MS derives this information based on information in the (U)SIM. If the MS does not have any information about other GANCs and associated SEGW stored, then the MS completes the Discovery procedure towards the Provisioning GANC. + +As part of the Registration Procedure, the Default GANC can indicate whether this GANC and SEGW address or the address of a GANC that the MS is being redirected to, may be stored by the MS. + +The MS may also store Serving GANC information for Serving GANCs with which the MS was able to complete a successful registration procedure. The default GANC is in control of whether the MS is allowed to store Serving GANC information. If there is no GERAN/UTRAN/E-UTRAN coverage in the AP location, the stored Serving GANC information shall be associated with the AP-ID. If there is GERAN/UTRAN/E-UTRAN coverage in the AP location, the stored Serving GANC information shall be associated with the GSM CGI, UTRAN CI or E-UTRAN CI and the LAI or TAI. The stored Serving GANC information is: + +- serving SEGW FQDN or IP address following successful registration; +- serving GANC FQDN or IP address following successful registration; and +- optionally, Serving GANC TCP port following successful registration and if returned from the network. + +The number of such entries to be stored in the MS is implementation specific. Only the last successfully registered GANC association shall be stored when the Default GANC indicates that the MS is allowed to store these addresses. An MS may preferentially join a generic IP access network point of attachment whose association with a Serving GANC has been stored in memory. + +On connecting to the generic IP access network, if the MS has a stored Serving GANC for the AP-ID or the GERAN/UTRAN/E-UTRAN cell, the MS shall attempt to register with the associated Serving GANC in its memory. The GANC may still reject the MS for any reason even though it may have served the MS before. The MS shall delete from its stored list the address of the Serving GANC on receiving a registration reject or if the registration fails for any other reason (e.g. not receiving any response). + +If the MS does not receive a response to the Registration Request sent to the Serving GANC (and which is not the Default GANC), it shall re-attempt to register with the Default GANC. If the MS does not receive a response to the registration request sent to the Default GANC, it shall attempt the discovery procedure with the Provisioning GANC in order to obtain a new Default GANC. + +In the case when a MS is attempting to register or discover a GANC after failing to register on a GANC, the MS provides in the Registration or Discovery procedure an indication that the MS has attempted to Register on another GANC, the failure reason, and the GANC and SEGW addresses of the failed registration. + +When the MS connects to a generic IP access network, for which it does not have a stored Serving GANC in its memory, it shall attempt to register with the Default GANC. + +#### 8.4.1.3 GANC capabilities + +To be populated with GANC specific information that needs to be transferred to the MS on successful registration. + +#### 8.4.1.4 MS capabilities + +To be populated with GAN specific capabilities of the MS that needs to be transferred to the GANC during registration and the interaction to what is reported to the CN is FFS. + +#### 8.4.1.4a Required GAN Services + +The MS may request which GAN services it requires from the GANC as part of the Registration procedures. + +#### 8.4.1.4b GAN Mode Selection + +The MS (i.e., with GAN Iu mode support) transfers its GAN Mode Support information to the GANC during Discovery and Registration procedures; i.e., in the GAN Classmark IE. GAN Mode Support options are GAN A/Gb mode supported, GAN Iu mode supported, or both modes supported. If no GAN Mode Support information is received, the GANC assumes that the MS supports GAN A/Gb mode operation only. + +The provisioning GANC may use the received GAN Mode Support information to assign the MS to an appropriate default GANC (e.g., if separate GAN A/Gb mode and GAN Iu mode GANCs are deployed in the network) or to an appropriate TCP port on the default GANC (e.g., if separate TCP ports are used for GAN A/Gb mode and GAN Iu mode service). During registration, the GAN Iu mode capable GANC shall also indicate the GAN mode to use for the current session in the GAN Mode Indicator IE; this allows the MS to determine the GAN Iu mode capability of the Home PLMN. + +The following table enumerates the discovery handling for the various combinations of MS and Home PLMN GAN mode capabilities. + +**Table 1: GAN Mode Selection procedures associated with GAN Discovery** + +| MS GAN Mode Capabilities | Home PLMN GAN Mode Capabilities | | | +|--------------------------|---------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | A/Gb only | Iu only | Both | +| A/Gb only | GANC: Handle as normal GAN A/Gb mode discovery
MS: Proceed with registration | GANC: No GAN Mode Support information provided or GAN A/Gb mode (only) indicated by MS, therefore Reject (Unspecified)
MS: Retry on next power-on | GANC: No GAN Mode Support information provided or GAN A/Gb mode (only) indicated by MS, therefore handle as normal GAN A/Gb mode discovery. Assign MS to GAN A/Gb-capable GANC.
MS: Proceed with registration | +| Iu only | GANC: Handle as normal GAN A/Gb mode discovery
MS: Proceed with registration | GANC: GAN Iu Mode Support (only) indicated by MS, therefore accept and assign MS to GAN Iu mode capable GANC.
MS: Proceed with registration | GANC: GAN Iu Mode Support (only) indicated by MS, therefore accept and assign MS to GAN Iu mode capable GANC.
MS: Proceed with registration | +| Both | GANC: Handle as normal GAN A/Gb discovery
MS: Proceed with registration | GANC: Support for both modes indicated by MS, therefore accept and assign MS to GAN Iu mode capable GANC.
MS: Proceed with registration | GANC: Support for both modes indicated by MS, therefore accept and assign MS to GAN A/Gb mode capable GANC or GAN Iu mode capable GANC (Note 1).
MS: Proceed with registration | + +Note 1: The GANC's choice of GAN Iu mode versus GAN A/Gb mode may be based on other information received in the GAN discovery message from the MS, information stored in the GANC, and on operator policy. + +The default or serving GANC may use the received GAN Mode Support information to redirect the MS to a different GANC or a different TCP port on the current GANC. The GAN Iu mode capable GANC shall also indicate the GAN mode to use for the current session in the GAN Mode Indicator IE. + +The following table enumerates the registration handling for the various combinations of MS and Default/Serving GANC GAN mode capabilities. + +**Table 2: GAN Mode Selection procedures associated with GAN Registration** + +| MS GAN Mode Capabilities | Default/Serving GANC GAN Mode Capabilities | | | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | A/Gb only | Iu only | Both | +| A/Gb only | GANC: Handle as normal GAN A/Gb mode registration
MS: Proceed per GAN A/Gb mode procedures | GANC: No GAN Mode Support information provided or GAN A/Gb mode (only) indicated by MS, therefore Reject (Invalid GANC)
MS: Attempt registration with Default GANC or re-discovery (per GAN A/Gb mode procedures) | GANC: No GAN Mode Support information provided or GAN A/Gb mode (only) indicated by MS, therefore handle as normal GAN A/Gb mode registration. If required, redirect MS to GAN A/Gb mode capable GANC.
MS: Proceed per GAN A/Gb mode procedures | +| Iu only | GANC: Handle as normal GAN A/Gb mode registration
MS: No GAN Mode Selection provided by GANC, therefore Deregister and treat as register reject (Invalid GANC) | GANC: GAN Iu Mode Support (only) indicated by MS, therefore accept and send GAN Mode Indicator = GAN Iu mode
MS: Proceed per GAN Iu mode procedures | GANC: GAN Iu Mode Support (only) indicated by MS, therefore accept and send GAN Mode Indicator = GAN Iu mode.
MS: Proceed per GAN Iu mode procedures | +| Both | GANC: Handle as normal GAN A/Gb mode registration
MS: No GAN Mode Selection provided by GANC, therefore proceed per GAN A/Gb mode procedures | GANC: Support for both modes indicated by MS, therefore accept and send GAN Mode Indicator = GAN Iu mode
MS: Proceed per GAN Iu mode procedures | GANC: Support for both modes indicated by MS, therefore accept and send GAN Mode Indicator = GAN Iu mode or GAN A/Gb mode (Note 1). If required, redirect MS to GAN Iu mode or GAN A/Gb mode capable GANC.
MS: Proceed per GAN Iu mode or GAN A/Gb mode procedures | + +Note 1: The GANC's choice of GAN Iu mode versus GAN A/Gb mode may be based on other information received in the GAN registration message from the MS, information stored in the GANC, and on operator policy. + +#### 8.4.1.5 Discovery Procedure + +##### 8.4.1.5.1 Normal Case + +When an MS supporting GAN first attempts to connect to a GAN, the MS needs to identify the Default GANC. Each GAN capable MS can be configured with the FQDN (or IP address) of the Provisioning GANC and the associated SEGW or the MS can derive this FQDN based on information in the (U)SIM (see 3GPP TS 23.003 [43]). The MS first connects to a Provisioning GANC-SEGW and GANC in the HPLMN of the MS, by establishing a secure IPsec tunnel and a TCP connection using the provisioned or derived addresses. The MS obtains the FQDN or IP address of the Default GANC in the HPLMN and the associated SEGW, through the Discovery procedure. + +If no GERAN/UTRAN/E-UTRAN coverage is available when an MS connects to the GANC for GAN service, then the GANC cannot necessarily determine the location of the MS for the purposes of assigning the MS to the correct serving GANC (e.g., to enable handover and location-based services). The GANC shall permit the operator to determine the service policy in this case; e.g. the operator could provide service to the user with certain limitations (possibly with a user interface indication on the MS). + +NOTE: When the MS initiates the Discovery/Registration procedures and no GERAN/UTRAN/E-UTRAN coverage is available, the GANC may have insufficient information to correctly route subsequent emergency calls. + +![Sequence diagram of the Discovery procedure. The diagram shows interactions between MS, DNS, and a Provisioning GANC (containing SEGW, DNS, and GANC). The steps are: 1. MS sends a DNS query for the Provisioning SEGW FQDN to the DNS. 2. DNS responds. 3. MS establishes a secure tunnel with the SEGW. 4. MS sends a DNS query for the Provisioning GANC FQDN to the DNS. 5. DNS responds. 6. MS sends a GA-RC DISCOVERY REQUEST (with CID, LAI/TAI, IMSI) to the GANC. 7. GANC responds with a GA-RC DISCOVERY ACCEPT (providing Default SEGW and GANC address). 8. Alternatively, GANC could send a GA-RC DISCOVERY REJECT with a Reject Cause. 9. MS releases the secure tunnel with the SEGW.](50214d232017279410e9c9db8eb75119_img.jpg) + +``` + +sequenceDiagram + participant MS + participant DNS + subgraph Provisioning GANC + participant SEGW + participant DNS2 as DNS + participant GANC + end + Note left of MS: 1. DNS query (provisioned or derived SEGW FQDN) + MS-->DNS: 1. DNS query (provisioned or derived SEGW FQDN) + DNS-->MS: 2. DNS response + Note left of MS: 3. Establish secure tunnel + MS->>SEGW: 3. Establish secure tunnel + Note left of MS: 4. DNS query (provisioning GANC FQDN) + MS-->DNS2: 4. DNS query (provisioning GANC FQDN) + DNS2-->MS: 5. DNS response + Note left of MS: 6. GA-RC DISCOVERY REQUEST (CID, LAI/TAI, IMSI) + MS->>GANC: 6. GA-RC DISCOVERY REQUEST (CID, LAI/TAI, IMSI) + Note left of MS: 7. GA-RC DISCOVERY ACCEPT (Default SEGW and GANC address) + GANC-->>MS: 7. GA-RC DISCOVERY ACCEPT (Default SEGW and GANC address) + Note left of MS: 8. GA-RC DISCOVERY REJECT (Reject Cause) + GANC-->>MS: 8. GA-RC DISCOVERY REJECT (Reject Cause) + Note left of MS: 9. Release secure tunnel + MS-->>SEGW: 9. Release secure tunnel + +``` + +Sequence diagram of the Discovery procedure. The diagram shows interactions between MS, DNS, and a Provisioning GANC (containing SEGW, DNS, and GANC). The steps are: 1. MS sends a DNS query for the Provisioning SEGW FQDN to the DNS. 2. DNS responds. 3. MS establishes a secure tunnel with the SEGW. 4. MS sends a DNS query for the Provisioning GANC FQDN to the DNS. 5. DNS responds. 6. MS sends a GA-RC DISCOVERY REQUEST (with CID, LAI/TAI, IMSI) to the GANC. 7. GANC responds with a GA-RC DISCOVERY ACCEPT (providing Default SEGW and GANC address). 8. Alternatively, GANC could send a GA-RC DISCOVERY REJECT with a Reject Cause. 9. MS releases the secure tunnel with the SEGW. + +**Figure 10: Discovery procedure** + +In the description below it is assumed that the MS has a mode selection of GAN-only or GAN-preferred or GERAN/UTRAN/E-UTRAN-preferred and that the MS has already connected to the generic IP access network. + +NOTE: It is implementation specific what signal level should be deemed as sufficient for triggering the GAN Discovery and Registration procedures. + +1. If the MS has a provisioned or derived FQDN of the Provisioning SEGW, it performs a DNS query (via the generic IP access network interface) to resolve the FQDN to an IP address. If the MS has a provisioned IP address for the Provisioning SEGW, the DNS step is omitted. +2. The DNS Server returns a response including the IP Address of the Provisioning SEGW. +3. The MS establishes a secure tunnel to the Provisioning SEGW. + +4. If the MS has a provisioned or derived FQDN of the Provisioning GANC, it performs a DNS query (via the secure tunnel) to resolve the FQDN to an IP address. If the MS has a provisioned IP address for the Provisioning GANC, the DNS step will be omitted. +5. The DNS Server returns a response including the IP Address of the Provisioning GANC. +6. The MS sets up a TCP connection to a well-defined port on the Provisioning GANC. It then queries the Provisioning GANC for the Default GANC, using GA-RC DISCOVERY REQUEST. The message contains: + - If the MS is camped on a GERAN/UTRAN/E-UTRAN cell, the current camping GERAN/UTRAN/E-UTRAN cell ID. + - The last LAI or TAI where the MS successfully registered. + - Generic IP access network attachment point information: AP-ID, as defined in annex C. + - MS Identity: IMSI. + - GAN Classmark: Including GAN Mode Support information indicating GAN A/Gb mode supported, GAN Iu mode supported or both modes supported. +7. The Provisioning GANC returns the GA-RC DISCOVERY ACCEPT message, using the information provided by the MS (e.g. the CGI), to provide the FQDN or IP address of the Default GANC and its associated Default SEGW. This is done so the MS is directed to a "local" Default GANC in the HPLMN to optimize network performance. +8. If the Provisioning GANC cannot accept the GA-RC DISCOVERY REQUEST message, it returns a GA-RC DISCOVERY REJECT message indicating the reject cause. +9. The secure IPsec tunnel to the Provisioning SEGW is released. It shall also be possible to reuse the same IPsec tunnel for GAN Registration procedures. In this case the IPsec tunnel is not released. + +#### 8.4.1.6 Registration procedure + +##### 8.4.1.6.1 Normal case + +Following the Discovery procedure the MS establishes a secure tunnel with the secure gateway of the Default GANC, provided by the Provisioning GANC in the Discovery procedure, and attempts to register with the Default GANC. The Default GANC may become the Serving GANC for that connection by accepting the registration, or the Default GANC may redirect a MS performing registration to a different Serving GANC. + +GANC redirection may be based on information provided by the MS during the Registration procedure, operator chosen policy or network load balancing. + +The GAN Registration procedure serves the following functions: + +- Ensures the MS is registered to the appropriate GANC entity i.e. with use of the redirection process; +- Informs the GANC that the MS is now connected through a generic IP access network and is available at a particular IP address. The GANC maintains the registration context for the purposes of (for example) mobile-terminated calling; +- Provides the MS with the operating parameters associated with the GAN service, including the GAN mode to use for the session, either A/Gb or Iu. The "System Information" message content that is applicable to the GAN cell is delivered to the MS during the GAN registration process. This enables the MS to switch to GAN mode, and following the Registration procedure trigger NAS procedures with the core network (such as Location/Routing Area Update, mobile originated calls, mobile terminated calls, etc.); and +- Enables the MS to request which GAN services are required. + +![Sequence diagram of the Registration procedure. Lifelines: MS, DNS, and Default or Serving GANC (containing SEGW, DNS, and GANC). The sequence shows 10 steps: 1. MS to DNS: DNS query (Default or Serving SEGW FQDN); 2. DNS to MS: DNS response; 3. MS to SEGW: Establish secure tunnel; 4. MS to DNS: DNS query (Default or Serving GANC FQDN); 5. DNS to MS: DNS response; 6. MS to GANC: GA-RC REGISTER REQUEST (CID, LAI/TAI, IMSI); 7. GANC to MS: GA-RC REGISTER ACCEPT (](32ff77da4286b58c4778033acaa10836_img.jpg) + +``` + +sequenceDiagram + participant MS + participant DNS + subgraph Default or Serving GANC + participant SEGW + participant DNS2 as DNS + participant GANC + end + Note right of Default or Serving GANC: Default or Serving GANC + MS->>DNS: 1. DNS query (Default or Serving SEGW FQDN) + DNS-->>MS: 2. DNS response + MS->>SEGW: 3. Establish secure tunnel + MS->>DNS2: 4. DNS query (Default or Serving GANC FQDN) + DNS2-->>MS: 5. DNS response + MS->>GANC: 6. GA-RC REGISTER REQUEST (CID, LAI/TAI, IMSI) + GANC-->>MS: 7. GA-RC REGISTER ACCEPT ("GAN System Information") + GANC-->>MS: 8. GA-RC REGISTER REJECT (Reject Cause) + GANC-->>MS: 9. GA-RC REGISTER REDIRECT (see note) + MS-->>SEGW: 10. Release secure tunnel + +``` + +Sequence diagram of the Registration procedure. Lifelines: MS, DNS, and Default or Serving GANC (containing SEGW, DNS, and GANC). The sequence shows 10 steps: 1. MS to DNS: DNS query (Default or Serving SEGW FQDN); 2. DNS to MS: DNS response; 3. MS to SEGW: Establish secure tunnel; 4. MS to DNS: DNS query (Default or Serving GANC FQDN); 5. DNS to MS: DNS response; 6. MS to GANC: GA-RC REGISTER REQUEST (CID, LAI/TAI, IMSI); 7. GANC to MS: GA-RC REGISTER ACCEPT ( + +NOTE: The GA-RC REGISTER REDIRECT message may contain: a single Serving SEGW and GANC address or a list of PLMN identities and associated Serving SEGW and GANC addresses; and an Indication of whether GANC address(es) can be stored in the MS for future use. + +**Figure 11: Registration procedure** + +1. If the MS was provided the FQDN of the Default or Serving SEGW, the MS shall perform a DNS query (via the generic IP access network interface) to resolve the FQDN to an IP address. If the MS has a provisioned IP address for the SEGW, the DNS step is omitted. +2. The DNS Server returns a response. +3. The MS shall then set up a secure IPsec tunnel to the SEGW. This step may be omitted if an IPsec tunnel is being reused from an earlier Discovery or Registration. +4. If the MS was provided the FQDN of the Default or Serving GANC, the MS shall then perform a DNS query (via the secure tunnel) to resolve the FQDN to an IP address. If the MS has an IP address for the GANC, the DNS step is omitted. +5. The DNS Server returns a response. +6. The MS then sets up a TCP connection to a TCP port on the GANC. The TCP port can either be a well-known port or one that has been earlier received from the network during Discovery or Registration. The MS shall attempt to register on the GANC by transmitting the GA-RC REGISTER REQUEST. The message includes: + - If the MS is camped on a GERAN/UTRAN/E-UTRAN cell, the MS includes the current camping GERAN/UTRAN/E-UTRAN cell ID. + - If the MS is camped on a UTRAN cell, the MS includes theUARFCN of the current serving cell. + - The last LAI or TAI where the MS successfully registered. + - Generic IP access network attachment point information: AP-ID, as defined in annex C. + +- MS Identity: IMSI. + - MS Capability Information. + - GAN Services Required + - GAN Classmark: Including GAN Mode Support information indicating GAN A/Gb mode supported, GAN Iu mode supported or both modes supported, and an indication of whether or not the MS supports RFC 4867 [54] bandwidth-efficient mode. +7. If the GANC accepts the registration attempt it shall respond with a GA-RC REGISTER ACCEPT. The message contains: +- GAN specific system information (e.g.): + - GAN Mode Indicator: GAN A/Gb mode or GAN Iu mode. + - Cell description of the GAN cell: + - If GAN A/Gb mode selected: The BCCH ARFCN, PLMN colour code, and base-station colour code corresponding to the GAN cell. + - If GAN Iu mode selected: The UTRA ARFCN (UARFCN) and Primary Scrambling Code (PSC) corresponding to the GAN cell. + - Location-area identification comprising the mobile country code, mobile network code, and location area code corresponding to the GANC cell. + - Cell identity identifying the cell within the location area corresponding to the GAN cell. + - Applicable system timer values (e.g., for the application-level keep-alive message transmission interval, see clause 8.4.4). + - GAN Capability Information. +- In this case the TCP connection and the secure IPsec tunnel are not released and are maintained as long as the MS is registered to this GANC. +8. Alternatively, the GANC may reject the request. In this case, it shall respond with a GA-RC REGISTER REJECT indicating the reject cause. The TCP connection and the secure IPsec tunnel are released and the MS shall act as defined in clause 8.4.1.3.2. +9. Alternatively, if the GANC wishes to redirect the MS to (another) Serving GANC, it shall respond with a GA-RC REGISTER REDIRECT providing the FQDN or IP address of the target Serving GANC and the associated SEGW. In this case the TCP connection is released and the secure IPsec tunnel is optionally released depending on if the network indicates that the same IPsec tunnel can be reused for the next registration. + +##### 8.4.1.6.2 Abnormal cases + +If the Serving GANC rejects the Register request and does not provide redirection to another Serving GANC, the MS shall re-attempt Registration to the Default GANC including a cause indicating the failed registration attempt and the Serving GANC and SEGW with which the Register request failed. The MS should also delete all stored information about this Serving GANC. + +If the Default GANC rejects a Registration Request and is unable to provide redirection to suitable Serving GANC, the MS may re-attempt the Discovery procedure to the Provisioning GANC (including a cause indicating the failed registration attempt and the Default GANC provided in the last Discovery procedure). The MS should also delete all stored information about the Default GANC. + +### 8.4.2 De-Registration + +The GA-RC De-Registration procedure allows the MS to explicitly inform the GANC that it is leaving GAN mode (e.g. when it detaches from the generic IP access network), by sending a GA-RC DEREGISTER message to the GANC, allowing the GANC to free resources that it assigned to the MS. The GANC also supports "implicit GAN deregistration", when the TCP connection to the MS is abruptly lost. + +The GANC can also autonomously release the MS registration context, and send a GA-RC DEREGISTER message to the MS. Alternatively, the GANC can implicitly deregister the MS by closing the TCP connection with the MS. + +NOTE: At power-down the GA-RC sublayer of the MS ensures that the MS explicitly detaches from the network, where possible, before completing the GA-RC De-Registration procedure. + +![Sequence diagram showing De-Registration initiated by the MS. The MS sends a GA-RC DEREGISTER message to the GANC.](b44f89b176c971c7dd264c07bfef2c2a_img.jpg) + +``` +sequenceDiagram + participant MS + participant GANC + Note left of MS: De-Registration initiated by the MS + MS->>GANC: 1. GA-RC DEREGISTER +``` + +Sequence diagram showing De-Registration initiated by the MS. The MS sends a GA-RC DEREGISTER message to the GANC. + +**Figure 12: De-Registration initiated by the MS** + +1. The MS sends the GA-RC DEREGISTER to the GANC, which removes the MS context in the GANC. + +![Sequence diagram showing De-Registration initiated by the GANC. The GANC sends a GA-RC DEREGISTER message to the MS.](48f209b7c0c1f91af40cfc3466dbd534_img.jpg) + +``` +sequenceDiagram + participant MS + participant GANC + Note right of GANC: De-Registration initiated by the GANC + GANC->>MS: 1. GA-RC DEREGISTER +``` + +Sequence diagram showing De-Registration initiated by the GANC. The GANC sends a GA-RC DEREGISTER message to the MS. + +**Figure 13: De-Registration initiated by the GANC** + +1. The GANC sends the GA-RC DEREGISTER to the MS. + +### 8.4.3 Registration Update + +The GA-RC Registration Update procedure allows the MS to update information in the GANC by sending a GA-RC REGISTER UPDATE UPLINK message to the GANC carrying the updated information. This message is sent as a result of the following: + +- Detecting the availability of GERAN/UTRAN/E-UTRAN coverage after reporting no coverage during GAN registration. +- Changes to the identity of the serving GERAN/UTRAN/E-UTRAN cell while in GERAN/UTRAN/E-UTRAN mode. +- Changes to theUARFCN of the serving UTRAN cell while in UTRAN mode. +- Establishment of a new serving cell as a result of inter-RAT handover from GERAN to UTRAN or E-UTRAN to UTRAN. +- Changes to the generic IP access network point of attachment. + +This may result in the MS being redirected to another serving GANC, or being denied service e.g. due to operator policy. + +The GAN Registration Update procedure also allows the GANC to update the GAN system information in the MS, if needed, by sending a GA-RC REGISTER UPDATE DOWNLINK message to the MS carrying the updated information. + +![Sequence diagram for Registration Update Uplink](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + MS->>GANC: 1. GA-RC REGISTER UPDATE UPLINK + GANC-->>MS: 2. GA-RC REGISTER REDIRECT + GANC-->>MS: 3. GA-RC DEREGISTER + +``` + +A sequence diagram showing the interaction between a Mobile Station (MS) and a GANC. The MS sends a solid arrow labeled '1. GA-RC REGISTER UPDATE UPLINK' to the GANC. The GANC then sends two dashed arrows back to the MS: '2. GA-RC REGISTER REDIRECT' and '3. GA-RC DEREGISTER'. + +Sequence diagram for Registration Update Uplink + +**Figure 14: Registration Update Uplink** + +1. When the MS detects any of the conditions listed above, it shall send the GA-RC REGISTER UPDATE UPLINK to the GANC with the updated information. Whenever the generic IP access network point of attachment changes, the MS shall send a GA-RC REGISTER UPDATE UPLINK to the GANC with the updated generic IP access network point of attachment information. If the MS requires to update the GANC with a new list of GAN Services required, then the MS sends GA-RC REGISTER UPDATE UPLINK message to the GANC including the new GAN Services Required list. +2. The GANC may optionally send the GA-RC REGISTER REDIRECT when it wants to redirect the MS based on updated information. +3. The GANC may also optionally deregister the MS on receiving an update by sending GA-RC DEREGISTER to the MS. + +![Sequence diagram for Registration Update Downlink](683f755e8456c884716de4fce48c7e63_img.jpg) + +``` + +sequenceDiagram + participant GANC + participant MS + GANC->>MS: 1. GA-RC REGISTER UPDATE DOWNLINK + +``` + +A sequence diagram showing the interaction between a Mobile Station (MS) and a GANC. The GANC sends a solid arrow labeled '1. GA-RC REGISTER UPDATE DOWNLINK' to the MS. + +Sequence diagram for Registration Update Downlink + +**Figure 15: Registration Update Downlink** + +1. The GANC sends GA-RC REGISTER UPDATE DOWNLINK with the updated system information. + +### 8.4.4 Keep Alive + +The Keep Alive process is a mechanism between the peer GA-RC entities to indicate that the MS is still registered to the GANC. Using periodic transmissions of the GA-RC KEEP ALIVE message the MS in turn determines that the GANC is still available using the currently established lower layer connection. + +![Sequence diagram for Keep Alive procedure](659a041a7997f9eea79f4e2f3ba265a5_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + MS->>GANC: 1. GA-RC KEEP ALIVE + +``` + +A sequence diagram showing the interaction between a Mobile Station (MS) and a GANC. The MS sends a solid arrow labeled '1. GA-RC KEEP ALIVE' to the GANC. + +Sequence diagram for Keep Alive procedure + +**Figure 16: Keep Alive procedure** + +1. The MS sends GA-RC KEEP ALIVE to the GANC. + +### 8.4.5 Cell Broadcast Information + +The Cell Broadcast Information is a mechanism between the peer GA-RC entities, allowing the GANC to pass the MS information relating to the Cell Broadcast Services. The MS includes GAN Service Required information in the GA-RC REGISTER REQUEST and GA-RC REGISTER UPDATE UPLINK messages passed to the GANC, indicating that the MS requires the Cell Broadcast Service. The GANC then passes the required information to the MS in the GA-RC CELL BROADCAST INFO message. + +![Diagram showing the Cell Broadcast Information exchange between MS and GANC. A horizontal arrow labeled '1. GA-RC CELL BROADCAST INFO' points from the GANC box to the MS box.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +``` + +graph LR + GANC[GANC] -- "1. GA-RC CELL BROADCAST INFO" --> MS[MS] + +``` + +Diagram showing the Cell Broadcast Information exchange between MS and GANC. A horizontal arrow labeled '1. GA-RC CELL BROADCAST INFO' points from the GANC box to the MS box. + +**Figure 16a: Cell Broadcast Information** + +1. The GANC sends the CELL BROADCAST INFO message to the MS, including information required by the MS. + +## 8.5 Authentication + +The Up interface shall support the ability to authenticate the MS with the GANC (for the purposes of establishing the secure tunnel) using GSM or UMTS credentials. Authentication between MS and GANC shall be performed using EAP-SIM or EAP-AKA within IKEv2. + +The MS and GANC-SEGW establish a secure association for protecting signalling traffic and user-plane (voice and data) traffic. The protocol for authentication is IKEv2. Mutual authentication and key generation is provided by EAP-SIM or EAP-AKA. + +The basic elements of these procedures are the following: + +- The MS connection with the GANC-SEGW is initiated by starting the IKEv2 initial exchanges (IKE\_SA\_INIT). The EAP-SIM or EAP-AKA procedure is started as a result of these exchanges. +- The EAP-SIM procedure for MS with SIM only or MS with USIM, but not capable of UMTS AKA, is performed between MS and AAA server (that has access to the AuC/HLR/HSS to retrieve subscriber information). The EAP-AKA procedure for MS with USIM and the MS is capable of UMTS AKA, is performed between MS and AAA server. The GANC-SEGW acts as relay for the EAP-SIM/EAP-AKA messages. +- When the EAP-SIM/EAP-AKA procedure has completed successfully, the IKEv2 procedure can be continued to completion and the signalling channel between MS and GANC-SEGW is secured. The MS and GAN can then continue with the discovery or registration procedure. +- Signalling flows for EAP-SIM and EAP-AKA authentication and fast re-authentication are shown in annex A. + +## 8.6 Encryption + +All control and user plane traffic over the Up interface shall be sent through the IPsec tunnel that is established as a result of the authentication procedure. Encryption shall use the negotiated cryptographic algorithm, based on core network policy, enforced by the GANC-SEGW. + +The MS and GANC-SEGW set up one Secure Association through which all traffic is sent. A single negotiated ciphering algorithm is applied to the connection. + +### 8.6.1 Establishment of a Secure Association + +After the authentication procedure (clause 8.5), the MS shall request an IP address on the network protected by the GANC-SEGW (i.e. the public IP interface of the GANC). The MS shall set up one IPsec Security Association (SA) between MS and GANC-SEGW. + +The MS shall initiate the creation of the SA i.e. it shall act as initiator in the Traffic Selector negotiation. The protocol ID field in the Traffic Selectors (TS) shall be set to zero, indicating that the protocol ID is not relevant. The IP address range in the TSi shall be set to the address assigned to the MS (within the network protected by the GANC-SEGW). The IP address range in the TSr shall be set to 0.0.0.0 - 255.255.255.255. The MS and GANC-SEGW shall use the IKEv2 mechanisms for detection of NAT, NAT traversal and keep-alive. + +All control and user plane data over the Up interface between MS and GANC shall be sent through the SA. + +The ciphering mode is negotiated during connection establishment. During setup of the SA, the MS includes a list of supported encryption algorithms as part of the IKE signalling, which include the mandatory and supported optional + +algorithms defined in the IPsec profile, and NULL encryption. The GANC-SEGW selects one of these algorithms, and signals this to the MS. + +When NULL encryption is applied, both control and user-plane traffic is sent unencrypted. This configuration can be selected e.g. when the connection between the generic IP access network and the GANC is under operator control. The integrity algorithm is the same as for either configuration i.e. non-ciphered traffic is still integrity protected. + +## 8.7 GA-CSR Connection handling + +The GA-CSR connection is a logical connection between the MS and the GANC for the CS domain. It is established when the upper layers in the MS request GA-CSR to enter dedicated mode. When a successful response is received from the network, GA-CSR replies to the upper layer that it has entered dedicated mode. The upper layers have then the possibility to request transmission of NAS messages to the network. + +### 8.7.1 GA-CSR Connection Establishment + +Figure 17 shows successful establishment of the GA-CSR Connection. + +![Sequence diagram for GA-CSR Connection Establishment between MS, GANC, and CN.](b4f6d3668f7e851eaff07ccf26001623_img.jpg) + +``` +sequenceDiagram + participant MS + participant GANC + participant CN + Note left of MS: + MS->>GANC: 1. GA-CSR REQUEST (Establishment Cause) + GANC-->>MS: 2. GA-CSR REQUEST ACCEPT + Note right of GANC: + GANC-->>MS: 3. GA-CSR REQUEST REJECT (Cause) +``` + +The diagram illustrates the interaction for GA-CSR connection establishment. It features three lifelines: MS (Mobile Station), GANC (Generic Access Network Controller), and CN (Core Network). The sequence begins with the MS sending a '1. GA-CSR REQUEST (Establishment Cause)' message to the GANC. The GANC responds with '2. GA-CSR REQUEST ACCEPT' via a solid arrow. Alternatively, it can send '3. GA-CSR REQUEST REJECT (Cause)' via a dashed arrow. The CN lifeline is shown but not involved in this specific sequence. + +Sequence diagram for GA-CSR Connection Establishment between MS, GANC, and CN. + +Figure 17: GA-CSR Connection Establishment + +1. The MS initiates GA-CSR connection establishment by sending the GA-CSR REQUEST message to the GANC. This message contains the Establishment Cause indicating the reason for GA-CSR connection establishment. +2. GANC signals the successful response to the MS by sending the GA-CSR REQUEST ACCEPT and the MS enters dedicated mode and the GA-CSR state changes to GA-CSR-DEDICATED. +3. Alternatively, the GANC may return a GA-CSR REQUEST REJECT indicating the reject cause. + +### 8.7.2 GA-CSR Connection Release + +Figure 18 shows release of the logical GA-CSR connection between the MS and the GANC. + +![Sequence diagram for GA-CSR Connection Release between MS, GANC, and CN.](901800172164e0494762ffa57a09993f_img.jpg) + +``` +sequenceDiagram + participant MS + participant GANC + participant CN + Note right of CN: + CN->>GANC: 1. Clear Command + GANC-->>CN: 2. Clear Complete + Note left of GANC: + GANC->>MS: 3. GA-CSR RELEASE + MS-->>GANC: 4. GA-CSR RELEASE COMPLETE +``` + +The diagram illustrates the interaction for GA-CSR connection release. It features three lifelines: MS (Mobile Station), GANC (Generic Access Network Controller), and CN (Core Network). The sequence starts with the CN sending a '1. Clear Command' to the GANC. The GANC responds with '2. Clear Complete' to the CN. Next, the GANC sends a '3. GA-CSR RELEASE' message to the MS. Finally, the MS responds with '4. GA-CSR RELEASE COMPLETE' to the GANC. + +Sequence diagram for GA-CSR Connection Release between MS, GANC, and CN. + +Figure 18: GA-CSR Connection Release + +1. The CN indicates to the GANC to release the user plane connection allocated to the MS, via the *Clear Command*. +2. The GANC confirms resource release to CN using the *Clear Complete* message. +3. The GANC commands the MS to release resources, using the GA-CSR RELEASE message. + +- The MS confirms resource release to the GANC using the GA-CSR RELEASE COMPLETE message and the MS enters idle mode and the GA-CSR state in the MS changes to GA-CSR-IDLE. + +## 8.8 Ciphering Configuration + +The message flow for ciphering configuration is shown in figure 19. + +![Sequence diagram for Ciphering Configuration showing interactions between MS, GANC, and CN.](552328a9daaf3bc0069424b500025880_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant CN + Note right of GANC: Verify MAC + CN->>GANC: 1. Cipher Mode Command + GANC->>MS: 2. GA-CSR CIPHERING MODE COMMAND (algorithm, cipher response, rand, ...) + MS->>GANC: 3. GA-CSR CIPHERING MODE COMPLETE (MAC(rand, ...), (IMEISV)) + GANC->>CN: 4. Cipher Mode Complete + +``` + +Sequence diagram for Ciphering Configuration showing interactions between MS, GANC, and CN. + +**Figure 19: Ciphering Configuration** + +- The CN sends BSSMAP "*Cipher Mode Command*" message to GANC. This message contains the cipher key Kc, and the encryption algorithms that the GANC may use. +- The GANC sends GA-CSR CIPHERING MODE COMMAND to the MS. This message indicate whether stream ciphering shall be started or not (after handover to GERAN) and if so, which algorithm to use, and a random number. The mobile station stores the information for possible future use after a handover to GERAN. The message also indicates whether the MS shall include IMEISV in the GA-CSR CIPHERING MODE COMPLETE message. +- The MS computes a MAC based on the random number, the MS IMSI and the key Kc. The MS then sends GA-CSR CIPHERING MODE COMPLETE message to signal its selected algorithm, the computed MAC, and the IMEISV, if indicated so in the GA-CSR CIPHERING MODE COMMAND. +- This GANC verifies the MAC. If the GANC verifies MAC to be correct it sends *Cipher Mode Complete* message to the CN. + +NOTE: The MAC proves that the identity that is authenticated to the GANC is the same as the identity authenticated to the core network. The configuration option of not enabling ciphering in the network will therefore open up the network to more security threats than in GERAN. + +## 8.9 GA-CSR Signalling and SMS Transport Procedures + +### 8.9.1 Network initiated CS Signalling + +![Sequence diagram for Downlink Control Plane Transport showing interactions between MS, GANC, and CN.](981668c6be5792b778cccb1af38477e2_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant CN + CN->>GANC: 1. DTAP(Layer 3 message) + GANC->>MS: 2. GA-CSR DL DIRECT TRANSFER (Layer 3 message) + +``` + +Sequence diagram for Downlink Control Plane Transport showing interactions between MS, GANC, and CN. + +**Figure 20: Downlink Control Plane Transport** + +- For Network initiated signalling/SMS, the Core Network sends a MM/CC signalling or SMS message to the GANC via the A interface. + +2. The GANC encapsulates the received message within a GA-CSR DL DIRECT TRANSFER message that is forwarded to the MS via the existing TCP connection. + +### 8.9.2 MS initiated CS Signalling + +![Sequence diagram for MS initiated CS Signalling showing message flow between MS, GANC, and CN.](036c200da9b64c3eb5aae2d67bb53e1f_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant CN + MS->>GANC: 1. GA-CSR UL DIRECT TRANSFER (Layer 3 message) + GANC->>CN: 2. DTAP(Layer 3 message) + +``` + +Sequence diagram for MS initiated CS Signalling showing message flow between MS, GANC, and CN. + +Figure 21: Uplink Control Plane Transport + +1. For MS initiated signalling/SMS, the MS GA-CSR receives a request from the NAS layer to transfer an uplink NAS signalling message or SMS message. The MS GA-CSR encapsulates the NAS message within a GA-CSR UL DIRECT TRANSFER message and sends the message to the GANC. +2. The GANC relays the received message to the Core Network encapsulated in DTAP. + +## 8.10 Mobile Originated Call Flow + +![Sequence diagram for Mobile Originated Call Flow showing interactions between MS, GANC, and CN.](2aa94b70ba3fadcba8420d9e3128253a_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant CN + MS->>GANC: 1. GA-CSR Connection Establishment + MS->>GANC: 2. GA-CSR UL DIRECT TRANSFER (CM Service Request) + GANC->>CN: 3. Complete Layer 3 Information (CM Service Request) + rect rgb(240, 240, 240) + Note over MS, CN: 4. Authentication + end + rect rgb(240, 240, 240) + Note over MS, CN: 5. Ciphering Configuration + end + MS->>CN: 6. GA-CSR UL DIRECT TRANSFER (Setup) + CN->>MS: 7. GA-CSR DL DIRECT TRANSFER (Call Proceeding) + CN->>GANC: 8. Assignment Request + GANC->>MS: 9. GA-CSR ACTIVATE CHANNEL + MS->>GANC: 10. Uplink user plane RTP stream + MS->>GANC: 11. GA-CSR ACTIVATE CHANNEL ACK + GANC->>MS: 12. Downlink user plane RTP stream + GANC->>CN: 13. Assignment Complete + GANC->>MS: 14. GA-CSR ACTIVATE CHANNEL COMPLETE + CN->>MS: 15. GA-CSR DL DIRECT TRANSFER (Alerting) + CN->>MS: 16. GA-CSR DL DIRECT TRANSFER (Connect) + MS->>CN: 17. GA-CSR UL DIRECT TRANSFER (Connect Ack) + MS->>GANC: 18. Voice traffic + GANC->>CN: 18. Voice traffic + +``` + +Sequence diagram for Mobile Originated Call Flow showing interactions between MS, GANC, and CN. + +Figure 22: Mobile Originated Call + +The description of the procedure in this sub-clause assumes the MS is in GAN A/Gb mode i.e. it has successfully registered with the GANC and GA-CSR is the serving RR entity in the MS. + +1. The GA-CSR Connection Establishment procedure is performed as described in clause 8.7.1. +2. Upon request from the upper layers, the MS sends the *CM Service Request* to the GANC in the GA-CSR UL DIRECT TRANSFER. +3. The GANC establishes an SCCP connection to the CN and forwards the *CM Service Request* to the CN using the *Complete Layer 3 Information*. Subsequent layer-3 messages between mobile station and core network will be sent between GANC and CN via DTAP. +4. The CN may optionally authenticate the MS using standard GERAN authentication procedures. +5. The CN may optionally initiate the Ciphering Configuration procedure described in clause 8.8. +6. The MS sends the *Setup* message providing details on the call to the CN and its bearer capability and supported codecs. This message is contained within the GA-CSR UL DIRECT TRANSFER between the MS and the GANC. The GANC forwards the *Setup* message to the CN. +7. The CN indicates it has received the call setup and it will accept no additional call-establishment information using the *Call Proceeding* message to the GANC. GANC forwards this message to the MS in the GA-CSR DL DIRECT TRANSFER. +8. The CN requests the GANC to assign call resources using *Assignment Request*. +9. The GANC sends the GA-CSR ACTIVATE CHANNEL to the MS including bearer path setup information such as: + - Channel mode. + - Multi-rate codec configuration. + - UDP port & the IP address for the uplink RTP stream. + - Voice sample size. + - An indication of whether RFC 4867 [54] octet-aligned mode (i.e., the default for GAN A/Gb mode) or bandwidth-efficient mode shall be used for the GA-CSR traffic channel. If an IP-based A-interface where bandwidth-efficient mode is used and the MS supports RFC 4867 bandwidth-efficient mode (see sub-clause 8.4.1.6), the GANC can enable "AoIP payload optimization" (i.e., avoiding the need for the GANC to do transcoding or conversion between RFC 4867 payload modes) by indicating that RFC 4867 bandwidth-efficient mode be used for the GA-CSR traffic channel. +10. The MS establishes the RTP path to the GANC. MS optionally sends idle RTP/UDP packets to the GANC but has not connected the user to the audio path. +11. The MS sends the GA-CSR ACTIVATE CHANNEL ACK to the GANC indicating the UDP port for the downlink RTP stream. +12. If a TDM-based A-interface channel is used for the call, the GANC establishes the downlink RTP path between itself and the MS. The GANC may start sending idle RTP/UDP packets to the MS. +13. The GANC signals to the CN that the call resources have been allocated by sending an *Assignment Complete* message. +14. The GANC signals the completion of the bearer path to the MS with the GA-CSR ACTIVATE CHANNEL COMPLETE message. An end-to-end audio path now exists between the MS and the CN. The MS can now connect the user to the audio path. +15. The CN signals to the MS, with the *Alerting* message, that the B-Party is ringing. The message is transferred to the GANC and GANC forwards the message to the MS in the GA-CSR DL DIRECT TRANSFER. If the MS has not connected the audio path to the user, it shall generate ring back to the calling party. Otherwise, the network-generated ring back will be returned to the calling party. + +16. The CN signals that the called party has answered, via the *Connect* message. The message is transferred to the GANC and GANC forwards the message to the MS in the GA-CSR DL DIRECT TRANSFER. It connects the user to the audio path. If the mobile station is generating ring back, it stops and connects the user to the audio path. +17. The MS sends the *Connect Ack* in response, and the two parties are connected for the voice call. This message is contained within the GA-CSR UL DIRECT TRANSFER between the MS and the GANC. The GANC forwards the *Connect Ack* message to the CN. +18. Bi-directional voice traffic flows between the MS and CN through the GANC. + +## 8.11 Mobile Terminated Call Flow + +![Sequence diagram of Mobile Terminated Call Flow between MS, GANC, and CN.](df1966d80c74bc127f159a48f38b13ee_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant CN + + Note right of CN: 1. Paging + CN->>GANC: + Note left of GANC: 2. GA-CSR PAGING REQUEST + GANC->>MS: + Note left of MS: 3. GA-CSR PAGING RESPONSE + MS->>GANC: + Note right of GANC: 4. Complete L3 Info (Paging Response) + GANC->>CN: + Note left of CN: 5. Authentication + Note left of CN: 6. Ciphering Configuration + Note right of CN: 7. GA-CSR DL DIRECT TRANSFER (Setup) + CN->>GANC: + Note left of GANC: 8. GA-CSR UL DIRECT TRANSFER (Call Confirmed) + GANC->>MS: + Note left of MS: 9. RTP stream setup + Note right of CN: Assignment procedure + CN->>GANC: + Note left of GANC: 10. GA-CSR UL DIRECT TRANSFER (Alerting) + GANC->>MS: + Note left of MS: 11. GA-CSR UL DIRECT TRANSFER (Connect) + GANC->>CN: + Note right of CN: 12. GA-CSR DL DIRECT TRANSFER (Connect Ack) + CN->>GANC: + Note left of GANC: 13. Voice traffic + GANC->>MS: + +``` + +Sequence diagram of Mobile Terminated Call Flow between MS, GANC, and CN. + +**Figure 23: Mobile Terminated Call** + +The description of the procedure in this clause assumes the MS is in GAN A/Gb mode i.e. it has successfully registered with the GANC and GA-CSR is the serving RR entity in the MS. + +1. A mobile-terminated call arrives at the CN. The CN sends a *Paging message* to the GANC identified through the last *Location Update* received by it and includes the TMSI if available. The IMSI of the mobile being paged is always included in the request. +2. GANC identifies the MS registration context using the IMSI provided by the CN. It then pages the MS using the GA-CSR PAGING REQUEST message. The message includes the TMSI, if available in the request from the CN, else it includes only the IMSI of the mobile. +3. The MS responds with a GA-CSR PAGING RESPONSE including the MS Classmark and ciphering key sequence number. The MS enters dedicated mode and the GA-CSR state changes to GA-CSR-DEDICATED. +4. The GANC establishes an SCCP connection to the CN. The GANC then forwards the paging response to the CN using the *Complete Layer 3 Information* message. +5. The CN may optionally authenticate the MS using standard GERAN authentication procedures. +6. The CN may optionally update the ciphering configuration in the MS, via the GANC, as described in clause 8.8. + +7. The CN initiates call setup using the *Setup* message sent to the MS via GANC. GANC forwards this message to the MS in the GA-CSR DL DIRECT TRANSFER message. +8. The MS responds with *Call Confirmed* using the GA-CSR UL DIRECT TRANSFER after checking its compatibility with the bearer service requested in the *Setup* and modifying the bearer service as needed. If the *Setup* included the signal information element, the MS alerts the user using the indicated signal, else the MS alerts the user after the successful configuration of the user plane. The GANC forwards the *Call Confirmed* message to the CN. +9. The CN initiates the assignment procedure with the GANC, which triggers the setup of the GA-CSR traffic channel, the same as steps 8-13 in the MO call scenario (see sub-clause 8.10). +10. The MS signals that it is alerting the user, via the *Alerting* message contained in the GA-CSR UL DIRECT TRANSFER. The GANC forwards the *Alerting* message to the CN. The CN sends a corresponding alerting message to the calling party. +11. The MS signals that the called party has answered, via the *Connect* message contained in the GA-CSR UL DIRECT TRANSFER. The GANC forwards the *Connect* message to the CN. The CN sends a corresponding *Connect* message to the calling party and through connects the audio. The MS connects the user to the audio path. +12. The CN acknowledges via the *Connect Ack* message to the GANC. GANC forwards this message to the MS in the GA-CSR DL DIRECT TRANSFER. The two parties on the call are connected on the audio path. +13. Bi-directional voice traffic flows between the MS and CN through the GANC. + +## 8.12 Call Clearing + +Figure 24 shows call clearing initiated by the mobile station. + +![Sequence diagram for Mobile Station initiated Call clearing. The diagram shows four steps: 1. MS sends GA-CSR UL DIRECT TRANSFER (Disconnect) to CN via GANC; 2. CN responds with GA-CSR DL DIRECT TRANSFER (Release) to GANC; 3. MS sends GA-CSR UL DIRECT TRANSFER (Release Complete) to CN via GANC; 4. GANC sends GA-CSR Connection Release to CN.](7722d62e33dcc894cc8555e9474c5606_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant CN + Note left of MS: MS initiates call clearing + MS->>CN: 1. GA-CSR UL DIRECT TRANSFER (Disconnect) + CN-->>GANC: 2. GA-CSR DL DIRECT TRANSFER (Release) + GANC-->>MS: 2. GA-CSR DL DIRECT TRANSFER (Release) + MS->>CN: 3. GA-CSR UL DIRECT TRANSFER (Release Complete) + Note right of MS: 4. GA-CSR Connection Release + GANC->>CN: 4. GA-CSR Connection Release + +``` + +Sequence diagram for Mobile Station initiated Call clearing. The diagram shows four steps: 1. MS sends GA-CSR UL DIRECT TRANSFER (Disconnect) to CN via GANC; 2. CN responds with GA-CSR DL DIRECT TRANSFER (Release) to GANC; 3. MS sends GA-CSR UL DIRECT TRANSFER (Release Complete) to CN via GANC; 4. GANC sends GA-CSR Connection Release to CN. + +**Figure 24: Mobile Station initiated Call clearing** + +1. The MS sends the *Disconnect* message to the CN to release the call. This message is contained in the GA-CSR UL DIRECT TRANSFER message between MS and GANC. The GANC forwards the *Disconnect* message to the CN. +2. The CN responds with a *Release* message to the GANC. The GANC forwards this message to the MS using the GA-CSR DL DIRECT TRANSFER message. +3. The MS responds with the *Release Complete* message. This message is contained within the GA-CSR UL DIRECT TRANSFER message between MS and GANC. The GANC forwards the *Disconnect* message to the CN. +4. The CN triggers the release of connection as described in clause 8.7.2. + +## 8.13 Channel Modify + +The GANC may use the Channel Modify procedures to modify parameters used for an ongoing call, this procedure may be used if coding scheme should be changed, in fault or congestion situations if the GANC for example detects "packet loss" and Handover to another GERAN/UTRAN mode is not possible or desired. + +The GANC may modify the following parameters: + +- Channel mode. +- Sample Size. +- IP address. +- RTP UDP port. +- RTCP UDP port. + +![Sequence diagram for Channel Mode Modify](fe7304192caf64cda93b580c5e7e5c06_img.jpg) + +A sequence diagram illustrating the 'Channel Mode Modify' procedure. It features three lifelines: MS (Mobile Station), GANC (GAN Controller), and CN (Core Network). The sequence of messages is as follows: 1. Call establishment (a horizontal bar spanning all three lifelines); 2. GA-CSR CHANNEL MODE MODIFY (an arrow from GANC to MS); 3. GA-CSR CHANNEL MODE MODIFY ACKNOWLEDGE (an arrow from MS to GANC). + +Sequence diagram for Channel Mode Modify + +**Figure 25: Channel Mode Modify** + +1. A call is established as described in clauses 8.10 or 8.11. +2. The GANC sends the GA-CSR CHANNEL MODE MODIFY message to the MS to modify parameters for the established call. +3. The MS responds with the GA-CSR CHANNEL MODE MODIFY ACKNOWLEDGE message to the GANC. + +## 8.14 CS Handover between GAN A/Gb mode and GERAN/UTRAN mode + +### 8.14.1 CS Handover to GAN A/Gb mode + +#### 8.14.1.1 GERAN to GAN CS Handover + +![Sequence diagram for GERAN to GAN CS Handover. Lifelines: MS (with GAN Registered), GANC, BSC, and CN. The sequence shows 14 steps: 1. Um: Measurement Report (MS to BSC), 2. Handover Required (BSC to CN), 3. Handover Request (CN to GANC), 4. Handover Request Acknowledge (GANC to CN), 5. Handover Command (CN to BSC), 6. Um: Handover Command (BSC to MS), 7. GA-CSR HANDOVER ACCESS (MS to GANC), 8. RTP stream setup (MS to GANC), 9. GA-CSR HANDOVER COMPLETE (MS to GANC), 10. Handover Detect (GANC to CN), 11. Voice traffic (GANC to MS), 12. Handover Complete (GANC to CN), 13. Clear Command (CN to BSC), 14. Clear Complete (BSC to CN). Step 6 is highlighted with a red arrow.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant BSC + participant CN + Note left of MS: GAN Registered + MS->>BSC: 1. Um: Measurement Report + BSC->>CN: 2. Handover Required + CN->>GANC: 3. Handover Request + GANC->>CN: 4. Handover Request Acknowledge + CN->>BSC: 5. Handover Command + BSC->>MS: 6. Um: Handover Command + MS->>GANC: 7. GA-CSR HANDOVER ACCESS + MS->>GANC: 8. RTP stream setup + MS->>GANC: 9. GA-CSR HANDOVER COMPLETE + GANC->>CN: 10. Handover Detect + GANC->>MS: 11. Voice traffic + GANC->>CN: 12. Handover Complete + CN->>BSC: 13. Clear Command + BSC->>CN: 14. Clear Complete + +``` + +Sequence diagram for GERAN to GAN CS Handover. Lifelines: MS (with GAN Registered), GANC, BSC, and CN. The sequence shows 14 steps: 1. Um: Measurement Report (MS to BSC), 2. Handover Required (BSC to CN), 3. Handover Request (CN to GANC), 4. Handover Request Acknowledge (GANC to CN), 5. Handover Command (CN to BSC), 6. Um: Handover Command (BSC to MS), 7. GA-CSR HANDOVER ACCESS (MS to GANC), 8. RTP stream setup (MS to GANC), 9. GA-CSR HANDOVER COMPLETE (MS to GANC), 10. Handover Detect (GANC to CN), 11. Voice traffic (GANC to MS), 12. Handover Complete (GANC to CN), 13. Clear Command (CN to BSC), 14. Clear Complete (BSC to CN). Step 6 is highlighted with a red arrow. + +**Figure 26: GERAN to GAN CS Handover** + +The description of the GERAN to GAN CS handover procedure assumes the following: + +- the MS is on an active call on the GERAN; and + - its mode selection is GAN-preferred, or if GERAN/UTRAN/E-UTRAN-preferred the RxLev from the current serving cell drops below a MS implementation specific threshold; and + - the MS has successfully registered with a GANC, allowing the MS to obtain GAN system information; and + - the GERAN provides information on neighbouring cells such that one of the {ARFCN, BSIC} in the neighbour list matches the {ARFCN, BSIC} associated with the GANC, as provided in the AS-related component of the system information obtained from GANC. +- The MS begins to include GAN cell information in the *Measurement Report message* to the GERAN. The MS reports the highest signal level for the GAN cell {ARFCN, BSIC}. This is not the actual measured signal level on GAN, rather an artificial value (i.e. RxLev = 63), allowing the MS to indicate preference for the GAN. + - Based on MS measurement reports and other internal algorithms, GERAN decides to handover to the GAN cell, using an internal mapping of {ARFCN, BSIC} to CGI. The GERAN starts the handover preparation by sending a *Handover Required* message to the CN, identifying the target (GAN) cell. + - The CN requests the target GANC to allocate resources for the handover, using *Handover Request message*. + - The target GANC acknowledges the *Handover Request* message, using *Handover Request Acknowledge* message, indicating it can support the requested handover, and provides a *Handover Command message* that indicates the radio channel to which the mobile station should be directed. + - The CN forwards the *Handover Command* message to the GERAN, completing the handover preparation. + - GERAN sends *Handover Command* message to the MS to initiate handover to GAN. The *Handover Command message* includes among other parameters information about the target GAN such as BCCH ARFCN, PLMN colour code and BSIC. The MS does not switch its audio path from GERAN to GAN until handover + +completion, i.e. until it sends the GA-CSR HANDOVER COMPLETE message, to keep the audio interruption short. + +7. The MS accesses the GANC using the GA-CSR HANDOVER ACCESS message, and provides the entire *Handover Command* message received from GERAN. Information in the Handover Command message (e.g. Handover Reference) allows the GANC to correlate the handover to the *Handover Request Acknowledge* message earlier sent to the CN and identify the successful completion of the handover. +8. The GANC sets up the bearer path with the MS, using the same steps as in steps 9 to 14 of Mobile Originated Call Flow as defined in sub-clause 8.10. +9. The MS transmits the GA-CSR HANDOVER COMPLETE message to indicate the completion of the handover procedure at its end. It switches the user from the GERAN user plane to the GAN user plane. +10. The GANC indicates to the CN that it has detected the MS, using *Handover Detect* message. The CN can optionally now switch the user plane from the source GERAN to the target GAN. +11. Bi-directional voice traffic is now flowing between the MS and CN, via GANC. +12. The target GANC indicates the handover is complete, using the *Handover Complete* message. If it had not done so before, the CN now switches the user plane from source GERAN to target GAN. The CN may use the target CGI used in the Handover procedure for charging purposes. +13. Finally, the CN tears down the connection to the source GERAN, using *Clear Command* message. +14. The source GERAN confirms the release of GERAN resources allocated for this call, using *Clear Complete* message. + +#### 8.14.1.2 UTRAN to GAN CS Handover + +![Sequence diagram for UTRAN to GAN CS Handover showing interactions between MS, GANC, RNC, and CN.](ef5f5c6665b6ae13660ede412333ba45_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant RNC + participant CN + + Note over MS: GAN Registered + MS->>RNC: 1. Uu: Measurement Report + RNC->>CN: 2. Relocation Required + CN->>GANC: 3. Handover Request + GANC->>CN: 4. Handover Request Acknowledge + CN->>RNC: 5. Relocation Command + RNC->>MS: 6. Uu: Handover from UTRAN command + MS->>GANC: 7. GA-CSR HANDOVER ACCESS + GANC->>MS: 8. RTP stream setup + MS->>GANC: 9. GA-CSR HANDOVER COMPLETE + GANC->>CN: 10. Handover Detect + MS<->CN: 11. Voice traffic + GANC->>CN: 12. Handover Complete + CN->>RNC: 13. Iu Release Cmd + RNC->>CN: 14. Iu Release Cmp + +``` + +Sequence diagram for UTRAN to GAN CS Handover showing interactions between MS, GANC, RNC, and CN. + +Figure 26b: UTRAN to GAN CS Handover + +The description of the UTRAN to GAN CS Handover procedure assumes the following: + +- the MS is on an active call on the UTRAN; and + - the MS has included the *Support of Handover to GAN* indication in the UE RAC; and + - the UE has been ordered by the RNC to make inter-RAT measurements, and + - if the MS is in GAN preferred mode with an Event 3A configured, the MS handles parameters associated with the Event 3A in a GAN specific manner (as described in 3GPP TS 44.318) for the reporting of the GAN cell {ARFCN, BSIC}; and + - when the UE is in GERAN/UTRAN/E-UTRAN-preferred mode and an event 3A has been configured for the GAN cell (and possibly for GERAN cells), the UE shall only send a measurement about the GAN cell, when this event is triggered and no GERAN cells from the neighbour cell list of the UE satisfy the triggering condition of this Event (as described in 3GPP TS 25.331); + - the UTRAN provides information on neighbouring cells such that one of the {ARFCN, BSIC} in the neighbour list matches the {ARFCN, BSIC} associated with the GANC, as provided in the AS-related component of the system information obtained from GANC. The selection of the RF channel numbers (ARFCNs) used for the UTRAN to GAN handover procedure should not correspond to a channel from a frequency band supported by any UE, to avoid UEs that do not require compressed mode from unnecessarily powering up their GSM receivers. +1. The MS begins to include information about a GAN cell in the *Measurement Report message sent* to the RNC. The MS reports the highest signal level for the GAN cell {ARFCN, BSIC}. This is not the actual measured signal level on GAN, rather an artificial value (i.e., GSM carrier RSSI = 63) allowing the UE to indicate preference for the GAN. + 2. Based on MS measurement reports and other internal algorithms, the RNC decides to initiate handover to the GAN cell, using an internal mapping of {ARFCN, BSIC} to CGI. The RNC starts the preparation phase of the Relocation procedure by sending a *Relocation Required* message to the CN, identifying the target (GAN) cell. + 3. The CN requests the target GANC to allocate resources for the handover, using *Handover Request message*. + 4. The target GANC acknowledges the handover request message, using *Handover Request Acknowledge message*, indicating it can support the requested handover, and including a *Handover Command message* that indicates the radio channel to which the mobile station should be directed. + 5. The CN sends the *Relocation Command* message to the RNC, completing the relocation preparation. + 6. The RNC sends *HANDOVER FROM UTRAN COMMAND message* to the MS to initiate handover to GAN. The *HANDOVER FROM UTRAN COMMAND message* includes the RR HANDOVER COMMAND message, specified in 44.018, which contains other parameters about the target GAN such as BCCH ARFCN, PLMN colour code and BSIC. The MS does not switch its audio path from UTRAN to GAN until handover completion, i.e. until it sends the GA-CSR HANDOVER COMPLETE message, to keep the audio interruption short. + 7. The MS accesses the GANC using the GA-CSR HANDOVER ACCESS message, and provides the entire *HANDOVER FROM UTRAN COMMAND* received from RNC. The handover reference in the *HANDOVER FROM UTRAN COMMAND* message allows the GANC to correlate the handover to the *Handover Request Acknowledge* message earlier sent to the CN and identify the successful completion of the handover. + 8. The GANC sets up the bearer path with the MS, using the same steps as in steps 9 to 14 of Mobile Originated Call Flow as defined in sub-clause 8.10. + 9. The MS transmits the GA-CSR HANDOVER COMPLETE to indicate the completion of the handover procedure from its perspective. It switches the user from the UTRAN user plane to the GAN user plane. + 10. The GANC indicates to the CN that it has detected the MS, using *Handover Detect* message. The CN can optionally now switch the user plane from the source RNC to the target GANC. + 11. Bi-directional voice traffic is now flowing between the MS and CN, via GANC. + +12. The target GANC indicates the handover is complete, using the *Handover Complete* message. If it has not done so before, the CN now switches the user plane from source RNC to target GAN. +13. Finally, the CN tears down the connection to the source RNC, using *Iu Release Command*. +14. The source RNC confirms the release of UTRAN resources allocated for this call, using *Iu Release Complete*. + +### 8.14.2 CS Handover from GAN A/Gb mode to GERAN + +![Sequence diagram for CS Handover from GAN A/Gb mode to GERAN. The diagram shows the interaction between MS, GANC, BSS, and MSC. The MS has an ongoing GAN CS connection. The sequence starts with the MS sending a GA-CSR UPLINK QUALITY INDICATION to the GANC. The GANC then sends a GA-CSR HANDOVER INFORMATION to the MS. The GANC sends a Handover Required to the MSC. The MSC sends a Handover Request to the BSS. The BSS sends a Handover Request Ack to the MSC. The MSC sends a Handover Command to the GANC. The GANC sends a GA-CSR HANDOVER COMMAND to the MS. The MS sends an Um: Handover Access to the BSS. The BSS sends a Handover Detect to the MSC. The MSC sends a Voice to the BSS. The BSS sends an Um: Physical Information to the MS. The MS sends an Um: Handover Complete to the BSS. The BSS sends a Handover Complete to the MSC. The MSC switches the voice traffic to the BSS. The MSC sends a Release Command to the GANC. The GANC sends a GA-CSR RELEASE to the MS. The GANC sends a Release Complete to the MSC. The MS sends a GA-CSR RELEASE COMPLETE to the GANC. The MS sends a GA-RC DEREGISTER to the GANC.](28085f681b9fff76a53c5b8b32338ee1_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant BSS + participant MSC + Note left of MS: Ongoing GAN CS connection + MS->>GANC: 1. GA-CSR UPLINK QUALITY INDICATION + GANC-->>MS: 2. GA-CSR HANDOVER INFORMATION + GANC->>MSC: 3. Handover Required + MSC->>BSS: 4. Handover Request + BSS->>MSC: 5. Handover Request Ack + MSC->>GANC: 6. Handover Command + GANC->>MS: 7. GA-CSR HANDOVER COMMAND + MS->>BSS: 8. Um: Handover Access + BSS->>MSC: 9. Handover Detect + MSC->>BSS: 10. Voice + BSS->>MS: 11. Um: Physical Information + MS->>BSS: 12. Um: Handover Complete + BSS->>MSC: 13. Handover Complete + Note right of MSC: Voice traffic switch + MSC->>GANC: 15. Release Command + GANC->>MS: 16. GA-CSR RELEASE + GANC->>MSC: 17. Release Complete + MS->>GANC: 18. GA-CSR RELEASE COMPLETE + MS->>GANC: 19. GA-RC DEREGISTER + +``` + +Sequence diagram for CS Handover from GAN A/Gb mode to GERAN. The diagram shows the interaction between MS, GANC, BSS, and MSC. The MS has an ongoing GAN CS connection. The sequence starts with the MS sending a GA-CSR UPLINK QUALITY INDICATION to the GANC. The GANC then sends a GA-CSR HANDOVER INFORMATION to the MS. The GANC sends a Handover Required to the MSC. The MSC sends a Handover Request to the BSS. The BSS sends a Handover Request Ack to the MSC. The MSC sends a Handover Command to the GANC. The GANC sends a GA-CSR HANDOVER COMMAND to the MS. The MS sends an Um: Handover Access to the BSS. The BSS sends a Handover Detect to the MSC. The MSC sends a Voice to the BSS. The BSS sends an Um: Physical Information to the MS. The MS sends an Um: Handover Complete to the BSS. The BSS sends a Handover Complete to the MSC. The MSC switches the voice traffic to the BSS. The MSC sends a Release Command to the GANC. The GANC sends a GA-CSR RELEASE to the MS. The GANC sends a Release Complete to the MSC. The MS sends a GA-CSR RELEASE COMPLETE to the GANC. The MS sends a GA-RC DEREGISTER to the GANC. + +**Figure 27: CS Handover from GAN A/Gb mode to GERAN** + +The procedure description in this sub-clause assumes the following: + +- the MS is on an active call on the GAN A/Gb mode; and +- the GERAN becomes available; and + - the MS mode selection is GERAN/UTRAN/E-UTRAN-preferred; or +- the MS mode selection is GAN-preferred and the MS begins to leave GAN coverage, based on its local measurements, received RTCP reports, as well as any uplink quality indications received from the GANC. + +The handover from GAN to GERAN procedure is always triggered by the MS. + +1. The GANC may send a GA-CSR UPLINK QUALITY INDICATION if there is a problem with the uplink quality for the ongoing call. Uplink Quality Indication is information sent by the GANC to the MS indicating the crossing of a uplink quality threshold in the uplink direction. Whenever the MS receives an indication of bad quality, it should start the handover procedure, as described in the next step. Alternatively, MS can use its local measurements or received RTCP reports, to decide to initiate the handover procedure. +2. The MS sends the GA-CSR HANDOVER INFORMATION message to the GANC including a list of target GERAN cells, identified by CGI, in order of preference (e.g. ranked by C1 path loss parameter) for handover, and the received signal strength for each identified GERAN cell. This list is the most recent information available from the GSM RR subsystem. In addition, the GA-CSR HANDOVER INFORMATION message may include a list of target UTRAN cells ranked in order of preference for handover, and the received signal strength for each identified UTRAN cell. +3. If the Serving GANC selects a target GERAN cell, the handover to GERAN procedure is performed. The Serving GANC starts the handover preparation by signalling to the CN the need for handover, using *Handover Required*, and including the GERAN cell list provided by the MS. The GANC may include only a subset of the cell list provided by the MS. +4. The CN selects a target GERAN cell and requests it to allocate the necessary resources, using *Handover Request*. +5. The target GERAN builds a GERAN RRC *Handover Command* message providing information on the channel allocated and sends it to the CN through the *Handover Request Acknowledge* message. +6. The CN signals the GANC to handover the MS to the GERAN, using *Handover Command* message, ending the handover preparation phase. +7. GANC transmits the GA-CSR HANDOVER COMMAND to the MS including the Handover from GAN Command IE. The Handover from GAN Command IE encapsulates the GERAN RRC *Handover Command* message. +8. The MS transmits *Handover Access* containing the handover reference element to allow the target GERAN to correlate this handover access with the *Handover Command* message transmitted earlier to the CN in response to the *Handover Required*. +9. The target GERAN confirms the detection of the handover to the CN, using the *Handover Detect* message. +10. The CN may at this point switch the user plane to the target BSS. +11. The GERAN provides *Physical Information* to the MS i.e. *Timing Advance*, to allow the MS to synchronize with the GERAN. +12. The MS signals to the GERAN that the handover is completed, using *Handover Complete*. +13. The GERAN confirms to the CN the completion of the handover, via *Handover Complete* message. The CN may use the target CGI used in the Handover procedure for charging purposes. +14. Bi-directional voice traffic is now flowing between the MS and CN, via the GERAN. +15. On receiving the confirmation of the completion of the handover, the CN indicates to the GANC to release any resources allocated to the MS, via the *Clear Command*. +16. If the GANC has not already received the GA-RC DEREGISTER message from the MS, the GANC commands the MS to release resources, using the GA-CSR RELEASE message. +17. GANC confirms resource release to CN using the *Clear Complete* message. +18. The MS confirms resource release to the GANC using the GA-CSR RELEASE COMPLETE message. +19. The MS may finally deregister from the GANC, using the GA-RC DEREGISTER message. Note that the MS may send the GA-RC DEREGISTER message at any time after transitioning from GAN A/Gb mode to GERAN mode (i.e., after step 12). + +### 8.14.3 CS Handover from GAN A/Gb mode to UTRAN + +![Sequence diagram for CS Handover from GAN A/Gb mode to UTRAN. The diagram shows the interaction between MS, GANC, RNS, and CN. The process starts with an ongoing GAN CS connection on the MS. The MS sends a GA-CSR UPLINK QUALITY INDICATION to the GANC. The GANC sends a GA-CSR HANDOVER INFORMATION to the MS. The GANC then sends a Handover Required to the CN. The CN sends a Relocation Request to the RNS. The RNS sends a Relocation Request Ack to the CN. The CN sends a Handover Command to the GANC. The GANC sends a GA-CSR HANDOVER COMMAND to the MS. The MS sends a Uu: UL Synchronization to the RNS. The RNS sends a Relocation Detect to the CN. The CN sends a Voice to the RNS. The RNS sends a Uu: Handover to UTRAN Complete to the MS. The RNS sends a Relocation Complete to the CN. The CN sends a Voice traffic to the MS. The CN sends a Release Command to the GANC. The GANC sends a GA-CSR RELEASE to the MS. The GANC sends a Release Complete to the CN. The MS sends a GA-CSR RELEASE COMPLETE to the GANC. The MS sends a GA-RC DEREGISTER to the GANC.](50ef8602c7c9edd2da0e2133e772c2a2_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant RNS + participant CN + + Note left of MS: Ongoing GAN CS connection + MS->>GANC: 1. GA-CSR UPLINK QUALITY INDICATION + GANC-->>MS: 2. GA-CSR HANDOVER INFORMATION + GANC->>CN: 3. Handover Required + CN->>RNS: 4. Relocation Request + RNS-->>CN: 5. Relocation Request Ack + CN->>GANC: 6. Handover Command + GANC-->>MS: 7. GA-CSR HANDOVER COMMAND + MS->>RNS: 8. Uu: UL Synchronization + RNS->>CN: 9. Relocation Detect + CN-->>RNS: 10. Voice + RNS-->>MS: 11. Uu: Handover to UTRAN Complete + RNS->>CN: 12. Relocation Complete + CN-->>MS: 13. Voice traffic + CN->>GANC: 14. Release Command + GANC-->>MS: 15. GA-CSR RELEASE + GANC->>CN: 16. Release Complete + MS->>GANC: 17. GA-CSR RELEASE COMPLETE + MS->>GANC: 18. GA-RC DEREGISTER + +``` + +Sequence diagram for CS Handover from GAN A/Gb mode to UTRAN. The diagram shows the interaction between MS, GANC, RNS, and CN. The process starts with an ongoing GAN CS connection on the MS. The MS sends a GA-CSR UPLINK QUALITY INDICATION to the GANC. The GANC sends a GA-CSR HANDOVER INFORMATION to the MS. The GANC then sends a Handover Required to the CN. The CN sends a Relocation Request to the RNS. The RNS sends a Relocation Request Ack to the CN. The CN sends a Handover Command to the GANC. The GANC sends a GA-CSR HANDOVER COMMAND to the MS. The MS sends a Uu: UL Synchronization to the RNS. The RNS sends a Relocation Detect to the CN. The CN sends a Voice to the RNS. The RNS sends a Uu: Handover to UTRAN Complete to the MS. The RNS sends a Relocation Complete to the CN. The CN sends a Voice traffic to the MS. The CN sends a Release Command to the GANC. The GANC sends a GA-CSR RELEASE to the MS. The GANC sends a Release Complete to the CN. The MS sends a GA-CSR RELEASE COMPLETE to the GANC. The MS sends a GA-RC DEREGISTER to the GANC. + +**Figure 28: CS Handover from GAN A/Gb mode to UTRAN** + +The procedure description in this sub-clause assumes the following: + +- the MS is on an active call on the GAN A/Gb mode; and +- the MS is capable of operating in all of the GAN A/Gb, GERAN and UTRAN modes; and +- the UTRAN becomes available; and + - the MS is in GERAN/UTRAN/E-UTRAN-preferred mode; or + - the MS mode selection is GAN preferred and begins to leave GAN coverage, based on its local measurements, received RTCP reports, as well as any uplink quality indications received from the GANC. + +The Inter-RAT handover from GAN procedure is always triggered by the MS. + +1. The GANC may send a GA-CSR UPLINK QUALITY INDICATION if there is a problem with the uplink quality for the ongoing call. Uplink Quality Indication is information sent by the GANC to the MS indicating the crossing of a uplink quality threshold in the uplink direction. Whenever the MS receives an indication of bad quality, it should start the handover procedure, as described in the next step. Alternatively, MS can use its local measurements or received RTCP reports, to decide to initiate the handover procedure. + +2. The MS sends the GA-CSR HANDOVER INFORMATION message to the Serving GANC including a list of candidate target UTRAN and GERAN cells, in order of preference for handover, and includes the received signal strength for each identified cell. The UTRAN cells are identified by the PLMN ID, the LAC and the 3G Cell identity (defined in 3GPP TS 25.331 [40]). + +NOTE: The choice of the candidate target UTRAN cells is out of the scope of this technical specification. + +3. If the Serving GANC selects UTRAN as a target RAT, the inter-RAT handover procedure is performed. The Serving GANC starts the handover preparation by signaling to the CN the need for handover, using *Handover Required* and including the target RNC-ID that the GANC derives from the target UTRAN cell it selects from the list of candidate target UTRAN cells provided by the MS. The GANC may include only a single RNC-ID in the *Handover Required* message. The GANC also includes the Source RNC to Target RNC Transparent Container that contains the selected target UTRAN cell ID. +4. The CN starts the inter-RAT handover procedure towards the target RNC identified by the Serving GANC. The CN requests from the target RNS to allocate the necessary resources using *Relocation Request*. +5. The target UTRAN builds a UTRAN RRC *Handover to UTRAN Command* message providing information on the allocated UTRAN resources and sends it to the CN through the *Relocation Request Acknowledge* message. +6. The CN signals the Serving GANC to handover the MS to the UTRAN, using *Handover Command* message (which includes the UTRAN RRC *Handover to UTRAN Command* message), ending the handover preparation phase. +7. The Serving GANC transmits the GA-CSR HANDOVER COMMAND to the MS including the Handover from GAN Command IE. The Handover from GAN Command IE includes the GERAN RRC *Inter System to UTRAN Handover Command* message, which encapsulates the UTRAN RRC *Handover to UTRAN Command* message. +8. Target RNS achieves uplink synchronization on the Uu interface. +9. The target UTRAN confirms the detection of the handover to the CN, using the *Relocation Detect* message. +10. The CN may at this point switch the user plane to the target RNS. +11. The MS signals to the UTRAN that the handover is completed, using *Handover to UTRAN Complete*. +12. The UTRAN confirms to the CN the completion of the handover, via *Relocation Complete* message. If the user plane has not been switched in step 10, the CN switches the user plane to the target RNS. +13. Bi-directional voice traffic is now flowing between the MS and CN, via the UTRAN. +14. On receiving the confirmation of the completion of the handover, the CN indicates to the Serving GANC to release any resources allocated to the MS, via the *Clear Command*. +15. If the Serving GANC has not already received the GA-RC DEREGISTER message from the MS, the Serving GANC commands the MS to release resources, using the GA-CSR RELEASE message. +16. The Serving GANC confirms resource release to CN using the *Clear Complete* message. +17. The MS confirms resource release to the Serving GANC using the GA-CSR RELEASE COMPLETE message. +18. The MS may finally deregister from the Serving GANC, using GA-RC DEREGISTER message. Note that the MS may send the GA-RC DEREGISTER message at any time after transitioning from GAN A/Gb mode to UTRAN mode (i.e., after step 11). + +## 8.15 Cell Change Order between GAN A/Gb mode and GERAN/UTRAN mode + +While in GERAN/UTRAN, a mobile station may be ordered to perform a cell reselection to GAN A/Gb mode, by using the Cell Change Order procedures used in GERAN/UTRAN, with no modifications. The mobile station regards the procedure as completed when it has successfully performed Rove In to GAN. + +While the mobile station is involved in a PS session in the GAN A/Gb mode, there is no identified need for a Cell Change Order procedure. + +## 8.16 GA-PSR Transport Channel Management Procedures + +The GA-PSR Transport Channel (GA-PSR TC) management procedures are the basic GA-PSR procedures specified to facilitate the control of the GA-PSR connection for the user data transfer. A UDP based GA-PSR connection between the MS and the GANC for GPRS data transfer is referred to as the GA-PSR Transport Channel. + +The GA-PSR Transport Channel consists of the following: + +- The IP address and destination UDP port number to be used for GPRS data transfer at both the GANC and MS. +- The GA-PSR Channel Timer. + +The MS or GANC will activate a GA-PSR Transport Channel only when needed; i.e. when the GPRS user data transfer is initiated. + +The GA-PSR can be in two different states, GA-PSR-STANDBY or GA-PSR-ACTIVE state. The state of the GA-PSR and the corresponding transport channel are always synchronized. + +- In GA-PSR-STANDBY state: + - The MS is not able to send or receive GPRS data to and from the GANC. The GANC or the MS needs to activate the GA-PSR Transport Channel before sending any GPRS data. + - A corresponding GA-PSR Transport Channel does not exist. When the GA-PSR Transport Channel is activated, the MS enters the GA-PSR-ACTIVE state. +- In GA-PSR-ACTIVE state: + - The MS is able to send and receive GPRS data to and from the GANC. Furthermore there exists a corresponding GA-PSR Transport Channel for this MS. + +A GA-PSR Channel Timer is also defined to control the transition from GA-PSR-ACTIVE to GA-PSR-STANDBY state as follows: + +- The MS GA-PSR layer implements a timer that is started when the MS enters GA-PSR-ACTIVE state and restarted each time a LLC-PDU is transmitted to or received from the network. When the timer expires, the MS deactivates the GA-PSR Transport Channel and the MS GA-PSR enters GA-PSR-STANDBY state. + +The GA-PSR Channel Timer value is returned to the MS as part of the GAN Registration procedure (i.e. in GA-RC REGISTER ACCEPT message). + +### 8.16.1 MS initiated Activation of GA-PSR Transport Channel + +Figure 29 depicts the MS initiated GA-PSR Transport Channel activation procedure. The basic idea is that the GANC and MS can dynamically negotiate the IP address and UDP port numbers for data transfer. This procedure can facilitate the GANC load balancing; moreover, it allows the GANC to optimize the processing and maintain the context for active users only. + +![Sequence diagram showing the activation of the GA-PSR Transport Channel between MS and GANC.](575d7d345b3ec04393bb2ec720ebabca_img.jpg) + +``` +sequenceDiagram + participant MS + participant GANC + Note left of MS: The uplink data transfer is initiated triggering the MS to activate GA-PSR TC + MS->>GANC: 1. GA-PSR ACTIVATE UTC REQ (MS UDP port) + GANC-->>MS: 2. GA-PSR ACTIVATE UTC ACK (GANC IP address, GANC UDP port) + MS->>GANC: 3. GA-PSR UNITDATA (TLLI, PFI, priority, LLC-PDU) + GANC-->>MS: 4. GA-PSR UNITDATA (TLLI, PFI, LLC-PDU) +``` + +The diagram illustrates the activation of the GA-PSR Transport Channel. It begins with a box labeled 'MS' and another labeled 'GANC'. A note below the MS box states: 'The uplink data transfer is initiated triggering the MS to activate GA-PSR TC'. The sequence of messages is: 1. GA-PSR ACTIVATE UTC REQ (MS UDP port) from MS to GANC; 2. GA-PSR ACTIVATE UTC ACK (GANC IP address, GANC UDP port) from GANC to MS; 3. GA-PSR UNITDATA (TLLI, PFI, priority, LLC-PDU) from MS to GANC; 4. GA-PSR UNITDATA (TLLI, PFI, LLC-PDU) from GANC to MS. + +Sequence diagram showing the activation of the GA-PSR Transport Channel between MS and GANC. + +**Figure 29: Activation of GA-PSR Transport Channel** + +Initially, the MS GA-PSR is in the GA-PSR-STANDBY state as the LLC layer requests the transfer of one or more uplink LLC-PDUs. As the MS GA-PSR is in GA-PSR-STANDBY state, the corresponding GA-PSR Transport Channel does not exist. This is a trigger for the MS to activate the GA-PSR Transport Channel (TC). + +1. The GA-PSR-layer sends a GA-PSR ACTIVATE UTC REQ message to the GANC to request the activation of the GA-PSR Transport Channel. This message contains MS UDP port number that the GANC can use for the downlink transfer. +2. The GANC replies with a GA-PSR ACTIVATE UTC ACK message that contains the IP-address and the UDP port number to be used for the uplink user data transfer. Upon receiving the acknowledgment, the MS GA-PSR transitions to GA-PSR-ACTIVE state. +3. After successful GA-PSR TC activation, the MS forwards the LLC-PDU to the GANC IP-address and UDP-port received in the acknowledgment message using GA-PSR UNITDATA message. The GANC forwards the LLC-PDU and other parameters to the core network as per procedure described in clause 8.17.2.3 (not shown in the sequence). The MS restarts the GA-PSR Channel Timer. +4. The GANC receives a downlink user data message for the MS as per procedure described in clause 8.17.2.2 (not shown in the sequence) while the GA-PSR TC is still active. The LLC-PDU and the required parameters are sent to the MS encapsulated in a GA-PSR UNITDATA message using the associated GA-PSR Transport Channel information (MS IP-address and UDP-port received in step 1). + +### 8.16.2 MS initiated Deactivation of the GA-PSR Transport Channel + +The following message sequence depicts the scenario when the MS deactivates the GA-PSR Transport Channel after the GA-PSR Channel Timer expires. In addition, when a PS handover from *GAN A/Gb mode* to *GERAN/UTRAN mode* is successfully completed both the GANC and the MS shall consider the GA-PSR Transport Channel as implicitly deactivated and the MS shall stop the GA-PSR Channel Timer. + +![Sequence diagram showing the deactivation of the GA-PSR Transport Channel between MS and GANC.](06291c5328a7a4335d41a48850a3a207_img.jpg) + +``` +sequenceDiagram + participant MS + participant GANC + Note left of MS: GA-PSR Channel Timer expires + MS->>GANC: 1. GA-PSR DEACTIVATE UTC REQ (Cause) + GANC-->>MS: 2. GA-PSR DEACTIVATE UTC ACK +``` + +The diagram illustrates the deactivation of the GA-PSR Transport Channel. It begins with a box labeled 'MS' and another labeled 'GANC'. A note below the MS box states: 'GA-PSR Channel Timer expires'. The sequence of messages is: 1. GA-PSR DEACTIVATE UTC REQ (Cause) from MS to GANC; 2. GA-PSR DEACTIVATE UTC ACK from GANC to MS. + +Sequence diagram showing the deactivation of the GA-PSR Transport Channel between MS and GANC. + +**Figure 30: Deactivation of GA-PSR Transport Channel** + +1. GA-PSR-layer in the MS sends the GA-PSR DEACTIVATE UTC REQ message to the GANC to request the deactivation of the GA-PSR Transport Channel. The message includes cause parameter to indicate "normal deactivation". +2. The GANC deletes the related MS information associated with the GA-PSR Transport Channel and replies to the MS with a GA-PSR DEACTIVATE UTC ACK message. Upon receiving the acknowledgment message, the MS enters GA-PSR-STANDBY state. + +### 8.16.3 Implicit Deactivation of the GA-PSR Transport Channel due to MS Deregistration + +When a GA-RC DEREGISTER message is received by the GANC or if the MS is implicitly deregistered, the GA-PSR Transport Channel associated with the MS, if any, is automatically released by the GANC. + +### 8.16.4 Network initiated GA-PSR Transport Channel Activation + +Figure 31 depicts a scenario when the GANC activates a GA-PSR Transport Channel for a GAN registered MS. This scenario covers the following cases: + +- The GANC receives a downlink user data packet (LLC PDU) from the core network and the specified MS does not have an active GA-PSR Transport Channel. +- PS Handover to GAN A/Gb mode is initiated in support of one or more PS domain services. + +![Sequence diagram showing Network initiated GA-PSR Transport Channel Activation between MS and GANC. The diagram includes four steps: 1. GA-PSR ACTIVATE UTC REQ (GANC IP address, GANC UDP port) from GANC to MS; 2. GA-PSR ACTIVATE UTC ACK (MS UDP port) from MS to GANC; 3. GA-PSR UNITDATA (TLLI, PFI, LLC-PDU) from GANC to MS; 4. GA-PSR UNITDATA (TLLI, PFI, priority, LLC-PDU) from GANC to MS. A callout box indicates that downlink data transfer is initiated for an MS in GA-PSR Standby state or when PS Handover to GAN mode is initiated.](921458d4fc1b778c2450592ac9745b48_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note right of GANC: The downlink data transfer is initiated for an MS in GA-PSR Standby state or PS Handover to GAN mode is initiated + GANC->>MS: 1. GA-PSR ACTIVATE UTC REQ (GANC IP address, GANC UDP port) + MS-->>GANC: 2. GA-PSR ACTIVATE UTC ACK (MS UDP port) + GANC->>MS: 3. GA-PSR UNITDATA (TLLI, PFI, LLC-PDU) + GANC->>MS: 4. GA-PSR UNITDATA (TLLI, PFI, priority, LLC-PDU) + +``` + +Sequence diagram showing Network initiated GA-PSR Transport Channel Activation between MS and GANC. The diagram includes four steps: 1. GA-PSR ACTIVATE UTC REQ (GANC IP address, GANC UDP port) from GANC to MS; 2. GA-PSR ACTIVATE UTC ACK (MS UDP port) from MS to GANC; 3. GA-PSR UNITDATA (TLLI, PFI, LLC-PDU) from GANC to MS; 4. GA-PSR UNITDATA (TLLI, PFI, priority, LLC-PDU) from GANC to MS. A callout box indicates that downlink data transfer is initiated for an MS in GA-PSR Standby state or when PS Handover to GAN mode is initiated. + +**Figure 31: Network initiated GA-PSR Transport Channel Activation** + +1. The GANC sends a GA-PSR ACTIVATE UTC REQ message to the MS to request the activation of the corresponding GA-PSR TC. The message contains the GANC IP address and UDP port number assigned to the GA-PSR TC and the MS GA-PSR transitions to GA-PSR-ACTIVE state. +2. The MS replies with a GA-PSR ACTIVATE UTC ACK message that contains the selected UDP-port number. Subsequently, the MS enters GA-PSR-ACTIVE state and starts the GA-PSR Channel Timer. +3. The GANC forwards the previously received downlink LLC-PDU to the MS using GA-PSR UNITDATA message as per procedure described in clause 8.17.1. For the case of PS handover to a GAN cell the reception of downlink LLC PDUs is enabled in the MS upon allocation of the GA-PSR Transport Channel in step 1. +4. The GA-PSR Transport Channel is active and the MS can send the uplink data using GA-PSR UNITDATA procedure described in clause 8.17.1. For the case of PS handover to a GAN cell the MS enables the transmission of uplink LLC PDUs on the allocated GA-PSR Transport Channel upon successful completion of the PS handover procedure. + +## 8.17 GPRS Data, Signalling and SMS Transport + +### 8.17.1 GA-PSR GPRS Data Transport Procedures + +Figure 32 illustrates the transport of GPRS user data messages via GAN. + +![Sequence diagram illustrating User Plane Data Transport between MS, GANC, and CN. The sequence starts with GA-PSR Transport Channel Activation from MS to GANC. The MS starts a GA-PSR Channel Timer. The MS sends GA-PSR UNITDATA (TLLI, PFI, priority, LLC-PDU) to GANC. The GANC forwards it as UL UNITDATA (..., LLC-PDU) to CN. The CN sends DL UNITDATA (..., LLC-PDU) back to GANC. The GANC forwards it as GA-PSR UNITDATA (TLLI, PFI, LLC-PDU) to MS. The MS restarts the GA-PSR Channel Timer. Additional GA-PSR user data transport can occur. When the GA-PSR Channel Timer expires, the MS sends GA-PSR Transport Channel Deactivation to GANC.](fcc757566216206ceddbd6c775e8db02_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant CN + Note left of MS: GA-PSR Channel Timer started + MS->>GANC: 1. GA-PSR Transport Channel Activation + Note left of MS: GA-PSR Channel Timer restarted + MS->>GANC: 2. GA-PSR UNITDATA (TLLI, PFI, priority, LLC-PDU) + GANC->>CN: 3. UL UNITDATA (..., LLC-PDU) + CN->>GANC: 4. DL UNITDATA (..., LLC-PDU) + Note left of MS: GA-PSR Channel Timer restarted + GANC->>MS: 5. GA-PSR UNITDATA (TLLI, PFI, LLC-PDU) + Note left of MS: GA-PSR Channel Timer expires + MS->>GANC: 6. Additional GA-PSR user data transport + Note left of MS: GA-PSR Channel Timer expires + MS->>GANC: 7. GA-PSR Transport Channel Deactivation + +``` + +Sequence diagram illustrating User Plane Data Transport between MS, GANC, and CN. The sequence starts with GA-PSR Transport Channel Activation from MS to GANC. The MS starts a GA-PSR Channel Timer. The MS sends GA-PSR UNITDATA (TLLI, PFI, priority, LLC-PDU) to GANC. The GANC forwards it as UL UNITDATA (..., LLC-PDU) to CN. The CN sends DL UNITDATA (..., LLC-PDU) back to GANC. The GANC forwards it as GA-PSR UNITDATA (TLLI, PFI, LLC-PDU) to MS. The MS restarts the GA-PSR Channel Timer. Additional GA-PSR user data transport can occur. When the GA-PSR Channel Timer expires, the MS sends GA-PSR Transport Channel Deactivation to GANC. + +**Figure 32: User Plane Data Transport** + +1. Optionally, if the GA-PSR is in GA-PSR-STANDBY state, the GA-PSR Transport Channel is activated as per description in clauses 8.16.1 or 8.16.4. Upon successful activation, the MS starts the GA-PSR Channel Timer. +2. The MS encapsulates the uplink LLC-PDU within the GA-PSR UNITDATA message that is forwarded to the GANC. The message includes parameters required for Gb interface procedures and TLLI as MS identifier. The MS restarts the GA-PSR Channel Timer. +3. The GANC forwards the LLC-PDU to the Core Network as per standard Gb interface procedures. +4. The Core Network sends the downlink LLC-PDU that contains GPRS user data via the Gb interface. The MS is identified with the TLLI. +5. Assuming that the corresponding GPRS TC is available, the GANC forwards the LLC-PDU to the MS encapsulated in the GA-PSR UNITDATA message. Upon receiving this message, the MS restarts the GA-PSR Channel Timer. +6. The GPRS data transfer (steps 2 to 5), both in uplink and downlink direction, can be processed as many times as necessary while the GA-PSR TC is active. +7. When the GA-PSR Channel Timer expires, the corresponding GA-PSR TC is deactivated as per description in clause 8.16.2. + +### 8.17.2 GA-PSR GPRS Signalling and SMS Transport Procedures + +#### 8.17.2.1 General + +The TCP connection that is used for GA-CSR signalling is also used for GA-PSR GPRS signalling and SMS transport identified by LLC SAPI 1 and SAPI 7 respectively. This TCP connection is available after GAN registration, so establishment of a separate channel, i.e. a TCP connection, for GPRS signalling and SMS transport is not required. + +#### 8.17.2.2 Network initiated GPRS Signalling + +For Network initiated signalling/SMS, the Core Network sends a GMM/SM signalling or SMS message to the GANC via the Gb interface as per standard GPRS; e.g. the LLC PDU may include GMM attach accept or SM PDP context activation accept message. The GANC encapsulates the received LLC PDU within a GA-PSR DATA message that is forwarded to the MS via the existing TCP connection. + +![Figure 33: Downlink Control Plane Data Transport sequence diagram](5801c19431e76330430e92a598cc7a16_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant CN + CN->>GANC: 1. DL UNITDATA (..., LLC-PDU) + GANC->>MS: 2. GA-PSR DATA (TLLI, PFI, LLC-PDU) + +``` + +Figure 33: Downlink Control Plane Data Transport sequence diagram + +**Figure 33: Downlink Control Plane Data Transport** + +1. The Core Network sends a GMM/SM signalling message or an SMS message as per GPRS via the Gb interface; e.g. the LLC-PDU may include GMM attach accept or SM PDP context activation accept message. +2. The GANC encapsulates the received LLC-PDU within a GA-PSR DATA message that is forwarded to the MS. + +#### 8.17.2.3 MS initiated GPRS Signalling + +For MS initiated signalling/SMS, the MS GA-PSR receives a request from the LLC layer to transfer an uplink GMM/SM signalling message or SMS message; e.g. this could be a GMM attach request or SM PDP context activation message. The GMM/SM signalling messages are identified with LLC SAPI 1 and SMS messages with LLC SAPI 7. The MS GA-PSR encapsulates the LLC PDU within a GA-PSR DATA message including the parameters that will be required for Gb interface procedures. Subsequently, the message is forwarded to the GANC, and the GANC forwards the message to the Core Network as per standard Gb interface procedures. + +![Figure 34: Uplink Control Plane Data Transport sequence diagram](9c05ae298f897f405d4f0c72d98cb2c7_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant CN + MS->>GANC: 1. GA-PSR DATA (TLLI, PFI, QoS, priority, LLC-PDU) + GANC->>CN: 2. UL UNITDATA (..., LLC-PDU) + +``` + +Figure 34: Uplink Control Plane Data Transport sequence diagram + +**Figure 34: Uplink Control Plane Data Transport** + +1. The MS GA-PSR receives a request from the LLC layer to transfer an uplink GMM/SM signalling message or SMS message; e.g. this could be a GMM attach request or SM PDP context activation message. The MS GA-PSR encapsulates the LLC-PDU within a GA-PSR DATA message including the parameters that will be required for Gb interface procedures. Subsequently, the message is forwarded to the GANC. +2. The GANC forwards the message to the Core Network as per standard Gb interface procedure. + +## 8.18 GA-PSR Specific Signalling Procedures + +### 8.18.1 Packet Paging for GPRS Data Service + +The Core Network sends a PS page for a mobile station that is currently GPRS attached via the GAN. + +![Figure 35: Packet Paging for GPRS sequence diagram](a3c1310e720178d2450a3748c7c75422_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant CN + CN->>GANC: 1. PAGING PS + GANC->>MS: 2. GA-PSR PS PAGE (Mobile Identity) + MS->>GANC: 3. LLC-PDU Transport + GANC->>CN: 4. UL UNITDATA (..., LLC-PDU) + +``` + +Figure 35: Packet Paging for GPRS sequence diagram + +**Figure 35: Packet Paging for GPRS** + +1. The Core Network sends a *PAGING PS* for a mobile station that is currently GPRS attached via the GAN. This message contains always IMSI and it may also contain P-TMSI. +2. GANC identifies the MS registration context using the IMSI provided by the CN and pages the MS using the GA-PSR PS PAGE message on the existing TCP signalling connection. The GA-PSR PS PAGE message on the + +Up interface includes the P-TMSI, if received in the *PAGING PS* message from the CN, else it includes the MS IMSI. + +3. The mobile station sends any LLC-PDU to respond to the page, activating GA-PSR TC, if needed. The uplink LLC-PDU is forwarded to the GANC using the GPRS data or signalling transfer mechanism as described in clause 8.17.2.3. +4. The GANC forwards the LLC-PDU to the Core Network via the standard Gb interface procedures. + +### 8.18.2 Packet Paging for CS Domain Service + +The Core Network may send a CS page for a mobile station that is currently GPRS attached via the GAN. + +![Sequence diagram for Packet Paging for CS Service](ada2aa7cce9cff9cf116d9ae2b8b7c27_img.jpg) + +``` +sequenceDiagram + participant MS + participant GANC + participant CN + Note right of CN: 1. PAGING CS + CN->>GANC: 1. PAGING CS + Note left of GANC: 2. GA-CSR PAGING REQUEST + GANC->>MS: 2. GA-CSR PAGING REQUEST + Note left of MS: 3. GA-CSR PAGING RESPONSE + MS->>GANC: 3. GA-CSR PAGING RESPONSE + Note right of GANC: 4. Paging Response + GANC->>CN: 4. Paging Response +``` + +Sequence diagram for Packet Paging for CS Service + +**Figure 36: Packet Paging for CS Service** + +1. The Core Network sends a *PAGING CS* for a GAN registered mobile station via the Gb interface. The mobile station is currently GPRS attached via the GAN. The *PAGING CS* message always contains IMSI as Mobile Identity and it may also contain TMSI. +2. GANC identifies the MS registration context using the IMSI provided by the CN and pages the MS using the GA-CSR PAGING REQUEST message on the existing TCP signalling connection. The GA-CSR PAGING REQUEST message on the Up interface includes the TMSI, if received in the *PAGING CS* message from the CN, else it includes the MS IMSI. +- 3-4. The mobile station initiates the standard CS page response procedure via the GAN as described in clause 8.11. + +### 8.18.3 GPRS Suspend Procedure + +The GPRS Suspend procedure is invoked if a mobile station is unable to support simultaneous voice and data services and is transitioning to dedicated mode. + +![Sequence diagram for GPRS Suspend](eae05333c9188c830bd0ebe58c50453a_img.jpg) + +``` +sequenceDiagram + participant MS + participant GANC + participant CN + Note left of GANC: 1. GA-CSR GPRS SUSPENSION REQUEST + MS->>GANC: 1. GA-CSR GPRS SUSPENSION REQUEST + Note right of GANC: 2. SUSPEND procedure + GANC->>CN: 2. SUSPEND procedure +``` + +Sequence diagram for GPRS Suspend + +**Figure 37: GPRS Suspend** + +1. While transitioning to dedicated mode and if unable to support simultaneous voice and data services, the mobile station sends a GA-CSR GPRS SUSPENSION REQUEST message to the GANC to suspend downlink GPRS traffic. The request is transferred via the existing TCP signalling connection and includes TLLI and Suspension Cause parameters as per standard GPRS. +2. The GANC initiates and completes the standard GPRS Suspend procedure as defined for Gb interface. + +### 8.18.4 GPRS Resume Procedure + +If the GPRS service has been suspended while the mobile station entered the dedicated mode, it needs to be resumed when the mobile station leaves the dedicated mode. + +![Sequence diagram for GPRS Resume Procedure showing interactions between MS, GANC, and CN.](76d19e4271bf243b20d55a98efd51483_img.jpg) + +``` +sequenceDiagram + participant MS + participant GANC + participant CN + Note right of CN: 1. Clear Command + CN->>GANC: 1. Clear Command + Note right of GANC: 2. Clear Complete + GANC->>CN: 2. Clear Complete + Note right of CN: 3. RESUME procedure + CN->>GANC: 3. RESUME procedure + Note left of GANC: 4. GA-CSR RELEASE(GPRS resumption) + GANC->>MS: 4. GA-CSR RELEASE(GPRS resumption) + Note left of MS: 5. GA-CSR RELEASE COMPLETE + MS->>GANC: 5. GA-CSR RELEASE COMPLETE + Note left of GANC: 6. Resume GPRS, if required + GANC->>CN: 6. Resume GPRS, if required +``` + +Sequence diagram for GPRS Resume Procedure showing interactions between MS, GANC, and CN. + +Figure 38: GPRS Resume + +Initially, the MS is in the dedicated mode and the GPRS service is suspended. + +1. The Core Network sends a *Clear Command* message to release the resources associated with the dedicated mode procedure. +2. The GANC responds with a *Clear Complete* message. +3. Optionally, the GANC may initiate the standard BSSGP GPRS resume procedure. +4. The GANC sends a *GA-CSR RELEASE* message to instruct the MS to release the GA-CSR Connection. The message includes GPRS resumption indication as per standard GSM/GPRS to indicate whether or not the network successfully resumed GPRS service. +5. The MS replies with a *GA-CSR RELEASE COMPLETE* message and resumes GPRS service internally. +6. Optionally, if the Core Network indicated unsuccessful resumption, the MS initiates GPRS service resumption as per standard GPRS. + +### 8.18.5 MS Initiated Downlink Flow Control + +The principle of the MS Initiated Downlink Flow Control is that the MS sends to the GANC flow control parameters, which allow the GANC to perform standard Gb interface procedures towards CN for downlink Flow Control either on MS or PFC level. + +The following figure illustrates the message flow involved in the normal case when the MS sends a GAN flow control request to the GANC as an indication that the MS is not able to handle current data rate. The GANC will utilize the standard MS based Gb interface flow control mechanism to adjust the data rate. + +![Sequence diagram for Downlink Flow Control showing interactions between MS, GANC, and CN.](0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg) + +``` +sequenceDiagram + participant MS + participant GANC + participant CN + + Note left of MS: 1. Flow control condition detected + MS->>GANC: 2. GA-PSR FC REQ (FC Adjustment) + Note left of MS: GA-PSR DL FC timer started + GANC->>CN: 3. Flow Control procedure + Note left of MS: GA-PSR DL FC timer expiry + Note left of MS: 4. GA-PSR FC REQ (FC Adjustment) + MS->>GANC: 4. GA-PSR FC REQ (FC Adjustment) + Note left of MS: GA-PSR DL FC timer started + GANC->>CN: 5. Flow Control procedure + Note left of MS: 6. GA-PSR DL FC timer expiry + Note left of MS: 7. Flow control condition resolved +``` + +The diagram illustrates the Downlink Flow Control process involving three entities: MS (Mobile Station), GANC (GAN Controller), and CN (Core Network). The sequence of events is as follows: 1. The MS detects a flow control condition. 2. The MS sends a GA-PSR FC REQ (FC Adjustment) message to the GANC and starts a GA-PSR DL FC timer. 3. The GANC initiates a Flow Control procedure with the CN. 4. Upon the timer expiry, if the condition persists, the MS sends another GA-PSR FC REQ (FC Adjustment) to the GANC and restarts the timer. 5. The GANC repeats the Flow Control procedure with the CN. 6. The GA-PSR DL FC timer expires again. 7. The flow control condition is resolved. + +Sequence diagram for Downlink Flow Control showing interactions between MS, GANC, and CN. + +**Figure 39: Downlink Flow Control** + +1. The MS detects a flow control condition related to the downlink data traffic. +2. The MS constructs a flow control request message (GA-PSR FC REQ) that is sent to the GANC via the GA-PSR TC and starts a GA-PSR downlink flow control timer to continue monitoring the flow control condition. The message includes the flow control adjustment IE to specify the required data rate correction. +3. Upon receiving the indication, the GANC calculates adjusted flow control parameters for the MS and sends the corresponding request to the Core Network to reduce the downlink data rate for the MS. The Core Network adjusts the downlink data rate for the MS as per request. +4. Upon the expiry of the GA-PSR downlink flow control timer, the MS evaluates the flow control condition and if it has not been resolved, calculates the adjustment again and forwards another request to the GANC. +5. The GANC processes the request and sends another request to the Core Network to adjust the downlink data rate for the MS. +6. The GA-PSR downlink flow control timer expires again. +7. Steps 4 to 6 are repeated until the flow control condition is resolved. + +### 8.18.6 Uplink Flow Control + +The principle of the Uplink Flow Control is that the GANC sends to the MS flow control parameters, which guide the MS on sending of GPRS data towards the GANC. + +The following figure illustrates the message flow involved in the normal case when the GANC initiates GAN flow control procedure when it is not able to handle current uplink data rate. + +![Sequence diagram illustrating Uplink Flow Control between MS, GANC, and CN. The GANC detects a flow control condition and sends three GA-PSR FC REQ messages to the MS. After the third request, the GANC determines the condition is resolved.](d6c377ae3e619ff992bd3647dbf43593_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant CN + Note right of GANC: 1. UL Flow Control condition detected + GANC->>MS: 2. GA-PSR FC REQ (FC Adjustment) + GANC->>MS: 3. GA-PSR FC REQ (FC Adjustment) + GANC->>MS: 4. GA-PSR FC REQ (FC Adjustment) + Note right of GANC: 5. UL Flow control condition resolved + +``` + +Sequence diagram illustrating Uplink Flow Control between MS, GANC, and CN. The GANC detects a flow control condition and sends three GA-PSR FC REQ messages to the MS. After the third request, the GANC determines the condition is resolved. + +**Figure 40: Uplink Flow Control** + +1. The GANC detects a flow control condition related to the uplink data traffic associated with a specific MS. +2. The GANC constructs a flow control request message (GA-PSR-FC-REQ) that is sent to the MS via the GA-PSR TC and starts a timer to continue monitoring the flow control condition. The message includes the flow control adjustment IE to specify the required data rate correction. Upon receiving the message, the MS adjusts the uplink data rate accordingly. +3. After the timer expires, the GANC evaluates the flow control condition and if it has not been resolved, calculates the adjustment again and forwards another request to the MS. +4. The GANC timer expires again. The GANC evaluates the flow control condition and determines that the condition has been resolved. Based on the GANC algorithm that is implemented, it may gradually increase the uplink data rate using the same GA-PSR-FC-REQ message. +5. The flow control condition does not exist any more and the procedure is complete. + +## 8.19 Short Message Service + +GAN provides support for both Circuit Switched (GSM based) and Packet Switched (GPRS based) SMS services. GAN-attached and GPRS enabled mobile stations will be able to send and receive GSM and GPRS SMS messages via the GAN, regardless of the GPRS class (B or C) with the restriction that the class C mobiles can support only GPRS based SMS. + +### 8.19.1 GSM based SMS + +GSM SMS support in GAN is based on the same mechanism that is utilized for GSM mobility management and call control. On the MS side, the SMS layers (including the supporting CM sub layer functions) utilize the services of the MM layer to transfer SMS messages per standard circuit switched GSM implementation. The SM-CP protocol is effectively tunnelled between the MS and the CN, using GA-CSR messages from the MS to the GANC, where the GANC relays the SM-CP to BSSAP DTAP messages for transport over the A interface. + +As with GSM mobility management and call control procedures, the secure IPsec tunnel and TCP session are used to provide secure and reliable SMS delivery over the IP network. + +### 8.19.2 GPRS based SMS + +GPRS SMS message transfer is based on the same mechanism as the transfer of the GPRS MM/SM signalling messages. On the MS side, the SMS layers (including the supporting CM sub layer functions) utilize the services of the LLC layer to transfer SMS messages per standard packet switched GPRS implementation. + +As with GPRS signalling, the secure IPsec tunnel and TCP session is used to provide secure and reliable GPRS SMS delivery over the IP network. + +## 8.20 Supplementary Services + +GSM has a large number of standardized supplementary services. These supplementary services involve procedures that operate end-to-end between the MS and the MSC. The DTAP messages used for the supplementary service are relayed between the MS and MSC in the same manner as in the other call control and mobility management scenarios described in this document. + +## 8.21 Emergency Services + +### 8.21.1 General + +The GANC can indicate, in the GAN Registration procedures, an Access Network preference for the placement of emergency calls. + +Based on the Access Network preference, and if any GERAN/UTRAN coverage is available (either from the GAN subscriber's home PLMN or from any roamer PLMN, irrespective of roamer agreements), the MS should switch from GAN mode to GERAN/UTRAN mode and place the emergency call over GERAN/UTRAN, to leverage the location determination infrastructure in GERAN/UTRAN. During the emergency call, the MS should not attempt to handover the call to GAN. After the emergency call is completed, the MS may perform normal rove-in procedures to re-enter GAN mode, if GAN coverage is still available. Alternatively there may be a penalty timer configured to ensure that the MS remains in GERAN/UTRAN for call-back purposes. On expiry of the penalty timer the MS may perform normal rove-in procedures to re-enter GAN mode, if GAN coverage is still available. + +Based on the Access Network preference, or if no GERAN/UTRAN coverage is available (neither from the GAN subscriber's home PLMN nor from any roamer PLMN, irrespective of roamer agreements), the MS places the emergency call over GAN. In GAN, the emergency call is handled just like a GSM emergency call origination. The cell ID associated with the GANC provides an indication of the location of the MS. Additionally, more accurate location information may be obtained by the GANC either directly from the MS (e.g. using AGPS) or from the generic IP access network point of attachment (e.g. using a database of IP or MAC addresses). If available, the GANC can pass this location information through BSSMAP or RANAP signalling to the core network, when requested. However, location services based on mechanisms using the GERAN/UTRAN physical layer cannot be applied. + +NOTE: A mechanism may be required in the GANC to force the MS to GERAN/UTRAN mode, if the location accuracy is not deemed sufficient for emergency calls in GAN mode. + +### 8.21.2 North American Emergency Calls + +#### 8.21.2.1 Phase 1 Solution + +##### 8.21.2.1.1 Phase 1 Requirements + +Wireless service providers were required by the FCC to have the capability to send wireless 911 calls to an E911 public safety answering point (PSAP) containing two important sets of data: + +1. The location of the cell tower through which the E911 call was processed. +2. The mobile directory number (MDN) or "call back number" of the wireless phone placing the 911 call. + +##### 8.21.2.1.2 Phase 1 Mechanism + +The GANC shall indicate during registration, when entering GAN mode, whether GERAN/UTRAN or GAN is preferred for support of emergency calls. + +- If GAN mode is the preferred emergency call mode, the emergency call shall be placed over GAN if the mobile is in GAN mode. The GANC can reject the call depending on operator policy. +- If GERAN/UTRAN mode is the preferred emergency mode, the emergency call shall be placed over the GERAN/UTRAN when a GERAN/UTRAN network is available. If a GERAN/UTRAN network is not available the emergency call shall be placed over GAN. + +#### 8.21.2.2 Phase 2 Solution + +##### 8.21.2.2.1 Phase 2 Requirements + +Wireless service providers are required by the FCC to have the ability to provide the actual caller's location to the E911 PSAP. The location accuracy requirements differ depending on whether a network-based or handset-based approach is chosen. + +- Network-based requirement: Within 100 meters, 67% of the time and within 300 meters, 95% of the time. +- Handset-based requirement: Within 50 meters, 67% of the time and within 150 meters, 95% of the time. + +The handset-based requirements apply to terminals supporting location determining mechanisms (e.g. A-GPS, E-OTD). This may require new, modified or upgraded terminals. + +##### 8.21.2.2.2 Phase 2 Mechanism + +The emergency call is placed over GERAN/UTRAN or GAN. If the emergency call is placed over GAN, the GANC will need to provide accurate location information for the MS or the AP through which the MS is placing the emergency call. This can be done in a number of ways: + +- the GANC can reference an AP-ID to location mapping database for the GAN service; +- the MS can provide its current location (e.g. obtained via AGPS) in GA-RC REGISTER REQUEST/UPDATE message; +- the GANC can reference an MS (public) IP address to location mapping database; +- the GANC can deliver the required location information to the SMLC via Lb interface and the SMLC is responsible for final location determination. + +The GANC passes this location information through BSSMAP or RANAP signalling to the CN, when requested. + +## 8.22 Location Services + +The GANC uses information received from the MS during the GAN Registration and GAN Registration Update procedures to determine the geographic location of an MS. + +1. **Cell-Info:** The MS provides the identity of the GSM, UTRAN or E-UTRAN cell it is camped on, in case GERAN/UTRAN/E-UTRAN coverage is available, at the time of GAN registration. The GANC determines the MS location to the resolution of a single cell. This enables location services that require location resolution provided by a cell (e.g. E911 Phase 1). + +NOTE 1: The accuracy of the location may be reduced if no up-to-date cellular coverage information is available. + +2. **Generic IP access network point of attachment information (AP-ID):** The MS provides the AP-ID at the time of GAN registration. The GANC may maintain an internal database of mapping between AP-ID and AP location. The AP Location may be defined as street address, postcode or zip code and would require a translation function to a GAD shape as defined in 3GPP TS 23.032 [41]. The GANC may then determine the MS location to the resolution of a single attachment point's coverage area. This can enable location services that require a location with greater resolution than that provided by a GSM cell (e.g. E911 Phase 2). + +NOTE 2: The location of the point of attachment may not be reliable, and is dependent on up-to-date information being provided either by the MS or by the owner of the point of attachment. + +## 8.23 PS Handovers between GAN A/Gb mode and GERAN/UTRAN mode + +Procedures for PS handover between GERAN/UTRAN mode and GAN A/Gb mode when an MS and BSS/RNC/GANC support this type of PS handover are described in 3GPP TS 43.129 [44]. + +# --- 9 High-Level Procedures for GAN Iu Mode + +## 9.1 Mechanism of Mode Selection in Multi-mode terminals + +See clause 8.1. + +## 9.2 PLMN Selection + +See clause 8.2. + +## 9.3 Re-selection between GERAN/UTRAN/E-UTRAN and GAN modes + +See clause 8.3. + +## 9.4 GAN Discovery and Registration related procedures + +See clause 8.4. + +## 9.5 Authentication + +See clause 8.5. + +## 9.6 Encryption + +See clause 8.6. + +## 9.7 GA-RRC Connection handling + +The GAN Iu mode GA-RRC CS and PS connections are logical connections between the MS and the GANC. + +A GA-RRC connection is established when the upper layers in the MS request the establishment of a signalling connection for either CS or PS domain and the MS is in GA-RRC-IDLE state for that domain; i.e., no GA-RRC connection exists. When a successful response is received from the network, GA-RRC replies to the upper layer that the MS has entered the RRC connected mode (i.e., the GA-RRC-CONNECTED state). The upper layers then have the possibility to request transmission of NAS messages to the network. + +Note that in the case of a network-initiated CS or PS session, the GA-RRC connection is implicitly established when the MS responds to the GA-RRC PAGING REQUEST message from the GANC with the GA-RRC INITIAL DIRECT TRANSFER containing the paging response. This is illustrated in clause 9.11 for the CS case and clause 9.16.7.2 for the PS case. + +Also, in the case of handover from GERAN or UTRAN to GAN Iu mode, the GA-RRC connection is implicitly established when the MS sends the GA-RRC RELOCATION ACK message to the GANC (normal case) or the GA-RRC RELOCATION ACCESS message to the GANC (exception case), as described in sub-clause 9.14. + +### 9.7.1 GA-RRC Connection Establishment + +The following figure shows successful and unsuccessful establishment of the GA-RRC connection for either the CS or PS domain. + +![Sequence diagram for GA-RRC Connection Establishment](64544fbada794f3cdf4f78f5d83613e4_img.jpg) + +A sequence diagram showing the interaction between MS, GANC, and CN for GA-RRC connection establishment. The MS sends a GA-RRC REQUEST message to the GANC. The GANC responds with either a GA-RRC REQUEST ACCEPT or a GA-RRC REQUEST REJECT. The CN is not involved in this process. + +``` +sequenceDiagram + participant MS + participant GANC + participant CN + Note left of MS: + MS->>GANC: 1. GA-RRC REQUEST + GANC-->>MS: 2. GA-RRC REQUEST ACCEPT + Note left of GANC: + GANC-->>MS: 3. GA-RRC REQUEST REJECT +``` + +Sequence diagram for GA-RRC Connection Establishment + +**Figure 43: GA-RRC Connection Establishment** + +1. The MS initiates GA-RRC connection establishment by sending the GA-RRC REQUEST message to the GANC. The message includes the CN Domain identity (CS or PS) and the Establishment Cause indicating the reason for GA-RRC connection establishment. +2. The GANC signals the acceptance of the connection request to the MS by sending the GA-RRC REQUEST ACCEPT and the MS enters the GA-RRC-CONNECTED state. +3. If the GANC determines that the GA-RRC connection request shall be rejected, it sends a GA-RRC REQUEST REJECT to the MS indicating the reject cause, completing the procedure. + +### 9.7.2 GA-RRC Connection Release + +The following figure shows release of the logical GA-RRC connection between the MS and the GANC. + +![Sequence diagram for GA-RRC Connection Release](22bc7139d3987c61ddefffa08036a923_img.jpg) + +A sequence diagram showing the interaction between MS, GANC, and CN for GA-RRC connection release. The CN sends an Iu Release Command to the GANC. The GANC sends a GA-RRC RELEASE message to the MS. The MS responds with a GA-RRC RELEASE COMPLETE message. The GANC then sends an Iu Release Complete message to the CN. + +``` +sequenceDiagram + participant MS + participant GANC + participant CN + Note right of CN: + CN->>GANC: 1. Iu Release Command + GANC-->>MS: 2. GA-RRC RELEASE + Note left of MS: + MS->>GANC: 4. GA-RRC RELEASE COMPLETE + Note right of GANC: + GANC->>CN: 3. Iu Release Complete +``` + +Sequence diagram for GA-RRC Connection Release + +**Figure 44: GA-RRC Connection Release** + +1. The CN indicates to the GANC to release the resources allocated to the MS, via the RANAP *Iu Release Command* message. +2. The GANC commands the MS to release resources, using the GA-RRC RELEASE message. The message includes the CN Domain Identity (CS or PS). +3. The GANC confirms resource release to the CN using the *Iu Release Complete* message. The GANC may optionally wait for receipt of the GA-RRC RELEASE COMPLETE message from the MS before sending the *Iu Release Complete* message to the CN. +4. The MS confirms resource release to the GANC using the GA-RRC RELEASE COMPLETE message and the GA-RRC state of the CS domain GA-RRC sublayer entity or the PS domain GA-RRC sublayer entity (i.e., depending on the value of the CN Domain Identity received in step 2) in the MS changes to GA-RRC-IDLE. + +### 9.7.3 GA-RRC Connection Release Request + +The following figure shows release of the logical CS or PS GA-RRC connection between the MS and the GANC when initiated by the MS or the GANC (i.e., due to abnormal conditions). + +![Sequence diagram for GA-RRC Connection Release Request. The diagram shows three entities: MS, GANC, and CN. The sequence of messages is: 1. GA-RRC RELEASE REQUEST from MS to GANC (dashed line); 2. Iu Release Request from GANC to CN (solid line); 3. GA-RRC Connection Release from CN to MS (solid line).](57939c16065211317c5442cf2a4009e0_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant CN + Note left of MS: 1. GA-RRC RELEASE REQUEST + MS-->>GANC: 1. GA-RRC RELEASE REQUEST + Note right of GANC: 2. Iu Release Request + GANC->>CN: 2. Iu Release Request + Note right of CN: 3. GA-RRC Connection Release + CN->>MS: 3. GA-RRC Connection Release + +``` + +Sequence diagram for GA-RRC Connection Release Request. The diagram shows three entities: MS, GANC, and CN. The sequence of messages is: 1. GA-RRC RELEASE REQUEST from MS to GANC (dashed line); 2. Iu Release Request from GANC to CN (solid line); 3. GA-RRC Connection Release from CN to MS (solid line). + +**Figure 45: GA-RRC Connection Release Request** + +1. The MS may initiate CS or PS GA-RRC connection release by sending the GA-RRC RELEASE REQUEST message to the GANC. The message includes the CN Domain identity (CS or PS) and the Cause indicating the reason for GA-RRC connection release. +2. On receipt of the GA-RRC RELEASE REQUEST from the MS or due to local conditions in the GANC, the GANC initiates Iu release for the particular CN domain by sending the *Iu Release Request* message to the CN Domain entity. +3. The CN triggers the release of connection as described in clause 9.7.2. + +## 9.8 Security Mode Control + +The message flow for security mode control is shown in the following figure. + +![Sequence diagram for Security Mode Control. The diagram shows three entities: MS, GANC, and CN. The sequence of messages is: 1. Security Mode Command from CN to GANC (solid line); 2. GA-RRC SECURITY MODE COMMAND from GANC to MS (solid line); 3. GA-RRC SECURITY MODE COMPLETE from MS to GANC (solid line); 4. Security Mode Complete from GANC to CN (solid line). A 'Verify MAC' box is shown on the GANC lifeline between steps 3 and 4.](10cc1e74f2b71404f021bb8b3cec0ff0_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant CN + Note right of CN: 1. Security Mode Command + CN->>GANC: 1. Security Mode Command + Note left of GANC: 2. GA-RRC SECURITY MODE COMMAND + GANC->>MS: 2. GA-RRC SECURITY MODE COMMAND + Note left of MS: 3. GA-RRC SECURITY MODE COMPLETE + MS->>GANC: 3. GA-RRC SECURITY MODE COMPLETE + Note right of GANC: Verify MAC + GANC->>CN: 4. Security Mode Complete + +``` + +Sequence diagram for Security Mode Control. The diagram shows three entities: MS, GANC, and CN. The sequence of messages is: 1. Security Mode Command from CN to GANC (solid line); 2. GA-RRC SECURITY MODE COMMAND from GANC to MS (solid line); 3. GA-RRC SECURITY MODE COMPLETE from MS to GANC (solid line); 4. Security Mode Complete from GANC to CN (solid line). A 'Verify MAC' box is shown on the GANC lifeline between steps 3 and 4. + +**Figure 46: Security Mode Control** + +1. The CN sends the RANAP *Security Mode Command* message to the GANC. This message contains the integrity key (IK) and allowed algorithms, and optionally the cipher key (CK) and allowed algorithms. +2. The GANC selects the integrity algorithm and (optionally) the ciphering algorithm based on the permitted algorithms received from the CN and the MS security capabilities indicated in the IE "3G Security Capability" received from the MS in the GA-RC REGISTER REQUEST message. The GANC sends the GA-RRC SECURITY MODE COMMAND message to the MS. This message indicates the selected integrity protection algorithm and ciphering algorithm (i.e., that are applicable after handover to UTRAN), and a random number. The MS stores the information for possible future use after a handover to UTRAN. +3. The MS computes a MAC based on the random number, the MS IMSI and the integrity key. The MS then sends the GA-RRC SECURITY MODE COMPLETE message including the computed MAC. + +4. The GANC verifies the MAC. If the GANC verifies the MAC to be correct it sends the *Security Mode Complete* message to the CN. + +NOTE: The MAC proves that the identity that is authenticated to the GANC is the same as the identity authenticated to the core network. + +## 9.9 NAS Signalling Procedures + +After GA-RRC connection establishment, NAS PDUs may be transferred from CN-to-MS and from MS-to-CN. + +The initial NAS PDU from the MS to a core network domain is transferred in the GA-RRC INITIAL DIRECT TRANSFER message as illustrated in the following figure. This scenario assumes that a GA-RRC connection already exists between the MS and GANC; if not, the procedure described in clause 9.7.1 is performed before step 1. + +![Sequence diagram for Initial MS-to-CN NAS signalling](7f663b2f8632236c6e40ca16272d62df_img.jpg) + +``` +sequenceDiagram + participant MS + participant GANC + participant CN + Note left of MS: + MS->>GANC: 1. GA-RRC INITIAL DIRECT TRANSFER (NAS-PDU) + GANC->>CN: 2. Initial UE Message (NAS-PDU) +``` + +The diagram shows a sequence of two messages between three entities: MS, GANC, and CN. Step 1: The MS sends a 'GA-RRC INITIAL DIRECT TRANSFER (NAS-PDU)' message to the GANC. Step 2: The GANC sends an 'Initial UE Message (NAS-PDU)' message to the CN. + +Sequence diagram for Initial MS-to-CN NAS signalling + +**Figure 47: Initial MS-to-CN NAS signalling** + +1. The MS receives a request from the NAS layer to establish a signalling connection to a core network domain. The request also includes a request to transfer an uplink NAS PDU. The MS encapsulates the NAS PDU within a GA-RRC INITIAL DIRECT TRANSFER message and sends the message to the GANC. The message includes the CN Domain identity (CS or PS). It also includes the Intra Domain NAS Node Selector (IDNNS) to be used by the GANC to route the establishment of a signalling connection to a CN node within the indicated CN domain (i.e., using IuFlex). +2. The GANC establishes a signalling connection to the indicated core network domain entity and relays the received NAS-PDU to the CN via the RANAP *Initial UE Message* message. + +Subsequent NAS PDUs from the MS to the core network domain entity are transferred in the GA-RRC UPLINK DIRECT TRANSFER message as illustrated in the following figure. + +![Sequence diagram for MS-to-CN NAS signalling](1018d0db7bb02c169f646cb9cc244dc6_img.jpg) + +``` +sequenceDiagram + participant MS + participant GANC + participant CN + Note left of MS: + MS->>GANC: 1. GA-RRC UL DIRECT TRANSFER (NAS-PDU) + GANC->>CN: 2. Direct Transfer (NAS-PDU) +``` + +The diagram shows a sequence of two messages between three entities: MS, GANC, and CN. Step 1: The MS sends a 'GA-RRC UL DIRECT TRANSFER (NAS-PDU)' message to the GANC. Step 2: The GANC sends a 'Direct Transfer (NAS-PDU)' message to the CN. + +Sequence diagram for MS-to-CN NAS signalling + +**Figure 48: MS-to-CN NAS signalling** + +1. The MS receives a request from the NAS layer to transfer an uplink NAS PDU. Assuming the required signalling connection already exists, the MS encapsulates the NAS PDU within a GA-RRC UL DIRECT TRANSFER message and sends the message to the GANC. The message includes the CN Domain identity (CS or PS). +2. The GANC relays the received NAS-PDU to the CN via the RANAP *Direct Transfer* message. + +NAS PDUs from the core network to the MS are transferred in the GA-RRC DOWNLINK DIRECT TRANSFER message as illustrated in the following figure. + +![Sequence diagram for CN-to-MS NAS signalling. It shows three lifelines: MS, GANC, and CN. Step 1: CN sends a 'Direct Transfer (NAS-PDU)' message to GANC. Step 2: GANC sends a 'GA-RRC DL DIRECT TRANSFER (NAS-PDU)' message to MS.](719ef0f734259484038b2434e5dc3f24_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant CN + Note right of CN: 1. Direct Transfer (NAS-PDU) + CN->>GANC: Direct Transfer (NAS-PDU) + Note right of GANC: 2. GA-RRC DL DIRECT TRANSFER (NAS-PDU) + GANC->>MS: GA-RRC DL DIRECT TRANSFER (NAS-PDU) + +``` + +Sequence diagram for CN-to-MS NAS signalling. It shows three lifelines: MS, GANC, and CN. Step 1: CN sends a 'Direct Transfer (NAS-PDU)' message to GANC. Step 2: GANC sends a 'GA-RRC DL DIRECT TRANSFER (NAS-PDU)' message to MS. + +**Figure 49: CN-to-MS NAS signalling** + +1. For CN-to-MS NAS signalling, the CN sends a NAS PDU to the GANC via the RANAP *Direct Transfer* message. +2. The GANC encapsulates the NAS PDU within a GA-RRC DL DIRECT TRANSFER message and forwards the message to the MS via the existing TCP connection. The message includes the CN Domain identity (CS or PS). + +## 9.10 Mobile Originated CS Call + +The description of the procedure in this sub-clause assumes the MS is in GAN Iu mode; i.e., it has successfully registered with the GANC and GA-RRC is the serving RR entity for CS services in the MS. It also assumes that no GA-RRC signalling connection for the CS domain exists between the MS and GANC; i.e., the CS domain GA-RRC sublayer entity in the MS is in the GA-RRC-IDLE state. If the CS domain GA-RRC sublayer entity in the MS is already in the GA-RRC-CONNECTED state, step 1 is skipped. + +![Sequence diagram for Mobile Originated CS Call. It shows three lifelines: MS, GANC, and MSC. The process starts with GA-RRC Connection Establishment (step 1) between MS and GANC. Then, MS sends GA-RRC INITIAL DIRECT TRANSFER (CM Service Request) to GANC (step 2). GANC sends Initial UE Message (CM Service Request) to MSC (step 3). MSC performs Authentication (step 4) and Security Mode Control (step 5) with GANC. GANC sends GA-RRC UL DIRECT TRANSFER (Setup) to MSC (step 6). MSC sends GA-RRC DL DIRECT TRANSFER (Call Proceeding) to GANC (step 7). GANC sends RAB Assignment Request to MSC (step 8). MSC performs Iu Bearer Establishment and Iu UP Initialization (step 9). GANC sends GA-RRC ACTIVATE CHANNEL to MS (step 10). MS sends GA-RRC ACTIVATE CHANNEL ACK to GANC (step 11). GANC sends GA-RRC ACTIVATE CHANNEL COMPLETE to MS (step 12). MSC sends RAB Assignment Response to GANC (step 13). GANC sends GA-RRC DL DIRECT TRANSFER (Alerting) to MS (step 14). GANC sends GA-RRC DL DIRECT TRANSFER (Connect) to MS (step 15). MS sends GA-RRC UL DIRECT TRANSFER (Connect Ack) to GANC (step 16). Finally, Voice traffic flows between MS and MSC (step 17).](dfe74512a9c9fb620f72c9dbc22874aa_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant MSC + Note left of MS: GA-RRC-CONNECTED + MS->>GANC: 1. GA-RRC Connection Establishment + Note left of MS: GA-RRC-CONNECTED + MS->>GANC: 2. GA-RRC INITIAL DIRECT TRANSFER (CM Service Request) + GANC->>MSC: 3. Initial UE Message (CM Service Request) + Note right of MSC: 4. Authentication + Note right of MSC: 5. Security Mode Control + GANC->>MSC: 6. GA-RRC UL DIRECT TRANSFER (Setup) + MSC->>GANC: 7. GA-RRC DL DIRECT TRANSFER (Call Proceeding) + GANC->>MSC: 8. RAB Assignment Request + Note right of MSC: 9. Iu Bearer Establishment and Iu UP Initialization + GANC->>MS: 10. GA-RRC ACTIVATE CHANNEL + MS->>GANC: 11. GA-RRC ACTIVATE CHANNEL ACK + GANC->>MS: 12. GA-RRC ACTIVATE CHANNEL COMPLETE + MSC->>GANC: 13. RAB Assignment Response + GANC->>MS: 14. GA-RRC DL DIRECT TRANSFER (Alerting) + GANC->>MS: 15. GA-RRC DL DIRECT TRANSFER (Connect) + MS->>GANC: 16. GA-RRC UL DIRECT TRANSFER (Connect Ack) + Note right of MSC: 17. Voice traffic + +``` + +Sequence diagram for Mobile Originated CS Call. It shows three lifelines: MS, GANC, and MSC. The process starts with GA-RRC Connection Establishment (step 1) between MS and GANC. Then, MS sends GA-RRC INITIAL DIRECT TRANSFER (CM Service Request) to GANC (step 2). GANC sends Initial UE Message (CM Service Request) to MSC (step 3). MSC performs Authentication (step 4) and Security Mode Control (step 5) with GANC. GANC sends GA-RRC UL DIRECT TRANSFER (Setup) to MSC (step 6). MSC sends GA-RRC DL DIRECT TRANSFER (Call Proceeding) to GANC (step 7). GANC sends RAB Assignment Request to MSC (step 8). MSC performs Iu Bearer Establishment and Iu UP Initialization (step 9). GANC sends GA-RRC ACTIVATE CHANNEL to MS (step 10). MS sends GA-RRC ACTIVATE CHANNEL ACK to GANC (step 11). GANC sends GA-RRC ACTIVATE CHANNEL COMPLETE to MS (step 12). MSC sends RAB Assignment Response to GANC (step 13). GANC sends GA-RRC DL DIRECT TRANSFER (Alerting) to MS (step 14). GANC sends GA-RRC DL DIRECT TRANSFER (Connect) to MS (step 15). MS sends GA-RRC UL DIRECT TRANSFER (Connect Ack) to GANC (step 16). Finally, Voice traffic flows between MS and MSC (step 17). + +**Figure 50: Mobile Originated CS Call** + +1. The CS GA-RRC Connection Establishment procedure is performed as described in clause 9.7.1. + +2. The MS sends the *CM Service Request* message to the GANC within the GA-RRC INITIAL DIRECT TRANSFER message. The message includes the CN Domain identity (CS). +3. The GANC establishes an SCCP connection to the MSC and forwards the NAS PDU (i.e., the CM Service Request message) to the MSC using the RANAP Initial UE Message. The message includes the Domain Indicator set to value 'CS domain'. Subsequent NAS messages between the MS and MSC will be sent between GANC and MSC using the RANAP Direct Transfer message. +4. The MSC may optionally authenticate the MS using standard UTRAN authentication procedures. +5. The MSC normally initiates the Security Mode Control procedure described in clause 9.8. +6. The MS sends the *Setup* message providing details on the call to the MSC and its bearer capability and supported codecs. This message is contained within the GA-RRC UL DIRECT TRANSFER between the MS and the GANC. The GANC forwards the *Setup* message to the MSC. +7. The MSC indicates it has received the call setup and it will accept no additional call-establishment information using the *Call Proceeding* message to the GANC. The GANC forwards this message to the MS in the GA-RRC DL DIRECT TRANSFER message. +8. The MSC requests the GANC to assign call resources using the RANAP *RAB Assignment Request* message. The MSC includes the RAB ID, the CN Transport Layer Address and the CN Iu Transport Association for user data. +9. The Iu bearer is established per standard Iu procedures. In the case of the ATM-based Iu-cs interface, this may include the exchange of ALCAP signalling between the GANC and the MSC to setup the ATM virtual circuit. For both ATM and IP-based Iu-cs interface types, Iu bearer establishment may also include the Iu UP initialization exchange, if Iu UP support mode is required as indicated by the MSC in the RANAP *RAB Assignment Request* message. +10. The GANC sends the GA-RRC ACTIVATE CHANNEL message to the MS including bearer path setup information such as: + - CN Domain ID (i.e., indicating CS domain). + - RAB ID (provided by the MSC in step 8). + - RAB Configuration (based on RAB parameters provided by the MSC in step 8). + - Multi-rate codec configuration. + - UDP port & the IP address for the uplink RTP stream. + - Voice sample size. +11. The MS sends the GA-RRC ACTIVATE CHANNEL ACK to the GANC indicating that the MS has successfully established a CS bearer channel for the call and including the UDP port for the downlink RTP stream. +12. The GANC signals the completion of the RAB establishment to the MS with the GA-RRC ACTIVATE CHANNEL COMPLETE message. +13. The GANC signals to the MSC that the RAB has been established by sending a RANAP *RAB Assignment Response* message. +14. The MSC signals to the MS, with the *Alerting* message, that the B-Party is ringing. The message is transferred to the GANC and GANC forwards the message to the MS in the GA-RRC DL DIRECT TRANSFER. If the MS has not connected the audio path to the user, it shall generate ring back to the calling party. Otherwise, the network-generated ring back will be returned to the calling party. +15. The MSC signals that the called party has answered, via the *Connect* message. The message is transferred to the GANC and GANC forwards the message to the MS in the GA-RRC DL DIRECT TRANSFER. The MS connects the user to the audio path. If the MS is generating ring back, it stops and connects the user to the audio path. + +16. The MS sends the *Connect Ack* message in response, and the two parties are connected for the voice call. This message is contained within the GA-RRC UL DIRECT TRANSFER between the MS and the GANC. The GANC forwards the *Connect Ack* message to the MSC. +17. Bi-directional voice traffic flows between the MS and MSC through the GANC. + +## 9.11 Mobile Terminated CS Call + +The description of the procedure in this clause assumes the MS is in GAN Iu mode; i.e., it has successfully registered with the GANC and GA-RRC is the serving RR entity for CS services in the MS. + +![Sequence diagram for Mobile Terminated CS Call showing interactions between MS, GANC, and MSC.](efb282bed9f06eef1987a14fb27bc599_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant MSC + Note left of MS: GA-RRC-CONNECTED + MSC->>GANC: 1. Paging + GANC->>MS: 2. GA-RRC PAGING REQUEST + MS->>GANC: 3. GA-RRC INITIAL DIRECT TRANSFER (Paging Response) + GANC->>MSC: 4. Initial UE Message (Paging Response) + Note over MS, GANC, MSC: 5. Authentication + Note over MS, GANC, MSC: 6. Security Mode Control + GANC->>MS: 7. GA-RRC DL DIRECT TRANSFER (Setup) + MS->>GANC: 8. GA-RRC UL DIRECT TRANSFER (Call Confirmed) + Note over MS, GANC, MSC: 9. Bearer establishment procedure + MS->>GANC: 10. GA-RRC UL DIRECT TRANSFER (Alerting) + MS->>GANC: 11. GA-RRC UL DIRECT TRANSFER (Connect) + GANC->>MS: 12. GA-RRC DL DIRECT TRANSFER (Connect Ack) + Note over MS, GANC, MSC: 13. Voice traffic + +``` + +Sequence diagram for Mobile Terminated CS Call showing interactions between MS, GANC, and MSC. + +**Figure 51: Mobile Terminated CS Call** + +1. A mobile-terminated call arrives at the MSC. The MSC sends a RANAP *Paging* message to the GANC identified through the last *Location Update* received by it and includes the TMSI if available. The IMSI of the mobile being paged is always included in the request. Note that the paging message may also be sent from the SGSN to the GANC (i.e., if the Gs interface is present between MSC/VLR and SGSN). +2. The GANC identifies the MS registration context using the IMSI provided by the MSC. It then pages the MS using the GA-RRC PAGING REQUEST message. The message includes the TMSI, if available in the request from the MSC; else it includes only the IMSI of the MS. The message includes the CN Domain identity (CS or PS). +3. The MS responds with a GA-RRC INITIAL DIRECT TRANSFER message containing the Paging Response message. The message includes the CN Domain identity (CS or PS). The CS domain GA-RRC sublayer entity in the MS transitions to the GA-RRC-CONNECTED state. +4. The GANC establishes an SCCP connection to the MSC. The GANC then forwards the paging response to the MSC using the RANAP *Initial UE Message*. Subsequent NAS messages between the MS and core network will be sent between GANC and MSC using the RANAP *Direct Transfer* message. +5. The MSC may optionally authenticate the MS using standard UTRAN authentication procedures. +6. The MSC normally updates the security configuration in the MS, via the GANC, as described in clause 9.8. + +7. The MSC initiates call setup using the *Setup* message sent to the MS via GANC. GANC forwards this message to the MS in the GA-RRC DL DIRECT TRANSFER message. +8. The MS responds with *Call Confirmed* using the GA-RRC UL DIRECT TRANSFER after checking it's compatibility with the bearer service requested in the *Setup* and modifying the bearer service as needed. If the *Setup* included the signal information element, the MS alerts the user using the indicated signal, else the MS alerts the user after the successful configuration of the user plane. The GANC forwards the *Call Confirmed* message to the MSC. +9. The MSC initiates the assignment procedure with the GANC, which triggers the setup of the RTP stream (voice bearer channel) between the GANC and MS, same as steps 8-13 in the MO call scenario described in clause 9.10. +10. The MS signals that it is alerting the user, via the *Alerting* message contained in the GA-RRC UL DIRECT TRANSFER. The GANC forwards the *Alerting* message to the MSC. The MSC sends a corresponding alerting message to the calling party. +11. The MS signals that the called party has answered, via the *Connect* message contained in the GA-RRC UL DIRECT TRANSFER. The GANC forwards the *Connect* message to the MSC. The MSC sends a corresponding *Connect* message to the calling party and through connects the audio. The MS connects the user to the audio path. +12. The MSC acknowledges via the *Connect Ack* message to the GANC. GANC forwards this message to the MS in the GA-RRC DL DIRECT TRANSFER. The two parties on the call are connected on the audio path. +13. Bi-directional voice traffic flows between the MS and MSC through the GANC. + +## 9.12 CS Call Clearing + +### 9.12.1 CS Call Release + +The following figure shows CS call clearing initiated by the MS. This scenario assumes that the MSC uses Iu Release to release the call (i.e., versus a separate RAB Release then Iu Release). + +![Sequence diagram for MS initiated CS Call release showing message exchange between MS, GANC, and MSC.](53001b5ae3f65139f78db410bb41ae30_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant MSC + MS->>GANC: 1. GA-RRC UL DIRECT TRANSFER (Disconnect) + GANC->>MSC: (Disconnect) + MSC->>GANC: 2. GA-RRC DL DIRECT TRANSFER (Release) + GANC->>MS: (Release) + MS->>GANC: 3. GA-RRC UL DIRECT TRANSFER (Release Complete) + GANC->>MSC: (Release Complete) + Note over MS,MSC: 4. GA-RRC Connection Release + +``` + +Sequence diagram for MS initiated CS Call release showing message exchange between MS, GANC, and MSC. + +**Figure 52: MS initiated CS Call release** + +1. The MS sends the *Disconnect* message to the CN to release the call. This message is contained in the GA-RRC UL DIRECT TRANSFER message between MS and GANC. The GANC forwards the *Disconnect* message to the CN (i.e., using the RANAP *Direct Transfer* message). +2. The CN responds with a *Release* message to the GANC. The GANC forwards this message to the MS using the GA-RRC DL DIRECT TRANSFER message. +3. The MS responds with the *Release Complete* message. This message is contained within the GA-RRC UL DIRECT TRANSFER message between MS and GANC. The GANC forwards the *Disconnect* message to the CN. +4. The CN triggers the release of connection as described in clause 9.7.2. + +### 9.12.2 CS Channel Release + +The following figure shows CS channel release (i.e., user plane only) corresponding to the Iu RAB Release procedure. + +![Sequence diagram for CS channel release showing interactions between MS, GANC, and MSC.](20cb2d2cc18d663dc1b82453c67250bb_img.jpg) + +``` + +sequenceDiagram + participant MSC + participant GANC + participant MS + Note right of MSC: 1. RAB Assignment Request + MSC->>GANC: 1. RAB Assignment Request + Note left of GANC: 2. GA-RRC DEACTIVATE CHANNEL + GANC->>MS: 2. GA-RRC DEACTIVATE CHANNEL + Note left of MS: 3. GA-RRC DEACTIVATE CHANNEL COMPLETE + MS->>GANC: 3. GA-RRC DEACTIVATE CHANNEL COMPLETE + Note right of GANC: 4. RAB Assignment Response + GANC->>MSC: 4. RAB Assignment Response + +``` + +Sequence diagram for CS channel release showing interactions between MS, GANC, and MSC. + +**Figure 53: CS channel release** + +1. The CN indicates to the GANC to release the RAB allocated to the MS (identified by the RAB ID), via the RANAP *RAB Assignment Request* message. +2. The GANC commands the MS to release the CS user plane channel (but maintain the CS signalling connection), using the GA-RRC DEACTIVATE CHANNEL message. The message includes the CN Domain ID (indicating CS) and the RAB ID. +3. The MS confirms CS channel release to the GANC using the GA-RRC DEACTIVATE CHANNEL COMPLETE message. The MS remains in the GA-RRC-CONNECTED state. +4. The GANC confirms resource release to CN using the *RAB Assignment Response* message. + +## 9.13 CS Channel Modification + +The GANC may initiate the CS channel modification procedure when it determines that one or more active CS channels require modification; e.g., based on information received from the MSC in the RAB Assignment Request message or based on local GANC logic. For example, the GANC may initiate this procedure if it detects "packet loss" and handover to GERAN/UTRAN is not possible or desired. CS channel modification and PTC modification use the same messages and the same basic message flows, but differ in the content of the messages. + +The GANC may modify the following parameters: + +- RAB Configuration +- Sample Size +- RTP UDP Port +- GANC IP Address +- Multi-rate Configuration 2 +- RTP Redundancy Configuration +- NAS Synchronisation Indicator +- RTCP UDP Port + +![Sequence diagram for CS Channel Modification showing interactions between MS, GANC, and MSC.](dbd4bab54b57e8d1abf80e3de6471130_img.jpg) + +``` +sequenceDiagram + participant MS + participant GANC + participant MSC + Note right of MSC: 1. CS call is established + GANC->>MS: 2. GA-RRC MODIFY CHANNEL + MS->>GANC: 3. GA-RRC MODIFY CHANNEL ACKNOWLEDGE +``` + +The diagram illustrates the sequence of messages for CS Channel Modification. It involves three entities: MS (Mobile Station), GANC (GAN Controller), and MSC (Mobile Switching Center). The sequence starts with a message '1. CS call is established' from the MSC to the MS. Next, the GANC sends a message '2. GA-RRC MODIFY CHANNEL' to the MS. Finally, the MS responds with a message '3. GA-RRC MODIFY CHANNEL ACKNOWLEDGE' to the GANC. + +Sequence diagram for CS Channel Modification showing interactions between MS, GANC, and MSC. + +**Figure 54: CS Channel Modification** + +1. A call is established as described in clauses 9.10 or 9.11. +2. The GANC sends the GA-RRC MODIFY CHANNEL message to the MS to modify parameters for the established call. +3. The MS responds with the GA-RRC MODIFY CHANNEL ACKNOWLEDGE message to the GANC. + +## 9.14 CS Handover between GAN Iu mode and GERAN/UTRAN mode + +### 9.14.1 CS Handover from GERAN to GAN + +The description of the GERAN to GAN Handover procedure assumes the following: + +- the MS is on an active call on the GERAN; and +- its mode selection is GAN-preferred, or if GERAN/UTRAN/E-UTRAN-preferred, the RxLev from the current serving cell drops below a defined threshold; and +- the MS has successfully registered with a GANC, allowing the MS to obtain GAN system information; and +- the GANC has directed the MS to operate in GAN Iu mode; and +- the GERAN provides information on neighbouring 3G cells such that one of the cells in the 3G neighbour list matches the 3G cell information associated with the GANC, as provided in the AS-related component of the system information obtained from the GANC. + +#### 9.14.1.1 Normal case: IMSI is present in Relocation Request message + +![Sequence diagram showing CS Handover from GERAN to GAN (IMSI in Relocation Request). The diagram illustrates the interaction between MS, GANC, BSC, and MSC. The MS starts in GA-RC-REGISTERED state and ends in GA-RC-CONNECTED state. The sequence includes 15 steps: 1. Um: Measurement Report (MS to BSC), 2. Handover Required (BSC to MSC), 3. Relocation Request (MSC to GANC), 4. Iu Bearer Establishment and Iu UP Initialization (GANC to MSC), 5. GA-RRc RELOCATION REQUEST (GANC to MS), 6. GA-RRc RELOCATION REQUEST ACK (MS to GANC), 7. Relocation Request Acknowledge (Handover To UTRAN Command) (GANC to MSC), 8. Handover Command (Handover To UTRAN Command) (MSC to GANC), 9. Um: Intersystem to UTRAN Handover Command (Handover to UTRAN Command) (GANC to MS), 10. GA-RRc RELOCATION COMPLETE (MS to GANC), 11. Relocation Detect (GANC to MSC), 12. Voice traffic (MSC to MS), 13. Relocation Complete (GANC to MSC), 14. Clear Command (MSC to BSC), 15. Clear Complete (BSC to MSC).](64cda8ce20067bc360ce2f3a5c9352b7_img.jpg) + +Sequence diagram showing CS Handover from GERAN to GAN (IMSI in Relocation Request). The diagram illustrates the interaction between MS, GANC, BSC, and MSC. The MS starts in GA-RC-REGISTERED state and ends in GA-RC-CONNECTED state. The sequence includes 15 steps: 1. Um: Measurement Report (MS to BSC), 2. Handover Required (BSC to MSC), 3. Relocation Request (MSC to GANC), 4. Iu Bearer Establishment and Iu UP Initialization (GANC to MSC), 5. GA-RRc RELOCATION REQUEST (GANC to MS), 6. GA-RRc RELOCATION REQUEST ACK (MS to GANC), 7. Relocation Request Acknowledge (Handover To UTRAN Command) (GANC to MSC), 8. Handover Command (Handover To UTRAN Command) (MSC to GANC), 9. Um: Intersystem to UTRAN Handover Command (Handover to UTRAN Command) (GANC to MS), 10. GA-RRc RELOCATION COMPLETE (MS to GANC), 11. Relocation Detect (GANC to MSC), 12. Voice traffic (MSC to MS), 13. Relocation Complete (GANC to MSC), 14. Clear Command (MSC to BSC), 15. Clear Complete (BSC to MSC). + +**Figure 55: CS Handover from GERAN to GAN (IMSI in Relocation Request)** + +- The MS has successfully registered with the GANC and begins to include GAN Iu mode cell information in the *Measurement Report message* to the GERAN. The MS reports the highest signal level for the GAN Iu mode cell. This is not the actual measured signal level on GAN, rather an artificial value (i.e., RxLev = 63), allowing the MS to indicate preference for the GAN. +- Based on MS measurement reports and other internal algorithms, the GERAN BSC decides to handover to the GAN Iu mode cell. The BSC starts the handover preparation by sending a *Handover Required* message to the MSC, identifying the target 3G RNC (GANC). +- The MSC requests the target GANC to allocate resources for the handover using the *Relocation Request* message. The MS is identified by the included IMSI parameter. +- The Iu bearer is established per standard Iu procedures. In the case of the ATM-based Iu-cs interface, this may include the exchange of ALCAP signalling between the GANC and the MSC to setup the ATM virtual circuit. For both ATM and IP-based Iu-cs interface types, Iu bearer establishment may also include the Iu UP initialization exchange, if Iu UP support mode is required as indicated by the MSC in the RANAP *Relocation Request* message. +- The GANC sends the GA-RRc RELOCATION REQUEST message to the MS including bearer path setup information such as: + - RAB ID (received from MSC in step 3) + - Multi-rate codec configuration. + - UDP port & the IP address for the uplink RTP stream. + - Voice sample size. + +6. The MS sends the GA-RRC RELOCATION REQUEST ACK to the GANC indicating that the MS has successfully established resources for the call and including the UDP port for the downlink RTP stream. +7. The GANC builds a *Handover to UTRAN Command* message and sends it to the MSC through the *Relocation Request Acknowledge* message. +8. The MSC forwards the *Handover to UTRAN Command* message to the GERAN BSC in the BSSMAP *Handover Command* message, completing the handover preparation. +9. The GERAN BSC sends the *Intersystem to UTRAN Handover Command* message, containing the *Handover to UTRAN Command* message, to the MS to initiate handover to GAN Iu mode. The MS does not switch its audio path from GERAN to GAN until handover completion (i.e., until it sends the GA-RRC RELOCATION COMPLETE message) to keep the audio interruption short. +10. The MS transmits the GA-RRC RELOCATION COMPLETE message to indicate the completion of the handover procedure. It switches the user from the GERAN user plane to the GAN Iu mode user plane. +11. The GANC indicates to the MSC that it has detected the MS, using *Relocation Detect* message. The MSC can optionally now switch the user plane from the source GERAN to the target GAN. +12. Bi-directional voice traffic is now flowing between the MS and CN, via GANC. +13. The GANC indicates the handover is complete, using the *Relocation Complete* message. If it had not done so before, the MSC now switches the user plane from source GERAN to target GAN. +14. Finally, the MSC tears down the connection to the source GERAN, using *Clear Command* message. +15. The source GERAN confirms the release of GERAN resources allocated for this call, using *Clear Complete* message. + +#### 9.14.1.2 Exception Case: No IMSI in Relocation Request + +![Sequence diagram for CS Handover from GERAN to GAN (No IMSI in Relocation Request). The diagram shows the interaction between MS, GANC, BSC, and MSC. The MS starts in GA-RC-REGISTERED state and ends in GA-RC-CONNECTED state. The sequence of messages is: 1. Um: Measurement Report (MS to BSC); 2. Handover Required (BSC to MSC); 3. Relocation Request (MSC to GANC); 4. Iu Bearer Establishment and Iu UP Initialization (GANC to MSC); 5. Relocation Request Acknowledge (Handover To UTRAN Command) (MSC to GANC); 6. Handover Command (Handover To UTRAN Command) (GANC to BSC); 7. Um: Intersystem to UTRAN Handover Command (Handover to UTRAN Command) (BSC to MS); 8. GA-RRC RELOCATION ACCESS (MS to GANC); 9. GA-RRC ACTIVATE CHANNEL (GANC to MS); 10. GA-RRC ACTIVATE CHANNEL ACK (MS to GANC); 11. GA-RRC ACTIVATE CHANNEL COMPLETE (GANC to MS); 12. GA-RRC RELOCATION COMPLETE (MS to GANC); 13. Relocation Detect (GANC to MSC); 14. Voice traffic (MSC to MS); 15. Relocation Complete (GANC to MSC); 16. Clear Command (MSC to BSC); 17. Clear Complete (BSC to MSC).](1c79f31a718d63814feb28ab46f64f19_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant BSC + participant MSC + + Note left of MS: GA-RC-REGISTERED + MS->>BSC: 1. Um: Measurement Report + BSC->>MSC: 2. Handover Required + MSC->>GANC: 3. Relocation Request + GANC->>MSC: 4. Iu Bearer Establishment and Iu UP Initialization + MSC->>GANC: 5. Relocation Request Acknowledge (Handover To UTRAN Command) + GANC->>BSC: 6. Handover Command (Handover To UTRAN Command) + BSC->>MS: 7. Um: Intersystem to UTRAN Handover Command (Handover to UTRAN Command) + Note left of MS: GA-RC-CONNECTED + MS->>GANC: 8. GA-RRC RELOCATION ACCESS + GANC->>MS: 9. GA-RRC ACTIVATE CHANNEL + MS->>GANC: 10. GA-RRC ACTIVATE CHANNEL ACK + GANC->>MS: 11. GA-RRC ACTIVATE CHANNEL COMPLETE + MS->>GANC: 12. GA-RRC RELOCATION COMPLETE + GANC->>MSC: 13. Relocation Detect + MSC->>MS: 14. Voice traffic + GANC->>MSC: 15. Relocation Complete + MSC->>BSC: 16. Clear Command + BSC->>MSC: 17. Clear Complete + +``` + +Sequence diagram for CS Handover from GERAN to GAN (No IMSI in Relocation Request). The diagram shows the interaction between MS, GANC, BSC, and MSC. The MS starts in GA-RC-REGISTERED state and ends in GA-RC-CONNECTED state. The sequence of messages is: 1. Um: Measurement Report (MS to BSC); 2. Handover Required (BSC to MSC); 3. Relocation Request (MSC to GANC); 4. Iu Bearer Establishment and Iu UP Initialization (GANC to MSC); 5. Relocation Request Acknowledge (Handover To UTRAN Command) (MSC to GANC); 6. Handover Command (Handover To UTRAN Command) (GANC to BSC); 7. Um: Intersystem to UTRAN Handover Command (Handover to UTRAN Command) (BSC to MS); 8. GA-RRC RELOCATION ACCESS (MS to GANC); 9. GA-RRC ACTIVATE CHANNEL (GANC to MS); 10. GA-RRC ACTIVATE CHANNEL ACK (MS to GANC); 11. GA-RRC ACTIVATE CHANNEL COMPLETE (GANC to MS); 12. GA-RRC RELOCATION COMPLETE (MS to GANC); 13. Relocation Detect (GANC to MSC); 14. Voice traffic (MSC to MS); 15. Relocation Complete (GANC to MSC); 16. Clear Command (MSC to BSC); 17. Clear Complete (BSC to MSC). + +**Figure 55a: CS Handover from GERAN to GAN (No IMSI in Relocation Request)** + +- 1-2. Same as steps 1-2 in clause 9.14.1.1. +3. The MSC requests the target GANC to allocate resources for the handover using the *Relocation Request* message. The IMSI parameter is not included in the message since it is not available at the MSC. +4. Same as step 4 in clause 9.14.1.1. +- 5-7. Same as steps 8-10 in clause 9.14.1.1. +8. The MS accesses the GANC using the GA-RRC RELOCATION ACCESS message, and provides the entire *Intersystem to UTRAN Handover Command* message received from GERAN. Information in the *Intersystem to UTRAN Handover Command* message (e.g. Handover Reference) allows the GANC to correlate the handover to the *Relocation Request Acknowledge* message sent to the MSC in step 5. +- 9-11. The GANC sets up the bearer path with the MS, using the procedure as in steps 10 to 12 in clause 9.10. +12. The MS transmits the GA-RRC RELOCATION COMPLETE message to indicate the completion of the handover procedure. It switches the user from the GERAN user plane to the GAN Iu mode user plane. + +13. The GANC indicates to the MSC that it has detected the MS, using the *Relocation Detect* message. The MSC can optionally now switch the user plane from the source GERAN to the target GAN. +14. Bi-directional voice traffic is now flowing between the MS and MSC, via the GANC. +15. The target GANC indicates the handover is complete, using the *Relocation Complete* message. If it had not done so before, the MSC now switches the user plane from source GERAN to target GAN. +16. Finally, the MSC tears down the connection to the source GERAN, using *Clear Command* message. +17. The source GERAN confirms the release of GERAN resources allocated for this call, using *Clear Complete* message. + +### 9.14.2 CS Handover from UTRAN to GAN + +The description of the UTRAN to GAN CS handover procedure assumes the following: + +- the MS is on an active call on the UTRAN; and +- the MS has successfully registered with a GANC, allowing the MS to obtain GAN system information; and +- the GANC has directed the MS to operate in GAN Iu mode; and +- the UTRAN provides information on neighbouring cells such that one of the cells in the neighbour list matches the cell associated with the GANC, as provided in the AS-related component of the system information obtained from GANC. + +#### 9.14.2.1 Normal Case: IMSI is present in Relocation Request message + +![Sequence diagram for CS Handover from UTRAN to GAN (IMSI in Relocation Request). The diagram shows the interaction between MS, GANC, RNC, and MSC. The MS sends a Measurement Report to the RNC. The RNC sends a Relocation Required to the MSC. The MSC sends a Relocation Request to the GANC. The GANC performs Iu Bearer Establishment and Iu UP Initialization. The GANC sends a GA-RRC RELOCATION REQUEST to the MS. The MS responds with a GA-RRC RELOCATION REQUEST ACK. The GANC sends a Relocation Request Acknowledge (Physical Channel Reconfiguration) to the MSC. The MSC sends a Relocation Command (Physical Channel Reconfiguration) to the RNC. The RNC sends a Physical Channel Reconfiguration to the MS. The MS sends a GA-RRC RELOCATION COMPLETE to the GANC. The GANC sends a Relocation Detect to the MSC. The MSC starts voice traffic to the MS. The GANC sends a Relocation Complete to the MSC. The MSC sends an Iu Release Command to the RNC. The RNC responds with an Iu Release Complete.](8f8caebe58364416a2eda21039d8c7bf_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant RNC + participant MSC + + Note left of MS: GA-RC-REGISTERED + MS->>RNC: 1. Uu: Measurement Report + RNC->>MSC: 2. Relocation Required + MSC->>GANC: 3. Relocation Request + Note right of GANC: 4. Iu Bearer Establishment and Iu UP Initialization + GANC->>MS: 5. GA-RRC RELOCATION REQUEST + MS->>GANC: 6. GA-RRC RELOCATION REQUEST ACK + Note left of MS: GA-RRC-CONNECTED + GANC->>MSC: 7. Relocation Request Acknowledge (Physical Channel Reconfiguration) + MSC->>RNC: 8. Relocation Command (Physical Channel Reconfiguration) + RNC->>MS: 9. Uu: Physical Channel Reconfiguration + MS->>GANC: 10. GA-RRC RELOCATION COMPLETE + GANC->>MSC: 11. Relocation Detect + MSC->>MS: 12. Voice traffic + GANC->>MSC: 13. Relocation Complete + MSC->>RNC: 14. Iu Release Command + RNC->>MSC: 15. Iu Release Complete + +``` + +Sequence diagram for CS Handover from UTRAN to GAN (IMSI in Relocation Request). The diagram shows the interaction between MS, GANC, RNC, and MSC. The MS sends a Measurement Report to the RNC. The RNC sends a Relocation Required to the MSC. The MSC sends a Relocation Request to the GANC. The GANC performs Iu Bearer Establishment and Iu UP Initialization. The GANC sends a GA-RRC RELOCATION REQUEST to the MS. The MS responds with a GA-RRC RELOCATION REQUEST ACK. The GANC sends a Relocation Request Acknowledge (Physical Channel Reconfiguration) to the MSC. The MSC sends a Relocation Command (Physical Channel Reconfiguration) to the RNC. The RNC sends a Physical Channel Reconfiguration to the MS. The MS sends a GA-RRC RELOCATION COMPLETE to the GANC. The GANC sends a Relocation Detect to the MSC. The MSC starts voice traffic to the MS. The GANC sends a Relocation Complete to the MSC. The MSC sends an Iu Release Command to the RNC. The RNC responds with an Iu Release Complete. + +**Figure 56: CS Handover from UTRAN to GAN (IMSI in Relocation Request)** + +1. The MS begins to include information about a GAN Iu mode cell in the *Measurement Report* message sent to the RNC. See Annex B.2.1 for further information. +2. Based on MS measurement reports and other internal algorithms, the RNC decides to initiate handover to the GAN Iu mode cell. The RNC starts the preparation phase of the Relocation procedure by sending a *Relocation Required* message to the MSC, identifying the target (GAN Iu mode) cell. +- 3-6. Same as steps 3-6 for CS handover from GERAN to GAN in clause 9.14.1.1. +7. The GANC acknowledges the relocation request message, using *Relocation Request Acknowledge* message, indicating it can support the requested handover, and including a *Physical Channel Reconfiguration* message that indicates the radio channel to which the MS should be directed. +8. The MSC sends the *Relocation Command* message to the RNC, completing the relocation preparation. +9. The RNC sends the *PHYSICAL CHANNEL RECONFIGURATION* message to the MS to initiate handover to GAN Iu mode. The MS does not switch its audio path from UTRAN to GAN until handover completion (i.e., until it sends the GA-RRC HANDOVER COMPLETE message) to keep the audio interruption short. +- 10-13. Same as steps 10-13 for CS handover from GERAN to GAN in clause 9.14.1.1. +14. Finally, the MSC tears down the connection to the source RNC, using *Iu Release Command*. +15. The source RNC confirms the release of UTRAN resources allocated for this call, using *Iu Release Complete*. + +### 9.14.2.2 Exception Case: No IMSI in Relocation Request + +![Sequence diagram for CS Handover from UTRAN to GAN (No IMSI in Relocation Request). The diagram shows the interaction between MS, GANC, RNC, and MSC. The MS sends a Measurement Report to the RNC, which triggers a Relocation Required to the MSC. The MSC sends a Relocation Request to the GANC. The GANC performs Iu Bearer Establishment and Iu UP Initialization. The MSC sends a Relocation Request Acknowledge (Physical Channel Reconfiguration) to the RNC, which then sends a Relocation Command (Physical Channel Reconfiguration) to the MS. The MS sends a GA-RRC RELOCATION ACCESS to the GANC. The GANC performs GA-RRC channel activation (ACTIVATE CHANNEL, ACK, COMPLETE) and then the MS sends a GA-RRC RELOCATION COMPLETE. The GANC sends a Relocation Detect to the MSC, followed by Voice traffic. The MSC sends a Relocation Complete to the GANC, which then sends an Iu Release Command to the RNC, and the RNC responds with an Iu Release Complete.](28f2f470a7b2446ae5f525123534383c_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant RNC + participant MSC + + Note left of MS: GA-RC-REGISTERED + MS->>RNC: 1. Uu: Measurement Report + RNC->>MSC: 2. Relocation Required + MSC->>GANC: 3. Relocation Request + GANC->>MSC: 4. Iu Bearer Establishment and Iu UP Initialization + MSC->>RNC: 5. Relocation Request Acknowledge (Physical Channel Reconfiguration) + RNC->>MS: 6. Relocation Command (Physical Channel Reconfiguration) + MS->>GANC: 7. Uu: Physical Channel Reconfiguration + Note left of MS: GA-RRC-CONNECTED + MS->>GANC: 8. GA-RRC RELOCATION ACCESS + GANC->>MS: 9. GA-RRC ACTIVATE CHANNEL + MS->>GANC: 10. GA-RRC ACTIVATE CHANNEL ACK + GANC->>MS: 11. GA-RRC ACTIVATE CHANNEL COMPLETE + MS->>GANC: 12. GA-RRC RELOCATION COMPLETE + GANC->>MSC: 13. Relocation Detect + MSC->>MS: 14. Voice traffic + MSC->>GANC: 15. Relocation Complete + GANC->>RNC: 16. Iu Release Command + RNC->>MSC: 17. Iu Release Complete + +``` + +Sequence diagram for CS Handover from UTRAN to GAN (No IMSI in Relocation Request). The diagram shows the interaction between MS, GANC, RNC, and MSC. The MS sends a Measurement Report to the RNC, which triggers a Relocation Required to the MSC. The MSC sends a Relocation Request to the GANC. The GANC performs Iu Bearer Establishment and Iu UP Initialization. The MSC sends a Relocation Request Acknowledge (Physical Channel Reconfiguration) to the RNC, which then sends a Relocation Command (Physical Channel Reconfiguration) to the MS. The MS sends a GA-RRC RELOCATION ACCESS to the GANC. The GANC performs GA-RRC channel activation (ACTIVATE CHANNEL, ACK, COMPLETE) and then the MS sends a GA-RRC RELOCATION COMPLETE. The GANC sends a Relocation Detect to the MSC, followed by Voice traffic. The MSC sends a Relocation Complete to the GANC, which then sends an Iu Release Command to the RNC, and the RNC responds with an Iu Release Complete. + +**Figure 56a: CS Handover from UTRAN to GAN (No IMSI in Relocation Request)** + +1-2. Same as steps 1-2 in clause 9.14.2.1. + +3. The MSC requests the target GANC to allocate resources for the handover using the *Relocation Request* message. The IMSI parameter is not included in the message since it is not available at the MSC. + +4. Same as step 4 in clause 9.14.2.1. + +5-7. Same as steps 7-9 in clause 9.14.2.1. + +8. The MS accesses the GANC using the GA-RRC RELOCATION ACCESS message, and provides the entire *Physical Channel Reconfiguration* message received from UTRAN. Information in the *Physical Channel Reconfiguration* message allows the GANC to correlate the handover to the *Relocation Request Acknowledge* message sent to the MSC in step 5. + +9-11. The GANC sets up the bearer path with the MS, using the procedure as in steps 10 to 12 in sub-clause 9.10. + +12. The MS transmits the GA-RRC RELOCATION COMPLETE message to indicate the completion of the handover procedure at its end. It switches the user from the UTRAN user plane to the GAN user plane. + +13. The GANC indicates to the MSC that it has detected the MS, using the *Relocation Detect* message. The MSC can optionally now switch the user plane from the source UTRAN to the target GAN. +14. Bi-directional voice traffic is now flowing between the MS and MSC, via the GANC. +15. The target GANC indicates the handover is complete, using the *Relocation Complete* message. If it had not done so before, the MSC now switches the user plane from source UTRAN to target GAN. +16. Finally, the MSC tears down the connection to the source RNC, using *Iu Release Command*. +17. The source RNC confirms the release of UTRAN resources allocated for this call, using *Iu Release Complete*. + +### 9.14.3 CS Handover from GAN Iu mode to GERAN + +The procedure description in this sub-clause assumes the following: + +- the MS is on an active call in GAN Iu mode; and +- the GERAN becomes available; and + - the MS mode selection is GERAN/UTRAN/E-UTRAN-preferred; or + - the MS mode selection is GAN-preferred and the MS begins to leave GAN coverage, based on its local measurements, received RTCP reports, as well as any uplink quality indications received from the GANC. + +![Sequence diagram for CS Handover from GAN lu mode to GERAN. The diagram shows interactions between MS, GANC, BSS, and MSC. The process starts with the MS sending a GA-RRC UPLINK QUALITY INDICATION to the GANC. The GANC then sends a GA-RRC RELOCATION INFORMATION to the MS. The GANC sends a Relocation Required to the MSC. The MSC sends a Handover Request to the BSS. The BSS sends a Handover Request Ack to the MSC. The MSC sends a Relocation Command to the GANC. The GANC sends a GA-RRC RELOCATION COMMAND to the MS. The MS sends an Um: Handover Access to the GANC. The GANC sends a Handover Detect to the BSS. The BSS sends a Voice to the MSC. The MSC sends an Um: Physical Information to the GANC. The GANC sends an Um: Handover Complete to the BSS. The BSS sends a Handover Complete to the MSC. The MSC sends a Voice traffic to the GANC. The GANC sends an lu Release Command to the MSC. The MSC sends a GA-RRC RELEASE to the GANC. The GANC sends an lu Release Complete to the MSC. The GANC sends a GA-RRC RELEASE COMPLETE to the MS. The MS sends a GA-RC DEREGISTER to the GANC.](3750b0149a6380885998ab3ca6a8787c_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant BSS + participant MSC + Note left of MS: Ongoing GAN CS connection + GANC->>MS: 1. GA-RRC UPLINK QUALITY INDICATION + MS->>GANC: 2. GA-RRC RELOCATION INFORMATION + GANC->>MSC: 3. Relocation Required + MSC->>BSS: 4. Handover Request + BSS->>MSC: 5. Handover Request Ack + MSC->>GANC: 6. Relocation Command + GANC->>MS: 7. GA-RRC RELOCATION COMMAND + MS->>GANC: 8. Um: Handover Access + GANC->>BSS: 9. Handover Detect + BSS->>MSC: 10. Voice + MSC->>GANC: 11. Um: Physical Information + GANC->>BSS: 12. Um: Handover Complete + BSS->>MSC: 13. Handover Complete + MSC->>GANC: 14. Voice traffic + GANC->>MSC: 15. lu Release Command + MSC->>GANC: 16. GA-RRC RELEASE + GANC->>MSC: 17. lu Release Complete + GANC->>MS: 18. GA-RRC RELEASE COMPLETE + MS->>GANC: 19. GA-RC DEREGISTER + +``` + +Sequence diagram for CS Handover from GAN lu mode to GERAN. The diagram shows interactions between MS, GANC, BSS, and MSC. The process starts with the MS sending a GA-RRC UPLINK QUALITY INDICATION to the GANC. The GANC then sends a GA-RRC RELOCATION INFORMATION to the MS. The GANC sends a Relocation Required to the MSC. The MSC sends a Handover Request to the BSS. The BSS sends a Handover Request Ack to the MSC. The MSC sends a Relocation Command to the GANC. The GANC sends a GA-RRC RELOCATION COMMAND to the MS. The MS sends an Um: Handover Access to the GANC. The GANC sends a Handover Detect to the BSS. The BSS sends a Voice to the MSC. The MSC sends an Um: Physical Information to the GANC. The GANC sends an Um: Handover Complete to the BSS. The BSS sends a Handover Complete to the MSC. The MSC sends a Voice traffic to the GANC. The GANC sends an lu Release Command to the MSC. The MSC sends a GA-RRC RELEASE to the GANC. The GANC sends an lu Release Complete to the MSC. The GANC sends a GA-RRC RELEASE COMPLETE to the MS. The MS sends a GA-RC DEREGISTER to the GANC. + +**Figure 57: CS Handover from GAN lu mode to GERAN** + +1. The GANC may send a GA-RRC UPLINK QUALITY INDICATION if there is a problem with the uplink quality for the ongoing call. Uplink Quality Indication is information sent by the GANC to the MS indicating the crossing of a uplink quality threshold in the uplink direction. Whenever the MS receives an indication of bad quality, it should start the handover procedure, as described in the next step. Alternatively, MS can use its local measurements or received RTCP reports, to decide to initiate the handover procedure. +2. The MS sends the GA-RRC RELOCATION INFORMATION message to the GANC including a list of target GERAN cells, identified by CGI, in order of preference (e.g. ranked by C1 path loss parameter) for handover, and the received signal strength for each identified GERAN cell. This list is the most recent information available from the GSM RR subsystem. In addition, the GA-RRC RELOCATION INFORMATION message may include a list of target UTRAN cells ranked in order of preference for handover, and the received signal strength for each identified UTRAN cell. +3. If the Serving GANC selects a target GERAN cell, the handover to GERAN procedure is performed. The Serving GANC starts the handover preparation by signalling to the MSC the need for handover, using *Relocation Required*, and including the selected GERAN cell from the list provided by the MS. +4. The MSC requests the target GERAN to allocate the necessary resources, using *Handover Request*. +5. The target GERAN builds a GERAN RRC *Handover Command* message providing information on the channel allocated and sends it to the MSC through the *Handover Request Acknowledge* message. + +6. The MSC signals the GANC to handover the MS to the GERAN, using the *Relocation Command* message which includes the encapsulated GERAN RRC *Handover Command* message, ending the handover preparation phase. +7. GANC transmits the GA-RRC RELOCATION COMMAND to the MS including the UTRAN RRC *Handover from UTRAN Command* message, which encapsulates the GERAN RRC *Handover Command* message. +8. The MS transmits *Handover Access* containing the handover reference element to allow the target GERAN to correlate this handover access with the *Handover Command* message transmitted earlier to the MSC in response to the *Handover Required*. +9. The target GERAN confirms the detection of the handover to the MSC, using the *Handover Detect* message. +10. The MSC may at this point switch the user plane to the target BSS. +11. The GERAN provides *Physical Information* to the MS (i.e., *Timing Advance*) to allow the MS to synchronize with the GERAN. +12. The MS signals to the GERAN that the handover is completed, using *Handover Complete*. +13. The GERAN confirms to the MSC the completion of the handover, via *Handover Complete* message. The MSC may use the target CGI used in the Handover procedure for charging purposes. +14. Bi-directional voice traffic is now flowing between the MS and MSC, via the GERAN. +15. On receiving the confirmation of the completion of the handover, the MSC indicates to the GANC to release any resources allocated to the MS, via the *Iu Release Command*. +16. If the GANC has not already received the GA-RC DEREGISTER message from the MS, the GANC commands the MS to release resources, using the GA-RRC RELEASE message. +17. GANC confirms resource release to MSC using the *Iu Release Complete* message. +18. The MS confirms resource release to the GANC using the GA-RRC RELEASE COMPLETE message. +19. The MS may finally deregister from the GANC, using GA-RC DEREGISTER message. Note that the MS may send the GA-RC DEREGISTER message at any time after transitioning from GAN Iu mode to GERAN mode (i.e., after step 12). + +#### 9.14.4 CS Handover from GAN Iu mode to UTRAN + +The procedure description in this sub-clause assumes the following: + +- the MS is on an active call in GAN Iu mode; and +- the MS is capable of operating in all of the GAN, GERAN and UTRAN modes; and +- the UTRAN becomes available; and + - the MS is in GERAN/UTRAN/E-UTRAN-preferred mode; or + - the MS mode selection is GAN preferred and begins to leave GAN coverage, based on its local measurements, received RTCP reports, as well as any uplink quality indications received from the GANC. + +![Sequence diagram for CS Handover from GAN lu mode to UTRAN. The diagram shows the interaction between MS, GANC, RNS, and CN. The process starts with an ongoing GAN CS connection. The MS sends GA-RRC RELOCATION INFORMATION to the GANC. The GANC sends Relocation Required to the CN. The CN sends Relocation Request to the RNS. The RNS sends Relocation Request Ack to the CN. The CN sends Relocation Command to the GANC. The GANC sends GA-RRC RELOCATION COMMAND to the MS. The MS sends Uu: UL Synchronization to the RNS. The RNS sends Relocation Detect to the CN. The CN sends Voice to the RNS. The RNS sends Physical Channel Reconfig Complete to the MS. The RNS sends Relocation Complete to the CN. The CN sends Voice traffic to the MS. The CN sends lu Release Command to the GANC. The GANC sends GA-RRC RELEASE to the MS. The CN sends lu Release Complete to the GANC. The GANC sends GA-RRC RELEASE COMPLETE to the MS. The MS sends GA-RC DEREGISTER to the GANC.](11f18bf0233d812ad2604f88f3385d60_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant RNS + participant CN + Note left of MS: Ongoing GAN CS connection + MS->>GANC: 1. GA-RRC UPLINK QUALITY INDICATION + GANC-->>MS: 2. GA-RRC RELOCATION INFORMATION + GANC->>CN: 3. Relocation Required + CN->>RNS: 4. Relocation Request + RNS->>CN: 5. Relocation Request Ack + CN->>GANC: 6. Relocation Command + GANC->>MS: 7. GA-RRC RELOCATION COMMAND + MS->>RNS: 8. Uu: UL Synchronization + RNS->>CN: 9. Relocation Detect + CN->>RNS: 10. Voice + RNS->>MS: 11. Uu: Physical Channel Reconfig Complete + RNS->>CN: 12. Relocation Complete + CN->>MS: 13. Voice traffic + CN->>GANC: 14. lu Release Command + GANC->>MS: 15. GA-RRC RELEASE + CN->>GANC: 16. lu Release Complete + GANC->>MS: 17. GA-RRC RELEASE COMPLETE + MS->>GANC: 18. GA-RC DEREGISTER + +``` + +Sequence diagram for CS Handover from GAN lu mode to UTRAN. The diagram shows the interaction between MS, GANC, RNS, and CN. The process starts with an ongoing GAN CS connection. The MS sends GA-RRC RELOCATION INFORMATION to the GANC. The GANC sends Relocation Required to the CN. The CN sends Relocation Request to the RNS. The RNS sends Relocation Request Ack to the CN. The CN sends Relocation Command to the GANC. The GANC sends GA-RRC RELOCATION COMMAND to the MS. The MS sends Uu: UL Synchronization to the RNS. The RNS sends Relocation Detect to the CN. The CN sends Voice to the RNS. The RNS sends Physical Channel Reconfig Complete to the MS. The RNS sends Relocation Complete to the CN. The CN sends Voice traffic to the MS. The CN sends lu Release Command to the GANC. The GANC sends GA-RRC RELEASE to the MS. The CN sends lu Release Complete to the GANC. The GANC sends GA-RRC RELEASE COMPLETE to the MS. The MS sends GA-RC DEREGISTER to the GANC. + +**Figure 58: CS Handover from GAN lu mode to UTRAN** + +1. The GANC may send a GA-RRC UPLINK QUALITY INDICATION if there is a problem with the uplink quality for the ongoing call. Uplink Quality Indication is information sent by the GANC to the MS indicating the crossing of a uplink quality threshold in the uplink direction. Whenever the MS receives an indication of bad quality, it should start the handover procedure, as described in the next step. Alternatively, MS can use its local measurements or received RTCP reports, to decide to initiate the handover procedure. +2. The MS sends the GA-RRC RELOCATION INFORMATION message to the Serving GANC including a list of candidate target UTRAN and GERAN cells, in order of preference for handover, and the received signal strength for each identified cell. The UTRAN cells are identified by the PLMN ID, the LAC and the 3G Cell identity (defined in 3GPP TS 25.331 [40]). + +NOTE: The choice of the candidate target UTRAN cells is out of the scope of this technical specification. + +3. If the Serving GANC selects UTRAN as the target RAT, the CS handover to UTRAN procedure is performed. The Serving GANC starts the handover preparation by signalling to the MSC the need for handover, using *Relocation Required* and including the target RNC-ID that the GANC derives from the target UTRAN cell it selects from the list of target UTRAN cells provided by the MS. The GANC may include only a single target RNC-ID in the *Relocation Required* message. The GANC also includes the Source RNC to Target RNC Transparent Container that contains the selected target UTRAN cell ID. +4. The MSC starts the relocation procedure towards the target RNC identified by the Serving GANC. The MSC requests from the target RNC to allocate the necessary resources using *Relocation Request*. + +5. The target RNC builds a *Physical Channel Reconfiguration* message providing information on the allocated UTRAN resources and sends it to the MSC through the *Relocation Request Acknowledge* message. +6. The MSC signals the Serving GANC to handover the MS to the UTRAN, using the *Relocation Command* message (which includes the *Physical Channel Reconfiguration* message), ending the handover preparation phase. +7. The Serving GANC transmits the GA-RRC RELOCATION COMMAND to the MS including the *Physical Channel Reconfiguration* message. +8. Target RNS achieves uplink synchronization on the Uu interface. +9. The target RNC confirms the detection of the handover to the MSC, using the *Relocation Detect* message. +10. The MSC may at this point switch the user plane to the target RNS. +11. The MS signals to the UTRAN that the handover is completed, using *Physical Channel Reconfig Complete*. +12. The UTRAN confirms to the MSC the completion of the handover, via *Relocation Complete* message. If the user plane has not been switched in step 10, the MSC switches the user plane to the target RNS. +13. Bi-directional voice traffic is now flowing between the MS and MSC, via the UTRAN. +14. On receiving the confirmation of the completion of the handover, the MSC indicates to the Serving GANC to release any resources allocated to the MS, via the *Iu Release Command*. +15. If the Serving GANC has not already received the GA-RC DEREGISTER message from the MS, the Serving GANC commands the MS to release resources, using the GA-RRC RELEASE message. +16. The Serving GANC confirms resource release to MSC using the *Iu Release Complete* message. +17. The MS confirms resource release to the Serving GANC using the GA-RRC RELEASE COMPLETE message. +18. The MS may finally deregister from the Serving GANC, using GA-RC DEREGISTER message. Note that the MS may send the GA-RC DEREGISTER message at any time after transitioning from GAN Iu mode to UTRAN mode (i.e., after step 11). + +## 9.15 Cell Change Order between GAN Iu mode and GERAN mode + +While in GERAN, a mobile station may be ordered to perform a cell reselection to GAN Iu mode, by using the Cell Change Order procedures used in GERAN, with no modifications. The mobile station regards the procedure as completed when it has successfully performed Rove In to GAN. + +While the mobile station is involved in a PS session in the GAN Iu mode, there is no identified need for a Cell Change Order procedure. + +## 9.16 GA-RRC Packet Transport Channel Management Procedures + +The GA-RRC Packet Transport Channel (GA-RRC PTC) provides the association between the MS and the network for the transport of PS domain user data over the Up interface in GAN Iu mode. + +The endpoint addresses of the PTC are identified by the IP addresses and UDP ports assigned to the PTC in the MS and GANC during the PTC activation procedure. The GA-RRC PTC is strictly limited to operating over the Up interface and as such all downlink GA-RRC messages sent by the GANC shall terminate at the MS and all uplink GA-RRC messages sent by the MS shall terminate at the GANC. + +Multiple PTC instances between a MS and the GANC may be activated at the same time, using the same endpoint addresses. Each PTC instance is assigned unique GA-RRC Tunnel Endpoint IDs (one on the MS and one on the GANC) during the activation procedure. + +The MS and GANC manage the activation and deactivation of the PTC instances based on the requests for RAB assignment from the SGSN and the configurable PTC Timer. + +## 9.16.1 States of the GA-RRC Packet Transport Channel + +The PS domain GA-RRC sublayer entity in the MS when in the GA-RRC-CONNECTED state can be in one of two PTC substates for each PTC: PTC-INACTIVE or PTC-ACTIVE. + +- **PTC-INACTIVE:** This is the initial/default PTC substate of the PS domain GA-RRC sublayer entity in the MS when in the GA-RRC-CONNECTED state in GAN Iu mode. The MS is not able to send or receive PS domain user data to or from the network using the PTC. The PTC must be activated before domain user data can be transferred via the PTC. When the PTC has been successfully activated between the MS and the GANC, the PS domain GA-RRC sublayer entity in the MS transitions to the PTC-ACTIVE substate for this PTC. +- **PTC-ACTIVE:** The PS domain GA-RRC sublayer entity in the MS is in the GA-RRC-CONNECTED state for this PTC and the PTC is active between the MS and the GANC and the MS is able to send and receive PS domain user data to and from the GANC. + +The following are the possible triggers for GA-RRC PTC activation: + +- The GANC initiates PTC activation when the GANC receives the RAB Assignment message from the SGSN; i.e., the MS receives a GA-RRC ACTIVATE CHANNEL message from the GANC; +- The GANC initiates PTC activation when the GANC receives the Relocation Request message from the SGSN; i.e., the MS receives a GA-RRC RELOCATION REQUEST message from the GANC including PTC information. + +On successful PTC activation and in parallel with transition to the PTC-ACTIVE substate, the MS starts the PTC Timer for this PTC. When the PTC Timer expires, the MS sends a message to the GANC to initiate PTC deactivation, as defined in clause 9.16.4. On successful PTC deactivation, the MS transitions to the PTC-INACTIVE substate for this PTC. + +At any time while the PS domain GA-RRC sublayer entity in the MS is in the GA-RRC-CONNECTED state and the PTC-ACTIVE substate, the MS may receive the GA-RRC DEACTIVATE CHANNEL message for this PTC. The MS de-activates the PTC and transitions to the PTC-INACTIVE substate. + +At any time while the PS domain GA-RRC sublayer entity in the MS is in the GA-RRC-CONNECTED state and the PTC-ACTIVE substate, the MS may receive the GA-RRC RELEASE message indicating the PS domain. In addition to requesting release of the PS GA-RRC connection, this is interpreted by the MS as an implicit PTC de-activation command; i.e. all active PTCs are deactivated. + +At any time while in GAN Iu mode, if the serving RR entity is switched to GSM-RR, UTRAN RRC or E-UTRAN RRC, the PS domain GA-RRC sublayer entity in the MS is disconnected from the GPRS SAPs and the MS enters GERAN/UTRAN/E-UTRAN mode. Simultaneously, the MS shall de-activate the associated PTC(s) regardless of the PTC Timer status for these PTC(s). + +The PS domain GA-RRC sublayer entity in the MS maintains one PTC for each active PDP context. The PTC Timer is restarted whenever any uplink user data packet is sent or downlink user data packet is received related to the PDP context. + +The PTC Timer value is provided to the MS as part of the GAN Registration procedure (i.e., in the GA-RC REGISTER ACCEPT message). + +## 9.16.2 PTC Activation + +### 9.16.2.1 PTC Activation when GANC receives RAB Assignment Request + +The following figure depicts the Packet Transport Channel activation procedure when the GANC receives the RAB Assignment Request message from the SGSN, assuming the PS domain GA-RRC sublayer entity in MS is in the GA-RRC-IDLE state. If the PS domain GA-RRC sublayer entity in MS is already in the GA-RRC-CONNECTED state, step 1 is skipped. + +![Sequence diagram illustrating PTC activation based on RAB Assignment Request. The diagram shows interactions between MS, GANC, and SGSN. The process starts with GA-RRC Connection Establishment, followed by Additional PS signalling procedures. The SGSN sends a RAB Assignment Request to the GANC, which then sends GA-RRC ACTIVATE CHANNEL to the MS. The MS responds with GA-RRC ACTIVATE CHANNEL ACK, and the GANC completes the activation with GA-RRC ACTIVATE CHANNEL COMPLETE. The GANC then sends a RAB Assignment Response to the SGSN. Additional PS signalling procedures follow, and finally, the MS sends GA-RRC PDU to the GANC, which relays it as G-PDU to the SGSN. The SGSN responds with G-PDU to the GANC, which relays it as GA-RRC PDU to the MS. Vertical ellipsis indicates further steps.](18003425d0e8638dde4acc9c5c468c5c_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant SGSN + Note left of MS: GA-RRC-CONNECTED +PTC-INACTIVE + MS->>GANC: 1. GA-RRC Connection Establishment + Note right of GANC: 2. Additional PS signalling procedures + SGSN->>GANC: 3. RAB Assignment Request + GANC->>MS: 4. GA-RRC ACTIVATE CHANNEL + MS->>GANC: 5. GA-RRC ACTIVATE CHANNEL ACK + GANC->>MS: 6. GA-RRC ACTIVATE CHANNEL COMPLETE + Note left of MS: GA-RRC-CONNECTED +PTC-ACTIVE + GANC->>SGSN: 7. RAB Assignment Response + Note right of GANC: 8. Additional PS signalling procedures + MS->>GANC: 9. GA-RRC PDU + GANC->>SGSN: 9. G-PDU + SGSN->>GANC: 10. G-PDU + GANC->>MS: 10. GA-RRC PDU + Note left of MS: ⋮ + +``` + +Sequence diagram illustrating PTC activation based on RAB Assignment Request. The diagram shows interactions between MS, GANC, and SGSN. The process starts with GA-RRC Connection Establishment, followed by Additional PS signalling procedures. The SGSN sends a RAB Assignment Request to the GANC, which then sends GA-RRC ACTIVATE CHANNEL to the MS. The MS responds with GA-RRC ACTIVATE CHANNEL ACK, and the GANC completes the activation with GA-RRC ACTIVATE CHANNEL COMPLETE. The GANC then sends a RAB Assignment Response to the SGSN. Additional PS signalling procedures follow, and finally, the MS sends GA-RRC PDU to the GANC, which relays it as G-PDU to the SGSN. The SGSN responds with G-PDU to the GANC, which relays it as GA-RRC PDU to the MS. Vertical ellipsis indicates further steps. + +**Figure 59: PTC activation based on RAB Assignment Request** + +1. The GA-RRC Connection Establishment procedure is performed as described in clause 9.7. The PS domain GA-RRC sublayer entity in the MS transitions to the GA-RRC-CONNECTED state and the PTC-INACTIVE substate. +2. Additional PS signalling procedures are performed; e.g., to initiate PDP context activation. +3. The SGSN initiates the RAB Assignment procedure and includes the RAB ID, the CN Transport Layer Address (IP address) and the CN Iu Transport Association (GTP-U Tunnel Endpoint Identifier, TEID) for user data. Note that the SGSN may initiate the activation of multiple RABs via a single *RAB Assignment Request* message; in this case, the SGSN sends the above parameters for each RAB to the GANC. +4. The GANC sends the GA-RRC ACTIVATE CHANNEL message to the MS to request activation of the Packet Transport Channel(s). The message includes the CN Domain ID, RAB ID, a TEID that the GANC assigns to the MS for downlink data transfer, the GANC PTC IP Address (i.e., the destination address for PTC GA-RRC PDU messages from the MS) and the GANC TEID assigned by the GANC for uplink data transfer, for each of the RABs. +5. The MS acknowledges the activation of the PTC(s). +6. The GANC signals the completion of the RAB establishment to the MS with the GA-RRC ACTIVATE CHANNEL COMPLETE message. On receipt of the message, the PS domain GA-RRC sublayer entity in the MS transitions to the PTC-ACTIVE substate for each PTC and starts the PTC Timer for each PTC. +7. The GANC sends the RAB Assignment Response message to the SGSN to complete the RAB Assignment procedure. The GANC includes the RAB ID, the RAN Transport Layer Address (i.e., the GANC's Iu-PS IP address) and the RAN Iu Transport Association (i.e., the TEID that the GANC assigned to the MS). +8. Additional PS signalling procedures are performed; e.g., to complete the PDP context activation. +9. The MS transfers uplink user data by sending a GA-RRC PDU message to the GANC PTC IP address received in step 4. The message includes the GANC TEID received in step 4, which allows the GANC to relay the GA- + +RRC PDU message payload using the correct GTP-U tunnel on the Iu-PS interface. The GANC relays the message payload to the SGSN in the Iu-PS G-PDU message. + +10. The SGSN transfers downlink user data by sending a Iu-PS G-PDU message to the GANC Iu-PS IP address received in step 7. The message includes the MS TEID received in step 7, which allows the GANC to relay the Iu-PS G-PDU message payload using the correct PTC on the Up interface. The GANC relays the message payload to the MS in the GA-RRC PDU message. + +### 9.16.2.2 PTC Activation when GANC receives Relocation Request + +The following figure depicts the Packet Transport Channel activation procedure when the GANC receives the Relocation Request message from the SGSN. + +![Sequence diagram illustrating the PTC activation procedure based on a Relocation Request. The diagram shows interactions between MS, GANC, and SGSN. The MS starts in GA-RC-REGISTERED state. The procedure involves: 1. Signalling procedures to prepare for PS handover; 2. Relocation Request from SGSN to GANC; 3. GA-RRC RELOCATION REQUEST from GANC to MS; 4. GA-RRC RELOCATION REQUEST ACK from MS to GANC; 5. Relocation Request Ack from GANC to SGSN; 6. Signalling procedures to complete PS handover; 7. GA-RRC PDU from MS to GANC and G-PDU from GANC to SGSN; 8. GA-RRC PDU from GANC to MS and G-PDU from SGSN to GANC. After step 4, the MS transitions to GA-RC-CONNECTED PTC-ACTIVE state. Vertical ellipsis indicate further steps.](49806c5ac206335a657bc126f17d37e8_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant SGSN + Note left of MS: GA-RC-REGISTERED + Note right of SGSN: 1. Signalling procedures to prepare for PS handover + SGSN->>GANC: 2. Relocation Request + GANC->>MS: 3. GA-RRC RELOCATION REQUEST + MS->>GANC: 4. GA-RRC RELOCATION REQUEST ACK + Note left of MS: GA-RC-CONNECTED +PTC-ACTIVE + GANC->>SGSN: 5. Relocation Request Ack + Note right of SGSN: 6. Signalling procedures to complete PS handover + MS->>GANC: 7. GA-RRC PDU + GANC->>SGSN: 7. G-PDU + GANC->>MS: 8. GA-RRC PDU + SGSN->>GANC: 8. G-PDU + Note left of MS: ... + +``` + +Sequence diagram illustrating the PTC activation procedure based on a Relocation Request. The diagram shows interactions between MS, GANC, and SGSN. The MS starts in GA-RC-REGISTERED state. The procedure involves: 1. Signalling procedures to prepare for PS handover; 2. Relocation Request from SGSN to GANC; 3. GA-RRC RELOCATION REQUEST from GANC to MS; 4. GA-RRC RELOCATION REQUEST ACK from MS to GANC; 5. Relocation Request Ack from GANC to SGSN; 6. Signalling procedures to complete PS handover; 7. GA-RRC PDU from MS to GANC and G-PDU from GANC to SGSN; 8. GA-RRC PDU from GANC to MS and G-PDU from SGSN to GANC. After step 4, the MS transitions to GA-RC-CONNECTED PTC-ACTIVE state. Vertical ellipsis indicate further steps. + +**Figure 59a: PTC activation based on Relocation Request** + +1. The MS has successfully registered with the GANC. The MS, GANC and SGSN perform signalling procedures related to PS handover, as described in sub-clause 9.23. +2. The SGSN sends the *Relocation Request* message to the GANC and includes the RAB ID, the CN Transport Layer Address (IP address) and the CN Iu Transport Association (GTP-U Tunnel Endpoint Identifier, TEID) for user data. Note that the SGSN may request the relocation of multiple RABs via a single *Relocation Request* message; in this case, the SGSN sends the above parameters for each RAB to the GANC. +3. The GANC sends the GA-RRC RELOCATION REQUEST message to the MS to request activation of the Packet Transport Channel(s) for PS handover purposes. The message includes the RAB ID, a TEID that the GANC assigns to the MS for downlink data transfer, the GANC PTC IP Address (i.e., the destination address for PTC GA-RRC PDU messages from the MS) and the GANC TEID assigned by the GANC for uplink data transfer, for each of the RABs. +4. The MS acknowledges the activation of the PTC(s) in the GA-RRC RELOCATION REQUEST ACK message. The PS domain GA-RRC sublayer entity in the MS transitions to the GA-RC-CONNECTED state and the PTC-ACTIVE substate for each PTC and starts the PTC Timer for each PTC. +5. The GANC sends the *Relocation Request Ack* message to the SGSN to complete the handover preparation procedure. The GANC includes the RAB ID, the RAN Transport Layer Address (i.e., the GANC's Iu-PS IP address) and the RAN Iu Transport Association (i.e., the TEID that the GANC assigned to the MS) for each RAB. +6. PS handover is performed, as described in sub-clause 9.23. + +7. The MS transfers uplink user data by sending a GA-RRC PDU message to the GANC PTC IP address received in step 3. The message includes the GANC TEID received in step 3, which allows the GANC to relay the GA-RRC PDU message payload using the correct GTP-U tunnel on the Iu-PS interface. The GANC relays the message payload to the SGSN in the Iu-PS G-PDU message. +8. The SGSN transfers downlink user data by sending a Iu-PS G-PDU message to the GANC Iu-PS IP address received in step 5. The message includes the MS TEID received in step 5, which allows the GANC to relay the Iu-PS G-PDU message payload using the correct PTC on the Up interface. The GANC relays the message payload to the MS in the GA-RRC PDU message. + +### 9.16.3 PTC Data transfer + +The following figure illustrates the transfer of GPRS user data packets via the GAN Packet Transport Channel. + +![Sequence diagram of PTC Data Transfer between MS, GANC, and SGSN.](7f16ae750ce9a533b0bd301dd986355e_img.jpg) + +The diagram illustrates the following sequence between MS, GANC, and SGSN: + +- 1. PTC Activation:** A horizontal box spanning MS, GANC, and SGSN lifelines. +- MS State:** A box on the MS lifeline labeled "GA-RRC-CONNECTED PTC-ACTIVE". +- Uplink Transfer:** + - Message "2. GA-RRC PDU" from MS to GANC. + - Message "2. G-PDU" from GANC to SGSN. + - A box on the MS lifeline labeled "Restart PTC Timer". +- Downlink Transfer:** + - Message "3. G-PDU" from SGSN to GANC. + - Message "3. GA-RRC PDU" from GANC to MS. + - A box on the MS lifeline labeled "Restart PTC Timer". +- Continuation:** Three vertical dots on the MS lifeline. + +Sequence diagram of PTC Data Transfer between MS, GANC, and SGSN. + +**Figure 60: PTC Data Transfer** + +1. If required, the GA-RRC PTC is activated as specified in clause 9.16.2. Upon the GA-RRC PTC activation, the PS domain GA-RRC sublayer entity in the MS enters the PTC-ACTIVE substate and starts the PTC Timer. +2. The MS transfers uplink user data by sending a GA-RRC PDU message to the GANC and restarts the PTC Timer. The GANC relays the message payload to the SGSN in the Iu-PS G-PDU message. +3. The SGSN transfers downlink user data by sending a Iu-PS G-PDU message to the GANC. The GANC relays the message payload to the MS in the GA-RRC PDU message. On receipt of the message, the PS domain GA-RRC sublayer entity in the MS restarts the PTC Timer. + +### 9.16.4 MS initiated PTC De-activation + +The following figure depicts the scenario when the MS initiates the de-activation of a Packet Transport Channel after the PTC Timer for that PTC expires. + +![Sequence diagram for MS initiated PTC de-activation. The diagram shows three lifelines: MS, GANC, and SGSN. The MS starts in GA-RRc-CONNECTED PTC-ACTIVE state. 1. PTC Timer expires. 2. MS sends GA-RRc DEACTIVATE CHANNEL REQUEST to GANC. 3. GANC sends RAB Release Request to SGSN. 4. SGSN sends RAB Assignment Request to GANC. 5. GANC sends GA-RRc DEACTIVATE CHANNEL to MS. 6. MS sends GA-RRc DEACTIVATE CHANNEL COMPLETE to GANC and transitions to GA-RRc-CONNECTED PTC-INACTIVE state. 7. GANC sends RAB Assignment Response to SGSN.](a963ca41bde1669b18a4b783616f228b_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant SGSN + Note left of MS: GA-RRc-CONNECTED PTC-ACTIVE + Note left of MS: 1. PTC Timer expires + MS->>GANC: 2. GA-RRc DEACTIVATE CHANNEL REQUEST + GANC->>SGSN: 3. RAB Release Request + SGSN->>GANC: 4. RAB Assignment Request + GANC->>MS: 5. GA-RRc DEACTIVATE CHANNEL + MS->>GANC: 6. GA-RRc DEACTIVATE CHANNEL COMPLETE + Note left of MS: GA-RRc-CONNECTED PTC-INACTIVE + GANC->>SGSN: 7. RAB Assignment Response + +``` + +Sequence diagram for MS initiated PTC de-activation. The diagram shows three lifelines: MS, GANC, and SGSN. The MS starts in GA-RRc-CONNECTED PTC-ACTIVE state. 1. PTC Timer expires. 2. MS sends GA-RRc DEACTIVATE CHANNEL REQUEST to GANC. 3. GANC sends RAB Release Request to SGSN. 4. SGSN sends RAB Assignment Request to GANC. 5. GANC sends GA-RRc DEACTIVATE CHANNEL to MS. 6. MS sends GA-RRc DEACTIVATE CHANNEL COMPLETE to GANC and transitions to GA-RRc-CONNECTED PTC-INACTIVE state. 7. GANC sends RAB Assignment Response to SGSN. + +**Figure 61: MS initiated PTC de-activation** + +The PS domain GA-RRc sublayer entity in the MS is in the GA-RRc-CONNECTED state and the PTC-ACTIVE substate. + +1. The PTC Timer associated with one of the active PTCs expires. +2. The MS sends the GA-RRc DEACTIVATE CHANNEL REQUEST message to the GANC, including the CN Domain ID, the RAB ID to identify the PTC and indicating the normal release as a cause for deactivation. +3. The GANC sends a RAB Release Request message to the SGSN to request the release of the associated RAB. Note that the GANC may also initiate Iu Release in this case, based on local policy settings. +4. The SGSN responds with the RAB Assignment Request indicating release. +5. The GANC sends the GA-RRc DEACTIVATE CHANNEL message to the MS, including the CN Domain ID and the RAB ID. +6. The MS de-activates the PTC, sends the GA-RRc DEACTIVATE CHANNEL COMPLETE message to the GANC and the PS domain GA-RRc sublayer entity in the MS transitions to the PTC-INACTIVE substate for this PTC. +7. The GANC sends the RAB Assignment Response message to notify the SGSN that the RAB Release procedure is complete. + +### 9.16.5 MS initiated PTC Re-activation + +The following figure depicts the scenario when the MS initiates re-activation of the Packet Transport Channel while the PS domain GA-RRc sublayer entity in the MS is in the GA-RRc-CONNECTED and the MS is in the PMM-CONNECTED state; e.g., a PS signalling connection and active PDP context exists between the MS and CN but the PTC was previously de-activated by the MS due to PTC Timer expiry. + +![Sequence diagram for MS initiated PTC re-activation. The diagram shows three lifelines: MS, GANC, and SGSN. The MS starts in GA-RRc-CONNECTED PTC-INACTIVE state. 1. MS sends GA-RRc UL DIRECT TRANSFER (Service Request=Data) to GANC. 2. GANC sends Direct Transfer (Service Request=Data) to SGSN. 3. Security Mode Control procedure occurs between GANC and SGSN. 4. SGSN sends RAB Direct Transfer (Service Accept) to GANC. 5. GANC sends GA-RRc DL DIRECT TRANSFER (Service Accept) to MS. 6. Packet Transport Channel (PTC) activation procedure occurs between GANC and SGSN. After step 6, the MS is in GA-RRc-CONNECTED PTC-ACTIVE state. 7. MS sends GA-RRc PDU to GANC, which is relayed as G-PDU to SGSN.](de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant SGSN + Note left of MS: GA-RRc-CONNECTED PTC-INACTIVE + MS->>GANC: 1. GA-RRc UL DIRECT TRANSFER (Service Request=Data) + GANC->>SGSN: 2. Direct Transfer (Service Request=Data) + Note right of SGSN: 3. Security Mode Control + SGSN->>GANC: 4. RAB Direct Transfer (Service Accept) + GANC->>MS: 5. GA-RRc DL DIRECT TRANSFER (Service Accept) + Note right of SGSN: 6. Packet Transport Channel (PTC) activation + Note left of MS: GA-RRc-CONNECTED PTC-ACTIVE + MS->>GANC: 7. GA-RRc PDU + GANC->>SGSN: 7. G-PDU + +``` + +Sequence diagram for MS initiated PTC re-activation. The diagram shows three lifelines: MS, GANC, and SGSN. The MS starts in GA-RRc-CONNECTED PTC-INACTIVE state. 1. MS sends GA-RRc UL DIRECT TRANSFER (Service Request=Data) to GANC. 2. GANC sends Direct Transfer (Service Request=Data) to SGSN. 3. Security Mode Control procedure occurs between GANC and SGSN. 4. SGSN sends RAB Direct Transfer (Service Accept) to GANC. 5. GANC sends GA-RRc DL DIRECT TRANSFER (Service Accept) to MS. 6. Packet Transport Channel (PTC) activation procedure occurs between GANC and SGSN. After step 6, the MS is in GA-RRc-CONNECTED PTC-ACTIVE state. 7. MS sends GA-RRc PDU to GANC, which is relayed as G-PDU to SGSN. + +**Figure 62: MS initiated PTC re-activation** + +The PS domain GA-RRc sublayer entity in the MS is in the GA-RRc-CONNECTED state and the PTC-INACTIVE substate. The MS is in the PMM-CONNECTED state (i.e., a PS signalling connection and an active PDP context exists). + +1. The MS has a PDU to send. The MS sends the *Service Request* message (with Service type value “Data”) to the GANC in the GA-RRc UL DIRECT TRANSFER message. +2. The GANC forwards the Service Request over the existing signalling connection to the SGSN using the RANAP *Direct Transfer* message. +3. The SGSN normally initiates the Security Mode Control procedure described in clause 9.8. +4. The SGSN responds with a Service Accept message. +5. The GANC forwards the message to the MS. +6. The MS, GANC and SGSN perform the RAB assignment and the PTC activation as described in steps 3-7 in clause 9.16.2.1. +7. The MS transfers the uplink user data by sending a GA-RRc PDU message to the GANC and starts the PTC Timer. The GANC relays the message to the SGSN in the Iu-PS G-PDU message. Additional data transfer may take place. + +## 9.16.6 Network initiated PTC De-activation + +The following figure depicts the scenario when the network initiates de-activation of one or more Packet Transport Channel(s). + +![Sequence diagram for Network initiated PTC de-activation. The diagram shows three entities: MS, GANC, and SGSN. The MS starts in GA-RRC-CONNECTED PTC-ACTIVE state. The GANC sends a RAB Release Request to the SGSN. The SGSN responds with a RAB Assignment Request to the GANC. The GANC then sends a GA-RRC DEACTIVATE CHANNEL message to the MS. The MS responds with a GA-RRC DEACTIVATE CHANNEL COMPLETE message. Finally, the GANC sends a RAB Assignment Response to the SGSN, and the MS transitions to GA-RRC-CONNECTED PTC-INACTIVE state.](e16bfa31d748f4d99ec4ae3d16656926_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant SGSN + Note left of MS: GA-RRC-CONNECTED PTC-ACTIVE + GANC->>SGSN: 1. RAB Release Request + SGSN-->>GANC: 2. RAB Assignment Request + GANC->>MS: 3. GA-RRC DEACTIVATE CHANNEL + MS-->>GANC: 4. GA-RRC DEACTIVATE CHANNEL COMPLETE + Note left of MS: GA-RRC-CONNECTED PTC-INACTIVE + GANC->>SGSN: 5. RAB Assignment Response + +``` + +Sequence diagram for Network initiated PTC de-activation. The diagram shows three entities: MS, GANC, and SGSN. The MS starts in GA-RRC-CONNECTED PTC-ACTIVE state. The GANC sends a RAB Release Request to the SGSN. The SGSN responds with a RAB Assignment Request to the GANC. The GANC then sends a GA-RRC DEACTIVATE CHANNEL message to the MS. The MS responds with a GA-RRC DEACTIVATE CHANNEL COMPLETE message. Finally, the GANC sends a RAB Assignment Response to the SGSN, and the MS transitions to GA-RRC-CONNECTED PTC-INACTIVE state. + +**Figure 63: Network initiated PTC de-activation** + +The PS domain GA-RRC sublayer entity in the MS is in the GA-RRC-CONNECTED state and the PTC-ACTIVE substate for one or more PTCs. + +1. Optionally, the GANC may initiate the PTC de-activation procedure; e.g., as a result of an error handling procedure. If so, the GANC sends the RAB Release Request message to the SGSN. +2. The SGSN sends a RAB Assignment Request to request the release of the associated RAB(s). The release request may include one or more RABs. +3. The GANC requests deactivation of the associated GA-RRC PTC(s) by sending the GA-RRC DEACTIVATE CHANNEL message to the MS, including the CN Domain ID and RAB ID(s). +4. The MS de-activates the PTC(s), sends the GA-RRC DEACTIVATE CHANNEL COMPLETE message to the GANC and transitions to the PTC-INACTIVE substate for the PTC(s). +5. The GANC sends the RAB Assignment Response message to notify the SGSN that the RAB Release procedure is complete. + +## 9.16.7 Network initiated PTC Re-activation + +### 9.16.7.1 Active PDP Context, PS Signalling Connection Exists + +The following figure depicts the scenario when the network initiates re-activation of the GA-RRC PTC while the PS domain GA-RRC sublayer entity in the MS is in the GA-RRC-CONNECTED and the MS is in the PMM-CONNECTED state; e.g., a PS signalling connection and active PDP context exists between the MS and CN but the associated PTC was previously de-activated. + +![Sequence diagram for Network initiated PTC re-activation, scenario 1. The diagram shows three entities: MS, GANC, and SGSN. The MS starts in GA-RRC-CONNECTED PTC-INACTIVE state. The GANC sends a Security Mode Control message to the MS. The MS responds with a Packet Transport Channel (PTC) activation message. The GANC then sends a GA-RRC PDU to the MS, and the MS transitions to GA-RRC-CONNECTED PTC-ACTIVE state. The SGSN sends a G-PDU to the GANC.](ffefa4f6eab4ce450aa5ecd3d3fd70bb_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant SGSN + Note left of MS: GA-RRC-CONNECTED PTC-INACTIVE + GANC->>MS: 1. Security Mode Control + MS-->>GANC: 2. Packet Transport Channel (PTC) activation + Note left of MS: GA-RRC-CONNECTED PTC-ACTIVE + GANC->>MS: 3. GA-RRC PDU + SGSN->>GANC: 3. G-PDU + +``` + +Sequence diagram for Network initiated PTC re-activation, scenario 1. The diagram shows three entities: MS, GANC, and SGSN. The MS starts in GA-RRC-CONNECTED PTC-INACTIVE state. The GANC sends a Security Mode Control message to the MS. The MS responds with a Packet Transport Channel (PTC) activation message. The GANC then sends a GA-RRC PDU to the MS, and the MS transitions to GA-RRC-CONNECTED PTC-ACTIVE state. The SGSN sends a G-PDU to the GANC. + +**Figure 64: Network initiated PTC re-activation, scenario 1** + +The PS domain GA-RRC sublayer entity in the MS is in the GA-RRC-CONNECTED state and the PTC-INACTIVE substate. The MS is in the PMM-CONNECTED state (i.e., a PS signalling connection and an active PDP context exists). + +1. The SGSN has a PDU to send to the MS. The SGSN may optionally initiate the Security Mode Control procedure described in clause 9.8. +2. The MS, GANC and SGSN perform the RAB assignment and PTC activation as described in steps 3-7 in clause 9.16.2.1. +3. The SGSN sends the downlink PDU. Additional data transfer may take place. + +### 9.16.7.2 Active PDP Context, No PS Signalling Connection + +The following figure depicts the scenario when the network initiates re-activation of the Packet Transport Channel while the MS is in the PMM-CONNECTED state; e.g., no PS signalling connection exists but an active PDP context exists between the MS and CN. + +![Sequence diagram for Network initiated PTC re-activation, scenario 2. The diagram shows interactions between MS, GANC, and SGSN. The MS starts in PMM-CONNECTED state. The sequence of messages is: 1. Paging (SGSN to GANC), 2. GA-RRC PAGING REQUEST (GANC to MS), 3. GA-RRC INITIAL DIRECT TRANSFER (Service Request=Paging Response) (MS to GANC), 4. Initial UE Message (Service Request=Paging Response) (GANC to SGSN), 5. Authentication (SGSN to MS), 6. Security Mode Control (SGSN to MS), 7. Packet Transport Channel (PTC) activation (SGSN to MS), 8. PS user data transfer using PTC (SGSN to MS). The MS transitions to GA-RRC-CONNECTED state after step 3.](ca5555bb37f54857199d243feff8479e_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant SGSN + Note left of MS: PMM-CONNECTED + SGSN->>GANC: 1. Paging + GANC->>MS: 2. GA-RRC PAGING REQUEST + MS->>GANC: 3. GA-RRC INITIAL DIRECT TRANSFER (Service Request=Paging Response) + Note left of MS: GA-RRC-CONNECTED + GANC->>SGSN: 4. Initial UE Message (Service Request=Paging Response) + SGSN->>MS: 5. Authentication + SGSN->>MS: 6. Security Mode Control + SGSN->>MS: 7. Packet Transport Channel (PTC) activation + SGSN->>MS: 8. PS user data transfer using PTC + +``` + +Sequence diagram for Network initiated PTC re-activation, scenario 2. The diagram shows interactions between MS, GANC, and SGSN. The MS starts in PMM-CONNECTED state. The sequence of messages is: 1. Paging (SGSN to GANC), 2. GA-RRC PAGING REQUEST (GANC to MS), 3. GA-RRC INITIAL DIRECT TRANSFER (Service Request=Paging Response) (MS to GANC), 4. Initial UE Message (Service Request=Paging Response) (GANC to SGSN), 5. Authentication (SGSN to MS), 6. Security Mode Control (SGSN to MS), 7. Packet Transport Channel (PTC) activation (SGSN to MS), 8. PS user data transfer using PTC (SGSN to MS). The MS transitions to GA-RRC-CONNECTED state after step 3. + +**Figure 65: Network initiated PTC re-activation, scenario 2** + +Initially, the SGSN receives downlink user data to transfer to the MS and the Iu connection is not established. The MS is in the PMM-CONNECTED state. + +1. The SGSN sends the RANAP *Paging* message to the MS via the GANC to locate the user. The paging request indicates paging for PS Domain signalling. +2. The GANC forwards the paging information to the MS in the GA-RRC PAGING REQUEST message. +3. The MS responds with a GA-RRC INITIAL DIRECT TRANSFER message. The PS domain GA-RRC sublayer entity in the MS transitions to the GA-RRC-CONNECTED state. +4. The GANC establishes an SCCP connection to the SGSN and forwards the *Service Request* message (with Service type value "Paging response") to the SGSN using the RANAP *Initial UE Message*. Subsequent NAS messages between the MS and core network will be sent between GANC and SGSN using the RANAP *Direct Transfer* message. +5. The SGSN may optionally authenticate the MS using standard UTRAN authentication procedures. +6. The SGSN normally initiates the Security Mode Control procedure described in clause 9.8. +7. The MS, GANC and SGSN perform the RAB assignment and the GA-RRC PTC activation as described in steps 3-7 in clause 9.16.2.1. + +8. The MS and SGSN exchange user data transfer via the established PTC as defined in clause 9.16.3. + +## 9.16.8 Implicit PTC De-activation due to MS De-registration + +As part of the GAN de-registration procedure, the GANC needs to release all resources allocated to the MS. GAN de-registration may be initiated either explicitly by the MS or implicitly by the GANC if the loss of the signalling connection is detected (as described in clause 9.4.2). + +![Sequence diagram illustrating the Implicit PTC De-activation due to MS De-registration. The diagram shows three entities: MS, GANC, and CN. The sequence of messages is: 1. GA-RC DEREGISTER (dashed arrow from GANC to MS); 2. Release CS domain resources (dashed arrow from GANC to CN); 3. Iu Release Request (solid arrow from GANC to CN); 4. Iu Release Command (solid arrow from CN to GANC); 5. Deactivate all MS PTCs (internal message in GANC); 6. Iu Release Complete (solid arrow from GANC to CN).](5a01395925fc88802da68fb5ac0f31ff_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant CN + Note right of GANC: 5. Deactivate all MS PTCs + GANC-->>MS: 1. GA-RC DEREGISTER + GANC-->>CN: 2. Release CS domain resources + GANC->>CN: 3. Iu Release Request + CN->>GANC: 4. Iu Release Command + GANC->>CN: 6. Iu Release Complete + +``` + +Sequence diagram illustrating the Implicit PTC De-activation due to MS De-registration. The diagram shows three entities: MS, GANC, and CN. The sequence of messages is: 1. GA-RC DEREGISTER (dashed arrow from GANC to MS); 2. Release CS domain resources (dashed arrow from GANC to CN); 3. Iu Release Request (solid arrow from GANC to CN); 4. Iu Release Command (solid arrow from CN to GANC); 5. Deactivate all MS PTCs (internal message in GANC); 6. Iu Release Complete (solid arrow from GANC to CN). + +**Figure 66: Implicit PTC deactivation** + +Initially, the PS domain GA-RRC sublayer entity in the MS is in the PTC-ACTIVE substate for one or more GA-RRC PTCs associated with the MS. + +1. The GAN de-registration procedure is initiated for the MS either by the MS or GANC. +2. Optionally, any outstanding resources associated with the CS Domain are released. +3. Optionally, if there are any outstanding resources associated with the PS Domain, the GANC initiates the Iu release procedure to the SGSN to release the corresponding RABs. +4. The SGSN responds with Iu Release Command. +5. Upon receiving the Iu Release Command, the GANC implicitly de-activates (i.e., locally) all associated PTCs and... +6. ...responds to the SGSN with an Iu Release Complete message. + +## 9.16.9 PTC Modification + +The GANC may initiate the packet transport channel (PTC) modification procedure when it determines that one or more active PTCs require modification; e.g., based on information received from the SGSN in the RAB Assignment Request message or based on local GANC logic. For example, the GANC may initiate this procedure if it detects "packet loss" and handover to GERAN/UTRAN is not possible or desired. CS channel modification and PTC modification use the same messages and the same basic message flows, but differ in the content of the messages. + +The GANC may modify the following PTC parameters: + +- RAB Configuration +- GANC TEID +- MS TEID +- GANC UDP Port +- GANC IP Address + +![Sequence diagram for PTC Modification between MS and GANC. The diagram shows three steps: 1. One or more PTCs are active (indicated by a box labeled 'GA-RRc-CONNECTED PTC-ACTIVE'), 2. GA-RRc MODIFY CHANNEL (arrow from GANC to MS), and 3. GA-RRc MODIFY CHANNEL ACKNOWLEDGE (arrow from MS to GANC).](6a993bfdf2e00cfad01c4d2188a75d86_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note right of GANC: 1. One or more PTCs are active + Note left of MS: GA-RRc-CONNECTED +PTC-ACTIVE + GANC->>MS: 2. GA-RRc MODIFY CHANNEL + MS->>GANC: 3. GA-RRc MODIFY CHANNEL ACKNOWLEDGE + +``` + +Sequence diagram for PTC Modification between MS and GANC. The diagram shows three steps: 1. One or more PTCs are active (indicated by a box labeled 'GA-RRc-CONNECTED PTC-ACTIVE'), 2. GA-RRc MODIFY CHANNEL (arrow from GANC to MS), and 3. GA-RRc MODIFY CHANNEL ACKNOWLEDGE (arrow from MS to GANC). + +**Figure 66a: PTC Modification** + +1. One or more PTC(s) are activated as described in sub-clause 9.16.2. +2. The GANC sends the GA-RRc MODIFY CHANNEL message to the MS to modify parameters for one or more of the activated PTCs. +3. The MS responds with the GA-RRc MODIFY CHANNEL ACKNOWLEDGE message to the GANC. + +9.17 (void) + +9.18 (void) + +## 9.19 Short Message Service + +GAN provides support for SMS via the CS domain and the PS domain. GAN-attached and GPRS enabled mobile stations will be able to send and receive SMS messages via the CS domain or the PS domain, regardless of the GPRS class (B or C) with the restriction that the class C mobiles can support only SMS via the PS domain. + +### 9.19.1 SMS via the CS domain + +Support for SMS via the CS domain in GAN is based on the same mechanism that is utilized for GSM mobility management and call control. On the MS side, the SMS layers (including the supporting CM sub layer functions) utilize the services of the MM layer to transfer SMS messages per standard circuit switched GSM implementation. The SM-CP protocol is effectively tunnelled between the MS and the CN, using GA-RRc messages from the MS to the GANC, where the GANC relays the SM-CP to RANAP messages for transport over the Iu-cs interface. + +As with GSM mobility management and call control procedures, the secure IPsec tunnel and TCP session are used to provide secure and reliable SMS delivery over the IP network. + +### 9.19.2 SMS via the PS domain + +Support for SMS via the PS domain is based on the same mechanism as the transfer of the GPRS MM/SM signalling messages. The SM-CP protocol is effectively tunnelled between the MS and the CN, using GA-RRc messages from the MS to the GANC, where the GANC relays the SM-CP to RANAP messages for transport over the Iu-ps interface. + +As with GPRS signalling, the secure IPsec tunnel and TCP session is used to provide secure and reliable GPRS SMS delivery over the IP network. + +## 9.20 Supplementary Services + +UMTS has a large number of standardized supplementary services. These supplementary services involve procedures that operate end-to-end between the MS and the MSC. The CM messages used for the supplementary service are relayed between the MS and MSC in the same manner as in the other call control and mobility management scenarios described in this document. + +## 9.21 Emergency Services + +See clause 8.21. + +## 9.22 Location Services + +See clause 8.22. + +## 9.23 PS Handover between GAN Iu mode and GERAN/UTRAN mode + +### 9.23.1 PS Handover from GERAN to GAN + +#### 9.23.1.1 Preparation Phase + +The description of the GERAN to GAN PS handover procedure assumes the following: + +- the MS has one or more active packet flow contexts in the GERAN; +- the MS has successfully registered with a GANC, allowing the MS to obtain GAN system information; +- the GANC has directed the MS to operate in GAN Iu mode; +- the PS handover is intra-SGSN (i.e., assumes that the SGSN is capable of both 2G and 3G operation and interworking); and +- the GERAN provides information on neighbouring cells such that one of the cells in the neighbour list matches the cell associated with the GANC, as provided in the AS-related component of the system information obtained from the GANC. + +![Sequence diagram of GERAN to GAN PS Handover Preparation Phase. The diagram shows four entities: MS, Target GANC, Source BSS, and 2G/3G SGSN. The MS is shown with a 'GAN Registered' status. The sequence of messages is: 1. Decision to perform PS handover (from Source BSS to Target GANC); 2. PS Handover Required (from Source BSS to 2G/3G SGSN); 3. Relocation Request (from 2G/3G SGSN to Target GANC); 4. GA-RRC PTC Activation (from Target GANC to MS); 5. Relocation Request Ack (from Target GANC to 2G/3G SGSN).](5e3888db7cda1becbce099b7304a44fa_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC as Target GANC + participant BSS as Source BSS + participant SGSN as 2G/3G SGSN + + Note left of MS: GAN Registered + Note right of BSS: 1. Decision to perform PS handover + BSS->>SGSN: 2. PS Handover Required + SGSN->>GANC: 3. Relocation Request + Note left of GANC: 4. GA-RRC PTC Activation + GANC->>SGSN: 5. Relocation Request Ack + +``` + +Sequence diagram of GERAN to GAN PS Handover Preparation Phase. The diagram shows four entities: MS, Target GANC, Source BSS, and 2G/3G SGSN. The MS is shown with a 'GAN Registered' status. The sequence of messages is: 1. Decision to perform PS handover (from Source BSS to Target GANC); 2. PS Handover Required (from Source BSS to 2G/3G SGSN); 3. Relocation Request (from 2G/3G SGSN to Target GANC); 4. GA-RRC PTC Activation (from Target GANC to MS); 5. Relocation Request Ack (from Target GANC to 2G/3G SGSN). + +**Figure 67: GERAN to GAN PS Handover Preparation Phase** + +1. The source BSS decides to initiate a PS handover. At this point both uplink and downlink user data is transmitted via the following: TBFs between MS and source BSS, BSSGP PFCs tunnel(s) between the source BSS and 3G/2G SGSN, GTP tunnel(s) between the 3G/2G SGSN and GGSN. +2. The source BSS sends a *PS Handover Required* message (TLLI, Cause, Source Cell Identifier, Target RNC Identifier, Source RNC to Target RNC Transparent Container, Active PFCs List) to the SGSN. +3. The SGSN determines from the Target RNC Identifier that this is a GERAN to UTRAN handover. The SGSN constructs a *Relocation Request* message as described in 3GPP TS 43.129 [44] and sends the message to the target GANC. +4. One or more GAN PTCs are activated between the MS and the GANC as specified in steps 3-4 in sub-clause 9.16.2.2. Upon each GA-RRC PTC activation, the PS domain GA-RRC sublayer entity in the MS enters the PTC-ACTIVE substate and starts the PTC Timer for the PTC. + +- The GANC sends the *Relocation Request Acknowledge* message (Target RNC to Source RNC Transparent Container, RABs setup list, RABs failed to setup list) to the SGSN. Upon sending the *Relocation Request Acknowledge* message the target GANC shall be prepared to receive downlink GTP PDUs from the SGSN for the accepted RABs. + +When the SGSN receives the *Relocation Request Acknowledge* message and it decides to proceed with the handover, the preparation phase is finished and the execution phase will follow. + +### 9.23.1.2 Execution Phase + +![Sequence diagram of GERAN to GAN PS Handover Execution Phase. Lifelines: MS, Target GANC, Source BSS, 2G/3G SGSN, GGSN. The diagram shows the flow of data and signaling during the execution phase of the handover.](d9d09655eb4282168769ac97178db50c_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Target GANC + participant Source BSS + participant 2G/3G SGSN + participant GGSN + + Note right of 2G/3G SGSN: 1. IP packets to source BSC + GGSN-->2G/3G SGSN: + 2G/3G SGSN->Source BSS: + Note right of Source BSS: 2. Send relayed N-PDUs over the allocated RABs + Source BSS-->Target GANC: + Target GANC-->MS: + Note right of 2G/3G SGSN: 3. PS Handover Required Ack + 2G/3G SGSN->Source BSS: + Note right of Source BSS: 4. Forward SRNS Context + Source BSS->Target GANC: + Note right of Target GANC: 5. PS Handover Command + Target GANC->MS: + Note right of MS: 6. GA-RRC RELOCATION COMPLETE + MS->Target GANC: + Note right of Target GANC: 7. Relocation Detect + Target GANC->2G/3G SGSN: + Note right of 2G/3G SGSN: 8. Relocation Complete + 2G/3G SGSN->Target GANC: + Note right of Target GANC: 9. Update PDP Context Procedure + Target GANC->2G/3G SGSN: + Note right of 2G/3G SGSN: 10. PFC Procedure + 2G/3G SGSN->Source BSS: + Note right of Source BSS: 11. Routing Area Update Procedure + Source BSS->2G/3G SGSN: + +``` + +Sequence diagram of GERAN to GAN PS Handover Execution Phase. Lifelines: MS, Target GANC, Source BSS, 2G/3G SGSN, GGSN. The diagram shows the flow of data and signaling during the execution phase of the handover. + +**Figure 68: GERAN to GAN PS Handover Execution Phase** + +- The SGSN continues to receive IP packets from the GGSN (via GTP) and forwards the associated PDU payload to the MS via the source BSS. +- When receiving the *Relocation Request Acknowledge* message the SGSN may, based on QoS, start downlink N-PDU relay and duplication to the target GANC if a Tunnel Endpoint is available as follows: + - For PDP context, which uses LLC ADM, all new downlink N-PDUs received after completion of the PS handover preparation phase are relayed to the target GANC. All such N-PDUs are encapsulated in a GTP-PDU when transmitted to the target GANC. + - If the 3G/2G SGSN forwards downlink packets to the target GANC, the target GANC may start blind transmission of downlink user data towards the MS over the allocated PTC(s). +- The SGSN continues the PS Handover by sending a *PS Handover Required Acknowledge* message (TLLI, List of Set Up PFCs, Target RNC to Source RNC Transparent Container) to the source BSS, as described in 3GPP TS 43.129 [44]. +- The SGSN shall send the *Forward SRNS Context* message (NSAPI, DL GTP-U number, UL GTP-U number) to the target GANC if there is at least one PDP context which requires "delivery order" to be preserved, as described in 3GPP TS 43.129 [44]. + +The target GANC proceed as follows: + +- For RABs not requiring lossless PDCP the target GANC may, according the QoS profile of the PDP context, store the received data until it receives confirmation of MS presence in the target cell. + +- The target GANC disregards PDCP sequence numbers, since lossless relocation is not supported. +5. The source BSS sends the *PS Handover Command* message containing the Handover to UTRAN Command message (as it is specified in 3GPP TS 25.331 [40]) to the MS, as described in 3GPP TS 43.129 [44]. + 6. Immediately after receiving the *PS Handover Command* message, the MS sends GA-RRC RELOCATION COMPLETE message to the GANC. + 7. Immediately upon receiving the GA-RRC RELOCATION COMPLETE message from the MS, the GANC sends the *Relocation Detect* message to the SGSN. + 8. The GANC sends the *Relocation Complete* message to the SGSN, indicating the completion of the PS handover. After the reception of the *Relocation Complete* message the SGSN shall be prepared to receive data from the target GANC. + 9. If the SGSN has established Direct Tunnel, the SGSN sends an *Update PDP Context Request* message (RNC Address, TEID, QoS Negotiated, DTI) to the GGSN concerned. The SGSN provides to the GGSN the GANC address for the User Plane and TEID for downlink data and shall include the DTI to instruct the GGSN to apply Direct Tunnel specific error handling procedure as defined in 3GPP TS 23.060 [19]. The GGSN updates the PDP context fields and returns an *Update PDP Context Response* message (TEID). From now on the GGSN sends new incoming downlink IP packets to the target GANC instead of the SGSN. + 10. The SGSN shall initiate PFC Management procedures towards the source GERAN cell in order to trigger the release of resources in the source cell. + 11. The MS and SGSN perform the Routing Area Update procedure as described in 3GPP TS 43.129 [44]. + +## 9.23.2 PS Handover from UTRAN to GAN + +### 9.23.2.1 Preparation Phase + +The description of the UTRAN to GAN PS handover procedure assumes the following: + +- the Iur interface between the UTRAN RNC and GANC is not supported. Therefore, only the Combined Hard Handover and SRNS Relocation is applicable for GAN – UTRAN PS handover. Consequently, only the “MS Involved” Relocation Type is supported; +- the MS has one or more active PDP Contexts with active RABs in the UTRAN; +- the MS has successfully registered with a GANC, allowing the MS to obtain GAN system information; +- the GANC has directed the MS to operate in GAN Iu mode; and +- the UTRAN provides information on neighbouring cells such that one of the cells in the neighbour list matches the cell associated with the GANC, as provided in the AS-related component of the system information obtained from the GANC. See Annex B.2.1 for more information. + +![Sequence diagram of UTRAN to GAN PS Handover Preparation Phase. Lifelines: MS (with GAN Registered), Target GANC, Source RNC, and SGSN. The sequence starts with a decision in the Source RNC, followed by messages: Relocation Required (Source RNC to SGSN), Relocation Request (SGSN to Target GANC), GA-RRC PTC Activation (between MS and Target GANC), and Relocation Request Ack (Target GANC to SGSN).](69467ece0a576b4c2ec3e0c89ba61527_img.jpg) + +``` + +sequenceDiagram + participant MS + note left of MS: GAN Registered + participant Target GANC + participant Source RNC + participant SGSN + + Note right of Source RNC: 1. Decision to perform Hard Handover & SRNS Relocation + Source RNC->>SGSN: 2. Relocation Required + SGSN->>Target GANC: 3. Relocation Request + Note left of Target GANC: 4. GA-RRC PTC Activation + Target GANC->>SGSN: 5. Relocation Request Ack + +``` + +Sequence diagram of UTRAN to GAN PS Handover Preparation Phase. Lifelines: MS (with GAN Registered), Target GANC, Source RNC, and SGSN. The sequence starts with a decision in the Source RNC, followed by messages: Relocation Required (Source RNC to SGSN), Relocation Request (SGSN to Target GANC), GA-RRC PTC Activation (between MS and Target GANC), and Relocation Request Ack (Target GANC to SGSN). + +**Figure 69: UTRAN to GAN PS Handover Preparation Phase** + +1. Based on measurement results and knowledge of the RAN topology, the source SRNC decides to initiate a combined hard handover and SRNS relocation. +2. The source SRNC sends a *Relocation Required* message (Relocation Type, Cause, Source ID, Target ID, Source RNC To Target RNC Transparent Container) to the SGSN. +3. The SGSN determines the target cell is the GANC, based on the contents of *Relocation Required*. It then sends the *Relocation Request* message (Permanent NAS UE Identity, Cause, CN Domain Indicator, Source RNC To Target RNC Transparent Container, RAB To Be Setup) to the GANC. + +If the IMSI is not present in the Permanent NAS UE Identity IE in the *Relocation Request* message, the GANC shall send the *Relocation Failure* message to the SGSN including Cause value “Relocation Failure In Target CN/RNC Or Target System” and abort the relocation procedure. + +4. One or more GAN PTCs are established between the GANC and MS as specified in steps 3-4 in sub-clause 9.16.2.2. Upon the GA-RRC PTC establishment, the PS domain GA-RRC sublayer entity in the MS enters the PTC-ACTIVE substate and starts the PTC Timer for the PTC. +5. The GANC sends the *Relocation Request Acknowledge* message (Target RNC To Source RNC Transparent Container, RABs Setup, RABs Failed To Setup) to the SGSN. + +## 9.23.2.2 Execution Phase + +![Sequence diagram of UTRAN to GAN PS Handover Execution Phase showing interactions between MS, Target GANC, Source RNC, and SGSN.](737abf1e655afd3324b6b3987945d913_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Target GANC + participant Source RNC + participant SGSN + + SGSN->>Source RNC: 1. Relocation Command + rect rgb(255, 255, 255) + Note over Target GANC, Source RNC: 2. Forwarding of GTP PDUs + end + Source RNC->>MS: 2. Uu: Physical Channel Reconfiguration + Source RNC->>SGSN: 2. Forward SRNS Context + SGSN->>Target GANC: 2. Forward SRNS Context + MS->>Target GANC: 3. GA-RRC RELOCATION COMPLETE + Target GANC->>SGSN: 4. Relocation Detect + Target GANC->>SGSN: 5. Relocation Complete + MS<->Target GANC: 6. PS user data transfer using PTC + Target GANC<->SGSN: 6. PS user data transfer using PTC + SGSN->>Source RNC: 7. Iu Release Command + Source RNC->>SGSN: 7. Iu Release Complete + rect rgb(255, 255, 255) + Note over MS, SGSN: 8. Routing Area Update Procedure + end + +``` + +Sequence diagram of UTRAN to GAN PS Handover Execution Phase showing interactions between MS, Target GANC, Source RNC, and SGSN. + +**Figure 70: UTRAN to GAN PS Handover Execution Phase** + +1. Upon receiving the positive acknowledgement from the GANC to serve the MS, the SGSN initiates the Execution Phase by sending the *Relocation Command* to the source SRNC. +2. a) The RNC may start forwarding GTP PDUs to the GANC while still transmitting them in the downlink to the MS. This forwarding is routed via the Iu-PS interface. The GANC may buffer, start a blind transmission of downlink user data towards the MS over the allocated PTC(s), or discard these forwarded GTP PDUs, depending on the QoS profile, network conditions, and whether it supports data forwarding. + b) The RNC instructs the MS to initiate the switch to GAN via the *Physical Channel Reconfiguration* message. + c) The RNC sends the *Forward SRNS Context* message to the GANC via the SGSN. In this message, the next-expected sequence number of uplink and downlink GTP-U packets are indicated to the GANC by the RNC. +3. Immediately after receiving the *Physical Channel Reconfiguration* message, the MS sends GA-RRC RELOCATION COMPLETE message to the GANC. Upon receiving this message and the *Forward SRNS Context* message, the GANC becomes the Serving RNC. +4. Immediately upon receiving the GA-RRC HANDOVER COMPLETE message from the MS, the GANC sends the *Relocation Detect* message to the SGSN. +5. The GANC sends the Relocation Complete message to the SGSN. +6. The MS, GANC and CN exchange user data via the established PTC. +7. The SGSN releases the Iu-PS connection with the old RNC. +8. If the Routing Area of the GANC cell (as indicated by the GANC to the MS in GAN registration) is different from that under the old RNC, then the MS performs the Routing Area Update procedure. + +### 9.23.3 PS Handover from GAN to GERAN + +The description of the GAN to GERAN PS handover procedure assumes the following: + +- the PS handover is intra-SGSN (i.e., assumes that the SGSN is capable of both 2G and 3G operation and interworking). + +#### 9.23.3.1 Preparation Phase + +![Sequence diagram of the GAN to GERAN PS Handover Preparation Phase. The diagram shows four lifelines: MS, Source GANC, Target BSS, and 2G/3G SGSN. The sequence of messages is: 1. Active GA-RRC PTC(s), RAB(s) and PDP Context(s) from Source GANC to 2G/3G SGSN; 2. GA-RRC UPLINK QUALITY INDICATION from Source GANC to MS (dashed line); 3. GA-RRC RELOCATION INFORMATION from MS to Source GANC; 4. Relocation Required from Source GANC to 2G/3G SGSN; 5. PS Handover Request from 2G/3G SGSN to Target BSS; 6. Reservation of resources in target BSS (self-message on Target BSS); 7. PS Handover Request Ack from Target BSS to 2G/3G SGSN.](98d9a07b2cfa04ebea4e5a4b556d184a_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Source GANC + participant Target BSS + participant 2G/3G SGSN + + Note left of MS: 1. Active GA-RRC PTC(s), RAB(s) and PDP Context(s) + Source GANC->>2G/3G SGSN: 1. Active GA-RRC PTC(s), RAB(s) and PDP Context(s) + Note left of MS: 2. GA-RRC UPLINK QUALITY INDICATION + Source GANC-->>MS: 2. GA-RRC UPLINK QUALITY INDICATION + Note left of MS: 3. GA-RRC RELOCATION INFORMATION + MS->>Source GANC: 3. GA-RRC RELOCATION INFORMATION + Note left of Source GANC: 4. Relocation Required + Source GANC->>2G/3G SGSN: 4. Relocation Required + Note left of 2G/3G SGSN: 5. PS Handover Request + 2G/3G SGSN->>Target BSS: 5. PS Handover Request + Note left of Target BSS: 6. Reservation of resources in target BSS + Target BSS->>Target BSS: 6. Reservation of resources in target BSS + Note left of Target BSS: 7. PS Handover Request Ack + Target BSS->>2G/3G SGSN: 7. PS Handover Request Ack + +``` + +Sequence diagram of the GAN to GERAN PS Handover Preparation Phase. The diagram shows four lifelines: MS, Source GANC, Target BSS, and 2G/3G SGSN. The sequence of messages is: 1. Active GA-RRC PTC(s), RAB(s) and PDP Context(s) from Source GANC to 2G/3G SGSN; 2. GA-RRC UPLINK QUALITY INDICATION from Source GANC to MS (dashed line); 3. GA-RRC RELOCATION INFORMATION from MS to Source GANC; 4. Relocation Required from Source GANC to 2G/3G SGSN; 5. PS Handover Request from 2G/3G SGSN to Target BSS; 6. Reservation of resources in target BSS (self-message on Target BSS); 7. PS Handover Request Ack from Target BSS to 2G/3G SGSN. + +**Figure 71: GAN to GERAN PS Handover Preparation Phase** + +- The MS is in active packet flow exchange with active PDP Context(s) and PTC(s) in the GAN. +- The GANC may send a GA-RRC UPLINK QUALITY INDICATION if there is a problem with the uplink quality for the ongoing session. Uplink Quality Indication is information sent by the GANC to the MS indicating the crossing of a uplink quality threshold in the uplink direction. Whenever the MS receives an indication of bad quality, it should start the PS handover procedure, as described in the next step. Alternatively, MS can use its local measurements to decide to initiate the PS handover procedure. +- The MS decides to initiate a PS handover from GAN to GERAN by sending GA-RRC RELOCATION INFORMATION message to the GANC. The GA-RRC RELOCATION INFORMATION message indicates a list of target GERAN A/Gb mode cells, identified by CGI, in order of preference for PS handover, and includes the received signal strength for each identified GERAN A/Gb mode cell. +- The GANC selects a target GERAN cell based on the contents of the GA-RRC RELOCATION INFORMATION message. It sends the *Relocation Required* message (Relocation Type, Cause, Source ID, Target ID, Source BSS To Target BSS Transparent Container) to the SGSN. The GANC sets Relocation Type to "UE Involved in relocation of SRNS". Target ID contains the identity of the target GERAN cell. +- 5-7. The SGSN and Target BSS complete the UTRAN to GERAN PS handover preparation as described in 3GPP TS 43.129 [44]. + +### 9.23.3.2 Execution Phase + +![Sequence diagram of GAN to GERAN PS Handover Execution Phase](a66383962afcd0f0458f0d45c101fabf_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Target BSS + participant Source GANC + participant 2G/3G SGSN + participant GGSN + + Note right of 2G/3G SGSN: 1. Relocation Command + 2G/3G SGSN->>Source GANC: 1. Relocation Command + Note over MS, 2G/3G SGSN: 2. Forwarding of data + Note right of Source GANC: 2. GA-RRC Relocation Command + Source GANC->>MS: 2. GA-RRC Relocation Command + Note right of Source GANC: 2. Forward SRNS Context + Source GANC->>2G/3G SGSN: 2. Forward SRNS Context + Note over MS, Target BSS: 3. GERAN A/Gb access procedures + Note over MS, Target BSS, 2G/3G SGSN, GGSN: 4. Completion of GERAN PS handover procedures + Note right of 2G/3G SGSN: 5. Iu Release Command + 2G/3G SGSN->>Source GANC: 5. Iu Release Command + Note right of Source GANC: 5. Iu Release Complete + Source GANC->>2G/3G SGSN: 5. Iu Release Complete + Note over MS, Target BSS, 2G/3G SGSN, GGSN: 6. Routing Area Update Procedure + +``` + +Sequence diagram of GAN to GERAN PS Handover Execution Phase + +**Figure 72: GAN to GERAN PS Handover Execution Phase** + +- The SGSN begins the Execution Phase by issuing a *Relocation Command* message (Target BSS to Source BSS Transparent Container (PS Handover Command with RN part and CN part), RABs to be Released List, RABs Subject to Data Forwarding List) to the GANC. +- The GANC may begin data forwarding for the RABs subject to data forwarding according to the procedure defined in 3GPP TS 43.129 [44]. + - The GANC sends GA-RRC RELOCATION COMMAND to the MS. This message contains the information from the Relocation Command received in step 1. + - The GANC sends the *Forward SRNS Context* message to the SGSN. +- The MS executes the GERAN A/Gb PS handover access procedures as described in 3GPP TS 43.129 [44]. +- After successfully accessing the GERAN cell, the MS, target BSS, SGSN and GGSN complete the GERAN PS handover procedures as described in 3GPP TS 43.129 [44]. +- The SGSN releases the Iu-PS connection by sending the *Iu Release Command* message to the GANC, to which GANC responds with the *Iu Release Complete* message. +- If the Routing Area of the UTRAN cell is different from that of the GAN cell, then the MS performs the Routing Area Update procedure. + +## 9.23.4 PS handover from GAN to UTRAN + +### 9.23.4.1 Preparation Phase + +![Sequence diagram of GAN to UTRAN PS Handover Preparation Phase](64bec4cd45e47e1976245711f702aca2_img.jpg) + +``` +sequenceDiagram + participant MS + participant Source GANC + participant Target RNC + participant SGSN + + Note over MS, Source GANC: 1. Active GA-RRC PTC(s), RAB(s) and PDP Context(s) + Note over Source GANC: 2. GA-RRC UPLINK QUALITY INDICATION + Note over MS: 3. GA-RRC RELOCATION INFORMATION + Note over Source GANC: 4. Relocation Required + Note over Target RNC: 5. Relocation Request + Note over Target RNC: 6. RAN, Iu Resource Allocation + Note over Target RNC: 7. Relocation Request Ack +``` + +The diagram illustrates the preparation phase of a PS handover from a GAN to UTRAN. It involves four main entities: MS (Mobile Station), Source GANC (GPRS AN Controller), Target RNC (Radio Network Controller), and SGSN (Serving GPRS Support Node). The sequence of messages is as follows: 1. Active GA-RRC PTC(s), RAB(s) and PDP Context(s) (between MS and Source GANC); 2. GA-RRC UPLINK QUALITY INDICATION (from Source GANC to MS); 3. GA-RRC RELOCATION INFORMATION (from MS to Source GANC); 4. Relocation Required (from Source GANC to SGSN); 5. Relocation Request (from SGSN to Target RNC); 6. RAN, Iu Resource Allocation (within Target RNC); 7. Relocation Request Ack (from Target RNC to SGSN). + +Sequence diagram of GAN to UTRAN PS Handover Preparation Phase + +**Figure 73: GAN to UTRAN PS Handover Preparation Phase** + +1. The MS is in active packet flow exchange with active PDP Context(s) and PTC(s) in the GAN. +2. The GANC may send a GA-RRC UPLINK QUALITY INDICATION if there is a problem with the uplink quality for the ongoing session. Uplink Quality Indication is information sent by the GANC to the MS indicating the crossing of a uplink quality threshold in the uplink direction. Whenever the MS receives an indication of bad quality, it should start the relocation procedure, as described in the next step. Alternatively, MS can use its local measurements to decide to initiate the handover procedure. +3. The MS decides to initiate a PS handover from GAN to UTRAN by sending GA-RRC RELOCATION INFORMATION message to the GANC. +4. The GANC selects a target RNC based on the contents of the GA-RRC RELOCATION INFORMATION message. It sends *Relocation Required* message to the SGSN containing the selected RNC information. +5. The SGSN sends a *Relocation Request* message to the target RNC. +6. The RNC performs the necessary allocation of radio and Iu transport resources. +7. The RNC returns *Relocation Request Acknowledge* message to the SGSN. This message contains a transparent container that contains channelization information needed by MS to access UTRAN. + +### 9.23.4.2 Execution Phase + +![Sequence diagram of GAN to UTRAN PS Handover Execution Phase. Lifelines: MS, Source GANC, Target RNC, SGSN. The sequence shows the transfer of context and commands between these entities to complete the handover.](b550cb515008f6bab9f295adcb28b5f6_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Source GANC + participant Target RNC + participant SGSN + + Note right of Target RNC: 4. UE access detected by RNC + + SGSN->>Source GANC: 1. Relocation Command + Source GANC->>MS: 2. GA-RRC RELOCATION COMMAND + Source GANC->>SGSN: 2. Forward SRNS Context + SGSN->>Target RNC: 3. Forward SRNS Context + Note right of Target RNC: 4. UE access detected by RNC + Target RNC->>SGSN: 4. Relocation Detect + MS->>Target RNC: 5. Uu: Physical Channel Reconfiguration Complete + Target RNC->>SGSN: 5. Relocation Complete + Note right of Target RNC: 6. Active RAB(s) and PDP Context(s) + SGSN->>Source GANC: 7. Iu Release Command + Source GANC->>SGSN: 7. Iu Release Complete + Note right of Target RNC: 8. Routing Area Update Procedure + +``` + +Sequence diagram of GAN to UTRAN PS Handover Execution Phase. Lifelines: MS, Source GANC, Target RNC, SGSN. The sequence shows the transfer of context and commands between these entities to complete the handover. + +**Figure 74: GAN to UTRAN PS Handover Execution Phase** + +- The SGSN begins the Execution Phase by issuing the *Relocation Command* message to the GANC. The message contains the channel access information in the target UTRAN cell. +- The GANC sends GA-RRC RELOCATION COMMAND to the MS. This message contains the information from the Relocation Command received in Step 1 earlier. + - The GANC also sends *Forward SRNS Context* message to the target RNC via the SGSN. +- The SGSN relays the *Forward SRNS Context* message to the target RNC. +- Upon receiving the GA-RRC RELOCATION COMMAND, the MS immediately suspends uplink GTP PDU transfer. It immediately begins accessing the UTRAN using the indicated channelization parameters in the message. The MS's access attempt is detected by the Node B and RNC, and is reported to the SGSN via the *Relocation Detect* message. +- The MS completes the lower layer setup and configuration, and sends the RRC *Physical Channel Reconfiguration Complete* to the target RNC. This triggers the target RNC to send the *Relocation Complete* message to SGSN. At this stage, the target RNC assumes the role of SRNC for the MS. +- The packet data flow is now active via the UTRAN. +- The SGSN releases the Iu-PS connection by sending the *Iu Release Command* message to the GANC, to which GANC responds with *Iu Release Complete* message. +- If the Routing Area of the UTRAN cell is different from that of the GAN cell, then the MS performs the Routing Area Update procedure. + +## Annex A (normative): Security mechanisms + +### A.1 EAP based Authentication + +#### A.1.1 EAP-SIM Procedure for authentication + +![Sequence diagram of the EAP-SIM authentication procedure. Lifelines: MS, Generic IP Access Network, GANC-SEGW, AAA, HSS/HLR. The process involves IKEv2 SA initiation, EAP-SIM challenge-response, and final GAN registration.](99a0eddf16e836f411661acee6facd17_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GIAN as Generic IP Access Network + participant GANC-SEGW + participant AAA + participant HSS/HLR + + Note left of MS: 1. Generic IP Access network connection establishment + MS->>GANC-SEGW: 2a. IKE_SA_INIT + GANC-SEGW-->>MS: 2b. IKE_SA_INIT + MS->>GANC-SEGW: 2c. IKE_AUTH (NAI in IDi, no AUTH included) + Note right of GANC-SEGW: 3. Select appropriate AAA server + GANC-SEGW->>AAA: 4. EAP Response/Identity [NAI based on IMSI] + AAA->>GANC-SEGW: 5. EAP Request/SIM Start + GANC-SEGW-->>MS: 6. EAP Request/SIM Start + MS->>GANC-SEGW: 7. EAP Response/SIM Start [NONCE_MT] + GANC-SEGW->>AAA: 8. EAP Response/SIM Start [NONCE_MT] + AAA->>HSS/HLR: 9. Send Auth Info + HSS/HLR-->>AAA: 10. Response (triplets) + AAA->>GANC-SEGW: 11. EAP Request/SIM-Challenge [RAND, MAC, Next re-auth ID] + GANC-SEGW-->>MS: 12. EAP Request/SIM-Challenge [RAND, MAC, Next re-auth ID] + Note left of MS: 13. Execute EAP/SIM + MS->>GANC-SEGW: 14. EAP SIM/Response-Challenge [MAC] + GANC-SEGW->>AAA: 15. EAP SIM/Response-Challenge [MAC] + Note right of AAA: 16. Verify MAC + AAA->>GANC-SEGW: 17. EAP Success + keying material + GANC-SEGW-->>MS: 18. EAP Success + MS-->>GANC-SEGW: 19. Complete IKE signalling + Note left of GIAN: 20. GAN Registration + +``` + +Sequence diagram of the EAP-SIM authentication procedure. Lifelines: MS, Generic IP Access Network, GANC-SEGW, AAA, HSS/HLR. The process involves IKEv2 SA initiation, EAP-SIM challenge-response, and final GAN registration. + +Figure A.1: EAP-SIM authentication procedure + +The EAP-SIM authentication mechanism is specified in [30]. This clause describes how this mechanism is used in GAN. + +1. The MS connects to the generic IP access network. +2. The MS obtains the IP address of the GANC-SEGW, and initializes the IKEv2 authentication procedure by starting the IKE\_SA\_INIT exchange. It indicates the desire to use EAP by leaving out the AUTH payload from message 3 of the IKE\_AUTH exchange, and the initiator identity is composed compliant with the Network Access Identifier (NAI) format specified in RFC 2486 [36], which contains the IMSI. + +3. The GANC-SEGW communicates with the local AAA server through the Wm interface, which in turn determines the proper AAA Server based on the realm part of the NAI. The routing path may include one or several AAA proxies (not shown in figure A.1). +4. The GANC-SEGW sends an EAP Response/Identity message to the AAA server, containing the identity included in the third IKE message. This triggers the start of EAP-SIM. +5. The AAA Server identifies the subscriber as a candidate for authentication with EAP-SIM, based on the received identity, and sends the EAP Request/SIM-Start packet to GANC-SEGW. +6. The GANC-SEGW forwards the EAP Request/SIM-Start packet to MS. +7. The MS chooses a fresh random number NONCE\_MT. The random number is used in network authentication. The MS sends the EAP Response/SIM-Start packet, containing NONCE\_MT, to the GANC-SEGW. +8. The GANC-SEGW forwards the EAP Response/SIM-Start packet to the AAA Server. +9. The AAA server requests authentication data from the HLR, based on the IMSI. Note that the AAA server could instead use cached triplets previously retrieved from the HLR to continue the authentication process. +10. The AAA server receives multiple triplets from the HLR. +11. The AAA server formulates an EAP-SIM/Challenge with multiple RAND challenges, and includes a message authentication code (MAC) whose master key is computed based on the associated Kc keys, as well as the NONCE\_MT. A new re-authentication identity may be chosen and protected (i.e. encrypted and integrity protected) using EAP-SIM generated keying material. The AAA Server sends this RAND, MAC and re-authentication identity to the GANC-SEGW in the EAP Request/SIM-Challenge message. +12. The GANC-SEGW forwards the EAP Request/SIM-Challenge message to the MS. +13. The MS runs N times the GSM A3/A8 algorithm in the SIM, once for each received RAND. This computing gives N SRES and Kc values. The MS calculates its copy of the network authentication MAC with the newly derived keying material and checks that it is equal with the received MAC. If the MAC is incorrect, the network authentication has failed and the MS cancels the authentication. The MS continues the authentication exchange only if the MAC is correct. The MS calculates a new MAC with the new keying material covering the EAP message concatenated to the N SRES responses. If a re-authentication ID was received, then the MS stores this ID for future authentications. +14. The MS sends EAP Response/SIM-Challenge containing calculated MAC to the GANC-SEGW. +15. The GANC-SEGW forwards the EAP Response/SIM-Challenge packet to the AAA Server. +16. The AAA Server verifies that its copy of the response MAC is equal to the received MAC. +17. If the comparison in step 16 is successful, then the AAA Server sends the EAP Success message to the GANC-SEGW. The AAA Server includes derived keying material for confidentiality and/or integrity protection between MS and GANC-SEGW, in the underlying AAA protocol message (i.e. not at EAP level). +18. The GANC-SEGW informs the MS about the successful authentication with the EAP Success message. +19. Now the EAP-SIM exchange has been successfully completed, the IKE signalling can be completed +20. The Secure Association between MS and GANC-SEGW has been completed and the MS can continue with the discovery or registration procedure. + +## A.1.2 EAP-AKA Procedure for authentication + +The EAP-AKA authentication mechanism is specified in [EAP AKA]. This section describes how this mechanism is used in GAN. + +![Sequence diagram of EAP-AKA authentication procedure between MS, Generic IP Access Network, GANC-SEGW, AAA, and HSS/HLR.](2b00743506f6a3bbd17af764162dc76d_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GIAN as Generic IP Access Network + participant GANC-SEGW + participant AAA + participant HSS/HLR + + Note left of MS: 1. Generic IP Access network connection establishment + MS->>GANC-SEGW: 2a. IKE_SA_INIT + GANC-SEGW-->>MS: 2b. IKE_SA_INIT + MS->>GANC-SEGW: 2c. IKE_AUTH (NAI in IDi, no AUTH included) + Note right of GANC-SEGW: 3. Select appropriate AAA server + GANC-SEGW->>AAA: 4. EAP Response/Identity [NAI based on IMSI] + AAA->>HSS/HLR: 5. Send Auth Info + HSS/HLR-->>AAA: 6. Response (Authentication vector) + AAA->>GANC-SEGW: 7. EAP Request/AKA Challenge[RAND, AUTN, MAC, Next re-auth ID] + GANC-SEGW->>MS: 8. EAP Request/AKA Challenge[RAND, AUTN, MAC, Next re-auth ID] + Note left of MS: 9. Run UMTS algorithms and verify AUTN + MS->>GANC-SEGW: 10. EAP Response/ AKA Challenge[RES, MAC] + GANC-SEGW->>AAA: 11. EAP Response/ AKA Challenge[RES, MAC] + Note right of AAA: 12. Check MAC and verify RES + AAA->>GANC-SEGW: 13. EAP Success + keying material + GANC-SEGW->>MS: 14. EAP Success + MS-->>GANC-SEGW: 15. Complete IKE signalling + Note left of MS: 16. GAN Registration + +``` + +Sequence diagram of EAP-AKA authentication procedure between MS, Generic IP Access Network, GANC-SEGW, AAA, and HSS/HLR. + +**Figure A.2: EAP-AKA authentication procedure** + +1. The MS connects to the generic IP access network. +2. The MS obtains the IP address of the GANC-SEGW, and initializes the IKEv2 authentication procedure by starting the IKE\_SA\_INIT exchange. It indicates the desire to use EAP by leaving out the AUTH payload from message 3, the first message of the IKE\_AUTH exchange, and the initiator identity is composed compliant with the Network Access Identifier (NAI) format specified in RFC 2486, which contains the IMSI and an indication that EAP-AKA should be used. +3. The GANC-SEGW communicates with the local AAA server through the Wm interface, which in turn determines the proper AAA Server based on the realm part of the NAI. The routing path may include one or several AAA proxies (not shown in figure A.2). +4. The GANC-SEGW sends an EAP Response/Identity message to the AAA server, containing the initiator identity included in the third IKE message. The leading digit of the NAI indicates that the MS wishes to use EAP-AKA. +5. The AAA server identifies the subscriber as a candidate for authentication with EAP-AKA, based on the received identity, and verifies that EAP-AKA shall be used based on subscription information. The AAA server requests the user profile and UMTS authentication vector(s) from the HSS/HLR, if these are not available in the AAA server. + +6. Optionally, the AAA receives user subscription and UMTS authentication vector(s) from the HSS/HLR. The UMTS authentication vector consists of random part (RAND), an authentication part (AUTH), an expected result part (XRES) and sessions keys for integrity check (IK) and encryption (CK). AAA server determines the EAP method (SIM or AKA) to be used, according to the user subscription and/or the indication received from the MS. +In this sequence diagram, it is assumed that the MS holds a USIM and EAP-AKA will be used. +7. The AAA server formulates an EAP-Request/AKA Challenge with RAND, AUTN and includes a message authentication code (MAC) whose master key is computed based on the associated IK and CK. A new re-authentication identity may be chosen and protected (i.e. encrypted and integrity protected) using EAP-AKA generated keying material. The AAA Server sends the RAND, AUTN, MAC and re-authentication identity to the GANC-SEGW in the EAP Request/AKA-Challenge message. +8. The GANC-SEGW forwards the EAP Request/AKA-Challenge message to the MS. +9. The MS runs UMTS algorithm on the USIM. The USIM verifies that the AUTN is correct and hereby authenticates the network. If AUTN is incorrect, the MS rejects the authentication (not shown in figure A.3). If AUTN is correct, the USIM computes RES, IK and CK. The MS calculates a new MAC with the new keying material (IK and CK) covering the EAP message. +If a re-authentication ID was received, then the MS stores this ID for future authentications. +10. The MS sends EAP Response/AKA-Challenge containing calculated RES and MAC to the GANC-SEGW. +11. The GANC-SEGW forwards the EAP Response/AKA-Challenge message to the AAA Server. +12. The AAA Server verifies the received MAC and compares XRES to the received RES. +13. If the checks in step 12 are successful, then the AAA Server sends the EAP Success message to the GANC-SEGW. The AAA Server includes derived keying material for confidentiality and/or integrity protection between MS and GANC-SEGW, in the underlying AAA protocol message (i.e. not at EAP level). +14. The GANC-SEGW informs the MS about the successful authentication with the EAP Success message. +15. Now the EAP-SIM exchange has been successfully completed, the IKE signaling can be completed. +16. The Secure Association between MS and GANC-SEGW has been completed and the MS can continue with the GAN discovery or registration procedure. + +## A.1.3 Fast Re-authentication + +When the authentication process is performed frequently, especially with a large number of connected Mobile Stations, performing fast re-authentication can reduce the network load resulting from this authentication. The fast re-authentication process allows the AAA server to authenticate a user based on keys derived from the last full authentication process. + +The MS and GANC-SEGW can use a procedure for fast re-authentication in order to re-authenticate an MS e.g. when setting up a new SA because the IP address of the MS has changed as a result of a handover between generic IP access network attachment points connected to different IP subnets. Fast re-authentication is provided by EAP-SIM and EAP-AKA, and does not make use of the GSM A3/A8 or UMTS algorithms. The MS may use the re-authentication ID in the IKE\_SA\_INIT. The decision to make use of the fast re-authentication procedure is taken by the AAA server. + +The basic elements of these procedures are the following: + +- The MS initiates a new SA with a GANC-SEGW that it was previously connected to and uses the re-authentication ID (re-authentication ID received during the previous full authentication procedure) in the IKE\_SA\_INIT exchange. The EAP-SIM or EAP-AKA procedure is started as a result of these exchanges. +- The AAA server and MS re-authenticate each other based on the keys derived on the preceding full authentication. + +### A.1.3.1 EAP-SIM Fast Re-authentication + +The EAP-SIM specification [30] includes support for fast re-authentication. The use of this mechanism may be subject to operator policy. + +![Sequence diagram of EAP-SIM fast re-authentication procedure. Lifelines: MS, GANC-SEGW, AAA, HSS/HLR. The process involves IKEv2 SA_INIT and AUTH exchanges, followed by EAP Response/Identity, EAP Request/SIM/Re-authentication, verification of Counter and MAC, and final EAP Success messages.](ef45b00396c293be0b18d32b97118bf4_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC-SEGW + participant AAA + participant HSS/HLR + + Note left of MS: 1a. IKE_SA_INIT + MS->>GANC-SEGW: 1a. IKE_SA_INIT + Note right of GANC-SEGW: 1b. IKE_SA_INIT + GANC-SEGW-->>MS: 1b. IKE_SA_INIT + Note left of MS: 1c. IKE_AUTH (Re-authentication Id) + MS->>GANC-SEGW: 1c. IKE_AUTH (Re-authentication Id) + Note right of GANC-SEGW: 2. EAP Response/Identity [Re-authentication ID] + GANC-SEGW->>AAA: 2. EAP Response/Identity [Re-authentication ID] + Note left of AAA: 3. EAP Request/SIM/Re-authentication [Counter, NONCE, MAC, Next re-auth ID] + AAA-->>GANC-SEGW: 3. EAP Request/SIM/Re-authentication [Counter, NONCE, MAC, Next re-auth ID] + Note right of GANC-SEGW: 4. EAP Request/SIM/Re-authentication [Counter, NONCE, MAC, Next re-auth ID] + GANC-SEGW-->>MS: 4. EAP Request/SIM/Re-authentication [Counter, NONCE, MAC, Next re-auth ID] + Note left of MS: 5. Verify Counter, MAC + MS->>GANC-SEGW: 6. EAP SIM/Response-Challenge [Counter, MAC] + Note right of GANC-SEGW: 7. EAP SIM/Response-Challenge [Counter, MAC] + GANC-SEGW->>AAA: 7. EAP SIM/Response-Challenge [Counter, MAC] + Note left of AAA: 8. Verify Counter, MAC + AAA-->>GANC-SEGW: 9. EAP Success + Note right of GANC-SEGW: 10. EAP Success + GANC-SEGW-->>MS: 10. EAP Success + +``` + +Sequence diagram of EAP-SIM fast re-authentication procedure. Lifelines: MS, GANC-SEGW, AAA, HSS/HLR. The process involves IKEv2 SA\_INIT and AUTH exchanges, followed by EAP Response/Identity, EAP Request/SIM/Re-authentication, verification of Counter and MAC, and final EAP Success messages. + +**Figure A.3: EAP-SIM fast re-authentication procedure** + +1. The MS initializes the IKEv2 authentication procedure by starting the IKE\_SA\_INIT exchange. It indicates the desire to use EAP by leaving out the AUTH payload from message 3 of the IKE\_AUTH exchange, and the initiator identity contains the re-authentication identity (this identity was previously delivered by AAA server in a full authentication procedure). +2. The GANC-SEGW sends an EAP Response/Identity message to the AAA server, containing the re-authentication ID as was included in the third IKE message. This triggers the start of EAP-SIM. +3. The AAA server initiates the Counter (which was initialized to one in the full authentication process) and sends it in the EAP Request message, together with the NONCE, the MAC (calculated over the NONCE) and a re-authentication id for a next fast re-authentication. If the AAA server is not able to deliver a re-authentication identity, then the MS shall force a full-authentication next time (to avoid the use of the re-authentication identity more than once). +4. The GANC-SEGW forwards the EAP Request message to the MS. +5. The MS verifies that the Counter value is fresh and the MAC is correct. +6. The MS sends the EAP Response message with the same Counter value and a calculated MAC to the GANC-SEGW. +7. The GANC-SEGW forwards the response to the AAA server. +8. The AAA server verifies that the Counter value is the same as it sent, and that the MAC is correct. +9. The AAA server sends an EAP Success message to the GANC-SEGW. +10. The GANC-SEGW forwards the EAP Success message to the MS. + +### A.1.3.2 EAP-AKA Fast Re-authentication + +The EAP-AKA specification [38] includes support for fast re-authentication. The use of this mechanism may be subject to operator policy. + +![Sequence diagram of EAP-AKA fast re-authentication procedure. Lifelines: MS, GANC-SEGW, AAA, HSS/HLR. The process involves IKEv2 SA_INIT and AUTH exchanges followed by EAP-AKA messages (Request/Response) between the MS and GANC-SEGW, which are then relayed to the AAA server. Verification steps occur at the MS and AAA server.](9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC-SEGW + participant AAA + participant HSS/HLR + + Note left of MS: 1a. IKE_SA_INIT + MS->>GANC-SEGW: 1a. IKE_SA_INIT + Note right of GANC-SEGW: 1b. IKE_SA_INIT + GANC-SEGW-->>MS: 1b. IKE_SA_INIT + Note left of MS: 1c. IKE_AUTH (Re-authentication Id) + MS->>GANC-SEGW: 1c. IKE_AUTH (Re-authentication Id) + Note right of GANC-SEGW: 2. EAP Response/Identity [Re-authentication Id] + GANC-SEGW->>AAA: 2. EAP Response/Identity [Re-authentication Id] + Note right of AAA: 3. EAP Request/AKA-Reauthentication [Counter, NONCE, MAC, Next re-auth Id] + AAA-->>GANC-SEGW: 3. EAP Request/AKA-Reauthentication [Counter, NONCE, MAC, Next re-auth Id] + Note right of GANC-SEGW: 4. EAP Request/ AKA-Reauthentication [Counter, NONCE, MAC, Next re-auth ID] + GANC-SEGW-->>MS: 4. EAP Request/ AKA-Reauthentication [Counter, NONCE, MAC, Next re-auth ID] + Note left of MS: 5. Verify Counter, MAC + MS->>GANC-SEGW: 6. EAP Response/AKA-Reauthentication [Counter, MAC] + Note right of GANC-SEGW: 7. EAP Response/AKA-Reauthentication [Counter, MAC] + GANC-SEGW->>AAA: 7. EAP Response/AKA-Reauthentication [Counter, MAC] + Note right of AAA: 8. Verify Counter, MAC + Note right of AAA: 9. EAP Success + AAA-->>GANC-SEGW: 9. EAP Success + Note right of GANC-SEGW: 10. EAP Success + GANC-SEGW-->>MS: 10. EAP Success + +``` + +Sequence diagram of EAP-AKA fast re-authentication procedure. Lifelines: MS, GANC-SEGW, AAA, HSS/HLR. The process involves IKEv2 SA\_INIT and AUTH exchanges followed by EAP-AKA messages (Request/Response) between the MS and GANC-SEGW, which are then relayed to the AAA server. Verification steps occur at the MS and AAA server. + +**Figure A.4: EAP-AKA fast re-authentication procedure** + +1. The MS initializes the IKEv2 authentication procedure by starting the IKE\_SA\_INIT exchange. It indicates the desire to use EAP by leaving out the AUTH payload from message 3, the first message of the IKE\_AUTH exchange, and the initiator identity contains the re-authentication identity (this identity was previously delivered by AAA server in a EAP-AKA full authentication procedure). +2. The GANC-SEGW sends an EAP Response/Identity message to the AAA server, containing the re-authentication ID as was included in the third IKE message. This triggers the start of EAP-AKA. +3. The AAA server initiates the Counter (which was initialized to one in the full authentication process) and sends it in the EAP Request/AKA-Reauthentication message, together with the NONCE, the MAC (calculated over the NONCE) and a re-authentication id for a next fast re-authentication. If the AAA server is not able to deliver a re-authentication identity, then the MS shall force a full-authentication next time (to avoid the use of the re-authentication identity more than once). +4. The GANC-SEGW forwards the EAP Request/AKA-Reauthentication message to the MS. +5. The MS verifies that the Counter value is fresh and the MAC is correct. +6. The MS sends the EAP Response/AKA-Reauthentication message with the same Counter value and a calculated MAC to the GANC-SEGW. +7. The GANC-SEGW forwards the response to the AAA server. +8. The AAA server verifies that the Counter value is the same as it sent, and that the MAC is correct. +9. The AAA server sends an EAP Success message to the GANC-SEGW. +10. The GANC-SEGW forwards the EAP Success message to the MS. + +--- + +## A.2 Profile of IKEv2 + +When IKEv2 [32] is used in the context of this specification the profile specified in this section shall be supported by the MS and the GANC-SEGW. + +IKEv2 shall meet the profiling given in clause 5.4.2 of TS 33.210 [55] with the following additions: + +- The pseudorandom function AES-XCBC-PRF-128 shall be considered mandatory. +- The integrity algorithm AES-XCBC-MAC-96 shall be considered mandatory. +- The MS shall support at least one of the mandatory encryption algorithms, at least one of the mandatory pseudorandom functions and at least one of the mandatory integrity algorithms. +- The MS shall support both Diffie-Hellman group 2 (1024-bit MODP) and Diffie-Hellman group 14 (2048-bit MODP). + +If the MS proposes one or more profiles that were not included in previous versions of this specification, and the SeGW indicates that the selected profiles are not acceptable (e.g., the SeGW has not been upgraded to the current version of this specification), the MS shall be prepared to “drop back” to one or more of the profiles that were included in previous versions of this specification. + +--- + +## A.3 Profile of IPsec ESP + +When IPSec ESP [56] is used in the context of this specification the profile specified in this section shall be supported by the MS and the GANC-SEGW. + +IPsec ESP shall meet the profiling given clause 5.3 of TS 33.210 [55] with the following additions: + +- The authentication algorithm AES-XCBC-MAC-96 shall be considered mandatory. +- The MS shall support at least one of the mandatory, non-NULL encryption algorithms and at least one of the mandatory authentication algorithms. +- Tunnel mode shall be used. + +If the MS proposes one or more profiles that were not included in previous versions of this specification, and the SeGW indicates that the selected profiles are not acceptable (e.g., the SeGW has not been upgraded to the current version of this specification), the MS shall be prepared to “drop back” to one or more of the profiles that were included in previous versions of this specification. + +--- + +## Annex B (informative): Configuration Information + +### B.1 GAN A/Gb mode ARFCN/BSIC for handover-to-GAN + +Selection of ARFCN may use the following guidelines: + +1. The ARFCN should not be allocated from the operator's existing BCCH pool so that a scarce BCCH is not used. +2. The ARFCN maybe desired to be the same unique number across the whole operator network to minimize the BSS configuration effort. + +The following are available options for the selection of the ARFCN: + +1. Ideally, the GAN is assigned an ARFCN value, which is not in the frequency bands currently used by the operator. +2. Typically, different PLMNs in the same country have disjoint frequency allocations. For each PLMN, some of the frequencies are reserved for BCCH beacon; BCCH will be transmitted with constant max power on time slot 0. Other frequencies are dedicated as traffic channels. The GAN ARFCN could use any non-BCCH frequency from the carrier's existing frequency pool. Standard GSM MSs will be able to tune onto this channel but will not be able to find the FCCH burst. +3. Alternatively, in a PCS-only (1 900 MHz) network, ARFCN can be any value falling within the GSM (900 MHz) or DCS (1 800 MHz) band. Standard GSM handsets operating in PCS-only mode will ignore this ARFCN. Tri-band handsets supporting automatic band change will not be able to find a BCCH on the associated frequency. + +--- + +### B.2 GAN Iu mode UARFCN/PSC for handover-to-GAN + +Selection of the UTRA Absolute RF Channel Number (UARFCN) and Primary Scrambling Code (PSC) may use the following guidelines: + +1. The GAN UARFCN may be allocated from the operator's existing UARFCN pool. +2. The GAN UARFCN should be the same as the macro network UARFCN value of the current serving UTRAN cell for the MS, to avoid the need to require the MS to do inter-frequency measurements for UTRAN-to-GAN handover purposes (e.g., requiring that the MS operate in compressed mode). The GANC may use the downlink UARFCN of the UTRAN cells in the current active set, received from the MS in the GA-RC REGISTER REQUEST message, when deciding which UARFCN to return to the MS in the GA-RC REGISTER ACCEPT message. Note that **all UTRAN cells in the current active set use the same downlink UARFCN.** +3. The GAN PSC may be desired to be the same unique number across the whole operator network to minimize the RNS configuration effort. + +#### B.2.1 Cell Measurement Quantities and Values + +As described in clause 9.14.2 (CS case) and clause 9.23.2 (PS case), handover from UTRAN to GAN Iu mode requires that the MS include information corresponding to the registered GAN Iu mode cell in the *Measurement Report* message sent to the RNC. The MS reports the "highest signal quality" for the GAN Iu mode cell. This is not the actual measured signal level on the GAN, rather an artificial value allowing the MS to indicate preference for the GAN. + +The RNC may request that the MS report either the downlink Ec/No (received energy per chip divided by the noise power spectral density in the band) or downlink RSCP (Received Signal Code Power) quantities. The MS shall report maximum values for the Ec/No or RSCP quantities. The maximum value of Ec/No is 63. The maximum value of RSCP is 91. + +--- + +## Annex C (informative): Identifiers in GAN + +### C.1 Identifiers for MSs and generic IP access network + +The following are the key MS and generic IP access network addressing parameters. + +1. The IMSI associated with the (U)SIM in the terminal. + - The MS provide the IMSI to the GANC during the Registration procedure. The GANC maintains a record for each registered MS. For example, IMSI is used by the GANC to index the appropriate MS record when the GANC receives a BSSMAP PAGING message. +2. Public IP Address of the MS. + - The Public IP address of MS is the source IP present in the outermost IP header of packets received from the MS by the GANC-SEGW. If available, this identifier may be used by the GANC to support location services and fraud detection or by service providers to signal Managed IP networks IP flows that require special QoS treatment. +3. The generic IP access network point of attachment address (AP-ID). + - The MS provides the AP-ID to the GANC at Registration. The AP-ID may be used by the GANC to support location services or by the service provider to restrict GAN access to authorized APs. + +--- + +### C.2 Cell identifiers for GAN A/Gb mode + +#### C.2.1 GAN Cell Id for Location Services & Billing + +Cell Global Identities (CGI) may be used to perform location-basing routing of a call for services such as: emergency services; operators; announcements and freephone numbers. Cell identities can be also used by the core network to identify the location of where a call was originated/terminated for charging purposes. The GANC provides a CGI to the core network indicating the GAN cell. + +##### C.2.1.1 Assigning GAN Cell Id based on GSM location + +In the GAN architecture, the MS has a direct IP-based connection to the GANC. The GAN coverage area may overlay the GERAN coverage area. Logical mapping of GAN Cells to a CGI can be completed at various resolutions, for example (but not limited to): + +- a GAN cell for each GSM cell; +- a GAN cell for each GSM routing area; or +- a GAN cell for each GSM location area. + +A single GANC could represent one or more cells (CGI) in one or more location areas (LAI). + +#### C.2.2 GAN Cell Id for handover-to-GAN + +The GAN cell id used for location and charging can be independent from the GAN cell id used for handover. + +A single GANC represents a single cell, and referred to as GAN cell, for the purpose of handover from GERAN to GAN. This "handover-GANC-CGI" is not visible to the MS. It is only used in the GERAN and CN for identifying a target cell (i.e. target GANC) for handover from GERAN to GAN, and ignored by the GANC, when received during the handover via the A-interface. + +The "handover-GANC-CGI" assigned to the GANC is configured as the target handover cell in all neighbouring GERAN cells (in the ARFCN/BSIC-to-CGI mapping table). Neighbouring GERAN cells are those whose service area "overlaps" the GANC service area, for the purpose of handover. + +For example, neighbour cells are: + +- All GERAN cells attached to the same MSC as the GANC. +- All GERAN cells attached to a different MSC but that can handover to the MSC to which the GANC is attached. + +When the MS reports measurements to the GERAN BSS on the GAN cell identified by its ARFCN/BSIC, then the GERAN BSS maps the ARFCN/BSIC to the "handover-GANC-CGI" through its mapping table, and is thus able to identify the target cell (GANC) for handover-to-GAN. + +### C.2.3 GAN ARFCN/BSIC for handover-to-GAN + +The GERAN-to-GAN handover method makes use of an RF channel number (ARFCN) and base station identity code (BSIC) parameters to identify the GAN target cell. All GANCs in a given operator domain can share the same ARFCN/BSIC values, if there is a single GANC neighbour per GSM cell. This ARFCN/BSIC is indicated to the MS by the GANC during GAN registration. + +The selection of the RF channel number (ARFCN) used for the UTRAN to GAN handover procedure should not correspond to a channel from any frequency band defined in 3GPP TS 45.005, to avoid UEs not requiring compressed mode for GSM measurements from unnecessarily powering up their GSM receivers. + +### C.3 (void) + +## Annex D (informative): Change history + +| Change history | | | | | | | | +|----------------|------------|-----------|------|-----|-----------------------------------------------------------------------------------|--------|--------| +| Date | TSG GERAN# | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2005-01 | 23 | GP-050544 | - | - | Version for Release 6 approved at TSG GERAN#23 | 2.0.0 | 6.0.0 | +| 2005-04 | 24 | GP-050934 | 001 | | Introduction of the support for Cell Broadcast in GAN | 6.0.0 | 6.1.0 | +| 2005-06 | 25 | GP-051594 | 003 | | Editorial correction PCCO to GAN | 6.1.0 | 6.2.0 | +| 2005-06 | 25 | GP-051595 | 004 | | GERAN preferred mode MS behaviour | 6.1.0 | 6.2.0 | +| 2005-06 | 25 | GP-051763 | 005 | 1 | GAN only mode MS behaviour | 6.1.0 | 6.2.0 | +| 2005-06 | 25 | GP-051704 | 007 | | Clarification to the CS charging description for GAN | 6.1.0 | 6.2.0 | +| 2005-09 | 26 | GP-052142 | 0009 | | Removal of addressing for the Generic Access Network | 6.2.0 | 6.3.0 | +| 2005-11 | 27 | GP-052796 | 0010 | 1 | Clarifications to GAN Stage 2 | 6.3.0 | 6.4.0 | +| 2006-01 | 28 | GP-060460 | 0008 | 6 | Introduction of the Inter RAT Handover to GAN definition | 6.4.0 | 6.5.0 | +| 2006-01 | 28 | GP-060391 | 0012 | 1 | Clarifications to GAN Stage 2 | 6.4.0 | 6.5.0 | +| 2006-04 | 29 | GP-060929 | 0013 | 1 | Clarification on GANC Selection | 6.5.0 | 6.6.0 | +| 2006-04 | 29 | GP-060924 | 0014 | 1 | Rove-in description alignment with 'Call re-establishment' | 6.5.0 | 6.6.0 | +| 2006-05 | 30 | GP-061188 | 0016 | | Clarification of GAN selection when MS in GERAN/UTRAN preferred mode | 6.6.0 | 6.7.0 | +| 2006-11 | 32 | GP-062357 | 0018 | 1 | GAN cell selection : Alignment with stage 3 | 6.7.0 | 6.8.0 | +| 2006-11 | 32 | GP-062272 | 0019 | | Cryptographic algorithm update | 6.7.0 | 6.8.0 | +| 2006-11 | 32 | GP-062119 | 0017 | 2 | PS Handover Support for GAN | 6.8.0 | 7.0.0 | +| 2007-02 | 33 | GP-070499 | 0021 | 3 | Correction of BSSMAP messages in the Mobile Terminated Call Flow | 7.0.0 | 7.1.0 | +| 2007-05 | 34 | GP-071010 | 0022 | 1 | GERAN/UTRAN cells scan for rove-out in GAN mode | 7.1.0 | 7.2.0 | +| 2007-08 | 35 | GP-071522 | 0024 | 3 | Editorial corrections to GERAN and GSM references for GAN emergency procedures | 7.2.0 | 7.3.0 | +| 2007-11 | 36 | GP-071945 | 0028 | 1 | Change of specification title | 7.3.0 | 7.4.0 | +| 2007-11 | 36 | GP-071977 | 0025 | 3 | Addition of GAN Iu Mode functionality to GAN Stage 2 | 7.4.0 | 8.0.0 | +| 2007-11 | 36 | GP-072013 | 0026 | 2 | Maintaining PLMN Continuity in GAN Mode | 7.4.0 | 8.0.0 | +| 2008-02 | 37 | GP-080397 | 0029 | 2 | Supplementing GAN Registration Update with UARFCN | 8.0.0 | 8.1.0 | +| 2008-05 | 38 | GP-080844 | 0030 | 1 | Stage 2 changes to align with GAN Stage 3 | 8.1.0 | 8.2.0 | +| 2008-05 | 38 | GP-080845 | 0033 | 1 | Stage 2 clarification of MS deregistration after handover from GAN to GERAN/UTRAN | 8.1.0 | 8.2.0 | +| 2008-08 | 39 | GP-081390 | 0034 | 2 | Supporting Multiple GAN Modes per PLMN | 8.2.0 | 8.3.0 | +| 2009-02 | 41 | GP-090164 | 0036 | | Clarification on the GANC Selection Process for PLMN Continuity | 8.3.0 | 8.4.0 | +| 2009-02 | 41 | GP-090165 | 0037 | | Clarification on Maintaining PLMN Continuity in GAN Mode | 8.3.0 | 8.4.0 | +| 2009-12 | 44 | | | | Version for Release 9 | 8.4.0 | 9.0.0 | +| 2010-11 | 48 | GP-101977 | 0039 | 1 | Changes to support rove in from LTE and rove out to LTE | 9.0.0 | 10.0.0 | +| 2010-11 | 48 | GP-101970 | 0040 | 1 | Changes to support RFC 4867 bandwidth-efficient mode | 9.0.0 | 10.0.0 | +| 2011-03 | 49 | GP-110199 | 0041 | | GAN IPsec alignment | 10.0.0 | 10.1.0 | +| 2012-09 | 55 | | | | Version for Release 11 | 10.1.0 | 11.0.0 | \ No newline at end of file diff --git a/marked/Rel-11/43_series/43901/16152cf1d84aea10848758f51a91ff6a_img.jpg b/marked/Rel-11/43_series/43901/16152cf1d84aea10848758f51a91ff6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..098d2aa54b0212d106cbd4992414eae62ecc6c1a --- /dev/null +++ b/marked/Rel-11/43_series/43901/16152cf1d84aea10848758f51a91ff6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3eb9b880434c766ce2f0a80c32fae0c69bd67608ebb36cd0437f12452a625592 +size 107550 diff --git a/marked/Rel-11/43_series/43901/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-11/43_series/43901/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a77bca1784072c1fb33e9b09739b175356a57f4f --- /dev/null +++ b/marked/Rel-11/43_series/43901/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb73e58b83b59fc3e040eae6df75dc0886bae169d05eede28ef09a452b66f5d8 +size 41955 diff --git a/marked/Rel-11/43_series/43901/73dff6b45b2b9ffd384bab3235f869af_img.jpg b/marked/Rel-11/43_series/43901/73dff6b45b2b9ffd384bab3235f869af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70ab9883f1358bc8819cbf2168477cba2921b4c9 --- /dev/null +++ b/marked/Rel-11/43_series/43901/73dff6b45b2b9ffd384bab3235f869af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45787c2770f98cd26e7a666f54add022133407603c049b5bb1516b93098d60e9 +size 56641 diff --git a/marked/Rel-11/43_series/43901/744acfe8d4e31bcf03f95714c2f6e567_img.jpg b/marked/Rel-11/43_series/43901/744acfe8d4e31bcf03f95714c2f6e567_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a559be1dedf6178425f7cf802f1433dbfdd951c4 --- /dev/null +++ b/marked/Rel-11/43_series/43901/744acfe8d4e31bcf03f95714c2f6e567_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:254437dc87e64dd08d6cb372d764e0230a21283a469f63b37e6158adc49ea38a +size 93843 diff --git a/marked/Rel-11/43_series/43901/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-11/43_series/43901/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a2ecbfe32083e1360661c2c4d9368e48d62f51b --- /dev/null +++ b/marked/Rel-11/43_series/43901/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe4ff9b6df304d18eec0336074e456326039c5e5847aed27148f609655ca0d04 +size 49941 diff --git a/marked/Rel-11/43_series/43901/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-11/43_series/43901/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..292909a301ede9afc31c08ba1428bc65114f8e75 --- /dev/null +++ b/marked/Rel-11/43_series/43901/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8de4452e403d2e405a749ddd08599cd1e6bc9fc999f07eccdda9a4af67ed13a1 +size 57598 diff --git a/marked/Rel-11/43_series/43901/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg b/marked/Rel-11/43_series/43901/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ee9ee74eb14afefebee36a9328ebcc9d8756e8a --- /dev/null +++ b/marked/Rel-11/43_series/43901/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e962fd4c1ffc879f55d1d10949f3801d06458ee5493437eb3902456241910a9 +size 127146 diff --git a/marked/Rel-11/43_series/43901/a51105b2031bad93b818b82f071c6add_img.jpg b/marked/Rel-11/43_series/43901/a51105b2031bad93b818b82f071c6add_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc18a4ad2b42d2326fae058106ff40d5383cb123 --- /dev/null +++ b/marked/Rel-11/43_series/43901/a51105b2031bad93b818b82f071c6add_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cab1c697bc73c79836197fc96fada15f3ba888eb8c3dfa707b894f47293c9c51 +size 50801 diff --git a/marked/Rel-11/43_series/43901/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/Rel-11/43_series/43901/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0027bd6463c83d14ba957884147689a82d914a7e --- /dev/null +++ b/marked/Rel-11/43_series/43901/bd671b21db63e6fdb2196e9b18502aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:baf713ba0cd9aa181e1afa8fd5e2ffa64179ed5d51643399b71a078ec6000d63 +size 155854 diff --git a/marked/Rel-11/43_series/43901/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-11/43_series/43901/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38d0d897b3de2834f8f41d081242901cb96f98b3 --- /dev/null +++ b/marked/Rel-11/43_series/43901/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83992671420d17165f82bb5361701a6ab6031018f82c4b63ae428dff98aae444 +size 47252 diff --git a/marked/Rel-11/43_series/43901/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-11/43_series/43901/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..adfa9c36b740d5c9f2c280c12571fbfd8f507cc3 --- /dev/null +++ b/marked/Rel-11/43_series/43901/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa92263ab429bce2649fea969094428a55f19df987b3dfe7e366c0fd89609c82 +size 51354 diff --git a/marked/Rel-11/43_series/43901/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-11/43_series/43901/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d8798ef7f87cbdc7a76de33dd225c328a16fd47 --- /dev/null +++ b/marked/Rel-11/43_series/43901/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e1ddf110ee19b0042443ebb188dc4af86e642ff6e1c5b76e36a4da9f496c85b +size 62231 diff --git a/marked/Rel-11/43_series/43901/raw.md b/marked/Rel-11/43_series/43901/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4814ff7ba312f69b68f37d275320ba5ce28b2f11 --- /dev/null +++ b/marked/Rel-11/43_series/43901/raw.md @@ -0,0 +1,1126 @@ + + + + + + +# Contents + +| | | +|-----------------------------------------------------------------|----| +| Foreword ..... | 5 | +| Introduction ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 7 | +| 4 Assumed high level requirements ..... | 9 | +| 5 Study results..... | 9 | +| 5.1 Architecture..... | 9 | +| 5.1.1 Architecture for generic access interface..... | 9 | +| 5.1.1.1 Functional architecture ..... | 9 | +| 5.1.1.2 Functional entities..... | 10 | +| 5.1.1.2.1 Mobile Stations (MS)..... | 10 | +| 5.1.1.2.2 Generic Access Network Controller (GANC) ..... | 10 | +| 5.1.1.3 Interfaces..... | 11 | +| 5.1.1.3.1 A/Gb interfaces ..... | 11 | +| 5.1.1.3.2 Up interface..... | 11 | +| 5.1.1.3.3 Wm interface..... | 11 | +| 5.1.1.4 High level description of generic access..... | 11 | +| 5.1.2 Signalling flows..... | 11 | +| 5.1.2.1 Registration for generic access ..... | 11 | +| 5.1.2.2 Deregistration..... | 13 | +| 5.1.3 Mobile originated call flow ..... | 14 | +| 5.1.4 Mobile terminated call flow ..... | 16 | +| 5.1.5 GPRS procedures..... | 17 | +| 5.1.5.1 GAN-GRR user data transport channel ..... | 17 | +| 5.1.5.2 GPRS user data transport procedures ..... | 17 | +| 5.1.5.3 GPRS signalling and SMS transport procedures ..... | 17 | +| 5.1.5.4 Packet paging for GPRS data service ..... | 17 | +| 5.1.5.5 Packet paging for CS domain service..... | 18 | +| 5.1.5.6 GPRS Suspend procedure..... | 18 | +| 5.1.5.7 GPRS Resume procedure..... | 18 | +| 5.2 Protocol aspects..... | 18 | +| 5.2.1 New Generic Layer..... | 18 | +| 5.2.1.1 CS domain signalling plane ..... | 18 | +| 5.2.1.2 CS domain user plane ..... | 20 | +| 5.2.1.3 PS domain signalling plane..... | 21 | +| 5.2.1.4 PS domain user plane..... | 22 | +| 5.2.2 Existing protocols..... | 23 | +| 5.2.2.1 Standard 3GPP protocols ..... | 23 | +| 5.2.2.1.1 Short Message Service ..... | 23 | +| 5.2.2.1.2 GSM SMS services ..... | 24 | +| 5.2.2.1.3 GPRS SMS services ..... | 24 | +| 5.2.2.1.4 Supplementary services..... | 24 | +| 5.2.2.2 Standard IP-based protocols ..... | 24 | +| 5.3 Security mechanisms..... | 24 | +| 5.3.1 Security levels ..... | 24 | +| 5.3.2 Up interface security..... | 25 | +| 5.4 Multi-mode terminal operation ..... | 25 | +| 5.4.1 Mechanism of mode selection in multi-mode terminals ..... | 26 | +| 5.4.2 PLMN selection..... | 26 | +| 5.4.3 Re-selection between GERAN/UTRAN and GAN modes ..... | 27 | +| 5.4.3.1 Rove-in (from GERAN/UTRAN to GAN)..... | 27 | + +| | | | +|-----------|-------------------------------------------------------------------------------------|----| +| 5.4.3.2 | Rove-out (from GAN to GERAN/UTRAN)..... | 27 | +| 5.4.3.3 | Ping-pong avoidance between GAN and GERAN/UTRAN ..... | 27 | +| 5.4.4 | Handovers between GAN and GERAN ..... | 28 | +| 5.4.4.1 | Cell identifiers in generic access ..... | 28 | +| 5.4.4.1.1 | GAN cell id for Location Services & billing ..... | 28 | +| 5.4.4.1.2 | GAN cell id for handover-to-GAN ..... | 29 | +| 5.4.4.2 | Handover to GAN ..... | 30 | +| 5.4.4.3 | Handover to GERAN..... | 32 | +| 5.4.4.4 | Other handover considerations ..... | 33 | +| 5.4.5 | Cell Change Order between GAN and GERAN ..... | 34 | +| 5.5 | Emergency call support in GAN ..... | 34 | +| 5.6 | Feasibility for support of services available through GERAN while in GAN mode ..... | 34 | +| 5.7 | Other considerations..... | 35 | +| 6 | Potential impacts on current specifications..... | 35 | +| 7 | Summary and conclusion ..... | 35 | +| Annex A: | Change history ..... | 36 | + +# --- Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- Introduction + +This document captures the results of the feasibility study of enabling generic access to A/Gb interface using alternate access means such as ADSL, Cable, Bluetooth, etc. Mobile stations obtain services from the GSM core network using such generic access means rather than through the traditional GERAN radio interface. The goal is to ensure no impact to the current A/Gb interface specifications. + +# --- 1 Scope + +This document studies the feasibility of generic access to A/Gb interface. Specific areas of study are: + +- Architecture to enable generic access. +- Access interface protocols required to provide connectivity to A/Gb interface and GSM/GPRS services. +- Security mechanisms to support generic access architecture. +- Determining feasibility for support of services currently supported through GERAN. + +The focus of the study shall be on establishing the feasibility for supporting generic access in the home network case, while also identifying issues with extending the solution to the roaming scenarios. + +# --- 2 References + +The following documents contain provisions, which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TS 22.011: "Service accessibility". +- [2] 3GPP TS 23.234: "3GPP system to Wireless Local Area Network (WLAN) interworking; System description". +- [3] 3GPP TS 26.103: "Speech codec list for GSM and UMTS". +- [4] ITU-T Recommendation V.110: "Support by an ISDN of data terminal equipments with V-Series type interfaces". +- [5] IETF RFC 791: "Internet Protocol". +- [6] IETF RFC 793: "Transmission Control Protocol". +- [7] IETF RFC 2406: "IP Encapsulating Security Payload (ESP)". +- [8] IKEv2 +- [9] EAP SIM +- [10] IPSec NAT +- [11] IETF RFC 768: "User Datagram Protocol". +- [12] IETF RFC 3550: "A Transport Protocol for Real-Time Applications". +- [13] 3GPP TS 33.234: "3G security; Wireless Local Area Network (WLAN) interworking security". +- [14] IETF RFC 2406: " IP Encapsulating Security Payload (ESP)". +- [15] 3GPP TS 23.122: "Non-Access-Stratum functions related to Mobile Station (MS) in idle mode". + +# 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply. + +**Generic Access Network:** an access network providing access to A/Gb interfaces using broadband IP network. + +**Generic Access Network Controller:** the network node that connects to the MSC and SGSN via the A-interface and Gb interface respectively and mimics the functionality of the GERAN BSS. + +**Roving:** the action of re-selection between 3GPP access technology and GAN for a mobile station in idle mode. + +**Rove in:** the mobile station reseleks from GERAN/UTRAN to GAN. + +**Rove out:** the mobile station reseleks from GAN to GERAN/UTRAN. + +**Handover:** a mobile station engaged in a call moves between GERAN/UTRAN and GAN. + +**Handover in:** the mobile station moves from GERAN/UTRAN to GAN. + +**Handover out:** the mobile station moves from GAN to GERAN/UTRAN. + +**Seamless:** free from noticeable transitions (i.e., no end-user action is required; speech interruptions are short; service interruptions are short; incoming calls are not missed; packet sessions are maintained; services work identically). + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| A | GSM A Interface : the A interface is located between the MSC (Mobile service Switching Centre) and the BSS (Base station system or radio Sub-System). | +| Gb | GSM Gb Interface : the Gb interface connects the Base Station System (BSS) to the Serving GPRS Support Node (SGSN) | +| Up | Interface between MS and GAN | +| Wm | Reference point between a Packet Data Gateway and a 3GPP AAA Server or 3GPP AAA proxy | + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|--------|----------------------------------------------------| +| A-GPS | Assisted-GPS | +| AAA | Authentication, Authorisation and Accounting | +| ADSL | Asymmetric Digital Subscriber Line | +| ARFCN | Absolute Radio Frequency Channel Number | +| BCCH | Broadcast Control CHannel | +| BSIC | Base transceiver Station Identity Code | +| BSS | Base Station Subsystem | +| BSSAP | Base Station Subsystem Application Part | +| BSSGP | Base Station Subsystem GPRS Protocol | +| BSSMAP | Base Station Subsystem Management Application Part | +| CBS | Cell Broadcast Service | +| CC | Call Control | +| CGI | Cell Global Identity | +| CI | Cell Identity | +| CM | Connection Management | +| CN | Core Network | +| CS | Circuit Switched | +| DSL | Digital Subscriber Line | +| DTAP | Direct Transfer Application Part | +| DTM | Dual Transfer Mode | + +| | | +|-------|----------------------------------------------------------| +| ESP | Encapsulating Security Payload | +| FFS | For Further Study | +| GAN | Generic Access Network | +| GANC | Generic Access Network Controller | +| GERAN | GSM EDGE Radio Access Network | +| GMM | GPRS Mobility Management | +| GMMRR | GPRS Mobility Management Radio Resource | +| GRR | GPRS Radio Resource | +| HLR | Home Location Register | +| HO | Handover | +| HPLMN | Home Public Land Mobile Network | +| HTTP | Hyper Text Transfer Protocol | +| IMS | IP Multimedia Subsystem | +| IMSI | International Mobile Subscriber Identity | +| IP | Internet Protocol | +| L1 | Layer 1 (physical layer) | +| LA | Location Area | +| LA | Location Area Identity | +| LCS | Location Services | +| LLC | Logical Link Control | +| MAC | Medium Access Control (protocol layering context) | +| MBMS | Multimedia Broadcast and Multicast Service | +| MM | Man Machine | +| MMI | Man Machine Interface | +| MMS | Multimedia Messaging Service | +| MO | Mobile Originated | +| MS | Mobile Station | +| MSC | Mobile Switching Centre | +| MVNO | Mobile Virtual Network Operator | +| NACC | Network Assisted Cell Change | +| NAS | Non-Access Stratum | +| NC2 | Network Control mode 2 | +| OTDOA | Observed Time Difference Of Arrival (positioning method) | +| PCM | Pulse Code Modulation | +| PDP | Packet Data Protocol | +| PDU | Protocol Data Unit | +| PLMN | Public Land Mobile Network | +| PS | Packet Switched | +| RAN | Radio Access Network | +| RR | Radio Resources | +| RRC | Radio Resource Control | +| RTCP | Real-Time Transport Control Protocol | +| RTP | Real Time Protocol | +| SAP | Service Access Point | +| SAPI | Service Access Point Identifier | +| SCCP | Signalling Connection Control Part | +| SGW | Security Gateway | +| SGSN | Serving GPRS Support Node | +| SID | Silence Descriptor | +| SIM | GSM Subscriber Identity Module | +| SM | Session Management | +| SMS | Short Message Service | +| SS | Supplementary Service | +| SSL | Secure Sockets Layer | +| TBF | Temporary Block Flow | +| TCP | Transmission Control Protocol | +| TFO | Tandem Free Operation | +| TLLI | Temporary Logical Link Identity | +| TMSI | Temporary Mobile Subscriber Identity | +| TrFO | Transcoding Free Operation | +| UDP | User Datagram Protocol | +| UNC | Universal Naming Convention | + +| | | +|-------|--------------------------------------------| +| UTRAN | Universal Terrestrial Radio Access Network | +| VBS | Voice Broadcast Service | +| VGCS | Voice Group Call Service | +| VPLMN | Visited Public Land Mobile Network | + +# --- 4 Assumed high level requirements + +This clause summarizes the various assumed requirements for the feasibility study, when providing generic access to A/Gb interfaces: + +- GAN interfaces to the core network shall use existing standard A interface to the MSC and Gb interface to the SGSN. Non-access stratum (NAS) protocols shall not be impacted. +- GAN shall reuse the existing GERAN identifiers toward the core network. +- GAN should support all telecommunication services supported using the A/Gb interfaces. +- GAN shall be able to operate over existing generic IP access networks (e.g. Cable, DSL, etc.). GAN-specific functionality shall not be required in the generic IP access network. +- Multi-mode terminals shall be able to perform automatic roving between GERAN/UTRAN and GAN, subject to the policies of the operator. +- Multi-mode terminals shall be able to perform seamless handover between GERAN/UTRAN and GAN, subject to the policies of the operator. +- PLMN selection and mechanisms for the avoidance of ping-pong between GERAN/UTRAN and GAN modes shall follow the principles enunciated in 3GPP TS 22.011. +- The home operator providing GAN service shall control access to Generic Access in all scenarios, including roaming. +- GAN shall provide security at least as good as GERAN for all traffic between mobile station and GANC. This includes support of bilateral authentication and encryption of all signalling and user plane traffic between mobile station and GANC. +- GAN should not require any change to existing standards e.g. the behaviour of MS in GERAN. Non-GAN capable MSs shall not be impacted due to GAN deployment. +- GAN shall be easily scaled with increasing users and traffic. It should efficiently use the resources of the generic IP access network. +- Existing charging mechanisms should be used for GAN. + +# --- 5 Study results + +## 5.1 Architecture + +### 5.1.1 Architecture for generic access interface + +#### 5.1.1.1 Functional architecture + +An option for the Generic Access Network architecture is illustrated below. + +![Figure 5.1.1.1.1: GAN Functional Architecture diagram. The diagram shows the functional architecture of a GAN. On the left, a Mobile Station (MS) is connected to a Generic IP Access Network. The MS connects to the Generic IP Access Network via an Up interface. The Generic IP Access Network connects to the Generic Access Network Controller (GANC) via an Up interface. The GANC contains a Security Gateway (SGW). The GANC is connected to the HPLMN/VPLMN via several interfaces: A (to MSC), Gb (to SGSN), Wm/Wg (to AAA Proxy/Server), and Wd (to HLR). The AAA Proxy/Server is connected to the HLR via a D'/Gr' interface. The HPLMN/VPLMN is shown as a dashed box containing the MSC, SGSN, AAA Proxy/Server, and HLR. A dashed line indicates that the AAA Proxy/Server is out of scope. The HPLMN (roaming case) is indicated by a downward arrow from the Wd interface.](e6df2733626a85205c1db682e6259c46_img.jpg) + +MS Mobile Station +GANC GAN Controller +SGW Security Gateway + +----- Out of Scope + +HPLMN (roaming case) + +Figure 5.1.1.1.1: GAN Functional Architecture diagram. The diagram shows the functional architecture of a GAN. On the left, a Mobile Station (MS) is connected to a Generic IP Access Network. The MS connects to the Generic IP Access Network via an Up interface. The Generic IP Access Network connects to the Generic Access Network Controller (GANC) via an Up interface. The GANC contains a Security Gateway (SGW). The GANC is connected to the HPLMN/VPLMN via several interfaces: A (to MSC), Gb (to SGSN), Wm/Wg (to AAA Proxy/Server), and Wd (to HLR). The AAA Proxy/Server is connected to the HLR via a D'/Gr' interface. The HPLMN/VPLMN is shown as a dashed box containing the MSC, SGSN, AAA Proxy/Server, and HLR. A dashed line indicates that the AAA Proxy/Server is out of scope. The HPLMN (roaming case) is indicated by a downward arrow from the Wd interface. + +**Figure 5.1.1.1.1: GAN Functional Architecture** + +#### 5.1.1.2 Functional entities + +##### 5.1.1.2.1 Mobile Stations (MS) + +The MS contains a new functional block to access a generic access network (GAN). + +##### 5.1.1.2.2 Generic Access Network Controller (GANC) + +The Generic Access Network Controller (GANC) appears to the core network as a GERAN base station subsystem (BSS). This entity mimics the role of the BSC in the GERAN architecture as seen from the perspective of the A/Gb interface. Thus the CN to which the GANC is connected to, is unaware of the different access mechanism being supported by the GANC compared to the BSC. A generic IP access network provides connectivity between the MS and the GANC. + +The functionality provided by the GANC includes the following: + +- User plane circuit switched services: +Inter-working circuit switched bearers over Up interface to circuit switched bearers over A-interface, including transcoding voice to/from the MS to PCM voice from/to the MSC (when TFO/TrFO features are not being utilized). +- User plane packet switched services: +Inter-working data transport channels over Up interface to packet flows over Gb interface +- Control plane functionality + - Security Gateway (SGW) for the set-up of secure tunnel with MS for mutual authentication, encryption and data integrity + - Registration for GAN service access and providing system information + - Set-up of GAN bearer paths for CS and PS services. This includes establishment, management, and teardown of signalling and user plane bearers between the MS and the GANC. + - GAN functions equivalent to GSM RR and GPRS RLC such as for paging and handovers. + - Transparent transfer of L3 messages between the MS and core network. + +NOTE: The AAA server is out of scope of the current study. It is used to authenticate the MS when it first sets up a secure tunnel to the GAN, specifically to the SGW. + +#### 5.1.1.3 Interfaces + +##### 5.1.1.3.1 A/Gb interfaces + +The GAN co-exists with the GERAN and interconnects to the core network via the same interfaces used by a standard GERAN BSS network element: + +- GSM A-interface for circuit switched services + +No changes are seen necessary to the A interface protocols. + +- GPRS Gb-interface for packet services + +No changes are seen necessary to the Gb interface protocols. + +##### 5.1.1.3.2 Up interface + +A single new interface, the Up interface, is defined between the GANC and the MS. + +##### 5.1.1.3.3 Wm interface + +The Wm interface is used between the GANC-SGW and AAA server, as defined by 3GPP TS 23.234. The Wm interface is out of scope of the current study. + +#### 5.1.1.4 High level description of generic access + +The following provides a general outline for how an MS accesses a generic access network which in turn is connected to the core network through the A/Gb interfaces, using the proposed GAN functional architecture: + +- 1 The MS shall first setup a secure tunnel over the new access interface Up, with the GANC-SGW. The identity of the GANC and its SGW, in terms of the IP address or equivalent shall be made known to the MS through any one of various mechanisms, such as provisioning in the terminal, etc. The MS shall be authenticated and authorized using SIM credentials, via the AAA server. +- 2 The MS shall then setup a signalling connection over the Up with the GANC and register with the GAN. During GAN registration, the MS provides information regarding its identity, location and capabilities. If the GAN accepts the registration, it provides system information to the MS, which is required for obtaining all the supported services and potentially handover functionality. The stored MS identity is used by the GAN, to support unicast paging using the Up signalling connection to the MS and other functions. +- 3 At this point, the MS can switch from 3GPP mode to GAN mode. Layer 3 messages (MM, CC, CM, SS) are transparently transferred to the core network through the signalling connection over the Up interface. When needed, the GANC and MS set up CS-domain and PS-domain user plane bearers over the GAN. GANC also provides additional functions to support handovers, etc. + +NOTE: 3GPP mode refers to the mode wherein the physical layer specification for that mode is part of 3GPP specifications, e.g. GERAN L1 and UTRAN L1. + +Identification by the MS of availability of generic access is out of scope of the current study. + +### 5.1.2 Signalling flows + +This clause explains how typical functionality such as MO, MT calls, paging, etc may be accomplished for the identified architecture options. + +#### 5.1.2.1 Registration for generic access + +The GAN Registration procedure is performed between the MS and the GANC. It serves the following functions: + +- It informs the GANC that the MS is now connected through a generic IP access network and is available at a particular IP address. The GANC maintains the registration context for the purposes of (for example) mobile-terminated calling. + +NOTE: The feasibility study is limited to cases wherein the IP address of the MS remains the same throughout the lifetime of the current registration to the GAN. + +- It provides the MS with the operating parameters associated with the GAN service. The "GSM System Information" message content that is applicable to the GAN cell is delivered to the MS during the GAN registration process. This enables the MS to switch to GAN mode, and following the Registration procedure trigger NAS procedures with the core network (such as Location/Routing Area Update, mobile originated calls, mobile terminated calls, etc.). + +This procedure is applicable only if the MS is operating in GAN-only, GAN-preferred or GERAN/UTRAN-preferred modes. + +In all other cases, the MS will not execute this procedure, and since it will not have successfully registered with a GANC, all subsequent GAN procedures will also not be executed by the MS. + +The Registration procedures consist of the following steps: + +- Attaching to a generic IP access network +- Registration with a GANC + +During the registration process, the MS can be redirected to another GANC, for reasons such as: + +- MS provided GERAN cell information. For example, the "appropriate" GANC is the one that is a neighbour of the GERAN cell the MS is currently located in, where "neighbour cells" are defined in clause 5.2.1. +- Load balancing, operator policy, roaming agreements, etc. + +The GAN may also reject the MS's request for registration. + +If no GSM coverage is available when an MS connects to the GANC, then the GANC may not reliably be able to determine the location of the MS for the purposes of assigning the MS to the appropriate GANC. The GANC functionality should permit the operator to determine the service policy in this case; e.g., the operator could provide GAN service to the user with certain limitations or deny GAN service. + +The MS sets up a secure connection to the GANC, and executes the GAN-RR Registration procedures: + +- The MS sends a GAN-RR Register Request message that carries the MS identity (IMSI), GERAN cell information (either current camping GSM CGI, or LAI of last cell where the MS successfully registered) and generic IP access network point of attachment. +- The MS additionally provides information about whether there is on-going CS connection in GERAN at the time of registration. This permits the GANC to redirect the MS to an appropriate GANC for enabling seamless handovers. +- If this GANC is the appropriate GANC, it returns a GAN-RR Register Accept message, which contains "System Information" for the cell represented by the GANC, including cell description, LAI and CI. The GANC may also omit information providing the identity of the GAN cell, in order to prohibit handovers being triggered from GERAN. +- If this GANC is not the appropriate GANC, it returns a GAN-RR Register Redirect message, using the GERAN cell information provided by the MS to identify the appropriate GANC (FQDN or IP address) and its associated SGW. In this case, the MS will repeat this Registration procedure with the redirected GANC. +- Alternately, the GANC may return a GAN-RR Register Reject message thereby denying GAN service to the MS. + +The Registration procedure can support the Access Class functionality by providing the necessary system information in the Registration message to the MS. + +The GAN Registration Update procedure allows the MS to update information in the GANC regarding changes in the identity of the overlapping GERAN cell or changes in the generic IP access network point of attachment, by sending a GAN-RR Register Update message to the GANC carrying the updated information. This may result in the MS being redirected to another serving GANC, or being denied service e.g. due to operator policy. + +The GAN Registration Update procedure also allows the GANC to update the GAN system information in the MS, if needed, by sending a GAN-RR Register Update message to the MS carrying the updated information. + +#### 5.1.2.2 Deregistration + +The GAN-RR Deregistration procedure allows the MS to explicitly inform the GANC that it is leaving GAN mode (e.g. when it detaches from the generic IP access network), by sending a GAN-RR Deregister message to the GANC, allowing the GANC to free resources that it assigned to the MS. The GANC also supports "implicit GAN deregistration", when the secure connection to the MS is abruptly lost. + +The GANC can also autonomously release the MS registration context, and send a GAN-RR Deregister message to the MS. Alternately, the GANC can implicitly deregister the MS by closing the secure connection with the MS. + +### 5.1.3 Mobile originated call flow + +![Sequence diagram of mobile originated call flow between MS and GANC.](bd671b21db63e6fdb2196e9b18502aac_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + Note right of GANC: Complete Layer 3 Info + MS->>GANC: 1. GAN-RR UL DIRECT TRANSFER (CM Service Request) + GANC->>GANC: 2. Complete Layer 3 Info + GANC-->>MS: 3. Authentication + GANC->>MS: 4. Cipher-Mode Command + MS->>GANC: 5. GAN-RR CIPHERING MODE COMMAND + GANC->>GANC: 7. Cipher-Mode Complete Command + MS->>GANC: 6. GAN-RR CIPHERING MODE COMPLETE + GANC->>MS: 8. GAN-RR DL DIRECT TRANSFER (CM Service Accept) + MS->>GANC: 9. GAN-RR UL DIRECT TRANSFER (Setup) + GANC->>GANC: 10. GAN-RR DL DIRECT TRANSFER (Call Proceeding) + GANC->>MS: 11. Assignment Request + MS->>GANC: 12. GAN-RR ACTIVATE CHANNEL + MS->>GANC: 13. Uplink user plane RTP Stream + MS->>GANC: 14. GAN-RR ACTIVATE CHANNEL ACK + MS->>GANC: 15. Downlink user plane RTP Stream + GANC->>GANC: 16. Assignment Complete + MS->>GANC: 17. GAN-RR ACTIVATE CHANNEL COMPLETE + GANC->>MS: 18. GAN-RR DL DIRECT TRANSFER (Alerting) + GANC->>MS: 19. GAN-RR DL DIRECT TRANSFER (Connect) + MS->>GANC: 20. GAN-RR UL DIRECT TRANSFER (Connect Ack) + Note right of GANC: VOICE TRAFFIC + MS-->>GANC: 21. VOICE TRAFFIC + +``` + +The sequence diagram illustrates the mobile originated call flow between the Mobile Station (MS) and the GANC. The process begins with the MS sending a GAN-RR UL DIRECT TRANSFER (CM Service Request) to the GANC. The GANC responds with 'Complete Layer 3 Info' (self-call), followed by an 'Authentication' message to the MS. The GANC then sends a 'Cipher-Mode Command' to the MS, which replies with 'GAN-RR CIPHERING MODE COMMAND'. The GANC completes the cipher mode with a self-call ('Cipher-Mode Complete Command') and then sends 'GAN-RR DL DIRECT TRANSFER (CM Service Accept)' to the MS. The MS responds with 'GAN-RR UL DIRECT TRANSFER (Setup)'. The GANC sends 'GAN-RR DL DIRECT TRANSFER (Call Proceeding)' (self-call) and an 'Assignment Request' to the MS. The MS activates the channel with 'GAN-RR ACTIVATE CHANNEL' and starts the 'Uplink user plane RTP Stream'. The MS sends 'GAN-RR ACTIVATE CHANNEL ACK' to the GANC and starts the 'Downlink user plane RTP Stream'. The GANC completes the assignment with a self-call ('Assignment Complete'). The MS sends 'GAN-RR ACTIVATE CHANNEL COMPLETE' to the GANC. The GANC then sends 'GAN-RR DL DIRECT TRANSFER (Alerting)' and 'GAN-RR DL DIRECT TRANSFER (Connect)' to the MS. The MS responds with 'GAN-RR UL DIRECT TRANSFER (Connect Ack)'. Finally, 'VOICE TRAFFIC' is established between the MS and the GANC. + +Sequence diagram of mobile originated call flow between MS and GANC. + +**Figure 5.1.3.1: Mobile originated speech call** + +The description of the procedure in this sub-clause assumes the MS is in GAN mode i.e. it has successfully registered with the GANC and GAN-RR is the serving RR entity in the MS. + +- 1) Upon request from the user to originate a call, the MS sends the *CM Service Request* to the GANC in the GAN-RR UL DIRECT TRANSFER. + +- 2) The GANC establishes an SCCP connection to the CN. The GANC then forwards the *CM Service Request* to the CN using the *Complete Layer 3 Information*. Subsequent layer-3 messages between mobile station and core network will be sent between GANC and CN via DTAP. +- 3) The CN may optionally authenticate the MS using standard GERAN authentication procedures. +- 4) The CN may optionally update the ciphering parameters in the GANC using the *Cipher-Mode Command*. +- 5) The GANC signals the permitted ciphering algorithms to the MS using the GAN-RR CIPHERING-MODE COMMAND. These algorithms do not apply for GAN. The MS stores this information for possible future use after a handover to GERAN. +- 6) The MS signals the selected ciphering algorithm in the GAN-RR CIPHERING-MODE COMPLETE message. +- 7) The GANC signals the selected ciphering algorithm to the CN using *Cipher-Mode Complete*. +- 8) The CN sends the *CM service accept* message in the GAN-RR DL DIRECT TRANSFER to the MS. +- 9) The MS sends the *Setup* message providing details on the call to the CN and its bearer capability and supported codecs. This message is contained within the GAN-RR UL DIRECT TRANSFER. +- 10) The CN indicates it has received the call setup and it will accept no additional call-establishment information using the GAN-RR DL DIRECT TRANSFER to convey the *Call Proceeding* indication to the MS. +- 11) The CN requests the GANC to assign call resources using *Assignment Request*. +- 12) The GANC sends the GAN-RR ACTIVATE CHANNEL to the MS including bearer path setup information such as: + - channel mode + - Multi-rate codec configuration + - the UDP port & the IP address for the uplink stream + - the voice sample size + - the cipher mode (for use in case of subsequent handover to GERAN) +- 13) The MS establishes the RTP path to the GANC. MS optionally sends idle RTP/UDP packets to the GANC but has not connected the user to the audio path. +- 14) The MS sends the GAN-RR ACTIVATE CHANNEL ACK to the GANC indicating the UDP port and IP address for the downlink stream. +- 15) The GANC establishes the downlink RTP path between itself and the MS. The GANC may start sending idle RTP/UDP packets to the MS. +- 16) The GANC signals to the CN that the call resources have been allocated by sending an *Assignment Complete* message. +- 17) The GANC signals the completion of the bearer path to the MS with the GAN-RR ACTIVATE CHANNEL COMPLETE message. An end-to-end audio path now exists between the MS and the CN. The MS can now connect the user to the audio path. +- 18) The CN signals that the called subscriber's phone is ringing, via the *Alerting* message. If the MS has not connected the audio path to the user, it shall generate ring back to the calling party. Otherwise, the network-generated ring back will be returned to the calling party. +- 19) The CN signals that the called party has answered, via the *Connect* message. It connects the user to the audio path. If the mobile station is generating ring back, it stops and connects the user to the audio path. +- 20) The MS sends the *Connect ACK* in response, and the two parties are connected for the voice call. +- 21) Bi-directional voice traffic flows between the MS and CN through the GANC. + +### 5.1.4 Mobile terminated call flow + +![Sequence diagram of mobile terminated call flow between MS, GANC, and CN.](16152cf1d84aea10848758f51a91ff6a_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant CN + + Note right of CN: 1. Paging Request + CN->>GANC: 1. Paging Request + Note left of GANC: 2. GAN-RR PAGING REQUEST + GANC->>MS: 2. GAN-RR PAGING REQUEST + Note left of MS: 3. GAN-RR PAGING RESPONSE + MS->>GANC: 3. GAN-RR PAGING RESPONSE + Note right of GANC: 4. Complete Layer 3 Info + GANC->>CN: 4. Complete Layer 3 Info + Note right of CN: 5. Authentication + CN-->>MS: 5. Authentication + Note right of CN: 6. Ciphering Configuration + CN-->>MS: 6. Ciphering Configuration + Note right of CN: 7. GAN-RR DL DIRECT TRANSFER (Setup) + CN->>GANC: 7. GAN-RR DL DIRECT TRANSFER (Setup) + Note left of GANC: 8. GAN-RR UL DIRECT TRANSFER (Call Confirmed) + GANC->>MS: 8. GAN-RR UL DIRECT TRANSFER (Call Confirmed) + Note right of CN: 9. RTP stream setup + CN-->>GANC: 9. RTP stream setup + Note right of GANC: Assignment Procedure + GANC-->>MS: Assignment Procedure + Note right of CN: 10. GAN-RR UL DIRECT TRANSFER (Alerting) + CN->>GANC: 10. GAN-RR UL DIRECT TRANSFER (Alerting) + Note right of CN: 11. GAN-RR UL DIRECT TRANSFER (Connect) + CN->>GANC: 11. GAN-RR UL DIRECT TRANSFER (Connect) + Note left of GANC: 12. GAN-RR DL DIRECT TRANSFER (Connect Ack) + GANC->>MS: 12. GAN-RR DL DIRECT TRANSFER (Connect Ack) + Note right of CN: 13. VOICE TRAFFIC + CN-->>MS: 13. VOICE TRAFFIC + +``` + +Sequence diagram of mobile terminated call flow between MS, GANC, and CN. + +**Figure 5.1.4.1: Mobile terminated speech call** + +The description of the procedure in this sub-clause assumes the MS is in GAN mode i.e. it has successfully registered with the GANC and GAN-RR is the serving RR entity in the MS. + +- 1) A mobile-terminated call arrives at the CN. The CN sends a *Paging Request* to the GANC identified through the last *Location Update* received by it and includes the TMSI if available. The IMSI of the mobile being paged is always included in the request. +- 2) GANC identifies the MS registration context using the IMSI provided by the CN. It then pages the MS using the GAN-RR PAGING REQUEST message. The message includes the TMSI if available in the request from the CN, else it includes only the IMSI of the mobile. +- 3) The MS responds with a GAN-RR PAGING RESPONSE including the MS Classmark and ciphering key sequence number. +- 4) The GANC establishes an SCCP connection to the CN. The GANC then forwards the paging response to the CN using the *Complete Layer 3 Information* message. +- 5) The CN may optionally authenticate the MS using standard GERAN authentication procedures. +- 6) The CN may optionally update the ciphering configuration in the MS, via the GANC, as described in steps 4-7 of the Mobile Originated calling scenario. +- 7) The CN initiates call setup using the *Setup* message sent to the MS using the GAN-RR DL DIRECT TRANSFER. + +- 8) The MS responds with *Call Confirmed* using the GAN-RR UL DIRECT TRANSFER after checking its compatibility with the bearer service requested in the *Setup* and modifying the bearer service as needed. If the *Setup* included the signal information element, the MS alerts the user using the indicated signal, else the MS alerts the user after the successful configuration of the user plane. +- 9) The CN initiates the assignment procedure with the GANC, which triggers the setup of the RTP stream (voice bearer channel) between the GANC and MS, same as steps 11-17 in MO call scenario. +- 10) The MS signals that it is alerting the user, via the *Alerting* message. The CN sends a corresponding alerting message to the calling party. +- 11) The MS signals that the called party has answered, via the *Connect* message. The CN sends a corresponding *Connect* message to the calling party and through connects the audio. The MS connects the user to the audio path. +- 12) The CN acknowledges via the *Connect Ack* message. The two parties on the call are connected on the audio path. +- 13) Bi-directional voice traffic flows between the MS and CN through the GANC. + +### 5.1.5 GPRS procedures + +#### 5.1.5.1 GAN-GRR user data transport channel + +GPRS user data transfer between MS and GANC uses a UDP-based GAN-GRR Transport Channel (identified by the IP address and UDP port at each end). The MS or GANC activates the GAN-GRR Transport Channel only when needed i.e. when the GPRS user data transfer is initiated. A timer is used to deactivate the GAN-GRR Transport Channel when no data is transmitted to or received for some period of time. + +#### 5.1.5.2 GPRS user data transport procedures + +For uplink data transfer, the MS activates the GAN-GRR Transport Channel if needed. It then encapsulates the uplink LLC PDU within the GAN-GRR UNITDATA message and forwards it to the GANC. The message includes parameters required for Gb interface procedures and TLLI as MS identifier. The GANC forwards the LLC PDU to the Core Network as per standard GPRS. + +For downlink data transfer, the Core Network sends the downlink LLC PDU that contains GPRS user data via the Gb interface. The MS is identified with the TLLI. The GANC activates the GAN-GRR Transport Channel if needed, and forwards the LLC PDU to the MS encapsulated in the GAN-GRR UNITDATA message. + +#### 5.1.5.3 GPRS signalling and SMS transport procedures + +The TCP session used for GAN-RR signalling is also used for GAN-GRR GPRS signalling and SMS transport. This TCP session is available after GAN registration, so there is no need to establish a separate connection for GPRS signalling and SMS transport. + +For uplink signalling/SMS, the MS GAN-GRR receives a request from the LLC layer to transfer an uplink GMM/SM signalling message or SMS message; e.g. this could be a GMM attach request or SM PDP context activation message. The GMM/SM signalling messages are identified with LLC SAPI 1 and SMS messages with LLC SAPI 7. The MS GAN-GRR encapsulates the LLC PDU within a GAN-GRR DATA message including the parameters that will be required for Gb interface procedures. Subsequently, the message is forwarded to the GANC, and the GANC forwards the message to the Core Network as per standard GPRS Gb procedure. + +For downlink signalling/SMS, the Core Network sends a GMM/SM signalling or SMS message to the GANC via the Gb interface as per standard GPRS; i.e. the LLC PDU may include GMM attach accept or SM PDP context activation accept message. The GANC encapsulates the received LLC PDU within a GAN-GRR DATA message that is forwarded to the MS via the existing signalling TCP connection. + +#### 5.1.5.4 Packet paging for GPRS data service + +The Core Network sends a PS page for a mobile station that is currently GPRS attached via the GAN. The paging message will include either PTMSI or IMSI as a mobile identifier. The GANC retrieves the MS registration context (based on IMSI) and forwards the corresponding GAN-GRR PS PAGE message to the MS using the TCP signalling connection. The message includes Mobile Identity IE as per standard GPRS. It will be either PTMSI if available or IMSI. + +The mobile station sends any LLC PDU to respond to the page. The uplink LLC PDU is forwarded to the GANC as described in above clauses. The GANC forwards the LLC PDU to the Core Network via the Gb interface as per standard GPRS. + +#### 5.1.5.5 Packet paging for CS domain service + +The Core Network sends a CS page for a mobile station that is currently GPRS attached via the GAN. The paging message will include either TMSI or IMSI as a mobile identifier. The GANC retrieves the MS registration context (based on IMSI) and forwards the corresponding GAN-RR Paging Request message to the MS using the TCP signalling connection. The message includes Channel Needed and Mobile Identity IEs as per standard GPRS. The Mobile Identity will be either TMSI or IMSI depending on the original BSSGP CS page. The mobile station initiates the standard CS page response procedure via the GAN. + +#### 5.1.5.6 GPRS Suspend procedure + +While transitioning to dedicated mode and if unable to support simultaneous voice and data services, the mobile station sends a GAN-GRR SUSPEND REQUEST message to the GANC to suspend downlink GPRS traffic. The request is transferred via the TCP signalling connection and includes TLLI and suspension cause parameters as per standard GPRS. The GANC initiates and completes the BSSGP GPRS suspend procedure as per standard GPRS. + +#### 5.1.5.7 GPRS Resume procedure + +If the GPRS service has been suspended while the mobile station was in the dedicated mode, it needs to be resumed when the mobile station leaves the dedicated mode. + +The Core Network sends a Clear Command message to release the resources associated with the dedicated mode procedure. The GANC responds with a Clear Complete message. Optionally, the GANC may initiate the standard BSSGP GPRS resume procedure. + +The GANC sends a GAN-RR RR RELEASE message to instruct the MS to release the RR connection. The message includes GPRS resume indication IE as per standard GSM/GPRS to indicate whether the network successfully resumed GPRS service or not. The MS replies with a GAN-RR RR RELEASE COMPLETE message and resumes GPRS service internally. Optionally, if the Core Network indicated unsuccessful resumption, the MS initiates GPRS service resumption as per standard GPRS. + +## 5.2 Protocol aspects + +This clause will capture options for any new generic access layer that will be needed to enable generic access to the A/Gb interfaces. + +### 5.2.1 New Generic Layer + +#### 5.2.1.1 CS domain signalling plane + +The Up protocol architecture in support of CS domain signalling, as well as GAN-specific signalling, is illustrated below. + +![Figure 5.2.1.1.1: Up CS domain signalling protocol architecture diagram. The diagram shows the protocol stack for the Up interface between a Mobile Station (MS) and a Mobile Switching Center (MSC) via a Generic IP Network and a GANC. The MS stack includes CC/SS/SMS, MM, GAN-RR, TCP, Remote IP, IPSec ESP, Transport IP, and Access Layers. The Generic IP Network contains Transport IP and Access Layers. The GANC stack includes GAN-RR, BSSAP, TCP, SCCP, Remote IP, IPSec ESP, MTP3, Transport IP, MTP2, Access Layers, and MTP1. The MSC stack includes CC/SS/SMS, MM, BSSAP, SCCP, MTP3, MTP2, and MTP1. Arrows indicate the flow of data between the MS and GANC, and between the GANC and MSC. The Up Interface is marked between the MS and GANC, and the A interface is marked between the GANC and MSC.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +Figure 5.2.1.1.1: Up CS domain signalling protocol architecture diagram. The diagram shows the protocol stack for the Up interface between a Mobile Station (MS) and a Mobile Switching Center (MSC) via a Generic IP Network and a GANC. The MS stack includes CC/SS/SMS, MM, GAN-RR, TCP, Remote IP, IPSec ESP, Transport IP, and Access Layers. The Generic IP Network contains Transport IP and Access Layers. The GANC stack includes GAN-RR, BSSAP, TCP, SCCP, Remote IP, IPSec ESP, MTP3, Transport IP, MTP2, Access Layers, and MTP1. The MSC stack includes CC/SS/SMS, MM, BSSAP, SCCP, MTP3, MTP2, and MTP1. Arrows indicate the flow of data between the MS and GANC, and between the GANC and MSC. The Up Interface is marked between the MS and GANC, and the A interface is marked between the GANC and MSC. + +**Figure 5.2.1.1.1: Up CS domain signalling protocol architecture** + +The salient features of this part of the Up interface, with respect to the CS domain, are as follows: + +- GSM protocols, MM and above, are carried transparently between the MS and MSC. This allows the MS to obtain all GSM services that it receives through a GSM BSS, through the GAN. +- GSM-RR protocol is replaced with a GAN-RR protocol. The generic IP access network presents different characteristics from that of the GSM radio link, so the GAN-RR protocol is designed to adapt to these characteristics. +- GAN-RR is transported over TCP between MS and GANC, which provides reliable transport of signalling messages. The underlying IPSec layer provides mutual authentication, encryption and data integrity. +- The GANC, acting like a BSC, terminates the GAN-RR protocol and inter-works it to the A-interface using BSSAP messaging. + +One potential realization of this architecture in the MS is illustrated in more detail below: + +![MS CS domain signalling architecture diagram showing layers from Connection Management (CM) down to GSM Baseband, with GAN-RR and GSM RR components.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +The diagram illustrates the MS CS domain signalling architecture. At the top, the Connection Management (CM) layer contains three sub-components: CC (Call Control), SS (Supplementary Services), and SMS (Short Message Service). These are connected via interfaces MMCC-SAP, MMSS-SAP, and MMSMS-SAP respectively to the Mobility Management (MM) layer. The MM layer connects to the RR-SAP interface, which leads to an 'Access Mode' switch. This switch can direct traffic to either the GAN-RR (GPRS Access Network Radio Resource) or the GSM RR (GSM Radio Resource) via GANGSM-SAP and GSMGAN-SAP interfaces. The GAN-RR path continues through a stack of protocols: TCP, Remote IP, IPSec ESP, Transport IP, and Access Layers. The GSM RR path continues through LAPDm and then to the GSM Baseband layer. + +MS CS domain signalling architecture diagram showing layers from Connection Management (CM) down to GSM Baseband, with GAN-RR and GSM RR components. + +Figure 5.2.1.1.2: MS CS domain signalling architecture + +The figure above illustrates the salient features of the MS architecture which are as follows: + +- The RR-SAP interface to the GSM-MM layer is preserved identically for both GSM and GAN access +- An access mode switch is provided to switch between GSM and GAN modes +- GAN-RR peers with GSM-RR to provide coordination for roving and handover + +#### 5.2.1.2 CS domain user plane + +The Up protocol architecture in support of CS domain user plan is below. + +![Up CS domain user plane protocol architecture diagram showing the flow of data from MS through Generic IP Network, GANC, and MSC.](a51105b2031bad93b818b82f071c6add_img.jpg) + +This diagram shows the Up CS domain user plane protocol architecture. It depicts the flow of user data from the MS (Mobile Station) to the MSC (Mobile Switching Center) via a Generic IP Network and a GANC (GPRS Access Network Controller). The MS contains layers for Codec/Rate Adaptation, RTP/UDP, Remote IP, IPSec ESP, Transport IP, and Access Layers. These connect to the Generic IP Network, which has its own Transport IP and Access Layers. The data then enters the GANC, which includes a 'Transcoding/Rate Adaptation (if necessary)' block, followed by Codec/Rate Adaptation, RTP/UDP, Remote IP, IPSec ESP, Transport IP, and Access Layers. The GANC also contains 'Speech Bearer' and 'Physical Layers' components. An interface labeled 'A' connects the GANC's Speech Bearer and Physical Layers to the MSC. The MSC contains layers for IWF (if necessary), Speech Bearer, and Physical Layers. Dashed arrows indicate the mapping of protocols between the MS and the GANC across the Generic IP Network. + +Up CS domain user plane protocol architecture diagram showing the flow of data from MS through Generic IP Network, GANC, and MSC. + +Figure 5.2.1.2.1: Up CS domain user plane protocol architecture + +The salient features of the CS domain user plane of the Up interface are as follows: + +- CS domain user plane is transported over RTP/UDP between MS and GANC. The underlying IPSec layer provides mutual authentication, encryption and data integrity. +- Voice codecs are supported as per [TS 26.103] for those codecs that have IETF-defined RTP framing formats. +- CS-data is transported over RTP/UDP, by defining a new frame format to carry the TAF-TRAU (V.110-like) frames over RTP.. +- TTY is transported using CTM over GSM codec over RTP/UDP. +- The GANC, acting like a BSC, terminates the CS domain user plane over RTP/UDP and inter-works it to speech bearers over the A-interface. + +#### 5.2.1.3 PS domain signalling plane + +The Up protocol architecture in support of PS domain signalling is illustrated below. + +![Figure 5.2.1.3.1: Up PS Domain Signalling Protocol Architecture. The diagram shows the protocol stack for the Up interface between a Mobile Station (MS) and a Serving GPRS Support Node (SGSN), with a GANC acting as a relay. The MS stack includes Upper Layers, LLC, GAN-GRR, TCP, Remote IP, IPSec ESP, Transport IP, and Access Layers. The GANC stack includes Relay, GAN-GRR, BSSGP, TCP, Remote IP, IPSec ESP, Network Service, Transport IP, Access Layers, and Physical. The SGSN stack includes Upper Layers, LLC, BSSGP, Network Service, and Physical. The GAN-GRR protocol is highlighted in green in the MS stack. The GANC acts as a relay between the MS and the SGSN, with the GAN-GRR protocol being terminated at the GANC and BSSGP being used on the Gb interface towards the SGSN.](73dff6b45b2b9ffd384bab3235f869af_img.jpg) + +Figure 5.2.1.3.1: Up PS Domain Signalling Protocol Architecture. The diagram shows the protocol stack for the Up interface between a Mobile Station (MS) and a Serving GPRS Support Node (SGSN), with a GANC acting as a relay. The MS stack includes Upper Layers, LLC, GAN-GRR, TCP, Remote IP, IPSec ESP, Transport IP, and Access Layers. The GANC stack includes Relay, GAN-GRR, BSSGP, TCP, Remote IP, IPSec ESP, Network Service, Transport IP, Access Layers, and Physical. The SGSN stack includes Upper Layers, LLC, BSSGP, Network Service, and Physical. The GAN-GRR protocol is highlighted in green in the MS stack. The GANC acts as a relay between the MS and the SGSN, with the GAN-GRR protocol being terminated at the GANC and BSSGP being used on the Gb interface towards the SGSN. + +**Figure 5.2.1.3.1: Up PS Domain Signalling Protocol Architecture** + +The salient features of this part of the Up interface are as follows: + +- GPRS LLC PDUs for signalling and SMS are carried transparently between the MS and SGSN. This allows the MS to obtain all GPRS services in the same way as if it were connected to a GERAN BSS. +- GPRS-RLC protocol is replaced with a GAN-GRR protocol. Given the IP packet transport characteristics over Up interface, the GPRS Temporary Block Flow (TBF) abstraction is not applicable. Instead GAN-GRR provides mechanisms to establish and teardown IP packet transport channel between MS and UNC. Therefore GAN-GRR is significantly lighter than GPRS-RLC. +- GAN-GRR is transported over TCP between MS and GANC, which provides reliable transport of signalling & SMS messages. The underlying IPSec layer provides mutual authentication, encryption and data integrity. +- The GANC, acting like a BSC, terminates the GAN-GRR protocol and inter-works it to the Gb-interface using BSSGP. + +One potential realization of this architecture in the MS is illustrated in more detail below: + +![MS PS domain protocol architecture diagram showing layers from App down to GSM Baseband, with GMM, IP, SNDPCP, and SMS at the top, and an Access Mode switch between LLC and GAN-GRR/GPRS RLC.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +The diagram illustrates the MS PS domain protocol architecture. At the top, three boxes represent 'App', 'IP', and 'SMS'. Below 'App' is 'GMM'. Below 'IP' is 'SNDPCP'. All three (GMM, SNDPCP, SMS) connect to a 'Logical Link Control (LLC)' box. Below the LLC box, two interfaces are shown: 'GMMRR-SAP' and 'GRR-SAP'. These connect to a green trapezoidal 'Access Mode' switch. Below the switch, the architecture splits into two parallel paths. The left path consists of 'GAN-GRR' (green box), which connects to a stack of 'TCP, UDP', 'Remote IP', 'IPSec ESP', 'Transport IP', and 'Access Layers'. The right path consists of 'GPRS RLC' (blue box), which connects to 'MAC' and then 'GSM Baseband'. There are two interfaces between GAN-GRR and GPRS RLC: 'GANGPRS-SAP' at the top and 'GPRSGAN-SAP' at the bottom, with arrows indicating bidirectional communication between the two RLC entities. + +MS PS domain protocol architecture diagram showing layers from App down to GSM Baseband, with GMM, IP, SNDPCP, and SMS at the top, and an Access Mode switch between LLC and GAN-GRR/GPRS RLC. + +**Figure 5.2.1.3.2: MS PS domain protocol architecture** + +The figure illustrates the salient features of the MS architecture which are as follows: + +- The GRR-SAP interface to the GPRS-LLC layer and GMMRR-SAP interface to the GPRS-GMM layer are preserved identically for both GPRS and GAN access +- An access mode switch is provided to switch between GPRS and GAN modes +- GAN-GRR peers with GPRS-RLC to provide coordination for roving and handover + +#### 5.2.1.4 PS domain user plane + +The Up PS domain user plane protocol architecture is illustrated below. + +![Figure 5.2.1.4.1: Up GPRS user plane protocol architecture diagram. The diagram shows the protocol stack for the Up interface between the MS (Mobile Station) and the SGSN (Serving GPRS Support Node). The MS stack includes IP, SNDPCP, LLC, GAN-GRR, UDP, Remote IP, IPSec ESP, Transport IP, and Access Layers. The GANC (GAN Controller) stack includes a Relay, GAN-GRR, BSSGP, UDP, Remote IP, IPSec ESP, Network Service, Transport IP, Access Layers, and Physical. The SGSN stack includes SNDPCP, LLC, BSSGP, Network Service, and Physical. Arrows indicate data flow: IP traffic goes from MS IP to SGSN IP via the GANC Relay; LLC PDUs are carried transparently between MS LLC and SGSN LLC via the GANC Relay; GAN-GRR PDUs are carried between MS GAN-GRR and GANC GAN-GRR over UDP; BSSGP messages are carried between GANC BSSGP and SGSN BSSGP; Transport IP and Access Layers are used for the connection between MS and GANC.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +Figure 5.2.1.4.1: Up GPRS user plane protocol architecture diagram. The diagram shows the protocol stack for the Up interface between the MS (Mobile Station) and the SGSN (Serving GPRS Support Node). The MS stack includes IP, SNDPCP, LLC, GAN-GRR, UDP, Remote IP, IPSec ESP, Transport IP, and Access Layers. The GANC (GAN Controller) stack includes a Relay, GAN-GRR, BSSGP, UDP, Remote IP, IPSec ESP, Network Service, Transport IP, Access Layers, and Physical. The SGSN stack includes SNDPCP, LLC, BSSGP, Network Service, and Physical. Arrows indicate data flow: IP traffic goes from MS IP to SGSN IP via the GANC Relay; LLC PDUs are carried transparently between MS LLC and SGSN LLC via the GANC Relay; GAN-GRR PDUs are carried between MS GAN-GRR and GANC GAN-GRR over UDP; BSSGP messages are carried between GANC BSSGP and SGSN BSSGP; Transport IP and Access Layers are used for the connection between MS and GANC. + +**Figure 5.2.1.4.1: Up GPRS user plane protocol architecture** + +The salient features of the PS domain user plane of the Up interface are as follows: + +- GPRS LLC PDUs carrying data, and higher layer protocols, are carried transparently between the MS and SGSN. This allows the MS to derive all GPRS services the same as if it were in a GERAN BSS. All existing GPRS applications and MMI in the MS are unchanged. +- LLC PDUs are carried over GAN-GRR from the MS to the GANC. GAN-GRR runs over UDP. The underlying IPSec layer provides mutual authentication, encryption and data integrity. GAN-GRR does not emulate the reliable transmission characteristics of GPRS RLC since it can be assumed that errors in wireless access layers (below IP) are addressed by lower layer retransmissions on a hop-by-hop basis, UDP provides a suitable transport that matches a wide range of application layer transport requirements. +- The GANC, acting like a BSC, terminates the GAN-GRR protocol and inter-works it to the Gb-interface using BSSGP. + +### 5.2.2 Existing protocols + +#### 5.2.2.1 Standard 3GPP protocols + +In case of option 1, the GAN can be designed such that the following standard 3GPP protocols are used without any modifications: + +- GSM MM, CM and higher layer protocols are used without any changes in the MS or the MSC; +- GSM voice encoding carried over IP between the MS and GANC; +- GPRS LLC and higher layer protocols are used without any changes on the MS and SGSN; +- A-interface protocols are used, without any changes, between the MSC and GANC; +- Gb-interface protocols are used, without any changes, between the SGSN and GANC; +- Wm interface protocols are used without any change between the GANC and the AAA server. + +Further, all GSM and GPRS protocols on the MS should be unaffected when they are operating over the GERAN BSS. + +##### 5.2.2.1.1 Short Message Service + +GAN provides support for both circuit switched (GSM based) and packet switched (GPRS based) SMS services. GAN-attached and GPRS enabled mobile stations will be able to send and receive GSM and GPRS SMS messages via the GAN, regardless of the GPRS class (B or C) with the restriction that the type C mobiles support only GPRS SMS messages. + +##### 5.2.2.1.2 GSM SMS services + +The GAN GSM SMS support is based on the same mechanism that is utilized for GSM mobility management and call control. On the MS side, the SMS layers (including the supporting CM sub layer functions) utilize the services of the MM layer to transfer SMS messages per standard circuit switched GSM implementation. The SM-CP protocol is effectively tunneled between the MS and the MSC, using GAN-RR messages to the GANC which interworks it to BSSAP messages. + +As with GSM mobility management and call control procedures, the secure IPSec tunnel and TCP session are used to provide secure and reliable SMS delivery over the IP network. + +##### 5.2.2.1.3 GPRS SMS services + +GPRS SMS message transfer is based on the same mechanism as the transfer of the GPRS MM/SM signalling messages. On the MS side, the SMS layers (including the supporting CM sub layer functions) utilize the services of the LLC layer to transfer SMS messages per standard packet switched GPRS implementation. + +GPRS SMS service employs the unacknowledged mode of LLC frame transfer, using SAPI=7 for the transfer of SMS messages. This SAPI identifies the SMS Logical Link Entity within the LLC layer. The CM-sub-layer entity retransmits the CP-DATA message if CP-DATA-ACK is not received. The SM-CP protocol is effectively tunneled between the MS and the SGSN, using GAN-GRR messages to the GANC which inter-works it to LLC-PDU relay functions. + +As with GPRS signalling, the secure IPSec tunnel and TCP session is used to provide secure and reliable GPRS SMS delivery over the IP network. + +##### 5.2.2.1.4 Supplementary services + +GSM has standardized a large number of supplementary services. These supplementary services involve procedures that operate end-to-end between the MS and the MSC. The DTAP messages used for the supplementary service are relayed between the MS and MSC in the same manner as in the other call control and mobility management scenarios described in this document. + +#### 5.2.2.2 Standard IP-based protocols + +The GAN can be designed such that the following standard IP-based protocols are used without any modifications: + +- IP over standard lower layers [RFC 791], +- TCP to provide a tunnel for GSM/GPRS signalling and SMS [RFC 793], +- IPsec ESP to provide a secure tunnel for GERAN user and control plane traffic [RFC 2406], +- IKEv2 [IKEv2] and EAP-SIM [EAP SIM] for authentication and establishing and maintaining a security association between MS and GANC, +- UDP [RFC 768] for IPsec NAT traversal [IPSec NAT], +- UDP for GPRS data transfer, +- RTP/UDP [RFC 3550] for transfer of circuit switched speech and user data over IP transport.- RTCP [RFC 3550] for control of RTP frames + +## 5.3 Security mechanisms + +### 5.3.1 Security levels + +GAN supports security mechanisms at different levels and interfaces as depicted below: + +![Diagram illustrating GAN security mechanisms. The diagram shows a sequence of components: MS (Mobile Station), Generic IP Network (cloud), GANC (Generic Access Network Controller), AGb interfaces, MSC SGSN (Mobile Switching Center / Serving GPRS Support Network), IP Network (cloud), and Application Server. Three security mechanisms are indicated by dashed arrows: 1. Up Interface Security (between MS and GANC), 2. CN Authentication, GPRS Ciphering (between MS and MSC SGSN), and 3. Data application security (e.g. HTTPS) (between MS and Application Server).](26d664119ad25250780f554633444e54_img.jpg) + +Diagram illustrating GAN security mechanisms. The diagram shows a sequence of components: MS (Mobile Station), Generic IP Network (cloud), GANC (Generic Access Network Controller), AGb interfaces, MSC SGSN (Mobile Switching Center / Serving GPRS Support Network), IP Network (cloud), and Application Server. Three security mechanisms are indicated by dashed arrows: 1. Up Interface Security (between MS and GANC), 2. CN Authentication, GPRS Ciphering (between MS and MSC SGSN), and 3. Data application security (e.g. HTTPS) (between MS and Application Server). + +**Figure 5.3.1.1: GAN security mechanisms** + +1. The **security mechanisms over the Up interface** protect signalling, voice and data traffic flows between the MS and the GANC from unauthorized use, data manipulation and eavesdropping; i.e., authentication, encryption and data integrity mechanisms are supported. +2. **Authentication** of the subscriber by the core network occurs between the MSC/VLR or SGSN and the MS and is transparent to the GANC – however, there will be a cryptographic binding between the MS-CN authentication and the MS-GANC authentication to prevent man in the middle attacks. **GPRS ciphering** is the standard LLC layer ciphering that operates between the MS and the SGSN. These mechanisms are out of scope of the present document. +3. Additional **application level security mechanisms** may be employed to secure the end-to-end communication between the MS and the application server. For example, the MS may run the HTTP protocol over an SSL session for secure web access. These mechanisms are out of scope of the present document. + +### 5.3.2 Up interface security + +All signalling traffic and user-plane traffic sent between MS and GANC over the Up interface is protected by an IPsec tunnel between the MS and SGW, that provides mutual authentication (using SIM credentials), encryption and data integrity using the same mechanisms as specified in [TS 33.234]. Specifically: + +- Authentication: + - The MS and the SGW use IKEv2, as specified in [IKEv2], in order to establish IPsec security associations. + - Public key signature based authentication with certificates, as specified in [IKEv2], is used to authenticate the SGW. + - EAP-SIM within IKEv2, as specified in [IKEv2, sub-clause 2.16], is used to authenticate the MS. + - A profile for IKEv2 is defined in [TS 33.234, sub-clause 6.5]. +- Confidentiality & data integrity: + - The confidentiality and data integrity of IP packets sent through the tunnel between the MS and the SGW, if required, is protected by IPsec ESP (RFC 2406). A profile for IPsec ESP is defined in [TS 33.234, sub-clause 6.6]. + +NOTE: The above option detailed in sub-clause 5.3.2 is essentially an adoption of the solution investigated and adopted by 3GPP TSG SA WG3 for the WLAN Inter-working feature in Rel-6. The aim of the current study is to forward the results of the feasibility study to SA WG3, for detailed analysis and comments on the viability of adoption of the WLAN Inter-working solution for Generic Access, following completion of the feasibility study in TSG GERAN. + +## 5.4 Multi-mode terminal operation + +*This clause will deal with the procedures for enabling selection and re-selection of generic access to A/Gb interface as opposed to traditional GERAN access.* + +### 5.4.1 Mechanism of mode selection in multi-mode terminals + +The physical layer of a Generic Access capable terminal may support any of a multiple of IP access technologies in addition to the GERAN radio interface, in support of multi-mode operation. The generic access terminal contains an "RR" entity with functionality specific to generic access, namely the GAN RR. The GAN RR entity serves the upper layers in identical fashion to the GSM RR entity, thereby ensuring that there is no change in functionality in the upper layers of the protocol stack. Mode selection relates to which of the RR entities is serving the upper layers i.e. MM at any given time. At any given time, the MS is therefore in one of two operating RR modes: + +- 3GPP mode: +In this mode of operation, the GSM RR or UTRAN RRC entity in the MS serves the upper layers over the Um interface. +- GAN mode: +In this mode of operation, the GAN RR entity serves the upper layers over the Up interface. + +The user can configure the terminal to operate in one of the above two modes at any given time. There can be however a default mode of operation that can be configured by the operator through various mechanisms, including terminal configuration. The operator may additionally be able to set the mode configuration of a terminal through the registration to GAN procedure. + +On power up, the MS always starts in 3GPP mode and executes the normal power-up sequence as specified in 3GPP TS 23.122. Following this, the MS may switch into GAN mode based on mode selection preference determined by user preferences or operator configuration. + +The various preferences for the MS that are possible through operator configuration are as follows: + +- GERAN/UTRAN-only: + +The MS RR entity remains in 3GPP mode and does not switch to GAN mode. + +- GERAN/UTRAN-preferred: + +The MS RR entity is configured in 3GPP mode as long as there is a GSM PLMN available through GERAN. If no GSM PLMN is available through GERAN, and MS has successfully registered with a GAN over the generic IP access network, then the MS switches to GAN mode. When a GSM PLMN becomes available over GERAN, or the MS has de-registered or loses connectivity with the GAN over the generic IP access network, the MS returns to 3GPP mode. + +- GAN-preferred: + +When the MS has successfully registered with the GAN over the generic IP access network, the MS switches to GAN mode and stays in this mode as long as the GAN is available. When the MS deregisters, or otherwise loses connectivity, with the GAN over the generic IP access network, the MS switches to 3GPP mode. + +- GAN-only: + +The MS switches to GAN mode (after initial power up sequence in 3GPP mode) and does not switch to 3GPP mode. + +Mechanisms to avoid ping-pong between GERAN and GAN modes of operation are necessary to provide a good user experience. + +### 5.4.2 PLMN selection + +There is no change in the PLMN selection procedure in the NAS layers (MM and above) in the MS. PLMN selection follows the rules specified in 3GPP TS 23.122. + +Currently the BSS can be connected to only one CN node each in the CS and PS domains, both of which are associated with the same PLMN. Hence, it is assumed that one GAN is associated with one PLMN. + +The identity of the PLMN associated with the GAN is made known to the MS on successful registration with the GAN. Hence, only the PLMN associated with the successfully registered GAN can be selected. The PLMN associated with the GAN the MS is registered on, is treated as an equivalent PLMN to the HPLMN. As a result, the concept of background + +scanning for higher priority PLMNs does not apply in GAN mode. It should be noted that it is the GAN operator of the HPLMN or the GAN operator associated with the HPLMN (in case of MVNO) that assigns the serving GAN to the MS. + +Upper layers do not have any visibility to the PLMNs available via GERAN when in GAN mode, since only one RR entity in the MS is connected to the MM at any given time. The RR entity (for *e.g.* GSM RR in GAN mode) that is not connected to the MM does not provide information to the MM through the connected RR entity (*e.g.* GAN RR in GAN mode). + +The above mechanisms of PLMN selection apply both in automatic and manual PLMN selection modes. + +In order to support roaming restrictions, it shall be possible for the GANC to be provisioned with a number of LA identities. Rules for the assignment of a location area identity to a MS based on the information provided by the MS, such as CGI, etc., would then allow the use of normal MM procedures to apply the roaming restrictions. + +Roaming network cannot be used for generic access unless the home network supports generic access. + +### 5.4.3 Re-selection between GERAN/UTRAN and GAN modes + +#### 5.4.3.1 Rove-in (from GERAN/UTRAN to GAN) + +This procedure is applicable only if the MS mode selection is GAN-only, GAN-preferred or GERAN/UTRAN-preferred but no GSM PLMN available. As long as MS is not in NC2 mode, the MS may rove in. + +Following successful GAN registration, the MS switches to GAN mode wherein the serving RR entity is GAN-RR. GAN-RR reports the NAS-related system information, as obtained from the GANC, to the NAS. NAS considers the GAN cell as the current serving cell. + +While in GAN mode, GSM-RR (and UTRAN RRC) is detached from the RR-SAP in the MS *i.e.* + +- it does not inform NAS about any GERAN/UTRAN cell re-selection and/or the change of system information of the current camping cell; +- it does not inform NAS about any newly found PLMN over GERAN (or UTRAN); +- it does not act on any paging request message received over GERAN (or UTRAN). + +#### 5.4.3.2 Rove-out (from GAN to GERAN/UTRAN) + +This procedure is applicable when MS detaches from the generic IP access network, and its mode selection is GAN-preferred or GERAN/UTRAN-preferred. + +When the MS detaches from the generic IP access network, depending on prevailing circumstances the MS may be able to deregister first with the GANC. + +For the GAN-preferred and GERAN/UTRAN-preferred mode selections, the MS detaches GAN-RR from NAS and re-attaches GSM-RR to NAS and restores normal GSM-RR functionality. + +For the GAN-only mode selection, GAN-RR (or UTRAN RRC) remains attached to NAS and the MS stays in GAN mode (in "No Service" condition). + +#### 5.4.3.3 Ping-pong avoidance between GAN and GERAN/UTRAN + +In order to support the requirements in 3GPP TS 22.011 one potential example of the mechanism to be supported by the MS is described below. + +Two timers are defined and provided to the MS at the time of registration to the GAN. In addition a counter N keeps track of the number of re-selections between GAN and 3GPP modes the MS has performed. + +On switch on, N is set to 1 and when the GAN RR entity is connected to MM, timer $T_{ping-pong-slowdown}$ is started with a value of $N*Y + X$ . If the MS switches mode before the expiry of $T_{ping-pong-slowdown}$ , timer $T_{ping-pong-avoid}$ is started with value $N*Y$ . N is incremented by 1. $T_{ping-pong-slowdown}$ is restarted with value $N*Y + X$ . The MS is now prohibited from switching modes until the $T_{ping-pong-avoid}$ timer expires. This mechanism ensures that the MS is forced to stay within a mode for a linearly increasing length of time if consecutive mode switches occur prior to the expiry of the $T_{ping-pong-slowdown}$ timer. If mode switch occurs post- $T_{ping-pong-slowdown}$ expiry, N is reset to 1 and at the next mode switch $T_{ping-pong-avoid}$ is started with value $Y$ . + +avoid and $T_{ping-pong-slowdown}$ are reset. $T_{ping-pong-slowdown}$ timer thereby acts as a penalty timer for the setting and re-setting of $T_{ping-pong-slowdown}$ . + +### 5.4.4 Handovers between GAN and GERAN + +#### 5.4.4.1 Cell identifiers in generic access + +In GAN, as in GERAN, a cell is identified by a Cell Global Identity (CGI) which is the concatenation of a Location Area Identity (LAI) and Cell Identity (CI). + +##### 5.4.4.1.1 GAN cell id for Location Services & billing + +Cell identities (CGI) are often used to route the call to location dependent services such as emergency calling, operators, announcements and freephone numbers. Cell identities can also used by the core network to identify the location of the call for billing purposes. To meet these requirements, the GANC provides a CGI to the core network indicating the GAN cell that the call originated from. + +###### 5.4.4.1.1.1 Assigning GAN cell id based on GSM location + +In the GAN architecture, the MS has a direct, IP-based connection to the GANC, so the notion of a "cell" is defined by some logical grouping of MSs being served by a GANC. Since the GAN coverage area overlaps the GERAN coverage area, the simplest grouping of MSs is based on the overlapping GSM cell that the MS is located in. This can be done at various location resolutions, such as: + +- a GAN cell for each GSM cell, or +- a GAN cell for each GSM location area, or +- a GAN cell for some other mapping of GSM cells into GAN cells + +The mapping of GSM cells into GAN cells is defined in the GANC. A single GANC could represent one or more cells (CGI) in one or more location areas (LAI) for location services. + +This mechanism allows the operator to leverage any existing location infrastructure for GSM cell sites, and provides MS location to the resolution of existing GSM cell sites. + +###### 5.4.4.1.1.2 Assigning GAN cell id based on other information + +The GANC can use other information provided by the MS, such as the identity or location of the generic access network point of attachment, or GPS co-ordinates, to identify the geographic location of the MS, and map it to a corresponding GAN cell id, based on operator configuration. + +###### 5.4.4.1.1.3 Determining GAN cell id during GAN registration + +During GAN registration, if the MS is in GERAN coverage, it indicates to the GANC the cell id of the overlapping GERAN cell. The GANC then maps this information to a corresponding GAN cell id and stores it in the registration context of that MS. This GAN cell id is also provided to the MS in the system information during GAN registration, so the MS can do a location update with the core network, if required. + +During GAN registration, if the MS is not in GSM coverage, then the cell id of the overlapping GERAN cell (and corresponding GAN cell id) may not be determined reliably. In this case, the GANC allows the operator to apply a service policy – either deny GAN service, or allow it with an explicit indication to the MS that its location is unknown. In the latter case, the GANC will assign a default GAN cell id for this MS registration context, and also indicate that to the MS in the system information. + +When the MS places a call (including an emergency call) over GAN, the GANC passes to the core network the GAN cell id (CGI) value stored in the MS registration context. The core network must be configured with the new GAN cell id values; however, the GERAN cell id and corresponding GAN cell id can share the same location information e.g. cell site address, location co-ordinates, serving Emergency Centre, etc. If the GAN cell id corresponds to the "no GSM coverage" case, the core network will need a special configuration for that cell id (e.g. to route an emergency call to a default Emergency Centre, no automatic location identification, etc.). + +###### 5.4.4.1.1.4 GAN cell id for roaming scenario + +If an MS reports a GERAN cell id to the GANC that indicates the MS is in a location that is not served by this GANC (e.g. because the MS is roaming in a foreign country or another PLMN), the GANC can map the MS to one of several distinct GAN cell ids (configured in the GANC according to operator policy). + +This GAN cell id is sent to the MS in system information during GAN registration (and is subsequently used by MS for core network registration). Therefore, it can be used to implement roaming restrictions, using existing mechanisms (e.g. in the SIM or in the HLR). + +##### 5.4.4.1.2 GAN cell id for handover-to-GAN + +The GAN cell id used for location and billing can be independent from the GAN cell id used for handover. + +A single GANC represents a single GAN cell for the purpose of handover-to-GAN. This "handover-GAN-CGI" is not visible to the GANC or the MS, and is only used in the source RAN and the core network for identifying a target cell for handover to GAN. + +To enable handover-to-GAN, the GANC is also assigned a single ARFCN; in fact, all GANCs in a given operator domain can share the same ARFCN value. This ARFCN is indicated to the MS by the GANC during GAN registration. + +The "handover-GAN-CGI" assigned to the GANC is configured as the target handover cell in all neighbouring source RAN cells (in their ARFCN/BSIC-to-CGI mapping table). Neighbouring source RAN cells are those whose service area "overlaps" the GANC service area, for the purpose of handover. For example, neighbour cells are: + +- All source RAN cells attached to the same MSC as the GANC +- All source RAN cells attached to a different MSC but that can handover to the MSC to which the GANC is attached. + +When the MS reports measurements to the source RAN BSS on the GAN cell identified by its ARFCN, then the source RAN BSS maps the ARFCN to the "handover-GAN-CGI" through its mapping table, and is thus able to identify the target cell (GANC) for handover-to-GAN. + +#### 5.4.4.2 Handover to GAN + +![Sequence diagram for Handover to GAN. Lifelines: MS, GANC, BSC, CN. The diagram shows 14 steps: 1. Um: Measurement Report (MS to BSC), 2. Handover Reqd. (BSC to CN), 3. Handover Request (CN to GANC), 4. Handover Request Ack (GANC to CN), 5. Handover Command (CN to BSC), 6. Um: Handover Command (BSC to MS), 7. GAN-RR HANDOVER ACCESS (MS to GANC), 8. RTP stream setup (dashed line MS to GANC), 9. GAN-RR HANDOVER COMPLETE (MS to GANC), 10. Handover Detect (GANC to CN), 11. VOICE (MS to CN), 12. Handover Complete (GANC to CN), 13. Clear Command (CN to BSC), 14. Clear Complete (BSC to CN). A box labeled 'GAN Registered' is shown under the MS lifeline.](744acfe8d4e31bcf03f95714c2f6e567_img.jpg) + +``` + +sequenceDiagram + participant MS + participant GANC + participant BSC + participant CN + Note left of MS: GAN Registered + MS->>BSC: 1. Um: Measurement Report + BSC->>CN: 2. Handover Reqd. + CN->>GANC: 3. Handover Request + GANC->>CN: 4. Handover Request Ack + CN->>BSC: 5. Handover Command + BSC->>MS: 6. Um: Handover Command + MS->>GANC: 7. GAN-RR HANDOVER ACCESS + MS-->>GANC: 8. RTP stream setup + MS->>GANC: 9. GAN-RR HANDOVER COMPLETE + GANC->>CN: 10. Handover Detect + MS->>CN: 11. VOICE + GANC->>CN: 12. Handover Complete + CN->>BSC: 13. Clear Command + BSC->>CN: 14. Clear Complete + +``` + +Sequence diagram for Handover to GAN. Lifelines: MS, GANC, BSC, CN. The diagram shows 14 steps: 1. Um: Measurement Report (MS to BSC), 2. Handover Reqd. (BSC to CN), 3. Handover Request (CN to GANC), 4. Handover Request Ack (GANC to CN), 5. Handover Command (CN to BSC), 6. Um: Handover Command (BSC to MS), 7. GAN-RR HANDOVER ACCESS (MS to GANC), 8. RTP stream setup (dashed line MS to GANC), 9. GAN-RR HANDOVER COMPLETE (MS to GANC), 10. Handover Detect (GANC to CN), 11. VOICE (MS to CN), 12. Handover Complete (GANC to CN), 13. Clear Command (CN to BSC), 14. Clear Complete (BSC to CN). A box labeled 'GAN Registered' is shown under the MS lifeline. + +Figure 5.4.4.2.1: Handover to GAN + +The description of the handover procedure assumes the following: + +- the MS is on an active call on the GERAN, and + - its mode selection is GAN-preferred, or if GERAN/UTRAN-preferred the RxLev from the current serving cell drops below a defined threshold, $RxLev\_access\_min + X$ dB (this threshold can be specified as a fixed value, or provided by the GERAN BSS to the MS in dedicated mode), and + - the MS has successfully registered with a GANC, allowing the MS to obtain GAN system information, and + - the GERAN provides information on neighbouring cells such that one of the {ARFCN, BSIC} in the neighbour list matches the {ARFCN, BSIC} associated with the GANC, as provided in the AS-related component of the system information obtained from GANC. +- 1) The MS now begins to include GAN cell information in the *Measurement Report* to the GERAN. The MS reports the highest signal level for the GAN cell {ARFCN, BSIC}. This is not the actual measured signal level on GAN, rather a "faked" value. + +- 2) Based on MS measurement reports and other internal algorithms, GERAN decides to handover to the GAN cell, using an internal mapping of {ARFCN, BSIC} to CGI. The GERAN starts the handover preparation by sending a *Handover Required* message to the CN, identifying the target (GAN) cell. +- 3) The CN requests the target GANC to allocate resources for the handover, using *Handover Request*. +- 4) The target GANC acknowledges the handover request, using *Handover Request Acknowledge*, indicating it can support the requested handover, and provides a *Handover Command* that indicates the radio channel to which the mobile station should be directed. +- 5) The CN forwards the *Handover Command* to the GERAN, completing the handover preparation. +- 6) GERAN sends *Handover Command* to the MS to initiate handover to GAN. The *Handover Command* includes among other parameters information about the target GAN such as BCCH ARFCN, PLMN color code and BSIC. The MS does not switch its audio path from GERAN to GAN until handover completion, i.e., until it sends the GAN-RR HANDOVER COMPLETE, to keep the audio interruption short. +- 7) The MS accesses the GANC using the GAN-RR HANDOVER ACCESS message, and provides the entire *Handover Command* received from GERAN. The handover reference in the handover command allows the GANC to correlate the handover to the *Handover Request Acknowledge* message earlier sent to the CN and identify the successful completion of the handover. +- 8) The GANC sets up the bearer path with the MS, using the same steps as in steps 11-17 of Mobile Originated calling scenario (with the exception that no *Assignment* or *Assignment Complete* message is exchanged with the CN). +- 9) The MS transmits the GAN-RR HANDOVER COMPLETE to indicate the completion of the handover procedure at its end. It switches the user from the GERAN user plane to the GAN user plane. +- 10) The GANC indicates to the CN that it has detected the MS, using *Handover Detect* message. The CN can optionally now switch the user plane from the source GERAN to the target GAN. +- 11) Bi-directional voice traffic is now flowing between the MS and CN, via GANC. +- 12) The target GANC indicates the handover is complete, using the *Handover Complete* message. If it had not done so before, the CN now switches the user plane from source GERAN to target GAN. +- 13) Finally, the CN tears down the connection to the source GERAN, using *Clear Command*. +- 14) The source GERAN confirms the release of GERAN resources allocated for this call, using *Clear Complete*. + +#### 5.4.4.3 Handover to GERAN + +![Sequence diagram for Handover to GERAN showing interactions between MS, GANC, BSC, and CN.](9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg) + +``` +sequenceDiagram + participant MS + participant GANC + participant BSC + participant CN + + Note over MS: Ongoing GAN connection + MS-->>GANC: 1. GAN-RR UPLINK QUALITY INDICATION + MS->>GANC: 2. GAN-RR HANDOVER REQUIRED + GANC->>CN: 3. Handover Required. + CN->>BSC: 4. Handover Request + BSC->>CN: 5. Handover Request Ack + CN->>GANC: 6. Handover Command + GANC->>MS: 7. GAN-RR HANDOVER COMMAND + MS->>BSC: 8. Um: Handover Access + BSC->>CN: 9. Handover Detect + CN<-->>BSC: 10. VOICE + BSC->>MS: 11. Um: Physical Information + MS->>BSC: 12. Um: Handover Complete + BSC->>CN: 13. Handover Complete + CN<-->>BSC: 14. VOICE + CN->>GANC: 15. Clear Command + GANC->>MS: 16. GAN-RR RR RELEASE + GANC->>CN: 17. Clear Complete + MS->>GANC: 18. GAN-RR RR RELEASE COMPLETE + GANC->>MS: 19. GAN-RR DEREGISTER +``` + +Sequence diagram for Handover to GERAN showing interactions between MS, GANC, BSC, and CN. + +**Figure 5.4.4.3.1: Handover to GERAN** + +The procedure description in this sub-clause assumes the following: + +- the MS is on an active call on the GAN, and +- the MS mode selection is GAN-preferred or GERAN/UTRAN-preferred, and + +- the MS begins to leave GAN coverage, based on its local measurements, received RTCP reports, as well as any uplink quality indications received from the GANC + +The handover from GAN to GERAN procedure is always triggered by the MS. + +- 1) The GANC may send a GAN-RR UPLINK QUALITY INDICATION if there is a problem with the uplink quality for the ongoing call. Whenever the MS receives an indication of bad quality, it should start the handover procedure, as described in the next step. Alternately, MS can use RTCP to measure uplink and downlink quality, to initiate the handover procedure. +- 2) The MS sends the GAN-RR HANDOVER REQUIRED message to the GANC indicating the Channel Mode and a list of GERAN cells, identified by CGI, in order of preference (e.g. ranked by C1 path loss parameter) for handover. This list is the most recent information available from the GSM RR subsystem. +- 3) The GANC starts the handover preparation by signalling to the CN the need for handover, using *Handover Required*, and including the GERAN cell list provided by the MS. +- 4) The CN selects a target GERAN cell and requests it to allocate the necessary resources, using *Handover Request*. +- 5) The target GERAN builds a *Handover Command* message providing information on the channel allocated and sends it to the CN through the *Handover Request Acknowledge* message. +- 6) The CN signals the GANC to handover the MS to the GERAN, using *Handover Command* message, ending the handover preparation phase. +- 7) GANC transmits the GAN-RR HANDOVER COMMAND to the MS including the details sent by the GERAN on the target resource allocation. +- 8) The MS transmits the *Um: Handover Access* containing the handover reference element to allow the target GERAN to correlate this handover access with the *Handover Command* message transmitted earlier to the CN in response to the *Handover Required*. +- 9) The target GERAN confirms the detection of the handover to the CN, using the *Handover Detect* message. +- 10) The CN may at this point switch the user plane to the target BSS. +- 11) The GERAN provides *Physical Information* to the MS i.e. *Timing Advance*, to allow the MS to synchronize with the GERAN. +- 12) The MS signals to the GERAN that the handover is completed, using *Handover Complete*. +- 13) The GERAN confirms to the CN the completion of the handover, via *Handover Complete* message. +- 14) Bi-directional voice traffic is now flowing between the MS and CN, via the GERAN. +- 15) On receiving the confirmation of the completion of the handover, the CN indicates to the GANC to release any resources allocated to the MS, via the *Clear Command*. +- 16) GANC commands the MS to release resources, using the GAN-RR RR RELEASE message. +- 17) GANC confirms resource release to CN using the *Clear Complete* message. +- 18) The MS confirms resource release to the GANC using the GAN-RR RR RELEASE COMPLETE message. +- 19) The MS may finally deregister from the GANC, using GAN-RR DEREGISTER message. + +#### 5.4.4.4 Other handover considerations + +The current mechanisms and definition for handover failure should continue to hold. + +Operator methods for setting thresholds to trigger HO from GAN are not seen as being possible due to the generic nature of access. + +Handover to and from UTRAN should be possible in a manner identical to the case for handovers between UTRAN and GERAN. + +### 5.4.5 Cell Change Order between GAN and GERAN + +While in GERAN, a mobile station may be ordered to perform a cell reselection to GAN, by using the Cell Change Order procedures used in GERAN, with no modifications. + +While the mobile station is involved in a PS session in the GAN, the GANC may decide to force the mobile station to perform a cell reselection to GERAN. To achieve this, the GANC may send a GAN GRR MEASUREMENT ORDER to the mobile station. Upon receipt of a GAN GRR MEASUREMENT REPORT, containing a list of GERAN cells, the GANC may send a GAN GRR CELL CHANGE ORDER to the mobile station. + +Given the inherent ability of a multi-mode terminal of simultaneous reception by GSM RR and GAN RR, it is not necessary to provide support for NACC. + +## 5.5 Emergency call support in GAN + +The GANC can indicate an operator preference for the access network for emergency calls placement in the registration accept message. Based on operator preference, and if a GSM PLMN is available, the MS should switch from GAN mode to 3GPP mode and place the emergency call over GERAN/UTRAN, to leverage the location determination infrastructure in GERAN/UTRAN. During the emergency call, the MS should not attempt to handover the call to GAN. After the emergency call is completed, the MS performs normal rove-in procedures, if GAN coverage is still available, to re-enter GAN mode. Alternately there may be a penalty timer configured to ensure that the MS remains in GERAN/UTRAN for call-back purposes. On expiry of the penalty timer the MS performs normal rove-in procedures, if GAN coverage is still available, to re-enter GAN mode. + +Based on operator preference, or if a GSM PLMN is not available, the MS places the emergency call over GAN. In GAN, the emergency call is handled just like a GSM emergency call origination. The CGI associated with the GANC provides an indication of the location of the MS. Additional, more accurate location information may be obtained by the GANC either directly from the MS (e.g. using AGPS) or from the generic IP access network point of attachment (e.g. using a database of IP or MAC addresses). If available, the GANC can pass this location information through BSSMAP to the core network, when requested. However, location services based on mechanisms using the GERAN physical layer cannot be applied. + +Mechanisms to deregister the MS if the location accuracy is not deemed sufficient for emergency calls in GAN mode by the operator can be supported. + +## 5.6 Feasibility for support of services available through GERAN while in GAN mode + +The complete support of LCS through Generic Access is FFS. However it was determined that a certain level of LCS support can be obtained through + +- appropriate assignment of CGIs for GAN cells, +- use of A-GPS + +Location services that rely on the physical layer of GERAN cannot be applied in the case of generic access, e.g. OTDOA. It is seen feasible to support all services requiring support of CC, MM, GMM, LLC and SS as well as SMS since support for the transfer of upper layer NAS messages is provided in an identical fashion as in GERAN. However, services such as VGCS, VBS and CBS cannot be provided in a generic fashion. Such services require specific support from the concerned generic access technology. CBS is a service provided by GERAN and if needed in GAN then it needs to be supported in the GANC through functionality such as IP multicast. + +It is seen feasible to support MBMS through Point-to-point means using current mechanisms of support through GPRS bearers. In case of point-to-multipoint MBMS service, notification of service and how the service area can be mapped to the GAN cell identity and location area are issues that need to be resolved. Point-to-multipoint MBMS support requires access network specific support. + +## 5.7 Other considerations + +- 1) It is noted that there is a need to define the frequency of SID and Idle-frame transmission to provide support to the GAN in the determination of uplink quality. + +- 2) It is noted that architecture studied in the feasibility study requires that in case of handover in a roaming scenario, the MS needs to have first registered on the GAN by first contacting the home operator. The visiting network cannot direct the MS to establish GAN connectivity. +- 3) It is noted that with the ability to connect to the home operator through generic access while roaming from a GERAN perspective, proper MMI indication will be needed to inform the user of the need for appropriate dialling of digits (e.g. addition of "+"-country code when roaming out of GAN coverage into the visiting network. Currently it is not typical, except in border regions, for the MS in the same geographical area to dial the called number differently. +- 4) The ability to have the SGW functionality in a physically separate node from the other GANC functionality implies the need for a trusted relationship between the two nodes, i.e. secure links between the GANC and the SGW. +- 5) The support of priority services needs to be studied further. +- 6) It was seen possible to have the MS continue to support its Class A/B/C of operation as in GERAN. It was also seen possible to provide support for DTM mode of operation. +- 7) For the case of Handovers in PS Domain that is currently being worked on in GERAN, it was seen possible to re-use the concept of mimicking the GERAN procedure by using a similar CGI identity mechanism for the GAN cell as in the case of CS domain handovers. + +# --- 6 Potential impacts on current specifications + +No impact on the current GERAN specifications was identified. + +# --- 7 Summary and conclusion + +It has been concluded that it is feasible to support generic access to the A/Gb interface, wherein an MS capable of generic access can obtain services provided by the core network, using alternate access methods such as through a generic IP based broadband connection. The generic broadband connection provides connectivity between the MS and the core network and may be obtained through any means or any combination of means such as ADSL, Cable, alternate wireless access, etc. The MS connects to a network node that interfaces with the core network through the standard A/Gb interfaces. A new interface that connects the MS to a generic access network needs to be defined. A new protocol that mimics the functionality as seen by the MM layer would need to be defined. + +It was determined that an MS supporting generic access to the A/Gb interface can support all the service requirements defined for the 3GPP system including support for SMS, MMS and IMS services that can be supported by GERAN. Due to the generic nature of the access network, services provided by the radio network in GERAN such as CBS, VGCS and VBS cannot be supported in a generic manner. However, support for such features is possible through access specific mechanisms such as multiple IP unicast in case of support of CBS. Emergency calls support was seen feasible in GAN mode with the limitations that location services relying on GERAN physical layer based mechanisms cannot be used. However, alternate mechanisms are possible. + +Given the current state of specifications and the on-going status of the work, it was not possible to conclude on the feasibility for support of MBMS. It was seen possible to support handovers in PS domain with the understanding that the current CS domain handover trigger mechanisms would continue to be used in this case as well thereby allowing the use of the mechanisms seen possible for CS domain handovers. + +# Annex A: Change history + +| Change history | | | | | | | | +|----------------|----------|-----------|----|-----|-----------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2004-08 | GERAN#21 | GP-042290 | | | Approved at GERAN#21 | | 6.0.0 | +| 2007-08 | GERAN#35 | | | | Version for Release 7 | 6.0.0 | 7.0.0 | +| 2008-12 | GERAN#40 | | | | Version for Release 8 | 7.0.0 | 8.0.0 | +| 2009-12 | GERAN#44 | | | | Version for Release 9 | 8.0.0 | 9.0.0 | +| 2011-03 | GERAN#49 | | | | Version for Release 10 | 9.0.0 | 10.0.0 | +| 2011-04 | | | | | Correction to previous entry in history table | 10.0.0 | 10.0.1 | +| 2012-01 | | | | | Correction to Symbols and Abbreviations | 10.0.1 | 10.0.2 | +| 2012-09 | GERAN#55 | | | | Version for Release 11 | 10.0.2 | 11.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25111/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/25_series/25111/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7cd7b73352915830ba1137d7f3bfc2b15c7eec57 --- /dev/null +++ b/marked/Rel-16/25_series/25111/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17b8e678ae07bdfcd14a651274b53d612d7842963edf5abc973b958a2037de7c +size 62600 diff --git a/marked/Rel-16/25_series/25111/raw.md b/marked/Rel-16/25_series/25111/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..609170d658dba4879c704a9ac4289eb222ab1153 --- /dev/null +++ b/marked/Rel-16/25_series/25111/raw.md @@ -0,0 +1,647 @@ + + + + + + +# --- Contents + +| | | +|---------------------------------------------|----| +| Foreword ..... | 4 | +| Introduction ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 6 | +| 4 General..... | 7 | +| 4.1 Main concepts ..... | 7 | +| 4.2 LMU Classes..... | 7 | +| 4.3 U-TDOA architecture..... | 7 | +| 5 LMU radio characteristics..... | 8 | +| 5.1 Frequency bands..... | 8 | +| 5.2 Channel arrangement..... | 8 | +| 5.3 Reference sensitivity level ..... | 9 | +| 5.4 Dynamic range ..... | 9 | +| 5.5 Adjacent Channel Selectivity (ACS)..... | 9 | +| 5.6 Blocking characteristics ..... | 9 | +| 5.7 Intermodulation characteristics ..... | 13 | +| 5.8 Spurious emissions..... | 14 | +| 6 LMU measurement requirements..... | 15 | +| 6.1 General ..... | 15 | +| 6.2 RRC States supported..... | 15 | +| 6.3 Maximum response times..... | 15 | +| 6.4 Nominal time accuracy..... | 15 | +| 6.5 Multipath scenarios ..... | 16 | +| 6.6 Moving scenario..... | 16 | +| 6.7 Cross correlation ..... | 16 | +| Annex A (informative): Change history..... | 17 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- Y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- Introduction + +In order to ensure correctness and consistency of the specifications (i.e., technical specifications and technical reports) under responsibility of the Technical Specification Groups (TSG) of the 3rd Generation Partnership Project (3GPP), clear, manageable and efficient mechanisms are necessary to handle version control, change control, document updating, distribution and management. + +Also, the fact that the specifications are/will be implemented by industry almost in parallel with the writing of them requires strict and fast procedures for handling of changes to the specifications. + +It is very important that the changes that are brought into the standard, from the past, at present and in the future, are well documented and controlled, so that technical consistency and backwards tracing are ensured. + +The 3GPP TSGs, and their sub-groups together with the Support Team are responsible for the technical content and consistency of the specifications whilst the Support Team alone is responsible for the proper management of the entire documentation, including specifications, meeting documents, administrative information and information exchange with other bodies. + +# --- 1 Scope + +The present document establishes the Location Measurement Unit (LMU) minimum RF characteristics of the FDD mode of UTRA. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TS 25.104: "Base Station (BS) radio transmission and reception (FDD)". +- [2] 3GPP TS 45.004: "Modulation". +- [3] 3GPP TS 25.141: "Base Station (BS) conformance testing (FDD)". +- [4] 3GPP TR 25.942: "Radio Frequency (RF) system scenarios". +- [5] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [5] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [5]. + +**Mean power:** When applied to a W-CDMA modulated signal this is the power (transmitted or received) in a bandwidth of at least $(1 + \alpha)$ times the chip rate of the radio access mode. The period of measurement shall be at least one timeslot unless otherwise stated. + +NOTE: The roll-off factor $\alpha$ is defined in clause 6.8.1 of [1]. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [5] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [5]. + +| | | +|--------|----------------------------------------------| +| ACS | Adjacent Channel Selectivity | +| BS | Base Station | +| BER | Bit Error Ratio | +| BLER | Block Error Ratio | +| CW | Continuous Wave (unmodulated signal) | +| DL | Down Link (forward link) | +| FDD | Frequency Division Duplexing | +| GSM | Global System for Mobile Communications | +| LMU | Location Measurement Unit | +| UARFCN | UTRA Absolute Radio Frequency Channel Number | +| UE | User Equipment | +| UL | Up Link (reverse link) | + +| | | +|--------|----------------------------------------| +| U-TDOA | Uplink Time Difference Of Arrival | +| WCDMA | Wideband Code Division Multiple Access | + +# --- 4 General + +## 4.1 Main concepts + +The LMU is either located as a separate unit in an existing network or typically located at Node B or BTS sites. Therefore the LMU radio requirements assume that the isolation between the LMU and any other network to be protected is to be at least 30dB. + +The communication link between LMU and Stand-Alone SMLC is not a radio interface over the air. Requirements in this document therefore do not cover the situation when the LMU is transmitting over the air on this interface between LMU and Stand-Alone SMLC. + +## 4.2 LMU Classes + +The requirements in this specification apply to Wide Area LMUs and Medium Range LMUs. + +Wide Area LMUs are characterised by requirements derived from Macro Cell scenarios with an LMU to UE minimum coupling loss equal to 70 dB. + +Medium Range LMUs are characterised by requirements derived from Micro Cell scenarios with an LMU to UE minimum coupling loss equal to 53 dB. + +For Pico Cell scenarios, the location of the BS provides sufficient accuracy; therefore, a Local Area LMUs class is not specified. + +## 4.3 U-TDOA architecture + +A sample architecture is shown in Figure 3.1 depicting the LMU's relationship with other network elements. The LMU is typically located at the Node B. The LMUs communicate with the SMLC that distributes UTDOA reference data from the reference LMU to other cooperating LMUs when performing UE positioning. + +![Figure 3.1: Example of UTDOA deployment. The diagram shows a network architecture with Node B, RNC, LMU, Stand-Alone SMLC, MSC, and SGSN. Node B is connected to RNC via Iub. RNC is connected to Stand-Alone SMLC via Iupc. Stand-Alone SMLC is connected to MSC and SGSN via Iupc. LMU is connected to Node B and Stand-Alone SMLC. A vertical arrow indicates that LMUs are typically located at Node B.](d0abac95583b52a3b35f74a215567334_img.jpg) + +``` + +graph TD + NodeB1[Node B] -- Iub --> RNC1[RNC] + NodeB2[Node B] -- Iub --> RNC2[RNC] + RNC1 -- Iupc --> SMLC[Stand-Alone SMLC] + RNC2 -- Iupc --> SMLC + SMLC -- Iupc --> MSC[MSC] + SMLC -- Iupc --> SGSN[SGSN] + NodeB1 -- LMU1[LMU] --> SMLC + NodeB2 -- LMU2[LMU] --> SMLC + LMU3[LMU] --> SMLC + LMU4[LMU] --> SMLC + LMU5[LMU] --> SMLC + LMU6[LMU] --> SMLC + LMU7[LMU] --> SMLC + LMU8[LMU] --> SMLC + LMU9[LMU] --> SMLC + LMU10[LMU] --> SMLC + LMU11[LMU] --> SMLC + LMU12[LMU] --> SMLC + LMU13[LMU] --> SMLC + LMU14[LMU] --> SMLC + LMU15[LMU] --> SMLC + LMU16[LMU] --> SMLC + LMU17[LMU] --> SMLC + LMU18[LMU] --> SMLC + LMU19[LMU] --> SMLC + LMU20[LMU] --> SMLC + LMU21[LMU] --> SMLC + LMU22[LMU] --> SMLC + LMU23[LMU] --> SMLC + LMU24[LMU] --> SMLC + LMU25[LMU] --> SMLC + LMU26[LMU] --> SMLC + LMU27[LMU] --> SMLC + LMU28[LMU] --> SMLC + LMU29[LMU] --> SMLC + LMU30[LMU] --> SMLC + LMU31[LMU] --> SMLC + LMU32[LMU] --> SMLC + LMU33[LMU] --> SMLC + LMU34[LMU] --> SMLC + LMU35[LMU] --> SMLC + LMU36[LMU] --> SMLC + LMU37[LMU] --> SMLC + LMU38[LMU] --> SMLC + LMU39[LMU] --> SMLC + LMU40[LMU] --> SMLC + LMU41[LMU] --> SMLC + LMU42[LMU] --> SMLC + LMU43[LMU] --> SMLC + LMU44[LMU] --> SMLC + LMU45[LMU] --> SMLC + LMU46[LMU] --> SMLC + LMU47[LMU] --> SMLC + LMU48[LMU] --> SMLC + LMU49[LMU] --> SMLC + LMU50[LMU] --> SMLC + LMU51[LMU] --> SMLC + LMU52[LMU] --> SMLC + LMU53[LMU] --> SMLC + LMU54[LMU] --> SMLC + LMU55[LMU] --> SMLC + LMU56[LMU] --> SMLC + LMU57[LMU] --> SMLC + LMU58[LMU] --> SMLC + LMU59[LMU] --> SMLC + LMU60[LMU] --> SMLC + LMU61[LMU] --> SMLC + LMU62[LMU] --> SMLC + LMU63[LMU] --> SMLC + LMU64[LMU] --> SMLC + LMU65[LMU] --> SMLC + LMU66[LMU] --> SMLC + LMU67[LMU] --> SMLC + LMU68[LMU] --> SMLC + LMU69[LMU] --> SMLC + LMU70[LMU] --> SMLC + LMU71[LMU] --> SMLC + LMU72[LMU] --> SMLC + LMU73[LMU] --> SMLC + LMU74[LMU] --> SMLC + LMU75[LMU] --> SMLC + LMU76[LMU] --> SMLC + LMU77[LMU] --> SMLC + LMU78[LMU] --> SMLC + LMU79[LMU] --> SMLC + LMU80[LMU] --> SMLC + LMU81[LMU] --> SMLC + LMU82[LMU] --> SMLC + LMU83[LMU] --> SMLC + LMU84[LMU] --> SMLC + LMU85[LMU] --> SMLC + LMU86[LMU] --> SMLC + LMU87[LMU] --> SMLC + LMU88[LMU] --> SMLC + LMU89[LMU] --> SMLC + LMU90[LMU] --> SMLC + LMU91[LMU] --> SMLC + LMU92[LMU] --> SMLC + LMU93[LMU] --> SMLC + LMU94[LMU] --> SMLC + LMU95[LMU] --> SMLC + LMU96[LMU] --> SMLC + LMU97[LMU] --> SMLC + LMU98[LMU] --> SMLC + LMU99[LMU] --> SMLC + LMU100[LMU] --> SMLC + +``` + +Figure 3.1: Example of UTDOA deployment. The diagram shows a network architecture with Node B, RNC, LMU, Stand-Alone SMLC, MSC, and SGSN. Node B is connected to RNC via Iub. RNC is connected to Stand-Alone SMLC via Iupc. Stand-Alone SMLC is connected to MSC and SGSN via Iupc. LMU is connected to Node B and Stand-Alone SMLC. A vertical arrow indicates that LMUs are typically located at Node B. + +Figure 3.1: Example of UTDOA deployment + +# 5 LMU radio characteristics + +An LMU performs BS receiver functions to obtain reference data for use at a cooperating LMU. The following clause describes the required LMU radio characteristics when performing these functions. + +## 5.1 Frequency bands + +- a) The LMU is designed to operate in the following bands: + +Table 4.1: Frequency bands + +| Operating Band | UL Frequencies
UE transmit, LMU receive | +|----------------|--------------------------------------------| +| I | 1920 – 1980 MHz | +| II | 1850 -1910 MHz | +| III | 1710-1785 MHz | +| IV | 1710-1755 MHz | +| V | 824 – 849MHz | +| VI | 830-840 MHz | +| VII | 2500 – 2570 MHz | +| VIII | 880 – 915 MHz | +| IX | 1749.9 – 1784.9 MHz | +| X | 1710-1770 MHz | + +- b) Deployment in other frequency bands is not precluded + +## 5.2 Channel arrangement + +The channel arrangement shall be as specified in Section 5.4 of [1]. + +## 5.3 Reference sensitivity level + +Using the reference measurement channel specification in TS 25.104 Annex A [1], the reference sensitivity level and performance of the LMU shall be as specified in Table 4.2. + +**Table 4.2: LMU reference sensitivity levels** + +| LMU Class | Reference measurement channel data rate | LMU sensitivity level (dBm) | BER | +|------------------|-----------------------------------------|-----------------------------|----------------------------| +| Wide Area LMU | 12.2 kbps | -121 | BER shall not exceed 0.001 | +| Medium Range LMU | 12.2 kbps | -111 | BER shall not exceed 0.001 | + +## 5.4 Dynamic range + +Receiver dynamic range is the receiver ability to handle a rise of interference in the reception frequency channel. The receiver shall fulfil a specified BER requirement for a specified sensitivity degradation of the wanted signal in the presence of an interfering AWGN signal in the same reception frequency channel. + +The BER shall not exceed 0.001 for the parameters specified in Table 4.3. + +**Table 4.3: Dynamic range** + +| Parameter | Level Wide Area LMU | Level Medium Range LMU | Unit | +|-----------------------------------------|---------------------|------------------------|--------------| +| Reference measurement channel data rate | 12.2 | 12.2 | kbps | +| Wanted signal mean power | -91 | -81 | dBm | +| Interfering AWGN signal | -73 | -63 | dBm/3.84 MHz | + +## 5.5 Adjacent Channel Selectivity (ACS) + +Adjacent channel selectivity (ACS) is a measure of the LMU receiver ability to receive a wanted signal at its assigned channel frequency in the presence of an adjacent channel signal at a given frequency offset from the centre frequency of the assigned channel. ACS is the ratio of the LMU receiver filter attenuation on the assigned channel frequency to the receiver filter attenuation on the adjacent channel(s). + +The interference signal is offset from the wanted signal by the frequency offset Fuw. The interference signal shall be a W-CDMA signal as specified in Annex C of TS 25.104 [1]. + +The BER shall not exceed 0.001 for the parameters specified in Table 4.4. + +**Table 4.4: LMU Adjacent channel selectivity** + +| Parameter | Level Wide Area LMU | Level Medium Range LMU | Unit | +|-------------------------------|---------------------|------------------------|------| +| Data rate | 12.2 | 12.2 | kbps | +| Wanted signal mean power | -115 | -105 | dBm | +| Interfering signal mean power | -52 | -42 | dBm | +| Fuw offset (Modulated) | 5 | 5 | MHz | + +## 5.6 Blocking characteristics + +The blocking characteristics are a measure of the LMU receiver ability to receive a wanted signal at its assigned channel frequency in the presence of an unwanted interferer on frequencies other than those of the adjacent channels. The performance as specified in Table 4.5-4.10 shall be met with a wanted and an interfering signal coupled to the LMU antenna input using the following parameters for the blocking and narrowband blocking requirements: + +**Table 4.5: Blocking performance requirement for Wide Area LMU** + +| Operating Band | Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------|----------------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------| +| I | 1920 – 1980 MHz | -40 dBm | -115 dBm | 10 MHz | WCDMA signal * | +| | 1900 – 1920 MHz
1980 – 2000 MHz | -40 dBm | -115 dBm | 10 MHz | WCDMA signal * | +| | 1 MHz -1900 MHz
2000 MHz – 12750 MHz | -15 dBm | -115 dBm | — | CW carrier | +| II | 1850 – 1910 MHz | -40 dBm | -115 dBm | 10 MHz | WCDMA signal * | +| | 1830 – 1850 MHz
1910 – 1930 MHz | -40 dBm | -115 dBm | 10 MHz | WCDMA signal * | +| | 1 MHz – 1830 MHz
1930 MHz – 12750 MHz | -15 dBm | -115 dBm | — | CW carrier | +| III | 1710 – 1785 MHz | -40 dBm | -115 dBm | 10 MHz | WCDMA signal * | +| | 1690 – 1710 MHz
1785 – 1805 MHz | -40 dBm | -115 dBm | 10 MHz | WCDMA signal * | +| | 1 MHz – 1690 MHz
1805 MHz – 12750 MHz | -15 dBm | -115 dBm | — | CW carrier | +| IV | 1710 – 1755 MHz | -40 dBm | -115 dBm | 10 MHz | WCDMA signal * | +| | 1690 – 1710 MHz
1755 – 1775 MHz | -40 dBm | -115 dBm | 10 MHz | WCDMA signal * | +| | 1 MHz – 1690 MHz
1775 MHz – 12750 MHz | -15 dBm | -115 dBm | — | CW carrier | +| V | 824-849 MHz | -40 dBm | -115 dBm | 10 MHz | WCDMA signal * | +| | 804-824 MHz
849-869 MHz | -40 dBm | -115 dBm | 10 MHz | WCDMA signal * | +| | 1 MHz – 804 MHz
869 MHz – 12750 MHz | -15 dBm | -115 dBm | — | CW carrier | +| VI | 810 – 830 MHz
840 – 860 MHz | -40 dBm | -115 dBm | 10 MHz | WCDMA signal * | +| | 1 MHz – 810 MHz
860 MHz – 12750 MHz | -15 dBm | -115 dBm | — | CW carrier | +| VII | 2500 – 2570 MHz | -40 dBm | -115 dBm | 10 MHz | WCDMA signal * | +| | 2480 – 2500 MHz
2570 – 2590 MHz | -40 dBm | -115 dBm | 10 MHz | WCDMA signal * | +| | 1 MHz -2480 MHz
2590 MHz – 12750 MHz | -15 dBm | -115 dBm | — | CW carrier | +| VIII | 880 – 915 MHz | -40 dBm | -115 dBm | 10 MHz | WCDMA signal * | +| | 860 – 880 MHz
915 – 925 MHz | -40 dBm | -115 dBm | 10 MHz | WCDMA signal * | +| | 1 MHz -860 MHz
925 MHz – 12750 MHz | -15 dBm | -115 dBm | — | CW carrier | +| IX | 1749.9 – 1784.9 MHz | -40 dBm | -115 dBm | 10 MHz | WCDMA signal * | +| | 1729.9 – 1749.9 MHz
1784.9 – 1804.9 MHz | -40 dBm | -115 dBm | 10 MHz | WCDMA signal * | +| | 1 MHz – 1729.9 MHz
1804.9 MHz – 12750 MHz | -15 dBm | -115 dBm | — | CW carrier | +| X | 1710 – 1770 MHz | -40 dBm | -115 dBm | 10 MHz | WCDMA signal * | +| | 1690 – 1710 MHz
1770 – 1790 MHz | -40 dBm | -115 dBm | 10 MHz | WCDMA signal * | +| | 1 MHz – 1690 MHz
1790 MHz – 12750 MHz | -15 dBm | -115 dBm | — | CW carrier | + +NOTE \*: The characteristics of the W-CDMA interference signal are specified in Annex C of [1] + +**Table 4.6: Blocking performance requirement for the Medium range LMU** + +| Operating Band | Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------|----------------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------| +| I | 1920 – 1980 MHz | -35 dBm | -105 dBm | 10 MHz | WCDMA signal * | +| | 1900 – 1920 MHz
1980 – 2000 MHz | -35 dBm | -105 dBm | 10 MHz | WCDMA signal * | +| | 1 MHz -1900 MHz
2000 MHz – 12750 MHz | -15 dBm | -105 dBm | — | CW carrier | +| II | 1850 – 1910 MHz | -35 dBm | -105 dBm | 10 MHz | WCDMA signal * | +| | 1830 – 1850 MHz
1910 – 1930 MHz | -35 dBm | -105 dBm | 10 MHz | WCDMA signal * | +| | 1 MHz – 1830 MHz
1930 MHz – 12750 MHz | -15 dBm | -105 dBm | — | CW carrier | +| III | 1710 – 1785 MHz | -35 dBm | -105 dBm | 10 MHz | WCDMA signal * | +| | 1690 – 1710 MHz
1785 – 1805 MHz | -35 dBm | -105 dBm | 10 MHz | WCDMA signal * | +| | 1 MHz – 1690 MHz
1805 MHz – 12750 MHz | -15 dBm | -105 dBm | — | CW carrier | +| IV | 1710 – 1755 MHz | -35 dBm | -105 dBm | 10 MHz | WCDMA signal * | +| | 1690 – 1710 MHz
1755 – 1775 MHz | -35 dBm | -105 dBm | 10 MHz | WCDMA signal * | +| | 1 MHz – 1690 MHz
1775 MHz – 12750 MHz | -15 dBm | -105 dBm | — | CW carrier | +| V | 824-849 MHz | -35 dBm | -105 dBm | 10 MHz | WCDMA signal * | +| | 804-824 MHz
849-869 MHz | -35 dBm | -105 dBm | 10 MHz | WCDMA signal * | +| | 1 MHz – 804 MHz
869 MHz – 12750 MHz | -15 dBm | -105 dBm | — | CW carrier | +| VI | 810 – 830 MHz
840 – 860 MHz | -35 dBm | -105 dBm | 10 MHz | WCDMA signal * | +| | 1 MHz – 810 MHz
860 MHz – 12750 MHz | -15 dBm | -105 dBm | — | CW carrier | +| VII | 2500 – 2570 MHz | -35 dBm | -105 dBm | 10 MHz | WCDMA signal * | +| | 2480 – 2500 MHz
2570 – 2590 MHz | -35 dBm | -105 dBm | 10 MHz | WCDMA signal * | +| | 1 MHz -2480 MHz
2590 MHz – 12750 MHz | -15 dBm | -105 dBm | — | CW carrier | +| VIII | 880 – 915 MHz | -35 dBm | -105 dBm | 10 MHz | WCDMA signal * | +| | 860 – 880 MHz
915 – 925 MHz | -35 dBm | -105 dBm | 10 MHz | WCDMA signal * | +| | 1 MHz -860 MHz
925 MHz – 12750 MHz | -15 dBm | -105 dBm | — | CW carrier | +| IX | 1749.9 – 1784.9 MHz | -35 dBm | -105 dBm | 10 MHz | WCDMA signal * | +| | 1729.9 – 1749.9 MHz
1784.9 – 1804.9 MHz | -35 dBm | -105 dBm | 10 MHz | WCDMA signal * | +| | 1 MHz – 1729.9 MHz
1804.9 MHz – 12750 MHz | -15 dBm | -105 dBm | — | CW carrier | +| X | 1710 – 1770 MHz | -35 dBm | -105 dBm | 10 MHz | WCDMA signal * | +| | 1690 – 1710 MHz
1770 – 1790 MHz | -35 dBm | -105 dBm | 10 MHz | WCDMA signal * | +| | 1 MHz – 1690 MHz
1790 MHz – 12750 MHz | -15 dBm | -105 dBm | — | CW carrier | + +NOTE \*: The characteristics of the W-CDMA interference signal are specified in Annex C of [1] + +**Table 4.7: Blocking performance requirement (narrowband) for the Wide Area LMU** + +| Operating Band | Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------| +| II | 1850 – 1910 MHz | - 47 dBm | -115 dBm | 2.7 MHz | GMSK modulated* | +| III | 1710 – 1785 MHz | - 47 dBm | -115 dBm | 2.8 MHz | GMSK modulated* | +| IV | 1710 – 1755 MHz | - 47 dBm | -115 dBm | 2.7 MHz | GMSK modulated* | +| V | 824 – 849 MHz | - 47 dBm | -115 dBm | 2.7 MHz | GMSK modulated* | +| VIII | 880 – 915 MHz | - 47 dBm | -115 dBm | 2.8 MHz | GMSK modulated* | +| X | 1710 – 1770 MHz | - 47 dBm | -115 dBm | 2.7 MHz | GMSK modulated* | + +NOTE \*: GMSK modulation as defined in TS 45.004 [2]. + +**Table 4.8: Narrowband blocking performance requirement for the Medium Range LMU** + +| Operating Band | Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------| +| II | 1850 – 1910 MHz | - 42 dBm | -105 dBm | 2.7 MHz | GMSK modulated* | +| III | 1710 – 1785 MHz | - 42 dBm | -105 dBm | 2.8 MHz | GMSK modulated* | +| IV | 1710 – 1755 MHz | - 42 dBm | -105 dBm | 2.7 MHz | GMSK modulated* | +| V | 824 – 849 MHz | - 42 dBm | -105 dBm | 2.7 MHz | GMSK modulated* | +| VIII | 880 – 915 MHz | - 42 dBm | -105 dBm | 2.8 MHz | GMSK modulated* | +| X | 1710 – 1770 MHz | - 42 dBm | -105 dBm | 2.7 MHz | GMSK modulated* | + +NOTE \*: GMSK modulation as defined in TS 45.004 [2]. + +Additional blocking requirements shall be applied for the protection of the LMU receiver in the presence of GSM900, DCS1800, PCS1900, GSM850, UTRA TDD, and UTRA FDD in bands I to X. + +**Table 4.9: Additional blocking performance requirement for Wide Area LMU.** + +| Co-located BS type | Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Type of Interfering Signal | +|-----------------------|----------------------------------------|-------------------------------|--------------------------|----------------------------| +| Macro GSM900 | 921 – 960 MHz | +16 dBm | -115 dBm | CW carrier | +| Macro DCS1800 | 1805 – 1880 MHz | +16 dBm | -115 dBm | CW carrier | +| Macro PCS1900 | 1930 – 1990 MHz | +16 dBm | -115 dBm | CW carrier | +| Macro GSM850 | 869 – 894 MHz | +16 dBm | -115 dBm | CW carrier | +| WA UTRA-FDD Band I | 2110 – 2170 MHz | +16 dBm | -115 dBm | CW carrier | +| WA UTRA-FDD Band II | 1930 – 1990 MHz | +16 dBm | -115 dBm | CW carrier | +| WA UTRA-FDD Band III | 1805 – 1880 MHz | +16 dBm | -115 dBm | CW carrier | +| WA UTRA-FDD Band IV | 2110 – 2155 MHz | +16 dBm | -115 dBm | CW carrier | +| WA UTRA-FDD Band V | 869 – 894 MHz | +16 dBm | -115 dBm | CW carrier | +| WA UTRA-FDD Band VI | 875 – 885 MHz | +16 dBm | -115 dBm | CW carrier | +| WA UTRA-FDD Band VII | 2620 – 2690 MHz | +16 dBm | -115 dBm | CW carrier | +| WA UTRA-FDD Band VIII | 925 – 960 MHz | +16 dBm | -115 dBm | CW carrier | +| WA UTRA-FDD Band IX | 1844.9 – 1879.9 MHz | +16 dBm | -115 dBm | CW carrier | +| WA UTRA-FDD Band X | 2110 – 2170 MHz | +16 dBm | -115 dBm | CW carrier | + +**Table 4.10: Additional blocking performance requirements for the LMU** + +| Co-located BS type | Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Type of Interfering Signal | +|-----------------------|----------------------------------------|-------------------------------|--------------------------|----------------------------| +| Micro GSM900 | 921 – 960 MHz | -3 dBm | -105 dBm | CW carrier | +| Micro DCS1800 | 1805 – 1880 MHz | +5 dBm | -105 dBm | CW carrier | +| Micro PCS1900 | 1930 – 1990 MHz | +5 dBm | -105 dBm | CW carrier | +| Micro GSM850 | 869 – 894 MHz | -3 dBm | -105 dBm | CW carrier | +| MR UTRA-FDD Band I | 2110 – 2170 MHz | +8 dBm | -105 dBm | CW carrier | +| MR UTRA-FDD Band II | 1930 – 1990 MHz | +8 dBm | -105 dBm | CW carrier | +| MR UTRA-FDD Band III | 1805 – 1880 MHz | +8 dBm | -105 dBm | CW carrier | +| MR UTRA-FDD Band IV | 2110 – 2155 MHz | +8 dBm | -105 dBm | CW carrier | +| MR UTRA-FDD Band V | 869 – 894 MHz | +8 dBm | -105 dBm | CW carrier | +| MR UTRA-FDD Band VI | 875 – 885 MHz | +8 dBm | -105 dBm | CW carrier | +| MR UTRA-FDD Band VII | 2620 – 2690 MHz | +8 dBm | -105 dBm | CW carrier | +| MR UTRA-FDD Band VIII | 925 – 960 MHz | +8 dBm | -105 dBm | CW carrier | +| MR UTRA-FDD Band IX | 1844.9 – 1879.9 MHz | +8 dBm | -105 dBm | CW carrier | +| MR UTRA-FDD Band X | 2110 – 2170 MHz | +8 dBm | -105 dBm | CW carrier | + +An additional blocking requirement may be applied for the protection of the LMU receivers when UTRA TDD is co-located with an LMU. + +The current state-of-the-art technology does not allow a single generic solution for co-location with UTRA-TDD on adjacent frequencies for 30dB BS-BS minimum coupling loss. + +However, there are certain site-engineering solutions that can be used in these cases. These techniques are addressed in TR 25.942 [4]. + +For an LMU, the static reference performance as specified in clause 5.3 should be met with a wanted and an interfering signal coupled to BS antenna input using the parameters in Table 4.11. + +**Table 4.11: Blocking performance requirement for a Wide Area LMU when co-located with UTRA TDD BS in other bands.** + +| Co-located BS type | Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Type of Interfering Signal | +|--------------------|----------------------------------------|-------------------------------|--------------------------|----------------------------| +| Wide Area TDD | 2585 – 2620 MHz | +16 dBm | -115 dBm | CW carrier | + +## 5.7 Intermodulation characteristics + +Third and higher order mixing of the two interfering RF signals can produce an interfering signal in the band of the desired channel. Intermodulation response rejection is a measure of the capability of the receiver to receive a wanted signal on its assigned channel frequency in the presence of two or more interfering signals which have a specific frequency relationship to the wanted signal. + +The static reference performance as specified in clause 5.3 shall be met for a LMU when the following signals are coupled to LMU antenna input: + +- A wanted signal at the assigned channel frequency with a mean power of -115 dBm. +- Two interfering signals with the following parameters. + +**Table 4.12: Intermodulation performance requirement (Wide Area LMU)** + +| Operating band | Interfering Signal mean power | Offset | Type of Interfering Signal | +|----------------|---------------------------------------------------------------------------------------|--------|----------------------------| +| All bands | - 48 dBm | 10 MHz | CW signal | +| | - 48 dBm | 20 MHz | WCDMA signal * | +| Note*: | The characteristics of the W-CDMA interference signal are specified in Annex C of [1] | | | + +**Table 4.13: Narrowband intermodulation performance requirement (Wide Area LMU)** + +| Operating band | Interfering Signal mean power | Offset | Type of Interfering Signal | +|-----------------------------------|-------------------------------|---------|----------------------------| +| II, III, IV, V, VIII, X | - 47 dBm | 3.5 MHz | CW signal | +| | - 47 dBm | 5.9 MHz | GMSK modulated* | +| * GMSK as defined in TS45.004 [2] | | | | + +The static reference performance as specified in clause 5.3 shall be met for a Medium Range LMU when the following signals are coupled to LMU antenna input: + +- A wanted signal at the assigned channel frequency with a mean power of -105 dBm. +- Two interfering signals with the following parameters. + +**Table 4.14: Intermodulation performance requirement (Medium Range LMU)** + +| Operating band | Interfering Signal mean power | Offset | Type of Interfering Signal | +|----------------------------------------------------------------------------------------------|-------------------------------|--------|----------------------------| +| All bands | - 44 dBm | 10 MHz | CW signal | +| | - 44 dBm | 20 MHz | WCDMA signal * | +| Note*: The characteristics of the W-CDMA interference signal are specified in Annex C of [1] | | | | + +**Table 4.15: Narrowband intermodulation performance requirement (Medium Range LMU)** + +| Operating band | Interfering Signal mean power | Offset | Type of Interfering Signal | +|-----------------------------------|-------------------------------|---------|----------------------------| +| II, III, IV, V, VIII, X | - 43 dBm | 3.5 MHz | CW signal | +| | - 43 dBm | 5.9 MHz | GMSK modulated* | +| * GMSK as defined in TS45.004 [2] | | | | + +## 5.8 Spurious emissions + +The spurious emissions power is the power of emissions generated or amplified in a receiver that appear at the LMU antenna connector. + +The power of any spurious emission shall not exceed: + +**Table 4.16: General LMU spurious emission requirement** + +| Band | Maximum level | Measurement Bandwidth | Note | +|-------------------|---------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| 30MHz – 1 GHz | -57 dBm | 100 kHz | | +| 1 GHz – 12.75 GHz | -47 dBm | 1 MHz | With the exception of frequencies between 12.5 MHz below the first carrier frequency and 12.5 MHz above the last carrier frequency used by the LMU. | + +In addition the following requirements shall be applied for the protection of UE, MS, and Node B, BS of the same and other systems, where the power of any spurious emission shall not exceed the limits: + +**Table 4.17: Additional LMU Spurious emissions limits** + +| Operating Band | Band | Maximum level | Measurement Bandwidth | Note | +|----------------|---------------------|---------------|-----------------------|------| +| I | 1920 – 1980 MHz | -78 dBm | 3.84 MHz | | +| II | 1850 – 1910 MHz | -78 dBm | 3.84 MHz | | +| III | 1710 – 1785 MHz | -78 dBm | 3.84 MHz | | +| IV | 1710 – 1755 MHz | -78 dBm | 3.84 MHz | | +| V | 824 – 849 MHz | -78 dBm | 3.84 MHz | | +| VI | 815 – 850 MHz | -78 dBm | 3.84 MHz | | +| VII | 2500 – 2570 MHz | -78 dBm | 3.84 MHz | | +| VIII | 880 – 915 MHz | -78 dBm | 3.84 MHz | | +| IX | 1749.9 – 1784.9 MHz | -78 dBm | 3.84 MHz | | +| X | 1710 – 1770 MHz | -78 dBm | 3.84 MHz | | + +In addition, the requirement in Table 4.18 may be applied to geographic areas in which both UTRA-TDD and UTRA-FDD are deployed. + +**Table 4.18: Additional spurious emission requirements for the TDD bands** + +| Operating Band | Band | Maximum level | Measurement Bandwidth | Note | +|----------------|------------------------------------|---------------|-----------------------|-------------------------| +| I | 1900 – 1920 MHz
2010 – 2025 MHz | -78 dBm | 3.84 MHz | Not applicable in Japan | +| | 2010 – 2025 MHz | -52 dBm | 1MHz | Applicable in Japan | +| VI, IX | 2010 – 2025 MHz | -52 dBm | 1MHz | | + +# 6 LMU measurement requirements + +## 6.1 General + +All tests at specified detection levels require that the LMU detection threshold be set such that the false alarm rate is at or below 5 % when no signal is present (noise only). + +## 6.2 RRC States supported + +UTDOA positioning technique does work in CELL\_DCH and CELL\_FACH state, not in URA\_PCH nor CELL\_PCH state. + +## 6.3 Maximum response times + +- 1) The maximum time for a Master LMU to establish a reference signal shall be, after the data capture has started, less than 5 seconds. +- 2) The maximum time for the distribution of the reference signal to another LMU involved in the positioning shall be less than 3 seconds. +- 3) The maximum time of detection of the time of arrival in an LMU given the reference signal shall be less than 15 seconds. + +## 6.4 Nominal time accuracy + +Nominal Time Accuracy requirement verifies the difference between the detected time of arrival and the real time of arrival. + +In an AWGN environment with no fading or multi-paths, the standard deviation of the timing error of the LMU shall be less than 30 ns when the signal presence is correctly detected. + +## 6.5 Multipath scenarios + +The purpose of the test case is to verify the LMU receiver's performance in multipath. + +For the 12.2 kbps reference measurement channel specified in 3GPP TS 25.104 Annex A [1], and with Rx diversity (using both diversity paths), the LMU shall be capable of detecting the earliest path, for at least 90 % of the location attempts, at the levels in Table 5.1. + +Nominal time accuracy for multipath fading scenarios includes an additional chip duration of 260 nanoseconds over that in Section 5.4. + +**Table 5.1: Multipath detection level** + +| Propagation condition | Detection level: Signal to Noise level in (dB) | Note | +|-------------------------|------------------------------------------------|--------| +| Static (AWGN) | -51.2 dB | NOTE 1 | +| Multipath fading Case 1 | -47.2dB | NOTE 2 | +| Multipath fading Case 2 | - 43.8 dB | NOTE 2 | +| Multipath fading Case 3 | - 41.9 dB | NOTE 2 | +| Multipath fading Case 4 | - 39.8 dB | NOTE 2 | + +NOTE 1: Static propagation condition is described in 3GPP TS 25.104 Annex B.1 [1]. + +NOTE 2: Multipath-fading case 1-4 is described in 3GPP TS 25.104 Annex B.2 [1]. + +## 6.6 Moving scenario + +The purpose of the test case is to verify the LMU receiver's performance to Doppler shift. + +In an AWGN environment with no fading or multi-paths, and at a speed of 250km/h, the detectability of the LMU shall be degraded by no more than 1.5 dB. + +## 6.7 Cross correlation + +The ability of the LMU to detect a weak terminal signal in the presence of a strong other terminal is covered in Section 5.5 when the other terminal interference is modelled as AWGN. + +# Annex A (informative): Change history + +| Change history | | | | | | | | | +|----------------|-------|-----------|----|-----|-----------------------------------------------------------------------|-----|--------|--------| +| Date | TSG | Doc. | CR | Rev | Subject/Comment | Cat | Old | New | +| 2005-08 | | | | | Initial version created | | | 0.1.0 | +| 2007-11 | | | | | Incorporate simulation results and synchronize with TS.104 | | 0.1.0 | 1.0.0 | +| 2007-12 | 38 | RP-071015 | | | Approved version at RAN TSG # 38 | | 1.0.0 | 7.0.0 | +| 2008-03 | 39 | RP-080122 | 1 | | Correcting multipath detection level in LMU performance specification | F | 7.0.0 | 7.1.0 | +| 2008-12 | SP-42 | | | | Upgraded unchanged from Rel-7 | | | 8.0.0 | +| 2009-12 | SP-46 | | | | Upgraded unchanged from Rel-8 | | | 9.0.0 | +| | SP-51 | | | | Upgraded unchanged from Rel-9 | | 9.0.0 | 10.0.0 | +| 2012-09 | SP-57 | - | - | - | Update to Rel-11 version (MCC) | | 10.0.0 | 11.0.0 | +| 2014-09 | SP-65 | - | - | - | Update to Rel-12 version (MCC) | | 11.0.0 | 12.0.0 | +| 2016-01 | SP-70 | - | - | - | Update to Rel-13 version (MCC) | | 12.0.0 | 13.0.0 | +| 2017-03 | RP-75 | - | - | - | Update to Rel-14 version (MCC) | | 13.0.0 | 14.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2018-06 | SA#80 | - | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-06 | SA#88 | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25116/0332672e127cd13bb6d2fc8d1e27bfa2_img.jpg b/marked/Rel-16/25_series/25116/0332672e127cd13bb6d2fc8d1e27bfa2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e65eb77bb459909d60d72f3fa7d8d6c45fac060 --- /dev/null +++ b/marked/Rel-16/25_series/25116/0332672e127cd13bb6d2fc8d1e27bfa2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a340c340e2f774bcac90af81cef71f1c1a1206864a71e44fdbd0a49f64a534a5 +size 46943 diff --git a/marked/Rel-16/25_series/25116/5adf12d50dfea82178ca002a2c48641b_img.jpg b/marked/Rel-16/25_series/25116/5adf12d50dfea82178ca002a2c48641b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff777d8f231b3016c4f55822e0a246dbd2667987 --- /dev/null +++ b/marked/Rel-16/25_series/25116/5adf12d50dfea82178ca002a2c48641b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d50e6a3f8260ce3b3bef515d051e3faacea5917d14aaa626849a7e92289abf9a +size 31563 diff --git a/marked/Rel-16/25_series/25116/85ad73d1c8ff59cd647b95f084937bc0_img.jpg b/marked/Rel-16/25_series/25116/85ad73d1c8ff59cd647b95f084937bc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b06ef78cc6e11158ddaecd9fde976bc2a16af7f6 --- /dev/null +++ b/marked/Rel-16/25_series/25116/85ad73d1c8ff59cd647b95f084937bc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef7446b75584f0989d615838192de829ac7cafef19dfec22310565f929746783 +size 29093 diff --git a/marked/Rel-16/25_series/25116/raw.md b/marked/Rel-16/25_series/25116/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..83030d0b75b5450e01dc7a86455c66a4783e2935 --- /dev/null +++ b/marked/Rel-16/25_series/25116/raw.md @@ -0,0 +1,786 @@ + + + + + + +# Contents + +| | | +|---------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 7 | +| 4 General..... | 7 | +| 4.1 Relationship between Minimum Requirements and Test Requirements ..... | 8 | +| 4.2 Regional requirements..... | 9 | +| 5 Frequency bands and channel arrangement ..... | 10 | +| 5.1 General ..... | 10 | +| 5.2 Frequency bands..... | 10 | +| 5.3 TX-RX frequency separation ..... | 10 | +| 5.4 Channel arrangement..... | 11 | +| 5.4.1 Channel spacing..... | 11 | +| 5.4.2 Channel raster..... | 11 | +| 5.4.3 Channel number..... | 11 | +| 6 Output power..... | 11 | +| 6.1 Maximum output power..... | 11 | +| 6.1.1 Minimum Requirements..... | 11 | +| 7 Frequency stability..... | 12 | +| 7.1 Minimum requirement..... | 12 | +| 8 Out of band gain..... | 12 | +| 8.1 Minimum requirement..... | 12 | +| 9 Unwanted emission..... | 13 | +| 9.1 Spectrum emission mask..... | 13 | +| 9.2 Spurious emissions..... | 14 | +| 9.2.1 Mandatory Requirements ..... | 15 | +| 9.2.1.1 Spurious emissions (Category A) ..... | 15 | +| 9.2.1.1.1 Minimum Requirement ..... | 15 | +| 9.2.1.2 Spurious emissions (Category B) ..... | 15 | +| 9.2.1.2.1 Minimum Requirement ..... | 15 | +| 9.2.2 Co-existence with GSM 900 ..... | 16 | +| 9.2.2.1 Operation in the same geographic area..... | 16 | +| 9.2.2.1.1 Minimum Requirement ..... | 16 | +| 9.2.2.2 Co-located base stations..... | 16 | +| 9.2.2.2.1 Minimum Requirement ..... | 16 | +| 9.2.3 Co-existence with DCS 1800 ..... | 16 | +| 9.2.3.1 Operation in the same geographic area..... | 16 | +| 9.2.3.1.1 Minimum Requirement ..... | 16 | +| 9.2.3.2 Co-located base stations..... | 17 | +| 9.2.3.2.1 Minimum Requirement ..... | 17 | +| 9.2.4 Co-existence with UTRA-FDD..... | 17 | +| 9.2.4.1 Operation in the same geographic area..... | 17 | +| 9.2.4.1.1 Minimum Requirement ..... | 17 | +| 9.2.4.2 Co-located base stations..... | 18 | +| 9.2.4.2.1 Minimum Requirement ..... | 18 | +| 9.2.5 Co-existence with unsynchronised TDD..... | 18 | +| 9.2.5.1 Operation in the same geographic area..... | 18 | +| 9.2.5.1.1 Minimum Requirement ..... | 19 | +| 9.2.5.2 Co-located base stations..... | 19 | +| 9.2.5.2.1 Minimum Requirement ..... | 19 | + +| | | | +|-----------------------------|--------------------------------------------------------------------|-----------| +| 10 | Modulation accuracy..... | 20 | +| 10.1 | Error Vector Magnitude ..... | 20 | +| 10.1.1 | Minimum requirement..... | 20 | +| 10.2 | Peak code domain error..... | 20 | +| 10.2.1 | Minimum requirement..... | 20 | +| 11 | Input intermodulation..... | 20 | +| 11.1 | General requirement..... | 20 | +| 11.1.1 | Minimum requirement..... | 20 | +| 12 | Output intermodulation..... | 21 | +| 12.0 | General ..... | 21 | +| 12.1 | Minimum requirement..... | 21 | +| 13 | Adjacent Channel Rejection Ratio (ACRR) ..... | 21 | +| 13.1 | Definitions and applicability ..... | 21 | +| 13.2 | Co-existence with UTRA..... | 21 | +| 13.2.1. | Minimum Requirements..... | 21 | +| 14 | Timing Accuracy..... | 22 | +| 14.1 | Minimum requirement..... | 22 | +| Annex A (normative): | Environmental requirements for the Repeater equipment ..... | 24 | +| Annex B (informative): | Change history..... | 25 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd 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 establishes the minimum RF characteristics of LCR TDD Repeater. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] ITU-R Recommendation SM.329, "Unwanted emissions in the spurious domain". +- [3] ITU-R Recommendation M.1545: "Measurement uncertainty as it applies to test limits for the terrestrial component of International Mobile Telecommunications-2000". +- [4] 3GPP TS 25.153: "LCR TDD Repeater conformance testing" +- [5] 3GPP TR 25.942: "RF system scenarios". +- [6] IEC 60721-3-3 (2002): "Classification of environmental conditions - Part 3: Classification of groups of environmental parameters and their severities - Section 3: Stationary use at weather protected locations". +- [7] IEC 60721-3-4 (1995): "Classification of environmental conditions - Part 3: Classification of groups of environmental parameters and their severities - Section 4: Stationary use at non-weather protected locations". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**Carrier:** The modulated waveform conveying the LCR TDD physical channels + +**Channel bandwidth:** The RF bandwidth supporting a single LCR TDD RF carrier with the transmission bandwidth configured in the uplink or downlink of a cell. The channel bandwidth is measured in MHz and is used as a reference for transmitter and receiver RF requirements. + +**Channel edge:** The lowest and highest frequency of the LCR TDD carrier, separated by the channel bandwidth. + +**Donor coupling loss:** is the coupling loss between the repeater and the donor base station. + +**Downlink:** Signal path where base station transmits and mobile receives. + +**Maximum output power, Pmax:** This is the mean power level per carrier measured at the antenna connector of the Repeater in specified reference condition. + +**Output power, Pout:** This is the mean power of one carrier at maximum repeater gain delivered to a load with resistance equal to the nominal load impedance of the transmitter. + +**Pass band:** The repeater can have one or several pass bands. The pass band is the frequency range that the repeater operates in with operational configuration. This frequency range can correspond to one or several consecutive nominal channels. If they are not consecutive each subset of channels shall be considered as an individual pass band. + +**Rated output power:** Rated output power of the repeater is the mean power level per carrier that the manufacturer has declared to be available at the antenna connector. + +**Repeater:** A device that receives, amplifies and transmits the radiated or conducted RF carrier both in the down-link direction (from the base station to the mobile area) and in the up-link direction (from the mobile to the base station) + +**Transmission bandwidth:** Bandwidth of an instantaneous transmission from a UE or BS, measured in Resource Block units. + +**Transmission bandwidth configuration:** The highest transmission bandwidth allowed for uplink or downlink in a given channel bandwidth, measured in Resource Block units. + +**Uplink:** Signal path where mobile transmits and base station receives. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|------------------------|----------------------------------------------------------------------------------------| +| BW Channel | Channel bandwidth | +| BW Config | Transmission bandwidth configuration, expressed in MHz. | +| BW Meas | Measurement bandwidth | +| BW Signal | Bandwidth of the repeater input signal filling the repeater pass band | +| F DL_low | The lowest frequency of the downlink operating band | +| F DL_high | The highest frequency of the downlink operating band | +| F UL_low | The lowest frequency of the uplink operating band | +| F UL_high | The highest frequency of the uplink operating band | +| f offset_PB | Distance from the channel edge frequency of the first or last channel in the pass band | +| N DL | Downlink LARFCN | +| N offs-DL | Offset used for calculating downlink LARFCN | +| N offs-UL | Offset used for calculating uplink LARFCN | +| N RB | Transmission bandwidth configuration, expressed in units of resource blocks | +| N UL | Uplink LARFCN | +| P max | Maximum output power | +| P out | Output power | + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|--------|-------------------------------------------------| +| ACRR | Adjacent Channel Rejection Ratio | +| BS | Base Station | +| LARFCN | LCR TDD Absolute Radio Frequency Channel Number | +| PB | Pass Band | + +# 4 General + +This specification applies only to LCR TDD repeaters. + +Unless otherwise stated, all requirements in this specification apply to both the up-link and down-link directions. + +## 4.1 Relationship between Minimum Requirements and Test Requirements + +The Minimum Requirements given in this specification make no allowance for measurement uncertainty. The test specification TS 25.153 section 4 defines Test Tolerances. These Test Tolerances are individually calculated for each test. The Test Tolerances are used to relax the Minimum Requirements in this specification to create Test Requirements. + +The measurement results returned by the Test System are compared - without any modification - against the Test Requirements as defined by the shared risk principle. + +The Shared Risk principle is defined in ITU-R M.1545 [3]. + +## 4.2 Regional requirements + +Some requirements in the present document may only apply in certain regions. Table 4.2-1 lists all requirements that may be applied differently in different regions. + +**Table 4.2-1: List of regional requirements** + +| Clause number | Requirement | Comments | +|---------------|------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 5.2 | Channel bandwidth | Some channel bandwidths may be applied regionally. | +| 5.3 | Frequency bands | Some bands may be applied regionally. | +| 5.4 | Channel arrangement | The requirement is applied according to what frequency bands in Clause 5.3 that are supported by the Repeater. | +| 6.1 | Maximum output power | In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the range of conditions defined as normal. | +| 9.1.1.1 | Operating band unwanted emissions (Category A) | This requirement is mandatory for regions where Category A limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [2] apply. | +| 9.1.1.2 | Operating band unwanted emissions (Category B) | This requirement is mandatory for regions where Category B limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [2], apply. | +| 9.1.3 | Operating band unwanted emissions : Additional requirements | These requirements may be applied regionally for some operating bands. | +| 9.2.1.1 | Spurious emissions (Category A) | This requirement is mandatory for regions where Category A limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [2] apply. | +| 9.2.1.2 | Spurious emissions (Category B) | This requirement is mandatory for regions where Category B limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [2], apply. | +| 9.2.2.1 | Co-existence with GSM900 - Operation in the same geographic area | This requirement may be applied for the protection of GSM 900 MS and GSM 900 BTS in geographic areas in which both GSM 900 and LCR TDD repeater are deployed. | +| 9.2.2.2 | Co-existence with GSM900 - Co-located base stations | This requirement may be applied for the protection of GSM 900 BTS receivers when GSM 900 BTS and LCR TDD repeater are co-located. | +| 9.2.3.1 | Co-existence with DCS1800 - Operation in the same geographic area | This requirement may be applied for the protection of DCS 1800 MS and DCS 1800 BTS in geographic areas in which both DCS 1800 and LCR TDD repeater are deployed. | +| 9.2.3.2 | Co-existence with DCS1800 - Co-located base stations | This requirement may be applied for the protection of DCS 1800 BTS receivers when DCS 1800 BTS and LCR TDD repeater are co-located. | +| 9.2.4.1 | Co-existence with UTRA FDD - Operation in the same geographic area | This requirement may be applied to geographic areas in which both LCR TDD repeater and UTRA-FDD are deployed. | +| 9.2.4.2 | Co-existence with UTRA FDD - Co-located base stations | This requirement may be applied for the protection of UTRA-FDD BS receivers when LCR TDD repeater and UTRA FDD BS are co-located. | +| 9.2.5.1 | Co-existence with unsynchronized TDD - Operation in the same geographic area | This requirement may be applied for the protection of UTRA-TDD BS receivers in same geographic areas in which unsynchronized TDD is deployed. | +| 9.2.5.2 | Co-existence with unsynchronized TDD -Co-located base stations | This requirement may be applied for the protection of UTRA-TDD BS receivers when UTRA-TDD BS are unsynchronized co-located. | +| 11.2 | Input Intermodulation: Co-location with other systems | These requirements may be applied for the protection of FDD Repeater input when GSM900, DCS1800, PCS1900, GSM850, UTRA FDD, UTRA TDD and/or E-UTRA BS are co-located with an LCR TDD Repeater. | +| 11.3 | Input Intermodulation: Co-existence with other systems | These requirements may be applied when GSM900, DCS1800, PCS1900, GSM850, UTRA FDD, UTRA TDD and/or E-UTRA BS operating in another frequency band co-exist with an LCR TDD Repeater. | + +# --- 5 Frequency bands and channel arrangement + +## 5.1 General + +The information presented in this section is based on the chip rates of 1.28 Mcps TDD. + +NOTE: Other chip rates may be considered in future releases. + +## 5.2 Frequency bands + +UTRA/TDD is designed to operate in the following bands; + +- a) 1900 - 1920 MHz: Uplink and downlink transmission +2010 - 2025 MHz Uplink and downlink transmission +- b) 1850 - 1910 MHz Uplink and downlink transmission +1930 - 1990 MHz Uplink and downlink transmission +- c) 1910 - 1930 MHz Uplink and downlink transmission +- d) 2570 - 2620 MHz Uplink and downlink transmission +- e) 2300 - 2400 MHz Uplink and downlink transmission +- f) 1880 - 1920 MHz: Uplink and downlink transmission + +Note: Deployment in existing and other frequency bands is not precluded. + +The co-existence of TDD and FDD in the same bands is still under study in WG4. + +## 5.3 TX-RX frequency separation + +No TX-RX frequency separation is required as Time Division Duplex (TDD) is employed. Each subframe consists of 7 main timeslots where all main timeslots (at least the first one) before the single switching point are allocated DL and all main timeslots (at least the last one) after the single switching point are allocated UL. + +## 5.4 Channel arrangement + +### 5.4.1 Channel spacing + +The channel spacing is 1.6MHz, but this can be adjusted to optimise performance in a particular deployment scenario. + +### 5.4.2 Channel raster + +The channel raster is 200 kHz for all bands, which means that the carrier frequency must be a multiple of 200 kHz. + +### 5.4.3 Channel number + +The carrier frequency is designated by the UTRA absolute radio frequency channel number (UARFCN). The value of the UARFCN in the IMT2000 band is defined in the general case as follows: + +$$N_t = 5 * F \qquad 0.0 \leq F \leq 3276.6 \text{ MHz}$$ + +where F is the carrier frequency in MHz. + +# --- 6 Output power + +Output power, $P_{out}$ , of the repeater is the mean power of one carrier at maximum repeater gain delivered to a load with resistance equal to the nominal load impedance of the transmitter. + +Rated output power, PRAT, of the repeater is the mean power level per carrier at maximum repeater gain that the manufacturer has declared to be available at the antenna connector. + +## 6.1 Maximum output power + +Maximum output power, Pmax, of the repeater is the mean power level per carrier measured at the antenna connector in specified reference condition. + +### 6.1.1 Minimum Requirements + +The requirements shall apply at maximum gain, with LCR TDD signals in the pass band of the repeater, at levels that produce the maximum rated output power per channel. + +When the power of all signals is increased by 10 dB, compared to the power level that produce the maximum rated output power, the requirements shall still be met. + +In normal conditions, the Repeater maximum output power shall remain within limits specified in Table 6.1 relative to the manufacturer's rated output power. + +**Table 6.1: Repeater output power; normal conditions** + +| Rated output power | Limit | +|--------------------|-----------------| +| $P \geq 31$ dBm | +2 dB and -2 dB | +| $P < 31$ dBm | +3 dB and -3 dB | + +In extreme conditions, the Repeater maximum output power shall remain within the limits specified in Table 6.2 relative to the manufacturer's rated output power. + +**Table 6.2: Repeater output power; extreme conditions** + +| Rated output power | Limit | +|--------------------|---------------------| +| $P \geq 31$ dBm | +2,5 dB and -2,5 dB | +| $P < 31$ dBm | +4 dB and -4 dB | + +In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the ranges of conditions defined as normal. + +# --- 7 Frequency stability + +Frequency stability is the ability to maintain the same frequency on the output signal with respect to the input signal. + +## 7.1 Minimum requirement + +The frequency deviation of the output signal with respect to the input signal shall be no more than $\pm 0,01$ ppm. + +# --- 8 Out of band gain + +Out of band gain refers to the gain of the repeater outside the pass band. + +## 8.1 Minimum requirement + +The intended use of a repeater in a system is to amplify the in band signals and not to amplify the out of band emission of the donor base station. + +In the intended application of the repeater, the out of band gain is less than the donor coupling loss. + +The repeater minimum donor coupling loss shall be declared by the manufacturer. This is this the minimum required attenuation between the donor BS and the repeater for proper repeater operation. + +The gain outside the pass band shall not exceed the maximum level specified in table 8.1, where: + +- $f\_offset$ is the distance from the centre frequency of the first or last channel within the pass band. + +**Table 8.1: Out of band gain limits 1** + +| Frequency offset from the carrier frequency, $f\_offset$ | Maximum gain | +|----------------------------------------------------------|--------------| +| $1,0 \leq f\_offset < 1,8$ MHz | 60 dB | +| $1,8 \leq f\_offset < 5,8$ MHz | 45 dB | +| $5,8 \leq f\_offset < 10,8$ MHz | 45 dB | +| $10,8$ MHz $\leq f\_offset$ | 35 dB | + +For $10,8$ MHz $\leq f\_offset$ the out of band gain shall not exceed the maximum gain of table 8.2 or the maximum gain stated in table 8.1 whichever is lower. + +**Table 8.2: Out of band gain limits 2** + +| Repeater maximum output power as in 9.1.1.1 | Maximum gain | +|-----------------------------------------------------------------------------|---------------------------------------------------------------------| +| $P < 31$ dBm | Out of band gain $\leq$ minimum donor coupling loss | +| $31$ dBm $\leq P < 43$ dBm | Out of band gain $\leq$ minimum donor coupling loss | +| $P \geq 43$ dBm | Out of band gain $\leq$ minimum donor coupling loss - ( $P-43$ dBm) | +| NOTE 1: The out of band gain is considered with $10,8$ MHz $\leq f\_offset$ | | + +# 9 Unwanted emission + +## 9.1 Spectrum emission mask + +The mask defined in Table 9.1 to 9.3 may be mandatory in certain regions. In other regions this mask may not be applied. + +For regions where this clause applies, the requirement shall be met by a LCR TDD repeater transmitting on a single RF carrier configured in accordance with the manufacturer's specification. Emissions shall not exceed the maximum level specified in table 9.1 to 9.3 for the appropriate LCR TDD repeater maximum output power, in the frequency range from $\Delta f = 0.8$ MHz to $\Delta f_{max}$ from the carrier frequency, where: + +- $\Delta f$ is the separation between the carrier frequency and the nominal -3dB point of the measuring filter closest to the carrier frequency. +- $f\_offset$ is the separation between the carrier frequency and the center frequency of the measuring filter. +- $f\_offset_{max}$ is either 4 MHz or the offset to the UMTS Tx band edge as defined in section 5.2, whichever is the greater. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measurement filter. + +![Illustrative diagram of spectrum emission mask. The graph shows power density in 30kHz [dBm] on the left y-axis (ranging from -45 to -20) and power density in 1 MHz [dBm] on the right y-axis (ranging from -30 to -5). The x-axis represents frequency separation Δf from the carrier [MHz] with markers at 0.8, 1.0, 1.8, 2.4, and Δf_max. Two masks are shown: one for P = 34 dBm (upper mask) and one for P = 26 dBm (lower mask). Both masks show a constant power density of -20 dBm in 30kHz from 0.8 to 1.0 MHz, followed by a 20 dB/decade roll-off until 1.8 MHz, where it flattens out at -28 dBm in 30kHz (or -13 dBm in 1 MHz) up to Δf_max.](0332672e127cd13bb6d2fc8d1e27bfa2_img.jpg) + +Illustrative diagram of spectrum emission mask. The graph shows power density in 30kHz [dBm] on the left y-axis (ranging from -45 to -20) and power density in 1 MHz [dBm] on the right y-axis (ranging from -30 to -5). The x-axis represents frequency separation Δf from the carrier [MHz] with markers at 0.8, 1.0, 1.8, 2.4, and Δf\_max. Two masks are shown: one for P = 34 dBm (upper mask) and one for P = 26 dBm (lower mask). Both masks show a constant power density of -20 dBm in 30kHz from 0.8 to 1.0 MHz, followed by a 20 dB/decade roll-off until 1.8 MHz, where it flattens out at -28 dBm in 30kHz (or -13 dBm in 1 MHz) up to Δf\_max. + +Illustrative diagram of spectrum emission mask + +Figure 9.1 + +Table 9.1: Spectrum emission mask values, BS maximum output power $P \geq 34$ dBm + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------------------------------------------------------------------|-----------------------| +| $0.8 \text{ MHz} \leq \Delta f < 1.0 \text{ MHz}$ | $0.815 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | -20 dBm | 30 kHz | +| $1.0 \text{ MHz} \leq \Delta f < 1.8 \text{ MHz}$ | $1.015 \text{ MHz} \leq f\_offset < 1.815 \text{ MHz}$ | $-20 \text{ dBm} - 10 \cdot \left( \frac{f\_offset}{\text{MHz}} - 1,015 \right) \text{ dB}$ | 30 kHz | +| See note | $1.815 \text{ MHz} \leq f\_offset < 2.3 \text{ MHz}$ | -28 dBm | 30 kHz | +| $1.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $2.3 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -13 dBm | 1 MHz | + +Table 9.2: Spectrum emission mask values, BS maximum output power $26 \leq P < 34$ dBm + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|-----------------------| +| $0.8 \text{ MHz} \leq \Delta f < 1.0 \text{ MHz}$ | $0.815 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $P - 54 \text{ dB}$ | 30 kHz | +| $1.0 \text{ MHz} \leq \Delta f < 1.8 \text{ MHz}$ | $1.015 \text{ MHz} \leq f\_offset < 1.815 \text{ MHz}$ | $P - 54 \text{ dB} - 10 \cdot \left( \frac{f\_offset}{\text{MHz}} - 1,015 \right) \text{ dB}$ | 30 kHz | +| See note | $1.815 \text{ MHz} \leq f\_offset < 2.3 \text{ MHz}$ | $P - 62 \text{ dB}$ | 30 kHz | +| $1.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $2.3 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $P - 47 \text{ dB}$ | 1 MHz | + +**Table 9.3: Spectrum emission mask values, BS maximum output power P < 26 dBm** + +| Frequency offset of measurement filter - 3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------------------------------------------------------------------|-----------------------| +| $0.8 \text{ MHz} \leq \Delta f < 1.0 \text{ MHz}$ | $0.815 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | -28 dBm | 30 kHz | +| $1.0 \text{ MHz} \leq \Delta f < 1.8 \text{ MHz}$ | $1.015 \text{ MHz} \leq f\_offset < 1.815 \text{ MHz}$ | $-28 \text{ dBm} - 10 \cdot \left( \frac{f\_offset}{\text{MHz}} - 1,015 \right) \text{ dB}$ | 30 kHz | +| See note | $1.815 \text{ MHz} \leq f\_offset < 2.3 \text{ MHz}$ | -36 dBm | 30 kHz | +| $1.8 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $2.3 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -21 dBm | 1 MHz | + +NOTE: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +## 9.2 Spurious emissions + +Spurious emissions are emissions which are caused by unwanted transmitter effects such as harmonics emission, parasitic emission, intermodulation products and frequency conversion products, but exclude out of band emissions. This is measured at the base station RF output port. + +The requirements shall apply whatever the type of transmitter considered (single carrier or multi carrier). It applies for all transmission modes foreseen by the manufacturer's. + +For 1.28 Mcps TDD option, either requirement applies at frequencies within the specified frequency ranges which are more than 4 MHz under the first carrier frequency used or more than 4 MHz above the last carrier frequency used. + +Unless otherwise stated, all requirements are measured as mean power. + +### 9.2.1 Mandatory Requirements + +The requirements of either subclause 9.2.1.1 or subclause 9.2.1.2 shall apply. + +#### 9.2.1.1 Spurious emissions (Category A) + +The following requirements shall be met in cases where Category A limits for spurious emissions, as defined in ITU-R Recommendation SM.329-9 [1], are applied. + +##### 9.2.1.1.1 Minimum Requirement + +The power of any spurious emission shall not exceed: + +**Table 9.4: LCR TDD repeater Mandatory spurious emissions limits, Category A** + +| Band | Minimum requirement | Measurement Bandwidth | Notes | +|------------------------------------------------------------|---------------------|-----------------------|--------| +| 9kHz - 150kHz | | 1 kHz | Note 1 | +| 150kHz - 30MHz | | 10 kHz | Note 1 | +| 30MHz - 1GHz | -13 dBm | 100 kHz | Note 1 | +| 1GHz - 12.75 GHz | | 1 MHz | Note 2 | +| NOTE 1: Bandwidth as in ITU SM.329 [1], s4.1 | | | | +| NOTE 2: Upper frequency as in ITU SM.329 [1], s2.5 table 1 | | | | + +NOTE: only the measurement bands are different according to the occupied bandwidth. + +#### 9.2.1.2 Spurious emissions (Category B) + +The following requirements shall be met in cases where Category B limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [1], are applied. + +##### 9.2.1.2.1 Minimum Requirement + +The power of any spurious emission shall not exceed: + +**Table 9.5: LCR TDD repeater Mandatory spurious emissions limits, Category B** + +| Band | Maximum Level | Measurement Bandwidth | Notes | +|------------------------------|---------------|-----------------------|--------| +| 9kHz - 150kHz | -36 dBm | 1 kHz | Note 1 | +| 150kHz - 30MHz | - 36 dBm | 10 kHz | Note 1 | +| 30MHz - 1GHz | -36 dBm | 100 kHz | Note 1 | +| 1GHz
↔
Fl -10 MHz | -30 dBm | 1 MHz | Note 1 | +| Fl -10MHz
↔
Fu +10 MHz | -15 dBm | 1 MHz | Note 2 | +| Fu +10 MHz
↔
12,5 GHz | -30 dBm | 1 MHz | Note 3 | + +NOTE 1: Bandwidth as in ITU SM.329 [1], s4.1 +NOTE 2: Limit based on ITU-R SM.329 [1], s4.3 and Annex 7 +NOTE 3: Bandwidth as in ITU-R SM.329 [1], s4.3 and Annex 7. Upper frequency as in ITU-R SM.329 [1], s2.5 table 1 + +Fl: Lower frequency of the band in which TDD operates +Fu: Upper frequency of the band in which TDD operates + +### 9.2.2 Co-existence with GSM 900 + +#### 9.2.2.1 Operation in the same geographic area + +This requirement may be applied for the protection of GSM 900 MS and GSM 900 BTS receivers in geographic areas in which both GSM 900 and UTRA are deployed. + +##### 9.2.2.1.1 Minimum Requirement + +The power of any spurious emission shall not exceed: + +**Table 9.6: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in geographic coverage area of GSM 900 MS and GSM 900 BTS receiver** + +| Band | Maximum Level | Measurement Bandwidth | Note | +|---------------|---------------|-----------------------|------| +| 876 - 915 MHz | -61 dBm | 100 kHz | | +| 921 - 960MHz | -57 dBm | 100 kHz | | + +#### 9.2.2.2 Co-located base stations + +This requirement may be applied for the protection of GSM 900 BTS receivers when GSM 900 BTS and UTRA BS are co-located. + +##### 9.2.2.2.1 Minimum Requirement + +The power of any spurious emission shall not exceed: + +**Table 9.7: LCR TDD repeater Spurious emissions limits for protection of the GSM 900 BTS receiver** + +| Band | Maximum Level | Measurement Bandwidth | Note | +|---------------|---------------|-----------------------|------| +| 876 - 915 MHz | -98 dBm | 100 kHz | | + +### 9.2.3 Co-existence with DCS 1800 + +#### 9.2.3.1 Operation in the same geographic area + +This requirement may be applied for the protection of DCS 1800 MS and DCS 1800 BTS receivers in geographic areas in which both DCS 1800 and UTRA are deployed. + +##### 9.2.3.1.1 Minimum Requirement + +The power of any spurious emission shall not exceed: + +**Table 9.8: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in the band a), d) and e) when operating in geographic coverage area of DCS 1800 MS and DCS 1800 BTS receiver** + +| Band | Maximum Level | Measurement Bandwidth | Note | +|-----------------|---------------|-----------------------|------| +| 1710 - 1785 MHz | -61 dBm | 100 kHz | | +| 1805 - 1880MHz | -47 dBm | 100 kHz | | + +**Table 9.8a: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in the band f) when operating in geographic coverage area of DCS 1800 MS and DCS 1800 BTS receiver operating in 1710-1755 MHz/1805-1850 MHz** + +| Band | Maximum Level | Measurement Bandwidth | Note | +|-----------------|---------------|-----------------------|------| +| 1710 - 1755 MHz | -61 dBm | 100 kHz | | +| 1805 - 1850MHz | -47 dBm | 100 kHz | | + +#### 9.2.3.2 Co-located base stations + +This requirement may be applied for the protection of DCS 1800 BTS receivers when DCS 1800 BTS and UTRA BS are co-located. + +##### 9.2.3.2.1 Minimum Requirement + +The power of any spurious emission shall not exceed: + +**Table 9.9: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in the band a), d) and e) when co-located with DCS 1800 BTS** + +| Band | Maximum Level | Measurement Bandwidth | Note | +|-----------------|---------------|-----------------------|------| +| 1710 - 1785 MHz | -98 dBm | 100 kHz | | + +**Table 9.10: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in the band f) when co-located with DCS1800 BTS** + +| Band | Maximum Level | Measurement Bandwidth | Note | +|-----------------|---------------|-----------------------|------| +| 1710 - 1755 MHz | -98 dBm | 100 kHz | | + +### 9.2.4 Co-existence with UTRA-FDD + +#### 9.2.4.1 Operation in the same geographic area + +This requirement may be applied to geographic areas in which both UTRA-TDD and UTRA-FDD operating in bands specified in Table 9.11 are deployed. + +##### 9.2.4.1.1 Minimum Requirement + +For LCR TDD repeater which use carrier frequencies within the band 2010 - 2025 MHz the requirements applies at all frequencies within the specified frequency bands in table 9.11. For LCR TDD repeater which use carrier frequencies within the band 1900-1920 MHz, the requirement applies at frequencies within the specified frequency range which are more than 4 MHz above the last carrier used in the frequency band 1900-1920 MHz. + +The power of any spurious emission shall not exceed: + +**Table 9.11: LCR TDD repeater Spurious emissions limits for LCR TDD repeater in geographic coverage area of UTRA-FDD** + +| Band | Maximum Level | Measurement Bandwidth | Note | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------|------| +| 1920 - 1980 MHz | -43 dBm (*) | 3,84 MHz | | +| 2110 - 2170 MHz | -52 dBm | 1 MHz | | +| 2500 - 2570 MHz | -43 dBm(**) | 3.84 MHz | | +| 2620 - 2690 MHz | -52 dBm | 1 MHz | | +| NOTE* For LCR TDD repeater which use carrier frequencies within the band 1900 - 1920 MHz or 1880-1920MHz, the requirement shall be measured RRC filtered mean power with the lowest centre frequency of measurement at 1922.6 MHz or 6.6 MHz above the highest TDD carrier used, whichever is higher. | | | | +| NOTE ** For LCR TDD repeater which use carrier frequencies within the band 2570 - 2620 MHz, the requirement shall be measured RRC filtered mean power with the highest centre frequency of measurement at 2567.5 MHz or 6.6 MHz below the lowest TDD carrier used, whichever is lower. | | | | + +NOTE: The requirements in Table 9.11 are based on a coupling loss of 70 dB between LCR TDD repeater and FDD Wide Area base stations. + +#### 9.2.4.2 Co-located base stations + +This requirement may be applied for the protection of UTRA-FDD BS receivers when UTRA-TDD BS and UTRA FDD BS are co-located. + +##### 9.2.4.2.1 Minimum Requirement + +For LCR TDD repeater which use carrier frequencies within the band 2010 - 2025 MHz the requirements applies at all frequencies within the specified frequency bands in table 9.12. For LCR TDD repeater which use carrier frequencies within the band 1900-1920 MHz, the requirement applies at frequencies within the specified frequency range which are more than 4 MHz above the last carrier used in the frequency band 1900-1920 MHz. + +The power of any spurious emission shall not exceed: + +**Table 9.12: LCR TDD repeater Spurious emissions limits for BS co-located with UTRA-FDD** + +| Band | Maximum Level | Measurement Bandwidth | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------| +| 1920 - 1980 MHz | -80 dBm (*) | 3,84 MHz | +| 2110 - 2170 MHz | -52 dBm | 1 MHz | +| 2500 - 2570 MHz | - 80 dBm(**) | 3.84 MHz | +| 2620 - 2690 MHz | -52 dBm | 1 MHz | +| NOTE * For LCR TDD repeater which use carrier frequencies within the band 1900 - 1920 MHz or 1880-1920MHz, the requirement shall be measured RRC filtered mean power with the lowest centre frequency of measurement at 1922.6 MHz or 6.6 MHz above the highest TDD carrier used, whichever is higher. | | | +| NOTE ** For LCR TDD repeater which use carrier frequencies within the band 2570 - 2620 MHz, the requirement shall be measured RRC filtered mean power with the highest centre frequency of measurement at 2567.5 MHz or 6.6MHz below the lowest TDD carrier used, whichever is lower. | | | + +NOTE: The requirements in Table 9.12 are based on a minimum coupling loss of 30 dB between LCR TDD repeater and UTRA-FDD base stations. + +### 9.2.5 Co-existence with unsynchronised TDD + +#### 9.2.5.1 Operation in the same geographic area + +This requirement shall apply in case the equipment is operated in the same geographic area with unsynchronised TDD BS. + +##### 9.2.5.1.1 Minimum Requirement + +In geographic areas where only 1,28 Mcps TDD is deployed, the RRC filtered mean power of any spurious emission shall not exceed the limits specified in table 9.13, otherwise the limits in table 9.14 shall apply. + +**Table 9.13: LCR TDD repeater Spurious emissions limits for operation in same geographic area with unsynchronised 1,28 Mcps TDD** + +| Band | Maximum Level | Measurement Bandwidth | +|-----------------|---------------|-----------------------| +| 1900 - 1920 MHz | -39 dBm | 1,28 MHz | +| 2010 - 2025 MHz | -39 dBm | 1,28 MHz | +| 2300 - 2400 MHz | -39 dBm | 1,28 MHz | +| 2570 - 2620 MHz | -39 dBm | 1,28 MHz | +| 1880 - 1920 MHz | -39 dBm | 1,28 MHz | + +**Table 9.14: LCR TDD repeater Spurious emissions limits for operation in same geographic area with unsynchronised TDD** + +| Band | Maximum Level | Measurement Bandwidth | +|-----------------|---------------|-----------------------| +| 1900 - 1920 MHz | -39 dBm | 3,84 MHz | +| 2010 - 2025 MHz | -39 dBm | 3,84 MHz | +| 2570 - 2620 MHz | -39 dBm | 3,84 MHz | + +NOTE: The requirements in Table 9.13 and 9.14 for the LCR TDD repeater are based on a minimum coupling loss of 67 dB between LCR TDD repeater and unsynchronised TDD base stations. + +#### 9.2.5.2 Co-located base stations + +This requirement shall apply in case of co-location with unsynchronised TDD BS. + +##### 9.2.5.2.1 Minimum Requirement + +In geographic areas where only 1,28 Mcps TDD is deployed, the RRC filtered mean power of any spurious emission in case of co-location shall not exceed the limits specified in table 9.15, otherwise the limits in table 9.16 shall apply. + +**Table 9.15: LCR TDD repeater Spurious emissions limits for co-location with unsynchronised 1,28 Mcps TDD** + +| Band | Maximum Level | Measurement Bandwidth | +|-------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------| +| 1900 - 1920 MHz | -76 dBm | 1,28 MHz | +| 2010 - 2025 MHz | -76 dBm | 1,28 MHz | +| 2300 - 2400 MHz | -76 dBm | 1,28 MHz | +| 2570 - 2620 MHz | -76 dBm | 1,28 MHz | +| 1880 - 1920 MHz | -76 dBm | 1,28 MHz | +| NOTE: The requirement applies for frequencies more than 10 MHz below or above the supported frequency range declared by the vendor. | | | + +**Table 9.16: LCR TDD repeater Spurious emissions limits for co-location with unsynchronised TDD** + +| Band | Maximum Level | Measurement Bandwidth | +|-----------------|---------------|-----------------------| +| 1900 - 1920 MHz | -76 dBm | 3,84 MHz | +| 2010 - 2025 MHz | -76 dBm | 3,84 MHz | +| 2570 - 2620 MHz | -76 dBm | 3,84 MHz | + +NOTE: The requirements in Table 9.15 and 9.16 for the LCR TDD repeater are based on a minimum coupling loss of 30 dB between unsynchronised TDD base stations. + +# --- 10 Modulation accuracy + +## 10.1 Error Vector Magnitude + +The modulation accuracy is defined by the Error Vector Magnitude (EVM), which is a measure of the difference between the theoretical waveform and a modified version of the measured waveform. This difference is called the error vector. The measured waveform is modified by first passing it through a matched root raised cosine filter with bandwidth 1.28MHz and roll-off $\alpha=0.22$ . The waveform is then further modified by selecting the frequency, absolute phase, absolute amplitude and chip clock timing so as to minimise the error vector. The EVM result is defined as root of the ratio of the mean error vector power to the mean reference signal power expressed as a %. + +The measurement interval is one power control group (timeslot). The repeater shall operate with an ideal LCR TDD signal in the pass band of the repeater at a level, which produce the maximum rated output power per channel, as specified by the manufacturer. + +### 10.1.1 Minimum requirement + +The Error Vector Magnitude shall not be worse than 8 %. + +## 10.2 Peak code domain error + +The code domain error is computed by projecting the error vector power onto the code domain at a specific spreading factor. The error power for each code is defined as the ratio to the mean power of the reference waveform expressed in dB. And the Peak Code Domain Error is defined as the maximum value for Code Domain Error. The measurement interval is one timeslot. + +### 10.2.1 Minimum requirement + +The peak code domain error shall not exceed -30 dB at spreading factor 16. + +# --- 11 Input intermodulation + +The input intermodulation is a measure of the capability of the repeater to inhibit the generation of interference in the pass band, in the presence of interfering signals on frequencies other than the pass band. + +## 11.1 General requirement + +The following requirement applies for interfering signals in the frequency bands defined in sub-clause 5.2, depending on the repeaters pass band. + +This requirement applies to the uplink and downlink of the repeater, at maximum gain. + +### 11.1.1 Minimum requirement + +For the parameters specified in table 11.1.1-1, the power in the pass band shall not increase with more than 10 dB at the output of the repeater as measured in the centre of the pass band, compared to the level obtained without interfering signals applied. + +The frequency separation between the two interfering signals shall be adjusted so that the 3rd order intermodulation product is positioned in the centre of the pass band. + +Table 11.1.1-1 specifies the parameters for two interfering signals, where: + +- $f_1$ offset is the offset from the channel edge frequency of the first or last channel in the pass band of the closer carrier. + +**Table 11.1.1-1: Input intermodulation requirement** + +| $f_1$ offset | Interfering Signal Levels | Type of signals | Measurement bandwidth | +|--------------|---------------------------|-----------------|-----------------------| +| 1,0 MHz | -40 dBm | 2 CW carriers | 1 MHz | + +# 12 Output intermodulation + +## 12.0 General + +The transmit intermodulation performance is a measure of the capability of the transmitter to inhibit the generation of signals in its non linear elements caused by presence of the wanted signal and an interfering signal reaching the transmitter via the antenna. + +The transmit intermodulation level is the power of the intermodulation products when a LCR TDD modulated interference signal is injected into the antenna connector at a mean power level of 30 dB lower than that of the mean power of the subject signal. + +## 12.1 Minimum requirement + +The frequency of the interference signal shall be $\pm 1.6$ MHz, $\pm 3.2$ MHz and $\pm 4.8$ MHz offset from the subject signal. The Transmit intermodulation level shall not exceed the out of band or the spurious emission requirements of section 9.1 and 9.2. + +# 13 Adjacent Channel Rejection Ratio (ACRR) + +## 13.1 Definitions and applicability + +Adjacent Channel Rejection Ratio (ACRR) is the ratio of the RRC weighted gain per carrier of the repeater in the pass band to the RRC weighted gain of the repeater on an adjacent channel. The carrier in the pass band and in the adjacent channel shall be of the same type (reference carrier). + +The requirement shall apply to the uplink and downlink of Repeater, at maximum gain, where the donor link is maintained via antennas (over the air Repeater). + +## 13.2 Co-existence with UTRA + +This requirement shall be applied for the protection of UTRA signals in geographic areas in which LCR TDD Repeater and UTRA BS are deployed so that they serve adjacent channels. The reference carrier is a UTRA-FDD carrier. + +### 13.2.1. Minimum Requirements + +In normal conditions the ACRR shall be higher than the value specified in the Table 13.2.1-1. + +**Table 13.2.1-1: Repeater ACRR** + +| Co-existence with other systems | Repeater maximum output Pmax | Channel offset from the channel edge from the first or last 5MHz channel within the pass band. | ACRR limit | +|---------------------------------|------------------------------|------------------------------------------------------------------------------------------------|------------| +| UTRA | $P \geq 31$ dBm | 2,5 MHz | 33dB | +| | $P \geq 31$ dBm | 5,0 MHz | 33dB | +| | $P < 31$ dBm | 2,5 MHz | 20dB | +| | $P < 31$ dBm | 5,0 MHz | 20dB | + +Note: For co-existence with TDD, a narrow band requirement is for further study. + +# 14 Timing Accuracy + +Timing Accuracy is the repeater synchronization accuracy with NodeB, it includes the downlink ramp on/off time and uplink ramp on/off time. + +## 14.1 Minimum requirement + +The downlink gain versus time should meet the mask specified in figure 14.1. The beginning and end point of downlink burst is calculated according to the trigger given by NodeB or LCR TDD signal generator. + +![Figure 14.1: Downlink gain ON/OFF template. A graph showing gain levels over time. The vertical axis has 'Zero Gain' and 'Rated Gain' labels. The horizontal axis shows a 'Downlink burst without GP' (Gain Profile) that rises from Zero Gain to Rated Gain and then falls back to Zero Gain. The rise and fall times are each marked as '8 chips' with double-headed arrows.](5adf12d50dfea82178ca002a2c48641b_img.jpg) + +Figure 14.1: Downlink gain ON/OFF template. A graph showing gain levels over time. The vertical axis has 'Zero Gain' and 'Rated Gain' labels. The horizontal axis shows a 'Downlink burst without GP' (Gain Profile) that rises from Zero Gain to Rated Gain and then falls back to Zero Gain. The rise and fall times are each marked as '8 chips' with double-headed arrows. + +**Figure 14.1: Downlink gain ON/OFF template** + +The uplink gain versus time should meet the mask specified in figure 14.2. The beginning and end point of uplink burst is calculated according to the trigger given by NodeB or LCR TDD signal generator. + +![Figure 14.2: Uplink gain ON/OFF template. A graph showing gain levels over time. The vertical axis has 'Zero Gain' and 'Rated Gain' labels. The horizontal axis shows an 'Uplink burst without GP' that rises from Zero Gain to Rated Gain and then falls back to Zero Gain. The rise and fall times are each marked as '8 chips' with double-headed arrows.](85ad73d1c8ff59cd647b95f084937bc0_img.jpg) + +Figure 14.2: Uplink gain ON/OFF template. A graph showing gain levels over time. The vertical axis has 'Zero Gain' and 'Rated Gain' labels. The horizontal axis shows an 'Uplink burst without GP' that rises from Zero Gain to Rated Gain and then falls back to Zero Gain. The rise and fall times are each marked as '8 chips' with double-headed arrows. + +**Figure 14.2: Uplink gain ON/OFF template** + +# --- Annex A (normative): Environmental requirements for the Repeater equipment + +The Repeater equipment shall fulfil all the requirements in the full range of environmental conditions for the relevant environmental class from the relevant IEC specifications listed below + +- 60 721-3-3 "Stationary use at weather protected locations" [6]; +- 60 721-3-4 "Stationary use at non weather protected locations" [7] + +Normally it should be sufficient for all tests to be conducted using normal test conditions except where otherwise stated. For guidance on the use of test conditions to be used in order to show compliance refer to TS 25.153. + +# Annex B (informative): Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|----|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2009-08 | RAN4#52 | R4-093324 | | | TS skeleton created from 3GPP TS template. | | 0.0.1 | +| 2009-11 | RAN4#53 | R4-094876 | | | TS with the TP approved at RAN4#52 and RAN4#52bis
R4-092917 Text proposal for LCR TDD Repeater Specification:
Output Power
R4-092918 Text proposal for LCR TDD Repeater Specification:
Frequency Error
R4-092919 Text proposal for LCR TDD Repeater Specification:
EVM
R4-092920 Text proposal for LCR TDD Repeater Specification:
PCDE
R4-092922 Text proposal for LCR TDD Repeater Specification:
Output Intermodulation
R4-093323 Text Proposal for LCR TDD Repeater Specification:
Frequency bands and channel arrangements
R4-093350 Text proposal for LCR TDD Repeater Specification:
Input Intermodulation
R4-093351 Text proposal for LCR TDD Repeater Specification:
Out of Band Gain
R4-093353 Text proposal for LCR TDD Repeater Specification:
ACRR
R4-093363 Text proposal for LCR TDD Repeater Specification:
Timing Accuracy
R4-093372 Text proposal for LCR TDD Repeater Specification:
Unwanted Emissions
R4-093746 Text proposal for 25.116: Clause 1 to Clause 3
R4-094015 Text proposal for 25.116: Clause 4 General | 0.0.1 | 1.0.0 | +| 2009-11 | RAN#46 | RP-091136 | | | Presentation to TSG for information | | | +| 2010-03 | RAN#47 | RP-100112 | | | Version update, presentation to TSG for approval, | 1.0.0 | 2.0.0 | +| 2010-03 | RAN#47 | RP-100112 | | | Approved by TSG RAN | 2.0.0 | 10.0.0 | +| 2012-09 | SP-57 | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | 11.0.0 | +| 2014-09 | SP-65 | - | - | - | Update to Rel-12 version (MCC) | 11.0.0 | 12.0.0 | +| 2016-01 | SP-70 | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | +| 2017-03 | - | - | - | - | Update to Rel-14 version (MCC) | 13.0.0 | 14.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2018-06 | SA#80 | - | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-06 | SA#88 | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25142/1c1fa3b79033665761d99885900218bf_img.jpg b/marked/Rel-16/25_series/25142/1c1fa3b79033665761d99885900218bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..995aaba443f0b0417fb555983b0c86f12ed1f5d7 --- /dev/null +++ b/marked/Rel-16/25_series/25142/1c1fa3b79033665761d99885900218bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34defec0918adc54728ef230916daecd8248cd7ed6e117c7f54d424aa965bd1f +size 58646 diff --git a/marked/Rel-16/25_series/25142/23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg b/marked/Rel-16/25_series/25142/23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d2cfd1896a757ad874bf5f306d6ca7440b75b62 --- /dev/null +++ b/marked/Rel-16/25_series/25142/23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9049edf783ea058156081427da79216d48a979719cf26c98f732b8542ef6314a +size 16980 diff --git a/marked/Rel-16/25_series/25142/265c8762616c43e9c49083d5546b9738_img.jpg b/marked/Rel-16/25_series/25142/265c8762616c43e9c49083d5546b9738_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf77a00c95c93b02e6fdd21c6b2771a4cb81291d --- /dev/null +++ b/marked/Rel-16/25_series/25142/265c8762616c43e9c49083d5546b9738_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d68f5d63a52f50469c854a2c5be77200f063802a1375edc8d52ece3eba3e0311 +size 162854 diff --git a/marked/Rel-16/25_series/25142/38c0f202ad5767f3df428353919fa90a_img.jpg b/marked/Rel-16/25_series/25142/38c0f202ad5767f3df428353919fa90a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5681640d4e1eefde7f31a266f043e4dda8113d27 --- /dev/null +++ b/marked/Rel-16/25_series/25142/38c0f202ad5767f3df428353919fa90a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb2e8a480b74a3f114f426ddda5607c75e74312e0cfe7b882df3aa42716c8b39 +size 54538 diff --git a/marked/Rel-16/25_series/25142/3d6d0738981fdd03d003cc653bdfdaae_img.jpg b/marked/Rel-16/25_series/25142/3d6d0738981fdd03d003cc653bdfdaae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85bd3c1ba4d73a2db90b07ca65d9cb61ea4c5ccf --- /dev/null +++ b/marked/Rel-16/25_series/25142/3d6d0738981fdd03d003cc653bdfdaae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cca29bbdba5da3bed534df4781807d1c66adc5e5106a265cd802a63500675689 +size 170177 diff --git a/marked/Rel-16/25_series/25142/409e3ccf9694772191dc84c49f3f7afb_img.jpg b/marked/Rel-16/25_series/25142/409e3ccf9694772191dc84c49f3f7afb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2fba7d6e83b0e2ac6ccfdb7abe3832c5855f6d1 --- /dev/null +++ b/marked/Rel-16/25_series/25142/409e3ccf9694772191dc84c49f3f7afb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37540ada50a1384d31c2cd054119553dfd3e811ab2a4c495c8120ecabf937cfe +size 61512 diff --git a/marked/Rel-16/25_series/25142/43b05bd1b6ee31fba18d3eb683903504_img.jpg b/marked/Rel-16/25_series/25142/43b05bd1b6ee31fba18d3eb683903504_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f49fa965c69fbb2d91112426b04e2f61e82b339 --- /dev/null +++ b/marked/Rel-16/25_series/25142/43b05bd1b6ee31fba18d3eb683903504_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba394207fc5a9f1efe55a0ef7dd0c31695b67ac0fdf6ebd2f0f81c22f99ee066 +size 59892 diff --git a/marked/Rel-16/25_series/25142/449dd9d482c5b47f1c013ce3e18b09e6_img.jpg b/marked/Rel-16/25_series/25142/449dd9d482c5b47f1c013ce3e18b09e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d072583acd778147b0d9c86d77d161e3fa1bbac3 --- /dev/null +++ b/marked/Rel-16/25_series/25142/449dd9d482c5b47f1c013ce3e18b09e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab99ad868ca953276307f50e67f9e4a5a933abaff596dbecc8822721c003805c +size 27170 diff --git a/marked/Rel-16/25_series/25142/4930881b4cec8929388e16e4f7be512d_img.jpg b/marked/Rel-16/25_series/25142/4930881b4cec8929388e16e4f7be512d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4c68ca5ef2f398d5c32806b714800ca8d831e90 --- /dev/null +++ b/marked/Rel-16/25_series/25142/4930881b4cec8929388e16e4f7be512d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e1d1c10810b662bf3dcdd27a6b148fa97e1f0fb99694366dfff581a5c18bc7a +size 28861 diff --git a/marked/Rel-16/25_series/25142/4f407c97df6e5ee98fdb248ada82de59_img.jpg b/marked/Rel-16/25_series/25142/4f407c97df6e5ee98fdb248ada82de59_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0135f2d9f3e0e1e0a944ffaf166752f967766ec --- /dev/null +++ b/marked/Rel-16/25_series/25142/4f407c97df6e5ee98fdb248ada82de59_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4db6edd98a16f4473f34a570a9448d02fb4f7a7d0495dc93627c0f94481d423 +size 212913 diff --git a/marked/Rel-16/25_series/25142/5635bd67a8ba929382fd61dede8952c7_img.jpg b/marked/Rel-16/25_series/25142/5635bd67a8ba929382fd61dede8952c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4adc225e40edab66f9d75577c623234bc5eb157f --- /dev/null +++ b/marked/Rel-16/25_series/25142/5635bd67a8ba929382fd61dede8952c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:151054660b65a6b0040c3af6ee3a515980186204876d21d83540b57a47b2ec54 +size 27339 diff --git a/marked/Rel-16/25_series/25142/56468323fb2f5ff6f0a8bf9bf1f691e8_img.jpg b/marked/Rel-16/25_series/25142/56468323fb2f5ff6f0a8bf9bf1f691e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59bf22f031a620e8e0ad7953b857fb28c5b38296 --- /dev/null +++ b/marked/Rel-16/25_series/25142/56468323fb2f5ff6f0a8bf9bf1f691e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e3885c92e59e78cd24d4cac05db3e8bef018e5cb1283c43972c9302b0391982 +size 30675 diff --git a/marked/Rel-16/25_series/25142/58f883d880e744531c77ddfd50af87bf_img.jpg b/marked/Rel-16/25_series/25142/58f883d880e744531c77ddfd50af87bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72bd779f6cd6c243a89dea1e4a5f616b7c0c774d --- /dev/null +++ b/marked/Rel-16/25_series/25142/58f883d880e744531c77ddfd50af87bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03b57006086686690960e8b14deb3c49f5aa6f52db173489a3221c186db53187 +size 42548 diff --git a/marked/Rel-16/25_series/25142/59b0fc7f07c6794ca85c36c2d06a5fd9_img.jpg b/marked/Rel-16/25_series/25142/59b0fc7f07c6794ca85c36c2d06a5fd9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58be22ab387fa21ddaa8e2d18e953e0517cc2855 --- /dev/null +++ b/marked/Rel-16/25_series/25142/59b0fc7f07c6794ca85c36c2d06a5fd9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69b659b3c56f5b0b8977bffe7be007b166175cd819ab901c53c5651069ffd923 +size 51444 diff --git a/marked/Rel-16/25_series/25142/5d819f259411162c4e3371915818ae22_img.jpg b/marked/Rel-16/25_series/25142/5d819f259411162c4e3371915818ae22_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74efae488265171a214c500232a537e5c5f710c2 --- /dev/null +++ b/marked/Rel-16/25_series/25142/5d819f259411162c4e3371915818ae22_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ab9761d3deb67ce060cb3570805edbb919c96558d76b3a9d173c6fc5431f6a6 +size 52844 diff --git a/marked/Rel-16/25_series/25142/5f6ee513bafbf5140814bda2337e145f_img.jpg b/marked/Rel-16/25_series/25142/5f6ee513bafbf5140814bda2337e145f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b693e0ec4f976360feb931f1bfeffdeaf46b458 --- /dev/null +++ b/marked/Rel-16/25_series/25142/5f6ee513bafbf5140814bda2337e145f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7adb7cfea47520d7d5ccf10827a86e67552c5887ce78fcc5db70260b8b7adf7d +size 30668 diff --git a/marked/Rel-16/25_series/25142/64c76a4fd6b7918cd8a2704de0265e8d_img.jpg b/marked/Rel-16/25_series/25142/64c76a4fd6b7918cd8a2704de0265e8d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b102ca4177c967ba5e6f155633af91303e7cbca --- /dev/null +++ b/marked/Rel-16/25_series/25142/64c76a4fd6b7918cd8a2704de0265e8d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3cd48033d1b8f3911c03e8b52ed611999ccfef1c6f91cb5de3b8f8504a4c344d +size 231424 diff --git a/marked/Rel-16/25_series/25142/7109096552c3464c931b0b39109b9b41_img.jpg b/marked/Rel-16/25_series/25142/7109096552c3464c931b0b39109b9b41_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53fbd4e46d2f19a3f046f26f7b9dfcc7dace2a08 --- /dev/null +++ b/marked/Rel-16/25_series/25142/7109096552c3464c931b0b39109b9b41_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b454580ae7b1230c29f00550ad2abd4e91084aac4974b6969bd0fa45259d910a +size 54597 diff --git a/marked/Rel-16/25_series/25142/728a02fe4a04e7f91835147194997cd4_img.jpg b/marked/Rel-16/25_series/25142/728a02fe4a04e7f91835147194997cd4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d203c8cd9a4d37e5038ddbeee484a85dd92d26c7 --- /dev/null +++ b/marked/Rel-16/25_series/25142/728a02fe4a04e7f91835147194997cd4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a903f075586cc943d65b16f0ad378d909166678619affa23312681b51d0b8c5b +size 51945 diff --git a/marked/Rel-16/25_series/25142/7be79849b00ccd5e7220d808251b1258_img.jpg b/marked/Rel-16/25_series/25142/7be79849b00ccd5e7220d808251b1258_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57791ce4cb436fede0cd224711748eb2be4b5db2 --- /dev/null +++ b/marked/Rel-16/25_series/25142/7be79849b00ccd5e7220d808251b1258_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d9eb0e92fa8b4bf7236e029e59a8eedb6877f52441aa68174bac235bc0a2f8c +size 30835 diff --git a/marked/Rel-16/25_series/25142/87f625baee73880fd5464a9f60b1b3b8_img.jpg b/marked/Rel-16/25_series/25142/87f625baee73880fd5464a9f60b1b3b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..208709df216c4f50026a02248135097c32f319a3 --- /dev/null +++ b/marked/Rel-16/25_series/25142/87f625baee73880fd5464a9f60b1b3b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64695091867e1b92caa6efa1e962e93dfde7e4897c3c0e5913b8c695877e722c +size 53747 diff --git a/marked/Rel-16/25_series/25142/89b3389b2c4fa1b452cf2b5daa5f82ad_img.jpg b/marked/Rel-16/25_series/25142/89b3389b2c4fa1b452cf2b5daa5f82ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e509f37fb6b0ff854045ab91538aa40767236224 --- /dev/null +++ b/marked/Rel-16/25_series/25142/89b3389b2c4fa1b452cf2b5daa5f82ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:507aaf9d78e9244e9b751c5cae54b1a3eed3760e0c91fcddc42075a009fe5488 +size 26325 diff --git a/marked/Rel-16/25_series/25142/8c05782074bb11421b43f2d5d6799b62_img.jpg b/marked/Rel-16/25_series/25142/8c05782074bb11421b43f2d5d6799b62_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1444f5e304181345065011e70c2a651bb408933 --- /dev/null +++ b/marked/Rel-16/25_series/25142/8c05782074bb11421b43f2d5d6799b62_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb11bbf0ad34b6207a03eb4a39ffbe4cc94558f43aa5e349b8edfe243427361a +size 24172 diff --git a/marked/Rel-16/25_series/25142/8e097ecef190600bbde2721e0f979b79_img.jpg b/marked/Rel-16/25_series/25142/8e097ecef190600bbde2721e0f979b79_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cfe52ab5e0d2fd2a5bcf50eb0621e7a6d731a04d --- /dev/null +++ b/marked/Rel-16/25_series/25142/8e097ecef190600bbde2721e0f979b79_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e2752263573b1bf807fe984eb8b4e8831a7ec60ac6ff2427a740d638a83b030 +size 56808 diff --git a/marked/Rel-16/25_series/25142/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-16/25_series/25142/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2916acc9d47929b4a1739ab14edc63043ebf355 --- /dev/null +++ b/marked/Rel-16/25_series/25142/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ebcc0a7f6454413b055a495e601bed3e360b1f9d89e4b465e8c5d3faad09d5c4 +size 25982 diff --git a/marked/Rel-16/25_series/25142/931bd52904f67b17796a38b47af51e30_img.jpg b/marked/Rel-16/25_series/25142/931bd52904f67b17796a38b47af51e30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c057f30326a5cb160cc6531b0125a4c74ca2857 --- /dev/null +++ b/marked/Rel-16/25_series/25142/931bd52904f67b17796a38b47af51e30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc6b8a04f6493ddefde7ebc71f4b6e4683ee968a8e9ac80c1e493fb569be0133 +size 53901 diff --git a/marked/Rel-16/25_series/25142/993921f0d5f99fb48933465306644535_img.jpg b/marked/Rel-16/25_series/25142/993921f0d5f99fb48933465306644535_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed97cdfb8f9824d71bbfdeefd6016cf626804759 --- /dev/null +++ b/marked/Rel-16/25_series/25142/993921f0d5f99fb48933465306644535_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5732cc3072f564236b9605fb8582254aad8808b6504102b18d90577a5d53c83 +size 137010 diff --git a/marked/Rel-16/25_series/25142/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg b/marked/Rel-16/25_series/25142/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d60d86174cb16f4c6a72386554b4b064def0bf0d --- /dev/null +++ b/marked/Rel-16/25_series/25142/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f27cbd04e5e79f99b5f20712afc5874f7509a860d7f0fd4ee9a540def1c69b5 +size 30645 diff --git a/marked/Rel-16/25_series/25142/9ba478ec5af01fd2fb458d145565198e_img.jpg b/marked/Rel-16/25_series/25142/9ba478ec5af01fd2fb458d145565198e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ebb3ef401ee2a5746547460c5aacfd3f55d549b --- /dev/null +++ b/marked/Rel-16/25_series/25142/9ba478ec5af01fd2fb458d145565198e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e6da7a1c28aa6f6dbff3f886535de5785e2c61508fc3731dd7d1a74046fd1bb +size 140427 diff --git a/marked/Rel-16/25_series/25142/9dee6d7157e1d03eb09a30a9aa81cc11_img.jpg b/marked/Rel-16/25_series/25142/9dee6d7157e1d03eb09a30a9aa81cc11_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9039d4dd75f60c3ac36d9c982d1e7df0560de195 --- /dev/null +++ b/marked/Rel-16/25_series/25142/9dee6d7157e1d03eb09a30a9aa81cc11_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4ef073ceaea52589f46877014b6ca9fff4f65d9fee09eed51d3f2225668bfb2 +size 30405 diff --git a/marked/Rel-16/25_series/25142/9ed248b025d766251d58be10b01a1cc0_img.jpg b/marked/Rel-16/25_series/25142/9ed248b025d766251d58be10b01a1cc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1749b36e3c085e9461efda498c838233103c4353 --- /dev/null +++ b/marked/Rel-16/25_series/25142/9ed248b025d766251d58be10b01a1cc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38bf8b60f4f77f8f3f11a4ca151c030077cbbf13a3174226617c6466c7458916 +size 30257 diff --git a/marked/Rel-16/25_series/25142/9f5f9afcedaa0d9b7991976f5000865c_img.jpg b/marked/Rel-16/25_series/25142/9f5f9afcedaa0d9b7991976f5000865c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..411630692b420c5dd2e03c9bb764cf509758e09d --- /dev/null +++ b/marked/Rel-16/25_series/25142/9f5f9afcedaa0d9b7991976f5000865c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe5c6bffbfd619193196fcd13e1b53352bdd79cb3624c33fc840bbf4df881b8e +size 227155 diff --git a/marked/Rel-16/25_series/25142/a4e9abbc6ca82471f1a223d0a68cd45e_img.jpg b/marked/Rel-16/25_series/25142/a4e9abbc6ca82471f1a223d0a68cd45e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0924d6d14f6da10598d091f93275ac9196a98cb5 --- /dev/null +++ b/marked/Rel-16/25_series/25142/a4e9abbc6ca82471f1a223d0a68cd45e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c071a9e16696760a52e7389547e054689dd16392aeedf310f4d0d8cbe802002e +size 30722 diff --git a/marked/Rel-16/25_series/25142/aa23dbbc50355aed4783a5698f0ac691_img.jpg b/marked/Rel-16/25_series/25142/aa23dbbc50355aed4783a5698f0ac691_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56091badabf1f79b1df768666731dbf063e0ad71 --- /dev/null +++ b/marked/Rel-16/25_series/25142/aa23dbbc50355aed4783a5698f0ac691_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:602d92ee0865160d367bb6c6230e08217cf0cc99a62bd6fc1da106e4ab5aceaf +size 224249 diff --git a/marked/Rel-16/25_series/25142/b437cd7078b36507e5d918fe6224e6dd_img.jpg b/marked/Rel-16/25_series/25142/b437cd7078b36507e5d918fe6224e6dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11f2eee32564a0220b4ad54bc9c5028287f1fdfc --- /dev/null +++ b/marked/Rel-16/25_series/25142/b437cd7078b36507e5d918fe6224e6dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0d966853169edead6e26e6a97959ba9640823f3d3b905ef8f5a37e9845a65d3 +size 53372 diff --git a/marked/Rel-16/25_series/25142/b57fe904794260818d988eb4bf9a1d0b_img.jpg b/marked/Rel-16/25_series/25142/b57fe904794260818d988eb4bf9a1d0b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b87e6ff235d23d2fb9ff7115e108662a68c4140 --- /dev/null +++ b/marked/Rel-16/25_series/25142/b57fe904794260818d988eb4bf9a1d0b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d488989d09b50811c22064fef585c6b19ded5d49794c377fa87138fb5999804 +size 43482 diff --git a/marked/Rel-16/25_series/25142/b6bb85a3062dcabdd98c757aec4413b2_img.jpg b/marked/Rel-16/25_series/25142/b6bb85a3062dcabdd98c757aec4413b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..efd3630fc789b375133708469bb74a3fc4942bb8 --- /dev/null +++ b/marked/Rel-16/25_series/25142/b6bb85a3062dcabdd98c757aec4413b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f71f297b3fa54a26afc69c0b08c05324f4aacd98e8b4ff988945a4155129ad85 +size 58025 diff --git a/marked/Rel-16/25_series/25142/b988d13a7e9ebb10a1df8e0957a15c51_img.jpg b/marked/Rel-16/25_series/25142/b988d13a7e9ebb10a1df8e0957a15c51_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1dabf8d54437af47f3d74f869e9a7f86ddd67b2e --- /dev/null +++ b/marked/Rel-16/25_series/25142/b988d13a7e9ebb10a1df8e0957a15c51_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2baf244549fa010a030b1c9255099b5aad2fd42059a6d9d90a52c6f48deaa7c4 +size 25416 diff --git a/marked/Rel-16/25_series/25142/c0ef0292328b1602e278f6a0b2ee07e0_img.jpg b/marked/Rel-16/25_series/25142/c0ef0292328b1602e278f6a0b2ee07e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2a3b8eff36b6906d2298708f1c1722d0f764d5d --- /dev/null +++ b/marked/Rel-16/25_series/25142/c0ef0292328b1602e278f6a0b2ee07e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:57a37200415239a51a318cd6ee4a546c03a495ab6f9fd0b6a85657f827894011 +size 226091 diff --git a/marked/Rel-16/25_series/25142/c24f22afc8106a8f9b76c759a1db6891_img.jpg b/marked/Rel-16/25_series/25142/c24f22afc8106a8f9b76c759a1db6891_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1459d37d198f328bf5cbae9a9da1154bb662804 --- /dev/null +++ b/marked/Rel-16/25_series/25142/c24f22afc8106a8f9b76c759a1db6891_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ed2900fb012664b72b59da3c4c6e40442bb834e48d35cf96673113765bb75e2 +size 138159 diff --git a/marked/Rel-16/25_series/25142/c55e08c6d3924487ee74b344ef4755f5_img.jpg b/marked/Rel-16/25_series/25142/c55e08c6d3924487ee74b344ef4755f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98e8232afdf77eaf7027651f6e53049c2110c9b8 --- /dev/null +++ b/marked/Rel-16/25_series/25142/c55e08c6d3924487ee74b344ef4755f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ddd86fd3bd5525c34ffdc6e6bc7bce4fb3026b2f165fdbe0c333d889a585933 +size 39225 diff --git a/marked/Rel-16/25_series/25142/c9bfcc4c4ef694696c292b03de45d2bb_img.jpg b/marked/Rel-16/25_series/25142/c9bfcc4c4ef694696c292b03de45d2bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2423ef853d0940377a89166cab92706985470d8 --- /dev/null +++ b/marked/Rel-16/25_series/25142/c9bfcc4c4ef694696c292b03de45d2bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a8086780f39cedb448d64577d9aab7d6c1c4f33e82d0d52c73910b78009e9325 +size 47892 diff --git a/marked/Rel-16/25_series/25142/cdb980c2fe504f3132b907d4de707c7f_img.jpg b/marked/Rel-16/25_series/25142/cdb980c2fe504f3132b907d4de707c7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14b1ddc7a636d7f2558b1010e0bdee095dd3f20b --- /dev/null +++ b/marked/Rel-16/25_series/25142/cdb980c2fe504f3132b907d4de707c7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aed949a564275a0a14740fc26a759b1a731bcbb45a8c363b7974ad7e9a024485 +size 48317 diff --git a/marked/Rel-16/25_series/25142/cf734b5645d3e02a8df25f67904cd2d3_img.jpg b/marked/Rel-16/25_series/25142/cf734b5645d3e02a8df25f67904cd2d3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b7c2b9b1dfc6223c1f67f4d8dc99e7d35cb349a --- /dev/null +++ b/marked/Rel-16/25_series/25142/cf734b5645d3e02a8df25f67904cd2d3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05adcd9161ac35298f0b6def93d1c9d930e3460d96cf3c53db5c961e77e90f97 +size 169716 diff --git a/marked/Rel-16/25_series/25142/db4df156e75d1e433a48c718d5d219a2_img.jpg b/marked/Rel-16/25_series/25142/db4df156e75d1e433a48c718d5d219a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..310f418f9cf601182bb2b60b0785758bc7c8efd2 --- /dev/null +++ b/marked/Rel-16/25_series/25142/db4df156e75d1e433a48c718d5d219a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7fbe670900a0a8a9f4ddf10770b8e4f4635257bbb31297f4c392f65db7ce67b +size 111262 diff --git a/marked/Rel-16/25_series/25142/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/25_series/25142/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1634055b8baca92684f6b259a011a592e3180c24 --- /dev/null +++ b/marked/Rel-16/25_series/25142/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca545d7b06d4bacd9ff3aee93978c6bbb27ff04e9f7fcbd1addccfde292fed22 +size 57306 diff --git a/marked/Rel-16/25_series/25142/f82e45705e7d3f028c734e7278ef154e_img.jpg b/marked/Rel-16/25_series/25142/f82e45705e7d3f028c734e7278ef154e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ce1b4b00570c2025f11a4163ffdba85c0c2b92c --- /dev/null +++ b/marked/Rel-16/25_series/25142/f82e45705e7d3f028c734e7278ef154e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:426ed03fb706033fd20e8c095aa28962f82d00f55890767ce6399a98fdfc82ab +size 60246 diff --git a/marked/Rel-16/25_series/25142/fe82ce00eaac699b60a35ccb558e7851_img.jpg b/marked/Rel-16/25_series/25142/fe82ce00eaac699b60a35ccb558e7851_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11d11b0027885597c2f1699f53f68734289cfe3a --- /dev/null +++ b/marked/Rel-16/25_series/25142/fe82ce00eaac699b60a35ccb558e7851_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f117fa0351a1705e026f8fcd04178745af7ee9af91c4d9692c24b6172f6591df +size 231482 diff --git a/marked/Rel-16/25_series/25142/raw.md b/marked/Rel-16/25_series/25142/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..33e9c25f06509c8d76a6b23776a2805c562cde39 --- /dev/null +++ b/marked/Rel-16/25_series/25142/raw.md @@ -0,0 +1,10788 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------------|----| +| Foreword..... | 17 | +| 1 Scope..... | 18 | +| 2 References..... | 18 | +| 3 Definitions, symbols, and abbreviations..... | 19 | +| 3.1 Definitions..... | 19 | +| 3.2 Symbols..... | 20 | +| 3.3 Abbreviations..... | 20 | +| 4 Frequency bands and channel arrangement..... | 22 | +| 4.1 General..... | 22 | +| 4.2 Frequency bands..... | 22 | +| 4.3 TX-RX frequency separation..... | 23 | +| 4.3.1 3,84 Mcps TDD option..... | 23 | +| 4.3.2 1,28 Mcps TDD option..... | 23 | +| 4.3.3 7,68 Mcps TDD option..... | 23 | +| 4.4 Channel arrangement..... | 23 | +| 4.4.1 Channel spacing..... | 23 | +| 4.4.1.1 3,84 Mcps TDD option..... | 23 | +| 4.4.1.2 1,28 Mcps TDD option..... | 23 | +| 4.4.1.3 7,68 Mcps TDD option..... | 23 | +| 4.4.2 Channel raster..... | 23 | +| 4.4.2.1 3,84 Mcps TDD Option..... | 23 | +| 4.4.3 Channel number..... | 23 | +| 5 General test conditions and declarations..... | 24 | +| 5.1 Base station classes..... | 24 | +| 5.1.1 Applicability of requirements and BS class definition..... | 24 | +| 5.1.2 Manufacturer's declaration of supported RF configurations..... | 24 | +| 5.2 Output power..... | 25 | +| 5.3 Specified frequency range and supported channel bandwidth..... | 25 | +| 5.3.1 RF bandwidth position for multi-carrier testing..... | 26 | +| 5.4 Relationship between RF generation and chip clock..... | 26 | +| 5.5 Spectrum emission mask..... | 26 | +| 5.6 Adjacent Channel Leakage power Ratio (ACLR)..... | 26 | +| 5.7 Tx spurious emissions..... | 27 | +| 5.7.1 Category of spurious emissions limit..... | 27 | +| 5.7.2 Co-existence with GSM..... | 27 | +| 5.7.3 Co-existence with DCS 1800..... | 27 | +| 5.7.4 Co-existence with UTRA FDD..... | 27 | +| 5.7.5 Co-existence with unsynchronised UTRA TDD and/or E-UTRA TDD..... | 28 | +| 5.8 Blocking characteristics..... | 28 | +| 5.9 Test environments..... | 28 | +| 5.9.1 Normal test environment..... | 28 | +| 5.9.2 Extreme test environment..... | 29 | +| 5.9.2.1 Extreme temperature..... | 29 | +| 5.9.3 Vibration..... | 29 | +| 5.9.4 Power supply..... | 29 | +| 5.10 Acceptable uncertainty of Test System..... | 30 | +| 5.10.1 Measurement of test environments..... | 30 | +| 5.10.2 Measurement of transmitter..... | 31 | +| 5.10.3 Measurement of receiver..... | 35 | +| 5.10.4 Measurement of performance requirements..... | 36 | +| 5.11 Test Tolerances (informative)..... | 36 | +| 5.11.1 Transmitter..... | 37 | +| 5.11.2 Receiver..... | 39 | +| 5.11.3 Performance requirements..... | 39 | +| 5.12 Interpretation of measurement results..... | 39 | + +| | | | +|-----------|-----------------------------------------------------------------------|----| +| 5.13 | Selection of configurations for testing..... | 39 | +| 5.14 | BS Configurations..... | 40 | +| 5.14.1 | Receiver diversity..... | 40 | +| 5.14.2 | Duplexers..... | 40 | +| 5.14.3 | Power supply options..... | 40 | +| 5.14.4 | Ancillary RF amplifiers..... | 41 | +| 5.14.5 | BS using antenna arrays..... | 41 | +| 5.14.5.1 | Receiver tests..... | 41 | +| 5.14.5.2 | Transmitter tests..... | 41 | +| 5.14.6 | MIMO transmission..... | 42 | +| 5.15 | Overview of the conformance test requirements..... | 42 | +| 5.16 | Format and interpretation of tests..... | 44 | +| 5.17 | Regional requirements..... | 44 | +| 5.18 | Definition of Additive White Gaussian Noise (AWGN) Interferer..... | 45 | +| 5.19 | Applicability of requirements..... | 45 | +| 5.20 | Test configurations for multi-carrier operation..... | 46 | +| 5.20.1 | UTTC1: Multi-carrier operation test configuration..... | 46 | +| 5.20.1.1 | UTTC1 generation..... | 46 | +| 5.20.1.1 | UTTC1 power allocation..... | 46 | +| 5.20.2 | UTTC2: Multi-band test configuration for full carrier allocation..... | 46 | +| 5.20.2.1 | UTTC2 generation..... | 46 | +| 5.20.2.2 | UTTC2 power allocation..... | 47 | +| 5.21 | Applicability of test configurations..... | 47 | +| 5.22 | Requirements for BS capable of multi-band operation..... | 49 | +| 6 | Transmitter characteristics..... | 50 | +| 6.1 | General..... | 50 | +| 6.1.1 | IMB Test Models..... | 50 | +| 6.1.1.1 | IMB Test Model 1 - TM 1..... | 50 | +| 6.1.1.2 | IMB Test Model 2 - TM 2..... | 51 | +| 6.2 | Maximum output power..... | 51 | +| 6.2.1 | Definition and applicability..... | 51 | +| 6.2.2 | Minimum Requirements..... | 51 | +| 6.2.3 | Test purpose..... | 51 | +| 6.2.4 | Method of test..... | 52 | +| 6.2.4.1 | Initial conditions..... | 52 | +| 6.2.4.1.0 | General test conditions..... | 52 | +| 6.2.4.1.1 | 3,84 Mcps TDD option..... | 52 | +| 6.2.4.1.2 | 1,28 Mcps TDD option..... | 52 | +| 6.2.4.1.3 | 7,68 Mcps TDD option..... | 53 | +| 6.2.4.2 | Procedure..... | 53 | +| 6.2.4.2.1 | 3,84 Mcps TDD option..... | 53 | +| 6.2.4.2.2 | 1,28 Mcps TDD option..... | 53 | +| 6.2.4.2.3 | 7,68 Mcps TDD option..... | 53 | +| 6.2.5 | Test Requirements..... | 54 | +| 6.3 | Frequency stability..... | 54 | +| 6.3.1 | Definition and applicability..... | 54 | +| 6.3.2 | Minimum Requirements..... | 54 | +| 6.3.3 | Test purpose..... | 54 | +| 6.3.4 | Method of test..... | 54 | +| 6.3.4.1 | Initial conditions..... | 54 | +| 6.3.4.1.0 | General test conditions..... | 54 | +| 6.3.4.1.1 | 3,84 Mcps TDD option..... | 55 | +| 6.3.4.1.2 | 1,28 Mcps TDD option..... | 55 | +| 6.3.4.1.3 | 7,68 Mcps TDD option..... | 55 | +| 6.3.4.2 | Procedure..... | 56 | +| 6.3.5 | Test Requirements..... | 56 | +| 6.4 | Output power dynamics..... | 56 | +| 6.4.1 | Inner loop power control..... | 56 | +| 6.4.2 | Power control steps..... | 57 | +| 6.4.2.1 | Definition and applicability..... | 57 | +| 6.4.2.2 | Minimum Requirements..... | 57 | + +| | | | +|-------------|---------------------------------------------------|----| +| 6.4.2.3 | Test purpose..... | 57 | +| 6.4.2.4 | Method of test..... | 57 | +| 6.4.2.4.1 | Initial conditions..... | 57 | +| 6.4.2.4.1.0 | General test conditions..... | 57 | +| 6.4.2.4.1.1 | 3,84 Mcps TDD option..... | 57 | +| 6.4.2.4.1.2 | 1,28 Mcps TDD option..... | 58 | +| 6.4.2.4.1.3 | 7,68 Mcps TDD option..... | 58 | +| 6.4.2.4.2 | Procedure..... | 59 | +| 6.4.2.4.2.1 | 3,84 Mcps TDD option..... | 59 | +| 6.4.2.4.2.2 | 1,28 Mcps TDD option..... | 59 | +| 6.4.2.4.2.3 | 7,68 Mcps TDD option..... | 60 | +| 6.4.2.5 | Test Requirements..... | 60 | +| 6.4.2.5.1 | 3,84 Mcps TDD option..... | 60 | +| 6.4.2.5.2 | 1,28 Mcps TDD option..... | 60 | +| 6.4.2.5.3 | 7,68 Mcps TDD option..... | 61 | +| 6.4.3 | Power control dynamic range..... | 61 | +| 6.4.3.1 | Definition and applicability..... | 61 | +| 6.4.3.2 | Minimum Requirements..... | 61 | +| 6.4.3.3 | Test purpose..... | 61 | +| 6.4.3.4 | Method of test..... | 61 | +| 6.4.3.4.1 | Initial conditions..... | 61 | +| 6.4.3.4.1.0 | General test conditions..... | 61 | +| 6.4.3.4.1.1 | 3,84 Mcps TDD option..... | 61 | +| 6.4.3.4.1.2 | 1,28 Mcps TDD option..... | 62 | +| 6.4.3.4.1.3 | 7,68 Mcps TDD option..... | 62 | +| 6.4.3.4.2 | Procedure..... | 63 | +| 6.4.3.4.2.1 | 3,84 Mcps TDD option..... | 63 | +| 6.4.3.4.2.2 | 1,28 Mcps TDD option..... | 63 | +| 6.4.3.4.2.3 | 7,68 Mcps TDD option..... | 64 | +| 6.4.3.5 | Test Requirements..... | 64 | +| 6.4.4 | Minimum output power..... | 64 | +| 6.4.4.1 | Definition and applicability..... | 64 | +| 6.4.4.2 | Minimum Requirements..... | 64 | +| 6.4.4.3 | Test purpose..... | 64 | +| 6.4.4.4 | Method of test..... | 65 | +| 6.4.4.4.1 | Initial conditions..... | 65 | +| 6.4.4.4.1.0 | General test conditions..... | 65 | +| 6.4.4.4.1.1 | 3,84 Mcps TDD option..... | 65 | +| 6.4.4.4.1.2 | 1,28 Mcps TDD option..... | 65 | +| 6.4.4.4.1.3 | 7,68 Mcps TDD option..... | 66 | +| 6.4.4.4.2 | Procedure..... | 66 | +| 6.4.4.4.2.1 | 3,84 Mcps TDD option..... | 66 | +| 6.4.4.4.2.2 | 1,28 Mcps TDD option..... | 66 | +| 6.4.4.4.2.3 | 7,68 Mcps TDD option..... | 67 | +| 6.4.4.5 | Test Requirements..... | 67 | +| 6.4.5 | Primary CCPCH power..... | 67 | +| 6.4.5.1 | Definition and applicability..... | 67 | +| 6.4.5.2 | Minimum Requirements..... | 67 | +| 6.4.5.3 | Test purpose..... | 68 | +| 6.4.5.4 | Method of test..... | 68 | +| 6.4.5.4.1 | Initial conditions..... | 68 | +| 6.4.5.4.1.0 | General test conditions..... | 68 | +| 6.4.5.4.1.1 | 3,84 Mcps TDD option..... | 68 | +| 6.4.5.4.1.2 | 1,28 Mcps TDD option..... | 68 | +| 6.4.5.4.1.3 | 7,68 Mcps TDD option..... | 69 | +| 6.4.5.4.2 | Procedure..... | 69 | +| 6.4.5.4.2.1 | 3,84 Mcps TDD option..... | 69 | +| 6.4.5.4.2.2 | 1,28 Mcps TDD option..... | 69 | +| 6.4.5.4.2.3 | 7,68 Mcps TDD option..... | 70 | +| 6.4.5.5 | Test Requirements..... | 70 | +| 6.4.6 | Differential accuracy of Primary CCPCH power..... | 70 | + +| | | | +|-------------|-----------------------------------|----| +| 6.4.6.1 | Definition and applicability..... | 70 | +| 6.4.6.2 | Minimum Requirements..... | 70 | +| 6.4.6.3 | Test purpose..... | 70 | +| 6.4.6.4 | Method of test..... | 70 | +| 6.4.6.4.1 | Initial conditions..... | 70 | +| 6.4.6.4.1.0 | General test conditions..... | 70 | +| 6.4.6.4.1.1 | 3,84 Mcps TDD option..... | 71 | +| 6.4.6.4.1.2 | 1,28 Mcps TDD option..... | 71 | +| 6.4.6.4.1.3 | 7,68 Mcps TDD option..... | 71 | +| 6.4.6.4.2 | Procedure..... | 72 | +| 6.4.6.4.2.1 | 3,84 Mcps TDD option..... | 72 | +| 6.4.6.4.2.2 | 1,28 Mcps TDD option..... | 72 | +| 6.4.6.4.2.3 | 7,68 Mcps TDD option..... | 72 | +| 6.4.6.5 | Test Requirements..... | 72 | +| 6.5 | Transmit ON/OFF power..... | 73 | +| 6.5.1 | Transmit OFF power..... | 73 | +| 6.5.1.1 | Definition and applicability..... | 73 | +| 6.5.1.2 | Minimum Requirements..... | 73 | +| 6.5.1.2.1 | 3,84 Mcps TDD option..... | 73 | +| 6.5.1.2.2 | 1,28 Mcps TDD option..... | 73 | +| 6.5.1.2.3 | 7,68 Mcps TDD option..... | 73 | +| 6.5.1.3 | Test purpose..... | 73 | +| 6.5.1.4 | Method of test..... | 73 | +| 6.5.1.4.1 | Initial conditions..... | 73 | +| 6.5.1.4.2 | Procedure..... | 73 | +| 6.5.1.5 | Test Requirements..... | 73 | +| 6.5.2 | Transmit ON/OFF time mask..... | 73 | +| 6.5.2.1 | Definition and applicability..... | 73 | +| 6.5.2.2 | Minimum Requirements..... | 74 | +| 6.5.2.2.1 | 3,84 Mcps TDD option..... | 74 | +| 6.5.2.2.2 | 1,28 Mcps TDD option..... | 74 | +| 6.5.2.2.3 | 7,68 Mcps TDD option..... | 74 | +| 6.5.2.3 | Test purpose..... | 75 | +| 6.5.2.4 | Method of test..... | 75 | +| 6.5.2.4.1 | Initial conditions..... | 75 | +| 6.5.2.4.1.0 | General test conditions..... | 75 | +| 6.5.2.4.1.1 | 3,84 Mcps TDD option..... | 75 | +| 6.5.2.4.1.2 | 1,28 Mcps TDD option..... | 76 | +| 6.5.2.4.1.3 | 7,68 Mcps TDD option..... | 76 | +| 6.5.2.4.2 | Procedure..... | 76 | +| 6.5.2.4.2.1 | 3,84 Mcps TDD option..... | 76 | +| 6.5.2.4.2.2 | 1,28 Mcps TDD option..... | 76 | +| 6.5.2.4.2.3 | 7,68 Mcps TDD option..... | 77 | +| 6.5.2.5 | Test Requirements..... | 77 | +| 6.5.2.5.1 | 3,84 Mcps TDD option..... | 77 | +| 6.5.2.5.2 | 1,28 Mcps TDD option..... | 77 | +| 6.5.2.5.3 | 7,68 Mcps TDD option..... | 77 | +| 6.6 | Output RF spectrum emissions..... | 77 | +| 6.6.1 | Occupied bandwidth..... | 77 | +| 6.6.1.1 | Definition and applicability..... | 77 | +| 6.6.1.2 | Minimum Requirements..... | 77 | +| 6.6.1.2.1 | 3,84 Mcps TDD option..... | 77 | +| 6.6.1.2.2 | 1,28 Mcps TDD option..... | 77 | +| 6.6.1.2.3 | 7,68 Mcps TDD option..... | 77 | +| 6.6.1.3 | Test purpose..... | 78 | +| 6.6.1.4 | Method of test..... | 78 | +| 6.6.1.4.1 | Initial conditions..... | 78 | +| 6.6.1.4.1.0 | General test conditions..... | 78 | +| 6.6.1.4.1.1 | 3,84 Mcps TDD option..... | 78 | +| 6.6.1.4.1.2 | 1,28 Mcps TDD option..... | 78 | +| 6.6.1.4.1.3 | 7,68 Mcps TDD option..... | 79 | + +| | | | +|-----------------|----------------------------------------------------------------------|----| +| 6.6.1.4.2 | Procedure..... | 79 | +| 6.6.1.4.2.1 | 3,84 Mcps TDD option..... | 79 | +| 6.6.1.4.2.2 | 1,28 Mcps TDD option..... | 79 | +| 6.6.1.4.2.3 | 7,68 Mcps TDD option..... | 80 | +| 6.6.1.5 | Test Requirements..... | 80 | +| 6.6.1.5.1 | 3,84 Mcps TDD option..... | 80 | +| 6.6.1.5.2 | 1,28 Mcps TDD option..... | 80 | +| 6.6.1.5.3 | 7,68 Mcps TDD option..... | 80 | +| 6.6.2 | Out of band emission..... | 80 | +| 6.6.2.1 | Spectrum emission mask..... | 81 | +| 6.6.2.1.1 | Definition and applicability..... | 81 | +| 6.6.2.1.1.1 | 3,84 Mcps TDD option..... | 81 | +| 6.6.2.1.1.2 | 1,28 Mcps TDD option..... | 81 | +| 6.6.2.1.1.3 | 7,68 Mcps TDD option..... | 81 | +| 6.6.2.1.2 | Minimum Requirements..... | 81 | +| 6.6.2.1.2.1 | 3,84 Mcps TDD option..... | 81 | +| 6.6.2.1.2.2 | 1,28 Mcps TDD option..... | 82 | +| 6.6.2.1.2.3 | 7,68 Mcps TDD option..... | 84 | +| 6.6.2.1.3 | Test purpose..... | 85 | +| 6.6.2.1.4 | Method of test..... | 85 | +| 6.6.2.1.4.1 | Initial conditions..... | 85 | +| 6.6.2.1.4.1.0 | General test conditions..... | 85 | +| 6.6.2.1.4.1.1 | 3,84 Mcps TDD option - General test set up..... | 85 | +| 6.6.2.1.4.1.2 | 1,28 Mcps TDD option - General test set up..... | 85 | +| 6.6.2.1.4.1.3 | 1,28 Mcps TDD option - Special test set up for 16QAM capable BS..... | 86 | +| 6.6.2.1.4.1.4 | 3,84 Mcps TDD option - Special test set up for 16QAM capable BS..... | 86 | +| 6.6.2.1.4.1.5 | 7,68 Mcps TDD option - General test set up..... | 87 | +| 6.6.2.1.4.1.6 | 7,68 Mcps TDD option - Special test set up for 16QAM capable BS..... | 87 | +| 6.6.2.1.4.2 | Procedure..... | 88 | +| 6.6.2.1.4.2.1 | 3,84 Mcps TDD option..... | 88 | +| 6.6.2.1.4.2.2 | 1,28 Mcps TDD option..... | 88 | +| 6.6.2.1.4.2.3 | 1,28 Mcps TDD option - 16QAM capable BS..... | 88 | +| 6.6.2.1.4.2.4 | 3,84 Mcps TDD option - 16QAM capable BS..... | 88 | +| 6.6.2.1.4.2.5 | 7,68 Mcps TDD option..... | 88 | +| 6.6.2.1.4.2.6 | 7,68 Mcps TDD option - 16QAM capable BS..... | 88 | +| 6.6.2.1.5 | Test Requirements..... | 89 | +| 6.6.2.1.5.1 | 3,84 Mcps TDD option..... | 89 | +| 6.6.2.1.5.2 | 1,28 Mcps TDD option..... | 90 | +| 6.6.2.1.5.3 | 1,28 Mcps TDD option - 16QAM capable BS..... | 91 | +| 6.6.2.1.5.4 | 3,84 Mcps TDD option - 16QAM capable BS..... | 91 | +| 6.6.2.1.5.5 | 7,68 Mcps TDD option..... | 91 | +| 6.6.2.1.5.6 | 7,68 Mcps TDD option - 16QAM capable BS..... | 92 | +| 6.6.2.2 | Adjacent Channel Leakage power Ratio (ACLR)..... | 92 | +| 6.6.2.2.1 | Definition and applicability..... | 92 | +| 6.6.2.2.2 | Minimum Requirements..... | 92 | +| 6.6.2.2.2.1 | Minimum requirement..... | 92 | +| 6.6.2.2.2.1.1 | 3,84 Mcps TDD option..... | 92 | +| 6.6.2.2.2.1.2 | 1,28 Mcps TDD option..... | 93 | +| 6.6.2.2.2.1.3 | 7,68 Mcps TDD option..... | 93 | +| 6.6.2.2.2.2 | Void..... | 93 | +| 6.6.2.2.2.2.1 | Void..... | 93 | +| 6.6.2.2.2.2.1.1 | Void..... | 93 | +| 6.6.2.2.2.2.1.2 | Void..... | 94 | +| 6.6.2.2.2.2.2 | Void..... | 94 | +| 6.6.2.2.2.2.2.1 | Void..... | 94 | +| 6.6.2.2.2.2.2.2 | Void..... | 94 | +| 6.6.2.2.2.2.3 | Void..... | 94 | +| 6.6.2.2.2.2.3.1 | Void..... | 94 | +| 6.6.2.2.2.2.3.2 | Void..... | 94 | +| 6.6.2.2.2.3 | Void..... | 94 | +| 6.6.2.2.2.3.1 | Void..... | 94 | + +| | | | +|-----------------|----------------------------------------------------------------------|-----| +| 6.6.2.2.2.3.1.1 | Void..... | 94 | +| 6.6.2.2.2.3.1.2 | Void..... | 94 | +| 6.6.2.2.2.3.2 | Void..... | 94 | +| 6.6.2.2.2.3.2.1 | Void..... | 94 | +| 6.6.2.2.2.3.2.2 | Void..... | 94 | +| 6.6.2.2.2.3.3 | Void..... | 94 | +| 6.6.2.2.2.3.3.1 | Void..... | 94 | +| 6.6.2.2.2.3.3.2 | Void..... | 94 | +| 6.6.2.2.3 | Test purpose..... | 94 | +| 6.6.2.2.4 | Method of test..... | 94 | +| 6.6.2.2.4.1 | Initial conditions..... | 94 | +| 6.6.2.2.4.1.0 | General test conditions..... | 94 | +| 6.6.2.2.4.1.1 | 3,84 Mcps TDD option - General test set up..... | 95 | +| 6.6.2.2.4.1.2 | 1,28 Mcps TDD option - General test set up..... | 95 | +| 6.6.2.2.4.1.3 | 1,28 Mcps TDD option - Special test set up for 16QAM capable BS..... | 95 | +| 6.6.2.2.4.1.4 | 3,84 Mcps TDD option - Special test set up for 16QAM capable BS..... | 96 | +| 6.6.2.2.4.1.5 | 7,68 Mcps TDD option - General test set up..... | 96 | +| 6.6.2.2.4.1.6 | 7,68 Mcps TDD option - Special test set up for 16QAM capable BS..... | 97 | +| 6.6.2.2.4.2 | Procedure..... | 97 | +| 6.6.2.2.4.2.1 | 3,84 Mcps TDD option..... | 97 | +| 6.6.2.2.4.2.2 | 1,28 Mcps TDD option..... | 98 | +| 6.6.2.2.4.2.3 | 1,28 Mcps TDD option - 16QAM capable BS..... | 98 | +| 6.6.2.2.4.2.4 | 3,84 Mcps TDD option - 16QAM capable BS..... | 98 | +| 6.6.2.2.4.2.5 | 7,68 Mcps TDD option..... | 98 | +| 6.6.2.2.4.2.6 | 7,68 Mcps TDD option - 16QAM capable BS..... | 99 | +| 6.6.2.2.5 | Test Requirements..... | 99 | +| 6.6.2.2.5.1 | 3,84 Mcps TDD option..... | 99 | +| 6.6.2.2.5.2 | 1,28 Mcps TDD option..... | 99 | +| 6.6.2.2.5.3 | 1,28 Mcps TDD option - 16QAM capable BS..... | 100 | +| 6.6.2.2.5.4 | 3,84 Mcps TDD option - 16QAM capable BS..... | 100 | +| 6.6.2.2.5.5 | 7,68 Mcps TDD option..... | 100 | +| 6.6.2.2.5.6 | 7,68 Mcps TDD option - 16QAM capable BS..... | 100 | +| 6.6.3 | Spurious emissions..... | 100 | +| 6.6.3.1 | Definition and applicability..... | 100 | +| 6.6.3.2 | Minimum Requirements..... | 101 | +| 6.6.3.2.1 | Mandatory requirements..... | 101 | +| 6.6.3.2.1.1 | Spurious emissions (Category A)..... | 101 | +| 6.6.3.2.1.1.1 | 3,84 Mcps TDD option..... | 101 | +| 6.6.3.2.1.1.2 | 1,28 Mcps TDD option..... | 101 | +| 6.6.3.2.1.1.3 | 7,68 Mcps TDD option..... | 101 | +| 6.6.3.2.1.2 | Spurious emissions (Category B)..... | 102 | +| 6.6.3.2.1.2.1 | 3,84 Mcps TDD option..... | 102 | +| 6.6.3.2.1.2.2 | 1,28 Mcps TDD option..... | 102 | +| 6.6.3.2.1.2.3 | 7,68 Mcps TDD option..... | 103 | +| 6.6.3.2.2 | Co-existence with GSM, DCS, UTRA and/or E-UTRA..... | 103 | +| 6.6.3.2.2.1 | Operation in the same geographic area..... | 103 | +| 6.6.3.2.2.2 | Co-located base stations..... | 106 | +| 6.6.3.2.3 | (void)..... | 108 | +| 6.6.3.2.3.1 | (void)..... | 108 | +| 6.6.3.2.3.2 | Void..... | 108 | +| 6.6.3.2.4 | Void..... | 108 | +| 6.6.3.2.5 | Co-existence with unsynchronised UTRA TDD and/or E-UTRA TDD..... | 108 | +| 6.6.3.2.5.1 | Operation in the same geographic area..... | 108 | +| 6.6.3.2.5.1.1 | 3,84 Mcps TDD option..... | 108 | +| 6.6.3.2.5.1.2 | 1,28 Mcps TDD option..... | 109 | +| 6.6.3.2.5.1.3 | 7,68 Mcps TDD option..... | 109 | +| 6.6.3.2.5.2 | Co-located base stations..... | 110 | +| 6.6.3.2.5.2.1 | 3,84 Mcps TDD option..... | 110 | +| 6.6.3.2.5.2.2 | 1,28 Mcps TDD option..... | 111 | +| 6.6.3.2.5.2.3 | 7,68 Mcps TDD option..... | 112 | +| 6.6.3.2.6 | Co-existence with PHS..... | 113 | + +| | | | +|-------------|----------------------------------------------------------------------|-----| +| 6.6.3.2.6.1 | 3,84 Mcps TDD option..... | 113 | +| 6.6.3.2.6.2 | (void)..... | 114 | +| 6.6.3.2.6.3 | 7,68 Mcps TDD option..... | 114 | +| 6.6.3.3 | Test purpose..... | 114 | +| 6.6.3.3.1 | 3,84 Mcps TDD option..... | 114 | +| 6.6.3.3.2 | 1,28 Mcps TDD option..... | 114 | +| 6.6.3.3.3 | 7,68 Mcps TDD option..... | 114 | +| 6.6.3.4 | Method of test..... | 114 | +| 6.6.3.4.1 | Initial conditions..... | 114 | +| 6.6.3.4.1.0 | General test conditions..... | 115 | +| 6.6.3.4.1.1 | 3,84 Mcps TDD option - General test set up..... | 115 | +| 6.6.3.4.1.2 | 1,28 Mcps TDD option - General test set up..... | 115 | +| 6.6.3.4.1.3 | 1,28 Mcps TDD option - Special test set up for 16QAM capable BS..... | 115 | +| 6.6.3.4.1.4 | 3,84 Mcps TDD option - Special test set up for 16QAM capable BS..... | 116 | +| 6.6.3.4.1.5 | 7,68 Mcps TDD option - General test set up..... | 116 | +| 6.6.3.4.1.6 | 7,68 Mcps TDD option - Special test set up for 16QAM capable BS..... | 117 | +| 6.6.3.4.2 | Procedure..... | 117 | +| 6.6.3.5 | Test Requirements..... | 117 | +| 6.7 | Transmit intermodulation..... | 118 | +| 6.7.1 | Definition and applicability..... | 118 | +| 6.7.1.1 | 3,84 Mcps TDD option..... | 118 | +| 6.7.1.2 | 1,28 Mcps TDD option..... | 118 | +| 6.7.1.3 | 7,68 Mcps TDD option..... | 118 | +| 6.7.2 | Minimum Requirements..... | 119 | +| 6.7.3 | Test purpose..... | 119 | +| 6.7.4 | Method of test..... | 119 | +| 6.7.4.1 | Initial conditions..... | 119 | +| 6.7.4.1.0 | General test conditions..... | 119 | +| 6.7.4.1.1 | 3,84 Mcps TDD option - General test set up..... | 119 | +| 6.7.4.1.2 | 1,28 Mcps TDD option - General test set up..... | 120 | +| 6.7.4.1.3 | 1,28 Mcps TDD option - Special test set up for 16QAM capable BS..... | 121 | +| 6.7.4.1.4 | 3,84 Mcps TDD option - Special test set up for 16QAM capable BS..... | 122 | +| 6.7.4.1.5 | 7,68 Mcps TDD option - General test set up..... | 123 | +| 6.7.4.1.6 | 7,68 Mcps TDD option - Special test set up for 16QAM capable BS..... | 124 | +| 6.7.4.2 | Procedure..... | 125 | +| 6.7.5 | Test Requirements..... | 125 | +| 6.8 | Transmit Modulation..... | 125 | +| 6.8.1 | Modulation accuracy..... | 125 | +| 6.8.1.1 | Definition and applicability..... | 125 | +| 6.8.1.2 | Minimum Requirements..... | 126 | +| 6.8.1.3 | Test purpose..... | 126 | +| 6.8.1.4 | Method of test..... | 126 | +| 6.8.1.4.1 | Initial conditions..... | 126 | +| 6.8.1.4.1.0 | General test conditions..... | 126 | +| 6.8.1.4.1.1 | 3,84 Mcps TDD option - General test setup..... | 126 | +| 6.8.1.4.1.2 | 1,28 Mcps TDD option - General test set up..... | 126 | +| 6.8.1.4.1.3 | 1,28 Mcps TDD option - Special test set up for 16QAM capable BS..... | 127 | +| 6.8.1.4.1.4 | 3,84 Mcps TDD option - Special test set up for 16QAM capable BS..... | 127 | +| 6.8.1.4.1.5 | 7,68 Mcps TDD option - General test setup..... | 128 | +| 6.8.1.4.1.6 | 7,68 Mcps TDD option - Special test set up for 16QAM capable BS..... | 128 | +| 6.8.1.4.2 | Procedure..... | 129 | +| 6.8.1.4.2.1 | 3,84 Mcps TDD option - General procedure..... | 129 | +| 6.8.1.4.2.2 | 1,28 Mcps TDD option - General procedure..... | 129 | +| 6.8.1.4.2.3 | 1,28 Mcps TDD option - Special procedure for 16QAM capable BS..... | 129 | +| 6.8.1.4.2.4 | 3,84 Mcps TDD option - Special test set up for 16QAM capable BS..... | 130 | +| 6.8.1.4.2.5 | 7,68 Mcps TDD option - General procedure..... | 130 | +| 6.8.1.4.2.6 | 7,68 Mcps TDD option - Special test set up for 16QAM capable BS..... | 131 | +| 6.8.1.5 | Test Requirements..... | 131 | +| 6.8.2 | Peak code domain error..... | 131 | +| 6.8.2.1 | Definition and applicability..... | 131 | +| 6.8.2.2 | Minimum Requirements..... | 132 | + +| | | | +|-------------|----------------------------------------------------------------------|-----| +| 6.8.2.3 | Test purpose..... | 132 | +| 6.8.2.4 | Method of test..... | 132 | +| 6.8.2.4.1 | Initial conditions..... | 132 | +| 6.8.2.4.1.0 | General test conditions..... | 132 | +| 6.8.2.4.1.1 | 3,84 Mcps TDD option - General test set up..... | 132 | +| 6.8.2.4.1.2 | 1,28 Mcps TDD option- General test set up..... | 132 | +| 6.8.2.4.1.3 | 1,28 Mcps TDD option - Special test set up for 16QAM capable BS..... | 133 | +| 6.8.2.4.1.4 | 3,84 Mcps TDD option - Special test set up for 16QAM capable BS..... | 133 | +| 6.8.2.4.1.5 | 7,68 Mcps TDD option - General test set up..... | 134 | +| 6.8.2.4.1.6 | 7,68 Mcps TDD option - Special test set up for 16QAM capable BS..... | 134 | +| 6.8.2.4.2 | Procedure..... | 135 | +| 6.8.2.5 | Test Requirements..... | 135 | +| 6.8.3 | Relative Code Domain Error..... | 135 | +| 6.8.3.1 | Definition and applicability..... | 135 | +| 6.8.3.2 | Minimum requirement..... | 135 | +| 6.8.3.3 | Test Purpose..... | 135 | +| 6.8.3.4 | Method of test..... | 135 | +| 6.8.3.4.1 | Initial conditions..... | 135 | +| 6.8.3.4.1.0 | General test conditions..... | 135 | +| 6.8.3.4.1.1 | 1,28 Mcps TDD option- General test set up..... | 135 | +| 6.8.3.4.1.2 | 1,28 Mcps TDD option - Special test set up for 64QAM capable BS..... | 136 | +| 6.8.3.4.2 | Procedure..... | 136 | +| 6.8.3.5 | Test Requirements..... | 137 | +| 6.8.4 | Time alignment error in MIMO transmission..... | 137 | +| 6.8.4.1 | Definition and applicability..... | 137 | +| 6.8.4.2 | Minimum requirement..... | 137 | +| 6.8.4.3 | Test Purpose..... | 137 | +| 6.8.4.4 | Method of test..... | 137 | +| 6.8.4.4.1 | Initial conditions..... | 137 | +| 6.8.4.4.1.0 | General test conditions..... | 137 | +| 6.8.4.4.1.1 | 1,28 Mcps TDD option- General test set up..... | 137 | +| 6.8.4.4.2 | Procedure..... | 138 | +| 6.8.4.4.2.1 | 1,28 Mcps TDD option..... | 138 | +| 6.8.4.5 | Test Requirements..... | 138 | +| 6.8.4.5.1 | 1,28 Mcps TDD option..... | 138 | +| 7 | Receiver characteristics..... | 138 | +| 7.1 | General..... | 138 | +| 7.2 | Reference sensitivity level..... | 139 | +| 7.2.1 | Definition and applicability..... | 139 | +| 7.2.2 | Minimum Requirements..... | 139 | +| 7.2.2.1 | 3,84 Mcps TDD option..... | 139 | +| 7.2.2.2 | 1,28 Mcps option..... | 140 | +| 7.2.2.3 | 7,68 Mcps TDD option..... | 140 | +| 7.2.3 | Test purpose..... | 140 | +| 7.2.4 | Method of test..... | 140 | +| 7.2.4.1 | Initial conditions..... | 140 | +| 7.2.4.1.0 | General test requirements..... | 140 | +| 7.2.4.1.1 | 3,84 Mcps TDD option..... | 140 | +| 7.2.4.1.2 | 1,28 Mcps TDD option..... | 141 | +| 7.2.4.1.3 | 7,68 Mcps TDD option..... | 141 | +| 7.2.4.2 | Procedure..... | 141 | +| 7.2.5 | Test Requirements..... | 141 | +| 7.2.5.1 | 3,84 Mcps TDD option..... | 141 | +| 7.2.5.2 | 1,28 Mcps TDD option..... | 142 | +| 7.2.5.3 | 7,68 Mcps TDD option..... | 142 | +| 7.3 | Dynamic range..... | 142 | +| 7.3.1 | Definition and applicability..... | 142 | +| 7.3.2 | Minimum Requirements..... | 142 | +| 7.3.2.1 | 3,84 Mcps TDD option..... | 142 | +| 7.3.2.2 | 1,28 Mcps TDD option..... | 142 | +| 7.3.2.3 | 7,68 Mcps TDD option..... | 143 | + +| | | | +|-----------|----------------------------------------------------------------------------------------|-----| +| 7.3.3 | Test purpose..... | 143 | +| 7.3.4 | Method of test..... | 143 | +| 7.3.4.1 | Initial conditions..... | 143 | +| 7.3.4.1.0 | General test conditions..... | 143 | +| 7.3.4.1.1 | 3,84 Mcps TDD option..... | 143 | +| 7.3.4.1.2 | 1,28 Mcps TDD option..... | 144 | +| 7.3.4.1.3 | 7,68 Mcps TDD option..... | 144 | +| 7.3.4.2 | Procedure..... | 144 | +| 7.3.5 | Test Requirements..... | 144 | +| 7.3.5.1 | 3,84 Mcps TDD option..... | 144 | +| 7.3.5.2 | 1,28 Mcps TDD option..... | 145 | +| 7.3.5.3 | 7,68 Mcps TDD option..... | 145 | +| 7.4 | Adjacent Channel Selectivity (ACS)..... | 145 | +| 7.4.1 | Definition and applicability..... | 145 | +| 7.4.2 | Minimum Requirements..... | 145 | +| 7.4.2.1 | 3,84 Mcps TDD option..... | 145 | +| 7.4.2.2 | 1,28 Mcps TDD option..... | 146 | +| 7.4.2.3 | 7,68 Mcps TDD option..... | 146 | +| 7.4.3 | Test purpose..... | 147 | +| 7.4.4 | Method of test..... | 147 | +| 7.4.4.1 | Initial conditions..... | 147 | +| 7.4.4.1.0 | General test conditions..... | 147 | +| 7.4.4.1.1 | 3,84 Mcps TDD option..... | 147 | +| 7.4.4.1.2 | 1,28 Mcps TDD option..... | 147 | +| 7.4.4.1.3 | 7,68 Mcps TDD option..... | 148 | +| 7.4.4.2 | Procedure..... | 148 | +| 7.4.4.2.1 | 3,84 Mcps TDD option..... | 148 | +| 7.4.4.2.2 | 1,28 Mcps TDD option..... | 148 | +| 7.4.4.2.3 | 7,68 Mcps TDD option..... | 148 | +| 7.4.5 | Test Requirements..... | 149 | +| 7.5 | Blocking characteristics..... | 149 | +| 7.5.1 | Definition and applicability..... | 149 | +| 7.5.1.1 | 3,84 Mcps TDD option..... | 149 | +| 7.5.1.2 | 1,28 Mcps TDD option..... | 149 | +| 7.5.1.3 | 7,68 Mcps TDD option..... | 149 | +| 7.5.2 | Minimum Requirements..... | 149 | +| 7.5.2.1 | 3,84 Mcps TDD option..... | 149 | +| 7.5.2.1.1 | General requirements..... | 149 | +| 7.5.2.1.2 | Co-location with GSM, DCS, UTRA-FDD and/or E-UTRA FDD..... | 151 | +| 7.5.2.1.3 | Void..... | 152 | +| 7.5.2.2 | 1,28 Mcps TDD option..... | 152 | +| 7.5.2.2.1 | General requirements..... | 152 | +| 7.5.2.2.2 | Co-location with GSM, DCS, UTRA FDD and/or E-UTRA FDD, UTRA TDD and/or E-UTRA TDD..... | 156 | +| 7.5.2.2.3 | Void..... | 160 | +| 7.5.2.3 | 7,68 Mcps TDD option..... | 160 | +| 7.5.2.3.1 | General requirements..... | 160 | +| 7.5.2.3.2 | Void..... | 162 | +| 7.5.2.3.3 | Void..... | 162 | +| 7.5.2.3.4 | Co-location with GSM, DCS, UTRA-FDD and/or E-UTRA FDD..... | 162 | +| 7.5.3 | Test purpose..... | 163 | +| 7.5.3.1 | 3,84 Mcps TDD option..... | 163 | +| 7.5.3.2 | 1,28 Mcps TDD option..... | 163 | +| 7.5.3.3 | 7,68 Mcps TDD option..... | 163 | +| 7.5.4 | Method of test..... | 163 | +| 7.5.4.1 | Initial conditions..... | 163 | +| 7.5.4.2 | Procedure..... | 164 | +| 7.5.4.2.1 | 3,84 Mcps TDD option..... | 164 | +| 7.5.4.2.2 | 1,28 Mcps TDD option..... | 164 | +| 7.5.4.2.3 | 7,68 Mcps TDD option..... | 165 | +| 7.5.5 | Test Requirements..... | 165 | + +| | | | +|-------------|---------------------------------------------------------|-----| +| 7.6 | Intermodulation characteristics..... | 165 | +| 7.6.1 | Definition and applicability..... | 165 | +| 7.6.2 | Minimum Requirements..... | 165 | +| 7.6.2.1 | 3,84 Mcps TDD option..... | 165 | +| 7.6.2.2 | 1,28 Mcps TDD option..... | 166 | +| 7.6.2.3 | 7,68 Mcps TDD option..... | 166 | +| 7.6.3 | Test purpose..... | 167 | +| 7.6.4 | Method of test..... | 167 | +| 7.6.4.1 | Initial conditions..... | 167 | +| 7.6.4.1.1 | 3,84 Mcps TDD option..... | 167 | +| 7.6.4.1.2 | 1,28 Mcps TDD option..... | 167 | +| 7.6.4.1.3 | 7,68 Mcps TDD option..... | 167 | +| 7.6.4.2 | Procedure..... | 168 | +| 7.6.4.2.1 | 3,84 Mcps TDD option..... | 168 | +| 7.6.4.2.2 | 1,28 Mcps TDD option..... | 168 | +| 7.6.4.2.3 | 7,68 Mcps TDD option..... | 168 | +| 7.6.5 | Test Requirements..... | 169 | +| 7.7 | Spurious emissions..... | 169 | +| 7.7.1 | Definition and applicability..... | 169 | +| 7.7.2 | Minimum Requirements..... | 169 | +| 7.7.2.1 | 3,84 Mcps TDD option..... | 169 | +| 7.7.2.2 | 1,28 Mcps TDD option..... | 170 | +| 7.7.2.3 | 7,68 Mcps TDD option..... | 170 | +| 7.7.3 | Test purpose..... | 171 | +| 7.7.4 | Method of test..... | 171 | +| 7.7.4.1 | Initial conditions..... | 171 | +| 7.7.4.1.0 | General test conditions..... | 171 | +| 7.7.4.1.1 | 3,84 Mcps TDD option..... | 171 | +| 7.7.4.1.2 | 1,28 Mcps TDD option..... | 171 | +| 7.7.4.1.3 | 7,68 Mcps TDD option..... | 172 | +| 7.7.4.2 | Procedure..... | 172 | +| 7.7.4.2.1 | 3,84 Mcps TDD option..... | 172 | +| 7.7.4.2.2 | 1,28 Mcps TDD option..... | 173 | +| 7.7.4.2.3 | 7,68 Mcps TDD option..... | 173 | +| 7.7.5 | Test Requirements..... | 174 | +| 8 | Performance requirements..... | 174 | +| 8.1 | General..... | 174 | +| 8.2 | Demodulation in static propagation conditions..... | 175 | +| 8.2.1 | Demodulation of DCH..... | 175 | +| 8.2.1.1 | Definition and applicability..... | 175 | +| 8.2.1.2 | Minimum Requirements..... | 175 | +| 8.2.1.2.1 | 3,84 Mcps TDD option..... | 175 | +| 8.2.1.2.2 | 1,28 Mcps TDD option..... | 176 | +| 8.2.1.2.3 | 7,68 Mcps TDD option..... | 176 | +| 8.2.1.3 | Test purpose..... | 177 | +| 8.2.1.4 | Method of test..... | 177 | +| 8.2.1.4.1 | Initial conditions..... | 177 | +| 8.2.1.4.1.0 | General test conditions..... | 177 | +| 8.2.1.4.1.1 | 3,84 Mcps TDD option..... | 177 | +| 8.2.1.4.1.2 | 1,28 Mcps TDD option..... | 177 | +| 8.2.1.4.1.3 | 7,68 Mcps TDD option..... | 178 | +| 8.2.1.4.2 | Procedure..... | 178 | +| 8.2.1.4.2.1 | 3,84 Mcps TDD option..... | 178 | +| 8.2.1.4.2.2 | 1,28 Mcps TDD option..... | 178 | +| 8.2.1.4.2.3 | 7,68 Mcps TDD option..... | 179 | +| 8.2.1.5 | Test Requirements..... | 179 | +| 8.2.1.5.1 | 3,84 Mcps TDD option..... | 180 | +| 8.2.1.5.2 | 1,28 Mcps TDD option..... | 180 | +| 8.2.1.5.3 | 7,68 Mcps TDD option..... | 180 | +| 8.3 | Demodulation of DCH in multipath fading conditions..... | 180 | +| 8.3.1 | Multipath fading Case 1..... | 180 | + +| | | | +|-------------|-----------------------------------|-----| +| 8.3.1.1 | Definition and applicability..... | 180 | +| 8.3.1.2 | Minimum Requirements..... | 180 | +| 8.3.1.2.1 | 3,84 Mcps TDD option..... | 180 | +| 8.3.1.2.2 | 1,28 Mcps TDD option..... | 181 | +| 8.3.1.2.3 | 7,68 Mcps TDD option..... | 181 | +| 8.3.1.3 | Test purpose..... | 182 | +| 8.3.1.4 | Method of test..... | 182 | +| 8.3.1.4.1 | Initial conditions..... | 182 | +| 8.3.1.4.1.0 | General test conditions..... | 182 | +| 8.3.1.4.1.1 | 3,84 Mcps TDD option..... | 182 | +| 8.3.1.4.1.2 | 1,28 Mcps TDD option..... | 183 | +| 8.3.1.4.1.3 | 7,68 Mcps TDD option..... | 183 | +| 8.3.1.4.2 | Procedure..... | 183 | +| 8.3.1.4.2.1 | 3,84 Mcps TDD option..... | 183 | +| 8.3.1.4.2.2 | 1,28 Mcps TDD option..... | 184 | +| 8.3.1.4.2.3 | 7,68 Mcps TDD option..... | 184 | +| 8.3.1.5 | Test Requirements..... | 185 | +| 8.3.1.5.1 | 3,84 Mcps TDD option..... | 185 | +| 8.3.1.5.2 | 1,28 Mcps TDD option..... | 185 | +| 8.3.1.5.3 | 7,68 Mcps TDD option..... | 185 | +| 8.3.2 | Multipath fading Case 2..... | 185 | +| 8.3.2.1 | Definition and applicability..... | 185 | +| 8.3.2.2 | Minimum Requirements..... | 185 | +| 8.3.2.2.1 | 3,84 Mcps TDD option..... | 185 | +| 8.3.2.2.2 | 1,28 Mcps option..... | 186 | +| 8.3.2.2.3 | 7,68 Mcps TDD option..... | 187 | +| 8.3.2.3 | Test purpose..... | 187 | +| 8.3.2.4 | Method of test..... | 187 | +| 8.3.2.4.1 | Initial conditions..... | 187 | +| 8.3.2.4.1.0 | General test conditions..... | 187 | +| 8.3.2.4.1.1 | 3,84 Mcps TDD option..... | 187 | +| 8.3.2.4.1.2 | 1,28 Mcps TDD option..... | 188 | +| 8.3.2.4.1.3 | 7,68 Mcps TDD option..... | 188 | +| 8.3.2.4.2 | Procedure..... | 188 | +| 8.3.2.4.2.1 | 3,84 Mcps TDD option..... | 188 | +| 8.3.2.4.2.2 | 1,28 Mcps TDD option..... | 189 | +| 8.3.2.4.2.3 | 7,68 Mcps TDD option..... | 189 | +| 8.3.2.5 | Test Requirements..... | 190 | +| 8.3.2.5.1 | 3,84 Mcps TDD option..... | 190 | +| 8.3.2.5.2 | 1,28 Mcps TDD option..... | 190 | +| 8.3.2.5.3 | 7,68 Mcps TDD option..... | 190 | +| 8.3.3 | Multipath fading Case 3..... | 190 | +| 8.3.3.1 | Definition and applicability..... | 190 | +| 8.3.3.2 | Minimum Requirements..... | 190 | +| 8.3.3.2.1 | 3,84 Mcps TDD option..... | 190 | +| 8.3.3.2.2 | 1,28 Mcps TDD option..... | 191 | +| 8.3.3.2.3 | 7,68 Mcps TDD option..... | 192 | +| 8.3.3.3 | Test purpose..... | 192 | +| 8.3.3.4 | Method of test..... | 193 | +| 8.3.3.4.1 | Initial conditions..... | 193 | +| 8.3.3.4.1.0 | General test conditions..... | 193 | +| 8.3.3.4.1.1 | 3,84 Mcps TDD option..... | 193 | +| 8.3.3.4.1.2 | 1,28 Mcps TDD option..... | 193 | +| 8.3.3.4.1.3 | 7,68 Mcps TDD option..... | 193 | +| 8.3.3.4.2 | Procedure..... | 193 | +| 8.3.3.4.2.1 | 3,84 Mcps TDD option..... | 193 | +| 8.3.3.4.2.2 | 1,28 Mcps TDD option..... | 194 | +| 8.3.3.4.2.3 | 7,68 Mcps TDD option..... | 195 | +| 8.3.3.5 | Test Requirements..... | 195 | +| 8.3.3.5.1 | 3,84 Mcps TDD option..... | 195 | +| 8.3.3.5.2 | 1,28 Mcps TDD option..... | 195 | + +| | | | +|--------------|---------------------------------------------------------------|-----| +| 8.3.3.5.3 | 7,68 Mcps TDD option..... | 196 | +| 8.3A | Demodulation of DCH in high speed train conditions..... | 196 | +| 8.3A.1 | Definition and applicability ..... | 196 | +| 8.3A.2 | Minimum requirement ..... | 196 | +| 8.3A.2.1 | 3.84 Mcps TDD option ..... | 196 | +| 8.3A.2.2 | 1.28 Mcps TDD option ..... | 196 | +| 8.3A.2.3 | 7.68 Mcps TDD option ..... | 197 | +| 8.3A.3 | Test purpose ..... | 197 | +| 8.3A.4 | Method of test ..... | 198 | +| 8.3A.4.1 | Initial conditions ..... | 198 | +| 8.3A.4.1.1 | General test conditions..... | 198 | +| 8.3A.4.1.1.1 | 3.84 Mcps TDD option..... | 198 | +| 8.3A.4.1.1.2 | 1.28 Mcps TDD option..... | 198 | +| 8.3A.4.1.1.3 | 7.68 Mcps TDD option..... | 198 | +| 8.3A.4.2 | Procedure ..... | 198 | +| 8.3A.4.2.1 | 3.84 Mcps TDD option..... | 198 | +| 8.3A.4.2.2 | 1.28 Mcps TDD option..... | 198 | +| 8.3A.4.2.3 | 7.68 Mcps TDD option..... | 199 | +| 8.3A.5 | Test requirements ..... | 199 | +| 8.3A.5.1 | 3,84 Mcps TDD option ..... | 199 | +| 8.3A.5.2 | 1,28 Mcps TDD option ..... | 199 | +| 8.3A.5.3 | 7,68 Mcps TDD option ..... | 200 | +| 8.4 | Demodulation of E-DCH FRC in multipath fading conditions..... | 200 | +| 8.4.1 | Definition and applicability..... | 200 | +| 8.4.2 | Minimum Requirements..... | 200 | +| 8.4.2.1 | 3,84 Mcps TDD Option..... | 200 | +| 8.4.2.2 | 1.28 Mcps TDD option..... | 201 | +| 8.4.2.3 | 7.68 Mcps TDD Option..... | 202 | +| 8.4.3 | Test purpose..... | 202 | +| 8.4.4 | Method of test..... | 202 | +| 8.4.4.1 | Initial conditions..... | 202 | +| 8.4.4.1.0 | General test conditions..... | 202 | +| 8.4.4.1.1 | 3,84 Mcps TDD option..... | 203 | +| 8.4.4.1.2 | 1.28 Mcps TDD option..... | 203 | +| 8.4.4.1.3 | 7.68 Mcps TDD option..... | 203 | +| 8.4.4.2 | Procedure..... | 203 | +| 8.4.4.2.1 | 3,84 Mcps TDD option..... | 203 | +| 8.4.4.2.2 | 1.28 Mcps TDD option..... | 204 | +| 8.4.4.2.3 | 7.68 Mcps TDD option..... | 204 | +| 8.4.5 | Test Requirements..... | 205 | +| 8.4.5.1 | 3,84 Mcps TDD option..... | 205 | +| 8.4.5.2 | 1.28 Mcps TDD option..... | 205 | +| 8.4.5.3 | 7.68 Mcps TDD option..... | 205 | +| 8.5 | Performance of ACK error detection for HS-SICH..... | 205 | +| 8.5.1 | ACK error detection in static propagation conditions..... | 205 | +| 8.5.1.1 | 3.84 Mcps TDD option..... | 205 | +| 8.5.1.2 | 1.28 Mcps TDD option..... | 205 | +| 8.5.1.2.1 | Definition and applicability..... | 205 | +| 8.5.1.2.2 | Minimum requirement..... | 205 | +| 8.5.1.2.3 | Test purpose..... | 207 | +| 8.5.1.2.4 | Method of test..... | 207 | +| 8.5.1.2.4.1 | Initial conditions..... | 207 | +| 8.5.1.2.4.2 | Procedure..... | 207 | +| 8.5.1.2.5 | Test requirements..... | 207 | +| 8.5.2 | ACK error detection in multipath fading conditions..... | 208 | +| 8.5.2.1 | 3,84 Mcps TDD option..... | 208 | +| 8.5.2.2 | 1,28 Mcps TDD option..... | 208 | +| 8.5.2.2.1 | Definition and applicability..... | 208 | +| 8.5.2.2.2 | Minimum requirement..... | 208 | +| 8.5.2.2.3 | Test purpose..... | 210 | +| 8.5.2.2.4 | Method of test..... | 210 | + +| | | | +|-------------|-------------------------|-----| +| 8.5.2.2.4.1 | Initial conditions..... | 210 | +| 8.5.2.2.4.2 | Procedure..... | 210 | +| 8.5.2.2.5 | Test requirements..... | 210 | + +**Annex A (normative): Measurement Channels..... 212** + +| | | | +|-----------|---------------------------------------------------|-----| +| A.1 | (void)..... | 212 | +| A.2 | Reference measurement channel..... | 212 | +| A.2.1 | UL reference measurement channel (12,2 kbps)..... | 212 | +| A.2.1.1 | 3,84 Mcps TDD option..... | 212 | +| A.2.1.2 | 1,28 Mcps option..... | 213 | +| A.2.1.3 | 7,68 Mcps TDD Option..... | 214 | +| A.2.2 | UL reference measurement channel (64 kbps)..... | 215 | +| A.2.2.1 | 3,84 Mcps TDD option..... | 215 | +| A.2.2.2 | 1,28 Mcps TDD option..... | 217 | +| A.2.2.3 | 7,68 Mcps TDD Option..... | 218 | +| A.2.3 | UL reference measurement channel (144 kbps)..... | 219 | +| A.2.3.1 | 3,84 Mcps TDD option..... | 219 | +| A.2.3.2 | 1,28 Mcps TDD option..... | 221 | +| A.2.3.3 | 7,68 Mcps TDD Option..... | 222 | +| A.2.4 | UL reference measurement channel (384 kbps)..... | 223 | +| A.2.4.1 | 3,84 Mcps TDD option..... | 223 | +| A.2.4.2 | 1,28 Mcps TDD option..... | 225 | +| A.2.4.3 | 7,68 Mcps TDD Option..... | 226 | +| A.2.5 | RACH reference measurement channel..... | 227 | +| A.2.5.1 | 3,84 Mcps TDD option..... | 227 | +| A.2.5.1.1 | RACH mapped to 1 code SF16..... | 227 | +| A.2.5.1.2 | RACH mapped to 1 code SF8..... | 228 | +| A.2.5.2 | 1,28 Mcps TDD option..... | 228 | +| A.2.5.2.1 | RACH mapped to 1 code SF16..... | 229 | +| A.2.5.2.2 | RACH mapped to 1 code SF8..... | 229 | +| A.2.5.2.3 | RACH mapped to 1 code SF4..... | 230 | +| A.2.5.3 | 7,68 Mcps TDD option..... | 230 | +| A.2.5.3.1 | RACH mapped to 1 code SF16..... | 231 | +| A.2.5.3.2 | RACH mapped to 1 code SF32..... | 231 | +| A.3 | E-DCH Reference measurement channels..... | 232 | +| A.3.1 | E-DCH Fixed Reference Channels..... | 232 | +| A.3.1.1 | 3,84 Mcps TDD Option..... | 232 | +| A.3.1.1.1 | Fixed Reference Channel 1 (FRC1)..... | 232 | +| A.3.1.1.2 | Fixed Reference Channel 2 (FRC2)..... | 233 | +| A.3.1.1.3 | Fixed Reference Channel 3 (FRC3)..... | 233 | +| A.3.1.2 | 1,28 Mcps TDD Option..... | 234 | +| A.3.1.2.1 | Fixed reference channel 1(FRC1)..... | 234 | +| A.3.1.2.2 | Fixed reference channel 2(FRC2)..... | 235 | +| A.3.1.2.3 | Fixed reference channel 3(FRC3)..... | 236 | +| A.3.1.2.4 | Fixed reference channel 4(FRC4)..... | 237 | +| A.3.1.3 | 7,68 Mcps TDD Option..... | 238 | +| A.3.1.3.1 | Fixed Reference Channel 1 (FRC1)..... | 238 | +| A.3.1.3.2 | Fixed Reference Channel 2 (FRC2)..... | 239 | +| A.3.1.3.3 | Fixed Reference Channel 3 (FRC3)..... | 240 | +| A.4 | HS-SICH Reference measurement channels..... | 241 | +| A.4.1 | 3,84 Mcps TDD Option..... | 241 | +| A.4.2 | 1,28 Mcps TDD Option..... | 241 | + +**Annex B (normative): Propagation conditions..... 243** + +| | | | +|-------|-----------------------------------------------|-----| +| B.1 | Static propagation condition..... | 243 | +| B.2 | Multi-path fading propagation conditions..... | 243 | +| B.2.1 | 3,84 Mcps TDD option..... | 243 | +| B.2.2 | 1,28 Mcps TDD option..... | 243 | + +| | | | +|-------------------------------|------------------------------------------------------------------|------------| +| B.2.3 | 7,68 Mcps TDD option..... | 244 | +| B.3 | High speed train conditions..... | 245 | +| Annex C (normative): | Global in-channel Tx test..... | 247 | +| C.1 | General..... | 247 | +| C.2 | Definition of the process..... | 247 | +| C.2.1 | Basic principle..... | 247 | +| C.2.2 | Output signal of the Tx under test..... | 247 | +| C.2.3 | Reference signal..... | 247 | +| C.2.4 | Classification of measurement results..... | 248 | +| C.2.5 | Process definition to achieve results of type "deviation"..... | 248 | +| C.2.5.1 | Decision Point Power..... | 249 | +| C.2.5.2 | Code-Domain Power..... | 249 | +| C.2.6 | Process definition to achieve results of type "residual"..... | 249 | +| C.2.6.1 | Error Vector Magnitude (EVM)..... | 250 | +| C.2.6.2 | Peak Code Domain Error (PCDE)..... | 250 | +| C.2.6.3 | Relative Code Domain Error (RCDE)..... | 250 | +| C.3 | Notes..... | 251 | +| C.3.1 | Symbol length..... | 251 | +| C.3.2 | Deviation..... | 251 | +| C.3.3 | Residual..... | 251 | +| C.3.4 | TDD..... | 251 | +| C.3.5 | Synch channel..... | 251 | +| C.3.6 | Formula for the minimum process..... | 252 | +| C.3.7 | Formula for EVM..... | 253 | +| Annex D (informative): | Derivation of Test Requirements..... | 253 | +| Annex E (informative): | Acceptable uncertainty of Test Equipment..... | 260 | +| Annex F (normative): | General rules for statistical testing..... | 262 | +| F.1 | Statistical testing of receiver BER/BLER performance..... | 262 | +| F.1.1 | Error Definition..... | 262 | +| F.1.2 | Test Method..... | 262 | +| F.1.3 | Test Criteria..... | 262 | +| F.1.4 | Calculation assumptions..... | 262 | +| F.1.4.1 | Statistical independence..... | 262 | +| F.1.4.2 | Applied formulas..... | 262 | +| F.1.4.3 | Approximation of the distribution..... | 263 | +| F.1.5 | Definition of good pass fail decision..... | 263 | +| F.1.6 | Good balance between test time and statistical significance..... | 264 | +| F.1.7 | Pass fail decision rules..... | 265 | +| F.1.8 | Test conditions for BER, BLER Tests..... | 266 | +| F.1.9 | Practical Use (informative)..... | 267 | +| Annex G (informative): | Change History..... | 270 | + +--- + +## Foreword + +This Technical Specification has been produced by the 3GPP. + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 Indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the specification. + +--- + +# 1 Scope + +The present document specifies the Radio Frequency (RF) test methods and conformance requirements for UTRA Base Stations (BS) operating in the TDD mode. These have been derived from, and are consistent with, the UTRA base station (BS) specifications defined in 3GPP TS 25.105 [1]. The document covers all three options of the TDD mode, which are the 3,84 Mcps (incorporating MBSFN IMB), the 1,28 Mcps and the 7,68 Mcps options respectively. The requirements are listed in different subsections only if the parameters deviate. + +In this TS, the reference point for RF connections (except for the measurement of mean transmitted RF carrier power) is the antenna connector, as defined by the manufacturer. This TS does not apply to repeaters or RF devices which may be connected to an antenna connector of a BS. + +--- + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. +- [1] 3GPP TS 25.105: "UTRA (BS) TDD: Radio transmission and reception". +- [2] IEC 60721-3-3 (1994): "Classification of environmental conditions - Part 3: Classification of groups of environmental parameters and their severities - Section 3: Stationary use at weather protected locations". +- [3] IEC 60721-3-4 (1995): "Classification of environmental conditions - Part 3: Classification of groups of environmental parameters and their severities - Section 4: Stationary use at non-weather protected locations". +- [4] IEC 60068-2-1 (1990): "Environmental testing - Part 2: Tests. Tests A: Cold". +- [5] ETR 028: "Uncertainties in the measurement of mobile radio equipment characteristics". +- [6] Recommendation ITU-R SM.329: "Unwanted emissions in the spurious domain". +- [7] Recommendation ITU-R SM.328: "Spectra and bandwidth of emissions". +- [8] IEC 60068-2-6 (1995): "Environmental testing - Part 2: Tests - Test Fc: Vibration (sinusoidal)". +- [9] 3GPP TR 25.942: "RF System Scenarios". +- [10] ITU-T recommendation O.153: "Basic parameters for the measurement of error performance at bit rates below the primary rate". +- [11] 3GPP TS 36.104: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception". +- [12] 3GPP TS 37.141: "E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) conformance testing". +- [13] ITU-R Recommendation M.1545, "Measurement uncertainty as it applies to test limits for the terrestrial component of International Mobile Telecommunications-2000". + +## 3 Definitions, symbols, and abbreviations + +### 3.1 Definitions + +**Ancillary RF amplifier:** a piece of equipment, which when connected by RF coaxial cables to the BS, has the primary function to provide amplification between the transmit and/or receive antenna connector of a BS and an antenna without requiring any control signal to fulfil its amplifying function. + +**BS RF bandwidth:** The bandwidth in which a Base Station simultaneously transmits and/or simultaneously receives multiple carriers within each supported operating band. + +**BS RF bandwidth edge:** The frequency of one of the edges of the Base Station RF bandwidth + +**Bit Error Ratio:** The Bit Error Ratio is defined as the ratio of the bits wrongly received to all data bits sent. The bits are the data bits above the convolutional/turbo decoder. The BER is the overall BER independent of frame erasures or when erased frames are not defined. + +**Block Error Ratio:** A Block Error Ratio is defined as the ratio of the number of erroneous blocks received to the total number of blocks sent. An erroneous block is a Transport Block whose cyclic redundancy check (CRC) is wrong. + +**Power Spectral Density:** The units of Power Spectral Density (PSD) are extensively used in this document. PSD is a function of power versus frequency and when integrated across a given bandwidth, the function represents the mean power in such a bandwidth. When the mean power is normalised to (divided by) the chip-rate it represents the mean energy per chip. Some signals are directly defined in terms of energy per chip, (DPCH\_Ec, Ec, and P-CCPCH\_Ec) and others defined in terms of PSD (Io, Ioc, Ior and $\hat{I}_{or}$ ). There also exist quantities that are a ratio of energy per chip to PSD (DPCH\_Ec/Ior, Ec/Ior etc.). This is the common practice of relating energy magnitudes in communication systems. + +It can be seen that if both energy magnitudes in the ratio are divided by time, the ratio is converted from an energy ratio to a power ratio, which is more useful from a measurement point of view. It follows that an energy per chip of X dBm/3,84 MHz can be expressed as a mean power per chip of X dBm. Similarly, a signal PSD of Y dBm/3,84 MHz can be expressed as a signal power of Y dBm. + +**Mean power:** When applied to a CDMA modulated signal this is the power (transmitted or received) in a bandwidth of at least $(1 + \alpha)$ times the chip rate of the radio access mode. The period of measurement shall be a transmit timeslot excluding the guard period unless otherwise stated. + +NOTE: The roll-off factor $\alpha$ is defined in section 6.8.1. + +**RRC filtered mean power:** The mean power as measured through a root raised cosine filter with roll-off factor $\alpha$ and a bandwidth equal to the chip rate of the radio access mode. + +NOTE: The RRC filtered mean power of a perfectly modulated CDMA signal is 0.246 dB lower than the mean power of the same signal. + +**Code domain power:** That part of the mean power which correlates with a particular (OVSF) code channel. The sum of all powers in the code domain equals the mean power in a bandwidth of $(1 + \alpha)$ times the chip rate of the radio access mode. + +**Highest Carrier:** The carrier with the highest carrier centre frequency transmitted/received in a specified operating band. + +**Inter RF bandwidth gap:** The frequency gap between two consecutive RF bandwidths that are placed within two supported operating bands respectively. + +**Multi-band Base Station:** Base Station characterized by the ability of its transmitter and/or receiver to process two or more carriers in common active RF components simultaneously, where at least one carrier is configured at a different non-overlapping operating band than the other carrier(s). + +**Multi-band transmitter:** Transmitter characterized by the ability to process two or more carriers in common active RF components simultaneously, where at least one carrier is configured at a different non-overlapping operating band than the other carrier(s). + +**Multi-band receiver:** Receiver characterized by the ability to process two or more carriers in common active RF components simultaneously, where at least one carrier is configured at a different non-overlapping operating band than the other carrier(s). + +**Maximum radio bandwidth:** Maximum frequency difference between the upper edge of the highest used carrier and the lower edge of the lowest used carrier. + +**Maximum BS RF bandwidth:** The maximum RF bandwidth supported by a BS within each supported operating band. + +**Output power, Pout:** The mean power of one carrier of the base station, delivered to a load with resistance equal to the nominal load impedance of the transmitter. + +**Lower RF bandwidth edge:** The frequency of the lower of the Base station RF bandwidth, used as a frequency reference point for transmitter and receiver requirements. + +**Lowest Carrier:** The carrier with the lowest carrier centre frequency transmitted/received in a specified operating band. + +**Maximum output power, Pmax:** The mean power level per carrier of the base station measured at the antenna connector in a specified reference condition. The period of measurement shall be a transmit timeslot excluding the guard period. + +**MBSFN-only operation:** Operation of a dedicated carrier solely for the purposes of MBSFN transmission. No receive functionality is implemented on the specified carrier frequency. + +**Rated output power, PRAT:** Rated output power of the base station is the mean power level per carrier that the manufacturer has declared to be available at the antenna connector. + +**Rated total output power:** Rated total output power of the base station is the mean power level that the manufacturer has declared to be available at the antenna connector. + +**Synchronized operation:** Operation of TDD in two different systems, where no simultaneous uplink and downlink occur. + +**Total power dynamic range:** The difference between the maximum and the minimum output power of the base station for a specified reference condition. + +**Total RF bandwidth:** Maximum sum of RF bandwidths in all supported operating bands. + +**Upper RF bandwidth edge:** The frequency of the upper edge of the Base Station RF Bandwidth; used as a frequency reference point for transmitter and receiver requirements. + +**Unsynchronized operation:** Operation of TDD in two different systems, where the conditions for synchronized operation are not met. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----------|-----------------| +| $\alpha$ | Roll-off factor | +|----------|-----------------| + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-------|----------------------------------------------------------------------------------------------------------------------| +| 3GPP | 3rd Generation Partnership Project | +| 16QAM | 16 - Quadrature Amplitude Modulation | +| AWGN | Additive White Gaussian Noise | +| BER | Bit Error Ratio | +| BLER | Block Error Ratio | +| dB | decibel | +| dBm | decibel relative to 1 milliWatt | +| DPCH | Mechanism used to simulate an individual intracell interferer in the cell with one code and a spreading factor of 16 | + +| | | +|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $\frac{DPCH_{o\_} E_c}{I_{or}}$ | Ratio of the average transmit energy per PN chip for the $DPCH_o$ to the total transmit power spectral density of all users in the cell in one timeslot as measured at the BS antenna connector | +| EVM | Error Vector Magnitude | +| F | Frequency (of the assigned channel frequency of the wanted signal) | +| Fuw | Frequency offset of the unwanted interfering signal from the assigned channel frequency of the wanted signal | +| HSDPA | High Speed Downlink Packet Access | +| HSUPA | High Speed Uplink Packet Access | +| HS-DSCH | High Speed Downlink Shared Channel | +| HS-PDSCH | High Speed Physical Downlink Shared Channel | +| IMB | Integrated Mobile Broadcast | +| IMT-2000 | International Mobile Telecommunications 2000 | +| Ioc | Power spectral density (integrated in a noise bandwidth equal to the chip rate and normalized to the chip rate) of a band limited white noise source (simulating interference from other cells) as measured at the BS antenna connector. | +| $\hat{I}_{or}$ | Received power spectral density (integrated in a bandwidth $(1+a)$ times the chip rate and normalized to the chip rate) of all users in the cell in one timeslot as measured at the BS antenna connector | +| IPR | Intellectual Property Rights | +| MBMS | Multimedia Broadcast Multicast Service | +| MBSFN | MBMS over a Single Frequency Network | +| MC | Multi-carrier | +| MC-HSDPA | Multi-carrier HSDPA | +| MC-HSUPA | Multi-carrier HSUPA | +| P | Output power | +| Pout | Output power of the base station | +| Pmax | Maximum output power of the base station | +| QPSK | Quadrature Phase Shift Keying | +| RAT | Radio Access Technology | +| RBER | Residual BER | +| RCDE | Relative Code Domain Error | +| REFSENS | Reference Sensitivity Level | +| RMS | Root-Mean Square | +| PRAT | Rated output power of the base station | +| RRC | Root-Raised Cosine | +| SC | Single Carrier | +| $T_c$ | Chip duration | +| TC | Test Configuration | +| TDM | Time Division Multiplexing | +| TS | Time Slot | +| UTTC | UTRA TDD Test Configuration | + +![Figure 3.3-1: Illustration of maximum radio bandwidth and Total RF bandwidth for Multi-band Base Station. The diagram shows two frequency bands, Band X and Band Y, each with a downlink (DL) frequency range. Band X consists of three segments: a red segment, a cyan segment, and a green segment. Band Y also consists of three segments: a red segment, a cyan segment, and a green segment. The total RF bandwidth is the sum of the bandwidths of Band X and Band Y. The maximum radio bandwidth is the total RF bandwidth plus the inter RF bandwidth gap. The BW_RF edge is indicated by a vertical line between the cyan and green segments of each band.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +The diagram illustrates the frequency spectrum for a multi-band base station. It shows two distinct frequency bands, Band X and Band Y, each with a downlink (DL) frequency range. Band X is composed of three segments: a red segment, a cyan segment, and a green segment. Band Y is similarly composed of a red segment, a cyan segment, and a green segment. The total RF bandwidth is the sum of the bandwidths of Band X and Band Y. The maximum radio bandwidth is the total RF bandwidth plus the inter RF bandwidth gap. The BWRF edge is indicated by a vertical line between the cyan and green segments of each band. + +Figure 3.3-1: Illustration of maximum radio bandwidth and Total RF bandwidth for Multi-band Base Station. The diagram shows two frequency bands, Band X and Band Y, each with a downlink (DL) frequency range. Band X consists of three segments: a red segment, a cyan segment, and a green segment. Band Y also consists of three segments: a red segment, a cyan segment, and a green segment. The total RF bandwidth is the sum of the bandwidths of Band X and Band Y. The maximum radio bandwidth is the total RF bandwidth plus the inter RF bandwidth gap. The BW\_RF edge is indicated by a vertical line between the cyan and green segments of each band. + +**Figure 3.3-1 Illustration of maximum radio bandwidth and Total RF bandwidth for Multi-band Base Station** + +## 4 Frequency bands and channel arrangement + +### 4.1 General + +The information presented in this section is based on a chip rate of 3,84 Mcps, 1,28 Mcps respectively and 7.68 Mcps . + +NOTE: Other chip rates may be considered in future releases. + +### 4.2 Frequency bands + +UTRA/TDD is designed to operate in the following bands: + +- a) 1900 - 1920 MHz: Uplink and downlink transmission +2010 - 2025 MHz Uplink and downlink transmission +- b) 1850 - 1910 MHz: Uplink and downlink transmission +1930 - 1990 MHz: Uplink and downlink transmission +- c) 1910 - 1930 MHz: Uplink and downlink transmission +- d) 2570 - 2620 MHz Uplink and downlink transmission +- e) 2300 - 2400 MHz Uplink and downlink transmission +- f) 1880 - 1920 MHz: Uplink and downlink transmission + +Note 1: Deployment in existing and other frequency bands is not precluded. + +Note 2: In China, Band a only includes 2010 - 2025 MHz for 1.28 Mcps TDD option. + +### 4.3 TX-RX frequency separation + +#### 4.3.1 3,84 Mcps TDD option + +No TX-RX frequency separation is required as Time Division Duplex (TDD) is employed. Each TDMA frame consists of 15 timeslots where each timeslot can be allocated to either transmit or receive. + +### 4.3.2 1,28 Mcps TDD option + +No TX-RX frequency separation is required as Time Division Duplex (TDD) is employed. Each subframe consists of 7 main timeslots where all main timeslots (at least the first one) before the single switching point are allocated UL and all main timeslots (at least the last one) after the single switching point are allocated DL. + +### 4.3.3 7,68 Mcps TDD option + +No TX-RX frequency separation is required as Time Division Duplex (TDD) is employed. Each TDMA frame consists of 15 timeslots where each timeslot can be allocated to either transmit or receive. + +## 4.4 Channel arrangement + +### 4.4.1 Channel spacing + +#### 4.4.1.1 3,84 Mcps TDD option + +The nominal channel spacing is 5 MHz, but this can be adjusted to optimise performance in a particular deployment scenario. + +#### 4.4.1.2 1,28 Mcps TDD option + +The nominal channel spacing is 1,6 MHz, but this can be adjusted to optimise performance in a particular deployment scenario. + +#### 4.4.1.3 7,68 Mcps TDD option + +The nominal channel spacing is 10 MHz, but this can be adjusted to optimise performance in a particular deployment scenario. + +### 4.4.2 Channel raster + +The channel raster is 200 kHz for all bands, which means that the carrier frequency must be a multiple of 200 kHz. + +#### 4.4.2.1 3,84 Mcps TDD Option + +In addition a number of additional centre frequencies are specified according to table 5.1, which means that the centre frequencies for these channels are shifted 100 kHz relative to the general raster. + +### 4.4.3 Channel number + +The carrier frequency is designated by the UTRA absolute radio frequency channel number (UARFCN). The value of the UARFCN in the IMT2000 band is defined in the general case as follows: + +$$N_t = 5 * F \text{ MHz} \qquad 0,0 \leq F \leq 3276,6 \text{ MHz}$$ + +where F is the carrier frequency in MHz. + +Additional channels applicable to operation in the frequency band defined in sub-clause 5.2(d) for 3,84 Mcps are defined via the following UARFCN definition: + +$$N_t = 5 * (F - 2150.1 \text{ MHz}) \qquad 2572.5 \text{ MHz} \leq F \leq 2617.5 \text{ MHz}$$ + +The 10 additional UARFCN for operations in frequency band defined in sub-clause 5.2(d) for 3,84 Mcps are hence: 2112, 2137, 2162, 2187, 2212, 2237, 2262, 2287, 2312, 2337. + +## 5 General test conditions and declarations + +Many of the tests in this TS measure a parameter relative to a value that is not fully specified in the UTRA specifications. For these tests, the Minimum Requirement is determined relative to a nominal value specified by the manufacturer. + +Certain functions of a BS are optional in the UTRA specifications. Some requirements for the BS may be regional as listed in subclause 5.17. + +When specified in a test, the manufacturer shall declare the nominal value of a parameter, or whether an option is supported. + +## 5.1 Base station classes + +### 5.1.1 Applicability of requirements and BS class definition + +The requirements in this specification apply to Wide Area base stations, Local Area base stations and Home Base Stations in co-ordinated network operation, unless otherwise stated. + +Wide Area BS are characterised by requirements derived from Macro Cell and Micro Cell scenarios with BS to UE coupling losses equal to 70 dB and 53 dB. The Wide Area Base Station has the same requirements as the base station for General Purpose application in Release 99 for 3,84 Mcps option, and in release 4 for both 3,84 Mcps and 1,28 Mcps option. + +Local Area BS are characterised by requirements derived from Pico Cell scenarios with a BS to UE coupling loss equals to 45 dB. + +Home Base Stations are characterised by requirements derived from Femto Cell scenarios. + +### 5.1.2 Manufacturer's declaration of supported RF configurations + +The manufacturer shall declare which operational configurations the BS supports by declaring the following parameters: + +- The intended class of the BS under test according to clause 5.1.1 +- The supported operating bands defined in clause 4.2; +- The frequency range within the above operating band(s) supported by the BS; +- The maximum Base Station RF bandwidth supported by a BS within each operating band; +- The supported operating configurations (multi-carrier and/or single carrier) within each operating band; +- The rated output power per carrier, PRAT; +- The rated total output power as a sum of all carriers; +- Maximum number of supported carriers within each band; +- Total number of supported carriers + +If the rated total output power and total number of supported carriers are not simultaneously supported, the manufacturer shall declare the following additional parameters: + +- The reduced number of supported carriers at the rated total output power; +- The reduced total output power at the maximum number of supported carriers. + +For BS capable of multi-band operation, the parameters above shall be declared for each supported operating band in single-band operation. In addition the manufacturer shall declare the following additional parameters for BS capable of multi-band operation: + +- Supported operating band combinations of the BS +- Supported operating band(s) of each antenna connector +- Support of multi-band transmitter and/or multi-band receiver, including mapping to antenna connector(s) +- Total number of supported carriers for the declared band combinations of the BS +- Maximum number of supported carriers per band in multi-band operation + +- Total RF bandwidth of transmitter and receiver for the declared band combinations of the BS +- Maximum RF bandwidth of each supported operating band in multi-band operation +- Maximum radio bandwidth in transmit and receive direction for the declared band combinations of the BS +- Any other limitations under simultaneous operation in the declared band combinations of the BS which have any impact on the test configuration generation +- Total output power as a sum over all supported operating bands in the declared band combinations of the BS +- Maximum supported power difference between any two carriers in any two different supported operating bands +- The rated output power per carrier in multi-band operation +- Rated total output power of each supported operating band in multi-band operation. + +## 5.2 Output power + +Void + +## 5.3 Specified frequency range and supported channel bandwidth + +The manufacturer shall declare: + +- which of the frequency bands defined in sub-clause 4.2 are supported by the BS. +- the frequency range within the above frequency band(s) supported by the BS. As TDD is employed, the same frequency range is used for transmit and receive operation. For the case of MBSFN-only operation, the frequency range is used for transmit only, since no receive requirement exists. + +For the single carrier testing, many tests in this TS are performed with appropriate frequencies in the bottom, middle and top of the operating frequency band of the BS. These are denoted as RF channels B (bottom), M (middle) and T (top). + +Unless otherwise stated, the test shall be performed with a single carrier at each of the RF channels B, M and T. + +When a test is performed by a test laboratory, the UARFCNs to be used for RF channels B, M and T shall be specified by the laboratory. The laboratory may consult with operators, the manufacturer or other bodies. + +When a test is performed by a manufacturer, the UARFCNs to be used for RF channels B, M and T may be specified by an operator. + +### 5.3.1 RF bandwidth position for multi-carrier testing + +Many tests in this TS are performed with the maximum RF bandwidth located at the bottom, middle and top of the supported frequency range in each operating band. These are denoted as $B_{\text{RFBW}}$ (bottom), $M_{\text{RFBW}}$ (middle) and $T_{\text{RFBW}}$ (top). + +Unless otherwise stated, the test shall be performed at $B_{\text{RFBW}}$ , $M_{\text{RFBW}}$ and $T_{\text{RFBW}}$ defined as following: + +- $B_{\text{RFBW}}$ : maximum RF bandwidth located at the bottom of the supported frequency range in each operating band; +- $M_{\text{RFBW}}$ : maximum RF bandwidth located in the middle of the supported frequency range in each operating band; +- $T_{\text{RFBW}}$ : maximum RF bandwidth located at the top of the supported frequency range in each operating band. + +For BS capable of dual-band operation, unless otherwise stated, the test shall be performed at $B_{\text{RFBW\_T'RFBW}}$ and $B'_{\text{RFBW\_T'RFBW}}$ defined as following: + +- $B_{\text{RFBW\_T'RFBW}}$ : the RF bandwidths located at the bottom of the supported frequency range in the lower operating band and at the highest possible simultaneous frequency position, within the maximum radio bandwidth, in the upper operating band. + +$B'_{\text{RFBW\_TRFBW}}$ : the RF bandwidths located at the top of the supported frequency range in the upper operating band and at the lowest possible simultaneous frequency position, within the maximum radio bandwidth, in the lower operating band. + +NOTE: $B_{\text{RFBW\_T'RFBW}} = B'_{\text{RFBW\_TRFBW}} = B_{\text{RFBW\_TRFBW}}$ when the declared maximum radio bandwidth spans both operating bands. $B_{\text{RFBW\_TRFBW}}$ means the RF bandwidths are located at the bottom of the supported frequency range in the lower operating band and at the top of the supported frequency range in the upper operating band. + +When a test is performed by a test laboratory, the position of $B_{\text{RFBW}}$ , $M_{\text{RFBW}}$ and $T_{\text{RFBW}}$ in each supported operating band, as well as the position of $B_{\text{RFBW\_T'RFBW}}$ and $B'_{\text{RFBW\_TRFBW}}$ in the supported operating band combinations, shall be specified by the laboratory. The laboratory may consult with operators, the manufacturer or other bodies. + +## 5.4 Relationship between RF generation and chip clock + +The manufacturer shall declare compliance with the requirement that the BS shall use the same frequency source for both RF generation and the chip clock. + +## 5.5 Spectrum emission mask + +The manufacturer shall declare whether the BS under test is intended to operate in regions where conformance to the spectrum emission mask defined in subclause 6.6.2.1.2 is mandatory. If so, the conformance test for spectrum emission mask specified in subclause 6.6.2.1 shall be performed; otherwise, this test is not required. + +## 5.6 Adjacent Channel Leakage power Ratio (ACLR) + +The manufacturer shall declare: + +- whether the BS under test is intended to operate in proximity to either another TDD BS or FDD BS that comprises uplink receive functionality operating on the first or second adjacent frequency. If so, conformance with the ACLR requirement specified in subclause 6.6.2.2.2 is mandatory; otherwise, this requirement need not to be tested. +- whether the BS under test is intended to operate co-sited to either another TDD BS or FDD BS that comprises uplink receive functionality operating on the first or second adjacent frequency. If so, conformance with the ACLR requirement specified in subclause 6.6.2.2.3 is mandatory; otherwise, this requirement need not to be tested. + +## 5.7 Tx spurious emissions + +### 5.7.1 Category of spurious emissions limit + +The manufacturer shall declare one of the following: + +- a) the BS shall be tested against Category A limits for spurious emissions, as defined in ITU-R Recommendation SM.329-9 [6]. + +or + +- b) the BS shall be tested against Category B limits for spurious emissions, as defined in ITU-R Recommendation SM.329-9 [6]. + +If the manufacturer declares Category A limits to be applicable, conformance with the spurious emissions requirements specified in subclause 6.6.3.2.1.1 is mandatory, and the requirements specified in subclause 6.6.3.2.1.2 need not to be tested. + +If the manufacturer declares Category B limits to be applicable, conformance with the spurious emissions requirements specified in subclause 6.6.3.2.1.2 is mandatory, and the requirements specified in subclause 6.6.3.2.1.1 need not to be tested. + +### 5.7.2 Co-existence with GSM + +The manufacturer shall declare: + +- whether the BS under test is intended to operate in geographic areas in which also GSM 900 is deployed. If so, compliance with the conformance requirement specified in subclause 6.6.3.2.2.1 is mandatory; otherwise, this requirement needs not to be tested. +- whether the BS under test is intended to operate co-located with a GSM 900 BTS. If so, compliance with the conformance requirement specified in subclause 6.6.3.2.2.2 is mandatory; otherwise, this requirement needs not to be tested. + +### 5.7.3 Co-existence with DCS 1800 + +The manufacturer shall declare: + +- whether the BS under test is intended to operate in geographic areas in which also DCS 1800 is deployed. If so, compliance with the conformance requirement specified in subclause 6.6.3.2.3.1 is mandatory; otherwise, this requirement needs not to be tested. +- whether the BS under test is intended to operate co-located with a DCS 1800 BTS. If so, compliance with the conformance requirement specified in subclause 6.6.3.2.3.2 is mandatory; otherwise, this requirement needs not to be tested. + +### 5.7.4 Co-existence with UTRA FDD + +The manufacturer shall declare: + +- whether the BS under test is intended to operate in geographic areas in which also UTRA FDD is deployed. If so, compliance with the conformance requirement specified in subclause 6.6.3.2.4.1 is mandatory; otherwise, this requirement needs not to be tested. +- whether the BS under test is intended to operate co-located with a UTRA FDD BS. If so, compliance with the conformance requirement specified in subclause 6.6.3.2.4.2 is mandatory; otherwise, this requirement needs not to be tested. + +### 5.7.5 Co-existence with unsynchronised UTRA TDD and/or E-UTRA TDD + +The manufacturer shall declare: + +- whether the BS under test is intended to operate in geographic areas in which also unsynchronised UTRA TDD and/or E-UTRA TDD that comprises uplink receive functionality is deployed. If so, compliance with the conformance requirement specified in subclause 6.6.3.2.5.1 is mandatory; otherwise, this requirement need not to be tested. +- whether the BS under test is intended to operate co-located with a unsynchronised UTRA TDD and/or E-UTRA TDD BS that comprises uplink receive functionality. If so, compliance with the conformance requirement specified in subclause 6.6.3.2.5.2 is mandatory; otherwise, this requirement needs not to be tested. + +## 5.8 Blocking characteristics + +The conformance requirements with respect to the parameter blocking characteristics are dependent on the operating frequency bands of the BS under test; see subclause 7.5.2. However, the need for a manufacturer's declaration of the frequency bands supported by the BS is already covered by subclause 5.3. The relationship between the frequency bands supported by the BS and the mandatory blocking requirements is given in table 5.1. + +**Table 5.1: Relationship between the frequency bands supported by the BS and the mandatory blocking requirements** + +| Supported frequency band according to manufacturer's declaration | Mandatory blocking requirement | +|------------------------------------------------------------------|--------------------------------| +| subclause 4.2a) | table 7.6 | +| subclause 4.2b) | table 7.7 | +| subclause 4.2c) | table 7.8 | + +In addition, the manufacturer shall declare: + +- whether the BS under test is intended to operate co-located with a GSM 900 BTS or a DCS 1800 BTS. If so, compliance with the conformance requirement specified in table 7.9 or 7.10, respectively, is mandatory; otherwise, this requirement needs not to be tested. + +## 5.9 Test environments + +For each test in this TS, the environmental conditions under which the BS is to be tested are defined. + +### 5.9.1 Normal test environment + +When a normal test environment is specified for a test, the test should be performed under any combination of conditions between the minimum and maximum limits stated in table 5.2. + +**Table 5.2: Limits of conditions for Normal Test Environment** + +| Condition | Minimum | Maximum | +|---------------------|------------------------------------------|---------| +| Barometric pressure | 86 kPa | 106 kPa | +| Temperature | 15°C | 30°C | +| Relative Humidity | 20 % | 85 % | +| Power supply | Nominal, as declared by the manufacturer | | +| Vibration | Negligible | | + +The ranges of barometric pressure, temperature and humidity represent the maximum variation expected in the uncontrolled environment of a test laboratory. If it is not possible to maintain these parameters within the specified limits, the actual values shall be recorded in the test report. + +NOTE: This may, for instance, be the case for measurements of radiated emissions performed on an open field test site. + +### 5.9.2 Extreme test environment + +The manufacturer shall declare one of the following: + +- a) The equipment class for the equipment under test, as defined in IEC 60721-3-3 [2]. +- b) The equipment class for the equipment under test, as defined in IEC 60721-3-4 [3]. +- c) For equipment that does not comply to the mentioned classes, the relevant classes from IEC 60 721 documentation for Temperature, Humidity and Vibration shall be declared. + +NOTE: Reduced functionality for conditions that fall out side of the standard operational conditions are not tested in this TS. These may be stated and tested separately. + +#### 5.9.2.1 Extreme temperature + +When an extreme temperature test environment is specified for a test, the test shall be performed at the standard minimum and maximum operating temperatures defined by the manufacturer's declaration for the equipment under test. + +##### Minimum temperature: + +- The test shall be performed with the environmental test equipment and methods of inducing the required environmental phenomena into the equipment, conforming to the test procedure of IEC 60 068-2-1 [4], Environmental Testing, Part 2: Tests - Tests A: Cold. The equipment shall be maintained at the stabilized condition for the duration of the test sequence. + +##### Maximum temperature: + +- The test shall be performed with the environmental test equipment and methods of inducing the required environmental phenomena in to the equipment, conforming to the test procedure of IEC 60 068-2-2 [5] (Environmental Testing, Part 2: Tests - Tests Bd Dry heat). The equipment shall be maintained at the stabilized condition for the duration of the test sequence. + +NOTE: It is recommended that the equipment is made fully operational prior to the equipment being taken to its lower operating temperature. + +### 5.9.3 Vibration + +When vibration conditions are specified for a test, the test shall be performed while the equipment is subjected to a vibration sequence as defined by the manufacturers declaration for the equipment under test. This shall use the environmental test equipment and methods of inducing the required environmental phenomena in to the equipment, conforming to the test procedure of IEC 60 068-2-6 [8], Environmental Testing, Part 2: Tests - Test Fc and guidance: Vibration (Sinusoidal). Other environmental conditions shall be within the ranges specified in subclause 5.9.1, Normal test environment. + +NOTE: The higher levels of vibration may induce undue physical stress in to equipment after a prolonged series of tests. The testing body should only vibrate the equipment during the RF measurement process. + +### 5.9.4 Power supply + +When extreme power supply conditions are specified for a test, the test shall be performed at the standard upper and lower limits of operating voltage defined by the manufacturer's declaration for the equipment under test. + +#### Upper voltage limit + +- The equipment shall be supplied with a voltage equal to the upper limit declared by the manufacturer (as measured at the input terminals to the equipment). The tests shall be carried out at a steady state minimum and maximum limit declared by the manufacturer for the equipment, to the methods described in IEC 60 068-2-1 [4] Test Ab/Ad: Cold and IEC 60 068-2-2 [5] Test Bb/Bd: Dry Heat. + +#### Lower voltage limit + +- The equipment shall be supplied with a voltage equal to the lower limit declared by the manufacturer (as measured at the input terminals to the equipment). The tests shall be carried out at a steady state minimum and maximum limit declared by the manufacturer for the equipment, to the methods described in IEC 60 068-2-1 [4] Test Ab/Ad: Cold and IEC 60 068-2-2 [5] Test Bb/Bd: Dry Heat. + +## 5.10 Acceptable uncertainty of Test System + +The maximum acceptable uncertainty of the Test System is specified below for each test, where appropriate. The Test System shall enable the stimulus signals in the test case to be adjusted to within the specified tolerance and the equipment under test to be measured with an uncertainty not exceeding the specified values. All tolerances and uncertainties are absolute values and are valid for a confidence level of 95 %, unless otherwise stated. + +A confidence level of 95 % is the measurement uncertainty tolerance interval for a specific measurement that contains 95 % of the performance of a population of test equipment. + +For RF tests it should be noted that the uncertainties in subclause 5.10 apply to the Test System operating into a nominal 50 ohm load and do not include system effects due to mismatch between the DUT and the Test System. + +### 5.10.1 Measurement of test environments + +The measurement accuracy of the BS test environments defined in subclause 5.9 shall be: + +| | | +|----------------------|-------------| +| Pressure: | ± 5 kPa | +| Temperature: | ± 2 degrees | +| Relative Humidity: | ± 5 % | +| DC Voltage: | ± 1,0 % | +| AC Voltage: | ± 1,5 % | +| Vibration: | 10 % | +| Vibration frequency: | 0,1 Hz | + +The above values shall apply unless the test environment is otherwise controlled and the specification for the control of the test environment specifies the uncertainty for the parameter. + +## 5.10.2 Measurement of transmitter + +**Table 5.3: Maximum Test System Uncertainty for transmitter tests** + +| Subclause | Maximum Test System Uncertainty | Derivation of Test System Uncertainty | +|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------| +| 6.2 Maximum output power | ± 0,7 dB | | +| 6.3 Frequency stability | ± 12 Hz | | +| 6.4.2 Power control steps | single step: ± 0,1 dB
ten steps: ± 0,3 dB | Result is difference between two absolute Code Domain Power measurements on the power controlled DPCH. | +| 6.4.3 Power control dynamic range | ± 0,3 dB | | +| 6.4.4 Minimum output power | ± 0,7 dB | | +| 6.4.5 Primary CCPCH power | ± 0,8 dB | | +| 6.4.6 Differential accuracy of Primary CCPCH power | ± 0,1 dB | | +| 6.5.1 Transmit OFF power | ± 2,0 dB | | +| 6.5.2 Transmit ON/OFF time mask | 3,84 Mcps TDD option:
Tx power limit = -79 dBm: ± 2,0 dB
Tx power limit = -33 dBm: ± 0,7 dB

1,28 Mcps TDD option:
Tx power limit = -82 dBm: ± 2,0 dB
Tx power limit = -42 dBm: ± 0,7 dB | | +| 6.6.1 Occupied Bandwidth | ± 100 kHz | Accuracy = ± 3*RBW.
Assume 30 kHz bandwidth | +| 6.6.2.1 Spectrum emission mask | ± 1,5 dB | | +| 6.6.2.2 Adjacent Channel Leakage power Ratio (ACLR) | 3,84 Mcps TDD option:

minimum requirement:
5 MHz offset: ± 0,8 dB
10 MHz offset: ± 0,8 dB

requirement for operation in the same geographic area with unsynchronised TDD BS on adjacent channels:
Wide Area BS:
5 MHz offset: ± 4 dB
10 MHz offset: ± 4 dB
Local Area BS:
5 MHz offset: ± 0,8 dB
10 MHz offset: ± 0,8 dB

requirement for operation in the same geographic area with FDD BS on adjacent channels:
Wide Area BS:
5 MHz offset: TBD
10 MHz offset: ± 4 dB
Local Area BS:
5 MHz offset: ± 0,8 dB
10 MHz offset: ± 0,8 dB

requirement in case of co-siting with unsynchronised TDD BS or FDD BS operating on adjacent channels:
Wide Area BS:
5 MHz offset: TBD
10 MHz offset: TBD
Local Area BS (co-siting with TDD BS):
5 MHz offset: ± 1 dB
10 MHz offset: ± 1 dB

1,28 Mcps TDD option:

minimum requirement:
1,6 MHz offset: ± 0,8 dB
3,2 MHz offset: ± 0,8 dB | | + +| | | | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| |

requirement for operation in the same geographic area with unsynchronised 1,28 Mcps TDD BS on adjacent channels:
Wide Area BS:
1,6 MHz offset: \pm 1 dB
3,2 MHz offset: \pm 1 dB
Local Area BS:
1,6 MHz offset: \pm 0,8 dB
3,2 MHz offset: \pm 0,8 dB

requirement for operation in the same geographic area with unsynchronised TDD BS on adjacent channels:
Wide Area BS:
3,4 MHz offset: \pm 1 dB
Local Area BS:
3,4 MHz offset: \pm 0,8 dB

requirement for operation in the same geographic area with FDD BS on adjacent channels:
Wide Area BS: \pm 4 dB
Local Area BS: \pm 0,8 dB

requirement in case of co-siting with unsynchronised 1,28 Mcps TDD BS on an adjacent channel:
Wide Area BS:
1,6 MHz offset: TBD
3,2 MHz offset: TBD
Local Area BS:
Wide Area BS: \pm 1 dB
Local Area BS: \pm 1 dB

requirement in case of co-siting with unsynchronised TDD BS on an adjacent channel:
Wide Area BS:
3,4 MHz offset: TBD
Local Area BS:
3,4 MHz offset: \pm 1 dB

requirement in case of co-siting with FDD BS on an adjacent channel:
Wide Area BS: TBD

Note: Impact of measurement period (averaging) and intermod effects in the measurement receiver not yet fully studied.

| | +|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| + +| | | | | +|-------|-------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------| +| 6.6.3 | Spurious emissions | $\pm 2,0$ dB for BS and coexistence bands for results
$> -60$ dBm
$\pm 3,0$ dB for results $< -60$ dBm

Outside above range:
$f \leq 2,2$ GHz: $\pm 1,5$ dB
$2,2$ GHz $< f \leq 4$ GHz: $\pm 2,0$ dB
$f > 4$ GHz: $\pm 4,0$ dB | | +| 6.7 | Transmit intermodulation | The value below applies to the setting of the interference signal level only and is unrelated to the measurement uncertainty of the tests (6.6.2.1, 6.6.2.2 and 6.6.3) which have to be carried out in the presence of the interference signal.

$\pm 1$ dB | The uncertainty of the interferer has double the effect on the result due to the frequency offset. | +| 6.8.1 | Modulation accuracy | $\pm 2,5$ % (for single code) | | +| 6.8.2 | Peak code domain error | $\pm 1$ dB | | +| 6.8.3 | Relative Code Domain Error | $\pm 1,0$ dB | | +| 6.8.4 | Time alignment error in MIMO transmission | 1,28 Mcps TDD option:
$\pm [78]$ ns | | + +### 5.10.3 Measurement of receiver + +**Table 5.4: Maximum Test System Uncertainty for receiver tests** + +| Subclause | Maximum Test System Uncertainty
(see NOTE 1) | Derivation of Test System Uncertainty | +|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 7.2 Reference sensitivity level | ± 0,7 dB | | +| 7.3 Dynamic range | ± 1,2 dB | Formula =
SQRT(signal level error 2
and AWGN level error 2 ) | +| 7.4 Adjacent Channel Selectivity (ACS) | ± 1,1 dB | Formula = SQRT
(wanted_level_error 2 +
interferer_level_error 2 ) +
ACLR effect

The ACLR effect is
calculated by:
(Formula to follow) | +| 7.5 Blocking characteristics | Maximum Test System Accuracy with Frequency offset of interfering signal < 15MHz:
± 1,4dB

Frequency offset of interfering signal ≥ 15MHz:
f < 2,2 GHz: ± 1,1 dB
2,2 GHz < f ≤ 4 GHz: ± 1,8 dB
f > 4 GHz: ± 3,2 dB | Formula =
SQRT (wanted_level_error 2
+ interferer_level_error 2 ) +
ACLR effect + Broadband
noise

(Frequency offset < 15
MHz: assuming ACLR of
interfering signal = 68 dB,
measurement uncertainty
of wanted signal = 0,7 dB)

(Frequency offset ≥ 15
MHz:
assuming -130 dBc
broadband noise from
interfering signal)

Harmonics and spurs of the
interfering signal need to
be carefully considered.
Perhaps need to avoid
harmonics of the interferer
that fall on top of the
receive channel.

For the -15 dBm CW
interfering signal, filtering of
the interfering signal (at
least 25 dB) is necessary to
eliminate problems with
broadband noise falling into
the bandwidth of the
wanted signal. | +| 7.6 Intermodulation characteristics | ± 1,3 dB | Formula = SQRT
((2*CW_level_error) 2 +
(mod_level_error) 2 +
(wanted_signal_level_error
) 2 )

(assuming:
CW_level_error: 0,5 dB
mod_level_error: 0,5 dB
wanted_signal_level_error:
0,7 dB) | +| 7.7 Spurious emissions | ± 3,0 dB for BS receive band (-78 dBm)

Outside above range:
f ≤ 2,2 GHz: ± 2,0 dB (-57 dBm)
2,2 GHz < f ≤ 4 GHz: ± 2,0 dB (-47 dBm)
f > 4 GHz : ± 4,0 dB (-47 dBm)
(see note 2) | | + +NOTE 1: Unless otherwise noted, only the Test System stimulus error is considered here. The effect of errors in the BER/FER measurements due to finite test duration is not considered. + NOTE 2: The Test System uncertainty figures for Spurious emissions apply to the measurement of the DUT and not to any stimulus signals. + +#### 5.10.4 Measurement of performance requirements + +**Table 5.5: Maximum Test System Uncertainty for Performance Requirements** + +| Subclause | Maximum Test System Uncertainty
(see NOTE 1) | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------| +| 8.2 Demodulation in static propagation conditions | TBD | +| 8.3 Demodulation of DCH in multipath fading conditions | TBD | +| 8.3A Demodulation of DCH in high speed train conditions | ± 0.4 dB | +| NOTE 1: Only the overall stimulus error is considered here. The effect of errors in the BER/FER measurements due to finite test duration is not considered. | | + +#### 5.11 Test Tolerances (informative) + +The Test Tolerances defined in this subclause have been used to relax the Minimum Requirements in this specification to derive the Test Requirements. + +The Test Tolerances are derived from Test System uncertainties, regulatory requirements and criticality to system performance. As a result, the Test Tolerance may sometimes be set to zero. + +The test tolerances should not be modified for any reason, e. g. to take account of commonly known test system errors (such as mismatch, cable loss, etc.) + +## 5.11.1 Transmitter + +**Table 5.6: Test Tolerance for transmitter tests** + +| Subclause | | Test Tolerance (see NOTE) | +|-----------|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 6.2 | Maximum output power | 0,7 dB | +| 6.3 | Frequency stability | 12 Hz | +| 6.4.2 | Power control steps | single step: 0,1 dB
ten steps: 0,3 dB | +| 6.4.3 | Power control dynamic range | 0,3 dB | +| 6.4.4 | Minimum output power | 0,7 dB | +| 6.4.5 | Primary CCPCH power | 0,8 dB | +| 6.4.6 | Differential accuracy of Primary CCPCH power | ± 0,1 dB | +| 6.5.1 | Transmit OFF power | 2,0 dB | +| 6.5.2 | Transmit ON/OFF time mask | 3,84 Mcps TDD option:
Tx power limit = -79 dBm: 2,0 dB
Tx power limit = -33 dBm: 0,7 dB

1,28 Mcps TDD option:
Tx power limit = -82 dBm: 2,0 dB
Tx power limit = -42 dBm: 0,7 dB

7,68 Mcps TDD option:
Tx power limit = -76 dBm: 2,0 dB
Tx power limit = -33 dBm: 0,7 dB | +| 6.6.1 | Occupied Bandwidth | 0 kHz | +| 6.6.2.1 | Spectrum emission mask | 1,5 dB | +| 6.6.2.2 | Adjacent Channel Leakage power Ratio (ACLR) | 3,84 Mcps TDD option:
minimum requirement: 0,8 dB

operation in the same geographic area:
Wide Area BS:
4 dB for TDD BS on adjacent channels
TBD/4 dB for FDD BS on adjacent channels
Local Area BS: 0,8 dB

co-siting:
Wide Area BS: TBD
Local Area BS: 1 dB

1,28 Mcps TDD option:
minimum requirement: 0,8 dB

operation in the same geographic area:
Wide Area BS: 1 dB for TDD BS on adjacent channels
4 dB for FDD BS on adjacent channels
Local Area BS: 0,8 dB

co-siting:
Wide Area BS: TBD
Local Area BS: 1 dB for TDD BS on adjacent channels

7,68 Mcps TDD option:
minimum requirement: 0,8 dB

operation in the same geographic area:
Wide Area BS:
4 dB for TDD BS on adjacent channels
TBD/4 dB for FDD BS on adjacent channels
Local Area BS: 0,8 dB

co-siting:
Wide Area BS: TBD
Local Area BS: 1 dB | +| 6.6.3 | Spurious emissions | 0 dB | + +| | | | +|-------|-------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 6.7 | Transmit intermodulation | Testing of transmit intermodulation consists of 3 parts:
- testing of spectrum emission mask, see 6.6.2.1
- testing of ACLR, see 6.6.2.2
- testing of spurious emissions, see 6.6.3
For each of these parts, the respective Test Tolerances as specified in this table shall apply.

Test Tolerance for setting of the interferer power level: 0 dB | +| 6.8.1 | Modulation accuracy | 0 % | +| 6.8.2 | Peak code domain error | 1 dB | +| 6.8.3 | Relative Code Domain Error | 1.0 dB | +| 6.8.4 | Time alignment error in MIMO transmission | 1,28 Mcps TDD option:
[78] ns | +| NOTE: | Unless otherwise stated, the Test Tolerances are applied to the DUT Minimum Requirement. See Annex D. | | + +## 5.11.2 Receiver + +**Table 5.7: Test Tolerances for receiver tests** + +| Subclause | Test Tolerances (see NOTE 1) | +|----------------------------------------|------------------------------| +| 7.2 Reference sensitivity level | 0,7 dB | +| 7.3 Dynamic range | 1,2 dB | +| 7.4 Adjacent Channel Selectivity (ACS) | 0 dB | +| 7.5 Blocking characteristics | 0 dB | +| 7.6 Intermodulation characteristics | 0 dB | +| 7.7 Spurious emissions | 0 dB (see NOTE 2) | + +NOTE 1: Unless otherwise stated, the Test Tolerances are applied to the stimulus signal(s). See Annex D. +NOTE 2: The Test Tolerance is applied to the DUT Minimum Requirement. See Annex D. + +## 5.11.3 Performance requirements + +**Table 5.8: Test Tolerances for performance requirements** + +| Subclause | Test Tolerance (see NOTE) | +|--------------------------------------------------------------------------------------------------------|---------------------------| +| 8.2 Demodulation in static propagation conditions | TBD | +| 8.3 Demodulation of DCH in multipath fading conditions | TBD | +| 8.3A Demodulation of DCH in high speed train conditions | 0.4dB | +| NOTE: Unless otherwise stated, the Test Tolerances are applied to the stimulus signal(s). See Annex D. | | + +## 5.12 Interpretation of measurement results + +The measurement results returned by the Test System are compared - without any modification - against the Test Requirements as defined by the shared risk principle. + +The Shared Risk principle is defined in ITU-R M.1545 [13]. + +The actual measurement uncertainty of the Test System for the measurement of each parameter shall be included in the test report. + +The recorded value for the Test System uncertainty shall be, for each measurement, equal to or lower than the appropriate figure in subclause 5.10 of this TS. + +If the Test System for a test is known to have a measurement uncertainty greater than that specified in subclause 5.10, it is still permitted to use this equipment provided that an adjustment is made as follows: + +Any additional uncertainty in the Test System over and above that specified in subclause 5.10 shall be used to tighten the Test Requirement - making the test harder to pass. (For some tests, e. g. receiver tests, this may require modification of stimulus signals). + +This procedure (defined in Annex D) will ensure that a Test System not compliant with subclause 5.10 does not increase the chance of passing a device under test where that device would otherwise have failed the test if a Test System compliant with subclause 5.10 had been used. + +## 5.13 Selection of configurations for testing + +Measurements shall be performed within the time slots under test as specified individually for each test within the subclause "Initial conditions". + +Most tests in this TS are only performed for a subset of the possible combinations of test conditions. For instance: + +- Not all TRXs in the configuration may be specified to be tested. +- Only one RF channel may be specified to be tested. +- Only one timeslot may be specified to be tested. + +When a test is performed by a test laboratory, the choice of which combinations are to be tested shall be specified by the laboratory. The laboratory may consult with operators, the manufacturer or other bodies. + +When a test is performed by a manufacturer, the choice of which combinations are to be tested may be specified by an operator. + +## 5.14 BS Configurations + +This TS has been written to specify tests for the standard configurations of BS which have been assumed in UTRA requirements specifications, in particular TS 25.105 [1]. However, there are other configurations of BS which comply with these specifications, but for which the application of these specifications is not fully defined. For some such configurations there may be alternate ways to apply the requirements of this specification to testing of the configuration, or some variation in the test method may be necessary. It may therefore be necessary for the parties to the testing to reach agreement over the method of testing in advance. + +If the BS is supplied in a number of different environmental enclosures or configurations, it may not be necessary to test RF parameters for each environmental configuration, provided that it can be demonstrated that the equipment has been tested at the worst internal environmental conditions. + +Where alternative interpretations of this specification are possible for a BS configuration under test, the interpretation which has been adopted in performing the test shall be recorded with the test results. + +Where variation in the test method within this TS has been necessary to enable a BS configuration to be tested, the variation in the test method which has been made in performing the test shall be recorded with the test results. Where possible, agreement should be reached in advance about the nature of such a variation with any party who will later receive the test results. + +Possible interpretations of this TS for some common configurations are given in the following subclauses. + +### 5.14.1 Receiver diversity + +For the tests in clause 7 of the present document, the requirement applies at each receiver antenna connector for receivers with antenna diversity. + +Receiver requirements are tested at the antenna connector, with the remaining receiver(s) disabled or their antenna connector(s) being terminated. If the manufacturer has declared the receiver paths to be equivalent, it is sufficient to apply the specified test signal at any one of the receiver antenna connectors. + +For a multi-band BS, multi-band tests for blocking and intermodulation are performed with the interferer(s) applied to each antenna connector mapped to the receiver for the wanted signal(s), however only to one antenna at a time. Antenna connectors to which no signals are applied are terminated. + +### 5.14.2 Duplexers + +Due to TDD operation, there is no need to use a duplexer in the BS. + +### 5.14.3 Power supply options + +If the BS is supplied with a number of different power supply configurations, it may not be necessary to test RF parameters for each of the power supply options, provided that it can be demonstrated that the range of conditions over which the equipment is tested is at least as great as the range of conditions due to any of the power supply configurations. + +This applies particularly if a BS contains a DC rail which can be supplied either externally or from an internal mains power supply. In this case, the conditions of extreme power supply for the mains power supply options can be tested by testing only the external DC supply option. The range of DC input voltages for the test should be sufficient to verify the performance with any of the power supplies, over its range of operating conditions within the BS, including variation of mains input voltage, temperature and output current. + +### 5.14.4 Ancillary RF amplifiers + +The requirements of this TS shall be met with the ancillary RF amplifier fitted. At tests according to clause 6 and 7 for TX and RX respectively, the ancillary amplifier is connected to the BS by a connecting network (including any cable(s), attenuator(s), etc.) with applicable loss to make sure the appropriate operating conditions of the ancillary amplifier and the BS. The applicable connecting network loss range is declared by the manufacturer. Other characteristics and the temperature dependence of the attenuation of the connecting network are neglected. The actual attenuation value of the connecting network is chosen for each test as one of the applicable extreme values. The lowest value is used unless otherwise stated. + +Sufficient tests should be repeated with the ancillary amplifier fitted and, if it is optional, without the ancillary RF amplifier to verify that the BS meets the requirements of this TS in both cases. + +### 5.14.5 BS using antenna arrays + +A BS may be configured with a multiple antenna port connection for some or all of its TRXs or with an antenna array related to one cell (not one array per TRX). This subclause applies to a BS which meets at least one of the following conditions: + +- The transmitter output signals from one or more TRX appear at more than one antenna port, or +- there is more than one receiver antenna port for a TRX or per cell and an input signal is required at more than one port for the correct operation of the receiver (NOTE: diversity reception does not meet this requirement) thus the outputs from the transmitters as well as the inputs to the receivers are directly connected to several antennas (known as "aircombining"), or + +If a BS is used, in normal operation, in conjunction with an antenna system which contains filters or active elements which are necessary to meet the UTRA requirements, the tests of conformance may be performed on a system comprising the BS together with these elements, supplied separately for the purposes of testing. In this case, it must be demonstrated that the performance of the configuration under test is representative of the system in normal operation, and the conformance assessment is only applicable when the BS is used with the antenna system. + +For testing of conformance of such a BS, the following procedure may be used: + +#### 5.14.5.1 Receiver tests + +For each test, the test signals applied to the receiver antenna connectors shall be such that the sum of the powers of the signals applied equals the power of the test signal(s) specified in the test. + +An example of a suitable test set up is shown in figure 5.1. + +![Figure 5.1: Receiver test set up. A block diagram showing a 'Test input port' connected to a 'Splitting network'. The 'Splitting network' has three output lines connected to a 'BSS' block. A dashed vertical line labeled 'RX antenna interface' passes through the connection points. The power at each connection point is labeled P_i. To the right of the BSS block, the text P_s = Sum(P_i) where P_s = required input power specified is shown.](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +Figure 5.1: Receiver test set up. A block diagram showing a 'Test input port' connected to a 'Splitting network'. The 'Splitting network' has three output lines connected to a 'BSS' block. A dashed vertical line labeled 'RX antenna interface' passes through the connection points. The power at each connection point is labeled P\_i. To the right of the BSS block, the text P\_s = Sum(P\_i) where P\_s = required input power specified is shown. + +Figure 5.1: Receiver test set up + +For spurious emissions from the receiver antenna connector, the test may be performed separately for each receiver antenna connector. + +#### 5.14.5.2 Transmitter tests + +For each test, the conformance requirement shall be met by the sum of the signals emitted by each transmitter antenna connector. This may be assessed by separately measuring the signals emitted by each antenna connector and summing the results, or by combining the signals and performing a single measurement. The characteristics (e.g. amplitude and phase) of the combining network should be such that the power of the combined signal is maximised. + +An example of a suitable test set up is shown in figure 5.2. + +![Figure 5.2: Transmitter test set up. A block diagram showing a 'BSS' block connected to a 'Combining network'. The 'Combining network' has three input lines from the BSS. A dashed vertical line labeled 'TX antenna interface' passes through the connection points. The output of the combining network is labeled 'Test output port'.](23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg) + +Figure 5.2: Transmitter test set up. A block diagram showing a 'BSS' block connected to a 'Combining network'. The 'Combining network' has three input lines from the BSS. A dashed vertical line labeled 'TX antenna interface' passes through the connection points. The output of the combining network is labeled 'Test output port'. + +Figure 5.2: Transmitter test set up + +For Intermodulation attenuation, the test may be performed separately for each transmitter antenna connector. + +#### 5.14.6 MIMO transmission + +Unless otherwise stated, for the tests in clause 6 of the present document, the requirement applies for each transmitter antenna connector in the case of MIMO transmission. + +Transmitter requirements are tested at the antenna connector, with the remaining antenna connector(s) being terminated. If the manufacturer has declared the transmitter paths to be equivalent, it is sufficient to measure the signal at any one of the transmitter antenna connectors. + +### 5.15 Overview of the conformance test requirements + +Tables 5.9, 5.10 and 5.11 give an overview of the conformance test requirements for the transmitter, the receiver and system performance, respectively. Requirements related to receive functionality for the BS under test do not apply for the case of MBSFN-only operation. + +**Table 5.9: Overview of the conformance tests requirements for the transmitter** + +| Parameter | Subclause | Note | +|----------------------------------------------|------------------|-------------------------------------| +| Maximum output power | 6.2 | manufacturer's declaration required | +| Frequency stability | 6.3 | manufacturer's declaration required | +| Output power dynamics | 6.4 | | +| Inner loop power control | 6.4.1 | | +| Power control steps | 6.4.2 | | +| Power control dynamic range | 6.4.3 | | +| Minimum output power | 6.4.4 | | +| Primary CCPCH power | 6.4.5 | | +| Differential accuracy of Primary CCPCH power | 6.4.6 | | +| Transmit OFF power | 6.5.1 | | +| Transmit ON/OFF time mask | 6.5.2 | | +| Output RF spectrum emissions | 6.6 | | +| Occupied bandwidth | 6.6.1 | | +| Out-of-band emission | 6.6.2 | | +| Spectrum emission mask | 6.6.2.1 | manufacturer's declaration required | +| Adjacent Channel Leakage power Ratio (ACLR) | 6.6.2.2 | manufacturer's declaration required | +| Spurious emissions | 6.6.3 | | +| Mandatory requirements | 6.6.3.2.1 | manufacturer's declaration required | +| Co-existence with GSM 900 | 6.6.3.2.2 | manufacturer's declaration required | +| Co-existence with DCS 1800 | 6.6.3.2.3 | manufacturer's declaration required | +| Co-existence with UTRA FDD | 6.6.3.2.4 | manufacturer's declaration required | +| Co-existence with unsynchronised TDD | 6.6.3.2.5 | manufacturer's declaration required | +| Transmit intermodulation | 6.7 | | +| Transmit modulation | 6.8 | | +| Modulation accuracy | 6.8.1 | | +| Peak code domain error | 6.8.2 | | + +**Table 5.10: Overview of the conformance tests requirements for the receiver** + +| Parameter | Subclause | Note | +|------------------------------------|------------------|-------------------------------------| +| Reference sensitivity level | 7.2 | | +| Dynamic range | 7.3 | | +| Adjacent Channel Selectivity (ACS) | 7.4 | | +| Blocking characteristics | 7.5 | manufacturer's declaration required | +| Intermodulation characteristics | 7.6 | | +| Spurious emissions | 7.7 | | + +**Table 5.11: Overview of the conformance test requirements for system performance** + +| Parameter | Subclause | Note | +|----------------------------------------------------|------------------|-------------| +| Demodulation in static propagation conditions | 8.2 | | +| Demodulation of DCH | 8.2.1 | | +| Demodulation of DCH in multipath fading conditions | 8.3 | | +| Multipath fading Case 1 | 8.3.1 | | +| Multipath fading Case 2 | 8.3.2 | | +| Multipath fading Case 3 | 8.3.3 | | +| Demodulation of DCH in high speed train conditions | 8.3A | | + +## 5.16 Format and interpretation of tests + +Each test in the following clauses has a standard format: + +### **X Title** + +The title gives the name of the parameter to be tested. + +#### **X.1 Definition and applicability** + +This subclause gives the general definition of the parameter under consideration and specifies whether the test is applicable to all equipment or to a certain subset only. + +#### **X.2 Minimum Requirements** + +This subclause is an informative copy of the Minimum Requirements defined by the core specification. + +In addition, this subclause contains the reference to the subclause of the 3GPP reference (or core) specification which defines the Minimum Requirements. + +#### **X.3 Test purpose** + +This subclause defines the purpose of the test. + +#### **X.4 Method of test** + +##### **X.4.1 Initial conditions** + +This subclause defines the initial conditions for each test, including the test environment, the RF channels to be tested and the basic measurement setup. + +##### **X.4.2 Procedure** + +This subclause describes the steps necessary to perform the test and provides further details of the test definition like point of access (e.g. antenna port), domain (e.g. frequency-span), range, weighting (e.g. bandwidth), and algorithms (e.g. averaging). + +#### **X.5 Test Requirements** + +This subclause defines the pass/fail criteria for the equipment under test. See subclause 5.12 Interpretation of measurement results. + +## 5.17 Regional requirements + +Some requirements in this specification may only apply in certain regions. Table 5.12 lists all requirements that may be applied differently in different regions. + +**Table 5.12: List of regional requirements** + +| Subclause number | Requirement | Comments | +|------------------|---------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 4.1 | General | Only 3,84 Mcps and 7,68 Mcps TDD options are currently applicable in Japan. | +| 4.2 | Frequency bands | Some bands may be applied regionally. | +| 5.1 | Base station classes | Only requirements for Wide Area Base Stations shall be applied as regional requirements in Japan. | +| 6.2.2 | Maximum output power | In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the ranges defined for the Normal test environment in subclause 5.8.1 | +| 6.6.2.1. | Spectrum emission mask | The mask specified may be mandatory in certain regions. In other regions this mask may not be applied. | +| 6.6.3.2.1.1 | Spurious emissions (Category A) | These requirements shall be met in cases where Category A limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [6], are applied. | +| 6.6.3.2.1.2 | Spurious emissions (Category B) | These requirements shall be met in cases where Category B limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [6], are applied. | +| 6.6.3.2.2.1 | Co-existence with GSM, DCS, UTRA and/or E-UTRA -Operation in the same geographic area | This requirement may be applied for the protection of other BS or UE receivers when GSM, DCS, UTRA and/or E-UTRA BS are operating in the same geographic area with a UTRA TDD BS. | +| 6.6.3.2.2.2 | Co-existence with GSM, DCS, UTRA and/or E-UTRA -Co-located base stations | This requirement may be applied for the protection of other BS receivers when GSM, DCS UTRA and/or E-UTRA BS are co-located with a UTRA TDD BS. | +| 6.6.3.2.5.1 | Co-existence with unsynchronised TDD - Operation in the same geographic area | This requirement may be applied for the protection of TDD BS receivers in geographic areas in which unsynchronised TDD is deployed. | +| 6.6.3.2.5.2 | Co-existence with unsynchronised TDD - Co-located base stations | This requirement may be applied for the protection of TDD BS receivers when unsynchronised TDD BS are co-located. | +| 6.6.3.2.6 | Co-existence with PHS | This requirement may be applied for the protection of PHS in geographic areas in which both PHS and UTRA TDD are deployed. | +| 7.5 | Blocking characteristic | The requirement is applied according to what frequency bands in subclause 4.2 that are supported by the BS. | +| 7.5 | Blocking characteristics | This requirement may be applied for the protection of UTRA TDD BS receivers when UTRA TDD BS and GSM 900/DCS1800 BS are co-located. | + +## 5.18 Definition of Additive White Gaussian Noise (AWGN) Interferer + +The minimum bandwidth of the AWGN interferer shall be 1,5 times chip rate of the radio access mode (e.g. 5,76 MHz for a chip rate of 3,84 Mcps and 1,92 MHz for a chip rate of 1,28 Mcps). The flatness across this minimum bandwidth shall be within $\pm 0,5$ dB, and the peak to average ratio at a probability of 0,001% shall exceed 10 dB. + +## 5.19 Applicability of requirements + +For BS that is UTRA TDD (single-RAT) capable only, the requirements in the present document are applicable and additional conformance to TS 37.141 [12] is optional. For a BS additionally conforming to TS 37.141 [12], conformance to some of the RF requirements in the present document can be demonstrated through the corresponding requirements in TS 37.141 [12] as listed in Table 5.13 + +**Table 5.13: Alternative RF test requirements for a BS additionally conforming to TS 37.141 [12]** + +| RF requirement | Clause in the present document | Alternative clause in TS 37.141 [16] | +|--------------------------------------|--------------------------------|----------------------------------------------| +| Base station output power | 6.2.5 | 6.2.1
6.2.2 | +| Transmit OFF power | 6.5.1.5 | 6.4 | +| Transmit ON/OFF time mask | 6.5.2.5 | 6.4 | +| Unwanted emissions | | | +| Spectrum emission mask | 6.6.2.1.5 | 6.6.2.5.1 | +| Transmitter spurious emissions | 6.6.3.5 | 6.6.1.5 (except for 6.6.1.5.3 and 6.6.1.5.4) | +| Transmitter intermodulation | 6.7.5 | 6.7.5.1&6.7.5.3 | +| Blocking | 7.5.5 | 7.4.5.1 and 7.4.5.5 | +| Out-of-band blocking | 7.5.5 | 7.5.5.1 | +| Co-location with other base stations | 7.5.5 | 7.5.5.2 | +| Receiver spurious emissions | 7.7.5 | 7.6.5.1 | +| Intermodulation | 7.6.5 | 7.7.5.1 | + +## 5.20 Test configurations for multi-carrier operation + +The test configurations shall be constructed using the methods defined below, subject to the parameters declared by the manufacturer for the supported RF configurations as listed in subclause 5.1.2. The applicable test configurations to be used for conformance testing are defined for each supported RF configuration in clause 5.21. + +Note: The test configurations in this subclause are intended for UTRA TDD 1.28Mcps option. + +### 5.20.1 UTTC1: Multi-carrier operation test configuration + +The purpose of the UTTC1 is to test both BS transmitter and receiver requirements. + +#### 5.20.1.1 UTTC1 generation + +UTTC1 should be constructed using the following method: + +- The RF bandwidth shall be the declared maximum supported RF bandwidth. +- Place two UTRA TDD 1.28Mcps option carriers adjacent to the high and low edge of the RF bandwidth. +- For transmitter tests, alternately place a UTRA TDD 1.28Mcps option carrier adjacent to the already placed carriers at the low and high edge of the RF bandwidth until there is no more space to fit a carrier or the BS does not support more carriers. The nominal carrier spacing defined in clause 4.4.1 shall apply. + +#### 5.20.1.1 UTTC1 power allocation + +Set the power of each carrier to the same level so that the sum of the carrier powers equals the rated total output power according to the manufacturer's declaration in sub clause 5.1.2. + +### 5.20.2 UTTC2: Multi-band test configuration for full carrier allocation + +The purpose of the UTTC2 is to test multi-band operation aspects considering maximum supported number of carriers. + +#### 5.20.2.1 UTTC2 generation + +UTTC2 is based on re-using the existing test configuration applicable per band involved in multi-band operation. It is constructed using the following method: + +- The RF bandwidth of each supported operating band in multi-band operation shall be the declared maximum RF bandwidth of each supported operating band in multi-band operation. +- The number of carriers of each supported operating band shall be the declared maximum number of supported carrier of each supported operating band in multi-band operation. Carriers shall first be placed at the outermost + +edges of the declared maximum radio bandwidth. Additional carriers shall next be placed at the edges of the RF bandwidths, if possible. + +- The allocated RF bandwidth of the outermost bands shall be located at the outermost edges of the declared maximum radio bandwidth. +- Each concerned band shall be considered as an independent band and the corresponding UTTC1 shall be generated in each band. The mirror image of the single-band test configuration shall be used in the highest band being tested for the BS to ensure a narrowband carrier being placed at both edges of the BS maximum radio bandwidth. +- If a multi-band BS supports only 3 carriers, two carriers shall be placed in one band according to UTTC1 while the remaining carrier shall be placed at the edge of the maximum radio bandwidth in the other band. +- If the sum of the maximum RF bandwidth of each supported operating bands is larger than the declared total RF bandwidth of transmitter and receiver for the declared band combinations of the BS, repeat the steps above for test configurations where the RF bandwidth of one of the operating band shall be reduced so that the total RF bandwidth of transmitter and receiver is not exceeded and vice versa. +- If the sum of the maximum number of supported carrier of each supported operating bands in multi-band operation is larger than the declared total number of supported carriers for the declared band combinations of the BS, repeat the steps above for test configurations where in each test configuration the number of carriers of one of the operating band shall be reduced so that the total number of supported carriers is not exceeded and vice versa. + +#### 5.20.2.2 UTTC2 power allocation + +Unless otherwise stated, set the power of each carrier in all supported operating bands to the same power so that the sum of the carrier powers equals the total output power according to the manufacturer's declaration. + +If the allocated power of a supported operating band(s) exceeds the declared rated total output power of the operating band(s) in multi-band operation, the exceeded part shall, if possible, be reallocated into the other band(s). If the power allocated for a carrier exceeds the rated output power declared for that carrier, the exceeded power shall, if possible, be reallocated into the other carriers. + +### 5.21 Applicability of test configurations + +The present clause defines for each RF test requirement the set of mandatory test configurations which shall be used for demonstrating conformance. The applicable test configurations are specified in the tables below for each supported RF configuration, which shall be declared according to subclause 5.1.2. The generation and power allocation for each test configuration is defined in clause 5.20. + +For a BS declared to be capable of single carrier operation only, a single carrier (SC) shall be used for testing. + +For a BS declared to be capable of multi-carrier operation in contiguous spectrum operation only, the test configurations in Table 5.14 shall be used for testing. + +Note: The applicability of test configurations in this subclause is only applicable to UTRA TDD 1.28Mcps option. + +**Table 5.14: Test configurations for a BS capable of multi-carrier operating in contiguous spectrum only** + +| BS test case | Test configuration | +|----------------------------------------------------|---------------------------| +| 6.2 Maximum output power | UTTC1 | +| 6.3 Frequency stability | UTTC1 | +| 6.4 Output power dynamics | - | +| 6.4.2 Power control steps | SC | +| 6.4.3 Power control dynamic range | SC | +| 6.4.4 Minimum output power | SC | +| 6.4.5 Primary CCPCH power | SC | +| 6.4.6 Differential accuracy of Primary CCPCH power | SC | +| 6.5 Transmit ON/OFF power | UTTC1 | +| 6.6 Output RF spectrum emissions | - | +| 6.6.1 Occupied bandwidth | SC | +| 6.6.2 Out of band emission | - | +| 6.6.2.1 Spectrum emission mask | UTTC1 | +| 6.6.2.2 Adjacent Channel Leakage Power Ratio(ACLR) | UTTC1 | +| 6.6.3 Spurious emissions | UTTC1 | +| 6.7 Transmitter intermodulation | UTTC1 | +| 6.8 Transmit Modulation | - | +| 6.8.1 Modulation accuracy | UTTC1 | +| 6.8.2 Peak code domain error | UTTC1 | +| 6.8.3 Relative Code Domain error | UTTC1 | +| 6.8.4 Time alignment error in MIMO transmission | UTTC1 | +| 7.2 Reference sensitivity level | SC | +| 7.3 Dynamic range | SC | +| 7.4 Adjacent Channel Selectivity(ACS) | UTTC1 | +| 7.5 Blocking | UTTC1 | +| 7.6 Intermodulation characteristics | UTTC1 | +| 7.7 Spurious emissions | UTTC1 | + +For a BS declared to be capable of multi-band operation, the test configuration in Table 5.15 shall be used for testing. In the case where multiple bands are mapped on common antenna connector, the test configuration in the second column of Table 5.15 shall be used. In the case where multiple bands are mapped on separate antenna connectors, the test configuration in the third column of Table 5.15 shall be used. + +**Table 5.15: Test configuration for a BS capable of multi-band operation** + +| BS test case | Test for Multi-Band capable BS | | +|----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------| +| | Common antenna connector | Separate antenna connector | +| 6.2 Maximum output power | UTTC1 (Note 1),
UTTC2 | UTTC1 (Note 1),
UTTC2 | +| 6.3 Frequency stability | UTTC1 (Note 1),
UTTC2 | UTTC1 (Note 1),
UTTC2 | +| 6.4 Output power dynamics | | | +| 6.4.2 Power control steps | SC | SC | +| 6.4.3 Power control dynamic range | SC | SC | +| 6.4.4 Minimum output power | SC | SC | +| 6.4.5 Primary CCPCH power | SC | SC | +| 6.4.6 Differential accuracy of Primary CCPCH power | SC | SC | +| 6.5 Transmit ON/OFF power | UTTC2 | UTTC2 | +| 6.6 Output RF spectrum emissions | | | +| 6.6.1 Occupied bandwidth | SC | SC | +| 6.6.2 Out of band emission | | | +| 6.6.2.1 Spectrum emission mask | UTTC1 (Note 1),
UTTC2 | UTTC1 (Note 1,2),
UTTC2 (Note 2) | +| 6.6.2.2 Adjacent Channel Leakage Power Ratio(ACLR) | UTTC1 (Note 1),
UTTC2 (Note 3) | UTTC1 (Note 1),
UTTC2 (Note 2,3) | +| 6.6.3 Spurious emissions | UTTC1 (Note 1),
UTTC2 | UTTC1 (Note 1,2),
UTTC2 (Note 2) | +| 6.7 Transmitter intermodulation | UTTC1 (Note 1), | UTTC1 (Note 1,2), | +| 6.8 Transmit Modulation | | | +| 6.8.1 Modulation accuracy | UTTC1 (Note 1),
UTTC2 | UTTC1 (Note 1),
UTTC2 | +| 6.8.2 Peak code domain error | UTTC1 (Note 1),
UTTC2 | UTTC1 (Note 1),
UTTC2 | +| 6.8.3 Relative Code Domain error | UTTC1 (Note 1),
UTTC2 | UTTC1 (Note 1),
UTTC2 | +| 6.8.4 Time alignment error in MIMO transmission | UTTC1 (Note 1) | UTTC1 (Note 1) | +| 7.2 Reference sensitivity level | SC | SC | +| 7.3 Dynamic range | SC | SC | +| 7.4 Adjacent Channel Selectivity(ACS) | UTTC2 | UTTC1 (Note 1),
UTTC2 (Note 4) | +| 7.5 Blocking | UTTC2 | UTTC1 (Note 1),
UTTC2 (Note 4) | +| 7.6 Intermodulation characteristics | UTTC2 | UTTC1 (Note 1),
UTTC2 (Note 4) | +| 7.7 Spurious emissions | UTTC1 (Note 1),
UTTC2 | UTTC1 (Note 1,2),
UTTC2 (Note 2) | +| Note 1: | UTTC1 shall be applied in each supported operating band according to Tables 5.14. | | +| Note 2: | Single-band requirement apply to each antenna connector for both multi-band operation test and single-band operation test. For single-band operation test, other antenna connector(s) is (are) terminated. | | +| Note 3: | UTTC2 may be applied for Inter RF bandwidth gap only. | | +| Note 4: | UTTC2 is only applied for multi-band receiver. | | + +## 5.22 Requirements for BS capable of multi-band operation + +For BS capable of multi-band operation, the RF requirements in clause 6 and 7 apply for each supported operating band unless otherwise stated. For some requirements it is explicitly stated that specific additions or exclusions to the requirement apply for BS capable of multi-band operation. In the case where multiple bands are mapped on separate antenna connectors, the following applies: + +- Single-band transmitter spurious emissions, operating band unwanted emissions, ACLR, transmitter intermodulation and receiver spurious emissions requirements apply to each antenna connector. +- If the BS is configured for single-band operation, single-band requirements shall apply to the antenna connector configured for single-band operation and no exclusions or provisions for multi-band capable BS are applicable. Single-band requirements are tested separately at the antenna connector configured for single-band operation, with all other antenna connectors terminated. + +For a BS capable of multi-band operation, the RF requirements in the present specification assume synchronized operation, where no simultaneous uplink and downlink occur between the supported operating bands. + +## 6 Transmitter characteristics + +### 6.1 General + +Unless otherwise stated, the requirements in clause 6 are expressed for a single transmitter antenna connector. In case of multi-carrier transmission with multiple transmitter antenna connectors or MIMO transmission, the requirements apply for each transmitter antenna connector. + +A BS supporting MC-HSDPA transmits multiple carriers simultaneously on adjacent carrier frequencies. + +Unless otherwise stated, all measurements shall be made at the BS antenna connector (test port A) with a full complement of transceivers for the configuration in normal operating conditions. If any external apparatus such as a TX amplifier, a filter or the combination of such devices is used, the tests according to subclauses 5.14.4 shall be performed to ensure that the requirements are met at test port B. + +![Diagram of transmitter test ports. A BS cabinet is connected to an External PA (if any), which is connected to an External device (e.g. TX filter). Test port A is at the BS cabinet output. Test port B is at the External device output. The signal flows from the BS cabinet towards the antenna connector.](9ed248b025d766251d58be10b01a1cc0_img.jpg) + +The diagram shows a sequence of components connected in series: a 'BS cabinet', an 'External PA (if any)', and an 'External device e.g. TX filter'. A wavy line represents the signal path between them. 'Test port A' is indicated by an arrow pointing to the output of the BS cabinet. 'Test port B' is indicated by an arrow pointing to the output of the External device. To the right of the External device, a dashed arrow points towards the text 'Towards antenna connector'. + +Diagram of transmitter test ports. A BS cabinet is connected to an External PA (if any), which is connected to an External device (e.g. TX filter). Test port A is at the BS cabinet output. Test port B is at the External device output. The signal flows from the BS cabinet towards the antenna connector. + +Figure 6.1: Transmitter test ports + +#### 6.1.1 IMB Test Models + +The set-up of physical channels for IMB transmitter tests shall be according with the test models below. + +##### 6.1.1.1 IMB Test Model 1 - TM 1 + +This model shall apply to QPSK tests. + +Table 6.0A: IMB TM 1 Active Channels + +| Type | Number of Channels | Time Activity | Fraction of Power (when channel is active) (%) | Level setting (per code) ( dB) | Channelisation on Code Index | +|-------------------------------------|--------------------|------------------------|------------------------------------------------|--------------------------------|------------------------------| +| P-CCPCH+SCH | 1 | All slots | 10 | -10 | 1 | +| P-CPICH | 1 | All slots | 10 | -10 | 0 | +| T-CPICH | 1 | All slots | 90 | -12.22 | 1-15 | +| S-CCPCH Frame Type 1 (SF=256, QPSK) | 1 | All slots | 0.5 | -23 | 3 | +| S-CCPCH Frame Type 2 (SF=16, QPSK) | 15 | Sub-frames {0,1,2,3,4} | 79.5 | -12.75 | 1-15 | + +The Base Station output power is set according to PRAT. + +##### 6.1.1.2 IMB Test Model 2 - TM 2 + +This model shall apply to 16QAM tests. + +**Table 6.0B: IMB TM 2 Active Channels** + +| Type | Number of Channels | Time Activity | Fraction of Power (when channel is active) (%) | Level setting (per code) ( dB) | Channelisation on Code Index | +|-------------------------------------|--------------------|------------------------|------------------------------------------------|--------------------------------|------------------------------| +| P-CCPCH+SCH | 1 | All slots | 10 | -10 | 1 | +| P-CPICH | 1 | All slots | 10 | -10 | 0 | +| T-CPICH | 1 | All slots | 90 | -12.22 | 1-15 | +| S-CCPCH Frame Type 1 (SF=256, QPSK) | 1 | All slots | 0.5 | -23 | 3 | +| S-CCPCH Frame Type 2 (SF=16, 16QAM) | 15 | Sub-frames {0,1,2,3,4} | 79.5 | -12.75 | 1-15 | + +The Base Station output power is set according to PRAT. + +## 6.2 Maximum output power + +### 6.2.1 Definition and applicability + +The following terms are defined in subclause 3.1. + +- Output power, Pout. +- Rated output power, PRAT. +- Rated total output power +- Maximum output power, Pmax. + +### 6.2.2 Minimum Requirements + +In normal conditions, the base station maximum output power shall remain within +2 dB and -2 dB of the manufacturer's rated output power. + +In extreme conditions, the base station maximum output power shall remain within +2,5 dB and -2,5 dB of the manufacturer's rated output power. + +In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the ranges defined for the Normal test environment in subclause 5.9.1. + +The normative reference for this requirement is TS 25.105 [1] subclause 6.2.1.1. + +### 6.2.3 Test purpose + +The test purpose is to verify the accuracy of the maximum output power across the frequency range and under normal and extreme conditions for all transmitters in the BS. + +### 6.2.4 Method of test + +#### 6.2.4.1 Initial conditions + +##### 6.2.4.1.0 General test conditions + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested for single carrier: B, M and T; see subclause 5.3. + +RF bandwidth positions to be tested for multi-carrier: BRFBW, MRFBW and TRFBW in single band operation; see subclause 5.3; BRFBW\_T and BRFBW\_T in multi-band operation, see subclause 5.3. + +In addition, for only one UARFCN or RF bandwidth position, the test shall be performed under extreme power supply as defined in subclause 5.9.4. + +NOTE: Tests under extreme power supply also test extreme temperature. + +#### 6.2.4.1.1 3,84 Mcps TDD option + +- (1) The transmitter under test and all other transmitters of the base station (if any) are switched on. +- (2) The power of the transmitters not under test (if any) are controlled down. +- (3) Connect the power measuring equipment to the BS antenna connector. +- (4) Set the parameters of the transmitted signal according to table 6.1. For MBSFN IMB operation the set of parameters for the transmitted signals is according to IMB test model 1 in subclause 6.1.1.1. + +**Table 6.1: Parameters of the transmitted signal for maximum output power test** + +| Parameter | Value/description | +|---------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | PRAT | +| Number of DPCH in each time slot under test | 9 | +| Power of each DPCH | 1/9 of Base Station output power | +| Data content of DPCH | real life (sufficient irregular) | + +#### 6.2.4.1.2 1,28 Mcps TDD option + +- (1) Connect the power measuring equipment to the BS antenna connector under test. +- (2) For a BS declared to be capable of single carrier operation only, set the parameters of the transmitted signal according to table 6.1A at manufacturer's declared rated output power, PRAT. + +For a BS declared to be capable of multi-carrier operation, set the base station to transmit according to Table 6.1A on all carriers configured using the test configuration and corresponding power setting specified in sub-clause 5.20 and 5.21 + +**Table 6.1A: Parameters of the transmitted signal for 1,28 Mcps TDD** + +| Parameter | Value/description | +|---------------------------------------------|--------------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i
is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| Number of DPCH in each time slot under test | 8 | +| Power of each DPCH | 1/8 of Base Station output power | +| Data content of DPCH | real life (sufficient irregular) | + +#### 6.2.4.1.3 7,68 Mcps TDD option + +- (1) The transmitter under test and all other transmitters of the base station (if any) are switched on. +- (2) The power of the transmitters not under test (if any) are controlled down. +- (3) Connect the power measuring equipment to the BS antenna connector. +- (4) Set the parameters of the transmitted signal according to table 6.1AA. + +**Table 6.1AA: Parameters of the transmitted signal for maximum output power test** + +| Parameter | Value/description | +|---------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | PRAT | +| Number of DPCH in each time slot under test | 9 | +| Power of each DPCH | 1/9 of Base Station output power | +| Data content of DPCH | real life (sufficient irregular) | + +## 6.2.4.2 Procedure + +### 6.2.4.2.1 3,84 Mcps TDD option + +- (1) Measure the output power of the BS signal. +- (2) Run step (1) for RF channels Low / Mid / High. + +### 6.2.4.2.2 1,28 Mcps TDD option + +- (1) Measure the Mean power of the BS signal at the antenna connector. +- (2) Run step (1) for RF channels or RF bandwidth positions defined in subclause 6.2.4.1.0. + +In addition, for a multi-band capable BS, the following steps shall apply: + +- (3) For multi-band capable BS and single band tests, repeat the test per involved band with no carrier activated in the other band. +- (4) For multi-band capable BS with separate antenna connector, the antenna connector not being under test in case of single-band or multi-band test shall be terminated. + +### 6.2.4.2.3 7,68 Mcps TDD option + +- (1) Measure the output power of the BS signal. +- (2) Run step (1) for RF channels Low / Mid / High. + +## 6.2.5 Test Requirements + +NOTE: If the Test Requirement below differs from the Minimum Requirement, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +In normal conditions, the measured output power, derived according to subclause 6.2.4.2, shall remain within +2,7 dB and -2,7 dB of the manufacturer's rated output power, PRAT. + +In extreme conditions, the measured output power, derived according to subclause 6.2.4.2, shall remain within +3,2 dB and -3,2 dB of the manufacturer's rated output power, PRAT. + +## 6.3 Frequency stability + +### 6.3.1 Definition and applicability + +Frequency stability is the ability of the BS to transmit at the assigned carrier frequency. + +## 6.3.2 Minimum Requirements + +The modulated carrier frequency of the BS is observed over a period of one timeslot. The frequency error shall be within the accuracy range given in Table 6.1B. + +**Table 6.1B: Frequency error Minimum Requirements** + +| BS class | Accuracy | +|---------------|-----------| +| Wide Area BS | ±0,05 ppm | +| Local Area BS | ±0,1 ppm | +| Home BS | ±0,25 ppm | + +The normative reference for this requirement is TS 25.105 [1] subclause 6.3.1.1 for the 3,84 Mcps TDD option, subclause 6.3.1.2 for the 1,28 Mcps TDD option and subclause 6.3.1.3 for the 7,68 Mcps TDD option. + +TS 25.105 subclause 6.3 specifies the additional requirement that the BS shall use the same frequency source for both RF generation and the chip clock. Compliance with this requirement is demonstrated by manufacturer's declaration; see subclause 5.4; a dedicated conformance test for this requirement is not defined. + +## 6.3.3 Test purpose + +The test purpose is to verify the accuracy of the carrier frequency across the frequency range and under normal and extreme conditions. + +## 6.3.4 Method of test + +### 6.3.4.1 Initial conditions + +#### 6.3.4.1.0 General test conditions + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested for single carrier: B, M and T; see subclause 5.3. + +RF bandwidth positions to be tested for multicarrier: $B_{RFBW}$ , $M_{RFBW}$ and $T_{RFBW}$ in single-band operation, see subclause 5.3; $B_{RFBW\_T'_{RFBW}}$ and $B'_{RFBW\_T_{RFBW}}$ in multi-band operation, see subclause 5.3. + +The following additional test shall be performed: + +On each RF channels or RF bandwidth positions the test shall be performed under extreme power supply as defined in subclause 5.9.4. + +NOTE: Tests under extreme power supply also test extreme temperature. + +#### 6.3.4.1.1 3,84 Mcps TDD option + +- (1) The transmitter under test and all other transmitters of the base station (if any) are switched on. +- (2) The power of the transmitters not under test (if any) are controlled down. +- (3) Connect the tester to the BS antenna connector. +- (4) Set the parameters of the transmitted signal according to table 6.2. For MBSFN IMB operation the set of parameters for the transmitted signals is according to IMB test model 1 in subclause 6.1.1.1. + +**Table 6.2: Parameters of the transmitted signal for frequency stability test** + +| Parameter | Value/description | +|---------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| Number of DPCH in each time slot under test | 1 | +| BS output power setting | PRAT | +| Data content of DPCH | real life (sufficient irregular) | + +#### 6.3.4.1.2 1,28 Mcps TDD option + +- (1) Connect the tester to the BS antenna connector under test. +- (2) For a BS declared to be capable of single carrier operation only, set the parameters of the transmitted signal according to table 6.2A at manufacturer's declared output power, PRAT. + +For a BS declared to be capable of multi-carrier operation, set the BS to transmit according to Table 6.2A on all carriers configured using the applicable test configuration and corresponding power setting specified in sub-clause 5.20 and 5.21 + +**Table 6.2A: Parameters of the transmitted signal for Frequency stability test for 1,28 Mcps TDD** + +| Parameter | Value/description | +|---------------------------------------------|-----------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 6:
transmit, if i
is 0, 4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| Number of DPCH in each time slot under test | 1 | +| Data content of DPCH | real life (sufficient irregular) | + +#### 6.3.4.1.3 7,68 Mcps TDD option + +- (1) The transmitter under test and all other transmitters of the base station (if any) are switched on. +- (2) The power of the transmitters not under test (if any) are controlled down. +- (3) Connect the tester to the BS antenna connector. +- (4) Set the parameters of the transmitted signal according to table 6.2AA. + +**Table 6.2AA: Parameters of the transmitted signal for frequency stability test** + +| Parameter | Value/description | +|---------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| Number of DPCH in each time slot under test | 1 | +| BS output power setting | PRAT | +| Data content of DPCH | real life (sufficient irregular) | + +### 6.3.4.2 Procedure + +- (1) Measure the frequency error delta $f$ across one burst (time slot), by applying the global in-channel Tx test method described in Annex C. +- (2) Repeat step (1) for 200 bursts (time slots). +- (3) Run steps (1) and (2) for RF channels or RF bandwidth positions defined in subclause 6.2.4.1.0. + +In addition, for a multi-band capable BS, the following steps shall apply: + +- (4) For multi-band capable BS and single band tests, repeat the test per involved band with no carrier activated in the other band. +- (5) For multi-band capable BS with separate antenna connector, the antenna connector not being under test in case of single-band or multi-band test shall be terminated. + +## 6.3.5 Test Requirements + +NOTE: If the Test Requirement below differs from the Minimum Requirement, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +For all measured bursts (time slots), the frequency error of each carrier, derived according to subclause 6.3.4.2, shall be within the accuracy range given in table 6.2B. + +**Table 6.2B: Frequency error Test Requirements** + +| BS class | Accuracy | +|---------------|------------------------------------------| +| Wide Area BS | $\pm (0,05 \text{ ppm} + 12 \text{ Hz})$ | +| Local Area BS | $\pm (0,1 \text{ ppm} + 12 \text{ Hz})$ | +| Home BS | $\pm (0,25 \text{ ppm} + 12 \text{ Hz})$ | + +## 6.4 Output power dynamics + +### 6.4.1 Inner loop power control + +Inner loop power control is the ability of the BS transmitter to adjust its code domain power in response to the UL received signal. + +For inner loop correction on the Downlink Channel, the base station adjusts the code domain power of a power controlled CCTrCH in response to each valid power control bit received from the UE on the Uplink Traffic Channel based on the mapping of the TPC bits in uplink CCTrCH to downlink CCTrCH. Inner loop control is based on SIR measurements at the UE receiver, and the corresponding TPC commands are generated by the UE. + +### 6.4.2 Power control steps + +#### 6.4.2.1 Definition and applicability + +The power control step is the step change in the DL code domain power in response to a TPC message from the UE. + +#### 6.4.2.2 Minimum Requirements + +The power control step sizes in the DL shall be 1 dB, 2 dB and 3 dB. + +The tolerance of the code domain power and the greatest average rate of change in code domain power due to the power control step shall be within the range shown in Table 6.3. + +**Table 6.3: Power control step size tolerance** + +| Step size | Tolerance | Range of average rate of change in code domain power per 10 steps | | +|-----------|-----------|-------------------------------------------------------------------|---------| +| | | Minimum | maximum | +| | | | | + +| | | | | +|------|---------------|-------------|-------------| +| 1 dB | $\pm 0,5$ dB | $\pm 8$ dB | $\pm 12$ dB | +| 2 dB | $\pm 0,75$ dB | $\pm 16$ dB | $\pm 24$ dB | +| 3 dB | $\pm 1$ dB | $\pm 24$ dB | $\pm 36$ dB | + +The normative reference for this requirement is TS 25.105 [1] subclause 6.4.2.1. + +### 6.4.2.3 Test purpose + +The DL power control is applied to adjust the BS code domain power to a value that is sufficiently high to generate a SIR at the UE receiver equal to the target SIR, while limiting the intercell interference. + +The test purpose is to verify the ability of the BS to interpret received TPC commands in a correct way and to adjust its code domain power according to these commands with the specified accuracy. + +### 6.4.2.4 Method of test + +#### 6.4.2.4.1 Initial conditions + +##### 6.4.2.4.1.0 General test conditions + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested: B, M and T; see subclause 5.3. + +##### 6.4.2.4.1.1 3,84 Mcps TDD option + +- (1) Connect the BS tester to the antenna connector of the BS under test. +- (2) Disable closed loop power control in the BS under test. +- (3) Set the initial parameters of the BS transmitted signal according to table 6.4. +- (4) Operate the BS in such a mode that it is able to interpret received TPC commands. +- (5) Start BS transmission. + +NOTE: The BS tester used for this test must have the ability: + +- to analyze the output signal of the BS under test with respect to code domain power, by applying the global in-channel Tx test method described in Annex C; +- to simulate an UE with respect to the generation of TPC commands embedded in a valid UE signal. + +**Table 6.4: Initial parameters of the BS transmitted signal for power control steps test** + +| Parameter | Value/description | +|---------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| Number of DPCH in each time slot under test | 1 | +| DPCH power | Minimum | +| Data content of DPCH | real life (sufficient irregular) | + +##### 6.4.2.4.1.2 1,28 Mcps TDD option + +- (1) Connect the BS tester to the antenna connector of the BS under test. +- (2) Disable closed loop power control in the BS under test. +- (3) Set the initial parameters of the BS transmitted signal according to Table 6.4A at manufacturer's declared output power, PRAT. + +- (4) Operate the BS in such a mode that it is able to interpret received TPC commands. +- (5) Start BS transmission. + +NOTE: The BS tester used for this test must have the ability + +- to analyze the output signal of the BS under test with respect to code domain power, by applying the global in-channel Tx test method described in Annex C; +- to simulate an UE with respect to the generation of TPC commands embedded in a valid UE signal. + +**Table 6.4A: Initial parameters of the BS transmitted signal for power control steps test for 1,28 Mcps TDD** + +| Parameter | Value/description | +|---------------------------------------------|-----------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 6:
transmit, if i
is 0, 4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| Number of DPCH in each time slot under test | 1 | +| Data content of DPCH | real life (sufficient irregular) | + +#### 6.4.2.4.1.3 7,68 Mcps TDD option + +- (1) Connect the BS tester to the antenna connector of the BS under test. +- (2) Disable closed loop power control in the BS under test. +- (3) Set the initial parameters of the BS transmitted signal according to table 6.4B. +- (4) Operate the BS in such a mode that it is able to interpret received TPC commands. +- (5) Start BS transmission. + +NOTE: The BS tester used for this test must have the ability: + +- to analyze the output signal of the BS under test with respect to code domain power, by applying the global in-channel Tx test method described in Annex C; +- to simulate an UE with respect to the generation of TPC commands embedded in a valid UE signal. + +**Table 6.4B: Initial parameters of the BS transmitted signal for power control steps test** + +| Parameter | Value/description | +|---------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| Number of DPCH in each time slot under test | 1 | +| DPCH power | Minimum | +| Data content of DPCH | real life (sufficient irregular) | + +#### 6.4.2.4.2 Procedure + +##### 6.4.2.4.2.1 3,84 Mcps TDD option + +- (1) Configure the BS transmitter to enable power control steps of size 1 dB. +- (2) Set the BS tester to produce a sequence of TPC commands related to the active DPCH. This sequence shall be transmitted to the BS within the odd time slots TS i (receive time slots of the BS) and shall consist of a series of + +TPC commands with content "Increase Tx power", followed by a series of TPC commands with content "Decrease Tx power". Each of these series should be sufficiently long so that the code domain power of the active DPCH is controlled to reach its maximum and its minimum, respectively. + +- (3) Measure the code domain power of the active DPCH over the 2464 active chips of each even time slot TS i (this excludes the guard period) by applying the global in-channel Tx test method described in Annex C. +- (4) Based on the measurement made in step (3), calculate the power control step sizes and the average rate of change per 10 steps. +- (5) Configure the BS transmitter to enable power control steps of 2 dB and of 3 dB, respectively, and repeat steps (2) to (4). + +#### 6.4.2.4.2.2 1,28 Mcps TDD option + +- (1) Configure the BS transmitter to enable power control steps of size 1 dB. +- (2) Set the BS tester to produce a sequence of TPC commands related to the active DPCH. This sequence shall be transmitted to the BS within receive time TS i slots of the BS and shall consist of a series of TPC commands with content "Decrease Tx power", followed by a series of TPC commands with content "Increase Tx power". Each of these series should be sufficiently long so that the code domain power of the active DPCH is controlled to reach its minimum and its maximum, respectively. +- (3) Measure the code domain power of the active DPCH over the 848 active chips of each transmit time slot TS i of the BS (this excludes the guard period) by applying the global in-channel Tx test method described in Annex C. +- (4) Based on the measurement made in step (3), calculate the power control step sizes and the average rate of change per 10 steps. +- (5) Configure the BS transmitter to enable power control steps of 2 dB and of 3 dB, respectively, and repeat steps (2) to (4). + +In addition, for a multi-band capable BS, the following steps shall apply: + +- (6) For multi-band capable BS and single band tests, repeat the tests per involved band with no carrier activated in the other band. +- (7) For multi-band capable BS with separate antenna connector, the antenna connector not being under test shall be terminated. + +#### 6.4.2.4.2.3 7,68 Mcps TDD option + +- (1) Configure the BS transmitter to enable power control steps of size 1 dB. +- (2) Set the BS tester to produce a sequence of TPC commands related to the active DPCH. This sequence shall be transmitted to the BS within the odd time slots TS i (receive time slots of the BS) and shall consist of a series of TPC commands with content "Increase Tx power", followed by a series of TPC commands with content "Decrease Tx power". Each of these series should be sufficiently long so that the code domain power of the active DPCH is controlled to reach its maximum and its minimum, respectively. +- (3) Measure the code domain power of the active DPCH over the 4928 active chips of each even time slot TS i (this excludes the guard period) by applying the global in-channel Tx test method described in Annex C. +- (4) Based on the measurement made in step (3), calculate the power control step sizes and the average rate of change per 10 steps. +- (5) Configure the BS transmitter to enable power control steps of 2 dB and of 3 dB, respectively, and repeat steps (2) to (4). + +#### 6.4.2.5 Test Requirements + +**NOTE:** If the Test Requirements below differ from the Minimum Requirement, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +#### 6.4.2.5.1 3,84 Mcps TDD option + +For all measurements, the tolerance of the power control step sizes and the average rate of change per 10 steps shall be within the limits given in Table 6.5. + +**Table 6.5: Test Requirements for power control step size tolerance** + +| Step size | Single step tolerance | Range of average rate of change in code domain power per 10 steps | | +|-----------|-----------------------|-------------------------------------------------------------------|---------------| +| | | Minimum | maximum | +| 1dB | $\pm 0,6$ dB | $\pm 7,7$ dB | $\pm 12,3$ dB | +| 2dB | $\pm 0,85$ dB | $\pm 15,7$ dB | $\pm 24,3$ dB | +| 3dB | $\pm 1,1$ dB | $\pm 23,7$ dB | $\pm 36,3$ dB | + +In case, the power control step size is set to 3 dB, the number of power control steps feasible within the power control dynamic range of the BS under test may be less than 10. In this case, the evaluation of the average rate of change in code domain power shall be based on the number of power control steps actually feasible, and the permitted range of average rate of change shall be reduced compared to the values given in table 6.5 in proportion to the ratio (number of power control steps actually feasible /10). + +EXAMPLE: If the number of power control steps actually feasible is 9, the minimum and maximum value of the range of average rate of change in code domain power are given by $\pm 21,3$ dB and $\pm 32,7$ dB, respectively. + +#### 6.4.2.5.2 1,28 Mcps TDD option + +For all measurements, the tolerance of the power control step sizes and the average rate of change per 10 steps shall be within the limits given in Table 6.5. + +In case, the power control step size is set to 3 dB, the number of power control steps feasible within the power control dynamic range of the BS under test may be less than 10. In this case, the evaluation of the average rate of change in code domain power shall be based on the number of power control steps actually feasible, and the permitted range of average rate of change shall be reduced compared to the values given in table 6.5 in proportion to the ratio (number of power control steps actually feasible /10). + +EXAMPLE: If the number of power control steps actually feasible is 9, the minimum and maximum value of the range of average rate of change in code domain power are given by 21,6 dB and 32,4 dB, respectively. + +#### 6.4.2.5.3 7,68 Mcps TDD option + +For all measurements, the tolerance of the power control step sizes and the average rate of change per 10 steps shall be within the limits given in Table 6.5. + +In case, the power control step size is set to 3 dB, the number of power control steps feasible within the power control dynamic range of the BS under test may be less than 10. In this case, the evaluation of the average rate of change in code domain power shall be based on the number of power control steps actually feasible, and the permitted range of average rate of change shall be reduced compared to the values given in table 6.5 in proportion to the ratio (number of power control steps actually feasible /10). + +EXAMPLE: If the number of power control steps actually feasible is 9, the minimum and maximum value of the range of average rate of change in code domain power are given by $\pm 21,3$ dB and $\pm 32,7$ dB, respectively. + +### 6.4.3 Power control dynamic range + +#### 6.4.3.1 Definition and applicability + +The power control dynamic range is the difference between the maximum and the minimum code domain power of one power controlled code channel for a specified reference condition. + +### 6.4.3.2 Minimum Requirements + +The DL power control dynamic range shall be greater than or equal to 30 dB. + +The normative reference for this requirement is TS 25.105 [1] subclause 6.4.3.1. + +### 6.4.3.3 Test purpose + +The test purpose is to verify the ability of the BS to control the code domain power of a single code signal over the specified dynamic range. + +### 6.4.3.4 Method of test + +#### 6.4.3.4.1 Initial conditions + +##### 6.4.3.4.1.0 General test conditions + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested: B, M and T; see subclause 5.3. + +##### 6.4.3.4.1.1 3,84 Mcps TDD option + +- (1) Connect the BS tester to the antenna connector of the BS under test. +- (2) Set the parameters of the BS transmitted signal according to table 6.6. +- (3) Operate the BS in such a mode that it is able to interpret received TPC commands +- (4) Start BS transmission. + +NOTE: The BS tester used for this test must have the ability: + +- to analyze the output signal of the BS under test with respect to code domain power, by applying the global in-channel Tx test method described in Annex C; +- to simulate an UE with respect to the generation of TPC commands embedded in a valid UE signal. + +**Table 6.6: Parameters of the BS transmitted signal for power control dynamic range test** + +| Parameter | Value/description | +|---------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| Number of DPCH in each time slot under test | 1 | +| Data content of DPCH | real life (sufficient irregular) | + +##### 6.4.3.4.1.2 1,28 Mcps TDD option + +- (1) Connect the BS tester to the antenna connector of the BS under test. +- (2) Set the parameters of the BS transmitted signal according to Table 6.6A at manufacturer's declared output power, PRAT. +- (3) Operate the BS in such a mode that it is able to interpret received TPC commands +- (4) Start BS transmission. + +NOTE: The BS tester used for this test must have the ability + +- to analyze the output signal of the BS under test with respect to code domain power, by applying the global in-channel Tx test method described in Annex C; + +- to simulate an UE with respect to the generation of TPC commands embedded in a valid UE signal. + +**Table 6.6A: Parameters of the BS transmitted signal for power control dynamic range test for 1,28 Mcps TDD** + +| Parameter | Value/description | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i ; i = 0, 1, 2, ..., 6:
transmit, if i is 0, 4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| Number of DPCH in each time slot under test | 1 | +| Data content of DPCH | real life (sufficient irregular) | + +#### 6.4.3.4.1.3 7,68 Mcps TDD option + +- (1) Connect the BS tester to the antenna connector of the BS under test. +- (2) Set the parameters of the BS transmitted signal according to table 6.6B. +- (3) Operate the BS in such a mode that it is able to interpret received TPC commands +- (4) Start BS transmission. + +NOTE: The BS tester used for this test must have the ability: + +- to analyze the output signal of the BS under test with respect to code domain power, by applying the global in-channel Tx test method described in Annex C; +- to simulate an UE with respect to the generation of TPC commands embedded in a valid UE signal. + +**Table 6.6B: Parameters of the BS transmitted signal for power control dynamic range test** + +| Parameter | Value/description | +|---------------------------------------------|--------------------------------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i ; i = 0, 1, 2, ..., 14:
transmit, if i is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i , i even and non zero | +| Number of DPCH in each time slot under test | 1 | +| Data content of DPCH | real life (sufficient irregular) | + +#### 6.4.3.4.2 Procedure + +##### 6.4.3.4.2.1 3,84 Mcps TDD option + +- (1) Configure the BS transmitter to enable power control steps of size 1 dB. +- (2) Set the BS tester to produce a sequence of TPC commands related to the active DPCH, with content "Increase Tx power". This sequence shall be sufficiently long so that the code domain power of the active DPCH is controlled to reach its maximum, and shall be transmitted to the BS within the odd time slots TS *i* (receive time slots of the BS). +- (3) Measure the code domain power of the active DPCH over the 2464 active chips of an even time slot TS *i* (this excludes the guard period) by applying the global in-channel Tx test method described in Annex C. +- (4) Set the BS tester to produce a sequence of TPC commands related to the active DPCH, with content "Decrease Tx power". This sequence shall be sufficiently long so that the code domain power of the active DPCH is controlled to reach its minimum, and shall be transmitted to the BS within the odd time slots TS *i* (receive time slots of the BS). + +- (5) Measure the code domain power of the active DPCH over the 2464 active chips of an even time slot TS i (this excludes the guard period) by applying the global in-channel Tx test method described in Annex C. +- (6) Determine the power control dynamic range by calculating the difference between the maximum code domain power measured in step (3) and the minimum code domain power measured in step (5). +- (7) Configure the BS transmitter to enable power control steps of 2 dB and of 3 dB, respectively, and repeat steps (2) to (6). + +#### 6.4.3.4.2.2 1,28 Mcps TDD option + +- (1) Configure the BS transmitter to enable power control steps of size 1 dB. +- (2) Set the BS tester to produce a sequence of TPC commands related to the active DPCH, with content "Decrease Tx power". This sequence shall be sufficiently long so that the code domain power of the active DPCH is controlled to reach its minimum, and shall be transmitted to the BS within the receive time slots TS i of the BS. +- (3) Measure the code domain power of the active DPCH over the 848 active chips of a transmit time slot TS i of the BS (this excludes the guard period) by applying the global in-channel Tx test method described in Annex C. +- (4) Set the BS tester to produce a sequence of TPC commands related to the active DPCH, with content "Increase Tx power". This sequence shall be sufficiently long so that the code domain power of the active DPCH is controlled to reach its maximum, and shall be transmitted to the BS within the receive time slots TS i of the BS. +- (5) Measure the code domain power of the active DPCH over the 848 active chips of a transmit time slot TS i of the BS (this excludes the guard period) by applying the global in-channel Tx test method described in Annex C. +- (6) Determine the power control dynamic range by calculating the difference between the maximum code domain power measured in step (3) and the minimum code domain power measured in step (5). +- (7) Configure the BS transmitter to enable power control steps of 2 dB and of 3 dB, respectively, and repeat steps (2) to (6). + +In addition, for a multi-band capable BS, the following steps shall apply: + +- (8) For multi-band capable BS and single band tests, repeat the tests per involved band with no carrier activated in the other band. +- (9) For multi-band capable BS with separate antenna connector, the antenna connector not being under test shall be terminated. + +#### 6.4.3.4.2.3 7,68 Mcps TDD option + +- (1) Configure the BS transmitter to enable power control steps of size 1 dB. +- (2) Set the BS tester to produce a sequence of TPC commands related to the active DPCH, with content "Increase Tx power". This sequence shall be sufficiently long so that the code domain power of the active DPCH is controlled to reach its maximum, and shall be transmitted to the BS within the odd time slots TS i (receive time slots of the BS). +- (3) Measure the code domain power of the active DPCH over the 4928 active chips of an even time slot TS i (this excludes the guard period) by applying the global in-channel Tx test method described in Annex C. +- (4) Set the BS tester to produce a sequence of TPC commands related to the active DPCH, with content "Decrease Tx power". This sequence shall be sufficiently long so that the code domain power of the active DPCH is controlled to reach its minimum, and shall be transmitted to the BS within the odd time slots TS i (receive time slots of the BS). +- (5) Measure the code domain power of the active DPCH over the 4928 active chips of an even time slot TS i (this excludes the guard period) by applying the global in-channel Tx test method described in Annex C. +- (6) Determine the power control dynamic range by calculating the difference between the maximum code domain power measured in step (3) and the minimum code domain power measured in step (5). +- (7) Configure the BS transmitter to enable power control steps of 2 dB and of 3 dB, respectively, and repeat steps (2) to (6). + +### 6.4.3.5 Test Requirements + +NOTE: If the Test Requirement below differs from the Minimum Requirement, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +The power control dynamic range derived according to subclause 6.4.3.4.2 shall be greater than or equal to 29,7 dB + +## 6.4.4 Minimum output power + +### 6.4.4.1 Definition and applicability + +The minimum controlled output power of the BS is when the power is set to a minimum value. + +### 6.4.4.2 Minimum Requirements + +The DL minimum output power shall be less than or equal to: + +Maximum output power - 30 dB. + +The normative reference for this requirement is TS 25.105 [1] subclause 6.4.4.1. + +### 6.4.4.3 Test purpose + +The test purpose is to verify the ability of the BS to reduce its output power to a specified value. + +### 6.4.4.4 Method of test + +#### 6.4.4.4.1 Initial conditions + +##### 6.4.4.4.1.0 General test conditions + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested: B, M and T; see subclause 5.3. + +##### 6.4.4.4.1.1 3,84 Mcps TDD option + +- (1) Connect the BS tester to the antenna connector of the BS under test. +- (2) Set the parameters of the BS transmitted signal according to table 6.7. +- (3) Operate the BS in such a mode that it is able to interpret received TPC commands +- (4) Start BS transmission. + +NOTE: The BS tester used for this test must have the ability: + +- to analyse the output signal of the BS under test with respect to mean power; +- to simulate an UE with respect to the generation of TPC commands embedded in a valid UE signal. + +**Table 6.7: Parameters of the BS transmitted signal for minimum power test** + +| Parameter | Value/description | +|---------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| Number of DPCH in each time slot under test | 1 | +| Data content of DPCH | real life (sufficient irregular) | + +## 6.4.4.4.1.2 1,28 Mcps TDD option + +- (1) Connect the BS tester to the antenna connector of the BS under test. +- (2) Set the parameters of the BS transmitted signal according to Table 6.7A at manufacturer's declared output power, PRAT. +- (3) Operate the BS in such a mode that it is able to interpret received TPC commands +- (4) Start BS transmission. + +NOTE: The BS tester used for this test must have the ability + +- to analyse the output signal of the BS under test with respect to mean power; +- to simulate an UE with respect to the generation of TPC commands embedded in a valid UE signal. + +**Table 6.7A: Parameters of the BS transmitted signal for minimum power test for 1,28 Mcps TDD** + +| Parameter | Value/description | +|---------------------------------------------|--------------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i
is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| Number of DPCH in each time slot under test | 1 | +| Data content of DPCH | real life (sufficient irregular) | + +## 6.4.4.4.1.3 7,68 Mcps TDD option + +- (1) Connect the BS tester to the antenna connector of the BS under test. +- (2) Set the parameters of the BS transmitted signal according to table 6.7B. +- (3) Operate the BS in such a mode that it is able to interpret received TPC commands +- (4) Start BS transmission. + +NOTE: The BS tester used for this test must have the ability: + +- to analyse the output signal of the BS under test with respect to mean power; +- to simulate an UE with respect to the generation of TPC commands embedded in a valid UE signal. + +**Table 6.7B: Parameters of the BS transmitted signal for minimum power test** + +| Parameter | Value/description | +|---------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| Number of DPCH in each time slot under test | 1 | +| Data content of DPCH | real life (sufficient irregular) | + +## 6.4.4.4.2 Procedure + +## 6.4.4.4.2.1 3,84 Mcps TDD option + +- (1) Configure the BS transmitter to enable power control steps of size 1 dB. +- (2) Set the BS tester to produce a sequence of TPC commands related to all active DPCH, with content "Decrease Tx power". This sequence shall be sufficiently long so that the output power of all active DPCH is controlled to + +reach its minimum, and shall be transmitted to the BS within the odd time slots TS i (receive time slots of the BS). + +- (3) Measure the power of the BS output signal over the 2464 active chips of an even and non zero time slot TS i (this excludes the guard period), and with a measurement filter that has a RRC filter response with a roll off $\alpha = 0,22$ and a bandwidth equal to the chip rate. The power is determined by calculating the RMS value of the signal samples at the measurement filter output taken at the decision points. +- (4) Configure the BS transmitter to enable power control steps of 2 dB and of 3 dB, respectively, and repeat steps (2) and (3). + +#### 6.4.4.4.2.2 1,28 Mcps TDD option + +- (1) Configure the BS transmitter to enable power control steps of size 1 dB. +- (2) Set the BS tester to produce a sequence of TPC commands related to all active DPCH, with content "Decrease Tx power". This sequence shall be sufficiently long so that the output power of all active DPCH is controlled to reach its minimum, and shall be transmitted to the BS within the receive time slots TS i of the BS. +- (3) Measure the power of the BS output signal over the 848 active chips of a time slot TS i (this excludes the guard period), and with a measurement filter that has a RRC filter response with a roll off $\alpha = 0,22$ and a bandwidth equal to the chip rate. The power is determined by calculating the RMS value of the signal samples at the measurement filter output taken at the decision points. +- (4) Configure the BS transmitter to enable power control steps of 2 dB and of 3 dB, respectively, and repeat steps (2) and (3). + +In addition, for a multi-band capable BS, the following steps shall apply: + +- (5) For multi-band capable BS and single band tests, repeat the tests per involved band with no carrier activated in the other band. +- (6) For multi-band capable BS with separate antenna connector, the antenna connector not being under test shall be terminated. + +#### 6.4.4.4.2.3 7,68 Mcps TDD option + +- (1) Configure the BS transmitter to enable power control steps of size 1 dB. +- (2) Set the BS tester to produce a sequence of TPC commands related to all active DPCH, with content "Decrease Tx power". This sequence shall be sufficiently long so that the output power of all active DPCH is controlled to reach its minimum, and shall be transmitted to the BS within the odd time slots TS i (receive time slots of the BS). +- (3) Measure the power of the BS output signal over the 4928 active chips of an even and non zero time slot TS i (this excludes the guard period), and with a measurement filter that has a RRC filter response with a roll off $\alpha = 0,22$ and a bandwidth equal to the chip rate. The power is determined by calculating the RMS value of the signal samples at the measurement filter output taken at the decision points. +- (4) Configure the BS transmitter to enable power control steps of 2 dB and of 3 dB, respectively, and repeat steps (2) and (3). + +#### 6.4.4.5 Test Requirements + +NOTE: If the Test Requirement below differs from the Minimum Requirement, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +For all measurements, the minimum output power derived in step (4) of subclause 6.4.4.4.2 shall be at least 29,3 dB below the maximum output power; see 6.2. + +## 6.4.5 Primary CCPCH power + +### 6.4.5.1 Definition and applicability + +Primary CCPCH power is the code domain power of the Primary Common Control Physical Channel averaged over the transmit timeslot. Primary CCPCH power is signalled on the BCH. + +### 6.4.5.2 Minimum Requirements + +The error between the BCH-broadcast value of the Primary CCPCH power and the Primary CCPCH code domain power averaged over the timeslot shall not exceed the values in table 6.8. The error is a function of the output power averaged over the timeslot, Pout, and the manufacturer's rated output power, PRAT. + +**Table 6.8: Errors between Primary CCPCH power and the broadcast value** + +| Output power in slot, dB | PCCPCH power tolerance | +|-----------------------------|------------------------| +| PRAT - 3 < Pout ≤ PRAT + 2 | +/- 2,5 dB | +| PRAT - 6 < Pout ≤ PRAT - 3 | +/- 3,5 dB | +| PRAT - 13 < Pout ≤ PRAT - 6 | +/- 5 dB | + +The normative reference for this requirement is TS 25.105 [1] subclause 6.4.5. + +### 6.4.5.3 Test purpose + +The code domain power of the Primary CCPCH received by the UE, together with the information on the Primary CCPCH nominal output power signaled on the BCH, are used by the UE for path loss estimation and adjustment of its own transmit power. Therefore, deviations of the Primary CCPCH code domain power from its nominal value are transposed by the UE into deviations from the wanted output power of the UE. + +The test purpose is to verify that the Primary CCPCH code domain power remains within its specified tolerances. + +### 6.4.5.4 Method of test + +#### 6.4.5.4.1 Initial conditions + +##### 6.4.5.4.1.0 General test conditions + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested: B, M and T; see subclause 5.3. + +##### 6.4.5.4.1.1 3,84 Mcps TDD option + +- (1) Connect the BS tester to the antenna connector of the BS under test. The BS tester must have the ability to analyze the output signal of the BS under test with respect to code domain power, by applying the global in-channel Tx test method described in Annex C. +- (2) Set the parameters of the BS transmitted signal according to table 6.9. + +**Table 6.9: Parameters of the BS transmitted signal for Primary CCPCH power testing** + +| Parameter | Value/description | +|----------------------------------------------|---------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i is even;
receive, if i is odd. | +| Time slots carrying PCCPCH | TS 0 and TS 8 | +| Number of additional DPCH in TS 0 and TS 8 | 3 | +| BS output power setting | PRAT | +| Relative power of PCCPCH | 1/4 of BS output power | +| Relative power of each DPCH in TS 0 and TS 8 | 1/4 of BS output power | +| Data content of DPCH | real life (sufficient irregular) | + +## 6.4.5.4.1.2 1,28 Mcps TDD option + +- (1) Connect the BS tester to the antenna connector of the BS under test. The BS tester must have the ability to analyze the output signal of the BS under test with respect to code domain power, by applying the global in-channel Tx test method described in Annex C. +- (2) Set the parameters of the BS transmitted signal according to Table 6.9A at manufacturer's declared output power, PRAT. + +**Table 6.9A: Parameters of the BS transmitted signal for Primary CCPCH power testing for 1,28 Mcps TDD** + +| Parameter | Value/description | +|----------------------------|----------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 6:
transmit, if i
is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots carrying PCCPCH | TS 0 | +| Relative power of PCCPCH | ½ of BS output power | +| Data content of DPCH | real life (sufficient irregular) | + +## 6.4.5.4.1.3 7,68 Mcps TDD option + +- (1) Connect the BS tester to the antenna connector of the BS under test. The BS tester must have the ability to analyze the output signal of the BS under test with respect to code domain power, by applying the global in-channel Tx test method described in Annex C. +- (2) Set the parameters of the BS transmitted signal according to table 6.9B. + +**Table 6.9B: Parameters of the BS transmitted signal for Primary CCPCH power testing** + +| Parameter | Value/description | +|----------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slots carrying PCCPCH | TS 0 and TS 8 | +| Number of additional DPCH in TS 0 and TS 8 | 3 | +| BS output power setting | PRAT | +| Relative power of PCCPCH | ¼ of BS output power | +| Relative power of each DPCH in TS 0 and TS 8 | ¼ of BS output power | +| Data content of DPCH | real life (sufficient irregular) | + +## 6.4.5.4.2 Procedure + +## 6.4.5.4.2.1 3,84 Mcps TDD option + +- (1) Measure the PCCPCH code domain power in TS 0 and TS 8 by applying the global in-channel Tx test method described in Annex C. +- (2) Reduce the base station output power by 2 dB, 5 dB and 13 dB, without changing the relative powers of the PCCPCH and the DPCHs, and repeat step (1) for each output power setting. + +## 6.4.5.4.2.2 1,28 Mcps TDD option + +- (1) Measure the PCCPCH code domain power in TS 0 by applying the global in-channel Tx test method described in Annex C. +- (2) Reduce the base station output power by 2 dB, 5 dB and 13 dB, without changing the relative powers of the PCCPCH and the DPCHs, and repeat step (1) for each output power setting. + +In addition, for a multi-band capable BS, the following steps shall apply: + +- (3) For multi-band capable BS and single band tests, repeat the tests per involved band with no carrier activated in the other band. +- (4) For multi-band capable BS with separate antenna connector, the antenna connector not being under test shall be terminated. + +#### 6.4.5.4.2.3 7,68 Mcps TDD option + +- (1) Measure the PCCPCH code domain power in TS 0 and TS 8 by applying the global in-channel Tx test method described in Annex C. +- (2) Reduce the base station output power by 2 dB, 5 dB and 13 dB, without changing the relative powers of the PCCPCH and the DPCHs, and repeat step (1) for each output power setting. + +### 6.4.5.5 Test Requirements + +NOTE: If the Test Requirement below differs from the Minimum Requirement, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +The Primary CCPCH power, measured according to subclause 6.4.5.4.2, shall be within the limits defined in table 6.10 + +**Table 6.10: Test Requirements for errors between Primary CCPCH power and the broadcast value** + +| Output power in slot, dB | PCCPCH power tolerance | +|-----------------------------|------------------------| +| PRAT - 3 < Pout ≤ PRAT + 2 | +/- 3,3 dB | +| PRAT - 6 < Pout ≤ PRAT - 3 | +/- 4,3 dB | +| PRAT - 13 < Pout ≤ PRAT - 6 | +/- 5,8 dB | + +## 6.4.6 Differential accuracy of Primary CCPCH power + +### 6.4.6.1 Definition and applicability + +The differential accuracy of the Primary CCPCH power is the relative transmitted power accuracy of PCCPCH in consecutive frames when the nominal PCCPCH power is not changed. + +### 6.4.6.2 Minimum Requirements + +The differential accuracy of PCCPCH power shall be within $\pm 0,5$ dB. + +The normative reference for this requirement is TS 25.105 [1] subclause 6.4.6. + +### 6.4.6.3 Test purpose + +The power of the Primary CCPCH received by the UE, together with the information on the Primary CCPCH nominal transmit power signaled on the BCH, are used by the UE for path loss estimation and adjustment of its own transmit power. Therefore, a lack of accuracy of the Primary CCPCH power over time will result in unwanted fluctuations of the transmit power of the UE which may degrade system performance. + +The test purpose is to verify that the differential accuracy of the Primary CCPCH power remains within its specified tolerances. + +### 6.4.6.4 Method of test + +#### 6.4.6.4.1 Initial conditions + +##### 6.4.6.4.1.0 General test conditions + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested: B, M and T; see subclause 5.3. + +## 6.4.6.4.1.1 3,84 Mcps TDD option + +- 1) Connect the BS tester to the antenna connector of the BS under test. The BS tester must have the ability to analyze the output signal of the BS under test with respect to code domain power, by applying the global in-channel Tx test method described in Annex C. +- 2) Set the parameters of the BS transmitted signal according to table 6.10A. + +**Table 6.10A: Parameters of the BS transmitted signal for testing of differential accuracy of the Primary CCPCH power** + +| Parameter | Value/description | +|----------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slots carrying PCCPCH | TS 0 and TS 8 | +| Number of additional DPCH in TS 0 and TS 8 | 3 | +| BS output power setting | PRAT | +| Relative power of PCCPCH | 1/4 of BS output power | +| Relative power of each DPCH in TS 0 and TS 8 | 1/4 of BS output power | +| Data content of DPCH | real life (sufficient irregular) | + +## 6.4.6.4.1.2 1,28 Mcps TDD option + +- 1) Connect the BS tester to the antenna connector of the BS under test. The BS tester must have the ability to analyze the output signal of the BS under test with respect to code domain power, by applying the global in-channel Tx test method described in Annex C. +- 2) Set the parameters of the BS transmitted signal according to Table 6.10A at manufacturer's declared output power, PRAT. + +**Table 6.10B: Parameters of the BS transmitted signal for testing of differential accuracy of the Primary CCPCH power for 1,28 Mcps TDD** + +| Parameter | Value/description | +|----------------------------|----------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 6:
transmit, if i
is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots carrying PCCPCH | TS 0 | +| Relative power of PCCPCH | 1/2 of BS output power | +| Data content of DPCH | real life (sufficient irregular) | + +## 6.4.6.4.1.3 7,68 Mcps TDD option + +- 1) Connect the BS tester to the antenna connector of the BS under test. The BS tester must have the ability to analyze the output signal of the BS under test with respect to code domain power, by applying the global in-channel Tx test method described in Annex C. +- 2) Set the parameters of the BS transmitted signal according to table 6.10C. + +**Table 6.10C: Parameters of the BS transmitted signal for testing of differential accuracy of the Primary CCPCH power** + +| Parameter | Value/description | +|----------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slots carrying PCCPCH | TS 0 and TS 8 | +| Number of additional DPCH in TS 0 and TS 8 | 3 | +| BS output power setting | PRAT | +| Relative power of PCCPCH | 1/4 of BS output power | +| Relative power of each DPCH in TS 0 and TS 8 | 1/4 of BS output power | +| Data content of DPCH | real life (sufficient irregular) | + +#### 6.4.6.4.2 Procedure + +##### 6.4.6.4.2.1 3,84 Mcps TDD option + +- 1) Measure the PCCPCH code domain power in TS 0 and TS 8 of consecutive frames by applying the global in-channel Tx test method described in Annex C. +- 2) Calculate the differential accuracy of the Primary CCPCH power by taking the the difference between the PCCPCH power measurement results of consecutive frames. + +##### 6.4.6.4.2.2 1,28 Mcps TDD option + +- 1) Measure the PCCPCH code domain power in TS 0 of consecutive frames by applying the global in-channel Tx test method described in Annex C. +- 2) Calculate the differential accuracy of the Primary CCPCH power by taking the the difference between the PCCPCH power measurement results of consecutive frames. + +In addition, for a multi-band capable BS, the following steps shall apply: + +- (3) For multi-band capable BS and single band tests, repeat the tests per involved band with no carrier activated in the other band. +- (4) For multi-band capable BS with separate antenna connector, the antenna connector not being under test shall be terminated. + +##### 6.4.6.4.2.3 7,68 Mcps TDD option + +- 1) Measure the PCCPCH code domain power in TS 0 and TS 8 of consecutive frames by applying the global in-channel Tx test method described in Annex C. +- 2) Calculate the differential accuracy of the Primary CCPCH power by taking the the difference between the PCCPCH power measurement results of consecutive frames. + +#### 6.4.6.5 Test Requirements + +NOTE: If the Test Requirement below differs from the Minimum Requirement, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +The differential accuracy of the Primary CCPCH power, measured according to subclause 6.4.6.4.2, shall be within $\pm 0,6$ dB. + +## 6.5 Transmit ON/OFF power + +### 6.5.1 Transmit OFF power + +#### 6.5.1.1 Definition and applicability + +The transmit OFF power is defined as the RRC filtered mean power measured over one chip when the transmitter is off. + +#### 6.5.1.2 Minimum Requirements + +##### 6.5.1.2.1 3,84 Mcps TDD option + +The transmit OFF power shall be less than -79 dBm. + +##### 6.5.1.2.2 1,28 Mcps TDD option + +The transmit OFF power shall be less than -82 dBm. + +For BS capable of multi-band operation, the requirement is only applicable during the transmitter OFF period in all supported operating bands. The normative reference for this requirement is TS 25.105 [1] subclause 6.5.1. + +##### 6.5.1.2.3 7,68 Mcps TDD option + +The transmit OFF power shall be less than -76 dBm. + +#### 6.5.1.3 Test purpose + +This test verifies the ability of the BS to reduce its transmit OFF power to a value below the specified limit. This ability is needed to minimize the interference for other users receiving on the same frequency. + +#### 6.5.1.4 Method of test + +##### 6.5.1.4.1 Initial conditions + +The conformance testing of transmit OFF power is included in the conformance testing of transmit ON/OFF time mask; therefore, see subclause 6.5.2.4.1 for initial conditions. + +##### 6.5.1.4.2 Procedure + +The conformance testing of transmit OFF power is included in the conformance testing of transmit ON/OFF time mask; therefore, see subclause 6.5.2.4.2 for procedure. + +#### 6.5.1.5 Test Requirements + +The conformance testing of transmit OFF power is included in the conformance testing of transmit ON/OFF time mask; therefore, see subclause 6.5.2.5 for test requirements. + +## 6.5.2 Transmit ON/OFF time mask + +### 6.5.2.1 Definition and applicability + +The transmit ON/OFF time mask defines the ramping time allowed for the BS between transmit OFF power and transmit ON power. + +### 6.5.2.2 Minimum Requirements + +#### 6.5.2.2.1 3,84 Mcps TDD option + +The transmit power level versus time should meet the mask specified in figure 6.1. + +![Figure 6.1: Transmit ON/OFF template diagram showing power levels and chip durations.](89b3389b2c4fa1b452cf2b5daa5f82ad_img.jpg) + +This diagram illustrates the transmit ON/OFF template. The vertical axis represents power levels, with 'Average ON Power' indicated by a dashed horizontal line and '-33 dBm' and 'TX off power' indicated by solid horizontal lines. The horizontal axis represents time in chips. A rectangular pulse represents the 'Burst without GP', which starts 27 chips after the beginning of the measurement interval and ends 31 chips before the end. The total duration of the burst is 84 chips. The 'TX off power' level is maintained for 84 chips after the burst ends. + +Figure 6.1: Transmit ON/OFF template diagram showing power levels and chip durations. + +Figure 6.1: Transmit ON/OFF template + +6.5.2.2.2 1,28 Mcps TDD option + +The transmit power level versus time should meet the mask specified in figure 6.1A. + +![Figure 6.1A: Transmit ON/OFF template for 1,28 Mcps TDD option diagram showing power levels and chip durations within DL Time slots.](58f883d880e744531c77ddfd50af87bf_img.jpg) + +This diagram shows the transmit ON/OFF template for the 1,28 Mcps TDD option. The vertical axis shows power levels: 'Average ON Power' (dashed line), '-42dBm' (solid line), and 'Tx off power -82dBm' (solid line). The horizontal axis is divided into 'DL Time slots'. The template shows a burst of power starting after an initial 8-chip guard period. The burst duration is 85 chips, followed by a 3-chip guard period, and then an 8-chip guard period at the end of the slot. The 'Tx off power' level is maintained during the guard periods. + +Figure 6.1A: Transmit ON/OFF template for 1,28 Mcps TDD option diagram showing power levels and chip durations within DL Time slots. + +Figure 6.1A: Transmit ON/OFF template for 1,28 Mcps TDD option + +The normative reference for this requirement is TS 25.105 [1] subclause 6.5.2. + +6.5.2.2.3 7,68 Mcps TDD option + +The transmit power level versus time should meet the mask specified in Figure 6.1B. + +![Figure 6.1B: Transmit ON/OFF template. The diagram shows a power level over time. The 'Average ON Power' is indicated by a dashed horizontal line. The 'Tx off power' is indicated by a dashed horizontal line. The 'Burst without GP' (Guard Period) is shown as a rectangular pulse. The duration of the burst is 54 chips. The duration of the guard period is 62 chips. The total duration of the time slot is 168 chips. The power level during the burst is -33 dBm.](449dd9d482c5b47f1c013ce3e18b09e6_img.jpg) + +Figure 6.1B: Transmit ON/OFF template. The diagram shows a power level over time. The 'Average ON Power' is indicated by a dashed horizontal line. The 'Tx off power' is indicated by a dashed horizontal line. The 'Burst without GP' (Guard Period) is shown as a rectangular pulse. The duration of the burst is 54 chips. The duration of the guard period is 62 chips. The total duration of the time slot is 168 chips. The power level during the burst is -33 dBm. + +**Figure 6.1B: Transmit ON/OFF template** + +### 6.5.2.3 Test purpose + +This test verifies the ability of the BS to reduce its transmit power outside of the active part of the Tx time slot (burst without guard period) to values below specified limits. This ability is needed to minimize the interference for other users receiving on the same frequency. + +### 6.5.2.4 Method of test + +#### 6.5.2.4.1 Initial conditions + +##### 6.5.2.4.1.0 General test conditions + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested for single carrier: B, M and T; see subclause 5.3. + +RF bandwidth positions to be tested: $B_{RFBW}$ , $M_{RFBW}$ and $T_{RFBW}$ in single band operation; see subclause 5.3; $B_{RFBW\_T'_{RFBW}}$ and $B'_{RFBW\_T_{RFBW}}$ in multi-band operation, see subclause 5.3. + +##### 6.5.2.4.1.1 3,84 Mcps TDD option + +- (1) Connect the power measuring equipment to the BS antenna connector. +- (2) Set the parameters of the transmitted signal according to table 6.11. + +**Table 6.11: Parameters of the transmitted signal for transmit ON/OFF time mask test** + +| Parameter | Value/description | +|---------------------------------------------|---------------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS $i$ ; $i = 0, 1, 2, \dots, 14$ :
transmit, if $i$ is even;
receive, if $i$ is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS $i$ , $i$ even and non zero | +| BS output power setting | PRAT | +| Number of DPCH in each time slot under test | 9 | +| Power of each DPCH | 1/9 of Base Station output power | +| Data content of DPCH | Real life (sufficient irregular) | + +##### 6.5.2.4.1.2 1,28 Mcps TDD option + +- (1) Connect the power measuring equipment to the BS antenna connector under test. + +- (2) For a BS declared to be capable of single carrier operation only, set the parameters of the transmitted signal according to Table 6.11A at manufacturer's declared output power, PRAT. + +For a BS declared to be capable of multi-carrier operation, set the base station to transmit according to Table 6.11A on all carriers configured using the applicable test configuration and corresponding power setting specified in subclass 5.20 and 5.2 + +**Table 6.11A: Parameters of the transmitted signal for transmit ON/OFF time mask test for 1,28 Mcps TDD** + +| Parameter | Value/description | +|---------------------------------------------|-----------------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i is 0,4,5,6;
receive, if i is UpPCH,1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| Number of DPCH in each time slot under test | 8 | +| Data content of DPCH | real life (sufficient irregular) | + +#### 6.5.2.4.1.3 7,68 Mcps TDD option + +- (1) Connect the power measuring equipment to the BS antenna connector. +- (2) Set the parameters of the transmitted signal according to table 6.11B. + +**Table 6.11B: Parameters of the transmitted signal for transmit ON/OFF time mask test** + +| Parameter | Value/description | +|---------------------------------------------|---------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | PRAT | +| Number of DPCH in each time slot under test | 9 | +| Power of each DPCH | 1/9 of Base Station output power | +| Data content of DPCH | Real life (sufficient irregular) | + +#### 6.5.2.4.2 Procedure + +##### 6.5.2.4.2.1 3,84 Mcps TDD option + +- (1) Measure the RRC filtered mean power of the BS output signal chipwise (i.e. averaged over time intervals of one chip duration) over the period starting 65 chips before the start of the odd time slots TS i (receive time slots of the BS), and ending 27 chips before the next even time slot (transmit time slot of the BS) starts. + +##### 6.5.2.4.2.2 1,28 Mcps TDD option + +- (1) Measure the RRC filtered mean power of the BS output signal chipwise (i.e. averaged over time intervals of one chip duration) over the transmit off power period starting 11 chips before the start of the receive time slot TS i = UpPCH, and ending 8 chips before the next transmit time slot TS i=4 starts. + +In addition, for a multi-band capable BS, the following steps shall apply: + +- (2) For multi-band capable BS with separate antenna connector, the antenna connector not being under test shall be terminated. + +#### 6.5.2.4.2.3 7,68 Mcps TDD option + +- (1) Measure the RRC filtered mean power of the BS output signal chipwise (i.e. averaged over time intervals of one chip duration) over the period starting 130 chips before the start of the odd time slots TS *i* (receive time slots of the BS), and ending 54 chips before the next even time slot (transmit time slot of the BS) starts. + +### 6.5.2.5 Test Requirements + +NOTE: If the Test Requirements below differ from the Minimum Requirements, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +#### 6.5.2.5.1 3,84 Mcps TDD option + +Each value of the power measured according to subclause 6.5.2.4.2.1 shall be below - 32,3 dBm in the period from 32 chips to 84 chips after the burst and below - 77 dBm in the period where the Tx OFF power specification is applicable. + +#### 6.5.2.5.2 1,28 Mcps TDD option + +Each value of the power measured according to subclause 6.5.2.4.2.2 shall be below - 41,3 dBm in the period from 85 chips to 88 chips after the burst and below - 80 dBm in the period where the Tx OFF power specification is applicable. + +For BS capable of multi-band operation, the Tx OFF power requirement is only applicable during the transmitter OFF period in all supported operating bands. + +#### 6.5.2.5.3 7,68 Mcps TDD option + +Each value of the power measured according to subclause 6.5.2.4.2.3 shall be below - 32,3 dBm in the period from 64 chips to 168 chips after the burst and below - 74 dBm in the period where the Tx OFF power specification is applicable. + +## 6.6 Output RF spectrum emissions + +### 6.6.1 Occupied bandwidth + +#### 6.6.1.1 Definition and applicability + +Occupied bandwidth is a measure of the bandwidth containing 99% of the total integrated power for transmitted spectrum and is centered on the assigned channel frequency. + +#### 6.6.1.2 Minimum Requirements + +##### 6.6.1.2.1 3,84 Mcps TDD option + +The occupied bandwidth shall be less than 5 MHz based on a chip rate of 3,84 Mcps. + +The normative reference for this requirement is TS 25.105 [1] subclause 6.6.1.1. + +##### 6.6.1.2.2 1,28 Mcps TDD option + +The occupied bandwidth shall be less than 1,6 MHz based on a chip rate of 1,28 Mcps. + +The reference for this requirement is TS 25.105 [1] subclause 6.6.1.2. + +##### 6.6.1.2.3 7,68 Mcps TDD option + +The occupied bandwidth shall be less than 10 MHz based on a chip rate of 7,68 Mcps. + +The reference for this requirement is TS 25.105 [1] subclause 6.6.1.3. + +#### 6.6.1.3 Test purpose + +The occupied bandwidth, defined in the Radio Regulations of the International Telecommunication Union ITU, is a useful concept for specifying the spectral properties of a given emission in the simplest possible manner; see also Recommendation ITU-R SM.328 [7]. The test purpose is to verify that the emission of the BS does not occupy an + +excessive bandwidth for the service to be provided and is, therefore, not likely to create interference to other users of the spectrum beyond undue limits. + +#### 6.6.1.4 Method of test + +##### 6.6.1.4.1 Initial conditions + +###### 6.6.1.4.1.0 General test conditions + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested: B, M and T; see subclause 5.3. + +###### 6.6.1.4.1.1 3,84 Mcps TDD option + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) Set the parameters of the BS transmitted signal according to table 6.12. For MBSFN IMB operation the set of parameters for the transmitted signals is according to IMB test model 1 in subclause 6.1.1.1. + +**Table 6.12: Parameters of the BS transmitted signal for occupied bandwidth testing** + +| Parameter | Value/description | +|---------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | PRAT | +| Number of DPCH in each time slot under test | 9 | +| Power of each DPCH | 1/9 of Base Station output power | +| Data content of DPCH | Real life (sufficient irregular) | + +###### 6.6.1.4.1.2 1,28 Mcps TDD option + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) Set the parameters of the BS transmitted signal according to Table 6.12A at manufacturer's declared output power, PRAT. + +**Table 6.12A: Parameters of the BS transmitted signal for occupied bandwidth testing for 1,28 Mcps TDD** + +| Parameter | Value/description | +|---------------------------------------------|--------------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i
is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| Number of DPCH in each time slot under test | 8 | +| Power of each DPCH | 1/8 of Base Station output power | +| Data content of DPCH | real life (sufficient irregular) | + +###### 6.6.1.4.1.3 7,68 Mcps TDD option + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) Set the parameters of the BS transmitted signal according to table 6.12B. + +**Table 6.12B: Parameters of the BS transmitted signal for occupied bandwidth testing** + +| Parameter | Value/description | +|---------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | PRAT | +| Number of DPCH in each time slot under test | 9 | +| Power of each DPCH | 1/9 of Base Station output power | +| Data content of DPCH | Real life (sufficient irregular) | + +#### 6.6.1.4.2 Procedure + +##### 6.6.1.4.2.1 3,84 Mcps TDD option + +- (1) Measure the power of the transmitted signal with a measurement filter of bandwidth 30 kHz. The characteristic of the filter shall be approximately Gaussian (typical spectrum analyzer filter). The centre frequency of the filter shall be stepped in contiguous 30 kHz steps from a minimum frequency, which shall be (7,5 - 0,015) MHz below the assigned channel frequency of the transmitted signal, up to a maximum frequency, which shall be (7,5 + 0,015) MHz above the assigned channel frequency of the transmitted signal. The time duration of each step shall be sufficiently long to capture one active time slot. The measured power shall be recorded for each step. +- (2) Determine the total output power by accumulating the recorded power measurement results of all steps. +- (3) Sum up the recorded power measurement results, starting from the step at the minimum frequency defined in (1) up to the step at a lower limit frequency by which this sum is equal to or greater than 0.5 % of the total output power determined in (2). This limit frequency is recorded as "Lower Frequency". +- (4) Sum up the recorded power measurement results, starting from the step at the maximum frequency defined in (1) down to the step at an upper limit frequency by which this sum is equal to or greater than 0.5 % of the total output power determined in (2). This limit frequency is recorded as "Upper Frequency". +- (5) Calculate the occupied bandwidth as the difference between the "Upper Frequency" obtained in (3) and the "Lower Frequency" obtained in (4). + +##### 6.6.1.4.2.2 1,28 Mcps TDD option + +- (1) Measure the power of the transmitted signal with a measurement filter of bandwidth 30 kHz. The characteristic of the filter shall be approximately Gaussian (typical spectrum analyser filter). The centre frequency of the filter shall be stepped in contiguous 30 kHz steps from a minimum frequency, which shall be (2,4 - 0,015) MHz below the assigned channel frequency of the transmitted signal, up to a maximum frequency, which shall be (2,4 + 0,015) MHz above the assigned channel frequency of the transmitted signal. The time duration of each step shall be sufficiently long to capture one active time slot. The measured power shall be recorded for each step. +- (2) Determine the total output power by accumulating the recorded power measurement results of all steps. +- (3) Sum up the recorded power measurement results, starting from the step at the minimum frequency defined in (1) up to the step at a lower limit frequency by which this sum is equal to or greater than 0,5 % of the total output power determined in (2). This limit frequency is recorded as "Lower Frequency". +- (4) Sum up the recorded power measurement results, starting from the step at the maximum frequency defined in (1) down to the step at an upper limit frequency by which this sum is equal to or greater than 0,5 % of the total output power determined in (2). This limit frequency is recorded as "Upper Frequency". +- (5) Calculate the occupied bandwidth as the difference between the "Upper Frequency" obtained in (3) and the "Lower Frequency" obtained in (4). + +In addition, for a multi-band capable BS, the following steps shall apply: + +- (6) For multi-band capable BS and single band tests, repeat the steps above per involved band with no carrier activated in the other band. + +- (7) For multi-band capable BS with separate antenna connector, the antenna connector not being under test shall be terminated. + +#### 6.6.1.4.2.3 7,68 Mcps TDD option + +- (1) Measure the power of the transmitted signal with a measurement filter of bandwidth 30 kHz. The characteristic of the filter shall be approximately Gaussian (typical spectrum analyzer filter). The centre frequency of the filter shall be stepped in contiguous 30 kHz steps from a minimum frequency, which shall be (15 - 0,015) MHz below the assigned channel frequency of the transmitted signal, up to a maximum frequency, which shall be (15 - 0,015) MHz above the assigned channel frequency of the transmitted signal. The time duration of each step shall be sufficiently long to capture one active time slot. The measured power shall be recorded for each step. +- (2) Determine the total output power by accumulating the recorded power measurement results of all steps. +- (3) Sum up the recorded power measurement results, starting from the step at the minimum frequency defined in (1) up to the step at a lower limit frequency by which this sum is equal to or greater than 0.5 % of the total output power determined in (2). This limit frequency is recorded as "Lower Frequency". +- (4) Sum up the recorded power measurement results, starting from the step at the maximum frequency defined in (1) down to the step at an upper limit frequency by which this sum is equal to or greater than 0.5 % of the total output power determined in (2). This limit frequency is recorded as "Upper Frequency". +- (5) Calculate the occupied bandwidth as the difference between the "Upper Frequency" obtained in (3) and the "Lower Frequency" obtained in (4). + +#### 6.6.1.5 Test Requirements + +NOTE: If the Test Requirement below differ from the Minimum Requirements, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +##### 6.6.1.5.1 3,84 Mcps TDD option + +The occupied bandwidth calculated in step (5) of subclause 6.6.1.4.2.1 shall be less than 5 MHz. + +##### 6.6.1.5.2 1,28 Mcps TDD option + +The occupied bandwidth calculated in step (5) of subclause 6.6.1.4.2.2 shall be less than 1,6 MHz. + +##### 6.6.1.5.3 7,68 Mcps TDD option + +The occupied bandwidth calculated in step (5) of subclause 6.6.1.4.2.3 shall be less than 10 MHz. + +### 6.6.2 Out of band emission + +Out of band emissions are unwanted emissions immediately outside the channel bandwidth resulting from the modulation process and non-linearity in the transmitter but excluding spurious emissions. This out of band emission requirement is specified both in terms of a spectrum emission mask and adjacent channel power ratio for the transmitter. + +#### 6.6.2.1 Spectrum emission mask + +##### 6.6.2.1.1 Definition and applicability + +###### 6.6.2.1.1.1 3,84 Mcps TDD option + +The spectrum emission mask specifies the limit of the transmitter out of band emissions at frequency offsets from the assigned channel frequency of the wanted signal between 2,5 MHz and 12,5 MHz. + +The mask defined in subclause 6.6.2.1.2.1 below may be mandatory in certain regions. In other regions this mask may not be applied. + +For regions in which the mask is mandatory, the requirements shall apply to both Wide Area BS and Local Area BS. + +#### 6.6.2.1.1.2 1,28 Mcps TDD option + +The spectrum emission mask specifies the limit of the transmitter out of band emissions at frequency offsets from the assigned channel frequency of the wanted signal between 0,8 MHz and 4 MHz. + +For BS capable of multi-band operation where multiple bands are mapped on separate antenna connectors, the single-band requirements apply and the cumulative evaluation of the emission limit in the inter RF bandwidth gap are not applicable. + +The mask defined in subclause 6.6.2.1.2.2 below may be mandatory in certain regions. In other regions this mask may not be applied. + +#### 6.6.2.1.1.3 7,68 Mcps TDD option + +The spectrum emission mask specifies the limit of the transmitter out of band emissions at frequency offsets from the assigned channel frequency of the wanted signal between 5 MHz and 25 MHz. + +The mask defined in subclause 6.6.2.1.2.3 below may be mandatory in certain regions. In other regions this mask may not be applied. + +For regions in which the mask is mandatory, the requirements shall apply to both Wide Area BS and Local Area BS. + +### 6.6.2.1.2 Minimum Requirements + +#### 6.6.2.1.2.1 3,84 Mcps TDD option + +For regions where this subclause applies, the requirement shall be met by a base station transmitting on a single RF carrier configured in accordance with the manufacturer's specification. Emissions shall not exceed the maximum level specified in tables 6.13 to 6.16 in the frequency range of $f\_offset$ from 2,515 MHz to $f\_offset_{max}$ from the carrier frequency, where: + +- $f\_offset$ is the separation between the carrier frequency and the centre of the measurement filter +- $f\_offset_{max}$ is either 12,5 MHz or the offset to the UMTS Tx band edge as defined in subclause 4.2, whichever is the greater. + +**Table 6.13: Spectrum emission mask values, BS maximum output power $P \geq 43$ dBm** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|---------------|-----------------------| +| $2,515 \text{ MHz} \leq f\_offset < 2,715 \text{ MHz}$ | -14 dBm | 30 kHz | +| $2,715 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | | 30 kHz | +| $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | -26 dBm | 30 kHz | +| $4,0 \text{ MHz} \leq f\_offset < 8,0 \text{ MHz}$ | -13 dBm | 1 MHz | +| $8,0 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -13 dBm | 1 MHz | + +**Table 6.14: Spectrum emission mask values, BS maximum output power $39 \leq P < 43$ dBm** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|---------------------|-----------------------| +| $2,515 \text{ MHz} \leq f\_offset < 2,715 \text{ MHz}$ | -14 dBm | 30 kHz | +| $2,715 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | | 30 kHz | +| $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | -26 dBm | 30 kHz | +| $4,0 \text{ MHz} \leq f\_offset < 8,0 \text{ MHz}$ | -13 dBm | 1 MHz | +| $8,0 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | $P - 56 \text{ dB}$ | 1 MHz | + +**Table 6.15: Spectrum emission mask values, BS maximum output power $31 \leq P < 39$ dBm** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|---------------------|-----------------------| +| $2,515 \text{ MHz} \leq f\_offset < 2,715 \text{ MHz}$ | $P - 53 \text{ dB}$ | 30 kHz | +| $2,715 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | | 30 kHz | +| $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | $P - 65 \text{ dB}$ | 30 kHz | +| $4,0 \text{ MHz} \leq f\_offset < 8,0 \text{ MHz}$ | $P - 52 \text{ dB}$ | 1 MHz | +| $8,0 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | $P - 56 \text{ dB}$ | 1 MHz | + +**Table 6.16: Spectrum emission mask values, BS maximum output power $P < 31$ dBm** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|---------------|-----------------------| +| $2,515 \text{ MHz} \leq f\_offset < 2,715 \text{ MHz}$ | -22 dBm | 30 kHz | +| $2,715 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | | 30 kHz | +| $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | -34 dBm | 30 kHz | +| $4,0 \text{ MHz} \leq f\_offset < 8,0 \text{ MHz}$ | -21 dBm | 1 MHz | +| $8,0 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -25 dBm | 1 MHz | + +The normative reference for this requirement is TS 25.105 [1] subclause 6.6.2.1.1 + +#### 6.6.2.1.2.2 1,28 Mcps TDD option + +For regions where this subclause applies, the requirement shall be met by a base station transmitting on a single RF carrier configured in accordance with the manufacturer's specification. Emissions shall not exceed the maximum level specified in tables 6.13A to 16A in the frequency range of $f\_offset$ from 0.815 MHz to $f\_offset_{max}$ from the carrier frequency, where: + +- $\Delta f$ is the separation between the carrier frequency and the nominal -3dB point of the measuring filter closest to the carrier frequency. +- $f\_offset$ is the separation between the carrier frequency and the centre of the measurement filter +- $f\_offset_{max}$ is either 4 MHz or the offset to the operating band edge, whichever is the greater. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measurement filter. + +For BS operating in multiple bands, inside any inter RF bandwidth gaps with $W_{gap} < 8 \text{ MHz}$ , emissions shall not exceed the cumulative sum of the minimum requirements specified at the RF bandwidth edges on each side of the inter RF bandwidth gap. The minimum requirement for RF bandwidth edge is specified in Tables 6.13A to 6.16A below, where in this case. + +- $\Delta f$ equal to 0.8MHz plus the separation between the RF bandwidth edge frequency and the nominal -3dB point of the measuring filter closest to the RF bandwidth edge. +- $f\_offset$ is equal to 0.8MHz plus the separation between the RF bandwidth edge frequency and the center frequency of the measuring filter. +- $f\_offset_{max}$ is either 4 MHz or the offset to the supported operating band edge as defined, whichever is the greater. +- $\Delta f_{max}$ is equal to $f\_offset_{max}$ minus half of the bandwidth of the measurement filter. + +For a multi-carrier BS, the definitions above apply to the lower edge of the carrier transmitted at the lowest carrier frequency and the upper edge of the carrier transmitted at the highest carrier frequency within a specified frequency band. + +**Table 6.13A: Spectrum emission mask values, BS maximum output power $P \geq 34$ dBm for 1,28 Mcps TDD** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------| +| $0.815 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | -20 dBm | 30 kHz | +| $1.015 \text{ MHz} \leq f\_offset < 1.815 \text{ MHz}$ | | 30 kHz | +| $1.815 \text{ MHz} \leq f\_offset < 2.3 \text{ MHz}$ | -28 dBm | 30 kHz | +| $2.3 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -13 dBm | 1 MHz | +| NOTE 1: For BS capable of multi-band operation with inter RF bandwidth gap less than 8MHz, the minimum requirement within the inter RF bandwidth gap is calculated as a cumulative sum of emissions from the two adjacent carriers on each side of the inter RF bandwidth gap. | | | + +**Table 6.14A: Spectrum emission mask values, BS maximum output power $26 \leq P < 34$ dBm for 1,28 Mcps TDD** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------| +| $0.815\text{MHz} \leq f\_offset < 1.015\text{MHz}$ | P-54 dB | 30 kHz | +| $1.015\text{MHz} \leq f\_offset < 1.815\text{MHz}$ | | 30 kHz | +| $1.815\text{MHz} \leq f\_offset < 2.3\text{MHz}$ | P-62 dB | 30 kHz | +| $2.3\text{MHz} \leq f\_offset < f\_offset_{max}$ | P - 47 dB | 1 MHz | +| NOTE 1: For BS capable of multi-band operation with inter RF bandwidth gap less than 8MHz, the minimum requirement within the inter RF bandwidth gap is calculated as a cumulative sum of emissions from the two adjacent carriers on each side of the inter RF bandwidth gap. | | | + +**Table 6.16A: Spectrum emission mask values, BS maximum output power $P < 26$ dBm for 1,28 Mcps TDD** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------| +| $0.815\text{MHz} \leq f\_offset < 1.015\text{MHz}$ | -28 dBm | 30 kHz | +| $1.015\text{MHz} \leq f\_offset < 1.815\text{MHz}$ | | 30 kHz | +| $1.815\text{MHz} \leq f\_offset < 2.3\text{MHz}$ | -36 dBm | 30 kHz | +| $2.3\text{MHz} \leq f\_offset < f\_offset_{max}$ | -21 dBm | 1 MHz | +| NOTE 1: For BS capable of multi-band operation with inter RF bandwidth gap less than 8MHz, the minimum requirement within the inter RF bandwidth gap is calculated as a cumulative sum of emissions from the two adjacent carriers on each side of the inter RF bandwidth gap. | | | + +The normative reference for this requirement is TS 25.105 [1] subclause 6.6.2.1.2. + +#### 6.6.2.1.2.3 7,68 Mcps TDD option + +For regions where this subclause applies, the requirement shall be met by a base station transmitting on a single RF carrier configured in accordance with the manufacturer's specification. Emissions shall not exceed the maximum level specified in tables 6.13B to 6.16B in the frequency range of $f\_offset$ from 5,015 MHz to $f\_offset_{max}$ from the carrier frequency, where: + +- $f\_offset$ is the separation between the carrier frequency and the centre of the measurement filter +- $f\_offset_{max}$ is either 25 MHz or the offset to the UMTS Tx band edge as defined in subclause 4.2, whichever is the greater. + +**Table 6.13B: Spectrum emission mask values, BS maximum output power $P \geq 43$ dBm** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|---------------|-----------------------| +| $5.015\text{MHz} \leq f\_offset < 5.215\text{MHz}$ | -17 dBm | 30 kHz | +| $5.215\text{MHz} \leq f\_offset < 6.015\text{MHz}$ | | 30 kHz | +| $6.015\text{MHz} \leq f\_offset < 6.5\text{MHz}$ | -29 dBm | 30 kHz | +| $6.5\text{MHz} \leq f\_offset < f\_offset_{max}$ | -16 dBm | 1 MHz | +| $5.015\text{MHz} \leq f\_offset < 5.215\text{MHz}$ | -17 dBm | 30 kHz | + +**Table 6.14B: Spectrum emission mask values, BS maximum output power $39 \leq P < 43$ dBm** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|---------------|-----------------------| +| $5.015\text{MHz} \leq f\_offset < 5.215\text{MHz}$ | -17 dBm | 30 kHz | +| $5.215\text{MHz} \leq f\_offset < 6.015\text{MHz}$ | | 30 kHz | +| $6.015\text{MHz} \leq f\_offset < 6.5\text{MHz}$ | -29 dBm | 30 kHz | +| $6.5\text{MHz} \leq f\_offset < 15.5\text{MHz}$ | -16 dBm | 1 MHz | +| $15.5\text{MHz} \leq f\_offset < f\_offset_{max}$ | P - 59 dB | 1 MHz | + +**Table 6.15B: Spectrum emission mask values, BS maximum output power $31 \leq P < 39$ dBm** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|--------------------|-----------------------| +| $5.015\text{MHz} \leq f\_offset < 5.215\text{MHz}$ | $P - 56\text{ dB}$ | 30 kHz | +| $5.215\text{MHz} \leq f\_offset < 6.015\text{MHz}$ | | 30 kHz | +| $6.015\text{MHz} \leq f\_offset < 6.5\text{MHz}$ | $P - 68\text{ dB}$ | 30 kHz | +| $6.5\text{MHz} \leq f\_offset < 15.5\text{MHz}$ | $P - 55\text{ dB}$ | 1 MHz | +| $15.5\text{MHz} \leq f\_offset < f\_offset_{\max}$ | $P - 59\text{ dB}$ | 1 MHz | + +**Table 6.16B: Spectrum emission mask values, BS maximum output power $P < 31$ dBm** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|---------------|-----------------------| +| $5.015\text{MHz} \leq f\_offset < 5.215\text{MHz}$ | -25 dBm | 30 kHz | +| $5.215\text{MHz} \leq f\_offset < 6.015\text{MHz}$ | | 30 kHz | +| $6.015\text{MHz} \leq f\_offset < 6.5\text{MHz}$ | -37 dBm | 30 kHz | +| $6.5\text{MHz} \leq f\_offset < 15.5\text{MHz}$ | -24 dBm | 1 MHz | +| $15.5\text{MHz} \leq f\_offset < f\_offset_{\max}$ | -28 dBm | 1 MHz | + +The normative reference for this requirement is TS 25.105 [1] subclause 6.6.2.1.3. + +### 6.6.2.1.3 Test purpose + +The test purpose is to verify that the BS out of band emissions do not result in undue interference to any other system (wideband, narrowband) operating at frequencies close to the assigned channel bandwidth of the wanted signal. + +This test is independent of the characteristics of possible victim systems and, therefore, complements the tests on occupied bandwidth in 6.6.1 (verifying the spectral concentration of the BS Tx emissions) and on ACLR in 6.6.2.2 (simulating the perception of other UTRA receivers). + +### 6.6.2.1.4 Method of test + +#### 6.6.2.1.4.1 Initial conditions + +For 3,84 Mcps BS supporting 16QAM, the spectrum emission mask requirements shall be tested with the general test set up specified in section 6.6.2.1.4.1.1 and also with the special test set up for 16QAM capable BS specified in section 6.6.2.1.4.1.4. + +For 1,28 Mcps BS supporting 16QAM, the spectrum emission mask requirements shall be tested with the general test set up specified in section 6.6.2.1.4.1.2 and also with the special test set up for 16QAM capable BS specified in section 6.6.2.1.4.1.3. + +#### 6.6.2.1.4.1.0 General test conditions + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested for single carrier: B, M and T; see subclause 5.3. + +RF bandwidth positions to be tested for multi-carrier: $B_{\text{RFBW}}$ , $M_{\text{RFBW}}$ and $T_{\text{RFBW}}$ in single band operation; see subclause 5.3; $B'_{\text{RFBW}}$ , $T'_{\text{RFBW}}$ and $B'_{\text{RFBW}}$ , $T'_{\text{RFBW}}$ in multi-band operation, see subclause 5.3. + +#### 6.6.2.1.4.1.1 3,84 Mcps TDD option - General test set up + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) Set the parameters of the BS transmitted signal according to table 6.17. For MBSFN IMB operation the set of parameters for the transmitted signals is according to IMB test model 1 in subclause 6.1.1.1. + +**Table 6.17: Parameters of the BS transmitted signal for spectrum emission mask testing** + +| Parameter | Value/description | +|---------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | PRAT | +| Number of DPCH in each time slot under test | 9 | +| Power of each DPCH | 1/9 of Base Station output power | +| Data content of DPCH | real life (sufficient irregular) | + +## 6.6.2.1.4.1.2 1,28 Mcps TDD option - General test set up + +- (1) Connect the measuring equipment to the antenna connector under test. +- (2) For a BS declared to be capable of single carrier operation only, set the parameters of the BS transmitted signal according to table 6.17A at manufacturer's declared output power, PRAT. + +For a BS declared to be capable of multi-carrier operation, set the base station to transmit according to Table 6.17A on all carriers configured using the applicable test configuration and corresponding power setting specified in subclause 5.20 and 5.21. + +**Table 6.17A: Parameters of the BS transmitted signal for spectrum emission mask testing for 1,28 Mcps TDD** + +| Parameter | Value/description | +|---------------------------------------------|--------------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i
is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| Number of DPCH in each time slot under test | 8 | +| Power of each DPCH | 1/8 of Base Station output power | +| Data content of DPCH | real life (sufficient irregular) | + +## 6.6.2.1.4.1.3 1,28 Mcps TDD option - Special test set up for 16QAM capable BS + +This test set up only applies for 16QAM capable BS. + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) For a BS declared to be capable of single carrier operation only, set the parameters of the BS transmitted signal according to table 6.17B at manufacturer's declared output power, PRAT. + +For a BS declared to be capable of multi-carrier operation, set the base station to transmit according to Table 6.17B on all carriers configured using the applicable test configuration and corresponding power setting specified in subclause 5.20 and 5.21. + +**Table 6.17B: Parameters of the BS transmitted signal for spectrum emission mask testing for 1,28 Mcps TDD - 16QAM capable BS** + +| Parameter | Value/description | +|-------------------------------------------------|--------------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i
is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| HS-PDSCH modulation | 16QAM | +| Number of HS-PDSCH in each time slot under test | 8 | +| Power of each HS-PDSCH | 1/8 of Base Station output power | +| Data content of HS-PDSCH | real life (sufficient irregular) | +| Spreading factor | 16 | + +#### 6.6.2.1.4.1.4 3,84 Mcps TDD option - Special test set up for 16QAM capable BS + +This test set up only applies for 16QAM capable BS. + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) Set the parameters of the BS transmitted signal according to table 6.17C. For MBSFN IMB operation the set of parameters for the transmitted signals is according to IMB test model 2 in subclause 6.1.1.2. + +**Table 6.17C: Parameters of the BS transmitted signal for spectrum emission mask testing - 16QAM capable BS** + +| Parameter | Value/description | +|-------------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | PRAT | +| HS-PDSCH modulation | 16QAM | +| Number of HS-PDSCH in each time slot under test | 9 | +| Power of each HS-PDSCH | 1/9 of Base Station output power | +| Data content of HS-PDSCH | real life (sufficient irregular) | +| Spreading factor | 16 | + +#### 6.6.2.1.4.1.5 7,68 Mcps TDD option - General test set up + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) Set the parameters of the BS transmitted signal according to table 6.17D. + +**Table 6.17D: Parameters of the BS transmitted signal for spectrum emission mask testing** + +| Parameter | Value/description | +|---------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | PRAT | +| Number of DPCH in each time slot under test | 9 | +| Power of each DPCH | 1/9 of Base Station output power | +| Data content of DPCH | real life (sufficient irregular) | + +#### 6.6.2.1.4.1.6 7,68 Mcps TDD option - Special test set up for 16QAM capable BS + +This test set up only applies for 16QAM capable BS. + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) Set the parameters of the BS transmitted signal according to table 6.17E. + +**Table 6.17E: Parameters of the BS transmitted signal for spectrum emission mask testing - 16QAM capable BS** + +| Parameter | Value/description | +|-------------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | PRAT | +| HS-PDSCH modulation | 16QAM | +| Number of HS-PDSCH in each time slot under test | 9 | +| Power of each HS-PDSCH | 1/9 of Base Station output power | +| Data content of HS-PDSCH | real life (sufficient irregular) | +| Spreading factor | 32 | + +#### 6.6.2.1.4.2 Procedure + +##### 6.6.2.1.4.2.1 3,84 Mcps TDD option + +Measure the power of the BS spectrum emissions by applying measurement filters with bandwidths as specified in the relevant table in subclause 6.6.2.1.2.1. The characteristic of the filters shall be approximately Gaussian (typical spectrum analyzer filters). The centre frequency of the filter shall be stepped in contiguous steps over the ranges of frequency offsets $f\_offset$ as given in the tables. The step width shall be equal to the respective measurement bandwidth. The time duration of each step shall be sufficiently long to capture one active time slot. + +For frequency offsets of the measurement filter centre frequency in the range $4,0 \text{ MHz} \leq f\_offset < f\_offset_{max}$ , the measurement shall be performed by applying filters with measurement bandwidth of 50 kHz or less and integrating the measured results over the nominal measurement bandwidth 1 MHz specified in the tables in subclause 6.6.2.1.2.1. + +##### 6.6.2.1.4.2.2 1,28 Mcps TDD option + +- 1) Measure the power of the BS spectrum emissions by applying measurement filters with bandwidths as specified in the relevant table in subclause 6.6.2.1.2.2. The characteristic of the filters shall be approximately Gaussian (typical spectrum analyzer filters). The centre frequency of the filter shall be stepped in contiguous steps over the ranges of frequency offsets $f\_offset$ as given in the tables. The step width shall be equal to the respective measurement bandwidth. The time duration of each step shall be sufficiently long to capture one active time slot. +- 2) The measurement shall be performed by applying filters with measurement bandwidth of 50 kHz or less and integrating the measured results over the nominal measurement bandwidth 1 MHz specified in the tables in subclause 6.6.2.1.2.2 when the measurement bandwidth is 1MHz. + +In addition, for a multi-band capable BS, the following steps shall apply: + +- 3) For multi-band capable BS and single band tests, repeat the steps above per involved band with no carrier activated in the other band. +- 4) For multi-band capable BS with separate antenna connector, the antenna connector not being under test in case of single-band or multi-band test shall be terminated. + +##### 6.6.2.1.4.2.3 1,28 Mcps TDD option - 16QAM capable BS + +The same procedure specified in 6.6.2.1.4.2.2 applies to 1,28 Mcps TDD option BS supporting 16QAM. + +#### 6.6.2.1.4.2.4 3,84 Mcps TDD option - 16QAM capable BS + +The same procedure specified in 6.6.2.1.4.2.1 applies to 3,84 Mcps TDD option BS supporting 16QAM. + +#### 6.6.2.1.4.2.5 7,68 Mcps TDD option + +Measure the power of the BS spectrum emissions by applying measurement filters with bandwidths as specified in the relevant table in subclause 6.6.2.1.2.3. The characteristic of the filters shall be approximately Gaussian (typical spectrum analyzer filters). The centre frequency of the filter shall be stepped in contiguous steps over the ranges of frequency offsets $f\_offset$ as given in the tables. The step width shall be equal to the respective measurement bandwidth. The time duration of each step shall be sufficiently long to capture one active time slot. + +For frequency offsets of the measurement filter centre frequency in the range $6,5 \text{ MHz} \leq f\_offset < f\_offset_{max}$ , the measurement shall be performed by applying filters with measurement bandwidth of 50 kHz or less and integrating the measured results over the nominal measurement bandwidth 1 MHz specified in the tables in subclause 6.6.2.1.2.3. + +#### 6.6.2.1.4.2.6 7,68 Mcps TDD option - 16QAM capable BS + +The same procedure specified in 6.6.2.1.4.2.5 applies to 7,68 Mcps TDD option BS supporting 16QAM. + +### 6.6.2.1.5 Test Requirements + +NOTE: If the Test Requirements below differ from the Minimum Requirements, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +#### 6.6.2.1.5.1 3,84 Mcps TDD option + +The spectrum emissions measured according to subclause 6.6.2.1.4.2.1 shall not exceed the maximum level specified in tables 6.18 to 6.21 for the appropriate BS maximum output power + +**Table 6.18: Test Requirements for spectrum emission mask values, +BS maximum output power $P \geq 43 \text{ dBm}$** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|---------------|-----------------------| +| $2,515 \text{ MHz} \leq f\_offset < 2,715 \text{ MHz}$ | -12,5 dBm | 30 kHz | +| $2,715 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | | 30 kHz | +| $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | -24,5 dBm | 30 kHz | +| $4,0 \text{ MHz} \leq f\_offset < 8,0 \text{ MHz}$ | -11,5 dBm | 1 MHz | +| $8,0 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -11,5 dBm | 1 MHz | + +**Table 6.19: Test Requirements for spectrum emission mask values, +BS maximum output power $39 \leq P < 43 \text{ dBm}$** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|-----------------------|-----------------------| +| $2,515 \text{ MHz} \leq f\_offset < 2,715 \text{ MHz}$ | -12,5 dBm | 30 kHz | +| $2,715 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | | 30 kHz | +| $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | -24,5 dBm | 30 kHz | +| $4,0 \text{ MHz} \leq f\_offset < 8,0 \text{ MHz}$ | -11,5 dBm | 1 MHz | +| $8,0 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | $P - 54,5 \text{ dB}$ | 1 MHz | + +**Table 6.20: Test Requirements for spectrum emission mask values, +BS maximum output power $31 \leq P < 39 \text{ dBm}$** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|-----------------------|-----------------------| +| $2,515 \text{ MHz} \leq f\_offset < 2,715 \text{ MHz}$ | $P - 51,5 \text{ dB}$ | 30 kHz | +| $2,715 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | | 30 kHz | +| $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | $P - 63,5 \text{ dB}$ | 30 kHz | +| $4,0 \text{ MHz} \leq f\_offset < 8,0 \text{ MHz}$ | $P - 50,5 \text{ dB}$ | 1 MHz | +| $8,0 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | $P - 54,5 \text{ dB}$ | 1 MHz | + +**Table 6.21: Test Requirements for spectrum emission mask values, BS maximum output power $P < 31$ dBm** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|---------------|-----------------------| +| $2,515 \text{ MHz} \leq f\_offset < 2,715 \text{ MHz}$ | -20,5 dBm | 30 kHz | +| $2,715 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | | 30 kHz | +| $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | -32,5 dBm | 30 kHz | +| $4,0 \text{ MHz} \leq f\_offset < 8,0 \text{ MHz}$ | -19,5 dBm | 1 MHz | +| $8,0 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -23,5 dBm | 1 MHz | + +#### 6.6.2.1.5.2 1,28 Mcps TDD option + +The spectrum emissions measured according to subclause 6.6.2.1.4.2.2 shall be within the mask defined in the table 6.18A to 6.21A. + +**Table 6.18A: Test requirements for spectrum emission mask values, BS maximum output power $P \geq 34$ dBm for 1,28 Mcps TDD** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|---------------|-----------------------| +| $0.815 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | -18.5 dBm | 30 kHz | +| $1.015 \text{ MHz} \leq f\_offset < 1.815 \text{ MHz}$ | | 30 kHz | +| $1.815 \text{ MHz} \leq f\_offset < 2.3 \text{ MHz}$ | -26.5 dBm | 30 kHz | +| $2.3 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -11.5 dBm | 1 MHz | + +NOTE 1: For BS capable of multi-band operation with inter RF bandwidth gap less than 8MHz, the test requirement within the inter RF bandwidth gap is calculated as a cumulative sum of emissions from the two adjacent carriers on each side of the inter RF bandwidth gap. + +**Table 6.19A: Test requirements for spectrum emission mask values, BS maximum output power $26 \leq P < 34$ dBm for 1,28 Mcps TDD** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|-----------------------|-----------------------| +| $0.815 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | $P - 52.5 \text{ dB}$ | 30 kHz | +| $1.015 \text{ MHz} \leq f\_offset < 1.815 \text{ MHz}$ | | 30 kHz | +| $1.815 \text{ MHz} \leq f\_offset < 2.3 \text{ MHz}$ | $P - 60.5 \text{ dB}$ | 30 kHz | +| $2.3 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | $P - 45.5 \text{ dB}$ | 1 MHz | + +NOTE 1: For BS capable of multi-band operation with inter RF bandwidth gap less than 8MHz, the test requirement within the inter RF bandwidth gap is calculated as a cumulative sum of emissions from the two adjacent carriers on each side of the inter RF bandwidth gap. + +**Table 6.21A: Test requirements for spectrum emission mask values, BS maximum output power $P < 26$ dBm for 1,28 Mcps TDD** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|---------------|-----------------------| +| $0.815 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$ | -26.5 dBm | 30 kHz | +| $1.015 \text{ MHz} \leq f\_offset < 1.815 \text{ MHz}$ | | 30 kHz | +| $1.815 \text{ MHz} \leq f\_offset < 2.3 \text{ MHz}$ | -34.5 dBm | 30 kHz | +| $2.3 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | -19.5 dBm | 1 MHz | + +NOTE 1: For BS capable of multi-band operation with inter RF bandwidth gap less than 8MHz, the test requirement within the inter RF bandwidth gap is calculated as a cumulative sum of emissions from the two adjacent carriers on each side of the inter RF bandwidth gap. + +#### 6.6.2.1.5.3 1,28 Mcps TDD option - 16QAM capable BS + +The spectrum emissions measured according to subclause 6.6.2.1.4.2.3 shall be within the mask defined in the table 6.18A to 6.21A in section 6.6.2.1.5.2. + +#### 6.6.2.1.5.4 3,84 Mcps TDD option - 16QAM capable BS + +The spectrum emissions measured according to subclause 6.6.2.1.4.2.4 shall be within the mask defined in the table 6.18 to 6.21 in section 6.6.2.1.5.1. + +#### 6.6.2.1.5.5 7,68 Mcps TDD option + +The spectrum emissions measured according to subclause 6.6.2.1.4.2.5 shall not exceed the maximum level specified in tables 6.18B to 6.21B for the appropriate BS maximum output power + +**Table 6.18B: Test Requirements for spectrum emission mask values, +BS maximum output power $P \geq 43$ dBm** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|---------------|-----------------------| +| $5.015\text{MHz} \leq f\_offset < 5.215\text{MHz}$ | -15.5 dBm | 30 kHz | +| $5.215\text{MHz} \leq f\_offset < 6.015\text{MHz}$ | | 30 kHz | +| $6.015\text{MHz} \leq f\_offset < 6.5\text{MHz}$ | -27.5 dBm | 30 kHz | +| $6.5\text{MHz} \leq f\_offset < f\_offset_{\max}$ | -14.5 dBm | 1 MHz | +| $15.5\text{MHz} \leq f\_offset < f\_offset_{\max}$ | -14.5 dBm | 1 MHz | + +**Table 6.19B: Test Requirements for spectrum emission mask values, +BS maximum output power $39 \leq P < 43$ dBm** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|---------------|-----------------------| +| $5.015\text{MHz} \leq f\_offset < 5.215\text{MHz}$ | -15.5 dBm | 30 kHz | +| $5.215\text{MHz} \leq f\_offset < 6.015\text{MHz}$ | | 30 kHz | +| $6.015\text{MHz} \leq f\_offset < 6.5\text{MHz}$ | -27.5 dBm | 30 kHz | +| $6.5\text{MHz} \leq f\_offset < 15.5\text{MHz}$ | -14.5 dBm | 1 MHz | +| $15.5\text{MHz} \leq f\_offset < f\_offset_{\max}$ | $P - 57.5$ dB | 1 MHz | + +**Table 6.20B: Test Requirements for spectrum emission mask values, +BS maximum output power $31 \leq P < 39$ dBm** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|---------------|-----------------------| +| $5.015\text{MHz} \leq f\_offset < 5.215\text{MHz}$ | $P - 54.5$ dB | 30 kHz | +| $5.215\text{MHz} \leq f\_offset < 6.015\text{MHz}$ | | 30 kHz | +| $6.015\text{MHz} \leq f\_offset < 6.5\text{MHz}$ | $P - 66.5$ dB | 30 kHz | +| $6.5\text{MHz} \leq f\_offset < 15.5\text{MHz}$ | $P - 53.5$ dB | 1 MHz | +| $15.5\text{MHz} \leq f\_offset < f\_offset_{\max}$ | $P - 57.5$ dB | 1 MHz | + +**Table 6.21B: Test Requirements for spectrum emission mask values, +BS maximum output power $P < 31$ dBm** + +| Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|----------------------------------------------------------------------|---------------|-----------------------| +| $5.015\text{MHz} \leq f\_offset < 5.215\text{MHz}$ | -23.5 dBm | 30 kHz | +| $5.215\text{MHz} \leq f\_offset < 6.015\text{MHz}$ | | 30 kHz | +| $6.015\text{MHz} \leq f\_offset < 6.5\text{MHz}$ | -35.5 dBm | 30 kHz | +| $6.5\text{MHz} \leq f\_offset < 15.5\text{MHz}$ | -22.5 dBm | 1 MHz | +| $15.5\text{MHz} \leq f\_offset < f\_offset_{\max}$ | -26.5 dBm | 1 MHz | + +#### 6.6.2.1.5.6 7,68 Mcps TDD option - 16QAM capable BS + +The spectrum emissions measured according to subclause 6.6.2.1.4.2.6 shall be within the mask defined in the table 6.18B to 6.21B in section 6.6.2.1.5.5. + +## 6.6.2.2 Adjacent Channel Leakage power Ratio (ACLR) + +### 6.6.2.2.1 Definition and applicability + +Adjacent Channel Leakage power Ratio (ACLR) is the ratio of the RRC filtered mean power centered on the assigned channel frequency to the RRC filtered mean power centered on an adjacent channel frequency. The requirements shall apply for all configurations of BS (single carrier or multi-carrier), and for all operating modes foreseen by the manufacturer's specification. + +In some cases the requirement is expressed as adjacent channel leakage power, which is the RRC filtered mean power for the given bandwidth of the victim system at the defined adjacent channel offset. + +### 6.6.2.2.2 Minimum Requirements + +#### 6.6.2.2.2.1 Minimum requirement + +##### 6.6.2.2.2.1.1 3,84 Mcps TDD option + +The ACLR of a single carrier BS or a multi-carrier BS with contiguous carrier frequencies shall be equal to or greater than the limits given in table 6.22. + +**Table 6.22: BS ACLR limits** + +| BS adjacent channel offset below the first or above the last carrier frequency used | ACLR limit | +|-------------------------------------------------------------------------------------|------------| +| 5 MHz | 45 dB | +| 10 MHz | 55 dB | + +If a BS provides multiple non-contiguous single carriers or multiple non-contiguous groups of contiguous single carriers, the above requirements shall be applied individually to the single carriers or group of single carriers. + +The normative reference for this requirement is TS 25.105 [1] subclause 6.6.2.2.1.1. + +##### 6.6.2.2.2.1.2 1,28 Mcps TDD option + +The ACLR of a single carrier BS or a multi-carrier BS with contiguous carrier frequencies shall be equal to or greater than the limits given in Table 6.22A. + +**Table 6.22A: BS ACLR limits for 1,28 Mcps TDD** + +| BS adjacent channel offset below the first or above the last carrier frequency used | ACLR limit | +|-------------------------------------------------------------------------------------|------------| +| 1,6 MHz | 40 dB | +| 3,2 MHz | 45 dB | + +If a BS provides multiple non-contiguous single carriers or multiple non-contiguous groups of contiguous single carriers, the above requirements shall be applied individually to the single carriers or group of single carriers. + +The requirements shall apply outside the Base Station RF bandwidth or maximum radio bandwidth edges whatever the type of transmitter considered (single carrier, multi-carrier). It applies for all transmission modes foreseen by the manufacturer's specification. + +For a BS operating in multiple bands, where multiple bands are mapped onto the same antenna connector, the ACLR requirement also applies for the first adjacent channel inside any inter RF bandwidth gap with a gap size $W_{\text{gap}} \geq 4.8\text{MHz}$ . The ACLR requirement for the second adjacent channel applies inside any inter RF bandwidth gap with a gap size $W_{\text{gap}} \geq 6.4\text{MHz}$ . + +The normative reference for this requirement is TS 25.105 [1] subclause 6.6.2.2.1.2 + +##### 6.6.2.2.2.1.3 7,68 Mcps TDD option + +The ACLR of a single carrier BS or a multi-carrier BS with contiguous carrier frequencies shall be equal to or greater than the limits given in table 6.22B. + +**Table 6.22B: BS ACLR limits** + +| BS adjacent channel offset below the first or above the last carrier frequency used | ACLR limit | +|--------------------------------------------------------------------------------------------|-------------------| +| 10 MHz | 45 dB | +| 20 MHz | 55 dB | + +If a BS provides multiple non-contiguous single carriers or multiple non-contiguous groups of contiguous single carriers, the above requirements shall be applied individually to the single carriers or group of single carriers. + +The normative reference for this requirement is TS 25.105 [1] subclause 6.6.2.2.1.3. + +6.6.2.2.2.2 Void + +6.6.2.2.2.2.1 Void + +6.6.2.2.2.2.1.1 Void + +6.6.2.2.2.2.1.2 Void + +6.6.2.2.2.2.2 Void + +6.6.2.2.2.2.2.1 Void + +6.6.2.2.2.2.2.2 Void + +6.6.2.2.2.2.3 Void + +6.6.2.2.2.2.3.1 Void + +6.6.2.2.2.2.3.2 Void + +6.6.2.2.2.3 Void + +6.6.2.2.2.3.1 Void + +6.6.2.2.2.3.1.1 Void + +6.6.2.2.2.3.1.2 Void + +6.6.2.2.2.3.2 Void + +6.6.2.2.2.3.2.1 Void + +6.6.2.2.2.3.2.2 Void + +6.6.2.2.2.3.3 Void + +6.6.2.2.2.3.3.1 Void + +6.6.2.2.2.3.3.2 Void + +6.6.2.2.3 Test purpose + +The test purpose is to verify the ability of the BS to limit the interference produced by the transmitted signal to other UTRA receivers operating at the first or second adjacent RF channel. + +6.6.2.2.4 Method of test + +6.6.2.2.4.1 Initial conditions + +For 3.84 Mcps BS supporting 16QAM, the ACLR requirements shall be tested with the general test set up specified in section 6.6.2.2.4.1.1 and also with the special test set up for 16QAM capable BS specified in section 6.6.2.2.4.1.4. + +For 1,28 Mcps BS supporting 16QAM, the ALCR requirements shall be tested with the general test set up specified in section 6.6.2.2.4.1.2 and also with the special test set up for 16QAM capable BS specified in section 6.6.2.2.4.1.3. + +For 7,68 Mcps BS supporting 16QAM, the ALCR requirements shall be tested with the general test set up specified in section 6.6.2.2.4.1.5 and also with the special test set up for 16QAM capable BS specified in section 6.6.2.2.4.1.6. + +#### 6.6.2.2.4.1.0 General test conditions + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested for single carrier: B, M and T; see subclause 5.3. + +RF bandwidth positions to be tested for multi-carrier: $B_{RFBW}$ , $M_{RFBW}$ and $T_{RFBW}$ in single band operation; see subclause 5.3; $B_{RFBW\_T}^{RFBW}$ and $B_{RFBW\_T}^{RFBW}$ in multi-band operation, see subclause 5.3. + +#### 6.6.2.2.4.1.1 3,84 Mcps TDD option - General test set up + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) Set the parameters of the BS transmitted signal according to table 6.25. For MBSFN IMB operation the set of parameters for the transmitted signals is according to IMB test model 1 in subclause 6.1.1.1. + +**Table 6.25: Parameters of the BS transmitted signal for ACLR testing** + +| Parameter | Value/description | +|---------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | PRAT | +| Number of DPCH in each time slot under test | 9 | +| Power of each DPCH | 1/9 of Base Station output power | +| Data content of DPCH | Real life (sufficient irregular) | + +#### 6.6.2.2.4.1.2 1,28 Mcps TDD option - General test set up + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) For a BS declared to be capable of single carrier operation only, set the parameters of the BS transmitted signal according to Table 6.25A at manufacturer's declared output power, PRAT. + +For a BS declared to be capable of multi-carrier operation, set the base station to transmit according to Table 6.25A on all carriers configured using the applicable test configuration and corresponding power setting specified in sub-clause 5.20 and 5.21. + +**Table 6.25A: Parameters of the BS transmitted signal for ACLR testing for 1,28 Mcps TDD** + +| Parameter | Value/description | +|---------------------------------------------|--------------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i
is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| Number of DPCH in each time slot under test | 8 | +| Power of each DPCH | 1/8 of Base Station output power | +| Data content of DPCH | real life (sufficient irregular) | + +#### 6.6.2.2.4.1.3 1,28 Mcps TDD option - Special test set up for 16QAM capable BS + +This test set up only applies for 16QAM capable BS. + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) For a BS declared to be capable of single carrier operation only, set the parameters of the BS transmitted signal according to Table 6.25B at manufacturer's declared output power, PRAT. + +For a BS declared to be capable of multi-carrier operation, set the base station to transmit according to Table 6.25B on all carriers configured using the applicable test configuration and corresponding power setting specified in sub-clause 5.20 and 5.21. + +**Table 6.25B: Parameters of the BS transmitted signal for ACLR testing for 1,28 Mcps TDD- 16QAM capable BS** + +| Parameter | Value/description | +|-------------------------------------------------|--------------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i
is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| HS-PDSCH modulation | 16QAM | +| Number of HS-PDSCH in each time slot under test | 8 | +| Power of each HS-PDSCH | 1/8 of Base Station output power | +| Data content of HS-PDSCH | real life (sufficient irregular) | +| Spreading factor | 16 | + +#### 6.6.2.2.4.1.4 3,84 Mcps TDD option - Special test set up for 16QAM capable BS + +This test set up only applies for 16QAM capable BS. + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) Set the parameters of the BS transmitted signal according to table 6.25C. For MBSFN IMB operation the set of parameters for the transmitted signals is according to IMB test model 2 in subclause 6.1.1.2. + +**Table 6.25C: Parameters of the BS transmitted signal for ACLR testing - 16QAM capable BS** + +| Parameter | Value/description | +|-------------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | PRAT | +| HS-PDSCH modulation | 16QAM | +| Number of HS-PDSCH in each time slot under test | 9 | +| Power of each HS-PDSCH | 1/9 of Base Station output power | +| Data content of HS-PDSCH | real life (sufficient irregular) | +| Spreading factor | 16 | + +#### 6.6.2.2.4.1.5 7,68 Mcps TDD option - General test set up + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) Set the parameters of the BS transmitted signal according to table 6.25D. + +**Table 6.25D: Parameters of the BS transmitted signal for ACLR testing** + +| Parameter | Value/description | +|---------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | PRAT | +| Number of DPCH in each time slot under test | 9 | +| Power of each DPCH | 1/9 of Base Station output power | +| Data content of DPCH | Real life (sufficient irregular) | + +## 6.6.2.2.4.1.6 7,68 Mcps TDD option - Special test set up for 16QAM capable BS + +This test set up only applies for 16QAM capable BS. + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) Set the parameters of the BS transmitted signal according to table 6.25E. + +**Table 6.25E: Parameters of the BS transmitted signal for ACLR testing - 16QAM capable BS** + +| Parameter | Value/description | +|-------------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | PRAT | +| HS-PDSCH modulation | 16QAM | +| Number of HS-PDSCH in each time slot under test | 9 | +| Power of each HS-PDSCH | 1/9 of Base Station output power | +| Data content of HS-PDSCH | real life (sufficient irregular) | +| Spreading factor | 32 | + +## 6.6.2.2.4.2 Procedure + +## 6.6.2.2.4.2.1 3,84 Mcps TDD option + +- 1) Measure the RRC filtered mean power centered on the lowest assigned channel frequency over the 2464 active chips of the even time slots TS i (this excludes the guard period). +- 2) Average over TBD time slots. +- 3) Measure the RRC filtered mean power at the first lower adjacent RF channel (center frequency 5 MHz below the lowest assigned channel frequency of the transmitted signal) over the useful part of the burst within the even time slots TS i (this excludes the guard period). +- 4) Average over TBD time slots. +- 5) Calculate the ACLR by the ratio + +$$\text{ACLR} = \text{average acc. to (2)} / \text{average interference power acc. to (4)}.$$ + +- 6) Repeat steps (3), (4) and (5) for the second lower adjacent RF channel (center frequency 10 MHz below the lowest assigned channel frequency of the transmitted signal). +- 7) In case of a multi-carrier Bs, repeat steps (1) and (2) for the highest assigned channel frequency. Otherwise, use the result obtained in step (2) above for further calculation in step (10). + +8) Measure the RRC filtered mean power at the first higher adjacent RF channel (center frequency 5 MHz above the highest assigned channel frequency of the transmitted signal) over the useful part of the burst within the even time slots TS i (this excludes the guard period). + +9) Average over TBD time slots. + +10) Calculate the ACLR by the ratio + +$$\text{ACLR} = \text{average power acc. to (7)} / \text{average interference power acc. to (9)}.$$ + +11) Repeat steps (8) to (10) for the second upper adjacent RF channel (center frequency 10 MHz above the highest assigned channel frequency of the transmitted signal). + +#### 6.6.2.2.4.2.2 1,28 Mcps TDD option + +1) Measure the RRC filtered mean power centered on the lowest assigned channel frequency of a operating band over the 848 active chips of the transmit time slots TS i (this excludes the guard period). + +2) Average over at least one time slot. + +3) Measure the RRC filtered mean power at the first lower adjacent RF channel (center frequency 1,6 MHz below the lowest assigned channel frequency of the transmitted signal) over the useful part of the burst within the transmit time slots TS i (this excludes the guard period). + +4) Average over at least one time slot. + +5) Calculate the ACLR by the ratio: + +$$\text{ACLR} = \text{average power acc. to (2)} / \text{average interference power acc. to (4)}.$$ + +6) Repeat steps (3), (4) and (5) for the second lower adjacent RF channel (center frequency 3,2 MHz below the lowest assigned channel frequency of the transmitted signal) and also for the first and second upper adjacent RF channel (center frequency 1,6 MHz and 3,2 MHz above the assigned channel frequency of the transmitted signal, respectively). + +7) In case of a multi-carrier BS, repeat steps (1) and 2 for the highest assigned channel frequency. Otherwise, use the result obtained in step (2) above for further calculation in step (10). + +8) Measure the RRC filtered mean power at the first higher adjacent RF channel (center frequency 1,6 MHz above the highest assigned channel frequency of the transmitted signal) over the useful part of the burst within the transmit time slots TS i (this excludes the guard period). + +9) Average over at least one time slot. + +10) Calculate the ACLR by the ratio + +$$\text{ACLR} = \text{average power acc. to (7)} / \text{average interference power acc. to (9)}.$$ + +11) Repeat steps (8) to (10) for the second upper adjacent RF channel (center frequency 3,2 MHz above the highest assigned channel frequency of the transmitted signal). + +In addition, for a multi-band capable BS, the following steps shall apply: + +12) For multi-band capable BS and single band tests, repeat the steps above per involved band with no carrier activated in the other band. + +13) For multi-band capable BS with separate antenna connector, the antenna connector not being under test in case of single-band or multi-band test shall be terminated. + +#### 6.6.2.2.4.2.3 1,28 Mcps TDD option - 16QAM capable BS + +The same procedure specified in 6.6.2.2.4.2.2 applies to 1,28 Mcps TDD option BS supporting 16QAM. + +#### 6.6.2.2.4.2.4 3,84 Mcps TDD option - 16QAM capable BS + +The same procedure specified in 6.6.2.2.4.2.1 applies to 3,84 Mcps TDD option BS supporting 16QAM. + +#### 6.6.2.2.4.2.5 7,68 Mcps TDD option + +- 1) Measure the RRC filtered mean power centered on the lowest assigned channel frequency over the 4928 active chips of the even time slots TS i (this excludes the guard period). +- 2) Average over TBD time slots. +- 3) Measure the RRC filtered mean power at the first lower adjacent RF channel (center frequency 10 MHz below the lowest assigned channel frequency of the transmitted signal) over the useful part of the burst within the even time slots TS i (this excludes the guard period). +- 4) Average over TBD time slots. +- 5) Calculate the ACLR by the ratio + +$$\text{ACLR} = \text{average acc. to (2)} / \text{average interference power acc. to (4)}.$$ + +- 6) Repeat steps (3), (4) and (5) for the second lower adjacent RF channel (center frequency 20 MHz below the lowest assigned channel frequency of the transmitted signal). + - 7) In case of a multi-carrier Bs, repeat steps (1) and (2) for the highest assigned channel frequency. Otherwise, use the result obtained in step (2) above for further calculation in step (10). + - 8) Measure the RRC filtered mean power at the first higher adjacent RF channel (center frequency 10 MHz above the highest assigned channel frequency of the transmitted signal) over the useful part of the burst within the even time slots TS i (this excludes the guard period). + - 9) Average over TBD time slots. + - 10) Calculate the ACLR by the ratio +- $$\text{ACLR} = \text{average power acc. to (7)} / \text{average interference power acc. to (9)}.$$ +- 11) Repeat steps (8) to (10) for the second upper adjacent RF channel (center frequency 20 MHz above the highest assigned channel frequency of the transmitted signal). + +#### 6.6.2.2.4.2.6 7,68 Mcps TDD option - 16QAM capable BS + +The same procedure specified in 6.6.2.2.4.2.5 applies to 7,68 Mcps TDD option BS supporting 16QAM. + +### 6.6.2.2.5 Test Requirements + +NOTE: If the Test Requirements below differ from the Minimum Requirements, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +#### 6.6.2.2.5.1 3,84 Mcps TDD option + +The ACLR calculated in steps (5) and (10) of subclause 6.6.2.2.4.2.1 shall be equal or greater than the limits given in table 6.26. In case the equipment is tested against the requirements defined for operation in the same geographic area or co-sited with unsynchronised TDD or FDD on adjacent channels, the adjacent channel leakage power measured according to steps (4) and (9) of subclause 6.6.2.2.4.2.1 shall not exceed the maximum levels specified in table 6.27, 6.27A, 6.28 or 6.28A, respectively. + +**Table 6.26: BS ACLR Test Requirements** + +| BS adjacent channel offset below the first or above the last carrier frequency used | ACLR limit | +|-------------------------------------------------------------------------------------|------------| +| 5 MHz | 44,2 dB | +| 10 MHz | 54,2 dB | + +#### 6.6.2.2.5.2 1,28 Mcps TDD option + +The ACLR calculated in steps (5) and (10) of subclause 6.6.2.2.4.2.2 shall be equal or greater than the limits given in table 6.26A. In case the equipment is tested against the requirements defined for operation in the same geographic area or co-sited with unsynchronised TDD or FDD on adjacent channels, the adjacent channel leakage power measured + +according to steps (3) and (4) of subclause 6.6.2.2.4.2.2 shall not exceed the maximum levels specified in tables 6.27B, 6.27C, 6.27D, 6.28B, 6.28C or 6.28D, respectively. + +**Table 6.26A: BS ACLR Test Requirements (1,28 Mcps option)** + +| BS adjacent channel offset below the first or above the last carrier frequency used | ACLR limit | +|-------------------------------------------------------------------------------------|------------| +| 1,6 MHz | 39.2 dB | +| 3,2 MHz | 44.2 dB | + +The requirements shall apply outside the Base Station RF bandwidth or maximum radio bandwidth edges whatever the type of transmitter considered (single carrier, multi-carrier). It applies for all transmission modes foreseen by the manufacturer's specification. + +For a BS operating in multiple bands, where multiple bands are mapped onto the same antenna connector, the ACLR requirement also applies for the first adjacent channel inside any inter RF bandwidth gap with a gap size $W_{\text{gap}} \geq 4.8\text{MHz}$ . The ACLR requirement for the second adjacent channel applies inside any inter RF bandwidth gap with a gap size $W_{\text{gap}} \geq 6.4\text{MHz}$ . + +#### 6.6.2.2.5.3 1,28 Mcps TDD option - 16QAM capable BS + +The same test requirements specified in section 6.6.2.2.5.2 apply to 1,28 Mcps TDD option BS supporting 16QAM. + +#### 6.6.2.2.5.4 3,84 Mcps TDD option - 16QAM capable BS + +The same test requirements specified in section 6.6.2.2.5.1 apply to 3,84 Mcps TDD option BS supporting 16QAM. + +#### 6.6.2.2.5.5 7,68 Mcps TDD option + +The ACLR calculated in steps (5) and (10) of subclause 6.6.2.2.4.2.5 shall be equal or greater than the limits given in table 6.26B. In case the equipment is tested against the requirements defined for operation in the same geographic area or co-sited with unsynchronised TDD or FDD on adjacent channels, the adjacent channel leakage power measured according to steps (4) and (9) of subclause 6.6.2.2.4.2.5 shall not exceed the maximum levels specified in table 6.27E, 6.27F, 6.27G, 6.28E, 6.28F or 6.28G, respectively. + +**Table 6.26B: BS ACLR Test Requirements** + +| BS adjacent channel offset below the first or above the last carrier frequency used | ACLR limit | +|-------------------------------------------------------------------------------------|------------| +| 10 MHz | 44,2 dB | +| 20 MHz | 54,2 dB | + +#### 6.6.2.2.5.6 7,68 Mcps TDD option - 16QAM capable BS + +The same test requirements specified in section 6.6.2.2.5.5 apply to 7,68 Mcps TDD option BS supporting 16QAM. + +### 6.6.3 Spurious emissions + +#### 6.6.3.1 Definition and applicability + +Spurious emissions are emissions which are caused by unwanted transmitter effects such as harmonics emission, parasitic emission, intermodulation products and frequency conversion products, but exclude out of band emissions. This is measured at the base station antenna connector. + +The requirements shall apply whatever the type of transmitter considered (single carrier or multiple carrier). It applies for all transmission modes foreseen by the manufacturer's specification. + +For 3,84 Mcps TDD option, either requirement (except 6.6.3.2.6) applies at frequencies within the specified frequency ranges which are more than 12,5 MHz under the first carrier frequency used or more than 12,5 MHz above the last carrier frequency used. + +For 1,28 Mcps TDD option, the mandatory spurious emission requirement applies from 9kHz to 12.75GHz, excluding the frequency ranges from 4 MHz below the lowest frequency of each supported operating band to 4 MHz above the highest frequency of each operating band. For BS capable of multi-band operation where multiple bands are mapped on + +the same antenna connector, this exclusion applies for each supported operating bands. For BS capable of multi-band operation where multiple bands are mapped on separate antenna connectors, the single-band requirements apply and the multi-band exclusions and provisions are not applicable. + +For 7.68 Mcps TDD option, either requirement (except 6.6.3.2.6) applies at frequencies within the specified frequency ranges which are more than 25 MHz under the first carrier frequency used or more than 25 MHz above the last carrier frequency used. + +Unless otherwise stated, all requirements are measured as mean power. + +### 6.6.3.2 Minimum Requirements + +#### 6.6.3.2.1 Mandatory requirements + +The requirements of either subclause 6.6.3.2.1.1 or subclause 6.6.3.2.1.2 shall apply. + +##### 6.6.3.2.1.1 Spurious emissions (Category A) + +The following requirements shall be met in cases where Category A limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [6], are applied. + +###### 6.6.3.2.1.1.1 3,84 Mcps TDD option + +The power of any spurious emission shall not exceed the maximum level given in Table 6.29. + +**Table 6.29: BS Mandatory spurious emissions limits, Category A** + +| Band | Maximum level | Measurement bandwidth | Notes | | +|--------------------------------------------------------------|---------------|-----------------------|--------|--| +| 9 kHz - 150 kHz | -13 dBm | 1 kHz | Note 1 | | +| 150 kHz - 30 MHz | | 10 kHz | Note 1 | | +| 30 MHz - 1 GHz | | 100 kHz | Note 1 | | +| 1 GHz - 12,75 GHz | | 1 MHz | Note 2 | | +| NOTE 1: Bandwidth as in ITU-R SM.329 [6], s4.1 | | | | | +| NOTE 2: Upper frequency as in ITU-R SM.329 [6], s2.5 table 1 | | | | | + +The normative reference for this requirement is TS 25.105 [1] subclause 6.6.3.1.1.1.1. + +###### 6.6.3.2.1.1.2 1,28 Mcps TDD option + +The power of any spurious emission shall not exceed the maximum level given in Table 6.29A. + +**Table 6.29A: BS Mandatory spurious emissions limits, Category A** + +| Band | Maximum level | Measurement bandwidth | Notes | | +|--------------------------------------------------------------|---------------|-----------------------|--------|--| +| 9 kHz - 150 kHz | -13 dBm | 1 kHz | Note 1 | | +| 150 kHz - 30 MHz | | 10 kHz | Note 1 | | +| 30 MHz - 1 GHz | | 100 kHz | Note 1 | | +| 1 GHz - 12,75 GHz | | 1 MHz | Note 2 | | +| NOTE 1: Bandwidth as in ITU-R SM.329 [6], s4.1 | | | | | +| NOTE 2: Upper frequency as in ITU-R SM.329 [6], s2.5 table 1 | | | | | + +The normative reference for this requirement is TS 25.105 [1] subclause 6.6.3.1.1.1.2. + +###### 6.6.3.2.1.1.3 7,68 Mcps TDD option + +The power of any spurious emission shall not exceed the maximum level given in Table 6.29B. + +**Table 6.29B: BS Mandatory spurious emissions limits, Category A** + +| Band | Maximum level | Measurement bandwidth | Notes | | +|--------------------------------------------------------------|---------------|-----------------------|--------|--| +| 9 kHz - 150 kHz | -13 dBm | 1 kHz | Note 1 | | +| 150 kHz - 30 MHz | | 10 kHz | Note 1 | | +| 30 MHz - 1 GHz | | 100 kHz | Note 1 | | +| 1 GHz - 12,75 GHz | | 1 MHz | Note 2 | | +| NOTE 1: Bandwidth as in ITU-R SM.329 [6], s4.1 | | | | | +| NOTE 2: Upper frequency as in ITU-R SM.329 [6], s2.5 table 1 | | | | | + +The normative reference for this requirement is TS 25.105 [1] subclause 6.6.3.1.1.1.3. + +#### 6.6.3.2.1.2 Spurious emissions (Category B) + +The following requirements shall be met in cases where Category B limits for spurious emissions, as defined in ITU-R Recommendation SM.329-9 [6], are applied. + +##### 6.6.3.2.1.2.1 3,84 Mcps TDD option + +The power of any spurious emission shall not exceed the maximum levels given in Table 6.30. + +**Table 6.30: BS Mandatory spurious emissions limits, Category B** + +| Band | Maximum level | Measurement bandwidth | Notes | +|------------------------------------------------------------------------------------------------------|---------------|-----------------------|--------| +| 9 kHz - 150 kHz | -36 dBm | 1 kHz | Note 1 | +| 150 kHz - 30 MHz | -36 dBm | 10 kHz | Note 1 | +| 30 MHz - 1 GHz | -36 dBm | 100 kHz | Note 1 | +| 1 GHz
-
Fl - 10 MHz | -30 dBm | 1 MHz | Note 1 | +| Fl -10 MHz-
Fu +10 MHz | -15 dBm | 1 MHz | Note 2 | +| Fu + 10 MHz
-
12,75 GHz | -30 dBm | 1 MHz | Note 3 | +| NOTE 1: Bandwidth as in ITU-R SM.329 [6], s4.1 | | | | +| NOTE 2: Specification in accordance with ITU-R SM.329 [6], s4.3 and Annex 7 | | | | +| NOTE 3: Bandwidth as in ITU-R SM.329 [6], s4.1. Upper frequency as in ITU-R SM.329 [6], s2.5 table 1 | | | | + +Fl: Lower frequency of the band in which TDD operates + +Fu: Upper frequency of the band in which TDD operates + +The normative reference for this requirement is TS 25.105 [1] subclause 6.6.3.1.2.1.1. + +##### 6.6.3.2.1.2.2 1,28 Mcps TDD option + +The power of any spurious emission shall not exceed the maximum levels given in Table 6.30A. + +**Table 6.30A: BS Mandatory spurious emissions limits, Category B for 1,28 Mcps TDD** + +| Band | Maximum Level | Measurement Bandwidth | Notes | +|--------------------------------------------------------------------------------------------------|---------------|-----------------------|--------| +| 9kHz - 150kHz | -36 dBm | 1 kHz | Note 1 | +| 150kHz - 30MHz | -36 dBm | 10 kHz | Note 1 | +| 30MHz - 1GHz | -36 dBm | 100 kHz | Note 1 | +| 1GHz
↔
Fl - 10 MHz | -30 dBm | 1 MHz | Note 1 | +| Fl - 10 MHz ↔ Fu + 10 MHz | -15 dBm | 1 MHz | Note 2 | +| Fu + 10 MHz
↔
12,75 GHz | -30 dBm | 1 MHz | Note 3 | +| NOTE 1: Bandwidth as in ITU-R SM.329 [6], s4.1 | | | | +| NOTE 2: Specification in accordance with ITU-R SM.329 [6], s4.1 | | | | +| NOTE 3: Bandwidth as in ITU-R SM.329-9, s4.1. Upper frequency as in ITU-R SM.329-9, s2.5 table 1 | | | | + +Fl: Lower frequency of the band in which TDD operates + +Fu: Upper frequency of the band in which TDD operates + +The reference for this requirement is TS 25.105 subclause 6.6.3.1.2.1.2. + +#### 6.6.3.2.1.2.3 7,68 Mcps TDD option + +The power of any spurious emission shall not exceed the maximum levels given in Table 6.30B. + +**Table 6.30B: BS Mandatory spurious emissions limits, Category B** + +| Band | Maximum Level | Measurement Bandwidth | Notes | +|------------------------------------------------------------------------------------------------------------------|---------------|-----------------------|--------| +| 9kHz - 150kHz | -36 dBm | 1 kHz | Note 1 | +| 150kHz - 30MHz | -36 dBm | 10 kHz | Note 1 | +| 30MHz - 1GHz | -36 dBm | 100 kHz | Note 1 | +| 1GHz
↔
Fl - 10 MHz | -30 dBm | 1 MHz | Note 1 | +| Fl - 10 MHz ↔ Fu + 10 MHz | -15 dBm | 1 MHz | Note 2 | +| Fu + 10 MHz
↔
12,75 GHz | -30 dBm | 1 MHz | Note 3 | +| NOTE 1: Bandwidth as in ITU-R SM.329 [6], s4.1 | | | | +| NOTE 2: Specification in accordance with ITU-R SM.329 [6], s4.3 and Annex 7 | | | | +| NOTE 3: Bandwidth as in ITU-R SM.329 [6], s4.3 and Annex 7. Upper frequency as in ITU-R SM.329 [6], s2.5 table 1 | | | | + +Fl: Lower frequency of the band in which TDD operates + +Fu: Upper frequency of the band in which TDD operates + +The normative reference for this requirement is TS 25.105 [1] subclause 6.6.3.1.2.1.3. + +#### 6.6.3.2.2 Co-existence with GSM, DCS, UTRA and/or E-UTRA + +##### 6.6.3.2.2.1 Operation in the same geographic area + +These requirements may be applied for the protection of other UE and/or BS receivers when GSM DCS, UTRA and/or E-UTRA BS are operating in other frequency bands in the same geographical area with a UTRA TDD BS. + +The power of any spurious emission shall not exceed the maximum level given in Table 6.31. + +For BS capable of multi-band operation, the exclusions and conditions in the Note column of Table 6.31 apply for each supported operating band. For BS capable of multi-band operation where multiple bands are mapped on separate + +antenna connectors, the exclusions and conditions in the Note column of Table 6.31 apply for the operating band supported at that antenna connector. + +**Table 6.31: BS Spurious emissions limits for UTRA TDD BS in geographic coverage area of systems operating in other frequency bands** + +| System type operating in the same geographical area | Band | Maximum level | Measurement bandwidth | Note | +|--------------------------------------------------------|-----------------------|---------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------| +| GSM900 | 876 MHz - 915 MHz | -61 dBm | 100 kHz | | +| | 921 MHz - 960 MHz | -57 dBm | 100 kHz | | +| DCS1800 | 1710 MHz - 1785 MHz | -61 dBm | 100 kHz | This requirement does not apply to UTRA TDD operating in Band b and c. For UTRA TDD BS operating in Band f, it applies for 1710 - 1755 MHz | +| | 1805 MHz - 1880 MHz | -47 dBm | 100 kHz | This requirement does not apply to UTRA TDD operating in Band b and c. For UTRA TDD BS operating in Band f, it applies for 1805 - 1850 MHz | +| GSM850 or CDMA850 | 824 - 849 MHz | -61 dBm | 100 kHz | | +| | 869 - 894 MHz | -57 dBm | 100 kHz | | +| WA BS UTRA FDD Band I or E-UTRA Band 1 | 1920 - 1980 MHz | -43 dBm (*) | 3,84 MHz | | +| | 2110 - 2170 MHz | -52 dBm | 1 MHz | | +| WA BS UTRA FDD Band III or E-UTRA Band 3 | 1710 - 1785 MHz | -43 dBm | 3,84 MHz | For UTRA TDD BS operating in Band f, it applies for 1710- 1755 MHz | +| | 1805 - 1880 MHz | -52 dBm | 1 MHz | For UTRA TDD BS operating in Band f, it applies for 1805- 1850 MHz | +| WA BS UTRA FDD Band V or E-UTRA Band 5 | 824 - 849 MHz | -43 dBm | 3,84 MHz | | +| | 869 - 894 MHz | -52 dBm | 1 MHz | | +| WA BS UTRA FDD Band VII or E-UTRA Band 7 | 2500 - 2570 MHz | -43 dBm(**) | 3,84 MHz | | +| | 2620 - 2690 MHz | -52 dBm | 1 MHz | | +| WA BS UTRA FDD Band VI or XIX, E-UTRA Band 6, 18 or 19 | 815-850 MHz | -43 dBm† | 3,84 MHz | Applicable in Japan | +| | 860-895 MHz | -52 dBm† | 1 MHz | Applicable in Japan | +| WA BS UTRA FDD Band XI or XXI or E-UTRA Band 11 or 21 | 1427.9MHz - 1452.9MHz | -43 dBm†† | 3,84 MHz | Applicable in Japan | +| | 1475.9MHz - 1500.9MHz | -52 dBm†† | 1 MHz | Applicable in Japan | +| WA BS UTRA FDD Band IX or E-UTRA Band 9 | 1749.9-1784.9 MHz | -43 dBm† | 3,84 MHz | Applicable in Japan | +| | 1844.9-1879.9 MHz | -52 dBm† | 1 MHz | Applicable in Japan | +| LA BS UTRA FDD Band I or E-UTRA Band 1 | 1920 - 1980 MHz | -40 dBm (*) | 3,84 MHz | | +| | 2110 - 2170 MHz | -52 dBm | 1 MHz | | +| LA BS UTRA FDD Band III or E-UTRA Band 3 | 1710 - 1785 MHz | -40 dBm (*) | 3,84 MHz | For UTRA TDD BS operating in Band f, it applies for 1710- 1755 MHz | +| | 1805 - 1880 MHz | -52 dBm | 1 MHz | For UTRA TDD BS operating in Band f, it applies for 1805- 1850 MHz | +| LA BS UTRA FDD Band V | 824 - 849 MHz | -40 dBm (*) | 3,84 MHz | | + +| | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-------------|----------|--| +| or
E-UTRA Band 5 | 869 - 894 MHz | -52 dBm | 1 MHz | | +| LA BS UTRA FDD Band VII
or
E-UTRA Band 7 | 2500 - 2570 MHz | -40 dBm(**) | 3.84 MHz | | +|

NOTE 1: The co-existence requirements do not apply for the 10 MHz frequency range immediately outside the operating band (see section 4.2). Emission limits for this excluded frequency range may be covered by local or regional requirements.

NOTE 2: The requirements for Wide Area BS for co-existence with UTRA FDD and/or E-UTRA FDD and for co-existence between unsynchronised TDD base stations are based on a coupling loss of 67dB between the TDD and FDD base stations. The scenarios leading to these requirements are addressed in TR 25.942 [9].

NOTE 3: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications.

| | | | | + +The normative reference for this requirement is TS 25.105 [1] subclause 6.6.3.2.1.1. + +#### 6.6.3.2.2.2 Co-located base stations + +These requirements may be applied for the protection of other BS receivers when GSM, DCS, E-UTRA and/or UTRA BS are co-located with a UTRA TDD BS. + +The power of any spurious emission shall not exceed the maximum level given in table 6.32. + +For BS capable of multi-band operation, the exclusions and conditions in the Note column of Table 6.32 apply for each supported operating band. For BS capable of multi-band operation where multiple bands are mapped on separate antenna connectors, the exclusions and conditions in the Note column of Table 6.32 apply for the operating band supported at that antenna connector. + +**Table 6.32: BS Spurious emissions limits for Wide Area BS co-located with another BS** + +| System type operating in the same geographical area | Band | Maximum level | Measurement bandwidth | Note | +|-----------------------------------------------------|-------------------|---------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------| +| Macro GSM900 | 876 MHz - 915 MHz | -98 dBm | 100 kHz | | +| Macro DCS1800 | 1710 - 1785 MHz | -98 dBm | 100 kHz | This requirement does not apply to UTRA TDD operating in Band b and c. For UTRA TDD BS operating in Band f, it applies for 1710 - 1755 MHz | +| GSM850 or CDMA850 | 824 - 849 MHz | -98 dBm | 100 kHz | | +| WA BS UTRA FDD Band I
or
E-UTRA Band 1 | 1920 - 1980 MHz | -80 dBm (*) | 3,84 MHz | | +| WA BS UTRA FDD Band III
or
E-UTRA Band 3 | 1710 - 1785 MHz | -80dBm | 3.84 MHz | For UTRA TDD BS operating in Band f, it applies for 1710-1755 MHz. | +| WA BS UTRA FDD Band V
or
E-UTRA Band 5 | 824 - 849 MHz | -80 dBm (*) | 3,84 MHz | | +| WA BS UTRA FDD Band VII
or
E-UTRA Band 7 | 2500 - 2570 MHz | - 80 dBm(**) | 3.84 MHz | | + +NOTE 1: The co-location requirements do not apply for the 10 MHz frequency range immediately outside the BS transmit frequency range of the operating band (see section 4.2). The current state-of-the-art technology does not allow a single generic solution for co-location with other system on adjacent frequencies for 30dB BS-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [9]. + +NOTE 2: The requirements in Table 6.17 are based on a minimum coupling loss of 30 dB between base stations. The co-location of different base station classes is not considered. + +NOTE 3: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. + +The normative reference for this requirement is TS 25.105 [1] subclause 6.6.3.2.2.1. + +6.6.3.2.3 (void) + +6.6.3.2.3.1 (void) + +**Table 6.33: Void****Table 6.33a: Void** + +6.6.3.2.3.2 Void + +**Table 6.34: Void****Table 6.34a: Void** + +6.6.3.2.4 Void + +6.6.3.2.4.1 Void + +**Table 6.35: Void** + +6.6.3.2.4.2 Void + +**Table 6.36: Void** + +6.6.3.2.5 Co-existence with unsynchronised UTRA TDD and/or E-UTRA TDD + +6.6.3.2.5.1 Operation in the same geographic area + +This requirement may be applied for the protection of TDD BS receivers in geographic areas in which unsynchronised UTRA TDD and/or E-UTRA TDD is deployed. + +6.6.3.2.5.1.1 3,84 Mcps TDD option + +The RRC filtered mean power of any spurious emission shall not exceed the maximum level given in table 6.36A. + +**Table 6.36A: BS Spurious emissions limits for operation in same geographic area with unsynchronised UTRA TDD and/or E-UTRA TDD** + +| System type operating in the same geographic area | Frequency range | Maximum Level | Measurement Bandwidth | +|---------------------------------------------------|-----------------|---------------|-----------------------| +| WA UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -39 dBm | 3,84 MHz | +| WA UTRA TDD Band a) or E-UTRA Band 34 | 2010 - 2025 MHz | -39 dBm | 3,84 MHz | +| WA UTRA TDD Band d) or E-UTRA Band 38 | 2570 - 2620 MHz | -39 dBm | 3,84 MHz | +| LA UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -36 dBm | 3,84 MHz | +| LA UTRA TDD Band a) or E-UTRA Band 34 | 2010 - 2025 MHz | -36 dBm | 3,84 MHz | +| LA UTRA TDD Band d) or E-UTRA Band 38 | 2570 - 2620 MHz | -36 dBm | 3,84 MHz | + +NOTE: The requirements in Table 6.36A for the Wide Area BS are based on a minimum coupling loss of 67 dB between unsynchronised TDD base stations. The requirements in Table 6.36A for the Local Area BS are based on a coupling loss of 70 dB between unsynchronised Wide Area and Local Area TDD base stations. The scenarios leading to these requirements are addressed in TR 25.942 [9]. + +The normative reference for this requirement is TS 25.105 [1] subclause 6.6.3.5.1.1.1. + +6.6.3.2.5.1.2 1,28 Mcps TDD option + +In geographic areas where 1,28 Mcps TDD is deployed, the RRC filtered mean power of any spurious emission shall not exceed the maximum level given in table 6.36B. + +For BS capable of multi-band operation, the exclusions and conditions in the Note of Table 6.36B apply for each supported operating band. For BS capable of multi-band operation where multiple bands are mapped on separate antenna connectors, the exclusions and conditions in the Note of Table 6.36B apply for the operating band supported at that antenna connector. + +**Table 6.36B: BS Spurious emissions limits for operation in same geographic area with unsynchronised 1,28 Mcps UTRA TDD and/or E-UTRA TDD** + +| System type operating in the same geographic area | Frequency range | Maximum Level | Measurement Bandwidth | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|---------------|-----------------------| +| WA UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -52 dBm | 1 MHz | +| WA UTRA TDD Band a) or E-UTRA Band 34 | 2010 - 2025 MHz | -52 dBm | 1 MHz | +| WA UTRA TDD Band d) or E-UTRA Band 38 | 2570 - 2620 MHz | -52 dBm | 1 MHz | +| WA UTRA TDD Band e) or E-UTRA Band 40 | 2300 - 2400 MHz | -52 dBm | 1 MHz | +| WA UTRA TDD Band f) or E-UTRA Band 39 | 1880 – 1920 MHz | -52 dBm | 1 MHz | +| WA E-UTRA Band 41 | 2496 – 2690 MHz | -52 dBm | 1 MHz | +| WA E-UTRA Band 42 | 3400 – 3600 MHz | -52 dBm | 1 MHz | +| WA E-UTRA Band 44 | 703 – 803 MHz | -52 dBm | 1 MHz | +| LA UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -52 dBm | 1 MHz | +| LA UTRA TDD Band a) or E-UTRA Band 34 | 2010 - 2025 MHz | -52 dBm | 1 MHz | +| LA UTRA TDD Band d) or E-UTRA Band 38 | 2570 - 2620 MHz | -52 dBm | 1 MHz | +| LA UTRA TDD Band e) or E-UTRA Band 40 | 2300 - 2400 MHz | -52 dBm | 1 MHz | +| LA UTRA TDD Band f) or E-UTRA Band 39 | 1880 – 1920 MHz | -52 dBm | 1 MHz | +| LA E-UTRA Band 41 | 2496 – 2690 MHz | -52 dBm | 1 MHz | +| LA E-UTRA Band 42 | 3400 – 3600 MHz | -52 dBm | 1 MHz | +| LA E-UTRA Band 44 | 703 – 803 MHz | -52 dBm | 1 MHz | +| LA E-UTRA Band 46 | 5150 – 5925 MHz | -52 dBm | 1 MHz | +| NOTE 1: The co-existence requirements do not apply for the 10 MHz frequency range immediately outside the operating band. | | | | +| NOTE 2: The requirements in this table are based on a minimum coupling loss of 67 dB between unsynchronised TDD base stations. The scenarios leading to these requirements are addressed in TR25.942 [9]. | | | | +| NOTE 3: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. | | | | + +**Table 6.36C: Void** + +The normative reference for this requirement is TS 25.105 [1] subclause 6.6.3.5.1.1.2. + +#### 6.6.3.2.5.1.3 7,68 Mcps TDD option + +The RRC filtered mean power of any spurious emission shall not exceed the maximum level given in table 6.36CA and 6.36CB. + +**Table 6.36CA: BS Spurious emissions limits for operation in same geographic area with unsynchronised UTRA TDD (7,68 Mcps TDD and 3,84 Mcps TDD) and/or E-UTRA TDD** + +| System type operating in the same geographic area | Frequency range | Maximum Level | Measurement Bandwidth | +|---------------------------------------------------|-----------------|---------------|-----------------------| +| WA UTRA TDD Band a)
or E-UTRA Band 33 | 1900 - 1920 MHz | -39 dBm | 3,84 MHz | +| WA UTRA TDD Band a)
or E-UTRA Band 34 | 2010 - 2025 MHz | -39 dBm | 3,84 MHz | +| WA UTRA TDD Band d)
or E-UTRA Band 38 | 2570 - 2620 MHz | -39 dBm | 3,84 MHz | +| LA UTRA TDD Band a)
or E-UTRA Band 33 | 1900 - 1920 MHz | -36 dBm | 3,84 MHz | +| LA UTRA TDD Band a)
or E-UTRA Band 34 | 2010 - 2025 MHz | -36 dBm | 3,84 MHz | +| LA UTRA TDD Band d)
or E-UTRA Band 38 | 2570 - 2620 MHz | -36 dBm | 3,84 MHz | + +**Table 6.36CB: BS Spurious emissions limits for operation in same geographic area with unsynchronised 1,28 Mcps UTRA TDD and/or E-UTRA TDD** + +| System type operating in the same geographic area | Frequency range | Maximum Level | Measurement Bandwidth | +|---------------------------------------------------|-----------------|---------------|-----------------------| +| WA UTRA TDD Band a)
or E-UTRA Band 33 | 1900 - 1920 MHz | -39 dBm | 1,28 MHz | +| WA UTRA TDD Band a)
or E-UTRA Band 34 | 2010 - 2025 MHz | -39 dBm | 1,28 MHz | +| WA UTRA TDD Band d)
or E-UTRA Band 38 | 2570 - 2620 MHz | -39 dBm | 1,28 MHz | +| WA UTRA TDD Band e)
or E-UTRA Band 40 | 2300 - 2400 MHz | -39 dBm | 1,28 MHz | +| LA UTRA TDD Band a)
or E-UTRA Band 33 | 1900 - 1920 MHz | -36 dBm | 1,28 MHz | +| LA UTRA TDD Band a)
or E-UTRA Band 34 | 2010 - 2025 MHz | -36 dBm | 1,28 MHz | +| LA UTRA TDD Band d)
or E-UTRA Band 38 | 2570 - 2620 MHz | -36 dBm | 1,28 MHz | +| LA UTRA TDD Band e)
or E-UTRA Band 40 | 2300 - 2400 MHz | -36 dBm | 1,28 MHz | + +NOTE: The requirements in Table 6.36CA and 6.36CB for the Wide Area BS are based on a minimum coupling loss of 67 dB between unsynchronised TDD base stations. The requirements in Table 6.36CA and 6.36CB for the Local Area BS are based on a coupling loss of 70 dB between unsynchronised Wide Area and Local Area TDD base stations. + +The normative reference for this requirement is TS 25.105 [1] subclause 6.6.3.5.1.1.3. + +#### 6.6.3.2.5.2 Co-located base stations + +This requirement may be applied for the protection of TDD BS receivers when unsynchronised UTRA TDD and/or E-UTRA TDD BS are co-located. + +##### 6.6.3.2.5.2.1 3,84 Mcps TDD option + +The RRC filtered mean power of any spurious emission shall not exceed the maximum level given in table 6.36D. + +**Table 6.36D: BS Spurious emissions limits for co-location with unsynchronised UTRA TDD and/or E-UTRA TDD** + +| System type operating in the same geographic area | Frequency range | Maximum Level | Measurement Bandwidth | +|----------------------------------------------------------|------------------------|----------------------|------------------------------| +| WA UTRA TDD Band a)
or E-UTRA Band 33 | 1900 - 1920 MHz | -76 dBm | 3,84 MHz | +| WA UTRA TDD Band a)
or E-UTRA Band 34 | 2010 - 2025 MHz | -76 dBm | 3,84 MHz | +| WA UTRA TDD Band d)
or E-UTRA Band 38 | 2570 - 2620 MHz | -76 dBm | 3,84 MHz | +| LA UTRA TDD Band a)
or E-UTRA Band 33 | 1900 - 1920 MHz | -66 dBm | 3,84 MHz | +| LA UTRA TDD Band a)
or E-UTRA Band 34 | 2010 - 2025 MHz | -66 dBm | 3,84 MHz | +| LA UTRA TDD Band d)
or E-UTRA Band 38 | 2570 - 2620 MHz | -66 dBm | 3,84 MHz | + +NOTE: The requirements in Table 6.36D for the Wide Area BS are based on a minimum coupling loss of 30 dB between unsynchronised TDD base stations. The requirements in Table 6.36D for the Local Area BS are based on a minimum coupling loss of 30 dB between unsynchronised Local Area base stations. The co-location of different base station classes is not considered. + +The normative reference for this requirement is TS 25.105 [1] subclause 6.6.3.5.2.1.1. + +#### 6.6.3.2.5.2.2 1,28 Mcps TDD option + +In geographic areas where 1,28 Mcps TDD is deployed, the RRC filtered mean power of any spurious emission in case of co-location shall not exceed the maximum level given in table 6.36E. + +For BS capable of multi-band operation, the exclusions and conditions in the Note of Table 6.36E apply for each supported operating band. For BS capable of multi-band operation where multiple bands are mapped on separate antenna connectors, the exclusions and conditions in the Note of Table 6.36E apply for the operating band supported at that antenna connector. + +**Table 6.36E: BS Spurious emissions limits for co-location with unsynchronised 1,28 Mcps UTRA TDD and/or E-UTRA TDD** + +| System type operating in the same geographic area | Frequency range | Maximum Level | Measurement Bandwidth | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|---------------|-----------------------| +| WA UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -96 dBm | 100 kHz | +| WA UTRA TDD Band a) or E-UTRA Band 34 | 2010 - 2025 MHz | -96 dBm | 100 kHz | +| WA UTRA TDD Band d) or E-UTRA Band 38 | 2570 - 2620 MHz | -96 dBm | 100 kHz | +| WA UTRA TDD Band e) or E-UTRA Band 40 | 2300 - 2400 MHz | -96 dBm | 100 kHz | +| WA UTRA TDD Band f) or E-UTRA Band 39 | 1880 - 1920 MHz | -96 dBm | 100 kHz | +| WA E-UTRA Band 41 | 2496 – 2690 MHz | -96 dBm | 100 kHz | +| WA E-UTRA Band 42 | 3400 – 3600 MHz | -96 dBm | 100 kHz | +| WA E-UTRA Band 44 | 703 – 803 MHz | -96 dBm | 100 kHz | +| LA UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -88 dBm | 100 kHz | +| LA UTRA TDD Band a) or E-UTRA Band 34 | 2010 - 2025 MHz | -88 dBm | 100 kHz | +| LA UTRA TDD Band d) or E-UTRA Band 38 | 2570 - 2620 MHz | -88 dBm | 100 kHz | +| LA UTRA TDD Band e) or E-UTRA Band 40 | 2300 - 2400 MHz | -88 dBm | 100 kHz | +| LA UTRA TDD Band f) or E-UTRA Band 39 | 1880 - 1920 MHz | -88 dBm | 100 kHz | +| LA E-UTRA Band 41 | 2496 – 2690 MHz | -88 dBm | 100 kHz | +| LA E-UTRA Band 42 | 3400 – 3600 MHz | -88 dBm | 100 kHz | +| LA E-UTRA Band 44 | 703 – 803 MHz | -88 dBm | 100 kHz | +| NOTE 1: The requirement applies for frequencies more than 10 MHz below or above the supported frequency range declared by the vendor. The current state-of-the-art technology does not allow a single generic solution for co-location with other system on adjacent frequencies for 30dB BS-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [9]. | | | | +| NOTE 2: The requirements in this table are based on a minimum coupling loss of 30 dB between unsynchronised TDD base stations. The scenarios leading to these requirements are addressed in TR 25.942 [9]. | | | | +| NOTE 3: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. | | | | + +**Table 6.36F: Void** + +NOTE: The requirements in Table 6.36E for the Wide Area BS are based on a minimum coupling loss of 30 dB between unsynchronised TDD base stations. The requirements in Table 6.36E for the Local Area BS are based on a minimum coupling loss of 30 dB between unsynchronised Local Area base stations. The co-location of different base station classes is not considered. + +The normative reference for this requirement is TS 25.105 [1] subclause 6.6.3.5.2.1.2. + +#### 6.6.3.2.5.2.3 7,68 Mcps TDD option + +The RRC filtered mean power of any spurious emission shall not exceed the maximum level given in table 6.36G and 6.36H. + +**Table 6.36G: BS Spurious emissions limits for co-location with unsynchronised UTRA TDD (7,68 Mcps TDD and 3,84 Mcps TDD) and/or E-UTRA TDD** + +| System type operating in the same geographic area | Frequency range | Maximum Level | Measurement Bandwidth | +|---------------------------------------------------|-----------------|---------------|-----------------------| +| WA UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -76 dBm | 3,84 MHz | +| WA UTRA TDD Band a) or E-UTRA Band 34 | 2010 - 2025 MHz | -76 dBm | 3,84 MHz | +| WA UTRA TDD Band d) or E-UTRA Band 38 | 2570 - 2620 MHz | -76 dBm | 3,84 MHz | +| LA UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -66 dBm | 3,84 MHz | +| LA UTRA TDD Band a) or E-UTRA Band 34 | 2010 - 2025 MHz | -66 dBm | 3,84 MHz | +| LA UTRA TDD Band d) or E-UTRA Band 38 | 2570 - 2620 MHz | -66 dBm | 3,84 MHz | + +**Table 6.36H: BS Spurious emissions limits for co-location with unsynchronised 1,28 Mcps UTRA TDD and/or E-UTRA TDD** + +| System type operating in the same geographic area | Frequency range | Maximum Level | Measurement Bandwidth | +|---------------------------------------------------|-----------------|---------------|-----------------------| +| WA UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -76 dBm | 1,28 MHz | +| WA UTRA TDD Band a) or E-UTRA Band 34 | 2010 - 2025 MHz | -76 dBm | 1,28 MHz | +| WA UTRA TDD Band d) or E-UTRA Band 38 | 2570 - 2620 MHz | -76 dBm | 1,28 MHz | +| WA UTRA TDD Band e) or E-UTRA Band 40 | 2300 - 2400 MHz | -76 dBm | 1,28 MHz | +| LA UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -71 dBm | 1,28 MHz | +| LA UTRA TDD Band a) or E-UTRA Band 34 | 2010 - 2025 MHz | -71 dBm | 1,28 MHz | +| LA UTRA TDD Band d) or E-UTRA Band 38 | 2570 - 2620 MHz | -71 dBm | 1,28 MHz | +| LA UTRA TDD Band e) or E-UTRA Band 40 | 2300 - 2400 MHz | -71 dBm | 1,28 MHz | + +NOTE: The requirements in Table 6.36G and 6.36H for the Wide Area BS are based on a minimum coupling loss of 30 dB between unsynchronised TDD base stations. The requirements in Table 6.36G and 6.36H for the Local Area BS are based on a minimum coupling loss of 30 dB between unsynchronised Local Area base stations. The co-location of different base station classes is not considered. + +The normative reference for this requirement is TS 25.105 [1] subclause 6.6.3.5.2.1.3. + +#### 6.6.3.2.6 Co-existence with PHS + +##### 6.6.3.2.6.1 3,84 Mcps TDD option + +This requirement may be applied for the protection of PHS in geographic areas in which both PHS and 3,84 Mcps UTRA TDD are deployed. For 3,84 Mcps TDD option, this requirement is also applicable at specified frequencies falling between 12.5MHz below the first carrier frequency used and 12.5MHz above the last carrier frequency used. + +The power of any spurious emission shall not exceed the maximum level given in table 6.36I. + +**Table 6.36I: BS Spurious emissions limits for BS in geographic coverage area of PHS (3,84 Mcps TDD option)** + +| Band | Maximum Level | Measurement Bandwidth | Note | +|---------------------|---------------|-----------------------|-------------------------------------------------------------------------------| +| 1884.5 - 1915.7 MHz | -41 dBm | 300 kHz | Applicable for transmission in 2010-2025 MHz as defined in subclause 4.2 (a). | + +6.6.3.2.6.2 (void) + +6.6.3.2.6.3 7,68 Mcps TDD option + +This requirement may be applied for the protection of PHS in geographic areas in which both PHS and 7,68 Mcps UTRA TDD are deployed. For 7,68 Mcps TDD option, this requirement is also applicable at specified frequencies falling between 25 MHz below the first carrier frequency used and 25MHz above the last carrier frequency used. + +The power of any spurious emission shall not exceed the maximum level given in table 6.36J. + +**Table 6.36J: BS Spurious emissions limits for BS in geographic coverage area of PHS (7,68 Mcps TDD option)** + +| Band | Maximum Level | Measurement Bandwidth | Note | +|---------------------|---------------|-----------------------|-------------------------------------------------------------------------------| +| 1884.5 - 1915.7 MHz | -41 dBm | 300 kHz | Applicable for transmission in 2010-2025 MHz as defined in subclause 4.2 (a). | + +6.6.3.3 Test purpose + +6.6.3.3.1 3,84 Mcps TDD option + +The test purpose is to verify the ability of the BS to limit the interference caused by unwanted transmitter effects to other systems operating at frequencies which are more than 12,5 MHz away from of the UTRA band used. + +6.6.3.3.2 1,28 Mcps TDD option + +The test purpose is to verify the ability of the BS to limit the interference caused by unwanted transmitter effects to other systems operating at frequencies which are more than 4 MHz away from of the UTRA band used. + +6.6.3.3.3 7,68 Mcps TDD option + +The test purpose is to verify the ability of the BS to limit the interference caused by unwanted transmitter effects to other systems operating at frequencies which are more than 25 MHz away from of the UTRA band used. + +6.6.3.4 Method of test + +6.6.3.4.1 Initial conditions + +For 3,84 Mcps BS supporting 16QAM, the spurious requirements shall be tested with the general test set up specified in section 6.6.3.4.1.1 and also with the special test set up for 16QAM capable BS specified in section 6.6.3.4.1.4. + +For 1,28 Mcps BS supporting 16QAM, the spurious requirements shall be tested with the general test set up specified in section 6.6.3.4.1.2 and also with the special test set up for 16QAM capable BS specified in section 6.6.3.4.1.3. + +For 7,68 Mcps BS supporting 16QAM, the spurious requirements shall be tested with the general test set up specified in section 6.6.3.4.1.5 and also with the special test set up for 16QAM capable BS specified in section 6.6.3.4.1.6. + +6.6.3.4.1.0 General test conditions + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested for single carrier: B, M and T; see subclause 5.3. + +RF bandwidth positions to be tested for multi-carrier: $B_{RFBW}$ , $M_{RFBW}$ and $T_{RFBW}$ in single band operation; see subclause 5.3; $B'_{RFBW\_T'_{RFBW}}$ and $B'_{RFBW\_T_{RFBW}}$ in multi-band operation, see subclause 5.3. + +#### 6.6.3.4.1.1 3,84 Mcps TDD option - General test set up + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) Set the parameters of the BS transmitted signal according to table 6.37. For MBSFN IMB operation the set of parameters for the transmitted signals is according to IMB test model 1 in subclause 6.1.1.1. + +**Table 6.37: Parameters of the BS transmitted signal for spurious emissions testing** + +| Parameter | Value/description | +|---------------------------------------------|---------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | PRAT | +| Number of DPCH in each time slot under test | 9 | +| Power of each DPCH | 1/9 of Base Station output power | +| Data content of DPCH | real life (sufficient irregular) | + +#### 6.6.3.4.1.2 1,28 Mcps TDD option - General test set up + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) For a BS declared to be capable of single carrier operation only, set the parameters of the BS transmitted signal according to table 6.37A at manufacturer's declared output power PRAT. + +For a BS declared to be capable of multi-carrier operation, set the base station to transmit according to Table 6.37A on all carriers configured using the applicable test configuration and corresponding power setting specified in subclause 5.20 and 5.21. + +**Table 6.37A: Parameters of the BS transmitted signal for spurious emissions testing for 1,28 Mcps TDD** + +| Parameter | Value/description | +|--------------------------------------------------|-----------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| Number of DPCH in each each time slot under test | 8 | +| Power of each DPCH | 1/8 of Base Station output power | +| Data content of DPCH | real life (sufficient irregular) | + +#### 6.6.3.4.1.3 1,28 Mcps TDD option - Special test set up for 16QAM capable BS + +This test set up only applies for 16QAM capable BS. + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) For a BS declared to be capable of single carrier operation only, set the parameters of the BS transmitted signal according to table 6.37B at manufacturer's declared output power PRAT. + +For a BS declared to be capable of multi-carrier operation, set the base station to transmit according to Table 6.37B on all carriers configured using the applicable test configuration and corresponding power setting specified in subclause 5.20 and 5.21. + +**Table 6.37B: Parameters of the BS transmitted signal for spurious emissions testing for 1,28 Mcps TDD - 16QAM capable BS** + +| Parameter | Value/description | +|-------------------------------------------------|--------------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i
is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| HS-PDSCH modulation | 16QAM | +| Number of HS-PDSCH in each time slot under test | 8 | +| Power of each HS-PDSCH | 1/8 of Base Station output power | +| Data content of HS-PDSCH | real life (sufficient irregular) | +| Spreading factor | 16 | + +#### 6.6.3.4.1.4 3,84 Mcps TDD option - Special test set up for 16QAM capable BS + +This test set up only applies for 16QAM capable BS. + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) Set the parameters of the BS transmitted signal according to table 6.37C. For MBSFN IMB operation the set of parameters for the transmitted signals is according to IMB test model 2 in subclause 6.1.1.2. + +**Table 6.37C: Parameters of the BS transmitted signal for spurious emissions testing - 16QAM capable BS** + +| Parameter | Value/description | +|-------------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | PRAT | +| HS-PDSCH modulation | 16QAM | +| Number of HS-PDSCH in each time slot under test | 9 | +| Power of each HS-PDSCH | 1/9 of Base Station output power | +| Data content of HS-PDSCH | real life (sufficient irregular) | +| Spreading factor | 16 | + +#### 6.6.3.4.1.5 7,68 Mcps TDD option - General test set up + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) Set the parameters of the BS transmitted signal according to table 6.37D. + +**Table 6.37D: Parameters of the BS transmitted signal for spurious emissions testing** + +| Parameter | Value/description | +|---------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | PRAT | +| Number of DPCH in each time slot under test | 9 | +| Power of each DPCH | 1/9 of Base Station output power | +| Data content of DPCH | real life (sufficient irregular) | + +#### 6.6.3.4.1.6 7,68 Mcps TDD option - Special test set up for 16QAM capable BS + +This test set up only applies for 16QAM capable BS. + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) Set the parameters of the BS transmitted signal according to table 6.37E. + +**Table 6.37E: Parameters of the BS transmitted signal for spurious emissions testing - 16QAM capable BS** + +| Parameter | Value/description | +|-------------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | PRAT | +| HS-PDSCH modulation | 16QAM | +| Number of HS-PDSCH in each time slot under test | 9 | +| Power of each HS-PDSCH | 1/9 of Base Station output power | +| Data content of HS-PDSCH | real life (sufficient irregular) | +| Spreading factor | 32 | + +#### 6.6.3.4.2 Procedure + +- 1) Measure the power of the spurious emissions by applying measurement filters with bandwidths as specified in the relevant tables of subclause 6.6.3.2. The characteristics of the measurement filter with the bandwidth 1,28 MHz or 3,84MHz shall be RRC with roll-off $\alpha = 0,22$ . The characteristics of the measurement filters with bandwidths 100 kHz and 1 MHz shall be approximately Gaussian (typical spectrum analyzer filter). The center frequency of the filter shall be stepped in contiguous steps over the frequency bands as given in the tables. The step width shall be equal to the respective measurement bandwidth. The time duration of each step shall be sufficiently long to capture one active time slot. + +In addition, for a multi-band capable BS, the following steps shall apply: + +- 2) For multi-band capable BS and single band tests, repeat the steps above per involved band with no carrier activated in the other band. +- 3) For multi-band capable BS with separate antenna connector, the antenna connector not being under test in case of single-band or multi-band test shall be terminated. + +#### 6.6.3.5 Test Requirements + +NOTE: If the Test Requirement below differs from the Minimum Requirement, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +The spurious emissions measured according to subclause 6.6.3.4.2 shall not exceed the limits specified in the relevant tables of 6.6.3.2. + +For 3,84 Mcps TDD BS supporting 16QAM, the measured spurious emissions shall not exceed the limits specified for 3,84 Mcps TDD option in section 6.6.3.2. + +For 1,28 Mcps TDD BS supporting 16QAM, the measured spurious emissions shall not exceed the limits specified for 1,28 Mcps TDD option in section 6.6.3.2. + +For 7,68 Mcps TDD BS supporting 16QAM, the measured spurious emissions shall not exceed the limits specified for 7,68 Mcps TDD option in section 6.6.3.2. + +## 6.7 Transmit intermodulation + +### 6.7.1 Definition and applicability + +The transmit intermodulation performance is a measure of the capability of the transmitter to inhibit the generation of signals in its non linear elements caused by presence of the wanted signal and an interfering signal reaching the transmitter via the antenna. + +The transmit intermodulation level is the power of the intermodulation products when a CDMA modulated interference signal is injected into the antenna connector at a power level of 30 dB lower than that of the rated total output power in the operating band. + +#### 6.7.1.1 3,84 Mcps TDD option + +The carrier frequency of the interference signal shall be $\pm 5$ MHz, $\pm 10$ MHz and $\pm 15$ MHz offset from the subject signal carrier frequency, but excluding interference carrier frequencies outside of the UTRA frequency bands specified in 4.2a, 4.2b or 4.2c, respectively. + +#### 6.7.1.2 1,28 Mcps TDD option + +The interfering signal offset from the subject signal shall be as defined in table 6.37F. + +For BS capable of multi-band operation where multiple bands are mapped on separate antenna connectors, the single-band requirements apply regardless of the interfering signals position relative to the inter RF bandwidth gap. + +**Table 6.37F: Interfering signal frequency offset** + +| Parameter | Value | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------| +| Interfering signal frequency offset from the subject signal carrier frequency | $\pm 1,6$ MHz
$\pm 3,2$ MHz
$\pm 4,8$ MHz | +| Interfering signal frequency offset from the edge of RF bandwidth | $\pm 0,8$ MHz
$\pm 2,4$ MHz
$\pm 4,0$ MHz | +| NOTE 1: Interference frequencies that are outside of the allocated frequency band are excluded from the requirement, unless the interfering signal positions fall within the frequency range of adjacent downlink operating bands in the same geographical area. | | + +#### 6.7.1.3 7,68 Mcps TDD option + +The carrier frequency of the interference signal shall be $\pm 10$ MHz, $\pm 20$ MHz and $\pm 30$ MHz offset from the subject signal carrier frequency, but excluding interference carrier frequencies outside of the UTRA frequency bands specified in 4.2a, 4.2b or 4.2c, respectively. + +### 6.7.2 Minimum Requirements + +The transmit intermodulation level shall not exceed the out of band or the spurious emission requirements of subclause 6.6.2 and 6.6.3, respectively. + +The normative reference for this requirement is TS 25.105 [1] subclause 6.7.1. + +### 6.7.3 Test purpose + +The test purpose is to verify the ability of the BS transmitter to restrict the generation of intermodulation products in its non linear elements caused by presence of the wanted signal and an interfering signal reaching the transmitter via the antenna to below specified levels. + +## 6.7.4 Method of test + +### 6.7.4.1 Initial conditions + +For 3,84 Mcps BS supporting 16QAM, the transmit intermodulation requirements shall be tested with the general test set up specified in section 6.7.4.1.1 and also with the special test set up for 16QAM capable BS specified in section 6.7.4.1.4. + +For 1,28 Mcps BS supporting 16QAM, the transmit intermodulation requirements shall be tested with the general test set up specified in section 6.7.4.1.2 and also with the special test set up for 16QAM capable BS specified in section 6.7.4.1.3. + +For 7,68 Mcps BS supporting 16QAM, the transmit intermodulation requirements shall be tested with the general test set up specified in section 6.7.4.5.1 and also with the special test set up for 16QAM capable BS specified in section 6.7.4.1.6. + +### 6.7.4.1.0 General test conditions + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested for single carrier: B, M and T; see subclause 5.3. + +RF bandwidth positions to be tested for multi-carrier: $B_{\text{RFBW}}$ , $M_{\text{RFBW}}$ and $T_{\text{RFBW}}$ in single band operation; see subclause 5.3. + +#### 6.7.4.1.1 3,84 Mcps TDD option - General test set up + +- (1) Connect the measuring equipment, the BS under test and the WCDMA signal generator as shown in figure 6.2. +- (2) Set the parameters of the BS transmitted signal according to table 6.38. For MBSFN IMB operation the set of parameters for the transmitted signals is according to IMB test model 1 in subclause 6.1.1.1. +- (3) Configure the WCDMA signal generator to produce an interference signal with a mean power level according to subclause 6.7.5. The interference signal shall be like-modulated as the BS transmitted signal, and the active time slots of both signals shall be synchronized. The carrier frequency of the interference signal shall be $\pm 5$ MHz, $\pm 10$ MHz and $\pm 15$ MHz offset from the carrier frequency of the wanted signal, but excluding interference frequencies outside of the UTRA frequency bands specified in 4.2a, 4.2b or 4.2c, respectively. + +![Figure 6.2: Measuring setup for Base Station transmit intermodulation testing. The diagram shows a 'Base Station under test TX' connected to a 'Directional coupler'. The 'Directional coupler' has three outputs: one to an 'Artificial load (Attenuator)' which then connects to 'Measuring equipment'; one to a 'CDMA Signal Generator'; and one to a 'Power Meter' via a switch. The 'Base Station under test TX' is also connected to the 'Power Meter' via the switch.](9dee6d7157e1d03eb09a30a9aa81cc11_img.jpg) + +Figure 6.2: Measuring setup for Base Station transmit intermodulation testing. The diagram shows a 'Base Station under test TX' connected to a 'Directional coupler'. The 'Directional coupler' has three outputs: one to an 'Artificial load (Attenuator)' which then connects to 'Measuring equipment'; one to a 'CDMA Signal Generator'; and one to a 'Power Meter' via a switch. The 'Base Station under test TX' is also connected to the 'Power Meter' via the switch. + +Figure 6.2: Measuring setup for Base Station transmit intermodulation testing + +**Table 6.38: Parameters of the BS transmitted signal for transmit intermodulation testing** + +| Parameter | Value/description | +|---------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is odd;
receive, if i is even. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | PRAT | +| Number of DPCH in each time slot under test | 9 | +| Power of each DPCH | 1/9 of Base Station output power | +| Data content of DPCH | real life (sufficient irregular) | + +#### 6.7.4.1.2 1,28 Mcps TDD option - General test set up + +- (1) Connect the measuring equipment, the BS under test and the 1,28 Mcps TDD signal generator as shown in figure 6.2A. +- (2) For a BS declared to be capable of single carrier operation only, set the parameters of the BS transmitted signal according to table 6.38A. + +For a BS declared to be capable of multi-carrier operation, set the base station to transmit according to Table 6.38A on all carriers configured using the applicable test configuration and corresponding power setting specified in subclause 5.20 and 5.21. + +- (3) Configure the 1,28 Mcps TDD signal generator to produce an interference signal with a power level according to subclause 6.7.5. The interference signal shall be like-modulated as the BS transmitted signal, and the active time slots of both signals shall be synchronized. The interfering signal offset from the subject signal shall be according to Table 6.37F. + +![Figure 6.2A: Measuring set up for Base Station transmit intermodulation testing. The diagram shows a 'Base Station under test TX' connected to a 'Directional coupler'. The 'Directional coupler' has three outputs: one to an 'Artificial load (Attenuator)' which then connects to 'Measuring equipment', one to a 'Power Meter', and one to a '1,28 Mcps TDD Signal Generator'.](56468323fb2f5ff6f0a8bf9bf1f691e8_img.jpg) + +``` + +graph LR + BS[Base Station under test TX] --> DC[Directional coupler] + DC --> AL[Artificial load Attenuator] + AL --> ME[Measuring equipment] + DC --> PM[Power Meter] + DC --> SG[1,28 Mcps TDD Signal Generator] + +``` + +Figure 6.2A: Measuring set up for Base Station transmit intermodulation testing. The diagram shows a 'Base Station under test TX' connected to a 'Directional coupler'. The 'Directional coupler' has three outputs: one to an 'Artificial load (Attenuator)' which then connects to 'Measuring equipment', one to a 'Power Meter', and one to a '1,28 Mcps TDD Signal Generator'. + +**Figure 6.2A: Measuring set up for Base Station transmit intermodulation testing****Table 6.38A: Parameters of the BS transmitted signal for transmit intermodulation testing for 1,28 Mcps TDD** + +| Parameter | Value/description | +|---------------------------------------------|--------------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i
is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| Number of DPCH in each time slot under test | 8 | +| Power of each DPCH | 1/8 of Base Station output power | +| Data content of DPCH | real life (sufficient irregular) | + +#### 6.7.4.1.3 1,28 Mcps TDD option - Special test set up for 16QAM capable BS + +This test set up only applies for 16QAM capable BS. + +- (1) Connect the measuring equipment, the BS under test and the 1,28 Mcps TDD signal generator as shown in figure 6.2B. +- (2) For a BS declared to be capable of single carrier operation only, set the parameters of the BS transmitted signal according to table 6.38B at manufacturer's declared output power, PRAT. + +For a BS declared to be capable of multi-carrier operation, set the base station to transmit according to Table 6.38B on all carriers configured using the applicable test configuration and corresponding power setting specified in subclause 5.20 and 5.21. + +- (3) Configure the 1,28 Mcps TDD signal generator to produce an interference signal with a power level according to subclause 6.7.5. The interference signal shall be like-modulated as the BS transmitted signal, and the active time slots of both signals shall be synchronized. The interfering signal offset from the subject signal shall be according to Table 6.37F. + +![Figure 6.2B: Measuring setup for Base Station transmit intermodulation testing. The diagram shows a 'Base Station under test TX' connected to a 'Directional coupler'. The 'Directional coupler' has three outputs: one to an 'Artificial load (Attenuator)' which then connects to 'Measuring equipment', one to a 'Power Meter', and one to a '1,28 Mcps TDD Signal Generator'.](7be79849b00ccd5e7220d808251b1258_img.jpg) + +``` + +graph LR + BS[Base Station under test TX] --> DC[Directional coupler] + DC --> AL[Artificial load Attenuator] + AL --> ME[Measuring equipment] + DC --> PM[Power Meter] + DC --> SG[1,28 Mcps TDD Signal Generator] + +``` + +Figure 6.2B: Measuring setup for Base Station transmit intermodulation testing. The diagram shows a 'Base Station under test TX' connected to a 'Directional coupler'. The 'Directional coupler' has three outputs: one to an 'Artificial load (Attenuator)' which then connects to 'Measuring equipment', one to a 'Power Meter', and one to a '1,28 Mcps TDD Signal Generator'. + +Figure 6.2B: Measuring setup for Base Station transmit intermodulation testing + +Table 6.38B: Parameters of the BS transmitted signal for transmit intermodulation testing for 1,28 Mcps TDD- 16QAM capable BS + +| Parameter | Value/description | +|-------------------------------------------------|--------------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i
is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| HS-PDSCH modulation | 16QAM | +| Number of HS-PDSCH in each time slot under test | 8 | +| Power of each HS-PDSCH | 1/8 of Base Station output power | +| Data content of HS-PDSCH | real life (sufficient irregular) | +| Spreading factor | 16 | + +#### 6.7.4.1.4 3,84 Mcps TDD option - Special test set up for 16QAM capable BS + +- (1) Connect the measuring equipment, the BS under test and the WCDMA signal generator as shown in figure 6.3. +- (2) Set the parameters of the BS transmitted signal according to table 6.38C. For MBSFN IMB operation the set of parameters for the transmitted signals is according to IMB test model 2 in subclause 6.1.1.2. + +- (3) Configure the WCDMA signal generator to produce an interference signal with a mean power level according to subclause 6.7.5. The interference signal shall be like-modulated as the BS transmitted signal, and the active time slots of both signals shall be synchronized. The carrier frequency of the interference signal shall be $\pm 5$ MHz, $\pm 10$ MHz and $\pm 15$ MHz offset from the carrier frequency of the wanted signal, but excluding interference frequencies outside of the UTRA frequency bands specified in 4.2a, 4.2b or 4.2c, respectively. + +![Figure 6.3: Measuring setup for Base Station transmit intermodulation testing. The diagram shows a Base Station under test TX connected to a Directional coupler. The Directional coupler is also connected to a CDMA Signal Generator and an Artificial load (Attenuator). The Artificial load is connected to Measuring equipment. A Power Meter is connected to the Base Station under test TX via a switch.](a4e9abbc6ca82471f1a223d0a68cd45e_img.jpg) + +``` + +graph LR + BS[Base Station under test TX] -- switch --> DC[Directional coupler] + DC --> AL[Artificial load Attenuator] + AL --> ME[Measuring equipment] + DC --> CDMA[CDMA Signal Generator] + BS -- switch --> PM[Power Meter] + +``` + +Figure 6.3: Measuring setup for Base Station transmit intermodulation testing. The diagram shows a Base Station under test TX connected to a Directional coupler. The Directional coupler is also connected to a CDMA Signal Generator and an Artificial load (Attenuator). The Artificial load is connected to Measuring equipment. A Power Meter is connected to the Base Station under test TX via a switch. + +Figure 6.3: Measuring setup for Base Station transmit intermodulation testing + +Table 6.38C: Parameters of the BS transmitted signal for transmit intermodulation testing - 16QAM capable BS + +| Parameter | Value/description | +|-------------------------------------------------|---------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | PRAT | +| HS-PDSCH modulation | 16QAM | +| Number of HS-PDSCH in each time slot under test | 9 | +| Power of each HS-PDSCH | 1/9 of Base Station output power | +| Data content of HS-PDSCH | real life (sufficient irregular) | +| Spreading factor | 16 | + +#### 6.7.4.1.5 7,68 Mcps TDD option - General test set up + +- (1) Connect the measuring equipment, the BS under test and the WCDMA signal generator as shown in figure 6.4. +- (2) Set the parameters of the BS transmitted signal according to table 6.38D. +- (3) Configure the WCDMA signal generator to produce an interference signal with a mean power level according to subclause 6.7.5. The interference signal shall be like-modulated as the BS transmitted signal, and the active time slots of both signals shall be synchronized. The carrier frequency of the interference signal shall be $\pm 10$ MHz, $\pm 20$ MHz and $\pm 30$ MHz offset from the carrier frequency of the wanted signal, but excluding interference frequencies outside of the UTRA frequency bands specified in 4.2a, 4.2b or 4.2c, respectively. + +![Figure 6.4: Measuring setup for Base Station transmit intermodulation testing. The diagram shows a Base Station under test TX connected to a Directional coupler. The Directional coupler is also connected to a CDMA Signal Generator and an Artificial load (Attenuator). The Artificial load is connected to Measuring equipment. A Power Meter is connected to the Base Station under test TX via a switch.](9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg) + +``` + +graph LR + BS[Base Station under test TX] -- switch --> PM[Power Meter] + BS -- switch --> DC[Directional coupler] + DC --> CS[CDMA Signal Generator] + DC --> AL[Artificial load Attenuator] + AL --> ME[Measuring equipment] + +``` + +Figure 6.4: Measuring setup for Base Station transmit intermodulation testing. The diagram shows a Base Station under test TX connected to a Directional coupler. The Directional coupler is also connected to a CDMA Signal Generator and an Artificial load (Attenuator). The Artificial load is connected to Measuring equipment. A Power Meter is connected to the Base Station under test TX via a switch. + +Figure 6.4: Measuring setup for Base Station transmit intermodulation testing + +Table 6.38D: Parameters of the BS transmitted signal for transmit intermodulation testing + +| Parameter | Value/description | +|---------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is odd;
receive, if i is even. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | PRAT | +| Number of DPCH in each time slot under test | 9 | +| Power of each DPCH | 1/9 of Base Station output power | +| Data content of DPCH | real life (sufficient irregular) | + +#### 6.7.4.1.6 7,68 Mcps TDD option - Special test set up for 16QAM capable BS + +- (1) Connect the measuring equipment, the BS under test and the WCDMA signal generator as shown in figure 6.5. +- (2) Set the parameters of the BS transmitted signal according to table 6.38D. +- (3) Configure the WCDMA signal generator to produce an interference signal with a mean power level according to subclause 6.7.5. The interference signal shall be like-modulated as the BS transmitted signal, and the active time slots of both signals shall be synchronized. The carrier frequency of the interference signal shall be $\pm 10$ MHz, $\pm 20$ MHz and $\pm 30$ MHz offset from the carrier frequency of the wanted signal, but excluding interference frequencies outside of the UTRA frequency bands specified in 4.2a, 4.2b or 4.2c, respectively. + +![Figure 6.5: Measuring setup for Base Station transmit intermodulation testing. The diagram shows a Base Station under test TX connected to a Directional coupler. The Directional coupler is also connected to a CDMA Signal Generator and an Artificial load (Attenuator). The Artificial load is connected to Measuring equipment. A Power Meter is connected to the Base Station under test TX via a switch.](5f6ee513bafbf5140814bda2337e145f_img.jpg) + +``` + +graph LR + BS[Base Station under test TX] -- switch --> PM[Power Meter] + BS -- switch --> DC[Directional coupler] + DC --> CS[CDMA Signal Generator] + DC --> AL[Artificial load Attenuator] + AL --> ME[Measuring equipment] + +``` + +Figure 6.5: Measuring setup for Base Station transmit intermodulation testing. The diagram shows a Base Station under test TX connected to a Directional coupler. The Directional coupler is also connected to a CDMA Signal Generator and an Artificial load (Attenuator). The Artificial load is connected to Measuring equipment. A Power Meter is connected to the Base Station under test TX via a switch. + +Figure 6.5: Measuring setup for Base Station transmit intermodulation testing + +**Table 6.38D: Parameters of the BS transmitted signal for transmit intermodulation testing - 16QAM capable BS** + +| Parameter | Value/description | +|-------------------------------------------------|---------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | PRAT | +| HS-PDSCH modulation | 16QAM | +| Number of HS-PDSCH in each time slot under test | 9 | +| Power of each HS-PDSCH | 1/9 of Base Station output power | +| Data content of HS-PDSCH | real life (sufficient irregular) | +| Spreading factor | 32 | + +#### 6.7.4.2 Procedure + +- 1) Apply the single-band test procedures for out of band and spurious emissions as described in 6.6.2 and 6.6.3, respectively, at the frequencies of all third and fifth order intermodulation products. The frequency band occupied by the interference signal are excluded from the measurements. + +In addition, for a multi-band capable BS, the following steps shall apply: + +- 2) For multi-band capable BS and single band tests, repeat the steps above per involved band with no carrier activated in the other band. +- 3) For multi-band capable BS with separate antenna connector, the antenna connector not being under test shall be terminated. + +NOTE: The third order intermodulation products are at frequencies $(F1 \pm 2F2)$ and $(2F1 \pm F2)$ , the fifth order intermodulation products are at frequencies $(2F1 \pm 3F2)$ , $(3F1 \pm 2F2)$ , $(4F1 \pm F2)$ and $(F1 \pm 4F2)$ , where F1 represents the frequencies within the bandwidth of the wanted signal and F2 represents the frequencies within the bandwidth of the CDMA modulated interference signal. + +#### 6.7.5 Test Requirements + +NOTE: If the Test Requirement below differs from the Minimum Requirement, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +The power level of the CDMA modulated interference signal shall be 30 dB below the rated total output power in the operating band. + +At the frequencies of all third and fifth order intermodulation products, the Test Requirements for out of band and spurious emissions as specified in subclauses 6.6.2.1.5 (Spectrum emission mask), 6.6.2.2.5 (ACLR) and 6.6.3.5 (Spurious emissions) shall be met. + +The requirement is always applicable outside the Base Station RF bandwidth or maximum radio bandwidth. + +For a BS capable of multi-band operation, the requirement applies relative to the RF bandwidth edges in each supported operating band. In case the inter RF bandwidth gap is less than 4.8 MHz, the requirement in the gap applies only for interfering signal offsets where the interfering signal falls completely within the inter RF bandwidth gap. + +## 6.8 Transmit Modulation + +### 6.8.1 Modulation accuracy + +#### 6.8.1.1 Definition and applicability + +The Error Vector Magnitude is a measure of the difference between the reference waveform and the measured waveform. This difference is called the error vector. Both waveforms pass through a matched Root Raised Cosine filter with bandwidth corresponding to the considered chip rate and roll-off $\alpha = 0,22$ . Both waveforms are then further modified by selecting the frequency, absolute phase, absolute amplitude and chip clock timing so as to minimise the error vector. The EVM result is defined as the square root of the ratio of the mean error vector power to the mean reference power expressed as a %. The measurement interval is one timeslot. The requirement is valid over the total power dynamic range as specified in section 3.1. See Annex C of this specification for further details. + +NOTE: The theoretical modulated waveform shall be calculated on the basis that the transmit pulse shaping filter is a root-raised cosine (RRC) with roll-off $\alpha = 0,22$ in the frequency domain. The impulse response of the chip impulse filter $RC_0(t)$ is + +$$RC_0(t) = \frac{\sin\left(\pi \frac{t}{T_c} (1 - \alpha)\right) + 4\alpha \frac{t}{T_c} \cos\left(\pi \frac{t}{T_c} (1 + \alpha)\right)}{\pi \frac{t}{T_c} \left(1 - \left(4\alpha \frac{t}{T_c}\right)^2\right)}$$ + +Where the roll-off factor $\alpha = 0,22$ and $T_c$ is the chip duration + +#### 6.8.1.2 Minimum Requirements + +The error vector magnitude (EVM) shall not exceed 12,5 %. The requirement is valid over the total power dynamic range as specified in section 3.1. + +The normative reference for this requirement is TS 25.105 [1] subclause 6.8.2.1. + +#### 6.8.1.3 Test purpose + +The test purpose is to verify the ability of the BS transmitter to generate a sufficient precise waveform and thus to enable the UE receiver to achieve the specified error performance. + +#### 6.8.1.4 Method of test + +##### 6.8.1.4.1 Initial conditions + +For 1,28 Mcps BS supporting 16QAM, the EVM requirements shall be tested with the general test set up specified in section 6.8.1.4.1.2 and also with the special test set up for 16QAM capable base station specified in section 6.8.1.4.1.2. + +##### 6.8.1.4.1.0 General test conditions + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested for single carrier: B, M and T; see subclause 5.3. + +RF bandwidth positions to be tested for multi-carrier: $B_{RFBW}$ , $M_{RFBW}$ and $T_{RFBW}$ in single band operation, see subclause 5.3; $B'_{RFBW}$ , $T'_{RFBW}$ and $B'_{RFBW}$ , $T'_{RFBW}$ in multi-band operation, see subclause 5.3; + +##### 6.8.1.4.1.1 3,84 Mcps TDD option - General test setup + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) Set the parameters of the BS transmitted signal according to table 6.39. For MBSFN IMB operation the set of parameters for the transmitted signals is according to IMB test model 1 in subclause 6.1.1.1. + +**Table 6.39: Parameters of the BS transmitted signal for modulation accuracy testing** + +| Parameter | Value/description | +|---------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| Number of DPCH in each time slot under test | 1 | +| Power of each DPCH | 1/9 of Base Station output power | +| BS power setting | PRAT | +| Data content of DPCH | real life (sufficient irregular) | + +#### 6.8.1.4.1.2 1,28 Mcps TDD option - General test set up + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) For a BS declared to be capable of single carrier operation only, set the parameters of the BS transmitted signal according to Table 6.39A at manufacturer's declared output power, PRAT. + +For a BS declared to be capable of multi-carrier operation, set the BS to transmit according to Table 6.39A on all carriers configured using the applicable test configuration and corresponding power setting specified in subclause 5.20 and 5.21. + +**Table 6.39A: Parameters of the BS transmitted signal for modulation accuracy testing at maximum BS output power for 1,28 Mcps TDD** + +| Parameter | Value/description | +|---------------------------------------------|----------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 6:
Transmit, if i
is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| Number of DPCH in each time slot under test | 10 | +| Power of each DPCH | 1/10 of Base Station output power | +| Data content of DPCH | real life (sufficient irregular) | + +#### 6.8.1.4.1.3 1,28 Mcps TDD option - Special test set up for 16QAM capable BS + +This test set up only applies for 16QAM capable BS. + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) For a BS declared to be capable of single carrier operation only, set the parameters of the BS transmitted signal according to table 6.39B at the manufacturer's declared output power, PRAT. + +For a BS declared to be capable of multi-carrier operation, set the BS to transmit according to Table 6.39B on all carriers configured using the applicable test configuration and corresponding power setting specified in subclause 5.20 and 5.21. + +**Table 6.39B: Parameters of the BS transmitted signal for modulation accuracy testing at maximum BS output power setting for 1,28 Mcps TDD - 16QAM capable BS** + +| Parameter | Value/description | +|-------------------------------------------------|--------------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i
is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| HS-PDSCH modulation | 16QAM | +| Number of HS-PDSCH in each time slot under test | 10 | +| Power of each HS-PDSCH | 1/10 of Base Station output power | +| Data content of HS-PDSCH | Real life (sufficient irregular) | +| Spreading factor | 16 | + +#### 6.8.1.4.1.4 3,84 Mcps TDD option - Special test set up for 16QAM capable BS + +This test set up only applies for 16QAM capable BS. + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) Set the parameters of the BS transmitted signal according to table 6.39BA. For MBSFN IMB operation the set of parameters for the transmitted signals is according to IMB test model 2 in subclause 6.1.1.2. + +**Table 6.39BA: Parameters of the BS transmitted signal for modulation accuracy testing at maximum BS output power setting for 3,84 Mcps TDD - 16QAM capable BS** + +| Parameter | Value/description | +|---------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i is
even;
receive, if i is odd. | +| Time slots under test | TS i, i even and non zero | +| HS-PDSCH modulation | 16QAM | +| Number of DPCH in each time slot under test | 9 | +| Power of each DPCH | 1/9 of Base Station output power | +| BS power setting | PRAT | +| Data content of DPCH | real life (sufficient irregular) | +| Spreading factor | 16 | + +#### 6.8.1.4.1.5 7,68 Mcps TDD option - General test setup + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) Set the parameters of the BS transmitted signal according to table 6.39BC. + +**Table 6.39BC: Parameters of the BS transmitted signal for modulation accuracy testing** + +| Parameter | Value/description | +|---------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| Number of DPCH in each time slot under test | 1 | +| Power of each DPCH | 1/9 of Base Station output power | +| BS power setting | PRAT | +| Data content of DPCH | real life (sufficient irregular) | + +#### 6.8.1.4.1.6 7,68 Mcps TDD option - Special test set up for 16QAM capable BS + +This test set up only applies for 16QAM capable BS. + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) Set the parameters of the BS transmitted signal according to table 6.39BD. + +**Table 6.39BD: Parameters of the BS transmitted signal for modulation accuracy testing at maximum BS output power setting for 7,68 Mcps TDD - 16QAM capable BS** + +| Parameter | Value/description | +|---------------------------------------------|---------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i is even;
receive, if i is odd. | +| Time slots under test | TS i, i even and non zero | +| HS-PDSCH modulation | 16QAM | +| Number of DPCH in each time slot under test | 9 | +| Power of each DPCH | 1/9 of Base Station output power | +| BS power setting | PRAT | +| Data content of DPCH | real life (sufficient irregular) | +| Spreading factor | 32 | + +#### 6.8.1.4.2 Procedure + +##### 6.8.1.4.2.1 3,84 Mcps TDD option - General procedure + +- (1) Measure the error vector magnitude (EVM) by applying the global in-channel Tx test method described in Annex C with the BS transmitted signal set as described in Table 6.39. +- (2) Set the BS transmitted signal according to Table 6.39BB and measure the error vector magnitude (EVM) by applying the global in-channel Tx test method described in Annex C. For MBSFN IMB operation the set of parameters for the transmitted signals is according to IMB test model 1 in subclause 6.1.1.1. A prerequisite for the test is that the BS output power setting is set to the maximum – 30 dB. + +**Table 6.39BB: Parameters of the BS transmitted signal for modulation accuracy testing at minimum BS output power setting for 3,84 Mcps TDD** + +| Parameter | Value/description | +|---------------------------------------------|---------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | Maximum output power - 30 dB | +| Number of DPCH in each time slot under test | 1 | +| Data content of DPCH | real life (sufficient irregular) | + +##### 6.8.1.4.2.2 1,28 Mcps TDD option - General procedure + +- (1) Measure the error vector magnitude (EVM) for each carrier by applying the global in-channel Tx test method described in Annex C with the BS transmitted signal set as described in Table 6.39A. +- (2) Measure the error vector magnitude (EVM) for each carrier by applying the global in-channel Tx test method described in Annex C with the BS transmitted signal on each carrier set as described in Table 6.39C. + +In addition, for a multi-band capable BS, the following steps shall apply: + +- (3) For multi-band capable BS and single band tests, repeat the steps above per involved band with no carrier activated in the other band. + +- (4) For multi-band capable BS with separate antenna connector, the antenna connector not being under test in case of single-band or multi-band test shall be terminated. + +**Table 6.39C: Parameters of the BS transmitted signal for modulation accuracy testing at minimum BS output power for 1,28 Mcps TDD** + +| Parameter | Value/description | +|---------------------------------------------|----------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 6:
Transmit, if i
is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slot under test | TS4, TS5 and TS6 | +| Number of DPCH in each time slot under test | 1 | +| BS output power setting on each carrier | Maximum output power - 30 dB | +| Data content of DPCH | Real life
(sufficient irregular) | + +#### 6.8.1.4.2.3 1,28 Mcps TDD option - Special procedure for 16QAM capable BS + +- (1) Measure the error vector magnitude (EVM) for each carrier by applying the global in-channel Tx test method described in Annex C with the BS transmitted signal set as described in Table 6.39B. +- (2) Measure the error vector magnitude (EVM) for each carrier by applying the global in-channel Tx test method described in Annex C with the BS transmitted signal on each carrier set as described in Table 6.39D. + +In addition, for a multi-band capable BS, the following steps shall apply: + +- (3) For multi-band capable BS and single band tests, repeat the steps above per involved band with no carrier activated in the other band. +- (4) For multi-band capable BS with separate antenna connector, the antenna connector not being under test in case of single-band or multi-band test shall be terminated. + +**Table 6.39D: Parameters of the BS transmitted signal for modulation accuracy testing at minimum BS output power setting for 1,28 Mcps TDD - 16QAM capable BS** + +| Parameter | Value/description | +|-------------------------------------------------|--------------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, 3, 4, 5, 6:
transmit, if i
is 0,4,5,6;
receive, if i is 1,2,3. | +| HS-PDSCH modulation | 16QAM | +| Time slots under test | TS4, TS5 and TS6 | +| Number of HS-PDSCH in each time slot under test | 1 | +| BS output power setting on each carrier | Maximum output power - 30 dB | +| Data content of HS-PDSCH | Real life
(sufficient irregular) | +| Spreading factor | 16 | + +#### 6.8.1.4.2.4 3,84 Mcps TDD option - Special test set up for 16QAM capable BS + +This test set up only applies for 16QAM capable BS. + +- (1) Measure the error vector magnitude (EVM) by applying the global in-channel Tx test method described in Annex C. +- (2) Set the BS transmitted signal according Table 6.39E and measure the error vector magnitude (EVM) by applying the global in-channel Tx test method described in Annex C. For MBSFN IMB operation the set of parameters for the transmitted signals is according to IMB test model 2 in subclause 6.1.1.2. A prerequisite for the test is that the BS output power setting is set to the maximum – 30 dB. + +**Table 6.39E: Parameters of the BS transmitted signal for modulation accuracy testing at minimum BS output power setting for 3,84 Mcps TDD - 16QAM capable BS** + +| Parameter | Value/description | +|-------------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | Maximum output power - 30 dB | +| HS-PDSCH modulation | 16QAM | +| Number of HS-PDSCH in each time slot under test | 1 | +| Data content of HS-PDSCH | real life (sufficient irregular) | +| Spreading factor | 16 | + +## 6.8.1.4.2.5 7,68 Mcps TDD option - General procedure + +- (1) Measure the error vector magnitude (EVM) by applying the global in-channel Tx test method described in Annex C with the BS transmitted signal set as described in Table 6.39F. +- (2) Set the BS transmitted signal according to Table 6.39F and measure the error vector magnitude (EVM) by applying the global in-channel Tx test method described in Annex C + +**Table 6.39F: Parameters of the BS transmitted signal for modulation accuracy testing at minimum BS output power setting for 7,68 Mcps TDD** + +| Parameter | Value/description | +|---------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | Maximum output power - 30 dB | +| Number of DPCH in each time slot under test | 1 | +| Data content of DPCH | real life (sufficient irregular) | + +## 6.8.1.4.2.6 7,68 Mcps TDD option - Special test set up for 16QAM capable BS + +This test set up only applies for 16QAM capable BS. + +- (1) Measure the error vector magnitude (EVM) by applying the global in-channel Tx test method described in Annex C. +- (2) Set the BS transmitted signal according Table 6.39G and measure the error vector magnitude (EVM) by applying the global in-channel Tx test method described in Annex C. + +**Table 6.39G: Parameters of the BS transmitted signal for modulation accuracy testing at minimum BS output power setting for 7,68 Mcps TDD - 16QAM capable BS** + +| Parameter | Value/description | +|-------------------------------------------------|---------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | Maximum output power- 30 dB | +| HS-PDSCH modulation | 16QAM | +| Number of HS-PDSCH in each time slot under test | 1 | +| Data content of HS-PDSCH | real life (sufficient irregular) | +| Spreading factor | 32 | + +### 6.8.1.5 Test Requirements + +NOTE: If the Test Requirement below differs from the Minimum Requirement, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +The error vector magnitude (EVM) for each carrier measured according to subclause 6.8.1.4.2 shall not exceed 12,5 %. + +## 6.8.2 Peak code domain error + +### 6.8.2.1 Definition and applicability + +The code domain error is computed by projecting the error vector power onto the code domain at a specific spreading factor. The error power for each code is defined as the ratio to the mean power of the reference waveform expressed in dB. And the Peak Code Domain Error is defined as the maximum value for Code Domain Error. The measurement interval is one timeslot. + +The requirements in this subclause shall apply to both Wide Area BS and Local Area BS. + +### 6.8.2.2 Minimum Requirements + +The peak code domain error shall not exceed -28 dB at spreading factor 16. For 7.68 Mcps, the peak code domain error shall not exceed -31 dB at spreading factor 32. + +The normative reference for this requirement is TS 25.105 [1] subclause 6.8.3.1. + +### 6.8.2.3 Test purpose + +The test purpose is to verify the ability of the BS transmitter to limit crosstalk among codes and thus to enable the UE receiver to achieve the specified error performance. + +### 6.8.2.4 Method of test + +#### 6.8.2.4.1 Initial conditions + +For 3,84 Mcps BS supporting 16QAM, the PCDE requirement shall be tested with the general test set up specified in section 6.8.2.4.1 and also with the special test set up for 16QAM capable BS specified in section 6.8.2.4.4. + +For 1,28 Mcps BS supporting 16QAM, the PCDE requirement shall be tested with the general test set up specified in section 6.8.2.4.2 and also with the special test set up for 16QAM capable BS specified in section 6.8.2.4.3. + +For 7,68 Mcps BS supporting 16QAM, the PCDE requirement shall be tested with the general test set up specified in section 6.8.2.4.1.5 and also with the special test set up for 16QAM capable BS specified in section 6.8.2.4.1.6. + +#### 6.8.2.4.1.0 General test conditions + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested for single carrier: B, M and T; see subclause 5.3. + +RF bandwidth positions to be tested for multi-carrier: $B_{RFBW}$ , $M_{RFBW}$ and $T_{RFBW}$ in single band operation, see subclause 5.3; $B_{RFBW\_T'_{RFBW}}$ and $B'_{RFBW\_T_{RFBW}}$ in multi-band operation, see subclause 5.3. + +#### 6.8.2.4.1.1 3,84 Mcps TDD option - General test set up + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) Set the parameters of the BS transmitted signal according to table 6.40. For MBSFN IMB operation the set of parameters for the transmitted signals is according to IMB test model 1 in subclause 6.1.1.1. + +**Table 6.40: Parameters of the BS transmitted signal** + +| Parameter | Value/description | +|---------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | PRAT | +| Number of DPCH in each time slot under test | 9 | +| Power of each DPCH | 1/9 of Base Station output power | +| Data content of DPCH | real life (sufficient irregular) | +| Spreading factor | 16 | + +#### 6.8.2.4.1.2 1,28 Mcps TDD option- General test set up + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) For a BS declared to be capable of single carrier operation only, set the parameters of the BS transmitted signal according to table 6.40A at manufacturer's declared output power, PRAT. + +For a BS declared to be capable of multi-carrier operation, set the BS to transmit according to Table 6.40A on all carriers configured using the applicable test configuration and corresponding power setting specified in subclause 5.20 and 5.21. + +**Table 6.40A: Parameters of the BS transmitted signal for 1,28 Mcps TDD** + +| Parameter | Value/description | +|---------------------------------------------|----------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 6:
transmit, if i
is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| Number of DPCH in each time slot under test | 10 | +| Power of each DPCH | 1/10 of Base Station output power | +| Data content of DPCH | real life (sufficient irregular) | +| Spreading factor | 16 | + +#### 6.8.2.4.1.3 1,28 Mcps TDD option - Special test set up for 16QAM capable BS + +This test set up only applies for 16QAM capable BS. + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) For a BS declared to be capable of single carrier operation only, set the parameters of the BS transmitted signal according to table 6.40B at manufacturer's declared output power, PRAT. + +For a BS declared to be capable of multi-carrier operation, set the BS to transmit according to Table 6.40B on all carriers configured using the applicable test configuration and corresponding power setting specified in subclause 5.20 and 5.21. + +**Table 6.40B: Parameters of the BS transmitted signal for 1,28 Mcps TDD - 16QAM capable BS** + +| Parameter | Value/description | +|-------------------------------------------------|----------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 6:
transmit, if i
is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| HS-PDSCH modulation | 16QAM | +| BS output power setting | PRAT | +| Number of HS-PDSCH in each time slot under test | 10 | +| Power of each HS-PDSCH | 1/10 of Base Station output power | +| Data content of HS-PDSCH | real life (sufficient irregular) | +| Spreading factor | 16 | + +#### 6.8.2.4.1.4 3,84 Mcps TDD option - Special test set up for 16QAM capable BS + +This test set up only applies for 16QAM capable BS. + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) Set the parameters of the BS transmitted signal according to table 6.40C. For MBSFN IMB operation the set of parameters for the transmitted signals is according to IMB test model 2 in subclause 6.1.1.2. + +**Table 6.40C: Parameters of the BS transmitted signal - 16QAM capable BS** + +| Parameter | Value/description | +|-------------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | PRAT | +| HS-PDSCH modulation | 16QAM | +| Number of HS-PDSCH in each time slot under test | 9 | +| Power of each HS-PDSCH | 1/9 of Base Station output power | +| Data content of HS-PDSCH | real life (sufficient irregular) | +| Spreading factor | 16 | + +#### 6.8.2.4.1.5 7,68 Mcps TDD option - General test set up + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) Set the parameters of the BS transmitted signal according to table 6.40D. + +**Table 6.40D: Parameters of the BS transmitted signal** + +| Parameter | Value/description | +|---------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | PRAT | +| Number of DPCH in each time slot under test | 9 | +| Power of each DPCH | 1/9 of Base Station output power | +| Data content of DPCH | real life (sufficient irregular) | +| Spreading factor | 32 | + +#### 6.8.2.4.1.6 7,68 Mcps TDD option - Special test set up for 16QAM capable BS + +This test set up only applies for 16QAM capable BS. + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) Set the parameters of the BS transmitted signal according to table 6.40E. + +**Table 6.40E: Parameters of the BS transmitted signal - 16QAM capable BS** + +| Parameter | Value/description | +|-------------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | PRAT | +| HS-PDSCH modulation | 16QAM | +| Number of HS-PDSCH in each time slot under test | 9 | +| Power of each HS-PDSCH | 1/9 of Base Station output power | +| Data content of HS-PDSCH | real life (sufficient irregular) | +| Spreading factor | 32 | + +#### 6.8.2.4.2 Procedure + +- 1) Measure the peak code domain error by applying the global in-channel Tx test method described in Annex C. + +In addition, for a multi-band capable BS, the following steps shall apply: + +- 2) For multi-band capable BS and single band tests, repeat the steps above per involved band with no carrier activated in the other band. +- 3) For multi-band capable BS with separate antenna connector, the antenna connector not being under test in case of single-band or multi-band test shall be terminated. + +#### 6.8.2.5 Test Requirements + +NOTE: If the Test Requirement below differs from the Minimum Requirement, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +The peak code domain error measured according to subclause 6.8.2.4.2 shall not exceed -27 dB. + +### 6.8.3 Relative Code Domain Error + +#### 6.8.3.1 Definition and applicability + +The Relative Code Domain Error is computed by projecting the error vector onto the code domain at a specified spreading factor. Only the active code channels in the composite reference waveform are considered for this requirement. The Relative Code Domain Error for every active code is defined as the ratio of the mean power of the error projection onto that code, to the mean power of the active code in the composite reference waveform. This ratio is expressed in dB. The measurement interval is one timeslot. + +The requirement for Relative Code Domain Error is only applicable for 64QAM modulated codes. + +#### 6.8.3.2 Minimum requirement + +The average Relative Code Domain Error for 64QAM modulated codes shall not exceed -21.9dB at spreading factor 16. The normative reference for this requirement is TS 25.105 [1] subclause 6.8.4.1 + +#### 6.8.3.3 Test Purpose + +It is the purpose of this test to verify that the Relative Code Domain Error is within the limit specified by 6.8.3.2. + +### 6.8.3.4 Method of test + +#### 6.8.3.4.1 Initial conditions + +For 1,28 Mcps BS supporting 64QAM, the RCDE requirement shall be tested with the general test set up specified in section 6.8.3.4.1.1 and also with the special test set up for 64QAM capable BS specified in section 6.8.3.4.1.2. + +##### 6.8.3.4.1.0 General test conditions + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested for single-carrier: B, M and T; see subclause 5.3. + +RF bandwidth positions to be tested for multi-carrier: $B_{RFBW}$ , $M_{RFBW}$ and $T_{RFBW}$ in single band operation, see subclause 5.3; $B_{RFBW\_T}^{RFBW}$ and $B_{RFBW\_T}^{RFBW}$ in multi-band operation, see subclause 5.3; + +##### 6.8.3.4.1.1 1.28 Mcps TDD option- General test set up + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) For a BS declared to be capable of single carrier operation only, set the parameters of the BS transmitted signal according to table 6.41 at manufacturer's declared output power, PRAT. + +For a BS declared to be capable of multi-carrier operation, set the BS to transmit according to table 6.41 on all carriers configured using the applicable test configuration and corresponding power setting specified in subclause 5.20 and 5.21. + +**Table 6.41: Parameters of the BS transmitted signal for 1,28 Mcps TDD** + +| Parameter | Value/description | +|-------------------------------------------------|-------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 6:
transmit, if i is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| Number of HS-PDSCH in each time slot under test | 10 | +| Power of each HS-PDSCH | 1/10 of Base Station output power | +| Data content of HS-PDSCH | real life (sufficient irregular) | +| Spreading factor | 16 | + +##### 6.8.3.4.1.2 1.28 Mcps TDD option - Special test set up for 64QAM capable BS + +This test set up only applies for 64QAM capable BS. + +- (1) Connect the measuring equipment to the antenna connector of the BS under test. +- (2) For a BS declared to be capable of single carrier operation only, set the parameters of the BS transmitted signal according to table 6.41A at manufacturer's declared output power, PRAT. + +For a BS declared to be capable of multi-carrier operation, set the BS to transmit according to Table 6.41A on all carriers configured using the applicable test configuration and corresponding power setting specified in subclause 5.20 and 5.21. + +**Table 6.41A: Parameters of the BS transmitted signal for 1,28 Mcps TDD - 64QAM capable BS** + +| Parameter | Value/description | +|-------------------------------------------------|----------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 6:
transmit, if i
is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS4, TS5 and TS6 | +| HS-PDSCH modulation | 64QAM | +| Number of HS-PDSCH in each time slot under test | 10 | +| Power of each HS-PDSCH | 1/10 of Base Station output power | +| Data content of HS-PDSCH | real life (sufficient irregular) | +| Spreading factor | 16 | + +#### 6.8.3.4.2 Procedure + +- 1) Measure the Relative code domain error by applying the global in-channel Tx test method described in Annex C. + +In addition, for a multi-band capable BS, the following steps shall apply: + +- 2) For multi-band capable BS and single band tests, repeat the steps above per involved band with no carrier activated in the other band. +- 3) For multi-band capable BS with separate antenna connector, the antenna connector not being under test in case of single-band or multi-band test shall be terminated. + +#### 6.8.3.5 Test Requirements + +NOTE: If the Test Requirement below differs from the Minimum Requirement, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +The Relative code domain error measured according to subclause 6.8.3.4.2 shall not exceed -20.9 dB. + +### 6.8.4 Time alignment error in MIMO transmission + +#### 6.8.4.1 Definition and applicability + +In MIMO transmission, signals are transmitted from two or more antennas. These signals shall be aligned. The time alignment error in MIMO transmission is specified as the delay between the signals from two antennas at the antenna ports. + +This test is only applicable for Node B supporting MIMO transmission. + +#### 6.8.4.2 Minimum requirement + +The time alignment error in MIMO for any possible configuration of two transmit antennas shall not exceed 65 ns. + +The normative reference for this requirement is TS 25.105 [1] subclause 6.8.5.1. + +#### 6.8.4.3 Test Purpose + +It is the purpose of this test to verify that the timing alignment error in MIMO is within the limit specified in 6.8.4.2. + +#### 6.8.4.4 Method of test + +##### 6.8.4.4.1 Initial conditions + +For 1,28 Mcps BS supporting MIMO transmission, the time alignment error shall be tested with the general test set up specified in section 6.8.4.4.1.1. + +###### 6.8.4.4.1.0 General test conditions + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested for single-carrier: Middle; see subclause 5.3. + +RF bandwidth positions to be tested for multi-carrier: $M_{RFBW}$ in single band operation, see subclause 5.3. + +#### 6.8.4.4.1.1 1.28 Mcps TDD option- General test set up + +- 1) Connect two base station RF antenna ports to the measurement equipment as shown in Figure 6.6. If available terminate the other unused antenna ports. + +![Figure 6.6: Measuring system Set-up for Test of Time alignment error. The diagram shows a 'BS under TX test' block with four 'TX' ports. The first two TX ports are connected to a 'Timing analyzer'. The third TX port is connected to a 'Termination' block via an ellipsis. The fourth TX port is connected to another 'Termination' block via an ellipsis.](5635bd67a8ba929382fd61dede8952c7_img.jpg) + +Figure 6.6: Measuring system Set-up for Test of Time alignment error. The diagram shows a 'BS under TX test' block with four 'TX' ports. The first two TX ports are connected to a 'Timing analyzer'. The third TX port is connected to a 'Termination' block via an ellipsis. The fourth TX port is connected to another 'Termination' block via an ellipsis. + +**Figure 6.6: Measuring system Set-up for Test of Time alignment error** + +- 2) For a BS declared to be capable of single carrier operation only, set the base station to transmit according to table 6.42 on one cell using MIMO, at manufacturer's declared output power, PRAT. + +For a FDD BS declared to be capable of multi-carrier operation, set the BS to transmit according to table 6.42 on all carriers configured using the applicable test configuration and corresponding power setting specified in subclause 5.20 and 5.21. + +**Table 6.42: Parameters of the BS transmitted signal for 1,28 Mcps TDD** + +| Parameter | Value/description | +|-----------------------|-------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 6:
transmit, if i is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS0 and DwPTS | +| Spreading factor | 16 | + +#### 6.8.4.4.2 Procedure + +##### 6.8.4.4.2.1 1.28 Mcps TDD option + +- 1) Start BS transmission at the manufacturer's specified maximum output power. +- 2) Measure the time alignment error between the P-CCPCH and DwPTS on the antenna ports under test. +- 3) Repeat the measurement for any other possible configuration of 2 transmit antennas. + +In addition, for a multi-band capable BS, the following steps shall apply: + +- 4) For multi-band capable BS and single band tests, repeat the steps above per involved band with no carrier activated in the other band. +- 5) For multi-band capable BS with separate antenna connector, the antenna connector not being under test in case of single-band or multi-band test shall be terminated. + +#### 6.8.4.5 Test Requirements + +NOTE: If the Test Requirement below differs from the Minimum Requirement, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +### 6.8.4.5.1 1.28 Mcps TDD option + +The time alignment error shall be less than $65 + [78]$ ns. + +## 7 Receiver characteristics + +### 7.1 General + +The requirements in clause 7 are expressed for a single receiver antenna connector. For receivers with antenna diversity, the requirements apply for each receiver antenna connector. + +For ACS, blocking and intermodulation characteristics, the negative offsets of the interfering signal apply relative to the assigned channel frequency of the lowest carrier frequency used and positive offsets of the interfering signal apply relative to the assigned channel frequency of the highest carrier frequency used. + +A BS supporting 1.28 Mcps MC-HSUPA receives multiple carriers simultaneously on adjacent carrier frequencies. + +All tests unless otherwise stated in this subclause shall be conducted on Base Station Systems fitted with a full complement of Transceivers for the configuration. The manufacturer shall provide appropriate logical or physical test access to perform all tests in this subclause. Measurements shall include any RX multicoupler. + +In all the relevant subclauses in this clause all Bit Error Ratio (BER), Residual BER (RBER) and Frame Erasure Ratio (FER) measurements shall be carried out according to the general rules for statistical testing defined in ITU-T Recommendation O.153 [10] and Annex F. + +The BER requirements defined for the receiver characteristics in this clause do not assume HARQ transmissions. + +When the BS is configured to receive multiple carriers, all the BER requirements are applicable for each received carrier. + +Unless otherwise stated, all tests in this clause shall be performed at the BS antenna connector (test port A). If any external apparatus such as a RX amplifier, a filter or the combination of such devices is used, the tests according to subclauses 5.14.4 shall be performed to ensure that the requirements are met at test port B. + +![Diagram of receiver test ports showing a BS cabinet connected to an External LNA (if any) and an External device (e.g. RX filter). Test port A is at the BS cabinet connector, and Test port B is at the External device connector. A signal path is shown from the antenna connector through the external devices to the BS cabinet.](4930881b4cec8929388e16e4f7be512d_img.jpg) + +The diagram illustrates the signal flow and test points for receiver testing. On the left is a box labeled 'BS cabinet'. A cable connects its right-side connector to a box labeled 'External LNA (if any)'. This cable has a label 'Test port A' pointing to the connector on the BS cabinet. Another cable connects the 'External LNA' box to a third box labeled 'External device e.g. RX filter'. A dashed line with an arrow points from the right side of the 'External device' box, labeled 'From antenna connector'. This dashed line has a label 'Test port B' pointing to the connector on the 'External device' box. The signal path is from right to left, starting from the antenna, through the external device, then the external LNA, and finally into the BS cabinet. + +Diagram of receiver test ports showing a BS cabinet connected to an External LNA (if any) and an External device (e.g. RX filter). Test port A is at the BS cabinet connector, and Test port B is at the External device connector. A signal path is shown from the antenna connector through the external devices to the BS cabinet. + +Figure 7.1: Receiver test ports + +### 7.2 Reference sensitivity level + +#### 7.2.1 Definition and applicability + +The reference sensitivity level is the minimum mean power received at the antenna connector at which the BER shall not exceed the specific value. + +## 7.2.2 Minimum Requirements + +### 7.2.2.1 3,84 Mcps TDD option + +Using the reference measurement channel specified in Annex A.2.1, the reference sensitivity level and performance of the BS shall be as specified in table 7.1. + +**Table 7.1: Minimum Requirements for BS reference sensitivity level** + +| BS class | Reference measurement channel data rate | BS reference sensitivity level | BER | +|---------------|-----------------------------------------|--------------------------------|----------------------------| +| Wide Area BS | 12,2 kbps | -109 dBm | BER shall not exceed 0,001 | +| Local Area BS | 12,2 kbps | -95 dBm | BER shall not exceed 0,001 | + +The normative reference for this requirement is TS 25.105 [1] subclause 7.2.1.1. + +### 7.2.2.2 1,28 Mcps option + +Using the reference measurement channel specified in Annex A.2.1.2, the reference sensitivity level and performance of the BS shall be as specified in table 7.1A. + +**Table 7.1A: Minimum Requirements for BS reference sensitivity level (1,28 Mcps option)** + +| BS class | Reference measurement channel data rate | BS reference sensitivity level | BER | +|---------------|-----------------------------------------|--------------------------------|----------------------------| +| Wide Area BS | 12,2 kbps | -110 dBm | BER shall not exceed 0,001 | +| Local Area BS | 12,2 kbps | -96 dBm | BER shall not exceed 0,001 | +| Home BS | 12,2 kbps | -101 dBm | BER shall not exceed 0,001 | + +The normative reference for this requirement is TS 25.105 [1] subclause 7.2.1.2. + +### 7.2.2.3 7,68 Mcps TDD option + +Using the reference measurement channel specified in Annex A.2.1, the reference sensitivity level and performance of the BS shall be as specified in table 7.1B. + +**Table 7.1B: Minimum Requirements for BS reference sensitivity level** + +| BS class | Reference measurement channel data rate | BS reference sensitivity level | BER | +|---------------|-----------------------------------------|--------------------------------|----------------------------| +| Wide Area BS | 12,2 kbps | -109 dBm | BER shall not exceed 0,001 | +| Local Area BS | 12,2 kbps | -95 dBm | BER shall not exceed 0,001 | + +The normative reference for this requirement is TS 25.105 [1] subclause 7.2.1.3. + +## 7.2.3 Test purpose + +The test purpose is to verify the ability of the BS to receive a prescribed single-code test signal of minimum input power under defined conditions (no interference, no multipath propagation) with a BER not exceeding a specified limit. This test is also used as a reference case for other tests to allow the assessment of degradations due to various sources of interference. + +## 7.2.4 Method of test + +### 7.2.4.1 Initial conditions + +#### 7.2.4.1.0 General test requirements + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested: B, M and T; see subclause 5.3. + +The following additional test shall be performed: + +On each of B, M and T, the test shall be performed under extreme power supply as defined in subclause 5.9.4. + +NOTE: Tests under extreme power supply also test extreme temperature. + +#### 7.2.4.1.1 3,84 Mcps TDD option + +- (1) Connect the BS tester (UE simulator) to the antenna connector of one BS Rx port. +- (2) Terminate or disable any other BS Rx port not under test. +- (3) Start transmission from the BS tester to the BS using the UL reference measurement channel (12.2 kbps) defined in Annex A.2.1. +- (4) The level of the BS tester output signal measured at the BS antenna connector shall be adjusted to the Test Requirement for the BS reference sensitivity level specified in table 7.2. + +#### 7.2.4.1.2 1,28 Mcps TDD option + +- (1) Connect the BS tester (UE simulator) to the antenna connector of one BS Rx port. +- (2) Terminate or disable any other BS Rx port not under test. +- (3) Start transmission from the BS tester to the BS using the UL reference measurement channel (12.2 kbps) defined in Annex A.2.1. +- (4) The level of BS tester output signal measured at the BS antenna connector shall be adjusted according to Table 7.1A. + +#### 7.2.4.1.3 7,68 Mcps TDD option + +- (1) Connect the BS tester (UE simulator) to the antenna connector of one BS Rx port. +- (2) Terminate or disable any other BS Rx port not under test. +- (3) Start transmission from the BS tester to the BS using the UL reference measurement channel (12.2 kbps) defined in Annex A.2.1. +- (4) The level of the BS tester output signal measured at the BS antenna connector shall be adjusted to the Test Requirement for the BS reference sensitivity level specified in table 7.2B. + +#### 7.2.4.2 Procedure + +- (1) Calculate BER according to annex F. +- (2) Interchange the connections of the BS Rx ports and repeat the measurement according to (1). + +In addition, for a multi-band capable BS, the following steps shall apply: + +- (3) For multi-band capable BS and single band tests, repeat the steps above per involved band with no carrier activated in the other band. +- (4) For multi-band capable BS with separate antenna connector, the antenna connector not being under test shall be terminated. + +### 7.2.5 Test Requirements + +NOTE: If the Test Requirements below differ from the Minimum Requirements, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +### 7.2.5.1 3,84 Mcps TDD option + +For any BS Rx port tested, the measured BER at the Test Requirement of the BS reference sensitivity level specified in table 7.2 shall not exceed 0,001. + +**Table 7.2: Test Requirement for BS reference sensitivity level** + +| BS class | Reference measurement channel data rate | BS reference sensitivity level | BER | +|---------------|-----------------------------------------|--------------------------------|----------------------------| +| Wide Area BS | 12,2 kbps | -108,3 dBm | BER shall not exceed 0,001 | +| Local Area BS | 12,2 kbps | -94,3 dBm | BER shall not exceed 0,001 | + +### 7.2.5.2 1,28 Mcps TDD option + +For any BS Rx port tested, the measured BER at the Test Requirement of the BS reference sensitivity level specified in table 7.2A shall not exceed 0,001. + +**Table 7.2A: Test Requirement for BS reference sensitivity level for 1,28 Mcps option** + +| BS class | Reference measurement channel data rate | BS reference sensitivity level | BER | +|---------------|-----------------------------------------|--------------------------------|----------------------------| +| Wide Area BS | 12,2 kbps | -109,3 dBm | BER shall not exceed 0,001 | +| Local Area BS | 12,2 kbps | -95,3 dBm | BER shall not exceed 0,001 | +| Home BS | 12,2 kbps | -100,3 dBm | BER shall not exceed 0,001 | + +### 7.2.5.3 7,68 Mcps TDD option + +For any BS Rx port tested, the measured BER at the Test Requirement of the BS reference sensitivity level specified in table 7.2B shall not exceed 0,001. + +**Table 7.2B: Test Requirement for BS reference sensitivity level** + +| BS class | Reference measurement channel data rate | BS reference sensitivity level | BER | +|---------------|-----------------------------------------|--------------------------------|----------------------------| +| Wide Area BS | 12,2 kbps | -108,3 dBm | BER shall not exceed 0,001 | +| Local Area BS | 12,2 kbps | -94,3 dBm | BER shall not exceed 0,001 | + +## 7.3 Dynamic range + +### 7.3.1 Definition and applicability + +Receiver dynamic range is the receiver ability to handle a rise of interference in the reception frequency channel. The receiver shall fulfil a specified BER requirement for a specified sensitivity degradation of the wanted signal in the presence of an interfering AWGN signal in the same reception frequency channel. + +### 7.3.2 Minimum Requirements + +#### 7.3.2.1 3,84 Mcps TDD option + +The BER shall not exceed 0,001 for the parameters specified in table 7.3. + +**Table 7.3: Minimum Requirements for Dynamic Range** + +| Parameter | | Level | Unit | +|-----------------------------------------|---------------|-------|--------------| +| Reference measurement channel data rate | | 12,2 | kbit/s | +| Wanted signal mean power | Wide Area BS | -79 | dBm | +| | Local Area BS | -65 | dBm | +| Interfering AWGN signal | Wide Area BS | -73 | dBm/3,84 MHz | +| | Local Area BS | -59 | dBm/3,84 MHz | + +The normative reference for this requirement is TS 25.105 [1] subclause 7.3.1.1. + +### 7.3.2.2 1,28 Mcps TDD option + +The BER shall not exceed 0,001 for the parameters specified in table 7.3A. + +**Table 7.3A: Minimum Requirements for Dynamic Range for 1,28 Mcps TDD** + +| Parameter | | Level | Unit | +|-----------------------------------------|---------------|-------|--------------| +| Reference measurement channel data rate | | 12,2 | kbit/s | +| Wanted signal mean power | Wide Area BS | -80 | dBm | +| | Local Area BS | -66 | dBm | +| | Home BS | -51 | dBm | +| Interfering AWGN signal | Wide Area BS | -76 | dBm/1,28 MHz | +| | Local Area BS | -62 | dBm/1,28 MHz | +| | Home BS | -47 | dBm | + +The normative reference for this requirement is TS 25.105 [1] subclause 7.3.1.2. + +### 7.3.2.3 7,68 Mcps TDD option + +The BER shall not exceed 0,001 for the parameters specified in table 7.3B. + +**Table 7.3B: Minimum Requirements for Dynamic Range** + +| Parameter | | Level | Unit | +|-----------------------------------------|---------------|-------|--------------| +| Reference measurement channel data rate | | 12,2 | kbit/s | +| Wanted signal mean power | Wide Area BS | -79 | dBm | +| | Local Area BS | -65 | dBm | +| Interfering AWGN signal | Wide Area BS | -70 | dBm/7,68 MHz | +| | Local Area BS | -56 | dBm/7,68 MHz | + +The normative reference for this requirement is TS 25.105 [1] subclause 7.3.1.3. + +## 7.3.3 Test purpose + +The test purpose is to verify the ability of the BS to receive a prescribed single-code test signal of maximum input power under defined conditions (specified interference, no multipath) with a BER not exceeding a specified limit. + +## 7.3.4 Method of test + +### 7.3.4.1 Initial conditions + +#### 7.3.4.1.0 General test conditions + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested: B, M and T; see subclause 5.3. + +#### 7.3.4.1.1 3,84 Mcps TDD option + +- (1) Connect the BS tester (UE simulator), generating the wanted signal, and a band-limited white noise source, generating the interfering AWGN signal, to the antenna connector of one BS Rx port. +- (2) Terminate or disable any other BS Rx port not under test. +- (3) Start transmission from the BS tester to the BS using the UL reference measurement channel (12,2 kbps) defined in Annex A.2.1. +- (4) The level of the BS tester output signal measured at the BS antenna connector shall be adjusted as specified in table 7.4. +- (5) The power spectral density of the band-limited white noise source measured at the BS antenna connector shall be adjusted as specified in table 7.4. The characteristics of the white noise source shall comply with the AWGN interferer definition in subclause 5.18 + +#### 7.3.4.1.2 1,28 Mcps TDD option + +- (1) Connect the BS tester (UE simulator), generating the wanted signal, and a band-limited white noise source, generating the interfering AWGN signal, to the antenna connector of one BS Rx port. +- (2) Terminate or disable any other BS Rx port not under test. +- (3) Start transmission from the BS tester to the BS using the UL reference measurement channel (12,2 kbps) defined in Annex A.2.1. +- (4) The level of the BS tester output signal measured at the BS antenna connector shall be adjusted as specified in table 7.3A. +- (5) The power spectral density of the band-limited white noise source measured at the BS antenna connector shall be adjusted as specified in table 7.3A. The characteristics of the white noise source shall comply with the AWGN interferer definition in subclause 5.18. + +#### 7.3.4.1.3 7,68 Mcps TDD option + +- (1) Connect the BS tester (UE simulator), generating the wanted signal, and a band-limited white noise source, generating the interfering AWGN signal, to the antenna connector of one BS Rx port. +- (2) Terminate or disable any other BS Rx port not under test. +- (3) Start transmission from the BS tester to the BS using the UL reference measurement channel (12,2 kbps) defined in Annex A.2.1. +- (4) The level of the BS tester output signal measured at the BS antenna connector shall be adjusted as specified in table 7.4B. +- (5) The power spectral density of the band-limited white noise source measured at the BS antenna connector shall be adjusted as specified in table 7.4B. The characteristics of the white noise source shall comply with the AWGN interferer definition in subclause 5.18 + +#### 7.3.4.2 Procedure + +- (1) Measure the BER by comparing the bit sequence of the information data transmitted by the BS tester with the bit sequence obtained from the BS receiver. +- (2) Interchange the connections of the BS Rx ports and repeat the measurement according to (1). + +In addition, for a multi-band capable BS, the following steps shall apply: + +- (3) For multi-band capable BS and single band tests, repeat the steps above per involved band with no carrier activated in the other band. +- (4) For multi-band capable BS with separate antenna connector, the antenna connector not being under test shall be terminated. + +## 7.3.5 Test Requirements + +NOTE: If the Test Requirement below differs from the Minimum Requirement, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +### 7.3.5.1 3,84 Mcps TDD option + +For any BS Rx port tested, the measured BER shall not exceed 0,001 for the parameters specified in table 7.4. + +**Table 7.4: Test Requirements for Dynamic Range** + +| Parameter | | Level | Unit | +|-----------------------------------------|---------------|-------|--------------| +| Reference measurement channel data rate | | 12,2 | kbit/s | +| Wanted signal mean power | Wide Area BS | -77,8 | dBm | +| | Local Area BS | -63,8 | dBm | +| Interfering AWGN signal | Wide Area BS | -73 | dBm/3,84 MHz | +| | Local Area BS | -59 | dBm/3,84 MHz | + +### 7.3.5.2 1,28 Mcps TDD option + +For any BS Rx port tested, the measured BER shall not exceed 0,001 for the parameters specified in table 7.4A. + +**Table 7.4A: Test Requirements for Dynamic Range for 1,28 Mcps TDD option** + +| Parameter | | Level | Unit | +|-----------------------------------------|---------------|-------|--------------| +| Reference measurement channel data rate | | 12,2 | kbit/s | +| Wanted signal mean power | Wide Area BS | -78,8 | dBm | +| | Local Area BS | -64,8 | dBm | +| | Home BS | -49,8 | dBm/1,28 MHz | +| Interfering AWGN signal | Wide Area BS | -76 | dBm/1,28 MHz | +| | Local Area BS | -62 | dBm/1,28 MHz | +| | Home BS | -47 | dBm/1,28 MHz | + +### 7.3.5.3 7,68 Mcps TDD option + +For any BS Rx port tested, the measured BER shall not exceed 0,001 for the parameters specified in table 7.4B. + +**Table 7.4B: Test Requirements for Dynamic Range** + +| Parameter | | Level | Unit | +|-----------------------------------------|---------------|-------|--------------| +| Reference measurement channel data rate | | 12,2 | kbit/s | +| Wanted signal mean power | Wide Area BS | -77,8 | dBm | +| | Local Area BS | -63,8 | dBm | +| Interfering AWGN signal | Wide Area BS | -70 | dBm/7,68 MHz | +| | Local Area BS | -56 | dBm/7,68 MHz | + +## 7.4 Adjacent Channel Selectivity (ACS) + +### 7.4.1 Definition and applicability + +Adjacent channel selectivity (ACS) is a measure of the receiver ability to receive a wanted signal at its assigned channel frequency in the presence of a single code CDMA modulated adjacent channel signal at a given frequency offset from the center frequency of the assigned channel. + +## 7.4.2 Minimum Requirements + +### 7.4.2.1 3,84 Mcps TDD option + +The BER, measured on the wanted signal in the presence of an interfering signal, shall not exceed 0,001 for the parameters specified in table 7.5. + +**Table 7.5: Parameters of the wanted signal and the interfering signal for ACS testing** + +| Parameter | | Level | Unit | +|--------------------------------------------------------------------------------------------------------------------------------|---------------|-------|--------| +| Reference measurement channel data rate | | 12,2 | kbit/s | +| Wanted signal mean power | Wide Area BS | -103 | dBm | +| | Local Area BS | -89 | dBm | +| Interfering signal mean power | Wide Area BS | -52 | dBm | +| | Local Area BS | -38 | dBm | +| Fuw (modulated) | | 5 | MHz | +| NOTE: Fuw is the frequency offset of the unwanted interfering signal from the assigned channel frequency of the wanted signal. | | | | + +The normative reference for this requirement is TS 25.105 [1] subclause 7.4.1.1. + +### 7.4.2.2 1,28 Mcps TDD option + +The BER, measured on the wanted signal in the presence of an interfering signal, shall not exceed 0,001 for the parameters specified in table 7.5A. + +The ACS requirement is always applicable outside the Base Station RF bandwidth or maximum radio bandwidth edges. The interfering signal offset is defined relative to the lower (upper) or maximum radio bandwidth edges. + +For BS capable of multi-band operation, the requirement applies in addition inside any inter RF bandwidth gap as long as the inter RF bandwidth gap size is at least 1.6MHz. The interfering signal offset is defined relative to lower/upper RF bandwidth edges inside the inter RF bandwidth gap and is equal to -0.8MHz/+0.8MHz, respectively. + +**Table 7.5A: Parameters of the wanted signal and the interfering signal for ACS testing for 1,28 Mcps TDD** + +| Parameter | | Level | Unit | +|--------------------------------------------------------------------------------------------------------------------------------|---------------|-------|--------| +| Reference measurement channel data rate | | 12,2 | kbit/s | +| Wanted signal mean power | Wide Area BS | -104 | dBm | +| | Local Area BS | -90 | dBm | +| | Home BS | -77 | dBm | +| Interfering signal mean power | Wide Area BS | -55 | dBm | +| | Local Area BS | -41 | dBm | +| | Home BS | -28 | dBm | +| Fuw (modulated) | | ±1,6 | MHz | +| NOTE: Fuw is the frequency offset of the unwanted interfering signal from the assigned channel frequency of the wanted signal. | | | | + +The normative reference for this requirement is TS 25.105 [1] subclause 7.4.1.2. + +### 7.4.2.3 7,68 Mcps TDD option + +The BER, measured on the wanted signal in the presence of an interfering signal, shall not exceed 0,001 for the parameters specified in table 7.5B. + +**Table 7.5B: Parameters of the wanted signal and the interfering signal for ACS testing** + +| Parameter | | Level | Unit | +|--------------------------------------------------------------------------------------------------------------------------------------------|---------------|-------|--------| +| Reference measurement channel data rate | | 12,2 | kbit/s | +| Wanted signal mean power | Wide Area BS | -103 | dBm | +| | Local Area BS | -89 | dBm | +| Interfering signal mean power | Wide Area BS | -49 | dBm | +| | Local Area BS | -35 | dBm | +| F uw (modulated) | | 10 | MHz | +| NOTE: F uw is the frequency offset of the unwanted interfering signal from the assigned channel frequency of the wanted signal. | | | | + +The normative reference for this requirement is TS 25.105 [1] subclause 7.4.1.3. + +## 7.4.3 Test purpose + +The test purpose is to verify the ability of the BS receiver filter to sufficiently suppress interfering signals in the channels adjacent to the wanted channel. + +## 7.4.4 Method of test + +### 7.4.4.1 Initial conditions + +#### 7.4.4.1.0 General test conditions + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested for single-carrier: B, M and T; see subclause 5.3. + +RF bandwidth positions to be tested for multi-carrier: $M_{RFBW}$ in single band operation, see subclause 5.3; $B_{RFBW\_T'_{RFBW}}$ and $B'_{RFBW\_T_{RFBW}}$ in multi-band operation, see subclause 5.3. + +#### 7.4.4.1.1 3,84 Mcps TDD option + +- (1) Connect an UE simulator operating at the assigned channel frequency of the wanted signal and a signal generator used to produce the interfering signal in the adjacent channel to the antenna connector of one Rx port. +- (2) Terminate or disable any other Rx port not under test. +- (3) Start transmission from the BS tester to the BS using the UL reference measurement channel (12,2 kbps) defined in Annex A.2.1. The level of the UE simulator signal measured at the BS antenna connector shall be adjusted to the value specified in table 7.5. +- (4) Set the signal generator to produce an interfering signal that is equivalent to a continuous wideband CDMA signal with one code of chip frequency 3,84 Mchip/s, filtered by an RRC transmit pulse-shaping filter with roll-off $\alpha = 0,22$ . The mean power level of the interfering signal measured at the BS antenna connector shall be adjusted to the value specified in table 7.5. + +#### 7.4.4.1.2 1,28 Mcps TDD option + +- (1) Generate the wanted signal according to the test configurations in subclauses 5.20 and 5.21 and adjust the input level to the base station under test according to Table 7.5A. The UL reference measurement channel (12,2 kbps) defined in Annex A.2.1 shall be used for each wanted carrier. +- (2) Set-up the interfering signal at the adjacent channel frequency and adjust the interfering signal level at the base station input according to Table 7.5A. The interfering signal is equivalent to a continuous CDMA signal with one code of chip frequency 1,28 Mchip/s, filtered by an RRC transmit pulse-shaping filter with roll-off $\alpha = 0,22$ . + +#### 7.4.4.1.3 7,68 Mcps TDD option + +- (1) Connect an UE simulator operating at the assigned channel frequency of the wanted signal and a signal generator used to produce the interfering signal in the adjacent channel to the antenna connector of one Rx port. + +- (2) Terminate or disable any other Rx port not under test. +- (3) Start transmission from the BS tester to the BS using the UL reference measurement channel (12,2 kbps) defined in Annex A.2.1. The level of the UE simulator signal measured at the BS antenna connector shall be adjusted to the value specified in table 7.5B. +- (4) Set the signal generator to produce an interfering signal that is equivalent to a continuous wideband CDMA signal with one code of chip frequency 7,68 Mchip/s, filtered by an RRC transmit pulse-shaping filter with roll-off $\alpha = 0,22$ . The mean power level of the interfering signal measured at the BS antenna connector shall be adjusted to the value specified in table 7.5B. + +#### 7.4.4.2 Procedure + +##### 7.4.4.2.1 3,84 Mcps TDD option + +- (1) Set the center frequency of the interfering signal to 5 MHz above the assigned channel frequency of the wanted signal. +- (2) Measure the BER of the wanted signal at the BS receiver. +- (3) Set the center frequency of the interfering signal to 5 MHz below the assigned channel frequency of the wanted signal. +- (4) Measure the BER of the wanted signal at the BS receiver. +- (5) Interchange the connections of the BS Rx ports and repeat the measurements according to steps (1) to (4). + +##### 7.4.4.2.2 1,28 Mcps TDD option + +- (1) Measure the BER of the wanted signal at the BS receiver. +- (2) Repeat the test for the other port(s), which was (were) terminated, + +In addition, for a multi-band capable BS, the following steps shall apply: + +- (3) For multi-band capable BS and single band tests, repeat the steps above per involved band with no carrier activated in the other band. +- (4) For multi-band capable BS with separate antenna connector, the antenna connector not being under test shall be terminated. + +##### 7.4.4.2.3 7,68 Mcps TDD option + +- (1) Set the center frequency of the interfering signal to 10 MHz above the assigned channel frequency of the wanted signal. +- (2) Measure the BER of the wanted signal at the BS receiver. +- (3) Set the center frequency of the interfering signal to 10 MHz below the assigned channel frequency of the wanted signal. +- (4) Measure the BER of the wanted signal at the BS receiver. +- (5) Interchange the connections of the BS Rx ports and repeat the measurements according to steps (1) to (4). + +#### 7.4.5 Test Requirements + +NOTE: If the Test Requirement below differs from the Minimum Requirement, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +The BER measured according to subclause 7.4.4.2 shall not exceed 0,001. + +## 7.5 Blocking characteristics + +### 7.5.1 Definition and applicability + +#### 7.5.1.1 3,84 Mcps TDD option + +The blocking characteristics is a measure of the receiver ability to receive a wanted signal at its assigned channel frequency in the presence of an unwanted interferer on frequencies other than those of the adjacent channels. The blocking performance requirements apply to interfering signals with center frequency within the ranges specified in tables 7.6-1, 7.7-1, 7.8-1, 7.9-1, 7.6-2, 7.7-2, 7.8-2, 7.9-2, 7.9 and 7.10 respectively, using a 1 MHz step size. + +In this subclause, different requirements shall apply to Wide Area BS and Local Area BS. The requirements in tables 7.6-1, 7.7-1, 7.8-1, 7.9-1 apply to Wide Area BS, and the requirements in tables 7.6-2, 7.7-2, 7.8-2 or 7.9-2 apply to Local Area BS, depending on which frequency band is used. The additional requirements in Tables 7.9 and 7.10 may be applied for the protection of TDD BS receivers when GSM900 and/or DCS1800 BTS are co-located with UTRA TDD Wide Area BS. + +#### 7.5.1.2 1,28 Mcps TDD option + +The blocking characteristics is a measure of the receiver ability to receive a wanted signal at its assigned channel frequency in the presence of an unwanted interferer on frequencies other than those of the adjacent channels. The interfering signal are either a narrow band CDMA signal with one code for in-band blocking or a CW signal for out-of-band. + +The requirements shall apply to BS class, depending on which frequency band is used. + +#### 7.5.1.3 7,68 Mcps TDD option + +The blocking characteristics is a measure of the receiver ability to receive a wanted signal at its assigned channel frequency in the presence of an unwanted interferer on frequencies other than those of the adjacent channels. The blocking performance requirements apply to interfering signals with center frequency within the ranges specified in tables 7.6-1B, 7.7-1B, 7.8-1B, 7.6-2B, 7.7-2B, 7.8-2B, 7.9B and 7.10F respectively, using a 1 MHz step size. + +In this subclause, different requirements shall apply to Wide Area BS and Local Area BS. The requirements in tables 7.6-1B, 7.7-1B or 7.8-1B apply to Wide Area BS, and the requirements in tables 7.6-2B, 7.7-2B or 7.8-2B apply to Local Area BS, depending on which frequency band is used. The additional requirements in Tables 7.9B and 7.10F may be applied for the protection of TDD BS receivers when GSM900 and/or DCS1800 BTS are co-located with UTRA TDD Wide Area BS. + +### 7.5.2 Minimum Requirements + +#### 7.5.2.1 3,84 Mcps TDD option + +##### 7.5.2.1.1 General requirements + +The static reference performance as specified in clause 7.2 shall be met with a wanted and an interfering signal coupled to the BS antenna input using the parameters specified in tables 7.6-1, 7.7-1, 7.8-1, 7.9-1, 7.6-2, 7.7-2, 7.8-2 or 7.9-2, respectively. + +**Table 7.6-1: Blocking requirements for Wide Area BS in operating bands defined in subclause 4.2 a)** + +| Center frequency of interfering signal | Interfering signal mean power | Wanted signal mean power | Minimum offset of interfering signal | Type of interfering signal | +|---------------------------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------| +| 1900 - 1920 MHz,
2010 - 2025 MHz | -40 dBm | -103 dBm | 10 MHz | WCDMA signal with one code | +| 1880 - 1900 MHz,
1990 - 2010 MHz,
2025 - 2045 MHz | -40 dBm | -103 dBm | 10 MHz | WCDMA signal with one code | +| 1920 - 1980 MHz | -40 dBm | -103 dBm | 10 MHz | WCDMA signal with one code | +| 1 - 1880 MHz,
1980 - 1990 MHz,
2045 - 12750 MHz | -15 dBm | -103 dBm | — | CW carrier | + +**Table 7.7-1: Blocking requirements for Wide Area BS in operating bands defined in subclause 4.2 b)** + +| Center frequency of interfering signal | Interfering signal mean power | Wanted signal mean power | Minimum offset of interfering signal | Type of interfering signal | +|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------| +| 1850 - 1990 MHz | -40 dBm | -103 dBm | 10 MHz | WCDMA signal with one code | +| 1830 - 1850 MHz,
1990 - 2010 MHz | -40 dBm | -103 dBm | 10 MHz | WCDMA signal with one code | +| 1 - 1830 MHz,
2010 - 12750 MHz | -15 dBm | -103 dBm | – | CW carrier | + +**Table 7.8-1: Blocking requirements for Wide Area BS in operating bands defined in subclause 4.2 c)** + +| Center frequency of interfering signal | Interfering signal mean power | Wanted signal mean power | Minimum offset of interfering signal | Type of interfering signal | +|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------| +| 1910 - 1930 MHz | -40 dBm | -103 dBm | 10 MHz | WCDMA signal with one code | +| 1890 - 1910 MHz,
1930 - 1950 MHz | -40 dBm | -103 dBm | 10 MHz | WCDMA signal with one code | +| 1 - 1890 MHz,
1950 - 12750 MHz | -15 dBm | -103 dBm | – | CW carrier | + +**Table 7.9-1: Blocking requirements for Wide Area BS in operating bands defined in subclause 4.2 d)** + +| Center frequency of interfering signal | Interfering signal mean power | Wanted signal mean power | Minimum offset of interfering signal | Type of interfering signal | +|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------| +| 2570 - 2620 MHz | -40 dBm | -103 dBm | 10 MHz | WCDMA signal with one code | +| 2550 - 2570 MHz,
2620 - 2640 MHz | -40 dBm | -103 dBm | 10 MHz | WCDMA signal with one code | +| 2500 - 2570 MHz,
2620 - 2690 MHz | -40 dBm | -103 dBm | 10 MHz | WCDMA signal with one code | +| 1 - 2550 MHz,
2690 - 12750 MHz | -15 dBm | -103 dBm | – | CW carrier | + +**Table 7.6-2: Blocking requirements for Local Area BS in operating bands defined in subclause 4.2 a)** + +| Center frequency of interfering signal | Interfering signal level | Wanted signal level | Minimum offset of interfering signal | Type of interfering signal | +|---------------------------------------------------------|--------------------------|---------------------|--------------------------------------|----------------------------| +| 1900 - 1920 MHz,
2010 - 2025 MHz | -30 dBm | + 6 dB | 10 MHz | WCDMA signal with one code | +| 1880 - 1900 MHz,
1990 - 2010 MHz,
2025 - 2045 MHz | -30 dBm | + 6 dB | 10 MHz | WCDMA signal with one code | +| 1920 - 1980 MHz | -30 dBm | + 6 dB | 10 MHz | WCDMA signal with one code | +| 1 - 1880 MHz,
1980 - 1990 MHz,
2045 - 12750 MHz | -15 dBm | + 6 dB | – | CW carrier | + +**Table 7.7-2: Blocking requirements for Local Area BS in operating bands defined in subclause 4.2 b)** + +| Center frequency of interfering signal | Interfering signal level | Wanted signal level | Minimum offset of interfering signal | Type of interfering signal | +|----------------------------------------|--------------------------|---------------------|--------------------------------------|----------------------------| +| 1850 - 1990 MHz | -30 dBm | + 6 dB | 10 MHz | WCDMA signal with one code | +| 1830 - 1850 MHz,
1990 - 2010 MHz | -30 dBm | + 6 dB | 10 MHz | WCDMA signal with one code | +| 1 - 1830 MHz,
2010 - 12750 MHz | -15 dBm | + 6 dB | – | CW carrier | + +**Table 7.8-2: Blocking requirements for Local Area BS in operating bands defined in subclause 4.2 c)** + +| Center frequency of interfering signal | Interfering signal level | Wanted signal level | Minimum offset of interfering signal | Type of interfering signal | +|----------------------------------------|--------------------------|---------------------|--------------------------------------|----------------------------| +| 1910 - 1930 MHz | -30 dBm | + 6 dB | 10 MHz | WCDMA signal with one code | +| 1890 - 1910 MHz,
1930 - 1950 MHz | -30 dBm | + 6 dB | 10 MHz | WCDMA signal with one code | +| 1 - 1890 MHz,
1950 - 12750 MHz | -15 dBm | + 6 dB | – | CW carrier | + +**Table 7.9-2: Blocking requirements for Local Area BS in operating bands defined in subclause 4.2 d)** + +| Center frequency of interfering signal | Interfering signal level | Wanted signal level | Minimum offset of interfering signal | Type of interfering signal | +|----------------------------------------|--------------------------|---------------------|--------------------------------------|----------------------------| +| 2570 - 2620 MHz | -30 dBm | + 6 dB | 10 MHz | WCDMA signal with one code | +| 2550 - 2570 MHz
2620 - 2640 MHz | -30 dBm | + 6 dB | 10 MHz | WCDMA signal with one code | +| 2500 - 2570 MHz
2620 - 2690 MHz | -30 dBm | + 6 dB | 10 MHz | WCDMA signal with one code | +| 1 - 2550 MHz,
2690 - 12750 MHz | -15 dBm | + 6 dB | – | CW carrier | + +The normative reference for this requirement is TS 25.105 [1] subclause 7.5.0.1. + +#### 7.5.2.1.2 Co-location with GSM, DCS, UTRA-FDD and/or E-UTRA FDD + +This additional blocking requirement may be applied for the protection of TDD BS receivers when GSM, DCS, UTRA-FDD and/or E-UTRA-FDD BTS are co-located with UTRA TDD Wide Area BS. + +The blocking performance requirement applies to interfering signals with center frequency within the ranges specified in the tables below, using a 1MHz step size. + +In case this additional blocking requirement is applied, the static reference performance as specified in clause 7.2.1 shall be met with a wanted and an interfering signal coupled to BS antenna input using the following parameters. + +**Table 7.9: Additional blocking requirements for Wide Area BS in operating bands defined in subclause 4.2 a) and 4.2 d)** + +| System type operating in the same geographic area | Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | Note | +|---------------------------------------------------|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------|-------------------------------------------------------------------------| +| GSM900 | 921 - 960 MHz | +16 dBm | -103 dBm | – | CW carrier | | +| DCS1800 | 1805 - 1880 | +16 dBm | -103 dBm | – | CW carrier | | +| WA BS UTRA FDD Band VII or E-UTRA Band 7 | 2620 - 2690 MHz | +13 dBm | -103 dBm | – | CW carrier | This requirement does not apply to UTRA TDD BS operating in Band 5.2(a) | +| LA BS UTRA FDD Band VII or E-UTRA Band 7 | 2620 - 2690 MHz | -6 dBm | -103 dBm | – | CW carrier | This requirement does not apply to UTRA TDD BS operating in Band 5.2(a) | + +NOTE 1: These requirements do not apply when the interfering signal falls within the uplink operating band or in the 10 MHz immediately outside the uplink operating band. + +NOTE 2: Some combinations of bands may not be possible to co-site based on the requirements above. The current state-of-the-art technology does not allow a single generic solution for co-location of UTRA TDD with UTRA FDD or E-UTRA FDD on adjacent frequencies for 30dB BS-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [9]. + +**Table 7.10: Void** + +The normative reference for this requirement is TS 25.105 [1] subclause 7.5.1.1. + +### 7.5.2.1.3 Void + +**Table 7.10A: Void****Table 7.10B: Void** + +### 7.5.2.2 1,28 Mcps TDD option + +#### 7.5.2.2.1 General requirements + +The static reference performance as specified in clause 7.2 shall be met with a wanted and an interfering signal coupled to the BS antenna input using the parameters specified in tables 7.6A-1, 7.7A-1, 7.8A-1, 7.9A-1, 7.6A-2, 7.7A-2, 7.8A-2 or 7.9A-2, respectively. + +The blocking requirement is always applicable outside the Base Station RF bandwidth or maximum radio bandwidth edges. The interfering signal offset is defined relative to the lower (upper) or maximum radio bandwidth edges. + +For BS capable of multi-band operation, the requirement in the in-band blocking frequency range applies for each supported operating band. The requirements applies in addition inside any inter RF bandwidth gap as long as the inter RF bandwidth gap size is at least 4.8MHz. The interfering signal offset is defined relative to the lower/upper RF bandwidth edges inside the inter RF bandwidth gap and is equal to -2.4MHz/+2.4MHz, respectively. + +For BS capable of multi-band operation, the requirement in the out-of-band blocking frequency ranges apply for each supported operating band, with the exception that the in-band blocking frequency ranges of all supported operating bands shall be excluded from the out-of-band blocking requirement. + +**Table 7.6A-1: Blocking requirements for Wide Area BS in operating bands defined in subclause 4.2 a) for 1,28 Mcps TDD** + +| Center frequency of interfering signal | Interfering signal mean power | Wanted signal mean power | Minimum offset of interfering signal | Type of interfering signal | +|---------------------------------------------------------|-------------------------------|--------------------------|--------------------------------------|------------------------------------| +| 1900 - 1920 MHz,
2010 - 2025 MHz | -40 dBm | -104 dBm | ±3.2 MHz | 1,28 Mcps TDD signal with one code | +| 1880 - 1900 MHz,
1990 - 2010 MHz,
2025 - 2045 MHz | -40 dBm | -104 dBm | ±3.2 MHz | 1,28 Mcps TDD signal with one code | +| 1920 - 1980 MHz | -40 dBm | -104 dBm | ±3.2 MHz | 1,28 Mcps TDD signal with one code | +| 1 - 1880 MHz,
1980 - 1990 MHz,
2045 - 12750 MHz | -15 dBm | -104 dBm | — | CW carrier | + +NOTE\*: For BS capable of multi-band operation, in case the interfering signal for in-band blocking is not in the in-band blocking frequency range of the operating band where the wanted signal is present, the wanted signal mean power shall not exceed -108.6dBm. + +**Table 7.7A-1: Blocking requirements for Wide Area BS in operating bands defined in subclause 4.2 b) for 1,28 Mcps TDD** + +| Center frequency of interfering signal | Interfering signal mean power | Wanted signal mean power | Minimum offset of interfering signal | Type of interfering signal | +|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|------------------------------------| +| 1850 - 1990 MHz | -40 dBm | -104 dBm | ±3.2 MHz | 1,28 Mcps TDD signal with one code | +| 1830 - 1850 MHz,
1990 - 2010 MHz | -40 dBm | -104 dBm | ±3.2 MHz | 1,28 Mcps TDD signal with one code | +| 1 - 1830 MHz,
2010 - 12750 MHz | -15 dBm | -104 dBm | — | CW carrier | + +NOTE\*: For BS capable of multi-band operation, in case the interfering signal for in-band blocking is not in the in-band blocking frequency range of the operating band where the wanted signal is present, the wanted signal mean power shall not exceed -108.6dBm. + +**Table 7.8A-1: Blocking requirements for Wide Area BS in operating bands defined in subclause 4.2 c) for 1,28 Mcps TDD** + +| Center frequency of interfering signal | Interfering signal mean power | Wanted signal mean power | Minimum offset of interfering signal | Type of interfering signal | +|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|------------------------------------| +| 1910 - 1930 MHz | -40 dBm | -104 dBm | ±3.2 MHz | 1,28 Mcps TDD signal with one code | +| 1890 - 1910 MHz,
1930 - 1950 MHz | -40 dBm | -104 dBm | ±3.2 MHz | 1,28 Mcps TDD signal with one code | +| 1 - 1890 MHz,
1950 - 12750 MHz | -15 dBm | -104 dBm | — | CW carrier | + +NOTE\*: For BS capable of multi-band operation, in case the interfering signal for in-band blocking is not in the in-band blocking frequency range of the operating band where the wanted signal is present, the wanted signal mean power shall not exceed -108.6dBm. + +**Table 7.8B-1: Blocking requirements for Wide Area BS in operating bands defined in 4.2(d) for 1,28 Mcps TDD** + +| Center Frequency of Interfering Signal | Interfering Signal Mean Power | Wanted Signal Mean Power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|------------------------------------| +| 2570 - 2620 MHz | -40dBm | -104 dBm | ±3.2MHz | 1,28 Mcps TDD signal with one code | +| 2500 - 2570 MHz,
2620 - 2690 MHz | -40dBm | -104 dBm | ±3.2 MHz | 1,28 Mcps TDD signal with one code | +| 1 - 2500 MHz,
2690 - 12750 MHz | -15 dBm | -104 dBm | – | CW carrier | + +NOTE\*: For BS capable of multi-band operation, in case the interfering signal for in-band blocking is not in the in-band blocking frequency range of the operating band where the wanted signal is present, the wanted signal mean power shall not exceed -108.6dBm. + +**Table 7.8C-1: Blocking requirements for Wide Area BS in operating bands defined in 4.2(e) for 1,28 Mcps TDD** + +| Center Frequency of Interfering Signal | Interfering Signal Mean Power | Wanted Signal Mean Power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|------------------------------------| +| 2300 - 2400 MHz | -40dBm | -104 dBm | ±3.2MHz | 1,28 Mcps TDD signal with one code | +| 2280 - 2300 MHz,
2400 - 2420MHz | -40dBm | -104 dBm | ±3.2 MHz | 1,28 Mcps TDD signal with one code | +| 1 - 2280 MHz,
2420 - 12750 MHz | -15 dBm | -104 dBm | – | CW carrier | + +NOTE\*: For BS capable of multi-band operation, in case the interfering signal for in-band blocking is not in the in-band blocking frequency range of the operating band where the wanted signal is present, the wanted signal mean power shall not exceed -108.6dBm. + +**Table 7.8D-1: Blocking requirements for Wide Area BS in operating bands defined in 5.2(f) for 1.28Mcps TDD** + +| Center Frequency of Interfering Signal | Interfering Signal Mean Power | Wanted Signal Mean Power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|---------------------------------------| +| 1880 - 1920 MHz | -40dBm | -104 dBm | ±3.2 MHz | Narrow band CDMA signal with one code | +| 1860 - 1880 MHz,
1920 – 1940 MHz | -40dBm | -104 dBm | ±3.2 MHz | Narrow band CDMA signal with one code | +| 1 - 1860 MHz,
1940 – 12750 MHz | -15 dBm | -104 dBm | – | CW carrier | + +NOTE\*: For BS capable of multi-band operation, in case the interfering signal for in-band blocking is not in the in-band blocking frequency range of the operating band where the wanted signal is present, the wanted signal mean power shall not exceed -108.6dBm. + +**Table 7.6A-2: Blocking requirements for Local Area BS and Home BS in operating bands defined in subclause 4.2 a) for 1,28 Mcps TDD** + +| Center frequency of interfering signal | Interfering signal level | Wanted signal level | Minimum offset of interfering signal | Type of interfering signal | +|---------------------------------------------------------|--------------------------|---------------------|--------------------------------------|------------------------------------| +| 1900 - 1920 MHz,
2010 - 2025 MHz | -30 dBm | + 6 dB | ±3,2 MHz | 1,28 Mcps TDD signal with one code | +| 1880 - 1900 MHz,
1990 - 2010 MHz,
2025 - 2045 MHz | -30 dBm | + 6 dB | ±3,2 MHz | 1,28 Mcps TDD signal with one code | +| 1920 - 1980 MHz | -30 dBm | + 6 dB | ±3,2 MHz | 1,28 Mcps TDD signal with one code | +| 1 - 1880 MHz,
1980 - 1990 MHz,
2045 - 12750 MHz | -15 dBm | + 6 dB | – | CW carrier | + +NOTE\*: For BS capable of multi-band operation, in case the interfering signal for in-band blocking is not in the in-band blocking frequency range of the operating band where the wanted signal is present, the wanted signal mean power shall not exceed -94.6dBm for Local Area BS. + +**Table 7.7A-2: Blocking requirements for Local Area BS and Home BS in operating bands defined in subclause 4.2 b) for 1,28 Mcps TDD** + +| Center frequency of interfering signal | Interfering signal level | Wanted signal level | Minimum offset of interfering signal | Type of interfering signal | +|----------------------------------------|--------------------------|---------------------|--------------------------------------|------------------------------------| +| 1850 - 1990 MHz | -30 dBm | + 6 dB | ±3,2 MHz | 1,28 Mcps TDD signal with one code | +| 1830 - 1850 MHz,
1990 - 2010 MHz | -30 dBm | + 6 dB | ±3,2 MHz | 1,28 Mcps TDD signal with one code | +| 1 - 1830 MHz,
2010 - 12750 MHz | -15 dBm | + 6 dB | – | CW carrier | + +NOTE\*: For BS capable of multi-band operation, in case the interfering signal for in-band blocking is not in the in-band blocking frequency range of the operating band where the wanted signal is present, the wanted signal mean power shall not exceed -94.6dBm for Local Area BS. + +**Table 7.8A-2: Blocking requirements for Local Area BS and Home BS in operating bands defined in subclause 4.2 c) for 1,28 Mcps TDD** + +| Center frequency of interfering signal | Interfering signal level | Wanted signal level | Minimum offset of interfering signal | Type of interfering signal | +|----------------------------------------|--------------------------|---------------------|--------------------------------------|------------------------------------| +| 1910 - 1930 MHz | -30 dBm | + 6 dB | ±3,2 MHz | 1,28 Mcps TDD signal with one code | +| 1890 - 1910 MHz,
1930 - 1950 MHz | -30 dBm | + 6 dB | ±3,2 MHz | 1,28 Mcps TDD signal with one code | +| 1 - 1890 MHz,
1950 - 12750 MHz | -15 dBm | + 6 dB | – | CW carrier | + +NOTE\*: For BS capable of multi-band operation, in case the interfering signal for in-band blocking is not in the in-band blocking frequency range of the operating band where the wanted signal is present, the wanted signal mean power shall not exceed -94.6dBm for Local Area BS. + +**Table 7.8B-2: Blocking requirements for Local Area BS and Home BS in operating bands defined in 4.2(d) for 1,28 Mcps TDD** + +| Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|------------------------------------| +| 2570 - 2620 MHz | -30 dBm | + 6 dB | ±3.2MHz | 1,28 Mcps TDD signal with one code | +| 2500 - 2570 MHz, 2620 - 2690 MHz | -30 dBm | + 6 dB | ±3.2 MHz | 1,28 Mcps TDD signal with one code | +| 1 - 2500 MHz, 2690 - 12750 MHz | -15 dBm | + 6 dB | – | CW carrier | + +NOTE\*: For BS capable of multi-band operation, in case the interfering signal for in-band blocking is not in the in-band blocking frequency range of the operating band where the wanted signal is present, the wanted signal mean power shall not exceed -94.6dBm for Local Area BS. + +**Table 7.8C-2: Blocking requirements for Local Area BS and Home BS in operating bands defined in 4.2(e) for 1,28 Mcps TDD** + +| Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|------------------------------------| +| 2300 - 2400 MHz | -30 dBm | + 6 dB | ±3.2MHz | 1,28 Mcps TDD signal with one code | +| 2280 - 2300 MHz, 2400 - 2420MHz | -30 dBm | + 6 dB | ±3.2 MHz | 1,28 Mcps TDD signal with one code | +| 1 - 2280 MHz, 2420 - 12750 MHz | -15 dBm | + 6 dB | – | CW carrier | + +NOTE\*: For BS capable of multi-band operation, in case the interfering signal for in-band blocking is not in the in-band blocking frequency range of the operating band where the wanted signal is present, the wanted signal mean power shall not exceed -94.6dBm for Local Area BS. + +**Table 7.8D-2: Blocking requirements for Local Area BS and Home BS in operating bands defined in 5.2(f)** + +| Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|---------------------------------------| +| 1880-1920 MHz | -30 dBm | -90 dBm | ±3.2 MHz | Narrow band CDMA signal with one code | +| 1860 - 1880 MHz, 1920 - 1940MHz | -30 dBm | -90 dBm | ±3.2 MHz | Narrow band CDMA signal with one code | +| 1 - 1860 MHz, 1940 - 12750 MHz | -15 dBm | -90 dBm | – | CW carrier | + +NOTE\*: For BS capable of multi-band operation, in case the interfering signal for in-band blocking is not in the in-band blocking frequency range of the operating band where the wanted signal is present, the wanted signal mean power shall not exceed -94.6dBm for Local Area BS. + +The normative reference for this requirement is TS 25.105 [1] subclause 7.5.0.2. + +#### 7.5.2.2.2 Co-location with GSM, DCS, UTRA FDD and/or E-UTRA FDD, UTRA TDD and/or E-UTRA TDD + +This additional blocking requirement may be applied for the protection of TDD BS receivers when GSM, DCS, UTRA FDD, E-UTRA FDD, FDD unsynchronized UTRA TDD and/or unsynchronized E-UTRA TDD BTS operating in a different frequency band are co-located with UTRA TDD Wide Area BS. + +The blocking performance requirement applies to interfering signals with centre frequency within the ranges specified in the tables below, using a 1MHz step size. + +In case this additional blocking requirement is applied, the static reference performance as specified in clause 7.2.1 shall be met with a wanted and an interfering signal coupled to BS antenna input using the following parameters. + +**Table 7.9A: Additional blocking requirements for Wide Area BS** + +| System type operating in the same geographic area | Centre Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | Note | +|---------------------------------------------------|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------|--------------------------------------------------------------------------| +| Macro GSM900 | 921 – 960 MHz | +16 dBm | -104 dBm | – | CW carrier | | +| Macro DCS1800 | 1805 – 1880 MHz | +16 dBm | -104 dBm | – | CW carrier | For UTRA TDD BS operating in Band 5.2(f), it applies for 1805 - 1850 MHz | +| GSM850 or CDMA850 | 869 – 894 MHz | +16 dBm | -104 dBm | – | CW carrier | | +| WA BS UTRA FDD Band I or E-UTRA Band 1 | 2110 – 2170 MHz | +16 dBm | -104 dBm | – | CW carrier | | +| WA BS UTRA FDD Band iii or E-UTRA Band 3 | 1805 – 1880 MHz | +16 dBm | -104 dBm | – | CW carrier | For UTRA TDD BS operating in Band 5.2(f), the requirement is FFS | +| WA BS UTRA FDD Band V or E-UTRA Band 5 | 869 – 894 MHz | +16 dBm | -104 dBm | – | CW carrier | | +| WA BS UTRA FDD Band VII or E-UTRA Band 7 | 2620 – 2690 MHz | +16 dBm | -104 dBm | – | CW carrier | | +| WA UTRA TDD Band a) or E-UTRA Band 33 | 1900 – 1920 MHz | +16 dBm | -104 dBm | – | CW carrier | | +| WA UTRA TDD Band a) or E-UTRA Band 34 | 2010 – 2025 MHz | +16 dBm | -104 dBm | – | CW carrier | | +| WA UTRA TDD Band d) or E-UTRA Band 38 | 2570 – 2620 MHz | +16 dBm | -104 dBm | – | CW carrier | | +| WA UTRA TDD Band f) or E-UTRA Band 39 | 1880 – 1920 MHz | +16 dBm | -104 dBm | – | CW carrier | | +| WA UTRA TDD Band e) or E-UTRA Band 40 | 2300 – 2400 MHz | +16 dBm | -104 dBm | – | CW carrier | | +| WA E-UTRA Band 41 | 2496 – 2690 MHz | +16 dBm | -104 dBm | – | CW carrier | | +| WA E-UTRA Band 42 | 3400 – 3600 MHz | +16 dBm | -104 dBm | – | CW carrier | | +| WA E-UTRA Band 44 | 703 – 803 MHz | +16 dBm | -104 dBm | – | CW carrier | | + +| | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|--------|----------|---|------------|------------------------------------------------------------------| +| Pico GSM850 | 869 – 894 | -7 dBm | -104 dBm | – | CW carrier | | +| Pico GSM900 | 921 – 960 | -7 dBm | -104 dBm | – | CW carrier | | +| Pico DCS1800 | 1805 – 1880 | -7 dBm | -104 dBm | – | CW carrier | | +| LA BS UTRA FDD Band I or E-UTRA Band 1 | 2110 – 2170 | -6 dBm | -104 dBm | – | CW carrier | | +| LA BS UTRA FDD Band III or E-UTRA Band 3 | 1805 – 1880 MHz | -6 dBm | -104 dBm | – | CW carrier | For UTRA TDD BS operating in Band 5.2(f), the requirement is FFS | +| LA BS UTRA FDD Band V or E-UTRA Band 5 | 869 – 894 MHz | -6 dBm | -104 dBm | – | CW carrier | | +| LA BS UTRA FDD Band VII or E-UTRA Band 7 | 2620 – 2690 MHz | -6 dBm | -104 dBm | – | CW carrier | | +| LA UTRA TDD Band a) or E-UTRA Band 33 | 1900 – 1920 MHz | -6 dBm | -104 dBm | – | CW carrier | | +| LA UTRA TDD Band a) or E-UTRA Band 34 | 2010 – 2025 MHz | -6 dBm | -104 dBm | – | CW carrier | | +| LA UTRA TDD Band d) or E-UTRA Band 38 | 2570 – 2620 MHz | -6 dBm | -104 dBm | – | CW carrier | | +| LA UTRA TDD Band f) or E-UTRA Band 39 | 1880 – 1920 MHz | -6 dBm | -104 dBm | – | CW carrier | | +| LA UTRA TDD Band e) or E-UTRA Band 40 | 2300 – 2400 MHz | -6 dBm | -104 dBm | – | CW carrier | | +| LA E-UTRA Band 41 | 2496 – 2690 MHz | -6 dBm | -104 dBm | – | CW carrier | | +| LA E-UTRA Band 42 | 3400 – 3600 MHz | -6 dBm | -104 dBm | – | CW carrier | | +| LA E-UTRA Band 44 | 703 – 803 MHz | -6 dBm | -104 dBm | – | CW carrier | | +| LA E-UTRA Band 46 | 5150 – 5925 MHz | -6 dBm | -104 dBm | – | CW carrier | | +| NOTE 1: These requirements do not apply when the interfering signal falls within any of the supported uplink operating band or in the 10 MHz frequency range immediately outside the any of the supported uplink operating band. | | | | | | | +| NOTE 2: Some combinations of bands may not be possible to co-site based on the requirements above. The current state-of-the-art technology does not allow a single generic solution for co-location of UTRA TDD with UTRA FDD or E-UTRA FDD on adjacent frequencies for 30dB BS-BS minimum coupling loss. | | | | | | | + +However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [9]. + +**Table 7.10A: Void** + +**Table 7.10A-1: Void** + +The normative reference for this requirement is TS 25.105 [1] subclause 7.5.1.2. + +#### 7.5.2.2.3 Void + +**Table 7.10B: Void** + +**Table 7.10C: Void** + +#### 7.5.2.3 7,68 Mcps TDD option + +##### 7.5.2.3.1 General requirements + +The static reference performance as specified in clause 7.2 shall be met with a wanted and an interfering signal coupled to the BS antenna input using the parameters specified in tables 7.6-1B, 7.7-1B, 7.8-1B, 7.6-2B, 7.7-2B or 7.8-2B, respectively. + +**Table 7.6-1B: Blocking requirements for Wide Area BS in operating bands defined in subclause 4.2 a)** + +| Center frequency of interfering signal | Interfering signal mean power | Wanted signal mean power | Minimum offset of interfering signal | Type of interfering signal | +|---------------------------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------| +| 1900 - 1920 MHz,
2010 - 2025 MHz | -40 dBm | -103 dBm | 20 MHz | WCDMA signal with one code | +| 1880 - 1900 MHz,
1990 - 2010 MHz,
2025 - 2045 MHz | -40 dBm | -103 dBm | 20 MHz | WCDMA signal with one code | +| 1920 - 1980 MHz | -40 dBm | -103 dBm | 20 MHz | WCDMA signal with one code | +| 1 - 1880 MHz,
1980 - 1990 MHz,
2045 - 12750 MHz | -15 dBm | -103 dBm | – | CW carrier | + +**Table 7.7-1B: Blocking requirements for Wide Area BS in operating bands defined in subclause 4.2 b)** + +| Center frequency of interfering signal | Interfering signal mean power | Wanted signal mean power | Minimum offset of interfering signal | Type of interfering signal | +|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------| +| 1850 - 1990 MHz | -40 dBm | -103 dBm | 20 MHz | WCDMA signal with one code | +| 1830 - 1850 MHz,
1990 - 2010 MHz | -40 dBm | -103 dBm | 20 MHz | WCDMA signal with one code | +| 1 - 1830 MHz,
2010 - 12750 MHz | -15 dBm | -103 dBm | – | CW carrier | + +**Table 7.8-1B: Blocking requirements for Wide Area BS in operating bands defined in subclause 4.2 c)** + +| Center frequency of interfering signal | Interfering signal mean power | Wanted signal mean power | Minimum offset of interfering signal | Type of interfering signal | +|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------| +| 1910 - 1930 MHz | -40 dBm | -103 dBm | 20 MHz | WCDMA signal with one code | +| 1890 - 1910 MHz,
1930 - 1950 MHz | -40 dBm | -103 dBm | 20 MHz | WCDMA signal with one code | +| 1 - 1890 MHz,
1950 - 12750 MHz | -15 dBm | -103 dBm | – | CW carrier | + +**Table 7.9-1B: Blocking requirements for Wide Area BS in operating bands defined in subclause 4.2 d)** + +| Centre Frequency of Interfering Signal | Interfering Signal Mean Power | Wanted Signal Mean Power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------| +| 2570 - 2620 MHz | -40 dBm | -103 dBm | 20 MHz | WCDMA signal with one code | +| 2550 - 2570 MHz
2620 - 2640 MHz | -40 dBm | -103 dBm | 20 MHz | WCDMA signal with one code | +| 2500 - 2570 MHz
2620 - 2690 MHz | -40 dBm | -103 dBm | 20 MHz | WCDMA signal with one code | +| 1 - 2550 MHz,
2690 - 12750 MHz | -15 dBm | -103 dBm | – | CW carrier | + +**Table 7.6-2B: Blocking requirements for Local Area BS in operating bands defined in subclause 4.2 a)** + +| Center frequency of interfering signal | Interfering signal level | Wanted signal level | Minimum offset of interfering signal | Type of interfering signal | +|---------------------------------------------------------|--------------------------|---------------------|--------------------------------------|----------------------------| +| 1900 - 1920 MHz,
2010 - 2025 MHz | -30 dBm | -89 dBm | 20 MHz | WCDMA signal with one code | +| 1880 - 1900 MHz,
1990 - 2010 MHz,
2025 - 2045 MHz | -30 dBm | -89 dBm | 20 MHz | WCDMA signal with one code | +| 1920 - 1980 MHz | -30 dBm | -89 dBm | 20 MHz | WCDMA signal with one code | +| 1 - 1880 MHz,
1980 - 1990 MHz,
2045 - 12750 MHz | -15 dBm | -89 dBm | – | CW carrier | + +**Table 7.7-2B: Blocking requirements for Local Area BS in operating bands defined in subclause 4.2 b)** + +| Center frequency of interfering signal | Interfering signal level | Wanted signal level | Minimum offset of interfering signal | Type of interfering signal | +|----------------------------------------|--------------------------|---------------------|--------------------------------------|----------------------------| +| 1850 - 1990 MHz | -30 dBm | -89 dBm | 20 MHz | WCDMA signal with one code | +| 1830 - 1850 MHz,
1990 - 2010 MHz | -30 dBm | -89 dBm | 20 MHz | WCDMA signal with one code | +| 1 - 1830 MHz,
2010 - 12750 MHz | -15 dBm | -89 dBm | – | CW carrier | + +**Table 7.8-2B: Blocking requirements for Local Area BS in operating bands defined in subclause 4.2 c)** + +| Center frequency of interfering signal | Interfering signal level | Wanted signal level | Minimum offset of interfering signal | Type of interfering signal | +|----------------------------------------|--------------------------|---------------------|--------------------------------------|----------------------------| +| 1910 - 1930 MHz | -30 dBm | -89 dBm | 20 MHz | WCDMA signal with one code | +| 1890 - 1910 MHz,
1930 - 1950 MHz | -30 dBm | -89 dBm | 20 MHz | WCDMA signal with one code | +| 1 - 1890 MHz,
1950 - 12750 MHz | -15 dBm | -89 dBm | – | CW carrier | + +**Table 7.9-2B: Blocking requirements for Local Area BS in operating bands defined in subclause 4.2 d)** + +| Centre Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------| +| 2570 - 2620 MHz | -30 dBm | -89 dBm | 20 MHz | WCDMA signal with one code | +| 2550 - 2570 MHz
2620 - 2640 MHz | -30 dBm | -89 dBm | 20 MHz | WCDMA signal with one code | +| 2500 - 2570 MHz
2620 - 2690 MHz | -30 dBm | -89 dBm | 20 MHz | WCDMA signal with one code | +| 1 - 2550 MHz,
2690 - 12750 MHz | -15 dBm | -89 dBm | – | CW carrier | + +The normative reference for this requirement is TS 25.105 [1] subclause 7.5.0.3. + +#### 7.5.2.3.2 Void + +**Table 7.9B: Void** + +**Table 7.10F: Void** + +#### 7.5.2.3.3 Void + +**Table 7.10G: Void** + +**Table 7.10H: Void** + +#### 7.5.2.3.4 Co-location with GSM, DCS, UTRA-FDD and/or E-UTRA FDD + +This additional blocking requirement may be applied for the protection of TDD BS receivers when GSM, DCS, UTRA-FDD and/or E-UTRA-FDD BTS are co-located with UTRA TDD Wide Area BS. + +The blocking performance requirement applies to interfering signals with center frequency within the ranges specified in the tables below, using a 1MHz step size. + +In case this additional blocking requirement is applied, the static reference performance as specified in clause 7.2.1 shall be met with a wanted and an interfering signal coupled to BS antenna input using the following parameters. + +**Table 7.9C: Additional blocking requirements for Wide Area BS in operating bands defined in subclause 4.2 a) and 4.2 d)** + +| System type operating in the same geographic area | Center Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | Note | +|---------------------------------------------------|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------|-------------------------------------------------------------------------| +| GSM900 | 921 - 960 MHz | +16 dBm | -103 dBm | – | CW carrier | | +| DCS1800 | 1805 - 1880 MHz | +16 dBm | -103 dBm | – | CW carrier | | +| WA BS UTRA FDD Band VII or E-UTRA Band 7 | 2620 - 2690 MHz | +13 dBm | -103 dBm | – | CW carrier | This requirement does not apply to UTRA TDD BS operating in Band 5.2(a) | +| LA BS UTRA FDD Band VII or E-UTRA Band 7 | 2620 - 2690 MHz | -6 dBm | -103 dBm | – | CW carrier | This requirement does not apply to UTRA TDD BS operating in Band 5.2(a) | + +NOTE 1: These requirements do not apply when the interfering signal falls within the uplink operating band or in the 10 MHz immediately outside the uplink operating band. + +NOTE 2: Some combinations of bands may not be possible to co-site based on the requirements above. The current state-of-the-art technology does not allow a single generic solution for co-location of UTRA TDD with UTRA FDD or E-UTRA FDD on adjacent frequencies for 30dB BS-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [9]. + +## 7.5.3 Test purpose + +### 7.5.3.1 3,84 Mcps TDD option + +The test stresses the ability of the BS receiver to withstand high-level interference from unwanted signals at frequency offsets of 10 MHz or more, without undue degradation of its sensitivity. + +### 7.5.3.2 1,28 Mcps TDD option + +The test stresses the ability of the BS receiver to withstand high-level interference from unwanted signals at frequency offsets of 3,2 MHz or more, without undue degradation of its sensitivity. + +### 7.5.3.3 7,68 Mcps TDD option + +The test stresses the ability of the BS receiver to withstand high-level interference from unwanted signals at frequency offsets of 20 MHz or more, without undue degradation of its sensitivity. + +## 7.5.4 Method of test + +### 7.5.4.1 Initial conditions + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested for single carrier: $M$ ; see subclause 5.3. The BS shall be configured to operate as close to the centre of the operating band as possible. + +RF bandwidth positions to be tested for multi-carrier: $M_{\text{RFBW}}$ in single band operation, see subclause 5.3; $B_{\text{RFBW\_T}}^{\text{RFBW}}$ and $B_{\text{RFBW\_T}}^{\text{RFBW}}$ in multi-band operation, see subclause 5.3; + +In addition, in multi-band operation: + +- For $B_{\text{RFBW\_T}}^{\text{RFBW}}$ , out-of-band blocking testing above the highest operating band may be omitted. + - For $B_{\text{RFBW\_T}}^{\text{RFBW}}$ , out-of-band blocking testing below the lowest operating band may be omitted. +- (1) Connect an UE simulator operating at the assigned channel frequency of the wanted signal and a signal generator to the antenna connector of one Rx port. + - (2) Terminate or disable any other Rx port not under test. + - (3) Start transmission from the BS tester to the BS using the UL reference measurement channel (12,2 kbps) defined in Annex A.2.1. For a BS supporting multi-carrier operation, generate the wanted signal according to the applicable test configuration (see subclause 5.20 and 5.21) using the UL reference measurement channel in Annex A.2.1 on all carriers for the BS under test. The level of the UE simulator signal measured at the BS antenna connector shall be set according to subclause 7.5.2.2. + +### 7.5.4.2 Procedure + +#### 7.5.4.2.1 3,84 Mcps TDD option + +- (1) Set the signal generator to produce an interfering signal at a frequency offset $F_{\text{uw}}$ from the assigned channel frequency of the wanted signal which is given by + +$$F_{\text{uw}} = \pm (n \times 1 \text{ MHz}),$$ + +where $n$ shall be increased in integer steps from $n = 10$ up to such a value that the center frequency of the interfering signal covers the range from 1 MHz to 12,75 GHz. The interfering signal level measured at the antenna connector shall be set in dependency of its center frequency, as specified in tables 7.6 to 7.10. The type of the interfering signal is either equivalent to a continuous wideband CDMA signal with one code of chip frequency 3,84 Mcchip/s, filtered by an RRC transmit pulse-shaping filter with roll-off $\alpha = 0,22$ , or a CW signal; see tables 7.6 to 7.10. + +- (2) Measure the BER of the wanted signal at the BS receiver. + +- (3) Interchange the connections of the BS Rx ports and repeat the measurements according to steps (1) and (2). + +#### 7.5.4.2.2 1,28 Mcps TDD option + +- (1) Set the signal generator to produce an interfering signal at a frequency offset Fuw from the assigned channel frequency of the wanted signal which is given by + +$$Fuw = \pm 3,2 \pm n \times 1 \text{ MHz}$$ + +where n shall be increased in integer steps from n = 0 up to such a value that the center frequency of the interfering signal covers the range from 1 MHz to 12,75 GHz. The interfering signal level measured at the antenna connector shall be set in dependency of its center frequency, as specified in tables 7.6A to 7.10A. The type of the interfering signal is either equivalent to a continuous wideband CDMA signal with one code of chip frequency 1,28 Mchip/s, filtered by an RRC transmit pulse-shaping filter with roll-off $\alpha = 0,22$ , or a CW signal; see tables 7.6A to 7.10A. + +- (2) Measure the BER of the wanted signal at the BS receiver. +- (3) Interchange the connections of the BS Rx ports and repeat the measurements according to steps (1) and (2). + +In addition, for a multi-band capable BS with separate antenna connectors, the following steps shall apply: + +- (4) For single band tests, repeat the steps above per involved band with no carrier activated in the other band. +- (5) The interfering signal shall first be applied on the same port as the wanted signal. The test shall be repeated with the interfering signal applied on the other port (if any) mapped to the same receiver as the wanted signal. Any antenna connector with no signal applied in case of single-band or multi-band test shall be terminated. +- (6) Repeat step (5) with the wanted signal for the other band(s) applied on the respective port(s). + +#### 7.5.4.2.3 7,68 Mcps TDD option + +- (1) Set the signal generator to produce an interfering signal at a frequency offset Fuw from the assigned channel frequency of the wanted signal which is given by + +$$Fuw = \pm (n \times 1 \text{ MHz}),$$ + +where n shall be increased in integer steps from n = 20 up to such a value that the center frequency of the interfering signal covers the range from 1 MHz to 12,75 GHz. The interfering signal level measured at the antenna connector shall be set in dependency of its center frequency, as specified in tables 7.6B to 7.10F. The type of the interfering signal is either equivalent to a continuous wideband CDMA signal with one code of chip frequency 7,68 Mchip/s, filtered by an RRC transmit pulse-shaping filter with roll-off $\alpha = 0,22$ , or a CW signal; see subclause tables 7.6B to 7.10F. + +- (2) Measure the BER of the wanted signal at the BS receiver. +- (3) Interchange the connections of the BS Rx ports and repeat the measurements according to steps (1) and (2). + +### 7.5.5 Test Requirements + +NOTE 1: If the Test Requirement below differs from the Minimum Requirement, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +In all measurements made according to subclause 7.5.4.2, the BER shall not exceed 0,001. + +NOTE 2: Annex F describes the procedure for BER tests taking into account the statistical consequence of frequent repetition of BER measurements within the blocking test. The consequence is: a DUT exactly on the limit may fail due to the statistical nature 2.55 times(mean value) in 12750 BER measurements using the predefined wrong decision probability of 0.02%. If the fail cases are $\leq 12$ , it is allowed to repeat the fail cases 1 time before the final verdict. + +## 7.6 Intermodulation characteristics + +### 7.6.1 Definition and applicability + +Third and higher order mixing of two interfering RF signals can produce an interfering signal in the band of the desired channel. Intermodulation response rejection is a measure of the capability of the receiver to receive a wanted signal on its assigned channel frequency in the presence of two or more interfering signals which have a specific frequency relationship to the wanted signal. + +### 7.6.2 Minimum Requirements + +#### 7.6.2.1 3,84 Mcps TDD option + +The static reference performance as specified in clause 7.2 should be met when the following signals are coupled to the BS antenna input. + +- A wanted signal at the assigned channel frequency, with mean power 6 dB above the static reference level. +- Two interfering signals with the parameters specified in table 7.11. + +**Table 7.11: Parameters of the interfering signals for intermodulation characteristics testing** + +| Interfering Signal mean power | | Offset | Type of Interfering Signal | +|-------------------------------|---------------|--------|----------------------------| +| Wide Area BS | Local Area BS | | | +| - 48 dBm | - 38 dBm | 10 MHz | CW signal | +| - 48 dBm | - 38 dBm | 20 MHz | WCDMA signal with one code | + +The normative reference for this requirement is TS 25.105 [1] subclause 7.6.1.1. + +#### 7.6.2.2 1,28 Mcps TDD option + +The static reference performance as specified in clause 7.2 should be met when the following signals are coupled to the BS antenna input. + +- A wanted signal at the assigned channel frequency, with mean power 6 dB above the static reference level. +- Two interfering signals with the parameters specified in table 7.11A. + +The blocking requirement is always applicable outside the Base Station RF bandwidth or maximum radio bandwidth edges. The interfering signal offset is defined relative to the lower (upper) or maximum radio bandwidth edges. + +For BS capable of multi-band operation, the requirement applies in addition inside any inter RF bandwidth gap, in case the gap size is at least 11.2MHz. The CW interfering signal offset is defined relative to lower/upper RF bandwidth edges inside the inter RF bandwidth gap and is equal to -2.4MHz/+2.4MHz, respectively. The modulated interfering signal offset is defined relative to lower/upper RF bandwidth edges inside the inter RF bandwidth gap and is equal to -5.6MHz/+5.6MHz, respectively. + +**Table 7.11A: Parameters of the interfering signals for intermodulation characteristics testing for 1,28 Mcps TDD** + +| Interfering Signal mean power | | Offset | Type of Interfering Signal | +|-------------------------------|-------------------------|----------|------------------------------------| +| Wide Area BS | Local Area BS / Home BS | | | +| - 48 dBm | - 38 dBm | ±3,2 MHz | CW signal | +| - 48 dBm | - 38 dBm | ±6,4 MHz | 1,28 Mcps TDD signal with one code | + +The normative reference for this requirement is TS 25.105 [1] subclause 7.6.1.2. + +#### 7.6.2.3 7,68 Mcps TDD option + +The static reference performance as specified in clause 7.2 should be met when the following signals are coupled to the BS antenna input. + +- A wanted signal at the assigned channel frequency, with mean power 6 dB above the static reference level. +- Two interfering signals with the parameters specified in table 7.11B. + +**Table 7.11B: Parameters of the interfering signals for intermodulation characteristics testing** + +| Interfering Signal mean power | | Offset | Type of Interfering Signal | +|-------------------------------|---------------|--------|----------------------------| +| Wide Area BS | Local Area BS | | | +| - 48 dBm | - 38 dBm | 20 MHz | CW signal | +| - 48 dBm | - 38 dBm | 40 MHz | WCDMA signal with one code | + +The normative reference for this requirement is subclause 7.6.1.3. + +## 7.6.3 Test purpose + +The test purpose is to verify the ability of the BS receiver to inhibit the generation of intermodulation products in its non-linear elements caused by the presence of two high-level interfering signals at frequencies with a specific relationship to the frequency of the wanted signal. + +## 7.6.4 Method of test + +### 7.6.4.1 Initial conditions + +#### 7.6.4.1.1 3,84 Mcps TDD option + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested: B, M and T; see subclause 5.3. + +- (1) Connect an UE simulator operating at the assigned channel frequency of the wanted signal and two signal generators to the antenna connector of one Rx port. +- (2) Terminate or disable any other Rx port not under test. +- (3) Start transmission from the BS tester to the BS using the UL reference measurement channel (12,2 kbps) defined in Annex A.2.1. The level of the UE simulator signal measured at the BS antenna connector shall be set to 6 dB above the reference sensitivity level specified in subclause 7.2.2. +- (4) Set the first signal generator to produce a CW signal with a level measured at the BS antenna connector as specified in table 7.11.. +- (5) Set the second signal generator to produce an interfering signal equivalent to a wideband CDMA signal with one code of chip frequency 3,84 MHz, filtered by an RRC transmit pulse-shaping filter with roll-off $\alpha = 0,22$ . The level of the signal measured at the BS antenna connector shall be set as specified in table 7.11. + +#### 7.6.4.1.2 1,28 Mcps TDD option + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested for single carrier: B, M and T; see subclause 5.3. + +RF bandwidth positions to be tested for multi-carrier: $B_{RFBW}$ , and $T_{RFBW}$ in single band operation, see subclause 5.3; $B_{RFBW\_T}{}_{RFBW}$ and $B'_{RFBW\_T}{}_{RFBW}$ in multi-band operation, see subclause 4.7.1; + +- (1) Connect an UE simulator operating at the assigned channel frequency of the wanted signal and two signal generators to the antenna connector of one Rx port. +- (2) Terminate or disable any other Rx port not under test. +- (3) Start transmission from the BS tester to the BS using the UL reference measurement channel (12,2 kbps) defined in Annex A.2.1. For a BS supporting multi-carrier operation, generate the wanted signal using the applicable test configuration specified in subclause 5.20 and 5.21, and the UL reference measurement channel in Annex A.2.1 shall be used on all carriers for the BS under test. The level of the UE simulator signal measured at the BS antenna connector shall be set to 6 dB above the reference sensitivity level specified in subclause 7.2.2. + +- (4) Set the first signal generator to produce a CW signal with a level measured at the BS antenna connector as specified in table 7.11A. +- (5) Set the second signal generator to produce an interfering signal equivalent to a wideband CDMA signal with one code of chip frequency 1,28 MHz, filtered by an RRC transmit pulse-shaping filter with roll-off $\alpha = 0,22$ . The level of the signal measured at the BS antenna connector shall be set as specified in table 7.11A. + +#### 7.6.4.1.3 7,68 Mcps TDD option + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested: B, M and T; see subclause 5.3. + +- (1) Connect an UE simulator operating at the assigned channel frequency of the wanted signal and two signal generators to the antenna connector of one Rx port. +- (2) Terminate or disable any other Rx port not under test. +- (3) Start transmission from the BS tester to the BS using the UL reference measurement channel (12,2 kbps) defined in Annex A.2.1. The level of the UE simulator signal measured at the BS antenna connector shall be set to 6 dB above the reference sensitivity level specified in subclause 7.2.2. +- (4) Set the first signal generator to produce a CW signal with a level measured at the BS antenna connector as specified in table 7.11B. +- (5) Set the second signal generator to produce an interfering signal equivalent to a wideband CDMA signal with one code of chip frequency 7,68 MHz, filtered by an RRC transmit pulse-shaping filter with roll-off $\alpha = 0,22$ . The level of the signal measured at the BS antenna connector shall be set as specified in table 7.11B. + +#### 7.6.4.2 Procedure + +##### 7.6.4.2.1 3,84 Mcps TDD option + +- (1) The frequency of the first and the second signal generator shall be set to 10 MHz and 20 MHz, respectively, above the assigned channel frequency of the wanted signal. +- (2) Measure the BER of the wanted signal at the BS receiver. +- (3) The frequency of the first and the second signal generator shall be set to 10 MHz and 20 MHz, respectively, below the assigned channel frequency of the wanted signal. +- (4) Measure the BER of the wanted signal at the BS receiver. +- (5) Interchange the connections of the BS Rx ports and repeat the measurements according to steps (1) to (4). + +##### 7.6.4.2.2 1,28 Mcps TDD option + +- (1) Measure the BER of the wanted signal at the BS receiver. +- (2) Interchange the connections of the BS Rx ports and repeat the measurements. + +In addition, for a multi-band capable BS with separate antenna connectors, the following steps shall apply: + +- (3) For single band tests, repeat the steps above per involved band with no carrier activated in the other band. +- (4) The interfering signal shall first be applied on the same port as the wanted signal. The test shall be repeated with the interfering signal applied on the other port (if any) mapped to the same receiver as the wanted signal. Any antenna connector with no signal applied in case of single-band or multi-band test shall be terminated. +- (5) Repeat step 4) with the wanted signal for the other band(s) applied on the respective port(s) + +##### 7.6.4.2.3 7,68 Mcps TDD option + +- (1) The frequency of the first and the second signal generator shall be set to 20 MHz and 40 MHz, respectively, above the assigned channel frequency of the wanted signal. +- (2) Measure the BER of the wanted signal at the BS receiver. + +- (3) The frequency of the first and the second signal generator shall be set to 20 MHz and 40 MHz, respectively, below the assigned channel frequency of the wanted signal. +- (4) Measure the BER of the wanted signal at the BS receiver. +- (5) Interchange the connections of the BS Rx ports and repeat the measurements according to steps (1) to (4). + +## 7.6.5 Test Requirements + +NOTE: If the Test Requirement below differs from the Minimum Requirement, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +The BER measured according subclause 7.6.4.2 to shall not exceed 0,001. + +## 7.7 Spurious emissions + +### 7.7.1 Definition and applicability + +The spurious emissions power is the power of emissions generated or amplified in a receiver that appear at the BS antenna connector. The requirements apply to all BS with separate Rx and Tx antenna connectors. For BS equipped with only a single antenna connector for both transmitter and receiver, the requirements of subclause 6.6.3 shall apply to this port, and this test need not be performed. + +### 7.7.2 Minimum Requirements + +#### 7.7.2.1 3,84 Mcps TDD option + +The power of any spurious emission shall not exceed the values given in table 7.12. + +**Table 7.12: Receiver spurious emission requirements** + +| Band | Maximum level | Measurement Bandwidth | Note | +|-----------------------|---------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| 30 MHz - 1 GHz | -57 dBm | 100 kHz | | +| 1 GHz - 1,9 GHz | -47 dBm | 1 MHz | With the exception of frequencies between 12,5 MHz below the first carrier frequency and 12,5 MHz above the last carrier frequency used by the BS | +| 1,900 - 1,980 GHz | -78 dBm | 3,84 MHz | With the exception of frequencies between 12,5 MHz below the first carrier frequency and 12,5 MHz above the last carrier frequency used by the BS | +| 1,980 - 2,010 GHz | -47 dBm | 1 MHz | With the exception of frequencies between 12,5 MHz below the first carrier frequency and 12,5 MHz above the last carrier frequency used by the BS | +| 2,010 - 2,025 GHz | -78 dBm | 3,84 MHz | With the exception of frequencies between 12,5 MHz below the first carrier frequency and 12,5 MHz above the last carrier frequency used by the BS | +| 2,025 - 2,500 GHz | -47 dBm | 1 MHz | With the exception of frequencies between 12,5 MHz below the first carrier frequency and 12,5 MHz above the last carrier frequency used by the BS | +| 2,500 - 2,620 | -78 dBm | 3,84 MHz | With the exception of frequencies between 12,5 MHz below the first carrier frequency and 12,5 MHz above the last carrier frequency used by the BS | +| 2,620 GHz - 12,75 GHz | -47 dBm | 1 MHz | With the exception of frequencies between 12,5 MHz below the first carrier frequency and 12,5 MHz above the last carrier frequency used by the BS | + +**Table 7.12AA: Additional receiver spurious emission requirements** + +| Band | Maximum level | Measurement Bandwidth | Note | +|----------------------------------------------|---------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 815 MHz - 850 MHz
1749.9 MHz - 1784.9 MHz | -78 dBm | 3,84 MHz | Applicable in Japan
With the exception of frequencies between 12,5 MHz below the first carrier frequency and 12,5 MHz above the last carrier frequency used by the BS | + +In addition to the requirements in table 7.12 and 7.12AA, the co-existence requirements for co-located base stations in subclauses 6.6.3.2.2.2, 6.6.3.2.3.2 and 6.6.3.2.4.2 may also be applied. + +The normative reference for this requirement is TS 25.105 [1] subclause 7.7.1.1. + +### 7.7.2.2 1,28 Mcps TDD option + +The power of any spurious emission shall not exceed the values given in table 7.12A. + +For BS capable of multi-band operation, the exclusion applies for all supported operating bands. + +For BS capable of multi-band operation where multiple bands are mapped on separate antenna connectors, the single-band requirements apply and the excluded frequency range is only applicable for the operating band supported on each antenna connector. + +**Table 7.12A: General receiver spurious emission minimum requirements** + +| Band | Maximum level | Measurement Bandwidth | Note | +|-------------------|---------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| 30MHz - 1 GHz | -57 dBm | 100 kHz | | +| 1 GHz - 12.75 GHz | -47 dBm | 1 MHz | With the exception of frequencies between 4 MHz below the first carrier frequency and 4 MHz above the last carrier frequency used by the BS. | + +**Table 7.12A-1: Void****Table 7.12A-2: Void** + +In addition to the requirements in table 7.12A, the power of any spurious emission shall not exceed the levels specified for Co-existence with other systems in the same geographical area in subclause 6.6.3.2.2.1 and 6.6.3.5.2.2.2. In addition, the co-existence requirements for co-located base stations specified in subclause 6.6.3.2.5.1.2 and 6.6.3.2.5.2.2 may also be applied. + +The normative reference for this requirement is TS 25.105 [1] subclause 7.7.1.2. + +### 7.7.2.3 7,68 Mcps TDD option + +The power of any spurious emission shall not exceed the values given in table 7.12B and table 7.12BB. + +**Table 7.12B: Receiver spurious emission requirements** + +| Band | Maximum level | Measurement Bandwidth | Note | +|----------------------------------------------------------------------|---------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| 30 MHz - 1 GHz | -57 dBm | 100 kHz | | +| 1 GHz - 1.9 GHz and
1.98 GHz - 2.01 GHz
2.025 GHz - 2.5 GHz | -47 dBm | 1 MHz | With the exception of frequencies between 25MHz below the first carrier frequency and 25MHz above the last carrier frequency used by the BS. | +| 1.9 GHz - 1.98 GHz and
2.01 GHz - 2.025 GHz
2.5 GHz - 2.62 GHz | -75 dBm | 7.68 MHz | With the exception of frequencies between 25MHz below the first carrier frequency and 25MHz above the last carrier frequency used by the BS. | +| 2.62 GHz - 12.75 GHz | -47 dBm | 1 MHz | With the exception of frequencies between 25MHz below the first carrier frequency and 25MHz above the last carrier frequency used by the BS. | + +**Table 7.12BB: Additional receiver spurious emission requirements** + +| Band | Maximum level | Measurement Bandwidth | Note | +|-----------------------------------------------------------------------|---------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 815 MHz - 850 MHz
1427.9MHz - 1452.9MHz
1749.9 MHz - 1784.9 MHz | -78 dBm | 3,84 MHz | Applicable in Japan
With the exception of frequencies between 25MHz below the first carrier frequency and 25MHz above the last carrier frequency used by the BS. | + +In addition to the requirements in table 7.12B and 7.12BB, the co-existence requirements for co-located base stations specified in subclause 6.6.3.2.2.2, 6.6.3.2.3.2 and 6.6.3.2.4.2 may also be applied. + +The normative reference for this requirement is subclause 6.3.7.1. + +## 7.7.3 Test purpose + +The test purpose is to verify the ability of the BS to limit the interference caused by receiver spurious emissions to other systems. + +## 7.7.4 Method of test + +### 7.7.4.1 Initial conditions + +#### 7.7.4.1.0 General test conditions + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested for single carrier: M; see subclause 5.3. + +RF bandwidth positions to be tested for multi-carrier: $M_{RFBW}$ in single band operation, see sub-clause 5.3; $B_{RFBW\_T}^{RFBW}$ and $B_{RFBW\_T}^{RFBW}$ in multi-band operation, see subclause 5.3; + +#### 7.7.4.1.1 3,84 Mcps TDD option + +- (1) Connect the measuring equipment to the antenna connector of one BS Rx port. +- (2) Terminate or disable any other BS Rx port not under test. +- (3) Set the BS receiver to operational mode. +- (4) Set the BS to transmit a signal with parameters according to table 7.13. +- (5) Terminate the Tx port(s). + +**Table 7.13: Parameters of the transmitted signal for Rx spurious emissions test** + +| Parameter | Value/description | +|---------------------------------------------|------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i
is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | PRAT | +| Number of DPCH in each time slot under test | 9 | +| Power of each DPCH | 1/9 of Base Station output power | +| Data content of DPCH | real life (sufficient irregular) | + +#### 7.7.4.1.2 1,28 Mcps TDD option + +- (1) Connect the measuring equipment to the antenna connector of one BS Rx port under test. +- (2) Terminate or disable any other BS Rx port not under test. +- (3) For a BS declared to be capable of single carrier operation only, set the BS to transmit a signal with parameters according to table 7.13A at manufacturer's declared output power, PRAT. + +For a BS declared to be capable of multi-carrier operation, set the BS to transmit according to Table 7.13A on all carriers using the applicable test configuration and corresponding power setting for receiver test, as specified in subclause 5.20 and 5.21 + +- (4) Terminate the Tx port(s). + +**Table 7.13A: Parameters of the transmitted signal for Rx spurious emissions test for 1,28 Mcps TDD** + +| Parameter | Value/description | +|---------------------------------------------|----------------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 6:
transmit, if i
is 0,4,5,6;
receive, if i is 1,2,3. | +| Time slots under test | TS1, TS2 and TS3 | +| Number of DPCH in each time slot under test | 8 | +| Power of each DPCH | 1/8 of Base Station output power | +| Data content of DPCH | real life (sufficient irregular) | + +#### 7.7.4.1.3 7,68 Mcps TDD option + +- (1) Connect the measuring equipment to the antenna connector of one BS Rx port. +- (2) Terminate or disable any other BS Rx port not under test. +- (3) Set the BS receiver to operational mode. +- (4) Set the BS to transmit a signal with parameters according to table 7.13B. +- (5) Terminate the Tx port(s). + +**Table 7.13B: Parameters of the transmitted signal for Rx spurious emissions test** + +| Parameter | Value/description | +|---------------------------------------------|---------------------------------------------------------------------------------| +| TDD Duty Cycle | TS i; i = 0, 1, 2, ..., 14:
transmit, if i is even;
receive, if i is odd. | +| Time slot carrying SCH | TS0 | +| Time slots under test | TS i, i even and non zero | +| BS output power setting | PRAT | +| Number of DPCH in each time slot under test | 9 | +| Power of each DPCH | 1/9 of Base Station output power | +| Data content of DPCH | real life (sufficient irregular) | + +## 7.7.4.2 Procedure + +### 7.7.4.2.1 3,84 Mcps TDD option + +- (1) Measure the power of the spurious emissions by applying the measuring equipment with the settings as specified in table 7.14. The characteristics of the measurement filter with the bandwidth 3,84 MHz shall be RRC with roll-off $\alpha = 0,22$ . The characteristics of the measurement filters with bandwidths 100 kHz and 1 MHz shall be approximately Gaussian (typical spectrum analyzer filter). The center frequency of the filters shall be stepped in contiguous steps over the frequency bands as specified in table 7.14 and table 7.14AA. The time duration of each step shall be sufficiently long to capture one even (transmit) time slot. +- (2) If the BS is equipped with more than one Rx port, interchange the connections of the BS Rx ports and repeat the measurement according to (1). + +**Table 7.14: Measurement equipment settings** + +| Stepped frequency range | Measurement bandwidth | Step width | Note | Detection mode | +|-------------------------|-----------------------|------------|---------------------------------------------------------------------------------------------------------------------------------------------------|----------------| +| 30 MHz - 1 GHz | 100 kHz | 100 kHz | With the exception of frequencies between 12,5 MHz below the first carrier frequency and 12,5 MHz above the last carrier frequency used by the BS | true RMS | +| 1 GHz - 1,900 GHz | 1 MHz | 1 MHz | | | +| 1,900 GHz - 1,980 GHz | 3,84 MHz | 200 kHz | | | +| 1,980 GHz - 2,010 GHz | 1 MHz | 1 MHz | | | +| 2,010 GHz - 2,025 GHz | 3,84 MHz | 200 kHz | | | +| 2,025 GHz - 2,500 GHz | 1 MHz | 1 MHz | | | +| 2,500 GHz - 2,620 GHz | 3,84 MHz | 200 kHz | | | +| 2,620 GHz - 12,75 GHz | 1 MHz | 1 MHz | | | + +**Table 7.14 AA: Additional measurement equipment settings** + +| Band | Measurement Bandwidth | Step Width | Note | Detection mode | +|----------------------------------------------|-----------------------|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------| +| 815 MHz - 850 MHz
1749,9 MHz - 1784,9 MHz | 3,84 MHz | 200 kHz | Applicable in Japan
With the exception of frequencies between 12,5 MHz below the first carrier frequency and 12,5 MHz above the last carrier frequency used by the BS | True RMS | + +### 7.7.4.2.2 1,28 Mcps TDD option + +- (1) Measure the power of the spurious emissions by applying the measuring equipment with the settings as specified in table 7.14A. The characteristics of the measurement filter with the bandwidth 1,28 MHz shall be RRC with roll-off $\alpha = 0,22$ . The characteristics of the measurement filters with bandwidths 100 kHz and 1 MHz shall be approximately Gaussian (typical spectrum analyzer filter). The center frequency of the filters shall be stepped in contiguous steps over the frequency bands as specified in table 7.14A. The time duration of each step shall be sufficiently long to capture one even (transmit) time slot. +- (2) Repeat the test for the other port(s), which was (were) terminated. + +In addition, for a multi-band capable BS, the following steps shall apply: + +- (3) For multi-band capable BS and single band tests, repeat the steps above per involved band with no carrier activated in the other band. +- (4) For multi-band capable BS with separate antenna connector, the antenna connector not being under test in case of single-band or multi-band test shall be terminated + +**Table 7.14A: Measurement equipment settings** + +| Stepped frequency range | Measurement bandwidth | Step width | Note | Detection mode | | +|-------------------------|-----------------------|------------|---------------------------------------------------------------------------------------------------------------------------------------------|----------------|--| +| 30 MHz - 1 GHz | 100 kHz | 100 kHz | | true RMS | | +| 1 GHz - 1,880 GHz | 1 MHz | 1 MHz | With the exception of frequencies between 4 MHz below the first carrier frequency and 4 MHz above the last carrier frequency used by the BS | | | +| 1,880 GHz - 1,980 GHz | 1,28 MHz | 200 kHz | | | | +| 1,980 GHz - 2,010 GHz | 1 MHz | 1 MHz | | | | +| 2,010 GHz - 2,025 GHz | 1,28 MHz | 200 kHz | | | | +| 2,025 – 2,300 GHz | 1 MHz | 1 MHz | | | | +| 2,300 GHz -2,400 GHz | 1,28 MHz | 200 kHz | | | | +| 2,400 GHz -2,500 GHz | 1 MHz | 1 MHz | | | | +| 2,500 GHz - 2,620GHz | 1,28 MHz | 200 kHz | | | | +| 2,620 GHz - 12,75 GHz | 1 MHz | 1 MHz | | | | + +### 7.7.4.2.3 7,68 Mcps TDD option + +- (1) Measure the power of the spurious emissions by applying the measuring equipment with the settings as specified in table 7.14B. The characteristics of the measurement filter with the bandwidth 7,68 MHz shall be RRC with roll-off $\alpha = 0,22$ . The characteristics of the measurement filters with bandwidths 100 kHz and 1 MHz shall be approximately Gaussian (typical spectrum analyzer filter). The center frequency of the filters shall be stepped in contiguous steps over the frequency bands as specified in table 7.14B and 7.14BB. The time duration of each step shall be sufficiently long to capture one even (transmit) time slot. +- (2) If the BS is equipped with more than one Rx port, interchange the connections of the BS Rx ports and repeat the measurement according to (1). + +**Table 7.14B: Measurement equipment settings** + +| Stepped frequency range | Measurement bandwidth | Step width | Note | Detection mode | | +|-------------------------|-----------------------|------------|-----------------------------------------------------------------------------------------------------------------------------------------------|----------------|--| +| 30 MHz - 1 GHz | 100 kHz | 100 kHz | | true RMS | | +| 1 GHz - 1,900 GHz | 1 MHz | 1 MHz | With the exception of frequencies between 25 MHz below the first carrier frequency and 25 MHz above the last carrier frequency used by the BS | | | +| 1,900 GHz - 1,980 GHz | 7,68 MHz | 200 kHz | | | | +| 1,980 GHz - 2,010 GHz | 1 MHz | 1 MHz | | | | +| 2,010 GHz - 2,025 GHz | 7,68 MHz | 200 kHz | | | | +| 2,025 GHz - 12,75 GHz | 1 MHz | 1 MHz | | | | + +**Table 7.14 BB: Additional measurement equipment settings** + +| Band | Measurement bandwidth | Step width | Note | Detection mode | +|-----------------------------------------------------------------------|-----------------------|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------| +| 815 MHz - 850 MHz
1427.9MHz - 1452.9MHz
1749.9 MHz - 1784.9 MHz | 3,84 MHz | 200 kHz | Applicable in Japan
With the exception of frequencies between 25MHz below the first carrier frequency and 25MHz above the last carrier frequency used by the BS. | true RMS | + +## 7.7.5 Test Requirements + +NOTE: If the Test Requirement below differs from the Minimum Requirement, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +The spurious emissions measured according to subclause 7.7.4.2 shall not exceed the limits specified in subclause 7.7.2. + +## 8 Performance requirements + +### 8.1 General + +Performance requirements for the BS are specified for the measurement channels defined in Annex A and the propagation conditions in Annex B. The requirements only apply to those measurement channels that are supported by the base station. The performance requirements for the high speed train conditions defined in Annex B.3 are optional. All Bit Error Ratio (BER) and Block Error ratio (BLER) measurements shall be carried out according to the general rules for statistical testing defined in ITU-T Recommendation O.153 [10] and Annex F. + +Unless stated otherwise, performance requirements apply for a single carrier only. Performance requirements for a BS supporting MC-HSUPA are defined in terms of single carrier requirements. + +The characteristics of the white noise source, simulating interference from other cells ( $I_{oc}$ ), shall comply with the AWGN interferer definition in subclause 5.18. + +The requirements only apply to a base station with dual receiver antenna diversity unless otherwise stated. The required $\hat{I}_{or}/I_{oc}$ shall be applied separately at each antenna port. + +**Table 8.1: Summary of Base Station performance targets** + +| Physical channel | Measurement channel | Static | Multi-path Case 1 | Multi-path Case 2** | Multi-path Case 3** | High speed train** | +|------------------|---------------------|------------------------------|------------------------------|------------------------------|------------------------------------------|------------------------------| +| | | Performance metric | | | | | +| DCH | 12,2 kbps | BLER < $10^{-2}$ | BLER < $10^{-2}$ | BLER < $10^{-2}$ | BLER < $10^{-2}$ | BLER < $10^{-2}$ | +| | 64 kbps | BLER < $10^{-1}$ , $10^{-2}$ | BLER < $10^{-1}$ , $10^{-2}$ | BLER < $10^{-1}$ , $10^{-2}$ | BLER < $10^{-1}$ , $10^{-2}$ , $10^{-3}$ | BLER < $10^{-1}$ , $10^{-2}$ | +| | 144 kbps | BLER < $10^{-1}$ , $10^{-2}$ | BLER < $10^{-1}$ , $10^{-2}$ | BLER < $10^{-1}$ , $10^{-2}$ | BLER < $10^{-1}$ , $10^{-2}$ , $10^{-3}$ | - | +| | 384 kbps | BLER < $10^{-1}$ , $10^{-2}$ | BLER < $10^{-1}$ , $10^{-2}$ | BLER < $10^{-1}$ , $10^{-2}$ | BLER < $10^{-1}$ , $10^{-2}$ , $10^{-3}$ | - | + +\*Note: Optional condition, not applicable for all BSs. +\*\*Note: Not applicable for Home BS + +## 8.2 Demodulation in static propagation conditions + +### 8.2.1 Demodulation of DCH + +#### 8.2.1.1 Definition and applicability + +The performance requirement of DCH in static propagation conditions is determined by the maximum Block Error Ratio (BLER) allowed when the receiver input signal is at a specified $\hat{I}_{or}/I_{oc}$ limit. The BLER is calculated for each of the measurement channels supported by the base station. + +In this subclause, different requirements shall apply to Wide Area BS, Local Area BS and Home BS. + +#### 8.2.1.2 Minimum Requirements + +##### 8.2.1.2.1 3,84 Mcps TDD option + +For the parameters specified in table 8.2, the BLER should not exceed the piece-wise linear BLER curve specified in table 8.3. These requirements are applicable for TFCS size 16. + +**Table 8.2: Parameters in static propagation conditions** + +| Parameters | | Unit | Test 1 | Test 2 | Test 3 | Test 4 | +|--------------------------------------------------------------------------------------|---------------|--------------|-------------------|-------------------|-------------------|--------| +| Number of DPCH o | | | 6 | 4 | 0 | 0 | +| $\frac{DPCH_o - E_c}{I_{or}}$ | | DB | -9 | -9,5 | - | - | +| I oc | Wide Area BS | dBm/3,84 MHz | -89 | | | | +| | Local Area BS | dBm/3,84 MHz | -74 | | | | +| Cell Parameter* | | | 0,1 | | | | +| DPCH Channelization Codes* | | C(k,Q) | C(1,8) | C(1,4)
C(5,16) | C(1,2)
C(9,16) | C(1,2) | +| DPCH o Channelization Codes* | | C(k,Q) | C(i,16) 3 ≤ i ≤ 8 | C(i,16) 6 ≤ i ≤ 9 | - | - | +| Information Data Rate | | Kbps | 12,2 | 64 | 144 | 384 | +| *Note: Refer to TS 25.223 for definition of channelization codes and cell parameter. | | | | | | | + +**Table 8.3: Performance requirements in AWGN channel.** + +| Test Number | $\frac{\hat{I}_{or}}{I_{oc}}$ [dB] | BLER | +|-------------|------------------------------------|------------------| +| 1 | -2,0 | 10 -2 | +| 2 | -0,4 | 10 -1 | +| | -0,1 | 10 -2 | +| 3 | -0,2 | 10 -1 | +| | 0,1 | 10 -2 | +| 4 | -0,8 | 10 -1 | +| | -0,6 | 10 -2 | + +The normative reference for this requirement is TS 25.105 [1] subclause 8.2.1.1.1. + +#### 8.2.1.2.2 1,28 Mcps TDD option + +For the parameters specified in table 8.2A, the BLER should not exceed the piece-wise linear BLER curve specified in table 8.3A. These requirements are applicable for TFCS size 16. + +**Table 8.2A: Parameters in static propagation conditions for 1,28 Mcps TDD** + +| Parameters | | Unit | Test 1 | Test 2 | Test 3 | Test 4 | +|------------------------------------|---------------|--------------|--------|--------|--------|--------| +| Number of DPCH o | | | 4 | 1 | 1 | 0 | +| Spread factor of DPCH o | | | 8 | 8 | 8 | | +| $\frac{DPCH_o - E_c}{I_{or}}$ | | dB | -7 | -7 | -7 | - | +| I oc | Wide Area BS | dBm/1,28 MHz | -91 | | | | +| | Local Area BS | dBm/1,28 MHz | -77 | | | | +| | Home BS | dBm/1,28 MHz | -82 | | | | +| Information Data Rate | | kbps | 12,2 | 64 | 144 | 384 | + +**Table 8.3A: Performance requirements in AWGN channel for 1,28 Mcps TDD** + +| Test Number | $\frac{\hat{I}_{or}}{I_{oc}}$ [dB] | BLER | +|-------------|------------------------------------|------------------| +| 1 | 0.6 | 10 -2 | +| 2 | -0.9 | 10 -1 | +| | -0.4 | 10 -2 | +| 3 | -0.3 | 10 -1 | +| | -0.1 | 10 -2 | +| 4 | 0.6 | 10 -1 | +| | 0.8 | 10 -2 | + +The normative reference for this requirement is TS 25.105 [1] subclause 8.2.1.1.2. + +### 8.2.1.2.3 7,68 Mcps TDD option + +For the parameters specified in table 8.2B, the BLER should not exceed the piece-wise linear BLER curve specified in table 8.3B. These requirements are applicable for TFCS size 16. + +**Table 8.2B: Parameters in static propagation conditions** + +| Parameters | | Unit | Test 1 | +|--------------------------------------------------------------------------------------|---------------|--------------|------------------------| +| Number of DPCH 0 | | | 14 | +| | | dB | -12 | +| I oc | Wide Area BS | dBm/7.68 MHz | -89 | +| | Local Area BS | dBm/7.68 MHz | -74 | +| Cell Parameter* | | | 0,1 | +| DPCH Channelization Codes* | | C(k,Q) | C(1, 16) | +| DPCH 0 Channelization Codes* | | C(k,Q) | C(i, 32)
3 ≤ i ≤ 16 | +| Information Data Rate | | kbps | 12.2 | +| *Note: Refer to TS 25.223 for definition of channelization codes and cell parameter. | | | | + +**Table 8.3B: Performance requirements in AWGN channel.** + +| Test Number | [dB] | BLER | +|-------------|------|------------------| +| 1 | -2.0 | 10 -2 | + +The normative reference for this requirement is TS 25.105 [1] subclause 8.2.1.1.3. + +### 8.2.1.3 Test purpose + +The test purpose is to verify the ability of the BS to receive a prescribed test signal under static propagation conditions with a BLER not exceeding a specified limit. Within the wanted channel, intracell interference sources as well as an additional intercell interference source are taken into account. Therefore, this test - as all other tests in clause 8 - mainly checks the ability of the signal processing part of the receiver to extract the wanted signal from the interfered-with input signal, whereas the tests in clause 7 concentrate on the receiver RF part. + +### 8.2.1.4 Method of test + +#### 8.2.1.4.1 Initial conditions + +##### 8.2.1.4.1.0 General test conditions + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested: B, M and T; see subclause 5.3. + +##### 8.2.1.4.1.1 3,84 Mcps TDD option + +Connect the BS tester (UE simulator) generating the wanted signal and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal with spreading factor 16, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.2. + +##### 8.2.1.4.1.2 1,28 Mcps TDD option + +Connect the BS tester (UE simulator) generating the wanted signal and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 + +generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal with spreading factor 8, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.2A. + +#### 8.2.1.4.1.3 7,68 Mcps TDD option + +Connect the BS tester (UE simulator) generating the wanted signal and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal with spreading factor 32, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.2B. + +#### 8.2.1.4.2 Procedure + +##### 8.2.1.4.2.1 3,84 Mcps TDD option + +- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value $I_{oc}$ as specified in table 8.2. +- (2) For a given test defined by the information data rate and the BLER objective, set the power of each DPCH0 measured at the BS antenna connector during the active time slots to the value specified in table 8.4. +- (3) Set up a call between the BS tester generating the wanted signal and the BS. The characteristics of the call shall be configured according to the information data rate to be provided and the corresponding UL reference measurement channel defined in Annex A. Depending on the information data rate, the UL reference measurement channel makes use of one or two Dedicated Physical Channels (DPCH1 and DPCH2) with different spreading factors SF. The power(s) of DPCH1 and DPCH2 (if applicable) measured at the BS antenna connector during the active time slots shall be set to the value(s) given in table 8.4. +- (4) Measure the BLER of the wanted signal at the BS receiver. + +**Table 8.4: Parameters of DPCH0 and the wanted signal** + +| Test Number | BLER objective | Number of DPCH 0 | Power of each DPCH 0 measured at the BS antenna connector [dBm] | | Parameters of the wanted signal | | | | +|-------------|----------------|-----------------------------|----------------------------------------------------------------------------|---------------|---------------------------------|----|--------------------------------------------------|---------------| +| | | | Wide Area BS | Local Area BS | DPCH | SF | Power measured at the BS antenna connector [dBm] | | +| | | | | | | | Wide Area BS | Local Area BS | +| 1 | $10^{-2}$ | 6 | -100,0 | -85 | DPCH 1 | 8 | -97,0 | -82,0 | +| 2 | $10^{-1}$ | 4 | -98,9 | -83,9 | DPCH 1 | 16 | -98,9 | -83,9 | +| | | | | | DPCH 2 | 4 | -92,9 | -77,9 | +| | $10^{-2}$ | 4 | -98,6 | -83,6 | DPCH 1 | 16 | -98,6 | -83,6 | +| | | | | | DPCH 2 | 4 | -92,6 | -77,6 | +| 3 | $10^{-1}$ | 0 | - | - | DPCH 1 | 16 | -98,7 | -83,7 | +| | | | | | DPCH 2 | 2 | -89,7 | -74,7 | +| | $10^{-2}$ | 0 | - | - | DPCH 1 | 16 | -98,4 | -83,4 | +| | | | | | DPCH 2 | 2 | -89,4 | -74,4 | +| 4 | $10^{-1}$ | 0 | - | - | DPCH 1 | 2 | -89,8 | -74,8 | +| | $10^{-2}$ | 0 | - | - | DPCH 1 | 2 | -89,6 | -74,6 | + +##### 8.2.1.4.2.2 1,28 Mcps TDD option + +- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value $I_{oc}$ as specified in table 8.2A. +- (2) For a given test defined by the information data rate and the BLER objective, set the power of each DPCH0 measured at the BS antenna connector during the active time slots to the value specified in table 8.4A. +- (3) Set up a call between the BS tester generating the wanted signal and the BS. The characteristics of the call shall be configured according to the information data rate to be provided and the corresponding UL reference measurement channel defined in Annex A. Depending on the information data rate, the UL reference + +measurement channel makes use of one or two Dedicated Physical Channels (DPCH1 and DPCH2) with different spreading factors SF. The power(s) of DPCH1 and DPCH2 (if applicable) measured at the BS antenna connector during the active time slots shall be set to the value(s) given in table 8.4A. + +- (4) Measure the BLER of the wanted signal at the BS receiver. + +**Table 8.4A: Parameters of DPCH0 and the wanted signal for 1,28 Mcps TDD** + +| Test Number | BLER objective | Number of DPCH 0 | Power of each DPCH 0 measured at the BS antenna connector [dBm] | | | Parameters of the wanted signal | | | | | +|-------------|------------------|-----------------------------|----------------------------------------------------------------------------|---------------|---------|---------------------------------|----|--------------------------------------------------|---------------|---------| +| | | | Wide Area BS | Local Area BS | Home BS | DPCH | SF | Power measured at the BS antenna connector [dBm] | | | +| | | | | | | | | Wide Area BS | Local Area BS | Home BS | +| 1 | 10 -2 | 4 | -97.4 | -83.4 | -88.4 | DPCH 1 | 8 | -97.4 | -83.4 | -88.4 | +| 2 | 10 -1 | 1 | -98.9 | -84.9 | -89.9 | DPCH 1 | 2 | -92.9 | -78.9 | -83.9 | +| | 10 -2 | 1 | -98.4 | -84.4 | -89.4 | DPCH 1 | 2 | -92.5 | -78.5 | -83.5 | +| 3 | 10 -1 | 1 | -98.3 | -84.3 | -89.3 | DPCH 1 | 2 | -92.3 | -78.3 | -83.3 | +| | 10 -2 | 1 | -98.1 | -84.1 | -89.1 | DPCH 1 | 2 | -92.1 | -78.1 | -83.1 | +| 4 | 10 -1 | 0 | - | - | | DPCH 1 | 16 | -99.9 | -85.9 | -90.9 | +| | | | | | | DPCH 2 | 2 | -90.9 | -76.9 | -81.9 | +| | 10 -2 | 0 | - | - | | DPCH 1 | 16 | -99.7 | -85.7 | -90.7 | +| | | | | | | DPCH 2 | 2 | -90.7 | -76.7 | -81.7 | + +#### 8.2.1.4.2.3 7,68 Mcps TDD option + +- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value Ioc as specified in table 8.2B. +- (2) For a given test defined by the information data rate and the BLER objective, set the power of each DPCH0 measured at the BS antenna connector during the active time slots to the value specified in table 8.4B. +- (3) Set up a call between the BS tester generating the wanted signal and the BS. The characteristics of the call shall be configured according to the information data rate to be provided and the corresponding UL reference measurement channel defined in Annex A. Depending on the information data rate, the UL reference measurement channel makes use of one or two Dedicated Physical Channels (DPCH1 and DPCH2) with different spreading factors SF. The power(s) of DPCH1 and DPCH2 (if applicable) measured at the BS antenna connector during the active time slots shall be set to the value(s) given in table 8.4B. +- (4) Measure the BLER of the wanted signal at the BS receiver. + +**Table 8.4B: Parameters of DPCH0 and the wanted signal** + +| Test Number | BLER objective | Number of DPCH 0 | Power of each DPCH 0 measured at the BS antenna connector [dBm] | | Parameters of the wanted signal | | | | +|-------------|------------------|-----------------------------|----------------------------------------------------------------------------|---------------|---------------------------------|----|--------------------------------------------------|---------------| +| | | | Wide Area BS | Local Area BS | DPCH | SF | Power measured at the BS antenna connector [dBm] | | +| | | | | | | | Wide Area BS | Local Area BS | +| 1 | 10 -2 | 14 | -103,0 | -88 | DPCH 1 | 16 | -100,0 | -85,0 | + +#### 8.2.1.5 Test Requirements + +NOTE: If the Test Requirement below differs from the Minimum Requirement, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +##### 8.2.1.5.1 3,84 Mcps TDD option + +The BLER measured according to subclause 8.2.1.4.2 shall not exceed the limits specified in table 8.3. + +#### 8.2.1.5.2 1,28 Mcps TDD option + +The BLER measured according to subclause 8.2.1.4.2. shall not exceed the limits specified in table 8.3A. + +#### 8.2.1.5.3 7,68 Mcps TDD option + +The BLER measured according to subclause 8.2.1.4.2 shall not exceed the limits specified in table 8.3B. + +### 8.3 Demodulation of DCH in multipath fading conditions + +#### 8.3.1 Multipath fading Case 1 + +##### 8.3.1.1 Definition and applicability + +The performance requirement of DCH in multipath fading Case 1 is determined by the maximum Block Error Ratio (BLER) allowed when the receiver input signal is at a specified $\hat{I}_{or}/I_{oc}$ limit. The BLER is calculated for each of the measurement channels supported by the base station. + +In this subclause, different requirements shall apply to Wide Area BS, Local Area BS and Home BS. + +##### 8.3.1.2 Minimum Requirements + +###### 8.3.1.2.1 3,84 Mcps TDD option + +For the parameters specified in table 8.5, the BLER should not exceed the piece-wise linear BLER curve specified in table 8.6. These requirements are applicable for TFCS size 16. + +**Table 8.5: Parameters in multipath Case 1 channel** + +| Parameters | | Unit | Test 1 | Test 2 | Test 3 | Test 4 | +|-----------------------------------------|---------------|--------------|---------------------------|---------------------------|-------------------|--------| +| Number of DPCH o | | | 6 | 4 | 0 | 0 | +| $\frac{DPCH_o - E_c}{I_{or}}$ | | dB | -9 | -9,5 | - | - | +| $I_{oc}$ | Wide Area BS | dBm/3,84 MHz | -89 | | | | +| | Local Area BS | dBm/3,84 MHz | -74 | | | | +| Cell Parameter* | | | 0,1 | | | | +| DPCH Channelization Codes* | | C(k,Q) | C(1,8) | C(1,4)
C(5,16) | C(1,2)
C(9,16) | C(1,2) | +| DPCH o Channelization Codes* | | C(k,Q) | C(i,16) $3 \leq i \leq 8$ | C(i,16) $6 \leq i \leq 9$ | - | - | +| Information Data Rate | | Kbps | 12,2 | 64 | 144 | 384 | + +\*Note: Refer to TS 25.223 for definition of channelization codes and cell parameter. + +**Table 8.6: Performance requirements in multipath Case 1 channel.** + +| Test Number | $\frac{\hat{I}_{or}}{I_{oc}}$ [dB] | BLER | +|-------------|------------------------------------|-----------| +| 1 | 6,5 | $10^{-2}$ | +| 2 | 5,5 | $10^{-1}$ | +| | 9,8 | $10^{-2}$ | +| 3 | 5,5 | $10^{-1}$ | +| | 9,8 | $10^{-2}$ | +| 4 | 5,1 | $10^{-1}$ | +| | 9,5 | $10^{-2}$ | + +The normative reference for this requirement is TS 25.105 [1] subclause 8.3.1.1.1. + +###### 8.3.1.2.2 1,28 Mcps TDD option + +For the parameters specified in table 8.5A, the BLER should not exceed the piece-wise linear BLER curve specified in table 8.6A. These requirements are applicable for TFCS size 16. + +**Table 8.5A: Parameters in multipath Case 1 channel for 1,28 Mcps TDD** + +| Parameters | | Unit | Test 1 | Test 2 | Test 3 | Test 4 | +|------------------------------------|---------------|--------------|--------|--------|--------|--------| +| Number of DPCH o | | | 4 | 1 | 1 | 0 | +| Spread factor of DPCH o | | | 8 | 8 | 8 | | +| $\frac{DPCH_{o\_}E_c}{I_{or}}$ | | dB | -7 | -7 | -7 | - | +| I oc | Wide Area BS | dBm/1,28 MHz | | | -91 | | +| | Local Area BS | dBm/1,28 MHz | | | -77 | | +| | Home BS | dBm/1,28 MHz | | | -82 | | +| Information Data Rate | | kbps | 12,2 | 64 | 144 | 384 | + +**Table 8.6A: Performance requirements multipath Case 1 channel for 1,28 Mcps TDD** + +| Test Number | $\frac{\hat{I}_{or}}{I_{oc}}$ [dB] | BLER | +|-------------|------------------------------------|-----------| +| 1 | 10.4 | $10^{-2}$ | +| 2 | 5.3 | $10^{-1}$ | +| | 9.4 | $10^{-2}$ | +| 3 | 5.7 | $10^{-1}$ | +| | 10.1 | $10^{-2}$ | +| 4 | 6.8 | $10^{-1}$ | +| | 10.9 | $10^{-2}$ | + +The normative reference for this requirement is TS 25.105 [1] subclause 8.3.1.1.2. + +### 8.3.1.2.3 7,68 Mcps TDD option + +For the parameters specified in table 8.5B, the BLER should not exceed the piece-wise linear BLER curve specified in table 8.6B. These requirements are applicable for TFCS size 16. + +**Table 8.5B: Parameters in multipath Case 1 channel** + +| Parameters | | Unit | Test 1 | +|--------------------------------------------------------------------------------------|---------------|--------------|--------------------------------| +| Number of DPCH o | | | 14 | +| | | dB | -12 | +| I oc | Wide Area BS | dBm/7.68 MHz | -89 | +| | Local Area BS | dBm/7.68 MHz | -74 | +| Cell Parameter* | | | 0,1 | +| DPCH Channelization Codes* | | C(k,Q) | C(1, 16) | +| DPCH o Channelization Codes* | | C(k,Q) | C(i, 32)
$3 \leq i \leq 16$ | +| Information Data Rate | | Kbps | 12.2 | +| *Note: Refer to TS 25.223 for definition of channelization codes and cell parameter. | | | | + +**Table 8.6B: Performance requirements in multipath Case 1 channel.** + +| Test Number | [dB] | BLER | +|-------------|------|-----------| +| 1 | 6.5 | $10^{-2}$ | + +The normative reference for this requirement is TS 25.105 [1] subclause 8.3.1.1.3. + +### 8.3.1.3 Test purpose + +The test purpose is to verify the ability of the BS to receive a prescribed test signal under defined propagation conditions (multipath fading Case 1) with a BLER not exceeding a specified limit. Within the wanted channel, independent intracell interference sources as well as an additional intercell interference source are taken into account. Therefore, this test - as all other tests in clause 8 - mainly checks the ability of the signal processing part of the receiver + +to extract the wanted signal from the distorted and interfered-with input signal, whereas the tests in clause 7 concentrate on the receiver RF part. + +#### 8.3.1.4 Method of test + +##### 8.3.1.4.1 Initial conditions + +###### 8.3.1.4.1.0 General test conditions + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested: B, M and T; see subclause 5.3. + +###### 8.3.1.4.1.1 3,84 Mcps TDD option + +- (1) Connect the BS tester (UE simulator) generating the wanted signal and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal with spreading factor 16, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.5. +- (2) The wanted signal produced by the BS tester and the interfering signals produced by the DPCH0 generators are individually passed through independent Multipath Fading Simulators (MFS) before entering the combining network. Each MFS shall be configured to simulate multipath fading Case 1. + +###### 8.3.1.4.1.2 1,28 Mcps TDD option + +- (1) Connect the BS tester (UE simulator) generating the wanted signal and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal with spreading factor 8, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.5A. +- (2) The wanted signal produced by the BS tester and the interfering signals produced by the DPCH0 generators are individually passed through independent Multipath Fading Simulators (MFS) before entering the combining network. Each MFS shall be configured to simulate multipath fading Case 1. + +###### 8.3.1.4.1.3 7,68 Mcps TDD option + +- (1) Connect the BS tester (UE simulator) generating the wanted signal and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal with spreading factor 32, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.5B. +- (2) The wanted signal produced by the BS tester and the interfering signals produced by the DPCH0 generators are individually passed through independent Multipath Fading Simulators (MFS) before entering the combining network. Each MFS shall be configured to simulate multipath fading Case 1. + +##### 8.3.1.4.2 Procedure + +###### 8.3.1.4.2.1 3,84 Mcps TDD option + +- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value $I_{oc}$ as specified in table 8.5. +- (2) For a given test defined by the information data rate and the BLER objective, set the power of each DPCH0 measured at the BS antenna connector during the active time slots to the value specified in table 8.7. + +- (3) Set up a call between the BS tester generating the wanted signal and the BS. The characteristics of the call shall be configured according to the information data rate to be provided and the corresponding UL reference measurement channel defined in Annex A. Depending on the information data rate, the UL reference measurement channel makes use of one or two Dedicated Physical Channels (DPCH1 and DPCH2) with different spreading factors SF. The power(s) of DPCH1 and DPCH2 (if applicable) measured at the BS antenna connector during the active time slots shall be set to the value(s) given in table 8.7. +- (4) Measure the BLER of the wanted signal at the BS receiver. + +**Table 8.7: Parameters of DPCH0 and the wanted signal** + +| Test Number | BLER objective | Number of DPCH 0 | Power of each DPCH 0 measured at the BS antenna connector [dBm] | | Parameters of the wanted signal | | | | +|-------------|------------------|-----------------------------|----------------------------------------------------------------------------|---------------|---------------------------------|----|--------------------------------------------------|---------------| +| | | | Wide Area BS | Local Area BS | DPCH | SF | Power measured at the BS antenna connector [dBm] | | +| | | | | | | | Wide Area BS | Local Area BS | +| 1 | 10 -2 | 6 | -91,5 | -76,5 | DPCH 1 | 8 | -88,5 | -73,5 | +| 2 | 10 -1 | 4 | -93,0 | -78,0 | DPCH 1 | 16 | -93,0 | -78,0 | +| | | | | | DPCH 2 | 4 | -87,0 | -72,0 | +| | 10 -2 | 4 | -88,7 | -73,7 | DPCH 1 | 16 | -88,7 | -73,7 | +| | | | | | DPCH 2 | 4 | -82,7 | -67,7 | +| 3 | 10 -1 | 0 | - | - | DPCH 1 | 16 | -93,0 | -78,0 | +| | | | | | DPCH 2 | 2 | -84,0 | -69,0 | +| | 10 -2 | 0 | - | - | DPCH 1 | 16 | -88,7 | -73,7 | +| | | | | | DPCH 2 | 2 | -79,7 | -64,7 | +| 4 | 10 -1 | 0 | - | - | DPCH 1 | 2 | -83,9 | -68,9 | +| | 10 -2 | 0 | - | - | DPCH 1 | 2 | -79,5 | -64,5 | + +#### 8.3.1.4.2.2 1,28 Mcps TDD option + +- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value Ioc as specified in table 8.5A. +- (2) For a given test defined by the information data rate and the BLER objective, set the power of each DPCH0 measured at the BS antenna connector during the active time slots to the value specified in table 8.7A. +- (3) Set up a call between the BS tester generating the wanted signal and the BS. The characteristics of the call shall be configured according to the information data rate to be provided and the corresponding UL reference measurement channel defined in Annex A. Depending on the information data rate, the UL reference measurement channel makes use of one or two Dedicated Physical Channels (DPCH1 and DPCH2) with different spreading factors SF. The power(s) of DPCH1 and DPCH2 (if applicable) measured at the BS antenna connector during the active time slots shall be set to the value(s) given in table 8.7A. +- (4) Measure the BLER of the wanted signal at the BS receiver. + +**Table 8.7A: Parameters of DPCH0 and the wanted signal for 1,28 Mcps TDD** + +| Test Number | BLER objective | Number of DPCH 0 | Power of each DPCH 0 measured at the BS antenna connector [dBm] | | | Parameters of the wanted signal | | | | | +|-------------|----------------|-----------------------------|----------------------------------------------------------------------------|---------------|---------|---------------------------------|----|--------------------------------------------------|---------------|---------| +| | | | Wide Area BS | Local Area BS | Home BS | DPCH | SF | Power measured at the BS antenna connector [dBm] | | | +| | | | | | | | | Wide Area BS | Local Area BS | Home BS | + +| | | | | | | | | | | | +|---|-----------|---|-------|-------|-------|-------------------|----|-------|-------|-------| +| 1 | $10^{-2}$ | 4 | -87.6 | -73,6 | -78.6 | DPCH 1 | 8 | -87.6 | -73,6 | -78.6 | +| 2 | $10^{-1}$ | 1 | -92.7 | -78,7 | -83.7 | DPCH 1 | 2 | -86.7 | -72,7 | -77.7 | +| | $10^{-2}$ | 1 | -88.6 | -74,6 | -79.6 | DPCH 1 | 2 | -82.6 | -68,6 | -73.6 | +| 3 | $10^{-1}$ | 1 | -92.3 | -78,3 | -83.3 | DPCH 1 | 2 | -86.3 | -72,3 | -77.3 | +| | $10^{-2}$ | 1 | -87.9 | -73,9 | -78.9 | DPCH 1 | 2 | -81.9 | -67,9 | -72.9 | +| 4 | $10^{-1}$ | 0 | - | | | DPCH 1 | 16 | -93.7 | -79.7 | -84.7 | +| | | | | | | DPCH 2 | 2 | -84.7 | -70.7 | -75.7 | +| | $10^{-2}$ | 0 | - | | | DPCH 1 | 16 | -89.6 | -75.6 | -80.6 | +| | | | | | | DPCH 2 | 2 | -80.6 | -66.6 | -71.6 | + +#### 8.3.1.4.2.3 7,68 Mcps TDD option + +- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value $I_{oc}$ as specified in table 8.5B. +- (2) For a given test defined by the information data rate and the BLER objective, set the power of each DPCH0 measured at the BS antenna connector during the active time slots to the value specified in table 8.7B. +- (3) Set up a call between the BS tester generating the wanted signal and the BS. The characteristics of the call shall be configured according to the information data rate to be provided and the corresponding UL reference measurement channel defined in Annex A. Depending on the information data rate, the UL reference measurement channel makes use of one or two Dedicated Physical Channels (DPCH1 and DPCH2) with different spreading factors SF. The power(s) of DPCH1 and DPCH2 (if applicable) measured at the BS antenna connector during the active time slots shall be set to the value(s) given in table 8.7B. +- (4) Measure the BLER of the wanted signal at the BS receiver. + +**Table 8.7B: Parameters of DPCH0 and the wanted signal** + +| Test Number | BLER objective | Number of DPCH 0 | Power of each DPCH 0 measured at the BS antenna connector [dBm] | | Parameters of the wanted signal | | | | +|-------------|----------------|-----------------------------|----------------------------------------------------------------------------|---------------|---------------------------------|----|--------------------------------------------------|---------------| +| | | | Wide Area BS | Local Area BS | DPCH | SF | Power measured at the BS antenna connector [dBm] | | +| | | | | | | | Wide Area BS | Local Area BS | +| 1 | $10^{-2}$ | 14 | -94,5 | -79,5 | DPCH 1 | 16 | -91,5 | -76,5 | + +#### 8.3.1.5 Test Requirements + +NOTE: If the Test Requirements below differ from the Minimum Requirements, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +##### 8.3.1.5.1 3,84 Mcps TDD option + +The BLER measured according to subclause 8.3.1.4.2 shall not exceed the limits specified in table 8.6. + +##### 8.3.1.5.2 1,28 Mcps TDD option + +The BLER measured according to subclause 8.3.1.4.2 shall not exceed the limits specified in table 8.6A. + +##### 8.3.1.5.3 7,68 Mcps TDD option + +The BLER measured according to subclause 8.3.1.4.2 shall not exceed the limits specified in table 8.6B. + +### 8.3.2 Multipath fading Case 2 + +#### 8.3.2.1 Definition and applicability + +The performance requirement of DCH in multipath fading Case 2 is determined by the maximum Block Error Ratio (BLER) allowed when the receiver input signal is at a specified $\hat{I}_{or}/I_{oc}$ limit. The BLER is calculated for each of the measurement channels supported by the base station. + +The requirements in this subclause shall apply to Wide Area BS only. There is no requirement to test Local Area BS and Home BS in multipath fading Case 2 conditions. + +### 8.3.2.2 Minimum Requirements + +#### 8.3.2.2.1 3,84 Mcps TDD option + +For the parameters specified in table 8.8, the BLER should not exceed the piece-wise linear BLER curve specified in table 8.8. These requirements are applicable for TFCS size 16. + +**Table 8.8: Parameters in multipath Case 2 channel** + +| Parameters | Unit | Test 1 | Test 2 | Test 3 | Test 4 | +|-----------------------------------------|--------------|-----------------|-------------------|-------------------|--------| +| Number of DPCH o | | 2 | 0 | 0 | 0 | +| $\frac{DPCH_o - E_c}{I_{or}}$ | DB | -6 | - | - | - | +| I oc | dBm/3,84 MHz | -89 | | | | +| Cell Parameter* | | 0,1 | | | | +| DPCH Channelization Codes* | C(k,Q) | C(1,8) | C(1,4)
C(5,16) | C(1,2)
C(9,16) | C(1,2) | +| DPCH o Channelization Codes* | C(k,Q) | C(i,16) 3≤ i ≤4 | - | - | - | +| Information Data Rate | Kbps | 12,2 | 64 | 144 | 384 | + +\*Note: Refer to TS 25.223 for definition of channelization codes and cell parameter. + +**Table 8.9: Performance requirements in multipath Case 2 channel.** + +| Test Number | $\frac{\hat{I}_{or}}{I_{oc}}$ [dB] | BLER | +|-------------|------------------------------------|------------------| +| 1 | -0,4 | 10 -2 | +| 2 | 0,2 | 10 -1 | +| | 2,5 | 10 -2 | +| 3 | 3,6 | 10 -1 | +| | 6,0 | 10 -2 | +| 4 | 2,8 | 10 -1 | +| | 5,2 | 10 -2 | + +The normative reference for this requirement is TS 25.105 [1] subclause 8.3.2.1.1. + +#### 8.3.2.2.2 1,28 Mcps option + +For the parameters specified in table 8.8A, the BLER should not exceed the piece-wise linear BLER curve specified in table 8.9A. These requirements are applicable for TFCS size 16. + +**Table 8.8A: Parameters in multipath Case 2 channel for 1,28 Mcps TDD** + +| Parameters | Unit | Test 1 | Test 2 | Test 3 | Test 4 | +|------------------------------------|--------------|--------|--------|--------|--------| +| Number of DPCH o | | 4 | 1 | 1 | 0 | +| Spread factor of DPCH o | | 8 | 8 | 8 | | +| $\frac{DPCH_o - E_c}{I_{or}}$ | dB | -7 | -7 | -7 | - | +| I oc | dBm/1,28 MHz | -91 | | | | +| Information Data Rate | kbps | 12,2 | 64 | 144 | 384 | + +**Table 8.9A: Performance requirements multipath Case 2 channel for 1,28 Mcps TDD.** + +| Test Number | $\frac{\hat{I}_{or}}{I_{oc}}$ [dB] | BLER | +|-------------|------------------------------------|-----------| +| 1 | 6.7 | $10^{-2}$ | +| 2 | 3.6 | $10^{-1}$ | +| | 5.9 | $10^{-2}$ | +| 3 | 4.2 | $10^{-1}$ | +| | 6.3 | $10^{-2}$ | +| 4 | 4.8 | $10^{-1}$ | +| | 7.1 | $10^{-2}$ | + +The normative reference for this requirement is TS 25.105 [1] subclause 8.3.2.1.2. + +### 8.3.2.2.3 7,68 Mcps TDD option + +For the parameters specified in table 8.8B, the BLER should not exceed the piece-wise linear BLER curve specified in table 8.9B. These requirements are applicable for TFCS size 16. + +**Table 8.8B: Parameters in multipath Case 2 channel** + +| Parameters | Unit | Test 1 | +|--------------------------------------------------------------------------------------|--------------|-------------------------------| +| Number of DPCH o | | 6 | +| | dB | -9 | +| $I_{oc}$ | dBm/7.68 MHz | -89 | +| Cell Parameter* | | 0,1 | +| DPCH Channelization Codes* | C(k,Q) | C(1, 16) | +| DPCH o Channelization Codes* | C(k,Q) | C(i, 32)
$3 \leq i \leq 8$ | +| Information Data Rate | kbps | 12.2 | +| *Note: Refer to TS 25.223 for definition of channelization codes and cell parameter. | | | + +**Table 8.9B: Performance requirements in multipath Case 2 channel.** + +| Test Number | [dB] | BLER | +|-------------|------|-----------| +| 1 | 1 | $10^{-2}$ | + +The normative reference for this requirement is TS 25.105 [1] subclause 8.3.2.1.3. + +### 8.3.2.3 Test purpose + +The test purpose is to verify the ability of the BS to receive a prescribed test signal under defined propagation conditions (multipath fading Case 2) with a BLER not exceeding a specified limit. Within the wanted channel, independent intracell interference sources as well as an additional intercell interference source are taken into account. Therefore, this test - as all other tests in clause 8 - mainly checks the ability of the signal processing part of the receiver to extract the wanted signal from the distorted and interfered-with input signal, whereas the tests in clause 7 concentrate on the receiver RF part. + +### 8.3.2.4 Method of test + +#### 8.3.2.4.1 Initial conditions + +##### 8.3.2.4.1.0 General test conditions + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested: B, M and T; see subclause 5.3. + +#### 8.3.2.4.1.1 3,84 Mcps TDD option + +- (1) Connect the BS tester (UE simulator) generating the wanted signal and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal with spreading factor 16, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.8. +- (2) The wanted signal produced by the BS tester and the interfering signals produced by the DPCH0 generators are individually passed through independent Multipath Fading Simulators (MFS) before entering the combining network. Each MFS shall be configured to simulate multipath fading Case 2. + +#### 8.3.2.4.1.2 1,28 Mcps TDD option + +- (1) Connect the BS tester (UE simulator) generating the wanted signal and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal with spreading factor 8, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.8A. +- (2) The wanted signal produced by the BS tester and the interfering signals produced by the DPCH0 generators are individually passed through independent Multipath Fading Simulators (MFS) before entering the combining network. Each MFS shall be configured to simulate multipath fading Case 2. + +#### 8.3.2.4.1.3 7,68 Mcps TDD option + +- (1) Connect the BS tester (UE simulator) generating the wanted signal and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal with spreading factor 32, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.8B. +- (2) The wanted signal produced by the BS tester and the interfering signals produced by the DPCH0 generators are individually passed through independent Multipath Fading Simulators (MFS) before entering the combining network. Each MFS shall be configured to simulate multipath fading Case 2. + +#### 8.3.2.4.2 Procedure + +##### 8.3.2.4.2.1 3,84 Mcps TDD option + +- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value $I_{oc}$ as specified in table 8.8. +- (2) For a given test defined by the information data rate and the BLER objective, set the power of each DPCH0 measured at the BS antenna connector during the active time slots to the value specified in table 8.101. +- (3) Set up a call between the BS tester generating the wanted signal and the BS. The characteristics of the call shall be configured according to the information data rate to be provided and the corresponding UL reference measurement channel defined in Annex A. Depending on the information data rate, the UL reference measurement channel makes use of one or two Dedicated Physical Channels (DPCH1 and DPCH2) with different spreading factors SF. The power(s) of DPCH1 and DPCH2 (if applicable) measured at the BS antenna connector during the active time slots shall be set to the value(s) given in table 8.10. +- (4) Measure the BLER of the wanted signal at the BS receiver. + +**Table 8.10: Parameters of DPCH0 and the wanted signal** + +| Test Number | BLER objective | Number of DPCH 0 | Power of each DPCH 0 measured at the BS antenna connector [dBm] | Parameters of the wanted signal | | | +|-------------|------------------|-----------------------------|----------------------------------------------------------------------------|---------------------------------|----|--------------------------------------------------| +| | | | | DPCH | SF | Power measured at the BS antenna connector [dBm] | +| 1 | 10 -2 | 2 | -95,4 | DPCH 1 | 8 | -92,4 | +| 2 | 10 -1 | 0 | - | DPCH 1 | 16 | -95,8 | +| | | | | DPCH 2 | 4 | -89,8 | +| | 10 -2 | 0 | - | DPCH 1 | 16 | -93,5 | +| | | | | DPCH 2 | 4 | -87,5 | +| 3 | 10 -1 | 0 | - | DPCH 1 | 16 | -94,9 | +| | | | | DPCH 2 | 2 | -85,9 | +| | 10 -2 | 0 | - | DPCH 1 | 16 | -92,5 | +| | | | | DPCH 2 | 2 | -83,5 | +| 4 | 10 -1 | 0 | - | DPCH 1 | 2 | -86,2 | +| | 10 -2 | 0 | - | DPCH 1 | 2 | -83,8 | + +#### 8.3.2.4.2.2 1,28 Mcps TDD option + +- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value Ioc as specified in table 8.8A. +- (2) For a given test defined by the information data rate and the BLER objective, set the power of each DPCH0 measured at the BS antenna connector during the active time slots to the value specified in table 8.10A. +- (3) Set up a call between the BS tester generating the wanted signal and the BS. The characteristics of the call shall be configured according to the information data rate to be provided and the corresponding UL reference measurement channel defined in Annex A. Depending on the information data rate, the UL reference measurement channel makes use of one or two Dedicated Physical Channels (DPCH1 and DPCH2) with different spreading factors SF. The power(s) of DPCH1 and DPCH2 (if applicable) measured at the BS antenna connector during the active time slots shall be set to the value(s) given in table 8.10A. +- (4) Measure the BLER of the wanted signal at the BS receiver. + +**Table 8.10A: Parameters of DPCH0 and the wanted signal for 1,28 Mcps TDD** + +| Test Number | BLER objective | Number of DPCH 0 | Power of each DPCH 0 measured at the BS antenna connector [dBm] | Parameters of the wanted signal | | | +|-------------|------------------|-----------------------------|----------------------------------------------------------------------------|---------------------------------|----|--------------------------------------------------| +| | | | | DPCH | SF | Power measured at the BS antenna connector [dBm] | +| 1 | 10 -2 | 4 | -91.3 | DPCH 1 | 8 | -91.3 | +| 2 | 10 -1 | 1 | -94.4 | DPCH 1 | 2 | -88.4 | +| | 10 -2 | 1 | -92.1 | DPCH 1 | 2 | -86.1 | +| 3 | 10 -1 | 1 | -93.8 | DPCH 1 | 2 | -87.8 | +| | 10 -2 | 1 | -91.7 | DPCH 1 | 2 | -85.7 | +| 4 | 10 -1 | 0 | - | DPCH 1 | 16 | -95.7 | +| | | | | DPCH 2 | 2 | -86.7 | +| | 10 -2 | 0 | - | DPCH 1 | 16 | -93.4 | +| | | | | DPCH 2 | 2 | -84.4 | + +#### 8.3.2.4.2.3 7,68 Mcps TDD option + +- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value Ioc as specified in table 8.8B. +- (2) For a given test defined by the information data rate and the BLER objective, set the power of each DPCH0 measured at the BS antenna connector during the active time slots to the value specified in table 8.10B. +- (3) Set up a call between the BS tester generating the wanted signal and the BS. The characteristics of the call shall be configured according to the information data rate to be provided and the corresponding UL reference measurement channel defined in Annex A. Depending on the information data rate, the UL reference measurement channel makes use of one or two Dedicated Physical Channels (DPCH1 and DPCH2) with different + +spreading factors SF. The power(s) of DPCH1 and DPCH2 (if applicable) measured at the BS antenna connector during the active time slots shall be set to the value(s) given in table 8.10B. + +(4) Measure the BLER of the wanted signal at the BS receiver. + +**Table 8.10B: Parameters of DPCH0 and the wanted signal** + +| Test Number | BLER objective | Number of DPCH 0 | Power of each DPCH 0 measured at the BS antenna connector [dBm] | Parameters of the wanted signal | | | +|-------------|------------------|-----------------------------|----------------------------------------------------------------------------|---------------------------------|----|--------------------------------------------------| +| | | | | DPCH | SF | Power measured at the BS antenna connector [dBm] | +| 1 | 10 -2 | 6 | -97 | DPCH 1 | 16 | -94 | + +### 8.3.2.5 Test Requirements + +NOTE: If the Test Requirements below differ from the Minimum Requirements, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +#### 8.3.2.5.1 3,84 Mcps TDD option + +The BLER measured according to subclause 8.3.2.4.2 shall not exceed the limits specified in table 8.9. + +#### 8.3.2.5.2 1,28 Mcps TDD option + +The BLER measured according to subclause 8.3.2.4.2 shall not exceed the limits specified in table 8.9A + +#### 8.3.2.5.3 7,68 Mcps TDD option + +The BLER measured according to subclause 8.3.2.4.2 shall not exceed the limits specified in table 8.9B. + +## 8.3.3 Multipath fading Case 3 + +### 8.3.3.1 Definition and applicability + +The performance requirement of DCH in multipath fading Case 3 is determined by the maximum Block Error Ratio (BLER) allowed when the receiver input signal is at a specified $\hat{I}_{or}/I_{oc}$ limit. The BLER is calculated for each of the measurement channels supported by the base station. + +The requirements in this subclause shall apply to Wide Area BS only. There is no requirement to test Local Area BS and Home BS in multipath fading Case 3 conditions. + +### 8.3.3.2 Minimum Requirements + +#### 8.3.3.2.1 3,84 Mcps TDD option + +For the parameters specified in table 8.11, the BLER should not exceed the piece-wise linear BLER curve specified in Table 8.12. These requirements are applicable for TFCS size 16. + +**Table 8.11: Parameters in multipath Case 3 channel** + +| Parameters | Unit | Test 1 | Test 2 | Test 3 | Test 4 | +|-----------------------------------------|--------------|---------------------------|-------------------|-------------------|--------| +| Number of DPCH 0 | | 2 | 0 | 0 | 0 | +| $\frac{DPCH_{0\_Ec}}{I_{or}}$ | dB | -6 | - | - | - | +| $I_{oc}$ | dBm/3,84 MHz | -89 | | | | +| Cell Parameter* | | 0,1 | | | | +| DPCH Channelization Codes* | C(k,Q) | C(1,8) | C(1,4)
C(5,16) | C(1,2)
C(9,16) | C(1,2) | +| DPCH 0 Channelization Codes* | C(k,Q) | C(i,16) $3 \leq i \leq 4$ | - | - | - | +| Information Data Rate | Kbps | 12,2 | 64 | 144 | 384 | + +\*Note: Refer to TS 25.223 for definition of channelization codes and cell parameter. + +**Table 8.12: Performance requirements in multipath Case 3 channel.** + +| Test Number | $\frac{\hat{I}_{or}}{I_{oc}}$ [dB] | BLER | +|-------------|------------------------------------|-----------| +| 1 | -0,1 | $10^{-2}$ | +| 2 | 0,8 | $10^{-1}$ | +| | 2,7 | $10^{-2}$ | +| | 4,2 | $10^{-3}$ | +| 3 | 4,5 | $10^{-1}$ | +| | 6,3 | $10^{-2}$ | +| | 8,0 | $10^{-3}$ | +| 4 | 3,6 | $10^{-1}$ | +| | 5,0 | $10^{-2}$ | +| | 6,3 | $10^{-3}$ | + +The normative reference for this requirement is TS 25.105 [1] subclause 8.3.3.1.1. + +### 8.3.3.2.2 1,28 Mcps TDD option + +For the parameters specified in table 8.11A, the BLER should not exceed the piece-wise linear BLER curve specified in Table 8.12A. These requirements are applicable for TFCS size 16. + +**Table 8.11A: Parameters in multipath Case 3 channel (1,28 Mcps option)** + +| Parameters | Unit | Test 1 | Test 2 | Test 3 | Test 4 | +|------------------------------------|--------------|--------|--------|--------|--------| +| Number of DPCH o | | 4 | 1 | 1 | 0 | +| Spread factor of DPCH o | | 8 | 8 | 8 | | +| $\frac{DPCH_o - E_c}{I_{or}}$ | dB | -7 | -7 | -7 | - | +| $I_{oc}$ | dBm/1,28 MHz | | | -91 | | +| Information Data Rate | kbps | 12,2 | 64 | 144 | 384 | + +**Table 8.12A: Performance requirements multipath Case 3 channel (1,28 Mcps option).** + +| Test Number | $\frac{\hat{I}_{or}}{I_{oc}}$ [dB] | BLER | +|-------------|------------------------------------|-----------| +| 1 | 5.6 | $10^{-2}$ | +| 2 | 3.2 | $10^{-1}$ | +| | 4.6 | $10^{-2}$ | +| | 5.9 | $10^{-3}$ | +| 3 | 3.7 | $10^{-1}$ | +| | 4.8 | $10^{-2}$ | +| | 5.9 | $10^{-3}$ | +| 4 | 3.9 | $10^{-1}$ | +| | 4.8 | $10^{-2}$ | +| | 5.7 | $10^{-3}$ | + +The normative reference for this requirement is TS 25.105 [1] subclause 8.3.3.1.2 + +### 8.3.3.2.3 7,68 Mcps TDD option + +For the parameters specified in table 8.11B, the BLER should not exceed the piece-wise linear BLER curve specified in Table 8.12B. These requirements are applicable for TFCS size 16. + +**Table 8.11B: Parameters in multipath Case 3 channel** + +| Parameters | Unit | Test 1 | +|--------------------------------------------------------------------------------------|--------------|-------------------------------| +| Number of DPCH 0 | | 6 | +| | dB | -9 | +| $I_{oc}$ | dBm/7.68 MHz | -89 | +| Cell Parameter* | | 0,1 | +| DPCH Channelization Codes* | C(k,Q) | C(1, 16) | +| DPCH 0 Channelization Codes* | C(k,Q) | C(i, 32)
$3 \leq i \leq 8$ | +| Information Data Rate | kbps | 12.2 | +| *Note: Refer to TS 25.223 for definition of channelization codes and cell parameter. | | | + +**Table 8.12B: Performance requirements in multipath Case 3 channel.** + +| Test Number | [dB] | BLER | +|-------------|------|-----------| +| 1 | -0.1 | $10^{-2}$ | + +The normative reference for this requirement is TS 25.105 [1] subclause 8.3.3.1.3. + +### 8.3.3.3 Test purpose + +The test purpose is to verify the ability of the BS to receive a prescribed test signal under defined propagation conditions (multipath fading Case 3) with a BLER not exceeding a specified limit. Within the wanted channel, independent intracell interference sources as well as an additional intercell interference source are taken into account. Therefore, this test - as all other tests in clause 8 - mainly checks the ability of the signal processing part of the receiver to extract the wanted signal from the distorted and interfered-with input signal, whereas the tests in clause 7 concentrate on the receiver RF part. + +### 8.3.3.4 Method of test + +#### 8.3.3.4.1 Initial conditions + +##### 8.3.3.4.1.0 General test conditions + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested: B, M and T; see subclause 5.3. + +##### 8.3.3.4.1.1 3,84 Mcps TDD option + +- (1) Connect the BS tester (UE simulator) generating the wanted signal and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal with spreading factor 16, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.11. +- (2) The wanted signal produced by the BS tester and the interfering signals produced by the DPCH0 generators are individually passed through independent Multipath Fading Simulators (MFS) before entering the combining network. Each MFS shall be configured to simulate multipath fading Case 3. + +##### 8.3.3.4.1.2 1,28 Mcps TDD option + +- (1) Connect the BS tester (UE simulator) generating the wanted signal and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal + +with spreading factor 8, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.11A. + +- (2) The wanted signal produced by the BS tester and the interfering signals produced by the DPCH0 generators are individually passed through independent Multipath Fading Simulators (MFS) before entering the combining network. Each MFS shall be configured to simulate multipath fading Case 3. + +#### 8.3.3.4.1.3 7,68 Mcps TDD option + +- (1) Connect the BS tester (UE simulator) generating the wanted signal and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal with spreading factor 32, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.11B. +- (2) The wanted signal produced by the BS tester and the interfering signals produced by the DPCH0 generators are individually passed through independent Multipath Fading Simulators (MFS) before entering the combining network. Each MFS shall be configured to simulate multipath fading Case 3. + +#### 8.3.3.4.2 Procedure + +##### 8.3.3.4.2.1 3,84 Mcps TDD option + +- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value $I_{oc}$ as specified in table 8.11. +- (2) For a given test defined by the information data rate and the BLER objective, set the power of each DPCH0 measured at the BS antenna connector during the active time slots to the value specified in table 8.13. +- (3) Set up a call between the BS tester generating the wanted signal and the BS. The characteristics of the call shall be configured according to the information data rate to be provided and the corresponding UL reference measurement channel defined in Annex A. Depending on the information data rate, the UL reference measurement channel makes use of one or two Dedicated Physical Channels (DPCH1 and DPCH2) with different spreading factors SF. The power(s) of DPCH1 and DPCH2 (if applicable) measured at the BS antenna connector during the active time slots shall be set to the value(s) given in table 8.131. +- (4) Measure the BLER of the wanted signal at the BS receiver. + +**Table 8.13: Parameters of DPCH0 and the wanted signal** + +| Test Number | BLER objective | Number of DPCH 0 | Power of each DPCH 0 measured at the BS antenna connector [dBm] | Parameters of the wanted signal | | | +|-------------|------------------|-----------------------------|----------------------------------------------------------------------------|---------------------------------|----|--------------------------------------------------| +| | | | | DPCH | SF | Power measured at the BS antenna connector [dBm] | +| 1 | 10 -2 | 2 | -95,1 | DPCH 1 | 8 | -92,1 | +| 2 | 10 -1 | 0 | - | DPCH 1 | 16 | -95,2 | +| | | | | DPCH 2 | 4 | -89,2 | +| | 10 -2 | 0 | - | DPCH 1 | 16 | -93,3 | +| | | | | DPCH 2 | 4 | -87,3 | +| 3 | 10 -1 | 0 | - | DPCH 1 | 16 | -94,0 | +| | | | | DPCH 2 | 2 | -85,0 | +| | 10 -2 | 0 | - | DPCH 1 | 16 | -92,2 | +| | | | | DPCH 2 | 2 | -83,2 | +| | 10 -3 | 0 | - | DPCH 1 | 16 | -90,5 | +| | | | | DPCH 2 | 2 | -81,5 | +| 4 | 10 -1 | 0 | - | DPCH 1 | 2 | -85,4 | +| | 10 -2 | 0 | - | DPCH 1 | 2 | -84,0 | +| | 10 -3 | 0 | - | DPCH 1 | 2 | -82,7 | + +## 8.3.3.4.2.2 1,28 Mcps TDD option + +- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value $I_{oc}$ as specified in table 8.11A. +- (2) For a given test defined by the information data rate and the BLER objective, set the power of each $DPCH_0$ measured at the BS antenna connector during the active time slots to the value specified in table 8.13A. +- (3) Set up a call between the BS tester generating the wanted signal and the BS. The characteristics of the call shall be configured according to the information data rate to be provided and the corresponding UL reference measurement channel defined in Annex A. Depending on the information data rate, the UL reference measurement channel makes use of one or two Dedicated Physical Channels ( $DPCH_1$ and $DPCH_2$ ) with different spreading factors SF. The power(s) of $DPCH_1$ and $DPCH_2$ (if applicable) measured at the BS antenna connector during the active time slots shall be set to the value(s) given in table 8.13A. +- (4) Measure the BLER of the wanted signal at the BS receiver. + +**Table 8.13A: Parameters of $DPCH_0$ and the wanted signal for 1,28 Mcps TDD** + +| Test Number | BLER objective | Number of $DPCH_0$ | Power of each $DPCH_0$ measured at the BS antenna connector [dBm] | Parameters of the wanted signal | | | +|-------------|----------------|--------------------|-------------------------------------------------------------------|---------------------------------|----|--------------------------------------------------| +| | | | | DPCH | SF | Power measured at the BS antenna connector [dBm] | +| 1 | $10^{-2}$ | 4 | -92.4 | $DPCH_1$ | 8 | -92.4 | +| 2 | $10^{-1}$ | 1 | -94.8 | $DPCH_1$ | 2 | -88.8 | +| | $10^{-2}$ | 1 | -93.4 | $DPCH_1$ | 2 | -87.4 | +| | $10^{-3}$ | 1 | -92.1 | $DPCH_1$ | 2 | -86.1 | +| 3 | $10^{-1}$ | 1 | -94.3 | $DPCH_1$ | 2 | -88.3 | +| | $10^{-2}$ | 1 | -93.2 | $DPCH_1$ | 2 | -87.2 | +| | $10^{-3}$ | 1 | -92.1 | $DPCH_1$ | 2 | -86.1 | +| 4 | $10^{-1}$ | 0 | - | $DPCH_1$ | 16 | -96.6 | +| | | | | $DPCH_2$ | 2 | -87.6 | +| | $10^{-2}$ | 0 | - | $DPCH_1$ | 16 | -95.7 | +| | $10^{-3}$ | 0 | - | $DPCH_2$ | 2 | -86.7 | +| | | | | $DPCH_1$ | 16 | -94.8 | +| | | | | $DPCH_2$ | 2 | -85.8 | + +## 8.3.3.4.2.3 7,68 Mcps TDD option + +- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value $I_{oc}$ as specified in table 8.11B. +- (2) For a given test defined by the information data rate and the BLER objective, set the power of each $DPCH_0$ measured at the BS antenna connector during the active time slots to the value specified in table 8.13B. +- (3) Set up a call between the BS tester generating the wanted signal and the BS. The characteristics of the call shall be configured according to the information data rate to be provided and the corresponding UL reference measurement channel defined in Annex A. Depending on the information data rate, the UL reference measurement channel makes use of one or two Dedicated Physical Channels ( $DPCH_1$ and $DPCH_2$ ) with different spreading factors SF. The power(s) of $DPCH_1$ and $DPCH_2$ (if applicable) measured at the BS antenna connector during the active time slots shall be set to the value(s) given in table 8.13B. +- (4) Measure the BLER of the wanted signal at the BS receiver. + +**Table 8.13B: Parameters of $DPCH_0$ and the wanted signal** + +| Test Number | BLER objective | Number of $DPCH_0$ | Power of each $DPCH_0$ measured at the BS antenna connector [dBm] | Parameters of the wanted signal | | | +|-------------|----------------|--------------------|-------------------------------------------------------------------|---------------------------------|----|--------------------------------------------------| +| | | | | DPCH | SF | Power measured at the BS antenna connector [dBm] | +| 1 | $10^{-2}$ | 6 | -98,1 | $DPCH_1$ | 16 | -95,1 | + +### 8.3.3.5 Test Requirements + +NOTE: If the Test Requirements below differ from the Minimum Requirements, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +#### 8.3.3.5.1 3,84 Mcps TDD option + +The BLER measured according to subclause 8.3.3.4.2 shall not exceed the limits specified in table 8.12. + +#### 8.3.3.5.2 1,28 Mcps TDD option + +The BLER measured according to subclause 8.3.3.4.2 shall not exceed the limits specified in table 8.12A. + +#### 8.3.3.5.3 7,68 Mcps TDD option + +The BLER measured according to subclause 8.3.3.4.2 shall not exceed the limits specified in table 8.12B. + +## 8.3A Demodulation of DCH in high speed train conditions + +### 8.3A.1 Definition and applicability + +The performance requirement of DCH in high speed train conditions is determined by the maximum BLER allowed when the receiver input signal is at a specified $I_{or}/I_{oc}$ limit. The BLER is calculated for the measurement channel supported by the base station. + +This requirement shall only be applied to BS supporting high speed mode. + +### 8.3A.2 Minimum requirement + +#### 8.3A.2.1 3.84 Mcps TDD option + +(void) + +#### 8.3A.2.2 1.28 Mcps TDD option + +For the parameters specified in Table 8.13C the BLER should not exceed the BLER requirement specified in Table 8.13D. These requirements are applicable for TFCS size 16. + +**Table 8.13C: DCH parameters in high speed train condition** + +| Parameters | Unit | Test 1 | Test 2 | +|--------------------------------------------------------------------------------------|-------------|-----------------------------|--------| +| Number of DPCHo | | 4 | 1 | +| Spread factor of DPCHO | | 8 | 8 | +| Scrambling code and basic midamble code number* | | 0 | 0 | +| DPCH Channelization Codes* | C(k,Q) | C(1,8) | C(1,2) | +| DPCHo Channelization Codes* | C(k,Q) | C(i,8)
$2 \leq i \leq 5$ | C(5,8) | +| $\frac{DPCH_o - E_c}{I_{or}}$ | dB | -7 | -7 | +| $I_{oc}$ | dBm/1.28MHz | -91 | | +| Information Data Rate | Kbps | 12.2 | 64 | +| *Note: Refer to TS 25.223 for definition of channelization codes and cell parameter. | | | | + +**Table 8.13D: DCH requirements in high speed train condition** + +| Test number | Scenario | dual receiver antenna diversity | [dB] | BLER | +|-------------|----------|---------------------------------|------|-----------| +| 1 | 1 | On | 4.0 | $10^{-2}$ | +| | | Off * | 7.5 | $10^{-2}$ | +| | 3 | Off * | 7.7 | $10^{-2}$ | +| 2 | 1 | On | 1.2 | $10^{-1}$ | +| | | On | 2.0 | $10^{-2}$ | +| | | Off * | 4.6 | $10^{-1}$ | +| | | Off * | 5.4 | $10^{-2}$ | +| | 3 | Off * | 4.8 | $10^{-1}$ | +| | | Off * | 6.0 | $10^{-2}$ | + +**\*Note:** The requirement is only applicable for BS without receiver antenna diversity, the required shall be applied at the BS Rx antenna port. + +The normative reference for this requirement is TS 25.105 [1] subclause 8.3A.2.2. + +### 8.3A.2.3 7.68 Mcps TDD option + +(void) + +## 8.3A.3 Test purpose + +The test shall verify the receiver's ability to receive the test signal in high speed train conditions with a BLER not exceeding the specified limit. + +## 8.3A.4 Method of test + +### 8.3A.4.1 Initial conditions + +#### 8.3A.4.1.1 General test conditions + +Test environment: normal; see subclause 5.9.1 + +RF channels to be tested: B, M and T; see subclause 5.3 + +#### 8.3A.4.1.1 3.84 Mcps TDD option + +(void) + +#### 8.3A.4.1.1 1.28 Mcps TDD option + +Connect the BS tester (UE simulator) generating the wanted signal , Channel Simulator generating Doppler shift and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal with spreading factor 8, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.13C. + +#### 8.3A.4.1.1 7.68 Mcps TDD option + +(void) + +### 8.3A.4.2 Procedure + +#### 8.3A.4.2.1 3.84 Mcps TDD option + +(void) + +#### 8.3A.4.2.2 1.28 Mcps TDD option + +- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value $I_{oc}$ as specified in table 8.13C. +- (2) For a given test defined by the information data rate and the BLER objective, set the power of each $DPCH_0$ measured at the BS antenna connector during the active time slots to the value specified in table 8.13E. +- (4) The Channel Simulator shall be configured according to the corresponding Doppler shift trajectories defined in annex B. +- (5) Set up a call between the BS tester generating the wanted signal and the BS. The characteristics of the call shall be configured according to the information data rate to be provided and the corresponding UL reference measurement channel defined in Annex A. Depending on the information data rate, the UL reference measurement channel makes use of one or two Dedicated Physical Channels ( $DPCH_1$ and $DPCH_2$ ) with different spreading factors SF. The power(s) of $DPCH_1$ and $DPCH_2$ (if applicable) measured at the BS antenna connector during the active time slots shall be set to the value(s) given in table 8.13E. +- (6) Measure the BLER of the wanted signal at the BS receiver. + +**Table 8.13E: Parameters of $DPCH_0$ and the wanted signal for 1,28 Mcps TDD** + +| Test Number | Scenario | Dual receiver antenna diversity | BLER objective | Number of $DPCH_0$ | Power of each $DPCH_0$ measured at the BS antenna connector [dBm] | Parameters of the wanted signal | | | +|-------------|----------|---------------------------------|----------------|--------------------|-------------------------------------------------------------------|---------------------------------|----|--------------------------------------------------| +| | | | | | | DPCH | SF | Power measured at the BS antenna connector [dBm] | +| 1 | 1 | On | $10^{-2}$ | 4 | -94.0 | $DPCH_1$ | 8 | -94.0 | +| | | Off * | $10^{-2}$ | 4 | -90.5 | $DPCH_1$ | 8 | -90.5 | +| | 3 | Off * | $10^{-2}$ | 4 | -90.3 | $DPCH_1$ | 8 | -90.3 | +| 2 | 1 | On | $10^{-1}$ | 1 | -96.8 | $DPCH_1$ | 2 | -90.8 | +| | | On | $10^{-2}$ | 1 | -96.0 | $DPCH_1$ | 2 | -90.0 | +| | | Off * | $10^{-1}$ | 1 | -93.4 | $DPCH_1$ | 2 | -87.4 | +| | | Off * | $10^{-2}$ | 1 | -92.6 | $DPCH_1$ | 2 | -86.6 | +| | 3 | Off * | $10^{-1}$ | 1 | -93.2 | $DPCH_1$ | 2 | -87.2 | +| | | Off * | $10^{-2}$ | 1 | -92.0 | $DPCH_1$ | 2 | -86.0 | + +\*Note: The requirement is only applicable for BS without receiver antenna diversity, the required shall be applied at the BS Rx antenna port. + +#### 8.3A.4.2.3 7.68 Mcps TDD option + +(void) + +### 8.3A.5 Test requirements + +NOTE: If the Test Requirement below differs from the Minimum Requirement, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +#### 8.3A.5.1 3,84 Mcps TDD option + +(void) + +### 8. 3A.5.2 1,28 Mcps TDD option + +The BLER measured according to subclause 8.3A.4.2.2. shall not exceed the limits specified in table 8.13F. + +**Table 8.13F: DCH requirements in high speed train condition** + +| Test number | Scenario | dual receiver antenna diversity | [dB] | BLER | +|-----------------------------------------------------------------------------------------------------------------------------------------------|----------|---------------------------------|------|-----------| +| 1 | 1 | On | 4.4 | $10^{-2}$ | +| | | Off * | 7.9 | $10^{-2}$ | +| | 3 | Off * | 8.1 | $10^{-2}$ | +| 2 | 1 | On | 1.6 | $10^{-1}$ | +| | | On | 2.4 | $10^{-2}$ | +| | | Off * | 5.0 | $10^{-1}$ | +| | | Off * | 5.8 | $10^{-2}$ | +| | 3 | Off * | 5.2 | $10^{-1}$ | +| | | Off * | 6.4 | $10^{-2}$ | +| *Note: The requirement is only applicable for BS without receiver antenna diversity, the required shall be applied at the BS Rx antenna port. | | | | | + +### 8. 3A.5.3 7,68 Mcps TDD option + +(void) + +## 8.4 Demodulation of E-DCH FRC in multipath fading conditions + +### 8.4.1 Definition and applicability + +The performance requirement of the E-DCH in multi-path fading condition is determined by the minimum throughput R. + +### 8.4.2 Minimum Requirements + +#### 8.4.2.1 3,84 Mcps TDD Option + +For the test parameters specified in Table 8.14, the minimum requirements are specified in Table 8.15. + +**Table 8.14: Test parameters for testing E-DCH (3,84 Mcps TDD Option)** + +| Parameter | Unit | Value | | | +|--------------------------------------------------------------------------------------|---------------|-----------------------|---------|---------| +| | | FRC1 | FRC2 | FRC3 | +| Max information rate | kbps | 34.7 | 1083.1 | 2073.7 | +| $I_{oc}$ | Wide Area BS | dBm/3,84 MHz -89 | | | +| | Local Area BS | dBm/3,84 MHz -74 | | | +| E-DCH $E_s/I_{or}$ | dB | 0 | 0 | 0 | +| Cell Parameter* | | 0, 1 | | | +| E-DCH channelization code* | C(k, Q) | C(1, 16) | C(1, 2) | C(1, 1) | +| RSN | | {0, 1, 2, 3} | | | +| HARQ combining | | IR | | | +| Maximum number of HARQ transmission | | 4 | | | +| Power control | | OFF | | | +| Receiver antenna diversity | | ON | | | +| Midamble | | Default midamble | | | +| Physical channels to be turned on | | E-PUCH | | | +| Propagation condition | | PA3, PB3, VA30, VA120 | | | +| *Note: Refer to TS 25.223 for definition of channelization codes and cell parameter. | | | | | + +**Table 8.15 Minimum Requirement for E-DCH (3,84 Mcps TDD Option)** + +| Fixed Reference Channel | | Reference value, $\hat{I}_{or}/I_{oc}$ (dB),
for R $\geq$ 30% and R $\geq$ 70% of maximum information bit rate | | | | +|-------------------------|-----|-------------------------------------------------------------------------------------------------------------------|--------|-------|-------| +| | | Propagation conditions | FRC1 | FRC2 | FRC3 | +| Pedestrian A (3 kmph) | 30% | | -13.76 | -0.55 | 4.94 | +| | 70% | | -9.89 | 5.2 | 12.76 | +| Pedestrian B (3 kmph) | 30% | | -12.12 | 0.48 | 5.13 | +| | 70% | | -9.46 | 5.22 | 13.1 | +| Vehicular A (30 kmph) | 30% | | -12.58 | -0.62 | 5.14 | +| | 70% | | -9.51 | 5.3 | 13.46 | +| Vehicular A (120 kmph) | 30% | | -12.55 | -0.69 | 5.1 | +| | 70% | | -9.78 | 5.22 | 13.14 | + +#### 8.4.2.2 1.28 Mcps TDD option + +For the test parameters specified in Table 8.14A, the minimum requirements are specified in Table 8.15A. + +**Table 8.14A: Test parameters for testing E-DCH (1.28 Mcps TDD Option)** + +| Parameter | Unit | Value | | | | +|-------------------------------------------------|---------------|------------------|---------|---------|---------| +| | | FRC1 | FRC2 | FRC3 | FRC4 | +| Max information rate | kbps | 56.4 | 227.8 | 515.6 | 1281.2 | +| $I_{oc}$ | Wide Area BS | dBm/1.28 MHz | -91 | | | +| | Local Area BS | dBm/1.28MHz | -77 | | | +| | Home BS | dBm/1.28MHz | -82 | | | +| Scrambling code and basic midamble code number* | | 0 | 0 | 0 | 0 | +| E-PUCH channelization code* | C(k, Q) | C(1, 4) | C(1, 2) | C(1, 2) | C(1, 1) | +| RSN | | {0, 1, 2, 3} | | | | +| HARQ combining | | IR | | | | +| Maximum number of HARQ transmission | | 4 | | | | +| Power control | | OFF | | | | +| Receiver antenna diversity | | ON | | | | +| Midamble | | Default midamble | | | | +| Propagation condition | | PA3, PB3, VA30 | | | | + +\*Note: Refer to TS 25.223 for definition of channelization codes, scrambling code and basic midamble code + +**Table 8.15A Minimum Requirement for E-DCH (1.28 Mcps TDD Option)** + +| Fixed Reference Channel | | Reference value, $\hat{I}_{or}/I_{oc}$ (dB),
for R $\geq$ 30% and R $\geq$ 70% of maximum information bit rate | | | | | +|-------------------------|-----|-------------------------------------------------------------------------------------------------------------------|-------|-------|-------|-------| +| | | Propagation conditions | FRC1 | FRC2 | FRC3 | FRC4 | +| Pedestrian A (3 kmph) | 30% | | -6.78 | -1.58 | 2.84 | 6.34 | +| | 70% | | -1.83 | 4.6 | 10.19 | 13.45 | +| Pedestrian B (3 kmph) | 30% | | -5.62 | -1.1 | 2.88 | 6.55 | +| | 70% | | -1.65 | 5.09 | 8.99 | 12.26 | +| Vehicular A (30 kmph) | 30% | | -4.96 | -0.88 | 3.09 | 7.14 | +| | 70% | | -1.2 | 6.0 | 10.89 | 14.01 | + +#### 8.4.2.3 7.68 Mcps TDD Option + +For the test parameters specified in Table 8.14B, the minimum requirements are specified in Table 8.15B. + +**Table 8.14B: Test parameters for testing E-DCH (7.68 Mcps TDD Option)** + +| Parameter | Unit | Value | | | +|--------------------------------------------------------------------------------------|---------------|-----------------------|---------|---------| +| | | FRC1 | FRC2 | FRC3 | +| Max information rate | kbps | 35.9 | 1083.1 | 2085.1 | +| $I_{oc}$ | Wide Area BS | dBm/7.68 MHz | -89 | | +| | Local Area BS | dBm/7.68 MHz | -74 | | +| E-DCH $E_c/I_{or}$ | dB | 0 | 0 | 0 | +| Cell Parameter* | | 0, 1 | | | +| E-DCH channelization code* | C(k, Q) | C(1, 32) | C(1, 4) | C(1, 2) | +| RSN | | {0, 1, 2, 3} | | | +| HARQ combining | | IR | | | +| Maximum number of HARQ transmission | | 4 | | | +| Power control | | OFF | | | +| Receiver antenna diversity | | ON | | | +| Midamble | | Default midamble | | | +| Physical channels to be turned on | | E-PUCH | | | +| Propagation condition | | PA3, PB3, VA30, VA120 | | | +| *Note: Refer to TS 25.223 for definition of channelization codes and cell parameter. | | | | | + +**Table 8.15B Minimum Requirement for E-DCH (7.68 Mcps TDD Option)** + +| Fixed Reference Channel | Reference value, $\hat{I}_{or}/I_{oc}$ (dB),
for R ≥ 30% and R ≥ 70% of maximum information bit rate | | | | +|---------------------------|---------------------------------------------------------------------------------------------------------|--------|-------|------| +| | Propagation conditions | FRC1 | FRC2 | FRC3 | +| Pedestrian A
(3 kmph) | 30% | -16.22 | -3.71 | 1.72 | +| | 70% | -12.56 | 1.79 | 9.39 | +| Pedestrian B
(3 kmph) | 30% | -14.44 | -3.71 | 1.45 | +| | 70% | -11.54 | 1.48 | 8.87 | +| Vehicular A
(30 kmph) | 30% | -14.81 | -3.68 | 1.48 | +| | 70% | -11.84 | 1.89 | 9.28 | +| Vehicular A
(120 kmph) | 30% | -14.81 | -3.83 | 1.38 | +| | 70% | -12.27 | 1.67 | 9.17 | + +### 8.4.3 Test purpose + +The test shall verify the receiver's ability to receive the test signal under multipath fading propagation conditions with a throughput not below a specified limit.† + +## 8.4.4 Method of test + +### 8.4.4.1 Initial conditions + +#### 8.4.4.1.0 General test conditions + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested: B, M and T; see subclause 5.3. + +#### 8.4.4.1.1 3,84 Mcps TDD option + +- (1) Connect the BS tester (UE simulator) generating the wanted signal and a band-limited white noise source, simulating interference from other cells, to both BS antenna connectors for diversity reception via a combining network. +- (2) The wanted signal produced by the BS tester to both BS antenna connectors are individually passed through independent Multipath Fading Simulators (MFS) before entering the combining network. Each MFS shall be configured to simulate multipath fading conditions specified in Table 8.14 and 8.15. + +#### 8.4.4.1.2 1.28Mcps TDD option + +- (1) Connect the BS tester (UE simulator) generating the wanted signal and a band-limited white noise source, simulating interference from other cells, to both BS antenna connectors for diversity reception via a combining network. +- (2) The wanted signal produced by the BS tester to both BS antenna connectors are individually passed through independent Multipath Fading Simulators (MFS) before entering the combining network. Each MFS shall be configured to simulate multipath fading conditions specified in Table 8.14A and 8.15A. + +#### 8.4.4.1.3 7.68 Mcps TDD option + +- (1) Connect the BS tester (UE simulator) generating the wanted signal and a band-limited white noise source, simulating interference from other cells, to both BS antenna connectors for diversity reception via a combining network. +- (2) The wanted signal produced by the BS tester to both BS antenna connectors are individually passed through independent Multipath Fading Simulators (MFS) before entering the combining network. Each MFS shall be configured to simulate multipath fading conditions specified in Table 8.14B and 8.15B. + +#### 8.4.4.2 Procedure + +##### 8.4.4.2.1 3,84 Mcps TDD option + +- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value $I_{oc}$ as specified in table 8.14. +- (2) The characteristics of the wanted signal shall be configured according to the corresponding E-DCH Fixed Reference Channel (FRC) measurement channel defined in annex A.3. Depending upon the E-DCH FRC measurement channel makes use of one physical channel (E-PUCH) with different spreading factors SF. The power of the E-PUCH measured at the BS antenna connector during the active time slots shall be set to the values given in Table 8.16. +- (3) The Multipath Fading Simulators shall be configured according to the corresponding channel model defined in annex D. +- (4) For each of the fixed reference channels in table 8.16 applicable for the base station, measure the throughput for each E-PUCH power and propagation condition settings. + +**Table 8.16: Parameters of the wanted signal (E-PUCH) (3,84 Mcps TDD Option)** + +| Propagation Conditions | Throughput R
(% of max
information bit
rate) | Wanted signal (E-PUCH) power measured at the BS
antenna connector (dBm) | | | | | | +|------------------------|-------------------------------------------------------|----------------------------------------------------------------------------|--------|--------|---------------|--------|--------| +| | | Wide Area BS | | | Local Area BS | | | +| | | FRC1 | FRC2 | FRC3 | FRC1 | FRC2 | FRC3 | +| Pedestrian A (3 kmph) | 30% | -102.76 | -89.55 | -84.06 | -87.76 | -74.55 | -69.06 | +| | 70% | -98.89 | -83.80 | -76.24 | -83.89 | -68.80 | -61.24 | +| Pedestrian B (3 kmph) | 30% | -101.12 | -88.52 | -83.87 | -86.12 | -73.52 | -68.87 | +| | 70% | -98.46 | -83.78 | -75.90 | -83.46 | -68.78 | -60.90 | +| Vehicular A (30 kmph) | 30% | -101.58 | -89.62 | -83.86 | -86.58 | -74.62 | -68.86 | +| | 70% | -98.51 | -83.70 | -75.54 | -83.51 | -68.70 | -60.54 | +| Vehicular A (120 kmph) | 30% | -101.55 | -89.69 | -83.90 | -86.55 | -74.69 | -68.90 | +| | 70% | -98.78 | -83.78 | -75.86 | -83.78 | -68.78 | -60.86 | + +##### 8.4.4.2.2 1.28Mcps TDD option + +- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value $I_{oc}$ as specified in table 8.14A. +- (2) The characteristics of the wanted signal shall be configured according to the corresponding E-DCH Fixed Reference Channel (FRC) measurement channel defined in annex A.3. Depending upon the E-DCH FRC measurement channel makes use of one physical channel (E-PUCH) with different spreading factors SF. The power of the E-PUCH measured at the BS antenna connector during the active time slots shall be set to the values given in Table 8.16A. + +- (3) The Multipath Fading Simulators shall be configured according to the corresponding channel model defined in annex B. +- (4) For each of the fixed reference channels in table 8.16A applicable for the base station, measure the throughput for each E-PUCH power and propagation condition settings. + +**Table 8.16A: Parameters of the wanted signal (E-PUCH) (1.28 Mcps TDD Option)** + +| Propagation Conditions | Throughput R (% of max information bit rate) | Wanted signal (E-PUCH) power measured at the BS antenna connector (dBm) | | | | | | | | | | | | +|------------------------|----------------------------------------------|-------------------------------------------------------------------------|--------|--------|--------|---------------|--------|--------|--------|--------------|--------|--------|--------| +| | | Wide Area BS | | | | Local Area BS | | | | Wide Area BS | | | | +| | | FRC1 | FRC2 | FRC1 | FRC2 | FRC1 | FRC2 | FRC1 | FRC2 | FRC1 | FRC2 | FRC3 | FRC4 | +| Pedestrian A (3 kmph) | 30% | -97.78 | -92.58 | -97.78 | -92.58 | -97.78 | -92.58 | -97.78 | -92.58 | -88.78 | -83.58 | -79.16 | -75.66 | +| | 70% | -92.83 | -86.4 | -92.83 | -86.4 | -92.83 | -86.4 | -92.83 | -86.4 | -83.83 | -77.4 | -71.81 | -68.55 | +| Pedestrian B (3 kmph) | 30% | -96.62 | -92.1 | -96.62 | -92.1 | -96.62 | -92.1 | -96.62 | -92.1 | -87.62 | -83.1 | -79.12 | -75.45 | +| | 70% | -92.65 | -85.91 | -92.65 | -85.91 | -92.65 | -85.91 | -92.65 | -85.91 | -83.65 | -76.91 | -73.01 | -69.74 | +| Vehicular A (30 kmph) | 30% | -95.96 | -91.88 | -95.96 | -91.88 | -95.96 | -91.88 | -95.96 | -91.88 | -86.96 | -82.88 | -78.91 | -74.86 | +| | 70% | -92.2 | -85 | -92.2 | -85 | -92.2 | -85 | -92.2 | -85 | -83.2 | -76 | -71.11 | -67.99 | + +#### 8.4.4.2.3 7.68 Mcps TDD option + +- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value $I_{oc}$ as specified in table 8.14B. +- (2) The characteristics of the wanted signal shall be configured according to the corresponding E-DCH Fixed Reference Channel (FRC) measurement channel defined in annex A.3. Depending upon the E-DCH FRC measurement channel makes use of one physical channel (E-PUCH) with different spreading factors SF. The power of the E-PUCH measured at the BS antenna connector during the active time slots shall be set to the values given in Table 8.16B. +- (3) The Multipath Fading Simulators shall be configured according to the corresponding channel model defined in annex D. +- (4) For each of the fixed reference channels in table 8.16B applicable for the base station, measure the throughput for each E-PUCH power and propagation condition settings. + +**Table 8.16B: Parameters of the wanted signal (E-PUCH) (7.68 Mcps TDD Option)** + +| Propagation Conditions | Throughput R (% of max information bit rate) | Wanted signal (E-PUCH) power measured at the BS antenna connector (dBm) | | | | | | +|------------------------|----------------------------------------------|-------------------------------------------------------------------------|--------|--------|---------------|--------|--------| +| | | Wide Area BS | | | Local Area BS | | | +| | | FRC1 | FRC2 | FRC3 | FRC1 | FRC2 | FRC3 | +| Pedestrian A (3 kmph) | 30% | -105.22 | -92.71 | -87.28 | -90.22 | -77.71 | -72.28 | +| | 70% | -101.56 | -87.21 | -79.61 | -86.56 | -72.21 | -64.61 | +| Pedestrian B (3 kmph) | 30% | -103.44 | -92.71 | -87.55 | -88.44 | -77.71 | -72.55 | +| | 70% | -100.54 | -87.52 | -80.13 | -85.54 | -72.52 | -65.13 | +| Vehicular A (30 kmph) | 30% | -103.81 | -92.68 | -87.52 | -88.81 | -77.68 | -72.52 | +| | 70% | -100.84 | -87.11 | -79.72 | -85.84 | -72.11 | -64.72 | +| Vehicular A (120 kmph) | 30% | -103.81 | -92.83 | -87.62 | -88.81 | -77.83 | -72.62 | +| | 70% | -101.27 | -87.33 | -79.83 | -86.27 | -72.33 | -64.83 | + +#### 8.4.5 Test Requirements + +NOTE: If the Test Requirements below differ from the Minimum Requirements, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +#### 8.4.5.1 3,84 Mcps TDD option + +The throughput measured according to subclause 8.4.4.2 shall be at least the limits specified in table 8.15. + +#### 8.4.5.2 1.28 Mcps TDD option + +The throughput measured according to subclause 8.4.4.2 shall be at least the limits specified in table 8.15A. + +#### 8.4.5.3 7.68 Mcps TDD option + +The throughput measured according to subclause 8.4.4.2 shall be at least the limits specified in table 8.15B. + +### 8.5 Performance of ACK error detection for HS-SICH + +#### 8.5.1 ACK error detection in static propagation conditions + +##### 8.5.1.1 3.84 Mcps TDD option + +(void) + +##### 8.5.1.2 1.28 Mcps TDD option + +###### 8.5.1.2.1 Definition and applicability + +The performance requirement of the HS-SICH is ACK error detection, $P(\text{ACK} \rightarrow \text{NACK})$ when ACK is transmitted. + +###### 8.5.1.2.2 Minimum requirement + +The performance requirement of ACK error detection, $P(\text{ACK} \rightarrow \text{NACK})$ should not exceed the required error ratio for the specified in Table 8.18A. + +**Table 8.17A: Test parameters for testing ACK error detection using HS-SICH type1 (1.28 Mcps TDD Option)** + +| Parameters | | Unit | Test | +|--------------------------------------------------------------------------------------|--------------|--------------|--------------------------------| +| Number of DPCHo | | | 2 | +| Spread factor of DPCHo | | | 8 | +| Scrambling code and basic midamble code number* | | | 0 | +| DPCHo Channelization Codes* | | $C(k, Q)$ | $C(i, 8)$
$2 \leq i \leq 3$ | +| | | dB | -4 | +| | | dB | -7 | +| loc | Wide Area BS | dBm/1,28 MHz | -91 | +| | Home BS | dBm/1,28 MHz | -82 | +| Closed loop power control | | | Off | +| Midamble | | | Default midamble | +| *Note: Refer to TS 25.223 for definition of channelization codes and cell parameter. | | | | + +**Table 8.17B: Test parameters for testing ACK error detection using HS-SICH type2 (1.28Mcps TDD Option)** + +| Parameters | | Unit | Test | +|-------------------------------------------------------------------------------------|--------------|--------------|---------------------| +| Number of DPCH 0 | | | 2 | +| Spread factor of DPCH 0 | | | 8 | +| Scrambling code and basic midamble code number (note) | | | 0 | +| DPCH 0 Channelization Codes* | | C(k,Q) | C(i,8)
2 ≤ i ≤ 3 | +| | | dB | -4.8 | +| | | dB | -4.8 | +| I oc | Wide Area BS | dBm/1.28 MHz | -91 | +| | Home BS | dBm/1.28 MHz | -82 | +| Closed loop power control | | | Off | +| Midamble | | | Default midamble | +| NOTE: Refer to TS 25.223 for definition of channelization codes and cell parameter. | | | | + +**Table 8.18A: Performance requirements for ACK error detection in AWGN channel using HS-SICH type1** + +| Received | Required error ratio | +|----------|----------------------| +| -3,1 dB | < 10 -2 | + +**Table 8.18B: Performance requirements for ACK error detection in AWGN channel using HS-SICH type2** + +| Received | Required error ratio | +|----------|----------------------| +| -5.3 dB | < 10 -2 | + +The reference for this requirement is TS 25.105 subclause 8.5. + +#### 8.5.1.2.3 Test purpose + +The test shall verify the receiver's ability to receive the test signal under static propagation conditions with an error ratio not exceeding a specified limit. + +#### 8.5.1.2.4 Method of test + +##### 8.5.1.2.4.1 Initial conditions + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested: B, M and T; see subclause 5.3 + +- (1) Connect the BS tester generating the wanted signal and AWGN generators to both BS antenna connectors for diversity reception via a combining network as shown in annex B. Connect the BS tester (UE simulator) generating the wanted signal and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal with spreading factor 8, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.17A. + +##### 8.5.1.2.4.2 Procedure + +- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value Ioc as specified in table 8.17A. + +- (2) The characteristics of the wanted signal (HS-SICH) shall be configured according to the corresponding UL reference measurement channel defined in annex A. Set the power of HS-SICH and each DPCH0 measured at the BS antenna connector during the active time slots to the value specified in table 8.17A. +- (3) The test signal generator sends the ACKs with HS-SICH and DPCH0s. Adjust the equipment so that required specified in table 8.18A is achieved The receiver tries to detect ACK. The error ratio is calculated for the ACKs that have been detected. + +#### 8.5.1.2.5 Test requirements + +The performance of ACK error detection, $P(\text{ACK} \rightarrow \text{NACK})$ should not exceed the required error ratio for the specified in Table 8.19A. + +**Table 8.19A: Performance requirements for ACK error detection in AWGN channel using HS-SICH type1** + +| Received | Required error ratio | +|----------|----------------------| +| -2,7dB | $< 10^{-2}$ | + +**Table 8.19B: Performance requirements for ACK error detection in AWGN channel using HS-SICH type2** + +| Received | Required error ratio | +|----------|----------------------| +| -4.9dB | $< 10^{-2}$ | + +NOTE: If the Test Requirements below differ from the Minimum Requirements, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +### 8.5.2 ACK error detection in multipath fading conditions + +#### 8.5.2.1 3,84Mcps TDD option + +(void) + +#### 8.5.2.2 1,28Mcps TDD option + +##### 8.5.2.2.1 Definition and applicability + +The performance requirement of the HS-SICH is ACK error detection, $P(\text{ACK} \rightarrow \text{NACK})$ when ACK is transmitted.. + +##### 8.5.2.2.2 Minimum requirement + +The performance of ACK error detection, $P(\text{ACK} \rightarrow \text{NACK})$ should not exceed the required error ratio for the specified in Table 8.20A. + +**Table 8.20A: Test parameters for testing ACK error detection using HS-SICH type1 (1,28Mcps TDD Option)** + +| Parameters | | Unit | Test | +|--------------------------------------------------------------------------------------|--------------|--------------|-----------------------------| +| Number of DPCH 0 | | | 2 | +| Spread factor of DPCH 0 | | | 8 | +| Scrambling code and basic midamble code number* | | | 0 | +| DPCH 0 Channelization Codes* | | C(k,Q) | C(i,8)
$2 \leq i \leq 3$ | +| | | dB | -4 | +| | | dB | -7 | +| I oc | Wide Area BS | dBm/1,28 MHz | -91 | +| | Home BS | dBm/1,28 MHz | -82 | +| Closed loop power control | | | Off | +| Midamble | | | Default midamble | +| *Note: Refer to TS 25.223 for definition of channelization codes and cell parameter. | | | | + +**Table 8.20B: Test parameters for testing ACK error detection using HS-SICH type2 (1.28Mcps TDD Option)** + +| Parameters | | Unit | Test | +|-------------------------------------------------------------------------------------|--------------|--------------|-----------------------------| +| Number of DPCH 0 | | | 2 | +| Spread factor of DPCH 0 | | | 8 | +| Scrambling code and basic midamble code number (note) | | | 0 | +| DPCH 0 Channelization Codes* | | C(k,Q) | C(i,8)
$2 \leq i \leq 3$ | +| | | dB | -4.8 | +| | | dB | -4.8 | +| I oc | Wide Area BS | dBm/1.28 MHz | -91 | +| | Home BS | dBm/1,28 MHz | -82 | +| Closed loop power control | | | Off | +| Midamble | | | Default midamble | +| NOTE: Refer to TS 25.223 for definition of channelization codes and cell parameter. | | | | + +**Table 8.21A: Performance requirements for ACK error detection in fading channels using HS-SICH type1** + +| Propagation conditions | Received(dB) | Required error ratio | +|-----------------------------------------------|--------------|----------------------| +| Case 1 | 1,2 | $< 10^{-2}$ | +| Case 2* | 0,9 | $< 10^{-2}$ | +| Case 3* | 0,2 | $< 10^{-2}$ | +| *Note: This case is not applicable to Home BS | | | + +**Table 8.21B: Performance requirements for ACK error detection in fading channels using HS-SICH type2** + +| Propagation conditions | Received(dB) | Required error ratio | +|-----------------------------------------------|--------------|----------------------| +| Case 1 | -1,2 | $< 10^{-2}$ | +| Case 2* | -0,7 | $< 10^{-2}$ | +| *Note: This case is not applicable to Home BS | | | + +The reference for this requirement is TS 25.105 subclause 8.5. + +### 8.5.2.2.3 Test purpose + +The test shall verify the receiver's ability to receive the test signal under multipath fading propagation conditions with an error ratio not exceeding a specified limit. + +### 8.5.2.2.4 Method of test + +#### 8.5.2.2.4.1 Initial conditions + +Test environment: normal; see subclause 5.9.1. + +RF channels to be tested: B, M and T; see subclause 5.3 + +- (1) Connect the BS tester generating the wanted signal and AWGN generators to both BS antenna connectors for diversity reception via a combining network as shown in annex B. Connect the BS tester (UE simulator) generating the wanted signal and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators), and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 generator shall produce an interfering signal that is equivalent to a valid UTRA TDD signal with spreading factor 8, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.20A. +- (2) The wanted signal produced by the BS tester and the interfering signals produced by the DPCH0 generators are individually passed through independent Multipath Fading Simulators (MFS) before entering the combining network. Each MFS shall be configured to simulate multipath fading Case 3. + +#### 8.5.2.2.4.2 Procedure + +- (1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value $I_{oc}$ as specified in table 8.20A. +- (2) The characteristics of the wanted signal (HS-SICH) shall be configured according to the corresponding UL reference measurement channel defined in annex A. Set the power of HS-SICH and each DPCH0 measured at the BS antenna connector during the active time slots to the value specified in table 8.20A. +- (3) The test signal generator sends the ACKs with HS-SICH and DPCH0s. Adjust the equipment so that required specified in table 8.21A is achieved The receiver tries to detect ACK. The error ratio is calculated for the ACKs that have been detected. + +### 8.5.2.2.5 Test requirements + +The performance of ACK error detection, $P(ACK \rightarrow NACK)$ should not exceed the required error ratio for the specified in Table 8.22A. + +**Table 8.22A: Performance requirements for ACK error detection in fading channels using HS-SICH type1** + +| Propagation conditions | Received (dB) | Required error ratio | +|-----------------------------------------------|---------------|----------------------| +| Case 1 | 1,8 | $< 10^{-2}$ | +| Case 2* | 1,5 | $< 10^{-2}$ | +| Case 3* | 0,8 | $< 10^{-2}$ | +| *Note: This case is not applicable to Home BS | | | + +**Table 8.22B: Performance requirements for ACK error detection in fading channels using HS-SICH type2** + +| Propagation conditions | Received (dB) | Required error ratio | +|-----------------------------------------------|---------------|----------------------| +| Case 1 | -0.6 | $< 10^{-2}$ | +| Case 2* | -0.1 | $< 10^{-2}$ | +| *Note: This case is not applicable to Home BS | | | + +NOTE: If the Test Requirements below differ from the Minimum Requirements, then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.11 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D. + +--- + +## Annex A (normative): Measurement Channels + +A.1 (void) + +A.2 Reference measurement channel + +A.2.1 UL reference measurement channel (12,2 kbps) + +A.2.1.1 3,84 Mcps TDD option + +Table A.1 + +| Parameter | Value | +|-----------------------------------------------------------------------|------------------| +| Information data rate | 12.2 kbps | +| RU's allocated | 2 RU | +| Midamble | 512 chips | +| Interleaving | 20 ms | +| Power control | 2 Bit/user | +| TFCI | 16 Bit/user | +| Inband signalling DCCH | 2 kbps | +| Puncturing level at Code rate 1/3 : DCH of the DTCH / DCH of the DCCH | 10% / 0% | + +![Figure A.1: Data flow diagram showing the processing of information data and DCCH through various stages including CRC attachment, tail bit attachment, convolutional coding, interleaving, RF-segmentation, puncturing, service multiplexing, and slot segmentation into four radio frames.](cf734b5645d3e02a8df25f67904cd2d3_img.jpg) + +The diagram illustrates the data processing flow for a 1,28 Mcps option. It starts with 'Information data' (244 bits) and 'DCCH' (4 bits MAC-Header, 96 bits). The process includes CRC attachment (16 bits), tail bit attachment (8 bits), convolutional coding at rate 1/3 (resulting in 804 bits), 1st interleaving, RF-segmentation into four 402-bit segments, puncturing and ratematching (10% level, resulting in 362 bits per segment), service multiplexing with 90-bit DCCH segments, 2nd interleaving, and finally slot segmentation into four radio frames. Each radio frame contains a midamble (MA), scrambling codes (SC), and data segments. The DCCH path shows MAC-Header (100 bits), CRC (12 bits), and tail bits (8 bits) being processed through convolutional coding and interleaving before being multiplexed with the data. + +Figure A.1: Data flow diagram showing the processing of information data and DCCH through various stages including CRC attachment, tail bit attachment, convolutional coding, interleaving, RF-segmentation, puncturing, service multiplexing, and slot segmentation into four radio frames. + +Figure A.1 + +A.2.1.2 1,28 Mcps option + +Table A.1A + +| Parameter | Value | +|----------------------------------------------------------------------|-----------------------| +| Information data rate | 12.2 kbps | +| RU's allocated | 1TS (1*SF8) = 2RU/5ms | +| Midamble | 144 | +| Interleaving | 20 ms | +| Power control | 4 Bit/user/10ms | +| TFCI | 16 Bit/user/10ms | +| Synchronisation Shift (SS) | 4 Bit/user/10ms | +| Inband signalling DCCH | 2.4 kbps | +| Puncturing level at Code rate 1/3 : DCH of the DTCH/ DCH of the DCCH | 33% / 33% | + +![Figure A.1A: Bit processing flow diagram for 7,68 Mcps TDD Option. The diagram shows the flow of bits from Information and MAC Header through various processing stages including CRC, Tail bit, Conv. Coding, 1st Interleaving, RF, Rate Matching, 2nd Interleaving, TFCI, TPC and Physical Channel mapping to Slots across 8 sub-frames.](9ba478ec5af01fd2fb458d145565198e_img.jpg) + +The diagram illustrates the bit processing flow for the 7,68 Mcps TDD Option. It is divided into three main horizontal sections: Information, MAC Header, and Slot. + +- Information Path:** + - Starts with 244 bits of Information. + - CRC adds 16 bits (244 + 16). + - Tail bit adds 8 bits (260bit/20m). + - Conv. Coding: (260+8)\*3=80. + - 1st Interleaving: 804bit/20m. + - RF: 402 + 402. + - Rate Matching: 402 bit puncturing to 268. Puncturing Level: 4 RU = 88 \* 4 = 352 Bits. A table shows the breakdown: gross 352 bit, - TFCI 16 bit, - TPC 4 bit, - SS 4 bit, - 60 bit, puncturing 268 bit. + - Output: 268 + 268 bits. +- MAC Header Path:** + - Starts with 4 + 96 bits (MAC Header). + - DCCH: 100 + 12. + - Tail bit: 112 + 8. + - Conv. Coding: (112+8)\*3=36. + - Output: 360bit. + - Rate Matching: Puncturing Level: Rate Matching. + - Output: 60 + 60 + 60 + 60 bits. +- Slot Path:** + - Service: 268 + 60 bits. + - 2nd Interleaving: 328 bits. + - TFCI, TPC and Physical Channel: 328 + 16 + 8 bits. + - Physical Channel: 176 + 176 bits. + - Slot: SF=8. Each sub-frame (Sub Frame #1 to #8) contains 84 chp, 144 chp, 4 chp, 80 chp, 84 chp, 144 chp, 4 chp, 80 chp. Labels below indicate TFCI, TPC & SS. + +Figure A.1A: Bit processing flow diagram for 7,68 Mcps TDD Option. The diagram shows the flow of bits from Information and MAC Header through various processing stages including CRC, Tail bit, Conv. Coding, 1st Interleaving, RF, Rate Matching, 2nd Interleaving, TFCI, TPC and Physical Channel mapping to Slots across 8 sub-frames. + +Figure A.1A + +A.2.1.3 7,68 Mcps TDD Option + +Table A.1B + +| Parameter | Value | +|-----------------------------------------------------------------------|-------------| +| Information data rate | 12.2 kbps | +| RU's allocated | 2 RU | +| Midamble | 1024 chips | +| Interleaving | 20 ms | +| Power control | 2 Bit/user | +| TFCI | 16 Bit/user | +| Inband signalling DCCH | 2 kbps | +| Puncturing level at Code rate 1/3 : DCH of the DTCH / DCH of the DCCH | 10% / 0% | + +![Figure A.1B: Bit processing flow diagram for UL reference measurement channel (64 kbps).](3d6d0738981fdd03d003cc653bdfdaae_img.jpg) + +The diagram illustrates the bit processing flow for the UL reference measurement channel (64 kbps) across four radio frames. The process starts with 'Information data' (244 bits) and 'DCCH' (4 bits for MAC-Header, 96 bits for CRC). The flow includes CRC attachment, tail bit attachment, convolutional coding (1/3), 1st interleaving, RF-segmentation, puncturing/ratematching, service multiplexing, 2nd interleaving, TFCI/TPC addition, and slot segmentation. The final output shows four radio frames, each containing 228 chips, a midamble (MA), and power control (PC) bits. + +**DCCH Processing:** + +- Information data: 244 bits +- MAC-Header: 4 bits +- CRC: 96 bits +- MAC-Header + CRC: 100 bits +- Tail bit attachment: 8 bits +- Conv. Coding 1/3: 112 bits +- 1st Interleaving (360): 120 x 3 = 360 bits +- Repetition 0% Rate Matching (360): 90 bits + +**Information Data Processing:** + +- Information data: 244 bits +- CRC attachment: 16 bits +- Tail bit attachment: 8 bits +- Conv. Coding 1/3: [(260 + 8) x 3 = 804 bits] +- 1st Interleaving: 804 bit/20ms +- RF-segmentation: 402 bits +- Puncturing Ratematching: 402 bit punct. to 362 bit puncturing-level: 10% +2 RU → 244 x 2 = 488 Bits available + + +| gross | 488 bit | +|----------|-------------| +| -TFCI | -16 bit * 2 | +| -TPC | -2 bit * 2 | +| -Signal. | -90 bit | +| punc. to | 362 bit | +- Service Multiplex: 362 bits + 90 bits (from DCCH) = 452 bits +- 2nd Interleaving: 452 bits +- TFCI / TPC: 16 bits +- Slot segmentation: 228 chips, MA (8 chips), PC (2 bits), 224 chips + +**Radio Frame Structure:** + +- SF=16 +- Radio Frame #1: 228 chips, MA (8 chips), PC (2 bits), 224 chips +- Radio Frame #2: 228 chips, MA (8 chips), PC (2 bits), 224 chips +- Radio Frame #3: 228 chips, MA (8 chips), PC (2 bits), 224 chips +- Radio Frame #4: 228 chips, MA (8 chips), PC (2 bits), 224 chips + +Figure A.1B: Bit processing flow diagram for UL reference measurement channel (64 kbps). + +Figure A.1B + +## A.2.2 UL reference measurement channel (64 kbps) + +### A.2.2.1 3,84 Mcps TDD option + +Table A.2 + +| Parameter | Value | +|---------------------------------------------------------------------------|----------------------| +| Information data rate | 64 kbps | +| RU's allocated | 1 SF4 + 1 SF16 = 5RU | +| Midamble | 512 chips | +| Interleaving | 20 ms | +| Power control | 2 Bit/user | +| TFCI | 16 Bit/user | +| Inband signalling DCCH | 2 kbps | +| Puncturing level at Code rate : 1/3 DCH of the DTCH / 1/2 DCH of the DCCH | 43.8% / 13.3% | + +![Figure A.2: Data flow diagram for 1,28 Mcps TDD option. It shows the processing of information data and DCCH through various stages including CRC attachment, Turbo coding, Trellis-termination, interleaving, RF-segmentation, puncturing, service multiplexing, and slot segmentation into four radio frames.](c0ef0292328b1602e278f6a0b2ee07e0_img.jpg) + +**Information data** + +1280 1280 + +**CRC attachment** + +1280 16 1280 16 + +**Turbo Coding 1/3** + +[(640 x 2) + 16] x 3 = 3888 [(640 x 2) + 16] x 2 = 3888 + +**Trellis-Termination** + +3888 bit/20ms 12 3888 bit/20ms 12 + +**1st Interleaving** + +3900 bit/20ms 3900 bit/20ms + +**RF-segmentation** + +1950 1950 1950 1950 + +**Puncturing Ratematching** + +1950 bit punct. to 1096 bit puncturing-level: 44% +5 RU → 244x5 = 1220 Bits available + +| | | +|----------|-------------| +| gross | 1220 bit | +| -TFCI | -16 bit * 4 | +| -TPC | 2 bit * 4 | +| -Signal. | -52 bit | +| punc. to | 1096 bit | + +1096 1096 1096 1096 + +**Service Multiplex.** + +1096 52 1096 52 1096 52 1096 52 + +**2nd Interleaving** + +1148 1148 1148 1148 + +**TFCI / TPC** + +1148 16 2 1148 16 2 1148 16 2 1148 16 2 + +**Slot segmentation** + +SF=16 + +122 MA 122 122 MA 122 122 MA 122 122 MA 122 + +SF=4 + +456 8 512 2 8 448 456 8 512 2 8 448 456 8 512 2 8 448 456 8 512 2 8 448 + +Radio Frame #1 Radio Frame #2 Radio Frame #3 Radio Frame #4 + +Figure A.2: Data flow diagram for 1,28 Mcps TDD option. It shows the processing of information data and DCCH through various stages including CRC attachment, Turbo coding, Trellis-termination, interleaving, RF-segmentation, puncturing, service multiplexing, and slot segmentation into four radio frames. + +Figure A.2 + +## A.2.2.2 1,28 Mcps TDD option + +Table A.2A + +| Parameter | Value | +|--------------------------------------------------------------------------|-----------------------| +| Information data rate | 64 kbps | +| RU's allocated | 1TS (1*SF2) = 8RU/5ms | +| Midamble | 144 | +| Interleaving | 20 ms | +| Power control (TPC) | 4 Bit/user/10ms | +| TFCI | 16 Bit/user/10ms | +| Synchronisation Shift (SS) | 4 Bit/user/10ms | +| Inband signalling DCCH | 2.4 kbps | +| Puncturing level at Code rate: 1/3 DCH of the DTCH / 1/2 DCH of the DCCH | 32% / 0 | + +![Diagram of downlink data flow for 7.68 Mcps TDD Option showing processing from Information Data to Slot Segmentation across 8 subframes.](c24f22afc8106a8f9b76c759a1db6891_img.jpg) + +**Information Data**: 1280 bits + +**CRC attachment**: 1280 + 16 bits + +**Turbo Coding 1/3**: $((640 \times 2) + 16) \times 3 = 3888$ + +**Trellis Termination**: 3888bit / 20ms (12 bits added) + +**Interleaving**: 3900bit / 20ms + +**RF-Segmentation**: 1950 bits | 1950 bits + +**Rate Matching**: 1950 bit punctured to 1324 bit. Puncturing Level: 32%. 16 RU = 88 \* 16 = 1408 Bits available. + +| | | +|---------------|----------| +| gross | 1408 bit | +| - TFCI | - 16 bit | +| - TPC | - 4 bit | +| - SS | - 4 bit | +| - Signalling | - 60 bit | +| puncturing to | 1324 bit | + +**MAC-Header**: 4 | 96 | DCCH (12 bits). After coding: 100 | 12. Convolutional Coding 1/2: $((112+8) \times 2) = 240$ bits. Puncturing Level: 0%. + +**Service Multiplexing**: Combines 1324 bits and 60 bits. + +**Interleaving**: 1384 bits + +**TFCI, TPC and SS**: 1384 | 16 | 8 bits + +**Physical Channel Mapping**: 704 bits per segment + +**Slot segmentation** SF=2: 348 | 144 chips | 348 | 144 chips + +Sub Frame #1 Sub Frame #2 Sub Frame #3 Sub Frame #4 Sub Frame #5 Sub Frame #6 Sub Frame #7 Sub Frame #8 + +Diagram of downlink data flow for 7.68 Mcps TDD Option showing processing from Information Data to Slot Segmentation across 8 subframes. + +**Figure A.2A** + +### A.2.2.3 7,68 Mcps TDD Option + +**Table A.2B** + +| Parameter | Value | +|---------------------------------------------------------------------------|----------------------| +| Information data rate | 64 kbps | +| RU’s allocated | 1 SF8 + 1 SF32 = 5RU | +| Midamble | 1024 chips | +| Interleaving | 20 ms | +| Power control | 2 Bit/user | +| TFCI | 16 Bit/user | +| Inband signalling DCCH | 2 kbps | +| Puncturing level at Code rate : 1/3 DCH of the DTCH / 1/2 DCH of the DCCH | 43.8% / 13.3% | + +![Figure A.2B: Data flow diagram showing the processing of information data through various stages including CRC attachment, Turbo Coding, Interleaving, and Slot Segmentation for four radio frames. The diagram is divided into three main sections: Information data, DCCH, and Slot Segmentation. The Information data section shows the flow from 1280 bits of information data through CRC attachment, Turbo Coding (1/3), Trellis-Termination, 1st Interleaving, RF-segmentation, and Puncturing/Ratematching to produce four 1096-bit blocks. These are then multiplexed with 52-bit segments, 2nd Interleaved, and TFCI/TPC added. The DCCH section shows the flow from a 4-bit MAC-Header through CRC attachment, Conv. Coding (1/2), 1st Interleaving, and Puncturing/Rate Matching to produce four 52-bit segments. The Slot Segmentation section shows the final bit blocks for SF=32 and SF=8, which are then mapped to four Radio Frames.](64c76a4fd6b7918cd8a2704de0265e8d_img.jpg) + +**Information Data Processing:** + +- Information data:** 1280 | 1280 +- CRC attachment:** 1280 | 16 | 1280 | 16 +- Turbo Coding 1/3:** $[(640 \times 2) + 16] \times 3 = 3888$ | $[(640 \times 2) + 16] \times 2 = 3888$ +- Trellis-Termination:** 3888 bit/20ms | 12 | 3888 bit/20ms | 12 +- 1st Interleaving:** 3900 bit/20ms | 3900 bit/20ms +- RF-segmentation:** 1950 | 1950 | 1950 | 1950 +- Puncturing Ratematching:** + - 1950 bit punct. to 1096 bit puncturing-level: 44% +5 RU $\rightarrow$ 244x5 = 1220 Bits available + - gross 1220 bit + - TFCI -16 bit \* 4 + - TPC 2 bit \* 4 + - Signal. -52 bit + - punc. to 1096 bit +- Service Multiplex.:** 1096 | 52 | 1096 | 52 | 1096 | 52 | 1096 | 52 +- 2nd Interleaving:** 1148 | 1148 | 1148 | 1148 +- TFCI / TPC:** 1148 | TF CI T PC | 1148 | TF CI T PC | 1148 | TF CI T PC | 1148 | TF CI T PC +- Slot segmentation:** + - SF=32:** 122 | MA | 122 | 122 | MA | 122 | 122 | MA | 122 | 122 | MA | 122 + - SF=8:** 456 | TF CI | MA | T PC | 448 | 456 | TF CI | MA | T PC | 448 | 456 | TF CI | MA | T PC | 448 | 456 | TF CI | MA | T PC | 448 + - chips: 8 1024 2 8 | 8 1024 2 8 | 8 1024 2 8 | 8 1024 2 8 +- Radio Frames:** Radio Frame #1 | Radio Frame #2 | Radio Frame #3 | Radio Frame #4 + +**DCCH Processing:** + +- DCCH:** 4 | 96 +- MAC-Header:** 100 | 12 +- CRC:** 112 | 8 +- Tail:** 120 x 2 = 240 +- Conv. Coding 1/2:** 1st Interleaving (240) +- Puncturing 13% Rate Matching (208):** 52 | 52 | 52 | 52 + +Figure A.2B: Data flow diagram showing the processing of information data through various stages including CRC attachment, Turbo Coding, Interleaving, and Slot Segmentation for four radio frames. The diagram is divided into three main sections: Information data, DCCH, and Slot Segmentation. The Information data section shows the flow from 1280 bits of information data through CRC attachment, Turbo Coding (1/3), Trellis-Termination, 1st Interleaving, RF-segmentation, and Puncturing/Ratematching to produce four 1096-bit blocks. These are then multiplexed with 52-bit segments, 2nd Interleaved, and TFCI/TPC added. The DCCH section shows the flow from a 4-bit MAC-Header through CRC attachment, Conv. Coding (1/2), 1st Interleaving, and Puncturing/Rate Matching to produce four 52-bit segments. The Slot Segmentation section shows the final bit blocks for SF=32 and SF=8, which are then mapped to four Radio Frames. + +Figure A.2B + +## A.2.3 UL reference measurement channel (144 kbps) + +### A.2.3.1 3,84 Mcps TDD option + +Table A.3 + +| Parameter | Value | +|---------------------------------------------------------------------------|----------------------| +| Information data rate | 144 kbps | +| RU's allocated | 1 SF2 + 1 SF16 = 9RU | +| Midamble | 256 chips | +| Interleaving | 20 ms | +| Power control | 2 Bit/user | +| TFCI | 16 Bit/user | +| Inband signalling DCCH | 2 kbps | +| Puncturing level at Code rate : 1/3 DCH of the DTCH / 1/2 DCH of the DCCH | 47.3% / 20% | + +![Figure A.3: Data flow diagram for 1,28 Mcps TDD option. It shows the processing of information data and DCCH through various stages including CRC attachment, Turbo coding, Trellis-termination, interleaving, RF-segmentation, puncturing, service multiplexing, and slot segmentation into four radio frames.](9f5f9afcedaa0d9b7991976f5000865c_img.jpg) + +**Information data** + +2880      2880 + +**CRC attachment** + +2880 | 16      2880 | 16 + +**Turbo Coding 1/3** + +[(1440 x 2) + 16] x 3 = 8688      [(1440 x 2) + 16] x 3 = 8688 + +**Trellis-Termination** + +8688 bit/20ms | 12      8688 bit/20ms | 12 + +**1st Interleaving** + +8700 bit/20ms      8700 bit/20ms + +**RF-segmentation** + +4350      4350      4350      4350 + +**Puncturing Ratematching** + +4350 bit punct. to 2292 bit puncturing-level: 47% +9 RU → 276x9 = 2484 Bits available + +| | | +|----------|-------------| +| gross | 2484 bit | +| -TFCI | -16 bit * 8 | +| -TPC | -2 bit * 8 | +| -Signal. | -48 bit | +| punc. to | 2292 bit | + +4350 bit punct. to 2292 bit puncturing-level: 47% +9 RU → 276x9 = 2484 Bits available + +| | | +|----------|-------------| +| gross | 2484 bit | +| -TFCI | -16 bit * 8 | +| -TPC | -2 bit * 8 | +| -Signal. | -48 bit | +| punc. to | 2292 bit | + +**DCCH** + +4 | 96 + +**MAC-Header** + +100 | 12 + +**CRC** + +112 | 8 + +**Tail** + +120 x 2 = 240 + +**Conv. Coding 1/2** + +**1st Interleaving (240)** + +**Puncturing 20% Rate Matching (192)** + +2292      2292      2292      2292 + +48      48      48      48 + +**Service Multiplex.** + +2292 | 48      2292 | 48      2292 | 48      2292 | 48 + +**2nd Interleaving** + +2340      2340      2340      2340 + +**TFCI / TPC** + +2340 | TF CI T PC | 16 2      2340 | TF CI T PC | 16 2      2340 | TF CI T PC | 16 2      2340 | TF CI T PC | 16 2 + +**Slot segmentation** + +**SF=16** + +138 | MA | 138      138 | MA | 138      138 | MA | 138      138 | MA | 138 + +**SF=2** + +1040 | TF CI | MA | T PC | TF CI | 1024 +8      256      2      8 +chips      8      256      2      8 +chips      8      256      2      8 +chips      8      256      2      8 +chips + +Radio Frame #1      Radio Frame #2      Radio Frame #3      Radio Frame #4 + +Figure A.3: Data flow diagram for 1,28 Mcps TDD option. It shows the processing of information data and DCCH through various stages including CRC attachment, Turbo coding, Trellis-termination, interleaving, RF-segmentation, puncturing, service multiplexing, and slot segmentation into four radio frames. + +Figure A.3 + +## A.2.3.2 1,28 Mcps TDD option + +Table A.3A + +| Parameter | Value | +|--------------------------------------------------------------------------|------------------------| +| Information data rate | 144 kbps | +| RU's allocated | 2TS (1*SF2) = 16RU/5ms | +| Midamble | 144 | +| Interleaving | 20 ms | +| Power control (TPC) | 8 Bit/user/10ms | +| TFCI | 32 Bit/user/10ms | +| Synchronisation Shift (SS) | 8 Bit/user/10ms | +| Inband signalling DCCH | 2.4 kbps | +| Puncturing level at Code rate: 1/3 DCH of the DTCH / 1/2 DCH of the DCCH | 38% / 7% | + +![Figure A.3A: Data flow diagram for 7,68 Mcps TDD Option. It illustrates the processing chain for Information Data (2880 bits) and DCCH (96 bits). Stages include CRC attachment, Turbo Coding 1/3, Trellis Termination, 1st Interleaving, RF-Segmentation, and Rate Matching. The Rate Matching stage for Information Data shows a puncturing level of 38% to reach 2712 bits, with a breakdown of TFCI, TPC, SS, and Signalling bits. The DCCH path includes MAC-Header, CRC, Convolutional Coding 1/2, and Rate Matching with 7% puncturing. Both paths merge at Service Multiplexing, followed by 2nd Interleaving, TFCI/TPC/SS insertion, Physical Channel Mapping, and finally Slot Segmentation into 8 sub-frames using SF=2 and 2 timeslots.](993921f0d5f99fb48933465306644535_img.jpg) + +Information Data: 2880 | 2880 + +CRC attachement: 2880 | 16 | 2880 | 16 + +Turbo Coding 1/3: $[(1440 \cdot 2) + 16] \cdot 3 = 8688$ | $[(1440 \cdot 2) + 16] \cdot 3 = 8688$ + +Trellis Termination: 8688bit / 20ms | 12 | 8688bit / 20ms | 12 + +1st Interleaving: 8700bit / 20ms | 8700bit / 20ms + +RF-Segmentation: 4350 | 4350 | 4350 | 4350 + +Rate Matching: +4350 bit punctured to 2712 bit +Puncturing Level: 38% + $32 \text{ RU} = 88 \cdot 32 = 2816 \text{ Bits available}$ + +| | | +|---------------|----------| +| gross | 2816 bit | +| - TFCI | - 32 bit | +| - TPC | - 8 bit | +| - SS | - 8 bit | +| - Signalling | - 56 bit | +| puncturing to | 2712 bit | + +MAC-Header: 4 | 96 | DCCH + +CRC: 100 | 12 + +112 | 8 + +$(112+8) \cdot 2 = 240$ +Convolutional Coding 1/2 + +240bit + +Puncturing Level: 7% +Rate Matching (224) + +Service Multiplexing: 2712 | 56 | 2712 | 56 | 2712 | 56 | 2712 | 56 + +2nd Interleaving: 2768 | 2768 | 2768 | 2768 + +TFCI, TPC and SS: 2768 | 32 | 16 | 2768 | 32 | 16 | 2768 | 32 | 16 | 2768 | 32 | 16 + +Physical Channel Mapping: 1408 | 1408 | 1408 | 1408 | 1408 | 1408 | 1408 | 1408 + +Slot segmentation: SF=2, 2 Timeslots + +Sub Frame #1 Sub Frame #2 Sub Frame #3 Sub Frame #4 Sub Frame #5 Sub Frame #6 Sub Frame #7 Sub Frame #8 + +Figure A.3A: Data flow diagram for 7,68 Mcps TDD Option. It illustrates the processing chain for Information Data (2880 bits) and DCCH (96 bits). Stages include CRC attachment, Turbo Coding 1/3, Trellis Termination, 1st Interleaving, RF-Segmentation, and Rate Matching. The Rate Matching stage for Information Data shows a puncturing level of 38% to reach 2712 bits, with a breakdown of TFCI, TPC, SS, and Signalling bits. The DCCH path includes MAC-Header, CRC, Convolutional Coding 1/2, and Rate Matching with 7% puncturing. Both paths merge at Service Multiplexing, followed by 2nd Interleaving, TFCI/TPC/SS insertion, Physical Channel Mapping, and finally Slot Segmentation into 8 sub-frames using SF=2 and 2 timeslots. + +**Figure A.3A** + +### A.2.3.3 7,68 Mcps TDD Option + +**Table A.3B** + +| Parameter | Value | +|---------------------------------------------------------------------------|----------------------| +| Information data rate | 144 kbps | +| RU's allocated | 1 SF4 + 1 SF32 = 9RU | +| Midamble | 512 chips | +| Interleaving | 20 ms | +| Power control | 2 Bit/user | +| TFCI | 16 Bit/user | +| Inband signalling DCCH | 2 kbps | +| Puncturing level at Code rate : 1/3 DCH of the DTCH / 1/2 DCH of the DCCH | 47.3% / 20% | + +![Figure A.3B: Data flow diagram showing the processing of information data through various stages including CRC attachment, Turbo Coding, Interleaving, and Slot Segmentation for four radio frames. The diagram is divided into three main sections: Information data, DCCH, and Slot segmentation. The Information data section shows the processing of 2880 bits through CRC attachment, Turbo Coding 1/3, Trellis-Termination, 1st Interleaving, RF-segmentation, and Puncturing Ratemaching to produce four 2292-bit blocks. These are then Service Multiplexed with 48-bit DCCH blocks, 2nd Interleaved to 2340 bits, and TFCI/TPC added. Finally, Slot Segmentation is performed for SF=32 and SF=4, resulting in four Radio Frames. The DCCH section shows the processing of 4 bits of MAC-Header and 96 bits of data through MAC-Header, CRC, and Conv. Coding 1/2 to produce four 120-bit blocks, which are then 1st Interleaved and Puncturing 20% Rate Matching is applied to produce four 48-bit blocks. The Slot Segmentation section shows the mapping of bits to slots for SF=32 and SF=4.](fe82ce00eaac699b60a35ccb558e7851_img.jpg) + +**Information data** + +2880      2880 + +**CRC attachment** + +2880 | 16      2880 | 16 + +**Turbo Coding 1/3** + +[(1440 x 2) + 16] x 3 = 8688      [(1440 x 2) + 16] x 3 = 8688 + +**Trellis-Termination** + +8688 bit/20ms | 12      8688 bit/20ms | 12 + +**1st Interleaving** + +8700 bit/20ms      8700 bit/20ms + +**RF-segmentation** + +4350      4350      4350      4350 + +**Puncturing Ratemaching** + +4350 bit punct. to 2292 bit puncturing-level: 47% +9 RU → 276x9 = 2484 Bits available + +| | | +|-----------------|-----------------| +| gross | 2484 bit | +| -TFCI | -16 bit * 8 | +| -TPC | -2 bit * 8 | +| -Signal. | -48 bit | +| punc. to | 2292 bit | + +2292      2292      2292      2292 + +**Service Multiplex.** + +2292 | 48      2292 | 48      2292 | 48      2292 | 48 + +**2nd Interleaving** + +2340      2340      2340      2340 + +**TFCI / TPC** + +2340 | TF CI T PC      2340 | TF CI T PC      2340 | TF CI T PC      2340 | TF CI T PC + +16 2      16 2      16 2      16 2 + +**Slot segmentation** + +**SF=32** + +138 | MA | 138      138 | MA | 138      138 | MA | 138      138 | MA | 138 + +**SF=4** + +1040 | TF CI MA T PC | 1024      1040 | TF CI MA T PC | 1024      1040 | TF CI MA T PC | 1024      1040 | TF CI MA T PC | 1024 + +8 512 2 8 chips      8 512 2 8 chips      8 512 2 8 chips      8 512 2 8 chips + +Radio Frame #1      Radio Frame #2      Radio Frame #3      Radio Frame #4 + +**DCCH** + +4 | 96 + +**MAC-Header** + +100 | 12 + +**CRC** + +112 | 8 + +**Tail** + +120 x 2 = 240 + +**Conv. Coding 1/2** + +**1st Interleaving (240)** + +**Puncturing 20% Rate Matching (192)** + +48 | 48 | 48 | 48 + +Figure A.3B: Data flow diagram showing the processing of information data through various stages including CRC attachment, Turbo Coding, Interleaving, and Slot Segmentation for four radio frames. The diagram is divided into three main sections: Information data, DCCH, and Slot segmentation. The Information data section shows the processing of 2880 bits through CRC attachment, Turbo Coding 1/3, Trellis-Termination, 1st Interleaving, RF-segmentation, and Puncturing Ratemaching to produce four 2292-bit blocks. These are then Service Multiplexed with 48-bit DCCH blocks, 2nd Interleaved to 2340 bits, and TFCI/TPC added. Finally, Slot Segmentation is performed for SF=32 and SF=4, resulting in four Radio Frames. The DCCH section shows the processing of 4 bits of MAC-Header and 96 bits of data through MAC-Header, CRC, and Conv. Coding 1/2 to produce four 120-bit blocks, which are then 1st Interleaved and Puncturing 20% Rate Matching is applied to produce four 48-bit blocks. The Slot Segmentation section shows the mapping of bits to slots for SF=32 and SF=4. + +Figure A.3B + +## A.2.4 UL reference measurement channel (384 kbps) + +### A.2.4.1 3,84 Mcps TDD option + +Table A.4 + +| Parameter | Value | +|---------------------------------------------------------------------------|--------------| +| Information data rate | 384 kbps | +| RU's allocated | 8*3TS = 24RU | +| Midamble | 256 chips | +| Interleaving | 20 ms | +| Power control | 2 Bit/user | +| TFCI | 16 Bit/user | +| Inband signalling DCCH | 2 kbps | +| Puncturing level at Code rate : 1/3 DCH of the DTCH / 1/2 DCH of the DCCH | 44% / 15.3% | + +![Figure A.4: Block diagram of the UL reference measurement channel processing flow for 384 kbps at 3.84 Mcps TDD option. The diagram shows the processing of information data and DCCH through various stages including CRC attachment, Turbo coding, Trellis termination, interleaving, RF-segmentation, puncturing, service multiplexing, and slot segmentation across four radio frames.](4f407c97df6e5ee98fdb248ada82de59_img.jpg) + +The diagram illustrates the processing flow for the UL reference measurement channel (384 kbps) at 3.84 Mcps TDD option. It is divided into two main sections: Information data and DCCH. + +**Information Data Processing:** + +- Information data:** Four blocks of 3840 bits each. +- CRC attachment:** Each 3840-bit block has a 16-bit CRC attached, resulting in 3856 bits per block. +- Turbo Coding 1/3:** Each 3856-bit block is Turbo coded at a rate of 1/3, resulting in $[(3840+16) \times 2] \times 3 = 23136$ bits per block. +- Trellis-Termination:** Each 23136-bit block is terminated with 24 bits, resulting in 23160 bits per block. +- 1st Interleaving:** Each 23160-bit block is interleaved, resulting in 23160 bits per block. +- RF-segmentation:** Each 23160-bit block is segmented into two 11580-bit blocks. +- Puncturing Ratematching:** Each 11580-bit block is punctured to 6429 bits at a puncturing level of 44%. The available bits (6624) are used for TFCI (16 bits \* 8 = 128 bits), TPC (2 bits \* 8 = 16 bits), and Signal (-51 bits), leaving 6429 bits for data. +- Service Multiplex:** Each 6429-bit block is multiplexed with 51 bits of DCCH data, resulting in 6480 bits per block. +- 2nd Interleaving:** Each 6480-bit block is interleaved, resulting in 6480 bits per block. +- TFCI / TPC:** Each 6480-bit block is further segmented into 16 TFCI bits and 2 TPC bits, resulting in 6480 bits per block. +- Slot segmentation:** Each 6480-bit block is segmented into two 1024-bit blocks, with a 16-bit MAC header and 256 chips of midamble. This results in 1040 bits per slot. +- SF=2 3 Timeslots:** Each 1040-bit block is mapped to three timeslots (TS #1..#3) within a radio frame. +- Radio Frame #1 to #4:** The processed data is distributed across four radio frames. + +**DCCH Processing:** + +- DCCH:** 4 bits of MAC-Header and 96 bits of data. +- CRC:** A 12-bit CRC is attached to the 100-bit block, resulting in 112 bits. +- Tail:** 8 bits of tail are added, resulting in 120 bits. +- Conv. Coding 1/2:** The 120 bits are convolutedly coded at a rate of 1/2, resulting in 240 bits. +- 1st Interleaving (240):** The 240 bits are interleaved. +- Puncturing 15% Rate Matching (204):** The 240 bits are punctured to 204 bits at a puncturing level of 15.3%. +- Service Multiplex:** The 204 bits are multiplexed with the 6429-bit information data blocks, resulting in 6480 bits per block (6429 bits of information data + 51 bits of DCCH data). + +Figure A.4: Block diagram of the UL reference measurement channel processing flow for 384 kbps at 3.84 Mcps TDD option. The diagram shows the processing of information data and DCCH through various stages including CRC attachment, Turbo coding, Trellis termination, interleaving, RF-segmentation, puncturing, service multiplexing, and slot segmentation across four radio frames. + +Figure A.4 + +## A.2.4.2 1,28 Mcps TDD option + +Table A.4A + +| Parameter | Value | +|--------------------------------------------------------------------------|---------------------------------| +| Information data rate | 384 kbps | +| RU's allocated | 4TS (1*SF2 + 1*SF16) = 36RU/5ms | +| Midamble | 144 | +| Interleaving | 20 ms | +| Power control (TPC) | 16 Bit/user/10ms | +| TFCI | 64 Bit/user/10ms | +| Synchronisation Shift (SS) | 16 Bit/user/10ms | +| Inband signalling DCCH | 2.4 kbps | +| Puncturing level at Code rate: 1/3 DCH of the DTCH / 1/2 DCH of the DCCH | 47% / 12% | + +![Figure A.4A: Data flow diagram for 1,28 Mcps TDD option showing processing steps from Information Data to Slot Segmentation across 8 sub-frames.](265c8762616c43e9c49083d5546b9738_img.jpg) + +The diagram illustrates the data processing flow for the 1,28 Mcps TDD option across 8 sub-frames. The main data path (DTCH) starts with 3840 bits of Information Data, followed by CRC attachment (16 bits), Turbo Coding (1/3), Trellis Termination (24 bits), 1st Interleaving, RF-Segmentation (11580 bits), and Rate Matching (punctured to 6187 bits). The Rate Matching stage includes a table for gross and punctured bits: + +| gross | 6336 bit | +|---------------|----------| +| - TFCI | - 64 bit | +| - TPC | - 16 bit | +| - SS | - 16 bit | +| - Signalling | 53 | +| puncturing to | 6187 bit | + +For the Inband Signalling DCCH, the flow starts with MAC-Header (4 + 96 bits), DCCH (100 + 12 bits), and Convolutional Coding (1/2) (112 + 8 bits), resulting in 240 bits. Rate Matching for DCCH uses a Puncturing Level of 12% (165 bits), resulting in 4 bits of 53-bit segments. Service Multiplexing combines the 6187 bits from DTCH and 53 bits from DCCH into 6240 bits, followed by 2nd Interleaving, TFCI, TPC and SS (64 + 32 bits), and Physical Channel Mapping (3168 bits). Slot Segmentation for SF=16 (4 Timeslots) and SF=2 (4 Timeslots) shows the mapping to chips (144 chips per timeslot). + +Figure A.4A: Data flow diagram for 1,28 Mcps TDD option showing processing steps from Information Data to Slot Segmentation across 8 sub-frames. + +Figure A.4A + +### A.2.4.3 7,68 Mcps TDD Option + +Table A.4B + +| Parameter | Value | +|---------------------------------------------------------------------------|---------------| +| Information data rate | 384 kbps | +| RU's allocated | 8*3TS = 24RU | +| Midamble | 512 chips | +| Interleaving | 20 ms | +| Power control | 2 Bit/user | +| TFCI | 16 Bit/user | +| Inband signalling DCCH | 2 kbps | +| Puncturing level at Code rate : 1/3 DCH of the DTCH / 1/2 DCH of the DCCH | 43.4% / 15.3% | + +![Figure A.4B: Data flow diagram for 7,68 Mcps TDD Option. It shows the processing of information data and DCCH through various stages including CRC attachment, Turbo coding, interleaving, and slot segmentation across four radio frames.](aa23dbbc50355aed4783a5698f0ac691_img.jpg) + +The diagram illustrates the data flow for the 7,68 Mcps TDD Option, showing the processing of information data and DCCH through various stages. + +**Information Data Processing:** + +- Information data:** Four blocks of 3840 bits each. +- CRC attachment:** Each 3840-bit block has a 16-bit CRC attached, resulting in 3856-bit blocks. +- Turbo Coding 1/3:** Each 3856-bit block is turbo-coded with a rate of 1/3, resulting in $[(3840+16) \times 2] \times 3 = 23136$ bits per block. +- Trellis-Termination:** Each 23136-bit block is terminated with 24 bits, resulting in 23160 bits per block. +- 1st Interleaving:** Each 23160-bit block is interleaved, resulting in 23160 bits per block. +- RF-segmentation:** Each 23160-bit block is segmented into two 11580-bit blocks. +- Puncturing Ratemaching:** Each 11580-bit block is punctured to 6429 bits at a puncturing level of 44%. This results in 6624 bits available for signaling: + + +| gross | 6624 bit | +|----------|-------------| +| -TFCI | -16 bit * 8 | +| -TPC | -2 bit * 8 | +| -Signal. | -51 bit | +| punc. to | 6429 bit | +- Service Multiplex.:** Each 6429-bit block is multiplexed with 51 bits of signaling, resulting in 6480-bit blocks. +- 2nd Interleaving:** Each 6480-bit block is interleaved, resulting in 6480 bits per block. +- TFCI / TPC:** Each 6480-bit block is further segmented into TFCI (16 bits) and TPC (2 bits) components. +- Slot segmentation:** The data is segmented into slots for three timeslots (SF=4). Each slot contains 1040 bits, a TFCI/TPC component, a Midamble (MA), and 1024 bits. The slot structure is: 8 chips, 512 chips, 2 bits, 8 bits, followed by the data bits (1040, MA, 1024). +- Radio Frames:** The slots are organized into four radio frames (Radio Frame #1 to #4). + +**DCCH Processing:** + +- DCCH:** 4 bits of MAC-Header and 96 bits of data. +- CRC:** A 12-bit CRC is attached to the 100-bit block, resulting in 112 bits. +- Tail:** 8 tail bits are added, resulting in 120 bits. +- Conv. Coding 1/2:** The 120 bits are convolutedly coded with a rate of 1/2, resulting in 240 bits. +- 1st Interleaving (240):** The 240 bits are interleaved. +- Puncturing 15% Rate Matching (204):** The 240 bits are punctured to 204 bits at a puncturing level of 15%. +- Signaling Bits:** The 204 bits are further segmented into four 51-bit blocks. + +Figure A.4B: Data flow diagram for 7,68 Mcps TDD Option. It shows the processing of information data and DCCH through various stages including CRC attachment, Turbo coding, interleaving, and slot segmentation across four radio frames. + +Figure A.4B + +## A.2.5 RACH reference measurement channel + +### A.2.5.1 3,84 Mcps TDD option + +Table A.5 + +| Parameter | Value | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------| +| Information data rate e.g. 2 TBs ( $B_{RACH}=2$ ):
SF16:
0% puncturing rate at CR=1/2
10% puncturing rate at CR=1/2
$N_{RACH} = \frac{\frac{232 + N_{RM}}{2} - 8}{B_{RACH}}$
SF8:
0% puncturing rate at CR=1/2
10% puncturing rate at CR=1/2
$N_{RACH} = \frac{\frac{464 + N_{RM}}{2} - 16}{B_{RACH}}$ | 46 bits per frame and TB
53 bits per frame and TB

96 bits per frame and TB
109 bits per frame and TB | +| RU's allocated | 1 RU | +| Midamble | 512 chips | +| Power control | 0 bit | +| TFCI | 0 bit | + +$N_{RACH}$ = number of bits per TB + +$B_{RACH}$ = number of TBs + +#### A.2.5.1.1 RACH mapped to 1 code SF16 + +![Diagram illustrating the mapping of RACH data to a radio frame for SF=16. The diagram shows the flow from information data through CRC, tail bits, convolutional coding, puncturing, interleaving, and slot segmentation to the final radio frame structure.](8e097ecef190600bbde2721e0f979b79_img.jpg) + +The diagram illustrates the mapping of RACH data to a radio frame for SF=16. It shows the following stages: + +- Information data:** Divided into $N_{RACH}$ bits for each of the $B_{RACH}$ transport blocks (TBs). +- CRC attachment:** An 8-bit CRC is added to each TB, resulting in $N_{RACH} + 8$ bits per TB. +- Tail bit attachment:** Tail bits are added, resulting in $(N_{RACH} + 8) \times B_{RACH}$ bits. +- Convolutional Coding 1/2:** The data is encoded with a rate of 1/2, resulting in $[(N_{RACH} + 8) \times B_{RACH} + 8] \times 2$ bits. +- Puncturing Ratematching:** Puncturing is applied to match the rate, resulting in $[(N_{RACH} + 8) \times B_{RACH} + 8] \times 2 - N_{RM} = 232$ bits. +- 2nd Interleaving:** The bits are interleaved, resulting in 232 bits. +- Slot segmentation:** The bits are segmented into slots. +- Radio Frame #1:** The final frame structure for SF=16 consists of 122 data bits, a 512-chip Midamble (MA), and 110 data bits. + +Diagram illustrating the mapping of RACH data to a radio frame for SF=16. The diagram shows the flow from information data through CRC, tail bits, convolutional coding, puncturing, interleaving, and slot segmentation to the final radio frame structure. + +Figure A.5 + +## A.2.5.1.2 RACH mapped to 1 code SF8 + +![Diagram of RACH mapping to 1 code SF8 showing bit processing steps from information data to slot segmentation.](43b05bd1b6ee31fba18d3eb683903504_img.jpg) + +The diagram illustrates the bit processing flow for RACH mapping to 1 code SF8. It is organized into several horizontal sections representing different processing stages: + +- Information data:** Shows a sequence of blocks labeled $N_{RACH}$ for TB #1 and TB # $B_{RACH}$ , with an ellipsis between them. +- CRC attachment:** Each $N_{RACH}$ block is followed by a 16-bit CRC block. +- Tail bit attachment:** Each CRC-attached block is followed by 8 tail bits. The total length for one TB is $(N_{RACH}+16) \times B_{RACH} + 8$ . +- Convolutional Coding 1/2:** The tail-bit-attached blocks are then coded, resulting in a length of $[(N_{RACH}+16) \times B_{RACH} + 8] \times 2$ . +- Puncturing Ratematching:** Bits are punctured to achieve a target rate, resulting in $[(N_{RACH}+16) \times B_{RACH} + 8] \times 2 - N_{RM} = 464$ bits. +- 2nd Interleaving:** The 464 bits are then interleaved. +- Slot segmentation:** The interleaved bits are segmented into slots. For SF=16, each slot contains 244 bits, a 512-chip Midamble (MA), and 220 bits, totaling 464 bits per slot. This is shown for Radio Frame #1. + +Diagram of RACH mapping to 1 code SF8 showing bit processing steps from information data to slot segmentation. + +Figure A.6 + +## A.2.5.2 1,28 Mcps TDD option + +Table A5.A + +| Parameter | Value | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Information data rate:
$88 * \frac{16}{SF} \left( \frac{N_{RM}}{100} + 1 \right) - 8$ $N_{RACH} = \frac{2}{B_{RACH}} - 16$ SF16 (RU's allocated:1):
0% puncturing rate at CR=1/2
~10% puncturing rate at CR=1/2

SF8 (RU's allocated:2):
0% puncturing rate at CR=1/2
~10% puncturing rate at CR=1/2

SF4 (RU's allocated:4):
0% puncturing rate at CR=1/2
~10% puncturing rate at CR=1/2 | Transport Block Set Size=1
CRC length = 16
Tail Bits = 8

20 bits per frame and TB
24 bits per frame and TB

64 bits per frame and TB
73 bits per frame and TB

152 bits per frame and TB
170 bits per frame and TB | +| TTI | 5msec | +| Midamble | 144 chips | +| Power control | 0 bit | +| TFCI | 0 bit | + + $N_{RACH}$ = number of bits per TB $B_{RACH}$ = number of TBs $N_{RM}$ = puncturing rate + +A.2.5.2.1 RACH mapped to 1 code SF16 + +![Figure A.5A: RACH mapping to 1 code SF16. The diagram shows the processing steps for a RACH preamble. It starts with Information data (N_RACH bits) across #1 to #B_RACH blocks. CRC attachment adds 16 bits. Tail bit attachment adds 8 bits. Convolutional Coding 1/2 doubles the bits. Puncturing/Ratematching results in 88 bits. 2nd Interleaving keeps it at 88 bits. Slot segmentation for SF=16 results in 44 bits, MA (144 chips), and 44 bits, all within a 5msec Radio Subframe #1.](f82e45705e7d3f028c734e7278ef154e_img.jpg) + +Figure A.5A illustrates the RACH mapping process for 1 code SF16. The diagram shows the following processing steps: + +- Information data:** #1 to #BRACH blocks, each containing NRACH bits. +- CRC attachment:** #1 to #BRACH blocks, each containing NRACH + 16 bits. +- Tail bit attachment:** (NRACH + 16) × BRACH + 8 bits. +- Convolutional Coding 1/2:** [(NRACH + 16) × BRACH + 8] × 2 bits. +- Puncturing/Ratematching:** [(NRACH + 16) × BRACH + 8] × 2 - NRM = 88 bits. +- 2nd Interleaving:** 88 bits. +- Slot segmentation:** For SF=16, the 88 bits are mapped to 44 bits, followed by MA (144 chips), and then 44 bits, all within a 5msec Radio Subframe #1. + +Figure A.5A: RACH mapping to 1 code SF16. The diagram shows the processing steps for a RACH preamble. It starts with Information data (N\_RACH bits) across #1 to #B\_RACH blocks. CRC attachment adds 16 bits. Tail bit attachment adds 8 bits. Convolutional Coding 1/2 doubles the bits. Puncturing/Ratematching results in 88 bits. 2nd Interleaving keeps it at 88 bits. Slot segmentation for SF=16 results in 44 bits, MA (144 chips), and 44 bits, all within a 5msec Radio Subframe #1. + +Figure A.5A + +A.2.5.2.2 RACH mapped to 1 code SF8 + +![Figure A.6A: RACH mapping to 1 code SF8. The diagram shows the processing steps for a RACH preamble. It starts with Information data (N_RACH bits) across #1 to #B_RACH blocks. CRC attachment adds 16 bits. Tail bit attachment adds 8 bits. Convolutional Coding 1/2 doubles the bits. Puncturing/Ratematching results in 16 bits. 2nd Interleaving keeps it at 16 bits. Slot segmentation for SF8 results in 88 bits, MA (144 chips), and 88 bits, all within a 5msec Radio Subframe #1.](409e3ccf9694772191dc84c49f3f7afb_img.jpg) + +Figure A.6A illustrates the RACH mapping process for 1 code SF8. The diagram shows the following processing steps: + +- Information data:** #1 to #BRACH blocks, each containing NRACH bits. +- CRC attachment:** #1 to #BRACH blocks, each containing NRACH + 16 bits. +- Tail bit attachment:** (NRACH + 16) × BRACH + 8 bits. +- Convolutional Coding 1/2:** [(NRACH + 16) × BRACH + 8] × 2 bits. +- Puncturing/Ratematching:** [(NRACH + 16) × BRACH + 8] × 2 - NRM = 16 bits. +- 2nd Interleaving:** 16 bits. +- Slot segmentation:** For SF8, the 16 bits are mapped to 88 bits, followed by MA (144 chips), and then 88 bits, all within a 5msec Radio Subframe #1. + +Figure A.6A: RACH mapping to 1 code SF8. The diagram shows the processing steps for a RACH preamble. It starts with Information data (N\_RACH bits) across #1 to #B\_RACH blocks. CRC attachment adds 16 bits. Tail bit attachment adds 8 bits. Convolutional Coding 1/2 doubles the bits. Puncturing/Ratematching results in 16 bits. 2nd Interleaving keeps it at 16 bits. Slot segmentation for SF8 results in 88 bits, MA (144 chips), and 88 bits, all within a 5msec Radio Subframe #1. + +Figure A.6A + +## A.2.5.2.3 RACH mapped to 1 code SF4 + +Figure A.7 + +## A.2.5.3 7,68 Mcps TDD option + +Table A5.B + +| Parameter | Value | +|-------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------| +| Information data rate e.g. 2 TBs ( $B_{RACH}=2$ ):
SF32:
0% puncturing rate at CR=1/2
10% puncturing rate at CR=1/2 | 46 bits per frame and TB
53 bits per frame and TB | +| SF16:
0% puncturing rate at CR=1/2
10% puncturing rate at CR=1/2 | 96 bits per frame and TB
109 bits per frame and TB | +| RU's allocated | 1 RU for SF32, 2 RUs for SF16 | +| Midamble | 1024 chips | +| Power control | 0 bit | +| TFCI | 0 bit | + +$N_{RACH}$ = number of bits per TB + +$B_{RACH}$ = number of TBs + +## A.2.5.3.1 RACH mapped to 1 code SF16 + +![Diagram illustrating the RACH mapping process for SF16. It shows the flow from Information data through CRC attachment, Tail bit attachment, Convolutional Coding 1/2, Puncturing Ratemaching, 2nd Interleaving, and Slot segmentation to form Radio Frame #1.](1c1fa3b79033665761d99885900218bf_img.jpg) + +The diagram illustrates the RACH mapping process for SF16. It shows the flow of data through various processing stages: + +- Information data:** The initial data is divided into $B_{RACH}$ transport blocks (TBs). The first TB has $N_{RACH}$ bits, and the last TB also has $N_{RACH}$ bits. +- CRC attachment:** A 16-bit CRC is attached to each TB, resulting in $N_{RACH} + 16$ bits per TB. +- Tail bit attachment:** Two tail bits are added to each TB, resulting in $(N_{RACH} + 16) \times B_{RACH} + 8$ bits. +- Convolutional Coding 1/2:** The data is then convolutedly coded with a rate of 1/2, resulting in $[(N_{RACH} + 16) \times B_{RACH} + 8] \times 2$ bits. +- Puncturing Ratemaching:** Puncturing is applied to achieve a target rate, resulting in $[(N_{RACH} + 16) \times B_{RACH} + 8] \times 2 - N_{RM} = 464$ bits. +- 2nd Interleaving:** The bits are then interleaved, resulting in 464 bits. +- Slot segmentation:** The bits are segmented into slots. For SF=16, each slot contains 244 data bits, 1024 midamble (MA) chips, and 220 tail bits. +- Radio Frame #1:** The segmented slots form the final Radio Frame #1. + +Diagram illustrating the RACH mapping process for SF16. It shows the flow from Information data through CRC attachment, Tail bit attachment, Convolutional Coding 1/2, Puncturing Ratemaching, 2nd Interleaving, and Slot segmentation to form Radio Frame #1. + +Figure A.8 + +### A.2.5.3.2 RACH mapped to 1 code SF32 + +![Diagram illustrating the mapping of RACH to 1 code SF32. It shows the flow from Information data through CRC attachment, Tail bit attachment, Convolutional Coding 1/2, Puncturing Ratemaching, 2nd Interleaving, and Slot segmentation to form a Radio Frame #1 with SF=32.](b6bb85a3062dcabdd98c757aec4413b2_img.jpg) + +The diagram illustrates the mapping of RACH to 1 code SF32. It shows the flow from Information data through various processing steps to form a Radio Frame #1. + +- Information data:** Divided into blocks #1 and #BRACH, each containing $N_{RACH}$ bits. +- CRC attachment:** An 8-bit CRC is attached to each block, resulting in $N_{RACH} + 8$ bits per block. +- Tail bit attachment:** Two tail bits are added to each block, resulting in $(N_{RACH} + 8) \times B_{RACH} + 8$ bits per block. +- Convolutional Coding 1/2:** The bits are encoded at a rate of 1/2, resulting in $[(N_{RACH} + 8) \times B_{RACH} + 8] \times 2$ bits. +- Puncturing Ratemaching:** The encoded bits are punctured and rate-matched to $[(N_{RACH} + 8) \times B_{RACH} + 8] \times 2 - N_{RM} = 232$ bits. +- 2nd Interleaving:** The 232 bits are interleaved. +- Slot segmentation:** The 232 bits are segmented into slots. For SF=32, this results in 122 MA (Main) slots and 110 slots, with a total of 1024 chips per slot. +- Radio Frame #1:** The segmented slots form Radio Frame #1. + +Diagram illustrating the mapping of RACH to 1 code SF32. It shows the flow from Information data through CRC attachment, Tail bit attachment, Convolutional Coding 1/2, Puncturing Ratemaching, 2nd Interleaving, and Slot segmentation to form a Radio Frame #1 with SF=32. + +Figure A.9 + +## A.3 E-DCH Reference measurement channels + +### A.3.1 E-DCH Fixed Reference Channels + +#### A.3.1.1 3,84 Mcps TDD Option + +##### A.3.1.1.1 Fixed Reference Channel 1 (FRC1) + +Table A.6: E-DCH Fixed Reference Channel 1 (3,84 Mcps TDD Option) + +| Parameter | Unit | Value | +|---------------------------------------|--------|-------| +| Maximum information bit throughput | kbps | 34.7 | +| Information Bit Payload ( $N_{INF}$ ) | Bits | 347 | +| Number Code Blocks | Blocks | 1 | +| Number of coded bits per TTI | Bits | 1200 | +| Coding Rate | | 0.312 | +| Modulation | | QPSK | +| Number of E-DCH Timeslots | Slots | 6 | +| Number of E-DCH codes per TS | Codes | 1 | +| Spreading factor | SF | 16 | +| Number of E-UCCH per TTI | | 4 | + +![Diagram showing the coding process for E-DCH FRC1. It includes steps: Inf. Bit Payload (347), CRC addition (347 + CRC 24), Code Block Segmentation (1 blocks of 371), Turbo coding R=1/3 (1 blocks of 3 x 371 + 12 tail bits = 1125 bits), Rate Matching (1200), and Time slot segmentation (4 slots of 178 bits and 2 slots of 244 bits, totaling 1200 bits/10 ms).](59b0fc7f07c6794ca85c36c2d06a5fd9_img.jpg) + +Inf. Bit Payload: 347 + +CRC addition: 347 | CRC 24 + +Code Block Segmentation: 1 blocks of 371 + +Turbo coding R=1/3: 1 blocks of $3 \times 371 + 12$ tail bits = 1125 bits + +Rate Matching: 1200 + +Time slot segmentation 1 codes/TS, 6 TS/TTI: + 4 slots of 178 bits + 2 slots of 244 bits + =1200bits/10 ms + +Diagram showing the coding process for E-DCH FRC1. It includes steps: Inf. Bit Payload (347), CRC addition (347 + CRC 24), Code Block Segmentation (1 blocks of 371), Turbo coding R=1/3 (1 blocks of 3 x 371 + 12 tail bits = 1125 bits), Rate Matching (1200), and Time slot segmentation (4 slots of 178 bits and 2 slots of 244 bits, totaling 1200 bits/10 ms). + +Figure A.10: Coding for E-DCH FRC1 (3,84 Mcps TDD Option) + +A.3.1.1.2 Fixed Reference Channel 2 (FRC2) + +Table A.7: E-DCH Fixed Reference Channel 2 (3,84 Mcps TDD Option) + +| Parameter | Unit | Value | +|---------------------------------------|--------|--------| +| Maximum information bit throughput | kbps | 1083.1 | +| Information Bit Payload ( $N_{INF}$ ) | Bits | 10831 | +| Number Code Blocks | Blocks | 3 | +| Number of coded bits per TTI | Bits | 22272 | +| Coding Rate | | 0.488 | +| Modulation | | 16QAM | +| Number of E-DCH Timeslots | Slots | 6 | +| Number of E-DCH codes per TS | Codes | 1 | +| Spreading factor | SF | 2 | +| Number of E-UCCH per TTI | | 2 | + +![Diagram showing the coding process for E-DCH FRC2. It includes steps: Inf. Bit Payload (10831), CRC addition (10831 + CRC 24), Code Block Segmentation (3 blocks of 3619), Turbo coding R=1/3 (3 blocks of 3x3619 + 12 tail bits = 32607bits), Rate Matching (22272), and Time slot segmentation (2 slots of 3328 bits, 4 slots of 3904 bits = 22272 bits/10 ms).](87f625baee73880fd5464a9f60b1b3b8_img.jpg) + +Inf. Bit Payload: 10831 + +CRC addition: 10831 | CRC 24 + +Code Block Segmentation: 3 blocks of 3619 + +Turbo coding R=1/3: 3 blocks of $3 \times 3619 + 12$ tail bits = 32607bits + +Rate Matching: 22272 + +Time slot segmentation 1 codes/TS, 6 TS/TTI: + 2 slots of 3328 bits + 4 slots of 3904 bits + =22272 bits/10 ms + +Diagram showing the coding process for E-DCH FRC2. It includes steps: Inf. Bit Payload (10831), CRC addition (10831 + CRC 24), Code Block Segmentation (3 blocks of 3619), Turbo coding R=1/3 (3 blocks of 3x3619 + 12 tail bits = 32607bits), Rate Matching (22272), and Time slot segmentation (2 slots of 3328 bits, 4 slots of 3904 bits = 22272 bits/10 ms). + +Figure A.11: Coding for E-DCH FRC2 (3,84 Mcps TDD Option) + +A.3.1.1.3 Fixed Reference Channel 3 (FRC3) + +Table A.8: E-DCH Fixed Reference Channel 3 (3,84 Mcps TDD Option) + +| Parameter | Unit | Value | +|---------------------------------------|--------|--------| +| Maximum information bit throughput | kbps | 2073.7 | +| Information Bit Payload ( $N_{INF}$ ) | Bits | 20737 | +| Number Code Blocks | Blocks | 5 | +| Number of coded bits per TTI | Bits | 28992 | +| Coding Rate | | 0.716 | +| Modulation | | 16QAM | +| Number of E-DCH Timeslots | Slots | 4 | +| Number of E-DCH codes per TS | Codes | 1 | +| Spreading factor | SF | 1 | +| Number of E-UCCH per TTI | | 2 | + +![](38c0f202ad5767f3df428353919fa90a_img.jpg) + +| | | | +|---------------------------------------------|-------------|-----------------------------------------------------| +| Inf. Bit Payload | 20737 | | +| CRC addition | 20737 | CRC 24 | +| Code Block Segmentation | 5 blocks of | 4153 | +| Turbo coding R=1/3 | 5 blocks of | $3 \times 4153 + 12 \text{ tail bits}$ = 62355 bits | +| Rate Matching | 28992 | | +| Time slot segmentation 1 codes/TS, 4 TS/TTI | 2 slots of | 6688 bits | +| | 2 slots of | 7808 bits | + += 28992 bits/10 ms + +Figure A.12: Coding for E-DCH FRC3 (3,84 Mcps TDD Option) + +### A.3.1.2 1.28Mcps TDD Option + +#### A.3.1.2.1 Fixed reference channel 1(FRC1) + +Table A.9: E-DCH Fixed reference channel 1 (1.28Mcps TDD option) + +| Parameter | Unit | Value | +|---------------------------------------|--------|--------| +| Maximum information bit throughput | kbps | 56.4 | +| Information Bit Payload ( $N_{INF}$ ) | Bits | 282 | +| Number Code Blocks | Blocks | 1 | +| Number of coded bits per TTI | Bits | 306 | +| Coding Rate | | 0.4965 | +| Modulation | | QPSK | +| Number of E-DCH Timeslots | Slots | 2 | +| Number of E-DCH codes per TS | Codes | 1 | +| Spreading factor | SF | 4 | +| Number of E-UCCH per TTI | | 4 | + +![Diagram showing the bit processing flow for E-DCH FRC1. It includes Inf. Bit Payload (282), CRC addition (282 + CRC 24), Code Block Segmentation (1 block of 306), Turbo coding R=1/3 (1 block of 3 * 306 + 12 tail bits = 930 bits), Rate Matching (568), and Time slot segmentation (2 slots of 284 bits = 568 bits/5 ms).](c9bfcc4c4ef694696c292b03de45d2bb_img.jpg) + +Inf. Bit Payload: 282 + +CRC addition: 282 | CRC 24 + +Code Block Segmentation: 1 blocks of 306 + +Turbo coding R=1/3: 1 blocks of $3 \times 306 + 12$ tail bits = 930 bits + +Rate Matching: 568 + +Time slot segmentation 1 codes/TS, 2TS/TTI: 2 slots of 284 bits = 568 bits/5 ms + +Diagram showing the bit processing flow for E-DCH FRC1. It includes Inf. Bit Payload (282), CRC addition (282 + CRC 24), Code Block Segmentation (1 block of 306), Turbo coding R=1/3 (1 block of 3 \* 306 + 12 tail bits = 930 bits), Rate Matching (568), and Time slot segmentation (2 slots of 284 bits = 568 bits/5 ms). + +**Figure A.12A: Coding for E-DCH FRC1 (1.28 Mcps TDD Option)** + +A.3.1.2.2 Fixed reference channel 2(FRC2) + +**Table A.10: E-DCH Fixed reference channel 2(1.28Mcps TDD option)** + +| Parameter | Unit | Value | +|---------------------------------------|--------|-------| +| Maximum information bit throughput | kbps | 227.8 | +| Information Bit Payload ( $N_{INF}$ ) | Bits | 1139 | +| Number Code Blocks | Blocks | 1 | +| Number of coded bits per TTI | Bits | 1163 | +| Coding Rate | | 0.85 | +| Modulation | | QPSK | +| Number of E-DCH Timeslots | Slots | 2 | +| Number of E-DCH codes per TS | Codes | 1 | +| Spreading factor | SF | 2 | +| Number of E-UCCH per TTI | | 2 | + +![Diagram showing the bit processing flow for E-DCH FRC2. It includes Inf. Bit Payload (1139), CRC addition (1139 + CRC 24), Code Block Segmentation (1 blocks of 1163), Turbo coding R=1/3 (1 blocks of 3 * 1163 + 12 tail bits = 3501 bits), Rate Matching (1340), and Time slot segmentation (2 slots of 670 bits = 1340bits/5 ms).](cdb980c2fe504f3132b907d4de707c7f_img.jpg) + +Inf. Bit Payload: 1139 + +CRC addition: 1139 | CRC 24 + +Code Block Segmentation: 1 blocks of 1163 + +Turbo coding R=1/3: 1 blocks of $3 \times 1163 + 12$ tail bits = 3501 bits + +Rate Matching: 1340 + +Time slot segmentation 1 codes/TS, 2TS/TTI: 2 slots of 670 bits = 1340bits/5 ms + +Diagram showing the bit processing flow for E-DCH FRC2. It includes Inf. Bit Payload (1139), CRC addition (1139 + CRC 24), Code Block Segmentation (1 blocks of 1163), Turbo coding R=1/3 (1 blocks of 3 \* 1163 + 12 tail bits = 3501 bits), Rate Matching (1340), and Time slot segmentation (2 slots of 670 bits = 1340bits/5 ms). + +Figure A.13: Coding for E-DCH FRC2 (1.28 Mcps TDD Option) + +A.3.1.2.3 Fixed reference channel 3(FRC3) + +Table A.11: E-DCH Fixed reference channel 3 (1.28Mcps TDD option) + +| Parameter | Unit | Value | +|---------------------------------------|--------|-------| +| Maximum information bit throughput | kbps | 489 | +| Information Bit Payload ( $N_{INF}$ ) | Bits | 2445 | +| Number Code Blocks | Blocks | 1 | +| Number of coded bits per TTI | Bits | 2469 | +| Coding Rate | | 0.598 | +| Modulation | | 16QAM | +| Number of E-DCH Timeslots | Slots | 3 | +| Number of E-DCH codes per TS | Codes | 1 | +| Spreading factor | SF | 2 | +| Number of E-UCCH per TTI | | 2 | + +![](b437cd7078b36507e5d918fe6224e6dd_img.jpg) + +| | | | +|---------------------------------------------|-------------|----------------------------------------------------| +| Inf. Bit Payload | 2445 | | +| CRC addition | 2445 | CRC 24 | +| Code Block Segmentation | 1 blocks of | 2469 | +| Turbo coding R=1/3 | 1 blocks of | $3 \times 2469 + 12 \text{ tail bits}$ = 7419 bits | +| Rate Matching | 4088 | | +| Time slot segmentation 1 codes/TS, 3 TS/TTI | 2 slots of | 1340bits | +| | 1 slots of | 1408bits | + += 4088 bits/5 ms + +**Figure A.14: Coding for E-DCH FRC3 (1.28 Mcps TDD Option)** + +#### A.3.1.2.4 Fixed reference channel 4(FRC4) + +**Table A.12: E-DCH Fixed reference channel 4 (1.28Mcps TDD option)** + +| Parameter | Unit | Value | +|---------------------------------------|--------|--------| +| Maximum information bit throughput | kbps | 1281.2 | +| Information Bit Payload ( $N_{INF}$ ) | Bits | 6406 | +| Number Code Blocks | Blocks | 2 | +| Number of coded bits per TTI | Bits | 6430 | +| Coding Rate | | 0.5757 | +| Modulation | | 16QAM | +| Number of E-DCH Timeslots | Slots | 4 | +| Number of E-DCH codes per TS | Codes | 1 | +| Spreading factor | SF | 1 | +| Number of E-UCCH per TTI | | 2 | + +![](5d819f259411162c4e3371915818ae22_img.jpg) + +| | | | +|-----------------------------------------------|-------------|---------------------------------------------------| +| Inf. Bit Payload | 6406 | | +| CRC addition | 6406 | CRC 24 | +| Code Block Segmentation | 2 blocks of | 3215 | +| Turbo coding R=1/3 | 2 blocks of | $3 \times 3215 + 12 \text{ tail bits}$ = 9657bits | +| Rate Matching | 11128 | | +| Time slot segmentation 1
codes/TS, 4TS/TTI | 2 slots of | 2748 bits | +| | 2 slots of | 2816 bits | +| | | =11128 bits/5 ms | + +Figure A.15: Coding for E-DCH FRC4 (1.28 Mcps TDD Option) + +### A.3.1.3 7,68 Mcps TDD Option + +#### A.3.1.3.1 Fixed Reference Channel 1 (FRC1) + +Table A.13: E-DCH Fixed Reference Channel 1 (7.68 Mcps TDD Option) + +| Parameter | Unit | Value | +|---------------------------------------|--------|-------| +| Maximum information bit throughput | kbps | 35.9 | +| Information Bit Payload ( $N_{INF}$ ) | Bits | 359 | +| Number Code Blocks | Blocks | 1 | +| Number of coded bits per TTI | Bits | 1200 | +| Coding Rate | | 0.323 | +| Modulation | | QPSK | +| Number of E-DCH Timeslots | Slots | 6 | +| Number of E-DCH codes per TS | Codes | 1 | +| Spreading factor | SF | 32 | +| Number of E-UCCH per TTI | | 4 | + +![](728a02fe4a04e7f91835147194997cd4_img.jpg) + +| | | | | +|---------------------------------------------|-------------|-------------------------------|-----------------| +| Inf. Bit Payload | 359 | | | +| CRC addition | 359 | CRC 24 | | +| Code Block Segmentation | 1 blocks of | 383 | | +| Turbo coding R=1/3 | 1 blocks of | $3 \times 383 + 12$ tail bits | = 1161 bits | +| Rate Matching | 1200 | | | +| Time slot segmentation 1 codes/TS, 6 TS/TTI | 4 slots of | 178 bits | =1200bits/10 ms | +| | 2 slots of | 244 bits | | + +**Figure A.16: Coding for E-DCH FRC1 (7.68 Mcps TDD Option)** + +### A.3.1.3.2 Fixed Reference Channel 2 (FRC2) + +**Table A.14: E-DCH Fixed Reference Channel 2 (7.68 Mcps TDD Option)** + +| Parameter | Unit | Value | +|---------------------------------------|--------|--------| +| Maximum information bit throughput | kbps | 1083.1 | +| Information Bit Payload ( $N_{INF}$ ) | Bits | 10831 | +| Number Code Blocks | Blocks | 3 | +| Number of coded bits per TTI | Bits | 22272 | +| Coding Rate | | 0.488 | +| Modulation | | 16QAM | +| Number of E-DCH Timeslots | Slots | 6 | +| Number of E-DCH codes per TS | Codes | 1 | +| Spreading factor | SF | 4 | +| Number of E-UCCH per TTI | | 2 | + +![](931bd52904f67b17796a38b47af51e30_img.jpg) + +| | | | +|------------------------------------------------|-------------|----------------------------------------------------| +| Inf. Bit Payload | 10831 | | +| CRC addition | 10831 | CRC 24 | +| Code Block Segmentation | 3 blocks of | 3619 | +| Turbo coding R=1/3 | 3 blocks of | $3 \times 3619 + 12 \text{ tail bits}$ = 32607bits | +| Rate Matching | 22272 | | +| Time slot segmentation 1
codes/TS, 6 TS/TTI | 2 slots of | 3328 bits | +| | 4 slots of | 3904 bits | + +=22272 bits/10 ms + +**Figure A.17: Coding for E-DCH FRC2 (7.68 Mcps TDD Option)** + +### A.3.1.3.3 Fixed Reference Channel 3 (FRC3) + +**Table A.15: E-DCH Fixed Reference Channel 3 (7.68 Mcps TDD Option)** + +| Parameter | Unit | Value | +|---------------------------------------|--------|--------| +| Maximum information bit throughput | kbps | 2085.1 | +| Information Bit Payload ( $N_{INF}$ ) | Bits | 20851 | +| Number Code Blocks | Blocks | 5 | +| Number of coded bits per TTI | Bits | 28992 | +| Coding Rate | | 0.720 | +| Modulation | | 16QAM | +| Number of E-DCH Timeslots | Slots | 6 | +| Number of E-DCH codes per TS | Codes | 1 | +| Spreading factor | SF | 2 | +| Number of E-UCCH per TTI | | 2 | + +![Diagram illustrating the coding process for E-DCH FRC3 (7.68 Mcps TDD Option).](7109096552c3464c931b0b39109b9b41_img.jpg) + +The diagram illustrates the coding process for E-DCH FRC3 (7.68 Mcps TDD Option): + +- Inf. Bit Payload:** 20851 bits. +- CRC addition:** 20851 bits + CRC 24 bits. +- Code Block Segmentation:** 5 blocks of 4175 bits each. +- Turbo coding R=1/3:** 5 blocks of $3 \times 4175 + 12$ tail bits = 62685 bits. +- Rate Matching:** 28992 bits. +- Time slot segmentation 1 codes/TS, 4 TS/TTI:** + - 2 slots of 6688 bits + - 2 slots of 7808 bits + = 28992 bits/10 ms + +Diagram illustrating the coding process for E-DCH FRC3 (7.68 Mcps TDD Option). + +Figure A.18: Coding for E-DCH FRC3 (7.68 Mcps TDD Option) + +## A.4 HS-SICH Reference measurement channels + +### A.4.1 3,84 Mcps TDD Option + +(void) + +### A.4.2 1,28 Mcps TDD Option + +Table A.16: HS-SICH type1 Reference Channel 1 (1,28 Mcps TDD Option) + +| Parameter | Unit | Value | +|---------------------|------|-------| +| Information bits | bits | 8 | +| Encoded bits | bits | 84 | +| Number of codes | - | 1 | +| Number of timeslots | - | 1 | +| TTI | ms | 5 | +| Spreading Factor | SF | 16 | + +![Diagram showing the coding process for HS-SICH type1 channel. It includes four boxes: 'Inf. Bit Payload' with value '8', 'Coding and multiplex' with value '84', 'Interleaving' with value '84bits/5ms', and 'Slot segmentation 1 codes/TS, 1TS/TTI' with a sub-table containing '44', '144chips', 'SS', 'TPC', '40'.](8c05782074bb11421b43f2d5d6799b62_img.jpg) + +Inf. Bit Payload + +8 + +Coding and multiplex + +84 + +Interleaving + +84bits/5ms + +Slot segmentation 1 codes/TS, 1TS/TTI + +| | | | | | +|----|----------|----|-----|----| +| 44 | 144chips | SS | TPC | 40 | +|----|----------|----|-----|----| + +Diagram showing the coding process for HS-SICH type1 channel. It includes four boxes: 'Inf. Bit Payload' with value '8', 'Coding and multiplex' with value '84', 'Interleaving' with value '84bits/5ms', and 'Slot segmentation 1 codes/TS, 1TS/TTI' with a sub-table containing '44', '144chips', 'SS', 'TPC', '40'. + +Figure A.19: Coding for HS-SICH type1 channel (1,28 Mcps TDD Option) + +Table A.17: HS-SICH type2 Reference Channel 1 (1.28 Mcps TDD Option) + +| Parameter | Unit | Value | +|---------------------|------|-------| +| Information bits | bits | 16 | +| Encoded bits | bits | 168 | +| Number of codes | - | 1 | +| Number of timeslots | - | 1 | +| TTI | ms | 5 | +| Spreading Factor | SF | 8 | + +![Diagram showing the coding process for HS-SICH type2 channel. It includes four boxes: 'Inf. Bit Payload' with value '16', 'Coding and multiplex' with value '168', 'Interleaving' with value '168bits/5ms', and 'Slot segmentation 1 codes/TS, 1TS/TTI' with a sub-table containing '88', '144chips', 'SS', 'TPC', '80'.](b988d13a7e9ebb10a1df8e0957a15c51_img.jpg) + +Inf. Bit Payload + +16 + +Coding and multiplex + +168 + +Interleaving + +168bits/5ms + +Slot segmentation 1 codes/TS, 1TS/TTI + +| | | | | | +|----|----------|----|-----|----| +| 88 | 144chips | SS | TPC | 80 | +|----|----------|----|-----|----| + +Diagram showing the coding process for HS-SICH type2 channel. It includes four boxes: 'Inf. Bit Payload' with value '16', 'Coding and multiplex' with value '168', 'Interleaving' with value '168bits/5ms', and 'Slot segmentation 1 codes/TS, 1TS/TTI' with a sub-table containing '88', '144chips', 'SS', 'TPC', '80'. + +Figure A.20: Coding for HS-SICH type2 channel (1.28 Mcps TDD Option) + +## Annex B (normative): Propagation conditions + +### B.1 Static propagation condition + +The propagation for the static performance measurement is an Additive White Gaussian Noise (AWGN) environment. No fading and multi-paths exist for this propagation model. + +### B.2 Multi-path fading propagation conditions + +#### B.2.1 3,84 Mcps TDD option + +Table B.1 and B.1A shows propagation conditions that are used for the performance measurements in multi-path fading environment. All taps have classical Doppler spectrum, defined as: + +$$(CLASS) \quad S(f) \propto 1/(1 - (f/f_D)^2)^{0.5} \quad \text{for } f \in -f_D, f_D$$ + +**Table B.1: Propagation Conditions for Multi path Fading Environments for 3,84 Mcps TDD option for operations referenced in 4.2 a), 4.2 b) and 4.2 c)** + +| Case 1, speed 3km/h | | Case 2, speed 3 km/h | | Case 3, speed 120 km/h | | +|---------------------|--------------------------|----------------------|--------------------------|------------------------|--------------------------| +| Relative Delay [ns] | Relative Mean Power [dB] | Relative Delay [ns] | Relative Mean Power [dB] | Relative Delay [ns] | Relative Mean Power [dB] | +| 0 | 0 | 0 | 0 | 0 | 0 | +| 976 | -10 | 976 | 0 | 260 | -3 | +| | | 12000 | 0 | 521 | -6 | +| | | | | 781 | -9 | + +**Table B.1A: Propagation Conditions for Multi path Fading Environments for operations referenced in 4.2 d)** + +| Case 1, speed 2.3km/h | | Case 2, speed 2.3 km/h | | Case 3, speed 92 km/h | | +|-----------------------|--------------------------|------------------------|--------------------------|-----------------------|--------------------------| +| Relative Delay [ns] | Relative Mean Power [dB] | Relative Delay [ns] | Relative Mean Power [dB] | Relative Delay [ns] | Relative Mean Power [dB] | +| 0 | 0 | 0 | 0 | 0 | 0 | +| 976 | -10 | 976 | 0 | 260 | -3 | +| | | 12000 | 0 | 521 | -6 | +| | | | | 781 | -9 | + +#### B.2.2 1,28 Mcps TDD option + +Table B.2 shows propagation conditions that are used for the performance measurements in multi-path fading environment. All taps have classical Doppler spectrum, defined as: + +$$(CLASS) \quad S(f) \propto 1/(1 - (f/f_D)^2)^{0.5} \quad \text{for } f \in -f_D, f_D$$ + +**Table B2: Propagation Conditions for Multi path Fading Environments** + +| Case 1 | | Case 2 | | Case 3 | | +|----------------------------------------------|--------------------------|-----------------------------------------------|--------------------------|-------------------------------------------------|--------------------------| +| Speed for operating in band a, b, c, f 3km/h | | Speed for operating in band a, b, c, f: 3km/h | | Speed for operating in band a, b, c, f: 120km/h | | +| Speed for operating in band d: 2.3km/h | | Speed for operating in band d: 2.3km/h | | Speed for operating in band d: 92km/h | | +| Speed for operating in band e: 2.6km/h | | Speed for operating in band e: 2.6km/h | | Speed for operating in band e: 102km/h | | +| Relative Delay [ns] | Relative Mean Power [dB] | Relative Delay [ns] | Relative Mean Power [dB] | Relative Delay [ns] | Relative Mean Power [dB] | +| 0 | 0 | 0 | 0 | 0 | 0 | +| 2928 | -10 | 2928 | 0 | 781 | -3 | +| | | 12000 | 0 | 1563 | -6 | +| | | | | 2344 | -9 | + +**Table B.2A: Propagation Conditions for Multipath Fading Environments for E-DCH Performance Requirements for 1,28 Mcps TDD** + +| ITU Pedestrian A
Speed 3km/h
(PA3) | | ITU Pedestrian B
Speed 3km/h
(PB3) | | ITU vehicular A
Speed 30km/h
(VA30) | | +|-----------------------------------------------|---------------------------|----------------------------------------------|---------------------------|------------------------------------------------|---------------------------| +| Speed for operating in band a, b, c, f: 3km/h | | Speed for operating in band a, b, c, f 3km/h | | Speed for operating in band a, b, c, f: 30km/h | | +| Speed for operating in band d: 2.3km/h | | Speed for operating in band d: 2.3km/h | | Speed for operating in band d: 23km/h | | +| Speed for operating in band e: 2.6km/h | | Speed for operating in band e: 2.6km/h | | Speed for operating in band e: 26km/h | | +| Relative Delay [ns] | Relative Mean Power [ dB] | Relative Delay [ns] | Relative Mean Power [ dB] | Relative Delay [ns] | Relative Mean Power [ dB] | +| 0 | 0 | 0 | 0 | 0 | 0 | +| 110 | -9.7 | 200 | -0.9 | 310 | -1.0 | +| 190 | -19.2 | 800 | -4.9 | 710 | -9.0 | +| 410 | -22.8 | 1200 | -8.0 | 1090 | -10.0 | +| | | 2300 | -7.8 | 1730 | -15.0 | +| | | 3700 | -23.9 | 2510 | -20.0 | + +Note: For MC-HSUPA requirements, the fading of the signals for each carrier shall be independent. + +## B.2.3 7,68 Mcps TDD option + +Table B.4 and B.5 shows propagation conditions that are used for the performance measurements in multi-path fading environment. All taps have classical Doppler spectrum, defined as: + +$$(CLASS) \quad S(f) \propto 1/(1 - (f/f_D)^2)^{0.5} \quad \text{for } f \in -f_D, f_D$$ + +**Table B.3: Propagation Conditions for Multi path Fading Environments for 3,84 Mcps TDD option for operations referenced in 4.2 a), 4.2 b) and 4.2 c)** + +| Case 1, speed 3km/h | | Case 2, speed 3 km/h | | Case 3, speed 120 km/h | | +|---------------------|--------------------------|----------------------|--------------------------|------------------------|--------------------------| +| Relative Delay [ns] | Relative Mean Power [dB] | Relative Delay [ns] | Relative Mean Power [dB] | Relative Delay [ns] | Relative Mean Power [dB] | +| 0 | 0 | 0 | 0 | 0 | 0 | +| 976 | -10 | 976 | 0 | 260 | -3 | +| | | 12000 | 0 | 521 | -6 | +| | | | | 781 | -9 | + +**Table B.5: Propagation Conditions for Multi path Fading Environments for operations referenced in 4.2 d)** + +| Case 1, speed 2.3km/h | | Case 2, speed 2.3 km/h | | Case 3, speed 92 km/h | | +|-----------------------|--------------------------|------------------------|--------------------------|-----------------------|--------------------------| +| Relative Delay [ns] | Relative Mean Power [dB] | Relative Delay [ns] | Relative Mean Power [dB] | Relative Delay [ns] | Relative Mean Power [dB] | +| 0 | 0 | 0 | 0 | 0 | 0 | +| 976 | -10 | 976 | 0 | 260 | -3 | +| | | 12000 | 0 | 521 | -6 | +| | | | | 781 | -9 | + +## B.3 High speed train conditions + +High speed train conditions are as follows: + +Scenario 1: Open space + +Scenario 3: Tunnel for multi-antennas + +The high speed train conditions for the test of the baseband performance are two non-fading propagation channels in both scenarios. + +Doppler shift for both scenarios is given by: + +$$(B.1)$$ + +where $f_d$ is the Doppler shift and $f_{max}$ is the maximum Doppler frequency. The cosine of angle is given by: + +$$(B.2)$$ + +$$(B.3)$$ + +$$(B.4)$$ + +where $d_0$ is the initial distance of the train from BS, and $d$ is BS-Railway track distance, both in meters; $v$ is the velocity of the train in m/s, $t$ is time in seconds. + +Doppler shift and cosine angle is given by equation B.1 and B.2-B.4 respectively, where the required input parameters listed in table B.6 and the resulting Doppler shift shown in Figure B.1 and B.2 are applied for all frequency bands. + +**Table B.6: Parameters for high speed train conditions** + +| Parameter | Value | | +|-----------|------------|------------| +| | Scenario 1 | Scenario 3 | +| | 1000 m | 300 m | +| | 50 m | 2 m | +| | 350 km/h | 300 km/h | +| | 1310 Hz | 1125 Hz | + +NOTE1: Parameters for HST conditions in table B. including $d_0$ and Doppler shift trajectories presented on figures B.1 and B.2 were derived for Band a). + +![Figure B.1: Doppler shift trajectory for scenario 1. A line graph showing Doppler Shift (Hz) on the y-axis (ranging from -1500 to 1500) versus Time (sec) on the x-axis (ranging from 0 to 50). The curve shows a smooth, periodic-like oscillation between approximately 1300 Hz and -1300 Hz.](b57fe904794260818d988eb4bf9a1d0b_img.jpg) + +This graph shows a smooth, periodic-like oscillation of Doppler shift over a 50-second time period. The y-axis represents Doppler Shift in Hz, ranging from -1500 to 1500 with major grid lines every 500 Hz. The x-axis represents Time in seconds, ranging from 0 to 50 with major grid lines every 10 seconds. The curve starts at approximately 1300 Hz at 0 seconds, decreases smoothly to a minimum of about -1300 Hz at 10 seconds, increases back to about 1300 Hz at 20 seconds, decreases again to about -1300 Hz at 30 seconds, increases to about 1300 Hz at 40 seconds, and finally decreases to about -1300 Hz at 50 seconds. + +Figure B.1: Doppler shift trajectory for scenario 1. A line graph showing Doppler Shift (Hz) on the y-axis (ranging from -1500 to 1500) versus Time (sec) on the x-axis (ranging from 0 to 50). The curve shows a smooth, periodic-like oscillation between approximately 1300 Hz and -1300 Hz. + +Figure B.1: Doppler shift trajectory for scenario 1 + +![Figure B.2: Doppler shift trajectory for scenario 3. A line graph showing Doppler Shift (Hz) on the y-axis (ranging from -1500 to 1500) versus Time (sec) on the x-axis (ranging from 0 to 20). The curve shows a square-wave-like oscillation between approximately 1100 Hz and -1100 Hz.](c55e08c6d3924487ee74b344ef4755f5_img.jpg) + +This graph shows a square-wave-like oscillation of Doppler shift over a 20-second time period. The y-axis represents Doppler Shift in Hz, ranging from -1500 to 1500 with major grid lines every 500 Hz. The x-axis represents Time in seconds, ranging from 0 to 20 with major grid lines every 5 seconds. The curve starts at approximately 1100 Hz at 0 seconds, drops sharply to about -1100 Hz at 2 seconds, remains constant at -1100 Hz until 5 seconds, jumps sharply back to about 1100 Hz at 5 seconds, remains constant at 1100 Hz until 9 seconds, drops sharply to about -1100 Hz at 9 seconds, remains constant at -1100 Hz until 12 seconds, jumps sharply back to about 1100 Hz at 12 seconds, remains constant at 1100 Hz until 16 seconds, drops sharply to about -1100 Hz at 16 seconds, remains constant at -1100 Hz until 19 seconds, and finally jumps sharply back to about 1100 Hz at 19 seconds. + +Figure B.2: Doppler shift trajectory for scenario 3. A line graph showing Doppler Shift (Hz) on the y-axis (ranging from -1500 to 1500) versus Time (sec) on the x-axis (ranging from 0 to 20). The curve shows a square-wave-like oscillation between approximately 1100 Hz and -1100 Hz. + +Figure B.2: Doppler shift trajectory for scenario 3 + +--- + +## Annex C (normative): Global in-channel Tx test + +### C.1 General + +The global in-channel Tx test enables the measurement of all relevant parameters that describe the in-channel quality of the output signal of the Tx under test in a single measurement process. + +The parameters describing the in-channel quality of a transmitter, however, are not necessarily independent. The algorithm chosen for description inside this annex places particular emphasis on the exclusion of all interdependencies among the parameters. Any other algorithm (e.g. having better computational efficiency) may be applied, as long as the results are the same within the accuracy limits. + +All notes referred to in the various subclauses of C.2 are put together in clause C.3 + +--- + +### C.2 Definition of the process + +#### C.2.1 Basic principle + +The process is based on the comparison of the actual **output signal of the Tx under test**, received by an ideal receiver, with a **reference signal**, that is generated by the measuring equipment and represents an ideal error free received signal. The reference signal shall be composed of the same number of codes at the correct spreading factors as contained in the test signal. Note, for simplification, the notation below assumes only codes of one spreading factor although the algorithm is valid for signals containing multiple spreading factors. All signals are represented as equivalent (generally complex) base band signals. + +#### C.2.2 Output signal of the Tx under test + +The output signal of the Tx under test is acquired by the measuring equipment, filtered by a matched filter (RRC characteristic with roll-off $\alpha = 0,22$ , correct in shape and in position on the frequency axis) and stored for further processing. + +The following form represents the physical signal in the entire measurement interval: + +one vector **Z**, containing $N = n_s \times sf + ma$ complex samples; + +with + +$n_s$ : number of symbols in the measurement interval; + +$sf$ : number of chips per symbol. ( $sf$ : spreading factor) (see Note: Symbol length) + +$ma$ : number of midamble chips, or for IMB the number of chips in the TDM pilot region + +#### C.2.3 Reference signal + +The reference signal is constructed by the measuring equipment according to the relevant Tx specifications. + +It is filtered by the same matched filter, mentioned in C.2.2, and stored at the intersymbol interference free instants. The following form represents the reference signal in the entire measurement interval: + +one vector **R**, containing $N = n_s \times sf + ma$ complex samples; + +where $n_s$ , $sf$ and $ma$ have the same meaning as defined above in C.2.2. + +#### C.2.4 Classification of measurement results + +The measurement results achieved by the global in-channel Tx test can be classified into two types: + +- **Results of type "deviation"**, where the error-free parameter has a non-zero magnitude. (These are the parameters that represent the signal). These parameters are: + +RF Frequency + +Power + +(in case of single code) + +Code Domain Power + +(in case of multi-code) + +Timing + +(only for UE) (see Note: Deviation) + +(Additional parameters: see Note: Deviation) + +- **Results of type "residual"**, where the error-free parameter has value zero. (These are the parameters that represent the error values of the measured signal; ideally, their magnitude is zero). These parameters are: + +Error Vector Magnitude (EVM) + +Peak Code Domain Error (PCDE) + +(Additional parameters: see Note: Residual) + +## C.2.5 Process definition to achieve results of type "deviation" + +The reference signal (**R**; see subclause C.2.3) and the signal under Test (**Z**; see subclause C.2.2) are varied with respect to the parameters mentioned in subclause C.2.4 under "results of type deviation" in order to achieve best fit. Best fit is achieved when the RMS difference value between the varied signal under test and the varied reference signal is an absolute minimum. + +Overview: + +**Z**: Signal under test. + +**R**: Reference signal, + +with frequency $f$ , the timing $t$ , the phase $\varphi$ , gain of code1 ( $g_1$ ), gain of code2 ( $g_2$ ) etc, and the gain of the synch channel $g_{\text{synch}}$ + +The parameters marked with a tilde in **Z** and **R** are varied in order to achieve a best fit. + +**R'** and **Z'** are each of length $n_s \cdot sf$ and depending on the length of the measurement interval result of possibly multiple successive applications of the minimum process. + +Detailed formula: see Note: Formula for the minimum process + +The varied reference signal, after the best-fit process, will be called **R'**. + +The varied signal under test, after the best fit process, will be called **Z'**. + +**R'** and **Z'** are each of length $n_s \cdot sf$ and depending on the length of the measurement interval result of possibly multiple successive applications of the minimum process. + +Those parameter values, which - after the best-fit process -lead to **R'** and **Z'**, represent directly the wanted results of type "deviation". These parameter values are expressed as deviations from the reference value, using the same units as the corresponding reference value. + +In the case of multi-code transmission, the best-fit process of the type "deviation" parameters frequency, timing (and any additional parameter as e.g. RF phase) is not done with respect to the individual codes, but commonly for the complete code set used; therefore, the process returns one measurement value only for each parameter. + +(These parameters are not varied on the individual codes signals such that the process would return $k_r$ frequency errors... ( $k_r$ : number of codes in the reference signal)). + +The only type-"deviation"-parameters varied individually are the code domain gain factors ( $g_1, g_2, \dots$ ) + +### C.2.5.1 Decision Point Power + +The mean-square value of the signal-under-test, sampled at the best estimate of the of Intersymbol-Interference-free points using the process defined in subclause 2.5, is referred to the *Decision Point Power* (DPP): + +### C.2.5.2 Code-Domain Power + +The samples, $Z'$ , are separated into symbol intervals to create $n_s$ time-sequential vectors $\mathbf{z}$ with $s_f$ complex samples comprising one symbol interval. The *Code Domain Power* is calculated according to the following steps: + +- 1) Take the vectors $\mathbf{z}$ defined above. +- 2) To achieve meaningful results it is necessary to descramble $\mathbf{z}$ , leading to $\mathbf{z}'$ +- 3) Take the orthogonal vectors of the channelization code set $\mathbf{C}$ (all codes belonging to one spreading factor) as defined in TS 25.213 and TS 25.223 (range +1, -1), and normalize by the norm of the vectors to produce $\mathbf{C}_{\text{norm}} = \mathbf{C} / \sqrt{s_f}$ . (see Note: Symbol length) +- 4) Calculate the inner product of $\mathbf{z}'$ with $\mathbf{C}_{\text{norm}}$ . Do this for all symbols of the measurement interval and for all codes in the code space. +This gives an array of format $k \times n_s$ , each value representing a specific symbol and a specific code, which can be exploited in a variety of ways. + +$k$ : total number of codes in the code space + +$n_s$ : number of symbols in the measurement interval + +- 5) Calculate $k$ mean-square values, each mean-square value unifying $n_s$ symbols within one code. +(These values can be called "*Absolute CodeDomainPower* (CDP)" [ $\text{Volt}^2$ ].) The sum of the $k$ values of CDP is equal to DPP. +- 6) Normalize by the decision point power to obtain + +$$\text{Relative CodeDomain Power} = \frac{\text{Absolute CodeDomainPower}}{\text{DecisionPointPower}}$$ + +## C.2.6 Process definition to achieve results of type "residual" + +The difference between the varied reference signal ( $\mathbf{R}'$ ; see subclause C.2.5.) and the varied Tx signal under test ( $\mathbf{Z}'$ ; see subclause C.2.2) is the error vector $\mathbf{E}$ versus time: + +$$\mathbf{E} = \mathbf{Z}' - \mathbf{R}'$$ + +Depending on the parameter to be evaluated, it is appropriate to represent $\mathbf{E}$ in one of the following two different forms: + +**Form EVM** (representing the physical error signal in the entire measurement interval) + +One vector $\mathbf{E}$ , containing $N = n_s \times s_f + m_a$ complex samples; + +where $n_s$ , $s_f$ and $m_a$ have the same meaning as defined above in C.2.2. + +**Form PCDE** (derived from Form EVM by separating the samples into symbol intervals) + +$n_s$ time-sequential vectors $\mathbf{e}$ with $s_f$ complex samples comprising one symbol interval. + +$\mathbf{E}$ gives results of type "residual" applying the two algorithms defined in subclauses C.2.6.1 and C.2.6.2. + +### C.2.6.1 Error Vector Magnitude (EVM) + +The Error Vector Magnitude EVM is calculated according to the following steps: + +- 1) Take the error vector $\mathbf{E}$ defined in subclause C.2.6 (Form EVM) and calculate the RMS value of $\mathbf{E}$ ; the result will be called $\text{RMS}(\mathbf{E})$ . + +- 2) Take the varied reference vector **R** defined in subclause C.2.3 and calculate the RMS value of **R**; the result will be called $\text{RMS}(\mathbf{R})$ . +- 3) Calculate EVM according to: + +$$\text{EVM} = \frac{\text{RMS}(\mathbf{E})}{\text{RMS}(\mathbf{R})} \times 100\% \quad (\text{here, EVM is relative and expressed in \%})$$ + +(see Note: TDD) + +(see Note: Formula for EVM) + +### C.2.6.2 Peak Code Domain Error (PCDE) + +The Peak Code Domain Error is calculated according to the following steps: + +- 1) Take the error vectors **e** defined in subclause C.2.6 (Form PCDE) +- 2) Take the orthogonal vectors of the spreading code set **C** (all codes belonging to one spreading factor) as defined in TS 25.213 and TS 25.223 (range +1, -1). (see Note: Symbol length) and normalize by the norm of the vectors to produce $\mathbf{C}_{\text{norm}} = \mathbf{C}/\sqrt{\text{s}f}$ . (see Note: Symbol length) +- 3) To achieve meaningful results, it is necessary to descramble **e**, leading to **e'** +- 4) Calculate the inner product of **e'** with $\mathbf{C}_{\text{norm}}$ . Do this for all symbols of the measurement interval and for all codes in the code space. +This gives an array of format $k \times n_s$ , each value representing an error-vector representing a specific symbol and a specific code, which can be exploited in a variety of ways. + +$k$ : total number of codes in the code space + +$n_s$ : number of symbols in the measurement interval + +- 5) Calculate $k$ RMS values, each RMS value unifying $n$ symbols within one code. +(These values can be called "Absolute CodeEVMs" [Volt].) +- 6) Find the peak value among the $k$ "absolute Code-EVMs". +(This value can be called "Absolute PeakCodeEVM" [Volt].) +- 7) Calculate PCDE according to: + +$$\text{PCDE} = 10 \lg \frac{(\text{absolute PeakCodeEVM})^2}{(\text{RMS}(\mathbf{R}))^2} \text{ dB} \quad (\text{a relative value in dB}).$$ + +see Note: TDD + +see Note: Synch channel + +### C.2.6.3 Relative Code Domain Error (RCDE) + +The Relative Code Domain Error is calculated for a wanted code according to the following steps: + +- 1) Calculate the value "*Absolute CodeEVM*" [Volt] for the wanted code according to C.2.6.2, as an RMS value unifying $n_s = 2400$ symbols corresponding to the measurement interval of one timeslot. +- 2) Calculate the value "*Absolute CodeDomainPower (CDP)*" [Volt2] for the wanted code according to C.2.5.2, with $n_s = 2400$ symbols corresponding to the measurement interval of one timeslot. +- 3) Calculate RCDE according to: + +4) The average RCDE across a set of wanted codes is defined as the mean of the linear RCDE values and subsequently expressed in dB. + +--- + +## C.3 Notes + +### C.3.1 Symbol length + +A general code-multiplexed signal is multi-code and multi-rate. In order to avoid unnecessary complexity, the measurement applications use a unique symbol-length, corresponding to a specific spreading factor, regardless of the really intended spreading factor. Nevertheless, the complexity with a multi-code / multi-rate signal can be mastered by introducing appropriate definitions. + +### C.3.2 Deviation + +It is conceivable to regard more parameters as type „deviation“, e.g. chip clock and RF phase. However, because chip clock and RF frequency are linked together by a statement in the core specifications [1], it is sufficient to process RF frequency only. + +The parameter RF phase must be varied within the best-fit process (C.2.5). Although necessary, this parameter-variation does not describe any error, as the modulation schemes used in the system do not depend on an absolute RF-phase. + +The parameter Timing must be varied within the best fit process (C.2.5.) This parameter variation does not describe any error, when applied to the Node B test. However when applied to the UE test, it describes the error of the UE's Timing Advance. + +### C.3.3 Residual + +It is conceivable to regard more parameters as type „residual“, e.g. IQ origin offset. As it is not the intention of the test to separate for different error sources, but to quantify the quality of the signal, all such parameters are not extracted by the best-fit process, instead remain part of EVM and PCDE. + +### C.3.4 TDD + +EVM covers the midamble (or for IMB the TDM pilot region) part as well as the data part; however PCDE disregards the midamble (or IMB TDM pilot) part. + +### C.3.5 Synch channel + +A node B signal contains a physical synch channel, which is non-orthogonal, related to the other DPCHs. In this context note: The code channel bearing the result of PCDE is exactly one of the DPCHs (never the synch channel). The origin of PCDE (erroneous code power) can be any DPCH and/or the synch channel. This means that the error due to the synch channel is projected onto the other (orthogonal) codes that make up the code domain. + +### C.3.6 Formula for the minimum process + +where + +L is the function to be minimised + +The parameters to be varied in order to minimize are: + +the RF frequency offset + +the timing offset + +the phase offset + +code power offsets (one offset for each code) + +the power offset of the midamble (or for IMB the TDM pilot region) + +the code power offset of the primary SCH + +the code power offsets of secondary SCHs, (i: 1,2,3) + +( and are only applied, if the timeslot under test contains the synchronisation channel.) + +$Z(v)$ Samples of the signal under Test + +$R(v)$ Samples of the reference signal + +counting index starting at the beginning of the measurement interval and ending at its end. + +$N$ No of chips during the measurement interval. + +$Z(v)$ : Samples of the signal under Test. It is modelled as a sequence of complex baseband samples $Z(\gamma)$ with a time-shift $\Delta t$ , a frequency offset $\Delta f$ , a phase offset $\Delta \varphi$ , the latter three with respect to the reference signal. + +$R(v)$ : Samples of the reference signal: + +where + +$g$ nominal gain of the code channel or midamble (or for IMB the TDM pilot region) + +The gain offset to be varied in the minimum process + +$Chip(v)$ is the chip sequence of the code channel or midamble (or for IMB the TDM pilot region) + +Indices at $g$ , $\Delta g$ and $Chip$ : The index indicates the code channel: + +$c = 1, 2, \dots$ No of code channels + +prim = primary SCH + +seci = three secondary SCHs, i:1,2,3 + +Range for $Chip_c$ : +1,-1 + +## C.3.7 Formula for EVM + +$Z'(\gamma)$ , $R'(\gamma)$ are the varied measured and reference signals. + +## Annex D (informative): Derivation of Test Requirements + +The Test Requirements in this specification have been calculated by relaxing the Minimum Requirements of the core specification using the Test Tolerances defined in subclause 5.11. When the Test Tolerance is zero, the Test Requirement will be the same as the Minimum Requirement. When the Test Tolerance is non-zero, the Test Requirements will differ from the Minimum Requirements, and the formula used for this relaxation is given in tables D.1 to D.3 + +Note that a formula for applying Test Tolerances is provided for all tests, even those with a test tolerance of zero. This is necessary in the case that the Test System uncertainty is greater than that allowed in subclause 5.10. In this event, the excess error shall be subtracted from the defined test tolerance in order to generate the correct tightened Test Requirements as defined in subclause 5.12. + +For example, a Test System having 0,9 dB accuracy for test 6.2 Maximum output power (which is 0,2 dB above the limit specified in subclause 5.10.2) would subtract 0,2 dB from the Test Tolerance of 0,7 dB defined in subclause 5.11.1. This new test tolerance of 0,5 dB would then be applied to the Minimum Requirement using the formula defined in Table D.1 to give a new range of $\pm 2,5$ dB of the manufacturer's rated output power. + +For the case where an excess error of 0.2 dB exists, when applied to a test with a test tolerance of zero, the test tolerance used in the formula would be -0.2 dB. + +**Table D.1: Derivation of Test Requirements (Transmitter tests)** + +| Test | Minimum Requirement in TS 25.105
(numbering of tables in the column below refers to TS 25.142) | Test Tolerance (TT) | Test Requirement in TS 25.142 | +|----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 6.2 Maximum output power | In normal conditions ...
within +2 dB and -2 dB of the manufacturer's rated output power

In extreme conditions...
within +2,5 dB and -2,5 dB of the manufacturer's rated output power | 0,7 dB | Formula: Upper limit + TT
Lower limit - TT

In normal conditions ...
within +2,7 dB and -2,7 dB of the manufacturer's rated output power

In extreme conditions...
within +3,2 dB and -3,2 dB of the manufacturer's rated output power | +| 6.3 Frequency stability | Frequency stability
Wide Area BS: $\pm 0,05$ ppm
Local Area BS: $\pm 0,1$ ppm | 12 Hz | Formula:
$\pm$ (frequency stability +TT)
Wide Area BS:
$\pm (0,05 \text{ ppm} + 12 \text{ Hz})$

Local Area BS:
$\pm (0,1 \text{ ppm} + 12 \text{ Hz})$ | +| 6.4.2 Power control steps | single step: step size tolerance specified in table 6.3

ten steps: minimum and maximum average rate of change in mean power specified in table 6.3 | single step:
0,1 dB

ten steps:
0,3 dB | Formula:
single step:
$\pm$ (step size tolerance + TT)

ten steps:
maximum average rate + TT
minimum average rate - TT

0,1 dB and 0,3 dB, respectively, applied as above to table 6.3 | +| 6.4.3 Power control dynamic range | range $\geq 30$ dB | 0,3 dB | Formula: Range - TT

range $\geq 29,7$ dB | +| 6.4.4 Minimum output power | PRAT - 30 dB | 0,7 dB | Formula :
PRAT - 30 dB +TT

PRAT - 29,3 dB | +| 6.4.5 Primary CCPCH power | PCCPCH power tolerance defined in table 6.8 | 0,8 dB | Formula:
$\pm$ (power tolerance + TT)

0,8 dB applied as above to table 6.8 | +| 6.4.6 Differential accuracy of Primary CCPCH power | Differential accuracy of PCCPCH power: $\leq \pm 0,5$ dB | 0,1 dB | Formula:
$\pm$ (PCPCH tolerance + TT)

$\pm 0,6$ dB | +| 6.5.1 Transmit OFF power | Tx OFF power limit $< -79$ dBm | 2,0 dB | Formula:
$< \text{Tx OFF power limit} + \text{TT}$

$< - 77$ dBm | + +| | | | | | +|------------|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 6.5.2 mask | Transmit ON/OFF time | Tx power limit:

3,84 Mcps TDD option:
< -33 dBm or -79 dBm, resp.

1,28 Mcps TDD option:
< -42 dBm or -82 dBm, resp. | < -33 dBm:
0,7 dB
< -79 dBm:
2,0 dB

< -42 dBm:
0,7 dB
< -82 dBm:
2,0 dB | Formula:
< Tx power limit + TT

for 3,84 Mcps TDD option:
< -32,3 dBm
or
< - 77 dBm

for 1,28 Mcps TDD option:
< -41,3 dBm
or
< -80 dBm | +| 6.6.1 | Occupied bandwidth | occupied bandwidth limit
3,84 Mcps TDD option: = 5 MHz
1,28 Mcps TDD option: 1,6 MHz | 0 kHz | Formula:
Occupied bandwidth limit + TT

3,84 Mcps TDD option: = 5 MHz
1,28 Mcps TDD option: 1,6 MHz | +| 6.6.2.1 | Spectrum emission mask | Maximum level defined in tables 6.13 to 6.16 | 1,5 dB | Formula: Maximum level + TT

Add 1,5 dB to Maximum level entries in tables 6.13 to 6.16 | + +| | | | | +|-----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 6.6.2.2 Adjacent Channel Leakage power Ratio (ACLR) |

3,84 Mcps TDD option:

minimum requirement:
ACLR limit = 45 dB at 5 MHz
ACLR limit = 55 dB at 10 MHz

requirement for operation in the same geographic area with unsynchronised TDD BS or FDD BS on adjacent channels:
Maximum Level defined in tables 6.23 and 6.23AA

requirement in case of co-siting with unsynchronised TDD BS or FDD BS operating on adjacent channels:
Maximum Level defined in tables 6.24 and 6.24A

1,28 Mcps TDD option:

minimum requirement:
ACLR limit = 40 dB at 1,6 MHz
ACLR limit = 45 dB at 3,2 MHz

requirement for operation in the same geographic area with unsynchronised TDD or FDD on adjacent channels:
Maximum Level defined in tables 6.23A, 6.23B and 6.23C

requirement in case of co-siting with unsynchronised TDD or FDD on an adjacent channel:
Maximum Level defined in tables 6.24B, 6.24C and 6.24D

|

3,84 Mcps TDD option:

min. req. : 0,8 dB

operation in the same geographic area:
4 dB (TBD in table 6.23A, 5 MHz offset, resp.) for Wide Area BS ; 0,8 dB for Local Area BS

co-siting:
TBD for Wide Area BS; 1 dB for Local Area BS

1,28 Mcps TDD option:

min. req. : 0,8 dB

operation in the same geographic area:
1 dB or 4 dB for the Wide Area BS; 0,8 dB for the Local Area BS

co-siting:
TBD for the Wide Area BS; 1 dB for the Local Area BS

|

Formula: ACLR limit - TT

3,84 Mcps TDD option:

min. requirement:
ACLR limit = 44,2 dB at 5 MHz
ACLR limit = 54,2 dB at 10 MHz

operation in the same geographic area:
Wide Area BS:
Add 4 dB (TBD in table 6.23A, 5 MHz offset, resp.) to the Maximum Level entries in tables 6.23 and 6.23AA.
Local Area BS:
Add 0,8 dB to the Maximum Level entries in tables 6.23 and 6.23AA.
co-siting:
Wide Area BS:
Add TBD to the Maximum Level entries in tables 6.24 and 6.24A.
Local Area BS:
Add 1 dB to the Maximum Level entries in tables 6.24 and 6.24A.

1,28 Mcps TDD option:

min. requirement:
ACLR limit = 39,2 dB at 1,6 MHz
ACLR limit = 44,2 dB at 3,2 MHz

operation in the same geographic area:
Wide Area BS:
Add 1 dB to the Maximum Level entries in tables 6.23A and 6.23B, and 4 dB to the Maximum Level entry in table 6.23C.
Local Area BS:
Add 0,8 dB to the Maximum Level entries in tables 6.23A, 6.23B and 6.23C.
co-siting:
Wide Area BS:
Add TBD to the Maximum Level entries in tables 6.24B, 6.24C and 6.24D.
Local Area BS:
Add 1 dB to the Maximum Level entries in tables 6.24B, 6.24C and 6.24D.

| +| 6.6.3 Spurious emissions | maximum level defined in tables 6.29 to 6.37 | 0 dB |

Formula: Maximum limit + TT

add 0 dB to maximum levels in tables 6.29 to 6.37

| + +| | | | | | +|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|--------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 6.7 | Transmit intermodulation (interferer requirements)

This tolerance applies to the stimulus and not the measurements defined in 6.6.2.1, 6.6.2.2 and 6.6.3. | Wanted signal level - interferer level = 30 dB | 0 dB | Formula: Ratio + TT

Wanted signal level - interferer level = 30 + 0 dB | +| 6.8.1 | Modulation accuracy | EVM limit = 12,5 % | 0 % | Formula: EVM limit + TT

EVM limit = 12,5 % | +| 6.8.2 | Peak code domain error | PCDE limit = - 28 dB | 1 dB | Formula: PCDE limit + TT

PCDE limit = - 27 dB | +| 6.8.3 | Relative Code Domain Error | RCDE limit = -21.9 dB | 1.0 dB | Formula: RCDE limit + TT

RCDE limit = -20.9 dB | +| 6.8.4 | Time alignment error in MIMO transmission | 1,28 Mcps TDD option:

Max time alignment error = 65 ns
Min time alignment error = - 65 ns | 1,28 Mcps TDD option:

[78] ns | Formula:
Max time alignment error + TT
Min time alignment error – TT

1,28 Mcps TDD option:
Max time alignment error = [143]ns
Min time alignment error = [-143]ns | + +**Table D.2: Derivation of Test Requirements (Receiver tests)** + +| Test | Minimum Requirement in TS 25.105
(numbering of tables in the column below refers to TS 25.142) | Test Tolerance (TT) | Test Requirement in TS 25.142 | +|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 7.2 Reference sensitivity | Reference sensitivity level
3,84 Mcps TDD option:
Wide Area BS: -109 dBm
Local Area BS: -95 dBm

1,28 Mcps TDD option:
Wide Area BS: -110 dBm
Local Area BS: -96 dBm

BER limit = 0,001 | 0,7 dB | Formula:
Reference sensitivity level + TT

Reference sensitivity level
3,84 Mcps TDD option:
Wide Area BS: -108,3 dBm
Local Area BS: -94,3 dBm

1,28 Mcps TDD option:
Wide Area BS: -110 dBm
Local Area BS: -95,3 dBm

BER limit is not changed | +| 7.3 Dynamic range | Wanted signal level =
+ 30 dB

Interfering AWGN level
3,84 Mcps TDD option:
Wide Area BS: -73 dBm/3,84 MHz
Local Area BS: -59 dBm/3,84 MHz

1,28 Mcps TDD option:
Wide Area BS: -76 dBm/1,28 MHz
Local Area BS: -62 dBm/1,28 MHz | 1,2 dB | Formula:
Wanted signal level + TT
AWGN level unchanged

Wanted signal level =
+ 31,2 dB | +| 7.4 Adjacent Channel Selectivity (ACS) | Wanted signal level =
Ref. sensitivity level + 6 dB

Interfering signal level
3,84 Mcps TDD option:
Wide Area BS: -52 dBm/3,84 MHz
Local Area BS: -38 dBm/3,84 MHz

1,28 Mcps TDD option:
Wide Area BS: -55 dBm/1,28 MHz
Local Area BS: -41 dBm/1,28 MHz | 0 dB | Formula:
Wanted signal level + TT
Interfering signal level unchanged

Wanted signal level =
Ref. sensitivity level + 6 dB | +| 7.5 Blocking characteristics | Wanted signal level =
+ 6 dB

3,84 Mcps TDD option:
Interfering signal level see tables 7.6 to 7.10

1,28 Mcps TDD option:
Interfering signal level see tables 7.6A to 7.10A | 0 dB | Formula:
Wanted signal level + TT
Interfering signal level unchanged

Wanted signal level =
+ 6 dB | +| 7.6 Intermodulation characteristics | Wanted signal level =
+ 6 dB

Interferer1 level (10 MHz offset CW for 3,84 Mcps TDD option; 3,2 MHz offset CW for 1,28 Mcps TDD option)) = -48 dBm

Interferer2 level (20 MHz offset W-CDMA Modulated for 3,84 Mcps TDD option; 6,4 Mcps offset W-CDMA Modulated for 1,28 Mcps TDD option)) = -48 dBm | 0 dB | Formula:
Wanted signal level + TT

Interferer 1 level: unchanged
Interferer 2 level: unchanged

Wanted signal level =
+ 6 dB | + +| | | | | | +|------------------|----------|-------------------------------------|------|--------------------------------------------------------------------------| +| 7.7
emissions | Spurious | Maximum level defined in table 7.12 | 0 dB | Formula: Maximum level + TT

Add TT to maximum level in table 7.12 | +|------------------|----------|-------------------------------------|------|--------------------------------------------------------------------------| + +**Table D.3: Derivation of Test Requirements (Performance requirements)** + +| Test | Minimum Requirement in TS 25.105 | Test Tolerance (TT) | Test Requirement in TS 25.142 | +|---------------------------------------------------------|----------------------------------|---------------------|-------------------------------| +| 8.2 Demodulation in static propagation conditions | | TBD | | +| 8.3 Demodulation of DCH in multipath fading conditions | | TBD | | +| 8.3A Demodulation of DCH in high speed train conditions | Received value | 0.4dB | Minimum requirement + TT | + +## Annex E (informative): Acceptable uncertainty of Test Equipment + +This informative annex specifies the critical parameters of the components of an overall Test System (e.g. Signal generators, Signal Analysers etc.) which are necessary when assembling a Test System which complies with subclause 5.10 Acceptable Uncertainty of Test System. These Test Equipment parameters are fundamental to the accuracy of the overall Test System and are unlikely to be improved upon through System Calibration. + +**Table E.1: Equipment accuracy for transmitter measurements** + +| Test | | Equipment accuracy | Range over which equipment accuracy applies | +|---------|----------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------| +| 6.2 | Maximum output power | Not critical | Not critical | +| 6.3 | Frequency stability | $\pm 10$ Hz + timebase = 12 Hz | Measurements in the range $\pm 500$ Hz. | +| 6.4.2 | Power control steps | single step: $\pm 0,1$ dB
ten steps: $\pm 0,3$ dB | Pmax to Pmax - 30 dB | +| 6.4.3 | Power control dynamic range | $\pm 0,3$ dB | Pmax to Pmax - 30 dB | +| 6.4.4 | Minimum output power | Not critical | Pmax to Pmax - 30 dB | +| 6.4.5 | Primary CCPCH power | Not critical | Not critical | +| 6.4.6 | Differential accuracy of Primary CCPCH power | $\pm 0,1$ dB | | +| 6.5.1 | Transmit OFF power | Not critical | Not critical | +| 6.5.2 | Transmit ON/OFF time mask | Not critical | Not critical | +| 6.6.1 | Occupied bandwidth | $\pm 100$ kHz | $\pm 1$ MHz of the minimum requirement | +| 6.6.2.1 | Spectrum emission mask | Not critical | Not critical | +| 6.6.2.2 | ACLR | minimum requirement: $\pm 0,8$ dB
requirement in case of operation in proximity: $\pm 4,0$ dB
requirement in case of co-siting: TBD | Measurements in the range $\pm 3$ dB of the minimum requirement at signal power = Pmax | +| 6.6.3 | Spurious emissions | Not critical | Not critical | +| 6.7 | Transmit intermodulation (interferer requirements) | Not critical | Not critical | +| 6.8.1 | Modulation accuracy | $\pm 2,5$ %
(for single code) | Specified accuracy applies to measurement results between $\pm 7,5$ % and 17,5% at signal power = Pmax to Pmax - 30 dB | +| 6.8.2 | Peak code domain error | $\pm 1$ dB | Measurements in the range -25 dB to -30 dB at signal power = Pmax | +| 6.8.3 | Relative Code Domain Error | $\pm 1,0$ dB | Measurements in the range -18.9 to -24.9 dB at signal power = Pmax | +| 6.8.4 | Time alignment error in MIMO transmission | 1,28 Mcps TDD option: $\pm [78]$ ns | | + +**Table E.2: Equipment accuracy for receiver measurements** + +| Subclause | | Equipment accuracy | Range over which equipment accuracy applies | +|-----------|---------------------------------|--------------------|---------------------------------------------| +| 7.2 | Reference sensitivity level | Not critical | Not critical | +| 7.3 | Dynamic range | Not critical | Not critical | +| 7.4 | Adjacent channel selectivity | Not critical | Not critical | +| 7.5 | Blocking characteristics | Not critical | Not critical | +| 7.6 | Intermodulation characteristics | Not critical | Not critical | +| 7.7 | Spurious Emissions | Not critical | Not critical | + +**Table E.3: Equipment accuracy for performance measurements** + +| Subclause | Equipment accuracy | Range over which equipment accuracy applies | +|---------------------------------------------------------|---------------------------|----------------------------------------------------| +| 8.2 Demodulation in static propagation conditions | Not critical | Not critical | +| 8.3 Demodulation of DCH in multipath fading conditions | Not critical | Not critical | +| 8.3A Demodulation of DCH in high speed train conditions | Not critical | Not critical | + +--- + +## Annex F (normative): General rules for statistical testing + +### F.1 Statistical testing of receiver BER/BLER performance + +#### F.1.1 Error Definition + +Bit Error Ratio (BER) and Block Error Ratio (BLER) are defined in section 3.1. + +#### F.1.2 Test Method + +Each test is performed in the following manner: + +- a) Setup the required test conditions. +- b) Record the number of samples tested and the number of occurred events (bit error or block error) +- c) Stop the test at a stop criterion which is minimum test time or an early pass or an early fail event. +- d) Once the test is stopped decide according to the pass fail decision rules ( subclause F.1.7) + +#### F.1.3 Test Criteria + +The test shall fulfil the following requirements: + +- a) good pass fail decision + - 1) to keep reasonably low the probability (risk) of passing a bad unit for each individual test; + - 2) to have high probability of passing a good unit for each individual test; +- b) good balance between test time and statistical significance + - 3) to perform measurements with a high degree of statistical significance; + - 4) to keep the test time as low as possible. + +#### F.1.4 Calculation assumptions + +##### F.1.4.1 Statistical independence + +- a) It is assumed, that error events are rare ( $\lim \text{BER BLER} \ll 0$ ) independent statistical events. However the memory of the convolutional /turbo coder is terminated after oneTTI. Samples and errors are summed up everyTTI. So the assumption of independent error events is justified. +- b) In the BLER test with fading there is the memory of the multipath fading channel which interferes the statistical independence. A minimum test time is introduced to average fluctuations of the multipath fading channel. So the assumption of independent error events is justified approximately. + +##### F.1.4.2 Applied formulas + +The formulas, applied to describe the BER BLER test, are based on the following experiments: + +- 1) After having observed a certain number of errors (**ne**) the number of samples are counted to calculate BER BLER. Provisions are made (note 1) such that the complementary experiment is valid as well: +- 2) After a certain number of samples (**ns**) the number of errors, occurred, are counted to calculate BER BLER. + +Experiment 1) stipulates to use the following Chi Square Distribution with degree of freedom ne: + +$$2 \cdot \text{dchisq}(2 \cdot \text{NE}, 2 \cdot \text{ne}).$$ + +Experiment 2) stipulates to use the Poisson Distribution: + +$$\text{dpois}(\text{ne}, \text{NE})$$ + +(NE: mean of the distribution) + +To determine the early stop conditions, the following inverse cumulative operation is applied: + +$$0.5 * \text{qchisq}(D, 2 * \text{ne}). \text{ This is applicable for experiment (1) and (2).}$$ + +D: wrong decision risk per test step + +Note: other inverse cumulative operations are available, however only this is suited for experiment (1) and (2). + +### F.1.4.3 Approximation of the distribution + +The test procedure is as follows: + +During a running measurement for a BS ns (number of samples) and ne (number of errors) are accumulated and from this the preliminary BER BLER is calculated. Then new samples up to the next error are taken. The entire past and the new samples are basis for the next preliminary BER BLER. Depending on the result at every step, the BS can pass, can fail or must continue the test. + +As early pass- and early fail-BSs leave the statistical totality under consideration, the experimental conditions are changed every step resulting in a distribution that is truncated more and more towards the end of the entire test. Such a distribution can not any more be handled analytically. The unchanged distribution is used as an approximation to calculate the early fail and early pass bounds. + +### F.1.5 Definition of good pass fail decision + +This is defined by the probability of wrong decision F at the end of the test. The probability of a correct decision is 1-F. + +The probability (risk) to fail a good DUT shall be $\leq F$ according to the following definition: The failed DUT is still better than the specified error ratio (Test requirement) with a probability of $\leq F$ . + +The probability to pass a bad DUT shall be $\leq F$ according to the following definition: The passed DUT is still worse than M times the specified error ratio ( $M > 1$ is the bad DUT factor) with a probability of $\leq F$ . + +This definitions lead to an early pass and an early fail limit: + +Early fail: $\text{ber} \geq \text{berlim}_{\text{fail}}$ + +$$(1)$$ + +For $\text{ne} \geq 7$ + +Early pass: $\text{ber} \leq \text{berlimbad}_{\text{pass}}$ + +$$(2)$$ + +For $\text{ne} \geq 1$ + +With + +ber (normalized BER,BLER): BER,BLER according to F.1.1 divided by Test requirement + +D: wrong decision probability for a test step . This is a numerically evaluated fraction of F, the wrong decision probability at the end of the test. See table F.1. + +ne: Number of error events + +M: bad DUT factor see table F.1. + +qchisq: inverse-cumulative-function of the chi-squared-distribution + +## F.1.6 Good balance between test time and statistical significance + +Three independent test parameters are introduced into the test and shown in Table F.1. These are the obvious basis of test time and statistical significance. From the first two of them four dependent test parameters are derived. The third independent test parameter is justified separately. + +**Table F.1: independent and dependant test parameters** + +| Independent parameters | | | Dependant parameters | | | +|-------------------------------------------------|--------------------------|------------------|---------------------------------------------------------|------------------------------------------|-------------------------------| +| Test Parameter | Value | Reference | Test parameter | Value | Reference | +| Bad DUT factor M | 1.5 | Tables F.4 & F.5 | Early pass/fail condition | Curves | Subclause F.1.5
Figure F.1 | +| Final probability of wrong pass/fail decision F | 0.2%,
(0.02%, note 2) | Subclause F.1.5 | Target number of error events | 345 | Table F.4 & F.5 | +| | | | Probability of wrong pass/fail decision per test step D | 0.0085%,
(0.0008% and 0.008%, note 2) | | +| | | | Test limit factor TL | 1.234 | Table F.4 & F.5 | +| Minimum test time | | Tables F.2 & F.3 | | | | + +The minimum test time is derived from the following justification: + +- 1) For no propagation conditions and static propagation condition + +No early fail calculated from fractional number of errors <1 (see note 1) + +- 2) For multipath fading condition + +No stop of the test until [990] wavelengths are crossed during relevant BS reception timeslots, relevant for BER BLER testing, with the speed given in the fading profile. + +- 3) For high speed train condition + +Scenario 1: 82.3s. This corresponds to 4 complete cycles of approach towards and departure leave to and from a BS antenna + +Scenario 3: 28.8s. This corresponds to 4 complete cycles of approach towards and departure from a BS antenna + +**Table F.2: minimum Test time** + +| Fading profile | Minimum test time | +|--------------------------------------------------------------------------------------------------------------|--------------------| +| Multipath propagation 3 km/h | [164 s*TSPF/TSRX] | +| Multipath propagation 120 km/h | [4.1 s* TSPF/TSRX] | +| High speed train conditions
Scenario 1 | 82.3 sec | +| High speed train conditions
Scenario 3 | 28.8 sec | +| TSPF = Time slots per frame
TSRX = relevant reception timeslots per frame, relevant for the BER BLER test | | + +TSPF and TSRX form the prolongation factor and depend on the user data rate and the TDD Option (3,84 Mchip/s or 1,28 Mchip/s ) + +**Table F.3: Prolongation factor for minimum Test time** + +| User Data rate | TSPF/TSRX for TDD 3,84 Mchip/s | TSPF/TSRX for TDD 1,28 Mchip/s | +|----------------|--------------------------------|--------------------------------| +| 12.2 kbit/s | 15/1 | 7/1 | +| 64 kbit/s | 15/1 | 7/1 | +| 144 kbit/s | 15/1 | 7/2 | +| 384 kbit/s | 15/3 | 7/4 | + +In tables F.4 and F.5 the minimum test time is converted in minimum number of samples. + +## F.1.7 Pass fail decision rules + +No decision is allowed before the minimum test time is elapsed. + +- 1) If minimum Test time < time for target number of error events then the following applies: The required confidence level 1-F (= correct decision probability) shall be achieved. This is fulfilled at an early pass or early fail event. + +### For BER: + +For every TTI (Transmit Time Interval) sum up the number of bits (ns) and the number of errors (ne) from the beginning of the test and calculate + +BER1 (including the artificial error at the beginning of the test (Note 1)) and + +BER0 (excluding the artificial error at the beginning of the test (Note 1)). + +If BER0 is above the early fail limit, fail the DUT. + +If BER1 is below the early pass limit, pass the DUT. + +Otherwise continue the test + +### For BLER: + +For every TTI sum up the number of blocks (ns) and the number of erroneous blocks (ne) from the beginning of the test and calculate + +BLER1 (including the artificial error at the beginning of the test (Note 1)) and + +BLER0 (excluding the artificial error at the beginning of the test (Note 1)). + +If BLER1 is below the early pass limit, pass the DUT. + +If BLER0 is above the early fail limit, fail the DUT. + +Otherwise continue the test + +- 2) If the minimum test time ≥ time for target error events, then the test runs for the minimum test time and the decision is done by comparing the result with the test limit. + +### For BER: + +For every TTI (Transmit Time Interval) sum up the number of bits (ns) and the number of errors (ne) from the beginning of the test and calculate BER0 + +### For BLER: + +For every TTI sum up the number of blocks (ns) and the number of erroneous blocks (ne) from the beginning of the test and calculate BLER0 + +If BER0/BLER0 is above the test limit, fail the DUT. + +If BER0/BLER0 is on or below the test limit, pass the DUT. + +## F.1.8 Test conditions for BER,BLER Tests + +Table F.4: Test conditions for BER tests + +| Type of test (BER) | Propagation conditions | Test requirement (BER) | Test limit (BER)= Test requirement (BER)x TL | Target number of error events (time) Note * | Minimum number of samples | Prob that good unit will fail = Prob that bad unit will pass (%) | Bad unit BER factor M | +|------------------------------------------------|------------------------|------------------------|----------------------------------------------|---------------------------------------------|---------------------------|------------------------------------------------------------------|-----------------------| +| Reference Sensitivity Level | - | 0.001 | 1.234 | 345 (22.9s) | Note 1 | 0.2 | 1.5 | +| Dynamic Range | - | 0.001 | 1.234 | 345 (22.9s) | Note 1 | 0.2 | 1.5 | +| Adjacent Channel Selectivity | - | 0.001 | 1.234 | 345 (22.9s) | Note 1 | 0.2 | 1.5 | +| Blocking Characteristics Pass condition Note 2 | - | 0.001 | 1.251 | 402 (26.3s) | Note 1 | 0.2 | 1.5 | +| Blocking Characteristics Fail condition Note 2 | - | 0.001 | 1.251 | 402 (26.3s) | Note 1 | 0.02 | 1.5 | +| Intermodulation Characteristics | - | 0.001 | 1.234 | 345 (22.9s) | Note 1 | 0.2 | 1.5 | + +Note \*: the time in the bracket means the reception time + +Table F.5: Test conditions for BLER tests + +| Type of test (BLER) | Information Bit rate (kbit/s) | Test requirement (BLER) | Test limit (BLER)= Test requirement (BLER)x TL | Target number of error events (time) | Minimum number of samples (time) TDD 3,84 Mchip/s | Minimum number of samples (time) TDD 1,28 Mchip/s | Prob that bad unit will pass = Prob that good unit will fail (%) | Bad unit BLER factor M | | +|----------------------------------------------------------------------------------------|-------------------------------|---------------------------------------------------|------------------------------------------------|----------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|------------------------------------------------------------------|------------------------|-----| +| Demodulation in Static Propagation conditions | 12.2
64
144
384 | 0.01
0.1
0.01
0.1
0.01
0.1
0.01 | 1.234 | 345
(559s)
(55.9s)
(559s)
(55.9s)
(559s)
(28s)
(280s) | Note1 | Note1 | 0.2 | 1.5 | | +| Demodulation of DCH in Multi-path Fading Propagation conditions 3km/h (Case 1, Case 2) | 12.2
64
144
384 | 0.01
0.1
0.01
0.1
0.01
0.1
0.01 | 1.234 | 345
(559s)
(55.9s)
(559s)
(55.9s)
(559s)
(28s)
(280s) | [(2460s)]
[123000]
[(123000)]
[123000]
[(123000)]
[123000]
[(820s)]
[82000]
[82000] | [(1148s)]
[5740]
[5740]
[5740]
[(574s)]
[2870]
[2870]
[(278s)]
[27800]
[27800] | | 0.2 | 1.5 | +| Demodulation of DCH in Multi-path Fading Propagation conditions 120 km/h (Case3) | 12.2
64
144
384 | 0.01
0.1
0.01
0.1
0.01
0.1
0.01 | 1.234 | 345
(559s)
(55.9s)
(559s)
(55.9s)
(559s)
(28s)
(280s) | [(61.5s)]
[3075]
[3075]
[3075]
[3075]
[3075]
[(20.5s)]
[2050]
[2050] | [(28.7s)]
[1435]
[1435]
[1435]
[(14.35s)]
[718]
[718]
[(7.175s)]
[718]
[718] | | 0.2 | 1.5 | +| Demodulation of DCH in high speed train condition | 12.2
64 | 0.01
0.1
0.01 | 1.234 | 345
(559s)
(55.9s)
(559s) | | Scenario 1
(82.3s)
4115
Scenario 3
(28.8s)
1440 | 0.2 | 1.5 | | + +## F.1.9 Practical Use (informative) + +See figure F.1: + +- The early fail limit represents formula (1) in F.1.5. The range of validity is $n_e \geq 7$ ( $\geq 8$ in case of blocking test) to $n_e = 345$ +- The early pass limit represents formula (2) in F.1.5. The range of validity is $n_e = 1$ to $n_e = 345$ . See note 1 +- The intersection co-ordinates of both curves are : target number of errors $n_e = 345$ and test limit $TL = 1.234$ . +- The range of validity for $TL$ is $n_e > 345$ . + +A typical BER BLER test, calculated from the number of samples and errors (F.1.2.(b)) using experimental method (1) or (2) (see F.1.4.2 calculation assumptions) runs along the yellow trajectory. With an errorless sample the trajectory goes down vertically. With an erroneous sample it jumps up right. The tester checks if the BER BLER test intersects the early fail or early pass limits. The real time processing can be reduced by the following actions: + +$BLER_0$ (excluding the artificial error at the beginning of the test (Note 1)). is calculated only in case of an error event. + +$BER_0$ (excluding the artificial error at the beginning of the test (Note 1)). is calculated only in case of an error event within a TTI. + +So the early fail limit cannot be missed by errorless samples. + +The check against the early pass limit may be done by transforming formula (2) in F.1.5 such that the tester checks against a Limit-Number-of-samples ( $NL(ne)$ ) depending on the current number of errors (including the artificial error at the beginning of the test (Note 1)). + +Early pass if + +TR: test requirement (0.001) + +![Figure F.1: A log-log plot showing the relationship between BER (normalised to test requirement) on the y-axis and the number of errors (ne) on the x-axis. The y-axis ranges from 0.1 to 10, and the x-axis ranges from 1 to 1000. The plot is divided into four regions: 'continue' (yellow), 'early fail' (pink), 'fail' (purple), and 'pass' (cyan). A red curve represents the 'early fail' limit, and a black curve represents the 'test limit'. A horizontal line at y=1 represents the 'test requirement'. A dashed orange line represents the 'BER trajectory'. A legend on the left shows 'berlim_fail(ne, D)' as a red line, 'berlimbad_pass(ne, D)' as a black line, 'M' as a horizontal line, 'TL' as a horizontal line, and '1' as a horizontal line.](db4df156e75d1e433a48c718d5d219a2_img.jpg) + +Figure F.1: A log-log plot showing the relationship between BER (normalised to test requirement) on the y-axis and the number of errors (ne) on the x-axis. The y-axis ranges from 0.1 to 10, and the x-axis ranges from 1 to 1000. The plot is divided into four regions: 'continue' (yellow), 'early fail' (pink), 'fail' (purple), and 'pass' (cyan). A red curve represents the 'early fail' limit, and a black curve represents the 'test limit'. A horizontal line at y=1 represents the 'test requirement'. A dashed orange line represents the 'BER trajectory'. A legend on the left shows 'berlim\_fail(ne, D)' as a red line, 'berlimbad\_pass(ne, D)' as a black line, 'M' as a horizontal line, 'TL' as a horizontal line, and '1' as a horizontal line. + +Figure F.1 + +NOTE 1: At the beginning of the test, an artificial error is introduced. This ensures that an ideal DUT meets the valid range of the early pass limit. In addition this ensures that the complementary experiment (F.1.4.2 bullet point (2)) is applicable as well. + +For the check against the early fail limit the artificial erroneous sample, introduced at the beginning of the test, is disregarded. + +Due to the nature of the test, namely discrete error events, the early fail condition shall not be valid, when fractional errors $< 1$ are used to calculate the early fail limit: Any early fail decision is postponed until number of errors $ne \geq 7$ . In the blocking test any early fail decision is postponed until number of errors $ne \geq 8$ . + +NOTE 2: $F=0.2\%$ is intended to be used for a test containing a few BER/BLER tests (e.g. receiver sensitivity is repeated 12 times(3 RF Channels \* 2 Power-supplies \* 2 Temperatures). For a test containing many BER/BLER tests (e.g. blocking test) this value is not appropriate for a single BER/BLER test. + +The blocking test contains approx. 12750 single BER tests. A DUT on the limit will fail approx. 25 to 26 times due to statistical reasons using wrong decision probability at the end of the test $F=0.2\%$ . This shall be solved by the following rule: + +All passes (based on $F=0.2\%$ ) are accepted, including the wrong decisions due to statistical reasons. + +An early fail limit based on $F=0.02\%$ instead of $0.2\%$ is established. That ensures that wrong decisions due to statistical reasons are reduced to 2 to 3 in 12750 BER measurements. If the fail cases are $\leq 12$ , it is allowed to repeat each fail cases 1 time before the final verdict. + +These asymmetric test conditions ensure that a DUT on the limit consumes hardly more test time for a blocking test than in the symmetric case and reduces the wrong decision probability considerably and on the other hand the repetition allowance sufficiently suppresses the residual statistically caused wrong verdict for the aggregate test. + +--- + +## Annex G (informative): Change History + +**Table G.1: Change History** + +| TSG | Doc | CR | R | Title | Cat | Curr | New | Work Item | +|-------|-----------|------|---|-----------------------------------------------------------------------------------------------|-----|-------|-------|------------------------| +| RP-29 | | | | Rel-7 version created based on v6.3.0 | | | 7.0.0 | | +| RP-29 | RP-050579 | 0176 | | Introduction of UMTS 2.6 GHz operating band for TDD | B | 6.2.0 | 7.0.0 | RInImp-UMTS2600 TDD | +| RP-29 | RP-050579 | 0177 | | UMTS 2.6 GHz TDD Propagation Conditions | B | 6.2.0 | 7.0.0 | RInImp-UMTS2600 TDD | +| RP-29 | RP-050579 | 0178 | 2 | Channel Raster for 3,84 Mcps TDD in UMTS 2.6 GHz | B | 6.2.0 | 7.0.0 | RInImp-UMTS2600 TDD | +| RP-29 | RP-050579 | 0179 | | UMTS 2.6 GHz TDD BS Transmitter Specifications | B | 6.2.0 | 7.0.0 | RInImp-UMTS2600 TDD | +| RP-29 | RP-050579 | 0180 | | UMTS 2.6 GHz TDD BS Receiver Specifications | B | 6.2.0 | 7.0.0 | RInImp-UMTS2600 TDD | +| RP-29 | RP-050579 | 0181 | | Introduction of Propagation Conditions for UMTS 2.6 GHz for 1,28Mcps TDD | B | 6.2.0 | 7.0.0 | RInImp-UMTS2600 TDD | +| RP-29 | RP-050579 | 0182 | | UMTS 2.6 GHz TDD BS receiver spurious emission | B | 6.2.0 | 7.0.0 | RInImp-UMTS2600 TDD | +| RP-30 | RP-050740 | 0183 | | Introduction of UMTS 2.6 BS transmitter specification for 1,28Mcps TDD | B | 7.0.0 | 7.1.0 | RInImp-UMTS2600 TDD | +| RP-30 | RP-050740 | 0184 | | Introduction of UMTS 2.6 BS receiver specification for 1,28Mcps TDD | B | 7.0.0 | 7.1.0 | RInImp-UMTS2600 TDD | +| RP-30 | RP-050841 | 0186 | | Name correction of logical and transport channels in Annex 2 | A | 7.0.0 | 7.1.0 | TEI6 | +| RP-32 | RP-060307 | 0187 | | UMTS 2.6 GHz blocking and spurious emission test condition | F | 7.1.0 | 7.2.0 | RInImp-UMTS2600 TDD | +| RP-32 | RP-060312 | 0188 | 1 | 7.68 Mcps Frequency Band & Channel Arrangement | B | 7.1.0 | 7.2.0 | VHCR TDD-RF | +| RP-32 | RP-060312 | 0189 | | 7.68 Mcps Transmitter Characteristics | B | 7.1.0 | 7.2.0 | VHCR TDD-RF | +| RP-32 | RP-060312 | 0190 | 1 | 7.68 Mcps Receiver Characteristics | B | 7.1.0 | 7.2.0 | VHCR TDD-RF | +| RP-32 | RP-060312 | 0191 | | 7.68 Mcps - Channel Performance | B | 7.1.0 | 7.2.0 | VHCR TDD-RF | +| RP-32 | RP-060312 | 0192 | | 7.68 Mcps Measurement Channels & Propagation Conditions | B | 7.1.0 | 7.2.0 | VHCR TDD-RF | +| RP-33 | RP-060517 | 0205 | | Clarification of Tx spurious emission level from 3,84 Mcps and 7.68 Mcps TDD BS into PHS band | F | 7.2.0 | 7.3.0 | TEI7 | +| RP-33 | RP-060518 | 0212 | 1 | Clarification on the deployment of UTRA TDD in Japan | A | 7.2.0 | 7.3.0 | TEI | +| RP-33 | RP-060519 | 0214 | 1 | Tx and Rx Spurious Emission from 3,84 Mcps and 7.68 Mcps TDD BS into FDD bands in Japan | A | 7.2.0 | 7.3.0 | TEI6 | +| RP-33 | RP-060528 | 0206 | | Performance requirements for 3,84 Mcps E-DCH channel. | B | 7.2.0 | 7.3.0 | EDCH TDD-RF | +| RP-33 | RP-060526 | 0207 | 2 | 7.68 Mcps Operations in 2.6 GHz band | B | 7.2.0 | 7.3.0 | RInImp-UMTS26V HCR TDD | +| RP-34 | RP-060818 | 0215 | | Performance requirements for 7.68 Mcps E-DCH channel. | B | 7.3.0 | 7.4.0 | TEI7 | +| RP-35 | RP-070081 | 0219 | | HS-SICH detection performance test specification for 1,28Mcps TDD | A | 7.4.0 | 7.5.0 | TEI6 | +| RP-35 | RP-070082 | 0216 | | Tx and Rx Spurious Emission from 7.68 Mcps TDD BS into FDD band in Japan | F | 7.4.0 | 7.5.0 | TEI7 | +| RP-35 | RP-070082 | 0217 | | Clarification on the deployment of UTRA TDD in Japan | F | 7.4.0 | 7.5.0 | TEI7 | +| RP-36 | RP-070369 | 0225 | | Modifying category B spurious emission limits for UTRA TDD BS | A | 7.5.0 | 7.6.0 | TEI | +| RP-36 | RP-070377 | 0221 | | Adding test case of E-DCH performance requirement for 1,28Mcps TDD option | F | 7.5.0 | 7.6.0 | LCRTDD-EDCH-RF | + +| | | | | | | | | | +|-------|-----------|------|---|--------------------------------------------------------------------------------------------------------|---|-------|--------|-----------------------| +| RP-37 | RP-070651 | 0227 | | 7.68 Mcps TDD Option test tolerances and transmit ON/OFF time mask level. | F | 7.6.0 | 7.7.0 | TEI7 | +| RP-37 | RP-070651 | 0226 | | Inclusion of 7.68 Mcps in the scope of document | F | 7.6.0 | 7.7.0 | TEI7 | +| RP-39 | RP-080119 | 0229 | 1 | Correcting the power allocation for HS-SICH performance detection | A | 7.7.0 | 7.8.0 | TEI6 | +| RP-40 | RP-080329 | 0234 | | RCDE for 1.28Mcps TDD 64QAM modulated codes | B | 7.8.0 | 7.9.0 | RANimp-64 Qam1.28T DD | +| RP-40 | RP-080384 | 0233 | 1 | UMTS2300MHz propagation channel model addition for 1.28Mcps TDD in 25.142 | B | 7.9.0 | 8.0.0 | RlnImp8-UMTS2300 TDD | +| RP-40 | RP-080384 | 0232 | 1 | UMTS2300MHz Receiver performance addition for 1.28Mcps TDD in 25.142 | B | 7.9.0 | 8.0.0 | RlnImp8-UMTS2300 TDD | +| RP-40 | RP-080384 | 0231 | 1 | UMTS2300MHz Transmitter performance addition for 1.28Mcps TDD in 25.142 | B | 7.9.0 | 8.0.0 | RlnImp8-UMTS2300 TDD | +| RP-40 | RP-080384 | 0230 | 1 | UMTS2300MHz New band introduction for 1.28Mcps TDD in 25.142 | B | 7.9.0 | 8.0.0 | RlnImp8-UMTS2300 TDD | +| RP-41 | RP-080636 | 0236 | 1 | Modify the Fixed Reference Channels of E-DCH for LCR TDD | A | 8.0.0 | 8.1.0 | TEI7 | +| RP-43 | RP-090166 | 0241 | | Correction of BS reference measurement channel and performance requirement for LCR TDD 384kbps service | A | 8.1.0 | 8.2.0 | TEI4 | +| RP-43 | RP-090197 | 0242 | | Introduction of band 1880MHz for 25.142 | F | 8.1.0 | 8.2.0 | RlnImp9-UMTS1880 TDD | +| RP-43 | RP-090197 | 0243 | | UMTS1880MHz: transmitter characteristic | F | 8.1.0 | 8.2.0 | RlnImp9-UMTS1880 TDD | +| RP-43 | RP-090197 | 0244 | | UMTS1880MHz: receiver characteristic and propagation conditions | F | 8.1.0 | 8.2.0 | RlnImp9-UMTS1880 TDD | +| RP-44 | RP-090553 | 0247 | | Correction of local area base station coexistence requirements | F | 8.2.0 | 8.3.0 | RlnImp9-UMTS1880 TDD | +| RP-44 | RP-090554 | 0245 | 1 | Addition of Time alignment error test for BS supporting 1.28Mcps TDD MIMO | F | 8.2.0 | 8.3.0 | RANimp-LCRMIMO | +| RP-44 | RP-090556 | 0246 | | Correction on the test parameter table of E-DCH for 1.28Mcps TDD | F | 8.2.0 | 8.3.0 | TEI8 | +| RP-45 | RP-090818 | 251 | | Changes to 25.142 accommodating IMB | F | 8.3.0 | 8.4.0 | MSBFN-DOB | +| RP-46 | RP-091285 | 255 | | BS test requirements in high speed train condition for LCR TDD | B | 8.5.0 | 9.0.0 | RlnImp9-LCRTDD350 | +| RP-47 | RP-100257 | 260 | | Correction of E-DCH FRC3 for LCR TDD | A | 9.0.0 | 9.1.0 | TEI7 | +| RP-47 | RP-100253 | 262 | | Protection of E-UTRA for UTRA TDD BS | A | 9.0.0 | 9.1.0 | LTE-RF | +| RP-47 | RP-100273 | 257 | | Additional BS test requirements in high speed train conditions for LCR TDD | F | 9.0.0 | 9.1.0 | RlnImp9-LCRTDD350 | +| RP-48 | RP-100631 | 263 | 1 | Corrections for performance requirements in HST condition | F | 9.1.0 | 9.2.0 | TEI9 | +| RP-49 | RP-100922 | 264 | 1 | Clarification on applicability of requirements for multi-carrier BS | F | 9.2.0 | 9.3.0 | RlnImp9-RFmulti | +| RP-50 | RP-101340 | 275 | | Addition of test case for HS-SICH type2 performance | A | 9.3.0 | 9.4.0 | TEI8 | +| RP-50 | RP-101340 | 277 | | Clarifications of Base Station transmit and receive configurations | A | 9.3.0 | 9.4.0 | TEI8 | +| RP-50 | RP-101351 | 267 | 1 | Introduction of the BS requirements for 1.28Mcps TDD MC-HSUPA | B | 9.4.0 | 10.0.0 | TDD_MC_H SUPA | +| RP-50 | RP-101352 | 269 | | 1.28Mcps TDD Home NodeB class into Base Station class in 25.142 | B | 9.4.0 | 10.0.0 | HNB_LCRT DD_RF-Perf | +| RP-50 | RP-101352 | 270 | | 1.28Mcps TDD Home NodeB Transmitter | B | 9.4.0 | 10.0.0 | HNB_LCRT DD_RF-Perf | +| RP-50 | RP-101352 | 271 | | 1.28Mcps TDD Home NodeB Receiver | B | 9.4.0 | 10.0.0 | HNB_LCRT DD_RF-Perf | + +| | | | | | | | | | +|-------|-----------|------|---|---------------------------------------------------------------------------------------------|---|--------|--------|-----------------------------| +| RP-50 | RP-101352 | 272 | | 1.28Mcps TDD Home NodeB Demodulation Requirement | B | 9.4.0 | 10.0.0 | HNB_LCRT
DD_RF-Perf | +| RP-51 | RP-110352 | 0278 | - | Adding missing demodulation requirements for LCR TDD Home BS | F | 10.0.0 | 10.1.0 | TEI10 | +| RP-51 | RP-110352 | 0279 | 1 | Harmonization of co-existence/co-location requirements between 25.142 and 36.141 | F | 10.0.0 | 10.1.0 | TEI10 | +| RP-52 | RP-110796 | 280 | | Correction of co-existence requirement for UTRA TDD | F | 10.1.0 | 10.2.0 | TEI10 | +| RP-52 | RP-110796 | 281 | | Correction of the test port description for TS 25.142 | F | 10.1.0 | 10.2.0 | TEI10 | +| RP-53 | RP-111262 | 282 | | Clarification of demodulation in static propagation and Multipath fading case 1 for Home BS | F | 10.2.0 | 10.3.0 | TEI10 | +| RP-56 | RP-120783 | 286 | | Update to regional requirement table | F | 10.3.0 | 10.4.0 | TEI10 | +| RP-56 | RP-120765 | 292 | 1 | Additional spurious emissions requirements for PHS | A | 10.3.0 | 10.4.0 | TEI8 | +| RP-56 | RP-120795 | 283 | 1 | TDD blocking for co-location | F | 10.4.0 | 11.0.0 | TEI11 | +| RP-56 | RP-120795 | 284 | 1 | WA co-existence/co-location | F | 10.4.0 | 11.0.0 | TEI11 | +| RP-56 | RP-120795 | 285 | 1 | Co-existence between TDD systems | F | 10.4.0 | 11.0.0 | TEI11 | +| RP-56 | RP-120795 | 287 | | LA co-existence/co-location | F | 10.4.0 | 11.0.0 | TEI11 | +| RP-56 | RP-120795 | 288 | | Co-existence/co-location between LA TDD systems | F | 10.4.0 | 11.0.0 | TEI11 | +| RP-56 | RP-120793 | 289 | | Introduction of Band 44 | B | 10.4.0 | 11.0.0 | LTE_APAC7
00-Core | +| RP-57 | RP-121296 | 296 | | Clarification for TDD Band | A | 11.0.0 | 11.1.0 | TEI8 | +| RP-59 | RP-130287 | 297 | | Update of BS co-existence requirement towards UTRA TDD bands in China | F | 11.1.0 | 11.2.0 | TEI11 | +| RP-60 | RP-130768 | 298 | 1 | On additional ACLR requirement | F | 11.2.0 | 11.3.0 | TEI11 | +| RP-60 | RP-130764 | 299 | | Co-existence around 3500 MHz | F | 11.2.0 | 11.3.0 | RInImp8-
UMTSLTE3
500 | +| RP-60 | RP-130768 | 300 | | Rel.11 CR for 25.142: Editorial Corrections and Amendment with Missed TT Values | F | 11.2.0 | 11.3.0 | TEI11 | +| RP-60 | RP-130768 | 301 | 1 | Addition of MC-HSDPA for general clause 6.1 | F | 11.2.0 | 11.3.0 | TEI11 | +| SP-65 | - | - | - | Update to Rel-12 version (MCC) | - | 11.3.0 | 12.0.0 | | +| RP-66 | RP-142146 | 314 | | Introduction of testing for multi-carrier and multi-band operation in TS25.142 | A | 12.0.0 | 12.1.0 | MB_MSR_
RF-Perf | +| RP-66 | RP-142146 | 315 | | Introduction of requirements for BS capable of multi-band operation | A | 12.0.0 | 12.1.0 | MB_MSR_
RF-Perf | +| RP-70 | RP-152132 | 317 | | TX intermodulation requirement correction | A | 12.1.0 | 12.2.0 | TEI11 | +| SP-70 | - | - | - | Update to Rel-13 version (MCC) | - | 12.2.0 | 13.0.0 | | +| | | | | Editorial Change to the cover page | | 13.0.0 | 13.0.1 | | + +| Change history | | | | | | | | +|----------------|---------|-----------|-----|-----|-----|--------------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2016-06 | RAN#72 | RP-161134 | 320 | | B | Introduction of Band 46 in TS 25.142 | 13.1.0 | +| 2017-03 | RAN#75 | - | - | - | - | Update to Rel-14 version (MCC) | 14.0.0 | +| 2018-06 | SA#80 | - | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| | | | | | | Editorial Change to the cover page | 15.0.1 | +| 2020-06 | SA#88 | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25143/04f7b8f64493f6d83188232f10f86fe2_img.jpg b/marked/Rel-16/25_series/25143/04f7b8f64493f6d83188232f10f86fe2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..65705313db85514d1207cfb6a73c369d91894f8a --- /dev/null +++ b/marked/Rel-16/25_series/25143/04f7b8f64493f6d83188232f10f86fe2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61c79d59e698bc98bbd496f652c6470b00ca10b442c930832150ae956ce3d7f6 +size 17855 diff --git a/marked/Rel-16/25_series/25143/18dbea0ac6b7ad13e47afda3ddd53b64_img.jpg b/marked/Rel-16/25_series/25143/18dbea0ac6b7ad13e47afda3ddd53b64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4216824e8a8cb5b78a2fd839ecb0c206bc73e3c9 --- /dev/null +++ b/marked/Rel-16/25_series/25143/18dbea0ac6b7ad13e47afda3ddd53b64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca7402ed21a85587d22d9b56cc5bfbfb725ba84521f098975ead7a654a281410 +size 39436 diff --git a/marked/Rel-16/25_series/25143/24a27d17656bcf0ee131539f2bbb34cd_img.jpg b/marked/Rel-16/25_series/25143/24a27d17656bcf0ee131539f2bbb34cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f80428b3648e0958bd5329037fd229e68a8a62e2 --- /dev/null +++ b/marked/Rel-16/25_series/25143/24a27d17656bcf0ee131539f2bbb34cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59b1126d895b0c600b2cd5aa63d6696a988e88101c7761b1833eac0799dc2381 +size 15780 diff --git a/marked/Rel-16/25_series/25143/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg b/marked/Rel-16/25_series/25143/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81df87ba9284ece160c90ce79bf7f0200637f70c --- /dev/null +++ b/marked/Rel-16/25_series/25143/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c94a69ba97dd02c1042b57c255e300e24c23401019390a2db551d7650b0c653d +size 29724 diff --git a/marked/Rel-16/25_series/25143/719ef0f734259484038b2434e5dc3f24_img.jpg b/marked/Rel-16/25_series/25143/719ef0f734259484038b2434e5dc3f24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66b7d88549f38bb30ca9f0f9c7f2aa21ae4b75ba --- /dev/null +++ b/marked/Rel-16/25_series/25143/719ef0f734259484038b2434e5dc3f24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a9c254e3889a206114b07964d2ac986501637452698454c46a1f198e01b6f0e +size 20483 diff --git a/marked/Rel-16/25_series/25143/b82b870697ef3993804c839b298c0f4f_img.jpg b/marked/Rel-16/25_series/25143/b82b870697ef3993804c839b298c0f4f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c70d038a617fab66e1e5860c503f083f25c6e5bb --- /dev/null +++ b/marked/Rel-16/25_series/25143/b82b870697ef3993804c839b298c0f4f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:004c3df280d5fb1959897b91d02f700997e9831b1960cdc13f8a873a06741001 +size 16482 diff --git a/marked/Rel-16/25_series/25143/bc6f0b99574deef4f696650b64a600c1_img.jpg b/marked/Rel-16/25_series/25143/bc6f0b99574deef4f696650b64a600c1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70fb813359bffcaadffdf7bd2088f2538f5dc3fe --- /dev/null +++ b/marked/Rel-16/25_series/25143/bc6f0b99574deef4f696650b64a600c1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18bfddc1fcd3b7f032d5f2cd100f208dbcf5781f0cda0149680794fc4e1da849 +size 23540 diff --git a/marked/Rel-16/25_series/25143/cc893412ff9ca2426705e878c75548ba_img.jpg b/marked/Rel-16/25_series/25143/cc893412ff9ca2426705e878c75548ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0c8d9e49cca903af8ff669b37bd6601ea1867ed --- /dev/null +++ b/marked/Rel-16/25_series/25143/cc893412ff9ca2426705e878c75548ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc0732f11d0e9f9c2f261feeacfb13872111f3fc25ec76b599a815665a613cb7 +size 17450 diff --git a/marked/Rel-16/25_series/25143/cdc21bbfcba380e98ece42e5b8da50bb_img.jpg b/marked/Rel-16/25_series/25143/cdc21bbfcba380e98ece42e5b8da50bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14ce640b5ab19e560f09521ef49af135662bb823 --- /dev/null +++ b/marked/Rel-16/25_series/25143/cdc21bbfcba380e98ece42e5b8da50bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca5679586fd63467cca8f7454335a18efd06596312bb785b49b76bcd62f1b824 +size 17642 diff --git a/marked/Rel-16/25_series/25143/ee0bf6a260cff72af8f0df0639b6a7c5_img.jpg b/marked/Rel-16/25_series/25143/ee0bf6a260cff72af8f0df0639b6a7c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19acc8bb49782fda39b313ccde0b6d055f96c797 --- /dev/null +++ b/marked/Rel-16/25_series/25143/ee0bf6a260cff72af8f0df0639b6a7c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:574eddbcd90e938a5b1725e9767310968063c60c53876e38c1afba4540cae1f2 +size 18908 diff --git a/marked/Rel-16/25_series/25143/raw.md b/marked/Rel-16/25_series/25143/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..79ca2e3df2072ca2ee07093c354985b9f1ae1389 --- /dev/null +++ b/marked/Rel-16/25_series/25143/raw.md @@ -0,0 +1,2408 @@ + + + + + + +# --- Contents + +| | | | +|---------|-----------------------------------------------|----| +| 1 | Scope..... | 7 | +| 2 | References..... | 7 | +| 3 | Definitions, symbols and abbreviations ..... | 8 | +| 3.1 | Definitions ..... | 8 | +| 3.2 | (void) ..... | 9 | +| 3.3 | Abbreviations ..... | 9 | +| 4 | Frequency bands and channel arrangement ..... | 9 | +| 4.1 | Frequency bands..... | 9 | +| 4.2 | TX – RX frequency separation..... | 10 | +| 4.3 | Channel arrangement..... | 11 | +| 4.3.1 | Channel spacing..... | 11 | +| 4.3.2 | Channel raster ..... | 11 | +| 4.3.3 | Channel number..... | 11 | +| 5 | General test conditions and declarations..... | 12 | +| 5.1 | Acceptable uncertainty of Test System..... | 13 | +| 5.1.1 | Measurements of test environments ..... | 13 | +| 5.1.2 | Measurements of Repeater ..... | 14 | +| 5.2 | Repeater test tolerances (informative)..... | 15 | +| 5.3 | Interpretation of measurement results ..... | 16 | +| 5.4 | Test Environment ..... | 17 | +| 5.4.1 | Normal test environment ..... | 17 | +| 5.4.2 | Extreme test environment..... | 17 | +| 5.4.2.1 | Extreme temperature..... | 17 | +| 5.4.3 | Vibration..... | 18 | +| 5.4.4 | Power supply ..... | 18 | +| 5.5 | Selection of configurations for testing ..... | 18 | +| 5.6 | Regional requirements..... | 19 | +| 5.7 | Test Models ..... | 20 | +| 5.8 | Format and interpretation of tests..... | 20 | +| 5.9 | Repeater configurations..... | 21 | +| 5.9.1 | Power supply options ..... | 21 | +| 5.9.2 | Combining of Repeaters ..... | 21 | +| 6 | Output power..... | 21 | +| 6.1 | Maximum output power ..... | 21 | +| 6.1.1 | Definition and applicability ..... | 21 | +| 6.1.2 | Minimum Requirements ..... | 21 | +| 6.1.3 | Test purpose..... | 22 | +| 6.1.4 | Method of test..... | 22 | +| 6.1.4.1 | Initial conditions ..... | 22 | +| 6.1.4.2 | Procedure ..... | 22 | +| 6.1.5 | Test Requirements ..... | 22 | +| 7 | Frequency stability..... | 23 | +| 7.1 | Definition and applicability..... | 23 | +| 7.2 | Minimum Requirement ..... | 23 | +| 7.3 | Test purpose ..... | 23 | +| 7.4 | Method of test..... | 24 | +| 7.4.1 | Initial conditions ..... | 24 | +| 7.4.2 | Procedure ..... | 24 | +| 7.5 | Test requirements ..... | 24 | +| 8 | Out of band gain..... | 24 | +| 8.1 | Definitions and applicability ..... | 24 | +| 8.2 | Minimum Requirements..... | 24 | +| 8.3 | Test purpose ..... | 25 | +| 8.4 | Method of test..... | 25 | + +| | | | +|-----------|-------------------------------------------------------------------------|----| +| 8.4.1 | Initial conditions ..... | 25 | +| 8.4.2 | Procedure ..... | 25 | +| 8.5 | Test requirements ..... | 25 | +| 9 | Unwanted emission ..... | 26 | +| 9.1 | Out of band emission..... | 26 | +| 9.1.1 | Void..... | 26 | +| 9.1.2 | Operating band unwanted emissions ..... | 26 | +| 9.1.2.1 | Definitions and applicability..... | 26 | +| 9.1.2.2 | Minimum Requirements ..... | 27 | +| 9.1.2.3 | Test purpose..... | 30 | +| 9.1.2.4 | Method of test..... | 30 | +| 9.1.2.4.1 | Initial conditions..... | 30 | +| 9.1.2.4.2 | Procedures ..... | 31 | +| 9.1.2.5 | Test requirements..... | 31 | +| 9.1.3 | Protection of BS receiver in the operating band..... | 34 | +| 9.1.3.1 | Minimum Requirement..... | 34 | +| 9.1.4 | Co-existence with services in adjacent frequency bands..... | 35 | +| 9.1.4.1 | Minimum requirement ..... | 35 | +| 9.2 | Spurious emissions..... | 35 | +| 9.2.1 | Definition and applicability ..... | 35 | +| 9.2.2 | Minimum Requirements..... | 35 | +| 9.2.2.1 | Spurious emission (Category A)..... | 35 | +| 9.2.2.2 | Spurious emission (Category B)..... | 36 | +| 9.2.2.3 | Void ..... | 37 | +| 9.2.2.4 | Co-existence with other systems in the same geographical area ..... | 37 | +| 9.2.2.4.1 | Minimum Requirements..... | 38 | +| 9.2.2.5 | Co-existence with co-located and co-sited base stations ..... | 41 | +| 9.2.2.5.1 | Minimum Requirements..... | 42 | +| 9.2.2.6 | Co-existence with PHS ..... | 44 | +| 9.2.2.6.1 | Minimum requirement..... | 45 | +| 9.2.2.7 | Co-existence with UTRA-TDD and/or E-UTRA TDD ..... | 45 | +| 9.2.2.7.1 | Operation in the same geographic area ..... | 45 | +| 9.2.2.7.2 | Co-located Repeaters and UTRA-TDD and/or E-UTRA TDD base stations ..... | 47 | +| 9.2.2.8 | (Void)..... | 49 | +| 9.2.2.9 | Protection of public safety operations ..... | 49 | +| 9.2.2.9.1 | Minimum Requirement ..... | 49 | +| 9.2.3 | Test purpose..... | 49 | +| 9.2.4 | Method of test..... | 49 | +| 9.2.4.1 | Initial conditions ..... | 49 | +| 9.2.4.2 | Procedures..... | 50 | +| 9.2.5 | Test requirements ..... | 50 | +| 10 | Modulation accuracy..... | 50 | +| 10.1 | Error vector magnitude..... | 50 | +| 10.1.1 | Definition and applicability ..... | 50 | +| 10.1.2 | Minimum Requirements..... | 50 | +| 10.1.3 | Test purpose..... | 51 | +| 10.1.4 | Method of test..... | 51 | +| 10.1.4.1 | Initial conditions ..... | 51 | +| 10.1.4.2 | Procedure ..... | 51 | +| 10.1.4.3 | Stimulus EVM effect ..... | 51 | +| 10.1.5 | Test requirements ..... | 51 | +| 10.2 | Peak code domain error..... | 51 | +| 10.2.1 | Definition and applicability ..... | 51 | +| 10.2.2 | Minimum Requirements..... | 51 | +| 10.2.3 | Test purpose..... | 51 | +| 10.2.4 | Method of test..... | 52 | +| 10.2.4.1 | Initial conditions ..... | 52 | +| 10.2.4.2 | Procedure ..... | 52 | +| 10.2.5 | Test requirements ..... | 52 | +| 10.3 | Relative Code Domain Error (RCDE) for 64QAM modulation ..... | 52 | + +| | | | +|----------|-----------------------------------------------|----| +| 10.3.1 | Definition and applicability ..... | 52 | +| 10.3.2 | Minimum requirement..... | 52 | +| 10.3.3 | Test purpose..... | 52 | +| 10.3.4 | Method of test..... | 52 | +| 10.3.4.1 | Initial conditions ..... | 52 | +| 10.3.4.2 | Procedure ..... | 53 | +| 10.3.5 | Test requirements ..... | 53 | +| 11 | Input intermodulation..... | 53 | +| 11.1 | Definition and applicability..... | 53 | +| 11.2 | Minimum Requirements..... | 53 | +| 11.2.1 | General requirement ..... | 53 | +| 11.2.2 | Co-location with BS in other systems ..... | 53 | +| 11.2.3 | Co-existence with other systems ..... | 57 | +| 11.3 | Test purpose ..... | 60 | +| 11.4 | Method of test..... | 60 | +| 11.4.1 | Initial conditions ..... | 60 | +| 11.4.2 | Procedure ..... | 61 | +| 11.5 | Test requirements ..... | 61 | +| 11.5.1 | Mandatory requirement ..... | 61 | +| 11.5.2 | Co-location with BS in other systems ..... | 61 | +| 11.5.3 | Co-existence with other systems ..... | 65 | +| 12 | Output intermodulation ..... | 68 | +| 12.1 | Definition and applicability..... | 68 | +| 12.2 | Minimum requirement..... | 69 | +| 12.3 | Test purpose ..... | 69 | +| 12.4 | Method of test..... | 69 | +| 12.4.1 | Initial conditions ..... | 69 | +| 12.4.2 | Procedures ..... | 69 | +| 12.5 | Test requirements ..... | 69 | +| 13 | Adjacent Channel Rejection Ratio (ACRR) ..... | 70 | +| 13.1 | Definitions and applicability ..... | 70 | +| 13.2 | Minimum Requirements..... | 70 | +| 13.3 | Test purpose ..... | 70 | +| 13.4 | Method of test..... | 70 | +| 13.4.1 | Initial conditions ..... | 70 | +| 13.4.2 | Procedure ..... | 70 | +| 13.4.3 | Test Requirements ..... | 71 | + +| | | | +|-------------------------------|-----------------------------------------------------------------------------------------|-----------| +| Annex A (informative): | Repeater measurement system set-up ..... | 72 | +| A.1 | Maximum output power..... | 72 | +| A.2 | Frequency stability..... | 72 | +| A.3 | Out of band gain..... | 72 | +| A.4 | Unwanted emission: Spectrum emission mask..... | 72 | +| A.5 | Unwanted emission: Spurious emission ..... | 73 | +| A.6 | Modulation Accuracy: Error Vector Magnitude ..... | 73 | +| A.7 | Modulation Accuracy: Peak Code Domain Error Error and Relative Coder Domain Error ..... | 73 | +| A.8 | Input inter modulation..... | 74 | +| A.9 | Output Intermodulation..... | 74 | +| Annex B (informative): | Derivation of Test Requirements ..... | 75 | +| Annex C (informative): | Acceptable uncertainty of Test Equipment ..... | 78 | +| Annex D (informative): | Change History..... | 79 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- Y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the Radio Frequency (RF) test methods and Minimum Requirements for UTRA FDD Repeaters. These have been derived from, and are consistent with the UTRA FDD Repeater specifications defined in TS 25.106. + +This document establishes the minimum RF characteristics of the UTRA FDD Repeater. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TS 25.104: "UTRA(BS) FDD; Radio transmission and Reception". +- [2] 3GPP TS 25.942: "RF system scenarios". +- [3] 3GPP TS 25.113 : "Base station EMC". +- [4] ITU-R recommendation SM.329: "Unwanted emissions in the spurious domain ". +- [5] ITU-T recommendation O.153: "Basic parameters for the measurement of error performance at bit rates below the primary rate". +- [6] IEC 60721-3-3 (1994): "Classification of environmental conditions – Part 3: Classification of groups of environmental parameters and their severities – Section 3: Stationary use at weather protected locations". + +- [7] IEC 60721-3-4 (1995): "Classification of environmental conditions – Part 3: Classification of groups of environmental parameters and their severities – Section 4: Stationary use at non-weather protected locations". +- [8] IEC 60068-2-1 (1990): "Environmental testing – Part 2: Tests. Tests A: Cold". +- [9] IEC 60068-2-2 (1974): "Environmental testing – Part 2: Tests. Tests B: Dry heat". +- [10] IEC 60068-2-6 (1995): "Environmental testing – Part 2: Tests – Test Fc: Vibration (sinusoidal)". +- [11] 3GPP TS 25.141: "Base station conformance testing (FDD)". +- [12] 3GPP TS 25.106: "UTRA Repeater; Radio transmission and reception". +- [13] 3GPP TS 36.143: "Evolved Universal Terrestrial Radio Access (E-UTRA); FDD repeater conformance testing" +- [14] CEPT ECC Decision (13)03, "The harmonised use of the frequency band 1452-1492 MHz for Mobile/Fixed Communications Networks Supplemental Downlink (MFCN SDL)". +- [15] 3GPP TS 36.104: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**Donor coupling loss:** is the coupling loss between the repeater and the donor base station. + +**Down-link:** signal path where base station transmits and mobile receives + +**Maximum output power, Pmax:** This is the mean power level per carrier measured at the antenna connector of the Repeater in specified reference condition. + +**Operating band:** the frequency range in which UTRA FDD operates, that is defined with a specific set of technical requirements. + +NOTE 1: The operating band(s) for an UTRA Repeater is declared by the manufacturer according to the designations in clause 4.1, Table 4.1. + +NOTE 2: Unless specified, operating band refers to the uplink operating band and downlink operating band. + +**Pass band:** the pass band is the frequency range in which the Repeater operates in with operational configuration. This frequency range can correspond to one or several consecutive nominal 5 MHz channels. If they are not consecutive each subset of channels shall be considered as an individual pass band. A repeater can have one or several pass bands. + +**Repeater:** a device that receives, amplifies and transmits the radiated or conducted RF carrier both in the down-link direction (from the base station to the mobile area) and in the up-link direction (from the mobile to the base station). In operating bands specified with only down-link or up-link, only the up-link or down-link as specified for the operating band is repeated. + +**Up-link:** signal path where mobile transmits and base station receives. + +## 3.2 (void) + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|----|--------------------------------------| +| BS | Base Transceiver Station | +| CW | Continuous Wave (unmodulated signal) | +| DL | Down Link (forward link) | + +| | | +|---------|----------------------------------------------| +| DTT | Digital Terrestrial Television | +| EIRP | Effective Isotropic Radiated Power | +| EVM | Error Vector Magnitude | +| FDD | Frequency Division Duplex | +| FFS | For Further Study | +| IMT2000 | International Mobile Telecommunication-2000 | +| ITU | International Telecommunication Union | +| MS | Mobile Station | +| RCDE | Relative Code Domain Error | +| RF | Radio Frequency | +| RSS | Root Sum of the Squares | +| TDD | Time Division Duplex | +| UARFCN | UTRA Absolute Radio Frequency Channel Number | +| UL | Up Link (reverse link) | +| UMTS | Universal Mobile Telecommunication System | +| UTRA | Universal Terrestrial Radio Access | +| WCDMA | Wide band Code Division Multiple Access | + +# 4 Frequency bands and channel arrangement + +## 4.1 Frequency bands + +- a) A UTRA/FDD Repeater is designed to operate in one or several pass bands within either of the following operating bands; + +**Table 4.1: Frequency bands** + +| Operating Band | UL Frequencies
UE transmit, Node B receive | DL frequencies
UE receive, Node B transmit | +|----------------|-----------------------------------------------|-----------------------------------------------| +| I | 1920 – 1980 MHz | 2110 -2170 MHz | +| II | 1850 -1910 MHz | 1930 -1990 MHz | +| III | 1710 – 1785 MHz | 1805 – 1880 MHz | +| IV | 1710 – 1755 MHz | 2110 – 2155 MHz | +| V | 824 – 849MHz | 869 – 894MHz | +| VI | 830 – 840 MHz | 875 – 885 MHz | +| VII | 2500 – 2570 MHz | 2620 – 2690 MHz | +| VIII | 880 – 915 MHz | 925 – 960 MHz | +| IX | 1749.9 – 1784.9 MHz | 1844.9 – 1879.9 MHz | +| X | 1710 – 1770 MHz | 2110 – 2170 MHz | +| XI | 1427.9 – 1452.9 MHz | 1475.9 – 1500.9 MHz | +| XII | 698 - 716 MHz | 728 - 746 MHz | +| XIII | 777 - 787 MHz | 746 - 756 MHz | +| XIV | 788 - 798 MHz | 758 - 768 MHz | +| XV | Reserved | Reserved | +| XVI | Reserved | Reserved | +| XVII | Reserved | Reserved | +| XVIII | Reserved | Reserved | +| XIX | 830 – 845 MHz | 875 -890 MHz | +| XX | 832 – 862 MHz | 791 – 821 MHz | +| XXI | 1447.9 – 1462.9 MHz | 1495.9 – 1510.9 MHz | +| XXII | 3410 – 3490 MHz | 3510 – 3590 MHz | +| XXV | 1850 – 1915 MHz | 1930 – 1995 MHz | +| XXVI | 814 – 849 MHz | 859 – 894 MHz | +| XXXII | N/A | 1452 – 1496 MHz | + +- b) Deployment in other frequency bands is not precluded. + +## 4.2 TX – RX frequency separation + +- a) A UTRA/FDD repeaters is designed to operate with the following TX to RX frequency separation + +**Table 4.2: TX-RX frequency separation** + +| Operating Band | TX-RX frequency separation | +|----------------|----------------------------| +| I | 190 MHz | +| II | 80 MHz | +| III | 95 MHz | +| IV | 400 MHz | +| V | 45 MHz | +| VI | 45 MHz | +| VII | 120 MHz | +| VIII | 45 MHz | +| IX | 95 MHz | +| X | 400 MHz | +| XI | 48 MHz | +| XII | 30 MHz | +| XIII | 31 MHz | +| XIV | 30 MHz | +| XIX | 45 MHz | +| XX | 41 MHz | +| XXI | 48 MHz | +| XXII | 100 MHz | +| XXV | 80 MHz | +| XXVI | 45 MHz | + +- b) A UTRA/FDD Repeater can support both fixed and variable up-link to down-link frequency separation. +- c) The use of other up-link to down-link frequency separations in existing or other frequency bands shall not be precluded. + +## 4.3 Channel arrangement + +### 4.3.1 Channel spacing + +The nominal channel spacing is 5 MHz, but this can be adjusted to optimise performance in a particular deployment scenario. + +### 4.3.2 Channel raster + +The channel raster is 200 kHz for all bands, which means that the centre frequency must be an integer multiple of 200 kHz. In addition a number of additional centre frequencies are specified according to the table 4.4, which means that the centre frequencies for these channels are shifted 100 kHz relative to the general raster. + +### 4.3.3 Channel number + +The carrier frequency is designated by the UTRA Absolute Radio Frequency Channel Number (UARFCN). + +For each operating band, the UARFCN values are defined as follows. + +Uplink: $N_U = 5 * (F_{UL} - F_{UL\_offset})$ , for the carrier frequency range $F_{UL\_low} \leq F_{UL} \leq F_{UL\_high}$ + +Downlink: $N_D = 5 * (F_{DL} - F_{DL\_offset})$ , for the carrier frequency range $F_{DL\_low} \leq F_{DL} \leq F_{DL\_high}$ + +For each operating Band, $F_{UL\_offset}$ , $F_{UL\_low}$ , $F_{UL\_high}$ , $F_{DL\_offset}$ , $F_{DL\_low}$ and $F_{DL\_high}$ are defined in Table 4.3 for the general UARFCN. For the additional UARFCN, $F_{UL\_offset}$ , $F_{DL\_offset}$ and the specific $F_{UL}$ and $F_{DL}$ are defined in Table 4.4. + +**Table 4.3: UARFCN definition (general)** + +| Band | UPLINK (UL) | | | DOWNLINK (DL) | | | +|-------|--------------------------------------------------------|-----------------------------------------------------|----------------------|--------------------------------------------------------|-----------------------------------------------------|----------------------| +| | UE transmit, Node B receive | | | UE receive, Node B transmit | | | +| | UARFCN formula offset
F UL _Offset [MHz] | Carrier frequency (F UL )
range [MHz] | | UARFCN formula offset
F DL _Offset [MHz] | Carrier frequency (F DL )
range [MHz] | | +| | | F UL low | F UL high | | F DL low | F DL high | +| I | 0 | 1922.4 | 1977.6 | 0 | 2112.4 | 2167.6 | +| II | 0 | 1852.4 | 1907.6 | 0 | 1932.4 | 1987.6 | +| III | 1525 | 1712.4 | 1782.6 | 1575 | 1807.4 | 1877.6 | +| IV | 1450 | 1712.4 | 1752.6 | 1805 | 2112.4 | 2152.6 | +| V | 0 | 826.4 | 846.6 | 0 | 871.4 | 891.6 | +| VI | 0 | 832.4 | 837.6 | 0 | 877.4 | 882.6 | +| VII | 2100 | 2502.4 | 2567.6 | 2175 | 2622.4 | 2687.6 | +| VIII | 340 | 882.4 | 912.6 | 340 | 927.4 | 957.6 | +| IX | 0 | 1752.4 | 1782.4 | 0 | 1847.4 | 1877.4 | +| X | 1135 | 1712.4 | 1767.6 | 1490 | 2112.4 | 2167.6 | +| XI | 733 | 1430.4 | 1450.4 | 736 | 1478.4 | 1498.4 | +| XII | -22 | 700.4 | 713.6 | -37 | 730.4 | 743.6 | +| XIII | 21 | 779.4 | 784.6 | -55 | 748.4 | 753.6 | +| XIV | 12 | 790.4 | 795.6 | -63 | 760.4 | 765.6 | +| XIX | 770 | 832.4 | 842.6 | 735 | 877.4 | 887.6 | +| XX | -23 | 834.4 | 859.6 | -109 | 793.4 | 818.6 | +| XXI | 1358 | 1450.4 | 1460.4 | 1326 | 1498.4 | 1508.4 | +| XXII | 2525 | 3412.4 | 3487.6 | 2580 | 3512.4 | 3587.6 | +| XXV | 875 | 1852.4 | 1912.6 | 910 | 1932.4 | 1992.6 | +| XXVI | -291 | 816.4 | 846.6 | -291 | 861.4 | 891.6 | +| XXXII | - | N/A | N/A | 131 | 1454.4 | 1493.6 | + +**Table 4.4: UARFCN definition (additional channels)** + +| Band | UPLINK (UL)
UE transmit, Node B receive | | DOWNLINK (DL)
UE receive, Node B transmit | | +|-------|----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------| +| | UARFCN
formula offset
$F_{UL\_Offset}$ [MHz] | Carrier frequency [MHz]
( $F_{UL}$ ) | UARFCN
formula offset
$F_{DL\_Offset}$ [MHz] | Carrier frequency [MHz]
( $F_{DL}$ ) | +| I | - | - | - | - | +| II | 1850.1 | 1852.5, 1857.5, 1862.5,
1867.5, 1872.5, 1877.5,
1882.5, 1887.5, 1892.5,
1897.5, 1902.5, 1907.5 | 1850.1 | 1932.5, 1937.5, 1942.5,
1947.5, 1952.5, 1957.5,
1962.5, 1967.5, 1972.5,
1977.5, 1982.5, 1987.5 | +| III | - | - | - | - | +| IV | 1380.1 | 1712.5, 1717.5, 1722.5,
1727.5, 1732.5, 1737.5,
1742.5, 1747.5, 1752.5 | 1735.1 | 2112.5, 2117.5, 2122.5,
2127.5, 2132.5, 2137.5,
2142.5, 2147.5, 2152.5 | +| V | 670.1 | 826.5, 827.5, 831.5,
832.5, 837.5, 842.5 | 670.1 | 871.5, 872.5, 876.5,
877.5, 882.5, 887.5 | +| VI | 670.1 | 832.5, 837.5 | 670.1 | 877.5, 882.5 | +| VII | 2030.1 | 2502.5, 2507.5, 2512.5,
2517.5, 2522.5, 2527.5,
2532.5, 2537.5, 2542.5,
2547.5, 2552.5, 2557.5,
2562.5, 2567.5 | 2105.1 | 2622.5, 2627.5, 2632.5,
2637.5, 2642.5, 2647.5,
2652.5, 2657.5, 2662.5,
2667.5, 2672.5, 2677.5,
2682.5, 2687.5 | +| VIII | - | - | - | - | +| IX | - | - | - | - | +| X | 1075.1 | 1712.5, 1717.5, 1722.5,
1727.5, 1732.5, 1737.5,
1742.5, 1747.5, 1752.5,
1757.5, 1762.5, 1767.5 | 1430.1 | 2112.5, 2117.5, 2122.5,
2127.5, 2132.5, 2137.5,
2142.5, 2147.5, 2152.5,
2157.5, 2162.5, 2167.5 | +| XI | - | - | - | - | +| XII | -39.9 | 700.5, 701.5, 706.5,
707.5, 712.5, 713.5 | -54.9 | 730.5, 731.5, 736.5, 737.5,
742.5, 743.5 | +| XIII | 11.1 | 779.5, 784.5 | -64.9 | 748.5, 753.5 | +| XIV | 2.1 | 790.5, 795.5 | -72.9 | 760.5, 765.5 | +| XIX | 755.1 | 832.5, 837.5, 842.5 | 720.1 | 877.5, 882.5, 887.5 | +| XX | - | - | - | - | +| XXI | - | - | - | - | +| XXII | - | - | - | - | +| XXV | 810.1 | 1852.5, 1857.5, 1862.5,
1867.5, 1872.5, 1877.5,
1882.5, 1887.5, 1892.5,
1897.5, 1902.5, 1907.5,
1912.5 | 845.1 | 1932.5, 1937.5, 1942.5,
1947.5, 1952.5, 1957.5,
1962.5, 1967.5, 1972.5,
1977.5, 1982.5, 1987.5,
1992.5 | +| XXVI | -325.9 | 816.5, 821.5, 826.5,
827.5, 831.5, 832.5,
836.5, 837.5, 841.5,
842.5, 846.5 | -325.9 | 861.5, 866.5, 871.5, 872.5,
876.5, 877.5, 881.5, 882.5,
886.5, 887.5, 891.5 | +| XXXII | - | - | 87.1 | 1454.5, 1459.5, 1464.5,
1469.5, 1474.5, 1479.5,
1484.5, 1489.5 | + +# 5 General test conditions and declarations + +This specification applies only to UTRA/FDD Repeater. + +The requirements of this clause apply to all applicable tests in this specification. Many of the tests in this specification measure a parameter relative to a value, that is not fully specified in the UTRA specifications. For these tests, the Minimum Requirement is determined relative to a nominal value specified by the manufacturer. + +Some requirements for the Repeater may be regional as listed in subclause 5.6. + +When specified in a test, the manufacturer shall declare the nominal value of a parameter, or whether an option is supported. + +Schematic drawings for the individual measurement set-up can be found in the Annex. + +## 5.1 Acceptable uncertainty of Test System + +The maximum acceptable uncertainty of the Test System is specified below for each test, where appropriate. The Test System shall enable the stimulus signals in the test case to be adjusted to within the specified tolerance, and the equipment under test to be measured with an uncertainty not exceeding the specified values. All tolerances and uncertainties are absolute values, and are valid for a confidence level of 95 %, unless otherwise stated. + +A confidence level of 95% is the measurement uncertainty tolerance interval for a specific measurement that contains 95% of the performance of a population of test equipment. + +For RF test it should be noted that the uncertainties in subclause 5.1 apply to the Test System operating into a nominal 50 ohm load and do not include system effects due to mismatch between the DUT and the Test System. + +### 5.1.1 Measurements of test environments + +The measurement accuracy of the Repeater test environments defined in Subclause 5.4, Test environments shall be. + +| | | +|----------------------|--------------| +| Pressure: | ± 5 kPa. | +| Temperature: | ± 2 degrees. | +| Relative Humidity: | ± 5 %. | +| DC Voltage: | ± 1,0 %. | +| AC Voltage: | ± 1,5 %. | +| Vibration: | 10 %. | +| Vibration frequency: | 0,1 Hz. | + +The above values shall apply unless the test environment is otherwise controlled and the specification for the control of the test environment specifies the uncertainty for the parameter. + +### 5.1.2 Measurements of Repeater + +**Table 5.1: Maximum Test System Uncertainty** + +| Subclause | Maximum Test System Uncertainty | Range over which Test System Uncertainty applies | +|--------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------| +| 6.1 Maximum output power | ±0,7 dB, $f \leq 3,0$ GHz
±1,0 dB, $3,0$ GHz $< f \leq 4,2$ GHz | | +| 7 Frequency error | ±12 Hz | Measurement results of ± 500 Hz | +| 8 Out of band gain | ±0,5 dB, $f \leq 3,0$ GHz
±0,8 dB, $3,0$ GHz $< f \leq 19,0$ GHz

Calibration of test set-up shall be made without D.U.T. in order to achieve the accuracy | | +| 9.1.2 Operating band unwanted emissions (except 9.1.3) | ±1,5 dB, $f \leq 3,0$ GHz
±1,8 dB, $3,0$ GHz $< f \leq 4,2$ GHz

Due to carrier leakage for measurements specified in a 1MHz bandwidth close to the carrier (4 MHz to 8 MHz), integration of the measurement using several narrower bandwidth measurements may be necessary in order to achieve the above accuracy.

The interference from the signal generator ACLR shall be minimum 10 dB below that of a Base Station according to TS25.141 | | +| 9.1.3 Protection of BS receiver in the operating band | for results $> -60$ dBm ±2,0 dB
for results $< -60$ dBm ±3,0 dB | | +| 9.2 Spurious emissions | In UTRA and coexistence receive bands:
for results $> -60$ dBm ±2,0 dB
for results $< -60$ dBm ±3,0 dB
Outside above range:
emission power
$f \leq 2,2$ GHz ±1,5 dB;
$2,2$ GHz $< f \leq 4$ GHz ±2,0 dB;
$4$ GHz $< f \leq 19$ GHz ±4,0 dB.

The interference from the signal generator ACLR shall be minimum 10 dB below that of a Base Station according to TS25.141 | | +| 10.1 Error vector magnitude | ± 2,5 % (single code applied)

(±2,5 % measurement error for single code).

5,0 % EVM in the stimulus signal (single code) will shift the EVM maximum value 0,7% to 18,2%.
(RSS repeater EVM and Stimulus EVM.) | Measurement results from 12,5% to 22,5% at signal power = $P\_max - 3$ dB to $P\_max - 18$ dB | +| 10.2 Peak code domain error | ±1,1dB

Formula: RSS measurement error and impedance mismatch error

(using ±1,0 dB measurement error and ±0,5 dB impedance mismatch error (stimulus side) assuming 14 dB return loss) | Measurement results from - 36 dB to - 30 dB, at signal power = $P\_max - 3$ dB to $P\_max - 18$ dB | +| 10.3 Relative Code Domain Error | 1.7 dB

Formula: Linear addition of the stimulus relative error power, analyser relative error power and repeater relative error power.normalised to repeater relative error power and expressed in dB.

-27dB RCDE in the stimulus signal and -27dB RCDE from the analyser and -21 dB repeater minimum requirement is assumed. | Measurements in the range -18 to - 21 dB at signal power = $P_{max}$ | +| 11 Input intermodulation Characteristics | ±1,2 dB

Formula: RSS CW1 level error, 2 x CW2 level error, and measurement error (using all errors = ±0,5 dB) | | + +| | | | +|-------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| 12 Output Intermodulation |

\pm 2,1 dB Spectrum emission

Formula: RSS 2x Interference signal level error and Spectrum emission measurement level error. (1 dB interference signal level error is assumed.)

Due to carrier leakage for measurements specified in a 1MHz bandwidth close to the carrier (4 MHz to 8 MHz), integration of the measurement using several narrower bandwidth measurements may be necessary in order to achieve the above accuracy.

The interference from the signal generator ACLR shall be minimum 10 dB below that of a Base Station

For spurious emission:

In UTRA and coexistence receive bands:
for results > -60 dBm \pm 2,0 dB
for results < -60 dBm \pm 3,0 dB

Outside above range:
emission power
f \leq 2,2 GHz \pm 1,5 dB;
2,2 GHz < f \leq 4 GHz \pm 2,0 dB;
4 GHz < f \leq 19 GHz \pm 4,0 dB.

The interference signal must have a spurious emission level at least 10 dB below the spurious levels required in 9.2.

| | +| 13 Adjacent Channel Rejection Ratio | $\pm 0,7$ dB | | + +## 5.2 Repeater test tolerances (informative) + +The Test Tolerances defined in this subclause have been used to relax the Minimum Requirements in this specification to derive the Test Requirements. + +The Test Tolerances are derived from Test System uncertainties, regulatory requirements and criticality to system performance. As a result, the Test Tolerances may sometimes be set to zero. + +The test tolerances should not be modified for any reason e.g. to take account of commonly known test system errors (such as mismatch, cable loss, etc.) + +**Table 5.2: Test Tolerance** + +| Subclause | Test Tolerance (Note 1) | Notes | +|---------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|------------------------------------------------------------------------------------------| +| 6.1 Maximum output power | 0,7 dB | | +| 9.1.2 Operating band unwanted emissions | 1,5 dB | 0 dB test tolerance for the additional Band II, IV, V, X, XII, XIII and XIV requirements | +| 9.2 Spurious emissions | 0 dB | | +| 7 Frequency error | 12 Hz | | +| 10.1 Error vector magnitude | 0 % | Target value is shifted due to stimulus EVM | +| 10.2 Peak code domain error | 1,1 dB | | +| 10.3 Relative Code Domain Error | 1,7 dB | | +| 8 Out of band gain | 0,5dB | | +| 11 Input intermodulation Characteristics | 1,2dB | | +| 12 Output intermodulation | 1,5 dB for spectrum emission
0 dB for spurious emission | | +| 13 Adjacent Channel Rejection Ratio | 0,7 dB | | +| NOTE 1: Unless otherwise stated, The Test Tolerances are applied to the DUT Minimum Requirement. See Annex B. | | | + +## 5.3 Interpretation of measurement results + +The measurement results returned by the Test System are compared – without any modification – against the Test Requirements as defined by the share risk principle. + +The share risk principle is defined in ETR 273 Part 1 sub-part 2 section 6.5. + +The actual measurement uncertainty of the Test System for the measurement of each parameter shall be included in the test report. + +The recorded value for the Test System uncertainty shall be, for each measurement, equal to or lower than the appropriate figure in subclause 5.1 of this specification. + +If the Test System for a test is known to have a measurement uncertainty greater than that specified in subclause 5.1, it is still permitted to use this apparatus provided that an adjustment is made as follows. + +Any additional uncertainty in the Test System over and above that specified in subclause 5.1 shall be used to tighten the Test Requirement-making the test harder to pass. (For some tests e.g. receiver test, this may require modification of stimulus signals). This procedure will ensure that a Test System not compliant with subclause 5.1 does not increase the chance of passing a device under test where that device would otherwise have failed the test if a Test System compliant with subclause 5.1 had been used. + +## 5.4 Test Environment + +For each test in the present document, the environmental conditions under which the Repeater is to be tested are defined. + +### 5.4.1 Normal test environment + +When a normal test environment is specified for a test, the test should be performed within the minimum and maximum limits of the conditions stated in Table 5.3. + +**Table 5.3: Limits of conditions for Normal Test Environment** + +| Condition | Minimum | Maximum | +|---------------------|------------------------------------------|---------| +| Barometric pressure | 86 kPa | 106 kPa | +| Temperature | 15°C | 30°C | +| Relative Humidity | 20 % | 85 % | +| Power supply | Nominal, as declared by the manufacturer | | +| Vibration | Negligible | | + +The ranges of barometric pressure, temperature and humidity represent the maximum variation expected in the uncontrolled environment of a test laboratory. If it is not possible to maintain these parameters within the specified limits, the actual values shall be recorded in the test report. + +NOTE: This may, for instance, be the case for measurements of radiated emissions performed on an open field test site. + +### 5.4.2 Extreme test environment + +The manufacturer shall declare one of the following: + +- 1) the equipment class for the equipment under test, as defined in the IEC 60 721-3-3 [6]; +- 2) the equipment class for the equipment under test, as defined in the IEC 60 721-3-4 [7]; +- 3) the equipment that does not comply to the mentioned classes, the relevant classes from IEC 60 721 [6], [7] documentation for Temperature, Humidity and Vibration shall be declared. + +NOTE: Reduced functionality for conditions that fall out side of the standard operational conditions are not tested in the present document. These may be stated and tested separately. + +#### 5.4.2.1 Extreme temperature + +When an extreme temperature test environment is specified for a test, the test shall be performed at the standard minimum and maximum operating temperatures defined by the manufacturer's declaration for the equipment under test. + +##### Minimum temperature: + +The test shall be performed with the environment test equipment and methods including the required environmental phenomena into the equipment, conforming to the test procedure of IEC 60 068-2-1 [8]. + +##### Maximum temperature: + +The test shall be performed with the environmental test equipment and methods including the required environmental phenomena into the equipment, conforming to the test procedure of IEC 60 068-2-2 [9]. + +NOTE: It is recommended that the equipment is made fully operational prior to the equipment being taken to its lower operating temperature. + +### 5.4.3 Vibration + +When vibration conditions are specified for a test, the test shall be performed while the equipment is subjected to a vibration sequence as defined by the manufacturer's declaration for the equipment under test. This shall use the environmental test equipment and methods of inducing the required environmental phenomena in to the equipment, conforming to the test procedure of IEC 60 068-2-6 [10]. Other environmental conditions shall be within the ranges specified in subclause 5.4.1. + +NOTE: The higher levels of vibration may induce undue physical stress in to equipment after a prolonged series of tests. The testing body should only vibrate the equipment during the RF measurement process. + +### 5.4.4 Power supply + +When extreme power supply conditions are specified for a test, the test shall be performed at the standard upper and lower limits of operating voltage defined by manufacturer's declaration for the equipment under test. + +#### Upper voltage limit: + +The equipment shall be supplied with a voltage equal to the upper limit declared by the manufacturer (as measured at the input terminals to the equipment). The tests shall be carried out at the steady state minimum and maximum temperature limits declared by the manufacturer for the equipment, to the methods described in IEC 60 068-2-1 [8] Test Ab/Ad and IEC 60 068-2-2 [9] Test Bb/Bd: Dry Heat. + +#### Lower voltage limit: + +The equipment shall be supplied with a voltage equal to the lower limit declared by the manufacturer (as measured at the input terminals to the equipment). The tests shall be carried out at the steady state minimum and maximum temperature limits declared by the manufacturer for the equipment, to the methods described in IEC 60 068-2-1 [8] Test Ab/Ad and IEC 60 068-2-2 [9] Test Bb/Bd: Dry Heat. + +## 5.5 Selection of configurations for testing + +Most tests in the present document are only performed for a subset of the possible combinations of test conditions. For instance: + +- only one RF channel may be specified to be tested; +- only one timeslot may be specified to be tested. + +When a test is performed by a test laboratory, the choice of which combinations are to be tested shall be specified by the laboratory. The laboratory may consult with operators, the manufacturer or other bodies. + +When a test is performed by a manufacturer, the choice of which combinations are to be tested may be specified by an operator. + +## 5.6 Regional requirements + +Some requirements in TS 25.143 may only apply in certain regions. Table 5.4 lists all requirements that may be applied differently in different regions. + +**Table 5.4: List of regional requirements** + +| Sub-clause number | Requirement | Comments | +|-------------------|---------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 4.1 | Frequency bands | Some bands may be applied regionally. | +| 4.2 | TX – RX frequency separation | The requirement is applied according to what frequency bands in clause 4.1 that are supported by the Repeater. | +| 4.3 | Channel arrangement | The requirement is applied according to what frequency bands in clause 4.1 that are supported by the Repeater. | +| 6.1 | Maximum output power | In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the ranges of conditions defined as normal. | +| 9.1.2 | Operating band unwanted emissions | The mask specified may be mandatory in certain regions. In other regions this mask may not be applied. Additional spectrum protection may apply regionally. | +| 9.2.2.1 | Spurious emissions (Category A) | These requirements shall be met in cases where Category A limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [4], are applied. | +| 9.2.2.2 | Spurious emissions (Category B) | These requirements shall be met in cases where Category B limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [4], are applied. | +| 9.2.2.4 | Spurious emissions: Co-existence with other systems in the same geographical area | These requirements may apply in geographic areas in which both UTRA FDD Repeater and GSM900, DCS1800, PCS1900, GSM850 and/or UTRA FDD operating in another frequency band are deployed. | +| 9.2.2.5 | Spurious emissions: Co-existence with co-located and co-sited base stations | These requirements may be applied for the protection of other BS receivers when GSM900, DCS1800, PCS1900, GSM850 and/or UTRA FDD BS operating in another frequency band are co-located with a UTRA FDD Repeater. | +| 9.2.2.6 | Spurious emissions: Co-existence with PHS | This requirement may be applied for the protection of PHS in geographic areas in which both PHS and UTRA FDD Repeaters are deployed. | +| 9.2.2.7.1 | Spurious emissions: Co-existence with UTRA TDD and/or E-UTRA TDD -Operation in the same geographic area | This requirement may be applied for the protection of UTRA UE in geographic areas in which both UTRA TDD BS and UTRA FDD Repeaters are deployed. | +| 9.2.2.7.2 | Spurious emissions: Co-existence with UTRA TDD and/or E-UTRA TDD – Co-location | This requirement may be applied for the protection of UTRA TDD BS receivers when UTRA TDD BS and UTRA FDD Repeaters are co-located. | +| 9.2.2.9 | Spurious emissions: Protection of public safety operations | This requirement shall be applied to Repeater operating in Bands XIII and XIV to ensure that appropriate interference protection is provided to 700 MHz public safety operations. | +| 11.2.2 | Input intermodulation: Co-location with BS in other systems | The requirement may be applied when GSM 900, DCS 1800, PCS1900, GSM850 and/or UTRA FDD BS operating in another frequency band and UTRA-FDD Repeaters are co-located. | +| 11.2.3 | Input Intermodulation: Co-existence with other systems | These requirements may apply in geographic areas in which both UTRA FDD Repeater and GSM900, DCS1800, PCS1900, GSM850 and/or UTRA FDD operating in another frequency band are deployed. | + +## 5.7 Test Models + +The set-up of physical channels for the Repeater tests shall be according to one of the test models described in TS 25.141 [11]. A reference to the applicable test model in TS 25.141 is made for each test in Table 5.5 by referring to the test model number as it appears in TS 25.141. + +These test models shall be used in the tests of both the up-link and the down-link directions of the Repeater unless otherwise stated. + +**Table 5.5: List of the applicable test models** + +| Test model number in TS 25.141 | Requirement | Comments | +|--------------------------------|----------------------------|----------| +| Test Model 1 | Repeater output power | | +| Test Model 1 | Out of band emission | | +| Test Model 1 | Spurious emission | | +| Test Model 1 | Error vector magnitude | | +| Test Model 3 | Peak code domain error | | +| Test Model 6 | Relative code domain error | | + +## 5.8 Format and interpretation of tests + +Each test in the following clauses has a standard format: + +# **X Title** + +All tests are applicable to all equipment within the scope of the present document, unless otherwise stated. + +## **X.1 Definition and applicability** + +This subclause gives the general definition of the parameter under consideration and specifies whether the test is applicable to all equipment or only to a certain subset. + +## **X.2 Minimum Requirements** + +This subclause is an informative copy of the Minimum Requirement defined by the core specification. + +In addition, this subclause contains the reference to the subclause to the 3GPP reference (or core) specification which defines the Minimum Requirement. + +## **X.3 Test purpose** + +This subclause defines the purpose of the test. + +## **X.4 Method of test** + +### **X.4.1 Initial conditions** + +This subclause defines the initial conditions for each test, including the basic measurement set-up. + +### **X.4.2 Procedure** + +This subclause describes the steps necessary to perform the test and provides further details of the test definition like point of access (e.g. antenna port), domain (e.g. frequency-span), range, weighting (e.g. bandwidth), and algorithms (e.g. averaging). + +## **X.5 Test Requirements** + +This subclause defines the pass/fail criteria for the equipment under test. See subclause 5.3 Interpretation of measurement results. + +## 5.9 Repeater configurations + +### 5.9.1 Power supply options + +If the repeater is supplied with a number of different power supply configurations, it may not be necessary to test RF parameters for each of the power supply options, provided that it can be demonstrated that the range of conditions over which the equipment is tested is at least as great as the range of conditions due to any of the power supply configurations. + +### 5.9.2 Combining of Repeaters + +If the repeater is intended for combination with additional apparatus connected to a repeater port and this combination is supplied as a system, the combination of repeater together with the additional apparatus shall also fulfil the repeater requirements. E.g. if the repeater is intended for combination such that multiple repeaters amplify the same signals into the same ports the combination shall also fulfil the repeater requirements. + +An example of such a configuration is shown in figure 5.1 + +![Figure 5.1: Example of repeater configuration. The diagram shows a signal path starting from a 'Test port' on the left, entering a 'Combiner / Splitter' block. The output of this block splits into two parallel 'Repeater' blocks. The outputs of these two repeaters are combined in a second 'Combiner / Splitter' block, which then connects to another 'Test port' on the right. Vertical dashed lines labeled 'Antenna connector' are positioned between the first combiner/splitter and the repeaters, and between the repeaters and the second combiner/splitter.](627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg) + +Figure 5.1: Example of repeater configuration. The diagram shows a signal path starting from a 'Test port' on the left, entering a 'Combiner / Splitter' block. The output of this block splits into two parallel 'Repeater' blocks. The outputs of these two repeaters are combined in a second 'Combiner / Splitter' block, which then connects to another 'Test port' on the right. Vertical dashed lines labeled 'Antenna connector' are positioned between the first combiner/splitter and the repeaters, and between the repeaters and the second combiner/splitter. + +Figure 5.1: Example of repeater configuration + +# 6 Output power + +Maximum output power, $P_{max}$ , of the Repeater is the mean power level per carrier at maximum Repeater gain that the manufacturer has declared to be available at the antenna connector. + +## 6.1 Maximum output power + +### 6.1.1 Definition and applicability + +Maximum output power, $P_{max}$ , of the Repeater is the mean power level per carrier measured at the antenna connector in specified reference condition. + +### 6.1.2 Minimum Requirements + +In normal conditions as specified in section 5.4.1, the Repeater maximum output power shall remain within limits specified in Table 6.1 relative to the manufacturer's rated output power. + +Table 6.1: Repeater output power; normal conditions + +| Rated output power | Limit | +|----------------------|-----------------| +| $P \geq 43$ dBm | +2 dB and -2 dB | +| $39 \leq P < 43$ dBm | +2 dB and -2 dB | +| $31 \leq P < 39$ dBm | +2 dB and -2 dB | +| $P < 31$ dBm | +3 dB and -3 dB | + +In extreme conditions as specified in section 5.4.2 and 5.4.4, the Repeater maximum output power shall remain within limits specified in Table 6.2 relative to the manufacturer's rated output power. + +**Table 6.2: Repeater output power; extreme conditions** + +| Rated output power | Limit | +|----------------------|---------------------| +| $P \geq 43$ dBm | +2,5 dB and -2,5 dB | +| $39 \leq P < 43$ dBm | +2,5 dB and -2,5 dB | +| $31 \leq P < 39$ dBm | +2,5 dB and -2,5 dB | +| $P < 31$ dBm | +4 dB and -4 dB | + +In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the ranges defined for the Normal test environment in subclause 5.4.1. + +### 6.1.3 Test purpose + +To verify that the Repeater maximum output power is within the limit specified in 6.1.2. + +### 6.1.4 Method of test + +#### 6.1.4.1 Initial conditions + +- 1) Set-up the equipment as shown in annex A. +- 2) Connect the signal generator equipment to the Repeater input port. +- 3) Connect the power measuring equipment to the Repeater output port. + +#### 6.1.4.2 Procedure + +- 1) Set the signal generator to transmit a signal modulated with a combination of PCCPCH, SCCPCH and Dedicated Physical Channels specified as test model 1 in TS 25.141. +- 2) Adjust the input power to the Repeater to create the maximum nominal Repeater output power at maximum gain. +- 3) Measure the mean power at the RF output port over a certain slot. +- 4) Increase the power with 10 dB compare to the level obtained in step 2. +- 5) Measure the mean power at the RF output port over a certain slot. + +In addition, on one UARFCN only, the test shall be performed under extreme power supply as defined in subclause 5.4.4 + +NOTE: Tests under extreme power supply also test extreme temperature. + +### 6.1.5 Test Requirements + +In normal conditions as specified in section 5.4.1, the Repeater maximum output power shall remain within limits specified in Table 6.3 relative to the manufacturer's rated output power. + +**Table 6.3: Repeater output power; normal conditions** + +| Rated output power | Carrier frequency | Limit | +|----------------------|------------------------------|---------------------| +| $P \geq 43$ dBm | $f \leq 3,0$ GHz | +2,7 dB and -2,7 dB | +| | $3,0$ GHz $< f \leq 4,2$ GHz | +3,0 dB and -3,0 dB | +| $39 \leq P < 43$ dBm | $f \leq 3,0$ GHz | +2,7 dB and -2,7 dB | +| | $3,0$ GHz $< f \leq 4,2$ GHz | +3,0 dB and -3,0 dB | +| $31 \leq P < 39$ dBm | $f \leq 3,0$ GHz | +2,7 dB and -2,7 dB | +| | $3,0$ GHz $< f \leq 4,2$ GHz | +3,0 dB and -3,0 dB | +| $P < 31$ dBm | $f \leq 3,0$ GHz | +3,7 dB and -3,7 dB | +| | $3,0$ GHz $< f \leq 4,2$ GHz | +4,0 dB and -4,0 dB | + +In extreme conditions as specified in section 5.4.2 and 5.4.4, the Repeater maximum output power shall remain within limits specified in Table 6.4 relative to the manufacturer's rated output power. + +**Table 6.4: Repeater output power; extreme conditions** + +| Rated output power | Carrier frequency | Limit | +|------------------------------|--------------------------------------------|---------------------| +| $P \geq 43 \text{ dBm}$ | $f \leq 3,0 \text{ GHz}$ | +3,2 dB and -3,2 dB | +| | $3,0 \text{ GHz} < f \leq 4,2 \text{ GHz}$ | +3,5 dB and -3,5 dB | +| $39 \leq P < 43 \text{ dBm}$ | $f \leq 3,0 \text{ GHz}$ | +3,2 dB and -3,2 dB | +| | $3,0 \text{ GHz} < f \leq 4,2 \text{ GHz}$ | +3,5 dB and -3,5 dB | +| $31 \leq P < 39 \text{ dBm}$ | $f \leq 3,0 \text{ GHz}$ | +3,2 dB and -3,2 dB | +| | $3,0 \text{ GHz} < f \leq 4,2 \text{ GHz}$ | +3,5 dB and -3,5 dB | +| $P < 31 \text{ dBm}$ | $f \leq 3,0 \text{ GHz}$ | +4,7 dB and -4,7 dB | +| | $3,0 \text{ GHz} < f \leq 4,2 \text{ GHz}$ | +5,0 dB and -5,0 dB | + +In certain regions, the minimum requirement for normal conditions may apply also for some conditions outside the ranges defined for the Normal test environment in subclause 5.4.1. + +NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non zero. The Test Tolerance for this test is defined in subclause 5.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex B. + +# 7 Frequency stability + +Frequency error is the measure of the difference between the frequency of the received signal and the frequency of the re-transmitted signal. + +## 7.1 Definition and applicability + +The frequency stability is a measure of the frequency deviation of the output signal with respect to the input signal. The test shall address the uplink and the downlink path of the Repeater. + +## 7.2 Minimum Requirement + +In normal conditions as specified in section 5.4.1 the frequency deviation shall be within $\pm 0,01 \text{ ppm}$ . + +## 7.3 Test purpose + +To verify that the Frequency Error is within the limit specified in 7.2. + +## 7.4 Method of test + +### 7.4.1 Initial conditions + +- 1) Set-up the equipment as shown in annex A. +- 2) Connect the cw signal generator equipment to the Repeater input port. +- 3) Connect the frequency counter to the Repeater output port. Both the signal generator and the frequency counter shall use the same reference frequency. +- 4) Adjust the input power to the Repeater to create the maximum nominal Repeater output power as declared by the manufacturer at maximum gain. + +### 7.4.2 Procedure + +Measure the frequency error for both paths uplink and downlink of the Repeater. + +## 7.5 Test requirements + +The measurement result of 7.4.2 shall not exceed: + +$$| f_{\text{IN}} - f_{\text{out}} | \leq (f_{\text{out}} * 0,01 \text{ ppm}) + 12 \text{ Hz}$$ + +# 8 Out of band gain + +## 8.1 Definitions and applicability + +Out of band gain refers to the gain of the Repeater immediately outside the pass band. The measurements shall apply to both paths uplink and downlink of the Repeater. + +## 8.2 Minimum Requirements + +The intended use of a repeater in a system is to amplify the in band signals and not to amplify the out of band emission of the donor base station. + +In the intended application of the repeater, the out of band gain is less than the donor coupling loss. + +The repeater minimum donor coupling loss shall be declared by the manufacturer. This is this the minimum required attenuation between the donor BS and the repeater for proper repeater operation. + +In normal conditions as specified in section 5.4.1 the gain outside the pass band shall not exceed the maximum level specified in Table 8.1, where: + +- $f\_offset$ is the distance from the centre frequency of the first or last 5 MHz channel within the pass band. + +**Table 8.1: Out of band gain limits 1** + +| Frequency offset from the carrier frequency, $f\_offset$ | Maximum gain | +|----------------------------------------------------------|--------------| +| $2,7 \leq f\_offset < 3,5 \text{ MHz}$ | 60 dB | +| $3,5 \leq f\_offset < 7,5 \text{ MHz}$ | 45 dB | +| $7,5 \leq f\_offset < 12,5 \text{ MHz}$ | 45 dB | +| $12,5 \text{ MHz} \leq f\_offset$ | 35 dB | + +For $12,5 \text{ MHz} \leq f\_offset$ the out of band gain shall not exceed the maximum gain of table 8.2 or the maximum gain stated in table 8.1 whichever is lower. + +**Table 8.2: Out of band gain limits 2** + +| Repeater maximum output power as in 9.1.1.1 | Maximum gain | +|---------------------------------------------|---------------------------------------------------------------------------| +| $P < 31 \text{ dBm}$ | Out of band gain $\leq$ minimum donor coupling loss | +| $31 \text{ dBm} \leq P < 43 \text{ dBm}$ | Out of band gain $\leq$ minimum donor coupling loss | +| $P \geq 43 \text{ dBm}$ | Out of band gain $\leq$ minimum donor coupling loss – (P-43dBm) | +| Note: | The out of band gain is considered with $12,5 \text{ MHz} \leq f\_offset$ | + +## 8.3 Test purpose + +The purpose of this test is to verify that the Repeater meets the out of band gain requirements as specified in TS 25.106. + +## 8.4 Method of test + +### 8.4.1 Initial conditions + +Set-up the equipment as shown in annex A. + +The test shall be performed with an offset between CW-signal and the first or last 5 MHz channel within the pass band of 2,7 MHz, 3 MHz, 3,5 MHz, 5 MHz, 7,5 MHz, 10 MHz, 12,5 MHz, 15 MHz and 20 MHz, excluding other pass + +bands. In addition the test shall also be performed for all harmonic frequencies of the repeaters pass band up to 12,75 GHz, for operating bands $f \leq 3,0\text{GHz}$ , or up to the 5th harmonic of the upper frequency edge of the DL or UL operating band, for operating bands $f > 3,0\text{GHz}$ . + +### 8.4.2 Procedure + +- 1) Set the Repeater to maximum gain. +- 2) Set the signal generator to generate a CW-signal, applied to the input port of the Repeater. The power level of the RF input signal shall be at least 5 dB below the power level which, when applied within the pass band, would produce the maximum rated output power, as declared by the manufacturer. This is to ensure that the equipment is operating in the linear output range. +- 3) The average output power in each case shall be measured using a spectrum analyser connected to the output port of the Repeater and the net gain shall be recorded compared to table 8.3 or table 8.4 whichever is lower. +- 4) With the same input power as in step 1) set the repeater gain to the minimum specified by the manufacturer. +- 5) The average output power in each case shall be measured using a spectrum analyser connected to the output port of the Repeater and the net gain shall be recorded and compared to table 8.3 or table 8.4 whichever is lower. + +## 8.5 Test requirements + +**Table 8.3: Out of band gain limits** + +| Frequency offset from the carrier frequency, $f\_offset$ | Maximum gain | +|----------------------------------------------------------|--------------| +| $2,7 \leq f\_offset < 3,5\text{ MHz}$ | 60,5 dB | +| $3,5 \leq f\_offset < 7,5\text{ MHz}$ | 45,5 dB | +| $7,5 \leq f\_offset < 12,5\text{ MHz}$ | 45,5 dB | +| $12,5\text{ MHz} \leq f\_offset$ | 35,5 dB | + +**Table 8.4: Out of band gain limits 2** + +| Repeater maximum output power as in 9.1.1.1 | Carrier frequency | Maximum gain | +|---------------------------------------------|------------------------------------------|--------------------------------------------------------------------------| +| $P < 31\text{ dBm}$ | $f \leq 3,0\text{ GHz}$ | Out of band gain $\leq$ minimum donor coupling loss + 0,5 dB | +| | $3,0\text{ GHz} < f \leq 4,2\text{ GHz}$ | Out of band gain $\leq$ minimum donor coupling loss + 0,8 dB | +| $31\text{ dBm} \leq P < 43\text{ dBm}$ | $f \leq 3,0\text{ GHz}$ | Out of band gain $\leq$ minimum donor coupling loss + 0,5 dB | +| | $3,0\text{ GHz} < f \leq 4,2\text{ GHz}$ | Out of band gain $\leq$ minimum donor coupling loss + 0,8 dB | +| $P \geq 43\text{ dBm}$ | $f \leq 3,0\text{ GHz}$ | Out of band gain $\leq$ minimum donor coupling loss – (P-43dBm) + 0,5 dB | +| | $3,0\text{ GHz} < f \leq 4,2\text{ GHz}$ | Out of band gain $\leq$ minimum donor coupling loss – (P-43dBm) + 0,8 dB | + +NOTE: The donor coupling loss is considered with $12,5\text{ MHz} \leq f\_offset$ + +# 9 Unwanted emission + +Unwanted emissions consist of out-of-band emissions and spurious emissions [4]. Out of band emissions are unwanted emissions immediately outside the pass band bandwidth resulting from the modulation process and non-linearity in the transmitter, but excluding spurious emissions. Spurious emissions are emissions which are caused by unwanted transmitter effects such as harmonics emission, parasitic emission, intermodulation products and frequency conversion products, but exclude out of band emissions. + +The out-of-band emissions requirement for repeater is specified both in terms operating band unwanted emissions and protection of the BS receiver in the operating band. The Operating band unwanted emissions define all unwanted emissions in the repeater operating band plus the frequency ranges 10 MHz above and 10 MHz below that band. Unwanted emissions outside of this frequency range are limited by a spurious emissions requirement. + +## 9.1 Out of band emission + +### 9.1.1 Void + +### 9.1.2 Operating band unwanted emissions + +#### 9.1.2.1 Definitions and applicability + +Operating band unwanted emissions comprise an emission mask applied outside the repeater passband and a general requirement applied outside the mask but inside the frequency range of the operating band unwanted emissions. + +The general operating band unwanted emissions limits are given in table 9.0. + +**Table 9.0: General operating band unwanted emissions requirements** + +| Frequency range of operating band | Category A | Category B | Measurement bandwidth | Notes | +|-----------------------------------|------------|------------|-----------------------|-------| +| $\leq 1$ GHz | -13 dBm | -16 dBm | 100 kHz | 1,2 | +| $\geq 1$ GHz | -13 dBm | -15 dBm | 1 MHz | 2,3 | + +NOTE 1: Bandwidth as in ITU-R Recommendation SM.329 [4], s4.1 + +NOTE 2: Limit based on ITU-R Recommendation SM.329 [4], s4.3 and Annex 7 + +NOTE 3: Bandwidth as in ITU-R Recommendation SM.329 [4], s4.1. Upper frequency as in ITU-R SM.329 [4], s2.5 table 1 + +The masks defined in Table 9.1, Table 9.2, Table 9.3, and Table 9.4 below may be mandatory in certain regions. In other regions this mask may not be applied. + +#### 9.1.2.2 Minimum Requirements + +For regions where this clause applies, the requirement shall be met by a repeater's RF-signal output at maximum gain with WCDMA signals in the pass band of the Repeater, at levels that produce the maximum rated output power per channel. In normal conditions as specified in section 5.4.1 emissions shall not exceed the maximum level specified in Table 9.1, Table 9.2, Table 9.3, and Table 9.4 for the appropriate Repeater maximum output power, in the frequency range from $\Delta f = 2,5$ MHz to $\Delta f_{\max}$ from the 5 MHz channel, where: + +- $\Delta f$ is the separation between the centre frequency of first or last 5 MHz channel used in the pass band and the nominal -3 dB point of the measuring filter closest to the carrier frequency. +- $f_{\text{offset}}$ is the separation between the centre frequency of first or last 5 MHz channel in the pass band and the centre of the measuring filter. +- $f_{\text{offsetmax}}$ is 12,5 MHz. +- $\Delta f_{\max}$ is equal to $f_{\text{offsetmax}}$ minus half of the bandwidth of the measurement filter. + +To select the table of the maximum level for the spectrum emission mask test, use the maximum output power as defined in subclause 3.1 Definition. If one channel is used for the spectrum emission mask test use this power for the selection. If two channels are used for the spectrum emission mask test use the power of one of these. + +**Table 9.1: Emission mask values, maximum output power $P \geq 43$ dBm** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 3) | Measurement bandwidth (Note 2) | +|---------------------------------------------------------------|----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|--------------------------------| +| $2,5 \text{ MHz} \leq \Delta f < 2,7 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 2,715 \text{ MHz}$ | $-14 \text{ dBm} + \Delta P$ | 30 kHz | +| $2,7 \text{ MHz} \leq \Delta f < 3,5 \text{ MHz}$ | $2,715 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | $-14 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 2,715 \right) \text{ dB} + \Delta P$ | 30 kHz | +| (Note 1) | $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | $-26 \text{ dBm} + \Delta P$ | 30 kHz | +| $3,5 \text{ MHz} \leq \Delta f < 7,5 \text{ MHz}$ | $4,0 \text{ MHz} \leq f\_offset < 8,0 \text{ MHz}$ | $-13 \text{ dBm} + \Delta P$ | 1 MHz | +| $7,5 \text{ MHz} \leq \Delta f \leq f_{\max}$ | $8,0 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $-13 \text{ dBm}$ | 1 MHz | + +NOTE 3: +- for carrier frequency $f \leq 3,0 \text{ GHz}$ : $\square \Delta P = 0 \text{ dB}$ ; +- for carrier frequency $3,0 \text{ GHz} < f \leq 4,2 \text{ GHz}$ : $\Delta P = 0,3 \text{ dB}$ + +**Table 9.2: Emission mask values, maximum output power $39 \leq P < 43$ dBm** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 3) | Measurement bandwidth (Note 2) | +|---------------------------------------------------------------|----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|--------------------------------| +| $2,5 \text{ MHz} \leq \Delta f < 2,7 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 2,715 \text{ MHz}$ | $-14 \text{ dBm} + \Delta P$ | 30 kHz | +| $2,7 \text{ MHz} \leq \Delta f < 3,5 \text{ MHz}$ | $2,715 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | $-14 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 2,715 \right) \text{ dB} + \Delta P$ | 30 kHz | +| (Note 1) | $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | $-26 \text{ dBm} + \Delta P$ | 30 kHz | +| $3,5 \text{ MHz} \leq \Delta f < 7,5 \text{ MHz}$ | $4,0 \text{ MHz} \leq f\_offset < 8,0 \text{ MHz}$ | $-13 \text{ dBm} + \Delta P$ | 1 MHz | +| $7,5 \text{ MHz} \leq \Delta f \leq f_{\max}$ | $8,0 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $P - 56 \text{ dB}$ | 1 MHz | + +NOTE 3: +- for carrier frequency $f \leq 3,0 \text{ GHz}$ : $\square \Delta P = 0 \text{ dB}$ ; +- for carrier frequency $3,0 \text{ GHz} < f \leq 4,2 \text{ GHz}$ : $\square \Delta P = 0,3 \text{ dB}$ + +**Table 9.3: Emission mask values, maximum output power $31 \leq P < 39$ dBm** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement (Note 3) | Measurement bandwidth (Note 2) | +|---------------------------------------------------------------|----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|--------------------------------| +| $2,5 \text{ MHz} \leq \Delta f < 2,7 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 2,715 \text{ MHz}$ | $P - 53 \text{ dB} + \Delta P$ | 30 kHz | +| $2,7 \text{ MHz} \leq \Delta f < 3,5 \text{ MHz}$ | $2,715 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | $P - 53 \text{ dB} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 2,715 \right) \text{ dB} + \Delta P$ | 30 kHz | +| (Note 1) | $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | $P - 65 \text{ dB} + \Delta P$ | 30 kHz | +| $3,5 \text{ MHz} \leq \Delta f < 7,5 \text{ MHz}$ | $4,0 \text{ MHz} \leq f\_offset < 8,0 \text{ MHz}$ | $P - 52 \text{ dB} + \Delta P$ | 1 MHz | +| $7,5 \text{ MHz} \leq \Delta f \leq f_{\max}$ | $8,0 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $P - 56 \text{ dB}$ | 1 MHz | + +NOTE 3: +- for carrier frequency $f \leq 3,0 \text{ GHz}$ : $\square \Delta P = 0 \text{ dB}$ ; +- for carrier frequency $3,0 \text{ GHz} < f \leq 4,2 \text{ GHz}$ : $\square \Delta P = 0,3 \text{ dB}$ + +**Table 9.4: Emission mask values, maximum output power P < 31 dBm** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement | Measurement bandwidth (Note 2) | +|---------------------------------------------------------------|----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|--------------------------------| +| $2,5 \text{ MHz} \leq \Delta f < 2,7 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 2,715 \text{ MHz}$ | $-22 \text{ dBm} + \Delta P$ | 30 kHz | +| $2,7 \text{ MHz} \leq \Delta f < 3,5 \text{ MHz}$ | $2,715 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | $-22 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 2,715 \right) \text{ dB} + \Delta P$ | 30 kHz | +| (Note 1) | $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | $-34 \text{ dBm} + \Delta P$ | 30 kHz | +| $3,5 \text{ MHz} \leq \Delta f < 7,5 \text{ MHz}$ | $4,0 \text{ MHz} \leq f\_offset < 8,0 \text{ MHz}$ | $-21 \text{ dBm} + \Delta P$ | 1 MHz | +| $7,5 \text{ MHz} \leq \Delta f \leq f\_max$ | $8,0 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | $-25 \text{ dBm}$ | 1 MHz | + +NOTE 3: +- for carrier frequency $f \leq 3,0 \text{ GHz}$ : $\square \Delta P = 0 \text{ dB}$ ; +- for carrier frequency $3,0 \text{ GHz} < f \leq 4,2 \text{ GHz}$ : $\square \Delta P = 0,3 \text{ dB}$ + +For operation in band II, IV, V, X, XII, XIII, XIV, XXV and XXVI, the applicable additional requirement in Tables 9.4A, 9.4B or 9.4C apply in addition to the minimum requirements in Tables 9.1 to 9.4. + +**Table 9.4A: Additional emission mask values for Bands II, IV, X, XXV** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Additional requirement | Measurement bandwidth (Note 2) | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------|--------------------------------| +| $2,5 \text{ MHz} \leq \Delta f < 3,5 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | $-15 \text{ dBm}$ | 30 kHz | +| $3,5 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $4,0 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | $-13 \text{ dBm}$ | 1 MHz | + +**Table 9.4B: Additional emission mask values for Band V and XXVI** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Additional requirement | Measurement bandwidth (Note 2) | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------|--------------------------------| +| $2,5 \text{ MHz} \leq \Delta f < 3,5 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | $-15 \text{ dBm}$ | 30 kHz | +| $3,5 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $3,55 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | $-13 \text{ dBm}$ | 100 kHz | + +**Table 9.4C: Additional emission mask values for Bands XII, XIII, XIV** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Additional requirement | Measurement bandwidth (Note 2) | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------|--------------------------------| +| $2,5 \text{ MHz} \leq \Delta f < 2,6 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 2,615 \text{ MHz}$ | $-13 \text{ dBm}$ | 30 kHz | +| $2,6 \text{ MHz} \leq \Delta f \leq \Delta f_{max}$ | $2,65 \text{ MHz} \leq f\_offset < f\_offset_{max}$ | $-13 \text{ dBm}$ | 100 kHz | + +In certain regions the following requirement may apply for protection of DTT. For UTRA Repeater operating in Band XX, the level of emissions in the band 470-790 MHz, measured in an 8MHz filter bandwidth on centre frequencies $F_{filter}$ according to Table 9.4D, shall not exceed the maximum emission level $P_{EM,N}$ declared by the manufacturer. + +**Table 9.4.D: Declared emissions levels for protection of DTT** + +| Filter centre frequency, $F_{\text{filter}}$ | Measurement bandwidth | Declared emission level [dBm] | +|---------------------------------------------------------------------|-----------------------|-------------------------------| +| $F_{\text{filter}} = 8 \cdot N + 306$ (MHz);
$21 \leq N \leq 60$ | 8 MHz | $P_{\text{EM,N}}$ | + +NOTE: The regional requirement is defined in terms of EIRP (effective isotropic radiated power), which is dependent on both the repeater emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The requirement defined above provides the characteristics of the repeater needed to verify compliance with the regional requirement. Compliance with the regional requirement can be determined using the method outlined in TS 25.104 [1] Annex D. + +In certain regions, the following requirements may apply to UTRA repeaters operating in Band XXXII within 1452-1492 MHz. The level of unwanted emissions, measured on centre frequencies $f_{\text{offset}}$ with filter bandwidth, according to Table 9.4E shall neither exceed the maximum emission level $P_{\text{EM,B32,a}}$ , $P_{\text{EM,B32,b}}$ nor $P_{\text{EM,B32,c}}$ declared by the manufacturer. + +**Table 9.4E: Declared operating band XXXII unwanted emission within 1452-1492 MHz** + +| Frequency offset of measurement filter centre frequency, $f_{\text{offset}}$ | Declared emission level [dBm] | Measurement bandwidth | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|-----------------------| +| 5 MHz | $P_{\text{EM,B32,a}}$ | 5 MHz | +| 10 MHz | $P_{\text{EM,B32,b}}$ | 5 MHz | +| $15 \text{ MHz} \leq f_{\text{offset}} \leq f_{\text{offset,max,B32}}$ | $P_{\text{EM,B32,c}}$ | 5 MHz | +| NOTE 1: f_{\text{offset,max,B32}} denotes the frequency difference between the lower channel carrier frequency and 1454.5 MHz, and the frequency difference between the upper channel carrier frequency and 1489.5 MHz for the set channel position. | | | + +NOTE: The regional requirement, included in [14], is defined in terms of EIRP per antenna, which is dependent on both the repeater emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The requirement defined above provides the characteristics of the base station needed to verify compliance with the regional requirement. The assessment of the EIRP level is described in Annex H of TS36.104 [15]. + +In certain regions, the following requirement may apply to UTRA repeaters operating in Band XXXII within 1452-1492 MHz for the protection of services in spectrum adjacent to the frequency range 1452-1492 MHz. The level of emissions, measured on centre frequencies $F_{\text{filter}}$ with filter bandwidth according to Table 9.4F shall neither exceed the maximum emission level $P_{\text{EM,B32,d}}$ nor $P_{\text{EM,B32,e}}$ declared by the manufacturer. This requirement applies in the frequency range 1429-1518 MHz even though part of the range falls in the spurious domain. + +**Table 9.4F: Operating band XXXII declared emission outside 1452-1492 MHz** + +| Filter centre frequency, $F_{\text{filter}}$ | Declared emission level [dBm] | Measurement bandwidth | +|---------------------------------------------------------------------|-------------------------------|-----------------------| +| $1429.5 \text{ MHz} \leq F_{\text{filter}} \leq 1448.5 \text{ MHz}$ | $P_{\text{EM,B32,d}}$ | 1 MHz | +| $F_{\text{filter}} = 1450.5 \text{ MHz}$ | $P_{\text{EM,B32,e}}$ | 3 MHz | +| $F_{\text{filter}} = 1493.5 \text{ MHz}$ | $P_{\text{EM,B32,e}}$ | 3 MHz | +| $1495.5 \text{ MHz} \leq F_{\text{filter}} \leq 1517.5 \text{ MHz}$ | $P_{\text{EM,B32,d}}$ | 1 MHz | + +NOTE: The regional requirement, included in [14], is defined in terms of EIRP, which is dependent on both the repeater emissions at the antenna connector and the deployment (including antenna gain and feeder loss). The requirement defined above provides the characteristics of the base station needed to verify compliance with the regional requirement. The assessment of the EIRP level is described in Annex H of TS36.104 [15]. + +Note for Tables 9.1, 9.2, 9.3, 9.4, 9.4A, 9.4B and 9.4C: + +NOTE 1: This frequency range ensures that the range of values of $f_{\text{offset}}$ is continuous. + +**NOTE 2** As a general rule, the resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. However, to improve measurement accuracy, sensitivity and efficiency, the resolution bandwidth can be smaller than the measurement bandwidth. When the resolution bandwidth is smaller than the measurement bandwidth, the result should be integrated over the measurement bandwidth in order to obtain the equivalent noise bandwidth of the measurement bandwidth. + +#### 9.1.2.3 Test purpose + +The purpose of this test is to verify that the Repeater meet the spectrum emission requirements as specified in TS 25.106. + +#### 9.1.2.4 Method of test + +##### 9.1.2.4.1 Initial conditions + +A measurement set-up is shown in annex A + +- 1) Connect a signal generator to the input port of the Repeater for tests of repeaters with a pass band corresponding to one 5 MHz channel. If the pass band corresponds to two or more 5 MHz carriers, two signal generators with a combining circuit or one signal generator with the ability to generate several WCDMA carriers is connected to the input. The signals shall be de-correlated as described in TS 25.141 [11], clause 6.1.1.6.3 of equal power. +- 2) Measurements with an offset from the carrier centre frequency between 2,515 MHz and 4,0 MHz shall use a 30 kHz measurement bandwidth. +- 3) Measurements with an offset from the carrier centre frequency between 4,0 MHz and ( $\Delta f_{max} - 500\text{ kHz}$ ) shall use a 1 MHz measurement bandwidth. The 1MHz measurement bandwidth may be calculated by integrating multiple 50 kHz or narrower filter measurements. +- 4) Detection mode: True RMS. + +##### 9.1.2.4.2 Procedures + +- 1) Set the Repeater to maximum gain. +- 2) Set the signal generator(s) to generate signal(s) in accordance to test model 1, TS 25.141 subclause 6.2.1.1.1, at level(s) which produce the manufacturer specified maximum output power at maximum gain. +- 3) Measure the emission at the specified frequencies with specified measurement bandwidth and note that the measured value does not exceed the specified value. +- 4) Increase the power with 10 dB compare to the level obtained in step 2. +- 5) Measure the emission at the specified frequencies with specified measurement bandwidth and note that the measured value does not exceed the specified value. +- 6) If the pass band corresponds to more than two consecutive nominal 5 MHz channels, repeat step 2) to 5) with any combination of two WCDMA modulated signals of equal power in the repeaters pass band. +- 7) Switch off the signal generator. +- 8) Measure the emission at the specified frequencies with specified measurement bandwidth and note that the measured value does not exceed the specified value. + +#### 9.1.2.5 Test requirements + +The measurement result of step 3 and 5 of 9.1.4.2 shall not exceed the maximum level specified in tables 9.5 to 9.8 for the appropriate Repeater maximum output power. + +**Table 9.5: Emission mask values, maximum output power $P \geq 43$ dBm** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement Band (Note 1) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|-----------------------| +| $2,5 \text{ MHz} \leq \Delta f < 2,7 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 2,715 \text{ MHz}$ | $-12,5 \text{ dBm} + \Delta P$ | 30 kHz | +| $2,7 \text{ MHz} \leq \Delta f < 3,5 \text{ MHz}$ | $2,715 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | $-12,5 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 2,715 \right) \text{ dB} + \Delta P$ | 30 kHz | +| | $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | $-24,5 \text{ dBm} + \Delta P$ | 30 kHz | +| $3,5 \text{ MHz} \leq \Delta f < 7,5 \text{ MHz}$ | $4,0 \text{ MHz} \leq f\_offset < 8,0 \text{ MHz}$ | $-11,5 \text{ dBm} + \Delta P$ | 1 MHz | +| $7,5 \text{ MHz} \leq \Delta f \leq f_{\max}$ | $8,0 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $-11,5 \text{ dBm}$ | 1 MHz | + +NOTE 1: +- for carrier frequency $f \leq 3,0 \text{ GHz}$ : $\square \Delta P = 0 \text{ dB}$ ; +- for carrier frequency $3,0 \text{ GHz} < f \leq 4,2 \text{ GHz}$ : $\square \Delta P = 0,3 \text{ dB}$ + +**Table 9.6: Emission mask values, maximum output power $39 \leq P < 43$ dBm** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement Band (Note 1) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|-----------------------| +| $2,5 \text{ MHz} \leq \Delta f < 2,7 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 2,715 \text{ MHz}$ | $-12,5 \text{ dBm} + \Delta P$ | 30 kHz | +| $2,7 \text{ MHz} \leq \Delta f < 3,5 \text{ MHz}$ | $2,715 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | $-12,5 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 2,715 \right) \text{ dB} + \Delta P$ | 30 kHz | +| | $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | $-24,5 \text{ dBm} + \Delta P$ | 30 kHz | +| $3,5 \text{ MHz} \leq \Delta f < 7,5 \text{ MHz}$ | $4,0 \text{ MHz} \leq f\_offset < 8,0 \text{ MHz}$ | $-11,5 \text{ dBm} + \Delta P$ | 1 MHz | +| $7,5 \text{ MHz} \leq \Delta f \leq f_{\max}$ | $8,0 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $P - 54,5 \text{ dB}$ | 1 MHz | + +NOTE 1: +- for carrier frequency $f \leq 3,0 \text{ GHz}$ : $\square \Delta P = 0 \text{ dB}$ ; +- for carrier frequency $3,0 \text{ GHz} < f \leq 4,2 \text{ GHz}$ : $\square \Delta P = 0,3 \text{ dB}$ + +**Table 9.7: Emission mask values, maximum output power $31 \leq P < 39$ dBm** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement Band (Note 1) | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|-----------------------| +| $2,5 \text{ MHz} \leq \Delta f < 2,7 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 2,715 \text{ MHz}$ | $P - 51,5 \text{ dB} + \Delta P$ | 30 kHz | +| $2,7 \text{ MHz} \leq \Delta f < 3,5 \text{ MHz}$ | $2,715 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | $P - 51,5 \text{ dB} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 2,715 \right) \text{ dB} + \Delta P$ | 30 kHz | +| | $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | $P - 63,5 \text{ dB} + \Delta P$ | 30 kHz | +| $3,5 \text{ MHz} \leq \Delta f < 7,5 \text{ MHz}$ | $4,0 \text{ MHz} \leq f\_offset < 8,0 \text{ MHz}$ | $P - 50,5 \text{ dB} + \Delta P$ | 1 MHz | +| $7,5 \text{ MHz} \leq \Delta f \leq f_{\max}$ | $8,0 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $P - 54,5 \text{ dB}$ | 1 MHz | + +NOTE 1: +- for carrier frequency $f \leq 3,0 \text{ GHz}$ : $\square \Delta P = 0 \text{ dB}$ ; +- for carrier frequency $3,0 \text{ GHz} < f \leq 4,2 \text{ GHz}$ : $\square \Delta P = 0,3 \text{ dB}$ + +**Table 9.8: Emission mask values, maximum output power P < 31 dBm** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Test requirement Band (Note 1) | Measurement bandwidth | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|-----------------------| +| $2,5 \text{ MHz} \leq \Delta f < 2,7 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 2,715 \text{ MHz}$ | $-20,5 \text{ dBm} + \Delta P$ | 30 kHz | +| $2,7 \text{ MHz} \leq \Delta f < 3,5 \text{ MHz}$ | $2,715 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | $-20,5 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 2,715 \right) \text{ dB} + \Delta P$ | 30 kHz | +| | $3,515 \text{ MHz} \leq f\_offset < 4,0 \text{ MHz}$ | $-32,5 \text{ dBm} + \Delta P$ | 30 kHz | +| $3,5 \text{ MHz} \leq \Delta f < 7,5 \text{ MHz}$ | $4,0 \text{ MHz} \leq f\_offset < 8,0 \text{ MHz}$ | $-19,5 \text{ dBm} + \Delta P$ | 1 MHz | +| $7,5 \text{ MHz} \leq \Delta f \leq f_{\max}$ | $8,0 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $-23,5 \text{ dBm}$ | 1 MHz | +| NOTE 1:
- for carrier frequency $f \leq 3,0 \text{ GHz}$ : $\square \Delta P = 0 \text{ dB}$ ;
- for carrier frequency $3,0 \text{ GHz} < f \leq 4,2 \text{ GHz}$ : $\square \Delta P = 0,3 \text{ dB}$ | | | | + +For operation in band II, IV, V, X, XII, XIII, XIV, XXV, and XXVI the applicable additional requirement in Tables 9.8A, 9.8B or 9.8C apply in addition to the minimum requirements in Tables 9.5 to 9.8. + +**Table 9.8A: Additional emission mask values for Bands II, IV, X, XXV** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Additional requirement | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------|-----------------------| +| $2,5 \text{ MHz} \leq \Delta f < 3,5 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | $-15 \text{ dBm}$ | 30 kHz | +| $3,5 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $4,0 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $-13 \text{ dBm}$ | 1 MHz | + +**Table 9.8B: Additional emission mask values for Band V and XXVI** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Additional requirement | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------|-----------------------| +| $2,5 \text{ MHz} \leq \Delta f < 3,5 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 3,515 \text{ MHz}$ | $-15 \text{ dBm}$ | 30 kHz | +| $3,5 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $3,55 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $-13 \text{ dBm}$ | 100 kHz | + +**Table 9.8C: Additional emission mask values for Bands XII, XIII, XIV** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Additional requirement | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|------------------------|-----------------------| +| $2,5 \text{ MHz} \leq \Delta f < 2,6 \text{ MHz}$ | $2,515 \text{ MHz} \leq f\_offset < 2,615 \text{ MHz}$ | $-13 \text{ dBm}$ | 30 kHz | +| $2,6 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $2,65 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $-13 \text{ dBm}$ | 100 kHz | + +**Table 9.8D: Declared emissions levels for protection of DTT** + +| Filter centre frequency, $F_{\text{filter}}$ | Measurement bandwidth | Declared emission level [dBm] | +|---------------------------------------------------------------------|-----------------------|-------------------------------| +| $F_{\text{filter}} = 8 \cdot N + 306$ (MHz);
$21 \leq N \leq 60$ | 8 MHz | $P_{\text{EM,N}}$ | + +**Table 9.8E: Declared operating band XXXII unwanted emission within 1452-1492 MHz** + +| Frequency offset of measurement filter centre frequency, $f_{\text{offset}}$ | Declared emission level [dBm] | Measurement bandwidth | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|-----------------------| +| 5 MHz | $P_{\text{EM,B32,a}}$ | 5 MHz | +| 10 MHz | $P_{\text{EM,B32,b}}$ | 5 MHz | +| $15 \text{ MHz} \leq f_{\text{offset}} \leq f_{\text{offsetmax, B32}}$ | $P_{\text{EM,B32,c}}$ | 5 MHz | +| NOTE 1: $f_{\text{offsetmax, B32}}$ denotes the frequency difference between the lower channel carrier frequency and 1454.5 MHz, and the frequency difference between the upper channel carrier frequency and 1489.5 MHz for the set channel position. | | | + +**Table 9.4F: Operating band XXXII declared emission outside 1452-1492 MHz** + +| Filter centre frequency, $F_{\text{filter}}$ | Declared emission level [dBm] | Measurement bandwidth | +|---------------------------------------------------------------------|-------------------------------|-----------------------| +| $1429.5 \text{ MHz} \leq F_{\text{filter}} \leq 1448.5 \text{ MHz}$ | $P_{\text{EM,B32,d}}$ | 1 MHz | +| $F_{\text{filter}} = 1450.5 \text{ MHz}$ | $P_{\text{EM,B32,e}}$ | 3 MHz | +| $F_{\text{filter}} = 1493.5 \text{ MHz}$ | $P_{\text{EM,B32,e}}$ | 3 MHz | +| $1495.5 \text{ MHz} \leq F_{\text{filter}} \leq 1517.5 \text{ MHz}$ | $P_{\text{EM,B32,d}}$ | 1 MHz | + +NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in subclause 5.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex B. + +### 9.1.3 Protection of BS receiver in the operating band + +This requirement shall be applied for the protection of UTRA-FDD BS receivers in geographic areas in which UTRA-FDD Repeater and UTRA-FDD BS are deployed. + +The requirement applies at frequencies that are more than 10 MHz below or more than 10 MHz above the repeater pass band. + +#### 9.1.3.1 Minimum Requirement + +This requirement applies to the uplink of the repeater, at maximum gain. + +In the up-link direction of the Repeater the power of any spurious emission shall not exceed: + +**Table 9.11A: Uplink operating band unwanted emission limits for protection of UTRA FDD BS receiver** + +| Maximum Level | Measurement Bandwidth | Note | +|---------------|-----------------------|------| +| -53 dBm | 100 kHz | | + +NOTE 1: These requirements in Table 9.11A for the up link direction of the Repeater reflect what can be achieved with present state of the art technology and are based on a coupling loss of 73 dB between a Repeater and a UTRA FDD BS receiver. + +NOTE 2: The requirements shall be reconsidered when the state of the art technology progresses. + +NOTE 3: The protection of R-GSM is for further study. + +### 9.1.4 Co-existence with services in adjacent frequency bands + +This requirement may be applied for the protection in bands adjacent to bands I or VII, as defined in clause 4.1 in geographic areas in which both an adjacent band service and UTRA are deployed. + +The requirement applies only to the down-link direction of the repeater. + +#### 9.1.4.1 Minimum requirement + +The power of any spurious emission shall not exceed: + +**Table 9.20: UTRA Repeater down-link spurious emissions limits for protection of adjacent band services** + +| Operating Band | Band | Maximum Level | Measurement Bandwidth | Note | +|----------------|---------------|------------------------------------------------|-----------------------|------| +| I | 2100-2105 MHz | $-30 + 3.4 (f - 2100 \text{ MHz}) \text{ dBm}$ | 1 MHz | | +| | 2175-2180 MHz | $-30 + 3.4 (2180 \text{ MHz} - f) \text{ dBm}$ | 1 MHz | | +| VII | 2610-2615 MHz | $-30 + 3.4 (f - 2610 \text{ MHz}) \text{ dBm}$ | 1 MHz | | +| | 2695-2700 MHz | $-30 + 3.4 (2700 \text{ MHz} - f) \text{ dBm}$ | 1 MHz | | + +## 9.2 Spurious emissions + +### 9.2.1 Definition and applicability + +Spurious emissions are emissions which are caused by unwanted transmitter effects such as harmonics emission, parasitic emission, intermodulation products and frequency conversion products, but exclude out of band emissions. This is measured at the Repeater output port. + +The requirements of either subclause 9.2.2.1 or subclause 9.2.2.2 shall apply whatever the type of Repeater considered (one or several pass bands). It applies for all configurations foreseen by the manufacturer's specification. + +The spurious emission limits apply from 9 kHz to 12.75 GHz (or above, as indicated in Table 9.9 and 9.10), excluding the frequency range from 10 MHz below the lowest frequency of the repeaters operating band up to 10 MHz above the highest frequency of the repeaters operating band. Exceptions are the requirement in Table 9.17 and 9.21 that apply also closer than 10 MHz from repeaters operating band. + +Unless otherwise stated, all requirements are measured as mean power (RMS). + +For repeaters capable of supporting both UTRA and E-UTRA, conformance to the UTRA spurious emission requirements can also be demonstrated using E-UTRA spurious emission test methods as described in TS 36.143 [13]. + +### 9.2.2 Minimum Requirements + +In normal conditions as specified in section 5.4.1 the following requirements shall be met. + +#### 9.2.2.1 Spurious emission (Category A) + +The following requirements shall be met in cases where Category A limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [4], are applied. + +At maximum Repeater gain, with WCDMA signals in the pass band of the Repeater, at levels that produce the maximum rated output power per channel, the power of any spurious emission shall not exceed the limits specified in Table 9.9. + +When the power in all channels is increased by 10 dB the requirements shall still be met. + +The requirement shall apply both with or without an input signal applied. + +**Table 9.9: Up-link and down-link: General spurious emissions limits, Category A** + +| Band | Maximum level | Measurement Bandwidth | Notes | | +|-----------------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------|----------------|--| +| 9kHz – 150kHz | -13 dBm | 1 kHz | Note 1 | | +| 150kHz – 30MHz | | 10 kHz | Note 1 | | +| 30MHz – 1GHz | | 100 kHz | Note 1 | | +| 1GHz – 12,75 GHz | | 1 MHz | Note 2 | | +| 12.75 GHz – 5 th harmonic of the upper frequency edge of the DL or UL operating band for DL or UL spurious emissions, respectively | | 1 MHz | Note 2, Note 3 | | +| NOTE 1: Bandwidth as in ITU-R SM.329 [4], s4.1 | | | | | +| NOTE 2: Upper frequency as in ITU-R SM.329 [4], s2.5 table 1 | | | | | +| NOTE 3: Applies only for Band XXII | | | | | + +#### 9.2.2.2 Spurious emission (Category B) + +The following requirements shall be met in cases where Category B limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [4], are applied. + +At maximum Repeater gain, with WCDMA signals in the pass band of the Repeater, at levels that produce the maximum rated power output per channel, the power of any spurious emission shall not exceed the limits specified in Tables 9.10 and 9.10A depending on the declared operating band for the down- and up-link. + +When the power in all channels is increased by 10 dB the requirements shall still be met. + +The requirement shall apply both with or without an input signal applied. + +**Table 9.10: General spurious emissions limits (Category B)** + +| Band | Maximum Level | Measurement Bandwidth | Note | +|-----------------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------|----------------| +| 9 kHz ↔ 150 kHz | -36 dBm | 1 kHz | Note 1 | +| 150 kHz ↔ 30 MHz | -36 dBm | 10 kHz | Note 1 | +| 30 MHz ↔ 1 GHz | -36 dBm | 100 kHz | Note 1 | +| 1 GHz ↔ 12.75 GHz | -30 dBm | 1 MHz | Note 2 | +| 12.75 GHz - 5 th harmonic of the upper frequency edge of the DL or UL operating band for DL or UL spurious emissions, respectively | -30 dBm | 1 MHz | Note 2, Note 3 | +| NOTE 1: Bandwidth as in ITU-R Recommendation SM.329 [4], s4.1 | | | | +| NOTE 2: Bandwidth as in ITU-R Recommendation SM.329 [4], s4.1. Upper frequency as in ITU-R SM.329 [4], s2.5 table 1 | | | | +| NOTE 3: Applies only for Band XXII | | | | + +**Table 9.10A: (Void)****Table 9.10B: (void)****Table 9.10C: (void)****Table 9.10D: (void)****Table 9.10E: (void)****Table 9.10F: (void)****9.2.2.3 Void****9.2.2.4 Co-existence with other systems in the same geographical area** + +These requirements may be applied for the protection of UE, MS and/or BS operating in other frequency bands in the same geographical area. The requirements may apply in geographic areas in which both UTRA FDD Repeater and a system operating in another frequency band than the FDD operating band are deployed. The system operating in the other frequency band may be GSM900, DCS1800, PCS1900, GSM850, E-UTRA FDD and/or UTRA FDD. + +##### 9.2.2.4.1 Minimum Requirements + +The power of any spurious emission shall not exceed the limits of Table 9.13 for a UTRA FDD Repeater where requirements for co-existence with the system listed in the first column apply. + +**Table 9.13: UTRA Repeater up-link and down-link spurious emissions limits in geographic coverage area of systems operating in other frequency bands** + +| System type operating in the same geographical area | Band for co-existence requirement | Maximum Level | Measurement Bandwidth | Note | +|-----------------------------------------------------|-----------------------------------|---------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GSM900 | 921 – 960 MHz | -57 dBm | 100 kHz | This requirement does not apply to UTRA FDD Repeater operating in band VIII. | +| | 876 – 915 MHz | -61 dBm | 100 kHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band VIII, since it is already covered by the requirement in sub-clause 9.1.3. | +| DCS1800 | 1805 – 1880 MHz | -47 dBm | 100 kHz | This requirement does not apply to UTRA FDD Repeater operating in band III. | +| | 1710 – 1785 MHz | -61 dBm | 100 kHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band III, since it is already covered by the requirement in sub-clause 9.1.3. | +| PCS1900 | 1930 – 1990 MHz | -47 dBm | 100 kHz | This requirement does not apply to UTRA FDD Repeater operating in frequency band II or band XXV. | +| | 1850 – 1910 MHz | -61 dBm | 100 kHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in frequency band II or band XXV, since it is already covered by the requirement in sub-clause 9.1.3. | +| GSM850 or CDMA850 | 869 – 894 MHz | -57 dBm | 100 kHz | This requirement does not apply to UTRA FDD Repeater operating in frequency band V or XXVI. | +| | 824 – 849 MHz | -61 dBm | 100 kHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in frequency band V or XXVI, since it is already covered by the requirement in sub-clause 9.1.3. | +| UTRA FDD Band I or E-UTRA Band 1 | 2110 – 2170 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band I. | +| | 1920 – 1980 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band I, since it is already covered by the requirement in sub-clause 9.1.3. | +| UTRA FDD Band II or E-UTRA Band 2 | 1930 – 1990 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV. | +| | 1850 – 1910 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band II or band XXV, since it is already covered by the requirement in sub-clause 9.1.3. | +| UTRA FDD Band III or E-UTRA Band 3 | 1805 – 1880 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III or band IX. | +| | 1710 – 1785 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band III, since it is already covered by the requirement in sub-clause 9.1.3.
This requirement does not apply to the uplink of UTRA FDD Repeater operating in band IX in the frequency range from 1749,9 MHz to 1784,9 MHz, since it is already covered by the requirement in sub-clause 9.1.3. | +| UTRA FDD Band IV or E-UTRA Band 4 | 2110 – 2155 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band IV or band X. | +| | 1710 – 1755 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band IV or band X, since it is already covered by the requirement in sub-clause 9.1.3. | +| UTRA FDD Band V or E-UTRA Band 5 | 869 – 894 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band V or band XXVI. | +| | 824 – 849 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band V or band XXVI, since it is already covered by the requirement in sub-clause 9.1.3. | +| UTRA FDD Band VI or XIX or E-UTRA Band 6, 18 or 19 | 860 – 890 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band V, VI, XIX, XX or XXVI. | +| | 815 – 830 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band V, VI, XIX, XX or XXVI. | +| | 830 – 845 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band VI or XIX, since it is already covered by the requirement in sub-clause 9.1.3. This requirement does not apply to the UL of UTRA FDD Repeater operating in band V, XX or XXVI. | +| | 2620 – 2690 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VII. | + +| | | | | | +|-------------------------------------------------|---------------------|---------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA FDD Band VII or E-UTRA Band 7 | 2500 – 2570 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band VII, since it is already covered by the requirement in sub-clause 9.1.3. | +| UTRA FDD Band VIII or E-UTRA Band 8 | 925 – 960 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VIII. | +| | 880 – 915 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band VIII, since it is already covered by the requirement in sub-clause 9.1.3. | +| UTRA FDD Band IX or E-UTRA Band 9 | 1844.9 – 1879.9 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III or band IX. | +| | 1749.9 – 1784.9 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band III or band IX, since it is already covered by the requirement in sub-clause 9.1.3. | +| UTRA FDD Band X or E-UTRA Band 10 | 2110 – 2170 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band IV or band X. | +| | 1710 – 1770 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band X, since it is already covered by the requirement in sub-clause 9.1.3. This requirement does not apply to the uplink of UTRA FDD Repeater operating in band IV in the frequency range from 1710 MHz to 1755 MHz, since it is already covered by the requirement in sub-clause 9.1.3. | +| UTRA FDD Band XI or XXI or E-UTRA Band 11 or 21 | 1475.9 – 1510.9 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XI, band XXI or band XXXII. | +| | 1427.9 – 1447.9 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band XI, since it is already covered by the requirement in sub-clause 9.1.3. For UTRA repeaters operating in band XXXII, this requirement applies for carriers allocated within 1475.9MHz and 1495.9MHz. | +| | 1447.9 - 1462.9 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band XXI, since it is already covered by the requirement in sub-clause 9.1.3. For UTRA repeaters operating in band XXXII, this requirement applies for carriers allocated within 1475.9MHz and 1495.9MHz. | +| UTRA FDD Band XII or E-UTRA Band 12 | 728 - 746 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XII. | +| | 698 - 716 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band XII, since it is already covered by the requirement in sub-clause 9.1.3. | +| UTRA FDD Band XIII or E-UTRA Band 13 | 746 - 756 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XIII. | +| | 777 - 787 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band XIII, since it is already covered by the requirement in sub-clause 9.1.3. | +| UTRA FDD Band XIV or E-UTRA Band 14 | 758 - 768 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XIV. | +| | 788 - 798 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band XIV, since it is already covered by the requirement in sub-clause 9.1.3. | +| E-UTRA Band 17 | 734 - 746 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XII. | +| | 704 - 716 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band XII, since it is already covered by the requirement in sub-clause 9.1.3. | +| UTRA FDD Band XX or E-UTRA Band 20 | 791 - 821 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XX. | +| | 832 - 862 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band XX, since it is already covered by the requirement in sub-clause 9.1.3. | +| UTRA FDD Band XXII or E-UTRA Band 22 | 3510 - 3590 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXII. | +| | 3410 - 3490 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD Repeater operating in band XXII, since it is already covered by the requirement in sub-clause 9.1.3. | + +| | | | | | +|---------------------------------------|---------------------|---------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRA Band 23 | 2180 - 2200 MHz | -52 dBm | 1 MHz | | +| | 2000 - 2020 MHz | -49 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV, where the limits are defined separately. | +| | 2000 – 2010 MHz | -30 dBm | 1 MHz | This requirement only applies to UTRA FDD Repeater operating in band II or band XXV. This requirement applies starting 5 MHz above the band XXV DL operating band. | +| | 2010 – 2020 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 24 | 525 – 1559 MHz | -52 dBm | 1 MHz | | +| | 1626.5 – 1660.5 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band XXV or E-UTRA Band 25 | 1930 - 1995 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD repeater operating in band II or band XXV. | +| | 1850 - 1915 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD repeater operating in band XXV since it is already covered by the requirement in sub-clause 9.1.3. For UTRA FDD repeater operating in band II, it applies for 1910 MHz to 1915 MHz, while the rest is covered in sub-clause 9.1.3. | +| UTRA FDD Band XXVI or E-UTRA Band 26 | 859 - 894 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD repeater operating in band V or band XXVI. | +| | 814 - 849 MHz | -49 dBm | 1 MHz | This requirement does not apply to the UL of the UTRA FDD repeater operating in band XXVI since it is already covered by the requirement in sub-clause 9.1.3. For UTRA FDD repeater operating in band V, it applies for 814 MHz to 824 MHz, while the rest is covered in sub-clause 9.1.3. | +| E-UTRA Band 27 | 852 - 869 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD repeater operating in band V or band XXVI. | +| | 807 - 824 MHz | -49 dBm | 1 MHz | For UTRA FDD repeater operating in band XXVI, it applies for 807 MHz to 814 MHz, while the rest is covered in sub-clause 9.1.3. | +| E-UTRA Band 28 | 758 - 803 MHz | -52 dBm | 1 MHz | | +| | 703 - 748 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 29 | 717 – 728 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 30 | 2350 - 2360 MHz | -52 dBm | 1 MHz | | +| | 2305 - 2315 MHz | -49 dBm | 1 MHz | | +| E-UTRA Band 31 | 462.5 – 467.5 MHz | -52 dBm | 1 MHz | | +| | 452.5 – 457.5 MHz | -49 dBm | 1 MHz | | +| UTRA FDD Band XXXII or E-UTRA Band 32 | 1452 – 1496 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA repeater operating in Band XI, XXI, or XXXII | + +NOTE 1: The co-existence requirements do not apply for the 10 MHz frequency range immediately outside the repeaters operating band (see Table 4.1). Emission limits for this excluded frequency range may be covered by local or regional requirements. + +NOTE 2: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. + +#### 9.2.2.5 Co-existence with co-located and co-sited base stations + +These requirements may be applied for the protection of other BS receivers when GSM900 and/or DCS1800, PCS1900, GSM850, E-UTRA FDD and/or UTRA FDD BS are co-located with a UTRA FDD Repeater. + +##### 9.2.2.5.1 Minimum Requirements + +The power of any spurious emission shall not exceed the limits of Table 9.14 for a UTRA FDD Repeater where requirements for co-location with the Base Station listed in the first column apply. + +**Table 9.14: UTRA Repeater up-link and down-link spurious emissions limits for Repeater co-located with Base Stations** + +| Type of co-located Base Station | Band for co-location requirement | Maximum Level | Measurement Bandwidth | Note | +|----------------------------------------------------|----------------------------------|---------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GSM900 | 876 – 915 MHz | -98 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band VIII. The sub-clause 9.1.3 requirement applies, but requires a 75dB coupling loss between BS and the repeater UL transmit port. | +| DCS1800 | 1710 – 1785 MHz | -98 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band III. The sub-clause 9.1.3 requirement applies, but requires a 75dB coupling loss between BS and the repeater UL transmit port. | +| PCS1900 | 1850 – 1910 MHz | -98 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band II or band XXV. The sub-clause 9.1.3 requirement applies, but requires a 75dB coupling loss between BS and the repeater UL transmit port. | +| GSM850 or CDMA850 | 824 – 849 MHz | -98 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band V or band XXVI. The sub-clause 9.1.3 requirement applies, but requires a 75dB coupling loss between BS and the repeater UL transmit port. | +| UTRA FDD Band I or E-UTRA Band 1 | 1920 – 1980 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band I. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| UTRA FDD Band II or E-UTRA Band 2 | 1850 – 1910 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band II or band XXV. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| UTRA FDD Band III or E-UTRA Band 3 | 1710 – 1785 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band III. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port.
This requirement does not apply to the uplink of UTRA FDD Repeater operating in band IX in the frequency Range from 1749,9 MHz to 1784,9 MHz, since it is already covered by the requirement in sub-clause 9.1.3, but requires a 73dB coupling loss between base station and the repeater UL transmit port. | +| UTRA FDD Band IV or E-UTRA Band 4 | 1710 – 1755 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band IV or band X. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| UTRA FDD Band V or E-UTRA Band 5 | 824 – 849 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band V or band XXVI. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| UTRA FDD Band VI or XIX or E-UTRA Band 6, 18 or 19 | 815 – 830 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band V, VI, XIX, XX or XXVI. | +| | 830 – 845 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band VI or XIX. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. This requirement does not apply to the UL of UTRA FDD Repeater operating in band V, XX or XXVI. | + +| | | | | | +|-------------------------------------------------|---------------------|---------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA FDD Band VII or E-UTRA Band 7 | 2500 – 2570 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band VII. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| UTRA FDD Band VIII or E-UTRA Band 8 | 880 – 915 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band VIII. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| UTRA FDD Band IX or E-UTRA Band 9 | 1749.9 – 1784.9 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band III or band IX. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| UTRA FDD Band X or E-UTRA Band 10 | 1710 – 1770 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band X. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port.
This requirement does not apply to the uplink of UTRA FDD Repeater operating in band IV in the frequency range from 1710 MHz to 1755 MHz, since it is already covered by the requirement in sub-clause 9.1.3, but requires a 73dB coupling loss between base station and the repeater UL transmit port. | +| UTRA FDD Band XI or XXI or E-UTRA Band 11 or 21 | 1427.9 – 1447.9 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band XI. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. This requirement applies only for operation between 1475.9 MHz and 1495.9 MHz for UTRA FDD repeater operating in band XXXII. | +| | 1447.9 - 1462.9 MHz | -96 dBm | 100 kHz | This requirement does not apply to the up-link of UTRA FDD Repeater operating in band XXI. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. This requirement applies only for operation between 1475.9 MHz and 1495.9 MHz for UTRA FDD repeater operating in band XXXII. | +| UTRA FDD Band XII or E-UTRA Band 12 | 698 - 716 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band XII. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| UTRA FDD Band XIII or E-UTRA Band 13 | 777 - 787 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band XIII. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| UTRA FDD Band XIV or E-UTRA Band 14 | 788 - 798 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band XIV. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| E-UTRA Band 17 | 704 – 716 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band XII. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| UTRA FDD Band XX or E-UTRA Band 20 | 832 – 862 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band XX. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|---------|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA FDD Band XXII or E-UTRA Band 22 | 3410 - 3490 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band XXII. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| E-UTRA Band 23 | 2000 - 2020 MHz | -96 dBm | 100 kHz | | +| E-UTRA Band 24 | 1626.5 - 1660.5 MHz | -96 dBm | 100 kHz | | +| UTRA FDD Band XXV or E-UTRA Band 25 | 1850 - 1915 MHz | -96 dBm | 100 kHz | This requirement does not apply to UTRA FDD Repeater operating in band XXV. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. For UTRA FDD Repeater operating in band II, it applies from 1910MHz to 1915MHz, while the rest is covered in sub-clause 9.1.3, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| UTRA FDD Band XXVI or E-UTRA Band 26 | 814 – 849 MHz | -96 dBm | 100 kHz | This requirement does not apply to the UL of UTRA FDD Repeater operating in band XXVI. The sub-clause 9.1.3 requirement applies, but requires a 73dB coupling loss between BS and the repeater UL transmit port. For UTRA FDD Repeater operating in band V, it applies from 814 MHz to 824MHz, while the rest is covered in sub-clause 9.1.3, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| E-UTRA Band 27 | 807 – 824 MHz | -96 dBm | 100 kHz | For UTRA FDD Repeater operating in band XXVI, this requirement applies from 807 MHz to 814MHz, while the rest is covered in sub-clause 9.1.3, but requires a 73dB coupling loss between BS and the repeater UL transmit port. | +| E-UTRA Band 28 | 703 – 748 MHz | -96 dBm | 100 kHz | | +| E-UTRA Band 30 | 2305 – 2315 MHz | -96 dBm | 100 kHz | | +| E-UTRA Band 31 | 452.5 – 457.5 MHz | -96 dBm | 100 kHz | | +| NOTE 1: The co-location requirements do not apply for the 10 MHz frequency range immediately outside the repeater operating band (see Table 4.1). The current state-of-the-art technology does not allow a single generic solution for co-location with other system on adjacent frequencies for 30 dB UTRA Repeater-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [2]. | | | | | +| NOTE 2: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. | | | | | + +#### 9.2.2.6 Co-existence with PHS + +This requirement may be applied for the protection of PHS in geographic areas in which both PHS and UTRA-FDD Repeaters are deployed. This requirement is also applicable at specified frequencies falling between 12,5 MHz below the centre frequency of the first 5 MHz channel or more than 12,5 MHz above the centre frequency of the last 5 MHz channel in the pass band. + +##### 9.2.2.6.1 Minimum requirement + +The power of any spurious emission shall not exceed: + +**Table 9.17: UTRA Repeater Spurious up-link and down-link emissions limits for in geographic coverage area of PHS** + +| Band | Maximum Level | Measurement Bandwidth | Note | +|---------------------|---------------|-----------------------|------| +| 1884,5 – 1915,7 MHz | -41 dBm | 300 kHz | | + +#### 9.2.2.7 Co-existence with UTRA-TDD and/or E-UTRA TDD + +##### 9.2.2.7.1 Operation in the same geographic area + +This requirement may be applied to geographic areas in which both UTRA-TDD and/or E-UTRA TDD and UTRA-FDD Repeaters are deployed. + +###### 9.2.2.7.1.1 Minimum requirement + +In the down-link direction of the Repeater the power of any spurious emission shall not exceed: + +**Table 9.18: UTRA Repeater down-link spurious emissions limits in geographic coverage area of UTRA-TDD and/or E-UTRA TDD** + +| System type operating in the same geographical area | Band for co-existence requirement | Maximum Level | Measurement Bandwidth | Note | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|---------------|-----------------------|------------------------------------------------------------------------------| +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -52 dBm | 1 MHz | | +| UTRA TDD Band a) or E-UTRA Band 34 | 2010 - 2025 MHz | -52 dBm | 1 MHz | | +| UTRA TDD Band d) or E-UTRA Band 38 | 2570 - 2620 MHz | -52 dBm | 1 MHz | | +| UTRA TDD Band f) or E-UTRA Band 39 | 1880 – 1920 MHz | -52 dBm | 1 MHz | Applicable in China | +| UTRA TDD in Band e) or E-UTRA Band 40 | 2300 – 2400 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 41 | 2496 – 2690 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 42 | 3400 – 3600 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXII. | +| E-UTRA Band 43 | 3600 – 3800 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 44 | 703 – 803 MHz | -52 dBm | 1 MHz | | +| NOTE 1: The co-existence requirements do not apply for the 10 MHz frequency range immediately outside the repeaters operating band (see Table 4.1). Emission limits for this excluded frequency range may be covered by local or regional requirements. | | | | | +| NOTE 2: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. | | | | | + +In the up-link direction of the Repeater the power of any spurious emission shall not exceed: + +**Table 9.18A: UTRA Repeater up-link spurious emissions limits in geographic coverage area of UTRA-TDD and/or E-UTRA TDD** + +| System type operating in the same geographical area | Band for co-existence requirement | Maximum Level | Measurement Bandwidth | Note | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|---------------|-----------------------|--------------------------------------------------------------------------------------------------------------| +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -53 dBm | 100 kHz | This requirement is applied only to UTRA FDD Repeater operating in band I, band II or band XXV. | +| | 1900 - 1920 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band I band II or band XXV. | +| UTRA TDD Band a) or E-UTRA Band 34 | 2010 - 2025 MHz | -52 dBm | 1 MHz | | +| UTRA TDD Band d) or E-UTRA Band 38 | 2570 - 2620 MHz | -53 dBm | 100 kHz | This requirement is applied only to UTRA FDD Repeater operating in band VII. | +| | 2570 - 2620 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VII. | +| UTRA TDD Band f) or E-UTRA Band 39 | 1880 – 1920 MHz | -53 dBm | 100 kHz | Applicable in China. This requirement is applied only to UTRA FDD Repeater operating in band II or band XXV. | +| | 1880 – 1920 MHz | -52 dBm | 1 MHz | Applicable in China. This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV. | +| UTRA TDD in Band e) or E-UTRA Band 40 | 2300 – 2400 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 41 | 2496 - 2690 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 42 | 3400 – 3600 MHz | -52 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXII. | +| E-UTRA Band 43 | 3600 – 3800 MHz | -52 dBm | 1 MHz | | +| E-UTRA Band 44 | 703 – 803 MHz | -52 dBm | 1 MHz | | +| NOTE 3: The co-existence requirements do not apply for the 10 MHz frequency range immediately outside the repeaters operating band (see Table 4.1). Emission limits for this excluded frequency range may be covered by local or regional requirements. | | | | | +| NOTE 4: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. | | | | | + +NOTE 1: The requirements of -53dBm/100kHz in Table 9.18 and in Table 9.18A, which are respectively for the down link and up link direction of the Repeater reflect what can be achieved with present state of the art technology and are based on a coupling loss of 73 dB between a Repeater and a UTRA TDD BS receiver. + +NOTE 2: The requirements shall be reconsidered when the state of the art technology progresses. + +##### 9.2.2.7.2 Co-located Repeaters and UTRA-TDD and/or E-UTRA TDD base stations + +This requirement may be applied for the protection of UTRA-TDD BS receivers when UTRA-TDD and/or E-UTRA TDD BS and UTRA-FDD Repeater are co-located. + +###### 9.2.2.7.2.1 Minimum requirement + +In the down-link direction of the Repeater the power of any spurious emission shall not exceed: + +**Table 9.19: UTRA Repeater down-link spurious emissions limits for protection of co-located UTRA TDD and/or E-UTRA TDD BS receiver** + +| Type of co-located Base Station | Band for co-location requirement | Maximum Level | Measurement Bandwidth | Note | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|---------------|-----------------------|-------------------------------------------------------------------------------| +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | - 86 dBm | 1 MHz | | +| UTRA TDD Band a) or E-UTRA Band 34 | 2010 - 2025 MHz | - 86 dBm | 1 MHz | | +| UTRA TDD Band d) or E-UTRA Band 38 | 2570 - 2620 MHz | - 86 dBm | 1 MHz | | +| UTRA TDD Band f) or E-UTRA Band 39 | 1880 - 1920MHz | -86 dBm | 1 MHz | Applicable in China | +| UTRA TDD Band e) or E-UTRA Band 40 | 2300 - 2400MHz | -86 dBm | 1 MHz | | +| E-UTRA Band 41 | 2496 - 2690 MHz | -86 dBm | 1 MHz | This requirement does not apply to E-UTRA FDD Repeater operating in band VII. | +| E-UTRA Band 42 | 3400 - 3600 MHz | -86 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXII. | +| E-UTRA Band 43 | 3600 - 3800 MHz | -86 dBm | 1 MHz | | +| E-UTRA Band 44 | 703 – 803 MHz | -86 dBm | 1 MHz | | +| NOTE 1: The co-location requirements do not apply for the 10 MHz frequency range immediately outside the repeaters operating band (see Table 4.1). Emission limits for this excluded frequency range may be covered by local or regional requirements. | | | | | +| NOTE 2: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. | | | | | + +In the up-link direction of the Repeater the power of any spurious emission shall not exceed: + +**Table 9.19A: UTRA Repeater up-link spurious emissions limits for protection of co-located UTRA TDD and/or E-UTRA TDD BS receiver** + +| Type of co-located Base Station | Band for co-location requirement | Maximum Level | Measurement Bandwidth | Note | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|---------------|-----------------------|--------------------------------------------------------------------------------------------------------------| +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | -53 dBm | 100 kHz | This requirement is applied only to UTRA FDD Repeater operating in band I, band II or band XXV. | +| | 1900 - 1920 MHz | -86 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band I, band II or band XXV. | +| UTRA TDD Band a) or E-UTRA Band 34 | 2010 - 2025 MHz | -83 dBm | 100 kHz | This requirement is applied only to UTRA FDD Repeater operating in band I. | +| | 2010 - 2025 MHz | -86 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band I | +| UTRA TDD Band d) or E-UTRA Band 38 | 2570 - 2620 MHz | -53 dBm | 100 kHz | This requirement is applied only to UTRA FDD Repeater operating in band VII. | +| | 2570 - 2620 MHz | -86 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VII. | +| UTRA TDD Band f) or E-UTRA Band 39 | 1880 – 1920 MHz | -53 dBm | 100 kHz | Applicable in China. This requirement is applied only to UTRA FDD Repeater operating in band II or band XXV. | +| | 1880 – 1920 MHz | -86 dBm | 1 MHz | Applicable in China. This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV. | +| UTRA TDD in Band e) or E-UTRA Band 40 | 2300 – 2400 MHz | -86 dBm | 1 MHz | | +| E-UTRA Band 41 | 2496 - 2690 MHz | -86 dBm | 1 MHz | This requirement does not apply to E-UTRA FDD Repeater operating in band VII. | +| E-UTRA Band 42 | 3400 – 3600 MHz | -86 dBm | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXII. | +| E-UTRA Band 43 | 3600 – 3800 MHz | -86 dBm | 1 MHz | | +| E-UTRA Band 44 | 703 – 803 MHz | -86 dBm | 1 MHz | | +| NOTE 4: The co-location requirements do not apply for the 10 MHz frequency range immediately outside the repeaters operating band (see Table 4.1). Emission limits for this excluded frequency range may be covered by local or regional requirements. | | | | | +| NOTE 5: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-location requirements may apply that are not covered by the 3GPP specifications. | | | | | + +NOTE 1: The requirements of -53dBm/100kHz in Table 9.19 and Table 9.19A, which are respectively for the down link and up link direction of the Repeater reflect what can be achieved with present state of the art technology and are based on a coupling loss of 73 dB between a Repeater and a UTRA TDD BS receiver. + +NOTE 2: The requirements of -83dBm/100kHz in Table 9.19A for the up link direction of the Repeater reflect what can be achieved with present state of the art technology and are based on a coupling loss of 43 dB between a Repeater and a UTRA TDD BS receiver. + +NOTE 3: The requirements shall be reconsidered when the state of the art technology progresses. + +#### 9.2.2.8 (Void) + +#### 9.2.2.9 Protection of public safety operations + +This requirement shall be applied to Repeater operating in Bands XIII and XIV to ensure that appropriate interference protection is provided to 700 MHz public safety operations. This requirement is also applicable at specified frequencies falling between 12.5 MHz below the first carrier frequency used and 12.5 MHz above the last carrier frequency used. + +##### 9.2.2.9.1 Minimum Requirement + +The power of any spurious emission shall not exceed: + +**Table 9.21: Spurious emissions limits for the up-link and down-link of UTRA Repeater for protection of 700 MHz public safety operations** + +| Operating Band | Band | Maximum Level | Measurement Bandwidth | Note | +|----------------|---------------|---------------|-----------------------|------| +| XIII | 763 - 775 MHz | -46 dBm | 6.25 kHz | | +| XIII | 793 - 805 MHz | -46 dBm | 6.25 kHz | | +| XIV | 769 - 775 MHz | -46 dBm | 6.25 kHz | | +| XIV | 799 - 805 MHz | -46 dBm | 6.25 kHz | | + +This requirement shall be applied to repeaters operating in Band XXVI to ensure that appropriate interference protection is provided to 800 MHz public safety operations. This requirement is also applicable at specified frequencies falling between 12.5 MHz below the first carrier frequency used and 12.5 MHz above the last carrier frequency used. + +The power of any spurious emission shall not exceed: + +**Table 6.16A: Spurious emissions limits for the up-link and down-link of UTRA Repeater for protection of 800 MHz public safety operations** + +| Operating Band | Band | Maximum Level | Measurement Bandwidth | Note | +|----------------|---------------|---------------|-----------------------|--------------------------------------------------------| +| XXVI | 851 - 859 MHz | -13 dBm | 100 kHz | Applicable for offsets > 37.5kHz from the channel edge | + +### 9.2.3 Test purpose + +This test measure conducted spurious emission from the Repeater transmitter antenna connector, while the Repeater is in operation. + +### 9.2.4 Method of test + +#### 9.2.4.1 Initial conditions + +A measurement set-up is shown in annex A. + +- 1) Connect a signal generator to the input port of the Repeater for tests of repeaters with a pass band corresponding to one 5 MHz channel. If the pass band corresponds to two or more 5 MHz carriers, two signal generators with a combining circuit or one signal generator with the ability to generate several WCDMA carriers is connected to the input. The signals shall be de-correlated as described in TS25.141 [11], clause 6.1.1.6.3 of equal power. + +- 2) Detection mode: True RMS. + +#### 9.2.4.2 Procedures + +- 1) Set the Repeater to maximum gain. +- 2) Set the signal generator(s) to generate signal(s) in accordance to test model 1, TS 25.141 subclause 6.2.1.1.1, at level(s) which produce the manufacturer specified maximum output power at maximum gain. +- 3) The detecting device shall be configured with a measurement bandwidth as stated in the tables. +- 4) Measure the emission at the specified frequencies with specified measurement bandwidth and note that the measured value does not exceed the specified value. +- 5) Increase the input power with 10 dB compare to the level obtained in step 2. +- 6) Measure the emission at the specified frequencies with specified measurement bandwidth and note that the measured value does not exceed the specified value. +- 7) If the pass band corresponds to more than two consecutive nominal 5 MHz channels, repeat step 2) to 6) with any combination of two WCDMA modulated signals of equal power in the repeaters pass band. +- 8) Switch off the signal generator. +- 9) Measure the emission at the specified frequencies with specified measurement bandwidth and note that the measured value does not exceed the specified value. + +### 9.2.5 Test requirements + +In all measurements, the requirements according to subclause 9.2.2 shall be fulfilled. + +# --- 10 Modulation accuracy + +In this section the procedure for testing the modulation accuracy of Repeaters is defined. This test includes EVM and peak code domain error. + +## 10.1 Error vector magnitude + +In this section the procedure for testing the Error Vector Magnitude (EVM) of Repeaters is defined. + +### 10.1.1 Definition and applicability + +The Error Vector Magnitude is a measure of the difference between the theoretical waveform and a modified version of the measured waveform. The modification is done according to annex E of TS25.141. This difference is called the error vector. The EVM result is defined as the square root of the ratio of the mean error vector power to the modified mean reference signal power expressed as a %. The measurement interval is one power control group (timeslot). + +### 10.1.2 Minimum Requirements + +In normal conditions as specified in section 5.4.1 the Error Vector Magnitude shall not be worse than 12,5 % as defined in TS25.106. + +### 10.1.3 Test purpose + +To verify that the EVM is within the limit specified in 10.1.2 after the signal passed through the Repeater.. + +### 10.1.4 Method of test + +#### 10.1.4.1 Initial conditions + +Set-up the equipment as shown in annex A. + +The test is based upon the test for the base station. Test model 1 as described in TS25.141 is used for the definition of the signal to test on. A signal generator providing the required signals is connected to the input of the Repeater. The Repeater is set to operate at full gain. The signal level is adjusted to the equivalent level to obtain the nominal output power as declared by the manufacturer. A signal analyser connected to the output is used to measure the EVM value. + +#### 10.1.4.2 Procedure + +The test has to be performed in the uplink and the downlink path of the Repeater. The EVM has to be measured according to Annex E of TS25.141 + +#### 10.1.4.3 Stimulus EVM effect + +The stimulus signal generator EVM will RSS with the tested repeater EVM. The target for the recorded value is adjusted accordingly in the test requirements. + +### 10.1.5 Test requirements + +In normal conditions as specified in section 5.4.1, the Error Vector Magnitude, as defined in TS25.106, shall not exceed 13,2%. + +## 10.2 Peak code domain error + +In this section the procedure for testing the Peak Code Domain Error of Repeaters is defined. + +### 10.2.1 Definition and applicability + +The Peak Code Domain Error is computed by projecting the error vector onto the code domain at a specific spreading factor. The Code Domain Error for every code in the domain is defined as the ratio of the mean power of the projection onto that code, to the mean power of the composite reference waveform. This ratio is expressed in dB. The Peak Code Domain Error is defined as the maximum value for the Code Domain Error for all codes. The measurement interval is one power control group (timeslot). + +### 10.2.2 Minimum Requirements + +In normal conditions as specified in section 5.4.1 the peak code domain error shall not exceed -35 dB at spreading factor 256 as defined in TS25.106. + +### 10.2.3 Test purpose + +To verify that the peak code domain error is within the limit specified in 10.2.2 after the signal passed through the Repeater. + +### 10.2.4 Method of test + +#### 10.2.4.1 Initial conditions + +Set-up the equipment as shown in annex A. + +The test is based upon the test for the base station. Test model 3 as described in TS25.141 is used for the definition of the signal to test on. A signal generator providing the required signals is connected to the input of the Repeater. The spreading factor of the signal generator is set to 256. The Repeater is set to operate at full gain. The signal level is adjusted to the equivalent level to obtain the nominal output power as declared by the manufacturer. A signal analyser connected to the output is used to measure the peak code domain error value. + +#### 10.2.4.2 Procedure + +The test has to be performed in the uplink and the downlink path of the Repeater. The peak code domain error as described in TS25.141 Annex E has to be measured. + +### 10.2.5 Test requirements + +In normal conditions as specified in section 5.4.1 the peak code domain error shall not exceed -33,9 dB at spreading factor 256 as defined in TS25.106. + +## 10.3 Relative Code Domain Error (RCDE) for 64QAM modulation + +### 10.3.1 Definition and applicability + +The Relative Code Domain Error is computed by projecting the error vector (as defined in 10.1) onto the code domain at a specified spreading factor. Only the active code channels in the composite reference waveform are considered for this requirement. The Relative Code Domain Error for every active code is defined as the ratio of the mean power of the error projection onto that code, to the mean power of the active code in the composite reference waveform. This ratio is expressed in dB. The measurement interval is one frame. + +The requirement for Relative Code Domain Error is only applicable for Repeater supporting 64QAM modulated codes. + +See TS25.141 [11] Annex E for further details. + +### 10.3.2 Minimum requirement + +The average Relative Code Domain Error for 64QAM modulated codes shall not exceed -21 dB at spreading factor 16. + +### 10.3.3 Test purpose + +To verify that the peak code domain error is within the limit specified in 10.3.2 after the signal passed through the Repeater. + +### 10.3.4 Method of test + +#### 10.3.4.1 Initial conditions + +Set-up the equipment as shown in annex A. + +The test is based upon the test for the base station. Test model 6 as described in TS25.141 is used for the definition of the signal to test on. A signal generator providing the required signals is connected to the input of the Repeater. The spreading factor of the signal generator is set to 16. The Repeater is set to operate at full gain. The signal level is adjusted to the equivalent level to obtain the nominal output power as declared by the manufacturer. A signal analyser connected to the output is used to measure the peak code domain error value. + +#### 10.3.4.2 Procedure + +The test has to be performed in the uplink and the downlink path of the Repeater. The relative code domain error as described in TS25.141 Annex E has to be measured. + +### 10.3.5 Test requirements + +In normal conditions as specified in section 5.4.1 the relative code domain error shall not exceed -19.3 dB at spreading factor 16 as defined in TS25.106. + +# --- 11 Input intermodulation + +The input intermodulation is a measure of the capability of the Repeater to inhibit the generation of interference in the pass band, in the presence of interfering signals on frequencies other than the pass band. + +## 11.1 Definition and applicability + +Third and higher order mixing of the two interfering RF signals can produce an interfering signal in the band of the desired channel. Intermodulation response rejection is a measure of the capability of the Repeater to maintain the wanted frequency free of internally created interference. + +The test requirements in Tables 11.2 may be applied for the protection of FDD Repeater input when GSM900, DCS1800, PCS1900, GSM850, E-UTRA FDD and/or UTRA FDD BS are co-located with a UTRA FDD Repeater. + +The additional test requirements in Tables 11.2AA may be applied for the protection of FDD Repeater input when a UTRA TDD BS is co-located with a UTRA FDD Repeater. + +This test applies to uplink and downlink path of the Repeater. + +## 11.2 Minimum Requirements + +### 11.2.1 General requirement + +In normal conditions as specified in section 5.4.1 the intermodulation performance should be met when the following signals are applied to the Repeater: + +**Table 11.1: General input intermodulation requirement** + +| f_offset | Interfering Signal Levels | Type of signals | Measurement bandwidth | +|-----------------|----------------------------------|------------------------|------------------------------| +| 3,5 MHz | -40 dBm | 2 CW carriers | 1 MHz | + +For the parameters specified in table 11.1, the power in the pass band shall not increase by more than 10 dB at the output of the Repeater as measured in the centre of the pass band, compared to the level obtained without interfering signals applied. + +### 11.2.2 Co-location with BS in other systems + +In normal conditions as specified in section 5.4.1 the intermodulation performance should be met when the following signals are applied to the Repeater: + +**Table 11.2: Input intermodulation requirements for interfering signals in other systems** + +| Co-located other systems | Frequency of interfering signals | Interfering Signal Levels | Type of signals | Measurement bandwidth | Note | +|----------------------------------------------------|----------------------------------|---------------------------|-----------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GSM900 | 921 – 960 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VIII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| DCS1800 | 1805 – 1880 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| PCS1900 | 1930 – 1990 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| GSM850 or CDMA850 | 869 – 894 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band V or XXVI, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band I or E-UTRA Band 1 | 2110 – 2170 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band I, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band II or E-UTRA Band 2 | 1930 – 1990 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band III or E-UTRA Band 3 | 1805 – 1880 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III or band IX, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band IV or E-UTRA Band 4 | 2110 – 2155 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band IV or band X, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band V or E-UTRA Band 5 | 869 – 894 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band V or band XXVI, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band VI or XIX or E-UTRA Band 6, 18 or 19 | 860 – 890 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VI, XIX, or XXVI since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band VII or E-UTRA Band 7 | 2620 – 2690 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band VIII or E-UTRA Band 8 | 925 – 960 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VIII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | + +| | | | | | | +|-------------------------------------------------|---------------------|---------|---------------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA-FDD Band IX or E-UTRA Band 9 | 1844.9 – 1879.9 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III or band IX, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band X or E-UTRA Band 10 | 2110 – 2170 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band IV or band X, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band XI or XXI or E-UTRA Band 11 or 21 | 1475.9 – 1510.9 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XI or band XXI, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. This requirement does not apply to UTRA FDD Repeater operating in band XXXII, between 1475.9 MHz and 1496 MHz, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between base station and the repeater DL receive port. | +| UTRA-FDD Band XII or E-UTRA Band 12 | 728 - 746 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band XIII or E-UTRA Band 13 | 746 - 756 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XIII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band XIV or E-UTRA Band 14 | 758 - 768 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XIV, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| E-UTRA Band 17 | 734 - 746 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band XX or E-UTRA Band 20 | 791 - 821 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XX, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band XXII or E-UTRA Band 22 | 3510 - 3590 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| E-UTRA Band 23 | 2180 - 2200 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 24 | 1525 – 1559 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band XXV or E-UTRA Band 25 | 1930 - 1995 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXV, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. For UTRA FDD Repeater operating in band II, it applies from 1990MHz to 1995MHz, while the rest is covered in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | + +| | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------|---------------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA-FDD Band XXVI or E-UTRA Band 26 | 859 - 894 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXVI, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. For UTRA FDD Repeater operating in band V, it applies from 859 MHz to 869 MHz, while the rest is covered in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| E-UTRA Band 27 | 852 - 869 MHz | +16 dBm | 2 CW carriers | 1 MHz | For UTRA FDD Repeater operating in band XXVI, it applies from 852 MHz to 859 MHz, while the rest is covered in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| E-UTRA Band 28 | 758 - 803 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 29 | 717 - 728 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 30 | 2350 - 2360 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 31 | 462.5 – 467.5 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band XXXII or E-UTRA Band 32 | 1452 - 1496 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XI, XXI or XXXII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| NOTE 1: The co-location requirements in the table 11.2 do not apply when the repeaters pass band frequency range is adjacent to the frequency range of the co-location requirement in the table 11.2. The current state-of-the-art technology does not allow a single generic solution for co-location with other system on adjacent frequencies for 30 dB Repeater-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [2] | | | | | | +| NOTE 2: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. | | | | | | + +**Table 11.2AA: Input intermodulation requirements for interfering signals in UTRA and E-UTRA TDD systems** + +| Co-located other systems | Frequency of interfering signals | Interfering Signal Levels | Type of signals | Measurement bandwidth | +|------------------------------------|----------------------------------|---------------------------|-----------------|-----------------------| +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | +16 dBm | 2 CW carriers | 1 MHz | +| UTRA TDD Band a) or E-UTRA Band 34 | 2010 – 2025 MHz | +16 dBm | 2 CW carriers | 1 MHz | +| UTRA-TDD Band d) or E-UTRA Band 38 | 2570 – 2620 MHz | +16 dBm | 2 CW carriers | 1 MHz | +| UTRA TDD Band f) or E-UTRA Band 39 | 1880 - 1920MHz | +16 dBm | 2 CW carriers | 1 MHz | +| UTRA TDD Band e) or E-UTRA Band 40 | 2300 - 2400MHz | +16 dBm | 2 CW carriers | 1 MHz | +| E-UTRA Band 41 | 2496 - 2690 MHz | +16 dBm | 2 CW carriers | 1 MHz | +| E-UTRA Band 42 | 3400 - 3600 MHz | +16 dBm | 2 CW carriers | 1 MHz | +| E-UTRA Band 43 | 3600 - 3800 MHz | +16 dBm | 2 CW carriers | 1 MHz | +| E-UTRA Band 44 | 703 - 803 MHz | +16 dBm | 2 CW carriers | 1 MHz | + +NOTE 1: The co-location requirements in Table 11.2AA do not apply when the repeaters pass band frequency range is adjacent to the frequency range of the co-location requirement in the Table 11.2AA. The current state-of-the-art technology does not allow a single generic solution for co-location with other system on adjacent frequencies for 30 dB Repeater-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [2] + +NOTE 2: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. + +For the parameters specified in table 11.2 and 11.2AA, the power in the pass band shall not increase with more than 10 dB at the output of the repeater as measured in the centre of the pass band, compared to the level obtained without interfering signals applied. + +### 11.2.3 Co-existence with other systems + +In normal conditions as specified in section 5.4.1 the intermodulation performance should be met when the following signals are applied to the Repeater: + +#### **Table 11.2A: Input intermodulation requirements for interfering signals in other systems** + +| Co-existence with other systems | Frequency of interfering signals | Interfering Signal Levels | Type of signals | Measurement bandwidth | Note | +|----------------------------------------------------|----------------------------------|---------------------------|-----------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GSM900 | 876 – 915 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VIII, since it is already covered by the requirement in sub-clause 11.2.1. | +| DCS1800 | 1710 – 1785 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III, since it is already covered by the requirement in sub-clause 11.2.1. | +| PCS1900 | 1850 – 1910 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV, since it is already covered by the requirement in sub-clause 11.2.1. | +| GSM850 or CDMA850 | 824 – 849 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band V or band XXVI, since it is already covered by the requirement in sub-clause 11.2.1. | +| UTRA-FDD Band I or E-UTRA Band 1 | 1920 – 1980 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band I, since it is already covered by the requirement in sub-clause 11.2.1. | +| UTRA-FDD Band II or E-UTRA Band 2 | 1850 – 1910 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV, since it is already covered by the requirement in sub-clause 11.2.1. | +| UTRA-FDD Band III or E-UTRA Band 3 | 1710 – 1785 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III or band IX, since it is already covered by the requirement in sub-clause 11.2.1. | +| UTRA-FDD Band IV or E-UTRA Band 4 | 1710 – 1755 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band IV or band X, since it is already covered by the requirement in sub-clause 11.2.1. | +| UTRA-FDD Band V or E-UTRA Band 5 | 824 – 849 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band V or band XXVI, since it is already covered by the requirement in sub-clause 11.2.1. | +| UTRA-FDD Band VI or XIX or E-UTRA Band 6, 18 or 19 | 815 – 845 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VI or band XIX, since it is already covered by the requirement in sub-clause 11.2.1. This requirement does not apply to the UL of UTRA FDD Repeater operating in band V or XX. | +| UTRA-FDD Band VII or E-UTRA Band 7 | 2500 – 2570 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VII, since it is already covered by the requirement in sub-clause 11.2.1. | +| UTRA-FDD Band VIII or E-UTRA Band 8 | 880 – 915 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VIII, since it is already covered by the requirement in sub-clause 11.2.1. | +| UTRA-FDD Band IX or E-UTRA Band 9 | 1749,9 – 1784,9 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III or band IX, since it is already covered by the requirement in sub-clause 11.2.1. | +| UTRA-FDD Band X or E-UTRA Band 10 | 1710 – 1770 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band IV or band X, since it is already covered by the requirement in sub-clause 11.2.1. | +| | 1427,9 – 1447,9 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XI, since it is already covered by the requirement in sub-clause 11.2.1. | + +| | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|---------|---------------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA-FDD Band XI or XXI or E-UTRA Band 11 or 21 | 1447.9 - 1462.9 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXI, since it is already covered by the requirement in sub-clause 11.2.1. For UTRA FDD Repeater operating in band XXXII, it applies from 1447.9 MHz to 1452 MHz, while the rest is covered in sub-clause 11.2.1. | +| UTRA-FDD Band XII or E-UTRA Band 12 | 698 - 716 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XII, since it is already covered by the requirement in sub-clause 11.2.1. | +| UTRA-FDD Band XIII or E-UTRA Band 13 | 777 - 787 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XIII, since it is already covered by the requirement in sub-clause 11.2.1. | +| UTRA-FDD Band XIV or E-UTRA Band 14 | 788 - 798 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XIV, since it is already covered by the requirement in sub-clause 11.2.1. | +| E-UTRA Band 17 | 704 - 716 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XII, since it is already covered by the requirement in sub-clause 11.2.1. | +| UTRA-FDD Band XX or E-UTRA Band 20 | 832 - 862 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XX, since it is already covered by the requirement in sub-clause 11.2.1. | +| UTRA-FDD Band XXII or E-UTRA Band 22 | 3410-3490 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXII, since it is already covered by the requirement in sub-clause 11.2.1. | +| E-UTRA Band 23 | 2000 - 2020 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 24 | 1626.5 – 1660.5 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band XXV or E-UTRA Band 25 | 1850-1915 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXV, since it is already covered by the requirement in sub-clause 11.2.1. For UTRA FDD Repeater operating in band II, it applies from 1910MHz to 1915MHz, while the rest is covered in sub-clause 11.2.1. | +| UTRA-FDD Band XXVI or E-UTRA Band 26 | 814 - 849 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXVI, since it is already covered by the requirement in sub-clause 11.2.1. For UTRA FDD Repeater operating in band V, it applies from 814MHz to 824 MHz, while the rest is covered in sub-clause 11.2.1. | +| E-UTRA Band 27 | 807 - 824 MHz | -15 dBm | 2 CW carriers | 1 MHz | For UTRA FDD Repeater operating in band XXVI, this requirement applies from 807MHz to 814 MHz, while the rest is covered in sub-clause 11.2.1. | +| E-UTRA Band 28 | 703 - 748 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 30 | 2305 - 2315 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 31 | 452.5 – 457.5 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| NOTE 1: The co-existence requirements in Table 11.2A do not apply when the repeaters pass band frequency range is adjacent to the frequency range of the co-existence requirement in the Table 11.2A. The current state-of-the-art technology does not allow a single generic solution for co-existence | | | | | | +| NOTE 2: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. | | | | | | + +**Table 11.2AAA: Input intermodulation requirements for interfering signals in UTRA and E-UTRA TDD systems** + +| Co-existence with other systems | Frequency of interfering signals | Interfering Signal Levels | Type of signals | Measurement bandwidth | Note | +|--------------------------------------------|----------------------------------|---------------------------|-----------------|-----------------------|----------------------------------------------------------------------------------------------------------------| +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 – 1920 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band I, band II or band XXV. | +| UTRA TDD Band a) or E-UTRA Band 34 | 2010 – 2025 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA-TDD Band d) and or E-UTRA TDD Band 38 | 2570 - 2620 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VII. | +| UTRA TDD Band f) or E-UTRA Band 39 | 1880 - 1920MHz | -15 dBm | 2 CW carriers | 1 MHz | Applicable in China.
This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV. | +| UTRA TDD Band e) or E-UTRA Band 40 | 2300 - 2400MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 41 | 2496 - 2690 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 42 | 3400 - 3600 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXII. | +| E-UTRA Band 43 | 3600 - 3800 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 44 | 703 - 803 MHz | -15 dBm | 2 CW carriers | 1 MHz | | + +NOTE 1: The co-existence requirements in Table 11.2AAA do not apply when the repeaters pass band frequency range is adjacent to the frequency range of the co-location requirement in the Table 11.2AAA. The current state-of-the-art technology does not allow a single generic solution for co-location with other system on adjacent frequencies for 30 dB Repeater-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [5] + +NOTE 2: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. + +For the parameters specified in table 11.2A and table 11.2AAA, the power in the pass band shall not increase with more than 10 dB at the output of the repeater as measured in the centre of the pass band, compared to the level obtained without interfering signals applied. + +## 11.3 Test purpose + +The purpose of this test is to verify that the Repeater meets the intermodulation characteristics requirements as specified in TS 25.106, subclause 11.1. + +## 11.4 Method of test + +### 11.4.1 Initial conditions + +- 1) Set-up the equipment as shown in annex A. +- 2) Set the Repeater to maximum gain. +- 3) Connect two signal generators with a combining circuit or one signal generator with the ability to generate several CW carriers to the input. + +- 4) Connect a spectrum analyser to the output of the Repeater. Set the resolution bandwidth to 1 MHz in the centre of the pass band. Set averaging to 1 second or more. + +### 11.4.2 Procedure + +- 1) Adjust the frequency of the input signals, either below or above the pass band, so that the lowest order intermodulation product is positioned in the centre of the pass band, according to subclause 11.2. +- 2) Take the measurement of the rise of the output signal. +- 3) Repeat the measurement for the opposite path of the Repeater. + +## 11.5 Test requirements + +### 11.5.1 Mandatory requirement + +In normal conditions as specified in section 5.4.1 the intermodulation performance should be met when the following signals are applied to the Repeater: + +**Table 11.3: Input intermodulation requirement** + +| f_offset | Interfering Signal Levels | Type of signals | Measurement bandwidth | +|-----------------|----------------------------------|------------------------|------------------------------| +| 3,5 MHz | -40 dBm | 2 CW carriers | 1 MHz | + +For the parameters specified in table 11.3, the power in the pass band shall not increase by more than 11,2 dB at the output of the Repeater as measured in the centre of the pass band, compared to the level obtained without interfering signals applied. + +### 11.5.2 Co-location with BS in other systems + +In normal conditions as specified in section 5.4.1 the intermodulation performance should be met when the following signals are applied to the Repeater: + +**Table 11.4: Input intermodulation requirements for interfering signals in other systems** + +| Co-located other systems | Frequency of interfering signals | Interfering Signal Levels | Type of signals | Measurement bandwidth | Note | +|----------------------------------------------------|----------------------------------|---------------------------|-----------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GSM900 | 921 – 960 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VIII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| DCS1800 | 1805 – 1880 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| PCS1900 | 1930 – 1990 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| GSM850 or CDMA850 | 869 – 894 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band V or XXVI, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band I or E-UTRA Band 1 | 2110 – 2170 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band I, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band II or E-UTRA Band 2 | 1930 – 1990 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band III or E-UTRA Band 3 | 1805 – 1880 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III or band IX, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band IV or E-UTRA Band 4 | 2110 – 2155 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band IV or band X, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band V or E-UTRA Band 5 | 869 – 894 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band V or XXVI, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band VI or XIX or E-UTRA Band 6, 18 or 19 | 860 – 890 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VI, XIX or XXVI since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band VII or E-UTRA Band 7 | 2620 – 2690 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band VIII or E-UTRA Band 8 | 925 – 960 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VIII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | + +| | | | | | | +|-------------------------------------------------|---------------------|---------|---------------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA-FDD Band IX or E-UTRA Band 9 | 1844.9 – 1879.9 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III or band IX, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band X or E-UTRA Band 10 | 2110 – 2170 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band IV or band X, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band XI or XXI or E-UTRA Band 11 or 21 | 1475.9 – 1510.9 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XI or band XXI, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port.
This requirement does not apply to UTRA FDD Repeater operating in band XXXII, between 1475.9 MHz and 1496 MHz, since it is already covered by the requirement in sub-clause 11.2.1, but requires 86dB coupling loss between base station and the repeater DL receive port. | +| UTRA-FDD Band XII or E-UTRA Band 12 | 728 - 746 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band XIII or E-UTRA Band 13 | 746 - 756 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XIII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band XIV or E-UTRA Band 14 | 758 - 768 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XIV, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| E-UTRA Band 17 | 734 - 746 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band XX or E-UTRA Band 20 | 791 - 821 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XX, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| UTRA-FDD Band XXII or E-UTRA Band 22 | 3510-3590 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| E-UTRA Band 23 | 2180 - 2200 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 24 | 1626.5 – 1660.5 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band XXV or E-UTRA Band 25 | 1930-1995 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXV, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port.
For UTRA FDD Repeater operating in band II, it applies from 1990MHz to 1995MHz, while the rest is covered in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | + +| | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------|---------------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA-FDD Band XXVI or E-UTRA Band 26 | 859 - 894 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXVI, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. For UTRA FDD Repeater operating in band V, it applies from 859 MHz to 869 MHz, while the rest is covered in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| E-UTRA Band 27 | 852 - 869 MHz | +16 dBm | 2 CW carriers | 1 MHz | For UTRA FDD Repeater operating in band XXVI, it applies from 852 MHz to 859 MHz, while the rest is covered in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| E-UTRA Band 28 | 758 - 803 MHz | +16 dBm | 2 CW carriers | 1 MHz | For UTRA FDD Repeater operating in band XXVI, it applies from 852 MHz to 859 MHz, while the rest is covered in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| E-UTRA Band 29 | 717 - 728 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 30 | 2350 - 2360 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 31 | 462.5 – 467.5 MHz | +16 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band XXXII or E-UTRA Band 32 | 1452 - 1496 MHz | +16 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XI, XXI or XXXII, since it is already covered by the requirement in sub-clause 11.2.1, but requires a 86dB coupling loss between BS and the repeater DL receive port. | +| NOTE 1: The co-location requirements in the table 11.4 do not apply when the repeaters pass band frequency range is adjacent to the frequency range of the co-location requirement in the table 11.4. The current state-of-the-art technology does not allow a single generic solution for co-location with other system on adjacent frequencies for 30 dB Repeater-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [2]. | | | | | | +| NOTE 2: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. | | | | | | + +**Table 11.4AA: Input intermodulation requirements for interfering signals in UTRA and E-UTRA TDD bands** + +| Co-located other systems | Frequency of interfering signals | Interfering Signal Levels | Type of signals | Measurement bandwidth | +|------------------------------------|----------------------------------|---------------------------|-----------------|-----------------------| +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 - 1920 MHz | +16 dBm | 2 CW carriers | 1 MHz | +| UTRA TDD Band a) or E-UTRA Band 34 | 2010 – 2025 MHz | +16 dBm | 2 CW carriers | 1 MHz | +| UTRA-TDD Band d) or E-UTRA Band 38 | 2570 – 2620 MHz | +16 dBm | 2 CW carriers | 1 MHz | +| UTRA TDD Band f) or E-UTRA Band 39 | 1880 - 1920MHz | +16 dBm | 2 CW carriers | 1 MHz | +| UTRA TDD Band e) or E-UTRA Band 40 | 2300 - 2400MHz | +16 dBm | 2 CW carriers | 1 MHz | +| E-UTRA Band 41 | 2496 - 2690 MHz | +16 dBm | 2 CW carriers | 1 MHz | +| E-UTRA Band 42 | 3400 - 3600 MHz | +16 dBm | 2 CW carriers | 1 MHz | +| E-UTRA Band 43 | 3600 - 3800 MHz | +16 dBm | 2 CW carriers | 1 MHz | +| E-UTRA Band 43 | 703 - 803 MHz | +16 dBm | 2 CW carriers | 1 MHz | + +NOTE 1: The co-location requirements in Table 11.4AA do not apply when the repeaters pass band frequency range is adjacent to the frequency range of the co-location requirement in the Table 11.4AA. The current state-of-the-art technology does not allow a single generic solution for co-location with other system on adjacent frequencies for 30 dB Repeater-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [2]. + +NOTE 2: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. + +For the parameters specified in table 11.4 and in table 11.4AA, the power in the pass band shall not increase with more than 11,2 dB at the output of the repeater as measured in the centre of the pass band, compared to the level obtained without interfering signals applied. + +### 11.5.3 Co-existence with other systems + +In normal conditions as specified in section 5.4.1 the intermodulation performance should be met when the following signals are applied to the Repeater: + +###### **Table 11.4A: Input intermodulation requirements for interfering signals in other systems** + +| Co-existence with other systems | Frequency of interfering signals | Interfering Signal Levels | Type of signals | Measurement bandwidth | Note | +|--------------------------------------------------|----------------------------------|---------------------------|-----------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GSM900 | 876 – 915 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VIII, since it is already covered by the requirement in sub-clause 11.2.1. | +| DCS1800 | 1710 – 1785 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III, since it is already covered by the requirement in sub-clause 11.2.1. | +| PCS1900 | 1850 – 1910 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV, since it is already covered by the requirement in sub-clause 11.2.1. | +| GSM850 or CDMA850 | 824 – 849 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band V or band XXVI, since it is already covered by the requirement in sub-clause 11.2.1. | +| UTRA-FDD Band I or E-UTRA Band 1 | 1920 – 1980 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band I, since it is already covered by the requirement in sub-clause 11.2.1. | +| UTRA-FDD Band II or E-UTRA Band 2 | 1850 – 1910 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV, since it is already covered by the requirement in sub-clause 11.2.1. | +| UTRA-FDD Band III or E-UTRA Band 3 | 1710 – 1785 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III or band IX, since it is already covered by the requirement in sub-clause 11.2.1. | +| UTRA-FDD Band IV or E-UTRA Band 4 | 1710 – 1755 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band IV or band X, since it is already covered by the requirement in sub-clause 11.2.1. | +| UTRA-FDD Band V or E-UTRA Band 5 | 824 – 849 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band V or band XXVI, since it is already covered by the requirement in sub-clause 11.2.1. | +| UTRA-FDD Band VI or XIX or E-UTRA Band 6, 18, 19 | 815 – 845 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VI or band XIX, since it is already covered by the requirement in sub-clause 11.2.1. This requirement does not apply to the UL of UTRA FDD Repeater operating in band V or XX. | +| UTRA-FDD Band VII or E-UTRA Band 7 | 2500 – 2570 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VII, since it is already covered by the requirement in sub-clause 11.2.1. | +| UTRA-FDD Band VIII or E-UTRA Band 8 | 880 – 915 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VIII, since it is already covered by the requirement in sub-clause 11.2.1. | +| UTRA-FDD Band IX or E-UTRA Band 9 | 1749,9 – 1784,9 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band III or band IX, since it is already covered by the requirement in sub-clause 11.2.1. | +| UTRA-FDD Band X or E-UTRA Band 10 | 1710 – 1770 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band IV or band X, since it is already covered by the requirement in sub-clause 11.2.1. | +| | 1427.9 – 1447.9 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XI, since it is already covered by the requirement in sub-clause 11.2.1. | + +| | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|---------|---------------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UTRA-FDD Band XI or XXI or E-UTRA Band 11 or 21 | 1447.9 - 1462.9 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXI, since it is already covered by the requirement in sub-clause 11.2.1. For UTRA FDD Repeater operating in band XXXII, it applies from 1447.5 MHz to 1452 MHz, while the rest is covered in sub-clause 11.2.1. | +| UTRA-FDD Band XII or E-UTRA Band 12 | 698 - 716 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XII, since it is already covered by the requirement in sub-clause 11.2.1. | +| UTRA-FDD Band XIII or E-UTRA Band 13 | 777 - 787 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XIII, since it is already covered by the requirement in sub-clause 11.2.1. | +| UTRA-FDD Band XIV or E-UTRA Band 14 | 788 - 798 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XIV, since it is already covered by the requirement in sub-clause 11.2.1. | +| E-UTRA Band 17 | 704 - 716 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XII, since it is already covered by the requirement in sub-clause 11.2.1. | +| UTRA-FDD Band XX or E-UTRA Band 20 | 832 - 862 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XX, since it is already covered by the requirement in sub-clause 11.2.1. | +| UTRA-FDD Band XXII or E-UTRA Band 22 | 3410 - 3490 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXII, since it is already covered by the requirement in sub-clause 11.2.1. | +| E-UTRA Band 23 | 2000 - 2020 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 24 | 1626.5 – 1660.5 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA-FDD Band XXV or E-UTRA Band 25 | 1850 - 1915 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXV, since it is already covered by the requirement in sub-clause 11.2.1. For UTRA FDD Repeater operating in band II, it applies from 1910MHz to 1915MHz, while the rest is covered in sub-clause 11.2.1. | +| UTRA-FDD Band XXVI or E-UTRA Band 26 | 814 - 849 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXVI, since it is already covered by the requirement in sub-clause 11.2.1. For UTRA FDD Repeater operating in band V, it applies from 814MHz to 824 MHz, while the rest is covered in sub-clause 11.2.1. | +| E-UTRA Band 27 | 807 - 824 MHz | -15 dBm | 2 CW carriers | 1 MHz | For UTRA FDD Repeater operating in band XXVI, this requirement applies from 807MHz to 814 MHz, while the rest is covered in sub-clause 11.2.1. | +| E-UTRA Band 28 | 703 - 748 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 30 | 2305 - 2315 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 31 | 452.5 – 457.5 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| NOTE 1: The co-existence requirements in Table 11.4A do not apply when the repeaters pass band frequency range is adjacent to the frequency range of the co-existence requirement in the Table 11.4A. The current state-of-the-art technology does not allow a single generic solution for co-existence. | | | | | | +| NOTE 2: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. | | | | | | + +**Table 11.4AAA: Input intermodulation requirements for interfering signals in UTRA and E-UTRA TDD systems** + +| Co-existence with other systems | Frequency of interfering signals | Interfering Signal Levels | Type of signals | Measurement bandwidth | Note | +|--------------------------------------------|----------------------------------|---------------------------|-----------------|-----------------------|----------------------------------------------------------------------------------------------------------------| +| UTRA TDD Band a) or E-UTRA Band 33 | 1900 – 1920 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band I, band II or band XXV. | +| UTRA TDD Band a) or E-UTRA Band 34 | 2010 – 2025 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| UTRA-TDD Band d) and or E-UTRA TDD Band 38 | 2570 - 2620 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band VII. | +| UTRA TDD Band f) or E-UTRA Band 39 | 1880 - 1920MHz | -15 dBm | 2 CW carriers | 1 MHz | Applicable in China.
This requirement does not apply to UTRA FDD Repeater operating in band II or band XXV. | +| UTRA TDD Band e) or E-UTRA Band 40 | 2300 - 2400MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 41 | 2496 - 2690 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 42 | 3400 - 3600 MHz | -15 dBm | 2 CW carriers | 1 MHz | This requirement does not apply to UTRA FDD Repeater operating in band XXII. | +| E-UTRA Band 43 | 3600 - 3800 MHz | -15 dBm | 2 CW carriers | 1 MHz | | +| E-UTRA Band 44 | 703 - 803 MHz | -15 dBm | 2 CW carriers | 1 MHz | | + +NOTE 1: The co-existence requirements in Table 11.4AAA do not apply when the repeaters pass band frequency range is adjacent to the frequency range of the co-location requirement in the Table 11.4AAA. The current state-of-the-art technology does not allow a single generic solution for co-location with other system on adjacent frequencies for 30 dB Repeater-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942 [5] + +NOTE 2: The table above assumes that two operating bands, where the frequency ranges would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications. + +For the parameters specified in table 11.4A and table 11.4AAA, the power in the pass band shall not increase with more than 11,2 dB at the output of the repeater as measured in the centre of the pass band, compared to the level obtained without interfering signals applied. + +# 12 Output intermodulation + +The output intermodulation requirement is a measure of the ability of the repeater to inhibit the generation of intermodulation products signals created by the presence of an interfering signal reaching the repeater via the output port. + +## 12.1 Definition and applicability + +The output intermodulation level is the power of the intermodulation products when a WCDMA modulated interference signal is injected into the output port at a level of 30 dB lower than that of the wanted signal. The frequency of the interference signal shall be $\pm 5$ MHz, $\pm 10$ MHz and $\pm 15$ MHz offset from the wanted signal, but within the frequency band allocated for UTRA FDD downlink as specified in subclause 4.1. + +The requirement is applicable for downlink signals. + +The normative reference for this requirement is in TS25.106 [12] section 12. + +## 12.2 Minimum requirement + +In normal conditions as specified in section 5.4.1, the output intermodulation level shall not exceed the out of band emission or the spurious emission requirements of section 9.1 and 9.2. + +## 12.3 Test purpose + +The test purpose is to verify the ability of the repeater to restrict the generation of intermodulation products in the presence of a subject signal on the repeater input and output ports, and an interfering signal applied at the repeater output port. + +## 12.4 Method of test + +### 12.4.1 Initial conditions + +- 1) Set-up the equipment as shown in annex A. +- 2) Connect a signal generator to the input port of the Repeater for tests of repeaters with a pass band corresponding to one 5 MHz channel. Connect a signal generator to the circulator on the output port and make sure the signal generator power is directed to the repeater output port. +- 3) Measurements with an offset from the carrier centre frequency between 2,515 MHz and 4,0 MHz shall use a 30 kHz measurement bandwidth. +- 4) Measurements with an offset from the carrier centre frequency between 4,0 MHz and ( $\Delta f_{max} - 500$ kHz) shall use a 1 MHz measurement bandwidth. The 1MHz measurement bandwidth may be calculated by integrating multiple 50 kHz or narrower filter measurements +- 5) Detection mode: True RMS. + +### 12.4.2 Procedures + +- 1) Set the Repeater to maximum gain. +- 2) Set the signal generator at the repeater input port (subject signal) to generate a signal in accordance to test model 1, TS 25.141 subclause 6.1.1.1, at the level which produce the manufacturer specified maximum output power at maximum gain. +- 3) Set the signal generator at the repeater output port (interference signal) to generate a signal in accordance to test model 1, TS 25.141 subclause 6.1.1.1, at the level producing signal power corresponding to 30 dB below the manufacturer specified maximum output power at the repeater output port with the specified frequency offset from the wanted signal. +- 4) Measure the emission at the specified frequencies with specified measurement bandwidth and note that the measured value does not exceed the specified value. Measurements in the band of the interfering signal shall be excluded. The measurements can be limited to the power of all third and fifth order intermodulation products. +- 5) Repeat from clause 3 until interference signals $\pm 5$ MHz, $\pm 10$ MHz and $\pm 15$ MHz frequency offset from the wanted signal has been tested. Note that interfering signals outside the UTRA-FDD allocated frequency band , as specifies in section 4.1. need not be tested. + +## 12.5 Test requirements + +In all measurements, the requirements according to sections 9.1.1.5 and the downlink requirements in section 9.2.2.1 or 9.2.2.2 shall be fulfilled. + +# 13 Adjacent Channel Rejection Ratio (ACRR) + +## 13.1 Definitions and applicability + +Adjacent Channel Rejection Ratio (ACRR) is the ratio of the RRC weighted gain per carrier of the repeater in the pass band to the RRC weighted gain of the repeater on an adjacent channel. + +The requirement shall apply to the uplink and downlink of Repeater where the donor link is maintained via antennas (over the air Repeater). + +## 13.2 Minimum Requirements + +In normal conditions the ACRR shall be higher than the value specified in the Table 13.1. + +**Table 13.1: Repeater ACRR** + +| Repeater maximum output power as in 9.1.1 | Channel offset from the centre frequency of the first or last 5 MHz channel within the pass band. | ACRR limit | +|-------------------------------------------|---------------------------------------------------------------------------------------------------|------------| +| $P \geq 31$ dBm | 5 MHz | 33dB | +| $P \geq 31$ dBm | 10 MHz | 33dB | +| $P < 31$ dBm | 5 MHz | 20dB | +| $P < 31$ dBm | 10 MHz | 20dB | + +## 13.3 Test purpose + +To verify that the Repeater ACRR requirement shall be met as specified in subclause 13.1. + +## 13.4 Method of test + +### 13.4.1 Initial conditions + +- 1) Set-up the equipment as shown in annex A. +- 2) Connect the signal generator equipment to the Repeater input port. +- 3) Connect the power measuring equipment to the Repeater output port. +- 4) The measurement device characteristics shall be: + - measurement filter bandwidth: defined in subclause 13.1; + - detection mode: true RMS voltage or true average power. + +### 13.4.2 Procedure + +- 1) Set the signal generator to transmit a signal modulated with a combination of PCCPCH, SCCPCH and Dedicated Physical Channels specified as test model 1 in TS 25.141 at the first or last 5 MHz channel within the pass band. +- 2) Adjust the input power to the Repeater to create the maximum nominal Repeater output power at maximum gain +- 3) Measure the RRC filtered mean power at the RF output port over a certain slot. +- 4) Set the signal generator to transmit the same signal and the same input power at one of the channel offsets according to Table 13.1. +- 5) Measure the RRC filtered mean power at the RF output port over a certain slot. +- 6) Calculate the ratio of the measured power in the pass band to the measured power at the channel offset. +- 7) Repeat step 4) to 6) until all channel offsets in Table 13.1 are measured. + +### 13.4.3 Test Requirements + +In normal conditions as specified in section 5.4.1, the ACRR shall be higher than the value specified in the Table 13.2. + +**Table 13.2: Repeater ACRR** + +| Repeater maximum output power as in 9.1.1.1 | Channel offset from the centre frequency of the first or last 5 MHz channel within the pass band. | ACRR limit | +|----------------------------------------------------|----------------------------------------------------------------------------------------------------------|-------------------| +| $P \geq 31$ dBm | 5 MHz | 32,3dB | +| $P \geq 31$ dBm | 10 MHz | 32,3dB | +| $P < 31$ dBm | 5 MHz | 19,3dB | +| $P < 31$ dBm | 10 MHz | 19,3dB | + +# Annex A (informative): Repeater measurement system set-up + +Example of measurement system set-ups are attached below as an informative annex. + +## A.1 Maximum output power + +![Block diagram for maximum output power measurement](cc893412ff9ca2426705e878c75548ba_img.jpg) + +``` +graph LR; A[WCDMA Signal Generator] --> B[Repeater under test]; B --> C[Power meter or equivalent]; +``` + +The diagram shows a linear measurement setup. On the right, a 'WCDMA Signal Generator' is connected to the right input of a 'Repeater under test' block. The left output of the 'Repeater under test' block is connected to a 'Power meter or equivalent' block on the left. Arrows indicate the signal flow from right to left. + +Block diagram for maximum output power measurement + +**Figure A.1: Measuring system set-up for maximum output power.** + +Note that a repeater is a bi-directional device. The signal generator may need protection. + +## A.2 Frequency stability + +![Block diagram for RF frequency stability measurement](b82b870697ef3993804c839b298c0f4f_img.jpg) + +``` +graph LR; A[CW Signal Generator] --> B[Repeater under test]; B --> C[Frequency counter]; +``` + +The diagram shows a linear measurement setup. On the right, a 'CW Signal Generator' is connected to the right input of a 'Repeater under test' block. The left output of the 'Repeater under test' block is connected to a 'Frequency counter' block on the left. Arrows indicate the signal flow from right to left. + +Block diagram for RF frequency stability measurement + +**Figure A.2: Measurement system set-up for RF frequency stability.** + +Note that a repeater is a bi-directional device. The signal generator may need protection. + +## A.3 Out of band gain + +![Block diagram for out of band gain measurement](bc6f0b99574deef4f696650b64a600c1_img.jpg) + +``` +graph LR; A[CW Signal Generator] --> B[-30 dB precision attenuator]; B --> C[Repeater under test]; C --> D[-30 dB precision attenuator]; D --> E[Spectrum analyser]; +``` + +The diagram shows a linear measurement setup. On the right, a 'CW Signal Generator' is connected to the right input of a '-30 dB precision attenuator' block. The output of this attenuator is connected to the right input of a 'Repeater under test' block. The left output of the 'Repeater under test' block is connected to another '-30 dB precision attenuator' block, which in turn is connected to a 'Spectrum analyser' block on the far left. Arrows indicate the signal flow from right to left. + +Block diagram for out of band gain measurement + +**Figure A.3: Measuring system set-up for out of band gain.** + +Note that a repeater is a bi-directional device. The signal generator may need protection. + +## A.4 Unwanted emission: Spectrum emission mask + +![Block diagram of the measuring system set-up for unwanted emission: spectrum emission mask. The diagram shows a WCDMA Signal Generator connected to a 5 MHz channel filter, which is connected to a Repeater under test, which is in turn connected to a Spectrum analyser.](719ef0f734259484038b2434e5dc3f24_img.jpg) + +``` +graph LR; WCDMA[WCDMA Signal Generator] --> Filter[5 MHz channel filter]; Filter --> Repeater[Repeater under test]; Repeater --> Analyser[Spectrum analyser]; +``` + +Block diagram of the measuring system set-up for unwanted emission: spectrum emission mask. The diagram shows a WCDMA Signal Generator connected to a 5 MHz channel filter, which is connected to a Repeater under test, which is in turn connected to a Spectrum analyser. + +**Figure A.4: Measuring system Set-up for unwanted emission: spectrum emission mask.** + +Note that a repeater is a bi-directional device. The signal generator may need protection. + +## A.5 Unwanted emission: Spurious emission + +![Block diagram of the measuring system set-up for unwanted emission: spurious emission. The diagram shows a WCDMA Signal Generator connected to a 5 MHz channel filter, which is connected to a Repeater under test, which is in turn connected to a Spectrum analyser.](ee0bf6a260cff72af8f0df0639b6a7c5_img.jpg) + +``` +graph LR; WCDMA[WCDMA Signal Generator] --> Filter[5 MHz channel filter]; Filter --> Repeater[Repeater under test]; Repeater --> Analyser[Spectrum analyser]; +``` + +Block diagram of the measuring system set-up for unwanted emission: spurious emission. The diagram shows a WCDMA Signal Generator connected to a 5 MHz channel filter, which is connected to a Repeater under test, which is in turn connected to a Spectrum analyser. + +**Figure A.5: Measuring system set-up for unwanted emission: spurious emission.** + +Note that a repeater is a bi-directional device. The signal generator may need protection. + +## A.6 Modulation Accuracy: Error Vector Magnitude + +![Block diagram of the measuring system set-up for modulation accuracy: error vector magnitude. The diagram shows a WCDMA Signal Generator connected to a Repeater under test, which is in turn connected to a Signal analyser.](cdc21bbfcba380e98ece42e5b8da50bb_img.jpg) + +``` +graph LR; WCDMA[WCDMA Signal Generator] --> Repeater[Repeater under test]; Repeater --> Analyser[Signal analyser]; +``` + +Block diagram of the measuring system set-up for modulation accuracy: error vector magnitude. The diagram shows a WCDMA Signal Generator connected to a Repeater under test, which is in turn connected to a Signal analyser. + +**Figure A.6: Measuring system set-up for modulation accuracy: error vector magnitude.** + +Note that a repeater is a bi-directional device. The signal generator may need protection. + +## A.7 Modulation Accuracy: Peak Code Domain Error Error and Relative Coder Domain Error + +![Block diagram of the measuring system set-up for modulation accuracy: peak code domain error and relative code domain error. The diagram shows a WCDMA Signal Generator connected to a Repeater under test, which is in turn connected to a Signal analyser.](24a27d17656bcf0ee131539f2bbb34cd_img.jpg) + +``` +graph LR; WCDMA[WCDMA Signal Generator] --> Repeater[Repeater under test]; Repeater --> Analyser[Signal analyser]; +``` + +Block diagram of the measuring system set-up for modulation accuracy: peak code domain error and relative code domain error. The diagram shows a WCDMA Signal Generator connected to a Repeater under test, which is in turn connected to a Signal analyser. + +**Figure A.7: Measuring system set-up for modulation accuracy: peak code domain error and relative code domain error.** + +Note that a repeater is a bi-directional device. The signal generator may need protection. + +## A.8 Input inter modulation + +![Block diagram for input intermodulation measurement. A CW Signal Generator is connected to the input of a Repeater under test. The output of the Repeater under test is connected to a Spectrum analyser.](04f7b8f64493f6d83188232f10f86fe2_img.jpg) + +``` +graph LR; CW[\"CW Signal Generator\"] --> Repeater[\"Repeater under test\"]; Repeater --> SA[\"Spectrum analyser\"]; +``` + +Block diagram for input intermodulation measurement. A CW Signal Generator is connected to the input of a Repeater under test. The output of the Repeater under test is connected to a Spectrum analyser. + +Figure A.8: Measuring system set-up for input intermodulation. + +## A.9 Output Intermodulation + +![Block diagram for output intermodulation measurement. Two WCDMA Signal Generators are connected to 5 MHz channel filters. The outputs of these filters are connected to a circulator. The circulator is also connected to a Spectrum analyser and a Repeater under test. The Repeater under test is connected to an attenuator, which is connected to the circulator.](18dbea0ac6b7ad13e47afda3ddd53b64_img.jpg) + +``` +graph LR; WCDMA1[\"WCDMA Signal Generator\"] --> F1[\"5 MHz channel filter\"]; WCDMA2[\"WCDMA Signal Generator\"] --> F2[\"5 MHz channel filter\"]; F1 --> C((\"circulator\")); F2 --> C; C --> SA[\"Spectrum analyser\"]; C --> Repeater[\"Repeater under test\"]; Repeater --> A[\"attenuator\"]; A --> C; +``` + +Block diagram for output intermodulation measurement. Two WCDMA Signal Generators are connected to 5 MHz channel filters. The outputs of these filters are connected to a circulator. The circulator is also connected to a Spectrum analyser and a Repeater under test. The Repeater under test is connected to an attenuator, which is connected to the circulator. + +Figure A.9: Measuring system set-up for Output Intermodulation. + +Note that a repeater is a bi-directional device. The signal generator may need protection. + +The 5 MHz channel filter is only required if the WCDMA signal generator does not fulfil the unwanted emission requirement for base stations (TS25.141 [11], section 6.5) with at least 10 dB margin in the described set-up. + +# --- Annex B (informative): Derivation of Test Requirements + +The Test Requirements in this specification have been calculated by relaxing the Minimum Requirements of the core specification using the Test Tolerances defined in subclause 5.2. When the Test Tolerance is zero, the Test Requirement will be the same as the Minimum Requirement. When the Test Tolerance is non-zero, the Test Requirements will differ from the Minimum Requirements, and the formula used for this relaxation is given in table B.1. + +## **Table B.1: Derivation of Test Requirements** + +| Clause number | Title | Minimum Requirement in TS 25.106 | Test Tolerance (TT) | Test Requirement in TS 25.143 | +|---------------|-----------------------------------|---------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 6.1 | Maximum output power | In normal conditions
Table 6.1 | 0,7 dB, $f \leq 3,0$ GHz;

1,0 dB,
$3,0$ GHz $< f \leq 4,2$ GHz | Formula:
Upper limit + TT
Lower limit – TT

In normal conditions refer to Table 6.3 | +| | | In extreme conditions
Tabel 6.2 | | In extreme conditions refer to Table 6.4 | +| 9.1.2 | Operating band unwanted emissions | Tables 9.1, 9.2, 9.3 and 9.4:
“Maximum level” = X dB | 1,5 dB, $f \leq 3,0$ GHz;
(0 dB for the additional Band II, IV, V, X, XII, XIII, XIV, XXV and XXVI requirements)

1,8 dB,
$3,0$ GHz $< f \leq 4,2$ GHz | Formula:
Maximum level + TT

Refer to tables 9.5, 9.6, 9.7 and 9.8
Tables 9.8A to 9.8F applies with TT = 0. | +| 7 | Frequency stability | 7.1 minimum requirement | 12 Hz | Formula:
Relative error + TT

Refer to 7.5 Test requirements | +| 8 | Out of Band Gain | Table 8.1: Out of band gain limits | 0,5 dB, $f \leq 3,0$ GHz; | Formula:
Maximum level + TT | +| | | | 0,8 dB,
$3,0$ GHz $< f \leq 4,2$ GHz | Refer to table 8.2 | +| 9.2 | Spurious emissions | Tables 9.5, to 9.15 | 0 dB | | +| 10.1 | Error Vector Magnitude | 10.1.1 Minimum requirement | 0 % | Formula:
RSS Stimulus EVM and Repeater EVM to get target EVM

Refer to 10.1.5 Test requirements | +| 10.2 | Peak code domain error | 10.2.1 Minimum requirement | 1,1 dB | Formula:
Maximum error + TT

Refer to 10.2.5 Test requirements | +| 10.3 | Relative code domain error | 10.3.1 Minimum requirement | 1,7 dB | Formula:
Maximum error + TT

Formula for linear offset:
Linear addition of relative error power from measurement system and repater

Formula TT:
Offset – minimum requirement.

Refer to 10.3.5 Test requirements | +| 11 | Input intermodulation | 11.5 Minimum requirements, and Tables 11.1 and 11.2 | 1,2 dB | Maximum in-band power increase + TT

Refer to 11.5 Test requirements. | + +| | | | | | +|----|------------------------|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------| +| 12 | Output intermodulation | 12.1 Minimum requirements | 1,5 dB for operating band unwanted emission

(0 dB for the additional Band II, IV, V, X, XII, XIII, XIV, XXV and XXVI requirements)
0 dB for spurious emissions | Maximum level + TT

Refer to tables 9.5 to 9.19

(Tables 9.8A to 9.8F applies with TT = 0) | +|----|------------------------|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------| + +# Annex C (informative): Acceptable uncertainty of Test Equipment + +This informative annex specifies the critical parameters of the components of an overall Test System (e.g. signal generators, signal analysers etc.) which are necessary when assembling a Test System which complies with subclause 5.1 Acceptable uncertainty of Test System. These Test Equipment parameters are fundamental to the accuracy of the overall Test System and are unlikely to be improved upon through System Calibration. + +**Table C.1: Equipment accuracy** + +| Test | Equipment accuracy | Test condition | +|---------------------------------------------------|-------------------------------------------------------|----------------------------------------------------------------------------------------| +| 6.1 Maximum output power | Not critical | | +| 9.1 Spectrum emission mask | Not critical | | +| 9.2 Spurious emissions | Not critical | | +| 11 Input intermodulation (interferer requirement) | Not critical | | +| 7 Frequency error | $\pm 10 \text{ Hz} + \text{timebase} = 12 \text{ Hz}$ | Range 0 to 500 Hz. (This is to allow for UE range that at 0,1 PPM is larger than BTS). | +| 10.1 Error vector magnitude | $\pm 2,5 \%$ (for single code) | $P\_Max-3$ to $P\_Max - 18 \text{ dB}$
Applies for reading from 10% to 25%. | +| 10.2 Peak code domain error | | | +| 10.3 Relative code domain error | | | +| 8 Out of band gain | | | +| 11 Input intermodulation Characteristics | | | +| 12 Output intermodulation | | | + +# Annex D (informative): Change History + +| TSG | Doc | CR | R | Title | Cat | Curr | New | Work Item | +|-------|-----------|------|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------|--------|------------------| +| RP-31 | | | | Rel-7 version created from v6.4.0 | | | 7.0.0 | | +| RP-31 | RP-060100 | 0053 | 2 | Introduction of operating band III to IX requirements in 25.143 | B | 6.3.0 | 7.0.0 | TEI7 | +| RP-31 | RP-060110 | 0054 | | Correction of spurious emissions for coexistence with GSM900 in same geographic area | F | 6.3.0 | 7.0.0 | RinImp-UMTS900 | +| RP-33 | RP-060520 | 0057 | 1 | Clean up of Spurious emissions | A | 7.0.0 | 7.1.0 | TEI5 | +| RP-33 | RP-060521 | 0060 | 1 | New UTRA Repeater up-link spurious emissions limits for co-existence/co-location with TDD | A | 7.0.0 | 7.1.0 | TEI5 | +| RP-34 | RP-060811 | 0063 | 1 | Corrections to input intermodulation | A | 7.1.0 | 7.2.0 | TEI5 | +| RP-36 | RP-070370 | 0067 | | Category B spurious emission limits for UTRA Repeater | A | 7.2.0 | 7.3.0 | TEI4 | +| RP-36 | RP-070373 | 0068 | | Introduction of operating band X into the repeater specification | B | 7.2.0 | 7.3.0 | TEI7 | +| RP-39 | RP-080126 | 0069 | | Introduction of UMTS1500 requirements | B | 7.3.0 | 8.0.0 | RinImp8-UMTS1500 | +| RP-42 | RP-080943 | 71 | 1 | Introduction of operating band unwanted emission | F | 8.0.0 | 8.1.0 | TEI8 | +| RP-44 | RP-080555 | 72 | | Spurious emission testing for repeater capable of UTRA and E-UTRA | F | 8.1.0 | 8.2.0 | TEI8 | +| RP-44 | RP-080555 | 73 | | Clean up | F | 8.1.0 | 8.2.0 | TEI8 | +| RP-44 | RP-080555 | 74 | | Test procedure amendment | F | 8.1.0 | 8.2.0 | TEI8 | +| RP-45 | RP-080819 | 75 | | Introduction of band XII, XIII, XIV | F | 8.2.0 | 8.3.0 | TEI8 | +| RP-45 | RP-080819 | 76 | | Operating band unwanted emissions test tolerance correction | F | 8.2.0 | 8.3.0 | TEI8 | +| RP-45 | RP-080819 | 77 | | CR to limit the scope to FDD only to 25.143 | F | 8.2.0 | 8.3.0 | TEI8 | +| RP-46 | RP-091277 | 078 | | Corrections on additional spectrum emission limits for Bands XII, XIII, XIV | F | 8.3.0 | 8.4.0 | TEI8 | +| RP-46 | RP-091281 | 079 | | Editorial corrections to 25.143 | F | 8.3.0 | 8.4.0 | TEI8 | +| | | | | Automatic upgrade from previous Release | | 8.4.0 | 9.0.0 | | +| RP-49 | RP-100913 | 083 | 2 | RCDE for 64QAM modulated codes for FDD Repeater | A | 9.0.0 | 9.1.0 | TEI7 | +| RP-49 | RP-100925 | 080 | | Introduction of operating band XIX, XX and XXI and correction of band XI | F | 9.0.0 | 9.1.0 | TEI9 | +| RP-50 | RP-101336 | 088 | | Protection of cdma and E-UTRA bands | A | 9.1.0 | 9.2.0 | TEI8 | +| RP-50 | RP-101337 | 090 | | Removal of brackets | A | 9.1.0 | 9.2.0 | TEI8 | +| RP-50 | RP-101347 | 084 | | Remove test settings for unwanted emissions from the minimum requirement | F | 9.1.0 | 9.2.0 | TEI9 | +| RP-50 | RP-101347 | 085 | | Corrections to the symbols and abbreviations clause related to DTT requirement | F | 9.1.0 | 9.2.0 | TEI9 | +| RP-50 | RP-101347 | 086 | | Co-existence with services in adjacent frequency bands | F | 9.1.0 | 9.2.0 | TEI9 | +| RP-50 | RP-101347 | 091 | | Editorial correction to TS 25.143 | F | 9.1.0 | 9.2.0 | TEI9 | +| RP-51 | RP-110352 | 092 | | Inclusion of E-UTRA TDD text to co-location on 25.143 | F | 9.2.0 | 10.0.0 | TEI10 | +| RP-55 | RP-120303 | 095 | 1 | Correction on the table of Regional requirements | B | 10.0.0 | 10.1.0 | TEI10 | +| RP-55 | RP-120303 | 096 | 1 | Introduction of operating frequency band XXII | B | 10.0.0 | 10.1.0 | TEI10 | +| RP-55 | RP-120303 | 097 | 1 | Introduction of operating frequency band XXV and protection limits towards E-UTRA Band 23 | B | 10.0.0 | 10.1.0 | TEI10 | +| RP-56 | RP-120783 | 099 | 2 | Update of the Definition clause with repeaters operating band definition and introduction of minor editorial changes for better alignment with BS core specification | F | 10.1.0 | 10.2.0 | TEI10 | +| RP-56 | RP-120765 | 104 | | Additional spurious emissions requirements for PHS | A | 10.1.0 | 10.2.0 | TEI8 | +| RP-57 | RP-121313 | 105 | 2 | Introduction of missing Spurious Emission and Input Intermodulation protection limits towards E-UTRA FDD Band 24 | F | 10.2.0 | 10.3.0 | TEI10 | + +| | | | | | | | | | +|-------|-----------|------|---|-----------------------------------------------------------------------------------------------------------------------------------------------------|---|--------|--------|--------------------------------------------------------------------------------------------------------------------------------------| +| RP-57 | RP-121312 | 109 | 1 | Repeater test uncertainties for UTRA bands above 3 GHz | F | 10.2.0 | 10.3.0 | RInImp8-UMTSLTE3500 | +| SP-57 | - | - | - | Update to Rel-11 version (MCC) | - | 10.3.0 | 11.0.0 | - | +| RP-58 | RP-121867 | 0113 | | Introduction of Spurious Emission limits and Input Intermodulation requirements towards missing UTRA and E-UTRA TDD frequency bands | A | 11.0.0 | 11.1.0 | TEI10 | +| RP-58 | RP-121867 | 0114 | | Introduction of a Note on non deployment of operating bands with overlapping frequency ranges for the tables for Input Intermodulation requirements | A | 11.0.0 | 11.1.0 | TEI10 | +| RP-58 | RP-121858 | 0115 | | Modifications of frequency ranges for E-UTRA Band 6, 18, 19 in the Tables for Spurious Emission limits and Input Intermodulation requirements | A | 11.0.0 | 11.1.0 | RInImp9-UMTSLTE800 | +| RP-58 | RP-121867 | 0118 | | The special cases for protection of UTRA Band III and Band X in co-existence and co-location with UTRA Repeaters | A | 11.0.0 | 11.1.0 | TEI10 | +| SP-65 | - | - | - | Update to Rel-12 version (MCC) | - | 11.1.0 | 12.0.0 | | +| RP-66 | RP-142154 | 121 | | Update with regard to operating bands of TS25.143 | F | 12.0.0 | 12.1.0 | LTE_UTRA_SDL_B andL-Perf, LTE450_Brazil-Perf, LTE_WCS_band-Perf, LTE_DL_FDD700-Perf, LTE_APAC700-Perf, LTE_e850_LB-Perf,E850_UB-Perf | +| SP-70 | - | - | - | Update to Rel-13 version (MCC) | - | 12.1.0 | 13.0.0 | | +| RP-75 | - | - | - | Update to Rel-14 version (MCC) | - | 13.0.0 | 14.0.0 | | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2018-06 | SA#80 | - | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-06 | SA#88 | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25172/86b4670fc1a5a694821ee92b99c1209a_img.jpg b/marked/Rel-16/25_series/25172/86b4670fc1a5a694821ee92b99c1209a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8a2dcba43ab5401765454d7354078042664f0cf --- /dev/null +++ b/marked/Rel-16/25_series/25172/86b4670fc1a5a694821ee92b99c1209a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70d9f15af4a9848b3b1952e6215248576a8fcd34610b154771089ccd13400154 +size 77723 diff --git a/marked/Rel-16/25_series/25172/b2ea162a0f53d5e0504b7d28346e0754_img.jpg b/marked/Rel-16/25_series/25172/b2ea162a0f53d5e0504b7d28346e0754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2c03edcfbc6162801faddaea82564080af28841 --- /dev/null +++ b/marked/Rel-16/25_series/25172/b2ea162a0f53d5e0504b7d28346e0754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3445fc605335ad3bcaf1f05a814710de21eb4f6c08d19947fb28d1920bb1469 +size 56337 diff --git a/marked/Rel-16/25_series/25172/e4c6fa93821e3546ee9fcae897ae2771_img.jpg b/marked/Rel-16/25_series/25172/e4c6fa93821e3546ee9fcae897ae2771_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0256fd7428c809df208538b141a595b1359c981c --- /dev/null +++ b/marked/Rel-16/25_series/25172/e4c6fa93821e3546ee9fcae897ae2771_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c11602a171aaf01eabeab15c510a433d8a398d86c352af4660e4f7866e3b6950 +size 25145 diff --git a/marked/Rel-16/25_series/25172/raw.md b/marked/Rel-16/25_series/25172/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..130af759fb051637379f2f354256c6da18a4cae6 --- /dev/null +++ b/marked/Rel-16/25_series/25172/raw.md @@ -0,0 +1,1165 @@ + + + + + + +# Contents + +| | | +|-----------------------------------------------------------------------|-----------| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols, abbreviations and test tolerances ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 7 | +| 3.4 Test tolerances..... | 8 | +| 4 General..... | 8 | +| 4.1 Introduction ..... | 8 | +| 4.2 Measurement parameters..... | 9 | +| 4.2.1 UE-based A-GANSS measurement parameters ..... | 9 | +| 4.2.2 UE-assisted A-GANSS measurement parameters ..... | 9 | +| 4.3 Response time ..... | 9 | +| 4.4 Time assistance ..... | 9 | +| 4.4.1 Use of fine time assistance ..... | 9 | +| 4.5 RRC states..... | 10 | +| 4.6 2D position error ..... | 10 | +| 4.7 User equipment supporting multiple constellations ..... | 10 | +| 4.8 User equipment supporting multiple signals..... | 10 | +| 5 A-GANSS minimum performance requirements..... | 10 | +| 5.1 Sensitivity..... | 11 | +| 5.1.1 Coarse time assistance..... | 11 | +| 5.1.1.1 Minimum requirements (coarse time assistance)..... | 11 | +| 5.1.2 Fine time assistance..... | 12 | +| 5.1.2.1 Minimum requirements (fine time assistance)..... | 12 | +| 5.2 Nominal accuracy..... | 12 | +| 5.2.1 Minimum requirements (nominal accuracy) ..... | 13 | +| 5.3 Dynamic range ..... | 13 | +| 5.3.1 Minimum requirements (dynamic range)..... | 14 | +| 5.4 Multi-path scenario ..... | 14 | +| 5.4.1 Minimum requirements (multi-path scenario)..... | 15 | +| 5.5 Moving scenario and periodic update ..... | 15 | +| 5.5.1 Minimum requirements (moving scenario and periodic update)..... | 16 | +| Annex A (normative): Test cases..... | 18 | +| A.1 Conformance tests..... | 18 | +| A.2 Requirement classification for statistical testing ..... | 18 | +| Annex B (normative): Test conditions..... | 19 | +| B.1 General..... | 19 | +| B.1.1 Parameter values ..... | 19 | +| B.1.2 Time assistance ..... | 19 | +| B.1.3 GANSS reference time..... | 19 | +| B.1.4 Reference and UE locations ..... | 20 | +| B.1.5 Satellite constellation and assistance data..... | 20 | +| B.1.6 Atmospheric delay..... | 20 | +| B.1.7 Sensors ..... | 20 | +| B.1.8 Information elements..... | 20 | +| B.1.9 GNSS signals..... | 20 | +| B.1.10 RESET UE POSITIONING STORED INFORMATION Message ..... | 20 | +| B.1.11 GNSS system time offsets..... | 21 | + +| | | | +|-----------------------------|--------------------------------------------------------------------------------|-----------| +| Annex C (normative): | Propagation conditions ..... | 22 | +| C.1 | Static propagation conditions..... | 22 | +| C.2 | Multi-path case..... | 22 | +| Annex D (normative): | Measurement sequence chart..... | 24 | +| D.1 | General..... | 24 | +| D.2 | TTFF measurement sequence chart ..... | 24 | +| D.3 | Periodic update measurement sequence chart..... | 25 | +| Annex E (normative): | Assistance data required for testing ..... | 27 | +| E.1 | Introduction..... | 27 | +| E.2 | GPS assistance data..... | 27 | +| E.3 | GANSS assistance data..... | 27 | +| Annex F (normative): | Converting UE-assisted measurement reports into position estimates .... | 31 | +| F.1 | Introduction..... | 31 | +| F.2 | UE measurement reports..... | 31 | +| F.3 | Weighted Least Squares (WLS) position solution ..... | 32 | +| Annex G (informative): | Change history..... | 35 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd 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 establishes the minimum performance requirements for A-GANSS for FDD mode of UTRA for the User Equipment (UE) that supports A-GANSS. It includes the minimum performance requirements for both UE-based and UE-assisted A-GANSS. The minimum performance requirements also include combinations of A-GPS and A-GANSS. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TS 25.101: "User Equipment (UE) radio transmission and reception (FDD)". +- [2] 3GPP TS 25.104: "Base Station (BS) radio transmission and reception (FDD)". +- [3] IS-GPS-200, Revision D, "Navstar GPS Space Segment/Navigation User Interfaces", March 7th, 2006. +- [4] IS-GPS-705, "Navstar GPS Space Segment/User Segment L5 Interfaces", September 22, 2005. +- [5] IS-GPS-800, "Navstar GPS Space Segment/User Segment L1C Interfaces", September 4, 2008. +- [6] IS-QZSS, "Quasi Zenith Satellite System Navigation Service Interface Specifications for QZSS", Ver.1.1, July 31, 2009. +- [7] "Galileo OS Signal in Space ICD (OS SIS ICD)", Draft 0, Galileo Joint Undertaking, May 23rd, 2006. +- [8] "Global Navigation Satellite System GLONASS Interface Control Document", Version 5.1, 2008. +- [9] "Specification for the Wide Area Augmentation System (WAAS) ", US Department of Transportation, Federal Aviation Administration, DTFA01-96-C-00025, 2001. +- [10] 3GPP TS 25.171: "Requirements for support of Assisted Global Positioning System (A-GPS) Frequency Division Duplex (FDD)". +- [11] 3GPP TS 34.171: "Terminal Conformance Specification, Assisted Global Positioning System (A-GPS) (FDD)". +- [12] 3GPP TS 34.172: "Terminal Conformance Specification, Assisted Galileo and Additional Navigation Satellite Systems (A-GANSS) (FDD)". +- [13] 3GPP TS 34.109: "Special conformance testing functions". +- [14] 3GPP TS 25.331: "Radio Resource Control (RRC) protocol specification". +- [15] ETSI TR 102 273-1-2: "Electromagnetic compatibility and Radio spectrum Matters (ERM); Improvement on Radiated Methods of Measurement (using test site) and evaluation of the corresponding measurement uncertainties; Part 1: Uncertainties in the measurement of mobile radio equipment characteristics; Sub-part 2: Examples and annexes". +- [16] P. Axelrad, R.G. Brown, "GPS Navigation Algorithms", in Chapter 9 of "Global Positioning System: Theory and Applications", Volume 1, B.W. Parkinson, J.J. Spilker (Ed.), Am. Inst. of Aeronautics and Astronautics Inc., 1996. + +- [17] S.K. Gupta, "Test and Evaluation Procedures for the GPS User Equipment", ION-GPS Red Book, Volume 1, p. 119. +- [18] 3GPP TS 25.215: "Physical layer; Measurements (FDD)". +- [19] BeiDou Navigation Satellite System Signal In Space Interface Control Document Open Service Signal B1I(Version 1.0), China Satellite Navigation Office, December 2012. + +# 3 Definitions, symbols, abbreviations and test tolerances + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TS 25.101 [1], 3GPP TS 25.104 [2] and the following apply: + +**Horizontal Dilution Of Precision (HDOP):** measure of position determination accuracy that is a function of the geometrical layout of the satellites used for the fix, relative to the receiver antenna. + +## 3.2 Symbols + +For the purposes of the present document, the following symbol applies: + +| | | +|---------------------------------|----------------------------------------------------------------------------------------------------------------------------| +| B1I | BeiDou B1I navigation signal with carrier frequency of 1561.098 MHz. | +| c | Speed of light. | +| E1 | Galileo E1 navigation signal with carrier frequency of 1575.420 MHz. | +| E5 | Galileo E5 navigation signal with carrier frequency of 1191.795 MHz. | +| E6 | Galileo E6 navigation signal with carrier frequency of 1278.750 MHz. | +| G1 | GLONASS navigation signal in the L1 sub-bands with carrier frequencies $1602 \text{ MHz} \pm k \times 562.5 \text{ kHz}$ . | +| G2 | GLONASS navigation signal in the L2 sub-bands with carrier frequencies $1246 \text{ MHz} \pm k \times 437.5 \text{ kHz}$ . | +| k | GLONASS channel number, $k = -7 \dots 13$ . | +| L1 C/A | GPS or QZSS L1 navigation signal carrying the Coarse/Acquisition code with carrier frequency of 1575.420 MHz. | +| L1C | GPS or QZSS L1 Civil navigation signal with carrier frequency of 1575.420 MHz. | +| L2C | GPS or QZSS L2 Civil navigation signal with carrier frequency of 1227.600 MHz. | +| L5 | GPS or QZSS L5 navigation signal with carrier frequency of 1176.450 MHz. | +| G | Geometry Matrix. | +| $\rho_{\text{GNSS}_m, i}$ | Measured pseudo-range of satellite i of $\text{GNSS}_m$ . | +| W | Weighting Matrix. | +| $\mathbf{1}_{\text{GNSS}_m, i}$ | Line of sight unit vector from the user to the satellite i of $\text{GNSS}_m$ . | +| x | State vector of user position and clock bias. | + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|---------|----------------------------------------------------------------------------------------------| +| A-GANSS | Assisted-Galileo and Additional Navigation Satellite Systems | +| A-GNSS | Assisted-GNSS | +| A-GPS | Assisted-Global Positioning System | +| AWGN | Additive White Gaussian Noise | +| BDS | BeiDou Navigation Satellite System | +| C/A | Coarse/Acquisition | +| DUT | Device Under Test | +| ECEF | Earth-Centered, Earth-Fixed | +| ECI | Earth-Centered-Inertial | +| FDD | Frequency Division Duplex | +| GEO | Geostationary Earth Orbit | +| GLONASS | GLObal'naya NAVigatsionnaya Sputnikovaya Sistema (Engl.: Global Navigation Satellite System) | + +| | | +|--------|--------------------------------------------| +| GNSS | Global Navigation Satellite System | +| GPS | Global Positioning System | +| GSS | GNSS System Simulator | +| HDOP | Horizontal Dilution Of Precision | +| ICD | Interface Control Document | +| IGSO | Inclined Geosynchronous Satellite Orbit | +| IS | Interface Specification | +| LOS | Line Of Sight | +| MEO | Medium Earth Orbit | +| QZS | Quasi-Zenith Satellite | +| QZSS | Quasi-Zenith Satellite System | +| RF | Radio Frequency | +| RRC | Radio Resource Control | +| SBAS | Space Based Augmentation System | +| SFN | System Frame Number | +| SS | FDD System Simulator | +| SV | Space Vehicle | +| TBD | To Be Determined | +| TOD | Time Of Day | +| TOW | Time Of Week | +| TTFF | Time To First Fix | +| UE | User Equipment | +| UTRA | Universal Terrestrial Radio Access | +| UTRAN | Universal Terrestrial Radio Access Network | +| WLS | Weighted Least Squares | +| WGS-84 | World Geodetic System 1984 | + +## 3.4 Test tolerances + +The requirements given in the present document make no allowance for measurement uncertainty. The test specification 3GPP TS 34.172 [12] defines test tolerances. These test tolerances are individually calculated for each test. The test tolerances are then added to the limits in the present document to create test limits. The measurement results are compared against the test limits as defined by the shared risk principle. + +Shared Risk is defined in ETR 273-1-2 [15], subclause 6.5. + +# --- 4 General + +## 4.1 Introduction + +The present document defines the minimum performance requirements for both UE-based and UE-assisted FDD A-GNSS terminals. The minimum performance requirements also include combinations of A-GPS and A-GNSS. + +## 4.2 Measurement parameters + +### 4.2.1 UE-based A-GNSS measurement parameters + +In case of UE-based A-GNSS, the measurement parameters are contained in the RRC UE POSITIONING POSITION ESTIMATE INFO IE. The measurement parameter in case of UE-based A-GNSS is the horizontal position estimate reported by the UE and expressed in latitude/longitude. + +### 4.2.2 UE-assisted A-GNSS measurement parameters + +In case of UE-assisted A-GNSS, the measurement parameters are contained in the RRC UE POSITIONING GNSS MEASURED RESULTS IE. The measurement parameters in case of UE-assisted A-GNSS are the UE GNSS code measurements, as specified in 3GPP TS 25.215 [18]. The UE GNSS code measurements that may be combined with UE GPS code phase measurements as specified in 3GPP TS 25.215 [18] are converted into a horizontal position estimate using the procedure detailed in Annex F. + +## 4.3 Response time + +Max Response Time is defined as the time starting from the moment that the UE has received the final RRC measurement control message containing reporting criteria different from "No Reporting" sent before the UE sends the measurement report containing the position estimate or the GANSS and GPS measured result, and ending when the UE starts sending the measurement report containing the position estimate or the GPS and GANSS measured result on the Uu interface. The response times specified for all test cases are Time-to-First-Fix (TTFF) unless otherwise stated, i.e. the UE shall not re-use any information on GANSS and GPS time, location or other aiding data that was previously acquired or calculated and stored internally in the UE. A dedicated test message 'RESET UE POSITIONING STORED INFORMATION' has been defined in TS 34.109 [13] clause 5.4 for the purpose of deleting this information and is detailed in subclause B.1.10. + +## 4.4 Time assistance + +Time assistance is the provision of GANSS reference time to the UE from the network via RRC messages. Currently two different GANSS time assistance methods can be provided by the network. + +- a) Coarse time assistance is always provided by the network and provides current GANSS time to the UE. The time provided is within $\pm 2$ seconds of GANSS system time. It is signalled to the UE by means of the GANSS Day and GANSS TOD fields in the GANSS Reference Time assistance data IE. +- b) Fine time assistance is optionally provided by the network and adds the provision to the UE of the relationship between the GANSS system time and the current UTRAN time. The accuracy of this relationship is $\pm 10 \mu\text{s}$ of the actual relationship. This addresses the case when the network can provide an improved GANSS time accuracy. It is signalled to the UE by means of the SFN and UTRAN GANSS timing of cell frames fields in the GANSS Reference Time assistance data IE. + +The specific GANSS system time is identified through the GANSS Time ID field of the GANSS Reference Time IE. In case where several GANSS are used in the tests, only one GANSS Time ID is used to determine the Time of Day. For all the constellations, the GANSS Time Model assistance and UTC Model assistance shall be available at the system simulator, as specified in Annex E. + +The time of applicability of time assistance is the beginning of the System Frame of the message containing the GANSS Reference time. + +### 4.4.1 Use of fine time assistance + +The use of fine time assistance to improve the GANSS performance of the UE is optional for the UE, even when fine time assistance is signalled by the network. Thus, there are a set minimum performance requirements defined for all UEs and additional minimum performance requirements that are valid for fine time assistance capable UEs only. These requirements are specified in subclause 5.1.2. + +## 4.5 RRC states + +The minimum A-GANSS performance requirements are specified in clause 5 for different RRC states that include Cell\_DCH and Cell\_FACH. Cell\_PCH and URA\_PCH states are for further study. The test and verification procedures are separately defined in Annex B. + +## 4.6 2D position error + +The 2D position error is defined by the horizontal difference in meters between the ellipsoid point reported or calculated from the UE Measurement Report and the actual position of the UE in the test case considered. + +## 4.7 User equipment supporting multiple constellations + +Minimum performance requirements are defined for each global GANSS constellation (Galileo, Modernized GPS, GLONASS and BDS). UEs supporting multiple global constellations shall meet the minimum performance requirements for a combined scenario where each UE supported constellation is simulated. + +NOTE: For test cases where signals from "GPS" and "Modernized GPS" are included, "GPS" and "Modernized GPS" are considered as a single constellation, unless otherwise specified. + +## 4.8 User equipment supporting multiple signals + +For UEs supporting multiple signals, different minimum performance requirements may be associated with different signals. The satellite simulator shall generate all signals supported by the UE. Signals not supported by the UE do not need to be simulated. The relative power levels of each signal type for each GNSS are defined in Table 4.8-1. The individual test scenarios in clause 5 define the reference signal power level for each satellite. The power level of each simulated satellite signal type shall be set to the reference signal power level defined in each test scenario in clause 5 plus the relative power level defined in Table 4.8-1. + +**Table 4.8-1: Relative signal power levels for each signal type for each GNSS** + +| | Galileo | | GPS/Modernized GPS | | GLONASS | | QZSS | | SBAS | | BDS | | | +|--|--------------------------------------------------------|-------|--------------------|---------|---------|-------|--------|---------|------|------|-----|----|-------| +| | Signal power levels relative to reference power levels | | | | | | | | | | | | | +| | E1 | 0 dB | L1 C/A | 0 dB | G1 | 0 dB | L1 C/A | 0 dB | L1 | 0 dB | B1I | D1 | 0 dB | +| | E6 | +2 dB | L1C | +1.5 dB | G2 | -6 dB | L1C | +1.5 dB | | | | D2 | +5 dB | +| | E5 | +2 dB | L2C | -1.5 dB | | | L2C | -1.5 dB | | | | | | +| | | | L5 | +3.6 dB | | | L5 | +3.6 dB | | | | | | + +NOTE 1: For test cases which involve "Modernized GPS", the satellite simulator shall also generate the GPS L1 C/A signal if the UE supports "GPS" in addition to "Modernized GPS". + +NOTE 2: The signal power levels in the Test Parameter Tables represent the total signal power of the satellite per channel not e.g. pilot and data channels separately. + +NOTE 3: For test cases which involve "BDS", D1 represents MEO/IGSO satellites B1I signal type and D2 represents GEO satellites B1I signal type. + +# 5 A-GNSS minimum performance requirements + +The A-GNSS minimum performance requirements are defined by assuming that all relevant and valid assistance data is received by the UE in order to perform GPS and GANSS measurements and/or position calculation. This clause does not include nor consider delays occurring in the various signalling interfaces of the network. + +In the following subclauses the minimum performance requirements are based on availability of the assistance data information and messages defined in Annexes D and E. + +The requirements in CELL\_PCH and URA\_PCH states are for further study. + +## 5.1 Sensitivity + +A sensitivity requirement is essential for verifying the performance of A-GNSS receiver in weak satellite signal conditions. In order to test the most stringent signal levels for the satellites the sensitivity test case is performed in AWGN channel. This test case verifies the performance of the first position estimate, when the UE is provided with only coarse time assistance and when it is additionally supplied with fine time assistance. + +### 5.1.1 Coarse time assistance + +In this test case 6 satellites are generated for the terminal. AWGN channel model is used. + +**Table 5.1.1-1: Test parameters** + +| System | Parameters | Unit | Value | +|--------------------|-------------------------------------------|---------|-------------------| +| | Number of generated satellites per system | - | See Table 5.1.1-2 | +| | Total number of generated satellites | - | 6 | +| | HDOP range | | 1.4 to 2.1 | +| | Propagation conditions | - | AWGN | +| | GANSS coarse time assistance error range | seconds | ±2 | +| Galileo | Reference high signal power level | dBm | -142 | +| | Reference low signal power level | dBm | -147 | +| GPS (1) | Reference high signal power level | dBm | -142 | +| | Reference low signal power level | dBm | -147 | +| GLONASS | Reference high signal power level | dBm | -142 | +| | Reference low signal power level | dBm | -147 | +| BDS | Reference high signal power level | dBm | -136 | +| | Reference low signal power level | dBm | -145 | + +Note 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. + +**Table 5.1.1-2: Power level and satellite allocation** + +| | | Satellite allocation for each constellation | | | +|----------------------|-------------------|---------------------------------------------|--------|--------| +| | | GNSS-1 (1) | GNSS-2 | GNSS-3 | +| Single constellation | High signal level | 1 | - | - | +| | Low signal level | 5 | - | - | +| Dual constellation | High signal level | 1 | - | - | +| | Low signal level | 2 | 3 | - | +| Triple constellation | High signal level | 1 | - | - | +| | Low signal level | 1 | 2 | 2 | + +Note 1: For GPS capable receivers, GNSS-1, i.e. the system having the satellite with high signal level, shall be GPS. + +#### 5.1.1.1 Minimum requirements (coarse time assistance) + +The position estimates shall meet the accuracy and response time specified in table 5.1.1.1-1. + +**Table 5.1.1.1-1: Minimum requirements (coarse time assistance)** + +| System | Success rate | 2-D position error | Max response time | +|--------|--------------|--------------------|-------------------| +| All | 95 % | 100 m | 20 s | + +### 5.1.2 Fine time assistance + +This requirement is only valid for fine time assistance capable UEs. In this requirement 6 satellites are generated for the terminal. AWGN channel model is used. + +**Table 5.1.2-1: Test parameters** + +| System | Parameters | Unit | Value | +|--------------------|-------------------------------------------|---------|-------------------| +| | Number of generated satellites per system | - | See Table 5.1.2-2 | +| | Total number of generated satellites | - | 6 | +| | HDOP range | | 1.4 to 2.1 | +| | Propagation conditions | - | AWGN | +| | GANSS coarse time assistance error range | seconds | ±2 | +| | GANSS fine time assistance error range | µs | ±10 | +| Galileo | Reference signal power level | dBm | -147 | +| GPS (1) | Reference signal power level | dBm | -147 | +| GLONASS | Reference signal power level | dBm | -147 | +| BDS | Reference signal power level | dBm | -147 | + +Note 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. + +**Table 5.1.2-2: Satellite allocation** + +| | Satellite allocation for each constellation | | | +|----------------------|---------------------------------------------|--------|--------| +| | GNSS-1 | GNSS-2 | GNSS-3 | +| Single constellation | 6 | - | - | +| Dual constellation | 3 | 3 | - | +| Triple constellation | 2 | 2 | 2 | + +#### 5.1.2.1 Minimum requirements (fine time assistance) + +The position estimates shall meet the accuracy and response time requirements in table 5.1.2.1-1. + +**Table 5.1.2.1-1: Minimum requirements for fine time assistance capable terminals** + +| System | Success rate | 2-D position error | Max response time | +|--------|--------------|--------------------|-------------------| +| All | 95 % | 100 m | 20 s | + +## 5.2 Nominal accuracy + +Nominal accuracy requirement verifies the accuracy of A-GANSS position estimate in ideal conditions. The primarily aim of the test is to ensure good accuracy for a position estimate when satellite signal conditions allow it. This test case verifies the performance of the first position estimate. + +In this requirement 6 satellites are generated for the terminal. If SBAS is to be tested one additional satellite shall be generated. AWGN channel model is used. The number of simulated satellites for each constellation is as defined in table 5.2-2. + +**Table 5.2-1: Test parameters** + +| System | Parameters | Unit | Value | +|--------------------|-------------------------------------------------|---------|-----------------------| +| | Number of generated satellites per system | - | See Table 5.2-2 | +| | Total number of generated satellites | - | 6 or 7 (2) | +| | HDOP Range | - | 1.4 to 2.1 | +| | Propagation conditions | - | AWGN | +| | GANSS coarse time assistance error range | seconds | ±2 | +| GPS (1) | Reference signal power level for all satellites | dBm | -128.5 | +| Galileo | Reference signal power level for all satellites | dBm | -127 | +| GLONASS | Reference signal power level for all satellites | dBm | -131 | +| QZSS | Reference signal power level for all satellites | dBm | -128.5 | +| SBAS | Reference signal power level for all satellites | dBm | -131 | +| BDS | Reference signal power level for all satellites | dBm | -133 | + +Note 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. +Note 2: 7 satellites apply only for SBAS case. + +If QZSS is supported, one of the GPS satellites will be replaced by a QZSS satellite with respective signal support. + +If SBAS is supported, the SBAS satellite with the highest elevation will be added to the scenario. + +**Table 5.2-2: Satellite allocation** + +| | Satellite allocation for each constellation | | | | +|----------------------------------------------------------------------------|---------------------------------------------|-----------------------|-----------------------|------| +| | GNSS 1 (1) | GNSS 2 (1) | GNSS 3 (1) | SBAS | +| Single constellation | 6 | -- | -- | 1 | +| Dual constellation | 3 | 3 | -- | 1 | +| Triple constellation | 2 | 2 | 2 | 1 | +| Note 1: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS. | | | | | + +### 5.2.1 Minimum requirements (nominal accuracy) + +The position estimates shall meet the accuracy and response time requirements in table 5.2.1-1. + +**Table 5.2.1-1: Minimum requirements** + +| System | Success rate | 2-D position error | Max response time | +|--------|--------------|--------------------|-------------------| +| All | 95 % | 15 m | 20 s | + +## 5.3 Dynamic range + +The aim of a dynamic range requirement is to ensure that a GANSS receiver performs well when visible satellites have rather different signal levels. Strong satellites are likely to degrade the acquisition of weaker satellites due to their cross-correlation products. Hence, it is important in this test case to keep use AWGN in order to avoid loosening the requirements due to additional margin because of fading channels. This test case verifies the performance of the first position estimate. + +In this requirement 6 satellites are generated for the terminal. Two different reference power levels, denoted as "high" and "low" are used for each GNSS. The allocation of "high" and "low" power level satellites depends on the number of supported GNSSs and it is defined in Table 5.3-2. AWGN channel model is used. + +**Table 5.3-1: Test parameters** + +| System | Parameters | Unit | Value | +|---------------------------------------------------------------------------------------------|-------------------------------------------|---------|-----------------| +| | Number of generated satellites per system | - | See Table 5.3-2 | +| | Total number of generated satellites | - | 6 | +| | HDOP Range | - | 1.4 to 2.1 | +| | Propagation conditions | - | AWGN | +| | GANSS coarse time assistance error range | seconds | ±2 | +| Galileo | Reference high signal power level | dBm | -127.5 | +| | Reference low signal power level | dBm | -147 | +| GPS (1) | Reference high signal power level | dBm | -129 | +| | Reference low signal power level | dBm | -147 | +| GLONASS | Reference high signal power level | dBm | -131.5 | +| | Reference low signal power level | dBm | -147 | +| BDS | Reference high signal power level | dBm | -133.5 | +| | Reference low signal power level | dBm | -145 | +| Note 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. | | | | + +**Table 5.3-2: Power level and satellite allocation** + +| | | Satellite allocation for each constellation | | | +|----------------------------------------------------------------------------|-------------------|---------------------------------------------|-----------------------|-----------------------| +| | | GNSS 1 (1) | GNSS 2 (1) | GNSS 3 (1) | +| Single constellation | High signal level | 2 | -- | -- | +| | Low signal level | 4 | -- | -- | +| Dual constellation | High signal level | 1 | 1 | -- | +| | Low signal level | 2 | 2 | -- | +| Triple constellation | High signal level | 1 | 1 | 1 | +| | Low signal level | 1 | 1 | 1 | +| Note 1: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS. | | | | | + +### 5.3.1 Minimum requirements (dynamic range) + +The position estimates shall meet the accuracy and response time requirements in table 5.3.1-1. + +**Table 5.3.1-1: Minimum requirements** + +| System | Success rate | 2-D position error | Max response time | +|--------|--------------|--------------------|-------------------| +| All | 95 % | 100 m | 20 s | + +## 5.4 Multi-path scenario + +The purpose of the test case is to verify the receiver's tolerance to multipath while keeping the test setup simple. This test case verifies the performance of the first position estimate. + +In this test 6 satellites are generated for the terminal. Some of the satellites have a one tap channel representing the Line-Of-Sight (LOS) signal. The other satellites have a two-tap channel, where the first tap represents the LOS signal and the second represents a reflected and attenuated signal as specified in Annex C.2. The number of satellites generated for each GNSS as well as the channel model used depends on the number of systems supported by the UE and is defined in table 5.4-2. The channel model as specified in Annex C.2 further depends on the generated signal. + +**Table 5.4-1: Test parameter** + +| System | Parameters | Unit | Value | +|---------------------------------------------------------------------------------------------|-------------------------------------------|---------|-----------------| +| | Number of generated satellites per system | - | See Table 5.4-2 | +| | Total number of generated satellites | - | 6 | +| | HDOP range | | 1.4 to 2.1 | +| | Propagation conditions | - | AWGN | +| | GNSS coarse time assistance error range | seconds | ±2 | +| Galileo | Reference signal power level | dBm | -127 | +| GPS (1) | Reference signal power level | dBm | -128.5 | +| GLONASS | Reference signal power level | dBm | -131 | +| BDS | Reference signal power level | dBm | -133 | +| Note 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. | | | | + +**Table 5.4-2: Channel model allocation** + +| | | Channel model allocation for each constellation | | | +|----------------------|-----------------|-------------------------------------------------|--------|--------| +| | | GNSS-1 | GNSS-2 | GNSS-3 | +| Single constellation | One-tap channel | 2 | -- | -- | +| | Two-tap channel | 4 | -- | -- | +| Dual constellation | One-tap channel | 1 | 1 | -- | +| | Two-tap channel | 2 | 2 | -- | +| Triple constellation | One-tap channel | 1 | 1 | 1 | +| | Two-tap channel | 1 | 1 | 1 | + +### 5.4.1 Minimum requirements (multi-path scenario) + +The position estimates shall meet the accuracy and response time requirements in table 5.4.1-1. + +**Table 5.4.1-1: Minimum requirements** + +| System | Success rate | 2-D position error | Max response time | +|--------|--------------|--------------------|-------------------| +| All | 95 % | 100 m | 20 s | + +## 5.5 Moving scenario and periodic update + +The purpose of the test case is to verify the receiver's capability to produce GANSS measurements or location fixes on a regular basis, and to follow when it is located in a vehicle that slows down, turns or accelerates. A good tracking performance is essential for certain location services. A moving scenario with periodic update is well suited for verifying the tracking capabilities of an A-GANSS receiver in changing UE speed and direction. In the requirement the UE moves on a rectangular trajectory, which imitates urban streets. AWGN channel model is used. This test is not performed as a Time to First Fix (TTFF) test. + +In this requirement 6 satellites are generated for the terminal. The UE is requested to use periodical reporting with a reporting interval of 2 seconds. + +The UE moves on a rectangular trajectory of 940 m by 1440 m with rounded corner defined in figure 5.5-1. The initial reference is first defined followed by acceleration to final speed of 100 km/h in 250 m. The UE then maintains the speed for 400 m. This is followed by deceleration to final speed of 25 km/h in 250 m. The UE then turn 90 degrees with turning radius of 20 m at 25 km/h. This is followed by acceleration to final speed of 100 km/h in 250 m. The sequence is repeated to complete the rectangle. + +**Table 5.5-1: Trajectory Parameters** + +| Parameter | Distance (m) | Speed (km/h) | +|----------------------------------|--------------|-------------------------| +| $l_{11}, l_{15}, l_{21}, l_{25}$ | 20 | 25 | +| $l_{12}, l_{14}, l_{22}, l_{24}$ | 250 | 25 to 100 and 100 to 25 | +| $l_{13}$ | 400 | 100 | +| $l_{23}$ | 900 | 100 | + +![Diagram of a rectangular trajectory with rounded corners. The horizontal dimension is labeled 1 440 m and the vertical dimension is labeled 940 m. The corners have a radius r = 20 m. The trajectory is defined by points l11, l12, l13, l14, l15 on the left side and l21, l22, l23, l24, l25 on the right side. Arrows indicate the direction of movement: l15 to l14, l14 to l13, l13 to l12, l12 to l11, l11 to l21, l21 to l22, l22 to l23, l23 to l24, l24 to l25, and l25 to l15.](e4c6fa93821e3546ee9fcae897ae2771_img.jpg) + +Diagram of a rectangular trajectory with rounded corners. The horizontal dimension is labeled 1 440 m and the vertical dimension is labeled 940 m. The corners have a radius r = 20 m. The trajectory is defined by points l11, l12, l13, l14, l15 on the left side and l21, l22, l23, l24, l25 on the right side. Arrows indicate the direction of movement: l15 to l14, l14 to l13, l13 to l12, l12 to l11, l11 to l21, l21 to l22, l22 to l23, l23 to l24, l24 to l25, and l25 to l15. + +**Figure 5.5-1: Rectangular trajectory of the moving scenario and periodic update test case** + +**Table 5.5-2: Test Parameters** + +| System | Parameters | Unit | Value | +|---------------------------------------------------------------------------------------------|-------------------------------------------------|---------|-----------------| +| | Number of generated satellites per system | - | See Table 5.5-3 | +| | Total number of generated satellites | - | 6 | +| | HDOP Range per system | - | 1.4 to 2.1 | +| | Propagation conditions | - | AWGN | +| | GANSS coarse time assistance error range | seconds | ±2 | +| Galileo | Reference signal power level for all satellites | dBm | -127 | +| GPS (1) | Reference signal power level for all satellites | dBm | -128.5 | +| GLONASS | Reference signal power level for all satellites | dBm | -131 | +| BDS | Reference signal power level for all satellites | dBm | -133 | +| Note 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. | | | | + +**Table 5.5-3: Satellite allocation** + +| | Satellite allocation for each constellation | | | +|----------------------------------------------------------------------------|---------------------------------------------|-----------------------|-----------------------| +| | GNSS 1 (1) | GNSS 2 (1) | GNSS 3 (1) | +| Single constellation | 6 | -- | -- | +| Dual constellation | 3 | 3 | -- | +| Triple constellation | 2 | 2 | 2 | +| Note 1: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS. | | | | + +### 5.5.1 Minimum requirements (moving scenario and periodic update) + +The position estimates shall meet the accuracy requirement of table 5.5.1-1 with the periodical reporting interval defined in table 5.5.1-1 after the first reported position estimates. + +NOTE: In the actual testing the UE may report error messages until it has been able to acquire GPS/GANSS measured results or a position estimate. The test equipment shall only consider the first measurement report different from an error message as the first position estimate in the requirement in table 5.5.1-1. + +**Table 5.5.1-1: Minimum requirements** + +| System | Success rate | 2-D position error | Periodical reporting interval | +|--------|--------------|--------------------|-------------------------------| +| All | 95 % | 50 m | 2 s | + +# --- Annex A (normative): Test cases + +## A.1 Conformance tests + +The conformance tests are specified in 3GPP TS 34.172 [12]. Statistical interpretation of the requirements is described in clause A.2. + +## --- A.2 Requirement classification for statistical testing + +Requirements in the present document are either expressed as absolute requirements with a single value stating the requirement, or expressed as a success rate. There are no provisions for the statistical variations that will occur when the parameter is tested. + +Annex B lists the test parameters needed for the tests. The test will result in an outcome of a test variable value for the DUT inside or outside the test limit. Overall, the probability of a "good" DUT being inside the test limit(s) and the probability of a "bad" DUT being outside the test limit(s) should be as high as possible. For this reason, when selecting the test variable and the test limit(s), the statistical nature of the test is accounted for. + +When testing a parameter with a statistical nature, a confidence level has to be set. The confidence level establishes the probability that a DUT passing the test actually meets the requirement and determines how many times a test has to be repeated. The confidence levels are defined for the final tests in 3GPP TS 34.172 [12]. + +# Annex B (normative): Test conditions + +## B.1 General + +This annex specifies the additional parameters that are needed for the test cases specified in clause 5 and applies to all tests unless otherwise stated. + +### B.1.1 Parameter values + +Additionally, amongst all the listed parameters (see Annex E), the following values for some important parameters are to be used in the measurement control message. + +**Table B.1.1-1: Parameter values** + +| Information element | Value - TTFF tests
(except nominal
accuracy test) | Value - TTFF tests
(nominal accuracy
test) | Value - Periodic tests | +|----------------------------|---------------------------------------------------------|--------------------------------------------------|------------------------| +| Measurement Reporting Mode | Periodical reporting | Periodical reporting | Periodical reporting | +| Amount of reporting | 1 | 1 | Infinite (see Note) | +| Reporting interval | 20 000 ms | 20 000 ms | 2 000 ms | +| Horizontal accuracy | 51.2 m | 7.7 m | 24.5 m | +| Vertical accuracy | 102 m | 102 m | 102 m | +| Note: | Infinite means during the complete test time. | | | + +In the Sensitivity test case with Fine Time Assistance, the following parameter values are used. + +**Table B.1.1-2: Parameters for fine time assistance test** + +| Information element | Value | +|-----------------------------------------------|---------| +| TUTRAN-GPS drift rate | 0 | +| TUTRAN-GNSS drift rate | 0 | +| UE Positioning GPS Reference Time Uncertainty | 10.2 µs | +| GNSS TOD Uncertainty | 10.2 µs | + +### B.1.2 Time assistance + +For every Test Instance in each TTFF test case, the GNSS/GPS Reference Time shall have a random offset, relative to GNSS/GPS system time, within the error range of Coarse Time Assistance defined in the test case. This offset value shall have a uniform random distribution. + +In addition, for every Fine Time Assistance Test Instance the IE UTRAN GPS/GNSS timing of cell frames shall have a random offset, relative to the true value of the relationship between the two time references, within the error range of Fine Time Assistance defined in the test case. This offset value shall have a uniform random distribution. + +For the Moving Scenario and Periodic Update Test Case the GNSS/GPS Reference Time shall be set to the nominal value. + +### B.1.3 GNSS reference time + +For every Test Instance in each TTFF test case, the GNSS reference time (and GPS reference time, if applicable) shall be advanced so that, at the time the fix is made, it is at least 2 minutes later than the previous fix. + +### B.1.4 Reference and UE locations + +There is no limitation on the selection of the reference location, consistent with achieving the required HDOP for the Test Case. For each test instance the reference location shall change sufficiently such that the UE shall have to use the new assistance data. The uncertainty of the semi-major axis is 3 km. The uncertainty of the semi-minor axis is 3 km. + +The orientation of major axis is 0 degrees. The uncertainty of the altitude information is 500 m. The confidence factor is 68 %. + +For every Test Instance in each TTFF test case, the UE location shall be randomly selected to be within 3 km of the Reference Location. The Altitude of the UE shall be randomly selected between 0 m to 500 m above WGS-84 reference ellipsoid. These values shall have uniform random distributions. + +For test cases which include satellites from regional systems, such as QZSS and SBAS, the reference location shall be selected within the defined coverage area of the systems. + +### B.1.5 Satellite constellation and assistance data + +The satellite constellation shall consist of 24 satellites for GLONASS; 27 satellites for GPS, Modernized GPS and Galileo; 3 satellites for QZSS; 2 satellites for SBAS and 35 satellites for BDS (5 GEO, 27 MEO, 3 IGSO). Almanac assistance data shall be available for all these satellites. At least 7 of the satellites per GPS, Modernized GPS, Galileo, GLONASS and BDS constellation shall be visible to the UE (that is, above 15 degrees elevation with respect to the UE). At least 1 of the satellites for QZSS shall be within 15 degrees of zenith; and at least 1 of the satellites for SBAS shall be visible to the UE. For BDS with reference location in Asia, at least 1 of the visible satellites shall be a GEO (above 15 degrees elevation with respect to the UE). All other satellite specific assistance data shall be available for all visible satellites. In each test, signals are generated for only 6 satellites (or 7 if SBAS is included). The HDOP for the test shall be calculated using these satellites. The simulated satellites for GPS, Modernized GPS, Galileo, GLONASS and BDS shall be selected from the visible satellites for each constellation consistent with achieving the required HDOP for the test. For BDS with reference location in Asia, 1 of the simulated satellites shall be a GEO. + +NOTE: Currently up to 30 BDS satellites (maximum 22 MEO) can be supported. + +### B.1.6 Atmospheric delay + +Typical Ionospheric and Tropospheric delays shall be simulated and the corresponding values inserted into the Ionospheric Model IEs. + +### B.1.7 Sensors + +The minimum performance requirements shall be met without the use of any data coming from sensors that can aid the positioning. + +### B.1.8 Information elements + +The information elements that are available to the UE in all the test cases are listed in Annex E. + +### B.1.9 GNSS signals + +The GNSS signal is defined at the A-GNSS antenna connector of the UE. For UE with integral antenna only, a reference antenna with a gain of 0 dBi is assumed. + +### B.1.10 RESET UE POSITIONING STORED INFORMATION Message + +In order to ensure each Test Instance in each TTFF test is performed under Time to First Fix (TTFF) conditions, a dedicated test signal (*RESET UE POSITIONING STORED INFORMATION*) defined in TS 34.109 [13] clause 5.4 shall be used. + +When the UE receives the '*RESET UE POSITIONING STORED INFORMATION*' signal, with the IE *UE POSITIONING TECHNOLOGY* set to *AGNSS* it shall: + +- discard any internally stored GPS and GANSS reference time, reference location, and any other aiding data obtained or derived during the previous test instance (e.g. expected ranges and Doppler); +- accept or request a new set of reference time or reference location or other required information, as in a TTFF condition; + +- calculate the position or perform GNSS measurements using the 'new' reference time or reference location or other information. + +### B.1.11 GNSS system time offsets + +If more than one GNSS is used in a test, the accuracy of the GNSS-GNSS Time Offsets used at the system simulator shall be better than 3 ns. + +# Annex C (normative): Propagation conditions + +## C.1 Static propagation conditions + +The propagation for the static performance measurement is an Additive White Gaussian Noise (AWGN) environment. No fading and multi-paths exist for this propagation model. + +## C.2 Multi-path case + +Doppler frequency difference between direct and reflected signal paths is applied to the carrier and code frequencies. The Carrier and Code Doppler frequencies of LOS and multi-path for GANSS signals are defined in table C.2-1. + +**Table C.2-1: Multipath case** + +| Initial Relative Delay [m] | Carrier Doppler frequency of tap [Hz] | Code Doppler frequency of tap [Hz] | Relative mean Power [dB] | +|--------------------------------------------------------|---------------------------------------|------------------------------------|--------------------------| +| 0 | $F_d$ | $F_d / N$ | 0 | +| X | $F_d - 0.1$ | $(F_d - 0.1) / N$ | Y | +| Note: Discrete Doppler frequency is used for each tap. | | | | + +Where the X and Y depends on the GNSS signal type and is shown in table C.2-2, and N is the ratio between the transmitted carrier frequency of the signals and the transmitted chip rate as shown in table C.2-3 (where k in table C.2-3 is the GLONASS frequency channel number). + +**Table C.2-2: Relative Delay and Attenuation of Non Line of Sight Signals** + +| System | Signals | X [m] | Y [dB] | +|--------------------|---------|-------|--------| +| Galileo | E1 | 125 | -4.5 | +| | E5a | 15 | -6 | +| | E5b | 15 | -6 | +| GPS/Modernized GPS | L1 C/A | 150 | -6 | +| | L1C | 125 | -4.5 | +| | L2C | 150 | -6 | +| | L5 | 15 | -6 | +| GLONASS | G1 | 275 | -12.5 | +| | G2 | 275 | -12.5 | +| BDS | B1I | 75 | -4.5 | + +**Table C.2-3: Ratio between the transmitted carrier frequency of the signals and the transmitted chip rate** + +| System | Signals | N | +|--------------------|---------|--------------------------| +| Galileo | E1 | 1540 | +| | E5a | 115 | +| | E5b | 118 | +| GPS/Modernized GPS | L1 C/A | 1540 | +| | L1C | 1540 | +| | L2C | 1200 | +| | L5 | 115 | +| GLONASS | G1 | $3135.03 + k \cdot 1.10$ | +| | G2 | $2438.36 + k \cdot 0.86$ | +| BDS | B1I | 763 | + +The initial carrier phase difference between taps shall be randomly selected between 0 and $2\pi$ . The initial value shall have uniform random distribution. + +# Annex D (normative): Measurement sequence chart + +## D.1 General + +The measurement Sequence Charts that are required in all the test cases, are defined in this clause. + +## D.2 TTFF measurement sequence chart + +The measurement sequence chart for the TTFF test cases, for both UE-assisted and UE-based GANSS, is defined in this subclause. + +![Sequence diagram showing the interaction between a System Simulator (SS) and a User Equipment (UE) for TTFF measurement. The sequence consists of six steps: (a) SS sends 'Reset UE Positioning Stored Information' to UE; (b) SS sends 'RRC Measurement Control (Setup)' to UE; (c) UE sends 'RRC Measurement Report (Assistance Data Request)' to SS; (d) SS sends 'RRC Measurement Control (Modify)' to UE; (e) SS sends 'RRC Measurement Control (Modify)' to UE (indicated by a dashed line); (f) UE sends 'RRC Measurement Report' to SS.](b2ea162a0f53d5e0504b7d28346e0754_img.jpg) + +``` + +sequenceDiagram + participant SS + participant UE + Note left of SS: (a) + SS->>UE: Reset UE Positioning Stored Information + Note left of SS: (b) + SS->>UE: RRC Measurement Control (Setup) + Note left of UE: (c) + UE->>SS: RRC Measurement Report (Assistance Data Request) + Note left of SS: (d) + SS->>UE: RRC Measurement Control (Modify) + Note left of SS: (e) + SS-->>UE: RRC Measurement Control (Modify) + Note left of UE: (f) + UE->>SS: RRC Measurement Report + +``` + +Sequence diagram showing the interaction between a System Simulator (SS) and a User Equipment (UE) for TTFF measurement. The sequence consists of six steps: (a) SS sends 'Reset UE Positioning Stored Information' to UE; (b) SS sends 'RRC Measurement Control (Setup)' to UE; (c) UE sends 'RRC Measurement Report (Assistance Data Request)' to SS; (d) SS sends 'RRC Measurement Control (Modify)' to UE; (e) SS sends 'RRC Measurement Control (Modify)' to UE (indicated by a dashed line); (f) UE sends 'RRC Measurement Report' to SS. + +**Figure D.2-1: Measurement Sequence Chart for the TTFF Test Cases** + +- (a) The system simulator sends a RESET UE POSITIONING STORED INFORMATION message with the IE *UE POSITIONING TECHNOLOGY* set to *AGNSS*. +- (b) The system simulator sends a RRC MEASUREMENT CONTROL message without assistance data including the following information elements: + +| | | +|------------------------------------------|------------------------------------------------------------------------| +| MEASUREMENT COMMAND | Setup | +| CHOICE MEASUREMENT TYPE | UE positioning measurement | +| UE POSITIONING REPORTING QUANTITY | | +| >Method Type | set to either 'UE assisted' or 'UE based', dependent on the test case; | +| >Positioning Methods | set to 'GPS'; | +| >Horizontal Accuracy | as defined in Annex B; | +| >Vertical Accuracy | as defined in Annex B; | +| >Additional Assistance Data Request | TRUE | +| >GANSS Positioning Methods | set according to the UE capabilities and test case; | +| MEASUREMENT VALIDITY | | +| >UE state | All states | +| CHOICE REPORTING CRITERIA | Periodical reporting criteria | +| >Amount of reporting | 1 (see Annex B); | +| >Reporting interval | 20 seconds (see Annex B); | + +- (c) The UE responds with a RRC MEASUREMENT REPORT message including the *UE POSITIONING ERROR* IE with 'Error Reason' set to 'Assistance data missing', and including a request for additional GPS and/or GANSS assistance data. +- (d) – (e) The system simulator provides the requested assistance data that are available as defined in Annex E in one or more RRC MEASUREMENT CONTROL messages with MEASUREMENT COMMAND IE set to 'modify' and the CHOICE REPORTING CRITERIA set to 'no reporting' in all but the last RRC MEASUREMENT CONTROL message. The last RRC MEASUREMENT CONTROL message which is required to deliver the entire set of requested assistance data in step (c) includes the CHOICE REPORTING CRITERIA set to 'Periodical reporting criteria' as defined in step (b). +- (f) The UE sends a RRC MEASUREMENT REPORT message including the IE *UE POSITIONING MEASURED RESULTS* with *UE POSITIONING POSITION ESTIMATE INFO* present in case of UE-based, or *UE POSITIONING GPS MEASURED RESULTS* and/or *UE POSITIONING GANSS MEASURED RESULTS* present in case of UE-assisted GANSS. + +Steps (a) to (f) are repeated for each test instance. + +## D.3 Periodic update measurement sequence chart + +The measurement sequence chart for the Moving Scenario and Periodic Update test case, for both UE-assisted and UE-based GANSS, is defined in this subclause. + +![Sequence diagram showing the interaction between System Simulator (SS) and User Equipment (UE) for periodic update measurement. The sequence starts with (a) SS to UE: Reset UE Positioning Stored Information. (b) SS to UE: RRC Measurement Control (Setup). (c) UE to SS: RRC Measurement Report (Assistance Data Request). (d) SS to UE: RRC Measurement Control (Modify). (e) SS to UE: RRC Measurement Control (Modify) - dashed line. (f) UE to SS: RRC Measurement Report. (g) UE to SS: RRC Measurement Report. (h) UE to SS: RRC Measurement Report. (i) UE to SS: RRC Measurement Report. Vertical ellipsis between (h) and (i) indicates repeated steps.](86b4670fc1a5a694821ee92b99c1209a_img.jpg) + +``` + +sequenceDiagram + participant SS + participant UE + Note left of SS: (a) + SS->>UE: Reset UE Positioning Stored Information + Note left of SS: (b) + SS->>UE: RRC Measurement Control (Setup) + Note left of UE: (c) + UE->>SS: RRC Measurement Report (Assistance Data Request) + Note left of SS: (d) + SS->>UE: RRC Measurement Control (Modify) + Note left of SS: (e) + SS-->>UE: RRC Measurement Control (Modify) + Note left of UE: (f) + UE->>SS: RRC Measurement Report + Note left of UE: (g) + UE->>SS: RRC Measurement Report + Note left of UE: (h) + UE->>SS: RRC Measurement Report + Note right of SS: ... + Note left of UE: (i) + UE->>SS: RRC Measurement Report + +``` + +Sequence diagram showing the interaction between System Simulator (SS) and User Equipment (UE) for periodic update measurement. The sequence starts with (a) SS to UE: Reset UE Positioning Stored Information. (b) SS to UE: RRC Measurement Control (Setup). (c) UE to SS: RRC Measurement Report (Assistance Data Request). (d) SS to UE: RRC Measurement Control (Modify). (e) SS to UE: RRC Measurement Control (Modify) - dashed line. (f) UE to SS: RRC Measurement Report. (g) UE to SS: RRC Measurement Report. (h) UE to SS: RRC Measurement Report. (i) UE to SS: RRC Measurement Report. Vertical ellipsis between (h) and (i) indicates repeated steps. + +Figure D.3-1: Measurement Sequence Chart for the Moving Scenario and Periodic Update Test Case + +- (a) The system simulator sends a RESET *UE POSITIONING STORED INFORMATION* message with the IE *UE POSITIONING TECHNOLOGY* set to *AGNSS*. +- (b) The system simulator sends a RRC MEASUREMENT CONTROL message without assistance data including the following information elements: + +| | | +|--------------------------------|----------------------------| +| MEASUREMENT COMMAND | Setup | +| CHOICE MEASUREMENT TYPE | UE positioning measurement | + +# UE POSITIONING REPORTING QUANTITY + +| | | +|-------------------------------------|------------------------------------------------------------------------| +| >Method Type | set to either 'UE assisted' or 'UE based', dependent on the test case; | +| >Positioning Methods | set to 'GPS'; | +| >Horizontal Accuracy | as defined in Annex B; | +| >Vertical Accuracy | as defined in Annex B; | +| >Additional Assistance Data Request | TRUE | +| >GNSS Positioning Methods | set according to the UE capabilities and test case; | +| MEASUREMENT VALIDITY | | +| >UE state | All states | +| CHOICE REPORTING CRITERIA | Periodical reporting criteria | +| >Amount of reporting | infinite (see Annex B); | +| >Reporting interval | 2 seconds (see Annex B); | + +- (c) The UE responds with a RRC MEASUREMENT REPORT message including the *UE POSITIONING ERROR* IE with 'Error Reason' set to 'Assistance data missing', and including a request for additional GPS and/or GNSS assistance data. +- (d) – (e) The system simulator provides the requested assistance data that are available as defined in Annex E in one or more RRC MEASUREMENT CONTROL messages with MEASUREMENT COMMAND IE set to 'modify' and the CHOICE REPORTING CRITERIA set to 'no reporting' in all but the last RRC MEASUREMENT CONTROL message. The last RRC MEASUREMENT CONTROL message which is required to deliver the entire set of requested assistance data in step (c) includes the CHOICE REPORTING CRITERIA set to 'Periodical reporting criteria' as defined in step (b). +- (f) The UE sends a RRC MEASUREMENT REPORT message including the IE *UE POSITIONING MEASURED RESULTS* with *UE POSITIONING POSITION ESTIMATE INFO* present in case of UE-based, or *UE POSITIONING GPS MEASURED RESULTS* and/or *UE POSITIONING GNSS MEASURED RESULTS* present in case of UE-assisted GNSS. +- (g) – (i) The UE continues to provide RRC MEASUREMENT REPORT messages as in step (g) until the moving trajectory has been completed. + +NOTE: The UE may report error messages at step (f) until it has been able to acquire GNSS signals. + +# Annex E (normative): Assistance data required for testing + +## E.1 Introduction + +This annex defines the assistance data IEs available at the SS in all test cases. The assistance data shall be given for satellites as defined in B.1.5. + +The information elements are given with reference to 3GPP TS 25.331 [14], where the details are defined. + +## E.2 GPS assistance data + +The GPS L1 C/A assistance data are as defined in 3GPP TS 25.171 [10], Annex E. + +## E.3 GANSS assistance data + +- a) **UE Positioning GANSS Reference Time IE.** This information element is defined in subclause 10.3.7.96o of 3GPP TS 25.331 [14]. + +**Table E.3-1: GANSS reference time IE** + +| Name of the IE | Fields of the IE | All tests except Sensitivity Fine Time Assistance | Sensitivity Fine Time Assistance test | +|-------------------------------------|------------------------------------|---------------------------------------------------|---------------------------------------| +| UE Positioning GANSS Reference Time | | | | +| | GANSS Day | Yes | Yes | +| | GANSS TOD | Yes | Yes | +| | GANSS TOD Uncertainty | Yes | Yes | +| | GANSS Time ID | Yes | Yes | +| | UTRAN GANSS Reference Time | | | +| | >UTRAN GANSS Timing of Cell Frames | | Yes | +| | >CHOICE mode | | Yes | +| | >>FDD | | Yes | +| | >>>Primary CPICH Info | | Yes | +| | >SFN | | Yes | +| | TUTRAN-GANSS Drift Rate | | Yes | + +- b) **UE Positioning GANSS Reference UE Position IE.** This information element is defined in subclause 10.3.8.4c of 3GPP TS 25.331 [14]. + +**Table E.3-2: GANSS reference location IE** + +| Name of the IE | Fields of the IE | +|--------------------------------------------|---------------------------------------------------------| +| UE Positioning GANSS Reference UE Position | Ellipsoid point with Altitude and uncertainty ellipsoid | + +- c) **UE Positioning GANSS Ionospheric Model IE.** This information element is defined in subclause 10.3.7.92a of 3GPP TS 25.331 [14]. + +**Table E.3-3: GANSS ionospheric model IE** + +| Name of the IE | Fields of the IE | +|----------------------------------------|------------------| +| UE Positioning GANSS Ionospheric Model | | + +- d) **UE Positioning GANSS Additional Ionospheric Model IE.** This information element is defined in subclause 10.3.7.92b of 3GPP TS 25.331 [14]. + +**Table E.3-4: GANSS additional ionospheric model IE** + +| Name of the IE | Fields of the IE | +|------------------------------------------------------|------------------| +| UE Positioning GANSS
Additional Ionospheric Model | | + +- e) **UE Positioning GANSS Time Model IE.** This information element is only required for multi system tests, and is defined in subclause 10.3.7.97a of 3GPP TS 25.331 [14]. + +**Table E.3-5: GANSS time model IE** + +| Name of the IE | Fields of the IE | +|------------------------------------|----------------------------------------------------| +| UE Positioning GANSS Time
Model | | +| | GNSS TOD_ID
For each GNSS included in the test. | + +- f) **UE Positioning GANSS Navigation Model IE.** This information element is defined in subclause 10.3.7.94a of 3GPP TS 25.331 [14]. + +**Table E.3-6: GANSS navigation model IE** + +| Name of the IE | Fields of the IE | +|------------------------------------------|------------------| +| UE Positioning GANSS
Navigation Model | | + +- g) **UE Positioning GANSS Additional Navigation Models IE.** This information element is defined in subclause 10.3.7.94b of 3GPP TS 25.331 [14]. + +**Table E.3-7: GANSS navigation model IE** + +| Name of the IE | Fields of the IE | +|------------------------------------------|------------------| +| UE Positioning GANSS
Navigation Model | | + +**Table E.3-8: GANSS clock and orbit model choices** + +| GANSS | Clock and Orbit Model Choice | +|---------------------|------------------------------| +| Galileo | Model-1 | +| Modernized GPS | Model-3 | +| GLONASS | Model-4 | +| QZSS QZS-L1 | Model-2 | +| QZSS QZS-L1C/L2C/L5 | Model-3 | +| SBAS | Model-5 | +| BDS | Model-6 | + +- h) **UE Positioning GANSS Reference Measurement Information IE.** This information element is defined in subclause 10.3.7.88b of 3GPP TS 25.331 [14]. + +**Table E.3-9: GANSS reference measurement information IE** + +| Name of the IE | Fields of the IE | +|--------------------------------------------------------|--------------------------------------| +| UE Positioning GANSS Reference Measurement Information | | +| | SatID | +| | Doppler (0 th order term) | +| | Doppler (1 st order term) | +| | Doppler Uncertainty | +| | Code Phase | +| | Integer Code Phase | +| | Code Phase Search Window | +| | Azimuth | +| | Elevation | + +- i) **UE Positioning GANSS Almanac IE.** This information element is defined in subclause 10.3.7.89a of 3GPP TS 25.331 [14]. + +**Table E.3-10: GANSS almanac model IE** + +| Name of the IE | Fields of the IE | +|------------------------------|------------------| +| UE Positioning GANSS Almanac | | + +**Table E.3-11: GANSS almanac choices** + +| GANSS | Almanac Model Choice | +|---------------------|----------------------| +| Galileo | Model-1 | +| Modernized GPS | Model-3,4 | +| GLONASS | Model-5 | +| QZSS QZS-L1 | Model-2 | +| QZSS QZS-L1C/L2C/L5 | Model-3,4 | +| SBAS | Model-6 | +| BDS | Model-7 | + +- j) **UE Positioning GANSS UTC Model IE.** This information element is defined in subclause 10.3.7.97c of 3GPP TS 25.331 [14]. + +**Table E.3-12: GANSS UTC model IE** + +| Name of the IE | Fields of the IE | +|--------------------------------|------------------| +| UE Positioning GANSS UTC Model | | + +- k) **UE Positioning GANSS Additional UTC Models IE.** This information element is defined in subclause 10.3.7.97d of 3GPP TS 25.331 [14]. + +**Table E.3-13: GANSS additional UTC model IE** + +| Name of the IE | Fields of the IE | +|-----------------------------------------------|------------------| +| UE Positioning GANSS Additional UTC Models IE | | + +**Table E.3-14: GANSS UTC model choices** + +| GANSS | UTC Model Choice | +|---------------------|--------------------------------| +| Galileo | UE Positioning GANSS UTC Model | +| Modernized GPS | Model-1 | +| GLONASS | Model-2 | +| QZSS QZS-L1 | UE Positioning GANSS UTC Model | +| QZSS QZS-L1C/L2C/L5 | Model-1 | +| SBAS | Model-3 | +| BDS | Model-4 | + +- I) **UE Positioning GANSS Auxiliary Information IE.** This information element is defined in subclause 10.3.7.97f of 3GPP TS 25.331 [14]. + +**Table E.3-15: GANSS auxiliary information IE** + +| Name of the IE | Fields of the IE | +|-----------------------------------------------|-------------------------| +| UE Positioning GANSS Auxiliary Information IE | | + +# --- Annex F (normative):Converting UE-assisted measurement reports into position estimates + +## F.1 Introduction + +To convert the UE measurement reports in case of UE-assisted mode of A-GANSS into position errors, a transformation between the "measurement domain" (code-phases, etc.) into the "state" domain (position estimate) is necessary. Such a transformation procedure is outlined in the following clauses. The details can be found in [3], [4], [5], [6], [7], [8], [9], [16] and [17]. + +## --- F.2 UE measurement reports + +In case of UE-assisted A-GANSS, the measurement parameters are contained in the RRC UE POSITIONING GANSS MEASURED RESULTS IE (subclause 10.3.7.93a in 3GPP TS 25.331 [14]). In case the UE provides also measurements on the GPS L1 C/A signal, the measurement parameters are contained in the RRC UE POSITIONING GPS MEASURED RESULTS IE (subclause 10.3.7.93 in 3GPP TS 25.331 [14]). The measurement parameters required for calculating the UE position are: + +- 1) Reference Time: The UE has two choices for the Reference Time: + - a) "UE GANSS Timing of Cell Frames" and/or "UE GPS Timing of Cell Frames"; + - b) "GANSS TOD msec" and/or "GPS TOW msec" if GPS L1 C/A signal measurements are also provided. + +NOTE: It is not expected that an UE will ever report both a GANSS TOD and a GPS TOW. However if two time stamps are provided and they derive from different user times, be aware that no compensation is made for this difference and this could affect the location accuracy. + +- 2) Measurement Parameters for each GANSS and GANSS Signal: 1 to : + - a) "Satellite ID"; mapping according to table 10.3.7.88b in 3GPP TS 25.331 [14]; + - b) "GANSS Code Phase"; + - c) "GANSS Integer Code Phase"; + - d) "GANSS Integer Code Phase Extension"; + - e) "Code Phase RMS Error"; +- 3) Additional Measurement Parameters in case of GPS L1 C/A signal measurements are also provided: 1 to : + - a) "Satellite ID (SV PRN)"; + - b) "Whole GPS chips"; + - c) "Fractional GPS Chips"; + - d) "Pseudorange RMS Error". + +Additional information required at the system simulator: + +- 1) "UE Positioning GANSS Reference UE Position" or "UE Positioning GPS Reference UE Position" (subclause 10.3.8.4c in 3GPP TS 25.331 [14]): +Used for initial approximate receiver coordinates. +- 2) "UE Positioning GANSS Navigation Model" and "UE Positioning GANSS Additional Navigation Models" (subclauses 10.3.7.94a and 10.3.7.94b in 3GPP TS 25.331 [14]): + +Contains the ephemeris and clock correction parameters as specified in the relevant ICD of each supported GANSS; used for calculating the satellite positions and clock corrections. + +- 3) "UE Positioning GANSS Ionospheric Model" (subclause 10.3.7.92a in 3GPP TS 25.331 [14]): +Contains the ionospheric parameters which allow the single frequency user to utilize the ionospheric model as specified in [7] for computation of the ionospheric delay. +- 4) "UE Positioning GANSS Additional Ionospheric Model" (subclause 10.3.7.92b in 3GPP TS 25.331 [14]): +Contains the ionospheric parameters which allow the single frequency user to utilize the ionospheric model as specified in [6] for computation of the ionospheric delay. +- 5) "UE Positioning GANSS Time Model" (subclause 10.3.7.97a in 3GPP TS 25.331 [14]): +Contains the GNSS-GNSS Time Offset for each supported GANSS. Note, that "UE Positioning GANSS Time Model" IE contains only the sub-ms part of the offset. Any potential integer seconds offset may be obtained from "UE Positioning GPS UTC Model" (subclause 10.3.7.97 in 3GPP TS 25.331 [14]), "UE Positioning GANSS UTC Model" (subclause 10.3.7.97c in 3GPP TS 25.331 [14]), or "UE Positioning GANSS Additional UTC Models" (subclause 10.3.7.97d in 3GPP TS 25.331 [14]). +- 6) "UE Positioning GPS Navigation Model" (subclause 10.3.7.94 in 3GPP TS 25.331 [14]): +Contains the GPS ephemeris and clock correction parameters as specified in [3]; used for calculating the GPS satellite positions and clock corrections in case of GPS L1 C/A signal measurements are the only GPS measurements provided in addition to GANSS measurements. +- 7) "UE Positioning GPS Ionospheric Model" (subclause 10.3.7.92 in 3GPP TS 25.331 [14]): +Contains the ionospheric parameters which allow the single frequency user to utilize the ionospheric model as specified in [3] for computation of the ionospheric delay. + +## F.3 Weighted Least Squares (WLS) position solution + +The WLS position solution problem is concerned with the task of solving for four unknowns; $x_u, y_u, z_u$ the receiver coordinates in a suitable frame of reference (usually ECEF) and $b_u$ the receiver clock bias relative to the selected GNSS specific system time. It typically requires the following steps: + +### Step 1: Formation of pseudo-ranges + +The observation of code phase reported by the UE for each satellite $SV_i$ is related to the pseudo-range/ $c$ modulo the "GANSS Code Phase Ambiguity", or modulo 1 ms (the length of the C/A code period) in case of GPS L1 C/A signal measurements. For the formation of pseudo-ranges, the integer number of milliseconds to be added to each code-phase measurement has to be determined first. Since 1 ms corresponds to a travelled distance of 300 km, the number of integer ms can be found with the help of reference location and satellite ephemeris. The distance between the reference location and each satellite $SV_i$ at the time of measurement is calculated, and the integer number of milliseconds to be added to the UE code phase measurements is obtained. + +### Step 2: Correction of pseudo-ranges for the GNSS-GNSS time offsets + +In case the UE reports measurements for more than a single GNSS, the pseudo-ranges are corrected for the time offsets between the GNSSs relative to the selected reference time using the GNSS-GNSS time offsets available at the system simulator: + +$$\rho_{GNSS_{m,i}} \equiv \rho_{GNSS_{m,i}} - c \cdot (t_{GNSS_k} - t_{GNSS_m}),$$ + +where $\rho_{GNSS_{m,i}}$ is the measured pseudo-range of satellite $i$ of GNSS $_m$ . The system time $t_{GNSS_k}$ of GNSS $_k$ is the reference time frame, and $(t_{GNSS_k} - t_{GNSS_m})$ is the available GNSS-GNSS time offset, and $c$ is the speed of light. + +### Step 3: Formation of weighting matrix + +The UE reported "Code Phase RMS Error" and/or "Pseudorange RMS Error" values are used to calculate the weighting matrix for the WLS algorithm described in [16]. According to 3GPP TS 25.331 [14], the encoding for these fields is a 6 bit value that consists of a 3 bit mantissa, $X_i$ and a 3 bit exponent, $Y_i$ for each $SV_i$ of GNSS $_j$ : + +$$w_{GNSS_{j,i}} = RMSError = 0.5 \times \left(1 + \frac{X_i}{8}\right) 2^{Y_i}$$ + +The weighting Matrix **W** is defined as a diagonal matrix containing the estimated variances calculated from the "Code Phase RMS Error" and/or "Pseudorange RMS Error" values: + +$$W = \text{diag}\{1/w_{\text{GNSS}_{1,1}}^2, 1/w_{\text{GNSS}_{1,2}}^2, \dots, 1/w_{\text{GNSS}_{1,n}}^2, \dots, 1/w_{\text{GNSS}_{m,1}}^2, 1/w_{\text{GNSS}_{m,2}}^2, \dots, 1/w_{\text{GNSS}_{m,l}}^2\}$$ + +### Step 4: WLS position solution + +The WLS position solution is described in e.g., [16] and usually requires the following steps: + +- 1) Computation of satellite locations at time of transmission using the ephemeris parameters and user algorithms defined in the relevant ICD of the particular GNSS. The satellite locations are transformed into WGS-84 reference frame, if needed. +- 2) Computation of clock correction parameters using the parameters and algorithms as defined in the relevant ICD of the particular GNSS. +- 3) Computation of atmospheric delay corrections using the parameters and algorithms defined in the relevant ICD of the particular GNSS for the ionospheric delay, and using the Gupta model defined in [17] p. 121 equation (2) for the tropospheric delay. For GNSSs which do not natively provide ionospheric correction models (e.g., GLONASS), the ionospheric delay is determined using the available ionospheric model (see subclause F.2) adapted to the particular GNSS frequency. +- 4) The WLS position solution starts with an initial estimate of the user state (position and clock offset). The Reference Location is used as initial position estimate. The following steps are required: + - a) Calculate geometric range (corrected for Earth rotation) between initial location estimate and each satellite included in the UE measurement report. + - b) Predict pseudo-ranges for each measurement including clock and atmospheric biases as calculated in 1) to 3) above and defined in the relevant ICD of the particular GNSS and [16]. + - c) Calculate difference between predicted and measured pseudo-ranges $\Delta\rho$ . + - d) Calculate the "Geometry Matrix" **G** as defined in [16]: + +$$G \equiv \begin{bmatrix} -\hat{\mathbf{i}}_{\text{GNSS}_{1,1}}^T & 1 \\ -\hat{\mathbf{i}}_{\text{GNSS}_{1,2}}^T & 1 \\ \vdots & \vdots \\ -\hat{\mathbf{i}}_{\text{GNSS}_{1,n}}^T & 1 \\ \vdots & \vdots \\ -\hat{\mathbf{i}}_{\text{GNSS}_{m,1}}^T & 1 \\ -\hat{\mathbf{i}}_{\text{GNSS}_{m,2}}^T & 1 \\ \vdots & \vdots \\ -\hat{\mathbf{i}}_{\text{GNSS}_{m,l}}^T & 1 \end{bmatrix} \text{ with } \hat{\mathbf{i}}_{\text{GNSS}_{m,i}} \equiv \frac{\mathbf{r}_{\text{sGNSS}_{m,i}} - \hat{\mathbf{r}}_u}{|\mathbf{r}_{\text{sGNSS}_{m,i}} - \hat{\mathbf{r}}_u|} \text{ where } \mathbf{r}_{\text{sGNSS}_{m,i}} \text{ is the satellite position vector for SV}_i \text{ of GNSS}_m \text{ (calculated in 1) above), and } \hat{\mathbf{r}}_u \text{ is the estimate of the user location.}$$ + +- e) Calculate the WLS solution according to [16]: + +$$\Delta\hat{\mathbf{x}} = (G^T W G)^{-1} G^T W \Delta\rho$$ + +- f) Adding the $\Delta\hat{\mathbf{x}}$ to the initial state estimate gives an improved estimate of the state vector: + +$$\hat{\mathbf{x}} \rightarrow \hat{\mathbf{x}} + \Delta\hat{\mathbf{x}}.$$ + +- 5) This new state vector $\hat{\mathbf{x}}$ can be used as new initial estimate and the procedure is repeated until the change in $\hat{\mathbf{x}}$ is sufficiently small. + +### Step 5: Transformation from Cartesian coordinate system to Geodetic coordinate system + +The state vector $\hat{\mathbf{x}}$ calculated in Step 4 contains the UE position in ECEF Cartesian coordinates together with the UE receiver clock bias relative to the selected GNSS system time. Only the user position is of further interest. It is usually desirable to convert from ECEF coordinates $x_u, y_u, z_u$ to geodetic latitude $\phi$ , longitude $\lambda$ and altitude $h$ on the WGS84 reference ellipsoid. + +### **Step 6: Calculation of "2-D Position Errors"** + +The latitude $\varphi$ / longitude $\lambda$ obtained after Step 5 is used to calculate the 2-D position error. + +# Annex G (informative): Change history + +| Date | Meeting | Document | CR num | Rev | Comment | Version old | Version New | +|---------|---------|-----------|--------|-----|-------------------------------------------------------------------------------------------------|-------------|-------------| +| 2010-02 | RAN4#54 | R4-100668 | | | Text proposal for A-GANSS minimum performance requirements in UTRAN | | 0.0.1 | +| 2010-03 | RAN#47 | RP-100133 | | | TS presented for information | 0.0.1 | 1.0.0 | +| 2010-05 | RAN4#55 | R4-101671 | | | Minor editorial corrections and alignments with GERAN | 1.0.0 | 2.0.0 | +| 2010-05 | RAN4#55 | R4-101671 | | | Approved by TSG RAN | 2.0.0 | 10.0.0 | +| 2010-12 | RP-50 | RP-101350 | 001 | 1 | Addition of Galileo sensitivity numbers in the A-GANSS minimum performance requirements in UMTS | 10.0.0 | 10.1.0 | +| 2011-04 | RP-51 | RP-110351 | 002 | | Addition of missing values and references | 10.1.0 | 10.2.0 | +| 2012-09 | SP-57 | - | - | - | Update to Rel-11 version (MCC) | 10.2.0 | 11.0.0 | +| 2014-06 | RP-64 | RP-140924 | 004 | 2 | CR to TS 25.172 on introduction BDS to A-GANSS of FDD mode of UTRA | 11.0.0 | 12.0.0 | +| 2014-12 | RP-66 | RP-142151 | 005 | - | Correction on BDS satellites number | 12.0.0 | 12.1.0 | +| 2016-01 | SP-70 | - | - | - | Update to Rel-13 version (MCC) | 12.1.0 | 13.0.0 | +| 2017-03 | RP-75 | - | - | - | Update to Rel-14 version (MCC) | 13.0.0 | 14.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2018-06 | SA#80 | - | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-06 | SA#88 | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25173/3f1987804d7d78bc3b3bc560e974280a_img.jpg b/marked/Rel-16/25_series/25173/3f1987804d7d78bc3b3bc560e974280a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01b443dd57d0f41faa756a69374dc16d08259308 --- /dev/null +++ b/marked/Rel-16/25_series/25173/3f1987804d7d78bc3b3bc560e974280a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7dbb20a66a539b9df9363974f246d18ec2119828965d45c243fd63046b10c889 +size 26478 diff --git a/marked/Rel-16/25_series/25173/86b4670fc1a5a694821ee92b99c1209a_img.jpg b/marked/Rel-16/25_series/25173/86b4670fc1a5a694821ee92b99c1209a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0057b46f91689454121127bc3a3a530d657f39f1 --- /dev/null +++ b/marked/Rel-16/25_series/25173/86b4670fc1a5a694821ee92b99c1209a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e0475dc62c838136ff54d1cfbf653f2e2f43dc1b046e0fca819c19c231578a8 +size 81459 diff --git a/marked/Rel-16/25_series/25173/b2ea162a0f53d5e0504b7d28346e0754_img.jpg b/marked/Rel-16/25_series/25173/b2ea162a0f53d5e0504b7d28346e0754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..197bf511992aa8d6d6ff6cf67484472628b42974 --- /dev/null +++ b/marked/Rel-16/25_series/25173/b2ea162a0f53d5e0504b7d28346e0754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a4ccd334b69467dce533e98fc8c4e7a9781b9324a2c2ce87f445076e8edc0a3 +size 56184 diff --git a/marked/Rel-16/25_series/25173/raw.md b/marked/Rel-16/25_series/25173/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ec567f447a59a9bcdefc8135c18e33a549fc3a51 --- /dev/null +++ b/marked/Rel-16/25_series/25173/raw.md @@ -0,0 +1,1135 @@ + + + + + + +# Contents + +| | | +|-----------------------------------------------------------------------|-----------| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols, abbreviations and test tolerances ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 8 | +| 3.4 Test tolerances..... | 8 | +| 4 General..... | 8 | +| 4.1 Introduction ..... | 8 | +| 4.2 Measurement parameters..... | 9 | +| 4.2.1 UE-based A-GANSS measurement parameters ..... | 9 | +| 4.2.2 UE-assisted A-GANSS measurement parameters ..... | 9 | +| 4.3 Response time ..... | 9 | +| 4.4 Time assistance ..... | 9 | +| 4.4.1 Use of fine time assistance ..... | 9 | +| 4.5 RRC states..... | 10 | +| 4.6 2D position error ..... | 10 | +| 4.7 User equipment supporting multiple constellations ..... | 10 | +| 4.8 User equipment supporting multiple signals..... | 10 | +| 5 A-GANSS minimum performance requirements..... | 11 | +| 5.1 Sensitivity..... | 11 | +| 5.1.1 Coarse time assistance..... | 11 | +| 5.1.1.1 Minimum requirements (coarse time assistance)..... | 11 | +| 5.1.2 Fine time assistance..... | 12 | +| 5.1.2.1 Minimum requirements (fine time assistance)..... | 12 | +| 5.2 Nominal accuracy..... | 12 | +| 5.2.1 Minimum requirements (nominal accuracy) ..... | 13 | +| 5.3 Dynamic range ..... | 13 | +| 5.3.1 Minimum requirements (dynamic range)..... | 14 | +| 5.4 Multi-path scenario ..... | 14 | +| 5.4.1 Minimum requirements (multi-path scenario)..... | 15 | +| 5.5 Moving scenario and periodic update ..... | 15 | +| 5.5.1 Minimum requirements (moving scenario and periodic update)..... | 16 | +| Annex A (normative): Test cases..... | 18 | +| A.1 Conformance tests..... | 18 | +| A.2 Requirement classification for statistical testing ..... | 18 | +| Annex B (normative): Test conditions..... | 19 | +| B.1 General..... | 19 | +| B.1.1 Parameter values ..... | 19 | +| B.1.2 Time assistance ..... | 19 | +| B.1.3 GANSS reference time..... | 19 | +| B.1.4 Reference and UE locations ..... | 20 | +| B.1.5 Satellite constellation and assistance data..... | 20 | +| B.1.6 Atmospheric delay..... | 20 | +| B.1.7 Sensors ..... | 20 | +| B.1.8 Information elements..... | 20 | +| B.1.9 GNSS signals..... | 20 | +| B.1.10 RESET UE POSITIONING STORED INFORMATION Message ..... | 20 | +| B.1.11 GNSS system time offsets..... | 21 | + +| | | | +|-----------------------------|--------------------------------------------------------------------------------|-----------| +| Annex C (normative): | Propagation conditions ..... | 22 | +| C.1 | Static propagation conditions..... | 22 | +| C.2 | Multi-path case..... | 22 | +| Annex D (normative): | Measurement sequence chart..... | 24 | +| D.1 | General..... | 24 | +| D.2 | TTFF measurement sequence chart ..... | 24 | +| D.3 | Periodic update measurement sequence chart..... | 25 | +| Annex E (normative): | Assistance data required for testing ..... | 27 | +| E.1 | Introduction..... | 27 | +| E.2 | GPS assistance data..... | 27 | +| E.3 | GANSS assistance data..... | 27 | +| Annex F (normative): | Converting UE-assisted measurement reports into position estimates .... | 31 | +| F.1 | Introduction..... | 31 | +| F.2 | UE measurement reports..... | 31 | +| F.3 | Weighted Least Squares (WLS) position solution ..... | 32 | +| Annex G (informative): | Change history..... | 35 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd 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 establishes the minimum performance requirements for A-GNSS for TDD mode of UTRA for the User Equipment (UE) that supports A-GNSS. It includes the minimum performance requirements for both UE-based and UE-assisted A-GNSS. The minimum performance requirements also include combinations of A-GPS and A-GNSS. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TS 25.102: "User Equipment (UE) radio transmission and reception (TDD)". +- [2] 3GPP TS 25.105: "Base Station (BS) radio transmission and reception (TDD)". +- [3] IS-GPS-200, Revision D, "Navstar GPS Space Segment/Navigation User Interfaces", March 7th, 2006. +- [4] IS-GPS-705, "Navstar GPS Space Segment/User Segment L5 Interfaces", September 22, 2005. +- [5] IS-GPS-800, "Navstar GPS Space Segment/User Segment L1C Interfaces", September 4, 2008. +- [6] IS-QZSS, "Quasi Zenith Satellite System Navigation Service Interface Specifications for QZSS", Ver.1.1, July 31, 2009. +- [7] "Galileo OS Signal in Space ICD (OS SIS ICD)", Draft 0, Galileo Joint Undertaking, May 23rd, 2006. +- [8] "Global Navigation Satellite System GLONASS Interface Control Document", Version 5.1, 2008. +- [9] "Specification for the Wide Area Augmentation System (WAAS) ", US Department of Transportation, Federal Aviation Administration, DTFA01-96-C-00025, 2001. +- [10] 3GPP TS 25.171: "Requirements for support of Assisted Global Positioning System (A-GPS) Frequency Division Duplex (FDD)". +- [11] 3GPP TS 34.171: "Terminal Conformance Specification, Assisted Global Positioning System (A-GPS) (FDD)". +- [12] 3GPP TS 34.172: "Terminal Conformance Specification, Assisted Galileo and Additional Navigation Satellite Systems (A-GNSS) (FDD)". +- [13] 3GPP TS 34.109: "Special conformance testing functions". +- [14] 3GPP TS 25.331: "Radio Resource Control (RRC) protocol specification". +- [15] ETSI TR 102 273-1-2: "Electromagnetic compatibility and Radio spectrum Matters (ERM); Improvement on Radiated Methods of Measurement (using test site) and evaluation of the corresponding measurement uncertainties; Part 1: Uncertainties in the measurement of mobile radio equipment characteristics; Sub-part 2: Examples and annexes". +- [16] P. Axelrad, R.G. Brown, "GPS Navigation Algorithms", in Chapter 9 of "Global Positioning System: Theory and Applications", Volume 1, B.W. Parkinson, J.J. Spilker (Ed.), Am. Inst. of Aeronautics and Astronautics Inc., 1996. + +- [17] S.K. Gupta, "Test and Evaluation Procedures for the GPS User Equipment", ION-GPS Red Book, Volume 1, p. 119. +- [18] 3GPP TS 25.225: "Physical layer; Measurements (TDD)". +- [19] BeiDou Navigation Satellite System Signal In Space Interface Control Document Open Service Signal B1I(Version 1.0), China Satellite Navigation Office, December 2012. +- [20] 3GPP TS 37.571: "User Equipment (UE) conformance specification for UE positioning". + +# 3 Definitions, symbols, abbreviations and test tolerances + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TS 25.102 [1], 3GPP TS 25.105 [2] and the following apply: + +**Horizontal Dilution Of Precision (HDOP):** measure of position determination accuracy that is a function of the geometrical layout of the satellites used for the fix, relative to the receiver antenna. + +## 3.2 Symbols + +For the purposes of the present document, the following symbol applies: + +| | | +|-----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------| +| B1I | BeiDou B1I navigation signal with carrier frequency of 1561.098 MHz | +| c | Speed of light. | +| E1 | Galileo E1 navigation signal with carrier frequency of 1575.420 MHz. | +| E5 | Galileo E5 navigation signal with carrier frequency of 1191.795 MHz. | +| E6 | Galileo E6 navigation signal with carrier frequency of 1278.750 MHz. | +| G1 | GLONASS navigation signal in the L1 sub-bands with carrier frequencies $1602 \text{ MHz} \pm k \times 562.5 \text{ kHz}$ . | +| G2 | GLONASS navigation signal in the L2 sub-bands with carrier frequencies $1246 \text{ MHz} \pm k \times 437.5 \text{ kHz}$ . | +| k | GLONASS channel number, $k = -7 \dots 13$ . | +| L1 C/A | GPS or QZSS L1 navigation signal carrying the Coarse/Acquisition code with carrier frequency of 1575.420 MHz. | +| L1C | GPS or QZSS L1 Civil navigation signal with carrier frequency of 1575.420 MHz. | +| L2C | GPS or QZSS L2 Civil navigation signal with carrier frequency of 1227.600 MHz. | +| L5 | GPS or QZSS L5 navigation signal with carrier frequency of 1176.450 MHz. | +| G | Geometry Matrix. | +| $\rho_{\text{GNSS}_m, i}$ | Measured pseudo-range of satellite i of GNSS m . | +| W | Weighting Matrix. | +| 1 GNSSm,i | Line of sight unit vector from the user to the satellite i of GNSS m . | +| x | State vector of user position and clock bias. | + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|---------|--------------------------------------------------------------| +| A-GANSS | Assisted-Galileo and Additional Navigation Satellite Systems | +| A-GNSS | Assisted-GNSS | +| A-GPS | Assisted-Global Positioning System | +| AWGN | Additive White Gaussian Noise | +| BDS | BeiDou Navigation Satellite System | +| C/A | Coarse/Acquisition | + +| | | +|---------|----------------------------------------------------------------------------------------------| +| DUT | Device Under Test | +| ECEF | Earth-Centered, Earth-Fixed | +| ECI | Earth-Centered-Inertial | +| FDD | Frequency Division Duplex | +| GEO | Geostationary Earth Orbit | +| GLONASS | GLObal'naya NAVigatsionnaya Sputnikovaya Sistema (Engl.: Global Navigation Satellite System) | +| GNSS | Global Navigation Satellite System | +| GPS | Global Positioning System | +| GSS | GNSS System Simulator | +| HDOP | Horizontal Dilution Of Precision | +| ICD | Interface Control Document | +| IGSO | Inclined Geosynchronous Satellite Orbit/Interface Specification | +| LOS | Line Of Sight | +| MEO | Medium Earth Orbit | +| QZS | Quasi-Zenith Satellite | +| QZSS | Quasi-Zenith Satellite System | +| RF | Radio Frequency | +| RRC | Radio Resource Control | +| SBAS | Space Based Augmentation System | +| SFN | System Frame Number | +| SS | System Simulator | +| SV | Space Vehicle | +| TOD | Time Of Day | +| TOW | Time Of Week | +| TTFF | Time To First Fix | +| UE | User Equipment | +| UTRA | Universal Terrestrial Radio Access | +| UTRAN | Universal Terrestrial Radio Access Network | +| WLS | Weighted Least Squares | +| WGS-84 | World Geodetic System 1984 | + +## 3.4 Test tolerances + +The requirements given in the present document make no allowance for measurement uncertainty. The test specification 3GPP TS 34.172 [12] defines test tolerances. These test tolerances are individually calculated for each test. The test tolerances are then added to the limits in the present document to create test limits. The measurement results are compared against the test limits as defined by the shared risk principle. + +Shared Risk is defined in ETR 273-1-2 [15], subclause 6.5. + +# --- 4 General + +## 4.1 Introduction + +The present document defines the minimum performance requirements for both UE-based and UE-assisted TDD A-GNSS terminals. The minimum performance requirements also include combinations of A-GPS and A-GNSS. + +## 4.2 Measurement parameters + +### 4.2.1 UE-based A-GNSS measurement parameters + +In case of UE-based A-GNSS, the measurement parameters are contained in the RRC UE POSITIONING POSITION ESTIMATE INFO IE. The measurement parameter in case of UE-based A-GNSS is the horizontal position estimate reported by the UE and expressed in latitude/longitude. + +### 4.2.2 UE-assisted A-GNSS measurement parameters + +In case of UE-assisted A-GNSS, the measurement parameters are contained in the RRC UE POSITIONING GANSS MEASURED RESULTS IE. The measurement parameters in case of UE-assisted A-GNSS are the UE GANSS code measurements, as specified in 3GPP TS 25.225 [18]. The UE GANSS code measurements that may be combined with UE GPS code phase measurements as specified in 3GPP TS 25.225 [18] are converted into a horizontal position estimate using the procedure detailed in Annex F. + +## 4.3 Response time + +Max Response Time is defined as the time starting from the moment that the UE has received the final RRC measurement control message containing reporting criteria different from "No Reporting" sent before the UE sends the measurement report containing the position estimate or the GANSS and GPS measured result, and ending when the UE starts sending the measurement report containing the position estimate or the GPS and GANSS measured result on the Uu interface. The response times specified for all test cases are Time-to-First-Fix (TTFF) unless otherwise stated, i.e. the UE shall not re-use any information on GANSS and GPS time, location or other aiding data that was previously acquired or calculated and stored internally in the UE. A dedicated test message 'RESET UE POSITIONING STORED INFORMATION' has been defined in TS 34.109 [13] clause 5.4 for the purpose of deleting this information and is detailed in subclause B.1.10. + +## 4.4 Time assistance + +Time assistance is the provision of GANSS reference time to the UE from the network via RRC messages. Currently two different GANSS time assistance methods can be provided by the network. + +- a) Coarse time assistance is always provided by the network and provides current GANSS time to the UE. The time provided is within $\pm 2$ seconds of GANSS system time. It is signalled to the UE by means of the GANSS Day and GANSS TOD fields in the GANSS Reference Time assistance data IE. +- b) Fine time assistance is optionally provided by the network and adds the provision to the UE of the relationship between the GANSS system time and the current UTRAN time. The accuracy of this relationship is $\pm 10 \mu\text{s}$ of the actual relationship. This addresses the case when the network can provide an improved GANSS time accuracy. It is signalled to the UE by means of the SFN and UTRAN GANSS timing of cell frames fields in the GANSS Reference Time assistance data IE. + +The specific GANSS system time is identified through the GANSS Time ID field of the GANSS Reference Time IE. In case where several GANSS are used in the tests, only one GANSS Time ID is used to determine the Time of Day. For all the constellations, the GANSS Time Model assistance and UTC Model assistance shall be available at the system simulator, as specified in Annex E. + +The time of applicability of time assistance is the beginning of the System Frame of the message containing the GANSS Reference time. + +### 4.4.1 Use of fine time assistance + +The use of fine time assistance to improve the GANSS performance of the UE is optional for the UE, even when fine time assistance is signalled by the network. Thus, there are a set minimum performance requirements defined for all UEs and additional minimum performance requirements that are valid for fine time assistance capable UEs only. These requirements are specified in subclause 5.1.2. + +## 4.5 RRC states + +The minimum A-GNSS performance requirements are specified in clause 5 for different RRC states that include Cell\_DCH and Cell\_FACH. Cell\_PCH and URA\_PCH states are for further study. The test and verification procedures are separately defined in Annex B. + +## 4.6 2D position error + +The 2D position error is defined by the horizontal difference in meters between the ellipsoid point reported or calculated from the UE Measurement Report and the actual position of the UE in the test case considered. + +## 4.7 User equipment supporting multiple constellations + +Minimum performance requirements are defined for each global GANSS constellation (Galileo, Modernized GPS, GLONASS and BDS). UEs supporting multiple global constellations shall meet the minimum performance requirements for a combined scenario where each UE supported constellation is simulated. + +NOTE: For test cases where signals from "GPS" and "Modernized GPS" are included, "GPS" and "Modernized GPS" are considered as a single constellation, unless otherwise specified. + +## 4.8 User equipment supporting multiple signals + +For UEs supporting multiple signals, different minimum performance requirements may be associated with different signals. The satellite simulator shall generate all signals supported by the UE. Signals not supported by the UE do not need to be simulated. The relative power levels of each signal type for each GNSS are defined in Table 4.8-1. The individual test scenarios in clause 5 define the reference signal power level for each satellite. The power level of each simulated satellite signal type shall be set to the reference signal power level defined in each test scenario in clause 5 plus the relative power level defined in Table 4.8-1. + +**Table 4.8-1: Relative signal power levels for each signal type for each GNSS** + +| | Galileo | | GPS/Modernized GPS | | GLONASS | | QZSS | | SBAS | | BDS | | | +|--------------------------------------------------------|---------|-------|--------------------|---------|---------|-------|--------|---------|------|------|-----|----|-------| +| | E1 | 0 dB | L1 C/A | 0 dB | G1 | 0 dB | L1 C/A | 0 dB | L1 | 0 dB | B1I | D1 | 0 dB | +| Signal power levels relative to reference power levels | E6 | +2 dB | L1C | +1.5 dB | G2 | -6 dB | L1C | +1.5 dB | | | | D2 | +5 dB | +| | E5 | +2 dB | L2C | -1.5 dB | | | L2C | -1.5 dB | | | | | | +| | | | L5 | +3.6 dB | | | L5 | +3.6 dB | | | | | | +| | | | | | | | | | | | | | | + +NOTE 1: For test cases which involve "Modernized GPS", the satellite simulator shall also generate the GPS L1 C/A signal if the UE supports "GPS" in addition to "Modernized GPS". + +NOTE 2: The signal power levels in the Test Parameter Tables represent the total signal power of the satellite per channel not e.g. pilot and data channels separately. + +NOTE 3: For test cases which involve "BDS", D1 represents MEO/IGSO satellites B1I signal type and D2 represents GEO satellites B1I signal type. + +# 5 A-GANSS minimum performance requirements + +The A-GANSS minimum performance requirements are defined by assuming that all relevant and valid assistance data is received by the UE in order to perform GPS and GANSS measurements and/or position calculation. This clause does not include nor consider delays occurring in the various signalling interfaces of the network. + +In the following subclauses the minimum performance requirements are based on availability of the assistance data information and messages defined in Annexes D and E. + +The requirements in CELL\_PCH and URA\_PCH states are for further study. + +## 5.1 Sensitivity + +A sensitivity requirement is essential for verifying the performance of A-GANSS receiver in weak satellite signal conditions. In order to test the most stringent signal levels for the satellites the sensitivity test case is performed in AWGN channel. This test case verifies the performance of the first position estimate, when the UE is provided with only coarse time assistance and when it is additionally supplied with fine time assistance. + +### 5.1.1 Coarse time assistance + +In this test case 6 satellites are generated for the terminal. AWGN channel model is used. + +**Table 5.1.1-1: Test parameters** + +| System | Parameters | Unit | Value | +|--------------------|-------------------------------------------|---------|-------------------| +| | Number of generated satellites per system | - | See Table 5.1.1-2 | +| | Total number of generated satellites | - | 6 | +| | HDOP range | | 1.4 to 2.1 | +| | Propagation conditions | - | AWGN | +| | GANSS coarse time assistance error range | seconds | $\pm 2$ | +| Galileo | Reference high signal power level | dBm | -142 | +| | Reference low signal power level | dBm | -147 | +| GPS (1) | Reference high signal power level | dBm | -142 | +| | Reference low signal power level | dBm | -147 | +| GLONASS | Reference high signal power level | dBm | -142 | +| | Reference low signal power level | dBm | -147 | +| BDS | Reference high signal power level | dBm | -136 | +| | Reference low signal power level | dBm | -145 | + +Note 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. + +**Table 5.1.1-2: Power level and satellite allocation** + +| | | Satellite allocation for each constellation | | | +|----------------------|-------------------|---------------------------------------------|--------|--------| +| | | GNSS-1 (1) | GNSS-2 | GNSS-3 | +| Single constellation | High signal level | 1 | - | - | +| | Low signal level | 5 | - | - | +| Dual constellation | High signal level | 1 | - | - | +| | Low signal level | 2 | 3 | - | +| Triple constellation | High signal level | 1 | - | - | +| | Low signal level | 1 | 2 | 2 | + +Note 1: For GPS capable receivers, GNSS-1, i.e. the system having the satellite with high signal level, shall be GPS. + +#### 5.1.1.1 Minimum requirements (coarse time assistance) + +The position estimates shall meet the accuracy and response time specified in table 5.1.1.1-1. + +**Table 5.1.1.1-1: Minimum requirements (coarse time assistance)** + +| System | Success rate | 2-D position error | Max response time | +|--------|--------------|--------------------|-------------------| +| All | 95 % | 100 m | 20 s | + +### 5.1.2 Fine time assistance + +This requirement is only valid for fine time assistance capable UEs. In this requirement 6 satellites are generated for the terminal. AWGN channel model is used. + +**Table 5.1.2-1: Test parameters** + +| System | Parameters | Unit | Value | +|---------------------------------------------------------------------------------------------|-------------------------------------------|---------|-------------------| +| | Number of generated satellites per system | - | See Table 5.1.2-2 | +| | Total number of generated satellites | - | 6 | +| | HDOP range | | 1.4 to 2.1 | +| | Propagation conditions | - | AWGN | +| | GANSS coarse time assistance error range | seconds | ±2 | +| | GANSS fine time assistance error range | µs | ±10 | +| Galileo | Reference signal power level | dBm | -147 | +| GPS (1) | Reference signal power level | dBm | -147 | +| GLONASS | Reference signal power level | dBm | -147 | +| BDS | Reference signal power level | dBm | -147 | +| Note 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. | | | | + +**Table 5.1.2-2: Satellite allocation** + +| | Satellite allocation for each constellation | | | +|----------------------|---------------------------------------------|--------|--------| +| | GNSS-1 | GNSS-2 | GNSS-3 | +| Single constellation | 6 | - | - | +| Dual constellation | 3 | 3 | - | +| Triple constellation | 2 | 2 | 2 | + +#### 5.1.2.1 Minimum requirements (fine time assistance) + +The position estimates shall meet the accuracy and response time requirements in table 5.1.2.1-1. + +**Table 5.1.2.1-1: Minimum requirements for fine time assistance capable terminals** + +| System | Success rate | 2-D position error | Max response time | +|--------|--------------|--------------------|-------------------| +| All | 95 % | 100 m | 20 s | + +## 5.2 Nominal accuracy + +Nominal accuracy requirement verifies the accuracy of A-GANSS position estimate in ideal conditions. The primarily aim of the test is to ensure good accuracy for a position estimate when satellite signal conditions allow it. This test case verifies the performance of the first position estimate. + +In this requirement 6 satellites are generated for the terminal. If SBAS is to be tested one additional satellite shall be generated. AWGN channel model is used. The number of simulated satellites for each constellation is as defined in table 5.2-2. + +**Table 5.2-1: Test parameters** + +| System | Parameters | Unit | Value | +|---------------------------------------------------------------------------------------------|-------------------------------------------------|---------|-----------------------| +| | Number of generated satellites per system | - | See Table 5.2-2 | +| | Total number of generated satellites | - | 6 or 7 (2) | +| | HDOP Range | - | 1.4 to 2.1 | +| | Propagation conditions | - | AWGN | +| | GANSS coarse time assistance error range | seconds | ±2 | +| GPS (1) | Reference signal power level for all satellites | dBm | -128.5 | +| Galileo | Reference signal power level for all satellites | dBm | -127 | +| GLONASS | Reference signal power level for all satellites | dBm | -131 | +| QZSS | Reference signal power level for all satellites | dBm | -128.5 | +| SBAS | Reference signal power level for all satellites | dBm | -131 | +| BDS | Reference signal power level for all satellites | dBm | -133 | +| Note 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. | | | | +| Note 2: 7 satellites apply only for SBAS case. | | | | + +If QZSS is supported, one of the GPS satellites will be replaced by a QZSS satellite with respective signal support. + +If SBAS is supported, the SBAS satellite with the highest elevation will be added to the scenario. + +**Table 5.2-2: Satellite allocation** + +| | Satellite allocation for each constellation | | | | +|----------------------------------------------------------------------------|---------------------------------------------|-----------------------|-----------------------|------| +| | GNSS 1 (1) | GNSS 2 (1) | GNSS 3 (1) | SBAS | +| Single constellation | 6 | -- | -- | 1 | +| Dual constellation | 3 | 3 | -- | 1 | +| Triple constellation | 2 | 2 | 2 | 1 | +| Note 1: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS. | | | | | + +### 5.2.1 Minimum requirements (nominal accuracy) + +The position estimates shall meet the accuracy and response time requirements in table 5.2.1-1. + +**Table 5.2.1-1: Minimum requirements** + +| System | Success rate | 2-D position error | Max response time | +|--------|--------------|--------------------|-------------------| +| All | 95 % | 15 m | 20 s | + +## 5.3 Dynamic range + +The aim of a dynamic range requirement is to ensure that a GANSS receiver performs well when visible satellites have rather different signal levels. Strong satellites are likely to degrade the acquisition of weaker satellites due to their cross-correlation products. Hence, it is important in this test case to keep use AWGN in order to avoid loosening the requirements due to additional margin because of fading channels. This test case verifies the performance of the first position estimate. + +In this requirement 6 satellites are generated for the terminal. Two different reference power levels, denoted as "high" and "low" are used for each GNSS. The allocation of "high" and "low" power level satellites depends on the number of supported GNSSs and it is defined in Table 5.3-2. AWGN channel model is used. + +**Table 5.3-1: Test parameters** + +| System | Parameters | Unit | Value | +|---------------------------------------------------------------------------------------------|-------------------------------------------|---------|-----------------| +| | Number of generated satellites per system | - | See Table 5.3-2 | +| | Total number of generated satellites | - | 6 | +| | HDOP Range | - | 1.4 to 2.1 | +| | Propagation conditions | - | AWGN | +| | GANSS coarse time assistance error range | seconds | ±2 | +| Galileo | Reference high signal power level | dBm | -127.5 | +| | Reference low signal power level | dBm | -147 | +| GPS (1) | Reference high signal power level | dBm | -129 | +| | Reference low signal power level | dBm | -147 | +| GLONASS | Reference high signal power level | dBm | -131.5 | +| | Reference low signal power level | dBm | -147 | +| BDS | Reference high signal power level | dBm | -133.5 | +| | Reference low signal power level | dBm | -145 | +| Note 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. | | | | + +**Table 5.3-2: Power level and satellite allocation** + +| | | Satellite allocation for each constellation | | | +|----------------------------------------------------------------------------|-------------------|----------------------------------------------------|-----------------------------|-----------------------------| +| | | GNSS 1(1) | GNSS 2(1) | GNSS 3(1) | +| Single constellation | High signal level | 2 | -- | -- | +| | Low signal level | 4 | -- | -- | +| Dual constellation | High signal level | 1 | 1 | -- | +| | Low signal level | 2 | 2 | -- | +| Triple constellation | High signal level | 1 | 1 | 1 | +| | Low signal level | 1 | 1 | 1 | +| Note 1: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS. | | | | | + +### 5.3.1 Minimum requirements (dynamic range) + +The position estimates shall meet the accuracy and response time requirements in table 5.3.1-1. + +**Table 5.3.1-1: Minimum requirements** + +| System | Success rate | 2-D position error | Max response time | +|---------------|---------------------|---------------------------|--------------------------| +| All | 95 % | 100 m | 20 s | + +## 5.4 Multi-path scenario + +The purpose of the test case is to verify the receiver's tolerance to multipath while keeping the test setup simple. This test case verifies the performance of the first position estimate. + +In this test 6 satellites are generated for the terminal. Some of the satellites have a one tap channel representing the Line-Of-Sight (LOS) signal. The other satellites have a two-tap channel, where the first tap represents the LOS signal and the second represents a reflected and attenuated signal as specified in Annex C.2. The number of satellites generated for each GNSS as well as the channel model used depends on the number of systems supported by the UE and is defined in table 5.4-2. The channel model as specified in Annex C.2 further depends on the generated signal. + +**Table 5.4-1: Test parameter** + +| System | Parameters | Unit | Value | +|---------------------------------------------------------------------------------------------|-------------------------------------------|-------------|-----------------| +| | Number of generated satellites per system | - | See Table 5.4-2 | +| | Total number of generated satellites | - | 6 | +| | HDOP range | | 1.4 to 2.1 | +| | Propagation conditions | - | AWGN | +| | GNSS coarse time assistance error range | seconds | ±2 | +| Galileo | Reference signal power level | dBm | -127 | +| GPS (1) | Reference signal power level | dBm | -128.5 | +| GLONASS | Reference signal power level | dBm | -131 | +| BDS | Reference signal power level | dBm | -133 | +| Note 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. | | | | + +**Table 5.4-2: Channel model allocation** + +| | | Channel model allocation for each constellation | | | +|----------------------|-----------------|--------------------------------------------------------|---------------|---------------| +| | | GNSS-1 | GNSS-2 | GNSS-3 | +| Single constellation | One-tap channel | 2 | -- | -- | +| | Two-tap channel | 4 | -- | -- | +| Dual constellation | One-tap channel | 1 | 1 | -- | +| | Two-tap channel | 2 | 2 | -- | +| Triple constellation | One-tap channel | 1 | 1 | 1 | +| | Two-tap channel | 1 | 1 | 1 | + +### 5.4.1 Minimum requirements (multi-path scenario) + +The position estimates shall meet the accuracy and response time requirements in table 5.4.1-1. + +**Table 5.4.1-1: Minimum requirements** + +| System | Success rate | 2-D position error | Max response time | +|--------|--------------|--------------------|-------------------| +| All | 95 % | 100 m | 20 s | + +## 5.5 Moving scenario and periodic update + +The purpose of the test case is to verify the receiver's capability to produce GANSS measurements or location fixes on a regular basis, and to follow when it is located in a vehicle that slows down, turns or accelerates. A good tracking performance is essential for certain location services. A moving scenario with periodic update is well suited for verifying the tracking capabilities of an A-GANSS receiver in changing UE speed and direction. In the requirement the UE moves on a rectangular trajectory, which imitates urban streets. AWGN channel model is used. This test is not performed as a Time to First Fix (TTFF) test. + +In this requirement 6 satellites are generated for the terminal. The UE is requested to use periodical reporting with a reporting interval of 2 seconds. + +The UE moves on a rectangular trajectory of 940 m by 1440 m with rounded corner defined in figure 5.5-1. The initial reference is first defined followed by acceleration to final speed of 100 km/h in 250 m. The UE then maintains the speed for 400 m. This is followed by deceleration to final speed of 25 km/h in 250 m. The UE then turn 90 degrees with turning radius of 20 m at 25 km/h. This is followed by acceleration to final speed of 100 km/h in 250 m. The sequence is repeated to complete the rectangle. + +**Table 5.5-1: Trajectory Parameters** + +| Parameter | Distance (m) | Speed (km/h) | +|----------------------------------|--------------|-------------------------| +| $l_{11}, l_{15}, l_{21}, l_{25}$ | 20 | 25 | +| $l_{12}, l_{14}, l_{22}, l_{24}$ | 250 | 25 to 100 and 100 to 25 | +| $l_{13}$ | 400 | 100 | +| $l_{23}$ | 900 | 100 | + +![Diagram of a rectangular trajectory with rounded corners. The horizontal dimension is labeled 1 440 m and the vertical dimension is labeled 940 m. The corners have a radius r = 20 m. The trajectory is defined by points l11, l12, l13, l14, l15 on the top side and l21, l22, l23, l24, l25 on the bottom side. Arrows indicate the direction of movement: clockwise.](3f1987804d7d78bc3b3bc560e974280a_img.jpg) + +The diagram shows a rectangular trajectory with rounded corners. The horizontal dimension is labeled 1 440 m and the vertical dimension is labeled 940 m. The corners have a radius $r = 20$ m. The trajectory is defined by points $l_{11}, l_{12}, l_{13}, l_{14}, l_{15}$ on the top side and $l_{21}, l_{22}, l_{23}, l_{24}, l_{25}$ on the bottom side. Arrows indicate the direction of movement: clockwise. + +Diagram of a rectangular trajectory with rounded corners. The horizontal dimension is labeled 1 440 m and the vertical dimension is labeled 940 m. The corners have a radius r = 20 m. The trajectory is defined by points l11, l12, l13, l14, l15 on the top side and l21, l22, l23, l24, l25 on the bottom side. Arrows indicate the direction of movement: clockwise. + +**Figure 5.5-1: Rectangular trajectory of the moving scenario and periodic update test case** + +**Table 5.5-2: Test Parameters** + +| System | Parameters | Unit | Value | +|---------------------------------------------------------------------------------------------|-------------------------------------------------|---------|-----------------| +| | Number of generated satellites per system | - | See Table 5.5-3 | +| | Total number of generated satellites | - | 6 | +| | HDOP Range per system | - | 1.4 to 2.1 | +| | Propagation conditions | - | AWGN | +| | GANSS coarse time assistance error range | seconds | ±2 | +| Galileo | Reference signal power level for all satellites | dBm | -127 | +| GPS (1) | Reference signal power level for all satellites | dBm | -128.5 | +| GLONASS | Reference signal power level for all satellites | dBm | -131 | +| BDS | Reference signal power level for all satellites | dBm | -133 | +| Note 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. | | | | + +**Table 5.5-3: Satellite allocation** + +| | Satellite allocation for each constellation | | | +|----------------------------------------------------------------------------|---------------------------------------------|-----------------------|-----------------------| +| | GNSS 1 (1) | GNSS 2 (1) | GNSS 3 (1) | +| Single constellation | 6 | -- | -- | +| Dual constellation | 3 | 3 | -- | +| Triple constellation | 2 | 2 | 2 | +| Note 1: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS. | | | | + +### 5.5.1 Minimum requirements (moving scenario and periodic update) + +The position estimates shall meet the accuracy requirement of table 5.5.1-1 with the periodical reporting interval defined in table 5.5.1-1 after the first reported position estimates. + +NOTE: In the actual testing the UE may report error messages until it has been able to acquire GPS/GANSS measured results or a position estimate. The test equipment shall only consider the first measurement report different from an error message as the first position estimate in the requirement in table 5.5.1-1. + +**Table 5.5.1-1: Minimum requirements** + +| System | Success rate | 2-D position error | Periodical reporting interval | +|--------|--------------|--------------------|-------------------------------| +| All | 95 % | 50 m | 2 s | + +# --- Annex A (normative): Test cases --- + +## A.1 Conformance tests + +The conformance tests are specified in 3GPP TS 37.571 [20]. Statistical interpretation of the requirements is described in clause A.2. + +## --- A.2 Requirement classification for statistical testing + +Requirements in the present document are either expressed as absolute requirements with a single value stating the requirement, or expressed as a success rate. There are no provisions for the statistical variations that will occur when the parameter is tested. + +Annex B lists the test parameters needed for the tests. The test will result in an outcome of a test variable value for the DUT inside or outside the test limit. Overall, the probability of a "good" DUT being inside the test limit(s) and the probability of a "bad" DUT being outside the test limit(s) should be as high as possible. For this reason, when selecting the test variable and the test limit(s), the statistical nature of the test is accounted for. + +When testing a parameter with a statistical nature, a confidence level has to be set. The confidence level establishes the probability that a DUT passing the test actually meets the requirement and determines how many times a test has to be repeated. The confidence levels are defined for the final tests in 3GPP TS 37.571 [20]. + +# Annex B (normative): Test conditions + +## B.1 General + +This annex specifies the additional parameters that are needed for the test cases specified in clause 5 and applies to all tests unless otherwise stated. + +### B.1.1 Parameter values + +Additionally, amongst all the listed parameters (see Annex E), the following values for some important parameters are to be used in the measurement control message. + +**Table B.1.1-1: Parameter values** + +| Information element | Value - TTFF tests (except nominal accuracy test) | Value - TTFF tests (nominal accuracy test) | Value - Periodic tests | +|----------------------------|---------------------------------------------------|--------------------------------------------|------------------------| +| Measurement Reporting Mode | Periodical reporting | Periodical reporting | Periodical reporting | +| Amount of reporting | 1 | 1 | Infinite (see Note) | +| Reporting interval | 20 000 ms | 20 000 ms | 2 000 ms | +| Horizontal accuracy | 51.2 m | 7.7 m | 24.5 m | +| Vertical accuracy | 102 m | 102 m | 102 m | + +Note: Infinite means during the complete test time. + +In the Sensitivity test case with Fine Time Assistance, the following parameter values are used. + +**Table B.1.1-2: Parameters for fine time assistance test** + +| Information element | Value | +|-----------------------------------------------|---------| +| TUTRAN-GPS drift rate | 0 | +| TUTRAN-GANSS drift rate | 0 | +| UE Positioning GPS Reference Time Uncertainty | 10.2 µs | +| GANSS TOD Uncertainty | 10.2 µs | + +### B.1.2 Time assistance + +For every Test Instance in each TTFF test case, the GANSS/GPS Reference Time shall have a random offset, relative to GANSS/GPS system time, within the error range of Coarse Time Assistance defined in the test case. This offset value shall have a uniform random distribution. + +In addition, for every Fine Time Assistance Test Instance the IE UTRAN GPS/GANSS timing of cell frames shall have a random offset, relative to the true value of the relationship between the two time references, within the error range of Fine Time Assistance defined in the test case. This offset value shall have a uniform random distribution. + +For the Moving Scenario and Periodic Update Test Case the GANSS/GPS Reference Time shall be set to the nominal value. + +### B.1.3 GANSS reference time + +For every Test Instance in each TTFF test case, the GANSS reference time (and GPS reference time, if applicable) shall be advanced so that, at the time the fix is made, it is at least 2 minutes later than the previous fix. + +### B.1.4 Reference and UE locations + +There is no limitation on the selection of the reference location, consistent with achieving the required HDOP for the Test Case. For each test instance the reference location shall change sufficiently such that the UE shall have to use the + +new assistance data. The uncertainty of the semi-major axis is 3 km. The uncertainty of the semi-minor axis is 3 km. The orientation of major axis is 0 degrees. The uncertainty of the altitude information is 500 m. The confidence factor is 68 %. + +For every Test Instance in each TTFF test case, the UE location shall be randomly selected to be within 3 km of the Reference Location. The Altitude of the UE shall be randomly selected between 0 m to 500 m above WGS-84 reference ellipsoid. These values shall have uniform random distributions. + +For test cases which include satellites from regional systems, such as QZSS and SBAS, the reference location shall be selected within the defined coverage area of the systems. + +### B.1.5 Satellite constellation and assistance data + +The satellite constellation shall consist of 24 satellites for GLONASS; 27 satellites for GPS, Modernized GPS and Galileo; 3 satellites for QZSS; 2 satellites for SBAS and 35 satellites for BDS (5 GEO, 27 MEO, 3 IGSO). Almanac assistance data shall be available for all these satellites. At least 7 of the satellites per GPS, Modernized GPS, Galileo, GLONASS and BDS constellation shall be visible to the UE (that is, above 15 degrees elevation with respect to the UE). At least 1 of the satellites for QZSS shall be within 15 degrees of zenith; and at least 1 of the satellites for SBAS shall be visible to the UE. For BDS with reference location in Asia, at least 1 of the visible satellites shall be a GEO (above 15 degrees elevation with respect to the UE). All other satellite specific assistance data shall be available for all visible satellites. In each test, signals are generated for only 6 satellites (or 7 if SBAS is included). The HDOP for the test shall be calculated using these satellites. The simulated satellites for GPS, Modernized GPS, Galileo, GLONASS and BDS shall be selected from the visible satellites for each constellation consistent with achieving the required HDOP for the test. For BDS with reference location in Asia, 1 of the simulated satellites shall be a GEO. + +NOTE: Currently up to 30 BDS satellites (maximum 22 MEO) can be supported. + +### B.1.6 Atmospheric delay + +Typical Ionospheric and Tropospheric delays shall be simulated and the corresponding values inserted into the Ionospheric Model IEs. + +### B.1.7 Sensors + +The minimum performance requirements shall be met without the use of any data coming from sensors that can aid the positioning. + +### B.1.8 Information elements + +The information elements that are available to the UE in all the test cases are listed in Annex E. + +### B.1.9 GNSS signals + +The GNSS signal is defined at the A-GNSS antenna connector of the UE. For UE with integral antenna only, a reference antenna with a gain of 0 dBi is assumed. + +### B.1.10 RESET UE POSITIONING STORED INFORMATION Message + +In order to ensure each Test Instance in each TTFF test is performed under Time to First Fix (TTFF) conditions, a dedicated test signal (*RESET UE POSITIONING STORED INFORMATION*) defined in TS 34.109 [13] clause 5.4 shall be used. + +When the UE receives the '*RESET UE POSITIONING STORED INFORMATION*' signal, with the IE *UE POSITIONING TECHNOLOGY* set to *AGNSS* it shall: + +- discard any internally stored GPS and GANSS reference time, reference location, and any other aiding data obtained or derived during the previous test instance (e.g. expected ranges and Doppler); +- accept or request a new set of reference time or reference location or other required information, as in a TTFF condition; + +- calculate the position or perform GNSS measurements using the 'new' reference time or reference location or other information. + +### B.1.11 GNSS system time offsets + +If more than one GNSS is used in a test, the accuracy of the GNSS-GNSS Time Offsets used at the system simulator shall be better than 3 ns. + +# Annex C (normative): Propagation conditions + +## C.1 Static propagation conditions + +The propagation for the static performance measurement is an Additive White Gaussian Noise (AWGN) environment. No fading and multi-paths exist for this propagation model. + +## C.2 Multi-path case + +Doppler frequency difference between direct and reflected signal paths is applied to the carrier and code frequencies. The Carrier and Code Doppler frequencies of LOS and multi-path for GANSS signals are defined in table C.2-1. + +**Table C.2-1: Multipath case** + +| Initial Relative Delay [m] | Carrier Doppler frequency of tap [Hz] | Code Doppler frequency of tap [Hz] | Relative mean Power [dB] | +|--------------------------------------------------------|---------------------------------------|------------------------------------|--------------------------| +| 0 | $F_d$ | $F_d / N$ | 0 | +| X | $F_d - 0.1$ | $(F_d - 0.1) / N$ | Y | +| Note: Discrete Doppler frequency is used for each tap. | | | | + +Where the X and Y depends on the GNSS signal type and is shown in table C.2-2, and N is the ratio between the transmitted carrier frequency of the signals and the transmitted chip rate as shown in table C.2-3 (where k in table C.2-3 is the GLONASS frequency channel number). + +**Table C.2-2: Relative Delay and Attenuation of Non Line of Sight Signals** + +| System | Signals | X [m] | Y [dB] | +|--------------------|---------|-------|--------| +| Galileo | E1 | 125 | -4.5 | +| | E5a | 15 | -6 | +| | E5b | 15 | -6 | +| GPS/Modernized GPS | L1 C/A | 150 | -6 | +| | L1C | 125 | -4.5 | +| | L2C | 150 | -6 | +| | L5 | 15 | -6 | +| GLONASS | G1 | 275 | -12.5 | +| | G2 | 275 | -12.5 | +| BDS | B1I | 75 | -4.5 | + +**Table C.2-3: Ratio between the transmitted carrier frequency of the signals and the transmitted chip rate** + +| System | Signals | N | +|--------------------|---------|--------------------------| +| Galileo | E1 | 1540 | +| | E5a | 115 | +| | E5b | 118 | +| GPS/Modernized GPS | L1 C/A | 1540 | +| | L1C | 1540 | +| | L2C | 1200 | +| | L5 | 115 | +| GLONASS | G1 | $3135.03 + k \cdot 1.10$ | +| | G2 | $2438.36 + k \cdot 0.86$ | +| BDS | B1I | 763 | + +The initial carrier phase difference between taps shall be randomly selected between 0 and $2\pi$ . The initial value shall have uniform random distribution. + +# Annex D (normative): Measurement sequence chart + +## D.1 General + +The measurement Sequence Charts that are required in all the test cases, are defined in this clause. + +## D.2 TTFF measurement sequence chart + +The measurement sequence chart for the TTFF test cases, for both UE-assisted and UE-based GANSS, is defined in this subclause. + +![Sequence diagram showing the measurement sequence for TTFF test cases between a System Simulator (SS) and a User Equipment (UE).](b2ea162a0f53d5e0504b7d28346e0754_img.jpg) + +``` + +sequenceDiagram + participant SS + participant UE + Note left of SS: (a) + SS->>UE: Reset UE Positioning Stored Information + Note left of SS: (b) + SS->>UE: RRC Measurement Control (Setup) + Note left of UE: (c) + UE-->>SS: RRC Measurement Report (Assistance Data Request) + Note left of SS: (d) + SS->>UE: RRC Measurement Control (Modify) + Note left of SS: (e) + SS-->>UE: RRC Measurement Control (Modify) + Note left of UE: (f) + UE-->>SS: RRC Measurement Report + +``` + +Sequence diagram showing the measurement sequence for TTFF test cases between a System Simulator (SS) and a User Equipment (UE). + +Figure D.2-1: Measurement Sequence Chart for the TTFF Test Cases + +- (a) The system simulator sends a RESET UE POSITIONING STORED INFORMATION message with the IE *UE POSITIONING TECHNOLOGY* set to *AGNSS*. +- (b) The system simulator sends a RRC MEASUREMENT CONTROL message without assistance data including the following information elements: + +| | | +|------------------------------------------|------------------------------------------------------------------------| +| MEASUREMENT COMMAND | Setup | +| CHOICE MEASUREMENT TYPE | UE positioning measurement | +| UE POSITIONING REPORTING QUANTITY | | +| >Method Type | set to either 'UE assisted' or 'UE based', dependent on the test case; | +| >Positioning Methods | set to 'GPS'; | +| >Horizontal Accuracy | as defined in Annex B; | +| >Vertical Accuracy | as defined in Annex B; | +| >Additional Assistance Data Request | TRUE | +| >GANSS Positioning Methods | set according to the UE capabilities and test case; | +| MEASUREMENT VALIDITY | | +| >UE state | All states | +| CHOICE REPORTING CRITERIA | Periodical reporting criteria | +| >Amount of reporting | 1 (see Annex B); | +| >Reporting interval | 20 seconds (see Annex B); | + +- (c) The UE responds with a RRC MEASUREMENT REPORT message including the *UE POSITIONING ERROR* IE with 'Error Reason' set to 'Assistance data missing', and including a request for additional GPS and/or GANSS assistance data. + +- (d) – (e) The system simulator provides the requested assistance data that are available as defined in Annex E in one or more RRC MEASUREMENT CONTROL messages with MEASUREMENT COMMAND IE set to 'modify' and the CHOICE REPORTING CRITERIA set to 'no reporting' in all but the last RRC MEASUREMENT CONTROL message. The last RRC MEASUREMENT CONTROL message which is required to deliver the entire set of requested assistance data in step (c) includes the CHOICE REPORTING CRITERIA set to 'Periodical reporting criteria' as defined in step (b). +- (f) The UE sends a RRC MEASUREMENT REPORT message including the IE UE POSITIONING MEASURED RESULTS with UE POSITIONING POSITION ESTIMATE INFO present in case of UE-based, or UE POSITIONING GPS MEASURED RESULTS and/or UE POSITIONING GANSS MEASURED RESULTS present in case of UE-assisted GANSS. + +Steps (a) to (f) are repeated for each test instance. + +## D.3 Periodic update measurement sequence chart + +The measurement sequence chart for the Moving Scenario and Periodic Update test case, for both UE-assisted and UE-based GANSS, is defined in this subclause. + +![Sequence diagram showing the interaction between a System Simulator (SS) and a User Equipment (UE) for a periodic update measurement test case. The sequence starts with (a) SS to UE: Reset UE Positioning Stored Information. (b) SS to UE: RRC Measurement Control (Setup). (c) UE to SS: RRC Measurement Report (Assistance Data Request). (d) SS to UE: RRC Measurement Control (Modify). (e) SS to UE: RRC Measurement Control (Modify) - shown as a dashed line. (f) UE to SS: RRC Measurement Report. (g) UE to SS: RRC Measurement Report. (h) UE to SS: RRC Measurement Report. Between (h) and (i), there are three vertical dots indicating repeated steps. (i) UE to SS: RRC Measurement Report.](86b4670fc1a5a694821ee92b99c1209a_img.jpg) + +Sequence diagram showing the interaction between a System Simulator (SS) and a User Equipment (UE) for a periodic update measurement test case. The sequence starts with (a) SS to UE: Reset UE Positioning Stored Information. (b) SS to UE: RRC Measurement Control (Setup). (c) UE to SS: RRC Measurement Report (Assistance Data Request). (d) SS to UE: RRC Measurement Control (Modify). (e) SS to UE: RRC Measurement Control (Modify) - shown as a dashed line. (f) UE to SS: RRC Measurement Report. (g) UE to SS: RRC Measurement Report. (h) UE to SS: RRC Measurement Report. Between (h) and (i), there are three vertical dots indicating repeated steps. (i) UE to SS: RRC Measurement Report. + +**Figure D.3-1: Measurement Sequence Chart for the Moving Scenario and Periodic Update Test Case** + +- (a) The system simulator sends a RESET UE POSITIONING STORED INFORMATION message with the IE *UE POSITIONING TECHNOLOGY* set to *AGNSS*. +- (b) The system simulator sends a RRC MEASUREMENT CONTROL message without assistance data including the following information elements: + +| | | +|------------------------------------------|------------------------------------------------------------------------| +| MEASUREMENT COMMAND | Setup | +| CHOICE MEASUREMENT TYPE | UE positioning measurement | +| UE POSITIONING REPORTING QUANTITY | | +| >Method Type | set to either 'UE assisted' or 'UE based', dependent on the test case; | +| >Positioning Methods | set to 'GPS'; | +| >Horizontal Accuracy | as defined in Annex B; | + +>Vertical Accuracy as defined in Annex B; +>Additional Assistance Data Request TRUE +>GNSS Positioning Methods set according to the UE capabilities and test case; +MEASUREMENT VALIDITY +>UE state All states +CHOICE REPORTING CRITERIA Periodical reporting criteria +>Amount of reporting infinite (see Annex B); +>Reporting interval 2 seconds (see Annex B); + +- (c) The UE responds with a RRC MEASUREMENT REPORT message including the *UE POSITIONING ERROR* IE with 'Error Reason' set to 'Assistance data missing', and including a request for additional GPS and/or GNSS assistance data. +- (d) – (e) The system simulator provides the requested assistance data that are available as defined in Annex E in one or more RRC MEASUREMENT CONTROL messages with MEASUREMENT COMMAND IE set to 'modify' and the CHOICE REPORTING CRITERIA set to 'no reporting' in all but the last RRC MEASUREMENT CONTROL message. The last RRC MEASUREMENT CONTROL message which is required to deliver the entire set of requested assistance data in step (c) includes the CHOICE REPORTING CRITERIA set to 'Periodical reporting criteria' as defined in step (b). +- (f) The UE sends a RRC MEASUREMENT REPORT message including the IE *UE POSITIONING MEASURED RESULTS* with *UE POSITIONING POSITION ESTIMATE INFO* present in case of UE-based, or *UE POSITIONING GPS MEASURED RESULTS* and/or *UE POSITIONING GNSS MEASURED RESULTS* present in case of UE-assisted GNSS. +- (g) – (i) The UE continues to provide RRC MEASUREMENT REPORT messages as in step (g) until the moving trajectory has been completed. + +NOTE: The UE may report error messages at step (f) until it has been able to acquire GNSS signals. + +# Annex E (normative): Assistance data required for testing + +## E.1 Introduction + +This annex defines the assistance data IEs available at the SS in all test cases. The assistance data shall be given for satellites as defined in B.1.5. + +The information elements are given with reference to 3GPP TS 25.331 [14], where the details are defined. + +## E.2 GPS assistance data + +The GPS L1 C/A assistance data are as defined in 3GPP TS 25.171 [10], Annex E. + +## E.3 GANSS assistance data + +- a) **UE Positioning GANSS Reference Time IE.** This information element is defined in subclause 10.3.7.96o of 3GPP TS 25.331 [14]. + +**Table E.3-1: GANSS reference time IE** + +| Name of the IE | Fields of the IE | All tests except Sensitivity Fine Time Assistance | Sensitivity Fine Time Assistance test | +|-------------------------------------|------------------------------------|---------------------------------------------------|---------------------------------------| +| UE Positioning GANSS Reference Time | | | | +| | GANSS Day | Yes | Yes | +| | GANSS TOD | Yes | Yes | +| | GANSS TOD Uncertainty | Yes | Yes | +| | GANSS Time ID | Yes | Yes | +| | UTRAN GANSS Reference Time | | | +| | >UTRAN GANSS Timing of Cell Frames | | Yes | +| | >CHOICE mode | | Yes | +| | >>FDD | | Yes | +| | >>>Primary CPICH Info | | Yes | +| | >SFN | | Yes | +| | TUTRAN-GANSS Drift Rate | | Yes | + +- b) **UE Positioning GANSS Reference UE Position IE.** This information element is defined in subclause 10.3.8.4c of 3GPP TS 25.331 [14]. + +**Table E.3-2: GANSS reference location IE** + +| Name of the IE | Fields of the IE | +|--------------------------------------------|---------------------------------------------------------| +| UE Positioning GANSS Reference UE Position | Ellipsoid point with Altitude and uncertainty ellipsoid | + +- c) **UE Positioning GANSS Ionospheric Model IE.** This information element is defined in subclause 10.3.7.92a of 3GPP TS 25.331 [14]. + +**Table E.3-3: GANSS ionospheric model IE** + +| Name of the IE | Fields of the IE | +|----------------------------------------|------------------| +| UE Positioning GANSS Ionospheric Model | | + +- d) **UE Positioning GANSS Additional Ionospheric Model IE.** This information element is defined in subclause 10.3.7.92b of 3GPP TS 25.331 [14]. + +**Table E.3-4: GANSS additional ionospheric model IE** + +| Name of the IE | Fields of the IE | +|---------------------------------------------------|------------------| +| UE Positioning GANSS Additional Ionospheric Model | | + +- e) **UE Positioning GANSS Time Model IE.** This information element is only required for multi system tests, and is defined in subclause 10.3.7.97a of 3GPP TS 25.331 [14]. + +**Table E.3-5: GANSS time model IE** + +| Name of the IE | Fields of the IE | +|---------------------------------|----------------------------------------------------| +| UE Positioning GANSS Time Model | | +| | GNSS_TOD_ID
For each GNSS included in the test. | + +- f) **UE Positioning GANSS Navigation Model IE.** This information element is defined in subclause 10.3.7.94a of 3GPP TS 25.331 [14]. + +**Table E.3-6: GANSS navigation model IE** + +| Name of the IE | Fields of the IE | +|---------------------------------------|------------------| +| UE Positioning GANSS Navigation Model | | + +- g) **UE Positioning GANSS Additional Navigation Models IE.** This information element is defined in subclause 10.3.7.94b of 3GPP TS 25.331 [14]. + +**Table E.3-7: GANSS navigation model IE** + +| Name of the IE | Fields of the IE | +|---------------------------------------|------------------| +| UE Positioning GANSS Navigation Model | | + +**Table E.3-8: GANSS clock and orbit model choices** + +| GANSS | Clock and Orbit Model Choice | +|---------------------|------------------------------| +| Galileo | Model-1 | +| Modernized GPS | Model-3 | +| GLONASS | Model-4 | +| QZSS QZS-L1 | Model-2 | +| QZSS QZS-L1C/L2C/L5 | Model-3 | +| SBAS | Model-5 | +| BDS | Model-6 | + +- h) **UE Positioning GANSS Reference Measurement Information IE.** This information element is defined in subclause 10.3.7.88b of 3GPP TS 25.331 [14]. + +**Table E.3-9: GANSS reference measurement information IE** + +| Name of the IE | Fields of the IE | +|--------------------------------------------------------|--------------------------------------| +| UE Positioning GANSS Reference Measurement Information | | +| | SatID | +| | Doppler (0 th order term) | +| | Doppler (1 st order term) | +| | Doppler Uncertainty | +| | Code Phase | +| | Integer Code Phase | +| | Code Phase Search Window | +| | Azimuth | +| | Elevation | + +- i) **UE Positioning GANSS Almanac IE.** This information element is defined in subclause 10.3.7.89a of 3GPP TS 25.331 [14]. + +**Table E.3-10: GANSS almanac model IE** + +| Name of the IE | Fields of the IE | +|------------------------------|------------------| +| UE Positioning GANSS Almanac | | + +**Table E.3-11: GANSS almanac choices** + +| GANSS | Almanac Model Choice | +|---------------------|----------------------| +| Galileo | Model-1 | +| Modernized GPS | Model-3,4 | +| GLONASS | Model-5 | +| QZSS QZS-L1 | Model-2 | +| QZSS QZS-L1C/L2C/L5 | Model-3,4 | +| SBAS | Model-6 | +| BDS | Model-7 | + +- j) **UE Positioning GANSS UTC Model IE.** This information element is defined in subclause 10.3.7.97c of 3GPP TS 25.331 [14]. + +**Table E.3-12: GANSS UTC model IE** + +| Name of the IE | Fields of the IE | +|--------------------------------|------------------| +| UE Positioning GANSS UTC Model | | + +- k) **UE Positioning GANSS Additional UTC Models IE.** This information element is defined in subclause 10.3.7.97d of 3GPP TS 25.331 [14]. + +**Table E.3-13: GANSS additional UTC model IE** + +| Name of the IE | Fields of the IE | +|-----------------------------------------------|------------------| +| UE Positioning GANSS Additional UTC Models IE | | + +**Table E.3-14: GANSS UTC model choices** + +| GANSS | UTC Model Choice | +|---------------------|--------------------------------| +| Galileo | UE Positioning GANSS UTC Model | +| Modernized GPS | Model-1 | +| GLONASS | Model-2 | +| QZSS QZS-L1 | UE Positioning GANSS UTC Model | +| QZSS QZS-L1C/L2C/L5 | Model-1 | +| SBAS | Model-3 | +| BDS | Model-4 | + +- I) UE Positioning GANSS Auxiliary Information IE.** This information element is defined in subclause 10.3.7.97f of 3GPP TS 25.331 [14]. + +**Table E.3-15: GANSS auxiliary information IE** + +| Name of the IE | Fields of the IE | +|-----------------------------------------------|-------------------------| +| UE Positioning GANSS Auxiliary Information IE | | + +# --- Annex F (normative): Converting UE-assisted measurement reports into position estimates --- + +## F.1 Introduction + +To convert the UE measurement reports in case of UE-assisted mode of A-GNSS into position errors, a transformation between the "measurement domain" (code-phases, etc.) into the "state" domain (position estimate) is necessary. Such a transformation procedure is outlined in the following clauses. The details can be found in [3], [4], [5], [6], [7], [8], [9], [19], [16] and [17]. + +## --- F.2 UE measurement reports + +In case of UE-assisted A-GNSS, the measurement parameters are contained in the RRC UE POSITIONING GANSS MEASURED RESULTS IE (subclause 10.3.7.93a in 3GPP TS 25.331 [14]). In case the UE provides also measurements on the GPS L1 C/A signal, the measurement parameters are contained in the RRC UE POSITIONING GPS MEASURED RESULTS IE (subclause 10.3.7.93 in 3GPP TS 25.331 [14]). The measurement parameters required for calculating the UE position are: + +- 1) Reference Time: The UE has two choices for the Reference Time: + - a) "UE GANSS Timing of Cell Frames" and/or "UE GPS Timing of Cell Frames"; + - b) "GANSS TOD msec" and/or "GPS TOW msec" if GPS L1 C/A signal measurements are also provided. + +NOTE: It is not expected that an UE will ever report both a GANSS TOD and a GPS TOW. However if two time stamps are provided and they derive from different user times, be aware that no compensation is made for this difference and this could affect the location accuracy. + +- 2) Measurement Parameters for each GANSS and GANSS Signal: 1 to : + - a) "Satellite ID"; mapping according to table 10.3.7.88b in 3GPP TS 25.331 [14]; + - b) "GANSS Code Phase"; + - c) "GANSS Integer Code Phase"; + - d) "GANSS Integer Code Phase Extension"; + - e) "Code Phase RMS Error"; +- 3) Additional Measurement Parameters in case of GPS L1 C/A signal measurements are also provided: 1 to : + - a) "Satellite ID (SV PRN)"; + - b) "Whole GPS chips"; + - c) "Fractional GPS Chips"; + - d) "Pseudorange RMS Error". + +Additional information required at the system simulator: + +- 1) "UE Positioning GANSS Reference UE Position" or "UE Positioning GPS Reference UE Position" (subclause 10.3.8.4c in 3GPP TS 25.331 [14]): +Used for initial approximate receiver coordinates. +- 2) "UE Positioning GANSS Navigation Model" and "UE Positioning GANSS Additional Navigation Models" (subclauses 10.3.7.94a and 10.3.7.94b in 3GPP TS 25.331 [14]): + +Contains the ephemeris and clock correction parameters as specified in the relevant ICD of each supported GANSS; used for calculating the satellite positions and clock corrections. + +- 3) "UE Positioning GANSS Ionospheric Model" (subclause 10.3.7.92a in 3GPP TS 25.331 [14]): +Contains the ionospheric parameters which allow the single frequency user to utilize the ionospheric model as specified in [7] for computation of the ionospheric delay. +- 4) "UE Positioning GANSS Additional Ionospheric Model" (subclause 10.3.7.92b in 3GPP TS 25.331 [14]): +Contains the ionospheric parameters which allow the single frequency user to utilize the ionospheric model as specified in [6] for computation of the ionospheric delay. +- 5) "UE Positioning GANSS Time Model" (subclause 10.3.7.97a in 3GPP TS 25.331 [14]): +Contains the GNSS-GNSS Time Offset for each supported GANSS. Note, that "UE Positioning GANSS Time Model" IE contains only the sub-ms part of the offset. Any potential integer seconds offset may be obtained from "UE Positioning GPS UTC Model" (subclause 10.3.7.97 in 3GPP TS 25.331 [14]), "UE Positioning GANSS UTC Model" (subclause 10.3.7.97c in 3GPP TS 25.331 [14]), or "UE Positioning GANSS Additional UTC Models" (subclause 10.3.7.97d in 3GPP TS 25.331 [14]). +- 6) "UE Positioning GPS Navigation Model" (subclause 10.3.7.94 in 3GPP TS 25.331 [14]): +Contains the GPS ephemeris and clock correction parameters as specified in [3]; used for calculating the GPS satellite positions and clock corrections in case of GPS L1 C/A signal measurements are the only GPS measurements provided in addition to GANSS measurements. +- 7) "UE Positioning GPS Ionospheric Model" (subclause 10.3.7.92 in 3GPP TS 25.331 [14]): +Contains the ionospheric parameters which allow the single frequency user to utilize the ionospheric model as specified in [3] for computation of the ionospheric delay. + +## F.3 Weighted Least Squares (WLS) position solution + +The WLS position solution problem is concerned with the task of solving for four unknowns; $x_u, y_u, z_u$ the receiver coordinates in a suitable frame of reference (usually ECEF) and $b_u$ the receiver clock bias relative to the selected GNSS specific system time. It typically requires the following steps: + +### Step 1: Formation of pseudo-ranges + +The observation of code phase reported by the UE for each satellite $SV_i$ is related to the pseudo-range/ $c$ modulo the "GANSS Code Phase Ambiguity", or modulo 1 ms (the length of the C/A code period) in case of GPS L1 C/A signal measurements. For the formation of pseudo-ranges, the integer number of milliseconds to be added to each code-phase measurement has to be determined first. Since 1 ms corresponds to a travelled distance of 300 km, the number of integer ms can be found with the help of reference location and satellite ephemeris. The distance between the reference location and each satellite $SV_i$ at the time of measurement is calculated, and the integer number of milliseconds to be added to the UE code phase measurements is obtained. + +### Step 2: Correction of pseudo-ranges for the GNSS-GNSS time offsets + +In case the UE reports measurements for more than a single GNSS, the pseudo-ranges are corrected for the time offsets between the GNSSs relative to the selected reference time using the GNSS-GNSS time offsets available at the system simulator: + +$$\rho_{GNSS_{m,i}} \equiv \rho_{GNSS_{m,i}} - c \cdot (t_{GNSS_k} - t_{GNSS_m}),$$ + +where $\rho_{GNSS_{m,i}}$ is the measured pseudo-range of satellite $i$ of GNSS $_m$ . The system time $t_{GNSS_k}$ of GNSS $_k$ is the reference time frame, and $(t_{GNSS_k} - t_{GNSS_m})$ is the available GNSS-GNSS time offset, and $c$ is the speed of light. + +### Step 3: Formation of weighting matrix + +The UE reported "Code Phase RMS Error" and/or "Pseudorange RMS Error" values are used to calculate the weighting matrix for the WLS algorithm described in [16]. According to 3GPP TS 25.331 [14], the encoding for these fields is a 6 bit value that consists of a 3 bit mantissa, $X_i$ and a 3 bit exponent, $Y_i$ for each $SV_i$ of GNSS $_j$ : + +$$w_{GNSS_{j,i}} = \text{RMSError} = 0.5 \times \left(1 + \frac{X_i}{8}\right) 2^{Y_i}$$ + +The weighting Matrix **W** is defined as a diagonal matrix containing the estimated variances calculated from the "Code Phase RMS Error" and/or "Pseudorange RMS Error" values: + +$$W = \text{diag}\{1/w_{\text{GNSS},1,1}^2, 1/w_{\text{GNSS},1,2}^2, \dots, 1/w_{\text{GNSS},1,n}^2, \dots, 1/w_{\text{GNSS},m,1}^2, 1/w_{\text{GNSS},m,2}^2, \dots, 1/w_{\text{GNSS},m,l}^2\}$$ + +### Step 4: WLS position solution + +The WLS position solution is described in e.g., [16] and usually requires the following steps: + +- 1) Computation of satellite locations at time of transmission using the ephemeris parameters and user algorithms defined in the relevant ICD of the particular GNSS. The satellite locations are transformed into WGS-84 reference frame, if needed. +- 2) Computation of clock correction parameters using the parameters and algorithms as defined in the relevant ICD of the particular GNSS. +- 3) Computation of atmospheric delay corrections using the parameters and algorithms defined in the relevant ICD of the particular GNSS for the ionospheric delay, and using the Gupta model defined in [17] p. 121 equation (2) for the tropospheric delay. For GNSSs which do not natively provide ionospheric correction models (e.g., GLONASS), the ionospheric delay is determined using the available ionospheric model (see subclause F.2) adapted to the particular GNSS frequency. +- 4) The WLS position solution starts with an initial estimate of the user state (position and clock offset). The Reference Location is used as initial position estimate. The following steps are required: + - a) Calculate geometric range (corrected for Earth rotation) between initial location estimate and each satellite included in the UE measurement report. + - b) Predict pseudo-ranges for each measurement including clock and atmospheric biases as calculated in 1) to 3) above and defined in the relevant ICD of the particular GNSS and [16]. + - c) Calculate difference between predicted and measured pseudo-ranges $\Delta\rho$ . + - d) Calculate the "Geometry Matrix" **G** as defined in [16]: + +$$G \equiv \begin{bmatrix} -\hat{\mathbf{i}}_{\text{GNSS},1,1}^T & 1 \\ -\hat{\mathbf{i}}_{\text{GNSS},1,2}^T & 1 \\ \vdots & \vdots \\ -\hat{\mathbf{i}}_{\text{GNSS},1,n}^T & 1 \\ \vdots & \vdots \\ -\hat{\mathbf{i}}_{\text{GNSS},m,1}^T & 1 \\ -\hat{\mathbf{i}}_{\text{GNSS},m,2}^T & 1 \\ \vdots & \vdots \\ -\hat{\mathbf{i}}_{\text{GNSS},m,l}^T & 1 \end{bmatrix} \text{ with } \hat{\mathbf{i}}_{\text{GNSS},m,i} \equiv \frac{\mathbf{r}_{\text{sGNSS},m,i} - \hat{\mathbf{r}}_u}{|\mathbf{r}_{\text{sGNSS},m,i} - \hat{\mathbf{r}}_u|} \text{ where } \mathbf{r}_{\text{sGNSS},m,i} \text{ is the satellite position vector for SV}_i \text{ of GNSS}_m \text{ (calculated in 1) above), and } \hat{\mathbf{r}}_u \text{ is the estimate of the user location.}$$ + +- e) Calculate the WLS solution according to [16]: + +$$\Delta\hat{\mathbf{x}} = (G^T W G)^{-1} G^T W \Delta\rho$$ + +- f) Adding the $\Delta\hat{\mathbf{x}}$ to the initial state estimate gives an improved estimate of the state vector: + +$$\hat{\mathbf{x}} \rightarrow \hat{\mathbf{x}} + \Delta\hat{\mathbf{x}}.$$ + +- 5) This new state vector $\hat{\mathbf{x}}$ can be used as new initial estimate and the procedure is repeated until the change in $\hat{\mathbf{x}}$ is sufficiently small. + +### Step 5: Transformation from Cartesian coordinate system to Geodetic coordinate system + +The state vector $\hat{\mathbf{x}}$ calculated in Step 4 contains the UE position in ECEF Cartesian coordinates together with the UE receiver clock bias relative to the selected GNSS system time. Only the user position is of further interest. It is usually desirable to convert from ECEF coordinates $x_u, y_u, z_u$ to geodetic latitude $\phi$ , longitude $\lambda$ and altitude $h$ on the WGS84 reference ellipsoid. + +### **Step 6: Calculation of "2-D Position Errors"** + +The latitude $\varphi$ / longitude $\lambda$ obtained after Step 5 is used to calculate the 2-D position error. + +# Annex G (informative): Change history + +| Date | Meeting | Document | CR num | Rev | Comment | Version old | Version New | +|---------|------------|-----------|--------|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------| +| 2013-11 | RAN4#69 | R4-136754 | | | A-BDS TS 25.17x (A-BDS TDD) Skeleton | | 0.0.1 | +| 2014-02 | RAN4#70bis | R4-142207 | | | Approved text proposals in the following document was implemented:
R4-141092 Text Proposals for TS 25.173 on introduction BDS to A-GANSS of TDD mode of UTRA | 0.0.1 | 0.1.0 | +| 2014-03 | RAN4#71 | R4-142654 | | | Approved text proposals in the following document was implemented:
R4-142209 Text Proposals for TS 25.173 section 5 and Annex D/E/F | 0.1.0 | 0.2.0 | +| | | | | | Approved text proposals in the following document was implemented:
R4-142655 Text Proposals to TS 25.173 version 0.2.0 | 0.2.0 | 0.3.0 | +| 2014-06 | RP-64 | | | | Presentation to plenary for approval | 0.3.0 | 1.0.0 | +| 2014-06 | RP-64 | | | | TR Approved by the plenary | 1.0.0 | 12.0.0 | +| 2014-12 | RP-66 | RP-142151 | 001 | | Correction on BDS satellites number | 12.0.0 | 12.1.0 | +| 2014-12 | RP-66 | RP-142151 | 002 | | Editorial modification of symbols and abbreviations in 25.173 | 12.0.0 | 12.1.0 | +| 2016-01 | SP-70 | - | - | - | Update to Rel-13 version (MCC) | 12.1.0 | 13.0.0 | +| 2017-03 | RP-75 | - | - | - | Update to Rel-14 version (MCC) | 13.0.0 | 14.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2018-06 | SA#80 | - | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-06 | SA#88 | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25202/18f841ac4f2ef28f34a026f1bdc5af9a_img.jpg b/marked/Rel-16/25_series/25202/18f841ac4f2ef28f34a026f1bdc5af9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b92433f405c62bb165b394b6756ec8bfa47e8d9 --- /dev/null +++ b/marked/Rel-16/25_series/25202/18f841ac4f2ef28f34a026f1bdc5af9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6c9418eaab2b45fa6d2e7ccf8e79397d9239c7048e99a9470e3fd6ad039d31c +size 18362 diff --git a/marked/Rel-16/25_series/25202/2396add2849eccefcbcfbe1c7142a253_img.jpg b/marked/Rel-16/25_series/25202/2396add2849eccefcbcfbe1c7142a253_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c208196a9e484119db5b561e0efae36071243c8b --- /dev/null +++ b/marked/Rel-16/25_series/25202/2396add2849eccefcbcfbe1c7142a253_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21c5ac054a5cf2316f700cf1216aa9347d2b6a54115ef747258ff64ff7ff4b9e +size 51132 diff --git a/marked/Rel-16/25_series/25202/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/25_series/25202/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f009bae6addb64c4525e3c9994b48c246b69968 --- /dev/null +++ b/marked/Rel-16/25_series/25202/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96033e95bb44fd2ae7d2b9a52376ab15226b1a3c0cabf71d2545a26a846550cf +size 107898 diff --git a/marked/Rel-16/25_series/25202/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/25_series/25202/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba5ad8e7f9e3055808425865b1bdf09892535d17 --- /dev/null +++ b/marked/Rel-16/25_series/25202/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:501e43b999a4af6ed7dce5c22d3899c53f91308a7b57c7ad389d286a87eaf010 +size 107612 diff --git a/marked/Rel-16/25_series/25202/a289b64f80c6df506c0c55d553fc4496_img.jpg b/marked/Rel-16/25_series/25202/a289b64f80c6df506c0c55d553fc4496_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9366fdd8660552c4f7e334997c9bd0203264c650 --- /dev/null +++ b/marked/Rel-16/25_series/25202/a289b64f80c6df506c0c55d553fc4496_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83c532c6789eb11d9cd7b495e0b9409d88a3e0fb8cb51cd9f847a1f9df99135d +size 55878 diff --git a/marked/Rel-16/25_series/25202/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/25_series/25202/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4eaa2e5a8d0d91d44ccdf5b285fd40bc039bf312 --- /dev/null +++ b/marked/Rel-16/25_series/25202/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ef3f4b7296076b2bbcc2617a6d0704cb132c8b9e8d1f653c416cc63fd3110c7 +size 109559 diff --git a/marked/Rel-16/25_series/25202/raw.md b/marked/Rel-16/25_series/25202/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..473458d39086915bcc2b9eaa5fcd54ff912ef505 --- /dev/null +++ b/marked/Rel-16/25_series/25202/raw.md @@ -0,0 +1,1114 @@ + + + + + + +# Contents + +| | | +|---------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 7 | +| 4 Background and introduction..... | 7 | +| 5 Requirements ..... | 8 | +| 6 Physical layer structure ..... | 8 | +| 6.0 Services offered to higher layers..... | 8 | +| 6.1 Frame structure..... | 8 | +| 6.2 Burst structure ..... | 8 | +| 6.3 Midambles..... | 9 | +| 6.4 Coding and Modulation..... | 12 | +| 6.5 Scrambling Codes ..... | 12 | +| 6.6 Synchronisation Codes..... | 13 | +| 6.7 Transmit diversity ..... | 13 | +| 6.9 Indicator Channels..... | 13 | +| 6.9.1 Paging Indicator Channel (PICH) ..... | 13 | +| 6.9.2 MBMS Indicator Channel (MICH)..... | 13 | +| 6.10 Mapping of transport channels to physical channels ..... | 13 | +| 7 Physical layer procedures..... | 15 | +| 7.1 Power Control ..... | 15 | +| 7.2 Timing Advance..... | 15 | +| 7.3 HSDPA procedures ..... | 15 | +| 7.4 Synchronisation procedures ..... | 15 | +| 7.5 RACH procedures ..... | 15 | +| 7.6 Discontinuous transmission (DTX) procedure..... | 15 | +| 7.7 Downlink transmit diversity procedure..... | 15 | +| 7.8 DSCH procedure ..... | 15 | +| 7.9 Macrodiversity procedure ..... | 15 | +| 7.10 IPDL procedure ..... | 16 | +| 7.11 E-DCH procedures ..... | 16 | +| 8 UE capabilities ..... | 16 | +| 9 Layer 2/3 protocol aspects ..... | 16 | +| 9.1 Protocol architecture ..... | 16 | +| 9.2 Signalling ..... | 16 | +| 9.2.1 General ..... | 16 | +| 9.2.2 L2/MAC differences..... | 16 | +| 9.2.3 L2/RRC differences..... | 16 | +| 9.3 HSDPA related issues ..... | 17 | +| 9.4 Mobility..... | 17 | +| 9.5 Idle Mode Procedures..... | 17 | +| 9.6 E-DCH related issues ..... | 17 | +| 10 Iub/Iur aspects ..... | 17 | +| 10.1 Impacts on Iub/Iur interfaces – general aspects ..... | 17 | +| 10.1.1 Timing advance and Rx Timing Deviation ..... | 17 | +| 10.1.2 Paging ..... | 18 | +| 10.1.3 DSCH Power Control from the RNC ..... | 18 | +| 10.2 Impacts on Iub/Iur control plane protocols ..... | 18 | +| 10.3 Impacts on Iub/Iur user plane protocols ..... | 18 | + +| | | | +|------------------------|-----------------------------------------------------|----| +| 11 | Radio aspects..... | 19 | +| 11.1 | UE radio transmission and reception ..... | 19 | +| 11.1.1 | Transmitter characteristics..... | 19 | +| 11.1.1.1 | Transmit power ..... | 19 | +| 11.1.1.2 | Output RF spectrum emissions ..... | 19 | +| 11.1.1.2.1 | Occupied bandwidth..... | 19 | +| 11.1.1.2.2 | Out of band emission..... | 19 | +| 11.1.1.2.2.1 | Spectrum emission mask ..... | 19 | +| 11.1.1.2.2.2 | Adjacent Channel Leakage power Ratio (ACLR)..... | 20 | +| 11.1.1.2.2.3 | Spurious emissions ..... | 20 | +| 11.1.2 | Receiver characteristics ..... | 20 | +| 11.1.2.1 | Reference sensitivity level..... | 20 | +| 11.1.2.1.1 | Minimum Requirement ..... | 20 | +| 11.1.2.2 | Adjacent Channel Selectivity (ACS) ..... | 20 | +| 11.1.2.2.1 | Minimum Requirement ..... | 20 | +| 11.1.2.3 | Blocking characteristics ..... | 21 | +| 11.1.2.3.1 | Minimum Requirement ..... | 21 | +| 11.1.2.4 | Spurious response ..... | 22 | +| 11.1.2.4.1 | Minimum Requirement ..... | 22 | +| 11.1.2.5 | Spurious emissions ..... | 22 | +| 11.1.2.5.1 | Minimum Requirement ..... | 23 | +| 11.2 | Base station radio transmission and reception ..... | 23 | +| 11.2.1 | Transmitter characteristics..... | 23 | +| 11.2.1.1 | Base station output power..... | 23 | +| 11.2.1.2 | Output RF spectrum emissions ..... | 23 | +| 11.2.1.2.1 | Occupied bandwidth..... | 23 | +| 11.2.1.2.2 | Out of band emission..... | 23 | +| 11.2.1.2.2.1 | Spectrum emission mask ..... | 23 | +| 11.2.1.2.2.2 | Adjacent Channel Leakage power Ratio (ACLR)..... | 25 | +| 11.2.1.2.2.2.1 | Minimum requirement ..... | 25 | +| 11.2.1.2.2.3 | Spurious emissions ..... | 26 | +| 11.2.2 | Receiver characteristics ..... | 26 | +| 11.2.2.1 | Reference sensitivity level..... | 26 | +| 11.2.2.1.1 | Minimum requirement..... | 26 | +| 11.2.2.2 | Adjacent Channel Selectivity (ACS) ..... | 26 | +| 11.2.2.2.1 | Minimum requirement..... | 26 | +| 11.2.2.3 | Blocking characteristics ..... | 27 | +| 11.2.2.3.1 | Minimum requirement..... | 27 | +| 11.2.2.3.2 | Collocation with GSM900 and/or DCS 1800 ..... | 28 | +| 11.2.2.4 | Spurious emissions ..... | 28 | +| 11.2.2.4.1 | Minimum requirement..... | 29 | +| Annex A (informative): | Change history..... | 30 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd 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 is the overall technical specification for the support of the 7.68Mcps TDD option in UTRA. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 25.895 (V6.0.0): "Analysis of higher chip rates for UTRA TDD evolution". +- [2] 3GPP TS 25.221: "Physical channels and mapping of transport channels onto physical channels (TDD)". +- [3] 3GPP TS 25.222: "Multiplexing and channel coding (TDD)". +- [4] 3GPP TS 25.223: "Spreading and modulation (TDD)". +- [5] 3GPP TS 25.224: "Physical layer procedures (TDD)". +- [6] 3GPP TS 25.225: "Physical layer; Measurements (TDD)". +- [7] 3GPP TS 25.301: "Radio Interface Protocol Architecture". +- [8] 3GPP TS 25.306: "UE Radio Access capabilities". +- [9] 3GPP TS 25.321: "Medium Access Control (MAC) protocol specification". +- [10] 3GPP TS 25.102: "User Equipment (UE) radio transmission and reception (TDD)". +- [11] 3GPP TS 25.105 "UTRAN (BS) TDD; Radio transmission and reception". +- [12] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [12] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [12]. + +(void) + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +(void) + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [12] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [12]. + +| | | +|----------|------------------------------------------------------| +| BCH | Broadcast Channel | +| CCPCH | Common Control Physical Channel | +| DCH | Dedicated Channel | +| DPCH | Dedicated Physical Channel | +| DSCH | Downlink Shared Channel | +| E-AGCH | E-DCH Absolute Grant Channel | +| E-DCH | Enhanced Dedicated Channel | +| E-HICH | E-DCH Hybrid ARQ Indicator Channel | +| E-PUCH | E-DCH Physical Uplink Channel | +| E-RUCCH | E-DCH Random Access Uplink Control Channel | +| FACH | Forward Access Channel | +| HS-DSCH | High Speed Downlink Shared Channel | +| HS-PDSCH | High Speed Physical Downlink Shared Channel | +| HS-SCCH | Shared Control Channel for HS-DSCH | +| HS-SICH | Shared Information Channel for HS-DSCH | +| P-CCPCH | Primary CCPCH | +| PCH | Paging Channel | +| PDSCH | Physical Downlink Shared Channel | +| PI | Paging Indicator (value calculated by higher layers) | +| PICH | Page Indicator Channel | +| PRACH | Physical Random Access Channel | +| PUSCH | Physical Uplink Shared Channel | +| RACH | Random Access Channel | +| S-CCPCH | Secondary CCPCH | +| SCH | Synchronisation Channel | +| TrCH | Transport Channel | +| USCH | Uplink Shared Channel | + +# --- 4 Background and introduction + +The 7.68Mcps TDD option is an evolution of the 3.84Mcps TDD option to a higher chip rate. There exists a great degree of commonality between the 3.84Mcps TDD option and the 7.68Mcps TDD option. Nevertheless, there are many aspects of the 7.68Mcps TDD option that require separate specification to the 3.84Mcps TDD option. The following aspects are specified at a high level in this document: + +- Physical layer structure; +- Physical layer procedures; +- UE capabilities; +- Layer 2/3 protocol aspects; +- Iub / Iur aspects; +- Radio aspects; + +# 5 Requirements + +- The 7.68Mcps TDD option shall provide significant enhancements in terms of user experience (throughput and delay) and/or capacity (at least to the extent shown in [1]). +- Full mobility shall be supported, i.e., mobility should be supported for high-speed UE cases also, but optimisation should be for low-speed to medium-speed scenarios. +- It is highly desirable for the 7.68Mcps TDD option to maintain commonality with the 3.84Mcps TDD option. New features shall therefore provide significant incremental gain for an acceptable complexity. +- The UE and network complexity shall be minimised for a given level of system performance. +- The impact on current releases in terms of both protocol and hardware perspectives shall be taken into account. + +# 6 Physical layer structure + +## 6.0 Services offered to higher layers + +The 7.68Mcps TDD option supports an identical set of transport channels and indicators to the 3.84Mcps TDD option. + +## 6.1 Frame structure + +The 7.68Mcps TDD option frame is of length 10ms and consists of 15 timeslots of duration $5120 \cdot T_c$ , where $T_c$ is the chip duration ( $T_c = 1 / 7.68 \cdot 10^6 = 130.2\text{ns}$ ). Any timeslot in the frame can be either uplink or downlink. At least one timeslot in the frame is assigned to the uplink and at least one timeslot in the frame is assigned to the downlink. The frame structure is shown in Figure 6.1.1. + +![Illustrative diagram of spectrum emission mask showing power density vs frequency separation.](2396add2849eccefcbcfbe1c7142a253_img.jpg) + +The diagram shows the spectrum emission mask for the 7.68Mcps TDD option. The x-axis represents 'Frequency separation Δf from the carrier [MHz]' with markers at 5.0, 5.2, 6.0, 7.0, 15.0, and f\_offset\_max. The y-axis represents 'Power density in 1 MHz [dBm]' ranging from -40 to -15. The mask is defined by several power levels: P = 43 dBm, P = 39 dBm, and P = 31 dBm. The power density is highest (P = 43 dBm) between 5.0 and 5.2 MHz, then decreases to P = 39 dBm between 5.2 and 6.0 MHz, and further decreases to P = 31 dBm for frequencies above 6.0 MHz up to 15.0 MHz. Beyond 15.0 MHz, the power density remains at P = 31 dBm until f\_offset\_max. + +Illustrative diagram of spectrum emission mask showing power density vs frequency separation. + +Figure 6.1.1: The 7.68Mcps TDD option frame structure + +## 6.2 Burst structure + +The 7.68Mcps burst consists of two data field portions, a midamble portion containing a training sequence and a guard period as shown in Figure 6.2.1. Several bursts can be transmitted at the same time where each burst uses a different OVSF channelisation code, but the same scrambling code. + +![Diagram of 7.68Mcps TDD option burst structure showing Data field, Midamble, Data field, and guard period.](18f841ac4f2ef28f34a026f1bdc5af9a_img.jpg) + +The diagram illustrates the structure of a 7.68Mcps TDD option burst. It is a horizontal bar divided into four segments: 'Data field', 'Midamble', 'Data field', and 'guard period'. The total duration of the burst is indicated as $5120 \cdot T_c$ . + +Diagram of 7.68Mcps TDD option burst structure showing Data field, Midamble, Data field, and guard period. + +Figure 6.2.1: 7.68Mcps TDD option burst structure + +Three burst types are specified: burst types 1, 2 and 3. The maximum number of training sequences supported in burst types 1 and 3 is either 4, 8 or 16 depending on cell configuration and either 4 or 8 for burst type 2 depending on cell configuration. The lengths of the fields within each burst are defined in Table 6.2.1. + +**Table 6.2.1: Number of chips within fields of the 7.68Mcps burst** + +| Field | Burst Type 1 | Burst Type 2 | Burst Type 3 | +|--------------|--------------|--------------|--------------| +| Data field 1 | 1952 | 2208 | 1952 | +| Midamble | 1024 | 512 | 1024 | +| Data field 2 | 1952 | 2208 | 1760 | +| Guard Period | 192 | 192 | 384 | + +On the downlink, a spreading factor of 32 is supported. Additionally for DPCH, PDSCH and HS-PDSCH, a spreading factor of 1 is supported on the downlink. + +On the uplink, spreading factors of 1, 2, 4, 8, 16 and 32 are supported for DPCH, PUSCH and E-PUCH. PRACH and E-RUCCH only support spreading factors 16 and 32 and HS-SICH only supports spreading factor 32. + +The spreading factors and burst types supported for different physical channels are defined in Table 6.2.2. + +**Table 6.2.2: Spreading factors and burst types supported by physical channels** + +| Physical channel | Supported spreading factors | Supported burst types | +|------------------|-----------------------------|-----------------------| +| UL DPCH | 1, 2, 4, 8, 16, 32 | 1, 2, 3 | +| DL DPCH | 1, 32 | 1, 2 | +| P-CCPCH | 32 | 1 | +| S-CCPCH | 32 | 1, 2 | +| PRACH | 16, 32 | 3 | +| PUSCH | 1, 2, 4, 8, 16, 32 | 1, 2, 3 | +| PDSCH | 1, 32 | 1, 2 | +| HS-PDSCH | 1, 32 | 1, 2 | +| HS-SCCH | 32 | 1, 2 | +| HS-SICH | 32 | 1, 2 | +| E-PUCH | 1, 2, 4, 8, 16, 32 | 1, 2, 3 | +| E-AGCH | 32 | 1, 2 | +| E-HICH | 32 | 1, 2 | +| E-RUCCH | 16, 32 | 3 | + +Transmission of TPC and TFCI are performed in accordance with the general procedures used for the existing 3.84 Mcps TDD option. Due to the maximum spreading factor being increased from 16 (3.84Mcps) to 32 (7.68Mcps), usage of SF16 for TPC/TFCI is replaced with SF32 where appropriate. + +## 6.3 Midambles + +Midambles for burst types 1, 2 and 3 are created using the method applied for 3.84Mcps TDD. The basic midamble code for burst types 1 and 3 is of length 912; for burst type 2 the basic midamble code is of length 456. + +Default, common and UE specific midamble modes are supported in the 7.68Mcps TDD option. The characteristics of these midamble allocations at 7.68Mcps are identical to their characteristics at 3.84Mcps. The number of active channelisation codes is signaled via midamble through an extension of the scheme applied at 3.84Mcps TDD (the extension accounts for the higher spreading factor supported at 7.68Mcps). + +Midamble transmit powers are allocated as for 3.84Mcps TDD. + +The association between midambles and channelisation codes for burst types 1, 2 and 3 are as shown in figure 6.3.1 for $K_{\text{cell}} = 16$ , figure 6.3.2 for $K_{\text{cell}} = 8$ and figure 6.3.3 for $K_{\text{cell}} = 4$ . Secondary channelisation codes are marked with a \*. + +These associations apply both for UL and DL. + +![A hierarchical tree diagram showing the association of Midambles to Spreading Codes for KCell = 16. The tree starts with m^(1) - c_1^(1) at the root, branching into m^(1) - c_2^(1) and m^(5) - c_2^(2). It further branches through multiple levels of midamble and code identifiers (c_4, c_8, c_16, c_32) to reach 32 terminal nodes at the far right.](e6df2733626a85205c1db682e6259c46_img.jpg) + +``` + +graph LR + root("m(1) - c1(1)") --> n1("m(1) - c2(1)") + root --> n2("m(5) - c2(2)") + + n1 --> n1_1("m(1) - c4(1)") + n1 --> n1_2("m(3) - c4(2)") + + n2 --> n2_1("m(5) - c4(3)") + n2 --> n2_2("m(7) - c4(4)") + + n1_1 --> n1_1_1("m(1) - c8(1)") + n1_1 --> n1_1_2("m(2) - c8(2)") + + n1_2 --> n1_2_1("m(3) - c8(3)") + n1_2 --> n1_2_2("m(6) - c8(4)") + + n2_1 --> n2_1_1("m(5) - c8(5)") + n2_1 --> n2_1_2("m(4) - c8(6)") + + n2_2 --> n2_2_1("m(7) - c8(7)") + n2_2 --> n2_2_2("m(8) - c8(8)") + + n1_1_1 --> n1_1_1_1("m(1) - c16(1)") + n1_1_1 --> n1_1_1_2("m(9) - c16(2)") + + n1_1_2 --> n1_1_2_1("m(2) - c16(3)") + n1_1_2 --> n1_1_2_2("m(10) - c16(4)") + + n1_2_1 --> n1_2_1_1("m(3) - c16(5)") + n1_2_1 --> n1_2_1_2("m(11) - c16(6)") + + n1_2_2 --> n1_2_2_1("m(6) - c16(7)") + n1_2_2 --> n1_2_2_2("m(14) - c16(8)") + + n2_1_1 --> n2_1_1_1("m(5) - c16(9)") + n2_1_1 --> n2_1_1_2("m(13) - c16(10)") + + n2_1_2 --> n2_1_2_1("m(4) - c16(11)") + n2_1_2 --> n2_1_2_2("m(12) - c16(12)") + + n2_2_1 --> n2_2_1_1("m(7) - c16(13)") + n2_2_1 --> n2_2_1_2("m(15) - c16(14)") + + n2_2_2 --> n2_2_2_1("m(8) - c16(15)") + n2_2_2 --> n2_2_2_2("m(16) - c16(16)") + + n1_1_1_1 --> t1("m(1) - c32(1)") + n1_1_1_1 --> t2("m(1) - c32(2)*") + n1_1_1_2 --> t3("m(9) - c32(3)") + n1_1_1_2 --> t4("m(9) - c32(4)*") + + n1_1_2_1 --> t5("m(2) - c32(5)") + n1_1_2_1 --> t6("m(2) - c32(6)*") + n1_1_2_2 --> t7("m(10) - c32(7)") + n1_1_2_2 --> t8("m(10) - c32(8)*") + + n1_2_1_1 --> t9("m(3) - c32(9)") + n1_2_1_1 --> t10("m(3) - c32(10)*") + n1_2_1_2 --> t11("m(11) - c32(11)") + n1_2_1_2 --> t12("m(11) - c32(12)*") + + n1_2_2_1 --> t13("m(6) - c32(13)") + n1_2_2_1 --> t14("m(6) - c32(14)*") + n1_2_2_2 --> t15("m(14) - c32(15)") + n1_2_2_2 --> t16("m(14) - c32(16)*") + + n2_1_1_1 --> t17("m(5) - c32(17)") + n2_1_1_1 --> t18("m(5) - c32(18)*") + n2_1_1_2 --> t19("m(13) - c32(19)") + n2_1_1_2 --> t20("m(13) - c32(20)*") + + n2_1_2_1 --> t21("m(4) - c32(21)") + n2_1_2_1 --> t22("m(4) - c32(22)*") + n2_1_2_2 --> t23("m(12) - c32(23)") + n2_1_2_2 --> t24("m(12) - c32(24)*") + + n2_2_1_1 --> t25("m(7) - c32(25)") + n2_2_1_1 --> t26("m(7) - c32(26)*") + n2_2_1_2 --> t27("m(15) - c32(27)") + n2_2_1_2 --> t28("m(15) - c32(28)*") + + n2_2_2_1 --> t29("m(8) - c32(29)") + n2_2_2_1 --> t30("m(8) - c32(30)*") + n2_2_2_2 --> t31("m(16) - c32(31)") + n2_2_2_2 --> t32("m(16) - c32(32)*") + +``` + +The diagram illustrates a binary tree structure representing the association of Midambles to Spreading Codes for $K_{Cell} = 16$ . The tree starts with the root node $m^{(1)} - c_1^{(1)}$ . It branches into two main paths: $m^{(1)} - c_2^{(1)}$ and $m^{(5)} - c_2^{(2)}$ . Each of these paths further branches into two nodes, and so on, following a binary tree structure. The nodes are labeled with midamble identifiers ( $m$ ) and code identifiers ( $c$ ) with superscripts indicating the level or index. The terminal nodes on the right are labeled with $m$ and $c_{32}$ identifiers, such as $m^{(1)} - c_{32}^{(1)}$ , $m^{(1)} - c_{32}^{(2)*}$ , $m^{(9)} - c_{32}^{(3)}$ , $m^{(9)} - c_{32}^{(4)*}$ , and so on, up to $m^{(16)} - c_{32}^{(32)*}$ . + +A hierarchical tree diagram showing the association of Midambles to Spreading Codes for KCell = 16. The tree starts with m^(1) - c\_1^(1) at the root, branching into m^(1) - c\_2^(1) and m^(5) - c\_2^(2). It further branches through multiple levels of midamble and code identifiers (c\_4, c\_8, c\_16, c\_32) to reach 32 terminal nodes at the far right. + +Figure 6.3.1: Association of Midambles to Spreading Codes for $K_{Cell} = 16$ + +![A hierarchical tree diagram showing the association of Midambles to Spreading Codes for K_Cell = 8. The tree starts with m^(1) - c_1^(1) at the root, branching into m^(1) - c_2^(1) and m^(5) - c_2^(2). It further branches through various levels of midambles (m) and codes (c) until it reaches the final spreading codes (c_32) at the leaf nodes. The labels include superscripts for the midamble index and parentheses for the code index, with some codes marked with an asterisk.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +The diagram illustrates the hierarchical association of Midambles to Spreading Codes for $K_{Cell} = 8$ . The tree structure is as follows: + +- Root:** $m^{(1)} - c_1^{(1)}$ + - Level 1:** $m^{(1)} - c_2^{(1)}$ and $m^{(5)} - c_2^{(2)}$ + - From $m^{(1)} - c_2^{(1)}$ :** + - $m^{(1)} - c_4^{(1)}$ + - $m^{(1)} - c_8^{(1)}$ + - $m^{(1)} - c_{16}^{(1)}$ → $m^{(1)} - c_{32}^{(1)}$ , $m^{(1)} - c_{32}^{(2)*}$ + - $m^{(1)} - c_{16}^{(2)*}$ → $m^{(1)} - c_{32}^{(3)*}$ , $m^{(1)} - c_{32}^{(4)*}$ + - $m^{(2)} - c_8^{(2)}$ + - $m^{(2)} - c_{16}^{(3)}$ → $m^{(2)} - c_{32}^{(5)}$ , $m^{(2)} - c_{32}^{(6)*}$ + - $m^{(2)} - c_{16}^{(4)*}$ → $m^{(2)} - c_{32}^{(7)*}$ , $m^{(2)} - c_{32}^{(8)*}$ + - $m^{(3)} - c_4^{(2)}$ + - $m^{(3)} - c_8^{(3)}$ + - $m^{(3)} - c_{16}^{(5)}$ → $m^{(3)} - c_{32}^{(9)}$ , $m^{(3)} - c_{32}^{(10)*}$ + - $m^{(3)} - c_{16}^{(6)*}$ → $m^{(3)} - c_{32}^{(11)*}$ , $m^{(3)} - c_{32}^{(12)*}$ + - $m^{(6)} - c_8^{(4)}$ + - $m^{(6)} - c_{16}^{(7)}$ → $m^{(6)} - c_{32}^{(13)}$ , $m^{(6)} - c_{32}^{(14)*}$ + - $m^{(6)} - c_{16}^{(8)*}$ → $m^{(6)} - c_{32}^{(15)*}$ , $m^{(6)} - c_{32}^{(16)*}$ + - From $m^{(5)} - c_2^{(2)}$ :** + - $m^{(5)} - c_4^{(3)}$ + - $m^{(5)} - c_8^{(5)}$ + - $m^{(5)} - c_{16}^{(9)}$ → $m^{(5)} - c_{32}^{(17)}$ , $m^{(5)} - c_{32}^{(18)*}$ + - $m^{(5)} - c_{16}^{(10)*}$ → $m^{(5)} - c_{32}^{(19)*}$ , $m^{(5)} - c_{32}^{(20)*}$ + - $m^{(4)} - c_8^{(6)}$ + - $m^{(4)} - c_{16}^{(11)}$ → $m^{(4)} - c_{32}^{(21)}$ , $m^{(4)} - c_{32}^{(22)*}$ + - $m^{(4)} - c_{16}^{(12)*}$ → $m^{(4)} - c_{32}^{(23)*}$ , $m^{(4)} - c_{32}^{(24)*}$ + - $m^{(7)} - c_4^{(4)}$ + - $m^{(7)} - c_8^{(7)}$ + - $m^{(7)} - c_{16}^{(13)}$ → $m^{(7)} - c_{32}^{(25)}$ , $m^{(7)} - c_{32}^{(26)*}$ + - $m^{(7)} - c_{16}^{(14)*}$ → $m^{(7)} - c_{32}^{(27)*}$ , $m^{(7)} - c_{32}^{(28)*}$ + - $m^{(8)} - c_8^{(8)}$ + - $m^{(8)} - c_{16}^{(15)}$ → $m^{(8)} - c_{32}^{(29)}$ , $m^{(8)} - c_{32}^{(30)*}$ + - $m^{(8)} - c_{16}^{(16)*}$ → $m^{(8)} - c_{32}^{(31)*}$ , $m^{(8)} - c_{32}^{(32)*}$ + +A hierarchical tree diagram showing the association of Midambles to Spreading Codes for K\_Cell = 8. The tree starts with m^(1) - c\_1^(1) at the root, branching into m^(1) - c\_2^(1) and m^(5) - c\_2^(2). It further branches through various levels of midambles (m) and codes (c) until it reaches the final spreading codes (c\_32) at the leaf nodes. The labels include superscripts for the midamble index and parentheses for the code index, with some codes marked with an asterisk. + +Figure 6.3.2: Association of Midambles to Spreading Codes for $K_{Cell} = 8$ + +![Figure 6.3.3: Association of Midambles to Spreading Codes for K_Cell = 4. The diagram shows a hierarchical tree structure starting from a root node m^{(1)} - c_1^{(1)}. It branches into two main paths: m^{(1)} - c_2^{(1)} and m^{(5)} - c_2^{(2)}. The m^{(1)} - c_2^{(1)} path further branches into m^{(1)} - c_4^{(1)} and m^{(3)} - c_4^{(2)}. The m^{(1)} - c_4^{(1)} path branches into m^{(1)} - c_8^{(1)} and m^{(1)} - c_8^{(2)*}. The m^{(1)} - c_8^{(1)} path branches into m^{(1)} - c_{16}^{(1)} and m^{(1)} - c_{16}^{(2)*}. The m^{(1)} - c_{16}^{(1)} path branches into m^{(1)} - c_{32}^{(1)} and m^{(1)} - c_{32}^{(2)*}. The m^{(1)} - c_{16}^{(2)*} path branches into m^{(1)} - c_{32}^{(3)*} and m^{(1)} - c_{32}^{(4)*}. The m^{(1)} - c_8^{(2)*} path branches into m^{(1)} - c_{16}^{(3)*} and m^{(1)} - c_{16}^{(4)*}. The m^{(1)} - c_{16}^{(3)*} path branches into m^{(1)} - c_{32}^{(5)*} and m^{(1)} - c_{32}^{(6)*}. The m^{(1)} - c_{16}^{(4)*} path branches into m^{(1)} - c_{32}^{(7)*} and m^{(1)} - c_{32}^{(8)*}. The m^{(3)} - c_4^{(2)} path branches into m^{(3)} - c_8^{(3)} and m^{(3)} - c_8^{(4)*}. The m^{(3)} - c_8^{(3)} path branches into m^{(3)} - c_{16}^{(5)} and m^{(3)} - c_{16}^{(6)*}. The m^{(3)} - c_{16}^{(5)} path branches into m^{(3)} - c_{32}^{(9)} and m^{(3)} - c_{32}^{(10)*}. The m^{(3)} - c_{16}^{(6)*} path branches into m^{(3)} - c_{32}^{(11)*} and m^{(3)} - c_{32}^{(12)*}. The m^{(3)} - c_8^{(4)*} path branches into m^{(3)} - c_{16}^{(7)*} and m^{(3)} - c_{16}^{(8)*}. The m^{(3)} - c_{16}^{(7)*} path branches into m^{(3)} - c_{32}^{(13)*} and m^{(3)} - c_{32}^{(14)*}. The m^{(3)} - c_{16}^{(8)*} path branches into m^{(3)} - c_{32}^{(15)*} and m^{(3)} - c_{32}^{(16)*}. The m^{(5)} - c_2^{(2)} path branches into m^{(5)} - c_4^{(3)} and m^{(7)} - c_4^{(4)}. The m^{(5)} - c_4^{(3)} path branches into m^{(5)} - c_8^{(5)} and m^{(5)} - c_8^{(6)*}. The m^{(5)} - c_8^{(5)} path branches into m^{(5)} - c_{16}^{(9)} and m^{(5)} - c_{16}^{(10)*}. The m^{(5)} - c_{16}^{(9)} path branches into m^{(5)} - c_{32}^{(17)} and m^{(5)} - c_{32}^{(18)*}. The m^{(5)} - c_{16}^{(10)*} path branches into m^{(5)} - c_{32}^{(19)*} and m^{(5)} - c_{32}^{(20)*}. The m^{(5)} - c_8^{(6)*} path branches into m^{(5)} - c_{16}^{(11)*} and m^{(5)} - c_{16}^{(12)*}. The m^{(5)} - c_{16}^{(11)*} path branches into m^{(5)} - c_{32}^{(21)*} and m^{(5)} - c_{32}^{(22)*}. The m^{(5)} - c_{16}^{(12)*} path branches into m^{(5)} - c_{32}^{(23)*} and m^{(5)} - c_{32}^{(24)*}. The m^{(7)} - c_4^{(4)} path branches into m^{(7)} - c_8^{(7)} and m^{(7)} - c_8^{(8)*}. The m^{(7)} - c_8^{(7)} path branches into m^{(7)} - c_{16}^{(13)} and m^{(7)} - c_{16}^{(14)*}. The m^{(7)} - c_{16}^{(13)} path branches into m^{(7)} - c_{32}^{(25)} and m^{(7)} - c_{32}^{(26)*}. The m^{(7)} - c_{16}^{(14)*} path branches into m^{(7)} - c_{32}^{(27)*} and m^{(7)} - c_{32}^{(28)*}. The m^{(7)} - c_8^{(8)*} path branches into m^{(7)} - c_{16}^{(15)*} and m^{(7)} - c_{16}^{(16)*}. The m^{(7)} - c_{16}^{(15)*} path branches into m^{(7)} - c_{32}^{(29)*} and m^{(7)} - c_{32}^{(30)*}. The m^{(7)} - c_{16}^{(16)*} path branches into m^{(7)} - c_{32}^{(31)*} and m^{(7)} - c_{32}^{(32)*}.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +Figure 6.3.3: Association of Midambles to Spreading Codes for K\_Cell = 4. The diagram shows a hierarchical tree structure starting from a root node m^{(1)} - c\_1^{(1)}. It branches into two main paths: m^{(1)} - c\_2^{(1)} and m^{(5)} - c\_2^{(2)}. The m^{(1)} - c\_2^{(1)} path further branches into m^{(1)} - c\_4^{(1)} and m^{(3)} - c\_4^{(2)}. The m^{(1)} - c\_4^{(1)} path branches into m^{(1)} - c\_8^{(1)} and m^{(1)} - c\_8^{(2)\*}. The m^{(1)} - c\_8^{(1)} path branches into m^{(1)} - c\_{16}^{(1)} and m^{(1)} - c\_{16}^{(2)\*}. The m^{(1)} - c\_{16}^{(1)} path branches into m^{(1)} - c\_{32}^{(1)} and m^{(1)} - c\_{32}^{(2)\*}. The m^{(1)} - c\_{16}^{(2)\*} path branches into m^{(1)} - c\_{32}^{(3)\*} and m^{(1)} - c\_{32}^{(4)\*}. The m^{(1)} - c\_8^{(2)\*} path branches into m^{(1)} - c\_{16}^{(3)\*} and m^{(1)} - c\_{16}^{(4)\*}. The m^{(1)} - c\_{16}^{(3)\*} path branches into m^{(1)} - c\_{32}^{(5)\*} and m^{(1)} - c\_{32}^{(6)\*}. The m^{(1)} - c\_{16}^{(4)\*} path branches into m^{(1)} - c\_{32}^{(7)\*} and m^{(1)} - c\_{32}^{(8)\*}. The m^{(3)} - c\_4^{(2)} path branches into m^{(3)} - c\_8^{(3)} and m^{(3)} - c\_8^{(4)\*}. The m^{(3)} - c\_8^{(3)} path branches into m^{(3)} - c\_{16}^{(5)} and m^{(3)} - c\_{16}^{(6)\*}. The m^{(3)} - c\_{16}^{(5)} path branches into m^{(3)} - c\_{32}^{(9)} and m^{(3)} - c\_{32}^{(10)\*}. The m^{(3)} - c\_{16}^{(6)\*} path branches into m^{(3)} - c\_{32}^{(11)\*} and m^{(3)} - c\_{32}^{(12)\*}. The m^{(3)} - c\_8^{(4)\*} path branches into m^{(3)} - c\_{16}^{(7)\*} and m^{(3)} - c\_{16}^{(8)\*}. The m^{(3)} - c\_{16}^{(7)\*} path branches into m^{(3)} - c\_{32}^{(13)\*} and m^{(3)} - c\_{32}^{(14)\*}. The m^{(3)} - c\_{16}^{(8)\*} path branches into m^{(3)} - c\_{32}^{(15)\*} and m^{(3)} - c\_{32}^{(16)\*}. The m^{(5)} - c\_2^{(2)} path branches into m^{(5)} - c\_4^{(3)} and m^{(7)} - c\_4^{(4)}. The m^{(5)} - c\_4^{(3)} path branches into m^{(5)} - c\_8^{(5)} and m^{(5)} - c\_8^{(6)\*}. The m^{(5)} - c\_8^{(5)} path branches into m^{(5)} - c\_{16}^{(9)} and m^{(5)} - c\_{16}^{(10)\*}. The m^{(5)} - c\_{16}^{(9)} path branches into m^{(5)} - c\_{32}^{(17)} and m^{(5)} - c\_{32}^{(18)\*}. The m^{(5)} - c\_{16}^{(10)\*} path branches into m^{(5)} - c\_{32}^{(19)\*} and m^{(5)} - c\_{32}^{(20)\*}. The m^{(5)} - c\_8^{(6)\*} path branches into m^{(5)} - c\_{16}^{(11)\*} and m^{(5)} - c\_{16}^{(12)\*}. The m^{(5)} - c\_{16}^{(11)\*} path branches into m^{(5)} - c\_{32}^{(21)\*} and m^{(5)} - c\_{32}^{(22)\*}. The m^{(5)} - c\_{16}^{(12)\*} path branches into m^{(5)} - c\_{32}^{(23)\*} and m^{(5)} - c\_{32}^{(24)\*}. The m^{(7)} - c\_4^{(4)} path branches into m^{(7)} - c\_8^{(7)} and m^{(7)} - c\_8^{(8)\*}. The m^{(7)} - c\_8^{(7)} path branches into m^{(7)} - c\_{16}^{(13)} and m^{(7)} - c\_{16}^{(14)\*}. The m^{(7)} - c\_{16}^{(13)} path branches into m^{(7)} - c\_{32}^{(25)} and m^{(7)} - c\_{32}^{(26)\*}. The m^{(7)} - c\_{16}^{(14)\*} path branches into m^{(7)} - c\_{32}^{(27)\*} and m^{(7)} - c\_{32}^{(28)\*}. The m^{(7)} - c\_8^{(8)\*} path branches into m^{(7)} - c\_{16}^{(15)\*} and m^{(7)} - c\_{16}^{(16)\*}. The m^{(7)} - c\_{16}^{(15)\*} path branches into m^{(7)} - c\_{32}^{(29)\*} and m^{(7)} - c\_{32}^{(30)\*}. The m^{(7)} - c\_{16}^{(16)\*} path branches into m^{(7)} - c\_{32}^{(31)\*} and m^{(7)} - c\_{32}^{(32)\*}. + +**Figure 6.3.3: Association of Midambles to Spreading Codes for $K_{\text{Cell}} = 4$** + +For PRACH and E-RUCCH, up to 16 midambles and channelisation codes may be supported. The training sequences, i.e. midambles, of different users active in the same time slot are time shifted versions of a basic midamble code, $m_1$ , or a second basic midamble code, $m_2$ , which is a time inverted version of the basic midamble code $m_1$ . A fixed association exists between PRACH/E-RUCCH midambles and channelisation codes. + +## 6.4 Coding and Modulation + +Multiplexing and channel coding is aligned with 3.84Mcps TDD with the exception that physical channel sequence numbering and the coding of the channelisation code set information on HS-SCCH and E-AGCH shall account for the support of SF32 at 7.68Mcps. + +## 6.5 Scrambling Codes + +The binary scrambling code, $c_{7.68}^n$ , for cell parameter $n$ in the 7.68Mcps TDD option is formed from the concatenation of the binary scrambling codes $c_{3.84}^n$ and $c_{3.84}^{(n+2) \bmod 128}$ shown in Annex A of [4]. + +## 6.6 Synchronisation Codes + +The synchronisation codes for the 7.68Mcps TDD option are formed by repetition coding of the 3.84Mcps TDD synchronisation code words. Unique modulation sequences are applied to these code words that enable the UE to determine the code group, frame alignment and chip rate of the cell. + +The synchronization channel (SCH) is constructed in an identical manner to the construction at 3.84Mcps. The relationship between code group, $n$ , and $t_{offset,n}$ at 7.68Mcps is: + +$$t_{offset,n} =$$ + +## 6.7 Transmit diversity + +Support for beamforming and transmit diversity are aligned with the 3.84Mcps TDD option. + +## 6.8 Measurements + +## 6.9 Indicator Channels + +### 6.9.1 Paging Indicator Channel (PICH) + +The paging indicator channel is spread at SF32, but in other respects is identical to the 3.84Mcps TDD PICH [2]. + +The PICH block may comprise up to $N_{PICH} = 8$ frames. The PCH block may comprise up to $2 \times N_{PCH} = 2 \times 16$ frames. + +### 6.9.2 MBMS Indicator Channel (MICH) + +The MBMS indicator channel is spread at SF32, but in other respects is identical to the 3.84Mcps TDD MICH [2]. + +## 6.10 Mapping of transport channels to physical channels + +In the 7.68Mcps TDD option, transport channels are mapped onto physical channels according to figure 6.10.1. + +| Transport Channels | Physical Channels | +|---------------------------|--------------------------------------------------------| +| DCH _____ | Dedicated Physical Channel (DPCH) | +| BCH _____ | Primary Common Control Physical Channel (P-CCPCH) | +| FACH _____ | Secondary Common Control Physical Channel (S-CCPCH) | +| PCH _____ | | +| RACH _____ | Physical Random Access Channel (PRACH) | +| USCH _____ | Physical Uplink Shared Channel (PUSCH) | +| DSCH _____ | Physical Downlink Shared Channel (PDSCH) | +| | Paging Indicator Channel (PICH) | +| | MBMS Indication Channel (MICH) | +| | Synchronisation Channel (SCH) | +| HS-DSCH _____ | High Speed Physical Downlink Shared Channel (HS-PDSCH) | +| | Shared Control Channel for HS-DSCH (HS-SCCH) | +| | Shared Information Channel for HS-DSCH (HS-SICH) | +| E-DCH _____ | E-DCH Physical Uplink Channel (E-PUCH) | +| | E-DCH Random Access Uplink Control Channel (E-RUCCH) | +| | E-DCH Absolute Grant Channel (E-AGCH) | +| | E-DCH Hybrid ARQ Indicator Channel (E-HICH) | + +**Figure 6.10.1: Transport channel to physical channel mapping** + +The mapping between DCH, BCH, FACH, USCH and DSCH transport channels to physical channels is identical to the mapping at 3.84Mcps TDD. + +The mapping between the RACH transport channel and the PRACH physical channel is identical to the mapping at 3.84Mcps TDD. + +The mapping between the HS-DSCH transport channel and HS-PDSCH physical channels is identical to the mapping at 3.84Mcps TDD. The association and timing between HS-SCCH, HS-DSCH and HS-SICH is identical to the association and timing at 3.84Mcps TDD with the exception that the UE must monitor up to a maximum of eight HS-SCCH ( $M=8$ ). + +The mapping between the E-DCH transport channel and E-PUCH physical channels is identical to the mapping at 3.84Mcps TDD. The association and timing between E-AGCH, E-PUCH and E-HICH is identical to the association and timing at 3.84Mcps TDD with the exception that up to two channelisation codes for E-HICH are supported for the 7.68Mcps option. + +The mapping of E-DCH control information to E-RUCCH when E-PUCH resources are unavailable is identical to that for 3.84Mcps TDD. + +# 7 Physical layer procedures + +## 7.1 Power Control + +Transmitter power control, both on the uplink and downlink, is aligned with that of 3.84Mcps TDD. + +## 7.2 Timing Advance + +The timing advance architecture is the same as for 3.84Mcps TDD. The required timing advance, 'UL Timing Advance' $TA_{ul}$ will be represented as a 7 bit number (0-127) and shall be the multiplier of 4 chips which is nearest to the required timing advance. + +PUSCH, UL DPCH and HS-SICH are timing advanced. PRACH and E-RUCCH are not timing advanced. + +## 7.3 HSDPA procedures + +The HS-DSCH procedure is aligned with 3.84Mcps TDD. When SCTD antenna diversity is applied to HS-PDSCH on the beacon channel, the presence of channelisation code $c_{32}^{(k=1)}$ shall implicitly indicate presence of channelisation code $c_{32}^{(k=2)}$ . + +## 7.4 Synchronisation procedures + +The synchronization procedures are aligned with 3.84Mcps TDD. + +## 7.5 RACH procedures + +The RACH procedure is aligned with 3.84Mcps TDD. However, the use of higher layer signaling to indicate that in some frames a timeslot shall be blocked for RACH uplink transmission is not supported. + +## 7.6 Discontinuous transmission (DTX) procedure + +The DTX procedure is aligned with that of 3.84Mcps TDD. + +## 7.7 Downlink transmit diversity procedure + +The downlink transmit diversity procedure is aligned with that of 3.84Mcps TDD. In Space Code Transmit Diversity mode the data sequence is spread with the channelisation codes $c_{32}^{(k=1)}$ and $c_{32}^{(k=2)}$ , the spread sequence on code $c_{32}^{(k=2)}$ is then transmitted on the diversity antenna. + +## 7.8 DSCH procedure + +Higher layer signaling is used to indicate to the UE the need for PDSCH detection. Physical layer signaling is not used to indicate to the UE the need for PDSCH detection. + +## 7.9 Macrodiversity procedure + +The macrodiversity procedure is aligned with that of 3.84Mcps TDD. + +## 7.10 IPDL procedure + +The IPDL procedure is aligned with that of 3.84Mcps TDD. + +## 7.11 E-DCH procedures + +The E-DCH procedures are aligned with those of 3.84Mcps TDD with modifications to accommodate SF32 for the E-PUCH code hopping procedure and the E-PUCH power control procedure. + +# 8 UE capabilities + +UE capabilities for the 7.68 Mcps TDD mode are based on those for 3.84 Mcps TDD. The capabilities for 7.68Mcps TDD account for the higher number of physical channels supported and additionally support higher peak bit rates. The minimum MBMS capability at 7.68Mcps is twice the minimum capability at 3.84Mcps. The detailed UE capabilities for 7.68Mcps TDD are described in [8]. + +# 9 Layer 2/3 protocol aspects + +## 9.1 Protocol architecture + +The protocol architecture for 7.68 Mcps TDD is the same as the protocol architecture for 3.84 Mcps TDD. Section 5.1 of [7] provides an overview of the radio interface protocol architecture. + +## 9.2 Signalling + +### 9.2.1 General + +There are signalling differences between 7.68 Mcps TDD and 3.84 Mcps TDD. These differences concern L2/MAC and L3/RRC (see Section 5.1 of [7]) only. L2/RLC, L2/BMC, L2/PDCP and L3 U-plane information are not impacted. + +### 9.2.2 L2/MAC differences + +The L2/MAC differences between 7.68 Mcps TDD and 3.84 Mcps TDD are due to the support of a higher capability HSDPA UE at 7.68 Mcps (20.4Mbps) and a higher capability E-DCH UE at 7.68 Mcps (17.7Mbps). The L2/MAC differences concern: + +- the maximum number of PDUs transmitted in a single TTI (636 at 7.68 Mcps compared to 318 for 3.84 Mcps TDD). +- HSDPA transport block size signalling. The maximum transport block size that can be signalled at 7.68 Mcps is twice that at 3.84 Mcps. A new table and formula for transport block size signalling for 7.68 Mcps TDD HS-DSCH is included in [9]. +- E-DCH transport block size signalling. The maximum transport block size that can be signalled at 7.68 Mcps is approximately twice that at 3.84 Mcps. A new table and formula for transport block size signalling for 7.68 Mcps TDD E-DCH is included in [9]. + +### 9.2.3 L2/RRC differences + +The L2/RRC differences concern: + +**Use of SF 32:** The signalling is extended to include support for SF32. The 7.68 Mcps cell will be configured to use SF 16 or 32 for PRACH and E-RUCCH rather than SF 8 and 16 as 3.84 Mcps + +**Open Loop Power Control:** Configuration of a cell for use of SF 16 or 32 with respect to the PRACH impacts calculation of the uplink transmit power for PRACH and requires the UE to add 3dB to the RACH Constant Value in the equation: + +$$P_{\text{PRACH}} = L_{\text{PCCPCH}} + I_{\text{BTS}} + \text{PRACH Constant value}$$ + +for the case where RACH Spreading Factor = 16. + +The same applies for open loop power control of E-RUCCH. + +**Capability Update Requirement:** A new IE "UE radio access 7.68 Mcps TDD capability update requirement" is used. + +**Uplink Timing Advance:** A different Uplink Timing Advance IE is required at 7.68 Mcps to account for the number of bits used to signal timing advance at 7.68 Mcps. A number of RRC messages are impacted due to the use of a different Uplink Timing Advance IE for 7.68 Mcps TDD to 3.84 Mcps TDD. + +**DL Physical Channel Capability:** The physical channel capability at 7.68 Mcps is extended in order to account for the greater number of physical channels supported at 7.68 Mcps. + +**Burst Types and Midambles:** Signalling related to burst types is modified since burst type 2 at 7.68 Mcps supports $K_{\text{cell}}$ of 4 or 8. + +## 9.3 HSDPA related issues + +The highest UE capability at 7.68Mcps is double that at 3.84Mcps, hence the maximum transport block size and the maximum number of PDUs that can be transmitted in a single TTI are double that of 3.84 Mcps. The range of UE capabilities is extended and the maximum UE capability for 7.68 Mcps is 20.4 Mbits/s. + +## 9.4 Mobility + +Inter RAT and intra RAT handover for 7.68 Mcps TDD is as for 3.84 Mcps TDD with handover between 3.84 Mcps TDD and 7.68 Mcps TDD cells also supported. Bands a), b), c), a + b), a + c), b + c) and a + b + c) can be configured for 7.68 Mcps TDD or 3.84 Mcps TDD or 1.28 Mcps TDD. + +## 9.5 Idle Mode Procedures + +Idle mode procedures are as for 3.84 Mcps TDD. + +## 9.6 E-DCH related issues + +The highest UE capability at 7.68Mcps is approximately double that at 3.84Mcps, hence the maximum transport block size and the maximum number of PDUs that can be transmitted in a single TTI are increased with respect to that of 3.84 Mcps. The range of UE capabilities is extended and the maximum UE capability for 7.68 Mcps is 17.7 Mbits/s. + +# --- 10 Iub/Iur aspects + +## 10.1 Impacts on Iub/Iur interfaces – general aspects + +### 10.1.1 Timing advance and Rx Timing Deviation + +The timing advance algorithm (in RRM, at the RNC) uses Rx Timing Deviation measurements made by the Node B and passed to the RNC in frame protocols. At 3.84 Mcps the resolution is 4 chips. The timing advance determined by RRM is signalled to the UE (RRC). + +In addition, the Node B can be configured to take more accurate Rx Timing Deviation measurements of a UE, which are sent to the RNC as dedicated measurements. At 3.84 Mcps the resolution of these is 0.0625 chips. These accurate measurements can be used in location (they are passed to the location system using the PCAP protocol). + +Strategy for 7.68 Mcps : + +Timing advance & Rx Timing Deviation over FP + +- > 4 chip resolution +- > same dynamic range as 3.84 Mcps (in secs) + +Rx Timing Deviation, dedicated measurement + +- > 0.0625 chip resolution giving greater measurement accuracy +- > same dynamic range as 3.84 Mcps (in secs) + +### 10.1.2 Paging + +For the 7.68Mcps option, the maximum number of paging indicators per paging block should be doubled to accommodate the greater number of users that may be supported by the 10 MHz carrier. To achieve this: + +- the number of PICH blocks per paging block (NPICH) is extended from {2,4} to {2,4,8} +- the number of PCH blocks per paging block (NPCH) is extended from {1..8} to {1..16}. + +Consequently, a unique value range for the PI-bitmap needs to be defined for 7.68 Mcps. + +### 10.1.3 DSCH Power Control from the RNC + +In 3.84 Mcps TDD, the PDSCH may be power controlled from the RNC by sending a transmit power level value in the DSCH DATA FRAME that carries DSCH transport blocks to the Node B. For 7.68 Mcps, the same method can be used and this has been agreed by RAN1. Since the transmit power level is expressed relative to the maximum transmit power, no changes are needed to accommodate 7.68Mcps. + +## 10.2 Impacts on Iub/Iur control plane protocols + +There are a number of changes to RNSAP, PCAP & NBAP protocols to incorporate: + +- **Use of SF 32:** The signalling is extended to include support for SF32. The 7.68 Mcps cell will be configured to use SF 16 or 32 for PRACH and E-RUCCH rather than SF 8 and 16 as 3.84 Mcps +- **Burst Types and Midambles:** Signalling related to burst types is modified since burst type 2 at 7.68Mcps supports $K_{cell}$ of 4 or 8. +- **Number of physical channels:** the SF32 change implies an increase in the number of physical channels that may be supported. +- **Measurements:** changes are introduced for Rx Timing Deviation and SFN-SFN measurements. +- **Cell Synchronisation:** this procedure is not supported. + +## 10.3 Impacts on Iub/Iur user plane protocols + +Specifications 25.425, 25.427 and 25.435 are modified to include 7.68Mcps operation in a similar fashion to 3.84 Mcps. Changes are also needed to accommodate the different rx timing deviation and timing advance signalling for 7.68Mcps compared to 3.84Mcps (see Section 10.1 above). The paging indicator bit-map is also revised (see Section 10.1 above). + +# --- 11 Radio aspects + +## 11.1 UE radio transmission and reception + +### 11.1.1 Transmitter characteristics + +#### 11.1.1.1 Transmit power + +Common with 3.84Mcps TDD option. + +#### 11.1.1.2 Output RF spectrum emissions + +##### 11.1.1.2.1 Occupied bandwidth + +Occupied bandwidth is a measure of the bandwidth containing 99% of the total integrated power of the transmitted spectrum, centred on the assigned channel frequency. The occupied channel bandwidth shall be less than 10 MHz based on a chip rate of 7.68 Mcps. + +##### 11.1.1.2.2 Out of band emission + +Out of band emissions are unwanted emissions immediately outside the nominal channel resulting from the modulation process and non-linearity in the transmitter but excluding spurious emissions. This out of band emission limit is specified in terms of a spectrum emission mask and adjacent channel leakage power ratio (ACLR). + +###### 11.1.1.2.2.1 Spectrum emission mask + +The spectrum emission mask of the UE applies to frequencies, which are between 5 MHz and 25MHz from the UE centre carrier frequency. The out of channel emission is specified relative to the RRC filtered mean power of the UE carrier. The power of any UE emission shall not exceed the levels specified in Table 11.1.1. + +**Table 11.1.1: Spectrum Emission Mask of higher chip rate reference configuration** + +| $\Delta f^*$ in MHz | Minimum requirement | Measurement bandwidth | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|-----------------------| +| 5.0 – 7.0 | $\left\{ -38 - 7.5 \cdot \left( \frac{\Delta f}{\text{MHz}} - 5.0 \right) \right\} \text{ dBc}$ | 30 kHz ** | +| 7.0 – 15 | $\left\{ -38 - 0.5 \cdot \left( \frac{\Delta f}{\text{MHz}} - 7.0 \right) \right\} \text{ dBc}$ | 1 MHz *** | +| 15.0 – 17.0 | $\left\{ -42 - 5.0 \cdot \left( \frac{\Delta f}{\text{MHz}} - 15.0 \right) \right\} \text{ dBc}$ | 1 MHz *** | +| 17.0 – 25.0 | -53 dBc | 1 MHz *** | +| * $\Delta f$ is the separation between the carrier frequency and the centre of the measuring filter. | | | +| ** The first and last measurement position with a 30 kHz filter is at $\Delta f$ equals to 5.015 MHz and 6.985 MHz | | | +| *** The first and last measurement position with a 1 MHz filter is at $\Delta f$ equals to 7.5 MHz and 24.5 MHz. As a general rule, the resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. To improve measurement accuracy, sensitivity and efficiency, the resolution bandwidth can be different from the measurement bandwidth. When the resolution bandwidth is smaller than the measurement bandwidth, the result should be integrated over the measurement bandwidth in order to obtain the equivalent noise bandwidth of the measurement bandwidth. | | | +| The lower limit shall be -47dBm/7.68 MHz or the minimum requirement presented in this table which ever is the higher. | | | + +###### 11.1.1.2.2.2 Adjacent Channel Leakage power Ratio (ACLR) + +Adjacent Channel Leakage power Ratio (ACLR) is the ratio of the RRC filtered mean power centered on the assigned channel frequency to the RRC filtered mean power centered on an adjacent channel frequency. + +If the adjacent channel RRC filtered mean power is greater than -50dBm measured with a 3.84 Mcps RRC filter then the ACLR shall be higher than the value specified in Table 11.1.2. + +**Table 11.1.2: UE ACLR of higher chip rate reference configuration** + +| Power Class | adjacent channel | Chip Rate for RRC Measurement Filter | ACLR limit | +|-------------|---------------------------|--------------------------------------|------------| +| 2, 3 | UE channel $\pm$ 7.5 MHz | 3.84 MHz | 33 dB | +| 2, 3 | UE channel $\pm$ 12.5 MHz | 3.84 MHz | 43 dB | +| 2, 3 | UE channel $\pm$ 20.0 MHz | 7.68 MHz | 43 dB | + +###### NOTE: + +- 1) The requirement shall still be met in the presence of switching transients. +- 2) The ACLR requirements reflect what can be achieved with present state of the art technology. + +###### 11.1.1.2.2.3 Spurious emissions + +The spurious emissions limits shall be common with 3.84 Mcps TDD option and shall be applicable for offsets greater than 25 MHz from the UE centre frequency. + +### 11.1.2 Receiver characteristics + +#### 11.1.2.1 Reference sensitivity level + +The reference sensitivity level is the minimum mean power received at the UE antenna port at which the BIT Error Ratio BER shall not exceed a specific value. + +##### 11.1.2.1.1 Minimum Requirement + +The BER shall not exceed 0.001 for the parameters specified in Table 11.1.3. + +**Table 11.1.3: Test parameters for reference sensitivity (7.68 Mcps TDD Option)** + +| Parameter | Level | Unit | +|--------------------------------|-------|--------------| +| $\frac{\sum DPCH\_Ec}{I_{or}}$ | 0 | dB | +| $\hat{I}_{or}$ | -105 | dBm/7.68 MHz | + +#### 11.1.2.2 Adjacent Channel Selectivity (ACS) + +Adjacent Channel Selectivity is a measure of a receiver's ability to receive a wanted signal at its assigned channel frequency in the presence of adjacent channel signal at a given frequency offset from the centre frequency of the assigned channel. ACS is the ratio of the receive filter attenuation on the assigned channel frequency to the receiver filter attenuation on the adjacent channel(s). + +##### 11.1.2.2.1 Minimum Requirement + +The ACS shall be better than the value indicated in Table 11.1.4 for the test parameters specified in Table 11.1.5 where the BER shall not exceed 0.001 + +**Table 11.1.4: Adjacent Channel Selectivity (7.68 Mcps TDD Option)** + +| Power Class | Unit | ACS | +|-------------|------|-----| +| 2 | dB | 33 | +| 3 | dB | 33 | + +**Table 11.1.5: Test parameters for Adjacent Channel Selectivity (7.68 Mcps TDD Option)** + +| Parameter | Unit | Level | +|---------------------------------------|--------------|--------------| +| $\frac{\sum DPCH\_Ec}{I_{or}}$ | dB | 0 | +| $\hat{I}_{or}$ | dBm/7.68 MHz | -91 | +| $I_{ac}$ mean power (modulated) | dBm | -52 | +| $F_{uw}$ offset (3.84 Mcps Modulated) | MHz | +7.5 or -7.5 | +| $F_{uw}$ offset (7.68 Mcps Modulated) | MHz | +10 or -10 | + +#### 11.1.2.3 Blocking characteristics + +The blocking characteristics is a measure of the receiver ability to receive a wanted signal at its assigned channel frequency in the presence of an unwanted interferer on frequencies other than those of the spurious response or the adjacent channels without this unwanted input signal causing a degradation of the performance of the receiver beyond a specified limit. The blocking performance shall apply at all frequencies except those at which a spurious response occur. + +##### 11.1.2.3.1 Minimum Requirement + +The BER shall not exceed 0.001 for the parameters specified in table 11.1.6 and table 11.1.7. For table 11.1.7 up to 24 exceptions are allowed for spurious response frequencies in each assigned frequency channel when measured using a 1MHz step size. + +**Table 11.1.6: In-band blocking** + +| Parameter | Level | | Unit | +|----------------------------------|-------------------------------------------|-------------------------------------------|--------------| +| $\frac{\sum DPCH\_Ec}{I_{or}}$ | 0 | | dB | +| $\hat{I}_{or}$ | -102 | | dBm/7.68 MHz | +| $I_{ouu}$ mean power (modulated) | -53
(for $F_{uw}$ offset $\pm 20$ MHz) | -41
(for $F_{uw}$ offset $\pm 30$ MHz) | dBm | + +**Table 11.1.7: Out of band blocking** + +| Parameter | Band 1 | Band 2 | Band 3 | Unit | +|----------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|----------------------------------|--------------| +| $\frac{\sum DPCH\_Ec}{I_{or}}$ | 0 | 0 | 0 | dB | +| $\hat{I}_{or}$ | -102 | -102 | -102 | dBm/7.68 MHz | +| $I_{ouw}$ (CW) | -44 | -30 | -15 | dBm | +| $F_{uw}$
For operation in frequency bands as defined in subclause 5.2(a) of TS25.102 [10] | 1840 < f < 1870
1950 < f < 1980
2055 < f < 2085 | 1815 < f < 1840
2085 < f < 2110 | 1 < f < 1815
2110 < f < 12750 | MHz | +| $F_{uw}$
For operation in frequency bands as defined in subclause 5.2(b) of TS25.102 [10] | 1790 < f < 1820
2020 < f < 2050 | 1765 < f < 1790
2050 < f < 2075 | 1 < f < 1765
2075 < f < 12750 | MHz | +| $F_{uw}$
For operation in frequency bands as defined in subclause 5.2(c) of TS25.102 [10] | 1850 < f < 1880
1960 < f < 1990 | 1825 < f < 1850
1990 < f < 2015 | 1 < f < 1825
2015 < f < 12750 | MHz | +| 1. | For operation referenced in 5.2(a) of TS25.102 [10], from 1870 < f < 1900 MHz, 1920 < f < 1950 MHz, 1980 < f < 2010 MHz and 2025 < f < 2055 MHz, the appropriate in-band blocking in table 11.1.6 or adjacent channel selectivity in section 11.1.4 shall be applied. | | | | +| 2. | For operation referenced in 5.2(b) of TS25.102 [10], from 1820 < f < 1850 MHz and 1990 < f < 2020 MHz, the appropriate in-band blocking in table 11.1.6 or adjacent channel selectivity in section 11.1.4 shall be applied. | | | | +| 3. | For operation referenced in 5.2(c) of TS25.102 [10], from 1880 < f < 1910 MHz and 1930 < f < 1960 MHz, the appropriate in-band blocking in table 11.1.6 or adjacent channel selectivity in section 11.1.4 shall be applied. | | | | + +#### 11.1.2.4 Spurious response + +Spurious response is a measure of the receiver's ability to receive a wanted signal on its assigned channel frequency without exceeding a given degradation due to the presence of an unwanted CW interfering signal at any other frequency at which a response is obtained i.e. for which the blocking limit is not met. + +##### 11.1.2.4.1 Minimum Requirement + +The BER shall not exceed 0.001 for the parameters specified in Table 11.1.8. + +**Table 11.1.8: Spurious Response** + +| Parameter | Level | Unit | +|--------------------------------|-------------------------------|--------------| +| $\frac{\sum DPCH\_Ec}{I_{or}}$ | 0 | dB | +| $\hat{I}_{or}$ | -102 | dBm/7.68 MHz | +| $I_{ouw}$ (CW) | -44 | dBm | +| $F_{uw}$ | Spurious response frequencies | MHz | + +#### 11.1.2.5 Spurious emissions + +The Spurious Emissions Power is the power of emissions generated or amplified in a receiver that appear at the UE antenna connector. + +##### 11.1.2.5.1 Minimum Requirement + +The power of any spurious emission shall not exceed: + +**Table 11.1.9: Receiver spurious emission requirements** + +| Band | Maximum level | Measurement Bandwidth | Note | +|----------------------------------------------------------------------------|---------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| 30 MHz – 1 GHz | -57 dBm | 100 kHz | | +| 1 GHz – 1.9 GHz and
1.92 GHz – 2.01 GHz and
2.025 GHz – 2.11 GHz | -47 dBm | 1 MHz | With the exception of frequencies between 25MHz below the first carrier frequency and 25MHz above the last carrier frequency used by the UE. | +| 1.9 GHz – 1.92 GHz and
2.01 GHz – 2.025 GHz and
2.11 GHz – 2.170 GHz | -57 dBm | 7.68 MHz | With the exception of frequencies between 25MHz below the first carrier frequency and 25MHz above the last carrier frequency used by the UE. | +| 2.170 GHz – 12.75 GHz | -47 dBm | 1 MHz | | + +## 11.2 Base station radio transmission and reception + +### 11.2.1 Transmitter characteristics + +#### 11.2.1.1 Base station output power + +Common with 3.84Mcps TDD option. + +#### 11.2.1.2 Output RF spectrum emissions + +##### 11.2.1.2.1 Occupied bandwidth + +Occupied bandwidth is a measure of the bandwidth containing 99% of the total integrated power for transmitted spectrum and is centered on the assigned channel frequency. The occupied channel bandwidth is less than 10 MHz based on a chip rate of 7.68 Mcps. + +##### 11.2.1.2.2 Out of band emission + +Out of band emissions are unwanted emissions immediately outside the channel bandwidth resulting from the modulation process and non-linearity in the transmitter but excluding spurious emissions. This out of band emission requirement is specified both in terms of a spectrum emission mask and adjacent channel power ratio for the transmitter. + +###### 11.2.1.2.2.1 Spectrum emission mask + +The mask defined in Table 11.2.1 to 11.2.4 below may be mandatory in certain regions. In other regions this mask may not be applied. + +For regions where this clause applies, the requirement shall be met by a base station transmitting on a single RF carrier configured in accordance with the manufacturer's specification. Emissions shall not exceed the maximum level specified in tables 11.2.1 to 11.2.4 for the appropriate BS maximum output power, in the frequency range from $\Delta f = 5$ MHz to $\Delta f_{\max}$ from the carrier frequency, where: + +- $\Delta f$ is the separation between the carrier frequency and the nominal -3dB point of the measuring filter closest to the carrier frequency. +- $f_{\text{offset}}$ is the separation between the carrier frequency and the center frequency of the measuring filter.- + $f_{\text{offsetmax}}$ is either 25 MHz or the offset to the UMTS Tx band edge as defined in TS25.105 [11], whichever is the greater. +- $\Delta f_{\max}$ is equal to $f_{\text{offsetmax}}$ minus half of the bandwidth of the measurement filter. + +![Illustrative diagram of spectrum emission mask. The graph shows Power density in 30kHz [dBm] on the left y-axis (ranging from -40 to -15) and Power density in 1 MHz [dBm] on the right y-axis (ranging from -25 to 0). The x-axis represents Frequency separation Δf from the carrier [MHz] with markers at 5.0, 5.2, 6.0, 7.0, 15.0, and f_offset_max. The mask is defined by three power levels: P = 43 dBm (top line), P = 39 dBm (middle line), and P = 31 dBm (bottom line). The mask starts at -17 dBm for 5 MHz ≤ Δf < 5.2 MHz, then decreases linearly to -29 dBm at 6.015 MHz, and then drops to -16 dBm for 6 MHz ≤ Δf ≤ Δf_max. The right y-axis is shifted such that 0 dBm corresponds to -15 dBm on the left axis.](a289b64f80c6df506c0c55d553fc4496_img.jpg) + +Illustrative diagram of spectrum emission mask. The graph shows Power density in 30kHz [dBm] on the left y-axis (ranging from -40 to -15) and Power density in 1 MHz [dBm] on the right y-axis (ranging from -25 to 0). The x-axis represents Frequency separation Δf from the carrier [MHz] with markers at 5.0, 5.2, 6.0, 7.0, 15.0, and f\_offset\_max. The mask is defined by three power levels: P = 43 dBm (top line), P = 39 dBm (middle line), and P = 31 dBm (bottom line). The mask starts at -17 dBm for 5 MHz ≤ Δf < 5.2 MHz, then decreases linearly to -29 dBm at 6.015 MHz, and then drops to -16 dBm for 6 MHz ≤ Δf ≤ Δf\_max. The right y-axis is shifted such that 0 dBm corresponds to -15 dBm on the left axis. + +Illustrative diagram of spectrum emission mask + +Figure 11.2.1: Spectrum emission mask + +Table 11.2.1: Spectrum emission mask values, BS maximum output power $P \geq 43$ dBm + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------------------------------------------------------------------|-----------------------| +| $5 \text{ MHz} \leq \Delta f < 5.2 \text{ MHz}$ | $5.015 \text{ MHz} \leq f\_offset < 5.215 \text{ MHz}$ | -17 dBm | 30 kHz | +| $5.2 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $5.215 \text{ MHz} \leq f\_offset < 6.015 \text{ MHz}$ | $-17 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 5.215 \right) \text{ dB}$ | 30 kHz | +| (see note) | $6.015 \text{ MHz} \leq f\_offset < 6.5 \text{ MHz}$ | -29 dBm | 30 kHz | +| $6 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $6.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -16 dBm | 1 MHz | + +Table 11.2.2: Spectrum emission mask values, BS maximum output power $39 \leq P < 43$ dBm + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------------------------------------------------------------------|-----------------------| +| $5 \text{ MHz} \leq \Delta f < 5.2 \text{ MHz}$ | $5.015 \text{ MHz} \leq f\_offset < 5.215 \text{ MHz}$ | -17 dBm | 30 kHz | +| $5.2 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $5.215 \text{ MHz} \leq f\_offset < 6.015 \text{ MHz}$ | $-17 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 5.215 \right) \text{ dB}$ | 30 kHz | +| (see note) | $6.015 \text{ MHz} \leq f\_offset < 6.5 \text{ MHz}$ | -29 dBm | 30 kHz | +| $6 \text{ MHz} \leq \Delta f < 15 \text{ MHz}$ | $6.5 \text{ MHz} \leq f\_offset < 15.5 \text{ MHz}$ | -16 dBm | 1 MHz | +| $15 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $15.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $P - 59 \text{ dB}$ | 1 MHz | + +**Table 11.2.3: Spectrum emission mask values, BS maximum output power $31 \leq P < 39$ dBm** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|-----------------------| +| $5 \text{ MHz} \leq \Delta f < 5.2 \text{ MHz}$ | $5.015 \text{ MHz} \leq f\_offset < 5.215 \text{ MHz}$ | $P - 56 \text{ dB}$ | 30 kHz | +| $5.2 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $5.215 \text{ MHz} \leq f\_offset < 6.015 \text{ MHz}$ | $P - 56 \text{ dB} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 5.215 \right) \text{ dB}$ | 30 kHz | +| (see note) | $6.015 \text{ MHz} \leq f\_offset < 6.5 \text{ MHz}$ | $P - 68 \text{ dB}$ | 30 kHz | +| $6 \text{ MHz} \leq \Delta f < 15 \text{ MHz}$ | $6.5 \text{ MHz} \leq f\_offset < 15.5 \text{ MHz}$ | $P - 55 \text{ dB}$ | 1 MHz | +| $15 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $15.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | $P - 59 \text{ dB}$ | 1 MHz | + +**Table 11.2.4: Spectrum emission mask values, BS maximum output power $P < 31$ dBm** + +| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Maximum level | Measurement bandwidth | +|---------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------------------------------------------------------------------|-----------------------| +| $5 \text{ MHz} \leq \Delta f < 5.2 \text{ MHz}$ | $5.015 \text{ MHz} \leq f\_offset < 5.215 \text{ MHz}$ | -25 dBm | 30 kHz | +| $5.2 \text{ MHz} \leq \Delta f < 6 \text{ MHz}$ | $5.215 \text{ MHz} \leq f\_offset < 6.015 \text{ MHz}$ | $-25 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 5.215 \right) \text{ dB}$ | 30 kHz | +| (see note) | $6.015 \text{ MHz} \leq f\_offset < 6.5 \text{ MHz}$ | -37 dBm | 30 kHz | +| $6 \text{ MHz} \leq \Delta f < 15 \text{ MHz}$ | $6.5 \text{ MHz} \leq f\_offset < 15.5 \text{ MHz}$ | -24 dBm | 1 MHz | +| $15 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$ | $15.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$ | -28 dBm | 1 MHz | + +NOTE: This frequency range ensures that the range of values of $f\_offset$ is continuous. + +###### 11.2.1.2.2.2 Adjacent Channel Leakage power Ratio (ACLR) + +Adjacent Channel Leakage power Ratio (ACLR) is the ratio of the RRC filtered mean power centered on the assigned channel frequency to the RRC filtered mean power centered on an adjacent channel frequency. The requirements shall apply for all configurations of BS (single carrier or multi-carrier), and for all operating modes foreseen by the manufacturer's specification. + +In some cases the requirement is expressed as adjacent channel leakage power, which is the RRC filtered mean power for the given bandwidth of the victim system at the defined adjacent channel offset. + +The requirement depends on the deployment scenario. Different deployment scenarios have been defined as given below. + +###### 11.2.1.2.2.2.1 Minimum requirement + +The ACLR of a single carrier BS or a multi-carrier BS with contiguous carrier frequencies shall be higher than the value specified in Table 11.2.5. + +**Table 11.2.5: BS ACLR** + +| BS adjacent channel offset below the first or above the last carrier frequency used | Chip Rate for RRC Measurement Filter | ACLR limit | +|-------------------------------------------------------------------------------------|--------------------------------------|------------| +| 7.5 MHz | 3.84 Mcps | 45 dB | +| 12.5 MHz | 3.84 Mcps | 55 dB | +| 10.0 MHz | 7.68 Mcps | 45 dB | +| 20.0 MHz | 7.68 Mcps | 55 dB | + +If a BS provides multiple non-contiguous single carriers or multiple non-contiguous groups of contiguous single carriers, the above requirements shall be applied individually to the single carriers or group of single carriers. + +###### 11.2.1.2.2.3 Spurious emissions + +Spurious emissions are emissions which are caused by unwanted transmitter effects such as harmonics emission, parasitic emission, intermodulation products and frequency conversion products, but exclude out of band emissions. This is measured at the base station RF output port. + +The requirements shall apply whatever the type of transmitter considered (single carrier or multi carrier). It applies for all transmission modes foreseen by the manufacturer. + +The requirement applies at frequencies within the specified frequency ranges which are more than 25 MHz under the first carrier frequency used or more than 25 MHz above the last carrier frequency used. + +The mandatory requirements for Category A and Category B shall be common with 3.84 Mcps TDD option. + +### 11.2.2 Receiver characteristics + +#### 11.2.2.1 Reference sensitivity level + +The reference sensitivity level is the minimum mean power received at the antenna connector at which the BER shall not exceed the specific value indicated in section 11.2.2.1.1. + +##### 11.2.2.1.1 Minimum requirement + +The UL reference measurement channel used in the simulations of TR25.895 is the 12.2 kbps channel specified in Annex A.2.1 of TS25.105 [11] with twice the spreading factor (SF=16) and mid-amble (1024 chips). The reference sensitivity level and performance of the BS shall be as specified in Table 11.2.6. + +**Table 11.2.6: BS reference sensitivity level** + +| BS Class | Reference measurement channel data rate | BS reference sensitivity level | BER | +|---------------|-----------------------------------------|--------------------------------|----------------------------| +| Wide Area BS | 12.2 kbps | -109 dBm | BER shall not exceed 0.001 | +| Local Area BS | 12.2 kbps | -95 dBm | BER shall not exceed 0.001 | + +#### 11.2.2.2 Adjacent Channel Selectivity (ACS) + +Adjacent channel selectivity (ACS) is a measure of the receiver ability to receive a wanted signal at its assigned channel frequency in the presence of a single code CDMA modulated adjacent channel signal at a given frequency offset from the center frequency of the assigned channel. ACS is the ratio of the receiver filter attenuation on the assigned channel frequency to the receiver filter attenuation on the adjacent channel(s). + +##### 11.2.2.2.1 Minimum requirement + +The BER shall not exceed 0.001 for the parameters specified in table 11.2.7. + +**Table 11.2.7: Adjacent channel selectivity** + +| Parameter | | Level | Unit | +|-----------------------------------------|---------------|-------|------| +| Reference measurement channel data rate | | 12.2 | kbps | +| Wanted signal mean power | Wide Area BS | -103 | dBm | +| | Local Area BS | -89 | dBm | +| Interfering signal mean power | Wide Area BS | -49 | dBm | +| | Local Area BS | -35 | dBm | +| Fuw offset (Modulated) | | 10 | MHz | + +#### 11.2.2.3 Blocking characteristics + +The blocking characteristics is a measure of the receiver ability to receive a wanted signal at its assigned channel frequency in the presence of an unwanted interferer on frequencies other than those of the adjacent channels. The blocking performance requirement applies to interfering signals with center frequency within the ranges specified in the tables below, using a 1MHz step size. + +##### 11.2.2.3.1 Minimum requirement + +The static reference performance as specified in clause 11.2.2.1.1 shall be met with a wanted and an interfering signal coupled to BS antenna input using the parameters as specified in Table 11.2.8 to 11.2.10 for the Wide Area BS and as specified in Table 11.2.11 to 11.2.13 for the Local Area BS. + +**Table 11.2.8: Blocking requirements for Wide Area BS for operating bands defined in 5.2(a) of TS 25.105 [11]** + +| Centre Frequency of Interfering Signal | Interfering Signal Mean Power | Wanted Signal Mean Power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|---------------------------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------| +| 1900 – 1920 MHz,
2010 – 2025 MHz | -40 dBm | -103 dBm | 20 MHz | WCDMA signal with one code | +| 1880 – 1900 MHz,
1990 – 2010 MHz,
2025 – 2045 MHz | -40 dBm | -103 dBm | 20 MHz | WCDMA signal with one code | +| 1920 – 1980 MHz | -40 dBm | -103 dBm | 20 MHz | WCDMA signal with one code | +| 1 – 1880 MHz,
1980 – 1990 MHz,
2045 – 12750 MHz | -15 dBm | -103 dBm | — | CW carrier | + +**Table 11.2.9: Blocking requirements for Wide Area BS for operating bands defined in 5.2(b) of TS 25.105 [11]** + +| Centre Frequency of Interfering Signal | Interfering Signal Mean Power | Wanted Signal Mean Power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------| +| 1850 – 1990 MHz | -40 dBm | -103 dBm | 20 MHz | WCDMA signal with one code | +| 1830 – 1850 MHz,
1990 – 2010 MHz | -40 dBm | -103 dBm | 20 MHz | WCDMA signal with one code | +| 1 – 1830 MHz,
2010 – 12750 MHz | -15 dBm | -103 dBm | — | CW carrier | + +**Table 11.2.10: Blocking requirements for Wide Area BS for operating bands defined in 5.2(c) of TS 25.105 [11]** + +| Centre Frequency of Interfering Signal | Interfering Signal Mean Power | Wanted Signal Mean Power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------| +| 1910 – 1930 MHz | -40 dBm | -103 dBm | 20 MHz | WCDMA signal with one code | +| 1890 – 1910 MHz,
1930 – 1950 MHz | -40 dBm | -103 dBm | 20 MHz | WCDMA signal with one code | +| 1 – 1890 MHz,
1950 – 12750 MHz | -15 dBm | -103 dBm | — | CW carrier | + +**Table 11.2.11: Blocking requirements for Local Area BS for operating bands defined in 5.2(a) of TS25.105 [11]** + +| Centre Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|---------------------------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------| +| 1900 – 1920 MHz,
2010 – 2025 MHz | -30 dBm | -89 dBm | 20 MHz | WCDMA signal with one code | +| 1880 – 1900 MHz,
1990 – 2010 MHz,
2025 – 2045 MHz | -30 dBm | -89 dBm | 20 MHz | WCDMA signal with one code | +| 1920 – 1980 MHz | -30 dBm | -89 dBm | 20 MHz | WCDMA signal with one code | +| 1 – 1880 MHz,
1980 – 1990 MHz,
2045 – 12750 MHz | -15 dBm | -89 dBm | — | CW carrier | + +**Table 11.2.12: Blocking requirements for Local Area BS for operating bands defined in 5.2(b) of TS 25.105 [11]** + +| Centre Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------| +| 1850 – 1990 MHz | -30 dBm | -89 dBm | 20 MHz | WCDMA signal with one code | +| 1830 – 1850 MHz,
1990 – 2010 MHz | -30 dBm | -89 dBm | 20 MHz | WCDMA signal with one code | +| 1 – 1830 MHz,
2010 – 12750 MHz | -15 dBm | -89 dBm | — | CW carrier | + +**Table 11.2.13: Blocking requirements for Local BS for operating bands defined in 5.2(c) of TS25.105 [11]** + +| Centre Frequency of Interfering Signal | Interfering Signal mean power | Wanted Signal mean power | Minimum Offset of Interfering Signal | Type of Interfering Signal | +|----------------------------------------|-------------------------------|--------------------------|--------------------------------------|----------------------------| +| 1910 – 1930 MHz | -30 dBm | -89 dBm | 20 MHz | WCDMA signal with one code | +| 1890 – 1910 MHz,
1930 – 1950 MHz | -30 dBm | -89 dBm | 20 MHz | WCDMA signal with one code | +| 1 – 1890 MHz,
1950 – 12750 MHz | -15 dBm | -89 dBm | — | CW carrier | + +##### 11.2.2.3.2 Collocation with GSM900 and/or DCS 1800 + +Common with 3.84 Mcps TDD option. + +#### 11.2.2.4 Spurious emissions + +The spurious emissions power is the power of emissions generated or amplified in a receiver that appear at the BS antenna connector. The requirements apply to all BS with separate RX and TX antenna port. The test shall be performed when both TX and RX are on with the TX port terminated. + +##### 11.2.2.4.1 Minimum requirement + +The power of any spurious emission shall not exceed: + +**Table 11.2.14: Receiver spurious emission requirements** + +| Band | Maximum level | Measurement Bandwidth | Note | +|------------------------------------------------|---------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| 30 MHz – 1 GHz | -57 dBm | 100 kHz | | +| 1 GHz – 1.9 GHz and
1.98 GHz – 2.01 GHz | -47 dBm | 1 MHz | With the exception of frequencies between 25MHz below the first carrier frequency and 25MHz above the last carrier frequency used by the BS. | +| 1.9 GHz – 1.98 GHz and
2.01 GHz – 2.025 GHz | -75 dBm | 7.68 MHz | With the exception of frequencies between 25MHz below the first carrier frequency and 25MHz above the last carrier frequency used by the BS. | +| 2.025 GHz – 12.75 GHz | -47 dBm | 1 MHz | With the exception of frequencies between 25MHz below the first carrier frequency and 25MHz above the last carrier frequency used by the BS. | + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------------|-----------|------|-----|------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2005-04 | RAN1#40 bis | R1-050343 | | | Frame Structure for 7.68Mcps TDD Option | - | 0.0.1 | +| 2005-04 | RAN1#40 bis | R1-050344 | | | Timing Advance for 7.68Mcps TDD Option | - | 0.0.1 | +| 2005-05 | RAN1#41 | | | | V0.0.1 approved by RAN1. | 0.0.1 | 0.1.0 | +| 2005-08 | RAN1#41 | R1-050455 | | | Services offered to higher layers by 7.68Mcps TDD option | 0.1.0 | 0.1.1 | +| 2005-08 | RAN1#41 | R1-050556 | | | Spreading factors and burst types for 7.68Mcps TDD option | 0.1.0 | 0.1.1 | +| 2005-09 | RAN1#42 | R1-050974 | | | V0.1.1 approved by RAN1 | 0.1.1 | 0.2.0 | +| 2005-09 | RAN1#42 | R1-050858 | | | 7.68Mcps TDD: Mapping of transport channels to physical channels | 0.2.0 | 0.2.1 | +| 2005-09 | RAN1#42 | R1-050859 | | | 7.68Mcps TDD: Paging aspects | 0.2.0 | 0.2.1 | +| 2005-09 | RAN1#42 | R1-050860 | | | 7.68Mcps TDD: PRACH Aspects | 0.2.0 | 0.2.1 | +| 2005-09 | RAN1#42 | R1-050861 | | | 7.68Mcps TDD: midamble aspects | 0.2.0 | 0.2.1 | +| 2005-09 | RAN1#42 | R1-050862 | | | 7.68Mcps TDD: Transmission of TPC and TFCI | 0.2.0 | 0.2.1 | +| 2005-09 | RAN1#42 | R1-050930 | | | Synchronisation aspects for 7.68Mcps TDD option | 0.2.0 | 0.2.1 | +| 2005-09 | RAN1#42 | R1-050931 | | | 7.68Mcps TDD: Transmitter power control | 0.2.0 | 0.2.1 | +| 2005-10 | RAN1#42 bis | R1-051251 | | | V0.2.1 approved by RAN1 | 0.2.1 | 0.3.0 | +| 2005-10 | RAN1#42 bis | R1-051223 | | | 7.68Mcps TDD option: HSDPA aspects of TS25.221 | 0.3.0 | 0.3.1 | +| 2005-10 | RAN1#42 bis | R1-051224 | | | SCH channel definition for the 7.68Mcps TDD option | 0.3.0 | 0.3.1 | +| 2005-10 | RAN1#42 bis | R1-051226 | | | Physical layer procedures for the 7.68Mcps TDD option | 0.3.0 | 0.3.1 | +| 2005-10 | RAN1#42 bis | R1-051228 | | | Tx diversity for the 7.68Mcps TDD option | 0.3.0 | 0.3.1 | +| 2005-10 | RAN1#42 bis | R1-051230 | | | 7.68Mcps TDD option: beacon channel aspects | 0.3.0 | 0.3.1 | +| 2005-11 | RAN1#43 | R1-051564 | | | V0.3.1 approved by RAN1 | 0.3.1 | 0.4.0 | +| 2005-11 | RAN1#43 | R1-051520 | | | Transport channel processing for the 7.68Mcps TDD option | 0.4.0 | 0.4.1 | +| 2005-11 | RAN1#43 | R1-051522 | | | Spreading and modulation for the 7.68Mcps TDD option | 0.4.0 | 0.4.1 | +| 2005-11 | RAN1#43 | R1-051620 | | | Updated to v0.4.2 | 0.4.1 | 0.4.2 | +| 2005-11 | TSG-RAN#30 | RP-050829 | | | v1.0.0 created for presentation to RAN plenary for information | 0.4.2 | 1.0.0 | +| 2006-02 | RAN1#44 | R1-060628 | | | MICH Aspects for the 7.68Mcps TDD option | 1.0.0 | 1.1.0 | +| 2006-02 | RAN1#44 | R1-060629 | | | IPDL Aspects for the 7.68Mcps TDD option | 1.0.0 | 1.1.0 | +| 2006-02 | RAN1#44 | R1-060728 | | | Response LS from RAN3 on input to TS25.202 | 1.1.0 | 1.1.1 | +| 2006-02 | RAN1#44 | R1-060744 | | | Response LS from RAN2 on input to TS25.202 | 1.1.0 | 1.1.1 | +| 2006-02 | RAN1#44 | R1-060736 | | | Response LS from RAN4 on input to TS25.202 | 1.1.0 | 1.1.1 | +| 2006-03 | RAN 31 | RP-060117 | | | v2.0.0 created for presentation to RAN plenary for approval | 1.1.1 | 2.0.0 | +| 20/03/06 | RAN 31 | RP-060117 | - | - | Approved as v7.0.0 to put under change control | 2.0.0 | 7.0.0 | +| 29/09/06 | RAN 33 | RP-060493 | 0001 | - | Introduction of E-DCH for 7.68Mcps TDD | 7.0.0 | 7.1.0 | +| 04/03/08 | RAN 39 | - | - | - | Creation of Release 8 further to RAN 39 decision | 7.1.0 | 8.0.0 | +| 07/12/09 | SP 46 | - | - | - | Creation of Release 9 further to SA 46 decision | 8.0.0 | 9.0.0 | +| 21/03/11 | SP 51 | - | - | - | Creation of Release 10 further to SA 51 decision | 9.0.0 | 10.0.0 | +| 2012-09 | SP 57 | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | 11.0.0 | +| 2014-09 | SP 65 | - | - | - | Update to Rel-12 version (MCC) | 11.0.0 | 12.0.0 | +| 2015-12 | SP 70 | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | - | - | - | - | Promotion to Release 14 without technical change (MCC) | 14.0.0 | +| 2018-06 | RP-80 | - | - | - | - | Promotion to Release 15 without technical change (MCC) | 15.0.0 | +| 2020-07 | RP-88e | - | - | - | - | Upgrade to Rel-16 version without technical change | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25221/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-16/25_series/25221/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9be1ba7e1d6bcf6b4e221af062abc73f5e963035 --- /dev/null +++ b/marked/Rel-16/25_series/25221/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d56b00a4702bf4b1758f63dd180de2bc13a6dd1ecf2c290b7e9cb125bb1e53b +size 40461 diff --git a/marked/Rel-16/25_series/25221/014daefdecf9d847ca82cb5b9f50731f_img.jpg b/marked/Rel-16/25_series/25221/014daefdecf9d847ca82cb5b9f50731f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..473aa1b0c034493dd0a7eb6ed6d6d70d355cfb46 --- /dev/null +++ b/marked/Rel-16/25_series/25221/014daefdecf9d847ca82cb5b9f50731f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69be571f63f4872e61a05eb378c58c02c1185bdc82bbe788fe876cf1195dbfaf +size 41209 diff --git a/marked/Rel-16/25_series/25221/077f85b82901283b4657fd2b45fc0294_img.jpg b/marked/Rel-16/25_series/25221/077f85b82901283b4657fd2b45fc0294_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b32ed690999657d6064bdbb473298089e2f9641 --- /dev/null +++ b/marked/Rel-16/25_series/25221/077f85b82901283b4657fd2b45fc0294_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7d6bc0bec240f9f8d1d5234b260e0a798370373ce1fac06dfe9c66119d7b203 +size 2746 diff --git a/marked/Rel-16/25_series/25221/09084c793f44a50d7a1558dbb45d317d_img.jpg b/marked/Rel-16/25_series/25221/09084c793f44a50d7a1558dbb45d317d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..957e60a6fe5852f2503097530a06fe885abbf6f7 --- /dev/null +++ b/marked/Rel-16/25_series/25221/09084c793f44a50d7a1558dbb45d317d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:842b2f36cb11eb41aa7ada13c7de0c635663374b2f80db5353edd2d67cd187d7 +size 32281 diff --git a/marked/Rel-16/25_series/25221/098802c99831a6a7d445310d5e874e16_img.jpg b/marked/Rel-16/25_series/25221/098802c99831a6a7d445310d5e874e16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63f3263412a0be68cafa7557c3785d86fe0a74f9 --- /dev/null +++ b/marked/Rel-16/25_series/25221/098802c99831a6a7d445310d5e874e16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c10513ae3332f8ec5dbb18a758c2ab8ec8b9c2f257886c85758d37d27d57e64d +size 18774 diff --git a/marked/Rel-16/25_series/25221/09955ff8214ffb6947951fc0f60eb6ab_img.jpg b/marked/Rel-16/25_series/25221/09955ff8214ffb6947951fc0f60eb6ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..077ff5d9ee06dd88ba1c37475eaf4ad339691e6e --- /dev/null +++ b/marked/Rel-16/25_series/25221/09955ff8214ffb6947951fc0f60eb6ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc4aa3d6c7743f0d335ba7e3dcbd115a1de39044a70602fa8c327e7140ca7c3f +size 27347 diff --git a/marked/Rel-16/25_series/25221/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Rel-16/25_series/25221/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93c6a464086c5781049b09b521da5f88e0828dec --- /dev/null +++ b/marked/Rel-16/25_series/25221/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a8721578cccb052830d066030c7b8598162e2d6f00807bb536378e86efd162af +size 43143 diff --git a/marked/Rel-16/25_series/25221/0b998e3ad8f9d104768642612605cb35_img.jpg b/marked/Rel-16/25_series/25221/0b998e3ad8f9d104768642612605cb35_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2210afbb83c89596159dbd4bb642cf1bf058a5d5 --- /dev/null +++ b/marked/Rel-16/25_series/25221/0b998e3ad8f9d104768642612605cb35_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:913582bef807be57cf4e1860a19bc3b321097665b71a3893bad8c0bf9dde127a +size 41603 diff --git a/marked/Rel-16/25_series/25221/0bbbad069459da54c1cdef84c90b316a_img.jpg b/marked/Rel-16/25_series/25221/0bbbad069459da54c1cdef84c90b316a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c27c7c13106449432f5dc5547aa8b800fc42f09a --- /dev/null +++ b/marked/Rel-16/25_series/25221/0bbbad069459da54c1cdef84c90b316a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65fef7389f4bb3f259498543e2acd8c230d63fbb5b96bc66c7c6b1517d742722 +size 40585 diff --git a/marked/Rel-16/25_series/25221/0d475a233dd118d11e7c7958dce3c1c2_img.jpg b/marked/Rel-16/25_series/25221/0d475a233dd118d11e7c7958dce3c1c2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e0227f1956aeee2c80a690b33423601268267b7 --- /dev/null +++ b/marked/Rel-16/25_series/25221/0d475a233dd118d11e7c7958dce3c1c2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2da12586aa19a2337c3ff510c0b3fb5fa9d6c70f1957098a03aa49b37e016b33 +size 21201 diff --git a/marked/Rel-16/25_series/25221/1043999278be2d0d419a47a907d4db77_img.jpg b/marked/Rel-16/25_series/25221/1043999278be2d0d419a47a907d4db77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e1866c02fd55d8bb27cf47030de6ff0326eebf2 --- /dev/null +++ b/marked/Rel-16/25_series/25221/1043999278be2d0d419a47a907d4db77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:72814e8c93adbca356c4d97335ea41a7b27631eb4525a0277c2b50d93f80e132 +size 11862 diff --git a/marked/Rel-16/25_series/25221/10b0dda884baae493ad958422d11b552_img.jpg b/marked/Rel-16/25_series/25221/10b0dda884baae493ad958422d11b552_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df971f9f40d95435e14362a8fb971c8d2f90d4c6 --- /dev/null +++ b/marked/Rel-16/25_series/25221/10b0dda884baae493ad958422d11b552_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c23fb3dbbbf61729c176e2ae07ce95eff2713df71f8b9f10c920b268a8d9f9d +size 20256 diff --git a/marked/Rel-16/25_series/25221/1187dbd674a100960ed23efa54ccd6c1_img.jpg b/marked/Rel-16/25_series/25221/1187dbd674a100960ed23efa54ccd6c1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f47cde65d2030f37a8f8c09c6b5b6638d21fd5cc --- /dev/null +++ b/marked/Rel-16/25_series/25221/1187dbd674a100960ed23efa54ccd6c1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3fec061318e7e5e4d706d22f67203561f63ef065ade7ea1ec7af514d462e08bb +size 41401 diff --git a/marked/Rel-16/25_series/25221/16152cf1d84aea10848758f51a91ff6a_img.jpg b/marked/Rel-16/25_series/25221/16152cf1d84aea10848758f51a91ff6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4e675787292027346ba6969b9c36e3dc537d0ca --- /dev/null +++ b/marked/Rel-16/25_series/25221/16152cf1d84aea10848758f51a91ff6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d027d4a2c2624ff4a308b58a3f6173c9fe81d7d807c59643dcde325062f39545 +size 28356 diff --git a/marked/Rel-16/25_series/25221/165508b2526a29efbae96fa16d525d28_img.jpg b/marked/Rel-16/25_series/25221/165508b2526a29efbae96fa16d525d28_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90a49bbf33a980889ffd6e9dc0912d95b67edae7 --- /dev/null +++ b/marked/Rel-16/25_series/25221/165508b2526a29efbae96fa16d525d28_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01e1ced9b16a8f32409496d38439fa257283e142e28f2e6a2850e0e8ce8edf44 +size 35959 diff --git a/marked/Rel-16/25_series/25221/17431d8b59408f09df7552d8bdbaa015_img.jpg b/marked/Rel-16/25_series/25221/17431d8b59408f09df7552d8bdbaa015_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55d4c02aef9f4e7a20b7db526aa1ad5354c0c824 --- /dev/null +++ b/marked/Rel-16/25_series/25221/17431d8b59408f09df7552d8bdbaa015_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67fe4d37a5ae71c3f951d8b8e1f97227f176143829f11d216971ce63734d2957 +size 42315 diff --git a/marked/Rel-16/25_series/25221/17b9d89b91e10c3efc38193baedee268_img.jpg b/marked/Rel-16/25_series/25221/17b9d89b91e10c3efc38193baedee268_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db5948f733a4e05cdc7a7d09f8107a0932db2e26 --- /dev/null +++ b/marked/Rel-16/25_series/25221/17b9d89b91e10c3efc38193baedee268_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d06fc545f80d230fa3c02ba53ae3497d2d760e233dcc31aa371701dfb37e2ad +size 11159 diff --git a/marked/Rel-16/25_series/25221/18291be12b470a557e8c9f3a74e021be_img.jpg b/marked/Rel-16/25_series/25221/18291be12b470a557e8c9f3a74e021be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..205f2d0cc6fbe05962c3ee6a851967a3aa1a16a3 --- /dev/null +++ b/marked/Rel-16/25_series/25221/18291be12b470a557e8c9f3a74e021be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d481ce1db24f052ec85232b2030f41c807d0f82759c5788c24b17247f297f209 +size 24629 diff --git a/marked/Rel-16/25_series/25221/184d3d9a856c77aae93652f4fe30f752_img.jpg b/marked/Rel-16/25_series/25221/184d3d9a856c77aae93652f4fe30f752_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..96fb7308c41b561bb884384550ef64e8b6064efe --- /dev/null +++ b/marked/Rel-16/25_series/25221/184d3d9a856c77aae93652f4fe30f752_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a78913775d75895c4bae237d7b1d84d424e34110df94b269d2b4f5bff9b6a7a +size 40944 diff --git a/marked/Rel-16/25_series/25221/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-16/25_series/25221/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ed59709b999ffd641bedeb27c23e9ef398d044b --- /dev/null +++ b/marked/Rel-16/25_series/25221/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:366d0f088bbf8908ae8ca0f452aea5462f677190fc1edc7cc466bbfd2c78c671 +size 34415 diff --git a/marked/Rel-16/25_series/25221/1b3c088f23921d4eeb45ffc05586e59b_img.jpg b/marked/Rel-16/25_series/25221/1b3c088f23921d4eeb45ffc05586e59b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2748faff2e0dd2ddfc328ffcee8d6b387d7833cf --- /dev/null +++ b/marked/Rel-16/25_series/25221/1b3c088f23921d4eeb45ffc05586e59b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:575fab260c99528479f7df0cb2fbf766f14c5485c801a908caf286b45aa72a51 +size 60656 diff --git a/marked/Rel-16/25_series/25221/1c140ee5d1a87186977da94a96bfa700_img.jpg b/marked/Rel-16/25_series/25221/1c140ee5d1a87186977da94a96bfa700_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b68d7f137f055a48d141cb2605ce8e5c5bc8404 --- /dev/null +++ b/marked/Rel-16/25_series/25221/1c140ee5d1a87186977da94a96bfa700_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6982f2d60ddeb4cd6224bb113ef6e8d8a9206c104d6711619071fa1d8bac43a4 +size 21954 diff --git a/marked/Rel-16/25_series/25221/1ca688982d625c3b8a8e382b675de466_img.jpg b/marked/Rel-16/25_series/25221/1ca688982d625c3b8a8e382b675de466_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..367ea30bdd7fd9bae4e9975491acf96583c14ee6 --- /dev/null +++ b/marked/Rel-16/25_series/25221/1ca688982d625c3b8a8e382b675de466_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4f0ac451ee44595a2a39aae39de2be182309ad9ace55ba733c909455457ef20 +size 41946 diff --git a/marked/Rel-16/25_series/25221/1ce027dfd26183da52137cf990213724_img.jpg b/marked/Rel-16/25_series/25221/1ce027dfd26183da52137cf990213724_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb1d03d00de6d9b4561ed4077c200a5a59624c5b --- /dev/null +++ b/marked/Rel-16/25_series/25221/1ce027dfd26183da52137cf990213724_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:287c488b445d993ea8820f7ea26a6e418ccd2b03d0c5fe671351c30458532cb0 +size 10979 diff --git a/marked/Rel-16/25_series/25221/1dbb1d90b2022a3a765c85929a515cc6_img.jpg b/marked/Rel-16/25_series/25221/1dbb1d90b2022a3a765c85929a515cc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a1a4266d84e79da3d6dec0219a4daf7cdcd28a85 --- /dev/null +++ b/marked/Rel-16/25_series/25221/1dbb1d90b2022a3a765c85929a515cc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:483629a4ce439155cc87c5124048f3f4748fa768bc6e56da26f52be0e03266f9 +size 41993 diff --git a/marked/Rel-16/25_series/25221/1ea7909aea2fb749a6fe98fbdb8cacae_img.jpg b/marked/Rel-16/25_series/25221/1ea7909aea2fb749a6fe98fbdb8cacae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e9b25d77cdf0ada2c406c89a9499b3bcd5f96b1 --- /dev/null +++ b/marked/Rel-16/25_series/25221/1ea7909aea2fb749a6fe98fbdb8cacae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:332793548d31c53535bbdb1776a9eb134b579a4a070a41334f7ffeeb0f95380a +size 50750 diff --git a/marked/Rel-16/25_series/25221/1f1614411edea7edfc86c839a608e1fc_img.jpg b/marked/Rel-16/25_series/25221/1f1614411edea7edfc86c839a608e1fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a05b5f3508568ef33a8ebb4b29a6429a32e1a74 --- /dev/null +++ b/marked/Rel-16/25_series/25221/1f1614411edea7edfc86c839a608e1fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3374dfa06ab4a9f5d643e118655c9b703464762b7705ec5ca39b6ed3bf1c9b6c +size 37013 diff --git a/marked/Rel-16/25_series/25221/23aceb0e7d3c1a644294899d9047df05_img.jpg b/marked/Rel-16/25_series/25221/23aceb0e7d3c1a644294899d9047df05_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05e9548895c3bd5bfdb6322d7a14273df2a579e2 --- /dev/null +++ b/marked/Rel-16/25_series/25221/23aceb0e7d3c1a644294899d9047df05_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d38f072494392053b001a7040712d0de77ac84a27217ac325f0b5769407b1e19 +size 41770 diff --git a/marked/Rel-16/25_series/25221/24029b85683e6c5b14e96022cd9b6ff6_img.jpg b/marked/Rel-16/25_series/25221/24029b85683e6c5b14e96022cd9b6ff6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9fbb1c0aab1fd7d11c790b6fcf71f3d2958416b7 --- /dev/null +++ b/marked/Rel-16/25_series/25221/24029b85683e6c5b14e96022cd9b6ff6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2273adde445360929311830d135abeaaf83dbd8f7d3be605ef5d56fd854c3c39 +size 10160 diff --git a/marked/Rel-16/25_series/25221/276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg b/marked/Rel-16/25_series/25221/276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76b5c6307bb4fef4d6502665cb5878743cf2ab89 --- /dev/null +++ b/marked/Rel-16/25_series/25221/276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37e3db72623e27e40a2e42932960524d1045d37bfc8bbe9d74761b8541e394e3 +size 41601 diff --git a/marked/Rel-16/25_series/25221/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/25_series/25221/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27e3ef8a1c7c5151feec197af9c3bffd4369c06a --- /dev/null +++ b/marked/Rel-16/25_series/25221/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af4553f367d1b9746448933f41ff7e81a7c2afa93a90af775e2fbee36a1c4dc0 +size 32548 diff --git a/marked/Rel-16/25_series/25221/2b00743506f6a3bbd17af764162dc76d_img.jpg b/marked/Rel-16/25_series/25221/2b00743506f6a3bbd17af764162dc76d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4703a073f771bbc9b9a7630b7b2349c7c7f02ca2 --- /dev/null +++ b/marked/Rel-16/25_series/25221/2b00743506f6a3bbd17af764162dc76d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be414862eaa77936810476268e13248d50d0736d2c5dc836e04d8ce5626302e0 +size 40660 diff --git a/marked/Rel-16/25_series/25221/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-16/25_series/25221/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..94ac23626cdc1ec8ac028a834071d303c49d5d49 --- /dev/null +++ b/marked/Rel-16/25_series/25221/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bdd2cf4d531ad74318661c1f7e05d13d2c409876ca0dc65c9ef78736afa45a4c +size 36716 diff --git a/marked/Rel-16/25_series/25221/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg b/marked/Rel-16/25_series/25221/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd3ef6f61199c0cf3682d553ea1ca49ccd8081ad --- /dev/null +++ b/marked/Rel-16/25_series/25221/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35170a51893bdff0ccef554ea0f019695c9faf51da22bcf17d391e27a0a5837d +size 150410 diff --git a/marked/Rel-16/25_series/25221/2dc649aff45a8a0924db45fc3bd6aabb_img.jpg b/marked/Rel-16/25_series/25221/2dc649aff45a8a0924db45fc3bd6aabb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..749e1e24d09a5edac9c153cf35bcfc375ae26cc4 --- /dev/null +++ b/marked/Rel-16/25_series/25221/2dc649aff45a8a0924db45fc3bd6aabb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9f446e924a01e98f6528dbcd82aa9b23cfac21896f77f30dec6d1a929055172 +size 41707 diff --git a/marked/Rel-16/25_series/25221/2f58bcce74146d4d983070d93be12291_img.jpg b/marked/Rel-16/25_series/25221/2f58bcce74146d4d983070d93be12291_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bfcb059606db93a38a9ea426ed9aee75174dd62c --- /dev/null +++ b/marked/Rel-16/25_series/25221/2f58bcce74146d4d983070d93be12291_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b40f80b45f561f7507b04ad52a85c2f7dacb04cb791baded8b9f80935743706f +size 22118 diff --git a/marked/Rel-16/25_series/25221/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-16/25_series/25221/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dbdf7823a2e496254aaa02d6dde6099a30132927 --- /dev/null +++ b/marked/Rel-16/25_series/25221/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d57dd5ac008eb87a3a09ecb21fd99fdf3754c17a703b6781053e363fa47beccc +size 40869 diff --git a/marked/Rel-16/25_series/25221/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-16/25_series/25221/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..565209a068cd0123457e8f12cecf7cf2b69db61e --- /dev/null +++ b/marked/Rel-16/25_series/25221/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e8b631249eef9eafbbf9517e9d3dde16572aba1143efc3d91f3b97833dd6b47 +size 60530 diff --git a/marked/Rel-16/25_series/25221/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-16/25_series/25221/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e244d8f29e5d9aea044308af8128d53338027b0 --- /dev/null +++ b/marked/Rel-16/25_series/25221/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0af208d2f284b40520d4a34c1ddec9bba80fe9d2e5e41122c9c18504cfae8c4 +size 40750 diff --git a/marked/Rel-16/25_series/25221/346324c08906e6d9320f632ab916f73e_img.jpg b/marked/Rel-16/25_series/25221/346324c08906e6d9320f632ab916f73e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c44fbd335b3d0bdbf9921deb2bdd869f65a1aeb --- /dev/null +++ b/marked/Rel-16/25_series/25221/346324c08906e6d9320f632ab916f73e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:518a5b3d428ddf742676e3053f438bddf4d2592d82c38240d2f93e7fa55a7fc7 +size 41711 diff --git a/marked/Rel-16/25_series/25221/3621e1493d508bd789fec58ba8be9a40_img.jpg b/marked/Rel-16/25_series/25221/3621e1493d508bd789fec58ba8be9a40_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20aae316cd56aa6430efd256ddc643ef36b99901 --- /dev/null +++ b/marked/Rel-16/25_series/25221/3621e1493d508bd789fec58ba8be9a40_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54d4514bb80e8fa04cb4414ddd1df23c3cf23d67b37a8ab3ecafcf19fa03772b +size 29981 diff --git a/marked/Rel-16/25_series/25221/367378559e35017a5e1a6f5c30798c5a_img.jpg b/marked/Rel-16/25_series/25221/367378559e35017a5e1a6f5c30798c5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d31ac039d7f6feadbc5480429189f47a7d837e29 --- /dev/null +++ b/marked/Rel-16/25_series/25221/367378559e35017a5e1a6f5c30798c5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e8cc20dc75eacefe9ca9ba1542e18e4247bedf263d367be500c87340ee23d98 +size 47147 diff --git a/marked/Rel-16/25_series/25221/3d590ad29ecfe728f07432e6fcb59064_img.jpg b/marked/Rel-16/25_series/25221/3d590ad29ecfe728f07432e6fcb59064_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0bf0a33d48a5585bf0d9cb145b6c1f49de928b92 --- /dev/null +++ b/marked/Rel-16/25_series/25221/3d590ad29ecfe728f07432e6fcb59064_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3771965ff4098adf03f781412176341636be6db784c1d455730123a1e28ec254 +size 99375 diff --git a/marked/Rel-16/25_series/25221/3d5f590e40a34de3e874fd845a4efd53_img.jpg b/marked/Rel-16/25_series/25221/3d5f590e40a34de3e874fd845a4efd53_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6fa176a7e5a47969b77cd4cec980224cd87dc1c --- /dev/null +++ b/marked/Rel-16/25_series/25221/3d5f590e40a34de3e874fd845a4efd53_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9685e10b0c85bdf76d6bc9ebfb1fd82677cd8e603223ac6bde5103707f8705aa +size 24894 diff --git a/marked/Rel-16/25_series/25221/3da1a07cb87051bf616c9876db958cf0_img.jpg b/marked/Rel-16/25_series/25221/3da1a07cb87051bf616c9876db958cf0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4865aefa1cc328142cd0de7e864d99c77f8585d7 --- /dev/null +++ b/marked/Rel-16/25_series/25221/3da1a07cb87051bf616c9876db958cf0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0108015d76166e5a02c6ce15e1b3b9e6b17e0b83d0479bab6310704d88604d3 +size 21023 diff --git a/marked/Rel-16/25_series/25221/3df9ebba5e1b927ad2dac12bc023c1c5_img.jpg b/marked/Rel-16/25_series/25221/3df9ebba5e1b927ad2dac12bc023c1c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..94df1e35b792ee66707e89383dd4d96f197f5fa9 --- /dev/null +++ b/marked/Rel-16/25_series/25221/3df9ebba5e1b927ad2dac12bc023c1c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75af2d4c57fca3a26a154efde978a7915d073dc854bf1031b66abf8c06f591f7 +size 32399 diff --git a/marked/Rel-16/25_series/25221/3f09464f0a8ac9446981a53f9b78df2c_img.jpg b/marked/Rel-16/25_series/25221/3f09464f0a8ac9446981a53f9b78df2c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28147ccd5eef8fe973cbd37c20938e356d8486ae --- /dev/null +++ b/marked/Rel-16/25_series/25221/3f09464f0a8ac9446981a53f9b78df2c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6751a526568ab8b17673de0edd0bd13aa1c22ebc69e6e973d4a7aa03a2ecce8a +size 35345 diff --git a/marked/Rel-16/25_series/25221/409498e57b1f988b2b604d12cd997002_img.jpg b/marked/Rel-16/25_series/25221/409498e57b1f988b2b604d12cd997002_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e02b429ca55fd2a2901c140f8cc45057a0026042 --- /dev/null +++ b/marked/Rel-16/25_series/25221/409498e57b1f988b2b604d12cd997002_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee701c72d70440b8b1496776569f1ba5702e4d987354da88ea86aa0e7a4ab126 +size 19827 diff --git a/marked/Rel-16/25_series/25221/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/Rel-16/25_series/25221/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ade2be316db9ee22610dc0d9d107141a088bfe23 --- /dev/null +++ b/marked/Rel-16/25_series/25221/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3dcdf5fc5877857fc81c1d79eaab78a301730d10cd702ac515afaadfd2e413f7 +size 59661 diff --git a/marked/Rel-16/25_series/25221/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg b/marked/Rel-16/25_series/25221/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..addcb8f0a7ade15e4f3518e14be2364bf7e4c76a --- /dev/null +++ b/marked/Rel-16/25_series/25221/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dca82afe7b7d9f45f71984c9520a6b41a53611b3fa049062d8d56811591ba9fa +size 20046 diff --git a/marked/Rel-16/25_series/25221/42c65f5cb106938992fc73c05c8713d2_img.jpg b/marked/Rel-16/25_series/25221/42c65f5cb106938992fc73c05c8713d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d847790dbdc8549f00e8578469d3e0e175ad2bca --- /dev/null +++ b/marked/Rel-16/25_series/25221/42c65f5cb106938992fc73c05c8713d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c32e6afac82ef442bc6547cc10daed4b9710f248cb9c427dd59272069611edba +size 64804 diff --git a/marked/Rel-16/25_series/25221/42d3842485845d9f6e511e6526061a55_img.jpg b/marked/Rel-16/25_series/25221/42d3842485845d9f6e511e6526061a55_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3173810f58350af5988f81ede97130db52856249 --- /dev/null +++ b/marked/Rel-16/25_series/25221/42d3842485845d9f6e511e6526061a55_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0744c09343fd741d253012d77a6a69ddda3969a3641495e0bd33ffa1063a187 +size 22579 diff --git a/marked/Rel-16/25_series/25221/4390b89fdb95cba102ee1f88e218b07b_img.jpg b/marked/Rel-16/25_series/25221/4390b89fdb95cba102ee1f88e218b07b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79d3d43113ab1c9097f7885636e81e66c82a2e94 --- /dev/null +++ b/marked/Rel-16/25_series/25221/4390b89fdb95cba102ee1f88e218b07b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad76fab0c6b0d7666b3957dd7782fcf7ae603f63348ec0463b1f2c6f09c79431 +size 41909 diff --git a/marked/Rel-16/25_series/25221/468be155058fd5d2862919eb8ec35496_img.jpg b/marked/Rel-16/25_series/25221/468be155058fd5d2862919eb8ec35496_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3f4472b041b7fdfaca597b63e6d7bca722338b1 --- /dev/null +++ b/marked/Rel-16/25_series/25221/468be155058fd5d2862919eb8ec35496_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90bddeb0e661b55602b9bc3a1ac38a9ddc2970e86cd1b07cb59c4481f01667b1 +size 41325 diff --git a/marked/Rel-16/25_series/25221/4807d5d16f0db93c98330469b9ce5676_img.jpg b/marked/Rel-16/25_series/25221/4807d5d16f0db93c98330469b9ce5676_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6fe01a430cd815f22850ca5b8dea776a2bcdbf16 --- /dev/null +++ b/marked/Rel-16/25_series/25221/4807d5d16f0db93c98330469b9ce5676_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e76e1791b9671fb8c59e376fca0bdfce78c5b20d4e26980c4838fa7e9816a43 +size 74562 diff --git a/marked/Rel-16/25_series/25221/48c6848be25e5a699f0a3412e68bc102_img.jpg b/marked/Rel-16/25_series/25221/48c6848be25e5a699f0a3412e68bc102_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f36c1b5647b5b8e64cf57b4ce33b5953a61bf0c9 --- /dev/null +++ b/marked/Rel-16/25_series/25221/48c6848be25e5a699f0a3412e68bc102_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe8b60400df3a9b7d9cd73e9445e683243dfe5b9a8591639470b37063d719c6e +size 26618 diff --git a/marked/Rel-16/25_series/25221/4b587081b669e7c6695b0e5db5ea7f6d_img.jpg b/marked/Rel-16/25_series/25221/4b587081b669e7c6695b0e5db5ea7f6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b647be7a002b8cdb1cbb66aef8d234e259cf46f4 --- /dev/null +++ b/marked/Rel-16/25_series/25221/4b587081b669e7c6695b0e5db5ea7f6d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:106168b706468a695bdde1e5856bb2be8104ccb8452a6d962d39ea0520361dc2 +size 18131 diff --git a/marked/Rel-16/25_series/25221/4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg b/marked/Rel-16/25_series/25221/4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63b2ec8eb0cd481e90396885124cea3f2949b613 --- /dev/null +++ b/marked/Rel-16/25_series/25221/4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5854a1b09817f3b5cd0802bcbef2fbb876b740d49ba05a21e8d5e01bac2b504d +size 34220 diff --git a/marked/Rel-16/25_series/25221/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg b/marked/Rel-16/25_series/25221/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7003cb06585cddc2c66a427975311f8e0249913e --- /dev/null +++ b/marked/Rel-16/25_series/25221/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18f31eafb42ac7ceab49d3bddb4364155ef083f50ef744e85f9b43fd8b5aadeb +size 22331 diff --git a/marked/Rel-16/25_series/25221/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg b/marked/Rel-16/25_series/25221/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..194c0c46d3a1ee0a2850eedd6c83c86ef0ad01f9 --- /dev/null +++ b/marked/Rel-16/25_series/25221/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96965806b07f4fb07554f013eac994055d90894058ceb7b52e6a200d9f94f9e9 +size 21894 diff --git a/marked/Rel-16/25_series/25221/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg b/marked/Rel-16/25_series/25221/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..556e454c45fffbfd712c7bfd163f793227bb2995 --- /dev/null +++ b/marked/Rel-16/25_series/25221/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:470505f4ed6ae151a55a922d6b3cb08ce68697ede7545956946a4b3436f0a025 +size 25433 diff --git a/marked/Rel-16/25_series/25221/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-16/25_series/25221/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40b003121b888cca750c487132bfd0c58b96f087 --- /dev/null +++ b/marked/Rel-16/25_series/25221/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c1fafd05ff1b3159e237cbaa98892978cb9e3a2147f65eabba7ad715e07d001e +size 13481 diff --git a/marked/Rel-16/25_series/25221/591746e6f224b8d929697a200e87e976_img.jpg b/marked/Rel-16/25_series/25221/591746e6f224b8d929697a200e87e976_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4f5ef1d9111c1f696ede3f7fa5ef4870f6abf33 --- /dev/null +++ b/marked/Rel-16/25_series/25221/591746e6f224b8d929697a200e87e976_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ee6553fb360bebe124d9ebdbbeafcf145708861856eb3e085aa45bd8aea701e +size 41959 diff --git a/marked/Rel-16/25_series/25221/5c65cabec7c5062117fb0d578916cf8b_img.jpg b/marked/Rel-16/25_series/25221/5c65cabec7c5062117fb0d578916cf8b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97937aafe03cc5f44d7bb56bbbba26d5593aa63f --- /dev/null +++ b/marked/Rel-16/25_series/25221/5c65cabec7c5062117fb0d578916cf8b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:044cc803608b7f769d75584319323fa8824a9699e6d42b6a3f30108a78955615 +size 47516 diff --git a/marked/Rel-16/25_series/25221/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg b/marked/Rel-16/25_series/25221/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..afe2102708d3abeb462cd3948cc6f48e5fafc9d0 --- /dev/null +++ b/marked/Rel-16/25_series/25221/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a34fad1fd40a0cba845f78221137b7252e4346373834d8442abf91e277b959d +size 43285 diff --git a/marked/Rel-16/25_series/25221/5ec3284657e4df0df3653dd61d0ecd13_img.jpg b/marked/Rel-16/25_series/25221/5ec3284657e4df0df3653dd61d0ecd13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb8bbbd0742c111e49d967e2e6636afd44566b59 --- /dev/null +++ b/marked/Rel-16/25_series/25221/5ec3284657e4df0df3653dd61d0ecd13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b11736df4e36260c2b2b96c3c7d895a686ecf9b3e36ccbf26300349a0cb7a71 +size 42001 diff --git a/marked/Rel-16/25_series/25221/6348f4fc8b3848158fcfbe85e26a731d_img.jpg b/marked/Rel-16/25_series/25221/6348f4fc8b3848158fcfbe85e26a731d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b23f3c61dbb56214e56d2ce85de7cc26a702807 --- /dev/null +++ b/marked/Rel-16/25_series/25221/6348f4fc8b3848158fcfbe85e26a731d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16b309fcebbacadbef201ca12e8b20927bf4f28e5aed8f7800e5281324531759 +size 41995 diff --git a/marked/Rel-16/25_series/25221/64bec4cd45e47e1976245711f702aca2_img.jpg b/marked/Rel-16/25_series/25221/64bec4cd45e47e1976245711f702aca2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ffc6cfd75d9191e6edad6ce8d55100d5250be92 --- /dev/null +++ b/marked/Rel-16/25_series/25221/64bec4cd45e47e1976245711f702aca2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e17a505fd9944ab909d1a223e83d74156d4e71ffa0efe83d5b4e05286f1478f1 +size 43161 diff --git a/marked/Rel-16/25_series/25221/65d47e1d0e5982c00e9bd116b89e2b6a_img.jpg b/marked/Rel-16/25_series/25221/65d47e1d0e5982c00e9bd116b89e2b6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c927b3daf8fa03f18d3c2a5a4e787260b5f42182 --- /dev/null +++ b/marked/Rel-16/25_series/25221/65d47e1d0e5982c00e9bd116b89e2b6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8eb8f75ee4b27e7029f458b0e252a40b5362976e34936b02cdf6c3801adb711c +size 49062 diff --git a/marked/Rel-16/25_series/25221/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Rel-16/25_series/25221/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80ada2893a124a261a4ddbf364a0ae04e16fb531 --- /dev/null +++ b/marked/Rel-16/25_series/25221/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e2183371c78e918440c3a6635247555d451975613060f63c08af0c71b729a3b4 +size 15291 diff --git a/marked/Rel-16/25_series/25221/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-16/25_series/25221/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b02684fcd2218ed7bd32989bd5cf5a12334791a2 --- /dev/null +++ b/marked/Rel-16/25_series/25221/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d1ca3b4062e2c8a64a8e13aa606d84f788515db83a2204595db6a4c42d23516 +size 62147 diff --git a/marked/Rel-16/25_series/25221/66f134956ab8cc4e2a57345df38dc091_img.jpg b/marked/Rel-16/25_series/25221/66f134956ab8cc4e2a57345df38dc091_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ff2d720c232b7dba5111f52bacb749a8293e917 --- /dev/null +++ b/marked/Rel-16/25_series/25221/66f134956ab8cc4e2a57345df38dc091_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f8850aa02fc3911c543ba7009d08965c94d366f8d1b9125f9e49e61b6b4261c +size 40729 diff --git a/marked/Rel-16/25_series/25221/67a1dd734d3de6e31754caf85d6fe77f_img.jpg b/marked/Rel-16/25_series/25221/67a1dd734d3de6e31754caf85d6fe77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..568512e51533d3e792c36873d6dcf9e0d9a353d2 --- /dev/null +++ b/marked/Rel-16/25_series/25221/67a1dd734d3de6e31754caf85d6fe77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9730b9d8596412efdfea0fc64eb622759a65d76a2589527152ab5ae19923a2c8 +size 41647 diff --git a/marked/Rel-16/25_series/25221/67d03c9e89620d73e3786c869e559752_img.jpg b/marked/Rel-16/25_series/25221/67d03c9e89620d73e3786c869e559752_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87912b637d682ba5b51ffb83a0e69fd1a568e795 --- /dev/null +++ b/marked/Rel-16/25_series/25221/67d03c9e89620d73e3786c869e559752_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5eecea0acfc95acc455ab356bb67fe77abf625f02e0cf240dca87ba6a940241 +size 18062 diff --git a/marked/Rel-16/25_series/25221/68ea9310fb829dd6007635a6cd4ea2ad_img.jpg b/marked/Rel-16/25_series/25221/68ea9310fb829dd6007635a6cd4ea2ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0658af40785adde73ec709d2412d10b7c06d6309 --- /dev/null +++ b/marked/Rel-16/25_series/25221/68ea9310fb829dd6007635a6cd4ea2ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7bfcca0ad5df0fd9bf9f25afa7854863c460cc3a228ac31dc7e1a1efa08eab3a +size 27904 diff --git a/marked/Rel-16/25_series/25221/6929132b4964d52244da61d4614bc4d6_img.jpg b/marked/Rel-16/25_series/25221/6929132b4964d52244da61d4614bc4d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9298fa12bc0f5e72ec8630e407e82ea6e3937d03 --- /dev/null +++ b/marked/Rel-16/25_series/25221/6929132b4964d52244da61d4614bc4d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84d758c45442d5e6dbd81d8c49c033d6beabeb68a36082f7c76fd8922eb04f55 +size 23182 diff --git a/marked/Rel-16/25_series/25221/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg b/marked/Rel-16/25_series/25221/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0730b499cc4e21ceef4cb2d85fcbe503a7ddacc7 --- /dev/null +++ b/marked/Rel-16/25_series/25221/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1ea110810636eca6cf3cc48245806d0297f17136767e3838de8b5630f1f27c6 +size 41689 diff --git a/marked/Rel-16/25_series/25221/6d2057d7e401741861ca63545a5d7d3b_img.jpg b/marked/Rel-16/25_series/25221/6d2057d7e401741861ca63545a5d7d3b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..767034fd3db4c23ba328372cc10dc250a827527e --- /dev/null +++ b/marked/Rel-16/25_series/25221/6d2057d7e401741861ca63545a5d7d3b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ddf3a45bea27a4aa9effc2b9b2e329eef1a4316b76d7d90fa46487cf2296f08a +size 2149 diff --git a/marked/Rel-16/25_series/25221/744acfe8d4e31bcf03f95714c2f6e567_img.jpg b/marked/Rel-16/25_series/25221/744acfe8d4e31bcf03f95714c2f6e567_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7354490deac4d65d920ea409f31bc7169c45bc9f --- /dev/null +++ b/marked/Rel-16/25_series/25221/744acfe8d4e31bcf03f95714c2f6e567_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f61c133566a7cc83cdc211d447d707caeed0584aeb8f6eaef0260c2e007eebb +size 23084 diff --git a/marked/Rel-16/25_series/25221/7472c67897a35ed6b67fcb47ea4c6b6c_img.jpg b/marked/Rel-16/25_series/25221/7472c67897a35ed6b67fcb47ea4c6b6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92ad6348eee68c0435ce03894d3c7faff20376a2 --- /dev/null +++ b/marked/Rel-16/25_series/25221/7472c67897a35ed6b67fcb47ea4c6b6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3329e4577f3b3b8dd4fdc5ac14ea2e1137a2acf4b0d337183bdc9152a044d3f0 +size 35081 diff --git a/marked/Rel-16/25_series/25221/759c7d62402f0b4651ddce292be5bdef_img.jpg b/marked/Rel-16/25_series/25221/759c7d62402f0b4651ddce292be5bdef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2e06cea0c3fb99067d051788d4bc29291f61898 --- /dev/null +++ b/marked/Rel-16/25_series/25221/759c7d62402f0b4651ddce292be5bdef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66ef2b32f8cbc14a937f8accf8fe9a160d288470b84d2bda8d0a90825b91e45d +size 19975 diff --git a/marked/Rel-16/25_series/25221/75e4b78ee25f885d73120e3066a5253e_img.jpg b/marked/Rel-16/25_series/25221/75e4b78ee25f885d73120e3066a5253e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f25cc5b62e0664cb59777a3832afd98b0c6e0199 --- /dev/null +++ b/marked/Rel-16/25_series/25221/75e4b78ee25f885d73120e3066a5253e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e2a76db49cd5c0ec63e1bade5940a9bd136624265fce6a5be85f5c86711d4b8 +size 13219 diff --git a/marked/Rel-16/25_series/25221/768942719f8a9b0d82888157aee1bae4_img.jpg b/marked/Rel-16/25_series/25221/768942719f8a9b0d82888157aee1bae4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d86391011ce378287bc8c5d5ad9f07207621cd80 --- /dev/null +++ b/marked/Rel-16/25_series/25221/768942719f8a9b0d82888157aee1bae4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4302807530bbd10dad2e4e5aeef70d027bfd5715e318a0b6ca100bd21d872d23 +size 32355 diff --git a/marked/Rel-16/25_series/25221/7818b1bd115c04ee738bcf90f51d945b_img.jpg b/marked/Rel-16/25_series/25221/7818b1bd115c04ee738bcf90f51d945b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..568512e51533d3e792c36873d6dcf9e0d9a353d2 --- /dev/null +++ b/marked/Rel-16/25_series/25221/7818b1bd115c04ee738bcf90f51d945b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9730b9d8596412efdfea0fc64eb622759a65d76a2589527152ab5ae19923a2c8 +size 41647 diff --git a/marked/Rel-16/25_series/25221/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-16/25_series/25221/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cfe75f8e03ad4c6d773bcddb17e7c3370e5b43ee --- /dev/null +++ b/marked/Rel-16/25_series/25221/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a45cc60a53ed085c3ca50d25e67af2219affff027908733cea19660a9dbb346 +size 72734 diff --git a/marked/Rel-16/25_series/25221/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-16/25_series/25221/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33241cb1ebc255e070cfbc379719e3e40c9d8ba9 --- /dev/null +++ b/marked/Rel-16/25_series/25221/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9bb2e26a0ed0c92256607ff4611df3bdeb25ae6bf5d889d728d9295a5102a8dc +size 8159 diff --git a/marked/Rel-16/25_series/25221/7c1ccebd0e8661557a8ffc00cfae58a0_img.jpg b/marked/Rel-16/25_series/25221/7c1ccebd0e8661557a8ffc00cfae58a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..573ff4e7e4c35e62bf35386a3275e8f8350a485f --- /dev/null +++ b/marked/Rel-16/25_series/25221/7c1ccebd0e8661557a8ffc00cfae58a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77e11197f1062ecf85565cf0efbac0444ced494f70e9938315c2386ff059b9ea +size 40823 diff --git a/marked/Rel-16/25_series/25221/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/25_series/25221/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..003d4a8300c66395edf4056dd5ac82d75dda4675 --- /dev/null +++ b/marked/Rel-16/25_series/25221/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d428d41eac01c9decd22f90cbe49b1e386e2232bba3989f78a124b0b9ba7d34b +size 116345 diff --git a/marked/Rel-16/25_series/25221/848073118eebfdbfdb9a60e3923fe0b3_img.jpg b/marked/Rel-16/25_series/25221/848073118eebfdbfdb9a60e3923fe0b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e569fc5d51aea1d73523d9593d400c6794f34b6 --- /dev/null +++ b/marked/Rel-16/25_series/25221/848073118eebfdbfdb9a60e3923fe0b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88618712358718112cd4b2231b4f620bf01c0c4397533b8137db6d3e4a46382b +size 52902 diff --git a/marked/Rel-16/25_series/25221/85b53faf49a839f512153285c78fbbdb_img.jpg b/marked/Rel-16/25_series/25221/85b53faf49a839f512153285c78fbbdb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3220318210e9e27678e07c310698e8c72f1d8ea4 --- /dev/null +++ b/marked/Rel-16/25_series/25221/85b53faf49a839f512153285c78fbbdb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6fb2e431cab2097f0cad4b9385deccf7b94941c848730f4c6eee8dc056c9cd3a +size 9727 diff --git a/marked/Rel-16/25_series/25221/87b70d2e8951032d28b4412d82cf1413_img.jpg b/marked/Rel-16/25_series/25221/87b70d2e8951032d28b4412d82cf1413_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb2dae3aa9246ed318353fb9da18011535a6fc87 --- /dev/null +++ b/marked/Rel-16/25_series/25221/87b70d2e8951032d28b4412d82cf1413_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c379447cbfa052e2afa28581af5e1ac8f0ca48df8d9ba03b176513cd8237433e +size 13082 diff --git a/marked/Rel-16/25_series/25221/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Rel-16/25_series/25221/8e80de0cac529b2c3775d677c5203133_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f7697cad874c636e00ff372dabb9e72f667bafb --- /dev/null +++ b/marked/Rel-16/25_series/25221/8e80de0cac529b2c3775d677c5203133_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0e342fdd00b5f18ba908c90a53f1a6c76b5a1b800eab18aefd6507dba285c7f +size 31265 diff --git a/marked/Rel-16/25_series/25221/8edfc370769207831f060f44d2281084_img.jpg b/marked/Rel-16/25_series/25221/8edfc370769207831f060f44d2281084_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90041eb6136766b225666ea8f892e873711473ec --- /dev/null +++ b/marked/Rel-16/25_series/25221/8edfc370769207831f060f44d2281084_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6022f5c45813ffa3a5c974ee6a10136400c9d81917e0679eb38e41221120f75 +size 42226 diff --git a/marked/Rel-16/25_series/25221/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/25_series/25221/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b99cf8ff6b33da425b12fd846422b64a72e2cec1 --- /dev/null +++ b/marked/Rel-16/25_series/25221/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60d0f6c6ba637be16032b6f99df2d5a13496ea2cecae439b126744ae0816f627 +size 19423 diff --git a/marked/Rel-16/25_series/25221/90df9788d66ecf65abf861caf76be5ca_img.jpg b/marked/Rel-16/25_series/25221/90df9788d66ecf65abf861caf76be5ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29f9c8b86f14693c185a5557c74a20b756804f05 --- /dev/null +++ b/marked/Rel-16/25_series/25221/90df9788d66ecf65abf861caf76be5ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e0bb2b88e237d32dfbb9a4405446ba53771fb7654db8e76397ec6743e9c86508 +size 26434 diff --git a/marked/Rel-16/25_series/25221/91b12db3c85bbf466ad27eb3665a1b06_img.jpg b/marked/Rel-16/25_series/25221/91b12db3c85bbf466ad27eb3665a1b06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53f5216e9f0761e02121828b0521ddd50d2930fa --- /dev/null +++ b/marked/Rel-16/25_series/25221/91b12db3c85bbf466ad27eb3665a1b06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60d3c15037fa29e5ef73d2639c265556cdb5592fd8d8d9fdf598d8c017b8bcad +size 7981 diff --git a/marked/Rel-16/25_series/25221/91c33f8e1713989e8192322ec2d1212b_img.jpg b/marked/Rel-16/25_series/25221/91c33f8e1713989e8192322ec2d1212b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..630e262fae99bf17b46be123c34af240b7a861ae --- /dev/null +++ b/marked/Rel-16/25_series/25221/91c33f8e1713989e8192322ec2d1212b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0159d9df3f264c865cf1baca947ff9324fa60dab95aee75702c1d093a742794 +size 50108 diff --git a/marked/Rel-16/25_series/25221/973221d410a5fc97ca8868e730bc796a_img.jpg b/marked/Rel-16/25_series/25221/973221d410a5fc97ca8868e730bc796a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b606115745a2b4538dc1111d2b075139b74bc0e --- /dev/null +++ b/marked/Rel-16/25_series/25221/973221d410a5fc97ca8868e730bc796a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c556565d86440d2da9a2870c25d61a5339714fcc8753585cf73325845c3d5e6d +size 8611 diff --git a/marked/Rel-16/25_series/25221/9870bf462aa0d916a16d14b5a100c60a_img.jpg b/marked/Rel-16/25_series/25221/9870bf462aa0d916a16d14b5a100c60a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..adceb176971a12e03de116d11fbd2c30738c5442 --- /dev/null +++ b/marked/Rel-16/25_series/25221/9870bf462aa0d916a16d14b5a100c60a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d01893ccd8f8ed11929c7c55672d4abc7bfff6958cc6cfb0b42e5392f68b7cb8 +size 35667 diff --git a/marked/Rel-16/25_series/25221/991dd3ca8ff5bdb023220b1d44775e1d_img.jpg b/marked/Rel-16/25_series/25221/991dd3ca8ff5bdb023220b1d44775e1d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d23d0ec49beb97bf1db3aff9669e2a75d03db124 --- /dev/null +++ b/marked/Rel-16/25_series/25221/991dd3ca8ff5bdb023220b1d44775e1d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea2a12e134b4df9329916b9aff05490c15f22c72a8a9c1fc771b65a7c271f615 +size 12388 diff --git a/marked/Rel-16/25_series/25221/99781d878388c3e0f359b1d6ce14119c_img.jpg b/marked/Rel-16/25_series/25221/99781d878388c3e0f359b1d6ce14119c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf9715eea08e4ceee47f65a8afb06207574dd91d --- /dev/null +++ b/marked/Rel-16/25_series/25221/99781d878388c3e0f359b1d6ce14119c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca234dbf895d3e112070c07ec3638960465c2c73022a125e9fe22d3b12fef6e3 +size 30562 diff --git a/marked/Rel-16/25_series/25221/99a0eddf16e836f411661acee6facd17_img.jpg b/marked/Rel-16/25_series/25221/99a0eddf16e836f411661acee6facd17_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd74c813d89ef7dc2db377979ec87bdf95d9903d --- /dev/null +++ b/marked/Rel-16/25_series/25221/99a0eddf16e836f411661acee6facd17_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ff9c522fccc3839680d77e1296d14ea6d2f28f73716754068b2a1078a465b75 +size 41409 diff --git a/marked/Rel-16/25_series/25221/9a14684f8ae1345c6efea6f5994c730c_img.jpg b/marked/Rel-16/25_series/25221/9a14684f8ae1345c6efea6f5994c730c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9da3719f6dbd884d8c51f975335d69b7681a115 --- /dev/null +++ b/marked/Rel-16/25_series/25221/9a14684f8ae1345c6efea6f5994c730c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:771c5e2e7a9ef624a42def6369338bddc4e548c226b92a2dadc92e16046ee415 +size 26239 diff --git a/marked/Rel-16/25_series/25221/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Rel-16/25_series/25221/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef741ba9a6213ac6e2f4eec93804876d6842e98a --- /dev/null +++ b/marked/Rel-16/25_series/25221/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8f57a6376fbaf2ff164ca8f8595c67672bd8716c0cc5461efa0a06ef9492118 +size 22713 diff --git a/marked/Rel-16/25_series/25221/9bafc60bf378685e5e246c3ffad7b792_img.jpg b/marked/Rel-16/25_series/25221/9bafc60bf378685e5e246c3ffad7b792_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb61c3f164c5897fa5ab8bce2269b5423a3e4dcd --- /dev/null +++ b/marked/Rel-16/25_series/25221/9bafc60bf378685e5e246c3ffad7b792_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3dd2adb54ca92d722a5e9bb9620f324c28603663808c92375e0226b6a996e600 +size 42510 diff --git a/marked/Rel-16/25_series/25221/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg b/marked/Rel-16/25_series/25221/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b77c9593b5b417165d7815e18dac48dc65a16d67 --- /dev/null +++ b/marked/Rel-16/25_series/25221/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:128712f1120564499f9648228e9b613a75e0296aaa7a3e0d628d1aa90daac115 +size 41370 diff --git a/marked/Rel-16/25_series/25221/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg b/marked/Rel-16/25_series/25221/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c748a661cd9884c8ed2fc027e5289d764e6f432f --- /dev/null +++ b/marked/Rel-16/25_series/25221/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e846035075a4bd094cc318cce9769dd2e29655319932a5a51258ddd8c0bfe230 +size 42119 diff --git a/marked/Rel-16/25_series/25221/9e5d66cdb5112ad5cab89552b126e4b9_img.jpg b/marked/Rel-16/25_series/25221/9e5d66cdb5112ad5cab89552b126e4b9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4820af4c39d28e925e4d03dfe41a87ca2cae8c73 --- /dev/null +++ b/marked/Rel-16/25_series/25221/9e5d66cdb5112ad5cab89552b126e4b9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9a6c055496c3501073ddfd9dcd9a0624baf6eb71cc8148940819d0e4b05ebbe +size 16855 diff --git a/marked/Rel-16/25_series/25221/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-16/25_series/25221/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cfb00aba7dfd517d8a67057c896f6f141968ddc6 --- /dev/null +++ b/marked/Rel-16/25_series/25221/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28fd728f4463234ba665f3ec6e342d7d4f94bbeff28f39d90e71c96835832a82 +size 101081 diff --git a/marked/Rel-16/25_series/25221/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-16/25_series/25221/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea84c8e3ce36b59dacf05ae9db24e8388f62f1a9 --- /dev/null +++ b/marked/Rel-16/25_series/25221/a0e8fe7862a6d7341faf5dac275277cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b979cc362cd3c3ceae1905083c8943286346a055eec8b18f66cc3156efc6a0b +size 58480 diff --git a/marked/Rel-16/25_series/25221/a166566092dd84196c2ec048ca175290_img.jpg b/marked/Rel-16/25_series/25221/a166566092dd84196c2ec048ca175290_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..94a826d742df1b066effdd4a8d0f4e90f178551e --- /dev/null +++ b/marked/Rel-16/25_series/25221/a166566092dd84196c2ec048ca175290_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ada2ce51413d954122fcda24214f6c0fc3a98460e53d18aa71d00a978f16f9b7 +size 40975 diff --git a/marked/Rel-16/25_series/25221/a320e67b369bfde4a5fa360b100da55c_img.jpg b/marked/Rel-16/25_series/25221/a320e67b369bfde4a5fa360b100da55c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f61b845b29a80d950313b03c42fcda0b86ca8341 --- /dev/null +++ b/marked/Rel-16/25_series/25221/a320e67b369bfde4a5fa360b100da55c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38505c7e13cd28c897e44fe2e70b4731ffc2a2c471d98b398b6b26b7c702653a +size 35717 diff --git a/marked/Rel-16/25_series/25221/a5404b7275b06497eecf9b5883604753_img.jpg b/marked/Rel-16/25_series/25221/a5404b7275b06497eecf9b5883604753_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac43d3fe4541c404ab02cdfdc459142cade43883 --- /dev/null +++ b/marked/Rel-16/25_series/25221/a5404b7275b06497eecf9b5883604753_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd211d937bfeacfcd74649f84309abbc9d17be625694d20748ff5cc586bf3c5d +size 41393 diff --git a/marked/Rel-16/25_series/25221/a66383962afcd0f0458f0d45c101fabf_img.jpg b/marked/Rel-16/25_series/25221/a66383962afcd0f0458f0d45c101fabf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26b1805ed4967be7b3b9319badb7f2619fddb027 --- /dev/null +++ b/marked/Rel-16/25_series/25221/a66383962afcd0f0458f0d45c101fabf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bdab13439400ef8990e440413fa15b3f3227dda42afbe2bb91ae793c27876de9 +size 42088 diff --git a/marked/Rel-16/25_series/25221/aa39f51ba214496042ee3e2ce4ecee80_img.jpg b/marked/Rel-16/25_series/25221/aa39f51ba214496042ee3e2ce4ecee80_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74aea1312753024bc96dc2c6eb215d326ad785d8 --- /dev/null +++ b/marked/Rel-16/25_series/25221/aa39f51ba214496042ee3e2ce4ecee80_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8898ffd0294f47262e5aa39c50d691fcd0f335f22ffa27e6c0bdfd1d659b1ecf +size 42016 diff --git a/marked/Rel-16/25_series/25221/acdccfc1d546eaad16a58be576456caf_img.jpg b/marked/Rel-16/25_series/25221/acdccfc1d546eaad16a58be576456caf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..68e958d3339331d42a7f4c191afd2cdad5d0eb3f --- /dev/null +++ b/marked/Rel-16/25_series/25221/acdccfc1d546eaad16a58be576456caf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:998d2192055680a99aa78d1263459d0bc80bb67721e90878ce726b2d7ef235b3 +size 15047 diff --git a/marked/Rel-16/25_series/25221/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-16/25_series/25221/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70257e2ca1835f50a76de943a1d66af92fe26881 --- /dev/null +++ b/marked/Rel-16/25_series/25221/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:073c79c3b0343e95ec77b8f011c544b68d89dc359272336737207a0312857b56 +size 47431 diff --git a/marked/Rel-16/25_series/25221/b4c825454b7a89b4d7744e4f45521174_img.jpg b/marked/Rel-16/25_series/25221/b4c825454b7a89b4d7744e4f45521174_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85daa51eb167e9a33a73b436775ee76f57cc9e6f --- /dev/null +++ b/marked/Rel-16/25_series/25221/b4c825454b7a89b4d7744e4f45521174_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a6822c122cc6e04d6241ca42b9d66c4946dd17cb3ee1ac3d6a462c6154a6cd3 +size 42423 diff --git a/marked/Rel-16/25_series/25221/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-16/25_series/25221/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c7c91170645b9a81c228ff9825ad6359a14e1d4 --- /dev/null +++ b/marked/Rel-16/25_series/25221/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c92d5831677238be68b55d47c22fba0144c5060ac7b6b9a4ebf79c26b7e534b +size 45060 diff --git a/marked/Rel-16/25_series/25221/b58cedaf15ad4f0edee5621820865ccc_img.jpg b/marked/Rel-16/25_series/25221/b58cedaf15ad4f0edee5621820865ccc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..16e1255b06070574db45361a6a0539365636bf16 --- /dev/null +++ b/marked/Rel-16/25_series/25221/b58cedaf15ad4f0edee5621820865ccc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45d4972a81408aae19d6c9ff1dcfe7b5e707d9db6ae3e29fee4aa4a395bbff90 +size 17869 diff --git a/marked/Rel-16/25_series/25221/b8efedb73292a798b3f2050f9335cae6_img.jpg b/marked/Rel-16/25_series/25221/b8efedb73292a798b3f2050f9335cae6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e5367e3eaa0adb979cf124f024b66fefc9f675a --- /dev/null +++ b/marked/Rel-16/25_series/25221/b8efedb73292a798b3f2050f9335cae6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a661e125a05c3b48f5f37374508f066a369872ca39c3ea886a795bc511468d52 +size 33539 diff --git a/marked/Rel-16/25_series/25221/b9d5785720b6edd0917019f211469dde_img.jpg b/marked/Rel-16/25_series/25221/b9d5785720b6edd0917019f211469dde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..287bf4517783e0e986f5dcee935e07f9737aa179 --- /dev/null +++ b/marked/Rel-16/25_series/25221/b9d5785720b6edd0917019f211469dde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc962a7aaaafc1d126b4a892d7c30a0e24652dccd3d6d4aecaded972280a1c82 +size 35120 diff --git a/marked/Rel-16/25_series/25221/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg b/marked/Rel-16/25_series/25221/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e90027ad0f16f5610c406b9694a923503f368c1 --- /dev/null +++ b/marked/Rel-16/25_series/25221/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7922509339d06b235ce5f56011207922ac187c19db69069149695ef96a9aeb0d +size 41234 diff --git a/marked/Rel-16/25_series/25221/c00d3fb4f9d9609639a6e7d7a356afd3_img.jpg b/marked/Rel-16/25_series/25221/c00d3fb4f9d9609639a6e7d7a356afd3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c08b0a44589101a1f61f66b0c61919e738fac2eb --- /dev/null +++ b/marked/Rel-16/25_series/25221/c00d3fb4f9d9609639a6e7d7a356afd3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a84ef08e3d8d181a8c361ecce0d4ff34a5a674b01467d7484585bd3c982aad9 +size 35133 diff --git a/marked/Rel-16/25_series/25221/c063ca3181a644e8ae4aebfd4cb1a2c3_img.jpg b/marked/Rel-16/25_series/25221/c063ca3181a644e8ae4aebfd4cb1a2c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d643b6e6faafda19909c6d5465f49d97819e111 --- /dev/null +++ b/marked/Rel-16/25_series/25221/c063ca3181a644e8ae4aebfd4cb1a2c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:968b18795e91b1729841d5431fabaae225d11d77efb30450e48aead5c4c28c60 +size 41386 diff --git a/marked/Rel-16/25_series/25221/c21bad844b5cb6026c067a1f43ce67c3_img.jpg b/marked/Rel-16/25_series/25221/c21bad844b5cb6026c067a1f43ce67c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea9d1809007a96e314a347879bff4f5fa7c3d850 --- /dev/null +++ b/marked/Rel-16/25_series/25221/c21bad844b5cb6026c067a1f43ce67c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f3bf6ea64d74dbf5da3a916c80f0d3a8c43423fd159d05e477afc6baa676d7bc +size 41441 diff --git a/marked/Rel-16/25_series/25221/c2ddad56c1553f2499aaf7ef8cef6777_img.jpg b/marked/Rel-16/25_series/25221/c2ddad56c1553f2499aaf7ef8cef6777_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..adaf8f28216da0de0e54c5280bb7fe3cc2cbc8c1 --- /dev/null +++ b/marked/Rel-16/25_series/25221/c2ddad56c1553f2499aaf7ef8cef6777_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:428f2580690963f09d5a8631481050cbe31a920241e6e8b15e7ad2c0b0ab73ba +size 13180 diff --git a/marked/Rel-16/25_series/25221/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-16/25_series/25221/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b2bd39d3389cdd16f1ce1efe64f15832d798d3c --- /dev/null +++ b/marked/Rel-16/25_series/25221/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:299292195b72826232372d6c733058fb498eedd8e47ae791217b50bb8abee0b4 +size 19938 diff --git a/marked/Rel-16/25_series/25221/d197b6ded14ea918198a280ff07122b8_img.jpg b/marked/Rel-16/25_series/25221/d197b6ded14ea918198a280ff07122b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d11b114192563a9cd39245abc53bc3fe3944e0c2 --- /dev/null +++ b/marked/Rel-16/25_series/25221/d197b6ded14ea918198a280ff07122b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc7259174f76afbd1c550eb3cee30d96c8a840a1a99e495ce70fd304e6156aaf +size 42147 diff --git a/marked/Rel-16/25_series/25221/d3b5eac55166fc428a223bba5c46961b_img.jpg b/marked/Rel-16/25_series/25221/d3b5eac55166fc428a223bba5c46961b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85c4a4e8521a570eece11dfe4a15a084505285ae --- /dev/null +++ b/marked/Rel-16/25_series/25221/d3b5eac55166fc428a223bba5c46961b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba94af5f68ac1b249a7037a20cae1c0aec6dff307bc2ead2cf1151f05f4c4b01 +size 27880 diff --git a/marked/Rel-16/25_series/25221/d4a9a1e5b2d8b51e6bf1abacd2421c83_img.jpg b/marked/Rel-16/25_series/25221/d4a9a1e5b2d8b51e6bf1abacd2421c83_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..742d7ff7e937494ba58601372f9e9c18f6b08714 --- /dev/null +++ b/marked/Rel-16/25_series/25221/d4a9a1e5b2d8b51e6bf1abacd2421c83_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:abb7977e3251baaadc3d14a112f98c8bbbebe460e55907f7aa421ab6dceb286d +size 40941 diff --git a/marked/Rel-16/25_series/25221/d79d33da852cb7bca3e87b400a15c3e8_img.jpg b/marked/Rel-16/25_series/25221/d79d33da852cb7bca3e87b400a15c3e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5543b5bc0be0e4486fcd3eaf1715e6117d0a6baf --- /dev/null +++ b/marked/Rel-16/25_series/25221/d79d33da852cb7bca3e87b400a15c3e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:886b4b5f9b600ac3c86e703fcb93a538757f353de54fa68b7dce1b6a247e999f +size 34565 diff --git a/marked/Rel-16/25_series/25221/d9cfc30025244dcd75766061f27ee09f_img.jpg b/marked/Rel-16/25_series/25221/d9cfc30025244dcd75766061f27ee09f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3f9906527991910a1100a71c17fddcc9ddf92cb --- /dev/null +++ b/marked/Rel-16/25_series/25221/d9cfc30025244dcd75766061f27ee09f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4c31c54c70b88bf0b8ae265e30e768fe275c5ebb7b5d6093c0c433cc7f5a309 +size 55228 diff --git a/marked/Rel-16/25_series/25221/da06747b80ea0d71593cbbd4c2ea89aa_img.jpg b/marked/Rel-16/25_series/25221/da06747b80ea0d71593cbbd4c2ea89aa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54174eaf31281350c12df7bd5480dc306fbd22a6 --- /dev/null +++ b/marked/Rel-16/25_series/25221/da06747b80ea0d71593cbbd4c2ea89aa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ff932803dd80389f90780fc79e86648acfbd4a1b6726366e81fa79feef2ea7a +size 34418 diff --git a/marked/Rel-16/25_series/25221/da5916a6e0721dae9522ac5b8abd218f_img.jpg b/marked/Rel-16/25_series/25221/da5916a6e0721dae9522ac5b8abd218f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5eb9c1b3cfb40b5d6f20af47897f30fb97a0f051 --- /dev/null +++ b/marked/Rel-16/25_series/25221/da5916a6e0721dae9522ac5b8abd218f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe73404f1b5b648bf5e5ce2d89176f479093588e274b55eb6abe4df5ae73c300 +size 13835 diff --git a/marked/Rel-16/25_series/25221/da85343976fdbb19f866d9ddbdad0eae_img.jpg b/marked/Rel-16/25_series/25221/da85343976fdbb19f866d9ddbdad0eae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3619ade7e943d7b4af0c722ea35855965a303c0 --- /dev/null +++ b/marked/Rel-16/25_series/25221/da85343976fdbb19f866d9ddbdad0eae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2706564dda3f607005abd80c9a9482242d6f4fd5a6ef55f1a4f9873aa76e2a9 +size 41545 diff --git a/marked/Rel-16/25_series/25221/da87c1b628b63a046d8a0d0fc2c058ea_img.jpg b/marked/Rel-16/25_series/25221/da87c1b628b63a046d8a0d0fc2c058ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b7203b6ad4e727e28b71f2c9b34227ac600db14 --- /dev/null +++ b/marked/Rel-16/25_series/25221/da87c1b628b63a046d8a0d0fc2c058ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dcfa23157d9ee1c054ec9c3612204502c76bb9dd8b3d3502476ab67dcf1fc2a7 +size 99382 diff --git a/marked/Rel-16/25_series/25221/dbe92208b9347289db4a331635197136_img.jpg b/marked/Rel-16/25_series/25221/dbe92208b9347289db4a331635197136_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c9d506b21162b6e537782021185133f0e3095be --- /dev/null +++ b/marked/Rel-16/25_series/25221/dbe92208b9347289db4a331635197136_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed7f75b3f99290b9bcb537119dacf22a8fc77876d76aa6b62d2cf1ac17e7b730 +size 71171 diff --git a/marked/Rel-16/25_series/25221/df1966d80c74bc127f159a48f38b13ee_img.jpg b/marked/Rel-16/25_series/25221/df1966d80c74bc127f159a48f38b13ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f5b723812bb455b72f669d2b301e65a74f6b7c4 --- /dev/null +++ b/marked/Rel-16/25_series/25221/df1966d80c74bc127f159a48f38b13ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:685f589c7b3ced5f1b4ec12e605f3ec2ef99edc547f2a53666f65087a4a0f7cf +size 37552 diff --git a/marked/Rel-16/25_series/25221/df1d0e45191302de72176e4390224c16_img.jpg b/marked/Rel-16/25_series/25221/df1d0e45191302de72176e4390224c16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af29ddf7b7c94544cff3a4a195f6fef1803635b2 --- /dev/null +++ b/marked/Rel-16/25_series/25221/df1d0e45191302de72176e4390224c16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4690414cd9d6218e699ed1e11335f9fcbbdde15b433bba4ee7ec6fc6e72cdad +size 25102 diff --git a/marked/Rel-16/25_series/25221/df935fc9efbd024af4ba77e46bb0bb19_img.jpg b/marked/Rel-16/25_series/25221/df935fc9efbd024af4ba77e46bb0bb19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b79dae1fb2d2e7b29ccb08d329f70a898c5a1b33 --- /dev/null +++ b/marked/Rel-16/25_series/25221/df935fc9efbd024af4ba77e46bb0bb19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb9ff9ae90c6ff3429e8eb6e1cdfe5d01630e9887dfeec0210a968f434cdb08f +size 41304 diff --git a/marked/Rel-16/25_series/25221/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-16/25_series/25221/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c42aa82c0a7dc275d244b767d01a07ee0439b672 --- /dev/null +++ b/marked/Rel-16/25_series/25221/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35f659cce1ba540dd72940a797af65da1225d513ac02d9a25d4c26a87cad80bd +size 41447 diff --git a/marked/Rel-16/25_series/25221/e18841eb4a995df8354a793459e12fd0_img.jpg b/marked/Rel-16/25_series/25221/e18841eb4a995df8354a793459e12fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91f24ed47684629983998814b8138ceb1e29de0b --- /dev/null +++ b/marked/Rel-16/25_series/25221/e18841eb4a995df8354a793459e12fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9374bc68a03961ab5b040241100c7079ecbf1c8e87f159d697c8e921ff9b36b0 +size 41530 diff --git a/marked/Rel-16/25_series/25221/e20792fef9de6560b2d6c5441da7614a_img.jpg b/marked/Rel-16/25_series/25221/e20792fef9de6560b2d6c5441da7614a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4977938fe21eba55985312d1c9a3f8e5ec532b28 --- /dev/null +++ b/marked/Rel-16/25_series/25221/e20792fef9de6560b2d6c5441da7614a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db96513125a5c2573df26f1c7cf3d74d1800fb315c23c2bb8a6ffc9135f83466 +size 41440 diff --git a/marked/Rel-16/25_series/25221/e354b57563dae469c00b412b2abdf765_img.jpg b/marked/Rel-16/25_series/25221/e354b57563dae469c00b412b2abdf765_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef50433892db5f158bdfd4132048af523aa70b5f --- /dev/null +++ b/marked/Rel-16/25_series/25221/e354b57563dae469c00b412b2abdf765_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:128beabde572e94467cf7bf94fb786cb3c3839d88e644bc7225f9904cfb3f2c3 +size 32006 diff --git a/marked/Rel-16/25_series/25221/e35f25e0b66752d4179a4cb108a3fb5a_img.jpg b/marked/Rel-16/25_series/25221/e35f25e0b66752d4179a4cb108a3fb5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0635750f2d200483901706b1e892b192ab460e4 --- /dev/null +++ b/marked/Rel-16/25_series/25221/e35f25e0b66752d4179a4cb108a3fb5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac8442632cf11deefc8d7c7a3be815a56d9912b34be24aabec5b392ee3b42df3 +size 41989 diff --git a/marked/Rel-16/25_series/25221/eabcb2f8b9acedb194571d5bc734b463_img.jpg b/marked/Rel-16/25_series/25221/eabcb2f8b9acedb194571d5bc734b463_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6bc4a51d304273ec6ef9f5b751b6c078ed2baab6 --- /dev/null +++ b/marked/Rel-16/25_series/25221/eabcb2f8b9acedb194571d5bc734b463_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8fcb1f7f3654ec2f763dcd0ea0cf04afe04a516667fbe13f9a017cdd8adc7887 +size 41502 diff --git a/marked/Rel-16/25_series/25221/ee0bf6a260cff72af8f0df0639b6a7c5_img.jpg b/marked/Rel-16/25_series/25221/ee0bf6a260cff72af8f0df0639b6a7c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a28cd394dfc0059ee653a70a46e017eb14d8651 --- /dev/null +++ b/marked/Rel-16/25_series/25221/ee0bf6a260cff72af8f0df0639b6a7c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:360f538e7bdeb055027d746b86482f319f169f25f4171d42d66791617cc2cccc +size 55565 diff --git a/marked/Rel-16/25_series/25221/ef0faba51289e3a364ba51e5ef4d1a43_img.jpg b/marked/Rel-16/25_series/25221/ef0faba51289e3a364ba51e5ef4d1a43_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b856f4fa3bb5ef5123dc02e7b497917dafc8634f --- /dev/null +++ b/marked/Rel-16/25_series/25221/ef0faba51289e3a364ba51e5ef4d1a43_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be9533170b0444acb2b3cb3898a943e00d5fa88a7f39f593898a55c11750e973 +size 41724 diff --git a/marked/Rel-16/25_series/25221/ef45b00396c293be0b18d32b97118bf4_img.jpg b/marked/Rel-16/25_series/25221/ef45b00396c293be0b18d32b97118bf4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3619ade7e943d7b4af0c722ea35855965a303c0 --- /dev/null +++ b/marked/Rel-16/25_series/25221/ef45b00396c293be0b18d32b97118bf4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2706564dda3f607005abd80c9a9482242d6f4fd5a6ef55f1a4f9873aa76e2a9 +size 41545 diff --git a/marked/Rel-16/25_series/25221/ef86416097668984aee7611317e77bb9_img.jpg b/marked/Rel-16/25_series/25221/ef86416097668984aee7611317e77bb9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb43275b06d88e9b4e694f2ef810a41740c520f7 --- /dev/null +++ b/marked/Rel-16/25_series/25221/ef86416097668984aee7611317e77bb9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d1ffb3190af7b359e8f890a25d57ec70265879810fdd10cfc700801f461bb99 +size 100140 diff --git a/marked/Rel-16/25_series/25221/efe7822cf973305b4681375549f04650_img.jpg b/marked/Rel-16/25_series/25221/efe7822cf973305b4681375549f04650_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f56d4c97b87c3da876e0c85446951300a3cf0f89 --- /dev/null +++ b/marked/Rel-16/25_series/25221/efe7822cf973305b4681375549f04650_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2557ca9aad89db1649d7b82afadb3f10493b4aa7c42b19f306dd89567b143497 +size 7907 diff --git a/marked/Rel-16/25_series/25221/f0a97d0d3818a253c1d2a009966081b1_img.jpg b/marked/Rel-16/25_series/25221/f0a97d0d3818a253c1d2a009966081b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c663b03b314b3d95088e410388c91625f90f41d --- /dev/null +++ b/marked/Rel-16/25_series/25221/f0a97d0d3818a253c1d2a009966081b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e069dd868917b0106cce07fa4628525e02a71c325e1547d93250e44b09d43cdf +size 21901 diff --git a/marked/Rel-16/25_series/25221/f1ba1e68228ebd4c3109371574a723e6_img.jpg b/marked/Rel-16/25_series/25221/f1ba1e68228ebd4c3109371574a723e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0453194031bcad6d7feea13a4784ce185d23adf3 --- /dev/null +++ b/marked/Rel-16/25_series/25221/f1ba1e68228ebd4c3109371574a723e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12302a2bb7186320ba57919515d2fb9c1d3bb245df837cf20294143e7911cd29 +size 41507 diff --git a/marked/Rel-16/25_series/25221/f2ea0f64a770b22b902820457d262265_img.jpg b/marked/Rel-16/25_series/25221/f2ea0f64a770b22b902820457d262265_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63efdb62fbbdccd29f19c1ffdc6b424da31633e4 --- /dev/null +++ b/marked/Rel-16/25_series/25221/f2ea0f64a770b22b902820457d262265_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ef24302d89bbe5cff526df993b6088f401303cf0899d54011f8f213e62068b5 +size 14809 diff --git a/marked/Rel-16/25_series/25221/f5d2a88925807080157c7cfb1d41cf0b_img.jpg b/marked/Rel-16/25_series/25221/f5d2a88925807080157c7cfb1d41cf0b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bab35a46bbacfe580fc5bd69b4b1090ed2cb9103 --- /dev/null +++ b/marked/Rel-16/25_series/25221/f5d2a88925807080157c7cfb1d41cf0b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd9cc5345a9868f57fff20e405e60977b39f3bfe809065e2708784ee2e7b6036 +size 39379 diff --git a/marked/Rel-16/25_series/25221/f9625fa3465b009051f85d91cfa1da7e_img.jpg b/marked/Rel-16/25_series/25221/f9625fa3465b009051f85d91cfa1da7e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef8edea2f0abdceb338a5659abcbb3afb1ad45ac --- /dev/null +++ b/marked/Rel-16/25_series/25221/f9625fa3465b009051f85d91cfa1da7e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:732cb64cc2ba1135d281b17bf9371d1bdd10505b89d12fe532fd85eac247ae81 +size 146446 diff --git a/marked/Rel-16/25_series/25221/fc3e2b49a9f850951570e502393b697f_img.jpg b/marked/Rel-16/25_series/25221/fc3e2b49a9f850951570e502393b697f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e85398920ede30375aa88d9fa638c1964e4a59ef --- /dev/null +++ b/marked/Rel-16/25_series/25221/fc3e2b49a9f850951570e502393b697f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1f69726b4d6478ce3a30cfdc535c6abc819b2b7e1c03d8e9dcc269fe22802c5 +size 41497 diff --git a/marked/Rel-16/25_series/25221/fe7304192caf64cda93b580c5e7e5c06_img.jpg b/marked/Rel-16/25_series/25221/fe7304192caf64cda93b580c5e7e5c06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a2dbfce18df31fe894d858260ae57b2d630e206 --- /dev/null +++ b/marked/Rel-16/25_series/25221/fe7304192caf64cda93b580c5e7e5c06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4865a4cbccbe0ca3a05da337310824811f44a252476be57162fb70be1134c353 +size 37287 diff --git a/marked/Rel-16/25_series/25221/ff1a293f8118c0f00dbfeb0ab843d6e6_img.jpg b/marked/Rel-16/25_series/25221/ff1a293f8118c0f00dbfeb0ab843d6e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ce815fac16c28dc49cdcc1de3071e4a9439441b --- /dev/null +++ b/marked/Rel-16/25_series/25221/ff1a293f8118c0f00dbfeb0ab843d6e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8e7b1b52a744f41afcec23c637f27c0595b86c52d1fa9af5dea1f51c673cb7c +size 41783 diff --git a/marked/Rel-16/25_series/25221/raw.md b/marked/Rel-16/25_series/25221/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..06312295bb9603f75eb77a36f38f5c36cce70995 --- /dev/null +++ b/marked/Rel-16/25_series/25221/raw.md @@ -0,0 +1,8013 @@ +Error: + +2 + +Error: Reference source not + +# --- Contents + +| | | +|------------------------------------------------------------------------------|----| +| Foreword..... | 12 | +| 1 Scope..... | 13 | +| 2 References..... | 13 | +| 3 Abbreviations..... | 14 | +| 4 Services offered to higher layers..... | 15 | +| 4.1 Transport channels..... | 15 | +| 4.1.1 Dedicated transport channels..... | 15 | +| 4.1.1.1 DCH – Dedicated Channel..... | 15 | +| 4.1.1.2 E-DCH – Enhanced Dedicated Channel..... | 15 | +| 4.1.2 Common transport channels..... | 15 | +| 4.1.2.1 BCH - Broadcast Channel..... | 16 | +| 4.1.2.2 FACH – Forward Access Channel..... | 16 | +| 4.1.2.3 PCH – Paging Channel..... | 16 | +| 4.1.2.4 RACH – Random Access Channel..... | 16 | +| 4.1.2.5 USCH – Uplink Shared Channel..... | 16 | +| 4.1.2.6 DSCH – Downlink Shared Channel..... | 16 | +| 4.1.2.7 HS-DSCH – High Speed Downlink Shared Channel..... | 16 | +| 4.1.2.8 E-DCH – Enhanced Dedicated Channel..... | 16 | +| 4.2 Indicators..... | 16 | +| 5 Physical channels for the 3.84 Mcps option..... | 17 | +| 5.1 Frame structure..... | 17 | +| 5.2 Dedicated physical channel (DPCH)..... | 18 | +| 5.2.1 Spreading..... | 19 | +| 5.2.1.1 Spreading for Downlink Physical Channels..... | 19 | +| 5.2.1.2 Spreading for Uplink Physical Channels..... | 19 | +| 5.2.2 Burst Types..... | 19 | +| 5.2.2.1 Burst Type 1..... | 19 | +| 5.2.2.2 Burst Type 2..... | 20 | +| 5.2.2.3 Burst Type 3..... | 20 | +| 5.2.2.3A Burst Type 4..... | 21 | +| 5.2.2.4 Transmission of TFCI..... | 21 | +| 5.2.2.5 Transmission of TPC..... | 23 | +| 5.2.2.6 Timeslot formats..... | 23 | +| 5.2.2.6.1 Downlink timeslot formats..... | 23 | +| 5.2.2.6.2 Uplink timeslot formats..... | 24 | +| 5.2.3 Training sequences for spread bursts..... | 26 | +| 5.2.4 Beamforming..... | 28 | +| 5.3 Common physical channels..... | 29 | +| 5.3.1 Primary common control physical channel (P-CCPCH)..... | 29 | +| 5.3.1.1 P-CCPCH Spreading..... | 29 | +| 5.3.1.2 P-CCPCH Burst Types..... | 29 | +| 5.3.1.3 P-CCPCH Training sequences..... | 29 | +| 5.3.2 Secondary common control physical channel (S-CCPCH)..... | 29 | +| 5.3.2.1 S-CCPCH Spreading..... | 29 | +| 5.3.2.2 S-CCPCH Burst Types..... | 29 | +| 5.3.2.2A S-CCPCH Modulation..... | 29 | +| 5.3.2.3 S-CCPCH Training sequences..... | 29 | +| 5.3.3 The physical random access channel (PRACH)..... | 29 | +| 5.3.3.1 PRACH Spreading..... | 29 | +| 5.3.3.2 PRACH Burst Type..... | 30 | +| 5.3.3.3 PRACH Training sequences..... | 30 | +| 5.3.3.4 PRACH timeslot formats..... | 30 | +| 5.3.3.5 Association between Training Sequences and Channelisation Codes..... | 30 | +| 5.3.4 The synchronisation channel (SCH)..... | 32 | +| 5.3.5 Physical Uplink Shared Channel (PUSCH)..... | 33 | +| 5.3.5.1 PUSCH Spreading..... | 33 | + +| | | | +|-----------|--------------------------------------------------------------------------|----| +| 5.3.5.2 | PUSCH Burst Types..... | 34 | +| 5.3.5.3 | PUSCH Training Sequences..... | 34 | +| 5.3.5.4 | UE Selection..... | 34 | +| 5.3.6 | Physical Downlink Shared Channel (PDSCH)..... | 34 | +| 5.3.6.1 | PDSCH Spreading..... | 34 | +| 5.3.6.2 | PDSCH Burst Types..... | 34 | +| 5.3.6.3 | PDSCH Training Sequences..... | 34 | +| 5.3.6.4 | UE Selection..... | 34 | +| 5.3.7 | The Paging Indicator Channel (PICH)..... | 34 | +| 5.3.7.1 | Mapping of Paging Indicators to the PICH bits..... | 34 | +| 5.3.7.2 | Structure of the PICH over multiple radio frames..... | 35 | +| 5.3.7.3 | PICH Training sequences..... | 36 | +| 5.3.8 | The physical node B synchronisation channel (PNBSCH)..... | 36 | +| 5.3.9 | High Speed Physical Downlink Shared Channel (HS-PDSCH)..... | 36 | +| 5.3.9.1 | HS-PDSCH Spreading..... | 36 | +| 5.3.9.2 | HS-PDSCH Burst Types..... | 36 | +| 5.3.9.3 | HS-PDSCH Training Sequences..... | 36 | +| 5.3.9.4 | UE Selection..... | 36 | +| 5.3.9.5 | HS-PDSCH timeslot formats..... | 36 | +| 5.3.10 | Shared Control Channel for HS-DSCH (HS-SCCH)..... | 37 | +| 5.3.10.1 | HS-SCCH Spreading..... | 37 | +| 5.3.10.2 | HS-SCCH Burst Types..... | 37 | +| 5.3.10.3 | HS-SCCH Training Sequences..... | 37 | +| 5.3.10.4 | HS-SCCH timeslot formats..... | 37 | +| 5.3.11 | Shared Information Channel for HS-DSCH (HS-SICH)..... | 37 | +| 5.3.11.1 | HS-SICH Spreading..... | 37 | +| 5.3.11.2 | HS-SICH Burst Types..... | 37 | +| 5.3.11.3 | HS-SICH Training Sequences..... | 37 | +| 5.3.11.4 | HS-SICH timeslot formats..... | 38 | +| 5.3.12 | The MBMS Indicator Channel (MICH)..... | 38 | +| 5.3.12.1 | Mapping of MBMS Indicators to the MICH bits for burst types 1 and 2..... | 38 | +| 5.3.12.1A | Mapping of MBMS Indicators to the MICH bits for burst type 4..... | 39 | +| 5.3.12.2 | MICH Training sequences..... | 40 | +| 5.3.13 | E-DCH Physical Uplink Channel (E-PUCH)..... | 40 | +| 5.3.13.1 | E-UCCH..... | 40 | +| 5.3.13.2 | E-PUCH Spreading..... | 41 | +| 5.3.13.3 | E-PUCH Burst Types..... | 41 | +| 5.3.13.4 | PUSCH Training Sequences..... | 41 | +| 5.3.13.5 | UE Selection..... | 41 | +| 5.3.13.6 | E-PUCH timeslot formats..... | 41 | +| 5.3.14 | E-DCH Random Access Uplink Control Channel (E-RUCCH)..... | 43 | +| 5.3.15 | E-DCH Absolute Grant Channel (E-AGCH)..... | 43 | +| 5.3.15.1 | E-AGCH Spreading..... | 43 | +| 5.3.15.2 | E-AGCH Burst Types..... | 43 | +| 5.3.15.3 | E-AGCH Training Sequences..... | 44 | +| 5.3.15.4 | E-AGCH timeslot formats..... | 44 | +| 5.3.16 | E-DCH Hybrid ARQ Acknowledgement Indicator Channel (E-HICH)..... | 44 | +| 5.3.16.1 | E-HICH Spreading..... | 45 | +| 5.3.16.2 | E-HICH Burst Types..... | 45 | +| 5.3.16.3 | E-HICH Training Sequences..... | 45 | +| 5.4 | Transmit Diversity for DL Physical Channels..... | 45 | +| 5.5 | Beacon characteristics of physical channels..... | 45 | +| 5.5.1 | Location of beacon channels..... | 45 | +| 5.5.2 | Physical characteristics of beacon channels..... | 46 | +| 5.6 | Midamble Allocation for Physical Channels..... | 46 | +| 5.6.1 | Midamble Allocation for DL Physical Channels..... | 46 | +| 5.6.1.1 | Midamble Allocation by signalling from higher layers..... | 47 | +| 5.6.1.2 | Midamble Allocation by layer 1..... | 47 | +| 5.6.1.2.1 | Default midamble..... | 47 | +| 5.6.1.2.2 | Common Midamble..... | 47 | +| 5.6.2 | Midamble Allocation for UL Physical Channels..... | 48 | + +| | | | +|------------|----------------------------------------------------------------------|----| +| 5.7 | Midamble Transmit Power..... | 48 | +| 5.8 | Physical channels for the 3.84 Mcps MBSFN IMB option..... | 49 | +| 5.8.1 | Transmit diversity..... | 50 | +| 5.8.2 | Common physical channels..... | 50 | +| 5.8.2.1 | Primary Common Pilot Channel (P-CPICH)..... | 50 | +| 5.8.2.2 | Time-multiplexed Common Pilot Channel (T-CPICH)..... | 50 | +| 5.8.2.3 | Primary common control physical channel (P-CCPCH)..... | 51 | +| 5.8.2.4 | Secondary common control physical channel (S-CCPCH)..... | 52 | +| 5.8.2.5 | Synchronisation channel (SCH)..... | 54 | +| 5.8.2.6 | The MBMS indicator channel (MICH)..... | 54 | +| 5.8.3 | Timing relationship between physical channels..... | 55 | +| 5A | Physical channels for the 1.28 Mcps option..... | 56 | +| 5A.1 | Frame structure..... | 57 | +| 5A.2 | Dedicated physical channel (DPCH)..... | 58 | +| 5A.2.1 | Spreading..... | 58 | +| 5A.2.2 | Burst Format..... | 58 | +| 5A.2.2a | Dedicated carrier MBSFN Burst Format..... | 59 | +| 5A.2.2.1 | Transmission of TFCI..... | 60 | +| 5A.2.2.1a | Transmission of TFCI for MT burst and MS burst..... | 61 | +| 5A.2.2.2 | Transmission of TPC..... | 62 | +| 5A.2.2.3 | Transmission of SS..... | 65 | +| 5A.2.2.4 | Timeslot formats..... | 67 | +| 5A.2.2.4.1 | Timeslot formats for QPSK..... | 68 | +| 5A.2.2.4.2 | Time slot formats for 8PSK..... | 71 | +| 5A.2.2.4.3 | Time slot formats for MBSFN..... | 71 | +| 5A.2.3 | Training sequences for spread bursts..... | 72 | +| 5A.2.3a | Training sequences for dedicated carrier MBSFN..... | 74 | +| 5A.2.4 | Beamforming..... | 74 | +| 5A.3 | Common physical channels..... | 74 | +| 5A.3.1 | Primary common control physical channel (P-CCPCH)..... | 74 | +| 5A.3.1.1 | P-CCPCH Spreading..... | 74 | +| 5A.3.1.2 | P-CCPCH Burst Format..... | 75 | +| 5A.3.1.3 | P-CCPCH Training sequences..... | 75 | +| 5A.3.2 | Secondary common control physical channel (S-CCPCH)..... | 75 | +| 5A.3.2.1 | S-CCPCH Spreading..... | 75 | +| 5A.3.2.2 | S-CCPCH Burst Format..... | 75 | +| 5A.3.2.3 | S-CCPCH Training sequences..... | 75 | +| 5A.3.3 | Fast Physical Access CHannel (FPACH)..... | 75 | +| 5A.3.3.1 | FPACH burst..... | 75 | +| 5A.3.3.1.1 | Signature Reference Number..... | 76 | +| 5A.3.3.1.2 | Relative Sub-Frame Number..... | 76 | +| 5A.3.3.1.3 | Received starting position of the UpPCH (UpPCH pos )..... | 76 | +| 5A.3.3.1.4 | Transmit Power Level Command for the RACH message..... | 76 | +| 5A.3.3.2 | FPACH Spreading..... | 76 | +| 5A.3.3.3 | FPACH Burst Format..... | 76 | +| 5A.3.3.4 | FPACH Training sequences..... | 76 | +| 5A.3.3.5 | FPACH timeslot formats..... | 76 | +| 5A.3.4 | The physical random access channel (PRACH)..... | 77 | +| 5A.3.4.1 | PRACH Spreading..... | 77 | +| 5A.3.4.2 | PRACH Burst Format..... | 77 | +| 5A.3.4.3 | PRACH Training sequences..... | 77 | +| 5A.3.4.4 | PRACH timeslot formats..... | 77 | +| 5A.3.4.5 | Association between Training Sequences and Channelisation Codes..... | 77 | +| 5A.3.5 | The synchronisation channels (DwPCH, UpPCH)..... | 77 | +| 5A.3.6 | Physical Uplink Shared Channel (PUSCH)..... | 78 | +| 5A.3.7 | Physical Downlink Shared Channel (PDSCH)..... | 78 | +| 5A.3.8 | The Page Indicator Channel (PICH)..... | 78 | +| 5A.3.8.1 | Mapping of Paging Indicators to the PICH bits..... | 78 | +| 5A.3.8.2 | Structure of the PICH over multiple radio frames..... | 79 | +| 5A.3.9 | High Speed Physical Downlink Shared Channel (HS-PDSCH)..... | 79 | +| 5A.3.9.1 | HS-PDSCH Spreading..... | 79 | + +| | | | +|------------|------------------------------------------------------------------|----| +| 5A.3.9.2 | HS-PDSCH Burst Format..... | 79 | +| 5A.3.9.3 | HS-PDSCH Training Sequences..... | 80 | +| 5A.3.9.4 | UE Selection..... | 80 | +| 5A.3.9.5 | HS-PDSCH timeslot formats..... | 80 | +| 5A.3.9.6 | Transmission of SS and TPC..... | 80 | +| 5A.3.10 | Shared Control Channel for HS-DSCH (HS-SCCH)..... | 80 | +| 5A.3.10.1 | HS-SCCH Spreading..... | 81 | +| 5A.3.10.2 | HS-SCCH Burst Format..... | 81 | +| 5A.3.10.3 | HS-SCCH Training Sequences..... | 81 | +| 5A.3.10.4 | HS-SCCH timeslot formats..... | 81 | +| 5A.3.11 | Shared Information Channel for HS-DSCH (HS-SICH)..... | 81 | +| 5A.3.11.1 | HS-SICH Spreading..... | 81 | +| 5A.3.11.2 | HS-SICH Burst Format..... | 81 | +| 5A.3.11.3 | HS-SICH Training Sequences..... | 81 | +| 5A.3.11.4 | HS-SICH timeslot formats..... | 81 | +| 5A.3.12 | The MBMS Indicator Channel (MICH) type1..... | 81 | +| 5A.3.12.1 | Mapping of MBMS Indicators to the type1 MICH bits..... | 82 | +| 5A.3.12a | The MBMS Indicator Channel (MICH) type 2..... | 82 | +| 5A.3.12.1 | Mapping of MBMS Indicators to the type 2 MICH bits..... | 82 | +| 5A.3.13 | Physical Layer Common Control Channel (PLCCH)..... | 83 | +| 5A.3.13.1 | PLCCH Spreading..... | 83 | +| 5A.3.13.2 | PLCCH Burst Type..... | 83 | +| 5A.3.13.3 | PLCCH Training Sequence..... | 83 | +| 5A.3.13.4 | PLCCH timeslot formats..... | 84 | +| 5A.3.14 | E-DCH Physical Uplink Channel..... | 84 | +| 5A.3.14.1 | E-UCCH..... | 84 | +| 5A.3.14.2 | E-PUCH Spreading..... | 85 | +| 5A.3.14.3 | E-PUCH Burst Types..... | 85 | +| 5A.3.14.4 | E-PUCH Training Sequences..... | 85 | +| 5A.3.14.5 | UE Selection..... | 85 | +| 5A.3.14.6 | E-PUCH timeslot formats..... | 85 | +| 5A.3.15 | E-DCH Random Access Uplink Control Channel (E-RUCCH)..... | 92 | +| 5A.3.15.1 | E-RUCCH Spreading..... | 92 | +| 5A.3.15.2 | E-RUCCH Burst Format..... | 92 | +| 5A.3.15.3 | E-RUCCH Training sequences..... | 92 | +| 5A.3.15.4 | E-RUCCH timeslot formats..... | 92 | +| 5A.3.16 | E-DCH Absolute Grant Channel (E-AGCH)..... | 92 | +| 5A.3.16.1 | E-AGCH Spreading..... | 92 | +| 5A.3.16.2 | E-AGCH Burst Types..... | 92 | +| 5A.3.16.3 | E-AGCH Training Sequences..... | 93 | +| 5A.3.16.4 | E-AGCH timeslot formats..... | 93 | +| 5A.3.17 | E-DCH Hybrid ARQ Acknowledgement Indicator Channel (E-HICH)..... | 93 | +| 5A.3.17.1 | E-HICH Spreading..... | 94 | +| 5A.3.17.2 | E-HICH Burst Types..... | 94 | +| 5A.3.17.3 | E-HICH Training Sequences..... | 94 | +| 5A.3.17.4 | E-HICH timeslot formats..... | 94 | +| 5A.3.18 | Standalone midamble channel..... | 94 | +| 5A.3.18.1 | Standalone midamble channel Burst Format..... | 94 | +| 5A.3.18.3 | Standalone midamble channel Training Sequences..... | 95 | +| 5A.3.18.4 | Standalone midamble channel timeslot formats..... | 95 | +| 5A.4 | Transmit Diversity for DL Physical Channels..... | 96 | +| 5A.5 | Beacon characteristics of physical channels..... | 96 | +| 5A.5.1 | Location of beacon channels..... | 96 | +| 5A.5.2 | Physical characteristics of the beacon function..... | 96 | +| 5A.6 | Midamble Allocation for Physical Channels..... | 97 | +| 5A.6.1 | Midamble Allocation for DL Physical Channels..... | 97 | +| 5A.6.1.1 | Midamble Allocation by signalling from higher layers..... | 97 | +| 5A.6.1.2 | Midamble Allocation by layer 1..... | 97 | +| 5A.6.1.2.1 | Default midamble..... | 97 | +| 5A.6.1.2.2 | Common Midamble..... | 98 | +| 5A.6.1.2.3 | Special Default Midamble..... | 98 | + +| | | | +|------------|----------------------------------------------------------------------|-----| +| 5A.6.2 | Midamble Allocation for UL Physical Channels..... | 98 | +| 5A.7 | Midamble Transmit Power..... | 98 | +| 5A.7a | Preamble Allocation and Preamble Transmit Power..... | 98 | +| 5B | Physical channels for the 7.68 Mcps option..... | 98 | +| 5B.1 | General..... | 98 | +| 5B.2 | Frame structure..... | 99 | +| 5B.3 | Dedicated physical channel (DPCH)..... | 100 | +| 5B.3.1 | Spreading..... | 100 | +| 5B.3.1.1 | Spreading for Downlink Physical Channels..... | 100 | +| 5B.3.1.2 | Spreading for Uplink Physical Channels..... | 100 | +| 5B.3.2 | Burst Types..... | 100 | +| 5B.3.2.1 | Burst Type 1..... | 101 | +| 5B.3.2.2 | Burst Type 2..... | 101 | +| 5B.3.2.3 | Burst Type 3..... | 102 | +| 5B.3.2.3A | Burst Type 4..... | 102 | +| 5B.3.2.4 | Transmission of TFCI..... | 103 | +| 5B.3.2.5 | Transmission of TPC..... | 104 | +| 5B.3.2.6 | Timeslot formats..... | 105 | +| 5B.3.2.6.1 | Downlink timeslot formats..... | 105 | +| 5B.3.2.6.2 | Uplink timeslot formats..... | 106 | +| 5B.3.3 | Training sequences for spread bursts..... | 108 | +| 5B.3.4 | Beamforming..... | 110 | +| 5B.4 | Common physical channels..... | 110 | +| 5B.4.1 | Primary common control physical channel (P-CCPCH)..... | 110 | +| 5B.4.1.1 | P-CCPCH Spreading..... | 110 | +| 5B.4.1.2 | P-CCPCH Burst Types..... | 110 | +| 5B.4.1.3 | P-CCPCH Training sequences..... | 110 | +| 5B.4.2 | Secondary common control physical channel (S-CCPCH)..... | 110 | +| 5B.4.2.1 | S-CCPCH Spreading..... | 110 | +| 5B.4.2.2 | S-CCPCH Burst Types..... | 111 | +| 5B.4.2.2A | S-CCPCH Modulation..... | 111 | +| 5B.4.2.3 | S-CCPCH Training sequences..... | 111 | +| 5B.4.3 | The physical random access channel (PRACH)..... | 111 | +| 5B.4.3.1 | PRACH Spreading..... | 111 | +| 5B.4.3.2 | PRACH Burst Type..... | 111 | +| 5B.4.3.3 | PRACH Training sequences..... | 111 | +| 5B.4.3.4 | PRACH timeslot formats..... | 111 | +| 5B.4.3.5 | Association between Training Sequences and Channelisation Codes..... | 111 | +| 5B.4.4 | The synchronisation channel (SCH)..... | 112 | +| 5B.4.5 | Physical Uplink Shared Channel (PUSCH)..... | 113 | +| 5B.4.5.1 | PUSCH Spreading..... | 113 | +| 5B.4.5.2 | PUSCH Burst Types..... | 114 | +| 5B.4.5.3 | PUSCH Training Sequences..... | 114 | +| 5B.4.5.4 | UE Selection..... | 114 | +| 5B.4.6 | Physical Downlink Shared Channel (PDSCH)..... | 114 | +| 5B.4.6.1 | PDSCH Spreading..... | 114 | +| 5B.4.6.2 | PDSCH Burst Types..... | 114 | +| 5B.4.6.3 | PDSCH Training Sequences..... | 114 | +| 5B.4.6.4 | UE Selection..... | 114 | +| 5B.4.7 | The Paging Indicator Channel (PICH)..... | 114 | +| 5B.4.7.1 | Mapping of Paging Indicators to the PICH bits..... | 114 | +| 5B.4.7.2 | Structure of the PICH over multiple radio frames..... | 115 | +| 5B.4.7.3 | PICH Training sequences..... | 115 | +| 5B.4.8 | High Speed Physical Downlink Shared Channel (HS-PDSCH)..... | 115 | +| 5B.4.8.1 | HS-PDSCH Spreading..... | 115 | +| 5B.4.8.2 | HS-PDSCH Burst Types..... | 115 | +| 5B.4.8.3 | HS-PDSCH Training Sequences..... | 116 | +| 5B.4.8.4 | UE Selection..... | 116 | +| 5B.4.8.5 | HS-PDSCH timeslot formats..... | 116 | +| 5B.4.9 | Shared Control Channel for HS-DSCH (HS-SCCH)..... | 116 | +| 5B.4.9.1 | HS-SCCH Spreading..... | 116 | + +| | | | +|------------|----------------------------------------------------------------------------------|-----| +| 5B.4.9.2 | HS-SCCH Burst Types..... | 116 | +| 5B.4.9.3 | HS-SCCH Training Sequences..... | 116 | +| 5B.4.9.4 | HS-SCCH timeslot formats..... | 116 | +| 5B.4.10 | Shared Information Channel for HS-DSCH (HS-SICH)..... | 117 | +| 5B.4.10.1 | HS-SICH Spreading..... | 117 | +| 5B.4.10.2 | HS-SICH Burst Types..... | 117 | +| 5B.4.10.3 | HS-SICH Training Sequences..... | 117 | +| 5B.4.10.4 | HS-SICH timeslot formats..... | 117 | +| 5B.4.11 | The MBMS Indicator Channel (MICH)..... | 117 | +| 5B.4.11.1 | Mapping of MBMS Indicators to the MICH bits for burst types 1 and 2..... | 117 | +| 5B.4.11.1A | Mapping of MBMS Indicators to the MICH bits for burst type 4..... | 118 | +| 5B.4.11.2 | MICH Training sequences..... | 119 | +| 5B.4.12 | E-DCH Physical Uplink Channel (E-PUCH)..... | 119 | +| 5B.4.12.1 | E-UCCH..... | 119 | +| 5B.4.12.2 | E-PUCH Spreading..... | 120 | +| 5B.4.12.3 | E-PUCH Burst Types..... | 120 | +| 5B.4.12.4 | PUSCH Training Sequences..... | 120 | +| 5B.4.12.5 | UE Selection..... | 120 | +| 5B.4.12.6 | E-PUCH timeslot formats..... | 121 | +| 5B.4.13 | E-DCH Random Access Uplink Control Channel (E-RUCCH)..... | 122 | +| 5B.4.14 | E-DCH Absolute Grant Channel (E-AGCH)..... | 122 | +| 5B.4.14.1 | E-AGCH Spreading..... | 123 | +| 5B.4.14.2 | E-AGCH Burst Types..... | 123 | +| 5B.4.14.3 | E-AGCH Training Sequences..... | 123 | +| 5B.4.15.4 | E-AGCH timeslot formats..... | 123 | +| 5B.4.15 | E-DCH Hybrid ARQ Acknowledgement Indicator Channel (E-HICH)..... | 123 | +| 5B.4.15.1 | E-HICH Spreading..... | 124 | +| 5B.4.15.2 | E-HICH Burst Types..... | 124 | +| 5B.4.15.3 | E-HICH Training Sequences..... | 124 | +| 5B.5 | Transmit Diversity for DL Physical Channels..... | 124 | +| 5B.6 | Beacon characteristics of physical channels..... | 124 | +| 5B.6.1 | Location of beacon channels..... | 125 | +| 5B.6.2 | Physical characteristics of beacon channels..... | 125 | +| 5B.7 | Midamble Allocation for Physical Channels..... | 125 | +| 5B.8 | Midamble Transmit Power..... | 125 | +| 6 | Mapping of transport channels to physical channels for the 3.84 Mcps option..... | 127 | +| 6.1 | Dedicated Transport Channels..... | 127 | +| 6.1.1 | The Dedicated Channel (DCH)..... | 127 | +| 6.1.2 | The Enhanced Uplink Dedicated Channel (E-DCH)..... | 128 | +| 6.1.2.1 | E-DCH/E-AGCH Association and Timing..... | 128 | +| 6.1.2.2 | E-DCH/E-HICH Association and Timing..... | 128 | +| 6.2 | Common Transport Channels..... | 129 | +| 6.2.1 | The Broadcast Channel (BCH)..... | 129 | +| 6.2.2 | The Paging Channel (PCH)..... | 129 | +| 6.2.2.1 | PCH/PICH Association..... | 130 | +| 6.2.3 | The Forward Channel (FACH)..... | 130 | +| 6.2.4 | The Random Access Channel (RACH)..... | 130 | +| 6.2.5 | The Uplink Shared Channel (USCH)..... | 130 | +| 6.2.6 | The Downlink Shared Channel (DSCH)..... | 130 | +| 6.2.7 | The High Speed Downlink Shared Channel (HS-DSCH)..... | 130 | +| 6.2.7.1 | HS-DSCH/HS-SCCH Association and Timing..... | 130 | +| 6.2.7.2 | HS-SCCH/HS-DSCH/HS-SICH Association and Timing..... | 131 | +| 6.3 | Mapping of TrCHs for the 3.84 Mcps MBSFN IMB option..... | 132 | +| 7 | Mapping of transport channels to physical channels for the 1.28 Mcps option..... | 132 | +| 7.1 | Dedicated Transport Channels..... | 132 | +| 7.1.1 | The Dedicated Channel (DCH)..... | 132 | +| 7.1.2 | The Enhanced Uplink Dedicated Channel (E-DCH)..... | 133 | +| 7.1.2.1 | E-DCH/E-AGCH Association and Timing..... | 133 | +| 7.1.2.2 | E-DCH/E-HICH Association and Timing..... | 134 | +| 7.2 | Common Transport Channels..... | 134 | + +| | | | +|------------------------------|-----------------------------------------------------------------------------------------------------|------------| +| 7.2.1 | The Broadcast Channel (BCH)..... | 134 | +| 7.2.2 | The Paging Channel (PCH)..... | 134 | +| 7.2.3 | The Forward Channel (FACH)..... | 134 | +| 7.2.4 | The Random Access Channel (RACH)..... | 134 | +| 7.2.5 | The Uplink Shared Channel (USCH)..... | 135 | +| 7.2.6 | The Downlink Shared Channel (DSCH)..... | 135 | +| 7.2.7 | The High Speed Downlink Shared Channel (HS-DSCH)..... | 135 | +| 7.2.7.1 | HS-DSCH/HS-SCCH Association and Timing..... | 135 | +| 7.2.7.2 | HS-SCCH/HS-DSCH/HS-SICH Association and Timing..... | 136 | +| 7.2.7.3 | PICH/HS-SCCH/HS-DSCH Association and Timing..... | 137 | +| 7.2.7.4 | PICH/ HS-DSCH Association and Timing..... | 137 | +| 8 | Mapping of transport channels to physical channels for the 7.68 Mcps option..... | 138 | +| 8.1 | Dedicated Transport Channels..... | 138 | +| 8.1.1 | The Dedicated Channel (DCH)..... | 138 | +| 8.1.2 | The Enhanced Uplink Dedicated Channel (E-DCH)..... | 138 | +| 8.1.2.1 | E-DCH/E-AGCH Association and Timing..... | 138 | +| 8.1.2.2 | E-DCH/E-HICH Association and Timing..... | 139 | +| 8.2 | Common Transport Channels..... | 140 | +| 8.2.1 | The Broadcast Channel (BCH)..... | 140 | +| 8.2.2 | The Paging Channel (PCH)..... | 140 | +| 8.2.3 | The Forward Channel (FACH)..... | 141 | +| 8.2.4 | The Random Access Channel (RACH)..... | 141 | +| 8.2.5 | The Uplink Shared Channel (USCH)..... | 141 | +| 8.2.6 | The Downlink Shared Channel (DSCH)..... | 141 | +| 8.2.7 | The High Speed Downlink Shared Channel (HS-DSCH)..... | 141 | +| 8.2.7.1 | HS-DSCH/HS-SCCH Association and Timing..... | 141 | +| 8.2.7.2 | HS-SCCH/HS-DSCH/HS-SICH Association and Timing..... | 141 | +| Annex A (normative): | Basic Midamble Codes for the 3.84 Mcps option..... | 142 | +| A.1 | Basic Midamble Codes for Burst Type 1 and 3..... | 142 | +| A.2 | Basic Midamble Codes for Burst Type 2 and 4..... | 147 | +| A.3 | Association between Midambles and Channelisation Codes..... | 150 | +| A.3.1 | Association for Burst Type 1/3 and $K_{Cell}=16$ Midambles..... | 150 | +| A.3.2 | Association for Burst Type 1/3 and $K_{Cell}=8$ Midambles..... | 151 | +| A.3.3 | Association for Burst Type 1/3 and $K_{Cell}=4$ Midambles..... | 151 | +| A.3.4 | Association for Burst Type 2 and $K_{Cell}=6$ Midambles..... | 152 | +| A.3.5 | Association for Burst Type 2 and $K_{Cell}=3$ Midambles..... | 152 | +| A.3.6 | Association for Burst Type 4 and $K_{Cell}=1$ Midamble..... | 153 | +| Annex AA (normative): | Basic Midamble Codes for the 1.28 Mcps option..... | 154 | +| AA.1 | Basic Midamble Codes..... | 154 | +| AA.2 | Association between Midambles and Channelisation Codes for default midamble allocation..... | 165 | +| AA.2.1 | Association for $K=16$ Midambles..... | 165 | +| AA.2.2 | Association for $K=14$ Midambles..... | 166 | +| AA.2.3 | Association for $K=12$ Midambles..... | 166 | +| AA.2.4 | Association for $K=10$ Midambles..... | 167 | +| AA.2.5 | Association for $K=8$ Midambles..... | 167 | +| AA.2.6 | Association for $K=6$ Midambles..... | 168 | +| AA.2.7 | Association for $K=4$ Midambles..... | 168 | +| AA.2.8 | Association for $K=2$ Midambles..... | 169 | +| AA.3 | Association between Midambles and Channelisation Codes for special default midamble allocation..... | 169 | +| AA.3.1 | Association for $K=16$ Midambles..... | 170 | +| AA.3.2 | Association for $K=14$ Midambles..... | 173 | +| AA.3.3 | Association for $K=12$ Midambles..... | 176 | +| AA.3.4 | Association for $K=10$ Midambles..... | 179 | +| AA.3.5 | Association for $K=8$ Midambles..... | 182 | + +| | | | +|------------------------------|---------------------------------------------------------------------------------------------------------------|------------| +| AA.3.6 | Association for K=6 Midambles..... | 185 | +| AA.3.7 | Association for K=4 Midambles..... | 188 | +| AA.3.8 | Association for K=2 Midambles..... | 191 | +| Annex AB (normative): | Basic Midamble Codes for the 7.68 Mcps option..... | 192 | +| AB.1 | Basic Midamble Codes for Burst Type 1 and 3..... | 192 | +| AB.2 | Basic Midamble Codes for Burst Type 2..... | 200 | +| AB.2A | Basic Midamble Codes for Burst Type 4..... | 201 | +| AB.3 | Association between Midambles and Channelisation Codes..... | 206 | +| AB.3.1 | Association for $K_{\text{Cell}} = 16$ Midambles..... | 206 | +| AB.3.2 | Association for $K_{\text{Cell}} = 8$ Midambles..... | 207 | +| AB.3.3 | Association for $K_{\text{Cell}} = 4$ Midambles..... | 208 | +| AB.3.4 | Association for Burst Types 4 and $K_{\text{Cell}} = 1$ Midamble..... | 208 | +| Annex B (normative): | Signalling of the number of channelisation codes for the DL common midamble case for 3.84Mcps TDD..... | 209 | +| B.1 | Mapping scheme for Burst Type 1 and $K_{\text{Cell}} = 16$ Midambles..... | 209 | +| B.2 | Mapping scheme for Burst Type 1 and $K_{\text{Cell}} = 8$ Midambles..... | 209 | +| B.3 | Mapping scheme for Burst Type 1 and $K_{\text{Cell}} = 4$ Midambles..... | 210 | +| B.4 | Mapping scheme for beacon timeslots and $K_{\text{Cell}} = 16$ Midambles..... | 210 | +| B.5 | Mapping scheme for beacon timeslots and $K_{\text{Cell}} = 8$ Midambles..... | 211 | +| B.6 | Mapping scheme for beacon timeslots and $K_{\text{Cell}} = 4$ Midambles..... | 211 | +| B.7 | Mapping scheme for Burst Type 2 and $K_{\text{Cell}} = 6$ Midambles..... | 211 | +| B.8 | Mapping scheme for Burst Type 2 and $K_{\text{Cell}} = 3$ Midambles..... | 212 | +| B.9 | Mapping scheme for Burst Type 4 and $K_{\text{Cell}} = 1$ Midamble..... | 212 | +| Annex BA (normative): | Signalling of the number of channelisation codes for the DL common midamble case for 1.28Mcps TDD..... | 213 | +| BA.1 | Mapping scheme for K=16 Midambles..... | 213 | +| BA.2 | Mapping scheme for K=14 Midambles..... | 213 | +| BA.3 | Mapping scheme for K=12 Midambles..... | 214 | +| BA.4 | Mapping scheme for K=10 Midambles..... | 214 | +| BA.5 | Mapping scheme for K=8 Midambles..... | 214 | +| BA.6 | Mapping scheme for K=6 Midambles..... | 215 | +| BA.7 | Mapping scheme for K=4 Midambles..... | 215 | +| BA.8 | Mapping scheme for K=2 Midambles..... | 215 | +| Annex BB (normative): | Signalling of the number of channelisation codes for the DL common midamble case for 7.68Mcps TDD..... | 216 | +| BB.1 | Mapping scheme for $K_{\text{Cell}} = 16$ Midambles..... | 216 | +| BB.2 | Mapping scheme for $K_{\text{Cell}} = 8$ Midambles..... | 216 | +| BB.3 | Mapping scheme for $K_{\text{Cell}} = 4$ Midambles..... | 217 | +| BB.4 | Mapping scheme for beacon timeslots and $K_{\text{Cell}} = 16$ Midambles..... | 217 | +| BB.5 | Mapping scheme for beacon timeslots and $K_{\text{Cell}} = 8$ Midambles..... | 218 | + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| BB.6 Mapping scheme for beacon timeslots and $K_{\text{Cell}}=4$ Midambles................................................................... | 218 | +| BB.7 Mapping scheme for Burst Type 4 and $K_{\text{Cell}}=1$ Midamble....................................................................... | 218 | +| Annex C (informative): CCPCH Multiframe Structure for the 3.84 Mcps option...................................................219 | | +| Annex CA (informative): CCPCH Multiframe Structure for the 1.28 Mcps option...................................................221 | | +| Annex CB (informative): Examples of the association of UL TPC commands to UL uplink time slots and CCTrCH pairs for 1.28 Mcps TDD................................................................................................222 | | +| Annex CC (informative): Examples of the association of UL SS commands to UL uplink time slots...................................................................................................................................................................223 | | +| Annex CD (normative): T-CPICH bit sequences for the 3.84 Mcps MBSFN IMB option..............................224 | | +| Annex D (informative): Change history....................................................................................................................... | 230 | + +## Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# 1 Scope + +The present document describes the characteristics of the physicals channels and the mapping of the transport channels to physical channels in the TDD mode of UTRA. + +# 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. +- [1] 3GPP TS 25.201: "Physical layer - general description". +- [2] 3GPP TS 25.211: "Physical channels and mapping of transport channels onto physical channels (FDD)". +- [3] 3GPP TS 25.212: "Multiplexing and channel coding (FDD)". +- [4] 3GPP TS 25.213: "Spreading and modulation (FDD)". +- [5] 3GPP TS 25.214: "Physical layer procedures (FDD)". +- [6] 3GPP TS 25.215: "Physical layer – Measurements (FDD)". +- [7] 3GPP TS 25.222: "Multiplexing and channel coding (TDD)". +- [8] 3GPP TS 25.223: "Spreading and modulation (TDD)". +- [9] 3GPP TS 25.224: "Physical layer procedures (TDD)". +- [10] 3GPP TS 25.225: "Physical layer – Measurements (TDD)". +- [11] 3GPP TS 25.301: "Radio Interface Protocol Architecture". +- [12] 3GPP TS 25.302: "Services Provided by the Physical Layer". +- [13] 3GPP TS 25.401: "UTRAN Overall Description". +- [14] 3GPP TS 25.402: "Synchronisation in UTRAN, Stage 2". +- [15] 3GPP TS 25.304: "UE Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode". +- [16] 3GPP TS 25.427: "UTRAN Iur and Iub interface user plane protocols for DCH data streams". +- [17] 3GPP TS 25.435: "UTRAN Iub Interface User Plane Protocols for Common Transport Channel Data Streams". +- [18] 3GPP TS25.308: High Speed Downlink Packet Access (HSDPA); Overall description; Stage 2 +- [19] 3GPP TS25.331: "RRC Protocol Specification ". + +## 3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|----------------|------------------------------------------------------| +| 16QAM | 16 Quadrature Amplitude Modulation | +| BCH | Broadcast Channel | +| CCPCH | Common Control Physical Channel | +| CCTrCH | Coded Composite Transport Channel | +| CDMA | Code Division Multiple Access | +| CQI | Channel Quality Indicator | +| DCH | Dedicated Channel | +| DL | Downlink | +| DPCH | Dedicated Physical Channel | +| DRX | Discontinuous Reception | +| DSCH | Downlink Shared Channel | +| DTX | Discontinuous Transmission | +| DwPCH | Downlink Pilot Channel | +| DwPTS | Downlink Pilot Time Slot | +| E-AGCH | E-DCH Absolute Grant Channel | +| E-DCH | Enhanced Dedicated Channel | +| E-HICH | E-DCH Hybrid ARQ Indicator Channel | +| E-PUCH | E-DCH Physical Uplink Channel | +| E-RUCCH | E-DCH Random Access Uplink Control Channel | +| E-UCCH | E-DCH Uplink Control Channel | +| FACH | Forward Access Channel | +| FDD | Frequency Division Duplex | +| FEC | Forward Error Correction | +| GP | Guard Period | +| GSM | Global System for Mobile Communication | +| HARQ | Hybrid ARQ | +| HS-DSCH | High Speed Downlink Shared Channel | +| HS-PDSCH | High Speed Physical Downlink Shared Channel | +| HS-SCCH | Shared Control Channel for HS-DSCH | +| HS-SICH | Shared Information Channel for HS-DSCH | +| IMB | Integrated Mobile Broadcast | +| MBSFN | MBMS over a Single Frequency Network | +| MIB | Master Information Block | +| MICH | MBMS Indicator Channel | +| MIMO | single user Multiple Input Multiple Output | +| MS burst | MBSFN Special burst | +| MT burst | MBSFN Traffic burst | +| MU-MIMO | Multi-User Multiple Input Multiple Output | +| NI | MBMS Notification Indicator | +| NRT | Non-Real Time | +| OVSF | Orthogonal Variable Spreading Factor | +| P-CCPCH | Primary CCPCH | +| PCH | Paging Channel | +| PDSCH | Physical Downlink Shared Channel | +| PI | Paging Indicator (value calculated by higher layers) | +| PICH | Page Indicator Channel | +| PLCCH | Physical Layer Common Control Channel | +| P q | Paging Indicator (indicator set by physical layer) | +| PRACH | Physical Random Access Channel | +| PUSCH | Physical Uplink Shared Channel | +| RACH | Random Access Channel | +| RF | Radio Frame | +| RT | Real Time | +| S-CCPCH | Secondary CCPCH | +| SCH | Synchronisation Channel | +| SCTD | Space Code Transmit Diversity | +| SF | Spreading Factor | + +| | | +|-------|-------------------------------------------| +| SFN | Cell System Frame Number | +| SS | Synchronisation Shift | +| TCH | Traffic Channel | +| TDD | Time Division Duplex | +| TDMA | Time Division Multiple Access | +| TFC | Transport Format Combination | +| TFCI | Transport Format Combination Indicator | +| TFI | Transport Format Indicator | +| TPC | Transmitter Power Control | +| TrCH | Transport Channel | +| TSTD | Time Switched Transmit Diversity | +| TTI | Transmission Time Interval | +| UE | User Equipment | +| UL | Uplink | +| UMTS | Universal Mobil Telecommunications System | +| UpPTS | Uplink Pilot Time Slot | +| UpPCH | Uplink Pilot Channel | +| USCH | Uplink Shared Channel | +| UTRAN | UMTS Terrestrial Radio Access Network | + +--- + +## 4 Services offered to higher layers + +### 4.1 Transport channels + +Transport channels are the services offered by layer 1 to the higher layers. A transport channel is defined by how and with what characteristics data is transferred over the air interface. A general classification of transport channels is into two groups: + +- Dedicated Channels, using inherent addressing of UE +- Common Channels, using explicit addressing of UE if addressing is needed + +General concepts about transport channels are described in [12]. + +#### 4.1.1 Dedicated transport channels + +There exists two types of dedicated transport channel, the Dedicated Channel (DCH) and the Enhanced Dedicated Channel (E-DCH). + +##### 4.1.1.1 DCH – Dedicated Channel + +The Dedicated Channel (DCH) is an up- or downlink transport channel that is used to carry user or control information between the UTRAN and a UE. + +##### 4.1.1.2 E-DCH – Enhanced Dedicated Channel + +The Enhanced Dedicated Channel (E-DCH) is an uplink transport channel. + +For 1.28Mcps TDD multi-carrier E-DCH transmission, a UE in CELL\_DCH state shall have only one E-DCH per carrier. There would be one or more E-DCHs to be transmitted from a UE in CELL\_DCH state in a TTI. + +#### 4.1.2 Common transport channels + +There are seven types of common transport channels for 3.84Mcps and 7.68Mcps TDD: BCH, FACH, PCH, RACH, USCH, DSCH, HS-DSCH. + +There are eight types of common transport channels for 1.28Mcps TDD: BCH, FACH, PCH, RACH, USCH, DSCH, HS-DSCH, E-DCH. + +#### 4.1.2.1 BCH – Broadcast Channel + +The Broadcast Channel (BCH) is a downlink transport channel that is used to broadcast system- and cell-specific information. + +#### 4.1.2.2 FACH – Forward Access Channel + +The Forward Access Channel (FACH) is a downlink transport channel that is used to carry control information to a mobile station when the system knows the location cell of the mobile station. The FACH may also carry short user packets. + +#### 4.1.2.3 PCH – Paging Channel + +The Paging Channel (PCH) is a downlink transport channel that is used to carry control information to a mobile station when the system does not know the location cell of the mobile station. + +#### 4.1.2.4 RACH – Random Access Channel + +The Random Access Channel (RACH) is an up link transport channel that is used to carry control information from mobile station. The RACH may also carry short user packets. + +#### 4.1.2.5 USCH – Uplink Shared Channel + +The uplink shared channel (USCH) is an uplink transport channel shared by several UEs carrying dedicated control or traffic data. + +#### 4.1.2.6 DSCH – Downlink Shared Channel + +The downlink shared channel (DSCH) is a downlink transport channel shared by several UEs carrying dedicated control or traffic data. + +#### 4.1.2.7 HS-DSCH – High Speed Downlink Shared Channel + +The High Speed Downlink Shared Channel (HS-DSCH) is a downlink transport channel shared by several UEs. The HS-DSCH is associated with one or several Shared Control Channels (HS-SCCH). The HS-DSCH is transmitted over the entire cell or over only part of the cell using e.g. beam-forming antennas. + +For 1.28Mcps TDD, in a multi-frequency HS-DSCH cell, the HS-DSCH may be transmitted to a UE on one or more carriers in CELL\_DCH state and on only one carrier in CELL\_FACH, CELL\_PCH and URA\_PCH state in a TTI. The term 'multi-carrier HS-DSCH reception' refers to the HS-DSCH reception on multiple carriers in a TTI for a UE. + +#### 4.1.2.8 E-DCH – Enhanced Dedicated Channel + +The Enhanced Dedicated Channel (E-DCH) is an uplink transport channel in CELL\_FACH and IDLE mode for 1.28Mcps TDD only. + +## 4.2 Indicators + +Indicators are means of fast low-level signalling entities which are transmitted without using information blocks sent over transport channels. The meaning of indicators is implicit to the receiver. + +The indicator(s) defined in the current version of the specifications are: Paging Indicator (PI) and MBMS Notification Indicator (NI). + +--- + +## 5 Physical channels for the 3.84 Mcps option + +Sub-clauses 5.1 to 5.7 do not apply to 3.84 Mcps MBSFN IMB. Sub-clause 5.8 describes physical channels for 3.84 Mcps MBSFN IMB. + +All physical channels take three-layer structure with respect to timeslots, radio frames and system frame numbering (SFN), see [14]. Depending on the resource allocation, the configuration of radio frames or timeslots becomes different. All physical channels need a guard period in every timeslot. The time slots are used in the sense of a TDMA component to separate different user signals in the time domain. The physical channel signal format is presented in figure 1. + +A physical channel in TDD is a burst, which is transmitted in a particular timeslot within allocated Radio Frames. The allocation can be continuous, i.e. the time slot in every frame is allocated to the physical channel or discontinuous, i.e. the time slot in a subset of all frames is allocated only. A burst is the combination of two data parts, a midamble part and a guard period. The duration of a burst is one time slot. Several bursts can be transmitted at the same time from one transmitter. In this case, the data parts must use different OVSF channelisation codes, but the same scrambling code. The midamble parts are either identically or differently shifted versions of a cell-specific basic midamble code, see section 5.2.3. Note when in MBSFN operation, a midamble is not necessarily cell-specific. + +![Figure 1: Physical channel signal format. The diagram shows a 'Radio Frame (10ms)' containing 'frame #i' and 'frame #i+1'. Below this, a 'Time Slot (2560*Tc)' is shown, which is subdivided into timeslots #0, #1, #2, ..., #13, and #14. Dashed lines indicate the relationship between the frame structure and the timeslot structure.](16152cf1d84aea10848758f51a91ff6a_img.jpg) + +Figure 1: Physical channel signal format. The diagram shows a 'Radio Frame (10ms)' containing 'frame #i' and 'frame #i+1'. Below this, a 'Time Slot (2560\*Tc)' is shown, which is subdivided into timeslots #0, #1, #2, ..., #13, and #14. Dashed lines indicate the relationship between the frame structure and the timeslot structure. + +**Figure 1: Physical channel signal format** + +The data part of the burst is spread with a combination of channelisation code and scrambling code. The channelisation code is a OVSF code, that can have a spreading factor of 1, 2, 4, 8, or 16. The data rate of the physical channel is depending on the used spreading factor of the used OVSF code. + +The midamble part of the burst can contain two different types of midambles: a short one of length 256 chips, or a long one of 512 chips. The data rate of the physical channel is depending on the used midamble length. Additionally, when in MBSFN operation a midamble of length 320 chips is used. + +So a physical channel is defined by frequency, timeslot, channelisation code, burst type and Radio Frame allocation. The scrambling code and the basic midamble code are broadcast and may be constant within a cell. When a physical channel is established, a start frame is given. The physical channels can either be of infinite duration, or a duration for the allocation can be defined. + +## 5.1 Frame structure + +The TDMA frame has a duration of 10 ms and is subdivided into 15 time slots (TS) of $2560 \cdot T_c$ duration each. A time slot corresponds to 2560 chips. The physical content of the time slots are the bursts of corresponding length as described in subclause 5.2.2. + +Each 10 ms frame consists of 15 time slots, each allocated to either the uplink or the downlink (figure 2). With such a flexibility, the TDD mode can be adapted to different environments and deployment scenarios. In any configuration at least one time slot has to be allocated for the downlink and at least one time slot has to be allocated for the uplink with the exception of no uplink timeslots when the entire carrier is dedicated to MBSFN + +![Figure 2: The TDD frame structure. The diagram shows a 'frequency' vs 'time' plot. A horizontal bar represents a 10 ms frame, subdivided into 15 time slots. Each time slot has a duration of 2560*Tc. The data rate is indicated as 3.84 Mchip/s.](df1d0e45191302de72176e4390224c16_img.jpg) + +Figure 2: The TDD frame structure. The diagram shows a 'frequency' vs 'time' plot. A horizontal bar represents a 10 ms frame, subdivided into 15 time slots. Each time slot has a duration of 2560\*Tc. The data rate is indicated as 3.84 Mchip/s. + +**Figure 2: The TDD frame structure** + +Examples for multiple and single switching point configurations as well as for symmetric and asymmetric UL/DL allocations are given in figure 3. + +![Figure 3: TDD frame structure examples. The figure shows five examples of 10 ms TDD frames, each divided into 10 subframes. Each subframe contains a downlink (DL) and uplink (UL) portion, indicated by downward and upward arrows respectively. The examples illustrate different switching-point configurations: multiple-switching-point symmetric, multiple-switching-point asymmetric, single-switching-point symmetric, single-switching-point asymmetric, and a case where the entire carrier is dedicated to MBSFN (all downlink).](8307f6b04df072c9332f9987e034272c_img.jpg) + +10 ms + +Multiple-switching-point configuration (symmetric DL/UL allocation) + +10 ms + +Multiple-switching-point configuration (asymmetric DL/UL allocation) + +10 ms + +Single-switching-point configuration (symmetric DL/UL allocation) + +10 ms + +Single-switching-point configuration (asymmetric DL/UL allocation) + +10 ms + +Entire carrier dedicated to MBSFN + +Figure 3: TDD frame structure examples. The figure shows five examples of 10 ms TDD frames, each divided into 10 subframes. Each subframe contains a downlink (DL) and uplink (UL) portion, indicated by downward and upward arrows respectively. The examples illustrate different switching-point configurations: multiple-switching-point symmetric, multiple-switching-point asymmetric, single-switching-point symmetric, single-switching-point asymmetric, and a case where the entire carrier is dedicated to MBSFN (all downlink). + +Figure 3: TDD frame structure examples + +## 5.2 Dedicated physical channel (DPCH) + +The DCH as described in subclause 4.1.1 is mapped onto the dedicated physical channel. + +### 5.2.1 Spreading + +Spreading is applied to the data part of the physical channels and consists of two operations. The first is the channelisation operation, which transforms every data symbol into a number of chips, thus increasing the bandwidth of the signal. The number of chips per data symbol is called the Spreading Factor (SF). The second operation is the scrambling operation, where a scrambling code is applied to the spread signal. Details on channelisation and scrambling operation can be found in [8]. + +#### 5.2.1.1 Spreading for Downlink Physical Channels + +Downlink physical channels shall use SF = 16. Multiple parallel physical channels can be used to support higher data rates. These parallel physical channels shall be transmitted using different channelisation codes, see [8]. These codes with SF = 16 are generated as described in [8]. + +Operation with a single code with spreading factor 1 is possible for the downlink physical channels. + +#### 5.2.1.2 Spreading for Uplink Physical Channels + +The range of spreading factor that may be used for uplink physical channels shall range from 16 down to 1. For each physical channel an individual minimum spreading factor $SF_{min}$ is transmitted by means of the higher layers. There are two options that are indicated by UTRAN: + +1. The UE shall use the spreading factor $SF_{min}$ , independent of the current TFC. +2. The UE shall autonomously increase the spreading factor depending on the current TFC. + +If the UE autonomously changes the SF, it shall always vary the channelisation code along the branch with the higher code numbering of the allowed OVSF sub tree, as depicted in [8]. In the event that code hopping is configured by higher layers, the allowed OVSF sub-tree is that subtended by the effective allocated OVSF code after the hop sequence has been applied to the allocated OVSF code (see [9]). + +For multicode transmission a UE shall use a maximum of two physical channels per timeslot simultaneously. These two parallel physical channels shall be transmitted using different channelisation codes, see [8]. + +## 5.2.2 Burst Types + +Four types of bursts for dedicated physical channels are defined. All of them consist of two data symbol fields, a midamble and a guard period, the lengths of which are different for the individual burst types. Thus, the number of data symbols in a burst depends on the SF and the burst type, as depicted in table 1. + +**Table 1: Number of data symbols (N) for burst types 1, 2, 3 and 4** + +| Spreading factor (SF) | Burst Type 1 | Burst Type 2 | Burst Type 3 | Burst Type 4 | +|-----------------------|--------------|--------------|--------------|--------------| +| 1 | 1952 | 2208 | 1856 | 2112 | +| 2 | 976 | 1104 | 928 | N/A | +| 4 | 488 | 552 | 464 | N/A | +| 8 | 244 | 276 | 232 | N/A | +| 16 | 122 | 138 | 116 | 132 | + +The support of burst types 1, 2 and 3 is mandatory for UEs supporting transmit and receive functions. UEs supporting transmit and receive functions and also MBSFN operation must additionally support burst type 4. UEs with receive only capability need only support burst type 4. The four different bursts defined here are well suited for different applications, as described in the following sections. + +### 5.2.2.1 Burst Type 1 + +The burst type 1 can be used for uplink and downlink. Due to its longer midamble field this burst type supports the construction of a larger number of training sequences, see 5.2.3. The maximum number of training sequences depend on the cell configuration, see annex A. For the burst type 1 this number may be 4, 8, or 16. + +The data fields of the burst type 1 are 976 chips long. The corresponding number of symbols depends on the spreading factor, as indicated in table 1 above. The midamble of burst type 1 has a length of 512 chips. The guard period for the burst type 1 is 96 chip periods long. The burst type 1 is shown in Figure 4. The contents of the burst fields are described in table 2. + +**Table 2: The contents of the burst type 1 fields** + +| Chip number (CN) | Length of field in chips | Length of field in symbols | | Contents of field | +|------------------|--------------------------|----------------------------|--|-------------------| +| 0-975 | 976 | Cf table 1 | | Data symbols | +| 976-1487 | 512 | - | | Midamble | +| 1488-2463 | 976 | Cf table 1 | | Data symbols | +| 2464-2559 | 96 | - | | Guard period | + +![Diagram of Burst Type 1 structure showing four fields: Data symbols (976 chips), Midamble (512 chips), Data symbols (976 chips), and GP (96 CP). The total length is 2560*Tc.](098802c99831a6a7d445310d5e874e16_img.jpg) + +The diagram illustrates the structure of a Burst Type 1. It consists of four contiguous fields: + + +- Data symbols: 976 chips +- Midamble: 512 chips +- Data symbols: 976 chips +- GP (Guard Period): 96 CP (chip periods) + + The total length of the burst is indicated as $2560 \cdot T_c$ . A double-headed arrow below the fields spans the entire length of the burst. + +Diagram of Burst Type 1 structure showing four fields: Data symbols (976 chips), Midamble (512 chips), Data symbols (976 chips), and GP (96 CP). The total length is 2560\*Tc. + +**Figure 4: Burst structure of the burst type 1. GP denotes the guard period and CP the chip periods** + +### 5.2.2.2 Burst Type 2 + +The burst type 2 can be used for uplink and downlink. It offers a longer data field than burst type 1 on the cost of a shorter midamble. Due to the shorter midamble field the burst type 2 supports a maximum number of training sequences of 3 or 6 only, depending on the cell configuration, see annex A. + +The data fields of the burst type 2 are 1104 chips long. The corresponding number of symbols depends on the spreading factor, as indicated in table 1 above. The guard period for the burst type 2 is 96 chip periods long. The burst type 2 is shown in Figure 5. The contents of the burst fields are described in table 3. + +Table 3: The contents of the burst type 2 fields + +| Chip number (CN) | Length of field in chips | Length of field in symbols | | Contents of field | +|------------------|--------------------------|----------------------------|--|-------------------| +| 0-1103 | 1104 | cf table 1 | | Data symbols | +| 1104-1359 | 256 | - | | Midamble | +| 1360-2463 | 1104 | cf table 1 | | Data symbols | +| 2464-2559 | 96 | - | | Guard period | + +![Figure 5: Burst structure of the burst type 2. The diagram shows a horizontal bar divided into four segments: 'Data symbols 1104 chips', 'Midamble 256 chips', 'Data symbols 1104 chips', and 'GP 96 CP'. Below the bar, a double-headed arrow spans the entire length, labeled '2560*Tc'.](40f30e4d577a17052f8b1e6dc802a0d8_img.jpg) + +Figure 5: Burst structure of the burst type 2. The diagram shows a horizontal bar divided into four segments: 'Data symbols 1104 chips', 'Midamble 256 chips', 'Data symbols 1104 chips', and 'GP 96 CP'. Below the bar, a double-headed arrow spans the entire length, labeled '2560\*Tc'. + +Figure 5: Burst structure of the burst type 2. GP denotes the guard period and CP the chip periods + +### 5.2.2.3 Burst Type 3 + +The burst type 3 is used for uplink only. Due to the longer guard period it is suitable for initial access or access to a new cell after handover. It offers the same number of training sequences as burst type 1. + +The data fields of the burst type 3 have a length of 976 chips and 880 chips, respectively. The corresponding number of symbols depends on the spreading factor, as indicated in table 1 above. The midamble of burst type 3 has a length of 512 chips. The guard period for the burst type 3 is 192 chip periods long. The burst type 3 is shown in Figure 6. The contents of the burst fields are described in table 4. + +Table 4: The contents of the burst type 3 fields + +| Chip number (CN) | Length of field in chips | Length of field in symbols | | Contents of field | +|------------------|--------------------------|----------------------------|--|-------------------| +| 0-975 | 976 | Cf table 1 | | Data symbols | +| 976-1487 | 512 | - | | Midamble | +| 1488-2367 | 880 | Cf table 1 | | Data symbols | +| 2368-2559 | 192 | - | | Guard period | + +![Figure 6: Burst structure of the burst type 3. The diagram shows a horizontal bar divided into four segments: 'Data symbols 976 chips', 'Midamble 512 chips', 'Data symbols 880 chips', and 'GP 192 CP'. Below the bar, a double-headed arrow spans the entire length, labeled '2560*Tc'.](0d475a233dd118d11e7c7958dce3c1c2_img.jpg) + +Figure 6: Burst structure of the burst type 3. The diagram shows a horizontal bar divided into four segments: 'Data symbols 976 chips', 'Midamble 512 chips', 'Data symbols 880 chips', and 'GP 192 CP'. Below the bar, a double-headed arrow spans the entire length, labeled '2560\*Tc'. + +Figure 6: Burst structure of the burst type 3. GP denotes the guard period and CP the chip periods + +### 5.2.2.3A Burst Type 4 + +The burst type 4 is used for downlink MBSFN operation only and supports a single training sequence. + +The data fields of the burst type 4 are 1056 chips long. The corresponding number of symbols is 132 as indicated in table 1 above. The midamble of burst type 4 has a length of 320 chips. The guard period for the burst type 4 is 128 chip periods long. The burst type 4 is shown in Figure 6A. The contents of the burst fields are described in table 4A. + +**Table 4A: The contents of the burst type 4 fields** + +| Chip number (CN) | Length of field in chips | Length of field in symbols | | Contents of field | +|------------------|--------------------------|----------------------------|--|-------------------| +| 0-1055 | 1056 | Cf table 1 | | Data symbols | +| 1056-1375 | 320 | - | | Midamble | +| 1376-2431 | 1056 | Cf table 1 | | Data symbols | +| 2432-2559 | 128 | - | | Guard period | + +![Figure 6A: Burst structure of the burst type 4. The diagram shows a horizontal bar divided into four segments: 'Data symbols 1056 chips', 'Midamble 320 chips', 'Data symbols 1056 chips', and 'GP 128 CP'. Below the bar, a double-headed arrow indicates a total length of 2560 * T_c.](3da1a07cb87051bf616c9876db958cf0_img.jpg) + +Figure 6A: Burst structure of the burst type 4. The diagram shows a horizontal bar divided into four segments: 'Data symbols 1056 chips', 'Midamble 320 chips', 'Data symbols 1056 chips', and 'GP 128 CP'. Below the bar, a double-headed arrow indicates a total length of 2560 \* T\_c. + +**Figure 6A: Burst structure of the burst type 4. GP denotes the guard period and CP the chip periods** + +### 5.2.2.4 Transmission of TFCI + +All burst types 1, 2, 3 and 4 provide the possibility for transmission of TFCI. + +The transmission of TFCI is negotiated at call setup and can be re-negotiated during the call. For each CCTrCH it is indicated by higher layer signalling, which TFCI format is applied, except for the MBSFN FACH where the (16,5) bi-orthogonal code is always used for TFCI when TFCI is applied. Additionally for each allocated timeslot it is signalled individually whether that timeslot carries the TFCI or not. The TFCI is always present in the first timeslot in a radio frame for each CCTrCH. If a time slot contains the TFCI, then it is always transmitted using the physical channel with the lowest physical channel sequence number (*p*) in that timeslot. Physical channel sequence numbering is determined by the rate matching function and is described in [7]. + +The transmission of TFCI is done in the data parts of the respective physical channel. In DL the TFCI code word bits and data bits are subject to the same spreading procedure as depicted in [8]. In DL, the modulation applied to the TFCI code word bits is the same as that applied to the data symbols. In UL, independent of the SF that is applied to the data symbols in the burst, the data in the TFCI field are always spread with SF=16 using the channelisation code in the branch with the highest code numbering of the allowed OVSF sub tree, as depicted in [8]. Hence the midamble structure and length is not changed. The TFCI code word is to be transmitted directly adjacent to the midamble, possibly after the TPC. Figure 7 shows the position of the TFCI code word in a traffic burst in downlink. Figure 8 shows the position of the TFCI code word in a traffic burst in uplink. + +![Figure 7: Position of the TFCI code word in the traffic burst in case of downlink. The diagram shows a horizontal bar with segments: 'Data symbols', 'Midamble', 'Data symbols', and 'GP'. Above the 'Midamble' segment, two labels '1st part of TFCI code word' and '2nd part of TFCI code word' point to its beginning and end respectively. Below the 'Midamble' segment, a double-headed arrow indicates its length as 512/320/256 chips. Below the entire bar, another double-headed arrow indicates a total length of 2560 * T_c.](d79d33da852cb7bca3e87b400a15c3e8_img.jpg) + +Figure 7: Position of the TFCI code word in the traffic burst in case of downlink. The diagram shows a horizontal bar with segments: 'Data symbols', 'Midamble', 'Data symbols', and 'GP'. Above the 'Midamble' segment, two labels '1st part of TFCI code word' and '2nd part of TFCI code word' point to its beginning and end respectively. Below the 'Midamble' segment, a double-headed arrow indicates its length as 512/320/256 chips. Below the entire bar, another double-headed arrow indicates a total length of 2560 \* T\_c. + +**Figure 7: Position of the TFCI code word in the traffic burst in case of downlink** + +![Figure 8: Position of the TFCI code word in the traffic burst in case of uplink. The diagram shows a traffic burst structure with fields: Data symbols, Midamble, TFCI (divided into 1st and 2nd parts of TFCI code word), Data symbols, and GP. A dimension line indicates the total length is 2560*Tc, and another indicates the Midamble length is 512/256 chips.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +Figure 8: Position of the TFCI code word in the traffic burst in case of uplink. The diagram shows a traffic burst structure with fields: Data symbols, Midamble, TFCI (divided into 1st and 2nd parts of TFCI code word), Data symbols, and GP. A dimension line indicates the total length is 2560\*Tc, and another indicates the Midamble length is 512/256 chips. + +Figure 8: Position of the TFCI code word in the traffic burst in case of uplink + +Two examples of TFCI transmission in the case of multiple DPCHs used for a connection are given in the Figure 9 and Figure 10 below. Combinations of the two schemes shown are also applicable. + +![Figure 9: Example of TFCI transmission with physical channels multiplexed in code domain. The diagram shows three horizontal bars representing different codes over time (t). The top two bars show Data (white) and Midamble (grey) segments. The bottom bar shows Data (white), Midamble (grey), and TFCI (dark grey) segments. A dimension line indicates a duration of 2560*Tc.](4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg) + +Figure 9: Example of TFCI transmission with physical channels multiplexed in code domain. The diagram shows three horizontal bars representing different codes over time (t). The top two bars show Data (white) and Midamble (grey) segments. The bottom bar shows Data (white), Midamble (grey), and TFCI (dark grey) segments. A dimension line indicates a duration of 2560\*Tc. + +Figure 9: Example of TFCI transmission with physical channels multiplexed in code domain + +![Figure 10: Example of TFCI transmission with physical channels multiplexed in time domain. The diagram shows three horizontal bars representing different time slots over time (t). Each slot contains Data (white), Midamble (grey), and TFCI (dark grey) segments. A dimension line indicates a duration of 2560*Tc.](75e4b78ee25f885d73120e3066a5253e_img.jpg) + +Figure 10: Example of TFCI transmission with physical channels multiplexed in time domain. The diagram shows three horizontal bars representing different time slots over time (t). Each slot contains Data (white), Midamble (grey), and TFCI (dark grey) segments. A dimension line indicates a duration of 2560\*Tc. + +Figure 10: Example of TFCI transmission with physical channels multiplexed in time domain + +In case the Node B receives an invalid TFI combination on the DCHs mapped to one CCTrCH the procedure described in [16] shall be applied. According to this procedure DTX shall be applied to all DPCHs to which the CCTrCH is mapped to. + +### 5.2.2.5 Transmission of TPC + +Burst types 1, 2 and 3 for dedicated channels provide the possibility for transmission of TPC in uplink. + +The transmission of TPC is done in the data parts of the traffic burst. Independent of the SF that is applied to the data symbols in the burst, the data in the TPC field are always spread with SF=16 using the channelisation code in the branch with the highest code numbering of the allowed OVSF sub tree, as depicted in [8]. Hence the midamble structure and length is not changed. The TPC information is to be transmitted directly after the midamble. Figure 11 shows the position of the TPC in a traffic burst. + +For every user the TPC information shall be transmitted at least once per transmitted frame. If a TFCI is applied for a CCTrCH, TPC shall be transmitted with the same channelization codes and in the same timeslots as the TFCI. If no TFCI is applied for a CCTrCH, TPC shall be transmitted using the physical channel corresponding to physical channel + +sequence number $p=1$ . Physical channel sequence numbering is determined by the rate matching function and is described in [7]. + +![Diagram of a traffic burst structure showing Data symbols, Midamble, TPC field, Data symbols, and GP. The total length is 2560*Tc, and the Midamble length is 512/256 chips.](09955ff8214ffb6947951fc0f60eb6ab_img.jpg) + +The diagram illustrates the structure of a traffic burst. It consists of five segments: 'Data symbols', 'Midamble', 'TPC field' (indicated by a hatched box), 'Data symbols', and 'GP'. A double-headed arrow below the 'Data symbols' and 'Midamble' segments indicates a length of '512/256 chips'. A longer double-headed arrow at the bottom indicates the total burst length is '2560\*Tc'. A line labeled 'TPC field' points to the hatched box within the 'Midamble' segment. + +Diagram of a traffic burst structure showing Data symbols, Midamble, TPC field, Data symbols, and GP. The total length is 2560\*Tc, and the Midamble length is 512/256 chips. + +**Figure 11: Position of TPC information in the traffic burst** + +The length of the TPC field is $N_{TPC}$ bits. The TPC field is formed via repetition encoding a single bit $b_{TPC}$ , $N_{TPC}$ times. + +The relationship between $b_{TPC}$ and the TPC command is shown in table 4B. + +**Table 4B: TPC bit pattern** + +| $b_{TPC}$ | TPC command | Meaning | +|-----------|-------------|-------------------| +| 0 | 'Down' | Decrease Tx Power | +| 1 | 'Up' | Increase Tx Power | + +## 5.2.2.6 Timeslot formats + +### 5.2.2.6.1 Downlink timeslot formats + +The downlink timeslot format depends on the spreading factor, midamble length and on the number of the TFCI code word bits, as depicted in the table 5a. For MBSFN operation the timeslot format also depends upon the symbol modulation scheme used. Slot formats 20-27 are only applicable to MBSFN operation with burst type 4. + +Table 5a: Time slot formats for the Downlink + +| Slot Format # | Spreading Factor | Midamble length (chips) | N TFCI code word (bits) | Bits/slot | N Data/Slot (bits) | N data/data field (bits) | +|---------------|------------------|-------------------------|------------------------------------|-----------|-------------------------------|-------------------------------------| +| 0 | 16 | 512 | 0 | 244 | 244 | 122 | +| 1 | 16 | 512 | 4 | 244 | 240 | 120 | +| 2 | 16 | 512 | 8 | 244 | 236 | 118 | +| 3 | 16 | 512 | 16 | 244 | 228 | 114 | +| 4 | 16 | 512 | 32 | 244 | 212 | 106 | +| 5 | 16 | 256 | 0 | 276 | 276 | 138 | +| 6 | 16 | 256 | 4 | 276 | 272 | 136 | +| 7 | 16 | 256 | 8 | 276 | 268 | 134 | +| 8 | 16 | 256 | 16 | 276 | 260 | 130 | +| 9 | 16 | 256 | 32 | 276 | 244 | 122 | +| 10 | 1 | 512 | 0 | 3904 | 3904 | 1952 | +| 11 | 1 | 512 | 4 | 3904 | 3900 | 1950 | +| 12 | 1 | 512 | 8 | 3904 | 3896 | 1948 | +| 13 | 1 | 512 | 16 | 3904 | 3888 | 1944 | +| 14 | 1 | 512 | 32 | 3904 | 3872 | 1936 | +| 15 | 1 | 256 | 0 | 4416 | 4416 | 2208 | +| 16 | 1 | 256 | 4 | 4416 | 4412 | 2206 | +| 17 | 1 | 256 | 8 | 4416 | 4408 | 2204 | +| 18 | 1 | 256 | 16 | 4416 | 4400 | 2200 | +| 19 | 1 | 256 | 32 | 4416 | 4384 | 2192 | +| 20 (QPSK) | 16 | 320 | 0 | 264 | 264 | 132 | +| 21 (QPSK) | 16 | 320 | 16 | 264 | 248 | 124 | +| 22 (16QAM) | 16 | 320 | 0 | 528 | 528 | 264 | +| 23 (16QAM) | 16 | 320 | 16 | 528 | 512 | 256 | +| 24 (QPSK) | 1 | 320 | 0 | 4224 | 4224 | 2112 | +| 25 (QPSK) | 1 | 320 | 16 | 4224 | 4208 | 2104 | +| 26 (16QAM) | 1 | 320 | 0 | 8448 | 8448 | 4224 | +| 27 (16QAM) | 1 | 320 | 16 | 8448 | 8432 | 4216 | + +#### 5.2.2.6.2 Uplink timeslot formats + +The uplink timeslot format depends on the spreading factor, midamble length, guard period length and on the number of the TFCI code word bits. Due to TPC, different amount of bits are mapped to the two data fields. The timeslot formats are depicted in the table 5b. Note that slot format #90 shall only be used for HS\_SICH. + +**Table 5b: Timeslot formats for the Uplink** + +| Slot Format # | Spreading Factor | Midamble length (chips) | Guard Period (chips) | N TFCI code word (bits) | N TPC (bits) | Bits/slot | N data/Slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) | +|---------------|------------------|-------------------------|----------------------|------------------------------------|-------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------| +| 0 | 16 | 512 | 96 | 0 | 0 | 244 | 244 | 122 | 122 | +| 1 | 16 | 512 | 96 | 0 | 2 | 244 | 242 | 122 | 120 | +| 2 | 16 | 512 | 96 | 4 | 2 | 244 | 238 | 120 | 118 | +| 3 | 16 | 512 | 96 | 8 | 2 | 244 | 234 | 118 | 116 | +| 4 | 16 | 512 | 96 | 16 | 2 | 244 | 226 | 114 | 112 | +| 5 | 16 | 512 | 96 | 32 | 2 | 244 | 210 | 106 | 104 | +| 6 | 16 | 256 | 96 | 0 | 0 | 276 | 276 | 138 | 138 | +| 7 | 16 | 256 | 96 | 0 | 2 | 276 | 274 | 138 | 136 | +| 8 | 16 | 256 | 96 | 4 | 2 | 276 | 270 | 136 | 134 | +| 9 | 16 | 256 | 96 | 8 | 2 | 276 | 266 | 134 | 132 | +| 10 | 16 | 256 | 96 | 16 | 2 | 276 | 258 | 130 | 128 | +| 11 | 16 | 256 | 96 | 32 | 2 | 276 | 242 | 122 | 120 | +| 12 | 8 | 512 | 96 | 0 | 0 | 488 | 488 | 244 | 244 | +| 13 | 8 | 512 | 96 | 0 | 2 | 486 | 484 | 244 | 240 | +| 14 | 8 | 512 | 96 | 4 | 2 | 482 | 476 | 240 | 236 | +| 15 | 8 | 512 | 96 | 8 | 2 | 478 | 468 | 236 | 232 | +| 16 | 8 | 512 | 96 | 16 | 2 | 470 | 452 | 228 | 224 | +| 17 | 8 | 512 | 96 | 32 | 2 | 454 | 420 | 212 | 208 | +| 18 | 8 | 256 | 96 | 0 | 0 | 552 | 552 | 276 | 276 | +| 19 | 8 | 256 | 96 | 0 | 2 | 550 | 548 | 276 | 272 | +| 20 | 8 | 256 | 96 | 4 | 2 | 546 | 540 | 272 | 268 | +| 21 | 8 | 256 | 96 | 8 | 2 | 542 | 532 | 268 | 264 | +| 22 | 8 | 256 | 96 | 16 | 2 | 534 | 516 | 260 | 256 | +| 23 | 8 | 256 | 96 | 32 | 2 | 518 | 484 | 244 | 240 | +| 24 | 4 | 512 | 96 | 0 | 0 | 976 | 976 | 488 | 488 | +| 25 | 4 | 512 | 96 | 0 | 2 | 970 | 968 | 488 | 480 | +| 26 | 4 | 512 | 96 | 4 | 2 | 958 | 952 | 480 | 472 | +| 27 | 4 | 512 | 96 | 8 | 2 | 946 | 936 | 472 | 464 | +| 28 | 4 | 512 | 96 | 16 | 2 | 922 | 904 | 456 | 448 | +| 29 | 4 | 512 | 96 | 32 | 2 | 874 | 840 | 424 | 416 | +| 30 | 4 | 256 | 96 | 0 | 0 | 1104 | 1104 | 552 | 552 | +| 31 | 4 | 256 | 96 | 0 | 2 | 1098 | 1096 | 552 | 544 | +| 32 | 4 | 256 | 96 | 4 | 2 | 1086 | 1080 | 544 | 536 | +| 33 | 4 | 256 | 96 | 8 | 2 | 1074 | 1064 | 536 | 528 | +| 34 | 4 | 256 | 96 | 16 | 2 | 1050 | 1032 | 520 | 512 | +| 35 | 4 | 256 | 96 | 32 | 2 | 1002 | 968 | 488 | 480 | +| 36 | 2 | 512 | 96 | 0 | 0 | 1952 | 1952 | 976 | 976 | +| 37 | 2 | 512 | 96 | 0 | 2 | 1938 | 1936 | 976 | 960 | +| 38 | 2 | 512 | 96 | 4 | 2 | 1910 | 1904 | 960 | 944 | +| 39 | 2 | 512 | 96 | 8 | 2 | 1882 | 1872 | 944 | 928 | +| 40 | 2 | 512 | 96 | 16 | 2 | 1826 | 1808 | 912 | 896 | +| 41 | 2 | 512 | 96 | 32 | 2 | 1714 | 1680 | 848 | 832 | +| 42 | 2 | 256 | 96 | 0 | 0 | 2208 | 2208 | 1104 | 1104 | +| 43 | 2 | 256 | 96 | 0 | 2 | 2194 | 2192 | 1104 | 1088 | +| 44 | 2 | 256 | 96 | 4 | 2 | 2166 | 2160 | 1088 | 1072 | +| 45 | 2 | 256 | 96 | 8 | 2 | 2138 | 2128 | 1072 | 1056 | +| 46 | 2 | 256 | 96 | 16 | 2 | 2082 | 2064 | 1040 | 1024 | +| 47 | 2 | 256 | 96 | 32 | 2 | 1970 | 1936 | 976 | 960 | +| 48 | 1 | 512 | 96 | 0 | 0 | 3904 | 3904 | 1952 | 1952 | +| 49 | 1 | 512 | 96 | 0 | 2 | 3874 | 3872 | 1952 | 1920 | + +| Slot Format # | Spreading Factor | Midamble length (chips) | Guard Period (chips) | N TFCI code word (bits) | N TPC (bits) | Bits/slot | N Data/Slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) | +|---------------|------------------|-------------------------|----------------------|------------------------------------|-------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------| +| 50 | 1 | 512 | 96 | 4 | 2 | 3814 | 3808 | 1920 | 1888 | +| 51 | 1 | 512 | 96 | 8 | 2 | 3754 | 3744 | 1888 | 1856 | +| 52 | 1 | 512 | 96 | 16 | 2 | 3634 | 3616 | 1824 | 1792 | +| 53 | 1 | 512 | 96 | 32 | 2 | 3394 | 3360 | 1696 | 1664 | +| 54 | 1 | 256 | 96 | 0 | 0 | 4416 | 4416 | 2208 | 2208 | +| 55 | 1 | 256 | 96 | 0 | 2 | 4386 | 4384 | 2208 | 2176 | +| 56 | 1 | 256 | 96 | 4 | 2 | 4326 | 4320 | 2176 | 2144 | +| 57 | 1 | 256 | 96 | 8 | 2 | 4266 | 4256 | 2144 | 2112 | +| 58 | 1 | 256 | 96 | 16 | 2 | 4146 | 4128 | 2080 | 2048 | +| 59 | 1 | 256 | 96 | 32 | 2 | 3906 | 3872 | 1952 | 1920 | +| 60 | 16 | 512 | 192 | 0 | 0 | 232 | 232 | 122 | 110 | +| 61 | 16 | 512 | 192 | 0 | 2 | 232 | 230 | 122 | 108 | +| 62 | 16 | 512 | 192 | 4 | 2 | 232 | 226 | 120 | 106 | +| 63 | 16 | 512 | 192 | 8 | 2 | 232 | 222 | 118 | 104 | +| 64 | 16 | 512 | 192 | 16 | 2 | 232 | 214 | 114 | 100 | +| 65 | 16 | 512 | 192 | 32 | 2 | 232 | 198 | 106 | 92 | +| 66 | 8 | 512 | 192 | 0 | 0 | 464 | 464 | 244 | 220 | +| 67 | 8 | 512 | 192 | 0 | 2 | 462 | 460 | 244 | 216 | +| 68 | 8 | 512 | 192 | 4 | 2 | 458 | 452 | 240 | 212 | +| 69 | 8 | 512 | 192 | 8 | 2 | 454 | 444 | 236 | 208 | +| 70 | 8 | 512 | 192 | 16 | 2 | 446 | 428 | 228 | 200 | +| 71 | 8 | 512 | 192 | 32 | 2 | 430 | 396 | 212 | 184 | +| 72 | 4 | 512 | 192 | 0 | 0 | 928 | 928 | 488 | 440 | +| 73 | 4 | 512 | 192 | 0 | 2 | 922 | 920 | 488 | 432 | +| 74 | 4 | 512 | 192 | 4 | 2 | 910 | 904 | 480 | 424 | +| 75 | 4 | 512 | 192 | 8 | 2 | 898 | 888 | 472 | 416 | +| 76 | 4 | 512 | 192 | 16 | 2 | 874 | 856 | 456 | 400 | +| 77 | 4 | 512 | 192 | 32 | 2 | 826 | 792 | 424 | 368 | +| 78 | 2 | 512 | 192 | 0 | 0 | 1856 | 1856 | 976 | 880 | +| 79 | 2 | 512 | 192 | 0 | 2 | 1842 | 1840 | 976 | 864 | +| 80 | 2 | 512 | 192 | 4 | 2 | 1814 | 1808 | 960 | 848 | +| 81 | 2 | 512 | 192 | 8 | 2 | 1786 | 1776 | 944 | 832 | +| 82 | 2 | 512 | 192 | 16 | 2 | 1730 | 1712 | 912 | 800 | +| 83 | 2 | 512 | 192 | 32 | 2 | 1618 | 1584 | 848 | 736 | +| 84 | 1 | 512 | 192 | 0 | 0 | 3712 | 3712 | 1952 | 1760 | +| 85 | 1 | 512 | 192 | 0 | 2 | 3682 | 3680 | 1952 | 1728 | +| 86 | 1 | 512 | 192 | 4 | 2 | 3622 | 3616 | 1920 | 1696 | +| 87 | 1 | 512 | 192 | 8 | 2 | 3562 | 3552 | 1888 | 1664 | +| 88 | 1 | 512 | 192 | 16 | 2 | 3442 | 3424 | 1824 | 1600 | +| 89 | 1 | 512 | 192 | 32 | 2 | 3202 | 3168 | 1696 | 1472 | +| 90 | 16 | 512 | 96 | 0 | 8 | 244 | 236 | 122 | 114 | + +### 5.2.3 Training sequences for spread bursts + +In this subclause, the training sequences for usage as midambles in burst type 1, 2, 3 and 4 (see subclause 5.2.2) are defined. The training sequences, i.e. midambles, of different users active in the same cell and same time slot are cyclically shifted versions of one cell-specific single basic midamble code. In the case of MBSFN timeslots there is only a single midamble and this is derived from a single basic midamble code which is not necessarily cell-specific. The applicable basic midamble codes are given in Annex A.1 and A.2. As different basic midamble codes are required for different burst formats, the Annex A.1 shows the basic midamble codes $m_{PL}$ for burst type 1 and 3, and Annex A.2 + +shows $\mathbf{m}_{\text{PS}}$ for burst types 2 and 4. It should be noted that burst type 2 must not be mixed with burst type 1 or 3 in the same timeslot of one cell and furthermore burst type 4 shall not be mixed with any other burst type in the same timeslot of one cell. + +The basic midamble codes in Annex A.1 and A.2 are listed in hexadecimal notation. The binary form of the basic midamble code shall be derived according to table 6 below. + +**Table 6: Mapping of 4 binary elements $m_i$ on a single hexadecimal digit** + +| 4 binary elements
$m_i$ | Mapped on hexadecimal digit | +|----------------------------|-----------------------------| +| -1 -1 -1 -1 | 0 | +| -1 -1 -1 1 | 1 | +| -1 -1 1 -1 | 2 | +| -1 -1 1 1 | 3 | +| -1 1 -1 -1 | 4 | +| -1 1 -1 1 | 5 | +| -1 1 1 -1 | 6 | +| -1 1 1 1 | 7 | +| 1 -1 -1 -1 | 8 | +| 1 -1 -1 1 | 9 | +| 1 -1 1 -1 | A | +| 1 -1 1 1 | B | +| 1 1 -1 -1 | C | +| 1 1 -1 1 | D | +| 1 1 1 -1 | E | +| 1 1 1 1 | F | + +For each particular basic midamble code, its binary representation can be written as a vector $\mathbf{m}_P$ : + +$$\mathbf{m}_P = (m_1, m_2, \dots, m_P) \quad (1)$$ + +According to Annex A.1, the size of this vector $\mathbf{m}_P$ is $P=456$ for burst types 1 and 3. Annex A.2 is setting $P=192$ for burst types 2 and 4. As QPSK modulation is used, the training sequences are transformed into a complex form, denoted as the complex vector $\underline{\mathbf{m}}_P$ : + +$$\underline{\mathbf{m}}_P = (\underline{m}_1, \underline{m}_2, \dots, \underline{m}_P) \quad (2)$$ + +The elements $\underline{m}_i$ of $\underline{\mathbf{m}}_P$ are derived from elements $m_i$ of $\mathbf{m}_P$ using equation (3): + +$$\underline{m}_i = (j)^i \cdot m_i \text{ for all } i = 1, \dots, P \quad (3)$$ + +Hence, the elements $\underline{m}_i$ of the complex basic midamble code are alternating real and imaginary. + +To derive the required training sequences (different shifts), this vector $\underline{\mathbf{m}}_P$ is periodically extended to the size: + +$$i_{\max} = L_m + (K' - 1)W + \lceil P/K \rceil \quad (4)$$ + +Notes on equation (4): + +- $L_m$ : Midamble length +- $K'$ : Maximum number of different midamble shifts in a cell, when no intermediate shifts are used. This value depends on the midamble length. + +- K: Maximum number of different midamble shifts in a cell, when intermediate shifts are used, $K=2K'$ . This value depends on the midamble length. + +Note that intermediate shifts are not used for burst type 4, i.e $K=K'=1$ for burst type 4 + +- W: Shift between the midambles, when the number of midambles is $K'$ . + +- $\lfloor x \rfloor$ denotes the largest integer smaller or equal to x + +Allowed values for $L_m$ , $K'$ and W are given in Annex A.1 and A.2. + +So we obtain a new vector $\underline{m}$ containing the periodic basic midamble sequence: + +$$\underline{m} = (\underline{m}_1, \underline{m}_2, \dots, \underline{m}_{i_{\max}}) = (\underline{m}_1, \underline{m}_2, \dots, \underline{m}_{L_m + (K'-1)W + \lfloor P/K \rfloor}) \quad (5)$$ + +The first P elements of this vector $\underline{m}$ are the same ones as in vector $\underline{m}^P$ , the following elements repeat the beginning: + +$$\underline{m}_i = \underline{m}_{i-P} \text{ for the subset } i = (P+1), \dots, i_{\max} \quad (6)$$ + +Using this periodic basic midamble sequence $\underline{m}$ for each shift k a midamble $\underline{m}^{(k)}$ of length $L_m$ is derived, which can be written as a shift specific vector: + +$$\underline{m}^{(k)} = (\underline{m}_1^{(k)}, \underline{m}_2^{(k)}, \dots, \underline{m}_{L_m}^{(k)}) \quad (7)$$ + +The $L_m$ midamble elements $\underline{m}_i^{(k)}$ are generated for each midamble of the first $K'$ shifts ( $k = 1, \dots, K'$ ) based on: + +$$\underline{m}_i^{(k)} = \underline{m}_{i+(K'-k)W} \text{ with } i = 1, \dots, L_m \text{ and } k = 1, \dots, K' \quad (8)$$ + +The elements of midambles for the second $K'$ shifts ( $k = (K'+1), \dots, K = (K'+1), \dots, 2K'$ ) are generated based on a slight modification of this formula introducing intermediate shifts: + +$$\underline{m}_i^{(k)} = \underline{m}_{i+(K-k-1)W + \lfloor P/K \rfloor} \text{ with } i = 1, \dots, L_m \text{ and } k = K'+1, \dots, K-1 \quad (9)$$ + +$$\underline{m}_i^{(k)} = \underline{m}_{i+(K'-1)W + \lfloor P/K \rfloor} \text{ with } i = 1, \dots, L_m \text{ and } k = K \quad (10)$$ + +The number $K_{\text{Cell}}$ of midambles that is supported in each cell can be smaller than K, depending on the cell size and the possible delay spreads, see annex A. The number $K_{\text{Cell}}$ is signalled by higher layers. The midamble sequences derived according to equations (7) to (10) have complex values and are not subject to channelisation or scrambling process, i.e. + +the elements $\underline{m}_i^{(k)}$ represent complex chips for usage in the pulse shaping process at modulation. + +The term 'a midamble code set' or 'a midamble code family' denotes K specific midamble codes $\underline{m}^{(k)}$ ; $k=1, \dots, K$ , based on a single basic midamble code $\underline{m}^P$ according to (1). + +## 5.2.4 Beamforming + +When DL beamforming is used, at least that user to which beamforming is applied and which has a dedicated channel shall get one individual midamble according to subclause 5.2.3, even in DL. DL beamforming is not applied to timeslots containing burst type 4. + +## 5.3 Common physical channels + +### 5.3.1 Primary common control physical channel (P-CCPCH) + +The BCH as described in subclause 4.1.2 is mapped onto the Primary Common Control Physical Channel (P-CCPCH). The position (time slot / code) of the P-CCPCH is known from the Physical Synchronisation Channel (PSCH), see subclause 5.3.4. + +#### 5.3.1.1 P-CCPCH Spreading + +The P-CCPCH uses fixed spreading with a spreading factor $SF = 16$ as described in subclause 5.2.1.1. The P-CCPCH always uses channelisation code $c_{Q=16}^{(k=1)}$ . + +#### 5.3.1.2 P-CCPCH Burst Types + +The burst type 1 as described in subclause 5.2.2 is used for the P-CCPCH unless the entire carrier is dedicated to MBMSFN then burst type 4 is used for P-CCPCH. No TFCI is applied for the P-CCPCH. + +#### 5.3.1.3 P-CCPCH Training sequences + +The training sequences, i.e. midambles, as described in subclause 5.2.3 are used for the P-CCPCH. + +### 5.3.2 Secondary common control physical channel (S-CCPCH) + +PCH and FACH as described in subclause 4.1.2 are mapped onto one or more secondary common control physical channels (S-CCPCH). In this way the capacity of PCH and FACH can be adapted to the different requirements. + +#### 5.3.2.1 S-CCPCH Spreading + +The S-CCPCH uses fixed spreading with a spreading factor $SF = 16$ as described in subclause 5.2.1.1. When S-CCPCH is used for MBMSFN operation the spreading factor may be $SF = 16$ or $SF = 1$ . + +#### 5.3.2.2 S-CCPCH Burst Types + +The burst types 1,2 or 4 as described in subclause 5.2.2 are used for the S-CCPCHs. TFCI may be applied for S-CCPCHs. + +#### 5.3.2.2A S-CCPCH Modulation + +When S-CCPCH is used for MBMSFN operation, burst type 4 shall be used and the modulation may be QPSK or 16QAM, see table 5A for slot formats. When S-CCPCH is used for all other purposes the modulation shall be QPSK. + +#### 5.3.2.3 S-CCPCH Training sequences + +The training sequences, i.e. midambles, as described in subclause 5.2.3 are used for the S-CCPCH. + +### 5.3.3 The physical random access channel (PRACH) + +The RACH as described in subclause 4.1.2 is mapped onto one uplink physical random access channel (PRACH). + +#### 5.3.3.1 PRACH Spreading + +The uplink PRACH uses either spreading factor $SF=16$ or $SF=8$ as described in subclause 5.2.1.2. The set of admissible spreading codes for use on the PRACH and the associated spreading factors are broadcast on the BCH (within the RACH configuration parameters on the BCH). + +#### 5.3.3.2 PRACH Burst Type + +The UEs send uplink access bursts of type 3 randomly in the PRACH. TFCI and TPC are not applied for the PRACH. + +### 5.3.3.3 PRACH Training sequences + +The training sequences, i.e. midambles, of different users active in the same time slot are time shifted versions of a single periodic basic code. The basic midamble codes for burst type 3 are shown in Annex A. The necessary time shifts are obtained by choosing either *all* $k=1,2,3,\dots,K'$ (for cells with small radius) or *uneven* $k=1,3,5,\dots\leq K'$ (for cells with large radius). Different cells use different periodic basic codes, i.e. different midamble sets. + +For cells with large radius additional midambles may be derived from the time-inverted Basic Midamble Sequence. Thus, the second Basic Midamble Code $m_2$ is the time inverted version of Basic Midamble Code $m_1$ . + +In this way, a joint channel estimation for the channel impulse responses of all active users within one time slot can be performed by a maximum of two cyclic correlations (in cells with small radius, a single cyclic correlator suffices). The different user specific channel impulse response estimates are obtained sequentially in time at the output of the cyclic correlators. + +### 5.3.3.4 PRACH timeslot formats + +For the PRACH the timeslot format is only spreading factor dependent. The timeslot formats 60 and 66 of table 5b are applicable for the PRACH. + +### 5.3.3.5 Association between Training Sequences and Channelisation Codes + +For the PRACH there exists a fixed association between the training sequence and the channelisation code. The generic rule to define this association is based on the order of the channelisation codes $c_Q^{(k)}$ given by $k$ and the order of the midambles $m_j^{(k)}$ given by $k$ , firstly, and $j$ , secondly, with the constraint that the midamble for a spreading factor $Q$ is the same as in the upper branch for the spreading factor $2Q$ . The index $j=1$ or $2$ indicates whether the original Basic Midamble Sequence ( $j=1$ ) or the time-inverted Basic Midamble Sequence is used ( $j=2$ ). + +- For the case that all $k$ are allowed and only one periodic basic code $m_1$ is available for the RACH, the association depicted in figure 12 is straightforward. +- For the case that only odd $k$ are allowed the principle of the association is shown in figure 13. This association is applied for one and two basic periodic codes. + +![A hierarchical tree diagram showing the association of Midambles to Channelisation Codes in an OVSF tree. The tree branches from left to right. The rightmost nodes are grouped into pairs. The top half of the tree shows nodes branching from $c_8$ to $c_{16}$ codes. The bottom half shows nodes at the $c_8$ level. Specific labels include $m_1^{(1)} - c_8^{(1)}$ branching to $m_1^{(1)} - c_{16}^{(1)}$ and $m_1^{(2)} - c_{16}^{(2)}$, and so on down the tree.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +The diagram illustrates an OVSF tree structure for associating Midambles to Channelisation Codes. The tree structure is as follows: + +- Top branch level 1 nodes: $m_1^{(1)} - c_8^{(1)}$ and $m_1^{(3)} - c_8^{(2)}$ +- Top branch level 2 (leaf) nodes: $m_1^{(1)} - c_{16}^{(1)}$ , $m_1^{(2)} - c_{16}^{(2)}$ , $m_1^{(3)} - c_{16}^{(3)}$ , $m_1^{(4)} - c_{16}^{(4)}$ +- Middle branch level 1 nodes: $m_1^{(5)} - c_8^{(3)}$ and $m_1^{(7)} - c_8^{(4)}$ +- Middle branch level 2 (leaf) nodes: $m_1^{(5)} - c_{16}^{(5)}$ , $m_1^{(6)} - c_{16}^{(6)}$ , $m_1^{(7)} - c_{16}^{(7)}$ , $m_1^{(8)} - c_{16}^{(8)}$ +- Bottom branch level 1 nodes: $m_1^{(2)} - c_8^{(5)}$ , $m_1^{(4)} - c_8^{(6)}$ , $m_1^{(6)} - c_8^{(7)}$ , and $m_1^{(8)} - c_8^{(8)}$ + +A hierarchical tree diagram showing the association of Midambles to Channelisation Codes in an OVSF tree. The tree branches from left to right. The rightmost nodes are grouped into pairs. The top half of the tree shows nodes branching from \$c\_8\$ to \$c\_{16}\$ codes. The bottom half shows nodes at the \$c\_8\$ level. Specific labels include \$m\_1^{(1)} - c\_8^{(1)}\$ branching to \$m\_1^{(1)} - c\_{16}^{(1)}\$ and \$m\_1^{(2)} - c\_{16}^{(2)}\$, and so on down the tree. + +Figure 12: Association of Midambles to Channelisation Codes in the OVSF tree for all $k$ + +![Figure 13: Association of Midambles to Channelisation Codes in the OVSF tree for odd k. The diagram shows a hierarchical tree structure starting from a single root on the left. The tree branches out to the right, with nodes labeled with midamble and channelisation code pairs. The labels are in the format m_i^{(j)} - c_8^{(k)} or m_i^{(j)} - c_{16}^{(k)}. The tree has four main branches from the root. The top branch leads to a node m_1^{(1)} - c_8^{(1)}, which further branches into m_1^{(1)} - c_{16}^{(1)} and m_1^{(3)} - c_{16}^{(2)}. The second main branch leads to a node m_1^{(5)} - c_8^{(2)}, which branches into m_1^{(5)} - c_{16}^{(3)} and m_1^{(7)} - c_{16}^{(4)}. The third main branch leads to a node m_2^{(1)} - c_8^{(3)}, which branches into m_2^{(1)} - c_{16}^{(5)} and m_2^{(3)} - c_{16}^{(6)}. The fourth main branch leads to a node m_2^{(5)} - c_8^{(4)}, which branches into m_2^{(5)} - c_{16}^{(7)} and m_2^{(7)} - c_{16}^{(8)}. Below these, there are more branches leading to nodes m_1^{(3)} - c_8^{(5)}, m_1^{(7)} - c_8^{(6)}, m_2^{(3)} - c_8^{(7)}, and m_2^{(7)} - c_8^{(8)}, each of which has two further branches that are partially cut off by the right edge of the diagram.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +Figure 13: Association of Midambles to Channelisation Codes in the OVSF tree for odd k. The diagram shows a hierarchical tree structure starting from a single root on the left. The tree branches out to the right, with nodes labeled with midamble and channelisation code pairs. The labels are in the format m\_i^{(j)} - c\_8^{(k)} or m\_i^{(j)} - c\_{16}^{(k)}. The tree has four main branches from the root. The top branch leads to a node m\_1^{(1)} - c\_8^{(1)}, which further branches into m\_1^{(1)} - c\_{16}^{(1)} and m\_1^{(3)} - c\_{16}^{(2)}. The second main branch leads to a node m\_1^{(5)} - c\_8^{(2)}, which branches into m\_1^{(5)} - c\_{16}^{(3)} and m\_1^{(7)} - c\_{16}^{(4)}. The third main branch leads to a node m\_2^{(1)} - c\_8^{(3)}, which branches into m\_2^{(1)} - c\_{16}^{(5)} and m\_2^{(3)} - c\_{16}^{(6)}. The fourth main branch leads to a node m\_2^{(5)} - c\_8^{(4)}, which branches into m\_2^{(5)} - c\_{16}^{(7)} and m\_2^{(7)} - c\_{16}^{(8)}. Below these, there are more branches leading to nodes m\_1^{(3)} - c\_8^{(5)}, m\_1^{(7)} - c\_8^{(6)}, m\_2^{(3)} - c\_8^{(7)}, and m\_2^{(7)} - c\_8^{(8)}, each of which has two further branches that are partially cut off by the right edge of the diagram. + +Figure 13: Association of Midambles to Channelisation Codes in the OVSF tree for odd $k$ + +### 5.3.4 The synchronisation channel (SCH) + +In TDD mode code group of a cell can be derived from the synchronisation channel. In order not to limit the uplink/downlink asymmetry the SCH is mapped on one or two downlink slots per frame only. + +There are two cases of SCH and P-CCPCH allocation as follows: + +- Case 1) SCH and P-CCPCH allocated in TS# $k$ , $k=0\dots 14$ +- Case 2) SCH allocated in two TS: TS# $k$ and TS# $k+8$ , $k=0\dots 6$ ; P-CCPCH allocated in TS# $k$ . + +Only case 1 is supported in the case that the entire carrier is dedicated to MBSFN. + +The position of SCH (value of $k$ ) in frame can change on a long term basis in any case. + +Due to this SCH scheme, the position of P-CCPCH is known from the SCH. + +Figure 14 is an example for transmission of SCH, $k=0$ , of Case 2. + +![Figure 14: Scheme for Synchronisation channel SCH. The diagram shows a frame structure with 10 subframes, where subframes 0 and 5 are highlighted. A zoomed-in view of a subframe shows a primary sequence C_p and three parallel secondary sequences b_i C_{s,i} (i=1,2,3). The primary sequence C_p has a length of 256 chips and a power level P_p. The secondary sequences have a total power level P_s, divided into three parallel sequences with power levels P_s/3 each. The time offset t_offset,n is indicated between the start of the subframe and the start of the sequences. The duration of a time slot is given as 2560 * T_c.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +Figure 14: Scheme for Synchronisation channel SCH. The diagram shows a frame structure with 10 subframes, where subframes 0 and 5 are highlighted. A zoomed-in view of a subframe shows a primary sequence C\_p and three parallel secondary sequences b\_i C\_{s,i} (i=1,2,3). The primary sequence C\_p has a length of 256 chips and a power level P\_p. The secondary sequences have a total power level P\_s, divided into three parallel sequences with power levels P\_s/3 each. The time offset t\_offset,n is indicated between the start of the subframe and the start of the sequences. The duration of a time slot is given as 2560 \* T\_c. + +$$b_i \in \{ \frac{1}{2}, -\frac{1}{2} \}, C_{s,i} \in \{ C_0, C_1, C_3, C_4, C_5, C_6, C_8, C_{10}, C_{12}, C_{13}, C_{14}, C_{15} \}, i=1,2,3; \text{ see [8]}$$ + +**Figure 14: Scheme for Synchronisation channel SCH consisting of one primary sequence $C_p$ and 3 parallel secondary sequences $C_{s,i}$ in slot $k$ and $k+8$ (example for $k=0$ in Case 2)** + +As depicted in figure 14, the SCH consists of a primary and three secondary code sequences each 256 chips long. The primary and secondary code sequences are defined in [8] clause 7 'Synchronisation codes for the 3.84 Mcps option'. + +Due to mobile to mobile interference, it is mandatory for public TDD systems to keep synchronisation between base stations. As a consequence of this, a capture effect concerning SCH can arise. The time offset $t_{offset,n}$ enables the system to overcome the capture effect. + +The time offset $t_{offset,n}$ is one of 32 values, depending on the code group of the cell, $n$ , cf. 'table 6 Mapping scheme for Cell Parameters, Code Groups, Scrambling Codes, Midambles and $t_{offset}$ ' in [8]. Note that the cell parameter will change from frame to frame, cf. 'Table 7 Alignment of cell parameter cycling and system frame number' in [8], but the cell will belong to only one code group and thus have one time offset $t_{offset,n}$ . The exact value for $t_{offset,n}$ , regarding column 'Associated $t_{offset}$ ' in table 6 in [8] is given by: + +$$t_{offset,n} = \begin{cases} n \cdot 48 \cdot T_c & n < 16 \\ (720 + n \cdot 48) T_c & n \geq 16 \end{cases}; \quad n = 0, \dots, 31$$ + +### 5.3.5 Physical Uplink Shared Channel (PUSCH) + +The USCH as described in subclause 4.1.2 is mapped onto one or more physical uplink shared channels (PUSCH). Timing advance, as described in [9], subclause 4.3, is applied to the PUSCH. + +#### 5.3.5.1 PUSCH Spreading + +The spreading factors that can be applied to the PUSCH are $SF = 1, 2, 4, 8, 16$ as described in subclause 5.2.1.2. + +#### 5.3.5.2 PUSCH Burst Types + +Burst types 1, 2 or 3 as described in subclause 5.2.2 can be used for PUSCH. TFCI and TPC can be transmitted on the PUSCH. + +### 5.3.5.3 PUSCH Training Sequences + +The training sequences as described in subclause 5.2.3 are used for the PUSCH. + +### 5.3.5.4 UE Selection + +The UE that shall transmit on the PUSCH is selected by higher layer signalling. + +## 5.3.6 Physical Downlink Shared Channel (PDSCH) + +The DSCH as described in subclause 4.1.2 is mapped onto one or more physical downlink shared channels (PDSCH). + +### 5.3.6.1 PDSCH Spreading + +The PDSCH uses either spreading factor $SF = 16$ or $SF = 1$ as described in subclause 5.2.1.1. + +### 5.3.6.2 PDSCH Burst Types + +Burst types 1 or 2 as described in subclause 5.2.2 can be used for PDSCH. TFCI can be transmitted on the PDSCH. + +### 5.3.6.3 PDSCH Training Sequences + +The training sequences as described in subclause 5.2.3 are used for the PDSCH. + +### 5.3.6.4 UE Selection + +To indicate to the UE that there is data to decode on the DSCH, three signalling methods are available: + +- 1) using the TFCI field of the associated channel or PDSCH; +- 2) using on the DSCH user specific midamble derived from the set of midambles used for that cell; +- 3) using higher layer signalling. + +When the midamble based method is used, the UE specific midamble allocation method shall be employed (see subclause 5.6), and the UE shall decode the PDSCH if the PDSCH was transmitted with the midamble assigned to the UE by UTRAN. For this method no other physical channels may use the same time slot as the PDSCH and only one UE may share the PDSCH time slot within one TTI. + +Note: From the above mentioned signalling methods, only the higher layer signalling method is supported by higher layers in this release. + +## 5.3.7 The Paging Indicator Channel (PICH) + +The Paging Indicator Channel (PICH) is a physical channel used to carry the paging indicators. + +### 5.3.7.1 Mapping of Paging Indicators to the PICH bits + +Figure 15 depicts the structure of a PICH burst and the numbering of the bits within the burst. The same burst type is used for the PICH in every cell. $N_{PIB}$ bits in a normal burst of type 1 or 2 are used to carry the paging indicators, where $N_{PIB}$ depends on the burst type: $N_{PIB}=240$ for burst type 1 and $N_{PIB}=272$ for burst type 2. The bits $s_{N_{PIB}+1}, \dots, s_{N_{PIB}+4}$ adjacent to the midamble are reserved for possible future use. + +![Diagram of Figure 15: Transmission and numbering of paging indicator carrying bits in a PICH burst. The diagram shows a '1 Time Slot' structure. It is divided into three main functional areas: 'Bits for Page Indication' on the left, 'Reserved Bits' in the center surrounding a 'Midamble', and 'Bits for Page Indication' on the right followed by a 'Guard Period'. Specific bit indices are labeled: s1, s3, ..., s_{N_{PIB}-1} on the left; s_{N_{PIB}+1}, s_{N_{PIB}+3} to the left of the midamble; s_{N_{PIB}+2}, s_{N_{PIB}+4} to the right of the midamble; and s2, s4, ..., s_{N_{PIB}} on the right side.](768942719f8a9b0d82888157aee1bae4_img.jpg) + +Diagram of Figure 15: Transmission and numbering of paging indicator carrying bits in a PICH burst. The diagram shows a '1 Time Slot' structure. It is divided into three main functional areas: 'Bits for Page Indication' on the left, 'Reserved Bits' in the center surrounding a 'Midamble', and 'Bits for Page Indication' on the right followed by a 'Guard Period'. Specific bit indices are labeled: s1, s3, ..., s\_{N\_{PIB}-1} on the left; s\_{N\_{PIB}+1}, s\_{N\_{PIB}+3} to the left of the midamble; s\_{N\_{PIB}+2}, s\_{N\_{PIB}+4} to the right of the midamble; and s2, s4, ..., s\_{N\_{PIB}} on the right side. + +Figure 15: Transmission and numbering of paging indicator carrying bits in a PICH burst + +Each paging indicator $P_q$ in one time slot is mapped to the bits $\{s_{2L_{PI} \cdot q+1}, \dots, s_{2L_{PI} \cdot (q+1)}}\}$ within this time slot. Thus, due to the interleaved transmission of the bits half of the symbols used for each paging indicator are transmitted in the first data part, and the other half of the symbols are transmitted in the second data part, as exemplary shown in figure 16 for a paging indicator length $L_{PI}$ of 4 symbols. + +![Figure 16: Example of mapping of paging indicators on PICH bits for L_PI=4. The diagram shows two identical time slot structures. Each slot has a total duration of 2560 T_C. It contains a 'Midamble (256 Chips)' block, '2 unused symbols', and a 'GP' (Guard Period) block. The first slot shows mapping for P_0 and P_33. The second slot shows mapping for P_0 and P_29. Arrows indicate the mapping of bits from the indicators into the data parts of the slot.](9870bf462aa0d916a16d14b5a100c60a_img.jpg) + +Figure 16: Example of mapping of paging indicators on PICH bits for L\_PI=4. The diagram shows two identical time slot structures. Each slot has a total duration of 2560 T\_C. It contains a 'Midamble (256 Chips)' block, '2 unused symbols', and a 'GP' (Guard Period) block. The first slot shows mapping for P\_0 and P\_33. The second slot shows mapping for P\_0 and P\_29. Arrows indicate the mapping of bits from the indicators into the data parts of the slot. + +**Figure 16: Example of mapping of paging indicators on PICH bits for $L_{PI}=4$** + +The setting of the paging indicators and the corresponding PICH bits (including the reserved ones) is described in [7]. + +$N_{PI}$ paging indicators of length $L_{PI}=2$ , $L_{PI}=4$ or $L_{PI}=8$ symbols are transmitted in each radio frame that contains the PICH. The number of paging indicators $N_{PI}$ per radio frame is given by the paging indicator length and the burst type, which are both known by higher layer signalling. In table 7 this number is shown for the different possibilities of burst types and paging indicator lengths. + +**Table 7: Number $N_{PI}$ of paging indicators per time slot for the different burst types and paging indicator lengths $L_{PI}$** + +| | $L_{PI}=2$ | $L_{PI}=4$ | $L_{PI}=8$ | +|--------------|-------------|-------------|-------------| +| Burst Type 1 | $N_{PI}=60$ | $N_{PI}=30$ | $N_{PI}=15$ | +| Burst Type 2 | $N_{PI}=68$ | $N_{PI}=34$ | $N_{PI}=17$ | + +### 5.3.7.2 Structure of the PICH over multiple radio frames + +As shown in figure 17, the paging indicators of $N_{PICH}$ consecutive frames form a PICH block, $N_{PICH}$ is configured by higher layers. Thus, $N_P = N_{PICH} \cdot N_{PI}$ paging indicators are transmitted in each PICH block. + +![Figure 17: Structure of a PICH block. The diagram shows a horizontal sequence of frames labeled '1 PICH Block' with a double-headed arrow above it. The frames are numbered 'Frame #' from 0 to N_PICH-1. Each frame contains a set of paging indicators P_0, ..., P_{N_{PI}-1}. The frames are shown as a sequence of boxes: [P_0, ..., P_{N_{PI}-1}] for frame 0, [P_0, ..., P_{N_{PI}-1}] for frame 1, an ellipsis for intermediate frames, [P_0, ..., P_{N_{PI}-1}] for frame N_PICH-2, and [P_0, ..., P_{N_{PI}-1}] for frame N_PICH-1.](4b587081b669e7c6695b0e5db5ea7f6d_img.jpg) + +Figure 17: Structure of a PICH block. The diagram shows a horizontal sequence of frames labeled '1 PICH Block' with a double-headed arrow above it. The frames are numbered 'Frame #' from 0 to N\_PICH-1. Each frame contains a set of paging indicators P\_0, ..., P\_{N\_{PI}-1}. The frames are shown as a sequence of boxes: [P\_0, ..., P\_{N\_{PI}-1}] for frame 0, [P\_0, ..., P\_{N\_{PI}-1}] for frame 1, an ellipsis for intermediate frames, [P\_0, ..., P\_{N\_{PI}-1}] for frame N\_PICH-2, and [P\_0, ..., P\_{N\_{PI}-1}] for frame N\_PICH-1. + +**Figure 17: Structure of a PICH block** + +The value PI ( $PI = 0, \dots, N_P-1$ ) calculated by higher layers for use for a certain UE, see [15], is associated to the paging indicator $P_q$ in the nth frame of one PICH block, where q is given by + +$$q = PI \bmod N_{PI}$$ + +and n is given by + +$$n = PI \bdiv N_{PI}$$ + +The PI bitmap in the PCH data frames over Iub contains indication values for all possible higher layer PI values, see [17]. Each bit in the bitmap indicates if the paging indicator $P_q$ associated with that particular PI shall be set to 0 or 1. Hence, the calculation in the formulas above is to be performed in Node B to make the association between PI and $P_q$ . + +### 5.3.7.3 PICH Training sequences + +The training sequences, i.e. midambles for the PICH, are generated as described in subclause 5.2.3. The allocation of midambles depends on whether SCTD is applied to the PICH. + +- If no antenna diversity is applied the PICH the midambles can be allocated as described in subclause 5.6. +- If SCTD antenna diversity is applied to the PICH the allocation of midambles shall be as described in [9]. + +## 5.3.8 The physical node B synchronisation channel (PNBSCH) + +In case cell sync bursts are used for Node B synchronisation the PNBSCH shall be used for the transmission of the cell sync burst [8]. The PNBSCH shall be mapped on the same timeslot as the PRACH acc. to a higher layer schedule. The cell sync burst shall be transmitted at the beginning of a timeslot. In case of Node B synchronisation via the air interface the transmission of a RACH may be prohibited on higher layer command in specified frames and timeslots. + +![Diagram of a timeslot structure for PNBSCH. It shows a 'Cell Sync Burst' of 2304 chips followed by a 'GP' (Guard Period) of 256 chips. The total duration of the timeslot is indicated as 2560 * Tc.](409498e57b1f988b2b604d12cd997002_img.jpg) + +| | | +|-------------------------------|-----------------| +| Cell Sync Burst
2304 chips | GP
256 chips | +|-------------------------------|-----------------| + +2560 \* Tc + +Diagram of a timeslot structure for PNBSCH. It shows a 'Cell Sync Burst' of 2304 chips followed by a 'GP' (Guard Period) of 256 chips. The total duration of the timeslot is indicated as 2560 \* Tc. + +## 5.3.9 High Speed Physical Downlink Shared Channel (HS-PDSCH) + +The HS-DSCH as described in subclause 4.1.2 is mapped onto one or more high speed physical downlink shared channels (HS-PDSCH). + +### 5.3.9.1 HS-PDSCH Spreading + +The HS-PDSCH shall use either spreading factor SF = 16 or SF=1, as described in 5.2.1.1. + +### 5.3.9.2 HS-PDSCH Burst Types + +Burst types 1 or 2 as described in subclause 5.2.2 can be used for PDSCH. TFCI shall not be transmitted on the HS-PDSCH. The TF of the HS-DSCH is derived from the associated HS-SCCH. + +### 5.3.9.3 HS-PDSCH Training Sequences + +The training sequences as described in subclause 5.2.3 are used for the HS-PDSCH. + +### 5.3.9.4 UE Selection + +To indicate to the UE that there is data to decode on the HS-DSCH, the UE id on the associated HS-SCCH shall be used. + +### 5.3.9.5 HS-PDSCH timeslot formats + +An HS-PDSCH may use QPSK or 16QAM modulation symbols. The time slot formats are shown in table 7A. + +Table 7A: Time slot formats for the HS-PDSCH + +| Slot Format # | Spreading Factor | Midamble length (chips) | N TFCI code word (bits) | Bits/slot | N Data/Slot (bits) | N data/data field (bits) | +|---------------|------------------|-------------------------|------------------------------------|-----------|-------------------------------|-------------------------------------| +| 0 (QPSK) | 16 | 512 | 0 | 244 | 244 | 122 | +| 1 (16QAM) | 16 | 512 | 0 | 488 | 488 | 244 | +| 2 (QPSK) | 16 | 256 | 0 | 276 | 276 | 138 | +| 3 (16QAM) | 16 | 256 | 0 | 552 | 552 | 276 | +| 4 (QPSK) | 1 | 512 | 0 | 3904 | 3904 | 1952 | +| 5 (16QAM) | 1 | 512 | 0 | 7808 | 7808 | 3904 | +| 6 (QPSK) | 1 | 256 | 0 | 4416 | 4416 | 2208 | +| 7 (16QAM) | 1 | 256 | 0 | 8832 | 8832 | 4416 | + +## 5.3.10 Shared Control Channel for HS-DSCH (HS-SCCH) + +The HS-SCCH is a DL physical channel that carries higher layer control information for HS-DSCH. The physical layer will process this information according to [7] and will transmit the resulting bits on the HS-SCCH the structure of which is described below. + +### 5.3.10.1 HS-SCCH Spreading + +The HS-SCCH shall use spreading factor $SF = 16$ , as described in 5.2.1.1. + +### 5.3.10.2 HS-SCCH Burst Types + +Burst type 1 as described in subclause 5.2.2 can be used for HS-SCCH. TFCI shall not be transmitted on the HS-SCCH. + +### 5.3.10.3 HS-SCCH Training Sequences + +The training sequences as described in subclause 5.2.3 are used for the HS-SCCH. + +### 5.3.10.4 HS-SCCH timeslot formats + +The HS-SCCH always uses time slot format #0 from table 5a, see section 5.2.2.6.1. + +## 5.3.11 Shared Information Channel for HS-DSCH (HS-SICH) + +The HS-SICH is a UL physical channel that carries higher layer control information and the Channel Quality Indicator CQI for HS-DSCH. The physical layer will process this information according to [7] and will transmit the resulting bits on the HS-SICH the structure of which is described below. + +### 5.3.11.1 HS-SICH Spreading + +The HS-SICH shall use spreading factor $SF = 16$ , as described in 5.2.1.2. + +### 5.3.11.2 HS-SICH Burst Types + +Burst type 1 as described in subclause 5.2.2 can be used for HS-SICH. TFCI shall not be transmitted on the HS-SICH, however, the HS-SICH shall carry TPC information. + +### 5.3.11.3 HS-SICH Training Sequences + +The training sequences as described in subclause 5.2.3 are used for the HS-SICH. + +### 5.3.11.4 HS-SICH timeslot formats + +The HS-SICH shall use time slot format #90 from table 5b, see section 5.2.2.6.2. + +## 5.3.12 The MBMS Indicator Channel (MICH) + +The MBMS Indicator Channel (MICH) is a physical channel used to carry the MBMS notification indicators. The UE may use multiple MICH within the MBMS modification period in order to make decisions on individual MBMS notification indicators. + +### 5.3.12.1 Mapping of MBMS Indicators to the MICH bits for burst types 1 and 2 + +Figure 17a depicts the structure of a MICH burst and the numbering of the bits within the burst. The same burst type is used for the MICH in every cell. $N_{\text{NIB}}$ bits in a normal burst of type 1 or 2 are used to carry the MBMS notification indicators, where $N_{\text{NIB}}$ depends on the burst type: $N_{\text{NIB}}=240$ for burst type 1 and $N_{\text{NIB}}=272$ for burst type 2. The bits $s_{N_{\text{NIB}}+1}, \dots, s_{N_{\text{NIB}}+4}$ adjacent to the midamble are reserved for possible future use. + +![Figure 17a: Transmission and numbering of MBMS notification indicator carrying bits in a MICH burst using burst types 1 and 2. The diagram shows a '1 Time Slot' containing several bit groups. From left to right: 'Bits for Notification Indication' (bits S1, S3, ..., S_NNIB-1), 'Reserved Bits' (bits S_NNIB+1, S_NNIB+3, which are part of the 'Midamble'), 'Midamble', 'Reserved Bits' (bits S_NNIB+2, S_NNIB+4, which are part of the 'Midamble'), 'Bits for Notification Indication' (bits S2, S4, ..., S_NNIB), and a 'Guard Period'. Arrows indicate the mapping of notification indicators to specific bit positions.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +Figure 17a: Transmission and numbering of MBMS notification indicator carrying bits in a MICH burst using burst types 1 and 2. The diagram shows a '1 Time Slot' containing several bit groups. From left to right: 'Bits for Notification Indication' (bits S1, S3, ..., S\_NNIB-1), 'Reserved Bits' (bits S\_NNIB+1, S\_NNIB+3, which are part of the 'Midamble'), 'Midamble', 'Reserved Bits' (bits S\_NNIB+2, S\_NNIB+4, which are part of the 'Midamble'), 'Bits for Notification Indication' (bits S2, S4, ..., S\_NNIB), and a 'Guard Period'. Arrows indicate the mapping of notification indicators to specific bit positions. + +**Figure 17a: Transmission and numbering of MBMS notification indicator carrying bits in a MICH burst using burst types 1 and 2** + +Each notification indicator $N_q$ in one time slot is mapped to the bits $\{S_{2LNI*q+1}, \dots, S_{2LNI*(q+1)}\}$ within this time slot. Thus, due to the interleaved transmission of the bits half of the symbols used for each MBMS notification indicator are transmitted in the first data part, and the other half of the symbols are transmitted in the second data part: an example is shown in figure 17b for a MBMS notification indicator length $L_{NI}$ of 4 symbols. + +![Figure 17b: Example of mapping of MBMS notification indicators on MICH bits for L_NI=4 for burst types 2 and 1 respectively. The diagram shows two side-by-side representations of a 2560T_C time slot. Each slot contains a 'Midamble (256 Chips)' and a 'GP' (Guard Period). Between the midamble and GP, there are '2 unused symbols'. On the left (Burst Type 2), notification indicators N0 and N33 are shown. On the right (Burst Type 1), notification indicators N0 and N29 are shown. Arrows indicate the mapping of these indicators to specific bit positions within the slot.](5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg) + +Figure 17b: Example of mapping of MBMS notification indicators on MICH bits for L\_NI=4 for burst types 2 and 1 respectively. The diagram shows two side-by-side representations of a 2560T\_C time slot. Each slot contains a 'Midamble (256 Chips)' and a 'GP' (Guard Period). Between the midamble and GP, there are '2 unused symbols'. On the left (Burst Type 2), notification indicators N0 and N33 are shown. On the right (Burst Type 1), notification indicators N0 and N29 are shown. Arrows indicate the mapping of these indicators to specific bit positions within the slot. + +**Figure 17b: Example of mapping of MBMS notification indicators on MICH bits for $L_{NI}=4$ for burst types 2 and 1 respectively** + +The setting of the MBMS notification indicators and the corresponding MICH bits (including the reserved ones) is described in [7]. + +$N_n$ MBMS notification indicators of length $L_{NI}=2$ , $L_{NI}=4$ or $L_{NI}=8$ symbols are transmitted in each MICH. The number of MBMS notification indicators $N_n$ per MICH is given by the MBMS notification indicator length and the burst type, which are both known by higher layer signalling. In table 7B this number is shown for burst types 1 and 2 and differing MBMS notification indicator lengths. + +**Table 7B: Number $N_n$ of MBMS notification indicators per time slot for the different burst types 1 and 2 and differing MBMS notification indicator lengths $L_{NI}$** + +| | $L_{NI}=2$ | $L_{NI}=4$ | $L_{NI}=8$ | +|--------------|------------|------------|------------| +| Burst Type 1 | $N_n=60$ | $N_n=30$ | $N_n=15$ | +| Burst Type 2 | $N_n=68$ | $N_n=34$ | $N_n=17$ | + +The value NI ( $NI = 0, \dots, N_{NI}-1$ ) calculated by higher layers, is associated to the MBMS notification indicator $N_q$ , where $q = NI \bmod N_n$ . + +The set of NI passed over the Iub indicates all higher layer NI values for which the notification indicator on MICH should be set to 1 during the corresponding modification period; all other indicators shall be set to 0. + +### 5.3.12.1A Mapping of MBMS Indicators to the MICH bits for burst type 4 + +When an entire carrier is dedicated to MBSFN operation, the MICH shall use burst type 4. In this case $N_{NIB}=256$ and there are 8 reserved/unused bits adjacent to the midamble reserved for possible future use. The transmission and numbering of MBMS notification indicator carrying bits in a MICH burst is similar to that of figure 17a with the + +exception of 4 reserved bits either side of the midamble as opposed to 2 for burst types 1 and 2. An example mapping is shown in figure 17ba for a MBMS notification indicator length $L_{NI}$ of 4 symbols. + +![Figure 17ba: Example of mapping of MBMS notification indicators on MICH bits for L_NI=4 for burst type 4. The diagram shows a horizontal bar representing a burst of 2560 T_c. It is divided into several segments. From left to right: a segment labeled N_0, a segment with '....', a segment labeled N_31, a shaded segment labeled 'Midamble (320 Chips)', a segment labeled '4 unused symbols', another segment with '....', and a final segment. The total length is indicated as 2560 T_c.](b58cedaf15ad4f0edee5621820865ccc_img.jpg) + +Figure 17ba: Example of mapping of MBMS notification indicators on MICH bits for L\_NI=4 for burst type 4. The diagram shows a horizontal bar representing a burst of 2560 T\_c. It is divided into several segments. From left to right: a segment labeled N\_0, a segment with '....', a segment labeled N\_31, a shaded segment labeled 'Midamble (320 Chips)', a segment labeled '4 unused symbols', another segment with '....', and a final segment. The total length is indicated as 2560 T\_c. + +**Figure 17ba: Example of mapping of MBMS notification indicators on MICH bits for $L_{NI}=4$ for burst type 4** + +The setting of the MBMS notification indicators and the corresponding MICH bits (including the reserved ones) is described in [7]. + +$N_n$ MBMS notification indicators of length $L_{NI}=2$ , $L_{NI}=4$ or $L_{NI}=8$ symbols are transmitted in each MICH. The number of MBMS notification indicators $N_n$ per MICH is given by the MBMS notification indicator length and the burst type, which are both known by higher layer signalling. In table 7BA this number is shown for the different possibilities of burst types and MBMS notification indicator lengths. + +**Table 7BA: Number $N_n$ of MBMS notification indicators per time slot for burst type 4 and differing MBMS notification indicator lengths $L_{NI}$** + +| | $L_{NI}=2$ | $L_{NI}=4$ | $L_{NI}=8$ | +|--------------|------------|------------|------------| +| Burst Type 4 | $N_n=64$ | $N_n=32$ | $N_n=16$ | + +The value $NI$ ( $NI = 0, \dots, N_{NI}-1$ ) calculated by higher layers, is associated to the MBMS notification indicator $N_q$ , where $q = NI \bmod N_n$ . + +The set of $NI$ passed over the Iub indicates all higher layer $NI$ values for which the notification indicator on MICH should be set to 1 during the corresponding modification period; all other indicators shall be set to 0. + +### 5.3.12.2 MICH Training sequences + +The training sequences, i.e. midambles for the MICH, are generated as described in subclause 5.2.3. The allocation of midambles depends on whether SCTD is applied to the MICH. + +- If no antenna diversity is applied the MICH the midambles can be allocated as described in subclause 5.6. +- If SCTD antenna diversity is applied to the MICH the allocation of midambles shall be as described in [9]. + +Note that when the entire carrier is dedicated to MBSFN operation MICH employs burst type 4 as described in subclause 5.3.12.1A. Burst type 4 supports a single midamble and hence SCTD is precluded from operation in such a scenario. + +### 5.3.13 E-DCH Physical Uplink Channel (E-PUCH) + +One or more E-PUCH are used to carry the uplink E-DCH transport channel and associated control information (E-UCCH) in each E-DCH TTI. In a timeslot designated by UTRAN for E-PUCH use, up to one E-PUCH may be transmitted by a UE. No other physical channels may be transmitted by a UE in an E-PUCH timeslot. + +Timing advance, as described in [9], subclause 4.3, is applied to the E-PUCH. + +### 5.3.13.1 E-UCCH + +The E-DCH Uplink Control Channel (E-UCCH) carries uplink control information associated with the E-DCH and is carried within indicator fields mapped to E-PUCH. Depending on the configuration by higher layers, an E-PUCH burst may or may not contain E-UCCH and TPC. When E-PUCH does contain E-UCCH, TPC is also transmitted. When E-PUCH does not contain E-UCCH, TPC is not transmitted. + +Higher layers shall indicate the maximum number of timeslots ( $N_{E-UCCH}$ ) that may contain E-UCCH/TPC in the E-DCH TTI. For an allocation of $n_{TS}$ E-PUCH timeslots, the UE shall transmit E-UCCH and TPC on the first $m$ allocated timeslots of the E-DCH TTI, where $m = \min(n_{TS}, N_{E-UCCH})$ . + +The E-UCCH comprises two parts, E-UCCH part 1 and E-UCCH part 2. + +E-UCCH part 1: + +- is of length 32 physical channel bits +- is mapped to the TFCI field of the E-PUCH (16 bits either side of the midamble) +- is spread at $SF=16$ using the channelisation code in the branch with the highest code numbering of the allowed OVSF sub tree, as depicted in [8] +- uses QPSK modulation + +E-UCCH part 2: + +- is of length 32 physical channel bits +- is spread using the same spreading factor as the data payloads +- uses the same modulation as the data payloads + +Figures 17c and 17d show the E-PUCH data burst with and without the E-UCCH/TPC fields. + +![Diagram of an E-PUCH data burst structure showing the placement of E-UCCH part 1, E-UCCH part 2, and TPC relative to data symbols and a midamble.](3621e1493d508bd789fec58ba8be9a40_img.jpg) + +The diagram illustrates the structure of an E-PUCH data burst. It consists of a horizontal sequence of fields: 'Data symbols', followed by a gap, then 'Midamble', another gap, 'Data symbols', and finally 'GP' (Guard Period). Above the 'Midamble' field, 'E-UCCH part 1' is indicated with lines pointing to the 16 bits immediately before and after the midamble. 'E-UCCH part 2' is indicated with lines pointing to the 16 bits immediately before and after the midamble, overlapping with the E-UCCH part 1 indicators. 'TPC' is indicated with a line pointing to the 16 bits immediately after the midamble. A double-headed arrow below the 'Midamble' field is labeled '512/256 chips'. A long double-headed arrow at the bottom of the diagram is labeled '2560 \* Tc', representing the total duration of the burst. + +Diagram of an E-PUCH data burst structure showing the placement of E-UCCH part 1, E-UCCH part 2, and TPC relative to data symbols and a midamble. + +**Figure 17c: Location of E-UCCH part 1, E-UCCH part 2 and TPC in the E-PUCH data burst** + +![Diagram of E-PUCH data burst structure without E-UCCH/TPC. It shows a sequence of four fields: Data symbols, Midamble, Data symbols, and GP. A double-headed arrow below the Midamble field indicates its length is 512/256 chips. A longer double-headed arrow below the entire sequence indicates the total length is 2560 * Tc.](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +Diagram of E-PUCH data burst structure without E-UCCH/TPC. It shows a sequence of four fields: Data symbols, Midamble, Data symbols, and GP. A double-headed arrow below the Midamble field indicates its length is 512/256 chips. A longer double-headed arrow below the entire sequence indicates the total length is 2560 \* Tc. + +Figure 17d: E-PUCH data burst without E-UCCH/TPC + +### 5.3.13.2 E-PUCH Spreading + +The spreading factors that can be applied to the E-PUCH are SF = 1, 2, 4, 8, 16 as described in subclause 5.2.1.2. + +### 5.3.13.3 E-PUCH Burst Types + +Burst types 1, 2 or 3 as described in subclause 5.2.2 can be used for E-PUCH. E-UCCH and TPC can be transmitted on the E-PUCH. + +### 5.3.13.4 PUSCH Training Sequences + +The training sequences as described in subclause 5.2.3 are used for the E-PUCH. + +### 5.3.13.5 UE Selection + +UEs that shall transmit on the E-PUCH are selected by higher layers. The UE id on the associated E-AGCH shall be used for identification. + +### 5.3.13.6 E-PUCH timeslot formats + +An E-PUCH may use QPSK or 16QAM modulation symbols and may or may not contain E-UCCH/TPC. The time slot formats are shown in table 7c. + +Table 7c: Timeslot formats for E-PUCH + +| slot format # | SF | Midamble Length (chips) | GP (chips) | N EUCCH1 (bits) | N EUCCH2 (bits) | N TPC (bits) | Bits/slot | N data/slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) | +|---------------|----|-------------------------|------------|----------------------------|----------------------------|-------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------| +| 0 (QPSK) | 16 | 512 | 96 | 0 | 0 | 0 | 244 | 244 | 122 | 122 | +| 1 (16QAM) | 16 | 512 | 96 | 0 | 0 | 0 | 488 | 488 | 244 | 244 | +| 2 (QPSK) | 16 | 512 | 96 | 32 | 32 | 2 | 244 | 178 | 90 | 88 | +| 3 (16QAM) | 16 | 512 | 96 | 32 | 32 | 2 | 454 | 388 | 196 | 192 | +| 4 (QPSK) | 16 | 256 | 96 | 0 | 0 | 0 | 276 | 276 | 138 | 138 | +| 5 (16QAM) | 16 | 256 | 96 | 0 | 0 | 0 | 552 | 552 | 276 | 276 | +| 6 (QPSK) | 16 | 256 | 96 | 32 | 32 | 2 | 276 | 210 | 106 | 104 | +| 7 (16QAM) | 16 | 256 | 96 | 32 | 32 | 2 | 518 | 452 | 228 | 224 | +| 8 (QPSK) | 8 | 512 | 96 | 0 | 0 | 0 | 488 | 488 | 244 | 244 | +| 9 (16QAM) | 8 | 512 | 96 | 0 | 0 | 0 | 976 | 976 | 488 | 488 | +| 10 (QPSK) | 8 | 512 | 96 | 32 | 32 | 2 | 454 | 388 | 196 | 192 | +| 11 (16QAM) | 8 | 512 | 96 | 32 | 32 | 2 | 874 | 808 | 408 | 400 | +| 12 (QPSK) | 8 | 256 | 96 | 0 | 0 | 0 | 552 | 552 | 276 | 276 | +| 13 (16QAM) | 8 | 256 | 96 | 0 | 0 | 0 | 1104 | 1104 | 552 | 552 | +| 14 (QPSK) | 8 | 256 | 96 | 32 | 32 | 2 | 518 | 452 | 228 | 224 | +| 15 (16QAM) | 8 | 256 | 96 | 32 | 32 | 2 | 1002 | 936 | 472 | 464 | +| 16 (QPSK) | 4 | 512 | 96 | 0 | 0 | 0 | 976 | 976 | 488 | 488 | +| 17 (16QAM) | 4 | 512 | 96 | 0 | 0 | 0 | 1952 | 1952 | 976 | 976 | +| 18 (QPSK) | 4 | 512 | 96 | 32 | 32 | 2 | 874 | 808 | 408 | 400 | + +| | | | | | | | | | | | +|------------|----|-----|-----|----|----|---|------|------|------|------| +| 19 (16QAM) | 4 | 512 | 96 | 32 | 32 | 2 | 1714 | 1648 | 832 | 816 | +| 20 (QPSK) | 4 | 256 | 96 | 0 | 0 | 0 | 1104 | 1104 | 552 | 552 | +| 21 (16QAM) | 4 | 256 | 96 | 0 | 0 | 0 | 2208 | 2208 | 1104 | 1104 | +| 22 (QPSK) | 4 | 256 | 96 | 32 | 32 | 2 | 1002 | 936 | 472 | 464 | +| 23 (16QAM) | 4 | 256 | 96 | 32 | 32 | 2 | 1970 | 1904 | 960 | 944 | +| 24 (QPSK) | 2 | 512 | 96 | 0 | 0 | 0 | 1952 | 1952 | 976 | 976 | +| 25 (16QAM) | 2 | 512 | 96 | 0 | 0 | 0 | 3904 | 3904 | 1952 | 1952 | +| 26 (QPSK) | 2 | 512 | 96 | 32 | 32 | 2 | 1714 | 1648 | 832 | 816 | +| 27 (16QAM) | 2 | 512 | 96 | 32 | 32 | 2 | 3394 | 3328 | 1680 | 1648 | +| 28 (QPSK) | 2 | 256 | 96 | 0 | 0 | 0 | 2208 | 2208 | 1104 | 1104 | +| 29 (16QAM) | 2 | 256 | 96 | 0 | 0 | 0 | 4416 | 4416 | 2208 | 2208 | +| 30 (QPSK) | 2 | 256 | 96 | 32 | 32 | 2 | 1970 | 1904 | 960 | 944 | +| 31 (16QAM) | 2 | 256 | 96 | 32 | 32 | 2 | 3906 | 3840 | 1936 | 1904 | +| 32 (QPSK) | 1 | 512 | 96 | 0 | 0 | 0 | 3904 | 3904 | 1952 | 1952 | +| 33 (16QAM) | 1 | 512 | 96 | 0 | 0 | 0 | 7808 | 7808 | 3904 | 3904 | +| 34 (QPSK) | 1 | 512 | 96 | 32 | 32 | 2 | 3394 | 3328 | 1680 | 1648 | +| 35 (16QAM) | 1 | 512 | 96 | 32 | 32 | 2 | 6754 | 6688 | 3376 | 3312 | +| 36 (QPSK) | 1 | 256 | 96 | 0 | 0 | 0 | 4416 | 4416 | 2208 | 2208 | +| 37 (16QAM) | 1 | 256 | 96 | 0 | 0 | 0 | 8832 | 8832 | 4416 | 4416 | +| 38 (QPSK) | 1 | 256 | 96 | 32 | 32 | 2 | 3906 | 3840 | 1936 | 1904 | +| 39 (16QAM) | 1 | 256 | 96 | 32 | 32 | 2 | 7778 | 7712 | 3888 | 3824 | +| 40 (QPSK) | 16 | 512 | 192 | 0 | 0 | 0 | 232 | 232 | 122 | 110 | +| 41 (16QAM) | 16 | 512 | 192 | 0 | 0 | 0 | 464 | 464 | 244 | 220 | +| 42 (QPSK) | 16 | 512 | 192 | 32 | 32 | 2 | 232 | 166 | 90 | 76 | +| 43 (16QAM) | 16 | 512 | 192 | 32 | 32 | 2 | 430 | 364 | 196 | 168 | +| 44 (QPSK) | 8 | 512 | 192 | 0 | 0 | 0 | 464 | 464 | 244 | 220 | +| 45 (16QAM) | 8 | 512 | 192 | 0 | 0 | 0 | 928 | 928 | 488 | 440 | +| 46 (QPSK) | 8 | 512 | 192 | 32 | 32 | 2 | 430 | 364 | 196 | 168 | +| 47 (16QAM) | 8 | 512 | 192 | 32 | 32 | 2 | 826 | 760 | 408 | 352 | +| 48 (QPSK) | 4 | 512 | 192 | 0 | 0 | 0 | 928 | 928 | 488 | 440 | +| 49 (16QAM) | 4 | 512 | 192 | 0 | 0 | 0 | 1856 | 1856 | 976 | 880 | +| 50 (QPSK) | 4 | 512 | 192 | 32 | 32 | 2 | 826 | 760 | 408 | 352 | +| 51 (16QAM) | 4 | 512 | 192 | 32 | 32 | 2 | 1618 | 1552 | 832 | 720 | +| 52 (QPSK) | 2 | 512 | 192 | 0 | 0 | 0 | 1856 | 1856 | 976 | 880 | +| 53 (16QAM) | 2 | 512 | 192 | 0 | 0 | 0 | 3712 | 3712 | 1952 | 1760 | +| 54 (QPSK) | 2 | 512 | 192 | 32 | 32 | 2 | 1618 | 1552 | 832 | 720 | +| 55 (16QAM) | 2 | 512 | 192 | 32 | 32 | 2 | 3202 | 3136 | 1680 | 1456 | +| 56 (QPSK) | 1 | 512 | 192 | 0 | 0 | 0 | 3712 | 3712 | 1952 | 1760 | +| 57 (16QAM) | 1 | 512 | 192 | 0 | 0 | 0 | 7424 | 7424 | 3904 | 3520 | +| 58 (QPSK) | 1 | 512 | 192 | 32 | 32 | 2 | 3202 | 3136 | 1680 | 1456 | +| 59 (16QAM) | 1 | 512 | 192 | 32 | 32 | 2 | 6370 | 6304 | 3376 | 2928 | + +### 5.3.14 E-DCH Random Access Uplink Control Channel (E-RUCCH) + +The E-RUCCH is used to carry E-DCH-associated uplink control signalling when E-PUCH resources are not available. The characteristics of the E-RUCCH physical channel are identical to those of PRACH (see subclause 5.3.3). + +Physical resources available for E-RUCCH are configured by higher layers. E-RUCCH may be mapped to the same physical resources that are assigned for PRACH. + +### 5.3.15 E-DCH Absolute Grant Channel (E-AGCH) + +The E-DCH Absolute Grant Channel (E-AGCH) is a downlink physical channel carrying the uplink E-DCH absolute grant control information. E-AGCH carries a TPC field (located immediately after the midamble and spread using SF16) which is used to control the E-PUCH power. Figure 17e illustrates the burst structure of the E-AGCH. + +![Figure 17e: Burst structure of E-AGCH. The diagram shows a horizontal bar representing the burst structure. From left to right, it consists of 'Data symbols', 'Midamble', a shaded 'TPC field', 'Data symbols', and 'GP'. A double-headed arrow below the 'Midamble' and 'TPC field' is labeled '512/256 chips'. A longer double-headed arrow at the bottom, spanning the entire length of the bar, is labeled '2560*Tc'.](9a14684f8ae1345c6efea6f5994c730c_img.jpg) + +Figure 17e: Burst structure of E-AGCH. The diagram shows a horizontal bar representing the burst structure. From left to right, it consists of 'Data symbols', 'Midamble', a shaded 'TPC field', 'Data symbols', and 'GP'. A double-headed arrow below the 'Midamble' and 'TPC field' is labeled '512/256 chips'. A longer double-headed arrow at the bottom, spanning the entire length of the bar, is labeled '2560\*Tc'. + +Figure 17e: Burst structure of E-AGCH + +One E-DCH absolute grant for a UE shall be transmitted over one E-AGCH. + +#### 5.3.15.1 E-AGCH Spreading + +The E-AGCH shall use spreading factor $SF = 16$ , as described in 5.2.1.1. + +#### 5.3.15.2 E-AGCH Burst Types + +Burst types 1 and 2 as described in subclause 5.2.2 can be used for E-AGCH. TPC shall be transmitted on E-AGCH whereas TFCI shall not be transmitted. + +#### 5.3.15.3 E-AGCH Training Sequences + +The training sequences as described in subclause 5.2.3 are used for the E-AGCH. + +#### 5.3.15.4 E-AGCH timeslot formats + +The E-AGCH uses the timeslot formats of Table 7d. These augment downlink slot formats 0...19 of table 5a, see subclause 5.2.2.6.1. + +Table 7d: Time slot formats for E-AGCH + +| Slot Format # | SF | Midamble length (chips) | $N_{TFCI}$ code word (bits) | $N_{TPC}$ (bits) | Bits/slot | $N_{Data/Slot}$ (bits) | $N_{data/data field (1)}$ (bits) | $N_{data/data field (2)}$ (bits) | +|---------------|----|-------------------------|-----------------------------|------------------|-----------|------------------------|----------------------------------|----------------------------------| +| 20 | 16 | 512 | 0 | 2 | 244 | 242 | 122 | 120 | +| 21 | 16 | 256 | 0 | 2 | 276 | 274 | 138 | 136 | + +### 5.3.16 E-DCH Hybrid ARQ Acknowledgement Indicator Channel (E-HICH) + +The E-DCH HARQ Acknowledgement indicator channel (E-HICH) is defined in terms of a SF16 downlink physical channel and a signature sequence. The E-HICH carries the uplink E-DCH hybrid ARQ acknowledgement indicator. Figure 17f illustrates the structure of the E-HICH. + +![Figure 17f – E-HICH Structure. The diagram shows the structure of an E-HICH burst across multiple users (user #H, user #1, user #0) and slots (Slot #0 to Slot #14). Each user's burst consists of data bits (b_{i,j}), spare bits, a midamble, and a GP. The total duration of one user's burst is 1xSF16. The slots are grouped into a 1 radio frame, 10ms duration.](32ff77da4286b58c4778033acaa10836_img.jpg) + +The diagram illustrates the E-HICH structure. At the top, three user bursts are shown: user #H, user #1, and user #0. Each burst contains a sequence of bits: $b_{i,0}, b_{i,1}, \dots, b_{i,119}$ , followed by two spare bits, a midamble, two more spare bits, $b_{i,120}, b_{i,121}, \dots, b_{i,239}$ , and a GP. The bits $b_{i,119}$ and $b_{i,120}$ are highlighted with boxes. The midamble is shown as a single block shared by all users. The GP is also shared. A bracket on the right indicates the total duration of one user's burst is $1 \times SF16$ . Below the user bursts, a timeline shows slots: Slot #0, Slot #1, Slot #2, ..., Slot #n, ..., Slot #14. A double-headed arrow below the slots indicates the total duration of one radio frame is 10ms. + +Figure 17f – E-HICH Structure. The diagram shows the structure of an E-HICH burst across multiple users (user #H, user #1, user #0) and slots (Slot #0 to Slot #14). Each user's burst consists of data bits (b\_{i,j}), spare bits, a midamble, and a GP. The total duration of one user's burst is 1xSF16. The slots are grouped into a 1 radio frame, 10ms duration. + +Figure 17f – E-HICH Structure + +A single channelisation code may carry one or multiple signature sequences. Each signature sequence conveys a HARQ acknowledgement indicator. A maximum of one indicator may be transmitted to a UE. Each acknowledgement indicator is coded to form a signature sequence of 240 bits ( $b_0, b_1, \dots, b_{239}$ ) as defined in [7] and is transmitted within a single E-HICH timeslot. The E-HICH also contains $U$ spare bit locations, where $U=4$ for burst type 1 and $U=36$ for burst type 2. The spare bit values are not defined. + +### 5.3.16.1 E-HICH Spreading + +Signature sequences (including spare bits inserted) that share the same channelisation code are combined and spread using spreading factor $SF=16$ as described in [8]. + +### 5.3.16.2 E-HICH Burst Types + +Burst types 1 and 2 as described in subclause 5.2.2 can be used for E-HICH. Neither TFCI nor TPC shall be transmitted on the E-HICH. + +### 5.3.16.3 E-HICH Training Sequences + +The training sequences as described in subclause 5.2.3 are used for the E-HICH. + +## 5.4 Transmit Diversity for DL Physical Channels + +Table 8 summarizes the different transmit diversity schemes for different downlink physical channel types that are described in [9]. + +**Table 8: Application of Tx diversity schemes on downlink physical channel types** + "X" – can be applied, "--" – must not be applied + +| Physical channel type | Open loop TxDiversity | | Closed loop TxDiversity | +|-----------------------|-----------------------|---------------------|-------------------------| +| | TSTD | SCTD (*) | | +| P-CCPCH | -- | X(†) | -- | +| S-CCPCH | X(**) | X(†) | -- | +| SCH | X | -- | -- | +| DPCH | -- | -- | X | +| PDSCH | -- | X | X | +| PICH | -- | X | -- | +| MICH | -- | X(†) | -- | +| HS-SCCH | -- | X | X | +| HS-PDSCH | -- | X | X | +| E-AGCH | -- | X | X | +| E-HICH | -- | X | -- | + +(\*) Note: SCTD may only be applied to physical channels when they are allocated to beacon locations. + +(\*\*) Note: TSTD may not be applied to S-CCPCH in beacon locations. + +(†) Note: that when the entire carrier is dedicated to MBSFN operation SCTD shall not be applied. + +## 5.5 Beacon characteristics of physical channels + +For the purpose of measurements, common physical channels that are allocated to particular locations (time slot, code) shall have particular physical characteristics, called beacon characteristics. Physical channels with beacon characteristics are called beacon channels. The locations of the beacon channels are called beacon locations. The ensemble of beacon channels shall provide the beacon function, i.e. a reference power level at the beacon locations, regularly existing in each radio frame. Thus, beacon channels must be present in each radio frame, the only exception is when idle periods are used to support time difference measurements for location services [9]. Then it may be possible that the beacon channels occur in the same frame and time slot as the idle periods. In this case, the beacon channels will not be transmitted in that particular frame and time slot. + +### 5.5.1 Location of beacon channels + +The beacon locations are determined by the SCH and depend on the SCH allocation case, see subclause 5.3.4: + +- Case 1) The beacon function shall be provided by the physical channels that are allocated to channelisation code $c_{Q=6}^{(k=1)}$ and to TS#k, k=0,...,14. +- Case 2) The beacon function shall be provided by the physical channels that are allocated to channelisation code $c_{Q=6}^{(k=1)}$ and to TS#k and TS#k+8, k=0,...,6. + +Note that by this definition the P-CCPCH always has beacon characteristics. + +### 5.5.2 Physical characteristics of beacon channels + +The beacon channels shall have the following physical characteristics. They: + +- are transmitted with reference power; +- are transmitted without beamforming; +- use burst type 1 or burst type 4 when MBSFN is applied to beacon channels; +- use midamble m(1) and m(2) exclusively in this time slot; and +- midambles m(9) and m(10) are always left unused in this time slot, if 16 midambles are allowed in that cell. + +Note that in the time slot where the P-CCPCH is transmitted only the midambles m(1) to m(8) shall be used, see 5.6.1. Thus, midambles m(9) and m(10) are always left unused in this time slot. + +Note that when MBSFN is applied to beacon channels there is a single midamble and hence midamble $m^{(1)}$ is exclusively used in the timeslot. + +The reference power corresponds to the sum of the power allocated to both midambles $m^{(1)}$ and $m^{(2)}$ . Two possibilities exist: + +- If SCTD antenna diversity is not applied to beacon channels all the reference power of any beacon channel is allocated to $m^{(1)}$ . +- If SCTD antenna diversity is applied to beacon channels, for any beacon channel midambles $m^{(1)}$ and $m^{(2)}$ are each allocated half of the reference power. + +## 5.6 Midamble Allocation for Physical Channels + +Midambles are part of the physical channel configuration which is performed by higher layers. Three different midamble allocation schemes exist: + +- UE specific midamble allocation: A UE specific midamble for DL or UL is explicitly assigned by higher layers. +- Default midamble allocation: The midamble for DL or UL is allocated by layer 1 depending on the associated channelisation code. +- Common midamble allocation: The midamble for the DL is allocated by layer 1 depending on the number of channelisation codes currently being present in the DL time slot. + +If a midamble is not explicitly assigned and the use of the common midamble allocation scheme is not signalled by higher layers, the midamble shall be allocated by layer 1, based on the default midamble allocation scheme. This default midamble allocation scheme is given by a fixed association between midambles and channelisation codes, see clause A.3, and shall be applied individually to all channelisation codes within one time slot. Different associations apply for different burst types and cell configurations with respect to the maximum number of midambles. + +For timeslots employing MBSFN operation burst type 4 is used and hence DL beamforming is not applied, subclause 5.2.4. Furthermore, as this burst type contains only a single midamble, i.e. $K_{\text{Cell}}=1$ , then all physical channels in such timeslots employ the same midamble and thus default and common midamble allocation amount to the same allocation strategies. + +### 5.6.1 Midamble Allocation for DL Physical Channels + +Beacon channels shall always use the reserved midambles $m^{(1)}$ and $m^{(2)}$ , see 5.5. For DL physical channels that are located in the same time slot as the P-CCPCH, midambles shall be allocated based on the default midamble allocation scheme, using the association for burst type 1 and $K_{\text{Cell}}=8$ midambles. For all other DL physical channels, the midamble is explicitly assigned by higher layers or allocated by layer 1. + +#### 5.6.1.1 Midamble Allocation by signalling from higher layers + +UE specific midambles may be signalled by higher layers to UE's as a part of the physical channel configuration, if: + +- multiple UEs use the physical channels in one DL time slot; and +- beamforming is applied to all of these DL physical channels; and +- no closed loop TxDiversity is applied to any of these DL physical channels; + +or + +- PDSCH physical layer signalling based on the midamble is used. + +#### 5.6.1.2 Midamble Allocation by layer 1 + +##### 5.6.1.2.1 Default midamble + +If a midamble is not explicitly assigned and the use of the common midamble allocation scheme is not signalled by higher layers, the UE shall derive the midambles from the allocated channelisation codes and shall use an individual midamble for each channelisation code group containing one primary and a set of secondary channelisation codes. The + +association between midambles and channelisation code groups is given in annex A.3. All the secondary channelisation codes within a set use the same midamble as the primary channelisation code to which they are associated. + +Higher layers shall allocate the channelisation codes in a particular order. Secondary codes shall only be allocated if the associated primary code is also allocated. If midambles are reserved for the beacon channels, all primary and secondary channelisation codes that are associated with the reserved midambles shall not be used. + +Channelisation codes of one channelisation code group shall not be allocated to different UE's. + +In the case that secondary channelisation codes are used, secondary channelisation codes of one channelisation code group shall be allocated in ascending order, with respect to their numbering, and beginning with the lowest code index in this channelisation code group. + +The UE shall assume different channel estimates for each of the individual midambles. + +The default midamble allocation shall not apply for those downlink channels that are intended for a UE which will be the only UE assigned to a given time slot or slots for the duration of the assigned channel's existence (as in the case of high rate services). + +#### 5.6.1.2.2 Common Midamble + +The use of the common midamble allocation scheme is signalled to the UE by higher layers as a part of the physical channel configuration. A common midamble may be assigned by layer 1 to all physical channels in one DL time slot, if: + +- a single UE uses all physical channels in one DL time slot (as in the case of high rate service); + +or + +- multiple UEs use the physical channels in one DL time slot; and +- no beamforming is applied to any of these DL physical channels; and +- no closed loop TxDiversity is applied to any of these DL physical channels; and +- midambles are not used for PDSCH physical layer signalling. + +The number of channelisation codes currently employed in the DL time slot is associated with the use of a particular common midamble. Different associations apply for different burst types and cell configurations with respect to the maximum number of midambles, see annex B. + +### 5.6.2 Midamble Allocation for UL Physical Channels + +If the midamble is explicitly assigned by higher layers, an individual midamble shall be assigned to all UE's in one UL time slot. + +If no midamble is explicitly assigned by higher layers, the UE shall derive the midamble from the channelisation code that is used for the data part (except for TFCI/TPC) of the burst. Note that in the event that code hopping is employed the midamble is derived from the channelisation code actually transmitted (i.e. the code used after the hop sequence has been applied – see [9]). The associations between midamble and channelisation code are the same as for DL physical channels. + +## 5.7 Midamble Transmit Power + +There shall be no offset between the sum of the powers allocated to all midambles in a timeslot and the sum of the powers allocated to the data symbol fields. The transmit power within a timeslot is hence constant. + +The midamble transmit power of beacon channels is equal to the reference power. If SCTD is used for beacon channels, the reference power is equally divided between the midambles $m^{(1)}$ and $m^{(2)}$ . + +The midamble transmit power of all other physical channels depends on the midamble allocation scheme used. The following rules apply + +- In case of Default Midamble Allocation, every midamble is transmitted with the same power as the associated codes. + +- In case of Common Midamble Allocation in the downlink, the transmit power of this common midamble is such that there is no power offset between the data parts and the midamble part of the overall transmit signal within one time slot. +- In case of UE Specific Midamble Allocation, the transmit power of the UE specific midamble is such that there is no power offset between the data parts and the midamble part of every user within one time slot. + +The following figure 18 depicts the midamble powers for the different channel types and midamble allocation schemes. + +Note 1: In figure 18, the codes c(1) to c(16) represent the set of usable codes and not the set of used codes. + +Note 2: The common midamble allocation and the midamble allocation by higher layers are not applicable in those beacon time slots, in which the P-CCPCH is located, see section 5.6.1. + +![Figure 18: Midamble powers for the different midamble allocation schemes. The figure consists of three columns of diagrams representing different time slot scenarios: 'No Beacon Time Slots', 'Beacon Time Slots when SCTD is not applied', and 'Beacon Time Slots when SCTD is applied'. Each column contains three rows of diagrams for different allocation schemes: 'Common Midamble Allocation', 'Default Midamble Allocation', and 'Midamble Allocation by Higher Layers'. Each diagram shows a power level 'P' on the y-axis and a sequence of codes and midambles on the x-axis. In the 'Common Midamble Allocation' row, the first diagram shows codes c(1) to c(16) with a single midamble m(x). The second and third diagrams show beacon channels, midambles m(1) to m(x), and codes c(1) to c(16). In the 'Default Midamble Allocation' row, the first diagram shows multiple midambles m(1) to m(K_CELL) and codes c(1) to c(16). The second and third diagrams show beacon channels, midambles m(1) to m(K_CELL), and codes c(1) to c(16). In the 'Midamble Allocation by Higher Layers' row, the first diagram shows multiple CCTrCHs (1 to U) with midambles m(1) to m(K_CELL). The second and third diagrams show beacon channels, midambles m(1) to m(K_CELL), and CCTrCHs (1 to U).](f9625fa3465b009051f85d91cfa1da7e_img.jpg) + +No Beacon Time Slots                      Beacon Time Slots when SCTD is not applied                      Beacon Time Slots when SCTD is applied + +x depends on the number of transmitted codes in that time slot + +M: Number of codes per Midamble (M=16/K\_CELL); in the P-CCPCH Time Slot M = 2, independent of K\_CELL +K\_CELL : Number of usable Midamble Shifts in this Cell + +U: Number of CCTrCHs in this Time Slot, multiple CCTrCHs of one user may share one midamble +K\_CELL : Number of usable Midamble Shifts in this Cell + +Figure 18: Midamble powers for the different midamble allocation schemes. The figure consists of three columns of diagrams representing different time slot scenarios: 'No Beacon Time Slots', 'Beacon Time Slots when SCTD is not applied', and 'Beacon Time Slots when SCTD is applied'. Each column contains three rows of diagrams for different allocation schemes: 'Common Midamble Allocation', 'Default Midamble Allocation', and 'Midamble Allocation by Higher Layers'. Each diagram shows a power level 'P' on the y-axis and a sequence of codes and midambles on the x-axis. In the 'Common Midamble Allocation' row, the first diagram shows codes c(1) to c(16) with a single midamble m(x). The second and third diagrams show beacon channels, midambles m(1) to m(x), and codes c(1) to c(16). In the 'Default Midamble Allocation' row, the first diagram shows multiple midambles m(1) to m(K\_CELL) and codes c(1) to c(16). The second and third diagrams show beacon channels, midambles m(1) to m(K\_CELL), and codes c(1) to c(16). In the 'Midamble Allocation by Higher Layers' row, the first diagram shows multiple CCTrCHs (1 to U) with midambles m(1) to m(K\_CELL). The second and third diagrams show beacon channels, midambles m(1) to m(K\_CELL), and CCTrCHs (1 to U). + +**Figure 18: Midamble powers for the different midamble allocation schemes** + +## 5.8 Physical channels for the 3.84 Mcps MBFSN IMB option + +Physical channels are defined by a specific carrier frequency, scrambling code, channelization code and in some cases a time start & stop (giving a duration). Scrambling and channelization codes are specified in [8]. Time durations are defined by start and stop instants, measured in integer multiples of chips. Suitable multiples of chips also used in specification are: + +**Radio frame:** A radio frame is a processing duration which consists of 15 slots. The length of a radio frame corresponds to 38400 chips (10 ms). + +**Slot:** A slot is a duration which consists of fields containing bits. The length of a slot corresponds to 2560 chips. + +**Sub-frame:** A sub-frame corresponds to 3 slots (2 ms). + +The default time duration for a physical channel is continuous from the instant when it is started to the instant when it is stopped. Physical channels that are not continuous will be explicitly described. In the case of 2 ms physical channel duration, the physical channel is active for only one 2 ms sub-frame (7680 chips) per radio frame. A physical channel of 2 ms duration may start at one of 5 start instances per radio frame. These correspond to 0 ms, 2 ms, 4 ms, 6 ms or 8 ms following the commencement of the radio frame and are denoted as sub-frames 0, 1, 2, 3 and 4 respectively. + +Transport channels are described (in more abstract higher layer models of the physical layer) as being capable of being mapped to physical channels. Within the physical layer itself the exact mapping is from a composite coded transport + +channel (CCTrCH) to the data part of a physical channel. In addition to data parts there are also channel control parts and physical signals. For the IMB option, both a continuous and a discontinuous pilot physical channel shall be transmitted using specific OVSF channelisation codes. + +The IMB option is only applicable for dedicated carrier MBSFN operations in which all TDD slots of the radio frame are configured in the downlink direction. All physical channels are common and downlink only. + +![Figure 18iA: Downlink transmissions in all TDD slots. A diagram showing a 10 ms radio frame divided into 15 TDD slots, each containing a downlink transmission indicated by a downward arrow.](1ce027dfd26183da52137cf990213724_img.jpg) + +A horizontal timeline at the top is labeled "10 ms". Below it, a row of 15 rectangular boxes represents TDD slots. Each box has a downward-pointing arrow in the center, indicating a downlink transmission in every slot. + +Figure 18iA: Downlink transmissions in all TDD slots. A diagram showing a 10 ms radio frame divided into 15 TDD slots, each containing a downlink transmission indicated by a downward arrow. + +**Figure 18iA: Downlink transmissions in all TDD slots** + +### 5.8.1 Transmit diversity + +Transmit diversity is not applicable to IMB physical channels for MBSFN operations. + +### 5.8.2 Common physical channels + +The common physical channels used on a dedicated carrier for the IMB option are P-CPICH, T-CPICH, P-CCPCH, S-CCPCH frame type 1, S-CCPCH frame type 2, SCH and MICH. + +#### 5.8.2.1 Primary Common Pilot Channel (P-CPICH) + +The primary common pilot channel (P-CPICH) is a fixed rate (30 kbps, SF=256) downlink physical channel using QPSK modulation and carrying a pre-defined bit sequence in which all bits are set to logical "0". The P-CPICH is transmitted continuously on all slots of the radio frame. Figure 18iiA shows the frame structure of the P-CPICH. + +![Figure 18iiA: Frame structure for Primary Common Pilot Channel. A diagram showing a radio frame of 10 ms duration divided into slots. A 'Pre-defined bit sequence' is shown above the slots, with a callout indicating that each slot contains 2560 chips and 20 bits of this sequence.](3f09464f0a8ac9446981a53f9b78df2c_img.jpg) + +The diagram shows a "Pre-defined bit sequence" in a long horizontal box at the top. Below it, a timeline represents "1 radio frame: $T_f = 10$ ms". This frame is divided into slots, with "Slot #0", "Slot #1", "Slot #i", and "Slot #14" explicitly labeled. Two diagonal lines connect the ends of the "Pre-defined bit sequence" box to the boundaries of "Slot #i", with the text " $T_{slot} = 2560$ chips , 20 bits" placed between them. + +Figure 18iiA: Frame structure for Primary Common Pilot Channel. A diagram showing a radio frame of 10 ms duration divided into slots. A 'Pre-defined bit sequence' is shown above the slots, with a callout indicating that each slot contains 2560 chips and 20 bits of this sequence. + +**Figure 18iiA: Frame structure for Primary Common Pilot Channel** + +The P-CPICH has the following characteristics: + +- The same channelization code is always used for the P-CPICH, see [8]; +- The P-CPICH is scrambled by the primary scrambling code, see [8]; +- There is one and only one P-CPICH per MBSFN cluster; +- The P-CPICH is broadcast over the entire MBSFN cluster. + +#### 5.8.2.2 Time-multiplexed Common Pilot Channel (T-CPICH) + +The time-multiplexed common pilot channel (T-CPICH) is composed of a set of 15 SF=16 physical channels using 16-QAM modulation, each carrying a pre-defined pilot bit sequence of length 64 bits. All of the channelization codes used to carry T-CPICH are OVSF codes as defined in [8] and are orthogonal to the P-CPICH. The T-CPICH chip-level sequence has a length of 256 chips and is transmitted at the end of each slot of the radio frame. The T-CPICH is not transmitted during the first 2304 chips of each slot. The structure of the T-CPICH is shown in figure 18iiiA. + +![Figure 18iiiA: Structure of the Time-multiplexed Common Pilot Channel (T-CPICH). The diagram shows a radio frame of 10 ms duration (T_f = 10 ms) divided into 15 slots (Slot #0 to Slot #14). Each slot has a duration of T_slot = 2560 chips. The T-CPICH is transmitted in Slot #1 and Slot #14. In Slot #1, the T-CPICH is shown as a 'TDM pilot' block of 256 chips at the end of the slot. In Slot #14, the T-CPICH is shown as a 'TDM pilot' block of 256 chips at the beginning of the slot. The rest of the frame is labeled '(Tx OFF)'.](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +Figure 18iiiA: Structure of the Time-multiplexed Common Pilot Channel (T-CPICH). The diagram shows a radio frame of 10 ms duration (T\_f = 10 ms) divided into 15 slots (Slot #0 to Slot #14). Each slot has a duration of T\_slot = 2560 chips. The T-CPICH is transmitted in Slot #1 and Slot #14. In Slot #1, the T-CPICH is shown as a 'TDM pilot' block of 256 chips at the end of the slot. In Slot #14, the T-CPICH is shown as a 'TDM pilot' block of 256 chips at the beginning of the slot. The rest of the frame is labeled '(Tx OFF)'. + +**Figure 18iiiA: Structure of the Time-multiplexed Common Pilot Channel (T-CPICH)** + +The T-CPICH has the following characteristics: + +- The T-CPICH is scrambled by the same scrambling code as P-CPICH +- There is one and only one T-CPICH per MBSFN cluster; +- The T-CPICH is broadcasted over the entire MBSFN cluster + +The UE may use the T-CPICH as the phase reference for all downlink physical channels. + +The pilot bit sequences carried on T-CPICH are defined as a function of the scrambling code index used for the MBSFN cluster and the slot index in which the T-CPICH is transmitted. With index $n$ of the primary scrambling code as defined in [4] and with the index $i = 0 \dots 14$ , of the slot in which the T-CPICH is transmitted, the T-CPICH pilot bit sequences $B^{(n)}_{\text{T-CPICH},0} \dots B^{(n)}_{\text{T-CPICH},959}$ are defined in table CD.1 of annex CD. For each slot index $i$ , the bit sequences $B^{(n)}_{\text{T-CPICH},0} \dots B^{(n)}_{\text{T-CPICH},959}$ are a concatenation of the 15 bit sequences $b^{(n)}_{\text{T-CPICH},0,m} \dots b^{(n)}_{\text{T-CPICH},63,m}$ carried on each OVSF code $C_{\text{ch},16,m}$ (see [8]) with $m = 1 \dots 15$ such that: + +$$\begin{aligned} \{ B^{(n)}_{\text{T-CPICH},0}, B^{(n)}_{\text{T-CPICH},1}, \dots, B^{(n)}_{\text{T-CPICH},959} \} = & \{ \{ b^{(n)}_{\text{T-CPICH},0,1}, b^{(n)}_{\text{T-CPICH},1,1} \dots b^{(n)}_{\text{T-CPICH},63,1} \}, \dots \\ & \{ b^{(n)}_{\text{T-CPICH},0,2}, b^{(n)}_{\text{T-CPICH},1,2} \dots b^{(n)}_{\text{T-CPICH},63,2} \}, \dots \\ & \dots \{ b^{(n)}_{\text{T-CPICH},0,15}, b^{(n)}_{\text{T-CPICH},1,15} \dots b^{(n)}_{\text{T-CPICH},63,15} \} \} \end{aligned}$$ + +The OVSF code $C_{\text{ch},16,0}$ is not used by T-CPICH. + +### 5.8.2.3 Primary common control physical channel (P-CCPCH) + +The Primary CCPCH is a fixed rate (30 kbps, SF=256) downlink physical channels used to carry the BCH transport channel. The BCH transport channel has a fixed transport format combination, hence the Primary CCPCH does not support TFCI. The P-CCPCH uses QPSK modulation. + +Figure 18ivA shows the frame structure of the P-CCPCH. The P-CCPCH is not transmitted during the first and last 256 chips of each slot. Instead, Primary SCH and Secondary SCH are transmitted during first DTX period and T-CPICH is transmitted during the last DTX period. + +![Figure 18ivA: Frame structure for Primary Common Control Physical Channel. The diagram shows a single slot with a total duration of T_slot = 2560 chips, 20 bits. The slot contains a 'Data' field of N_data1 = 16 bits, flanked by two '(Tx OFF)' regions of 256 chips each. Below the slot, a timeline shows Slot #0, Slot #1, Slot #i, and Slot #14.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +Diagram illustrating the frame structure for the Primary Common Control Physical Channel (P-CCPCH). The slot structure shows a total duration of $T_{\text{slot}} = 2560$ chips, 20 bits. The slot contains a 'Data' field of $N_{\text{data1}} = 16$ bits, flanked by two '(Tx OFF)' regions of 256 chips each. Below the slot, a timeline shows Slot #0, Slot #1, Slot #i, and Slot #14. + +Figure 18ivA: Frame structure for Primary Common Control Physical Channel. The diagram shows a single slot with a total duration of T\_slot = 2560 chips, 20 bits. The slot contains a 'Data' field of N\_data1 = 16 bits, flanked by two '(Tx OFF)' regions of 256 chips each. Below the slot, a timeline shows Slot #0, Slot #1, Slot #i, and Slot #14. + +Figure 18ivA: Frame structure for Primary Common Control Physical Channel + +#### 5.8.2.4 Secondary common control physical channel (S-CCPCH) + +The Secondary CCPCH is used to carry FACH transport channels. + +For MBSFN IMB, there are two types of Secondary CCPCH: + +- Secondary CCPCH frame type 1; consists of 15 slots per radio frame +- Secondary CCPCH frame type 2; consists of 3 slots (i.e. one sub-frame) per radio frame. + +Both of the Secondary CCPCH frame types may include TFCI in order to support multiple transport format combinations. It is the UTRAN that determines if a TFCI should be transmitted, hence making it mandatory for all UEs to support the use of TFCI. The structures of the Secondary CCPCH frame type 1 and Secondary CCPCH frame type 2 are shown in figure 18vA and figure 18viA, respectively. + +Physical channel bits of Secondary CCPCH frame type 1 slots are mapped to a QPSK signal point constellation whereas physical channel bits of Secondary CCPCH frame type 2 can be mapped either to QPSK or 16QAM signal point constellations. In the case of Secondary CCPCH frame type 2, the signal point constellation to be used for the data field is given by higher layer signalling. + +![Figure 18vA: Frame structure for Secondary Common Control Physical Channel frame type 1. The diagram shows a slot with a total duration of T_slot = 2560 chips. The slot contains a 'TFCI' field of N_TFCI bits, a 'Data' field of N_data1 bits, and a '(Tx OFF)' region of 256 chips. The total duration of the TFCI and Data fields is 18 bits. Below the slot, a timeline shows Slot #0, Slot #1, Slot #i, and Slot #14, with a label '1 radio frame: T_f = 10 ms'.](5c65cabec7c5062117fb0d578916cf8b_img.jpg) + +Diagram illustrating the frame structure for the Secondary Common Control Physical Channel (S-CCPCH) frame type 1. The slot structure shows a total duration of $T_{\text{slot}} = 2560$ chips. The slot contains a 'TFCI' field of $N_{\text{TFCI}}$ bits, a 'Data' field of $N_{\text{data1}}$ bits, and a '(Tx OFF)' region of 256 chips. The total duration of the TFCI and Data fields is 18 bits. Below the slot, a timeline shows Slot #0, Slot #1, Slot #i, and Slot #14, with a label '1 radio frame: $T_f = 10$ ms'. + +Figure 18vA: Frame structure for Secondary Common Control Physical Channel frame type 1. The diagram shows a slot with a total duration of T\_slot = 2560 chips. The slot contains a 'TFCI' field of N\_TFCI bits, a 'Data' field of N\_data1 bits, and a '(Tx OFF)' region of 256 chips. The total duration of the TFCI and Data fields is 18 bits. Below the slot, a timeline shows Slot #0, Slot #1, Slot #i, and Slot #14, with a label '1 radio frame: T\_f = 10 ms'. + +Figure 18vA: Frame structure for Secondary Common Control Physical Channel frame type 1 + +![Figure 18viA: Frame structure for Secondary Common Control Physical Channel frame type 2. The diagram shows a hierarchical view of the frame structure. At the top, a slot is shown with a TFCI field (N_TFCI bits) and a Data field (N_data1 bits). The total number of bits in a slot is m*144 bits (where m = 2, 4). This is spread into 256 chips. A dashed box labeled (Tx OFF) is shown at the end of the slot. Below this, a subframe is shown, consisting of multiple slots (Slot #0, Slot #1, Slot #2). The total duration of a subframe is T_subframe = 7680 chips. The subframe index is i. The start position of the subframe within the radio frame is i*7680 chips. A dashed box labeled (Tx OFF) is shown at the beginning and end of the subframe. At the bottom, a radio frame is shown, with a total duration of 1 radio frame: T_f = 10 ms.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +Figure 18viA: Frame structure for Secondary Common Control Physical Channel frame type 2. The diagram shows a hierarchical view of the frame structure. At the top, a slot is shown with a TFCI field (N\_TFCI bits) and a Data field (N\_data1 bits). The total number of bits in a slot is m\*144 bits (where m = 2, 4). This is spread into 256 chips. A dashed box labeled (Tx OFF) is shown at the end of the slot. Below this, a subframe is shown, consisting of multiple slots (Slot #0, Slot #1, Slot #2). The total duration of a subframe is T\_subframe = 7680 chips. The subframe index is i. The start position of the subframe within the radio frame is i\*7680 chips. A dashed box labeled (Tx OFF) is shown at the beginning and end of the subframe. At the bottom, a radio frame is shown, with a total duration of 1 radio frame: T\_f = 10 ms. + +**Figure 18viA: Frame structure for Secondary Common Control Physical Channel frame type 2** + +The parameter $m$ in figure 18viA determines the total number of bits per Secondary CCPCH slot. The parameter $m$ takes the value of 2 for QPSK modulation and 4 for 16-QAM modulation. The sub-frame index $i$ in figure 18viA determines the start position of the sub-frame within the radio frame. + +The values for the number of bits per field are given in table 8iA in which the channel bit and symbol rates are the rates immediately before spreading. + +A FACH transport channel may be mapped to one Secondary CCPCH of frame type 1 or to one or more Secondary CCPCHs of frame type 2 that reside within the same sub-frame. + +**Table 8iA: Secondary CCPCH frame type 1 and 2 fields** + +| Slot Format #i | Channel Bit Rate (kbps) | Channel Symbol Rate (kbps) | SF | S-CCPCH frame type | Bits/Frame | Bits/Slot | N_data1 | N_TFCI | +|----------------|-------------------------|----------------------------|-----|--------------------|------------|-----------|---------|--------| +| 0 | 30 | 15 | 256 | 1 | 270 | 18 | 18 | 0 | +| 1 | 30 | 15 | 256 | 1 | 270 | 18 | 16 | 2 | +| 2 | 480 | 240 | 16 | 2 | 864 | 288 | 288 | 0 | +| 3 | 480 | 240 | 16 | 2 | 864 | 288 | 272 | 16 | +| 4* | 960 | 240 | 16 | 2 | 1728 | 576 | 576 | 0 | +| 5* | 960 | 240 | 16 | 2 | 1728 | 576 | 560 | 16** | + +\* Slot formats applicable to 16QAM. + +\*\* This indicates that the number of modulation symbols occupied by TFCI is 4. As described in [7] and [8], QPSK modulation is applied to 8 TFCI bits per slot which results in the same number of 4 TFCI symbols + +For slot formats using TFCI, the TFCI value in each radio frame corresponds to a certain transport format combination of the FACHs currently in use. This correspondence is (re-)negotiated at each FACH addition/removal. The mapping of the TFCI bits onto slots for the IMB option is described in [7]. + +In the case of S-CCPCH frame type 1, when an S-CCPCH CCTrCH carries TFCI, the TFCI field shall be present on all slots of the radio frame. In this case there is only one S-CCPCH in the CCTrCH. + +In the case of S-CCPCH frame type 2, when an S-CCPCH CCTrCH carries TFCI, the TFCI field shall be present on all slots of the sub-frame for the S-CCPCH with the lowest channelization code index in the CCTrCH. In this case, the TFCI field shall not be present on the other S-CCPCHs of the same CCTrCH. + +### 5.8.2.5 Synchronisation channel (SCH) + +The Synchronisation Channel (SCH) is a downlink signal used for cell search and radio frame synchronisation on the MBSFN carrier. The SCH consists of two sub channels, the Primary and Secondary SCH. The 10 ms radio frames of the Primary and Secondary SCH are divided into 15 slots, each of length 2560 chips. Figure 18viiA illustrates the structure of the SCH radio frame. + +![Figure 18viiA: Structure of Synchronisation Channel (SCH). The diagram illustrates a 10 ms SCH radio frame divided into 15 slots, from Slot #0 to Slot #14. Each slot contains a Primary SCH block labeled ac_p and a Secondary SCH block labeled ac_s^{i,k}. For Slot #0, the secondary block is ac_s^{i,0}; for Slot #1, it is ac_s^{i,1}; and for Slot #14, it is ac_s^{i,14}. The width of these blocks is indicated as 256 chips. The total width of a slot is 2560 chips. The entire frame is labeled as 'One 10 ms SCH radio frame'.](df1966d80c74bc127f159a48f38b13ee_img.jpg) + +Figure 18viiA: Structure of Synchronisation Channel (SCH). The diagram illustrates a 10 ms SCH radio frame divided into 15 slots, from Slot #0 to Slot #14. Each slot contains a Primary SCH block labeled ac\_p and a Secondary SCH block labeled ac\_s^{i,k}. For Slot #0, the secondary block is ac\_s^{i,0}; for Slot #1, it is ac\_s^{i,1}; and for Slot #14, it is ac\_s^{i,14}. The width of these blocks is indicated as 256 chips. The total width of a slot is 2560 chips. The entire frame is labeled as 'One 10 ms SCH radio frame'. + +**Figure 18viiA: Structure of Synchronisation Channel (SCH)** + +The Primary SCH consists of a modulated code of length 256 chips, the Primary Synchronisation Code (PSC) denoted $c_p$ in figure 18viiA, transmitted once every slot. The PSC is the same for every cell in the system. + +The Secondary SCH consists of repeatedly transmitting a length 15 sequence of modulated codes of length 256 chips, the Secondary Synchronisation Codes (SSC), transmitted in parallel with the Primary SCH. The SSC is denoted $c_s^{i,k}$ in figure 18viiA, where $i = 0, 1, \dots, 7$ is the number of the scrambling code group, and $k = 0, 1, \dots, 14$ is the slot number. Each SSC is chosen from a set of 16 different codes of length 256. This sequence on the Secondary SCH indicates which of the code groups the cell's downlink scrambling code belongs to. + +The primary and secondary synchronization codes for the MBSFN IMB option, defined in [8], are modulated by the symbol $a = -1$ . + +### 5.8.2.6 The MBMS indicator channel (MICH) + +The MBMS Indicator Channel (MICH) is a fixed rate (SF=256) physical channel used to carry the MBMS notification indicators. The MICH is always associated with an S-CCPCH frame type 1 to which a FACH transport channel carrying MBMS control data is mapped. MICH uses QPSK modulation. + +Figure 18viiiA illustrates the frame structure of the MICH where the 10 ms radio frames of the MICH are divided into 15 slots, each of length 2560 chips. One MICH radio frame of length 10 ms consists of 270 bits ( $b_0, b_1, \dots, b_{269}$ ). Of these, 256 bits ( $b_0, b_1, \dots, b_{255}$ ) are used to carry notification indicators. The remaining 14 bits are not formally part of the MICH and shall not be transmitted (DTX). This implies that the transmitter is turned off during the last 2048 chips of slot #14 in every radio frame. + +![Figure 18viiiA: Structure of MBMS Indicator Channel (MICH). The diagram shows a 10 ms radio frame (T_f = 10 ms) divided into 15 slots (Slot #0, Slot #1, ..., Slot #i, ..., Slot #14). An expanded view of a single slot shows it is divided into a 'Data' section where N_{data1} = 18 bits, and a final section of 256 chips labeled '(Tx OFF)'. The total slot duration is T_{slot} = 2560 chips, 20 bits.](1ca688982d625c3b8a8e382b675de466_img.jpg) + +Figure 18viiiA: Structure of MBMS Indicator Channel (MICH). The diagram shows a 10 ms radio frame (T\_f = 10 ms) divided into 15 slots (Slot #0, Slot #1, ..., Slot #i, ..., Slot #14). An expanded view of a single slot shows it is divided into a 'Data' section where N\_{data1} = 18 bits, and a final section of 256 chips labeled '(Tx OFF)'. The total slot duration is T\_{slot} = 2560 chips, 20 bits. + +**Figure 18viiiA: Frame structure for the MBMS Indicator Channel (MICH)** + +In each MICH frame, $N_n$ notification indicators $\{N_0, \dots, N_{N_n-1}\}$ are transmitted, where $N_n=16, 32, 64, \text{ or } 128$ . + +The NI calculated by higher layers is associated to the index $q$ of the notification indicator $N_q$ , where $q$ is computed as a function of the NI computed by higher layers, the SFN of the P-CCPCH radio frame during which the start of the MICH radio frame occurs, and the number of notification indicators per frame ( $N_n$ ): + +where $G = 2^{16}$ , $C = 25033$ and NI is the 16 bit Notification Indicator calculated by higher layers. + +The set of NI signalled over Iub indicates all higher layer NI values for which the associated notification indicator on MICH shall be set to 1 during the corresponding modification period. Hence, the calculation in the formula above shall be performed in the Node B every MICH frame for each NI signalled over Iub to make the association between NI and $q$ and set the related $N_q$ to 1. All other notification indicators on MICH shall be set to 0. + +The mapping from $\{N_0, \dots, N_{N_n-1}\}$ to the MICH bits $\{b_0, \dots, b_{255}\}$ are according to table 8iiA. + +**Table 8iiA: Mapping of notification indicators $N_q$ to MICH bits** + +| Number of notification indicators per frame ( $N_n$ ) | $N_q = 1$ | $N_q = 0$ | +|-------------------------------------------------------|-------------------------------------------------------|-------------------------------------------------------| +| $N_n=16$ | $\{b_{16q}, \dots, b_{16q+15}\} = \{1, 1, \dots, 1\}$ | $\{b_{16q}, \dots, b_{16q+15}\} = \{0, 0, \dots, 0\}$ | +| $N_n=32$ | $\{b_{8q}, \dots, b_{8q+7}\} = \{1, 1, \dots, 1\}$ | $\{b_{8q}, \dots, b_{8q+7}\} = \{0, 0, \dots, 0\}$ | +| $N_n=64$ | $\{b_{4q}, \dots, b_{4q+3}\} = \{1, 1, \dots, 1\}$ | $\{b_{4q}, \dots, b_{4q+3}\} = \{0, 0, \dots, 0\}$ | +| $N_n=128$ | $\{b_{2q}, b_{2q+1}\} = \{1, 1\}$ | $\{b_{2q}, b_{2q+1}\} = \{0, 0\}$ | + +### 5.8.3 Timing relationship between physical channels + +Timing between the common physical channels is summarized in figure 18ixA. The P-CCPCH, on which the cell SFN is transmitted, is used as timing reference for all the physical channels. The SCH, P-CPICH, T-CPICH, P-CCPCH and S-CCPCH frame types 1 and 2 have identical radio frame timings. The sub-frame number $i$ of an S-CCPCH frame type 2 radio frame is signalled by higher layers. The start position of an S-CCPCH frame type 2 sub-frame is then given by, $\tau_{MICH}$ , chips after the start of the radio frame. + +The frame timing of MICH is advanced by $\tau_{MICH} = 3$ slots (7680 chips) with respect to the timings of the other physical channels. + +![Figure 18ixA: Radio frame and sub-frame timing of downlink physical channels. The diagram shows the timing of various physical channels over two consecutive 10 ms radio frames. The channels are Primary SCH, Secondary SCH, P-CPICH, T-CPICH, P-CCPCH, S-CCPCH frame type 1, S-CCPCH frame type 2, and MICH. The P-CCPCH channel is divided into two 10 ms frames based on (SFN modulo 2). The S-CCPCH frame type 2 channel shows a subframe #i starting at i*7680 chips. The MICH channel shows a timing offset tau_MICH.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +The diagram illustrates the timing of downlink physical channels across two 10 ms radio frames. The channels shown are: + +- Primary SCH** and **Secondary SCH**: Continuous bursts of 256 chips every 2.5 ms. +- P-CPICH**: A continuous burst of 256 chips every 2.5 ms. +- T-CPICH**: Continuous bursts of 256 chips every 2.5 ms. +- P-CCPCH**: Divided into two 10 ms frames: "Radio frame with (SFN modulo 2) = 0" and "Radio frame with (SFN modulo 2) = 1". +- S-CCPCH frame type 1**: Continuous bursts of 256 chips every 2.5 ms. +- S-CCPCH frame type 2**: Shows a subframe #i starting at $i \cdot 7680$ chips. +- MICH**: Shows a timing offset $\tau_{\text{MICH}}$ relative to the start of the second radio frame. + +The total duration shown is 20 ms, divided into two 10 ms radio frames. + +Figure 18ixA: Radio frame and sub-frame timing of downlink physical channels. The diagram shows the timing of various physical channels over two consecutive 10 ms radio frames. The channels are Primary SCH, Secondary SCH, P-CPICH, T-CPICH, P-CCPCH, S-CCPCH frame type 1, S-CCPCH frame type 2, and MICH. The P-CCPCH channel is divided into two 10 ms frames based on (SFN modulo 2). The S-CCPCH frame type 2 channel shows a subframe #i starting at i\*7680 chips. The MICH channel shows a timing offset tau\_MICH. + +Figure 18ixA: Radio frame and sub-frame timing of downlink physical channels + +## 5A Physical channels for the 1.28 Mcps option + +All physical channels take three-layer structure with respect to timeslots, radio frames and system frame numbering (SFN), see [14]. Depending on the resource allocation, the configuration of radio frames or timeslots becomes different. All physical channels need guard symbols in every timeslot. The time slots are used in the sense of a TDMA component to separate different user signals in the time and the code domain. The physical channel signal format for 1.28 Mcps TDD is presented in figure 18A. + +A physical channel in TDD is a burst, which is transmitted in a particular timeslot within allocated Radio Frames. The allocation can be continuous, i.e. the time slot in every frame is allocated to the physical channel or discontinuous, i.e. the time slot in a subset of all frames is allocated only. A burst is the combination of a data part, a midamble and a guard period or only a midamble for standalone midamble channel. The duration of a burst is one time slot. Note when in the entire carrier dedicated to MBSFN operation, a burst is the combination of a preamble and a data part. Several bursts can be transmitted at the same time from one transmitter. In this case, the data part must use different OVSF channelisation codes, but the same scrambling code. The midamble part has to use the same basic midamble code, but can use different midambles. In a multi-frequency cell the midamble parts in different carrier shall also have to use the same basic midamble code, but can use different midambles. Note when in MBSFN operation, a midamble or preamble is not necessarily cell-specific. + +![Figure 18A: Physical channel signal format for 1.28Mcps TDD option. The diagram shows a hierarchy of time intervals: a Radio frame (10ms) containing frame #i and frame #i+1; a subframe (5ms) containing subframe #1 and subframe #2; and timeslots #0, #1, #2, and #6. Arrows indicate the nesting of these intervals.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +Figure 18A: Physical channel signal format for 1.28Mcps TDD option. The diagram shows a hierarchy of time intervals: a Radio frame (10ms) containing frame #i and frame #i+1; a subframe (5ms) containing subframe #1 and subframe #2; and timeslots #0, #1, #2, and #6. Arrows indicate the nesting of these intervals. + +**Figure 18A: Physical channel signal format for 1.28Mcps TDD option** + +The data part of the burst is spread with a combination of channelisation code and scrambling code. The channelisation code is a OVSF code, that can have a spreading factor of 1, 2, 4, 8, or 16. The data rate of the physical channel is depending on the used spreading factor of the used OVSF code. + +So a physical channel is defined by frequency, timeslot, channelisation code, burst type and Radio Frame allocation. The scrambling code and the basic midamble code or preamble code are broadcast and may be constant within a cell. When a physical channel is established, a start frame is given. The physical channels can either be of infinite duration, or a duration for the allocation can be defined. + +## 5A.1 Frame structure + +The TDMA frame has duration of 10 ms and is divided into 2 sub-frames of 5ms. The frame structure for each sub-frame in the 10ms frame length is the same. + +![Figure 18B: Structure of the sub-frame for 1.28Mcps TDD option. The diagram shows a 5ms subframe (6400chip) divided into 7 traffic time slots. The first slot is DwPTS (96chips) with a downlink arrow. The second slot is GP (96chips). The third slot is UpPTS (160chips) with an uplink arrow. The remaining four slots are traffic slots with uplink arrows. A 'Switching Point' is indicated between the DwPTS and GP slots, and another between the UpPTS and the first traffic slot.](90df9788d66ecf65abf861caf76be5ca_img.jpg) + +Figure 18B: Structure of the sub-frame for 1.28Mcps TDD option. The diagram shows a 5ms subframe (6400chip) divided into 7 traffic time slots. The first slot is DwPTS (96chips) with a downlink arrow. The second slot is GP (96chips). The third slot is UpPTS (160chips) with an uplink arrow. The remaining four slots are traffic slots with uplink arrows. A 'Switching Point' is indicated between the DwPTS and GP slots, and another between the UpPTS and the first traffic slot. + +**Figure 18B: Structure of the sub-frame for 1.28Mcps TDD option** + +- Time slot#n (n from 0 to 6): the nth traffic time slot, 864 chips duration; +- DwPTS: downlink pilot time slot, 96 chips duration; +- UpPTS: uplink pilot time slot, 160 chips duration; +- GP: main guard period for TDD operation, 96 chips duration; + +In Figure 18B, the total number of traffic time slots for uplink and downlink is 7, and the length for each traffic time slot is 864 chips duration. Among the 7 traffic time slots, time slot#0 is always allocated as downlink while time slot#1 is always allocated as uplink. The time slots for the uplink and the downlink are separated by switching points. Between the downlink time slots and uplink time slots, the special period is the switching point to separate the uplink and + +downlink. In each sub-frame of 5ms for 1.28Mcps option, there are two switching points (uplink to downlink and vice versa). + +Using the above frame structure, the 1.28Mcps TDD option can operate on both symmetric and asymmetric mode by properly configuring the number of downlink and uplink time slots. In any configuration at least one time slot (time slot#0) has to be allocated for the downlink and at least one time slot has to be allocated for the uplink (time slot#1). + +In case of entire carrier dedicated to MBSFN, no uplink timeslot is used, and DwPTS, UpPTS and GP(96 chips duration) are combined into one short timeslot, the duration of which is 0.275ms. + +In a multi-frequency cell the traffic time slots allocated for uplink and downlink pair(s) for one UE should be on the same carrier. + +Examples for symmetric and asymmetric UL/DL allocations are given in figure 18C. + +![Figure 18C: 1.28Mcps TDD sub-frame structure examples. The diagram shows three examples of 5ms sub-frames, each divided into 10 time slots. The first example, 'Symmetric DL/UL allocation', shows 5 downlink slots (indicated by downward arrows) and 5 uplink slots (indicated by upward arrows). The second example, 'Asymmetric DL/UL allocation', shows 6 downlink slots and 4 uplink slots. The third example, 'Entire carrier dedicated to MBSFN', shows 10 downlink slots and 0 uplink slots. Each sub-frame is labeled '5 ms' above it.](367378559e35017a5e1a6f5c30798c5a_img.jpg) + +Figure 18C: 1.28Mcps TDD sub-frame structure examples. The diagram shows three examples of 5ms sub-frames, each divided into 10 time slots. The first example, 'Symmetric DL/UL allocation', shows 5 downlink slots (indicated by downward arrows) and 5 uplink slots (indicated by upward arrows). The second example, 'Asymmetric DL/UL allocation', shows 6 downlink slots and 4 uplink slots. The third example, 'Entire carrier dedicated to MBSFN', shows 10 downlink slots and 0 uplink slots. Each sub-frame is labeled '5 ms' above it. + +Figure 18C: 1.28Mcps TDD sub-frame structure examples + +Note 1: In a multi-frequency cell, it is suggested the switching point configuration on secondary frequencies to be the same as that on primary frequency. + +## 5A.2 Dedicated physical channel (DPCH) + +The DCH as described in subclause 4.1.1 'Dedicated transport channels' is mapped onto the dedicated physical channel. + +### 5A.2.1 Spreading + +The spreading of physical channels is the same as in 3.84 Mcps TDD (cf. 5.2.1 'Spreading'). When there are more than two uplink physical channels to be transmitted in one timeslot, UE shall always guarantee the transmission of DPCH with data to be transmitted and non-scheduled E-PUCH. + +### 5A.2.2 Burst Format + +A traffic burst consists of two data symbol fields, a midamble of 144 chips and a guard period. The data fields of the burst are 352 chips long. The corresponding number of symbols depends on the spreading factor, as indicated in table 8A below. The guard period is 16 chip periods long. + +The burst format is shown in Figure 18D. The contents of the traffic burst fields is described in table 8B. + +**Table 8A: number of symbols per data field in a traffic burst** + +| Spreading factor (Q) | Number of symbols (N) per data field in Burst | +|----------------------|-----------------------------------------------| +| 1 | 352 | +| 2 | 176 | +| 4 | 88 | +| 8 | 44 | +| 16 | 22 | + +**Table 8B: The contents of the traffic burst format fields** + +| Chip number (CN) | Length of field in chips | Length of field in symbols | Contents of field | +|------------------|--------------------------|----------------------------|-------------------| +| 0-351 | 352 | cf table 8A | Data symbols | +| 352-495 | 144 | - | Midamble | +| 496-847 | 352 | cf table 8A | Data symbols | +| 848-863 | 16 | - | Guard period | + +![Diagram of burst structure showing four fields: Data symbols (352 chips), Midamble (144 chips), Data symbols (352 chips), and Guard Period (16 chips). A double-headed arrow below indicates the total duration is 864 * Tc.](10b0dda884baae493ad958422d11b552_img.jpg) + +| | | | | +|---------------------------|-----------------------|---------------------------|----------------| +| Data symbols
352 chips | Midamble
144 chips | Data symbols
352 chips | GP
16
CP | +|---------------------------|-----------------------|---------------------------|----------------| + +$864 \cdot T_c$ + +Diagram of burst structure showing four fields: Data symbols (352 chips), Midamble (144 chips), Data symbols (352 chips), and Guard Period (16 chips). A double-headed arrow below indicates the total duration is 864 \* Tc. + +**Figure 18D: Burst structure of the traffic burst format (GP denotes the guard period and CP the chip periods)** + +## 5A.2.2a Dedicated carrier MBSFN Burst Format + +In this case, there are two bursts, one is MBSFN Traffic burst (MT burst) for 7 normal timeslots, and the other is MBSFN Special burst (MS burst) for 1 short timeslot. Both of them consist of a preamble and a data symbol field, the lengths of which are different for the individual bursts. Thus, the number of data symbols in a burst depends on the SF and the burst type, as depicted in table 8A.a. + +**Table 8A.a: number of symbols per data field in a MBSFN burst** + +| Spreading factor (Q) | Number of symbols (N) per data field in Burst | | +|----------------------|-----------------------------------------------|----------| +| | MT Burst | MS Burst | +| 1 | 768 | N/A | +| 2 | 384 | N/A | +| 16 | 48 | 16 | + +*Note: MS burst only supports SF=16.* + +The support of both bursts is mandatory and only used in dedicated carrier MBSFN. The both different bursts defined here are well suited for this application, as described in the following paragraphs. + +The MT burst can be used for the regular timeslots, the duration of which is 0.675ms. The data fields of the MT burst are 768 chips long. The corresponding number of symbols depends on the spreading factor, as indicated in table 8A.a above. The preamble of MT burst has a length of 96 chips. The MT burst is shown in Figure 18D.a. The contents of the burst fields are described in table 8B.a. + +**Table 8B.a: The contents of the MT burst** + +| Chip number (CN) | Length of field in chips | Length of field in symbols | Contents of field | +|------------------|--------------------------|----------------------------|-------------------| +| 0-95 | 96 | - | Preamble | +| 96-863 | 768 | cf table 8A.a | Data symbols | + +![Figure 18D.a: Burst structure of the MT burst. The diagram shows a horizontal rectangle divided into two parts by a vertical line. Below the rectangle is a double-headed arrow spanning its entire length.](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +Figure 18D.a: Burst structure of the MT burst. The diagram shows a horizontal rectangle divided into two parts by a vertical line. Below the rectangle is a double-headed arrow spanning its entire length. + +**Figure 18D.a: Burst structure of the MT burst** + +The MS burst can be used for the short timeslot, the duration of which is 0.275ms. The data fields of the MS burst are 256 chips long. The corresponding number of symbols is 16, as indicated in table 8A.a above. The preamble of the MS burst has a length of 96 chips. The MS burst format is shown in Figure 18D.b. The contents of the burst fields are described in table 8B.b. + +**Table 8B.b: The contents of the MS burst** + +| Chip number (CN) | Length of field in chips | Length of field in symbols | Contents of field | +|------------------|--------------------------|----------------------------|-------------------| +| 0-95 | 96 | - | Preamble | +| 96-351 | 256 | cf table 8A.a | Data symbols | + +![Figure 18D.b: Burst structure of the MS burst. The diagram shows a horizontal rectangle divided into two parts by a vertical line. Below the rectangle is a double-headed arrow spanning its entire length.](91b12db3c85bbf466ad27eb3665a1b06_img.jpg) + +Figure 18D.b: Burst structure of the MS burst. The diagram shows a horizontal rectangle divided into two parts by a vertical line. Below the rectangle is a double-headed arrow spanning its entire length. + +**Figure 18D.b: Burst structure of the MS burst** + +### 5A.2.2.1 Transmission of TFCI + +The traffic burst format provides the possibility for transmission of TFCI in uplink and downlink. + +The transmission of TFCI is configured by higher Layers. For each CCTrCH it is indicated by higher layer signalling, which TFCI format is applied. Additionally for each allocated timeslot it is signalled individually whether that timeslot carries the TFCI or not. The TFCI is always present in the first timeslot in a radio frame for each CCTrCH. If a time slot contains the TFCI, then it is always transmitted using the physical channel with the lowest physical channel sequence number (*p*) in that timeslot. Physical channel sequence numbering is determined by the rate matching function and is described in [7]. + +The transmission of TFCI is done in the data parts of the respective physical channel, this means that TFCI code word bits and data bits are subject to the same spreading procedure as depicted in [8]. Hence the midamble structure and length is not changed. + +The TFCI code word bits are equally distributed between the two subframes and the respective data fields. The TFCI code word is to be transmitted possibly either directly adjacent to the midamble or after the SS and TPC symbols. Figure 18E shows the position of the TFCI code word in a traffic burst, if neither SS nor TPC are transmitted. Figure 18F shows the position of the TFCI code word in a traffic burst , if SS and TPC are transmitted. + +Error: + +60 + +Error: Reference source not + +![Figure 18E: Position of the TFCI code word in the traffic burst in case of no TPC and SS in 1.28 Mcps TDD. The diagram shows a 10ms Radio Frame consisting of two 5ms Sub-frames. Each sub-frame contains a Time slot x (864 Chips). The first sub-frame shows the 1st part of the TFCI code word at the end of the first data symbol block and the 2nd part at the beginning of the second data symbol block, flanking the Midamble. The second sub-frame shows the 3rd and 4th parts in similar positions. A Guard Period (GP) is at the end of each time slot.](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +Figure 18E: Position of the TFCI code word in the traffic burst in case of no TPC and SS in 1.28 Mcps TDD. The diagram shows a 10ms Radio Frame consisting of two 5ms Sub-frames. Each sub-frame contains a Time slot x (864 Chips). The first sub-frame shows the 1st part of the TFCI code word at the end of the first data symbol block and the 2nd part at the beginning of the second data symbol block, flanking the Midamble. The second sub-frame shows the 3rd and 4th parts in similar positions. A Guard Period (GP) is at the end of each time slot. + +**Figure 18E: Position of the TFCI code word in the traffic burst in case of no TPC and SS in 1.28 Mcps TDD** + +![Figure 18F: Position of the TFCI code word in the traffic burst in case of TPC and SS in 1.28 Mcps TDD. This diagram follows the structure of Figure 18E but adds SS symbols and TPC symbols. In the first sub-frame, SS symbols follow the 1st part of the TFCI code word, and TPC symbols precede the 2nd part. This pattern is repeated for the 3rd and 4th parts in the second sub-frame.](848073118eebfdbfdb9a60e3923fe0b3_img.jpg) + +Figure 18F: Position of the TFCI code word in the traffic burst in case of TPC and SS in 1.28 Mcps TDD. This diagram follows the structure of Figure 18E but adds SS symbols and TPC symbols. In the first sub-frame, SS symbols follow the 1st part of the TFCI code word, and TPC symbols precede the 2nd part. This pattern is repeated for the 3rd and 4th parts in the second sub-frame. + +**Figure 18F: Position of the TFCI code word in the traffic burst in case of TPC and SS in 1.28 Mcps TDD** + +#### 5A.2.2.1a Transmission of TFCI for MT burst and MS burst + +Both MT burst and MS burst provide the possibility for transmission of TFCI in downlink. The procedure of transmitting TFCI is the same as 5A.2.2. + +The transmission of TFCI is done in the data parts of the respective physical channel, this means that TFCI code word bits and data bits are subject to the same spreading procedure as depicted in [8]. Hence the preamble structure and length is not changed. + +The TFCI code word bits are equally distributed among the four subframes and the respective data fields. The TFCI code word is to be transmitted directly at the beginning and at the end of data symbols. Figure 18E.a shows the position of the TFCI code word in the MT burst. Figure 18E.b shows the position of the TFCI code word in the MS burst. + +Note: when the modulation is 16QAM the number of the TFCI bits need be expanded. The procedure of expansion is detailed described in [7] + +![Figure 18E.a: Position of the TFCI code word in the MT burst format in 1.28 Mcps TDD. The diagram illustrates four consecutive sub-frames. In each sub-frame, small rectangular blocks representing TFCI code word segments are placed at the very beginning and the very end of the data symbol sections, surrounding the central midamble area.](1043999278be2d0d419a47a907d4db77_img.jpg) + +Figure 18E.a: Position of the TFCI code word in the MT burst format in 1.28 Mcps TDD. The diagram illustrates four consecutive sub-frames. In each sub-frame, small rectangular blocks representing TFCI code word segments are placed at the very beginning and the very end of the data symbol sections, surrounding the central midamble area. + +**Figure 18E.a: Position of the TFCI code word in the MT burst format in 1.28 Mcps TDD** + +![Figure 18E.b: Position of the TFCI code word in the MS burst format in 1.28 Mcps TDD. The diagram shows two identical burst structures. Each burst contains a midamble (a rectangle with two diagonal lines) and two TFCI code words (smaller rectangles). Arrows indicate the start and end of the TFCI code words within the burst. A horizontal line with arrows at the ends indicates the total duration of the burst.](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +Figure 18E.b: Position of the TFCI code word in the MS burst format in 1.28 Mcps TDD. The diagram shows two identical burst structures. Each burst contains a midamble (a rectangle with two diagonal lines) and two TFCI code words (smaller rectangles). Arrows indicate the start and end of the TFCI code words within the burst. A horizontal line with arrows at the ends indicates the total duration of the burst. + +Figure 18E.b: Position of the TFCI code word in the MS burst format in 1.28 Mcps TDD + +### 5A.2.2.2 Transmission of TPC + +In this section, transmission of TPC over dedicated physical channels is described. Optionally, UTRAN may configure some UL CCTrCH's to be controlled via TPC commands on PLCCH (for example in the case of HS-DSCH operation without an associated downlink DPCH). PLCCH is described in section 5A.3.13. + +Within the context of this subclause, only those TPC commands not borne by PLCCH (in the DL case) nor by PLCCH-controlled physical channels (in the UL case) are considered. That is to say that those UL timeslot/CCTrCH pairs controlled by PLCCH and those DL TPC commands mapped to PLCCH are excluded from consideration when deriving the mapping between UL/DL TPC commands and the UL/DL CCTrCH's they control. The association between PLCCH and UL timeslot/CCTrCH pair(s) is signalled by higher layers. + +The burst type for dedicated channels provides the possibility for transmission of TPC in uplink and downlink. + +The transmission of TPC is done in the data parts of the traffic burst. Hence the midamble structure and length is not changed. The TPC information is to be transmitted directly after the SS information, which is transmitted after the midamble. Figure 18G shows the position of the TPC command in a traffic burst. + +For every user the TPC information is to be transmitted at least once per 5ms sub-frame. For each allocated timeslot it is signalled individually whether that timeslot carries TPC information or not. If applied in a timeslot, transmission of TPC symbols is done in the data parts of the traffic burst and they are transmitted using the physical channel with the lowest physical channel sequence number ( $p$ ) in that timeslot. Physical channel sequence numbering is determined by the rate matching function and is described in [7]. + +TPC symbols may also be transmitted on more than one physical channel in a time slot. For this purpose, higher layers allocate an additional number of $N_{TPC}$ physical channels, individually for each time slot. The TPC symbols shall then be transmitted using the physical channels with the $N_{TPC}+1$ lowest physical channel sequence numbers ( $p$ ) in that time slot. Physical channel sequence numbering is determined by the rate matching function and is described in [7]. If the rate matching function results in $N_{RM} < N_{TPC}+1$ remaining physical channels in this time slot, TPC symbols shall be transmitted only on the $N_{RM}$ remaining physical channels. + +The TPC symbols are spread with the same spreading factor (SF) and spreading code as the data parts of the respective physical channel. + +![Figure 18G: Position of TPC information in the traffic burst in downlink and uplink. The diagram shows a traffic burst structure: Data symbols, Midamble, SS symbol(s), TPC symbol(s) (highlighted in yellow), Data symbols, and GP. A double-headed arrow below the Midamble indicates a length of 144 chips. A longer double-headed arrow below the entire burst (from the start of the first Data symbols to the start of the GP) indicates a total length of 864 Chips.](3d5f590e40a34de3e874fd845a4efd53_img.jpg) + +Figure 18G: Position of TPC information in the traffic burst in downlink and uplink. The diagram shows a traffic burst structure: Data symbols, Midamble, SS symbol(s), TPC symbol(s) (highlighted in yellow), Data symbols, and GP. A double-headed arrow below the Midamble indicates a length of 144 chips. A longer double-headed arrow below the entire burst (from the start of the first Data symbols to the start of the GP) indicates a total length of 864 Chips. + +Figure 18G: Position of TPC information in the traffic burst in downlink and uplink + +For the number of TPC symbols per time slot there are 3 possibilities, that can be configured by higher layers, individually for each timeslot: + +- e) 1) one TPC symbol + +- f) 2) no TPC symbols +- g) 3) 16/SF TPC symbols + +So, in case 3), when SF=1, there are 16 TPC symbols which correspond to 32 bits (for QPSK) and 48 bits (for 8PSK). + +In the following the uplink is described only. For the description of the downlink, downlink (DL) and uplink (UL) have to be interchanged. + +Each of the TPC symbols for uplink power control in the DL will be associated with an UL time slot and an UL CCTrCH pair. This association varies with + +- the number of allocated UL time slots and UL CCTrCHs on these time slots (time slot and CCTrCH pair) and +- the allocated TPC symbols in the DL. + +In case a UE has + +- more than one channelisation code + +and/or + +- channelisation codes being of lower spreading factor than 16 and using 16/SF SS and 16/SF TPC symbols, + +the TPC commands for each UL time slot CCTrCH pair (all channelisation codes on that time slot belonging to the same time slot and CCTrCH pair have the same TPC command) will be distributed to the following rules: + +1. The UL time slots and CCTrCH pairs the TPC commands are intended for will be numbered from the first to the last UL time slot and CCTrCH pair allocated to the regarded UE (starting with 0). The number of a time slot and CCTrCH pair is smaller than the number of another time slot and CCTrCH pair within the same time slot if its spreading code with the lowest SC number according to the following table has a lower SC number than the spreading code with the lowest SC number of the other time slot and CCTrCH pair. +2. The commanding TPC symbols on all DL CCTrCHs allocated to one UE are numbered consecutively starting with zero according to the following rules: + - a) The numbers of the TPC commands of a regarded DL time slot are lower than those of DL time slots being transmitted after that time slot + - b) Within a DL time slot the numbers of the TPC commands of a regarded channelisation code are lower than those of channelisation codes having a higher spreading code number + +The spreading code number is defined by the following table (see[8]): + +| SC number | SF (Q) | Walsh code number (k) | +|-----------|--------|-----------------------| +| 0 | 16 | $c_{Q=16}^{(k=1)}$ | +| | ... | | +| 15 | 16 | $c_{Q=16}^{(k=16)}$ | +| 16 | 8 | $c_{Q=8}^{(k=1)}$ | +| | ... | | +| 23 | 8 | $c_{Q=8}^{(k=8)}$ | +| 24 | 4 | $c_{Q=4}^{(k=1)}$ | +| | ... | | +| 27 | 4 | $c_{Q=4}^{(k=4)}$ | +| 28 | 2 | $c_{Q=2}^{(k=1)}$ | +| 29 | 2 | $c_{Q=2}^{(k=2)}$ | +| 30 | 1 | $c_{Q=1}^{(k=1)}$ | + +Note: Spreading factors 2-8 are not used in DL + +- c) Within a channelisation code numbers of the TPC commands are lower than those of TPC commands being transmitted after that time + +The following equation is used to determine the UL time slot which is controlled by the regarded TPC symbol in the DL: + +, + +where + +$UL_{pos}$ is the number of the controlled uplink time slot and CCTrCH pairs. + +$SFN'$ is the system frame number counting the sub-frames. The system frame number of the radio frames (SFN) can be derived from $SFN'$ by + +$SFN = SFN' \text{ div } 2$ , where div is the remainder free division operation. + +$N_{UL\_PCsymbols}$ is the number of UL TPC symbols in a sub-frame (excluding those on PLCCH-controlled resources). + +$TPC_{DLpos}$ is the number of the regarded UL TPC symbol in the DL within the sub-frame. + +$N_{ULslot}$ is the number of UL slots and CCTrCH pairs in a sub-frame (excluding those associated with PLCCH). + +When one of the above parameters is changed due to higher layer reconfiguration, the new relationship between TPC symbols and controlled UL time slots shall be valid, beginning with the radio frame, for which the new parameters are set. + +In Annex CB two examples of the association of TPC commands to time slots and CCTrCH pairs are shown. + +Coding of TPC: + +The relationship between the TPC Bits and the transmitter power control command for QPSK is the same as in the 3.84Meps TDD cf. [5.2.2.5 'Transmission of TPC']. + +The relationship between the TPC Bits and the transmitter power control command for 8PSK is given in table 8C + +**Table 8C: TPC Bit Pattern for 8PSK** + +| TPC Bits | TPC command | Meaning | +|----------|-------------|-------------------| +| 000 | 'Down' | Decrease Tx Power | +| 110 | 'Up' | Increase Tx Power | + +### 5A.2.2.3 Transmission of SS + +In this section, transmission of SS over dedicated physical channels is described. Optionally, UTRAN may configure some UL CCTrCH's to be controlled via SS commands on PLCCH (for example in the case of HS-DSCH operation without an associated downlink DPCH). PLCCH is described in section 5A.3.13. + +Within the context of this subclause, only those SS commands not borne by PLCCH are considered. That is to say that those UL timeslots controlled exclusively by PLCCH and those SS commands carried by PLCCH are excluded from consideration when deriving the mapping between DL SS commands and the UL timeslots they control. The association between PLCCH and UL timeslot/CCTrCH pair(s) is signalled by higher layers. + +The burst type for dedicated channels provides the possibility for transmission of uplink synchronisation control (ULSC). + +The transmission of ULSC is done in the data parts of the traffic burst. Hence the midamble structure and length is not changed. The ULSC information is to be transmitted directly after the midamble. Figure 18H shows the position of the SS command in a traffic burst. + +For every user the ULSC information shall be transmitted at least once per transmitted sub-frame. + +For each allocated timeslot it is signalled individually whether that timeslot carries ULSC information or not. If applied in a time slot, transmission of SS symbols is done in the data parts of the traffic burst and they are transmitted using the physical channel with the lowest physical channel sequence number ( $p$ ) in that timeslot. Physical channel sequence numbering is determined by the rate matching function and is described in [7]. + +SS symbols may also be transmitted on more than one physical channel in a time slot. For this purpose, higher layers allocate an additional number of $N_{SS}$ physical channels, individually for each time slot. The SS symbols shall then be transmitted using the physical channels with the $N_{SS}+1$ lowest physical channel sequence numbers ( $p$ ) in that time slot. Physical channel sequence numbering is determined by the rate matching function and is described in [7]. If the rate matching function results in $N_{RM} < N_{SS}+1$ remaining physical channels in this time slot, SS symbols shall be transmitted only on the $N_{RM}$ remaining physical channels. + +The SS symbols are spread with the same spreading factor (SF) and spreading code as the data parts of the respective physical channel. + +The SS is utilised to command a timing adjustment by $(k/8) T_c$ each $M$ sub-frames, where $T_c$ is the chip period. The $k$ and $M$ values are signalled by the network. The SS, as one of L1 signals, is to be transmitted once per 5ms sub-frame. + +$M$ (1-8) and $k$ (1-8) can be adjusted during call setup or readjusted during the call. + +Note: The smallest step for the SS signalled by the UTRAN is $1/8 T_c$ . For the UE capabilities regarding the SS adjustment of the UE it is suggested to set the tolerance for the executed command to be $[1/9; 1/7] T_c$ . + +![Diagram of a traffic burst structure showing the position of SS symbols. The burst consists of Data symbols, a Midamble (144 chips), and a GP. The SS symbol(s) are located at the start of the second Data symbols section, immediately following the Midamble.](42d3842485845d9f6e511e6526061a55_img.jpg) + +The diagram illustrates the structure of a traffic burst. It is a horizontal bar divided into five segments: 'Data symbols', 'Midamble', a small yellow rectangle representing 'SS symbol(s)', 'Data symbols', and 'GP'. Below the 'Midamble' segment, a double-headed arrow indicates its length as '144 chips'. Below the entire bar, another double-headed arrow indicates the total length as '864 Chips'. An arrow points from the text 'SS symbol(s)' to the yellow rectangle. + +Diagram of a traffic burst structure showing the position of SS symbols. The burst consists of Data symbols, a Midamble (144 chips), and a GP. The SS symbol(s) are located at the start of the second Data symbols section, immediately following the Midamble. + +**Figure 18H: Position of ULSC information in the traffic burst (downlink and uplink)** + +Note that for the uplink where there is no SS symbol used, the SS symbol space is reserved for future use. This can keep UL and DL slots the same structure. + +For the number of SS symbols per time slot there are 3 possibilities, that can be configured by higher layers individually for each time slot: + +- one SS symbol +- no SS symbol +- 16/SF SS symbols + +So, in case 3, when SF=1, there are 16 SS symbols which correspond to 32 bits (for QPSK) and 48 bits (for 8PSK). + +Each of the SS symbols in the DL will be associated with an UL time slot depending on the allocated UL time slots and the allocated SS symbols in the DL. + +Note: Even though the different time slots of the UE are controlled with independent SS commands, the UE is not in need to execute SS commands leading to a deviation of more than [3] chip with respect to the average timing advance applied by the UE. + +The synchronisation shift commands for each UL time slot (all channelisation codes on that time slot have the same SS command) will be distributed to the following rules: + +1. The UL time slots the SS commands are intended for will be numbered from the first to the last UL time slot occupied by the regarded UE (starting with 0) considering all CCTrCHs allocated to that UE. +2. The commanding SS symbols on all downlink CCTrCHs allocated to one UE are numbered consecutively starting with zero according to the following rules: + - a) The numbers of the SS commands of a regarded DL time slot are lower than those of DL time slots being transmitted after that time slot + - b) Within a DL time slot the numbers of the SS commands of a regarded channelisation code are lower than those of channelisation codes having a bigger spreading code number + +The spreading code number is defined by the following table: (see TS 25.223) + +| Spreading code number | SF (Q) | Walsh code number (k) | +|-----------------------|------------------------------------------|-----------------------| +| 0 | 16 | $c_{Q=16}^{(k=1)}$ | +| | ... | | +| 15 | 16 | $c_{Q=16}^{(k=16)}$ | +| | Spreading factors 2-8 are not used in DL | | +| 30 | 1 | $c_{Q=1}^{(k=1)}$ | + +- c) Within a channelisation code numbers of the SS commands are lower than those of SS commands being transmitted after that time + +The following equation is used to determine the UL time slot which is controlled by the regarded SS symbol: + +, + +where + +ULpos is the number of the controlled uplink time slot. + +SFN' is the system frame number counting the sub-frames. The system frame number of the radio frames (SFN) can be derived from SFN' by + +SFN = SFN' div 2, where div is the remainder free division operation. + +NSSsymbols is the number of SS symbols in a sub-frame (excluding those associated with PLCCH). + +SSpos is the number of the regarded SS symbol within the sub-frame. + +NULslot is the number of UL slots in a sub-frame (excluding those slots exclusively controlled by PLCCH). + +When one of the above parameters is changed due to higher layer reconfiguration, the new relationship between SS symbols and controlled UL time slots shall be valid, beginning with the radio frame, for which the new parameters are set. + +The relationship between the SS Bits and the SS command for QPSK is the given in table 8D: + +**Table 8D: Coding of the SS for QPSK** + +| SS Bits | SS command | Meaning | +|---------|--------------|------------------------------------------------------| +| 00 | 'Down' | Decrease synchronisation shift by k/8 T c | +| 11 | 'Up' | Increase synchronisation shift by k/8 T c | +| 01 | 'Do nothing' | No change | + +The relationship between the SS Bits and the SS command for 8PSK is given in table 8E: + +**Table 8E: Coding of the SS for 8PSK** + +| SS Bits | SS command | Meaning | +|---------|--------------|------------------------------------------------------| +| 000 | 'Down' | Decrease synchronisation shift by k/8 T c | +| 110 | 'Up' | Increase synchronisation shift by k/8 T c | +| 011 | 'Do nothing' | No change | + +#### 5A.2.2.4 Timeslot formats + +The timeslot format depends on the spreading factor, the number of the TFCI code word bits, the number of SS and TPC symbols and the applied modulation scheme (QPSK/8PSK) as depicted in the following tables. + +## 5A.2.2.4.1 Timeslot formats for QPSK + +## 5A.2.2.4.1.1 Downlink timeslot formats + +Table 8F : Time slot formats for the Downlink + +| Slot Format # | Spreading Factor | Midamble length (chips) | N TFCI code word (bits) | N SS & N TPC (bits) | Bits/slot | N Data/Slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) | +|---------------|------------------|-------------------------|------------------------------------|-------------------------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------| +| 0 | 16 | 144 | 0 | 0 & 0 | 88 | 88 | 44 | 44 | +| 1 | 16 | 144 | 4 | 0 & 0 | 88 | 86 | 42 | 44 | +| 2 | 16 | 144 | 8 | 0 & 0 | 88 | 84 | 42 | 42 | +| 3 | 16 | 144 | 16 | 0 & 0 | 88 | 80 | 40 | 40 | +| 4 | 16 | 144 | 32 | 0 & 0 | 88 | 72 | 36 | 36 | +| 5 | 16 | 144 | 0 | 2 & 2 | 88 | 84 | 44 | 40 | +| 6 | 16 | 144 | 4 | 2 & 2 | 88 | 82 | 42 | 40 | +| 7 | 16 | 144 | 8 | 2 & 2 | 88 | 80 | 42 | 38 | +| 8 | 16 | 144 | 16 | 2 & 2 | 88 | 76 | 40 | 36 | +| 9 | 16 | 144 | 32 | 2 & 2 | 88 | 68 | 36 | 32 | +| 10 | 1 | 144 | 0 | 0 & 0 | 1408 | 1408 | 704 | 704 | +| 11 | 1 | 144 | 4 | 0 & 0 | 1408 | 1406 | 702 | 704 | +| 12 | 1 | 144 | 8 | 0 & 0 | 1408 | 1404 | 702 | 702 | +| 13 | 1 | 144 | 16 | 0 & 0 | 1408 | 1400 | 700 | 700 | +| 14 | 1 | 144 | 32 | 0 & 0 | 1408 | 1392 | 696 | 696 | +| 15 | 1 | 144 | 0 | 2 & 2 | 1408 | 1404 | 704 | 700 | +| 16 | 1 | 144 | 4 | 2 & 2 | 1408 | 1402 | 702 | 700 | +| 17 | 1 | 144 | 8 | 2 & 2 | 1408 | 1400 | 702 | 698 | +| 18 | 1 | 144 | 16 | 2 & 2 | 1408 | 1396 | 700 | 696 | +| 19 | 1 | 144 | 32 | 2 & 2 | 1408 | 1388 | 696 | 692 | +| 20 | 1 | 144 | 0 | 32 & 32 | 1408 | 1344 | 704 | 640 | +| 21 | 1 | 144 | 4 | 32 & 32 | 1408 | 1342 | 702 | 640 | +| 22 | 1 | 144 | 8 | 32 & 32 | 1408 | 1340 | 702 | 638 | +| 23 | 1 | 144 | 16 | 32 & 32 | 1408 | 1336 | 700 | 636 | +| 24 | 1 | 144 | 32 | 32 & 32 | 1408 | 1328 | 696 | 632 | + +5A.2.2.4.1.2 + +Uplink timeslot formats + +**Table 8G : Time slot formats for the Uplink** + +| Slot Format # | Spreading Factor | Midamble length (chips) | N TFCI code word (bits) | N SS & N TPC (bits) | Bits/slot | N Data/Slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) | +|---------------|------------------|-------------------------|------------------------------------|-------------------------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------| +| 0 | 16 | 144 | 0 | 0 & 0 | 88 | 88 | 44 | 44 | +| 1 | 16 | 144 | 4 | 0 & 0 | 88 | 86 | 42 | 44 | +| 2 | 16 | 144 | 8 | 0 & 0 | 88 | 84 | 42 | 42 | +| 3 | 16 | 144 | 16 | 0 & 0 | 88 | 80 | 40 | 40 | +| 4 | 16 | 144 | 32 | 0 & 0 | 88 | 72 | 36 | 36 | +| 5 | 16 | 144 | 0 | 2 & 2 | 88 | 84 | 44 | 40 | +| 6 | 16 | 144 | 4 | 2 & 2 | 88 | 82 | 42 | 40 | +| 7 | 16 | 144 | 8 | 2 & 2 | 88 | 80 | 42 | 38 | +| 8 | 16 | 144 | 16 | 2 & 2 | 88 | 76 | 40 | 36 | +| 9 | 16 | 144 | 32 | 2 & 2 | 88 | 68 | 36 | 32 | +| 10 | 8 | 144 | 0 | 0 & 0 | 176 | 176 | 88 | 88 | +| 11 | 8 | 144 | 4 | 0 & 0 | 176 | 174 | 86 | 88 | +| 12 | 8 | 144 | 8 | 0 & 0 | 176 | 172 | 86 | 86 | +| 13 | 8 | 144 | 16 | 0 & 0 | 176 | 168 | 84 | 84 | +| 14 | 8 | 144 | 32 | 0 & 0 | 176 | 160 | 80 | 80 | +| 15 | 8 | 144 | 0 | 2 & 2 | 176 | 172 | 88 | 84 | +| 16 | 8 | 144 | 4 | 2 & 2 | 176 | 170 | 86 | 84 | +| 17 | 8 | 144 | 8 | 2 & 2 | 176 | 168 | 86 | 82 | +| 18 | 8 | 144 | 16 | 2 & 2 | 176 | 164 | 84 | 80 | +| 19 | 8 | 144 | 32 | 2 & 2 | 176 | 156 | 80 | 76 | +| 20 | 8 | 144 | 0 | 4 & 4 | 176 | 168 | 88 | 80 | +| 21 | 8 | 144 | 4 | 4 & 4 | 176 | 166 | 86 | 80 | +| 22 | 8 | 144 | 8 | 4 & 4 | 176 | 164 | 86 | 78 | +| 23 | 8 | 144 | 16 | 4 & 4 | 176 | 160 | 84 | 76 | +| 24 | 8 | 144 | 32 | 4 & 4 | 176 | 152 | 80 | 72 | +| 25 | 4 | 144 | 0 | 0 & 0 | 352 | 352 | 176 | 176 | +| 26 | 4 | 144 | 4 | 0 & 0 | 352 | 350 | 174 | 176 | +| 27 | 4 | 144 | 8 | 0 & 0 | 352 | 348 | 174 | 174 | +| 28 | 4 | 144 | 16 | 0 & 0 | 352 | 344 | 172 | 172 | +| 29 | 4 | 144 | 32 | 0 & 0 | 352 | 336 | 168 | 168 | +| 30 | 4 | 144 | 0 | 2 & 2 | 352 | 348 | 176 | 172 | +| 31 | 4 | 144 | 4 | 2 & 2 | 352 | 346 | 174 | 172 | +| 32 | 4 | 144 | 8 | 2 & 2 | 352 | 344 | 174 | 170 | +| 33 | 4 | 144 | 16 | 2 & 2 | 352 | 340 | 172 | 168 | +| 34 | 4 | 144 | 32 | 2 & 2 | 352 | 332 | 168 | 164 | +| 35 | 4 | 144 | 0 | 8 & 8 | 352 | 336 | 176 | 160 | +| 36 | 4 | 144 | 4 | 8 & 8 | 352 | 334 | 174 | 160 | +| 37 | 4 | 144 | 8 | 8 & 8 | 352 | 332 | 174 | 158 | +| 38 | 4 | 144 | 16 | 8 & 8 | 352 | 328 | 172 | 156 | +| 39 | 4 | 144 | 32 | 8 & 8 | 352 | 320 | 168 | 152 | +| 40 | 2 | 144 | 0 | 0 & 0 | 704 | 704 | 352 | 352 | +| 41 | 2 | 144 | 4 | 0 & 0 | 704 | 702 | 350 | 352 | +| 42 | 2 | 144 | 8 | 0 & 0 | 704 | 700 | 350 | 350 | +| 43 | 2 | 144 | 16 | 0 & 0 | 704 | 696 | 348 | 348 | +| 44 | 2 | 144 | 32 | 0 & 0 | 704 | 688 | 344 | 344 | +| 45 | 2 | 144 | 0 | 2 & 2 | 704 | 700 | 352 | 348 | +| 46 | 2 | 144 | 4 | 2 & 2 | 704 | 698 | 350 | 348 | +| 47 | 2 | 144 | 8 | 2 & 2 | 704 | 696 | 350 | 346 | +| 48 | 2 | 144 | 16 | 2 & 2 | 704 | 692 | 348 | 344 | +| 49 | 2 | 144 | 32 | 2 & 2 | 704 | 684 | 344 | 340 | +| 50 | 2 | 144 | 0 | 16 & 16 | 704 | 672 | 352 | 320 | + +| Slot Format # | Spreading Factor | Midamble length (chips) | N TFCI code word (bits) | N SS & N TPC (bits) | Bits/slot | N Data/Slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) | +|---------------|------------------|-------------------------|------------------------------------|-------------------------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------| +| 51 | 2 | 144 | 4 | 16 & 16 | 704 | 670 | 350 | 320 | +| 52 | 2 | 144 | 8 | 16 & 16 | 704 | 668 | 350 | 318 | +| 53 | 2 | 144 | 16 | 16 & 16 | 704 | 664 | 348 | 316 | +| 54 | 2 | 144 | 32 | 16 & 16 | 704 | 656 | 344 | 312 | +| 55 | 1 | 144 | 0 | 0 & 0 | 1408 | 1408 | 704 | 704 | +| 56 | 1 | 144 | 4 | 0 & 0 | 1408 | 1406 | 702 | 704 | +| 57 | 1 | 144 | 8 | 0 & 0 | 1408 | 1404 | 702 | 702 | +| 58 | 1 | 144 | 16 | 0 & 0 | 1408 | 1400 | 700 | 700 | +| 59 | 1 | 144 | 32 | 0 & 0 | 1408 | 1392 | 696 | 696 | +| 60 | 1 | 144 | 0 | 2 & 2 | 1408 | 1404 | 704 | 700 | +| 61 | 1 | 144 | 4 | 2 & 2 | 1408 | 1402 | 702 | 700 | +| 62 | 1 | 144 | 8 | 2 & 2 | 1408 | 1400 | 702 | 698 | +| 63 | 1 | 144 | 16 | 2 & 2 | 1408 | 1396 | 700 | 696 | +| 64 | 1 | 144 | 32 | 2 & 2 | 1408 | 1388 | 696 | 692 | +| 65 | 1 | 144 | 0 | 32 & 32 | 1408 | 1344 | 704 | 640 | +| 66 | 1 | 144 | 4 | 32 & 32 | 1408 | 1342 | 702 | 640 | +| 67 | 1 | 144 | 8 | 32 & 32 | 1408 | 1340 | 702 | 638 | +| 68 | 1 | 144 | 16 | 32 & 32 | 1408 | 1336 | 700 | 636 | +| 69 | 1 | 144 | 32 | 32 & 32 | 1408 | 1328 | 696 | 632 | + +#### 5A.2.2.4.2 Time slot formats for 8PSK + +The Downlink and the Uplink timeslot formats are described together in the following table. + +**Table 8H: Timeslot formats for 8PSK modulation** + +| Slot Format # | Spreading Factor | Midamble length (chips) | N TFCI
code word (bits) | N SS & N TPC (bits) | Bits/slot | N Data/Slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) | +|---------------|------------------|-------------------------|---------------------------------------|-------------------------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------| +| 0 | 1 | 144 | 0 | 0 & 0 | 2112 | 2112 | 1056 | 1056 | +| 1 | 1 | 144 | 6 | 0 & 0 | 2112 | 2109 | 1053 | 1056 | +| 2 | 1 | 144 | 12 | 0 & 0 | 2112 | 2106 | 1053 | 1053 | +| 3 | 1 | 144 | 24 | 0 & 0 | 2112 | 2100 | 1050 | 1050 | +| 4 | 1 | 144 | 48 | 0 & 0 | 2112 | 2088 | 1044 | 1044 | +| 5 | 1 | 144 | 0 | 3 & 3 | 2112 | 2106 | 1056 | 1050 | +| 6 | 1 | 144 | 6 | 3 & 3 | 2112 | 2103 | 1053 | 1050 | +| 7 | 1 | 144 | 12 | 3 & 3 | 2112 | 2100 | 1053 | 1047 | +| 8 | 1 | 144 | 24 | 3 & 3 | 2112 | 2094 | 1050 | 1044 | +| 9 | 1 | 144 | 48 | 3 & 3 | 2112 | 2082 | 1044 | 1038 | +| 10 | 1 | 144 | 0 | 48 & 48 | 2112 | 2016 | 1056 | 960 | +| 11 | 1 | 144 | 6 | 48 & 48 | 2112 | 2013 | 1053 | 960 | +| 12 | 1 | 144 | 12 | 48 & 48 | 2112 | 2010 | 1053 | 957 | +| 13 | 1 | 144 | 24 | 48 & 48 | 2112 | 2004 | 1050 | 954 | +| 14 | 1 | 144 | 48 | 48 & 48 | 2112 | 1992 | 1044 | 948 | +| 15 | 16 | 144 | 0 | 0 & 0 | 132 | 132 | 66 | 66 | +| 16 | 16 | 144 | 6 | 0 & 0 | 132 | 129 | 63 | 66 | +| 17 | 16 | 144 | 12 | 0 & 0 | 132 | 126 | 63 | 63 | +| 18 | 16 | 144 | 24 | 0 & 0 | 132 | 120 | 60 | 60 | +| 19 | 16 | 144 | 48 | 0 & 0 | 132 | 108 | 54 | 54 | +| 20 | 16 | 144 | 0 | 3 & 3 | 132 | 126 | 66 | 60 | +| 21 | 16 | 144 | 6 | 3 & 3 | 132 | 123 | 63 | 60 | +| 22 | 16 | 144 | 12 | 3 & 3 | 132 | 120 | 63 | 57 | +| 23 | 16 | 144 | 24 | 3 & 3 | 132 | 114 | 60 | 54 | +| 24 | 16 | 144 | 48 | 3 & 3 | 132 | 102 | 54 | 48 | + +#### 5A.2.2.4.3 Time slot formats for MBSFN + +Downlink timeslot formats using QPSK or 16QAM modulation is dedicated for MBSFN operation and is described in the following table. + +Table 8Ha : Time slot formats for MBSFN + +| Slot Format # | Spreading Factor | Midamble /preamble length (chips) | N TFCI code word (bits) | N SS & N TPC (bits) | Bits/slot | N Data/Slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) | +|-------------------------|------------------|-----------------------------------|------------------------------------|-------------------------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------| +| 0(QPSK) * | 1 | 144 | 16 | 0 & 0 | 1408 | 1404 | 702 | 702 | +| 1(QPSK) * | 16 | 144 | 16 | 0 & 0 | 88 | 84 | 42 | 42 | +| 2(16QAM) * | 1 | 144 | 32 | 0 & 0 | 2816 | 2808 | 1404 | 1404 | +| 3(16QAM) * | 16 | 144 | 32 | 0 & 0 | 176 | 168 | 84 | 84 | +| 4(QPSK) ** | 1 | 96 | 16 | 0 & 0 | 1536 | 1532 | N/A | N/A | +| 5(QPSK) ** | 2 | 96 | 16 | 0 & 0 | 768 | 764 | N/A | N/A | +| 6(QPSK) ** | 16 | 96 | 16 | 0 & 0 | 96 | 92 | N/A | N/A | +| 7(16QAM) ** | 1 | 96 | 32 | 0 & 0 | 3072 | 3064 | N/A | N/A | +| 8(16QAM) ** | 2 | 96 | 16 | 0 & 0 | 1536 | 1528 | N/A | N/A | +| 9(16QAM) ** | 16 | 96 | 32 | 0 & 0 | 192 | 184 | N/A | N/A | +| 10(QPSK) *** | 16 | 96 | 16 | 0 & 0 | 32 | 24 | N/A | N/A | +| 11(QPSK) *** | 16 | 96 | 0 | 0 & 0 | 32 | 32 | N/A | N/A | + +NOTE: \* denotes that these timeslot formats are used in the traffic burst for mixed carrier MBSFN. \*\* denotes that these timeslot formats are used in the MT burst for dedicated carrier MBSFN. \*\*\* denotes that these timeslot formats are used in the MS burst for dedicated carrier MBSFN. The burst in the dedicated carrier MBSFN has only one data field. + +### 5A.2.3 Training sequences for spread bursts + +In this subclause, the training sequences for usage as midambles are defined. The training sequences, i.e. midambles, of different users active in the same cell and same time slot are cyclically shifted versions of one single basic midamble code. In the case of MBSFN timeslots there is only a single midamble and this is derived from a single basic midamble code which is not necessarily cell-specific. The applicable basic midamble codes are given in Annex AA.1. + +The basic midamble codes in Annex AA.1 are listed in hexadecimal notation. The binary form of the basic midamble code shall be derived according to table 8I below. + +**Table 81: Mapping of 4 binary elements $m_i$ on a single hexadecimal digit:** + +| 4 binary elements $m_i$ | Mapped on hexadecimal digit | +|-------------------------|-----------------------------| +| -1 -1 -1 -1 | 0 | +| -1 -1 -1 1 | 1 | +| -1 -1 1 -1 | 2 | +| -1 -1 1 1 | 3 | +| -1 1 -1 -1 | 4 | +| -1 1 -1 1 | 5 | +| -1 1 1 -1 | 6 | +| -1 1 1 1 | 7 | +| 1 -1 -1 -1 | 8 | +| 1 -1 -1 1 | 9 | +| 1 -1 1 -1 | A | +| 1 -1 1 1 | B | +| 1 1 -1 -1 | C | +| 1 1 -1 1 | D | +| 1 1 1 -1 | E | +| 1 1 1 1 | F | + +For each particular basic midamble code, its binary representation can be written as a vector $\mathbf{m}_P$ : + +$$\mathbf{m}_P = (m_1, m_2, \dots, m_P) \quad (1)$$ + +According to Annex AA.1, the size of this vector $\mathbf{m}_P$ is $P=128$ . As QPSK modulation is used, the training sequences are transformed into a complex form, denoted as the complex vector $\underline{\mathbf{m}}_P$ : + +$$\underline{\mathbf{m}}_P = (\underline{m}_1, \underline{m}_2, \dots, \underline{m}_P) \quad (2)$$ + +The elements $\underline{m}_i$ of $\underline{\mathbf{m}}_P$ are derived from elements $m_i$ of $\mathbf{m}_P$ using equation (3): + +$$\underline{m}_i = (j)^i \cdot m_i \text{ for all } i = 1, \dots, P \quad (3)$$ + +Hence, the elements $\underline{m}_i$ of the complex basic midamble code are alternating real and imaginary. + +To derive the required training sequences, this vector $\underline{\mathbf{m}}_P$ is periodically extended to the size: + +$$i_{\max} = L_m + (K - 1)W \quad (4)$$ + +Notes on equation (4): + +K and W are taken from Annex AA.1 + +So we obtain a new vector $\underline{\mathbf{m}}$ containing the periodic basic midamble sequence: + +$$\underline{\mathbf{m}} = (\underline{m}_1, \underline{m}_2, \dots, \underline{m}_{i_{\max}}) = (\underline{m}_1, \underline{m}_2, \dots, \underline{m}_{L_m + (K-1)W}) \quad (5)$$ + +The first $P$ elements of this vector $\underline{\mathbf{m}}$ are the same ones as in vector $\underline{\mathbf{m}}_P$ , the following elements repeat the beginning: + +$$\underline{m}_i = \underline{m}_{i-P} \text{ for the subset } i = (P+1), \dots, i_{\max} \quad (6)$$ + +Using this periodic basic midamble sequence $\underline{\mathbf{m}}$ for each user $k$ a midamble $\underline{\mathbf{m}}^{(k)}$ of length $L_m$ is derived, which can be written as a user specific vector: + +$$\underline{m}^{(k)} = (\underline{m}_1^{(k)}, \underline{m}_2^{(k)}, \dots, \underline{m}_{L_m}^{(k)}) \quad (7)$$ + +The $L_m$ midamble elements $\underline{m}_i^{(k)}$ are generated for each midamble of the $k$ users ( $k = 1, \dots, K$ ) based on: + +$$\underline{m}_i^{(k)} = \underline{m}_{i+(K-k)W} \text{ with } i = 1, \dots, L_m \text{ and } k = 1, \dots, K \quad (8)$$ + +The midamble sequences derived according to equations (7) to (8) have complex values and are not subject to channelisation or scrambling process, i.e. the elements $\underline{m}_i^{(k)}$ represent complex chips for usage in the pulse shaping process at modulation. + +The term 'a midamble code set' or 'a midamble code family' denotes $K$ specific midamble codes $\underline{m}^{(k)}$ ; $k=1, \dots, K$ , based on a single basic midamble code $\underline{m}_P$ according to (1). + +### 5A.2.3a Training sequences for dedicated carrier MBSFN + +When the entire carrier is dedicated to MBSFN, preamble is used for the training sequences in each timeslot. In this case, for all timeslots employing MBSFN operation, only a single preamble is needed, i.e. $K_{\text{Cell}}=1$ , then all physical channels in such timeslots employ the same preamble with the same allocation strategies. + +For dedicated carrier MBSFN, the preamble has a fixed length of $L_p=96$ , and the generation of preamble is the same as in the 1.28 Mcps TDD cf. [5A.2.3 Training sequences for spread bursts], which is corresponding to: + +$$W = \left\lfloor \frac{P}{K} \right\rfloor, \quad K=1, P=64$$ + +Note: that $\lfloor x \rfloor$ denotes the largest integer number less or equal to $x$ . + +The preamble is generated from one of the basic preamble codes shown in table AA.1a. + +The mapping of these Basic Preamble Codes to MBSFN Cell Parameters is shown in [8]. + +### 5A.2.4 Beamforming + +Beamforming is same as that of the 3.84Mcps TDD, cf. [5.2.4 Beamforming ]. + +Beamforming is not applicable to DL time slots with MBSFN transmission. + +## 5A.3 Common physical channels + +### 5A.3.1 Primary common control physical channel (P-CCPCH) + +The BCH as described in section 4.1.2 'Common Transport Channels' is mapped onto the Primary Common Control Physical Channels (P-CCPCH1 and P-CCPCH2). The position (time slot / code) of the P-CCPCHs is fixed in the 1.28Mcps TDD. The P-CCPCHs are mapped onto the first two code channels of timeslot#0 with spreading factor of 16. When the entire carrier is dedicated to MBSFN, the P-CCPCH is mapped onto the first two code channels of MS timeslot with spreading factor of 16. The P-CCPCH is always transmitted with an antenna pattern configuration that provides whole cell coverage. + +In a multi-frequency cell the carrier which transmits P-CCPCH is called the primary frequency and the others are called secondary frequencies. A multi-frequency cell has only one primary frequency. + +#### 5A.3.1.1 P-CCPCH Spreading + +The P-CCPCH uses fixed spreading with a spreading factor $SF = 16$ . The P-CCPCH1 and P-CCPCH2 always use channelisation code $c_{Q=6}^{(k=1)}$ and $c_{Q=6}^{(k=2)}$ respectively. + +### 5A.3.1.2 P-CCPCH Burst Format + +The burst format as described in section 5A.2.2 is used for the P-CCPCH. No TFCI is applied for the P-CCPCH. + +### 5A.3.1.3 P-CCPCH Training sequences + +The training sequences, i.e. midambles, as described in subclause 5A.2.3 are used for the P-CCPCH. When the entire carrier is dedicated to MBSFN, the training sequences, i.e. preambles, as described in subclause 5A.2.3.a are used for the P-CCPCH. + +## 5A.3.2 Secondary common control physical channel (S-CCPCH) + +PCH and FACH as described in subclause 4.1.2 are mapped onto one or more secondary common control physical channels (S-CCPCH). In this way the capacity of PCH and FACH can be adapted to the different requirements. The time slot and codes used for the S-CCPCH are broadcast on the BCH. + +In a multi-frequency cell S-CCPCH shall be transmitted only on the primary frequency. + +### 5A.3.2.1 S-CCPCH Spreading + +Except for physical channels in MBSFN time slot, the S-CCPCH uses fixed spreading with a spreading factor $SF = 16$ , as described in subclause 5A.2.1. And the S-CCPCH in MBSFN time slot may use spreading with spreading factor $SF = 1, 2$ or $16$ . + +Note: $SF=2$ is only used on dedicated MBSFN frequency. + +### 5A.3.2.2 S-CCPCH Burst Format + +The burst format as described in section 5A.2.2 is used for the S-CCPCH. TFCI may be applied for S-CCPCHs. + +### 5A.3.2.3 S-CCPCH Training sequences + +The training sequences, i.e. midambles, as described in the subclause 5A.2.3 are also used for the S-CCPCH. + +## 5A.3.3 Fast Physical Access CHannel (FPACH) + +The Fast Physical Access CHannel (FPACH) is used by the Node B to carry, in a single burst, the acknowledgement of a detected signature with timing and power level adjustment indication to an user equipment. FPACH makes use of one code with spreading factor 16, so that its burst is composed by 44 symbols. The spreading code, training sequence and time slot position are configured by the network and signalled on the BCH. + +In a multi-frequency cell the FPACH is transmitted on the primary frequency. The FPACH may also be also transmitted on the secondary frequency in case of handover or E-DCH procedure. + +### 5A.3.3.1 FPACH burst + +The FPACH burst contains 32 information bits. Table 8J reports the content description of the FPACH information bits and their priority order: + +Table 8J: FPACH information bits description + +| Information field | Length (in bits) | +|----------------------------------------------------------------------------|------------------| +| Signature Reference Number | 3 (MSB) | +| Relative Sub-Frame Number | 2 | +| Received starting position of the UpPCH ( $UpPCH_{Pos}$ ) | 11 | +| Transmit Power Level Command for RACH message | 7 | +| Extended part of Received starting position of the UpPCH ( $UpPCH_{Pos}$ ) | 2 | +| Reserved bits (default value: 0) | 7 (LSB) | + +The use and generation of the information fields is explained in [9]. + +#### 5A.3.3.1.1 Signature Reference Number + +The reported number corresponds to the numbering principle for the cell signatures as described in [8]. + +The Signature Reference Number value range is 0 – 7 coded in 3 bits such that: + +bit sequence(0 0 0) corresponds to the first signature of the cell; ...; bit sequence (1 1 1) corresponds to the 8th signature of the cell. + +#### 5A.3.3.1.2 Relative Sub-Frame Number + +The Relative Sub-Frame Number value range is 0 – 3 coded such that: + +bit sequence (0 0) indicates one sub-frame difference; ...; bit sequence (1 1) indicates 4 sub-frame difference. + +#### 5A.3.3.1.3 Received starting position of the UpPCH (UpPCHPOS) + +The size of UpPCHPOS is extended to be 13bits and the received starting position of the UpPCH value range is 0 – 8191 coded such that: + +The 11 least significant bits (LSB) of UpPCHPOS are transmitted in the Received starting position of the UpPCH information field and the 2 most significant bits (MSB) of UpPCHPOS are transmitted in the first 2bits of the Reserve bits information field. Bit sequence (0 0 ... 0 0 0) indicates the received starting position zero chip; ...; bit sequence (1 1 ... 1 1 1) indicates the received starting position 8191\*1/8 chip. + +#### 5A.3.3.1.4 Transmit Power Level Command for the RACH message + +The transmit power level command is transmitted in 7 bits. + +#### 5A.3.3.2 FPACH Spreading + +The FPACH uses only spreading factor SF=16 as described in subclause 5A.3.3. The set of admissible spreading codes for use on the FPACH is broadcast on the BCH. + +#### 5A.3.3.3 FPACH Burst Format + +The burst format as described in section 5A.2.2 is used for the FPACH. + +#### 5A.3.3.4 FPACH Training sequences + +The training sequences, i.e. midambles, as described in subclause 5A.2.3 are used for FPACH. + +#### 5A.3.3.5 FPACH timeslot formats + +The FPACH uses slot format #0 of the DL time slot formats given in subclause 5A.2.2.4.1.1. + +### 5A.3.4 The physical random access channel (PRACH) + +The RACH as described in subclause 4.1.2 is mapped onto one or more uplink physical random access channels (PRACH). In such a way the capacity of RACH can be flexibly scaled depending on the operators need. + +In a multi-frequency cell the PRACH shall be transmitted only on the primary frequency. + +#### 5A.3.4.1 PRACH Spreading + +The uplink PRACH uses either spreading factor SF=16, SF=8 or SF=4 as described in subclause 5A.2.1. The set of admissible spreading codes for use on the PRACH and the associated spreading factors are broadcast on the BCH (within the RACH configuration parameters on the BCH). + +#### 5A.3.4.2 PRACH Burst Format + +The burst format as described in section 5A.2.2 is used for the PRACH. + +### 5A.3.4.3 PRACH Training sequences + +The training sequences, i.e. midambles, of different users active in the same time slot are time shifted versions of a single periodic basic code. The basic midamble codes as described in subclause 5A.2.3 are used for PRACH. + +### 5A.3.4.4 PRACH timeslot formats + +The PRACH uses the following time slot formats taken from the uplink timeslot formats described in sub-clause 5A.2.2.4.1.2: + +| Spreading Factor | Slot Format # | +|------------------|---------------| +| 16 | 0 | +| 8 | 10 | +| 4 | 25 | + +### 5A.3.4.5 Association between Training Sequences and Channelisation Codes + +The association between training sequences and channelisation codes of PRACH in the 1.28McpsTDD is same as that of the DPCH. + +## 5A.3.5 The synchronisation channels (DwPCH, UpPCH) + +There are two dedicated physical synchronisation channels —DwPCH and UpPCH in each 5ms sub-frame of the 1.28Mcps TDD. The DwPCH is used for the down link synchronisation and the UpPCH is used for the uplink synchronisation. + +The position and the contents of the DwPCH are equal to the DwPTS as described in the subclause 5A.1., while the position and the contents of the UpPCH are equal to the UpPTS or other uplink access position indicated by the higher layers. + +The DwPCH is transmitted at each sub-frame with an antenna pattern configuration which provides whole cell coverage. Furthermore it is transmitted with a constant power level which is signalled by higher layers. + +In a multi-frequency cell the DwPCH shall be transmitted only on the primary frequency. The UpPCH is transmitted on the primary frequency. The UpPCH may also be transmitted on the secondary frequencies in case of handover and the E-RUCCH procedure. + +The burst structure of the DwPCH (DwPTS) is described in the figure 18I. + +![Figure 18I: burst structure of the DwPCH ( DwPTS). The diagram shows a horizontal bar representing a 75us time interval. Below this bar, a table shows two segments: GP(32chips) and SYNC_DL(64chips).](973221d410a5fc97ca8868e730bc796a_img.jpg) + +| | | +|-------------|------------------| +| 75us | | +| GP(32chips) | SYNC_DL(64chips) | + +Figure 18I: burst structure of the DwPCH ( DwPTS). The diagram shows a horizontal bar representing a 75us time interval. Below this bar, a table shows two segments: GP(32chips) and SYNC\_DL(64chips). + +**Figure 18I: burst structure of the DwPCH ( DwPTS)** + +Note: 'GP' for 'Guard Period' + +The burst structure of the UpPCH (UpPTS) is described in the figure 18J. + +![Figure 18J: burst structure of the UpPCH ( UpPTS). The diagram shows a horizontal bar representing a 125us time interval. Below this bar, a table shows two segments: SYNC_UL(128chips) and GP(32chips).](efe7822cf973305b4681375549f04650_img.jpg) + +| | | +|-------------------|-------------| +| 125us | | +| SYNC_UL(128chips) | GP(32chips) | + +Figure 18J: burst structure of the UpPCH ( UpPTS). The diagram shows a horizontal bar representing a 125us time interval. Below this bar, a table shows two segments: SYNC\_UL(128chips) and GP(32chips). + +**Figure 18J: burst structure of the UpPCH ( UpPTS)** + +The SYNC-DL code in DwPCH and the SYNC-UL code in UpPCH are not spreaded. The details about the SYNC-DL and SYNC-UL code are described in the corresponding subclause and annex in [8]. + +### 5A.3.6 Physical Uplink Shared Channel (PUSCH) + +For Physical Uplink Shared Channel (PUSCH) the burst structure of DPCH as described in subclause 5A.2 and the training sequences as described in subclause 5A.2.3 shall be used. PUSCH provides the possibility for transmission of TFCI, SS, and TPC in uplink. + +The PUSCH is common with 3.84 Mcps TDD with respect to Spreading and UE selection, cf. [5.3.5 Physical Uplink Shared Channel (PUSCH)]. + +### 5A.3.7 Physical Downlink Shared Channel (PDSCH) + +For Physical Downlink Shared Channel (PDSCH) the burst structure of DPCH as described in subclause 5A.2 and the training sequences as described in subclause 5A.2.3 shall be used. PDSCH provides the possibility for transmission of TFCI, SS, and TPC in downlink. + +The PDSCH is common with 3.84 Mcps TDD with respect to Spreading and UE selection, cf. [5.3.6 Physical Downlink Shared Channel (PDSCH)]. + +### 5A.3.8 The Page Indicator Channel (PICH) + +The Paging Indicator Channel (PICH) is a physical channel used to carry the paging indicators. + +The PICH may be associated with + +- an S-CCPCH to which a PCH transport channel is mapped, or +- an HS-SCCH associated with the HS-PDSCH(s) to which an HS-DSCH transport channel is mapped, or +- an HS-PDSCH to which an HS-DSCH transport channel carrying paging message is mapped. + +In a multi-frequency cell the PICH shall be transmitted only on the primary frequency. + +#### 5A.3.8.1 Mapping of Paging Indicators to the PICH bits + +Figure 18K depicts the structure of a PICH transmission and the numbering of the bits within the bursts. The burst type as described in [5A.2.2 'Burst Format'] is used for the PICH. $N_{PIB}$ bits are used to carry the paging indicators, where $N_{PIB}=352$ . + +![Figure 18K: Transmission and numbering of paging indicator carrying bits in the PICH bursts. The diagram shows two subframes, subframe #1 and subframe #2, each containing two bursts. Each burst is divided into three parts: 'Bits for Page Indication' (bits 0 to 175), 'Midamble' (bits 176 to 263), and 'Guard Period' (bits 264 to 351). The total number of bits per burst is 352. The subframes are labeled 'Time Slot#i, subframe #1' and 'Time Slot#i, subframe #2'. The index i is given as {0, 2, 3, 4, 5, 6}.](3df9ebba5e1b927ad2dac12bc023c1c5_img.jpg) + +Figure 18K: Transmission and numbering of paging indicator carrying bits in the PICH bursts. The diagram shows two subframes, subframe #1 and subframe #2, each containing two bursts. Each burst is divided into three parts: 'Bits for Page Indication' (bits 0 to 175), 'Midamble' (bits 176 to 263), and 'Guard Period' (bits 264 to 351). The total number of bits per burst is 352. The subframes are labeled 'Time Slot#i, subframe #1' and 'Time Slot#i, subframe #2'. The index i is given as {0, 2, 3, 4, 5, 6}. + +**Figure 18K: Transmission and numbering of paging indicator carrying bits in the PICH bursts** + +Each paging indicator $P_q$ (where $P_q, q = 0, \dots, N_{PI}-1, P_q \in \{0, 1\}$ ) in one radio frame is mapped to the bits $\{S_{2L_{PI} \cdot q+1}, \dots, S_{2L_{PI} \cdot (q+1)}}\}$ in subframe #1 or subframe #2. + +The setting of the paging indicators and the corresponding PICH bits is described in [7]. + +$N_{PI}$ paging indicators of length $L_{PI}=2, L_{PI}=4$ or $L_{PI}=8$ symbols are transmitted in each radio frame that contains the PICH. The number of paging indicators $N_{PI}$ per radio frame is given by the paging indicator length, which is signalled by higher layers. In table 8K this number is shown for the different possibilities of paging indicator lengths. + +**Table 8K: Number $N_{PI}$ of paging indicators per radio frame for different paging indicator lengths $L_{PI}$** + +| | $L_{PI}=2$ | $L_{PI}=4$ | $L_{PI}=8$ | +|--------------------------|------------|------------|------------| +| $N_{PI}$ per radio frame | 88 | 44 | 22 | + +### 5A.3.8.2 Structure of the PICH over multiple radio frames + +The structure of the PICH over multiple radio frames is common with 3.84 Mcps TDD, cf. [5.3.7.2 Structure of the PICH over multiple radio frames] + +### 5A.3.9 High Speed Physical Downlink Shared Channel (HS-PDSCH) + +The HS-DSCH as described in subclause 4.1.2 is mapped onto one or more high speed physical downlink shared channels (HS-PDSCH). In a multi-frequency HS-DSCH cell, HS-PDSCHs may be transmitted on one or more carriers in CELL\_DCH state and on only one carrier in CELL\_FACH, CELL\_PCH and URA\_PCH state in a TTI to a UE and the carriers allocated to the UE shall be on contiguous frequencies. In CELL\_FACH state, the HS-PDSCHs shall be transmitted on a same carrier as the one on which the uplink transmission resources are allocated to the UE. This carrier can be the primary frequency or the secondary frequency. In CELL\_PCH and URA\_PCH state, HS-PDSCHs can only be transmitted on the primary frequency. For UE not supporting multi-carrier HS-DSCH reception, the HS-PDSCHs shall be allocated on a same carrier as the one on which the associated DPCH or the uplink transmission resources is allocated. + +#### 5A.3.9.1 HS-PDSCH Spreading + +For the UEs not configured in MIMO mode, the HS-PDSCH shall use either spreading factor SF = 16 or SF=1, as described in 5.2.1.1. + +For the UEs configured in MIMO mode, if SF=16 is configured by higher layers [19] to be not supported for dual stream transmission, the HS-PDSCH shall use spreading factor SF=1 only. Otherwise, the HS-PDSCH shall use either spreading factor SF = 16 or SF=1. + +Spreading of the HS-PDSCH is common with 3.84 Mcps TDD, cf. [5.3.9.1 HS-PDSCH Spreading] + +#### 5A.3.9.2 HS-PDSCH Burst Format + +The burst format as described in section 5A.2.2 shall be used for the HS-PDSCH. + +#### 5A.3.9.3 HS-PDSCH Training Sequences + +The training sequences as described in subclause 5A.2.3 are used for the HS-PDSCH. + +#### 5A.3.9.4 UE Selection + +UE selection is common with 3.84 Mcps TDD, cf. [5.3.9.4 UE selection]. + +#### 5A.3.9.5 HS-PDSCH timeslot formats + +An HS-PDSCH may use QPSK, 16QAM or 64QAM modulation symbols. The time slot formats are shown in table 8KA. + +**Table 8KA: Time slot formats for the HS-PDSCH** + +| Slot Format # | SF | Midamble length (chips) | N TFCI code word (bits) | N SS & N TPC (bits) | Bits/slot | N Data/Slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) | +|---------------|----|-------------------------|------------------------------------|-------------------------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------| +| 0 (QPSK) | 16 | 144 | 0 | 0 & 0 | 88 | 88 | 44 | 44 | +| 1 (16QAM) | 16 | 144 | 0 | 0 & 0 | 176 | 176 | 88 | 88 | +| 2 (QPSK) | 1 | 144 | 0 | 0 & 0 | 1408 | 1408 | 704 | 704 | +| 3 (16QAM) | 1 | 144 | 0 | 0 & 0 | 2816 | 2816 | 1408 | 1408 | +| 4 (64QAM) | 16 | 144 | 0 | 0 & 0 | 264 | 264 | 132 | 132 | +| 5 (64QAM) | 1 | 144 | 0 | 0 & 0 | 4224 | 4224 | 2112 | 2112 | +| 6 (QPSK) | 16 | 144 | 0 | 2 & 2 | 88 | 84 | 44 | 40 | +| 7 (16QAM) | 16 | 144 | 0 | 2 & 2 | 172 | 168 | 88 | 80 | +| 8 (QPSK) | 1 | 144 | 0 | 2 & 2 | 1408 | 1404 | 704 | 700 | +| 9 (16QAM) | 1 | 144 | 0 | 2 & 2 | 2812 | 2808 | 1408 | 1400 | + +Note: Time slot format 6-9 are exclusively used for semi-persistent HS-PDSCH resources. Whether data field is QPSK or 16QAM modulated, QPSK modulation is used for SS and TPC symbols. + +### 5A.3.9.6 Transmission of SS and TPC + +For the transmissions on the semi-persistent HS-PDSCH resources without an HS-SCCH, the SS and TPC command for HS-SICH can be conveyed in HS-PDSCH. The transmission of SS and TPC is done in the data parts of the traffic burst. Hence the midamble structure and length is not changed. The TPC information is to be transmitted directly after the SS information, which is transmitted after the midamble. The SS and TPC are transmitted using the physical channel with the lowest physical channel number and the timeslot with the lowest timeslot number. + +### 5A.3.10 Shared Control Channel for HS-DSCH (HS-SCCH) + +The HS-SCCH is a DL physical channel that carries higher layer control information for HS-DSCH. The physical layer will process this information according to [7] and will transmit the resulting bits on the HS-SCCH the structure of which is described below. A number of HS-SCCH types are defined for different purpose, and the actual description is given in [7]. + +The information on the HS-SCCH is carried by two separate physical channels (HS-SCCH1 and HS-SCCH2). The term HS-SCCH refers to the ensemble of these physical channels. + +In CELL\_FACH or CELL\_PCH state, HS-SCCH order may carry an uplink synchronization establishment command. The structure is the same as described above. + +In case of multi-carrier HS-DSCH reception, the HS-DSCH transmission on each allocated carrier is associated with its respective HS-SCCHs. The HS-SCCHs and HS-SICHs controlling the same HS-DSCH transmission on a carrier for the same UE shall be allocated on a same carrier. + +#### 5A.3.10.1 HS-SCCH Spreading + +Spreading of the HS-SCCH is common with 3.84 Mcps TDD, cf. [5.3.10.1 HS-SCCH Spreading]. + +#### 5A.3.10.2 HS-SCCH Burst Format + +The burst format as described in section 5A.2.2 shall be used for the HS-SCCH. + +#### 5A.3.10.3 HS-SCCH Training Sequences + +The training sequences as described in subclause 5A.2.3 are used for the HS-SCCH. + +#### 5A.3.10.4 HS-SCCH timeslot formats + +HS-SCCH1 shall use time slot format #5 and HS-SCCH2 shall use time slot format #0 from table 8F, see section 5A.2.2.4.1.1, i.e. HS-SCCH shall carry TPC and SS but no TFCI. + +## 5A.3.11 Shared Information Channel for HS-DSCH (HS-SICH) + +The HS-SICH is a UL physical channel that carries higher layer control information and the Channel Quality Indicator CQI for HS-DSCH. If there is associated HS-SICH to an HS-SCCH order, the HS-SICH carries the acknowledgement to the HS-SCCH order command. The HS-SICH may also used as the acknowledgement for an HS-SCCH allocating semi-persistent HS-PDSCH resources. The physical layer will process this information according to [7] and will transmit the resulting bits on the HS-SICH the structure of which is described below. + +In case of multi-carrier HS-DSCH reception, the HS-DSCH transmission on each allocated carrier is related to its respective HS-SICHs. The HS-SCCHs and HS-SICHs controlling the same HS-DSCH transmission on a carrier for the same UE shall be allocated on a same carrier. + +### 5A.3.11.1 HS-SICH Spreading + +The HS-SICH shall use spreading factor $SF = 16$ , as described in 5.2.1.2. + +When MIMO dual-stream is transmitted, the HS-SICH shall use spreading factor $SF=8$ which shall utilize an additional $SF=16$ channelisation code along the branch with the higher code numbering of the allowed OVSF sub tree. + +### 5A.3.11.2 HS-SICH Burst Format + +The burst format as described in section 5A.2.2 shall be used for the HS-SICH. + +### 5A.3.11.3 HS-SICH Training Sequences + +The training sequences as described in subclause 5A.2.3 are used for the HS-SICH. + +### 5A.3.11.4 HS-SICH timeslot formats + +The HS-SICH Type 1 shall use time slot format #5 while HS-SICH Type 2 shall use time slot format #20 from table 8G, see section 5A.2.2.4.1.2, i.e., it shall carry TPC and SS but no TFCI. For HS-SICH type 2, two identical TPC symbols denoting one TPC command are transmitted directly after the two identical SS symbols denoting one SS command, which are transmitted after the midamble. + +## 5A.3.12 The MBMS Indicator Channel (MICH) type1 + +The MBMS Indicator Channel (MICH) type1 is a physical channel used to carry the MBMS notification indicators on a non MBSFN dedicated carrier. The UE may use multiple MICH within the MBMS modification period in order to make decisions on individual MBMS notification indicators. + +### 5A.3.12.1 Mapping of MBMS Indicators to the type1 MICH bits + +Figure 18L depicts the structure of a type1 MICH transmission and the numbering of the bits within the bursts. The burst type as described in [5A.2.2 'Burst Format'] is used for the MICH. $N_{NIB}$ bits are used to carry the MBMS notification indicators, where $N_{NIB}=352$ . + +![Figure 18L: Transmission and numbering of MBMS notification indicator carrying bits in a type1 MICH burst. The diagram shows two subframes, subframe #1 and subframe #2, each containing two bursts. Each burst has a 'Bits for MBMS Notification' section, a 'Midamble' section, and a 'Guard Period' section. The bits are numbered s1, s2, ..., s174 in subframe #1 and s177, s178, ..., s352 in subframe #2. The midamble is shown as a shaded block, and the guard period as a white block at the end of each burst. The time slot numbering is shown below the bursts, with subframe #1 starting at s2 and subframe #2 starting at s179.](165508b2526a29efbae96fa16d525d28_img.jpg) + +Figure 18L: Transmission and numbering of MBMS notification indicator carrying bits in a type1 MICH burst. The diagram shows two subframes, subframe #1 and subframe #2, each containing two bursts. Each burst has a 'Bits for MBMS Notification' section, a 'Midamble' section, and a 'Guard Period' section. The bits are numbered s1, s2, ..., s174 in subframe #1 and s177, s178, ..., s352 in subframe #2. The midamble is shown as a shaded block, and the guard period as a white block at the end of each burst. The time slot numbering is shown below the bursts, with subframe #1 starting at s2 and subframe #2 starting at s179. + +**Figure 18L: Transmission and numbering of MBMS notification indicator carrying bits in a type1 MICH burst** + +Each notification indicator $N_q$ (where $N_q, q = 0, \dots, N_n-1, N_q \in \{0, 1\}$ ) in one radio frame is mapped to the bits $\{s_{2LN_i*q+1}, \dots, s_{2LN_i*(q+1)}}\}$ in subframe #1 or subframe #2. + +The setting of the MBMS notification indicators and the corresponding type1 MICH bits is described in [7]. + +$N_n$ MBMS notification indicators of length $L_{NI}=2$ , $L_{NI}=4$ or $L_{NI}=8$ symbols are transmitted in each radio frame that contains the MICH. The number of MBMS notification indicators $N_{NI}$ per radio frame is given by the MBMS notification indicator length, which is signalled by higher layers. In table 8KB this number is shown for the different possibilities of MBMS notification indicator lengths. + +**Table 8KB: Number $N_{NI}$ of MBMS notification indicators per radio frame on type1 MICH for different MBMS notification indicator lengths $L_{NI}$** + +| | $L_{NI}=2$ | $L_{NI}=4$ | $L_{NI}=8$ | +|-----------------------|------------|------------|------------| +| $N_n$ per radio frame | 88 | 44 | 22 | + +The value NI ( $NI = 0, \dots, N_{NI}-1$ ) calculated by higher layers, is associated to the MBMS notification indicator $N_q$ , where $q = NI \bmod N_n$ . + +The set of NI passed over the Iub indicates all higher layer NI values for which the notification indicator on MICH type1 should be set to 1 during the corresponding modification period; all other indicators shall be set to 0. + +### 5A.3.12a The MBMS Indicator Channel (MICH) type 2 + +The MBMS Indicator Channel (MICH) type 2 is a physical channel used to carry the MBMS notification indicators and system information change indicator on a MBMSFN dedicated carrier only. The UE may use multiple MICH within the MBMS modification period in order to make decisions on individual MBMS notification indicators. + +#### 5A.3.12.1 Mapping of MBMS Indicators to the type 2 MICH bits + +Figure 18La depicts the structure of a type 2 MICH transmission and the numbering of the bits within the bursts. The burst type as described in [5A.2.2a 'MS Burst Format'] is used for the type 2 MICH. $2 \cdot L_{NI}$ bits are used to carry the system information change indicators and $N_{NIB} - 2 \cdot L_{NI}$ bits are used to carry the MBMS notification indicators, where $N_{NIB}=128$ for 10ms long MICH type 2. + +![Diagram showing the transmission and numbering of MBMS notification indicator carrying bits in a type 2 MICH burst across two subframes. Subframe #1 and Subframe #2 each contain a CP (Cyclic Prefix) and a Preamble. The bits are divided into 'Bits for SI change notification' and 'Bits for MBMS Notification'. In subframe #1, the SI change notification bits are labeled s1_1, s1_2, ..., s1_LNI, s1_1, s1_2, s1_3, s1_4, s1_5, s1_6. The MBMS notification bits are labeled s2_1, s2_2, ..., s2_LNI, s2_1, s2_2, s2_3, s2_4, s2_5, s2_6. In subframe #2, the SI change notification bits are labeled s1_1, s1_2, ..., s1_LNI, s1_1, s1_2, s1_3, s1_4, s1_5, s1_6. The MBMS notification bits are labeled s2_1, s2_2, ..., s2_LNI, s2_1, s2_2, s2_3, s2_4, s2_5, s2_6.](99781d878388c3e0f359b1d6ce14119c_img.jpg) + +Diagram showing the transmission and numbering of MBMS notification indicator carrying bits in a type 2 MICH burst across two subframes. Subframe #1 and Subframe #2 each contain a CP (Cyclic Prefix) and a Preamble. The bits are divided into 'Bits for SI change notification' and 'Bits for MBMS Notification'. In subframe #1, the SI change notification bits are labeled s1\_1, s1\_2, ..., s1\_LNI, s1\_1, s1\_2, s1\_3, s1\_4, s1\_5, s1\_6. The MBMS notification bits are labeled s2\_1, s2\_2, ..., s2\_LNI, s2\_1, s2\_2, s2\_3, s2\_4, s2\_5, s2\_6. In subframe #2, the SI change notification bits are labeled s1\_1, s1\_2, ..., s1\_LNI, s1\_1, s1\_2, s1\_3, s1\_4, s1\_5, s1\_6. The MBMS notification bits are labeled s2\_1, s2\_2, ..., s2\_LNI, s2\_1, s2\_2, s2\_3, s2\_4, s2\_5, s2\_6. + +**Figure 18La: Transmission and numbering of MBMS notification indicator carrying bits in a type 2 MICH burst** + +Each notification indicator $N_q$ (where $N_q, q = 0, \dots, N_n-1, N_q \in \{0, 1\}$ ) in one radio frame is mapped to the bits $\{s_{2LNI \cdot q+1}, \dots, s_{2LNI \cdot (q+1)}}\}$ in subframe #1 or subframe #2. + +The setting of the MBMS notification indicators and the corresponding MICH bits is described in [7]. + +$N_n$ MBMS notification indicators of length $L_{NI}=2$ , $L_{NI}=4$ or $L_{NI}=8$ symbols are transmitted in each radio frame that contains the MICH. The number of MBMS notification indicators $N_{NI}$ per MICH length is given by the MBMS notification indicator length, which is signalled by higher layers. In table 8KBa this number is shown for the different possibilities of MBMS notification indicator lengths. + +**Table 8KBa: Number $N_{NI}$ of MBMS notification indicators per radio frame on type 2 MICH for different MBMS notification indicator lengths $L_{NI}$** + +| | $L_{NI}=2$ | $L_{NI}=4$ | $L_{NI}=8$ | +|-----------------------|------------|------------|------------| +| $N_n$ per radio frame | 31 | 15 | 7 | + +The value NI ( $NI = 0, \dots, N_{NI}-1$ ) calculated by higher layers, is associated to the MBMS notification indicator $N_q$ , where $q = NI \bmod N_n$ . + +The set of NI passed over the Iub indicates all higher layer NI values for which the notification indicator on type 2 MICH should be set to 1 during the corresponding modification period; all other indicators shall be set to 0. + +### 5A.3.13 Physical Layer Common Control Channel (PLCCH) + +The Physical Layer Common Control Channel (PLCCH) is a Node B terminated channel which may be used to carry dedicated (UE-specific) TPC and SS information to multiple UEs. The PLCCH carries TPC and SS information only. No higher layer data is mapped to PLCCH. Each uplink CCTrCH is controlled either by PLCCH or by other appropriate downlink physical channels, under the control of higher layer signalling. + +#### 5A.3.13.1 PLCCH Spreading + +The PLCCH uses only spreading factor $SF=16$ as described in subclause 5A.2.1. The spreading codes for use on the PLCCH are indicated by higher layers. + +#### 5A.3.13.2 PLCCH Burst Type + +The burst format as described in section 5A.2.2 is used for the PLCCH. + +#### 5A.3.13.3 PLCCH Training Sequence + +The training sequences as described in subclause 5A.2.3 are used for PLCCH. + +#### 5A.3.13.4 PLCCH timeslot formats + +The PLCCH shall use time slot format #0 from table 8G, see section 5A.2.2.4.1.2. + +### 5A.3.14 E-DCH Physical Uplink Channel + +UE may have E-PUCH on each carrier. The E-PUCH on one carrier has at least one E-UCCH and one TPC on it. The TPC on the E-PUCH is used to carry the TPC command for the associated downlink control channel on the same carrier. The E-PUCH on one carrier and the E-UCCH and TPC mapped on it obey the following description. + +One or more E-PUCH on one carrier are used to carry the uplink E-DCH transport channel and associated control information (E-UCCH) in each E-DCH TTI. In a timeslot designated by UTRAN for E-PUCH use, up to one E-PUCH may be transmitted by a UE. + +#### 5A.3.14.1 E-UCCH + +The E-DCH Uplink Control Channel (E-UCCH) carries uplink control information associated with the E-DCH and is mapped to E-PUCH on the same carrier. Depending on the configuration of the number of E-UCCH instances and the number of E-PUCH timeslots, an E-PUCH burst may or may not contain E-UCCH and TPC. When E-PUCH does contain E-UCCH, TPC is also transmitted. When E-PUCH does not contain E-UCCH, TPC is not transmitted. + +One E-UCCH instance : + +- is of length 32 physical channel bits +- is mapped to the data field of the E-PUCH +- is spread at SF appointed by CRRI + +- uses QPSK modulation + +There shall be at least one E-UCCH and TPC in every E-DCH TTI. Multiple instances of the same E-UCCH information and TPC can be transmitted within an E-DCH TTI, the detailed number of instances can be set by NodeB MAC-e/i for scheduled transmissions and signalled by higher layers for non-scheduled transmissions. When an E-DCH data block is transmitted on multiple (N) timeslots in one TTI, there will be multiple E-PUCH timeslots. All repetitions of E-UCCH and TPC are evenly distributed on multiple E-PUCH timeslots. N is the number of timeslots of the E-PUCH, M is the number of E-UCCH and TPC instances in one TTI; K is the integral part of M/N; L is the residue of M/N. S is the number of E-UCCHs and TPCs in one E-PUCH timeslot. S equals K+1 for the first L E-PUCH timeslots and equals K for the last (N-L) E-PUCH timeslots. + +The mapping relationship between the TPC commands on the Non-scheduled E-PUCH and the DL timeslot and CCTrCH pairs is the same as that between the TPC commands on the UL DPCH and the DL timeslot and CCTrCH pairs (see subclause 5A.2.2.2). + +The burst composition of the E-UCCH information and the E-DCH data is shown in figure 18M. + +![Figure 18M: Multiplexing structure of E-DCH and E-UCCH. The diagram shows a sequence of blocks representing an E-DCH TTI. It starts with a 'DATA BURST' block, followed by a block containing 'E-UCCH' and 'TPC' sub-fields. This is followed by a 'MIDDLE PART' block, then another block with 'E-UCCH' and 'TPC', and finally another 'DATA BURST' block. Below the diagram, a long double-headed arrow spans the entire sequence and is labeled 'E-DCH TTI'. Two shorter double-headed arrows are positioned below the first and second 'E-UCCH/TPC' blocks, both labeled 'E-UCCH/TPC'.](c2ddad56c1553f2499aaf7ef8cef6777_img.jpg) + +Figure 18M: Multiplexing structure of E-DCH and E-UCCH. The diagram shows a sequence of blocks representing an E-DCH TTI. It starts with a 'DATA BURST' block, followed by a block containing 'E-UCCH' and 'TPC' sub-fields. This is followed by a 'MIDDLE PART' block, then another block with 'E-UCCH' and 'TPC', and finally another 'DATA BURST' block. Below the diagram, a long double-headed arrow spans the entire sequence and is labeled 'E-DCH TTI'. Two shorter double-headed arrows are positioned below the first and second 'E-UCCH/TPC' blocks, both labeled 'E-UCCH/TPC'. + +Figure 18M: Multiplexing structure of E-DCH and E-UCCH + +An E-UCCH is composed of 32 bits: $k_0, k_1 \dots k_{31}$ . It is segmented evenly into two parts shown in figure 18N. + +![Figure 18N: E-UCCH code composition. The diagram shows a horizontal bar representing 32 bits of an E-UCCH, with specific bit positions labeled: k0, k15, k16, and k31. Below this bar, two arrows point to two separate rectangular boxes. The left box is labeled 'FIRST PART OF E-UCCH (E-UCCH PART 1)' and the right box is labeled 'SECOND PART OF E-UCCH (E-UCCH PART 2)'.](17b9d89b91e10c3efc38193baedee268_img.jpg) + +Figure 18N: E-UCCH code composition. The diagram shows a horizontal bar representing 32 bits of an E-UCCH, with specific bit positions labeled: k0, k15, k16, and k31. Below this bar, two arrows point to two separate rectangular boxes. The left box is labeled 'FIRST PART OF E-UCCH (E-UCCH PART 1)' and the right box is labeled 'SECOND PART OF E-UCCH (E-UCCH PART 2)'. + +Figure 18N: E-UCCH code composition + +Figures 18O and 18P show the E-PUCH data burst with and without the E-UCCH/TPC fields. + +![Figure 18O: E-PUCH data burst with E-UCCH/TPC. This diagram is identical to Figure 18M, showing the multiplexing structure of E-DCH and E-UCCH within an E-DCH TTI. It includes 'DATA BURST', 'E-UCCH/TPC', 'MIDDLE PART', 'E-UCCH/TPC', and 'DATA BURST' blocks, with arrows indicating the 'E-DCH TTI' and 'E-UCCH/TPC' components.](acdccfc1d546eaad16a58be576456caf_img.jpg) + +Figure 18O: E-PUCH data burst with E-UCCH/TPC. This diagram is identical to Figure 18M, showing the multiplexing structure of E-DCH and E-UCCH within an E-DCH TTI. It includes 'DATA BURST', 'E-UCCH/TPC', 'MIDDLE PART', 'E-UCCH/TPC', and 'DATA BURST' blocks, with arrows indicating the 'E-DCH TTI' and 'E-UCCH/TPC' components. + +Figure 18O: E-PUCH data burst with E-UCCH/TPC + +![Figure 18P: E-PUCH data burst without E-UCCH/TPC. The diagram shows a sequence of blocks representing an E-DCH TTI without E-UCCH/TPC fields. It consists of a 'DATA BURST AND TPC' block, a 'MIDDLE PART' block, and another 'DATA BURST AND TPC' block. On the far right, there are small boxes for 'E-UCCH' and 'TPC'. Below the diagram, a long double-headed arrow spans the entire sequence and is labeled 'E-DCH TTI'.](24029b85683e6c5b14e96022cd9b6ff6_img.jpg) + +Figure 18P: E-PUCH data burst without E-UCCH/TPC. The diagram shows a sequence of blocks representing an E-DCH TTI without E-UCCH/TPC fields. It consists of a 'DATA BURST AND TPC' block, a 'MIDDLE PART' block, and another 'DATA BURST AND TPC' block. On the far right, there are small boxes for 'E-UCCH' and 'TPC'. Below the diagram, a long double-headed arrow spans the entire sequence and is labeled 'E-DCH TTI'. + +Figure 18P: E-PUCH data burst without E-UCCH/TPC + +#### 5A.3.14.2 E-PUCH Spreading + +The spreading factors that can be applied to the E-PUCH are $SF = 1, 2, 4, 8, 16$ as described in subclause 5A.2.1. All E-PUCH use the same spreading factor within an E-DCH TTI. For scheduled transmissions, E-PUCHs use the spreading factor indicated by CRRI on E-AGCH. + +#### 5A.3.14.3 E-PUCH Burst Types + +The burst types as described in subclause 5A.2.2 can be used for E-PUCH. E-UCCH and TPC can be transmitted on the E-PUCH. + +In case that TPC on non-scheduled E-PUCH is not used to adjust transmitting power level of downlink DPCH, Node B should not apply TPC commands received from non-scheduled E-PUCH. + +#### 5A.3.14.4 E-PUCH Training Sequences + +The training sequences as described in subclause 5A.2.3 are used for the E-PUCH. + +#### 5A.3.14.5 UE Selection + +UEs that shall transmit on the E-PUCH are selected by higher layers. The UE id on the associated E-AGCH shall be used for identification. + +#### 5A.3.14.6 E-PUCH timeslot formats + +An E-PUCH may use QPSK or 16QAM modulation symbols and may or may not contain E-UCCH/TPC. The time slot formats are shown in table 8KC. + +Error: + +3 + +Error: Reference source not + +**Table 8KC: Time slot formats for the E-PUCH** + +Error: + +4 + +Error: Reference source not + +| Slot Format # | 0 (QPSK) | 1 (16QAM) | 2 (QPSK) | 3 (16QAM) | 4 (QPSK) | 5 (16QAM) | 6 (QPSK) | 7 (16QAM) | 8 (QPSK) | 9 (16QAM) | 10 (QPSK) | 11 (16QAM) | 12 (QPSK) | 13 (16QAM) | +|----------------------------------------|----------|-----------|----------|-----------|----------|-----------|----------|-----------|----------|-----------|-----------|------------|-----------|------------| +| Spreading Factor | 16 | 16 | 16 | 16 | 16 | 16 | 8 | 8 | 8 | 8 | 8 | 8 | 8 | 8 | +| Midamble length (chips) | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | +| Bits/slot | 88 | 176 | 88 | 142 | 88 | 108 | 176 | 352 | 176 | 318 | 176 | 284 | 176 | 250 | +| N Data/Slot (bits) | 88 | 176 | 54 | 108 | 20 | 40 | 176 | 352 | 142 | 284 | 108 | 216 | 74 | 148 | +| N data/data field(1) (bits) | 44 | 88 | 28 | 56 | 12 | 24 | 88 | 176 | 72 | 144 | 56 | 112 | 40 | 80 | +| N EUCCH8_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N EUCCH7_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N EUCCH6_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N EUCCH5_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N EUCCH4_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N EUCCH3_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | +| N EUCCH2_part1 (bits) | 0 | 0 | 0 | 0 | 16 | 16 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | +| N EUCCH1_part1 (bits) | 0 | 0 | 16 | 16 | 16 | 16 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | +| N TPC1 (bits) | 0 | 0 | 2 | 2 | 2 | 2 | 0 | 0 | 2 | 2 | 2 | 2 | 2 | 2 | +| N EUCCH1_part2 (bits) | 0 | 0 | 16 | 16 | 16 | 16 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | +| N TPC2 (bits) | 0 | 0 | 0 | 0 | 2 | 2 | 0 | 0 | 0 | 0 | 2 | 2 | 2 | 2 | +| N EUCCH2_part2 (bits) | 0 | 0 | 0 | 0 | 16 | 16 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | +| N TPC3 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 2 | +| N EUCCH3_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | +| N TPC4 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N EUCCH4_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N TPC5 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N EUCCH5_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N TPC6 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N EUCCH6_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N TPC7 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N EUCCH7_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N TPC8 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N EUCCH8_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N data/data field(2) | 44 | 88 | 26 | 52 | 8 | 16 | 88 | 176 | 70 | 140 | 52 | 104 | 34 | 68 | + +Error: + +5 + +Error: Reference source not + +| Slot Format # | 0
(QPSK) | 1
(16QAM) | 2
(QPSK) | 3
(16QAM) | 4
(QPSK) | 5
(16QAM) | 6
(QPSK) | 7
(16QAM) | 8
(QPSK) | 9
(16QAM) | 10
(QPSK) | 11
(16QAM) | 12
(QPSK) | 13
(16QAM) | +|---------------|-------------|--------------|-------------|--------------|-------------|--------------|-------------|--------------|-------------|--------------|--------------|---------------|--------------|---------------| +| (bits) | | | | | | | | | | | | | | | + +Error: + +6 + +Error: Reference source not + +Error: + +7 + +Error: Reference source not + +| Slot Format # | 14 (QPSK) | 15 (16QAM) | 16 (QPSK) | 17 (16QAM) | 18 (QPSK) | 19 (16QAM) | 20 (QPSK) | 21 (16QAM) | 22 (QPSK) | 23 (16QAM) | 24 (QPSK) | 25 (16QAM) | 26 (QPSK) | 27 (16QAM) | +|----------------------------------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------| +| Spreading Factor | 8 | 8 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | +| Midamble length (chips) | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | +| Bits/slot | 176 | 216 | 352 | 704 | 352 | 670 | 352 | 636 | 352 | 602 | 352 | 568 | 352 | 534 | +| N Data/Slot (bits) | 40 | 80 | 352 | 704 | 318 | 636 | 284 | 568 | 250 | 500 | 216 | 432 | 182 | 364 | +| N data/data field(1) (bits) | 24 | 48 | 176 | 352 | 160 | 320 | 144 | 288 | 128 | 256 | 112 | 224 | 96 | 192 | +| N EUCCH8_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N EUCCH7_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N EUCCH6_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N EUCCH5_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | +| N EUCCH4_part1 (bits) | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | +| N EUCCH3_part1 (bits) | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | +| N EUCCH2_part1 (bits) | 16 | 16 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | +| N EUCCH1_part1 (bits) | 16 | 16 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | +| N TPC1 (bits) | 2 | 2 | 0 | 0 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | +| N EUCCH1_part2 (bits) | 16 | 16 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | +| N TPC2 (bits) | 2 | 2 | 0 | 0 | 0 | 0 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | +| N EUCCH2_part2 (bits) | 16 | 16 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | +| N TPC3 (bits) | 2 | 2 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 2 | 2 | 2 | 2 | 2 | +| N EUCCH3_part2 (bits) | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | +| N TPC4 (bits) | 2 | 2 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 2 | 2 | 2 | +| N EUCCH4_part2 (bits) | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | +| N TPC5 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 2 | +| N EUCCH5_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | +| N TPC6 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N EUCCH6_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N TPC7 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N EUCCH7_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N TPC8 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N EUCCH8_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N data/data field(2) | 16 | 32 | 176 | 352 | 158 | 316 | 140 | 280 | 122 | 244 | 104 | 208 | 86 | 172 | + +Error: + +8 + +Error: Reference source not + +| Slot Format # | 14
(QPSK) | 15
(16QAM) | 16
(QPSK) | 17
(16QAM) | 18
(QPSK) | 19
(16QAM) | 20
(QPSK) | 21
(16QAM) | 22
(QPSK) | 23
(16QAM) | 24
(QPSK) | 25
(16QAM) | 26
(QPSK) | 27
(16QAM) | +|----------------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------| +| (bits) | | | | | | | | | | | | | | | + +Error: + +9 + +Error: Reference source not + +Error: + +10 + +Error: Reference source not + +| Slot Format # | 28 (QPSK) | 29 (16QAM) | 30 (QPSK) | 31 (16QAM) | 32 (QPSK) | 33 (16QAM) | 34 (QPSK) | 35 (16QAM) | 36 (QPSK) | 37 (16QAM) | 38 (QPSK) | 39 (16QAM) | 40 (QPSK) | 41 (16QAM) | +|----------------------------------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------| +| Spreading Factor | 4 | 4 | 4 | 4 | 4 | 4 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | +| Midamble length (chips) | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | +| Bits/slot | 352 | 500 | 352 | 466 | 352 | 432 | 704 | 1408 | 704 | 1374 | 704 | 1340 | 704 | 1306 | +| N Data/Slot (bits) | 148 | 296 | 114 | 228 | 80 | 160 | 704 | 1408 | 670 | 1340 | 636 | 1272 | 602 | 1204 | +| N data/data field(1) (bits) | 80 | 160 | 64 | 128 | 48 | 96 | 352 | 704 | 336 | 672 | 320 | 640 | 304 | 608 | +| N EUCCH8_part1 (bits) | 0 | 0 | 0 | 0 | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N EUCCH7_part1 (bits) | 0 | 0 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N EUCCH6_part1 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N EUCCH5_part1 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N EUCCH4_part1 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N EUCCH3_part1 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | +| N EUCCH2_part1 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | +| N EUCCH1_part1 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | +| N TPC1 (bits) | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 0 | 2 | 2 | 2 | 2 | 2 | 2 | +| N EUCCH1_part2 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | +| N TPC2 (bits) | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 0 | 0 | 0 | 2 | 2 | 2 | 2 | +| N EUCCH2_part2 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | +| N TPC3 (bits) | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 2 | +| N EUCCH3_part2 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | +| N TPC4 (bits) | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N EUCCH4_part2 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N TPC5 (bits) | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N EUCCH5_part2 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N TPC6 (bits) | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N EUCCH6_part2 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N TPC7 (bits) | 0 | 0 | 2 | 2 | 2 | 2 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N EUCCH7_part2 (bits) | 0 | 0 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N TPC8 (bits) | 0 | 0 | 0 | 0 | 2 | 2 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N EUCCH8_part2 (bits) | 0 | 0 | 0 | 0 | 16 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | +| N data/data field(2) | 68 | 136 | 50 | 100 | 32 | 64 | 352 | 704 | 334 | 668 | 316 | 632 | 298 | 596 | + +Error: + +11 + +Error: Reference source not + +| Slot Format # | 28
(QPSK) | 29
(16QAM) | 30
(QPSK) | 31
(16QAM) | 32
(QPSK) | 33
(16QAM) | 34
(QPSK) | 35
(16QAM) | 36
(QPSK) | 37
(16QAM) | 38
(QPSK) | 39
(16QAM) | 40
(QPSK) | 41
(16QAM) | +|----------------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------| +| (bits) | | | | | | | | | | | | | | | + +Error: + +12 + +Error: Reference source not + +Error: + +13 + +Error: Reference source not + +| Slot Format # | 42 (QPSK) | 43 (16QAM) | 44 (QPSK) | 45 (16QAM) | 46 (QPSK) | 47 (16QAM) | 48 (QPSK) | 49 (16QAM) | 50 (QPSK) | 51 (16QAM) | 52 (QPSK) | 53 (16QAM) | 54 (QPSK) | 55 (16QAM) | +|----------------------------------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------| +| Spreading Factor | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | +| Midamble length (chips) | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | +| Bits/slot | 704 | 1272 | 704 | 1238 | 704 | 1204 | 704 | 1170 | 704 | 1136 | 1408 | 2816 | 1408 | 2782 | +| N Data/Slot (bits) | 568 | 1136 | 534 | 1068 | 500 | 1000 | 466 | 932 | 432 | 864 | 1408 | 2816 | 1374 | 2748 | +| N data/data field(1) (bits) | 288 | 576 | 272 | 544 | 256 | 512 | 240 | 480 | 224 | 448 | 704 | 1408 | 688 | 1376 | +| N EUCCH8_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | 0 | 0 | 0 | 0 | +| N EUCCH7_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | +| N EUCCH6_part1 (bits) | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | +| N EUCCH5_part1 (bits) | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | +| N EUCCH4_part1 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | +| N EUCCH3_part1 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | +| N EUCCH2_part1 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | +| N EUCCH1_part1 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 16 | 16 | +| N TPC1 (bits) | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 0 | 2 | 2 | +| N EUCCH1_part2 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 16 | 16 | +| N TPC2 (bits) | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 0 | 0 | 0 | +| N EUCCH2_part2 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | +| N TPC3 (bits) | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 0 | 0 | 0 | +| N EUCCH3_part2 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | +| N TPC4 (bits) | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 0 | 0 | 0 | +| N EUCCH4_part2 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | +| N TPC5 (bits) | 0 | 0 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 0 | 0 | 0 | +| N EUCCH5_part2 (bits) | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | +| N TPC6 (bits) | 0 | 0 | 0 | 0 | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 0 | 0 | 0 | +| N EUCCH6_part2 (bits) | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | +| N TPC7 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 2 | 2 | 2 | 0 | 0 | 0 | 0 | +| N EUCCH7_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | 0 | 0 | 0 | 0 | +| N TPC8 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 2 | 0 | 0 | 0 | 0 | +| N EUCCH8_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | 0 | 0 | 0 | 0 | +| N data/data field(2) | 280 | 560 | 262 | 524 | 244 | 488 | 226 | 452 | 208 | 416 | 704 | 1408 | 686 | 1372 | + +Error: + +14 + +Error: Reference source not + +| Slot Format # | 42
(QPSK) | 43
(16QAM) | 44
(QPSK) | 45
(16QAM) | 46
(QPSK) | 47
(16QAM) | 48
(QPSK) | 49
(16QAM) | 50
(QPSK) | 51
(16QAM) | 52
(QPSK) | 53
(16QAM) | 54
(QPSK) | 55
(16QAM) | +|----------------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------| +| (bits) | | | | | | | | | | | | | | | + +Error: + +15 + +Error: Reference source not + +Error: + +16 + +Error: Reference source not + +| Slot Format # | 56 (QPSK) | 57 (16QAM) | 58 (QPSK) | 59 (16QAM) | 60 (QPSK) | 61 (16QAM) | 62 (QPSK) | 63 (16QAM) | 64 (QPSK) | 65 (16QAM) | 66 (QPSK) | 67 (16QAM) | 68 (QPSK) | 69 (16QAM) | +|----------------------------------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------|-----------|------------| +| Spreading Factor | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | +| Midamble length (chips) | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | 144 | +| Bits/slot | 1408 | 2748 | 1408 | 2714 | 1408 | 2680 | 1408 | 2646 | 1408 | 2612 | 1408 | 2578 | 1408 | 2544 | +| N Data/Slot (bits) | 1340 | 2680 | 1306 | 2612 | 1272 | 2544 | 1238 | 2476 | 1204 | 2408 | 1170 | 2340 | 1136 | 2272 | +| N data/data field(1) (bits) | 672 | 1344 | 656 | 1312 | 640 | 1280 | 624 | 1248 | 608 | 1216 | 592 | 1184 | 576 | 1152 | +| N EUCCH8_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | +| N EUCCH7_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | +| N EUCCH6_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | +| N EUCCH5_part1 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | +| N EUCCH4_part1 (bits) | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | +| N EUCCH3_part1 (bits) | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | +| N EUCCH2_part1 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | +| N EUCCH1_part1 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | +| N TPC1 (bits) | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | +| N EUCCH1_part2 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | +| N TPC2 (bits) | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | +| N EUCCH2_part2 (bits) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | +| N TPC3 (bits) | 0 | 0 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | +| N EUCCH3_part2 (bits) | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | +| N TPC4 (bits) | 0 | 0 | 0 | 0 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | +| N EUCCH4_part2 (bits) | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | +| N TPC5 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | +| N EUCCH5_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | +| N TPC6 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 2 | 2 | 2 | 2 | 2 | +| N EUCCH6_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | 16 | 16 | +| N TPC7 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 2 | 2 | 2 | +| N EUCCH7_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | 16 | 16 | +| N TPC8 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 2 | +| N EUCCH8_part2 (bits) | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 16 | 16 | +| N data/data field(2) | 668 | 1336 | 650 | 1300 | 632 | 1264 | 614 | 1228 | 596 | 1192 | 578 | 1156 | 560 | 1120 | + +Error: + +17 + +Error: Reference source not + +| Slot Format # | 56
(QPSK) | 57
(16QAM) | 58
(QPSK) | 59
(16QAM) | 60
(QPSK) | 61
(16QAM) | 62
(QPSK) | 63
(16QAM) | 64
(QPSK) | 65
(16QAM) | 66
(QPSK) | 67
(16QAM) | 68
(QPSK) | 69
(16QAM) | +|---------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------|---------------| +| (bits) | | | | | | | | | | | | | | | + +### 5A.3.15 E-DCH Random Access Uplink Control Channel (E-RUCCH) + +The E-RUCCH is used to carry E-DCH-associated uplink control signalling when E-PUCH resources are not available. It shall be mapped to the same random access physical resources defined by UTRAN. + +For multi-carrier E-DCH transmission, each UE is configured with only one carrier for the E-RUCCH transmission. + +The E-RUCCH on the configured carrier shall be mapped to the same random access physical resources defined by UTRAN on the same carrier. + +#### 5A.3.15.1 E-RUCCH Spreading + +The E-RUCCH uses spreading factor SF=16 or SF=8 as described in subclause 5A.2.1. The set of admissible spreading codes used on the E-RUCCH are based on the spreading codes of PRACH. + +#### 5A.3.15.2 E-RUCCH Burst Format + +The burst format as described in section 5A.2.2 is used for the E-RUCCH. + +#### 5A.3.15.3 E-RUCCH Training sequences + +The training sequences, i.e. midambles, as described in subclause 5A.2.3 are used for E-RUCCH. + +#### 5A.3.15.4 E-RUCCH timeslot formats + +The timeslot format depends on the spreading factor of the E-RUCCH: + +| Spreading Factor | Slot Format # | +|------------------|---------------| +| 16 | 0 | +| 8 | 10 | + +### 5A.3.16 E-DCH Absolute Grant Channel (E-AGCH) + +The E-DCH Absolute Grant Channel (E-AGCH) on one carrier is a downlink physical channel carrying the uplink E-DCH absolute grant control information of the same carrier. The E-AGCH on one carrier uses two separate physical channels (E-AGCH1 and E-AGCH2). The term E-AGCH refers to the ensemble of these physical channels. The detailed description of the E-AGCH on one carrier is given below. + +#### 5A.3.16.1 E-AGCH Spreading + +Spreading of the E-AGCH is common with 3.84Mcps TDD, cf. [5.3.15.1 E-AGCH Spreading]. + +#### 5A.3.16.2 E-AGCH Burst Types + +The burst structures for E-AGCH1 and E-AGCH2 are shown in figure 18Q and 18R. + +![Diagram of E-AGCH1 burst structure showing Data symbols, Midamble, SS symbol(s), TPC symbol(s), and GP. The Midamble is 144 chips long, and the total burst length is 864 chips.](48c6848be25e5a699f0a3412e68bc102_img.jpg) + +The diagram illustrates the E-AGCH1 burst structure. It consists of a horizontal bar divided into five segments: 'Data symbols', 'Midamble', 'SS symbol(s)' (highlighted in yellow), 'TPC symbol(s)' (highlighted in yellow), and 'GP'. A double-headed arrow below the 'Midamble' segment is labeled '144 chips'. A longer double-headed arrow below the entire bar is labeled '864 Chips'. Arrows from the labels 'SS symbol(s)' and 'TPC symbol(s)' point to their respective segments in the burst. + +Diagram of E-AGCH1 burst structure showing Data symbols, Midamble, SS symbol(s), TPC symbol(s), and GP. The Midamble is 144 chips long, and the total burst length is 864 chips. + +Figure 18Q: E-AGCH1 burst structure + +![Figure 18R: E-AGCH2 burst structure diagram showing four segments: Data symbols (352 chips), Midamble (144 chips), Data symbols (352 chips), and GP (16 CP). The total duration is 864 * Tc.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +| | | | | +|---------------------------|-----------------------|---------------------------|-------------| +| Data symbols
352 chips | Midamble
144 chips | Data symbols
352 chips | GP
16 CP | +| 864 * T c | | | | + +Figure 18R: E-AGCH2 burst structure diagram showing four segments: Data symbols (352 chips), Midamble (144 chips), Data symbols (352 chips), and GP (16 CP). The total duration is 864 \* Tc. + +Figure 18R: E-AGCH2 burst structure + +#### 5A.3.16.3 E-AGCH Training Sequences + +The training sequences as described in subclause 5A.2.3 are used for the E-AGCH. + +#### 5A.3.16.4 E-AGCH timeslot formats + +E-AGCH1 shall use time slot format #5 and E-AGCH2 shall use time slot format #0 from table 8F, see section 5A.2.2.4.1.1, i.e. E-AGCH shall carry TPC and SS for E-PUCH power control and synchronization but no TFCI. + +Table 8KD: Timeslot formats for the E-AGCH + +| Slot Format # | Spreading Factor | Midamble length (chips) | N TFCI code word (bits) | N ss &N TPC (bits) | Bits/slot | N Data/Slot (bits) | N data/data field (1) (bits) | N data/data field (2) (bits) | +|---------------|------------------|-------------------------|------------------------------------|------------------------------------------|-----------|-------------------------------|-----------------------------------------|-----------------------------------------| +| 0 | 16 | 144 | 0 | 0&0 | 88 | 88 | 44 | 44 | +| 5 | 16 | 144 | 0 | 2&2 | 88 | 84 | 44 | 40 | + +### 5A.3.17 E-DCH Hybrid ARQ Acknowledgement Indicator Channel (E-HICH) + +The E-DCH HARQ Acknowledgement indicator channel (E-HICH) on one carrier is defined in terms of a SF16 downlink physical channel and a signature sequence on the same carrier. + +The E-HICH on one carrier carries one or multiple users' acknowledgement indicator on the same carrier. The detailed description of the E-HICH on one carrier is given below. + +Figure 18S illustrates the structure of the E-HICH on one carrier. The E-HICH contains 8 spare bit locations. The spare bit values are undefined. The power of each user's acknowledgement indicator may be set independently by the Node-B. The number of E-HICHs in a cell is configured by the system. + +The acknowledgement indicators for the E-PUCH semi-persistent scheduling operation can be transmitted on the same E-HICH carrying indicators for scheduled traffic or the E-HICH carrying indicators for non-scheduled traffic. + +![Figure 18S: E-HICH Structure diagram showing a burst with segments: Data Symbols, Spare bits (two grey blocks), Midamble, Data Symbols, and GP. The total duration is 864 chips.](2f58bcce74146d4d983070d93be12291_img.jpg) + +| | | | | | | +|--------------|--|----------|--|--------------|----| +| Data Symbols | | Midamble | | Data Symbols | GP | +| 864 chips | | | | | | + +Figure 18S: E-HICH Structure diagram showing a burst with segments: Data Symbols, Spare bits (two grey blocks), Midamble, Data Symbols, and GP. The total duration is 864 chips. + +Figure 18S: E-HICH Structure + +For Scheduled transmissions, at most four E-HICHs can be configured for one user's scheduled transmission. Which E-HICH is used to convey the HARQ acknowledgment indicator is indicated by the 2-bit E-HICH indicator on E-AGCH. A single E-HICH may carry one or multiple HARQ acknowledgement indicator(s) which are decided by the Node-B. + +For Non-Scheduled transmissions, E-HICHs carry not only the HARQ acknowledgement indicators but also TPC and SS commands. The 80 signature sequences are divided into 20 groups while each group includes 4 sequences. Every non-scheduled user is assigned only one group which are signalled by higher layer. Among the 4 sequences, the first one is used to indicate ACK/NACK, and the other three are used to indicate the TPC/SS commands. The three sequences and their three reverse sequences are the six possible sequences used to indicate the TPC/SS combination state. The reverse sequence is constructed by reverse every bit of the sequence from 0 to 1 or from 1 to 0. The mapping between the index and the TPC/SS command is shown in table 8KE. The index is calculated according to the equation: $index = 2 * A + B$ , ( $A = 0, 1, 2$ ; $B = 0, 1$ ). A is the relative index of the selected sequence among the three assigned sequences and B equals to 1 when the reverse sequence is chosen, otherwise, B equals to 0. The power of the sequence used for TPC/SS indication can be set differently from the one used to indicate ACK/NACK. + +**Table 8KE: Mapping between the index and TPC/SS command** + +| index | TPC command | SS command | +|-------|-------------|--------------| +| 0 | 'DOWN' | 'DOWN' | +| 1 | 'UP' | 'DOWN' | +| 2 | 'DOWN' | 'UP' | +| 3 | 'UP' | 'UP' | +| 4 | 'DOWN' | 'Do Nothing' | +| 5 | 'UP' | 'Do Nothing' | + +For the E-DCH semi-persistent scheduling operation, E-HICHs carry not only the HARQ acknowledgement indicators but also TPC and SS commands. Each user is also assigned one signature sequence group including 4 sequences whose usage is completely complying with the definition in non-scheduled transmissions. + +The acknowledgement indicator for an E-DCH transmission in TTI "N" is carried by the E-HICH in TTI "N+[TA]" (TA is determined according to the value of $n_{E-HICH}$ ). The E-HICH is thus synchronously related to those E-DCH transmissions for which it carries acknowledgement information. + +#### 5A.3.17.1 E-HICH Spreading + +Multiple users' signature sequences (including the inserted spare bits) sharing the same channelisation code are combined and spread using spreading factor SF=16 as described in [8]. + +#### 5A.3.17.2 E-HICH Burst Types + +The burst structures for E-HICH are shown in figure 18D. + +#### 5A.3.17.3 E-HICH Training Sequences + +The training sequences as described in subclause 5A.2.3 are used for the E-HICH. + +#### 5A.3.17.4 E-HICH timeslot formats + +E-HICH shall use time slot format #0 from table 8F. + +### 5A.3.18 Standalone midamble channel + +#### 5A.3.18.1 Standalone midamble channel Burst Format + +A standalone midamble channel traffic burst consists of a midamble of 144 chips only. The burst format is shown in Figure 18T. The contents of the traffic burst fields are described in table 8KF. + +**Table 8KF: The contents of the standalone midamble channel traffic burst format fields** + +| Chip number (CN) | Length of field in chips | Contents of field | +|------------------|--------------------------|-------------------| +| 0-351 | 352 | NULL | +| 352-495 | 144 | Midamble | +| 496-863 | 368 | NULL | + +![Figure 18T: Burst structure of the standalone midamble channel traffic burst format. The diagram shows a horizontal bar divided into three equal-width rectangular segments. Below the bar, a double-headed arrow spans the entire length, indicating the full burst duration.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +Figure 18T: Burst structure of the standalone midamble channel traffic burst format. The diagram shows a horizontal bar divided into three equal-width rectangular segments. Below the bar, a double-headed arrow spans the entire length, indicating the full burst duration. + +Figure 18T: Burst structure of the standalone midamble channel traffic burst format + +#### 5A.3.18.3 Standalone midamble channel Training Sequences + +The training sequences as described in subclause 5A.2.3 are used for the standalone midamble channel. + +#### 5A.3.18.4 Standalone midamble channel timeslot formats + +The timeslot formats for the standalone midamble channel are shown in table 8KG. + +**Table 8KG: Timeslot formats for the standalone midamble channel** + +| Slot Format # | Midamble length (chips) | N TFCI code word (bits) | N SS & N TPC (bits) | Bits/slot | N Data/Slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) | +|---------------|-------------------------|------------------------------------|-------------------------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------| +| 0 | 144 | 0 | 0 & 0 | 0 | 0 | 0 | 0 | + +## 5A.4 Transmit Diversity for DL Physical Channels + +Table 8L summarizes the different transmit diversity schemes for different downlink physical channel types in 1.28Mcps TDD that are described in [9]. + +**Table 8L: Application of Tx diversity schemes on downlink physical channel types in 1.28Mcps TDD** + "X" – can be applied, "-" – must not be applied + +| Physical channel type | Open loop TxDiversity | | Closed loop TxDiversity | +|--------------------------------|-----------------------|------|-------------------------| +| | TSTD | SCTD | | +| P-CCPCH | X(†) | X(†) | – | +| S-CCPCH | X(†) | X(†) | – | +| DwPCH | X | – | – | +| DPCH | X | – | X | +| PDSCH | X | X | X | +| PICH | X | X | – | +| MICH | X(†) | X(†) | – | +| PLCCH | X | X | – | +| HS-SCCH | – | X | X | +| HS-PDSCH (UE not in MIMO mode) | – | – | X | +| HS-PDSCH (UE in MIMO mode) | – | – | – | +| E-AGCH | -- | X | X | +| E-HICH | -- | X | -- | + +(\*) Note: SCTD may only be applied to physical channels when they are allocated to beacon locations. + +(†) Note: that when the entire carrier is dedicated to MBMSFN operation, TSTD and SCTD shall not be applied. + +## 5A.5 Beacon characteristics of physical channels + +For the purpose of measurements, common physical channels that are allocated to particular locations (time slot, code) shall have particular physical characteristics, called beacon characteristics. Physical channels with beacon characteristics are called beacon channels. The location of the beacon channels is called beacon location. The beacon + +channels shall provide the beacon function, i.e. a reference power level at the beacon location, regularly existing in each subframe. Thus, beacon channels must be present in each subframe. + +### 5A.5.1 Location of beacon channels + +The beacon location is described as follows: + +The beacon function shall be provided by the physical channels that are allocated to channelisation code $c_{Q=16}^{(k=1)}$ and $c_{Q=16}^{(k=2)}$ in Timeslot#0. + +Note that by this definition the P-CCPCH always has beacon characteristics. In a multi-frequency cell beacon channels are always transmitted on the primary frequency. + +### 5A.5.2 Physical characteristics of the beacon function + +The beacon channels shall have the following physical characteristics. + +They: + +- are transmitted with reference power; +- are transmitted without beamforming; +- use midamble $m^{(1)}$ and $m^{(2)}$ exclusively in this time slot + +The reference power corresponds to the sum of the power allocated to both midambles $m^{(1)}$ and $m^{(2)}$ . Two possibilities exist: + +- If SCTD antenna diversity is not applied to beacon channels, all the reference power of any beacon channel is allocated to $m^{(1)}$ . +- If SCTD antenna diversity is applied to beacon channels, for any beacon channel midambles $m^{(1)}$ and $m^{(2)}$ are each allocated half of the reference power. + +## 5A.6 Midamble Allocation for Physical Channels + +Midambles are part of the physical channel configuration which is performed by higher layers. Four different midamble allocation schemes exist: + +- UE specific midamble allocation: A UE specific midamble for DL or UL is explicitly assigned by higher layers. +- Default midamble allocation: The midamble for DL or UL is allocated by layer 1 depending on the associated channelisation code. +- Common midamble allocation: The midamble for the DL is allocated by layer 1 depending on the number of channelisation codes currently being present in the DL time slot. +- Special Default midamble allocation: The midamble for DL or UL is also allocated by layer 1 depending on the associated channelisation code while the association is different from default midamble allocation. + +If a midamble is not explicitly assigned and the use of the common midamble allocation scheme is not signalled by higher layers, the midamble shall be allocated by layer 1, based on default or special default midamble allocation scheme. This default or special default midamble allocation scheme is given by a fixed association between midambles and channelisation codes, and shall be applied individually to all channelisation codes within one time slot. Different associations apply for different burst types and cell configurations with respect to the maximum number of midambles. + +The associations between channelisation codes and midambles for the default, special default and common midamble allocation differ from the 3.84 Mcps TDD option. The associations are given in Annex AA.2 [Association between Midambles and channelisation Codes for default midamble allocation], Annex AA.3 [Association between Midambles and channelisation Codes for special default midamble allocation] and BA [Signalling of the number of channelisation codes for the DL common midamble case for 1.28Mcps TDD] respectively. + +However, for timeslots employing MBSFN operation there is no single midamble restriction per MBSFN timeslot, i.e. $K_{\text{Cell}} \geq 1$ , whilst this does not undermine the specification that all physical channels in such timeslots employ the same midamble(s) and thus default and common midamble allocation amount to the same allocation strategies. + +### 5A.6.1 Midamble Allocation for DL Physical Channels + +Beacon channels shall always use the reserved midambles $m^{(1)}$ and $m^{(2)}$ , see 5A.5. For the other DL physical channels that are located in timeslot #0, midambles shall be allocated based on the default midamble allocation scheme, using the association for $K=8$ midambles. For all other DL physical channels, the midamble is explicitly assigned by higher layers or allocated by layer 1. + +#### 5A.6.1.1 Midamble Allocation by signalling from higher layers + +The midamble allocation by signalling is the same like in the 3.84 Mcps TDD cf. [5.6.1.1 Midamble allocation by signalling from higher layers] + +#### 5A.6.1.2 Midamble Allocation by layer 1 + +##### 5A.6.1.2.1 Default midamble + +The default midamble allocation by layer 1 is the same like in the 3.84 Mcps TDD cf. [5.6.1.2.1 Default midamble]. The associations between midambles and channelisation codes are given in Annex AA.2 [Association between Midambles and channelisation Codes for default midamble allocation]. + +If the variable E\_DCH\_SPS\_STATUS = TRUE then two E-HICHs associated with the same midamble shift in the same timeslot can be configured. + +##### 5A.6.1.2.2 Common Midamble + +The common midamble allocation by layer 1 is the same like in the 3.84 Mcps TDD cf. [5.6.1.2.2 Common midamble]. The respective associations are given in Annex BA [Signalling of the number of channelisation codes for the DL common midamble case for 1.28 Mcps TDD]. + +##### 5A.6.1.2.3 Special Default Midamble + +For MIMO dual stream transmission, there are two patterns (pattern 1 and pattern 2) of the association between midambles and channelisation codes for special default midamble allocation scheme for each cell configurations with respect to the maximum number of midambles. + +For MU-MIMO transmission, there are four patterns (pattern 1A, pattern 1B, pattern 2A and pattern 2B) of the association between midambles and channelisation codes for special default midamble allocation scheme for each cell configurations with respect to the maximum number of midambles. + +If the UE is configured in MIMO or MU-MIMO mode and the default midamble allocation scheme is signalled to the UE by higher layers, the default or special default midamble allocation scheme can be used. Whether the default or special default midamble allocation scheme is used is signalled to the UE by the related physical channel in [7]. The association between midambles and channelisation codes for the special default midamble allocation scheme for both MIMO dual stream transmission and MU-MIMO transmission are given in Annex AA.3 [Association between Midambles and channelisation Codes for special default midamble allocation]. + +### 5A.6.2 Midamble Allocation for UL Physical Channels + +The midamble allocation for UL Physical Channels is the same as in the 3.84 Mcps TDD cf. [5.6.2 Midamble allocation for UL Physical Channels] + +## 5A.7 Midamble Transmit Power + +When standalone midamble channel is not transmitted, the setting of the midamble transmit power is done as in the 3.84 Mcps TDD option cf. 5.7 'Midamble Transmit Power' + +## 5A.7a Preamble Allocation and Preamble Transmit Power + +When the entire carrier is dedicated to MBSFN, for all timeslots employing MBSFN operation, only a single preamble is needed, i.e. $K_{\text{Cell}}=1$ , then all physical channels in such timeslots employ the same preamble with the same allocation strategies. + +There shall be no offset between the sum of the powers allocated to all preambles in a timeslot and the sum of the powers allocated to the data symbol fields. The transmit power within a timeslot is hence constant. + +# 5B Physical channels for the 7.68 Mcps option + +## 5B.1 General + +All physical channels take a three-layer structure with respect to timeslots, radio frames and system frame numbering (SFN). Depending on the resource allocation, the configuration of radio frames or timeslots becomes different. All physical channels need a guard period in every timeslot. The time slots are used in the sense of a TDMA component to separate different user signals in the time domain. The physical channel signal format is presented in figure 18AA. + +A physical channel in the 7.68 Mcps TDD option is a burst, which is transmitted in a particular timeslot within allocated Radio Frames. The allocation can be continuous, i.e. the time slot in every frame is allocated to the physical channel or discontinuous, i.e. the time slot in a subset of all frames is allocated only. A burst is the combination of two data parts, a midamble part and a guard period. The duration of a burst is one time slot. Several bursts can be transmitted at the same time from one transmitter. In this case, the data parts must use different OVSF channelisation codes, but the same scrambling code. The midamble parts are either identically or differently shifted versions of a cell-specific basic midamble code, see section 5B.3.3. Note when in MBSFN operation, a midamble is not necessarily cell-specific. + +![Figure 18AA: Physical channel signal format. The diagram illustrates the hierarchical structure of a radio frame and timeslots. At the top, a 'Radio Frame (10ms)' is shown as a horizontal bar containing 'frame #i' and 'frame #i+1'. Below this, a 'Timeslot (5120 * T_c)' is shown as a horizontal bar containing 'timeslot #0', 'timeslot #1', 'timeslot #2', a gap, 'timeslot #13', and 'timeslot #14'. Dashed lines connect the corners of the 'frame #i' box to the corners of the 'timeslot #0' box, indicating that one frame contains 15 timeslots.](d3b5eac55166fc428a223bba5c46961b_img.jpg) + +Figure 18AA: Physical channel signal format. The diagram illustrates the hierarchical structure of a radio frame and timeslots. At the top, a 'Radio Frame (10ms)' is shown as a horizontal bar containing 'frame #i' and 'frame #i+1'. Below this, a 'Timeslot (5120 \* T\_c)' is shown as a horizontal bar containing 'timeslot #0', 'timeslot #1', 'timeslot #2', a gap, 'timeslot #13', and 'timeslot #14'. Dashed lines connect the corners of the 'frame #i' box to the corners of the 'timeslot #0' box, indicating that one frame contains 15 timeslots. + +**Figure 18AA: Physical channel signal format** + +The data part of the burst is spread with a combination of channelisation code and scrambling code. The channelisation code is an OVSF code, that can have a spreading factor of 1, 2, 4, 8, 16 or 32. The data rate of the physical channel depends on the used spreading factor of the used OVSF code. + +The midamble part of the burst can contain two different types of midambles: a short one of length 512 chips, or a long one of length 1024 chips. The data rate of the physical channel depends on the used midamble length. Additionally, when in MBSFN operation a midamble of length 640 chips is used. + +So a physical channel is defined by frequency, timeslot, channelisation code, burst type and Radio Frame allocation. The scrambling code and the basic midamble code are broadcast and may be constant within a cell. When a physical channel is established, a start frame is given. The physical channels can either be of infinite duration, or of a duration defined by allocation. + +## 5B.2 Frame structure + +The TDMA frame has a duration of 10 ms and is subdivided into 15 time slots (TS) of $5120 \cdot T_c$ duration each. A time slot corresponds to 5120 chips. The physical content of the time slots are the bursts of corresponding length as described in subclause 5B.3.2. + +Each 10 ms frame consists of 15 time slots, each allocated to either the uplink or the downlink (figure 18AB). With such a flexibility, the TDD mode can be adapted to different environments and deployment scenarios. In any configuration at least one time slot has to be allocated for the downlink and at least one time slot has to be allocated for the uplink with the exception of no uplink timeslots when the entire carrier is dedicated to MBSFN. + +![Figure 18AB: The TDD frame structure. The diagram shows a 10ms frame divided into 15 time slots. Each slot contains a pair of arrows pointing in opposite directions, representing uplink and downlink traffic. The total duration of the frame is 10ms. The chip rate is 7.68Mcps. The duration of one time slot is 5120 * Tc.](e354b57563dae469c00b412b2abdf765_img.jpg) + +The diagram illustrates the TDD frame structure. A horizontal axis represents time, and a vertical axis represents frequency. A 10ms frame is shown, divided into 15 time slots. Each slot contains a vertical double-headed arrow. The total duration of the frame is 10ms. The chip rate is 7.68Mcps. The duration of one time slot is $5120 * T_c$ . + +Figure 18AB: The TDD frame structure. The diagram shows a 10ms frame divided into 15 time slots. Each slot contains a pair of arrows pointing in opposite directions, representing uplink and downlink traffic. The total duration of the frame is 10ms. The chip rate is 7.68Mcps. The duration of one time slot is 5120 \* Tc. + +**Figure 18AB: The TDD frame structure** + +Examples for multiple and single switching point configurations as well as for symmetric and asymmetric UL/DL allocations are given in figure 3. + +## 5B.3 Dedicated physical channel (DPCH) + +The DCH as described in subclause 4.1.1 is mapped onto the dedicated physical channel. + +### 5B.3.1 Spreading + +Spreading is applied to the data part of the physical channels and consists of two operations. The first is the channelisation operation, which transforms every data symbol into a number of chips, thus increasing the bandwidth of the signal. The number of chips per data symbol is called the Spreading Factor (SF). The second operation is the scrambling operation, where a scrambling code is applied to the spread signal. Details on channelisation and scrambling operation can be found in [8]. + +#### 5B.3.1.1 Spreading for Downlink Physical Channels + +Downlink physical channels shall use SF=32 or SF=1. + +Multiple parallel physical channels can be used to support higher data rates. Within a timeslot, parallel physical channels shall be transmitted using different channelisation codes, see [8]. These codes with SF =32 are generated as described in [8]. + +#### 5B.3.1.2 Spreading for Uplink Physical Channels + +The range of spreading factors that may be used for uplink physical channels shall range from 32 down to 1. For each physical channel an individual minimum spreading factor $SF_{min}$ is transmitted by means of the higher layers. There are two options that are indicated by UTRAN: + +1. The UE shall use the spreading factor $SF_{min}$ , independent of the current TFC. +2. The UE shall autonomously increase the spreading factor depending on the current TFC. + +If the UE autonomously changes the SF, it shall always vary the channelisation code along the branch with the higher code numbering of the allowed OVSF sub tree, as depicted in [8]. In the event that code hopping is configured by higher layers, the allowed OVSF sub-tree is that subtended by the effective allocated OVSF code after the hop sequence has been applied to the allocated OVSF code (see [9]). + +For multicode transmission a UE shall use a maximum of two physical channels per timeslot simultaneously. These two parallel physical channels shall be transmitted using different channelisation codes, see [8]. + +### 5B.3.2 Burst Types + +Four types of bursts are defined. All of them consist of two data symbol fields, a midamble and a guard period, the lengths of which are different for the individual burst types. Thus, the number of data symbols in a burst depends on the SF and the burst type, as depicted in table 8AA. + +**Table 8AA: Number of data symbols (N) for burst type 1, 2, 3 and 4** + +| Spreading factor (SF) | Burst Type 1 | Burst Type 2 | Burst Type 3 | Burst Type 4 | +|-----------------------|--------------|--------------|--------------|--------------| +| 1 | 3904 | 4416 | 3712 | 4224 | +| 2 | 1952 | 2208 | 1856 | N/A | +| 4 | 976 | 1104 | 928 | N/A | +| 8 | 488 | 552 | 464 | N/A | +| 16 | 244 | 276 | 232 | N/A | +| 32 | 122 | 138 | 116 | 132 | + +The support of burst types 1, 2 and 3 is mandatory for UEs supporting transmit and receive functions. UEs supporting transmit and receive functions and also MBSFN operation must additionally support burst type 4. UEs with receive only capability need only support burst type 4.. The three different bursts defined here are well suited for different applications, as described in the following sections. + +#### 5B.3.2.1 Burst Type 1 + +Burst type 1 can be used for uplink and downlink. Due to its longer midamble field this burst type supports the construction of a larger number of training sequences. The maximum number of training sequences depends on the cell configuration. For burst type 1 this number may be 4, 8, or 16. + +The data fields of burst type 1 are 1952 chips long. The corresponding number of symbols depends on the spreading factor, as indicated in table 8AA above. The midamble of burst type 1 has a length of 1024 chips. The guard period for the burst type 1 is 192 chip periods long. Burst type 1 is shown in Figure 18AC. The contents of the burst fields are described in table 8AB. + +**Table 8AB: The contents of burst type 1 fields** + +| Chip number (CN) | Length of field in chips | Length of field in symbols | | Contents of field | +|------------------|--------------------------|----------------------------|--|-------------------| +| 0-1951 | 1952 | Cf table 8AA | | Data symbols | +| 1952-2975 | 1024 | - | | Midamble | +| 2976-4927 | 1952 | Cf table 8AA | | Data symbols | +| 4928-5119 | 192 | - | | Guard period | + +![Diagram of Burst Type 1 structure showing four fields: Data symbols (1952 chips), Midamble (1024 chips), Data symbols (1952 chips), and GP (192 CP). The total length is 5120 * Tc.](1c140ee5d1a87186977da94a96bfa700_img.jpg) + +| | | | | +|----------------------------|------------------------|----------------------------|-----------------| +| Data symbols
1952 chips | Midamble
1024 chips | Data symbols
1952 chips | GP
192
CP | +|----------------------------|------------------------|----------------------------|-----------------| + +5120 \* Tc + +Diagram of Burst Type 1 structure showing four fields: Data symbols (1952 chips), Midamble (1024 chips), Data symbols (1952 chips), and GP (192 CP). The total length is 5120 \* Tc. + +**Figure 18AC: Burst structure of burst type 1. GP denotes the guard period and CP the chip periods** + +#### 5B.3.2.2 Burst Type 2 + +Burst type 2 can be used for uplink and downlink. It offers a longer data field than burst type 1 at the cost of a shorter midamble. Due to the shorter midamble field the burst type 2 supports a maximum number of training sequences of 4 or 8 only, depending on the cell configuration. + +The data fields of the burst type 2 are 2208 chips long. The corresponding number of symbols depends on the spreading factor, as indicated in table 8AA above. The guard period for the burst type 2 is 192 chip periods long. Burst type 2 is shown in Figure 18AD. The contents of the burst fields are described in table 8AC. + +Table 8AC: The contents of burst type 2 fields + +| Chip number (CN) | Length of field in chips | Length of field in symbols | | Contents of field | +|------------------|--------------------------|----------------------------|--|-------------------| +| 0-2207 | 2208 | cf table 8AA | | Data symbols | +| 2208-2719 | 512 | - | | Midamble | +| 2720-4927 | 2208 | cf table 8AA | | Data symbols | +| 4928-5119 | 192 | - | | Guard period | + +![Figure 18AD: Burst structure of the burst type 2. The diagram shows a horizontal bar divided into four segments: 'Data symbols 2208 chips', 'Midamble 512 chips', 'Data symbols 2208 chips', and 'GP 192 CP'. Below the bar, a double-headed arrow indicates a total length of 5120 * T_c.](4cde160bcc69b7b6c81b648dd0e4252e_img.jpg) + +Figure 18AD: Burst structure of the burst type 2. The diagram shows a horizontal bar divided into four segments: 'Data symbols 2208 chips', 'Midamble 512 chips', 'Data symbols 2208 chips', and 'GP 192 CP'. Below the bar, a double-headed arrow indicates a total length of 5120 \* T\_c. + +Figure 18AD: Burst structure of the burst type 2. GP denotes the guard period and CP the chip periods + +#### 5B.3.2.3 Burst Type 3 + +Burst type 3 is used for uplink only. Due to the longer guard period it is suitable for initial access or access to a new cell after handover. It offers the same number of training sequences as burst type 1. + +The data fields of the burst type 3 have a length of 1952 chips and 1760 chips, respectively. The corresponding number of symbols depends on the spreading factor, as indicated in table 8AA above. The midamble of burst type 3 has a length of 1024 chips. The guard period for the burst type 3 is 384 chip periods long. Burst type 3 is shown in Figure 18AE. The contents of the burst fields are described in table 8AD. + +Table 8AD: The contents of burst type 3 fields + +| Chip number (CN) | Length of field in chips | Length of field in symbols | | Contents of field | +|------------------|--------------------------|----------------------------|--|-------------------| +| 0-1951 | 1952 | Cf table 8AA | | Data symbols | +| 1952-2975 | 1024 | - | | Midamble | +| 2976-4735 | 1760 | Cf table 8AA | | Data symbols | +| 4736-5119 | 384 | - | | Guard period | + +![Figure 18AE: Burst structure of the burst type 3. The diagram shows a horizontal bar divided into four segments: 'Data symbols 1952 chips', 'Midamble 1024 chips', 'Data symbols 1760 chips', and 'GP 384 CP'. Below the bar, a double-headed arrow indicates a total length of 5120 * T_c.](6929132b4964d52244da61d4614bc4d6_img.jpg) + +Figure 18AE: Burst structure of the burst type 3. The diagram shows a horizontal bar divided into four segments: 'Data symbols 1952 chips', 'Midamble 1024 chips', 'Data symbols 1760 chips', and 'GP 384 CP'. Below the bar, a double-headed arrow indicates a total length of 5120 \* T\_c. + +Figure 18AE: Burst structure of the burst type 3. GP denotes the guard period and CP the chip periods + +#### 5B.3.2.3A Burst Type 4 + +The burst type 4 is used for downlink MBSFN operation only and supports a single training sequence. + +The data fields of the burst type 4 are 2112 chips long. The corresponding number of symbols is 132 as indicated in table 8AA above. The midamble of burst type 4 has a length of 640 chips. The guard period for the burst type 4 is 256 chip periods long. The burst type 4 is shown in Figure 18AEA. The contents of the burst fields are described in table 8ADA. + +Table 8ADA: The contents of burst type 4 fields + +| Chip number (CN) | Length of field in chips | Length of field in symbols | | Contents of field | +|------------------|--------------------------|----------------------------|--|-------------------| +| 0-2111 | 2112 | Cf table 8AA | | Data symbols | +| 2112-2751 | 640 | - | | Midamble | +| 2752-4863 | 2112 | Cf table 8AA | | Data symbols | +| 4864-5119 | 256 | - | | Guard period | + +![Figure 18AEA: Burst structure of the burst type 4. The diagram shows a horizontal bar divided into four segments: Data symbols (2112 chips), Midamble (640 chips), Data symbols (2112 chips), and GP (256 CP). A double-headed arrow below the bar indicates a total length of 5120*Tc.](759c7d62402f0b4651ddce292be5bdef_img.jpg) + +Figure 18AEA: Burst structure of the burst type 4. The diagram shows a horizontal bar divided into four segments: Data symbols (2112 chips), Midamble (640 chips), Data symbols (2112 chips), and GP (256 CP). A double-headed arrow below the bar indicates a total length of 5120\*Tc. + +Figure 18AEA: Burst structure of the burst type 4. GP denotes the guard period and CP the chip periods + +#### 5B.3.2.4 Transmission of TFCI + +All burst types 1, 2, 3 and 4 provide the possibility for transmission of TFCI. + +The transmission of TFCI is negotiated at call setup and can be re-negotiated during the call. For each CCTrCH it is indicated by higher layer signalling, which TFCI format is applied, except for the MBSFN FACH where the (16,5) bi-orthogonal code is always used for TFCI when TFCI is applied. Additionally for each allocated timeslot it is signalled individually whether that timeslot carries the TFCI or not. The TFCI is always present in the first timeslot in a radio frame for each CCTrCH. If a time slot contains the TFCI, then it is always transmitted using the physical channel with the lowest physical channel sequence number (*p*) in that timeslot. Physical channel sequence numbering is determined by the rate matching function and is described in [7]. + +The transmission of TFCI is done in the data parts of the respective physical channel. In DL the TFCI code word bits and data bits are subject to the same spreading procedure as depicted in [8]. In DL, the modulation applied to the TFCI code word bits is the same as that applied to the data symbols. In UL, independent of the SF that is applied to the data symbols in the burst, the data in the TFCI field are always spread with SF=32 using the channelisation code in the branch with the highest code numbering of the allowed OVSF sub tree, as depicted in [8]. Hence the midamble structure and length is not changed. The TFCI code word is to be transmitted directly adjacent to the midamble, possibly after the TPC. Figure 18AF shows the position of the TFCI code word in a traffic burst in downlink. Figure 18AG shows the position of the TFCI code word in a traffic burst in uplink. + +![Figure 18AF: Position of the TFCI code word in the traffic burst in case of downlink. The diagram shows a horizontal bar with segments: Data symbols, Midamble, Data symbols, and GP. The TFCI code word is split into two parts: the 1st part is adjacent to the first Data symbols segment, and the 2nd part is adjacent to the second Data symbols segment. A double-headed arrow below the Midamble segment indicates a length of 1024/512 chips. A larger double-headed arrow below the entire bar indicates a total length of 5120*Tc.](68ea9310fb829dd6007635a6cd4ea2ad_img.jpg) + +Figure 18AF: Position of the TFCI code word in the traffic burst in case of downlink. The diagram shows a horizontal bar with segments: Data symbols, Midamble, Data symbols, and GP. The TFCI code word is split into two parts: the 1st part is adjacent to the first Data symbols segment, and the 2nd part is adjacent to the second Data symbols segment. A double-headed arrow below the Midamble segment indicates a length of 1024/512 chips. A larger double-headed arrow below the entire bar indicates a total length of 5120\*Tc. + +Figure 18AF: Position of the TFCI code word in the traffic burst in case of downlink + +![Figure 18AG: Position of the TFCI code word in the traffic burst in case of uplink. The diagram shows a traffic burst structure with fields: Data symbols, Midamble, TPC, Data symbols, and GP. The 1st part of the TFCI code word is located within the Midamble, and the 2nd part is located in the TPC field. The Midamble length is 1024/512 chips. The total burst length is 5120*T_c.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +Diagram illustrating the position of the TFCI code word in the traffic burst in case of uplink. The burst structure consists of Data symbols, Midamble, TPC, Data symbols, and GP. The 1st part of the TFCI code word is located within the Midamble, and the 2nd part is located in the TPC field. The Midamble length is 1024/512 chips. The total burst length is 5120\*Tc. + +Figure 18AG: Position of the TFCI code word in the traffic burst in case of uplink. The diagram shows a traffic burst structure with fields: Data symbols, Midamble, TPC, Data symbols, and GP. The 1st part of the TFCI code word is located within the Midamble, and the 2nd part is located in the TPC field. The Midamble length is 1024/512 chips. The total burst length is 5120\*T\_c. + +**Figure 18AG: Position of the TFCI code word in the traffic burst in case of uplink** + +Two examples of TFCI transmission in the case of multiple DPCHs used for a connection are given in the Figure 18AH and Figure 18AI below. Combinations of the two schemes shown are also applicable. + +![Figure 18AH: Example of TFCI transmission with physical channels multiplexed in code domain. The diagram shows a grid of codes over time. The vertical axis is labeled 'Code' and the horizontal axis is labeled 't'. A legend indicates Data (white), Midamble (light gray), and TFCI (dark gray). The TFCI is shown as a small dark gray block within the Data symbols.](f0a97d0d3818a253c1d2a009966081b1_img.jpg) + +Diagram illustrating the position of the TFCI code word in the traffic burst in case of uplink. The burst structure consists of Data symbols, Midamble, TPC, Data symbols, and GP. The 1st part of the TFCI code word is located within the Midamble, and the 2nd part is located in the TPC field. The Midamble length is 1024/512 chips. The total burst length is 5120\*Tc. + +Figure 18AH: Example of TFCI transmission with physical channels multiplexed in code domain. The diagram shows a grid of codes over time. The vertical axis is labeled 'Code' and the horizontal axis is labeled 't'. A legend indicates Data (white), Midamble (light gray), and TFCI (dark gray). The TFCI is shown as a small dark gray block within the Data symbols. + +**Figure 18AH: Example of TFCI transmission with physical channels multiplexed in code domain** + +![Figure 18AI: Example of TFCI transmission with physical channels multiplexed in time domain. The diagram shows a sequence of time slots. The vertical axis is labeled 'Code' and the horizontal axis is labeled 't'. A legend indicates Data (white), Midamble (light gray), and TFCI (dark gray). The TFCI is shown as a small dark gray block within the Data symbols.](f2ea0f64a770b22b902820457d262265_img.jpg) + +Diagram illustrating the position of the TFCI code word in the traffic burst in case of uplink. The burst structure consists of Data symbols, Midamble, TPC, Data symbols, and GP. The 1st part of the TFCI code word is located within the Midamble, and the 2nd part is located in the TPC field. The Midamble length is 1024/512 chips. The total burst length is 5120\*Tc. + +Figure 18AI: Example of TFCI transmission with physical channels multiplexed in time domain. The diagram shows a sequence of time slots. The vertical axis is labeled 'Code' and the horizontal axis is labeled 't'. A legend indicates Data (white), Midamble (light gray), and TFCI (dark gray). The TFCI is shown as a small dark gray block within the Data symbols. + +**Figure 18AI: Example of TFCI transmission with physical channels multiplexed in time domain** + +#### 5B.3.2.5 Transmission of TPC + +Burst types 1, 2 and 3 for dedicated and shared channels provide the possibility for transmission of TPC in uplink. + +The transmission of TPC is done in the data parts of the traffic burst. Independent of the SF that is applied to the data symbols in the burst, the data in the TPC field are always spread with SF=32 using the channelisation code in the branch with the highest code numbering of the allowed OVSF sub tree, as depicted in [8]. Hence the midamble structure and length is not changed. The TPC information is to be transmitted directly after the midamble. Figure 18AJ shows the position of the TPC in a traffic burst. + +For every user the TPC information shall be transmitted at least once per transmitted frame. If a TFCI is applied for a CCTrCH, TPC shall be transmitted with the same channelization codes and in the same timeslots as the TFCI. If no TFCI is applied for a CCTrCH, TPC shall be transmitted using the physical channel corresponding to physical channel sequence number $p=1$ . Physical channel sequence numbering is determined by the rate matching function and is described in [7]. + +![Diagram showing the position of the TPC field in a traffic burst. The burst consists of Data symbols, a Midamble, a TPC field (shaded), Data symbols, and a GP. The Midamble length is 1024/512 chips. The total burst length is 5120 * Tc.](744acfe8d4e31bcf03f95714c2f6e567_img.jpg) + +The diagram illustrates the structure of a traffic burst. It is a horizontal bar divided into five segments: 'Data symbols', 'Midamble', 'TPC field' (indicated by a shaded box), 'Data symbols', and 'GP'. A double-headed arrow below the 'Midamble' segment is labeled '1024/512 chips'. A longer double-headed arrow below the entire bar is labeled '5120\*Tc'. A line points from the label 'TPC field' to the shaded box. + +Diagram showing the position of the TPC field in a traffic burst. The burst consists of Data symbols, a Midamble, a TPC field (shaded), Data symbols, and a GP. The Midamble length is 1024/512 chips. The total burst length is 5120 \* Tc. + +**Figure 18AJ: Position of TPC information in the traffic burst** + +The length of the TPC field is $N_{TPC}$ bits. The TPC field is formed via repetition encoding a single bit $b_{TPC}$ , $N_{TPC}$ times. + +The relationship between $b_{TPC}$ and the TPC command is shown in table 8AE. + +**Table 8AE: TPC bit pattern** + +| $b_{TPC}$ | TPC command | Meaning | +|-----------|-------------|-------------------| +| 0 | 'Down' | Decrease Tx Power | +| 1 | 'Up' | Increase Tx Power | + +#### 5B.3.2.6 Timeslot formats + +##### 5B.3.2.6.1 Downlink timeslot formats + +The downlink timeslot format depends on the spreading factor, midamble length and on the number of TFCI code word bits, as depicted in the table 8AF. For MBSFN operation the timeslot format also depends upon the symbol modulation scheme used. Slot formats 20-27 are only applicable to MBSFN operation with burst type 4. + +**Table 8AF: Time slot formats for the Downlink** + +| Slot Format # | Spreading Factor | Midamble length (chips) | $N_{TFCI}$ code word (bits) | Bits/slot | $N_{Data/Slot}$ (bits) | $N_{data/data field}$ (bits) | +|---------------|------------------|-------------------------|-----------------------------|-----------|------------------------|------------------------------| +| 0 | 32 | 1024 | 0 | 244 | 244 | 122 | +| 1 | 32 | 1024 | 4 | 244 | 240 | 120 | +| 2 | 32 | 1024 | 8 | 244 | 236 | 118 | +| 3 | 32 | 1024 | 16 | 244 | 228 | 114 | +| 4 | 32 | 1024 | 32 | 244 | 212 | 106 | +| 5 | 32 | 512 | 0 | 276 | 276 | 138 | +| 6 | 32 | 512 | 4 | 276 | 272 | 136 | +| 7 | 32 | 512 | 8 | 276 | 268 | 134 | +| 8 | 32 | 512 | 16 | 276 | 260 | 130 | +| 9 | 32 | 512 | 32 | 276 | 244 | 122 | +| 10 | 1 | 1024 | 0 | 7808 | 7808 | 3904 | +| 11 | 1 | 1024 | 4 | 7808 | 7804 | 3902 | +| 12 | 1 | 1024 | 8 | 7808 | 7800 | 3900 | +| 13 | 1 | 1024 | 16 | 7808 | 7792 | 3896 | +| 14 | 1 | 1024 | 32 | 7808 | 7776 | 3888 | +| 15 | 1 | 512 | 0 | 8832 | 8832 | 4416 | +| 16 | 1 | 512 | 4 | 8832 | 8828 | 4414 | + +| Slot Format # | Spreading Factor | Midamble length (chips) | N TFCI code word (bits) | Bits/slot | N Data/Slot (bits) | N data/data field (bits) | +|---------------|------------------|-------------------------|------------------------------------|-----------|-------------------------------|-------------------------------------| +| 17 | 1 | 512 | 8 | 8832 | 8824 | 4412 | +| 18 | 1 | 512 | 16 | 8832 | 8816 | 4408 | +| 19 | 1 | 512 | 32 | 8832 | 8800 | 4400 | +| 20 (QPSK) | 32 | 640 | 0 | 264 | 264 | 132 | +| 21 (QPSK) | 32 | 640 | 16 | 264 | 248 | 124 | +| 22 (16QAM) | 32 | 640 | 0 | 528 | 528 | 264 | +| 23 (16QAM) | 32 | 640 | 16 | 528 | 512 | 256 | +| 24 (QPSK) | 1 | 640 | 0 | 8448 | 8448 | 4224 | +| 25 (QPSK) | 1 | 640 | 16 | 8448 | 8432 | 4216 | +| 26 (16QAM) | 1 | 640 | 0 | 16896 | 16896 | 8448 | +| 27 (16QAM) | 1 | 640 | 16 | 16896 | 16880 | 8440 | + +##### 5B.3.2.6.2 Uplink timeslot formats + +The uplink timeslot format depends on the spreading factor, midamble length, guard period length and on the number of TFCI code word bits. Due to TPC, different amount of bits are mapped to the two data fields. The timeslot formats are depicted in the table 8AG. Note that slot format #90 shall only be used for HS\_SICH. + +**Table 8AG: Time slot formats for the Uplink** + +| Slot Format # | Spreading Factor | Midamble length (chips) | Guard Period (chips) | N TFCI code word (bits) | N TPC (bits) | Bits/slot | N Data/Slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) | +|---------------|------------------|-------------------------|----------------------|------------------------------------|-------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------| +| 0 | 32 | 1024 | 192 | 0 | 0 | 244 | 244 | 122 | 122 | +| 1 | 32 | 1024 | 192 | 0 | 2 | 244 | 242 | 122 | 120 | +| 2 | 32 | 1024 | 192 | 4 | 2 | 244 | 238 | 120 | 118 | +| 3 | 32 | 1024 | 192 | 8 | 2 | 244 | 234 | 118 | 116 | +| 4 | 32 | 1024 | 192 | 16 | 2 | 244 | 226 | 114 | 112 | +| 5 | 32 | 1024 | 192 | 32 | 2 | 244 | 210 | 106 | 104 | +| 6 | 32 | 512 | 192 | 0 | 0 | 276 | 276 | 138 | 138 | +| 7 | 32 | 512 | 192 | 0 | 2 | 276 | 274 | 138 | 136 | +| 8 | 32 | 512 | 192 | 4 | 2 | 276 | 270 | 136 | 134 | +| 9 | 32 | 512 | 192 | 8 | 2 | 276 | 266 | 134 | 132 | +| 10 | 32 | 512 | 192 | 16 | 2 | 276 | 258 | 130 | 128 | +| 11 | 32 | 512 | 192 | 32 | 2 | 276 | 242 | 122 | 120 | +| 12 | 16 | 1024 | 192 | 0 | 0 | 488 | 488 | 244 | 244 | +| 13 | 16 | 1024 | 192 | 0 | 2 | 486 | 484 | 244 | 240 | +| 14 | 16 | 1024 | 192 | 4 | 2 | 482 | 476 | 240 | 236 | +| 15 | 16 | 1024 | 192 | 8 | 2 | 478 | 468 | 236 | 232 | +| 16 | 16 | 1024 | 192 | 16 | 2 | 470 | 452 | 228 | 224 | +| 17 | 16 | 1024 | 192 | 32 | 2 | 454 | 420 | 212 | 208 | +| 18 | 16 | 512 | 192 | 0 | 0 | 552 | 552 | 276 | 276 | +| 19 | 16 | 512 | 192 | 0 | 2 | 550 | 548 | 276 | 272 | +| 20 | 16 | 512 | 192 | 4 | 2 | 546 | 540 | 272 | 268 | +| 21 | 16 | 512 | 192 | 8 | 2 | 542 | 532 | 268 | 264 | +| 22 | 16 | 512 | 192 | 16 | 2 | 534 | 516 | 260 | 256 | +| 23 | 16 | 512 | 192 | 32 | 2 | 518 | 484 | 244 | 240 | +| 24 | 8 | 1024 | 192 | 0 | 0 | 976 | 976 | 488 | 488 | +| 25 | 8 | 1024 | 192 | 0 | 2 | 970 | 968 | 488 | 480 | +| 26 | 8 | 1024 | 192 | 4 | 2 | 958 | 952 | 480 | 472 | +| 27 | 8 | 1024 | 192 | 8 | 2 | 946 | 936 | 472 | 464 | + +| Slot Format # | Spreading Factor | Midamble length (chips) | Guard Period (chips) | N TFCI code word (bits) | N TPC (bits) | Bits/slot | N Data/Slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) | +|---------------|------------------|-------------------------|----------------------|------------------------------------|-------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------| +| 28 | 8 | 1024 | 192 | 16 | 2 | 922 | 904 | 456 | 448 | +| 29 | 8 | 1024 | 192 | 32 | 2 | 874 | 840 | 424 | 416 | +| 30 | 8 | 512 | 192 | 0 | 0 | 1104 | 1104 | 552 | 552 | +| 31 | 8 | 512 | 192 | 0 | 2 | 1098 | 1096 | 552 | 544 | +| 32 | 8 | 512 | 192 | 4 | 2 | 1086 | 1080 | 544 | 536 | +| 33 | 8 | 512 | 192 | 8 | 2 | 1074 | 1064 | 536 | 528 | +| 34 | 8 | 512 | 192 | 16 | 2 | 1050 | 1032 | 520 | 512 | +| 35 | 8 | 512 | 192 | 32 | 2 | 1002 | 968 | 488 | 480 | +| 36 | 4 | 1024 | 192 | 0 | 0 | 1952 | 1952 | 976 | 976 | +| 37 | 4 | 1024 | 192 | 0 | 2 | 1938 | 1936 | 976 | 960 | +| 38 | 4 | 1024 | 192 | 4 | 2 | 1910 | 1904 | 960 | 944 | +| 39 | 4 | 1024 | 192 | 8 | 2 | 1882 | 1872 | 944 | 928 | +| 40 | 4 | 1024 | 192 | 16 | 2 | 1826 | 1808 | 912 | 896 | +| 41 | 4 | 1024 | 192 | 32 | 2 | 1714 | 1680 | 848 | 832 | +| 42 | 4 | 512 | 192 | 0 | 0 | 2208 | 2208 | 1104 | 1104 | +| 43 | 4 | 512 | 192 | 0 | 2 | 2194 | 2192 | 1104 | 1088 | +| 44 | 4 | 512 | 192 | 4 | 2 | 2166 | 2160 | 1088 | 1072 | +| 45 | 4 | 512 | 192 | 8 | 2 | 2138 | 2128 | 1072 | 1056 | +| 46 | 4 | 512 | 192 | 16 | 2 | 2082 | 2064 | 1040 | 1024 | +| 47 | 4 | 512 | 192 | 32 | 2 | 1970 | 1936 | 976 | 960 | +| 48 | 2 | 1024 | 192 | 0 | 0 | 3904 | 3904 | 1952 | 1952 | +| 49 | 2 | 1024 | 192 | 0 | 2 | 3874 | 3872 | 1952 | 1920 | +| 50 | 2 | 1024 | 192 | 4 | 2 | 3814 | 3808 | 1920 | 1888 | +| 51 | 2 | 1024 | 192 | 8 | 2 | 3754 | 3744 | 1888 | 1856 | +| 52 | 2 | 1024 | 192 | 16 | 2 | 3634 | 3616 | 1824 | 1792 | +| 53 | 2 | 1024 | 192 | 32 | 2 | 3394 | 3360 | 1696 | 1664 | +| 54 | 2 | 512 | 192 | 0 | 0 | 4416 | 4416 | 2208 | 2208 | +| 55 | 2 | 512 | 192 | 0 | 2 | 4386 | 4384 | 2208 | 2176 | +| 56 | 2 | 512 | 192 | 4 | 2 | 4326 | 4320 | 2176 | 2144 | +| 57 | 2 | 512 | 192 | 8 | 2 | 4266 | 4256 | 2144 | 2112 | +| 58 | 2 | 512 | 192 | 16 | 2 | 4146 | 4128 | 2080 | 2048 | +| 59 | 2 | 512 | 192 | 32 | 2 | 3906 | 3872 | 1952 | 1920 | +| 59a | 1 | 1024 | 192 | 0 | 0 | 7808 | 7808 | 3904 | 3904 | +| 59b | 1 | 1024 | 192 | 0 | 2 | 7746 | 7744 | 3904 | 3840 | +| 59c | 1 | 1024 | 192 | 4 | 2 | 7622 | 7616 | 3840 | 3776 | +| 59d | 1 | 1024 | 192 | 8 | 2 | 7498 | 7488 | 3776 | 3712 | +| 59e | 1 | 1024 | 192 | 16 | 2 | 7250 | 7232 | 3648 | 3584 | +| 59f | 1 | 1024 | 192 | 32 | 2 | 6754 | 6720 | 3392 | 3328 | +| 59g | 1 | 512 | 192 | 0 | 0 | 8832 | 8832 | 4416 | 4416 | +| 59h | 1 | 512 | 192 | 0 | 2 | 8770 | 8768 | 4416 | 4352 | +| 59i | 1 | 512 | 192 | 4 | 2 | 8646 | 8640 | 4352 | 4288 | +| 59j | 1 | 512 | 192 | 8 | 2 | 8522 | 8512 | 4288 | 4224 | +| 59k | 1 | 512 | 192 | 16 | 2 | 8274 | 8256 | 4160 | 4096 | +| 59l | 1 | 512 | 192 | 32 | 2 | 7778 | 7744 | 3904 | 3840 | +| 60 | 32 | 1024 | 384 | 0 | 0 | 232 | 232 | 122 | 110 | +| 61 | 32 | 1024 | 384 | 0 | 2 | 232 | 230 | 122 | 108 | +| 62 | 32 | 1024 | 384 | 4 | 2 | 232 | 226 | 120 | 106 | +| 63 | 32 | 1024 | 384 | 8 | 2 | 232 | 222 | 118 | 104 | +| 64 | 32 | 1024 | 384 | 16 | 2 | 232 | 214 | 114 | 100 | +| 65 | 32 | 1024 | 384 | 32 | 2 | 232 | 198 | 106 | 92 | + +| Slot Format # | Spreading Factor | Midamble length (chips) | Guard Period (chips) | N TFCI code word (bits) | N TPC (bits) | Bits/slot | N Data/Slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) | +|---------------|------------------|-------------------------|----------------------|------------------------------------|-------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------| +| 66 | 16 | 1024 | 384 | 0 | 0 | 464 | 464 | 244 | 220 | +| 67 | 16 | 1024 | 384 | 0 | 2 | 462 | 460 | 244 | 216 | +| 68 | 16 | 1024 | 384 | 4 | 2 | 458 | 452 | 240 | 212 | +| 69 | 16 | 1024 | 384 | 8 | 2 | 454 | 444 | 236 | 208 | +| 70 | 16 | 1024 | 384 | 16 | 2 | 446 | 428 | 228 | 200 | +| 71 | 16 | 1024 | 384 | 32 | 2 | 430 | 396 | 212 | 184 | +| 72 | 8 | 1024 | 384 | 0 | 0 | 928 | 928 | 488 | 440 | +| 73 | 8 | 1024 | 384 | 0 | 2 | 922 | 920 | 488 | 432 | +| 74 | 8 | 1024 | 384 | 4 | 2 | 910 | 904 | 480 | 424 | +| 75 | 8 | 1024 | 384 | 8 | 2 | 898 | 888 | 472 | 416 | +| 76 | 8 | 1024 | 384 | 16 | 2 | 874 | 856 | 456 | 400 | +| 77 | 8 | 1024 | 384 | 32 | 2 | 826 | 792 | 424 | 368 | +| 78 | 4 | 1024 | 384 | 0 | 0 | 1856 | 1856 | 976 | 880 | +| 79 | 4 | 1024 | 384 | 0 | 2 | 1842 | 1840 | 976 | 864 | +| 80 | 4 | 1024 | 384 | 4 | 2 | 1814 | 1808 | 960 | 848 | +| 81 | 4 | 1024 | 384 | 8 | 2 | 1786 | 1776 | 944 | 832 | +| 82 | 4 | 1024 | 384 | 16 | 2 | 1730 | 1712 | 912 | 800 | +| 83 | 4 | 1024 | 384 | 32 | 2 | 1618 | 1584 | 848 | 736 | +| 84 | 2 | 1024 | 384 | 0 | 0 | 3712 | 3712 | 1952 | 1760 | +| 85 | 2 | 1024 | 384 | 0 | 2 | 3682 | 3680 | 1952 | 1728 | +| 86 | 2 | 1024 | 384 | 4 | 2 | 3622 | 3616 | 1920 | 1696 | +| 87 | 2 | 1024 | 384 | 8 | 2 | 3562 | 3552 | 1888 | 1664 | +| 88 | 2 | 1024 | 384 | 16 | 2 | 3442 | 3424 | 1824 | 1600 | +| 89 | 2 | 1024 | 384 | 32 | 2 | 3202 | 3168 | 1696 | 1472 | +| 89a | 1 | 1024 | 384 | 0 | 0 | 7424 | 7424 | 3904 | 3520 | +| 89b | 1 | 1024 | 384 | 0 | 2 | 7362 | 7360 | 3904 | 3456 | +| 89c | 1 | 1024 | 384 | 4 | 2 | 7238 | 7232 | 3840 | 3392 | +| 89d | 1 | 1024 | 384 | 8 | 2 | 7114 | 7104 | 3776 | 3328 | +| 89e | 1 | 1024 | 384 | 16 | 2 | 6866 | 6848 | 3648 | 3200 | +| 89f | 1 | 1024 | 384 | 32 | 2 | 6370 | 6336 | 3392 | 2944 | +| 90 | 32 | 1024 | 192 | 0 | 8 | 244 | 236 | 122 | 114 | + +### 5B.3.3 Training sequences for spread bursts + +In this subclause, the training sequences for usage as midambles in burst type 1, 2, 3 and 4 (see subclause 5B.3.2) are defined. The training sequences, i.e. midambles, of different users active in the same cell and same time slot are cyclically shifted versions of one cell-specific single basic midamble code. In the case of MBSFN timeslots there is only a single midamble and this is derived from a single basic midamble code which is not necessarily cell-specific. The applicable basic midamble codes are given in Annex AB.1, Annex AB.2 and Annex AB.2A. As different basic midamble codes are required for different burst formats, Annex AB.1 shows the basic midamble codes $\mathbf{m}_p$ for burst type 1 and 3, Annex AB.2 shows $\mathbf{m}_{ps}$ for burst type 2 and Annex AB.2A shows $\mathbf{m}_p$ for burst type 4. It should be noted that burst type 2 must not be mixed with burst type 1 or 3 in the same timeslot of one cell and furthermore burst type 4 shall not be mixed with any other burst type in the same timeslot of one cell. + +The basic midamble codes in Annex AB.1, Annex AB.2 and Annex AB.2A are listed in hexadecimal notation. The binary form of the basic midamble code shall be derived according to table 6 (section 5.2.3). + +For each particular basic midamble code, its binary representation can be written as a vector $\mathbf{m}_p$ : + +$$\mathbf{m}_p = (m_1, m_2, \dots, m_{p_p}) \quad (1)$$ + +According to Annex AB.1, the size of this vector $\underline{m}^P$ is $P=912$ for burst type 1 and 3. According to Annex AB.2, the size of this vector $\underline{m}^P$ is $P=456$ for burst type 2. According to Annex AB.2A, the size of vector $\underline{m}^P$ is $P=384$ for burst type 4. As QPSK modulation is used, the training sequences are transformed into a complex form, denoted as the complex vector $\underline{m}^P$ : + +$$\underline{m}^P = (\underline{m}_1, \underline{m}_2, \dots, \underline{m}_P) \quad (2)$$ + +The elements $\underline{m}_i$ of $\underline{m}^P$ are derived from elements $m_i$ of $\underline{m}^P$ using equation (3): + +$$\underline{m}_i = (j)^i \cdot m_i \text{ for all } i = 1, \dots, P \quad (3)$$ + +Hence, the elements $\underline{m}_i$ of the complex basic midamble code are alternating real and imaginary. + +To derive the required training sequences (different shifts), this vector $\underline{m}^P$ is periodically extended to the size: + +$$i_{\max} = L_m + (K' - 1)W + \lfloor P/K \rfloor \quad (4)$$ + +Notes on equation (4): + +- $L_m$ : Midamble length +- $K'$ : Maximum number of different midamble shifts in a cell, when no intermediate shifts are used. This value depends on the midamble length. +- $K$ : Maximum number of different midamble shifts in a cell, when intermediate shifts are used, $K=2K'$ . This value depends on the midamble length. + +Note that intermediate shifts are not used for burst type 4, i.e. $K=K'=1$ for burst type 4. + +- $W$ : Shift between the midambles, when the number of midambles is $K'$ . +- $\lfloor x \rfloor$ denotes the largest integer smaller or equal to $x$ + +Allowed values for $L_m$ , $K'$ and $W$ are given in Annex AB.1, Annex AB.2 and Annex AB.2A. + +So we obtain a new vector $\underline{m}$ containing the periodic basic midamble sequence: + +$$\underline{m} = (\underline{m}_1, \underline{m}_2, \dots, \underline{m}_{i_{\max}}) = (\underline{m}_1, \underline{m}_2, \dots, \underline{m}_{L_m + (K' - 1)W + \lfloor P/K \rfloor}) \quad (5)$$ + +The first $P$ elements of this vector $\underline{m}$ are the same ones as in vector $\underline{m}^P$ , the following elements repeat the beginning: + +$$\underline{m}_i = \underline{m}_{i-P} \text{ for the subset } i = (P+1), \dots, i_{\max} \quad (6)$$ + +Using this periodic basic midamble sequence $\underline{m}$ for each shift $k$ a midamble $\underline{m}^{(k)}$ of length $L_m$ is derived, which can be written as a shift specific vector: + +$$\underline{m}^{(k)} = (\underline{m}_1^{(k)}, \underline{m}_2^{(k)}, \dots, \underline{m}_{L_m}^{(k)}) \quad (7)$$ + +The $L_m$ midamble elements $\underline{m}_i^{(k)}$ are generated for each midamble of the first $K'$ shifts ( $k = 1, \dots, K'$ ) based on: + +$$\underline{m}_i^{(k)} = \underline{m}_{i + (K' - k)W} \text{ with } i = 1, \dots, L_m \text{ and } k = 1, \dots, K' \quad (8)$$ + +The elements of midambles for the second $K'$ shifts ( $k = (K'+1), \dots, K = (K'+1), \dots, 2K'$ ) are generated based on a slight modification of this formula introducing intermediate shifts: + +$$\underline{m}_i^{(k)} = \underline{m}_{i+(K-k-1)W+\lfloor P/K \rfloor} \text{ with } i = 1, \dots, L_m \text{ and } k = K'+1, \dots, K-1 \quad (9)$$ + +$$\underline{m}_i^{(k)} = \underline{m}_{i+(K'-1)W+\lfloor P/K \rfloor} \text{ with } i = 1, \dots, L_m \text{ and } k = K \quad (10)$$ + +The number $K_{\text{Cell}}$ of midambles that is supported in each cell can be smaller than $K$ , depending on the cell size and the possible delay spreads, see Annex AB. The number $K_{\text{Cell}}$ is signalled by higher layers. The midamble sequences derived according to equations (7) to (10) have complex values and are not subject to channelisation or scrambling process, i.e. + +the elements $\underline{m}_i^{(k)}$ represent complex chips for usage in the pulse shaping process at modulation. + +The term 'a midamble code set' or 'a midamble code family' denotes $K$ specific midamble codes $\underline{m}^{(k)}$ ; $k=1, \dots, K$ , based on a single basic midamble code $\underline{m}_P$ according to (1). + +### 5B.3.4 Beamforming + +Support for beamforming is identical to 3.84Mcps TDD cf. [5.2.4 Beamforming]. + +## 5B.4 Common physical channels + +### 5B.4.1 Primary common control physical channel (P-CCPCH) + +The BCH as described in subclause 4.1.2 is mapped onto the Primary Common Control Physical Channel (P-CCPCH). The position (time slot / code) of the P-CCPCH is known from the Physical Synchronisation Channel (PSCH), see subclause 5B.4.4. + +#### 5B.4.1.1 P-CCPCH Spreading + +The P-CCPCH uses fixed spreading with a spreading factor $SF = 32$ as described in subclause 5B.3.1.1. The P-CCPCH always uses channelisation code . + +#### 5B.4.1.2 P-CCPCH Burst Types + +Burst type 1 as described in subclause 5B.2.2 is used for the P-CCPCH unless the entire carrier is dedicated to MBSFN then burst type 4 is used for P-CCPCH. No TFCI is applied for the P-CCPCH. + +#### 5B.4.1.3 P-CCPCH Training sequences + +The training sequences, i.e. midambles, as described in subclause 5B.3.3 are used for the P-CCPCH. + +### 5B.4.2 Secondary common control physical channel (S-CCPCH) + +PCH and FACH as described in subclause 4.1.2 are mapped onto one or more secondary common control physical channels (S-CCPCH). In this way the capacity of PCH and FACH can be adapted to the different requirements. + +#### 5B.4.2.1 S-CCPCH Spreading + +The S-CCPCH uses fixed spreading with a spreading factor $SF = 32$ as described in subclause 5B.3.1.1. When S-CCPCH is used for MBSFN operation the spreading factor may be $SF = 32$ or $SF = 1$ . + +#### 5B.4.2.2 S-CCPCH Burst Types + +Burst types 1, 2 or 4 as described in subclause 5B.3.2 are used for the S-CCPCHs. TFCI may be applied for S-CCPCHs. + +##### 5B.4.2.2A S-CCPCH Modulation + +When S-CCPCH is used for MBSFN operation, burst type 4 shall be used and the modulation may be QPSK or 16QAM, see table 8AF for slot formats. When S-CCPCH is used for all other purposes the modulation shall be QPSK. + +#### 5B.4.2.3 S-CCPCH Training sequences + +The training sequences, i.e. midambles, as described in subclause 5B.3.3 are used for the S-CCPCH. + +### 5B.4.3 The physical random access channel (PRACH) + +The RACH as described in subclause 4.1.2 is mapped onto one uplink physical random access channel (PRACH). + +#### 5B.4.3.1 PRACH Spreading + +The uplink PRACH uses either spreading factor $SF=32$ or $SF=16$ as described in subclause 5B.3.1.2. The set of admissible spreading codes for use on the PRACH and the associated spreading factors are broadcast on the BCH (within the RACH configuration parameters on the BCH). + +#### 5B.4.3.2 PRACH Burst Type + +The UEs send uplink access bursts of type 3 randomly in the PRACH. TFCI and TPC are not applied for the PRACH. + +#### 5B.4.3.3 PRACH Training sequences + +The training sequences, i.e. midambles, of different users active in the same time slot are time shifted versions of a basic midamble code, $m_1$ , or a second basic midamble code, $m_2$ , which is a time inverted version of the basic midamble code $m_1$ . The basic midamble codes for burst type 3 are shown in Annex AB. The necessary time shifts are obtained by choosing all $k=1,2,3,\dots,K'$ . Different cells use different periodic basic codes, i.e. different midamble sets. + +#### 5B.4.3.4 PRACH timeslot formats + +For the PRACH the timeslot format is only spreading factor dependent. The timeslot formats 60 and 66 of table 8AG are applicable for the PRACH. + +#### 5B.4.3.5 Association between Training Sequences and Channelisation Codes + +For the PRACH the fixed association between a training sequence and associated channelisation code is defined in figure 18AK. In this figure, midamble $m_j^{(k)}$ is formed from the $k^{\text{th}}$ shift of the original basic midamble code ( $j=1$ ) or of the time-inverted basic midamble code ( $j=2$ ). + +![Figure 18AK: Association of midambles to channelisation codes for PRACH in the OVSF tree. The diagram shows a hierarchical tree structure starting from a single root on the left. The tree branches out to the right, with nodes labeled with midamble identifiers (m) and channelisation codes (c). The first level of branches leads to nodes labeled m1^(1) - c16^(1), m1^(3) - c16^(2), m1^(5) - c16^(3), m1^(7) - c16^(4), m2^(1) - c16^(5), m2^(3) - c16^(6), m2^(5) - c16^(7), and m2^(7) - c16^(8). The next level of branches further splits these into nodes labeled with c32 codes, such as m1^(1) - c32^(1), m1^(2) - c32^(2), m1^(3) - c32^(3), m1^(4) - c32^(4), m1^(5) - c32^(5), m1^(6) - c32^(6), m1^(7) - c32^(7), m1^(8) - c32^(8), m2^(1) - c32^(9), m2^(2) - c32^(10), m2^(3) - c32^(11), m2^(4) - c32^(12), m2^(5) - c32^(13), m2^(6) - c32^(14), m2^(7) - c32^(15), and m2^(8) - c32^(16). The final level of branches shows some nodes ending in open brackets, indicating further potential splits.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +Figure 18AK: Association of midambles to channelisation codes for PRACH in the OVSF tree. The diagram shows a hierarchical tree structure starting from a single root on the left. The tree branches out to the right, with nodes labeled with midamble identifiers (m) and channelisation codes (c). The first level of branches leads to nodes labeled m1^(1) - c16^(1), m1^(3) - c16^(2), m1^(5) - c16^(3), m1^(7) - c16^(4), m2^(1) - c16^(5), m2^(3) - c16^(6), m2^(5) - c16^(7), and m2^(7) - c16^(8). The next level of branches further splits these into nodes labeled with c32 codes, such as m1^(1) - c32^(1), m1^(2) - c32^(2), m1^(3) - c32^(3), m1^(4) - c32^(4), m1^(5) - c32^(5), m1^(6) - c32^(6), m1^(7) - c32^(7), m1^(8) - c32^(8), m2^(1) - c32^(9), m2^(2) - c32^(10), m2^(3) - c32^(11), m2^(4) - c32^(12), m2^(5) - c32^(13), m2^(6) - c32^(14), m2^(7) - c32^(15), and m2^(8) - c32^(16). The final level of branches shows some nodes ending in open brackets, indicating further potential splits. + +Figure 18AK: Association of midambles to channelisation codes for PRACH in the OVSF tree + +### 5B.4.4 The synchronisation channel (SCH) + +The code group of a cell can be derived from the synchronisation channel. In order not to limit uplink/downlink asymmetry, the SCH is mapped on one or two downlink slots per frame only. + +There are two cases of SCH and P-CCPCH allocation as follows: + +- Case 1) SCH and P-CCPCH allocated in TS#k, k=0...14 +- Case 2) SCH allocated in two TS: TS#k and TS#k+8, k=0...6; P-CCPCH allocated in TS#k. + +The position of SCH (value of k) in the frame can change on a long term basis in any case. + +Due to this SCH scheme, the position of P-CCPCH is known from the SCH. + +Figure 18AL is an example for transmission of SCH, k=0, of Case 2. + +![Figure 18AL: Scheme for Synchronisation channel SCH. The diagram shows a frame structure at the top with 15 slots, where 1 frame = 10ms. Two slots are highlighted with a shaded pattern. Below, a zoomed-in view of a single time slot is shown, labeled 'Time slot = 5120 x Tc'. Inside the slot, there is a primary sequence block labeled C_p with a length of 512 chips. To its left is a time offset t_offset,n. Below C_p are three parallel secondary sequence blocks labeled b_1 C_{s,1}, b_2 C_{s,2}, and b_3 C_{s,3}. Vertical double-headed arrows indicate power levels: P_p for the primary sequence, P_s for the total secondary sequence power, and P_s/3 for each individual secondary sequence power.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +Figure 18AL: Scheme for Synchronisation channel SCH. The diagram shows a frame structure at the top with 15 slots, where 1 frame = 10ms. Two slots are highlighted with a shaded pattern. Below, a zoomed-in view of a single time slot is shown, labeled 'Time slot = 5120 x Tc'. Inside the slot, there is a primary sequence block labeled C\_p with a length of 512 chips. To its left is a time offset t\_offset,n. Below C\_p are three parallel secondary sequence blocks labeled b\_1 C\_{s,1}, b\_2 C\_{s,2}, and b\_3 C\_{s,3}. Vertical double-headed arrows indicate power levels: P\_p for the primary sequence, P\_s for the total secondary sequence power, and P\_s/3 for each individual secondary sequence power. + +$b_i \in \{\pm 1, \pm j\}$ , $C_{s,i} \in \{C_0, C_1, C_3, C_4, C_5, C_6, C_8, C_{10}, C_{12}, C_{13}, C_{14}, C_{15}\}$ , $i = 1, 2, 3$ ; see section 8.4 + +**Figure 18AL: Scheme for Synchronisation channel SCH consisting of one primary sequence $C_p$ and 3 parallel secondary sequences $C_{s,i}$ in slot $k$ and $k+8$ (example for $k=0$ in Case 2)** + +As depicted in figure 18AL, the SCH consists of a primary and three secondary code sequences each 512 chips long. The primary and secondary code sequences are defined in [8]. + +Due to mobile to mobile interference, it is mandatory for public TDD systems to keep synchronisation between base stations. As a consequence of this, a capture effect concerning SCH can arise. The time offset $t_{\text{offset},n}$ enables the system to overcome the capture effect. + +The time offset $t_{\text{offset},n}$ is one of 32 values, depending on the code group of the cell, $n$ , [8]. Note that the cell parameter will change from frame to frame, but the cell will belong to only one code group and thus have one time offset $t_{\text{offset},n}$ . The exact value for $t_{\text{offset},n}$ is given by: + +### 5B.4.5 Physical Uplink Shared Channel (PUSCH) + +The USCH as described in subclause 4.1.2 is mapped onto one or more physical uplink shared channels (PUSCH). Timing advance, as described in [9], is applied to the PUSCH. + +#### 5B.4.5.1 PUSCH Spreading + +The spreading factors that can be applied to the PUSCH are $SF = 1, 2, 4, 8, 16$ or $32$ as described in subclause 5B.3.1.2. + +#### 5B.4.5.2 PUSCH Burst Types + +Burst types 1, 2 or 3 as described in subclause 5B.3.2 can be used for PUSCH. TFCI and TPC can be transmitted on the PUSCH. + +#### 5B.4.5.3 PUSCH Training Sequences + +The training sequences as described in subclause 5B.3.3 are used for the PUSCH. + +#### 5B.4.5.4 UE Selection + +The UE that shall transmit on the PUSCH is selected by higher layer signalling. + +### 5B.4.6 Physical Downlink Shared Channel (PDSCH) + +The DSCH as described in subclause 4.1.2 is mapped onto one or more physical downlink shared channels (PDSCH). + +#### 5B.4.6.1 PDSCH Spreading + +The PDSCH uses either spreading factor $SF = 32$ or $SF = 1$ as described in subclause 5B.3.1.1. + +#### 5B.4.6.2 PDSCH Burst Types + +Burst types 1 or 2 as described in subclause 5B.3.2 can be used for PDSCH. TFCI can be transmitted on the PDSCH. + +#### 5B.4.6.3 PDSCH Training Sequences + +The training sequences as described in subclause 5B.3.3 are used for the PDSCH. + +#### 5B.4.6.4 UE Selection + +To indicate to the UE that there is data to decode on the DSCH, higher layer signalling is used. + +### 5B.4.7 The Paging Indicator Channel (PICH) + +The Paging Indicator Channel (PICH) is a physical channel used to carry the paging indicators. + +#### 5B.4.7.1 Mapping of Paging Indicators to the PICH bits + +Figure 18AM depicts the structure of a PICH burst and the numbering of the bits within the burst. The same burst type is used for the PICH in every cell. $N_{PIB}$ bits in a normal burst of type 1 or 2 are used to carry the paging indicators, where $N_{PIB}$ depends on the burst type: $N_{PIB}=240$ for burst type 1 and $N_{PIB}=272$ for burst type 2. The bits $s_{N_{PIB}+1}, \dots, s_{N_{PIB}+4}$ adjacent to the midamble are reserved for possible future use. + +![Diagram of a PICH burst structure within a 1 Time Slot. The burst is divided into three main sections: 'Bits for Page Indication' (left), 'Reserved Bits' (middle), and 'Bits for Page Indication' (right). The 'Bits for Page Indication' sections contain bits s1, s3, ..., s_{N_{PIB}-1}, s_{N_{PIB}+1}, s_{N_{PIB}+3} on the left and s_{N_{PIB}+2}, s_{N_{PIB}+4}, s2, s4, ..., s_{N_{PIB}} on the right. The 'Reserved Bits' section contains the 'Midamble'. The entire burst is followed by a 'Guard Period'. The total duration is labeled '1 Time Slot'.](09084c793f44a50d7a1558dbb45d317d_img.jpg) + +The diagram illustrates the bit structure of a PICH burst within a single time slot. The burst is composed of several bit groups and a midamble. On the left, 'Bits for Page Indication' include $s_1, s_3, \dots, s_{N_{PIB}-1}$ . In the center, 'Reserved Bits' include $s_{N_{PIB}+1}, s_{N_{PIB}+3}$ . The 'Midamble' follows. On the right, 'Reserved Bits' include $s_{N_{PIB}+2}, s_{N_{PIB}+4}$ , and 'Bits for Page Indication' include $s_2, s_4, \dots, s_{N_{PIB}}$ . The burst concludes with a 'Guard Period'. The entire sequence is contained within '1 Time Slot'. + +Diagram of a PICH burst structure within a 1 Time Slot. The burst is divided into three main sections: 'Bits for Page Indication' (left), 'Reserved Bits' (middle), and 'Bits for Page Indication' (right). The 'Bits for Page Indication' sections contain bits s1, s3, ..., s\_{N\_{PIB}-1}, s\_{N\_{PIB}+1}, s\_{N\_{PIB}+3} on the left and s\_{N\_{PIB}+2}, s\_{N\_{PIB}+4}, s2, s4, ..., s\_{N\_{PIB}} on the right. The 'Reserved Bits' section contains the 'Midamble'. The entire burst is followed by a 'Guard Period'. The total duration is labeled '1 Time Slot'. + +**Figure 18AM: Transmission and numbering of paging indicator carrying bits in a PICH burst** + +Each paging indicator $P_q$ in one time slot is mapped to the bits $\{s_{2L_{pi} \cdot q + 1}, \dots, s_{2L_{pi} \cdot (q+1)}}\}$ within this time slot. Thus, due to the interleaved transmission of the bits half of the symbols used for each paging indicator are transmitted in the first data part, and the other half of the symbols are transmitted in the second data part; an example is shown in figure 18AN for a paging indicator length $L_{pi}$ of 4 symbols. + +![Figure 18AN: Example of mapping of paging indicators on PICH bits for L_Pi=4. The diagram shows two radio frame structures. The left frame has a total duration of 5120 T_c and contains a Midamble of 512 Chips. It shows P_0 and P_33 as paging indicators, with 2 unused symbols between them. The right frame also has a total duration of 5120 T_c and contains a Midamble of 1024 Chips. It shows P_0 and P_29 as paging indicators, with 2 unused symbols between them. Both frames include a GP (Guard Period) at the end.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +Figure 18AN: Example of mapping of paging indicators on PICH bits for L\_Pi=4. The diagram shows two radio frame structures. The left frame has a total duration of 5120 T\_c and contains a Midamble of 512 Chips. It shows P\_0 and P\_33 as paging indicators, with 2 unused symbols between them. The right frame also has a total duration of 5120 T\_c and contains a Midamble of 1024 Chips. It shows P\_0 and P\_29 as paging indicators, with 2 unused symbols between them. Both frames include a GP (Guard Period) at the end. + +**Figure 18AN: Example of mapping of paging indicators on PICH bits for $L_{Pi}=4$** + +The setting of the paging indicators and the corresponding PICH bits (including the reserved ones) is described in [4]. + +$N_{Pi}$ paging indicators of length $L_{Pi}=2$ , $L_{Pi}=4$ or $L_{Pi}=8$ symbols are transmitted in each radio frame that contains the PICH. The number of paging indicators $N_{Pi}$ per radio frame is given by the paging indicator length and the burst type, which are both known by higher layer signalling. In table 8AH this number is shown for the different possibilities of burst types and paging indicator lengths. + +**Table 8AH: Number $N_{Pi}$ of paging indicators per time slot for the different burst types and paging indicator lengths $L_{Pi}$** + +| | $L_{Pi}=2$ | $L_{Pi}=4$ | $L_{Pi}=8$ | +|--------------|-------------|-------------|-------------| +| Burst Type 1 | $N_{Pi}=60$ | $N_{Pi}=30$ | $N_{Pi}=15$ | +| Burst Type 2 | $N_{Pi}=68$ | $N_{Pi}=34$ | $N_{Pi}=17$ | + +#### 5B.4.7.2 Structure of the PICH over multiple radio frames + +The structure of PICH over multiple radio frames is identical to the structure of PICH in 3.84Mcps TDD cf [section 5.3.7.2]. + +#### 5B.4.7.3 PICH Training sequences + +The training sequences, i.e. midambles for the PICH, are generated as described in subclause 5B.3.3. The allocation of midambles depends on whether SCTD is applied to the PICH. + +- If no antenna diversity is applied the PICH the midambles can be allocated as described in subclause 5B.7. +- If SCTD antenna diversity is applied to the PICH the allocation of midambles shall be as described in [9]. + +### 5B.4.8 High Speed Physical Downlink Shared Channel (HS-PDSCH) + +The HS-DSCH as described in subclause 4.1.2 is mapped onto one or more high speed physical downlink shared channels (HS-PDSCH). + +#### 5B.4.8.1 HS-PDSCH Spreading + +The HS-PDSCH shall use either spreading factor $SF = 32$ or $SF=1$ , as described in 5B.3.1.1. + +#### 5B.4.8.2 HS-PDSCH Burst Types + +Burst types 1 or 2 as described in subclause 5B.3.2 can be used for PDSCH. TFCI shall not be transmitted on the HS-PDSCH. The TF of the HS-DSCH is derived from the associated HS-SCCH. + +#### 5B.4.8.3 HS-PDSCH Training Sequences + +The training sequences as described in subclause 5B.3.3 are used for the HS-PDSCH. + +#### 5B.4.8.4 UE Selection + +To indicate to the UE that there is data to decode on the HS-DSCH, the UE id on the associated HS-SCCH shall be used. + +#### 5B.4.8.5 HS-PDSCH timeslot formats + +An HS-PDSCH may use QPSK or 16QAM modulation symbols. The time slot formats are shown in table 8AI. + +Table 8AI: Time slot formats for the HS-PDSCH + +| Slot Format # | Spreading Factor | Midamble length (chips) | N TFCI code word (bits) | Bits/slot | N Data/Slot (bits) | N data/data field (bits) | +|---------------|------------------|-------------------------|------------------------------------|-----------|-------------------------------|-------------------------------------| +| 0 (QPSK) | 32 | 1024 | 0 | 244 | 244 | 122 | +| 1 (16QAM) | 32 | 1024 | 0 | 488 | 488 | 244 | +| 2 (QPSK) | 32 | 512 | 0 | 276 | 276 | 138 | +| 3 (16QAM) | 32 | 512 | 0 | 552 | 552 | 276 | +| 4 (QPSK) | 1 | 1024 | 0 | 7808 | 7808 | 3904 | +| 5 (16QAM) | 1 | 1024 | 0 | 15616 | 15616 | 7808 | +| 6 (QPSK) | 1 | 512 | 0 | 8832 | 8832 | 4416 | +| 7(16QAM) | 1 | 512 | 0 | 17664 | 17664 | 8832 | + +### 5B.4.9 Shared Control Channel for HS-DSCH (HS-SCCH) + +The HS-SCCH is a DL physical channel that carries higher layer control information for HS-DSCH. The physical layer will process this information according to [7] and will transmit the resulting bits on the HS-SCCH the structure of which is described below. + +#### 5B.4.9.1 HS-SCCH Spreading + +The HS-SCCH shall use spreading factor SF = 32, as described in 5B.3.1.1. + +#### 5B.4.9.2 HS-SCCH Burst Types + +Burst type 1 as described in subclause 5B.3.2 can be used for HS-SCCH. TFCI shall not be transmitted on the HS-SCCH. + +#### 5B.4.9.3 HS-SCCH Training Sequences + +The training sequences as described in subclause 5B.3.3 are used for the HS-SCCH. + +#### 5B.4.9.4 HS-SCCH timeslot formats + +The HS-SCCH always uses time slot format #0 from table 8AF, see section 5B.3.2.6.1. + +### 5B.4.10 Shared Information Channel for HS-DSCH (HS-SICH) + +The HS-SICH is a UL physical channel that carries higher layer control information and the Channel Quality Indicator CQI for HS-DSCH. The physical layer will process this information according to [7] and will transmit the resulting bits on the HS-SICH the structure of which is described below. + +#### 5B.4.10.1 HS-SICH Spreading + +The HS-SICH shall use spreading factor SF = 32, as described in 5B.3.1.2. + +#### 5B.4.10.2 HS-SICH Burst Types + +Burst type 1 as described in subclause 5B.3.2 can be used for HS-SICH. TFCI shall not be transmitted on the HS-SICH, however, the HS-SICH shall carry TPC information. + +#### 5B.4.10.3 HS-SICH Training Sequences + +The training sequences as described in subclause 5B.3.3 are used for the HS-SICH. + +#### 5B.4.10.4 HS-SICH timeslot formats + +The HS-SICH shall use time slot format #90 from table 8AF, see section 5B.3.2.6.2. + +### 5B.4.11 The MBMS Indicator Channel (MICH) + +The MBMS Indicator Channel (MICH) is a physical channel used to carry the MBMS notification indicators. The UE may use multiple MICH within the MBMS modification period in order to make decisions on individual MBMS notification indicators. + +#### 5B.4.11.1 Mapping of MBMS Indicators to the MICH bits for burst types 1 and 2 + +Figure 18AO depicts the structure of a MICH burst and the numbering of the bits within the burst. The same burst type is used for the MICH in every cell. $N_{NIB}$ bits in a normal burst of type 1 or 2 are used to carry the MBMS notification indicators, where $N_{NIB}$ depends on the burst type: $N_{NIB}=240$ for burst type 1 and $N_{NIB}=272$ for burst type 2. The bits $s_{NNIB+1}, \dots, s_{NNIB+4}$ adjacent to the midamble are reserved for possible future use. + +![Diagram of a MICH burst structure showing bits for notification indication, reserved bits, midamble, and guard period within a 1 time slot.](4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg) + +The diagram illustrates the structure of a MICH burst within a single time slot. It is divided into three main sections: 'Bits for Notification Indication' (on the left and right), 'Reserved Bits' (in the center), and a 'Midamble' (in the middle). The left 'Bits for Notification Indication' section contains symbols $s_1, s_3, \dots, s_{NNIB-1}$ . The 'Reserved Bits' section contains symbols $s_{NNIB+1}, s_{NNIB+3}$ (hatched) and $s_{NNIB+2}, s_{NNIB+4}$ (hatched). The 'Midamble' is a central block. The right 'Bits for Notification Indication' section contains symbols $s_2, s_4, \dots, s_{NNIB}$ . The entire burst is followed by a 'Guard Period' (hatched). A double-headed arrow at the bottom indicates the total duration of '1 Time Slot'. + +Diagram of a MICH burst structure showing bits for notification indication, reserved bits, midamble, and guard period within a 1 time slot. + +**Figure 18AO: Transmission and numbering of MBMS notification indicator carrying bits in a MICH burst using burst types 1 and 2** + +Each notification indicator $N_q$ in one time slot is mapped to the bits $\{s_{2L_{NI} \cdot q+1}, \dots, s_{2L_{NI} \cdot (q+1)}}\}$ within this time slot. Thus, due to the interleaved transmission of the bits half of the symbols used for each MBMS notification indicator are transmitted in the first data part, and the other half of the symbols are transmitted in the second data part: an example is shown in figure 18AP for a MBMS notification indicator length $L_{NI}$ of 4 symbols. + +![Diagram showing the mapping of MBMS notification indicators N0 and N33 (burst type 2) and N0 and N29 (burst type 1) onto MICH bits, including unused symbols and midamble chip counts.](1dbb1d90b2022a3a765c85929a515cc6_img.jpg) + +This diagram shows two examples of bit mapping for a 5120 $T_c$ time slot. The left example for burst type 2 shows a midamble of 256 chips, with notification indicators $N_0$ and $N_{33}$ mapped to specific bits. It also shows '2 unused symbols' and a 'GP' (Guard Period). The right example for burst type 1 shows a midamble of 512 chips, with notification indicators $N_0$ and $N_{29}$ mapped. It also shows '2 unused symbols' and a 'GP'. + +Diagram showing the mapping of MBMS notification indicators N0 and N33 (burst type 2) and N0 and N29 (burst type 1) onto MICH bits, including unused symbols and midamble chip counts. + +**Figure 18AP: Example of mapping of MBMS notification indicators on MICH bits for $L_{NI}=4$ for burst types 2 and 1 respectively** + +The setting of the MBMS notification indicators and the corresponding MICH bits (including the reserved ones) is described in [7]. + +$N_n$ MBMS notification indicators of length $L_{NI}=2, L_{NI}=4$ or $L_{NI}=8$ symbols are transmitted in each MICH. The number of MBMS notification indicators $N_n$ per MICH is given by the MBMS notification indicator length and the burst type, + +which are both known by higher layer signalling. In table 18AJ this number is shown for burst types 1 and 2 and differing MBMS notification indicator lengths. + +**Table 18AJ: Number $N_n$ of MBMS notification indicators per time slot for burst types 1 and 2 and differing MBMS notification indicator lengths $L_{NI}$** + +| | $L_{NI}=2$ | $L_{NI}=4$ | $L_{NI}=8$ | +|--------------|------------|------------|------------| +| Burst Type 1 | $N_n=60$ | $N_n=30$ | $N_n=15$ | +| Burst Type 2 | $N_n=68$ | $N_n=34$ | $N_n=17$ | + +The value $NI$ ( $NI = 0, \dots, N_{NI}-1$ ) calculated by higher layers, is associated to the MBMS notification indicator $N_q$ , where $q = NI \bmod N_n$ . + +The set of $NI$ passed over the Iub indicates all higher layer $NI$ values for which the notification indicator on MICH should be set to 1 during the corresponding modification period; all other indicators shall be set to 0. + +##### 5B.4.11.1A Mapping of MBMS Indicators to the MICH bits for burst type 4 + +When an entire carrier is dedicated to MBSFN operation, the MICH shall use burst type 4. In this case $N_{NIB}=256$ and there are 8 reserved/unused bits adjacent to the midamble reserved for possible future use. The transmission and numbering of MBMS notification indicator carrying bits in a MICH burst is similar to that of figure 18AO with the exception of 4 reserved bits either side of the midamble as opposed to 2 for burst types 1 and 2. An example mapping is shown in figure 18AP.1 for a MBMS notification indicator length $L_{NI}$ of 4 symbols. + +![Diagram of a MICH burst structure for burst type 4. The total burst length is 5120 Tc. It consists of several segments: a leading part of length N0, followed by a part of length N31, then a 'Midamble (640 Chips)' which is 4 symbols long, followed by another part of length N31, and finally a trailing part of length N0. The midamble is highlighted in grey. The diagram shows the mapping of MBMS notification indicators to the MICH bits, with the midamble being a fixed part of the burst structure.](9e5d66cdb5112ad5cab89552b126e4b9_img.jpg) + +Diagram of a MICH burst structure for burst type 4. The total burst length is 5120 Tc. It consists of several segments: a leading part of length N0, followed by a part of length N31, then a 'Midamble (640 Chips)' which is 4 symbols long, followed by another part of length N31, and finally a trailing part of length N0. The midamble is highlighted in grey. The diagram shows the mapping of MBMS notification indicators to the MICH bits, with the midamble being a fixed part of the burst structure. + +**Figure 18AP.1: Example of mapping of MBMS notification indicators on MICH bits for $L_{NI}=4$ for burst type 4** + +The setting of the MBMS notification indicators and the corresponding MICH bits (including the reserved ones) is described in [7]. + +$N_n$ MBMS notification indicators of length $L_{NI}=2$ , $L_{NI}=4$ or $L_{NI}=8$ symbols are transmitted in each MICH. The number of MBMS notification indicators $N_n$ per MICH is given by the MBMS notification indicator length and the burst type, which are both known by higher layer signalling. In table 18AK this number is shown for the different possibilities of burst types and MBMS notification indicator lengths. + +**Table 18AK: Number $N_n$ of MBMS notification indicators per time slot for burst type 4 and differing MBMS notification indicator lengths $L_{NI}$** + +| | $L_{NI}=2$ | $L_{NI}=4$ | $L_{NI}=8$ | +|--------------|------------|------------|------------| +| Burst Type 4 | $N_n=64$ | $N_n=32$ | $N_n=16$ | + +The value $NI$ ( $NI = 0, \dots, N_{NI}-1$ ) calculated by higher layers, is associated to the MBMS notification indicator $N_q$ , where $q = NI \bmod N_n$ . + +The set of $NI$ passed over the Iub indicates all higher layer $NI$ values for which the notification indicator on MICH should be set to 1 during the corresponding modification period; all other indicators shall be set to 0. + +#### 5B.4.11.2 MICH Training sequences + +The training sequences, i.e. midambles for the MICH, are generated as described in subclause 5B.3.3. The allocation of midambles depends on whether SCTD is applied to the MICH. + +- If no antenna diversity is applied the MICH the midambles can be allocated as described in subclause 5B.7. +- If SCTD antenna diversity is applied to the MICH the allocation of midambles shall be as described in [9]. + +Note that when the entire carrier is dedicated to MBFSN operation MICH employs burst type 4 as described in subclause 5B.4.11.1A. Burst type 4 supports a single midamble and hence SCTD is precluded from operation in such a scenario. + +### 5B.4.12 E-DCH Physical Uplink Channel (E-PUCH) + +One or more E-PUCH are used to carry the uplink E-DCH transport channel and associated control information (E-UCCH) in each E-DCH TTI. In a timeslot designated by UTRAN for E-PUCH use, up to one E-PUCH may be transmitted by a UE. No other physical channels may be transmitted by a UE in an E-PUCH timeslot. + +Timing advance, as described in [9], subclause 4.3, is applied to the E-PUCH. + +#### 5B.4.12.1 E-UCCH + +The E-DCH Uplink Control Channel (E-UCCH) carries uplink control information associated with the E-DCH and is carried within indicator fields mapped to E-PUCH. Depending on the configuration by higher layers, an E-PUCH burst may or may not contain E-UCCH and TPC. When E-PUCH does contain E-UCCH, TPC is also transmitted. When E-PUCH does not contain E-UCCH, TPC is not transmitted. + +Higher layers shall indicate the maximum number of timeslots ( $N_{E-UCCH}$ ) that may contain E-UCCH/TPC in the E-DCH TTI. For an allocation of $n_{TS}$ E-PUCH timeslots, the UE shall transmit E-UCCH and TPC on the first $m$ allocated timeslots of the E-DCH TTI, where $m = \min(n_{TS}, N_{E-UCCH})$ . + +The E-UCCH comprises two parts, E-UCCH part 1 and E-UCCH part 2. + +E-UCCH part 1: + +- is of length 32 physical channel bits +- is mapped to the TFCI field of the E-PUCH (16 bits either side of the midamble) +- is spread at SF=32 using the channelisation code in the branch with the highest code numbering of the allowed OVSF sub tree, as depicted in [8] +- uses QPSK modulation + +E-UCCH part 2: + +- is of length 32 physical channel bits +- is spread using the same spreading factor as the data payloads +- uses the same modulation as the data payloads + +Figures 18APA and 18APB show the E-PUCH data burst with and without the E-UCCH/TPC fields. + +![Figure 18APA: Location of E-UCCH part 1, E-UCCH part 2 and TPC in the E-PUCH data burst. The diagram shows a data burst structure with 'Data symbols', 'Midamble', 'Data symbols', and 'GP'. The 'Midamble' section is divided into 'E-UCCH part 1', 'E-UCCH part 2', and 'TPC'. The total length of the burst is 5120 * Tc, and the 'Midamble' section is 1024/512 chips long.](8e80de0cac529b2c3775d677c5203133_img.jpg) + +Figure 18APA: Location of E-UCCH part 1, E-UCCH part 2 and TPC in the E-PUCH data burst. The diagram shows a data burst structure with 'Data symbols', 'Midamble', 'Data symbols', and 'GP'. The 'Midamble' section is divided into 'E-UCCH part 1', 'E-UCCH part 2', and 'TPC'. The total length of the burst is 5120 \* Tc, and the 'Midamble' section is 1024/512 chips long. + +Figure 18APA: Location of E-UCCH part 1, E-UCCH part 2 and TPC in the E-PUCH data burst + +![Figure 18APB: E-PUCH data burst without E-UCCH/TPC. The diagram shows a data burst structure with 'Data symbols', 'Midamble', 'Data symbols', and 'GP'. The 'Midamble' section is 1024/512 chips long, and the total length of the burst is 5120 * Tc.](67d03c9e89620d73e3786c869e559752_img.jpg) + +Figure 18APB: E-PUCH data burst without E-UCCH/TPC. The diagram shows a data burst structure with 'Data symbols', 'Midamble', 'Data symbols', and 'GP'. The 'Midamble' section is 1024/512 chips long, and the total length of the burst is 5120 \* Tc. + +Figure 18APB: E-PUCH data burst without E-UCCH/TPC + +#### 5B.4.12.2 E-PUCH Spreading + +The spreading factors that can be applied to the E-PUCH are $SF = 1, 2, 4, 8, 16, 32$ as described in subclause 5B.3.1.2. + +#### 5B.4.12.3 E-PUCH Burst Types + +Burst types 1, 2 or 3 as described in subclause 5B.3.2 can be used for E-PUCH. E-UCCH and TPC can be transmitted on the E-PUCH. + +#### 5B.4.12.4 PUSCH Training Sequences + +The training sequences as described in subclause 5B.3.3 are used for the E-PUCH. + +#### 5B.4.12.5 UE Selection + +UEs that shall transmit on the E-PUCH are selected by higher layers. The UE id on the associated E-AGCH shall be used for identification. + +#### 5B.4.12.6 E-PUCH timeslot formats + +An E-PUCH may use QPSK or 16QAM modulation symbols and may or may not contain E-UCCH/TPC. The time slot formats are shown in table 19. + +Table 19: Timeslot formats for E-PUCH + +| slot format # | SF | Midamble Length (chips) | GP (chips) | $N_{EUCCH1}$ (bits) | $N_{EUCCH2}$ (bits) | $N_{TPC}$ (bits) | Bits/slot | $N_{data/slot}$ (bits) | $N_{data/data\ field(1)}$ (bits) | $N_{data/data\ field(2)}$ (bits) | +|---------------|----|-------------------------|------------|---------------------|---------------------|------------------|-----------|------------------------|----------------------------------|----------------------------------| +| 0 (QPSK) | 32 | 1024 | 192 | 0 | 0 | 0 | 244 | 244 | 122 | 122 | +| 1 (16QAM) | 32 | 1024 | 192 | 0 | 0 | 0 | 488 | 488 | 244 | 244 | + +| slot format # | SF | Midamble Length (chips) | GP (chips) | N UECCH1 (bits) | N UECCH2 (bits) | N TPC (bits) | Bits/slot | N data/slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) | +|---------------|----|-------------------------|------------|----------------------------|----------------------------|-------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------| +| 2 (QPSK) | 32 | 1024 | 192 | 32 | 32 | 2 | 244 | 178 | 90 | 88 | +| 3 (16QAM) | 32 | 1024 | 192 | 32 | 32 | 2 | 454 | 388 | 196 | 192 | +| 4 (QPSK) | 32 | 512 | 192 | 0 | 0 | 0 | 276 | 276 | 138 | 138 | +| 5 (16QAM) | 32 | 512 | 192 | 0 | 0 | 0 | 552 | 552 | 276 | 276 | +| 6 (QPSK) | 32 | 512 | 192 | 32 | 32 | 2 | 276 | 210 | 106 | 104 | +| 7 (16QAM) | 32 | 512 | 192 | 32 | 32 | 2 | 518 | 452 | 228 | 224 | +| 8 (QPSK) | 16 | 1024 | 192 | 0 | 0 | 0 | 488 | 488 | 244 | 244 | +| 9 (16QAM) | 16 | 1024 | 192 | 0 | 0 | 0 | 976 | 976 | 488 | 488 | +| 10 (QPSK) | 16 | 1024 | 192 | 32 | 32 | 2 | 454 | 388 | 196 | 192 | +| 11 (16QAM) | 16 | 1024 | 192 | 32 | 32 | 2 | 874 | 808 | 408 | 400 | +| 12 (QPSK) | 16 | 512 | 192 | 0 | 0 | 0 | 552 | 552 | 276 | 276 | +| 13 (16QAM) | 16 | 512 | 192 | 0 | 0 | 0 | 1104 | 1104 | 552 | 552 | +| 14 (QPSK) | 16 | 512 | 192 | 32 | 32 | 2 | 518 | 452 | 228 | 224 | +| 15 (16QAM) | 16 | 512 | 192 | 32 | 32 | 2 | 1002 | 936 | 472 | 464 | +| 16 (QPSK) | 8 | 1024 | 192 | 0 | 0 | 0 | 976 | 976 | 488 | 488 | +| 17 (16QAM) | 8 | 1024 | 192 | 0 | 0 | 0 | 1952 | 1952 | 976 | 976 | +| 18 (QPSK) | 8 | 1024 | 192 | 32 | 32 | 2 | 874 | 808 | 408 | 400 | +| 19 (16QAM) | 8 | 1024 | 192 | 32 | 32 | 2 | 1714 | 1648 | 832 | 816 | +| 20 (QPSK) | 8 | 512 | 192 | 0 | 0 | 0 | 1104 | 1104 | 552 | 552 | +| 21 (16QAM) | 8 | 512 | 192 | 0 | 0 | 0 | 2208 | 2208 | 1104 | 1104 | +| 22 (QPSK) | 8 | 512 | 192 | 32 | 32 | 2 | 1002 | 936 | 472 | 464 | +| 23 (16QAM) | 8 | 512 | 192 | 32 | 32 | 2 | 1970 | 1904 | 960 | 944 | +| 24 (QPSK) | 4 | 1024 | 192 | 0 | 0 | 0 | 1952 | 1952 | 976 | 976 | +| 25 (16QAM) | 4 | 1024 | 192 | 0 | 0 | 0 | 3904 | 3904 | 1952 | 1952 | +| 26 (QPSK) | 4 | 1024 | 192 | 32 | 32 | 2 | 1714 | 1648 | 832 | 816 | +| 27 (16QAM) | 4 | 1024 | 192 | 32 | 32 | 2 | 3394 | 3328 | 1680 | 1648 | +| 28 (QPSK) | 4 | 512 | 192 | 0 | 0 | 0 | 2208 | 2208 | 1104 | 1104 | +| 29 (16QAM) | 4 | 512 | 192 | 0 | 0 | 0 | 4416 | 4416 | 2208 | 2208 | +| 30 (QPSK) | 4 | 512 | 192 | 32 | 32 | 2 | 1970 | 1904 | 960 | 944 | +| 31 (16QAM) | 4 | 512 | 192 | 32 | 32 | 2 | 3906 | 3840 | 1936 | 1904 | +| 32 (QPSK) | 2 | 1024 | 192 | 0 | 0 | 0 | 3904 | 3904 | 1952 | 1952 | +| 33 (16QAM) | 2 | 1024 | 192 | 0 | 0 | 0 | 7808 | 7808 | 3904 | 3904 | +| 34 (QPSK) | 2 | 1024 | 192 | 32 | 32 | 2 | 3394 | 3328 | 1680 | 1648 | +| 35 (16QAM) | 2 | 1024 | 192 | 32 | 32 | 2 | 6754 | 6688 | 3376 | 3312 | +| 36 (QPSK) | 2 | 512 | 192 | 0 | 0 | 0 | 4416 | 4416 | 2208 | 2208 | +| 37 (16QAM) | 2 | 512 | 192 | 0 | 0 | 0 | 8832 | 8832 | 4416 | 4416 | +| 38 (QPSK) | 2 | 512 | 192 | 32 | 32 | 2 | 3906 | 3840 | 1936 | 1904 | +| 39 (16QAM) | 2 | 512 | 192 | 32 | 32 | 2 | 7778 | 7712 | 3888 | 3824 | +| 40 (QPSK) | 1 | 1024 | 192 | 0 | 0 | 0 | 7808 | 7808 | 3904 | 3904 | +| 41 (16QAM) | 1 | 1024 | 192 | 0 | 0 | 0 | 15616 | 15616 | 7808 | 7808 | +| 42 (QPSK) | 1 | 1024 | 192 | 32 | 32 | 2 | 6754 | 6688 | 3376 | 3312 | +| 43 (16QAM) | 1 | 1024 | 192 | 32 | 32 | 2 | 13474 | 13408 | 6768 | 6640 | +| 44 (QPSK) | 1 | 512 | 192 | 0 | 0 | 0 | 8832 | 8832 | 4416 | 4416 | +| 45 (16QAM) | 1 | 512 | 192 | 0 | 0 | 0 | 17664 | 17664 | 8832 | 8832 | +| 46 (QPSK) | 1 | 512 | 192 | 32 | 32 | 2 | 7778 | 7712 | 3888 | 3824 | +| 47 (16QAM) | 1 | 512 | 192 | 32 | 32 | 2 | 15522 | 15456 | 7792 | 7664 | +| 48 (QPSK) | 32 | 1024 | 384 | 0 | 0 | 0 | 232 | 232 | 122 | 110 | +| 49 (16QAM) | 32 | 1024 | 384 | 0 | 0 | 0 | 464 | 464 | 244 | 220 | +| 50 (QPSK) | 32 | 1024 | 384 | 32 | 32 | 2 | 232 | 166 | 90 | 76 | + +| slot format # | SF | Midamble Length (chips) | GP (chips) | N UECCH1 (bits) | N UECCH2 (bits) | N TPC (bits) | Bits/slot | N data/slot (bits) | N data/data field(1) (bits) | N data/data field(2) (bits) | +|---------------|----|-------------------------|------------|----------------------------|----------------------------|-------------------------|-----------|-------------------------------|----------------------------------------|----------------------------------------| +| 51 (16QAM) | 32 | 1024 | 384 | 32 | 32 | 2 | 430 | 364 | 196 | 168 | +| 52 (QPSK) | 16 | 1024 | 384 | 0 | 0 | 0 | 464 | 464 | 244 | 220 | +| 53 (16QAM) | 16 | 1024 | 384 | 0 | 0 | 0 | 928 | 928 | 488 | 440 | +| 54 (QPSK) | 16 | 1024 | 384 | 32 | 32 | 2 | 430 | 364 | 196 | 168 | +| 55 (16QAM) | 16 | 1024 | 384 | 32 | 32 | 2 | 826 | 760 | 408 | 352 | +| 56 (QPSK) | 8 | 1024 | 384 | 0 | 0 | 0 | 928 | 928 | 488 | 440 | +| 57 (16QAM) | 8 | 1024 | 384 | 0 | 0 | 0 | 1856 | 1856 | 976 | 880 | +| 58 (QPSK) | 8 | 1024 | 384 | 32 | 32 | 2 | 826 | 760 | 408 | 352 | +| 59 (16QAM) | 8 | 1024 | 384 | 32 | 32 | 2 | 1618 | 1552 | 832 | 720 | +| 60 (QPSK) | 4 | 1024 | 384 | 0 | 0 | 0 | 1856 | 1856 | 976 | 880 | +| 61 (16QAM) | 4 | 1024 | 384 | 0 | 0 | 0 | 3712 | 3712 | 1952 | 1760 | +| 62 (QPSK) | 4 | 1024 | 384 | 32 | 32 | 2 | 1618 | 1552 | 832 | 720 | +| 63 (16QAM) | 4 | 1024 | 384 | 32 | 32 | 2 | 3202 | 3136 | 1680 | 1456 | +| 64 (QPSK) | 2 | 1024 | 384 | 0 | 0 | 0 | 3712 | 3712 | 1952 | 1760 | +| 65 (16QAM) | 2 | 1024 | 384 | 0 | 0 | 0 | 7424 | 7424 | 3904 | 3520 | +| 66 (QPSK) | 2 | 1024 | 384 | 32 | 32 | 2 | 3202 | 3136 | 1680 | 1456 | +| 67 (16QAM) | 2 | 1024 | 384 | 32 | 32 | 2 | 6370 | 6304 | 3376 | 2928 | +| 68 (QPSK) | 1 | 1024 | 384 | 0 | 0 | 0 | 7424 | 7424 | 3904 | 3520 | +| 69 (16QAM) | 1 | 1024 | 384 | 0 | 0 | 0 | 14848 | 14848 | 7808 | 7040 | +| 70 (QPSK) | 1 | 1024 | 384 | 32 | 32 | 2 | 6370 | 6304 | 3376 | 2928 | +| 71 (16QAM) | 1 | 1024 | 384 | 32 | 32 | 2 | 12706 | 12640 | 6768 | 5872 | + +### 5B.4.13 E-DCH Random Access Uplink Control Channel (E-RUCCH) + +The E-RUCCH is used to carry E-DCH-associated uplink control signalling when E-PUCH resources are not available. The characteristics of the E-RUCCH physical channel are identical to those of PRACH (see subclause 5B.4.3). + +Physical resources available for E-RUCCH are configured by higher layers. E-RUCCH may be mapped to the same physical resources that are assigned for PRACH. + +### 5B.4.14 E-DCH Absolute Grant Channel (E-AGCH) + +The E-DCH Absolute Grant Channel (E-AGCH) is a downlink physical channel carrying the uplink E-DCH absolute grant control information. Unlike other downlink physical channel types, E-AGCH also carries a TPC field (located immediately after the midamble and spread using SF32) which is used to control the E-PUCH power. Figure 18APC illustrates the burst structure of the E-AGCH. + +![Figure 18APC: Burst structure of E-AGCH. The diagram shows a horizontal bar representing the burst structure. From left to right, it consists of 'Data symbols', 'Midamble', 'Data symbols', and 'GP'. A shaded rectangular section within the 'Midamble' is labeled 'TPC field'. Below the 'Midamble' section, a double-headed arrow indicates its length as '1024/512 chips'. Below the entire bar, another double-headed arrow indicates the total length as '5120*Tc'.](18291be12b470a557e8c9f3a74e021be_img.jpg) + +Figure 18APC: Burst structure of E-AGCH. The diagram shows a horizontal bar representing the burst structure. From left to right, it consists of 'Data symbols', 'Midamble', 'Data symbols', and 'GP'. A shaded rectangular section within the 'Midamble' is labeled 'TPC field'. Below the 'Midamble' section, a double-headed arrow indicates its length as '1024/512 chips'. Below the entire bar, another double-headed arrow indicates the total length as '5120\*Tc'. + +Figure 18APC: Burst structure of E-AGCH + +One E-DCH absolute grant for a UE shall be transmitted over one E-AGCH. + +#### 5B.4.14.1 E-AGCH Spreading + +The E-AGCH shall use spreading factor $SF = 32$ , as described in 5B.3.1.1. + +#### 5B.4.14.2 E-AGCH Burst Types + +Burst types 1 and 2 as described in subclause 5B.3.2 can be used for E-AGCH. TPC shall be transmitted on E-AGCH whereas TFCI shall not be transmitted. + +#### 5B.4.14.3 E-AGCH Training Sequences + +The training sequences as described in subclause 5B.3.3 are used for the E-AGCH. + +#### 5B.4.15.4 E-AGCH timeslot formats + +The E-AGCH uses the timeslot formats of Table 20. These augment downlink slot formats 0...19 of table 8AF, see subclause 5B.3.2.6.1. + +Table 20: Time slot formats for E-AGCH + +| Slot Format # | SF | Midamble length (chips) | $N_{TFCI}$ code word (bits) | $N_{TPC}$ (bits) | Bits/slot | $N_{Data/Slot}$ (bits) | $N_{data/data\ field\ (1)}$ (bits) | $N_{data/data\ field\ (2)}$ (bits) | +|---------------|----|-------------------------|-----------------------------|------------------|-----------|------------------------|------------------------------------|------------------------------------| +| 20 | 32 | 1024 | 0 | 2 | 244 | 242 | 122 | 120 | +| 21 | 32 | 512 | 0 | 2 | 276 | 274 | 138 | 136 | + +### 5B.4.15 E-DCH Hybrid ARQ Acknowledgement Indicator Channel (E-HICH) + +The E-DCH HARQ Acknowledgement indicator channel (E-HICH) is defined in terms of a SF32 downlink physical channel and a signature sequence. The E-HICH carries the uplink E-DCH hybrid ARQ acknowledgement indicator. Figure 18APD illustrates the structure of the E-HICH. + +![Diagram illustrating the E-HICH structure. It shows a grid of bits for multiple users (user #H, user #1, user #0) across 15 timeslots (Slot #0 to Slot #14). Each user's row contains bits b_{i,j,k} where i is the user index, j is the timeslot index, and k is the bit index within the timeslot. The bits are grouped into 'spare bits' and 'midamble' sections. A 'GP' (Guard Period) is indicated for each user's row. The entire structure is labeled '1xSF32'. Below the grid, a horizontal arrow indicates '1 radio frame, 10ms' spanning the 15 timeslots.](1b3c088f23921d4eeb45ffc05586e59b_img.jpg) + +The diagram illustrates the E-HICH structure across 15 timeslots (Slot #0 to Slot #14) for multiple users (user #H, user #1, user #0). Each user's row contains bits $b_{i,j,k}$ where $i$ is the user index, $j$ is the timeslot index, and $k$ is the bit index within the timeslot. The bits are grouped into 'spare bits' and 'midamble' sections. A 'GP' (Guard Period) is indicated for each user's row. The entire structure is labeled '1xSF32'. Below the grid, a horizontal arrow indicates '1 radio frame, 10ms' spanning the 15 timeslots. + +Diagram illustrating the E-HICH structure. It shows a grid of bits for multiple users (user #H, user #1, user #0) across 15 timeslots (Slot #0 to Slot #14). Each user's row contains bits b\_{i,j,k} where i is the user index, j is the timeslot index, and k is the bit index within the timeslot. The bits are grouped into 'spare bits' and 'midamble' sections. A 'GP' (Guard Period) is indicated for each user's row. The entire structure is labeled '1xSF32'. Below the grid, a horizontal arrow indicates '1 radio frame, 10ms' spanning the 15 timeslots. + +Figure 18APD – E-HICH Structure + +A single channelisation code may carry one or multiple signature sequences. Each signature sequence conveys a HARQ acknowledgement indicator. A maximum of one indicator may be transmitted to a UE. Each acknowledgement indicator is coded to form a signature sequence of 240 bits ( $b_0, b_1, \dots, b_{239}$ ) as defined in [7] and is transmitted within a single E-HICH timeslot. The E-HICH also contains $U$ spare bit locations, where $U=4$ for burst type 1 and $U=36$ for burst type 2. The spare bit values are not defined. + +#### 5B.4.15.1 E-HICH Spreading + +Signature sequences (including spare bits inserted) that share the same channelisation code are combined and spread using spreading factor $SF=32$ as described in [8]. + +#### 5B.4.15.2 E-HICH Burst Types + +Burst types 1 and 2 as described in subclause 5B.3.2 can be used for E-HICH. Neither TFCI nor TPC shall be transmitted on the E-HICH. + +#### 5B.4.15.3 E-HICH Training Sequences + +The training sequences as described in subclause 5B.3.3 are used for the E-HICH. + +## 5B.5 Transmit Diversity for DL Physical Channels + +Support for transmit diversity is the same as that for the 3.84 Mcps TDD option cf. [5.4 Transmit Diversity].. + +## 5B.6 Beacon characteristics of physical channels + +For the purpose of measurements, common physical channels that are allocated to particular locations (time slot, code) shall have particular physical characteristics, called beacon characteristics. Physical channels with beacon characteristics are called beacon channels. The locations of the beacon channels are called beacon locations. The ensemble of beacon channels shall provide the beacon function, i.e. a reference power level at the beacon locations, regularly existing in each radio frame. Thus, beacon channels must be present in each radio frame, the only exception is when idle periods are used to support time difference measurements for location services [9]. Then it may be possible that the beacon channels occur in the same frame and time slot as the idle periods. In this case, the beacon channels will not be transmitted in that particular frame and time slot. + +### 5B.6.1 Location of beacon channels + +The beacon locations are determined by the SCH and depend on the SCH allocation case, see subclause 5B.4.4: + +- Case 1) The beacon function shall be provided by the physical channels that are allocated to channelisation code and to $TS\#k$ , $k=0, \dots, 14$ . +- Case 2) The beacon function shall be provided by the physical channels that are allocated to channelisation code and to $TS\#k$ and $TS\#k+8$ , $k=0, \dots, 6$ . + +Note that by this definition the P-CCPCH always has beacon characteristics. + +### 5B.6.2 Physical characteristics of beacon channels + +The beacon channels shall have the following physical characteristics. They: + +- are transmitted with reference power; +- are transmitted without beamforming; +- use burst type 1 or burst type 4 when MBSFN is applied to beacon channels; +- use midamble $m^{(1)}$ and $m^{(2)}$ exclusively in this time slot; and +- midambles $m^{(9)}$ and $m^{(10)}$ are always left unused in this time slot, if 16 midambles are allowed in that cell. + +Note that in the time slot where the P-CCPCH is transmitted only the midambles $m^{(1)}$ to $m^{(8)}$ shall be used, see 5B.7.1. Thus, midambles $m^{(9)}$ and $m^{(10)}$ are always left unused in this time slot. + +Note that when MBSFN is applied to beacon channels there is a single midamble and hence midamble $m^{(1)}$ is exclusively used in the timeslot. + +The reference power corresponds to the sum of the power allocated to both midambles $m^{(1)}$ and $m^{(2)}$ . Two possibilities exist: + +- If SCTD antenna diversity is not applied to beacon channels all the reference power of any beacon channel is allocated to $m^{(1)}$ . +- If SCTD antenna diversity is applied to beacon channels, for any beacon channel midambles $m^{(1)}$ and $m^{(2)}$ are each allocated half of the reference power. + +## 5B.7 Midamble Allocation for Physical Channels + +Midamble allocation for physical channels is identical to 3.84Mcps TDD [section 5.6]. The association between midambles and channelisation codes is given in Annex AB.3. + +## 5B.8 Midamble Transmit Power + +There shall be no offset between the sum of the powers allocated to all midambles in a timeslot and the sum of the powers allocated to the data symbol fields. The transmit power within a timeslot is hence constant. + +The midamble transmit power of beacon channels is equal to the reference power. If SCTD is used for beacon channels, the reference power is equally divided between the midambles $m^{(1)}$ and $m^{(2)}$ . + +The midamble transmit power of all other physical channels depends on the midamble allocation scheme used. The following rules apply + +- In case of Default Midamble Allocation, every midamble is transmitted with the same power as the associated codes. +- In case of Common Midamble Allocation in the downlink, the transmit power of this common midamble is such that there is no power offset between the data parts and the midamble part of the overall transmit signal within one time slot. +- In case of UE Specific Midamble Allocation, the transmit power of the UE specific midamble is such that there is no power offset between the data parts and the midamble part of every user within one time slot. + +The following figure 18AQ depicts the midamble powers for the different channel types and midamble allocation schemes. + +Note 1: In figure 18AQ, the codes $c(1)$ to $c(32)$ represent the set of usable codes and not the set of used codes. + +Note 2: The common midamble allocation and the midamble allocation by higher layers are not applicable in those beacon time slots, in which the P-CCPCH is located, see section 5B.7. + +![Figure 18AQ: Midamble powers for the different midamble allocation schemes. The figure shows a grid of 9 diagrams illustrating power allocation for Common, Default, and Higher Layer midamble schemes across three beacon time slot scenarios (None, SCTD not applied, SCTD applied).](2d62ff2bded0c21414a0f40fdf8fd537_img.jpg) + +| No Beacon Time Slots | Beacon Time Slots when SCTD is not applied | Beacon Time Slots when SCTD is applied | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|----------------------------------------|-----------|------|-----------|--------|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|---------------|-----------------|-----------|---------------|-----------|--------------------------|----------------|------------|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|---------------|-----------------|---------------|---------------|---------------|-----------|-------|-----|------------|------------|----------------|--------------------------|----------------|------------|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|---------------|-----------------|---------------|---------|---------------|---------|-------|-------|-----|-----|-----|----------------|--------------------------|----------------|------------|------------| +|

Common Midamble Allocation

P ↑

c(1)Midamble m(x)Code c(1)
......
c(32)Code c(32)

x depends on the number of transmitted codes in that time slot

| c(1) | Midamble m(x) | Code c(1) | ... | ... | c(32) | Code c(32) |

P ↑

Beacon ChannelsMidamble m(1)Beacon Channels
Code c(n)Midamble m(x)Code c(n)
......
Code c(32)Code c(32)
| Beacon Channels | Midamble m(1) | Beacon Channels | Code c(n) | Midamble m(x) | Code c(n) | ... | ... | Code c(32) | Code c(32) |

P ↑

Beacon ChannelsMidamble m(1)Beacon Channels
Midamble m(2)
Code c(n)Midamble m(x)Code c(n)
......
Code c(32)Code c(32)
| Beacon Channels | Midamble m(1) | Beacon Channels | Midamble m(2) | Code c(n) | Midamble m(x) | Code c(n) | ... | ... | Code c(32) | Code c(32) | | | | | | | | | | | | | | | | | | | | | | | | +| c(1) | Midamble m(x) | | Code c(1) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ... | | | ... | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| c(32) | | Code c(32) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Beacon Channels | Midamble m(1) | Beacon Channels | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Code c(n) | Midamble m(x) | Code c(n) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ... | | ... | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Code c(32) | | Code c(32) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Beacon Channels | Midamble m(1) | Beacon Channels | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Midamble m(2) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Code c(n) | Midamble m(x) | Code c(n) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ... | | ... | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Code c(32) | | Code c(32) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|

Default Midamble Allocation

P ↑

c(1)Midamble m(1)Code c(1)
c(M)Code c(M)
c(M+1)Midamble m(2)c(M+1)
c(2M)c(2M)
.........
c(32-M+1)Midamble m(K_{CELL})Code c(32-M+1)
c(32)Code c(32)
| c(1) | Midamble m(1) | Code c(1) | c(M) | Code c(M) | c(M+1) | Midamble m(2) | c(M+1) | c(2M) | c(2M) | ... | ... | ... | c(32-M+1) | Midamble m( $K_{CELL}$ ) | Code c(32-M+1) | c(32) | Code c(32) |

P ↑

Beacon ChannelsMidamble m(1)Beacon Channels
c(2M+1)Midamble m(3)c(2M+1)
c(3M)c(3M)
.........
Code c(32-M+1)Midamble m(K_{CELL})Code c(32-M+1)
Code c(32)Code c(32)
| Beacon Channels | Midamble m(1) | Beacon Channels | c(2M+1) | Midamble m(3) | c(2M+1) | c(3M) | c(3M) | ... | ... | ... | Code c(32-M+1) | Midamble m( $K_{CELL}$ ) | Code c(32-M+1) | Code c(32) | Code c(32) |

P ↑

Beacon ChannelsMidamble m(1)Beacon Channels
Midamble m(2)
c(2M+1)Midamble m(3)c(2M+1)
c(3M)c(3M)
.........
Code c(32-M+1)Midamble m(K_{CELL})Code c(32-M+1)
Code c(32)Code c(32)
| Beacon Channels | Midamble m(1) | Beacon Channels | Midamble m(2) | c(2M+1) | Midamble m(3) | c(2M+1) | c(3M) | c(3M) | ... | ... | ... | Code c(32-M+1) | Midamble m( $K_{CELL}$ ) | Code c(32-M+1) | Code c(32) | Code c(32) | +| c(1) | Midamble m(1) | | Code c(1) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| c(M) | | Code c(M) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| c(M+1) | Midamble m(2) | c(M+1) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| c(2M) | | c(2M) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ... | ... | ... | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| c(32-M+1) | Midamble m( $K_{CELL}$ ) | Code c(32-M+1) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| c(32) | | Code c(32) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Beacon Channels | Midamble m(1) | Beacon Channels | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| c(2M+1) | Midamble m(3) | c(2M+1) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| c(3M) | | c(3M) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ... | ... | ... | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Code c(32-M+1) | Midamble m( $K_{CELL}$ ) | Code c(32-M+1) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Code c(32) | | Code c(32) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Beacon Channels | Midamble m(1) | Beacon Channels | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Midamble m(2) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| c(2M+1) | Midamble m(3) | c(2M+1) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| c(3M) | | c(3M) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ... | ... | ... | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Code c(32-M+1) | Midamble m( $K_{CELL}$ ) | Code c(32-M+1) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Code c(32) | | Code c(32) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +M: Number of codes per Midamble ( $M=32/K_{CELL}$ ); in the P-CCPCH Time Slot M = 2, independent of $K_{CELL}$ + $K_{CELL}$ : Number of usable Midamble Shifts in this Cell + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|-------------------|-------------------|-------------------|---------------|-------------------|-----|-----|-----|-------------------|--------------------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|---------------|-----------------|-------------------|---------------|-------------------|-----|-----|-----|-------------------|--------------------------|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|---------------|-----------------|---------------|-------------------|---------------|-------------------|-----|-----|-----|-------------------|--------------------------|-------------------| +|

Midamble Allocation by Higher Layers

P ↑

Codes of CCTrCH 1Midamble m(1)Codes of CCTrCH 1
Codes of CCTrCH 2Midamble m(2)Codes of CCTrCH 2
.........
Codes of CCTrCH UMidamble m(K_{CELL})Codes of CCTrCH U
| Codes of CCTrCH 1 | Midamble m(1) | Codes of CCTrCH 1 | Codes of CCTrCH 2 | Midamble m(2) | Codes of CCTrCH 2 | ... | ... | ... | Codes of CCTrCH U | Midamble m( $K_{CELL}$ ) | Codes of CCTrCH U |

P ↑

Beacon ChannelsMidamble m(1)Beacon Channels
Codes of CCTrCH 1Midamble m(3)Codes of CCTrCH 1
.........
Codes of CCTrCH UMidamble m(K_{CELL})Codes of CCTrCH U
| Beacon Channels | Midamble m(1) | Beacon Channels | Codes of CCTrCH 1 | Midamble m(3) | Codes of CCTrCH 1 | ... | ... | ... | Codes of CCTrCH U | Midamble m( $K_{CELL}$ ) | Codes of CCTrCH U |

P ↑

Beacon ChannelsMidamble m(1)Beacon Channels
Midamble m(2)
Codes of CCTrCH 1Midamble m(3)Codes of CCTrCH 1
.........
Codes of CCTrCH UMidamble m(K_{CELL})Codes of CCTrCH U
| Beacon Channels | Midamble m(1) | Beacon Channels | Midamble m(2) | Codes of CCTrCH 1 | Midamble m(3) | Codes of CCTrCH 1 | ... | ... | ... | Codes of CCTrCH U | Midamble m( $K_{CELL}$ ) | Codes of CCTrCH U | +| Codes of CCTrCH 1 | Midamble m(1) | Codes of CCTrCH 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Codes of CCTrCH 2 | Midamble m(2) | Codes of CCTrCH 2 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ... | ... | ... | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Codes of CCTrCH U | Midamble m( $K_{CELL}$ ) | Codes of CCTrCH U | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Beacon Channels | Midamble m(1) | Beacon Channels | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Codes of CCTrCH 1 | Midamble m(3) | Codes of CCTrCH 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ... | ... | ... | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Codes of CCTrCH U | Midamble m( $K_{CELL}$ ) | Codes of CCTrCH U | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Beacon Channels | Midamble m(1) | Beacon Channels | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| | Midamble m(2) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Codes of CCTrCH 1 | Midamble m(3) | Codes of CCTrCH 1 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| ... | ... | ... | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| Codes of CCTrCH U | Midamble m( $K_{CELL}$ ) | Codes of CCTrCH U | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +U: Number of CCTrCHs in this Time Slot, multiple CCTrCHs of one user may share one midamble + $K_{CELL}$ : Number of usable Midamble Shifts in this Cell + +Figure 18AQ: Midamble powers for the different midamble allocation schemes. The figure shows a grid of 9 diagrams illustrating power allocation for Common, Default, and Higher Layer midamble schemes across three beacon time slot scenarios (None, SCTD not applied, SCTD applied). + +**Figure 18AQ: Midamble powers for the different midamble allocation schemes** + +# 6 Mapping of transport channels to physical channels for the 3.84 Mcps option + +This clause describes the way in which transport channels are mapped onto physical resources, see figure 19. Sub-clauses 6.1 and 6.2 do not apply to 3.84 Mcps MBSFN IMB. Mappings between transport channels and physical resources for 3.84 Mcps MBSFN IMB are described in sub-clause 6.3. + +| Transport Channels | Physical Channels | +|--------------------|--------------------------------------------------------| +| DCH _____ | Dedicated Physical Channel (DPCH) | +| BCH _____ | Primary Common Control Physical Channel (P-CCPCH) | +| FACH _____ | Secondary Common Control Physical Channel (S-CCPCH) | +| PCH _____ | | +| RACH _____ | Physical Random Access Channel (PRACH) | +| USCH _____ | Physical Uplink Shared Channel (PUSCH) | +| DSCH _____ | Physical Downlink Shared Channel (PDSCH) | +| | Paging Indicator Channel (PICH) | +| | MBMS Indication Channel (MICH) | +| | Synchronisation Channel (SCH) | +| | Physical Node B Synchronisation Channel (PNBSCH) | +| HS-DSCH _____ | High Speed Physical Downlink Shared Channel (HS-PDSCH) | +| | Shared Control Channel for HS-DSCH (HS-SCCH) | +| | Shared Information Channel for HS-DSCH (HS-SICH) | +| E-DCH _____ | E-DCH Physical Uplink Channel (E-PUCH) | +| | E-DCH Random Access Uplink Control Channel (E-RUCCH) | +| | E-DCH Absolute Grant Channel (E-AGCH) | +| | E-DCH Hybrid ARQ Indicator Channel (E-HICH) | + +Figure 19: Transport channel to physical channel mapping + +## 6.1 Dedicated Transport Channels + +### 6.1.1 The Dedicated Channel (DCH) + +A dedicated transport channel is mapped onto one or more physical channels. An interleaving period is associated with each allocation. The frame is subdivided into slots that are available for uplink and downlink information transfer. The mapping of transport blocks on physical channels is described in TS 25.222 ("multiplexing and channel coding"). + +![Figure 20: Mapping of Transport Blocks onto the physical bearer. The diagram shows four radio frames (Frame 1, Frame 2, Frame 3, Frame 4). Each frame is represented by a grid of 10 columns and 2 rows. Above each frame, 'Transport Block(s)' are shown mapping to 'Coded bits', which are then mapped to specific cells in the grid. In Frame 1, the mapping is to the 3rd cell. In Frame 2, it's to the 4th cell. In Frame 3, it's to the 3rd cell. In Frame 4, it's to the 4th cell.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +Figure 20: Mapping of Transport Blocks onto the physical bearer. The diagram shows four radio frames (Frame 1, Frame 2, Frame 3, Frame 4). Each frame is represented by a grid of 10 columns and 2 rows. Above each frame, 'Transport Block(s)' are shown mapping to 'Coded bits', which are then mapped to specific cells in the grid. In Frame 1, the mapping is to the 3rd cell. In Frame 2, it's to the 4th cell. In Frame 3, it's to the 3rd cell. In Frame 4, it's to the 4th cell. + +**Figure 20: Mapping of Transport Blocks onto the physical bearer** + +For NRT packet data services, shared channels (USCH and DSCH) can be used to allow efficient allocations for a short period of time. + +### 6.1.2 The Enhanced Uplink Dedicated Channel (E-DCH) + +The enhanced uplink dedicated channel is mapped on one or several E-PUCH, see subclause 5.3.13. + +#### 6.1.2.1 E-DCH/E-AGCH Association and Timing + +The E-DCH is always associated with a number of E-DCH Absolute Grant Channels (E-AGCH) and one hybrid ARQ indicator channel (E-HICH). A grant of E-DCH transmission resources may be transmitted to the UE on any one of the associated E-AGCH. All relevant Layer 1 control information related to an E-DCH TTI is transmitted in the associated E-AGCH and E-HICH. + +The E-DCH related time slot information that is carried on the E-AGCH refers to the next valid E-PUCH allocation, which is given by the following limitation: There shall be an offset of $n_{E-AGCH} \geq 6$ time slots between the E-AGCH carrying the E-DCH related information and the first indicated E-PUCH (in time) for a given UE. The E-DCH related time slot information shall not refer to two subsequent radio frames but shall always refer to either the same or the following radio frame, as illustrated in figure 20a. Note that the figure only shows the E-AGCH that carries the E-DCH related information for the given UE. + +![Figure 20a: Timing for E-AGCH and E-DCH for different radio frame configurations for a given UE. The diagram shows two radio frames, Radio Frame #n and Radio Frame #n+1. Each frame has 10 slots. In Radio Frame #n, the E-AGCH is in slot 3 and the 1st E-PUCH is in slot 9. The offset n_E-AGCH is the number of slots between the start of the E-AGCH and the start of the 1st E-PUCH. In Radio Frame #n+1, the E-AGCH is in slot 3 and the 1st E-PUCH is in slot 9. The offset n_E-AGCH is the number of slots between the start of the E-AGCH and the start of the 1st E-PUCH.](f5d2a88925807080157c7cfb1d41cf0b_img.jpg) + +Figure 20a: Timing for E-AGCH and E-DCH for different radio frame configurations for a given UE. The diagram shows two radio frames, Radio Frame #n and Radio Frame #n+1. Each frame has 10 slots. In Radio Frame #n, the E-AGCH is in slot 3 and the 1st E-PUCH is in slot 9. The offset n\_E-AGCH is the number of slots between the start of the E-AGCH and the start of the 1st E-PUCH. In Radio Frame #n+1, the E-AGCH is in slot 3 and the 1st E-PUCH is in slot 9. The offset n\_E-AGCH is the number of slots between the start of the E-AGCH and the start of the 1st E-PUCH. + +**Figure 20a: Timing for E-AGCH and E-DCH for different radio frame configurations for a given UE** + +#### 6.1.2.2 E-DCH/E-HICH Association and Timing + +All E-DCH operations within the cell are associated with the same E-HICH channelisation code. A single E-HICH channelisation code exists in the cell per E-DCH TTI (10ms). For a given UE, a HARQ acknowledgement indicator is synchronously linked with the E-DCH TTI transmission to which it relates. There is thus a one-to-one association between an E-DCH TTI transmission and its respective HARQ acknowledgment indicator on the associated E-HICH. + +The associated E-HICH shall reside on the first instance of the E-HICH channelisation code to occur after $n_{E-HICH}$ timeslots have elapsed since the start of the last E-PUCH of the corresponding E-DCH TTI (see examples of figure 20b). The value of $n_{E-HICH}$ is configurable by higher layers within the range 4 to 44 timeslots. + +![Figure 20b: Timing for E-DCH and E-HICH for a given UE. The diagram shows two radio frames, Radio Frame #n and Radio Frame #n+M. In Radio Frame #n, the 'Last E-PUCH' is shown in the 4th timeslot and 'E-HICH' is in the 8th timeslot. A horizontal arrow labeled n_E-HICH points from the start of the frame to the E-HICH. In Radio Frame #n+M, the 'last E-PUCH' is in the 2nd timeslot and 'E-HICH' is in the 7th timeslot. A horizontal arrow labeled n_E-HICH points from the start of the frame to the E-HICH. Vertical dashed lines connect the start of the E-HICH in one frame to the start of the E-HICH in the next frame.](0a73b03fba21af142d619a9a662e6490_img.jpg) + +Figure 20b: Timing for E-DCH and E-HICH for a given UE. The diagram shows two radio frames, Radio Frame #n and Radio Frame #n+M. In Radio Frame #n, the 'Last E-PUCH' is shown in the 4th timeslot and 'E-HICH' is in the 8th timeslot. A horizontal arrow labeled n\_E-HICH points from the start of the frame to the E-HICH. In Radio Frame #n+M, the 'last E-PUCH' is in the 2nd timeslot and 'E-HICH' is in the 7th timeslot. A horizontal arrow labeled n\_E-HICH points from the start of the frame to the E-HICH. Vertical dashed lines connect the start of the E-HICH in one frame to the start of the E-HICH in the next frame. + +**Figure 20b: Timing for E-DCH and E-HICH for a given UE** + +The HARQ acknowledgement indicator associated with an E-DCH transmission is transmitted using one of 240 signature sequences carried by the associated E-HICH channelisation code. Which signature sequence $r = 0, 1, 2, \dots, 239$ is used is calculated for each E-DCH resource allocation using the information signalled on the associated E-AGCH as follows: + +where: + +- $t_0$ is the bit position ( $1 \dots n_{\text{TRR}}$ ) of the first active timeslot in the timeslot resource related information bitmap (see [7]) on E-AGCH and where bit position 1 corresponds to the lowest-numbered timeslot +- $q_0$ is the allocated channelisation code index ( $1, 2, 3, \dots, Q_0$ ) +- $Q_0$ is the spreading factor of the allocated uplink channelisation code + +## 6.2 Common Transport Channels + +### 6.2.1 The Broadcast Channel (BCH) + +The BCH is mapped onto the P-CCPCH. The secondary SCH codes indicate in which timeslot a mobile can find the P-CCPCH containing BCH. + +### 6.2.2 The Paging Channel (PCH) + +The PCH is mapped onto one or several S-CCPCHs so that capacity can be matched to requirements. The location of the PCH is indicated on the BCH. It is always transmitted at a reference power level. + +To allow an efficient DRX, the PCH is divided into PCH blocks, each of which comprising $N_{\text{PCH}}$ paging sub-channels. $N_{\text{PCH}}$ is configured by higher layers. Each paging sub-channel is mapped onto 2 consecutive PCH frames within one PCH block. Layer 3 information to a particular UE is transmitted only in the paging sub-channel, that is assigned to the UE by higher layers, see [15]. The assignment of UEs to paging sub-channels is independent of the assignment of UEs to page indicators. + +#### 6.2.2.1 PCH/PICH Association + +As depicted in figure 21, a paging block consists of one PICH block and one PCH block. If a paging indicator in a certain PICH block is set to '1' it is an indication that UEs associated with this paging indicator shall read their + +corresponding paging sub-channel within the same paging block. The value $N_{GAP} > 0$ of frames between the end of the PICH block and the beginning of the PCH block is configured by higher layers. + +![Diagram of a Paging Block structure showing PICH and PCH blocks and their sub-channels.](fe7304192caf64cda93b580c5e7e5c06_img.jpg) + +The diagram illustrates the structure of a Paging Block. At the top, a long double-headed arrow labeled 'Paging Block' spans the entire width. Below this, the block is divided into two main sections: 'PICH Block' on the left and 'PCH Block' on the right, each indicated by its own double-headed arrow. The PICH Block contains a series of slots, with the first three shown and an ellipsis indicating more. The PCH Block is divided into sub-channels labeled 'Sub-Channel #0', 'Sub-Channel #1', and 'Sub-Channel #NPCH-1', with an ellipsis between #1 and #NPCH-1. Below the sub-channel labels, a row of slots is shown for the PCH. At the bottom, three double-headed arrows indicate time durations: $N_{PICH}$ for the PICH Block, $N_{GAP}$ for the gap between blocks, and $2 \cdot N_{PCH}$ for the PCH Block. + +Diagram of a Paging Block structure showing PICH and PCH blocks and their sub-channels. + +Figure 21: Paging Sub-Channels and Association of PICH and PCH blocks + +### 6.2.3 The Forward Channel (FACH) + +The FACH is mapped onto one or several S-CCPCHs. The location of the FACH is indicated on the BCH and both, capacity and location can be changed, if required. FACH may or may not be power controlled. + +### 6.2.4 The Random Access Channel (RACH) + +The RACH has intraslot interleaving only and is mapped onto PRACH. The same slot may be used for PRACH by more than one cell. Multiple transmissions using different spreading codes may be received in parallel. More than one slot per frame may be administered for the PRACH. The location of slots allocated to PRACH is broadcast on the BCH. The PRACH uses open loop power control. The details of the employed open loop power control algorithm may be different from the corresponding algorithm on other channels. + +### 6.2.5 The Uplink Shared Channel (USCH) + +The uplink shared channel is mapped on one or several PUSCH, see subclause 5.3.5. + +### 6.2.6 The Downlink Shared Channel (DSCH) + +The downlink shared channel is mapped on one or several PDSCH, see subclause 5.3.6. + +### 6.2.7 The High Speed Downlink Shared Channel (HS-DSCH) + +The high speed downlink shared channel is mapped on one or several HS-PDSCH, see subclause 5.3.9. + +#### 6.2.7.1 HS-DSCH/HS-SCCH Association and Timing + +The HS-DSCH is always associated with a number of High Speed Shared Control Channels (HS-SCCH). The number of HS-SCCHs that are associated with an HS-DSCH for one UE can range from a minimum of one HS-SCCH ( $M=1$ ) to a maximum of four HS-SCCH ( $M=4$ ). All relevant Layer 1 control information is transmitted in the associated HS-SCCH i.e. the HS-PDSCH does not carry any Layer 1 control information. + +The HS-DSCH related time slot information that is carried on the HS-SCCH refers to the next valid HS-PDSCH allocation, which is given by the following limitation: There shall be an offset of $n_{HS-SCCH} \geq 4$ time slots between the HS-SCCH carrying the HS-DSCH related information and the first indicated HS-PDSCH (in time) for a given UE. The HS-DSCH related time slot information shall not refer to two subsequent radio frames but shall always refer to either the same or the following radio frame, as illustrated in figure 21A. Note that the figure only shows the HS-SCCH that carries the HS-DSCH related information for the given UE. + +![Figure 21A: Timing for HS-SCCH and HS-DSCH for different radio frame configurations for a given UE. The diagram shows two radio frame configurations. The top configuration shows a single radio frame 'Radio Frame #n' containing an HS-SCCH and a 1st HS-PDSCH. The bottom configuration shows two radio frames, 'Radio Frame #n' and 'Radio Frame #n+1', with the HS-SCCH in frame #n and the 1st HS-PDSCH in frame #n+1. Arrows indicate the timing offset n_HS-SCCH from the start of the HS-SCCH to the start of the 1st HS-PDSCH.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +Figure 21A: Timing for HS-SCCH and HS-DSCH for different radio frame configurations for a given UE. The diagram shows two radio frame configurations. The top configuration shows a single radio frame 'Radio Frame #n' containing an HS-SCCH and a 1st HS-PDSCH. The bottom configuration shows two radio frames, 'Radio Frame #n' and 'Radio Frame #n+1', with the HS-SCCH in frame #n and the 1st HS-PDSCH in frame #n+1. Arrows indicate the timing offset n\_HS-SCCH from the start of the HS-SCCH to the start of the 1st HS-PDSCH. + +**Figure 21A: Timing for HS-SCCH and HS-DSCH for different radio frame configurations for a given UE** + +#### 6.2.7.2 HS-SCCH/HS-DSCH/HS-SICH Association and Timing + +The HS-SCCH is always associated with one HS-SICH. The association between the HS-SCCH in DL and HS-SICH in UL shall be pre-defined by higher layers and is common for all UEs. + +The UE shall transmit the HS-DSCH related ACK / NACK on the next available associated HS-SICH with the following limitation: There shall be an offset of $n_{\text{HS-SICH}} \geq 17$ time slots between the last allocated HS-PDSCH (in time) and the HS-SICH for the given UE. Hence, the HS-SICH transmission shall be made in the next or next but one radio frame, following the HS-DSCH transmission, as illustrated in figure 21B. Note that the figure only shows the HS-SICH that carries the HS-DSCH related ACK / NACK for the given UE. + +![Figure 21B: Timing for HS-DSCH and HS-SICH for different radio frame configurations for a given UE. The diagram shows two radio frame configurations. The top configuration shows three radio frames: 'Radio Frame #n' containing the last HS-PDSCH, 'Radio Frame #n+1' (indicated by dots), and 'Radio Frame #n+2' containing the HS-SICH. The bottom configuration shows two radio frames: 'Radio Frame #n' containing the last HS-PDSCH, 'Radio Frame #n+1' (indicated by dots), and 'Radio Frame #n+2' containing the HS-SICH. Arrows indicate the timing offset n_HS-SICH from the start of the last HS-PDSCH to the start of the HS-SICH.](65d47e1d0e5982c00e9bd116b89e2b6a_img.jpg) + +Figure 21B: Timing for HS-DSCH and HS-SICH for different radio frame configurations for a given UE. The diagram shows two radio frame configurations. The top configuration shows three radio frames: 'Radio Frame #n' containing the last HS-PDSCH, 'Radio Frame #n+1' (indicated by dots), and 'Radio Frame #n+2' containing the HS-SICH. The bottom configuration shows two radio frames: 'Radio Frame #n' containing the last HS-PDSCH, 'Radio Frame #n+1' (indicated by dots), and 'Radio Frame #n+2' containing the HS-SICH. Arrows indicate the timing offset n\_HS-SICH from the start of the last HS-PDSCH to the start of the HS-SICH. + +**Figure 21B: Timing for HS-DSCH and HS-SICH for different radio frame configurations for a given UE** + +## 6.3 Mapping of TrCHs for the 3.84 Mcps MBSFN IMB option + +The following mappings are supported: + +- BCH mapped to P-CCPCH. +- FACH mapped to S-CCPCH +- MICH (no transport channel is mapped to MICH) + +# 7 Mapping of transport channels to physical channels for the 1.28 Mcps option + +This clause describes the way in which the transport channels are mapped onto physical resources, see figure 22. + +| Transport channels | Physical channels | +|--------------------|--------------------------------------------------------| +| DCH | Dedicated Physical Channel (DPCH) | +| BCH | Primary Common Control Physical Channels (P-CCPCH) | +| PCH | Secondary Common Control Physical Channels(S-CCPCH) | +| FACH | Secondary Common Control Physical Channels(S-CCPCH) | +| | PICH | +| | MICH | +| | PLCCH | +| RACH | Physical Random Access Channel (PRACH) | +| USCH | Physical Uplink Shared Channel (PUSCH) | +| DSCH | Physical Downlink Shared Channel (PDSCH) | +| | Down link Pilot Channel (DwPCH) | +| | Up link Pilot Channel (UpPCH) | +| | FPACH | +| HS-DSCH | High Speed Physical Downlink Shared Channel (HS-PDSCH) | +| | Shared Control Channel for HS-DSCH (HS-SCCH) | +| | Shared Information Channel for HS-DSCH (HS-SICH) | +| E-DCH | E-DCH Physical Uplink Channel (E-PUCH) | +| | E-DCH Uplink Control Physical Channel (E-UCCH) | +| | E-DCH Random Access Uplink Control Channel (E-RUCCH) | +| | E-DCH Absolute Grant Channel (E-AGCH) | +| | E-DCH Hybrid ARQ Indicator Channel (E-HICH) | + +Figure 22: Transport channel to physical channel mapping for 1.28Mcps TDD + +## 7.1 Dedicated Transport Channels + +### 7.1.1 The Dedicated Channel (DCH) + +The mapping of transport blocks to physical bearers is in principle the same as in 3.84 Mcps TDD but due to the subframe structure the coded bits are mapped onto each of the subframes within the given TTI. + +![Diagram illustrating the mapping of Transport Blocks onto the physical bearer. It shows two radio frames, n and n+1, each containing subframes 2n, 2n+1, 2(n+1), and 2(n+1)+1. Arrows indicate the mapping of Transport Block(s) to Coded Bits, which are then distributed across the subframes of both frames.](42c65f5cb106938992fc73c05c8713d2_img.jpg) + +The diagram shows the mapping of transport blocks to physical bearers. At the top, a box labeled 'Transport Block(s)' points down to a box labeled 'Coded Bits'. From the 'Coded Bits' box, four arrows point to four subframes: 'Sub-frame 2n', 'Sub-frame 2n+1', 'Sub-frame 2(n+1)', and 'Sub-frame 2(n+1)+1'. These subframes are grouped into two radio frames: 'Radio frame n' (containing subframes 2n and 2n+1) and 'Radio frame n+1' (containing subframes 2(n+1) and 2(n+1)+1). Each subframe is represented by a grid of 10 rows and 15 columns, with a single cell highlighted in each grid to show the mapping point. + +Diagram illustrating the mapping of Transport Blocks onto the physical bearer. It shows two radio frames, n and n+1, each containing subframes 2n, 2n+1, 2(n+1), and 2(n+1)+1. Arrows indicate the mapping of Transport Block(s) to Coded Bits, which are then distributed across the subframes of both frames. + +Figure 23 : Mapping of Transport Blocks onto the physical bearer ( TTI= 20ms ) + +### 7.1.2 The Enhanced Uplink Dedicated Channel (E-DCH) + +The enhanced uplink dedicated channel is mapped on one or several E-PUCH, see subclause 5A.3.14. + +For multi-carrier E-DCH transmission, the E-DCH on one carrier is always associated with a number of E-AGCH and up to four E-HICHs on the same carrier. The E-DCH, E-AGCH and E-HICH on the same carrier obey the following timing relationships. + +#### 7.1.2.1 E-DCH/E-AGCH Association and Timing + +The E-DCH is always associated with a number of E-DCH Absolute Grant Channels (E-AGCH) and up to four hybrid ARQ Indicator Channel (E-HICH). A grant of E-DCH transmission resources may be transmitted to the UE on any one of the associated E-AGCH. All relevant Layer 1 control information related to an E-DCH TTI is transmitted in the associated E-AGCH and E-HICH. + +The E-DCH related timeslot information that is carried on the E-AGCH refers to the next valid E-PUCH allocation, which is given by the following limitation: There shall be an offset of $n_{E-AGCH} \geq 7$ time slots between the E-AGCH carrying the E-DCH related information and the first indicated E-PUCH (in time) for a given UE. DwPTS and UpPTS shall not be taken into account in this limitation as illustrated in figure 23A. Note that the figure only shows the E-AGCH that carries the E-DCH related information for the given UE and that DwPTS and UpPTS are not considered in this figure. + +![Figure 23A: Timing for E-AGCH and E-PUCH for different radio frame configurations for a given UE. The diagram shows two horizontal bars representing radio frames. The top bar is solid black. The bottom bar is divided into 10 equal segments by vertical lines. A single vertical line in the bottom bar is highlighted, representing the E-AGCH. The E-PUCH is indicated by a gap in the top bar, starting at the same time as the E-AGCH in the bottom bar.](85b53faf49a839f512153285c78fbbdb_img.jpg) + +Figure 23A: Timing for E-AGCH and E-PUCH for different radio frame configurations for a given UE. The diagram shows two horizontal bars representing radio frames. The top bar is solid black. The bottom bar is divided into 10 equal segments by vertical lines. A single vertical line in the bottom bar is highlighted, representing the E-AGCH. The E-PUCH is indicated by a gap in the top bar, starting at the same time as the E-AGCH in the bottom bar. + +**Figure 23A: Timing for E-AGCH and E-PUCH for different radio frame configurations for a given UE** + +When E-AGCH is allocated in TS0, the timing between E-AGCH and the associated E-PUCH is defined as: E-AGCH is sent in the n-th sub-frame while the E-PUCH is sent in the (n+2)-th sub-frame. + +For the semi-persistent E-DCH resources, the timing between E-AGCH and the first E-PUCH can also use the same limitation: There shall be an offset of $n_{E-AGCH} \geq 7$ time slots between the E-AGCH carrying the semi-persistent E-DCH related information and the first indicated semi-persistent E-PUCH (in time) for a given UE. Once the semi-persistent resources are assigned to UE, UE can use these resources continuously until the semi-persistent resources have been released or reconfigured by Node B or RNC. + +#### 7.1.2.2 E-DCH/E-HICH Association and Timing + +For a given UE, a HARQ acknowledgement indicator (E-HICH) is synchronously linked with the E-DCH TTI transmission to which it relates. + +The associated E-HICH shall reside on the first E-HICH instance of the E-HICH channelisation code to occur after $n_{E-HICH}$ timeslots have elapsed since the start of the last E-PUCH of the corresponding E-DCH TTI (see examples of figure 23B). DwPTS and UpPTS are not considered in the figure. The value of $n_{E-HICH}$ is configurable by higher layers within the range 4 to 15 timeslots. DwPTS and UpPTS shall not be taken into account in this limitation. + +![Figure 23B: Timing for E-DCH and E-HICH for a given UE. The diagram shows two horizontal timelines. The top timeline consists of seven adjacent rectangular blocks representing timeslots. A long double-headed arrow spans above all seven blocks. A shorter single-headed arrow points to the right, starting below the third block and ending below the fifth block. The bottom timeline also consists of seven rectangular blocks, but the fourth block is split into two dashed-line segments. A long double-headed arrow spans above all seven blocks. A shorter single-headed arrow points to the right, starting below the third block and ending below the seventh block.](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +Figure 23B: Timing for E-DCH and E-HICH for a given UE. The diagram shows two horizontal timelines. The top timeline consists of seven adjacent rectangular blocks representing timeslots. A long double-headed arrow spans above all seven blocks. A shorter single-headed arrow points to the right, starting below the third block and ending below the fifth block. The bottom timeline also consists of seven rectangular blocks, but the fourth block is split into two dashed-line segments. A long double-headed arrow spans above all seven blocks. A shorter single-headed arrow points to the right, starting below the third block and ending below the seventh block. + +Figure 23B: Timing for E-DCH and E-HICH for a given UE + +## 7.2 Common Transport Channels + +### 7.2.1 The Broadcast Channel (BCH) + +There are two P-CCPCHs, P-CCPCH 1 and P-CCPCH 2 which are mapped onto timeslot#0 using the channelisation codes $C_{Q=16}^{(k=1)}$ and $C_{Q=16}^{(k=2)}$ with spreading factor 16. The BCH is mapped onto the P-CCPCH1+P-CCPCH2. + +The position of the P-CCPCHs is indicated by the relative phases of the bursts in the DwPTS with respect to the P-CCPCHs midamble sequences, see [8]. One special combination of the phase differences of the burst in the DwPTS with respect to the P-CCPCH midamble indicates the position of the P-CCPCH in the multi-frame and the start position of the interleaving period. + +### 7.2.2 The Paging Channel (PCH) + +If the PICH is associated with an S-CCPCH to which a PCH transport channel is mapped, the mapping of Paging Channels onto S-CCPCHs and the association between PCHs and Paging Indicator Channels is the same as in the 3.84 Mcps TDD option, cf. 6.2.2 'The paging Channel' and 6.2.2.1 'PCH/PICH Association' respectively. + +### 7.2.3 The Forward Channel (FACH) + +The FACH is mapped onto one or several S-CCPCHs. The location of the FACH is indicated on the BCH and both, capacity and location can be changed, if required. FACH may or may not be power controlled. + +### 7.2.4 The Random Access Channel (RACH) + +The RACH is mapped onto PRACH. More than one slot per frame may be administered for the PRACH. The location of slots allocated to PRACH is broadcast on the BCH. The uplink sync codes (SYNC-UL sequences) used by the UEs for UL synchronisation have a well known association with the P-RACHs, as broadcast on the BCH. On the PRACH, both power control and uplink synchronisation control are used. + +### 7.2.5 The Uplink Shared Channel (USCH) + +The uplink shared channel is mapped onto one or several PUSCH, see subclause 5A.3.6 'Physical Uplink Shared Channel (PUSCH)' + +### 7.2.6 The Downlink Shared Channel (DSCH) + +The downlink shared channel is mapped onto one or several PDSCH, see subclause 5A.3.7 'Physical Downlink Shared Channel (PDSCH)' + +### 7.2.7 The High Speed Downlink Shared Channel (HS-DSCH) + +The high speed downlink shared channel is mapped on one or several HS-PDSCH, see subclause 5A.3.9. + +#### 7.2.7.1 HS-DSCH/HS-SCCH Association and Timing + +The HS-DSCH can be associated with a number of High Speed Shared Control Channels (HS-SCCH). In a multi-frequency HS-DSCH cell, HS-DSCH may be mapped on HS-PDSCHs on one or more carrier in CELL\_DCH state and on only one carrier in CELL\_FACH, CELL\_PCH and URA\_PCH state for UE supporting multi-carrier HS-DSCH reception configured by higher layers. HS-DSCH transmission on each carrier is associated with a HS-SCCH subset and the number of HS-SCCHs in one HS-SCCH subset can range from a minimum of one HS-SCCH ( $M=1$ ) to a maximum of four HS-SCCH ( $M=4$ ). All the HS-SCCH subsets for one UE constitute a HS-SCCH set. For UE not supporting multi-carrier HS-DSCH reception, only one HS-SCCH subset is allocated by higher layers. All relevant Layer 1 control information is transmitted in the associated HS-SCCH i.e. the HS-PDSCH does not carry any Layer 1 control information. + +The HS-DSCH related time slot information that is carried on the HS-SCCH refers to the next valid HS-PDSCH allocation, which is given by the following limitation: The indicated HS-PDSCH shall be on the sub-frame next to the HS-SCCH carrying the HS-DSCH related information. The HS-DSCH related time slot information shall not refer to two subsequent sub-frames but shall always refer to the following sub-frame, as illustrated in figure 24. Note that the figure only shows the HS-SCCH that carries the HS-DSCH related information for the given UE and that DwPTS and UpPTS are not considered in this figure. In case of multi-carrier HS-DSCH reception, the timing for HS-DSCH transmission on each carrier and its associated HS-SCCH applies the same rule. + +When the indicated HS-PDSCH includes TS0, the timing between HS-SCCH and HS-PDSCH including TS0 is defined as: HS-SCCH is sent in the $n$ -th sub-frame while HS-PDSCH is sent in the $(n+1)$ -th sub-frame, where the included TS0 is sent in TS0 of the $(n+2)$ -th sub-frame. + +For the semi-persistent HS-DSCH resources, the timing between HS-SCCH and the first HS-PDSCH applies the rule that, if the HS-SCCH is transmitted in subframe $N$ , then the first HS-PDSCH is transmitted in subframe $N+2$ , as illustrated in figure 24A. Once the semi-persistent resources are assigned to UE, UE can use these resources continuously until the semi-persistent resources have been released or reconfigured by Node B or RNC. + +![Figure 24: Timing diagram for HS-SCCH and HS-PDSCH. It shows two sub-frames, Sub-Frame #n and Sub-Frame #n+1. Each sub-frame is divided into 7 slots. In Sub-Frame #n, the third slot is labeled HS-SCCH. In Sub-Frame #n+1, the sixth slot is labeled '1st HS-PDSCH'. A double-headed arrow above the sub-frames indicates the transition from the end of Sub-Frame #n to the start of Sub-Frame #n+1.](87b70d2e8951032d28b4412d82cf1413_img.jpg) + +Figure 24: Timing diagram for HS-SCCH and HS-PDSCH. It shows two sub-frames, Sub-Frame #n and Sub-Frame #n+1. Each sub-frame is divided into 7 slots. In Sub-Frame #n, the third slot is labeled HS-SCCH. In Sub-Frame #n+1, the sixth slot is labeled '1st HS-PDSCH'. A double-headed arrow above the sub-frames indicates the transition from the end of Sub-Frame #n to the start of Sub-Frame #n+1. + +Figure 24: Timing for HS-SCCH and HS-DSCH for different radio frame configurations for a given UE + +![Figure 24A: Timing diagram for HS-SCCH and first semi-persistent HS-PDSCH. It shows a sequence of slots across sub-frames. A horizontal dashed line with double-headed arrows spans from the third slot of one sub-frame (labeled HS-SCCH) to the third slot of the sub-frame after next (labeled 1st HS-PDSCH), indicating a N+2 timing relationship.](1043999278be2d0d419a47a907d4db77_img.jpg) + +Figure 24A: Timing diagram for HS-SCCH and first semi-persistent HS-PDSCH. It shows a sequence of slots across sub-frames. A horizontal dashed line with double-headed arrows spans from the third slot of one sub-frame (labeled HS-SCCH) to the third slot of the sub-frame after next (labeled 1st HS-PDSCH), indicating a N+2 timing relationship. + +Figure 24A: Timing for HS-SCCH and first semi-persistent HS-DSCH for different radio frame configurations for a given UE + +#### 7.2.7.2 HS-SCCH/HS-DSCH/HS-SICH Association and Timing + +The HS-SCCH is always associated with one HS-SICH, carrying the ACK/NACK and Channel Quality information (CQI). The association between the HS-SCCH in DL and HS-SICH in UL shall be pre-defined by higher layers and is common for all UEs. For the HS-DSCH semi-persistent scheduling operation, the associated HS-SICH to the HS-DSCH is conveyed by HS-SICH Indicator on HS-SCCH. + +The UE in CELL\_DCH state and in CELL\_FACH state with a dedicated UE identity shall transmit the HS-DSCH related ACK / NACK on the next available associated HS-SICH with the following limitation: There shall be an offset of $n_{\text{HS-SICH}} \geq 9$ time slots between the last allocated HS-PDSCH (in time) and the HS-SICH for the given UE. DwPTS and UpPTS shall not be taken into account in this limitation. Hence, the HS-SICH transmission shall always be made in the next but one sub-frame, following the HS-DSCH transmission, as illustrated in figure 25. Note that the figure only shows the HS-SICH that carries the HS-DSCH related ACK / NACK for the given UE and that DwPTS and UpPTS are not considered in this figure. In case of multi-carrier HS-DSCH reception, the timing for HS-DSCH transmission on each carrier and its related HS-SICH applies the same rule. For the HS-SCCH order which is an uplink synchronization establishment order for UEs in CELL\_FACH and CELL\_PCH state, the UE shall not transmit associated HS-SICH. + +![Figure 25: Timing for HS-DSCH and HS-SICH for different radio frame configurations for a given UE. The diagram shows three sub-frames: Sub-Frame #n, Sub-Frame #n+1, and Sub-Frame #n+2. In Sub-Frame #n, the 'last HS-PDSCH' is transmitted. In Sub-Frame #n+1, there is a gap indicated by '.....'. In Sub-Frame #n+2, the 'HS-SICH' is transmitted. A horizontal arrow labeled n_HS-SICH indicates the offset in time slots between the end of the last HS-PDSCH in Sub-Frame #n and the start of the HS-SICH in Sub-Frame #n+2.](50ef8602c7c9edd2da0e2133e772c2a2_img.jpg) + +Figure 25: Timing for HS-DSCH and HS-SICH for different radio frame configurations for a given UE. The diagram shows three sub-frames: Sub-Frame #n, Sub-Frame #n+1, and Sub-Frame #n+2. In Sub-Frame #n, the 'last HS-PDSCH' is transmitted. In Sub-Frame #n+1, there is a gap indicated by '.....'. In Sub-Frame #n+2, the 'HS-SICH' is transmitted. A horizontal arrow labeled n\_HS-SICH indicates the offset in time slots between the end of the last HS-PDSCH in Sub-Frame #n and the start of the HS-SICH in Sub-Frame #n+2. + +**Figure 25: Timing for HS-DSCH and HS-SICH for different radio frame configurations for a given UE** + +When the indicated HS-PDSCH includes TS0, the timing between HS-PDSCH including TS0 and HS-SICH is defined as: HS-PDSCH is sent in the n-th sub-frame while HS-SICH is sent in the (n+2)-th sub-frame, where the included TS0 is sent in TS0 of the (n+1)-th sub-frame and there shall be an offset of $n_{\text{HS-SICH}} \geq 9$ time slots between the last allocated HS-PDSCH (in time) and the HS-SICH. + +There shall be an associated HS-SICH for the HS-SCCH command for allocation or release of the semi-persistent HS-PDSCH resources and HS-SCCH command for activation or deactivation of DRX. There shall also be an associated HS-SICH for HS-SCCH type 1 or HS-SCCH type 4 or HS-SCCH type 8 with transport block size information set to all zeros. There is no associated HS-PDSCH in these cases. The timing between the HS-SCCH and the HS-SICH for the given UE as illustrated in figure 25A. The UE shall transmit the HS-SCCH related ACK on the next available associated HS-SICH with the following limitation: There shall be an offset of $n'_{\text{HS-SICH}} \geq 14$ time slots between the HS-SCCH (in time) and the HS-SICH for the given UE. DwPTS and UpPTS shall not be taken into account in this limitation. + +![Figure 25A: Timing for HS-SCCH and HS-SICH for different radio frame configurations for a given UE. The diagram shows a horizontal arrow pointing to the right, representing the timing sequence. No sub-frames or specific channels are explicitly labeled in this partial diagram.](077f85b82901283b4657fd2b45fc0294_img.jpg) + +Figure 25A: Timing for HS-SCCH and HS-SICH for different radio frame configurations for a given UE. The diagram shows a horizontal arrow pointing to the right, representing the timing sequence. No sub-frames or specific channels are explicitly labeled in this partial diagram. + +**Figure 25A: Timing for HS-SCCH and HS-SICH for different radio frame configurations for a given UE** + +When HS-SCCH is allocated in TS0, the timing between HS-SCCH for the HS-SCCH command and the associated HS-SICH is defined as: HS-SCCH is sent in the n-th sub-frame while HS-SICH is sent in the (n+3)-th sub-frame. + +#### 7.2.7.3 PICH/HS-SCCH/HS-DSCH Association and Timing + +When the UE in CELL\_PCH state with a dedicated UE identity detects the PICH identifying DCCH/DTCH/BCCH transmission, the UE shall receive the corresponding HS-SCCH subframes. The association and timing between PICH and HS-SCCH is depicted in figure 25A. If a paging indicator in a certain PICH block is set to '1' it is an indication that UEs associated with this paging indicator shall read their corresponding HS-SCCH in the M frames where M is Reception window size configured by higher layers. The value $N_{\text{GAP}} > 0$ of frames between the end of the PICH block and the beginning of the HS-SCCH is configured by higher layers. Note: for DCCH/DTCH transmission, HS-SCCH shall be HS-SCCH order; while for BCCH transmission, the association and timing between HS-SCCH and HS-DSCH is the same as described in subclause 7.2.7.1. + +![Timing diagram for PICH and HS-SCCH for different radio frame configurations for a given UE. The diagram shows two sets of radio frames. The first set consists of four frames, with a double-headed arrow above it indicating a duration. The second set consists of six frames, also with a double-headed arrow above it. Below these sets is a thick black horizontal bar with a double-headed arrow, representing the timing relationship between the two configurations.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +Timing diagram showing two radio frame sequences. The first sequence on the left consists of 4 adjacent rectangular blocks (frames) with a horizontal double-headed arrow above it. The second sequence on the right consists of 6 adjacent rectangular blocks (frames) with a horizontal double-headed arrow above it. Below both sequences is a long, thick horizontal black line with double-headed arrows at its ends, spanning the width of both frame sequences. + +Timing diagram for PICH and HS-SCCH for different radio frame configurations for a given UE. The diagram shows two sets of radio frames. The first set consists of four frames, with a double-headed arrow above it indicating a duration. The second set consists of six frames, also with a double-headed arrow above it. Below these sets is a thick black horizontal bar with a double-headed arrow, representing the timing relationship between the two configurations. + +Figure 25A: Timing for PICH and HS-SCCH for different radio frame configurations for a given UE + +#### 7.2.7.4 PICH/ HS-DSCH Association and Timing + +When the UE in URA\_PCH or CELL\_PCH state without a dedicated UE identity detects the PICH identifying PCCH transmission, the UE shall receive the corresponding HS-DSCH TTIs. The association and timing between PICH and HS-DSCH is depicted in figure 25B. If a paging indicator in a certain PICH block is set to '1' it is an indication that UEs associated with this paging indicator shall read their corresponding sub-channel and consider that paging message is retransmitted in $2*m$ subframes where $m$ denotes Paging Sub-Channel Size configured by higher layers which is the number of frames that each paging sub-channel occupies. The value $N_{GAP} > 0$ of frames between the end of the PICH block and the beginning of the HS-DSCH is configured by higher layers. + +![Timing diagram for PICH and HS-DSCH for different radio frame configurations for a given UE. The diagram shows a single set of four frames. Above the frames is a double-headed arrow indicating a duration.](6d2057d7e401741861ca63545a5d7d3b_img.jpg) + +Timing diagram showing a single sequence of 4 adjacent rectangular blocks (frames). A horizontal double-headed arrow is positioned above the sequence, indicating its duration. + +Timing diagram for PICH and HS-DSCH for different radio frame configurations for a given UE. The diagram shows a single set of four frames. Above the frames is a double-headed arrow indicating a duration. + +Figure 25B: Timing for PICH and HS-DSCH for different radio frame configurations for a given UE + +# 8 Mapping of transport channels to physical channels for the 7.68 Mcps option + +This clause describes the way in which transport channels are mapped onto physical resources, see figure 26. + +| Transport Channels | Physical Channels | +|--------------------|--------------------------------------------------------| +| DCH _____ | Dedicated Physical Channel (DPCH) | +| BCH _____ | Primary Common Control Physical Channel (P-CCPCH) | +| FACH _____ | Secondary Common Control Physical Channel (S-CCPCH) | +| PCH _____ | | +| RACH _____ | Physical Random Access Channel (PRACH) | +| USCH _____ | Physical Uplink Shared Channel (PUSCH) | +| DSCH _____ | Physical Downlink Shared Channel (PDSCH) | +| | Paging Indicator Channel (PICH) | +| | MBMS Indication Channel (MICH) | +| | Synchronisation Channel (SCH) | +| HS-DSCH _____ | High Speed Physical Downlink Shared Channel (HS-PDSCH) | +| | Shared Control Channel for HS-DSCH (HS-SCCH) | +| | Shared Information Channel for HS-DSCH (HS-SICH) | +| E-DCH _____ | E-DCH Physical Uplink Channel (E-PUCH) | +| | E-DCH Random Access Uplink Control Channel (E-RUCCH) | +| | E-DCH Absolute Grant Channel (E-AGCH) | +| | E-DCH Hybrid ARQ Indicator Channel (E-HICH) | + +Figure 26: Transport channel to physical channel mapping + +## 8.1 Dedicated Transport Channels + +### 8.1.1 The Dedicated Channel (DCH) + +Mapping of dedicated transport channels to physical channels is identical to 3.84Mcps TDD cf. [6.1 Dedicated Transport Channels]. + +### 8.1.2 The Enhanced Uplink Dedicated Channel (E-DCH) + +The enhanced uplink dedicated channel is mapped on one or several E-PUCH, see subclause 5B.4.12. + +#### 8.1.2.1 E-DCH/E-AGCH Association and Timing + +The E-DCH is always associated with a number of E-DCH Absolute Grant Channels (E-AGCH) and with one or two hybrid ARQ indicator channels (E-HICH). A grant of E-DCH transmission resources may be transmitted to the UE on any one of the associated E-AGCH. All relevant Layer 1 control information related to an E-DCH TTI is transmitted in the associated E-AGCH and one of the E-HICHs. + +The E-DCH related time slot information that is carried on the E-AGCH refers to the next valid E-PUCH allocation, which is given by the following limitation: There shall be an offset of $n_{E-AGCH} \geq 6$ time slots between the E-AGCH carrying the E-DCH related information and the first indicated E-PUCH (in time) for a given UE. The E-DCH related time slot information shall not refer to two subsequent radio frames but shall always refer to either the same or the following radio frame, as illustrated in figure 27. Note that the figure only shows the E-AGCH that carries the E-DCH related information for the given UE. + +![Figure 27: Timing for E-AGCH and E-DCH for different radio frame configurations for a given UE. The diagram shows two radio frames, Radio Frame #n and Radio Frame #n+1. In Radio Frame #n, an E-AGCH is shown in the 4th time slot. In Radio Frame #n, the 1st E-PUCH is shown in the 10th time slot. The offset between the E-AGCH and the 1st E-PUCH is labeled n_E-AGCH. In Radio Frame #n+1, the E-AGCH is shown in the 4th time slot, and the 1st E-PUCH is shown in the 10th time slot. The offset between the E-AGCH and the 1st E-PUCH is also labeled n_E-AGCH.](1f1614411edea7edfc86c839a608e1fc_img.jpg) + +Figure 27: Timing for E-AGCH and E-DCH for different radio frame configurations for a given UE. The diagram shows two radio frames, Radio Frame #n and Radio Frame #n+1. In Radio Frame #n, an E-AGCH is shown in the 4th time slot. In Radio Frame #n, the 1st E-PUCH is shown in the 10th time slot. The offset between the E-AGCH and the 1st E-PUCH is labeled n\_E-AGCH. In Radio Frame #n+1, the E-AGCH is shown in the 4th time slot, and the 1st E-PUCH is shown in the 10th time slot. The offset between the E-AGCH and the 1st E-PUCH is also labeled n\_E-AGCH. + +Figure 27: Timing for E-AGCH and E-DCH for different radio frame configurations for a given UE + +#### 8.1.2.2 E-DCH/E-HICH Association and Timing + +E-DCH operations within the cell are associated with one or two channelisation codes carrying E-HICH (E-HICH1 and E-HICH2). If the number of timeslots configured for E-DCH use is 7 or more (this corresponds to the length of the timeslot resource related information field on E-AGCH – see [7]), both E-HICH1 and E-HICH2 channelisation codes shall be configured by higher layers, otherwise only the channelisation code E-HICH1 is configured. + +A single instance of E-HICH1 (and E-HICH2 if configured) channelisation codes exist in the cell per E-DCH TTI (10ms). For a given UE, a HARQ acknowledgement indicator is synchronously linked with the E-DCH TTI transmission to which it relates. There is thus a one-to-one association between an E-DCH TTI transmission and its respective HARQ acknowledgment indicator on one of the associated E-HICHs. + +For each channelisation code carrying E-HICH, the associated instance shall be the first instance of that channelisation code to occur after $n_{E-HICH}$ timeslots have elapsed since the start of the last E-PUCH of the corresponding E-DCH TTI (see examples of figure 28). The value of $n_{E-HICH}$ is configurable by higher layers within the range 4 to 44 timeslots. + +![Figure 28: Timing for E-DCH and E-HICH for a given UE. The diagram shows two radio frames, Radio Frame #n and Radio Frame #n+M. In Radio Frame #n, the last E-PUCH is shown in the 3rd time slot. In Radio Frame #n, the E-HICH is shown in the 8th time slot. The offset between the last E-PUCH and the E-HICH is labeled n_E-HICH. In Radio Frame #n+M, the last E-PUCH is shown in the 2nd time slot, and the E-HICH is shown in the 7th time slot. The offset between the last E-PUCH and the E-HICH is also labeled n_E-HICH.](2dc649aff45a8a0924db45fc3bd6aabb_img.jpg) + +Figure 28: Timing for E-DCH and E-HICH for a given UE. The diagram shows two radio frames, Radio Frame #n and Radio Frame #n+M. In Radio Frame #n, the last E-PUCH is shown in the 3rd time slot. In Radio Frame #n, the E-HICH is shown in the 8th time slot. The offset between the last E-PUCH and the E-HICH is labeled n\_E-HICH. In Radio Frame #n+M, the last E-PUCH is shown in the 2nd time slot, and the E-HICH is shown in the 7th time slot. The offset between the last E-PUCH and the E-HICH is also labeled n\_E-HICH. + +Figure 28: Timing for E-DCH and E-HICH for a given UE + +The HARQ acknowledgement indicator associated with an E-DCH transmission is transmitted using one of 240 signature sequences carried by one of the associated E-HICH channelisation codes. Which signature sequence $r = 0, 1, 2, \dots, 239$ and (in the case that two channelisation codes are configured for E-HICH) which channelisation code is used are calculated for each E-DCH resource allocation using the following information signalled on the associated E\_AGCH: + +- $t_0$ is the bit position ( $1 \dots n_{\text{TRR}}$ ) of the first active timeslot in the timeslot resource related information bitmap (see [7]) on E-AGCH and where bit position 1 corresponds to the lowest-numbered timeslot +- $q_0$ is the allocated channelisation code index ( $1, 2, 3, \dots, Q_0$ ) +- $Q_0$ is the spreading factor of the allocated uplink channelisation code + +The value $r'$ is first calculated as: + +Then: + +- if $r' \leq 239$ , $r = r'$ and channelisation code E-HICH1 is used +- if $r' > 239$ , $r = (r' - 240)$ and channelisation code E-HICH2 is used. + +## 8.2 Common Transport Channels + +### 8.2.1 The Broadcast Channel (BCH) + +The mapping of the broadcast channel (BCH) to physical channels is identical to 3.84Mcps TDD cf. [6.2.1 The Broadcast Channel (BCH)]. + +### 8.2.2 The Paging Channel (PCH) + +The mapping of the paging channel (PCH) to physical channels is identical to 3.84Mcps TDD cf. [6.2.2 The Paging Channel (PCH)]. + +### 8.2.3 The Forward Channel (FACH) + +The mapping of the forward access channel (FACH) to physical channels is identical to 3.84Mcps TDD cf. [6.2.3 The Forward Access Channel (FACH)]. + +### 8.2.4 The Random Access Channel (RACH) + +The mapping of the random access channel (RACH) to physical channels is identical to 3.84Mcps TDD cf. [6.2.4 The Random Access Channel (RACH)]. + +### 8.2.5 The Uplink Shared Channel (USCH) + +The mapping of the uplink shared channel (USCH) to physical channels is identical to 3.84Mcps TDD cf. [6.2.5 The Uplink Shared Channel (USCH)]. + +### 8.2.6 The Downlink Shared Channel (DSCH) + +The mapping of the downlink shared channel (DSCH) to physical channels is identical to 3.84Mcps TDD cf. [6.2.6 The Downlink Shared Channel (DSCH)]. + +### 8.2.7 The High Speed Downlink Shared Channel (HS-DSCH) + +The high speed downlink shared channel is mapped on one or several HS-PDSCH, see subclause 5B.4.8. + +#### 8.2.7.1 HS-DSCH/HS-SCCH Association and Timing + +The HS-DSCH/HS-SCCH association and timing is identical to 3.84Mcps TDD cf. [section 6.2.7.1 HS-DSCH/HS-SCCH Association and Timing] with the exception that the number of HS-SCCHs that are associated with an HS-DSCH for one UE can range from a minimum of one HS-SCCH ( $M=1$ ) to a maximum of eight HS-SCCH ( $M=8$ ). + +#### 8.2.7.2 HS-SCCH/HS-DSCH/HS-SICH Association and Timing + +The HS-SCCH/HS-DSCH/HS-SICH association and timing is identical to 3.84Mcps TDD cf. [6.2.7.2 HS-SCCH/HS-DSCH/HS-SICH Association and Timing]. + +# --- Annex A (normative): Basic Midamble Codes for the 3.84 Mcps option + +## A.1 Basic Midamble Codes for Burst Type 1 and 3 + +In the case of burst type 1 or 3 (see subclause 5.2.2) the midamble has a length of $L_m=512$ , which is corresponding to: + +$K'=8$ ; $W=57$ ; $P=456$ . + +Depending on the possible delay spread timeslots are configured to use $K_{Cell}$ midambles which are generated from the Basic Midamble Codes (see table A.1) + +- for all $k=1,2,\dots,K$ ; $K=2K'$ or +- for $k=1,2,\dots,K'$ , only, or +- for odd $k=1,3,5,\dots,\leq K'$ , only. + +In the beacon slot # $k$ , where the P-CCPCH is located, the number of midambles $K_{Cell}=8$ (cf section 5.6.1). In all of the other timeslots that use burst type 1 or 3, $K_{Cell}$ is individually configured from higher layers. + +Depending on the cell size midambles for PRACH are generated from the Basic Midamble Codes (see table A.1) + +- for $k=1,2,\dots,K'$ or +- for odd $k=1,3,5,\dots,\leq K'$ , only. + +The mapping of these Basic Midamble Codes to Cell Parameters is shown in TS 25.223. + +**Table A.1: Basic Midamble Codes $m_p$ according to equation (5) from subclause 5.2.3 for case of burst type 1 and 3** + +| Code ID | Basic Midamble Codes $m_{PL}$ of length $P=456$ | +|------------|---------------------------------------------------------------------------------------------------------------------| +| $m_{PL0}$ | 8DF65B01E4650910A4BF89992E48F43860B07FE55FA0028E454EDCD1F0A09A6F029668F55427253FB8A71E5EF2EF360E539C489584413C6DC4 | +| $m_{PL1}$ | 4C63F9BC3FD7B655D5401653BE75E1018DC26D271AADA1CF13FD348386759506270F2F953E93A44468E0A76605EAE8526225903B1201077602 | +| $m_{PL2}$ | 8522611FFCAEB55A5F07D966036C852E7B15B893B3ABA9672C327380283D168564B8E1200F0E2205AF1BB23A58679899785CFA2A6C131CFDC4 | +| $m_{PL3}$ | F58107E6B777C221999BDE9340E192DC6C31AB8AE85E70AA9BBEB39727435412A5A27C0EF73AB453ED0D28E5B032B94306EC1304736C91E922 | +| $m_{PL4}$ | 89670985013DFD2223164B68A63BD58C7867E97316742D3ABD6CBDA4FC4E08C0B0CBE44451575C72F887507956BD1F27C466681800B4B016EE | +| $m_{PL5}$ | FCDEF63500D6745CDB962594AF171740241E982E9210FC238C4DD85541F08C1A010F7B3161A7F4DF19BAD916FD308AB1CED2A32538C184E92C | +| $m_{PL6}$ | DB04CE77A5BA7C0E09B6D3551072B11A7A43B6A355C1D6FDCF725D587874999895748DD09832ABC35CEC3008338249612E6FE5005E13B03103 | +| $m_{PL7}$ | D2F61A622D0BA9E448CD29587D398EF8CDC3B6582B6CDD50E9E20BF5FE2B3258041E14D60821DC6725132C22D787CD5D497780D4241E3B420D | +| $m_{PL8}$ | 7318524E62D806FA149ECC5435058A2B74111524B84727FE9A7923B4A1F0D8FCD89208F34BE55CADEB90130F9954BB30605A98C11045FF173D | +| $m_{PL9}$ | 8E832B4FA1A11E0BF318E84F54725C8052E0D099EF0AF54BC342BEE44976C9F38DE701623C7BF6474DF90D2E2222A4915C8080E7CD3EC84DAC | +| $m_{PL10}$ | CFA5BAC90780876C417933C43103B55699A8AD51164E590AF9DA6AF0C18804E1F74862F00CE7ECC899C85B6ABB0CAD5E50836AD7A39878FE2F | +| $m_{PL11}$ | AD539094A19858A75458F1B98E286A4F7DC3A117083D04724CBE83F34102817C5531329CDB437FFF712241B644BDF0C1FEC8598A63C2F21BD7 | +| $m_{PL12}$ | BEB8483139529BDE23E42DA6AB8170DD0BFB30CE28A4502FAF3C8EDA219B9A6D5B849D9C9E4451F74E2408EA046061201E0C1D69CF48F3A94 | +| $m_{PL13}$ | C482462CA7846266060D21688BA00B72E1EC84A3D5B7194C8DA39E21A3CE12BF512C8AAB6A7079F73C0D3E4F40AC555A4BCC453F1DFE3F6C82 | +| $m_{PL14}$ | 9663373935FD5C213AC58C0670206683D579D2526C05B0A81030DDF61A221D8A68EAD8D6F7AA0D662C07C6DCD0115A54D39F03F7122B0675AC | +| $m_{PL15}$ | 387397AE5CD3F2B3912C26B8F87CE82CEFE55507DB08FB0C4CF2FD6858896201ACA7264281D0298440DD3481E5E9DDDB24C16F30EB7A22948A | +| $m_{PL16}$ | AFE9266843C892571B6230D808788C63B9065EA3BDFF687B92B8734A8D7099559FEA22C9416576D0C087EB4503E87E356471B330182A24A3E6 | +| $m_{PL17}$ | 6E6C550A4CB74010F6C3E0328651DF421C456D9A5E8AE9D3946C10189D72B579184552EE3E799970969C870FE8A37B6C4BA890992103486DC0 | +| $m_{PL18}$ | D803CA71B6F99CFB3105D40F4695D61EB0B62E803F79302EE3D2A6BF12EA70D304B181E8B38B3B74F5022B67EB8109808C62532688C563D4BE | +| $m_{PL19}$ | E599ED48D01772055DBE9D343A4EA5EABE643DA38F06904FC7523B08C4101F021B199AF759A00D9AC298881D79413A77470992A75C771492D0 | +| $m_{PL20}$ | 9F30AC4162CE5D185953705F3D45F026F38E9B5721AEFE07370214D526A2C4B344B508B57BFB2492320C05903C79CBEE08C6E7F218B57E14D6 | +| $m_{PL21}$ | B5971060DA84685B4D042ED0189FAF13C961B2EF61CC164E363B22AAB14AC8AF607906C1C6E04F2054C687AA6741A9E70639857DA02B6FFFFA | +| $m_{PL22}$ | 97135FC2226C4B4A5CBA5FCA3732763B87455F73A1148006F3DF214BD4C936D061E04045160E2CE33B9CD09D08FDE2A37F4E998322B4401D27 | +| $m_{PL23}$ | 4D256D57C861B9791151A78D5299C56D116B6178B2A2D04BB95FB76540AF28341DC6EC4E7ED3BF9E508478D9C8F44914805DA82429E1CF320E | +| $m_{PL24}$ | 858EF5C84CE32D18D9ABA110EEA7474CF0CD70254D2928C3F4DFF6BB3A518587CADA19029078AC90A8336C8178203BE3289E601F07D089CB64 | +| $m_{PL25}$ | 920A8796A511650AEF32F93DD3C39C624E07AE03CE8C96139973F54DCB9803C5164ADB502D4FF561564D607037FCD172921F1982B102C3312C | +| $m_{PL26}$ | 485C5DAE76B360A9C56E20B8422EA3E6ACF07CB093B5587CB0E6A5498A4714081EA98DBCD B0482B26E0D097C03444473D233BEF3C8E440DEBF | +| $m_{PL27}$ | 565A9D54EA789892B024F97E728E8E112411942C48BD0C5BC8AA457D8DC9941F0F7424B38643FFE6521CD306FBC56FE10F1428D4C245B5606 | +| $m_{PL28}$ | 5AEF2C0C2C378179A1AC36242E6B3EDB72C42D3624437674F8D51260C0898C201837CBA14E9E23D1EF6451C4ACF27AB031F457A8A1BFD148AE | +| $m_{PL29}$ | 87D8FE685417822A23D925307E6C11081ADAC4702BCCD9BE448E78984D109B50DEF5B7C58BC71EA1F0A6826BA8AD1978843E7697F3E416AADA | + +| Code ID | Basic Midamble Codes $m_{PL}$ of length $P=456$ | +|------------|---------------------------------------------------------------------------------------------------------------------| +| $m_{PL30}$ | 84802B72AF27B5BE724D1FB629E0E627BDB0D9061292562F98350C1D0C9D4B9D8E2BF71123C82EBB161003AE9829E07244D78F19926F8847A2 | +| $m_{PL31}$ | 8CCB5128238BCB088E30972D62792AEF02B9BDDCAD68C9916C00BF91CBE788B0F03851FAAF88605534FD73436C259D270B1013CB14226F658 | +| $m_{PL32}$ | 62F4E6FAC2BF1979CE6854AA2D33534BFB2F946519101A6589131C3640707D40E67ED804AF8736AD213CAF5935741900061967E8285C27E34C | +| $m_{PL33}$ | 4095E5B4EEAFCDF68A34B267EEA28D8444FA533900F41499E260D2E65C256A52E1DD5861F5227C98E00687D107233F51A1167BCF72FB184654 | +| $m_{PL34}$ | 5630E9A79FCAD303404D9E5A802299162657AAC734761C6E90DA8BCE4F61A763E0BB48D3FEB3F78468C828ABA4828DAD06E0F904CFD40421DC | +| $m_{PL35}$ | CD12B24C0BCA8AAC1FCBF0500A3BC684A180E863D888F2506B48C68ECF17F76CB285991FBA18EB6397211FAD002F482D57A258CD45DE3FF1A6 | +| $m_{PL36}$ | AFCF2A50877286CD3405442730C45514F082D9EC296B367C0F64F04C4E0007DCA9E50BEED5C102126E319ACBC64F1729272F2F72C9397029FE | +| $m_{PL37}$ | 18F89EE8589D20882A72A44DCDF0050F0A3D88DBA6531614973D26905FDF41E3F779FF0648E8AF1540928511BCF4C25D9C64AF34AC31B8965 | +| $m_{PL38}$ | F890D550F33F032ECDA3A51FED427D634F64EB29AF1332A23CD961258E4BAED040E7B336918E250EC272A12816B9EBFFA1E0AE401185F08C10 | +| $m_{PL39}$ | ACE5DD61506047E80FB7D41BD3992DF4D7F18EB46CC145C0E9105428C2F8F299141F5D66691904A7DC2513A3B83994ACB1292246B32818FE9D | +| $m_{PL40}$ | 150680FF900C9B46E1E24D54BE2238CB950A934E5CCDE9BC3939EB51CB0AE202B7D339EEC2018B33A0AB9B63DA5D512D64FB58C0E51A1C82C2 | +| $m_{PL41}$ | 51A579EED2663A002D32D10A0753173612F4D5BA167D1807C61F25C4D42C063682E8E9DD019F79D446A046EB3F75E50FEB228DC52F08E694B6 | +| $m_{PL42}$ | CDC644FE4C0C6897604F9D14D714123BF16FFF0E49F35F674908CA60653702FE27BCCA2A47098453AF8661055C8C549EB6A951A8396AD4B94D | +| $m_{PL43}$ | 750A10366C595373C5001CA3E4239764B1409D602CF6052B39BC6A3255A15FE06C782C4C5F847026A7E79838A2933A61C77BB6CBF5915B2DA5 | +| $m_{PL44}$ | B7490686D78E409082C4C48FE18D4C35429C20AADF96076B92FC4E85490664753DB0891A0B27FD849BB7FCA99E3B38F22F8C662852COD35AA6 | +| $m_{PL45}$ | D86E1B575B47D23DA811806A54C231281F03317830E7BD305D3CAA7D6382A5233104CFD54D22DF9F34535E5B390D9040CF1375FEA44CEC29E2 | +| $m_{PL46}$ | 828655960C026EC67B683480992AC2ED2C43ABC606F5220C2945F373470BE7ED5BCCF7C1AA0986BBCC84F11F1658AA568FAA0A60C5F0B5BFA | +| $m_{PL47}$ | D76230E02C8533653AAB99B288AA2ADE25A1C1BF28516C04239240EAF1EFC0B98974B51F886861D8A1E9F5D62CFFEC309F071A9716B325101B | +| $m_{PL48}$ | EA207662865B8A07D69648964DED818EE474A90B94473408871880E63EF0596B9FCFEC3C06B86EA6AD2B06C91672EFB33C70241A5450B59B8A | +| $m_{PL49}$ | 9CB5459549909835FAB22F0D99298C120ACF479F814CCE749079D40688F28101037762F125C776DA9C5FA1FCE0E76E452F8185354FDCDE94E2 | +| $m_{PL50}$ | 227506304AEC1D6F93569B51FDC3405A0F38194F65BE17163A3CB9827A35AECEA757D020FE249377ECD561428A38FEED004EC859C272563185 | +| $m_{PL51}$ | 96B9AEC9938910F0E533422A3977519B05CD4AD3909BC15A7502D48D49C124FA192A8E57027CFEB11DF542010603CE5C9FDF8E626D4FBF8CF4 | +| $m_{PL52}$ | A6AAD06E095A9BE0BD9F8A2ED40C3CBDABE91C700CBB778C8696CC06F3A675C16BDB2918E5F2111005A8727206DC6A9684E05655185C398EEB | +| $m_{PL53}$ | CD168D384A78DA172991AD333EE2A9880905AFE59E2A2A4AC4414C40F82874F98A3CBE7B44F4C7F4710B35FD88AFC0399FAEB070EB9CA4D30A | +| $m_{PL54}$ | 22016CA87AD1549174A8699DD65599697871091457E83E0912E7E77A06531C209394D283D18A38662B73681DD9C5BF330FED978BDA7D487CA8 | +| $m_{PL55}$ | B9401B0843AA6F7827A13BD66C922287E8886C31EB5B90B82B472CCD6DA3D8D4FBF78B8F8496DFA8252B06429D5DD17142F1C908ACCD70EA0C | +| $m_{PL56}$ | E42B9EFD5C5D09AC27B3C7DA28D02493A70521223B9D7A76A9D13E9C171017964D16A70C08EAD02C3DC948889C23E365AFCF01BF20B89B0BF5C | +| $m_{PL57}$ | 9DA0180168DB915E9F3597B59312198E1B5CC00D743C2ECB0DBAADA3E35A2465ED1EAA9D74734D49A313CE4DFF020D0760E3153DC485603943 | +| $m_{PL58}$ | B6C966619ECB98191D719C187C07BD503425650CAA3A2D1F2DF5212B1441D7A0C1D36A4C9C2550240AD17CA43BB3943DFFFBF1E283D81299CC | +| $m_{PL59}$ | DB0E8C41F08A03D477C1AA548799274C4BF3EB68F2636166FDC8D4B1E7132539930297E228BA232BB5C279FA5ECA3AC10E24361AF050A453B8 | +| $m_{PL60}$ | 89BC2E2E7974EEBA833CF32F224C85A289148478527DB48FA6EAEA84C5E288CC3914CB54ADA0476278750187F68FBEA41017E1E58DF1A5A3D | +| $m_{PL61}$ | 70A457D1314A278625443EEB52520815EC92CEF17417B97440DCB531BC1CE83212F63270418D0FBDE71F6DB9E0EA88772E1E4535B6633E4425 | +| $m_{PL62}$ | C388460AD54B36C4452CF0433BD347100ACC24C79C535AD3E1F23FE0425E93A044C553BFA | + +| Code ID | Basic Midamble Codes $m_{PL}$ of length $P=456$ | +|---------|-------------------------------------------------| +| | 116E09AA4BB32F13CFA76FBA1BC17520F45EFD44 | + +| Code ID | Basic Midamble Codes $m_{PL}$ of length $P=456$ | +|------------|-------------------------------------------------------------------------------------------------------------------------| +| $m_{PL63}$ | 0BAFCADCDF9AA2846681782CD3B90CA036A863C78EE1507620BC394D0C6804B4C97A15BC9
C0D7B79E6892EA1BFF1A0DD9573A9213AB140DD0D2 | +| $m_{PL64}$ | 833B0226789A62882FCD27A30885E67872B1A1C2FA484AD498011599DD57E8E2A07A560B4716
7AA5F60EF47177DBB1632D5387A2896348640B | +| $m_{PL65}$ | 8F52820323ABA5E6C6B465821B621600B980E59F53A599DA5646BA103214336836CF17E3386C
E4FB2BC5F25CCB30CF7F500546828EC8786B8E | +| $m_{PL66}$ | E2E9A29C3C8207B9A4508FD2F667A159F068EEE8D00686F46EA904C3692C1D79DFF1B32E510
3720D47B4B58AC35384A26087027E141B3126A8 | +| $m_{PL67}$ | 70E7C39FD2D3AE1DCE341699A544D801A8688A6EE47C5CB3630022147DDC06241FC5337A34
8A462B2472DEC5E104DD520ADA5114DB065D4B0D | +| $m_{PL68}$ | 9E3483CAB164BD053C4971D4D87494CC689033D589EF80E5453376E4A8DCC02183B98C36B0
FF7DDC0AD07FCE8B4D5164371BD03A2110AD1247 | +| $m_{PL69}$ | 04DA1C649B0608938DAADD3FE920A4F681690C54505429DBDCDCF10067AB5714BCDDFE1F2
8692710F794765781C1D233344E119BEE8A8416DC | +| $m_{PL70}$ | 7A18D6D30BDF44410714C3DCA27D8F9EA8542D87122205640B98313C91AD9A0B993A5A7BC
3E035F93B8BBE6D4204BC82A9FA8D4C1A7618CF | +| $m_{PL71}$ | EB9525E10265A48733C8E0E77E459310112A71DCA680F68AC044B64BC0A31D02EEA0F7ACAA
AB7F1E574E94FEA2D1301CB14B03263DA8122B76 | +| $m_{PL72}$ | E706C6ED2D6F89153835079BE0C6D45310845EF2F9F6C6AE91B7419810508BA501C0148BF09
955BAD90D6391BA8EBA5CEFB23221CC75143D7 | +| $m_{PL73}$ | DF071A10AC4120CD1431590BEDCFF9483CA7047B19590D035D309240BDB4264E9A3A2761402
EC97FD8BC51B4AF32E37FBC47162A2357D18751 | +| $m_{PL74}$ | F0F952B2238139F46D8254D1A2C1C22A16BA71EC0C0C900ED1442452D7F44C798BC65FF4067
1B88074BA0B74C6510996EEAC495C5B49C37DEB | +| $m_{PL75}$ | 1C86BD82EDA81FD65418D3837B5552A853791456D93B06C62C650D86CFBEC269AFFD772763
064062C03751B9428C6DA2E60383025F9E404B70 | +| $m_{PL76}$ | B390978DD2552C88AABA7838489A6F5A8E9C41E95FFA2215819FB8A5BFE39C8A706CC658E5
49E966611B843A1468406C41C09D1560BEDA4F1B | +| $m_{PL77}$ | 1A69EC9D053C7E84BAE7A48CCC71857D0C6B06D1065E3EA4633B133AA022B8104F6EE7C69B
6184B746C8822958B0A16686F27C8A0E3B4EFEAD | +| $m_{PL78}$ | C95B2070816DC97C6D8DD2583263E73F9AAAFD13F0548D2EBD835824418F11E54111005FB71
3AB234BE412347358281C7DE331EDD21B8BEA52 | +| $m_{PL79}$ | 56D6408399F23C2ED85EE0F68111D69A91A3AD9A732AC57CA08F86CC28B3CF4E4B02EBBA0
BCE5CAE5BACC4D5200407079C04093A84BB18DBA | +| $m_{PL80}$ | E662E7043867BE250764DA0596D34A582A619B408B505E6211DD6286E93A37F95B1EA680C0C
5F3E777E3F71E8D75495D59043217FC0E222E16 | +| $m_{PL81}$ | 27D5E681C222297AD478A079EF12F1A98F744B66335303322EF8880B931FEBF8322F4302944E
80BED468A0A516D410B183D863795992DA7DDB | +| $m_{PL82}$ | 5100336C05F9E5BF35201906C1C588858E0DAF56130DF5554B9AB21CA15311A90290624CD63
E03F5EDA49DB7A0C32AB5F1CA427A2D5635FDA5 | +| $m_{PL83}$ | C696DC993BFAE9A61B781B9C5C3F5CFAA4C8339D8B03A9B0387883D0482A41AC78D652242
5959846E561D26A30FF79A205C801A85889736B2 | +| $m_{PL84}$ | D562297561AFF42D3168296C1153E4E39BE7B2EB0348BC704625AA08391235075EE0DE0A79A
B03222FEDB27218C56F96EAC2F91CC8FCE64B12 | +| $m_{PL85}$ | DD0B6768FC01CC0A551F8ACC36907129623E975AB8B3FF58037F1859E2FA8C62C2D9D1E850
6916029A2C3F8CAD9A26AE2CC652F48800859F5C | +| $m_{PL86}$ | 923920696EB3AB413786C41854822282BB83F6900D33A232D470BE198BBF086067B72613300C
593B74251E2F079857ADBBBCD86583A9DCAA6DC | +| $m_{PL87}$ | B8EF30C797D8D2C4EF11244F137D806E556A436626D0115A621C92C34D166A68BCEDFA0040
DA8FD6F987B1CD5C2AA1C1B045E64475F0F8DABD | +| $m_{PL88}$ | E1887001D414405ED6419E9EE1D1D346D924ED57ADF04B31B7948099976B2D1501A60DFFB28
7AD44C8783DF0C1EA5AA5D273D1389C8EA22DCC | +| $m_{PL89}$ | 8C2E379A58AA96748141CA84C35987905F984A49D3AD9BFF7807AC244C16C1DF74343C2E1F2
5514F5A0954CFBB3C92E25EF783136844998AC5 | +| $m_{PL90}$ | 78F8A99E0A54E27F51C0726FE7A11EB26B1E29FE65F55AC8AC58011465900B958488A90F6DF
614A58431DC8B6C6B9A6F032EE0E0B1306EC4B4 | +| $m_{PL91}$ | 88F7A31B7B20E0F05CA26E729B4F8A1933962D7BD7BE3E1EB130B28C794C0B4D01CADE0900
6FF97E80117509733F3A9DC225413A0AE08CA662 | +| $m_{PL92}$ | BE4DFCEAC18905AC8D5DA27A794F88A4D3058D2EFA3B075A819DEAE688EAF8940A653ED71
04E7B403D490F0A9030264E1F12B8922C75775E61 | +| $m_{PL93}$ | 5BA4B79FC4550234D8922963BF3537485E3C8745A5DB90D3E2E454B30FF61112F508155B7C2B
3C4C628AF846240C2021ACDE547E5A41F666B8 | +| $m_{PL94}$ | 00556D35649F7610AB24A43C4F16D6AC0571FD126F11880C5CD72100D730E4E4D6BB73C33F8
37FAF1072743B249ADA2E09598B1EB23F1180A7 | +| $m_{PL95}$ | 7A0CC9F21BD69CF3023E944545C2176EF0D4F450B765C28359FB8A32137D043D0E5713E67B3 | + +| Code ID | Basic Midamble Codes $m_{PL}$ of length $P=456$ | +|-------------|---------------------------------------------------------------------------------------------------------------------| +| | F61320985D2C6106605081F87D2296321468A2F | +| $m_{PL96}$ | DA669880995B0671201172BABFF141D5854A245E211879EF3038A7C84170DABDB368455F24653161E7886E15B253F93E3A3C568EFB17CDEB1A | +| $m_{PL97}$ | 4E294E53D1661C1F6F748302A7723DA951C00FDB8BEBBF67A68710BA0F1A255DFB1627059D41A23D3961726DE6FEB10E5D209CC4505B209812 | +| $m_{PL98}$ | 73385DF701414E144768A67EF72924B1653479E962FB1554B7E54BC5284D9B3E41C0C133F878972230721918AA425501B920B204FECE0C7F8A | +| $m_{PL99}$ | F4492160805F258CE592DF4D1200566F81D173458D78EA3ABED79A14AF88170DB1D4A9A5931D2B80C58C27FE17D806E3E6A66CDAAD09F118D4 | +| $m_{PL100}$ | 44D562D9012D8B07B8F44596467C11A163982BB7EAEAC184078B6B8CE46B5D7E17C39CEF576A025491183017FA09931D070B307B86524B03FF | +| $m_{PL101}$ | FCAEEFCC49A13B4FFA12C0CC6A2B90CF4F57D78B1E98294B04675C2F0991661FDC61A452A247F8C29E0284AA21026F368307375AA2C3F1E12C | +| $m_{PL102}$ | C486DF0510DCAD5AB86E178A686D398E11A0ECFAC5A326C10129257E5456B22FB8E147E9190D9929A5DFFE44715FA47D62F04CFC9B1C201414 | +| $m_{PL103}$ | C10AF383DC708E257E15A8AB337BCE684A2F4AC7A22DC2C25C277F8E8D0858E79317CDDDD9AA2EA6CBE604D24AC0945026103E7B4126FD361A4 | +| $m_{PL104}$ | A5C60A181148D9A931B2DDDB9D169648BA54F366B4EFAE88F6861909EE0F07C037EE349D0EC59A823286E366CA3943589EEA7F828C3728085F | +| $m_{PL105}$ | 96136AEBD5E28462B0421DF292BA899FFA660D80EA01620D2C7490E5347127884AA3C3D1FF44BCEEF6C29EC589CDEF200C5742C5964F8B2B52 | +| $m_{PL106}$ | 40F63C04ACAD986255D1E16B769A6D4C11A1D075E804BDC0AC61923E9A67F5D7417756328072455F6E22B1C64E06F367D1B0808295C2D90E22 | +| $m_{PL107}$ | F4882D413578C4888C5F002CF6D0E03778134A860436551FD57537E4CED334B3C9CEBACE615238271717AA762448B86FA53D2074BCE35658A7 | +| $m_{PL108}$ | BCCC92D72C920E685530591FC351743D1E23DE044BF81D32650406113E23ECC757FDE4E386B6E2E7195EE4969717A7BD0812AC312B33A54308 | +| $m_{PL109}$ | 6ED59DE0D44370A861CE2B42CF5E578E764A682AB5777905EE027D7160490EDC6C28989B23805AA697FCD215CB401BC5E4D430624C01B16192 | +| $m_{PL110}$ | DE80C0E273B92CC3C5034F7A20DB3914643C430B425C8B9249EAF73ACE8C3BCF17957242CF534D87A67D4DC0252275262E737F4095450CFA14 | +| $m_{PL111}$ | 9505C4FEF2A397D5059F4729D013292A8321FFF929ACB0A210D0A13E13061227C44A68FBD8CE6B66CE3D783363CD039AB35EE52603E09B758 | +| $m_{PL112}$ | E8BE90D7F954B14D8002A4AC20765ABEED80634498C836D79B0F9338DBC17B28F05CF4E79136779E1C55AA30B6215F890882887B3B53C23E2 | +| $m_{PL113}$ | 9F4B622C1358AE5468DC31E4B2CA320E5E20458C1DE5405BF4F9AD7D45A5BCAA39EC0626FFFC698C16A009CCCB7A18A64E85E70BA71731BA24 | +| $m_{PL114}$ | B91B2624843CF48299AFC2B1442570B41F28F578530D1E322E0B54282372131C71ACB924E70768A243EEC3200E7A5EBFA77111D9FB07FEA8AE | +| $m_{PL115}$ | 965F42DDA3A4650FE2F5103932B68F166FA424B9F0F7045311D962C2A9F66B9BC6C66FB480F9800354E0C54A72251071422CF1DFC44F94C00C | +| $m_{PL116}$ | 08ADCE48699FC30FA0788073BDAADB9177BBB4C1CED41F93085218364B8BAD8488561EF0FE1B0DDAA403C602494CB35697D62AA0A2B93A64CF | +| $m_{PL117}$ | 9A313BED80B1220D77C8ADA4B2E0B3D284A5120A94B741380923C78D3AD32BC3E71EC6EEA520E9D447D8727697598BB987F17506F482003ABD | +| $m_{PL118}$ | 24C9AD4C14EFEC002A3473FCAB04E492F2E269161A2960BA8AF09FD710B444A40C4E8B138418E62301E91FBA97AFDC58759A76D00F676736C7 | +| $m_{PL119}$ | 6514C7733711CE4942CD2123AB37186EB7FECB7E78ABB28744864942FCF4C0F810054AF55B1042EB53064F0857C61D85B2CF0D2DC5826AF22F | +| $m_{PL120}$ | B2C80CDC83E48C36BC6FDA8661208EAD392F3A0571BE41DFAD765E744932ADEA50061E66C05498A5381B2A1F1B446587089DC4E4A2DF03D82 | +| $m_{PL121}$ | 639368BA75CC709A3D9F28EDA237E32C2017A9BF1E382045B9426AEE0A4049DCB4E1D7EBE4647B855212824557497CFA039885A3BA42F98F63 | +| $m_{PL122}$ | 6A70DDC17D0C8024B1C853F0C1948561EF32510151BE0C63BCA9171F20217891D1021EE72586CAFF557F8973336913A94A2A699B8740B054B8 | +| $m_{PL123}$ | 2E32E3A35CCD001172CE310B63B4E406126045A0FA3795BE3E3D9B56F72405FC94FD89946818BAECD24A61BABBEBE2D23052AB01EF73CA0CF4A | +| $m_{PL124}$ | 829395C35205A480AC1351C25E234BF52D384A3DE1C5138A650A6F82F739757D812D9C38231AB9FD81AA0648B11F6F6113F9312C57624FC746 | +| $m_{PL125}$ | D98FFE19C0AAAAB0571A9075ECDFD3E7373F5255DC669116A8C6913F0123E598F930934C5F6A601C37C529C371A0C391B59AC5A9E286D04011 | +| $m_{PL126}$ | C1A108192BCE6C2430A63C189BB33856BE6B8B524703FCB205DAEF37EF544CD43CA09B6181B417398083FF2F781BA4AE89A5CA291DB928D71 | +| $m_{PL127}$ | 42568DF9F61849BF9E7DEE750604BE2E0BC16CC464B1CDE15015E01D6498E9F3E6D6950E5824651F212BA0057CE9529B9CCAB88D8136B8545E | + +## --- A.2 Basic Midamble Codes for Burst Type 2 and 4 + +In the case of burst type 2 (see subclause 5.2.2) the midamble has a length of $L_m=256$ , which is corresponding to: + +$K'=3$ ; $W=64$ ; $P=192$ . + +Depending on the possible delay spread timeslots are configured to use $K_{\text{Cell}}$ midambles which are generated from the Basic Midamble Codes (see table A.2) + +- for all $k=1,2,\dots,K$ ; $K=2K'$ or +- for $k=1,2,\dots,K'$ , only. + +In all timeslots that use burst type 2, $K_{\text{Cell}}$ is individually configured from higher layers. + +In the case of burst type 4 (see subclause 5.2.2) the midamble has a length of $L_m=320$ , which corresponds to: + +$K=K'=1$ ; $W=128$ ; $P=192$ . + +Thus for burst type 4, $K_{\text{Cell}}$ shall have a value of 1 and the midamble is generated from the Basic Midamble Codes (see table A.2). + +The mapping of these Basic Midamble Codes to Cell Parameters is shown in TS 25.223. + +**Table A.2: Basic Midamble Codes $m_p$ according to equation (5) from subclause 5A.2.3 for case of burst types 2 and 4** + +| Code ID | Basic Midamble Codes $m_{ps}$ of length $P=192$ | +|------------|--------------------------------------------------| +| $m_{ps0}$ | 5D253744435A24EF0ECC21F43AA5B8144FBDB348C746080C | +| $m_{ps1}$ | 9D7174187201B5CE0136B7A6D85D39A9DD8D4B00E23835E4 | +| $m_{ps2}$ | AE90B477C294E55D28467476C6011029CDE29B7325DF0683 | +| $m_{ps3}$ | BC8A44125F823E51E568641EC12A6C68EAFDFA2350E3233C | +| $m_{ps4}$ | 898B7317B830D207C9BC7B521D5715680824DC08347B2943 | +| $m_{ps5}$ | 466C7482C8827655BC13F479C7C1417290679A9841297C4A | +| $m_{ps6}$ | AC0734C27C7DC1B818A8492744290DFE866B0EBA62B0B56E | +| $m_{ps7}$ | 0A92106325B15A8C15FC3764724CE67A5056D50A77F9360E | +| $m_{ps8}$ | AE69F62E23035083E6094B89493D33E06FDB6532D473A280 | +| $m_{ps9}$ | B485D4E3614C9C373EA1365FA6FA890E9844084EBA90EB0C | +| $m_{ps10}$ | 66182885E2D28360D2FEAB842C65304FFC956CE8DC8A90C7 | +| $m_{ps11}$ | CC30A9B0A742FCC1E9A408415368391F1299AEA3CB6509FE | +| $m_{ps12}$ | 673928915886947F464FDDAAD29A07D182328EBC5839089A | +| $m_{ps13}$ | 4418861C14D62B46EE6D70D4BF05A3ED801A01BD6CDC5235 | +| $m_{ps14}$ | DAD62DC88F52F2D140062C2330BE6540E6F86192322AFB04 | +| $m_{ps15}$ | A2122BAF24529CEA9855FB43CE40923E7CA7B30D92E40702 | +| $m_{ps16}$ | 6C44AB41E11F54B0929DF65673BD231F92A380132D9F1712 | +| $m_{ps17}$ | 1DC2742E756CDA6421340D0087DD087A615E4B8688CB2F75 | +| $m_{ps18}$ | 2E0105328B56E9E07D9B5A62F38B08AF8D8C2817B54F3302 | +| $m_{ps19}$ | 88315EC30A94CA4EDB2C77079D9BD810A2E280B50DABB213 | +| $m_{ps20}$ | 440E0093D28CB2B2B0A95D18CEB4AB934C33FA45C1CFC7B0 | +| $m_{ps21}$ | CC9BF85D41A96A6EC314F9611D5E1C0672556C8850801BB4 | +| $m_{ps22}$ | 1ABEA04C99BC26972715F01957C0B6B959CC71CD88120817 | +| $m_{ps23}$ | EC5A33DA0BA4470442C5CB324A8E47B0A9F7968FC8108EE8 | +| $m_{ps24}$ | F82086290271DB446B5B1DC15D9BE96414B19B3D5E0F540C | +| $m_{ps25}$ | 11A1A790D6958FD3A9157DF1E05D1378248CA201EBCC7592 | +| $m_{ps26}$ | AA8564882231907BCE78092DC6C9DD4F5A0E4A34AFCFB809 | +| $m_{ps27}$ | 912EE2238212F87BC7CDA7F30441ED184A6AA954EC4D20C8 | +| $m_{ps28}$ | 2D200D8B8891B804673E380A1AF5AB875986E29D37D3FDC9 | +| $m_{ps29}$ | 75E086B6C818423491BF9D6365C52FD1C5E42A576E268170 | +| $m_{ps30}$ | 50ADBF27DA2A3701470186B699118E16DDB0D10F705607B1 | +| $m_{ps31}$ | 656C0692B4E22023590A906D2A74DFD471C883A7B1E0B3A2 | +| $m_{ps32}$ | C21FDACD09A3CDCE74C4794010A3E45769B142505C56A0E6 | +| $m_{ps33}$ | CD9392A87C2D4D7CE5801CDDA8A76339B6F900F008B290E2 | +| $m_{ps34}$ | 956426FEFD8B8D52073E87984E10C4D255064E1372C04A24 | +| $m_{ps35}$ | C4F4D6DF1B754AD6063FD10C331C1428ABB27B0700134B94 | +| $m_{ps36}$ | B65548082B34E9FAF43F33C4070F79099758CFD41B491A11 | +| $m_{ps37}$ | C8317EA111A82B04E78B88B864B1EF5D711BBEB4A0527036 | +| $m_{ps38}$ | 8FB7AD1188E8D1A5219845013672560FD38904E70537403B | +| $m_{ps39}$ | B41A324E0D80AA0598A8D391C1D7FFC82B4A075218E98EC3 | +| $m_{ps40}$ | 49A6350A62E208B011E86528B9A481A0E76D723F6675FF82 | +| $m_{ps41}$ | C344C8C23C42A7B7442E6022E95AE4B08A4BFA786F35F911 | +| $m_{ps42}$ | 28F430CF67D69C9DF60E25656413BC5F932A022DB1406C44 | +| $m_{ps43}$ | 2FA5D70CF0FED4213F32116051450391C2A627D9B670C428 | +| $m_{ps44}$ | 959537D988FDD4F1360B4E84701AE5409229C30EDF8BC404 | +| $m_{ps45}$ | CDD2E0450F9EC12F81391AD4633CB29F315B4A0A890A9A22 | +| $m_{ps46}$ | 158776A20B4B82C563EC08F086830EA66DBD2DCCB4DF6026 | +| $m_{ps47}$ | 431FCACBE48208975950342709D11F19AD5FB047F3B440C9 | +| $m_{ps48}$ | 86B141AC571BA6B42653B12FF04D4F0E6C81F3EB608660A2 | +| $m_{ps49}$ | 86D297ABD34E8510F6CDB0EA617F1F1051C8799117B02211 | +| $m_{ps50}$ | 80B2D9530B34E781311D95CFA3857F277CC07014D324AF5A | +| $m_{ps51}$ | 2B607B93FD8B45601C1E574E14CFC6912C22AEC1045ADC49 | +| $m_{ps52}$ | D234C5C45E105A837E6DD74BC4E534523A20317BA0625A29 | +| $m_{ps53}$ | 768CCDB3E2A7A2B863128382590946B25472BE2BFFC40641 | +| $m_{ps54}$ | 3DA38212E0A987EE1F665D4E13C2AA4446E00A76C948A073 | +| $m_{ps55}$ | 09173135E4A2CFC8F2678750AB5257110906F013587BDE82 | +| $m_{ps56}$ | 522E070B266F35E99C1F3C42D2017F8E415550492B72F086 | +| $m_{ps57}$ | D63E4BD805262A3DEF05C7D86C422E5048921E5531784132 | +| $m_{ps58}$ | 564AF806E28131611E5F884229265D446A50E1E488EAFBBA | +| $m_{ps59}$ | A2603E009D3D30147727B750C35C62299AF754D3E4A54E1C | +| $m_{ps60}$ | 938504B02599D33E28246E4271C375AE81A3BBE8D3F8A920 | +| $m_{ps61}$ | 461516B2CAC6FC42A4B707CC6073BBE573C014892C811776 | +| $m_{ps62}$ | 29186DE4CCAAB2CD0100BB19EA595879D63F0F0CFA881AA5 | + +| Code ID | Basic Midamble Codes $m_{ps}$ of length $P=192$ | +|-------------|--------------------------------------------------| +| $m_{ps63}$ | A064B449CB784A91B803369CDC5EF61A670AAAC044BA3E68 | +| $m_{ps64}$ | 8719C454D88FF5149DB943CB6CADA01D0B9664B357A18203 | +| $m_{ps65}$ | A27EC68720F00A714AA2C45A7EF232286984D7B193F5C916 | +| $m_{ps66}$ | AC8361676AB424E48F0789082B0CD2EFB8D2E627D041DD66 | +| $m_{ps67}$ | ABA1BEB0064733A0620906BF2B29C95883F069D7E4C35D39 | +| $m_{ps68}$ | 9E22EEDED47D92CA1D0B7530EC6062287BD83A04874AE00C | +| $m_{ps69}$ | 0BADEF288B20F5686C5DE3A71219AC2172054326BE831696 | +| $m_{ps70}$ | 953801EB2AF58C2F80E49A6CC46085CB554243E3B3BBEC8C | +| $m_{ps71}$ | 333A504C51C8FAC5025994565C3F600F154F64FAEF4EA484 | +| $m_{ps72}$ | A6583E19647662005474153A6F8DD88A473853E94B720CE7 | +| $m_{ps73}$ | 90ACAF707D18AF34F5848C58166830AF620ACDC1B2DFDDA8 | +| $m_{ps74}$ | 39C5C598A374EA82F3F83378258248DAD3808812DD0E74BB | +| $m_{ps75}$ | F79525DE694629346D73F6256CC0F140F82603197AAA1844 | +| $m_{ps76}$ | B8C2A8F139097699A693022E78588D4058DB0A65FF52F813 | +| $m_{ps77}$ | 449B50C2A52996FA5A828A907F30F9F460EE3D99930DF890 | +| $m_{ps78}$ | 62CEC9574D30184BCB4F94EECF0CC23D2D2A8D0003F0AA33 | +| $m_{ps79}$ | B56D258889703F76A0738EE3A7D355994159A4851833E198 | +| $m_{ps80}$ | 65894AA54C0F6C9A206521C9FC379A8AAF6E621C03CF849C | +| $m_{ps81}$ | 2D47F3414E30CC02C6835D95C9BA204488F0FFCB4852677D | +| $m_{ps82}$ | 12BE4DD8B906B584010F8A330AB67B278E8642FA33D51B68 | +| $m_{ps83}$ | BC928A90A4B10906CAEE638BF768E08542F48F1676006DF0 | +| $m_{ps84}$ | 30C544E437C8ADA143566CD1BC4E9E7BA84139A08505C2F4 | +| $m_{ps85}$ | 84FD5B05506192B753FBA2C719B584E0EDA01814999867D2 | +| $m_{ps86}$ | 191F14DD00034E03AB5BB4342F1138B2CD33784E60CFD75A | +| $m_{ps87}$ | B8ACE7990B6A98A80A61162C4D2D5F88F24E8F7DE4207590 | +| $m_{ps88}$ | EC1DBE72E8EED0C61054FC2695422AC0AD2D888265B21AB0 | +| $m_{ps89}$ | 9A1B4CA467AB7E082AF4278E44D177EA78424508C23E8B08 | +| $m_{ps90}$ | 999EE541C608164AC975214F3A37A677FC2CA03E2C2A4B20 | +| $m_{ps91}$ | 1BDCC20265031432917A2EB828FB356A22DF9CB609C0F8F3 | +| $m_{ps92}$ | EB4A81859C93338B8A1B87C02C815AE09D765F6F2249B958 | +| $m_{ps93}$ | E6A5D1629F4CF09A1F280DE0C480D4C73B26ADE321A50AEE | +| $m_{ps94}$ | BAAB7286DD24C80B15A7958039B904F1CA83C310C8C7AFF2 | +| $m_{ps95}$ | 12220F72619E983717C68FFE1C4148F2354B7B1955B65620 | +| $m_{ps96}$ | A198706E24FAA08BD09EE392414816038E667BB34307D6B2 | +| $m_{ps97}$ | 30B3493B4C035881A7A722E4546527AAE787FA2C0893AC46 | +| $m_{ps98}$ | 5A7318126522843DCB7F00A2D9F9BA8F88963E4152BC923C | +| $m_{ps99}$ | 844844B0CACA702C332CE2692B4166F4B0C63E62BF151BF | +| $m_{ps100}$ | B8297389526410313692F861DC60DA86A23607F7DDE24755 | +| $m_{ps101}$ | 6C1144CF8BC01538D655D29ED62DE6E74A3180EC905BF1E0 | +| $m_{ps102}$ | E9DB3221FACFC5C88691A7013EF09672A130D52C3413AAE2 | +| $m_{ps103}$ | 2FD0508615EC4CD4BF18ADD46D777078869130C8921A4F0E | +| $m_{ps104}$ | 40911B4E0525AC874228F6EF642E59154730CB187C7E417A | +| $m_{ps105}$ | 2034C6A027D4D850F5184AA64C3153231F4651B616BBFCF9 | +| $m_{ps106}$ | 57833235451525A1DFA213FCE0B419B6494BC7B99F488410 | +| $m_{ps107}$ | 6DC3D57F2E39158D036825F8804810D77CA1ECA610ECD894 | +| $m_{ps108}$ | F5C50DE43AA7B731CAB7683524021701F97650499A7070E4 | +| $m_{ps109}$ | F2184D2699785442E09FA22CC2D60A5A13FFF22AE660A470 | +| $m_{ps110}$ | EF0029DE0D79207205458CF4D7328E81A93518D93C9A74BD | +| $m_{ps111}$ | 9D6D8992482FB885AA5E878C3BA2045538B09886C23CDC2D | +| $m_{ps112}$ | C0A5AB67D1CEA126F6476C75443F0A11CBE749412EF03104 | +| $m_{ps113}$ | 1853A5C20CDF968C5A180D8EB5E72BF15517D06680D98412 | +| $m_{ps114}$ | 8CEA1223227ADF37D0DAAB320906E1C79029F480D25181A7 | +| $m_{ps115}$ | 5561038E96A658EF3EC665612FF92B064065D1ACC1F54812 | +| $m_{ps116}$ | C55A6263F08D664A1E53584560DFF5E611640D8281D9A843 | +| $m_{ps117}$ | 4386A8EA59124D043F29056A4598735A4FC7BC11119B90C1 | +| $m_{ps118}$ | D6571B20668BED50BD7C80388C162632BCB069AA67C7FC22 | +| $m_{ps119}$ | 4F9F09ABBC1391EC2CCA5359FB52250E533BF04324154106 | +| $m_{ps120}$ | 662659F42188C9453F6E6DF00C579627045DA1461A3A0EA5 | +| $m_{ps121}$ | 8DCC9274C0C2A9BA6096BF27FACA542CD01CA8653D60A80F | +| $m_{ps122}$ | 5C1210A1E50E505F6B73C90156C9D9F19AE2310BBD820DF0 | +| $m_{ps123}$ | B1E0A7CE26202E223D4FC06D5C9BBA4E5F6D98204D2D5286 | +| $m_{ps124}$ | DB506776958E34552F7E60E4B400D836153218F918E22FA6 | +| $m_{ps125}$ | ECAA60300439B2360B2AC3C43FB6241ACDE5055B295FA71C | + +| Code ID | Basic Midamble Codes $m_{PS}$ of length $P=192$ | +|-------------|--------------------------------------------------| +| $m_{PS126}$ | BF1E6D9AA9CA4AC092BE60500C77D0DC7A6A236520F86722 | +| $m_{PS127}$ | 051C5FA122845A30B4EC306B38016B45667C7754F92F13A0 | + +## A.3 Association between Midambles and Channelisation Codes + +The following mapping schemes apply for the association between midambles and channelisation codes if no midamble is allocated by higher layers. Secondary channelisation codes are marked with a \*. These associations apply both for UL and DL. + +### A.3.1 Association for Burst Type 1/3 and $K_{Cell}=16$ Midambles + +![A hierarchical tree diagram showing the association of midambles to spreading codes. The root node is m^{(1)} - c_1^{(1)}. It branches into two nodes: m^{(1)} - c_2^{(1)} and m^{(5)} - c_2^{(2)}. m^{(1)} - c_2^{(1)} branches into m^{(1)} - c_4^{(1)} and m^{(3)} - c_4^{(2)}. m^{(5)} - c_2^{(2)} branches into m^{(5)} - c_4^{(3)} and m^{(7)} - c_4^{(4)}. m^{(1)} - c_4^{(1)} branches into m^{(1)} - c_8^{(1)} and m^{(2)} - c_8^{(2)}. m^{(3)} - c_4^{(2)} branches into m^{(3)} - c_8^{(3)} and m^{(6)} - c_8^{(4)}. m^{(5)} - c_4^{(3)} branches into m^{(5)} - c_8^{(5)} and m^{(4)} - c_8^{(6)}. m^{(7)} - c_4^{(4)} branches into m^{(7)} - c_8^{(7)} and m^{(8)} - c_8^{(8)}. Finally, each of the 8 leaf nodes at the c_8 level branches into two nodes at the c_{16} level, resulting in 16 leaf nodes: m^{(1)} - c_{16}^{(1)}, m^{(9)} - c_{16}^{(2)}, m^{(2)} - c_{16}^{(3)}, m^{(10)} - c_{16}^{(4)}, m^{(3)} - c_{16}^{(5)}, m^{(11)} - c_{16}^{(6)}, m^{(6)} - c_{16}^{(7)}, m^{(14)} - c_{16}^{(8)}, m^{(5)} - c_{16}^{(9)}, m^{(13)} - c_{16}^{(10)}, m^{(4)} - c_{16}^{(11)}, m^{(12)} - c_{16}^{(12)}, m^{(7)} - c_{16}^{(13)}, m^{(15)} - c_{16}^{(14)}, m^{(8)} - c_{16}^{(15)}, and m^{(16)} - c_{16}^{(16)}.](b8efedb73292a798b3f2050f9335cae6_img.jpg) + +A hierarchical tree diagram showing the association of midambles to spreading codes. The root node is m^{(1)} - c\_1^{(1)}. It branches into two nodes: m^{(1)} - c\_2^{(1)} and m^{(5)} - c\_2^{(2)}. m^{(1)} - c\_2^{(1)} branches into m^{(1)} - c\_4^{(1)} and m^{(3)} - c\_4^{(2)}. m^{(5)} - c\_2^{(2)} branches into m^{(5)} - c\_4^{(3)} and m^{(7)} - c\_4^{(4)}. m^{(1)} - c\_4^{(1)} branches into m^{(1)} - c\_8^{(1)} and m^{(2)} - c\_8^{(2)}. m^{(3)} - c\_4^{(2)} branches into m^{(3)} - c\_8^{(3)} and m^{(6)} - c\_8^{(4)}. m^{(5)} - c\_4^{(3)} branches into m^{(5)} - c\_8^{(5)} and m^{(4)} - c\_8^{(6)}. m^{(7)} - c\_4^{(4)} branches into m^{(7)} - c\_8^{(7)} and m^{(8)} - c\_8^{(8)}. Finally, each of the 8 leaf nodes at the c\_8 level branches into two nodes at the c\_{16} level, resulting in 16 leaf nodes: m^{(1)} - c\_{16}^{(1)}, m^{(9)} - c\_{16}^{(2)}, m^{(2)} - c\_{16}^{(3)}, m^{(10)} - c\_{16}^{(4)}, m^{(3)} - c\_{16}^{(5)}, m^{(11)} - c\_{16}^{(6)}, m^{(6)} - c\_{16}^{(7)}, m^{(14)} - c\_{16}^{(8)}, m^{(5)} - c\_{16}^{(9)}, m^{(13)} - c\_{16}^{(10)}, m^{(4)} - c\_{16}^{(11)}, m^{(12)} - c\_{16}^{(12)}, m^{(7)} - c\_{16}^{(13)}, m^{(15)} - c\_{16}^{(14)}, m^{(8)} - c\_{16}^{(15)}, and m^{(16)} - c\_{16}^{(16)}. + +Figure A.1: Association of Midambles to Spreading Codes for Burst Type 1/3 and $K_{Cell}=16$ + +### A.3.2 Association for Burst Type 1/3 and $K_{Cell}=8$ Midambles + +![Figure A.2: Association of Midambles to Spreading Codes for Burst Type 1/3 and K_Cell=8. This is a hierarchical tree diagram showing the mapping of midambles to spreading codes. The root node is m^{(1)} - c_1^{(1)}. It branches into two nodes: m^{(1)} - c_2^{(1)} and m^{(5)} - c_2^{(2)}. m^{(1)} - c_2^{(1)} branches into m^{(1)} - c_4^{(1)} and m^{(3)} - c_4^{(2)}. m^{(5)} - c_2^{(2)} branches into m^{(5)} - c_4^{(3)} and m^{(7)} - c_4^{(4)}. Each of these four nodes branches into two nodes: m^{(1)} - c_8^{(1)}, m^{(2)} - c_8^{(2)}, m^{(3)} - c_8^{(3)}, m^{(6)} - c_8^{(4)}, m^{(5)} - c_8^{(5)}, m^{(4)} - c_8^{(6)}, m^{(7)} - c_8^{(7)}, and m^{(8)} - c_8^{(8)}. Each of these eight nodes branches into two nodes: m^{(1)} - c_{16}^{(1)}, m^{(1)} - c_{16}^{(2)*}, m^{(2)} - c_{16}^{(3)}, m^{(2)} - c_{16}^{(4)*}, m^{(3)} - c_{16}^{(5)}, m^{(3)} - c_{16}^{(6)*}, m^{(6)} - c_{16}^{(7)}, m^{(6)} - c_{16}^{(8)*}, m^{(5)} - c_{16}^{(9)}, m^{(5)} - c_{16}^{(10)*}, m^{(4)} - c_{16}^{(11)}, m^{(4)} - c_{16}^{(12)*}, m^{(7)} - c_{16}^{(13)}, m^{(7)} - c_{16}^{(14)*}, m^{(8)} - c_{16}^{(15)}, and m^{(8)} - c_{16}^{(16)*}.](d9cfc30025244dcd75766061f27ee09f_img.jpg) + +Figure A.2: Association of Midambles to Spreading Codes for Burst Type 1/3 and K\_Cell=8. This is a hierarchical tree diagram showing the mapping of midambles to spreading codes. The root node is m^{(1)} - c\_1^{(1)}. It branches into two nodes: m^{(1)} - c\_2^{(1)} and m^{(5)} - c\_2^{(2)}. m^{(1)} - c\_2^{(1)} branches into m^{(1)} - c\_4^{(1)} and m^{(3)} - c\_4^{(2)}. m^{(5)} - c\_2^{(2)} branches into m^{(5)} - c\_4^{(3)} and m^{(7)} - c\_4^{(4)}. Each of these four nodes branches into two nodes: m^{(1)} - c\_8^{(1)}, m^{(2)} - c\_8^{(2)}, m^{(3)} - c\_8^{(3)}, m^{(6)} - c\_8^{(4)}, m^{(5)} - c\_8^{(5)}, m^{(4)} - c\_8^{(6)}, m^{(7)} - c\_8^{(7)}, and m^{(8)} - c\_8^{(8)}. Each of these eight nodes branches into two nodes: m^{(1)} - c\_{16}^{(1)}, m^{(1)} - c\_{16}^{(2)\*}, m^{(2)} - c\_{16}^{(3)}, m^{(2)} - c\_{16}^{(4)\*}, m^{(3)} - c\_{16}^{(5)}, m^{(3)} - c\_{16}^{(6)\*}, m^{(6)} - c\_{16}^{(7)}, m^{(6)} - c\_{16}^{(8)\*}, m^{(5)} - c\_{16}^{(9)}, m^{(5)} - c\_{16}^{(10)\*}, m^{(4)} - c\_{16}^{(11)}, m^{(4)} - c\_{16}^{(12)\*}, m^{(7)} - c\_{16}^{(13)}, m^{(7)} - c\_{16}^{(14)\*}, m^{(8)} - c\_{16}^{(15)}, and m^{(8)} - c\_{16}^{(16)\*}. + +Figure A.2: Association of Midambles to Spreading Codes for Burst Type 1/3 and $K_{Cell}=8$ + +### A.3.3 Association for Burst Type 1/3 and $K_{Cell}=4$ Midambles + +![Figure A.3: Association of Midambles to Spreading Codes for Burst Type 1/3 and K_Cell=4. This is a hierarchical tree diagram showing the mapping of midambles to spreading codes. The root node is m^{(1)} - c_1^{(1)}. It branches into two nodes: m^{(1)} - c_2^{(1)} and m^{(5)} - c_2^{(2)}. m^{(1)} - c_2^{(1)} branches into m^{(1)} - c_4^{(1)} and m^{(3)} - c_4^{(2)}. m^{(5)} - c_2^{(2)} branches into m^{(5)} - c_4^{(3)} and m^{(7)} - c_4^{(4)}. Each of these four nodes branches into two nodes: m^{(1)} - c_8^{(1)}, m^{(1)} - c_8^{(2)*}, m^{(3)} - c_8^{(3)}, m^{(3)} - c_8^{(4)*}, m^{(5)} - c_8^{(5)}, m^{(5)} - c_8^{(6)*}, m^{(7)} - c_8^{(7)}, and m^{(7)} - c_8^{(8)*}. Each of these eight nodes branches into two nodes: m^{(1)} - c_{16}^{(1)}, m^{(1)} - c_{16}^{(2)*}, m^{(1)} - c_{16}^{(3)*}, m^{(1)} - c_{16}^{(4)*}, m^{(3)} - c_{16}^{(5)}, m^{(3)} - c_{16}^{(6)*}, m^{(3)} - c_{16}^{(7)*}, m^{(3)} - c_{16}^{(8)*}, m^{(5)} - c_{16}^{(9)}, m^{(5)} - c_{16}^{(10)*}, m^{(5)} - c_{16}^{(11)*}, m^{(5)} - c_{16}^{(12)*}, m^{(7)} - c_{16}^{(13)}, m^{(7)} - c_{16}^{(14)*}, m^{(7)} - c_{16}^{(15)*}, and m^{(7)} - c_{16}^{(16)*}.](91c33f8e1713989e8192322ec2d1212b_img.jpg) + +Figure A.3: Association of Midambles to Spreading Codes for Burst Type 1/3 and K\_Cell=4. This is a hierarchical tree diagram showing the mapping of midambles to spreading codes. The root node is m^{(1)} - c\_1^{(1)}. It branches into two nodes: m^{(1)} - c\_2^{(1)} and m^{(5)} - c\_2^{(2)}. m^{(1)} - c\_2^{(1)} branches into m^{(1)} - c\_4^{(1)} and m^{(3)} - c\_4^{(2)}. m^{(5)} - c\_2^{(2)} branches into m^{(5)} - c\_4^{(3)} and m^{(7)} - c\_4^{(4)}. Each of these four nodes branches into two nodes: m^{(1)} - c\_8^{(1)}, m^{(1)} - c\_8^{(2)\*}, m^{(3)} - c\_8^{(3)}, m^{(3)} - c\_8^{(4)\*}, m^{(5)} - c\_8^{(5)}, m^{(5)} - c\_8^{(6)\*}, m^{(7)} - c\_8^{(7)}, and m^{(7)} - c\_8^{(8)\*}. Each of these eight nodes branches into two nodes: m^{(1)} - c\_{16}^{(1)}, m^{(1)} - c\_{16}^{(2)\*}, m^{(1)} - c\_{16}^{(3)\*}, m^{(1)} - c\_{16}^{(4)\*}, m^{(3)} - c\_{16}^{(5)}, m^{(3)} - c\_{16}^{(6)\*}, m^{(3)} - c\_{16}^{(7)\*}, m^{(3)} - c\_{16}^{(8)\*}, m^{(5)} - c\_{16}^{(9)}, m^{(5)} - c\_{16}^{(10)\*}, m^{(5)} - c\_{16}^{(11)\*}, m^{(5)} - c\_{16}^{(12)\*}, m^{(7)} - c\_{16}^{(13)}, m^{(7)} - c\_{16}^{(14)\*}, m^{(7)} - c\_{16}^{(15)\*}, and m^{(7)} - c\_{16}^{(16)\*}. + +Figure A.3: Association of Midambles to Spreading Codes for Burst Type 1/3 and $K_{Cell}=4$ + +### A.3.4 Association for Burst Type 2 and $K_{\text{Cell}}=6$ Midambles + +![Figure A.4: Association of Midambles to Spreading Codes for Burst Type 2 and KCell=6. This tree diagram shows the hierarchical association of midambles to spreading codes. The root node is m^(1) - c_1^(1). It branches into two main paths: m^(1) - c_2^(1) and m^(2) - c_2^(2). The m^(1) - c_2^(1) path further branches into m^(1) - c_4^(1) and m^(3) - c_4^(2). The m^(1) - c_4^(1) path leads to m^(1) - c_8^(1) and m^(5) - c_8^(2), which further branch into m^(1) - c_16^(1), m^(1) - c_16^(2)*, m^(5) - c_16^(3), and m^(5) - c_16^(4)*. The m^(3) - c_4^(2) path leads to m^(3) - c_8^(3) and m^(3) - c_8^(4)*, which further branch into m^(3) - c_16^(5), m^(3) - c_16^(6)*, m^(3) - c_16^(7)*, and m^(3) - c_16^(8)*. The m^(2) - c_2^(2) path branches into m^(2) - c_4^(3) and m^(4) - c_4^(4). The m^(2) - c_4^(3) path leads to m^(2) - c_8^(5) and m^(6) - c_8^(6), which further branch into m^(2) - c_16^(9), m^(2) - c_16^(10)*, m^(6) - c_16^(11), and m^(6) - c_16^(12)*. The m^(4) - c_4^(4) path leads to m^(4) - c_8^(7) and m^(4) - c_8^(8)*, which further branch into m^(4) - c_16^(13), m^(4) - c_16^(14)*, m^(4) - c_16^(15)*, and m^(4) - c_16^(16)*.](1ea7909aea2fb749a6fe98fbdb8cacae_img.jpg) + +Figure A.4: Association of Midambles to Spreading Codes for Burst Type 2 and KCell=6. This tree diagram shows the hierarchical association of midambles to spreading codes. The root node is m^(1) - c\_1^(1). It branches into two main paths: m^(1) - c\_2^(1) and m^(2) - c\_2^(2). The m^(1) - c\_2^(1) path further branches into m^(1) - c\_4^(1) and m^(3) - c\_4^(2). The m^(1) - c\_4^(1) path leads to m^(1) - c\_8^(1) and m^(5) - c\_8^(2), which further branch into m^(1) - c\_16^(1), m^(1) - c\_16^(2)\*, m^(5) - c\_16^(3), and m^(5) - c\_16^(4)\*. The m^(3) - c\_4^(2) path leads to m^(3) - c\_8^(3) and m^(3) - c\_8^(4)\*, which further branch into m^(3) - c\_16^(5), m^(3) - c\_16^(6)\*, m^(3) - c\_16^(7)\*, and m^(3) - c\_16^(8)\*. The m^(2) - c\_2^(2) path branches into m^(2) - c\_4^(3) and m^(4) - c\_4^(4). The m^(2) - c\_4^(3) path leads to m^(2) - c\_8^(5) and m^(6) - c\_8^(6), which further branch into m^(2) - c\_16^(9), m^(2) - c\_16^(10)\*, m^(6) - c\_16^(11), and m^(6) - c\_16^(12)\*. The m^(4) - c\_4^(4) path leads to m^(4) - c\_8^(7) and m^(4) - c\_8^(8)\*, which further branch into m^(4) - c\_16^(13), m^(4) - c\_16^(14)\*, m^(4) - c\_16^(15)\*, and m^(4) - c\_16^(16)\*. + +Figure A.4: Association of Midambles to Spreading Codes for Burst Type 2 and $K_{\text{Cell}}=6$ + +### A.3.5 Association for Burst Type 2 and $K_{\text{Cell}}=3$ Midambles + +![Figure A.5: Association of Midambles to Spreading Codes for Burst Type 2 and KCell=3. This tree diagram shows the hierarchical association of midambles to spreading codes. The root node is m^(1) - c_1^(1). It branches into two main paths: m^(1) - c_2^(1) and m^(2) - c_2^(2). The m^(1) - c_2^(1) path further branches into m^(1) - c_4^(1) and m^(3) - c_4^(2). The m^(1) - c_4^(1) path leads to m^(1) - c_8^(1) and m^(1) - c_8^(2)*, which further branch into m^(1) - c_16^(1), m^(1) - c_16^(2)*, m^(1) - c_16^(3)*, and m^(1) - c_16^(4)*. The m^(3) - c_4^(2) path leads to m^(3) - c_8^(3) and m^(3) - c_8^(4)*, which further branch into m^(3) - c_16^(5), m^(3) - c_16^(6)*, m^(3) - c_16^(7)*, and m^(3) - c_16^(8)*. The m^(2) - c_2^(2) path branches into m^(2) - c_4^(3) and m^(2) - c_4^(4)*. The m^(2) - c_4^(3) path leads to m^(2) - c_8^(5) and m^(2) - c_8^(6)*, which further branch into m^(2) - c_16^(9), m^(2) - c_16^(10)*, m^(2) - c_16^(11)*, and m^(2) - c_16^(12)*. The m^(2) - c_4^(4)* path leads to m^(2) - c_8^(7)* and m^(2) - c_8^(8)*, which further branch into m^(2) - c_16^(13)*, m^(2) - c_16^(14)*, m^(2) - c_16^(15)*, and m^(2) - c_16^(16)*.](ee0bf6a260cff72af8f0df0639b6a7c5_img.jpg) + +Figure A.5: Association of Midambles to Spreading Codes for Burst Type 2 and KCell=3. This tree diagram shows the hierarchical association of midambles to spreading codes. The root node is m^(1) - c\_1^(1). It branches into two main paths: m^(1) - c\_2^(1) and m^(2) - c\_2^(2). The m^(1) - c\_2^(1) path further branches into m^(1) - c\_4^(1) and m^(3) - c\_4^(2). The m^(1) - c\_4^(1) path leads to m^(1) - c\_8^(1) and m^(1) - c\_8^(2)\*, which further branch into m^(1) - c\_16^(1), m^(1) - c\_16^(2)\*, m^(1) - c\_16^(3)\*, and m^(1) - c\_16^(4)\*. The m^(3) - c\_4^(2) path leads to m^(3) - c\_8^(3) and m^(3) - c\_8^(4)\*, which further branch into m^(3) - c\_16^(5), m^(3) - c\_16^(6)\*, m^(3) - c\_16^(7)\*, and m^(3) - c\_16^(8)\*. The m^(2) - c\_2^(2) path branches into m^(2) - c\_4^(3) and m^(2) - c\_4^(4)\*. The m^(2) - c\_4^(3) path leads to m^(2) - c\_8^(5) and m^(2) - c\_8^(6)\*, which further branch into m^(2) - c\_16^(9), m^(2) - c\_16^(10)\*, m^(2) - c\_16^(11)\*, and m^(2) - c\_16^(12)\*. The m^(2) - c\_4^(4)\* path leads to m^(2) - c\_8^(7)\* and m^(2) - c\_8^(8)\*, which further branch into m^(2) - c\_16^(13)\*, m^(2) - c\_16^(14)\*, m^(2) - c\_16^(15)\*, and m^(2) - c\_16^(16)\*. + +Figure A.5: Association of Midambles to Spreading Codes for Burst Type 2 and $K_{\text{Cell}}=3$ + +Note that the association for burst type 2 can be derived from the association for burst type 1 and 3, using the following table: + +| | | | | | | | | | +|----------------|------|------|------|------|------|------|------|------| +| Burst Type 1/3 | m(1) | m(2) | m(3) | m(4) | m(5) | m(6) | m(7) | m(8) | +| Burst Type 2 | m(1) | m(5) | m(3) | m(6) | m(2) | m(4) | - | - | + +### A.3.6 Association for Burst Type 4 and $K_{\text{Cell}}=1$ Midamble + +For burst type 4 there is only a single midamble defined, thus all channelisation codes are associated with the same midamble. + +# --- Annex AA (normative): Basic Midamble Codes for the 1.28 Mcps option + +## AA.1 Basic Midamble Codes + +The midamble has a length of $L_m=144$ , which is corresponding to: + +$$K=2, 4, 6, 8, 10, 12, 14, 16, \quad W = \left\lfloor \frac{P}{K} \right\rfloor, P=128$$ + +Note: that $\lfloor x \rfloor$ denotes the largest integer number less or equal to $x$ . + +Depending on the possible delay spread timeslots are configured to use $K$ midambles. In timeslot 0 the number of midambles $K=8$ (cf section 6.6.1). In all of the other timeslots, $K$ is individually configured from higher layers. + +The $K$ midambles are generated from one of the basic midamble codes shown in table AA.1. + +The mapping of these Basic Midamble Codes to Cell Parameters is shown in [8]. + +**Table AA.1: Basic Midamble Codes $m_p$ according to equation (5) from subclause 5A.2.3** + +| Code ID | Basic Midamble Codes $m_p$ of length $P=128$ | +|-----------|----------------------------------------------| +| $m_{P0}$ | B2AC420F7C8DEBFA69505981BCD028C3 | +| $m_{P1}$ | 0C2E988E0DBA046643F57B0EA6A435E2 | +| $m_{P2}$ | D5CEC680C36A4454135F86DD37043962 | +| $m_{P3}$ | E150D08CAC2A00FF9B32592A631CF85B | +| $m_{P4}$ | E0A9C3A8F6E40329B2F2943246003D44 | +| $m_{P5}$ | FE22658100A3A683EA759018739BD690 | +| $m_{P6}$ | B46062F89BB2A1139D76A1EF32450DA0 | +| $m_{P7}$ | EE63D75CC099092579400D956A90C3E0 | +| $m_{P8}$ | D9C0E040756D427A2611DAA35E6CD614 | +| $m_{P9}$ | EB56D03A498EC4FEC98AE220BC390450 | +| $m_{P10}$ | F598703DB0838112ED0BABB98642B665 | +| $m_{P11}$ | A0BC26A992D4558B9918986C14861EFF | +| $m_{P12}$ | 541350D109F1DD68099796637B824F88 | +| $m_{P13}$ | 892D344A962314662F01F9455F7BC302 | +| $m_{P14}$ | 49F270E29CCD742A40480DD4215E1632 | +| $m_{P15}$ | 6A5C0410C6C39AA04E77423C355926DE | +| $m_{P16}$ | 7976615538203103D4DBCC219B16A9E1 | +| $m_{P17}$ | A6C3C3175845400BD2B738C43EE2645F | +| $m_{P18}$ | A0FD56258D228642C6F641851C3751ED | +| $m_{P19}$ | EFA48C3FC84AC625783C6C9510A2269A | +| $m_{P20}$ | 62A8EB1A420334B23396E8D76BC19740 | +| $m_{P21}$ | 9E96235699D5D41C9816C921023BC741 | +| $m_{P22}$ | 4362AE4CAE0DCC32D60A3FED1341A848 | +| $m_{P23}$ | 454C068E6C4F190942E0904B95D61DFB | +| $m_{P24}$ | 607FEEA6E2E99206718A49C0D6A25034 | +| $m_{P25}$ | E1D1BCDA39A09095B5C81645103A077C | +| $m_{P26}$ | 994B445E558344DE211C8286DDD3D1A3 | +| $m_{P27}$ | C15233273581417638906ADB61FDCA3C | +| $m_{P28}$ | 8B79A274D542F096FB1388098230F8A1 | +| $m_{P29}$ | DF58AC1C5F44B2A40266385CE1DA5640 | +| $m_{P30}$ | B5949A1CC69962C464401D05FF5C1A7A | +| $m_{P31}$ | 85AC489841ED3EAA2D83BBB0039CC707 | +| $m_{P32}$ | AE371CC144BC95923CA8108D8B49FE82 | +| $m_{P33}$ | 7F188484A649D1C22BDA1F09D49B5117 | +| $m_{P34}$ | ADAA3C657089DEF7C0284903A491C9B0 | +| $m_{P35}$ | C3F96893C7504DC3B51488604AF64F4C | +| $m_{P36}$ | B4002F5AE0CE8623AC979D368E9148C1 | +| $m_{P37}$ | 0EEBCC0C795C02A106C24ABB36D08C6E | +| $m_{P38}$ | 4B0F537E384A893F58971580D9894433 | +| $m_{P39}$ | 08E0035AB29B7ECC53C15DAA0687CC8F | +| $m_{P40}$ | 8611ACBC4C82781D77654EE862506D60 | +| $m_{P41}$ | 63315261A8F1CB02549802DBFD197C07 | +| $m_{P42}$ | 9A2609A434F43E7DCADC0E22B2EF4012 | +| $m_{P43}$ | F4C9F0A127A88461209ABF8C69CE4D00 | +| $m_{P44}$ | C79124EE3FFC28C5C4524D2B01670D42 | +| $m_{P45}$ | C91985C4FED53D09361914354BA80E79 | +| $m_{P46}$ | 82AA517260779ECFF26212C1A10BDC29 | +| $m_{P47}$ | 561DE2040ACB458E0DBD354E43E111D9 | +| $m_{P48}$ | 2E58C7202D17392BC1235782CEFABB09 | +| $m_{P49}$ | C4FAA121C698047650F6503126A577C1 | +| $m_{P50}$ | E7B75206A9B410E44346E0DAE842A23C | +| $m_{P51}$ | 3F8B1C32682B28D098D3805ED130EA7F | +| $m_{P52}$ | 8D5FC2C1C6715F824B401434C8D4BB82 | +| $m_{P53}$ | 0B2A43453ACC028FE6EB6E1CB0740B59 | +| $m_{P54}$ | BC56948FC700BA4883262EE73E12D82A | +| $m_{P55}$ | 558D136710272912FA4F183D1189A7FD | +| $m_{P56}$ | 5709E7F82DC6500B7B12A3072D182645 | +| $m_{P57}$ | 86D4F161C844AE5E20EE39FD5493B044 | +| $m_{P58}$ | 8729B6EDC382B152185885F013DAE222 | +| $m_{P59}$ | 154C45B50720F4C362C14C77FE8335A1 | +| $m_{P60}$ | C6A0962890351F4EB802DE43A7662C9E | +| $m_{P61}$ | D19D69D6B380B4B22457CB80033519F0 | +| $m_{P62}$ | C7D89509FB0DAE9255998E0A00C2B262 | + +| | | +|-------------------|----------------------------------| +| m P63 | DFD481C652C0C905D61D66F1732C4AA2 | +| m P64 | 06C848619AF1D6C910A8EAC4B622FC06 | +| m P65 | 0635E29D4E7AC8ABC189890241F45ECA | +| m P66 | B272B020586AAD7B093AC2F459076638 | +| m P67 | B608ACE46E1A6BC96181EEDD88B54140 | +| m P68 | 0A516092B3ED7849B168AFE223B8670E | +| m P69 | D1A658C5009E04D0D7D5E9205EE663E8 | +| m P70 | AC316DC39B91EB60B1AABD8280740432 | +| m P71 | E3F06825476A026CD287625E514519FC | +| m P72 | A56D092080DDE8994F387C175CC56833 | +| m P73 | 15EA799DE587C506D0CD99A408217B05 | +| m P74 | A59C020BAB9AF6D3F813C391CA244CD2 | +| m P75 | 74B0101EB9F3167434B94BABC8378882 | +| m P76 | CE752975C8DA9B0100386DB82A8C3D20 | +| m P77 | BBB38DCDB1E9118570AC147DC05241A4 | +| m P78 | 944ABBF0866098101F6971731AB2E986 | +| m P79 | 2BB147B2A30C68B4853F90481A166EB6 | +| m P80 | 444840ACCF3F23C45B56D7704BF18283 | +| m P81 | 87604F7450D1AD188C452981A5C7FC9B | +| m P82 | 8C3842EBC948A65BC4C8B387F11B7090 | +| m P83 | 10B4767D071CF5DB2288E4029576135A | +| m P84 | 6F07AAB697CD0089572C6B062E2018E4 | +| m P85 | D3D65B442057E613A8655060C8D29E27 | +| m P86 | 5EDA330514C604BF4E0894E09EC57A74 | +| m P87 | B0899CD094060724DED82AE85F18A43A | +| m P88 | B2D999B86DF902BC25015CAE3A0823C4 | +| m P89 | C23CD40F04242B92D46EED82CD9A9A18 | +| m P90 | D22DDCC5CB82960125DD24655F3C8788 | +| m P91 | 54987218FBD99AE4340FD4C9458E9850 | +| m P92 | BE4341822997A7B11EA1E8A1A2767005 | +| m P93 | 255200FBA6EE48E6DE0A82B0461B8D0F | +| m P94 | 6FBD58A663932423503690CF9C171701 | +| m P95 | D215033A4AA87EC1C232BAC7EDA09370 | +| m P96 | CA0959B01AE48E80204F1E4A3F29CE55 | +| m P97 | 582043413B9B825903E3A3545ED59463 | +| m P98 | 5016541922971C703D16E284CBDF633B | +| m P99 | 7347EF160A1733CA98D43608A83A920B | +| m P100 | 908B22AD433CCA00B3FD47C691F1A290 | +| m P101 | BB22A272FC6923DF1B43BA4118806570 | +| m P102 | 0FA75C87474836B47DC7624D61193802 | +| m P103 | A22EBA0658A4D0FF1E9CA5030A65CC06 | +| m P104 | 6C9C51CA15F1F4981F4C46180A6A6697 | +| m P105 | 4C847ACF8BC15359C405322851C9BDE2 | +| m P106 | C1D29499C0082C9DE473ED15B14D63E0 | +| m P107 | 7E85ECC98AC761005076C5572869A431 | +| m P108 | D8F11121595B8F49F78A7039E44126A0 | +| m P109 | 1A0BC814445FD71C8E5B1A9163ED2059 | +| m P110 | A7591F27F8B0C00C68CC41697954FA04 | +| m P111 | 6CA2CE595E7406D79C4840183D41B9D0 | +| m P112 | C093D3CC701FC20E66F5AB22516C5460 | +| m P113 | D0E0CDE9B595546B96C4F8066B469020 | +| m P114 | E99F743A451431C8B427054A4E6F2007 | +| m P115 | C0D21A344A2C07DF2A6EBE6250C7B91E | +| m P116 | F031223E282CF7A4D8EF174A908668AE | +| m P117 | E4BD244AC16C55C7137FB068FD44280C | +| m P118 | C44920DE2028F19FC2AAB36A0DCFDAD0 | +| m P119 | 3FA7054E77135250699E6C8A11600742 | +| m P120 | D5740B4D8870C1C5B5A214C4266FC537 | +| m P121 | F0B7942D43BB6F38446442EB8126AB80 | +| m P122 | 83DB9534EAD6238FA8968798CDF04848 | +| m P123 | EB9663CDDC2B291690703125BABC800 | +| m P124 | 84D547225D4BBD20DEF1A583240C6E0F | +| m P125 | B51F6A771838BE934724AE6A2669802 | +| m P126 | D92AC05E10496794BBD115233B1C068 | + +| | | +|-------------------|----------------------------------| +| m P127 | D3ACF0078EDA9856BBB0AF8651132103 | +|-------------------|----------------------------------| + +###### **Table AA.1a: Basic Preamble Codes** + +| Code ID | Basic Preamble Codes of length P=64 | +|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $p_{P0}$ | 1.000000+j0.000000, 0.989177+j0.146730, 0.923880+j0.382683, 0.740951+j0.671559, 0.382683+j0.923880, -0.146730+j0.989177, -0.707107+j0.707107, -0.998795+j0.049068, -0.707107-j0.707107, 0.146731-j0.989176, 0.923880-j0.382683, 0.740951+j0.671559, -0.382684+j0.923879, -0.989176-j0.146731, 0.000000-j1.000000, 0.998795-j0.049067, 0.000000+j1.000000, -0.989176-j0.146731, 0.382684-j0.923879, 0.740951+j0.671559, -0.923880+j0.382683, 0.146731-j0.989176, 0.707107+j0.707107, -0.998795+j0.049067, 0.707107-j0.707106, -0.146731+j0.989176, -0.382683-j0.923880, 0.740951+j0.671559, -0.923879-j0.382684, 0.989176+j0.146731, -1.000000-j0.000001, 0.998795-j0.049067, -1.000000-j0.000001, 0.989176+j0.146731, -0.923879-j0.382684, 0.740950+j0.671560, -0.382683-j0.923880, -0.146732+j0.989176, 0.707108-j0.707106, -0.998796+j0.049067, 0.707106+j0.707108, 0.146732-j0.989176, -0.923880+j0.382682, 0.740950+j0.671560, 0.382685-j0.923879, -0.989176-j0.146732, -0.000002+j1.000000, 0.998796-j0.049066, 0.000002-j1.000000, -0.989176-j0.146732, -0.382685+j0.923879, 0.740950+j0.671560, 0.923880-j0.382682, 0.146733-j0.989176, -0.707105-j0.707108, -0.998796+j0.049065, -0.707108+j0.707105, -0.146733+j0.989176, 0.382681+j0.923880, 0.740949+j0.671561, 0.923879+j0.382686, 0.989176+j0.146733, 1.000000+j0.000003, 0.998796-j0.049065 | +| $p_{P1}$ | 1.000000+j0.000000, 0.903989+j0.427555, 0.382683+j0.923880, -0.595699+j0.803208, -0.923880-j0.382683, 0.427555-j0.903989, 0.707107+j0.707107, -0.989177+j0.146730, 0.707107-j0.707107, -0.427555+j0.903989, 0.382684-j0.923879, -0.595700+j0.803207, 0.923880-j0.382683, -0.903989-j0.427555, 0.000001-j1.000000, -0.903989-j0.427556, -0.923880+j0.382683, -0.595700+j0.803207, -0.382684+j0.923879, -0.427556+j0.903989, -0.707108+j0.707106, -0.989177+j0.146729, -0.707106-j0.707108, 0.427556-j0.903989, 0.923879+j0.382685, -0.595701+j0.803207, -0.382682-j0.923880, 0.903988+j0.427557, -1.000000-j0.000002, 0.989177-j0.146728, -1.000000-j0.000002, 0.903988+j0.427557, -0.382681-j0.923881, -0.595702+j0.803206, 0.923878+j0.382686, 0.427558-j0.903988, -0.707104-j0.707109, -0.989177+j0.146727, -0.707109+j0.707104, -0.427559+j0.903988, -0.382687+j0.923878, -0.595703+j0.803205, -0.923881+j0.382679, -0.903987-j0.427559, 0.000005-j1.000000, 0.989177-j0.146726, -0.000005+j1.000000, -0.903987-j0.427560, 0.923882-j0.382678, -0.595704+j0.803204, 0.382689-j0.923877, -0.427561+j0.903987, 0.707111-j0.707102, -0.989178+j0.146724, 0.707102+j0.707112, 0.427562-j0.903986, -0.923877-j0.382690, -0.595706+j0.803203, 0.382676+j0.923883, 0.903986+j0.427563, 1.000000+j0.000009, 0.989178-j0.146722 | +| $p_{P2}$ | 1.000000+j0.000000, 0.740951+j0.671559, -0.382683+j0.923880, -0.857729-j0.514103, 0.923880-j0.382683, -0.671559+j0.740951, 0.707107-j0.707107, -0.970031+j0.242980, 0.707107+j0.707107, 0.671559-j0.740951, -0.382683-j0.923880, -0.857728-j0.514103, -0.923879-j0.382684, -0.740951-j0.671559, 0.000001-j1.000000, 0.970031-j0.242979, -0.000001+j1.000000, -0.740950-j0.671560, 0.923879+j0.382685, -0.857728-j0.514104, 0.382682+j0.923880, 0.671560-j0.740950, -0.707105-j0.707108, -0.970032+j0.242978, -0.707108+j0.707105, -0.671561+j0.740949, -0.923881+j0.382681, -0.857727-j0.514105, 0.382686-j0.923878, 0.740949+j0.671561, -1.000000-j0.000003, 0.970032-j0.242977, -1.000000-j0.000004, 0.740948+j0.671562, 0.382688-j0.923878, -0.857726-j0.514107, -0.923881+j0.382679, -0.671563+j0.740948, -0.707111+j0.707103, -0.970033+j0.242975, -0.707102-j0.707111, 0.671564-j0.740947, 0.382677+j0.923882, -0.857725-j0.514109, 0.923877+j0.382690, -0.740946-j0.671565, -0.000008+j1.000000, 0.970033-j0.242972, 0.000009-j1.000000, -0.740945-j0.671566, -0.923876-j0.382692, -0.857724-j0.514111, -0.382674-j0.923883, 0.671567-j0.740944, 0.707099+j0.707115, -0.970034+j0.242969, 0.707115-j0.707098, -0.671568+j0.740943, 0.923884-j0.382672, -0.857722-j0.514114, -0.382696+j0.923874, 0.740942+j0.671569, 1.000000+j0.000014, 0.970035-j0.242966 | +| $p_{P3}$ | 1.000000+j0.000000, 0.514103+j0.857729, -0.923880+j0.382683, 0.427555-j0.903989, -0.382684+j0.923879, 0.857729-j0.514103, -0.707107-j0.707107, -0.941544+j0.336890, -0.707107+j0.707106, -0.857729+j0.514102, -0.923879-j0.382684, 0.427556-j0.903989, 0.382683+j0.923880, -0.514102-j0.857729, -0.000001+j1.000000, 0.941545-j0.336889, 0.000001-j1.000000, -0.514101-j0.857729, -0.382682-j0.923880, 0.427557-j0.903988, 0.923879+j0.382685, -0.857730+j0.514101, 0.707109-j0.707105, -0.941545+j0.336887, 0.707105+j0.707109, 0.857730-j0.514100, 0.382687-j0.923878, 0.427559-j0.903988, 0.923881-j0.382679, 0.514099+j0.857731, -1.000000-j0.000005, 0.941546-j0.336885, -1.000000-j0.000006, 0.514098+j0.857732, 0.923882-j0.382678, 0.427561-j0.903986, 0.382690-j0.923877, 0.857732-j0.514096, 0.707101+j0.707112, -0.941547+j0.336882, 0.707113-j0.707101, -0.857733+j0.514095, 0.923876+j0.382692, 0.427564-j0.903985, -0.382674-j0.923883, -0.514094-j0.857734, 0.000011-j1.000000, 0.941548-j0.336879, -0.000012+j1.000000, -0.514092-j0.857735, 0.382671+j0.923885, 0.427567-j0.903983, -0.923874-j0.382697, -0.857736+j0.514090, -0.707118+j0.707096, -0.941549+j0.336875, -0.707095-j0.707118, 0.857737-j0.514088, -0.382700+j0.923873, 0.427572-j0.903981, -0.923887+j0.382666, 0.514086+j0.857739, 1.000000+j0.000020, 0.941551-j0.336870 | +| $p_{P4}$ | 1.000000+j0.000000, 0.242980+j0.970031, -0.923880-j0.382683, 0.941544+j0.336890, -0.382683-j0.923880, -0.970031+j0.242980, -0.707107+j0.707107, -0.903989+j0.427555, -0.707106-j0.707107, 0.970031-j0.242980, -0.923880+j0.382683, 0.941544+j0.336891, 0.382684-j0.923879, -0.242979-j0.970032, 0.000001-j1.000000, 0.903990-j0.427554, -0.000002+j1.000000, -0.242978-j0.970032, -0.382686+j0.923879, 0.941543+j0.336892, 0.923881-j0.382681, 0.970032-j0.242977, | + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0.707104+j0.707109, -0.903991+j0.427552, 0.707110-j0.707104, -0.970032+j0.242976,
0.382679+j0.923881, 0.941542+j0.336895, 0.923877+j0.382688, 0.242974+j0.970033, -1.000000-
j0.000006, 0.903992-j0.427549, -1.000000-j0.000007, 0.242973+j0.970033, 0.923876+j0.382691,
0.941541+j0.336898, 0.382675+j0.923883, -0.970034+j0.242971, 0.707114-j0.707100,
-0.903994+j0.427546, 0.707099+j0.707115, 0.970034-j0.242969, 0.923884-j0.382672,
0.941540+j0.336902, -0.382696+j0.923874, -0.242967-j0.970035, -0.000014+j1.000000, 0.903996-
j0.427542, 0.000016-j1.000000, -0.242964-j0.970035, 0.382699-j0.923873, 0.941538+j0.336906,
-0.923887+j0.382667, 0.970036-j0.242962, -0.707093-j0.707121, -0.903998+j0.427537,
-0.707122+j0.707092, -0.970037+j0.242959, -0.382662-j0.923888, 0.941536+j0.336912, -0.923870-
j0.382706, 0.242956+j0.970037, 1.000000+j0.000026, 0.904001-j0.427531 | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $p_{P5}$ | 1.000000+j0.000000, -0.049068+j0.998795, -0.382683-j0.923880, -0.242980+j0.970031, 0.923879+j0.382684, 0.998795+j0.049068, 0.707107+j0.707107, -0.857729+j0.514102, 0.707107-j0.707106, -0.998795-j0.049068, -0.382684+j0.923879, -0.242981+j0.970031, -0.923880+j0.382682, 0.049069-j0.998795, -0.000002+j1.000000, 0.857730-j0.514101, 0.000002-j1.000000, 0.049070-j0.998795, 0.923881-j0.382681, -0.242983+j0.970030, 0.382687-j0.923878, -0.998795-j0.049072, -0.707110+j0.707104, -0.857731+j0.514099, -0.707103-j0.707110, 0.998795+j0.049073, -0.923877-j0.382689, -0.242986+j0.970030, 0.382677+j0.923882, -0.049075+j0.998795, -1.000000-j0.000008, 0.857733-j0.514096, -1.000000-j0.000009, -0.049077+j0.998795, 0.382674+j0.923883, -0.242990+j0.970029, -0.923875-j0.382694, 0.998795+j0.049079, -0.707098-j0.707115, -0.857735+j0.514092, -0.707116+j0.707097, -0.998795-j0.049082, 0.382697-j0.923874, -0.242995+j0.970028, 0.923886-j0.382669, 0.049085-j0.998795, 0.000018-j1.000000, 0.857738-j0.514087, -0.000019+j1.000000, 0.049088-j0.998794, -0.923887+j0.382664, -0.243001+j0.970026, -0.382704+j0.923871, -0.998794-j0.049091, 0.707124-j0.707090, -0.857741+j0.514081, 0.707088+j0.707125, 0.998794+j0.049094, 0.923869+j0.382709, -0.243008+j0.970024, -0.382656-j0.923891, -0.049098+j0.998794, 1.000000+j0.000032, 0.857745-j0.514075 | +| $p_{P6}$ | 1.000000+j0.000000, -0.336890+j0.941544, 0.382684-j0.923880, -0.989176-j0.146731, -0.923880+j0.382683, -0.941544-j0.336890, 0.707107-j0.707106, -0.803208+j0.595699, 0.707106+j0.707107, 0.941544+j0.336891, 0.382682+j0.923880, -0.989176-j0.146732, 0.923879+j0.382685, 0.336892-j0.941543, 0.000002-j1.000000, 0.803209-j0.595697, -0.000003+j1.000000, 0.336893-j0.941543, -0.923878-j0.382687, -0.989176-j0.146734, -0.382680-j0.923881, 0.941543+j0.336894, -0.707103-j0.707110, -0.803211+j0.595695, -0.707111+j0.707103, -0.941542-j0.336896, 0.923882-j0.382677, -0.989175-j0.146738, -0.382691+j0.923877, -0.336898+j0.941541, -1.000000-j0.000009, 0.803213-j0.595692, -1.000000-j0.000010, -0.336900+j0.941540, -0.382694+j0.923875, -0.989175-j0.146743, 0.923884-j0.382672, -0.941539-j0.336903, -0.707117+j0.707097, -0.803217+j0.595687, -0.707096-j0.707118, 0.941538+j0.336906, -0.382667-j0.923886, -0.989174-j0.146749, -0.923872-j0.382701, 0.336909-j0.941537, -0.000021+j1.000000, 0.803220-j0.595682, 0.000023-j1.000000, 0.336912-j0.941536, 0.923870+j0.382706, -0.989173-j0.146756, 0.382659+j0.923890, 0.941535+j0.336916, 0.707087+j0.707127, -0.803225+j0.595676, 0.707128-j0.707085, -0.941533-j0.336920, -0.923892+j0.382653, -0.989172-j0.146764, 0.382716-j0.923866, -0.336924+j0.941532, 1.000000+j0.000037, 0.803231-j0.595668 | +| $p_{P7}$ | 1.000000+j0.000000, -0.595699+j0.803208, 0.923880-j0.382683, 0.049068-j0.998795, 0.382684-j0.923879, 0.803207+j0.595700, -0.707106-j0.707107, -0.740952+j0.671558, -0.707107+j0.707106, 0.803207-j0.595712, 0.923879+j0.382685, -0.049069-j0.998795, -0.382682-j0.923880, 0.595701-j0.803206, -0.000002+j1.000000, 0.740953-j0.671557, 0.000003-j1.000000, 0.595702-j0.803205, 0.382680+j0.923881, 0.049072-j0.998795, -0.923878-j0.382688, -0.803204-j0.595704, 0.707111-j0.707103, -0.740955+j0.671554, 0.707102+j0.707112, 0.803203+j0.595705, -0.382691+j0.923877, 0.049076-j0.998795, -0.923883+j0.382675, -0.595707+j0.803202, -1.000000-j0.000010, 0.740959-j0.671551, -1.000000-j0.000012, -0.595709+j0.803200, -0.923885+j0.382671, 0.049082-j0.998795, -0.382697+j0.923874, 0.803198+j0.595712, 0.707095+j0.707118, -0.740963+j0.671546, 0.707120-j0.707094, -0.803196-j0.595715, -0.923872-j0.382702, 0.049089-j0.998794, 0.382663+j0.923888, 0.595718-j0.803194, 0.000024-j1.000000, 0.740968-j0.671540, -0.000026+j1.000000, 0.595721-j0.803191, -0.382657-j0.923890, 0.049097-j0.998794, 0.923868+j0.382712, -0.803189-j0.595725, -0.707130+j0.707084, -0.740974+j0.671534, -0.707082-j0.707132, 0.803186+j0.595729, 0.382718-j0.923865, 0.049107-j0.998794, 0.923895-j0.382646, -0.595733+j0.803183, 1.000000+j0.000043, 0.740981-j0.671526 | +| $p_{P8}$ | 1.000000+j0.000000, -0.803208+j0.595699, 0.923879+j0.382684, 0.998795-j0.049067, 0.382683+j0.923880, -0.595699-j0.803208, -0.707107+j0.707106, -0.671560+j0.740951, -0.707106-j0.707107, 0.595698+j0.803208, 0.923880-j0.382682, 0.998796-j0.049066, -0.382685+j0.923879, 0.803209-j0.595697, 0.000003-j1.000000, 0.671561-j0.740949, -0.000004+j1.000000, 0.803210-j0.595696, 0.382688-j0.923878, 0.998796-j0.049063, -0.923882+j0.382678, 0.595695+j0.803211, 0.707102+j0.707111, -0.671564+j0.740946, 0.707112-j0.707101, -0.595693-j0.803212, -0.382675-j0.923883, 0.998796-j0.049058, -0.923876-j0.382693, -0.803214+j0.595690, -1.000000-j0.000012, 0.671568-j0.740943, -1.000000-j0.000013, -0.803216+j0.595688, -0.923874-j0.382697, 0.998796-j0.049052, -0.382668-j0.923886, -0.595685-j0.803218, 0.707120-j0.707094, -0.671574+j0.740938, 0.707092+j0.707121, 0.595682+j0.803220, -0.923888+j0.382662, 0.998797-j0.049044, 0.382706-j0.923870, 0.803223-j0.595678, -0.000027+j1.000000, 0.671580-j0.740932, 0.000030-j1.000000, 0.803226-j0.595675, -0.382713+j0.923867, 0.998797-j0.049034, 0.923893-j0.382651, 0.595670+j0.803229, -0.707080-j0.707133, -0.671588+j0.740925, -0.707135+j0.707078, -0.595666-j0.803232, 0.382644+j0.923896, 0.998798-j0.049023, 0.923862+j0.382726, -0.803236+j0.595661, 1.000000+j0.000049, 0.671596-j0.740917 | +| $p_{P9}$ | 1.000000+j0.000000, -0.941544+j0.336890, 0.382683+j0.923880, 0.146730+j0.989177, -0.923879-j0.382684, 0.336889+j0.941544, 0.707106+j0.707107, -0.595700+j0.803207, 0.707108-j0.707106, -0.336889-j0.941545, 0.382685-j0.923879, 0.146729+j0.989177, 0.923880-j0.382681, 0.941545-j0.336887, -0.000003+j1.000000, 0.595702-j0.803205, 0.000004-j1.000000, 0.941546-j0.336886, -0.923881+j0.382679, 0.146725+j0.989177, | + +| | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

-0.382689+j0.923877, -0.336884-j0.941546, -0.707112+j0.707102, -0.595706+j0.803203, -0.707101-j0.707113, 0.336881+j0.941547, 0.923876+j0.382693, 0.146720+j0.989178, -0.382673-j0.923884, -0.941548+j0.336878, -1.000000-j0.000013, 0.595711-j0.803199, -1.000000-j0.000015, -0.941549+j0.336875, -0.382668-j0.923886, 0.146713+j0.989179, 0.923872+j0.382701, 0.336871+j0.941551, -0.707092-j0.707122, -0.595717+j0.803194, -0.707123+j0.707090, -0.336867-j0.941552, -0.382707+j0.923870, 0.146704+j0.989180, -0.923890+j0.382658, 0.941554-j0.336862, 0.000030-j1.000000, 0.595725-j0.803189, -0.000033+j1.000000, 0.941556-j0.336857, 0.923893-j0.382650, 0.146694+j0.989182, 0.382719-j0.923865, -0.336852-j0.941558, 0.707136-j0.707077, -0.595734+j0.803182, 0.707075+j0.707138, 0.336846+j0.941560, -0.923861-j0.382728, 0.146681+j0.989184, 0.382636+j0.923899, -0.941562+j0.336840, 1.000000+j0.000055, 0.595745-j0.803174

| +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $p_{P10}$ | 1.000000+j0.000000, -0.998795+j0.049068, -0.382684+j0.923879, -0.970031+j0.242980, 0.923880-j0.382683, -0.049067-j0.998795, 0.707107-j0.707106, -0.514104+j0.857728, 0.707106+j0.707108, 0.049066+j0.998796, -0.382682-j0.923880, -0.970032+j0.242978, -0.923879-j0.382686, 0.998796-j0.049065, 0.000003-j1.000000, 0.514106-j0.857727, -0.000004+j1.000000, 0.998796-j0.049063, 0.923877+j0.382688, -0.970033+j0.242974, 0.382677+j0.923882, 0.049060+j0.998796, -0.707101-j0.707112, -0.514110+j0.857724, -0.707114+j0.707100, -0.049057-j0.998796, -0.923884+j0.382673, -0.970034+j0.242969, 0.382695-j0.923875, -0.998796+j0.049054, -1.000000-j0.000015, 0.514116-j0.857721, -1.000000-j0.000017, -0.998796+j0.049050, 0.382701-j0.923872, -0.970036+j0.242961, -0.923888+j0.382664, -0.049046-j0.998797, -0.707123+j0.707090, -0.514124+j0.857716, -0.707089-j0.707125, 0.049041+j0.998797, 0.382657+j0.923890, -0.970038+j0.242952, 0.923868+j0.382712, 0.998797-j0.049036, -0.000034+j1.000000, 0.514133-j0.857711, 0.000037-j1.000000, 0.998797-j0.049030, -0.923864-j0.382720, -0.970041+j0.242940, -0.382644-j0.923896, 0.049023+j0.998798, 0.707074+j0.707139, -0.514144+j0.857704, 0.707142-j0.707072, -0.049017-j0.998798, 0.923900-j0.382634, -0.970045+j0.242927, -0.382736+j0.923858, -0.998798+j0.049009, 1.000000+j0.000060, 0.514156-j0.857697 | +| $p_{P11}$ | 1.000000+j0.000000, -0.970031-j0.242980, -0.923880+j0.382683, -0.336890-j0.941544, -0.382684+j0.923879, -0.242981+j0.970031, -0.707106-j0.707107, -0.427556+j0.903989, -0.707108+j0.707106, 0.242982-j0.970031, -0.923879-j0.382685, -0.336888-j0.941545, 0.382681+j0.923881, 0.970030+j0.242983, -0.000004+j1.000000, 0.427559-j0.903987, 0.000005-j1.000000, 0.970030+j0.242985, -0.382678-j0.923882, -0.336884-j0.941546, 0.923877+j0.382690, 0.242988-j0.970029, 0.707113-j0.707101, -0.427564+j0.903985, 0.707099+j0.707114, -0.242991+j0.970029, 0.382695-j0.923875, -0.336878-j0.941548, 0.923885-j0.382670, -0.970028-j0.242995, -1.000000-j0.000016, 0.427571-j0.903982, -1.000000-j0.000018, -0.970027-j0.242999, 0.923887-j0.382665, -0.336870-j0.941551, 0.382705-j0.923871, -0.243004+j0.970025, 0.707089+j0.707125, -0.427579+j0.903978, 0.707127-j0.707087, 0.243009-j0.970024, 0.923868+j0.382712, -0.336859-j0.941555, -0.382652-j0.923892, 0.970023+j0.243014, 0.000037-j1.000000, 0.427590-j0.903973, -0.000040+j1.000000, 0.970021+j0.243021, 0.382643+j0.923896, -0.336847-j0.941559, -0.923862-j0.382727, 0.243027-j0.970019, -0.707142+j0.707071, -0.427602+j0.903967, -0.707068-j0.707145, -0.243035+j0.970018, -0.382737+j0.923857, -0.336833-j0.941564, -0.923903+j0.382626, -0.970016-j0.243042, 1.000000+j0.000066, 0.427617-j0.903960 | +| $p_{P12}$ | 1.000000+j0.000000, -0.857729-j0.514103, -0.923879-j0.382684, 0.903989-j0.427555, -0.382683-j0.923880, 0.514103-j0.857728, -0.707107+j0.707106, -0.336891+j0.941544, -0.707106-j0.707108, -0.514104+j0.857728, -0.923880+j0.382681, 0.903990-j0.427553, 0.382686-j0.923878, 0.857727+j0.514106, 0.000004-j1.000000, 0.336894-j0.941543, -0.000005+j1.000000, 0.857726+j0.514136, -0.382689+j0.923877, 0.903992-j0.427549, 0.923883-j0.382676, -0.514110+j0.857724, 0.707100+j0.707114, -0.336900+j0.941541, 0.707115-j0.707099, 0.514113-j0.857722, 0.382671+j0.923885, 0.903995-j0.427542, 0.923874+j0.382698, -0.857720-j0.514117, -1.000000-j0.000017, 0.336907-j0.941538, -1.000000-j0.000020, -0.857718-j0.514121, 0.923871+j0.382704, 0.903999-j0.427534, 0.382661+j0.923889, 0.514125-j0.857715, 0.707126-j0.707087, -0.336917+j0.941534, 0.707085+j0.707128, -0.514130+j0.857712, 0.923892-j0.382652, 0.904004-j0.427523, -0.382717+j0.923865, 0.857709+j0.514138, -0.000040+j1.000000, 0.336929-j0.941530, 0.000044-j1.000000, 0.857705+j0.514142, 0.382727-j0.923861, 0.904010-j0.427511, -0.923899+j0.382636, -0.514148+j0.857701, -0.707068-j0.707146, -0.336943+j0.941525, -0.707148+j0.707065, 0.514155-j0.857697, -0.382625-j0.923904, 0.904017-j0.427496, -0.923854-j0.382746, -0.857693-j0.514163, 1.000000+j0.000072, 0.336960-j0.941519 | +| $p_{P13}$ | 1.000000+j0.000000, -0.671559-j0.740951, -0.382683-j0.923880, 0.514102+j0.857729, 0.923879+j0.382684, -0.740952+j0.671558, 0.707106+j0.707107, -0.242981+j0.970031, 0.707108-j0.707106, 0.740952-j0.671558, -0.382686+j0.923879, 0.514100+j0.857730, -0.923881+j0.382680, 0.671556+j0.740954, -0.000004+j1.000000, 0.242985-j0.970030, 0.000006-j1.000000, 0.671554+j0.740955, 0.923882-j0.382677, 0.514096+j0.857733, 0.382691-j0.923876, 0.740957-j0.671552, -0.707114+j0.707099, -0.242991+j0.970029, -0.707098-j0.707115, -0.740960+j0.671549, -0.923874-j0.382697, 0.514090+j0.857736, 0.382668+j0.923886, -0.671546-j0.740963, -1.000000-j0.000019, 0.243000-j0.970026, -1.000000-j0.000021, -0.671542-j0.740966, 0.382661+j0.923889, 0.514081+j0.857742, -0.923869-j0.382708, -0.740970+j0.671538, -0.707086-j0.707128, -0.243011+j0.970024, -0.707130+j0.707084, 0.740974-j0.671533, 0.382717-j0.923866, 0.514070+j0.857748, 0.923895-j0.382647, 0.671528+j0.740979, 0.000043-j1.000000, 0.243024-j0.970020, -0.000047+j1.000000, 0.671523+j0.740984, -0.923899+j0.382636, 0.514057+j0.857756, -0.382734+j0.923858, 0.740989-j0.671517, 0.707149-j0.707065, -0.243040+j0.970016, 0.707062+j0.707152, -0.740995+j0.671510, 0.923853+j0.382746, 0.514042+j0.857765, -0.382616-j0.923907, -0.671503-j0.741002, 1.000000+j0.000078, 0.243058-j0.970012 | +| $p_{P14}$ | 1.000000+j0.000000, -0.427555-j0.903989, 0.382684-j0.923879, -0.803208+j0.595699, -0.923880+j0.382683, 0.903990-j0.427554, 0.707107-j0.707106, -0.146732+j0.989176, 0.707106+j0.707108, -0.903990+j0.427553, 0.382681+j0.923880, -0.803209+j0.595697, 0.923878+j0.382687, 0.427551+j0.903991, 0.000005-j1.000000, 0.146736-j0.989176, -0.000006+j1.000000, 0.427549+j0.903992, -0.923877-j0.382690, -0.803213+j0.595693, -0.382675-j0.923883, -0.903994+j0.427546, -0.707099-j0.707115, -0.146742+j0.989175, -0.707116+j0.707098, | + +| | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0.903995-j0.427542, 0.923885-j0.382669, -0.803217+j0.595686, -0.382700+j0.923873, -0.427538-j0.903997, -1.000000-j0.000020, 0.146752-j0.989173, -1.000000-j0.000023, -0.427533-j0.904000, -0.382707+j0.923870, -0.803224+j0.595677, 0.923891-j0.382657, 0.904002-j0.427528, -0.707129+j0.707084, -0.146764+j0.989172, -0.707082-j0.707132, -0.904005+j0.427522, -0.382648-j0.923894, -0.803232+j0.595667, -0.923863-j0.382723, 0.427515+j0.904008, -0.000046+j1.000000, 0.146778-j0.989169, 0.000050-j1.000000, 0.427508+j0.904012, 0.923859+j0.382734, -0.803241+j0.595654, 0.382629+j0.923902, -0.904016+j0.427500, 0.707062+j0.707152, -0.146796+j0.989167, 0.707155-j0.707058, 0.904020-j0.427491, -0.923908+j0.382616, -0.803253+j0.595639, 0.382756-j0.923850, -0.427482-j0.904024, 1.000000+j0.000083, 0.146816-j0.989164 | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| P P15 | 1.000000+j0.000000, -0.146730-j0.989177, 0.923880-j0.382683, -0.671559-j0.740951, 0.382684-j0.923879, -0.989177+j0.146730, -0.707106-j0.707108, -0.049069+j0.998795, -0.707108+j0.707106, 0.989177-j0.146728, 0.923879+j0.382686, -0.671557-j0.740953, -0.382680-j0.923881, 0.146726+j0.989177, -0.000005+j1.000000, 0.049073-j0.998795, 0.000006-j1.000000, 0.146723+j0.989178, 0.382676+j0.923883, -0.671552-j0.740957, -0.923876-j0.382693, 0.989178-j0.146720, 0.707115-j0.707098, -0.049081+j0.998795, 0.707097+j0.707117, -0.989179+j0.146715, -0.382699+j0.923873, -0.671546-j0.740963, -0.923887+j0.382666, -0.146710-j0.989179, -1.000000-j0.000022, 0.049091-j0.998794, -1.000000-j0.000024, -0.146705-j0.989180, -0.923890+j0.382658, -0.671537-j0.740971, -0.382712+j0.923868, -0.989181+j0.146698, 0.707083+j0.707131, -0.049104+j0.998794, 0.707133-j0.707080, 0.989182-j0.146691, -0.923864-j0.382722, -0.671527-j0.740980, 0.382641+j0.923897, 0.146683+j0.989183, 0.000050-j1.000000, 0.049119-j0.998793, -0.000054+j1.000000, 0.146675+j0.989185, -0.382629-j0.923902, -0.671514-j0.740992, 0.923855+j0.382742, 0.989186-j0.146666, -0.707155+j0.707059, -0.049138+j0.998792, -0.707055-j0.707158, -0.989188+j0.146656, 0.382756-j0.923850, -0.671499-j0.741005, 0.923912-j0.382606, -0.146645-j0.989189, 1.000000+j0.000089, 0.049160-j0.998791 | +| P P16 | 1.000000+j0.000000, 0.146731-j0.989176, 0.923879+j0.382684, 0.671559-j0.740951, 0.382683+j0.923880, 0.989176+j0.146731, -0.707108+j0.707106, 0.049066+j0.998796, -0.707105-j0.707108, -0.989176-j0.146733, 0.923881-j0.382681, 0.671561-j0.740949, -0.382687+j0.923878, -0.146735+j0.989176, 0.000005-j1.000000, -0.049062-j0.998796, -0.000007+j1.000000, -0.146738+j0.989175, 0.382691-j0.923876, 0.671566-j0.740945, -0.923884+j0.382674, -0.989175-j0.146742, 0.707098+j0.707116, 0.049054+j0.998796, 0.707117-j0.707096, 0.989174+j0.146746, -0.382667-j0.923886, 0.671573-j0.740939, -0.923872-j0.382702, 0.146752-j0.989173, -1.000000-j0.000023, -0.049043-j0.998797, -1.000000-j0.000026, 0.146758-j0.989172, -0.923868-j0.382710, 0.671582-j0.740930, -0.382653-j0.923892, 0.989171+j0.146765, 0.707133-j0.707081, 0.049029+j0.998797, 0.707078+j0.707135, -0.989170-j0.146772, -0.923896+j0.382643, 0.671593-j0.740920, 0.382728-j0.923861, -0.146781+j0.989169, -0.000053+j1.000000, -0.049013-j0.998798, 0.000057-j1.000000, -0.146790+j0.989168, -0.382741+j0.923856, 0.671607-j0.740908, 0.923905-j0.382621, -0.989166-j0.146799, -0.707056-j0.707158, 0.048993+j0.998799, -0.707162+j0.707052, 0.989165+j0.146810, 0.382606+j0.923911, 0.671623-j0.740893, 0.923845+j0.382766, 0.146821-j0.989163, 1.000000+j0.000095, -0.048970-j0.998800 | +| P P17 | 1.000000+j0.000000, 0.427555-j0.903989, 0.382683+j0.923880, 0.803207+j0.595700, -0.923879-j0.382684, -0.903989-j0.427556, 0.707106+j0.707108, 0.146729+j0.989177, 0.707108-j0.707105, 0.903988+j0.427557, 0.382686-j0.923878, 0.803205+j0.595702, 0.923881-j0.382679, -0.427560+j0.903987, -0.000006+j1.000000, -0.146724-j0.989177, 0.000007-j1.000000, -0.427563+j0.903986, -0.923883+j0.382675, 0.803201+j0.595707, -0.382694+j0.923875, 0.903984+j0.427566, -0.707116+j0.707097, 0.146716+j0.989179, -0.707096-j0.707118, -0.903982-j0.427571, 0.923872+j0.382701, 0.803196+j0.595715, -0.382664-j0.923888, 0.427576-j0.903980, -1.000000-j0.000024, -0.146705-j0.989180, -1.000000-j0.000028, 0.427582-j0.903977, -0.382655-j0.923891, 0.803188+j0.595726, 0.923866+j0.382716, -0.903974-j0.427588, -0.707080-j0.707134, 0.146690+j0.989182, -0.707137+j0.707077, 0.903970+j0.427596, -0.382727+j0.923862, 0.803178+j0.595739, -0.923899+j0.382636, -0.427604+j0.903966, 0.000056-j1.000000, -0.146673-j0.989185, -0.000061+j1.000000, -0.427612+j0.903962, 0.923905-j0.382622, 0.803167+j0.595754, 0.382749-j0.923852, 0.903958+j0.427622, 0.707161-j0.707053, 0.146652+j0.989188, 0.707048+j0.707165, -0.903953-j0.427632, -0.923846-j0.382765, 0.803153+j0.595773, 0.382596+j0.923916, 0.427643-j0.903948, 1.000000+j0.000101, -0.146628-j0.989192 | +| P P18 | 1.000000+j0.000000, 0.671559-j0.740951, -0.382684+j0.923879, -0.514103+j0.857728, 0.923880-j0.382683, 0.740950+j0.671560, 0.707108-j0.707106, 0.242979+j0.970032, 0.707105+j0.707108, -0.740949-j0.671561, -0.382680-j0.923881, -0.514106+j0.857727, -0.923878-j0.382688, -0.671563+j0.740948, 0.000006-j1.000000, -0.242974-j0.970033, -0.000008+j1.000000, -0.671565+j0.740945, 0.923876+j0.382692, -0.514112+j0.857723, 0.382673+j0.923884, -0.740942-j0.671569, -0.707097-j0.707117, 0.242965+j0.970035, -0.707119+j0.707095, 0.740939+j0.671572, -0.923887+j0.382665, -0.514121+j0.857718, 0.382704-j0.923871, 0.671577-j0.740935, -1.000000-j0.000026, -0.242954-j0.970038, -1.000000-j0.000029, 0.671582-j0.740930, 0.382714-j0.923867, -0.514133+j0.857711, -0.923894+j0.382650, 0.740925+j0.671588, -0.707136+j0.707078, 0.242939+j0.970042, -0.707075-j0.707139, -0.740919-j0.671594, 0.382638+j0.923899, -0.514147+j0.857702, 0.923859+j0.382734, -0.671601+j0.740913, -0.000059+j1.000000, -0.242920-j0.970046, 0.000064-j1.000000, -0.671609+j0.740906, -0.923853-j0.382748, -0.514165+j0.857691, -0.382614-j0.923908, -0.740899-j0.671617, 0.707049+j0.707164, 0.242899+j0.970052, 0.707168-j0.707045, 0.740891+j0.671626, 0.923915-j0.382597, -0.514186+j0.857679, -0.382776+j0.923841, 0.671635-j0.740882, 1.000000+j0.000106, -0.242874-j0.970058 | +| P P19 | 1.000000+j0.000000, 0.857729-j0.514103, -0.923880+j0.382683, -0.903989-j0.427555, -0.382684+j0.923879, -0.514102-j0.857729, -0.707106-j0.707108, 0.336888+j0.941545, -0.707108+j0.707105, 0.514100+j0.857730, -0.923878-j0.382687, -0.903988-j0.427559, 0.382679+j0.923881, -0.857731+j0.514098, -0.000006+j1.000000, -0.336883-j0.941546, 0.000008-j1.000000, -0.857733+j0.514095, -0.382674-j0.923883, -0.903984-j0.427565, 0.923875+j0.382695, 0.514091+j0.857736, 0.707117-j0.707096, 0.336875+j0.941550, 0.707094+j0.707119, -0.514086-j0.857738, 0.382702-j0.923872, -0.903980-j0.427575, 0.923889-j0.382661, 0.857742-j0.514081, -1.000000-j0.000027, -0.336863-j0.941554, -1.000000-j0.000031, 0.857745-j0.514075, 0.923893-j0.382657 | + +| | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| j0.382651, -0.903974-j0.427588,
0.382719-j0.923865, -0.514068-j0.857750, 0.707076+j0.707137, 0.336847+j0.941559, 0.707140-
j0.707073, 0.514060+j0.857754, 0.923860+j0.382732, -0.903966-j0.427605, -0.382631-j0.923901,
-0.857759+j0.514051, 0.000062-j1.000000, -0.336829-j0.941566, -0.000068+j1.000000,
-0.857765+j0.514042, 0.382615+j0.923908, -0.903957-j0.427624, -0.923849-j0.382757,
0.514032+j0.857771, -0.707167+j0.707046, 0.336806+j0.941574, -0.707042-j0.707172, -0.514021-
j0.857778, -0.382774+j0.923842, -0.903946-j0.427647, -0.923920+j0.382586, 0.857784-j0.514010,
1.000000+j0.000112, -0.336781-j0.941583 | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $P_{P20}$ | 1.000000+j0.000000, 0.970031-j0.242980, -0.923879-j0.382684, 0.336890-j0.941544, -0.382683-j0.923880, 0.242979+j0.970032, -0.707108+j0.707106, 0.427553+j0.903990, -0.707105-j0.707108, -0.242977-j0.970032, -0.923881+j0.382680, 0.336894-j0.941543, 0.382688-j0.923878, -0.970033+j0.242975, 0.000007-j1.000000, -0.427548-j0.903993, -0.000009+j1.000000, -0.970034+j0.242971, -0.382693+j0.923875, 0.336901-j0.941540, 0.923885-j0.382671, -0.242966-j0.970035, 0.707096+j0.707118, 0.427540+j0.903997, 0.707120-j0.707094, 0.242961+j0.970036, 0.382663+j0.923888, 0.336912-j0.941536, 0.923870+j0.382707, 0.970038-j0.242954, -1.000000-j0.000029, -0.427528-j0.904002, -1.000000-j0.000032, 0.970040-j0.242947, 0.923866+j0.382717, 0.336926-j0.941531, 0.382646+j0.923895, 0.242939+j0.970042, 0.707139-j0.707075, 0.427512+j0.904010, 0.707071+j0.707142, -0.242929-j0.970044, 0.923901-j0.382633, 0.336944-j0.941525, -0.382739+j0.923857, -0.970047+j0.242919, -0.000066+j1.000000, -0.427493-j0.904019, 0.000071-j1.000000, -0.970049+j0.242908, 0.382755-j0.923850, 0.336966-j0.941517, -0.923911+j0.382606, -0.242896-j0.970052, -0.707043-j0.707170, 0.427471+j0.904029, -0.707175+j0.707038, 0.242883+j0.970056, -0.382588-j0.923919, 0.336991-j0.941508, -0.923837-j0.382786, 0.970059-j0.242869, 1.000000+j0.000118, -0.427445-j0.904041 | +| $P_{P21}$ | 1.000000+j0.000000, 0.998795+j0.049068, -0.382683-j0.923880, 0.970031+j0.242981, 0.923879+j0.382684, 0.049069-j0.998795, 0.707106+j0.707108, 0.514101+j0.857730, 0.707109-j0.707105, -0.049071+j0.998795, -0.382687+j0.923878, 0.970030+j0.242985, -0.923882+j0.382679, -0.998795-j0.049074, -0.000007+j1.000000, -0.514096-j0.857733, 0.000009-j1.000000, -0.998795-j0.049078, 0.923884-j0.382673, 0.970028+j0.242992, 0.382696-j0.923874, -0.049083+j0.998795, -0.707118+j0.707095, 0.514087+j0.857738, -0.707093-j0.707121, 0.049089-j0.998794, -0.923871-j0.382704, 0.970025+j0.243004, 0.382659+j0.923890, 0.998794+j0.049096, -1.000000-j0.000030, -0.514075-j0.857745, -1.000000-j0.000034, 0.998794+j0.049104, 0.382648+j0.923894, 0.970021+j0.243019, -0.923863-j0.382723, 0.049113-j0.998793, -0.707073-j0.707140, 0.514060+j0.857754, -0.707144+j0.707070, -0.049123+j0.998793, 0.382737-j0.923857, 0.970017+j0.243039, 0.923904-j0.382625, -0.998792-j0.049134, 0.000069-j1.000000, -0.514041-j0.857766, -0.000075+j1.000000, -0.998792-j0.049146, -0.923911+j0.382609, 0.970011+j0.243062, -0.382764+j0.923846, -0.049158+j0.998791, 0.707173-j0.707040, 0.514019+j0.857779, 0.707035+j0.707178, 0.049172-j0.998790, 0.923838+j0.382784, 0.970004+j0.243089, -0.382576-j0.923924, 0.998790+j0.049187, 1.000000+j0.000124, -0.513993-j0.857794 | +| $P_{P22}$ | 1.000000+j0.000000, 0.941544+j0.336890, 0.382684-j0.923879, -0.146731+j0.989176, -0.923880+j0.382683, -0.336891+j0.941544, 0.707108-j0.707106, 0.595698+j0.803209, 0.707105+j0.707109, 0.336893-j0.941543, 0.382680+j0.923881, -0.146735+j0.989176, 0.923877+j0.382688, -0.941542-j0.336896, 0.000007-j1.000000, -0.595693-j0.803212, -0.000009+j1.000000, -0.941541-j0.336900, -0.923875-j0.382694, -0.146743+j0.989175, -0.382670-j0.923885, 0.336905-j0.941539, -0.707095-j0.707119, 0.595684+j0.803219, -0.707121+j0.707092, -0.336911+j0.941537, 0.923889-j0.382661, -0.146756+j0.989173, -0.382709+j0.923869, 0.941534+j0.336917, -1.000000-j0.000031, -0.595672-j0.803227, -1.000000-j0.000036, 0.941531+j0.336925, -0.382720+j0.923864, -0.146772+j0.989170, 0.923897-j0.382642, -0.336934+j0.941528, -0.707142+j0.707072, 0.595657+j0.803239, -0.707068-j0.707146, 0.336944-j0.941525, -0.382628-j0.923903, -0.146793+j0.989167, -0.923854-j0.382744, -0.941521-j0.336955, -0.000072+j1.000000, -0.595639-j0.803252, 0.000078-j1.000000, -0.941517-j0.336967, 0.923847+j0.382762, -0.146818+j0.989164, 0.382599+j0.923915, 0.336979-j0.941512, 0.707037+j0.707177, 0.595617+j0.803268, 0.707182-j0.707032, -0.336993+j0.941507, -0.923923+j0.382579, -0.146847+j0.989159, 0.382796-j0.923833, 0.941502+j0.337008, 1.000000+j0.000129, -0.595592-j0.803287 | +| $P_{P23}$ | 1.000000+j0.000000, 0.803207+j0.595699, 0.923880-j0.382683, -0.998795-j0.049068, 0.382684-j0.923879, 0.595700-j0.803207, -0.707106-j0.707108, 0.671557+j0.740953, -0.707109+j0.707105, -0.595702+j0.803206, 0.923878+j0.382687, -0.998795-j0.049073, -0.382678-j0.923882, -0.803204-j0.595705, -0.000008+j1.000000, -0.671553-j0.740957, 0.000010-j1.000000, -0.803201-j0.595708, 0.382672+j0.923884, -0.998795-j0.049081, -0.923874-j0.382697, -0.595713+j0.803198, 0.707120-j0.707094, 0.671544+j0.740964, 0.707092+j0.707122, 0.595718-j0.803194, -0.382706+j0.923870, -0.998794-j0.049094, -0.923890+j0.382657, 0.803189+j0.595724, -1.000000-j0.000033, -0.671533-j0.740975, -1.000000-j0.000037, 0.803184+j0.595731, -0.923895+j0.382645, -0.998793-j0.049112, -0.382727+j0.923862, 0.595739-j0.803178, 0.707070+j0.707143, 0.671519+j0.740988, 0.707147-j0.707066, -0.595748+j0.803172, -0.923855-j0.382742, -0.998792-j0.049134, 0.382620+j0.923906, -0.803165-j0.595757, 0.000075-j1.000000, -0.671501-j0.741004, -0.000082+j1.000000, -0.803157-j0.595768, -0.382602-j0.923913, -0.998791-j0.049160, 0.923843+j0.382772, -0.595779+j0.803148, -0.707180+j0.707034, 0.671480+j0.741023, -0.707029-j0.707185, 0.595791-j0.803139, 0.382793-j0.923834, -0.998789-j0.049190, 0.923928-j0.382566, 0.803130+j0.595805, 1.000000+j0.000135, -0.671456-j0.741045 | +| $P_{P24}$ | 1.000000+j0.000000, 0.595699+j0.803208, 0.923879+j0.382684, -0.049067-j0.998795, 0.382683+j0.923880, -0.803208+j0.595698, -0.707108+j0.707106, 0.740950+j0.671561, -0.707105-j0.707109, 0.803210-j0.595696, 0.923881-j0.382679, -0.049063-j0.998796, -0.382689+j0.923877, -0.595694-j0.803212, 0.000008-j1.000000, -0.740945-j0.671566, -0.000010+j1.000000, -0.595690-j0.803214, 0.382695-j0.923875, -0.049054-j0.998796, -0.923886+j0.382669, 0.803218-j0.595686, 0.707094+j0.707120, 0.740937+j0.671574, 0.707122-j0.707091, -0.803222+j0.595680, -0.382660- | + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| j0.923889, -0.049040-j0.998797, -0.923868-j0.382711, 0.595674+j0.803227, -1.000000-j0.000034,
-0.740927-j0.671586, -1.000000-j0.000039, 0.595666+j0.803232, -0.923863-j0.382724, -0.049022-
j0.998798, -0.382639-j0.923898, -0.803238+j0.595658, 0.707145-j0.707069, 0.740913+j0.671601,
0.707065+j0.707149, 0.803245-j0.595649, -0.923905+j0.382623, -0.048999-j0.998799, 0.382750-
j0.923852, -0.595639-j0.803252, -0.000078+j1.000000, -0.740896-j0.671620, 0.000085-j1.000000,
-0.595628-j0.803260, -0.382769+j0.923844, -0.048972-j0.998800, 0.923918-j0.382591, 0.803269-
j0.595616, -0.707031-j0.707183, 0.740876+j0.671641, -0.707188+j0.707025, -0.803279+j0.595603,
0.382569+j0.923927, -0.048940-j0.998802, 0.923829+j0.382806, 0.595590+j0.803289,
1.000000+j0.000141, -0.740853-j0.671667 | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $P_{P25}$ | 1.000000+j0.000000, 0.336890+j0.941544, 0.382683+j0.923880, 0.989177-j0.146730, -0.923879-j0.382684, 0.941545-j0.336889, 0.707106+j0.707108, 0.803206+j0.595701, 0.707109-j0.707105, -0.941545+j0.336886, 0.382688-j0.923878, 0.989177-j0.146725, 0.923882-j0.382678, -0.336883-j0.941546, -0.000008+j1.000000, -0.803202-j0.595707, 0.000011-j1.000000, -0.336879-j0.941548, -0.923885+j0.382671, 0.989179-j0.146716, -0.382698+j0.923873, -0.941550+j0.336873, -0.707121+j0.707093, 0.803195+j0.595716, -0.707090-j0.707123, 0.941552-j0.336866, 0.923869+j0.382708, 0.989181-j0.146702, -0.382655-j0.923891, 0.336859+j0.941555, -1.000000-j0.000036, -0.803185-j0.595730, -1.000000-j0.000040, 0.336850+j0.941558, -0.382642-j0.923897, 0.989184-j0.146683, 0.923860+j0.382730, 0.941562-j0.336840, -0.707067-j0.707147, 0.803172+j0.595747, -0.707151+j0.707063, -0.941566+j0.336828, -0.382747+j0.923853, 0.989187-j0.146660, -0.923908+j0.382614, -0.336816-j0.941570, 0.000082-j1.000000, -0.803157-j0.595768, -0.000089+j1.000000, -0.336803-j0.941575, 0.923916-j0.382595, 0.989191-j0.146632, 0.382779-j0.923840, -0.941580+j0.336788, 0.707186-j0.707028, 0.803138+j0.595792, 0.707022+j0.707192, 0.941586-j0.336773, -0.923830-j0.382802, 0.989196-j0.146599, 0.382556+j0.923932, 0.336756+j0.941592, 1.000000+j0.000147, -0.803117-j0.595821 | +| $P_{P26}$ | 1.000000+j0.000000, 0.049068+j0.998795, -0.382684+j0.923879, 0.242980+j0.970031, 0.923880-j0.382683, -0.998796+j0.049066, 0.707108-j0.707105, 0.857727+j0.514105, 0.707105+j0.707109, 0.998796-j0.049064, -0.382679-j0.923881, 0.242975+j0.970033, -0.923877-j0.382689, -0.049060-j0.998796, 0.000009-j1.000000, -0.857724-j0.514111, -0.000011+j1.000000, -0.049055-j0.998796, 0.923874+j0.382696, 0.242965+j0.970035, 0.382668+j0.923886, 0.998796-j0.049049, -0.707092-j0.707121, 0.857717+j0.514122, -0.707124+j0.707090, -0.998797+j0.049042, -0.923890+j0.382658, 0.242951+j0.970039, 0.382713-j0.923867, 0.049033+j0.998797, -1.000000-j0.000037, -0.857708-j0.514136, -1.000000-j0.000042, 0.049023+j0.998798, 0.382727-j0.923862, 0.242932+j0.970043, -0.923900+j0.382635, -0.998798+j0.049012, -0.707148+j0.707065, 0.857697+j0.514155, -0.707061-j0.707152, 0.998799-j0.049000, 0.382618+j0.923907, 0.242908+j0.970049, 0.923850+j0.382755, -0.048986-j0.998799, -0.000085+j1.000000, -0.857683-j0.514179, 0.000092-j1.000000, -0.048972-j0.998800, -0.923841-j0.382776, 0.242879+j0.970056, -0.382584-j0.923921, 0.998801-j0.048956, 0.707025+j0.707189, 0.857667+j0.514206, 0.707195-j0.707019, -0.998802+j0.048939, 0.923931-j0.382560, 0.242846+j0.970065, -0.382816+j0.923825, 0.048920+j0.998803, 1.000000+j0.000153, -0.857648-j0.514238 | +| $P_{P27}$ | 1.000000+j0.000000, -0.242980+j0.970031, -0.923880+j0.382683, -0.941544+j0.336889, -0.382684+j0.923879, 0.970031+j0.242982, -0.707105-j0.707108, 0.903988+j0.427557, -0.707109+j0.707105, -0.970030-j0.242984, -0.923878-j0.382688, -0.941546+j0.336884, 0.382677+j0.923882, 0.242988-j0.970029, -0.000009+j1.000000, -0.903985-j0.427564, 0.000011-j1.000000, 0.242993-j0.970028, -0.382670-j0.923885, -0.941549+j0.336875, 0.923873+j0.382700, -0.970027-j0.242999, 0.707122-j0.707092, 0.903979+j0.427576, 0.707089+j0.707124, 0.970025+j0.243006, 0.382710-j0.923868, -0.941555+j0.336860, 0.923892-j0.382652, -0.243015+j0.970023, -1.000000-j0.000038, -0.903972-j0.427592, -1.000000-j0.000043, -0.243025+j0.970020, 0.923898-j0.382638, -0.941561+j0.336841, 0.382734-j0.923859, 0.970017+j0.243036, 0.707064+j0.707150, 0.903962+j0.427613, 0.707154-j0.707059, -0.970014-j0.243048, 0.923851+j0.382752, -0.941570+j0.336817, -0.382609-j0.923910, 0.242962-j0.970011, 0.000088-j1.000000, -0.903950-j0.427638, -0.000096+j1.000000, 0.243077-j0.970007, 0.382588+j0.923919, -0.941580+j0.336788, -0.923837-j0.382787, -0.970003-j0.243093, -0.707192+j0.707021, 0.903936+j0.427668, -0.707015-j0.707198, 0.969999+j0.243110, -0.382812+j0.923826, -0.941592+j0.336755, -0.923936+j0.382546, -0.243129+j0.969994, 1.000000+j0.000158, -0.903919-j0.427703 | +| $P_{P28}$ | 1.000000+j0.000000, -0.514103+j0.857729, -0.923879-j0.382684, -0.427555-j0.903990, -0.382683-j0.923880, -0.857728-j0.514104, -0.707108+j0.707105, 0.941543+j0.336892, -0.707104-j0.707109, 0.857727+j0.514106, -0.923881+j0.382679, -0.427550-j0.903992, 0.382690-j0.923877, 0.514110-j0.857724, 0.000009-j1.000000, -0.941541-j0.336900, -0.000012+j1.000000, 0.514114-j0.857722, -0.382697+j0.923874, -0.427540-j0.903996, 0.923886-j0.382667, 0.857718+j0.514120, 0.707091+j0.707122, 0.941536+j0.336912, 0.707125-j0.707089, -0.857714-j0.514127, 0.382656+j0.923891, -0.427526-j0.904003, 0.923866+j0.382716, -0.514135+j0.857710, -1.000000-j0.000040, -0.941530-j0.336930, -1.000000-j0.000045, -0.514144+j0.857704, 0.923860+j0.382730, -0.427507-j0.904012, 0.382631+j0.923901, -0.857698-j0.514154, 0.707151-j0.707062, 0.941522+j0.336952, 0.707058+j0.707156, 0.857691+j0.514165, 0.923909-j0.382613, -0.427483-j0.904023, -0.382761+j0.923848, 0.514178-j0.857684, -0.000091+j1.000000, -0.941512-j0.336979, 0.000099-j1.000000, 0.514191-j0.857676, 0.382783-j0.923838, -0.427454-j0.904037, -0.923924+j0.382576, 0.857667+j0.514206, -0.707018-j0.707195, 0.941500+j0.337012, -0.707202+j0.707012, -0.857657-j0.514222, -0.382551-j0.923935, -0.427421-j0.904053, -0.923821-j0.382825, -0.514239+j0.857647, 1.000000+j0.000164, -0.941487-j0.337049 | +| $P_{P29}$ | 1.000000+j0.000000, -0.740951+j0.671559, -0.382683-j0.923880, 0.857729-j0.514102, 0.923879+j0.382684, 0.671558+j0.740952, 0.707105+j0.707108, 0.970031+j0.242983, 0.707109-j0.707104, -0.671556-j0.740954, -0.382688+j0.923878, 0.857732-j0.514097, -0.923882+j0.382677, 0.740957-j0.671553, -0.000010+j1.000000, -0.970029-j0.242991, 0.000012-j1.000000, 0.740960-j0.671549, 0.923885-j0.382669, 0.857737-j0.514088, 0.382701-j0.923872, -0.671544-j0.740965, -0.707123+j0.707091, 0.970025+j0.243004, -0.707088- | + +| | | +|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | j0.707126, 0.671538+j0.740971, -0.923868-j0.382712, 0.857746-j0.514074, 0.382650+j0.923893, -0.740977+j0.671530, -1.000000-j0.000041, -0.970021-j0.243023, -1.000000-j0.000047, -0.740984+j0.671522, 0.382635+j0.923900, 0.857757-j0.514055, -0.923857-j0.382738, 0.671513+j0.740993, -0.707061-j0.707153, 0.970015+j0.243047, -0.707158+j0.707056, -0.671503-j0.741002, 0.382756-j0.923849, 0.857771-j0.514032, 0.923913-j0.382603, 0.741012-j0.671492, 0.000094-j1.000000, -0.970007-j0.243076, -0.000103+j1.000000, 0.741023-j0.671480, -0.923922+j0.382581, 0.857788-j0.514004, -0.382794+j0.923834, -0.671467-j0.741035, 0.707198-j0.707015, 0.969999+j0.243110, 0.707009+j0.707205, 0.671452+j0.741048, 0.923823+j0.382821, 0.857808-j0.513971, -0.382536-j0.923940, -0.741062+j0.671437, 1.000000+j0.000170, -0.969989-j0.243150 | +| P P30 | 1.000000+j0.000000, -0.903989+j0.427555, 0.382684-j0.923879, 0.595699+j0.803208, -0.923880+j0.382682, -0.427554-j0.903990, 0.707108-j0.707105, 0.989176+j0.146733, 0.707104+j0.707109, 0.427551+j0.903991, 0.382679+j0.923882, 0.595694+j0.803211, 0.923877+j0.382690, 0.903993-j0.427547, 0.000010-j1.000000, -0.989175-j0.146742, -0.000013+j1.000000, 0.903995-j0.427542, -0.923873-j0.382698, 0.595685+j0.803218, -0.382665-j0.923887, 0.427536+j0.903998, -0.707090-j0.707123, 0.989173+j0.146756, -0.707126+j0.707087, -0.427528-j0.904002, 0.923892-j0.382654, 0.595671+j0.803228, -0.382718+j0.923865, -0.904006+j0.427519, -1.000000-j0.000042, -0.989170-j0.146775, -1.000000-j0.000048, -0.904011+j0.427509, -0.382733+j0.923859, 0.595653+j0.803242, 0.923903-j0.382628, -0.427497-j0.904017, -0.707154+j0.707059, 0.989166+j0.146800, -0.707054-j0.707159, 0.427485+j0.904023, -0.382608-j0.923911, 0.595631+j0.803259, -0.923845-j0.382766, 0.904029-j0.427471, -0.000098+j1.000000, -0.989162-j0.146831, 0.000106-j1.000000, 0.904037-j0.427455, 0.923836+j0.382790, 0.595603+j0.803279, 0.382569+j0.923927, 0.427439+j0.904044, 0.707012+j0.707201, 0.989156+j0.146868, 0.707208-j0.707005, -0.427421-j0.904053, -0.923938+j0.382541, 0.595571+j0.803302, 0.382835-j0.923817, -0.904062+j0.427401, 1.000000+j0.000176, -0.989150-j0.146910 | +| P P31 | 1.000000+j0.000000, -0.989177+j0.146730, 0.923880-j0.382683, -0.740952+j0.671558, 0.382684-j0.923879, 0.146729+j0.989177, -0.707105-j0.707108, 0.998795+j0.049071, -0.707109+j0.707104, -0.146726-j0.989177, 0.923877+j0.382688, -0.740956+j0.671554, -0.382676-j0.923882, 0.989178-j0.146722, -0.000010+j1.000000, -0.998795-j0.049079, 0.000013-j1.000000, 0.989179-j0.146716, 0.382668+j0.923886, -0.740963+j0.671545, -0.923872-j0.382702, -0.146709-j0.989180, 0.707124-j0.707090, 0.998794+j0.049094, 0.707087+j0.707127, 0.146700+j0.989181, -0.382714+j0.923867, -0.740975+j0.671532, -0.923894+j0.382648, -0.989183+j0.146690, -1.000000-j0.000044, -0.998793-j0.049114, -1.000000-j0.000050, -0.989184+j0.146678, -0.923901+j0.382632, -0.740991+j0.671515, -0.382741+j0.923856, 0.146665+j0.989186, 0.707058+j0.707156, 0.998792+j0.049141, 0.707161-j0.707053, -0.146651-j0.989188, -0.923847-j0.382761, -0.741010+j0.671493, 0.382598+j0.923915, 0.989191-j0.146635, 0.000101-j1.000000, -0.998790-j0.049173, -0.000110+j1.000000, 0.989193-j0.146618, -0.382574-j0.923925, -0.741034+j0.671467, 0.923830+j0.382802, -0.146599-j0.989196, -0.707204+j0.707009, 0.998788+j0.049211, -0.707002-j0.707212, 0.146578+j0.989199, 0.382830-j0.923819, -0.741062+j0.671437, 0.923945-j0.382526, -0.989202+j0.146557, 1.000000+j0.000181, -0.998786-j0.049255 | + +## AA.2 Association between Midambles and Channelisation Codes for default midamble allocation + +The following mapping schemes apply for the association between midambles and channelisation codes if no midamble is allocated by higher layers. Secondary channelisation codes are marked with \*. These associations apply for both UL and DL. + +### AA.2.1 Association for K=16 Midambles + +![A hierarchical tree diagram showing the association of 16 Midambles to spreading codes for K=16. The root node is m^(1) - c_1^(1), which branches into m^(1) - c_2^(1) and m^(9) - c_2^(2). These further branch into m^(1) - c_4^(1), m^(5) - c_4^(2), m^(9) - c_4^(3), and m^(13) - c_4^(4). Each of these then branches into m^(1) - c_8^(1), m^(3) - c_8^(2), m^(5) - c_8^(3), m^(7) - c_8^(4), m^(9) - c_8^(5), m^(11) - c_8^(6), m^(13) - c_8^(7), and m^(15) - c_8^(8). Finally, each of these branches into two leaf nodes representing spreading codes c_16^(1) through c_16^(16).](da06747b80ea0d71593cbbd4c2ea89aa_img.jpg) + +A hierarchical tree diagram showing the association of 16 Midambles to spreading codes for K=16. The root node is m^(1) - c\_1^(1), which branches into m^(1) - c\_2^(1) and m^(9) - c\_2^(2). These further branch into m^(1) - c\_4^(1), m^(5) - c\_4^(2), m^(9) - c\_4^(3), and m^(13) - c\_4^(4). Each of these then branches into m^(1) - c\_8^(1), m^(3) - c\_8^(2), m^(5) - c\_8^(3), m^(7) - c\_8^(4), m^(9) - c\_8^(5), m^(11) - c\_8^(6), m^(13) - c\_8^(7), and m^(15) - c\_8^(8). Finally, each of these branches into two leaf nodes representing spreading codes c\_16^(1) through c\_16^(16). + +Figure AA.1: Association of Midambles to Spreading Codes for K=16 + +### AA.2.2 Association for K=14 Midambles + +![A hierarchical tree diagram showing the association of 14 Midambles to spreading codes for K=14. The root node is m^(1) - c_1^(1), which branches into m^(1) - c_2^(1) and m^(9) - c_2^(2). These further branch into m^(1) - c_4^(1), m^(5) - c_4^(2), m^(9) - c_4^(3), and m^(13) - c_4^(4). Each of these then branches into m^(1) - c_8^(1), m^(3) - c_8^(2), m^(5) - c_8^(3), m^(7) - c_8^(4), m^(9) - c_8^(5), m^(11) - c_8^(6), m^(13) - c_8^(7), and m^(14) - c_8^(8). Finally, each of these branches into two leaf nodes representing spreading codes c_16^(1) through c_16^(14) and c_16^(14)* through c_16^(16)*.](4390b89fdb95cba102ee1f88e218b07b_img.jpg) + +A hierarchical tree diagram showing the association of 14 Midambles to spreading codes for K=14. The root node is m^(1) - c\_1^(1), which branches into m^(1) - c\_2^(1) and m^(9) - c\_2^(2). These further branch into m^(1) - c\_4^(1), m^(5) - c\_4^(2), m^(9) - c\_4^(3), and m^(13) - c\_4^(4). Each of these then branches into m^(1) - c\_8^(1), m^(3) - c\_8^(2), m^(5) - c\_8^(3), m^(7) - c\_8^(4), m^(9) - c\_8^(5), m^(11) - c\_8^(6), m^(13) - c\_8^(7), and m^(14) - c\_8^(8). Finally, each of these branches into two leaf nodes representing spreading codes c\_16^(1) through c\_16^(14) and c\_16^(14)\* through c\_16^(16)\*. + +Figure AA.2: Association of Midambles to Spreading Codes for K=14 + +### AA.2.3 Association for K=12 Midambles + +![A hierarchical tree diagram showing the association of 12 midambles to spreading codes for K=12. The root node is m^(1) - c_1^(1), which branches into m^(1) - c_2^(1) and m^(9) - c_2^(2). Further sub-nodes include m^(1) - c_4^(1), m^(5) - c_4^(2), m^(9) - c_4^(3), and m^(11) - c_4^(4), leading to leaf nodes representing specific midamble-code pairs like m^(1) - c_16^(1) through m^(12) - c_16^(16).](d197b6ded14ea918198a280ff07122b8_img.jpg) + +A hierarchical tree diagram showing the association of 12 midambles to spreading codes for K=12. The root node is m^(1) - c\_1^(1), which branches into m^(1) - c\_2^(1) and m^(9) - c\_2^(2). Further sub-nodes include m^(1) - c\_4^(1), m^(5) - c\_4^(2), m^(9) - c\_4^(3), and m^(11) - c\_4^(4), leading to leaf nodes representing specific midamble-code pairs like m^(1) - c\_16^(1) through m^(12) - c\_16^(16). + +Figure AA.3: Association of Midambles to Spreading Codes for K=12 + +### AA.2.4 Association for K=10 Midambles + +![A hierarchical tree diagram showing the association of 10 midambles to spreading codes for K=10. The root node is m^(1) - c_1^(1), which branches into m^(1) - c_2^(1) and m^(7) - c_2^(2). Further sub-nodes include m^(1) - c_4^(1), m^(5) - c_4^(2), m^(7) - c_4^(3), and m^(9) - c_4^(4), leading to leaf nodes representing specific midamble-code pairs like m^(1) - c_16^(1) through m^(10) - c_16^(16).](014daefdecf9d847ca82cb5b9f50731f_img.jpg) + +A hierarchical tree diagram showing the association of 10 midambles to spreading codes for K=10. The root node is m^(1) - c\_1^(1), which branches into m^(1) - c\_2^(1) and m^(7) - c\_2^(2). Further sub-nodes include m^(1) - c\_4^(1), m^(5) - c\_4^(2), m^(7) - c\_4^(3), and m^(9) - c\_4^(4), leading to leaf nodes representing specific midamble-code pairs like m^(1) - c\_16^(1) through m^(10) - c\_16^(16). + +Figure AA.4: Association of Midambles to Spreading Codes for K=10 + +### AA.2.5 Association for K=8 Midambles + +![Tree diagram for K=8 showing the association of midambles m to spreading codes c. The root is m^{(1)} - c_1^{(1)}. It splits into m^{(1)} - c_2^{(1)} and m^{(5)} - c_2^{(2)}. These split into c_4 nodes: m^{(1)} - c_4^{(1)}, m^{(3)} - c_4^{(2)}, m^{(5)} - c_4^{(3)}, and m^{(7)} - c_4^{(4)}. These split into c_8 nodes: m^{(1)} - c_8^{(1)}, m^{(2)} - c_8^{(2)}, m^{(3)} - c_8^{(3)}, m^{(4)} - c_8^{(4)}, m^{(5)} - c_8^{(5)}, m^{(6)} - c_8^{(6)}, m^{(7)} - c_8^{(7)}, and m^{(8)} - c_8^{(8)}. Finally, each c_8 node splits into two c_{16} nodes, where the second node in each pair is marked with an asterisk: (m^{(1)} - c_{16}^{(1)}, m^{(1)} - c_{16}^{(2)*}), (m^{(2)} - c_{16}^{(3)}, m^{(2)} - c_{16}^{(4)*}), (m^{(3)} - c_{16}^{(5)}, m^{(3)} - c_{16}^{(6)*}), (m^{(4)} - c_{16}^{(7)}, m^{(4)} - c_{16}^{(8)*}), (m^{(5)} - c_{16}^{(9)}, m^{(5)} - c_{16}^{(10)*}), (m^{(6)} - c_{16}^{(11)}, m^{(6)} - c_{16}^{(12)*}), (m^{(7)} - c_{16}^{(13)}, m^{(7)} - c_{16}^{(14)*}), (m^{(8)} - c_{16}^{(15)}, m^{(8)} - c_{16}^{(16)*}).](184d3d9a856c77aae93652f4fe30f752_img.jpg) + +Tree diagram for K=8 showing the association of midambles m to spreading codes c. The root is m^{(1)} - c\_1^{(1)}. It splits into m^{(1)} - c\_2^{(1)} and m^{(5)} - c\_2^{(2)}. These split into c\_4 nodes: m^{(1)} - c\_4^{(1)}, m^{(3)} - c\_4^{(2)}, m^{(5)} - c\_4^{(3)}, and m^{(7)} - c\_4^{(4)}. These split into c\_8 nodes: m^{(1)} - c\_8^{(1)}, m^{(2)} - c\_8^{(2)}, m^{(3)} - c\_8^{(3)}, m^{(4)} - c\_8^{(4)}, m^{(5)} - c\_8^{(5)}, m^{(6)} - c\_8^{(6)}, m^{(7)} - c\_8^{(7)}, and m^{(8)} - c\_8^{(8)}. Finally, each c\_8 node splits into two c\_{16} nodes, where the second node in each pair is marked with an asterisk: (m^{(1)} - c\_{16}^{(1)}, m^{(1)} - c\_{16}^{(2)\*}), (m^{(2)} - c\_{16}^{(3)}, m^{(2)} - c\_{16}^{(4)\*}), (m^{(3)} - c\_{16}^{(5)}, m^{(3)} - c\_{16}^{(6)\*}), (m^{(4)} - c\_{16}^{(7)}, m^{(4)} - c\_{16}^{(8)\*}), (m^{(5)} - c\_{16}^{(9)}, m^{(5)} - c\_{16}^{(10)\*}), (m^{(6)} - c\_{16}^{(11)}, m^{(6)} - c\_{16}^{(12)\*}), (m^{(7)} - c\_{16}^{(13)}, m^{(7)} - c\_{16}^{(14)\*}), (m^{(8)} - c\_{16}^{(15)}, m^{(8)} - c\_{16}^{(16)\*}). + +Figure AA.5: Association of Midambles to Spreading Codes for K=8 + +### AA.2.6 Association for K=6 Midambles + +![Tree diagram for K=6 showing the association of midambles m to spreading codes c. The root is m^{(1)} - c_1^{(1)}. It splits into m^{(1)} - c_2^{(1)} and m^{(5)} - c_2^{(2)}. These split into c_4 nodes: m^{(1)} - c_4^{(1)}, m^{(3)} - c_4^{(2)}, m^{(5)} - c_4^{(3)}, and m^{(6)} - c_4^{(4)}. These split into c_8 nodes: m^{(1)} - c_8^{(1)}, m^{(2)} - c_8^{(2)}, m^{(3)} - c_8^{(3)}, m^{(4)} - c_8^{(4)}, m^{(5)} - c_8^{(5)}, m^{(5)} - c_8^{(6)*}, m^{(6)} - c_8^{(7)}, and m^{(6)} - c_8^{(8)*}. Finally, each c_8 node splits into two c_{16} nodes: (m^{(1)} - c_{16}^{(1)}, m^{(1)} - c_{16}^{(2)*}), (m^{(2)} - c_{16}^{(3)}, m^{(2)} - c_{16}^{(4)*}), (m^{(3)} - c_{16}^{(5)}, m^{(3)} - c_{16}^{(6)*}), (m^{(4)} - c_{16}^{(7)}, m^{(4)} - c_{16}^{(8)*}), (m^{(5)} - c_{16}^{(9)}, m^{(5)} - c_{16}^{(10)*}), (m^{(5)} - c_{16}^{(11)*}, m^{(5)} - c_{16}^{(12)*}), (m^{(6)} - c_{16}^{(13)}, m^{(6)} - c_{16}^{(14)*}), (m^{(6)} - c_{16}^{(15)*}, m^{(6)} - c_{16}^{(16)*}).](df935fc9efbd024af4ba77e46bb0bb19_img.jpg) + +Tree diagram for K=6 showing the association of midambles m to spreading codes c. The root is m^{(1)} - c\_1^{(1)}. It splits into m^{(1)} - c\_2^{(1)} and m^{(5)} - c\_2^{(2)}. These split into c\_4 nodes: m^{(1)} - c\_4^{(1)}, m^{(3)} - c\_4^{(2)}, m^{(5)} - c\_4^{(3)}, and m^{(6)} - c\_4^{(4)}. These split into c\_8 nodes: m^{(1)} - c\_8^{(1)}, m^{(2)} - c\_8^{(2)}, m^{(3)} - c\_8^{(3)}, m^{(4)} - c\_8^{(4)}, m^{(5)} - c\_8^{(5)}, m^{(5)} - c\_8^{(6)\*}, m^{(6)} - c\_8^{(7)}, and m^{(6)} - c\_8^{(8)\*}. Finally, each c\_8 node splits into two c\_{16} nodes: (m^{(1)} - c\_{16}^{(1)}, m^{(1)} - c\_{16}^{(2)\*}), (m^{(2)} - c\_{16}^{(3)}, m^{(2)} - c\_{16}^{(4)\*}), (m^{(3)} - c\_{16}^{(5)}, m^{(3)} - c\_{16}^{(6)\*}), (m^{(4)} - c\_{16}^{(7)}, m^{(4)} - c\_{16}^{(8)\*}), (m^{(5)} - c\_{16}^{(9)}, m^{(5)} - c\_{16}^{(10)\*}), (m^{(5)} - c\_{16}^{(11)\*}, m^{(5)} - c\_{16}^{(12)\*}), (m^{(6)} - c\_{16}^{(13)}, m^{(6)} - c\_{16}^{(14)\*}), (m^{(6)} - c\_{16}^{(15)\*}, m^{(6)} - c\_{16}^{(16)\*}). + +Figure AA.6: Association of Midambles to Spreading Codes for K=6 + +### AA.2.7 Association for K=4 Midambles + +![A hierarchical tree diagram showing the association of midambles to spreading codes for K=4. The root node is m^{(1)} - c_1^{(1)}, which branches into m^{(1)} - c_2^{(1)} and m^{(3)} - c_2^{(2)}. m^{(1)} - c_2^{(1)} branches into m^{(1)} - c_4^{(1)} and m^{(2)} - c_4^{(2)}. m^{(3)} - c_2^{(2)} branches into m^{(3)} - c_4^{(3)} and m^{(4)} - c_4^{(4)}. Further branches lead to m^{(1)} - c_8^{(1)}, m^{(1)} - c_8^{(2)*}, m^{(2)} - c_8^{(3)}, m^{(2)} - c_8^{(4)*}, m^{(3)} - c_8^{(5)}, m^{(3)} - c_8^{(6)*}, m^{(4)} - c_8^{(7)}, m^{(4)} - c_8^{(8)*}. Each of these 8 nodes branches into two spreading codes, resulting in 16 leaf nodes labeled m^{(1)} - c_{16}^{(1)} through m^{(4)} - c_{16}^{(16)*}.](c063ca3181a644e8ae4aebfd4cb1a2c3_img.jpg) + +A hierarchical tree diagram showing the association of midambles to spreading codes for K=4. The root node is m^{(1)} - c\_1^{(1)}, which branches into m^{(1)} - c\_2^{(1)} and m^{(3)} - c\_2^{(2)}. m^{(1)} - c\_2^{(1)} branches into m^{(1)} - c\_4^{(1)} and m^{(2)} - c\_4^{(2)}. m^{(3)} - c\_2^{(2)} branches into m^{(3)} - c\_4^{(3)} and m^{(4)} - c\_4^{(4)}. Further branches lead to m^{(1)} - c\_8^{(1)}, m^{(1)} - c\_8^{(2)\*}, m^{(2)} - c\_8^{(3)}, m^{(2)} - c\_8^{(4)\*}, m^{(3)} - c\_8^{(5)}, m^{(3)} - c\_8^{(6)\*}, m^{(4)} - c\_8^{(7)}, m^{(4)} - c\_8^{(8)\*}. Each of these 8 nodes branches into two spreading codes, resulting in 16 leaf nodes labeled m^{(1)} - c\_{16}^{(1)} through m^{(4)} - c\_{16}^{(16)\*}. + +Figure AA.7: Association of Midambles to Spreading Codes for K=4 + +### AA.2.8 Association for K=2 Midambles + +![A hierarchical tree diagram showing the association of midambles to spreading codes for K=2. The root node is m^{(1)} - c_1^{(1)}, which branches into m^{(1)} - c_2^{(1)} and m^{(2)} - c_2^{(2)}. m^{(1)} - c_2^{(1)} branches into m^{(1)} - c_4^{(1)} and m^{(1)} - c_4^{(2)*}. m^{(2)} - c_2^{(2)} branches into m^{(2)} - c_4^{(3)} and m^{(2)} - c_4^{(4)*}. Further branches lead to m^{(1)} - c_8^{(1)}, m^{(1)} - c_8^{(2)*}, m^{(1)} - c_8^{(3)*}, m^{(1)} - c_8^{(4)*}, m^{(2)} - c_8^{(5)}, m^{(2)} - c_8^{(6)*}, m^{(2)} - c_8^{(7)*}, m^{(2)} - c_8^{(8)*}. Each of these 8 nodes branches into two spreading codes, resulting in 16 leaf nodes labeled m^{(1)} - c_{16}^{(1)} through m^{(2)} - c_{16}^{(16)*}.](e35f25e0b66752d4179a4cb108a3fb5a_img.jpg) + +A hierarchical tree diagram showing the association of midambles to spreading codes for K=2. The root node is m^{(1)} - c\_1^{(1)}, which branches into m^{(1)} - c\_2^{(1)} and m^{(2)} - c\_2^{(2)}. m^{(1)} - c\_2^{(1)} branches into m^{(1)} - c\_4^{(1)} and m^{(1)} - c\_4^{(2)\*}. m^{(2)} - c\_2^{(2)} branches into m^{(2)} - c\_4^{(3)} and m^{(2)} - c\_4^{(4)\*}. Further branches lead to m^{(1)} - c\_8^{(1)}, m^{(1)} - c\_8^{(2)\*}, m^{(1)} - c\_8^{(3)\*}, m^{(1)} - c\_8^{(4)\*}, m^{(2)} - c\_8^{(5)}, m^{(2)} - c\_8^{(6)\*}, m^{(2)} - c\_8^{(7)\*}, m^{(2)} - c\_8^{(8)\*}. Each of these 8 nodes branches into two spreading codes, resulting in 16 leaf nodes labeled m^{(1)} - c\_{16}^{(1)} through m^{(2)} - c\_{16}^{(16)\*}. + +Figure AA.8: Association of Midambles to Spreading Codes for K=2 + +## AA.3 Association between Midambles and Channelisation Codes for special default midamble allocation + +The following mapping schemes apply for the association between midambles and channelisation codes if no midamble is allocated by higher layers. Secondary channelisation codes are marked with \*. These associations apply for both UL and DL. + +### AA.3.1 Association for K=16 Midambles + +![Figure AA.3.1a: Association of Midambles to Spreading Codes for K=16 pattern 1. This is a hierarchical tree diagram showing the mapping of midambles to spreading codes. The root node is m^{(1)} - c_1^{(1)}. It branches into two nodes: m^{(1)} - c_2^{(1)} and m^{(9)} - c_2^{(2)}. m^{(1)} - c_2^{(1)} branches into m^{(1)} - c_4^{(1)} and m^{(5)} - c_4^{(2)}. m^{(9)} - c_2^{(2)} branches into m^{(9)} - c_4^{(3)} and m^{(13)} - c_4^{(4)}. Further branches lead to m^{(1)} - c_8^{(1)}, m^{(1)} - c_8^{(2)*}, m^{(5)} - c_8^{(3)}, m^{(5)} - c_8^{(4)*}, m^{(9)} - c_8^{(5)}, m^{(9)} - c_8^{(6)*}, m^{(13)} - c_8^{(7)}, m^{(13)} - c_8^{(8)*}, m^{(15)} - c_8^{(9)}, and m^{(15)} - c_8^{(10)*}. Each of these 16 nodes finally branches into two spreading codes, resulting in 32 codes in total, labeled m^{(1)} - c_{16}^{(1)} through m^{(15)} - c_{16}^{(16)*}.](7472c67897a35ed6b67fcb47ea4c6b6c_img.jpg) + +Figure AA.3.1a: Association of Midambles to Spreading Codes for K=16 pattern 1. This is a hierarchical tree diagram showing the mapping of midambles to spreading codes. The root node is m^{(1)} - c\_1^{(1)}. It branches into two nodes: m^{(1)} - c\_2^{(1)} and m^{(9)} - c\_2^{(2)}. m^{(1)} - c\_2^{(1)} branches into m^{(1)} - c\_4^{(1)} and m^{(5)} - c\_4^{(2)}. m^{(9)} - c\_2^{(2)} branches into m^{(9)} - c\_4^{(3)} and m^{(13)} - c\_4^{(4)}. Further branches lead to m^{(1)} - c\_8^{(1)}, m^{(1)} - c\_8^{(2)\*}, m^{(5)} - c\_8^{(3)}, m^{(5)} - c\_8^{(4)\*}, m^{(9)} - c\_8^{(5)}, m^{(9)} - c\_8^{(6)\*}, m^{(13)} - c\_8^{(7)}, m^{(13)} - c\_8^{(8)\*}, m^{(15)} - c\_8^{(9)}, and m^{(15)} - c\_8^{(10)\*}. Each of these 16 nodes finally branches into two spreading codes, resulting in 32 codes in total, labeled m^{(1)} - c\_{16}^{(1)} through m^{(15)} - c\_{16}^{(16)\*}. + +Figure AA.3.1a: Association of Midambles to Spreading Codes for K=16 pattern 1 + +![Figure AA.3.1aa: Association of Midambles to Spreading Codes for K=16 pattern 1A. This diagram is similar to Figure AA.3.1a but with a different branching structure for the secondary codes. The root node is m^{(1)} - c_1^{(1)}. It branches into m^{(1)} - c_2^{(1)} and m^{(9)} - c_2^{(2)}. m^{(1)} - c_2^{(1)} branches into m^{(1)} - c_4^{(1)} and m^{(5)} - c_4^{(2)}. m^{(9)} - c_2^{(2)} branches into m^{(9)} - c_4^{(3)} and m^{(13)} - c_4^{(4)}. Further branches lead to m^{(1)} - c_8^{(1)}, m^{(1)} - c_8^{(2)*}, m^{(5)} - c_8^{(3)}, m^{(5)} - c_8^{(4)*}, m^{(9)} - c_8^{(5)}, m^{(9)} - c_8^{(6)*}, m^{(13)} - c_8^{(7)}, m^{(13)} - c_8^{(8)*}, m^{(15)} - c_8^{(9)}, and m^{(15)} - c_8^{(10)*}. Each of these 16 nodes finally branches into two spreading codes, resulting in 32 codes in total, labeled m^{(1)} - c_{16}^{(1)} through m^{(15)} - c_{16}^{(16)*}.](468be155058fd5d2862919eb8ec35496_img.jpg) + +Figure AA.3.1aa: Association of Midambles to Spreading Codes for K=16 pattern 1A. This diagram is similar to Figure AA.3.1a but with a different branching structure for the secondary codes. The root node is m^{(1)} - c\_1^{(1)}. It branches into m^{(1)} - c\_2^{(1)} and m^{(9)} - c\_2^{(2)}. m^{(1)} - c\_2^{(1)} branches into m^{(1)} - c\_4^{(1)} and m^{(5)} - c\_4^{(2)}. m^{(9)} - c\_2^{(2)} branches into m^{(9)} - c\_4^{(3)} and m^{(13)} - c\_4^{(4)}. Further branches lead to m^{(1)} - c\_8^{(1)}, m^{(1)} - c\_8^{(2)\*}, m^{(5)} - c\_8^{(3)}, m^{(5)} - c\_8^{(4)\*}, m^{(9)} - c\_8^{(5)}, m^{(9)} - c\_8^{(6)\*}, m^{(13)} - c\_8^{(7)}, m^{(13)} - c\_8^{(8)\*}, m^{(15)} - c\_8^{(9)}, and m^{(15)} - c\_8^{(10)\*}. Each of these 16 nodes finally branches into two spreading codes, resulting in 32 codes in total, labeled m^{(1)} - c\_{16}^{(1)} through m^{(15)} - c\_{16}^{(16)\*}. + +Figure AA.3.1aa: Association of Midambles to Spreading Codes for K=16 pattern 1A + +![A hierarchical tree diagram showing the association of Midambles to Spreading Codes for K=16 pattern 1B. The root node is m^(3) - c_1^(1), which branches into m^(3) - c_2^(1) and m^(11) - c_2^(2). Further sub-nodes include m^(3) - c_4^(1), m^(7) - c_4^(2), m^(11) - c_4^(3), m^(15) - c_4^(4), m^(3) - c_8^(1), m^(3) - c_8^(2)*, m^(7) - c_8^(3), m^(7) - c_8^(4)*, m^(11) - c_8^(5), m^(11) - c_8^(6)*, m^(15) - c_8^(7), m^(15) - c_8^(8)*. Each of these 8 nodes branches into two spreading codes, resulting in 16 leaf nodes labeled m^(3) - c_16^(1) through m^(15) - c_16^(16).](fc3e2b49a9f850951570e502393b697f_img.jpg) + +A hierarchical tree diagram showing the association of Midambles to Spreading Codes for K=16 pattern 1B. The root node is m^(3) - c\_1^(1), which branches into m^(3) - c\_2^(1) and m^(11) - c\_2^(2). Further sub-nodes include m^(3) - c\_4^(1), m^(7) - c\_4^(2), m^(11) - c\_4^(3), m^(15) - c\_4^(4), m^(3) - c\_8^(1), m^(3) - c\_8^(2)\*, m^(7) - c\_8^(3), m^(7) - c\_8^(4)\*, m^(11) - c\_8^(5), m^(11) - c\_8^(6)\*, m^(15) - c\_8^(7), m^(15) - c\_8^(8)\*. Each of these 8 nodes branches into two spreading codes, resulting in 16 leaf nodes labeled m^(3) - c\_16^(1) through m^(15) - c\_16^(16). + +Figure AA.3.1ab: Association of Midambles to Spreading Codes for K=16 pattern 1B + +![A hierarchical tree diagram showing the association of Midambles to Spreading Codes for K=16 pattern 2. The root node is m^(2) - c_1^(1), which branches into m^(2) - c_2^(1) and m^(10) - c_2^(2). Further sub-nodes include m^(2) - c_4^(1), m^(6) - c_4^(2), m^(10) - c_4^(3), m^(14) - c_4^(4), m^(2) - c_8^(1), m^(4) - c_8^(2), m^(6) - c_8^(3), m^(8) - c_8^(4), m^(10) - c_8^(5), m^(12) - c_8^(6), m^(14) - c_8^(7), m^(16) - c_8^(8). Each of these 8 nodes branches into two spreading codes, resulting in 16 leaf nodes labeled m^(2) - c_16^(1) through m^(16) - c_16^(16).](a320e67b369bfde4a5fa360b100da55c_img.jpg) + +A hierarchical tree diagram showing the association of Midambles to Spreading Codes for K=16 pattern 2. The root node is m^(2) - c\_1^(1), which branches into m^(2) - c\_2^(1) and m^(10) - c\_2^(2). Further sub-nodes include m^(2) - c\_4^(1), m^(6) - c\_4^(2), m^(10) - c\_4^(3), m^(14) - c\_4^(4), m^(2) - c\_8^(1), m^(4) - c\_8^(2), m^(6) - c\_8^(3), m^(8) - c\_8^(4), m^(10) - c\_8^(5), m^(12) - c\_8^(6), m^(14) - c\_8^(7), m^(16) - c\_8^(8). Each of these 8 nodes branches into two spreading codes, resulting in 16 leaf nodes labeled m^(2) - c\_16^(1) through m^(16) - c\_16^(16). + +Figure AA.3.1b: Association of Midambles to Spreading Codes for K=16 pattern 2 + +Error: + +104 + +Error: Reference source not + +![Tree diagram showing the association of Midambles to Spreading Codes for K=16 pattern 2A. The root node is m^{(2)} - c_1^{(1)}, which branches into m^{(2)} - c_2^{(1)} and m^{(10)} - c_2^{(2)}. Further branches lead to m^{(2)} - c_4^{(1)}, m^{(6)} - c_4^{(2)}, m^{(10)} - c_4^{(3)}, and m^{(14)} - c_4^{(4)}. These then branch into m^{(2)} - c_8^{(1)}, m^{(2)} - c_8^{(2)*}, m^{(6)} - c_8^{(3)}, m^{(6)} - c_8^{(4)*}, m^{(10)} - c_8^{(5)}, m^{(10)} - c_8^{(6)*}, m^{(14)} - c_8^{(7)}, and m^{(14)} - c_8^{(8)*}. Finally, these branch into 16 leaf nodes representing spreading codes c_{16}^{(1)} through c_{16}^{(16)*}.](6a993bfdf2e00cfad01c4d2188a75d86_img.jpg) + +``` +graph LR; Root["m^{(2)} - c_1^{(1)}"] --> M2C2["m^{(2)} - c_2^{(1)}"]; Root --> M10C2["m^{(10)} - c_2^{(2)}"]; M2C2 --> M2C4["m^{(2)} - c_4^{(1)}"]; M2C2 --> M6C4["m^{(6)} - c_4^{(2)}"]; M10C2 --> M10C4["m^{(10)} - c_4^{(3)}"]; M10C2 --> M14C4["m^{(14)} - c_4^{(4)}"]; M2C4 --> M2C8_1["m^{(2)} - c_8^{(1)}"]; M2C4 --> M2C8_2["m^{(2)} - c_8^{(2)*}"]; M6C4 --> M6C8_3["m^{(6)} - c_8^{(3)}"]; M6C4 --> M6C8_4["m^{(6)} - c_8^{(4)*}"]; M10C4 --> M10C8_5["m^{(10)} - c_8^{(5)}"]; M10C4 --> M10C8_6["m^{(10)} - c_8^{(6)*}"]; M14C4 --> M14C8_7["m^{(14)} - c_8^{(7)}"]; M14C4 --> M14C8_8["m^{(14)} - c_8^{(8)*}"]; M2C8_1 --> C16_1["m^{(2)} - c_{16}^{(1)}"]; M2C8_1 --> C16_2["m^{(2)} - c_{16}^{(2)*}"]; M2C8_2 --> C16_3["m^{(2)} - c_{16}^{(3)*}"]; M2C8_2 --> C16_4["m^{(2)} - c_{16}^{(4)*}"]; M6C8_3 --> C16_5["m^{(6)} - c_{16}^{(5)}"]; M6C8_3 --> C16_6["m^{(6)} - c_{16}^{(6)*}"]; M6C8_4 --> C16_7["m^{(6)} - c_{16}^{(7)*}"]; M6C8_4 --> C16_8["m^{(6)} - c_{16}^{(8)*}"]; M10C8_5 --> C16_9["m^{(10)} - c_{16}^{(9)}"]; M10C8_5 --> C16_10["m^{(10)} - c_{16}^{(10)*}"]; M10C8_6 --> C16_11["m^{(10)} - c_{16}^{(11)*}"]; M10C8_6 --> C16_12["m^{(10)} - c_{16}^{(12)*}"]; M14C8_7 --> C16_13["m^{(14)} - c_{16}^{(13)}"]; M14C8_7 --> C16_14["m^{(14)} - c_{16}^{(14)*}"]; M14C8_8 --> C16_15["m^{(14)} - c_{16}^{(15)*}"]; M14C8_8 --> C16_16["m^{(14)} - c_{16}^{(16)*}"]; +``` + +Tree diagram showing the association of Midambles to Spreading Codes for K=16 pattern 2A. The root node is m^{(2)} - c\_1^{(1)}, which branches into m^{(2)} - c\_2^{(1)} and m^{(10)} - c\_2^{(2)}. Further branches lead to m^{(2)} - c\_4^{(1)}, m^{(6)} - c\_4^{(2)}, m^{(10)} - c\_4^{(3)}, and m^{(14)} - c\_4^{(4)}. These then branch into m^{(2)} - c\_8^{(1)}, m^{(2)} - c\_8^{(2)\*}, m^{(6)} - c\_8^{(3)}, m^{(6)} - c\_8^{(4)\*}, m^{(10)} - c\_8^{(5)}, m^{(10)} - c\_8^{(6)\*}, m^{(14)} - c\_8^{(7)}, and m^{(14)} - c\_8^{(8)\*}. Finally, these branch into 16 leaf nodes representing spreading codes c\_{16}^{(1)} through c\_{16}^{(16)\*}. + +Figure AA.3.1ba: Association of Midambles to Spreading Codes for K=16 pattern 2A + +![Tree diagram showing the association of Midambles to Spreading Codes for K=16 pattern 2B. The root node is m^{(4)} - c_1^{(1)}, which branches into m^{(4)} - c_2^{(1)} and m^{(12)} - c_2^{(2)}. Further branches lead to m^{(4)} - c_4^{(1)}, m^{(8)} - c_4^{(2)}, m^{(12)} - c_4^{(3)}, and m^{(16)} - c_4^{(4)}. These then branch into m^{(4)} - c_8^{(1)}, m^{(4)} - c_8^{(2)*}, m^{(8)} - c_8^{(3)}, m^{(8)} - c_8^{(4)*}, m^{(12)} - c_8^{(5)}, m^{(12)} - c_8^{(6)*}, m^{(16)} - c_8^{(7)}, and m^{(16)} - c_8^{(8)*}. Finally, these branch into 16 leaf nodes representing spreading codes c_{16}^{(1)} through c_{16}^{(16)*}.](ff1a293f8118c0f00dbfeb0ab843d6e6_img.jpg) + +``` +graph LR; Root["m^{(4)} - c_1^{(1)}"] --> M4C2["m^{(4)} - c_2^{(1)}"]; Root --> M12C2["m^{(12)} - c_2^{(2)}"]; M4C2 --> M4C4["m^{(4)} - c_4^{(1)}"]; M4C2 --> M8C4["m^{(8)} - c_4^{(2)}"]; M12C2 --> M12C4["m^{(12)} - c_4^{(3)}"]; M12C2 --> M16C4["m^{(16)} - c_4^{(4)}"]; M4C4 --> M4C8_1["m^{(4)} - c_8^{(1)}"]; M4C4 --> M4C8_2["m^{(4)} - c_8^{(2)*}"]; M8C4 --> M8C8_3["m^{(8)} - c_8^{(3)}"]; M8C4 --> M8C8_4["m^{(8)} - c_8^{(4)*}"]; M12C4 --> M12C8_5["m^{(12)} - c_8^{(5)}"]; M12C4 --> M12C8_6["m^{(12)} - c_8^{(6)*}"]; M16C4 --> M16C8_7["m^{(16)} - c_8^{(7)}"]; M16C4 --> M16C8_8["m^{(16)} - c_8^{(8)*}"]; M4C8_1 --> C16_1["m^{(4)} - c_{16}^{(1)}"]; M4C8_1 --> C16_2["m^{(4)} - c_{16}^{(2)*}"]; M4C8_2 --> C16_3["m^{(4)} - c_{16}^{(3)*}"]; M4C8_2 --> C16_4["m^{(4)} - c_{16}^{(4)*}"]; M8C8_3 --> C16_5["m^{(8)} - c_{16}^{(5)}"]; M8C8_3 --> C16_6["m^{(8)} - c_{16}^{(6)*}"]; M8C8_4 --> C16_7["m^{(8)} - c_{16}^{(7)*}"]; M8C8_4 --> C16_8["m^{(8)} - c_{16}^{(8)*}"]; M12C8_5 --> C16_9["m^{(12)} - c_{16}^{(9)}"]; M12C8_5 --> C16_10["m^{(12)} - c_{16}^{(10)*}"]; M12C8_6 --> C16_11["m^{(12)} - c_{16}^{(11)*}"]; M12C8_6 --> C16_12["m^{(12)} - c_{16}^{(12)*}"]; M16C8_7 --> C16_13["m^{(16)} - c_{16}^{(13)}"]; M16C8_7 --> C16_14["m^{(16)} - c_{16}^{(14)*}"]; M16C8_8 --> C16_15["m^{(16)} - c_{16}^{(15)*}"]; M16C8_8 --> C16_16["m^{(16)} - c_{16}^{(16)*}"]; +``` + +Tree diagram showing the association of Midambles to Spreading Codes for K=16 pattern 2B. The root node is m^{(4)} - c\_1^{(1)}, which branches into m^{(4)} - c\_2^{(1)} and m^{(12)} - c\_2^{(2)}. Further branches lead to m^{(4)} - c\_4^{(1)}, m^{(8)} - c\_4^{(2)}, m^{(12)} - c\_4^{(3)}, and m^{(16)} - c\_4^{(4)}. These then branch into m^{(4)} - c\_8^{(1)}, m^{(4)} - c\_8^{(2)\*}, m^{(8)} - c\_8^{(3)}, m^{(8)} - c\_8^{(4)\*}, m^{(12)} - c\_8^{(5)}, m^{(12)} - c\_8^{(6)\*}, m^{(16)} - c\_8^{(7)}, and m^{(16)} - c\_8^{(8)\*}. Finally, these branch into 16 leaf nodes representing spreading codes c\_{16}^{(1)} through c\_{16}^{(16)\*}. + +Figure AA.3.1bb: Association of Midambles to Spreading Codes for K=16 pattern 2B + +### AA.3.2 Association for K=14 Midambles + +![A hierarchical tree diagram showing the association of midambles to spreading codes for K=14 pattern 1. The root node is m^{(1)} - c_1^{(1)}, which branches into m^{(1)} - c_2^{(1)} and m^{(9)} - c_2^{(2)}. Further branches lead to m^{(1)} - c_4^{(1)}, m^{(5)} - c_4^{(2)}, m^{(9)} - c_4^{(3)}, and m^{(13)} - c_4^{(4)}, which then lead to m^{(1)} - c_8^{(1)}, m^{(3)} - c_8^{(2)}, m^{(5)} - c_8^{(3)}, m^{(7)} - c_8^{(4)}, m^{(9)} - c_8^{(5)}, m^{(11)} - c_8^{(6)}, m^{(13)} - c_8^{(7)}, and m^{(13)} - c_8^{(8)}. Each of these leads to two leaf nodes representing spreading codes, such as m^{(1)} - c_{16}^{(1)} and m^{(1)} - c_{16}^{(2)*}.](c00d3fb4f9d9609639a6e7d7a356afd3_img.jpg) + +A hierarchical tree diagram showing the association of midambles to spreading codes for K=14 pattern 1. The root node is m^{(1)} - c\_1^{(1)}, which branches into m^{(1)} - c\_2^{(1)} and m^{(9)} - c\_2^{(2)}. Further branches lead to m^{(1)} - c\_4^{(1)}, m^{(5)} - c\_4^{(2)}, m^{(9)} - c\_4^{(3)}, and m^{(13)} - c\_4^{(4)}, which then lead to m^{(1)} - c\_8^{(1)}, m^{(3)} - c\_8^{(2)}, m^{(5)} - c\_8^{(3)}, m^{(7)} - c\_8^{(4)}, m^{(9)} - c\_8^{(5)}, m^{(11)} - c\_8^{(6)}, m^{(13)} - c\_8^{(7)}, and m^{(13)} - c\_8^{(8)}. Each of these leads to two leaf nodes representing spreading codes, such as m^{(1)} - c\_{16}^{(1)} and m^{(1)} - c\_{16}^{(2)\*}. + +Figure AA.3.2a: Association of Midambles to Spreading Codes for K=14 pattern 1 + +![A hierarchical tree diagram similar to Figure AA.3.2a, but with some nodes enclosed in rectangular boxes. The root node m^{(1)} - c_1^{(1)} is boxed. It branches into m^{(1)} - c_2^{(1)} (boxed) and m^{(9)} - c_2^{(2)} (boxed). m^{(1)} - c_2^{(1)} branches into m^{(1)} - c_4^{(1)} (boxed) and m^{(5)} - c_4^{(2)} (boxed). m^{(9)} - c_2^{(2)} branches into m^{(9)} - c_4^{(3)} (boxed) and m^{(13)} - c_4^{(4)} (boxed). Further branches lead to m^{(1)} - c_8^{(1)}, m^{(1)} - c_8^{(2)*}, m^{(5)} - c_8^{(3)}, m^{(5)} - c_8^{(4)*}, m^{(9)} - c_8^{(5)}, m^{(9)} - c_8^{(6)*}, m^{(13)} - c_8^{(7)}, and m^{(13)} - c_8^{(8)*}. Each of these leads to two leaf nodes representing spreading codes, such as m^{(1)} - c_{16}^{(1)} and m^{(1)} - c_{16}^{(2)*}.](e20792fef9de6560b2d6c5441da7614a_img.jpg) + +A hierarchical tree diagram similar to Figure AA.3.2a, but with some nodes enclosed in rectangular boxes. The root node m^{(1)} - c\_1^{(1)} is boxed. It branches into m^{(1)} - c\_2^{(1)} (boxed) and m^{(9)} - c\_2^{(2)} (boxed). m^{(1)} - c\_2^{(1)} branches into m^{(1)} - c\_4^{(1)} (boxed) and m^{(5)} - c\_4^{(2)} (boxed). m^{(9)} - c\_2^{(2)} branches into m^{(9)} - c\_4^{(3)} (boxed) and m^{(13)} - c\_4^{(4)} (boxed). Further branches lead to m^{(1)} - c\_8^{(1)}, m^{(1)} - c\_8^{(2)\*}, m^{(5)} - c\_8^{(3)}, m^{(5)} - c\_8^{(4)\*}, m^{(9)} - c\_8^{(5)}, m^{(9)} - c\_8^{(6)\*}, m^{(13)} - c\_8^{(7)}, and m^{(13)} - c\_8^{(8)\*}. Each of these leads to two leaf nodes representing spreading codes, such as m^{(1)} - c\_{16}^{(1)} and m^{(1)} - c\_{16}^{(2)\*}. + +Figure AA.3.2aa: Association of Midambles to Spreading Codes for K=14 pattern 1A + +Error: + +106 + +Error: Reference source not + +![Tree diagram showing the association of Midambles to Spreading Codes for K=14 pattern 1B. The root node is m^(3) - c_1^(1), which branches into m^(3) - c_2^(1) and m^(11) - c_2^(2). Further sub-nodes include m^(3) - c_4^(1), m^(7) - c_4^(2), m^(11) - c_4^(3), and m^(11) - c_4^(4)*, which further branch into m^(3) - c_8^(1), m^(3) - c_8^(2)*, m^(7) - c_8^(3), m^(7) - c_8^(4)*, m^(11) - c_8^(5), m^(11) - c_8^(6)*, m^(11) - c_8^(7)*, and m^(11) - c_8^(8)*. Each of these nodes finally branches into two spreading codes, such as m^(3) - c_16^(1) and m^(3) - c_16^(2)*.](e18841eb4a995df8354a793459e12fd0_img.jpg) + +The diagram shows a hierarchical tree structure for Pattern 1B. The root is $m^{(3)} - c_1^{(1)}$ . It splits into $m^{(3)} - c_2^{(1)}$ and $m^{(11)} - c_2^{(2)}$ . These further split into four nodes at the next level: $m^{(3)} - c_4^{(1)}$ , $m^{(7)} - c_4^{(2)}$ , $m^{(11)} - c_4^{(3)}$ , and $m^{(11)} - c_4^{(4)*}$ . The tree continues to branch until it reaches 16 leaf nodes representing spreading codes $c_{16}$ associated with midambles $m^{(3)}$ , $m^{(7)}$ , and $m^{(11)}$ . + +Tree diagram showing the association of Midambles to Spreading Codes for K=14 pattern 1B. The root node is m^(3) - c\_1^(1), which branches into m^(3) - c\_2^(1) and m^(11) - c\_2^(2). Further sub-nodes include m^(3) - c\_4^(1), m^(7) - c\_4^(2), m^(11) - c\_4^(3), and m^(11) - c\_4^(4)\*, which further branch into m^(3) - c\_8^(1), m^(3) - c\_8^(2)\*, m^(7) - c\_8^(3), m^(7) - c\_8^(4)\*, m^(11) - c\_8^(5), m^(11) - c\_8^(6)\*, m^(11) - c\_8^(7)\*, and m^(11) - c\_8^(8)\*. Each of these nodes finally branches into two spreading codes, such as m^(3) - c\_16^(1) and m^(3) - c\_16^(2)\*. + +**Figure AA.3.2ab: Association of Midambles to Spreading Codes for K=14 pattern 1B** + +![Tree diagram showing the association of Midambles to Spreading Codes for K=14 pattern 2. The root node is m^(2) - c_1^(1), which branches into m^(2) - c_2^(1) and m^(10) - c_2^(2). Further sub-nodes include m^(2) - c_4^(1), m^(6) - c_4^(2), m^(10) - c_4^(3), and m^(14) - c_4^(4), which further branch into m^(2) - c_8^(1), m^(4) - c_8^(2), m^(6) - c_8^(3), m^(8) - c_8^(4), m^(10) - c_8^(5), m^(12) - c_8^(6), m^(14) - c_8^(7), and m^(14) - c_8^(8)*. Each of these nodes finally branches into two spreading codes, such as m^(2) - c_16^(1) and m^(2) - c_16^(2)*.](9bafc60bf378685e5e246c3ffad7b792_img.jpg) + +The diagram shows a hierarchical tree structure for Pattern 2. The root is $m^{(2)} - c_1^{(1)}$ . It splits into $m^{(2)} - c_2^{(1)}$ and $m^{(10)} - c_2^{(2)}$ . These further split into four nodes: $m^{(2)} - c_4^{(1)}$ , $m^{(6)} - c_4^{(2)}$ , $m^{(10)} - c_4^{(3)}$ , and $m^{(14)} - c_4^{(4)}$ . The tree continues to branch until it reaches 16 leaf nodes representing spreading codes $c_{16}$ associated with midambles $m^{(2)}$ , $m^{(4)}$ , $m^{(6)}$ , $m^{(8)}$ , $m^{(10)}$ , $m^{(12)}$ , and $m^{(14)}$ . + +Tree diagram showing the association of Midambles to Spreading Codes for K=14 pattern 2. The root node is m^(2) - c\_1^(1), which branches into m^(2) - c\_2^(1) and m^(10) - c\_2^(2). Further sub-nodes include m^(2) - c\_4^(1), m^(6) - c\_4^(2), m^(10) - c\_4^(3), and m^(14) - c\_4^(4), which further branch into m^(2) - c\_8^(1), m^(4) - c\_8^(2), m^(6) - c\_8^(3), m^(8) - c\_8^(4), m^(10) - c\_8^(5), m^(12) - c\_8^(6), m^(14) - c\_8^(7), and m^(14) - c\_8^(8)\*. Each of these nodes finally branches into two spreading codes, such as m^(2) - c\_16^(1) and m^(2) - c\_16^(2)\*. + +**Figure AA.3.2b: Association of Midambles to Spreading Codes for K=14 pattern 2** + +![A hierarchical tree diagram showing the association of midambles to spreading codes for K=14 pattern 2A. The root node is m^{(2)} - c_1^{(1)}, which branches into m^{(2)} - c_2^{(1)} and m^{(10)} - c_2^{(2)}. These further branch into m^{(2)} - c_4^{(1)}, m^{(6)} - c_4^{(2)}, m^{(10)} - c_4^{(3)}, and m^{(14)} - c_4^{(4)}. Each of these branches into m^{(2)} - c_8^{(1)}, m^{(2)} - c_8^{(2)*}, m^{(6)} - c_8^{(3)}, m^{(6)} - c_8^{(4)*}, m^{(10)} - c_8^{(5)}, m^{(10)} - c_8^{(6)*}, m^{(14)} - c_8^{(7)}, and m^{(14)} - c_8^{(8)*}. Finally, each of these branches into two spreading codes, such as m^{(2)} - c_{16}^{(1)} and m^{(2)} - c_{16}^{(2)*}.](0b998e3ad8f9d104768642612605cb35_img.jpg) + +A hierarchical tree diagram showing the association of midambles to spreading codes for K=14 pattern 2A. The root node is m^{(2)} - c\_1^{(1)}, which branches into m^{(2)} - c\_2^{(1)} and m^{(10)} - c\_2^{(2)}. These further branch into m^{(2)} - c\_4^{(1)}, m^{(6)} - c\_4^{(2)}, m^{(10)} - c\_4^{(3)}, and m^{(14)} - c\_4^{(4)}. Each of these branches into m^{(2)} - c\_8^{(1)}, m^{(2)} - c\_8^{(2)\*}, m^{(6)} - c\_8^{(3)}, m^{(6)} - c\_8^{(4)\*}, m^{(10)} - c\_8^{(5)}, m^{(10)} - c\_8^{(6)\*}, m^{(14)} - c\_8^{(7)}, and m^{(14)} - c\_8^{(8)\*}. Finally, each of these branches into two spreading codes, such as m^{(2)} - c\_{16}^{(1)} and m^{(2)} - c\_{16}^{(2)\*}. + +Figure AA.3.2ba: Association of Midambles to Spreading Codes for K=14 pattern 2A + +![A hierarchical tree diagram showing the association of midambles to spreading codes for K=14 pattern 2B. The root node is m^{(4)} - c_1^{(1)}, which branches into m^{(4)} - c_2^{(1)} and m^{(12)} - c_2^{(2)}. These further branch into m^{(4)} - c_4^{(1)}, m^{(8)} - c_4^{(2)}, m^{(12)} - c_4^{(3)}, and m^{(12)} - c_4^{(4)}. Each of these branches into m^{(4)} - c_8^{(1)}, m^{(4)} - c_8^{(2)*}, m^{(8)} - c_8^{(3)}, m^{(8)} - c_8^{(4)*}, m^{(12)} - c_8^{(5)}, m^{(12)} - c_8^{(6)*}, m^{(12)} - c_8^{(7)}, and m^{(12)} - c_8^{(8)*}. Finally, each of these branches into two spreading codes, such as m^{(4)} - c_{16}^{(1)} and m^{(4)} - c_{16}^{(2)*}.](346324c08906e6d9320f632ab916f73e_img.jpg) + +A hierarchical tree diagram showing the association of midambles to spreading codes for K=14 pattern 2B. The root node is m^{(4)} - c\_1^{(1)}, which branches into m^{(4)} - c\_2^{(1)} and m^{(12)} - c\_2^{(2)}. These further branch into m^{(4)} - c\_4^{(1)}, m^{(8)} - c\_4^{(2)}, m^{(12)} - c\_4^{(3)}, and m^{(12)} - c\_4^{(4)}. Each of these branches into m^{(4)} - c\_8^{(1)}, m^{(4)} - c\_8^{(2)\*}, m^{(8)} - c\_8^{(3)}, m^{(8)} - c\_8^{(4)\*}, m^{(12)} - c\_8^{(5)}, m^{(12)} - c\_8^{(6)\*}, m^{(12)} - c\_8^{(7)}, and m^{(12)} - c\_8^{(8)\*}. Finally, each of these branches into two spreading codes, such as m^{(4)} - c\_{16}^{(1)} and m^{(4)} - c\_{16}^{(2)\*}. + +Figure AA.3.2bb: Association of Midambles to Spreading Codes for K=14 pattern 2B + +### AA.3.3 Association for K=12 Midambles + +![A hierarchical tree diagram showing the association of midambles to spreading codes for K=12 pattern 1. The root node is m^(1) - c_1^(1), which branches into m^(1) - c_2^(1) and m^(9) - c_2^(2). Further branches lead to nodes like m^(1) - c_4^(1), m^(5) - c_4^(2), m^(9) - c_4^(3), and m^(11) - c_4^(4), which then lead to m^(1) - c_8^(1), m^(3) - c_8^(2), m^(5) - c_8^(3), m^(7) - c_8^(4), m^(9) - c_8^(5), m^(9) - c_8^(6), m^(11) - c_8^(7), and m^(11) - c_8^(8). Finally, these lead to 16 leaf nodes representing spreading codes such as m^(1) - c_16^(1), m^(1) - c_16^(2)*, m^(3) - c_16^(3), m^(3) - c_16^(4)*, m^(5) - c_16^(5), m^(5) - c_16^(6)*, m^(7) - c_16^(7), m^(7) - c_16^(8)*, m^(9) - c_16^(9), m^(9) - c_16^(10)*, m^(9) - c_16^(11)*, m^(9) - c_16^(12)*, m^(11) - c_16^(13), m^(11) - c_16^(14)*, m^(11) - c_16^(15)*, and m^(11) - c_16^(16)*.](5ec3284657e4df0df3653dd61d0ecd13_img.jpg) + +A hierarchical tree diagram showing the association of midambles to spreading codes for K=12 pattern 1. The root node is m^(1) - c\_1^(1), which branches into m^(1) - c\_2^(1) and m^(9) - c\_2^(2). Further branches lead to nodes like m^(1) - c\_4^(1), m^(5) - c\_4^(2), m^(9) - c\_4^(3), and m^(11) - c\_4^(4), which then lead to m^(1) - c\_8^(1), m^(3) - c\_8^(2), m^(5) - c\_8^(3), m^(7) - c\_8^(4), m^(9) - c\_8^(5), m^(9) - c\_8^(6), m^(11) - c\_8^(7), and m^(11) - c\_8^(8). Finally, these lead to 16 leaf nodes representing spreading codes such as m^(1) - c\_16^(1), m^(1) - c\_16^(2)\*, m^(3) - c\_16^(3), m^(3) - c\_16^(4)\*, m^(5) - c\_16^(5), m^(5) - c\_16^(6)\*, m^(7) - c\_16^(7), m^(7) - c\_16^(8)\*, m^(9) - c\_16^(9), m^(9) - c\_16^(10)\*, m^(9) - c\_16^(11)\*, m^(9) - c\_16^(12)\*, m^(11) - c\_16^(13), m^(11) - c\_16^(14)\*, m^(11) - c\_16^(15)\*, and m^(11) - c\_16^(16)\*. + +Figure AA.3.3a: Association of Midambles to Spreading Codes for K=12 pattern 1 + +![A hierarchical tree diagram showing the association of midambles to spreading codes for K=12 pattern 1A. The root node is m^(1) - c_1^(1), which branches into m^(1) - c_2^(1) and m^(9) - c_2^(2). Further branches lead to nodes like m^(1) - c_4^(1), m^(5) - c_4^(2), m^(9) - c_4^(3), and m^(9) - c_4^(4), which then lead to m^(1) - c_8^(1), m^(1) - c_8^(2)*, m^(5) - c_8^(3), m^(5) - c_8^(4)*, m^(9) - c_8^(5), m^(9) - c_8^(6)*, m^(9) - c_8^(7)*, and m^(9) - c_8^(8)*. Finally, these lead to 16 leaf nodes representing spreading codes such as m^(1) - c_16^(1), m^(1) - c_16^(2)*, m^(1) - c_16^(3)*, m^(1) - c_16^(4)*, m^(5) - c_16^(5), m^(5) - c_16^(6)*, m^(5) - c_16^(7)*, m^(5) - c_16^(8)*, m^(9) - c_16^(9), m^(9) - c_16^(10)*, m^(9) - c_16^(11)*, m^(9) - c_16^(12)*, m^(9) - c_16^(13)*, m^(9) - c_16^(14)*, m^(9) - c_16^(15)*, and m^(9) - c_16^(16)*.](7c1ccebd0e8661557a8ffc00cfae58a0_img.jpg) + +A hierarchical tree diagram showing the association of midambles to spreading codes for K=12 pattern 1A. The root node is m^(1) - c\_1^(1), which branches into m^(1) - c\_2^(1) and m^(9) - c\_2^(2). Further branches lead to nodes like m^(1) - c\_4^(1), m^(5) - c\_4^(2), m^(9) - c\_4^(3), and m^(9) - c\_4^(4), which then lead to m^(1) - c\_8^(1), m^(1) - c\_8^(2)\*, m^(5) - c\_8^(3), m^(5) - c\_8^(4)\*, m^(9) - c\_8^(5), m^(9) - c\_8^(6)\*, m^(9) - c\_8^(7)\*, and m^(9) - c\_8^(8)\*. Finally, these lead to 16 leaf nodes representing spreading codes such as m^(1) - c\_16^(1), m^(1) - c\_16^(2)\*, m^(1) - c\_16^(3)\*, m^(1) - c\_16^(4)\*, m^(5) - c\_16^(5), m^(5) - c\_16^(6)\*, m^(5) - c\_16^(7)\*, m^(5) - c\_16^(8)\*, m^(9) - c\_16^(9), m^(9) - c\_16^(10)\*, m^(9) - c\_16^(11)\*, m^(9) - c\_16^(12)\*, m^(9) - c\_16^(13)\*, m^(9) - c\_16^(14)\*, m^(9) - c\_16^(15)\*, and m^(9) - c\_16^(16)\*. + +Figure AA.3.3aa: Association of Midambles to Spreading Codes for K=12 pattern 1A + +Error: + +109 + +Error: Reference source not + +![Tree diagram showing the association of Midambles to Spreading Codes for K=12 pattern 1B. The root node is m^{(3)} - c_1^{(1)}, which branches into m^{(3)} - c_2^{(1)} and m^{(11)} - c_2^{(2)}. m^{(3)} - c_2^{(1)} branches into m^{(3)} - c_4^{(1)} and m^{(7)} - c_4^{(2)}. m^{(11)} - c_2^{(2)} branches into m^{(11)} - c_4^{(3)} and m^{(11)} - c_4^{(4)*}. Further branches lead to m^{(3)} - c_8^{(1)}, m^{(3)} - c_8^{(2)*}, m^{(7)} - c_8^{(3)}, m^{(7)} - c_8^{(4)*}, m^{(11)} - c_8^{(5)}, m^{(11)} - c_8^{(6)*}, m^{(11)} - c_8^{(7)*}, and m^{(11)} - c_8^{(8)*}. Each of these nodes branches into two spreading codes at SF=16.](ba676d18b6a00f27c5bfaec9eeec20be_img.jpg) + +Tree diagram showing the association of Midambles to Spreading Codes for K=12 pattern 1B. The root node is m^{(3)} - c\_1^{(1)}, which branches into m^{(3)} - c\_2^{(1)} and m^{(11)} - c\_2^{(2)}. m^{(3)} - c\_2^{(1)} branches into m^{(3)} - c\_4^{(1)} and m^{(7)} - c\_4^{(2)}. m^{(11)} - c\_2^{(2)} branches into m^{(11)} - c\_4^{(3)} and m^{(11)} - c\_4^{(4)\*}. Further branches lead to m^{(3)} - c\_8^{(1)}, m^{(3)} - c\_8^{(2)\*}, m^{(7)} - c\_8^{(3)}, m^{(7)} - c\_8^{(4)\*}, m^{(11)} - c\_8^{(5)}, m^{(11)} - c\_8^{(6)\*}, m^{(11)} - c\_8^{(7)\*}, and m^{(11)} - c\_8^{(8)\*}. Each of these nodes branches into two spreading codes at SF=16. + +**Figure AA.3.3ab: Association of Midambles to Spreading Codes for K=12 pattern 1B** + +![Tree diagram showing the association of Midambles to Spreading Codes for K=12 pattern 2. The root node is m^{(2)} - c_1^{(1)}, which branches into m^{(2)} - c_2^{(1)} and m^{(10)} - c_2^{(2)}. m^{(2)} - c_2^{(1)} branches into m^{(2)} - c_4^{(1)} and m^{(6)} - c_4^{(2)}. m^{(10)} - c_2^{(2)} branches into m^{(10)} - c_4^{(3)} and m^{(12)} - c_4^{(4)}. Further branches lead to m^{(2)} - c_8^{(1)}, m^{(4)} - c_8^{(2)}, m^{(6)} - c_8^{(3)}, m^{(8)} - c_8^{(4)}, m^{(10)} - c_8^{(5)}, m^{(10)} - c_8^{(6)*}, m^{(12)} - c_8^{(7)}, and m^{(12)} - c_8^{(8)*}. Each of these nodes branches into two spreading codes at SF=16.](b4c825454b7a89b4d7744e4f45521174_img.jpg) + +Tree diagram showing the association of Midambles to Spreading Codes for K=12 pattern 2. The root node is m^{(2)} - c\_1^{(1)}, which branches into m^{(2)} - c\_2^{(1)} and m^{(10)} - c\_2^{(2)}. m^{(2)} - c\_2^{(1)} branches into m^{(2)} - c\_4^{(1)} and m^{(6)} - c\_4^{(2)}. m^{(10)} - c\_2^{(2)} branches into m^{(10)} - c\_4^{(3)} and m^{(12)} - c\_4^{(4)}. Further branches lead to m^{(2)} - c\_8^{(1)}, m^{(4)} - c\_8^{(2)}, m^{(6)} - c\_8^{(3)}, m^{(8)} - c\_8^{(4)}, m^{(10)} - c\_8^{(5)}, m^{(10)} - c\_8^{(6)\*}, m^{(12)} - c\_8^{(7)}, and m^{(12)} - c\_8^{(8)\*}. Each of these nodes branches into two spreading codes at SF=16. + +**Figure AA.3.3b: Association of Midambles to Spreading Codes for K=12 pattern 2** + +Error: + +110 + +Error: Reference source not + +![Tree diagram showing the association of Midambles to Spreading Codes for K=12 pattern 2A. The root node is m^{(2)} - c_1^{(1)}, which branches into m^{(2)} - c_2^{(1)} and m^{(10)} - c_2^{(2)}. Further sub-nodes include m^{(2)} - c_4^{(1)}, m^{(6)} - c_4^{(2)}, m^{(10)} - c_4^{(3)}, and m^{(10)} - c_4^{(4)}, which further branch into m^{(2)} - c_8^{(1)}, m^{(2)} - c_8^{(2)}, m^{(6)} - c_8^{(3)}, m^{(6)} - c_8^{(4)}, m^{(10)} - c_8^{(5)}, m^{(10)} - c_8^{(6)}, m^{(10)} - c_8^{(7)}, and m^{(10)} - c_8^{(8)}. Each of these nodes finally branches into two spreading codes, such as m^{(2)} - c_{16}^{(1)} and m^{(2)} - c_{16}^{(2)*}.](a5404b7275b06497eecf9b5883604753_img.jpg) + +Tree diagram showing the association of Midambles to Spreading Codes for K=12 pattern 2A. The root node is m^{(2)} - c\_1^{(1)}, which branches into m^{(2)} - c\_2^{(1)} and m^{(10)} - c\_2^{(2)}. Further sub-nodes include m^{(2)} - c\_4^{(1)}, m^{(6)} - c\_4^{(2)}, m^{(10)} - c\_4^{(3)}, and m^{(10)} - c\_4^{(4)}, which further branch into m^{(2)} - c\_8^{(1)}, m^{(2)} - c\_8^{(2)}, m^{(6)} - c\_8^{(3)}, m^{(6)} - c\_8^{(4)}, m^{(10)} - c\_8^{(5)}, m^{(10)} - c\_8^{(6)}, m^{(10)} - c\_8^{(7)}, and m^{(10)} - c\_8^{(8)}. Each of these nodes finally branches into two spreading codes, such as m^{(2)} - c\_{16}^{(1)} and m^{(2)} - c\_{16}^{(2)\*}. + +Figure AA.3.3ba: Association of Midambles to Spreading Codes for K=12 pattern 2A + +![Tree diagram showing the association of Midambles to Spreading Codes for K=12 pattern 2B. The root node is m^{(4)} - c_1^{(1)}, which branches into m^{(4)} - c_2^{(1)} and m^{(12)} - c_2^{(2)}. Further sub-nodes include m^{(4)} - c_4^{(1)}, m^{(8)} - c_4^{(2)}, m^{(12)} - c_4^{(3)}, and m^{(12)} - c_4^{(4)}, which further branch into m^{(4)} - c_8^{(1)}, m^{(4)} - c_8^{(2)}, m^{(8)} - c_8^{(3)}, m^{(8)} - c_8^{(4)}, m^{(12)} - c_8^{(5)}, m^{(12)} - c_8^{(6)}, m^{(12)} - c_8^{(7)}, and m^{(12)} - c_8^{(8)}. Each of these nodes finally branches into two spreading codes, such as m^{(4)} - c_{16}^{(1)} and m^{(4)} - c_{16}^{(2)*}.](1187dbd674a100960ed23efa54ccd6c1_img.jpg) + +Tree diagram showing the association of Midambles to Spreading Codes for K=12 pattern 2B. The root node is m^{(4)} - c\_1^{(1)}, which branches into m^{(4)} - c\_2^{(1)} and m^{(12)} - c\_2^{(2)}. Further sub-nodes include m^{(4)} - c\_4^{(1)}, m^{(8)} - c\_4^{(2)}, m^{(12)} - c\_4^{(3)}, and m^{(12)} - c\_4^{(4)}, which further branch into m^{(4)} - c\_8^{(1)}, m^{(4)} - c\_8^{(2)}, m^{(8)} - c\_8^{(3)}, m^{(8)} - c\_8^{(4)}, m^{(12)} - c\_8^{(5)}, m^{(12)} - c\_8^{(6)}, m^{(12)} - c\_8^{(7)}, and m^{(12)} - c\_8^{(8)}. Each of these nodes finally branches into two spreading codes, such as m^{(4)} - c\_{16}^{(1)} and m^{(4)} - c\_{16}^{(2)\*}. + +Figure AA.3.3bb: Association of Midambles to Spreading Codes for K=12 pattern 2B + +### AA.3.4 Association for K=10 Midambles + +![Tree diagram showing the association of Midambles to Spreading Codes for K=10 pattern 1. The root node is m^{(1)} - c_1^{(1)}, which branches into m^{(1)} - c_2^{(1)} and m^{(7)} - c_2^{(2)}. m^{(1)} - c_2^{(1)} branches into m^{(1)} - c_4^{(1)} and m^{(5)} - c_4^{(2)}. m^{(7)} - c_2^{(2)} branches into m^{(7)} - c_4^{(3)} and m^{(9)} - c_4^{(4)}. Further branches lead to leaf nodes representing spreading codes like m^{(1)} - c_{16}^{(1)} through m^{(9)} - c_{16}^{(16)}.](a66383962afcd0f0458f0d45c101fabf_img.jpg) + +The diagram illustrates a hierarchical tree structure for associating midambles to spreading codes. The root node is $m^{(1)} - c_1^{(1)}$ . It branches into two main paths: $m^{(1)} - c_2^{(1)}$ and $m^{(7)} - c_2^{(2)}$ . The $m^{(1)} - c_2^{(1)}$ path further branches into $m^{(1)} - c_4^{(1)}$ and $m^{(5)} - c_4^{(2)}$ . The $m^{(7)} - c_2^{(2)}$ path branches into $m^{(7)} - c_4^{(3)}$ and $m^{(9)} - c_4^{(4)}$ . Each of these four nodes then branches into two sub-nodes, $m^{(\cdot)} - c_8^{(\cdot)}$ , which finally branch into leaf nodes representing spreading codes $m^{(\cdot)} - c_{16}^{(\cdot)}$ . The leaf nodes are: $m^{(1)} - c_{16}^{(1)}$ , $m^{(1)} - c_{16}^{(2)*}$ , $m^{(3)} - c_{16}^{(3)}$ , $m^{(3)} - c_{16}^{(4)*}$ , $m^{(5)} - c_{16}^{(5)}$ , $m^{(5)} - c_{16}^{(6)*}$ , $m^{(5)} - c_{16}^{(7)*}$ , $m^{(5)} - c_{16}^{(8)*}$ , $m^{(7)} - c_{16}^{(9)}$ , $m^{(7)} - c_{16}^{(10)*}$ , $m^{(7)} - c_{16}^{(11)*}$ , $m^{(7)} - c_{16}^{(12)*}$ , $m^{(9)} - c_{16}^{(13)}$ , $m^{(9)} - c_{16}^{(14)*}$ , $m^{(9)} - c_{16}^{(15)*}$ , and $m^{(9)} - c_{16}^{(16)*}$ . + +Tree diagram showing the association of Midambles to Spreading Codes for K=10 pattern 1. The root node is m^{(1)} - c\_1^{(1)}, which branches into m^{(1)} - c\_2^{(1)} and m^{(7)} - c\_2^{(2)}. m^{(1)} - c\_2^{(1)} branches into m^{(1)} - c\_4^{(1)} and m^{(5)} - c\_4^{(2)}. m^{(7)} - c\_2^{(2)} branches into m^{(7)} - c\_4^{(3)} and m^{(9)} - c\_4^{(4)}. Further branches lead to leaf nodes representing spreading codes like m^{(1)} - c\_{16}^{(1)} through m^{(9)} - c\_{16}^{(16)}. + +Figure AA.3.4a: Association of Midambles to Spreading Codes for K=10 pattern 1 + +![Tree diagram showing the association of Midambles to Spreading Codes for K=10 pattern 1A. The root node is m^{(1)} - c_1^{(1)}, which branches into m^{(1)} - c_2^{(1)} and m^{(9)} - c_2^{(2)}. m^{(1)} - c_2^{(1)} branches into m^{(1)} - c_4^{(1)} and m^{(5)} - c_4^{(2)}. m^{(9)} - c_2^{(2)} branches into m^{(9)} - c_4^{(3)} and m^{(9)} - c_4^{(4)}. Further branches lead to leaf nodes representing spreading codes like m^{(1)} - c_{16}^{(1)} through m^{(9)} - c_{16}^{(16)}.](591746e6f224b8d929697a200e87e976_img.jpg) + +The diagram illustrates a hierarchical tree structure for associating midambles to spreading codes. The root node is $m^{(1)} - c_1^{(1)}$ . It branches into two main paths: $m^{(1)} - c_2^{(1)}$ and $m^{(9)} - c_2^{(2)}$ . The $m^{(1)} - c_2^{(1)}$ path further branches into $m^{(1)} - c_4^{(1)}$ and $m^{(5)} - c_4^{(2)}$ . The $m^{(9)} - c_2^{(2)}$ path branches into $m^{(9)} - c_4^{(3)}$ and $m^{(9)} - c_4^{(4)}$ . Each of these four nodes then branches into two sub-nodes, $m^{(\cdot)} - c_8^{(\cdot)}$ , which finally branch into leaf nodes representing spreading codes $m^{(\cdot)} - c_{16}^{(\cdot)}$ . The leaf nodes are: $m^{(1)} - c_{16}^{(1)}$ , $m^{(1)} - c_{16}^{(2)*}$ , $m^{(1)} - c_{16}^{(3)*}$ , $m^{(1)} - c_{16}^{(4)*}$ , $m^{(5)} - c_{16}^{(5)}$ , $m^{(5)} - c_{16}^{(6)*}$ , $m^{(5)} - c_{16}^{(7)*}$ , $m^{(5)} - c_{16}^{(8)*}$ , $m^{(9)} - c_{16}^{(9)}$ , $m^{(9)} - c_{16}^{(10)*}$ , $m^{(9)} - c_{16}^{(11)*}$ , $m^{(9)} - c_{16}^{(12)*}$ , $m^{(9)} - c_{16}^{(13)*}$ , $m^{(9)} - c_{16}^{(14)*}$ , $m^{(9)} - c_{16}^{(15)*}$ , and $m^{(9)} - c_{16}^{(16)*}$ . + +Tree diagram showing the association of Midambles to Spreading Codes for K=10 pattern 1A. The root node is m^{(1)} - c\_1^{(1)}, which branches into m^{(1)} - c\_2^{(1)} and m^{(9)} - c\_2^{(2)}. m^{(1)} - c\_2^{(1)} branches into m^{(1)} - c\_4^{(1)} and m^{(5)} - c\_4^{(2)}. m^{(9)} - c\_2^{(2)} branches into m^{(9)} - c\_4^{(3)} and m^{(9)} - c\_4^{(4)}. Further branches lead to leaf nodes representing spreading codes like m^{(1)} - c\_{16}^{(1)} through m^{(9)} - c\_{16}^{(16)}. + +Figure AA.3.4aa: Association of Midambles to Spreading Codes for K=10 pattern 1A + +Error: + +112 + +Error: Reference source not + +![Tree diagram showing the association of Midambles to Spreading Codes for K=10 pattern 1B. The root node is m^(3) - c_1^(1), which branches into m^(3) - c_2^(1) and m^(7) - c_2^(2). m^(3) - c_2^(1) branches into m^(3) - c_4^(1) and m^(3) - c_4^(2)*. m^(3) - c_4^(1) branches into m^(3) - c_8^(1) and m^(3) - c_8^(2)*. m^(3) - c_8^(1) branches into m^(3) - c_16^(1) and m^(3) - c_16^(2)*. m^(3) - c_8^(2)* branches into m^(3) - c_16^(3)* and m^(3) - c_16^(4)*. m^(3) - c_4^(2)* branches into m^(3) - c_8^(3)* and m^(3) - c_8^(4)*. m^(3) - c_8^(3)* branches into m^(3) - c_16^(5)* and m^(3) - c_16^(6)*. m^(3) - c_8^(4)* branches into m^(3) - c_16^(7)* and m^(3) - c_16^(8)*. m^(7) - c_2^(2) branches into m^(7) - c_4^(3) and m^(7) - c_4^(4)*. m^(7) - c_4^(3) branches into m^(7) - c_8^(5) and m^(7) - c_8^(6)*. m^(7) - c_8^(5) branches into m^(7) - c_16^(9) and m^(7) - c_16^(10)*. m^(7) - c_8^(6)* branches into m^(7) - c_16^(11)* and m^(7) - c_16^(12)*. m^(7) - c_4^(4)* branches into m^(7) - c_8^(7)* and m^(7) - c_8^(8)*. m^(7) - c_8^(7)* branches into m^(7) - c_16^(13)* and m^(7) - c_16^(14)*. m^(7) - c_8^(8)* branches into m^(7) - c_16^(15)* and m^(7) - c_16^(16)*.](9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg) + +``` + + graph LR + A["m(3) - c1(1)"] --> B["m(3) - c2(1)"] + A --> C["m(7) - c2(2)"] + B --> D["m(3) - c4(1)"] + B --> E["m(3) - c4(2)*"] + D --> F["m(3) - c8(1)"] + D --> G["m(3) - c8(2)*"] + F --> H["m(3) - c16(1)"] + F --> I["m(3) - c16(2)*"] + G --> J["m(3) - c16(3)*"] + G --> K["m(3) - c16(4)*"] + E --> L["m(3) - c8(3)*"] + E --> M["m(3) - c8(4)*"] + L --> N["m(3) - c16(5)*"] + L --> O["m(3) - c16(6)*"] + M --> P["m(3) - c16(7)*"] + M --> Q["m(3) - c16(8)*"] + C --> R["m(7) - c4(3)"] + C --> S["m(7) - c4(4)*"] + R --> T["m(7) - c8(5)"] + R --> U["m(7) - c8(6)*"] + T --> V["m(7) - c16(9)"] + T --> W["m(7) - c16(10)*"] + U --> X["m(7) - c16(11)*"] + U --> Y["m(7) - c16(12)*"] + S --> Z["m(7) - c8(7)*"] + S --> AA["m(7) - c8(8)*"] + Z --> AB["m(7) - c16(13)*"] + Z --> AC["m(7) - c16(14)*"] + AA --> AD["m(7) - c16(15)*"] + AA --> AE["m(7) - c16(16)*"] + +``` + +Tree diagram showing the association of Midambles to Spreading Codes for K=10 pattern 1B. The root node is m^(3) - c\_1^(1), which branches into m^(3) - c\_2^(1) and m^(7) - c\_2^(2). m^(3) - c\_2^(1) branches into m^(3) - c\_4^(1) and m^(3) - c\_4^(2)\*. m^(3) - c\_4^(1) branches into m^(3) - c\_8^(1) and m^(3) - c\_8^(2)\*. m^(3) - c\_8^(1) branches into m^(3) - c\_16^(1) and m^(3) - c\_16^(2)\*. m^(3) - c\_8^(2)\* branches into m^(3) - c\_16^(3)\* and m^(3) - c\_16^(4)\*. m^(3) - c\_4^(2)\* branches into m^(3) - c\_8^(3)\* and m^(3) - c\_8^(4)\*. m^(3) - c\_8^(3)\* branches into m^(3) - c\_16^(5)\* and m^(3) - c\_16^(6)\*. m^(3) - c\_8^(4)\* branches into m^(3) - c\_16^(7)\* and m^(3) - c\_16^(8)\*. m^(7) - c\_2^(2) branches into m^(7) - c\_4^(3) and m^(7) - c\_4^(4)\*. m^(7) - c\_4^(3) branches into m^(7) - c\_8^(5) and m^(7) - c\_8^(6)\*. m^(7) - c\_8^(5) branches into m^(7) - c\_16^(9) and m^(7) - c\_16^(10)\*. m^(7) - c\_8^(6)\* branches into m^(7) - c\_16^(11)\* and m^(7) - c\_16^(12)\*. m^(7) - c\_4^(4)\* branches into m^(7) - c\_8^(7)\* and m^(7) - c\_8^(8)\*. m^(7) - c\_8^(7)\* branches into m^(7) - c\_16^(13)\* and m^(7) - c\_16^(14)\*. m^(7) - c\_8^(8)\* branches into m^(7) - c\_16^(15)\* and m^(7) - c\_16^(16)\*. + +Figure AA.3.4ab: Association of Midambles to Spreading Codes for K=10 pattern 1B + +![Tree diagram showing the association of Midambles to Spreading Codes for K=10 pattern 2. The root node is m^(2) - c_1^(1), which branches into m^(2) - c_2^(1) and m^(8) - c_2^(2). m^(2) - c_2^(1) branches into m^(2) - c_4^(1) and m^(6) - c_4^(2). m^(2) - c_4^(1) branches into m^(2) - c_8^(1) and m^(4) - c_8^(2). m^(2) - c_8^(1) branches into m^(2) - c_16^(1) and m^(2) - c_16^(2)*. m^(4) - c_8^(2) branches into m^(4) - c_16^(3) and m^(4) - c_16^(4)*. m^(6) - c_4^(2) branches into m^(6) - c_8^(3) and m^(6) - c_8^(4)*. m^(6) - c_8^(3) branches into m^(6) - c_16^(5) and m^(6) - c_16^(6)*. m^(6) - c_8^(4)* branches into m^(6) - c_16^(7)* and m^(6) - c_16^(8)*. m^(8) - c_2^(2) branches into m^(8) - c_4^(3) and m^(10) - c_4^(4). m^(8) - c_4^(3) branches into m^(8) - c_8^(5) and m^(8) - c_8^(6)*. m^(8) - c_8^(5) branches into m^(8) - c_16^(9) and m^(8) - c_16^(10)*. m^(8) - c_8^(6)* branches into m^(8) - c_16^(11)* and m^(8) - c_16^(12)*. m^(10) - c_4^(4) branches into m^(10) - c_8^(7) and m^(10) - c_8^(8)*. m^(10) - c_8^(7) branches into m^(10) - c_16^(13) and m^(10) - c_16^(14)*. m^(10) - c_8^(8)* branches into m^(10) - c_16^(15)* and m^(10) - c_16^(16)*.](64bec4cd45e47e1976245711f702aca2_img.jpg) + +``` + + graph LR + A["m(2) - c1(1)"] --> B["m(2) - c2(1)"] + A --> C["m(8) - c2(2)"] + B --> D["m(2) - c4(1)"] + B --> E["m(6) - c4(2)"] + D --> F["m(2) - c8(1)"] + D --> G["m(4) - c8(2)"] + F --> H["m(2) - c16(1)"] + F --> I["m(2) - c16(2)*"] + G --> J["m(4) - c16(3)"] + G --> K["m(4) - c16(4)*"] + E --> L["m(6) - c8(3)"] + E --> M["m(6) - c8(4)*"] + L --> N["m(6) - c16(5)"] + L --> O["m(6) - c16(6)*"] + M --> P["m(6) - c16(7)*"] + M --> Q["m(6) - c16(8)*"] + C --> R["m(8) - c4(3)"] + C --> S["m(10) - c4(4)"] + R --> T["m(8) - c8(5)"] + R --> U["m(8) - c8(6)*"] + T --> V["m(8) - c16(9)"] + T --> W["m(8) - c16(10)*"] + U --> X["m(8) - c16(11)*"] + U --> Y["m(8) - c16(12)*"] + S --> Z["m(10) - c8(7)"] + S --> AA["m(10) - c8(8)*"] + Z --> AB["m(10) - c16(13)"] + Z --> AC["m(10) - c16(14)*"] + AA --> AD["m(10) - c16(15)*"] + AA --> AE["m(10) - c16(16)*"] + +``` + +Tree diagram showing the association of Midambles to Spreading Codes for K=10 pattern 2. The root node is m^(2) - c\_1^(1), which branches into m^(2) - c\_2^(1) and m^(8) - c\_2^(2). m^(2) - c\_2^(1) branches into m^(2) - c\_4^(1) and m^(6) - c\_4^(2). m^(2) - c\_4^(1) branches into m^(2) - c\_8^(1) and m^(4) - c\_8^(2). m^(2) - c\_8^(1) branches into m^(2) - c\_16^(1) and m^(2) - c\_16^(2)\*. m^(4) - c\_8^(2) branches into m^(4) - c\_16^(3) and m^(4) - c\_16^(4)\*. m^(6) - c\_4^(2) branches into m^(6) - c\_8^(3) and m^(6) - c\_8^(4)\*. m^(6) - c\_8^(3) branches into m^(6) - c\_16^(5) and m^(6) - c\_16^(6)\*. m^(6) - c\_8^(4)\* branches into m^(6) - c\_16^(7)\* and m^(6) - c\_16^(8)\*. m^(8) - c\_2^(2) branches into m^(8) - c\_4^(3) and m^(10) - c\_4^(4). m^(8) - c\_4^(3) branches into m^(8) - c\_8^(5) and m^(8) - c\_8^(6)\*. m^(8) - c\_8^(5) branches into m^(8) - c\_16^(9) and m^(8) - c\_16^(10)\*. m^(8) - c\_8^(6)\* branches into m^(8) - c\_16^(11)\* and m^(8) - c\_16^(12)\*. m^(10) - c\_4^(4) branches into m^(10) - c\_8^(7) and m^(10) - c\_8^(8)\*. m^(10) - c\_8^(7) branches into m^(10) - c\_16^(13) and m^(10) - c\_16^(14)\*. m^(10) - c\_8^(8)\* branches into m^(10) - c\_16^(15)\* and m^(10) - c\_16^(16)\*. + +Figure AA.3.4b: Association of Midambles to Spreading Codes for K=10 pattern 2 + +![Tree diagram showing the association of Midambles to Spreading Codes for K=10 pattern 2A. The root node is m^(2) - c_1^(1), which branches into m^(2) - c_2^(1) and m^(10) - c_2^(2). m^(2) - c_2^(1) branches into m^(2) - c_4^(1) and m^(6) - c_4^(2). m^(10) - c_2^(2) branches into m^(10) - c_4^(3) and m^(10) - c_4^(4). Further branches lead to leaf nodes representing spreading codes c_16^(1) through c_16^(16).](17431d8b59408f09df7552d8bdbaa015_img.jpg) + +Diagram illustrating the association of Midambles to Spreading Codes for K=10 pattern 2A. The tree structure shows the hierarchical decomposition of the root node $m^{(2)} - c_1^{(1)}$ into various intermediate nodes and finally into 16 leaf nodes representing spreading codes $c_{16}^{(1)}$ through $c_{16}^{(16)}$ . + +The root node $m^{(2)} - c_1^{(1)}$ branches into $m^{(2)} - c_2^{(1)}$ and $m^{(10)} - c_2^{(2)}$ . + +$m^{(2)} - c_2^{(1)}$ branches into $m^{(2)} - c_4^{(1)}$ and $m^{(6)} - c_4^{(2)}$ . + +$m^{(10)} - c_2^{(2)}$ branches into $m^{(10)} - c_4^{(3)}$ and $m^{(10)} - c_4^{(4)}$ . + +$m^{(2)} - c_4^{(1)}$ branches into $m^{(2)} - c_8^{(1)}$ and $m^{(2)} - c_8^{(2)}$ . + +$m^{(6)} - c_4^{(2)}$ branches into $m^{(6)} - c_8^{(3)}$ and $m^{(6)} - c_8^{(4)}$ . + +$m^{(10)} - c_4^{(3)}$ branches into $m^{(10)} - c_8^{(5)}$ and $m^{(10)} - c_8^{(6)}$ . + +$m^{(10)} - c_4^{(4)}$ branches into $m^{(10)} - c_8^{(7)}$ and $m^{(10)} - c_8^{(8)}$ . + +The leaf nodes are: + +- $m^{(2)} - c_{16}^{(1)}$ , $m^{(2)} - c_{16}^{(2)}$ , $m^{(2)} - c_{16}^{(3)}$ , $m^{(2)} - c_{16}^{(4)}$ +- $m^{(6)} - c_{16}^{(5)}$ , $m^{(6)} - c_{16}^{(6)}$ , $m^{(6)} - c_{16}^{(7)}$ , $m^{(6)} - c_{16}^{(8)}$ +- $m^{(10)} - c_{16}^{(9)}$ , $m^{(10)} - c_{16}^{(10)}$ , $m^{(10)} - c_{16}^{(11)}$ , $m^{(10)} - c_{16}^{(12)}$ +- $m^{(10)} - c_{16}^{(13)}$ , $m^{(10)} - c_{16}^{(14)}$ , $m^{(10)} - c_{16}^{(15)}$ , $m^{(10)} - c_{16}^{(16)}$ + +Tree diagram showing the association of Midambles to Spreading Codes for K=10 pattern 2A. The root node is m^(2) - c\_1^(1), which branches into m^(2) - c\_2^(1) and m^(10) - c\_2^(2). m^(2) - c\_2^(1) branches into m^(2) - c\_4^(1) and m^(6) - c\_4^(2). m^(10) - c\_2^(2) branches into m^(10) - c\_4^(3) and m^(10) - c\_4^(4). Further branches lead to leaf nodes representing spreading codes c\_16^(1) through c\_16^(16). + +Figure AA.3.4ba: Association of Midambles to Spreading Codes for K=10 pattern 2A + +![Tree diagram showing the association of Midambles to Spreading Codes for K=10 pattern 2B. The root node is m^(4) - c_1^(1), which branches into m^(4) - c_2^(1) and m^(8) - c_2^(2). m^(4) - c_2^(1) branches into m^(4) - c_4^(1) and m^(4) - c_4^(2). m^(8) - c_2^(2) branches into m^(8) - c_4^(3) and m^(8) - c_4^(4). Further branches lead to leaf nodes representing spreading codes c_16^(1) through c_16^(16).](8edfc370769207831f060f44d2281084_img.jpg) + +Diagram illustrating the association of Midambles to Spreading Codes for K=10 pattern 2B. The tree structure shows the hierarchical decomposition of the root node $m^{(4)} - c_1^{(1)}$ into various intermediate nodes and finally into 16 leaf nodes representing spreading codes $c_{16}^{(1)}$ through $c_{16}^{(16)}$ . + +The root node $m^{(4)} - c_1^{(1)}$ branches into $m^{(4)} - c_2^{(1)}$ and $m^{(8)} - c_2^{(2)}$ . + +$m^{(4)} - c_2^{(1)}$ branches into $m^{(4)} - c_4^{(1)}$ and $m^{(4)} - c_4^{(2)}$ . + +$m^{(8)} - c_2^{(2)}$ branches into $m^{(8)} - c_4^{(3)}$ and $m^{(8)} - c_4^{(4)}$ . + +$m^{(4)} - c_4^{(1)}$ branches into $m^{(4)} - c_8^{(1)}$ and $m^{(4)} - c_8^{(2)}$ . + +$m^{(4)} - c_4^{(2)}$ branches into $m^{(4)} - c_8^{(3)}$ and $m^{(4)} - c_8^{(4)}$ . + +$m^{(8)} - c_4^{(3)}$ branches into $m^{(8)} - c_8^{(5)}$ and $m^{(8)} - c_8^{(6)}$ . + +$m^{(8)} - c_4^{(4)}$ branches into $m^{(8)} - c_8^{(7)}$ and $m^{(8)} - c_8^{(8)}$ . + +The leaf nodes are: + +- $m^{(4)} - c_{16}^{(1)}$ , $m^{(4)} - c_{16}^{(2)}$ , $m^{(4)} - c_{16}^{(3)}$ , $m^{(4)} - c_{16}^{(4)}$ +- $m^{(4)} - c_{16}^{(5)}$ , $m^{(4)} - c_{16}^{(6)}$ , $m^{(4)} - c_{16}^{(7)}$ , $m^{(4)} - c_{16}^{(8)}$ +- $m^{(8)} - c_{16}^{(9)}$ , $m^{(8)} - c_{16}^{(10)}$ , $m^{(8)} - c_{16}^{(11)}$ , $m^{(8)} - c_{16}^{(12)}$ +- $m^{(8)} - c_{16}^{(13)}$ , $m^{(8)} - c_{16}^{(14)}$ , $m^{(8)} - c_{16}^{(15)}$ , $m^{(8)} - c_{16}^{(16)}$ + +Tree diagram showing the association of Midambles to Spreading Codes for K=10 pattern 2B. The root node is m^(4) - c\_1^(1), which branches into m^(4) - c\_2^(1) and m^(8) - c\_2^(2). m^(4) - c\_2^(1) branches into m^(4) - c\_4^(1) and m^(4) - c\_4^(2). m^(8) - c\_2^(2) branches into m^(8) - c\_4^(3) and m^(8) - c\_4^(4). Further branches lead to leaf nodes representing spreading codes c\_16^(1) through c\_16^(16). + +Figure AA.3.4bb: Association of Midambles to Spreading Codes for K=10 pattern 2B + +### AA.3.5 Association for K=8 Midambles + +![Tree diagram showing the association of Midambles to Spreading Codes for K=8 pattern 1.](276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg) + +Diagram illustrating the association of Midambles to Spreading Codes for K=8 pattern 1. The hierarchy starts with $m^{(1)} - c_1^{(1)}$ , which branches into $m^{(1)} - c_2^{(1)}$ and $m^{(5)} - c_2^{(2)}$ . + $m^{(1)} - c_2^{(1)}$ branches into $m^{(1)} - c_4^{(1)}$ and $m^{(3)} - c_4^{(2)}$ . + $m^{(5)} - c_2^{(2)}$ branches into $m^{(5)} - c_4^{(3)}$ and $m^{(7)} - c_4^{(4)}$ . + Further branches lead to $m^{(1)} - c_8^{(1)}$ , $m^{(1)} - c_8^{(2)*}$ , $m^{(3)} - c_8^{(3)}$ , $m^{(3)} - c_8^{(4)*}$ , $m^{(5)} - c_8^{(5)}$ , $m^{(5)} - c_8^{(6)*}$ , $m^{(7)} - c_8^{(7)}$ , and $m^{(7)} - c_8^{(8)*}$ . + Each of these leads to two spreading codes at the 16-chip level, for example, $m^{(1)} - c_{16}^{(1)}$ and $m^{(1)} - c_{16}^{(2)*}$ , continuing up to $m^{(7)} - c_{16}^{(16)*}$ . + +Tree diagram showing the association of Midambles to Spreading Codes for K=8 pattern 1. + +Figure AA.3.5a: Association of Midambles to Spreading Codes for K=8 pattern 1 + +![Tree diagram showing the association of Midambles to Spreading Codes for K=8 pattern 1A.](99a0eddf16e836f411661acee6facd17_img.jpg) + +Diagram illustrating the association of Midambles to Spreading Codes for K=8 pattern 1A. The hierarchy starts with $m^{(1)} - c_1^{(1)}$ , which branches into $m^{(1)} - c_2^{(1)}$ and $m^{(5)} - c_2^{(2)}$ . + $m^{(1)} - c_2^{(1)}$ branches into $m^{(1)} - c_4^{(1)}$ and $m^{(1)} - c_4^{(2)*}$ . + $m^{(5)} - c_2^{(2)}$ branches into $m^{(5)} - c_4^{(3)}$ and $m^{(5)} - c_4^{(4)*}$ . + Further branches lead to $m^{(1)} - c_8^{(1)}$ , $m^{(1)} - c_8^{(2)*}$ , $m^{(1)} - c_8^{(3)*}$ , $m^{(1)} - c_8^{(4)*}$ , $m^{(5)} - c_8^{(5)}$ , $m^{(5)} - c_8^{(6)*}$ , $m^{(5)} - c_8^{(7)*}$ , and $m^{(5)} - c_8^{(8)*}$ . + Each of these leads to two spreading codes at the 16-chip level, for example, $m^{(1)} - c_{16}^{(1)}$ and $m^{(1)} - c_{16}^{(2)*}$ , continuing up to $m^{(5)} - c_{16}^{(16)*}$ . + +Tree diagram showing the association of Midambles to Spreading Codes for K=8 pattern 1A. + +Figure AA.3.5aa: Association of Midambles to Spreading Codes for K=8 pattern 1A + +Error: + +115 + +Error: Reference source not + +![Tree diagram showing the association of midambles to spreading codes for K=8 pattern 1B. The root node is m^(3) - c_1^(1), which branches into m^(3) - c_2^(1) and m^(7) - c_2^(2). m^(3) - c_2^(1) branches into m^(3) - c_4^(1) and m^(3) - c_4^(2). m^(7) - c_2^(2) branches into m^(7) - c_4^(3) and m^(7) - c_4^(4). Further branches lead to m^(3) - c_8^(1) through m^(3) - c_8^(4) and m^(7) - c_8^(5) through m^(7) - c_8^(8), which finally lead to 16 spreading codes m^(3) - c_16^(1) through m^(7) - c_16^(16).](eabcb2f8b9acedb194571d5bc734b463_img.jpg) + +``` +graph LR; m3c11["m^(3) - c_1^(1)"] --> m3c21["m^(3) - c_2^(1)"]; m3c11 --> m7c22["m^(7) - c_2^(2)"]; m3c21 --> m3c41["m^(3) - c_4^(1)"]; m3c21 --> m3c42["m^(3) - c_4^(2)"]; m7c22 --> m7c43["m^(7) - c_4^(3)"]; m7c22 --> m7c44["m^(7) - c_4^(4)"]; m3c41 --> m3c81["m^(3) - c_8^(1)"]; m3c41 --> m3c82["m^(3) - c_8^(2)"]; m3c42 --> m3c83["m^(3) - c_8^(3)"]; m3c42 --> m3c84["m^(3) - c_8^(4)"]; m7c43 --> m7c85["m^(7) - c_8^(5)"]; m7c43 --> m7c86["m^(7) - c_8^(6)"]; m7c44 --> m7c87["m^(7) - c_8^(7)"]; m7c44 --> m7c88["m^(7) - c_8^(8)"]; m3c81 --> m3c161["m^(3) - c_16^(1)"]; m3c81 --> m3c162["m^(3) - c_16^(2)*"]; m3c82 --> m3c163["m^(3) - c_16^(3)*"]; m3c82 --> m3c164["m^(3) - c_16^(4)*"]; m3c83 --> m3c165["m^(3) - c_16^(5)*"]; m3c83 --> m3c166["m^(3) - c_16^(6)*"]; m3c84 --> m3c167["m^(3) - c_16^(7)*"]; m3c84 --> m3c168["m^(3) - c_16^(8)*"]; m7c85 --> m7c169["m^(7) - c_16^(9)"]; m7c85 --> m7c1610["m^(7) - c_16^(10)*"]; m7c86 --> m7c1611["m^(7) - c_16^(11)*"]; m7c86 --> m7c1612["m^(7) - c_16^(12)*"]; m7c87 --> m7c1613["m^(7) - c_16^(13)*"]; m7c87 --> m7c1614["m^(7) - c_16^(14)*"]; m7c88 --> m7c1615["m^(7) - c_16^(15)*"]; m7c88 --> m7c1616["m^(7) - c_16^(16)*"]; +``` + +Tree diagram showing the association of midambles to spreading codes for K=8 pattern 1B. The root node is m^(3) - c\_1^(1), which branches into m^(3) - c\_2^(1) and m^(7) - c\_2^(2). m^(3) - c\_2^(1) branches into m^(3) - c\_4^(1) and m^(3) - c\_4^(2). m^(7) - c\_2^(2) branches into m^(7) - c\_4^(3) and m^(7) - c\_4^(4). Further branches lead to m^(3) - c\_8^(1) through m^(3) - c\_8^(4) and m^(7) - c\_8^(5) through m^(7) - c\_8^(8), which finally lead to 16 spreading codes m^(3) - c\_16^(1) through m^(7) - c\_16^(16). + +Figure AA.3.5ab: Association of Midambles to Spreading Codes for K=8 pattern 1B + +![Tree diagram showing the association of midambles to spreading codes for K=8 pattern 2. The root node is m^(2) - c_1^(1), which branches into m^(2) - c_2^(1) and m^(6) - c_2^(2). m^(2) - c_2^(1) branches into m^(2) - c_4^(1) and m^(4) - c_4^(2). m^(6) - c_2^(2) branches into m^(6) - c_4^(3) and m^(8) - c_4^(4). Further branches lead to m^(2) - c_8^(1) through m^(2) - c_8^(2), m^(4) - c_8^(3) through m^(4) - c_8^(4), m^(6) - c_8^(5) through m^(6) - c_8^(6), and m^(8) - c_8^(7) through m^(8) - c_8^(8), which finally lead to 16 spreading codes m^(2) - c_16^(1) through m^(8) - c_16^(16).](ef0faba51289e3a364ba51e5ef4d1a43_img.jpg) + +``` +graph LR; m2c11["m^(2) - c_1^(1)"] --> m2c21["m^(2) - c_2^(1)"]; m2c11 --> m6c22["m^(6) - c_2^(2)"]; m2c21 --> m2c41["m^(2) - c_4^(1)"]; m2c21 --> m4c42["m^(4) - c_4^(2)"]; m6c22 --> m6c43["m^(6) - c_4^(3)"]; m6c22 --> m8c44["m^(8) - c_4^(4)"]; m2c41 --> m2c81["m^(2) - c_8^(1)"]; m2c41 --> m2c82["m^(2) - c_8^(2)"]; m4c42 --> m4c83["m^(4) - c_8^(3)"]; m4c42 --> m4c84["m^(4) - c_8^(4)"]; m6c43 --> m6c85["m^(6) - c_8^(5)"]; m6c43 --> m6c86["m^(6) - c_8^(6)"]; m8c44 --> m8c87["m^(8) - c_8^(7)"]; m8c44 --> m8c88["m^(8) - c_8^(8)"]; m2c81 --> m2c161["m^(2) - c_16^(1)"]; m2c81 --> m2c162["m^(2) - c_16^(2)*"]; m2c82 --> m2c163["m^(2) - c_16^(3)*"]; m2c82 --> m2c164["m^(2) - c_16^(4)*"]; m4c83 --> m4c165["m^(4) - c_16^(5)"]; m4c83 --> m4c166["m^(4) - c_16^(6)*"]; m4c84 --> m4c167["m^(4) - c_16^(7)*"]; m4c84 --> m4c168["m^(4) - c_16^(8)*"]; m6c85 --> m6c169["m^(6) - c_16^(9)"]; m6c85 --> m6c1610["m^(6) - c_16^(10)*"]; m6c86 --> m6c1611["m^(6) - c_16^(11)*"]; m6c86 --> m6c1612["m^(6) - c_16^(12)*"]; m8c87 --> m8c1613["m^(8) - c_16^(13)"]; m8c87 --> m8c1614["m^(8) - c_16^(14)*"]; m8c88 --> m8c1615["m^(8) - c_16^(15)*"]; m8c88 --> m8c1616["m^(8) - c_16^(16)*"]; +``` + +Tree diagram showing the association of midambles to spreading codes for K=8 pattern 2. The root node is m^(2) - c\_1^(1), which branches into m^(2) - c\_2^(1) and m^(6) - c\_2^(2). m^(2) - c\_2^(1) branches into m^(2) - c\_4^(1) and m^(4) - c\_4^(2). m^(6) - c\_2^(2) branches into m^(6) - c\_4^(3) and m^(8) - c\_4^(4). Further branches lead to m^(2) - c\_8^(1) through m^(2) - c\_8^(2), m^(4) - c\_8^(3) through m^(4) - c\_8^(4), m^(6) - c\_8^(5) through m^(6) - c\_8^(6), and m^(8) - c\_8^(7) through m^(8) - c\_8^(8), which finally lead to 16 spreading codes m^(2) - c\_16^(1) through m^(8) - c\_16^(16). + +Figure AA.3.5b: Association of Midambles to Spreading Codes for K=8 pattern 2 + +![Tree diagram showing the association of Midambles to Spreading Codes for K=8 pattern 2A. The root node is m^{(2)} - c_1^{(1)}, which branches into m^{(2)} - c_2^{(1)} and m^{(6)} - c_2^{(2)}. m^{(2)} - c_2^{(1)} branches into m^{(2)} - c_4^{(1)} and m^{(2)} - c_4^{(2)*}. m^{(6)} - c_2^{(2)} branches into m^{(6)} - c_4^{(3)} and m^{(6)} - c_4^{(4)*}. Further branches lead to m^{(2)} - c_8^{(1)}, m^{(2)} - c_8^{(2)*}, m^{(2)} - c_8^{(3)*}, m^{(2)} - c_8^{(4)*}, m^{(6)} - c_8^{(5)}, m^{(6)} - c_8^{(6)*}, m^{(6)} - c_8^{(7)*}, and m^{(6)} - c_8^{(8)*}. Each of these nodes further branches into two spreading codes, resulting in 16 leaf nodes: m^{(2)} - c_{16}^{(1)}, m^{(2)} - c_{16}^{(2)*}, m^{(2)} - c_{16}^{(3)*}, m^{(2)} - c_{16}^{(4)*}, m^{(2)} - c_{16}^{(5)*}, m^{(2)} - c_{16}^{(6)*}, m^{(2)} - c_{16}^{(7)*}, m^{(2)} - c_{16}^{(8)*}, m^{(6)} - c_{16}^{(9)}, m^{(6)} - c_{16}^{(10)*}, m^{(6)} - c_{16}^{(11)*}, m^{(6)} - c_{16}^{(12)*}, m^{(6)} - c_{16}^{(13)*}, m^{(6)} - c_{16}^{(14)*}, m^{(6)} - c_{16}^{(15)*}, and m^{(6)} - c_{16}^{(16)*}.](2b00743506f6a3bbd17af764162dc76d_img.jpg) + +Tree diagram showing the association of Midambles to Spreading Codes for K=8 pattern 2A. The root node is m^{(2)} - c\_1^{(1)}, which branches into m^{(2)} - c\_2^{(1)} and m^{(6)} - c\_2^{(2)}. m^{(2)} - c\_2^{(1)} branches into m^{(2)} - c\_4^{(1)} and m^{(2)} - c\_4^{(2)\*}. m^{(6)} - c\_2^{(2)} branches into m^{(6)} - c\_4^{(3)} and m^{(6)} - c\_4^{(4)\*}. Further branches lead to m^{(2)} - c\_8^{(1)}, m^{(2)} - c\_8^{(2)\*}, m^{(2)} - c\_8^{(3)\*}, m^{(2)} - c\_8^{(4)\*}, m^{(6)} - c\_8^{(5)}, m^{(6)} - c\_8^{(6)\*}, m^{(6)} - c\_8^{(7)\*}, and m^{(6)} - c\_8^{(8)\*}. Each of these nodes further branches into two spreading codes, resulting in 16 leaf nodes: m^{(2)} - c\_{16}^{(1)}, m^{(2)} - c\_{16}^{(2)\*}, m^{(2)} - c\_{16}^{(3)\*}, m^{(2)} - c\_{16}^{(4)\*}, m^{(2)} - c\_{16}^{(5)\*}, m^{(2)} - c\_{16}^{(6)\*}, m^{(2)} - c\_{16}^{(7)\*}, m^{(2)} - c\_{16}^{(8)\*}, m^{(6)} - c\_{16}^{(9)}, m^{(6)} - c\_{16}^{(10)\*}, m^{(6)} - c\_{16}^{(11)\*}, m^{(6)} - c\_{16}^{(12)\*}, m^{(6)} - c\_{16}^{(13)\*}, m^{(6)} - c\_{16}^{(14)\*}, m^{(6)} - c\_{16}^{(15)\*}, and m^{(6)} - c\_{16}^{(16)\*}. + +Figure AA.3.5ba: Association of Midambles to Spreading Codes for K=8 pattern 2A + +![Tree diagram showing the association of Midambles to Spreading Codes for K=8 pattern 2B. The root node is m^{(4)} - c_1^{(1)}, which branches into m^{(4)} - c_2^{(1)} and m^{(8)} - c_2^{(2)}. m^{(4)} - c_2^{(1)} branches into m^{(4)} - c_4^{(1)} and m^{(4)} - c_4^{(2)*}. m^{(8)} - c_2^{(2)} branches into m^{(8)} - c_4^{(3)} and m^{(8)} - c_4^{(4)*}. Further branches lead to m^{(4)} - c_8^{(1)}, m^{(4)} - c_8^{(2)*}, m^{(4)} - c_8^{(3)*}, m^{(4)} - c_8^{(4)*}, m^{(8)} - c_8^{(5)}, m^{(8)} - c_8^{(6)*}, m^{(8)} - c_8^{(7)*}, and m^{(8)} - c_8^{(8)*}. Each of these nodes further branches into two spreading codes, resulting in 16 leaf nodes: m^{(4)} - c_{16}^{(1)}, m^{(4)} - c_{16}^{(2)*}, m^{(4)} - c_{16}^{(3)*}, m^{(4)} - c_{16}^{(4)*}, m^{(4)} - c_{16}^{(5)*}, m^{(4)} - c_{16}^{(6)*}, m^{(4)} - c_{16}^{(7)*}, m^{(4)} - c_{16}^{(8)*}, m^{(8)} - c_{16}^{(9)}, m^{(8)} - c_{16}^{(10)*}, m^{(8)} - c_{16}^{(11)*}, m^{(8)} - c_{16}^{(12)*}, m^{(8)} - c_{16}^{(13)*}, m^{(8)} - c_{16}^{(14)*}, m^{(8)} - c_{16}^{(15)*}, and m^{(8)} - c_{16}^{(16)*}.](0bbbad069459da54c1cdef84c90b316a_img.jpg) + +Tree diagram showing the association of Midambles to Spreading Codes for K=8 pattern 2B. The root node is m^{(4)} - c\_1^{(1)}, which branches into m^{(4)} - c\_2^{(1)} and m^{(8)} - c\_2^{(2)}. m^{(4)} - c\_2^{(1)} branches into m^{(4)} - c\_4^{(1)} and m^{(4)} - c\_4^{(2)\*}. m^{(8)} - c\_2^{(2)} branches into m^{(8)} - c\_4^{(3)} and m^{(8)} - c\_4^{(4)\*}. Further branches lead to m^{(4)} - c\_8^{(1)}, m^{(4)} - c\_8^{(2)\*}, m^{(4)} - c\_8^{(3)\*}, m^{(4)} - c\_8^{(4)\*}, m^{(8)} - c\_8^{(5)}, m^{(8)} - c\_8^{(6)\*}, m^{(8)} - c\_8^{(7)\*}, and m^{(8)} - c\_8^{(8)\*}. Each of these nodes further branches into two spreading codes, resulting in 16 leaf nodes: m^{(4)} - c\_{16}^{(1)}, m^{(4)} - c\_{16}^{(2)\*}, m^{(4)} - c\_{16}^{(3)\*}, m^{(4)} - c\_{16}^{(4)\*}, m^{(4)} - c\_{16}^{(5)\*}, m^{(4)} - c\_{16}^{(6)\*}, m^{(4)} - c\_{16}^{(7)\*}, m^{(4)} - c\_{16}^{(8)\*}, m^{(8)} - c\_{16}^{(9)}, m^{(8)} - c\_{16}^{(10)\*}, m^{(8)} - c\_{16}^{(11)\*}, m^{(8)} - c\_{16}^{(12)\*}, m^{(8)} - c\_{16}^{(13)\*}, m^{(8)} - c\_{16}^{(14)\*}, m^{(8)} - c\_{16}^{(15)\*}, and m^{(8)} - c\_{16}^{(16)\*}. + +Figure AA.3.5bb: Association of Midambles to Spreading Codes for K=8 pattern 2B + +### AA.3.6 Association for K=6 Midambles + +![Hierarchical tree diagram for K=6 pattern 1. Root: m^{(1)} - c_1^{(1)}. Level 2: m^{(1)} - c_2^{(1)}, m^{(5)} - c_2^{(2)}. Level 3: m^{(1)} - c_4^{(1)}, m^{(3)} - c_4^{(2)}, m^{(5)} - c_4^{(3)}, m^{(5)} - c_4^{(4)*}. Level 4: m^{(1)} - c_8^{(1)}, m^{(1)} - c_8^{(2)*}, m^{(3)} - c_8^{(3)}, m^{(3)} - c_8^{(4)*}, m^{(5)} - c_8^{(5)}, m^{(5)} - c_8^{(6)*}, m^{(5)} - c_8^{(7)*}, m^{(5)} - c_8^{(8)*}. Level 5: 16 leaf nodes from m^{(1)} - c_{16}^{(1)} to m^{(5)} - c_{16}^{(16)*}.](6348f4fc8b3848158fcfbe85e26a731d_img.jpg) + +Tree structure for Figure AA.3.6a: + +- $m^{(1)} - c_1^{(1)}$ + - $m^{(1)} - c_2^{(1)}$ + - $m^{(1)} - c_4^{(1)}$ + - $m^{(1)} - c_8^{(1)} → m^{(1)} - c_{16}^{(1)}, m^{(1)} - c_{16}^{(2)*}$ + - $m^{(1)} - c_8^{(2)*} → m^{(1)} - c_{16}^{(3)*}, m^{(1)} - c_{16}^{(4)*}$ + - $m^{(3)} - c_4^{(2)}$ + - $m^{(3)} - c_8^{(3)} → m^{(3)} - c_{16}^{(5)}, m^{(3)} - c_{16}^{(6)*}$ + - $m^{(3)} - c_8^{(4)*} → m^{(3)} - c_{16}^{(7)*}, m^{(3)} - c_{16}^{(8)*}$ + - $m^{(5)} - c_2^{(2)}$ + - $m^{(5)} - c_4^{(3)}$ + - $m^{(5)} - c_8^{(5)} → m^{(5)} - c_{16}^{(9)}, m^{(5)} - c_{16}^{(10)*}$ + - $m^{(5)} - c_8^{(6)*} → m^{(5)} - c_{16}^{(11)*}, m^{(5)} - c_{16}^{(12)*}$ + - $m^{(5)} - c_4^{(4)*}$ + - $m^{(5)} - c_8^{(7)*} → m^{(5)} - c_{16}^{(13)*}, m^{(5)} - c_{16}^{(14)*}$ + - $m^{(5)} - c_8^{(8)*} → m^{(5)} - c_{16}^{(15)*}, m^{(5)} - c_{16}^{(16)*}$ + +Hierarchical tree diagram for K=6 pattern 1. Root: m^{(1)} - c\_1^{(1)}. Level 2: m^{(1)} - c\_2^{(1)}, m^{(5)} - c\_2^{(2)}. Level 3: m^{(1)} - c\_4^{(1)}, m^{(3)} - c\_4^{(2)}, m^{(5)} - c\_4^{(3)}, m^{(5)} - c\_4^{(4)\*}. Level 4: m^{(1)} - c\_8^{(1)}, m^{(1)} - c\_8^{(2)\*}, m^{(3)} - c\_8^{(3)}, m^{(3)} - c\_8^{(4)\*}, m^{(5)} - c\_8^{(5)}, m^{(5)} - c\_8^{(6)\*}, m^{(5)} - c\_8^{(7)\*}, m^{(5)} - c\_8^{(8)\*}. Level 5: 16 leaf nodes from m^{(1)} - c\_{16}^{(1)} to m^{(5)} - c\_{16}^{(16)\*}. + +Figure AA.3.6a: Association of Midambles to Spreading Codes for K=6 pattern 1 + +![Hierarchical tree diagram for K=6 pattern 1A. Root: m^{(1)} - c_1^{(1)}. Level 2: m^{(1)} - c_2^{(1)}, m^{(5)} - c_2^{(2)}. Level 3: m^{(1)} - c_4^{(1)}, m^{(1)} - c_4^{(2)*}, m^{(5)} - c_4^{(3)}, m^{(5)} - c_4^{(4)*}. Level 4: m^{(1)} - c_8^{(1)}, m^{(1)} - c_8^{(2)*}, m^{(1)} - c_8^{(3)*}, m^{(1)} - c_8^{(4)*}, m^{(5)} - c_8^{(5)}, m^{(5)} - c_8^{(6)*}, m^{(5)} - c_8^{(7)*}, m^{(5)} - c_8^{(8)*}. Level 5: 16 leaf nodes from m^{(1)} - c_{16}^{(1)} to m^{(5)} - c_{16}^{(16)*}.](d4a9a1e5b2d8b51e6bf1abacd2421c83_img.jpg) + +Tree structure for Figure AA.3.6aa: + +- $m^{(1)} - c_1^{(1)}$ + - $m^{(1)} - c_2^{(1)}$ + - $m^{(1)} - c_4^{(1)}$ + - $m^{(1)} - c_8^{(1)} → m^{(1)} - c_{16}^{(1)}, m^{(1)} - c_{16}^{(2)*}$ + - $m^{(1)} - c_8^{(2)*} → m^{(1)} - c_{16}^{(3)*}, m^{(1)} - c_{16}^{(4)*}$ + - $m^{(1)} - c_4^{(2)*}$ + - $m^{(1)} - c_8^{(3)*} → m^{(1)} - c_{16}^{(5)*}, m^{(1)} - c_{16}^{(6)*}$ + - $m^{(1)} - c_8^{(4)*} → m^{(1)} - c_{16}^{(7)*}, m^{(1)} - c_{16}^{(8)*}$ + - $m^{(5)} - c_2^{(2)}$ + - $m^{(5)} - c_4^{(3)}$ + - $m^{(5)} - c_8^{(5)} → m^{(5)} - c_{16}^{(9)}, m^{(5)} - c_{16}^{(10)*}$ + - $m^{(5)} - c_8^{(6)*} → m^{(5)} - c_{16}^{(11)*}, m^{(5)} - c_{16}^{(12)*}$ + - $m^{(5)} - c_4^{(4)*}$ + - $m^{(5)} - c_8^{(7)*} → m^{(5)} - c_{16}^{(13)*}, m^{(5)} - c_{16}^{(14)*}$ + - $m^{(5)} - c_8^{(8)*} → m^{(5)} - c_{16}^{(15)*}, m^{(5)} - c_{16}^{(16)*}$ + +Hierarchical tree diagram for K=6 pattern 1A. Root: m^{(1)} - c\_1^{(1)}. Level 2: m^{(1)} - c\_2^{(1)}, m^{(5)} - c\_2^{(2)}. Level 3: m^{(1)} - c\_4^{(1)}, m^{(1)} - c\_4^{(2)\*}, m^{(5)} - c\_4^{(3)}, m^{(5)} - c\_4^{(4)\*}. Level 4: m^{(1)} - c\_8^{(1)}, m^{(1)} - c\_8^{(2)\*}, m^{(1)} - c\_8^{(3)\*}, m^{(1)} - c\_8^{(4)\*}, m^{(5)} - c\_8^{(5)}, m^{(5)} - c\_8^{(6)\*}, m^{(5)} - c\_8^{(7)\*}, m^{(5)} - c\_8^{(8)\*}. Level 5: 16 leaf nodes from m^{(1)} - c\_{16}^{(1)} to m^{(5)} - c\_{16}^{(16)\*}. + +Figure AA.3.6aa: Association of Midambles to Spreading Codes for K=6 pattern 1A + +Error: + +118 + +Error: Reference source not + +![A hierarchical tree diagram showing the association of midambles to spreading codes for K=6 pattern 1B. The root node is m^(3) - c_1^(1), which branches into m^(3) - c_2^(1) and m^(3) - c_2^(2). m^(3) - c_2^(1) branches into m^(3) - c_4^(1) and m^(3) - c_4^(2). m^(3) - c_4^(1) branches into m^(3) - c_8^(1) and m^(3) - c_8^(2). m^(3) - c_4^(2) branches into m^(3) - c_8^(3) and m^(3) - c_8^(4). m^(3) - c_2^(2) branches into m^(3) - c_4^(3) and m^(3) - c_4^(4). m^(3) - c_4^(3) branches into m^(3) - c_8^(5) and m^(3) - c_8^(6). m^(3) - c_4^(4) branches into m^(3) - c_8^(7) and m^(3) - c_8^(8). Each m^(3) - c_8^(i) node branches into two leaf nodes: m^(3) - c_16^(i) and m^(3) - c_16^(i)*. The leaf nodes are numbered 1 through 16.](ef45b00396c293be0b18d32b97118bf4_img.jpg) + +A hierarchical tree diagram showing the association of midambles to spreading codes for K=6 pattern 1B. The root node is m^(3) - c\_1^(1), which branches into m^(3) - c\_2^(1) and m^(3) - c\_2^(2). m^(3) - c\_2^(1) branches into m^(3) - c\_4^(1) and m^(3) - c\_4^(2). m^(3) - c\_4^(1) branches into m^(3) - c\_8^(1) and m^(3) - c\_8^(2). m^(3) - c\_4^(2) branches into m^(3) - c\_8^(3) and m^(3) - c\_8^(4). m^(3) - c\_2^(2) branches into m^(3) - c\_4^(3) and m^(3) - c\_4^(4). m^(3) - c\_4^(3) branches into m^(3) - c\_8^(5) and m^(3) - c\_8^(6). m^(3) - c\_4^(4) branches into m^(3) - c\_8^(7) and m^(3) - c\_8^(8). Each m^(3) - c\_8^(i) node branches into two leaf nodes: m^(3) - c\_16^(i) and m^(3) - c\_16^(i)\*. The leaf nodes are numbered 1 through 16. + +Figure AA.3.6ab: Association of Midambles to Spreading Codes for K=6 pattern 1B + +![A hierarchical tree diagram showing the association of midambles to spreading codes for K=6 pattern 2. The root node is m^(2) - c_1^(1), which branches into m^(2) - c_2^(1) and m^(6) - c_2^(2). m^(2) - c_2^(1) branches into m^(2) - c_4^(1) and m^(4) - c_4^(2). m^(2) - c_4^(1) branches into m^(2) - c_8^(1) and m^(2) - c_8^(2). m^(4) - c_4^(2) branches into m^(4) - c_8^(3) and m^(4) - c_8^(4). m^(6) - c_2^(2) branches into m^(6) - c_4^(3) and m^(6) - c_4^(4). m^(6) - c_4^(3) branches into m^(6) - c_8^(5) and m^(6) - c_8^(6). m^(6) - c_4^(4) branches into m^(6) - c_8^(7) and m^(6) - c_8^(8). Each m^(i) - c_8^(i) node branches into two leaf nodes: m^(i) - c_16^(i) and m^(i) - c_16^(i)*. The leaf nodes are numbered 1 through 16.](aa39f51ba214496042ee3e2ce4ecee80_img.jpg) + +A hierarchical tree diagram showing the association of midambles to spreading codes for K=6 pattern 2. The root node is m^(2) - c\_1^(1), which branches into m^(2) - c\_2^(1) and m^(6) - c\_2^(2). m^(2) - c\_2^(1) branches into m^(2) - c\_4^(1) and m^(4) - c\_4^(2). m^(2) - c\_4^(1) branches into m^(2) - c\_8^(1) and m^(2) - c\_8^(2). m^(4) - c\_4^(2) branches into m^(4) - c\_8^(3) and m^(4) - c\_8^(4). m^(6) - c\_2^(2) branches into m^(6) - c\_4^(3) and m^(6) - c\_4^(4). m^(6) - c\_4^(3) branches into m^(6) - c\_8^(5) and m^(6) - c\_8^(6). m^(6) - c\_4^(4) branches into m^(6) - c\_8^(7) and m^(6) - c\_8^(8). Each m^(i) - c\_8^(i) node branches into two leaf nodes: m^(i) - c\_16^(i) and m^(i) - c\_16^(i)\*. The leaf nodes are numbered 1 through 16. + +Figure AA.3.6b: Association of Midambles to Spreading Codes for K=6 pattern 2 + +![Tree diagram showing the association of midambles to spreading codes for K=6 pattern 2A. The root node is m^{(2)} - c_1^{(1)}, which branches into m^{(2)} - c_2^{(1)} and m^{(6)} - c_2^{(2)}. m^{(2)} - c_2^{(1)} branches into m^{(2)} - c_4^{(1)} and m^{(2)} - c_4^{(2)*}. m^{(6)} - c_2^{(2)} branches into m^{(6)} - c_4^{(3)} and m^{(6)} - c_4^{(4)*}. Further branches lead to m^{(2)} - c_8^{(1)}, m^{(2)} - c_8^{(2)*}, m^{(2)} - c_8^{(3)*}, m^{(2)} - c_8^{(4)*}, m^{(6)} - c_8^{(5)*}, m^{(6)} - c_8^{(6)*}, m^{(6)} - c_8^{(7)*}, and m^{(6)} - c_8^{(8)*}. Each of these nodes further branches into two spreading codes, resulting in 16 leaf nodes labeled m^{(2)} - c_{16}^{(1)} through m^{(6)} - c_{16}^{(16)*}.](9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg) + +``` + +graph LR; + m2c1["m^{(2)} - c_1^{(1)}"] --> m2c2_1["m^{(2)} - c_2^{(1)}"]; + m2c1 --> m6c2_2["m^{(6)} - c_2^{(2)}"]; + m2c2_1 --> m2c4_1["m^{(2)} - c_4^{(1)}"]; + m2c2_1 --> m2c4_2["m^{(2)} - c_4^{(2)*}"]; + m6c2_2 --> m6c4_3["m^{(6)} - c_4^{(3)}"]; + m6c2_2 --> m6c4_4["m^{(6)} - c_4^{(4)*}"]; + m2c4_1 --> m2c8_1["m^{(2)} - c_8^{(1)}"]; + m2c4_1 --> m2c8_2["m^{(2)} - c_8^{(2)*}"]; + m2c4_2 --> m2c8_3["m^{(2)} - c_8^{(3)*}"]; + m2c4_2 --> m2c8_4["m^{(2)} - c_8^{(4)*}"]; + m6c4_3 --> m6c8_5["m^{(6)} - c_8^{(5)*}"]; + m6c4_3 --> m6c8_6["m^{(6)} - c_8^{(6)*}"]; + m6c4_4 --> m6c8_7["m^{(6)} - c_8^{(7)*}"]; + m6c4_4 --> m6c8_8["m^{(6)} - c_8^{(8)*}"]; + m2c8_1 --> m2c16_1["m^{(2)} - c_{16}^{(1)}"]; + m2c8_1 --> m2c16_2["m^{(2)} - c_{16}^{(2)*}"]; + m2c8_2 --> m2c16_3["m^{(2)} - c_{16}^{(3)*}"]; + m2c8_2 --> m2c16_4["m^{(2)} - c_{16}^{(4)*}"]; + m2c8_3 --> m2c16_5["m^{(2)} - c_{16}^{(5)*}"]; + m2c8_3 --> m2c16_6["m^{(2)} - c_{16}^{(6)*}"]; + m2c8_4 --> m2c16_7["m^{(2)} - c_{16}^{(7)*}"]; + m2c8_4 --> m2c16_8["m^{(2)} - c_{16}^{(8)*}"]; + m6c8_5 --> m6c16_9["m^{(6)} - c_{16}^{(9)*}"]; + m6c8_5 --> m6c16_10["m^{(6)} - c_{16}^{(10)*}"]; + m6c8_6 --> m6c16_11["m^{(6)} - c_{16}^{(11)*}"]; + m6c8_6 --> m6c16_12["m^{(6)} - c_{16}^{(12)*}"]; + m6c8_7 --> m6c16_13["m^{(6)} - c_{16}^{(13)*}"]; + m6c8_7 --> m6c16_14["m^{(6)} - c_{16}^{(14)*}"]; + m6c8_8 --> m6c16_15["m^{(6)} - c_{16}^{(15)*}"]; + m6c8_8 --> m6c16_16["m^{(6)} - c_{16}^{(16)*}"]; + +``` + +Tree diagram showing the association of midambles to spreading codes for K=6 pattern 2A. The root node is m^{(2)} - c\_1^{(1)}, which branches into m^{(2)} - c\_2^{(1)} and m^{(6)} - c\_2^{(2)}. m^{(2)} - c\_2^{(1)} branches into m^{(2)} - c\_4^{(1)} and m^{(2)} - c\_4^{(2)\*}. m^{(6)} - c\_2^{(2)} branches into m^{(6)} - c\_4^{(3)} and m^{(6)} - c\_4^{(4)\*}. Further branches lead to m^{(2)} - c\_8^{(1)}, m^{(2)} - c\_8^{(2)\*}, m^{(2)} - c\_8^{(3)\*}, m^{(2)} - c\_8^{(4)\*}, m^{(6)} - c\_8^{(5)\*}, m^{(6)} - c\_8^{(6)\*}, m^{(6)} - c\_8^{(7)\*}, and m^{(6)} - c\_8^{(8)\*}. Each of these nodes further branches into two spreading codes, resulting in 16 leaf nodes labeled m^{(2)} - c\_{16}^{(1)} through m^{(6)} - c\_{16}^{(16)\*}. + +Figure AA.3.6ba: Association of Midambles to Spreading Codes for K=6 pattern 2A + +![Tree diagram showing the association of midambles to spreading codes for K=6 pattern 2B. The root node is m^{(4)} - c_1^{(1)}, which branches into m^{(4)} - c_2^{(1)} and m^{(4)} - c_2^{(2)*}. m^{(4)} - c_2^{(1)} branches into m^{(4)} - c_4^{(1)} and m^{(4)} - c_4^{(2)*}. m^{(4)} - c_2^{(2)*} branches into m^{(4)} - c_4^{(3)} and m^{(4)} - c_4^{(4)*}. Further branches lead to m^{(4)} - c_8^{(1)}, m^{(4)} - c_8^{(2)*}, m^{(4)} - c_8^{(3)*}, m^{(4)} - c_8^{(4)*}, m^{(4)} - c_8^{(5)*}, m^{(4)} - c_8^{(6)*}, m^{(4)} - c_8^{(7)*}, and m^{(4)} - c_8^{(8)*}. Each of these nodes further branches into two spreading codes, resulting in 16 leaf nodes labeled m^{(4)} - c_{16}^{(1)} through m^{(4)} - c_{16}^{(16)*}.](67a1dd734d3de6e31754caf85d6fe77f_img.jpg) + +``` + +graph LR; + m4c1["m^{(4)} - c_1^{(1)}"] --> m4c2_1["m^{(4)} - c_2^{(1)}"]; + m4c1 --> m4c2_2["m^{(4)} - c_2^{(2)*}"]; + m4c2_1 --> m4c4_1["m^{(4)} - c_4^{(1)}"]; + m4c2_1 --> m4c4_2["m^{(4)} - c_4^{(2)*}"]; + m4c2_2 --> m4c4_3["m^{(4)} - c_4^{(3)*}"]; + m4c2_2 --> m4c4_4["m^{(4)} - c_4^{(4)*}"]; + m4c4_1 --> m4c8_1["m^{(4)} - c_8^{(1)}"]; + m4c4_1 --> m4c8_2["m^{(4)} - c_8^{(2)*}"]; + m4c4_2 --> m4c8_3["m^{(4)} - c_8^{(3)*}"]; + m4c4_2 --> m4c8_4["m^{(4)} - c_8^{(4)*}"]; + m4c4_3 --> m4c8_5["m^{(4)} - c_8^{(5)*}"]; + m4c4_3 --> m4c8_6["m^{(4)} - c_8^{(6)*}"]; + m4c4_4 --> m4c8_7["m^{(4)} - c_8^{(7)*}"]; + m4c4_4 --> m4c8_8["m^{(4)} - c_8^{(8)*}"]; + m4c8_1 --> m4c16_1["m^{(4)} - c_{16}^{(1)}"]; + m4c8_1 --> m4c16_2["m^{(4)} - c_{16}^{(2)*}"]; + m4c8_2 --> m4c16_3["m^{(4)} - c_{16}^{(3)*}"]; + m4c8_2 --> m4c16_4["m^{(4)} - c_{16}^{(4)*}"]; + m4c8_3 --> m4c16_5["m^{(4)} - c_{16}^{(5)*}"]; + m4c8_3 --> m4c16_6["m^{(4)} - c_{16}^{(6)*}"]; + m4c8_4 --> m4c16_7["m^{(4)} - c_{16}^{(7)*}"]; + m4c8_4 --> m4c16_8["m^{(4)} - c_{16}^{(8)*}"]; + m4c8_5 --> m4c16_9["m^{(4)} - c_{16}^{(9)*}"]; + m4c8_5 --> m4c16_10["m^{(4)} - c_{16}^{(10)*}"]; + m4c8_6 --> m4c16_11["m^{(4)} - c_{16}^{(11)*}"]; + m4c8_6 --> m4c16_12["m^{(4)} - c_{16}^{(12)*}"]; + m4c8_7 --> m4c16_13["m^{(4)} - c_{16}^{(13)*}"]; + m4c8_7 --> m4c16_14["m^{(4)} - c_{16}^{(14)*}"]; + m4c8_8 --> m4c16_15["m^{(4)} - c_{16}^{(15)*}"]; + m4c8_8 --> m4c16_16["m^{(4)} - c_{16}^{(16)*}"]; + +``` + +Tree diagram showing the association of midambles to spreading codes for K=6 pattern 2B. The root node is m^{(4)} - c\_1^{(1)}, which branches into m^{(4)} - c\_2^{(1)} and m^{(4)} - c\_2^{(2)\*}. m^{(4)} - c\_2^{(1)} branches into m^{(4)} - c\_4^{(1)} and m^{(4)} - c\_4^{(2)\*}. m^{(4)} - c\_2^{(2)\*} branches into m^{(4)} - c\_4^{(3)} and m^{(4)} - c\_4^{(4)\*}. Further branches lead to m^{(4)} - c\_8^{(1)}, m^{(4)} - c\_8^{(2)\*}, m^{(4)} - c\_8^{(3)\*}, m^{(4)} - c\_8^{(4)\*}, m^{(4)} - c\_8^{(5)\*}, m^{(4)} - c\_8^{(6)\*}, m^{(4)} - c\_8^{(7)\*}, and m^{(4)} - c\_8^{(8)\*}. Each of these nodes further branches into two spreading codes, resulting in 16 leaf nodes labeled m^{(4)} - c\_{16}^{(1)} through m^{(4)} - c\_{16}^{(16)\*}. + +Figure AA.3.6bb: Association of Midambles to Spreading Codes for K=6 pattern 2B + +### AA.3.7 Association for K=4 Midambles + +![A hierarchical tree diagram showing the association of midambles to spreading codes for K=4 pattern 1. The root node is m^{(1)} - c_1^{(1)}, which branches into m^{(1)} - c_2^{(1)} and m^{(3)} - c_2^{(2)}. m^{(1)} - c_2^{(1)} branches into m^{(1)} - c_4^{(1)} and m^{(1)} - c_4^{(2)}. m^{(3)} - c_2^{(2)} branches into m^{(3)} - c_4^{(3)} and m^{(3)} - c_4^{(4)}. Further branches lead to m^{(1)} - c_8^{(1)}, m^{(1)} - c_8^{(2)}, m^{(1)} - c_8^{(3)}, m^{(1)} - c_8^{(4)}, m^{(3)} - c_8^{(5)}, m^{(3)} - c_8^{(6)}, m^{(3)} - c_8^{(7)}, and m^{(3)} - c_8^{(8)}. Each of these nodes finally branches into two leaf nodes representing spreading codes, such as m^{(1)} - c_{16}^{(1)}, m^{(1)} - c_{16}^{(2)*}, etc.](b9d5785720b6edd0917019f211469dde_img.jpg) + +A hierarchical tree diagram showing the association of midambles to spreading codes for K=4 pattern 1. The root node is m^{(1)} - c\_1^{(1)}, which branches into m^{(1)} - c\_2^{(1)} and m^{(3)} - c\_2^{(2)}. m^{(1)} - c\_2^{(1)} branches into m^{(1)} - c\_4^{(1)} and m^{(1)} - c\_4^{(2)}. m^{(3)} - c\_2^{(2)} branches into m^{(3)} - c\_4^{(3)} and m^{(3)} - c\_4^{(4)}. Further branches lead to m^{(1)} - c\_8^{(1)}, m^{(1)} - c\_8^{(2)}, m^{(1)} - c\_8^{(3)}, m^{(1)} - c\_8^{(4)}, m^{(3)} - c\_8^{(5)}, m^{(3)} - c\_8^{(6)}, m^{(3)} - c\_8^{(7)}, and m^{(3)} - c\_8^{(8)}. Each of these nodes finally branches into two leaf nodes representing spreading codes, such as m^{(1)} - c\_{16}^{(1)}, m^{(1)} - c\_{16}^{(2)\*}, etc. + +Figure AA.3.7a: Association of Midambles to Spreading Codes for K=4 pattern 1 + +![A hierarchical tree diagram similar to Figure AA.3.7a, but with a different branching structure for the midambles. The root node is m^{(1)} - c_1^{(1)}, which branches into m^{(1)} - c_2^{(1)} and m^{(1)} - c_2^{(2)}. m^{(1)} - c_2^{(1)} branches into m^{(1)} - c_4^{(1)} and m^{(1)} - c_4^{(2)}. m^{(1)} - c_2^{(2)} branches into m^{(1)} - c_4^{(3)} and m^{(1)} - c_4^{(4)}. Further branches lead to m^{(1)} - c_8^{(1)}, m^{(1)} - c_8^{(2)}, m^{(1)} - c_8^{(3)}, m^{(1)} - c_8^{(4)}, m^{(1)} - c_8^{(5)}, m^{(1)} - c_8^{(6)}, m^{(1)} - c_8^{(7)}, and m^{(1)} - c_8^{(8)}. Each of these nodes finally branches into two leaf nodes representing spreading codes, such as m^{(1)} - c_{16}^{(1)}, m^{(1)} - c_{16}^{(2)*}, etc.](66f134956ab8cc4e2a57345df38dc091_img.jpg) + +A hierarchical tree diagram similar to Figure AA.3.7a, but with a different branching structure for the midambles. The root node is m^{(1)} - c\_1^{(1)}, which branches into m^{(1)} - c\_2^{(1)} and m^{(1)} - c\_2^{(2)}. m^{(1)} - c\_2^{(1)} branches into m^{(1)} - c\_4^{(1)} and m^{(1)} - c\_4^{(2)}. m^{(1)} - c\_2^{(2)} branches into m^{(1)} - c\_4^{(3)} and m^{(1)} - c\_4^{(4)}. Further branches lead to m^{(1)} - c\_8^{(1)}, m^{(1)} - c\_8^{(2)}, m^{(1)} - c\_8^{(3)}, m^{(1)} - c\_8^{(4)}, m^{(1)} - c\_8^{(5)}, m^{(1)} - c\_8^{(6)}, m^{(1)} - c\_8^{(7)}, and m^{(1)} - c\_8^{(8)}. Each of these nodes finally branches into two leaf nodes representing spreading codes, such as m^{(1)} - c\_{16}^{(1)}, m^{(1)} - c\_{16}^{(2)\*}, etc. + +Figure AA.3.7aa: Association of Midambles to Spreading Codes for K=4 pattern 1A + +Error: + +121 + +Error: Reference source not + +![Tree diagram showing the association of midambles to spreading codes for K=4 pattern 1B. The root node is m^(3) - c_1^(1), which branches into m^(3) - c_2^(1) and m^(3) - c_2^(2). m^(3) - c_2^(1) branches into m^(3) - c_4^(1) and m^(3) - c_4^(2). m^(3) - c_4^(1) branches into m^(3) - c_8^(1) and m^(3) - c_8^(2). m^(3) - c_8^(1) branches into m^(3) - c_16^(1) and m^(3) - c_16^(2)*. m^(3) - c_8^(2) branches into m^(3) - c_16^(3)* and m^(3) - c_16^(4)*. m^(3) - c_4^(2) branches into m^(3) - c_8^(3)* and m^(3) - c_8^(4)*. m^(3) - c_8^(3)* branches into m^(3) - c_16^(5)* and m^(3) - c_16^(6)*. m^(3) - c_8^(4)* branches into m^(3) - c_16^(7)* and m^(3) - c_16^(8)*. m^(3) - c_2^(2) branches into m^(3) - c_4^(3)* and m^(3) - c_4^(4)*. m^(3) - c_4^(3)* branches into m^(3) - c_8^(5)* and m^(3) - c_8^(6)*. m^(3) - c_8^(5)* branches into m^(3) - c_16^(9)* and m^(3) - c_16^(10)*. m^(3) - c_8^(6)* branches into m^(3) - c_16^(11)* and m^(3) - c_16^(12)*. m^(3) - c_4^(4)* branches into m^(3) - c_8^(7)* and m^(3) - c_8^(8)*. m^(3) - c_8^(7)* branches into m^(3) - c_16^(13)* and m^(3) - c_16^(14)*. m^(3) - c_8^(8)* branches into m^(3) - c_16^(15)* and m^(3) - c_16^(16)*.](da85343976fdbb19f866d9ddbdad0eae_img.jpg) + +``` +graph LR; m3_c1_1["m^(3) - c_1^(1)"] --> m3_c2_1["m^(3) - c_2^(1)"]; m3_c1_1 --> m3_c2_2["m^(3) - c_2^(2)"]; m3_c2_1 --> m3_c4_1["m^(3) - c_4^(1)"]; m3_c2_1 --> m3_c4_2["m^(3) - c_4^(2)"]; m3_c4_1 --> m3_c8_1["m^(3) - c_8^(1)"]; m3_c4_1 --> m3_c8_2["m^(3) - c_8^(2)"]; m3_c8_1 --> m3_c16_1["m^(3) - c_16^(1)"]; m3_c8_1 --> m3_c16_2["m^(3) - c_16^(2)*"]; m3_c8_2 --> m3_c16_3["m^(3) - c_16^(3)*"]; m3_c8_2 --> m3_c16_4["m^(3) - c_16^(4)*"]; m3_c4_2 --> m3_c8_3["m^(3) - c_8^(3)*"]; m3_c4_2 --> m3_c8_4["m^(3) - c_8^(4)*"]; m3_c8_3 --> m3_c16_5["m^(3) - c_16^(5)*"]; m3_c8_3 --> m3_c16_6["m^(3) - c_16^(6)*"]; m3_c8_4 --> m3_c16_7["m^(3) - c_16^(7)*"]; m3_c8_4 --> m3_c16_8["m^(3) - c_16^(8)*"]; m3_c2_2 --> m3_c4_3["m^(3) - c_4^(3)*"]; m3_c2_2 --> m3_c4_4["m^(3) - c_4^(4)*"]; m3_c4_3 --> m3_c8_5["m^(3) - c_8^(5)*"]; m3_c4_3 --> m3_c8_6["m^(3) - c_8^(6)*"]; m3_c8_5 --> m3_c16_9["m^(3) - c_16^(9)*"]; m3_c8_5 --> m3_c16_10["m^(3) - c_16^(10)*"]; m3_c8_6 --> m3_c16_11["m^(3) - c_16^(11)*"]; m3_c8_6 --> m3_c16_12["m^(3) - c_16^(12)*"]; m3_c4_4 --> m3_c8_7["m^(3) - c_8^(7)*"]; m3_c4_4 --> m3_c8_8["m^(3) - c_8^(8)*"]; m3_c8_7 --> m3_c16_13["m^(3) - c_16^(13)*"]; m3_c8_7 --> m3_c16_14["m^(3) - c_16^(14)*"]; m3_c8_8 --> m3_c16_15["m^(3) - c_16^(15)*"]; m3_c8_8 --> m3_c16_16["m^(3) - c_16^(16)*"]; +``` + +Tree diagram showing the association of midambles to spreading codes for K=4 pattern 1B. The root node is m^(3) - c\_1^(1), which branches into m^(3) - c\_2^(1) and m^(3) - c\_2^(2). m^(3) - c\_2^(1) branches into m^(3) - c\_4^(1) and m^(3) - c\_4^(2). m^(3) - c\_4^(1) branches into m^(3) - c\_8^(1) and m^(3) - c\_8^(2). m^(3) - c\_8^(1) branches into m^(3) - c\_16^(1) and m^(3) - c\_16^(2)\*. m^(3) - c\_8^(2) branches into m^(3) - c\_16^(3)\* and m^(3) - c\_16^(4)\*. m^(3) - c\_4^(2) branches into m^(3) - c\_8^(3)\* and m^(3) - c\_8^(4)\*. m^(3) - c\_8^(3)\* branches into m^(3) - c\_16^(5)\* and m^(3) - c\_16^(6)\*. m^(3) - c\_8^(4)\* branches into m^(3) - c\_16^(7)\* and m^(3) - c\_16^(8)\*. m^(3) - c\_2^(2) branches into m^(3) - c\_4^(3)\* and m^(3) - c\_4^(4)\*. m^(3) - c\_4^(3)\* branches into m^(3) - c\_8^(5)\* and m^(3) - c\_8^(6)\*. m^(3) - c\_8^(5)\* branches into m^(3) - c\_16^(9)\* and m^(3) - c\_16^(10)\*. m^(3) - c\_8^(6)\* branches into m^(3) - c\_16^(11)\* and m^(3) - c\_16^(12)\*. m^(3) - c\_4^(4)\* branches into m^(3) - c\_8^(7)\* and m^(3) - c\_8^(8)\*. m^(3) - c\_8^(7)\* branches into m^(3) - c\_16^(13)\* and m^(3) - c\_16^(14)\*. m^(3) - c\_8^(8)\* branches into m^(3) - c\_16^(15)\* and m^(3) - c\_16^(16)\*. + +Figure AA.3.7ab: Association of Midambles to Spreading Codes for K=4 pattern 1B + +![Tree diagram showing the association of midambles to spreading codes for K=4 pattern 2. The root node is m^(2) - c_1^(1), which branches into m^(2) - c_2^(1) and m^(4) - c_2^(2). m^(2) - c_2^(1) branches into m^(2) - c_4^(1) and m^(2) - c_4^(2). m^(2) - c_4^(1) branches into m^(2) - c_8^(1) and m^(2) - c_8^(2). m^(2) - c_8^(1) branches into m^(2) - c_16^(1) and m^(2) - c_16^(2)*. m^(2) - c_8^(2) branches into m^(2) - c_16^(3)* and m^(2) - c_16^(4)*. m^(2) - c_4^(2) branches into m^(2) - c_8^(3)* and m^(2) - c_8^(4)*. m^(2) - c_8^(3)* branches into m^(2) - c_16^(5)* and m^(2) - c_16^(6)*. m^(2) - c_8^(4)* branches into m^(2) - c_16^(7)* and m^(2) - c_16^(8)*. m^(4) - c_2^(2) branches into m^(4) - c_4^(3)* and m^(4) - c_4^(4)*. m^(4) - c_4^(3)* branches into m^(4) - c_8^(5)* and m^(4) - c_8^(6)*. m^(4) - c_8^(5)* branches into m^(4) - c_16^(9)* and m^(4) - c_16^(10)*. m^(4) - c_8^(6)* branches into m^(4) - c_16^(11)* and m^(4) - c_16^(12)*. m^(4) - c_4^(4)* branches into m^(4) - c_8^(7)* and m^(4) - c_8^(8)*. m^(4) - c_8^(7)* branches into m^(4) - c_16^(13)* and m^(4) - c_16^(14)*. m^(4) - c_8^(8)* branches into m^(4) - c_16^(15)* and m^(4) - c_16^(16)*.](23aceb0e7d3c1a644294899d9047df05_img.jpg) + +``` +graph LR; m2_c1_1["m^(2) - c_1^(1)"] --> m2_c2_1["m^(2) - c_2^(1)"]; m2_c1_1 --> m4_c2_2["m^(4) - c_2^(2)"]; m2_c2_1 --> m2_c4_1["m^(2) - c_4^(1)"]; m2_c2_1 --> m2_c4_2["m^(2) - c_4^(2)"]; m2_c4_1 --> m2_c8_1["m^(2) - c_8^(1)"]; m2_c4_1 --> m2_c8_2["m^(2) - c_8^(2)"]; m2_c8_1 --> m2_c16_1["m^(2) - c_16^(1)"]; m2_c8_1 --> m2_c16_2["m^(2) - c_16^(2)*"]; m2_c8_2 --> m2_c16_3["m^(2) - c_16^(3)*"]; m2_c8_2 --> m2_c16_4["m^(2) - c_16^(4)*"]; m2_c4_2 --> m2_c8_3["m^(2) - c_8^(3)*"]; m2_c4_2 --> m2_c8_4["m^(2) - c_8^(4)*"]; m2_c8_3 --> m2_c16_5["m^(2) - c_16^(5)*"]; m2_c8_3 --> m2_c16_6["m^(2) - c_16^(6)*"]; m2_c8_4 --> m2_c16_7["m^(2) - c_16^(7)*"]; m2_c8_4 --> m2_c16_8["m^(2) - c_16^(8)*"]; m4_c2_2 --> m4_c4_3["m^(4) - c_4^(3)*"]; m4_c2_2 --> m4_c4_4["m^(4) - c_4^(4)*"]; m4_c4_3 --> m4_c8_5["m^(4) - c_8^(5)*"]; m4_c4_3 --> m4_c8_6["m^(4) - c_8^(6)*"]; m4_c8_5 --> m4_c16_9["m^(4) - c_16^(9)*"]; m4_c8_5 --> m4_c16_10["m^(4) - c_16^(10)*"]; m4_c8_6 --> m4_c16_11["m^(4) - c_16^(11)*"]; m4_c8_6 --> m4_c16_12["m^(4) - c_16^(12)*"]; m4_c4_4 --> m4_c8_7["m^(4) - c_8^(7)*"]; m4_c4_4 --> m4_c8_8["m^(4) - c_8^(8)*"]; m4_c8_7 --> m4_c16_13["m^(4) - c_16^(13)*"]; m4_c8_7 --> m4_c16_14["m^(4) - c_16^(14)*"]; m4_c8_8 --> m4_c16_15["m^(4) - c_16^(15)*"]; m4_c8_8 --> m4_c16_16["m^(4) - c_16^(16)*"]; +``` + +Tree diagram showing the association of midambles to spreading codes for K=4 pattern 2. The root node is m^(2) - c\_1^(1), which branches into m^(2) - c\_2^(1) and m^(4) - c\_2^(2). m^(2) - c\_2^(1) branches into m^(2) - c\_4^(1) and m^(2) - c\_4^(2). m^(2) - c\_4^(1) branches into m^(2) - c\_8^(1) and m^(2) - c\_8^(2). m^(2) - c\_8^(1) branches into m^(2) - c\_16^(1) and m^(2) - c\_16^(2)\*. m^(2) - c\_8^(2) branches into m^(2) - c\_16^(3)\* and m^(2) - c\_16^(4)\*. m^(2) - c\_4^(2) branches into m^(2) - c\_8^(3)\* and m^(2) - c\_8^(4)\*. m^(2) - c\_8^(3)\* branches into m^(2) - c\_16^(5)\* and m^(2) - c\_16^(6)\*. m^(2) - c\_8^(4)\* branches into m^(2) - c\_16^(7)\* and m^(2) - c\_16^(8)\*. m^(4) - c\_2^(2) branches into m^(4) - c\_4^(3)\* and m^(4) - c\_4^(4)\*. m^(4) - c\_4^(3)\* branches into m^(4) - c\_8^(5)\* and m^(4) - c\_8^(6)\*. m^(4) - c\_8^(5)\* branches into m^(4) - c\_16^(9)\* and m^(4) - c\_16^(10)\*. m^(4) - c\_8^(6)\* branches into m^(4) - c\_16^(11)\* and m^(4) - c\_16^(12)\*. m^(4) - c\_4^(4)\* branches into m^(4) - c\_8^(7)\* and m^(4) - c\_8^(8)\*. m^(4) - c\_8^(7)\* branches into m^(4) - c\_16^(13)\* and m^(4) - c\_16^(14)\*. m^(4) - c\_8^(8)\* branches into m^(4) - c\_16^(15)\* and m^(4) - c\_16^(16)\*. + +Figure AA.3.7b: Association of Midambles to Spreading Codes for K=4 pattern 2 + +![Tree diagram showing the association of midambles to spreading codes for K=4 pattern 2A. The root node is m^{(2)} - c_1^{(1)}, which branches into m^{(2)} - c_2^{(1)} and m^{(2)} - c_2^{(2)*}. Each of these branches into two m^{(2)} - c_4 nodes, which in turn branch into eight m^{(2)} - c_8 nodes, finally leading to 16 m^{(2)} - c_{16} nodes.](c21bad844b5cb6026c067a1f43ce67c3_img.jpg) + +Diagram illustrating the association of Midambles to Spreading Codes for K=4 pattern 2A. The tree structure shows the hierarchical decomposition of the initial midamble $m^{(2)} - c_1^{(1)}$ into subsequent levels of midambles and spreading codes. + +The root node is $m^{(2)} - c_1^{(1)}$ . It branches into two nodes: $m^{(2)} - c_2^{(1)}$ and $m^{(2)} - c_2^{(2)*}$ . + +Each of these nodes branches into two nodes: $m^{(2)} - c_4^{(1)}$ and $m^{(2)} - c_4^{(2)*}$ (from the first branch), and $m^{(2)} - c_4^{(3)*}$ and $m^{(2)} - c_4^{(4)*}$ (from the second branch). + +Each of these four nodes branches into two nodes: $m^{(2)} - c_8^{(1)}$ and $m^{(2)} - c_8^{(2)*}$ , $m^{(2)} - c_8^{(3)*}$ and $m^{(2)} - c_8^{(4)*}$ , $m^{(2)} - c_8^{(5)*}$ and $m^{(2)} - c_8^{(6)*}$ , and $m^{(2)} - c_8^{(7)*}$ and $m^{(2)} - c_8^{(8)*}$ . + +Each of these eight nodes branches into two nodes, resulting in 16 nodes at the final level: $m^{(2)} - c_{16}^{(1)}$ , $m^{(2)} - c_{16}^{(2)*}$ , $m^{(2)} - c_{16}^{(3)*}$ , $m^{(2)} - c_{16}^{(4)*}$ , $m^{(2)} - c_{16}^{(5)*}$ , $m^{(2)} - c_{16}^{(6)*}$ , $m^{(2)} - c_{16}^{(7)*}$ , $m^{(2)} - c_{16}^{(8)*}$ , $m^{(2)} - c_{16}^{(9)*}$ , $m^{(2)} - c_{16}^{(10)*}$ , $m^{(2)} - c_{16}^{(11)*}$ , $m^{(2)} - c_{16}^{(12)*}$ , $m^{(2)} - c_{16}^{(13)*}$ , $m^{(2)} - c_{16}^{(14)*}$ , $m^{(2)} - c_{16}^{(15)*}$ , and $m^{(2)} - c_{16}^{(16)*}$ . + +Tree diagram showing the association of midambles to spreading codes for K=4 pattern 2A. The root node is m^{(2)} - c\_1^{(1)}, which branches into m^{(2)} - c\_2^{(1)} and m^{(2)} - c\_2^{(2)\*}. Each of these branches into two m^{(2)} - c\_4 nodes, which in turn branch into eight m^{(2)} - c\_8 nodes, finally leading to 16 m^{(2)} - c\_{16} nodes. + +**Figure AA.3.7ba: Association of Midambles to Spreading Codes for K=4 pattern 2A** + +![Tree diagram showing the association of midambles to spreading codes for K=4 pattern 2B. The root node is m^{(4)} - c_1^{(1)}, which branches into m^{(4)} - c_2^{(1)} and m^{(4)} - c_2^{(2)*}. Each of these branches into two m^{(4)} - c_4 nodes, which in turn branch into eight m^{(4)} - c_8 nodes, finally leading to 16 m^{(4)} - c_{16} nodes.](7818b1bd115c04ee738bcf90f51d945b_img.jpg) + +Diagram illustrating the association of Midambles to Spreading Codes for K=4 pattern 2B. The tree structure shows the hierarchical decomposition of the initial midamble $m^{(4)} - c_1^{(1)}$ into subsequent levels of midambles and spreading codes. + +The root node is $m^{(4)} - c_1^{(1)}$ . It branches into two nodes: $m^{(4)} - c_2^{(1)}$ and $m^{(4)} - c_2^{(2)*}$ . + +Each of these nodes branches into two nodes: $m^{(4)} - c_4^{(1)}$ and $m^{(4)} - c_4^{(2)*}$ (from the first branch), and $m^{(4)} - c_4^{(3)*}$ and $m^{(4)} - c_4^{(4)*}$ (from the second branch). + +Each of these four nodes branches into two nodes: $m^{(4)} - c_8^{(1)}$ and $m^{(4)} - c_8^{(2)*}$ , $m^{(4)} - c_8^{(3)*}$ and $m^{(4)} - c_8^{(4)*}$ , $m^{(4)} - c_8^{(5)*}$ and $m^{(4)} - c_8^{(6)*}$ , and $m^{(4)} - c_8^{(7)*}$ and $m^{(4)} - c_8^{(8)*}$ . + +Each of these eight nodes branches into two nodes, resulting in 16 nodes at the final level: $m^{(4)} - c_{16}^{(1)}$ , $m^{(4)} - c_{16}^{(2)*}$ , $m^{(4)} - c_{16}^{(3)*}$ , $m^{(4)} - c_{16}^{(4)*}$ , $m^{(4)} - c_{16}^{(5)*}$ , $m^{(4)} - c_{16}^{(6)*}$ , $m^{(4)} - c_{16}^{(7)*}$ , $m^{(4)} - c_{16}^{(8)*}$ , $m^{(4)} - c_{16}^{(9)*}$ , $m^{(4)} - c_{16}^{(10)*}$ , $m^{(4)} - c_{16}^{(11)*}$ , $m^{(4)} - c_{16}^{(12)*}$ , $m^{(4)} - c_{16}^{(13)*}$ , $m^{(4)} - c_{16}^{(14)*}$ , $m^{(4)} - c_{16}^{(15)*}$ , and $m^{(4)} - c_{16}^{(16)*}$ . + +Tree diagram showing the association of midambles to spreading codes for K=4 pattern 2B. The root node is m^{(4)} - c\_1^{(1)}, which branches into m^{(4)} - c\_2^{(1)} and m^{(4)} - c\_2^{(2)\*}. Each of these branches into two m^{(4)} - c\_4 nodes, which in turn branch into eight m^{(4)} - c\_8 nodes, finally leading to 16 m^{(4)} - c\_{16} nodes. + +**Figure AA.3.7bb: Association of Midambles to Spreading Codes for K=4 pattern 2B** + +### AA.3.8 Association for K=2 Midambles + +![Tree diagram showing the association of midambles m^(1) to spreading codes c_16 for K=2 pattern 1.](f1ba1e68228ebd4c3109371574a723e6_img.jpg) + +This tree diagram illustrates the association of midambles $m^{(1)}$ to spreading codes $c_{16}$ for K=2 pattern 1. The hierarchy starts with $m^{(1)} - c_1^{(1)}$ at the root, which branches into $m^{(1)} - c_2^{(1)}$ and $m^{(1)} - c_2^{(2)}$ . Each of these further branches into four $m^{(1)} - c_4^{(i)}$ nodes (where i ranges from 1 to 4). Each $c_4$ node then branches into two $m^{(1)} - c_8^{(j)}$ nodes (where j ranges from 1 to 8). Finally, each $c_8$ node branches into two $m^{(1)} - c_{16}^{(k)}$ nodes (where k ranges from 1 to 16), resulting in a total of 16 leaf nodes. + +Tree diagram showing the association of midambles m^(1) to spreading codes c\_16 for K=2 pattern 1. + +Figure AA.3.8a: Association of Midambles to Spreading Codes for K=2 pattern 1 + +![Tree diagram showing the association of midambles m^(2) to spreading codes c_16 for K=2 pattern 2.](a166566092dd84196c2ec048ca175290_img.jpg) + +This tree diagram illustrates the association of midambles $m^{(2)}$ to spreading codes $c_{16}$ for K=2 pattern 2. The hierarchy starts with $m^{(2)} - c_1^{(1)}$ at the root, which branches into $m^{(2)} - c_2^{(1)}$ and $m^{(2)} - c_2^{(2)}$ . Each of these further branches into four $m^{(2)} - c_4^{(i)}$ nodes (where i ranges from 1 to 4). Each $c_4$ node then branches into two $m^{(2)} - c_8^{(j)}$ nodes (where j ranges from 1 to 8). Finally, each $c_8$ node branches into two $m^{(2)} - c_{16}^{(k)}$ nodes (where k ranges from 1 to 16), resulting in a total of 16 leaf nodes. + +Tree diagram showing the association of midambles m^(2) to spreading codes c\_16 for K=2 pattern 2. + +Figure AA.3.8b: Association of Midambles to Spreading Codes for K=2 pattern 2 + +# --- Annex AB (normative): Basic Midamble Codes for the 7.68 Mcps option + +## AB.1 Basic Midamble Codes for Burst Type 1 and 3 + +In the case of burst type 1 or 3 (see subclause 5B.3.2) the midamble has a length of $L_m=1024$ , which corresponds to: + +$K'=8$ ; $W=114$ ; $P=912$ . + +Depending on the possible delay spread cells are configured to use $K_{\text{Cell}}$ midambles which are generated from the Basic Midamble Codes of length 912 defined in table AB.1 below + +- for all $k=1,2,\dots,K$ ; $K=2K'$ or +- for $k=1,2,\dots,K'$ , only, or +- for odd $k=1,3,5,\dots,\leq K'$ , only. + +In the beacon slot # $k$ , where the P-CCPCH is located, the number of midambles $K_{\text{Cell}}=8$ (cf section 5B.7). In all of the other timeslots that use burst type 1 or 3, $K_{\text{Cell}}$ is individually configured from higher layers. + +The mapping of these Basic Midamble Codes to Cell Parameters is shown in TS 25.223. + +**Table AB.1: Basic Midamble Codes $m_p$ according to equation (5) from subclause 5B.3.3 for case of burst type 1 and 3** + +| Code ID | Basic Midamble Codes $m_p$ of length $P=912$ | +|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $m_{p0}$ | 9E57CC4EFF411BC3A56568FCBECB53005A3A19CA729C922826FB5E2F55D4A0C6D57335B055
188F2274154ED0F61107BD34023FDC3887072689755E733FABEED9B7967C46E9452F78E0CB
97CAFB92DD44C90E40E3CFE9DB4054AC45EB8F260FDF8CFB5C3C23733F7344633F26CB092
AC89F4 | +| $m_{p1}$ | 3AC41CCDCEB89F45AA67884536D0B796A5E048D76D2F9531E2E31516496B3B76196D68FB7F6
CFD8C5EA232B5C012953FFCF4C1CA7A2BDEB236426E422FD4F050C4022188D8068F47441FC
31B005F8F53452DB8D72839DF021A45D8BC51D1CF440A665D1F751145D2F04CA352BF2C0BC
F589E | +| $m_{p2}$ | 4241DBD18BB9C42E335530533B27F0411A0588156421FA0F306C2598CD9C2D3F7D954C64E4E
EC699B2414356F1D47E2A3D09A56EA850ED4319AFE7AF07538A9499206DD943AE990F43FA33
FAB6CA8E6B3615D16D17B7FF914377BC59870C269E851B4E012B107EF92542B3A2B458E10DA
709 | +| $m_{p3}$ | CCF886D4B65C6CEC0E3F8D8186F6CEA1FCFFEE878506F22EF69AAD6F51FDF2071B34E4ACB
CD2545866C36B31C3235DD38361403E53DE6CD4FB1DC91752BF5F6C3AB442E292A90471F2A
5B9FE7599CEB4651D235D505052C22F54F868C18AB14205FD41FD468375B661BE35F0AA67E5
F33693 | +| $m_{p4}$ | F95E0D6F5101D3D7BBB354646818EAED147E3E4CB0249F696738B3F3A65192F5F012868C190
BCB967DEB112D907A85F33161C68B9E425A3F5EA26022F6C40ED01B8DE7FF6A6F75F313FAC
3DCD47C7EAAC32A9AE47D633CA6F47AAB8EA282B467D8CE21B1352FFCD36966F0A9B2EDE
ODF6252 | +| $m_{p5}$ | 6FCD348CB614E6C68534737B6AB3F693A7256A85D5C28C6A77DBEA1ED62E1813E7CC88AE99
0BE4432387ED43C60FBA6556C5DBD7111B1B53FF5FBAFAF86CB761F15EE2782C7616C816A1
C77E27F197DAE6BCBD028F37E5DA7906198C98F72207A0A8FF108EAA66C84D976049E4BA42
E0C27D | +| $m_{p6}$ | 94503C230B52660711010625B04D9B98ABD0872DE470F3323F1D4120F46518715929FFF471421
2C26EC813F9B0601B573A3B38F8833BBCB57390D8E16A8561C54E6FEF9D8A64B2E06C07E417
B426671CDFAC9C7FA20D15B556CB39FADF128560A57D26B0C9354C1CFA5334A7C5F96B9528
1A | +| $m_{p7}$ | 92B52AE0D72D7559C4A277EC57995B7B8BF3CBDA1DF8FA7D6A96DD02F93B28F84C18E6F905
D87A12D923E38C4DD659819F1CECFDB48DB8EB129DD472A2718045ACDE58C35A273FECA71
365FA35130215FD801BFA471D27ECBA3A8CA946E83060465BFA9A1F3C8888133D22BF43E1C8
9F26F2 | +| $m_{p8}$ | BD71D9BF8F8250A64EC5131043F2B0E7424A365508E4E268A4A9857BAE4E3360058B8AF6FB4
A10B3C2BFAD8ED116229056B01F7E59E3D9D4120089EB213106B920925EB2422196AF8FA999
8389664E80DA294E1B4B7D6807FF3743EAE53276AB634EA1B080FD55425C318B1EF670E9783
EF0 | +| $m_{p9}$ | D61ABD7705BAB371765DE3FD732D2C5A51D5DA1BA0BF789170F01936183A55CD1693685BD1
BEC7BF691144BE24A8B74D7FCF1830425997806FE10C49E98F73BBE07835ACE5F2E6E083294
BA4048D8AD59A4E6EFE538B6D1991C21BD130D25555985D5E8AC1623FAC93663C5E1CCC77
A2B3FA | +| $m_{p10}$ | 652DE6FBD477D92AFC5424953C64A722EAA5D5CB0E6A04CB43273841F71525016D8DD83708
11E3F38851E973D8EC2CEF3180D1462E6530623B004813C1E154B6CF790BE4C712573ED7348
9BC2952048A5C17F51A25604A6CA660EA480618F8DA78470580CA9B987BE33F3EC6485AF440
ADC3 | +| $m_{p11}$ | 49AADFAED5D1C27455F2FE9D2C66B31E3792F088E20562C3B6DB2E4F2C67445690164E34043
B5C98819236020C15264BAD09CD75608EE4BF2F62D3671611443D541DA129FF475E26214AFE
00419D12EDFDC443A4F7A6DD38B2BF62F64294A80937969E9920FC3A33DE7B131C61F20C195
621 | +| $m_{p12}$ | 6D408E783793B8F8B438F512CC4AA7F94B296885D9F59505F339C5C1F7FDB8F2567866B876F1
6614BB6E3788E1B237DD8BB955341911ABADD6E7D3276F7068DCAD08737243631C42CB77CC
CFF7FD7A03B52D5D4C73F8716A83B6094827098095F19F136491EB1405992E3ADB80B685FEC
B2A | +| $m_{p13}$ | 349BA9F2D6B07CC41DDBDBB446F844D77A86E96C9C2F191F1BA42D0402754B40DFE76BAF4
DBEF3DFC28E426ACCEA6327FA51C4DAD1B6F2A9082332FA4E0BC21FCF10CA9822CDDEAEC
38760194855253E3E3D46C8565CE9EE86761B7E28BBF5C4958A3EE709B8FE9CDD0CF9560A1
DAF6CF971 | +| $m_{p14}$ | 033E68B1E9D433BC88119CCAB47004E20B6E1B8F0E4C2756DD549EBDBC5243BC898694426A
3EDECEAAF00A7AD02D4AD1F0189A1E99B0B1D796E8BB8C5EE977280408DA0F772EA3A1AD7
44CC0C78C39070BFD324269BF86D67916D157A9BE63D9E94B76F690050368150867198BD0A6
8031CA | +| $m_{p15}$ | C08FA672B545FA416E4856DF87BA5CBFBBD64EC62A2A294427A563F691A28EF5610A0CCA37
ABA21BD98535B4BC3F0C009CAA962384B5004063D16083C93D1A7C6002BD1D51A27B671EBB
C4860092DF3B3C389A0E909E664FC4B99E5B1A39B72500335491372956E1782EDC5330CBEAB
7A636 | +| $m_{p16}$ | F8AB480C79497D13EF846E58F4D6A0B52CF2A71AB1236661B0D84D8CCA603B157BC07C0000
306487C41A7CFC6A3A58C1276E8BBB592F9341C298E17886E3A2AA2A08576FA2380C710422F | + +| Code ID | Basic Midamble Codes $m_p$ of length $P=912$ | +|---------|-------------------------------------------------------------------------------------| +| | CC0B1AB50B13D6B676EA102B6A035449A77652524F3D79B05F9EB24C286D7A8E4AFA1596788
C987 | + +| Code ID | Basic Midamble Codes $m_p$ of length $P=912$ | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $m_{p17}$ | 53F0FFAE B51656B7DC819B749FB5DF94E4A9545B669AFA52F385C5869C4D9A2F3BB5FC874B
9DE055EAD1159C47E7BAE8F08C7F3A202D18AF084CB9DA377C3BF8F9B710F9262855E5E04F
9C92C11E4B03DCBDFDF06311DFB839969036DD115654AD90E2096862B37338272506327E3D3
9D189 | +| $m_{p18}$ | BA58B8BE4FB00B6122DA4EB61BFB9B775811B88EE9444BD8400CC9866193AD636A86A23588
F59E176DA8A18B856E8FFB41A8D7E91A9E874AB50B89E971AB36050058BC70C84220ED0D568
1F7CD84CD493A65B41B42E10D38B18598C63F73163EAAC1C93CF3A3CAA3BDFB29D02521777
14756 | +| $m_{p19}$ | 0C0769A781CC98EDFB93319AC2BEB03C8475C874CA1AFF16BEDE90B07D5C6EA8ECB401916
B5688AD4C0D97DF085CB0A16CA4D678A0AC1E00F9737B4CAA93A163F827B39AFF1AFB831C
EDB26EF565102DB24ECC2B6BAF72B44FF5EB88574B38ACF3EEFD87E4F6173846B151271DD1
E1466DC4 | +| $m_{p20}$ | 132C03285553D9205AA3746EAF108D92461B3DBA03866E70A2F47360DF17502559E5AFAA2EE
6C7DC800D8F620A3294A3E2B1FFFC17AA6634D6B7F3353A652CB0825A4E13A3CE5E91F7225
181A0678F53B3D038BACAFE214FD4BB4C2D80EF35D42A2F19B69CA2162E30543BE9BD85481
85D0D | +| $m_{p21}$ | C2E92D3AA8981AE97C3325B1FC1843CB0E8C5E394C201981A8DD8D1BEBF8F649166508A5A1
7819D02EB0A8EF797D8C51DADBCA9A66D949A4C7E6B37ACCE1A2E578469D1B9D8D1A47E7
BEA9DD0002FF7D64BF6519A63D9084C0841A8841E183973644DF590AD107E852F3357A70A2A
5637E22 | +| $m_{p22}$ | 9BEF2F948ABC4CAC809972EA52EFE03907142A44F3053F970445B1EDF5D1FC9F03B6EE30F7
CD74C04B68389D5826E85E763653ED75D1469A240E406B3989EDA065BD84E34F790D74D2D17
D7ABCEC25CF7FF130C4BDA979BB5A9133CF3E79B3558E921EAF013A0CC4B87C5FDC4AA9
F245E15 | +| $m_{p23}$ | 6DE4817165AAC324EA17347B78FB4E1D642F74E15F292880975C42F405D440B1FB101E64DBF
0A0ABDDCDDDB388672248D2BE9431F7BD77CEF1583F04680865B315E8551A232547A807CEF
C742E529CCE892EE7FB2F312E96EF7372AB4F7310F87912793FCF2BAE5DC0E6DE2CE9FB40F
53513 | +| $m_{p24}$ | FF5034A2747FF78F34664125AD31AB2ADD077839D8CC44372D13589649381A2198631F1454BC
450ECD0AC8D8695034CA8130B5E5DABB9EDF7A4AFC0738D82B7BAC7086FE813289092AF218
F5D04BCBCF98A07F4C2E0F8BC9C52F45C5813A693EF555A2B1EF308908FC993B2266B2AA09
C3DA | +| $m_{p25}$ | FE1DBAC430C3B1815990B234583A86EB45EDCB32A38C92C3502B5611819701B1F545410092C
AD7E962D3D6E232059CF0C9E8DEA6F7DA21D89F611EFE129D854C5B957FC810E0730EA0C56
03B035DD9D19686BD7BD8FF0C9979C900E955A649616DA71D0FAFF079176E541F1AA27F024E
669E | +| $m_{p26}$ | 8C0A6F60BEF5DA92E8702CEF3563B50B8C1C2D29DC82B97FDEFBE322024205726A0E5B9E6C
BE0F9F02FEFB264E62FF99955B536091CEFE5C6986957149C2954E0EC43C73650855376E0A8
A4ED9873AA8AED98D10579ADFB05A8713C37851692C3B4405D9D86E6BDA0EA9A4BD0CEB7C
79E6FD | +| $m_{p27}$ | 205BB79C6DEFF102C2FEDA5301BC5B6D62957A3A02B486DD6BEB878558827499DFC1DC79E
C55241B208599E32B99959F9589624E2C0AAF11E3C8CCCFA7EB88AE7B844B483BE360CF3441
1EF739BF073AAAF3F84E516CFA10992D606789A20F15686F54CBCE8A1305BEBF7EFE8EBA95
F723B5 | +| $m_{p28}$ | F32AE20D70B2FDB523682A5AE7A83307F740DFAAE0DBB58F828DF0ED20AC79C85E2FCAE3E
C342E79F0EC8054231A541952736CFFED94A4F44FB7DF473C476FFB3CC87BF18A0938AC776
A26DEB32BF906D2C90F57ED192BC33F1312746B143AF383C972A2B61AD8D46F3C4E56026150
6CC87B | +| $m_{p29}$ | 8F6A99C81370432B4D05459359C92D87DC3D10E82454B911EAD9E80AF07F26B198C6ED71E72
F608118B67C61E8C64EA654B7BB0ED91A3DAB2B77C5CCF92AEEA8D6DB9E9AFC142F6FA9D
2E79E443DD42D0F66BFE92D9BAE58113B8811E50FF8796E13C43BB210076AE2F8FD0A1FDF3
D5B2AFE | +| $m_{p30}$ | 3BE3E2BD5546AFE1933CDBEA679EC8FBAB69C0ACFD5B2DF9A72CC5B4132123D6EFE9F907
CB187DB647C6C7E59F71E830DB84472B40C011CB418DACED36025BEF7289FA803D1E32FA2
D35F667D2AF8B78985D469532B5FA8336072B7FC74A515B8700CAEFCB625AC212AE335E6EB
C37207FA3 | +| $m_{p31}$ | 2642A80A8DD998C3198E6EF691B68257560C5E875A32F8C101478B24F9150883476B03F26B6A
137E117057B525F37E3749D1C1DFFC2BD059C6F4FBA8765D58493C87894E819EBC1172A62D
D6F3DFF2B18A5987B0841FE85BC85575B0B1048A9138E6C9181017A501CBE76337926BD9AC7
78F | +| $m_{p32}$ | 362817D18ED89453CFAAB83B0D182FC12F3E90C124514F404743D223487FD2A2026603D3CEC
04AADB26D2DD8123B2D18C4ADF6A95260FC8055D29B0EC561FC355BEA5E97CA030B0187
773B726299C2CB91CD7E0EE28B89C63EBE333F316DB6209B012A230FAAA29C52D41F9DBC6B
66F7BF | +| $m_{p33}$ | 6E92DBCC6445EDBDAE1D566F99C4FA5AD9823981B71A883BCD14967C2358711A59B856EC48
90697E030009682A332D0F7CD85FA7E509CB2538BF395306603EE229C950D749D3A4EC4172F | + +| Code ID | Basic Midamble Codes $m_p$ of length $P=912$ | +|---------|-------------------------------------------------------------------------------------| +| | 8400B1E1BA5479098A79F48F3F977C400D54135F75DBC6CF97019E30954AAA550D95ED4E08F
C2AE | + +| Code ID | Basic Midamble Codes $m_p$ of length $P=912$ | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $m_{p34}$ | 82B02C0023B142BFFF4C2EAC7E5F83D3C76A7A18EAC7B621A0F9B65152E475C8F8E2A30479
EC3EE9263F73426722E9A96DC53EC42D7C0BC50A643E66E9B8C0BDE8E893A7562CA33856D4
219A5A59F599590164B4015BB9EDCD26904B9716449FD02CA7380C6A50CE22A40E0CDB787D
109122 | +| $m_{p35}$ | CF2673929413ED857B0DC9894D8AE460C19CEEA9CBEDB810388C0ED13E11FB7201ED5A686
5ADA459DC8E5023C73FC13D159A7A540F64FBF586A2504C18843F42714D4699DF6591944AB4
4126A4A83D175E8C41EFB28D34048E2EBEF454150F4878F6A02A874B1BE46CCBF8577A5EBF3
77578 | +| $m_{p36}$ | E0FAEF096093575ADD91187D72DDB6E6401BC189A5014D6149E092146BF879450EFC3E504C3
06D0151ED465840ED503FF3BF92CE33E411A17AA7DADB365731D271791B8C21BED3557892C
4D0B3795A24EB61566C3143A54797B8BF25194A9F8CE20C5C991FA29BBA64211B4807066A45
B9E8 | +| $m_{p37}$ | 234F19C1B17B1C403171712FDB575CB8FCBFE15B39F548E682452117597AB24B8E7E51834F22
2508ADF3260AEC2246AE84359DC0130229580F98275BD036F82BCCACBFDA34391C556EE7E4
C90A2C67252C2614175A2D0C37D5C861A0D735DA8E05D2E7712332C0BC0B33FDFED4FD90A
61D2F | +| $m_{p38}$ | 415B84B33D1F23316B8C7DE312EBDA1091AA5BA44319C7289C78701DD437028F8CBCA30C53
4FFF1875A230EF762F1293A9C9BFB32856DBE06EE915D1AD66417474A705B7BFF4EC8DD4488
34789AE9BBBA1D2D99080CF03841DA0242E0204D3B80680C1AA6935F3F6E9F0AA2B51E5A7A
227D0 | +| $m_{p39}$ | FF16F0619F5A297CC40FC2F97DA2A92A9D144C2D1C1043F53DA05909FB7F23DD82ECE70545
330C327A097FBB2F93A0E7970DC64768F76FCA0E5D255B4116550E838664791055B8D24A5837
B6DE3CA65C522A50CC25284D68C3BF61440DEA011345F3127A802234B66E5FCB893830BD39
C6E3 | +| $m_{p40}$ | E9EF50791AEFDCEA8D5FCE9398C3FD7A8AFBB50F2268234F62FD799FCA3BE94285C92BEE0
44A546DBC29319E983C6FDA5431BCB78AED499872F24F228FA4782FEBEB6AA13606239E56F7
D19107CFA441C2004192386AD0BB6DB381ECACE4D153DD844F9179263E899DB195F16D9581
248259 | +| $m_{p41}$ | C310A1E57CDA2246752056F432E5808F423AE04F5757F6B3D2E798FBCAF12517BA77CACCDF
11B18D6A04CB37D80A077C8F90FDED0D33F8739312401B6889E16B8665ACA75075210424AB7
BB2516828B2CAF89ADD0B8CD223FA9850B170D465125723D43C5DCFB7264F4247B4C0F5D32
83C15 | +| $m_{p42}$ | DF2A1C8FF69CFDEB8D36F67744F0C94A6028C7FFC376E4F32AE818557C2F017F040D8809614
1C90B1F4F55A22AC386BC40ED96EA1B7BFAC91AA0BF97E36F60E225E167D926536AA22BB1C
E36BB9B42C53CD1A56B2354F23807B350BDCE7C9B01CE6AC7AF212C050F8E827CBC3AFF71
D50E97 | +| $m_{p43}$ | 88F8ED04165EA0D34E412F8C7175D3C387A9B18E0316E00DB2F6BB74CB24BA74EDDA374036
FA0A4224F6434752B67462C8445EA3E51884BB5C079A862E7711AAEBE14C50DA149B032066C
88E38CD0FA85AA6213F28E5BB2D67BB1E000E16B6330BDDDB9796AFA27EEBB6A0A7A1395DF
FF1588 | +| $m_{p44}$ | 5439C5FF080A258601EDAB8A0B54F51AC7C66B6D8165AEA5BE1E15AD85DFAAE4F908AC8404
DA4CAEB3FA93AD698C835F3B60205DCDE971BE63D570267B04CC26A8CF3D5051B22D9B0F4
099CA151A89508E1838185F90D7BE73161CA5CC3950E2E848B26F85B98331398AFFEFEB9A04
6A5A3E | +| $m_{p45}$ | 9D26B1376B5C4F5F586486CF35762FF481842D6353D6006AC191D1157CC39678F0B4D31A1668
AF65E2B78B5D7DADDB45621DAE6A3E4B0322FE0D5713485234392040C32551461A0749B5362
7F0364A998A18CC02EE708732DCA8189E523D588EF5D3CF70E87EA5140007BF84AEC5BC1BB
391 | +| $m_{p46}$ | 89530DB4E7FEC9DB64622E6FB8F0879B24F3D023C83AD69D674189910F1EE52BED4FCCC501
EA81E122E8336A89D209FACD7F6A89F65611A470C16B12CFCB84AE475E6B82895CDA52F564
DA7726210D073B38342F6BAA22014A7D0EAFD6202DE5B03CAACA0610884223E4C787E06F84
A8CBFB | +| $m_{p47}$ | A9E83B98E0C2ED7950FEB892BCAC4ECD503CDBD193D143BD03F2459DC6895A81314861930
CBD9ECFF114865CFECFBF025075D3FD471558FB7C6A6CEF8547E937CF52DA324E4EA04319
B78376D2F4BFFE8E467DD8C29DD0D44135ADF1D179886A82320FC35AABE4957641C9762F7C
3AA7D970 | +| $m_{p48}$ | E113DC0ACF1E85730EA81E964487D1D8263A186C5B627B8F96D95244284FAF1E9D8351D1DD
7957D205C15F26F3919B34196FBEDED8E88D96C00441A438D27B215AB448B6F6D9DA895FFF1
0EB3D4FEB44468F21E77CE64757F6D8A627C4A2BF0DD9D67684F80F3C1BDDADAD192EF32B
AE5479 | +| $m_{p49}$ | 687C6FAAB36FF9C20DDBCF1CBB7AE82F334E48CC6C10B988D8154DA5D18746F3E9153A551
0C2B026F5CC7B6A7562644E5936CEF2A023F40BF239A1F2A6DC75782F2D056174E8A904A7A1
1D3E301C0842F8BEAAA3D36C86F240309635A90E10E766FD8149844F8B42A9C4A59FE4863AD
0E285 | +| $m_{p50}$ | FFDBD37063D55715CEC274D716DB7DEDAB90ED8808952BEDA0E75599D5A29C13C483FB97D
3A0822F46F2E1F4ABB756A7FD4710DE7333B488203F7152FE1D1DECBE5AB17EDB806681DED | + +| Code ID | Basic Midamble Codes $m_p$ of length $P=912$ | +|---------|---------------------------------------------------------------------------------------| +| | C8CC12C11753418E2B2A5C95D60FD2DC9970DF38C84CE7864833B69046AD039D261DC1C14
CF056DC8 | + +| Code ID | Basic Midamble Codes $m_p$ of length $P=912$ | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $m_{p51}$ | F1748076429321CABC98153CA2C18D3ECD24CAF8B22CD97C1674F6A3EE26C016CC1B8E8C3
D0BBB98482D09ADB2B06CAAAFD73FEA2203F8A2B791ADE9C14A5DA7015A442392535CC10A
10399B2F80D818DF180707211A8D858ADD9DB1EE10BBD6F92F2DA9CC03512EAAE5BE18F7A
A87573FDC | +| $m_{p52}$ | 81DDF8E2BBAD0D040EF4796A5EA19DFA9C0CA8067068909896A83C2E1E239D83D2B858E086
4A7BDD2962AD001EB19665E4414BE81FBA6D7BBB1787AEDB0C81913D5C86E3905B20DBA6C
9DAC555B4BA05574F3120FE8F3326B336B61BBC2068BCE2788641CD59032731BFA73E58869A
11E4B7 | +| $m_{p53}$ | 0F59625A8BBF1E83A906E5EB9E5E1CF85DADC7BCF7736DC02DDEADC8736F7399E4CE10601
DD832D32AEA53AC895EB92DF5FFB409985EED5BC9C775C7A655102E644435ED2EB84DDF30
130F101FBF2A93FE65D473593FF3A4134A41C4C7EA6A50448F8B2FE1F91F1E9E84C95818D2C
A340C59 | +| $m_{p54}$ | 3AA62BAC2BB34A4B7D06A968E20E16A1C79D865C1F87DCA2B3DE6F3D49D962175B4D7FACE
8EB162E9E0FFF9FABD6F57305051838A7D5A370DB79F9246B3ABF10719EF9EFD86664DEC9B
06137911903AFE43D00DC992F9F8FAD1C017CBB7591E1A02BDE56B75B2F82FE61234ADCE34
AFA8017 | +| $m_{p55}$ | 1682757D7852076B78872B235412EA5CE2AA997BD66C8689DB605F04779E70F61A4E5AB75C6
5F1BD3D9948C2442D9AF89EEAE6609E7E1DFC95294C318AAE8FB0C2E025713BE5B38A08F8
A8463D12081EF250C482A2DD9803628B07C9076CACFFEF49EDD6A3440A6952C73493E0DEA0
DB112 | +| $m_{p56}$ | 016B428AAA41A03CB6BAEB518F27D34CD9F4E0A7F0C149D3B8F35B9481274E4258C01E6D1F
0EF01256E48B00C7D4F9FFC242273890A4D5BF9338A1F5D74F01BF56EB2E5DE461AD46F7844
6DC2B56667E8732E73E95768CC05615752A8D2C88DF077277F026CA1A1057DA0C15D10CD609
3DAA | +| $m_{p57}$ | 68C2F3594AD2A41BFD7BBF60702C5581B3F75E54CE7D1B3A598400306FAA22783335DAC415A
F939C4596A104724F53953BB51239BEB77D2574FDC37CA1B07C5E7AAC2774DC35DFD6B83DC
CEFC3C0A9B3EACE9A6052C44E8C327B24D173A760BF9535EF8095F35D9DA3E289F636521ED
06584 | +| $m_{p58}$ | BC27B7917AA3ECA9ACE1F94A1A917FE1CE6754E906AD4645719CB3818FC58A48F8CBBF3293
8D18D68203507A4D2205C049AA7741E089777205F1EDA69439984BA8DFFE45C210253D528305
BFAD36FCC90683801A0F19022923E45DD0A52F6E2E3F9A49333250F76A8BA8C325A39B362D9
F2F | +| $m_{p59}$ | 057CA87F217E30182A60109027005CEF36F98571B1C11A6525308632CD39232853177DB25A639
192FB65EA70A70D90CCAA34FBF7C2E6233A362F46345F15CC5B2565DD7537010E1BCC22AAD
D2C7BB05EB6BC05A5DF289A8AE249EAC10F21666C742A09462FE8F1D38B5860CDEFCFAE2FE
BDB0 | +| $m_{p60}$ | A2AD4999053CFAA50A1093DB07AEABCF6F80C293E00D8ECCB12B56CE7FBA3F62D686C15B3
E1A941AB480ADD6F2176C537686F770D73ED366086E67F2C46B8AC06B870880AAA2D9B44421
7504ED74C7B90390485AFC46A63F15CAD9251C638278707D46A384DB62A7BA27245A5E16D62
31908 | +| $m_{p61}$ | A196D99A227C44C27BF2BB0B6029557118925061AC9ECE965EA7AC380CFE1C0C33E5B7567E
4FB77B7AC7DF34E4557545366A943D375E4D8A211CF03FB7F37620E9EE47267D78ED1D0A247
8A353D2217AD5AD76892388EE7F0144ECD69CE3B5B04928CFA6A68C9FD0FE817942FF143D9
C2DD3 | +| $m_{p62}$ | 2968ADAЕ21E52DC8AE811AD840AB7600A5C6FACB2F3BF707D0DE018178B5FF73BB31F5C88
E9B6C02C54B8D7B1A049E39CD7960F7109AA5EE9A18E9C3E9F0E8359952E144169870381391
E3761E3137204CA71CCC4DB38CE4394068303F088A2497FD49DF4864CBEFA1675AAA8950685
77AD0 | +| $m_{p63}$ | AF21B04CE4B418B9A0AD80221A9C47978750483A83E9096D9F09069C3065E8F6F1FA68EAD50
B78736311BDD70F72D97290C06888ACDEA4FBCA3B25FFBC5C8E91676C4384EC68C5D3C40C
CD5AC3E75116CDC28C05F08B479A73E2AF7D380F69CEDA810A60B6FD6609CFB8A7D4E98DE
0596C4A | +| $m_{p64}$ | 56BC72E0F1CB9DA84FBABFF84FA635E1AF9B60BEA6C22F8953156C90691F44D2B4078EBD8E
A8BF6760BCE5217E2B0C2E19D4470D3321083486339AFD6D57FF66E21C149B40FCFC5CDAC8
0F7B6ED2AE576F3ECD4D14A5C56DCE7CD04147F9D725A783D9915D2E7A036FC854CC373EE
8333305 | +| $m_{p65}$ | EDF8D061318EC3126958D38D4E0A0C71460B5F46E16CB7FD7A4084D174F900BC8A79C672C6
12E46E2AECD FCF3C744F40510FB20D15FD9C2E696F8FCCFBF80FA6A435369889E17A612EB2
22D50A6B88BA06408DE022EBF4EA74295F5B921AE86029D376E2D51250B79053EB3AA58B4C6
F3199 | +| $m_{p66}$ | B86E98A32DEB7FB6F9A120725EC9C07CF1864670A9D5082D7DB7FC7656AE8EFA05D661E63
A06D436DEA5CB02E5F29F4B3D364701B1481BCACF306804FC14EE48A19CB8095F9C456502B
39A08593AE258DBC12B358D6918C3EB8546F9F3E36646282E08142CFA309CECC823549E0294
6606A | +| $m_{p67}$ | 070850FC776EF3F88456CC9841604D144CDD4B58247B2938AA074009F128682E25FE0E6DF2C
3991A5029A7E4EECA22C5718D6C457F3B529702EF34C7CBE96B6EC2A2391DD6079A21941855 | + +| Code ID | Basic Midamble Codes $m_p$ of length $P=912$ | +|---------|------------------------------------------------------------------------------------| +| | B5BAE1729CEDE009BFE8CBA54C25E7F0960990B004755A647D568D290A645C4C3B8E7262C3
47B5 | + +| Code ID | Basic Midamble Codes $m_p$ of length $P=912$ | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $m_{p68}$ | D96CD3FAF18CE3B8D470CCA2567E54544F4F9FC471F02F6441AB5F786DC9099E16C9482468
A2BF0DD84C87E36C8A7D39500538FECCF76B03086065EBF38819530458E0D4B3ADF3C66C06
6A0651D3E8A84BBF6A4697C05DE066B112A8B6118977923DC3A01F43014B02C525663748B4F6
5E79 | +| $m_{p69}$ | F660B66151AC70269D9405C9A987C3FF25DFB65AEA14E5EB2A699BFA335AB16974D00112062
12F3A3FEA6F0A6971FB3C6F4D73A6D44543FF1FA0775D57D13AEF2E470177C55F1D823299B1
DCFE4CA851D7E9075CE9B8D6344B47354DA209DCE4EA6C0EB1F43ED231C04DBB510C68B2
D2F336 | +| $m_{p70}$ | 88C9890A01B550D44B635B0D4C01C20AEC17B0EA42389FFFB0D70386CC2BAD4D5A8E021A22
8BBD4059FD12854187F2F0DB1D6CF7AB654AEC2877D2B1A3A8C508CD9329A096F161B8DE72
866C2C99BB67024C9261A24AFCFAFF3A483E8D71BA7AD985E9DD0CEC2A4B31E088A7CCB7C4
F39CDC8 | +| $m_{p71}$ | 1309529E28E71D99D501350D9662F3BF5E3D54AC16408117F0083FBA22F1AAD9CC29552590B
051B725B81B56E33E36C72F8EEFDA5F3EEF4629885BF827E05A4B918B831FCFDAACC9656FC4
1D30FAC255D2C931D3E090897C3E75CCA520061DE330C60AFA9545148B27A1377300B064389
7976 | +| $m_{p72}$ | AAB7E27B83CD46F2EF18B91FFE9D9C69BB92327B0DDE3664C8974EF7BCBC77234772C02007
B344BB99DDF344F7E5A6C3CA3F01B0F28DCD566BE913C274F296F056A74CEDD7680CA7969
A34CD785597008543208DFC63DB6C847BD364BAFE11751515287B210554A5610D7035A374E02
43E72 | +| $m_{p73}$ | 7972CD5FFC6AF3780BB7A88BD4BF9799AC403D1976D8B4ABEAEF4888BF0C269C96572D81B3
BB55E33D30900CBEAAF1969F08E4EFC7CFE7F99DB9A184869DCB18A3D143AC725E46F01B11
EEF3940932A7AFA30E87E156428EA927872FB64CFD072106F00811359CB146C957C15C3E920
DA96B | +| $m_{p74}$ | D62ABF2E9F79492FD2A22FF60CAA94DBEC39C380F12290B133DE53F18B1914DB0555BF6AAF
47539337FDFAEADC58B320D67644408C4F5105F8907F2254731D319FC3CA221974D5E9006979B
CA2BD89C04F2D1E1FF2D4C51F3BBF2CA5BB2FE8FD34CF05AB45599BCD6DCE5C2BC53E114
A723DC | +| $m_{p75}$ | A0D97790B621153CF61E6DF09D07FABB17CD0EDFD030E300ADB777FE3569C35F747E4DD156
6196305DA32BDE5BF26E395D6836254BFF3DAC9FE2BBACC4A5900A14E2E72E0D4D05D09A7
A3BCF211D1E2F7E36CA379B52BC21D937BC628D6686F59171C5DC4A223D9AB1B8F89019FD
D50683ED | +| $m_{p76}$ | A133814EC7D9BA19C3BF38946484310280B2333E631F2A29137230EF8B8F9A30A958D8AEE03
A5578EA40ADC014AB6D8204C396AD7EAB3C17B1325D7D55FFE946525ADD5CBE28F3DA392D
8873C82C6CB6CB65760DB5B0D985786A7B04237C0D0C5F43C903E9CC3126AEBF3BC5CD434
9FE2602 | +| $m_{p77}$ | 89D74B62E35F853EC718FE7A32C7B39AFC27A41C87CA9BC76FF6640DA6ADADA997562B010
AA1841DB918E947989291BDCB50C9F40FFF623CCB0336FAAF878FD49BE092804AA73A3A419
07D5CD32A375C898373D93FCC4C9EA84A2DB9802521FD5376F9635EE1D0C3E8DC34849369A
757F5C | +| $m_{p78}$ | 2DDE87087BDB66B5DF7744CB16AE7164D2E5AA7B7B2CD8BB46C6A602DC9A108752DB6967F
1728B12FEEEB1FCB681DDC48ED7C1C3DA5536AD84CFD9F5E94E6148F4DD3D9CF3C830F3B
6401C8206B0ADF952AD505B96C74C615FC6F70381949B2E6E25F42D3E6563041FA5F501CAAA
A93C519D | +| $m_{p79}$ | ACD35DB85397D81E1124B62A60CE35E4E8214318527F96F273AB6718822971BA76448B3A6E66
2FAFF4D37BB2176934F80AFB3E03FF494AEE2F7C5B1D0B723E316AC0D67AE53A1C0637E155
729422E7F78F5FE19BB9DCF674D13157B2F8994C5DC03780B6EEC2AA0E57FB7F8A6FC0EC81
AF87 | +| $m_{p80}$ | 43FCF00452F2E93D9A4110003601467549D08A20E4DE27F025843FAE54D9E2E5820D890558C7
541FC771CDDECEA6648984D63183ADD8E5BA52F6E56956B6F1CBCD93374F34F4709DBB812
D155528403D364CA2E54BF1F6828FB342B3D378185A6E3E8572B2F28EF6AB194C184ACF4FC4
09FC | +| $m_{p81}$ | B130A5C2EC864C8FF71CFDC347DB4CEE38259F34A8F9CBD143763AA9DE869CA25E1A6A49D
7A6FE1DC029DB9076FB6F111351C6FDBF0D1C1DDE412B835FCF0B97ADEEE7AE09241C2FD6
20D63F894BB09E839021D4D81932BE52926A33AC9C81AB3D9586AD2E8AE53CFEDB55D43965
CA9EE422 | +| $m_{p82}$ | 7AE9E0D3F5D0295917B116C28DC20E9B305296A3FF02339C1BBA86CD3D566D0C8948839C2D
4751730DB66179EEDF5B04404B7D867219715C87F9A18408284F0C0894E1864A55596DB9851D
0DB68B8AF7EEBAC5C01DA3284E6B42F7FCE8877AF04713C98274FB93FC8C8D421B0B572B5
DD1F0 | +| $m_{p83}$ | 9737D9C29C179CA57976D04DF9597432A763D93B69B799EC14FFEF6F84A2F56EA0EAFD13FD
6D2C69462FFB551A58C17B06E32C59E605C34CA287EF8EA38F99C45D93A922C50B19FD02B1
30F5E704BF435A8998BE97F76181B64C56760D8A5B0043F290C1637783FBE77E9D113955431B
6F21 | +| $m_{p84}$ | 29FE9F4CB903F8BFFB5134A5D8A2B3D7A8936A3311BB1905D9ADBA1E3467AC5D3F5F6A7758
130E4445856422CE094D85B620611E7D8F5B3C0CF386490214FB6DED5CF761BD2BC87CBB0F | + +| Code ID | Basic Midamble Codes $m_p$ of length $P=912$ | +|---------|--------------------------------------------------------------------------------------| +| | 4171B566FA32761C9CF11147417F50C47BD1986AFB9EC129CDA74EB0947C06B935F5A175D22
E2E35 | + +| Code ID | Basic Midamble Codes $m_p$ of length $P=912$ | +|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $m_{p85}$ | 50D3795F988F865B3A9739FB23047D301913B7BDA5F87D0A3EAC478002A20C571D553EA1903
93D404E1718BDE3C780D26BC9FB48EB555A9228C323036F000CEC60AF43E23F734B104A4998
B4662D1770B46B1643EE6A9B4D8D9308F4410821FDB39403652D53952D5CDE7903BEB66FDA2
596 | +| $m_{p86}$ | F84F4D2894AFF4B26CF0FB72DE03D5C43D98F7A13C95FCAFA16D9AD2DEE38EBA7CE7CCD5
1F02DDEA932436451B6AF185E2C27173FC5DC4D5217E0451F4864933F7D829691994CD982D
2D7D7B302333F13CAE7DAF6EC9E67188955207AC461AC2AC124FF94ABD2705560E5DCFC6F9
8C8AF0E | +| $m_{p87}$ | 058C6EE106A2DCE93EF5220D1BDFDF725CBC4DB869698A72F89A886AD38A0F42ABEDC4966
FADF33AD0C39388055421F2D4D22FF5E698C4B1F002633C051582D899A9CC51973000BC3D43
E64BB0E080F392DAA65ED11D081DB55BAA3AE3EF2B5B135136E2BBBF81F17A926D9293233C
08F58A | +| $m_{p88}$ | 600EE81F7C9864F1B8C7337A7C1582B1A038B8461F5381276E514C27A86B1C96F61A3DFC489
0023AA73A8F8FAD7750B3A632BF745881704C91198D40F0C6DE51293656203E4545EC660659E
FDE97CB52C4540AD7E6942B475BF5C8C2047E38E3F79731AB972F64B519B4DF44BF25254FB2
8A | +| $m_{p89}$ | FDDF8C811955AA732713A5973F621C8A763E4057047D3CE2791D20A49250C5BCAB0FC702FA6
563274372D03275D6B3FDFB4E981D7D35A7EEA2D99F607E88CB38D7D4B35A40934EA67B3EC
9E7FE2ABFED68969E0534FC6720346D8C07CDEFC5173554F14E05BD81DCA647C355AB8379B
EE206 | +| $m_{p90}$ | 62451F8749EFD5DCF5729A3D5BF4AB67A5854398C8D6A2CCB07F2BE0D676221F764716E0A
EF70515873645A9F438C1250072FA65A167AEB30CF099AFC2C2504E129D7FF2BDB28B78A36A
0D621F74FDD36D5EEC9BC4625EFEC4AF6CDCDC496B747134E6D94D87F7141481DEEB83B84
1C0E33 | +| $m_{p91}$ | F8DF107B028097DB928CF7A03F0157BC3B50EACC30063934EE28413D7764CDDA46D17EF91C
A7205516B76933B3D50D385D871357AEFA2E34D1E3E929FCD08B940AD54762D21B73B0C144
C4C2309A26AD3EBEDBDBDCBB0B1A49AF796DC5D8F62F479A6CC739D6B391D97C39FA017E
F2D85855 | +| $m_{p92}$ | A45FCBE0688A55D051B057C34508507010F607661BA244DB1A7CE599CB4ABC6F3575A765E41
C2EB8B5BC49E61162478CEB07461787BOEB6AD14CEAC878DC9257E48418C2F3292BD087FF3
B4CB7758B00BC5380427E620776FFF7128254CAEF743129B317B8C21D0ED02B3B94785048B3
B274 | +| $m_{p93}$ | 432250D31BCDC883439F92FFA76470DE1B6689465A0FBD3A12AB4D165012AB32B7EDEBC859
68CB1BA84C24321CDDCAADB0175DC6C2FE2EBA78EB788E049F8ED34A3AF1F42519957C748
96872C3BC6C0A7A210E8438EC84085A3C4E3884E8B79AA57F85937D815C493C044B80519F76
EAC075 | +| $m_{p94}$ | 4E3834426643F2C419007C48053C6B7AEA54D231D68631D5CE305FC33C155405B2566ADF0BC
3E4D70B498B3CB2981425D610559C2EB63213F07AAF3E240653230436ABF9D823799A05D78D
4D5A45A67F6637C9D9A4BEF410BC0290BCFB47E206A64FB6EADA1CCFC9B77023EC705670A
9439C | +| $m_{p95}$ | B655DDE80717690057C86FB8C2F94A922D4965624E527B42C080EDC3114472B5D58E3076EE6
06A6513515FF6FE1F5C6CC4F6A34AD865C7EAF03558BDDA4A96A838B1D13543B87E382A4C
EC3383E4F2EC960D9707CC52624905326B32B0F6C8F3CB3FE7D912B8040518E61C0C1D0BE6
135F4 | +| $m_{p96}$ | D3817A6FD2936F4738A55F19CFBD1EE3801CB86F9B9656D39BB4CCE5EC930CB801BA371A05
876F63F2A9919BF8E769F140338176169439309841D43FC304EED8D80164D2EFABDE83DBBAE
A927748597DC553E6A2EC52E3D7340FFBEAF817484A7558B59753BD8661596C940CA6F16570
D6F3 | +| $m_{p97}$ | OCCD1503DBC6DB746E369372930B18BEC1C972C30D3BAC9547590AA432AA5280492851CF89
35F74A5431E97169A3322586719FD703B122B70A0394D784A010D6B9BCA2A9C7284B8368127F
2C00BB31CFC8EC1B3A31EF6EE148114BC0867C1182A742FA26A2EF1F62F948762C3FC6DF7E
1E4C | +| $m_{p98}$ | 68AD9382C2FB0471F415D72240613B24F019FD981423501796E76898F2D423801EA8321E01CF
EB9DCE4AADE7CBDF0C10F94F98E6C9A561204D4051487E5326173030FBE760C28D8BE6815F
CE78805E9C55CF7994AC8482B6A13254CE7FD3ACCD6D96CC35913962F57965D2BA905D50F4
F7F4 | +| $m_{p99}$ | 965AD6AFCF7A822E2D0A7F3F8B23BDD9DA7667882789C85A010B0CD095E2BD43919DD6BC
8F290FD5FB7B1F0A4F8C47C348EEC37F483875721352856568DFCFC16AA1168E1D948E9861A
5E693AA0AC4F26225CC888DF6F326DF4D5014C892ED9A6A8E99C4140BAF7C03873532F0CB1
EDB7EF | +| $m_{p100}$ | 11514B31D4E01ABB0202CD8B26B4F3610886058BA519EF4C9701EDF8ED2E935F65AFC454C0
B672B14B06672BB742640EA5BDBDA47FA5F87BE583F65331E2A30CD850B4619637DD7B84646
06F10236714131E1D2AB4EC55654D05A93050E6F8748B4DC83C6202B7FD63CA1FC0EA00DBD
48538 | +| $m_{p101}$ | F6FE8BDAEBB7FAA334EC95ADC619F8A04171707C84C79A7C96F973392176EB7AC5626FB24D
0F88EE8D5FC99DA5F03C381A93ED455B13DAAA4DA3EF7A092D114316F6D25F319473BFA8EF | + +| Code ID | Basic Midamble Codes $m_p$ of length $P=912$ | +|---------|--------------------------------------------------------------------------------------| +| | 025438B0A510DB7F4E8436A38B16606150D2B35B2872DC206AFB17732FD16219BA58CBA1CE4
02B9A | + +| Code ID | Basic Midamble Codes $m_p$ of length $P=912$ | +|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| $m_{P102}$ | 912FF3C82D2B7FDA4703DAE6E349E1844212B4672DB02A4D0D4465220C1A4CF0E7D56C945A
DA538D465A76C7DC3AE272BCBBAA4FB9D9925EC41FAE0735380C1126E36EBEE55270F99A0
D851FEB280B103E3F51080B99496B2E3027F6EC16D91EF42C58E4089AAE68CE075D323C4A2
D409CE0 | +| $m_{P103}$ | 4789D7468124CE0AB731772154704A07BDD14C319DAA60E9E3B55E30D61616301AC560BB31B
6341FA629F630204D057A74B8226EDE4A4696159DF3BC7DC3597072A1A95464142AF23103CB7
C28AA69A7D2CB990967427F9EADF3EB65FB95DD72CEA804DEEE0924307794D99FF406F0AC4
0F6 | +| $m_{P104}$ | 9A5C8700EF68EFCF28CD6552C267515F58593EA84FD48BB5D63EA028DA77F92787FECA4FED
AAC04591502198A10725B62AA7361C932B58C6F4D431103A56AF5A8400E8DE5AD26788F28526
387908EE52B030B639DEBA260A321B09BD60E7BF3C54E1D8264A04B0F65D81F9473622CC05C
3AC | +| $m_{P105}$ | 9F6A2D1D54D09A6A3AF7BF514DC754301A164602D531807186D9930FCFAF112D40F72D17DC
E9C40E9EEE8FD2E5D1D3BA4543ED609DAF163CED9BD0074D3E5F7E17F5AC7B4FC4CA0690
977DA3533AFDBA5BD328BA079BF2335364035D68673B98330B92AF5E3C26A9AB596986EFE96
65219F8 | +| $m_{P106}$ | FFEDAA9F3DC1F267C121D6303743286B1AB1094A1790B58B1E4DDA9D16303A3289BC4440987
775D6491383589C96181AE093289D42230FD88BA098F3575FC393246726C9EAF6955EF135EF
07E862915734A5994D2CA7301FE844DE7B4BA9417CF10045BEF5F4D4C5BC044A347E5C9E998
21 | +| $m_{P107}$ | 644CA39E3F93C4AC795EFCF5B8BD90228E2638BAE24CF4C3DE75697823DF4AEDD3253E980
81C4BD215DC64A9E6BC0115027F6BA4E4FE2A93FC726DBA4D9D21DACDBC76B45377B68863
F9FD426E4F89625657EF97C03D277C373E15D21EB721AFEAD246ADF1A0A2A0CEA730BCA98
CDD4CB808 | +| $m_{P108}$ | AF16DD60C5458A3D27E36850281E401B10116D5B0BCEA1B159C97487584652047981333D5573
686F4C0A063E1186306FD02DEFE2C61722C5BBED60249AA2D9260ACDF870B3B5F5CFD75815
80DE486D8D9F332A6C6B6464AB0E9D54159CCCD03D6F9CA12C13DE34145B34FA40703FDC7
6AEE7 | +| $m_{P109}$ | 33FC7C9D9FF74A2FF009240C3AF398937D078012219BA54C6B0B0D9448391CD1D4017CBDB5
4AA59355EF05A9712779D71761D96F650EE10546C39694938AEE89F7CE6FCCF4BF987D0E9DD
584992F2732D5838A92E537559EDE2FCEE82302D7FD8B1C9CF8215B67BE61D4EF4523EF9032
B1E2 | +| $m_{P110}$ | DDAC8DB73BF5A8FD9A74561DE805959C2ADC755274740993616B3771D10C6F5B0B8E4939A4
44F280B39CFD29EA0F562FEE0405451D8D9DAEF8B1E0C8D69CBEDD6D23D8A56A3A9B87B
D6EDE46FBCCC135D70B8FD4619C35F9A72E93E8954FA787B8452347E4B209013736D0EC059
A243803B | +| $m_{P111}$ | 516913696CB4D961C939529F64585F08C42D1FD1DCDC78F16DFD5BCE287434ED251FA1AABF
676006D75FC455DDE30C8840BE6AEAD10F8A12C641800C35B8CECC9BB54037AB1075190EE3
D2D8D81F675898FC442A57B3A7B18B0AF90528DA8019245182E920B926AE569D656E3BB03A9
75CD9 | +| $m_{P112}$ | B2419222199441C48BB085E7982DCFC0FAEB16D39DBFD22270AB8EA6A802DF3580ED6A68A9
0E3AF03281B48ED3FAA2DC45371E3733539E70B137ED82D5A2CCC2031BE3D6A4786EE9D9A9
153658EA0B483EDD49F9D1E189F3D418B73825CAF3B4D05A805F80FCCC5949704252390DD3
E86EF6 | +| $m_{P113}$ | 04D96F94A767AB70BE85D6EBFF3831E2825595CAF1583CAF2B75010816DF65757F4BB4BC58E
011FC5CC50F220EC72ABF672E8C9A29821D4A106603187276492C366618C68CECF60AA6D4B4
F03505EE0BEB591336E130EF4593C5C11749CC3D2974B1AACD0DF19672F9330457241E201DB
7CC | +| $m_{P114}$ | 12CE52D22E8BDFC665F49D86AC6C488C9012088FA091E5EE13B7C45A9A5CB156F147D6ACB
FF87C4817350AD15C5FC3773F3C58FD0D3B88242CC46DD43A5288933ABE5A6055FD67B1159
3C900A9654D82BE40200E38C7A9643BF25419861A2D674B84995301121FB34389CC5AC83E94
CCC738 | +| $m_{P115}$ | 3831B0AED8C54E6F5F348C22351E35AB1099C47149117A40521B30D005DB13A81337A7EF75B
0A6FDEE2012E394935C2D61C0BAED3B65D4FC768C30F654E97BD33A54F49A2753915CAA137
F8B99861872F00F6C019DA1A2727E1FD648608CC108EFA2D85490980F7570C37619D5F4785E
A45 | +| $m_{P116}$ | 2D7BDCD4C93F3175F441994A9B188976A7F4F714A80AF693139FBB757C1D0D71274167EEF2C
36F891612ABF8B3504FB2A1F0BC1DF24186A6C2B79A4EF118F67FF477AFD650F6BD208599D3
31C3B5ECFBD173C25D7CBB9A0C9D4E0F455509A8BEFD805201429E3192D82477E4E85D606C
53AC | +| $m_{P117}$ | 01E085F900F58E7769F8C8A24DCA26984EE56F2D8CF0A0726508094A20ACAEF0703351EBF8E
DDC1C59012F9A3032B11D5BB260FAD321280BE48642CE84C0D3681E57784332A87DA3C06C2
CCF0993A6EC2BE1A979414EFADEEF3CEC8E12C41F55DE52D48F0B851EA968C159B9CB2D51
4CF4C5 | +| $m_{P118}$ | 32814E789480CDAF8D0E09BF65DC4863B99B8542F0693D77ADAF6F32D0173110789E26F1BB8
F9A8A71D09DAB03FD52935945D7A4EC68C8B043B27AA81200CCA1DA23A9833217CFCAB5D6 | + +| Code ID | Basic Midamble Codes $m_p$ of length $P=912$ | +|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 2E0C488EA2DA2C73DB031F205D7F960E9D8918A5C652C1501EE93204D273464BEF438A94DF4496AE | +| $m_{P119}$ | 15DD44EF0204B908795A090C32188643FBE7366EBF30DADCFB2C41953A854FEE39EAA7E9E4E58E30B45409B72AD05B43BAE11095FB1D20FB2A73E04448DEC973926BD7BA0EC291A29AA7EBDA5783A2A253649F036962A0E4525A07C66653394116352439A2520891F8E18D2CD360FFE0B111 | +| $m_{P120}$ | 89217691E99FDDDE0598092D7413C6946390C718299455B5B455CFDE3E2E15CAE056389BE60C836B500053044568990C9EE40582F6978F91EE5ABD501408EFD805F4F64FCE2FAA5607976AC016633E12FED435EDC627548B79898DE3B5FA8B246196CB2F4289A0E3FBC7A4A911274D4CCC980 | +| $m_{P121}$ | B3047C6EC9C960702C122202B7BA48D54A1015C1F9CA22D879FF5435C6EF930FC5EF8FD8113B48BE47D794B87E5194F8E7B4525B4CEE45FF5D0D70CCC00C67496943EBDC878DE4F9BC8849A24CFB05282B117F140A4B1967B8F4E38A0637A4E8C916914CFAC15D399174B1AA65C86DA472EA | +| $m_{P122}$ | CED19A2B452FB08A4E677AE137AD75601BD7824CE59E4FA627A3C5AD101920FFD89328B3A917782F05781BA0292EEB18193BC1C3C02B48D272D449F381CA20B12B1C27A480C628A33AC472F2EBEEB775D3D3681A365C728DB9476CBF8744D84448FC6303BDD28BC38413277F6B61CCD4A913 | +| $m_{P123}$ | EA7FD3D0732484865089964AFD0181F0A64E0B9BF58C20C3F34D45739C01ECDD11681E3B4D175D237A19C2800C8024FB7D3A14DDDA53180B10E8F1C569DD9CE06FF19EC958989AE43ED26E96DCA2E954BCBB6EB502F0C269EA75F5CF002BF49B383A00159C0D39AC71D502B557163616B66E | +| $m_{P124}$ | D08DC6EE2CB2EB2D3890230CF7411F51F71024C8F05CDA7F958CBCB81B12C0CF27342431CCD1BBF61DEF50298E87ECB4A98C489D3CABDB55CE95EEAFF850BA13C0F772CD9F2943F961227078A05FA3AEE18E61657D04AA37B7F98BF5B6DDEF0F87ACAA5B4D1D2CE0622DF6B8816EFAA2F448 | +| $m_{P125}$ | 70C1FC8BAE04C07CD256269A02056B79CD0014D188197B4BE89AF8A460026EA8FBC7C13A7793F2822A94A4A7234727516D44A5BA521E3E28C34396C69BEC8233FD0D82FA8D5B2C4F12F9284962A6F19C2E655AC44BA85F064E8D134F28F9EC479FDBFBA74223466D185CA34C7188C6E7E515 | +| $m_{P126}$ | 82323B03B81937932EF44D0BB2A22DF5F8803080618940A4F1DED2778230FBE3D04545B86B1AAC4AFD43A90DA09148456DD81684F7C143C48C710076ED7A60BD6128BB9C4717DB97331CFB667E9EC1D4B03191B3A218B12CC957A3F5182A452694FDE1A4241B1410DD104BE1551F1E85F8A5 | +| $m_{P127}$ | BE616513AE32C4143C92A7CECDB56F082F7907098FF61403161D95CA3767AAF7F46A8D60D66C6195D27F25FC5D0D840F7DDDD67A3E492FD9FB85A805CA0438F822BDE583BC11B74C760ED2FBC9DAC6F361EDF71B17B96B065D5E2E43A9A87A7CD561FC8F4BC809F474D68E6C4B6A7542065A | + +## AB.2 Basic Midamble Codes for Burst Type 2 + +In the case of burst type 2 (see subclause 5B.3.2) the midamble has a length of $L_m=512$ , which corresponds to: + +$$K'=8; W=57; P=456.$$ + +Depending on the possible delay spread cells are configured to use $K_{\text{cell}}$ midambles which are generated from the Basic Midamble Codes of length $P$ defined in Annex A.1. + +- for $k=1,2,\dots,K'$ , only, or +- for odd $k=1,3,5,\dots,\leq K'$ , only. + +## AB.2A Basic Midamble Codes for Burst Type 4 + +In the case of burst type 4 (see subclause 5B.3.2.3A) the midamble has a length of $L_m=640$ , which corresponds to: + +$$K=K'=1; W=256; P=384.$$ + +Thus for burst type 4, $K_{\text{cell}}$ shall have a value of 1 and the midamble is generated from the Basic Midamble Codes (see table AB.2). + +The mapping of these Basic Midamble Codes to Cell Parameters is shown in TS 25.223. + +**Table AB.2: Basic Midamble Codes $m_p$ according to equation (5) from subclause 5B.3.3 for the case of burst type 4** + +| Code ID | Basic Midamble Codes $m_p$ of length $P=384$ | +|-----------|---------------------------------------------------------------------------------------------------| +| $m_{p0}$ | A88E403803494ACD25F9E40A2DCDD572F13461ABE91E3931AE9BAA94CB6250B33216EC49AE028C3BBC10389C97F8652F | +| $m_{p1}$ | CC81718FE2E076D4CF6787847831AAD28E7B131136D8F6BA65B6F32240918434A3F445405562FB1449F10E152DAF8E57 | +| $m_{p2}$ | F40249685685DC493F2F7B8FA91E3373C9CC902C0BD54963EB4661355AE6F0CAA345E3043FD5943520360E136708D755 | +| $m_{p3}$ | 7699416BBFC40E597656AB7B319EBEA4B6B898BA357DC20BF01A36A2FCBBC1191012836E532F0F16EDF1B1CEF8C8B8CF | +| $m_{p4}$ | FAEFD4A1EAB45332B43D34DD877032192973A4D6F3DF1394E26FCB2FE608A777FBACAFB87B8598AFEC0387456274D828 | +| $m_{p5}$ | D7E24FEBBDDEE2558FD4B77BE0F9C79D86192A829A93A8B8B4D93322B1ED2C5D8408D9F64E75390B7FA9E471EE94503C8 | +| $m_{p6}$ | 419C96CBF5D07CF7E8CA5F0F768F635EDB2AC91013955685FC464F533BC0A7258D1F820E79FB4E3D64AAC88DCDBB3089 | +| $m_{p7}$ | E3A9C7C56BD042B22E63B7A593F95A82FF67F59F50DF76D419022A69C986F86F98C0D3981B3297BA8844BB0E9CFD7C81 | +| $m_{p8}$ | 6D15CF45BA384523320B323033CAD89B6738F7AB22D252DC51AE9EE06F290819C6BE3F7F9A07DE5BB70E57E8F878BDE4 | +| $m_{p9}$ | D8EEF2FB18D658B7C0BB3A1186FCCB4F5EFC5768F6989946D7858A678EE850D90BBF2520B92A7131143B9F7EB9F92E8A | +| $m_{p10}$ | 13C613CF8AB1ADBB998FA7E415710C87FB2C4C64B040E153FD2A8FD05DB395B4BC4BBF5611855AD3F354DB99F1A7364C | +| $m_{p11}$ | 64B93D117F33C1FB4BDCF82823C977CD7F749512ED50B51D9399EEDEADDF57C39B1EEFD1823272C26121F74967803ADD4 | +| $m_{p12}$ | E9757EF85FFC178DD991A01C81AE8A36E47B1450E6DA60C96967E798E47B43C3BABE4AE7FEF186B305E6AEDDC8D0A4A2 | +| $m_{p13}$ | D83562B863CAECEB41458179A04E4D90DA7B6F15C627A81480ACF210A3403E7E60506E859665EB6AE94BB2079988DBCF | +| $m_{p14}$ | 54D018301703F6E38A1DB4496DB91650AA4715A51D4D1807401CEC4AFEB6368B9AD50A15FB7238935963FB0987671C8 | +| $m_{p15}$ | 20176660D98A8C4D0442BDF1F0EE3FB4D1684B7A93684FA4395B784D1CA8838A238F28AFE9003C4D3EC0562C5E79DEA6 | +| $m_{p16}$ | C5771FEDE124CE07C75F48321D8B0EEF34275CFFDD49F7D59685CCA298D09D36A558C903E2EE5C74A20EB02E50FFBF9A | +| $m_{p17}$ | 7B2AD0AA898419CE863FA812CF47B32F369C9A404A936648F0DBBFBF521E822635E7A87B17C138E2357E957737F4D67F | +| $m_{p18}$ | 0005E4C456A52687FB8C38217E39A6CBCD18EC8AC6951F7482CC19BACE70BA1E6E116AA6A5780F656C72B49EAFCD0312 | +| $m_{p19}$ | F7561674AA43738CC1EFE9434061CF17B8FC55792BFFBEEA2B61F5E1A46BB14B19926DC98BD4B747166044BC0F652693 | +| $m_{p20}$ | C1F98B595BFB89F7F40B1D84965981E7035455112C337DA389E04D8146B6F40D83352895247E53142A8D7BF7063A0E88 | +| $m_{p21}$ | 2374B1EB35DE57B4114DA547D25C39887663800D53E7C0A4A8A97525E7E364FA011B23A113A4C1067763DA770E58CAEC | +| $m_{p22}$ | D3E5382DF383595C983C2CC2369703A5867C84AB2EBD9C72044EDD8CD5683BDF4CDF10ED04D4DEB1D3D459020247A206 | +| $m_{p23}$ | 7344E4A74618745A817E7036FF6535629AF647E852129F6F70887CEAA8393DC859725FC7BD52CDF241B31FA7BEDF9BD4 | +| $m_{p24}$ | E1EAA999935A9C04CE360B3077241EF63FE1103A3C15AFB1CFB7AEFB93CCD5357B0068E70F28EDA990B6906AAFFA4D2 | +| $m_{p25}$ | 39BF69ED889CD875DA83108FEF691ACD1FFAD5B5E76218318EB45DEAB2022D82455B592C1FC550FE197165A07E346D5D | +| $m_{p26}$ | B817C216E9A0A224D8E5A4DF3F68D53BBB89B156261C5FD877FA96352A073B6B0E53BCF0765093DB7AF0C6E13AD98BE8 | +| $m_{p27}$ | 075DCFDE008B110F56C59A61219770846DAA58B896D4914047EF786F03E13F985B03BBE4FB3B352A19548163C5144B69 | +| $m_{p28}$ | 913AFDAD21CDAB1D363C8FFEE158E9EB5EB699D54DE5E65770A963D349744BC935C4ED0C49903CFA0F13EEFEE3BDD511 | +| $m_{p29}$ | B6C348E72A210714B90035C905F22D6777849F28C0922E3356DF84F655896C2E8E8DAD0C1AABD7CC81633CEA68E8AC47 | +| $m_{p30}$ | 51813E8CB9F2259B52C62FA1955034D0BD52B39C108EC46D3AFF6F8F8C3BDD1ACB3725345CE83C0AD7DCDBEC4547FC96 | +| $m_{p31}$ | CD1DDE061856436714BEDDE2EE9DE7A9A2D795125FBE023A13AE1DE727EAF0B6265AAD72BA3BF4C40C82996F486A50EE | +| $m_{p32}$ | 1690CBF556A6D9268773D5840033E9DF832FFBE2BD0F09D93DFC18E92340EF9CFD11BB6331 | + +| Code ID | Basic Midamble Codes $m_p$ of length $P=384$ | +|---------|----------------------------------------------| +| | D7D572D7D17CECAC6D2D23 | + +| Code ID | Basic Midamble Codes $m_p$ of length $P=384$ | +|-----------|-------------------------------------------------------------------------------------------------------| +| $m_{p33}$ | 244048BA6D32A3793E12532E670BAA42EE28BF58116F67B9EDD184E1861476D928447A874A1
EB0A6A43F1760EB19B83C | +| $m_{p34}$ | 81FE8B4F56FC4BCB5E1366CF41E6C559FC109846FFF538636862AA52A5F12E1F974B656D381
1C882A30D56CF2775E473 | +| $m_{p35}$ | 921F5B3F5FC92ECE95B09141BAFC214696D1E534E711856E327FD1D8823D4854C510E6C381B
ABC0B29C600B193F9130A | +| $m_{p36}$ | 50A3DF0CC1B0A1BB8573F7F973106FBC94504D86DFDA067C119072D8745FA8D6A263D07DAD
DA3723ADB439BDE5DB539E | +| $m_{p37}$ | C3C0412A03C79A6A77AE17DFD4C56963BB56550C3745C9A5DF8E68855CCB60290CDC0F314E
260AFF330194A62CD4DB44 | +| $m_{p38}$ | 66B2C238B87005022F58273FA04E2C590C6D710ADE4549E735E99E17D1170A1244AED82D51
465FF3FB6416C179C246C | +| $m_{p39}$ | CC0D235E5D80947EB754EFC63F6EECA6F0B9D9197C24C7A14CD72CAAB26A8F5386A231B77
A3AE0D204369C57DF0D8E6B | +| $m_{p40}$ | 6CBC1D14CFB4B14362940B67BFFE9B3C333F1DD8A97D9F947292EC91A3D01BE0FCED3529F
78AFA2A2F74213B87218E6C | +| $m_{p41}$ | C3119C5FF33FC2CB957EBB2E9B993A85BD70BB99E3A6CDA07E4343ED282293A5F4E7F9C9E
D356B322C38259FE10EEFD4 | +| $m_{p42}$ | B684A2F64D90CAB23140481057AED62E36315FD5759ED05747E4A149E784C78C52FC09EF812
32BD1C1647C95CE10CCC3 | +| $m_{p43}$ | A70B5E173176C74A6CD11BA10D026B8C86BB44814CD7C27C0A03137CAB8725AF6CE05F7A6B
2BA9BCFB1072A8152843A6 | +| $m_{p44}$ | 9257486C5A5AEA7B21B9D736FA20C34C22AA3FBC1EC9B66CAB8F8625DE7F4522DDFD8D7A5
22F6AC31AD7B03463310C1E | +| $m_{p45}$ | 1FAEF03FD59EC8BF1FA57595018F1F7EF9F4517CD0F1AC5B82FED8877AD34E7333F06C3D5B
CB359B2B2B1084036664A51 | +| $m_{p46}$ | F838C88284898DDA2EBE40972DA884AFE7912367CBCF5453894E639EA54A053653E888038530
BC516737C43786A5F2C0 | +| $m_{p47}$ | 1171FDDE14B8A432BAA6401868CEA05A02572C83FFA26E16444B0AD21C67B3F190D9C3A61C
3F123523266BD232BC4BB5 | +| $m_{p48}$ | 6055579BEFD3E751073BE2EF913BE962643CA37C14A172E607C7A8A8C57B521D34B121ACF6
AFE419DC7E4DE665239251 | +| $m_{p49}$ | 5D9DA3875FF37C084F7917873538EB73E66B62B74B82EF127855AAF990DF7D2D06FEFB33168
1846B928BDE429E01551C | +| $m_{p50}$ | 24A63008BB9355A32892C8BB5F50D6B1B0007563BB7E2526DF1C9D4C2439630E9EA3E8FC6FF
A34E297324EF00AD1D063 | +| $m_{p51}$ | 2E64310629FBDD2F27B3487A7882789B23B833273D1E7AF4E7DF99E26555DA45AAA7BAD244F
A71B00B6155C0CA50EFE9 | +| $m_{p52}$ | E47949C3577D92C3635CB7A96E8D63A778815DB1324053579BA12560B46E7EF7B935183E3DE
0A79FE88FF857B90DF2A8 | +| $m_{p53}$ | D11CD2FCD449E3504A3CB8A92650B9376A927F882231507D9FC7A851AF31AD0977E1DBD594
52532C0E841E82501CF8B1 | +| $m_{p54}$ | D9173DEB459627122EB6F6E27B11FFFF944AD65E9F2729FD0F340486AA4F2E58CA7647C25DE
C30FF55530922C46314F9 | +| $m_{p55}$ | 70ED8ABA76E26BC7C9E8748930944691EC16B7F70204273306D10824DA33E8A2EF190FA80E
D616212F2926A8457C7DC | +| $m_{p56}$ | D7CB3386C837EF00E8E56C07A3620AA239E182929956B9423B364E3117D2E6165EDE6FAF13A
009C4304AF6F3A5154ECA | +| $m_{p57}$ | E1671C07DDCF6CF5DF9A9E0CD9E6FE5C56E21CBF48028EEF2DC57993E44A46C1D32B0DAF
DA39695EEB5D8AE603315355 | +| $m_{p58}$ | 036B1806C6F2E9C263C0470BCDE197D43C8B9A2046A26B8FDAAC49FFA1E6096A7E87229574
A67B7BB7FBBEB9754A7EDB | +| $m_{p59}$ | BE3B978749D105923F6B5D8FB00F96D7C9B6C50989513D7197FE2C5DF74BEF6B328B9E884C6
BF848A9C57D0C42613CE5 | +| $m_{p60}$ | 54195927E67F3D1A28EA929625B6FD934EBF60662A37D64B2BCCFD8A3C806E5EDEBE9BCFC
37F7EEA5026E071C2F10CEB | +| $m_{p61}$ | 088C7E3F08322F71C5234A2DC35A19E385FE21BEE0CC9C2E6DF7E9F4BE424B86A583F64A9C
EABA6FE76E0A9D9DAC9545 | +| $m_{p62}$ | 2BD321E1A7ABFAAC6CF26EE71D2EC4373C05FA907BFDD3C929446FCE9714F98A89A0F41260
E658C8BDEEA291EDF5ED3F | +| $m_{p63}$ | 0CACCF6119FFB876DC319D3F95AB34899FEA7DA7C264A8B897087F5D58776F4978D9F4A8DF
40E0858655C82E7974F3C0 | +| $m_{p64}$ | 370B1A0FA2DA6E5F8B79D567C59404BB5DCF7584C3193BD37CBF1CFE465FC28EF6F15634E4
6B7620CC3AFE5482ADCD40 | +| $m_{p65}$ | C4EF59CE4C46245B85E50AAEBDA987F51614860DBF05A0BF66706D08B2CBEF9306A9A3A811 | + +| Code ID | Basic Midamble Codes $m_p$ of length $P=384$ | +|---------|----------------------------------------------| +| | 7682CD40A02C394DA8563B | + +| Code ID | Basic Midamble Codes $m_p$ of length $P=384$ | +|-----------|---------------------------------------------------------------------------------------------------| +| $m_{P66}$ | 3C77FF11EA6861254F844E393C6D8856939780A8A1F86148AE88E8C09320627CE6176936FF96ED6642AE7E33A82C5599 | +| $m_{P67}$ | A5AD10EFCF9DE41D6436B38590FFF5C582B9AA60ED65FE5596DE566CED7E8E41C11156B5418926875F06DBA319CCDA1A | +| $m_{P68}$ | 82B543431DDF83D2647C3778A41BCAD41295CDDD0A496D133E2F5F4577582F7D377AB993CF18516298EADFB3BE01AE7B | +| $m_{P69}$ | 027F6793D64483CF5569FEF03190B2190CD0A210AAED5C13D8A726433660F8095A6A46715276050C77B2FBA0DCF5A3C5 | +| $m_{P70}$ | B37EECA1A844DA19736EF3C5FDC6E3571BC7E04FB0A1E2522D1A39E21A0BF2D1D066BB9C0B99F6CA0D3A82FB7561272E | +| $m_{P71}$ | AB07BD3A4F83028263156FF5E307FD5D253689D76A8AE789691F339258EE9BD1EED8DF3C3E625E325B28A96A467FA181 | +| $m_{P72}$ | 2A7DA74C4C39B7BEE0CFC2C9F22E00910EC527B3515F486A767FD63B4C72C24F87EEAA337E3357B868D6B88C6A19FE2D | +| $m_{P73}$ | 21008CAA6C91705013C5753F1400B994BB1F197327B09D0E7DC7DA0A6436DEB19835E26A949051EF75DAE4BF7864250F | +| $m_{P74}$ | 3CB53B21CF1908B000B5675EA9FDC8DD3501FD7C5CB77A3C48C6EDA3F4D6133E9EC68374E708978B296CCD708C75DFDA | +| $m_{P75}$ | 6F9CF0F9C735DAEEE85F6EEB096A163D18DFB7D165F2A9BBECBE152C8CEEBFA32CEA5816A4966469DDC92CC095728360 | +| $m_{P76}$ | 597EC8A534D095769B15D0337343CCDCA78E696E9C7F18E7BE1C4C474FCFFCBA2E4EB257C04012BD7094ABAC47842FB5 | +| $m_{P77}$ | 333D73827842A2203FEB548072C28C290492A2B355EDD78C1B65E0ED270680E67B98929EE5C89743A78FC342CCD00AFE | +| $m_{P78}$ | 5BF3C14AB0643D1DBAE821BACFFD1A47A6FE901F2338162624331AFC25A2A66E38EA958114398D13E4FB4699A4051AC2 | +| $m_{P79}$ | C99275C3D2108C1C9BAFD62AD68C51DC57ACBBE8B263A18868F4A1A89823C914FE19C85B4163B4B10177A2B0513FBC2C | +| $m_{P80}$ | 4C66765966E60CB0B1D25566FFD085EBE34571B31C820D42F30A53BA4BB2C3C220DB0B717C7D3961DED7902B25FFF67D | +| $m_{P81}$ | 1602E7FB6ADDE8FE385D43E33322D734D8E7B920CFAD9F71ACAD855C71A57B8B40CEC5ACA32E073B642E070B6A6A2AC | +| $m_{P82}$ | 5B43BD325ECE4E2DFAE4DB8C861F5A7445897406EBCC625E075184D18440B395DC4EDABBC20E29518A41F7F1652003A9 | +| $m_{P83}$ | 3FF81A8A1493C202BB1062C49D88395F74DAF53A69BA63896571383099CA5F8B915E0670867C61EC8A794FAAC0A44A17 | +| $m_{P84}$ | FF8DBBA2E6C93F02CA775F8510E975E825AF2F43D3818746BB4BF930D54E84EF5E34B447CC375DE50CF61436C62DDDDCD | +| $m_{P85}$ | 40D95EFAD7A7D2B1E00839BD4892ADB5CD1F93B8BAF7CFE528BAB563AF711CE5A6A4C1C9019FC705FE07A8364B9BC866 | +| $m_{P86}$ | 531F4E313FB8FAF0B40B70B65DD7414C4CD9028D34CE27730690B5BF05FA3C7E5F0FDE11AEA05A450BB358433FFABAF3 | +| $m_{P87}$ | A2FF0392249EB69A3EE41A07D50AAB42B1786988D5C3569D31238B86320529825A03432995CCF599561A6E728C1077FE | +| $m_{P88}$ | 6FDB10A9B40B83D1D5335E99DFDCA540CB0AF54157145634F60AD3690EDED4688BFFBB1C36F38D95ECAFFC363D1C32DC | +| $m_{P89}$ | 92E6BBCDAD4D50572520D0FA4D6957A844180CE6B56814CDAC0D01FCD45973860CCF95D0438D2E99740EB6247F362BBF | +| $m_{P90}$ | 64F199A6673EEBEE362837001ED5CB04C787CA34B5812D1EB9ACDFC26BD8CF7D6837A3E175776E47EA7BA8A185BAEE02 | +| $m_{P91}$ | 677B0CDD0AA2362F9FE396A86105F98DF40DA2F6F9056BEC59D4F58FDF9F8B3C96CB75691229298B087CECCE960FF58A | +| $m_{P92}$ | DEF9FAEEDEFE2419FA4B449D1B89B5682E2737893D73861E8896751C98EDB97FE420C49B47BD5C613C6FA4975D45C9E1 | +| $m_{P93}$ | 1726AFC63875C59FE90AAC65B025B474391B5260DC7CE6BB922B02ECBFA91C53B9110C02AA5251ACF6E8C1360B26A00E | +| $m_{P94}$ | 35312E77E51F7B5DE09F130BB39C8EAF2CEB52F25D1E212FF6ED76A1FF24B777C40887143C8A62794595D0B1D0BF2CD8 | +| $m_{P95}$ | 5D24F5A606D43E707271201EFA13E6895BA4F2902A20A40D58E238E601644ADA7CD86D9E99C5656ABF1202B6CC8E43B1 | +| $m_{P96}$ | F80DF53DF2589FF24B7B328D55FC7F0D48FB86C29C29621C6A430B08AAFB7D5AA85198373A77F7B12892E881C3926E7A | +| $m_{P97}$ | D052486802107E23E728599BB13AF620978666D0D7754F5865C0D22E9360DA73D581D8C4438EBC5C2C3D56C74222297D | +| $m_{P98}$ | C31DC3517E333297B221A9F7CE515A937E73E7CA83267C2E9F5EBEAE1B2560FE08ACEDF23F | + +| Code ID | Basic Midamble Codes $m_p$ of length $P=384$ | +|------------|-------------------------------------------------------------------------------------------------------| +| | 36BC3ADE463F2D54D20846 | +| $m_{P99}$ | 88A39E4C76F47734449643EEDA50D53FF03257408630A124DF37A3E1CEE6CE99774A8D4F4BB
C051610E8678D178102C1 | +| $m_{P100}$ | F97DF22FC49643368615CF1AE6D533DF665526FF687D6700FDABAE8508387A0F3C8CC570095
33C6CB4E6BE4745BD79D9 | +| $m_{P101}$ | CA8B772CF3F8D8DDA7F6F150055AC969C3DD65E9877C874BF8FF647059C4F72A73571B46913
EC206CAC682EDDCB01563 | +| $m_{P102}$ | 211E6E505E3B7C4BDC9DFAF1EB0457627847593C0557E1426A1DA992CDF40CCADA7C9FA6D
ECDF1D3CCB9C23DFCFA6B1 | +| $m_{P103}$ | 548D9792FE5C5707FB28B1277DB9735FA78847F0DA1D6C153EC719BBDD5187C496F72579E6
C74405859C218A03B9FEA3 | +| $m_{P104}$ | 49FCBC2408159269EE42A32A5F0F44D1D30DC91756E274E573DF961E7B05DA1C532AF3036B
B31BFE77AEBC37051FC96A | +| $m_{P105}$ | 09C767858FB0AA0BCFBA1FE6BBEBEC75765BDA2456959A84FE9161E2E5F4260666D3FEBA71
924E26447BAD5B92E58E79 | +| $m_{P106}$ | 622AF5FCD674D2C2D87205243E19B1C65726D78513C8FB88945A5F38D1C6400411753F63402F
6280CF702ECD6852E4BD | +| $m_{P107}$ | B53353D78D382A74373C16B36888D56575DD25E5701E7F8C8619DB360B422632E7002905B16B
1B6D9BD5023B815C2C6C | +| $m_{P108}$ | E183A082E8344992730B23036E315AED6E156FA27045DF86B067A99FB68D2DFA3201205457D3
BD31A88F0BD88BF8C32D | +| $m_{P109}$ | 9AB97BB759FDDE364A61F5158E6938AE346A03F6D073D0C4ED838015ECF56477D736A487650
670FDD6D0AB1245EB60FC | +| $m_{P110}$ | 08C36A4F926400AF9A17D43CAF2613A9D639549C94EED7CD6FF00E60D985DAFC394AB8BA4
CCC9EBFC7939D5C3AB27FEA | +| $m_{P111}$ | 9881A3B723E688515287243A605FA52838AE13E94BFBF4D97D6E04530C2EE43906F7F81019E8
6AE4B32504A92F399AA1 | +| $m_{P112}$ | 2807EC91A1E3CC4847A758D16EAFE7E3AB0DB5180A978BFF7450F06778DA79CAA15E467B1B
CCBF6992DEC69AE88D89D3 | +| $m_{P113}$ | 9E9A5527723F3A4F339E828920D2556D21CD5E6FDC89B6575AF9FFA38233BBC05E8F2AE7052
AC7DBF622BF369A76F0E2 | +| $m_{P114}$ | 71812CEECEAC08C71C633D4C815AD805555A6ED7A778FD5F4D4810E5D92DA662B6836015E8
F9303A79798493E4166CC0 | +| $m_{P115}$ | 4147CB2F5C019034CADC1EBB6331B3DE37197611A6635B0784B4BF0DBBF12AEEAEA3D2E794
B9C1B6BB97FCC9D408DAAF | +| $m_{P116}$ | 445499D892AE276B0C2CE2BD81924E91B6A8D072EA3E63503F2287EB5F5E639EDE88082C164
18FC294E08D069F4CC127 | +| $m_{P117}$ | 66EE0C821076D702D1D5C35D37F25F0DCE3C8692B9CB65C4CEA5579F5AC3EF25CB06691B7
6DE6D972AF370A27F1415EC | +| $m_{P118}$ | D60A097019B8C9171A344854DDDCF6472F39DE9B9447956F78B60763A80EF6CF93B650E7B0A
81D59DD4B0FCBCD25FB0E | +| $m_{P119}$ | 7244FEFA50F90D284132D7DFE7E93C0EF16DA1A10765118691471255518CB76C44AE6B274C0
D3BC5C143B06AEE07615B | +| $m_{P120}$ | 8D6B45351ABE278271368F0E2DA5EE5BD014746202478243DAC30EB011326BF99845BDAADF74
3D54214C193A2DF54F991 | +| $m_{P121}$ | 42B80322CDB54071258B9B6911523E063CFC88AF918ACBBADDFE89EB7C261003E32931C3FC
BA525A48553A533458E872 | +| $m_{P122}$ | 3E1A4867271132EB25B853FEB3B44F80F69D57BF796D71F53C46D598E5BD2D22F8347B64559
1FAC08AFCFDFE5C838317 | +| $m_{P123}$ | 91AB7E8D6CB2EBCB099F275B1BA0C7D8D18E8A6FA2EFF169100AE4FF0ECB94F79FDDDA7F5
AD42EAC766741C96E608D6F | +| $m_{P124}$ | E16CC4455F92D7F7AAC7D83A63E94A286AE4B9CFDBC3181FFB94CC26CFDB43DCA63A169A
20BE959E65062A5524DCCB86 | +| $m_{P125}$ | 9E1BEC0CB9835F5FAFEB3C4A27D32A982346ADC4215F5A7237C4D1009CB2DECB9C1C486DD
ACDADEAE123F958666B0EE7 | +| $m_{P126}$ | CB04C57E4069E0CF9D4AD9D71567C2D243A9FB0DEDEECBA8D77EBF02CCFA77B4C491915B
039FE851A4B8D9197D577A16 | +| $m_{P127}$ | 7CB3DEC05A1E73C703BF610AC8914E2F4D63329FEFB69E1B35E86F92AB87EB27EEBC098B5
B1119CC8BD1B149B2A01946 | + +## AB.3 Association between Midambles and Channelisation Codes + +The following mapping schemes apply for the association between midambles and channelisation codes if no midamble is allocated by higher layers. These mapping schemes apply for all burst types 1, 2 and 3. Secondary channelisation codes are marked with a \*. These associations apply both for UL and DL. + +### AB.3.1 Association for $K_{\text{Cell}} = 16$ Midambles + +![A hierarchical tree diagram showing the association between midambles and channelisation codes for K_Cell = 16. The tree starts with m^(1) - c_1^(1) at the root, branching into m^(1) - c_2^(1) and m^(5) - c_2^(2). It further branches into m^(1) - c_4^(1), m^(3) - c_4^(2), m^(5) - c_4^(3), and m^(7) - c_4^(4). Each of these branches into m^(1) - c_8^(1), m^(2) - c_8^(2), m^(3) - c_8^(3), m^(6) - c_8^(4), m^(5) - c_8^(5), m^(4) - c_8^(6), m^(7) - c_8^(7), and m^(8) - c_8^(8). Each of these branches into m^(1) - c_16^(1), m^(9) - c_16^(2), m^(2) - c_16^(3), m^(10) - c_16^(4), m^(3) - c_16^(5), m^(11) - c_16^(6), m^(6) - c_16^(7), m^(14) - c_16^(8), m^(5) - c_16^(9), m^(13) - c_16^(10), m^(4) - c_16^(11), m^(12) - c_16^(12), m^(7) - c_16^(13), m^(15) - c_16^(14), m^(8) - c_16^(15), and m^(16) - c_16^(16). Finally, each of these branches into m^(1) - c_32^(1), m^(1) - c_32^(2)*, m^(9) - c_32^(3), m^(9) - c_32^(4)*, m^(2) - c_32^(5), m^(2) - c_32^(6)*, m^(10) - c_32^(7), m^(10) - c_32^(8)*, m^(3) - c_32^(9), m^(3) - c_32^(10)*, m^(11) - c_32^(11), m^(11) - c_32^(12)*, m^(6) - c_32^(13), m^(6) - c_32^(14)*, m^(14) - c_32^(15), m^(14) - c_32^(16)*, m^(5) - c_32^(17), m^(5) - c_32^(18)*, m^(13) - c_32^(19), m^(13) - c_32^(20)*, m^(4) - c_32^(21), m^(4) - c_32^(22)*, m^(12) - c_32^(23), m^(12) - c_32^(24)*, m^(7) - c_32^(25), m^(7) - c_32^(26)*, m^(15) - c_32^(27), m^(15) - c_32^(28)*, m^(8) - c_32^(29), m^(8) - c_32^(30)*, m^(16) - c_32^(31), and m^(16) - c_32^(32)*.](ef86416097668984aee7611317e77bb9_img.jpg) + +A hierarchical tree diagram showing the association between midambles and channelisation codes for K\_Cell = 16. The tree starts with m^(1) - c\_1^(1) at the root, branching into m^(1) - c\_2^(1) and m^(5) - c\_2^(2). It further branches into m^(1) - c\_4^(1), m^(3) - c\_4^(2), m^(5) - c\_4^(3), and m^(7) - c\_4^(4). Each of these branches into m^(1) - c\_8^(1), m^(2) - c\_8^(2), m^(3) - c\_8^(3), m^(6) - c\_8^(4), m^(5) - c\_8^(5), m^(4) - c\_8^(6), m^(7) - c\_8^(7), and m^(8) - c\_8^(8). Each of these branches into m^(1) - c\_16^(1), m^(9) - c\_16^(2), m^(2) - c\_16^(3), m^(10) - c\_16^(4), m^(3) - c\_16^(5), m^(11) - c\_16^(6), m^(6) - c\_16^(7), m^(14) - c\_16^(8), m^(5) - c\_16^(9), m^(13) - c\_16^(10), m^(4) - c\_16^(11), m^(12) - c\_16^(12), m^(7) - c\_16^(13), m^(15) - c\_16^(14), m^(8) - c\_16^(15), and m^(16) - c\_16^(16). Finally, each of these branches into m^(1) - c\_32^(1), m^(1) - c\_32^(2)\*, m^(9) - c\_32^(3), m^(9) - c\_32^(4)\*, m^(2) - c\_32^(5), m^(2) - c\_32^(6)\*, m^(10) - c\_32^(7), m^(10) - c\_32^(8)\*, m^(3) - c\_32^(9), m^(3) - c\_32^(10)\*, m^(11) - c\_32^(11), m^(11) - c\_32^(12)\*, m^(6) - c\_32^(13), m^(6) - c\_32^(14)\*, m^(14) - c\_32^(15), m^(14) - c\_32^(16)\*, m^(5) - c\_32^(17), m^(5) - c\_32^(18)\*, m^(13) - c\_32^(19), m^(13) - c\_32^(20)\*, m^(4) - c\_32^(21), m^(4) - c\_32^(22)\*, m^(12) - c\_32^(23), m^(12) - c\_32^(24)\*, m^(7) - c\_32^(25), m^(7) - c\_32^(26)\*, m^(15) - c\_32^(27), m^(15) - c\_32^(28)\*, m^(8) - c\_32^(29), m^(8) - c\_32^(30)\*, m^(16) - c\_32^(31), and m^(16) - c\_32^(32)\*. + +Figure AB.1: Association of Midambles to Spreading Codes for $K_{\text{Cell}} = 16$ + +### AB.3.2 Association for $K_{\text{Cell}} = 8$ Midambles + +![A hierarchical tree diagram showing the association of midambles to spreading codes. The root node is m^{(1)} - c_1^{(1)}, which branches into m^{(1)} - c_2^{(1)} and m^{(5)} - c_2^{(2)}. The diagram continues to branch out to the right, showing associations with codes c_4, c_8, c_{16}, and c_{32} across different midamble indices (1 through 8).](da87c1b628b63a046d8a0d0fc2c058ea_img.jpg) + +The diagram illustrates the association of midambles to spreading codes for $K_{\text{Cell}} = 8$ . It is a hierarchical tree structure starting from the root node $m^{(1)} - c_1^{(1)}$ . + +- $m^{(1)} - c_1^{(1)}$ branches into: + - $m^{(1)} - c_2^{(1)}$ + - $m^{(1)} - c_2^{(1)}$ branches into $m^{(1)} - c_4^{(1)}$ and $m^{(3)} - c_4^{(2)}$ . + - $m^{(1)} - c_4^{(1)}$ branches into $m^{(1)} - c_8^{(1)}$ and $m^{(2)} - c_8^{(2)}$ . + - $m^{(1)} - c_8^{(1)}$ branches into $m^{(1)} - c_{16}^{(1)}$ and $m^{(1)} - c_{16}^{(2)*}$ . + - $m^{(1)} - c_{16}^{(1)}$ branches into $m^{(1)} - c_{32}^{(1)}$ and $m^{(1)} - c_{32}^{(2)*}$ . + - $m^{(1)} - c_{16}^{(2)*}$ branches into $m^{(1)} - c_{32}^{(3)*}$ and $m^{(1)} - c_{32}^{(4)*}$ . + - $m^{(2)} - c_8^{(2)}$ branches into $m^{(2)} - c_{16}^{(3)}$ and $m^{(2)} - c_{16}^{(4)*}$ . + - $m^{(2)} - c_{16}^{(3)}$ branches into $m^{(2)} - c_{32}^{(5)}$ and $m^{(2)} - c_{32}^{(6)*}$ . + - $m^{(2)} - c_{16}^{(4)*}$ branches into $m^{(2)} - c_{32}^{(7)*}$ and $m^{(2)} - c_{32}^{(8)*}$ . + - $m^{(3)} - c_4^{(2)}$ branches into $m^{(3)} - c_8^{(3)}$ and $m^{(6)} - c_8^{(4)}$ . + - $m^{(3)} - c_8^{(3)}$ branches into $m^{(3)} - c_{16}^{(5)}$ and $m^{(3)} - c_{16}^{(6)*}$ . + - $m^{(3)} - c_{16}^{(5)}$ branches into $m^{(3)} - c_{32}^{(9)}$ and $m^{(3)} - c_{32}^{(10)*}$ . + - $m^{(3)} - c_{16}^{(6)*}$ branches into $m^{(3)} - c_{32}^{(11)*}$ and $m^{(3)} - c_{32}^{(12)*}$ . + - $m^{(6)} - c_8^{(4)}$ branches into $m^{(6)} - c_{16}^{(7)}$ and $m^{(6)} - c_{16}^{(8)*}$ . + - $m^{(6)} - c_{16}^{(7)}$ branches into $m^{(6)} - c_{32}^{(13)}$ and $m^{(6)} - c_{32}^{(14)*}$ . + - $m^{(6)} - c_{16}^{(8)*}$ branches into $m^{(6)} - c_{32}^{(15)*}$ and $m^{(6)} - c_{32}^{(16)*}$ . + - $m^{(5)} - c_2^{(2)}$ + - $m^{(5)} - c_2^{(2)}$ branches into $m^{(5)} - c_4^{(3)}$ and $m^{(7)} - c_4^{(4)}$ . + - $m^{(5)} - c_4^{(3)}$ branches into $m^{(5)} - c_8^{(5)}$ and $m^{(4)} - c_8^{(6)}$ . + - $m^{(5)} - c_8^{(5)}$ branches into $m^{(5)} - c_{16}^{(9)}$ and $m^{(5)} - c_{16}^{(10)*}$ . + - $m^{(5)} - c_{16}^{(9)}$ branches into $m^{(5)} - c_{32}^{(17)}$ and $m^{(5)} - c_{32}^{(18)*}$ . + - $m^{(5)} - c_{16}^{(10)*}$ branches into $m^{(5)} - c_{32}^{(19)*}$ and $m^{(5)} - c_{32}^{(20)*}$ . + - $m^{(4)} - c_8^{(6)}$ branches into $m^{(4)} - c_{16}^{(11)}$ and $m^{(4)} - c_{16}^{(12)*}$ . + - $m^{(4)} - c_{16}^{(11)}$ branches into $m^{(4)} - c_{32}^{(21)}$ and $m^{(4)} - c_{32}^{(22)*}$ . + - $m^{(4)} - c_{16}^{(12)*}$ branches into $m^{(4)} - c_{32}^{(23)*}$ and $m^{(4)} - c_{32}^{(24)*}$ . + - $m^{(7)} - c_4^{(4)}$ branches into $m^{(7)} - c_8^{(7)}$ and $m^{(8)} - c_8^{(8)}$ . + - $m^{(7)} - c_8^{(7)}$ branches into $m^{(7)} - c_{16}^{(13)}$ and $m^{(7)} - c_{16}^{(14)*}$ . + - $m^{(7)} - c_{16}^{(13)}$ branches into $m^{(7)} - c_{32}^{(25)}$ and $m^{(7)} - c_{32}^{(26)*}$ . + - $m^{(7)} - c_{16}^{(14)*}$ branches into $m^{(7)} - c_{32}^{(27)*}$ and $m^{(7)} - c_{32}^{(28)*}$ . + - $m^{(8)} - c_8^{(8)}$ branches into $m^{(8)} - c_{16}^{(15)}$ and $m^{(8)} - c_{16}^{(16)*}$ . + - $m^{(8)} - c_{16}^{(15)}$ branches into $m^{(8)} - c_{32}^{(29)}$ and $m^{(8)} - c_{32}^{(30)*}$ . + - $m^{(8)} - c_{16}^{(16)*}$ branches into $m^{(8)} - c_{32}^{(31)*}$ and $m^{(8)} - c_{32}^{(32)*}$ . + +A hierarchical tree diagram showing the association of midambles to spreading codes. The root node is m^{(1)} - c\_1^{(1)}, which branches into m^{(1)} - c\_2^{(1)} and m^{(5)} - c\_2^{(2)}. The diagram continues to branch out to the right, showing associations with codes c\_4, c\_8, c\_{16}, and c\_{32} across different midamble indices (1 through 8). + +Figure AB.2: Association of Midambles to Spreading Codes for $K_{\text{Cell}} = 8$ + +### AB.3.3 Association for $K_{\text{Cell}} = 4$ Midambles + +![A hierarchical tree diagram showing the association of midambles to spreading codes for K_Cell = 4. The tree starts with a root node m^{(1)} - c_1^{(1)} on the left. It branches into two main paths: m^{(1)} - c_2^{(1)} and m^{(5)} - c_2^{(2)}. The m^{(1)} - c_2^{(1)} path further branches into m^{(1)} - c_4^{(1)} and m^{(3)} - c_4^{(2)}. The m^{(5)} - c_2^{(2)} path branches into m^{(5)} - c_4^{(3)} and m^{(7)} - c_4^{(4)}. Each of these four nodes then branches into m^{(\cdot)} - c_8^{(\cdot)} and m^{(\cdot)} - c_8^{(\cdot)*}. Each of these eight nodes then branches into m^{(\cdot)} - c_{16}^{(\cdot)} and m^{(\cdot)} - c_{16}^{(\cdot)*}. Finally, each of these sixteen nodes branches into two spreading codes: m^{(\cdot)} - c_{32}^{(\cdot)} and m^{(\cdot)} - c_{32}^{(\cdot)*}. The indices for the spreading codes are: (1), (2)*, (3)*, (4)*, (5)*, (6)*, (7)*, (8)* for the first group; (9), (10)*, (11)*, (12)*, (13)*, (14)*, (15)*, (16)* for the second group; (17), (18)*, (19)*, (20)*, (21)*, (22)*, (23)*, (24)* for the third group; and (25), (26)*, (27)*, (28)*, (29)*, (30)*, (31)*, (32)* for the fourth group.](3d590ad29ecfe728f07432e6fcb59064_img.jpg) + +A hierarchical tree diagram showing the association of midambles to spreading codes for K\_Cell = 4. The tree starts with a root node m^{(1)} - c\_1^{(1)} on the left. It branches into two main paths: m^{(1)} - c\_2^{(1)} and m^{(5)} - c\_2^{(2)}. The m^{(1)} - c\_2^{(1)} path further branches into m^{(1)} - c\_4^{(1)} and m^{(3)} - c\_4^{(2)}. The m^{(5)} - c\_2^{(2)} path branches into m^{(5)} - c\_4^{(3)} and m^{(7)} - c\_4^{(4)}. Each of these four nodes then branches into m^{(\cdot)} - c\_8^{(\cdot)} and m^{(\cdot)} - c\_8^{(\cdot)\*}. Each of these eight nodes then branches into m^{(\cdot)} - c\_{16}^{(\cdot)} and m^{(\cdot)} - c\_{16}^{(\cdot)\*}. Finally, each of these sixteen nodes branches into two spreading codes: m^{(\cdot)} - c\_{32}^{(\cdot)} and m^{(\cdot)} - c\_{32}^{(\cdot)\*}. The indices for the spreading codes are: (1), (2)\*, (3)\*, (4)\*, (5)\*, (6)\*, (7)\*, (8)\* for the first group; (9), (10)\*, (11)\*, (12)\*, (13)\*, (14)\*, (15)\*, (16)\* for the second group; (17), (18)\*, (19)\*, (20)\*, (21)\*, (22)\*, (23)\*, (24)\* for the third group; and (25), (26)\*, (27)\*, (28)\*, (29)\*, (30)\*, (31)\*, (32)\* for the fourth group. + +Figure AB.3: Association of Midambles to Spreading Codes for $K_{\text{Cell}} = 4$ + +### AB.3.4 Association for Burst Types 4 and $K_{\text{Cell}} = 1$ Midamble + +For burst type 4 there is only a single midamble defined, thus all channelisation codes are associated with the same midamble. + +# Annex B (normative): Signalling of the number of channelisation codes for the DL common midamble case for 3.84Mcps TDD + +The following mapping schemes shall apply for the association between the number of channelisation codes employed in a timeslot and the use of a particular midamble shift in the DL common midamble case. In the following tables the presence of a particular midamble shift is indicated by '1'. Midamble shifts marked with '0' are left unused. Mapping schemes B.4, B.5 and B.6 are not applicable to beacon timeslots where a P-CCPCH is present, because the default midamble allocation scheme is applied to these timeslots. Note that in mapping schemes B.4, B.5 and B.6, the fixed and pre-allocated channelisation code for the beacon channel is included into the number of indicated channelisation codes. + +## B.1 Mapping scheme for Burst Type 1 and $K_{Cell}=16$ Midambles + +| m1 | m2 | m3 | m4 | m5 | m6 | m7 | m8 | m9 | m10 | m11 | m12 | m13 | m14 | m15 | m16 | | +|----|----|----|----|----|----|----|----|----|-----|-----|-----|-----|-----|-----|-----|----------| +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 code | +| 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 codes | +| 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 codes | +| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 4 codes | +| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 5 codes | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 6 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 7 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 8 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 9 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 10 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 11 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 12 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 13 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 14 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 15 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 16 codes | + +## B.2 Mapping scheme for Burst Type 1 and $K_{Cell}=8$ Midambles + +| M1 | m2 | m3 | m4 | m5 | m6 | m7 | m8 | | +|----|----|----|----|----|----|----|----|---------------------| +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 code or 9 codes | +| 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 2 codes or 10 codes | +| 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 3 codes or 11 codes | +| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 4 codes or 12 codes | +| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 5 codes or 13 codes | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 6 codes or 14 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 7 codes or 15 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 8 codes or 16 codes | + +## B.3 Mapping scheme for Burst Type 1 and $K_{Cell}=4$ Midambles + +| m1 | m3 | m5 | m7 | | +|----|----|----|----|--------------------------| +| 1 | 0 | 0 | 0 | 1 or 5 or 9 or 13 codes | +| 0 | 1 | 0 | 0 | 2 or 6 or 10 or 14 codes | +| 0 | 0 | 1 | 0 | 3 or 7 or 11 or 15 codes | +| 0 | 0 | 0 | 1 | 4 or 8 or 12 or 16 codes | + +## B.4 Mapping scheme for beacon timeslots and $K_{Cell}=16$ Midambles + +| m1 | m2 | m3 | M4 | m5 | m6 | m7 | M8 | m9 | m10 | m11 | M12 | m13 | m14 | m15 | m16 | | +|----|-----------|----|----|----|----|----|----|----|-----|-----|-----|-----|-----|-----|-----|--------------------------------------------------------------------| +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 code (see note 1) | +| 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 codes (SCTD applied to beacon in this time slot, see note 2) | +| 1 | $x^{(1)}$ | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 13 codes | +| 1 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 codes (SCTD not applied to beacon in this time slot) or 14 codes | +| 1 | $x^{(1)}$ | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 codes or 15 codes | +| 1 | $x^{(1)}$ | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 4 codes or 16 codes | +| 1 | $x^{(1)}$ | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 5 codes | +| 1 | $x^{(1)}$ | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 6 codes | +| 1 | $x^{(1)}$ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 7 codes | +| 1 | $x^{(1)}$ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 8 codes | +| 1 | $x^{(1)}$ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 9 codes | +| 1 | $x^{(1)}$ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 10 codes | +| 1 | $x^{(1)}$ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 11 codes | +| 1 | $x^{(1)}$ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 12 codes | + +(\*) For the case of SCTD applied to beacon, midamble shift 2 is used by the diversity antenna. + +Note 1: If only one code is present in a beacon time slot, this code is a beacon channel and the beacon channel is the only channel in this slot, by default. Therefore, only the beacon midamble(s) shall be used. + +Note 2: If SCTD is applied to the beacon and only two codes are present in a beacon time slot, the beacon channel is the only channel in this slot, by default. Therefore, only the beacon midambles shall be used. + +## B.5 Mapping scheme for beacon timeslots and $K_{\text{Cell}}=8$ Midambles + +| m1 | m2 | m3 | m4 | m5 | m6 | m7 | M8 | | +|----|-----------|----|----|----|----|----|----|-------------------------------------------------------------------| +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 code (see note 1) | +| 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 2 codes (SCTD applied to beacon in this time slot, see note 2) | +| 1 | $x^{(1)}$ | 1 | 0 | 0 | 0 | 0 | 0 | 7 or 13 codes | +| 1 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 2 (SCTD not applied to beacon in this time slot) or 8 or 14 codes | +| 1 | $x^{(1)}$ | 0 | 0 | 1 | 0 | 0 | 0 | 3 or 9 or 15 codes | +| 1 | $x^{(1)}$ | 0 | 0 | 0 | 1 | 0 | 0 | 4 or 10 or 16 codes | +| 1 | $x^{(1)}$ | 0 | 0 | 0 | 0 | 1 | 0 | 5 codes or 11 codes | +| 1 | $x^{(1)}$ | 0 | 0 | 0 | 0 | 0 | 1 | 6 codes or 12 codes | + +(\*) For the case of SCTD applied to beacon, midamble shift 2 is used by the diversity antenna. + +Note 1: If only one code is present in a beacon time slot, this code is a beacon channel and the beacon channel is the only channel in this slot, by default. Therefore, only the beacon midamble(s) shall be used. + +Note 2: If SCTD is applied to beacon and only two codes are present in a beacon time slot, the beacon channel is the only channel in this slot, by default. Therefore, only the beacon midambles shall be used. + +## B.6 Mapping scheme for beacon timeslots and $K_{\text{Cell}}=4$ Midambles + +| m1 | m3 | m5 | m7 | | +|----|----|----|----|--------------------------------| +| 1 | 0 | 0 | 0 | 1code (see note 1) | +| 1 | 1 | 0 | 0 | 4 or 7 or 10 or 13 or 16 codes | +| 1 | 0 | 1 | 0 | 2 or 5 or 8 or 11 or 14 codes | +| 1 | 0 | 0 | 1 | 3 or 6 or 9 or 12 or 15 codes | + +Note 1: If only one code is present in a beacon time slot, this code is a beacon channel and the beacon channel is the only channel in this slot, by default. Therefore, only the beacon midamble shall be used. + +## B.7 Mapping scheme for Burst Type 2 and $K_{\text{Cell}}=6$ Midambles + +| m1 | m2 | m3 | m4 | m5 | m6 | | +|----|----|----|----|----|----|---------------------| +| 1 | 0 | 0 | 0 | 0 | 0 | 1 or 7 or 13 codes | +| 0 | 1 | 0 | 0 | 0 | 0 | 2 or 8 or 14 codes | +| 0 | 0 | 1 | 0 | 0 | 0 | 3 or 9 or 15 codes | +| 0 | 0 | 0 | 1 | 0 | 0 | 4 or 10 or 16 codes | +| 0 | 0 | 0 | 0 | 1 | 0 | 5 or 11 codes | +| 0 | 0 | 0 | 0 | 0 | 1 | 6 or 12 codes | + +## --- B.8 Mapping scheme for Burst Type 2 and $K_{\text{Cell}}=3$ Midambles + +| m1 | m2 | m3 | | +|----|----|----|-------------------------------------| +| 1 | 0 | 0 | 1 or 4 or 7 or 10 or 13 or 16 codes | +| 0 | 1 | 0 | 2 or 5 or 8 or 11 or 14 codes | +| 0 | 0 | 1 | 3 or 6 or 9 or 12 or 15 codes | + +## --- B.9 Mapping scheme for Burst Type 4 and $K_{\text{Cell}}=1$ Midamble + +| m1 | | +|----|---------------------------------------------------------------| +| 1 | 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15 or 16 codes | + +# Annex BA (normative): Signalling of the number of channelisation codes for the DL common midamble case for 1.28Mcps TDD + +The following mapping schemes shall apply for the association between the number of channelisation codes employed in a timeslot and the use of a particular midamble shift in the DL common midamble case. In the following tables the presence of a particular midamble shift is indicated by '1'. Midamble shifts marked with '0' are left unused. + +## BA.1 Mapping scheme for K=16 Midambles + +| m1 | m2 | m3 | m4 | m5 | m6 | M7 | M8 | m9 | m10 | m11 | m12 | M13 | m14 | m15 | m16 | | +|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------| +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 code | +| 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 codes | +| 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 codes | +| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 4 codes | +| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 5 codes | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 6 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 7 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 8 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 9 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 10 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 11 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 12 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 13 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 14 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 15 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 16 codes | + +## BA.2 Mapping scheme for K=14 Midambles + +| m1 | m2 | m3 | m4 | m5 | m6 | M7 | M8 | m9 | m10 | m11 | m12 | M13 | m14 | | +|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|-----------------| +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 or 15 code(s) | +| 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 or 16 codes | +| 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 codes | +| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 4 codes | +| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 5 codes | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 6 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 7 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 8 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 9 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 10 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 11 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 12 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 13 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 14 codes | + +## BA.3 Mapping scheme for K=12 Midambles + +| m1 | m2 | m3 | m4 | m5 | m6 | M7 | M8 | m9 | m10 | m11 | m12 | | +|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|-----------------| +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 or 13 code(s) | +| 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 or 14 codes | +| 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 or 15 codes | +| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 4 or 16 codes | +| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 5 codes | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 6 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 7 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 8 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 9 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 10 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 11 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 12 codes | + +## BA.4 Mapping scheme for K=10 Midambles + +| m1 | m2 | m3 | m4 | m5 | m6 | M7 | M8 | m9 | m10 | | +|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|-----------------| +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 or 11 code(s) | +| 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 or 12 codes | +| 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 or 13codes | +| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 4 or 14 codes | +| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 5 or 15 codes | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 6 or 16 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 7 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 8 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 9 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 10 codes | + +## BA.5 Mapping scheme for K=8 Midambles + +| m1 | m2 | m3 | m4 | m5 | m6 | m7 | m8 | | +|----------|----------|----------|----------|----------|----------|----------|----------|----------------| +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 or 9 code(s) | +| 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 2 or 10 codes | +| 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 3 or 11 codes | +| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 4 or 12 codes | +| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 5 or 13 codes | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 6 or 14 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 7 or 15 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 8 or 16 codes | + +## --- BA.6 Mapping scheme for K=6 Midambles + +| m1 | m2 | m3 | m4 | m5 | m6 | | +|----|----|----|----|----|----|----------------------| +| 1 | 0 | 0 | 0 | 0 | 0 | 1 or 7 or 13 code(s) | +| 0 | 1 | 0 | 0 | 0 | 0 | 2 or 8 or 14 codes | +| 0 | 0 | 1 | 0 | 0 | 0 | 3 or 9 or 15 codes | +| 0 | 0 | 0 | 1 | 0 | 0 | 4 or 10 or 16 codes | +| 0 | 0 | 0 | 0 | 1 | 0 | 5 or 11 codes | +| 0 | 0 | 0 | 0 | 0 | 1 | 6 or 12 codes | + +## --- BA.7 Mapping scheme for K=4 Midambles + +| m1 | m2 | m3 | m4 | | +|----|----|----|----|---------------------------| +| 1 | 0 | 0 | 0 | 1 or 5 or 9 or 13 code(s) | +| 0 | 1 | 0 | 0 | 2 or 6 or 10 or 14 codes | +| 0 | 0 | 1 | 0 | 3 or 7 or 11 or 15 codes | +| 0 | 0 | 0 | 1 | 4 or 8 or 12 or 16 codes | + +## --- BA.8 Mapping scheme for K=2 Midambles + +| m1 | m2 | | +|----|----|-------------------------------------------------| +| 1 | 0 | 1 or 3 or 5 or 7 or 9 or 11 or 13 or 15 code(s) | +| 0 | 1 | 2 or 4 or 6 or 8 or 10 or 12 or 14 or 16 codes | + +# Annex BB (normative): Signalling of the number of channelisation codes for the DL common midamble case for 7.68Mcps TDD + +The following mapping schemes shall apply for the association between the number of channelisation codes employed in a timeslot and the use of a particular midamble shift in the DL common midamble case. In the following tables the presence of a particular midamble shift is indicated by '1'. Midamble shifts marked with '0' are left unused. Mapping schemes in section BB.4, BB.5 and BB.6 are not applicable to beacon timeslots where a P-CCPCH is present, because the default midamble allocation scheme is applied to these timeslots. Note that in the mapping schemes of sections BB.4, BB.5 and BB.6, the fixed and pre-allocated channelisation code for the beacon channel is included into the number of indicated channelisation codes. + +## BB.1 Mapping scheme for $K_{Cell}=16$ Midambles + +| m1 | m2 | m3 | m4 | m5 | m6 | m7 | M8 | m9 | m10 | m11 | m12 | m13 | m14 | m15 | m16 | | +|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------------| +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 or 17 code | +| 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 or 18 codes | +| 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 or 19 codes | +| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 4 or 20 codes | +| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 5 or 21 codes | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 6 or 22 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 7 or 23 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 8 or 24 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 9 or 25 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 10 or 26 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 11 or 27 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 12 or 28 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 13 or 29 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 14 or 30 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 15 or 31 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 16 or 32 codes | + +## BB.2 Mapping scheme for $K_{Cell}=8$ Midambles + +| M1 | m2 | m3 | m4 | m5 | m6 | m7 | m8 | | +|----------|----------|----------|----------|----------|----------|----------|----------|---------------------------| +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 or 9 or 17 or 25 codes | +| 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 2 or 10 or 18 or 26 codes | +| 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 3 or 11 or 19 or 27 codes | +| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 4 or 12 or 20 or 28 codes | +| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 5 or 13 or 21 or 29 codes | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 6 or 14 or 22 or 30 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 7 or 15 or 23 or 31 codes | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 8 or 16 or 24 or 32 codes | + +## BB.3 Mapping scheme for $K_{\text{Cell}}=4$ Midambles + +| m1 | m3 | m5 | m7 | | +|----|----|----|----|--------------------------------------------------| +| 1 | 0 | 0 | 0 | 1 or 5 or 9 or 13 or 17 or 21 or 25 or 29 codes | +| 0 | 1 | 0 | 0 | 2 or 6 or 10 or 14 or 18 or 22 or 26 or 30 codes | +| 0 | 0 | 1 | 0 | 3 or 7 or 11 or 15 or 19 or 23 or 27 or 31 codes | +| 0 | 0 | 0 | 1 | 4 or 8 or 12 or 16 or 20 or 24 or 28 or 32 codes | + +## BB.4 Mapping scheme for beacon timeslots and $K_{\text{Cell}}=16$ Midambles + +| m1 | m2 | m3 | M4 | m5 | m6 | m7 | M8 | m9 | m10 | m11 | M12 | m13 | m14 | m15 | m16 | | +|----|-----------|----|----|----|----|----|----|----|-----|-----|-----|-----|-----|-----|-----|--------------------------------------------------------------------------| +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 code (see note 1) | +| 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 codes (SCTD applied to beacon in this time slot, see note 2) | +| 1 | $x^{(*)}$ | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 13 or 25 codes | +| 1 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 codes (SCTD not applied to beacon in this time slot) or 14 or 26 codes | +| 1 | $x^{(*)}$ | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 or 15 or 27 codes | +| 1 | $x^{(*)}$ | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 4 or 16 or 28 codes | +| 1 | $x^{(*)}$ | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 5 or 17 or 29 codes | +| 1 | $x^{(*)}$ | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 6 or 18 or 30 codes | +| 1 | $x^{(*)}$ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 7 or 19 or 31 codes | +| 1 | $x^{(*)}$ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 8 or 20 or 32 codes | +| 1 | $x^{(*)}$ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 9 or 21 codes | +| 1 | $x^{(*)}$ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 10 or 22 codes | +| 1 | $x^{(*)}$ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 11 or 23 codes | +| 1 | $x^{(*)}$ | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 12 or 24 codes | + +(\*) For the case of SCTD applied to beacon, midamble shift 2 is used by the diversity antenna. + +Note 1: If only one code is present in a beacon time slot, this code is a beacon channel and the beacon channel is the only channel in this slot, by default. Therefore, only the beacon midamble(s) shall be used. + +Note 2: If SCTD is applied to the beacon and only two codes are present in a beacon time slot, the beacon channel is the only channel in this slot, by default. Therefore, only the beacon midambles shall be used. + +## BB.5 Mapping scheme for beacon timeslots and $K_{\text{Cell}}=8$ Midambles + +| m1 | m2 | m3 | m4 | m5 | m6 | m7 | M8 | | +|----|------------------|----|----|----|----|----|----|-------------------------------------------------------------------------------------| +| 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 code (see note 1) | +| 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 2 codes (SCTD applied to beacon in this time slot, see note 2) | +| 1 | x (*) | 1 | 0 | 0 | 0 | 0 | 0 | 7 or 13 or 19 or 25 or 31 codes | +| 1 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 2 (SCTD not applied to beacon in this time slot) or 8 or 14 or 20 or 26 or 32 codes | +| 1 | x (*) | 0 | 0 | 1 | 0 | 0 | 0 | 3 or 9 or 15 or 21 or 27 codes | +| 1 | x (*) | 0 | 0 | 0 | 1 | 0 | 0 | 4 or 10 or 16 or 22 or 28 codes | +| 1 | x (*) | 0 | 0 | 0 | 0 | 1 | 0 | 5 or 11 or 17 or 23 or 29 codes | +| 1 | x (*) | 0 | 0 | 0 | 0 | 0 | 1 | 6 or 12 or 18 or 24 or 30 codes | + +(\*) For the case of SCTD applied to beacon, midamble shift 2 is used by the diversity antenna. + +Note 1: If only one code is present in a beacon time slot, this code is a beacon channel and the beacon channel is the only channel in this slot, by default. Therefore, only the beacon midamble(s) shall be used. + +Note 2: If SCTD is applied to beacon and only two codes are present in a beacon time slot, the beacon channel is the only channel in this slot, by default. Therefore, only the beacon midambles shall be used. + +## BB.6 Mapping scheme for beacon timeslots and $K_{\text{Cell}}=4$ Midambles + +| m1 | m3 | m5 | m7 | | +|----|----|----|----|-------------------------------------------------------------------| +| 1 | 0 | 0 | 0 | 1code (see note 1) | +| 1 | 1 | 0 | 0 | 4 or 7 or 10 or 13 or 16 or 19 or 22 or 25 or 28 or 31 codes | +| 1 | 0 | 1 | 0 | 2 or 5 or 8 or 11 or 14 or 17 or 20 or 23 or 26 or 29 or 32 codes | +| 1 | 0 | 0 | 1 | 3 or 6 or 9 or 12 or 15 or 18 or 21 or 24 or 27 or 30 codes | + +Note 1: If only one code is present in a beacon time slot, this code is a beacon channel and the beacon channel is the only channel in this slot, by default. Therefore, only the beacon midamble shall be used. + +## BB.7 Mapping scheme for Burst Type 4 and $K_{\text{Cell}}=1$ Midamble + +| m1 | | +|----|-------------------------------------------------------------------------------------------------------------------------------| +| 1 | 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31 or 32 codes | + +# --- Annex C (informative): CCPCH Multiframe Structure for the 3.84 Mcps option + +In the following figures C.1 to C.3 some examples for Multiframe Structures on Primary and Secondary CCPCH are given. The figures show the placement of Common Transport Channels on the Common Control Physical Channels. Additional S-CCPCH capacity can be allocated on other codes and timeslots of course, e.g. FACH capacity is related to overall cell capacity and can be configured according to the actual needs. Channel capacities in the annex are derived using bursts with long midambles (Burst format 1). Every TrCH-box in the figures is assumed to be valid for two frames (see row 'Frame #'), i.e. the transport channels in CCPCHs have an interleaving time of 20msec. + +The actual CCPCH Multiframe Scheme used in the cell is described and broadcast on BCH. Thus the system information structure has its roots in this particular transport channel and allocations of other Common Channels can be handled this way, i.e. by pointing from BCH. + +| Frame # | 0
1 | 2
3 | 4
5 | 6
7 | 8
9 | 10
11 | 12
13 | 14
15 | 16
17 | 18
19 | 20
21 | 22
23 | 24
25 | 26
27 | 28
29 | 30
31 | 32
33 | 34
35 | 36
37 | 38
39 | 40
41 | 42
43 | 44
45 | 46
47 | 48
49 | 50
51 | 52
53 | 54
55 | 56
57 | 58
59 | 60
61 | 62
63 | +|--------------------------|--------|--------|--------|--------|--------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------| +| CCPCHs in TS k, Code 0 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CCPCHs in TS k+8, Code 0 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +![Timing diagram showing the sequence of channels: BCH 12,2 kbps, FACH 25,93 kbps, PCH 9,15 kbps, and PICH 1,53 kbps.](991dd3ca8ff5bdb023220b1d44775e1d_img.jpg) + +The diagram shows a horizontal sequence of four channels: **BCH 12,2 kbps**, **FACH 25,93 kbps**, **PCH 9,15 kbps**, and **PICH 1,53 kbps**. Each channel name is enclosed in a rectangular box, and they are separated by small gray vertical bars. + +Timing diagram showing the sequence of channels: BCH 12,2 kbps, FACH 25,93 kbps, PCH 9,15 kbps, and PICH 1,53 kbps. + +Figure C.1: Example for a multiframe structure for CCPCHs and PICH that is repeated every 64th frame + +| Frame # | 0
1 | 2
3 | 4
5 | 6
7 | 8
9 | 10
11 | 12
13 | 14
15 | 16
17 | 18
19 | 20
21 | 22
23 | 24
25 | 26
27 | 28
29 | 30
31 | 32
33 | 34
35 | 36
37 | 38
39 | 40
41 | 42
43 | 44
45 | 46
47 | 48
49 | 50
51 | 52
53 | 54
55 | 56
57 | 58
59 | 60
61 | 62
63 | +|--------------------------|--------|--------|--------|--------|--------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------| +| CCPCHs in TS k, Code 0 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CCPCHs in TS k+8, Code 0 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CCPCHs in TS k+8, Code n | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +![Timing diagram showing the sequence of channels: BCH 22,88 kbps, FACH 36,6 kbps, PCH 12,2 kbps, and PICH 1,53 kbps.](da5916a6e0721dae9522ac5b8abd218f_img.jpg) + +The diagram shows a horizontal sequence of four channels: **BCH 22,88 kbps**, **FACH 36,6 kbps**, **PCH 12,2 kbps**, and **PICH 1,53 kbps**. Each channel name is enclosed in a rectangular box, and they are separated by small gray vertical bars. + +Timing diagram showing the sequence of channels: BCH 22,88 kbps, FACH 36,6 kbps, PCH 12,2 kbps, and PICH 1,53 kbps. + +Figure C.2: Example for a multiframe structure for CCPCHs and PICH that is repeated every 64th frame, n=1...7 + +# Annex CA (informative): CCPCH Multiframe Structure for the 1.28 Mcps option + +![](4807d5d16f0db93c98330469b9ce5676_img.jpg) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------|---|---|---|---|---|---|---|---|---|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| Frame # | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 8 | 9 | 10 | 12 | 14 | 16 | 18 | 20 | 22 | 24 | 26 | 28 | 30 | 32 | 34 | 36 | 38 | 40 | 42 | 44 | 46 | 48 | 50 | 52 | 54 | 56 | 58 | 60 | 62 | +| | | | | | | | 7 | | | 11 | 13 | 15 | 17 | 19 | 21 | 23 | 25 | 27 | 29 | 31 | 33 | 35 | 37 | 39 | 41 | 43 | 45 | 47 | 49 | 51 | 53 | 55 | 57 | 59 | 61 | 63 | +| CCPCH1 in TS 0, $c_{Q=16}^{(k=1)}$ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CCPCH2 in TS 0, $c_{Q=16}^{(k=2)}$ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + + + +| | | | | | +|--------------|--|-------------|-------------|--------------| +| BCH 13.2kbps | | PCH 8.8kbps | FACH 11kbps | PICH 2.2kbps | +|--------------|--|-------------|-------------|--------------| + +Figure CA.1: Example for a multiframe structure for CCPCHs and PICH that is repeated every 64th frame (128 sub-frame) + +![](dbe92208b9347289db4a331635197136_img.jpg) + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|------------------------------------|---|---|---|---|---|---|---|---|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----| +| Frame # | 0 | 1 | 2 | 3 | 4 | 6 | 7 | 8 | 10 | 12 | 14 | 16 | 18 | 20 | 22 | 24 | 26 | 28 | 30 | 32 | 34 | 36 | 38 | 40 | 42 | 44 | 46 | 48 | 50 | 52 | 54 | 56 | 58 | 60 | 62 | +| | | | | | 5 | | | 9 | 11 | 13 | 15 | 17 | 19 | 21 | 23 | 25 | 27 | 29 | 31 | 33 | 35 | 37 | 39 | 41 | 43 | 45 | 47 | 49 | 51 | 53 | 55 | 57 | 59 | 61 | 63 | +| CCPCH1 in TS k, $c_{Q=16}^{(k=i)}$ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +| CCPCH2 in TS k, $c_{Q=16}^{(k=j)}$ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | + + + +| | | | | | | +|--------------|--|---------------|--|--------------|--| +| PCH 13.2kbps | | FACH 19.8kbps | | PICH 2.2kbps | | +|--------------|--|---------------|--|--------------|--| + +Figure CA.2: Example for a multiframe structure for S-CCPCHs and PICH that is repeated every 64th frame, $i,j=1 \dots 16$ ( $i \neq j$ ), $k \neq 0, 1$ , (128 sub-frame) + +# Annex CB (informative): Examples of the association of UL TPC commands to UL uplink time slots and CCTrCH pairs for 1.28 Mcps TDD + +In the following two examples of the association of UL TPC commands to UL time slots and CCTrCHs are shown (see 5A.2.2.2): + +**Table CB.1 Two examples of the association of UL TPC commands to UL uplink time slots and CCTrCH pairs with NULslot=3** + +Case 1: $N_{UL\_TPCsymbols}=2$ ; Case 2: $N_{UL\_TPCsymbols}=4$ + +| Sub-Frame Number | Case 1
(2 UL TPC symbols) | | The order of the served UL time slot and CCTrCH pairs (UL time slot and CCTrCH number) | Case 2
(4 UL TPC symbols) | | +|------------------|------------------------------------|-----|----------------------------------------------------------------------------------------|------------------------------|------------------------------------| +| | The order of UL TPC symbols | | | The order of UL TPC symbols | | +| SFN'=0 | (1 st
$UL_{pos}=0$ ) | 0 → | 0 (TS3) ← | 0 → | (1 st
$UL_{pos}=0$ ) | +| | | 1 → | 1 (TS4) ← | 1 → | | +| | | | 2 (TS5) ← | 2 → | | +| | | | 1 (TS4) ← | 3 → | | +| SFN'=1 | (1 st
$UL_{pos}=2$ ) | 0 ↘ | 0 (TS3) ← | 0 ↖ | (1 st
$UL_{pos}=2$ ) | +| | | 1 → | 1 (TS4) ← | 1 ↖ | | +| | | | 2 (TS5) ← | 2 → | | +| | | | 0 (TS3) ← | 3 → | | +| SFN'=2 | (1 st
$UL_{pos}=2$ ) | 0 ↘ | 0 (TS3) ← | 0 ↖ | (1 st
$UL_{pos}=1$ ) | +| | | 1 ↘ | 1 (TS4) ← | 1 ↖ | | +| | | | 2 (TS5) ← | 2 ↖ | | +| | | | 0 (TS3) ← | 3 ↖ | | +| ... | ... | | ... | ... | | + +# Annex CC (informative): Examples of the association of UL SS commands to UL uplink time slots + +In the following two examples of the association of UL SS commands to UL uplink time slots are shown (see 5A.2.2.3): + +**Table CC.1 Two examples of the association of UL SS commands to UL uplink time slots with $N_{ULslot}=3$** + +Case 1: $N_{SSsymbols}=2$ ; Case 2: $N_{SSsymbols}=4$ + +| Sub-Frame Number | Case 1
(2 UL SS symbols) | | The order of the served UL time slot (UL time slot number) | Case 2
(4 UL SS symbols) | | +|------------------|------------------------------------|-----|------------------------------------------------------------|-----------------------------|------------------------------------| +| | The order of UL SS symbols | | | The order of UL SS symbols | | +| SFN'=0 | (1 st
$UL_{pos}=0$ ) | 0 → | 0 (TS3) ← | 0 | (1 st
$UL_{pos}=0$ ) | +| | | 1 → | 1 (TS4) ← | 1 | | +| | | | 2 (TS5) ← | 2 | | +| | | | 1 (TS4) ← | 3 | | +| SFN'=1 | (1 st
$UL_{pos}=2$ ) | 0 → | 0 (TS3) ← | 0 | (1 st
$UL_{pos}=2$ ) | +| | | 1 → | 1 (TS4) ← | 1 | | +| | | | 2 (TS5) ← | 2 | | +| | | | 0 (TS3) ← | 3 | | +| SFN'=2 | (1 st
$UL_{pos}=2$ ) | 0 → | 0 (TS3) ← | 0 | (1 st
$UL_{pos}=1$ ) | +| | | 1 → | 1 (TS4) ← | 1 | | +| | | | 2 (TS5) ← | 2 | | +| | | | 0 (TS3) ← | 3 | | +| ... | ... | ... | ... | ... | ... | + +# --- Annex CD (normative): T-CPICH bit sequences for the 3.84 Mcps MBSFN IMB option + +**Table CD.1: T-CPICH pilot bit sequences for the 3.84 Mcps MBSFN IMB option** + +| Primary scrambling code index $n$ | Slot index $i$ | T-CPICH pilot bit sequences $B^{(n)}_{T-CPICH,0} \dots B^{(n)}_{T-CPICH,959}$ in hexadecimal representation (reading from left to right, then from top to bottom) | +|-----------------------------------|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | 0 | B8BC9229F99056BF241881D6EDFD552DDED31C7E5CB4830D2C88B7949337D640E518702906868AE4
F0D2E4EF09DCE5CD845CAF825488880EC5FC89408420FFD854389FE54E5AEB782B4447049A3B1810
C3574F0DB9C88A8F0DCF11ECE48ECC5A872D9EB65270EB5113004A8500E6B7EEB46A79CD5B9E1742 | +| | 1 | A619B3A7F98FAD8EB1C5A49B826DF7E600A2A26565B4B31079586E83F864340538C2BA87E957A7B8
FC30E32CFB648F8529110A492AB99CD6820E84064C6F8C1E08CBCAF8492D97A0CF135BCE0ED9C484
5ADDE53A1545C943D4982F0D1CAD790BD7B349959C840C4B1798CC9C666EC934EC544A4A5E42AFF00 | +| | 2 | 4248448A60CDC808CEE8DA329AD54888F3B74035717A9ADE41A2EC0AEE4DFD006D4EC2EB5D72D50D
9DC8A76D9646749EDC6003918938455DAE0A5C008A008C3074A58F00D88FAB9B12936CC672528C36
24B9CF484EA0E91AE617B94A9B4144C9D1FB321B16184187FDAC28C5495CB94F41C819096626641F | +| | 3 | E7D15E21FAEEAEDE08C75EC4CC49C9C30BE4098C1AEDC781D99C13575248A207D51525A52964D8
FF62E2D64FCA2CF838A96FAB92397AC4B48CE614A8EDEAA0736CEE29275951CC189A2012D292E433
E098AF3C01B43D10B946355CCC55C1F85BBA6C80794FEF080793AD070F104C10CAA8828B02E7B4A | +| | 4 | 64EF0E94CE9129C86724EB94583C257C647D63548480D9344CBFE1A9D28163E549AF594EA6D25AAC
1F3E72FFC18109095600C2DA848D2382AEDBEF410C374C20C10AA2DCA53A7983842DF2CE81F57051
8299D57D9E97D4C90AEEDCEF16646A0416C968841E12B7672C94FD4816FE154EE990290849C2EE56 | +| | 5 | 1D922F3889C4D6606EB1D622E65EA16F4F28B40B49E90C49B62E84F1E4C04D2D4345220E9008E1A5
C45C8AD0872E626FAABA048CBF75D0082C3A706C99842A9B6B1E0ADD4A5820402C43535768650B38
0B80594224E7B531A46CC15BAF3A18E913C2C43EA15A9CB716636CDDF76BE4C8488CB8F8847080F0 | +| | 6 | CE94A497F0BF9CBADEC3C49D4D94B076889E24B55C0583851C30787A2427044AF3B8CE94EF101D4E
2A4008557E924862E1116261C4C4D4F89A8262C757EDE1B71EC054983482618B288D698E48FD6329
C213076CE28C85B0D1EC918782C5B0083868600C9FAD0469CDE6915FB2481A4966E71B2B6838E023 | +| | 7 | 63B60CAB008C3BD59577111A4818BB84A61C99D08A2C84CE954818DCAFE4999EAED0BDE9078234D7
92CC2F9839BE4AE418D65B0392C10D58501E4967E3445315900C2691B27D23751594BF21820D2D31
0509EE6A4222B21F0A212EC8453E8C4AE9158DD1BD4A8A9D98284A55313CA8ED508896A2A8C522D5 | +| | 8 | A6D910704AFC9CD24324B764913B7E20DD71E4F4DAB12543658168AC14CA9095E9C8B54FD1C00A8E
1051A1CF30A363E4F8F749AC48A1828B92A6EC411925D2F1E7F1D63410C93E2DA43ACD696E6D0674
9547E387DA5BF4C0024DF044A71354CC74E7CE9B92647216ABCC16BC26EF0ECD8CB8C806BB4E3D9 | +| | 9 | 4088C20812CEC1246ABE6AE55EA2C842C7F56E1B9E4BA6C8CEFE187C56D48637CC1A83064504478A
741674C048EB018A12BA6C5CB790EB0382ADB2E9E689ED79D3C262917D4B9DE30C5F05ECE97CDCEE
42C80CE72CF0D1DFB1CE4D9A85DDB46879CC8009DCF84D62BCC489A14D49D949852E32A6C468F154 | +| | 10 | 24FB5A5C09ECD46F410A52349BC0C4E080F5579B29C3EA418407794AC8FE45495564F48703EDC180
D059288DC674217AD2EF00A6C6FE44A296FA485B0928CD88ACDCFCF9F9C254E23D9D1E849764A9
82DC83ACBCDDF8F2FAA074A26F48A52F27A16D2970C0BF4DCFC123CAABB6D3C66EA68C1D551BDA6A | +| | 11 | C93DD61EA5D6D473E29B8422C8D14D8A035B692327D6492F888B42A6578B01E9061DED09237CC071
31A1F992665078CAA72C7F51C7F00EC64E28989E56E2C97902B88D226446B46A26AE4C68CC4F1A0D
1B1AD23242F9484AD0F0C1CD4C8863784138C48D6F711DDE890409D9A5ECC2001A828929D93247FF | +| | 12 | CD0E265B8DF204AFDC655FB7CECAF603B4E0EA685E97BE4E64B85C01A414C490C565485A19EFA8F5
C10B1A31A9E841369502CB0E0D5B32D3E120ADA0EE07DD7422A5808386EC474CE750C88624090129
6A12600AD616E1463C8B3BAF6AE08C4A2B585700B028DD0C440DE4B06CA8856DAFBF1D17E5478B67 | +| | 13 | 36F087C42AE04202FC029EA0A8098749966E394ED214846821196EEFEA23185C79A68584351BAF40
0F03B5ACED8CE7FADC884485B448900C4C1E5C79B15CE489213C66580F35CD155516FCD7845AB694
49D48040E2E8EC17C2EC8510E1AF70377E0A26E3EA354AC35F5588C386ABB6A0213082D7E7245545 | +| | 14 | C5E241B1C1F6F78AE0192A590FC25DE1AE529BE5F554806451197AE4B65EDFC26200CD0BBCB95B70
F0A4D31F48E4B411EA390D821A1BD31428BBB50CC099B03CA194BC9E4BACCEE0A28E6A16414E1C
F550D55989A18FE8E5C36AAEFDDAC6C2A50CC2898E8348175387D8FF15C2D618418826911EE07E17 | +| 128 | 0 | 6A1E8328A92DD0BC88C805C2C69604C3DE84E19DF5AA89942E66F9FCC41A8C26B604E4D8458A576
0CEE09C8822CC068075318E1B50263DAC873E02347FBD25191D5859C285866CD8E80BD27B7604AA2
2DC6DC7F8D8953A52B00D9C896CB5CD62388FA050175EFA0BC2ED888FB9550DB0F5819F90186C6C | +| | 1 | 5EA97D8C6A17B02A01BBE2C589943DDE2FB17E827FE400F6DF582700B244865CF8D4D20C912F380D
6494D81AD350219C1EC7A5FCF8504B81B89BCE12D845A38032682C9BC6C5585AEEE47F4A1F95B968
84C01446E2A46DC0013453FDF6300F67840231CC8D53C7A447420A28C999EF3866C12B084C0C3D45 | +| | 2 | C63FA876D54C06CA8D1198252AA2D79AFE579FAC8E39954EAF5CE8CB1B680C49B24000C042C4C36
EFC64961BF69A09688900125B82654479A95C4704E950C9C5E4136E5AC3B31CFB4261D12D6686E2A
6C1D68C1A923C0D1610CB56EC46D78086D22448D5C08FA75C077525BC58173996904524A6CE04198 | +| | 3 | A009CC8B8EABE248CC2E612E7F3408BEAFF1FBC3C8E7F6048A2AB9DAC3056D6A93C6ECC927A835C3
5718CC12983D4AF24FAD84989E7D5CEC29DF607CF0B68141955B107C098AE83CAACC03C0258140A9
E477D338028C96A84A9D5B00E94A45A1D0A09CED0072060DA0C0CC8206D35D880984959B1CD8827B | +| | 4 | 8ED0C874B6109F08704C51D4788AD52A4915B3E75542BC421C882E94F3C82A6A6C9CC02E1018B41F
0A1D70B96FCA55DC66E5D04688A638C22088AEE85ADDF422F1E5E101F6208056B4209A83F7499258
B05197BDA6F2A2D37B412C98860DC0DF388FA8BE1CFDD87646FCB888B479D296D77C4DCDB4E9809F7 | +| | 5 | C65CA06C3386A8845C5284202B80FD53F9D56FC4A54C4A762867552900E48EED2C742C34D9262624
4DA4BD86AC5E1F1764878A675C024777D8CF3DB9AF9D75728061A47F58BBC28CC6A54E8909C495D8
97E324C96C3427CA493EB68DD5D744DFA80A9710D60FEC963EC0894AC1D736CC0F1DD7029CD569CA | + +| | | +|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 6 | 5878BC84924406251337E2C101D84ACF291C08CDA72B0405FF40C2B944357D330A3A6E144028E0C0
2B00C63BA0310CC392AAC2626A9D80BF18540DDE00152CCA6689814861085F54CCBBEC97753EF03A
4C2558DFE7F1081C5F2B9149E4784A8F8ED5403D1D311DB0AC221E974DE792C198802D927EC98E1C | +| 7 | 654C6915BE1ED93C9278589710E51E0C6F26348A30A01BC69D1CC02DEFB4304AA631CA84C2235C2B
CD45420C0560CDBDB4F016483361C8A1C57A396756D654BEA337EA6808CA66913CB495ECF071CCA0
85978CFD284A2AAC1885917A9121A8ED4658EC3A1AA6D06C28E9441C133CD50A3052C06582784EEB | +| 8 | 60C55B146D808554AECFB07F70AEC905B8BF094D58248CF860ACB4194920C87C0CCD07BC228ED527
5BBF8AED0D7C1B8125441062B4D4F3FBC9E0EC788441F58856A9A3A040C14D65CC8C2D200FC76538
472048F0B5D13E4A225D552380CA8858D304C2CC26782EA0D4307FCEA84163A4CE5418188F932C5E | +| 9 | 2B13B8061528965ADEA41890CB013D05CB7397F94B15A0804D40001E862841633D6E58B36B9CD443
195DCB78648B2845C378AB4986FFEB6A6FEE86FE63C103CDE561C852963C069625001706904726EB4
CD843C6536894F9E69C855A2D88FD0F93C6D822673E45A1A1A80E14DC0D5B0192CCDA80FF89CD026 | +| 10 | 2F6B2858CA8C56A2836437CE778F7470C0C286295973C4CC1DEEE48A3D1C7CC948CCE5C6484BDBF2
C5803AFEC5AE810065F856091588948C084001346C5478323156E684296E28CB49398D4C0432CB8B
27272F5A42B8C2657B24C30D9AE088B0FC499CE05DE5BAC9ACEBD869CAA8A3F5741552BEA0FA0710 | +| 11 | 6FBA060A03BE2A87137F5B5510FA0490E0D8C2EE9C885A250DCF187DBA65C273308C940E1850AE31
7C9060AC5F11218F88C8022D26EA61AE274B80ABDE0F4C9D05C4A5CCB99A6972940E5CA60D298C5C
1E0A03E48146AE0F9AF74EEB81E10905BFD0F93116860EC4D16E951F6E6184EDC8BD94A67549F3C1 | +| 12 | 471C41321B7A781EA0DD019A625510A9DA4062C40B58869809C6850376C3083E4E39266DC0A8E331
112FB1076E0A2A7ECE985821DA78AB47D7D7BE8102A07A89CD50F0A01087B299E6872DE1AF81F1D0
EE40CA8C514ED08840AA41358D86C72B90A0D4338D20B0C4BFF651ACCCA247A61E46E65848B98488 | +| 13 | 8DDCB00E9018344546E7CA400C406C49153D96D5618B99CF4C6C2496312481AF50580E231CA78629
222A3BD7B08A1FD03CDB20889C4F00DA2AA917C7897814EAA650186C5FC7224E91D7A688A1F29464
09504F35CD1895281123290499466248A68A839DD529DFDB81E85C23403D5B51EDCDA8002B5FB14E | +| 14 | 414AAE5011E04AC64414FCAB8D1E95034A260A46A68B6CE4738D4017B108D401314BF0882067AD38
A5287430C302BC2F9258E69080FE0980777B004EA9B094BA49ACA9295DB3ED6DD413427A960CC6B6
66B5DF1F0350CF9A987A854424D4CCEAC5D5C8A0FDACD9E1ECA43954F9FB30CC53DB1959E7D65668 | +| 256 | 0 D044A6AB0F1C9ECA900C30E034CC9D959D8184E5DCFC1802C9632670AD00454532D2DF0CBADAD AFC
A04888F7653E1DE6D14A07743E335FC4DAA2F81D4C6AAC34AC0BC84B290B516FCA5BEF098943E94B
B241505E8A58C59AAC6A8B900581EB749A6C8162D0889300ABB9520DBF3A063D2B4B85B384312BA | +| | 1 80B3E7A74638FB6C82A56750986490B09810DD707010A2866C9DC0C0AD4589AA1D7A1498EDF5D0A0
FC84DCB61661B45D87BC2429CF2E4589445093F4A95E8C58CC7447E94AAD5EB3191134C0880E1194
FB0F5B869C07E34D09900D044C86CE5F8EE9783F5E7492652091210581305B0CC0D2E1FC99E29D4D | +| | 2 994D84D955E8FC9DC68C92048D8166DF29667A405AA21CADBA065CE1374463E0991144542BDF265B
A2FE87476CC9CC403D28009E6D0A2C850A42AA626D51ED009F5B31710AAAB4B842F3FD98A664CE0E
C121E64E8CCAD2E542E2CCE301274149FB05F8ABE3FC78654D8D44C5D44E88CC100CE0412D63F45F | +| | 3 2C5ACD90BD4CF469B5AC940A80D0EB94DA8F692DAE674F8CC38C413210C30DB185DDBE819D5158A2
81AD8785CD88D63A479575B1453B9D38C10EC87404055D80C45182C1C54C225AA3F05D1DD746C82F
4099E68ED0BE251578A07931F87E9413748DEC9A355501D47C4386D81BE9CAC39624C9511590254A | +| | 4 ABF8D9044BD4668241634E4482C8B9A87C9DC3D784D344024310DF08811F6C9FECC46694FB025E14
F206DD80777D29D81578752E28F3CF24FA3E975AEBBF3ED0EE9C8402115CC95C024F76A9767E8BC4
60DAF86423888C988B3984DF0D08980BE3EE88DC52EE1CEFF2F0201E762A570B554EC24E4AAC9804 | +| | 5 BD8AB598AF9356E9E507887B61641A61CE52D7E890AEACF894CB8BCD924F789FED400B8540A48B82
BCE1774E61D784EC5FEAB2C81BC82F4CCEEC65F0079A4E406EA44E1E0C988383C3A3866A93FD4C8A
8B7C8424D69BE067E0884003E0263AB90C0ADBF8A8EC9A0F10AA73429079A4D31CB5DE0CE463FDF67 | +| | 6 EEEEDC95D80C8CDF39CE2FFD2C7A6A19E6068998EDA4C33023D53A8900A243C026E28B0746FAF6CE
64C858EF2E0E0102865C35DC71E2A6A2998A88187872D407060D75F7A1246684157D8886982989E981
1C1E1808621D867D7A3EF94ABB1AF434A81423947B142680525984A8BB079D1E92E4E490D54CFF45 | +| | 7 674544848D9002DC1A287053CB96138EBDBB57F30FB731D9E1D54F9EF05A8DE688A874996D139062
B6A74CD48E0A289444FE7D0100D93847C20FC491ED4486E2001E88CCED206C8E574F11281ACA5616
2DEC4842BAC11D2D6B17D72453C9A9A5834D06D5A2A77094F0932487645E106E9A9CF6CBFAA4EA77 | +| | 8 C3CEA9FAC99F2BDD54D5000C10CC46C03DE62A71918AB8D66DE719D0686805526241948C3E4F44BA
84C5F1DE2E819CE9483B130846706114A5B89AE4DE3369C9652C1A4AE25000925DE2802349EABA0C
53B671FA15CDEBE68C8D0D86A64E59E88A4C282C47A3110DEB435FCC6C7BAADCDCDD8155BA1A60CA | +| | 9 3DB54E7AA4402CA90D875E552EF99CD92A523B6D98898748F702DE0D00C1DD9A6383E2B2591DF213
DDC7A9A60B49954734B88245DF995B9299AE8B48241B245BEAAD9FDC6C26526A0A8061815611DD951
0280288F8D28620484797498FFDCDCDE4B8840967C358DFB048D8051FC8D586BBAAC260DAD471145C6 | +| | 10 D4210A71B6C588CE83D139ACB4A3AB659121C05470E699823D6CE3838A5C585458AC1659AB8C4EA9
3C8DE470A8D08EA138B9C230AE4E489447FEC3064AE3F4D4D3C3214A19AB40CD8400905FF13AE3B7
1407A92442538E97E2A858C00B002B380294F2728F76EDBF5EC546F751242AA489116FF8246A7B95 | +| | 11 A99D574B117A9BA535132EB469C28172B50C036EED0F9D9D38654064D067FDB05A9EEB54655E886D
C11409F94C6D615B5CA487367A2A8480ED48C9AC8D004F47C4B01BC997C10CE3C4434C25CC029E3E
4EFC962A3EE6CBC20EFC4F8509E238AC167C663B8C2D0C6DF0BA7F76EBC4E05D2C408198C65C3F5 | +| | 12 23E00B8501CFD6D758E51B1ED1BED045F4F1C4D3340462980C14C9E2C8428502838B5C27D685B6E6
B684D1121AB2061428D3B6D167CEEE0FBD496C5C9FE8F5A4FA79C6A8D4BEDA90E8F9F36609F7AD0
FC720760CE30E9C4830CABADE4C8EDB81FB8A2DE6DD54103222834D055989C96988CEC406978A6A8 | +| | 13 9275CCA48B80849F30DFA3DB846549A1C700A701AA30A5DCF00F83A5F3B5926F70205105FFC41C1 | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | CC78D0D109A4E08A36345C4F6A0C79FF7B8ED121DC6B41040A92792B74580CCC4DA8A2C5C48FD6EA
CF2B0B17A5A47F43A46430D612C562BAB8508C3BD74964C639ADD147316A91D3898FA6412225B4C3 | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | +|-----|----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 14 | B8900BE8712BF48612ED498C3CEC079540D665C1D95D2970994870402592ABBD7DBEA58188002A06
3A65E56C9CF8E8185ED2B4806B2EEA8427158F720650FA28640A393C8C5126CD51167FBD164A6E0D
8810CE4882F42DF908FBFC66AAA7F445CEDB914E20080840867C90737C169EE529035A854E15A79B | +| 384 | 0 | 6FC11D043CA2EE8AAC696BCC440C1DC19A8D1C8BAAE89E3444EE1747A10509DBA5CD08C2516FF63A
A202D8B5E2A1BEADCF50CA2CAA56A54CD5407C7211ABCD5443BEBFEA089B44072542373B11C6803
9F9CC8C64DC898ECB40534A5834C98AD84C7412FCE87287B8CCC3F6F6EDA1D791CD470A508250279 | +| | 1 | 4356D82DAE59E70BD63014AF5E91D9ECAFD9AA081D1E2817750BD6B6D5D2CFC00D080480A9CC110
618766D0641B98410CC552497311ACF8523AE4E94136C1C13C56C43A0354D8ED16B0064A6D1D65BD
2A4C29D9D8C806915F6FE660371C202BCC8F735970E9362A524BC3C1188DEBEA0C0ACA1881A546CB | +| | 2 | 32C51B2C81FF8885C46086A8203A8A8796BF97F254DF2C467234E62E86ACC4F96149BC4EBC382CB2
5531186CFA341A80BE7907D808DAA38072ACB4A118727536396A40368748094E59384028F3843994
82FB8041D35123E0B814D0743638041CD8429B42A804118DA259B764336F6AFC025CE3C1B34FDBF0 | +| | 3 | 09C344BD38CD92139C421B41C5A5B3C18B8CEFFA2ADD35395036304A0B670145A6CC758AA5EAE292
7ACC9EA9276C48271B8D3D29A81CAD510124BA4C4A82822E856B0A6DC5DB747C6AAEE97F92C129E8
53589FCC969E6C2265D1FC710FC3C5CB4EC94120AC4254FA5E434C1D5785BD74029F5865A58660CC | +| | 4 | 871150B0CA021EF37F00AE694702483E9A073B8F05C0480456872F6101143702A02F4A031F5D88F
FE10E5CDDE0F375ADEC824462743D350D26D15D20B513C02C91148914C6459746C80EDFEA9F0663A
8F7ACCF85158BC28BF99CA5CD9719A3756F662CF4399DE84A9A52C8E77980DADD5787A282CD81AB5 | +| | 5 | C051D44AD1858A14F6DE75BA4D1586B544B9C407847C59C13862577A4F99ECB66904943E4EE010CB
C4CB9831D547C06B4DD2861CCD5FD8407095375291523DB911C1EA622006C317FA19D287DC36B0D6
89C8DD105C05DAB54854202C8C0CEBEE8D210132050712F853441F1DC4863B24D516D6EB4B642EC | +| | 6 | 084ECE527E41486B8BEB2A07D43DC1048DC10E0E79F4CFAD0BEFD19F6AD5F34B59EE02ECBEA02B5
88341A0E89159C5CF8C78958B995D1E58BAAE55994525F0CFA45123FCEE42BCD2B849553427A59E1
267A4A8D28A4C9A4775D80156C6B99A02CA9CBE53854C732F0424B500BB746817CD384D88903004D | +| | 7 | 0D9E4E66F4ADB1ECD516D7395C9BAADA958E0D051A86C4BED16A5D210DC624933825490496A8C92C
3802B2894FBC47208A0A22ACE2EC1A58BAA5950003882B1C0665C7600600C2967C2E9B7D464AF76A
8F605EFC1D30E72DC5927AD50B9AB55C32555D17A4B78565F578D5852069994F8B6CC62E6E01732D | +| | 8 | 0B2229462DAB2EFA7A02DC728CA3847DCD5684DEE3E8FD2B666098C54C80A268C49B837976125812
856170220B87A5C104FBE5666CB985194AFC194D84F3695EB0481415A960806F0C583A9ACA309C01
AE7C7D608C603A4DB9A82844A7FED0E0FCD1D44876D0A09CCCB278CF79CCEB84E56BB8D4EDFB8CD5B | +| | 9 | 7E893EC40E9AAF294ED51D5A4089F8643FA9664D8D6CE85A0D8334652DE947A29C3E5F3799BCEF
2490E7C953092F649B21A4A5190478D1C5E4FCADCBD0B58B5A0A120479ADD98017180BAF4B70C1C6
856068A9EFB1851657E4A7644C41B018D86A3B2A0A2DC15000E9D074A8EC95DAA28AE4D69D142651 | +| | 10 | 00C83EA49E22CEF2C2617432C2881412DC5662AAC2E20D7EAA92542068DC54508445E1C6584D812C
08F544B9FA8E4E1CCBF7870FE8A712E52040D5C5032072BA70864CADC454C44102004C7798726FAA
11C6989093E4664F501C1951A002B59E26A5D74064C596D6E75A9C2C4490D4E3A8C087FB06F6D9E7 | +| | 11 | 9AB5192C271160AF894BD66A82E8CF2C8E56FD967DFCBEC00024E0294DC5BE594F2F13A2EB62EA03
4706096DC0DA2F286A86CA4D4C93AA25610A43F498DA0541DE643C839784867492FA676C4380D8CC
41BA06006DC5A81E3F14D800217F8546914D2E7D67860131550807B4AEC550B45A8AC43E04DDFAD8 | +| | 12 | 5D7C8C8401EC80E085C20278DCC82274409816447951F9633350648E60B892BD544A2023A79B81D0
15E816F3EC492523158285CD7146480E48E5F46C10E8A11F36131C5DCA42D823C088FC600E5FFA7C
D00E04CFD789953C6B45BC1EE58CE99B8EDC0BE95145C0C59294D5F50E34ACB17F47A2BBD144D9DF | +| | 13 | 8269EF0305623CD2CC821CE0BF62F0CE623B2CBF9C128A6688CC41E8A4C1B5104D838891ECE47310
A9A65D47442A50B4B30C3966268A416F9282D6D84A07572DA675C7DA920B0E553B4C9E889840DA89
170C6750F5C06EA808A084FC324624FE1C14691D6590C8C92041B5B721126B6EFE439E48A6E4866F | +| | 14 | 15A1CFCC0521A6C215C64A614BEC6AB6BA045FA73D04567B9C10087A245A22C50CAC7D82B70A1F
C1A6776860921B34A49924102CC4446ECB28D40B4D7B818E7FC08A6EA18E4DEF86B69689FDF5520
16DDF41B6440DB86BCD0A84A64049E306B5F91D5DBC70ED954029F986369DED22CD0C3470E88E | +| 512 | 0 | A6947FC6947CD99887AB40E8AD774B46D83460455CBC1C436FDBB2B40F07857EAF0C404AC808E3B7
F8A2DAFE8351E8EC00B981124E42F251F80C68578F5D9081EFD88460F05473220B53E99279A2782F
48D4B8F799F861D2CB38A24993B1C0E710C0C09C4364110514FBC3E182925458CEB1E08630060834 | +| | 1 | 36128D8F37226E79801042EBC4C1298822846E63425B8711D53140341823B4CDB864800484270C5E
4B04E92D63B135919F9D302D047294A4DFE55984890D7DCF6F8376D727C001542A7F077C6BB829C0
60057B456B1867FCA98DEE94F5E5C4B0C895C4ECB08763DB0B7DD5A0E58CA8D93DEFD6601D10D9BC | +| | 2 | 97C1501D8FA00E2076149253FB3868876809EE49DF4D84AC77F4BAC6A1C48D2E246A1540F8C5B795
ACE0A47C1EF42504C0CFDE218E4D370289550C8AEA6F58E6C445C3C8462A4C6729CF83B2E048CE5C
756038C19478B0429B6C91B3CD0857ED42B3694658B3195C809C141CBA86BEE76DAD731EC16890E01 | +| | 3 | 89F88DAAE1BC3D0B4ACC34FAC79096B6615A2085F60B0C2511DE676A0F6EC080AF446C45C390A2EC
0A2106E48E88C0257E565284D298C4298B9CDD6EF400EE8D1325D0962BD991512F0799FAF2DFDB02
260CA0E7E54DFA29A4956BD480ACDE9930341ED66B17EAFACE485ADDD160A7C830A15D8FF0D09C20 | +| | 4 | 1E946C4D2694B885FC254FB6546B2C4AF5987994F51AC90827E08798E0C0D5750FDD8CAB9F58A895
448BF01E4BC8CE37477291C425D52E3E41D526888CBC3225664D649106EB907AF8F4C96B3704B887
041119AD0C5A8FBACFC457F3AFC74D12E7C9ECB5E5304B48206A421122EAC2287C499D8C2C455D40 | +| | 5 | B00870C4D8804598D27D8EE6194E1CFE276B65D82B737C3E2AC399829FA17CD1E52CA7E71E2B86F15
18904129A62589E694D0D4E988089EFD8A8414808F58E5D9FD8B84DB89C35D4D0DE51B24DCDA8AAA
D3616BB57CA3D30826F2015C35976EA8CDF614CA5AE45C8E68062605A07460C9252438F969905526 | +| | 6 | 1DCB60F29CC421E385F9F5715B67C11C053064C824B3C471C026DECAC799861FEE000D54C4CCE68B | + +| | | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 4E9ACD08C8522E5407600F8F7DA30D4CC8A104CE023BEF8AFCD28C34CF607422AE6FC4CBEF6D9B54
2DC7ABD8B4A5E8884232AB0180DBE049EA42AB968D805162798F67DFCA1DCCA5055620C86D7236C6 | +|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +| | | | +|-----|----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | 7 | 988678E7C0C19CFCC345B71BECC27DF0624C5B4F024786DE864860E19F121DC9D529444581A92710
67F280EC1A8E4E4AC623069C3F14808FB402DF516CAFECC3A4FFDE5D478D5CE8C3AEFE59024C2CE22
10ACD2D48D60E9073526278D2DD88BEB4154386C37E81C1661ABCE24A47E73C81C9C5C1065352FD4 | +| | 8 | C156599A4E4F06B2990C9FEEA46D8884D110019DBD470E7FF4C9CC38D610ADCEF94A4E14199BF9E9
1E96C44C2F01316BB6CFE6E33264D5C0EB408B54CEA6D7EC45F6E84B0CED84F7A0F064201C5DC406
B4CCD8862FA907AB04FF72588B6B92A08B4300175C9489F28691C8A5BBC08A186FBEB6A501767805 | +| | 9 | 1865FAB7D45A3E60D484CC9EDAB1CA690144E1CC26D0B39A2432C50EB00162D6FFC01DE80A1D8826
DFC0209A0E90BA6828C5D62590414FCB6ACF50A7902484055708662D3F024EC0E8E89A1C6605BB6E
5ED888B8AF447029BD3F0267F6ACFC2E00567995C3016CD01D909A6971ADC6A2A360774840FC32D9 | +| | 10 | AC4815F7471DD1C96AF1CB089465C6ECE675CCCC410EA64AD3DE0B66E75C909178E079E8A672E2E5
D47BA1C3CCB2CC8118F208EC3373380C15047801045CDC6E4D9E14032A243EA3269E24004512E328
2823F4F064A0BEAA8D43DCFE2C49449E5541BE52BEE63C8857FB2694C0A2DC9A568CA4519CCD48F1 | +| | 11 | A2BBD1D1D4450CCD20779B04E41A644D924C4048F6AE3C851CE2CC5E947B8583A921B06DCF4E6F31
CCCB1E5E800D0EC2411A449C6E1F981E17A8B0C08AA5470E9E520169DADC9239CDAE1C42058DFB6BA
0EA13AE7782F667C69C6ACCB20D6FC60C8239726E215158946BD951C4E0640E685C5E7C5C9A8B804 | +| | 12 | 57DCB22ECE4C2182C6CABF2E8BA04011929C4761CB725C0D044448C0A6CBB48994A2920E789006B9
78D2E0E2C08094CAA88D532D9CACCCA711BDF8942325BD64F706D82EF8D2D0B85EE2B08D98EB2F4C
41C929301298AAE829608C8A3220CEA607946E9B7CDADFBCC5684ACCB0A20E3845224C3C491B1E5 | +| | 13 | 878F97E1620BD906CD79D015D0D2A53EE4124E845AD4852028690366812E8AD5FAB1056E48F0970D
CCE62A55AF13C2EAEFD936268469B0286D42E0C03F240E42653CB8130104F2486962CC2047229E6
80157DE209710C1DE6944E4E5E4168AD4D309DF41BA46FCD8DA85921C9EDBBC75D7920F0BB36B6C8 | +| | 14 | CD1869AE1100EC1E8680C64AC48489843C69E045301598608D4D899CC9D9F1C23CD84B3C3205D90F
CD2C38C93E299148BD9B0B5ED1789ED478A0093C1E846DE7D8E8659055EB5CBFE884BDB95DD04E0C
A28DD51E580CAC3473A8C087907602BA9A627CC966D5E3801553D986E2842C10E2C9E6ADFEA60645 | +| 640 | 0 | 138D98B4815C8984B7DC08B87C868127445149E316DBB49C1C9F4B226E0A02385A5CD2A895F97CDD
801FE39DD4EAE41CCA8CF6FD693C7300E8E641094808A5A6007ACF62CB91A3C87D571F0094424EF5
E12E7EC5417B9825CDBEF6D9E59F654953DC8C988008CEA2706FD4E797AF0508088A2828F10B1D2D | +| | 1 | E158EBAD648F1D4C89883C537A89DFF151E344C8AC521AC0F48971508627D1C5A546B16F134CF4CA
BEACA EA628E4F845DA66D45C14983F90100F94FF9400507A8D6239405EB186A504653D2AED633CD9
72049290CFB9E81C54E04828A9C0DC9998C6950C1BD9D70D85375D115049F2231AA7C1F592CB4A7D | +| | 2 | 2020F33A1F67956340CC43E28A1841A6B0ED400EC0EE9B3C94689DEFE632204EC51A80C5FC9F089
8455BA6D54949B67A5D0704A7988723007E088C1C3E104D42F28687400EC2D2BCEA9C359C61CFDC8
4B185DAAC7BD8FF7A544EDABDFD640A7D72BADE148E481002EBE64568D7D70C2678E37EA1685D6B0 | +| | 3 | 871CACD6880544988157EAA226AD8D020C75CD109222C8CE55C894248E8C6D8F68249D63F1CA3CB9
5541BD1F88B52CA2D5C62681C4260161B544A569AEC0CCEAD52E14B7CB06607CE415194DD2377DCB
0375005DCB1639D983C67150534E94DCE0099C4CE6C17430A68108C1D1BC4596DB774D797E12ADEC | +| | 4 | C5BA82C4171A25CAAF1D53C5480D8C500E8588258090F38155BD0D9401F45E2700C99C4808776EE0
284B58F4345DBB851782FD0F4E891C3D4C5CB9A98D595866152E88C3148C94068B61863603C224E2
084020C0F6E78D1500A8323741217AF7808D7E85975BC3461DA398C70D55590E32F6E6403A5C8A8C | +| | 5 | 13CAE785764E1AD020828D0119416C58DC8C6BCBE3B8B664CB2E4D80EBFC46CCCFE27CC10D4A25C
557543509C7D8BACAC5BC4AACF51645CB8C408B820C015666C3B14A3149B2884620840C926D90B56
0A307884C63CA66B582919A8A18A39071B89770C5C44E20C39AA30CD68C11D4FBAD87E9A026AB421 | +| | 6 | 064202ACE41AD49CA9D068826CC22D13F055A83D18BB52D9B0A056252450140CFB1E89C70BC9B4D1
EC05D9723C448399171FA4A4558C420A60001C70A9CB355B0794E580562A50C024680BA7B3F02BB0
98AD1CE1114022723DCE739CBA16DE70C04725AAE9EE4C671C586DF064A5CA295C8E66C4EC86D9D6 | +| | 7 | 21B78C8061BB57C01FE591F46223220A9E062D422589987082CEAB141BFF921D4B21C8C90E7E0A80
20B9E3C9026D12590C42197287948F22D3FD977BAD2B90B74DEB6C098647AE55002D953E48C434EE
C78E4D5547838014EB8066644C209A4E4A1229FC121DF6CAB62B14AF9888E376B1D3DD1D3506832 | +| | 8 | 4A0E3441EC8A5AD6D5C1D21DC4890C06E39E018039A7C56E81291DA4805D096DD1C16064959910E8
5ECEEA5713B07F41502328006178ACBA0FDBCBC6B457A786EAA50E1A87A4A84C5C8DA06A8B4747D7
264997C84F0FD440DBA49EFD3D4AA8A8AE67DB122700A2D805DCA170856C5273FD3C8C82DB05A192 | +| | 9 | B1523862484C051A901F2A80FD1CDEE46483649324090D944CDC65E8EE37BF50C249E399C829A4CB
3358A8AA5CEE1C2A66AEA1CF3007885E12E73CC5D7599801D600A749666321E39BF0CBCA77581B93
89C725322799B7E4155CCE85C484D0D5EE426D5005C4E10C25A81DCE699EFDCA1EFC61FC1FA813A5 | +| | 10 | 0439C8F3B954205BF68C434E9480E4473441E16D83CCF12EA54179BC7E14FBFA4137AC232D257B2E
807CBAE831A4A1E1A1DA1003E0DA48A256E760A3E60F00406C21F85DE87E9D914EE6590D809166A4
1742E7ADCA8E48D7CEBC9643497DB20A426A5591840F5089458430346444E5AA904460298824C144 | +| | 11 | B469FC749052A6838980075486A7533B9914550CD2A8BC78BCED04478C6BDD5864DE1ECC826C4D45
42AC1D7AFE1864ED85CDEC6FBA2D4C9B8FE42F601DA00F86AC4F5BA88280A9A52072D95B2A7103AD
9C8E5BDE0AE91498A6ECC8B08C825B42DD8DE4D7AC1D30BA295B2DAAFD024BB04A54C212309CA3CE | +| | 12 | 68A5B8D8DDFC53E64D4C9D4A45A6C88A9B314A2E66F214187D7A98DD9931463BD2BC0B58DCA01688
5779FA4E61E421151028B74C8D583DDB698818142BE6E130A74D875C0E415C8DE484CE81854C2440
CA36C879F2A9949241C06EE51759BF6D882FFEC19A4F022D6485AE129E8C4665DDEE8857206B28EF | +| | 13 | C748FC01802B268F11044E28658E35B74845A9C35AA5029673EBACAD8F838F664857F9ABF888EC0
180DB550E6F27E60E5B4AFE6C6D7C34E0A12052DF008EC9422A2E8012E97063B80D24648D3AEAD42
D0F8E392BA037894A805DA01E887F8DE1ACCAA98B5C2AEDAC1C5D8202509D8E9FD16CA499080607 | +| | 14 | 5C02AE4063C16081D918F0A5249B7A64C5EAB1D6A77CE405447E2C1C121F919C0D3B073082129A85 | + +| | | | +|--|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | 7E4A7091B0006CF059C2682980468EFE09B56A8DCE6BC5D880046CC62288A590C9AC0A08CC5DAE52
09C24AEC94759DC9A2E05C79C0ED09F05B2BD660C91E054BEBB5294F09D93DE85AC60A99ED6E1845 | +|--|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +**Error:** + +173 + +**Error: Reference source not** + +| | | | +|-----|----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 768 | 0 | 15E21E6B24200F1FFA8985625F766D026C46898996945FC504D8499C468728735C756CBD6A92155B
BD6CFA674CBC9D0B090A9ECDE54587ACB0688F9666C0686EB217BEA2754AA65EA264C9198199E264
4B02CAADEC1D45DC892774385A904F643C66EC14BAE65C3267F0B2413C22A921C6804F85026014C1 | +| | 1 | C50F328B4C5C48022A8E0CE14393A8456D8EE9DA6DE5A36223B41D9C0ABA3B4820D92D29369CC90D
77866629041BCED58A2AEC947C8815781E94C49639CE44DD125887A49321CC1ECF841D55880B7FD5
08854192A444D9FC042E45C19FA92B6FB94EA5B8CB521BE1E06BE2CDDD0048DE095FE0EA26CB5434 | +| | 2 | B77D70563885A1E0E502B45E9847643BB0C22B44B4050F5CB47ADD09C2072E60F8E1ACE002F65A6A
CDE91B545D6C7E685D02F29216D84B248C6C9D47DA8B7ABB09F08CA601B0C51C64CE8DD9C3A83040
66A825E685EE9A15F4C3BE47B1385AA8A8F8916FDDADD9B22189DA69774C6608D9246A9C61436C2 | +| | 3 | 20046C0E3801B9CEA71B0DCB5CADC5C51A8C028D114C036CA5D06FB44A428F36CDDA37A4CB548759
864B94712C2043F51D84E740B8DFE64E158018A41A17D0F5CD3FCC41CF0B44D16880F51C81680045
214998AA2D2A5B02F914C696A7D6E49300C7A70CA788200D5AC8F82B59C4625E91002FAD8605DC58 | +| | 4 | 1F169F9838CD517840B079DEE61F3CDD2751B3409492D7B2DCCB625CC18744E59FC42C838FE40F6
1A963C616A087DEB046FE80095BCBC28A06C44AEEC504016940924EF6AE1AF545B6180E9C4DBF849
9EC85F857C6958CD8C4D5E7F710240BABCEEF22565524CABD1FE6367E9EE50FE6F087CCB9C69F5615 | +| | 5 | 6346FC9AEE28C004895127E3A64960D4A1510DC1BD9715F6ECC7C3B88EFAF1D915819491A935A67
6940CDCE1C34EDC5E5284B8797B5016D18DF8D7C0FC80504A4F63AA51EA5389880B99548C4A04455
954C245D1C649A8B133C108601C09431D0FD63E7E41FD0F3116BDCE16CD77B62BE9D85EFB959266 | +| | 6 | 9728C4C0DC66F2709EE22543B509EB6302006F0EEF939B850268FBF0300A380842677F0609609
D582B8B052A8D4DA9601399284A43C4874A5059104292489FD1F78AD52120F152C69F0A1459D709B
537050E421CCD096309CAE0E8E8C6752AA10589A2281487ED001D9D111006D955D841C5A1C6D201F | +| | 7 | E9A00C8880DF2784030486E650254748640AD06C0ECD914F0A73AB904CB8085074070021024FC612
896272B5068BA10EA50E2B66909CDC5BC3AB7920567019EDD44C7B119B8E404D08B0DACA34561E7F
E85A251CE166E4C259F1848866F9A7F4DA644C7C4C2A85341465924BD705214F5A8509A7E5003428 | +| | 8 | B21CA5DB7DCDEF97D50219CAE77EC242AA58DC4378E11874A50D0FCA45805366C82927F51CA42809
1C404D4821FCCDE34052463089FB320F541181E698D64C2F1D5AE7DA8A9B9D4716902815545FC845
2E72A869E8ABACA4E812BBDFC80AC1B4DEAB64AAA1803B392501068E6418A8F418A7C8AA29C84C8C | +| | 9 | 02F0AD8E99A24D3CD4C02B3CFCB0D5349EAD59114B05752129002406633AF9A069F69D6032C10D9E
4C424D16B016FA58D6CB40804E90601CA4595FC0BBBDDB7C8FB7C0BBBDDB21C841155D46938A888CF98
F12650E61C6EC4C1FACFB542D6E5CCF3096A402DEF5AA31E133CCF15C9A45B0CAA485250E041C461 | +| | 10 | 6189B50C25863E82FC3D5A843CE8F4D84D437C2CA5C8BC0C0A389ABB478CD52DF9C4EB448481DC0
D4150643A2DA896F51742A82BA0986F1662914B2926593A1510E077026C51F8A7F88DEEEED4F16B3
E50E8630AE03FA570AC753D18551D2D9C64005A2954D604DAD9D798E4A589760076A3D41921603B9 | +| | 11 | 8049797BDA828C0012FAA3266E044397F57E538CE3C0C174248D00E2D89FBA46884A549684D1E24
C8AAB885A1176797446874282042880A62534D840EFA909C86EC4C6BCEB48DE1BF80B3AED94C71AF
94D6C750E402DB698744787B0A6CB4A664690C07CFAF56A4B6DC7BE55407B6C52AB19CD559483F7E | +| | 12 | 40591C4191A1E8E0B853A463A7D805940800F389ABD07003C599D4092041CD4C9D310CCA3E4C6EF1
A1784AB914E8CB729DE6BF0847A1DCE6C8C046D317D29495316AED1B6FB1891CA890C818EDCE6E028
3B2043D4E02ACD68A74EB66ADA9F941A99D525AC04F9CEA086F578D1A6C5B8B30985A187E8CC7DC | +| | 13 | 504E99F104FF9FE0C9A78CF29682C49B0E2E74FB2E20EC419DA401208F6C993D03E8148A3297A485
C4E18A2D3A9CA7ACF940F7DA50DA3474FAE9BB5B35AA7CC2C17F652E728200799B7EEA89C4B04E56
DDA5DC588F89CEC1E280CD48000B13165D9AF495EE672829C5ADC42CAE6901A4F910A4DC406CFE61 | +| | 14 | 15C15542F044CC049F0E6550AE45EFA5DBD76D5298C34AE8D6CCC62440DA4543CA78058186A06C53
F4C74BCE7B4AC9F12E2D4DB884A6EE6E6CE79996035A2964E40A22F1F6CE3BB19F841279354B228C
5C1C95CD29A13884102378E180B5A489B064FD0050875ED44849108FA1A09218DF61A21A8FCB6B6A | +| 896 | 0 | 400A0A000B9A5DA2C21814C6FE024101E699344E89C46C773CEE08D14D5E225A94C5AECC6C12006
0B152FD950DCB59CDA552F2A85CE418D2CAA864D827503F49C2E2EF02243A088E5A187E5968019E4
5D57FC96845C9057BC419B3B69BB970F8FD4E035DA0C9C14BDAAE05A280FAC030800F14ADA8CEA | +| | 1 | 4455C04B07B8A84F81A05237092273284397638305F91971C9E867A0C86341AA5219F4DE9EB420D9
ECE4D4E2C2CCD5BBCC2CE155591D2EE949D2B3149D411C1C7A145E439875A7E3F8704C53E4C09828
4CC86FD4151C768EF771F840C4C477E019FC249436C267118646D4A07468864DEA4CA781825C505B | +| | 2 | 41A9C458FAEC095BE34D11978C96344F340205907066B8ABFC6EB6F53719583F96D0861C774129A8
4BC4F94C5EC2C1C44EA5908FB4DF46456992425E119C86E0A467EE436008DB4657B6D68892FD3886
548DF6781740991D7828A5B39452ACD101CCA411C4410AA0E880D38C0CD8A37C6B6D6477CC20B9ED | +| | 3 | 0C0660753C1A2C8DE6CEC2AC4C03F541CBA8CF27078D5E582BD62E3B87DD0C624543534410437383
809E0C066F2A5C676C352BFC7D35EC6E86CBF3E1CB0572E2D293B60A5C5334DE790BB6C7C43EB8418
39C0CABD205B006185069FD842AD5CB9226659ECA8EFFD5C16D2908678DAE4BEED04C4D35CE9E7821 | +| | 4 | 65CD384F2B9666D909DF68CDD637C33C1696F5E8197844A82AD6CD9823EE1E40DE62CD1272440E5A
524A2603CC24EE6498CCFA1C919F870458140D851A0CD0E571196974BDC30ED8918CAAEC12446ACA
CE0F4F080A6C9887D96703CD88C7E49AC3648D7F0BC72B7DC9B1A1D4B1CAF3A46943A680F849ED9A | +| | 5 | E52994D6BDC01558000D3F22E416BB651A5E194EEE823A4C05793E665C5A6BA77960FC1081B6355A
BA480753A0EE860434D01AC81DE4092403D05E12B0468A65A800C82447977C814A52326415FBE568
1BA286727FF095384C288DEAD496C4E41E99C62DA8B62102D420184487A48043E97B81C053041C72 | +| | 6 | 28ACC0A9E893A55F1CBBBCA24BDB83295E813168BEE80AA22148CD06F0F608B8AEF2E4C424004EEA5
B000E8C90CDBD46ACC5385110D1E470F8F66E6012706C025292C8D1F302955D2E11B64AC11B65AC0F
91B44981E19DC8129B6C2928687541187FDBFF5B7FA354814F523464FB138A54488970EB455CD05 | +| | 7 | BDBB40572F15AA8050CD6F44E23D8AB1A9D9157A909716E41BBFD6C0E884E10E58A4E27FCC45091 | + +| | | | +|--|----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | E689CC84D458D14B12FAF47CC4C0CA9DCA15873FD4FEC05AD00989BC06E24F6D4F82400EAF0B43C5
E285E2CF365E63448D42B0E20F89F461807055CCAADFDA123374CDC3B364F858064CD30C67710330 | +| | 8 | A1CDC0AC064A07BDE5F496CCAF3A3C91A98CFE182DD0C54F9ECCE25E981D129A8A23B630E8C78E0DA
58742533BB3D2A2FEEC1C139AC9DD60CE2083846F4B0C303E9E5999DB105E7E9C6F35326BE895580
4BC4AE86C4155D02966887724BCD8FC0E44DC118546BA6AF2F82EA4EE80447A418B8CE492CF49ECA | +| | 9 | EC1C57AADEC8FBBC0B4140BC8C1D38DAC1416C48D5B482C839C469803288B6454FA8718D80FE92AF
81BDE6EE147C5EBEDD8730D582C141C001730D43021360E25DC1769AEEDABD44F4E6F75CDC9018
74A2E6C88B460A49501CD946E5FE0725EC9C68F6DFAB1D74CD55CE3C909E9065863022100A8C2F03 | +| | 10 | 1CCD864CA6FDC0FD6AA18EE7B48A1F6B214645141D07AF691CD58C8F82DA596FC931023DBF026C0E
0282A1798C069848668CE08E82902E72BD6D46A381D8AA922DDA785A6858D85CCCF8F28FB8CDEF98
9B04606D9B08B8ACDD09CD5545EA4DDA4E548E5B587D1E894D50725E0968C0F949EEA3D5DBEC826D | +| | 11 | 9BD4603A5C0BAA644862019295B6F09CC05CAAEE86306DF955307116D1852005A98C8EFE844ED14C4
A49DC462F596130E492C7DCCC47D64FC0045EAFFD1E01CEAAF6C38255CB7ECB4446174CACA116ED8
5A7050B48ED5B178B8F2A722544C90720DC9961E0AD6B868AE9DB5E045C6CA35DEEEE08B9E6E58D | +| | 12 | C0A81E46262DE865209B11883FC6ECD70E049C8341EABAC7D8B8E615C2027A820887866E12B86F2A
FA70A8BD50A049203A1D7188006422598E461C27749329C00090916AFD453874AD4EAC9150B8C4AD
C5E25FD38AE19C8CA6A4CA1244BD37383AB8BE81181944579F93C3D3CB7E04C7977CC0600CBC6FFD | +| | 13 | 7124526DAED23B9E828FDD9B9E8B3D4C214E87148BE9DF3AE1890EEACB11569EAC09E5955A160CCE
A0A9EAD06B3C96B5A395A6B32A8CF1F1EED05ADB4EDDCF49882B202D1CD4BA67E248730D2280CC27
02D100406641C0E6B7F0910566C1AD0461A807CFE1BAE09EEE4660B55A4EEBC4EE122B0ECE694E8D | +| | 14 | C3AE1C4C5C0BF009AA4D4171F41786A49CC55A01C5C5CD9A56F342E9B870650E88A1A48D0AD96F66
8448A9210D83A655448F7AA2024D1DBCDB49ACC485C3EBCDD7494D5406D590FE5B74ED031C076588
168BC607880040641BB6D65E0F5FDA160C32C671639FA86DE4E36A1D7454B40C900A93DEE3B4E10F | + +# --- Annex D (informative): Change history + +| Change history | | | | | | | | +|----------------|--------|-----------|-----|-----|--------------------------------------------------------------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 14/01/00 | RAN_05 | RP-99591 | - | - | Approved at TSG RAN #5 and placed under Change Control | - | 3.0.0 | +| 14/01/00 | RAN_06 | RP-99691 | 001 | 02 | Primary and Secondary CCPCH in TDD | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99691 | 002 | 02 | Removal of Superframe for TDD | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99691 | 006 | - | Corrections to TS25.221 | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99691 | 007 | 1 | Clarifications for Spreading in UTRA TDD | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99691 | 008 | - | Transmission of TFCI bits for TDD | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99691 | 009 | - | Midamble Allocation in UTRA TDD | 3.0.0 | 3.1.0 | +| 14/01/00 | RAN_06 | RP-99690 | 010 | - | Introduction of the timeslot formats to the TDD specifications | 3.0.0 | 3.1.0 | +| 14/01/00 | - | - | - | - | Change history was added by the editor | 3.1.0 | 3.1.1 | +| 31/03/00 | RAN_07 | RP-000067 | 003 | 2 | Cycling of cell parameters | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000067 | 011 | - | Correction of Midamble Definition for TDD | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000067 | 012 | - | Introduction of the timeslot formats for RACH to the TDD specifications | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000067 | 013 | - | Paging Indicator Channel reference power | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000067 | 014 | 1 | Removal of Synchronisation Case 3 in TDD | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000067 | 015 | 1 | Signal Point Constellation | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000067 | 016 | - | Association between Midambles and Channelisation Codes | 3.1.1 | 3.2.0 | +| 31/03/00 | RAN_07 | RP-000067 | 017 | - | Removal of ODMA from the TDD specifications | 3.1.1 | 3.2.0 | +| 26/06/00 | RAN_08 | RP-000271 | 018 | 1 | Removal of the reference to ODMA | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000271 | 019 | - | Editorial changes in transport channels section | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000271 | 020 | 1 | TPC transmission for TDD | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000271 | 021 | - | Editorial modification of 25.221 | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000271 | 023 | - | Clarifications on TxDiversity for UTRA TDD | 3.2.0 | 3.3.0 | +| 26/06/00 | RAN_08 | RP-000271 | 024 | - | Clarifications on PCH and PICH in UTRA TDD | 3.2.0 | 3.3.0 | +| 23/09/00 | RAN_09 | RP-000344 | 022 | 1 | Correction to midamble generation in UTRA TDD | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000344 | 026 | 2 | Some corrections for TS25.221 | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000344 | 028 | - | Terminology regarding the beacon function | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000344 | 030 | 1 | TDD Access Bursts for HOV | 3.3.0 | 3.4.0 | +| 23/09/00 | RAN_09 | RP-000344 | 031 | 1 | Number of codes signalling for the DL common midamble case | 3.3.0 | 3.4.0 | +| 15/12/00 | RAN_10 | RP-000542 | 034 | - | Correction on TFCI & TPC Transmission | 3.4.0 | 3.5.0 | +| 15/12/00 | RAN_10 | RP-000542 | 035 | 1 | Clarifications on Midamble Associations | 3.4.0 | 3.5.0 | +| 15/12/00 | RAN_10 | RP-000542 | 036 | - | Clarification on PICH power setting | 3.4.0 | 3.5.0 | +| 16/03/01 | RAN_11 | - | - | - | Approved as Release 4 specification (v4.0.0) at TSG RAN #11 | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010062 | 033 | 2 | Correction to SCH section | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010062 | 037 | 1 | Bit Scrambling for TDD | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010062 | 039 | 1 | Corrections of PUSCH and PDSCH | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010062 | 040 | - | Alteration of SCH offsets to avoid overlapping Midamble | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010062 | 041 | - | Clarifications & Corrections for TS25.221 | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010062 | 045 | 1 | Corrections on the PRACH and clarifications on the midamble generation and the behaviour in case of an invalid TFI combination on the DCHs | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010062 | 046 | - | Clarification of TFCI transmission | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010062 | 048 | - | Corrections to Table 5.1b "Timeslot formats for the Uplink" | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010073 | 042 | 2 | Introduction of the Physical Node B Synchronization Channel | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010071 | 043 | 1 | Inclusion of 1.28Mcps TDD in TS 25.221 | 3.5.0 | 4.0.0 | +| 16/03/01 | RAN_11 | RP-010072 | 044 | - | Correction of beacon characteristics due to IPDLs | 3.5.0 | 4.0.0 | +| 15/06/01 | RAN_12 | RP-010336 | 051 | - | Clarification of Midamble Usage in TS25.221 | 4.0.0 | 4.1.0 | +| 15/06/01 | RAN_12 | RP-010336 | 053 | - | Addition to the abbreviation list, correction of references to tables and figures | 4.0.0 | 4.1.0 | +| 15/06/01 | RAN_12 | RP-010342 | 049 | - | Correction of spelling in definition of beacon characteristics | 4.0.0 | 4.1.0 | +| 15/06/01 | RAN_12 | RP-010342 | 055 | - | Correction of Note for PDSCH signalling methods | 4.0.0 | 4.1.0 | +| 21/09/01 | RAN_13 | RP-010522 | 057 | - | TFCI Terminology | 4.1.0 | 4.2.0 | +| 21/09/01 | RAN_13 | RP-010522 | 063 | - | Clarification of notations in TS25.221 and TS25.223 | 4.1.0 | 4.2.0 | +| 21/09/01 | RAN_13 | RP-010522 | 062 | - | Addition and correction of the reference | 4.1.0 | 4.2.0 | +| 21/09/01 | RAN_13 | RP-010528 | 058 | 1 | Corrections for TS 25.221 | 4.1.0 | 4.2.0 | +| 14/12/01 | RAN_14 | RP-010741 | 065 | 1 | Transmit Diversity for P-CCPCH and PICH | 4.2.0 | 4.3.0 | +| 14/12/01 | RAN_14 | RP-010741 | 067 | - | Clarification of midamble transmit power in TS25.221 | 4.2.0 | 4.3.0 | +| 14/12/01 | RAN_14 | RP-010746 | 059 | - | Bit Scrambling for 1.28 Mcps TDD | 4.2.0 | 4.3.0 | +| 14/12/01 | RAN_14 | RP-010746 | 068 | - | Transmit Diversity for P-CCPCH and PICH | 4.2.0 | 4.3.0 | +| 14/12/01 | RAN_14 | RP-010746 | 069 | - | Corrections of reference numbers in TS 25.221 | 4.2.0 | 4.3.0 | +| 08/03/02 | RAN_15 | RP-020049 | 071 | 2 | Clarification of spreading for UL physical channels | 4.3.0 | 4.4.0 | +| 08/03/02 | RAN_15 | RP-020049 | 073 | 1 | Common midamble allocation for beacon time slot | 4.3.0 | 4.4.0 | +| 08/03/02 | RAN_15 | RP-020049 | 075 | 3 | Correction to a transmission of paging indicators bits | 4.3.0 | 4.4.0 | +| 08/03/02 | RAN_15 | RP-020058 | 076 | 1 | CR to include HSDPA in TS25.221 | 4.3.0 | 5.0.0 | +| 07/06/02 | RAN_16 | RP-020434 | 080 | 2 | Clarification of shared channel functionality for TDD | 5.0.0 | 5.1.0 | +| 07/06/02 | RAN_16 | RP-020313 | 082 | - | Clarification of shared channel functionality for TDD | 5.0.0 | 5.1.0 | +| 07/06/02 | RAN_16 | RP-020317 | 081 | - | TxDiversity for HSDPA in TDD | 5.0.0 | 5.1.0 | +| 19/09/02 | RAN_17 | RP-020559 | 092 | 1 | Corrections to channelisation code mapping for 1.28 Mcps TDD | 5.1.0 | 5.2.0 | +| 19/09/02 | RAN_17 | RP-020576 | 094 | - | Correction to S-CCPCH description for 1.28 Mcps TDD | 5.1.0 | 5.2.0 | + +| Change history | | | | | | | | +|----------------|--------|-----------|------|-----|----------------------------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 19/09/02 | RAN_17 | RP-020579 | 104 | 2 | Corrections to transmit diversity mode for TDD beacon-function physical channels | 5.1.0 | 5.2.0 | +| 19/09/02 | RAN_17 | RP-020569 | 090 | 1 | Corrections to channelisation code mappings for 3.84 Mcps TDD | 5.1.0 | 5.2.0 | +| 19/09/02 | RAN_17 | RP-020572 | 097 | 2 | Corrections to transmit diversity mode for TDD beacon-function physical channels | 5.1.0 | 5.2.0 | +| 21/12/02 | RAN_18 | RP-020848 | 105 | - | Correction of the number of transport channels in clause 4.1 | 5.2.0 | 5.3.0 | +| 21/12/02 | RAN_18 | RP-020852 | 107 | - | Editorial modification to the section numberings | 5.2.0 | 5.3.0 | +| 26/03/03 | RAN_19 | RP-030138 | 109 | 3 | Clarification of number of midamble shifts in different time slots | 5.3.0 | 5.4.0 | +| 26/03/03 | RAN_19 | RP-030138 | 110 | 1 | Correction to applicable HS-SICH burst types and timeslot formats | 5.3.0 | 5.4.0 | +| 26/03/03 | RAN_19 | RP-030138 | 111 | - | Correction to HS-SCCH minimum timing requirement for UTRA TDD (3.84 Mcps Option) | 5.3.0 | 5.4.0 | +| 26/03/03 | RAN_19 | RP-030138 | 112 | 3 | Miscellaneous Corrections | 5.3.0 | 5.4.0 | +| 26/03/03 | RAN_19 | RP-030138 | 113 | - | HSDPA timing requirements | 5.3.0 | 5.4.0 | +| 24/06/03 | RAN_20 | RP-030275 | 114 | 1 | Corrections to field coding of TPC for support of HS-SICH (3.84Mcps TDD) | 5.4.0 | 5.5.0 | +| 13/01/04 | RAN_22 | - | - | - | Created for M.1457 update | 5.5.0 | 6.0.0 | +| 09/06/04 | RAN_24 | RP-040235 | 116 | 2 | Addition of TSTD for S-CCPCH in 3.84Mcps TDD | 6.0.0 | 6.1.0 | +| 13/12/04 | RAN_26 | RP-040451 | 117 | - | Introduction of MICH | 6.1.0 | 6.2.0 | +| 14/03/05 | RAN_27 | RP-050089 | 118 | - | Release 6 HS-DSCH operation without a DL DPCH for 3.84Mcps TDD | 6.2.0 | 6.3.0 | +| 16/06/05 | RAN_28 | RP-050240 | 124 | 1 | Correction to transmission of SS for 1.28Mcps TDD | 6.3.0 | 6.4.0 | +| 16/06/05 | RAN_28 | RP-050255 | 127 | 1 | Correction to the examples of the association of UL SS commands to UL uplink time slots | 6.3.0 | 6.4.0 | +| 16/06/05 | RAN_28 | RP-050239 | 130 | 1 | Correction to transmission of TPC for 1.28Mcps TDD | 6.3.0 | 6.4.0 | +| 16/06/05 | RAN_28 | RP-050255 | 133 | 1 | Correction to the examples of the association of UL TPC commands to UL uplink time slot and CCTrCH pairs | 6.3.0 | 6.4.0 | +| 29/06/05 | - | - | - | - | Editorial revision to the incorrect implementation of CR127r1 and CR133r1 | 6.4.0 | 6.4.1 | +| 26/09/05 | RAN_29 | RP-050448 | 0134 | - | Change of burst type to burst format | 6.4.1 | 6.5.0 | +| 20/03/06 | RAN_31 | RP-060078 | 0135 | - | Introduction of the Physical Layer Common Control Channel (PLCCH) | 6.5.0 | 7.0.0 | +| 20/03/06 | RAN_31 | RP-060079 | 0136 | - | Introduction of 7.68Mcps TDD option | 6.5.0 | 7.0.0 | +| 29/09/06 | RAN_33 | RP-060492 | 0138 | - | Introduction of E-DCH for 3.84Mcps and 7.68Mcps TDD | 7.0.0 | 7.1.0 | +| 09/03/07 | RAN_35 | RP-070118 | 0139 | 2 | Introduction of E-DCH for 1.28Mcps TDD | 7.1.0 | 7.2.0 | +| 30/05/07 | RAN_36 | RP-070385 | 0140 | 2 | Support for MBSFN operation | 7.2.0 | 7.3.0 | +| 30/05/07 | RAN_36 | RP-070386 | 0142 | - | Support for LCR TDD MBSFN operation | 7.2.0 | 7.3.0 | +| 30/05/07 | RAN_36 | RP-070386 | 0143 | - | Addition of spreading factor 2 for MBSFN time slot for 1.28Mcps TDD | 7.2.0 | 7.3.0 | +| 11/09/07 | RAN_37 | RP-070650 | 0144 | - | Introduction of multi-frequency operation for 1.28Mcps TDD | 7.3.0 | 7.4.0 | +| 11/09/07 | RAN_37 | RP-070647 | 0145 | - | TFCI mapping for S-CCPCH and 16QAM for 1.28Mcps TDD MBSFN | 7.3.0 | 7.4.0 | +| 27/11/07 | RAN_38 | RP-070943 | 0148 | 2 | More improvement on dedicated carrier for 1.28Mcps TDD MBMS | 7.4.0 | 7.5.0 | +| 04/03/08 | RAN_39 | RP-080140 | 0150 | - | Clarification of uplink multicode capability for 1.28Mcps TDD EUL | 7.5.0 | 7.6.0 | +| 04/03/08 | RAN_39 | RP-080140 | 0151 | - | EUL power control improvements for 1.28Mcps TDD | 7.5.0 | 7.6.0 | +| 04/03/08 | RAN_39 | RP-080140 | 0152 | - | E-AGCH timing for 1.28Mcps TDD EUL | 7.5.0 | 7.6.0 | +| 04/03/08 | RAN_39 | RP-080140 | 0153 | - | Clarification of the description about E-PUCH for 1.28Mcps TDD EUL | 7.5.0 | 7.6.0 | +| 04/03/08 | RAN_39 | - | - | - | Creation of Release 8 further to RAN_39 decision | 7.6.0 | 8.0.0 | +| 28/05/08 | RAN_40 | RP-080356 | 0155 | - | Introduction of 64QAM for 1.28 Mcps TDD HSDPA | 8.0.0 | 8.1.0 | +| 28/05/08 | RAN_40 | RP-080348 | 0157 | - | Applicability of sync case 2 | 8.0.0 | 8.1.0 | +| 09/09/08 | RAN_41 | RP-080663 | 0161 | - | Modification of the timing requirement between HS-SCCH and HS-PDSCH for 1.28Mcps TDD | 8.1.0 | 8.2.0 | +| 09/09/08 | RAN_41 | RP-080662 | 0163 | - | Correction on the time slot format for LCR TDD MBSFN | 8.1.0 | 8.2.0 | +| 03/12/08 | RAN_42 | RP-080977 | 166 | - | Correction on FPACH misalignment for 1.28Mcps TDD | 8.2.0 | 8.3.0 | +| 03/12/08 | RAN_42 | RP-080976 | 168 | - | Correction of E-PUCH TPC description for 1.28Mcps TDD | 8.2.0 | 8.3.0 | +| 03/12/08 | RAN_42 | RP-080987 | 169 | 1 | Introduction of the Enhanced CELL_FACH, CELL_PCH, URA_PCH state for 1.28Mcps TDD | 8.2.0 | 8.3.0 | +| 03/12/08 | RAN_42 | RP-081118 | 170 | 1 | Support for 3.84 Mcps MBSFN IMB operation | 8.2.0 | 8.3.0 | +| 03/03/09 | RAN_43 | RP-090230 | 172 | - | Clarification of uplink multicode transmission for 1.28Mcps TDD | 8.3.0 | 8.4.0 | +| 03/03/09 | RAN_43 | RP-090239 | 173 | - | TFI for Secondary CCPCH frame type 2 with 16QAM | 8.3.0 | 8.4.0 | +| 03/03/09 | RAN_43 | RP-090241 | 174 | - | Introducing of MIMO for 1.28Mcps TDD | 8.3.0 | 8.4.0 | +| 03/03/09 | RAN_43 | RP-090240 | 175 | 1 | Introduction CPC for 1.28Mcps TDD | 8.3.0 | 8.4.0 | +| 03/03/09 | RAN_43 | RP-090231 | 177 | - | Editorial correction for annex CB & CC | 8.3.0 | 8.4.0 | +| 03/03/09 | RAN_43 | RP-090239 | 178 | - | Specification of T-CPICH sequences for MBSFN IMB | 8.3.0 | 8.4.0 | +| 26/05/09 | RAN_44 | RP-090531 | 179 | - | Minor corrections for MBSFN IMB | 8.4.0 | 8.5.0 | +| 26/05/09 | RAN_44 | RP-090533 | 180 | - | Corrections of HS-PDSCH timeslot formats for 1.28Mcps TDD | 8.4.0 | 8.5.0 | +| 26/05/09 | RAN_44 | RP-090526 | 182 | - | E-PUCH timeslot format parameter corrections for 1.28Mcps TDD | 8.4.0 | 8.5.0 | +| 15/09/09 | RAN_45 | RP-090893 | 184 | - | Clarification of the transmission of SS and TPC in CPC for 1.28Mcps TDD | 8.5.0 | 8.6.0 | +| 15/09/09 | RAN_45 | RP-090893 | 185 | 1 | Change of the timing definition in CELL-PCH for 1.28Mcps TDD | 8.5.0 | 8.6.0 | + +| Change history | | | | | | | | +|----------------|--------|-----------|-----|-----|-----------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 01/12/09 | RAN_46 | RP-091166 | 189 | 1 | Correction on E-AGCH and SPS E-PUCH Association and Timing for 1.28Mcps TDD | 8.6.0 | 8.7.0 | +| 01/12/09 | RAN_46 | RP-091166 | 197 | - | Timing association between HS-SCCH and SPS HS-PDSCH for LCR TDD | 8.6.0 | 8.7.0 | +| 01/12/09 | RAN_46 | RP-091176 | 195 | 1 | Modification to HSPA timing relationship for TS0 for 1.28Mcps TDD | 8.7.0 | 9.0.0 | +| 16/03/10 | RAN_47 | RP-100202 | 200 | 1 | Clarification of timing association between HS | 9.0.0 | 9.1.0 | +| 16/03/10 | RAN_47 | RP-100203 | 202 | 1 | Clarification of TPC and SS transmission on HS | 9.0.0 | 9.1.0 | +| 01/06/10 | RAN_48 | RP-100586 | 204 | - | Clarification of HS-SCCH/HS-DSCH/HS-SICH association for HS-SCCH order | 9.1.0 | 9.2.0 | +| 01/06/10 | RAN_48 | RP-100588 | 206 | 1 | Resource sharing between scheduled and non-scheduled E-HICHs for LCR TDD | 9.1.0 | 9.2.0 | +| 01/06/10 | RAN_48 | RP-100587 | 208 | 1 | Clarification for support of an E-HICH pair for 1.28Mcps TDD | 9.1.0 | 9.2.0 | +| 20/07/10 | - | - | - | - | Correction of version references in change history table | 9.2.0 | 9.2.1 | +| 14/09/10 | RAN_49 | RP-100895 | 210 | - | Correction of E-DCH Physical Uplink Channel for 1.28Mcps TDD | 9.2.1 | 9.3.0 | +| 07/12/10 | RAN_50 | RP-101317 | 211 | 2 | Introduction of MC-HSUPA for 1.28Mcps TDD | 9.3.0 | 10.0.0 | +| 07/12/10 | RAN_50 | RP-101319 | 212 | 1 | Introduction of MU-MIMO for 1.28Mcps TDD | 9.3.0 | 10.0.0 | +| 15/09/11 | RAN_53 | RP-111227 | 220 | 2 | Clarifications on HSUPA for LCR TDD | 10.0.0 | 10.1.0 | +| 05/12/11 | RAN_54 | RP-111664 | 224 | - | TPC on Non-scheduled E-PUCH for LCR TDD | 10.1.0 | 10.2.0 | +| 2012-09 | SP_57 | - | - | - | Update to Rel-11 version (MCC) | 10.2.0 | 11.0.0 | +| 2014-09 | SP_65 | - | - | - | Update to Rel-12 version (MCC) | 11.0.0 | 12.0.0 | +| 2015-12 | SP_70 | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | RP-75 | - | - | - | - | Promotion to Release 14 without technical change (MCC) | 14.0.0 | +| 2018-06 | RP-80 | - | - | - | - | Promotion to Release 15 without technical change (MCC) | 15.0.0 | +| 2020-07 | RP-88e | - | - | - | - | Upgrade to Rel-16 version without technical change | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25322/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/25_series/25322/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7637a5ed53007a98fc57b3805a3421c2204e2200 --- /dev/null +++ b/marked/Rel-16/25_series/25322/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f2cd5f94217bf8ea580b9bbd1e8866b3164642eb40753450813c2a9a3303484 +size 277508 diff --git a/marked/Rel-16/25_series/25322/265d5cb06b401cf460a20fd2c93fd6d5_img.jpg b/marked/Rel-16/25_series/25322/265d5cb06b401cf460a20fd2c93fd6d5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..410501debd0d3d3f3deb0a2392fb7356e37859b0 --- /dev/null +++ b/marked/Rel-16/25_series/25322/265d5cb06b401cf460a20fd2c93fd6d5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b08badb4cfb6c6435b27aab780a922399e28012f1accc4f5833c8d9aeea24fa +size 24664 diff --git a/marked/Rel-16/25_series/25322/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-16/25_series/25322/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82974890a03c7ac791e571a7312817b9adfbba1a --- /dev/null +++ b/marked/Rel-16/25_series/25322/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aed1f40b26d5f7a1c594d5816947260156a2a3f1e843d29568f62195a7cc6023 +size 72462 diff --git a/marked/Rel-16/25_series/25322/3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg b/marked/Rel-16/25_series/25322/3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3b56d6c5ed3584bf8248a6086dc0c50397a4a965 --- /dev/null +++ b/marked/Rel-16/25_series/25322/3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:deac6e192f7bb03d723ef36f6e6ed8164fefad2ba58f93238a75dbccf1a5ad71 +size 30773 diff --git a/marked/Rel-16/25_series/25322/410562339ce067fdc6fa41940c118658_img.jpg b/marked/Rel-16/25_series/25322/410562339ce067fdc6fa41940c118658_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5964b73e4f373f7adc64f1a9891ededbc90ddd28 --- /dev/null +++ b/marked/Rel-16/25_series/25322/410562339ce067fdc6fa41940c118658_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3cff03c481338e1d6a8b669c709865c0691468e57adb04bba28662a46e33110b +size 86239 diff --git a/marked/Rel-16/25_series/25322/4ca4ef49a4f79d5621932651f7ae3f5e_img.jpg b/marked/Rel-16/25_series/25322/4ca4ef49a4f79d5621932651f7ae3f5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9d92fde1b6c7a597d71005a73c4dd8c9f73c58c --- /dev/null +++ b/marked/Rel-16/25_series/25322/4ca4ef49a4f79d5621932651f7ae3f5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:414aae1630dafd00ffd48ea53045dc23ad00d6a7f9ef08da2726570135eeb9e8 +size 10573 diff --git a/marked/Rel-16/25_series/25322/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/25_series/25322/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44f9979fd41f22ab1e667900aac7aae09938361f --- /dev/null +++ b/marked/Rel-16/25_series/25322/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b99e53938a50c356a8540b6c977cb303e03436d183a8a36ce7d46a086d3a305b +size 90528 diff --git a/marked/Rel-16/25_series/25322/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg b/marked/Rel-16/25_series/25322/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b537e847f6b92bffce9d0b8f786951bb654ca2f1 --- /dev/null +++ b/marked/Rel-16/25_series/25322/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4fcf52c79a6a9c5b31343ebf0154e5bfdf130c7d0f2e1ad39e4bd2232ba569ad +size 10894 diff --git a/marked/Rel-16/25_series/25322/759c7d62402f0b4651ddce292be5bdef_img.jpg b/marked/Rel-16/25_series/25322/759c7d62402f0b4651ddce292be5bdef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a9465b30df03ee5cce40551823c9b6b66bfc0e6 --- /dev/null +++ b/marked/Rel-16/25_series/25322/759c7d62402f0b4651ddce292be5bdef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f79468c52fd4e86bdc0a28c2bc715f8a7dc0b3fb90019999bed0aa76853a17b +size 14351 diff --git a/marked/Rel-16/25_series/25322/7f17c430b9598e4d748a8041457810b3_img.jpg b/marked/Rel-16/25_series/25322/7f17c430b9598e4d748a8041457810b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e774162c2ea6c77e60d8457b82b609227b5e8006 --- /dev/null +++ b/marked/Rel-16/25_series/25322/7f17c430b9598e4d748a8041457810b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:828bf395685799e7c0bcfeeb7042c0d33fcb8bf1cc2fcb38a012d04941acae1a +size 84761 diff --git a/marked/Rel-16/25_series/25322/8395ccdee8a80af834aca2bdfd7f9a9b_img.jpg b/marked/Rel-16/25_series/25322/8395ccdee8a80af834aca2bdfd7f9a9b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b05ec26757470cab461d7244a0e92521aa75800f --- /dev/null +++ b/marked/Rel-16/25_series/25322/8395ccdee8a80af834aca2bdfd7f9a9b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:278381b46d396633e457e0927f05ea2e79e88e86da3000ff972b4d709cad6583 +size 14794 diff --git a/marked/Rel-16/25_series/25322/9b686adccf125267a013fa25721231a3_img.jpg b/marked/Rel-16/25_series/25322/9b686adccf125267a013fa25721231a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1a3b014ca324bd616d8365bc5a0785be7980d97 --- /dev/null +++ b/marked/Rel-16/25_series/25322/9b686adccf125267a013fa25721231a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3fdbe408e25fac69db74a702ea75cf8b4ef7bac02b58266361a16bcfbefcec4 +size 2946 diff --git a/marked/Rel-16/25_series/25322/9b9262a549828579ab904148450734f6_img.jpg b/marked/Rel-16/25_series/25322/9b9262a549828579ab904148450734f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5ff3c9932d460bd128a6f450e25c867528acb4e --- /dev/null +++ b/marked/Rel-16/25_series/25322/9b9262a549828579ab904148450734f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb4b0f1ee77563639863a6eaf8f757ce17ea54b193d2bf38836a570ce0b500f5 +size 10807 diff --git a/marked/Rel-16/25_series/25322/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg b/marked/Rel-16/25_series/25322/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..381ffab7ba457009bc53757eff51b2e9337590dd --- /dev/null +++ b/marked/Rel-16/25_series/25322/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba59b66eed970cfae524e88009cf2d547f31de93ae75c756e2b474ee06721805 +size 16543 diff --git a/marked/Rel-16/25_series/25322/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/25_series/25322/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e0483d3e42c2b885014c64aef99de72b95c77c2 --- /dev/null +++ b/marked/Rel-16/25_series/25322/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b1daa1129ba1ed3237f5136d4fcfa57c3b48065d661c25646a9f691310ca4f3 +size 63545 diff --git a/marked/Rel-16/25_series/25322/b5987d63203a5fa601921039922ac520_img.jpg b/marked/Rel-16/25_series/25322/b5987d63203a5fa601921039922ac520_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72bdad40071a9d6768e7093fb13b5f87af49855f --- /dev/null +++ b/marked/Rel-16/25_series/25322/b5987d63203a5fa601921039922ac520_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:403689ebe3cb93a49dfde4219e83b6a1e8285abafc9a271a58bb302733fe7dc6 +size 36565 diff --git a/marked/Rel-16/25_series/25322/bb3063a33c89b248574f64b6d8dfc404_img.jpg b/marked/Rel-16/25_series/25322/bb3063a33c89b248574f64b6d8dfc404_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5f1bf39986906eb1b530f8bfa783801ee4f5e65 --- /dev/null +++ b/marked/Rel-16/25_series/25322/bb3063a33c89b248574f64b6d8dfc404_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02c94a2430458124b3cb96af2c93c02b46a42acd361445488798e6cf04fbd682 +size 11589 diff --git a/marked/Rel-16/25_series/25322/d6015fcef74bce83d04acd2e17b4fc15_img.jpg b/marked/Rel-16/25_series/25322/d6015fcef74bce83d04acd2e17b4fc15_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c467add410a0789edfe37317bd5d0d65863b427 --- /dev/null +++ b/marked/Rel-16/25_series/25322/d6015fcef74bce83d04acd2e17b4fc15_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06fe65061d71c75d5c055e4aa723ea8d04b81330fa4539e2f539c22c23b8bfe3 +size 116361 diff --git a/marked/Rel-16/25_series/25322/db5ab5d386827a5d5f5fad0f45612b90_img.jpg b/marked/Rel-16/25_series/25322/db5ab5d386827a5d5f5fad0f45612b90_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f7a932ae09091835ec76fc2de9b7bbc1a451088 --- /dev/null +++ b/marked/Rel-16/25_series/25322/db5ab5d386827a5d5f5fad0f45612b90_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:887674700b45cf1f56c3c15e47b880d2e9e43ebd4072cc3f11f31f26b7c033a7 +size 15581 diff --git a/marked/Rel-16/25_series/25322/e05c1a13b44ab41505609d82b00cf4df_img.jpg b/marked/Rel-16/25_series/25322/e05c1a13b44ab41505609d82b00cf4df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33e273709ea689e19f61bddf6611dbcdb66c7e4e --- /dev/null +++ b/marked/Rel-16/25_series/25322/e05c1a13b44ab41505609d82b00cf4df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8bd9f833a1688eaa5e5013cece55ddae5b1ca5b74d577daa74dea9dda2b0995 +size 26849 diff --git a/marked/Rel-16/25_series/25322/e7010c66da16316c2935dfbbef5056b3_img.jpg b/marked/Rel-16/25_series/25322/e7010c66da16316c2935dfbbef5056b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ae2dbce851105550cea77f3499fd1b16f80aec5 --- /dev/null +++ b/marked/Rel-16/25_series/25322/e7010c66da16316c2935dfbbef5056b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f416bddb2e1185f87955a4c8864fc3b612bfbc9aa2981e52bffbe46a6e7b571 +size 19617 diff --git a/marked/Rel-16/25_series/25322/e90987faabad6a6665cd8ed1151dc474_img.jpg b/marked/Rel-16/25_series/25322/e90987faabad6a6665cd8ed1151dc474_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..706ec5ae668b0eedf26768164c7c420577529ff2 --- /dev/null +++ b/marked/Rel-16/25_series/25322/e90987faabad6a6665cd8ed1151dc474_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f53b56d46fcf95f91241fb35cfd341779687b4aa79d0f6c5f944008a259212f8 +size 31605 diff --git a/marked/Rel-16/25_series/25322/raw.md b/marked/Rel-16/25_series/25322/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c046941e971104569847d8a73ec148a4946ddbb4 --- /dev/null +++ b/marked/Rel-16/25_series/25322/raw.md @@ -0,0 +1,3716 @@ + + + + + + +# Contents + +| | | +|---------------------------------------------------------------|----| +| Foreword ..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Definitions and abbreviations ..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Abbreviations ..... | 8 | +| 4 General..... | 9 | +| 4.1 Objective ..... | 9 | +| 4.2 Overview of the RLC sublayer architecture..... | 10 | +| 4.2.1 Model of the RLC sublayer ..... | 10 | +| 4.2.1.1 Transparent mode (TM) RLC entities ..... | 12 | +| 4.2.1.1.1 Transmitting TM RLC entity ..... | 12 | +| 4.2.1.1.2 Receiving TM RLC entity..... | 12 | +| 4.2.1.2 Unacknowledged mode (UM) RLC entities ..... | 13 | +| 4.2.1.2.1 Transmitting UM RLC entity..... | 14 | +| 4.2.1.2.2 Receiving UM RLC entity ..... | 15 | +| 4.2.1.3 Acknowledged mode (AM) RLC entity ..... | 15 | +| 4.2.1.3.1 Transmitting side..... | 16 | +| 4.2.1.3.2 Receiving side ..... | 17 | +| 5 Functions..... | 17 | +| 6 Services provided to upper layers ..... | 18 | +| 6.1 Mapping of services/functions onto logical channels ..... | 19 | +| 7 Services expected from MAC ..... | 21 | +| 8 Elements for layer-to-layer communication ..... | 21 | +| 8.1 Primitives between RLC and upper layers..... | 21 | +| 8.2 Primitive parameters ..... | 23 | +| 9 Elements for peer-to-peer communication..... | 24 | +| 9.1 Protocol data units ..... | 24 | +| 9.1.1 Data PDUs ..... | 24 | +| 9.1.2 Control PDUs ..... | 25 | +| 9.2 Formats and parameters ..... | 25 | +| 9.2.1 Formats ..... | 25 | +| 9.2.1.1 General..... | 26 | +| 9.2.1.2 TMD PDU..... | 26 | +| 9.2.1.3 UMD PDU ..... | 26 | +| 9.2.1.4 AMD PDU ..... | 27 | +| 9.2.1.5 STATUS PDU ..... | 27 | +| 9.2.1.6 Piggybacked STATUS PDU..... | 28 | +| 9.2.1.7 RESET, RESET ACK PDU..... | 28 | +| 9.2.2 Parameters ..... | 28 | +| 9.2.2.1 D/C field ..... | 29 | +| 9.2.2.2 PDU Type ..... | 29 | +| 9.2.2.3 Sequence Number (SN) ..... | 29 | +| 9.2.2.4 Polling bit (P)..... | 29 | +| 9.2.2.5 Extension bit (E) ..... | 29 | +| 9.2.2.6 Reserved 1 (R1)..... | 30 | +| 9.2.2.7 Header Extension Type (HE)..... | 30 | +| 9.2.2.8 Length Indicator (LI) ..... | 30 | +| 9.2.2.9 Data field..... | 34 | +| 9.2.2.10 Padding (PAD)..... | 36 | +| 9.2.2.11 SUFI..... | 36 | +| 9.2.2.11.1 The No More Data super-field ..... | 37 | +| 9.2.2.11.2 The Acknowledgement super-field ..... | 37 | + +| | | | +|------------|-----------------------------------------------------------------------------------|----| +| 9.2.2.11.3 | The Window Size super-field..... | 37 | +| 9.2.2.11.4 | The List super-field..... | 38 | +| 9.2.2.11.5 | The Bitmap super-field..... | 38 | +| 9.2.2.11.6 | The Relative List super-field..... | 39 | +| 9.2.2.11.7 | The Move Receiving Window Acknowledgement super-field..... | 40 | +| 9.2.2.11.8 | The Move Receiving Window (MRW) super-field ..... | 40 | +| 9.2.2.11.9 | The Poll (POLL) super-field ..... | 41 | +| 9.2.2.12 | Reserved 2 (R2) ..... | 41 | +| 9.2.2.13 | Reset Sequence Number (RSN)..... | 41 | +| 9.2.2.14 | Hyper Frame Number Indicator (HFNI)..... | 42 | +| 9.3 | Protocol states ..... | 42 | +| 9.3.1 | State model for transparent mode entities ..... | 42 | +| 9.3.1.1 | NULL State..... | 42 | +| 9.3.1.2 | DATA_TRANSFER_READY State ..... | 42 | +| 9.3.2 | State model for unacknowledged mode entities ..... | 42 | +| 9.3.2.1 | NULL State..... | 42 | +| 9.3.2.2 | DATA_TRANSFER_READY State ..... | 43 | +| 9.3.2.3 | LOCAL_SUSPEND State ..... | 43 | +| 9.3.3 | State model for acknowledged mode entities ..... | 44 | +| 9.3.3.1 | NULL State..... | 44 | +| 9.3.3.2 | DATA_TRANSFER_READY State ..... | 44 | +| 9.3.3.3 | RESET_PENDING State..... | 44 | +| 9.3.3.4 | LOCAL_SUSPEND State ..... | 46 | +| 9.3.3.5 | RESET_AND_SUSPEND State ..... | 46 | +| 9.4 | State variables ..... | 46 | +| 9.5 | Timers..... | 49 | +| 9.6 | Protocol Parameters..... | 51 | +| 9.7 | Specific functions..... | 52 | +| 9.7.1 | Polling function for acknowledged mode..... | 52 | +| 9.7.2 | STATUS transmission for acknowledged mode ..... | 54 | +| 9.7.3 | SDU discard function for acknowledged, unacknowledged, and transparent mode ..... | 55 | +| 9.7.3.1 | Timer based discard, with explicit signalling ..... | 55 | +| 9.7.3.2 | Timer based discard, without explicit signalling ..... | 56 | +| 9.7.3.3 | SDU discard after MaxDAT number of transmissions..... | 56 | +| 9.7.3.4 | No_discard after MaxDAT number of transmissions..... | 56 | +| 9.7.3.5 | SDU discard not configured ..... | 56 | +| 9.7.4 | Void..... | 57 | +| 9.7.5 | Local Suspend function for acknowledged and unacknowledged mode..... | 57 | +| 9.7.6 | RLC Stop, RLC Continue function for acknowledged and unacknowledged mode..... | 57 | +| 9.7.7 | RLC re-establishment function for acknowledged and unacknowledged mode ..... | 58 | +| 9.7.8 | Ciphering for acknowledged and unacknowledged mode..... | 60 | +| 9.7.9 | Reconfiguration of RLC parameters by upper layers ..... | 60 | +| 9.7.10 | Duplicate avoidance and reordering for unacknowledged mode ..... | 61 | +| 10 | Handling of unknown, unforeseen and erroneous protocol data ..... | 63 | +| 10.1 | Erroneous Sequence Number ..... | 63 | +| 10.2 | Inconsistent status indication ..... | 63 | +| 10.3 | Invalid PDU format..... | 63 | +| 10.4 | RLC PDU with CRC error ..... | 63 | +| 11 | Elementary procedures..... | 63 | +| 11.1 | Transparent mode data transfer procedure ..... | 64 | +| 11.1.1 | General ..... | 64 | +| 11.1.2 | Transmission of TMD PDU ..... | 64 | +| 11.1.2.1 | TMD PDU contents to set..... | 64 | +| 11.1.2.2 | Submission of TMD PDUs to the lower layer ..... | 64 | +| 11.1.3 | Reception of TMD PDU..... | 65 | +| 11.1.4 | Abnormal cases ..... | 65 | +| 11.1.4.1 | Void ..... | 65 | +| 11.1.4.2 | SDU discard without explicit signalling ..... | 65 | +| 11.2 | Unacknowledged mode data transfer procedure ..... | 65 | +| 11.2.1 | General ..... | 65 | + +| | | | +|------------|------------------------------------------------------------------------------------------------|----| +| 11.2.2 | Transmission of UMD PDU ..... | 66 | +| 11.2.2.1 | UMD PDU contents to set ..... | 66 | +| 11.2.2.2 | Submission of UMD PDUs to the lower layer ..... | 66 | +| 11.2.3 | Reception of UMD PDU ..... | 67 | +| 11.2.3.1 | SDU discard and re-assembly ..... | 67 | +| 11.2.3.2 | Out of sequence SDU delivery ..... | 68 | +| 11.2.4 | Abnormal cases ..... | 69 | +| 11.2.4.1 | Length Indicator value reserved for UMD PDU ..... | 69 | +| 11.2.4.2 | Invalid length indicator value ..... | 69 | +| 11.2.4.3 | SDU discard without explicit signalling ..... | 69 | +| 11.2.4.4 | Invalid PDU size ..... | 69 | +| 11.3 | Acknowledged mode data transfer procedure ..... | 69 | +| 11.3.1 | General ..... | 69 | +| 11.3.2 | Transmission of AMD PDU ..... | 70 | +| 11.3.2.1 | AMD PDU contents to set ..... | 71 | +| 11.3.2.1.1 | Setting of the Polling bit ..... | 72 | +| 11.3.2.1.2 | Void ..... | 72 | +| 11.3.2.2 | Submission of AMD PDUs to lower layer ..... | 72 | +| 11.3.3 | Reception of AMD PDU by the Receiver ..... | 72 | +| 11.3.3a | Reached maximum number of attempts ..... | 73 | +| 11.3.4 | Abnormal cases ..... | 73 | +| 11.3.4.1 | Void ..... | 73 | +| 11.3.4.2 | Receiving an AMD PDU outside the reception window ..... | 73 | +| 11.3.4.3 | Timer_Discard timeout ..... | 74 | +| 11.3.4.3.1 | SDU discard with explicit signalling ..... | 74 | +| 11.3.4.4 | Void ..... | 74 | +| 11.3.4.5 | Invalid length indicator value ..... | 74 | +| 11.3.4.6 | Length Indicator value reserved for AMD PDU ..... | 74 | +| 11.3.4.7 | Void ..... | 74 | +| 11.3.4.8 | Receiving an AMD PDU within the reception window more than once (Handling of Duplicates) ..... | 74 | +| 11.3.4.9 | Full Buffer Behavior ..... | 74 | +| 11.3.4.10 | Invalid PDU size ..... | 75 | +| 11.3.5 | Transmission of POLL SUFI ..... | 75 | +| 11.4 | RLC reset procedure ..... | 75 | +| 11.4.1 | General ..... | 75 | +| 11.4.2 | Initiation ..... | 75 | +| 11.4.2.1 | RESET PDU contents to set ..... | 76 | +| 11.4.3 | Reception of the RESET PDU by the Receiver ..... | 76 | +| 11.4.3.1 | RESET ACK PDU contents to set ..... | 77 | +| 11.4.4 | Reception of the RESET ACK PDU by the Sender ..... | 77 | +| 11.4.4a | Reached maximum number of attempts ..... | 78 | +| 11.4.5 | Abnormal cases ..... | 78 | +| 11.4.5.1 | Timer_RST timeout ..... | 78 | +| 11.4.5.2 | Void ..... | 78 | +| 11.4.5.3 | Reception of the RESET PDU by the Sender ..... | 78 | +| 11.5 | STATUS report transfer procedure ..... | 79 | +| 11.5.1 | General ..... | 79 | +| 11.5.2 | Initiation ..... | 79 | +| 11.5.2.1 | Piggybacked STATUS PDU ..... | 79 | +| 11.5.2.2 | STATUS PDU contents to set ..... | 79 | +| 11.5.2.3 | Submission of STATUS PDUs to the lower layer ..... | 80 | +| 11.5.3 | Reception of the STATUS PDU by the Sender ..... | 81 | +| 11.5.4 | Abnormal cases ..... | 81 | +| 11.5.4.1 | Void ..... | 81 | +| 11.6 | SDU discard with explicit signalling procedure ..... | 81 | +| 11.6.1 | General ..... | 81 | +| 11.6.2 | Initiation ..... | 82 | +| 11.6.2.1 | Void ..... | 82 | +| 11.6.2.2 | STATUS PDU contents to set ..... | 83 | +| 11.6.3 | Reception of the STATUS PDU by the Receiver ..... | 84 | +| 11.6.3.1 | STATUS PDU contents to set ..... | 84 | +| 11.6.4 | Termination ..... | 85 | + +11.6.5 Expiration of timer Timer\_MRW..... 85 +11.6.6 Abnormal cases ..... 85 +11.6.6.1 Reception of obsolete/corrupted MRW SUFI by the Receiver ..... 85 +11.6.6.2 Void ..... 86 +11.6.6.3 Reception of obsolete/corrupted MRW\_ACK SUFI by the Sender ..... 86 +11.7 Void..... 86 +11.8 Void..... 86 +Annex A (informative): Change history..... 87 + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the Radio Link Control protocol for the UE-UTRAN radio interface. + +Features for the current Release: + +- Transparent mode. +- Unacknowledged mode. +- Acknowledged mode. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TS 25.401: "UTRAN Overall Description". +- [2] 3GPP TR 25.990: "Vocabulary for UTRAN". +- [3] 3GPP TS 25.301: "Radio Interface Protocol Architecture". +- [4] 3GPP TS 25.302: "Services provided by the Physical Layer". +- [5] 3GPP TS 25.303: "Interlayer procedures in Connected Mode". +- [6] 3GPP TS 25.304: "UE Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode". +- [7] 3GPP TS 25.321: "Medium Access Control (MAC); protocol specification". +- [8] 3GPP TS 25.331: "Radio Resource Control (RRC); protocol specification". +- [9] 3GPP TS 33.102: "3G security; Security architecture". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in [2] apply. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|------|---------------------------| +| AM | Acknowledged Mode | +| AMD | Acknowledged Mode Data | +| ARQ | Automatic Repeat Request | +| BCCH | Broadcast Control CHannel | +| BCH | Broadcast CHannel | +| C- | Control- | +| CCCH | Common Control CHannel | + +| | | +|--------|---------------------------------------------| +| CCH | Control CHannel | +| CCTrCH | Coded Composite Transport CHannel | +| CRC | Cyclic Redundancy Check | +| CTCH | Common Traffic CHannel | +| DCCH | Dedicated Control CHannel | +| DCH | Dedicated CHannel | +| DL | DownLink | +| DSCH | Downlink Shared CHannel | +| DTCH | Dedicated Traffic CHannel | +| FACH | Forward link Access CHannel | +| FDD | Frequency Division Duplex | +| L1 | Layer 1 (physical layer) | +| L2 | Layer 2 (data link layer) | +| L3 | Layer 3 (network layer) | +| LI | Length Indicator | +| LSB | Least Significant Bit | +| MAC | Medium Access Control | +| MBMS | Multimedia Broadcast Multicast Service | +| MCCH | MBMS point-to-multipoint Control CHannel | +| MRW | Move Receiving Window | +| MSB | Most Significant Bit | +| MSCH | MBMS point-to-multipoint Scheduling CHannel | +| MTCH | MBMS point-to-multipoint Traffic CHannel | +| PCCH | Paging Control CHannel | +| PCH | Paging CHannel | +| PDU | Protocol Data Unit | +| PHY | PHYsical layer | +| PhyCH | Physical CHannels | +| RACH | Random Access CHannel | +| RLC | Radio Link Control | +| RRC | Radio Resource Control | +| SAP | Service Access Point | +| SDU | Service Data Unit | +| SHCCH | SHared channel Control CHannel | +| SN | Sequence Number | +| SUFI | SUPER Field | +| TCH | Traffic CHannel | +| TDD | Time Division Duplex | +| TFI | Transport Format Indicator | +| TM | Transparent Mode | +| TMD | Transparent Mode Data | +| TTI | Transmission Time Interval | +| U- | User- | +| UE | User Equipment | +| UL | UpLink | +| UM | Unacknowledged Mode | +| UMD | Unacknowledged Mode Data | +| UMTS | Universal Mobile Telecommunications System | +| UTRA | UMTS Terrestrial Radio Access | +| UTRAN | UMTS Terrestrial Radio Access Network | + +# --- 4 General + +## 4.1 Objective + +This subclause describes the architecture of the RLC sublayer. + +## 4.2 Overview of the RLC sublayer architecture + +The model presented in this subclause is intended to support the definition of the RLC sublayer only, and is not meant to specify or constrain the implementation of the protocol. The RLC sublayer consists of RLC entities, of which there are three types: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM) RLC entities. + +### 4.2.1 Model of the RLC sublayer + +Figure 4.1 illustrates different RLC entities in the RLC model. + +An UM and a TM RLC entity can be configured to be a transmitting RLC entity or a receiving RLC entity. The transmitting RLC entity transmits RLC PDUs and the receiving RLC entity receives RLC PDUs. An AM RLC entity consists of a transmitting side, and a receiving side, where the transmitting side of the AM RLC entity transmits RLC PDUs and the receiving side of the AM RLC entity receives RLC PDUs. + +Elementary procedures (see clause 11) are defined between a "Sender" and a "Receiver". In UM and TM, the transmitting RLC entity acts as a Sender and the peer RLC entity acts as a Receiver. An AM RLC entity acts either as a Sender or as a Receiver depending on the elementary procedure. The Sender is the transmitter of AMD PDUs and the Receiver is the receiver of AMD PDUs. A Sender or a Receiver can reside at either the UE or the UTRAN. + +There is one transmitting and one receiving RLC entity for each transparent mode (TM) and unacknowledged mode (UM) service. There is one combined, transmitting and receiving entity for the acknowledged mode (AM) service. + +In the present document, "transmitted" is equivalent to "submitted to the lower layer" unless otherwise explicitly stated. Each RLC UM, and TM entity uses one logical channel to send or receive data PDUs. An AM RLC entity can be configured to use one or two logical channels to send or receive data and control PDUs. If two logical channels are configured, they are of the same type (DCCH or DTCH). In figure 4.1, the dashed lines between the AM-Entities illustrate the possibility to send and receive RLC PDUs on separate logical channels, e.g. control PDUs on one and data PDUs on the other. A more detailed description of the different entities is given in subclauses 4.2.1.1, 4.2.1.2 and 4.2.1.3. + +![Overview model of the RLC sublayer diagram showing MS and UTRAN components with RLC entities (AM, UM, Tr) and their connections to Upper Layers and MAC.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +The diagram illustrates the RLC sublayer architecture across the Radio Interface between the MS (Mobile Station) and the UTRAN (UTRA Network). The RLC sublayer is shown as a shaded gray area containing various entities. The diagram is organized vertically with 'Upper Layers' at the top, 'RLC' in the middle, and 'MAC' at the bottom. + +On the MS side (left): + +- Transmitting side:** Contains 'Transm. Tr-Entity' and 'Transm. UM-Entity'. Arrows point from Upper Layers into these entities, and then down to the MAC layer. +- AM-Entity:** A bidirectional entity spanning both transmitting and receiving sides, connected to both Upper Layers and MAC. +- Receiving side:** Contains 'Receiv. UM-Entity' and 'Receiv. Tr-Entity'. Arrows point from the MAC layer up into these entities, and then up to the Upper Layers. + +On the UTRAN side (right): + +- Transmitting side:** Contains 'Transm. Tr-Entity' and 'Transm. UM-Entity'. Arrows point from Upper Layers into these entities, and then down to the MAC layer. +- AM-Entity:** A bidirectional entity similar to the MS side. +- Receiving side:** Contains 'Receiv. UM-Entity' and 'Receiv. Tr-Entity'. Arrows point from the MAC layer up into these entities, and then up to the Upper Layers. + +The 'Radio Interface' is represented by a thick vertical line in the center. Horizontal lines with arrows connect the transmitting side of the MS to the receiving side of the UTRAN, and vice versa, representing data transmission across the air interface. Solid lines represent data flow, while dashed lines represent control/feedback flow (specifically for the AM-Entity). + +Overview model of the RLC sublayer diagram showing MS and UTRAN components with RLC entities (AM, UM, Tr) and their connections to Upper Layers and MAC. + +**Figure 4.1: Overview model of the RLC sublayer** + +#### 4.2.1.1 Transparent mode (TM) RLC entities + +Figure 4.2 below shows the model of two transparent mode peer RLC entities. The logical channels used to communicate with the lower layer are described in the figure below. + +![Figure 4.2: Model of two transparent mode peer entities. The diagram shows two RLC entities, a Transmitting TM RLC entity on the left and a Receiving TM RLC entity on the right, connected by a Radio Interface (Uu). The Transmitting TM RLC entity receives RLC SDUs from upper layers through the TM-SAP, stores them in a Transmission buffer, and then segments them for transmission. The Receiving TM RLC entity receives TMD PDUs from the lower layer through logical channels (CCCH/DTCH/SHCCH for UE, BCCH/PCCH/DCCH/DTCH for UTRAN), stores them in a Reception buffer, and then reassembles them for delivery to upper layers through the TM-SAP. The logical channels are labeled as CCCH/DTCH/SHCCH - UE and BCCH/PCCH/DCCH/DTCH - UTRAN on the left, and CCCH/DTCH/SHCCH - UTRAN and BCCH/PCCH/DCCH/DTCH - UE on the right.](7f17c430b9598e4d748a8041457810b3_img.jpg) + +Figure 4.2: Model of two transparent mode peer entities. The diagram shows two RLC entities, a Transmitting TM RLC entity on the left and a Receiving TM RLC entity on the right, connected by a Radio Interface (Uu). The Transmitting TM RLC entity receives RLC SDUs from upper layers through the TM-SAP, stores them in a Transmission buffer, and then segments them for transmission. The Receiving TM RLC entity receives TMD PDUs from the lower layer through logical channels (CCCH/DTCH/SHCCH for UE, BCCH/PCCH/DCCH/DTCH for UTRAN), stores them in a Reception buffer, and then reassembles them for delivery to upper layers through the TM-SAP. The logical channels are labeled as CCCH/DTCH/SHCCH - UE and BCCH/PCCH/DCCH/DTCH - UTRAN on the left, and CCCH/DTCH/SHCCH - UTRAN and BCCH/PCCH/DCCH/DTCH - UE on the right. + +**Figure 4.2: Model of two transparent mode peer entities** + +##### 4.2.1.1.1 Transmitting TM RLC entity + +The transmitting TM-RLC entity receives RLC SDUs from upper layers through the TM-SAP. + +All received RLC SDUs must be of a length that is a multiple of one of the valid TMD PDU lengths. + +If segmentation has been configured by upper layers and a RLC SDU is larger than the TMD PDU size used by the lower layer for that TTI, the transmitting TM RLC entity segments RLC SDUs to fit the TMD PDUs size without adding RLC headers. All the TMD PDUs carrying one RLC SDU are sent in the same TTI, and no segment from another RLC SDU are sent in this TTI. + +If segmentation has not been configured by upper layers, then more than one RLC SDU can be sent in one TTI by placing one RLC SDU in one TMD PDU. All TMD PDUs in one TTI must be of equal length. + +When the processing of a RLC SDU is complete, the resulting one or more TMD PDU(s) are/is submitted to the lower layer through either a BCCH, DCCH, PCCH, CCCH, SHCCH or a DTCH logical channel. + +##### 4.2.1.1.2 Receiving TM RLC entity + +The receiving TM-RLC entity receives TMD PDUs through the configured logical channels from the lower layer. If segmentation is configured by upper layers, all TMD PDUs received within one TTI are reassembled to form the RLC SDU. + +If segmentation is not configured by upper layers, each TMD PDU is treated as a RLC SDU. + +The receiving TM RLC entity delivers RLC SDUs to upper layers through the TM-SAP. + +#### 4.2.1.2 Unacknowledged mode (UM) RLC entities + +Figure 4.3 below shows the model of two unacknowledged mode peer RLC entities when duplicate avoidance and reordering is not configured. The different functions shown in Figure 4.3 below apply to different logical channel types as described in subclause 6.1. + +![Diagram of two unacknowledged mode peer RLC entities (Transmitting and Receiving) connected via the Radio Interface (Uu). The Transmitting entity (UE/UTRAN) includes Transmission buffer, Segmentation & Concatenation, Add RLC header, and Ciphering. The Receiving entity (UTRAN/UE) includes Reassembly, Remove RLC header, Reception buffer, and Deciphering. Data flows from UE/UTRAN through the Transmitting entity to the Radio Interface (Uu) and then to the Receiving entity to UTRAN/UE. Logical channel types are listed at the bottom: DCCH/DTCH – UE, CCCH/SHCCH/DCCH/DTCH/CTCH/MCCH/MSCH/MTCH – UTRAN for the transmitting side; and DCCH/DTCH – UTRAN, CCCH/SHCCH/DCCH/DTCH/CTCH/MCCH/MSCH/MTCH – UE for the receiving side.](410562339ce067fdc6fa41940c118658_img.jpg) + +The diagram illustrates the model of two unacknowledged mode (UM) RLC entities connected via the Radio Interface (Uu). On the left, the Transmitting UM RLC entity (UE/UTRAN) receives data from the UM-SAP and processes it through a Transmission buffer, Segmentation & Concatenation, Add RLC header, and Ciphering. On the right, the Receiving UM RLC entity (UTRAN/UE) processes data through Reassembly, Remove RLC header, Reception buffer, and Deciphering before sending it to the UM-SAP. The logical channel types are specified at the bottom: DCCH/DTCH – UE, CCCH/SHCCH/DCCH/DTCH/CTCH/MCCH/MSCH/MTCH – UTRAN for the transmitting side; and DCCH/DTCH – UTRAN, CCCH/SHCCH/DCCH/DTCH/CTCH/MCCH/MSCH/MTCH – UE for the receiving side. + +Diagram of two unacknowledged mode peer RLC entities (Transmitting and Receiving) connected via the Radio Interface (Uu). The Transmitting entity (UE/UTRAN) includes Transmission buffer, Segmentation & Concatenation, Add RLC header, and Ciphering. The Receiving entity (UTRAN/UE) includes Reassembly, Remove RLC header, Reception buffer, and Deciphering. Data flows from UE/UTRAN through the Transmitting entity to the Radio Interface (Uu) and then to the Receiving entity to UTRAN/UE. Logical channel types are listed at the bottom: DCCH/DTCH – UE, CCCH/SHCCH/DCCH/DTCH/CTCH/MCCH/MSCH/MTCH – UTRAN for the transmitting side; and DCCH/DTCH – UTRAN, CCCH/SHCCH/DCCH/DTCH/CTCH/MCCH/MSCH/MTCH – UE for the receiving side. + +**Figure 4.3: Model of two unacknowledged mode peer entities configured for use without duplicate avoidance and reordering** + +Figure 4.3a below shows the model of two unacknowledged mode peer RLC entities configured for duplicate avoidance and reordering. Because duplicate avoidance and reordering is only specified for MTCH/CCCH in this release, ciphering/ deciphering is omitted. + +![Figure 4.3a: Model of two unacknowledged mode peer entities configured for use with duplicate avoidance and reordering. The diagram shows the flow of data between UTRAN and UE across the Radio Interface (Uu). On the UTRAN side, data enters the Transmitting UM RLC entity through the UM-SAP, passing through a Transmission buffer, Segmentation & Concatenation, and Add RLC header. On the UE side, data exits the Receiving UM RLC entity through the UM-SAP, passing through Duplicate avoidance and reordering, Reception buffer, Remove RLC header, and Reassembly. The logical channels MTCH/CCCH are shown at the bottom of each side.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +The diagram illustrates the architecture of two unacknowledged mode (UM) RLC entities connected via the Radio Interface (Uu). On the UTRAN side, the Transmitting UM RLC entity receives RLC SDUs from upper layers through the UM-SAP. These SDUs are processed through a Transmission buffer, Segmentation & Concatenation, and an Add RLC header block. The resulting UMD PDUs are then sent to the lower layer via MTCH/CCCH logical channels. On the UE side, the Receiving UM RLC entity receives UMD PDUs from the lower layer via MTCH/CCCH logical channels. These PDUs are processed through Duplicate avoidance and reordering, a Reception buffer, Remove RLC header, and Reassembly blocks before being sent to upper layers through the UM-SAP. The Radio Interface (Uu) is shown as the central vertical line separating the UTRAN and UE components. + +Figure 4.3a: Model of two unacknowledged mode peer entities configured for use with duplicate avoidance and reordering. The diagram shows the flow of data between UTRAN and UE across the Radio Interface (Uu). On the UTRAN side, data enters the Transmitting UM RLC entity through the UM-SAP, passing through a Transmission buffer, Segmentation & Concatenation, and Add RLC header. On the UE side, data exits the Receiving UM RLC entity through the UM-SAP, passing through Duplicate avoidance and reordering, Reception buffer, Remove RLC header, and Reassembly. The logical channels MTCH/CCCH are shown at the bottom of each side. + +**Figure 4.3a: Model of two unacknowledged mode peer entities configured for use with duplicate avoidance and reordering** + +##### 4.2.1.2.1 Transmitting UM RLC entity + +The transmitting UM-RLC entity receives RLC SDUs from upper layers through the UM-SAP. + +The transmitting UM RLC entity segments the RLC SDU into UMD PDUs of appropriate size, if the RLC SDU is larger than the length of available space in the UMD PDU. The size of the UMD PDUs after segmentation and/or concatenation shall be smaller than or equal to the largest UL UMD PDU size. If MAC-i/s has been configured and the RLC PDU size is set to "flexible size", the size of the UMD PDUs after segmentation and/or concatenation shall be larger than or equal to the Minimum UL RLC PDU size. If data to be transmitted is not enough to create a UMD PDU of the minimum size, it is allowed to create a UMD PDU including all data to be transmitted, even if the resulting size is smaller than the Minimum UL RLC PDU size. The UMD PDU may contain segmented and/or concatenated RLC SDUs. UMD PDU may also contain padding to ensure that it is of a valid length. Length Indicators are used to define boundaries between RLC SDUs within UMD PDUs unless the "Extension bit" already indicates that a UMD PDU contains exactly one complete SDU. Length Indicators are also used to define whether Padding is included in the UMD PDU. + +If ciphering is configured and started, an UMD PDU is ciphered (except for the UMD PDU header) before it is submitted to the lower layer. + +The transmitting UM RLC entity submits UMD PDUs to the lower layer through either a CCCH, SHCCH, DCCH, CTCH, DTCH, MCCH, MSCH or an MTCH logical channel. + +##### 4.2.1.2.2 Receiving UM RLC entity + +The receiving UM-RLC entity receives UMD PDUs through the configured logical channels from the lower layer. When duplicate avoidance and reordering is configured there may be one or more than one input from the lower layer. Inputs can be added or removed without changing the buffer contents, state variables or timers within the receiving UM RLC entity. Where duplicate avoidance and reordering is not configured there is only one input from the lower layer and it is not reconfigured. + +When configured, duplicate avoidance and reordering is the first receive function that is applied to the input UMD PDU streams in the receiving UM RLC entity. It can only be configured in a UE, it is not used in UTRAN. It completes + +duplicate detection and re-ordering of the UMD PDUs that are received from the one or more inputs to produce a single ordered sequence of PDUs that is passed to the next in sequence RLC receiver function. + +The receiving UM RLC entity deciphers (if ciphering is configured and started) the received UMD PDUs (except for the UMD PDU header). It removes RLC headers from received UMD PDUs, and reassembles RLC SDUs (if segmentation and/or concatenation has been performed by the transmitting UM RLC entity). + +If a receiving UM RLC entity is configured for out of sequence SDU delivery, it will reassemble SDUs and transfer them to the upper layers as soon as all PDUs that contain the SDU have been received even if earlier PDUs have not yet been received. It will store PDUs pending the retransmission of missing PDUs by the transmitting UM RLC. PDUs are removed from storage after recovery of all of its associated SDUs, or by a sequence number window function or a storage timer. Out of sequence SDU delivery is configured only in the UE and is only used with MCCH. + +RLC SDUs are delivered by the receiving UM RLC entity to the upper layers through the UM-SAP. If SN\_Delivery is configured, the sequence number of RLC PDU in which RLC SDU is mapped to is also delivered to the upper layers through the UM-SAP. + +#### 4.2.1.3 Acknowledged mode (AM) RLC entity + +Figure 4.4 below shows the model of an acknowledged mode RLC entity. + +The AM RLC entity can be configured to utilise one or two logical channels. The figure 4.4 shows the model of the AM RLC entity when one logical channel (shown as a solid line) and when two logical channels (shown as dashed lines) are used. + +If one logical channel is configured, the transmitting side of the AM RLC entity submits AMD and Control PDUs to the lower layer on that logical channel. If fixed RLC PDU size is configured the RLC PDU size shall be the same for AMD PDUs and control PDUs. If flexible RLC PDU size is configured the AMD PDU size is variable up to a maximum RLC PDU size. + +In case two logical channels are configured in the uplink, AMD PDUs and control PDUs except acknowledgement status report, MRW ACK SUFI and WINDOW SUFI shall be transmitted on the first logical channel, and acknowledgement status reports, MRW ACK SUFI and WINDOW SUFI shall be transmitted on the second logical channel. In case two logical channels are configured in the downlink, AMD and Control PDUs can be transmitted on any of the two logical channels. + +![Figure 4.4: Model of an acknowledged mode entity. This diagram illustrates the internal architecture of an AM-RLC entity, divided into Transmitting and Receiving sides by a central dashed line. On the Transmitting side, data flows from the AM-SAP through Segmentation/Concatenation and Add RLC header, then into a Retransmission buffer & management block. It then passes through a MUX, a Transmission buffer, and a block for setting PDU header fields and piggybacking STATUS PDUs. Ciphering (only for AMD PDU) is applied before the data is sent to the DCCH/DTCH** channels. The Receiving side shows data coming from DCCH/DTCH* channels through Demux/Routing, then Deciphering, and into a Reception buffer & Retransmission management block. The RLC header is removed, and piggybacked information is extracted. The RLC Control Unit, which includes a Piggybacked status Optional block, receives acknowledgements and sends them back to the transmitting side. The entire entity is labeled UE/UTRAN at the top.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +Figure 4.4: Model of an acknowledged mode entity. This diagram illustrates the internal architecture of an AM-RLC entity, divided into Transmitting and Receiving sides by a central dashed line. On the Transmitting side, data flows from the AM-SAP through Segmentation/Concatenation and Add RLC header, then into a Retransmission buffer & management block. It then passes through a MUX, a Transmission buffer, and a block for setting PDU header fields and piggybacking STATUS PDUs. Ciphering (only for AMD PDU) is applied before the data is sent to the DCCH/DTCH\*\* channels. The Receiving side shows data coming from DCCH/DTCH\* channels through Demux/Routing, then Deciphering, and into a Reception buffer & Retransmission management block. The RLC header is removed, and piggybacked information is extracted. The RLC Control Unit, which includes a Piggybacked status Optional block, receives acknowledgements and sends them back to the transmitting side. The entire entity is labeled UE/UTRAN at the top. + +**Figure 4.4: Model of an acknowledged mode entity** + +##### 4.2.1.3.1 Transmitting side + +The transmitting side of the AM-RLC entity receives RLC SDUs from upper layers through the AM-SAP. + +If fixed RLC PDU size is configured, RLC SDUs are segmented and/or concatenated into AMD PDUs of a fixed length. The segmentation is performed if the received RLC SDU is larger than the length of available space in the AMD PDU. The uplink AMD PDU size is a semi-static value that is configured by upper layers and can only be changed through re-establishment of the AM RLC entity by upper layers. + +If flexible RLC PDU size is configured, RLC SDUs are segmented and/or concatenated to create RLC PDUs larger than or equal to the Minimum UL RLC PDU size and smaller than or equal to the largest UL AMD PDU size. If data to be transmitted is not enough to create an AMD PDU of the minimum size, it is allowed to create an AMD PDU including all data to be transmitted, even if the resulting size is smaller than the Minimum UL RLC PDU size. + +**NOTE:** In downlink, if flexible RLC PDU size is configured, RLC SDUs are segmented if the SDU is larger than the maximum RLC PDU size. Concatenation may be performed up to the maximum RLC PDU size. + +The AMD PDU may contain segmented and/or concatenated RLC SDUs. The AMD PDU may also contain Padding to ensure that it is of a valid size. If fixed RLC PDU size is configured, Length Indicators or a special value of the HE field can be used to define boundaries between RLC SDUs within AMD PDUs. Length Indicators are also used to define whether Padding or Piggybacked STATUS PDU is included in the AMD PDU. If flexible RLC PDU size is configured, + +the Length Indicator size is configured by upper layers. The use of the special value of the HE field is configured by higher layers. + +After the segmentation and/or concatenation are performed, the AMD PDUs are placed in the Retransmission buffer and at the MUX. + +AMD PDUs buffered in the Retransmission buffer are deleted or retransmitted based on the status report found within a STATUS PDU or Piggybacked STATUS PDU sent by the peer AM RLC entity. This status report may contain positive or negative acknowledgements of individual AMD PDUs received by the peer AM RLC entity. + +The MUX multiplexes AMD PDUs from the Retransmission buffer that need to be retransmitted, and the newly generated AMD PDUs delivered from the Segmentation/Concatenation function. + +The PDUs are delivered to the function that completes the AMD PDU header and potentially replaces padding with piggybacked status information. A Piggybacked STATUS PDUs can be of variable size in order to match the amount of free space in the AMD PDU. The AMD PDU header is completed based on the input from the RLC Control Unit that indicates the values to set in various fields (e.g. Polling Bit). The function also multiplexes, if required, Control PDUs received from the RLC Control Unit (RESET and RESET ACK PDUs), and from the Reception buffer (Piggybacked STATUS and STATUS PDUs), with AMD PDUs. + +The ciphering (if configured) is then applied to the AMD PDUs. The AMD PDU header is not ciphered. Piggybacked STATUS PDU and Padding in AMD PDU (when present) are ciphered. Control PDUs (i.e. STATUS PDU, RESET PDU, and RESET ACK PDU) are not ciphered. + +The transmitting side of the AM RLC entity submits AMD PDUs to the lower layer through either one or two DCCH or DTCH logical channels. + +##### 4.2.1.3.2 Receiving side + +The receiving side of the AM-RLC entity receives AMD and Control PDUs through the configured logical channels from the lower layer. + +If fixed RLC PDU size is configured, the AMD PDU size is a semi-static value that is configured by upper layers and can only be changed through re-establishment of the AM RLC entity by upper layers. In the case where the AMD PDU size is not configured, it is determined based on the first PDU received. The downlink and uplink AMD PDU sizes need not be the same. + +If flexible RLC PDU size is configured, the AMD PDU size is variable up to the maximum RLC PDU size, and the Length Indicator size is configured by upper layers. + +AMD PDUs are routed to the Deciphering Unit, where AMD PDUs (minus the AMD PDU header) are deciphered (if ciphering is configured and started), and then delivered to the Reception buffer. + +The AMD PDUs are placed in the Reception buffer until a complete RLC SDU has been received. The Receiver acknowledges successful reception or requests retransmission of the missing AMD PDUs by sending one or more STATUS PDUs to the AM RLC peer entity, through its transmitting side. If a Piggybacked STATUS PDU is found in an AMD PDU, it is delivered to the Retransmission buffer & Management Unit at the transmitting side of the AM RLC entity, in order to purge the buffer of positively acknowledged AMD PDUs, and to indicate which AMD PDUs need to be retransmitted. + +Once a complete RLC SDU has been received, the associated AMD PDUs are reassembled by the Reassembly Unit and delivered to upper layers through the AM-SAP. + +RESET and RESET ACK PDUs are delivered to the RLC Control Unit for processing. If a response to the peer AM RLC entity is needed, an appropriate Control PDU is delivered, by the RLC Control Unit to the transmitting side of the AM RLC entity. The received STATUS PDUs are delivered to the Retransmission buffer and Management Unit at the transmitting side of the AM RLC entity, in order to purge the buffer of positively acknowledged AMD PDUs, and to indicate which AMD PDUs need to be retransmitted. + +# --- 5 Functions + +The following functions are supported by RLC sublayer. For an overall description of the following functions see [3]: + +- Segmentation and reassembly. + +- Concatenation. +- Padding. +- Transfer of user data. +- Error correction. +- In-sequence delivery of upper layer PDUs. +- Duplicate detection. +- Flow control. +- Sequence number check. +- Protocol error detection and recovery. +- Ciphering. +- SDU discard. +- Out of sequence SDU delivery. +- Duplicate avoidance and reordering. + +# --- 6 Services provided to upper layers + +This clause describes the different services provided by RLC sublayer to upper layers. It also includes the mapping of RLC functions to different RLC services. For a detailed description of the RLC services see [3]. + +## - **Transparent data transfer Service:** + +The following functions are needed to support transparent data transfer: + +- Segmentation and reassembly. +- Transfer of user data. +- SDU discard. + +## - **Unacknowledged data transfer Service:** + +The following functions are needed to support unacknowledged data transfer: + +- Segmentation and reassembly. +- Concatenation. +- Padding. +- Transfer of user data. +- Ciphering. +- Sequence number check. +- SDU discard. +- Out of sequence SDU delivery. +- Duplicate avoidance and reordering. +- Provisioning of sequence number. + +## - **Acknowledged data transfer Service:** + +The following functions are needed to support acknowledged data transfer: + +- Segmentation and reassembly. +- Concatenation. +- Padding. +- Transfer of user data. +- Error correction. +- In-sequence delivery of upper layer PDUs. +- Duplicate detection. +- Flow Control. +- Protocol error detection and recovery. +- Ciphering. +- SDU discard. +- **Maintenance of QoS as defined by upper layers.** +- **Notification of unrecoverable errors.** + +## 6.1 Mapping of services/functions onto logical channels + +The following tables show the applicability of services and functions to the logical channels in UL/DL and UE/UTRAN. A '+' in a column denotes that the service/function is applicable for the logical channel in question whereas a '-' denotes that the service/function is not applicable. + +**Table 6.1: RLC modes and functions in UE uplink side** + +| Service | Functions | CCCH | SHCC H | DCCH | DTCH | +|-------------------------------|-------------------------------------|------|--------|------|------| +| Transparent Service | Applicability | + | + | - | + | +| | Segmentation | - | - | - | + | +| | Transfer of user data | + | + | - | + | +| | SDU Discard | - | - | - | + | +| Unacknowledged Service | Applicability | - | - | + | + | +| | Segmentation | - | - | + | + | +| | Concatenation | - | - | + | + | +| | Padding | - | - | + | + | +| | Transfer of user data | - | - | + | + | +| | Ciphering | - | - | + | + | +| | SDU Discard | - | - | + | + | +| Acknowledged Service | Applicability | - | - | + | + | +| | Segmentation | - | - | + | + | +| | Concatenation | - | - | + | + | +| | Padding | - | - | + | + | +| | Transfer of user data | - | - | + | + | +| | Flow Control | - | - | + | + | +| | Error Correction | - | - | + | + | +| | Protocol error detection & recovery | - | - | + | + | +| | Ciphering | - | - | + | + | +| | SDU Discard | - | - | + | + | + +**Table 6.2: RLC modes and functions in UE downlink side** + +| Service | Functions | BCC H | PCC H | SHCC H | CCC H | DCC H | DTC H | CTC H | MCC H | MTCH | MSCH | +|-------------------------------|-------------------------------------|-------|-------|--------|-------|-------|-------|-------|-------|------|------| +| Transparent Service | Applicability | + | + | - | - | + | + | - | - | - | - | +| | Reassembly | - | - | - | - | + | + | - | - | - | - | +| | Transfer of user data | + | + | - | - | + | + | - | - | - | - | +| Unacknowledged Service | Applicability | - | - | + | + | + | + | + | + | + | + | +| | Reassembly | - | - | + | + | + | + | + | + | + | + | +| | Deciphering | - | - | - | - | + | + | - | - | - | - | +| | Sequence number check | - | - | + | + | + | + | + | + | + | + | +| | Transfer of user data | - | - | + | + | + | + | + | + | + | + | +| | Duplicate avoidance and reordering | - | - | - | + | - | - | - | - | + | - | +| | Out of sequence SDU delivery | - | - | - | - | - | - | - | + | - | - | +| Acknowledged Service | Applicability | - | - | - | - | + | + | - | - | - | - | +| | Reassembly | - | - | - | - | + | + | - | - | - | - | +| | Error correction | - | - | - | - | + | + | - | - | - | - | +| | Flow Control | - | - | - | - | + | + | - | - | - | - | +| | In sequence delivery | - | - | - | - | + | + | - | - | - | - | +| | Duplicate detection | - | - | - | - | + | + | - | - | - | - | +| | Protocol error detection & recovery | - | - | - | - | + | + | - | - | - | - | +| | Deciphering | - | - | - | - | + | + | - | - | - | - | +| | Transfer of user data | - | - | - | - | + | + | - | - | - | - | +| | SDU Discard | - | - | - | - | + | + | - | - | - | - | + +NOTE: Duplicate avoidance and reordering function is optional in UE. + +**Table 6.3: RLC modes and functions in UTRAN downlink side** + +| Service | Functions | BCCH | PCC H | CCCH | SHCC H | DCC H | DTC H | CTC H | MCC H | MTCH | MSCH | +|-------------------------------|-------------------------------------|------|-------|------|--------|-------|-------|-------|-------|------|------| +| Transparent Service | Applicability | + | + | - | - | + | + | - | - | - | - | +| | Segmentation | - | - | - | - | + | + | - | - | - | - | +| | Transfer of user data | + | + | - | - | + | + | - | - | - | - | +| | SDU Discard | - | - | - | - | + | + | - | - | - | - | +| Unacknowledged Service | Applicability | - | - | + | + | + | + | + | + | + | + | +| | Segmentation | - | - | + | + | + | + | + | + | + | + | +| | Concatenation | - | - | + | + | + | + | + | + | + | + | +| | Padding | - | - | + | + | + | + | + | + | + | + | +| | Ciphering | - | - | - | - | + | + | - | - | - | - | +| | Transfer of user data | - | - | + | + | + | + | + | + | + | + | +| | SDU Discard | - | - | - | - | + | + | - | + | + | + | +| Acknowledged Service | Applicability | - | - | - | - | + | + | - | - | - | - | +| | Segmentation | - | - | - | - | + | + | - | - | - | - | +| | Concatenation | - | - | - | - | + | + | - | - | - | - | +| | Padding | - | - | - | - | + | + | - | - | - | - | +| | Transfer of user data | - | - | - | - | + | + | - | - | - | - | +| | Flow Control | - | - | - | - | + | + | - | - | - | - | +| | Error Correction | - | - | - | - | + | + | - | - | - | - | +| | Protocol error detection & recovery | - | - | - | - | + | + | - | - | - | - | +| | Ciphering | - | - | - | - | + | + | - | - | - | - | +| | SDU Discard | - | - | - | - | + | + | - | - | - | - | + +**Table 6.4: RLC modes and functions in UTRAN uplink side** + +| Service | Functions | CCCH | SHCC H | DCCH | DTCH | +|-------------------------------|-------------------------------------|------|--------|------|------| +| Transparent Service | Applicability | + | + | - | + | +| | Reassembly | - | - | - | + | +| | Transfer of user data | + | + | - | + | +| Unacknowledged Service | Applicability | - | - | + | + | +| | Reassembly | - | - | + | + | +| | Deciphering | - | - | + | + | +| | Sequence number check | - | - | + | + | +| | Transfer of user data | - | - | + | + | +| Acknowledged Service | Applicability | - | - | + | + | +| | Reassembly | - | - | + | + | +| | Error correction | - | - | + | + | +| | Flow Control | - | - | + | + | +| | In sequence delivery | - | - | + | + | +| | Duplicate detection | - | - | + | + | +| | Protocol error detection & recovery | - | - | + | + | +| | Deciphering | - | - | + | + | +| | Transfer of user data | - | - | + | + | +| | SDU Discard | - | - | + | + | + +# 7 Services expected from MAC + +For a detailed description of the service provided by the MAC sublayer to upper layers see [3]. + +- Data transfer. + +# 8 Elements for layer-to-layer communication + +The interaction between the RLC sublayer and other layers are described in terms of primitives where the primitives represent the logical exchange of information and control between the RLC sublayer and other layers. The primitives shall not specify or constrain the implementation. + +## 8.1 Primitives between RLC and upper layers + +The primitives between RLC and upper layers are shown in table 8.1. + +**Table 8.1: Primitives between RLC and upper layers** + +| Generic Name | Parameters | | | | +|----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|-------------|-----------------------------------| +| | Req. | Ind. | Resp. | Conf. | +| RLC-AM-DATA | Data, CNF, DiscardReq, MUI, UE-ID type indicator | Data, DiscardInfo | Not Defined | Status, MUI | +| RLC-UM-DATA | Data, UE-ID type indicator, DiscardReq, MUI | Data, Sequence_Number | Not Defined | MUI | +| RLC-TM-DATA | Data, UE-ID type indicator, DiscardReq, MUI | Data, Error_Indicator | Not Defined | MUI | +| CRLC-CONFIG | E/R, Stop (UM/AM only), Continue (UM/AM only), Ciphering Elements (UM/AM only), TM_parameters (TM only), UM_parameters (UM only), AM_parameters (AM only), SN_Delivery (UM only) | Not Defined | Not Defined | Not Defined | +| CRLC-SUSPEND (UM/AM only) | N | Not Defined | Not Defined | VT(US) (UM only), VT(S) (AM only) | +| CRLC-RESUME (UM/AM only) | No Parameter | Not Defined | Not Defined | Not Defined | +| CRLC-STATUS | Not Defined | EVC | Not Defined | Not Defined | + +Each Primitive is defined as follows: + +### **RLC-AM-DATA-Req/Ind/Conf** + +- RLC-AM-DATA-Req is used by upper layers to request transmission of an RLC SDU in acknowledged mode. +- RLC-AM-DATA-Ind is used by the AM RLC entity to deliver to upper layers an RLC SDU that has been transmitted in acknowledged mode and to indicate to upper layers of the discarded RLC SDU in the peer RLC AM entity. +- RLC-AM-DATA-Conf is used by the AM RLC entity to confirm to upper layers the reception of an RLC SDU by the peer-RLC AM entity or to inform the upper layers of a discarded SDU. + +### **RLC-UM-DATA-Req/Ind/Conf** + +- RLC-UM-DATA-Req is used by upper layers to request transmission of an RLC SDU in unacknowledged mode. +- RLC-UM-DATA-Ind is used by the UM RLC entity to deliver to upper layers an RLC SDU that has been transmitted in unacknowledged mode. If SN\_Delivery is configured, RLC-UM-DATA-Ind is used by the UM RLC entity to deliver to upper layers also Sequence\_Number. +- RLC-UM-DATA-Conf is used by the UM RLC entity to inform the upper layers of a discarded SDU. + +### **RLC-TM-DATA-Req/Ind/Conf** + +- RLC-TM-DATA-Req is used by upper layers to request transmission of an RLC SDU in transparent mode. +- RLC-TM-DATA-Ind is used by the TM RLC entity to deliver to upper layers an RLC SDU that has been transmitted in transparent mode. +- RLC-TM-DATA-Conf is used by the TM RLC entity to inform the upper layers of a discarded SDU. + +### **CRLC-CONFIG-Req** + +This primitive is used by upper layers to establish, re-establish, release, stop, continue or modify the RLC. Ciphering elements are included for UM and AM operation. + +### **CRLC-SUSPEND-Req/Conf** + +- CRLC-SUSPEND-Req is used by upper layers to suspend the UM or AM RLC entity. +- CRLC-SUSPEND-Conf is used by the UM or AM RLC entity to confirm that the entity is suspended. + +### **CRLC-RESUME-Req** + +This primitive is used by upper layers to resume the UM or AM RLC entity after the UM or AM RLC entity has been suspended. + +### **CRLC-STATUS-Ind** + +It is used by an RLC entity to send status information to upper layers. + +## **8.2 Primitive parameters** + +Following parameters are used in the primitives: + +- 1) The parameter Data is the RLC SDU that is mapped onto the Data field in RLC PDUs. When AM or UM RLC entities are used, the length of the Data parameter is a multiple of 8 bits, otherwise (TM RLC entity) the length of Data parameter is a bit-string whose length may not be a multiple of 8 bits. +- 2) The parameter Confirmation Request (CNF) indicates whether the transmitting side of the AM RLC entity needs to confirm the reception of the RLC SDU by the peer-RLC AM entity. If required, once all AMD PDUs that make up the RLC SDU are positively acknowledged by the receiving AM RLC entity, the transmitting AM RLC entity notifies upper layers. +- 3) The parameter Message Unit Identifier (MUI) is an identity of the RLC SDU, which is used to indicate which RLC SDU that is confirmed with the RLC-AM-DATA-Conf. primitive, or discarded with the RLC-AM/UM/TM-DATA-Conf. Primitive. +- 4) The parameter E/R indicates establishment, re-establishment, release or modification of an RLC entity, where re-establishment is applicable to AM and UM RLC entities only. If re-establishment is requested, the state variables and configurable parameters are initialised according to subclause 9.7.7. If release is requested, all protocol parameters, variables and timers are released and the RLC entity enters the NULL state. If modification is requested, the protocol parameters indicated by upper layers (e.g. ciphering parameters) are only modified, while keeping the other protocol parameters, such as the protocol variables, protocol timers and protocol state unchanged. AM RLC entities are always re-established if any of the uplink or downlink AMD PDU size is changed. The modification of other protocol parameters does not require a re-establishment. +- 5) The parameter Event Code (EVC) indicates the reason for the CRLC-STATUS-Ind e.g., unrecoverable errors such as data link layer loss or recoverable status events such as reset. +- 6) The parameter Ciphering Elements are only applicable for UM and AM operations. These parameters are Ciphering Mode, Ciphering Key, Transmitting Activation Time (Sequence Number to activate a new ciphering configuration at the Sender), Receiving Activation Time (Sequence Number to activate a new ciphering configuration at the Receiver) and HFN (Hyper Frame Number). +- 7) The AM\_parameters are only applicable for AM operation. These parameters are AMD PDU size, which can be either a fixed value or set to flexible size, largest UL AMD PDU size (only used when flexible PDU size is configured by upper layers, see subclause 9.2.2.8), Length Indicator Size, In-sequence Delivery Indication (indicating that RLC SDUs are delivered to upper layers in sequence or that they can be delivered out of sequence), Timer values (see subclause 9.5), Use of a special value of the HE field (see subclause 9.2.2.7), Protocol parameter values (see subclause 9.6), Polling triggers (see subclause 9.7.1), Status triggers (see subclause 9.7.2), Periodical Status blocking configuration (see subclause 9.7.2), SDU discard mode (see subclause 9.7.3), Minimum WSN (see subclause 9.2.2.11.3), and Send MRW. The Minimum WSN is always greater than or equal to the number of transport blocks in the smallest transport block set. The Send MRW indicates that the information of each discarded RLC SDU is sent to the Receiver, and the MRW SUFI is sent to the Receiver even if no segments of the RLC SDU to be discarded were submitted to a lower layer. +- 8) The parameter DiscardInfo indicates to upper layer the discarded RLC SDU in the peer-RLC AM entity. It is applicable only when in-sequence delivery is configured and it is to be used when upper layers require the reliable data transfer. + +- 9) The Stop parameter is applicable to AM and UM RLC entities only and indicates to the RLC entity to (see subclause 9.7.6): +- not transmit nor receive any RLC PDUs. +- 10) The Continue parameter is applicable to AM and UM RLC entities only and indicates to the RLC entity to continue transmission and reception of RLC PDUs. +- 11) The UM\_parameters are only applicable for UM operation. It contains Timer\_Discard value (see subclause 9.5), use Alternative E-bit interpretation (see subclause 9.2.2.5), largest UL UMD PDU size (see subclause 9.2.2.8), DL RLC UM LI size (see subclause 9.2.2.8) and SN\_Delivery. For a receiving UM RLC in a UE, an additional parameter indicating use/ no use of out of sequence SDU delivery is included (see subclause 11.2.3.2). If out of sequence SDU delivery is used, the parameters OSD\_Window\_Size (see subclause 9.6) and the timeout value of Timer\_OSD (see subclause 9.5) are included. For a receiving UM RLC in a UE, an additional parameter indicating use/ no use of duplicate avoidance and reordering is included (see subclause 9.7.10). If duplicate avoidance and reordering is used, the parameters DAR\_Window\_Size (see subclause 9.6) and the timeout value of Timer\_DAR (see subclause 9.5) are included. If out-of-sequence support is configured, the parameter Configured\_Rx\_Window\_Size is included. If SN\_Delivery parameter is configured, the receiving RLC entity delivers an RLC SDU with Sequence\_Number to the upper layers. When SN\_Delivery parameter is configured, the DL transmitting RLC entity should neither concatenate nor segment RLC SDUs, the UL transmitting RLC entity shall not concatenate RLC SDUs and may segment RLC SDUs. +- 12) The TM\_parameters are only applicable for TM operation. It contains e.g. segmentation indication (see subclauses 9.2.2.9 and 11.1.2.1), Timer\_Discard value (see subclause 9.5) and delivery of erroneous SDU indication (see subclause 11.1.3). +- 13) The N parameter indicates that an RLC entity will not send a PDU with "Sequence Number">=VT(S)+N for AM and "Sequence Number">=VT(US)+N for UM, where N is a non-negative integer. +- 14) The VT(S) parameter indicates the value of the Send State Variable for the case of the AM. +- 15) The VT(US) parameter indicates the value of the UM Data State Variable, for the case of the UM. +- 16) The Error\_Indicator parameter indicates that the RLC SDU is erroneous (see subclause 11.1.3). +- 17) The parameter UE-ID type indicator indicates the RNTI type (U-RNTI or C-RNTI) to be used for the associated RLC SDU. This parameter is not required at the UE. +- 18) The parameter DiscardReq indicates whether the transmitting RLC entity needs to inform the upper layers of the discarded RLC SDU. If required, the transmitting RLC entity notifies upper layers when the SDU is discarded. +- 19) The parameter Status is only applicable for AM operation. This parameter indicates whether a RLC SDU is successfully transmitted or discarded. +- 20) The parameter Sequence\_Number is the value that is mapped onto the Sequence Number (SN) field in an RLC PDU. It is applicable only for UM operation when SN\_Delivery is configured for the UMD RLC entity. +- 21) The parameter Minimum UL PDU size is applicable for AM and UM operation in the uplink. The Minimum UL PDU size determines the smallest size of the RLC AMD or UMD PDU after segmentation or concatenation (see section 9.2.2.9). If data to be transmitted is not enough to create a PDU of the minimum size, it is allowed to create a PDU including all data to be transmitted, even if the resulting size is smaller than the Minimum UL RLC PDU size. + +# --- 9 Elements for peer-to-peer communication + +## 9.1 Protocol data units + +The structures defined in this subclause are normative. + +### 9.1.1 Data PDUs + +- a) TMD PDU (Transparent Mode Data PDU). + +The TMD PDU is used to convey RLC SDU data without adding any RLC overhead. The TMD PDU is used by RLC when it is in transparent mode. + +#### b) UMD PDU (Unacknowledged Mode Data PDU). + +The UMD PDU is used to convey sequentially numbered PDUs containing RLC SDU data. UMD PDUs are used by RLC when it is configured for unacknowledged data transfer. + +#### c) AMD PDU (Acknowledged Mode Data PDU). + +The AMD PDU is used to convey sequentially numbered PDUs containing RLC SDU data. AMD PDUs are used by RLC when it is configured for acknowledged data transfer. + +### 9.1.2 Control PDUs + +Control PDUs are only used in acknowledged mode. + +#### a) STATUS PDU and Piggybacked STATUS PDU. + +The STATUS PDU and the Piggybacked STATUS PDU are used: + +- by the Receiver to inform the Sender about missing and received AMD PDUs in the Receiver; +- by the Receiver to inform the Sender about the size of the allowed transmission window; +- by the Sender to request the Receiver to move the reception window; and +- by the Receiver to acknowledge the Sender about the reception of the request to move the reception window. + +#### b) RESET PDU. + +The RESET PDU is used to reset all protocol states, protocol variables and protocol timers of the peer RLC entity in order to synchronise the two peer entities. It is sent by the Sender to the Receiver. + +#### c) RESET ACK PDU. + +The RESET ACK PDU is an acknowledgement to the RESET PDU. It is sent by the Receiver to the Sender. + +**Table 9.1: RLC PDU names and descriptions** + +| Data Transfer Mode | PDU name | Description | +|-----------------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------| +| Transparent | TMD | Transparent mode data | +| Unacknowledged | UMD | Sequenced unacknowledged mode data | +| Acknowledged | AMD | Sequenced acknowledged mode data | +| | STATUS | Solicited or Unsolicited Status Report, Change window size command, SDU discard command, or SDU discard acknowledgement | +| | Piggybacked STATUS | Piggybacked Solicited or Unsolicited Status Report, Change window size command, SDU discard command, or SDU discard acknowledgement | +| | RESET | Reset Command | +| | RESET ACK | Reset Acknowledgement | + +## 9.2 Formats and parameters + +The formats of RLC PDUs and their parameters defined in this subclause are normative. + +### 9.2.1 Formats + +This subclause specifies the format of the RLC PDUs. The parameters of each RLC PDU are explained in subclause 9.2.2. + +#### 9.2.1.1 General + +An RLC PDU is a bit string. In the figures in subclause 9.2, bit strings are represented by tables in which the first bit is the leftmost one on the first line of the table, the last bit is the rightmost one on the last line of the table, and more generally the bit string is to be read from left to right and then in the reading order of the lines. + +Depending on the provided service, RLC SDUs are bit strings, with any non-null length, or bit strings with a multiple of 8 bits in length. An RLC SDU is included into an RLC PDU from first bit onward. + +#### 9.2.1.2 TMD PDU + +The TMD PDU is used to transfer user data when RLC is operating in transparent mode. No overhead is added to the SDU by RLC. The data length is not constrained to be a multiple of 8 bits. + +![](9b686adccf125267a013fa25721231a3_img.jpg) + +| | +|------| +| Data | +|------| + +**Figure 9.1: TMD PDU** + +#### 9.2.1.3 UMD PDU + +The UMD PDU is used to transfer user data when RLC is operating in unacknowledged mode. The length of the data part shall be a multiple of 8 bits. The UMD PDU header consists of the first octet, which contains the "Sequence Number". The RLC header consists of the first octet and all the octets that contain "Length Indicators". + +![](e05c1a13b44ab41505609d82b00cf4df_img.jpg) + +| | | | +|------------------|---|----------------| +| Sequence Number | E | Oct1 | +| Length Indicator | E | (Optional) (1) | +| ⋮ | | | +| ⋮ | | | +| Length Indicator | E | (Optional) | +| Data | | | +| PAD | | (Optional) | +| | | Last Octet | + +**Figure 9.2: UMD PDU** + +NOTE (1): The "Length Indicator" may be 15 bits. + +#### 9.2.1.4 AMD PDU + +The AMD PDU is used to transfer user data, piggybacked status information and the Polling bit when RLC is operating in acknowledged mode. The length of the data part shall be a multiple of 8 bits. The AMD PDU header consists of the + +first two octets, which contain the "Sequence Number". The RLC header consists of the first two octets and all the octets that contain "Length Indicators". + +![](e90987faabad6a6665cd8ed1151dc474_img.jpg) + +| | | | | | +|---------------------------------|-----------------|---|----|---------------------| +| D/C | Sequence Number | | | Oct1 | +| Sequence Number | | P | HE | Oct2 | +| Length Indicator | | | E | Oct3 (Optional) (1) | +| . | | | | | +| . | | | | | +| . | | | | | +| Length Indicator | | | E | | +| Data | | | | | +| PAD or a piggybacked STATUS PDU | | | | OctN | + +**Figure 9.3: AMD PDU** + +NOTE (1): The "Length Indicator" may be 15 bits. + +#### 9.2.1.5 STATUS PDU + +The STATUS PDU is used to exchange status information between two RLC AM entities. + +The format of the STATUS PDU is given in figure 9.4 below. The length of each super field (SUF) is dependent on its type and contents. + +![](db5ab5d386827a5d5f5fad0f45612b90_img.jpg) + +| | | | | +|------------------|----------|------------------|-------| +| D/C | PDU type | SUF 1 | Oct 1 | +| SUF 1 | | | Oct2 | +| ... | | | | +| SUF k | | | | +| PAD | | | OctN | + +**Figure 9.4: STATUS PDU** + +A STATUS PDU can include super-fields of different types. The size of a STATUS PDU is variable and upper bounded by the maximum RLC PDU size used by the logical channel on which the control PDUs are sent. If fixed RLC PDU size has been configured by upper layers, padding shall be included to match one of the PDU sizes used by the logical channel on which the control PDUs are sent. The length of the STATUS PDU shall be a multiple of 8 bits. If flexible RLC PDU size has been configured by upper layers padding is only included to make the length of the STATUS PDU a multiple of 8 bits. + +#### 9.2.1.6 Piggybacked STATUS PDU + +The format of the piggybacked STATUS PDU is the same as for the STATUS PDU except that the D/C field is replaced by a reserved bit (R2). This PDU can be piggybacked in an AMD PDU if the data leaves out enough room in the AMD PDU. The PDU Type field is set to "000" and all other values are invalid for this version of the protocol. + +![](759c7d62402f0b4651ddce292be5bdef_img.jpg) + +| | | | | +|-------------------|----------|-------------------|------| +| R2 | PDU Type | SUFI 1 | Oct1 | +| SUFI 1 | | | Oct2 | +| ... | | | | +| SUFI k | | | | +| PAD | | | OctN | + +**Figure 9.5: Piggybacked STATUS PDU** + +#### 9.2.1.7 RESET, RESET ACK PDU + +The RESET PDU includes a one-bit sequence number field (RSN). The value of this bit is carried over in the RESET ACK PDU sent in response in order to allow the peer entity to identify which RESET PDU it was sent in response to. + +![](9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg) + +| | | | | | +|------|----------|-----|----|------| +| D/C | PDU Type | RSN | R1 | Oct1 | +| HFNI | | | | | +| HFNI | | | | | +| HFNI | | PAD | | | +| | | | | OctN | + +**Figure 9.6: RESET, RESET ACK PDU** + +The size of a RESET or RESET ACK PDU is variable and upper bounded by the maximum RLC PDU size used by the logical channel on which the control PDUs are sent. If fixed RLC PDU size has been configured by upper layers, padding shall be included to match one of the PDU sizes used by the logical channel on which the control PDUs are sent. The length of the RESET or RESET ACK PDU shall be a multiple of 8 bits. If flexible RLC PDU size has been configured by upper layers padding is only included to make the length of the RESET or RESET ACK PDU a multiple of 8 bits. + +### 9.2.2 Parameters + +If not otherwise mentioned in the definition of each field, the bits in the parameters shall be interpreted as follows: the left-most bit string is the first and most significant and the right most bit is the last and least significant bit. + +Unless otherwise mentioned, integers are encoded in standard binary encoding for unsigned integers. In all cases, including when a value extends over more than one octet as shown in the tables, the bits appear ordered from MSB to LSB when read in the RLC PDU. + +#### 9.2.2.1 D/C field + +Length: 1bit. + +The D/C field indicates the type of an AM PDU. It can be either data or control PDU. + +| Bit | Description | +|-----|-------------| +| 0 | Control PDU | +| 1 | Data PDU | + +#### 9.2.2.2 PDU Type + +Length: 3 bit. + +The PDU type field indicates the Control PDU type. + +| Bit | PDU Type | +|---------|----------------------------------------------------------------------------------------| +| 000 | STATUS | +| 001 | RESET | +| 010 | RESET ACK | +| 011-111 | Reserved
(PDUs with this coding will be discarded by this version of the protocol). | + +#### 9.2.2.3 Sequence Number (SN) + +This field indicates the "Sequence Number" of the RLC PDU, encoded in binary. + +| PDU type | Length | Notes | +|----------|---------|----------------------------------------| +| AMD PDU | 12 bits | Used for retransmission and reassembly | +| UMD PDU | 7 bits | Used for reassembly | + +#### 9.2.2.4 Polling bit (P) + +Length: 1bit. + +This field is used to request a status report (one or several STATUS PDUs) from the Receiver. + +| Bit | Description | +|-----|-----------------------------| +| 0 | Status report not requested | +| 1 | Request a status report | + +#### 9.2.2.5 Extension bit (E) + +Length: 1bit. + +The interpretation of this bit depends on RLC mode and higher layer configuration: + +- In the UMD PDU, the "Extension bit" in the first octet has either the normal E-bit interpretation or the alternative E-bit interpretation depending on higher layer configuration. The "Extension bit" in all the other octets always has the normal E-bit interpretation. +- In the AMD PDU, the "Extension bit" always has the normal E-bit interpretation. + +**Normal E-bit interpretation:** + +| Bit | Description | +|-----|-----------------------------------------------------------| +| 0 | The next field is data, piggybacked STATUS PDU or padding | +| 1 | The next field is Length Indicator and E bit | + +Alternative E-bit interpretation: + +| Bit | Description | +|-----|-----------------------------------------------------------------------------------| +| 0 | The next field is a complete SDU, which is not segmented, concatenated or padded. | +| 1 | The next field is Length Indicator and E bit | + +#### 9.2.2.6 Reserved 1 (R1) + +Length: 3 bits. + +This field in the RESET PDU and RESET ACK PDU is used to have a multiple of 8 bits in length. It shall always be coded to "000". Other values are reserved and will be considered invalid for this version of the protocol. + +#### 9.2.2.7 Header Extension Type (HE) + +Length: 2 bits. + +This two-bit field indicates if the next octet is data or a "Length Indicator" and E bit. + +| Value | Description | +|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 00 | The succeeding octet contains data | +| 01 | The succeeding octet contains a length indicator and E bit | +| 10 | This value is the special value of HE field and indicates that the succeeding octet contains data and the last octet of the PDU is the last octet of an SDU. | +| 11 | Reserved (PDUs with this coding will be discarded by this version of the protocol). | + +#### 9.2.2.8 Length Indicator (LI) + +Unless the "Extension bit" indicates that a UMD PDU contains a complete SDU which is not segmented, concatenated or padded, or the HE field indicates that an AMD PDU contains the last octet of the RLC SDU, a "Length Indicator" is used to indicate the last octet of each RLC SDU ending within the PDU. If the "Extension bit" indicates that the UMD PDU contains a complete SDU which is not segmented, concatenated or padded, or the HE field indicates that an AMD PDU contains the last octet of the SDU, no LIs are present in this RLC PDU. + +Except for the predefined values reserved for special purposes and listed in the tables below, the "Length Indicator" shall: + +- be set to the number of octets between the end of the RLC header and up to and including the last octet of an RLC SDU segment; +- be included in the PDUs that they refer to. + +The size of the "Length Indicator" may be either 7 bits or 15 bits. The "Length Indicator" size is determined independently for uplink and downlink. The value of a "Length Indicator" shall not exceed the values specified in subclauses 11.2.4.2 and 11.3.4.5 respectively for UMD and AMD PDUs. + +The "Length Indicators" which refer to the same PDU shall: + +- not be reordered in case of retransmission; +- be in the same order as the RLC SDUs that they refer to. + +For AM uplink and for AM downlink when "Fixed RLC PDU size" is configured: + +- if the "AMD PDU size" is $\leq 126$ octets: + - 7-bit "Length Indicators" shall be used. +- else: + - 15-bit "Length Indicators" shall be used. +- the size of the "Length Indicator" is always the same for all AMD PDUs, for one RLC entity. + +For AM downlink and AM uplink when "Flexible RLC PDU size" is configured: + +- if "Length Indicator size" is set to 7 bits: + - 7-bit "Length Indicators" shall be used. +- else: + - 15-bit "Length Indicators" shall be used. + +For UM uplink: + +- if the "largest UL UMD PDU size" is $\leq 125$ octets: + - 7-bit "Length Indicators" shall be used. +- else: + - 15-bit "Length Indicators" shall be used. + +For UM downlink: + +- the "Length Indicator" size provided in "DL RLC UM LI size" shall be used. + +For UM: + +- between modifications of the "largest UMD PDU size", the size of the "Length Indicator" is the same for all UMD PDUs; +- if the RLC SDU begins in the beginning of the RLC PDU; and +- if the RLC PDU is transmitted in uplink; and +- if the "Length Indicators" indicating that a RLC SDU ended exactly in the end or one octet short (only when 15-bit "Length Indicators" is used) of the previous RLC PDU are not present; and +- if the "Extension bit" does not indicate that the UMD PDU contains a complete SDU which is not segmented, concatenated or padded; and +- if the "Length Indicator" indicating that the first data octet in this RLC PDU is the first octet of an RLC SDU and the last octet in this RLC PDU is the last octet of the same RLC SDU is not present; and +- if the "Length Indicator" indicating that the first data octet in this RLC PDU is the first octet of an SDU and the same RLC SDU is one octet short of exactly filling the PDU (only when 15-bit "Length Indicators" is used) is not present: + - if 7-bit "Length Indicator" is used: + - the "Length Indicator" with value "111 1100" shall be used. + - if 15-bit "Length Indicator" is used: + - the "Length Indicator" with value "111 1111 1111 1100" shall be used. +- in downlink: + - if 7-bit "Length Indicator" is used: + +- the Receiver shall be prepared to receive the "Length Indicator" with value "111 1100"; +- the Receiver shall follow the discard rules in subclause 11.2.3 both when the "Length Indicator" with value "111 1100" is present and when it is absent. +- if 15-bit "Length Indicator" is used: + - the Receiver shall be prepared to receive the "Length Indicator" with value "111 1111 1111 1100"; + - the Receiver shall follow the discard rules in subclause 11.2.3 both when the "Length Indicator" with value "111 1111 1111 1100" is present and when it is absent. + +In the case where the end of the last segment of an RLC SDU exactly ends at the end of a PDU and there is no "Length Indicator" that indicates the end of the RLC SDU, and the HE field of the PDU does not indicate that the last octet of the AMD PDU is the last octet of an SDU, and the "Extension bit" of the following PDU does not indicate that the UMD PDU contains a complete SDU which is not segmented, concatenated or padded, and the "Length Indicator" of the following PDU does not indicate that the first data octet in that PDU is the first octet of an SDU and the last octet in that PDU is the last octet of the same SDU, and the "Length Indicator" of the following PDU does not indicate that the first data octet in that RLC PDU is the first octet of an SDU and the same RLC SDU is one octet short of exactly filling the PDU (only when 15-bit "Length Indicators" is used): + +- if 7-bit "Length Indicator" is used: + - a "Length Indicator" with value "000 0000" shall be placed as the first "Length Indicator" in the following PDU; +- if 15-bit "Length Indicator" is used: + - a "Length Indicator" with value "000 0000 0000 0000" shall be placed as the first "Length Indicator" in the following PDU. + +In the case where a PDU contains a 15-bit "Length Indicator" indicating that an RLC SDU ends with one octet left in the PDU, the last octet of this PDU shall: + +- be padded by the Sender and ignored by the Receiver though there is no "Length Indicator" indicating the existence of Padding; and +- not be filled with the first octet of the next RLC SDU data. + +In the case where 15-bit "Length Indicators" are used in a PDU and the last segment of an RLC SDU is one octet short of exactly filling the PDU and there is no "Length Indicator" that indicates the end of the RLC SDU: + +- if a 15-bit "Length Indicator" is used for the following PDU: + - the "Length Indicator" with value "111 1111 1111 1011" shall be placed as the first "Length Indicator" in the following PDU; + - the remaining one octet in the current PDU shall be padded by the Sender and ignored at the Receiver though there is no "Length Indicator" indicating the existence of Padding; +- if a 7-bit "Length Indicator" size is configured for the following PDU: + - if RLC is configured for UM mode: + - if the "Extension bit" of that PDU does not indicate that the UMD PDU contains a complete SDU which is not segmented, concatenated or padded, and the "Length Indicator" of that PDU does not indicate that the first data octet in that PDU is the first octet of an SDU and the last octet in that PDU is the last octet of the same SDU: + - the "Length Indicator" with value "000 0000" shall be placed as the first "Length indicator" in the following PDU; + - the "Sequence Number" shall be incremented by 2 before it is transmitted. + +For UM and AM RLC: + +- if a 7 bit "Length Indicator" is used in a RLC PDU and one or more padding octets are present in the RLC PDU after the end of the last RLC SDU: + - indicate the presence of padding by including a "Length Indicator" with value "1111111" as the last "Length Indicator" in the PDU. +- if a 15 bit "Length Indicator" is used in a RLC PDU and two or more padding octets are present in the RLC PDU after the end of the last RLC SDU: + - indicate the presence of padding by including a "Length Indicator" with value "111 1111 1111 1111" as the last "Length Indicator" in the PDU. + +NOTE: After the "Length Indicator" indicating the presence of padding has been included in the RLC PDU, the length of the padding may be zero. + +In the case where the "alternative E-bit interpretation" is configured for UM RLC and an RLC PDU contains a segment of an SDU but neither the first octet nor the last octet of this SDU: + +- if a 7-bit "Length Indicator" is used: + - the "Length Indicator" with value "111 1110" shall be used. +- if a 15-bit "Length Indicator" is used: + - the "Length Indicator" with value "111 1111 1111 1110" shall be used. + +In the case where the "alternative E-bit interpretation" is configured for UM RLC and the first data octet in this RLC PDU is the first octet of an SDU and the last octet in this RLC PDU is the last octet of the same SDU: + +- if a 7-bit "Length Indicator" is used: + - the "Length Indicator" with value "111 1101" shall be used. +- if a 15-bit "Length Indicator" is used: + - the "Length Indicator" with value "111 1111 1111 1101" shall be used. + +In the case where the "alternative E-bit interpretation" is configured for UM RLC and the first data octet in this RLC PDU is the first octet of an SDU and the same RLC SDU is one octet short of exactly filling the PDU and a 15-bit "Length Indicator" is used: + +- the "Length Indicator" with value "111 1111 1111 1010" shall be used. + +If a "Length Indicator" is still awaiting transmission and there is no RLC SDU available, an RLC PDU consisting of this "Length Indicator", the appropriate padding "Length Indicator" and padding may be transmitted. + +Predefined values of the "Length Indicator" are used to indicate padding. The values that are reserved for special purposes are listed in the tables below depending on the size of the "Length Indicator". Only predefined "Length Indicator" values can refer to the padding space. These values shall only be placed after all other "Length Indicators" for a PDU. + +STATUS PDUs can be piggybacked on the AMD PDU by using part or all of the padding space. A predefined "Length Indicator" shall be used to indicate the presence of a piggybacked STATUS PDU. This "Length Indicator" replaces the padding "Length Indicator". The piggybacked STATUS PDU shall be appended immediately following the PDU data. When only part of the padding space is used, the end of the piggybacked STATUS PDU is indicated by one of the SUFI fields NO\_MORE or ACK. Thus no additional "Length Indicator" is required to show that there is still padding in the AMD PDU. + +If "SDU discard with explicit signalling" is configured: + +- an AMD PDU can contain a maximum number of 15 "Length Indicators" indicating the end of 15 corresponding SDUs; and +- the rest of the AMD PDU space shall be used as padding or as piggybacked STATUS PDU. + +Length: 7 bits + +| Bit | Description | +|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0000000 | The previous RLC PDU was exactly filled with the last segment of an RLC SDU and there is no "Length Indicator" that indicates the end of the RLC SDU in the previous RLC PDU. | +| 1111100 | UMD PDU: The first data octet in this RLC PDU is the first octet of an RLC SDU. AMD PDU: Reserved (PDUs with this coding will be discarded by this version of the protocol). | +| 1111101 | UMD PDU: The first data octet in this RLC PDU is the first octet of an RLC SDU and the last octet in this RLC PDU is the last octet of the same RLC SDU. AMD PDU: Reserved (PDUs with this coding will be discarded by this version of the protocol). | +| 1111110 | AMD PDU: The rest of the RLC PDU includes a piggybacked STATUS PDU. UMD PDU: The RLC PDU contains a segment of an SDU but neither the first octet nor the last octet of this SDU. | +| 1111111 | The rest of the RLC PDU is padding. The padding length can be zero. | + +Length: 15bits + +| Bit | Description | +|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 000000000000000 | The previous RLC PDU was exactly filled with the last segment of an RLC SDU and there is no "Length Indicator" that indicates the end of the RLC SDU in the previous RLC PDU. | +| 111111111111010 | UMD PDU: The first data octet in this RLC PDU is the first octet of an RLC SDU and the second last octet in this RLC PDU is the last octet of the same RLC SDU. The remaining one octet in the RLC PDU is ignored. | +| 111111111111011 | The last segment of an RLC SDU was one octet short of exactly filling the previous RLC PDU and there is no "Length Indicator" that indicates the end of the RLC SDU in the previous RLC PDU. The remaining one octet in the previous RLC PDU is ignored. | +| 111111111111100 | UMD PDU: The first data octet in this RLC PDU is the first octet of an RLC SDU. AMD PDU: Reserved (PDUs with this coding will be discarded by this version of the protocol). | +| 111111111111101 | UMD PDU: The first data octet in this RLC PDU is the first octet of an RLC SDU and the last octet in this RLC PDU is the last octet of the same RLC SDU. AMD PDU: Reserved (PDUs with this coding will be discarded by this version of the protocol). | +| 111111111111110 | AMD PDU: The rest of the RLC PDU includes a piggybacked STATUS PDU. UMD PDU: The RLC PDU contains a segment of an SDU but neither the first octet nor the last octet of this SDU. | +| 111111111111111 | The rest of the RLC PDU is padding. The padding length can be zero. | + +#### 9.2.2.9 Data field + +RLC SDUs or segments of RLC SDUs are mapped to this field in transparent, unacknowledged and acknowledged modes. + +Transparent mode data: + +- the length of RLC SDUs is not constrained to a multiple of 8 bits; +- if "Segmentation" is configured: + - all the RLC PDUs carrying segments of a RLC SDU shall be sent in one TTI; + - only RLC PDUs carrying segments from a single RLC SDU shall be sent in one TTI; +- otherwise (Segmentation is not configured): + - TMD PDU size is fixed within a single TTI and is equal to the RLC SDU size. + +Unacknowledged mode data and Acknowledged mode data: + +- the length of RLC SDUs is constrained to a multiple of 8 bits; +- if "Fixed RLC PDU size" is configured: + - the last segment of an RLC SDU shall be concatenated with the first segment of the next RLC SDU in order to fill the data field completely and avoid unnecessary padding unless otherwise specified in subclause 9.2.2.8 or subclause 11.2.2.2. The "Length Indicator" field is used to point the borders between RLC SDUs (see subclause 9.2.2.8). +- if "Flexible RLC PDU size" is configured: + - in downlink, the last segment of an RLC SDU may be concatenated with the first segment of the next RLC SDU in order to fill the data field up to a maximum RLC PDU size. The "Length Indicator" field is used to point the borders between RLC SDUs (see subclause 9.2.2.8). + - in uplink, the last segment of an RLC SDU shall be concatenated with the first segment of the next RLC SDU in order to fill the data field at least up to the Minimum UL RLC PDU size. It is allowed to concatenate up to the largest UL AMD PDU size for Acknowledged mode data and largest UMD PDU size for Unacknowledged mode data. The "Length Indicator" field is used to point the borders between RLC SDUs (see subclause 9.2.2.8). If data to be transmitted is not enough to create a UMD PDU of the minimum size, it is allowed to create a UMD PDU including all data to be transmitted, even if the resulting size is smaller than the Minimum UL RLC PDU size. + - in uplink, if MAC-i/is has been configured: + - if the UE pre-generates RLC PDUs for transmission in a later TTI and there is only one activated uplink frequency: + - provided that the UE has sufficient amount of data available for transmission, the size of the data field of the RLC PDU shall be chosen so that each RLC PDU to be multiplexed to the MAC-i/is PDU matches the maximum amount of data allowed to be transmitted by the applicable current grant (scheduled or non-scheduled) for the current TTI. + - RLC PDUs may only be pre-generated if the amount of data in outstanding pre-generated RLC PDUs for this logical channel is less than or equal to four times the maximum amount of data allowed to be transmitted by the applicable current grant (scheduled or non-scheduled) for the current TTI. + - else if the UE pre-generates RLC PDUs for transmission in a later TTI and there are two activated uplink frequencies for FDD or more than one scheduled uplink frequencies for 1.28 Mcps TDD: + - provided that the UE has sufficient amount of data available for transmission, the size of the data field of the RLC PDU shall be chosen so that each RLC PDU to be multiplexed to the MAC-i/is PDU matches the minimum of the following: + - For FDD, + - maximum amount of data allowed to be transmitted by the applicable current grant (scheduled or non-scheduled) on the primary uplink frequency for the current TTI. + - maximum amount of data allowed to be transmitted by the applicable current grant (scheduled) on the secondary uplink frequency for the current TTI. + - For 1.28 Mcps TDD, + - maximum amount of data allowed to be transmitted by the applicable current grant (scheduled) on the each scheduled uplink frequency for the current TTI. + - For FDD, RLC PDUs may only be pre-generated if the amount of data in outstanding pre-generated RLC PDUs for this logical channel is less than or equal to eight times the minimum of the following: + - maximum amount of data allowed to be transmitted by the applicable current grant (scheduled or non-scheduled) on the primary uplink frequency for the current TTI. + +- maximum amount of data allowed to be transmitted by the applicable current grant (scheduled) on the secondary uplink frequency for the current TTI. +- For 1.28 Mcps TDD, RLC PDUs may only be pre-generated if the amount of data in outstanding pre-generated RLC PDUs for this logical channel is less than or equal to 4N times the minimum of the following: + - maximum amount of data allowed to be transmitted by the applicable current grant (scheduled) of each uplink frequency for the current TTI. + +NOTE: N is the number of configured uplink frequencies. + +- else: + - the size of the data field of the RLC PDU shall be chosen so that the RLC PDU size matches the data requested for this logical channel by the current E-TFC selection. +- if "Flexible RLC PDU size" is configured, the maximum size of the data field of the RLC PDU is 1503 octets. + +#### 9.2.2.10 Padding (PAD) + +All unused space in a PDU shall be located at the end of the PDU and is referred to as padding. Padding shall have a length such that the PDU as a whole has one of the predefined total lengths. + +Padding may have any value and the Receiver and the Sender shall disregard it. + +#### 9.2.2.11 SUFI + +Which SUFI fields to use is implementation dependent, but when a STATUS PDU includes information about which AMD PDUs have been received and which are detected as missing, information shall not be included about AMD PDUs with "Sequence Number" ≥ VR(H) or "Sequence Number" ≥ VR(MR), i.e. AMD PDUs that have not yet reached the Receiver or are above the receiving window. Information about AMD PDUs with "Sequence Number" < VR(R) shall not be given except when this is necessary in order to use the BITMAP SUFI, see subclause 9.2.2.11.5. + +Length: variable number of bits. + +The SUFI can include three sub-fields: type information (type of super-field, e.g. list, bitmap, acknowledgement, etc), length information (providing the length of a variable length field within the following value field) and a value. + +Figure 9.7 shows the structure of the super-field. The size of the type sub-field is non-zero but the size of the other sub-fields may be zero. + +| | +|--------| +| Type | +| Length | +| Value | + +**Figure 9.7: The Structure of a Super-Field** + +The length of the type field is 4 bits and it may have any of following values. + +| Bit | Description | +|-----------|---------------------------------------------------------------------------------| +| 0000 | No More Data ( NO_MORE ) | +| 0001 | Window Size ( WINDOW ) | +| 0010 | Acknowledgement ( ACK ) | +| 0011 | List ( LIST ) | +| 0100 | Bitmap ( BITMAP ) | +| 0101 | Relative list ( Rlist ) | +| 0110 | Move Receiving Window ( MRW ) | +| 0111 | Move Receiving Window Acknowledgement ( MRW_ACK ) | +| 1000 | Poll ( POLL ) | +| 1001-1111 | Reserved (PDUs with this encoding are invalid for this version of the protocol) | + +The size and presence of the sub-fields "Length" and "Value" depend on the super-field type and is specified for each super field separately. + +##### 9.2.2.11.1 The No More Data super-field + +The 'No More Data' super-field indicates the end of the data part of a STATUS PDU and is shown in Figure 9.8 below. It shall always be placed as the last SUFI if it is included in a STATUS PDU. All data after this SUFI shall be regarded as padding and shall be neglected. + +| | +|--------------| +| Type=NO_MORE | +|--------------| + +**Figure 9.8: NO\_MORE field in a STATUS PDU** + +##### 9.2.2.11.2 The Acknowledgement super-field + +The 'Acknowledgement' super-field consists of a type identifier field (ACK) and a sequence number (LSN) as shown in figure 9.9 below. The acknowledgement super-field is also indicating the end of the data part of a STATUS PDU. Thus, no 'NO\_MORE' super-field is needed in the STATUS PDU when the 'ACK' super-field is present. The ACK SUFI shall always be placed as the last SUFI if it is included in a STATUS PDU. All data after this SUFI shall be regarded as padding and shall be neglected. + +| | +|------------| +| Type = ACK | +| LSN | + +**Figure 9.9: The ACK fields in a STATUS PDU** + +###### LSN + +Length: 12 bits + +Acknowledges the reception of all AMD PDUs with "Sequence Number" < LSN (Last Sequence Number) that are *not* indicated to be erroneous in earlier parts of the STATUS PDU. This means that if the LSN is set to a value greater than VR(R), all erroneous AMD PDUs shall be included in the same STATUS PDU and if the LSN is set to VR(R), the erroneous AMD PDUs can be split into several STATUS PDUs. At the transmitter, if the value of the LSN =< the value of the first error indicated in the STATUS PDU, VT(A) will be updated according to the LSN, otherwise VT(A) will be updated according to the first error indicated in the STATUS PDU. VT(A) is only updated based on STATUS PDUs where ACK SUFI (or MRW\_ACK SUFI) is included. The LSN shall not be set to a value > VR(H) nor < VR(R). + +##### 9.2.2.11.3 The Window Size super-field + +The Window Size super-field consists of a type identifier (WINDOW) and a window size number (WSN) as shown in Figure 9.10 below. The Receiver is always allowed to change the transmission window size of the peer entity during a connection, but the minimum and the maximum allowed value is given by upper layers configuration. The reception window size of the Receiver is not changed. + +| | +|---------------| +| Type = WINDOW | +| WSN | + +**Figure 9.10: The WINDOW fields in a STATUS PDU** + +###### WSN + +Length: 12 bits + +The value of VT(WS) to be used by the transmitter. The range of the WSN is [0, 212-1]. The minimum value of VT(WS) is 1. If WSN is zero the SUFI shall be discarded by this version of the protocol. The variable VT(WS) is set equal to WSN upon reception of this SUFI. If WSN is greater than Configured\_Tx\_Window\_Size, VT(WS) shall be set equal to Configured\_Tx\_Window\_Size. + +##### 9.2.2.11.4 The List super-field + +The List Super-Field consists of a type identifier field (LIST), a list length field (LENGTH) and a list of LENGTH number of pairs as shown in figure 9.11 below: + +| | +|----------------------| +| Type = LIST | +| LENGTH | +| SN 1 | +| L 1 | +| SN 2 | +| L 2 | +| ... | +| SN LENGTH | +| L LENGTH | + +Figure 9.11: The List fields in a STATUS PDU + +###### LENGTH + +Length: 4 bits + +The number of (SNi, Li)-pairs in the super-field of type LIST. The value "0000" is invalid and the STATUS PDU is discarded. + +###### SNi + +Length: 12 bits + +"Sequence Number" of AMD PDU, which was not correctly received. + +###### Li + +Length: 4 bits + +Number of consecutive AMD PDUs not correctly received following AMD PDU with "Sequence Number" SNi. + +##### 9.2.2.11.5 The Bitmap super-field + +The Bitmap Super-Field consists of a type identifier field (BITMAP), a bitmap length field (LENGTH), a first sequence number (FSN) and a bitmap as shown in figure 9.12 below: + +| | +|----------------------| +| Type = BITMAP | +| LENGTH | +| FSN | +| Bitmap | + +Figure 9.12: The Bitmap fields in a STATUS PDU + +###### LENGTH + +Length: 4 bits + +The size of the bitmap in octets equals LENGTH+1, i.e. LENGTH="0000" means that the size of the bitmap is one octet and LENGTH="1111" gives the maximum bitmap size of 16 octets. + +###### FSN + +Length: 12 bits + +The "Sequence Number" for the first bit in the bitmap. FSN shall not be set to a value lower than VR(R)-7 when the reception window size is less than half the maximum RLC AM "Sequence Number". If the reception window size is larger, FSN shall not be set to a value lower than VR(R). + +###### Bitmap + +Length: Variable number of octets given by the LENGTH field. + +Status of the "Sequence Number" fields in the interval $[FSN, FSN + (LENGTH+1)*8 - 1]$ indicated in the bitmap where each position (from left to right) can have two different values (0 and 1) with the following meaning ( $bit\_position \in [0, (LENGTH+1)*8 - 1]$ ): + +1: Sequence Number = (FSN + bit\_position) has been correctly received. + +0: Sequence Number = (FSN + bit\_position) has not been correctly received. + +The UE may remove AMD PDUs from the transmitter that have been indicated to be correctly received by a BITMAP SUFI. + +NOTE: The transmission window is not advanced based on BITMAP SUFIs, see subclause 9.4. + +##### 9.2.2.11.6 The Relative List super-field + +The Relative List super-field consists of a type identifier field (RLIST), a list length field (LENGTH), the first sequence number (FSN) and a list of LENGTH number of codewords (CW) as shown in figure 9.13 below. + +| | +|----------------------| +| Type = RLIST | +| LENGTH | +| FSN | +| CW 1 | +| CW 2 | +| ... | +| CW LENGTH | + +Figure 9.13: The RList fields in a STATUS PDU + +###### LENGTH + +Length: 4 bits + +The number of codewords (CW) in the super-field of type RLIST. + +###### FSN + +Length: 12 bits + +The "Sequence Number" for the first erroneous AMD PDU in the RLIST, i.e. LENGTH="0000" means that only FSN is present in the SUFI. + +###### CW + +Length: 4 bits + +The CW consists of 4 bits where the three first bits are part of a number and the last bit is a status indicator and it shall be interpreted as follows: + +| Code Word | Description | +|--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| X1X2X3 0 | Next 3 bits of the number are X 1 X 2 X 3 and the number continues in the next CW. The most significant bit within this CW is X 1 . | +| X1X2X3 1 | Next 3 bits of the number are X 1 X 2 X 3 and the number is terminated. The most significant bit within this CW is X 1 . This is the most significant CW within the number. | + +By default, the number given by the CWs represents a distance between the previous indicated erroneous AMD PDU up to and including the next erroneous AMD PDU. + +One special value of CW is defined: + +**000 1** 'Error burst indicator'. + +The error burst indicator means that the next CWs will represent the number of subsequent erroneous AMD PDUs (not counting the already indicated error position). After the number of errors in a burst is terminated with XXX 1, the next codeword will again by default be the least significant bits (LSB) of the distance to the next error. + +If the last CW, as indicated by the value of the LENGTH field, does not contain a "1" in its rightmost position, or the last CW, as indicated by the value of the LENGTH field does contain a "1" in its rightmost position, but is a special "error burst indicator" CW, the encoding of the RLIST SUFI is invalid, and the STATUS PDU is discarded. + +##### 9.2.2.11.7 The Move Receiving Window Acknowledgement super-field + +The 'Move Receiving Window Acknowledgement' super-field acknowledges the reception of a MRW SUFI. The format is given in figure 9.14 below. + +| | +|-----------------------| +| Type = MRW_ACK | +| N | +| SN_ACK | + +Figure 9.14: The MRW\_ACK fields in a STATUS PDU + +**N** + +Length: 4 bits + +The N field shall be set equal to the NLENGTH field in the received MRW SUFI if the SN\_ACK field is equal to the SN\_MRLENGTH field. Otherwise N shall be set to 0. + +With the aid of this field in combination with the SN\_ACK field, it can be determined if the MRW\_ACK corresponds to a previously transmitted MRW SUFI. + +**SN\_ACK** + +Length: 12 bits + +The SN\_ACK field indicates the updated value of VR(R) after the reception of the MRW SUFI. With the aid of this field in combination with the N field, it can be determined if the MRW\_ACK corresponds to a previously transmitted MRW SUFI. + +##### 9.2.2.11.8 The Move Receiving Window (MRW) super-field + +The 'Move Receiving Window' super-field is used to request the Receiver to move its reception window and optionally to indicate the set of discarded RLC SDUs, as a result of an RLC SDU discard in the Sender. The format is given in figure 9.15 below. + +| | +|-------------------------------------| +| Type = MRW | +| LENGTH | +| SN_MR W1 | +| SN_MR W2 | +| ... | +| SN_MR WLENGTH | +| N LENGTH | + +Figure 9.15: The MRW fields in a STATUS PDU + +**LENGTH** + +Length: 4 bits + +The number of SN\_MRWi fields in the super-field of type MRW. + +The values "0001" through "1111" indicate 1 through 15 SN\_MRWi respectively. The value "0000" indicates that one SN\_MRWi field is present and that the RLC SDU to be discarded in the Receiver extends above the configured transmission window in the Sender. + +**SN\_MRWi** + +Length: 12 bits + +When "Send MRW" is configured, an $SN\_MRW_{i}$ shall be used to indicate the end of each discarded RLC SDU, i.e. the number of $SN\_MRW_{i}$ fields shall equal the number of RLC SDUs discarded by that MRW SUFI. When "Send MRW" is not configured, an $SN\_MRW_{i}$ field shall be used to indicate the end of the last RLC SDU to be discarded in the Receiver and additional ones may optionally be used to indicate the end of other discarded RLC SDUs. $SN\_MRW_{i}$ is the "Sequence Number" of the AMD PDU that contains the "Length Indicator" or the special value of the HE field of the i:th RLC SDU to be discarded in the Receiver (except for $SN\_MRW_{LENGTH}$ when $N_{LENGTH} = 0$ , see definition of $N_{LENGTH}$ ). The order of the $SN\_MRW_{i}$ shall be in the same sequential order as the RLC SDUs that they refer to. + +Additionally $SN\_MRW_{LENGTH}$ requests the Receiver to discard all not yet successfully received SDUs that have segments or "Length Indicators" indicating the end of the SDUs in the AMD PDUs with "Sequence Number" $< SN\_MRW_{LENGTH}$ , and to move the reception window accordingly. In addition, when $N_{LENGTH} > 0$ , the Receiver has to discard the not yet successfully received SDUs that have segments or "Length Indicators" indicating the end of the SDUs in the AMD PDU with sequence number $SN\_MRW_{LENGTH}$ up to and including the octet indicated by the $N_{LENGTH}$ :th "Length Indicator" field of the PDU with sequence number $SN\_MRW_{LENGTH}$ . + +**$N_{LENGTH}$** + +Length: 4 bits + +$N_{LENGTH}$ is used together with $SN\_MRW_{LENGTH}$ to indicate the end of the last RLC SDU to be discarded in the Receiver. + +$N_{LENGTH}$ indicates which "Length Indicator" in the AMD PDU with "Sequence Number" $SN\_MRW_{LENGTH}$ corresponds to the last RLC SDU to be discarded in the Receiver. $N_{LENGTH} = 0$ indicates that the end of the last RLC SDU was indicated in the AMD PDU with "Sequence Number" $SN\_MRW_{LENGTH} - 1$ and that the first data octet in the AMD PDU with "Sequence Number" $SN\_MRW_{LENGTH}$ is the first data octet to be reassembled next. + +##### 9.2.2.11.9 The Poll (POLL) super-field + +The 'Poll' super-field is used to request a status report (one or several STATUS PDUs) from the receiver. The poll super-field in downlink can only be used if flexible RLC PDU size is configured in the downlink. The poll super-field in uplink can only be used if flexible RLC PDU size is configured in the uplink. The format is given in figure 9.15b below. + +| | +|--------------------| +| Type = POLL | +| Poll_SN | + +**Figure 9.15b: The POLL fields in a STATUS PDU** + +**Poll\_SN** + +Length: 12 bits + +When "Poll" is configured, the $Poll\_SN$ field shall be set to $VT(S)-1$ . + +#### 9.2.2.12 Reserved 2 (R2) + +Length: 1 bit + +This bit in the Piggybacked STATUS PDU is used to make the Piggybacked STATUS PDU a multiple of 8 bits in length and for this purpose it is coded as 0. Otherwise the PDU is treated as invalid and hence shall be discarded by this version of the protocol. + +#### 9.2.2.13 Reset Sequence Number (RSN) + +Length: 1 bit + +This field is used to indicate the sequence number of the transmitted RESET PDU. If this RESET PDU is a retransmission of the original RESET PDU then the retransmitted RESET PDU would have the same RSN value as the original RESET PDU. Otherwise it will have the next RSN value. The initial value of this field is zero. The value of this field shall be reinitialised when the RLC is re-established. It shall not be reinitialised when the RLC is reset. + +#### 9.2.2.14 Hyper Frame Number Indicator (HFNI) + +Length: 20 bit + +This field is used to indicate the hyper frame number (HFN) to the peer entity. With the aid of this field the HFN in UE and UTRAN can be synchronised. + +## 9.3 Protocol states + +The content presented in this subclause is intended to support the definition of the RLC protocol states only, and is not meant to specify or constrain the implementation of the protocol. + +### 9.3.1 State model for transparent mode entities + +Figure 9.16 illustrates the state model for transparent mode RLC entities (both transmitting and receiving). A transparent mode entity can be in one of the following states. + +#### 9.3.1.1 NULL State + +In the NULL state the RLC entity does not exist and therefore it is not possible to transfer any data through it. + +Upon reception of a CRLC-CONFIG-Req from upper layers indicating establishment, the RLC entity: + +- is created; and +- enters the DATA\_TRANSFER\_READY state. + +#### 9.3.1.2 DATA\_TRANSFER\_READY State + +In the DATA\_TRANSFER\_READY state, transparent mode data can be exchanged between the entities according to subclause 11.1. + +Upon reception of a CRLC-CONFIG-Req from upper layer indicating release, the RLC entity: + +- enters the NULL state; and +- is considered as being terminated. + +![State model diagram for transparent mode entities showing two states: 1. NULL and 2. DATA_TRANSFER_READY. Transitions are triggered by CRLC-CONFIG-Req signals.](265d5cb06b401cf460a20fd2c93fd6d5_img.jpg) + +``` +stateDiagram-v2 + [*] --> 1.NULL + 1.NULL --> 2.DATA_TRANSFER_READY : CRLC-CONFIG-Req + 2.DATA_TRANSFER_READY --> 1.NULL : CRLC-CONFIG-Req +``` + +The diagram illustrates the state transitions for transparent mode RLC entities. It consists of two circular states: '1. NULL' on the left and '2. DATA\_TRANSFER\_READY' on the right. A curved arrow points from the NULL state to the DATA\_TRANSFER\_READY state, labeled 'CRLC-CONFIG-Req'. Another curved arrow points from the DATA\_TRANSFER\_READY state back to the NULL state, also labeled 'CRLC-CONFIG-Req'. To the right of the states, there is a legend indicating that a dotted line represents a 'Received signal' and a solid line represents a 'Sent signal'. + +State model diagram for transparent mode entities showing two states: 1. NULL and 2. DATA\_TRANSFER\_READY. Transitions are triggered by CRLC-CONFIG-Req signals. + +**Figure 9.16: The state model for transparent mode entities** + +### 9.3.2 State model for unacknowledged mode entities + +Figure 9.17 illustrates the state model for unacknowledged mode RLC entities (both transmitting and receiving). An unacknowledged mode entity can be in one of the following states. + +#### 9.3.2.1 NULL State + +In the NULL state the RLC entity does not exist and therefore it is not possible to transfer any data through it. + +Upon reception of a CRLC-CONFIG-Req from upper layer indicating establishment the RLC entity: + +- is created; and +- enters the DATA\_TRANSFER\_READY state. + +#### 9.3.2.2 DATA\_TRANSFER\_READY State + +In the DATA\_TRANSFER\_READY state, unacknowledged mode data can be exchanged between the entities according to subclause 11.2. + +Upon reception of a CRLC-CONFIG-Req from upper layer indicating release, the RLC entity: + +- enters the NULL state; and +- is considered as being terminated. + +Upon reception of a CRLC-CONFIG-Req from upper layer indicating modification, the RLC entity: + +- stays in the DATA\_TRANSFER\_READY state; +- modifies only the protocol parameters and timers as indicated by upper layers. + +Upon reception of a CRLC-SUSPEND-Req from upper layers, the RLC entity: + +- enters the LOCAL\_SUSPEND state. + +#### 9.3.2.3 LOCAL\_SUSPEND State + +In the LOCAL\_SUSPEND state, the RLC entity is suspended, i.e. it does not send UMD PDUs with "Sequence Number" greater than or equal to a certain specified value (see subclause 9.7.5). + +Upon reception of a CRLC-CONFIG-Req from upper layer indicating release, the RLC entity: + +- enters the NULL state; and +- is considered as being terminated. + +Upon reception of a CRLC-RESUME-Req from upper layers, the RLC entity: + +- enters the DATA\_TRANSFER\_READY state; and +- resumes the data transmission. + +Upon reception of a CRLC-CONFIG-Req from upper layer indicating modification, the RLC entity: + +- stays in the LOCAL\_SUSPEND state; +- modifies only the protocol parameters and timers as indicated by upper layers. + +![Figure 9.17: The state model for unacknowledged mode entities. The diagram shows three states: 1. NULL, 2. DATA_TRANSFER_READY, and 3. LOCAL_SUSPEND. Transitions are triggered by CRLC-CONFIG-Req, CRLC-RESUME-Req, CRLC-SUSPEND-Req, and CRLC-SUSPEND-Conf. State 2 has a self-loop for data transfer. State 3 has self-loops for 'Received signal' and 'Sent signal'.](32ff77da4286b58c4778033acaa10836_img.jpg) + +``` + +stateDiagram-v2 + [*] --> 1.NULL + 1.NULL --> 2.DATA_TRANSFER_READY : CRLC-CONFIG-Req + 2.DATA_TRANSFER_READY --> 2.DATA_TRANSFER_READY : CRLC-CONFIG-Req + 2.DATA_TRANSFER_READY --> 3.LOCAL_SUSPEND : CRLC-SUSPEND-Req + 3.LOCAL_SUSPEND --> 2.DATA_TRANSFER_READY : CRLC-CONFIG-Req + 3.LOCAL_SUSPEND --> 1.NULL : CRLC-RESUME-Req + 3.LOCAL_SUSPEND --> 1.NULL : CRLC-CONFIG-Req + 3.LOCAL_SUSPEND --> 3.LOCAL_SUSPEND : Received signal + 3.LOCAL_SUSPEND --> 3.LOCAL_SUSPEND : Sent signal + 3.LOCAL_SUSPEND --> 2.DATA_TRANSFER_READY : CRLC-SUSPEND-Conf + +``` + +Figure 9.17: The state model for unacknowledged mode entities. The diagram shows three states: 1. NULL, 2. DATA\_TRANSFER\_READY, and 3. LOCAL\_SUSPEND. Transitions are triggered by CRLC-CONFIG-Req, CRLC-RESUME-Req, CRLC-SUSPEND-Req, and CRLC-SUSPEND-Conf. State 2 has a self-loop for data transfer. State 3 has self-loops for 'Received signal' and 'Sent signal'. + +Figure 9.17: The state model for unacknowledged mode entities + +### 9.3.3 State model for acknowledged mode entities + +Figure 9.18 illustrates the state model for the acknowledged mode RLC entity (both transmitting and receiving). An acknowledged mode entity can be in one of the following states. + +#### 9.3.3.1 NULL State + +In the NULL state the RLC entity does not exist and therefore it is not possible to transfer any data through it. + +Upon reception of a CRLC-CONFIG-Req from upper layer indicating establishment, the RLC entity: + +- is created; and +- enters the DATA\_TRANSFER\_READY state. + +#### 9.3.3.2 DATA\_TRANSFER\_READY State + +In the DATA\_TRANSFER\_READY state, acknowledged mode data can be exchanged between the entities according to subclause 11.3. + +Upon reception of a CRLC-CONFIG-Req from upper layer indicating release, the RLC entity: + +- enters the NULL state; and +- is considered as being terminated. + +Upon detection of an initiating condition for the RLC reset procedure described in subclause 11.4.2, the RLC entity: + +- initiates the RLC reset procedure (see subclause 11.4); and +- enters the RESET\_PENDING state. + +Upon reception of a RESET PDU, the RLC entity responds according to subclause 11.4.3. + +Upon reception of a RESET ACK PDU, the RLC entity takes no action. + +Upon reception of CRLC-SUSPEND-Req from upper layer, the RLC entity is suspended and enters the LOCAL\_SUSPEND state. + +#### 9.3.3.3 RESET\_PENDING State + +In the RESET\_PENDING state the entity waits for a response from its peer entity and no data can be exchanged between the entities. + +Upon reception of a CRLC-CONFIG-Req from upper layer indicating release, the RLC entity: + +- enters the NULL state; and +- is considered as being terminated. + +Upon reception of a RESET ACK PDU with the same RSN value as in the corresponding RESET PDU, the RLC entity: + +- acts according to subclause 11.4.4; and +- enters the DATA\_TRANSFER\_READY state. + +Upon reception of a RESET ACK PDU with a different RSN value as in the corresponding RESET PDU, the RLC entity: + +- discards the RESET ACK PDU (see subclause 11.4.4); and +- stays in the RESET\_PENDING state. + +Upon reception of a RESET PDU, the RLC entity: + +- responds according to subclause 11.4.3; and +- stays in the RESET\_PENDING state. + +Upon reception of CRLC-SUSPEND-Req from upper layer, the RLC entity: + +- enters the RESET\_AND\_SUSPEND state. + +![State model diagram for acknowledged mode entities showing five states: 1. NULL, 2. DATA_TRANSFER_READY, 3. RESET_PENDING, 4. LOCAL_SUSPEND, and 5. RESET_AND_SUSPEND. Transitions are triggered by CRLC-CONFIG-Req, RESET, RESET ACK, CRLC-SUSPEND-Req, CRLC-SUSPEND-Conf, and CRLC-RESUME-Req signals.](d6015fcef74bce83d04acd2e17b4fc15_img.jpg) + +``` + +stateDiagram-v2 + [*] --> NULL + NULL --> DATA_TRANSFER_READY: CRLC-CONFIG-Req + DATA_TRANSFER_READY --> NULL: CRLC-CONFIG-Req + DATA_TRANSFER_READY --> DATA_TRANSFER_READY: RESET + DATA_TRANSFER_READY --> RESET_PENDING: RESET + DATA_TRANSFER_READY --> LOCAL_SUSPEND: CRLC-SUSPEND-Req + LOCAL_SUSPEND --> DATA_TRANSFER_READY: CRLC-RESUME-Req + LOCAL_SUSPEND --> RESET_AND_SUSPEND: RESET + RESET_PENDING --> NULL: CRLC-CONFIG-Req + RESET_PENDING --> DATA_TRANSFER_READY: RESET ACK + RESET_PENDING --> RESET_PENDING: RESET ACK + RESET_PENDING --> LOCAL_SUSPEND: CRLC-SUSPEND-Req + LOCAL_SUSPEND --> RESET_PENDING: CRLC-SUSPEND-Conf + LOCAL_SUSPEND --> RESET_AND_SUSPEND: CRLC-RESUME-Req + RESET_AND_SUSPEND --> NULL: CRLC-CONFIG-Req + RESET_AND_SUSPEND --> DATA_TRANSFER_READY: RESET ACK + RESET_AND_SUSPEND --> RESET_PENDING: CRLC-SUSPEND-Conf + RESET_AND_SUSPEND --> LOCAL_SUSPEND: CRLC-RESUME-Req + +``` + +Legend: + +- Received signal (dashed line) +- Sent signal (solid line) + +State model diagram for acknowledged mode entities showing five states: 1. NULL, 2. DATA\_TRANSFER\_READY, 3. RESET\_PENDING, 4. LOCAL\_SUSPEND, and 5. RESET\_AND\_SUSPEND. Transitions are triggered by CRLC-CONFIG-Req, RESET, RESET ACK, CRLC-SUSPEND-Req, CRLC-SUSPEND-Conf, and CRLC-RESUME-Req signals. + +Figure 9.18: The state model for the acknowledged mode entities + +#### 9.3.3.4 LOCAL\_SUSPEND State + +In the LOCAL\_SUSPEND state, the RLC entity is suspended, i.e. it does not send AMD PDUs with "Sequence Number" greater than or equal to certain specified value (see subclause 9.7.5). + +Upon reception of CRLC-RESUME-Req from upper layers in this state, the RLC entity: + +- resumes the data transmission; and +- enters the DATA\_TRANSFER\_READY state. + +Upon reception of CRLC-CONFIG-Req from upper layers indicating release, the RLC entity: + +- enters the NULL state; and +- is considered as being terminated. + +Upon detection of an initiating condition for RLC reset procedure described in subclause 11.4.2, the RLC entity: + +- initiates the RLC reset procedure (see subclause 11.4); and +- enters the RESET\_AND\_SUSPEND state. + +#### 9.3.3.5 RESET\_AND\_SUSPEND State + +In the RESET\_AND\_SUSPEND state, the entity waits for a response from its peer entity or a primitive (CRLC-RESUME-Req) from its upper layer and no data can be exchanged between the entities. + +Upon reception of CRLC-CONFIG-Req from upper layer indicating release, the RLC entity: + +- enters the NULL state; and +- is considered as being terminated. + +Upon reception of a RESET ACK PDU with the same RSN value as in the corresponding RESET PDU, the RLC entity: + +- acts according to subclause 11.4.4; and +- enters the LOCAL\_SUSPEND state. + +Upon reception of CRLC-RESUME-Req from upper layer in this state, the RLC entity: + +- is resumed, i.e. releases the suspend constraint; and +- enters the RESET\_PENDING state. + +## 9.4 State variables + +The state variables defined in this subclause are normative. + +This sub-clause describes the state variables used in AM and UM in order to specify the peer-to-peer protocol. All state variables are non-negative integers. UMD and AMD PDUs are numbered by modulo integer sequence numbers (SN) cycling through the field: 0 to $2^{12} - 1$ for AM and 0 to $2^7 - 1$ for UM. All arithmetic operations contained in the present document on VT(S), VT(A), VT(MS), VR(R), VR(H) and VR(MR) are affected by the AM modulus. All arithmetic operations contained in the present document on VT(US), VR(US), VR(UDH), VR(UDR), VR(UOH) and VR(UM) are affected by the UM modulus. When performing arithmetic comparisons of state variables or Sequence number values a modulus base shall be used. This modulus base is subtracted (within the appropriate field) from all the values involved and then an absolute comparison is performed. At the Sender, VT(A) and VT(US) shall be assumed to be the modulus base in AM and UM respectively. At the Receiver, VR(R) shall be assumed to be the modulus base in AM and VR(US) shall be assumed to be the modulus base in UM when neither the "out of sequence SDU delivery" nor the "duplicate avoidance and reordering" function are configured. When "out of sequence SDU delivery" is configured, $(VR(UOH) - OSD\_Window\_Size + 1)$ shall be assumed to be the modulus base at the Receiver in UM; when the "duplicate avoidance and reordering" function is configured, $(VR(UDH) - DAR\_Window\_Size + 1)$ shall be assumed to be the modulus base at the Receiver in UM. + +The RLC shall maintain the following state variables in the Sender. + +### a) VT(S) - Send state variable. + +This state variable contains the "Sequence Number" of the next AMD PDU to be transmitted for the first time (i.e. excluding retransmitted PDUs). It shall be updated after the aforementioned AMD PDU is transmitted or after transmission of a MRW SUFI which includes $SN\_MRW\_LENGTH > VT(S)$ (see subclause 11.6). + +The initial value of this variable is 0. + +### b) VT(A) - Acknowledge state variable. + +This state variable contains the "Sequence Number" following the "Sequence Number" of the last in-sequence acknowledged AMD PDU. This forms the lower edge of the transmission window of acceptable acknowledgements. VT(A) shall be updated based on the receipt of a STATUS PDU including an ACK (see subclause 9.2.2.11.2) and/or an MRW\_ACK SUFI (see subclause 11.6). + +The initial value of this variable is 0. For the purpose of initialising the protocol, this value shall be assumed to be the first "Sequence Number" following the last in-sequence acknowledged AMD PDU. + +### c) VT(DAT). + +This state variable counts the number of times a AMD PDU has been scheduled to be transmitted. There shall be one VT(DAT) for each PDU and each shall be incremented every time the corresponding AMD PDU is scheduled to be transmitted or every time a STATUS PDU containing the POLL SUFI is scheduled to be transmitted and the sequence number of the corresponding AMD PDU is equal to VT(S)-1. + +The initial value of this variable is 0. + +### d) VT(MS) - Maximum Send state variable. + +This state variable contains the "Sequence Number" of the first AMD PDU that can be rejected by the peer Receiver, $VT(MS) = VT(A) + VT(WS)$ . This value represents the upper edge of the transmission window. The transmitter shall not transmit AMD PDUs with "Sequence Number" $\geq VT(MS)$ unless $VT(S) \geq VT(MS)$ . In that case, the AMD PDU with "Sequence Number" $= VT(S) - 1$ can also be transmitted. VT(MS) shall be updated when VT(A) or VT(WS) is updated. + +The initial value of this variable is Configured\_Tx\_Window\_size. + +### e) VT(US) – UM data state variable. + +This state variable contains the "Sequence Number" of the next UMD PDU to be transmitted. It shall be incremented by 1 each time a UMD PDU is transmitted. + +The initial value of this variable is 0. + +NOTE: For the UTRAN side, the initial value of this variable can be different from 0. + +### f) VT(PDU). + +This state variable is used when the "poll every Poll\_PDU PDU" polling trigger is configured. It shall be incremented by 1 for each AMD PDU that is transmitted including both new and retransmitted AMD PDUs. When it becomes equal to the value Poll\_PDU, a new poll shall be transmitted and the state variable shall be set to zero. + +The initial value of this variable is 0. + +### g) VT(SDU). + +This state variable is used when the "poll every Poll\_SDU SDU" polling trigger is configured. It shall be incremented by 1 for a given SDU when the AMD PDU carrying the first segment of this SDU is scheduled to be transmitted for the first time. When it becomes equal to the value Poll\_SDU a new poll shall be transmitted and the state variable shall be set to zero. The "Polling bit" shall be set to "1" in the first transmission of the AMD PDU that contains the last segment of an RLC SDU (indicated either by the "Length Indicator" indicating the end of the SDU or by the special value of the HE field). + +The initial value of this variable is 0. + +### h) VT(RST) - Reset state variable. + +This state variable is used to count the number of times a RESET PDU is scheduled to be transmitted before the reset procedure is completed. VT(RST) shall be incremented by 1 according to subclauses 11.4.2 and 11.4.5.1. VT(RST) shall only be reset upon the reception of a RESET ACK PDU ( i.e. VT(RST) shall not be reset when an RLC reset initiated by the peer RLC entity occurs) unless otherwise specified in subclause 9.7.7. + +The initial value of this variable is 0. + +### i) VT(MRW) – MRW command send state variable. + +This state variable is used to count the number of times a MRW command is transmitted. VT(MRW) is incremented by 1 each time a timer Timer\_MRW expires. VT(MRW) shall be reset when the SDU discard with explicit signalling procedure is terminated. + +The initial value of this variable is 0. + +### j) VT(WS) – Transmission window size state variable. + +This state variable contains the size that shall be used for the transmission window. VT(WS) shall be set equal to the WSN field when the transmitter receives a STATUS PDU including a WINDOW SUFI. + +The initial value of this variable is Configured\_Tx\_Window\_size. + +The RLC shall maintain the following state variables in the Receiver: + +### a) VR(R) - Receive state variable. + +This state variable contains the "Sequence Number" following that of the last in-sequence AMD PDU received. It shall be updated upon the receipt of the AMD PDU with "Sequence Number" equal to VR(R). + +The initial value of this variable is 0. For the purpose of initialising the protocol, this value shall be assumed to be the first "Sequence Number" following the last in-sequence received AMD PDU. + +### b) VR(H) - Highest expected state variable. + +This state variable contains the "Sequence Number" following the highest "Sequence Number" of any AMD PDU received or identified to be missing.. When a AMD PDU is received with "Sequence Number" x or a POLL SUFI is received with POLL\_SN=x such that $VR(H) \leq x < VR(MR)$ , this state variable shall be set equal to $x+1$ . + +The initial value of this variable is 0. + +### c) VR(MR) - Maximum acceptable Receive state variable. + +This state variable contains the "Sequence Number" of the first AMD PDU that shall be rejected by the Receiver, $VR(MR) = VR(R) + \text{Configured\_Rx\_Window\_Size}$ . + +### d) VR(US) - Receiver Send Sequence state variable. + +This state variable is applicable only when "out of sequence SDU delivery" is not configured. This state variable contains the "Sequence Number" following that of the last UMD PDU received by the reception buffer (see Fig. 4.3 and 4.3a). When a UMD PDU with "Sequence Number" equal to x is received by the reception buffer, the state variable shall set equal to $x + 1$ . + +The initial value of this variable is 0. + +### e) VR(UOH) –UM out of sequence SDU delivery highest received state variable. + +This state variable contains the "Sequence Number" of the highest numbered UMD PDU that has been received. + +The initial value of this variable is set according to subclause 11.2.3.2. + +### f) VR(UDR) –UM duplicate avoidance and reordering send state variable. + +This state variable contains the "Sequence Number" of the next UMD PDU that is expected to be received in sequence. Its value is set according to subclause 9.7.10. + +The initial value of this variable is set according to subclause 9.7.10. + +- g) VR(UDH) – UM duplicate avoidance and reordering highest received state variable. + +This state variable contains the "Sequence Number" of the highest numbered UMD PDU that has been received by the duplicate avoidance and reordering function. + +The initial value of this variable is set according to 9.7.10. + +- h) VR(UDT) – UM duplicate avoidance and reordering timer state variable. + +This state variable contains the sequence number of the UMD PDU associated with Timer\_DAR when the timer is running. Its value is set according to subclause 9.7.10. + +- i) VR(UM) - Maximum acceptable Receive state variable. + +This state variable contains the "Sequence Number" of the first UMD PDU that shall be rejected by the Receiver, $VR(UM) = VR(US) + Configured\_Rx\_Window\_Size$ . This state variable is only applicable when out-of-sequence reception is configured by higher layers. + +- j) VR(X) – Timer\_Reordering state variable + +This state variable holds the value of SN following the SN of the RLC data PDU which triggered Timer\_Reordering. + +The initial value of this variable is set according to 11.3.3. + +- k) VR(MS) – Maximum STATUS transmit variable + +This state variable holds the highest possible value of the SN which can be indicated by LSN when a STATUS PDU needs to be constructed. + +The initial value of this variable is 0. + +## 9.5 Timers + +The timers defined in this subclause are normative. The timers shall be considered active from the time they are started until the time they either expire or are stopped. + +- a) Timer\_Poll. + +This timer shall only be used when so configured by upper layers. The value of the timer is signalled by upper layers. In the UE this timer shall be started (or restarted) when the successful or unsuccessful transmission of a poll is indicated by lower layer. In UTRAN it should be started when a poll is submitted to lower layer. If $x$ is the value of the state variable VT(S) after the poll was submitted to lower layer, the timer shall be stopped upon receiving: + +- positive acknowledgements for all the AMD PDUs with "Sequence Number" up to and including $x - 1$ ; or +- a negative acknowledgement for the AMD PDU with "Sequence Number" = $x - 1$ . + +If the timer expires and no STATUS PDU fulfilling the criteria above has been received: + +- the Receiver shall be polled once more; +- the timer shall be restarted; and +- the new value of VT(S) shall be saved. + +If a new poll is sent when the timer is active, the timer shall be restarted at the time specified above, and the value of VT(S) shall be saved. + +- b) Timer\_Poll\_Prohibit. + +This timer shall only be used when so configured by upper layers. It is used to prohibit transmission of polls within a certain period. The value of the timer is signalled by upper layers. + +In the UE this timer shall be started (or restarted) when the successful or unsuccessful transmission of a poll is indicated by lower layer. In UTRAN it should be started when a poll is submitted to lower layer. + +From the time a poll is triggered until the timer expires, polling is prohibited. If another poll is triggered while polling is prohibited, its transmission shall be delayed until the timer expires (see subclause 9.7.1). Only one poll shall be transmitted when Timer\_Poll\_Prohibit expires even if several polls were triggered in the meantime. This timer shall not be affected by the reception of STATUS PDUs. + +When Timer\_Poll\_Prohibit is not configured by upper layers, polling is never prohibited. + +- c) Void +- d) Timer\_Discard. + +This timer shall be used when timer-based SDU discard is configured by upper layers. The value of the timer is signalled by upper layers. In the transmitter, a new timer is started upon reception of an SDU from upper layer. + +In UM/TM, if a timer expires before the corresponding SDU is submitted to lower layer, "SDU discard without explicit signalling" specified in subclauses 11.2.4.3 and 11.1.4.2 shall be initiated. In AM, if a timer expires before the corresponding SDU is acknowledged, "SDU discard with explicit signalling" specified in subclause 11.6 shall be initiated. + +- e) Timer\_Poll\_Periodic. + +This timer shall only be used when "timer based polling" is configured by upper layers. The value of the timer is signalled by upper layers. The timer shall be started when the RLC entity is created. When the timer expires, the RLC entity shall: + +- restart the timer; +- if AMD PDUs are available for transmission or retransmission (not yet acknowledged): + - trigger a poll. + +- f) Timer\_Status\_Prohibit. + +This timer shall only be used when so configured by upper layers. It is meant to prohibit the Receiver from sending consecutive acknowledgement status reports. A status report is an acknowledgement status report if it contains any of the SUFI's LIST, BITMAP, RLIST or ACK. The value of the timer is signalled by upper layers. + +In the UE, this timer shall be started (or restarted) when the successful or unsuccessful transmission of the last STATUS PDU of an acknowledgement status report is indicated by lower layer. In UTRAN it should be started when the last STATUS PDU of an acknowledgement status report is submitted to lower layer. + +From the time an acknowledgement status report is triggered until the Timer\_Status\_Prohibit timer expires, acknowledgement is prohibited. If another such status report is triggered while acknowledgement is prohibited, its transmission shall be delayed until the timer expires (see subclause 9.7.2). The status report may be updated during this time. The transmission of SUFI's MRW, MRW\_ACK, WINDOW or NO\_MORE is not restricted. + +When Timer\_Status\_Prohibit is not configured by upper layers, acknowledgement is not prohibited. + +- g) Timer\_Status\_Periodic. + +This timer shall only be used when timer based status reporting is configured by upper layers. + +This timer shall be started when the RLC entity is created. When the timer expires the transmission of a status report shall be triggered and the timer shall be restarted. This timer can be blocked by upper layers. The timer shall be restarted when upper layers indicate that it is no longer blocked. + +### h) Timer\_RST. + +This timer is meant to handle the loss of a RESET PDU by the peer entity, or the loss of a RESET ACK PDU from the peer entity. The value of the timer is signalled by upper layers. + +In the UE this timer shall be started (or restarted) when the successful or unsuccessful transmission of a RESET PDU is indicated by lower layer. In UTRAN it should be started when a RESET PDU is submitted to lower layer. + +Timer\_RST shall only be stopped upon reception of a RESET ACK PDU (with same RSN as RESET PDU), i.e. this timer shall not be stopped when an RLC reset initiated by the peer RLC entity occurs. If this timer expires, the RESET PDU shall be retransmitted. + +### i) Timer\_MRW. + +This timer is used to trigger the retransmission of a status report containing an MRW SUFI field. The value of the timer is signalled by upper layers. + +In the UE this timer shall be started (or restarted) when the successful or unsuccessful transmission of a STATUS PDU containing the MRW SUFI is indicated by lower layer. In UTRAN, it should be started when a STATUS PDU containing the MRW SUFI is submitted to lower layer. + +Each time the timer expires the MRW SUFI is retransmitted. It shall be stopped when one of the termination criteria for the SDU discard with explicit signalling procedure is fulfilled (see subclause 11.6.4). + +### j) Timer\_OSD + +This timer is used with UM out of sequence SDU delivery. It is used to trigger the deleting of stored PDUs. + +The timer is started and stopped according to subclause 11.2.3.2. + +### k) Timer\_DAR + +This timer is used with the UM duplicate avoidance and reordering function. It is used to trigger the transfer of PDUs to the next in sequence UM RLC receiver function. + +The timer is started and stopped according to subclause 9.7.10. + +### l) Timer\_Reordering + +This timer shall only be used when so configured by upper layers. + +The timer is started and stopped according to 11.3.3. There is only one Timer\_Reordering running at a given time. While it is running, any positive or negative acknowledgment is prohibited. The status report may be updated during this time. + +## 9.6 Protocol Parameters + +The behaviour defined in this subclause is normative. The values of the protocol parameters defined in this subclause are signalled by upper layers. + +### a) MaxDAT. + +The maximum number of transmissions of an AMD PDU is equal to MaxDAT – 1. This protocol parameter represents the upper limit for state variable VT(DAT). When VT(DAT) equals the value MaxDAT, either RLC RESET procedure or SDU discard procedure shall be initiated according to the configuration by upper layers. + +### b) Poll\_PDU. + +This protocol parameter indicates how often the transmitter shall poll the Receiver in the case where "polling every Poll\_PDU PDU" is configured by upper layers. It represents the upper limit for the state variable VT(PDU). When VT(PDU) equals the value Poll\_PDU a poll shall be transmitted to the peer entity. + +### c) Poll\_SDU. + +This protocol parameter indicates how often the transmitter shall poll the Receiver in the case where "polling every Poll\_SDU SDU" is configured by upper layers. It represents the upper limit for state variable VT(SDU). When VT(SDU) equals the value Poll\_SDU a poll shall be transmitted to the peer entity. + +### d) Poll\_Window. + +This protocol parameter indicates when the transmitter shall poll the Receiver in the case where "window-based polling" is configured by upper layers. A poll is triggered for each AMD PDU when $J \geq \text{Poll\_Window}$ , where $J$ is the transmission window percentage defined as: + +$$J = \frac{(4096 + \text{VT}(\text{S}) + 1 - \text{VT}(\text{A})) \bmod 4096}{\text{VT}(\text{WS})} * 100 ,$$ + +where the constant 4096 is the modulus for AM described in subclause 9.4 and VT(S) is the value of the variable before the AMD PDU is submitted to lower layer. + +### e) MaxRST. + +The maximum number of transmissions of a RESET PDU is equal to MaxRST - 1. This protocol parameter represents the upper limit for state variable VT(RST). When VT(RST) equals the value MaxRST, unrecoverable error shall be indicated to upper layers. + +### f) Configured\_Tx\_Window\_Size. + +This protocol parameter indicates both the maximum allowed transmission window size and the value for the state variable VT(WS). + +### g) Configured\_Rx\_Window\_Size. + +This protocol parameter indicates the reception window size. This parameter is applicable both for RLC UM and AM. This parameter is only configured for RLC-UM in case out-of-sequence reception is supported. + +### h) MaxMRW. + +The maximum number of transmissions of an MRW command is equal to MaxMRW. This protocol parameter represents the upper limit for state variable VT(MRW). When VT(MRW) equals the value MaxMRW, the RLC RESET procedure shall be initiated. + +### i) OSD\_Window\_Size. + +This protocol parameter indicates the size of the out of sequence SDU delivery storage window. + +### j) DAR\_Window\_Size. + +This protocol parameter indicates the size of the duplicate avoidance and reordering receive window. + +## 9.7 Specific functions + +The functions defined in this subclause are normative. + +### 9.7.1 Polling function for acknowledged mode + +The Polling function is used by the Sender to request the peer RLC entity for a status report. The "Polling bit" in the AMD PDU or the POLL SUFI indicate the poll request. There are several triggers for initiating the Polling function. Which of the triggers shall be used is configured by upper layers for each RLC entity. The following triggers can be configured: + +#### 1) Last PDU in buffer. + +When an AMD PDU to be transmitted for the first time is submitted to lower layer, the Sender shall: + +- if the AMD PDU is the last AMD PDU scheduled for transmission according to subclause 11.3.2 (i.e. no data received from upper layer remains to be segmented into AMD PDUs); or +- if the AMD PDU is the last AMD PDU that is allowed to transmit according to subclause 11.3.2.2: + +- trigger a poll for this AMD PDU. + +#### 2) Last PDU in Retransmission buffer. + +When a retransmitted AMD PDU is submitted to lower layer, the Sender shall: + +- if the AMD PDU is the last AMD PDU scheduled for retransmission according to subclause 11.3.2; or +- if the AMD PDU is the last of the AMD PDUs scheduled for retransmission that are allowed to transmit according to subclause 11.3.2.2: + - trigger a poll for this AMD PDU. + +#### 3) Poll timer. + +The timer Timer\_Poll is started and stopped according to subclause 9.5 a). When the timer Timer\_Poll expires the Sender triggers the Polling function. + +#### 4) Every Poll\_PDU PDU. + +The Sender triggers the Polling function for every Poll\_PDU PDU. Both retransmitted and new AMD PDUs shall be counted. + +#### 5) Every Poll\_SDUs SDU. + +The Sender triggers the Polling function for every Poll\_SDUs SDU. The poll shall be triggered for the first transmission of the AMD PDU that contains the last segment of an RLC SDU (indicated either by the "Length Indicator" indicating the end of the SDU or by the special value of the HE field). + +#### 6) Window based. + +The Sender triggers the Polling function when the condition described in subclause 9.6 d) ("Poll\_Window") is fulfilled. + +#### 7) Timer based. + +The Sender triggers the Polling function periodically. + +UTRAN should configure RLC to avoid deadlock situations. + +The Poll Prohibit function is used by the Sender to delay the initiation of the Polling function. Usage of the Poll Prohibit function is configured by upper layers. The Poll Prohibit function consists of starting the timer Timer\_Poll\_Prohibit according to subclause 9.5 b) and delaying the Polling function according to the following rules: + +When the Polling function is triggered, the Sender shall: + +- if polling is not prohibited (see subclause 9.5 b)); and +- if there is one or more AMD PDUs to be transmitted or there are AMD PDUs not acknowledged by the Receiver: + - initiate the Polling function by setting the polling bit according to subclause 11.3.2.1.1. +- otherwise (if there is no PDU to be transmitted and all PDUs have already been acknowledged): + - not initiate the Polling function. + +Upon expiry of the timer Timer\_Poll\_Prohibit, the Sender shall: + +- if the Polling function was triggered at least once while the timer Timer\_Poll\_Prohibit was active; and +- if there is one or more AMD PDUs to be transmitted or there are AMD PDUs not acknowledged by the Receiver: + - initiate the Polling function once by setting the polling bit according to subclause 11.3.2.1.1. +- otherwise (if there is no PDU to be transmitted and all PDUs have already been acknowledged): + +- not initiate the Polling function. + +NOTE 1: In downlink, UTRAN can initiate the Polling function by assembling a POLL SUFI according to subclause 9.2.2.11.9 when "flexible RLC PDU size" in downlink is configured. + +NOTE 2: In uplink, the UE can initiate the Polling function by assembling a POLL SUFI according to subclause 9.2.2.11.9 when "flexible RLC PDU size" in uplink is configured. + +### 9.7.2 STATUS transmission for acknowledged mode + +The Receiver transmits status reports to the Sender in order to inform the Sender about which AMD PDUs have been received and not received. Each status report consists of one or several STATUS PDUs. The Receiver shall trigger the transmission of a status report when receiving a poll request. Additionally, the following triggers for transmission of status reports are configurable by upper layers: + +- 1) Detection of missing PDU(s). + +If the Receiver detects one or several missing AMD PDUs it shall trigger the transmission of a status report to the Sender. + +- 2) Timer based status report transfer. + +The Receiver triggers the transmission of a status report to the Sender periodically. The timer Timer\_Status\_Periodic controls the time period according to subclause 9.5 g). When "Periodical Status blocking" is configured by upper layers, the trigger shall not be active. + +- 3) Void + +There are several functions that can prohibit the Receiver from sending a status report containing any of the SUFIs LIST, BITMAP, RLIST or ACK. Status reports containing other SUFIs are not prohibited. Upper layers control which functions should be used for each RLC entity. If any of the following functions is used the transmission of the status report shall be delayed, even if any of the triggering conditions above are fulfilled: + +- 1) STATUS prohibit. + +The timer Timer\_Status\_Prohibit is started according to subclause 9.5 f). The Receiver is not allowed to transmit a status report while acknowledgement is prohibited (see subclause 9.5 f)). If a status report was triggered during this time, the status report is transmitted after the timer Timer\_Status\_Prohibit has expired, as described below. + +- 2) Void + +- 3) Timer\_Reordering + +The timer Timer\_Reordering is started according to subclause 11.3.3. The receiver is not allowed to transmit a status report while the timer is running. If a status report was triggered during this time, the status report is transmitted after the timer Timer\_Reordering has expired, as described below. + +When a status report is triggered the Receiver shall: + +- if transmission of status reports is not prohibited by any of the functions "STATUS prohibit" or "Timer\_Reordering": + - assemble and transmit the status report to the Sender, as specified in subclauses 11.5.2.2 and 11.5.2.3. +- otherwise (if the status report is prohibited by at least one of the functions "STATUS prohibit"): + - if MRW, MRW\_ACK, WINDOW or POLL SUFIs are required in the status report: + - send a status report immediately excluding ACK, LIST, BITMAP, and RLIST SUFIs; + - if ACK, LIST, BITMAP, or RLIST SUFIs are required in the status report: + - delay sending these SUFIs until the prohibit function terminates. + +Upon expiry of the timer Timer\_Status\_Prohibit, the Receiver shall: + +- if at least one status report was triggered during the time the transmission of a status reports was prohibited that could not be transmitted due to prohibition; and +- if transmission of a status reports is no longer prohibited by any of the functions "STATUS prohibit" or "Timer\_Reordering": + - transmit one status report to the Sender, using the procedure described in subclause 11.5.2.3. + +Upon expiry of the timer Timer\_Reordering, the Receiver shall: + +- if at least one status report was triggered during the time the transmission of a status reports was prohibited that could not be transmitted due to prohibition; and +- if transmission of a status reports is no longer prohibited by any of the functions "STATUS prohibit" or "Timer\_Reordering": + - update VR(MS) to the SN of the first AMD PDU with SN $\geq$ VR(X) which has not been received; + - transmit one status report to the Sender, using the procedure described in subclause 11.5.2.3. + - if VR(H) $>$ VR(MS): + - start Timer\_Reordering; + - set VR(X) to VR(H). + +### 9.7.3 SDU discard function for acknowledged, unacknowledged, and transparent mode + +The SDU discard function is used by the Sender to discharge RLC PDUs from the RLC PDU buffer, when the transmission of the RLC PDUs does not succeed for a period of time or for a number of transmissions. The SDU discard function allows to avoid buffer overflow. There are several alternative operation modes of the RLC SDU discard function. Upper layers control, which discard function shall be used for each RLC entity. + +The following is a list of operation modes for the RLC SDU discard function, which are described in detail in the subsequent subclauses. + +**Table 9.2: List of criteria that control when to perform SDU discard** + +| Operation mode | Presence | +|--------------------------------------------------|--------------------| +| Timer based discard, with explicit signalling | Network controlled | +| Timer based discard, without explicit signalling | Network controlled | +| SDU discard after MaxDAT number of transmissions | Network controlled | +| No discard after MaxDAT number of transmissions | Network controlled | + +#### 9.7.3.1 Timer based discard, with explicit signalling + +This alternative is only applicable to RLC entities operating in acknowledged mode. It uses a timer based triggering of SDU discard (Timer\_Discard). This makes the SDU discard function insensitive to variations in the channel rate and provides means for exact definition of maximum delay. However, the SDU loss rate of the connection is increased as SDUs are discarded. + +For every SDU received from upper layers, the Sender shall: + +- start a timer Timer\_Discard. + +When the timer Timer\_Discard of a SDU expires, the Sender shall: + +- discard the SDU; +- if "Send MRW" is configured, or one or more segments of the discarded SDU were submitted to the lower layer: + - utilise explicit signalling to inform the Receiver according to subclause 11.6. + +NOTE: The support of the configuration "Send MRW" and the functionality connected with this configuration is implementation dependent. + +#### 9.7.3.2 Timer based discard, without explicit signalling + +This alternative is only applicable to RLC entities operating in unacknowledged or transparent mode. It uses the same timer based trigger for SDU discard (Timer\_Discard) as the one described in the subclause 9.7.3.1. The difference is that this discard method does not use any peer-to-peer signalling. + +For every SDU received from upper layers, the Sender shall: + +- start timer monitoring of the transmission time of the SDU. + +When the transmission time exceeds the configured value for a SDU, the Sender shall: + +- discard the SDU without explicit signalling (for RLC entities operating in unacknowledged mode apply subclause 11.2.4.3 for updating the state variables). + +#### 9.7.3.3 SDU discard after MaxDAT number of transmissions + +This alternative uses the number of transmissions as a trigger for SDU discard, and is therefore only applicable for acknowledged mode RLC. This makes the SDU discard function dependent on the channel rate. Also, this variant of the SDU discard function strives to keep the SDU loss rate constant for the connection, on the cost of a variable delay. + +If the number of times an AMD PDU is scheduled for transmission reaches MaxDAT, the Sender shall: + +- discard all SDUs that have segments or "Length Indicators" indicating the end of the SDUs in the AMD PDU; and +- utilise explicit signalling to inform the Receiver according to clause 11.6. + +#### 9.7.3.4 No\_discard after MaxDAT number of transmissions + +This alternative uses the number of transmissions, and is therefore only applicable for acknowledged mode RLC. + +If the number of times an AMD PDU is scheduled for transmission reaches MaxDAT, the Sender shall: + +- initiate the RLC Reset procedure (see subclause 11.3.4.4). + +#### 9.7.3.5 SDU discard not configured + +If SDU discard has not been configured for an unacknowledged mode RLC entity, SDUs in the transmitter shall not be discarded unless the Transmission buffer is full. + +When the Transmission buffer in an unacknowledged mode RLC entity is full, the Sender may: + +- if segments of the SDU to be discarded have been submitted to lower layer: + - discard the SDU without explicit signalling according to subclause 11.2.4.3. +- otherwise, if no segments of the SDU to be discarded have been submitted to lower layer: + - remove the SDU from the Transmission buffer without utilising any of the discard procedures. + +If SDU discard has not been configured for a transparent mode RLC entity, the Sender shall upon reception of new SDUs from upper layer: + +- discard all SDUs received from upper layer in previous TTIs that are not yet submitted to lower layer; +- submit the new SDUs in the first possible TTI. + +For an acknowledged mode RLC entity, an SDU discard mode is always configured. + +### 9.7.4 Void + +### 9.7.5 Local Suspend function for acknowledged and unacknowledged mode + +The upper layers may suspend an RLC entity. + +When an RLC entity operating in unacknowledged mode is suspended by upper layers with the parameter N, the RLC entity shall: + +- acknowledge the suspend request with a confirmation containing the current value of VT(US); +- not send UMD PDUs with "Sequence Number" $SN \geq VT(US) + N$ . + +When an RLC entity operating in acknowledged mode is suspended by upper layers with the parameter N, the RLC entity shall: + +- acknowledge the suspend request with a confirmation containing the current value of VT(S); +- not send AMD PDUs with "Sequence Number" $SN \geq VT(S) + N$ . + +When an RLC entity operating in unacknowledged mode is resumed by upper layers, the RLC entity shall: + +- resume data transfer procedure. + +When an RLC entity operating in acknowledged mode is resumed by upper layers, the RLC entity shall: + +- if the RLC entity is suspended and a RLC Reset procedure is not ongoing: + - resume data transfer procedure. +- otherwise, if the RLC entity is suspended and a RLC Reset procedure is ongoing: + - remove the suspend constraint; + - resume the RLC reset procedure according to subclause 11.4. + +### 9.7.6 RLC Stop, RLC Continue function for acknowledged and unacknowledged mode + +The upper layer may stop an RLC entity. + +When an RLC entity is stopped, the RLC timers are not affected. + +When a RLC entity is stopped by upper layers, the RLC entity shall: + +- not submit any RLC PDUs to lower layer or receive any RLC PDUs; +- delay triggered Polling functions or status transmissions until the RLC entity is continued. + +NOTE: If the TFC selection exchange has been initiated by sending the RLC Entity Info parameter to MAC, the RLC entity may delay the stop function until the end of the next TTI. + +When a RLC entity is continued by upper layers, the RLC entity shall: + +- if the RLC entity is stopped: + - continue the data transmission and reception; + - process the triggered Polling functions and status transmissions. +- otherwise, if the RLC is not stopped: + - take no action. + +### 9.7.7 RLC re-establishment function for acknowledged and unacknowledged mode + +RLC re-establishment is performed upon request by upper layers. + +The RLC re-establishment function is applicable for AM or UM RLC. For UM, the whole RLC entity is re-established. For AM, upper layers may request re-establishment of the whole RLC entity or only the transmitting or receiving side of the RLC entity. + +When an UM RLC entity is re-established by upper layers, the RLC entity shall: + +- reset the state variables to their initial value; +- set the configurable parameters to their configured value; +- set the hyper frame number (HFN) to the value configured by upper layers; +- if it is a receiving UM RLC entity: + - discard all UMD PDUs. + - stop all timers; +- if it is a transmitting UM RLC entity: + - discard the RLC SDUs for which one or more segments have been submitted to a lower layer; + - if requested: + - inform the upper layers of the discarded SDUs. + - not stop Timer\_Discard if the RLC SDU is not discarded. + +When the transmitting and/or receiving side of an AM RLC entity is re-established by upper layers, the RLC entity shall: + +- if the receiving side of the RLC entity is re-established: + - reset the state variables specified for the receiver in subclause 9.4 to their initial values; + - set the configurable parameters applicable for the receiving side in subclause 9.6 to their configured values; + - set the hyper frame number (HFN) in the receiving side (DL in the UE) to the value configured by upper layers; + - discard the AMD PDUs in the receiving side. +- if only the receiving side of the RLC entity is re-established: + - discard acknowledgement status report, WINDOW SUFI and MRW\_ACK SUFI in all STATUS PDUs and piggybacked STATUS PDUs, RESET PDU and RESET ACK PDU (i.e. discard all control PDUs except MRW SUFI and POLL SUFI); + - if an RLC reset procedure is ongoing (i.e. Timer\_RST is running): + - stop Timer\_RST; + - abort the ongoing RLC reset procedure; + - reset VT(RST); + - restart a new RLC reset procedure after the RLC re-establishment terminates. + - stop Timer\_Status\_Prohibit; + - for the remaining control PDUs and SUFI that were scheduled for transmission before re-establishment but were not delivered to lower layer: + +- assemble the control PDUs and SUFI that were not discarded into new control PDUs with the configured RLC PDU size; +- schedule the new control PDUs for transmission. +- if the transmitting side of the RLC entity is re-established: + - reset the state variables specified for the sender in subclause 9.4 to their initial values; + - set the configurable parameters applicable for the transmitting side in subclause 9.6 to their configured values; + - set the hyper frame number (HFN) in the transmitting side (UL in the UE) to the value configured by upper layers; + - discard SDUs in the transmitting side that have been completely transmitted (the AMD PDUs containing segments of the SDU and the "Length Indicator" indicating the end of the SDU have been transmitted); + - the UE may also discard partially transmitted SDUs (at least one AMD PDU containing a segment of the SDU has been transmitted); + - segment the SDUs that were not discarded into AMD PDUs with the configured RLC PDU size (that may be different from the size before the re-establishment); + - if only the transmitter side of the RLC entity is re-established: + - discard MRW SUFI and POLL SUFI in all STATUS PDUs and piggybacked STATUS PDUs, RESET PDU and RESET ACK PDU (i.e. discard all control PDUs except acknowledgement status report, WINDOW SUFI and MRW\_ACK SUFI); + - for the remaining control PDUs and SUFI that were scheduled for transmission before re-establishment but were not delivered to lower layer: + - assemble the control PDUs and SUFI that were not discarded into new control PDUs with the configured RLC PDU size; + - schedule the control PDUs for transmission. + - if an RLC reset procedure is ongoing (i.e. Timer\_RST is running): + - stop Timer\_RST; + - abort the ongoing RLC reset procedure; + - restart a new RLC reset procedure after the RLC re-establishment terminates. + - stop Timer\_Poll, Timer\_MRW and Timer\_Poll\_Prohibit. + - if both the transmitter and receiver side of the RLC entity is re-established: + - discard the control PDUs in both transmitting and receiving side and the AMD PDUs in the transmitting side; + - if an RLC reset procedure is ongoing (i.e. Timer\_RST is running): + - abort the ongoing RLC reset procedure. + - stop all timers described in subclause 9.5 except Timer\_Poll\_Periodic and Timer\_Status\_Periodic, and Timer\_Discard for SDUs that have not been discarded. + - if requested: + - inform the upper layers of the discarded SDUs. + +NOTE: If the TFC selection exchange has been initiated by sending the RLC Entity Info parameter to MAC, the RLC entity may delay the re-establishment function until the end of the next TTI. + +### 9.7.8 Ciphering for acknowledged and unacknowledged mode + +The ciphering function is performed in RLC, according to the following rules if a radio bearer is using a non-transparent RLC mode (AM or UM). The data unit that is ciphered, depends on the transmission mode as described below. + +- For RLC UM mode, the ciphering unit is the UMD PDU excluding the first octet, i.e. excluding the UMD PDU header. This is shown below in Figure 9.19. + +![Diagram of a UMD PDU structure showing the ciphering unit. The PDU consists of a header (Sequence Number and Length Indicator), followed by Data, and then PAD. The ciphering unit is indicated by a double-headed arrow on the left, encompassing the header, data, and padding. The first octet (Sequence Number) is excluded from the ciphering unit. The Length Indicator is marked as Optional (1). The Data and PAD fields are also marked as Optional.](3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg) + +| | | | +|------------------|---|----------------| +| Sequence Number | E | Oct1 | +| Length Indicator | E | (Optional) (1) | +| ⋮ | | | +| Length Indicator | E | (Optional) | +| Data | | | +| PAD | | (Optional) | +| | | OctN | + +Diagram of a UMD PDU structure showing the ciphering unit. The PDU consists of a header (Sequence Number and Length Indicator), followed by Data, and then PAD. The ciphering unit is indicated by a double-headed arrow on the left, encompassing the header, data, and padding. The first octet (Sequence Number) is excluded from the ciphering unit. The Length Indicator is marked as Optional (1). The Data and PAD fields are also marked as Optional. + +**Figure 9.19: Ciphering unit for a UMD PDU** + +- For RLC AM mode, the ciphering unit is the AMD PDU excluding the first two octets, i.e. excluding the AMD PDU header. This is shown below in Figure 9.20. + +![Diagram of an AMD PDU structure showing the ciphering unit. The PDU header consists of three octets: D/C and Sequence Number (Oct1), Sequence Number, P, and HE (Oct2), and Length Indicator and E (Oct3, Optional). The ciphering unit is indicated by a double-headed arrow on the left, encompassing the header, data, and padding. The first two octets (Oct1 and Oct2) are excluded from the ciphering unit. The Data and PAD or a piggybacked STATUS PDU fields are also marked as Optional.](b5987d63203a5fa601921039922ac520_img.jpg) + +| | | | | +|---------------------------------|-----------------|------|-----------------| +| D/C | Sequence Number | | Oct1 | +| Sequence Number | | P HE | Oct2 | +| Length Indicator | | E | Oct3 (Optional) | +| ⋮ | | | | +| Length Indicator | | E | | +| Data | | | | +| PAD or a piggybacked STATUS PDU | | | OctN | + +Diagram of an AMD PDU structure showing the ciphering unit. The PDU header consists of three octets: D/C and Sequence Number (Oct1), Sequence Number, P, and HE (Oct2), and Length Indicator and E (Oct3, Optional). The ciphering unit is indicated by a double-headed arrow on the left, encompassing the header, data, and padding. The first two octets (Oct1 and Oct2) are excluded from the ciphering unit. The Data and PAD or a piggybacked STATUS PDU fields are also marked as Optional. + +**Figure 9.20: Ciphering unit for an AMD PDU** + +The ciphering algorithm and key to be used are configured by upper layers [8] and the ciphering method shall be applied as specified in [9]. + +The parameters that are required by RLC for ciphering are defined in [9] and are input to the ciphering algorithm. The parameters required by RLC which are provided by upper layers [8] are listed below: + +- RLC AM HFN (Hyper frame number for radio bearers that are mapped onto RLC AM); +- RLC UM HFN (Hyper frame number for radio bearers that are mapped onto RLC UM); +- BEARER (defined as the radio bearer identifier in [9]. It will use the value RB identity –1 as in [8]); +- CK (Ciphering Key). + +### 9.7.9 Reconfiguration of RLC parameters by upper layers + +The RLC parameters for an RLC entity may be reconfigured (modified) by upper layers. + +When an RLC parameter is reconfigured by the upper layer, the UE shall: + +- start using the reconfigured value of the RLC parameter. + +If the parameter Configured\_Rx\_Window\_Size is reconfigured: + +- the UE shall update the state variable VR(UM), (see clause 9.4); +- the UE shall update the state variable VR(MR), (see clause 9.4); +- for AMD PDUs with "Sequence Number" x such that VR(MR) ≤ x < VR(H): + - the UE may discard these AMD PDUs; if discarded, the state variable VR(H) should be updated accordingly; + - consider the discarded AMD PDUs as not having been received. + +If the parameter Configured\_Tx\_Window\_Size is reconfigured: + +- the UE shall set the state variable VT(WS) equal to the Configured\_Tx\_Window\_Size; +- the UE shall update the state variable VT(MS), (see subclause 9.4); +- for AMD PDUs with "Sequence Number" x such that VT(MS) ≤ x < VT(S): + - the UE shall not discard any AMD PDUs that are not positively acknowledged; + - the UE may discard AMD PDUs that are positively acknowledged. + +When the transmission window size or the reception window size is reconfigured the required buffer memory may temporarily exceed the size of the configured window and thus exceed the available buffer memory (see subclause 11.3.4.9). + +If the parameter OSD\_Window\_Size is reconfigured: + +- the UE shall remove from storage any PDUs whose sequence numbers, SN, are outside of the storage window $VR(UOH) \geq SN > VR(UOH) - OSD\_Window\_Size$ . + +If the parameter DAR\_Window\_Size is reconfigured: + +- the UE shall remove from storage any PDUs whose sequence numbers are outside of the storage window and deliver them to the higher RLC function to perform reassembly specified in subclause 11.2.3 and update the state variable VR(UDR) as specified in subclause 9.7.10; +- the UE shall update the state variables VR(UDT) and operate the timer Timer\_DAR if needed (see subclause 9.7.10). + +### 9.7.10 Duplicate avoidance and reordering for unacknowledged mode + +The duplicate avoidance and reordering function can be configured for use within a receiving UM RLC entity in the UE. It combines PDU sequences received from several sources and/or repeat transmissions from a single source to form a single ordered PDU sequence that is passed to the header removal and reassembly functions. It completes duplicate detection, discard and re-ordering based on the UM PDU sequence number. Where the UM RLC receives input from several sources, inputs can be added or removed without changing the buffer contents, state variables and timers associated with the duplicate avoidance and reordering function or any subsequent UM RLC function. + +The duplicate avoidance and reordering function makes use of the state variable VR(UDR) and a receive window whose span is from $VR(UDH) - DAR\_Window\_Size + 1$ to $VR(UDH)$ inclusively. For re-ordering the function uses a buffer for the temporary storage of PDUs. + +For each PDU received, the duplicate avoidance and reordering function shall (in the following SN denotes the sequence number of each PDU): + +Setting initial values of state variables: + +- If the PDU is the first PDU received by the duplicate avoidance and reordering function after establishment or re-establishment: + +- VR(UDH) is assigned the value SN; +- VR(UDR) is assigned the value VR(UDH) – DAR\_Window\_Size + 1. + +Duplicate detection and re-ordering: + +- if SN is within the receive window: + - if SN < VR(UDR) or if a PDU with sequence number SN is already stored in the buffer: + - the PDU shall be discarded; + - else: + - the PDU shall be stored in the buffer. +- if SN is outside of the receive window: + - the PDU shall be stored in the buffer; + - VR(UDH) shall be assigned the value SN, thereby advancing the receive window; + - for any stored PDUs with sequence numbers < VR(UDH) – DAR\_Window\_Size + 1, i.e. outside the receive window after its position is updated, remove the PDU from the buffer and deliver them to the higher RLC function to perform the actions specified in subclause 11.2.3; + - if VR(UDR) < VR(UDH) – DAR\_Window\_Size + 1, i.e. VR(UDR) is outside the updated receive window; + - VR(UDR) shall be assigned the value VR(UDH) – DAR\_Window\_Size + 1. +- if PDU with sequence number VR(UDR) is stored in the buffer: + - for this PDU and any sequence of stored PDUs with consecutive sequence numbers starting at VR(UDR) + 1, remove the PDUs from the buffer and deliver them to the higher RLC function to perform the actions specified in subclause 11.2.3; + - VR(UDR) shall be assigned the value of x + 1 where x is the sequence number of the highest numbered PDU that was delivered to the higher RLC function. + +Timer operation: + +- if Timer\_DAR is not active when a PDU is stored with SN > VR(UDR) by the duplicate avoidance and reordering function: + - Timer\_DAR shall be started; + - VR(UDT) shall be assigned the value of the sequence number of the PDU. +- Timer\_DAR shall be stopped: + - if the PDU with sequence number VR(UDT) is removed from the buffer before Timer\_DAR expires. +- if Timer\_DAR expires: + - for all stored PDUs with sequence numbers lower or equal to VR(UDT) and for any sequence of stored PDUs with consecutive sequence numbers starting at VR(UDT) + 1, remove the PDUs from the buffer and deliver them to the higher RLC function to perform the actions specified in subclause 11.2.3; + - VR(UDR) shall be assigned the value x + 1 where x is the sequence number of the highest numbered PDU that was delivered to the higher RLC function. +- When Timer\_DAR is stopped or expires, and there remain PDUs stored by the duplicate avoidance and reordering function: + - Timer\_DAR shall be started; + - VR(UDT) shall be assigned the sequence number of the highest numbered stored PDU. + +# --- 10 Handling of unknown, unforeseen and erroneous protocol data + +Errors and the handling of errors defined in this clause are normative. + +## 10.1 Erroneous Sequence Number + +A STATUS PDU or Piggybacked STATUS PDU including "erroneous Sequence Number" is a STATUS PDU or Piggybacked STATUS PDU that contains: + +- a LIST, BITMAP or RLIST SUFI in which the "Sequence Number" of at least one AMD PDU that is negatively acknowledged is outside the interval $VT(A) \leq \text{"Sequence Number"} < VT(S)$ ; or +- an ACK SUFI in which "LSN" is outside the interval $VT(A) \leq \text{"LSN"} \leq VT(S)$ . + +If an AM RLC entity receives a STATUS PDU or a Piggybacked STATUS PDU including "erroneous Sequence Number", it shall: + +- discard the STATUS PDU or the Piggybacked STATUS PDU; +- if inter-Node B Multiflow operation is not configured by higher layers, initiate the RLC reset procedure (see subclause 11.4). + +## 10.2 Inconsistent status indication + +If an AM RLC entity receives a STATUS PDU or a Piggybacked STATUS PDU that indicates different status for the same AMD PDU, it shall: + +- discard the STATUS PDU or the Piggybacked STATUS PDU. + +## 10.3 Invalid PDU format + +If an UM or AM RLC entity receives a RLC PDU that contains reserved or invalid values (see subclause 9.2), it shall: + +- discard the RLC PDU. + +## 10.4 RLC PDU with CRC error + +If an UM or AM RLC entity receives a RLC PDU with an error indication, it shall: + +- discard the RLC PDU. + +If a TM RLC entity receives a RLC PDU with an error indication, it shall: + +- if "Delivery of Erroneous SDUs" is configured: + - process the RLC PDU according to subclause 11.1.3; +- otherwise: + - discard the RLC PDU. + +# --- 11 Elementary procedures + +Procedures defined in this clause are normative. + +This description assumes elementary procedures. Interactions between procedures are not described. + +## 11.1 Transparent mode data transfer procedure + +### 11.1.1 General + +The transparent mode data transfer procedure is used for transferring data between two RLC peer entities, which are operating in transparent mode. Data is transferred from Sender to Receiver. This procedure should only apply to entities in DATA\_TRANSFER\_READY state. Figure 11.1 below illustrates the elementary procedure for transparent mode data transfer. + +Channels that can be used are DTCH, CCCH (uplink only), SHCCH (uplink only), BCCH and PCCH. The type of logical channel depends on if the RLC entity is located in the user plane (DTCH) or in the control plane (CCCH/BCCH/SHCCH/PCCH). + +![Diagram illustrating the transparent mode data transfer procedure. A Sender box is on the left and a Receiver box is on the right. A horizontal arrow labeled 'TMD PDU' points from the Sender to the Receiver. Below each box is a grey rectangular block representing the lower layer.](4ca4ef49a4f79d5621932651f7ae3f5e_img.jpg) + +``` + +graph LR + Sender[Sender] -- "TMD PDU" --> Receiver[Receiver] + Sender --- S_Lower[ ] + Receiver --- R_Lower[ ] + style S_Lower fill:#888,stroke:none + style R_Lower fill:#888,stroke:none + +``` + +Diagram illustrating the transparent mode data transfer procedure. A Sender box is on the left and a Receiver box is on the right. A horizontal arrow labeled 'TMD PDU' points from the Sender to the Receiver. Below each box is a grey rectangular block representing the lower layer. + +**Figure 11.1: Transparent mode data transfer procedure** + +### 11.1.2 Transmission of TMD PDU + +Upon a request of transparent mode data transfer from upper layer, the Sender shall: + +- if no SDU discard configuration has been made by upper layers: + - discard SDUs received in previous TTIs upon reception of new SDUs from upper layers (see subclause 9.7.3.5); +- otherwise (if "Timer Based SDU Discard without explicit signalling" is configured): + - start a timer Timer\_Discard for each SDU received from upper layers (see subclause 9.7.3); +- schedule the RLC SDUs that have been received from upper layer for transmission; +- if one or more RLC SDUs have been scheduled for transmission: + - notify the lower layer of reception of data from upper layers; + - perform the actions specified in subclause 11.1.2.2. + +#### 11.1.2.1 TMD PDU contents to set + +The Sender shall set the data field of the TMD PDU to all or a subset of the data contained in the SDU as described in subclause 11.1.2.2. + +#### 11.1.2.2 Submission of TMD PDUs to the lower layer + +If one or more RLC SDUs have been scheduled for transmission, according to subclause 11.1.2, the Sender shall: + +- if it is configured for segmented operation: + - inform the lower layer of the size of the next SDU to be sent; + - segment the SDU according to the PDU size indicated by the lower layer. +- otherwise (the Sender is configured for non-segmented operation): + - inform the lower layer of the number and size of SDUs available for transmission; +- submit to the lower layer, the requested number of TMD PDUs; + +- buffer the SDUs that are not submitted to the lower layer according to the discard configuration (see subclause 9.7.3). + +### 11.1.3 Reception of TMD PDU + +Upon delivery by the lower layer of a set of TMD PDUs (received within one TTI), the Receiver shall: + +- if it is configured for segmented operation: + - reassemble the TMD PDUs received in one TTI into one RLC SDU. +- otherwise (it is configured for non-segmented operation): + - treat each received TMD PDU as a SDU; +- if "Delivery of Erroneous SDUs" is configured as "no": + - submit only the RLC SDUs received without error to upper layers through the TM-SAP. +- else if "Delivery of Erroneous SDUs" is configured as "yes": + - submit all RLC SDUs to upper layers through the TM-SAP; + - provide an error indication for each SDU received in error. +- otherwise if "Delivery of Erroneous SDUs" is configured as "No detect": + - submit all RLC SDUs to upper layers through the TM-SAP. + +If segmentation is performed in transparent mode RLC, an SDU is erroneous if one or more of the TMD PDUs received in a TTI contains an error. If segmentation is not performed, an SDU is erroneous if the corresponding TMD PDU is erroneous. + +### 11.1.4 Abnormal cases + +#### 11.1.4.1 Void + +#### 11.1.4.2 SDU discard without explicit signalling + +Upon expiry of the timer Timer\_Discard in the Sender, the Sender shall: + +- discard the associated SDU; +- if requested: + - inform the upper layers of the discarded SDU. + +In the case where the TFC selection exchange has been initiated by sending the RLC Entity Info parameter to MAC, the UE may wait until after it provides MAC with the requested set of PDUs before discarding the afore-mentioned SDU. + +## 11.2 Unacknowledged mode data transfer procedure + +### 11.2.1 General + +The unacknowledged mode data transfer procedure is used for transferring data between two RLC peer entities, which are operating in unacknowledged mode. Data is transferred from Sender to Receiver. This procedure should only apply to RLC entities in DATA\_TRANSFER\_READY state or LOCAL\_SUSPEND state. Figure 11.2 below illustrates the elementary procedure for unacknowledged mode data transfer. + +Channels that can be used are DTCH, DCCH, CCCH (downlink only), CTCH, SHCCH (downlink only), MCCH, MSCH, MTCH. The type of logical channel depends on if the RLC entity is located in the user plane (DTCH, CTCH, MTCH) or in the control plane (DCCH/CCCH(downlink only)/SHCCH(downlink only)/MCCH/MSCH). One or + +several PDUs may be transmitted in each transmission time interval (TTI). For each TTI, MAC decides which PDU size shall be used and how many PDUs shall be transmitted. + +![Diagram illustrating the unacknowledged mode data transfer procedure. A 'Sender' box is on the left and a 'Receiver' box is on the right. A horizontal arrow labeled 'UMD PDU' points from the Sender to the Receiver. Below each box is a grey rectangular block representing the lower layer.](74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg) + +Diagram illustrating the unacknowledged mode data transfer procedure. A 'Sender' box is on the left and a 'Receiver' box is on the right. A horizontal arrow labeled 'UMD PDU' points from the Sender to the Receiver. Below each box is a grey rectangular block representing the lower layer. + +**Figure 11.2: Unacknowledged mode data transfer procedure** + +### 11.2.2 Transmission of UMD PDU + +Upon a request of unacknowledged mode data transfer from upper layer, the Sender shall: + +- if no SDU discard configuration has been made by upper layers: + - only discard SDUs when the Transmission buffer is full (see subclause 9.7.3); +- if "Timer based SDU Discard without explicit signalling" is configured: + - start a timer Timer\_Discard for each SDU received from upper layer (see subclause 9.7.3); +- schedule the RLC SDUs received from upper layer for transmission; +- if one or more RLC SDUs have been scheduled for transmission: + - notify the lower layer of reception of data from upper layers; + - perform the actions specified in subclause 11.2.2.2. + +A UMD PDU shall be considered to be a padding PDU if it consists only of an RLC Header with one length indicator (indicating that the rest of the PDU is padding) and padding. + +#### 11.2.2.1 UMD PDU contents to set + +The Sender shall: + +- set the field "Sequence Number" equal to VT(US); +- set a "Length Indicator" field for each SDU that ends in the UMD PDU according to subclause 9.2.2.8. + +For each "Extension bit" field in the RLC header, the Sender shall: + +- if the next field in the UMD PDU is a "Length Indicator": + - set the "Extension bit" to "1"; +- otherwise if the next field in the UMD PDU is data: + - set the "Extension bit" to "0". + +#### 11.2.2.2 Submission of UMD PDUs to the lower layer + +If one or more SDUs have been scheduled for transmission according to subclause 11.2.2, the Sender shall: + +- inform the lower layer of the number and size of SDUs scheduled for transmission; +- if "SN\_Delivery" is configured: + - segment, but not concatenate SDUs +- else: + +- segment, and if possible concatenate the SDUs according to the PDU sizes indicated by the lower layer (see subclause 9.2.2.9); +- submit to the lower layer, the requested number of UMD PDUs; +- update VT(US) for each UMD PDU submitted to the lower layer (see subclause 9.4); +- buffer the SDUs that are not submitted to the lower layer according to the discard configuration (see subclause 9.7.3). + +### 11.2.3 Reception of UMD PDU + +Upon delivery of a set of UMD PDUs from the lower layer or from the duplicate avoidance and reordering subentity, the Receiver shall: + +- if "out of sequence SDU delivery" is configured: + - perform the actions specified in subclause 11.2.3.2; +- else: + - perform the actions specified in subclause 11.2.3.1. + +#### 11.2.3.1 SDU discard and re-assembly + +Upon delivery of a set of UMD PDUs from the lower layer or from the duplicate avoidance and reordering subentity, the Receiver shall: + +- if out-of-sequence reception is configured and $SN \geq VR(UM)$ : + - discard the UMD PDU. +- else: + - update VR(US) according to each received UMD PDU (see subclause 9.4); + - if the updating step of VR(US) is not equal to one (i.e. one or more UMD PDUs are missing): + - discard the SDUs that could have segments or "Length Indicators" indicating the end of the SDUs in the missing UMD PDUs according to subclauses 9.2.2.8 and 9.2.2.9. + - if the special "Length Indicator" "1111 100" or "1111 1111 1111 100" is the first "Length Indicator" of a UMD PDU received on the downlink: + - consider the first data octet in this UMD PDU as the first octet of an RLC SDU. + - if the "Extension bit" indicates that the UMD PDU contains a complete SDU which is not segmented, concatenated or padded: + - consider the data part in this UMD PDU as one complete RLC SDU. + - if the special "Length Indicator" "1111 101" or "1111 1111 1111 101" is the first "Length Indicator" of a UMD PDU received on the downlink: + - consider the first data octet in this UMD PDU as the first octet of an RLC SDU and the last data octet as the last octet of the same RLC SDU. + - if the special "Length Indicator" "1111 1111 1111 010" is the first "Length Indicator" of a UMD PDU received on the downlink: + - consider the first data octet in this UMD PDU as the first octet of an RLC SDU and the second last data octet as the last octet of the same RLC SDU. + - reassemble the received UMD PDUs into RLC SDUs; + - submit the RLC SDUs to upper layers through the UM-SAP. + +#### 11.2.3.2 Out of sequence SDU delivery + +To enable the recovery of SDUs from UMD PDUs that are received in different transmissions the receiving function shall store PDUs until all SDUs that are associated with the PDU can be reconstructed or until they are discarded in accordance with the procedures described below. SDUs are transferred to the upper layers as soon as all PDUs that contain the segments of the SDU and the "Length Indicator" indicating the end of the SDU have been received. + +Upon delivery of a set of UMD PDUs from the lower layer, the Receiver shall for each PDU (in the following SN denotes the sequence number of each PDU): + +- If the PDU is the first PDU received (after the receiving entity is established or re-established or after Timer\_OSD expires): + - VR(UOH) shall be assigned the value SN-1. +- if $VR(UOH) \geq SN > VR(UOH) - OSD\_Window\_Size$ then: + - if a PDU with sequence number SN is already stored: + - discard the PDU; + - else: + - store the PDU in sequence number order. +- else: + - VR(UOH) shall be assigned the value SN, thereby advancing the storage window; + - store the PDU in sequence number order; + - remove from storage any PDUs whose sequence numbers, SN, are outside of the storage window $VR(UOH) \geq SN > VR(UOH) - OSD\_Window\_Size$ ; + - if Timer\_OSD is active then Timer\_OSD shall be stopped; + - Timer\_OSD shall be started. +- if a PDU with sequence number SN was stored: + - if the PDU contains one or more complete SDUs and/or if the PDU contains segments of SDUs for which all the remaining segments and length indicators are contained in stored PDUs: + - re-assemble the SDUs; + - submit the SDUs to upper layers through the UM-SAP; + - remove from storage any PDUs which do not contain any segment of a SDU that has not been re-assembled, and do not contain one of the special length indicators "0000 000", "0000 0000 0000 000" or "1111 1111 1111 011" that indicate the end of a SDU that has not been re-assembled. + +NOTE 0: If PDUs are removed from storage after SDU recovery then retransmitted PDUs may result in the duplicate transfer of SDUs to the higher layers. + +- if Timer\_OSD expires: + - remove from storage all stored PDUs. + +NOTE 1: When configured for out of sequence SDU delivery, the transmitter should consider the possibility that a loss of a number of $128 - OSD\_Window\_Size$ consecutively numbered PDUs may result in an undetected protocol error in the receiver, if the transmit state variable VT(US), at the end of a time interval equal to the duration of Timer\_OSD, is greater than $128 + SN - OSD\_Window\_Size + 1$ , where SN is the lowest sequence number of any PDU transmitted or retransmitted within that time interval. + +NOTE 2: The transmitter should not concatenate within a single PDU, SDUs or fractions of SDUs that contain MBMS Access Information messages with SDUs or fractions of SDUs that contain other MCCH message types. + +NOTE 3: SDUs are contained within consecutively numbered PDUs. To enable SDUs containing MBMS Access Information messages to be transmitted at their designated times, the transmitter may transmit PDUs out of sequence order. + +NOTE 4: The transmitter should not transmit within a single PDU, SDUs or fractions of SDUs that contain MBMS Access Information messages with the special length indicator "0000 000", "0000 0000 0000 000", and "1111 1111 1111 011". + +### 11.2.4 Abnormal cases + +#### 11.2.4.1 Length Indicator value reserved for UMD PDU + +Upon delivery by the lower layer of an UMD PDU that contains a "Length Indicator" value specified to be reserved for UMD PDUs in this version of the protocol, the Receiver shall: + +- ignore that UMD PDU. + +#### 11.2.4.2 Invalid length indicator value + +If the "Length Indicator" of an UMD PDU has a value that is larger than the PDU size – RLC header size and is not one of the predefined values listed in the table of subclause 9.2.2.8, the Receiver shall: + +- ignore the UMD PDU. + +#### 11.2.4.3 SDU discard without explicit signalling + +Upon expiry of the timer Timer\_Discard in the Sender, the Sender shall: + +- discard the associated SDU; +- if requested: + - inform the upper layers of the discarded SDU; +- for the first UMD PDU to be transmitted after the discard operation, the Sender shall: + - increment VT(US) so that the "Sequence Number" field in this UMD PDU is incremented with two compared with the previous UMD PDU; + - fill the first data octet in this UMD PDU with the first octet of an RLC SDU; + - if the "Extension bit" does not indicate that the UMD PDU contains a complete SDU which is not segmented, concatenated or padded: + - set the first "Length Indicator" in this UMD PDU to indicate that the previous RLC PDU was exactly filled with the last segment of an RLC SDU (to avoid that the Receiver unnecessarily discards an extra SDU). + +In the case where the TFC selection exchange has been initiated by sending the RLC Entity Info parameter to MAC, the UE may wait until after it provides MAC with the requested set of UMD PDUs before discarding the afore-mentioned SDU. + +#### 11.2.4.4 Invalid PDU size + +In the UE, if the "DL RLC UM LI size" is configured to 7 bits, if a received UMD PDU has a size larger than 125 octets, the Receiver shall: + +- ignore that UMD PDU. + +## 11.3 Acknowledged mode data transfer procedure + +### 11.3.1 General + +The acknowledged mode data transfer procedure is used for transferring data between two RLC peer entities, which are operating in acknowledged mode. Data is transferred from Sender to Receiver. This procedure should only apply to + +RLC entities in DATA\_TRANSFER\_READY state or LOCAL\_SUSPEND state. Figure 11.3 below illustrates the elementary procedure for acknowledged mode data transfer. + +The AMD PDUs shall be transmitted on the DCCH logical channel if the Sender is located in the control plane and on the DTCH if it is located in the user plane. One or several PDUs may be transmitted in each transmission time interval (TTI) and MAC decides how many PDUs shall be transmitted in each TTI. + +![Diagram illustrating the Acknowledged mode data transfer procedure. A Sender box is on the left and a Receiver box is on the right. A horizontal arrow labeled 'AMD PDU' points from the Sender to the Receiver. Below each box is a grey rectangular block representing the lower layers.](9b9262a549828579ab904148450734f6_img.jpg) + +Diagram illustrating the Acknowledged mode data transfer procedure. A Sender box is on the left and a Receiver box is on the right. A horizontal arrow labeled 'AMD PDU' points from the Sender to the Receiver. Below each box is a grey rectangular block representing the lower layers. + +**Figure 11.3: Acknowledged mode data transfer procedure** + +### 11.3.2 Transmission of AMD PDU + +Upon a request of acknowledged mode data transfer from upper layers or upon retransmission of AMD PDUs, the Sender shall: + +- when RLC SDUs are received from upper layers: + - if "fixed RLC PDU size" has been configured: + - segment, and if possible concatenate the RLC SDUs into AMD PDUs where the fixed PDU size is configured by upper layer (see subclause 9.2.2.9); + - if the last octet of the PDU is the last octet of an SDU and there is no SDU concatenation inside the PDU, and the "use of the special value of the HE field" has been configured by higher layers, set the HE field to indicate that the last octet of the PDU is the last octet of an SDU (see subclause 9.2.2.7). + - if "flexible RLC PDU size" has been configured: + - the last segment of an RLC SDU shall be concatenated with the first segment of the next RLC SDU in order to fill the data field at least up to the Minimum UL RLC PDU size. If data to be transmitted is not enough to create an AMD PDU of the minimum size, it is allowed to create an AMD PDU including all data to be transmitted, even if the resulting size is smaller than the Minimum UL RLC PDU size. + - set a "Length Indicator" field for each SDU that ends in the AMD PDU according to subclause 9.2.2.8, except for the SDUs where the end of the SDU has been indicated by the HE field according to subclause 9.2.2.7; + - if "Timer based SDU Discard with explicit signalling" is configured: + - start a timer Timer\_Discard for each SDU received from upper layer (see subclause 9.7.3); + - schedule the AMD PDUs for transmission; +- for each AMD PDU which has been negatively acknowledged (see subclause 11.5.3): + - if the "Sequence Number" of the AMD PDU is less than VT(MS): + - schedule the AMD PDU for retransmission; +- if a poll has been triggered by one of configured polling functions (see subclause 9.7.1); and +- if polling is not prohibited (see subclause 9.5); and +- if no AMD PDU is scheduled for transmission or retransmission; and +- if there is at least one PDU that has been transmitted, has not been discarded and has not yet been acknowledged: + +- if the value of "Configured\_Tx\_Window\_Size" is larger than or equal to "2048": + - select the AMD PDU with "Sequence Number" equal to VT(S)-1; or + - assemble a POLL SUFI according to subclause 9.2.2.11.9 when "flexible RLC PDU size" is configured; +- otherwise if the "Configured\_Tx\_Window\_Size" is less than "2048": + - select the AMD PDU with "Sequence Number" equal to VT(S)-1; or + - select an AMD PDU that has not been discarded and has not yet been acknowledged by the peer entity; or + - assemble a POLL SUFI according to subclause 9.2.2.11.9 when "flexible RLC PDU size" is configured; +- if an AMD PDU was selected, schedule the selected AMD PDU for retransmission (in order to transmit a poll), or if a POLL SUFI was assembled, schedule a STATUS PDU containing the POLL SUFI for transmission: + - if the timer Timer\_Poll is configured: + - start the timer Timer\_Poll according to subclause 9.5. + +NOTE 1: In downlink, if "flexible RLC PDU size" is configured, the UTRAN should segment, and if possible concatenate the RLC SDUs into AMD PDUs with a size not larger than the maximum RLC PDU size. + +NOTE 2: In downlink, UTRAN can initiate the Polling function by assembling a POLL SUFI when "flexible RLC PDU size" in downlink is configured. If a POLL SUFI was assembled, UTRAN should schedule and submit to lower layer a STATUS PDU containing the POLL SUFI. + +NOTE 3: In uplink, the UE can initiate the Polling function by assembling a POLL SUFI according to subclause 9.2.2.11.9 when "flexible RLC PDU size" in uplink is configured. If a POLL SUFI was assembled, the UE should schedule and submit to lower layer a STATUS PDU containing the POLL SUFI. + +Each time an AMD PDU is scheduled for transmission or retransmission, the Sender shall: + +- increment the value of the corresponding VT(DAT); +- if VT(DAT) = MaxDAT: + - perform the actions specified in subclause 11.3.3a; +- else: + - notify the lower layer that data is available for transmission; + - perform the actions specified in subclause 11.3.2.2. + +In AM, a PDU shall be considered to be a padding PDU if it is: + +- an AMD PDU consisting only of an RLC Header with one "Length Indicator" (indicating that the rest of the PDU is padding) and padding; or +- a STATUS PDU consisting only of a NO\_MORE SUFI. + +#### 11.3.2.1 AMD PDU contents to set + +If the AMD PDU is transmitted for the first time, the Sender shall: + +- set the "Sequence Number" field equal to VT(S); +- if the last octet of the PDU is the last octet of an SDU and there is no SDU concatenation inside the PDU, and the use of the special value of HE field has been configured by higher layers, set the HE field to indicate that the last octet of the PDU is the last octet of an SDU (see subclause 9.2.2.7) +- set a "Length Indicator" field for each SDU that ends in the AMD PDU according to subclause 9.2.2.8, except for the SDUs where the end of the SDU has been indicated by the HE field according to subclause 9.2.2.7; + +- set the "Polling bit" to the value specified in subclause 11.3.2.1.1. + +Otherwise if the AMD PDU is retransmitted: + +- use the same value of the "Sequence Number" field as in the original transmission of the AMD PDU; +- if the "Length Indicator" fields needed in the AMD PDU according to subclause 9.2.2.8 has changed due to that a piggybacked STATUS PDU is included in the AMD PDU or a piggybacked STATUS PDU was included in the previous transmission of the AMD PDU: + - update the "Length Indicator" fields according to 9.2.2.8. +- set the "Polling bit" to the value specified in subclause 11.3.2.1.1. + +##### 11.3.2.1.1 Setting of the Polling bit + +The Sender shall: + +- if a poll has been triggered by one or several poll triggers (see subclause 9.7.1): + - if polling is not prohibited, see subclause 9.5: + - set the "Polling bit" in the AMD PDU header to "1"; +- otherwise: + - set the "Polling bit" in the AMD PDU header to "0". + +##### 11.3.2.1.2 Void + +#### 11.3.2.2 Submission of AMD PDUs to lower layer + +If one or more AMD PDUs have been scheduled for transmission or retransmission according to subclause 11.3.2, the Sender shall: + +- not submit any AMD PDUs to lower layer that is not allowed to transmit. AMD PDUs are only allowed to transmit: + - if the AMD PDU has a "Sequence Number" < VT(MS) or the AMD PDU has a "Sequence Number" equal to VT(S)-1; and + - if the AMD PDU is not restricted to be transmitted by the local suspend function, see subclause 9.7.5. +- inform the lower layer of both the numbers of AMD PDUs scheduled and allowed for transmission or retransmission; +- set the AMD PDU contents according to subclause 11.3.2.1; +- submit to the lower layer the requested number of AMD PDUs; +- treat retransmissions with higher priority than AMD PDUs transmitted for the first time; +- update the state variables in clause 9.4 for each AMD PDU submitted to lower layer except VT(DAT) which has already been updated, see subclause 11.3.2; +- if the "Polling bit" is set to "1" in any of the AMD PDUs; and +- if the timer Timer\_Poll is configured; + - start the timer Timer\_Poll according to subclause 9.5; +- buffer the AMD PDUs that are not submitted to the lower layer according to the discard configuration (see subclause 9.7.3). + +### 11.3.3 Reception of AMD PDU by the Receiver + +Upon reception of an AMD PDU, the Receiver shall: + +- in the UE if "fixed RLC PDU size" has been configured: + - if the "downlink AMD PDU size" has not yet been set: + - set the "downlink AMD PDU size" to the size of the received PDU. +- update VR(R), VR(H) and VR(MR) state variables for each received AMD PDU (see clause 9.4); +- if Timer\_Reordering is configured: + - if a received AMD PDU SN = VR(MS) + - update VR(MS) to SN of the first AMD PDU that has not been received; + - if Timer\_Reordering is running: + - if VR(X) = VR(R); or + - if VR(X) falls outside of the receiving window and VR(X) is not equal to VR(MR): + - stop and reset Timer\_Reordering; + - if Timer\_Reordering is not running (includes the case Timer\_Reordering is stopped due to actions above): + - if VR(H) > VR(R): + - start Timer\_Reordering; + - set VR(X) to VR(H). +- if a received AMD PDU includes a "Polling bit" set to "1", or "Missing PDU Indicator" is configured and the Receiver detects that a PDU is missing: + - initiate the STATUS PDU transfer procedure; +- reassemble the received AMD PDUs into RLC SDUs; +- if "In-Sequence Delivery" is configured: + - deliver the RLC SDUs in-sequence (i.e. in the same order as the RLC SDUs were originally transmitted by the peer entity) to upper layers through the AM-SAP. +- otherwise: + - deliver the RLC SDUs in arbitrary order to upper layers through the AM-SAP. + +### 11.3.3a Reached maximum number of attempts + +If VT(DAT) = MaxDAT, the Sender shall: + +- if "No\_discard after MaxDAT number of transmissions" is configured: + - initiate the RLC reset procedure, see subclause 11.4. +- if "SDU discard after MaxDAT number of transmissions" is configured: + - initiate the "SDU discard with explicit signalling" procedure for the corresponding SDU, see subclause 11.6. + +### 11.3.4 Abnormal cases + +#### 11.3.4.1 Void + +#### 11.3.4.2 Receiving an AMD PDU outside the reception window + +Upon reception of an AMD PDU with "Sequence Number" outside the interval $VR(R) \leq SN < VR(MR)$ , the Receiver shall: + +- discard the AMD PDU; +- if the "polling bit" in the discarded AMD PDU is set to "1": + - initiate the STATUS PDU transfer procedure. + +#### 11.3.4.3 Timer\_Discard timeout + +##### 11.3.4.3.1 SDU discard with explicit signalling + +Upon expiry of the timer Timer\_Discard, the Sender shall: + +- initiate the SDU discard with explicit signalling procedure, see subclause 11.6.2. + +In the case where the TFC selection exchange has been initiated by sending the RLC Entity Info parameter to MAC, the UE may wait until after it provides MAC with the requested set of PDUs before discarding the afore-mentioned SDUs. + +#### 11.3.4.4 Void + +#### 11.3.4.5 Invalid length indicator value + +If the "Length Indicator" of an AMD PDU has a value that is larger than the PDU size – RLC header size and is not one of the predefined values listed in the table of subclause 9.2.2.8, the Receiver shall: + +- ignore that AMD PDU. + +#### 11.3.4.6 Length Indicator value reserved for AMD PDU + +Upon delivery by the lower layer of an AMD PDU that contains a "Length Indicator" value specified to be reserved for AMD PDUs in this version of the protocol, the Receiver shall: + +- ignore that AMD PDU. + +#### 11.3.4.7 Void + +#### 11.3.4.8 Receiving an AMD PDU within the reception window more than once (Handling of Duplicates) + +Upon reception of an AMD PDU with a "Sequence Number" within the interval $VR(R) \leq SN < VR(MR)$ , for which "Sequence Number" an AMD PDU has already been received, the Receiver shall: + +- discard the AMD PDU; +- consider the AMD PDU with this "Sequence Number" as having been correctly received in the next status report to be transmitted; +- if the "polling bit" in the discarded AMD PDU is set to "1": + - initiate the STATUS PDU transfer procedure. +- if a piggybacked STATUS PDU is included in the AMD PDU: + - perform the actions specified in subclause 11.5.3. + +#### 11.3.4.9 Full Buffer Behavior + +It is foreseen that in some conditions, e.g. when the window size is re-configured, the UE may have memory limitations. + +While the buffer memory is full: + +- the UE is not required to segment RLC SDUs into AMD PDUs as per Subclause 11.3.2; +- the UE shall: + - be able to process incoming AMD PDUs (especially to be able to process and store the AMD PDU with "Sequence Number" = VR(R)); + - operate according to the normal protocol, e.g. process STATUS reports and perform retransmissions; +- the UE may discard received AMD PDUs with "Sequence Number" within the receiving window and consider the discarded AMD PDUs as not having been received. + +#### 11.3.4.10 Invalid PDU size + +In the UE, if "fixed RLC PDU size" has been configured and if a received AMD PDU has a size different from the configured "downlink AMD PDU size", the Receiver shall: + +- ignore that AMD PDU. + +### 11.3.5 Transmission of POLL SUFI + +Each time a STATUS PDU containing the POLL SUFI is scheduled for transmission, the Sender shall: + +- increment the value of the corresponding VT(DAT) of the AMD PDU with sequence number equal to VT(S)-1; +- if VT(DAT) = MaxDAT: + - perform the actions specified in subclause 11.3.3a; +- else: + - notify the lower layer that STATUS PDU is available for transmission. + +## 11.4 RLC reset procedure + +### 11.4.1 General + +The RLC reset procedure is used to reset two RLC peer entities, which are operating in acknowledged mode. Figure 11.4 below illustrates the elementary procedure for an RLC reset. During the reset procedure the hyper frame numbers (HFN) in UTRAN and UE are synchronised. Two HFNs used for ciphering needs to be synchronised, DL HFN in downlink and UL HFN in uplink. In the reset procedure, the highest UL HFN and DL HFN used by the RLC entity in the transmitting sides, i.e. the HFNs associated with AMD PDUs of "Sequence Number"=VT(S)-1 if at least one AMD PDU had been transmitted or of "Sequence Number"=0 if no AMD PDU had been transmitted, are exchanged between UE and UTRAN. + +The RESET PDUs and the RESET ACK PDUs have higher priority than AMD PDUs. + +![Sequence diagram of the RLC reset procedure. A Sender sends a RESET message to a Receiver, and the Receiver responds with a RESET ACK message.](8395ccdee8a80af834aca2bdfd7f9a9b_img.jpg) + +``` + +sequenceDiagram + participant Sender + participant Receiver + Note left of Sender: + Sender->>Receiver: RESET + Note right of Receiver: + Receiver->>Sender: RESET ACK + Note left of Sender: + +``` + +Sequence diagram of the RLC reset procedure. A Sender sends a RESET message to a Receiver, and the Receiver responds with a RESET ACK message. + +Figure 11.4: RLC reset procedure + +### 11.4.2 Initiation + +The Sender shall: + +- if one of the following triggers is detected: + - 1) "No\_Discard after MaxDAT number of transmissions" is configured and VT(DAT) equals the value MaxDAT (see subclause 9.7.3.4); + - 2) VT(MRW) equals the value MaxMRW; + - 3) A STATUS PDU or a piggybacked STATUS PDU including "erroneous Sequence Number" is received (see clause 10); + - stop transmitting any AMD PDU or STATUS PDU; + - ignore any incoming AMD PDU, piggybacked STATUS PDU or STATUS PDU; + - increment VT(RST) by 1; + - if VT(RST) = MaxRST: + - perform the actions specified in subclause 11.4.4a. + - else (if VT(RST) < MaxRST): + - submit a RESET PDU to the lower layer; + - start the timer Timer\_RST according to the description in subclause 9.5. + +NOTE: If the TFC selection exchange has been initiated by sending the RLC Entity Info parameter to MAC, the RLC entity may delay the RLC reset procedure until the end of the next TTI. + +When a reset procedure has been initiated it can only be ended upon reception of a RESET ACK PDU with the same RSN value as in the corresponding RESET PDU, upon request of re-establishment due to request of re-establishment (for the whole RLC entity or for only the transmitting or receiving side of the RLC entity), or release from upper layer. A reset procedure is not interrupted by the reception of a RESET PDU from the peer entity. + +#### 11.4.2.1 RESET PDU contents to set + +The Sender shall: + +- set the HFNI field to the currently highest used HFN (DL HFN when the RESET PDU is sent by UTRAN or UL HFN when the RESET PDU is sent by the UE); +- set the RSN field to the sequence number of the RESET PDU. The sequence number of the first RESET PDU after the AM entity is established or re-established (for the whole RLC entity or for only the transmitting or receiving side of the RLC entity) shall be "0". This sequence number is incremented every time a new RESET PDU is transmitted, but not when a RESET PDU is retransmitted. + +### 11.4.3 Reception of the RESET PDU by the Receiver + +Upon reception of a RESET PDU the Receiver shall: + +- if the RESET PDU is not the first RESET PDU received since the entity was established or re-established; and +- if the RSN value in the RESET PDU is the same as the RSN value in the last received RESET PDU: + - only submit a RESET ACK PDU to the lower layer with the contents set exactly as in the last transmitted RESET ACK PDU (i.e., in this case the RLC entity is not reset). +- if the RESET PDU is the first RESET PDU received since the entity was established or re-established; or +- if the RSN value is different from the RSN value in the last received RESET PDU: + - submit a RESET ACK PDU to the lower layer with the content set as specified in subclause 11.4.3.1; + - reset the state variables described in subclause 9.4 except VT(RST) to their initial values; + - stop all the timers described in subclause 9.5 except Timer\_RST, Timer\_Discard, Timer\_Poll\_Periodic and Timer\_Status\_Periodic; + +- reset configurable parameters to their configured values; +- discard all RLC PDUs in the receiving side of the AM RLC entity; +- discard all RLC SDUs that were transmitted before the reset in the transmitting side of the AM RLC entity; +- if requested for the transmitting side: + - inform the upper layers of the discarded SDUs. +- set the HFN (DL HFN when the RESET PDU is received in UE or UL HFN when the RESET PDU is received in UTRAN) equal to the HFNI field in the received RESET PDU; +- increase with one the UL HFN and DL HFN, and the updated HFN values shall be used for the first transmitted and received AMD PDUs after the reset procedure. + +NOTE: If the TFC selection exchange has been initiated by sending the RLC Entity Info parameter to MAC, the RLC entity may delay the RLC SDUs discard in the transmitting side of the AM RLC entity until the end of the next TTI. + +#### 11.4.3.1 RESET ACK PDU contents to set + +The RLC entity shall: + +- set the hyper frame number indicator field (HFNI) to the currently highest used HFN (DL HFN when the RESET ACK PDU is sent by UTRAN or UL HFN when the RESET ACK PDU is sent by the UE); +- set the RSN field to the same value as in the corresponding received RESET PDU. + +### 11.4.4 Reception of the RESET ACK PDU by the Sender + +Upon reception of a RESET ACK PDU, the Sender shall: + +- if the Sender has already transmitted a RESET PDU which has not been yet acknowledged by a RESET ACK PDU: + - if the received RSN value is the same as the one in the corresponding RESET PDU: + - set the HFN value (DL HFN when the RESET ACK PDU is received in UE or UL HFN when the RESET ACK PDU is received in UTRAN) to the HFNI field of the received RESET ACK PDU; + - reset the state variables described in subclause 9.4 to their initial values; + - stop all the timers described in subclause 9.5 except Timer\_Discard, Timer\_Poll\_Periodic and Timer\_Status\_Periodic; + - reset configurable parameters to their configured values; + - discard all RLC PDUs in the receiving side of the AM RLC entity; + - discard all RLC SDUs that were transmitted before the reset in the transmitting side of the AM RLC entity; + - if requested for the transmitting side: + - inform the upper layers of the discarded SDUs. + - increase with one the UL HFN and DL HFN, and the updated HFN values shall be used for the first transmitted and received AMD PDUs after the reset procedure; + - otherwise (if the received RSN value is not the same as the one in the corresponding RESET PDU): + - discard the RESET ACK PDU; + +- otherwise (if the Sender has not transmitted a RESET PDU which has not been yet acknowledged by a RESET ACK PDU): + - discard the RESET ACK PDU. + +NOTE: If the TFC selection exchange has been initiated by sending the RLC Entity Info parameter to MAC, the RLC entity may delay the RLC SDUs discard in the transmitting side until the end of the next TTI. + +### 11.4.4a Reached maximum number of attempts + +If VT(RST) = MaxRST, the Sender shall: + +- terminate the ongoing RLC RESET procedure; +- stop the timer Timer\_RST if it was started; +- indicate unrecoverable error to upper layer. + +### 11.4.5 Abnormal cases + +#### 11.4.5.1 Timer\_RST timeout + +If Timer\_RST expires before the reset procedure is terminated, the Sender shall: + +- increment VT(RST) by one; +- if VT(RST) < MaxRST: + - set the RESET PDU as previously transmitted; + - transmit the RESET PDU; + - restart Timer\_RST according to the description in subclause 9.5. +- else (if VT(RST) = MaxRST): + - perform the actions specified in subclause 11.4.4a. + +#### 11.4.5.2 Void + +#### 11.4.5.3 Reception of the RESET PDU by the Sender + +Upon reception of a RESET PDU, the Sender shall: + +- submit a RESET ACK PDU to the lower layer with the content set as specified in subclause 11.4.3.1; +- reset the state variables described in subclause 9.4 except VT(RST) to their initial values; +- stop all the timers described in subclause 9.5 except Timer\_RST, Timer\_Discard, Timer\_Poll\_Periodic and Timer\_Status\_Periodic; +- reset configurable parameters to their configured values; +- discard all RLC PDUs in the receiving side of the AM RLC entity; +- discard all RLC SDUs that were transmitted before the reset in the transmitting side of the AM RLC entity; +- if requested for the transmitting side: + - inform the upper layers of the discarded SDUs. +- set the HFN (DL HFN when the RESET PDU is received in UE or UL HFN when the RESET PDU is received in UTRAN) equal to the HFNI field in the received RESET PDU. + +NOTE: If the TFC selection exchange has been initiated by sending the RLC Entity Info parameter to MAC, the RLC entity may delay the RLC SDUs discard in the transmitting side until the end of the next TTI. + +## 11.5 STATUS report transfer procedure + +### 11.5.1 General + +The status report transfer procedure is used for transferring of status information between two RLC peer entities, which are operating in acknowledged mode. Figure 11.5 below illustrates the elementary procedure for status report transfer. A status report consists of one or several STATUS PDUs. + +In case two logical channels are configured in the uplink, only acknowledgement status reports, MRW ACK SUFI and WINDOW SUFI shall be transmitted on the second logical channel. In case two logical channels are configured in the downlink, control PDUs can be transmitted on any of the two logical channels. + +The STATUS PDUs have higher priority than AMD PDUs. + +![Diagram illustrating the Status report transfer procedure. A Sender (top left) and a Receiver (top right) are shown. A horizontal arrow labeled 'STATUS PDU' points from the Receiver to the Sender. Below each entity is a grey rectangular block representing the lower layers.](bb3063a33c89b248574f64b6d8dfc404_img.jpg) + +``` + +graph LR + Sender[Sender] + Receiver[Receiver] + Receiver -- STATUS PDU --> Sender + subgraph LowerLayers + direction TB + L1[ ] + L2[ ] + end + Sender --- L1 + Receiver --- L2 + style L1 fill:#888,stroke:none + style L2 fill:#888,stroke:none + +``` + +Diagram illustrating the Status report transfer procedure. A Sender (top left) and a Receiver (top right) are shown. A horizontal arrow labeled 'STATUS PDU' points from the Receiver to the Sender. Below each entity is a grey rectangular block representing the lower layers. + +Figure 11.5: Status report transfer procedure + +### 11.5.2 Initiation + +The Receiver shall: + +- if one of the following triggers is detected: + - 1) The "Polling bit" in a received AMD PDU is set to "1"; + - 2) "Missing PDU Indicator" is configured and a missing AMD PDU is detected; + - 3) The "Timer based STATUS transfer" is configured and the timer Timer\_Status\_Periodic has expired: + - act on the trigger as specified in subclause 9.7.2. + - 4) Void + - 5) If the flexible RLC PDU size is configured and POLL SUFI is received: + - consider that Poll\_SN has been transmitted by the sender as specified in subclause 9.4: + - act on the trigger as specified in subclause 9.7.2. + +#### 11.5.2.1 Piggybacked STATUS PDU + +The Receiver may: + +- if STATUS PDU(s) to be sent fit into padding octets in AMD PDU(s) to be sent: + - piggyback a STATUS PDU on the AMD PDU to be sent. + +Submission of a piggybacked STATUS PDU in an AMD PDU to the lower layer follows the same rules as an ordinary STATUS PDU. + +#### 11.5.2.2 STATUS PDU contents to set + +On triggering of a status report, the Receiver shall: + +- if the "STATUS prohibit" is not active: + +- If Timer\_Reordering is not configured: + - include negative acknowledgements for all AMD PDUs detected as missing; + - include an ACK SUFI positively acknowledging all AMD PDUs received up to at least VR(R); +- If Timer\_Reordering is configured, for all SN such that VR(R) <= SN < VR(MS): + - include negative acknowledgements for all AMD PDUs detected as missing; + - include an ACK SUFI positively acknowledging all AMD PDUs received up to at least VR(R); +- if an MRW SUFI assembled as specified in subclause 11.6.2.2 had not been sent: + - optionally include the MRW SUFI; +- if an MRW\_ACK SUFI assembled as specified in subclause 11.6.2.2 is awaiting transmission: + - optionally include the MRW\_ACK SUFI; +- if the Sender's transmission window is to be updated: + - optionally include the WINDOW SUFI; +- if all SUFIs can be accommodated in one STATUS PDU: + - construct the status report using one STATUS PDU, using one of the allowed PDU sizes; + - if the SUFIs included do not fill the entire STATUS PDU: + - if the STATUS PDU is not terminated with an ACK SUFI: + - terminate the STATUS PDU with a NO\_MORE SUFI. + - use padding in the remainder of the STATUS PDU (padding size may be zero); +- otherwise (the status report is segmented): + - construct STATUS PDUs including only complete SUFIs using one of the allowed PDU sizes. The set of STATUS PDUs shall accommodate all the SUFIs to form the complete status report. Indication of the same AMD PDU shall not be given in more than one STATUS PDU of a status report, but the ACK SUFI can be present in more than one STATUS PDU of a status report; + - if any STATUS PDU constructed is not entirely filled with SUFIs: + - if the STATUS PDU is not terminated with an ACK SUFI: + - terminate that STATUS PDU with a NO\_MORE SUFI. + - use padding in the remainder of that STATUS PDU (padding size may be zero). + +Which SUFI fields to use is implementation dependent. Bitmap SUFI is used to indicate both received and/or missing AMD PDUs. List SUFI and/or Relative List SUFI are used to indicate missing AMD PDUs only. Acknowledgement SUFI is used to indicate the received AMD PDUs. (For SUFI details see 9.2.2.11.) + +#### 11.5.2.3 Submission of STATUS PDUs to the lower layer + +The Receiver shall: + +- inform the lower layer of the STATUS PDUs scheduled for transmission; +- submit to the lower layer, the requested number of PDUs (STATUS PDUs, piggybacked AMD/STATUS PDUs and optionally AMD PDUs, see also subclause 11.3.2.2); +- if "Timer based STATUS transfer" is configured and the timer Timer\_Status\_Periodic has expired: + - restart the timer Timer\_Status\_Periodic according to subclause 9.5 f); + +- if the STATUS PDU includes the MRW SUFI: + - start the timer Timer\_MRW according to subclause 9.5 i). + +### 11.5.3 Reception of the STATUS PDU by the Sender + +Upon reception of the STATUS PDU/piggybacked STATUS PDU, the Sender shall: + +- if an RLC SDU is positively acknowledged by the STATUS PDU: + - if requested: + - inform the upper layers of the reception of the RLC SDU by the peer AM RLC entity. +- update the state variables VT(A) and VT(MS) according to the received STATUS PDU/piggybacked STATUS PDU; +- if the STATUS PDU includes negatively acknowledged AMD PDUs: + - initiate the acknowledged data transfer procedure; and + - retransmit these AMD PDUs. Retransmitted AMD PDUs shall have higher priority than AMD PDUs to be transmitted for the first time; + - if an AMD PDU is negatively acknowledged more than once in a STATUS PDU: + - retransmit the AMD PDU only once. +- if the STATUS PDU includes the MRW SUFI: + - take the actions specified in subclause 11.6.3. +- if the STATUS PDU includes the MRW\_ACK SUFI: + - take the actions specified in subclause 11.6.4. +- if the STATUS PDU includes the WINDOW SUFI: + - update the current transmission window size, VT(WS). + +### 11.5.4 Abnormal cases + +#### 11.5.4.1 Void + +## 11.6 SDU discard with explicit signalling procedure + +### 11.6.1 General + +The SDU discard with explicit signalling procedure is used for discarding SDUs and transferring the discard information between two peer entities, which are operating in acknowledged mode. The Sender shall discard an SDU that has not been successfully transmitted for a period of time or for a number of transmissions, and send a Move Receiving Window (MRW) SUFI to the Receiver. According to the MRW SUFI, the Receiver shall discard AMD PDUs carrying that SDU and update the reception window. Figure 11.6 below illustrates the elementary procedure for SDU discard with explicit signalling. + +![Sequence diagram illustrating SDU discard with explicit signalling. A Sender sends a STATUS PDU (MRW SUFI) to a Receiver, which responds with a STATUS PDU (MRW_ACK SUFI).](e7010c66da16316c2935dfbbef5056b3_img.jpg) + +``` + +sequenceDiagram + participant Sender + participant Receiver + Sender->>Receiver: STATUS PDU (MRW SUFI) + Receiver-->>Sender: STATUS PDU (MRW_ACK SUFI) + +``` + +Sequence diagram illustrating SDU discard with explicit signalling. A Sender sends a STATUS PDU (MRW SUFI) to a Receiver, which responds with a STATUS PDU (MRW\_ACK SUFI). + +**Figure 11.6: SDU discard with explicit signalling** + +### 11.6.2 Initiation + +The Sender shall initiate the SDU discard with explicit signalling procedure if one of the following triggers is detected: + +- "Timer based SDU discard with explicit signalling" is configured, Timer\_Discard expires for an SDU, and one or more segments of the SDU have been submitted to lower layer; +- "Timer based SDU discard with explicit signalling" is configured, Timer\_Discard expires for an SDU, and "Send MRW" is configured; +- "SDU discard after MaxDAT number of transmissions" is configured, and MaxDAT number of transmissions is reached (i.e. $VT(DAT) \geq MaxDAT$ ) for an AMD PDU. + +Upon initiation of the SDU discard with explicit signalling procedure, the Sender shall: + +- if "Timer based SDU discard with explicit signalling" is configured: + - discard all SDUs up to and including the SDU for which the timer Timer\_Discard expired. +- if "SDU discard after MaxDAT number of transmissions" is configured: + - discard all SDUs that have segments or "Length Indicators" indicating the end of the SDUs in AMD PDUs with "Sequence Number" SN inside the interval $VT(A) \leq SN \leq X$ , where X is the value of the "Sequence Number" of the AMD PDU with $VT(DAT) \geq MaxDAT$ . +- if requested: + - inform the upper layers of the discarded SDUs +- discard all AMD PDUs including segments of the discarded SDUs or "Length Indicators" indicating the end of the SDUs, unless they also carry a segment of a SDU which is not discarded; +- if more than 15 discarded SDUs are to be informed to the Receiver (see subclause 11.6.2.2): + - if "Send MRW" is not configured: + - assemble an MRW SUFI with the discard information of the SDUs. + - otherwise ("Send MRW" is configured): + - assemble an MRW SUFI with the discard information of the first 15 SDUs; and + - include the discard information of the rest SDUs in another MRW SUFI which shall be sent by the next SDU discard with explicit signalling procedure (after the current SDU discard with explicit signalling procedure is terminated). +- otherwise (less than or equal to 15 discarded SDUs are to be informed to the Receiver): + - assemble an MRW SUFI with the discard information of the SDUs. +- schedule and submit to lower layer a STATUS PDU/piggybacked STATUS PDU containing the MRW SUFI; +- if $SN\_MRW_{LENGTH}$ in the MRW SUFI $> VT(S)$ : + +- update VT(S) to SN\_MRWLENGTH. +- start a timer Timer\_MRW according to subclause 9.5. + +If a new SDU discard with explicit signalling procedure is triggered when the current SDU discard with explicit signalling procedure is still going on, no new MRW SUFIs shall be sent before the current SDU discard with explicit signalling procedure is terminated by one of the termination criteria specified in subclause 11.6.4. + +#### 11.6.2.1 Void + +#### 11.6.2.2 STATUS PDU contents to set + +The Sender shall: + +- if "Send MRW" is configured: + - if no new SDU is present inside the AMD PDU which contains the "Length Indicator" of the last discarded SDU or if the AMD PDU contains the special value of the HE field to indicate the end of the last discarded SDU: + - set the last SN\_MRWi field in the MRW SUFI to 1 + "Sequence Number" of the AMD PDU which contains the "Length Indicator" of the last discarded SDU or the special value of the HE field to indicate the end of the last discarded SDU; + - set the NLENGTH field in the MRW SUFI to "0000". + - otherwise: + - set the last SN\_MRWi field in the MRW SUFI to the "Sequence Number" of the AMD PDU which contains the "Length Indicator" of the last discarded SDU; + - set the NLENGTH field in the MRW SUFI so that the last data octet to be discarded in the Receiver shall be the octet indicated by the NLENGTH:th "Length Indicator" field of the AMD PDU which contains the "Length Indicator" of the last discarded SDU; + - set each of the other SN\_MRWi fields in the MRW SUFI to the "Sequence Number" of the AMD PDU which contains the "Length Indicator" of the i:th discarded SDU or the special value of the HE field to indicate the end of the i:th discarded SDU. +- otherwise ("Send MRW" is not configured): + - if no new SDU is present inside the AMD PDU which contains the "Length Indicator" of the last discarded SDU or if the AMD PDU contains the special value of the HE field to indicate the end of the last discarded SDU: + - set the last SN\_MRWi field in the MRW SUFI to 1 + "Sequence Number" of the AMD PDU which contains the "Length Indicator" of the last SDU to be discarded in the Receiver or the special value of the HE field to indicate the end of the last discarded SDU; + - set the NLENGTH field in the MRW SUFI to "0000". + - otherwise: + - set the last SN\_MRWi field in the MRW SUFI to the "Sequence Number" of the AMD PDU which contains the "Length Indicator" of the last SDU to be discarded in the Receiver; + - set the NLENGTH field in the MRW SUFI so that the last data octet to be discarded in the Receiver shall be the octet indicated by the NLENGTH:th "Length Indicator" field of the AMD PDU which contains the "Length Indicator" of the last SDU to be discarded in the Receiver; + - optionally set each of the other SN\_MRWi fields in the MRW SUFI to the "Sequence Number" of the AMD PDU which contains the "Length Indicator" or the special value of the HE field to indicate the end of the i:th SDU to be discarded in the Receiver; + +- if the MRW SUFI contains only one SN\_MRWi field and the value of SN\_MRWi field $\geq$ VT(A)+Configured\_Tx\_Window\_Size: + - set the LENGTH field in the MRW SUFI to "0000". +- otherwise: + - set the LENGTH field in the MRW SUFI to the number of SN\_MRWi fields in the same MRW SUFI. In this case, SN\_MRWi shall be in the interval $VT(A) \leq SN\_MRW_i < VT(A)+Configured\_Tx\_Window\_Size$ . + +### 11.6.3 Reception of the STATUS PDU by the Receiver + +Upon reception of the STATUS PDU/piggybacked STATUS PDU containing an MRW SUFI, the Receiver shall: + +- if the LENGTH field in the received MRW SUFI is "0000": + - consider SN\_MRWi to be above or equal to VR(R). +- otherwise: + - consider SN\_MRWi to be less than VR(MR); +- consider all the SN\_MRWi other than SN\_MRWi to be in sequential order within the list and sequentially above or equal to SN\_MRWi-1; +- deliver all the successfully received SDUs from the SDU that have segments or "Length Indicators" indicating the end of the SDUs in AMD PDU with "Sequence Number" of VR(R) up to and including the last SDU that is indicated by the MRW SUFI; +- discard AMD PDUs up to and including the PDU with sequence number SN\_MRWLENGTH-1; +- if the NLENGTH field in the received MRW SUFI is "0000": + - reassemble from the first data octet of the AMD PDU with sequence number SN\_MRWLENGTH after the discard. +- otherwise: + - discard further the data octets in the AMD PDU with sequence number SN\_MRWLENGTH up to and including the octet indicated by the NLENGTH:th "Length Indicator" field of the PDU with sequence number SN\_MRWLENGTH; + - reassemble from the succeeding data octet in the AMD PDU with sequence number SN\_MRWLENGTH after the discard; +- if "Send MRW" is configured: + - inform upper layers about all of the discarded SDUs that were not previously delivered to upper layer or discarded by other MRW SUFIs; +- update the state variables VR(R), VR(H) and VR(MR) according to the received STATUS PDU/piggybacked STATUS PDU; +- assemble a MRW\_ACK SUFI according to subclause 11.6.3.1; +- schedule and submit to lower layer a STATUS PDU/piggybacked STATUS PDU containing the MRW\_ACK SUFI. + +#### 11.6.3.1 STATUS PDU contents to set + +The Receiver shall: + +- set the SN\_ACK field in the MRW\_ACK SUFI to the new value of VR(R), updated after reception of the MRW SUFI; +- if the SN\_ACK field in the MRW\_ACK SUFI is set equal to the SN\_MRWLENGTH field in the received MRW SUFI: + +- set the N field in the MRW\_ACK SUFI to the NLENGTH field in the received MRW SUFI. +- otherwise: + - set the N field in the MRW\_ACK SUFI to "0000". +- include the MRW\_ACK SUFI in the next STATUS PDU/piggybacked STATUS PDU to be transmitted, according to subclause 11.5.2. + +### 11.6.4 Termination + +The Sender shall terminate the SDU discard with explicit signalling procedure if one of the following criteria is fulfilled: + +- a STATUS PDU/piggybacked STATUS PDU containing an MRW\_ACK SUFI is received, and the SN\_ACK field in the received MRW\_ACK SUFI > the SN\_MRWLENGTH field in the transmitted MRW\_SUFI, and the N field in the received MRW\_ACK SUFI is set equal to "0000"; +- a STATUS PDU/piggybacked STATUS PDU containing an MRW\_ACK SUFI is received, and the SN\_ACK field in the received MRW\_ACK SUFI = the SN\_MRWLENGTH field in the transmitted MRW\_SUFI, and the N field in the received MRW\_ACK SUFI is set equal to the NLENGTH field in the transmitted MRW\_SUFI; +- a STATUS PDU/piggybacked STATUS PDU containing an ACK SUFI is received, and this STATUS PDU/piggybacked STATUS PDU indicates that all AMD PDUs up to and including the AMD PDU with "Sequence Number" equal to (SN\_MRWLENGTH field in the transmitted MRW\_SUFI) – 1 has been received or discarded by the peer entity. + +Upon termination of the SDU discard with explicit signalling procedure, the Sender shall: + +- stop the timer Timer\_MRW; +- update VT(A) and VT(MS) according to the received STATUS PDU/piggybacked STATUS PDU; + +The Sender shall not confirm to upper layers the SDUs that are requested to be discarded. + +### 11.6.4a Reached maximum number of attempts + +If VT(MRW) = MaxMRW, the Sender shall: + +- terminate the SDU discard with explicit signalling procedure; +- stop the timer Timer\_MRW if it was started; +- initiate the RLC RESET procedure (see subclause 11.4). + +### 11.6.5 Expiration of timer Timer\_MRW + +If Timer\_MRW expires before the discard procedure is terminated, the Sender shall: + +- increment VT(MRW) by one; +- if VT(MRW) < MaxMRW: + - set the MRW\_SUFI as previously transmitted (even if additional SDUs were discarded in the mean-time); + - include the MRW\_SUFI in a new status report (if other SUFIs are included, their contents shall be updated); + - transmit the status report by either including it in a STATUS PDU or piggybacked in an AMD PDU; + - restart Timer\_MRW for this discard procedure according to the description in subclause 9.5. +- else (if VT(MRW) = MaxMRW): + - perform the actions specified in subclause 11.6.4a. + +### 11.6.6 Abnormal cases + +#### 11.6.6.1 Reception of obsolete/corrupted MRW SUFI by the Receiver + +If the received MRW SUFI contains outdated information about the reception window (reception window already moved further than MRW SUFI is indicating), the Receiver shall: + +- discard the MRW SUFI; +- set the SN\_ACK field in the MRW\_ACK SUFI to the current value of VR(R); +- set the N field in the MRW\_ACK SUFI to "0000"; +- include the MRW\_ACK SUFI in the next STATUS PDU/piggybacked STATUS PDU to be transmitted, according to subclause 11.5.2. + +#### 11.6.6.2 Void + +#### 11.6.6.3 Reception of obsolete/corrupted MRW\_ACK SUFI by the Sender + +The Sender shall discard the received MRW\_ACK SUFI if one of the following cases occurs: + +- no ongoing SDU discard with explicit signalling procedure; or +- the SN\_ACK field in the received MRW\_ACK SUFI < the SN\_MRWLENGTH field in the transmitted MRW SUFI; or +- the SN\_ACK field in the received MRW\_ACK SUFI = the SN\_MRWLENGTH field in the transmitted MRW SUFI, and the N field in the received MRW\_ACK SUFI is not equal to the NLENGTH field in the transmitted MRW SUFI; or +- the SN\_ACK field in the received MRW\_ACK SUFI > the SN\_MRWLENGTH field in the transmitted MRW SUFI, and the N field in the received MRW\_ACK SUFI is not equal to "0000". + +## 11.7 Void + +## 11.8 Void + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|-----|-----|-----|----------------------------------------------------------------------------|-------------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New version | +| 10/1999 | RP-05 | RP-99465 | - | | | Approved at TSG-RAN #5 and placed under Change Control | 3.0.0 | +| 12/1999 | RP-06 | RP-99641 | 001 | | | RLC: Editorial corrections | 3.1.0 | +| | RP-06 | RP-99641 | 002 | 1 | | Editorial changes on RLC protocol specification | 3.1.0 | +| | RP-06 | RP-99643 | 003 | 1 | | MRW procedure | 3.1.0 | +| | RP-06 | RP-99643 | 004 | | | SDU Discard Functionality | 3.1.0 | +| | RP-06 | RP-99643 | 005 | 2 | | Change in RLC control PDU format | 3.1.0 | +| | RP-06 | RP-99642 | 006 | 1 | | Editorial corrections regarding CTCH | 3.1.0 | +| | RP-06 | RP-99641 | 007 | | | Updated RLC SDL | 3.1.0 | +| | RP-06 | RP-99642 | 011 | | | RLC Editorial Changes | 3.1.0 | +| | RP-06 | RP-99642 | 013 | | | Editorial Modification on RLC specification | 3.1.0 | +| | RP-06 | RP-99641 | 014 | | | Editorial changes | 3.1.0 | +| | RP-06 | RP-99642 | 015 | | | Change to one PU in a AMD PDU | 3.1.0 | +| | RP-06 | RP-99643 | 016 | 1 | | Introduction of RLC suspend state | 3.1.0 | +| | RP-06 | RP-99641 | 017 | 1 | | RLC editorial corrections | 3.1.0 | +| 01/2000 | - | - | - | | | Editorial corrections in title and Annex A (SDL) | 3.1.1 | +| | - | - | - | | | Correction of persistent error regarding SDL in Table of Contents | 3.1.2 | +| 03/2000 | RP-07 | RP-000040 | 018 | 1 | | RLC editorial changes | 3.2.0 | +| | RP-07 | RP-000040 | 021 | 1 | | Corrections to RLC | 3.2.0 | +| | RP-07 | RP-000040 | 025 | 2 | | Corrections to RLC | 3.2.0 | +| | RP-07 | RP-000040 | 026 | 1 | | STATUS PDUs | 3.2.0 | +| | RP-07 | RP-000040 | 027 | 1 | | Clarification of RLC AMD Model | 3.2.0 | +| | RP-07 | RP-000040 | 028 | | | Corrections to Timer_discard procedures | 3.2.0 | +| | RP-07 | RP-000040 | 029 | 1 | | Segmentation of RLC SDUs | 3.2.0 | +| | RP-07 | RP-000040 | 030 | 2 | | Modification of SDU discard to support virtual PDCP sequence numbers | 3.2.0 | +| | RP-07 | RP-000040 | 031 | | | Removal of SCCH | 3.2.0 | +| | RP-07 | RP-000040 | 032 | | | Updated RLC SDL | 3.2.0 | +| | RP-07 | RP-000040 | 033 | 1 | | RLC Editorial Changes | 3.2.0 | +| | RP-07 | RP-000040 | 034 | | | Order of bit transmission for RLC PDUs | 3.2.0 | +| 06/2000 | RP-08 | RP-000220 | 038 | | | Corrections to RLC | 3.3.0 | +| | RP-08 | RP-000220 | 039 | | | Correction to the description of the MRW SUFI fields | 3.3.0 | +| | RP-08 | RP-000220 | 040 | 1 | | Editorial corrections to length indicators and local suspend rate | 3.3.0 | +| | RP-08 | RP-000220 | 041 | 4 | | Clarification of the RESET PDU | 3.3.0 | +| | RP-08 | RP-000220 | 043 | 1 | | Clarification of RLC/MAC interaction | 3.3.0 | +| | RP-08 | RP-000220 | 044 | 2 | | General RLC corrections | 3.3.0 | +| | RP-08 | RP-000220 | 045 | | | Clarification of RLC Transparent Mode operation | 3.3.0 | +| | RP-08 | RP-000220 | 048 | | | Editorial corrections to abbreviations, SCCH, BCCH | 3.3.0 | +| | RP-08 | RP-000220 | 052 | | | Updated RLC SDL | 3.3.0 | +| | RP-08 | RP-000220 | 053 | | | Correction to RLC | 3.3.0 | +| | RP-08 | RP-000220 | 055 | | | RLC Logical Channel mapping | 3.3.0 | +| | RP-08 | RP-000220 | 057 | | | Correction of EPC timer mechanism | 3.3.0 | +| 09/2000 | RP-09 | RP-000358 | 059 | 1 | | State variables after window change | 3.4.0 | +| | RP-09 | RP-000358 | 060 | 4 | | SDU discard | 3.4.0 | +| | RP-09 | RP-000358 | 061 | 5 | | General RLC corrections | 3.4.0 | +| | RP-09 | RP-000358 | 066 | | | Editorial changes to RLC | 3.4.0 | +| | RP-09 | RP-000358 | 067 | 4 | | Correction to RLC window size range | 3.4.0 | +| | RP-09 | RP-000358 | 068 | 2 | | Window based polling | 3.4.0 | +| | RP-09 | RP-000358 | 070 | 2 | | General corrections to RLC | 3.4.0 | +| | RP-09 | RP-000358 | 071 | | | State Transition in RLC Acknowledged Mode | 3.4.0 | +| | RP-09 | RP-000358 | 073 | | | Clarification of the Length Indicators | 3.4.0 | +| | RP-09 | RP-000358 | 076 | 1 | | RLC corrections | 3.4.0 | +| | RP-09 | RP-000358 | 077 | 1 | | Corrections to reset procedure and length indicator definitions | 3.4.0 | +| | RP-09 | RP-000358 | 078 | | | RLC Modes for SHCCH | 3.4.0 | +| | RP-09 | RP-000358 | 079 | | | CCCH in UM RLC | 3.4.0 | +| 12/2000 | RP-10 | RP-000568 | 080 | 1 | | Length Indicator and PDU formats | 3.5.0 | +| | RP-10 | RP-000568 | 083 | 3 | | Clarification to the Estimated PDU Counter | 3.5.0 | +| | RP-10 | RP-000568 | 084 | 2 | | Model of UM and AM entities | 3.5.0 | +| | RP-10 | RP-000568 | 085 | 1 | | General RLC corrections | 3.5.0 | +| | RP-10 | RP-000568 | 086 | 1 | | General RLC corrections | 3.5.0 | +| | RP-10 | RP-000568 | 087 | 5 | | RLC timers | 3.5.0 | +| | RP-10 | RP-000568 | 088 | 1 | | Reset procedure | 3.5.0 | +| | RP-10 | RP-000568 | 089 | 1 | | Editorial corrections to RLC | 3.5.0 | +| | RP-10 | RP-000568 | 090 | 2 | | RLC UM protocol | 3.5.0 | +| | RP-10 | RP-000568 | 092 | 2 | | Clarification to window size parameters, MRW SUFI and window based polling | 3.5.0 | + +| Change history | | | | | | | | +|----------------|-------|-----------|-----|-----|-----|---------------------------------------------------------------------------------------------------------------------|-------------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New version | +| | RP-10 | RP-000568 | 093 | 3 | | General RLC Corrections | 3.5.0 | +| | RP-10 | RP-000568 | 094 | 1 | | RLC Reset handling | 3.5.0 | +| | RP-10 | RP-000568 | 095 | | | Inclusion of stage 3 for ciphering | 3.5.0 | +| 03/2001 | RP-11 | RP-010026 | 097 | 1 | | Clarification on LIST SUFI and RLIST SUFI | 3.6.0 | +| | RP-11 | RP-010026 | 098 | 1 | | Corrections and clarifications for SDU discard without explicit signalling | 3.6.0 | +| | RP-11 | RP-010026 | 099 | 1 | | Tr mode operation | 3.6.0 | +| | RP-11 | RP-010026 | 100 | 1 | | Timer based discard with explicit signalling | 3.6.0 | +| | RP-11 | RP-010026 | 101 | | | Annex updates | 3.6.0 | +| | RP-11 | RP-010026 | 103 | | | Clarification on MRW SUFI and SDU discard procedure | 3.6.0 | +| | RP-11 | RP-010026 | 104 | 1 | | General clarification on SN arithmetic comparison | 3.6.0 | +| | RP-11 | RP-010026 | 105 | 2 | | General clarification on RLC header and PDU header | 3.6.0 | +| | RP-11 | RP-010026 | 106 | 1 | | Clarification on the primitives between RLC and higher layers | 3.6.0 | +| | RP-11 | RP-010026 | 107 | 1 | | Clarification on the model of AM entity | 3.6.0 | +| | RP-11 | RP-010026 | 109 | 2 | | Clarification on UMD transfer procedure | 3.6.0 | +| | RP-11 | RP-010026 | 110 | 1 | | RLC status transmission in CELL_PCH and URA_PCH | 3.6.0 | +| | RP-11 | RP-010026 | 111 | | | Re-establishment description | 3.6.0 | +| | RP-11 | RP-010026 | 112 | 1 | | Clarifications on the RESET and RESET ACK PDU sizes | 3.6.0 | +| | RP-11 | RP-010026 | 113 | 1 | | Editorial corrections and clarifications | 3.6.0 | +| | RP-11 | RP-010026 | 114 | 1 | | Clarifications on the RLC-AM-DATA-Conf primitive | 3.6.0 | +| | RP-11 | RP-010026 | 116 | | | Removal of the payload unit concept | 3.6.0 | +| | RP-11 | RP-010026 | 118 | 2 | | Padding Blocks and TFC selection pre-empting | 3.6.0 | +| | RP-11 | - | - | | | Upgrade to Release 4 - no technical change | 4.0.0 | +| 06/2001 | RP-12 | RP-010309 | 120 | | | Clarification on ACK SUFI | 4.1.0 | +| | RP-12 | RP-010309 | 122 | | | MRW SUFI clarification and enhancement | 4.1.0 | +| | RP-12 | RP-010309 | 124 | | | Clarification on AM states | 4.1.0 | +| | RP-12 | RP-010309 | 126 | | | Clarification on HFN update in RESET procedure | 4.1.0 | +| | RP-12 | RP-010309 | 128 | | | Clarification of RLC Discard | 4.1.0 | +| | RP-12 | RP-010309 | 130 | | | Removal of reference to RRC | 4.1.0 | +| | RP-12 | RP-010309 | 132 | | | Clarification in the LI Parameters section | 4.1.0 | +| | RP-12 | RP-010309 | 136 | | | Cleanup of RLC services and functions | 4.1.0 | +| | RP-12 | RP-010309 | 138 | | | Clarification on RLC re-establishment | 4.1.0 | +| | RP-12 | RP-010309 | 140 | | | Corrections and clarifications to the LIST and RLIST SUFI types | 4.1.0 | +| 09/2001 | RP-13 | RP-010542 | 142 | | | General clarifications | 4.2.0 | +| | RP-13 | RP-010542 | 150 | | | Correction to RLC state variables | 4.2.0 | +| 12/2001 | RP-14 | RP-010761 | 152 | | | General clarifications | 4.3.0 | +| | RP-14 | RP-010761 | 156 | | | Send state variable for Timer_Poll and window based polling | 4.3.0 | +| | RP-14 | RP-010761 | 158 | | | Unexpected data interruption during transmission scheduling | 4.3.0 | +| | RP-14 | RP-010761 | 162 | | | UE-ID Type Indicator | 4.3.0 | +| | RP-14 | RP-010761 | 164 | | | Removal of obsolete Send MRW option | 4.3.0 | +| | RP-14 | RP-010771 | 160 | | | Content of retransmitted RESET ACK PDU | 4.3.0 | +| | RP-14 | RP-010771 | 166 | | | Usage of UM RLC Special Length Indicator | 4.3.0 | +| | RP-14 | RP-010771 | 170 | | | Indication of SDU transmission result | 4.3.0 | +| 03/2002 | RP-15 | RP-020068 | 172 | | | Clarification on MRW SUFI and SDU discard with explicit signalling procedure | 4.4.0 | +| | RP-15 | RP-020068 | 176 | | | SDU discard termination | 4.4.0 | +| | RP-15 | RP-020068 | 180 | | | Initial value of VT(US) | 4.4.0 | +| | RP-15 | - | - | | | Upgrade to Release 5 - no technical change | 5.0.0 | +| 06/2002 | RP-16 | RP-020327 | 186 | | | Handling abnormal UMD PDUs and AMD PDUs | 5.1.0 | +| | RP-16 | RP-020327 | 189 | | | Clarification of the use of Length Indicators | 5.1.0 | +| | RP-16 | RP-020327 | 192 | 1 | | Correction to MaxDAT, MaxRST and MaxMRW | 5.1.0 | +| | RP-16 | RP-020327 | 195 | | | Clarification on polling functions | 5.1.0 | +| 09/2002 | RP-17 | RP-020539 | 198 | | | Correction to the behaviour after expiration of Timer_MRW during the SDU discard with explicit signalling procedure | 5.2.0 | +| | RP-17 | RP-020539 | 201 | | | Corrections to RLC retransmissions | 5.2.0 | +| | RP-17 | RP-020637 | 204 | 1 | | Corrections to RLC RESET procedure and Length Indicators | 5.2.0 | +| | RP-17 | RP-020539 | 207 | | | Corrections on handling of timers during a RLC reset or re-establishment | 5.2.0 | +| | RP-17 | RP-020551 | 209 | | | Corrections on indication of SDU transmission result | 5.2.0 | +| 12/2002 | RP-18 | RP-020719 | 212 | | | RB id in ciphering | 5.3.0 | +| | RP-18 | RP-020862 | 213 | | | Generation of RLC Status Reports to coordinate with MAC-hs reset | 5.3.0 | +| 03/2003 | RP-19 | RP-030101 | 216 | | | Correction to VT(MRW) definition | 5.4.0 | +| | RP-19 | RP-030116 | 217 | | | Enhancement of MRW procedure | 5.4.0 | +| 06/2003 | RP-20 | RP-030292 | 220 | 2 | | Handling of erroneous PDUs | 5.5.0 | +| | RP-20 | RP-030292 | 225 | | | Setting of the "Polling bit" in the "Every Poll SDU SDU" function | 5.5.0 | +| | RP-20 | RP-030297 | 222 | | | Receiver behaviour when detecting an AMD PDU duplicate | 5.5.0 | +| | RP-20 | RP-030297 | 227 | | | RLC window size reconfigurations | 5.5.0 | +| 09/2003 | RP-21 | RP-030483 | 230 | | | SDU Concatenation Exceptions and SDU Concatenation in AM Mode | 5.6.0 | +| | RP-21 | RP-030483 | 233 | 1 | | Decision of Discarded SDUs from Discarded PDUs | 5.6.0 | +| | RP-21 | RP-030483 | 236 | 1 | | RLC Reset Triggering and Update of VT(RST) | 5.6.0 | +| | RP-21 | RP-030483 | 239 | | | correction to the 'SDU discard with explicit signalling' procedure | 5.6.0 | +| | RP-21 | RP-030478 | 242 | | | Elimination of EPC mechanism | 5.6.0 | + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-----|-----|-----------------------------------------------------------------------------------------------------------|-------------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New version | +| | RP-21 | RP-030483 | 245 | | | Correction of MRW and RESET timers in RLC | 5.6.0 | +| | RP-21 | RP-030490 | 247 | | | Reconfiguration of RLC window size | 5.6.0 | +| 12-2003 | RP-22 | RP-030616 | 250 | | | BITMAP and status report content | 5.7.0 | +| | RP-22 | RP-030620 | 252 | | | Indication of discarded SDU in RLC Reset and Re-establishment | 5.7.0 | +| | RP-22 | - | - | | | Upgrade to Release 6 - no technical change | 6.0.0 | +| 06-2004 | RP-24 | RP-040224 | 258 | | | DL RLC Size handling | 6.1.0 | +| 12-2004 | RP-26 | RP-040504 | 262 | 1 | | Correction of MRW SUFI content setting rule | 6.2.0 | +| | RP-26 | RP-040504 | 264 | 1 | | Correction of Poll Prohibit function | 6.2.0 | +| | RP-26 | RP-040490 | 265 | 1 | | Inclusion of out of sequence SDU delivery | 6.2.0 | +| | RP-26 | RP-040490 | 266 | | | Addition of MBMS Logical Channels and UM functionality for 'duplicate avoidance and reordering' | 6.2.0 | +| 03-2005 | RP-27 | RP-050113 | 260 | 1 | | Correction of MRW termination on reception of ACK SUFI | 6.3.0 | +| | RP-27 | RP-050113 | 265 | | | Correction to RLC Re-establishment | 6.3.0 | +| | RP-27 | RP-050113 | 267 | | | CRCLC-Config-Req in LOCAL_SUSPEND State | 6.3.0 | +| | RP-27 | RP-050113 | 268 | | | Protocol error detection and recovery | 6.3.0 | +| | RP-27 | RP-050068 | 270 | | | Removal of the EPC mechanism | 6.3.0 | +| | RP-27 | RP-050082 | 271 | | | Inclusion of transmitter constraints | 6.3.0 | +| 06-2005 | RP-28 | RP-050319 | 0272 | | | Correction on actions taken Upon reception of a duplicated AMD PDU within the reception window | 6.4.0 | +| | RP-28 | RP-050315 | 0273 | | | Clarification on a Transmitter Constraint | 6.4.0 | +| | RP-28 | RP-050319 | 0274 | | | Reconfiguration of RLC parameters by upper layers may lead to Logic inconsistency of state variable VrH | 6.4.0 | +| | RP-28 | RP-050302 | 0276 | | | Erroneous Sequence Number definition | 6.4.0 | +| | RP-28 | RP-050319 | 0277 | | | Selecting a PDU to transmit a poll | 6.4.0 | +| | RP-28 | RP-050319 | 0278 | | | Support for out-of-sequence PDUs in RLC-UM | 6.4.0 | +| | RP-28 | RP-050315 | 0279 | 1 | | Clarification of the "Out of sequence SDU delivery" | 6.4.0 | +| | RP-28 | RP-050317 | 0280 | | | RLC LI Optimization for VoIP | 6.4.0 | +| | RP-28 | RP-050315 | 0281 | | | Correction to Out Of Sequence Delivery | 6.4.0 | +| | RP-28 | RP-050315 | 0282 | | | Clarification on operations when UE MCCH RLC entity is re-established and OSD_Window_Size is reconfigured | 6.4.0 | +| 09-2005 | RP-29 | RP-050463 | 0284 | | | Single Sided RLC Re-establishment | 6.5.0 | +| | RP-29 | RP-050481 | 0285 | | | Removal RLC-SDU alignment capability | 6.5.0 | +| | RP-29 | RP-050468 | 0286 | | | Arithmetic comparison for DAR function and VR(US) after MBMS being included | 6.5.0 | +| | RP-29 | RP-050468 | 0287 | | | Clarification on DAR window reconfiguration | 6.5.0 | +| | RP-29 | RP-050468 | 0288 | | | Clarification on reception of UMD PDU when OSD function is configured | 6.5.0 | +| 12-2005 | RP-30 | RP-050784 | 0290 | | | Correction on transmission of AMD PDU | 6.6.0 | +| | RP-30 | RP-050788 | 0293 | | | Initiation of state variable VR(UOH) | 6.6.0 | +| | RP-30 | RP-050788 | 0294 | | | Clarification on reception of UMD PDU when OSD function is configured | 6.6.0 | +| | RP-30 | RP-050797 | 0296 | | | Corrections to RLC re-establishment | 6.6.0 | +| | RP-30 | RP-050802 | 0297 | 1 | | RLC UMD header optimisation for RT services over HSDPA/HSUPA | 6.6.0 | +| 03-2006 | RP-31 | RP-060090 | 0292 | 2 | | Correction to RLC Re-establishment Procedure | 6.7.0 | +| | RP-31 | RP-060090 | 0298 | | | Correction to RLC reset procedure | 6.7.0 | +| | RP-31 | RP-060094 | 0299 | | | Introducing missing "and" to the RLC UMD operation with LI optimisation | 6.7.0 | +| | RP-31 | - | - | | | Upgrade to the Release 7 - no technical change | 7.0.0 | +| 06/2006 | RP-32 | RP-060363 | 0301 | 1 | | Clarification on abortion of RLC Reset procedure | 7.1.0 | +| | RP-32 | RP-060363 | 0303 | | | RLC SDU Discard during re-establishment | 7.1.0 | +| 09/2006 | RP-33 | RP-060575 | 0305 | | | AMD PDU discard | 7.2.0 | +| 06/2007 | RP-36 | | | | | Removing an incomplete optimization for RLC operations during HSDPA cell change | 7.3.0 | +| | RP-36 | RP-070407 | 0306 | 1 | | Correction to Out of Sequence Reception function | 7.3.0 | +| | RP-36 | RP-070407 | 0307 | - | | DAR over CCCH | 7.3.0 | +| | RP-36 | RP-070407 | 0308 | - | | Introduction of Improved L2 support for high data rates | 7.3.0 | +| | RP-36 | RP-070404 | 0309 | 2 | | Corrections on modulus base in UM in RLC | 7.3.0 | +| | RP-36 | RP-070416 | 0311 | - | | Using special value of HE field to indicate end of an SDU for RLC AM | 7.3.0 | +| | RP-36 | RP-070407 | 0312 | - | | | 7.3.0 | +| 09/2007 | RP-37 | RP-070626 | 0313 | | | Correction on POLL SUFI | 7.4.0 | +| | RP-37 | RP-070626 | 0314 | | | Special HE value setting | 7.4.0 | +| 12/2007 | RP-38 | RP-070905 | 0315 | | | Correction to Control Information transmission with two logical channels | 7.5.0 | +| | RP-38 | RP-070910 | 0316 | | | Introduction of CS Voice over HSPA | 8.0.0 | +| 03/2008 | RP-39 | RP-080178 | 0319 | - | | Correction to Reception of UM RLC | 8.1.0 | +| | RP-39 | RP-080191 | 0321 | - | | Correction to Control Information transmission | 8.1.0 | +| | RP-39 | RP-080191 | 0323 | - | | Poll SUFI and Status Reporting | 8.1.0 | +| | RP-39 | RP-080202 | 0324 | - | | Introducing flexible RLC PDU size in the uplink | 8.1.0 | +| | RP-39 | RP-080190 | 0326 | - | | Correction to the RLC RESET and RESET ACK PDU with flexible RLC PDU size | 8.1.0 | +| 06/2008 | RP-40 | RP-080403 | 0328 | 1 | | Correction on UM model depiction | 8.2.0 | +| | RP-40 | RP-080391 | 0330 | 1 | | Clarification on DAR Operation | 8.2.0 | +| | RP-40 | RP-080405 | 0331 | - | | CS-HSPA UL Segmentation | 8.2.0 | +| | RP-40 | RP-080395 | 0333 | 3 | | Removal of UTRAN behaviour | 8.2.0 | +| | RP-40 | RP-080414 | 0334 | - | | Correction to transmitting AM RLC entity | 8.2.0 | + +| Change history | | | | | | | | +|----------------|--------|-----------|------|-----|-----|---------------------------------------------------------------------------------------|-------------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New version | +| | RP-40 | RP-080414 | 0335 | 1 | | Removal of Redundant Description in Transmitting Side | 8.2.0 | +| | RP-40 | RP-080390 | 0338 | - | | Non-applicability of ciphering for MCCH, MSCH and MTCH | 8.2.0 | +| | RP-40 | RP-080395 | 0343 | - | | Maximum RLC PDU size | 8.2.0 | +| | RP-40 | RP-080414 | 0344 | 1 | | RLC PDU size adaptation | 8.2.0 | +| 09/2008 | RP-41 | RP-080685 | 0349 | - | | Correction to definition of N_LENGTH | 8.3.0 | +| 03/2009 | RP-43 | RP-090117 | 0353 | - | | Correction for VR(UM) | 8.4.0 | +| | RP-43 | RP-090140 | 0354 | - | | Concatenation/segmentation in case SN_Delivery parameter is configured | 8.4.0 | +| | RP-43 | RP-090138 | 0356 | 1 | | Clarification for the description of transmitting UM RLC entity | 8.4.0 | +| | RP-43 | RP-090138 | 0357 | - | | Correction to RLC text for MAC i/s | 8.4.0 | +| | RP-43 | RP-090151 | 0358 | - | | Removal of DCCH logical channel mapped on RLC TM entity | 8.4.0 | +| 06/2009 | RP-44 | RP-090519 | 0359 | - | | Submission of UMD PDU when SN_Delivery is configured | 8.5.0 | +| | RP-44 | RP-090505 | 0364 | - | | Removal of references to MAC-hs reset | 8.5.0 | +| 09/2009 | RP-45 | RP-090917 | 0366 | - | | Clarification on minimum PDU size | 8.6.0 | +| | RP-45 | RP-090909 | 0368 | - | | Clarification to LI setting after Timer_Discard expiry when alternative e-bit is used | 8.6.0 | +| 12/2009 | RP-46 | RP-091329 | 0369 | - | | Introduction of POLL_SUFi in UL data transfer | 8.7.0 | +| | RP-46 | RP-091336 | 0373 | - | | Partial radio awareness for DC-HSUPA capable UEs | 9.0.0 | +| 03/2010 | RP-47 | RP-100286 | 0375 | - | | RLC recovery with uplink POLL_SUFi(R9) | 9.1.0 | +| 06/2010 | RP-48 | RP-100537 | 0379 | 2 | | Correction of Poll_SUFi handling for Improved L2 Uplink | 9.2.0 | +| 12/2010 | RP-50 | RP-101365 | 0388 | - | | Introduction of LCR TDD MC-HSUPA in 25.322 | 10.0.0 | +| 06/2011 | RP-52 | RP-110771 | 0391 | 2 | | Accept RLC PDUs with special value HE field if it's supported | 10.1.0 | +| 09/2012 | RP-57 | RP-121369 | 0403 | - | | Introduction of Multiflow in TS 25.322 | 11.0.0 | +| 12/2012 | RP-58 | RP-121943 | 0404 | - | | Introduction of further Multiflow agreements in TS 25.322 | 11.1.0 | +| 03/2013 | RP-59 | RP-130239 | 0405 | - | | Clarification on RLC Status Report prohibit functions | 11.2.0 | +| 09/2014 | RP-65 | - | - | - | - | Upgrade to the Release 12 - no technical change | 12.0.0 | +| 12/2015 | RP-70 | - | - | - | - | Upgrade to the Release 13 - no technical change | 13.0.0 | +| 03/2017 | RP-75 | - | - | - | - | Upgrade to Release 14 - no technical change | 14.0.0 | +| 06/2018 | RP-80 | - | - | - | - | Upgrade to Release 15 - no technical change | 15.0.0 | +| 2020-07 | RP-88e | - | - | - | - | Upgrade to Rel-16 version without technical change | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25323/051638d871c75230edb3d005fa668810_img.jpg b/marked/Rel-16/25_series/25323/051638d871c75230edb3d005fa668810_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..934489c0690b665b643cc60b019909b2782e725c --- /dev/null +++ b/marked/Rel-16/25_series/25323/051638d871c75230edb3d005fa668810_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9319d1dd8a8ef4cc87f5d19f56d56f7568ec72e56d34b975f99f75520a19543 +size 24527 diff --git a/marked/Rel-16/25_series/25323/088921fa3f5a44c8551815122517eefd_img.jpg b/marked/Rel-16/25_series/25323/088921fa3f5a44c8551815122517eefd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80ca0bdf7fc2bcc38b2b62e1d876321e2ca5468f --- /dev/null +++ b/marked/Rel-16/25_series/25323/088921fa3f5a44c8551815122517eefd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8683ec3a2a87edf45b1eb99f7f30cb6f3a5446051087434025f1339564ec739 +size 18826 diff --git a/marked/Rel-16/25_series/25323/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/marked/Rel-16/25_series/25323/1b5a812c8aa20fd5cba28e97001d32de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5da228ea90a98208320dca65b91b4cb834686c3 --- /dev/null +++ b/marked/Rel-16/25_series/25323/1b5a812c8aa20fd5cba28e97001d32de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ceefdba7c7e924d8ea79e8ec6a3346fdd1e10a60efcba1009fedc8ad41ffbc8 +size 53348 diff --git a/marked/Rel-16/25_series/25323/2ba086df3506f81bae3a9b53725dcfea_img.jpg b/marked/Rel-16/25_series/25323/2ba086df3506f81bae3a9b53725dcfea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d0f052db2250f00307941c25cf65000c2b423a4 --- /dev/null +++ b/marked/Rel-16/25_series/25323/2ba086df3506f81bae3a9b53725dcfea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:640a7ab3bd5756865a136d30df6f21b36b68dfbecca1839e45e8322a6a6a6346 +size 71210 diff --git a/marked/Rel-16/25_series/25323/382a9c9e4816bd229191ab4591424dd8_img.jpg b/marked/Rel-16/25_series/25323/382a9c9e4816bd229191ab4591424dd8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d6450d985142e406430ceb07f751a3cdb448d49 --- /dev/null +++ b/marked/Rel-16/25_series/25323/382a9c9e4816bd229191ab4591424dd8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9052801b06103dffd52e57139d3a92cd03cd0d3c2799af9e0a8eb139a70e4260 +size 101605 diff --git a/marked/Rel-16/25_series/25323/41eb258722adc992426b1ae707f4a2cb_img.jpg b/marked/Rel-16/25_series/25323/41eb258722adc992426b1ae707f4a2cb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0e64de27369a28f09c8f2bf86892ab3b995fcfb --- /dev/null +++ b/marked/Rel-16/25_series/25323/41eb258722adc992426b1ae707f4a2cb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d8b37fa8ab6d4d4a1c86b1c7e6d3b1f19ea79c986e907b5f4de1e4ed2b46590 +size 25642 diff --git a/marked/Rel-16/25_series/25323/61126a1f3affdeea7b41bb68cba95138_img.jpg b/marked/Rel-16/25_series/25323/61126a1f3affdeea7b41bb68cba95138_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd81b18e03c041bed3a174871e691c784f5c1a54 --- /dev/null +++ b/marked/Rel-16/25_series/25323/61126a1f3affdeea7b41bb68cba95138_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7fe1d9d4d1b4a2625818e5fab8cd8f23819c4811760090ae77e8430a1285c45 +size 26238 diff --git a/marked/Rel-16/25_series/25323/704082cc3e11776bda29595c76411362_img.jpg b/marked/Rel-16/25_series/25323/704082cc3e11776bda29595c76411362_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d448016175943f512154501d7b21f7ed17c912b --- /dev/null +++ b/marked/Rel-16/25_series/25323/704082cc3e11776bda29595c76411362_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20f22f59e7a7ad1b795453ce798b6365e4c9e39086b06f23f93b7edd7d3b41ad +size 42361 diff --git a/marked/Rel-16/25_series/25323/744acfe8d4e31bcf03f95714c2f6e567_img.jpg b/marked/Rel-16/25_series/25323/744acfe8d4e31bcf03f95714c2f6e567_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec95331b74dd1afc6e45118d31c64dd849d1eacf --- /dev/null +++ b/marked/Rel-16/25_series/25323/744acfe8d4e31bcf03f95714c2f6e567_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75943ef1fea2cd5ccb8d977125cde3d8a793b8f4ab5fe754bcd096605db0cd36 +size 20885 diff --git a/marked/Rel-16/25_series/25323/853ef5420f0432e626e83987e3f38a0b_img.jpg b/marked/Rel-16/25_series/25323/853ef5420f0432e626e83987e3f38a0b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d3a1fc7c7476e59f37f334f09cd16c69286c7a0 --- /dev/null +++ b/marked/Rel-16/25_series/25323/853ef5420f0432e626e83987e3f38a0b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:880f525aa8a3a3a1e209ab9b5d5dafe5f174e0e54147e1040699c12003b48fc0 +size 26556 diff --git a/marked/Rel-16/25_series/25323/896e86ed12aff206d302c64f2e3091fa_img.jpg b/marked/Rel-16/25_series/25323/896e86ed12aff206d302c64f2e3091fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6ab929aaad57bdbafb4be8354216a64321094f2 --- /dev/null +++ b/marked/Rel-16/25_series/25323/896e86ed12aff206d302c64f2e3091fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1821b6e2c87f9e9b38b748f5ae2d482b748992c3d5486cafe6de8078acb7d03e +size 106692 diff --git a/marked/Rel-16/25_series/25323/8f38356601e137ac471fc4771b9c5a5c_img.jpg b/marked/Rel-16/25_series/25323/8f38356601e137ac471fc4771b9c5a5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93d02c4c56e2393bf3ca5ee8649f94b5a350f659 --- /dev/null +++ b/marked/Rel-16/25_series/25323/8f38356601e137ac471fc4771b9c5a5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f1590b18e754a754198bdf4d6048795959dc2632ac7a0d8d57b7d908a197fc5 +size 31961 diff --git a/marked/Rel-16/25_series/25323/bf30e154f82662d212f21fccdfa2980f_img.jpg b/marked/Rel-16/25_series/25323/bf30e154f82662d212f21fccdfa2980f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1840c091f538e3c2ad60564c6943b29856ec26ca --- /dev/null +++ b/marked/Rel-16/25_series/25323/bf30e154f82662d212f21fccdfa2980f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2173bb474b68b2d0132820a5cf24b2947e7d0345c9deb692924ad4851b4babae +size 22174 diff --git a/marked/Rel-16/25_series/25323/c53adc66eab40abd5f8b9107d950ad04_img.jpg b/marked/Rel-16/25_series/25323/c53adc66eab40abd5f8b9107d950ad04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1743005e881005b6a05f247d2edd530303a7a1fb --- /dev/null +++ b/marked/Rel-16/25_series/25323/c53adc66eab40abd5f8b9107d950ad04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6b50a224005de38789904b2d80c713d12f6fa9aba4563db0ec563cc596e1f7a +size 31909 diff --git a/marked/Rel-16/25_series/25323/f3c5e85b70f94b9c3c521f594d69539f_img.jpg b/marked/Rel-16/25_series/25323/f3c5e85b70f94b9c3c521f594d69539f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b80dab8d6c5d50c3e8576aa0f92b74bd0f464ac --- /dev/null +++ b/marked/Rel-16/25_series/25323/f3c5e85b70f94b9c3c521f594d69539f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:273fddb6e9a7c4066532b22a23c4a2f348f89156d49af11329be20c0ad8078de +size 19313 diff --git a/marked/Rel-16/25_series/25323/raw.md b/marked/Rel-16/25_series/25323/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4db870543d9bffce63794294a416bfc7455458c6 --- /dev/null +++ b/marked/Rel-16/25_series/25323/raw.md @@ -0,0 +1,1680 @@ + + + + + + +# Contents + +| | | +|-----------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions and Abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 8 | +| 4 General..... | 9 | +| 4.1 Objective ..... | 9 | +| 4.2 Overview on sublayer architecture..... | 9 | +| 5 Functions..... | 10 | +| 5.1 Header Compression ..... | 10 | +| 5.1.1 Mapping of PID values..... | 10 | +| 5.1.2 IP Header Compression (RFC 2507)..... | 11 | +| 5.1.2.1 Context identifiers..... | 11 | +| 5.1.2.2 Mapping of PID values for RFC 2507..... | 11 | +| 5.1.2.3 Management of Full Header transmission..... | 11 | +| 5.1.3 Robust Header Compression ..... | 11 | +| 5.1.3.1 Context identifiers..... | 12 | +| 5.1.3.2 Void ..... | 12 | +| 5.1.3.3 Mapping of PID values ..... | 12 | +| 5.1.3.4 Void ..... | 12 | +| 5.1.3.5 Protocol Parameters ..... | 12 | +| 5.1.3.6 Configuration by RRC..... | 13 | +| 5.2 Void..... | 13 | +| 5.3 Data Transfer..... | 13 | +| 5.3.1 Data transfer over acknowledged mode RLC..... | 14 | +| 5.3.2 Data transfer over unacknowledged and transparent mode RLC..... | 14 | +| 5.4 SRNS Relocation..... | 14 | +| 5.4.1 Lossless SRNS Relocation ..... | 15 | +| 5.4.1.1 Void ..... | 15 | +| 5.4.1.2 Void ..... | 15 | +| 5.4.1.3 Void ..... | 15 | +| 5.4.2 Context relocation ..... | 15 | +| 5.5 Lossless DL RLC PDU size change..... | 17 | +| 5.6 General procedures..... | 17 | +| 5.6.1.1 PDCP Sequence Numbering..... | 17 | +| 5.6.1.2 PDCP Sequence Number synchronization ..... | 18 | +| 5.6.1.3 Sequence Number and Data Forwarding..... | 19 | +| 5.6.1.4 CS Counter Handling..... | 19 | +| 5.7 Header Compression and Decompression for MBMS..... | 19 | +| 5.7.1 Cell change inside the same cell group ..... | 19 | +| 5.7.2 Cell change between cell groups ..... | 20 | +| 6 Services ..... | 20 | +| 6.1 Services provided to upper layers ..... | 20 | +| 6.2 Services expected from RLC layer..... | 20 | +| 7 Elements for layer-to-layer communication ..... | 20 | +| 7.1 Primitives between PDCP and upper layers..... | 20 | +| 8 Elements for peer-to-peer communication..... | 22 | +| 8.1 Protocol data units..... | 22 | +| 8.2 Formats..... | 22 | +| 8.2.1 PDCP-No-Header PDU ..... | 22 | +| 8.2.2 PDCP Data PDU..... | 22 | +| 8.2.3 PDCP SeqNum PDU ..... | 23 | +| 8.2.4 PDCP AMR Data PDU ..... | 23 | + +| | | | +|-----------------------------|----------------------------------------------------------------------|-----------| +| 8.3 | Parameters ..... | 23 | +| 8.3.1 | PDU Type..... | 23 | +| 8.3.2 | PID..... | 24 | +| 8.3.3 | Data..... | 24 | +| 8.3.4 | Sequence number..... | 24 | +| 8.3.5 | CS counter ..... | 24 | +| 9 | Handling of unknown, unforeseen and erroneous protocol data ..... | 24 | +| 9.1 | Invalid PDU type..... | 24 | +| 9.2 | Invalid PID value ..... | 25 | +| 9.3 | PDCP Unrecoverable Error Detection ..... | 25 | +| Annex A (normative): | ROHC performance testing..... | 26 | +| A.1 | Introduction ..... | 26 | +| A.1.1 | Purpose of the performance testing ..... | 26 | +| A.1.2 | Input sequence for uncompressed headers ..... | 26 | +| A.1.3 | Feedback format for the test cases..... | 27 | +| A.1.4 | Feedback generation for test cases (R-mode only)..... | 27 | +| A.1.5 | Calculation of compressed header size..... | 28 | +| A.2 | Test outline – RoHC RTP Profile 0x0001 ..... | 28 | +| A.2.1 | Test 1a - Base test of ROHC RTP O-mode compressor ..... | 28 | +| A.2.1.1 | Test purpose..... | 28 | +| A.2.1.2 | Sequence details..... | 28 | +| A.2.1.3 | Test requirement ..... | 29 | +| A.2.2 | Test 1b - Base test of ROHC RTP R-mode compressor ..... | 29 | +| A.2.2.1 | Test purpose..... | 29 | +| A.2.2.2 | Sequence details..... | 29 | +| A.2.2.3 | Test requirement ..... | 30 | +| A.2.3 | Void ..... | 31 | +| A.2.3.1 | Void ..... | 31 | +| A.2.3.2 | Void ..... | 31 | +| A.2.3.3 | Void ..... | 31 | +| A.2.4 | Void ..... | 31 | +| A.2.4.1 | Void ..... | 31 | +| A.2.4.2 | Void ..... | 31 | +| A.2.4.3 | Void ..... | 31 | +| A.2.5 | Test 3a - Re-establishment of TS function after DTX in O-mode ..... | 31 | +| A.2.5.1 | Test purpose..... | 31 | +| A.2.5.2 | Sequence details..... | 31 | +| A.2.5.3 | Test requirement ..... | 31 | +| A.2.6 | Test 3b - Re-establishment of TS function after DTX in R-mode ..... | 32 | +| A.2.6.1 | Test purpose..... | 32 | +| A.2.6.2 | Sequence details..... | 32 | +| A.2.6.3 | Test requirement ..... | 32 | +| A.2.7 | Test 4a - Compressor response to single lost packets in O-mode ..... | 33 | +| A.2.7.1 | Test purpose..... | 33 | +| A.2.7.2 | Sequence details..... | 33 | +| A.2.7.3 | Test requirement ..... | 33 | +| A.2.8 | Test 4b - Compressor response to single lost packets in R-mode ..... | 33 | +| A.2.8.1 | Test purpose..... | 33 | +| A.2.8.2 | Sequence details..... | 33 | +| A.2.8.3 | Test requirement ..... | 33 | +| A.2.9 | Void ..... | 34 | +| A.2.9.1 | Void ..... | 34 | +| A.2.9.2 | Void ..... | 34 | +| A.2.9.3 | Void ..... | 34 | +| A.2.10 | Void ..... | 34 | +| A.2.10.1 | Void ..... | 34 | +| A.2.10.2 | Void ..... | 34 | +| A.2.10.3 | Void ..... | 34 | +| A.2.11 | Test 6a - TS function during DTX with varying delta in O-mode ..... | 34 | +| A.2.11.1 | Test purpose..... | 34 | + +| | | | +|-------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------| +| A.2.11.2 | Sequence details.................................................................................................................................................. | 34 | +| A.2.11.3 | Test requirement ................................................................................................................................................. | 34 | +| A.2.12 | Test 6b - TS function during DTX with varying delta in R-mode ................................................................... | 35 | +| A.2.12.1 | Test purpose....................................................................................................................................................... | 35 | +| A.2.12.2 | Sequence details.................................................................................................................................................. | 35 | +| A.2.12.3 | Test requirement ................................................................................................................................................. | 35 | +| A.2.13 | Test 7a – SRNS relocation in O-mode ............................................................................................................. | 36 | +| A.2.13.1 | Test purpose....................................................................................................................................................... | 36 | +| A.2.13.2 | Sequence details.................................................................................................................................................. | 36 | +| A.2.13.3 | Test requirement ................................................................................................................................................. | 36 | +| A.3 | Test packet structures......................................................................................................................................... | 38 | +| Annex B (informative): | Reference model for generating ROHC performance requirements ....... | 41 | +| B.1 | Introduction ....................................................................................................................................................... | 41 | +| B.2 | For Voice over IP (VoIP) optimisation ............................................................................................................. | 41 | +| B.2.1 | ROHC parameters optimisations for VoIP ....................................................................................................... | 41 | +| B.2.2 | Parameter setting for ROHC reference model for VoIP.................................................................................... | 41 | +| B.2.3 | Setting the parameter value N in test cases for VoIP ....................................................................................... | 41 | +| Annex C (informative): | Change history................................................................................................................................... | 42 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd 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 the description of the Packet Data Convergence Protocol (PDCP). + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [2] 3GPP TS 25.331: "Radio Resource Control (RRC); protocol specification". +- [3] 3GPP TS 25.301: "Radio Interface Protocol Architecture". +- [4] 3GPP TS 25.303: "Interlayer Procedures in Connected Mode". +- [5] 3GPP TS 25.322: "RLC Protocol Specification". +- [6] IETF RFC 2507: "IP Header Compression". +- [7] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [8] IETF RFC 3095: "RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed". +- [9] IETF RFC 3096: "Requirements for robust IP/UDP/RTP header compression". +- [10] IETF RFC 4815: "ROBust Header Compression (ROHC): Corrections and Clarifications to RFC 3095". +- [11] 3GPP TS 26.101: "Mandatory speech codec speech processing functions; Adaptive Multi-Rate (AMR) speech codec frame structure". +- [12] 3GPP TS 26.201: "Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Frame structure". + +# --- 3 Definitions and Abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in [7] and the following apply. + +| | | +|----------------------------|-----------------------------------------------------------------------------------------------| +| N-context | Refers collectively to both N-context-C and N-context-D . | +| N-context* | Refers collectively to both N-context-C* and N-context-D* . | +| N-context-C | The compression context for downlink in SRNC at any given point of time. | +| N-context-C* | The frozen snapshot of the compression context for downlink taken by SRNC. | +| N-context-C-static* | The frozen snapshot of the static part of the compression context for downlink taken by SRNC. | +| N-context-D | The decompression context for uplink in SRNC at any given point of time. | +| N-context-D* | The frozen snapshot of the decompression context for uplink taken by SRNC. | +| N-context-D-static* | The frozen snapshot of the static part of the decompression context for uplink taken by SRNC. | + +| | | +|----------------------------|------------------------------------------------------------------------------------------------------| +| M-context | Refers collectively to both M-context-C and M-context-D . | +| M-context* | Refers collectively to both M-context-C* and M-context-D* . | +| M-context-C | The compression context for uplink in UE at any given point of time. | +| M-context-C* | The frozen snapshot of the compression context for uplink taken by UE. | +| M-context-C-static* | The frozen snapshot of the static part of the compression context for uplink taken by UE. | +| M-context-D | The decompression context for downlink in UE at any given point of time. | +| M-context-D* | The frozen snapshot of the decompression context for downlink taken by UE. | +| M-context-D-static* | The frozen snapshot of the static part of the decompression context for downlink taken by UE. | +| M-HC | Entity located in the mobile terminal that performs header compression for uplink (i.e. UE PDCP) | +| M-HCD | Refers collectively to both M-HC and M-HD . | +| M-HD | Entity located in the mobile terminal that performs header decompression for downlink (i.e. UE PDCP) | +| N-HC | Entity located in the network that performs header compression for downlink (i.e. RNC PDCP) | +| N-HCD | Refers collectively to N-HC and N-HD | +| N-HD | Entity located in the network that performs header decompression for uplink (i.e. RNC PDCP) | + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-------|--------------------------------------------| +| AMR | Adaptive Multi-Rate | +| AS | Access Stratum | +| CID | Context Identifier | +| C-SAP | Control Service Access Point | +| HC | Header Compression | +| IETF | Internet Engineering Task Force | +| IP | Internet Protocol | +| L2 | Layer 2 (data link layer) | +| L3 | Layer 3 (network layer) | +| MBMS | Multimedia Broadcast Multicast Service | +| M-HC | Mobile Header Compressor | +| M-HCD | Mobile Header Compressor/Decompressor | +| M-HD | Mobile Header Decompressor | +| NAS | Non Access Stratum | +| N-HC | Network Header Compressor | +| N-HCD | Network Header Compressor/Decompressor | +| N-HD | Network Header Decompressor | +| PDCP | Packet Data Convergence Protocol | +| PDU | Protocol Data Unit | +| PID | Packet Identifier | +| PPP | Point-to-Point Protocol | +| p-t-p | Point-to-Point | +| p-t-m | Point-to-Multipoint | +| RB | Radio Bearer | +| RFC | Request For Comments | +| RLC | Radio Link Control | +| RNC | Radio Network Controller | +| ROHC | RObust Header Compression | +| RTP | Real Time Protocol | +| SDU | Service Data Unit | +| TCP | Transmission Control Protocol | +| UDP | User Datagram Protocol | +| UE | User Equipment | +| UMTS | Universal Mobile Telecommunications System | +| UTRA | UMTS Terrestrial Radio Access | +| UTRAN | UMTS Terrestrial Radio Access Network | + +# 4 General + +## 4.1 Objective + +The present document describes the functionality of the PDCP. + +## 4.2 Overview on sublayer architecture + +Figure 1 shows the model of the PDCP within the radio interface protocol architecture. The radio interface protocol architecture is defined in [3]. + +Every PS domain RAB is associated with one RB, which in turn is associated with one PDCP entity. Each PDCP entity is associated with one or two (one for each direction) RLC entities depending on the RB characteristic (i.e. uni-directional or bi-directional) and RLC mode. The PDCP entities are located in the PDCP sublayer. + +Every PDCP entity uses zero, one or several different header compression protocols. Each individual PDCP entity uses at most one instance of each header compression protocol. Several PDCP entities may be defined for a UE with each using the same or a different set of header compression protocols. In this version of the specification, only two header compression protocols, RFC 2507 [6] and ROHC [8], [10], are supported. + +Every CS domain voice RAB is associated with one RB, which in turn is associated with one PDCP entity. Each PDCP entity is associated with two UM RLC entities as CS voice RBs are always bi-directional. The PDCP entities are located in the PDCP sublayer. The PDCP entity serving CS service does not use header compression. + +The PDCP sublayer is configured by upper layer [2] through the PDCP-C-SAP. + +![Figure 1: PDCP structure diagram showing the PDCP sublayer with multiple PDCP entities, their associated RLC entities, and the interfaces (SAPs) between them.](2ba086df3506f81bae3a9b53725dcfea_img.jpg) + +The diagram illustrates the PDCP structure within the radio interface protocol architecture. At the top, 'Radio Bearers' are shown as vertical lines. These bearers connect to 'PDCP-SAPs' (Service Access Points), represented by circles. Above the PDCP-SAPs, a 'PDCP-SDU' (Service Data Unit) is shown entering the system. The PDCP-SAPs are part of a 'C-SAP' (Control Service Access Point) interface. Below the PDCP-SAPs is the 'PDCP sublayer', which contains three 'PDCP entity' boxes. The first PDCP entity contains two 'HC Protocol' boxes (HC Protocol 1 and HC Protocol 2). The second PDCP entity contains an 'SDU numbering' box and two 'HC Protocol' boxes (HC Protocol 1 and HC Protocol 2). The third PDCP entity contains one 'HC Protocol' box (HC Protocol 1). Below the PDCP entities is the 'RLC' sublayer, which contains several 'RLC entity' boxes represented by ovals. The PDCP entities are connected to the RLC entities via 'SAPs': 'UM-SAP' (User Plane Service Access Point), 'AM-SAP' (Acknowledged Mode Service Access Point), and 'TM-SAP' (Transparent Mode Service Access Point). Arrows indicate the flow of data: from the PDCP entities down to the RLC entities, and from the RLC entities up to the PDCP entities. A 'RLC-SDU' (Service Data Unit) is shown entering the RLC sublayer from the right. The diagram also shows ellipses indicating additional bearers, PDCP entities, and RLC entities. + +Figure 1: PDCP structure diagram showing the PDCP sublayer with multiple PDCP entities, their associated RLC entities, and the interfaces (SAPs) between them. + +**Figure 1: PDCP structure** + +Figure 1 represents one possible structure for the PDCP sublayer and should not restrict implementation. A PDCP entity is mapped to either one AM RLC entity or one or two UM or TM RLC entities. When a PDCP entity is mapped to two UM or TM RLC entities each RLC entity is used for a different direction. + +# 5 Functions + +PDCP provides its services to the NAS at the UE or the relay at the Radio Network Controller (RNC). + +The Packet Data Convergence Protocol shall perform the following functions: + +- header compression and decompression of IP data streams (e.g., TCP/IP and RTP/UDP/IP headers for IPv4 and IPv6) at the transmitting and receiving entity, respectively. +- transfer of user data. This function is used for conveyance of data between users of PDCP services. +- maintenance of PDCP sequence numbers for radio bearers that are configured to support lossless SRNS Relocation or lossless DL RLC PDU size change. +- transfer of CS counter if the radio bearer is connected to a CS domain radio access bearer. +- add and remove the padding in PDCP PDU for octet alignment. + +PDCP uses the services provided by the Radio Link Control (RLC) sublayer. + +## 5.1 Header Compression + +The header compression protocol is specific to the particular network layer, transport layer or upper layer protocol combinations e.g. TCP/IP and RTP/UDP/IP. The network layer protocol type, e.g. IP or PPP, is indicated during PDP context activation as defined in [1]. The header compression protocols and their parameters are configured by upper layers for each PDCP entity. Compressor and decompressor initiated signalling between peer PDCP entities, during operation, is accomplished through in-band signalling. + +### 5.1.1 Mapping of PID values + +Depending on the configuration by upper layers (i.e. PDCP PDU type to be used and header compressor protocol), the PDCP sublayer shall be able to: + +- identify different types of header compression protocols; +- if RFC2507: + - distinguish different header compression protocol packet types within a header compression protocol. + +The above requirements are realised by utilising the PID field in the PDCP PDU. + +The mapping of the PID values shall follow the general rules listed below: + +- PID values shall be mapped to the different packet types independently at each PDCP entity; +- PID value "0" shall indicate "no compression". PID value "0" shall be used in a PDCP PDU containing in its Data field a PDCP SDU that is unchanged by the Sender and that shall not be decompressed by the Receiver.; +- PID values are mapped in ascending order, starting from 1, for every configured header compression protocol, in the order of configuration by upper layer. The first available PID value is assigned to the first packet type of the header compression protocol as defined in the specification for this header compression protocol. PID values are mapped for all the specified packet types defined for the header compression protocol and in the order defined in subclause 5.1.2.2 and 5.1.3.3 for the respective header compression protocol; +- PID values are re-mapped for the PDCP entity after any reconfiguration of the header compression protocols for that entity. + +The following table illustrates an example of the PID value mapping to the packet types when five arbitrary header compression methods are configured for one PDCP entity: RFC 2507[6], Methods A and B, ROHC [8], [10] and Method C. Method A, Method B and Method C are imaginary header compression protocols introduced for the purpose of illustration. + +**Table 1: Example of the PID value mapping table** + +| PID Value | Optimisation method | Packet type | +|------------------|----------------------------|---------------------------| +| 0 | No header compression | - | +| 1 | RFC 2507 | Full header | +| 2 | RFC 2507 | Compressed TCP | +| 3 | RFC 2507 | Compressed TCP nondelta | +| 4 | RFC 2507 | Compressed non TCP | +| 5 | RFC 2507 | Context state | +| 6 | Method A | Packet Type 1 of Method A | +| 7 | Method A | Packet Type 2 of Method A | +| 8 | Method B | Packet Type 1 of Method B | +| 9 | Method B | Packet Type 2 of Method B | +| 10 | RFC 3095, RFC 4815 | ROHC packet format | +| 11 | Method C | Packet Type 1 of Method C | +| 12 | Method C | Packet Type 2 of Method C | +| 13...31 | Unassigned value | - | + +### 5.1.2 IP Header Compression (RFC 2507) + +The detailed operation of the RFC 2507 header compression protocol is specified in IETF RFC 2507 [6]. The mechanisms related to error recovery and packet reordering are also described in RFC 2507. These mechanisms shall be included in the functionality of the header compression supported by PDCP. The implementation of the RFC 2507 header compression functionality is not covered in this specification and is left to the implementation. + +#### 5.1.2.1 Context identifiers + +Context identifiers for RFC 2507 shall only be included in the RFC 2507 packet types format, as defined in [6]. + +#### 5.1.2.2 Mapping of PID values for RFC 2507 + +PID values shall be mapped to the RFC 2507 header compression packet types in the order presented in Table 2 below where "n" is the number of PID values already mapped to other protocol packet types. + +**Table 2: Mapping of PID values for RFC 2507 header compression protocol** + +| PID value | Optimisation method | Packet type | +|------------------|----------------------------|--------------------------| +| n+1 | RFC 2507 | Full header | +| n+2 | RFC 2507 | Compressed TCP | +| n+3 | RFC 2507 | Compressed TCP non-delta | +| n+4 | RFC 2507 | Compressed non-TCP | +| n+5 | RFC 2507 | Context state | + +#### 5.1.2.3 Management of Full Header transmission + +Transmission of a full header packet may be controlled by the lower layer information. + +For a TCP stream, if the PDCP receives from lower layer the information of failed transmission of a single packet, the PDCP may send the next packet as a full header. + +For a non-TCP stream, if the PDCP receives from lower layer the information of successful transmission of a full header packet, the PDCP may stop sending a full header packet that contains the same full header as the previously transmitted one. + +### 5.1.3 Robust Header Compression + +The detailed operation of the, "RObust Header Compression (ROHC)" protocol is specified in IETF RFC 3095 [8] and IETF RFC 4815 [10]. + +#### 5.1.3.1 Context identifiers + +The context of the ROHC protocol is defined in [8] and [10]. ROHC can be configured to support one or several contexts. Each context is identified by a value known as the context identifier (CID). + +#### 5.1.3.2 Void + +#### 5.1.3.3 Mapping of PID values + +The following PID value shall be mapped to the robust header compression protocol as presented in the table where n is the number of PID values already assigned to other protocol packet types. + +**Table 4: Mapping of PID values for RFC 3905 header compression protocol** + +| PID value | Optimisation method | Packet type | +|-----------|---------------------|--------------------| +| n+1 | RFC 3095, RFC 4815 | ROHC packet format | + +#### 5.1.3.4 Void + +#### 5.1.3.5 Protocol Parameters + +ROHC has two types of parameters [8], [10]: + +- configuration parameters: these are mandatory and must be configured between compressor and decompressor peers. +- implementation parameters: these are optional and, when used, stipulate how the compression protocol operates. + +These parameters are categorized in four different groups, as defined below: + +- M: Mandatory and configured by upper layers. +- MO: Parameters that must be supported and when used can only be configured or triggered by upper layers. +- O: Optional parameters that are not configured by upper layers. They may be used locally (i.e. UTRAN and/or in UE). +- N/A: These are not used in ROHC. + +The usage and definition of the parameters shall be as specified below. + +- MAX\_CID (M): This is the maximum CID value that can be used. One CID value shall always be reserved for uncompressed flows. +- LARGE\_CIDS: This is not configured by upper layers but inferred from the configured value of MAX\_CID according to the following rule: + +If MAX\_CID > 15 then LARGE\_CIDS = TRUE else LARGE\_CIDS = FALSE. + +- PROFILES (M): Profiles are used to define which profiles are allowed to be used by the UE in uplink. In downlink, all the profiles defined in [8] shall be supported. +- FEEDBACK\_FOR (N/A): +- MRRU (M): Segmentation is not used by default. +- NO\_OF\_PACKET\_SIZES\_ALLOWED (N/A). +- PACKET\_SIZES\_ALLOWED (N/A) +- PAYLOAD\_SIZES (O). +- NO\_OF\_PACKET\_SIZES\_USED (O). + +- PACKET\_SIZES\_USED (O). +- CONTEXT\_REINITIALIZATION (MO). +- MODE (O). +- CLOCK\_RESOLUTION (O). +- REVERSE\_DECOMPRESSION\_DEPTH (M): Default value is that reverse decompression is not used. + +#### 5.1.3.6 Configuration by RRC + +If the variable "PDCP\_ROHC\_TARGET\_MODE" [2] is stored in the UE, and if applicable for the ROHC profile applied, the de-compressor shall only perform the operational state transitions defined in [8] to the stored mode. + +If the variable "PDCP\_ROHC\_TARGET\_MODE" [2] is not stored in the UE, the de-compressor shall not restrict the operational state transitions defined in [8]. + +## 5.2 Void + +## 5.3 Data Transfer + +If header compression is configured the PDCP entity in the Sender shall: + +- perform header compression upon reception of a PDCP SDU from upper layers; +- if the radio bearer is configured for lossless SRNS Relocation or lossless DL RLC PDU size change: + - maintain PDCP sequence numbering as specified in subclause 5.6.1.1; +- submit the PDCP PDU to lower layer in the sequence received from the upper layer. + +If radio bearer is connected to a CS domain radio access bearer, the sender shall: + +- if the PDCP SDU length is of 1 or more bits: + - include the CS counter in the PDCP AMR Data PDU as specified in subclause 5.6.1.4; + - indicate the PDCP AMR PDU type in the PDU type field; + - fill the data field of the PDCP AMR PDU type with the PDCP SDU and add padding bits as specified in subclause 8.2.4. + +NOTE: If no AMR or AMR WB frames is generated by upper layers, no PDCP PDU is submitted to the lower layer. + +When the PDCP entity at the Receiver receives the PDCP PDU from lower layers, it shall: + +- if the received PDCP PDU is of type PDCP AMR Data PDU: + - the PDCP SDU is derived from the data field of the PDCP AMR Data PDU. The receiver determines the bit aligned data content and Frame Type from the PDU Data field length, as possible AMR and AMR WB payload has a unique size when being octet aligned; + - deliver the PDCP SDU and CS counter from the received PDCP header to the upper layer. +- else: + - perform header decompression (if header compression is configured) of the PDCP PDU to obtain the PDCP SDU; and + - deliver the PDCP SDU to the upper layer in the order received from the lower layer; + +- if the received PDCP PDU is of type PDCP SeqNum PDU: + - follow the procedure in subclause 5.6.1.2. + +### 5.3.1 Data transfer over acknowledged mode RLC + +Figure 2 shows the PDCP data transfer over acknowledged mode RLC. + +![Sequence diagram for PDCP data transfer over acknowledged mode RLC. The diagram is divided into 'Originator' and 'Receiver' sections. The Originator side has vertical lifelines for 'PDCP user', 'PDCP', and 'RLC'. The Receiver side has vertical lifelines for 'RLC', 'PDCP', and 'PDCP user'. Sequence of events: 1. PDCP user sends 'PDCP-DATA.req' to PDCP. 2. PDCP sends 'RLC-AM-DATA.req' to RLC. 3. Originator RLC sends data across to Receiver RLC. 4. Receiver RLC sends 'Acknowledgement' back to Originator RLC. 5. Receiver RLC sends 'RLC-AM-DATA.ind' to Receiver PDCP. 6. Receiver PDCP sends 'PDCP-DATA.ind' to Receiver PDCP user. 7. Originator RLC sends 'RLC-AM-DATA.cnf (NOTE)' to Originator PDCP.](1b5a812c8aa20fd5cba28e97001d32de_img.jpg) + +Sequence diagram for PDCP data transfer over acknowledged mode RLC. The diagram is divided into 'Originator' and 'Receiver' sections. The Originator side has vertical lifelines for 'PDCP user', 'PDCP', and 'RLC'. The Receiver side has vertical lifelines for 'RLC', 'PDCP', and 'PDCP user'. Sequence of events: 1. PDCP user sends 'PDCP-DATA.req' to PDCP. 2. PDCP sends 'RLC-AM-DATA.req' to RLC. 3. Originator RLC sends data across to Receiver RLC. 4. Receiver RLC sends 'Acknowledgement' back to Originator RLC. 5. Receiver RLC sends 'RLC-AM-DATA.ind' to Receiver PDCP. 6. Receiver PDCP sends 'PDCP-DATA.ind' to Receiver PDCP user. 7. Originator RLC sends 'RLC-AM-DATA.cnf (NOTE)' to Originator PDCP. + +**Figure 2: PDCP data transfer over acknowledged mode RLC** + +NOTE: If the primitive RLC-AM-DATA.req is used with parameter CNF, the primitive RLC-AM-DATA.cnf is delivered. Otherwise, this primitive is not delivered. + +### 5.3.2 Data transfer over unacknowledged and transparent mode RLC + +Figure 3 shows the PDCP data transfer over unacknowledged or transparent mode RLC. + +![Sequence diagram for PDCP data transfer over unacknowledged or transparent mode RLC. The diagram is divided into 'Sender' and 'Receiver' sections. Both sides have vertical lifelines for 'PDCP user', 'PDCP', and 'RLC'. Sequence of events: 1. Sender PDCP user sends 'PDCP-DATA.req' to Sender PDCP. 2. Sender PDCP sends 'RLC-UM-DATA.req / RLC-TM-DATA.req' to Sender RLC. 3. Sender RLC sends data across to Receiver RLC. 4. Receiver RLC sends 'RLC-UM-DATA.ind / RLC-TM-DATA.ind' to Receiver PDCP. 5. Receiver PDCP sends 'PDCP-DATA.ind' to Receiver PDCP user.](704082cc3e11776bda29595c76411362_img.jpg) + +Sequence diagram for PDCP data transfer over unacknowledged or transparent mode RLC. The diagram is divided into 'Sender' and 'Receiver' sections. Both sides have vertical lifelines for 'PDCP user', 'PDCP', and 'RLC'. Sequence of events: 1. Sender PDCP user sends 'PDCP-DATA.req' to Sender PDCP. 2. Sender PDCP sends 'RLC-UM-DATA.req / RLC-TM-DATA.req' to Sender RLC. 3. Sender RLC sends data across to Receiver RLC. 4. Receiver RLC sends 'RLC-UM-DATA.ind / RLC-TM-DATA.ind' to Receiver PDCP. 5. Receiver PDCP sends 'PDCP-DATA.ind' to Receiver PDCP user. + +**Figure 3: PDCP data transfer over unacknowledged or transparent mode RLC** + +## 5.4 SRNS Relocation + +In case of SRNS Relocation upper layer indicates to PDCP to perform either the re-initialisation or the context relocation of compression protocols of an RB, or the release of the compression protocols of an RB. In this version of the specification, context relocation is only applicable to RFC3095. Each of the compression protocols is handled independently, but the context relocation capability is optional for the UE and it is indicated as a part of the UE radio access capabilities. + +The re-initialisation of a given compression protocol entails the following: + +- Compression parameters may be reconfigured by upper layers during re-initialisation, otherwise compression parameters remain valid during re-initialisation. +- All compression state information is initialised, e.g. header compression contexts. Therefore, the first 'compressed' packet type after SRNS Relocation is a full header. + +- The PDCP sequence numbers are not changed due to the PDCP header compression protocol re-initialisation. + +The context relocation of a given compression protocol entails the following: + +- Configured compression parameters remain valid during context relocation. +- A snapshot of the compression state information (context) is taken in the source RNC and transferred to the target RNC, which initialises the header compression protocol according to the transferred snapshot. Therefore, the (de)compression continues after SRNS Relocation from the context used before relocation. +- Some additional specific actions are performed both in UE and UTRAN during the SRNS Relocation in order to keep the (de)compressors consistent. + +### 5.4.1 Lossless SRNS Relocation + +Lossless SRNS Relocation is only applicable when RLC is configured for in-sequence delivery and acknowledged mode. The support of lossless SRNS Relocation is configured by upper layer. + +For the support of lossless SRNS Relocation, the PDCP entities maintain sequence numbers for PDCP SDUs, as described in subclause 5.6.1.1. + +These sequence numbers are synchronised between PDCP Sender and Receiver, as described in subclause 5.6.1.2. + +When a lossless SRNS Relocation is performed sequence numbers are exchanged between UE and UTRAN. They are used to confirm PDCP SDUs transmitted but not yet acknowledged by the Receiver, as described in subclause 5.6.1.3. After relocation the data transfer begins with the first unconfirmed PDCP SDU. + +#### 5.4.1.1 Void + +#### 5.4.1.2 Void + +#### 5.4.1.3 Void + +### 5.4.2 Context relocation + +The header compression context relocation is performed by the decision of upper layers in source RNC based on the UE radio capabilities. The decision is done independently every time the SRNS relocation occurs and is specific for each header compression protocol. It is indicated to UE as a part of the SRNS relocation signalling of the upper layer and the selected relocation method is configured to UE PDCP by the upper layer. + +The header compression context relocation shall not be performed if the radio bearer is configured to support the lossless SRNS Relocation. + +**In the UE**, upon reception of the indication about SRNS relocation being performed: + +- the upper layer configures PDCP (*CPDCP-CONFIG.Req*) to perform either re-initialisation (R) or the context relocation (C) of header compression protocols; +- if the context relocation is to be applied for RFC3095 header compression protocol: + - if the **compressor** (M-HC) is operating in **R mode**: + - uplink data may be compressed and transmitted normally. + - if the **compressor** (M-HC) is operating in **O mode**: + - compress and transmit uplink data as specified in [8] using the assumption that all ROHC uplink packets transmitted are likely to be lost. When SRNS relocation is completed, M-HC should return to normal operation. + +NOTE: When the M-HC is using the assumption that all ROHC uplink packets transmitted are likely to be lost: + +- the M-HC can not transit to a higher compression state; + - for W-LSB encoding, the M-HC updates the set of candidate reference values used by the decompressor by adding newly transmitted values but not removing old values. +- if the **compressor** (M-HC) is operating in **U mode**: + - M-HC shall transit to FO state and send IR-DYN to re-synchronise the dynamic part of the uplink context. + - if the reverse decompression is applied in the **decompressor** (M-HD): + - flush the reverse decompression buffer by discarding all packets in the buffer. + - in the **decompressor** (M-HD), in **all modes**: + - downlink data may be received and decompressed normally. + +**In the UTRAN source RNC**, while SRNS relocation is being performed: + +- if the context relocation is to be applied for RFC3095 header compression protocol: + - PDCP is requested to take a context snapshot by the upper layer (*CPDCP-CONTEXT.Req*); +- if the **compressor** (source N-HC) is operating in **R mode**: + - the source N-HC should take a snapshot of its header compression compressor context (denoted *N-context-C\**); + - header compression contexts should not be updated anymore even though downlink data may be compressed and transmitted otherwise normally. This can be done by sending R-1\* packets. +- if the **compressor** (source N-HC) is operating in **O mode**: + - the source N-HC should take a snapshot of its header compression compressor context (denoted *N-context-C\**); + - after the snapshot is taken, the source N-HC should only send UO-0 or UO-1\* packets. This means only RTP SN, RTP TS, and IP-ID (for IPv4 only) fields are updated in the decompressor context at M-HD. +- if the **compressor** (source N-HC) is operating in **U mode**: + - the source N-HC should take a snapshot of the static part of its header compression compressor context (denoted *N-context-C-static\**). +- if the **decompressor** (source N-HD) is operating in **R or O mode**: + - if the source N-HD is sure about the integrity of the *N-context-D*: + - the source N-HD should take a snapshot of its header compression decompressor context (denoted as *N-context-D\**). + - if the source N-HD is only sure about the integrity of the static part of the *N-context-D* (e.g. due to multiple detected errors): + - the source N-HD should take a snapshot only of the static part of the *N-context-D* (denoted as *N-context-D-static\**). + - RFC3095 acknowledgments should not be generated anymore even though uplink data may be received and decompressed otherwise normally. +- if the **decompressor** (source N-HD) is operating in **U mode**: + +- the source N-HD should take a snapshot of the static part of its header compression decompressor context (denoted *N-context-D-static\**). +- either *N-context-C\** or *N-context-C-static\** and either *N-context-D\** or *N-context-D-static\** should be delivered to the upper layer as *Context-Info (CPDCP-CONTEXT.Conf)*, which is to be transmitted further to the target RNC. + +**In the UTRAN target RNC**, while SRNS relocation is being performed: + +- the upper layer configures PDCP (*CPDCP-CONFIG.Req*) to perform either initialisation (I) or the context relocation (C) of header compression protocols; +- the new header compression entity should be created; +- if the context relocation is to be applied for RFC3095 header compression protocol: + - in the **compressor** (target N-HC), in **all modes**: + - the header compression compressor (target N-HC) should be initialised to the same mode as used in the source N-HC using *N-context-C\** as the initial header compression compressor context; + - in addition, if the source N-HC was operating in U-mode, the target N-HC should first send IR-DYN to resynchronise the dynamic part of the downlink context. + - in the **decompressor** (target N-HD), in **all modes**: + - if *Context-Info* carries N-context-D\*: + - the header compression decompressor (target N-HD) should be initialised to the same mode as used in the source N-HD using *N-context-D\** as the initial header compression decompressor context. + - if *Context-Info* carries N-context-D-static\*: + - the header compression decompressor (target N-HD) should be initialised to the same mode as used in the source N-HD using *N-context-D-static\** as the initial header compression decompressor context; + - the target N-HD should send a request for IR-DYN. + +## 5.5 Lossless DL RLC PDU size change + +Lossless DL RLC PDU size change is only applicable when RLC is configured for in-sequence delivery and acknowledged mode. The support of lossless DL RLC PDU size change is configured by upper layer. + +For the support of lossless DL RLC PDU size change, the PDCP entities maintain sequence numbers for DL PDCP SDUs, as described in subclause 5.6.1.1. + +These DL sequence numbers are synchronised between PDCP Sender in the UTRAN and Receiver in the UE, as described in subclause 5.6.1.2. + +When a lossless DL RLC PDU size change is performed the next expected DL\_Receive PDCP SN is sent from the UE to the UTRAN. It is used to confirm DL PDCP SDUs transmitted but not yet acknowledged by the Receiver in the UE, as described in subclause 5.6.1.3. After lossless DL RLC PDU size change the data transfer begins with the first unconfirmed DL PDCP SDU. + +## 5.6 General procedures + +#### 5.6.1.1 PDCP Sequence Numbering + +The value of the PDCP sequence number ranges from 0 to 65535. The PDCP SN window size indicates the maximum number of PDCP SDUs, not confirmed to have been successfully transmitted to the peer entity by lower layer, that can be numbered at any given time. The PDCP SN window size is configured by upper layers. PDCP sequence numbers are set to "0" when the PDCP entity is set-up for the first time. + +In the following the "submission/reception of a PDCP SDU to/from lower layer" is used as a synonym for the submission/reception of a PDCP Data PDU or a PDCP SeqNum PDU to/from lower layer that carries in its Data field a compressed or uncompressed PDCP SDU. + +If lossless SRNS relocation and/or lossless DL RLC PDU size change are/is supported by the UE, for each radio bearer configured to support "lossless SRNS relocation or lossless DL RLC PDU size change" as specified in [1], PDCP sequence numbers are applied: + +- in the UE: + - the DL\_Receive PDCP SN shall be set to "0" for the first PDCP SDU received from lower layer; + - the DL\_Receive PDCP SN shall be incremented by "1" for the next PDCP SDU received from lower layer. +- in the UTRAN: + - the DL\_Send PDCP SN should be set to "0" for the first PDCP SDU submitted to lower layer; + - the DL\_Send PDCP SN should be incremented by "1" for the next PDCP SDU submitted to lower layer. + +Additionally, if lossless SRNS relocation is supported by the UE, for each radio bearer configured to support "lossless SRNS relocation or lossless DL RLC PDU size change" as specified in [1], PDCP sequence numbers are applied: + +- in the UE: + - the UL\_Send PDCP SN shall be set to "0" for the first PDCP SDU submitted to lower layer; + - the UL\_Send PDCP SN shall be incremented by "1" for the next PDCP SDU submitted to lower layer; +- in the UTRAN: + - the UL\_Receive PDCP SN should be set to "0" for the first PDCP SDU received from lower layer; + - the UL\_Receive PDCP SN should be incremented by "1" for the next PDCP SDU received from lower layer. + +PDCP sequence numbers shall not be decremented in a PDCP entity. + +#### 5.6.1.2 PDCP Sequence Number synchronization + +For radio bearers that are configured to support "lossless SRNS Relocation or lossless DL RLC PDU size change" as specified in [1]: + +the UE PDCP entity shall: + +- if the UE supports lossless SRNS relocation, + - if a PDCP entity has to synchronise the UL PDCP SN following a RLC reset or RLC transmitting side re-establishment not caused by a lossless SRNS Relocation; or + - if the UE PDCP entity receives an invalid "next expected UL Receive PDCP SN" from upper layer after a lossless SRNS Relocation; + - trigger the PDCP SN synchronisation procedure by submitting one PDCP SeqNum PDU to lower layer; + - consider that the synchronisation procedure is complete on confirmation by lower layer of the successful transmission of the PDCP SeqNum PDU. +- if the UE supports lossless DL RLC PDU size change but not lossless SRNS relocation, the UE PDCP entity shall not submit PDCP SeqNum PDU to lower layer. + +- the UTRAN PDCP entity should: + +- if a PDCP entity has to synchronise the DL PDCP SN following a RLC reset or RLC transmitting side re-establishment not caused by a lossless SRNS Relocation or a lossless DL RLC size change; or +- if the UTRAN PDCP entity receives an invalid "next expected DL\_Receive PDCP SN" from upper layer after lossless SRNS Relocation or lossless DL RLC PDU size change: + +- trigger the PDCP SN synchronisation procedure by submitting one PDCP SeqNum PDU to lower layer; +- consider that the synchronisation procedure is complete on confirmation by lower layer of the successful transmission of the PDCP SeqNum PDU. + +In the UE/UTRAN, the "next expected UL/DL\_Receive PDCP SN" is considered invalid if its value is less than the UL/DL\_Send PDCP SN of the first transmitted but not yet acknowledged PDCP SDU or greater than that of the first unsent PDCP SDU. + +On receiving a PDCP SeqNum PDU: + +- the UE PDCP entity shall: + - set the value of the DL\_Receive PDCP SN to the value indicated in the PDCP SeqNum PDU; +- the UTRAN PDCP entity should: + - set the value of the UL\_Receive PDCP SN to the value indicated in the PDCP SeqNum PDU. + +NOTE: If UTRAN has the intention to use only the lossless DL RLC PDU size change, UTRAN may not maintain UL PDCP SN. In this case, UTRAN should still transfer the user data to upper layer. + +#### 5.6.1.3 Sequence Number and Data Forwarding + +In case of a lossless SRNS Relocation procedure or lossless DL RLC size change, as described in [1]: + +- the UE shall send to the UTRAN the next expected DL\_Receive PDCP SN. + +Additionally, in case of lossless SRNS relocation procedure, as described in [1]: + +- the UTRAN should send to the UE the next expected UL\_Receive PDCP SN. + +This information exchange synchronises the Sequence Numbers at the UE and UTRAN PDCP entities. + +When requested by the upper layer, for each radio bearer configured to support lossless SRNS Relocation, the PDCP sublayer in the source RNC should forward the following to the target RNC: + +- the UL\_Receive PDCP SN of the next PDCP SDU expected to be received from the UE; +- the DL\_Send PDCP SN of the first transmitted but not yet acknowledged PDCP SDU; +- the transmitted but not yet acknowledged PDCP SDUs together with their related DL\_Send PDCP SNs; +- the not yet transmitted PDCP SDUs. + +#### 5.6.1.4 CS Counter Handling + +In case the radio bearer is connected to a CS domain radio access bearer, the CS counter shall be included in the PDCP AMR Data PDU. + +The value of the CS counter shall be set to the first to fifth LSBs of the CFN at which the packet has been received from higher layers. + +In the receiving side, the CS counter shall be delivered to the upper layer together with the PDCP SDU. + +The CS counter is used to manage the delay jitter generated by the radio layer. The CS counter plus the value of the information element "Max CS delay", as signalled in [2], indicates the latest instance at which the AMR or AMR WB frames is delivered to the upper layer. + +## 5.7 Header Compression and Decompression for MBMS + +Header compression and decompression for a p-t-m MBMS service is performed in ROHC U-mode. + +Applying ROHC for p-t-m RB configuration is optional and should be configured per MBMS session. + +### 5.7.1 Cell change inside the same cell group + +When a UE moves to a cell that is the same cell group with that of the previous cell while receiving a p-t-m MBMS service which is provided in both cells, the UE shall: + +- continue header decompression during and after cell change. + +### 5.7.2 Cell change between cell groups + +When a UE moves to a cell that is the different cell group with that of the previous cell while receiving a p-t-m MBMS service which is provided in both cells, the UE shall: + +- reconfigure and re-initialise the PDCP entity; +- reuse the static part of the header decompressor context used in the previous cell; +- re-initialise header decompression after receiving IR-DYN or IR packet and correcting the CID of the context with the CID being used in the new cell. + +NOTE: How to correct CID is implementation issue and is not specified. + +# --- 6 Services + +## 6.1 Services provided to upper layers + +The following services are provided by PDCP to upper layers: + +- transfer of user data; +- maintenance of PDCP SDU sequence numbers. + +## 6.2 Services expected from RLC layer + +For a detailed description of the following functions see [5]. + +- transparent data transfer Service; +- unacknowledged data transfer Service; +- acknowledged data transfer Service. + +# --- 7 Elements for layer-to-layer communication + +The interaction between the PDCP layer and other layers are described in terms of primitives where the primitives represent the logical exchange of information and control between the PDCP layer and other layers. The primitives shall not specify or constrain implementations. + +## 7.1 Primitives between PDCP and upper layers + +The primitives between PDCP and upper layers are shown in Table 5. + +**Table 5: Primitives between PDCP and upper layers** + +| Generic Name | Parameter | | | | +|---------------|----------------------------------------------------------------------------------------------------|------------------|-------------|----------------------------------| +| | Req. | Ind. | Resp. | Conf. | +| PDCP-DATA | Data | Data, CS Counter | Not Defined | Not Defined | +| CPDCP-CONFIG | PDCP-Info, RLC-SAP
SN_Sync, R/I/C/RS,
Context-Info, PDCP
Unrecoverable Error
Detection | Not Defined | Not Defined | Not Defined | +| CPDCP-CONTEXT | None | Not Defined | Not Defined | Context-Info | +| CPDCP-RELEASE | RLC-SAP | Not Defined | Not Defined | Not Defined | +| CPDCP-SN | PDCP SN | Not Defined | Not Defined | Not Defined | +| CPDCP-RELOC | Next_Receive_SN | Not Defined | Not Defined | Next_Receive_SN,
Next_Send_SN | + +Each Primitive is defined as follows: + +### a) PDCP-DATA-Req./Ind. + +- PDCP-DATA-Req is used by upper user-plane protocol layers to request a transmission of upper layer PDU. PDCP-DATA-Ind is used to deliver PDCP SDU that has been received to upper user plane protocol layers. + +### b) CPDCP-CONFIG-Req. + +- CPDCP-CONFIG-Req is used to configure and – in case of already existing PDCP entity – to reconfigure a PDCP entity and to assign it to the radio bearer associated with that entity. + +### c) CPDCP-RELEASE-Req. + +- CPDCP-RELEASE-Req is used by upper layers to release a PDCP entity. + +### d) CPDCP-SN-Req. + +- This primitive is used at the UTRAN. CPDCP-SN-Req is used to transfer the PDCP SN to PDCP. + +### e) CPDCP-RELOC-Req/Conf. + +- CPDCP-RELOC-Req initiates the SRNS Relocation procedure in PDCP for those radio bearers that are configured to support lossless SRNS Relocation. The Next\_Receive\_SN is only included at the UE side. +- CPDCP-RELOC-Conf is used to transfer the Next\_Receive\_SN and/or Next\_Send\_SN to upper layers for lossless SRNS Relocation. The Next\_Send\_SN is only included at the source RNC. + +### f) CPDCP-CONTEXT-Req./Conf. + +- CPDCP-CONTEXT-Req initiates specific actions in the source RNC in order to perform context relocation as a part of the SRNS relocation. The primitive is applicable only in the source RNC. +- CPDCP-CONTEXT-Conf is used to transfer the header compression context information from PDCP to upper layer in order to perform context relocation as a part of the SRNS relocation. The primitive is applicable only in the source RNC. + +The following parameters are used in the primitives: + +#### 1) PDCP-Info: + +- Contains the parameters for each of the header compression protocols configured to be used by one PDCP entity. + +#### 2) RLC-SAP: + +- The RLC-SAP (TM/UM/AM) used by PDCP entity when communicating with RLC sublayer. + +#### 3) SN\_Sync: + +- Indicates that PDCP should start PDCP SN synchronisation procedure. +- 4) Next\_Send\_SN: +- The Send PDCP SN of the next PDCP SDU to be sent. There is one in the uplink (UL\_Send PDCP SN) and one in the downlink (DL\_Send PDCP SN). Refer to subclause 5.4.1. +- 5) Next\_Receive\_SN: +- The Receive PDCP SN of the next PDCP SDU expected to be received. There is one in the uplink (UL\_Receive PDCP SN) and one in the downlink (DL\_Receive PDCP SN). Refer to subclause 5.4.1. +- 6) PDCP SN: +- This includes a PDCP sequence number. +- 7) R/I/C/RS +- Indicates that PDCP should Re-initialise (R)/Initialise (I) the header compression protocols. Alternatively (Context-relocation, C) it indicates that UE PDCP shall perform specific actions related to context relocation during SRNS relocation. (RS) indicates to Re-initialise while keeping the static part of the header compression (only for ROHC). R/I/C/RS indication is given separately for each of the configured header compression protocol, if several exist for a given radio bearer. +- 8) Context-Info: +- Contains the header compression context information of each of the header compression protocols that are subject to the context relocation during SRNS relocation. +- 9) CS Counter: +- Contains the timing information of AMR or AMR WB frame that will be used by upper layer. +- 10) PDCP Unrecoverable Error Detection: +- Determines whether PDCP Unrecoverable Error Detection shall be performed in a PDCP entity. + +# --- 8 Elements for peer-to-peer communication + +## 8.1 Protocol data units + +Different PDU formats are defined for the PDCP protocol, one not introducing any overhead to the (compressed) PDCP SDU, others introducing such overhead. + +## 8.2 Formats + +A PDCP PDU shall be a multiple of 8 bits, if the RLC entity is configured for unacknowledged or acknowledged mode. Otherwise, if the RLC entity is configured for transparent mode, it is bit-aligned. In Tables 6, 7 and 8, bit strings are represented as follows: the first bit is the leftmost one on the first line of the table, the last bit is the rightmost on the last line of the table, and more generally the bit string is to be read from left to right and then in the reading order of the lines. + +SDUs are bit strings, with any non-null length. If not compressed within PDCP an SDU is included from first bit onward. + +### 8.2.1 PDCP-No-Header PDU + +The PDCP-No-Header PDU does not introduce any overhead to the PDCP SDU. The use of the PDCP-No-Header PDU is configured by the upper layer. + +The format of the PDCP-No-Header PDU is shown in Table 6. + +**Table 6: PDCP-No-Header PDU** + +| | +|------| +| Data | +|------| + +### 8.2.2 PDCP Data PDU + +The PDCP Data PDU is used to convey: + +- data containing an uncompressed PDCP SDU; or +- header compression related control signalling; or +- data that has been obtained from PDCP SDU after header compression. + +The format of the PDCP Data PDU is shown in Table 7. + +Table 7: PDCP Data PDU format + +| | | +|----------|-----| +| PDU type | PID | +| Data | | + +### 8.2.3 PDCP SeqNum PDU + +The PDCP SeqNum PDU is used to convey a PDCP SDU sequence number and: + +- data containing an uncompressed PDCP SDU; or +- data that has been obtained from PDCP SDU after header compression. + +The format of the PDCP SeqNum PDU is shown in Table 8. + +Table 8: PDCP SeqNum PDU format + +| | | +|-----------------|-----| +| PDU type | PID | +| Sequence number | | +| Data | | +| | | + +### 8.2.4 PDCP AMR Data PDU + +The PDCP AMR Data PDU is used to convey: + +- a PDCP SDU containing AMR or AMR WB frame + +The format of the PDCP AMR Data PDU is shown in Table 9. + +Table 9: PDCP AMR Data PDU format + +| | | +|----------|------------| +| PDU type | CS counter | +| Data | | + +The PDCP PDU is octet aligned but the actual PDCP SDU carrying the AMR or AMR WB frame may not be octet aligned. The data field contains the "AMR Core Frame" of AMR IF1 as defined in [11] or "AMR-WB Core Frame" of AMR-WB IF1 as defined in [12]. The AMR classes are always encoded in the order of class A, B and C, where d(0) of the "AMR Core Frame" or "AMR-WB Core Frame" is carried in the first bit of data field. Any padding for octet alignment is inserted at the end of the data field. + +## 8.3 Parameters + +If not otherwise mentioned in the definition of each field then the bits in the parameters shall be interpreted as follows: the left most bit string is the first and most significant and the right most bit is the last and least significant bit. + +Unless otherwise mentioned, integers are encoded in standard binary encoding for unsigned integers. In all cases the bits appear ordered from MSB to LSB when read in the PDU. + +### 8.3.1 PDU Type + +Length: 3 bits. + +The PDU type field indicates the PDCP Data PDU type. + +| Bit | PDU Type | +|----------------|---------------------------------------------------------------------------------| +| 000 | PDCP Data PDU (Table 7) | +| 001 | PDCP SeqNum PDU (Table 8) | +| 010 | PDCP AMR Data PDU (Table 9) | +| 011-111 | Reserved (PDUs with this encoding are invalid for this version of the protocol) | + +### 8.3.2 PID + +Length: 5 bits. + +The PID field indicates the used header compression and packet type. + +| Bit | Description | +|--------------------|---------------------------------------------------------------------------------------| +| 00000 | No header compression | +| 00001-11111 | Dynamically negotiated header compression identifier, as described in subclause 5.1.1 | + +The PID field value indicates the used header compression protocol type and packet type. A specific header compression protocol may utilize a certain range of consecutive values from the PID field value space for different packet types. The Receiving PDCP entity performs the necessary operation (e.g. header decompression) according to the PID field value. + +### 8.3.3 Data + +The Data field may include either one of the following: + +- Uncompressed PDCP SDU; +- Header compressed PDCP SDU; +- Header compression protocol feedback information. + +### 8.3.4 Sequence number + +Length: 16 bits + +PDCP SDU sequence number. + +### 8.3.5 CS counter + +Length: 5 bits + +CS counter field value indicates the timing of AMR or AMR WB frame. + +# --- 9 Handling of unknown, unforeseen and erroneous protocol data + +## 9.1 Invalid PDU type + +If a PDCP entity receives a PDCP PDU with a PDU Type set to Reserved (see subclause 8.3.1), it shall: + +- discard the PDCP PDU. + +If a PDCP entity is not configured for lossless SRNS Relocation or lossless DL RLC PDU size change and receives a PDCP SeqNum PDU, it shall: + +- discard the PDCP SeqNum PDU. + +## 9.2 Invalid PID value + +If a PDCP entity receives a PDCP PDU with a PID value that is not mapped with a valid packet type (see subclause 5.1.1), it shall: + +- discard the PDCP PDU. + +## 9.3 PDCP Unrecoverable Error Detection + +For each radio bearer that is configured to perform PDCP Unrecoverable Error Detection: + +- if the PDCP entity receives 2 or 3 consecutive PDCP PDUs with an unexpected or invalid PDU Type or PID value: + - the UE PDCP entity may indicate PDCP Unrecoverable Error to upper layer [2]. +- if the PDCP entity receives 4 consecutive PDCP PDUs with an unexpected or invalid PDU Type or PID value: + - the UE PDCP entity shall indicate PDCP Unrecoverable Error to upper layer [2]. + +NOTE1: Until the UE receives 4 consecutive PDCP PDUs with an unexpected or invalid PDU Type or PID value, the UE may apply a self-recovery mechanism. For example, the UE PDCP entity may indicate to RLC layer that HFN can be incremented. + +NOTE2: The PDCP unrecoverable error detection is performed before the invalid PDU type check specified in subclause 9.1. + +NOTE3: PDCP unrecoverable error detection in the UE can only detect the problem in the downlink. + +# --- Annex A (normative): ROHC performance testing + +## A.1 Introduction + +This subclause defines performance test cases for ROHC. The ROHC profile within scope is profile 0x0001 for compression of RTP/UDP/IP headers only. This subclause is not meant to bring incoherent limitations to implementations, and is not meant to create a sub-specification of [8], [10] either, as a consequence of the requirements on performance that it defines. + +### A.1.1 Purpose of the performance testing + +The purpose of the test cases is to ensure that ROHC implementations meet minimal requirements that can fairly be expected when subjected to an input sequence that includes frequently occurring and commonly observed changes in the values of header fields. The metrics used correspond to: + +- the average compressed header size for an entire test sequence, to assess an implementation's efficiency in terms of its overall compression ratio, and +- the average compressed header size for different sub-sequences within each test case, to assess an implementation's ability to minimize the variance in compressed header size with respect to the selection of the packet format used for individual packets. + +The latter is to avoid a less desirable behaviour where a compressor would consistently and exclusively use two types of compressed header formats; one format that offers no compression but that completely updates and/or repairs the context e.g. when the patterns of the header fields to be compressed do not allow optimal compression, and another format that provides the most efficient compression ratio otherwise. While it is noted that the use of larger headers is perfectly acceptable protocol-wise [8], the tests herein are meant to encourage compressor implementations to actively and efficiently implement compression. + +These metrics are defined so that they are not impacted by an implementation's specific robustness algorithm(s) as well as to allow a wide range of compression strategies. + +Compressor implementations are expected to implement robustness algorithms according to the optimistic approach for the U/O-modes of operation. The optimistic approach is the part of the selection of the packet format where a format that contains the necessary information to update a field is used a number N time, starting from the packet for which a new value has to be established in the decompressor context. While N is an implementation parameter, the metrics for each sequence in U/O-mode is expressed in terms of this parameter. Implementation should use the value N as an input parameter for the testing, to adapt to the expected robustness level required for the testing. The value of the parameter N is defined in test case definition separately (informative value is given in Annex B.2.3.). Similarly, R-mode operation requires that an update be conveyed to the decompressor until it gets acknowledged; however for R-mode, relevant test cases provide explicit feedback messages when necessary. + +The performance tests for ROHC as described in this subclause are carried out by providing a sequence of uncompressed IP/UDP/RTP packets to the ROHC RTP compressor, together with artificially generated feedback messages that are synchronized with the packet sequence. All packets in these sequences are built on the same base structure, with most field values being constant. The performance test cases define different change patterns for three specific fields: the IPv4 IP ID, the RTP SN, and the RTP TS. + +### A.1.2 Input sequence for uncompressed headers + +The structure of the IPv4/UDP/RTP header and IPv6/UDP/RTP header is outlined in annex A.3, along with tables of the values to be used for each field. Fields with values marked ANY can have any value;; these are the addressing fields that uniquely identify the flow of packets being compressed and their respective value does not otherwise affect the expected compression ratio as they are either sent in uncompressed form or completely omitted in compressed packets. The checksum values are dependent on the entire content of the packet and are calculated according to their respective protocol specifications, RFC 768 and RFC 791, which are referred to in the tables. For the input sequence, the UDP checksum with IPv4 shall always be enabled and thus have a non-zero value, i.e the two octets of the UDP checksum are always included as part of the calculation of the compressed header size for both IPv4 and IPv6. Each test sequence defines specific values to create varying change patterns for the IPv4 IP ID, the RTP SN, and the RTP TS. A dummy payload of an arbitrary non-zero value shall be appended at the end of the header data, following the RTP header. + +The outline of each test case follows the same format with respect to the input sequences and the requirements. Test 1a and 1b are base tests using a well-behaving flow of packets as one of the inputs. All subsequent tests are based on test 1a or test 1b, each with specific test events added to the packet flow of the base tests. + +### A.1.3 Feedback format for the test cases + +The feedback messages used in the test cases, when applicable, are artificially generated and interspersed with the input sequence of uncompressed packets. Feedback messages are generated according to the following format: + +![](088921fa3f5a44c8551815122517eefd_img.jpg) + +``` + + 0 1 2 3 4 5 6 7 + | 1 1 1 1 0 | Code | feedback type octet ++---+---+---+---+---+---+---+---+ +| Mode | SN | ++---+---+---+---+---+---+---+---+ +| N | ++---+---+---+---+---+---+---+---+ +| 0 1 | ++---+---+---+---+---+---+---+---+ ++---+---+---+---+---+---+---+---+ ++---+---+---+---+---+---+---+---+ + +``` + +Where: + +feedback data above the type octet is 4 octets) + +- Acktype is set to 0x0 (means ACK) +- Mode is set as defined by the test case +- SN is set as defined by the test case +- CRC is the 8-bit CRC computed over the entire feedback payload including any CID fields but excluding the packet type, the 'Size' field and the 'Code' octet, using the polynomial defined in [8], [10]. + +NOTE: If compressor uses CID field in compressed packet, the CID field should be included in the feedback packet and the Code and CID should be set as defined in [8]. + +### A.1.4 Feedback generation for test cases (R-mode only) + +This subclause defines a mechanism by which the test equipment shall dynamically generate feedback messages for each test case, once a transition to R-mode has been initiated and for the entire R-mode operation thereafter. Test cases may define additional feedback messages as input to the compressor. + +The test equipment shall generate a feedback message when the ROHC packet type octet of the received compressed header matches any of the values as described in the table A.1.4. The compressed header type can be identified by inspecting the packet type octet of the compressed header, i.e. the first octet of the ROHC base header [8]. + +**Table A.1.4: Bitmasks for feedback generation** + +| Compressed Header Type (binary mask) | Packet Type | Outcome | +|--------------------------------------|---------------|---------------| +| 01xxxxxx | R-0-CRC | Send feedback | +| 110xxxxx | UOR-2* | Send feedback | +| 1111110x | IR | Send feedback | +| 11111000 | IR-DYN | Send feedback | +| Other values | Other packets | No feedback | + +where 'x' means 'any value'. + +The feedback message shall be of the format as described in subclause A.1.3 using: + +- Mode is set to 0x3 (means R-mode) +- SN is set to the RTP SN corresponding to the received compressed header. + +The test equipment shall index the input sequence of uncompressed headers using the RTP Sequence Number, and it shall associate the correct RTP SN to each compressed header that it receives back from the compressor. The test equipment can derive the RTP SN by counting the number of received compressed headers. + +NOTE: The purpose of this mechanism is only to provide feedback to the compressor when operating in R-mode; it is not meant to make further verifications of any specific ROHC functionality and applies only to the test cases defined in this annex. + +### A.1.5 Calculation of compressed header size + +The following fields shall be excluded from the calculation of the size of the compressed header in evaluation of compression performance: + +- ROHC CID/add-CID octet(s); +- ROHC padding octets; +- ROHC segmentation octets; +- ROHC feedback octets, either piggybacked on the behalf of an associated decompressor or as feedback packets interspersed within the flow of compressed packets. + +## A.2 Test outline – RoHC RTP Profile 0x0001 + +RoHC compression shall start in U-mode, in accordance with RFC3095. Transition to other compression modes shall be initiated by the test equipment sending a feedback packet of type 2, indicating the desired mode transition. + +### A.2.1 Test 1a - Base test of ROHC RTP O-mode compressor + +#### A.2.1.1 Test purpose + +The purpose of the base test case is to verify that the compressor properly implements compression for a well-behaved IP/UDP/RTP packet flow, i.e. that it makes use of efficient compressed packet formats available to ROHC RTP [8] when operating in O-mode. + +#### A.2.1.2 Sequence details + +A sequence consisting of 70 packets in total is used, where all header fields are set according to the basic test packet structure, as described in subclause A.3, with addition of the following: + +1. The RTP Sequence Number is a linearly increasing counter with a packet-to-packet delta of 1, set to 0x0000 for the first packet and thus ending with 0x0045 (69) in the last packet of the sequence +2. The RTP Time Stamp is a linearly increasing counter with a packet-to-packet delta of 160, set to 0x00000000 for the first packet and thus ending with 0x00002B20 (11040) in the last packet of the sequence. +3. The IP Identification is set to the same value as the RTP Sequence Number; this means that for IPv4 the IP-ID behaviour is not random, thus value(RND)=0 defined in [8] for both IPv4 and IPv6. + +Between the 6th and 7th packets (SN=5 and SN=6) of the sequence, a ROHC feedback packet of feedback type 2 is to be given to the ROHC compressor to trigger an immediate transition to O-mode operation. The format of that packet is as follows: + +![](61126a1f3affdeea7b41bb68cba95138_img.jpg) + +| | | | | | | | | +|-------------------------------|---------|---|------|---|----|---|---| +| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | +| +---+---+---+---+---+---+---+ | | | | | | | | +| | 1 | 1 | 1 | 1 | et | | | +| +---+---+---+---+---+---+---+ | | | | | | | | +| | Acktype | | Mode | | | S | | +| | | | | | | | | +| | 0 | | 0 | | 0 | 1 | | +| | | | | | | | | +| | 0 | | 0 | | 0 | 1 | | +| | | | | | | | | +| | CRC | | | | | | | +| +---+---+---+---+---+---+---+ | | | | | | | | + +set to 0x4 (indicates that feedback data above is set to 0x0 (means ACK)) + +- Mode is set to 0x2 (means O-mode) + +- SN is set to 0x000 +- CRC is the 8-bit CRC computed over the entire feedback payload including any CID fields but excluding the packet type, the 'Size' field and the 'Code' octet, using the polynomial defined in [8], [10]. + +NOTE: If compressor uses CID field in compressed packet, the CID field should be included in the feedback packet and the Code and CID should be set as defined in [8]. + +#### A.2.1.3 Test requirement + +**Table A.2.1.3: Test Requirement for Test 1a** + +| | Average Compressed Header Size, IPv4 | Average Compressed Header size, IPv6 | +|-----------|--------------------------------------|--------------------------------------| +| SN <= N-1 | 44 octets | 68 octets | +| SN >= N | 5 octets | 5 octets | + +N is smaller than 8. + +The sequence of expected compressed headers can be illustrated as follow (informative): + +![Figure A.2.1.3: Expected outcome for Test 1a. A graph showing Header Size (octets) on the Y-axis versus RTP SN on the X-axis. The Y-axis has labels IR, IR-DYN, and 5. The X-axis has labels 0, N-1, 5, 6, and 69. The graph shows a step function: from SN 0 to N-1, the header size is IR; at SN N-1, it drops to 5; it remains at 5 until SN 69. A vertical arrow labeled 'Feedback-2 (ACK, mode=0x2, SN=0x000)' points to the 5 octet level between SN 5 and 6.](f3c5e85b70f94b9c3c521f594d69539f_img.jpg) + +Figure A.2.1.3: Expected outcome for Test 1a. A graph showing Header Size (octets) on the Y-axis versus RTP SN on the X-axis. The Y-axis has labels IR, IR-DYN, and 5. The X-axis has labels 0, N-1, 5, 6, and 69. The graph shows a step function: from SN 0 to N-1, the header size is IR; at SN N-1, it drops to 5; it remains at 5 until SN 69. A vertical arrow labeled 'Feedback-2 (ACK, mode=0x2, SN=0x000)' points to the 5 octet level between SN 5 and 6. + +**Figure A.2.1.3: Expected outcome for Test 1a** + +### A.2.2 Test 1b - Base test of ROHC RTP R-mode compressor + +#### A.2.2.1 Test purpose + +The purpose of the base test case is to verify that the compressor properly implements compression for a well-behaved IP/UDP/RTP packet flow, i.e. that it makes use of efficient compressed packet formats available to ROHC RTP [8] when operating in R-mode. + +#### A.2.2.2 Sequence details + +A sequence consisting of 70 packets in total is used where all header fields are set according to the basic test packet structure, as described in subclause A.3, with addition of the following: + +1. The RTP Sequence Number is a linearly increasing counter with a packet-to-packet delta of 1, set to 0x0000 for the first packet and thus ending with 0x0045 (69) in the last packet of the sequence +2. The RTP Time Stamp is a linearly increasing counter with a packet-to-packet delta of 160, set to 0x00000000 for the first packet and thus ending with 0x00002B20 (11040) in the last packet of the sequence. +3. The IP Identification is set to the same value as the RTP Sequence Number; this means that for IPv4 the IP-ID behaviour is not random, thus value(RND)=0 defined in [8] for both IPv4 and IPv6. + +Between the 6th and 7th (SN=5 and SN=6) packets of the sequence, the first ROHC feedback packet of feedback type 2 is to be given to the ROHC compressor to initiate transition to R-mode operation. The format of that packet is as follows: + +![](744acfe8d4e31bcf03f95714c2f6e567_img.jpg) + +``` + + 0 1 2 3 4 5 6 7 + +---+---+---+---+---+---+---+ + | 1 1 1 1 0 | Code | feedback type octet + +---+---+---+---+---+---+---+ + |-----ode | SN | + +---+---+---+---+---+---+---+ + | +---+---+---+---+---+---+ + | 0 0 0 - - - - - - - - - + | CRC - - - - - - - - + +``` + +Where: + +- Code is set to 0x4 (indicate octet is 4 octets) +- Acktype is set to 0x0 (as R-mode) +- SN is set to 0x000 +- CRC is the 8-bit CRC computed over the entire feedback payload including any CID fields but excluding the packet type, the 'Size' field and the 'Code' octet, using the polynomial defined in [8], [10]. + +The test equipment waits for a UOR-2, IR-DYN or IR packet from the RoHC compressor with the mode transition parameter set to R. The value of x is the RTP SN of this received packet for which the test equipment generates the second feedback packet of type 2, as described in subclause A.1.4. + +#### A.2.2.3 Test requirement + +**Table A.2.2.3: Test Requirement for Test 1b** + +| | Average Compressed Header Size, IPv4 | Average Compressed Header size, IPv6 | +|---------------------------|--------------------------------------|--------------------------------------| +| SN <= N-1 | 44 octets | 68 octets | +| N <= SN <= 5 | 5 octets | 5 octets | +| 6 <= SN <= x | 9 octets | 9 octets | +| SN >= x+1 | 5 octets | 5 octets | + +The sequence of expected compressed headers can be illustrated as follows (informative): + +![Figure A.2.2.3: Expected outcome for Test 1b. A graph showing Header Size (octets) on the Y-axis versus RTP SN on the X-axis. The Y-axis has labels for IR, IR-DYN, 9, and 5. The X-axis has labels for 0, N-1, 5, 6, x, x+1, and 69. The graph shows a step function: from SN=0 to SN=N-1, the header size is IR; from SN=N-1 to SN=5, the header size is 5 octets; from SN=6 to SN=x, the header size is 9 octets; from SN=x+1 to SN=69, the header size is 5 octets. Two feedback packets are indicated: 'Feedback-2 (ACK, mode=0x3, SN=0x000)' at SN=5 and 'Feedback-2 (ACK, mode=0x3, SN=x)' at SN=x.](41eb258722adc992426b1ae707f4a2cb_img.jpg) + +Figure A.2.2.3: Expected outcome for Test 1b. A graph showing Header Size (octets) on the Y-axis versus RTP SN on the X-axis. The Y-axis has labels for IR, IR-DYN, 9, and 5. The X-axis has labels for 0, N-1, 5, 6, x, x+1, and 69. The graph shows a step function: from SN=0 to SN=N-1, the header size is IR; from SN=N-1 to SN=5, the header size is 5 octets; from SN=6 to SN=x, the header size is 9 octets; from SN=x+1 to SN=69, the header size is 5 octets. Two feedback packets are indicated: 'Feedback-2 (ACK, mode=0x3, SN=0x000)' at SN=5 and 'Feedback-2 (ACK, mode=0x3, SN=x)' at SN=x. + +**Figure A.2.2.3: Expected outcome for Test 1b** + +### A.2.3 Void + +A.2.3.1 Void + +A.2.3.2 Void + +A.2.3.3 Void + +### A.2.4 Void + +A.2.4.1 Void + +A.2.4.2 Void + +A.2.4.3 Void + +### A.2.5 Test 3a - Re-establishment of TS function after DTX in O-mode + +#### A.2.5.1 Test purpose + +The purpose of the TS re-establishment test case is to verify that the compressor re-establishes the proper TS value after a DTX period, i.e. that it use efficient header formats available to ROHC RTP [8] when operating in O-mode. + +#### A.2.5.2 Sequence details + +The test sequence is the same as in subclause A.2.1, with the following exception: + +1. The RTP Time Stamp is a linearly increasing counter with a packet-to-packet delta of 160, set to 0x00000000 for the first packet. +2. For packet with SN = 20, TS is increased to represent a 32 (0.64 seconds) packet skip (32x160) and is thus set to $(20+32)\times 160=8320$ (0x00002080). Then TS continues to grow as stated in 1 above. +3. For packet with SN = 30, TS is increased to represent a 128 (2.56 seconds) packet skip (128x160) and is thus set to $(30+32+128)\times 160=30400$ (0x000076C0). Then TS continues to grow as stated in 1 above. +4. For packet with SN = 40, TS is increased to represent a 2048 (40.96 seconds) packet skip (2048x160) and is thus set to $(40+32+128+2048)\times 160=359680$ (0x00057D00). Then TS continues to grow as stated in 1 above. +5. TS thus ends at 364320 (0x00058F20) in the last packet of the sequence with RTP sequence number 69. + +#### A.2.5.3 Test requirement + +**Table A.2.5.3: Test Requirement for Test 3a** + +| | Average Compressed Header Size, IPv4 | Average Compressed Header size, IPv6 | +|---------------------------------|--------------------------------------|--------------------------------------| +| SN <= 19 | See Test 1a | | +| 20 <= SN <= 19 + N | 10 octets | 10 octets | +| 30 <= SN <= 29 + N | 10 octets | 10 octets | +| 40 <= SN <= 39 + N | 10 octets | 10 octets | +| Other SN values | 5 octets | 5 octets | + +The sequence of expected compressed headers can be illustrated as follow (informative): + +![Figure A.2.5.3: Expected outcome for Test 3a. A graph showing Header Size (octets) on the Y-axis (0 to 10) versus RTP SN on the X-axis (0 to 69). The graph shows a step function representing header sizes. The first segment (SN 0 to 20) is labeled 'See Test 1a' and has a height of 10 octets. At SN 20, there is a 'TS jump(deltaTS=32x160)' indicated by an arrow. The next segment (SN 20 to 30) has a height of 5 octets. At SN 30, there is a 'TS jump(deltaTS=128x160)' indicated by an arrow. The next segment (SN 30 to 40) has a height of 10 octets. At SN 40, there is a 'TS jump(deltaTS=2048x160)' indicated by an arrow. The final segment (SN 40 to 69) has a height of 5 octets. The X-axis is marked at 0, 20, 20+N, 30, 30+N, 40, 40+N, and 69. The Y-axis is marked at 0, 5, 10, and has labels IR and IR-DYN.](853ef5420f0432e626e83987e3f38a0b_img.jpg) + +Figure A.2.5.3: Expected outcome for Test 3a. A graph showing Header Size (octets) on the Y-axis (0 to 10) versus RTP SN on the X-axis (0 to 69). The graph shows a step function representing header sizes. The first segment (SN 0 to 20) is labeled 'See Test 1a' and has a height of 10 octets. At SN 20, there is a 'TS jump(deltaTS=32x160)' indicated by an arrow. The next segment (SN 20 to 30) has a height of 5 octets. At SN 30, there is a 'TS jump(deltaTS=128x160)' indicated by an arrow. The next segment (SN 30 to 40) has a height of 10 octets. At SN 40, there is a 'TS jump(deltaTS=2048x160)' indicated by an arrow. The final segment (SN 40 to 69) has a height of 5 octets. The X-axis is marked at 0, 20, 20+N, 30, 30+N, 40, 40+N, and 69. The Y-axis is marked at 0, 5, 10, and has labels IR and IR-DYN. + +Figure A.2.5.3: Expected outcome for Test 3a + +### A.2.6 Test 3b - Re-establishment of TS function after DTX in R-mode + +#### A.2.6.1 Test purpose + +The purpose of the TS re-establish test case is to verify that the compressor re-establishes the proper TS value after a DTX period, i.e. that it use the efficient header formats available to ROHC RTP [8] when operating in R-mode. + +#### A.2.6.2 Sequence details + +The test sequence is the same as in subclause A.2.2, with the following exception: + +1. The RTP Time Stamp is a linearly increasing counter with a packet-to-packet delta of 160, set to 0x00000000 for the first packet. +2. For packet with SN = 20, TS is increased to represent a 32 (0.64 seconds) packet skip ( $32 \times 160$ ) and is thus set to $(20+32) \times 160 = 8320$ (0x00002080). Then TS continues to grow as stated in 1 above. +3. For packet with SN = 30, TS is increased to represent a 128 (2.56 seconds) packet skip ( $128 \times 160$ ) and is thus set to $(30+32+128) \times 160 = 30400$ (0x000076C0). Then TS continues to grow as stated in 1 above. +4. For packet with SN = 40, TS is increased to represent a 2048 (40.96 seconds) packet skip ( $2048 \times 160$ ) and is thus set to $(40+32+128+2048) \times 160 = 359680$ (0x00057D00). Then TS continues to grow as stated in 1 above. +5. TS thus ends at 393120 (0x0005FFA0) in the last packet of the sequence with RTP sequence number 69. + +#### A.2.6.3 Test requirement + +Table A.2.6.3: Test Requirement for Test 3b + +| | Average Compressed Header Size, IPv4 | Average Compressed Header size, IPv6 | +|---------------------------------|--------------------------------------|--------------------------------------| +| SN <= 19 | See Test 1b | | +| 20 <= SN <= 19 + x | 10 octets | 10 octets | +| 30 <= SN <= 29 + x | 10 octets | 10 octets | +| 40 <= SN <= 39 + x | 10 octets | 10 octets | +| Other SN values | 5 octets | 5 octets | + +The sequence of expected compressed headers can be illustrated as follow (informative): + +![Figure A.2.6.3: Expected outcome for Test 3b. A graph showing Header Size (octets) on the Y-axis (values 5, 10, IR, IR-DYN) versus RTP SN on the X-axis (values 0, 20, 20+x, 30, 30+x, 40, 40+x, 69). The graph shows a step function representing header sizes. The first segment (SN 0 to 20) has a header size of IR. At SN 20, there is a 'TS jump(deltaTS=32x160)' indicated by an arrow. The next segment (SN 20 to 30) has a header size of 10. At SN 30, there is a 'TS jump(deltaTS=128x160)' indicated by an arrow. The next segment (SN 30 to 40) has a header size of 10. At SN 40, there is a 'TS jump(deltaTS=2048x160)' indicated by an arrow. The final segment (SN 40 to 69) has a header size of 5. A shaded box from SN 0 to 20 contains the text 'See Test 1b'.](051638d871c75230edb3d005fa668810_img.jpg) + +Figure A.2.6.3: Expected outcome for Test 3b. A graph showing Header Size (octets) on the Y-axis (values 5, 10, IR, IR-DYN) versus RTP SN on the X-axis (values 0, 20, 20+x, 30, 30+x, 40, 40+x, 69). The graph shows a step function representing header sizes. The first segment (SN 0 to 20) has a header size of IR. At SN 20, there is a 'TS jump(deltaTS=32x160)' indicated by an arrow. The next segment (SN 20 to 30) has a header size of 10. At SN 30, there is a 'TS jump(deltaTS=128x160)' indicated by an arrow. The next segment (SN 30 to 40) has a header size of 10. At SN 40, there is a 'TS jump(deltaTS=2048x160)' indicated by an arrow. The final segment (SN 40 to 69) has a header size of 5. A shaded box from SN 0 to 20 contains the text 'See Test 1b'. + +**Figure A.2.6.3: Expected outcome for Test 3b** + +### A.2.7 Test 4a - Compressor response to single lost packets in O-mode + +#### A.2.7.1 Test purpose + +The purpose of this test is to verify that the compressor does not panic just because there is a single missing packet, i.e. the compressed packet size should not increase due to such events. + +#### A.2.7.2 Sequence details + +The test sequence is the same as in subclause A.2.1, with the following exception: + +- Packets with SN 20, 30, and 40 are removed from the sequence. + +#### A.2.7.3 Test requirement + +Maximal compressed header overhead for the test are the same as in A.2.1. + +### A.2.8 Test 4b - Compressor response to single lost packets in R-mode + +#### A.2.8.1 Test purpose + +The purpose of this test is to verify that the compressor does not panic just because there is a single missing packet, i.e. the compressed packet size should not increase due to such events. + +#### A.2.8.2 Sequence details + +The test sequence is the same as in subclause A.2.2, with the following exception: + +- Packets with SN 20, 30, and 40 are removed from the sequence. + +#### A.2.8.3 Test requirement + +Maximal compressed header overhead for the test are the same as in A.2.2. + +### A.2.9 Void + +A.2.9.1 Void + +A.2.9.2 Void + +A.2.9.3 Void + +### A.2.10 Void + +A.2.10.1 Void + +A.2.10.2 Void + +A.2.10.3 Void + +### A.2.11 Test 6a - TS function during DTX with varying delta in O-mode + +#### A.2.11.1 Test purpose + +The purpose of this test case is to verify that the compressor properly handles variations in the function between the TS value and the SN during and after a DTX period, during which SID packets are sent periodically, i.e. that it uses efficient header formats available to ROHC RTP [8] when operating in O-mode. + +#### A.2.11.2 Sequence details + +The test sequence is the same as in subclause A.2.1, with the following exception: + +1. The RTP Time Stamp is a linearly increasing counter with a packet-to-packet delta of 160, set to 0x00000000 for the first packet. +2. For packets SN = 20, 21 and 22, TS is increased to represent a 7 (0.14 seconds) packet skip (7x160) and is thus set to $(20+7) \times 160 = 4320$ (0x000010E0), $(21+7+7) \times 160 = 5600$ (0x000015E0) and $(22+7+7+7) \times 160 = 6880$ (0x00001AE0), respectively. +3. For packets SN = 30, 31, 32, 33 and 34, TS is increased to represent a 7 (0.14 seconds) packet skip (7x160) and is thus set to 9280 (0x00002440), 10560 (0x00002940), 11840 (0x00002E40), 13120 (0x00003340) and 14400 (0x00003840) respectively. +4. For packets SN = 40, 41, 42, 43, 44, 45, and 46, TS is increased to represent a 7 (0.14 seconds) packet skip (7x160) and is thus set to 16480 (0x00004060), 17760 (0x00004560), 19040 (0x00004A60), 20320 (0x00004F60), 21600 (0x00005460), 22880 (0x00005960) and 24160 (0x00005E60) respectively. +5. TS thus ends at 27840 (0x00006CC0) in the last packet of the sequence with RTP sequence number 69. + +#### A.2.11.3 Test requirement + +**Table A.2.11.3: Test Requirement for Test 6a** + +| | Average Compressed Header Size, IPv4 | Average Compressed Header size, IPv6 | +|-------------------------------------------------------------------------------------------------------|--------------------------------------|--------------------------------------| +| SN <= 19 | See Test 1a | | +| 20 <= SN <= 22 + N
30 <= SN <= 34 + N
40 <= SN <= 46 + N | 15 octets | 15 octets | +| Other SN values | 5 octets | 5 octets | + +The sequence of expected compressed headers can be illustrated as follow (informative): + +![Figure A.2.11.3: Expected outcome for Test 6a. A graph showing Header Size (octets) on the Y-axis (values 5, 16, IR, IR-DYN) versus RTP SN on the X-axis (values 0 to 69). The graph shows three groups of packets with varying header sizes. The first group (SN 0-19) has a header size of 16 octets, labeled 'See Test 1a'. The second group (SN 20-34) has a header size of 5 octets. The third group (SN 30-46) has a header size of 16 octets. The fourth group (SN 40-69) has a header size of 5 octets. Arrows labeled 'TS jump(deltaTS=7x160)' point to the transitions between header sizes at SN 20, 30, and 40.](8f38356601e137ac471fc4771b9c5a5c_img.jpg) + +Figure A.2.11.3: Expected outcome for Test 6a. A graph showing Header Size (octets) on the Y-axis (values 5, 16, IR, IR-DYN) versus RTP SN on the X-axis (values 0 to 69). The graph shows three groups of packets with varying header sizes. The first group (SN 0-19) has a header size of 16 octets, labeled 'See Test 1a'. The second group (SN 20-34) has a header size of 5 octets. The third group (SN 30-46) has a header size of 16 octets. The fourth group (SN 40-69) has a header size of 5 octets. Arrows labeled 'TS jump(deltaTS=7x160)' point to the transitions between header sizes at SN 20, 30, and 40. + +Figure A.2.11.3: Expected outcome for Test 6a + +### A.2.12 Test 6b - TS function during DTX with varying delta in R-mode + +#### A.2.12.1 Test purpose + +The purpose of this test case is to verify how efficiently the compressor handles variations in the function between the TS value and the SN during and after a DTX period, during which SID packets are sent periodically, i.e. that it uses the efficient header formats available to ROHC RTP [8] when operating in R-mode. + +#### A.2.12.2 Sequence details + +The test sequence is the same as in subclause A.2.2, with the following exception: + +1. The RTP Time Stamp is a linearly increasing counter with a packet-to-packet delta of 160, set to 0x00000000 for the first packet. +2. For packets SN = 20, 21 and 22, TS is increased to represent a 7 (0.14 seconds) packet skip ( $7 \times 160$ ) and is thus set to $(20+7) \times 160 = 4320$ (0x000010E0), $(21+7+7) \times 160 = 5600$ (0x000015E0) and $(22+7+7+7) \times 160 = 6880$ (0x00001AE0), respectively. +3. For packets SN = 30, 31, 32, 33 and 34, TS is increased to represent a 7 (0.14 seconds) packet skip ( $7 \times 160$ ) and is thus set to 9280 (0x00002440), 10560 (0x00002940), 11840 (0x00002E40), 13120 (0x00003340) and 14400 (0x00003840) respectively. +4. For packets SN = 40, 41, 42, 43, 44, 45, and 46, TS is increased to represent a 7 (0.14 seconds) packet skip ( $7 \times 160$ ) and is thus set to 16480 (0x00004060), 17760 (0x00004560), 19040 (0x00004A60), 20320 (0x00004F60), 21600 (0x00005460), 22880 (0x00005960) and 24160 (0x00005E60) respectively. +5. TS thus ends at 27840 (0x00006CC0) in the last packet of the sequence with RTP sequence number 69. + +#### A.2.12.3 Test requirement + +Table A.2.12.3: Test Requirement for Test 6b + +| | Average Compressed Header Size, IPv4 | Average Compressed Header size, IPv6 | +|----------------------------------------------------------------|--------------------------------------|--------------------------------------| +| SN <= 19 | See Test 1b | | +| 20 <= SN <= 22 + x
30 <= SN <= 34 + x
40 <= SN <= 46 + x | 15 octets | 15 octets | +| Other SN values | 5 octets | 5 octets | + +The sequence of expected compressed headers can be illustrated as follow (informative): + +![Figure A.2.12.3: Expected outcome for Test 6b. This is a graph showing Header Size (octets) on the Y-axis versus RTP SN on the X-axis. The Y-axis has labels for IR, IR-DYN, 16, and 5. The X-axis has labels for 0, 20, 21, 22, 22+x, 30, 31, 32, 33, 34, 34+x, 40, 41, 42, 43, 44, 45, 46, 46+x, and 69. The graph shows a series of steps representing header sizes. The first step is a shaded box labeled 'See Test 1b' with a height of 16 octets, spanning from SN 0 to 20. Subsequent steps have a height of 5 octets. There are three 'TS jump(deltaTS=7x160)' labels with arrows pointing to the start of the 5-octet steps at SN 22, 32, and 42. The steps continue until SN 69.](c53adc66eab40abd5f8b9107d950ad04_img.jpg) + +Figure A.2.12.3: Expected outcome for Test 6b. This is a graph showing Header Size (octets) on the Y-axis versus RTP SN on the X-axis. The Y-axis has labels for IR, IR-DYN, 16, and 5. The X-axis has labels for 0, 20, 21, 22, 22+x, 30, 31, 32, 33, 34, 34+x, 40, 41, 42, 43, 44, 45, 46, 46+x, and 69. The graph shows a series of steps representing header sizes. The first step is a shaded box labeled 'See Test 1b' with a height of 16 octets, spanning from SN 0 to 20. Subsequent steps have a height of 5 octets. There are three 'TS jump(deltaTS=7x160)' labels with arrows pointing to the start of the 5-octet steps at SN 22, 32, and 42. The steps continue until SN 69. + +Figure A.2.12.3: Expected outcome for Test 6b + +### A.2.13 Test 7a – SRNS relocation in O-mode + +#### A.2.13.1 Test purpose + +This test applies to UEs supporting header compression context relocation from Rel-5 onwards. + +The purpose of this test case is to verify that the compressor does not interrupt efficient header compression upon reception of the indication about SRNS relocation being performed, i.e. that it makes use of efficient compressed packet formats available to ROHC RTP [8] when operating in O-mode when data transmission is resumed after SRNS relocation. + +Continuation of efficient header compression upon reception of the indication about SRNS relocation being performed is possible according to subclause 5.4.2, i.e. the compressor shall compress and transmit uplink data as specified in [8] using the assumption that all ROHC uplink packets transmitted are likely to be lost. + +#### A.2.13.2 Sequence details + +The test sequence is the same as in subclause A.2.1, with the following exception: + +Packets with SN = 10 to SN = 59 are removed from the sequence. + +SRNS relocation occurs between packet with SN = 9 and packet with SN = 60, thus simulating a 1s long SRNS relocation that affects compression of the IP/UDP/RTP packet flow. + +NOTE: The operation of the ROHC compressor is not affected by the time interval between packets with SN = 9 and SN = 60 (timer-based compression is not allowed because no appropriate feedback is provided). + +#### A.2.13.3 Test requirement + +Table A.2.13.3: Test Requirement for Test 7a + +| | Average Compressed Header Size, IPv4 | Average Compressed Header size, IPv6 | +|------------------|--------------------------------------|--------------------------------------| +| SN <= N-1 | 44 octets | 68 octets | +| N <= SN <= 9 | 5 octets | 5 octets | +| 60 <= SN <= 59+N | 8 octets | 8 octets | +| SN >= 60+N | 5 octets | 5 octets | + +N is smaller than 8. The sequence of expected compressed headers can be illustrated as follow (informative): + +![A graph showing Header Size (octets) on the y-axis and RTP SN on the x-axis. The y-axis has labels IR, IR-DYN, 8, and 5. The x-axis has labels 0, N, 7, 8, 9, 60, 60 + N, and 69. A vertical arrow labeled 'Feedback(ACK, mode=0x2, SN=0x000)' points down at x=7. A horizontal double-headed arrow labeled 'SRNS relocation' spans from x=9 to x=60. The header size is IR from x=0 to x=N, 5 from x=N to x=9, 8 from x=60 to x=60+N, and 5 from x=60+N to x=69.](bf30e154f82662d212f21fccdfa2980f_img.jpg) + +A graph showing Header Size (octets) on the y-axis and RTP SN on the x-axis. The y-axis has labels IR, IR-DYN, 8, and 5. The x-axis has labels 0, N, 7, 8, 9, 60, 60 + N, and 69. A vertical arrow labeled 'Feedback(ACK, mode=0x2, SN=0x000)' points down at x=7. A horizontal double-headed arrow labeled 'SRNS relocation' spans from x=9 to x=60. The header size is IR from x=0 to x=N, 5 from x=N to x=9, 8 from x=60 to x=60+N, and 5 from x=60+N to x=69. + +Figure A.2.13.3: Expected outcome for Test 7a + +## A.3 Test packet structures + +IPv6/UDP/RTP + +![](382a9c9e4816bd229191ab4591424dd8_img.jpg) + +``` + + 0 1 2 3 + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + |Version| Traffic Class | Flow Label | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Payload Length | Next Header | Hop Limit | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | | + + + + | | + + Source Address + + | | + + + + | | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | | + + + + | | + + Destination Address + + | | + + + + | | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Source Port | Destination Port | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Length | Checksum | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + |V=2|P|X| CC |M| PT | sequence number | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | timestamp | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | synchronization source (SSRC) identifier | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +``` + +IPv4/UDP/RTP + +![](896e86ed12aff206d302c64f2e3091fa_img.jpg) + +``` + + 0 1 2 3 + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + |Version| IHL |Type of Service| Total Length | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Identification |R|D|F| Fragment Offset | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Time to Live | Protocol | Header Checksum | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Source Address | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Destination Address | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Options | Padding | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Source Port | Destination Port | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Length | Checksum | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + |V=2|P|X| CC |M| PT | sequence number | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | timestamp | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +``` + +``` + +| synchronization source (SSRC) identifier | ++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +``` + +### IPv6 header fields + +| Field | Size (bits) | Value | +|---------------------|-------------|----------------| +| Traffic Class | 8 | 0x6 | +| Payload Length | 16 | 0x00000 | +| Next Header | 8 | 0x0034 | +| Hop Limit | 8 | 0x11 | +| Source Address | 128 | Test dependent | +| Destination Address | 128 | ANY | + +### IPv4 header fields + +| Field | Size (bits) | Value | +|---------------------|-------------|----------------| +| Header Length (IHL) | 4 | 0x5 | +| Packet Length | 16 | 0x0048 | +| Identification | 16 | Test dependent | +| Reserved flag (R) | 1 | 0x0 | +| Don't Fragment (D) | 1 | 0x1 | +| More Fragments (F) | 1 | 0x0 | +| Fragment Offset | 13 | 0x0000 | +| Time To Live | 8 | Test dependent | +| Protocol | 8 | 0x11 | +| Header Checksum | 16 | See RFC 791 | +| Source Address | 32 | ANY | +| Destination Address | 32 | ANY | + +### UDP header fields + +| Field | Size (bits) | Value | +|------------------|-------------|-------------| +| Destination Port | 16 | ANY | +| Checksum | 16 | See RFC 768 | + +### RTP header fields + +| Field | Size (bits) | Value | +|-------------------|-------------|----------------| +| Version (V) | 2 | 0x2 | +| Padding (P) | 1 | 0x0 | +| Extension (X) | 1 | 0x0 | +| CSRC Counter (CC) | 4 | 0x0 | +| Marker (M) | 1 | 0x0 | +| Payload Type (PT) | 7 | 0x60 | +| Sequence Number | 16 | Test dependent | +| Timestamp | 32 | Test dependent | +| SSRC | 32 | ANY | + +# Annex B (informative): Reference model for generating ROHC performance requirements + +## B.1 Introduction + +ROHC compressor and de-compressor may use a set of parameters in order to operate (e.g. L confidence parameter, dynamic FOTimer and static IRTimer, K1 out of N1, K2 out of N2...) that may be optimised for a given application (e.g. Voice over IP, Videotelephony over IP, Interactive Gaming over IP...). + +NOTE: L confidence parameter allows setting the number of times an IR or IR-Dyn packet is transmitted and FOTimer and IRTimer are used in order to determine when a transition to a lower compressor state is necessary: The dynamic timer FOTimer triggers SO state to FO state transition and the static IRTimer triggers SO/FO state to IR state transition. + +## B.2 For Voice over IP (VoIP) optimisation + +### B.2.1 ROHC parameters optimisations for VoIP + +For the support of VoIP in UTRAN, ROHC compressor and de-compressor parameter values (L confidence parameter, dynamic FOTimer and static IRTimer, K1 out of N1, K2 out of N2) may be used. Values used in ROHC reference model are given in annex B.2.2 for O-mode. + +- The initialisation phase duration; +- The reaction delay to decompression failure; +- The header compression ratio (compressed header size / uncompressed header size); +- The error rates (in UDP and PDCP layers); +- The amount of transferred data (including ROHC compressed packets and feedbacks); +- The resource usage (transport block occupancy in the RLC layer). + +### B.2.2 Parameter setting for ROHC reference model for VoIP + +The following parameters setting is applied in the reference model for ROHC performance tests of VoIP application: + +**Table B.2.2: ROHC parameters setting for VoIP** + +| ROHC parameter | O-mode | +|----------------|-------------| +| L | 2 | +| FOTimer | 0.12 second | +| IRTimer | 0.12 second | +| K1 / N1 | 2 / 20 | +| K2 / N2 | 1 / 1 | + +### B.2.3 Setting the parameter value N in test cases for VoIP + +In test cases for VoIP to evaluate ROHC Compression performance for both O- and R-mode, the parameter N (defined in Annex A) is set to 4. + +# Annex C (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-----|-----|---------------------------------------------------------------------------------------------------------------------|-------------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New version | +| 12/1999 | RP-06 | RP-99645 | - | | | Approved at TSG-RAN #6 and placed under Change Control | 3.0.0 | +| 03/2000 | RP-07 | RP-000041 | 004 | | | Bit order of PDCP PDUs | 3.1.0 | +| | RP-07 | RP-000041 | 005 | | | Changes to PDCP | 3.1.0 | +| 06/2000 | RP-08 | RP-000221 | 006 | 4 | | Changes in PDCP PDU format due to PDCP sequence numbering | 3.2.0 | +| 09/2000 | RP-09 | RP-000359 | 009 | 3 | | Clarification of PDCP Sequence Numbering | 3.2.0 | +| | RP-09 | RP-000359 | 011 | | | Clarification on how to handle invalid PDUs | 3.3.0 | +| | RP-09 | RP-000359 | 012 | 2 | | Primitives required for SRNS relocation | 3.3.0 | +| | RP-09 | RP-000359 | 015 | | | Handling of invalid PDCP PDU sequence number | 3.3.0 | +| 03/2001 | RP-11 | RP-010027 | 018 | 1 | | Editorial Corrections | 3.4.0 | +| | RP-11 | RP-010027 | 019 | 1 | | Updates necessary for Rel-4 specification | 3.4.0 | +| | RP-11 | RP-010039 | 017 | 2 | | Robust Header Compression | 4.0.0 | +| 06/2001 | RP-12 | RP-010310 | 021 | | | Clarification on PDCP Sequence numbering | 4.1.0 | +| 09/2001 | RP-13 | RP-010543 | 028 | | | Header compression protocol reinitialisation during SRNS relocation | 4.2.0 | +| | RP-13 | RP-010543 | 030 | | | PDCP SDU Sequence Numbering | 4.2.0 | +| | RP-13 | RP-010543 | 036 | | | Corrections to PDCP | 4.2.0 | +| | RP-13 | RP-010553 | 026 | | | Selection of the RFC 3095 CID transmission | 4.2.0 | +| 12/2001 | RP-14 | RP-010762 | 038 | | | General PDCP corrections | 4.3.0 | +| | RP-14 | RP-010772 | 039 | | | Management of Full Header transmission | 4.3.0 | +| 03/2002 | RP-15 | RP-020069 | 043 | | | Clarification on PDCP sequence numbering | 4.4.0 | +| | RP-15 | - | - | | | Upgrade to Release 5 - no technical change | 5.0.0 | +| 06/2002 | RP-16 | RP-020328 | 049 | | | Clarification on PDCP sequence number synchronization procedure | 5.1.0 | +| | RP-16 | RP-020345 | 050 | | | RFC 3095 context relocation | 5.1.0 | +| 09/2002 | RP-17 | RP-020540 | 053 | | | Mapping relation between PDCP and RLC | 5.2.0 | +| | RP-17 | RP-020552 | 055 | | | Corrections to RFC3095 operation | 5.2.0 | +| | RP-17 | RP-020552 | 057 | | | Mismatches between Rel-4 and R'99 in PDCP | 5.2.0 | +| 12/2003 | RP-22 | - | - | | | Upgrade to Release 6 - no technical changes | 6.0.0 | +| 03/2005 | RP-27 | RP-050067 | 059 | 2 | | Lossless DL RLC PDU size change | 6.1.0 | +| 06/2005 | RP-28 | RP-050315 | 060 | 1 | | Introduction of MBMS | 6.2.0 | +| | RP-28 | RP-050303 | 062 | 2 | | Target mode for ROHC operation | 6.2.0 | +| | RP-28 | RP-050303 | 064 | | | Performance testing of ROHC | 6.2.0 | +| 09/2005 | RP-29 | RP-050468 | 065 | | | Correction of MBMS header compression | 6.3.0 | +| 12/2005 | RP-30 | RP-050784 | 067 | 1 | | Correction of the ROHC context relocation procedure | 6.4.0 | +| 03/2006 | RP-31 | RP-060083 | 069 | | | Reference model for generating ROHC performance requirements | 6.5.0 | +| | RP-31 | - | - | | | Upgrade to Release 7 - no technical changes | 7.0.0 | +| 06/2006 | RP-32 | RP-060374 | 0072 | 1 | | RoHC Segmentation, padding and Packet_sizes_allowed parameter removal | 7.1.0 | +| | RP-32 | RP-060374 | 0075 | | | Removal of unnecessary ROHC test cases | 7.1.0 | +| | RP-32 | RP-060374 | 0078 | | | Introduction of ROHC test requirements | 7.1.0 | +| 09/2006 | RP-33 | RP-060573 | 0081 | | | Removal of CID indication in PDCP PID | 7.2.0 | +| 12/2006 | RP-34 | RP-060717 | 0296 | 1 | | Correction of feedback format for ROHC performance testing | 7.3.0 | +| | RP-34 | RP-060717 | 0299 | 1 | | Correction on acceptable configurations for compression entities | 7.3.0 | +| 03/2007 | RP-35 | RP-070149 | 0301 | | | Introduction of new test for O-mode including test requirement in case SRNS relocation for ROHC performance testing | 7.4.0 | +| 06/2007 | RP-36 | RP-070407 | 0302 | | | PDCP reinitialisation at SRNS relocation | 7.5.0 | +| | RP-36 | RP-070406 | 0304 | | | Update of normative references for Robust Header Compression (RFC3095) | 7.5.0 | +| 09/2007 | RP-37 | | | | | Incorrect reference to RFC number for Header Compression packet formats | 7.6.0 | +| | RP-37 | RP-070636 | 0305 | | | Correction for configuration of RFC3095 header compression | 7.6.0 | +| 12/2007 | RP-38 | RP-070893 | 0309 | | | Clarification on RoHC Performance Testing | 7.7.0 | +| | RP-38 | RP-070910 | 0310 | | | Introduction of CS voice over HSPA | 8.0.0 | +| 03/2008 | RP-39 | RP-080201 | 0311 | 1 | | CS-HSPA UL AMR Rate and maximum jitter time | 8.1.0 | +| 09/2008 | RP-41 | RP-080687 | 0312 | | | Clarification of the CS counter handling | 8.2.0 | +| 12/2008 | RP-42 | RP-081012 | 0313 | 1 | | Delivery of CS Counter | 8.3.0 | +| 03/2009 | RP-43 | RP-090140 | 0314 | | | Coding of the PDCP AMR Data PDU payload | 8.4.0 | +| | RP-43 | RP-090140 | 0315 | 1 | | Condition to identify a CS-HSPA configuration | 8.4.0 | +| 06/2009 | | | | | | Corrects Release shown on cover | 8.4.1 | +| 07/2009 | | | | | | Corrects file properties. Adds previous line in this history table (and this one!). | 8.4.2 | +| 12/2009 | RP-46 | RP-091328 | 0317 | 2 | | UM RLC ciphering error detection and recovery | 8.5.0 | +| 12/2009 | RP-46 | - | - | - | | Upgrade to the Release 9 - no technical change | 9.0.0 | +| 09/2010 | RP-49 | RP-100859 | 0320 | 1 | | Clarification on PDCP CID field (Rel-9) | 9.1.0 | +| 03/2011 | RP-51 | - | - | - | | Upgrade to the Release 10 - no technical change | 10.0.0 | +| 06/2011 | RP-52 | RP-110825 | 0323 | 1 | | Removing RoHC discrepancy | 10.1.0 | +| 09/2012 | RP-57 | - | - | - | | Upgrade to the Release 11 - no technical change | 11.0.0 | + +| | | | | | | | | +|---------|--------|---|---|---|---|----------------------------------------------------|--------| +| 09/2014 | RP-65 | - | - | - | | Upgrade to the Release 12 - no technical change | 12.0.0 | +| 12/2015 | RP-70 | - | - | - | | Upgrade to the Release 13 - no technical change | 13.0.0 | +| 03/2017 | RP-75 | - | - | - | | Upgrade to Release 14 - no technical change | 14.0.0 | +| 06/2018 | RP-80 | | | | | Upgrade to Release 15 - no technical change | 15.0.0 | +| 2020-07 | RP-88e | - | - | - | - | Upgrade to Rel-16 version without technical change | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25324/a7c51c18111139f9aca2805114108565_img.jpg b/marked/Rel-16/25_series/25324/a7c51c18111139f9aca2805114108565_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d402994403933e6ec9ad9c219e645191306ab62 --- /dev/null +++ b/marked/Rel-16/25_series/25324/a7c51c18111139f9aca2805114108565_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5da1cf3f6a6f9c20a03f1d4eacf6b449e8c23227818dc09d7cc6361a60b76f12 +size 9773 diff --git a/marked/Rel-16/25_series/25324/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/25_series/25324/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13cc87beead32e4e6949049b49f7bc4fca718820 --- /dev/null +++ b/marked/Rel-16/25_series/25324/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67ad795bfe48ac7148d4358d5873024aca9dc563e64cd4ba6cfe34f8d45e8b4b +size 52254 diff --git a/marked/Rel-16/25_series/25324/raw.md b/marked/Rel-16/25_series/25324/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..304d06ae96b6598d7c1918c86dc89ac5bf4c40fb --- /dev/null +++ b/marked/Rel-16/25_series/25324/raw.md @@ -0,0 +1,964 @@ + + + + + + +# Contents + +| | | +|-------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 7 | +| 4 General..... | 7 | +| 4.1 Model of BMC ..... | 7 | +| 5 Functions..... | 8 | +| 6 Services provided to Upper Layers..... | 8 | +| 7 Services expected from RLC ..... | 9 | +| 8 Elements for layer-to-layer communication ..... | 9 | +| 8.1 Service Primitives between RRC and BMC ..... | 9 | +| 8.1.1 Primitives..... | 9 | +| 8.1.1.1 CBMC-Measurement-IND ..... | 9 | +| 8.1.1.2 CBMC-Rx-IND ..... | 9 | +| 8.1.1.3 CBMC-Config-REQ ..... | 10 | +| 8.1.2 Parameters ..... | 10 | +| 8.1.2.1 CB-Traffic-Volume ..... | 10 | +| 8.1.2.2 Action..... | 10 | +| 8.1.2.3 DRX selection..... | 10 | +| 8.1.2.4 CTCH configuration ..... | 10 | +| 8.2 Service Primitives between upper layer (U-plane) and BMC..... | 11 | +| 8.2.1 Primitives..... | 11 | +| 8.2.1.1 Primitives used in relation to UMTS Core Network ..... | 11 | +| 8.2.1.1.1 BMC-Data-REQ..... | 11 | +| 8.2.1.1.2 BMC-Data-IND..... | 12 | +| 8.2.1.1.3 BMC-Data-CNF ..... | 12 | +| 8.2.1.1.4 BMC-Congestion-IND ..... | 12 | +| 8.2.1.1.5 BMC-Normal-IND ..... | 12 | +| 8.2.1.1.6 BMC-Activation-REQ ..... | 12 | +| 8.2.1.1.7 BMC-Deactivation-REQ..... | 12 | +| 8.2.1.1.8 BMC-DRX-REQ..... | 13 | +| 8.2.1.1.9 BMC-Error-IND..... | 13 | +| 8.2.1.2 Primitives used for ANSI-41 Core Network..... | 13 | +| 8.2.1.2.1 BMC-Data41-REQ..... | 13 | +| 8.2.1.2.2 BMC-Data41-IND..... | 13 | +| 8.2.1.2.3 BMC-Error41-IND..... | 13 | +| 8.2.2 Parameters ..... | 14 | +| 8.2.2.1 Message-ID..... | 14 | +| 8.2.2.2 Serial Number ..... | 14 | +| 8.2.2.3 Data-Coding-Scheme..... | 14 | +| 8.2.2.4 CB-Data ..... | 14 | +| 8.2.2.5 Category..... | 14 | +| 8.2.2.6 Repetition-Period ..... | 14 | +| 8.2.2.7 Number-of-Broadcasts-Requested..... | 14 | +| 8.2.2.8 CB-DRX-Schedule-Period..... | 14 | +| 8.2.2.9 Reserved-CB-Capacity ..... | 15 | +| 8.2.2.10 Cause..... | 15 | +| 8.2.2.11 Transport Layer Message..... | 15 | +| 8.2.2.12 Broadcast Address ..... | 15 | +| 8.2.2.13 Error Type..... | 15 | + +| | | | +|------------------------|-------------------------------------------|----| +| 9 | Procedures..... | 15 | +| 9.1 | BMC Message Broadcast..... | 15 | +| 9.2 | Generation of Schedule message..... | 15 | +| 9.3 | Traffic volume measurement ..... | 16 | +| 9.4 | BMC message reception..... | 16 | +| 10 | BMC Messages ..... | 17 | +| 10.1 | General ..... | 17 | +| 10.2 | BMC CBS Message ..... | 17 | +| 10.3 | BMC Schedule Message ..... | 17 | +| 10.4 | BMC CBS41 Message ..... | 18 | +| 11 | Information Elements..... | 19 | +| 11.1 | Message Type..... | 19 | +| 11.2 | Message ID..... | 19 | +| 11.3 | Serial Number ..... | 19 | +| 11.4 | Data Coding Scheme..... | 20 | +| 11.5 | CB Data..... | 20 | +| 11.6 | Offset to Begin CTCH Block Set Index..... | 20 | +| 11.7 | Length of CBS Schedule Period..... | 21 | +| 11.8 | New Message Bitmap..... | 21 | +| 11.9 | Message Description ..... | 22 | +| 11.10 | Broadcast Address..... | 23 | +| 11.11 | CB Data41 ..... | 23 | +| 11.12 | CBS Schedule Message Extension..... | 24 | +| 11.13 | CBS Message Serial Numbers ..... | 24 | +| 11.14 | Serial Number List Entry ..... | 25 | +| Annex A (informative): | Change history..... | 26 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd 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 the description of the Broadcast/Multicast Control Protocol (BMC). This protocol adapts broadcast and multicast services on the radio interface. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TS 25.322: "RLC Protocol Specification". +- [2] 3GPP TS 25.301: "Radio Interface Protocol Architecture". +- [3] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)". +- [4] 3GPP TS 23.038: "Alphabets and Language". +- [5] 3GPP TS 25.419: "UTRAN Iu interface: Service Area Broadcast Protocol SABP". +- [6] 3GPP TS 25.925: "Radio Interface for Broadcast/Multicast Services". +- [7] TTA/EIA-41-D: "Technical realization of Cell Broadcast Service (CBS)". +- [8] TTA/EIA-637-A: "TR45 – Short Message Service for Spread Spectrum Systems". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply. + +**CB message:** user data as transmitted from Cell Broadcast Centre to UE (BMC SDU) + +**CB repetition period:** period after which a CB message should be broadcast again if more than one repetition are requested + +**Number of Broadcast Requested:** number of broadcasts requested for a CB message. This number is infinite or finite + +**DRX Schedule Period:** schedule period as optionally requested by the CBC (unit: seconds) + +**Reserved CB Capacity:** percentage of the capacity reserved for CB messages with category HIGH on the allocated radio resources CTCH, FACH and S-CCPCH. This parameter can be set optionally by the CBC. + +**CTCH Block Set:** subset of the transport block set of FACH on which the CTCH used for CBS is mapped uniquely + +**CBS schedule period:** finite sequence of CTCH Block Sets of variable length in which scheduled CB messages are broadcast + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-----|-----------------------------| +| AS | Access Stratum | +| BMC | Broadcast/Multicast Control | + +| | | +|---------|------------------------------------| +| C-SAP | Control Service Access Point | +| CBC | Cell Broadcast Centre | +| CBS | Cell Broadcast Service | +| CTCH | Common Traffic Channel | +| CTCH-BS | CTCH Block Set | +| FACH | Forward Access Channel | +| IE | Information Element | +| kbps | kilo-bits per second | +| L1 | Layer 1 (physical layer) | +| L2 | Layer 2 (data link layer) | +| L3 | Layer 3 (network layer) | +| MAC | Medium Access Control | +| NAS | Non Access Stratum | +| NSAPI | Network layer Service Access Point | +| PDCP | Packet Data Convergence Protocol | +| RLC | Radio Link Control | +| RRC | Radio Resource Control | +| UE | User Equipment | + +# --- 4 General + +## 4.1 Model of BMC + +Broadcast/Multicast Control (BMC) is a sublayer of L2 that exists in the User-Plane only. It is located above RLC. The L2/BMC sublayer is assumed as transparent for all services except broadcast/multicast. + +Figure 4.1-1 shows the model of the L2/BMC sublayer within the UTRAN radio interface protocol architecture. + +At the UTRAN side, the BMC sublayer shall consist of one BMC protocol entity per cell. Each BMC entity requires a single CTCH, which is provided by the MAC sublayer, through the RLC sublayer. The BMC requests the Unacknowledged Mode service of the RLC. + +It is assumed that there is a function in the RNC above BMC that resolves the geographical area information of the CB message (or, if applicable, performs evaluation of a cell list) received from the Cell Broadcast Centre (CBC). A BMC protocol entity serves only those messages at BMC-SAP that are to be broadcast into a specified cell. + +![Figure 4.1-1: BMC protocol model diagram showing the stack of layers for BMC. At the top is a dashed box labeled 'user-plane'. Below it is an oval labeled 'BMC-SAP'. This is connected to a grey box labeled 'L2/BMC sublayer' which contains a white box labeled 'BMC'. To the left of the BMC sublayer is an oval labeled 'CBMC-SAP' connected to the RRC layer (a grey box labeled 'RRC'). Below the BMC sublayer is an oval labeled 'UM'. This is connected to another grey box labeled 'L2/RLC sublayer' which contains a white box labeled 'RLC'. At the bottom is an oval labeled 'CTCH-SAP'.](d0abac95583b52a3b35f74a215567334_img.jpg) + +``` + +graph TD + user_plane[user-plane] --- BMC_SAP((BMC-SAP)) + BMC_SAP --- L2_BMC_sublayer[L2/BMC sublayer] + subgraph L2_BMC_sublayer [L2/BMC sublayer] + BMC[BMC] + end + RRC[RRC] --- CBMC_SAP((CBMC-SAP)) + CBMC_SAP --- L2_BMC_sublayer + L2_BMC_sublayer --- UM((UM)) + UM --- L2_RLC_sublayer[L2/RLC sublayer] + subgraph L2_RLC_sublayer [L2/RLC sublayer] + RLC[RLC] + end + L2_RLC_sublayer --- CTCH_SAP((CTCH-SAP)) + +``` + +Figure 4.1-1: BMC protocol model diagram showing the stack of layers for BMC. At the top is a dashed box labeled 'user-plane'. Below it is an oval labeled 'BMC-SAP'. This is connected to a grey box labeled 'L2/BMC sublayer' which contains a white box labeled 'BMC'. To the left of the BMC sublayer is an oval labeled 'CBMC-SAP' connected to the RRC layer (a grey box labeled 'RRC'). Below the BMC sublayer is an oval labeled 'UM'. This is connected to another grey box labeled 'L2/RLC sublayer' which contains a white box labeled 'RLC'. At the bottom is an oval labeled 'CTCH-SAP'. + +Figure 4.1-1: BMC protocol model + +# 5 Functions + +The functions are specified in [2]. They are: + +- Storage of Cell Broadcast Messages. +- Traffic volume monitoring and radio resource request for CBS. +- Scheduling of BMC messages. +- Transmission of BMC messages to UE. +- Delivery of Cell Broadcast messages to upper layer (NAS). + +# 6 Services provided to Upper Layers + +The BM-SAP provides a broadcast/multicast transmission service in the user plane on the radio interface for common user data in unacknowledged mode. + +The BMC sublayer interacts with other entities as illustrated in figure 1 of chapter 4. The interactions with the upper layer/U-plane and the RRC layer are specified in terms of primitives where the primitives represent the logical exchange of information and control between the BMC sublayer and higher layers. They do not specify or constrain implementations. The (adjacent) layers connect to each other through Service Access Points (SAPs). + +Three types of primitives are used for this document, as follows: + +- **REQUEST:** +This type is used when a higher layer is requesting a service from a lower layer. +- **INDICATION:** +This type is used by a lower layer providing a service to notify its higher layer of activities concerning that higher layer. + +###### - **CONFIRM:** + +This type is used by a lower layer providing the requested service to confirm to the higher layer that the activity has been completed. + +The primitives defined below are for communications between upper layer and BMC, as well as RRC and BMC in the same protocol stack. + +For the BMC sublayer two sets of primitives are defined. + +## - **Primitives between BMC and upper layer (U-plane):** + +BMC - Generic name - Type: Parameters. + +### - **Primitives between BMC and the RRC entity:** + +CBMC - Generic name - Type: Parameters. + +# 7 Services expected from RLC + +The BMC uses the unacknowledged mode service of the RLC sublayer. + +See [1] for details. + +# 8 Elements for layer-to-layer communication + +## 8.1 Service Primitives between RRC and BMC + +### 8.1.1 Primitives + +The primitives supported at CBMC-SAP between RRC and BMC are shown in Table 8.1.1-1. + +**Table 8.1.1-1: Primitives between BMC and RRC** + +| Generic Name | Parameters | +|----------------------|-----------------------| +| CBMC-Measurement-IND | CB-Traffic-Volume | +| CBMC-Rx-IND | Action, DRX selection | +| CBMC-Config-REQ | CTCH configuration | + +#### 8.1.1.1 CBMC-Measurement-IND + +The CBMC-Measurement-IND primitive is used by BMC to indicate the CB traffic volume. + +**Primitive Type:** indication. + +##### **Parameters:** + +CB-Traffic-Volume. + +#### 8.1.1.2 CBMC-Rx-IND + +The CBMC-Rx-IND primitive is used by BMC to indicate to RRC whether CB message reception shall start or stop and indicate when CB messages of interest are arriving in the next CBS schedule period. + +**Primitive Type:** indication. + +##### **Parameters:** + +Action. + +DRX selection. + +#### 8.1.1.3 CBMC-Config-REQ + +The CBMC-Config-REQ primitive is used by RRC to inform the BMC about the setting of the CTCH configuration. + +**Primitive Type:** indication. + +##### **Parameters:** + +CTCH configuration. + +### 8.1.2 Parameters + +#### 8.1.2.1 CB-Traffic-Volume + +Expected CTCH transmission rate [kbps]. + +Value set: 0,1,...,32. + +#### 8.1.2.2 Action + +Start CBS reception. + +Stop CBS reception. + +#### 8.1.2.3 DRX selection + +List of absolute CTCH BS indices which are of interest and which should be received by Layer 1. + +#### 8.1.2.4 CTCH configuration + +Current CTCH-BS index, $1 \leq i \leq 256$ . + +FACH identification. + +Transport Format Set of the allocated FACH (TB size, TBS size, TTI). + +Reserved CTCH transmission rate [kbps]: 0,1,...,32. + +## 8.2 Service Primitives between upper layer (U-plane) and BMC + +### 8.2.1 Primitives + +The primitives supported at BMC-SAP between BMC and upper layer (U-plane) are shown in Table 8.2.1-1. + +**Table 8.2.1-1: Primitives between BMC and upper layer** + +**Legend: [ ] optional parameters** + +| Generic Name | Parameters | +|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| BMC-Data-REQ | Message-ID,
[, Old-Serial-Number],
New-Serial-Number,
Data-Coding-Scheme,
CB-Data ,
[Category],
Repetition-Period,
Number-of-Broadcasts-Requested | +| BMC-Data-IND | Message-ID,
Serial-Number,
Data-Coding-Scheme,
CB-Data | +| BMC-Data-CNF | Message-ID,
Serial-Number | +| BMC-Congestion-IND | | +| BMC-Normal-IND | | +| BMC-Activation-REQ | Message-ID (n times) | +| BMC-Deactivation-REQ | Message-ID (n times) | +| BMC-DRX-REQ | CB-DRX-Schedule-Period, Reserved-CB-Capacity | +| BMC-Error-IND | Cause | +| BMC-Data41-REQ | Transport Layer Message,
Broadcast Address | +| BMC-Data41-IND | Transport Layer Message, | +| BMC-Error41-IND | Error Type | + +#### 8.2.1.1 Primitives used in relation to UMTS Core Network + +##### 8.2.1.1.1 BMC-Data-REQ + +The BMC-Data-REQ primitive is used by upper layer to request repeated transmission of CB messages. + +**Primitive Type:** request. + +###### **Parameters:** + +Message-ID; +[Old-Serial-Number]; +New-Serial-Number; +Data-Coding-Scheme; +CB-Data; +[Category]; +Repetition-Period; +Number-of-Broadcasts-Requested. + +##### 8.2.1.1.2 BMC-Data-IND + +The BMC-Data-IND primitive is used to indicate received CB messages (i.e. CB Data) to upper layer. + +**Primitive Type:** indication. + +###### **Parameters:** + +Message-ID; + +Serial-Number; + +Data-Coding-Scheme; + +CB-Data. + +##### **8.2.1.1.3 BMC-Data-CNF** + +The BMC-Data-CNF primitive is used to indicate the complete broadcast of CB messages. + +**Primitive Type:** confirmation. + +###### **Parameters:** + +Message-ID. + +Serial-Number. + +##### **8.2.1.1.4 BMC-Congestion-IND** + +The BMC-Congestion-IND primitive is used to indicate to upper layer (BM-IWF) that the BMC entity is congested. + +**Primitive Type:** indication. + +**Parameters:** None. + +##### **8.2.1.1.5 BMC-Normal-IND** + +The BMC-Normal-IND primitive is used to indicate to upper layer (BM-IWF) that the BMC has recovered from a congestion situation and is operating normal. + +**Primitive Type:** indication. + +**Parameters:** None. + +##### **8.2.1.1.6 BMC-Activation-REQ** + +The BMC-Activation-REQ primitive is used to request CB message reception and to notify which CB messages are of interest and shall be delivered to the upper layer. + +**Primitive Type:** request. + +###### **Parameters:** + +Message-ID (n times). + +##### **8.2.1.1.7 BMC-Deactivation-REQ** + +The BMC-Deactivation-REQ primitive is used to request stop of reception of listed CB messages. If no more CB messages are to be received, CB message reception shall stop. + +**Primitive Type:** request. + +###### **Parameters:** + +Message-ID (n times). + +##### **8.2.1.1.8 BMC-DRX-REQ** + +The BMC-DRX-REQ primitive is used to command CBS discontinuous reception (CB DRX). + +NOTE: In UMTS, a Set DRX procedure is not requested for the CBC in TS 23.041. It is left to an O&M system to provide such a function or not. + +**Primitive Type:** request. + +**Parameters:** + +CB-DRX-Schedule-Period. + +Reserved-CB-Capacity. + +##### 8.2.1.1.9 BMC-Error-IND + +The BMC-Error-IND primitive is used to indicate unsuccessful operations of the BMC entity requested. + +**Primitive Type:** indication. + +**Parameters:** + +Cause. + +#### 8.2.1.2 Primitives used for ANSI-41 Core Network + +##### 8.2.1.2.1 BMC-Data41-REQ + +The BMC-Data41-REQ primitive is used by upper layer (Transport Layer) to request repeated transmission of CBS messages if the source is ANSI-41 core network. + +**Primitive Type:** request. + +**Parameters:** + +Transport Layer Message. + +Broadcast Address. + +##### 8.2.1.2.2 BMC-Data41-IND + +The BMC-Data-IND primitive is used to indicate received CB messages to upper layer (Transport Layer) if the source is ANSI-41 core network. + +**Primitive Type:** indication. + +**Parameters:** + +Transport Layer Message. + +Broadcast Address. + +##### 8.2.1.2.3 BMC-Error41-IND + +The BMC-Error-IND primitive is used to report BMC Layer Error to the upper layer (Transport Layer) if the source is ANSI-41 core network. + +**Primitive Type:** indication. + +**Parameters:** + +Error Type. + +### 8.2.2 Parameters + +#### 8.2.2.1 Message-ID + +Part of the CB message identification describing the source and type of a CB message. This parameter is described in [3]. + +#### 8.2.2.2 Serial Number + +Part of the CB message identification describing variants of a CB message. This parameter is described in [3]. + +#### 8.2.2.3 Data-Coding-Scheme + +Data coding scheme applied to the CB information. This parameter is described in [4] and [3]. + +#### 8.2.2.4 CB-Data + +CB information to be broadcast. + +NOTE: The relation to GSM CBS pages can be found in [6] or [3]. + +#### 8.2.2.5 Category + +Indicates the category (priority) of the CB message. + +Values: + +HIGH (CB message is to be broadcast at the earliest opportunity in the reserved CB capacity of the current CB DRX schedule period). + +NORMAL (default, CB messages to be broadcast according to the associated repetition period). + +BACKGROUND (CB message to be broadcast in the CB capacity not occupied by HIGH or NORMAL CB messages within a CB DRX schedule period). + +This parameter is described in [3]. + +#### 8.2.2.6 Repetition-Period + +Indicates the period of time after which broadcast of the CB message should be repeated. This parameter is described in [3]. + +NOTE: For GSM, the repetition period is a multiple of 1.883 seconds (cf. [3]). + +#### 8.2.2.7 Number-of-Broadcasts-Requested + +Number of times a CB message is to be broadcast. + +Values: + +0 indefinitely. + +$n$ , $1 \leq n \leq 65535$ finite number of times to be broadcast. + +This parameter is described in [3]. + +#### 8.2.2.8 CB-DRX-Schedule-Period + +Indication of the CB DRX schedule period length. + +#### 8.2.2.9 Reserved-CB-Capacity + +Indicates the capacity reserved for CB messages with Category = HIGH or new CB messages. + +#### 8.2.2.10 Cause + +CB message already stored. + +Old CB message not stored. + +#### 8.2.2.11 Transport Layer Message + +This parameter is described in [8]. + +#### 8.2.2.12 Broadcast Address + +This parameter is described in [8]. + +#### 8.2.2.13 Error Type + +The error codes shall be SMS\_CauseCode values as defined in the SMS\_CauseCode Table in [7]. + +# 9 Procedures + +## 9.1 BMC Message Broadcast + +![Sequence diagram showing the procedure for broadcast of BMC messages. A UE (User Equipment) and a UTRAN (UMTS Radio Access Network) are shown. An arrow labeled 'BMC message' points from the UTRAN to the UE.](a7c51c18111139f9aca2805114108565_img.jpg) + +``` +sequenceDiagram + participant UE + participant UTRAN + Note left of UE: UE + Note right of UTRAN: UTRAN + UTRAN->>UE: BMC message +``` + +Sequence diagram showing the procedure for broadcast of BMC messages. A UE (User Equipment) and a UTRAN (UMTS Radio Access Network) are shown. An arrow labeled 'BMC message' points from the UTRAN to the UE. + +**Figure 9.1-1: Procedure for broadcast of BMC messages** + +This procedure is used for broadcasting BMC messages from the network to UEs in a cell. A UE supporting Cell Broadcast Service (CBS) shall be capable to receive BMC messages in the Idle mode and in CELL\_PCH and URA\_PCH RRC-states of Connected mode. + +Three types of BMC messages are identified: CBS Message, CBS41 Message and Schedule Message. + +## 9.2 Generation of Schedule message + +NOTE: Principles and examples are described in [6]. + +This procedure calculates the CBS schedule periods and assigns BMC messages (i.e. CBS Messages, CBS41 Messages and Schedule Messages) to the CBS schedule periods and gives an indication which of the CTCH Block Sets containing a part of or a complete BMC messages has the status "new". + +NOTE: The concatenation function of RLC shall not be applied. RLC Length Indicators shall not be concatenated with RLC SDUs they do not refer to. + +Algorithms used for scheduling are implementation dependent and thus do not need to be specified. Some parameters may be set by CBC or O&M system. + +CTCH Block Sets are indicated in a New Message Bitmap IE of BMC Schedule Message as new (bit position of a CTCH Block Set is set to value "1") when one of the following conditions is met: + +- The CTCH Block Set contains part of or a complete BMC message which was either not sent during the previous CBS schedule period, +- or sent unscheduled during the preceding CBS schedule period; +- or, the CTCH Block Set is indicated as of free usage, reading advised, +- or it contains the Schedule Message partly or complete of the following CBS schedule period, +- or it contains a CBS41 Message partly or complete. + +Other BMC messages sent in the same CBS schedule messages are indicated as "old" (bit position of CTCH Block Set containing this message partly or complete is set to value 0). + +The indication "new" is set both for the first transmission of a BMC message in the CBS schedule period or a repetition of it within the CBS schedule period. For CBS41 Messages, repetition is not specified. + +The input parameters of the scheduling procedure are set by CBC or RRC or by the O&M system for the BMC. + +The CBC input parameters are: + +CB messages (i.e. BMC SDUs), +Message Identifier per CB message, +Serial Number per CB message, +CB repetition period per CB message, +Number of Broadcast Requested per CB message. + +The RRC input parameters are: + +Sizes of CTCH Block Sets, +Timing of CTCH Block Set sequence. + +The O&M (BMC) input parameters are: + +DRX Schedule Period (cell related parameter) requested optionally, +Reserved CB Capacity (cell related parameter) requested optionally. + +## 9.3 Traffic volume measurement + +The BMC entity on the network side predicts periodically the expected amount of CBS traffic volume (unit: kbps) that is needed for transmission of CB messages currently and indicates this to RRC. + +The algorithms used for traffic volume prediction are implementation dependent and thus do not need to be specified. Some parameters may be set by O&M system. The algorithms depend on the chosen algorithms for CB message scheduling (cf. subclause 9.2). + +## 9.4 BMC message reception + +The BMC entity on the UE side evaluates received BMC Schedule Messages and takes decisions which BMC messages should be received. The reception of a BMC message is indicated to RRC if the CTCH Block Sets carrying this BMC message are indicated as new. If the upper layer has requested reception of individual CB messages when in status "old", the reception of these BMC messages are also indicated to RRC. + +If not otherwise requested by upper layers, only those CB messages received in BMC CBS Messages should be delivered to upper layers for which the Serial Number associated with the CB message has changed. This implies that the BMC has to store the last received Serial Number of each CB message activated by upper layers. + +Every CBS41 Message received by BMC shall be delivered to upper layer. + +# --- 10 BMC Messages + +## 10.1 General + +A BMC message is equivalent with a BMC PDU. There are three types of BMC messages defined, CBS messages and CBS41 messages, which carry cell broadcast data from higher layer, and *Schedule messages*, which provide information for support of Discontinuous Reception (DRX) of cell broadcast data at the UE. + +BMC messages and information elements are specified using the tabular format methodology as specified in TR 25.921, and additional text is describing the encoding. + +NOTE: Only IEs marked as MP or CV in the "Need" column exist, with the exception of the IE "BMC Schedule Message Extension" of the BMC Schedule Message (see subclause 10.3). + +BMC messages (i.e. BMC PDUs) specified by tabular format consist of an ordered sequence IE1,...IEn of information element fields. + +The octet string of a BMC message is defined as the concatenation of the octets of the IEs maintaining the sequence order. The bits within an octet are numbered 0 to 7; bit 0 is the least significant bit and is transmitted first. The octets are transmitted in order of increasing octet number, i.e. starting with octet 1. This means that bit 0 of octet 1 is transmitted as the first (leftmost) bit in the Data field of the UMD PDU [1]. + +The UE shall ignore any unrecognised bits at the end of a BMC message. + +NOTE: Although not explicitly stated as a requirement in release '99, 4 and 5 specifications it is assumed that release '99, 4, 5 UEs will also ignore any unrecognised bits at the end of a BMC message. + +## 10.2 BMC CBS Message + +The CBS Message carries the cell broadcast data and the address information if the address information is based on GSM CBS. + +RLC-SAP: UM; + +Logical channel: CTCH; + +Direction: UTRAN → UE. + +**Table 10.2-1: CBS Message** + +| Information Element | Need | Multi | Type and reference | Semantics description | +|---------------------|------|-------|--------------------|-----------------------| +| Message Type | MP | | Sec. 11.1 | | +| Message ID | MP | | Sec. 11.2 | | +| Serial Number | MP | | Sec. 11.3 | | +| Data Coding Scheme | MP | | Sec. 11.4 | | +| CB Data | MP | | Sec. 11.5 | | + +## 10.3 BMC Schedule Message + +The BMC Schedule Message describes for the succeeding CBS schedule period the time locations for each CBS Message and the location of the Schedule Message of the following CBS schedule period. The UE is not required to start receiving a CBS Schedule Period earlier than 100ms after UE has received the complete BMC Schedule message. + +RLC-SAP: UM. + +Logical channel: CTCH. + +Direction: UTRAN → UE. + +**Table 10. 3-1: Schedule Message** + +| Information Element | Need | Multi | Type and reference | Semantics description | Version | +|---------------------------------|------|----------------------------------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------| +| Message Type | MP | | Sec. 11.1 | | | +| Offset to Begin CTCH BS index | MP | | Sec. 11.6 | | | +| Length of CBS Scheduling Period | MP | | Sec. 11.7 | | | +| New Message Bitmap | MP | | Sec. 11.8 | | | +| Message Description | MP | 1 to | Sec. 11.9 | Message Description IE is included for each new message (1 in the New message bitmap) as well as for each old message (0 in the New message bitmap). The i-th Message Description IE refers to the i-th bit in the New Message Bitmap IE. The multiplicity for the IE "Message Description" does not require an additional length indication in the encoded message. The multiplicity shall be derived from the IE "Length of CBS Scheduling Period". | | +| BMC Schedule Message Extension | OP | | Sec 11.12 | | REL-6 | + +The IE "BMC Schedule Message Extension" is optional. There is no explicit mechanism to indicate the presence of this IE in the BMC Schedule Message. + +## 10.4 BMC CBS41 Message + +The CBS41 Message carries the cell broadcast data and the address information if the address information is based on ANSI-41 CBS. + +RLC-SAP: UM. + +Logical channel: CTCH. + +Direction: UTRAN → UE. + +**Table 10.4-1: CBS41 Message** + +| Information Element | Need | Multi | Type and reference | Semantics description | +|---------------------|------|-------|--------------------|-----------------------| +| Message Type | MP | | Sec. 11.1 | | +| Broadcast Address | MP | | Sec. 11.10 | | +| CB Data41 | MP | | Sec. 11.11 | | + +# 11 Information Elements + +## 11.1 Message Type + +**Table 11.1-1: Message Type IE** + +| IE/Group name | Need | Multi | Type and reference | Semantics description | +|---------------|------|-------|---------------------------------------|-----------------------------------------------------------------------------------------------------------| +| Message Type | MP | | Enumerated (0 .. 255)
Table 11.1-2 | This IE is coded as the binary representation of the Message Type. This IE is mapped onto a single octet. | + +Coding of Message Type + +**Table 11.1-2: Coding of Message Type IE** + +| | | +|------------|---------------------------------------------------------------------------------------------------| +| 1 | CBS Message | +| 2 | Schedule Message | +| 3 | CBS41 Message | +| 0, 4.. 255 | Reserved for future use (PDUs with this coding will be discarded by this version of the protocol) | + +## 11.2 Message ID + +**Table 11.2-1: Message ID IE** + +| IE/Group name | Need | Multi | Type and reference | Semantics description | +|---------------|------|-------|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Message ID | MP | | Octet string (2) | Identification of source and type of CBS message. The first octet contains octet 1 of the equivalent IE defined in and encoded according to [3] and so on. | + +## 11.3 Serial Number + +**Table 11.3-1: Serial Number IE** + +| IE/Group Name | Need | Multi | Type and reference | Semantics description | +|---------------|------|-------|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Serial Number | MP | | Octet string (2) | Identification of variations of a CBS message (part of the overall CBS message identification). The first octet contains octet 1 of the equivalent IE defined in and encoded according to [3] and so on. | + +## 11.4 Data Coding Scheme + +**Table 11.4-1: Data Coding Scheme IE** + +| IE/Group name | Need | Multi | Type and reference | Semantics description | +|--------------------|------|-------|--------------------|------------------------------------------------------------------------------------------------------| +| Data Coding Scheme | MP | | Bitstring(8) | Identification of the alphabet/coding and the language applied. This IE is encoded according to [4]. | + +## 11.5 CB Data + +**Table 11.5-1: CB Data IE** + +| IE/Group name | Need | Multi | Type and reference | Semantics description | +|---------------|------|-------|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CB Data | MP | | Octet string (N)
$N \geq 1$ | Content of CBS message. The first octet contains octet 1 of the equivalent IE defined in and encoded according to [4] and so on.
NOTE: This IE contains the CB Data as received in the SABP with the length indicator of the PER aligned bit string as received on SABP being removed. | + +NOTE: The number N is less than or equal to 1246 octets if a GSM CBS message is broadcast. + +## 11.6 Offset to Begin CTCH Block Set Index + +**Table 11.6-1: Offset to Begin CTCH Block Set Index IE** + +| IE/Group name | Need | Multi | Type and reference | Semantics description | +|-------------------------------|------|-------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Offset to Begin CTCH BS Index | MP | | Integer (1..255) | Pointer to the first CTCH BS of the next CBS Schedule Period relative to the CTCH BS index of the first part of the current BMC Schedule Message. This IE is coded as the binary representation of the Offset to Begin CTCH BS Index. This IE is mapped onto a single octet. The value 0 is reserved. | + +## 11.7 Length of CBS Schedule Period + +**Table 11.7-1: Length of CBS Schedule Period IE** + +| Information Element/Group name | Need | Multi | Type and reference | Semantics description | +|--------------------------------|------|-------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Length of CBS Schedule Period | MP | | Integer (1..255) | Number of consecutive CTCH BS of the next CBS Schedule Period. Together with Offset to Begin CTCH BS Index it points to the end of the CBS schedule period. This IE is coded as the binary representation of the Length of CBS Schedule Period. This IE is mapped onto a single octet. The Value 0 is reserved. | + +## 11.8 New Message Bitmap + +**Table 11.8-1: New Message Bitmap IE** + +| Information Element/Group name | Need | Multi | Type and reference | Semantics description | +|--------------------------------|------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------| +| New Message Bitmap | MP | | Octet string (N)

if "Length of CBS Schedule Period" mod 8 = 0 then
N = "Length of CBS Schedule Period" div 8,
else
N = "Length of CBS Schedule Period" div 8 + 1.

Table 11.8-2 | Bitmap indicating CTCH BS which contains new CBS Messages completely or partly | + +Coding of New Message Bitmap. + +**Table 11.8-2: Coding of New Message Bitmap IE** + +| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | Bit | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-------------------|-----------------|---|---|---|---|---------| +| CTCH BS index B | CTCH BS index B+1 | CTCH BS index B+2 | ... | | | | | Octet 1 | +| | | | | | | | | Octet 2 | +| | | | | | | | | ... | +| | ... | CTCH BS index E-1 | CTCH BS index E | 0 | 0 | 0 | 0 | Octet n | +| Legend: B First CTCH BS index of the CBS schedule period, $1 \leq B \leq 256$
E Last CTCH BS index of the CBS schedule period,
$E = B + \text{Length of CBS Schedule Period} - 1$ | | | | | | | | | + +CTCH BS Index i: + +Each bit of the New CBS Message Bitmap refers to the content of CTCH BS index i, $i=B, \dots, E$ . Its meaning is as follows: + +- 1 The CTCH BS index i contains a BMC Message partly or completely which was either not sent during the previous schedule period, or sent unscheduled during the preceding schedule period; or, the CTCH BS is indicated as of free usage, reading advised; or it contains the Schedule Message partly or complete of the following CBS schedule period, or it contains a CBS41 Message partly or complete. The value is 1 both for the first transmission of a given BMC message in the CBS schedule period or a repetition of it within the CBS schedule period. +- 0 The CTCH BS is such that value 1 is not suitable. + +The length of the New Message Bitmap is given by the IE Length of CBS Schedule Period. If it is not a multiple of 8 the remaining bit positions are padded with "0". + +## 11.9 Message Description + +**Table 11.9-1: Message Description IE** + +| IE/Group Name | Need | Multi | Type and reference | Semantics description | +|-----------------------------------------------|---------|-------|----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Message Description Type | MP | | Enumerated(0..255)

Table 11.9-3 | This IE is coded as the binary representation of the Message Description Type. This IE is mapped onto a single octet. | +| Message ID | CV MDT1 | | Octet string (2) | This IE is coded as the binary representation of the Message ID. The first octet contains octet 1 of the equivalent IE defined in and encoded according to [3] and so on. | +| Offset to CTCH BS index of first transmission | CV MDT2 | | Integer (0..255) | This IE is coded as the binary representation of the Offset to CTCH BS index of first transmission relative to the start of the BMC schedule period. This IE is mapped onto a single octet. | + +**Table 11.9-2: Conditions** + +| Condition | Explanation | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MDT1 | If Message Description Type = 1 or 5 then:
the CB-Message-Id IE is included | +| MDT2 | If Message Description Type = 0 or 4 then:
the Offset to CTCH BS index of first transmission IE is included
pointing to the CTCH BS index where the BMC message is transmitted
the first time within the schedule period. | + +**Table 11.9-3: Encoding of Message Description Type** + +| Value | Explanation | +|---------|------------------------------------------------------------------------------------------| +| 0 | Repetition of new BMC CBS message within schedule period | +| 1 | New BMC CBS message (a BMC CBS message never previously sent) | +| 2 | Reading advised | +| 3 | Reading optional | +| 4 | Repetition of old BMC CBS message within schedule period | +| 5 | Old BMC CBS message (repetition of a BMC CBS message sent in a previous schedule period) | +| 6 | Schedule message | +| 7 | CBS41 message | +| 8 | no message | +| 9.. 255 | Reserved for future use
(IEs received with this value will be replaced by value 3) | + +NOTE: Message Description Type values 0, 1, 4, 5 and 6 indicate transmission of a BMC message partly or completely. + +## 11.10 Broadcast Address + +**Table 11.10-1: Data Coding Scheme IE** + +| IE/Group name | Need | Multi | Type and reference | Semantics description | +|-------------------|------|-------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| Broadcast Address | MP | | Octet string (5) | Address information for higher layer.
The first octet contains octet 1 of the equivalent IE defined in and encoded according to [8] and so on. | + +## 11.11 CB Data41 + +**Table 11.11-1: CB Data IE** + +| IE/Group name | Need | Multi | Type and reference | Semantics description | +|---------------|------|-------|--------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| CB Data41 | MP | | Octet string (N)
$N \geq 1$ | Content of CBS message (ANSI-41).
The first octet contains octet 1 of the equivalent IE defined in and encoded according to [8] and so on. | + +## 11.12 CBS Schedule Message Extension + +**Table 11.12-1: CBS Schedule Message Extension IE** + +| Information Element | Need | Multi | Type and reference | Semantics description | Version | +|-------------------------|---------|-------|--------------------------------------|-----------------------|---------| +| Future extension bitmap | MP | | Octet string(1) | | REL-6 | +| Extension 0 | CV ext0 | | CBS Message Serial Numbers Sec 11.13 | | REL-6 | +| Extension 1 | CV ext1 | | Null | | REL-6 | +| Extension 2 | CV ext2 | | Null | | REL-6 | +| Extension 3 | CV ext3 | | Null | | REL-6 | +| Extension 4 | CV ext4 | | Null | | REL-6 | +| Extension 5 | CV ext5 | | Null | | REL-6 | +| Extension 6 | CV ext6 | | Null | | REL-6 | +| Extension 7 | CV ext7 | | Null | | REL-6 | + +**Table 11.12-2: Conditions** + +| Condition | Explanation | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| extn | If bit n of the Future extension bitmap is set to 1 then Extension n is present.
If bit n of the Future extension bitmap is set to 0 then Extension n is not present. | + +## 11.13 CBS Message Serial Numbers + +**Table 11.13: CBS Message Serial Numbers IE** + +| Information Element | Need | Multi | Type and reference | Semantics description | Version | +|------------------------------|------|------------------------------------|--------------------|-----------------------|---------| +| Length of Serial Number List | MP | | Integer (0..255) | | REL-6 | +| Serial Number List Entry | MP | 0 to The CTCH BS Index IE indicates the index of the CTCH BS within the BMC Schedule Period which contains the start of the BMC CBS Message.

This IE is coded as the binary representation of the CTCH BS Index. This IE is mapped onto a single octet.

| REL-6 | + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|--------|-----------|------|-----|-----|-------------------------------------------------------------------------------------------|-------------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New version | +| 12/1999 | RP-06 | RP-99647 | - | | | Approved at TSG-RAN #6 and placed under Change Control | 3.0.0 | +| 03/2000 | RP-07 | RP-000042 | 001 | | | Miscellaneous corrections | 3.1.0 | +| | RP-07 | RP-000042 | 002 | 2 | | Correction of messages and bit ordering | 3.1.0 | +| 09/2000 | RP-09 | RP-000360 | 005 | | | Corrections | 3.2.0 | +| 12/2000 | RP-10 | RP-000569 | 006 | 1 | | Correction to ANSI-41 Cell Broadcast Service | 3.3.0 | +| 03/2001 | RP-11 | RP-010028 | 007 | | | Corrections | 3.4.0 | +| | RP-11 | - | - | | | Upgrade to Release 4 - no technical change | 4.0.0 | +| 03/2002 | RP-15 | - | - | | | Upgrade to Release 5 - no technical change | 5.0.0 | +| 06/2002 | RP-16 | RP-020329 | 010 | | | Clarification on BMC message encoding | 5.1.0 | +| 12/2002 | RP-18 | RP-020720 | 013 | 1 | | Bit order in BMC messages | 5.2.0 | +| 03/2003 | RP-19 | RP-030102 | 016 | 1 | | Maximum size of BMC PDU | 5.3.0 | +| 12/2003 | RP-22 | - | - | | | Upgrade to Release 6 - no technical changes | 6.0.0 | +| 06/2004 | RP-24 | RP-040202 | 020 | | | Corrections to BMC Schedule message | 6.1.0 | +| 12/2004 | RP-26 | RP-040476 | 024 | 1 | | Correction of BMC message bit order and IE coding | 6.2.0 | +| 06/2005 | RP-28 | RP-050319 | 0025 | | | Clarification of RLC concatenation procedure with BMC | 6.3.0 | +| 09/2005 | RP-29 | RP-050464 | 0027 | 1 | | Cell Broadcast | 6.4.0 | +| 03/2006 | RP-31 | RP-060090 | 0028 | | | Introduction of Serial Number in BMC Schedule Message | 6.5.0 | +| | RP-31 | - | - | | | Upgrade to Release 7 - no technical changes | 7.0.0 | +| 06/2006 | RP-32 | RP-060363 | 0030 | | | Interpretation of "Offset to CTCH BS index of first transmission" in BMC Schedule message | 7.1.0 | +| 12/2007 | RP-38 | - | - | | | Upgrade to the Release 8 - no technical change | 8.0.0 | +| 12/2009 | RP-46 | - | - | | | Upgrade to the Release 9 - no technical change | 9.0.0 | +| 03/2011 | RP-51 | - | - | - | | Upgrade to the Release 10 - no technical change | 10.0.0 | +| 09/2012 | RP-57 | - | - | - | | Upgrade to the Release 11 - no technical change | 11.0.0 | +| 09/2014 | RP-65 | - | - | - | | Upgrade to the Release 12 - no technical change | 12.0.0 | +| 12/2015 | RP-70 | - | - | - | | Upgrade to the Release 13 - no technical change | 13.0.0 | +| 03/2017 | RP-75 | - | - | - | | Upgrade to Release 14 - no technical change | 14.0.0 | +| 06/2018 | RP-80 | - | - | - | | Upgrade to Release 15 - no technical change | 15.0.0 | +| 2020-07 | RP-88e | - | - | - | - | Upgrade to Rel-16 version without technical change | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25346/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg b/marked/Rel-16/25_series/25346/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44fb04ed9c545baddd7e31d195937c0e3d25fc0e --- /dev/null +++ b/marked/Rel-16/25_series/25346/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3cd03c9faa81de9b89146ff8fb4de962444a933e441adbd33156a78f36ce3b5 +size 16166 diff --git a/marked/Rel-16/25_series/25346/036ceaf207a7b289ca76e160892eb724_img.jpg b/marked/Rel-16/25_series/25346/036ceaf207a7b289ca76e160892eb724_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e4dbe33686f44f02c595ce0f24bd5430f394e5e --- /dev/null +++ b/marked/Rel-16/25_series/25346/036ceaf207a7b289ca76e160892eb724_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b7ae35829e71fa12ad660b527cb65a1c4171a9041ae2ce92675a926ac7ea3ff +size 76103 diff --git a/marked/Rel-16/25_series/25346/0f1767577a073167eb9628d72034e083_img.jpg b/marked/Rel-16/25_series/25346/0f1767577a073167eb9628d72034e083_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b936a1cfaffa49c612256a67818ae6f57db7cca0 --- /dev/null +++ b/marked/Rel-16/25_series/25346/0f1767577a073167eb9628d72034e083_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8699dd3e723223a908f88f63163d43bf9edb4b60aead6ae561ef3da2a58a688 +size 19867 diff --git a/marked/Rel-16/25_series/25346/18291be12b470a557e8c9f3a74e021be_img.jpg b/marked/Rel-16/25_series/25346/18291be12b470a557e8c9f3a74e021be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..434ed214f148a477e2d7f66eb77b02e63b6b4495 --- /dev/null +++ b/marked/Rel-16/25_series/25346/18291be12b470a557e8c9f3a74e021be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac55294411b0d39afdb0deda922b3ac5830585e7749964de412ab83547eeb70a +size 20721 diff --git a/marked/Rel-16/25_series/25346/18d8d7c537faf9057bd1fe0e7d152d7f_img.jpg b/marked/Rel-16/25_series/25346/18d8d7c537faf9057bd1fe0e7d152d7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f678fbd88eeb55579a6ef8106c5a10625396cb5 --- /dev/null +++ b/marked/Rel-16/25_series/25346/18d8d7c537faf9057bd1fe0e7d152d7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa8b418965b6a0dd35891c8db80eceae1f4468e30a1deb19be86c23b67474b9f +size 20089 diff --git a/marked/Rel-16/25_series/25346/195611c20b2dc7ed0fa3033392e22908_img.jpg b/marked/Rel-16/25_series/25346/195611c20b2dc7ed0fa3033392e22908_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d60dab07795f08517b8efda7cb18789e24cdf69 --- /dev/null +++ b/marked/Rel-16/25_series/25346/195611c20b2dc7ed0fa3033392e22908_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4518b4127b4f44e5d57082a74ec74d121b5c0f0c07fca5220db198c98e40daf +size 12436 diff --git a/marked/Rel-16/25_series/25346/1c140ee5d1a87186977da94a96bfa700_img.jpg b/marked/Rel-16/25_series/25346/1c140ee5d1a87186977da94a96bfa700_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad3b0314e389450a3aacff8ad5818a866a97730e --- /dev/null +++ b/marked/Rel-16/25_series/25346/1c140ee5d1a87186977da94a96bfa700_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26b5bd81b58ac00d787107b4c56ea535f3fc544350e4488b7e996d6c4c4248c6 +size 16114 diff --git a/marked/Rel-16/25_series/25346/1f1614411edea7edfc86c839a608e1fc_img.jpg b/marked/Rel-16/25_series/25346/1f1614411edea7edfc86c839a608e1fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2ec415840d39ecba7739e8c79444cfd1f00ee4e --- /dev/null +++ b/marked/Rel-16/25_series/25346/1f1614411edea7edfc86c839a608e1fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8828cfc57453b866bb55c45921b936cc08f1922df3bd6db38bad12ac442ec00 +size 119228 diff --git a/marked/Rel-16/25_series/25346/23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg b/marked/Rel-16/25_series/25346/23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f694bcaba92ed09cfef0c0b8539253ea9859c468 --- /dev/null +++ b/marked/Rel-16/25_series/25346/23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e83a53b6c317ebce55fab17b317d64d3b08523516d8be1398c14c3c98804988 +size 26976 diff --git a/marked/Rel-16/25_series/25346/2876be3592c7b4878400b85f209b2b6a_img.jpg b/marked/Rel-16/25_series/25346/2876be3592c7b4878400b85f209b2b6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ead2c9a58ee088edf69237534d7833299996a37 --- /dev/null +++ b/marked/Rel-16/25_series/25346/2876be3592c7b4878400b85f209b2b6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f2f7058994721a1888e4f6be938033366ef89cb4d467db31ad65d7ed9d0243c +size 35607 diff --git a/marked/Rel-16/25_series/25346/30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg b/marked/Rel-16/25_series/25346/30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db9de8be79acf1e6aff3a89cd86491a0edff3ace --- /dev/null +++ b/marked/Rel-16/25_series/25346/30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94c836e6393d66d0f86981e4f83a0004a9fc5a20d2fb7775a002d6214e5f3b3c +size 16743 diff --git a/marked/Rel-16/25_series/25346/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-16/25_series/25346/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a81f1f9ab59a372becfc8208ff60d8fe9a514e61 --- /dev/null +++ b/marked/Rel-16/25_series/25346/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f270b55ff981849183bb3cf72580040da522c36d1dc16b0d2ce50236ab7a690f +size 25233 diff --git a/marked/Rel-16/25_series/25346/3711f8e9365e67e6019303fc07924eed_img.jpg b/marked/Rel-16/25_series/25346/3711f8e9365e67e6019303fc07924eed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c21526894a3a5185c7aa025caac709e78051487a --- /dev/null +++ b/marked/Rel-16/25_series/25346/3711f8e9365e67e6019303fc07924eed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c19baa11ae30897208952ed6958f5370b1495b5e24a62bbbd8e813e993b9b3ba +size 12844 diff --git a/marked/Rel-16/25_series/25346/3b00a61116faef21d3a6009fd350b46a_img.jpg b/marked/Rel-16/25_series/25346/3b00a61116faef21d3a6009fd350b46a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2f3b75b0c566dedfb49811dbccceda8c18e79c8 --- /dev/null +++ b/marked/Rel-16/25_series/25346/3b00a61116faef21d3a6009fd350b46a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f829f4380a49fea2973492cf647305208138fdd68bf9a7f47fa2f424f3ff2c7 +size 35434 diff --git a/marked/Rel-16/25_series/25346/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-16/25_series/25346/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf78e2ff01643d18dd962300cd3f10d01fd62f2f --- /dev/null +++ b/marked/Rel-16/25_series/25346/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af11e4a8749f63e3e2a38172e46581f641c619ef620a3c90c6fe6eb25a023a06 +size 96056 diff --git a/marked/Rel-16/25_series/25346/65d47e1d0e5982c00e9bd116b89e2b6a_img.jpg b/marked/Rel-16/25_series/25346/65d47e1d0e5982c00e9bd116b89e2b6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..201ae6fd265b71313275f45b878d9f08391e8d4c --- /dev/null +++ b/marked/Rel-16/25_series/25346/65d47e1d0e5982c00e9bd116b89e2b6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55a861c555b0cc5e954d9d33128ed58e3367ee2b877fd2ca2bb2705144104a8b +size 14768 diff --git a/marked/Rel-16/25_series/25346/6f659142d4789aa889184459f884787e_img.jpg b/marked/Rel-16/25_series/25346/6f659142d4789aa889184459f884787e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05495dd15ad5d45534bbef12ae581d857a90315c --- /dev/null +++ b/marked/Rel-16/25_series/25346/6f659142d4789aa889184459f884787e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb96deaea8d062e47b2969e507eb7973e40f3a75dfbe0b0fd066892b51572afa +size 42092 diff --git a/marked/Rel-16/25_series/25346/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg b/marked/Rel-16/25_series/25346/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e18813a3286c26315d29b43fb13c207f9855f469 --- /dev/null +++ b/marked/Rel-16/25_series/25346/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc8ca8bde558b0232c87a91972760f4c5eebf66a9a3299073c8c621b924a4396 +size 20559 diff --git a/marked/Rel-16/25_series/25346/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/25_series/25346/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f04beb16b83cf66aa3037c20e180e2023e7381c6 --- /dev/null +++ b/marked/Rel-16/25_series/25346/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f710516f391400702d4b31ea9ccfad11709347b3ea2c5897c0aa09e14c3e0c5 +size 28425 diff --git a/marked/Rel-16/25_series/25346/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg b/marked/Rel-16/25_series/25346/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b9a7476d68c1e5041513d6c66e8908cfa3a7a49 --- /dev/null +++ b/marked/Rel-16/25_series/25346/8ed7f57cc317f6574bec781d01ae6ad2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6fca6686e3a1bbc360a5ba3170440bb90d65d56e94835664ba6fbc7d75a38c74 +size 34705 diff --git a/marked/Rel-16/25_series/25346/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/25_series/25346/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e63e15f1bcf102be9e38880131a87d5a79bb16b5 --- /dev/null +++ b/marked/Rel-16/25_series/25346/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08919a25acbeb252ab56636a5b746a83d741e5f26d9b2697b5fc40831101e386 +size 75743 diff --git a/marked/Rel-16/25_series/25346/94d3fdcc244924326f02533aeb2d93fc_img.jpg b/marked/Rel-16/25_series/25346/94d3fdcc244924326f02533aeb2d93fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e418666a61fd6dc6693ed9e9af6e023d148eec5 --- /dev/null +++ b/marked/Rel-16/25_series/25346/94d3fdcc244924326f02533aeb2d93fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe60a3394c36073795395efec1cf8e530bddc54165ceb0f1b7c6e569c4a9e816 +size 38226 diff --git a/marked/Rel-16/25_series/25346/9c8070d46f1d2480a875239e792f1ef6_img.jpg b/marked/Rel-16/25_series/25346/9c8070d46f1d2480a875239e792f1ef6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3c52488c64617f384839322c71d7cb8c19d8ae1 --- /dev/null +++ b/marked/Rel-16/25_series/25346/9c8070d46f1d2480a875239e792f1ef6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:038dc5589e8ace14b4763b1091fe3e08269d86e927ca28abbe66aae9a15dd7d5 +size 116797 diff --git a/marked/Rel-16/25_series/25346/9ed248b025d766251d58be10b01a1cc0_img.jpg b/marked/Rel-16/25_series/25346/9ed248b025d766251d58be10b01a1cc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2adfb413cf353be9a36b2f5cca0ff6a773f7a86 --- /dev/null +++ b/marked/Rel-16/25_series/25346/9ed248b025d766251d58be10b01a1cc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff66aa4aa8c07ac24efd4e289c66019bfcbfc8e846cf427575fcb439e6bec45a +size 40028 diff --git a/marked/Rel-16/25_series/25346/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg b/marked/Rel-16/25_series/25346/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2321bfdd585e7291bb5ed5de8e3507620774a483 --- /dev/null +++ b/marked/Rel-16/25_series/25346/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6c4fc3cf483c9558cbdc309ef9cdf9cc5e2cc4e75c61a02e46a81da38586ffb +size 14940 diff --git a/marked/Rel-16/25_series/25346/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg b/marked/Rel-16/25_series/25346/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..affdac0929177d8e8687b064389458366ecec6b9 --- /dev/null +++ b/marked/Rel-16/25_series/25346/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b16ac4d850bcf4103219a08610a32843c1e14fb5892703208908bda9a5e7b0cc +size 23231 diff --git a/marked/Rel-16/25_series/25346/a5184899f915014fa38608754efcc9c7_img.jpg b/marked/Rel-16/25_series/25346/a5184899f915014fa38608754efcc9c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38671ce099da0eec149e1e1838eaad18d2f07b59 --- /dev/null +++ b/marked/Rel-16/25_series/25346/a5184899f915014fa38608754efcc9c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3995e23d47e8b1005dce86258d886faeb879ad0871e99f60b7754f272a215d7b +size 19916 diff --git a/marked/Rel-16/25_series/25346/a97518a839da75f8379c578562b01bc2_img.jpg b/marked/Rel-16/25_series/25346/a97518a839da75f8379c578562b01bc2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec1d3788d2aba94979a43c2d3f9bfd4ed6492b7f --- /dev/null +++ b/marked/Rel-16/25_series/25346/a97518a839da75f8379c578562b01bc2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ebf2b34907b1527a2dc5b28960108164d86d38a07a8320e771a505819dd9c65 +size 21159 diff --git a/marked/Rel-16/25_series/25346/adc59ed6840bcb2d392ea323abfccedc_img.jpg b/marked/Rel-16/25_series/25346/adc59ed6840bcb2d392ea323abfccedc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..88ba4b54259a51de77733a744cdf21d879e61b15 --- /dev/null +++ b/marked/Rel-16/25_series/25346/adc59ed6840bcb2d392ea323abfccedc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e0927a63102e4430cbf36b90de9aa4c129eb461d55aaa9c0334fedbfa562580 +size 23587 diff --git a/marked/Rel-16/25_series/25346/ae375ead8aa673286b534e079e9a8533_img.jpg b/marked/Rel-16/25_series/25346/ae375ead8aa673286b534e079e9a8533_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a90592d8a512aa0d853c76429cecb5c4705e45fa --- /dev/null +++ b/marked/Rel-16/25_series/25346/ae375ead8aa673286b534e079e9a8533_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8426827591554b506eefeb1c3063d03189008a42047d7f152cf8cbab721bf89c +size 19902 diff --git a/marked/Rel-16/25_series/25346/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/25_series/25346/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0826296e9badeb61b688d5a3daa0c3b95269c34 --- /dev/null +++ b/marked/Rel-16/25_series/25346/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd6b07b04ff5226a864a35feb166dc3fcf146c66f7edabfa1a19931ff43a09e0 +size 50104 diff --git a/marked/Rel-16/25_series/25346/b06a4c871dfd0ce034cf801519d0039a_img.jpg b/marked/Rel-16/25_series/25346/b06a4c871dfd0ce034cf801519d0039a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..493bba4cbb9af7f56583024dbf80b5eb5ad1c562 --- /dev/null +++ b/marked/Rel-16/25_series/25346/b06a4c871dfd0ce034cf801519d0039a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d57c7480573fcdc529c5eb393d71d30688e8ea492e4c44d24fa45c1c027ff3f0 +size 14939 diff --git a/marked/Rel-16/25_series/25346/b17128855e79bd21a030ff6fcf1c3310_img.jpg b/marked/Rel-16/25_series/25346/b17128855e79bd21a030ff6fcf1c3310_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0b8d8f021ecc044ba0d898900e23a7137e2f755 --- /dev/null +++ b/marked/Rel-16/25_series/25346/b17128855e79bd21a030ff6fcf1c3310_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3a38c24784a949e7051c9143272d4080630ab72fd77d1857c9388be2a32dbf7 +size 9697 diff --git a/marked/Rel-16/25_series/25346/b2ea162a0f53d5e0504b7d28346e0754_img.jpg b/marked/Rel-16/25_series/25346/b2ea162a0f53d5e0504b7d28346e0754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2c16096f588aee6f770f3d3137dd7b0255943db --- /dev/null +++ b/marked/Rel-16/25_series/25346/b2ea162a0f53d5e0504b7d28346e0754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6cbcab8c9d245c276481e1f10cb4112dc6d701d712e6ace1581ffdd6ac13d1f +size 21965 diff --git a/marked/Rel-16/25_series/25346/b4f6d3668f7e851eaff07ccf26001623_img.jpg b/marked/Rel-16/25_series/25346/b4f6d3668f7e851eaff07ccf26001623_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..158289deee90774e69ef83d8af2c893a1e1150df --- /dev/null +++ b/marked/Rel-16/25_series/25346/b4f6d3668f7e851eaff07ccf26001623_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e87d308ec8a9f2f6509cebfff5a8998931e6b0961fbe5e95a30952987bd9468d +size 19657 diff --git a/marked/Rel-16/25_series/25346/c3e8a7fe2e4f51806e05b9b1aae20d57_img.jpg b/marked/Rel-16/25_series/25346/c3e8a7fe2e4f51806e05b9b1aae20d57_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..584b4973bbb8c364c22a099879683ff04a80482c --- /dev/null +++ b/marked/Rel-16/25_series/25346/c3e8a7fe2e4f51806e05b9b1aae20d57_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:232d27792b73b4d3db9d90e2aa04fe03ff00ddb03e5d37b2d4aa814c90ce167f +size 13296 diff --git a/marked/Rel-16/25_series/25346/c8fcc1ae5d86caaae5607b58d16be8e4_img.jpg b/marked/Rel-16/25_series/25346/c8fcc1ae5d86caaae5607b58d16be8e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83a14ec6684bbbcb74e1d02d8b4dc0554e404d6c --- /dev/null +++ b/marked/Rel-16/25_series/25346/c8fcc1ae5d86caaae5607b58d16be8e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:248a90bb19b109a67448cf9e2fa1553ee814e29f6914093f7495bd9bec49db48 +size 21165 diff --git a/marked/Rel-16/25_series/25346/cdd9c57c9c578160002ead5cdaef414d_img.jpg b/marked/Rel-16/25_series/25346/cdd9c57c9c578160002ead5cdaef414d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9be66c40eb97dce09ab2d7c8a617e5c90d3104f --- /dev/null +++ b/marked/Rel-16/25_series/25346/cdd9c57c9c578160002ead5cdaef414d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:adc865573d25abc20b8e25b1bbcf1da52f579ab3d94f9ce8276721a14a4801a9 +size 16742 diff --git a/marked/Rel-16/25_series/25346/ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg b/marked/Rel-16/25_series/25346/ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f33c1054b8105413bff22e7fb9810a11a1393ddb --- /dev/null +++ b/marked/Rel-16/25_series/25346/ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6007e22324b17d5d06cfe8d79052ba9d1312b42a2c847381bc4fbd91569fcf4 +size 16443 diff --git a/marked/Rel-16/25_series/25346/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/25_series/25346/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ad0385544ffb0961041b63968c65f22ed105180 --- /dev/null +++ b/marked/Rel-16/25_series/25346/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:715354f5000f08f605c33363efdd935d97b992e591b54ff6f4f4a71a37229124 +size 54912 diff --git a/marked/Rel-16/25_series/25346/d3b5eac55166fc428a223bba5c46961b_img.jpg b/marked/Rel-16/25_series/25346/d3b5eac55166fc428a223bba5c46961b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dfeda4c6cda9f5efd07319e66f314ba499dcd301 --- /dev/null +++ b/marked/Rel-16/25_series/25346/d3b5eac55166fc428a223bba5c46961b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3ea335cf0e04fe593b6af191d8d1376d34d8cd674f6f26bd22de6f187ef8967 +size 37161 diff --git a/marked/Rel-16/25_series/25346/d7948c38a18636aefecdd95388196460_img.jpg b/marked/Rel-16/25_series/25346/d7948c38a18636aefecdd95388196460_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb7d4159a4bc977fa40ed18b5bc8eeb0552f74de --- /dev/null +++ b/marked/Rel-16/25_series/25346/d7948c38a18636aefecdd95388196460_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d867ef0ad4c817731da19962d6bf065f0cc6eb7b1425a2922bc449c1a91d4323 +size 12438 diff --git a/marked/Rel-16/25_series/25346/d9c0a780cd22626253dab4aa41699e2f_img.jpg b/marked/Rel-16/25_series/25346/d9c0a780cd22626253dab4aa41699e2f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e28416621788b1ac7708428561ad2ef2370d2a42 --- /dev/null +++ b/marked/Rel-16/25_series/25346/d9c0a780cd22626253dab4aa41699e2f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3af4fdcb28258238efbd4c4c9b555ecb1e8221e42d439fbf3ddfc0dddc9cde13 +size 77932 diff --git a/marked/Rel-16/25_series/25346/df65c22a46ec3e7285e44de67d3a59cf_img.jpg b/marked/Rel-16/25_series/25346/df65c22a46ec3e7285e44de67d3a59cf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c2de5df3b2fe92758fe51ac46574fd64d9957de --- /dev/null +++ b/marked/Rel-16/25_series/25346/df65c22a46ec3e7285e44de67d3a59cf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7217b1849b7acfedfaa5183f1fd463f709a1984a0631975ffefaeed1b91159c +size 13297 diff --git a/marked/Rel-16/25_series/25346/e3eebf9854831ba50eca8b26c468f65e_img.jpg b/marked/Rel-16/25_series/25346/e3eebf9854831ba50eca8b26c468f65e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4928d07f1767ccecb83ccd91a0277b97c8b296a --- /dev/null +++ b/marked/Rel-16/25_series/25346/e3eebf9854831ba50eca8b26c468f65e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea8cf09d932a46413f4e550d443e6b9f9c7a22ecc9025f152adf0f801b00ce9b +size 13428 diff --git a/marked/Rel-16/25_series/25346/e417ae35ab07134888be901c201d54cd_img.jpg b/marked/Rel-16/25_series/25346/e417ae35ab07134888be901c201d54cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d31bcc14a72482cb66a3c4a425eadcd2f7129bd9 --- /dev/null +++ b/marked/Rel-16/25_series/25346/e417ae35ab07134888be901c201d54cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a607e309e3deeb606b2f1588f23bd656904ece553e26af23967f814c12f71e34 +size 14358 diff --git a/marked/Rel-16/25_series/25346/e9f5aa7b76362051c591d6783211f820_img.jpg b/marked/Rel-16/25_series/25346/e9f5aa7b76362051c591d6783211f820_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a1630cdb06067df814f61e4434660837677fac1 --- /dev/null +++ b/marked/Rel-16/25_series/25346/e9f5aa7b76362051c591d6783211f820_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de5a0ef2f569acc039040e284b5935a3f2a4f6f5f0ee17414bf1315e40f5e96b +size 12446 diff --git a/marked/Rel-16/25_series/25346/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg b/marked/Rel-16/25_series/25346/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a95da0bf8429ed9be19a16cba6fb90a72ac4d22 --- /dev/null +++ b/marked/Rel-16/25_series/25346/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc696bcd8c943cbc6592d1107521823804b09a3ba23773002691edb0890f7a13 +size 31264 diff --git a/marked/Rel-16/25_series/25346/fe7304192caf64cda93b580c5e7e5c06_img.jpg b/marked/Rel-16/25_series/25346/fe7304192caf64cda93b580c5e7e5c06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..810bfbdd0ab58af515233f583fd1c1a56965b376 --- /dev/null +++ b/marked/Rel-16/25_series/25346/fe7304192caf64cda93b580c5e7e5c06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c4ad3e082d4a16ccb5d7669e99aa5937e8dfe59be41fb4dd670b4116ad50d4b +size 12776 diff --git a/marked/Rel-16/25_series/25346/raw.md b/marked/Rel-16/25_series/25346/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..3d0455b7b595ce3fa240a3a1ac29caebc70e4597 --- /dev/null +++ b/marked/Rel-16/25_series/25346/raw.md @@ -0,0 +1,2642 @@ + + + + + + +# Contents + +| | | +|--------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions, symbols and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Symbols..... | 9 | +| 3.3 Abbreviations ..... | 9 | +| 4 Background and introduction..... | 10 | +| 5 MBMS UTRAN and protocol architecture..... | 10 | +| 5.1 MBMS UTRAN architecture principles ..... | 10 | +| 5.1.1 MBMS Service Context in CRNC ..... | 10 | +| 5.1.2 MBMS Session start and MBMS Session Stop..... | 11 | +| 5.1.3 MBMS Iu bearer..... | 11 | +| 5.1.4 MBMS Iub bearer..... | 12 | +| 5.1.5 Mapping of MBMS Iu bearer to p-t-p and p-t-m connections ..... | 12 | +| 5.1.6 UE Linking/De-linking..... | 12 | +| 5.1.7 RNC Registration ..... | 14 | +| 5.1.8 RNC De-Registration ..... | 14 | +| 5.1.9 CN De-Registration..... | 14 | +| 5.1.10 URA Linking/De-linking..... | 14 | +| 5.1.11 IP Multicast Distribution ..... | 15 | +| 5.2 MBMS Uu Principles..... | 15 | +| 5.2.1 MBMS Service States in UE..... | 15 | +| 5.2.2 One PDCP and RLC entity shared among multiple cells within one RNS ..... | 16 | +| 5.2.3 MCCH Information Scheduling ..... | 16 | +| 5.2.4 MBMS Notification..... | 17 | +| 5.2.5 MBMS Counting ..... | 18 | +| 5.2.6 MBMS Radio Bearer Release in the UE ..... | 19 | +| 5.2.7 MBMS Session Repetition ..... | 20 | +| 5.2.8 MBMS Service Prioritisation ..... | 20 | +| 5.3 Protocol structure ..... | 21 | +| 5.3.1 MBMS User Plane Protocol Stack Architecture ..... | 21 | +| 5.3.2 MBMS Control Plane Protocol Stack Architecture..... | 22 | +| 5.4 MAC architecture..... | 23 | +| 5.4.1 UTRAN MAC Architecture to support MBMS ..... | 23 | +| 5.4.2 MAC-c/sh/m architecture: UTRAN side..... | 23 | +| 5.4.3 MAC-c/sh/m architecture: UE side ..... | 24 | +| 6 MBMS Channel Structure..... | 25 | +| 6.1 Point-to-Point Transmission..... | 25 | +| 6.2 Point-to-multipoint Transmission ..... | 25 | +| 6.2.1 Logical Channels ..... | 25 | +| 6.2.1.1 MBMS point-to-multipoint Control Channel (MCCH)..... | 25 | +| 6.2.1.2 MBMS point-to-multipoint Traffic Channel (MTCH)..... | 25 | +| 6.2.1.3 MBMS point-to-multipoint Scheduling Channel (MSCH) ..... | 25 | +| 6.2.2 Transport Channel ..... | 26 | +| 6.2.3 Physical Channel ..... | 26 | +| 6.2.4 Mapping between channels ..... | 26 | +| 6.2.5 Data Flows through Layer 2 ..... | 27 | +| 6.2.5.1 Data flow for MCCH mapped to FACH..... | 27 | +| 6.2.5.2 Data flow for MTCH mapped to FACH..... | 27 | +| 6.2.5.3 Data flow for MSCH mapped to FACH..... | 27 | +| 6.3 MBMS Notification Indicator Channel..... | 27 | +| 7 MBMS Reception and UE Capability..... | 27 | +| 7.1 Selective and Soft Combining for MBMS P-T-M transmission..... | 27 | + +| | | | +|------------|------------------------------------------------------------------------|----| +| 7.1.bis | Simulcast Combining (TDD only) ..... | 28 | +| 7.1.ter | Chip Combining (1.28Mcps TDD)..... | 29 | +| 7.1A | MBMS over a Single Frequency Network (MBSFN)..... | 30 | +| 7.1A.1 | 3.84 / 7.68 MCPS TDD MBMS over a Single Frequency Network (MBSFN)..... | 31 | +| 7.1A.2 | FDD MBMS over a Single Frequency Network (MBSFN)..... | 32 | +| 7.1A.3 | 1.28 MCPS TDD MBMS over a Single Frequency Network (MBSFN)..... | 32 | +| 7.1A.4 | 3.84 Mcps TDD IMB MBMS over a Single Frequency Network (MBSFN) ..... | 33 | +| 7.1B | MBMS in case of inter-RNC synchronization ..... | 34 | +| 7.1B.1 | Control Plane aspects ..... | 34 | +| 7.1B.1.1 | MBMS Parameter Configurations ..... | 34 | +| 7.1B.1.2 | MBMS Counting and mode switch coordination ..... | 34 | +| 7.1B.1.3 | Control Plane Coordination at MBMS Session Start..... | 35 | +| 7.1B.1.3.1 | Coordination of neighbor cell configuration ..... | 35 | +| 7.1B.1.4 | MCCH synchronization in an MBSFN cluster ..... | 36 | +| 7.1B.2 | User Plane aspects ..... | 36 | +| 7.1B.2.1 | Timing requirements..... | 36 | +| 7.1B.2.2 | MBMS User Data flow synchronization ..... | 36 | +| 7.1B.2.3 | User Plane recovery in case of Multiple Packets Loss ..... | 37 | +| 7.2 | UE Capability ..... | 38 | +| 7.3 | MBMS Reception..... | 39 | +| 7.3.1 | MBMS Reception in RRC Idle Mode ..... | 39 | +| 7.3.2 | MBMS Reception in RRC Connected Mode: URA_PCH state..... | 39 | +| 7.3.3 | MBMS Reception in RRC Connected Mode: CELL_PCH state ..... | 40 | +| 7.3.4 | MBMS Reception in RRC Connected Mode: CELL_FACH state ..... | 40 | +| 7.3.5 | MBMS Reception in RRC Connected Mode: CELL_DCH state ..... | 40 | +| 8 | UTRAN Signalling Flows for MBMS ..... | 41 | +| 8.1 | MBMS High Level Signalling Scenarios..... | 41 | +| 8.1.1 | Session start..... | 41 | +| 8.1.2 | Joining (during a session)..... | 43 | +| 8.1.3 | Recounting..... | 44 | +| 8.1.4 | Session stop ..... | 45 | +| 8.2 | MBMS RNC Signalling Flows ..... | 45 | +| 8.2.1 | MBMS Session Start procedure ..... | 45 | +| 8.2.2 | MBMS Session Update procedure ..... | 46 | +| 8.2.3 | MBMS Session Stop procedure..... | 46 | +| 8.2.4 | RNC Registration procedure ..... | 47 | +| 8.2.5 | RNC De-Registration procedure ..... | 47 | +| 8.2.6 | CN De-Registration procedure ..... | 47 | +| 8.2.7 | MBMS Channel Type Switching over Uu ..... | 48 | +| 8.2.8 | MBMS UE Linking ..... | 48 | +| 8.2.9 | MBMS UE De-Linking ..... | 49 | +| 8.2.10 | MBMS Service Id Request..... | 49 | +| 8.2.11 | MBMS Attach/Detach over Iur ..... | 50 | +| 8.2.12 | MBMS Channel Type Reconfiguration over Iur ..... | 50 | +| 8.2.13 | Information Exchange over Iur..... | 51 | +| 8.2.14 | MBMS RAB Establishment Indication ..... | 52 | +| 8.2.15 | MBMS RAB Release ..... | 52 | +| 8.2.16 | MBMS Session Start procedure in case of IP Multicast transport ..... | 53 | +| 8.2.17 | MBSFN MCCH Information..... | 54 | +| 8.3 | MBMS Uu Signalling Flows..... | 54 | +| 8.3.1 | Broadcast of MBMS System Information ..... | 54 | +| 8.3.2 | MBMS Service Information ..... | 55 | +| 8.3.3 | MBMS Radio Bearer Information..... | 55 | +| 8.3.4 | MBMS Access Information..... | 56 | +| 8.3.5 | MBMS Neighbouring Cell Information ..... | 56 | +| 8.3.6 | MBMS Joined Indication ..... | 57 | +| 8.3.7 | MTCH Scheduling Information ..... | 57 | +| 8.3.8 | MBMS Change Information..... | 58 | +| 8.3.9 | MBMS P-T-P Modification Request..... | 58 | +| 8.3.10 | MBMS Counting Response..... | 59 | +| 8.3.11 | MBMS Selected Services Information ..... | 59 | + +| | | | +|-------------------------------|-------------------------------------------------------------------|-----------| +| 9 | Security for MBMS..... | 59 | +| 10 | Mobility Procedures for MBMS ..... | 60 | +| 10.1 | Use of Periodical Transmission of MBMS Critical Information ..... | 60 | +| 10.2 | UE Actions for Mobility ..... | 60 | +| 10.2.1 | RRC idle mode ..... | 60 | +| 10.2.2 | URA_PCH State ..... | 61 | +| 10.2.3 | CELL_PCH ..... | 61 | +| 10.2.4 | CELL_FACH ..... | 62 | +| 10.2.5 | CELL_DCH State..... | 62 | +| 11 | Resource Management for MBMS ..... | 63 | +| 11.1 | MBMS Access Control Procedure ..... | 63 | +| 11.2 | Frequency layer Convergence..... | 64 | +| 11.3 | Frequency layer Dispersion..... | 64 | +| Annex A (informative): | MBMS Phases in UTRAN ..... | 65 | +| A1 | Security for MBMS..... | 65 | +| A2 | MBMS Phase 2 ..... | 65 | +| A3 | MBMS Phase 3 ..... | 66 | +| A4 | MBMS Phases and Status Parameters ..... | 66 | +| Annex B (informative): | MBMS Control Information ..... | 67 | +| Annex C (informative): | Change history..... | 69 | + +# --- Foreword + +This Technical Report has been produced by the 3rd 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 is a technical specification of the overall support of Multimedia Broadcast Multicast Service in UTRA. + +# --- 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. + +[1] 3GPP TR 21.905: " Vocabulary for 3GPP Specifications ". + +[2] 3GPP TS 22.146: "Multimedia Broadcast/Multicast Service; Stage 1". + +[3] 3GPP TS 22.246: "MBMS User Services; Stage 1". + +[4] 3GPP TS 23.246: "Multimedia Broadcast Multicast Service; Architecture and Functional Description". + +[5] 3GPP TR 25.992: "Multimedia Broadcast Multicast Service (MBMS); UTRAN/GERAN Requirements". + +[6] 3GPP TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes". + +[7] 3GPP TS 33.246: "3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS)". + +[8] 3GPP TS 25.301: "Radio Interface Protocol Architecture". + +[9] 3GPP TS 25.211: "Physical channels and mapping of transport channels onto physical channels (FDD)". + +[10] 3GPP TS 25.221: "Physical channels and mapping of transport channels onto physical channels (TDD) ". + +[11] 3GPP TS 25.304: "User Equipment (UE) procedures in idle mode and procedures for cell reselection in connected mode". + +[12] 3GPP TS 25.306: "UE Radio Access capabilities". + +[13] 3GPP TS 25.331: "Radio Resource Control (RRC); Protocol Specification". + +[14] 3GPP TS 25.446: "“MBMS Synchronisation Protocol (SYNC)”". + +[15] 3GPP TS 23.007: "“Restoration procedures”". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply. + +![Figure 3.1: MBMS Timeline, based on [4].](d0abac95583b52a3b35f74a215567334_img.jpg) + +The diagram illustrates the MBMS timeline across three horizontal axes: UE1 events, UE2 events, and Service 1. The timeline is divided into three phases: Phase 1 (MBMS phase in UTRAN), Phase 2, and Phase 3. Key events include: + +- UE1 events:** Subscription can be at any time, subscription to service 1, service leave. +- UE2 events:** Service join by the user can be at any time. +- Service 1:** Start service 1 announcement, 1st session start, idle period of session 1, Data transfer (Service 1 session 1), session stop, Data transfer (Service 1 session 2), Stop Service 1 announcement. +- Data Transfer:** Announcement, Data sent to UE1, Data sent to UE1 and UE2, Data sent to UE2. +- Phases:** Phase 1 (MBMS phase in UTRAN), Phase 2, Phase 3. + +Figure 3.1: MBMS Timeline, based on [4]. + +Figure 3.1: MBMS Timeline, based on [4]. + +**MBMS session start** is the point at which the BM-SC is ready to send data. + +**MBMS notification** informs the UEs about forthcoming and about ongoing MBMS data transfer. + +**MBMS Cell Group** is a group of multiple cells belonging to one RNS and sharing one PDCP and RLC entity to utilize p-t-m transmission of the MBMS Service + +**MBMS session stop** is the point at which the BM-SC determines that there will be no more data to send for some period of time. + +**Data transfer** is the phase when MBMS data are transferred to the UEs. + +**MBMS service availability** is the phase between start of service announcement and the end of the last session or stop of service announcement. + +**MBMS Iu data bearer** denotes the data bearer established between SGSN and RNC to transport MBMS data + +**MBMS radio bearer** denotes the data bearer established between RNC and UE(s) to transport MBMS data + +**MBMS RAB** denotes both, the MBMS Iu data bearer and the MBMS radio bearer + +**MBMS Service Context** contains the necessary information for the UTRAN to control the MBMS Service in UTRAN. + +**MBMS Activated Services:** a set of services made up of those in MBMS multicast mode that the UE has joined as well as those in MBMS broadcast mode that the UE is interested in receiving. + +**MBMS Selected Services:** a subset of the MBMS activated services in MBMS Broadcast mode for which the UE applies RRC procedures to inform UTRAN that the service has been selected (by upper layers). + +**MBMS Iu signalling connection** denotes the signalling connection established between the RNC and the CN node to serve one MBMS Service Context. + +**MBMS Service Announcement:** Mechanism to allow users to be informed about the MBMS services available [4] + +**Pool area:** see definition in ref.[6] + +**MBMS Multicast Service Activation:** see description in ref.[4] + +**Critical Information:** MBMS Neighbouring Cell Information, MBMS Radio Bearer Information and MBMS Service Information sent on MCCH. + +**Non-critical information:** MBMS Access Information sent on MCCH. + +**MBMS Service Area:** The area in which a specific MBMS session is made available. Each transmission and retransmission of an MBMS session of an MBMS Bearer Service may be made available to a different MBMS Service Area. The MBMS Service Area is described by a list of MBMS Service Area IDs, where each MBMS Service Area ID represents a group of cells. The definition of an MBMS Service Area ID is independent of an MBMS session, and of an MBMS Bearer Service. [4] + +**L1-combining schedule:** Indicates when the soft combining is applicable between the specific S-CCPCH of the cell and the specific S-CCPCH of the neighbouring cell. + +**MBMS Single Frequency Network:** A simulcast transmission technique realised by transmission of identical waveforms at the same time via a group of cells covering a geographic area. + +**MBSFN mode:** In order to achieve higher spectral efficiency synchronized cells operate in MBSFN mode which implies that they transmit exactly the same content over an area that is seen as one MBSFN cell by the UE. + +**MBSFN cluster:** Set of cells operating in MBSFN mode providing only MBMS service in PtM mode and seen as one cell by a UE. + +**MBMS service transmission schedule:** Indicates when the specific MBMS service is expected to be transmitted in the cell in specific S-CCPCH. The information is transmitted on MSCH + +**S-CCPCH:** In case of TDD, the S-CCPCH refers to the CCTrCH carrying FACH. In case of 3.84 Mcps TDD MBSFN IMB, the S-CCPCH refers either to S-CCPCH frame type 1 or S-CCPCH frame type 2, or both S-CCPCH frame type 1 and S-CCPCH frame type 2. + +**UE Link** denotes the stored information in the RNC on MBMS services joined by the UE in the state other than URA\_PCH in the course of the UE Linking procedure. + +**URA Link** denotes the stored information in the RNC on MBMS services joined by a UE in URA\_PCH state in the course of the URA Linking procedure. + +**MBMS Master RNC:** role an RNC can take with respect to one or more specific MBSFN cluster(s). MRNC may be used for Inter-RNC MBSFN operation whenever dynamic synchronization of radio resources used for MBMS services is centrally controlled. There is only one MBMS Master RNC for any MBSFN cluster, which may control one or more MBSFN cluster(s). The MRNC has the overall control of the logical resources of the RNSs that are used for MBSFN operation within the MBSFN cluster(s). + +**Synchronisation Sequence:** Each SYNC PDU contains a time stamp which indicates the start time of the synchronisation sequence. Each synchronisation sequence has the same duration which is configured in the BM-SC and the RNCs operating in inter-RNC synchronisation mode. + +**Synchronisation Period:** The synchronisation period provides the time reference for the indication of the start time of each synchronisation sequence. The time stamp which is provided in each SYNC PDU is a relative value which refers to the start time of the synchronisation period. The duration of the synchronisation period is configurable. + +## 3.2 Symbols + +(void) + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TS 21.905 [1] and the following apply: + +| | | +|-----------------|---------------------------------------------------------| +| CELL_DCH | | +| CELL_FACH | | +| FFS | For Further Study | +| FLC | Frequency Layer Convergence | +| IMB | Integrated Mobile Broadcast | +| LCI | Layer Convergence Information | +| MBMS | Multimedia Broadcast Multicast Service | +| MBSFN | MBMS over a Single Frequency Network | +| MBMS service ID | Multimedia Broadcast Multicast Service service Identity | +| MBMS Session ID | Multimedia Broadcast Multicast Service session identity | +| MCCH | MBMS point-to-multipoint Control Channel | +| MICH | MBMS notification Indicator Channel | +| MRNC | MBMS Master RNC | +| MSCH | MBMS point-to-multipoint Scheduling Channel | +| MTCH | MBMS point-to-multipoint Traffic Channel | +| NI | Notification Indicator | +| PL | Preferred Layer | +| p-t-p | Point-to-Point | +| p-t-m | Point-to-Multipoint | +| PF | Probability Factor | + +# --- 4 Background and introduction + +The Introduction of the Multimedia Broadcast Multicast Service in UTRA describes techniques for optimised transmission of MBMS bearer service in UTRA such as point-to-multipoint transmission, selective combining and transmission mode selection between point-to-multipoint and point-to-point bearer. + +The Stage 1 MBMS service requirements are defined in [2] and MBMS Stage 1 user services are defined in [3]. UTRAN (and GERAN) requirements are covered in TR 25.992 [5]. The overall architecture, functional description and the reference architecture of MBMS are covered in TS 23.246 [3]. + +# --- 5 MBMS UTRAN and protocol architecture + +## 5.1 MBMS UTRAN architecture principles + +### 5.1.1 MBMS Service Context in CRNC + +Each RNC-which is controlling one or several cells within an MBMS Service area maintains an MBMS Service Context for each MBMS service. + +- 1 Each CRNC MBMS Service Context is associated with an MBMS service ID, i.e. TMGI. +- 2 The CRNC MBMS Service Context contains a list of PMM connected mode UEs which are present in one or several cells of the CRNC and which have activated the MBMS service and/or a list of URAs in which there is at least one URA\_PCH UE which has activated the MBMS service. The list includes at least the U-RNTI of the UEs in the state other than URA\_PCH and/or URA-IDs. + +NOTE: The MBMS Service Context in the CRNC contains no information about RRC Idle mode UEs. + +- 3 The MBMS Service Context is created in the CRNC either + - if the SGSN informs the RNC that a UE has activated the MBMS Service in a cell controlled by the CRNC by the UE Linking procedure. In this case, the CRNC is the SRNC of the UE, + - or if the RNC is notified of an MBMS Session Start, + - or if the RNC serves as a Drift RNC for a PMM-CONNECTED UE and receives for this UE a UE Link from the SRNC containing the MBMS Service Id of the concerned MBMS Service, + - or if the RNC receives a URA Link containing the MBMS Service Id of the concerned MBMS Service. +- 4 Each RNC which is informed by the SGSN that a UE has activated one (or several) MBMS Service(s) by the UE Linking procedure maintains an MBMS Service Context for each indicated MBMS service, irrespectively of the MBMS Service Area. +- 5 The MBMS Service Context is released by the CRNC either + - if the MBMS Service Context does not contain any UE/URA information after a UE/URA Unlinking procedure from a SGSN and there is no active MBMS Session for the concerned MBMS Service, + - or if the MBMS Service Context does not contain any UE Link/URA Link at the time of a Session Stop + - or if the RNC receives a CN De-Registration for MBMS Service +- 6 Associated functionalities: + - 6.1 Bearer type selection for MBMS transmissions based on information in the CRNC MBMS Service Context. The decision process requires inter-working with Radio Resource Management and with the UE's SRNC in the case of p-t-p bearers. + - 6.2 MBMS RB control for p-t-m bearers in each cell, based on information in the CRNC MBMS Service Context. + - 6.3 Update of the MBMS Service Context when a PMM-CONNECTED UE, which has activated an MBMS Service, has entered a cell. Update of the MBMS Service Context via Iur is performed by UE Linking. + +- 6.4 Update of the MBMS Service Context when a PMM-CONNECTED UE, which has activated an MBMS Service, has left a cell. Update of the MBMS Service Context via Iur is performed by UE Un-Linking. + +NOTE: For further details of UE linking via the Iur interface see chapter 5.1.6. + +### 5.1.2 MBMS Session start and MBMS Session Stop + +At MBMS Session Start and MBMS Session Stop the RNC receives a respective request from the CN. The MBMS Session Start Request shall contain the MBMS Service Id, MBMS Bearer Service Type and MBMS Session Attributes (MBMS Service Area Information, QoS parameters, ...). The MBMS Session Start Request triggers the RNC to notify UEs, which have activated the MBMS Service of the MBMS Session Start. The MBMS Session Stop Request may trigger the RNC to notify UEs, which have activated the MBMS Service of the MBMS Session Stop. + +The MBMS Session Start and Session Stop procedures provide the setup and release of the MBMS RAB in the following way: + +The MBMS Session Start Request shall contain all information necessary to setup an MBMS RAB. When the RNC receives an MBMS Session Start Request, it typically executes MBMS Iu data bearer set up and shall inform the sending CN node, of the outcome in the MBMS Session Start response message. + +Upon reception of MBMS Session Start Request, if the MBMS Service Context is not yet present in the RNC, the RNC shall store the MBMS Service Id. Further the RNC shall memorise the MBMS Bearer Service Type, MBMS Counting Information, MBMS Counting Information and MBMS Session Attributes (MBMS Service Area Information, QoS parameters, ...) as part of the MBMS Service Context. + +The RNC may choose not to execute the MBMS Iu data bearer setup, for a particular MBMS service, when: + +1. The RNC does not control any cell contained within the MBMS Service Area, or +2. The RNC controls at least one cell contained within the MBMS Service Area and a list of PMM-Idle Mode UEs is included in MBMS Session Start but no RA's contained within the list are under the control of the RNC + +The RNC may not execute the MBMS Iu data bearer setup for a given Iu interface in case of Iu-flex. In those cases the CN node shall be informed accordingly. + +In case of Iu-flex, the RNC might receive more than one MBMS Session Start Request for an MBMS Service and shall not set up more than one MBMS Iu bearer for a certain MBMS Service towards a pool area. + +When the RNC receives an MBMS Session Stop Request it shall release the associated MBMS RAB resources. + +The MBMS Session Start and Session Stop procedures serve to establish and release the MBMS Iu signalling connection. + +### 5.1.3 MBMS Iu bearer + +For each MBMS service, data is transferred via an MBMS RAB between the SGSN and the UE. For each MBMS service, data is transferred via one MBMS Iu bearer between SGSN and the RNC in the whole MBMS Service area. Signalling messages specific for an MBMS Service are transferred via one dedicated MBMS Iu signalling connection between the RNC and the SGSN. + +- 1 One MBMS Iu bearer is established per MBMS service at MBMS Session Start. +- 2 Regarding Iu-flex the RNC shall not set up more than one MBMS Iu bearer. +- 3 Because of the dedicated channels and Iur mobility, there is a need to send MBMS data to an RNC which is not necessarily part of the MBMS Service area. +- 4 The MBMS Iu bearer on Iu is established per MBMS service and not per UE individually. +- 5 Each PMM-CONNECTED mode UE with an activated MBMS service has its UE context bind to the MBMS Iu bearer. +- 6 There could be several MBMS RBs linked to one MBMS Iu bearer (i.e. one MBMS Iu bearer on Iu maybe mapped to multiple DTCH and/or or p-t-m traffic channels over the radio -interface). + +### 5.1.4 MBMS Iub bearer + +The existing FACH transport channel mechanism over Iub is to be used in case of p-t-m MBMS transmission. + +### 5.1.5 Mapping of MBMS Iu bearer to p-t-p and p-t-m connections + +The service specific MBMS RAB on Iu may be mapped to p-t-m bearers in order to provide MBMS data via common channels. + +- 1 The MBMS control function in the CRNC may decide to establish a p-t-m connection, if the number of counted MBMS users in a cell exceeds a certain operator-defined threshold or if the MBMS Counting Information indicates that MBMS Counting procedures are not applicable. +- 2 The MBMS control function in the CRNC may decide to establish a p-t-m connection depending on the congestion scenario expected for a specific cell (e.g. in hotspot areas where no bearer type switching is needed). and/or the MBMS service characteristics (e.g. session duration time) on a per cell basis. +- 3 The MBMS control function in the CRNC may, through a configurable parameter enable/disable bearer type switching and the associated procedures on a per cell basis. +- 4 The MBMS control function in the CRNC establishes an MBMS RB by sending service specific signalling messages (e.g. MBMS RB Setup message) to all the UEs in the cell listening MBMS point-to-multipoint control channel (MCCH). UEs with activated service(s) may then execute the RB set-up. +- 5 MBMS data is transferred on an MBMS point-to-multipoint traffic channel (MTCH) to all the UEs which have executed the RB setup. +- 6 The MBMS control function in the CRNC releases the MBMS RB (e.g. MBMS RB Release) when the data transfer has been finished or it has been interrupted by the CRNC. +- 7 p-t-p transmission of MBMS data should use the DTCH as defined for other dedicated services. +- 8 p-t-m transmission of MBMS data applies to all RRC states and modes. + +### 5.1.6 UE Linking/De-linking + +UE Linking denotes the process where a UE, which has joined one or several MBMS services, is linked to one or several MBMS service context in the RNC. + +MBMS UE linking procedure in the SRNC is performed in following cases. + +1. When the UE, which has joined an MBMS service, is moved to PMM-CONNECTED and sets up a PS RAB This may happen at any point in time during the whole MBMS service availability (i.e. before, during and between MBMS sessions). +2. When the UE joins an MBMS service and is in PMM-CONNECTED due to an existing PS RAB. This may happen at any point in time during the whole MBMS service availability (i.e. before, during and between MBMS sessions). +3. When the UE is moved to PMM-CONNECTED only for MBMS purpose, e.g. to respond to counting/recounting indication or respond to p-t-p bearer indication from RNC. This may happen at any point in time during MBMS sessions. +4. When the UE is moved to PMM-CONNECTED and the UE provides MBMS Selected Services Information to the RNC. + +Keeping UEs in PMM-CONNECTED only for MBMS between sessions is implementation specific. The UE linking in the SRNC for services delivered over MBMS Multicast mode is performed via UE dedicated Iu procedures. An entry for the UE is added to the related MBMS service context(s) in the SRNC. If an MBMS service context doesn't exist yet it needs to be created. + +In cases where a UE is present in a cell under the control of a drift RNC, the UE Linking is performed via Iur in the following way. + +1. When the UE, which has activated one or several MBMS services, is in CELL\_DCH state and starts to consume radio resources from one or several cells controlled by the DRNC, MBMS UE Linking in the DRNC is performed via UE dedicated Iur procedures. After that the DRNC shall update the MBMS Service context on the request of every radio link setup/release from the SRNC. +2. When the UE, which has activated one or several MBMS services, is in CELL\_FACH state and starts to consume radio resources from one cell controlled by the DRNC, MBMS UE Linking in the DRNC is + +performed via UE dedicated Iur procedures. After that the DRNC shall update the MBMS Service context in the DRNC at every intra-DRNC cell change without the need to receive UE Link from the SRNC. + +3. If the UE is in CELL\_DCH and CELL\_FACH state and there is no dedicated RNL signalling activity ongoing for this UE and UE Linking is performed in the SRNC for an MBMS Service, MBMS UE Linking in the DRNC is performed via the MBMS Attach procedure. +4. If the UE is in CELL\_PCH and moves to a cell within the DRNC area for the first time, the MBMS UE Linking in the DRNC is performed. The cell the UE moved to is indicated to the DRNC. After that at every intra-DRNC cell change the DRNC shall update the MBMS Service context in the DRNC without the need to receive UE Link from the SRNC. +5. If the UE is in CELL\_PCH and there is no mobility related signalling activity ongoing for this UE and UE Linking is performed in the SRNC for an MBMS Service, MBMS UE Linking in the DRNC is performed via the MBMS Attach procedure. +6. If the UE is in RRC connected mode and UE Linking is performed in the SRNC for an MBMS Service and a session of this MBMS Service is ongoing UE Linking in the DRNC needs to be performed immediately. + +At MBMS UE linking in the DRNC the MBMS service context in the DRNC needs to be updated. If an MBMS service context does not exist yet then it shall be created and if needed, DRNC can acquire the APN and IP Multicast Address from the SRNC for the specific service via Information Exchange procedure. + +UE De-linking denotes the process where a UE, which has joined MBMS service(s), is removed from one or several MBMS service contexts in the RNC. + +MBMS UE De-linking procedure in the SRNC is performed in following cases. + +1. When the UE has left the MBMS service and is in PMM-CONNECTED due to an existing PS RAB. This may happen at any point in time during the whole MBMS service availability (i.e. before, during and between MBMS sessions). +2. When the UE sends new MBMS Selected Services Information to the RNC omitting an MBMS service which is identified on the MCCH. +3. When CN decides to de-link a certain PMM-CONNECTED mode UE due to e.g. error cases. + +MBMS UE De-linking in the SRNC for services in MBMS Multicast mode is performed via UE dedicated Iu procedure. The entry for the UE is removed from the concerned MBMS service context(s) in the SRNC. + +MBMS UE De-linking procedure in the DRNC is performed via Iur in the following way: + +1. If the UE is in CELL\_DCH or CELL\_FACH state and stops consuming the radio resources from one or several cells controlled by the DRNC, MBMS UE is De-linked from the MBMS Service Context in the DRNC via UE dedicated Iur procedure. +2. If the UE is in CELL\_DCH or CELL\_FACH state and there is no dedicated RNL signalling activity ongoing for this UE and UE De-linking is performed in the SRNC for an MBMS Service, MBMS UE De-linking in the DRNC is performed via the MBMS Detach procedure. +3. If the UE is in CELL\_PCH and leaves for a cell out of the DRNC area the UE is delinked from the MBMS Service context in the DRNC via the MBMS Detach procedure. The cell the UE moved out of is indicated to the DRNC. +4. If the UE is in RRC connected mode and UE De-linking is performed in the SRNC for an MBMS Service and a session of this MBMS Service is ongoing UE De-linking in the DRNC needs to be performed immediately. + +### 5.1.7 RNC Registration + +RNC Registration for a certain MBMS Service denotes the process where the CN becomes aware of an RNC hosting UEs, which have activated that MBMS Service. + +Due to UE mobility, a RNC with no MBMS Service Context, can be informed that a PMM-CONNECTED UE, which has entered the cell, has activated an MBMS Service by means of the MBMS UE Linking procedure via the Iur + +interface. Then the RNC informs the CN that it would like to receive MBMS Session Start Request messages when applicable for the concerned MBMS Service by sending MBMS Registration Request message. + +It results in the set-up of a corresponding MBMS distribution tree, but it does not result in the establishment of Iu user plane, which will be established by the MBMS Session Start procedure. + +1. Implicit Registration + - RNC Registration for Serving RNCs is performed implicitly, i.e. due to UE linking and MBMS Multicast Service Activation. No explicit registration procedure needs to be performed. +2. Explicit Registration + - RNC Registration for Drift RNCs is performed explicitly if an RNC becomes a Drift RNC for a UE, which has activated an MBMS service and has no MBMS Service Context for that MBMS Service. + - RNC Registration for Drift RNCs is performed explicitly if an RNC is no longer the SRNC of any connected UE which has activated an MBMS service, but hosts at least a UE which consumes radio resources of the RNC via Iur. This shall happen only before sessions or between sessions. + - The DRNC will perform a registration towards its default CN node only. + +### 5.1.8 RNC De-Registration + +RNC De-Registration for a certain MBMS Service denotes the process where the CN becomes aware that an RNC registered at a CN node does not host any more PMM-CONNECTED UEs which have activated that MBMS Service. + +- Implicit RNC De-Registration + - RNC De-Registration for Serving RNCs is performed implicitly, i.e. due to UE Unlinking and MBMS Multicast Service Deactivation. No explicit de-registration procedure needs to be performed. +- Explicit RNC De-Registration + - RNC De-Registration for Drift RNCs is performed explicitly if a RNC is not acting as a Serving RNC and has ceased to act as a Drift RNC for UEs which have activated an MBMS service, it will perform a de-registration towards the CN node it was registered to. + - The timing of RNC De-Registration is implementation specific. + +NOTE: When the Drift RNC performs the explicit De-registration, the Implicit registration may still remain and in that case Iu data bearer should not be removed. + +### 5.1.9 CN De-Registration + +CN De-Registration denotes the process where the CN informs the RNC that a certain MBMS service is no longer available. CN De-Registration should result in releasing of all associated MBMS Service Contexts and resources. + +The CN De-Registration procedure serves to release the MBMS Iu signalling connection. + +### 5.1.10 URA Linking/De-linking + +URA Linking denotes the process where a URA, which contains one or more cells in which at least one URA\_PCH UE has joined the MBMS service or has passed MBMS Selected Service Information about the MBMS service, is linked to an MBMS service context in the RNC. An entry for the URA is added to the MBMS service context in the RNC. + +If the UE in URA\_PCH state, which has activated one or several MBMS Services, is present within a URA containing one or more cells that are controlled by one or more drift RNCs, the URA Linking is performed in the following way. + +1. If the UE is in URA\_PCH, having activated one or more MBMS services, is the first UE for the particular MBMS service to move to a URA which contains one or more cells that are controlled by one or more DRNCs, the URA is linked to the MBMS Service context in each applicable DRNC. The URA the UE moved to will be indicated. +2. As long as the SRNC serves UEs in URA\_PCH in URAs containing cells controlled by one or more DRNCs, the SRNC shall keep the other RNCs informed about every URA in which UEs having activated certain MBMS services have to be notified. This is done when the first UE enters the URA, by indicating to the other RNCs a list of URAs and the corresponding MBMS Services via MBMS Attach procedure. + +NOTE: Bullet points 1 and 2 above may be merged in a future version of this document. + +At MBMS URA linking in the RNC the MBMS service context in the RNC needs to be updated. If an MBMS service context does not exist yet then it shall be created and acquire the APN and IP Multicast Address from the SRNC for the specific service via Information Exchange procedure. + +URA De-linking denotes the process where a URA is removed from one or several MBMS service contexts in the RNC. + +1. If the UE is in URA\_PCH and, for the particular MBMS service, is the last UE to leave a URA which contains one or more cells controlled by one or more DRNCs the URA is de-linked from the MBMS Service context in each applicable DRNC via the MBMS Detach procedure. + +### 5.1.11 IP Multicast Distribution + +To improve the transport efficiency the IP Multicast may be used for the MBMS payload distribution in the backbone network between the GGSN and the RNCs, bypassing the SGSN. + +The GGSN allocates during the session start the Transport Layer Address used for the IP-multicast and the DL TEID used for the Iu Transport association. The RNCs will receive these parameters from SGSN in the Session Start message as part of the MBMS session attributes. + +The RNC may accept or reject the proposed IP Multicast distribution in the MBMS Session Start Response to the SGSN. If accepted the RNC shall report the channel (IP Multicast and Source address) to the backbone in order to join the bearer service multicast distribution. If one or more downstream RNC nodes doesn't accept IP Multicast distribution, the SGSN will establish an MBMS RAB which the IP multicast distribution is not applied, to related RNCs. + +The MBMS payload is forwarded by the GGSN towards the IP Multicast address. The RNCs joined to that IP Multicast address will receive the user data packets (SYNC PDU) together with the synchronisation-related information in header part of SYNC PDU. The information in header part of SYNC PDU is delivered to allow the softcombining and MBSFN transmission across the RNCs. The details of inter-RNC synchronization are described in section 7.1B. + +In case the header compression is used in MBMS PtM mode for an MBMS stream the compression is done in BM-SC. The usage of header compression is configured in advance in the BM-SC and the RNC is receiving the information during the MBMS Session start as part of the session attributes. In case header compression is configured, the MBMS user data packets forwarded from BM-SC to RNCs via GGSN will contain in addition to the synchronisation-related information and PDCP protocol information, the full IP header of the payload and the payload with compressed header. The RNC using MBMS PtP mode in a cell may process the UE dedicated RoHC for the full IP header of the payload and replace the compressed header of PtM mode with it. + +## 5.2 MBMS Uu Principles + +### 5.2.1 MBMS Service States in UE + +The MBMS bearer service has following service states in the UE: + +1. Not active, UE has not joined any MBMS multicast service or not activated the broadcast mode of the MBMS +2. Not active, UE has joined at least one MBMS multicast service and/or activated the broadcast mode of the MBMS, but MBMS SYSTEM INFORMATION is not broadcasted on BCCH. +3. Active, UE has joined at least one MBMS multicast service and/or activated the broadcast mode of the MBMS, but any of the services that UE has joined (interested in broadcast mode) is not being transmitted. UE monitors MICH to find modifications in the MCCH as defined in 5.1.6 +4. Active; at least one MBMS service appearing in the list of MBMS Activated Services, is received on p-t-m + - UE is receiving MBMS transmission on MTCH + - UE is using DRX based on scheduling information informing that coming MTCH transmission is not in the interest of the UE. +5. Active; at least one MBMS service is received on p-t-p + +6. Active; at least one MBMS service is received on p-t-p and at least one MBMS service is received on p-t-m. (only valid if UE has capability to support this combination) + +When MBMS transmission is started in cell the UE moves from state 3 to either state 4 or state 5 (6), depending on p-t-p transmission mode and after MBMS transmission ends in the cell, the UE moves from state 4 or state 5 (6) to state 3. + +### 5.2.2 One PDCP and RLC entity shared among multiple cells within one RNS + +For each MBMS service, a group of multiple cells belonging to one RNS shares one PDCP entity and RLC entity over p-t-m transmission. The group of multiple cells is called 'MBMS Cell Group'. + +1. There are one or more MBMS Cell Groups per RNS. The MBMS Cell Groups are managed by the CRNC. +2. There are one or more cells pertaining to the same RNS for one MBMS Cell Group. +3. The MBMS Cell Group identity is used to uniquely identify a group of multiple cells, which for each MBMS service share the same PDCP entity and RLC entity within an RNS. + +In case the MBMS combining methods are used across multiple RNSs for an MBMS service, the RNSs belong to the same IP Multicast group used for the MBMS user data distribution from the GGSN to CRNCs. One common PDCP entity for header compression is used for MBMS P-t-M transmission among the RNSs being part of the IP Multicast group. + +The RLC entity for p-t-m transmission is shared by a group of multiple cells belonging to one RNS. The RLC entities, within the RNSs shall be synchronized to each other in way that they, process the user data in the same manner with the help of information delivered by the SYNC-protocol to RNS. + +### 5.2.3 MCCH Information Scheduling + +The MCCH information will be transmitted based on a fixed schedule. This schedule will identify the TTI containing the beginning of the MCCH information. The transmission of this information may take a variable number of TTIs and the UTRAN should transmit MCCH information in consecutive TTIs. The UE will keep receiving the S-CCPCH until: + +- It receives all of the MCCH information, or +- It receives a TTI that does not include any MCCH data, or +- The information contents indicate that further reception is not required (e.g. no modification to the desired service information). + +Based on this behaviour, the UTRAN may repeat the MCCH information following a scheduled transmission in order to improve reliability. The MCCH schedule will be common for all services. + +The entire MCCH information will be transmitted periodically based on a "repetition period". The "modification period" will be defined as an integer multiple of the repetition period. The MBMS ACCESS INFORMATION may be transmitted periodically based on an "access info period". This period will be an integer divider of the "repetition period". + +MCCH information is split into critical and non-critical information. The critical information is made up of the MBMS NEIGHBOURING CELL INFORMATION, MBMS SERVICE INFORMATION and MBMS RADIO BEARER INFORMATION. The non-critical information corresponds to the MBMS ACCESS INFORMATION. Changes to critical information will only be applied at the first MCCH transmission of a modification period and in the beginning of each modification period UTRAN transmits the MBMS CHANGE INFORMATION including MBMS services ids whose MCCH information is modified at that modification period. MBMS CHANGE INFORMATION is repeated at least once in each repetition period of that modification period. Changes to non-critical information could take place at any time. + +The Figure 5.2.3 below illustrates the schedule with which the MBMS SERVICE INFORMATION and RADIO BEARER INFORMATION would be transmitted. Different colours indicate potentially different MCCH content. + +![Figure 5.2.3: MCCH Information Schedule. This diagram shows the timing of MCCH information changes. A horizontal timeline represents time. Above the timeline, two 'Modification period' intervals are marked with double-headed arrows, separated by vertical dashed lines. Within each modification period, a 'Repetition period' is indicated by a double-headed arrow starting from the beginning of the period. Below the timeline, a series of colored blocks (purple, yellow, green, red) represent MCCH transmissions. An arrow labeled 'Change information' points to the first yellow block at the start of the first modification period.](8307f6b04df072c9332f9987e034272c_img.jpg) + +Figure 5.2.3: MCCH Information Schedule. This diagram shows the timing of MCCH information changes. A horizontal timeline represents time. Above the timeline, two 'Modification period' intervals are marked with double-headed arrows, separated by vertical dashed lines. Within each modification period, a 'Repetition period' is indicated by a double-headed arrow starting from the beginning of the period. Below the timeline, a series of colored blocks (purple, yellow, green, red) represent MCCH transmissions. An arrow labeled 'Change information' points to the first yellow block at the start of the first modification period. + +Figure 5.2.3: MCCH Information Schedule + +### 5.2.4 MBMS Notification + +The MBMS notification mechanism is used to inform UEs of an upcoming change in critical MCCH information. Notifications are based on service groups. The mapping between service IDs and service groups is specified in [11]. + +The MBMS notification indicators will be sent on an MBMS specific PICH, called the MICH. A single MICH frame will be able to carry indications for every service-group. + +Critical MCCH information can only be changed at the beginning of a modification period as described in Section 5.2.3. The MBMS notification indicator corresponding to the service group of every affected service shall be set continuously during the entire modification period preceding the first change in MCCH information related to a given service. Subsequent changes in the MCCH information in the next modification period related to the same service can be signalled on the MCCH. + +UEs which are not receiving any MBMS service on MTCH or p-t-p channel are free to read the MBMS notification at any time; however the modification interval shall be long enough so that UEs are able to reliably detect it even if they only receive the MICH during their regular Release '99 paging occasions. + +Upon detecting the MBMS notification indication for a service group, UEs with an activated service corresponding to this group shall start reading the MCCH at the beginning of the next modification period. The UE shall read at least MBMS CHANGE INFORMATION. + +The Figure 5.2.4 below illustrates the timing relation between the setting of the MICH and the first MCCH critical information change. The green colour for the MICH indicates when the NI is set for the service. For the MCCH, different colours indicate MCCH content related to the notification of different services. + +UEs, which are receiving MBMS service(s) on MTCH in idle mode or URA\_PCH, CELL\_PCH, or CELL\_FACH state shall read the MCCH at the beginning of the each modification period to receive the MBMS CHANGE INFORMATION, which will indicate MBMS service IDs and optionally MBMS Session ID whose MCCH information is modified at that modification period. If MBMS service Id and optionally MBMS Session ID, which UE has activated, is indicated in MBMS CHANGE INFORMATION the UE shall read the rest of the MCCH information. + +![Figure 5.2.4: Illustration of MICH timing relative to Modification period. This diagram shows the relationship between MICH and MCCH timing. The top timeline represents the MICH, with a long red bar and a green segment. The green segment starts at the beginning of the first 'Modification period' and continues through the start of the second. The 'Repetition period' is indicated by a double-headed arrow. The bottom timeline represents the MCCH, with a series of colored blocks (yellow, blue, red). An arrow labeled 'Change Information' points to the first yellow block at the start of the first modification period. Vertical dashed lines align the start of modification periods and the start of the green MICH segment.](6f659142d4789aa889184459f884787e_img.jpg) + +Figure 5.2.4: Illustration of MICH timing relative to Modification period. This diagram shows the relationship between MICH and MCCH timing. The top timeline represents the MICH, with a long red bar and a green segment. The green segment starts at the beginning of the first 'Modification period' and continues through the start of the second. The 'Repetition period' is indicated by a double-headed arrow. The bottom timeline represents the MCCH, with a series of colored blocks (yellow, blue, red). An arrow labeled 'Change Information' points to the first yellow block at the start of the first modification period. Vertical dashed lines align the start of modification periods and the start of the green MICH segment. + +Figure 5.2.4: Illustration of MICH timing relative to Modification period + +### 5.2.5 MBMS Counting + +MBMS Counting is used to determine the optimum transmission mechanism for a given service. + +1. The need for counting is indicated in the notification, and achieved by requesting UEs, belonging to the same MBMS service group, to respond to counting by sending MBMS COUNTING RESPONSE signalling flow to CRNC. + - a. For UEs in idle mode the counting response refers to the RRC connection establishment procedure. + - b. For UEs in URA\_PCH, or CELL\_PCH state the counting response refers to cell update procedure + - c. For UEs in CELL\_FACH state the counting response refers to signalling on CCCH or DCCH. +2. The exact number of UEs that need to respond to counting is an RRM issue. +3. Since it is desirable in a specific cell, to avoid bringing a large number of UEs for counting purposes to RRC connected mode at the same time (RACH load, etc), RRM may control the load due to the RRC connection establishment requests, by setting an access "probability factor". For UEs in PMM connected mode the UTRAN may set different "probability factor" than for UEs in idle mode. +4. Following counting, the number of subscribers that need to be maintained in RRC connected mode or for which the RNC releases their connection, is also an RRM issue. In Broadcast Mode, the RNC may also decide to reject the RRC connection establishment and indicate during this reject that counting has been completed. +5. For a given MBMS service, the counting indication in the notification may be switched on and off, on per-cell basis. +6. The RNC may use notification to indicate counting during an ongoing MBMS session (term used is re-counting). +7. The RNC receives via Iu from CN information (MBMS service ID) about UEs who are in RRC Connected mode, and have joined the MBMS service. This information may be used for counting purposes. + +The MBMS counting function includes a mechanism by which the UTRAN can prompt UEs with a given activated service to become RRC connected. This procedure is only applicable for UEs in idle mode and relies on the MBMS ACCESS INFORMATION transmitted on the MCCH. The probability factor indicates the probability with which UEs need to attempt an RRC connection procedure. + +In order to trigger counting for a given service, the UTRAN may use the regular MBMS notification mechanism outlined in section 5.2.4 to force UEs with that service activated to read the MCCH information. + +Once a UE detects that the counting procedure is on-going for the specific service it wants to receive, it will attempt to respond to the counting based on the probability factor included in the MCCH. If the response to counting is for a service identified in the list of MBMS Selected Services, the UE should provide the MBMS Service ID in the response. + +Also, the UE will keep receiving the MBMS ACCESS INFORMATION at every access info period until the UE successfully responds to the counting or counting is no longer required. Whenever it receives new MBMS ACCESS INFORMATION the UE will update its probability factor with the new value. + +The Figure 5.2.5 below illustrates this mechanism. The green colour for the MICH indicates when the NI is set for the service. The green colour for the MBMS ACCESS INFORMATION indicates that the counting procedure is on-going and that UEs need to establish an RRC connection based on the included probability factor (PF). For the critical MCCH info, different colours indicate potentially different content. + +![Figure 5.2.5: Illustration of Access Info period during MBMS counting. The diagram shows three horizontal timelines: MICH, ACCESS INFO, and Critical Info. The MICH timeline has a green segment followed by a red segment, with a 'Modification period' indicated by a double-headed arrow. The ACCESS INFO timeline shows a sequence of blocks: PF0 (green), PF0 (green), PF1 (green), PF2 (green), and three red blocks labeled 'Access Information'. Below these, 'UE Access with PF0', 'UE Access with PF1', and 'UE Access with PF2' are indicated. The 'Access info period' is marked by a double-headed arrow. The Critical Info timeline shows a yellow block followed by a blue block labeled 'Change Information', and then three blue blocks labeled 'MCCH Information'. A 'Repetition period' is indicated by a double-headed arrow between the first and second MCCH Information blocks.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +Figure 5.2.5: Illustration of Access Info period during MBMS counting. The diagram shows three horizontal timelines: MICH, ACCESS INFO, and Critical Info. The MICH timeline has a green segment followed by a red segment, with a 'Modification period' indicated by a double-headed arrow. The ACCESS INFO timeline shows a sequence of blocks: PF0 (green), PF0 (green), PF1 (green), PF2 (green), and three red blocks labeled 'Access Information'. Below these, 'UE Access with PF0', 'UE Access with PF1', and 'UE Access with PF2' are indicated. The 'Access info period' is marked by a double-headed arrow. The Critical Info timeline shows a yellow block followed by a blue block labeled 'Change Information', and then three blue blocks labeled 'MCCH Information'. A 'Repetition period' is indicated by a double-headed arrow between the first and second MCCH Information blocks. + +**Figure 5.2.5: Illustration of Access Info period during MBMS counting** + +For every UE brought to RRC connected state for the purpose of counting, UTRAN will initiate the PMM Connection establishment procedure and will obtain from CN the set of MBMS services these users have joined. + +Counting for on-going services (re-counting) will rely on the same scheduling of the MCCH information. + +### 5.2.6 MBMS Radio Bearer Release in the UE + +The UE releases the MBMS RB by using one of the following mechanisms: + +- Explicit MBMS RB Release +- Implicit MBMS RB Release + +The Explicit MBMS RB Release mechanism allows UTRAN to explicitly indicate to MBMS UEs that an MBMS Radio Bearer should be released. For p-t-m transmissions the Explicit MBMS RB Release indication is contained within the MBMS SERVICE INFORMATION signalling flow. For p-t-p transmission the release of MBMS radio bearers is completed in the same way as for a non-MBMS radio bearer. If the Explicit MBMS RB Release indication is received, the UE releases the MBMS RB. + +The Implicit MBMS RB Release mechanism applies only to p-t-m transmission and enables a UE to release the MBMS Radio Bearer without receiving the Explicit MBMS RB Release. The UE identifies Implicit MBMS RB release if it detects that the RB is not present in the MBMS SERVICE INFORMATION signalling flow. + +### 5.2.7 MBMS Session Repetition + +In the case that the BM-SC repeats MBMS sessions (send multiple time identical content), the MBMS service Id and MBMS session Id is used to identify specific MBMS service and session. The validity of the session Id is handled on the MBMS application layer between the BM-SC and the UE. If UTRAN receives the MBMS session ID in session start, the UTRAN should: + +- include MBMS session Id in critical and non critical information send on MCCH +Note: The non-critical information may contain index referring to critical information, avoiding repetition of MBMS service and session Id in non-critical information. + +If the UE has already received correctly the data of the MBMS session, which is being indicated on MCCH, the UE may: + +- ignore FLC by not applying the Layer Convergence Information +- ignore counting procedure in Idle, URA\_PCH, CELL\_PCH, and CELL\_FACH state +- ignore p-t-m MBMS RB setup signalled on MCCH +- ignore p-t-p MBMS RB indication signalled on MCCH +- reject the p-t-p RB setup for MBMS service, signalled on DCCH + +In the case that UTRAN receives reject from the UE to the p-t-p RB setup for MBMS service on DCCH, the UTRAN should not try to re-establish p-t-p RB setup for that MBMS service and session. + +In the case that the UE has accepted the p-t-p RB for repeated MBMS session the UE shall receive the complete session. + +### 5.2.8 MBMS Service Prioritisation + +The CN may assign the Allocation and Retention Priority for the MBMS bearer service. The Allocation and Retention Priority allows for prioritisation between MBMS bearer services and between MBMS bearer services and non MBMS bearer services in the UTRAN. + +The UE may assign internally different priorities for different MBMS services to prioritise MBMS and non MBMS service reception. In case that UE has no capability to receive simultaneously, the dedicated non MBMS service and the MBMS service and the MBMS service has priority over the non MBMS service the UE may: + +- initialise signalling with CN on NAS layer to stop reception of dedicated non MBMS service + +If the UE has no capacity on receiving all MBMS services, which it has activated and which are transmitted simultaneously on p-t-m RBs, the UE may + +- stop autonomously ongoing reception of lower priority MBMS service +- act on MCCH message assigned to the highest priority MBMS service +- start autonomously the reception p-t-m RB of the highest priority MBMS service + +If the reception p-t-p RB of the lower priority MBMS service is blocking the reception of p-t-m RB of the higher priority MBMS service the UE may: + +If p-t-p RB is being established + +- reject the setup of p-t-p MBMS RB + +If the UTRAN receives reject message UTRAN should not try to re-establish p-t-p RB setup for that MBMS service and session. + +If p-t-p RB is already existing + +- request the release of p-t-p MBMS RB from the UTRAN or only indicate frequency of higher priority MBMS service + +If the UTRAN receives release request message UTRAN may release the p-t-p MBMS RB. + +## 5.3 Protocol structure + +### 5.3.1 MBMS User Plane Protocol Stack Architecture + +![Figure 5.3.1-1: Protocol Stack for MTCH. This diagram shows the protocol stack for MTCH in MBMS. It consists of three main entities: UE, Node B, and Controlling RNC. The UE and Controlling RNC have identical stacks: PDCP, RLC, MAC, and PHY. The Node B has a PHY layer. Arrows indicate data flow from the Controlling RNC down through its stack, then through the Node B's PHY layer, and up through the UE's stack. The PDCP, RLC, and MAC layers in the UE and Controlling RNC are shown with dashed outlines.](a24e89a6fe9bb70c83f8bf5202baba95_img.jpg) + +Figure 5.3.1-1: Protocol Stack for MTCH. This diagram shows the protocol stack for MTCH in MBMS. It consists of three main entities: UE, Node B, and Controlling RNC. The UE and Controlling RNC have identical stacks: PDCP, RLC, MAC, and PHY. The Node B has a PHY layer. Arrows indicate data flow from the Controlling RNC down through its stack, then through the Node B's PHY layer, and up through the UE's stack. The PDCP, RLC, and MAC layers in the UE and Controlling RNC are shown with dashed outlines. + +**Figure 5.3.1-1: Protocol Stack for MTCH** + +Figure 5.3.1-1 illustrates the protocol termination for MTCH in MBMS, which is used in p-t-m transmission. + +If configured by CRNC the PDCP sub-layer performs header compression/decompression for the MBMS traffic. + +The PDCP sub-layer may operate with the RFC 3095 header compression protocol. In that case, header compression should be performed under RFC 3095 U-mode. + +In the UTRAN, for p-t-m transmission, there is one PDCP entity for each MBMS service for each MBMS Cell Group that provides the service (an MBMS Cell Group may contain one or more than one cell). + +In the UTRAN, for p-t-m transmission, there is one RLC entity for each MBMS service in each cell or cell group in case of utilization of selective combining or maximum ratio combining in TDD, and one MAC entity for each cell. + +In the UE side, there is one PDCP and RLC entity for each MBMS service in each UE. In each UE there is one MAC entity per received cell when UE is performing the selective combining between these cells. + +In case of p-t-p transmission, DTCH is used for MBMS transmission and the protocol termination for DTCH mapped on DCH and RACH/FACH are presented in [8]. + +![Figure 5.3.1-2: Protocol Stack for MTCH (P-T-M) in case of IP multicast distribution. This diagram shows the protocol stack for MTCH in MBMS for IP multicast distribution. It consists of four main entities: UE, Node B, Controlling RNC, and BM-SC. The UE has a stack of PDCP, RLC, MAC, and PHY. The Node B has a PHY layer. The Controlling RNC has a stack of RLC, MAC, and a TNL layer. Above the Controlling RNC's RLC/MAC stack is a SYNC layer. The BM-SC has a stack of PDCP, SYNC, and TNL. Arrows indicate data flow from the BM-SC down through its stack, then through the Controlling RNC's TNL and SYNC layers, then through the Controlling RNC's RLC and MAC layers, then through the Node B's PHY layer, and up through the UE's stack. The PDCP, RLC, and MAC layers in the UE are shown with dashed outlines. The PDCP, SYNC, and TNL layers in the BM-SC are also shown with dashed outlines.](2876be3592c7b4878400b85f209b2b6a_img.jpg) + +Figure 5.3.1-2: Protocol Stack for MTCH (P-T-M) in case of IP multicast distribution. This diagram shows the protocol stack for MTCH in MBMS for IP multicast distribution. It consists of four main entities: UE, Node B, Controlling RNC, and BM-SC. The UE has a stack of PDCP, RLC, MAC, and PHY. The Node B has a PHY layer. The Controlling RNC has a stack of RLC, MAC, and a TNL layer. Above the Controlling RNC's RLC/MAC stack is a SYNC layer. The BM-SC has a stack of PDCP, SYNC, and TNL. Arrows indicate data flow from the BM-SC down through its stack, then through the Controlling RNC's TNL and SYNC layers, then through the Controlling RNC's RLC and MAC layers, then through the Node B's PHY layer, and up through the UE's stack. The PDCP, RLC, and MAC layers in the UE are shown with dashed outlines. The PDCP, SYNC, and TNL layers in the BM-SC are also shown with dashed outlines. + +**Figure 5.3.1-2: Protocol Stack for MTCH (P-T-M) in case of IP multicast distribution** + +Figure 5.3.1-2 illustrates the protocol termination for MTCH in MBMS, which is used in p-t-m transmission in case of IP Multicast distribution. + +Based on the configuration in BM-SC the PDCP sub-layer may perform header compression/decompression for the MBMS traffic. + +The PDCP sub-layer may operate with the RFC 3095 header compression protocol. In that case, header compression should be performed under RFC 3095 U-mode. + +In the UTRAN, for p-t-m transmission, there is one PDCP entity for each MBMS service for each MBMS IP Multicast Group that provides the service (an MBMS IP Multicast Group may contain one or more than one RNC, see section 5.2.2). + +For p-t-m transmission there is one RLC entity for each MBMS service in each cell or in a group of multiple cells belonging to one RNS. The RLC entities, in the RNSs synchronized to each other, shall process the user data similar manner with the help of information delivered by the SYNC-protocol to RNS. There is one MAC entity for each cell. + +In the UE side, there is one PDCP and RLC entity for each MBMS service in each UE. In each UE there is one MAC entity per received cell when UE is performing the selective combining between these cells. + +In case of p-t-p transmission, DTCH is used for MBMS transmission and the protocol termination for DTCH mapped on DCH and RACH/FACH are presented in [8]. + +### 5.3.2 MBMS Control Plane Protocol Stack Architecture + +![Figure 5.3.2-1: Protocol Stack for MCCH and MSCH. This diagram shows the protocol stack for MCCH and MSCH across three entities: UE, Node B, and Controlling RNC. The UE stack consists of RRC, RLC, MAC, and PHY layers. The Node B stack consists of a single PHY layer. The Controlling RNC stack consists of RRC, RLC, and MAC layers. Arrows indicate the flow of data: from the Controlling RNC's MAC layer to the Node B's PHY layer, and from the Node B's PHY layer to the UE's PHY layer. Additionally, there are horizontal arrows between the RRC, RLC, and MAC layers of the UE and the Controlling RNC, indicating direct connections between these entities.](b2ea162a0f53d5e0504b7d28346e0754_img.jpg) + +Figure 5.3.2-1: Protocol Stack for MCCH and MSCH. This diagram shows the protocol stack for MCCH and MSCH across three entities: UE, Node B, and Controlling RNC. The UE stack consists of RRC, RLC, MAC, and PHY layers. The Node B stack consists of a single PHY layer. The Controlling RNC stack consists of RRC, RLC, and MAC layers. Arrows indicate the flow of data: from the Controlling RNC's MAC layer to the Node B's PHY layer, and from the Node B's PHY layer to the UE's PHY layer. Additionally, there are horizontal arrows between the RRC, RLC, and MAC layers of the UE and the Controlling RNC, indicating direct connections between these entities. + +**Figure 5.3.2-1: Protocol Stack for MCCH and MSCH** + +Figure 5.3.2-1 illustrates the protocol termination for MCCH and MSCH in MBMS, which are MBMS p-t-m control channels. + +MBMS functionalities are included in MAC and RRC. + +In case of p-t-p transmission, DCCH is used for MBMS and the protocol termination for DCCH mapped on DCH and FACH are presented in [8]. + +![Figure 5.3.2-2: Protocol Stack for MCCH. This diagram shows the protocol stack for MCCH across four entities: UE, Node B, Controlling RNC, and MBMS Master RNC. The UE stack consists of RRC, RLC, MAC, and PHY layers. The Node B stack consists of a single PHY layer. The Controlling RNC stack consists of RRC, RLC, and MAC layers. The MBMS Master RNC stack consists of MCCH IC and RNSAP layers. Arrows indicate the flow of data: from the Controlling RNC's RRC layer to the MBMS Master RNC's MCCH IC and RNSAP layers, and from the MBMS Master RNC's MCCH IC and RNSAP layers back to the Controlling RNC's RRC layer. There are also horizontal arrows between the RRC, RLC, and MAC layers of the UE and the Controlling RNC. Vertical arrows point from the Controlling RNC's MAC layer to the Node B's PHY layer, and from the Node B's PHY layer to the UE's PHY layer.](8ed7f57cc317f6574bec781d01ae6ad2_img.jpg) + +Figure 5.3.2-2: Protocol Stack for MCCH. This diagram shows the protocol stack for MCCH across four entities: UE, Node B, Controlling RNC, and MBMS Master RNC. The UE stack consists of RRC, RLC, MAC, and PHY layers. The Node B stack consists of a single PHY layer. The Controlling RNC stack consists of RRC, RLC, and MAC layers. The MBMS Master RNC stack consists of MCCH IC and RNSAP layers. Arrows indicate the flow of data: from the Controlling RNC's RRC layer to the MBMS Master RNC's MCCH IC and RNSAP layers, and from the MBMS Master RNC's MCCH IC and RNSAP layers back to the Controlling RNC's RRC layer. There are also horizontal arrows between the RRC, RLC, and MAC layers of the UE and the Controlling RNC. Vertical arrows point from the Controlling RNC's MAC layer to the Node B's PHY layer, and from the Node B's PHY layer to the UE's PHY layer. + +**Figure 5.3.2-2: Protocol Stack for MCCH** + +In case MRNC is used, figure 5.3.2-2 illustrates the protocol termination for MCCH in MBMS, which is MBMS p-t-m control channel. + +MBSFN MCCH Information Control function is split between MRNC and CRNC. The MRNC controls the logical resources of the RNSs that are used for MBSFN operation within the MBSFN cluster(s). The MRNC informs the CRNC of the MCCH configuration (using transfer of MCCH Information Control messages) and schedule information to be used (included in RNSAP). The CRNC performs the MCCH configuration and sends the MCCH information accordingly. + +## 5.4 MAC architecture + +### 5.4.1 UTRAN MAC Architecture to support MBMS + +![Figure 5.4.1: UTRAN MAC architecture diagram showing the flow of data and control signals through various MAC entities (MAC-hs, MAC-c/sh/m, MAC-d) and logical channels (MSCH, MCCH, MTCH, etc.) to transport channels (HS-DSCH, FACH, RACH, etc.).](d9c0a780cd22626253dab4aa41699e2f_img.jpg) + +The diagram illustrates the UTRAN MAC architecture for MBMS. It is divided into three main sections by vertical dashed lines. + +- Left Section (MAC-hs):** + - Top: MAC Control (oval). + - Middle: MAC-hs (rectangle). + - Bottom: HS-DSCH transport channels (ovals). + - Associated Downlink Signalling and Associated Uplink Signalling are shown below the transport channels. +- Middle Section (MAC-c/sh/m):** + - Top: Logical channels MSCH, MCCH, PCCH, BCCH, MTCH, MTCH, CCCH, CTCH, SHCCH (TDD only). A 'Configuration without MAC-c/sh' line is also present. + - Middle: MAC-c/sh/m (rectangle). A 'Configuration with MAC-c/sh' line connects to it. + - Bottom: Transport channels PCH, FACH, FACH, RACH, CPCH (FDD only), USCH (TDD only), USCH (TDD only), DSCH, DSCH. An 'Iub' interface is indicated between the MAC-hs and MAC-c/sh/m sections. +- Right Section (MAC-d):** + - Top: MAC Control (oval), MAC Control (oval), DCCH, DTCH, DTCH. + - Middle: MAC-d (rectangle). + - Bottom: DCH, DCH transport channels (ovals). + - The 'Iur or local' interface is indicated between the MAC-c/sh/m and MAC-d sections. + +Figure 5.4.1: UTRAN MAC architecture diagram showing the flow of data and control signals through various MAC entities (MAC-hs, MAC-c/sh/m, MAC-d) and logical channels (MSCH, MCCH, MTCH, etc.) to transport channels (HS-DSCH, FACH, RACH, etc.). + +**Figure 5.4.1: UTRAN MAC architecture** + +To support MBMS user and control plane transmission, a multicast functionality is added in the MAC c/sh, entitled "MAC m", to take care of scheduling of MBMS related transport channels as presented in Figure 5.4.1. In addition, three logical channels are considered for p-t-m transmission of MBMS: MCCH, MSCH and MTCH. These logical channels are mapped on FACH. In case of p-t-p transmission DTCH and DCCH are used. + +### 5.4.2 MAC-c/sh/m architecture: UTRAN side + +Figure 5.4.2 illustrates the MAC-m additions to the MAC-c/sh architecture in the UTRAN side, needed to transmit MBMS data over a common transport channel (FACH). + +MAC-c/sh/m is located in the controlling RNC. The following functionalities are covered: + +- Scheduling / Buffering / Priority Handling: This function manages common transport resources between MBMS and non-MBMS data flow(s) according to their priority and delay requirements set by higher layers. +- TCTF MUX: This function handles insertion of the TCTF field in the MAC header and also the respective mapping between logical channels (i.e. MTCH and MCCH) and transport channels. The TCTF field indicates which type of logical channel (i.e. MTCH and MCCH) is used. +- Addition of MBMS-ID: For p-t-m type of logical channels, the MBMS-ID field in the MAC header is used to distinguish between MBMS services. +- TFC selection: Transport format combination selection is done for a common transport channel (FACH) mapped to MTCH, MSCH and MCCH. In the case of MBMS soft combining (excluding TrCH combining in TDD), the combinable S-CCPCHs shall have the same TFC during the TTIs in which L1 combining is used. + +There is one MAC-c/sh/m entity in the UTRAN for each cell. + +![Figure 5.4.2: UTRAN side MAC-m architecture additions to MAC-c/sh. The diagram shows a stack of MAC functions. At the top, logical channels MCCH, MSCH, MTCH, and MTCH are shown. Below them, a block labeled 'add MBMS-ID' is connected to the MTCH lines. This is followed by 'TCTF MUX', 'Scheduling/Buffering/ Priority Handling', and 'TFC selection'. These functions are grouped within a larger block labeled 'MAC-c/sh/m'. Below this block, the transport channels FACH and FACH are shown. A 'MAC-Control' oval on the left is connected to the top of the stack.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +Figure 5.4.2: UTRAN side MAC-m architecture additions to MAC-c/sh. The diagram shows a stack of MAC functions. At the top, logical channels MCCH, MSCH, MTCH, and MTCH are shown. Below them, a block labeled 'add MBMS-ID' is connected to the MTCH lines. This is followed by 'TCTF MUX', 'Scheduling/Buffering/ Priority Handling', and 'TFC selection'. These functions are grouped within a larger block labeled 'MAC-c/sh/m'. Below this block, the transport channels FACH and FACH are shown. A 'MAC-Control' oval on the left is connected to the top of the stack. + +Figure 5.4.2: UTRAN side MAC-m architecture additions to MAC-c/sh + +### 5.4.3 MAC-c/sh/m architecture: UE side + +Figure 5.4.3 illustrates the MAC-m additions to the MAC-c/sh architecture in the UE side, needed to receive MBMS data over a transport channel (FACH). + +The following functionalities are covered: + +- TCTF DEMUX: This function handles detection and deletion of the TCTF field in the MAC header, and also the respective mapping between logical channels (i.e. MTCH and MCCH) and transport channels. The TCTF field indicates which type of logical channel (i.e. MTCH and MCCH) is used. +- Reading of MBMS-ID: The MBMS-ID identifies data to a specific MBMS service. + +There is one MAC-m entity in the UE or in case of selective combining one MAC-m entity for each selectively combined cell in the UE. + +![Figure 5.4.3: UE side MAC-m additions to MAC-c/sh. The diagram shows a stack of MAC functions. At the top, logical channels MCCH, MSCH, MTCH, and MTCH are shown. Below them, a block labeled 'read MBMS-ID' is connected to the MTCH lines. This is followed by 'TCTF DEMUX'. These functions are grouped within a larger block labeled 'MAC-c/sh/m'. Below this block, the transport channels FACH and FACH are shown. A 'MAC-Control' oval on the left is connected to the top of the stack.](d3b5eac55166fc428a223bba5c46961b_img.jpg) + +Figure 5.4.3: UE side MAC-m additions to MAC-c/sh. The diagram shows a stack of MAC functions. At the top, logical channels MCCH, MSCH, MTCH, and MTCH are shown. Below them, a block labeled 'read MBMS-ID' is connected to the MTCH lines. This is followed by 'TCTF DEMUX'. These functions are grouped within a larger block labeled 'MAC-c/sh/m'. Below this block, the transport channels FACH and FACH are shown. A 'MAC-Control' oval on the left is connected to the top of the stack. + +Figure 5.4.3: UE side MAC-m additions to MAC-c/sh + +# 6 MBMS Channel Structure + +There exists two transmission modes to provide the MBMS service: + +- Point-to-point transmission (p-t-p) +- Point-to-multipoint transmission (p-t-m) + +## 6.1 Point-to-Point Transmission + +Point-to-point transmission is used to transfer MBMS specific control/user plane information as well as dedicated control/user plane information between the network and one UE in RRC Connected Mode. It is used only for the multicast mode of MBMS and for services identified in the list of MBMS Selected Services. + +For a UE in CELL\_FACH and Cell\_DCH, DCCH or DTCH is used, allowing all existing mappings to transport channels. + +A detailed description of channels used for point-to-point transmission is given in [8]. + +## 6.2 Point-to-multipoint Transmission + +Point-to-multipoint transmission is used to transfer MBMS specific control/user plane information between the network and several UEs in RRC Connected or Idle Mode. It is used for broadcast or multicast mode of MBMS. + +### 6.2.1 Logical Channels + +#### 6.2.1.1 MBMS point-to-multipoint Control Channel (MCCH) + +This logical channel is used for a p-t-m downlink transmission of control plane information between network and UEs in RRC Connected or Idle Mode. The control plane information on MCCH is MBMS specific and is sent to UEs in a cell with an activated (joined) MBMS service. MCCH can be sent in S-CCPCH carrying the DCCH of the UEs in CELL\_FACH state, or in standalone S-CCPCH, or in same S-CCPCH with MTCH. For 3.84 Mcps TDD MBSFN IMB, MCCH is sent in a standalone S-CCPCH frame type 1 only. + +The MCCH is always mapped to one specific FACH in the S-CCPCH as indicated on the BCCH. If MCCH is the only logical channel mapped in to the FACH, the absence of the TCTF field is explicitly signalled otherwise the TCTF field is used in MAC header to identify MCCH logical channel type. In case of soft combining, the MCCH is mapped to a different S-CCPCH (CCTrCH in TDD) than MTCH. + +Reception of paging has priority over reception of MCCH for Idle mode and URA/CELL\_PCH UEs. + +#### 6.2.1.2 MBMS point-to-multipoint Traffic Channel (MTCH) + +This logical channel is used for a p-t-m downlink transmission of user plane information between network and UEs in RRC Connected or Idle Mode. The user plane information on MTCH is MBMS Service specific and is sent to UEs in a cell with an activated MBMS service. + +The MTCH is always mapped to one specific FACH in the S-CCPCH, or in the S-CCPCH frame type 2 in case of 3.84 Mcps TDD MBSFN IMB, as indicated on the MCCH. The TCTF field is always used in MAC header to identify MTCH logical channel type. + +#### 6.2.1.3 MBMS point-to-multipoint Scheduling Channel (MSCH) + +This logical channel is used for a p-t-m downlink transmission of MBMS service transmission schedule between network and UEs in RRC Connected or Idle Mode. The control plane information on MSCH is MBMS service and S-CCPCH specific and is sent to UEs in a cell receiving MTCH. One MSCH is sent in each S-CCPCH carrying the MTCH. + +The MSCH is always mapped to one specific FACH in the S-CCPCH as indicated on the MCCH. Due to different error requirements the MSCH is mapped to a different FACH than MTCH. If MSCH is the only logical channel mapped in to the FACH, the absence of the TCTF field is explicitly signalled otherwise the TCTF field is used in MAC header to identify MSCH logical channel type. + +### 6.2.2 Transport Channel + +FACH is used as a transport channel for MTCH, MSCH and MCCH. + +### 6.2.3 Physical Channel + +SCCPCH is used as a physical channel for FACH carrying MTCH or MCCH or MSCH. + +### 6.2.4 Mapping between channels + +Only in downlink, the following connections between logical channels and transport channels exist: + +- MCCH can be mapped to FACH +- MTCH can be mapped to FACH +- MSCH can be mapped to FACH + +The mappings as seen from the UE and UTRAN sides are shown in Figure 6.2.4-1 and Figure 6.2.4-2 respectively. + +![Figure 6.2.4-1: Logical channels mapped onto transport channel, seen from the UE side. The diagram shows three logical channels (MSCH-SAP, MCCH-SAP, MTCH-SAP) at the top, each connected to a MAC SAP. Below the MAC SAPs is a horizontal line representing the MAC layer. From the MAC layer, three arrows point down to a single transport channel labeled FACH. The label 'Transport Channel' is placed to the right of the FACH label.](ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg) + +Figure 6.2.4-1: Logical channels mapped onto transport channel, seen from the UE side. The diagram shows three logical channels (MSCH-SAP, MCCH-SAP, MTCH-SAP) at the top, each connected to a MAC SAP. Below the MAC SAPs is a horizontal line representing the MAC layer. From the MAC layer, three arrows point down to a single transport channel labeled FACH. The label 'Transport Channel' is placed to the right of the FACH label. + +Figure 6.2.4-1: Logical channels mapped onto transport channel, seen from the UE side + +![Figure 6.2.4-2: Logical channels mapped onto transport channel, seen from the UTRAN side. The diagram shows three logical channels (MSCH-SAP, MCCH-SAP, MTCH-SAP) at the top, each connected to a MAC SAP. Below the MAC SAPs is a horizontal line representing the MAC layer. From the MAC layer, three arrows point down to a single transport channel labeled FACH. The label 'Transport Channel' is placed to the right of the FACH label.](1c140ee5d1a87186977da94a96bfa700_img.jpg) + +Figure 6.2.4-2: Logical channels mapped onto transport channel, seen from the UTRAN side. The diagram shows three logical channels (MSCH-SAP, MCCH-SAP, MTCH-SAP) at the top, each connected to a MAC SAP. Below the MAC SAPs is a horizontal line representing the MAC layer. From the MAC layer, three arrows point down to a single transport channel labeled FACH. The label 'Transport Channel' is placed to the right of the FACH label. + +Figure 6.2.4-2: Logical channels mapped onto transport channel, seen from the UTRAN side + +### 6.2.5 Data Flows through Layer 2 + +#### 6.2.5.1 Data flow for MCCH mapped to FACH + +For MCCH, the RLC mode to be employed is UM-RLC, with required enhancements to support out of sequence SDU delivery. A MAC header is used for logical channel type identification. + +#### 6.2.5.2 Data flow for MTCH mapped to FACH + +For MTCH, the RLC mode to be employed is UM-RLC, with required enhancements to support selective combining. Quick repeat may be used in RLC-UM. A MAC header is used for logical channel type identification and MBMS service identification. For MBMS in case of inter-RNC MBSFN and soft combining, MAC PDUs to be transmitted in one TTI shall be ordered according to MBMS-ID when multiple MTCHs are multiplexed onto one FACH. + +#### 6.2.5.3 Data flow for MSCH mapped to FACH + +For MSCH, the RLC mode to be employed is UM-RLC. A MAC header is used for logical channel type identification. + +## 6.3. MBMS Notification Indicator Channel + +MBMS notification utilizes a new MBMS specific PICH called the MBMS Notification Indicator Channel (MICH) in each cell. Its coding is defined in [9] (FDD) and [10] (TDD). + +# --- 7 MBMS Reception and UE Capability + +## 7.1 Selective and Soft Combining for MBMS P-T-M transmission + +The selective combining for MBMS p-t-m transmission is supported by RLC PDU numbering. Therefore, the selective combining in the UE is possible from cells providing similar MBMS RB bit rate, provided that the de-synchronization between MBMS p-t-m transmission streams does not exceed the RLC re-ordering capability of the UE. Thus, there exist one RLC entity in the UE side. + +To support selective combining it is decided to: + +- Introduce re-ordering as a configurable feature of RLC-UM, within the RLC specification. +- Use the same mechanism as what is specified for MAC-hs (single T1 timer). + +For selective combining there exist one RLC entity per MBMS service utilizing p-t-m transmission in the cell group of the CRNC. All cells in the cell group are under the same CRNC, i.e. Iur support is not considered. + +For soft combining to be possible, the relative delay between the radio links to be combined, when they are received by the UE, must be no more than (1 TTI)+(1 slot). + +The UE capability requirements to support selective and soft combining are defined in chapter 7.2. In case de-synchronization occurs between MBMS transmissions in neighbouring cells belonging to an MBMS cell group the CRNC may perform re-synchronization actions enabling UEs to perform the selective combining between these cells. + +For TDD, selection combining and soft combining can be used when Node-Bs are synchronised. For FDD soft combining can be used when Node-Bs are synchronized inside UE's soft combining reception window, and the data fields of the soft combined S-CCPCHs are identical during soft combining moments. + +When selective or soft combining is available between cells the UTRAN should send MBMS NEIGHBOURING CELL INFORMATION containing the MTCH configuration of the neighbouring cells, available for selective or soft combining. When partial soft combining is applied the MBMS NEIGHBOURING CELL INFORMATION contains the L1-combining schedule, which indicates the time moments when the UE may soft combine the S-CCPCH transmitted in neighbouring cells with the S-CCPCH transmitted in the serving cell. With MBMS NEIGHBOURING CELL INFORMATION the UE is able to receive MTCH transmission from neighbouring cell without reception of the MCCH of that cell. + +The UE determines the neighbouring cell suitable for selective or soft combining based on threshold (e.g. measured CPICH Ec/No) and the presence of MBMS NEIGHBOURING CELL INFORMATION of that neighbour cell. + +The possibility of performing selective or soft combining should be signalled to the UE. + +### 7.1.bis Simulcast Combining (TDD only) + +In contrast to FDD, downlink macro diversity has not been a characteristic of TDD during release '99/4/5. As such TDD receivers are not typically designed to facilitate the simultaneous reception of multiple radio links and the incorporation of such a requirement for MBMS in TDD would have non-trivial impacts on the receiver design. + +Much of the receiver complexity increase associated with the combining of multiple radio links in the UE can however be avoided in TDD by combining macro-diversity with timeslot re-use. This also allows for the throughput gains from timeslot re-use to be combined with further gains from macro diversity. + +In such a scheme, the transmissions of the same information from the multiple participating cells are arranged such that they arrive at the UE on substantially different timeslots, thereby removing the requirement at the UE to detect multiple cells in the same timeslot. + +As such, cells are partitioned into transmission "groups" or "sets". Each transmission set is allocated a timeslot (or set of timeslots) for MBMS transmission. The assigned slots are typically exclusively used by that MBMS set; sets do not transmit when another set is active. The UE attempts to receive information from each set and to combine them either at the physical layer or RLC layer in order to enhance reception reliability. + +Figure 7.1.bis shows such a scheme applied to a tri-sectorized deployment model. 3 timeslots ( $t_1$ , $t_2$ and $t_3$ ) are allocated to each sector for the purposes of MBMS transmission. Each sector is assigned to a particular "MBMS transmission set", set 1, 2 or 3. + +An MBMS data unit or transport block is encoded over several radio frames (eg: 80ms TTI). The physical channel bits that result are effectively transmitted three times; once by MBMS set 1 in timeslot $t_1$ , once by MBMS set 2 in timeslot $t_2$ , and once by MBMS set 3 in timeslot $t_3$ . + +![Figure 7.1.bis: Example of non-time-coincident macro diversity transmission. The figure illustrates a tri-sectorized cell deployment model across three timeslots (t1, t2, and t3). Each timeslot shows a different MBMS transmission set active. A legend defines the symbols: a red circle for a cell site with 3 sector transmitters, a green triangle for a UE receiver, a red hatched box for MBMS from set 1, a yellow box for MBMS from set 2, a blue hatched box for MBMS from set 3, and a green dotted box for other channels. A graph on the right shows the transmission schedule for each set over multiple timeslots.](9c8070d46f1d2480a875239e792f1ef6_img.jpg) + +**Legend:** + +- = cell site with a group of 3 individual sector transmitters +- ▲ = UE receiver +- ▨ = MBMS from set 1 +- = MBMS from set 2 +- ▤ = MBMS from set 3 +- ▒ = other channels + +**Transmission Schedule:** + +| timeslot | set 1 | set 2 | set 3 | other channels | +|----------|-------|-------|-------|----------------| +| t1 | Yes | No | No | No | +| t2 | No | Yes | No | No | +| t3 | No | No | Yes | No | +| t4 | No | No | No | Yes | +| t5 | No | No | No | Yes | +| t6 | No | No | No | Yes | +| ... | No | No | No | Yes | + +Figure 7.1.bis: Example of non-time-coincident macro diversity transmission. The figure illustrates a tri-sectorized cell deployment model across three timeslots (t1, t2, and t3). Each timeslot shows a different MBMS transmission set active. A legend defines the symbols: a red circle for a cell site with 3 sector transmitters, a green triangle for a UE receiver, a red hatched box for MBMS from set 1, a yellow box for MBMS from set 2, a blue hatched box for MBMS from set 3, and a green dotted box for other channels. A graph on the right shows the transmission schedule for each set over multiple timeslots. + +**Figure 7.1.bis: Example of non-time-coincident macro diversity transmission** + +A given UE may be configured to listen to the separate transmissions of the MBMS physical channels (one from each set) which, over the course of the TTI, correspond to the MBMS transport block(s). The signals from each MBMS set + +are largely non-time-coincident and do not require the use of an extensively modified receiver architecture –a receiver architecture resembling that of a normal "single-radio-link" TDD receiver may be used. + +The received transport blocks may be provided to the RLC layer for selective combining, or soft information may be buffered and combined across MBMS sets during the course of the TTI via physical layer soft combining . + +The UTRAN shall signal to the UE on the MCCH which services may be soft combined (and in which cells). The cell group for soft combining may be different than the cell group for selective combining. The UE may assume that transmissions of a given service that may soft combined take place in the same frame. + +### 7.1.ter Chip Combining (1.28Mcps TDD) + +Chip Combining is a technique that bears some relation to Space Code Transmit Diversity (SCTD) in existing releases except that the combining is performed between cells with different scrambling codes instead of between transmit antennas of the same cell with the same scrambling code. + +Chip Combining has been proposed as another form of combining method for p-t-m transmissions for 1.28Mcps TDD mode. All involved cells still keep their own configuration of scrambling code (i.e. different cells participating in the p-t-m transmission have different scrambling codes on the MBMS timeslots). As for SFN transmission, in Chip Combining mode, all Node Bs involved are closely time synchronized, which is an inherent characteristic of TDD systems. + +The UE interested in one p-t-m MBMS service gets the active configuration, such as the midamble codes and the scrambling codes used in the current cell and in the involved neighbouring cells from BCCH and/or MCCH. The UE must monitor the signal strengths of the involved cells and must select a number of cells to combine. In an active p-t-m timeslot, the UE performs channel estimation of each cell to be combined and gets the system matrixes of each involved cell respectively, and then, one compound system matrix can be formed by combining the system matrix of these involved cells. After that, the UE uses joint detection algorithm to recover the MBMS data with the compound system matrix. + +Chip Combining brings no change and requirement to network equipment. However, in order to approach the performance offered by SFN, a relatively large number of cells must be detected and efficiently combined by the UE. Alternatively, chip combining could be used for small service areas (only a small number of cells participate in a simulcast transmission). In this case the number of cells which must be combined by the UE can be reduced and the performance loss compared to SFN is then lowered. + +A UE should have a minimum capability to detect and combine a certain number of cells so that performance of the MBMS p-t-m (and hence coverage of the MBMS service) can be guaranteed. The complexity of the UE and the performance of the chip combining method would have some bearing on the choice of this minimum number of cells that must be combined by the UE. + +## 7.1A MBMS over a Single Frequency Network (MBSFN) + +Another form of combining is possible for p-t-m transmissions and is realised via utilisation of the same scrambling code at a given moment in time by a group of cells covering a geographic area and is applicable for FDD and for TDD. This form of combining is referred to as MBMS over a Single Frequency Network (MBSFN). Signals from multiple cells may be combined by the UE in the same manner as used for multipath signal components from a single cell. + +The UE reception of MBMS services provided in MBSFN mode shall not affect the UE behaviour on the unicast carrier. Especially the UE mobility on the unicast carrier is not affected by the reception of MBMS services provided on a cell operating in MBSFN mode and can imply that the reception of the MBMS service on the cell operating in MBSFN mode is impossible due to the limited support of combination of frequency bands for MBMS SFN reception and unicast reception. + +MBSFN requires all Node Bs involved in the simulcast transmission to be closely time synchronised and exactly the same content is delivered to each of the involved Node Bs. All involved Node Bs are assumed to share the same CRNC (the MBSFN area is limited to the area controlled by a single RNC). + +For TDD, some or all timeslots may utilise an MBSFN mode of transmission. Such timeslots are configured by the RNC to use the same scrambling codes across participating Node-Bs. Any non-MBSFN timeslots continue to use the scrambling codes associated with the cell ID. The timeslots that are operating in the MBSFN mode form together with the synchronized neighbouring cells transmitting the exactly same data the over the MBSFN cluster. + +For FDD, Node-Bs participating in an MBSFN transmission do so on all slots of the radio frame. Thus, MBSFN transmission occupies an entire carrier in the case of FDD, whereas for TDD, part or all of the carrier may be used for MBSFN. + +In addition, MBSFN Integrated Mobile Broadcast (3.84 Mcps TDD MBSFN IMB) is defined. In this configuration, the downlink physical channels for the MBSFN option are mapped on a 3.84 Mcps TDD carrier frequency [10]. RF channel spacing according to the 3.84 Mcps TDD option is used. The entire carrier is used downlink for the 3.84 Mcps TDD MBSFN IMB transmission. For the Node B, the transmitter RF requirements defined for the 3.84 Mcps TDD carriers apply. For the UE, the receiver RF requirements defined for the 3.84 Mcps TDD carriers apply. A primary synchronisation code shall be used, which is orthogonal to the primary synchronisation code used in normal 3.84 Mcps TDD configurations. Unless specified otherwise, the RRC and the MAC protocols are operated according to the FDD requirements applicable for MBSFN. + +It shall be possible for UEs supporting MBSFN to receive MBMS via carriers operating in FDD or TDD MBSFN mode and to also obtain unicast and MBMS (those not provided via MBSFN) by another carrier. + +Allied to MBSFN is the use of higher order modulation techniques (16QAM) for S-CCPCH and in the case of 3.84/7.68 Mcps TDD only the use of a new burst type to support longer delay spread. In case of 3.84 Mcps TDD MBSFN IMB, there are two types of S-CCPCHs: S-CCPCH frame type1 and S-CCPCH frame type2. S-CCPCH frame type 1 consists of 15 slots per radio frame and uses a channelisation code of spreading factor 256. FACH carrying MCCH is mapped onto S-CCPCH type 1. S-CCPCH frame type 2 uses channelisation codes of spreading factor 16 and consists of 5 sub-frames per radio frame; each sub-frame consisting of 3 slots. S-CCPCH frame type 2 is used to support short duty cycles on MTCH. The FACH carrying MTCH may be mapped onto one or more codes of spreading factor 16. + +Reception of MBMS services over a network operating in MBSFN mode implies that the UE is registered to a PLMN in order to perform higher layer procedures such as subscription to MBMS broadcast services. The means by which a UE obtains details of services provided, subscribes to those services it is interested in and obtains any ciphering keys necessary to decrypt services and/or means by which the services are delivered (MBSFN mode, frequency band used etc.), is considered to be outside the scope of 3GPP specifications. However, it is envisaged that the UE may obtain service details via a point-to-point connection via the carrier that is used to provide unicast services. + +The UE selects a MBSFN cluster to receive MBMS service that is part of one of the registered PLMN or part of the equivalent PLMN list. (Note: Network sharing is supported on carriers operating in MBSFN mode using the possibility to broadcast multiple PLMNs in the MIB just as it supported on carriers supporting unicast services) + +For the MBSFN cluster in 1.28 Mcps TDD mode, the UE that needs receive MBMS services delivered in an MBSFN cluster may first get synchronized to the non MBSFN cell that the MBSFN cluster is associated with and then search the MBSFN cluster with the information indicated in the system information of the non MBSFN cell. From the UE's perspective, the registered PLMN of the MBSFN cluster should be the same as the PLMN that is registered by the UE from the associated unicast carrier. + +A MBSFN cluster provides only MBMS service in PtM mode. Counting and PtP establishment procedures are not supported for a cell operating in MBSFN mode. + +For FDD, 3.84 Mcps TDD IMB and 3.84/7.68 Mcps TDD, the selection between MBSFN clusters is performed similarly to the way that cell selection is performed for cells that are not operating in MBSFN mode. The UE shall meet the minimum performance requirements specified for the reception of a MBMS cluster. The UE may consider a minimum receive power of the CPICH (FDD and 3.84 Mcps TDD IMB) or P-CCPCH (3.84/7.68 Mcps TDD) in order to determine when to receive MBMS service broadcast in MBSFN mode. However apart from background search procedures for receiving other MBSFN clusters the UE is not required to perform inter-frequency measurements for other MBSFN clusters. Hierarchical cell structure, rules for fast moving UEs and inter-frequency and inter RAT measurements are not applicable for the cell operating in MBSFN mode. The intra frequency measurements for the reselection between MBSFN clusters are not specified. + +In a MBSFN cluster only MIB, system information blocks 3, 5/5bis and 11 may be broadcast. The content of other system information blocks is ignored by the UE. + +A MBSFN cluster on one frequency might indicate the existence and the services provided by other MBSFN clusters on different frequencies. The MBSFN cluster on one frequency may also indicate other MBSFN frequencies that have to be selected in order for the UE to be aware of available services that are not provided via the currently selected MBSFN cluster and for which the availability can not be indicated on the current MBSFN cluster. The choice of the MBSFN frequency based on this information is UE implementation specific. Because inter frequency measurements for MBSFN frequencies are not applicable the choice of the MBSFN frequency done by the UE may be completely service dependant. For FDD, 3.84 Mcps TDD IMB and 3.84/7.68 Mcps TDD the UE only has to discover one MBMS cluster + +on another frequency that fulfils the selection criteria. Other frequencies on which MBMS service is broadcast in MBSFN mode is indicated on the MBSFN frequency. + +A cluster operating in MBSFN mode does not provide paging information because the MBSFN cluster will not be considered as a suitable cell by the UE. + +The cells in a MBSFN cluster belong to different MBMS service areas compared to the cells of a carrier providing unicast service. This allows the RNC to know which services are intended for the transmission on the cells of a MBSFN cluster. The same MBMS bearer service is not provided on a MBSFN cluster and the unicast cells. + +The minimum MBMS service area must be equal to one MBSFN cluster. A MBMS bearer service must be transmitted in a complete MBSFN cluster. + +### 7.1A.1 3.84 / 7.68 MCPS TDD MBMS over a Single Frequency Network (MBSFN) + +A TDD UE operating on a carrier not dedicated to MBSFN shall follow MBMS procedures specified with respect to the RRC states (see Section 10). For TDD carriers not dedicated to MBSFN, MBMS services may be delivered via MBSFN and/or non-MBSFN means. In the case that any non-MBSFN transmissions are used to deliver MBMS services, the MCCH should not be transmitted via MBSFN means. + +The reception of MBMS on a cell operating in MBSFN mode is independent to the UE behaviour for the reception of service on the frequency that the UE is camping on for obtaining unicast or MBMS service. For the reception of MBMS service on a TDD cell dedicated to MBSFN operation the UE is conceptually an independent component which receives MBMS service on a TDD cell dedicated to MBSFN. + +The TDD component of a UE for receiving MBMS service on a TDD carrier dedicated to downlink MBSFN shall: + +- receive services provided via MBSFN independently of RRC state transitions for any non-MBSFN component of the UE +- obtain details concerning the MCCH provided via the BCCH of the cell providing MBSFN and listen to that MCCH for details of MBMS services provided p-t-m on the TDD DL-only carrier +- search for a suitable TDD MBSFN cluster providing the MBMS services that it is interested in: + - o is only required to support BCH and FACH transport channels and physical channels P-CCPCH, S-CCPCH, SCH on the TDD carrier + - o may optionally support MICH on the TDD carrier + - o shall expect to receive S-CCPCH configuration information via System Information Block 5 (the UE shall expect to receive System Information blocks 3, 5 and 11 only in addition to the Master Information Block) via the BCH on the TDD carrier. + +### 7.1A.2 FDD MBMS over a Single Frequency Network (MBSFN) + +A FDD UE operating on a carrier not dedicated to MBSFN shall follow MBMS procedures specified with respect to the RRC states (see Section 10). + +The reception of MBMS on a cell operating in MBSFN mode is independent to the UE behaviour for the reception of service on the frequency that the UE is camping on for obtaining unicast or MBMS service. For the reception of MBMS service on a FDD cell dedicated to MBSFN operation the UE is conceptually an independent component which receives MBMS service on a FDD cell dedicated to MBSFN. + +The FDD component of a UE operating in a receive-only mode on a FDD carrier operating in MBSFN mode shall: + +- receive services provided via MBSFN independently of RRC state transitions for any non-MBSFN component of the UE +- obtain details concerning the MCCH provided via the BCCH of the cell providing MBSFN and listen to that MCCH for details of MBMS services provided p-t-m on the FDD DL-only carrier +- search for a suitable FDD MBSFN cluster: + +- is only required to support BCH and FACH transport channels and physical channels P-CCPCH, S-CCPCH and SCH on the FDD carrier +- may optionally support MICH on the FDD carrier +- shall expect to receive S-CCPCH configuration information via System Information Block 5 (the UE shall expect to receive System Information blocks 3, 5 and 11 only in addition to the Master Information Block) via the BCH on the FDD carrier. + +#### 7.1A.31.28 MCPS TDD MBMS over a Single Frequency Network (MBSFN) + +A TDD UE operating on a carrier not dedicated to MBSFN shall follow MBMS procedures specified with respect to the RRC states (see Section 10). For TDD carriers not dedicated to MBSFN, MBMS services may be delivered via MBSFN and/or non-MBSFN means. In the case that any non-MBSFN transmissions are used to deliver MBMS services, the MCCH should not be transmitted via MBSFN means. + +The reception of MBMS on a cell operating in MBSFN mode is independent to the UE behaviour for the reception of service on the frequency that the UE is camping on for obtaining unicast or MBMS service. For the reception of MBMS service on a TDD cell dedicated to MBSFN operation the UE is conceptually an independent component which receives MBMS service on a TDD cell dedicated to MBSFN. + +The TDD component of a UE for receiving MBMS service on a TDD carrier dedicated to downlink MBSFN shall: + +- receive services provided via MBSFN independently of RRC state transitions for any non-MBSFN component of the UE +- obtain details concerning the MCCH provided via the BCCH of the cell providing MBSFN and listen to that MCCH for details of MBMS services provided p-t-m on the TDD DL-only carrier +- search for a suitable TDD MBSFN cluster providing the MBMS services that it is interested in: + - is only required to support BCH and FACH transport channels and physical channels P-CCPCH, S-CCPCH on the TDD carrier + - may optionally support MICH on the TDD carrier + - shall expect to receive S-CCPCH configuration information via System Information Block 5 (the UE shall expect to receive System Information blocks 3, 5 and 11 only in addition to the Master Information Block) via the BCH on the TDD carrier. + +NOTE: For 1.28 Mcps TDD, if a cell is operating in MBSFN mode, system information and MCCH messages are transmitted through the Special Timeslot [10]. + +#### 7.1A.43.84 Mcps TDD IMB MBMS over a Single Frequency Network (MBSFN) + +A 3.84 Mcps TDD MBSFN IMB capable UE operating on an FDD or 3.84/7.68 Mcps TDD carrier not dedicated to MBSFN shall follow MBMS procedures specified with respect to the RRC states (see Section 10). + +The reception of MBMS on a cell operating in MBSFN mode is independent to the UE behaviour for the reception of service on the frequency that the UE is camping on for obtaining unicast or MBMS service. For the reception of MBMS service on a cell dedicated to 3.84 Mcps TDD MBSFN IMB operation, the UE is conceptually an independent component which receives MBMS service on a cell dedicated to 3.84 Mcps TDD MBSFN IMB. + +The 3.84 Mcps TDD MBSFN IMB component of a UE receiving MBMS service on a 3.84 Mcps TDD carrier dedicated to 3.84 Mcps TDD MBSFN IMB shall: + +- receive services provided via MBSFN independently of RRC state transitions for any non-MBSFN component of the UE; +- obtain details concerning the MCCH provided via the BCCH of the cell providing 3.84 Mcps TDD MBSFN IMB and listen to that MCCH for details of MBMS services provided p-t-m on the 3.84 Mcps TDD carrier dedicated to 3.84 Mcps TDD MBSFN IMB; +- search for a suitable MBSFN cluster providing the MBMS services the UE has activated; + +- o is only required to support BCH and FACH transport channels and physical channels P-CCPCH, S-CCPCH frame type 1, S-CCPCH frame type 2 and SCH on the 3.84 Mcps TDD carrier dedicated to 3.84 Mcps TDD MBSFN IMB; +- o may optionally support MICH on the 3.84 Mcps TDD carrier dedicated to 3.84 Mcps TDD MBSFN IMB; +- o shall expect to receive S-CCPCH frame type 1 configuration information via System Information Block 5 (the UE shall expect to receive System Information blocks 3, 5 and 11 only in addition to the Master Information Block) via the BCH on the 3.84 Mcps TDD carrier dedicated to 3.84 Mcps TDD MBSFN IMB. + +## 7.1B MBMS in case of inter-RNC synchronization + +### 7.1B.1 Control Plane aspects + +#### 7.1B.1.1 MBMS Parameter Configurations + +The common parameters in MBMS P-t-M RB configurations shall be configured in each RNC semi-static manner via O&M. + +The parameters, transmitted in RRC: MBMS Common P-T-M RB Information and to be configured, are: + +- RB Information list + - RB identity + - PDCP info + - RLC info +- TrCh information for each TrCH + - Transport channel identity + - TFS +- TrCh information for each CCTrCh + - CCTrCH identity + - TFCS + +In case of soft combining the Secondary CCPCH configurations shall be aligned between the neighboring cells. + +In case of MBSFN: + +If MBMS services are controlled statically, the parameters to be configured for MBSFN: + +- PhyCh information + - PhyCh identity + - Secondary CCPCH info MBMS + +.In the case the used parameter value in a cell may depend on the received RAB QoS and/or MBMS service area ID and/or TMGI value, the mapping information should be configured via O&M. Such mapping information should be available in RNCs before the MBMS session setup. + +If MRNC is used, the parameters shall be configured by MRNC, and the MRNC shall inform CRNC of the configuration and mapping information of MBMS service to RB information at session start. + +In addition to parameters used for air interface, the pool of DL TEIDs used for the MBMS transmission on Iu carried by IP-multicast distribution shall be configured in all RNCs by O&M. The stored DL TEIDs used in IP multicast distribution shall not be used by the RNC for any other transmission. + +#### 7.1B.1.2 MBMS Counting and mode switch coordination + +The RNC shall generate the MBMS Counting procedure towards UEs as in case of intra-RNC selective/soft combining (see section 5.2.5). + +If the RNS controlled by a RNC is smaller than the possible selective / soft combining area, the status of the cells in surrounding RNC that are part of the selective/soft combining area should be known before deciding on the own transmission mode. Therefore the RNC shall exchange the transmission mode and counting information with the neighbouring RNCs, which are controlling cells part of the same selective/soft combining area as the cells controlled by the current RNC. Also the neighbour cells indicated for selective/soft combining in MBMS NEIGHBOURING CELL P-T-M RB INFORMATION message have to be coordinated between RNCs. + +The RNSAP function, *Information Exchange* is used for counting and mode switch coordination. + +The RNC may request for the counting results and transmission mode information in cells controlled by a neighbour RNC by sending the INFORMATION EXCHANGE INITIATION REQUEST message to the relevant neighbouring RNCs. + +For counting the INFORMATION EXCHANGE INITIATION REQUEST message will contain the information about the cells controlled by the sending RNC, for which the sending RNC have requested counting. The RNC receiving the INFORMATION EXCHANGE INITIATION REQUEST message shall first identify if any of the cells received in the message is announced as a neighbour cell for the MBMS service in the cells controlled by the receiving RNC (own cells). Thereafter the receiving RNC shall perform counting in these own cells and inform sending RNC about the result over Iur in the INFORMATION EXCHANGE INITIATION RESPONSE message. + +For MBMS transmission mode change the INFORMATION EXCHANGE INITIATION REQUEST message will contain information about the cells controlled by the sending RNC ("initiating cell list") and the TMGIs for which the MBMS transmission mode are requested to be reported when the transmission mode is changed. The MBMS transmission mode shall be reported for cells under control of the RNC receiving the INFORMATION EXCHANGE INITIATION REQUEST message. The MBMS transmission mode for the TMGIs in the INFORMATION EXCHANGE INITIATION REQUEST message shall be reported for the cells that have a configured neighbour relation to the cells in the "initiating cell list". + +The RNC initiating the Information Exchange Initiation procedure shall use the received MBMS transmission mode information of the neighbour cells under control of another RNC to update MBMS NEIGHBOURING CELL P\_T\_M RB INFORMATION message content of its own cells. + +#### 7.1B.1.3 Control Plane Coordination at MBMS Session Start + +##### 7.1B.1.3.1 Coordination of neighbor cell configuration + +The RNC shall at MBMS session start in its own cells, being part of the targeted MBMS service area, activate the RNSAP Information Exchange Initiation procedure to all neighboring RNCs, which are controlling cells allowed to be used for selective/soft combining with the relevant own cells of the RNC. The response, INFORMATION EXCHANGE INITIATION RESPONSE and INFORMATION REPORT messages shall contain the copy of the RRC containers, which were sent out on MCCH announcing the active MBMS session and for each MBMS session that is started a list of cell identities in which the MBMS session (identified with TMGI) was setup. + +The receiving RNC shall identify based on the received information the valid neighbor cells for soft/selective combining in the RNC, which is the sender of the message for the new MBMS session, and retrieve the S-CCPCH configuration in those neighboring cells. Finally the MBMS COMMON P-T-M RB INFORMATION shall be updated with the received S-CCPCH configuration information and the neighboring cells are announced in MBMS NEIGHBOURING CELL P-T-M RB INFORMATION. + +As part of the "Valid neighbor cell identification" the RNC shall verify that the configuration of the cells of the sending RNC is aligned and possible for soft combining, e.g. that the MBMS logical channel id is aligned for all MBMS sessions. The RNC shall not accept the cell as neighbor cell if not aligned. The consequence of a mismatch is that the soft/selective combining gain is lost for this MBMS session, but as this abnormal condition only occurs rarely it is regarded as acceptable. + +###### Coordination of MBMS configurations after RNC restarts + +In case of restart the RNC may lose all the MBMS configurations of its cells as well the neighbor cell MBMS information and any other MBMS related parameters. + +The RNC will recover from that situation by getting the MBMS configurations updated in a three phase approach: + +1. via O&M the MBMS service configurations for its cells. In addition to the MBMS service area configurations there are other parameters which can be configured semi-static manner via O&M system like indicated above. +2. As part of the general restart procedure the SGSN will send the Session Starts for all ongoing MBMS sessions to the RNC. RNC will respond to the MBMS Session Start messages normal manner in line with the MBMS service area configurations of its cells. +3. After the RNC has become aware of the active MBMS sessions it will identify the relevant neighboring RNCs which should be contacted to retrieve the necessary parameters for the neighbor cell configuration. + +#### 7.1B.1.4 MCCH synchronization in an MBSFN cluster + +To synchronize MCCH dynamically, the logical entity "MBMS Master RNC" may be introduced to control the resources of the RNSs within the MBSFN cluster(s). There's only one MBMS Master RNC for any MBSFN cluster. The other RNC can be seen as the CRNC. + +If MRNC is used, the RNSAP procedure "MBSFN MCCH Information" is used to transfer information between MRNC and CRNC to synchronize the MCCH. + +### 7.1B.2 User Plane aspects + +#### 7.1B.2.1 Timing requirements + +The soft combining and MBSFN mode across RNCs will require similar timing requirements between the cells controlled by different RNCs as what is required for cells part of same RNC in Rel-6 and Rel-7. The summary of the timing requirements is presented in the table below. + +**Table 7.1B.2.1-1 The table summarizes the timing requirements for WCDMA MBMS** + +| Functionality | Release | Timing requirement | +|----------------------------------------------------|------------------|--------------------| +| MBMS 40 ms TTI | 3GPP Release 6 | 40.667 ms | +| MBMS 80 ms TTI | 3GPP Release 6 | 80.667 ms | +| MBMS with single frequency network support (MBSFN) | 3GPP Release 7/8 | 12.8 microseconds | + +There are several ways to synchronize the network elements to a common reference time: which meet Rel6/MBSFN timing requirements. + +- 3GPP synchronization in UTRAN, +- Network Time Protocol (NTP), +- Relying on IP multicast distribution, +- Global positioning system (GPS), +- IEEE1588. + +All the listed synchronisation methods may be used but the provided accuracy could be dependent on the synchronisation deployment solution + +#### 7.1B.2.2 MBMS User Data flow synchronization + +The synchronized radio interface transmission from the cells controlled by different RNCs require a SYNC-protocol support over the Iu-interface between the BM-SC and the RNCs. + +As part of the SYNC-protocol procedure the BM-SC shall include to the SYNC PDU packets a time stamp which tells the timing based on which the RNC sends MBMS data over air interface. This time stamp is based on a common time reference available at the BM-SC and the RNCs and represents a relative time value which refers to the start time of the synchronisation period. + +MBMS user data shall be time-stamped based on separable synchronization sequences which are tied to multiples of the TTI length. Synchronization sequence is transmitted continuously, even if there is no MBMS user data in the + +synchronization sequence. Each synchronization sequence for each service is denoted by a single timestamp value working in such a manner that an increase of the timestamp value by one synchronisation sequence length shall be interpreted as an implicit start-of-a-new-synchronization-sequence-indicator, so that the RNC becomes aware that a new sequence is starting. For additional robustness, the timestamp shall be replicated to all packets that shall be submitted over the air interface within one or multiple TTIs. + +When adding the Time Stamp the BM-SC should take into account following factors: arrival time of data, the Maximum Transmission Delay from BM-SC to the farthest RNC, the length of the synchronization sequence used for time stamping and other extra delay (e.g. processing delay in RNC and NodeB ). The parameters 'Max Tx Delay', 'synchronization sequence length' and 'Other Extra Delay' are set via O&M in BM-SC. + +The BM-SC does not know the absolute time point at which a TTI starts, but the sequence length for the time stamp is set by O&M like the delay parameters. The BM-SC will use the delay parameters to define the transmission time point of that user data packet and for the following user data packets the sequence length for the time stamp: following user data packets arriving within e.g. 40ms will receive the same time stamp value as the first data packet, if the sequence length is set to be 40 ms. + +The RNC shall schedule the received data packets in the TTIs following the time point indicated by the timestamp. + +NOTE: From the timestamp the RNC can interpret the TTI from which the transmission of the first user data packet with that time stamp value shall start. Whether there will be data packets to be transmitted in the following TTIs will depend on the used synchronization sequence length vs. the TTI length and on the user data flow. + +In case MRNC is used and TDM multiplexing is used over air interface, scheduling transmission time interval is defined as a time interval of the minimal common multiple of synchronization sequence length and TDM period (CFN period shall be divided by TDM period) in the MRNC. The MRNC shall inform the scheduling transmission time interval to the RNCs over Iur together with MCCH message. The RNC shall schedule received data packets in the scheduling transmission time interval following the time point indicated by the timestamp. If multiple synchronization sequences are to be transmitted consecutively in one scheduling transmission time interval, these synchronization sequences shall be processed as if they are a single synchronization sequence. + +In case MRNC is not used and TDM is used over air interface, the synchronization sequence length should be configured to be multiples of the TDM Period (CFN period shall be a multiple of the TDM period). + +The elementary procedures related to the SYNC-protocol are defined in [14]. + +In addition to the Time Stamp parameter the BM-SC shall provide together with each MBMS User data packet the '*Packet Counter*' and '*Elapsed Octet Counter*' information. Based on these parameters the RNC is able to notice if any data packets were lost during transmission via IP Multicast and to know the size of the lost payload, in case of a single packet is lost. Additionally the RNC is able to reorder the PDUs before passing them to RLC processing, if needed. + +At the end of each synchronization sequence the BM-SC shall send to the RNCs at least one user data frame, which contains counter information including '*Total Number Of Packet Counter*' and '*Total Number Of Octet*' without MBMS payload. This *Total Counter* frame is implicitly marking the end-of-sync.seq.. The *Total Counter* frame without payload may be repeated in order to improve the reliability of the delivery to the RNCs. + +If neither Total Counter frame nor data Frame is received by a RNC for a synchronization sequence, the RNC shall regard the whole synchronization sequence data frame as lost. + +#### 7.1B.2.3 User Plane recovery in case of Multiple Packets Loss + +In case multiple contiguous SYNC PDUs are lost in the RNC, the division of payload between the lost packets is not necessarily known by the RNC. This may lead to an incorrect RLC SN value usage in the RNC, when handling the first data packet received from BM-SC after the multiple packet loss. The RNC is able to notice the loss of multiple user data packets based on the '*Packet Counter*' information delivered by the SYNC-protocol together with the user data packets. In such a situation the radio interface transmission should be avoided until the RNC is able to resynchronize its transport block creation with the neighbouring RNCs or the radio interface transmission may be avoided for exact TTI(s) impacted by the lost SYNC PDUs using the help of the length information of the lost SYNC PDU provided by SYNC protocol. + +In case of soft combining and MBSFN mode the RNC resynchronization is supported by the RLC SN reset at the start of each synchronization sequence in all RNCs part of the IP Multicast distribution. The RNCs are able to notice the start + +of the synchronization sequence from the new time stamp value and the packet counter information received from BM-SC. + +In case MRNC is used and TDM multiplexing is used over air interface, the RNC re-synchronization is supported by the RLC SN reset at the start of each scheduling transmission time interval signalled from MRNC in all RNCs part of the IP Multicast distribution. + +In case of selective combining the RNC shall request from the neighbouring RNCs, which are used for selective combining for that particular MBMS stream, the correct RLC SN value to be used for the first RLC PDU of the next synchronization sequence. + +## 7.2 UE Capability + +The UE MBMS capability is not sent to UTRAN and is subject to UE implementation, including the relation between MBMS capability and actual RRC state which is also a UE implementation. A consequence is that a UE may be counted although its actual capability does not allow to receive MBMS transmissions e.g. because of its current RRC state. + +The standard will describe a minimum UE capability requirement in order to allow operators to configure MBMS channels that can be common to all UEs supporting the given service. + +There are some UE capability requirements that are common to all eventual service categories: + +The minimum UE capability for MBMS capable UE, is one primary CCPCH plus all the configurations below. The UE is not required to support these configurations simultaneously. + +1. One PICH and one MICH +2. One S-CCPCH and one MICH +3. One S-CCPCH (dedicated FACH and possibly the FACH, which may carry MCCH) and two S-CCPCH with 80ms TTI for MTCH reception +4. One S-CCPCH (dedicated FACH and possibly the FACH, which may carry MCCH) and three S-CCPCH with 40ms TTI for MTCH reception +5. One PICH and two S-CCPCH with 80ms TTI for MTCH reception +6. One PICH and three S-CCPCH with 40ms TTI for MTCH reception + +The requirement one reflects the case when the UE is in Idle mode, or URA\_PCH, CELL\_PCH state and MBMS reception is not ongoing and requirement five and six are for the case that MBMS reception is ongoing in Idle mode, or URA\_PCH, CELL\_PCH state. + +The requirement two reflects the case when the UE is in CELL\_FACH state and MBMS is reception not ongoing and requirement three and four are for the case when MBMS reception is ongoing respectively. + +The requirement for the number of simultaneous S-CCPCHs for MTCH reception includes those S-CCPCHs for which combining is performed. + +When MBMS ptm reception is ongoing, the UE is required to periodically monitor the MCCH, which may be mapped onto a different S-CCPCH from MTCH, and a different S-CCPCH than the R'99 FACH when the UE is in CELL\_FACH state. However this does not increase the requirement for the number of S-CCPCHs to be simultaneously received by the UE. + +The ability of the UE to receive DPCH/HS-PDSCH simultaneously with S-CCPCH carrying MTCH/MCCH is subject to UE capability. + +The minimum MBMS bit rate that all MBMS capable UEs shall support is to be defined [12]. + +For FDD, the UE shall support selective combining and soft combining on cells not indicating that they provide MBMS service in MBSFN mode. + +For FDD and 3.84 Mcps TDD IMB, the UE is not required to support selective combining and soft combining on cells indicating that they provide MBMS service in MBSFN mode. + +For a TDD UE supporting both transmit and receive functions, selective and soft combining shall be supported. For a 3.84 / 7.68 Mcps TDD UE supporting both transmit and receive functions, MBSFN operation shall also be supported. For a UE supporting 3.84 / 7.68 Mcps TDD MBSFN receive only, support for selective combining and soft combining is not required. + +The standard may restrict further the UE implementation options by defining certain capability combinations. + +If the UE is supporting MBMS ptm reception in CELL\_DCH state, it shall have capability to acquire MCCH configuration from BCCH after handover procedure, and after that receive MCCH and MTCH. + +## 7.3 MBMS Reception + +The following descriptions add MBMS specific processes to be considered for each RRC State/Mode. + +The BCCH contains information regarding the MCCH, while the latter contains information on the MTCH. + +In the sub-sections below, how and when the UE reads the MCCH is not described as periodic MCCH transmission is described in section 5.2.3. + +The reception of multiple MBMS services simultaneously is subject to UE capability; selection principles between MBMS services are defined in section 5.2.8. The specific actions related to MBMS session repetition are specified in section 5.2.7. + +### 7.3.1 MBMS Reception in RRC Idle Mode + +In idle mode, the UE shall: + +- if the UE supports MBMS and +- if the UE has activated an MBMS service and there is an ongoing session for this service in the cell where the UE is situated, i.e. MTCH and MCCH are available + - act on RRC messages received on MCCH and: + - if the MBMS service requires the establishment of an RRC Connection due to counting response or due to the utilisation of p-t-p transfer mode for the MBMS service: + - inform upper layers that the MBMS Service requires the establishment of an RRC Connection. + - if the MBMS service does not require the establishment of an RRC Connection : + - listen to the common transport channel on which the MTCH is mapped. + - if the UE determines that a neighbouring cell is suitable for selective or soft combining and the UE has valid MBMS NEIGHBOURING CELL INFORMATION of that cell: + - performs selective or soft combining of MTCH between the selected cell and the neighbouring cell. + +### 7.3.2 MBMS Reception in RRC Connected Mode: URA\_PCH state + +In URA\_PCH, the UE shall: + +- if the UE supports MBMS and +- if the UE has activated an MBMS service and there is an ongoing session for this service in the URA where the UE is situated, i.e. MTCH and MCCH are available + - act on RRC messages received on MCCH, + - if on the MCCH it is indicated that the MBMS service in the cell requires a counting response or is due to the utilisation of p-t-p transfer mode for the MBMS service: + - initiate a cell update procedure, for sending MBMS COUNTING RESPONSE, or MBMS P-T-P MODIFICATION REQUEST signalling flow. The cause to be used in the cell update procedure is defined in [13]. + +- for each MBMS service that the UE has activated and where transmission on a MTCH is indicated in the MCCH, listen to the common transport channel on which the MTCH is mapped, +- if the UE determines that a neighbouring cell is suitable for selective or soft combining and the UE has valid MBMS NEIGHBOURING CELL INFORMATION of that cell + - performs selective or soft combining of MTCH between the selected cell and the neighbouring cell. + +### 7.3.3 MBMS Reception in RRC Connected Mode: CELL\_PCH state + +In CELL\_PCH, the UE shall: + +- if the UE supports MBMS and +- if the UE has activated an MBMS service and there is an ongoing session for this service in the cell where the UE is situated, i.e. MTCH and MCCH are available + - act on RRC messages received on MCCH + - if on the MCCH it is indicated that the MBMS service in the cell requires counting response or is due to the utilisation of p-t-p transfer mode for the MBMS service: + - initiate a cell update procedure for sending MBMS COUNTING RESPONSE, or MBMS P-T-P MODIFICATION REQUEST signalling flow. The cause to be used in the cell update procedure is defined in [13]. + - listen to the common transport channel on which the MTCH is mapped, + - if the UE determines that a neighbouring cell is suitable for selective or soft combining and the UE has valid MBMS NEIGHBOURING CELL INFORMATION of that cell + - performs selective or soft combining of MTCH between the selected cell and the neighbouring cell. + +### 7.3.4 MBMS Reception in RRC Connected Mode: CELL\_FACH state + +In CELL\_FACH, the UE shall: + +- if the UE supports MBMS and +- if the UE has activated an MBMS service and there is an ongoing session for this service in the cell where the UE is situated, i.e. MTCH and MCCH are available + - act on RRC messages received on MCCH + - if on the MCCH it is indicated that the MBMS service in the cell requires a counting response or is due to the utilisation of p-t-p transfer mode for MBMS service: + - initiate a counting response for sending MBMS COUNTING RESPONSE, or MBMS P-T-P MODIFICATION REQUEST signalling flow. + - listen to the common transport channel on which the MTCH is mapped + - if the UE determines that a neighbouring cell is suitable for selective or soft combining and the UE has valid MBMS NEIGHBOURING CELL INFORMATION of that cell + - performs selective or soft combining of MTCH between the selected cell and the neighbouring cell. + +NOTE: For UEs in CELL\_FACH, UTRAN may decide to send MBMS data over DTCH. + +### 7.3.5 MBMS Reception in RRC Connected Mode: CELL\_DCH state + +In CELL\_DCH, the UE shall, + +- if the UE supports MBMS and + +- if the UE has activated an MBMS service and there is an ongoing session for this service in the cell where the UE is situated, i.e. MTCH and MCCH are available and +- if the UE has the capabilities: + - act on RRC messages received on MCCH + - listen to the common transport channel on which the MTCH is mapped. + - if the UE determines that a neighbouring cell is suitable for selective or soft combining and the UE has valid MBMS NEIGHBOURING CELL INFORMATION of that cell and UE has capability + - performs selective or soft combining of MTCH between the selected cell and the neighbouring cell. + +NOTE: For UEs in CELL\_DCH, UTRAN may decide to send MBMS data over DTCH + +# 8 UTRAN Signalling Flows for MBMS + +## 8.1 MBMS High Level Signalling Scenarios + +### 8.1.1 Session start + +Upon receiving a session start indication from CN, UTRAN initiates the session start sequence to allocate radio resources to UEs for receiving the MBMS content. As part of this sequence, UTRAN may apply the counting procedure (counting the number of idle mode, URA\_PCH, CELL\_PCH and CELL\_FACH state UEs) to decide whether to use the p-t-m or p-t-p transfer mode. For MBMS Broadcast mode, the applicability of the counting procedure for a service is indicated by the CN. + +The Figure 8.1.1 shows an example of a possible session start sequence. + +![Sequence diagram showing the session start process between a UE and UTRAN. The diagram consists of three vertical lifelines: UE and UTRAN. The sequence of messages is: 1. Notification for session start (from UTRAN to UE), 2. MBMS RB (MTCH, DTCH) establishment (from UTRAN to UE), and 3. MBMS data transfer (from UTRAN to UE).](eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg) + +``` + +sequenceDiagram + participant UE + participant UTRAN + Note over UE, UTRAN: 1. Notification for session start + UTRAN->>UE: + Note over UE, UTRAN: 2. MBMS RB (MTCH, DTCH) establishment + UTRAN->>UE: + Note over UE, UTRAN: 3. MBMS data transfer + UTRAN->>UE: + +``` + +Sequence diagram showing the session start process between a UE and UTRAN. The diagram consists of three vertical lifelines: UE and UTRAN. The sequence of messages is: 1. Notification for session start (from UTRAN to UE), 2. MBMS RB (MTCH, DTCH) establishment (from UTRAN to UE), and 3. MBMS data transfer (from UTRAN to UE). + +Figure 8.1.1: Session start + +In general, the session start sequence involves the following steps: + +- In case UTRAN applies counting to determine the most optimal transfer mode the following steps are performed: + - UTRAN sets the correct MBMS Notification Indicator (NI) and sends the MBMS CHANGE INFORMATION and the MBMS ACCESS INFORMATION including service ID, the session ID if received from the CN, and access probability on MCCH. + - Upon DRX wakeup, UEs in idle mode as well as UEs in CELL\_PCH, URA\_PCH and CELL\_FACH not receiving an MBMS service provided in p-t-m transfer mode evaluate the MBMS NI and if set, read the MBMS CHANGE INFORMATION from MCCH at beginning of the modification period. UEs in idle mode as well as UEs in CELL\_PCH, URA\_PCH and CELL\_FACH receiving an MBMS service provided in p-t-m transfer mode read the MBMS CHANGE INFORMATION directly. If service Id of activated MBMS service and session ID that the UE has not received is indicated in MBMS CHANGE + +INFORMATION UEs continue reading the rest of MCCH information. Upon receiving the MBMS ACCESS INFORMATION including access probability, UEs in idle mode or URA\_PCH, CELL\_PCH, and CELL\_FACH state for which the probability check passes, initiate counting response. UTRAN counts the UEs with an activated MBMS service by combining the UE linking from CN and received counting responses from UEs. + +- In the case that no UE is counted as present in the cell then UTRAN may decide not to provide any RB for the service in the cell. +- In case a pre- defined threshold is reached, UTRAN applies the p-t-m RB establishment procedure specified below. Otherwise, UTRAN may repeat the MBMS ACCESS INFORMATION a number of times, using different probability values. If the threshold is not reached, UTRAN applies the p-t-p RB establishment procedure +- In case UTRAN selects the p-t-m RB establishment procedure: + - UTRAN configures MTCH and updates MCCH (MBMS SERVICE INFORMATION and MBMS RADIO BEARER INFORMATION) by including the service ID, the session ID if received from the CN, and p-t-m RB information for the concerned MBMS service + - In case p-t-m RB establishment is not preceded by counting, UTRAN sets the correct MBMS Notification Indicator (NI) and sends MBMS CHANGE INFORMATION. + - UTRAN sends the MBMS dedicated notification message including the service ID and cause= session start on DCCH to inform UEs in CELL\_DCH that are not receiving an MBMS service provided using p-t-m transfer mode + - In case p-t-m RB establishment is preceded by counting, UEs read MCCH at the pre- defined time(s) to acquire the MBMS SERVICE INFORMATION and MBMS RADIO BEARER INFORMATION + - In case p-t-m RB establishment is not preceded by counting, Upon DRX wakeup, UEs not receiving MTCH evaluate the MBMS NI and if set, read MCCH at beginning of modification period to acquire MBMS CHANGE INFORMATION. UEs in idle mode as well as UEs in CELL\_PCH, URA\_PCH and CELL\_FACH receiving an MBMS service provided in p-t-m transfer mode read the MBMS CHANGE INFORMATION directly. If service Id of activated MBMS service and session ID that the UE has not received is indicated in MBMS CHANGE INFORMATION UEs continue reading the rest of MCCH information to acquire the MBMS SERVICE INFORMATION and MBMS RADIO BEARER INFORMATION + - UEs that are incapable of receiving the MTCH for the session that is started in parallel to the existing activity notify the user. This enables the user to choose between the ongoing activity and the new MBMS service + - Upon receiving MBMS dedicated notification with cause= session start, UEs in CELL\_DCH that are incapable of receiving the MCCH and the corresponding MTCH in parallel to the existing activity notify the user. This enables the user to choose between the ongoing activity and the new MBMS service. If the user decides to receive the new MBMS service, the UE shall read MCCH to acquire the MBMS SERVICE INFORMATION and MBMS RADIO BEARER INFORMATION. + - Upon receiving the MBMS SERVICE INFORMATION and the MBMS RB INFORMATION including the p-t-m RB information for the concerned MBMS service, the UE starts receiving the p-t-m radio bearers +- In case UTRAN selects the p-t-p RB establishment procedure: + - UTRAN indicates on MCCH in MBMS CHANGE INFORMATION that MBMS service is provided via p-t-p + - After receiving MBMS CHANGE INFORMATION UEs with an activated MBMS service, after possible service prioritisation, request MBMS p-t-p RB establishment by sending MBMS P-T-P MODIFICATION REQUEST signalling flow. + - Furthermore, UTRAN establishes the p-t-p RB by means of appropriate RRC procedures e.g. the RB setup procedure + +- UEs establish the p-t-p radio bearers by means of the RRC procedure selected by UTRAN eg. the RB setup procedure +- UTRAN updates MCCH (MBMS SERVICE INFO) to inform UEs joining or entering the cell at a later point in time. + +### 8.1.2 Joining (during a session) + +In case the user wants to join an MBMS service (before or during a session), the UE initiates NAS procedures (e.g. MBMS service activation). + +If no session is ongoing upon completion of the joining procedure, the joining procedure is transparent to the AS. + +In case a session using p-t-m transfer mode is ongoing upon completion of the joining procedure, the UE may initiate reception of the p-t-m radio bearers. In case the ongoing session applies p-t-p transfer mode, UTRAN may establish the p-t-p radio bearers. UTRAN would do this upon receiving a UE linking indication from CN, which normally follows the joining. As a result of the UE linking, UTRAN may decide to change the transfer mode from p-t-p to p-t-m. This change of transfer mode is out of the scope of this sequence (to be covered by a separate sequence). + +The Figure 8.1.2 shows an example of a possible joining sequence. + +![Sequence diagram showing the joining process between a UE and UTRAN. The diagram consists of three vertical lifelines: UE and UTRAN. The sequence of messages is: 1. Joining (NAS) from UE to UTRAN; 2. Initiate reception of PTM RBs from UTRAN to UE; 3. MBMS data transfer, PTM from UTRAN to UE.](23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg) + +``` + +sequenceDiagram + participant UE + participant UTRAN + Note right of UE: 1. Joining (NAS) + Note right of UTRAN: 2. Initiate reception of PTM RBs + Note right of UTRAN: 3. MBMS data transfer, PTM + +``` + +Sequence diagram showing the joining process between a UE and UTRAN. The diagram consists of three vertical lifelines: UE and UTRAN. The sequence of messages is: 1. Joining (NAS) from UE to UTRAN; 2. Initiate reception of PTM RBs from UTRAN to UE; 3. MBMS data transfer, PTM from UTRAN to UE. + +**Figure 8.1.2: Joining with continuation of p-t-m** + +In general, the joining sequence involves the following steps: + +- UEs in idle mode first perform RRC connection establishment, while UEs in CELL\_PCH and URA\_PCH first perform cell update +- UEs initiate the joining procedure (NAS) +- In case UTRAN continues to use the p-t-m transfer mode: + - UTRAN sends the MBMS dedicated notification message on DCCH including the service ID and cause= session ongoing to inform UEs in CELL\_DCH + - Upon receiving MBMS dedicated notification with cause= session ongoing, UEs in CELL\_DCH that are incapable of receiving the MCCH and the corresponding MTCH in parallel to the existing activity notify the upper layer. This enables the user to choose between the ongoing activity and the new MBMS service. If the user chooses to receive the new MBMS service or if the UE in Cell\_DCH is capable of receiving MCCH and MTCH in parallel to the existing activity, the UE shall read MCCH to acquire the MBMS SERVICE INFORMATION and MBMS RADIO BEARER INFORMATION from MCCH. + - Upon acquiring the MBMS SERVICE INFORMATION and the MBMS RADIO BEARER INFORMATION including the p-t-m RB information for the concerned MBMS service, the UE starts receiving the p-t-m radio bearers +- In case UTRAN continues using the p-t-p transfer mode: + +- UTRAN establishes the p-t-p RB by means of appropriate RRC procedures eg. the RB setup procedure +- UEs establish the p-t-p radio bearers by means of the RRC procedure selected by UTRAN eg. the RB setup procedure. + +### 8.1.3 Recounting + +During a p-t-m MBMS session, UTRAN may perform re- counting to verify if p-t-m is still the optimal transfer mode. The purpose of the re- counting procedure is to count the number of idle mode, URA\_PCH, CELL\_PCH, and CELL\_FACH state UEs that have joined a specific service. As a result of this procedure, UTRAN may decide to change the transfer mode from p-t-m to p-t-p. This change of transfer mode is outside the scope of this sequence (to be covered by a separate sequence). + +The Figure 8.1.3 shows an example of a possible recounting sequence. + +![Sequence diagram showing the recounting process between a UE and UTRAN. The sequence starts with 'MBMS data transfer, PTM', followed by '1. Notification for re-counting', then '2: Act based on messages received on MCCH', and finally 'MBMS data transfer, PTM'.](3b00a61116faef21d3a6009fd350b46a_img.jpg) + +``` + +sequenceDiagram + participant UE + participant UTRAN + Note right of UTRAN: MBMS data transfer, PTM + Note right of UTRAN: 1. Notification for re-counting + Note right of UTRAN: 2: Act based on messages received on MCCH + Note right of UTRAN: MBMS data transfer, PTM + +``` + +Sequence diagram showing the recounting process between a UE and UTRAN. The sequence starts with 'MBMS data transfer, PTM', followed by '1. Notification for re-counting', then '2: Act based on messages received on MCCH', and finally 'MBMS data transfer, PTM'. + +**Figure 8.1.3: Recounting with continuation of p-t-m** + +In case UTRAN applies re- counting to determine the most optimal transfer mode, the following steps are performed: + +- UTRAN sends the MBMS CHANGE INFORMATION and the MBMS ACCESS INFORMATION including service ID, and access probability on MCCH +- UEs in idle mode as well as UEs in CELL\_PCH, URA\_PCH and CELL\_FACH receiving an MBMS service provided in p-t-m transfer mode read the MBMS CHANGE INFORMATION at the beginning of each modification period. If service Id of activated MBMS service is indicated in MBMS CHANGE INFORMATION UEs continue reading the rest of MCCH information. +- Upon receiving the MBMS ACCESS INFORMATION including access probability, UEs in idle mode or URA\_PCH, CELL\_PCH and CELL\_FACH state for which the probability check passes, initiate counting response. +- UTRAN counts the UEs with an activated MBMS service by combining the UE linking from CN and received counting responses from UEs. +- In the case that no UE is counted as present in the cell then UTRAN may decide not to provide any RB for the service in the cell. +- In case a pre- defined threshold is reached, UTRAN continues using the p-t-m transfer mode. Otherwise, UTRAN may repeat the MBMS ACCESS INFORMATION a number of times, using different probability values. If the threshold is not reached, UTRAN switches transfer mode from p-t-m to p-t-p +- In case UTRAN continues using the p-t-m transfer mode, it may return UEs that responded to counting back to idle mode by releasing the RRC connection. + +### 8.1.4 Session stop + +UTRAN may apply the session stop procedure to inform UEs that the end of MTCH transmission concerns the end of a session rather than just an idle period. The purpose of the procedure is to reduce the UE power consumption. + +The Figure 8.1.4 shows an example of a possible session stop sequence. + +![Sequence diagram for Session stop procedure between UE and UTRAN.](a5184899f915014fa38608754efcc9c7_img.jpg) + +``` + +sequenceDiagram + participant UE + participant UTRAN + Note right of UE: 1. Termination of MBMS data transfer, PTM + Note right of UE: 2. Notification for session stop + +``` + +The diagram shows a sequence of two steps between a UE and a UTRAN. The first step is 'Termination of MBMS data transfer, PTM' and the second step is 'Notification for session stop'. + +Sequence diagram for Session stop procedure between UE and UTRAN. + +**Figure 8.1.4: Session stop** + +In case UTRAN provides the service p-t-m, the session stop sequence involves the following steps: + +- UTRAN updates the MBMS CHANGE INFORMATION, MBMS SERVICE INFORMATION and the MBMS RADIO BEARER INFORMATION including the service ID and the explicit radio bearer release indicator. UTRAN updates MCCH (MBMS SERVICE INFORMATION) to inform UEs joining or entering the cell in a later point of time. +- UEs in idle mode as well as UEs in CELL\_PCH, URA\_PCH and CELL\_FACH receiving an MBMS service provided in p-t-m transfer mode read the MBMS CHANGE INFORMATION at the beginning of the each modification period. If service Id of activated MBMS service is indicated in MBMS CHANGE INFORMATION UEs continue reading the rest of MCCH information. +- Upon receiving this information the UE stops receiving the MTCH + +In case UTRAN provides the service p-t-p, the session stop sequence involves the following steps: + +- UTRAN releases the p-t-p radio bearers and updates MCCH (MBMS SERVICE INFO) to inform UEs joining or entering the cell at a later point in time. + +## 8.2 MBMS RNC Signalling Flows + +### 8.2.1 MBMS Session Start procedure + +![Sequence diagram for MBMS Session Start procedure between RNC and CN.](c8fcc1ae5d86caaae5607b58d16be8e4_img.jpg) + +``` + +sequenceDiagram + participant RNC + participant CN + Note right of CN: [RANAP] MBMS SESSION START REQUEST + Note left of RNC: [RANAP] MBMS SESSION START RESPONSE + +``` + +The diagram shows a sequence of two messages between an RNC and a CN. The first message is '[RANAP] MBMS SESSION START REQUEST' sent from the CN to the RNC. The second message is '[RANAP] MBMS SESSION START RESPONSE' sent from the RNC to the CN. + +Sequence diagram for MBMS Session Start procedure between RNC and CN. + +**Figure 8.2.1: MBMS Session Start procedure. Successful operation.** + +The MBMS Session Start procedure is initiated by the CN when an MBMS Session is started. The MBMS SESSION START REQUEST is sent to each RNC that is connected to the CN (in case of Iu-flex the RNC may receive more than one MBMS SESSION START REQUEST message). + +The MBMS SESSION START REQUEST contains the MBMS Service Id, and optionally the MBMS Session ID, MBMS Bearer Service Type and the MBMS Session Attributes (MBMS Service Area Information, QoS parameters...) It may also include a list of RAs which lists each RA that contains at least one PMM-IDLE UE that has activated the service. + +MBMS Session Start procedure also provides the MBMS Iu Data Bearer Establishment functionality. In case of Iu-flex the RNC shall not establish more than one MBMS Iu bearer for a certain service towards a pool area and shall inform the respective CN nodes accordingly. + +MBMS Session Start procedure may also be initiated by the CN to restore the MBMS service following an RNC failure or an Iu path failure as specified in TS 23.007 [15]. + +The MBMS Session Start procedure in case of IP Multicast is described in section 8.2.16. + +### 8.2.2 MBMS Session Update procedure + +![Sequence diagram for MBMS Session Update procedure. The diagram shows two vertical lifelines: RNC on the left and CN on the right. A horizontal arrow points from the CN lifeline to the RNC lifeline, labeled '[RANAP] MBMS SESSION UPDATE REQUEST'. A return horizontal arrow points from the RNC lifeline to the CN lifeline, labeled '[RANAP] MBMS SESSION UPDATE RESPONSE'.](a97518a839da75f8379c578562b01bc2_img.jpg) + +``` +sequenceDiagram + participant CN + participant RNC + Note left of CN: MBMS Session Update procedure initiated by CN + CN->>RNC: [RANAP] MBMS SESSION UPDATE REQUEST + RNC-->>CN: [RANAP] MBMS SESSION UPDATE RESPONSE +``` + +Sequence diagram for MBMS Session Update procedure. The diagram shows two vertical lifelines: RNC on the left and CN on the right. A horizontal arrow points from the CN lifeline to the RNC lifeline, labeled '[RANAP] MBMS SESSION UPDATE REQUEST'. A return horizontal arrow points from the RNC lifeline to the CN lifeline, labeled '[RANAP] MBMS SESSION UPDATE RESPONSE'. + +**Figure 8.2.2: MBMS Session Update procedure. Successful operation.** + +The MBMS Session Update procedure is initiated by the CN when an MBMS Session is ongoing and SGSN notices that there is a need to update the list of RAs. The MBMS SESSION UPDATE REQUEST contains the MBMS Service Id, and e.g. List of RAs with PMM Idle UEs.. + +### 8.2.3 MBMS Session Stop procedure + +![Sequence diagram for MBMS Session Stop procedure. The diagram shows two vertical lifelines: RNC on the left and CN on the right. A horizontal arrow points from the CN lifeline to the RNC lifeline, labeled '[RANAP] MBMS SESSION STOP REQUEST'. A return horizontal arrow points from the RNC lifeline to the CN lifeline, labeled '[RANAP] MBMS SESSION STOP RESPONSE'.](18d8d7c537faf9057bd1fe0e7d152d7f_img.jpg) + +``` +sequenceDiagram + participant CN + participant RNC + Note left of CN: MBMS Session Stop procedure initiated by CN + CN->>RNC: [RANAP] MBMS SESSION STOP REQUEST + RNC-->>CN: [RANAP] MBMS SESSION STOP RESPONSE +``` + +Sequence diagram for MBMS Session Stop procedure. The diagram shows two vertical lifelines: RNC on the left and CN on the right. A horizontal arrow points from the CN lifeline to the RNC lifeline, labeled '[RANAP] MBMS SESSION STOP REQUEST'. A return horizontal arrow points from the RNC lifeline to the CN lifeline, labeled '[RANAP] MBMS SESSION STOP RESPONSE'. + +**Figure 8.2.3: MBMS Session Stop procedure.** + +This signalling flow depicts the MBMS Session Stop procedure. + +This procedure is initiated by the CN to the RNCs with an ongoing MBMS session, when no more data will be sent for that MBMS service for some period of time. + +The MBMS Session Stop procedure also provides the MBMS Iu Data Bearer Release functionality. + +### 8.2.4 RNC Registration procedure + +![Sequence diagram for MBMS Registration procedure. The RNC sends a [RANAP] MBMS REGISTRATION REQUEST to the CN, and the CN responds with a [RANAP] MBMS REGISTRATION RESPONSE.](a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg) + +``` +sequenceDiagram + participant RNC + participant CN + Note left of RNC: RNC initiates registration + RNC->>CN: [RANAP] MBMS REGISTRATION REQUEST + CN-->>RNC: [RANAP] MBMS REGISTRATION RESPONSE +``` + +Sequence diagram for MBMS Registration procedure. The RNC sends a [RANAP] MBMS REGISTRATION REQUEST to the CN, and the CN responds with a [RANAP] MBMS REGISTRATION RESPONSE. + +**Figure 8.2.4: MBMS Registration procedure.** + +This signalling flow depicts the MBMS Registration procedure. + +This procedure is initiated by the RNC in the case that the RNC is not SRNC for any UE that has joined the MBMS Service, but this RNC is DRNC for PMM-CONNECTED UEs that have joined the MBMS Service and there is no MBMS Service Context for the MBMS Service in this RNC. + +This procedure shall be initiated by the DRNC, as soon as a UE link is received over the Iur and there exists no MBMS Service Context for the MBMS service for which the UE link is received. + +### 8.2.5 RNC De-Registration procedure + +![Sequence diagram for RNC MBMS De-Registration procedure. The RNC sends a [RANAP] MBMS DE-REGISTRATION REQUEST to the CN, and the CN responds with a [RANAP] MBMS DE-REGISTRATION RESPONSE.](30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg) + +``` +sequenceDiagram + participant RNC + participant CN + Note left of RNC: RNC initiates de-registration + RNC->>CN: [RANAP] MBMS DE-REGISTRATION REQUEST + CN-->>RNC: [RANAP] MBMS DE-REGISTRATION RESPONSE +``` + +Sequence diagram for RNC MBMS De-Registration procedure. The RNC sends a [RANAP] MBMS DE-REGISTRATION REQUEST to the CN, and the CN responds with a [RANAP] MBMS DE-REGISTRATION RESPONSE. + +**Figure 8.2.5: RNC MBMS De-Registration procedure.** + +This signalling flow depicts the RNC De-Registration procedure. This procedure is initiated by the RNC towards the CN node it was registered to in case the RNC is not acting as a Serving RNC for any UE that has activated the MBMS Service and has ceased to act as a Drift RNC for UEs which has activated an MBMS service. + +### 8.2.6 CN De-Registration procedure + +![Sequence diagram for CN MBMS De-Registration procedure. The CN sends a [RANAP] MBMS DE-REGISTRATION REQUEST to the RNC, and the RNC responds with a [RANAP] MBMS DE-REGISTRATION RESPONSE.](cdd9c57c9c578160002ead5cdaef414d_img.jpg) + +``` +sequenceDiagram + participant RNC + participant CN + Note right of CN: CN initiates de-registration + CN->>RNC: [RANAP] MBMS DE-REGISTRATION REQUEST + RNC-->>CN: [RANAP] MBMS DE-REGISTRATION RESPONSE +``` + +Sequence diagram for CN MBMS De-Registration procedure. The CN sends a [RANAP] MBMS DE-REGISTRATION REQUEST to the RNC, and the RNC responds with a [RANAP] MBMS DE-REGISTRATION RESPONSE. + +**Figure 8.2.6: CN MBMS De-Registration procedure.** + +This signalling flow depicts the CN De-Registration procedure. + +This procedure is initiated by the CN in order to inform the RNC that a certain MBMS Service is no longer available. + +### 8.2.7 MBMS Channel Type Switching over Uu + +![Sequence diagram for MBMS Channel Type Switching over Uu. The diagram shows three entities: UE, CRNC, and SRNC. The sequence starts with MBMS CONTROL (p-t-p) from CRNC to UE, followed by two MBMS DATA (p-t-m) messages from CRNC to UE. The CRNC then determines to switch the channel type from p-t-m to p-t-p. It sends an MBMS Channel Type Reconfiguration Signalling over Iur to the SRNC. The SRNC decides whether to perform channel type switching to p-t-p or not. The SRNC sends an [RRC] RB SETUP message to the UE, and the UE responds with an [RRC] RB SETUP COMPLETE message. Finally, the SRNC sends MBMS Data (p-t-p) to the UE.](036ceaf207a7b289ca76e160892eb724_img.jpg) + +``` + +sequenceDiagram + participant UE + participant CRNC + participant SRNC + Note right of CRNC: CRNC determines to switch channel type from p-t-m to p-t-p + CRNC->>UE: MBMS CONTROL (p-t-p) + CRNC->>UE: MBMS DATA (p-t-m) + CRNC->>UE: MBMS DATA (p-t-m) + CRNC->>SRNC: MBMS Channel Type Reconfiguration Signalling over Iur + Note right of SRNC: SRNC decides whether to perform channel type switching to p-t-p or not + SRNC->>UE: [RRC] RB SETUP + UE->>SRNC: [RRC] RB SETUP COMPLETE + SRNC->>UE: MBMS Data (p-t-p) + +``` + +Sequence diagram for MBMS Channel Type Switching over Uu. The diagram shows three entities: UE, CRNC, and SRNC. The sequence starts with MBMS CONTROL (p-t-p) from CRNC to UE, followed by two MBMS DATA (p-t-m) messages from CRNC to UE. The CRNC then determines to switch the channel type from p-t-m to p-t-p. It sends an MBMS Channel Type Reconfiguration Signalling over Iur to the SRNC. The SRNC decides whether to perform channel type switching to p-t-p or not. The SRNC sends an [RRC] RB SETUP message to the UE, and the UE responds with an [RRC] RB SETUP COMPLETE message. Finally, the SRNC sends MBMS Data (p-t-p) to the UE. + +**Figure 8.2.7: Channel type switching signalling flow from p-t-m to p-t-p.** + +The CRNC is responsible for the decision regarding having p-t-m transmission or no p-t-m transmission in a cell for a specific MBMS service. The CRNC informs all the SRNCs having UEs in that cell about its decision. The SRNC is the RNC controlling the RRC connection and RBs to a specific UE. In the example shown, the CRNC decided to no longer use p-t-m, then the SRNC decided to perform channel type switching to deliver the MBMS service over DTCH mapped on a dedicated channel. The RB SETUP message contains the MBMS Service Id. It is FFS whether the SRNC always follows the CRNC's request or not. + +NOTE: the channel type switching in this case includes a change of both transport and logical channels. + +### 8.2.8 MBMS UE Linking + +![Sequence diagram for MBMS UE linking. The diagram shows two entities: SRNC and CN. The SRNC sends a [RANAP] MBMS UE LINKING REQUEST message to the CN, and the CN responds with a [RANAP] MBMS UE LINKING RESPONSE message.](18291be12b470a557e8c9f3a74e021be_img.jpg) + +``` + +sequenceDiagram + participant SRNC + participant CN + SRNC->>CN: [RANAP] MBMS UE LINKING REQUEST + CN->>SRNC: [RANAP] MBMS UE LINKING RESPONSE + +``` + +Sequence diagram for MBMS UE linking. The diagram shows two entities: SRNC and CN. The SRNC sends a [RANAP] MBMS UE LINKING REQUEST message to the CN, and the CN responds with a [RANAP] MBMS UE LINKING RESPONSE message. + +**Figure 8.2.8: MBMS UE linking signalling flow** + +This signalling flow is only applicable for handling UEs in PMM-CONNECTED mode with activated MBMS Services. + +The signalling flow is used to link a specific UE to one or several MBMS service contexts in the SRNC. The MBMS UE LINKING REQUEST message contains the whole list of MBMS Service Ids and MBMS PTP RAB IDs (e.g. mapped from NSAPIs) activated by the UE. If there has not been an MBMS service context related to an MBMS Service Id then SRNC creates an MBMS service context as a result of this procedure. + +### 8.2.9 MBMS UE De-Linking + +![Sequence diagram for MBMS UE De-linking signalling flow between CN and SRNC.](7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg) + +``` +sequenceDiagram + participant CN + participant SRNC + Note left of CN: + CN->>SRNC: [RANAP] MBMS UE DE-LINKING REQUEST + Note right of SRNC: + SRNC->>CN: [RANAP] MBMS UE DE-LINKING RESPONSE +``` + +The diagram shows a sequence of two messages between a Core Network (CN) and a Radio Network Controller (SRNC). The first message is a '[RANAP] MBMS UE DE-LINKING REQUEST' sent from the CN to the SRNC. The second message is a '[RANAP] MBMS UE DE-LINKING RESPONSE' sent from the SRNC back to the CN. + +Sequence diagram for MBMS UE De-linking signalling flow between CN and SRNC. + +**Figure 8.2.9: MBMS UE De-linking signalling flow** + +This signalling flow is only applicable for handling UEs in PMM-CONNECTED mode with activated MBMS Services. + +The signalling flow is used to remove a specific UE from one or several MBMS service context in the SRNC. The MBMS UE DE-LINKING REQUEST message contains the list of MBMS Service Ids de-activated by the UE. + +### 8.2.10 MBMS Service Id Request + +![Sequence diagram for MBMS Service Id list over Iu signalling flow between UE, RNC, MSC, and SGSN.](94d3fdcc244924326f02533aeb2d93fc_img.jpg) + +``` +sequenceDiagram + participant UE + participant RNC + participant MSC + participant SGSN + Note left of UE: + UE->>RNC: Iu-cs connection establishment + Note right of RNC: + RNC->>MSC: [RANAP] COMMON ID + Note right of MSC: + MSC->>SGSN: [RANAP] MBMS SERVICE ID REQ + Note right of SGSN: + SGSN->>RNC: [RANAP] MBMS SERVICE ID RESPONSE +``` + +The diagram shows a sequence of four messages between a User Equipment (UE), Radio Network Controller (RNC), Mobile Switching Center (MSC), and Serving GPRS Support Node (SGSN). The first message is 'Iu-cs connection establishment' sent from the UE to the RNC. The second message is '[RANAP] COMMON ID' sent from the RNC to the MSC. The third message is '[RANAP] MBMS SERVICE ID REQ' sent from the MSC to the SGSN. The fourth message is '[RANAP] MBMS SERVICE ID RESPONSE' sent from the SGSN back to the RNC. + +Sequence diagram for MBMS Service Id list over Iu signalling flow between UE, RNC, MSC, and SGSN. + +**Figure 8.2.10: MBMS Service Id list over Iu signalling flow** + +This signalling flow is applicable for handling MBMS to UEs in RRC-Connected, PMM-IDLE state. The list of MBMS services the user has joined is sent over Iu. + +The purpose of this signalling flow is to perform UE linking for a RRC connected, PMM idle user. The UE provides an indication that the user has joined at least one MBMS service and the PS Domain specific IDNNS (the message that would carry this information is FFS) whenever an Iu-cs connection is established and the UE is PMM idle (that is there is no Iu-ps connection). The RNC requests the MBMS services the UE has joined from the SGSN (or the SGSN the UE is attached to in case of Iu-flex) using a connectionless procedure. The MBMS SERVICE ID REQ contains the IMSI of the UE. The SGSN response contains the full list of MBMS services the user has joined. + +The MBMS service list is then stored in the RNC. The list is deleted when the UE moves to RRC idle and the RRC context is removed in the RNC. + +### 8.2.11 MBMS Attach/Detach over Iur + +![Sequence diagram for MBMS attach request signalling flow. It shows two lifelines: CRNC and SRNC. The SRNC sends an '[RNSAP] MBMS ATTACH REQUEST' message to the CRNC. The CRNC responds with an '[RNSAP] MBMS ATTACH RESPONSE' message to the SRNC.](0f1767577a073167eb9628d72034e083_img.jpg) + +``` +sequenceDiagram + participant SRNC + participant CRNC + Note right of SRNC: [RNSAP] MBMS ATTACH REQUEST + SRNC->>CRNC: [RNSAP] MBMS ATTACH REQUEST + Note left of CRNC: [RNSAP] MBMS ATTACH RESPONSE + CRNC->>SRNC: [RNSAP] MBMS ATTACH RESPONSE +``` + +Sequence diagram for MBMS attach request signalling flow. It shows two lifelines: CRNC and SRNC. The SRNC sends an '[RNSAP] MBMS ATTACH REQUEST' message to the CRNC. The CRNC responds with an '[RNSAP] MBMS ATTACH RESPONSE' message to the SRNC. + +**Figure 8.2.11-1: MBMS attach request signalling flow: Successful Operation.** + +This signalling flow is only applicable for handling UEs in RRC connected mode with activated MBMS Services. + +The purpose of this signalling flow is + +- to either allow the CRNC to add one or several new UEs to the total number of UEs in a given cell using one or several MBMS services. The MBMS ATTACH REQUEST then contains the Cell Id of the new cell (may contain the URA Id of the new URA for UEs in URA\_PCH state), the whole list of affected MBMS Service Ids and a UTRAN specific UE Identification if necessary. +- or to allow the SRNC to inform the DRNC in which URA notifications for MBMS Services have to be sent. The MBMS ATTACH REQUEST then contains a list of URAs and the corresponding MBMS Services. + +![Sequence diagram for MBMS detach request signalling flow. It shows two lifelines: CRNC and SRNC. The SRNC sends an '[RNSAP] MBMS DETACH REQUEST' message to the CRNC. The CRNC responds with an '[RNSAP] MBMS DETACH RESPONSE' message to the SRNC.](b4f6d3668f7e851eaff07ccf26001623_img.jpg) + +``` +sequenceDiagram + participant SRNC + participant CRNC + Note right of SRNC: [RNSAP] MBMS DETACH REQUEST + SRNC->>CRNC: [RNSAP] MBMS DETACH REQUEST + Note left of CRNC: [RNSAP] MBMS DETACH RESPONSE + CRNC->>SRNC: [RNSAP] MBMS DETACH RESPONSE +``` + +Sequence diagram for MBMS detach request signalling flow. It shows two lifelines: CRNC and SRNC. The SRNC sends an '[RNSAP] MBMS DETACH REQUEST' message to the CRNC. The CRNC responds with an '[RNSAP] MBMS DETACH RESPONSE' message to the SRNC. + +**Figure 8.2.11-2: MBMS detach request signalling flow: Successful Operation.** + +This signalling flow is only applicable for handling UEs in RRC connected mode with activated MBMS Services. + +The purpose of this signalling flow is + +- to either allow the CRNC to decrease the total number of UEs receiving one or several MBMS service in a given cell. The MBMS DETACH REQUEST contains the Cell Id of the old cell (may contain the URA Id of the old URA for UEs in URA\_PCH state), the whole list of affected MBMS Service Ids and a UTRAN specific UE Identification if necessary. +- or to allow the SRNC to inform the DRNC in which URA there is not anymore a need to send notifications for MBMS Services due to the presence of UEs in URA\_PCH. The MBMS DETACH REQUEST then contains a list of URAs and the corresponding MBMS Services + +### 8.2.12 MBMS Channel Type Reconfiguration over Iur + +These signalling flows need further study. + +![Sequence diagram showing Channel Type Reconfiguration signalling flow between DRNC and SRNC.](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +``` + +sequenceDiagram + participant DRNC + participant SRNC + DRNC->>SRNC: [RNSAP] MBMS CHANNEL TYPE RECONFIGURAION INDICATION + SRNC->>DRNC: [RNSAP] MBMS CHANNEL TYPE RECONFIGURATION CONFIRMATION + +``` + +Sequence diagram showing Channel Type Reconfiguration signalling flow between DRNC and SRNC. + +**Figure 8.2.12: Channel Type Reconfiguration signalling flow: Successful Operation.** + +This signalling flow is only applicable for handling MBMS UEs in RRC connected mode. + +The purpose of this signalling flow is that the CRNC informs the selected channel type to the SRNCs used in a cell under the CRNC. The MBMS CHANNEL TYPE RECONFIGURATION INDICATION contains a list of U-RNTI, Channel type and MBMS Service Id corresponding to the UEs connected to the SRNC. + +### 8.2.13 Information Exchange over Iur + +These signalling flows is used by the DRNC to acquire the MBMS related information for MBMS service identified by TMGI and is used between the RNCs, which are controlling cells neighbouring to each other for selective/soft combining in case of inter-RNC synchronization. + +![Sequence diagram showing Information Exchange Initiation signalling flow between DRNC/RNC1 and SRNC/RNC2.](9ed248b025d766251d58be10b01a1cc0_img.jpg) + +``` + +sequenceDiagram + participant DRNC/RNC1 + participant SRNC/RNC2 + DRNC/RNC1->>SRNC/RNC2: [RNSAP] INFORMATION EXCHANGE INITIATION REQUEST + SRNC/RNC2->>DRNC/RNC1: [RNSAP] INFORMATION EXCHANGE INITIATION RESPONSE + Note over SRNC/RNC2: Transmission Mode Change + SRNC/RNC2->>DRNC/RNC1: [RNSAP] INFORMATION REPORT + +``` + +Sequence diagram showing Information Exchange Initiation signalling flow between DRNC/RNC1 and SRNC/RNC2. + +**Figure 8.2.13: Information Exchange Initiation signalling flow: Successful Operation.** + +The purpose of this signalling flow is that the DRNC request the APN and IP multicast address for an MBMS service. The INFORMATION EXCHANGE INITIATION REQUEST includes the TMGI for which the APN and IP multicast address are requested. In the INFORMATION EXCHANGE INITIATION RESPONSE message, the corresponding APN and IP multicast address are included. + +If the Information Exchange procedure is started and the transmission mode is changed, this shall be reported by the INFORMATION REPORT message. + +And the additional purpose of this signalling flow used in case of inter-RNC synchronization is + +- to request the external neighbouring RNC(s) to provide the counting results in cells the neighbouring RNC controls +- to request the external neighbouring RNC(s) to inform about the transmission mode change in cells the neighbouring RNC controls for a MBMS session + +- to request the external neighbouring RNC(s) to provide the MBMS PTM RB configuration used in cells the neighbouring RNC controls +- to request the external neighbouring RNC(s) to provide the RLC Sequence Number. + +### 8.2.14 MBMS RAB Establishment Indication + +![Sequence diagram for MBMS RAB Establishment Indication procedure](036c200da9b64c3eb5aae2d67bb53e1f_img.jpg) + +``` + +sequenceDiagram + participant RNC + participant CN + RNC->>CN: [RANAP] MBMS RAB ESTABLISHMENT INDICATION + +``` + +The diagram shows two vertical lifelines labeled 'RNC' and 'CN'. A single horizontal arrow points from the RNC lifeline to the CN lifeline. Above the arrow is the text '[RANAP] MBMS RAB ESTABLISHMENT INDICATION'. + +Sequence diagram for MBMS RAB Establishment Indication procedure + +**Figure 8.2.14: MBMS RAB Establishment Indication procedure** + +This signalling flow is used by the RNC to indicate to the CN the establishment of the MBMS RAB corresponding to the MBMS Iu signalling connection. + +When the RNC decides not to establish an MBMS Iu bearer, for a particular MBMS service, during MBMS Session Start procedure, for example the RNC does not control any contained in MBMS Service Area Information and the RNC does not belong to any of the RA in a list of RAs which lists each RA that contains at least one PMM-IDLE UE but later when a UE linking (via Iu or Iur) is performed or as a result (p-t-p decision) of channel type reconfiguration in another RNC, the RNC establishes the Iu bearer and uses this procedure to inform the CN that an Iu bearer has been established. + +If Iu-Flex is active, the selection of the CN node is implementation dependant. + +The MBMS RAB ESTABLISHMENT INDICATION message contains the *Transport Layer Address* IE and the *Iu Transport Association* IE. + +### 8.2.15 MBMS RAB Release + +![Sequence diagram for MBMS RAB Release Request procedure](ae375ead8aa673286b534e079e9a8533_img.jpg) + +``` + +sequenceDiagram + participant RNC + participant CN + RNC->>CN: [RANAP] MBMS RAB RELEASE REQUEST + CN->>RNC: [RANAP] MBMS RAB RELEASE + +``` + +The diagram shows two vertical lifelines labeled 'RNC' and 'CN'. There are two horizontal arrows. The first arrow points from RNC to CN with the text '[RANAP] MBMS RAB RELEASE REQUEST'. The second arrow points from CN back to RNC with the text '[RANAP] MBMS RAB RELEASE'. + +Sequence diagram for MBMS RAB Release Request procedure + +**Figure 8.2.15: MBMS RAB Release Request procedure.** + +This signalling flow is used by the RNC to indicate to the CN to request the release of an MBMS RAB. + +At reception of the MBMS RAB RELEASE REQUEST message the CN should initiate the release of all MBMS resources related to the Iu connection without releasing the Iu signalling connection. + +The RNC shall at reception of MBMS RAB RELEASE initiate the release of the related MBMS RAB resources. + +The MBMS RAB release may be initiated e.g. for the following reasons (unexhausted): + +- There are lack of radio resource in UTRAN and RNC decided to pre-empt an MBMS RAB for a on-going MBMS session based on Allocation/Retention Priority +- When there are no UEs with a given activated MBMS service consuming radio resources in cells under the RNC or the RNC is controlling UEs in cells under another RNC; +- In case of channel type switching from ptp to ptm in cells under control of another RNC in its role of DRNC; +- There are no cells under the RNC which are part of the RA List Of Idle UEs if received. + +### 8.2.16 MBMS Session Start procedure in case of IP Multicast transport + +![Sequence diagram for MBMS Session Start procedure. The diagram shows two lifelines: RNC and CN. The CN sends a '[RANAP] MBMS SESSION START REQUEST' message to the RNC. The RNC then sends an 'IGMP JOIN' message to an external entity (indicated by a dot). Finally, the RNC sends a '[RANAP] MBMS SESSION START RESPONSE' message back to the CN.](adc59ed6840bcb2d392ea323abfccedc_img.jpg) + +``` + +sequenceDiagram + participant RNC + participant CN + participant MulticastGroup as ● + CN->>RNC: [RANAP] MBMS SESSION START REQUEST + RNC->>MulticastGroup: IGMP JOIN + RNC->>CN: [RANAP] MBMS SESSION START RESPONSE + +``` + +Sequence diagram for MBMS Session Start procedure. The diagram shows two lifelines: RNC and CN. The CN sends a '[RANAP] MBMS SESSION START REQUEST' message to the RNC. The RNC then sends an 'IGMP JOIN' message to an external entity (indicated by a dot). Finally, the RNC sends a '[RANAP] MBMS SESSION START RESPONSE' message back to the CN. + +**Figure 8.2.16-1: MBMS Session Start procedure. Successful operation.** + +The MBMS Session Start procedure is initiated by the CN when an MBMS Session is started. The MBMS SESSION START REQUEST is sent to each RNC that is connected to the CN (in case of Iu-flex the RNC may receive more than one MBMS SESSION START REQUEST message). + +The MBMS SESSION START REQUEST contains the MBMS Service Id, and optionally the MBMS Session ID, MBMS Bearer Service Type, the MBMS Session Attributes (MBMS Service Area Information, QoS parameters, ...) and Transport Layer Address used for the IP-multicast and Iu Transport Association (DL TEID) IE. In addition in case PDCP is used for the MBMS service the PDCP information is included. It may also include a list of RAs which lists each RA that contains at least one PMM-IDLE UE that has activated the service. + +The RNC stores the session attributes in the MBMS Service Context, sets the state attribute of its MBMS Service Context to 'Active' and joins the IP Multicast group, which is used for the User data delivery of this MBMS session between the GGSN and RNCs in case radio resource is available. In case of successful joining the indicated IP Multicast group the RNC replies to the CN nodes from which it has received the MBMS Session Start Request message that the IP Multicast Bearer setup was successful and establishes the radio resource for the transfer of MBMS data to the interested UEs. + +### 8.2.17 MBSFN MCCH Information + +![Sequence diagram for MBSFN MCCH Information procedure. The diagram shows two lifelines: CRNC and MRNC. The MRNC sends an 'MBSFN MCCH INFORMATION' message to the CRNC.](b17128855e79bd21a030ff6fcf1c3310_img.jpg) + +``` + +sequenceDiagram + participant CRNC + participant MRNC + MRNC->>CRNC: MBSFN MCCH INFORMATION + +``` + +Sequence diagram for MBSFN MCCH Information procedure. The diagram shows two lifelines: CRNC and MRNC. The MRNC sends an 'MBSFN MCCH INFORMATION' message to the CRNC. + +**Figure 8.2.17-1: MBSFN MCCH Information procedure, Successful Operation** + +The signalling flow shall be used only if MRNC is used for MBSFN operation. + +The MBSFN MCCH INFORMATION message contains the MCCH messages list sent on the MRNC and the MCCH configuration information of the MRNC. + +The signalling flow is used by the MRNC to inform the CRNC of the MCCH configuration and scheduling information used in MRNC upon receipt of MBMS SESSION START message from CN. + +The CRNC shall prepare the setup of the requested MBMS sessions upon receipt of MBMS SESSION START message from CN, then instead of preparing RRC messages and physical configuration, wait for the MBSFN MCCH INFORMATION message that is sent from MRNC. + +Upon receipt of the MBSFN MCCH INFORMATION message, if the *MCCH Configuration* IE exists, the CRNC shall setup or reconfigure the MCCH of all cells in the MBSFN cluster with the configuration contained in this IE, and update the System Information of these cells. + +The CRNC shall decode the *L3 Information* IE contained in the *MCCH Message List* IE and apply the RLC/MAC/PHY configuration specified by relative MCCH Message to setup the RB information of MTCH, and then send the *L3 Information* IE on the MCCH in the receiving sequence at the beginning of the first MCCH modification period following the CFN carried in the message. + +## 8.3 MBMS Uu Signalling Flows + +### 8.3.1 Broadcast of MBMS System Information + +![Sequence diagram showing the broadcast of MBMS system information from CRNC to UE.](c3e8a7fe2e4f51806e05b9b1aae20d57_img.jpg) + +``` + +sequenceDiagram + participant UE + participant CRNC + CRNC->>UE: MBMS SYSTEM INFORMATION + +``` + +The diagram illustrates a sequence of events between a User Equipment (UE) and a Control Radio Network Controller (CRNC). The UE is represented by a box on the left, and the CRNC by a box on the right. Vertical lines extend downwards from each box, representing their respective timelines. A horizontal arrow points from the CRNC's timeline to the UE's timeline, labeled 'MBMS SYSTEM INFORMATION', indicating the transmission of this information from the CRNC to the UE. + +Sequence diagram showing the broadcast of MBMS system information from CRNC to UE. + +**Figure 8.3.1: Broadcast of MBMS system information.** + +This signalling flow is applicable for handling MBMS to UEs in PMM IDLE and PMM-CONNECTED mode. + +The purpose of the signalling flow is for UTRAN to broadcast MBMS system information to UEs using the BCCH. The MBMS SYSTEM INFORMATION shall be repeatedly transmitted after its first transmission. Upon receiving the first MBMS SYSTEM INFORMATION, the UE shall establish the radio bearer carrying an MCCH. + +The MBMS SYSTEM INFORMATION includes: + +- MCCH schedule information (access info, repetition and modification periods) +- Configuration of a radio bearer carrying an MCCH + +More information may be included in the MBMS SYSTEM INFORMATION. + +### 8.3.2 MBMS Service Information + +![Sequence diagram showing MBMS Service Information signalling flow from CRNC to UE.](195611c20b2dc7ed0fa3033392e22908_img.jpg) + +``` + +sequenceDiagram + participant UE + participant CRNC + CRNC->>UE: MBMS SERVICE INFORMATION + +``` + +A sequence diagram illustrating the signalling flow for MBMS Service Information. It features two vertical lifelines: 'UE' on the left and 'CRNC' on the right. A horizontal arrow points from the CRNC lifeline to the UE lifeline, with the text 'MBMS SERVICE INFORMATION' centered above the arrow. + +Sequence diagram showing MBMS Service Information signalling flow from CRNC to UE. + +**Figure 8.3.2: MBMS service information signalling flow** + +This signalling flow is applicable for handling MBMS to UEs in PMM IDLE and PMM-CONNECTED mode. + +The purpose of the signalling flow is for RNC to inform UEs of all of MBMS services available in one cell. The MBMS SERVICE INFORMATION shall be transmitted periodically on MCCH to provide an indication of the status of the MBMS service in the cell and to support mobility. + +The MBMS SERVICE INFORMATION contains MBMS service ids, optionally the MBMS Session ID, and an indication of the service status in the cell i.e. whether it is provided by p-t-m or p-t-p bearers or whether explicit release is indicated. The MBMS service ids indicate the MBMS services which are being served in the cell or the MBMS services which can be served if the UE requests it. P-t-m indication indicates that the MBMS service is on p-t-m in the cell, thus it informs the UE of the need of reception of the MBMS RADIO BEARER INFORMATION. + +### 8.3.3 MBMS Radio Bearer Information + +![Sequence diagram showing MBMS Radio Bearer Information signalling flow from CRNC to UE.](e3eebf9854831ba50eca8b26c468f65e_img.jpg) + +``` + +sequenceDiagram + participant UE + participant CRNC + CRNC->>UE: MBMS RADIO BEARER INFORMATION + +``` + +A sequence diagram illustrating the signalling flow for MBMS Radio Bearer Information. It features two vertical lifelines: 'UE' on the left and 'CRNC' on the right. A horizontal arrow points from the CRNC lifeline to the UE lifeline, with the text 'MBMS RADIO BEARER INFORMATION' centered above the arrow. + +Sequence diagram showing MBMS Radio Bearer Information signalling flow from CRNC to UE. + +**Figure 8.3.3: MBMS radio bearer information signalling flow** + +This signalling flow is applicable for handling MBMS to UEs in IDLE and PMM-CONNECTED mode. + +The purpose of the signalling flow is for the RNC to inform UE(s) regarding the MTCH radio bearer information. MBMS RADIO BEARER INFORMATION is only available for p-t-m transmission. MBMS RADIO BEARER INFORMATION shall be transmitted periodically on MCCH to support mobility in the MBMS service. + +MBMS RADIO BEARER INFORMATION includes MBMS Service Id, radio bearer, transport channel and physical channel information per MBMS service. + +### 8.3.4 MBMS Access Information + +![Sequence diagram showing MBMS Access Information signalling flow from CRNC to UE.](fe7304192caf64cda93b580c5e7e5c06_img.jpg) + +``` + +sequenceDiagram + participant UE + participant CRNC + CRNC->>UE: MBMS ACCESS INFORMATION + +``` + +A sequence diagram illustrating the signalling flow for MBMS Access Information. It features two vertical lifelines: 'UE' on the left and 'CRNC' on the right. A horizontal arrow points from the CRNC lifeline to the UE lifeline, with the text 'MBMS ACCESS INFORMATION' centered above the arrow. + +Sequence diagram showing MBMS Access Information signalling flow from CRNC to UE. + +**Figure 8.3.4: MBMS Access Information signalling flow** + +This signalling flow is applicable for handling MBMS UEs in IDLE mode or URA\_PCH, CELL\_PCH, CELL\_FACH state. + +The purpose of the signalling flow is for the RNC to inform UE(s) with particular activated MBMS service of the potential need to make an MBMS Counting Response i.e. establish an RRC connection or make a cell update. The MBMS ACCESS INFORMATION is transmitted during counting and re-counting on MCCH. The MBMS ACCESS INFORMATION includes, for each service for which counting is required, the MBMS service identifier, probability factors for idle and connected modes and an indication of the connected mode states to which the signalling flow applies. + +### 8.3.5 MBMS Neighbouring Cell Information + +![Sequence diagram showing MBMS Neighbouring Cell Information signalling flow from CRNC to UE.](b06a4c871dfd0ce034cf801519d0039a_img.jpg) + +``` + +sequenceDiagram + participant UE + participant CRNC + CRNC->>UE: MBMS NEIGHBOURING CELL INFORMATION + +``` + +A sequence diagram illustrating the signalling flow for MBMS Neighbouring Cell Information. It features two vertical lifelines: 'UE' on the left and 'CRNC' on the right. A horizontal arrow points from the CRNC lifeline to the UE lifeline, with the text 'MBMS NEIGHBOURING CELL INFORMATION' centered above the arrow. + +Sequence diagram showing MBMS Neighbouring Cell Information signalling flow from CRNC to UE. + +**Figure 8.3.5: MBMS Neighbouring Cell Information signalling flow** + +This signalling flow is applicable for handling MBMS to UEs in PMM IDLE and CONNECTED mode. + +The purpose of the MBMS NEIGHBOURING CELL INFORMATION signalling flow is for the UTRAN to inform to UEs of the MTCH configuration of the neighbouring cells which are available for selective combining. In case of partial soft combining, the MBMS NEIGHBOURING CELL INFORMATION contains the L1-combining schedule, which indicates when the soft combining is applicable between the specific S-CCPCH of the cell and the specific S-CCPCH of the neighbouring cell. With MBMS NEIGHBOURING CELL INFORMATION the UE is able to receive MTCH transmission from neighbouring cell without reception of the MCCH of that cell. The MBMS NEIGHBOURING CELL INFORMATION shall be repeatedly transmitted on MCCH when selective or soft combining is utilized in the MBMS p-t-m transmission in the given cell group. + +### 8.3.6 MBMS Joined Indication + +![Sequence diagram showing MBMS Joined Indication signalling flow from UE to SRNC.](df65c22a46ec3e7285e44de67d3a59cf_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SRNC + UE->>SRNC: MBMS JOINED INDICATION + +``` + +A sequence diagram illustrating the signalling flow for MBMS Joined Indication. It features two vertical lifelines: 'UE' on the left and 'SRNC' on the right. A horizontal arrow points from the UE lifeline to the SRNC lifeline, with the text 'MBMS JOINED INDICATION' centered above the arrow. + +Sequence diagram showing MBMS Joined Indication signalling flow from UE to SRNC. + +**Figure 8.3.6: MBMS joined indication signalling flow** + +This signalling flow is applicable for handling MBMS to UEs in RRC-Connected, PMM-IDLE state. The MBMS JOINED INDICATION is sent over the DCCH. + +The signalling flow is initiated by the UE after entering RRC-Connected, PMM-IDLE state. The purpose of the signalling flow is to enable the UE to inform the SRNC that the user has joined at least one MBMS service. The SRNC requests the MBMS services the UE has joined from the SGSN as defined in subclause 8.2.10. + +In SRNC relocation this information is transmitted from source RNC to target RNC. + +NOTE: If SRNC has valid linking information the complete service list of activated services is also transmitted from source RNC to target RNC in SRNC relocation. + +### 8.3.7 MTCH Scheduling Information + +![Sequence diagram showing MTCH Scheduling Information flow from CRNC to UE.](65d47e1d0e5982c00e9bd116b89e2b6a_img.jpg) + +``` + + sequenceDiagram + participant UE + participant CRNC + CRNC->>UE: MTCH SCHEDULING INFORMATION + +``` + +Sequence diagram showing MTCH Scheduling Information flow from CRNC to UE. + +**Figure 8.3.7: MTCH scheduling information.** + +This signalling flow is applicable for handling MBMS to UEs in PMM IDLE and CONNECTED mode. + +The purpose of the signalling flow is to enable UEs to perform discontinuous reception of MTCH. The UE may discontinuously receive MTCH based on scheduling information indicated by the MTCH SCHEDULING INFORMATION. This signalling is transmitted on MSCH mapped on SCCPCH carrying MTCH. The MTCH SCHEDULING INFORMATION is signalled on each MSCH repetition period. The MSCH repetition period and the offset from the cell timing are indicated on MCCH. In case of soft combining, the MSCH repetition period is same for all soft combinable S-CCPCH. The scheduling information allows to cover different periods for different MBMS services. + +The MTCH SCHEDULING INFORMATION includes for each service: + +- MBMS service Id (the actual coding is defined in *stage-3*). +- Beginning and duration of MBMS data transmission (one contiguous block or more is defined in *Stage-3*). +- Duration can be infinite (no DTX). This option could be signalled in the MCCH (*Stage-3 definition*). +- Indication of no MBMS data transmission for either this period or several consecutive periods (a period is expressed in MSCH repetition period). + +### 8.3.8 MBMS Change Information + +![Sequence diagram showing MBMS Change Information flow from CRNC to UE.](3711f8e9365e67e6019303fc07924eed_img.jpg) + +``` + + sequenceDiagram + participant UE + participant CRNC + CRNC->>UE: MBMS CHANGE INFORMATION + +``` + +Sequence diagram showing MBMS Change Information flow from CRNC to UE. + +**Figure 8.3.8: MBMS change information.** + +This signalling flow is applicable for handling MBMS to UEs in PMM IDLE and CONNECTED mode. UTRAN should transmit this signalling flow in beginning of each modification period on MCCH and repeat it at least in every repetition period of that modification period. UE shall read this information flow when detecting that MICH bits set for a service that UE has activated, or periodically at the begin of each modification period when receiving MTCH. + +The purpose of the signalling flow is to indicate MBMS services whose MCCH information is changed in that modification period. The content of MBMS CHANGE INFORMATION shall be minimized, so that the MCCH reading time for the UEs, activated MBMS service whose MCCH information is not modified on that modification period, is minimized. + +The MBMS CHANGE INFORMATION includes: + +- The MBMS service Ids for which MCCH information is modified on that modification period. + +### 8.3.9 MBMS P-T-P Modification Request + +![Sequence diagram for MBMS P-T-P Modification Request. A UE sends an MBMS P-T-P Modification Request message to an SRNC.](d7948c38a18636aefecdd95388196460_img.jpg) + +``` +sequenceDiagram + participant UE + participant SRNC + UE->>SRNC: MBMS P-T-P Modification Request +``` + +Sequence diagram for MBMS P-T-P Modification Request. A UE sends an MBMS P-T-P Modification Request message to an SRNC. + +**Figure 8.3.9: MBMS P-T-P Modification Request.** + +This signalling flow is applicable for handling UEs with an activated service that requires MBMS p-t-p RB in PMM IDLE and CONNECTED mode. In idle mode, URA\_PCH and CELL\_PCH states the UE may transmit this signalling flow to request the setup of a p-t-p MBMS RB after receiving the indication on MCCH that p-t-p transfer mode is utilised or, in CELL\_DCH state, to request the release of the p-t-p MBMS RB due to higher priority MBMS service, or to indicate the frequency used for transmitting the higher priority service as specified in subclause 5.2.8. This signalling flow is transmitted on DCCH or on CCCH dependent upon UE state. + +UEs in idle mode are required to perform RRC connection establishment for sending this information flow. UEs that are in URA\_PCH or CELL\_PCH state are required to make a cell update and UEs that are in CELL\_DCH state transmit an MBMS MODIFICATION REQUEST message. + +When UTRAN receives this message from the UE, the UTRAN may setup or release the p-t-p MBMS RB by normal RB release procedure or , in the case of a preferred frequency being indicated, it may perform inter-frequency HHO. + +The MBMS P-T-P Modification Request message includes the identity of the MBMS service when the service appears in the list of MBMS Selected Services. + +### 8.3.10 MBMS Counting Response + +![Sequence diagram for MBMS Counting Response. A UE sends an MBMS Counting Response message to a CRNC.](e9f5aa7b76362051c591d6783211f820_img.jpg) + +``` +sequenceDiagram + participant UE + participant CRNC + UE->>CRNC: MBMS Counting Response +``` + +Sequence diagram for MBMS Counting Response. A UE sends an MBMS Counting Response message to a CRNC. + +**Figure 8.3.10: MBMS Counting Response.** + +This signalling flow is applicable for UEs passing the probability check in counting procedure in idle mode or URA\_PCH, CELL\_PCH or CELL\_FACH state. For the UE in idle mode this signalling flow refers to the complete RRC connection establishment procedure. For UEs in URA\_PCH, CELL\_PCH and CELL\_FACH state this signalling flow refers to cell update procedure. + +The MBMS Counting Response message includes the identity of the MBMS service when the service appears in the list of MBMS Selected Services. + +### 8.3.11 MBMS Selected Services Information + +![](e417ae35ab07134888be901c201d54cd_img.jpg) + +``` + +sequenceDiagram + participant UE + participant CRNC/SRNC + UE->>CRNC/SRNC: MBMS Selected Services Information + +``` + +The diagram illustrates a sequence of events between a User Equipment (UE) and a CRNC/SRNC. The UE is shown on the left and the CRNC/SRNC on the right. A horizontal arrow points from the UE to the CRNC/SRNC, with the text "MBMS Selected Services Information" centered above it. Vertical lines extend downwards from both the UE and the CRNC/SRNC boxes. + +**Figure 8.3.11: MBMS Selected Services Information.** + +This signalling flow is applicable for UEs entering CELL\_DCH state. The purpose of the signalling flow is to enable the UE to inform the SRNC that the user requires the reception of MBMS Selected Services. When the SRNC is not the CRNC of the UE, this signalling flow may interact with the URA linking/de-linking described in subclause 5.1.10. + +This signalling flow is also applicable for UEs in CELL\_DCH states, when the list of MBMS Selected Services has been modified. + +This signalling flow is also applicable for UEs in CELL\_PCH, URA\_PCH and CELL\_FACH states when the list of MBMS Selected Services has been modified by the upper layers and the MBMS Service appears in the MCCH of the cell and the RNC has indicated in the MBMS GENERAL INFORMATION message that it should be notified of a change to this list. If an MBMS Service is contained in the list of MBMS Selected Services but is currently not available in the cell, when the service appears on the MCCH the UE does not perform this signalling flow. + +The purpose of the signalling flow is to enable the UE to inform the CRNC that the list of MBMS Selected Services in the UE has been modified. + +# 9 Security for MBMS + +Ciphering for MBMS multicast data is done between the BM-SC and the UE as defined in [7]. Therefore, for MBMS p-t-m data transmissions no radio interface ciphering is applied. + +In case of p-t-p MBMS data transmissions, if the security is activated for the UE the ciphering is also applied for p-t-p MBMS data RB as for any other RB of the UE. + +# 10 Mobility Procedures for MBMS + +One of the requirements in [5] is: "Data loss during cell change should be minimal". Therefore, when the UE receiving an MBMS session in idle mode or connected mode (not including CELL\_DCH) re-selects between cells, it should be possible to provide service continuity to this UE. + +The following mechanism has been identified to minimise the data loss on cell change. + +## 10.1 Use of Periodical Transmission of MBMS Critical Information + +In this mechanism, the cell periodically transmits an MBMS critical information, informing all MBMS services currently configured for p-t-m transmission or p-t-p transmission. If MBMS service is configured for p-t-m transmission, the periodical transmission of MBMS critical information may also contain the Radio Bearer information corresponding to each MBMS service and Neighbouring cell information. + +If the cell is configured for p-t-p transmission, then the UE would perform a normal RRC connection establishment. + +## 10.2 UE Actions for Mobility + +The UE mobility between intra frequency cells is not affected by the MBMS reception. The mobility between different frequency layers is affected by the Frequency Layer Convergence process as defined in 11.2, if used by the network. + +In CELL\_FACH and in CELL\_DCH state the RRC operation has priority over MBMS reception, thus UE performs the inter frequency and inter RAT measurements as configured by the SRNC. UTRAN should utilize different periodicities between MCCH transmissions and CELL\_FACH state measurement occasion, such that CELL\_FACH state measurements and MCCH transmissions are not constantly overlapping for some UE. + +In Idle mode and in CELL\_PCH, URA\_PCH states the measurements are performed as configured by the network based on the Release 5. The MBMS specific measurement occasions to S-CCPCH for UEs in idle mode and in CELL\_PCH, URA\_PCH states are not introduced and measurements have priority over MBMS reception. The usage of channel protection (channel coding) to recover some of the lost transport blocks is possible. + +UEs may have DRx occasions for specific MBMS service when UE can stop decoding S-CCPCH and perform measurements. DRx occasion are based on scheduling information. + +R'99 standards have some means to reduce need for number of measurements, which can be utilized for MBMS. + +When the UE reselects the cell due to the mobility or returns to on service from out of service, the UE shall acquire the MCCH information if the activated MBMS service is available in the selected cell for the reception of the service. The service is available when the session has been already started and the service is being served on p-t-p/p-t-m in the cell, or the service can be served in the cell if the UE requests it. + +If the MBMS service is available in the cell, the UE will perform an action for the service reception in the cell. For example, if the service is on p-t-p, the idle mode UE will initiate RRC connection establishment procedure. Otherwise, the UE does not need to perform such an action in the cell. The UE, which moves to the new cell, will operate according to the RRC state/mode as follows. + +Whenever the UE moves between p-t-m cells while continuing to receive a service, UE shall receive MCCH information in a new cell, which includes an MBMS cell group identity. If a UE moves between cells belong to the same MBMS cell group based on the MCCH information, the UE does not need to re- establish RLC entity and re-initialise PDCP entity for the service received on MTCH. If a UE moves between cells belong to different MBMS cell groups based on the MCCH information, the UE shall re- establish RLC entity and re- initialise PDCP entity for the service received on MTCH. + +### 10.2.1 RRC idle mode + +Idle mode UE shall: + +- if BCCH contains information regarding the MCCH in the new cell: + - listen to the MCCH and receive the MBMS SERVICE INFORMATION; + - if the MBMS SERVICE INFORMATION contains the activated MBMS service-id: + - if MBMS SERVICE INFORMATION indicates that the service is on p-t-m: + - receive the MBMS RADIO BEARER INFORMATION and listen to the MTCH; + - else: + - initiate RRC connection establishment procedure and request the setup of MBMS p-t-p RB; + - if the UE receive the MBMS RADIO BEARER INFORMATION before the MBMS SERVICE INFORMATION and; + - if MBMS RADIO BEARER INFORMATION contains the activated MBMS service id: + - listen to the MTCH without the need of receiving the MBMS SERVICE INFORMATION. + +### 10.2.2 URA\_PCH State + +URA\_PCH state UE shall: + +- perform URA update procedure if needed; +- if BCCH contains information regarding the MCCH in the new cell: + - listen to the MCCH and receive the MBMS SERVICE INFORMATION; + +- if MBMS SERVICE INFORMATION contains the activated MBMS service id: + - if MBMS SERVICE INFORMATION indicates that the service is on p-t-m: + - receive the MBMS RADIO BEARER INFORMATION and listen to the MTCH; + - else: + - initiate cell update procedure and request to setup the MBMS p-t-p RB; +- if the UE receive the MBMS RADIO BEARER INFORMATION before MBMS SERVICE INFORMATION message and; + - if MBMS RADIO BEARER INFORMATION contains the activated MBMS service id: + - listen to the MTCH without the need of receiving the MBMS SERVICE INFORMATION. + +### 10.2.3 CELL\_PCH + +CELL\_PCH state UE shall: + +- perform cell update procedure; +- if BCCH contains information regarding the MCCH in the new cell: + - listen to the MCCH and receive the MBMS SERVICE INFORMATION; +- if MBMS SERVICE INFORMATION contains the activated MBMS service id and: + - if MBMS SERVICE INFORMATION indicates that the service is on p-t-m: + - receive the MBMS RADIO BEARER INFORMATION message and listen to the MTCH. + - else: + - initiate the cell update procedure and request to setup the MBMS p-t-p RB. +- if the UE receive the MBMS RADIO BEARER INFORMATION before the MBMS SERVICE INFORMATION and; + - if MBMS RADIO BEARER INFORMATION contains the activated MBMS service id: + - listen to the MTCH without the need of receiving the MBMS SERVICE INFORMATION. + +### 10.2.4 CELL\_FACH + +CELL\_FACH state UE shall: + +- perform cell update procedure +- if BCCH contains information regarding the MCCH in the new cell: + - listen to the MCCH and receive the MBMS SERVICE INFORMATION; +- if MBMS SERVICE INFORMATION contains the activated MBMS service id and; + - if MBMS SERVICE INFORMATION indicates that the service is on p-t-m: + - receive the MBMS RADIO BEARER INFORMATION and listen to the MTCH; + - else: + - initiate request to setup the MBMS p-t-p RB; +- if the UE receive the MBMS RADIO BEARER INFORMATION before the MBMS SERVICE INFORMATION and; + - if MBMS RADIO BEARER INFORMATION contains the activated MBMS service id: + +- listen to the MTCH without the need of receiving the MBMS SERVICE INFORMATION. + +### 10.2.5 CELL\_DCH State + +CELL\_DCH state UE shall: + +- act on the RRC message received on DCCH in handover. +- if the UE has the capability to support MBMS in CELL\_DCH: + - if BCCH contains information regarding the MCCH in the new cell: + - listen to the MCCH and receive the MBMS SERVICE INFORMATION; + - if MBMS SERVICE INFORMATION contains the activated MBMS service id and; + - if MBMS SERVICE INFORMATION indicates that the service is on p-t-m: + - receive the MBMS RADIO BEARER INFORMATION and listen to the MTCH. + - if the UE receive the MBMS RADIO BEARER INFORMATION before the MBMS SERVICE INFORMATION and; + - if MBMS RADIO BEARER INFORMATION contains the activated MBMS service id: + - listen to the MTCH without the need of receiving the MBMS SERVICE INFORMATION. + +# 11 Resource Management for MBMS + +## 11.1 MBMS Access Control Procedure + +MCCH messages initiating counting or recounting cause multiple responses from UEs within a cell. This may result in RACH congestion if number of UEs is high in a cell. To avoid this, CRNC may perform MBMS access control procedure during counting or recounting procedure. MBMS access control procedure is described in Figure 11.1. + +![Sequence diagram of MBMS Access Control Procedure between UEs and CRNC.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +``` + +sequenceDiagram + participant UEs + participant CRNC + Note right of CRNC: 1. Setting of the initial +probability factor + CRNC->>UEs: 2. Signaling the initial probability factor + Note left of UEs: 3. UE in Idle mode request +RRC connection based on the +initial probability factor 1 +UE in URA/CELL_PCH or +CELL_FACH state response +counting based on the initial +probability factor 2 + Note right of CRNC: 4. Detecting the needs for +updating + Note right of CRNC: 5. Updating to the optimum +probability factor + CRNC->>UEs: 6. Signaling the updated probability factor + Note left of UEs: 7. UE in Idle mode request RRC +connection based on the updated +probability factor 1 +UE in URA/CELL_PCH or CELL_FACH +state response counting based on the +updated probability factor 2 + +``` + +The diagram illustrates the MBMS Access Control Procedure between UEs and CRNC. It consists of 7 steps: 1. CRNC sets the initial probability factor. 2. CRNC signals this factor to UEs. 3. UEs in Idle mode or specific states (URA/CELL\_PCH, CELL\_FACH) perform requests or counting based on initial probability factors 1 and 2. 4. CRNC detects update needs. 5. CRNC updates to an optimum probability factor. 6. CRNC signals the updated factor. 7. UEs perform requests or counting based on updated probability factors 1 and 2. + +Sequence diagram of MBMS Access Control Procedure between UEs and CRNC. + +**Figure 11.1: MBMS Access Control Procedure** + +1. CRNC calculates an initial probability factor for an MBMS service when a MCCH message causing counting or recounting is about to be sent. CRNC can use different probability factor for UEs in Idle mode and for different UEs in URA\_PCH, CELL\_PCH and CELL\_FACH. +2. CRNC includes the probability factor into the MCCH message and sends it to UEs. This can be done in MBMS Group Notification. +3. UEs in idle mode or in URA\_PCH, CELL\_PCH and CELL\_FACH state passing the probability check performs counting response UEs keep listening to MCCH to get updated probability factor until they have successfully responded to counting or counting is no longer required. +4. CRNC detects the probability factor needs to be updated. Detecting mechanism is not to be standardized. +5. CRNC recalculates the probability factor. The way of calculating new probability factor is not to be standardized. +6. CRNC includes the updated probability factor into the MCCH message and sends it to UEs. +7. UEs in idle mode or in URA\_PCH, CELL\_PCH or CELL\_FACH state that pass the probability check, by using updated probability factor, perform counting response. + +CRNC and UEs that are still trying to perform the counting response repeat step 3 ~ step 7 until e.g. counting or recounting procedure ends. + +## 11.2 Frequency layer Convergence + +Frequency Layer Convergence (FLC) denotes the process where the UTRAN requests UEs to preferentially re-select to the frequency layer on which the MBMS service is intended to be transmitted. This layer preference could be done by + +an additional MBMS session related Layer Convergence Information (LCI) such as offset and target frequency. The FLC is supported by specifications for both networks utilizing HCS and for networks not utilizing HCS. + +The preferred layer (PL) is indicated per MBMS service and the LCI (offset) is the same for all MBMS services on a given preferred layer. UTRAN can consist of multiple preferred layers and the PL for given services is decided by RRM. Thus the PL for an MBMS service might be different in different parts of the service area. Network co-ordination between RNCs may be added for the Rel-7. The CN may also request the RNC (e.g. using “no-FLC-flag” value) not to apply any frequency layer convergence mechanisms for the MBMS service (e.g. emergency service). In case no PL info is specified for the MBMS service, the UE may assume that the MBMS service is available on all frequencies. + +The LCI can be signalled to UEs by the CRNC after the session start is received over Iu interface until reception of the session stop. The UEs shall take LCI into account whenever it is signalled on the MCCH in Idle mode and URA\_PCH, CELL\_PCH and in CELL\_FACH states. The FLC is not applicable in CELL\_DCH state, as it is only effecting UEs cell re-selection procedure. + +The UE shall ignore Sintersearch parameter only for the potential preferred layers when LCI is signalled and on preferred layer the UE shall apply the Sintersearch parameter. In case of UE is in CELL\_FACH state without measurement occasions, the UE may not be able to measure cells on preferred layers. + +In the case that the UE has joined multiple services and they have different frequencies as preferred layer, the UE should apply the FLC applicable for the highest priority MBMS service, which it has activated and has a PL. The priority setting of different MBMS services is decided by NAS. + +Based on RRM decision, a given MBMS service can be provided on non-preferred layer by p-t-p or p-t-m transfer mode. + +The details of the mechanism are defined in state 3. + +## 11.3 Frequency layer Dispersion + +Frequency Layer Dispersion (FLD) denotes the process where the UTRAN redistributes UEs across the frequencies. UTRAN can use FLD per MBMS session. + +For FDD, the FLD is applicable in Idle mode, URA\_PCH, CELL\_PCH and CELL\_FACH states. + +For TDD, the FLD is applicable in Idle mode, URA\_PCH and CELL\_PCH states. + +When FLC is applied, the UE stores the frequency where it was camped previously. Upon session stop or service deactivation, the UE attempts to return to that frequency. + +If the UE does not find a suitable cell on the target frequency, the UE attempts to select a cell on a randomly chosen frequency. + +Dispersion applies when the MBMS session on the MBMS preferred frequency ends, or when the MBMS service on the MBMS preferred frequency is deactivated by the UE. Dispersion does not apply in the case where the UE decides to receive another service for which FLC is applied. + +The details of the mechanism are defined in the stage 3. + +# Annex A (informative): MBMS Phases in UTRAN + +![Figure A: Timeline of MBMS Service. This diagram illustrates the timeline of an MBMS service across five horizontal axes: UE1 events, UE2 events, Service 1 events, Transfer of data, and MBMS phase in UTRAN. UE1 and UE2 events show subscription, service join, and service leave actions. Service 1 events show session start, idle periods, data transfers, and session stops. Transfer of data shows announcements and data sent to specific UEs. The MBMS phase in UTRAN is divided into Phase 1 (idle), Phase 2 (setup), and Phase 3 (data transfer).](1f1614411edea7edfc86c839a608e1fc_img.jpg) + +The diagram shows the following timeline elements: + +- UE1 events:** Subscription to service1 (black dot), User service join (green dot), service leave (red X). +- UE2 events:** subscription to service1 (black dot), service leave (red X). +- Service 1 events:** Start Service 1 announcement (blue dot), 1st Session start (green dot), Idle period of seconds (dashed green line), Data transfer (green double-headed arrows), 1st session stop (red dot), Service 1 Session 2 (green double-headed arrow), Stop Service 1 announcement (blue dot). +- Transfer of data:** Announcement (blue bar), Data sent to UE1 (green bar), Data sent to UE1 and UE2 (green bar), Data sent to UE1 and UE2 (green bar), Data sent to UE2 (green bar). +- MBMS phase in UTRAN:** Phase 1 (black), Phase 2 (green), Phase 3 (green), Phase 1 (black), Phase 2 (green), Phase 3 (green), Phase 1 (black). + +Callouts indicate that subscription and service join can occur at any time. RB setup is shown between Phase 1 and Phase 2. + +Figure A: Timeline of MBMS Service. This diagram illustrates the timeline of an MBMS service across five horizontal axes: UE1 events, UE2 events, Service 1 events, Transfer of data, and MBMS phase in UTRAN. UE1 and UE2 events show subscription, service join, and service leave actions. Service 1 events show session start, idle periods, data transfers, and session stops. Transfer of data shows announcements and data sent to specific UEs. The MBMS phase in UTRAN is divided into Phase 1 (idle), Phase 2 (setup), and Phase 3 (data transfer). + +**Figure A: Timeline of MBMS Service** + +The UTRAN MBMS behavior is divided into 3 phases. Figure A illustrates the timeline of an MBMS service with regards to these phases. + +## A1 Security for MBMS + +A cell stays in phase 1, if there is no ongoing session for the MBMS service, or if it does not belong to the MBMS service area of the service. + +A UE that has joined an MBMS service may regularly try to receive MBMS notification in a cell [FFS]. At this phase the UE does not request service delivery to UTRAN. + +## A2 MBMS Phase 2 + +This phase starts when UTRAN receives the MBMS "session start" from CN, and ends when UTRAN initially sets up MBMS radio bearer for the session, or decides not to set up the MBMS radio bearer in a cell. + +In this phase, UTRAN transmits notification to UEs about the incoming service and could perform counting procedure to decide the type of MBMS radio bearer. UTRAN decides whether to set up p-t-m, p-t-p radio bearer or no radio bearer, based on the number of UEs that expected to receive the service in the cell. A UE that has at least one activated MBMS service acts on an RRC message in MCCH. + +## A3 MBMS Phase 3 + +This phase starts after initial MBMS radio bearer setup and ends when UTRAN receives the MBMS "session stop" from CN. + +In this phase, UTRAN transmits the data for the MBMS service received from CN using, if any, the established radio bearer. If there is no set-up radio bearer, UTRAN waits for service delivery request from UE. Recounting and radio bearer reconfiguration may be performed during this phase. + +UTRAN behaviour in this phase can be divided into three states: no transmission, p-t-p transmission, and p-t-m transmission. Each cell belonging to the same MBMS service area may be in any of three states. With the variation of the number of UEs, the state of a cell may change between the three states. UTRAN may broadcast the state of each cell. + +- 1) **No Transmission:** In this state of a cell, there is no established radio bearer because there is no UE who wants to receive the service. An MBMS-joined (or MBMS-interested in broadcast mode) UE in idle mode that moves into the cell of this state requests service delivery to UTRAN. +- 2) **P-t-p Transmission:** In this state of a cell, p-t-p radio bearer is established. A UE that has joined (or interested in broadcast mode) an MBMS service may receive MBMS data over p-t-p radio bearer if there is MBMS data to receive. +- 3) **P-t-m Transmission:** In this state of a cell, p-t-m radio bearer is established. A UE that has joined (or interested in broadcast mode) an MBMS service may receive MBMS data over p-t-m radio bearer if there is MBMS data to receive. + +## A4 MBMS Phases and Status Parameters + +Table 1 lists the MBMS parameters that need to be broadcast in each MBMS phase. The list is [FFS] + +**Table 1: MBMS Status Parameters** + +| | Phase 1 | Phase 2 | Phase 3 | Description | +|--------------------|---------|------------|----------------------|-----------------------------------------| +| Service ID | X | O | O | Identity of the Service | +| Transmission State | X | X | O (NONE/p-t-p/p-t-m) | State of the cell for MBMS transmission | +| Counting | X | O (On/Off) | O (On/Off) | Whether counting procedure is going on. | + +- 1) **Service ID:** This parameter indicates the identity of the service concerned. +- 2) **Transmission state:** This parameter indicates to UE(s) the state of the concerned cell while it is in phase 3. According to this parameter, UE entering the cell starts re-configuration of the radio bearer, or requests service delivery to UTRAN. Specifically, if this parameter is set to "p-t-m", UE receives service over p-t-m radio bearer and if set to "p-t-p", UE receives service over p-t-p radio bearer. If it is set to NONE, UE has to request UTRAN to deliver the service. +- 3) **Counting:** The counting parameter informs UEs whether counting is required (and is going on) or not. If this parameter is set to "ON", UE should perform RRC connection procedure. + +# Annex B (informative): MBMS Control Information + +Tables 2 and 3 describe MBMS control information in the downlink and uplink. + +**Table 2: Mapping of MBMS Control Parameters in DL** + +| Information Element | Description | +|----------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MICH – Transmitted continuously – Can be modified at a modification period boundary | | +| MBMS Notification Indicators | Indicates when new information is to be transmitted on MCCH in the next modification period. | +| BCCH - Transmitted periodically | | +| MCCH System Information | Includes:
- Configuration of the radio bearer carrying MCCH,
- MCCH schedule information (access info, repetition and modification periods). | +| MCCH – Non Critical Information – Transmitted at access info events – Can be modified at any transmission | | +| MBMS Access Information | Contains parameters that control, for the purposes of counting, whether UEs should establish an RRC connection (idle mode) or make a cell update (URA_PCH state). It may include for each service for which counting is in progress:
- MBMS service identity,
- Probability factor (Idle mode),
- Probability factor (URA_PCH),
Additional parameters may be identified in stage 3. | +| MCCH – Critical Information – Transmitted at repetition period Events – Can be modified at a modification period boundary | | +| MBMS Change Information | Identifies MBMS services for which parameters are modified in this modification period. It may include for each service listed:
- MBMS service identity,
- MBMS session identity.
Additional parameters may be identified in stage 3. In stage 3, MBMS Change Information is contained in the MBMS MODIFIED SERVICES INFORMATION message. | +| MBMS Service Information | Identifies MBMS services that are available in the cell. It may include for each service listed:
- MBMS service identity,
- MBMS session identity,
- Indication that a p-t-m bearer is established for the service in the cell,
- RB release indication,
- Preferred frequency layer information.
Additional parameters may be identified in stage 3. In stage 3, MBMS Services Information for a service is contained in either the MBMS MODIFIED SERVICES INFORMATION or the MBMS UNMODIFIED SERVICES INFORMATION messages depending upon the change status of the service. | +| MBMS Radio Bearer Information | Contains, for one or more MBMS services information describing the radio bearer and the p-t-m bearer that is used within the serving cell. It may include for each service listed:
- MBMS service identity,
- MBMS cell group identity,
- Physical channel information,
- Transport channel information,
- Radio Bearer information.
Additional parameters may be identified in stage 3. | + +| | | +|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MBMS Neighbouring Cell Information | Contains, for one or more MBMS services transmitted in neighbour cells that can be used for soft or selective combining, information describing the p-t-m bearer to which it is mapped in the neighbour cell. It may include for each service listed:
  • - MBMS service identity,
  • - Cell identification information,
  • - Physical channel information,
  • - Transport channel information,
  • - Radio Bearer information,
  • - L1 scheduling information,
  • - Soft/ selective combining information.
Additional parameters may be identified in stage 3. | +| MSCH – Transmitted periodically | | +| MTCH Scheduling Information | Contains information that enables UEs to perform discontinuous reception of MTCH. It may include for each of one or more services:
  • - MBMS service identity,
  • - The start time and duration of a period of data transmission,
  • - Indication that there is no data transmission for one or more MSCH repetition periods.
| + +**Table 3: Mapping of MBMS Control Parameters in UL** + +| Information Element | Description | +|---------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| DCCH - Service Related Control Information | | +| MBMS Joined Indication | Indicates that a PMM IDLE state UE in RRC connected mode has joined at least one MBMS service | +| MBMS P-T-P Modification Request | UEs in CELL_DCH state may transmit this signalling flow to request the release of a p-t-p MBMS RB for a higher priority MBMS service. | + +# Annex C (informative): Change history + +| Change history | | | | | | | | +|----------------|--------------------|-----------------------------------------|----|-----|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New version | +| 8/02 | RAN2#31 | R2-021846 | | | | | 0.0.1 | +| 9/02 | RAN2#32 | R2-020590 | | | | Skeleton Endorsed with some changes in sections from RAN2#31 | 1.0.0 | +| 11/02 | RAN2#33 | R2-022927 | | | | No MBMS Discussions | | +| 1/03 | RAN2/3 MBMS AdHoc | R2-030006 | | | | R2-022644 and R2-022699 | 1.1.0 | +| 2/03 | RAN2#34 | R2-030122 | | | | Inclusion of R2-030010, R2-030050, figure from R2-030015, mechanism 1 from R2-030062, + editorial changes + principles in section 5.1.3 | 1.4.0 | +| 4/03 | RAN2#35 | R2-030707 | | | | Inclusion of R2-030010 + section 5.1.4 based on agreed bullet points from RAN2#34 + correction of version numbering + addition of "change history" section. | 1.5.0 | +| 5/03 | RAN2/3 AdHoc | R2-030882 | | | | -R2-030907 "Functional Description on MAC-c/sh/m".
-R2-030902 on the "MBMS Control Plane Protocol Stack".
-R2-030910 on MBMS UTRAN Phases in Annex A.
-R3-030584: only inclusion of sections: 7.1.3 and 7.1.4. In 7.1.3 there is one additional comment regarding the addition of "PMM" wherever CONNECTED mode" is mentioned.
-R3-030614: Addition of chapter 5.1.x
-R3-030615: changes in section 5.1.2.
-R3-030615: proposed section 5.1 was reworded. | 1.6.0 | +| 5/03 | RAN2#36 | | | | | - Inclusion of contribution R2-03930, sections: 7.2.1.1 and 7.2.1.2 from decisions from RAN2/3 MBMS adhoc.
- Use of term "MBMS service context" instead of "MBMS context" throughout the document.
- Correction of spelling mistake in figure 1: "Protocol Stack for MCTCH" should be: "Protocol Stack for MTCH".
- Revision of Appendix A "MBMS Phase 1": Part of the second paragraph has been deleted due to concerns from RAN3.
- During the RAN2 MBMS AdHoc it was decided that MCCH and MTCH are to be mapped on FACH. This decision is captured at the bottom of 5.3.1 by adding the sentence "Both logical channels are mapped on FACH". FACH is also mentioned in several places in 5.3.2 (MAC Architecture) as an example (e.g. FACH). The "e.g." has now been deleted. | 1.6.1 | +| 06/03 | TSG RAN #20 | | | | | The version 2.0.0 identical to version 1.6.1 was presented in TSG RAN plenary meeting for information and approval. The TS was not approved so drafting work will continue in WG2/3 based on version 2.0.0.
The changes in version 2.1.0 compared to 2.0.0 are in Section 5.1.4 Counting where point 8 "The possibility for the RNC to receive the service Id in RRC connection request is [FFS]..." is removed. This reflects to the decision made in RAN2/3AdHoc 05/03 but was missing from earlier versions, and pointed out by RAN WG2 chairman in reflector and in TSG RAN #20. | 2.1.0 | +| 09/03 | RAN2#37
RAN3#37 | R2-031713
R3-031174
R3-031223 | | | | Editorial corrections based on R2-031713 included.
New chapter "7. MBMS reception UE Capability" created and agreed UE capability text inserted to the new chapter "7.1. UE Capability" .
Modifications based on R3-031174 to the definitions
Sections 5.1.1, 5.1.5 and 5.1.6 enhanced and sections 5.1.7, 5.1.8 and 5.1.9 created, and signalling flows updated in section 7.1.based on R3-031223

Following Editorial enhancements proposed by editor: Chapter 5.3.1.1 and 5.3.1.2 moved to under chapter 6.1. Logical channels and chapter "5.4 MBMS Reception in RRC States/Modes" moved under chapter 7. in new chapter "7.2 MBMS reception " | 2.2.0 | +| 10/03 | RAN2#38 | R2-032116

R2-032074
R2-032121 | | | | Chapter 5.2.1 MBMS User Plane Protocol Stack Architecture enhanced accordingly.
Chapter 9 Security for MBMS enhanced accordingly
Chapter 8.2.2 MBMS service availability enhanced, (message changed to information). Chapter 9.2. UE Actions for Mobility created and 9.2.4 text depending UE capability inserted | 2.3.0 | + +| Change history | | | | | | | | +|----------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|-----|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New version | +| | | R2-032277
R2-032087
R2-032275
R2-032081
R2-032281 | | | | Chapters 8.2.4. MBMS Joined Services Indication and 8.2.5 MBMS PMM-Connected State Required Indication created
Chapters 6.1. re-formatted, Section 6.2.1-6.2.5 created
The MBMS access control procedure inserted in chapter 11.1
Broadcast of MBMS System Information signalling flow added.
Tables inserted to an informative annex to identify MBMS control information and describe their mapping on transport channels | | +| | RAN3#38 | R3-031421 | | | | MBMS Time line and MBMS Service announcement definitions included in Section 3.1 Chapter 5.1.1 One Context per MBMS Service in CRNC and 5.1.8 RNC deregistration updated accordingly
Editorial harmonization of terms: MCCH and MTCH used constantly. (NCCH and CTCH removed)
In Uu signalling messages CRNC introduced to keep messages send/received in SRNC and CRNC inline. | | +| 11/03 | RAN2#39 | R2-032350
R2-032398
R2-032667
R2-032666
R2-032497 | | | | The Signalling flow MBMS service availability changed to MBMS service information in 8.2.2. Appropriate changes done in 10.2.
In the Chapter 7.1. included that MBMS UE must capability to receive two SCCPCH
MBMS notification principles chapter created as 5.1.5 and PICH bits used for MBMS notification defined in 6.2.3 physical channels chapters.
The number of different protocol entities clarified in chapter 5.2.1. The shared PDCP entity principle created in 5.1.4. Protocol layer re-establishments due to mobility defined in 10.2.
UEs measurements are clarified based in working assumption in Section 10.2.
Editorial enhancements to chapter names in chapters 5.1.1, 5.1.2 and 5.1.3 | 2.4.0 | +| 01/04 | RAN2#40
RAN3#40 | R2-04086
Meeting report
R2-040027
R2-040070
R3-040061
R3-040075
R3-040076 | | | | A chapter 11.2 Frequency layer Convergence introduced based on revised text from R2-04086
Text inserted based on conclusion on selective combining, multiplexing and measurement occasions
Editorial clarifications. Constant usage of MBMS Service Area as defined in [4]
Session stop included
High level signalling scenarios inserted
Modification to chapter 5.1.8
Modification to RNC registration procedure
Additional modifications to 5.1.8 | 2.5.0 | +| 02/04 | RAN2#41
RAN3#41 | Meeting minutes
R2-040572
R2-040690
R2-040711
R3-040577
R3-040576
R3-040314
R3-040393
R3-040575
R3-040458
R3-040516
R3-040545
Meeting minutes | | | | Selective combining, simulcast for TDD, Neighbouring cell info, included MCCH scheduling, MBMS notification and counting enhanced. MBMS access
MTCH Scheduling information signalling flow included
MBMS high level signalling scenarios updated
Editorial clean up, separation of UTRAN architecture principles and MBMS Uu principles chapter created
Functionality to filtering of MBMS notifications and Session update signalling flow included
MBMS Service Id Request to handle UEs in RRC connected PMM idle state. The Signalling flow MBMS Joined Indication modified and MBMS PMM connected stated required removed.
FFS removed from RNC De-Registration and CN De-Registration
Clarifications to MBMS Iu bearer and MBMS Session Start and Session Stop and CN De-Registration
UE linking over Iur modified according agreements
Clarification to creation of MBMS Service context after receiving the first UE linking
Editorial clean up to RAN3 specific sections.
The Iub bearer mechanisms defined.
Editorial enhancements based on comments after email review on RAN1/2/3 reflectors. | 2.6.0 | +| 03/2004 | RAN#23 | RP-040079 | | | | Upgrade towards Change Control (Release 6) and ETSI MCC clean-up. | 6.0.0 | +| 06/2004 | RP-24 | RP-040216 | 001 | | | Updates based on the MBMS ad-hoc, Budapest, 20-22 April 2004 | 6.1.0 | +| | RP-24 | RP-040216 | 002 | | | Updates to TS25.346 from the RAN3#42 meeting in Montreal, Canada, 10-14 May 2004 | 6.1.0 | +| 09/2004 | RP-25 | RP-040340 | 003 | | | Introduction of MBMS Change Information and Removal of usage of the secondary notification indicators | 6.2.0 | +| | RP-25 | RP-040340 | 004 | | | Clarifications to Frequency Layer Convergence and UE behaviour at return on Service | 6.2.0 | + +| Change history | | | | | | | | +|----------------|--------|-----------|------|-----|-----|---------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New version | +| | RP-25 | RP-040340 | 005 | | | Iur Linking for URA_PCH UEs and MBMS Session Start Request corrections for TS25.346 from RAN3#43 | 6.2.0 | +| 12/2004 | RP-26 | RP-040492 | 006 | 1 | | Actions due to MBMS session repetition and MBMS service prioritisation | 6.3.0 | +| | RP-26 | RP-040492 | 007 | 1 | | Introduction of MSCH and soft combining and other general corrections | 6.3.0 | +| | RP-26 | RP-040492 | 008 | | | Corrections to UE Linking, Session Start and addition of URA Linking and Information Exchange procedure | 6.3.0 | +| | RP-26 | RP-040492 | 009 | | | Update of Annex B | 6.3.0 | +| 03/2005 | RP-27 | RP-050080 | 010 | | | Introduction of MBMS Frequency dispersion | 6.4.0 | +| | RP-27 | RP-050080 | 011 | | | Correction on MBMS multiplexing and soft combining in TDD | 6.4.0 | +| | RP-27 | RP-050080 | 012 | | | Clarification to UE capabilities to consider MCCH reception and selective/soft combining requirements | 6.4.0 | +| | RP-27 | RP-050080 | 013 | | | Extending the counting procedure for UEs in CELL_PCH/FACH state and introducing UE initialised p-t-p setup request | 6.4.0 | +| | RP-27 | RP-050080 | 015 | | | Introduction of new procedure in MBMS stage 2 spec | 6.4.0 | +| 06/2005 | RP-28 | RP-050314 | 0016 | | | FLD scenario clarifications | 6.5.0 | +| | RP-28 | RP-050314 | 0018 | | | Handling the validity of the MBMS session Id | 6.5.0 | +| 09/2005 | RP-29 | RP-050468 | 0019 | | | Change of scope for the MBMS Access Information and MBMS P-T-P Modification Request signalling flows plus editorial corrections | 6.6.0 | +| 12/2005 | RP-30 | RP-050788 | 0020 | | | Correction to MBMS Cell Group | 6.7.0 | +| 03/2006 | RP-31 | - | - | | | Upgrade to Release 7 - no technical change | 7.0.0 | +| | RP-32 | RP-060368 | 0022 | | | Clarification of conditions for soft combining | 7.1.0 | +| 09/2006 | RP-33 | RP-060624 | 0024 | 1 | | Enhancing MBMS support for Mobile TV | 7.2.0 | +| 03/2007 | RP-35 | RP-070151 | 0026 | 1 | | Modification of the MBMS Service Area definition | 7.3.0 | +| 06/2007 | RP-36 | RP-070400 | 0027 | 4 | | MBMS TDD and FDD Physical Layer Improvements | 7.4.0 | +| | RP-36 | RP-070401 | 0029 | | | MSCH transmission - alignment to stage 3 | 7.4.0 | +| 09/2007 | RP-37 | RP-070625 | 0032 | | | MBMS Counting completion (stage 2) | 7.5.0 | +| | RP-37 | RP-070625 | 0034 | | | MBMS services naming | 7.5.0 | +| | RP-37 | RP-070632 | 0036 | | | Editorial Corrections concerning non MBSFN dedicated TDD carriers | 7.5.0 | +| 12/2007 | RP-38 | RP-070902 | 0037 | | | More improvement on Dedicated Carrier for 1.28Mcps TDD MBMS | 7.6.0 | +| | RP-38 | - | - | | | Upgrade to the Release 8 - no technical change | 8.0.0 | +| 03/2008 | RP-39 | RP-080177 | 0040 | - | | Correction on Frequency Layer Dispersion (FLD) in MBMS stage 2 | 8.1.0 | +| | RP-39 | RP-080180 | 0042 | 1 | | Clarification of FLC flag in MBMS stage 2 | 8.1.0 | +| 12/2008 | RP-42 | RP-081023 | 0045 | - | | Introduction of MBMS Improved Solution | 8.2.0 | +| | RP-42 | RP-081129 | 0046 | 2 | | Support for 3.84 Mcps MBSFN IMB operation | 8.2.0 | +| 03/2009 | RP-43 | RP-090143 | 0047 | - | | Correction of MBMS improvements | 8.3.0 | +| | RP-43 | RP-090264 | 0048 | - | | Correction on MBMS Improved Solution | 8.3.0 | +| 12/2009 | RP-46 | RP-091326 | 0049 | - | | Correction for the Synchronisation Sequence | 8.4.0 | +| 12/2009 | RP-46 | - | - | - | | Upgrade to the Release 9 - no technical change | 9.0.0 | +| 03/2010 | RP-47 | RP-100305 | 0051 | - | | Clarification on Total counter frame | 9.1.0 | +| | RP-47 | RP-100305 | 0052 | - | | Calculation of time stamp value | 9.1.0 | +| | RP-47 | RP-100291 | 0053 | - | | Update for SYNC Description | 9.1.0 | +| 03/2011 | RP-51 | - | - | - | | Upgrade to the Release 10 - no technical change | 10.0.0 | +| 09/2012 | RP-57 | - | - | - | | Upgrade to the Release 11 - no technical change | 11.0.0 | +| 03/2014 | RP-63 | RP-140363 | 0054 | - | | Introduction of MBMS Restoration | 12.0.0 | +| 12/2015 | RP-70 | - | - | - | | Upgrade to the Release 13 - no technical change | 13.0.0 | +| 03/2017 | RP-75 | - | - | - | | Upgrade to Release 14 - no technical change | 14.0.0 | +| 06/2018 | SA-80 | - | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-07 | RP-88e | - | - | - | - | Upgrade to Rel-16 version without technical change | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25401/080a7af02bc47cf21ebfae4e0be39745_img.jpg b/marked/Rel-16/25_series/25401/080a7af02bc47cf21ebfae4e0be39745_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d31bd3c8c253ecd32a5f424fb6accd6b44055bc4 --- /dev/null +++ b/marked/Rel-16/25_series/25401/080a7af02bc47cf21ebfae4e0be39745_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b943ab0bf5acbbc9c664e90cde21ee72d7090c5a51c92968b7ffc3304c872f12 +size 39711 diff --git a/marked/Rel-16/25_series/25401/0c80c383f76034e117adf5e5eaadaaf3_img.jpg b/marked/Rel-16/25_series/25401/0c80c383f76034e117adf5e5eaadaaf3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28e8c15640e702bece0bd50972a6603d75bd0b04 --- /dev/null +++ b/marked/Rel-16/25_series/25401/0c80c383f76034e117adf5e5eaadaaf3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:568431d64da8da9a33abdcf4c16534f40b5101c92d739662ab65281bc6a808d5 +size 27522 diff --git a/marked/Rel-16/25_series/25401/0d0897dd7f03672d186db9d56ea0d6f5_img.jpg b/marked/Rel-16/25_series/25401/0d0897dd7f03672d186db9d56ea0d6f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7fce7e947666b97028f1c3013e9122a840ce371 --- /dev/null +++ b/marked/Rel-16/25_series/25401/0d0897dd7f03672d186db9d56ea0d6f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc9ef6f70935682ac19d4abc5d1934be1e112d180be5a20672061e340459aae5 +size 39292 diff --git a/marked/Rel-16/25_series/25401/1033dc9fde75540d224c907681b1b7aa_img.jpg b/marked/Rel-16/25_series/25401/1033dc9fde75540d224c907681b1b7aa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56c82eda734ce150999a13ff4ca1e78beb6d89e6 --- /dev/null +++ b/marked/Rel-16/25_series/25401/1033dc9fde75540d224c907681b1b7aa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:108eb728531503be1f86e041586399c5451c235c62b45ce4ab734d96dfe5e27b +size 70944 diff --git a/marked/Rel-16/25_series/25401/1230eaa9d75a09d7e7b8509931e9190e_img.jpg b/marked/Rel-16/25_series/25401/1230eaa9d75a09d7e7b8509931e9190e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8336552268aa2fd1c928ef4edd050a56b1ed210 --- /dev/null +++ b/marked/Rel-16/25_series/25401/1230eaa9d75a09d7e7b8509931e9190e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:729e46d39cda5c5d76f939112cb24665c61b46b70cdaec5d614f4eb5bb578e3a +size 4689 diff --git a/marked/Rel-16/25_series/25401/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-16/25_series/25401/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5edde85b6b3f4b5c1230f67d899c4764c7c83f69 --- /dev/null +++ b/marked/Rel-16/25_series/25401/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8fe36e9f00028735837b3a717022755b613384891f88389d3bf1cd7dbd837eea +size 40037 diff --git a/marked/Rel-16/25_series/25401/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/25_series/25401/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c59b845fc1b03c183e060169966023147ce7b3d --- /dev/null +++ b/marked/Rel-16/25_series/25401/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3060d0bbbe11eaa468e387701b4bf495b0984cfce766710923e1f9781ad39d08 +size 59174 diff --git a/marked/Rel-16/25_series/25401/28085f681b9fff76a53c5b8b32338ee1_img.jpg b/marked/Rel-16/25_series/25401/28085f681b9fff76a53c5b8b32338ee1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..316cf94235316c489937b1a7a8b2334c9405496b --- /dev/null +++ b/marked/Rel-16/25_series/25401/28085f681b9fff76a53c5b8b32338ee1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9be60ff032f76914b1fbf779eaa5b2da6eea65fabc9a1d709ad0ba3c234fa9fe +size 68066 diff --git a/marked/Rel-16/25_series/25401/29f586959675cafdf81cf934954908eb_img.jpg b/marked/Rel-16/25_series/25401/29f586959675cafdf81cf934954908eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..331dea82419d248cc7c530b7f32abe39a54ebe48 --- /dev/null +++ b/marked/Rel-16/25_series/25401/29f586959675cafdf81cf934954908eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1e0679b94f81ed23f7fc6c66a6989632a4944cefaf0e512353c6154ada370b4 +size 26781 diff --git a/marked/Rel-16/25_series/25401/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-16/25_series/25401/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28c994546d57b9ee10b9f01cec48304115611f63 --- /dev/null +++ b/marked/Rel-16/25_series/25401/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43a1d2fd14d254b3123930bab1c4df7e3943f704f96b6dffb6698d9c22fe911c +size 6081 diff --git a/marked/Rel-16/25_series/25401/30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg b/marked/Rel-16/25_series/25401/30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f13f350fbdd879890c33e3d5c5e5b12d17557e33 --- /dev/null +++ b/marked/Rel-16/25_series/25401/30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9ead18a33dc85358ce591c9810def034008006e624021a6840615bc9fb97e0c +size 39847 diff --git a/marked/Rel-16/25_series/25401/32149dde9c4281699916b0b9518c1e3f_img.jpg b/marked/Rel-16/25_series/25401/32149dde9c4281699916b0b9518c1e3f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9b25ce3fdead3755cb82e828290d8fe93dfbeb5 --- /dev/null +++ b/marked/Rel-16/25_series/25401/32149dde9c4281699916b0b9518c1e3f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9892e7bdbe1f5b1ebcfb1d77e3dd496cdad491109274ad1552c164b252827201 +size 4966 diff --git a/marked/Rel-16/25_series/25401/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-16/25_series/25401/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d46390d0a761ac363210525c5bbd3fbffd8ecc85 --- /dev/null +++ b/marked/Rel-16/25_series/25401/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e473fed17b146fe9dd89708f14d74f01fe050a43e1624c089b539b550c39dd93 +size 100435 diff --git a/marked/Rel-16/25_series/25401/3337af75dfee8af7687b4f49914d6c93_img.jpg b/marked/Rel-16/25_series/25401/3337af75dfee8af7687b4f49914d6c93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8302c86ad2645a865c7ccfc60e74499e026cc19f --- /dev/null +++ b/marked/Rel-16/25_series/25401/3337af75dfee8af7687b4f49914d6c93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7e31d7f4c0e88797df41cd72f1a407babe4dffb908bd95d594c8d59244865c0 +size 63571 diff --git a/marked/Rel-16/25_series/25401/33a8f3f01dfa8bce75d23017855a13c5_img.jpg b/marked/Rel-16/25_series/25401/33a8f3f01dfa8bce75d23017855a13c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93200a2facfb8c458c01db860eec59fed90994c2 --- /dev/null +++ b/marked/Rel-16/25_series/25401/33a8f3f01dfa8bce75d23017855a13c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d43510226c056f69e0717a3a0f6bc4218c1661cc642e6de37060185cd1cd504b +size 42614 diff --git a/marked/Rel-16/25_series/25401/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg b/marked/Rel-16/25_series/25401/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45ae04a0e68519fb6cd3a03cf7360902fcc3e834 --- /dev/null +++ b/marked/Rel-16/25_series/25401/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22d28e79c1222c3475600fb232c1ac5e0a757bd13fdaf5ec78af2e22ffb0e757 +size 5485 diff --git a/marked/Rel-16/25_series/25401/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/Rel-16/25_series/25401/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1df9581760c36f897395ab4af3e3ca45c0b30425 --- /dev/null +++ b/marked/Rel-16/25_series/25401/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5f9046f21f98e0647b0721e6e84a4a9c69da30bceaf6edf52d0df0c4182bbdd +size 26238 diff --git a/marked/Rel-16/25_series/25401/41a438d7e4adc17c3a4005e7c9500091_img.jpg b/marked/Rel-16/25_series/25401/41a438d7e4adc17c3a4005e7c9500091_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a37375b87af9c20c78604092e953df3391a06ab --- /dev/null +++ b/marked/Rel-16/25_series/25401/41a438d7e4adc17c3a4005e7c9500091_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5cab3191687dee65c758ca9c4dfec557cc0e458855967fe2996ea53576e99e2 +size 58485 diff --git a/marked/Rel-16/25_series/25401/4346261cc730a1eb683f35e4ce9deacf_img.jpg b/marked/Rel-16/25_series/25401/4346261cc730a1eb683f35e4ce9deacf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..974ff7b53ccea6dc8dd4dea6adff4a82b014ba84 --- /dev/null +++ b/marked/Rel-16/25_series/25401/4346261cc730a1eb683f35e4ce9deacf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52fd007193e9c4c5ed0a0d4c1f32331b6facb4eb15dfafeec467a119e0c08aa9 +size 52926 diff --git a/marked/Rel-16/25_series/25401/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg b/marked/Rel-16/25_series/25401/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1204e46a151e6cad097f7a31b42c18f1c05e0aa --- /dev/null +++ b/marked/Rel-16/25_series/25401/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b92f4e4ccc9678acc581283cdbfbfffd31f88a67f927256f03d74ce6dd29df7a +size 20318 diff --git a/marked/Rel-16/25_series/25401/4ac41fc8bdb77c3dce8adfe7b954860e_img.jpg b/marked/Rel-16/25_series/25401/4ac41fc8bdb77c3dce8adfe7b954860e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23ad99deb2e214cc5bda212c1a30e394209c22b9 --- /dev/null +++ b/marked/Rel-16/25_series/25401/4ac41fc8bdb77c3dce8adfe7b954860e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e23a5e30526f0994fa411eb4c56067131f67b44fb99e6f767548cc826f487a2 +size 45393 diff --git a/marked/Rel-16/25_series/25401/51db757d054ce1ce83c436a3578b56ca_img.jpg b/marked/Rel-16/25_series/25401/51db757d054ce1ce83c436a3578b56ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8af1bbb4f4b9f73260b4d2d37bf4361687c06565 --- /dev/null +++ b/marked/Rel-16/25_series/25401/51db757d054ce1ce83c436a3578b56ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d49519dc6eafe1f224afe71fce314fcd03aea45ec36b6c7d317f535fd0ff9e24 +size 27326 diff --git a/marked/Rel-16/25_series/25401/6069ca3ced0728f1947d195c57bb0d5f_img.jpg b/marked/Rel-16/25_series/25401/6069ca3ced0728f1947d195c57bb0d5f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..368405a4be4073c3fcaed6e1358a16718b79898b --- /dev/null +++ b/marked/Rel-16/25_series/25401/6069ca3ced0728f1947d195c57bb0d5f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec1970969c789004a0f4b7c6eebb93c0be228d34c27a0aa7c4cfe4a567d6dff5 +size 4939 diff --git a/marked/Rel-16/25_series/25401/63a2519518616620ef0e53d98b923c05_img.jpg b/marked/Rel-16/25_series/25401/63a2519518616620ef0e53d98b923c05_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db605932dfc68b68bf78890a464868abe93f31c3 --- /dev/null +++ b/marked/Rel-16/25_series/25401/63a2519518616620ef0e53d98b923c05_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a510a4189d3a34ecbe54a8a818d5faac7825b8cf72fe4937a8e805dc4fa85226 +size 42573 diff --git a/marked/Rel-16/25_series/25401/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Rel-16/25_series/25401/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a7442990db00a5bdebf690d3aa83bc13bd6ac79 --- /dev/null +++ b/marked/Rel-16/25_series/25401/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf83aa232c1dbf5c5ad551612c4d5f91d56b4aba4142b827197ba409fc58d7b1 +size 184987 diff --git a/marked/Rel-16/25_series/25401/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-16/25_series/25401/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80a24af92dbb704fcee0e10872af079c225b3806 --- /dev/null +++ b/marked/Rel-16/25_series/25401/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:927cef80226997e02275dfa5e67cb551a6944922fbafd9b9eebf1f8e1faeca99 +size 81381 diff --git a/marked/Rel-16/25_series/25401/67d03c9e89620d73e3786c869e559752_img.jpg b/marked/Rel-16/25_series/25401/67d03c9e89620d73e3786c869e559752_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9d57cc38a948692e87fe336fa92826744af5631 --- /dev/null +++ b/marked/Rel-16/25_series/25401/67d03c9e89620d73e3786c869e559752_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7295728550c1a25f679b1bf9e52073e420b99c4674943ce370e0ed6eeb5b27a +size 30942 diff --git a/marked/Rel-16/25_series/25401/69e5f1993021af230d08c08aac97d9df_img.jpg b/marked/Rel-16/25_series/25401/69e5f1993021af230d08c08aac97d9df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad7a76c5c679492be0966fc6c7cc9f6ee0dfc8c9 --- /dev/null +++ b/marked/Rel-16/25_series/25401/69e5f1993021af230d08c08aac97d9df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c368688d4dc32a972d2e5066b93f6e1704eeb55d080e68ce088189581fd27c7 +size 33207 diff --git a/marked/Rel-16/25_series/25401/78e846f2858d131dc5a4dcbabcca1e4d_img.jpg b/marked/Rel-16/25_series/25401/78e846f2858d131dc5a4dcbabcca1e4d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe7075fbebfc181c2aa769c6dbf6ac7db7a628ca --- /dev/null +++ b/marked/Rel-16/25_series/25401/78e846f2858d131dc5a4dcbabcca1e4d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d89841930be08a0479ca8c716a970cd0c486aa3c06152d31d27512cebc1d40e4 +size 24196 diff --git a/marked/Rel-16/25_series/25401/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/Rel-16/25_series/25401/7ed5d5770331f31ade15439a21c31425_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba5c63d28032ffd6bacb46b46fdbbdef73e75088 --- /dev/null +++ b/marked/Rel-16/25_series/25401/7ed5d5770331f31ade15439a21c31425_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2280f94026f141d96dcd4644e8dc21fc0b43cf7eed92923cf59fd3ebb010af69 +size 27341 diff --git a/marked/Rel-16/25_series/25401/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg b/marked/Rel-16/25_series/25401/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13a90ac7c9ee728e50dcdd3c6f11bb39d759eb88 --- /dev/null +++ b/marked/Rel-16/25_series/25401/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bed957403cc5d6703c03f5026eb956e835f11310c06a607962c21163e9fca025 +size 38963 diff --git a/marked/Rel-16/25_series/25401/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/25_series/25401/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0aa218cfebd324c03e13fe2c0d69a48104b8d55a --- /dev/null +++ b/marked/Rel-16/25_series/25401/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9920dd2228be267a47ddfac0941146b9567df8b13a5b24eac1e9850ae906bb7 +size 38862 diff --git a/marked/Rel-16/25_series/25401/848073118eebfdbfdb9a60e3923fe0b3_img.jpg b/marked/Rel-16/25_series/25401/848073118eebfdbfdb9a60e3923fe0b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db63064097c2156c9386b079196b2a44dd74a9e4 --- /dev/null +++ b/marked/Rel-16/25_series/25401/848073118eebfdbfdb9a60e3923fe0b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c7ddf7dbad324a5f916b54f25a6eabfa6f849b761ff1d906b8d3ec14ee4da55 +size 48550 diff --git a/marked/Rel-16/25_series/25401/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg b/marked/Rel-16/25_series/25401/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a456e1b260ad16a6e3d8ff051dcc3469175bd8c --- /dev/null +++ b/marked/Rel-16/25_series/25401/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b34a5077421aba3da5e90d125d17340648ed43182d78f82b4c106b01799df3c +size 25726 diff --git a/marked/Rel-16/25_series/25401/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg b/marked/Rel-16/25_series/25401/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ea4d9516ec2d18449839aebea16266131079dd3 --- /dev/null +++ b/marked/Rel-16/25_series/25401/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:627c01d770588a6fdf35412a7a439ce072b855f37b975178b81eceed36a73cc1 +size 31707 diff --git a/marked/Rel-16/25_series/25401/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-16/25_series/25401/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81e83df7122748c792fb06ea6d7bebb0eb34e912 --- /dev/null +++ b/marked/Rel-16/25_series/25401/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fef88abcaf49eaa41429d9124f7ebb7c43654094c373204b839e2b08db6b1666 +size 42818 diff --git a/marked/Rel-16/25_series/25401/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg b/marked/Rel-16/25_series/25401/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c59f2f4b7dabaa018085d06841189780b030dce --- /dev/null +++ b/marked/Rel-16/25_series/25401/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:075667159c254e5d7f1a0fc0fea9de5eaed174dfb2d5b0a69ad68a9fa95dd976 +size 69539 diff --git a/marked/Rel-16/25_series/25401/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-16/25_series/25401/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2afb95bcd6a3d25695752996fb8383296291f5a1 --- /dev/null +++ b/marked/Rel-16/25_series/25401/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3848f24a76c36315f579e736f52fc165c7643ca87c219b53550891171f6a6bbd +size 33188 diff --git a/marked/Rel-16/25_series/25401/9a14684f8ae1345c6efea6f5994c730c_img.jpg b/marked/Rel-16/25_series/25401/9a14684f8ae1345c6efea6f5994c730c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a5770d426cde168d2ceec1e6091d82c09dae444f --- /dev/null +++ b/marked/Rel-16/25_series/25401/9a14684f8ae1345c6efea6f5994c730c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e9c4adb32001f029726dd8c061037a070bd17799bb54074cf5c507759c46957 +size 40493 diff --git a/marked/Rel-16/25_series/25401/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Rel-16/25_series/25401/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f10cde218c4e7a730a347a573179673713f231e --- /dev/null +++ b/marked/Rel-16/25_series/25401/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56088a8c1e7a15a03296be8001237a3c8b3f0e6f634c3e4d5f9d0f9bb11b22c4 +size 53528 diff --git a/marked/Rel-16/25_series/25401/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg b/marked/Rel-16/25_series/25401/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf77a70713a020b6d01159a32316f306003fa617 --- /dev/null +++ b/marked/Rel-16/25_series/25401/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5020f83c235012717abf6f420d8e121803cbfb2bcec4bbbc6ff57916d4e33287 +size 47921 diff --git a/marked/Rel-16/25_series/25401/9b9d2abd741ed4bafe7f78f89961c663_img.jpg b/marked/Rel-16/25_series/25401/9b9d2abd741ed4bafe7f78f89961c663_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0dfd85fa6bdfcd6b44e748fafd377efed3278b72 --- /dev/null +++ b/marked/Rel-16/25_series/25401/9b9d2abd741ed4bafe7f78f89961c663_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af573bb4ce420ee2b3c61100b2cb60850752606a156c1157961e484bd3f9d82e +size 24809 diff --git a/marked/Rel-16/25_series/25401/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg b/marked/Rel-16/25_series/25401/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97632c5c71f3a58c8c5f0a808216f1c8c7fa64ed --- /dev/null +++ b/marked/Rel-16/25_series/25401/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa6e745d7c88a1e0c8187dbb80b2d6052bdcb9500a797f80c2e4a83ff5a45548 +size 29388 diff --git a/marked/Rel-16/25_series/25401/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/25_series/25401/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d6052b72c7a5ac3bb03bfc6efbe92b15fa462692 --- /dev/null +++ b/marked/Rel-16/25_series/25401/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8838d86bf92f87d7176232dd43a819f2dc734883b7b96103155a71573dbedae3 +size 18443 diff --git a/marked/Rel-16/25_series/25401/a734898ce18e972938949637c32a34f4_img.jpg b/marked/Rel-16/25_series/25401/a734898ce18e972938949637c32a34f4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8ec10809b14f0e4f2b0f84bb07c1c3cfd68bfa4 --- /dev/null +++ b/marked/Rel-16/25_series/25401/a734898ce18e972938949637c32a34f4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8b6ff4d3a261295ee41ca5e5f54fcb2f8d7a80348b9718385c8a2180bc2cc2d +size 109630 diff --git a/marked/Rel-16/25_series/25401/adc59ed6840bcb2d392ea323abfccedc_img.jpg b/marked/Rel-16/25_series/25401/adc59ed6840bcb2d392ea323abfccedc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..876a4dcaa185b4fe97fdff3a39bc52a2830c74ee --- /dev/null +++ b/marked/Rel-16/25_series/25401/adc59ed6840bcb2d392ea323abfccedc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:665d7b81fcd36219585d13c37514d2ac1d3dafe413c69ac82176adf5675b6652 +size 39983 diff --git a/marked/Rel-16/25_series/25401/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-16/25_series/25401/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a3614decabd25799b7abdb8bbbe07a92ec38f7de --- /dev/null +++ b/marked/Rel-16/25_series/25401/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:675f8f4c6966d80e7e4197dbbdb4c6958e0153fb122e219f7af92e92fbdaccfa +size 51506 diff --git a/marked/Rel-16/25_series/25401/b44f89b176c971c7dd264c07bfef2c2a_img.jpg b/marked/Rel-16/25_series/25401/b44f89b176c971c7dd264c07bfef2c2a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06ecae174f6ab6d2592bf64757bd1e29936fa843 --- /dev/null +++ b/marked/Rel-16/25_series/25401/b44f89b176c971c7dd264c07bfef2c2a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6299cdf8970a82d80aeeb521bdbe4feb08845d222ee6a9b8f4cf14ca2a1b32e5 +size 30522 diff --git a/marked/Rel-16/25_series/25401/b7fd98a4fcc4990a613abfc31c5bdb5e_img.jpg b/marked/Rel-16/25_series/25401/b7fd98a4fcc4990a613abfc31c5bdb5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89358b2f30ca32a239b10a19a53508737d3fbef0 --- /dev/null +++ b/marked/Rel-16/25_series/25401/b7fd98a4fcc4990a613abfc31c5bdb5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:636753617be8d2a803572911a099bb8bb6099bb882b29d961789b011540a9ea9 +size 27317 diff --git a/marked/Rel-16/25_series/25401/c02e1ac41cfdcb36d2fe7c86a5c5d5a9_img.jpg b/marked/Rel-16/25_series/25401/c02e1ac41cfdcb36d2fe7c86a5c5d5a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09c7b59fe95ccf05dd74faae6c575124be9c4bb4 --- /dev/null +++ b/marked/Rel-16/25_series/25401/c02e1ac41cfdcb36d2fe7c86a5c5d5a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94b660852c3d82cc35455fdc5a0b8a126109021a32c7d8939c6dae41d6a940f3 +size 5248 diff --git a/marked/Rel-16/25_series/25401/d116934392360da963e91d840d1e45a8_img.jpg b/marked/Rel-16/25_series/25401/d116934392360da963e91d840d1e45a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1d763d3ff2ea47796945fa4b4430c49698f5357 --- /dev/null +++ b/marked/Rel-16/25_series/25401/d116934392360da963e91d840d1e45a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c3eba35990e7e8ff7e4c31b8b5db174925fd263f91220d5b4213e41a2d6bf69 +size 45424 diff --git a/marked/Rel-16/25_series/25401/d8698aacaeead6dfed9a1e448670a2e4_img.jpg b/marked/Rel-16/25_series/25401/d8698aacaeead6dfed9a1e448670a2e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ca95f9bcfcae95a5212cfb36ae8a654589b15c8 --- /dev/null +++ b/marked/Rel-16/25_series/25401/d8698aacaeead6dfed9a1e448670a2e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4706d16c1bf926e177afe4cc9432abd73a606b38a0affcbac435dbc5525e24a +size 79727 diff --git a/marked/Rel-16/25_series/25401/db5deafdae53dbc7d5972957f708c691_img.jpg b/marked/Rel-16/25_series/25401/db5deafdae53dbc7d5972957f708c691_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce34fc43ce66f5ee0dff1f41f861540798eb4abb --- /dev/null +++ b/marked/Rel-16/25_series/25401/db5deafdae53dbc7d5972957f708c691_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a39027287beccc1905849e083f91a05376093ea67e9b29c9a7729596ed78a4c9 +size 5284 diff --git a/marked/Rel-16/25_series/25401/dc37a040cf9e2add7488c7c37cbf3687_img.jpg b/marked/Rel-16/25_series/25401/dc37a040cf9e2add7488c7c37cbf3687_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81bfa7ed329b0ff2800f442ca13069f015a1151b --- /dev/null +++ b/marked/Rel-16/25_series/25401/dc37a040cf9e2add7488c7c37cbf3687_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c79b6ecf526f4a0470f5052d587f63ccb4d1f59a6ecf0546a3829ed51a257e6d +size 5518 diff --git a/marked/Rel-16/25_series/25401/ddd86d7df6cf14d68c0faf111c1e8fae_img.jpg b/marked/Rel-16/25_series/25401/ddd86d7df6cf14d68c0faf111c1e8fae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f39d1fa49976449891dc94806dc2c0521cead502 --- /dev/null +++ b/marked/Rel-16/25_series/25401/ddd86d7df6cf14d68c0faf111c1e8fae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8bdccb34e686596a3147a23406225b7425f1ba03c6ea9f1e9d96787cba5c0a0a +size 50005 diff --git a/marked/Rel-16/25_series/25401/e190b6ddb7c2e64b940749a1c5612256_img.jpg b/marked/Rel-16/25_series/25401/e190b6ddb7c2e64b940749a1c5612256_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c35a5d97d292fa3e879eed58d2f1f909052ef19 --- /dev/null +++ b/marked/Rel-16/25_series/25401/e190b6ddb7c2e64b940749a1c5612256_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0185b3a8930580349e6a23df7b8e0c8494188c967ec2b0fc70f5df49272c7a62 +size 46583 diff --git a/marked/Rel-16/25_series/25401/e3eebf9854831ba50eca8b26c468f65e_img.jpg b/marked/Rel-16/25_series/25401/e3eebf9854831ba50eca8b26c468f65e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2606f0e0bb3f11e2cbb6b6aee29d450407216d3 --- /dev/null +++ b/marked/Rel-16/25_series/25401/e3eebf9854831ba50eca8b26c468f65e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5cabda20c78dbe940d3d391b665e30a2ef7a045221640a5a1452d6ae5024d22d +size 4709 diff --git a/marked/Rel-16/25_series/25401/e97d663314aff9c29bf8971323e6539e_img.jpg b/marked/Rel-16/25_series/25401/e97d663314aff9c29bf8971323e6539e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3f6292e02327920a22381918af82e6cd59bf8ec --- /dev/null +++ b/marked/Rel-16/25_series/25401/e97d663314aff9c29bf8971323e6539e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4973a43cec083d6704b476ecdfef51a691a4f2b459aae77ed69183cb7fe472fe +size 26574 diff --git a/marked/Rel-16/25_series/25401/f87d644b84c7f7c79ba51f388161a71a_img.jpg b/marked/Rel-16/25_series/25401/f87d644b84c7f7c79ba51f388161a71a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a9e119447e46d9333c57ababf8b50a79473bacb --- /dev/null +++ b/marked/Rel-16/25_series/25401/f87d644b84c7f7c79ba51f388161a71a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79065c60ecd5848262a6643a9be2d33c1f8615a275ecf1bee4f50b1ea30bb83a +size 5265 diff --git a/marked/Rel-16/25_series/25401/raw.md b/marked/Rel-16/25_series/25401/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2d08751e3468b03cd08b6369cf6c45fa7e95bffe --- /dev/null +++ b/marked/Rel-16/25_series/25401/raw.md @@ -0,0 +1,2236 @@ + + + + + + +# Contents + +| | | +|---------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions and abbreviations ..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Abbreviations ..... | 10 | +| 3.3 Notation..... | 12 | +| 4 General principles ..... | 13 | +| 5 UMTS General architecture ..... | 13 | +| 5.1 Overview ..... | 13 | +| 5.2 General protocols architecture ..... | 14 | +| 5.2.1 User plane..... | 14 | +| 5.2.2 Control plane ..... | 15 | +| 6 UTRAN Architecture..... | 15 | +| 6.1 UTRAN Identifiers..... | 20 | +| 6.1.1 PLMN Identity..... | 20 | +| 6.1.2 CN Domain Identifier..... | 20 | +| 6.1.3 RNC Identifier..... | 20 | +| 6.1.4 Service Area Identifier..... | 20 | +| 6.1.5 Cell Identifier..... | 20 | +| 6.1.6 Local Cell Identifier ..... | 20 | +| 6.1.7 UE Identifiers ..... | 20 | +| 6.1.7.1 Usage of RNTI..... | 22 | +| 6.1.7.a UE Identifiers in GERAN A/Gb mode (1.28Mcps TDD)..... | 22 | +| 6.1.8 Identifiers for dedicated resources within UTRAN..... | 22 | +| 6.1.8.1 Radio Network Control Plane identifiers..... | 22 | +| 6.1.8.2 Transport Network Identifiers ..... | 23 | +| 6.1.8.3 Binding identifier..... | 24 | +| 6.1.9 URA Identity ..... | 25 | +| 6.1.10 Service Identifiers for MBMS ..... | 25 | +| 6.1.10.1 IP Multicast Address and APN..... | 25 | +| 6.1.10.2 TMGI ..... | 26 | +| 6.1.10.3 Session Identifier ..... | 26 | +| 6.1.10.4 MBMS Service Area..... | 26 | +| 6.1.10.5 MBMS Cell Group Identifier..... | 26 | +| 6.1.10.6 MBMS UTRAN Cell Group Identifier..... | 26 | +| 6.1.11 Transport Network Identifiers for MBMS ..... | 26 | +| 6.1.12 Binding Identifiers for MBMS ..... | 26 | +| 6.1.13 Use of Extended Identifiers ..... | 26 | +| 6.2 Transport Addresses..... | 26 | +| 6.3 Function Distribution Principles ..... | 27 | +| 7 UTRAN Functions description ..... | 27 | +| 7.1 List of functions ..... | 27 | +| 7.2 Functions description ..... | 29 | +| 7.2.0 Transfer of user data..... | 29 | +| 7.2.1 Functions related to overall system access control..... | 29 | +| 7.2.1.1 Admission Control..... | 29 | +| 7.2.1.2 Congestion Control..... | 29 | +| 7.2.1.3 System information broadcasting ..... | 29 | +| 7.2.1.4 MOCN and GWCN configuration support..... | 29 | +| 7.2.2 Radio channel ciphering and deciphering ..... | 30 | +| 7.2.3 Functions related to Mobility ..... | 30 | +| 7.2.3.1 Handover..... | 30 | +| 7.2.3.2 SRNS Relocation..... | 30 | + +| | | | +|-----------|-------------------------------------------------------------------------------------------------------------------|----| +| 7.2.3.3 | Paging support ..... | 30 | +| 7.2.3.4 | Positioning ..... | 31 | +| 7.2.3.5 | NAS Node Selection Function..... | 31 | +| 7.2.3.6 | Shared Networks Access Control ..... | 31 | +| 7.2.3.7 | GERAN System Information Retrieval ..... | 31 | +| 7.2.3.8 | Enhanced SRNS Relocation ..... | 31 | +| 7.2.3.9 | Subscriber Profile ID for RAT/Frequency Priority ..... | 32 | +| 7.2.4 | Functions related to radio resource management and control ..... | 32 | +| 7.2.4.1 | Radio resource configuration and operation..... | 32 | +| 7.2.4.2 | Radio environment survey ..... | 32 | +| 7.2.4.3 | Combining/splitting control ..... | 32 | +| 7.2.4.4 | Connection set-up and release ..... | 33 | +| 7.2.4.5 | Allocation and deallocation of Radio Bearers ..... | 33 | +| 7.2.4.6 | [TDD - Dynamic Channel Allocation (DCA)] ..... | 33 | +| 7.2.4.7 | Radio protocols function..... | 33 | +| 7.2.4.8 | RF power control ..... | 33 | +| 7.2.4.8.1 | UL Outer Loop Power Control..... | 33 | +| 7.2.4.8.2 | DL Outer Loop Power Control..... | 34 | +| 7.2.4.8.3 | UL Inner Loop Power Control ..... | 34 | +| 7.2.4.8.4 | DL Inner Loop Power Control ..... | 34 | +| 7.2.4.8.5 | UL Open Loop Power Control ..... | 34 | +| 7.2.4.8.6 | DL Open Loop Power Control ..... | 34 | +| 7.2.4.9 | Radio channel coding..... | 35 | +| 7.2.4.10 | Radio channel decoding..... | 35 | +| 7.2.4.11 | Channel coding control..... | 35 | +| 7.2.4.12 | Initial (random) access detection and handling ..... | 35 | +| 7.2.4.13 | CN Distribution function for Non Access Stratum messages..... | 35 | +| 7.2.4.14 | [3.84 Mcps and 7.68 Mcps TDD - Timing Advance]..... | 35 | +| 7.2.4.15 | Service specific function for Non Access Stratum messages ..... | 35 | +| 7.2.4.16 | [1.28 Mcps TDD – Uplink Synchronisation]..... | 36 | +| 7.2.5 | Functions related to broadcast and multicast services (broadcast/multicast interworking function
BM-IWF) ..... | 36 | +| 7.2.5.1 | Broadcast/Multicast Information Distribution ..... | 36 | +| 7.2.5.2 | Broadcast/Multicast Flow Control..... | 36 | +| 7.2.5.3 | CBS Status Reporting ..... | 36 | +| 7.2.6 | Tracing..... | 36 | +| 7.2.7 | Volume Reporting ..... | 36 | +| 7.2.8 | RAN Information Management..... | 36 | +| 7.2.9 | Functions related to MBMS ..... | 36 | +| 7.2.9.1 | MBMS provision ..... | 36 | +| 7.2.9.2 | MBMS Notification Coordination ..... | 37 | +| 7.2.10 | SIPTO at Iu-PS ..... | 37 | +| 7.2.11 | Explicit Congestion Notification ..... | 37 | +| 7.2.12 | MDT ..... | 37 | +| 7.2.13 | SIPTO at the Local Network with Standalone GW ..... | 37 | +| 7.2.14 | Traffic Volume for RAN Sharing..... | 37 | +| 8 | Mobility Management..... | 38 | +| 8.1 | Signalling connection..... | 38 | +| 8.2 | Consequences for Mobility Handling ..... | 38 | +| 9 | Synchronisation..... | 38 | +| 9.1 | SYNCHRONISATION MODEL..... | 38 | +| 10 | UTRAN O&M Requirements ..... | 39 | +| 10.1 | O&M of Node B..... | 39 | +| 10.1.1 | Implementation Specific O&M ..... | 40 | +| 10.1.2 | Logical O&M ..... | 40 | +| 10.2 | O&M of RNC..... | 41 | +| 10.2.1 | O&M requirements..... | 41 | +| 11 | UTRAN Interfaces ..... | 41 | +| 11.1 | General Protocol Model for UTRAN Interfaces ..... | 41 | + +| | | | +|--------------------------------|---------------------------------------------------------------------------------------------------------------------------|-----------| +| 11.1.1 | General ..... | 41 | +| 11.1.2 | Horizontal Layers ..... | 41 | +| 11.1.3 | Vertical Planes..... | 41 | +| 11.1.3.1 | Control Plane ..... | 41 | +| 11.1.3.2 | User Plane..... | 42 | +| 11.1.3.3 | Transport Network Control Plane..... | 42 | +| 11.1.3.4 | Transport Network User Plane ..... | 43 | +| 11.2 | Protocol Model (Informative) ..... | 43 | +| 11.2.1 | RACH Transport Channel..... | 43 | +| 11.2.2 | CPCH [FDD] Transport Channel..... | 44 | +| 11.2.3 | FACH Transport Channel..... | 44 | +| 11.2.4 | DCH Transport Channel..... | 45 | +| 11.2.5 | DSCH Transport Channel [TDD]..... | 46 | +| 11.2.6 | USCH Transport Channel [TDD]..... | 47 | +| 11.2.7 | HS-DSCH Transport Channel..... | 48 | +| 11.2.8 | E-DCH Transport Channel..... | 51 | +| 12 | UTRAN Performance Requirements ..... | 53 | +| 12.1 | UTRAN delay requirements..... | 53 | +| Annex A (informative): | SPID ranges and mapping of SPID values to cell reselection and inter-RAT/inter frequency handover priorities ..... | 54 | +| Annex A2 (Informative): | Deployment of Extended Identifiers..... | 55 | +| A2.1 | RNC Sizing Changes..... | 55 | +| A2.1.1 | U-RNTI Considerations..... | 55 | +| A2.1.2 | Extend S-RNTI and reduce RNC-ID: Solution 1 ..... | 56 | +| A2.1.3 | Pooled RNCs: Solution 2..... | 56 | +| A2.2 | RNC ID Extension ..... | 57 | +| A2.2.1 | Solution for RNC-ID Extension ..... | 57 | +| A2.2.2 | Rules for Configuration..... | 58 | +| A2.2.3 | Configuration Example ..... | 61 | +| Annex B (informative): | Change history..... | 63 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document describes the overall architecture of the UTRAN, including internal interfaces and assumptions on the radio and Iu interfaces. + +# --- 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] Void +- [2] 3GPP TS 23.110: "UMTS Access Stratum Services and Functions". +- [3] Void +- [4] 3GPP TS 25.442: "UTRAN Implementation Specific O&M Transport". +- [5] 3GPP TS 25.402: "Synchronisation in UTRAN, Stage 2". +- [6] 3GPP TS 23.003: "Numbering, Addressing and Identification". +- [7] 3GPP TS 25.331: " Radio Resource Control (RRC); Protocol specification". +- [8] 3GPP TS 23.101: "General UMTS Architecture". +- [9] 3GPP TS 25.414: " UTRAN Iu Interface Data Transport & Transport Signalling". +- [10] 3GPP TS 25.424: "UTRAN Iur Interface Data Transport & Transport Signalling for Common Transport Channel Data Streams". +- [11] 3GPP TS 25.434: "UTRAN Iub Interface Data Transport & Transport Signalling for Common Transport Channel Data Streams". +- [12] IETF RFC 2460 (1998-12): "Internet Protocol, Version 6 (Ipv6) Specification". +- [13] Void +- [14] IETF RFC 768 (1980-08): "User Datagram Protocol". +- [15] "Information technology – Open Systems Interconnection – Network service definition", X.213, ISO/IEC 8348. +- [16] "Information technology – Open Systems Interconnection – Network service definition Amendment 1: Addition of the Internet protocol address format identifier", X.213/Amd.1, ISO/IEC 8348. +- [17] IETF RFC 791 (1981-09): "Internet Protocol". +- [18] 3GPP TS 25.426: "UTRAN Iur and Iub Interface Data Transport & Transport Signalling for DCH Data Streams". +- [19] Void + +- [20] 3GPP TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes". +- [21] 3GPP TR 43.930: "Iur-g interface; Stage 2". +- [22] 3GPP TR 44.901: "External Network Assisted Cell Change". +- [23] 3GPP TS 48.018: "General Packet Radio Service (GPRS); BSS GPRS Protocol (BSSGP)". +- [24] 3GPP TS 25.460: "UTRAN Iuant Interface: General Aspects and Principles". +- [25] 3GPP TS 25.461: "UTRAN Iuant Interface: Layer 1". +- [26] 3GPP TS 25.462: "UTRAN Iuant Interface: Signalling Transport". +- [27] Void +- [28] 3GPP TS 23.251: "Network sharing - Architecture and functional description". +- [29] 3GPP TS 25.410: "UTRAN Iu Interface: general aspects and principles". +- [30] 3GPP TS 25.346: "Introduction of the Multimedia Broadcast Multicast Service (MBMS) in the Radio Access Network (RAN); Stage 2". +- [31] 3GPP TS 25.413: "UTRAN Iu Interface RANAP Signalling". +- [32] 3GPP TS 25.466: "UTRAN Iuant Interface: Application part". +- [33] 3GPP TS 25.305: "Stage 2 functional specification of UE positioning in UTRAN". +- [34] IETF RFC 4548 (2006-05): "Internet Code Point (ICP) Assignments for NSAP Addresses" +- [35] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA), Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; stage 2". +- [36] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [37] IETF RFC 3168 (2001-09): "The Addition of Explicit Congestion Notification (ECN) to IP". +- [38] 3GPP TS 37.320: "Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRA); Radio measurement collection for Minimization of Drive Tests (MDT); Overall description; Stage 2". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**[1.28Mcps TDD - Multi-frequency Cell:** If multiple frequencies are configured in one cell, the cell is defined as the multi-frequency cell.] + +**[1.28Mcps TDD - Primary frequency:** In a multi-frequency cell, the frequency on which the P-CCPCH is transmitted is defined as primary frequency.] + +**[1.28Mcps TDD - Secondary frequency:** In a multi-frequency cell, any frequency other than the primary frequency is defined as secondary frequency.] + +**ALCAP:** generic name for the transport signalling protocols used to set-up and tear-down transport bearers + +**Cell:** Radio Network object that can be uniquely identified by a User Equipment from a (cell) identification that is broadcasted over a geographical area from one *UTRAN Access Point* +A Cell is either FDD or TDD mode. + +**DCN-ID:** DCN identity identifies a specific dedicated core network (DCN). + +**Iu:** interface between an RNC and an MSC, SGSN or CBC, providing an interconnection point between the RNS and the Core Network. It is also considered as a reference point + +**Iub:** interface between the RNC and the Node B + +**Iur:** logical interface between two RNCs + +Whilst logically representing a point to point link between RNCs, the physical realisation need not be a point to point link. + +**Iur-g:** logical interface between RNC/BSS and BSS + +Whilst logically representing a point to point link between RNC/BSS and BSS, the physical realisation need not be a point to point link. + +**Logical Model:** Logical Model defines an abstract view of a network or network element by means of information objects representing network element, aggregations of network elements, the topological relationship between the elements, endpoints of connections (termination points), and transport entities (such as connections) that transport information between two or more termination points + +The information objects defined in the Logical Model are used, among others, by connection management functions. In this way, a physical implementation independent management is achieved. + +**Network sharing supporting UE:** as defined in TS 23.251 [28]. + +**Network sharing non-supporting UE:** as defined in TS 23.251 [28]. + +**Node B:** logical node in the RNS responsible for radio transmission / reception in one or more cells to/from the UE +The logical node terminates the Iub interface towards the RNC. + +**Radio Resources:** resources that constitute the radio interface in UTRAN, e.g. frequencies, scrambling codes, spreading factors, power for common and dedicated channels + +**Node B Application Part:** Radio Network Signalling over the Iub + +**Radio Network Controller:** logical node in the RNS in charge of controlling the use and the integrity of the radio resources + +**Controlling RNC:** role an RNC can take with respect to a specific set of Node B's + +There is only one Controlling RNC for any Node B. The Controlling RNC has the overall control of the logical resources of its node B's. + +**MBMS Master RNC:** role an RNC can take with respect to one or more specific MBSFN cluster(s) + +MRNC may be used for Inter-RNC MBSFN operation whenever dynamic synchronization of radio resources used for MBMS services is centrally controlled. There is only one MBMS Master RNC for any MBSFN cluster, which may control one or more MBSFN cluster(s). The MRNC has the overall control of the logical resources of the RNSs that are used for MBSFN operation within the MBSFN cluster(s). + +**Radio Network Subsystem:** RNS can be either a full UTRAN or only a part of a UTRAN + +An RNS offers the allocation and release of specific radio resources to establish means of connection in between an UE and the UTRAN. A Radio Network Subsystem contains one RNC and is responsible for the resources and transmission/reception in a set of cells. + +**Serving RNS:** role an RNS can take with respect to a specific connection between an UE and UTRAN + +There is one Serving RNS for each UE that has a connection to UTRAN. The Serving RNS is in charge of the radio connection between a UE and the UTRAN. The Serving RNS terminates the Iu for this UE. + +**Drift RNS:** role an RNS can take with respect to a specific connection between an UE and UTRAN + +An RNS that supports the Serving RNS with radio resources when the connection between the UTRAN and the UE need to use cell(s) controlled by this RNS is referred to as Drift RNS. + +**Radio Access Network Application Part:** Radio Network Signalling over the Iu + +**Radio Network Subsystem Application Part:** Radio Network Signalling over the Iur + +**RRc Connection:** point-to-point bi-directional connection between RRc peer entities on the UE and the UTRAN sides, respectively + +An UE has either zero or one RRc connection. + +**Stand-Alone SMLC:** as defined in TS 25.305 [33]. + +**User Equipment:** Mobile Equipment with one or several UMTS Subscriber Identity Module(s) + +A device allowing a user access to network services via the Uu interface. The UE is defined in ref. TS 23.101 [8]. If this term is used in the context of Iur-g, it means MS in case it uses radio resources of a DBSS. + +**Universal Terrestrial Radio Access Network:** UTRAN is a conceptual term identifying that part of the network which consists of RNCs and Node Bs between Iu and Uu + +The concept of UTRAN instantiation is currently undefined. + +**User Datagram Protocol:** as defined in IETF RFC 768 [14]. + +**UTRAN Access Point:** conceptual point within the UTRAN performing radio transmission and reception + +A UTRAN access point is associated with one specific *cell*, i.e. there exists one UTRAN access point for each cell. It is the UTRAN-side end point of a *radio link*. + +**Radio Link:** "radio link" is a logical association between a single User Equipment and a single UTRAN access point. Its physical realisation comprises one or more radio bearer transmissions. + +**Radio Link Set:** set of one or more Radio Links that has a common generation of Transmit Power Control (TPC) commands in the DL + +**Uu:** Radio interface between UTRAN and the User Equipment + +**RAB sub-flows:** Radio Access Bearer can be realised by UTRAN through several sub-flows + +These sub-flows correspond to the NAS service data streams that have QoS characteristics that differ in a predefined manner within a RAB e.g. different reliability classes. + +RAB sub-flows have the following characteristics: + +- 1) The sub-flows of a RAB are established and released at the RAB establishment and release, respectively. +- 2) The sub-flows of a RAB are submitted and delivered together at the RAB SAP. +- 3) The sub-flows of a RAB are carried over the same Iu transport bearer. +- 4) The sub-flows of a RAB are organised in a predefined manner at the SAP and over the Iu interface. The organisation is imposed by the NAS as part of its co-ordination responsibility. + +**Set of co-ordinated DCHs:** set of co-ordinated DCHs is a set of dedicated transport channels that are always established and released in combination + +Individual DCHs within a set of co-ordinated DCHs cannot be operated on individually e.g. if the establishment of one DCH fails, the establishment of all other DCHs in the set of co-ordinated DCHs shall be terminated unsuccessfully. A set of coordinated DCHs is transferred over one transport bearer. All DCHs in a set of co-ordinated DCHs shall have the same TTI. + +**Shared Network Area (SNA):** Area consisting of one or more LA's to which access can be controlled. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|--------|-------------------------------------------| +| AAL | ATM Adaptation Layer | +| AAL2 | ATM Adaptation Layer 2 | +| ALCAP | Access Link Control Application Part | +| APN | Access Point Name | +| ATM | Asynchronous Transfer Mode | +| BM-IWF | Broadcast Multicast Interworking Function | +| BMC | Broadcast/Multicast Control | +| BSS | Base Station Subsystem | +| CBC | Cell Broadcast Centre | + +| | | +|----------|--------------------------------------------------| +| CBS | Cell Broadcast Service | +| CN | Core Network | +| CRNC | Controlling Radio Network Controller | +| DCH | Dedicated Channel | +| DCN | Dedicated Core Network | +| DL | Downlink | +| DRNS | Drift RNS | +| DSP | Domain Specific Part | +| EAB | Extended Access Barring | +| E-DCH | Enhanced UL DCH | +| EDGE | Enhanced Data rates for Global Evolution | +| FACH | Forward Access Channel | +| FFS | For Further Study | +| GERAN | GSM EDGE Radio Access Network | +| GSM | Global System for Mobile Communications | +| GTP | GPRS Tunnelling Protocol | +| GWCN | GateWay Core Network | +| HPLMN | Home PLMN | +| IDP | Initial Domain Part | +| IPv4 | Internet Protocol, version 4 | +| IPv6 | Internet Protocol, version 6 | +| LA | Location Area | +| L-GW | Local GateWay | +| MAC | Medium Access Control | +| MBMS | Multimedia Broadcast Multicast Service | +| MCCH | MBMS point-to-multipoint Control Channel | +| MDT | Minimization of Drive-Tests | +| MOCN | Multi Operator Core Network | +| MRNC | MBMS Master Radio Network Controller | +| MSCH | MBMS point-to-multipoint Scheduling Channel | +| MTCH | MBMS point-to-multipoint Traffic Channel | +| NACC | Network Assisted Cell Change | +| NAS | Non Access Stratum | +| NBAP | Node B Application Part | +| NNSF | NAS Node Selection Function | +| NSAP | Network Service Access Point | +| PCH | Paging Channel | +| PLMN | Public Land Mobile Network | +| PTM | Point To Multipoint | +| PTP | Point To Point | +| QoE | Quality of Experience | +| QoS | Quality of Service | +| RAB | Radio Access Bearer | +| RACH | Random Access Channel | +| RANAP | Radio Access Network Application Part | +| RET | Remote Electrical Tilting | +| RIM | RAN Information Management | +| RNC | Radio Network Controller | +| RNL | Radio Network Layer | +| RNS | Radio Network Subsystem | +| RNSAP | Radio Network Subsystem Application Part | +| RNTI | Radio Network Temporary Identity | +| SAB | Service Area Broadcast | +| SAS | Stand-Alone SMLC | +| SIPTO | Selected IP Traffic Offload | +| SIPTO@LN | Selected IP Traffic Offload at the Local Network | +| SMLC | Serving Mobile Location Centre | +| SNA | Shared Network Area | +| SRNC | Serving Radio Network Controller | +| SRNS | Serving RNS | +| S-GW | Serving GateWay | +| TMA | Tower Mounted Amplifier | + +| | | +|-------|--------------------------------------------| +| TBSS | Target BSS | +| TEID | Tunnel Endpoint Identifier | +| TMGI | Temporary Mobile Group Identity | +| TNL | Transport Network Layer | +| TTI | Transmission Time Interval | +| UDP | User Datagram Protocol | +| UE | User Equipment | +| UL | Uplink | +| UMTS | Universal Mobile Telecommunication System | +| URA | UTRAN Registration Area | +| USIM | UMTS Subscriber Identity Module | +| UTRAN | Universal Terrestrial Radio Access Network | + +## 3.3 Notation + +For the purposes of the present document, the following notations apply: + +- [FDD] This tagging of a word indicates that the word preceding the tag "[FDD]" applies only to FDD. This tagging of a heading indicates that the heading preceding the tag "[FDD]" and the section following the heading applies only to FDD. +- [TDD] This tagging of a word indicates that the word preceding the tag "[TDD]" applies only to TDD, including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[TDD]" and the section following the heading applies only to TDD, including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. +- [3.84Mcps TDD] This tagging of a word indicates that the word preceding the tag "[3.84Mcps TDD]" applies only to 3.84Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[3.84Mcps TDD]" and the section following the heading applies only to 3.84Mcps TDD. +- [1.28Mcps TDD] This tagging of a word indicates that the word preceding the tag "[1.28Mcps TDD]" applies only to 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[1.28Mcps TDD]" and the section following the heading applies only to 1.28Mcps TDD. +- [7.68Mcps TDD] This tagging of a word indicates that the word preceding the tag "[7.68Mcps TDD]" applies only to 7.68Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[7.68Mcps TDD]" and the section following the heading applies only to 7.68Mcps TDD. +- [FDD - ...] This tagging indicates that the enclosed text following the "[FDD - " applies only to FDD. Multiple sequential paragraphs applying only to FDD are enclosed separately to enable insertion of TDD specific (or common) paragraphs between the FDD specific paragraphs. +- [TDD - ...] This tagging indicates that the enclosed text following the "[TDD - " applies only to TDD including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. Multiple sequential paragraphs applying only to TDD are enclosed separately to enable insertion of FDD specific (or common) paragraphs between the TDD specific paragraphs. +- [3.84Mcps TDD - ...] This tagging indicates that the enclosed text following the "[3.84Mcps TDD - " applies only to 3.84Mcps TDD. Multiple sequential paragraphs applying only to 3.84Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 3.84Mcps TDD specific paragraphs. +- [1.28Mcps TDD - ...] This tagging indicates that the enclosed text following the "[1.28Mcps TDD - " applies only to 1.28Mcps TDD. Multiple sequential paragraphs applying only to 1.28Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 1.28Mcps TDD specific paragraphs. +- [7.68Mcps TDD - ...] This tagging indicates that the enclosed text following the "[7.68Mcps TDD - " applies only to 7.68Mcps TDD. Multiple sequential paragraphs applying only to 7.68Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 7.68Mcps TDD specific paragraphs. + +| | | +|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Message | When referring to a message in the specification, the MESSAGE NAME is written with all letters in upper case characters followed by the word "message", e.g. RADIO LINK SETUP REQUEST message. | +| IE | When referring to an information element (IE) in the specification, the Information Element Name is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation "IE", e.g. Transport Format Set IE . | +| Value of an IE | When referring to the value of an information element (IE) in the specification, the "Value" is enclosed by quotation marks, e.g. "Abstract Syntax Error (Reject)". | +| Frame | When referring to a control or data frame in the specification, the CONTROL/DATA FRAME NAME is written with all letters in upper case characters followed by the words "control/data frame", e.g. FACH FLOW CONTROL control frame. | + +# --- 4 General principles + +The general principles guiding the definition of UTRAN Architecture as well as the UTRAN interfaces are the following: + +- Logical separation of signalling and data transport networks. +- UTRAN and CN functions are fully separated from transports functions. Addressing scheme used in UTRAN and CN shall not be tied to the addressing schemes of transport functions. The fact that some UTRAN or CN function resides in the same equipment as some transport functions does not make the transport functions part of the UTRAN or the CN. +- [FDD - Macro diversity is fully handled in the UTRAN.] +- Mobility for RRC connection is fully controlled by the UTRAN. +- When defining the UTRAN interfaces the following principles were followed: The functional division across the interfaces shall have as few options as possible. +- Interfaces should be based on a logical model of the entity controlled through this interface. +- One Physical Network Element can implement multiple Logical Nodes. + +Transport Network Control Plane is a functional plane in the interfaces protocol structure that is used for the transport bearer management. The actual signalling protocol that is in use within the Transport Network Control Plane depends on the underlying transport layer technology. The intention is not to specify a new UTRAN specific Application Part for the Transport Network Control Plane but to use signalling protocols standardised in other groups (if needed) for the applied transport layer technology. + +# --- 5 UMTS General architecture + +## 5.1 Overview + +Figure 1 shows a simplified UMTS architecture with the external reference points and interfaces to the UTRAN. + +![Figure 1: UMTS Architecture diagram showing CN (Core Network) connected to UTRAN (UMTS Terrestrial Radio Access Network) via the Iu interface, and UTRAN connected to UE (User Equipment) via the Uu interface.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +Diagram illustrating the UMTS Architecture. It shows three main components stacked vertically: CN (Core Network) at the top, UTRAN (UMTS Terrestrial Radio Access Network) in the middle, and UE (User Equipment) at the bottom. The CN is connected to the UTRAN via the Iu interface. The UTRAN is connected to the UE via the Uu interface. + +UTRAN UMTS Terrestrial Radio Access Network + CN Core Network + UE User Equipment + +Figure 1: UMTS Architecture diagram showing CN (Core Network) connected to UTRAN (UMTS Terrestrial Radio Access Network) via the Iu interface, and UTRAN connected to UE (User Equipment) via the Uu interface. + +**Figure 1: UMTS Architecture** + +## 5.2 General protocols architecture + +The protocols over Uu and Iu interfaces are divided into two structures: + +### - **User plane protocols** + +These are the protocols implementing the actual radio access bearer service, i.e. carrying user data through the access stratum. + +### - **Control plane protocols** + +These are the protocols for controlling the radio access bearers and the connection between the UE and the network from different aspects (including requesting the service, controlling different transmission resources, handover & streamlining etc.). Also a mechanism for transparent transfer of NAS messages is included. + +### 5.2.1 User plane + +The radio access bearer service is offered from SAP to SAP by the Access Stratum. Figure 2 shows the protocols on the Uu and Iu interfaces that linked together provide this radio access bearer service. + +![Figure 2: Iu and Uu User plane diagram showing the protocol stack across the UE, UTRAN, and CN. The Non-Access Stratum (NAS) is shown above the Access Stratum. The Access Stratum contains Radio protocols (1) in the UE, Radio protocols (1) and Iu protocols (2) in the UTRAN, and Iu protocols (2) in the CN. The Radio (Uu) interface is between the UE and UTRAN, and the Iu interface is between the UTRAN and CN.](e190b6ddb7c2e64b940749a1c5612256_img.jpg) + +Diagram illustrating the Iu and Uu User plane. The diagram shows the protocol stack across the UE, UTRAN, and CN. The Non-Access Stratum (NAS) is shown above the Access Stratum. The Access Stratum contains Radio protocols (1) in the UE, Radio protocols (1) and Iu protocols (2) in the UTRAN, and Iu protocols (2) in the CN. The Radio (Uu) interface is between the UE and UTRAN, and the Iu interface is between the UTRAN and CN. + +Figure 2: Iu and Uu User plane diagram showing the protocol stack across the UE, UTRAN, and CN. The Non-Access Stratum (NAS) is shown above the Access Stratum. The Access Stratum contains Radio protocols (1) in the UE, Radio protocols (1) and Iu protocols (2) in the UTRAN, and Iu protocols (2) in the CN. The Radio (Uu) interface is between the UE and UTRAN, and the Iu interface is between the UTRAN and CN. + +- (1) The radio interface protocols are defined in documents TS 25.2xx and TS 25.3xx. + (2) The Iu interface protocols are defined in documents TS 25.41x. + +**Figure 2: Iu and Uu User plane** + +### 5.2.2 Control plane + +Figure 3 shows the control plane (signalling) protocol stacks on Iu and Uu interfaces. + +![Figure 3: Iu and Uu Control plane diagram showing protocol stacks for UE, UTRAN, and CN across Non-Access and Access strata.](9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg) + +The diagram illustrates the control plane protocol stacks for the Uu and Iu interfaces. It is divided into two main strata: the Non-Access Stratum (NAS) at the top and the Access Stratum (AS) below. The UE (User Equipment) on the left contains a NAS stack (CM, MM, GMM, SM (3)) and an AS stack (Radio protocols (1)). The UTRAN (Radio Network Subsystem) in the center contains an AS stack (Radio protocols (1) and Iu protocols (2)). The CN (Core Network) on the right contains a NAS stack (CM, MM, GMM, SM (3)) and an AS stack (Iu protocols (2)). The Uu interface is the radio interface between the UE and the UTRAN. The Iu interface is the interface between the UTRAN and the CN. Arrows indicate the flow of signalling messages between the NAS and AS stacks within each entity, and between the AS stacks across the interfaces. + +Figure 3: Iu and Uu Control plane diagram showing protocol stacks for UE, UTRAN, and CN across Non-Access and Access strata. + +- (1) The radio interface protocols are defined in documents TS 25.2xx and TS 25.3xx. +- (2) The protocol is defined in documents TS 25.41x. (Description of Iu interface). +- (3) **CM, MM, GMM, SM:** This exemplifies a set of NAS control protocols between UE and CN. There may be different NAS protocol stacks in parallel. The evolution of the protocol architecture for these protocols is outside the scope of the present document. + +**Figure 3: Iu and Uu Control plane** + +NOTE: Both the Radio protocols and the Iu protocols contain a mechanism to transparently transfer NAS messages. + +# 6 UTRAN Architecture + +The UTRAN consists of a set of Radio Network Subsystems connected to the Core Network through the Iu. + +A RNS consists of a Radio Network Controller one or more Node Bs and optionally one SAS. A Node B is connected to the RNC through the Iub interface. + +A Node B can support FDD mode, TDD mode or dual-mode operation. + +There are three chip-rate options in the TDD mode: 7.68 Mcps TDD, 3.84 Mcps TDD and 1.28 Mcps TDD. Each TDD cell supports one of these options. + +A Node B which supports TDD cells can support one chip-rate option only, or more than one option. + +A RNC which supports TDD cells can support one chip-rate option only, or more than one option. + +The RNC is responsible for the Handover decisions that require signalling to the UE. + +A RNC may include a combining/splitting function to support combination/splitting of information streams (see subclause 7.2.4.3). + +Inside the UTRAN, the RNCs of the Radio Network Subsystems can be interconnected together through the Iur. Iu(s) and Iur are logical interfaces. Iur can be conveyed over direct physical connection between RNCs or virtual networks using any suitable transport network. + +The UTRAN architecture is shown in figure 4. + +![Figure 4: UTRAN Architecture diagram showing a Core Network connected to two RNCs via Iu interfaces. Each RNC is part of an RNS and is connected to two Node Bs via Iub interfaces. The two RNCs are also interconnected via an Iur interface.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +The diagram illustrates the UTRAN architecture. At the top, a 'Core Network' block is connected to two 'RNC' (Radio Network Controller) blocks via 'Iu' interfaces. Each 'RNC' is enclosed in a dashed box labeled 'RNS' (Radio Network Subsystem). Within each 'RNS', the 'RNC' is connected to two 'Node B' (NodeB) blocks via 'Iub' interfaces. Each 'Node B' is represented by a rectangle with three circles below it. The two 'RNC' blocks are also connected to each other via an 'Iur' interface. + +Figure 4: UTRAN Architecture diagram showing a Core Network connected to two RNCs via Iu interfaces. Each RNC is part of an RNS and is connected to two Node Bs via Iub interfaces. The two RNCs are also interconnected via an Iur interface. + +**Figure 4: UTRAN Architecture** + +Regarding the UE positioning method, the RNC may have full internal support for this function and/or may be connected to one SAS via the Iupc interface. The following picture illustrates the resulting UTRAN architecture when the Iupc interface is adopted. + +![Figure 4a: UTRAN Architecture with the Iupc option diagram showing a Core Network connected to two RNCs via Iu interfaces. Each RNC is part of an RNS and is connected to two Node Bs via Iub interfaces. The two RNCs are also interconnected via an Iur interface. Additionally, the left RNC is connected to an SAS (Serving AS) via an Iupc interface.](41a438d7e4adc17c3a4005e7c9500091_img.jpg) + +This diagram shows the UTRAN architecture with the Iupc option. It is similar to Figure 4, but the left 'RNC' is also connected to an 'SAS' (Serving AS) block via an 'Iupc' interface. The 'SAS' is located within the left 'RNS' dashed box. All other connections (Core Network to RNCs via Iu, RNCs to Node Bs via Iub, and RNCs to each other via Iur) remain the same. + +Figure 4a: UTRAN Architecture with the Iupc option diagram showing a Core Network connected to two RNCs via Iu interfaces. Each RNC is part of an RNS and is connected to two Node Bs via Iub interfaces. The two RNCs are also interconnected via an Iur interface. Additionally, the left RNC is connected to an SAS (Serving AS) via an Iupc interface. + +**Figure 4a: UTRAN Architecture with the Iupc option** + +The RNC may be connected to BSS supporting GERAN Iu mode via the Iur-g interface. The following picture illustrates the UTRAN and GERAN Iu mode connection when the Iur-g interface is adopted. For 1.28Mcps TDD, the RNC may be connected to BSS supporting GERAN A/Gb mode via the Iur-g interface. The figure 4c illustrates the UTRAN and GERAN A/Gb mode connection when the Iur-g interface is adopted for 1.28Mcps TDD. + +![Figure 4b: UTRAN and GERAN Iu mode connection with Iur-g](8307f6b04df072c9332f9987e034272c_img.jpg) + +This diagram illustrates the network architecture for UTRAN and GERAN Iu mode connection with Iur-g. At the top is a 'Core Network' block. Below it, a 'GERAN BSS' block is connected to the Core Network via an 'Iu' interface. To the right, an 'RNS' (Radio Network Subsystem) block is also connected to the Core Network via an 'Iu' interface. The 'GERAN BSS' and the 'RNS' are connected to each other via an 'Iur-g' interface. Inside the 'RNS' block, there is an 'RNC' (Radio Network Controller) block at the top, which is connected to two 'Node B' blocks (represented by rectangles with three circles below them) via 'Iub' interfaces. + +Figure 4b: UTRAN and GERAN Iu mode connection with Iur-g + +**Figure 4b: UTRAN and GERAN Iu mode connection with Iur-g** + +![Figure 4c: UTRAN and GERAN A/Gb mode connection with Iur-g for 1.28Mcps TDD](33a8f3f01dfa8bce75d23017855a13c5_img.jpg) + +This diagram illustrates the network architecture for UTRAN and GERAN A/Gb mode connection with Iur-g for 1.28Mcps TDD. At the top is a 'Core Network' block. Below it, a 'GERAN BSS' block is connected to the Core Network via 'A' and 'Gb' interfaces. To the right, an 'RNS' block is connected to the Core Network via an 'Iu' interface. The 'GERAN BSS' and the 'RNS' are connected to each other via an 'Iur-g' interface. Inside the 'RNS' block, there is an 'RNC 1.28Mcps TDD' block at the top, which is connected to two 'Node B' blocks (represented by rectangles with three circles below them) via 'Iub' interfaces. + +Figure 4c: UTRAN and GERAN A/Gb mode connection with Iur-g for 1.28Mcps TDD + +**Figure 4c: UTRAN and GERAN A/Gb mode connection with Iur-g for 1.28Mcps TDD** + +Each RNS is responsible for the resources of its set of cells. + +For each connection between User Equipment and the UTRAN, One RNS is the Serving RNS. When required, Drift RNSs support the Serving RNS by providing radio resources as shown in figure 5. The role of an RNS (Serving or Drift) is on a per connection basis between a UE and the UTRAN. + +![Figure 5: Serving and Drift RNS](29f586959675cafdf81cf934954908eb_img.jpg) + +This diagram illustrates the network architecture for Serving and Drift RNS. At the top is a 'Core Network' block. Below it, a 'DRNS' (Drift Radio Network Subsystem) block and an 'SRNS' (Serving Radio Network Subsystem) block are connected to the Core Network via an 'Iu' interface. The 'DRNS' and the 'SRNS' are connected to each other via an 'Iur' interface. Inside the 'DRNS' block, there is a 'Cells' block (represented by a row of circles) which is connected to a 'UE' (User Equipment) block. Inside the 'SRNS' block, there is also a 'Cells' block (represented by a row of circles) which is connected to the 'UE' block. + +Figure 5: Serving and Drift RNS + +**Figure 5: Serving and Drift RNS** + +To support UE mobility between UTRAN and GERAN Iu mode, the Serving RNS may be connected to the DBSS and vice versa as illustrated in figures 5a and 5b. For 1.28Mcps TDD, to support UE mobility between UTRAN and + +GERAN A/Gb mode, the Serving RNS may be connected to the TBSS as illustrated in figure 5c. The role of an RNS or BSS (Serving or Drift) is on a per connection basis between a UE and the UTRAN/Iu mode, or between a UE and the UTRAN/GERAN A/Gb mode for 1.28Mcp TDD. + +![Figure 5a: Serving RNS and Drift BSS, GERAN Iu mode. The diagram shows a Core Network at the top connected via an Iu interface to an SRNS (Serving RNS) and a DBSS (Drift BSS). The DBSS is connected to a Cell, which is in turn connected to an MS (Mobile Station). The SRNS is also connected to a Cell, which is connected to the MS.](9b9d2abd741ed4bafe7f78f89961c663_img.jpg) + +The diagram illustrates the network architecture for GERAN Iu mode. At the top is a 'Core Network' block. Below it, an 'SRNS' (Serving RNS) and a 'DBSS' (Drift BSS) are shown. The SRNS is connected to the Core Network via an 'Iu' interface. The DBSS is connected to the SRNS via an 'Iur-g' interface. Both the SRNS and the DBSS are connected to a 'Cell' (represented by a row of circles). The MS (Mobile Station) is connected to the Cell of the DBSS. + +Figure 5a: Serving RNS and Drift BSS, GERAN Iu mode. The diagram shows a Core Network at the top connected via an Iu interface to an SRNS (Serving RNS) and a DBSS (Drift BSS). The DBSS is connected to a Cell, which is in turn connected to an MS (Mobile Station). The SRNS is also connected to a Cell, which is connected to the MS. + +**Figure 5a: Serving RNS and Drift BSS, GERAN Iu mode** + +![Figure 5b: Serving BSS and Drift RNS, GERAN Iu mode. The diagram shows a Core Network at the top connected via an Iu interface to an SBSS (Serving BSS) and a DRNC (Drift RNS). The DRNC is connected to a Cell, which is in turn connected to a UE (User Equipment). The SBSS is also connected to a Cell, which is connected to the UE.](8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg) + +The diagram illustrates the network architecture for GERAN Iu mode. At the top is a 'Core Network' block. Below it, an 'SBSS' (Serving BSS) and a 'DRNC' (Drift RNS) are shown. The SBSS is connected to the Core Network via an 'Iu' interface. The DRNC is connected to the SBSS via an 'Iur-g' interface. Both the SBSS and the DRNC are connected to a 'Cell' (represented by a row of circles). The UE (User Equipment) is connected to the Cell of the DRNC. + +Figure 5b: Serving BSS and Drift RNS, GERAN Iu mode. The diagram shows a Core Network at the top connected via an Iu interface to an SBSS (Serving BSS) and a DRNC (Drift RNS). The DRNC is connected to a Cell, which is in turn connected to a UE (User Equipment). The SBSS is also connected to a Cell, which is connected to the UE. + +**Figure 5b: Serving BSS and Drift RNS, GERAN Iu mode** + +![Figure 5c: Serving RNS and Target BSS, GERAN A/Gb mode. The diagram shows a Core Network at the top connected via an Iu interface to an SRNS 1.28Mcps TDD (Serving RNS) and a TBSS (Target BSS). The TBSS is connected to a Cell, which is in turn connected to an MS (Mobile Station). The SRNS 1.28Mcps TDD is also connected to a Cell, which is connected to the MS.](51db757d054ce1ce83c436a3578b56ca_img.jpg) + +The diagram illustrates the network architecture for GERAN A/Gb mode. At the top is a 'Core Network' block. Below it, an 'SRNS 1.28Mcps TDD' (Serving RNS) and a 'TBSS' (Target BSS) are shown. The SRNS 1.28Mcps TDD is connected to the Core Network via an 'Iu' interface. The TBSS is connected to the SRNS 1.28Mcps TDD via an 'Iur-g' interface. Both the SRNS 1.28Mcps TDD and the TBSS are connected to a 'Cell' (represented by a row of circles). The MS (Mobile Station) is connected to the Cell of the TBSS. + +Figure 5c: Serving RNS and Target BSS, GERAN A/Gb mode. The diagram shows a Core Network at the top connected via an Iu interface to an SRNS 1.28Mcps TDD (Serving RNS) and a TBSS (Target BSS). The TBSS is connected to a Cell, which is in turn connected to an MS (Mobile Station). The SRNS 1.28Mcps TDD is also connected to a Cell, which is connected to the MS. + +**Figure 5c: Serving RNS and Target BSS, GERAN A/Gb mode** + +The UTRAN is layered into a Radio Network Layer and a Transport Network Layer. + +The UTRAN architecture, i.e. the UTRAN logical nodes and interfaces between them, are defined as part of the Radio Network Layer. + +For each UTRAN interface (Iu, Iur, Iub, Iupc) the related transport network layer protocol and functionality is specified. The transport network layer provides services for user plane transport, signalling transport and transport of implementation specific O&M. + +An implementation of equipment compliant with the specifications of a certain interface shall support the Radio Network Layer protocols specified for that interface. It shall also as a minimum, for interoperability, support the transport network layer protocols according to the transport network layer specifications for that interface. + +The network architecture of the transport network layer is not specified by 3GPP and is left as an operator issue. + +The equipment compliant to 3GPP standards shall at least be able to act as endpoints in the transport network layer, and may also act as a switch/router within the transport network layer. + +For implementation specific O&M signalling to the Node B, only the transport network layer protocols are in the scope of UTRAN specifications. + +![Figure 6: Protocol layering diagram showing the relationship between the Radio Network Layer and the Transport Layer. The Radio Network Layer contains Node B Management System, Node B, CRNC/DRNC/MRNC, SBSS, DBSS, SAS, and CN. The Transport Layer contains O&M Network (25.442), UP Transport (25.414, 25.424, 25.426, 25.434), Signalling Link (25.432), Signalling Network (25.412, 25.422, 25.4x2), and Iu PS UP Network (25.414). Connections are shown between various components across the layers.](a734898ce18e972938949637c32a34f4_img.jpg) + +The diagram illustrates the protocol layering between the Radio Network Layer (top) and the Transport Layer (bottom), separated by a dashed line. In the Radio Network Layer, from left to right, are the Node B Management System, Node B, CRNC/DRNC/MRNC, SBSS, DBSS, SAS, and CN. Connections include: Node B Management System to Node B (dotted); Node B to CRNC/DRNC/MRNC (Iub); CRNC/DRNC/MRNC to SBSS (Iur-g); CRNC/DRNC/MRNC to DBSS (Iur-g); CRNC/DRNC/MRNC to SAS (Iupc); CRNC/DRNC/MRNC to CN (Iu); and CN to CRNC/DRNC/MRNC (Iu). In the Transport Layer, from left to right, are the O&M Network (25.442), UP Transport (25.414, 25.424, 25.426, 25.434), Signalling Link (25.432), Signalling Network (25.412, 25.422, 25.4x2), and Iu PS UP Network (25.414). Connections include: Node B Management System to O&M Network; Node B to UP Transport; CRNC/DRNC/MRNC to UP Transport; SBSS to UP Transport; DBSS to UP Transport; SAS to Signalling Network; CN to Iu PS UP Network; and CRNC/DRNC/MRNC to Signalling Network. + +Figure 6: Protocol layering diagram showing the relationship between the Radio Network Layer and the Transport Layer. The Radio Network Layer contains Node B Management System, Node B, CRNC/DRNC/MRNC, SBSS, DBSS, SAS, and CN. The Transport Layer contains O&M Network (25.442), UP Transport (25.414, 25.424, 25.426, 25.434), Signalling Link (25.432), Signalling Network (25.412, 25.422, 25.4x2), and Iu PS UP Network (25.414). Connections are shown between various components across the layers. + +Figure 6: Protocol layering + +Figure 6 illustrates which parts of the transport network layer that may be (but are not mandated to be) configured by the operator as transport networks, i.e. the radio network layer provides a destination address, namely: + +- Transport network for implementation specific O&M traffic; +- Signalling network for Iu, Iur, Iur-g and Iupc; +- Transport network for Iub, Iur and Iu CS user plane connections; +- Transport network for Iu PS user plane connections. + +The signalling link for Iub signalling as seen by the radio network layer cannot be configured as a network (no address provided). + +A transport network for UTRAN may be configured by the operator to be used also for other traffic than UTRAN traffic. + +## 6.1 UTRAN Identifiers + +### 6.1.1 PLMN Identity + +A Public Land Mobile Network is uniquely identified as defined in TS 23.003 [6] subclause 12.1. + +### 6.1.2 CN Domain Identifier + +A CN Domain Edge Node is identified as defined in TS 23.003 [6] sub-clause 12.2. + +### 6.1.3 RNC Identifier + +An RNC node is uniquely identified by its RNC Identifier among the nodes in UTRAN and GERAN Iu mode as defined in TS 23.003 [6] sub-clause 12.3. A BSS node in GERAN Iu mode is uniquely identified by its RNC Identifier among the nodes in GERAN Iu mode and UTRAN. + +### 6.1.4 Service Area Identifier + +The Service Area Identifier (SAI) is defined in TS 23.003 [6] sub-clause 12.4. + +### 6.1.5 Cell Identifier + +The Cell identifier (C-Id) is used to uniquely identify a cell within an RNS/BSS. The Cell-Id together with the identifier of the controlling RNC/BSS (CRNC-Id) constitutes the UTRAN/GERAN Cell Identity (UC-Id) and is used to identify the cell uniquely within UTRAN/GERAN Iu mode. UC-Id or C-Id is used to identify a cell in UTRAN Iub and Iur interfaces or Iur-g interface. + +- **UC-Id = RNC-Id + C-Id.** + +The C-Id is defined by the operator, and set in the RNC/BSS via O&M. The C-Id is set in a Node B by its C-RNC or in the GERAN Iu mode cell. + +### 6.1.6 Local Cell Identifier + +The Local Cell identifier is used to uniquely identify the set of resources within a Node B required to support a cell (as identified by a C-Id). As a minimum it shall be unique within the Node B, but it is also capable of supporting uniqueness within the UTRAN for management system purposes. + +The Local Cell Identifier is used for the initial configuration of a Node B when no C-Id is defined. The Local Cell identifier is defined by the operator, and set in both the Node B and its C-RNC via O&M. The relationship between the Local Cell Identifier and C-Id is set in the C-RNC via O&M. + +### 6.1.7 UE Identifiers + +Radio Network Temporary Identities (RNTI) are used as UE identifiers within UTRAN/GERAN Iu mode and in signalling messages between UE and UTRAN/GERAN Iu mode. + +Six types of RNTI exist: + +- 1) Serving RNC/BSS RNTI (s-RNTI); +- 2) Drift RNC/BSS RNTI (d-RNTI); +- 3) Cell RNTI (c-RNTI); +- 4) UTRAN/GERAN RNTI (u-RNTI); +- 5) [TDD – DSCH RNTI (DSCH-RNTI)]; +- 6) HS-DSCH RNTI (HS-DSCH RNTI); +- 7) E-DCH RNTI (E-RNTI); + +#### **s-RNTI is used:** + +- by UE to identify itself to the Serving RNC/BSS; +- by SRNC/SBSS to address the UE/MS; +- by DRNC/DBSS to identify the UE to Serving RNC. + +s-RNTI is allocated for all UEs having a RRC connection, it is allocated by the Serving RNC/BSS and it is unique within the Serving RNC/BSS. s-RNTI is reallocated always when the Serving RNC/BSS for the RRC connection is changed. + +#### **d-RNTI is used:** + +- by serving RNC/BSS to identify the UE to Drift RNC/BSS. + +NOTE: The d-RNTI is never used on Uu. + +d-RNTI is allocated by drift RNC/BSS upon drift UE contexts establishment and it shall be unique within the drift RNC/BSS. Serving RNC/BSS shall know the mapping between s-RNTI and the d-RNTIs allocated in Drift RNCs/BSSs for the same UE. Drift RNC/BSS shall know the s-RNTI and SRNC-ID related to existing d-RNTI within the drift RNC/BSS. + +#### **c-RNTI is used:** + +- by UE to identify itself to the controlling RNC; +- by controlling RNC to address the UE. + +c-RNTI is allocated by controlling RNC upon UE accessing a new cell. C-RNTI shall be unique within the accessed cell. Controlling RNC shall know the d-RNTI associated to the c-RNTI within the same logical RNC (if any). + +When c-RNTI is allocated to an UE in URA\_PCH state, if it is a cell specific c-RNTI, it shall be unique within the accessed cell; if it is an URA wide c-RNTI, it shall be unique within an URA. + +#### **u-RNTI** + +The u-RNTI is allocated to an UE having a RRC connection and identifies the UE within UTRAN/GERAN Iu mode. + +u-RNTI is composed of: + +- SRNC identity; +- s-RNTI. + +#### **[TDD – DSCH-RNTI is used:]** + +- [TDD – by controlling RNC to address the UE on the DSCH and USCH]. + +[TDD – DSCH-RNTI is allocated by controlling RNC upon UE establishing a DSCH or USCH channel. DSCH-RNTI shall be unique within the cell carrying the DSCH and/or USCH. DSCH-RNTI is used as UE identifier in RRC messages concerning DSCH and USCH allocations and is used in both the downlink and uplink. + +#### **HS-DSCH RNTI is used:** + +- for the UE specific CRC in HS-SCCH and HS-PDSCH. + +HS-DSCH RNTI is allocated by controlling RNC upon UE establishing a HS-DSCH channel. HS-DSCH RNTI shall be unique within the cell carrying the HS-DSCH. + +When HS-DSCH RNTI is allocated to an UE in URA\_PCH state, if it is a cell specific HS-DSCH RNTI, it shall be unique within the accessed cell; if it is an URA wide HS-DSCH RNTI, it shall be unique within an URA. + +#### **E-RNTI is used:** + +- for the UE[FDD - /UE group] specific CRC in E-AGCH. + +E-DCH RNTI is allocated by NodeB upon UE establishing an E-DCH channel. E-DCH RNTI allocated to a UE [FDD - /UE group] shall be unique within the cell carrying the E-DCH. + +When E-RNTI is allocated to an UE in URA\_PCH state, if it is a cell specific E-RNTI, it shall be unique within the accessed cell; if it is an URA wide E-RNTI, it shall be unique within an URA. + +Each RNC has a unique identifier within the UTRAN part of the PLMN, denoted by RNC identifier (RNC-ID). This identifier is used to route UTRAN interface messages to correct RNC. RNC-ID of the serving RNC together with the s-RNTI is a unique identifier of the UE in the UTRAN part of the PLMN. + +#### 6.1.7.1 Usage of RNTI + +u-RNTI is used as a UE identifier for the first cell access (at cell change) when a RRC connection exists for this UE and for UTRAN originated paging including associated response messages. RNC-ID is used by Controlling RNC/BSS to route the received uplink messages towards the Serving RNC/BSS. + +NOTE: For the initial access a unique core network UE identifier is used. + +c-RNTI is used as a UE identifier in all other DCCH/DTCH common channel messages on air interface. + +### 6.1.7a UE Identifiers in GERAN A/Gb mode (1.28Mcps TDD) + +Radio Network Temporary Identity (RNTI) is used as a UE identifier within UTRAN /GERAN A/Gb mode and in signalling messages between UE and UTRAN /GERAN A/Gb mode. One type of RNTI exists: + +- Drift RNTI (D-RNTI) + +The D-RNTI is allocated by the TBSS and is used to identify the UE during a handover via the Iur-g interface. + +There is one possible scenario in which the D-RNTI is used: + +- The serving RAN node is a UTRAN RNC and the target RAN node is a GERAN BSS in A/Gb mode. + +### 6.1.8 Identifiers for dedicated resources within UTRAN + +#### 6.1.8.1 Radio Network Control Plane identifiers + +Each addressable object in each reference point has an application part level identifier. This identifier is allocated autonomously by the entity responsible for initiation of the setup of the object. This application part identifier will be used as a reference to the object that is setup. Both ends of the reference point shall memorise the AP Identifier during the lifetime of the object. Application part identifier can be related to a specific Transport Network identifier and that relationship shall also be memorised by both ends. + +Table 1 lists the basic AP level identifiers in each reference point. + +**Table 1: Basic AP level identifiers in each reference point** + +| Object | Identifier | Abbreviation | Valid for | +|---------------------------------|------------------------|--------------|-----------| +| Radio Access Bearer | Radio Access Bearer ID | RAB-ID | Iu | +| Dedicated Transport channel | DCH-ID | DCH-ID | Iur, Iub | +| [TDD – Downlink Shared Channel] | DSCH-ID | DSCH-ID | Iur, Iub | +| [TDD – Uplink Shared Channel] | USCH-ID | USCH-ID | Iur, Iub | + +#### 6.1.8.2 Transport Network Identifiers + +Transport Network identifiers are used in the Transport Network Layer (TNL) to identify the transport bearer and may be used in User Plane in the actual data transmission using the transport link. The Transport Network identifier identifies the transport link according to the naming conventions defined for the transport link type in question. Both ends of the reference point of the concerned TNL shall memorise the Transport Network identifiers during the lifetime of the transport link. Each Transport Network identifier can be bound to an Application Part identifier. + +The Transport Network identifiers vary depending on the transport link type. + +Table 2 indicates examples of the identifiers used for different transmission link types. + +**Table 2: Examples of the identifiers used for different transmission link types** + +| Transmission link type | Transport Network Identifier | +|------------------------|------------------------------| +| AAL2 | AAL2 Path ID + CID | +| GTP over IP | IP address + TEID | +| UDP over IP | IP address + UDP port | + +The communication of Transport Network identifiers is made in two ways: + +When an ALCAP is used, the transport layer address communicated via the Radio Network Layers protocols (NBAP, RNSAP, RANAP...) is a Transport Network Control Plane address and the Transport Network identifiers are communicated through this Transport Network Control Plane only. + +When no ALCAP is used, the Transport Network identifiers are directly communicated via the Radio Network Layers protocols (NBAP, RNSAP, RANAP...) on all interfaces. + +In both cases, the transport layer address (e.g. IP address) is encapsulated by the Transport Network Layer in the NSAP structure as defined in [Annex A of X.213, ISO/IEC 8348 [15], X.213/Amd. 1, ISO/IEC 8348 [16]] transported transparently on Iub, Iur and Iu-CS and passed transparently from the Radio Network Layer to the Transport Network Layer. The NSAP structure (encapsulation) is only used in order to provide to the TNL explicit identification of the type of the TNL address that is being conveyed by the given RNL protocol. It is then the responsibility of the Transport Network Layer to interpret this structure (e.g. to determine accordingly if the requested network type is ATM or IP). + +On the Iu-PS, the NSAP structure is not used in RANAP but the 'straight IP addressing' shall be used. + +The following scheme depicts the encapsulation of a native IPv6 (IETF RFC 2460 [12]) address in NSAP structure when conveyed in RANAP, RNSAP and NBAP. + +![](86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg) + +| Octet 1 | octet 2 | octet 3 | octet 4 | +|--------------------|-----------------------|---------|-----------------| +| AFI=35 (IANA) | ICP=0 (embedded IPv6) | | IPv6 (byte 1) | +| IPv6 (bytes 2-5) | | | | +| IPv6 (bytes 6-9) | | | | +| IPv6 (bytes 10-13) | | | | +| IPv6 (bytes 14-16) | | | 0 0 0 0 0 0 0 0 | + +**Figure 6A: IPv6 address embedded in NSAP structure in RANAP/RNSAP/NBAP.** + +Note 1: The last octet of the DSP (the DSP is the remaining octets after the IDP IETF RFC 4548 [34]) the encapsulation of a native IPv6 address in NSAP structure is unspecified. + +Note 2: The encapsulation of a native IPv4 address in NSAP structure when conveyed in RANAP, RNSAP and NBAP shall be encoded according to IETF RFC 4548 [34]. The last 13 octets of the DSP are unspecified. + +Note 3: The default values for the unspecified octets are zero. + +#### 6.1.8.3 Binding identifier + +Binding Identifier (Binding ID) is used to initialise the linkage between ALCAP and Application Part (RANAP, RNSAP, NBAP) identifiers. Binding identifier can be used both in Radio Network Control plane Application Part protocols and in Transport Network Control Plane's ALCAP protocol. When no ALCAP is used, Binding ID may also be used to carry the UDP port on Iub, Iur and Iu-CS interfaces. + +Binding ID binds the Radio and Transport Network Control plane identifiers together. To ensure maximal independence of those two planes, the binding ID should be used only when necessary: Binding ID shall thus be used only in Radio Network Control plane Application Part messages in which a new association between the planes is created and in ALCAP messages creating new transport bearers. + +Binding ID for each transport bearer shall be allocated before the setup of that transport bearer. + +The Binding ID is sent on one direction using the Application Part protocol and is return in the other direction by the ALCAP protocol. + +When an Application Part procedure with an allocated Binding ID is applied for modifying an existing Radio Network User Plane connection, the decision to use the Binding ID (and the ALCAP procedures) shall be done by that end of the reference point that decides whether to use the existing transport bearer or to set up a new transport bearer. + +The Binding ID shall already be assigned and tied to a radio application procedure when the first ALCAP message is received in a node. + +The association between the connection Id in the Application Part protocol (e.g. identifying a RAB) and the corresponding connection Id in the ALCAP protocol (e.g. identifying the AAL2 channel for that RAB) that was created with the help of Binding ID shall be memorised by both peers of each reference point for the lifetime of the corresponding transport bearer. + +The Binding ID may be released and re-used as soon as both the Application Part procedure and the ALCAP procedure that used it are completed in both peers of the reference point. + +Figure 6a illustrates how application instances of the Radio Network Control Plane and instances of the Transport Network Plane are linked together through the Binding Identifier in the set-up phase. + +![Figure 6a: Usage of Binding ID. A sequence diagram showing three steps between two nodes, AP-1 and AP-2. Step 1: AP-1 sends a 'Radio Network Control Plane Setup (Response)' message to AP-2, containing '[Node 1 Transport Address, Binding ID]'. Step 2: AP-2 receives the message and sends a request to its ALCAP-2 instance, containing 'Node 1 Transport Address, Binding ID'. Step 3: ALCAP-2 sends an 'ALCAP Establish Request' message to ALCAP-1, containing '[Node 1 Transport Address, Binding ID]'. Dashed arrows indicate the flow of the Binding ID from AP-1 to AP-2 and then from AP-2 to ALCAP-2.](9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg) + +Figure 6a: Usage of Binding ID. A sequence diagram showing three steps between two nodes, AP-1 and AP-2. Step 1: AP-1 sends a 'Radio Network Control Plane Setup (Response)' message to AP-2, containing '[Node 1 Transport Address, Binding ID]'. Step 2: AP-2 receives the message and sends a request to its ALCAP-2 instance, containing 'Node 1 Transport Address, Binding ID'. Step 3: ALCAP-2 sends an 'ALCAP Establish Request' message to ALCAP-1, containing '[Node 1 Transport Address, Binding ID]'. Dashed arrows indicate the flow of the Binding ID from AP-1 to AP-2 and then from AP-2 to ALCAP-2. + +- Step 1: Application Part AP-1 assigns the Binding Identifier and sends a Radio Network Control Plane Set-up (Response) message (which of the two messages depends on the involved interface - lu/lur or lub). The message contains the originating node Transport layer address and the Binding Identifier. +- Step 2: Among reception of the Radio Network Control Plane Set-up message, the peer entity AP-2 requests ALCAP-2 to establish a transport bearer. The Binding Identifier is passed to ALCAP-2. +- Step 3: ALCAP-2 sends an ALCAP Establish Request to the peer entity ALCAP-1. The message contains the Binding Identifier. The Binding Identifier allows correlating the incoming transport connection with the Application Part transaction in step 1. + +**Figure 6a: Usage of Binding ID** + +Table 3 indicates the binding identifier allocating entity in each interface. + +**Table 3: Binding identifier allocating entity in each interface** + +| Reference point | Allocating entity | Application part message including Binding-ID | +|-----------------|-------------------|-----------------------------------------------| +| Iu | CN | Request from CN | +| Iur | DRNC | Response to the request from SRNC | +| Iub | Node-B | Response to the request from DRNC | + +### 6.1.9 URA Identity + +The URA identity is used to uniquely identify an URA, which is a specified set of UTRAN and/or GERAN cells. The URA identity can be used to indicate to the UE and the SRNC which URA it shall use in case there are multiple URA identities broadcast in the cell where the UE is located. + +### 6.1.10 Service Identifiers for MBMS + +#### 6.1.10.1 IP Multicast Address and APN + +The IP Multicast Address and an APN are used to enable the routing of MBMS registration requests within the CN. These identifiers are transparent to RAN. + +#### 6.1.10.2 TMGI + +The Temporary Mobile Group Identity (TMGI) is used for group notification purposes and is unique within HPLMN. TMGI is used at the start of a session and at UE linking to identify an MBMS Bearer Service. + +The structure of TMGI is specified in TS 23.003 [6]. + +#### 6.1.10.3 Session Identifier + +MBMS session Identifier is used to identify one specific session of a MBMS service and is forwarded transparently to the UE. + +#### 6.1.10.4 MBMS Service Area + +The MBMS Service Area is defined in TS 25.413 [31]. + +The mapping between a MBMS Service Area and a list of cells is set in the RNC via O&M. + +#### 6.1.10.5 MBMS Cell Group Identifier + +The MBMS Cell Group Identifier is defined in TS 25.346 [30] + +#### 6.1.10.6 MBMS UTRAN Cell Group Identifier + +Void. + +### 6.1.11 Transport Network Identifiers for MBMS + +Transport Network identifiers are used in the Transport Network Layer (TNL) to identify the MBMS transport bearers and may be used in User Plane in the actual MBMS data transmission using the transport link. Each MBMS Transport Network identifier can be binded to an Application Part identifier. The Application Part identifier over the Iu interface is the TMGI corresponding to one MBMS Bearer Service. + +The handling of the MBMS Transport Network identifiers is the same as the handling of Transport Network identifiers for dedicated resources described in section 6.1.8.2. + +### 6.1.12 Binding Identifiers for MBMS + +Binding identifiers can be used for MBMS both in Radio Network Control plane Application Part protocols and in Transport Network Control Plane's ALCAP protocol. When ALCAP is used, Binding Identifiers (Binding ID) are used to initialise the linkage between ALCAP and the MBMS Application Part (RNSAP, NBAP) identifiers. When no ALCAP is used, the Binding ID may also be used to carry the UDP port on Iub and Iur interfaces. + +The handling of the MBMS Binding identifiers is the same as the handling of Binding identifiers for dedicated resources described in section 6.1.8.3. + +### 6.1.13 Use of Extended Identifiers + +The use and deployment of extended RNC-ID and extended S-RNTI in deployments is described in Annex A2. + +## 6.2 Transport Addresses + +The transport layer address parameter is transported in the radio network application signalling procedures that result in establishment of transport bearer connections. + +The transport layer address parameter shall not be interpreted in the radio network application protocols and reveal the addressing format used in the transport layer. + +The formats of the transport layer addresses are further elaborated in TS 25.414 [9], TS 25.424 [10], TS 25.434 [11], TS 25.426 [18]. + +## 6.3 Function Distribution Principles + +For radio resource management functionality, the following principles apply: + +- The CRNC owns the radio resources of a cell. +- The SRNC handles the connection to one UE, and may borrow radio resources of a certain cell from the CRNC. +- When used, the MRNC controls the logical resources of the RNSs that are used for MBSFN operation within the MBSFN cluster(s). + +Dynamical control of power for dedicated channels, within limits admitted by CRNC, is done by the SRNC. + +- Dynamic control on smaller time-scale for some radio links of the UE connection may be done by the Node B. This “inner loop” control is controlled by an “outer loop”, for which the SRNC has overall responsibility. +- Scheduling of data for dedicated channels is done by the SRNC, while for common channels it is done by the CRNC. + +For management of node-internal resources, the following principle apply: + +- Each UTRAN node is considered a network element on its own. The knowledge about the equipment of a network element is kept within the network element itself and its management system. The node itself always manages node-internal resources. + +For transport network resource management, the following principle apply: + +- Management of transport network resources belong to the Transport Layer. Mechanisms relevant for the selected transport technology are used. No functional split between UTRAN nodes is specified what regards the Transport Layer. + +As a general guideline, the UTRAN protocols should be designed in such a way that they minimise the need for a DRNC to interpret the user plane frame protocol information other than for the combining/splitting purpose. + +# --- 7 UTRAN Functions description + +## 7.1 List of functions + +- Transfer of User Data. +- Functions related to overall system access control: + - Admission Control; + - Congestion Control; + +- System information broadcasting. +- Radio channel ciphering and deciphering. +- Integrity protection. +- Functions related to mobility: + - Handover; + - SRNS Relocation; + - Paging support; + - Positioning; + - GERAN System Information Retrieval; + - Enhanced SRNS Relocation. +- Functions related to radio resource management and control: + - Radio resource configuration and operation; + - Radio environment survey; + - Combining/splitting control; + - Connection set-up and release; + - Allocation and deallocation of Radio Bearers; + - [TDD - Dynamic Channel Allocation (DCA)]; + - Radio protocols function; + - RF power control; + - [3.84 Mcps TDD and 7.68Mcps TDD - Timing Advance]; + - [1.28 Mcps TDD – Uplink Synchronisation]; + - Radio channel coding; + - Radio channel decoding; + - Channel coding control; + - Initial (random) access detection and handling; + - CN Distribution function for Non Access Stratum messages. +- Synchronisation. +- Functions related to broadcast and multicast services (see note) (broadcast/multicast interworking function BM-IWF). + +NOTE: Only Broadcast is applicable for Release 99. + +- Broadcast/Multicast Information Distribution. +- Broadcast/Multicast Flow Control. +- CBS Status Reporting. +- Tracing. +- MDT. + +- Volume reporting. +- NAS Node Selection. +- RAN Information Management. +- MBMS provision. +- MBMS Notification. +- MOCN and GWCN configuration support. +- SIPTO at Iu-PS (optional). +- Explicit Congestion Notification. +- Traffic Volume for RAN Sharing. +- QoE. + +## 7.2 Functions description + +### 7.2.0 Transfer of user data + +This function provides user data transfer capability across the UTRAN between the Iu and Uu reference points. + +### 7.2.1 Functions related to overall system access control + +System access is the means by which a UMTS user is connected to the UTRAN in order to use UMTS services and/or facilities. User system access may be initiated from either the mobile side, e.g. a mobile originated call, or the network side, e.g. a mobile terminated call. + +#### 7.2.1.1 Admission Control + +The purpose of the admission control is to admit or deny new users, new radio access bearers or new radio links (for example due to handover). The admission control should try to avoid overload situations and base its decisions on interference and resource measurements. The admission control is employed at for example initial UE access, RAB assignment/reconfiguration and at handover. These cases may give different answers depending on priority and situation. + +The Admission Control function based on UL interference and DL power is located in the Controlling RNC. + +The Serving RNC is performing admission Control towards the Iu interface. + +#### 7.2.1.2 Congestion Control + +The task of congestion control is to monitor, detect and handle situations when the system is reaching a near overload or an overload situation with the already connected users. This means that some part of the network has run out, or will soon run out of resources. The congestion control should then bring the system back to a stable state as seamless as possible. + +NOTE: This admission Control function is related to Radio Resources. + +Congestion control is performed within UTRAN. + +The RNC may trigger EAB as specified in TS 23.060 [36] subclause 5.3.6.4 and TS 23.251[28] subclause 4.6. + +#### 7.2.1.3 System information broadcasting + +This function provides the mobile station with the Access Stratum and Non Access Stratum information which are needed by the UE for its operation within the network. + +The basic control and synchronisation of this function is located in UTRAN. + +#### 7.2.1.4 MOCN and GWCN configuration support + +In the MOCN configuration only the radio access part of the network is shared. For the MOCN configuration it is required that the rerouting function, as described in TS 25.410 [29], is supported. + +In the GWCN configuration, besides shared radio access network, the core network operators also share part of the core network, at least MSC and/or SGSN. + +For both the GWCN and MOCN configurations, the RNC carries the selected PLMN-id between network sharing supporting UEs and the corresponding CN. + +The network sharing MOCN and GWCN configurations are described in detail in TS 23.251 [28]. + +### 7.2.2 Radio channel ciphering and deciphering + +This function is a pure computation function whereby the radio transmitted data can be protected against a non-authorised third-party. Ciphering and deciphering may be based on the usage of a session-dependent key, derived through signalling and/or session dependent information. + +This function is located in the UE and in the UTRAN. + +### 7.2.3 Functions related to Mobility + +#### 7.2.3.1 Handover + +This function manages the mobility of the radio interface. It is based on radio measurements and it is used to maintain the Quality of Service requested by the Core Network. + +Handover may be directed to/from another system (e.g. UMTS to GSM handover). + +The handover function may be either controlled by the network, or independently by the UE. Therefore, this function may be located in the SRNC, the UE, or both. + +#### 7.2.3.2 SRNS Relocation + +The SRNS Relocation function coordinates the activities when the SRNS role is to be taken over by another RNS/BSS. The SRNS relocation function manages the Iu interface connection mobility from an RNS to another RNS/BSS. + +![Diagram illustrating SRNS Relocation. The diagram is split into two parts: 'Before SRNS Relocation' and 'After SRNS Relocation'. In both parts, a 'Core Network' box is at the top, connected via an 'Iu' interface to an 'SRNS' box. Below the SRNS box are three circles representing 'Cells'. A 'UE' box is at the bottom, connected to the cells by a zigzag line. In the 'Before' part, the SRNS is connected to a 'DRNS' box via an 'Iur' interface. In the 'After' part, the SRNS is connected to an 'RNS' box via an 'Iur' interface. The DRNS and RNS boxes also have three circles representing 'Cells' below them.](4ac41fc8bdb77c3dce8adfe7b954860e_img.jpg) + +Diagram illustrating SRNS Relocation. The diagram is split into two parts: 'Before SRNS Relocation' and 'After SRNS Relocation'. In both parts, a 'Core Network' box is at the top, connected via an 'Iu' interface to an 'SRNS' box. Below the SRNS box are three circles representing 'Cells'. A 'UE' box is at the bottom, connected to the cells by a zigzag line. In the 'Before' part, the SRNS is connected to a 'DRNS' box via an 'Iur' interface. In the 'After' part, the SRNS is connected to an 'RNS' box via an 'Iur' interface. The DRNS and RNS boxes also have three circles representing 'Cells' below them. + +**Figure 7: Serving RNS Relocation** + +The SRNS Relocation is initiated by the SRNC. + +This function is located in the RNC and the CN. + +#### 7.2.3.3 Paging support + +This function provides the capability to request a UE to contact the UTRAN/GERAN Iu mode when the UE is in Idle, CELL\_PCH or URA\_PCH/GRA\_PCH states (TS 25.331 [7], TR 43.930 [21]). This function also encompasses a coordination function between the different Core Network Domains onto a single RRC connection. + +#### 7.2.3.4 Positioning + +This function provides the capability to determine the geographic position and optionally the velocity of a UE. + +#### 7.2.3.5 NAS Node Selection Function + +The optional NAS Node Selection Function (NNSF) enables the RNC to initially assign CN resources to serve a UE and subsequently setup a signalling connection to the assigned CN resource. + +The NNSF is described in detail in TS 23.236 [20]. + +The Reroute NAS Request procedure enables a SGSN to trigger the RNC to setup a signalling connection to another SGSN node within a given DCN as described in TS 23.060 [36]. + +RNC selects serving SGSN based on the DCN-ID provided by the UE and the configuration in RNC if a serving SGSN corresponding to the information provided by the UE (e.g. NRI, etc.) cannot be found by the RNC. + +#### 7.2.3.6 Shared Networks Access Control + +The Shared Networks Access Control function allows the CN to request the UTRAN to apply UE specific access control to LAs of the UTRAN and LAs of neighbouring networks. + +The Shared Networks Access Control function is based on either whole PLMNs or Shared Network Areas (SNAs). An SNA is an area corresponding to one or more LAs within a single PLMN to which UE access can be controlled. + +In order to apply Shared Networks Access Control for the UTRAN or for a neighbouring system, the UTRAN shall be aware of whether the concerned LA belongs to one (or several) SNA(s) or not. + +If access for a specific UE needs to be restricted, the CN shall provide SNA Access Information for that UE. The SNA Access Information indicates which PLMNs and/or which SNAs the UE is allowed to access. + +Based on whether the LA belongs to the PLMNs or SNAs the UE is allowed to access, the UTRAN determines if access to a certain LA for a certain UE shall be allowed. + +If access is not allowed, the UTRAN shall request the CN to release existing resources either by initiating Iu Release Request procedure with cause value “Access Restricted due to Shared Network” or by requesting a relocation with the same cause value. + +#### 7.2.3.7 GERAN System Information Retrieval + +In order to provide the UE with system information related to NACC towards a GERAN system - to be used as an optimisation - the GERAN System Information Retrieval function allows: + +- The source RAN to request GERAN (via CN) to provide this system information. +- The SRNC to request the DRNC (via Iur interface) to provide this system information, if available. + +The request and subsequent transfer of the GERAN System Information is performed transparently with the RIM function. The RIM function is further described in section 7.2.8. + +#### 7.2.3.8 Enhanced SRNS Relocation + +The Enhanced SRNS Relocation function coordinates the activities when the SRNS role is to be taken over by another RNS. The Enhanced SRNS Relocation function manages the Iu interface connection mobility from an RNS to another RNS. + +The Enhanced SRNS Relocation is initiated by the SRNC. The relocation of the SRNS functionality is prepared via RNSAP means. The CN is not informed until the preparation and execution of the relocation has taken place. + +This function is located in the RNC and the CN. + +#### 7.2.3.9 Subscriber Profile ID for RAT/Frequency Priority + +The RRM strategy in UTRAN may be based on user specific information. + +The Subscriber Profile ID for RAT/Frequency Priority (SPID) parameter received by the RNC via the Iu interface is an index referring to user information (e.g. mobility profile, service usage profile). The information is UE specific and applies to all its Radio Bearers. + +This index is mapped by the RNC to locally defined configuration in order to apply specific RRM strategies (e.g. to define RRC\_IDLE mode priorities and control inter-RAT/inter frequency handover in RRC\_CONNECTED mode). + +### 7.2.4 Functions related to radio resource management and control + +*Radio resource management* is concerned with the allocation and maintenance of radio communication resources. UMTS radio resources must be shared between circuit transfer mode services and packet transfer modes services (i.e. Connection-oriented and/or connectionless-oriented services). + +#### 7.2.4.1 Radio resource configuration and operation + +This function performs configures the radio network resources, i.e. cells and common transport channels, and takes the resources into or out of operation. + +#### 7.2.4.2 Radio environment survey + +This function performs measurements on radio channels (current and surrounding cells) and translates these measurements into radio channel quality estimates. Measurements may include: + +- 1) Received signal strengths (current and surrounding cells); +- 2) Estimated bit error ratios, (current and surrounding cells); +- 3) Estimation of propagation environments (e.g. high-speed, low-speed, satellite, etc.); +- 4) Transmission range (e.g. through timing information); +- 5) Doppler shift; +- 6) Synchronisation status; +- 7) Received interference level; +- 8) Total DL transmission power per cell. + +This function is located in the UE and in the UTRAN. + +#### 7.2.4.3 Combining/splitting control + +This function controls the combining/splitting of information streams to receive/ transmit the same information through multiple physical channels (possibly in different cells) from/ towards a single mobile terminal. + +The UL combining of information streams may be performed using any suitable algorithm, for example: + +- [FDD - based on maximum ratio algorithm (maximum ratio combining)]; +- [FDD - based on quality information associated to each TBS (selection-combining)]; +- [TDD - based on the presence/absence of the signal (selection)]. + +[FDD - combining/splitting control should interact with channel coding control in order to reduce the bit error ratio when combining the different information streams]. + +In some cases, depending on physical network configuration, there may be several entities which combine the different information streams, i.e. there may be combining/splitting at the SRNC, DRNC or Node B level. + +This function is located in the UTRAN. + +#### 7.2.4.4 Connection set-up and release + +This function is responsible for the control of connection element set-up and release in the radio access sub network. The purpose of this function is: + +- 1) To participate in the processing of the end-to-end connection set-up and release; +- 2) And to manage and maintain the element of the end-to-end connection, which is located in the radio access sub network. + +In the former case, this function will be activated by request from other functional entities at call set-up/release. In the latter case, i.e. when the end-to-end connection has already been established, this function may also be invoked to cater for in-call service modification or at handover execution. + +This function is located both in the UE and in the RNC. + +#### 7.2.4.5 Allocation and deallocation of Radio Bearers + +This function consists of translating the connection element set-up (resp. release) requests into physical radio channel allocation (resp. deallocation) accordingly to the QoS of the Radio Access Bearer. + +This function may be activated during the call since e.g. the user service request may vary, or macro diversity may be used. + +This function is located in the CRNC and SRNC. + +#### 7.2.4.6 [TDD - Dynamic Channel Allocation (DCA)] + +DCA is used in the TDD mode. It includes Fast DCA and Slow DCA. Slow DCA is the process of assigning radio resources, including time slots, to different TDD cells according to the varying cell load. Fast DCA is the process of assigning resources to Radio Bearers, and is related to Admission Control. + +#### 7.2.4.7 Radio protocols function + +This function provides user data and signalling transfer capability across the UMTS radio interface by adapting the services (according to the QoS of the Radio Access Bearer) to the Radio transmission. This function includes amongst other: + +- Multiplexing of services and multiplexing of UEs on Radio bearers; +- Segmentation and reassembly; +- Acknowledged/Unacknowledged delivery according to the Radio Access Bearer QoS. + +#### 7.2.4.8 RF power control + +This group of functions controls the level of the transmitted power in order to minimise interference and keep the quality of the connections. It consist of the following functions: UL Outer Loop Power Control, DL Outer Loop Power Control, UL Inner Loop Power Control, DL Inner Loop Power Control, UL Open Loop Power Control and DL Open Loop Power Control. + +##### 7.2.4.8.1 UL Outer Loop Power Control + +The UL Outer Loop Power Control located in the SRNC [TDD – except for uplink shared channels where it is located in the CRNC] sets the target quality value for the UL Inner Loop Power Control which is located in Node B for FDD and 1.28 Mcps TDD and is located in the UE for 3.84 Mcps and 7.68 Mcps TDD. It receives input from quality estimates of the transport channel. The UL outer loop power control is mainly used for a long-term quality control of the radio channel. + +In FDD and 1.28 Mcps TDD this function is located in the UTRAN, in 3.84 Mcps and 7.68 Mcps TDD the function is performed in UTRAN and the target quality value is sent to the UE by the SRNC or the CRNC, respectively. + +In FDD and 1.28 Mcps TDD, if the connection involves both a SRNS and a DRNS the function UL Outer Loop Power Control (located in the SRNC [1.28 Mcps TDD – or in the CRNC, respectively]) sets the target quality for the UL Inner Loop Power Control function (located in Node B). + +##### 7.2.4.8.2 DL Outer Loop Power Control + +The DL Outer Loop Power Control sets the target quality value for the DL inner loop power control. It receives input from quality estimates of the transport channel, measured in the UE. The DL outer loop power control is mainly used for a long-term quality control of the radio channel. + +This function is located mainly in the UE, but some control parameters are set by the UTRAN. + +The SRNC, regularly (or under some algorithms), sends the target down link power range based on the measurement report from UE. + +##### 7.2.4.8.3 UL Inner Loop Power Control + +The UL Inner Loop Power Control sets the power of the uplink dedicated [TDD – and shared] physical channels. + +In FDD, it is a closed loop process. It receives the quality target from UL Outer Loop Power Control and quality estimates of the uplink dedicated physical control channel. The power control commands are sent on the downlink dedicated physical control channel to the UE. This function is located in both the UTRAN and the UE. + +In 3.84 Mcps and 7.68 Mcps TDD it is a open loop process, it receives the quality target from the UL Outer Loop Power Control and uses the quality target and quality estimates of downlink channels to set the transmit power. This function is located in the UE. + +In 1.28 Mcps TDD, it is a closed loop process. It receives the quality target from UL Outer Loop Power Control, and quality estimates of the uplink dedicated physical channels as well as physical uplink shared channels, if any. The power control commands are sent on the downlink dedicated physical channels and physical downlink shared channels, if any, to the UE. This function is located in both the UTRAN and the UE. + +##### 7.2.4.8.4 DL Inner Loop Power Control + +The DL Inner Loop Power Control sets the power of the downlink dedicated [TDD – and shared] physical channels. It receives the quality target from DL Outer Loop Power Control and quality estimates of the [FDD - downlink dedicated physical control channel] [TDD – downlink dedicated physical channels and physical downlink shared channels if any]. The power control commands are sent on the [FDD - uplink dedicated physical control channel] [TDD – downlink dedicated physical channels and physical downlink shared channels if any] to the UTRAN. + +This function is located in both the UTRAN and the UE. + +##### 7.2.4.8.5 UL Open Loop Power Control + +The UL Open Loop Power Control sets the initial power of the UE, i.e. at random access. The function uses UE measurements and broadcasted cell/system parameters as input. + +This function is located in both the UTRAN and the UE. + +##### 7.2.4.8.6 DL Open Loop Power Control + +The DL Open Loop Power Control sets the initial power of downlink channels. It receives downlink measurement reports from the UE. + +This function is located in both the UTRAN and the UE. + +#### 7.2.4.9 Radio channel coding + +This function introduces redundancy into the source data flow, increasing its rate by adding information calculated from the source data, in order to allow the detection or correction of signal errors introduced by the transmission medium. The channel coding algorithm(s) used and the amount of redundancy introduced may be different for the different types of logical channels and different types of data. + +This function is located in both the UE and in the UTRAN. + +#### 7.2.4.10 Radio channel decoding + +This function tries to reconstruct the source information using the redundancy added by the channel coding function to detect or correct possible errors in the received data flow. The channel decoding function may also employ a priori error + +likelihood information generated by the demodulation function to increase the efficiency of the decoding operation. The channel decoding function is the complement function to the channel coding function. + +This function is located in both the UE and in the UTRAN. + +#### 7.2.4.11 Channel coding control + +This function generates control information required by the channel coding/ decoding execution functions. This may include channel coding scheme, code rate, etc. + +This function is located in both the UE and in the UTRAN. + +#### 7.2.4.12 Initial (random) access detection and handling + +This function will have the ability to detect an initial access attempt from a mobile station and will respond appropriately. The handling of the initial access may include procedures for a possible resolution of colliding attempts, etc. The successful result will be the request for allocation of appropriate resources for the requesting mobile station. + +This function is located in the UTRAN. + +#### 7.2.4.13 CN Distribution function for Non Access Stratum messages + +In the RRC protocol, messages from the NAS shall be transparently transferred within the Access Stratum using the Direct Transfer procedure. A distribution function in the UE and the SRNC shall handle the CN domain indicator being part of the AS message to direct messages to the appropriate NAS entity i.e. the appropriate Mobility Management instance in the UE domain and the appropriate CN domain. + +In the downlink direction the UE shall be provided by the SRNC with the information on the originating CN domain for the individual NAS message. + +In the uplink direction, the process performed by the distribution function in the UE consists in inserting the appropriate values for the CN domain indicator in the AS message and the process performed by the SRNC consists in evaluating the CN domain indicator contained in the AS message and distribute the NAS message to the corresponding RANAP instance for transfer over Iu interface. + +This distribution function is located in both the UE and in the SRNC. + +#### 7.2.4.14 [3.84 Mcps and 7.68 Mcps TDD - Timing Advance] + +This function is used in uplink to align the uplink radio signals from the UE to the UTRAN. Timing Advance is based on uplink burst timing measurements performed by the Node B L1, and on Timing Advance commands sent downlink to the UE. + +#### 7.2.4.15 Service specific function for Non Access Stratum messages + +A service specific function in the UE provides a SAP for a particular service (e.g. a given priority). In the downlink direction, the SRNC may base the routing on this SAP. + +This service specific function is located in both the UE and the SRNC. + +#### 7.2.4.16 [1.28 Mcps TDD – Uplink Synchronisation] + +This function is used in uplink to synchronise the uplink radio signals from the UE to the UTRAN. At the detection of uplink burst, the Node B will evaluate the received power level and timing, and reply by sending the adjustment information to UE to modify its timing and power level for next transmission and for establishment of the Uplink synchronisation procedure. + +### 7.2.5 Functions related to broadcast and multicast services (broadcast/multicast interworking function BM-IWF) + +See note. + +#### 7.2.5.1 Broadcast/Multicast Information Distribution + +The broadcast/multicast information distribution function distributes received CBS messages towards the BMC entities configured per cell for further processing. The distribution of broadcast/multicast information relate on the mapping between service area and cells controlled by the RNC. The provision of this mapping information is an O&M function. + +NOTE: Only Broadcast is applicable for Release 99. + +#### 7.2.5.2 Broadcast/Multicast Flow Control + +When processing units of the RNC becomes congested, the Broadcast/Multicast Flow Control function informs the data source about this congestion situation and takes means to resolve the congestion. + +#### 7.2.5.3 CBS Status Reporting + +The RNC collects status data per cell (e.g. No-of-Broadcast-Completed-List, Radio-Resource-Loading-List), and matches these data to Service Areas. The status data is transmitted to the CBC, if a query has been made by the CBC. + +### 7.2.6 Tracing + +This function allows tracing of various events related to the UE and its activities. + +### 7.2.7 Volume Reporting + +The data volume reporting function is used to report the volume of unacknowledged data to the CN for accounting purpose. + +### 7.2.8 RAN Information Management + +The RAN Information Management (RIM) function is a generic mechanism that allows the request and transfer of information between two RAN nodes e.g. GERAN System information. The RIM mechanism allows to start, stop and resume both on demand and on event transfer of information. RIM also provides native error handling function at RIM level and at RIM application level. The RIM function is further described in TR 44.901 [22] and TS 48.018 [23]. + +### 7.2.9 Functions related to MBMS + +#### 7.2.9.1 MBMS provision + +The MBMS provision enables the RNC to provide a multicast service via an optimised transmission of the MBMS bearer service in UTRAN via techniques such as PTM transmission, selective combining, Soft Combining and transmission mode selection between PTM and PTP bearer. + +The MBMS provision enables the RNC to provide a broadcast service via a PTM transmission bearer. + +#### 7.2.9.2 MBMS Notification Coordination + +The characteristic of MBMS implies a need for MBMS notification co-ordination i.e. specific handling of MBMS Notification when UE is in Cell-DCH state. MBMS notification co-ordination is performed by UTRAN when the session is ongoing. The TMGI is used for coordination. + +The MBMS functions are further described in TS 25.346 [30]. + +### 7.2.10 SIPTO at Iu-PS + +If supported, SIPTO at Iu- PS Function provides the capability to offload certain PS RABs from the CN at RAB setup. The SIPTO at Iu-PS is implementation dependent and may be implemented in a separate entity outside of RNS, for further information see TS 23.060 [36]. + +### 7.2.11 Explicit Congestion Notification + +The RNC and the UE support of the Explicit Congestion Notification (ECN) is specified in Section 5 of IETF RFC 3168 [37] (i.e., the normative part of IETF RFC 3168 [37] that applies to the end-to-end flow of IP packets), and below. This enables the RNC to control the initial codec rate selection and/or to trigger a codec rate reduction. Thereby the + +RNC can increase capacity (e.g., in terms of number of accepted VoIP calls), and improve coverage (e.g. for high bit rate video sessions). + +The RNC should set the Congestion Experienced (CE) codepoint ('11') in PDCP SDUs in the downlink direction to indicate downlink (radio) congestion if those PDCP SDUs have one of the two ECN-Capable Transport (ECT) codepoints set. + +The RNC should set the Congestion Experienced (CE) codepoint ('11') in PDCP SDUs in the uplink direction to indicate uplink (radio) congestion if those PDCP SDUs have one of the two ECN-Capable Transport (ECT) codepoints set. + +### 7.2.12 MDT + +This function allows to activate and handle MDT sessions by trace procedure as described in TS37.320 [38]. + +### 7.2.13 SIPTO at the Local Network with Standalone GW + +SIPTO@LN provides access to a defined IP network (e.g. the Internet) without the user plane traversing the mobile operator's core network by using standalone GW (with S-GW and L-GW collocated) function in the local network, as specified in TS 23.060 [36]. + +### 7.2.14 Traffic Volume for RAN Sharing + +The traffic volume for RAN sharing function is used to report the traffic volume of the CS and the PS traffic per CN operator in the shared network. The traffic volume is collected at UTRAN and reported to O&M. + +For the PS traffic, the DL data volume is defined as the amount of PDCP SDU bits in the downlink delivered from PDCP layer to RLC layer per participating core network operator. + +The UL data volume is defined as the amount of PDCP SDU bits successfully received by the RNC in the uplink per participating core network operator. + +NOTE: Implementation may collect data volume on a different layer, e.g., MAC-d PDU, but if inter-vendor interoperability is needed the measurement type shall be for PDCP SDU. + +For the CS traffic, the traffic volume is defined as the cumulative time duration of CS service sessions per participating core network operator. + +# --- 8 Mobility Management + +## 8.1 Signalling connection + +Based on TS 23.110 [2], the UE may either have or not have a signalling connection: + +- 1) When a signalling connection exists that is established over the Dedicated Control Service Access Point (DC-SAP) from the Access Stratum. +Therefore, the CN can reach the UE by the dedicated connection SAP on the CN side, and the UTRAN has a context with the UE and CN for this particular connection. This context is erased when the connection is released. The *dedicated connection* can be initiated from the UE only. + +NOTE: A dedicated connection is currently defined as Signalling Connection in TS 23.110 [2]. Note that in the radio interface, dedicated or common channels can be used. + +Depending on the activity of a UE, the location of the UE is known either on cell level (higher activity) or in a larger area consisting of several cells (lower activity). This will (i) minimise the number of location update messages for moving UEs with low activity and (ii) remove the need for paging for UEs known on cell level. + +- 2) When a dedicated connection does not exist, the CN must reach the UE via the Notification SAP. The message sent to the UE can be a request to the UE to establish a dedicated connection. The UE is addressed with a user/terminal identity and a "geographical area". + +## 8.2 Consequences for Mobility Handling + +It is generally agreed to contain radio access specific procedures within UTRAN. This means that all cell level mobility should be handled within UTRAN. Also the cell structure of the radio network should not necessarily be known outside the UTRAN. + +When there exists a dedicated connection to the UE, the UTRAN shall handle the radio interface mobility of the UE. This includes procedures such as soft handover, and procedures for handling mobility in the CELL\_PCH and URA\_PCH/GRA\_PCH state TS 25.331 [7]. + +When a dedicated connection between the UTRAN and the UE does not exist, no UE information is needed in UTRAN. Therefore, the mobility is handled directly between UE and CN outside access stratum (e.g. by means of registration procedures). When paging the UE, the CN indicates a 'geographical area' that is translated within UTRAN to the actual cells that shall be paged. A 'geographical area' shall be identified in a cell-structure independent way. One possibility is the use of 'Location Area identities'. + +During the lifetime of the dedicated connection, the registrations to the CN are suppressed by the UE. When a dedicated connection is released, the UE performs a new registration to the CN, when needed. + +Thus, the UTRAN does not contain any permanent 'location registers' for the UE, but only temporary contexts for the duration of the dedicated connection. This context may typically contain location information (e.g. current cell(s) of the UE) and information about allocated radio resources and related connection references. + +# --- 9 Synchronisation + +## 9.1 SYNCHRONISATION MODEL + +Different synchronisation issues are identified within UTRAN, i.e.: + +- Network Synchronisation; +- Node Synchronisation; +- Transport Channel synchronisation; +- Radio Interface Synchronisation; +- Time Alignment handling. + +The Nodes involved by the above mentioned synchronisation issues (with exception of Network and Node Synchronisation) are shown by the Synchronisation Issues Model of figure 8. Further details of synchronisation are in TS 25.402 [5]. + +![Figure 8: Synchronisation issues model. This diagram illustrates the synchronization hierarchy in a UTRAN network. At the top, a Vocoder is connected to a CN (Core Network). Below the CN, two RNCs (Radio Network Controllers) are shown, each connected to multiple Node Bs. The RNCs are part of an RNS (Radio Network System). At the bottom, two UEs (User Equipment), UE1 and UE2, are connected to Node Bs. The diagram is divided into three horizontal layers by dashed lines, each with a vertical double-headed arrow on the left indicating a synchronization domain: 'Time Alignment Handling' (top layer), 'Transport Channel Synchronisation' (middle layer), and 'Radio Interface Synchronisation' (bottom layer). A callout box points to the interface between a Node B and a UE, stating '[TDD] Radio Interface Sync.' and 'Optional TDD only input & output sync ports'.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +Figure 8: Synchronisation issues model. This diagram illustrates the synchronization hierarchy in a UTRAN network. At the top, a Vocoder is connected to a CN (Core Network). Below the CN, two RNCs (Radio Network Controllers) are shown, each connected to multiple Node Bs. The RNCs are part of an RNS (Radio Network System). At the bottom, two UEs (User Equipment), UE1 and UE2, are connected to Node Bs. The diagram is divided into three horizontal layers by dashed lines, each with a vertical double-headed arrow on the left indicating a synchronization domain: 'Time Alignment Handling' (top layer), 'Transport Channel Synchronisation' (middle layer), and 'Radio Interface Synchronisation' (bottom layer). A callout box points to the interface between a Node B and a UE, stating '[TDD] Radio Interface Sync.' and 'Optional TDD only input & output sync ports'. + +Figure 8: Synchronisation issues model + +# 10 UTRAN O&M Requirements + +## 10.1 O&M of Node B + +The O&M of Node B is separated in two parts: the O&M linked to the actual implementation of Node B, denoted as Implementation Specific O&M, and the O&M which impacts on the traffic carrying resources in Node B controlled from the RNC, denoted *logical O&M*. The RNS architecture with the O&M interfaces is shown in figure 9. + +![Figure 9: RNS architecture with O&M interfaces. This diagram shows the management architecture for an RNS. At the top, a 'Management Platform(s)' box contains four models: 'Node B Management Model' (blue), 'RNC Management Model' (blue), 'Node B Management Model' (yellow), and 'Co-located equipment Management Model' (red). Below this, a central 'RNC' box contains 'RNC O&M', 'Node B Logical O&M', and 'Traffic Functions'. To the left and right are 'Node B' boxes. Each Node B box contains 'RET Antenna Control', 'TMA Control', 'Implementation O&M specific', 'Logical O&M', and 'Traffic Functions'. The left Node B is connected to the RNC via an 'Iub interface' (green line) and to the Management Platform via an 'Iuant interface' (blue line). The right Node B is connected to the RNC via an 'Iub interface' (green line) and to the Management Platform via an 'Iuant interface' (blue line). A red line connects the 'Co-located equipment' box to the right Node B's 'Implementation O&M specific' block.](d8698aacaeead6dfed9a1e448670a2e4_img.jpg) + +Figure 9: RNS architecture with O&M interfaces. This diagram shows the management architecture for an RNS. At the top, a 'Management Platform(s)' box contains four models: 'Node B Management Model' (blue), 'RNC Management Model' (blue), 'Node B Management Model' (yellow), and 'Co-located equipment Management Model' (red). Below this, a central 'RNC' box contains 'RNC O&M', 'Node B Logical O&M', and 'Traffic Functions'. To the left and right are 'Node B' boxes. Each Node B box contains 'RET Antenna Control', 'TMA Control', 'Implementation O&M specific', 'Logical O&M', and 'Traffic Functions'. The left Node B is connected to the RNC via an 'Iub interface' (green line) and to the Management Platform via an 'Iuant interface' (blue line). The right Node B is connected to the RNC via an 'Iub interface' (green line) and to the Management Platform via an 'Iuant interface' (blue line). A red line connects the 'Co-located equipment' box to the right Node B's 'Implementation O&M specific' block. + +Figure 9: RNS architecture with O&M interfaces + +NOTE 1: The concept of an interface from the RNC to the management system is shown for clarity only. Its definition is outside the scope of 3GPP-TSG-RAN-WG3. + +NOTE 2: The presentation of the O&M functions within the management system is shown for clarity only. Their actual implementation is outside the scope of 3GPP-TSG-RAN-WG3. + +NOTE 3: The standardisation of the Implementation Specific O&M is outside the scope of 3GPP-TSG-RAN-WG3. The 3GPP-TSG-RAN-WG3 should only address the bearer for the Implementation Specific O&M. + +NOTE 4: The figure shows only logical connections and does not intend to mandate any physical interfaces. + +NOTE 5: The Iuant interface to the control unit of the RET antennas or TMAs is specified in the series of Technical Specifications 25.460 [24], 25.461 [25], 25.462 [26] and 25.466 [32]. An Implementation Specific O&M function is needed for the RET antennas or TMAs control to translate the control signalling from the Node B Element Manager into the control commands of the Iuant interface specified in TS 25.460 [24]. + +### 10.1.1 Implementation Specific O&M + +The Implementation Specific O&M functions are heavily dependent on the implementation of Node B, both for its hardware components and for the management of the software components. It needs therefore to be implementation dependent, and be performed between Node B and the management system. + +One solution for the transport of Implementation Specific O&M is to route from Node B to the management system via the RNC. In this case, the Implementation Specific O&M interface and Iub interface share the same physical bearer, and TS 25.442 [4] specifies the routing function and the transport bearer for this scenario. The deployment of the routing across the RNC in the UTRAN is optional. Where signalling between co-located equipment and its management system is required, this may be carried over the same bearer as Implementation Specific O&M. + +### 10.1.2 Logical O&M + +Logical O&M is the signalling associated with the control of logical resources (channels, cells,...) owned by the RNC but physically implemented in the Node B. The RNC controls these logical resources. A number of O&M procedures physically implemented in Node B impact on the logical resources and therefore require an information exchange between RNC and Node B. All messages needed to support this information exchange are classified as Logical O&M forming an integral part of NBAP. + +## 10.2 O&M of RNC + +### 10.2.1 O&M requirements + +The O&M of an RNC shall, if supported, configure the UTRAN with reporting criteria for the Traffic Volume for RAN Sharing function. The O&M may configure the UTRAN to collect and report volume reports on a per cell basis. + +# --- 11 UTRAN Interfaces + +## 11.1 General Protocol Model for UTRAN Interfaces + +### 11.1.1 General + +The general protocol model for UTRAN Interfaces is depicted in figure 10, and described in detail in the following subclauses. The structure is based on the principle that the layers and planes are logically independent of each other. Therefore, as and when required, the standardisation body can easily alter protocol stacks and planes to fit future requirements. + +![Figure 10: General Protocol Model for UTRAN Interfaces. The diagram shows two main layers: Radio Network Layer and Transport Network Layer. The Radio Network Layer is divided into Control Plane (containing Application Protocol) and User Plane (containing Data Stream(s)). The Transport Network Layer is divided into three vertical planes: Transport User Network Plane (left), Transport Network Control Plane (middle), and Transport User Network Plane (right). The Control Plane in the Transport Network Layer contains Signalling Bearer(s) which connect to the Application Protocol in the Radio Network Layer. The Transport Network Control Plane contains ALCAP(s) and Signalling Bearer(s) which connect to the Signalling Bearer(s) in the Transport User Network Plane. The User Plane in the Transport Network Layer contains Data Bearer(s) which connect to the Data Stream(s) in the Radio Network Layer. All three planes in the Transport Network Layer connect to the Physical Layer at the bottom.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +Figure 10: General Protocol Model for UTRAN Interfaces. The diagram shows two main layers: Radio Network Layer and Transport Network Layer. The Radio Network Layer is divided into Control Plane (containing Application Protocol) and User Plane (containing Data Stream(s)). The Transport Network Layer is divided into three vertical planes: Transport User Network Plane (left), Transport Network Control Plane (middle), and Transport User Network Plane (right). The Control Plane in the Transport Network Layer contains Signalling Bearer(s) which connect to the Application Protocol in the Radio Network Layer. The Transport Network Control Plane contains ALCAP(s) and Signalling Bearer(s) which connect to the Signalling Bearer(s) in the Transport User Network Plane. The User Plane in the Transport Network Layer contains Data Bearer(s) which connect to the Data Stream(s) in the Radio Network Layer. All three planes in the Transport Network Layer connect to the Physical Layer at the bottom. + +**Figure 10: General Protocol Model for UTRAN Interfaces** + +### 11.1.2 Horizontal Layers + +The Protocol Structure consists of two main layers, Radio Network Layer, and Transport Network Layer. All UTRAN related issues are visible only in the Radio Network Layer, and the Transport Network Layer represents standard transport technology that is selected to be used for UTRAN, but without any UTRAN specific requirements. + +### 11.1.3 Vertical Planes + +#### 11.1.3.1 Control Plane + +The Control Plane Includes the Application Protocol, i.e. RANAP, RNSAP or NBAP, and the Signalling Bearer for transporting the Application Protocol messages. + +Among other things, the Application Protocol is used for setting up bearers for (i.e. Radio Access Bearer or Radio Link) in the Radio Network Layer. In the three plane structure the bearer parameters in the Application Protocol are not directly tied to the User Plane technology, but are rather general bearer parameters. + +The Signalling Bearer for the Application Protocol may or may not be of the same type as the Signalling Protocol for the ALCAP. The Signalling Bearer is always set up by O&M actions. + +#### 11.1.3.2 User Plane + +The User Plane Includes the Data Stream(s) and the Data Bearer(s) for the Data Stream(s). The Data Stream(s) is/are characterised by one or more frame protocols specified for that interface. + +#### 11.1.3.3 Transport Network Control Plane + +The Transport Network Control Plane does not include any Radio Network Layer information, and is completely in the Transport Layer. It includes the ALCAP protocol(s) that is/are needed to set up the transport bearers (Data Bearer) for the User Plane. It also includes the appropriate Signalling Bearer(s) needed for the ALCAP protocol(s). + +The Transport Network Control Plane is a plane that acts between the Control Plane and the User Plane. The introduction of Transport Network Control Plane is performed in a way that the Application Protocol in the Radio Network Control Plane is kept completely independent of the technology selected for Data Bearer in the User Plane. Indeed, the decision to actually use an ALCAP protocol is completely kept within the Transport Network Layer. + +It should be noted that ALCAP might not be used for all types Data Bearers. If there is no ALCAP signalling transaction, the Transport Network Control Plane is not needed at all. This is the case when pre-configured Data + +Bearers are used or when the IP (IETF RFC 791 [17]) UTRAN option is used between two IP UTRAN nodes or between an IP UTRAN node and an IP CN node. + +When Transport Network Control Plane is used, the transport bearers for the Data Bearer in the User Plane are set up in the following fashion. First there is a signalling transaction by the Application Protocol in the Control Plane, which triggers the set up of the Data Bearer by the ALCAP protocol that is specific for the User Plane technology. + +The following interworking alternatives are specified for the IP-ATM interworking: + +- 1) ATM/IP Dual Stack supported in the IP UTRAN node. When an ATM/IP dual stack is implemented in the IP UTRAN node, support of an IP ALCAP protocol is not required. + +Annex A of TS 25.414 [9] shows an example of protocols for the case the ATM&IP UTRAN/CN-node has no ATM connectivity. + +![Diagram of Rel5 IP UTRAN node with IP and ATM transport options.](4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg) + +The diagram shows a 'Rel5 IP UTRAN node' represented by a large rectangle. Inside this rectangle, at the top, is a box labeled 'RNL'. Below 'RNL' are two side-by-side boxes labeled 'IP' and 'ATM'. A horizontal line labeled 'IP transport option' enters the node from the left and connects to the 'IP' box. Another horizontal line labeled 'ATM transport option' exits the node to the right and connects to the 'ATM' box. + +Diagram of Rel5 IP UTRAN node with IP and ATM transport options. + +- 2) An Interworking Function (IWF), either internal or external to the UTRAN/CN node. + +Annex A of TS 25.414 [9] shows an example of a protocol stack for the case when the IWF is an external unit to the UTRAN/CN node. Other protocol stacks for this case are not precluded. + +![Diagram of Rel5 IP UTRAN node with an internal TNL Interworking Function.](e97d663314aff9c29bf8971323e6539e_img.jpg) + +The diagram shows a 'Rel5 IP UTRAN node' represented by a dashed rectangle. Inside, on the left, is a box labeled 'RNL' above two 'IP' boxes. On the right, there is a box labeled 'TNL Interworking Function' above an 'IP' box and an 'ATM' box. A horizontal line labeled 'IP transport option' enters from the left and connects to the left 'IP' box. A horizontal line labeled 'ATM transport option' exits to the right and connects to the 'ATM' box. The 'IP' box under 'RNL' and the 'IP' box under 'TNL Interworking Function' are connected by a vertical line. + +Diagram of Rel5 IP UTRAN node with an internal TNL Interworking Function. + +#### 11.1.3.4 Transport Network User Plane + +The Data Bearer(s) in the User Plane, and the Signalling Bearer(s) for Application Protocol, belong also to Transport Network User Plane. As described in the previous subclause, the Data Bearers in Transport Network User Plane are directly controlled by Transport Network Control Plane during real time operation, but the control actions required for setting up the Signalling Bearer(s) for Application Protocol are considered O&M actions. + +## 11.2 Protocol Model (Informative) + +The following subclause is a informative subclause which aim is to provide an overall picture of how the MAC layer is distributed over Uu, Iub and Iur for the RACH, FACH, DCH, [TDD – DSCH, USCH] and HS-DSCH. + +### 11.2.1 RACH Transport Channel + +Figure 11 shows the protocol stack model for the RACH transport channel when the Controlling and Serving RNC are co-incident. + +For the RACH transport channel, Dedicated MAC (MAC-d) uses the services of Common MAC (MAC-c/sh). + +![Figure 11: RACH: Coincident Controlling and Serving RNC. This diagram shows the protocol stack for a User Equipment (UE), NodeB, and a combined CRNC/SRNC. The UE stack consists of DTCH, DCCH, and CCCH channels at the top, followed by MAC-d, MAC-c/sh, and PHY layers. The NodeB stack consists of PHY, RachFP, and TNL layers. The CRNC/SRNC stack consists of CCCH, DCCH, and DTCH channels at the top, followed by MAC-d, MAC-c/sh, RachFP, and TNL layers. The interfaces shown are Uu between UE and NodeB, and Iub between NodeB and CRNC/SRNC.](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +Figure 11: RACH: Coincident Controlling and Serving RNC. This diagram shows the protocol stack for a User Equipment (UE), NodeB, and a combined CRNC/SRNC. The UE stack consists of DTCH, DCCH, and CCCH channels at the top, followed by MAC-d, MAC-c/sh, and PHY layers. The NodeB stack consists of PHY, RachFP, and TNL layers. The CRNC/SRNC stack consists of CCCH, DCCH, and DTCH channels at the top, followed by MAC-d, MAC-c/sh, RachFP, and TNL layers. The interfaces shown are Uu between UE and NodeB, and Iub between NodeB and CRNC/SRNC. + +**Figure 11: RACH: Coincident Controlling and Serving RNC** + +The Common MAC (MAC-c/sh) entity in the UE transfers MAC-c/sh PDU to the peer MAC-c/sh entity in the RNC using the services of the Physical Layer. + +An Interworking Function (IWF) in the Node B interworks the RACH frame received by the PHY entity into the RACH Frame Protocol (RACH FP) entity. + +The RACH Frame Protocol entity adds header information to form a RACH FP PDU that is transported to the RNC over a transport bearer. + +At the RNC, the RACH FP entity delivers the MAC-c/sh PDU to the MAC-c/sh entity. + +Figure 12 shows the protocol model for the RACH transport channel with separate Controlling and Serving RNC. In this case, Iur RACH Frame Protocol (RACH FP) is used to interwork the Common MAC (MAC-c/sh) at the Controlling RNC with the Dedicated MAC (MAC-d) at the Serving RNC. + +![Figure 12: RACH: Separate Controlling and Serving RNC. This diagram shows the protocol stack for a User Equipment (UE), NodeB, a Controlling RNC (CRNC), and a Serving RNC (SRNC). The UE stack is identical to Figure 11. The NodeB stack is identical to Figure 11. The CRNC stack consists of CCCH at the top, followed by MAC-c/sh, RachFP, and TNL layers. The SRNC stack consists of DCCH and DTCH channels at the top, followed by MAC-d, RACH FP, and TNL layers. The interfaces shown are Uu between UE and NodeB, Iub between NodeB and CRNC, and Iur between CRNC and SRNC.](63a2519518616620ef0e53d98b923c05_img.jpg) + +Figure 12: RACH: Separate Controlling and Serving RNC. This diagram shows the protocol stack for a User Equipment (UE), NodeB, a Controlling RNC (CRNC), and a Serving RNC (SRNC). The UE stack is identical to Figure 11. The NodeB stack is identical to Figure 11. The CRNC stack consists of CCCH at the top, followed by MAC-c/sh, RachFP, and TNL layers. The SRNC stack consists of DCCH and DTCH channels at the top, followed by MAC-d, RACH FP, and TNL layers. The interfaces shown are Uu between UE and NodeB, Iub between NodeB and CRNC, and Iur between CRNC and SRNC. + +**Figure 12: RACH: Separate Controlling and Serving RNC** + +### 11.2.2 CPCH [FDD] Transport Channel + +Void. + +### 11.2.3 FACH Transport Channel + +Figure 15 shows the protocol model for the FACH transport channel when the Controlling and Serving RNC are co-incident. + +![Figure 15: FACH Co-incident Controlling and Serving RNC. This diagram illustrates the protocol stack for the FACH transport channel when the Controlling RNC (CRNC) and Serving RNC (SRNC) are co-located. On the left, the User Equipment (UE) stack consists of MAC-d, MAC-c/sh/m, and PHY layers. The MAC-d layer is connected to DTCH, DCCH, MTCH, and MCCH channels. The MAC-c/sh/m layer is connected to CCCH, MSCH, and FACH FP. The PHY layer is connected to the Uu interface. In the center, the NodeB stack consists of PHY and TNL layers. The PHY layer is connected to the Uu interface and the FACH FP. The TNL layer is connected to the Iub interface. On the right, the CRNC/SRNC stack consists of MAC-d, MAC-c/sh/m, FACH FP, and TNL layers. The MAC-d layer is connected to MTCH, MCCH, DCCH, and DTCH channels. The MAC-c/sh/m layer is connected to MSCH, CCCH, and FACH FP. The FACH FP layer is connected to the Iub interface. The TNL layer is connected to the Iub interface.](9a14684f8ae1345c6efea6f5994c730c_img.jpg) + +Figure 15: FACH Co-incident Controlling and Serving RNC. This diagram illustrates the protocol stack for the FACH transport channel when the Controlling RNC (CRNC) and Serving RNC (SRNC) are co-located. On the left, the User Equipment (UE) stack consists of MAC-d, MAC-c/sh/m, and PHY layers. The MAC-d layer is connected to DTCH, DCCH, MTCH, and MCCH channels. The MAC-c/sh/m layer is connected to CCCH, MSCH, and FACH FP. The PHY layer is connected to the Uu interface. In the center, the NodeB stack consists of PHY and TNL layers. The PHY layer is connected to the Uu interface and the FACH FP. The TNL layer is connected to the Iub interface. On the right, the CRNC/SRNC stack consists of MAC-d, MAC-c/sh/m, FACH FP, and TNL layers. The MAC-d layer is connected to MTCH, MCCH, DCCH, and DTCH channels. The MAC-c/sh/m layer is connected to MSCH, CCCH, and FACH FP. The FACH FP layer is connected to the Iub interface. The TNL layer is connected to the Iub interface. + +**Figure 15: FACH Co-incident Controlling and Serving RNC** + +The Common MAC (MAC-c/sh/m) entity in the RNC transfers MAC-c PDU to the peer MAC-c entity in the UE using the services of the FACH Frame Protocol (FACH FP) entity. + +The FACH Frame Protocol entity adds header information to form a FACH FP PDU which is transported to the Node B over a transport bearer. + +An Interworking Function (IWF) in the Node B interworks the FACH frame received by FACH Frame Protocol (FACH FP) entity into the PHY entity. + +FACH scheduling is performed by MAC-c/sh/m in the CRNC. + +Figure 16 shows the protocol model for the FACH transport channel with separate Controlling and Serving RNC. In this case, Iur FACH Frame Protocol is used to interwork the Common MAC (MAC-c) at the Controlling RNC with the Dedicated MAC (MAC-d) at the Serving RNC. + +![Figure 16: FACH: Separate Controlling and Serving RNC. This diagram illustrates the protocol stack for the FACH transport channel when the Controlling RNC (CRNC) and Serving RNC (SRNC) are separate. On the left, the User Equipment (UE) stack consists of MAC-d, MAC-c/sh, and PHY layers. The MAC-d layer is connected to DTCH, DCCH, MTCH, and MCCH channels. The MAC-c/sh layer is connected to CCCH, MSCH, and FACH FP. The PHY layer is connected to the Uu interface. In the center, the NodeB stack consists of PHY and TNL layers. The PHY layer is connected to the Uu interface and the FACH FP. The TNL layer is connected to the Iub interface. On the right, the CRNC stack consists of MAC-c/sh/m, FACH FP, and TNL layers. The MAC-c/sh/m layer is connected to MTCH, MCCH, MSCH, and CCCH channels. The FACH FP layer is connected to the Iub interface. The TNL layer is connected to the Iur interface. On the far right, the SRNC stack consists of MAC-d, FACH FP, and TNL layers. The MAC-d layer is connected to DCCH and DTCH channels. The FACH FP layer is connected to the Iur interface. The TNL layer is connected to the Iur interface.](ddd86d7df6cf14d68c0faf111c1e8fae_img.jpg) + +Figure 16: FACH: Separate Controlling and Serving RNC. This diagram illustrates the protocol stack for the FACH transport channel when the Controlling RNC (CRNC) and Serving RNC (SRNC) are separate. On the left, the User Equipment (UE) stack consists of MAC-d, MAC-c/sh, and PHY layers. The MAC-d layer is connected to DTCH, DCCH, MTCH, and MCCH channels. The MAC-c/sh layer is connected to CCCH, MSCH, and FACH FP. The PHY layer is connected to the Uu interface. In the center, the NodeB stack consists of PHY and TNL layers. The PHY layer is connected to the Uu interface and the FACH FP. The TNL layer is connected to the Iub interface. On the right, the CRNC stack consists of MAC-c/sh/m, FACH FP, and TNL layers. The MAC-c/sh/m layer is connected to MTCH, MCCH, MSCH, and CCCH channels. The FACH FP layer is connected to the Iub interface. The TNL layer is connected to the Iur interface. On the far right, the SRNC stack consists of MAC-d, FACH FP, and TNL layers. The MAC-d layer is connected to DCCH and DTCH channels. The FACH FP layer is connected to the Iur interface. The TNL layer is connected to the Iur interface. + +**Figure 16: FACH: Separate Controlling and Serving RNC** + +### 11.2.4 DCH Transport Channel + +Figure 17 shows the protocol model for the DCH transport channel when the Controlling and Serving RNC are co-incident. + +![Figure 17: DCH: Co-incident Controlling and Serving RNC. This diagram illustrates the protocol stack for the DCH transport channel when the Controlling RNC (CRNC) and Serving RNC (SRNC) are co-located. On the left, the User Equipment (UE) stack consists of MAC-d, PHY, and DTCH/DCCH channels. The UE is connected to a NodeB via the Uu interface. The NodeB stack includes PHY, DchFP, and TNL. The NodeB is connected to the CRNC/SRNC via the Iub interface. The CRNC/SRNC stack consists of MAC-d, PHY, DchFP, and TNL, with DCCH and DTCH channels at the top.](0c80c383f76034e117adf5e5eaadaaf3_img.jpg) + +Figure 17: DCH: Co-incident Controlling and Serving RNC. This diagram illustrates the protocol stack for the DCH transport channel when the Controlling RNC (CRNC) and Serving RNC (SRNC) are co-located. On the left, the User Equipment (UE) stack consists of MAC-d, PHY, and DTCH/DCCH channels. The UE is connected to a NodeB via the Uu interface. The NodeB stack includes PHY, DchFP, and TNL. The NodeB is connected to the CRNC/SRNC via the Iub interface. The CRNC/SRNC stack consists of MAC-d, PHY, DchFP, and TNL, with DCCH and DTCH channels at the top. + +**Figure 17: DCH: Co-incident Controlling and Serving RNC** + +The DCH transport channel introduces the concept of distributed PHY layer. + +An Interworking Function (IWF) in the Node B interworks between the DCH Frame Protocol (DCH FP) entity and the PHY entity. + +![Figure 18: DCH: Separate Controlling and Serving RNC. This diagram illustrates the protocol stack for the DCH transport channel when the CRNC and SRNC are separate. The UE stack on the left includes MAC-d, PHY-upper, PHY, and DTCH/DCCH channels. The UE connects to a NodeB via the Uu interface. The NodeB stack includes PHY, DchFP, and TNL. The NodeB connects to the CRNC via the Iub interface. The CRNC stack includes PHY, DchFP, and TNL. The CRNC connects to the SRNC via the Iur interface. The SRNC stack includes MAC-d, PHY, DchFP, and TNL, with DCCH and DTCH channels at the top.](0d0897dd7f03672d186db9d56ea0d6f5_img.jpg) + +Figure 18: DCH: Separate Controlling and Serving RNC. This diagram illustrates the protocol stack for the DCH transport channel when the CRNC and SRNC are separate. The UE stack on the left includes MAC-d, PHY-upper, PHY, and DTCH/DCCH channels. The UE connects to a NodeB via the Uu interface. The NodeB stack includes PHY, DchFP, and TNL. The NodeB connects to the CRNC via the Iub interface. The CRNC stack includes PHY, DchFP, and TNL. The CRNC connects to the SRNC via the Iur interface. The SRNC stack includes MAC-d, PHY, DchFP, and TNL, with DCCH and DTCH channels at the top. + +**Figure 18: DCH: Separate Controlling and Serving RNC** + +Figure 18 shows the protocol model for the DCH transport channel with separate Controlling and Serving RNC. In this case, the Iub DCH FP is terminated in the CRNC and interworked with the Iur DCH FP through a PHY function. This function performs optional soft handover or can be a null function. + +### 11.2.5 DSCH Transport Channel [TDD] + +Figure 19 shows the protocol model for the DSCH transport channel when the Controlling and Serving RNC are co-incident. + +![Figure 19: DSCH Co-incident Controlling and Serving RNC. This diagram illustrates the protocol stack for the DSCH transport channel when the Controlling RNC (CRNC) and Serving RNC (SRNC) are co-located. On the left, the User Equipment (UE) stack consists of MAC-d, MAC-c/sh, and PHY layers. The UE is connected to the NodeB via the Uu interface. The NodeB stack includes PHY, DschFP, and TNL layers. The NodeB is connected to the CRNC/SRNC via the Iub interface. The CRNC/SRNC stack consists of MAC-d, MAC-c/sh, DschFP, and TNL layers. Arrows indicate data flow: DTCH and DCCH channels are shown entering the MAC-d layer in the CRNC/SRNC and exiting the MAC-d layer in the UE.](67d03c9e89620d73e3786c869e559752_img.jpg) + +Figure 19: DSCH Co-incident Controlling and Serving RNC. This diagram illustrates the protocol stack for the DSCH transport channel when the Controlling RNC (CRNC) and Serving RNC (SRNC) are co-located. On the left, the User Equipment (UE) stack consists of MAC-d, MAC-c/sh, and PHY layers. The UE is connected to the NodeB via the Uu interface. The NodeB stack includes PHY, DschFP, and TNL layers. The NodeB is connected to the CRNC/SRNC via the Iub interface. The CRNC/SRNC stack consists of MAC-d, MAC-c/sh, DschFP, and TNL layers. Arrows indicate data flow: DTCH and DCCH channels are shown entering the MAC-d layer in the CRNC/SRNC and exiting the MAC-d layer in the UE. + +**Figure 19: DSCH Co-incident Controlling and Serving RNC** + +The Shared MAC (MAC-c/sh) entity in the RNC transfers MAC-c/sh PDU to the peer MAC-c/sh entity in the UE using the services of the DSCH Frame Protocol (DSCH FP) entity. The DSCH FP entity adds header information to form a DSCH FP PDU that is transported to the Node B over a transport bearer. + +An Interworking Function (IWF) in the Node B interworks the DSCH frame received by DSCH FP entity into the PHY entity. DSCH scheduling is performed by MAC-c/sh in the CRNC. + +Figure 20 shows the protocol model for the DSCH transport channel with separate Controlling and Serving RNC. In this case, Iur DSCH Frame Protocol is used to interwork the MAC-c/sh at the Controlling RNC with the MAC-d at the Serving RNC. + +![Figure 20: DSCH: Separate Controlling and Serving RNC. This diagram illustrates the protocol stack for the DSCH transport channel when the Controlling RNC (CRNC) and Serving RNC (SRNC) are separate. The UE stack on the left is identical to Figure 19. The UE is connected to the NodeB via the Uu interface. The NodeB stack includes PHY, DschFP, and TNL layers. The NodeB is connected to the CRNC via the Iub interface. The CRNC stack consists of MAC-c/sh, DschFP, and TNL layers. The CRNC is connected to the SRNC via the Iur interface. The SRNC stack consists of MAC-d, DschFP, and TNL layers. Arrows indicate data flow: DTCH and DCCH channels are shown entering the MAC-d layer in the SRNC and exiting the MAC-d layer in the UE.](080a7af02bc47cf21ebfae4e0be39745_img.jpg) + +Figure 20: DSCH: Separate Controlling and Serving RNC. This diagram illustrates the protocol stack for the DSCH transport channel when the Controlling RNC (CRNC) and Serving RNC (SRNC) are separate. The UE stack on the left is identical to Figure 19. The UE is connected to the NodeB via the Uu interface. The NodeB stack includes PHY, DschFP, and TNL layers. The NodeB is connected to the CRNC via the Iub interface. The CRNC stack consists of MAC-c/sh, DschFP, and TNL layers. The CRNC is connected to the SRNC via the Iur interface. The SRNC stack consists of MAC-d, DschFP, and TNL layers. Arrows indicate data flow: DTCH and DCCH channels are shown entering the MAC-d layer in the SRNC and exiting the MAC-d layer in the UE. + +**Figure 20: DSCH: Separate Controlling and Serving RNC** + +### 11.2.6 USCH Transport Channel [TDD] + +Figure 21 shows the protocol model for the USCH transport channel when the Controlling and Serving RNC are co-incident. + +![Figure 21: USCH Co-incident Controlling and Serving RNC. This diagram illustrates the protocol stack for the USCH transport channel when the Controlling RNC (CRNC) and Serving RNC (SRNC) are co-located. On the left, the User Equipment (UE) stack consists of DTCH and DCCH channels at the top, followed by MAC-d, MAC-c/sh, and PHY layers. The UE is connected to a NodeB via the Uu interface. The NodeB stack includes PHY and TNL layers, with an UschFP entity positioned between them. The NodeB is connected to the CRNC/SRNC via the Iub interface. The CRNC/SRNC stack consists of TNL, UschFP, MAC-c/sh, and MAC-d layers at the top, which then branches into DCCH and DTCH channels.](b44f89b176c971c7dd264c07bfef2c2a_img.jpg) + +Figure 21: USCH Co-incident Controlling and Serving RNC. This diagram illustrates the protocol stack for the USCH transport channel when the Controlling RNC (CRNC) and Serving RNC (SRNC) are co-located. On the left, the User Equipment (UE) stack consists of DTCH and DCCH channels at the top, followed by MAC-d, MAC-c/sh, and PHY layers. The UE is connected to a NodeB via the Uu interface. The NodeB stack includes PHY and TNL layers, with an UschFP entity positioned between them. The NodeB is connected to the CRNC/SRNC via the Iub interface. The CRNC/SRNC stack consists of TNL, UschFP, MAC-c/sh, and MAC-d layers at the top, which then branches into DCCH and DTCH channels. + +**Figure 21: USCH Co-incident Controlling and Serving RNC** + +The Shared MAC (MAC-c/sh) entity in the RNC *receives* MAC-c/sh PDU *from* the peer MAC-c/sh entity in the UE using the services of the Interworking Function in the Node B, and the USCH Frame Protocol (USCH FP) entity. The USCH FP entity *in the Node B* adds header information to form a USCH FP PDU that is transported to the RNC over a transport bearer. + +An Interworking Function (IWF) in the Node B interworks *the received USCH PHY entity into an USCH frame to be transmitted by the USCH FP entity over the Iub interface*. USCH scheduling is performed by MAC-c/sh in UE and by C-RRc in the CRNC. + +Figure 22 shows the protocol model for the USCH transport channel with separate Controlling and Serving RNC. In this case, Iur USCH Frame Protocol is used to interwork the MAC-c/sh at the Controlling RNC with the MAC-d at the Serving RNC. + +![Figure 22: USCH: Separate Controlling and Serving RNC. This diagram illustrates the protocol stack for the USCH transport channel when the Controlling RNC (CRNC) and Serving RNC (SRNC) are separate. The UE stack on the left is identical to Figure 21. The UE connects to a NodeB via the Uu interface. The NodeB stack includes PHY, TNL, and UschFP layers. The NodeB connects to the CRNC via the Iub interface. The CRNC stack consists of TNL, UschFP, and MAC-c/sh layers. The CRNC is connected to the SRNC via the Iur interface. The SRNC stack consists of TNL, UschFP, and MAC-d layers at the top, which then branch into DCCH and DTCH channels.](30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg) + +Figure 22: USCH: Separate Controlling and Serving RNC. This diagram illustrates the protocol stack for the USCH transport channel when the Controlling RNC (CRNC) and Serving RNC (SRNC) are separate. The UE stack on the left is identical to Figure 21. The UE connects to a NodeB via the Uu interface. The NodeB stack includes PHY, TNL, and UschFP layers. The NodeB connects to the CRNC via the Iub interface. The CRNC stack consists of TNL, UschFP, and MAC-c/sh layers. The CRNC is connected to the SRNC via the Iur interface. The SRNC stack consists of TNL, UschFP, and MAC-d layers at the top, which then branch into DCCH and DTCH channels. + +**Figure 22: USCH: Separate Controlling and Serving RNC** + +### 11.2.7 HS-DSCH Transport Channel + +Figure 23 shows the protocol model for the HS-DSCH transport channel when the Controlling and Serving RNC are co-incident. [FDD and 1.28 Mcps TDD – The protocol model in Figure 23 is applied for HS-DSCH configured for UEs in Cell\_DCH.] + +![Figure 23: HS-DSCH Co-incident Controlling and Serving RNC. This diagram illustrates the protocol stack for the HS-DSCH transport channel when the Controlling and Serving RNC are co-located. On the left, the UE (User Equipment) stack consists of MAC-d, MAC-(e)hs, and PHY layers. The MAC-d layer is connected to DTCH and DCCH channels. The UE is connected to the NodeB via the Uu interface. The NodeB stack includes PHY, MAC-(e)hs, and a combined HS-DSCHFP/HS-DSCHFP entity. The NodeB is connected to the CRNC/SRNC via the Iub interface. The CRNC/SRNC stack consists of TNL, HS-DSCHFP, and MAC-d layers. The MAC-d layer is connected to DCCH and DTCH channels.](69e5f1993021af230d08c08aac97d9df_img.jpg) + +Figure 23: HS-DSCH Co-incident Controlling and Serving RNC. This diagram illustrates the protocol stack for the HS-DSCH transport channel when the Controlling and Serving RNC are co-located. On the left, the UE (User Equipment) stack consists of MAC-d, MAC-(e)hs, and PHY layers. The MAC-d layer is connected to DTCH and DCCH channels. The UE is connected to the NodeB via the Uu interface. The NodeB stack includes PHY, MAC-(e)hs, and a combined HS-DSCHFP/HS-DSCHFP entity. The NodeB is connected to the CRNC/SRNC via the Iub interface. The CRNC/SRNC stack consists of TNL, HS-DSCHFP, and MAC-d layers. The MAC-d layer is connected to DCCH and DTCH channels. + +**Figure 23: HS-DSCH Co-incident Controlling and Serving RNC** + +The High Speed MAC (MAC-hs) or Enhanced High Speed MAC (MAC-ehs) entity in the Node B transfers MAC-hs (or MAC-ehs) PDU to the peer MAC-hs (or MAC-ehs) entity in the UE over the Uu interface. The Dedicated MAC (MAC-d) entity in the RNC transfers MAC-d PDUs to the MAC-hs or MAC-ehs in the Node B using the services of the HS-DSCH Frame Protocol (HS-DSCH FP) entity. The HS-DSCH FP entity adds header information to form a HS-DSCH FP PDU that is transported to the Node B over a transport bearer. + +A Relaying Function in the Node B relays the HS-DSCH frame received by HS-DSCH FP entity to the MAC-hs (or MAC-ehs) entity. HS-DSCH scheduling is performed by MAC-hs (or MAC-ehs) in the Node B. + +Figure 24 shows the protocol model for the HS-DSCH transport channel with separate Controlling and Serving RNC. [FDD and 1.28 Mcps TDD – The protocol model in Figure 24 is applied for HS-DSCH configured for UEs in Cell\_DCH.] In this case, Iur HS-DSCH Frame Protocol is used to interwork the Flow Control function at the Controlling RNC with the MAC-d at the Serving RNC. Also in this case, Iub HS-DSCH Frame Protocol is used to interwork the MAC-hs (or MAC-ehs) at the Node B with the Flow Control function at the Controlling RNC. + +![Figure 24: HS-DSCH: Separate Controlling and Serving RNC (configuration with CRNC flow control). This diagram illustrates the protocol stack for the HS-DSCH transport channel when the Controlling and Serving RNC are separate. On the left, the UE stack consists of MAC-d, MAC-(e)hs, and PHY layers. The MAC-d layer is connected to DTCH and DCCH channels. The UE is connected to the NodeB via the Uu interface. The NodeB stack includes PHY, MAC-(e)hs, and HS-DSCHFP layers. The NodeB is connected to the CRNC via the Iub interface. The CRNC stack consists of CRNC HS-DSCH Flow Control, HS-DSCHFP, and TNL layers. The CRNC is connected to the SRNC via the Iur interface. The SRNC stack consists of HS-DSCHFP and MAC-d layers. The MAC-d layer is connected to DCCH and DTCH channels.](d116934392360da963e91d840d1e45a8_img.jpg) + +Figure 24: HS-DSCH: Separate Controlling and Serving RNC (configuration with CRNC flow control). This diagram illustrates the protocol stack for the HS-DSCH transport channel when the Controlling and Serving RNC are separate. On the left, the UE stack consists of MAC-d, MAC-(e)hs, and PHY layers. The MAC-d layer is connected to DTCH and DCCH channels. The UE is connected to the NodeB via the Uu interface. The NodeB stack includes PHY, MAC-(e)hs, and HS-DSCHFP layers. The NodeB is connected to the CRNC via the Iub interface. The CRNC stack consists of CRNC HS-DSCH Flow Control, HS-DSCHFP, and TNL layers. The CRNC is connected to the SRNC via the Iur interface. The SRNC stack consists of HS-DSCHFP and MAC-d layers. The MAC-d layer is connected to DCCH and DTCH channels. + +**Figure 24: HS-DSCH: Separate Controlling and Serving RNC (configuration with CRNC flow control)** + +Figure 25 shows the protocol model for the HS-DSCH transport channel with the Controlling RNC user plane RNL being bypassed. [FDD and 1.28 Mcps TDD – The protocol model in Figure 25 is applied for HS-DSCH configured for UEs in Cell\_DCH.] In this case, the CRNC does not have any user plane RNL function for the HS-DSCH. MAC-d in SRNC is located directly above MAC-hs (or MC-ehs) in Node B, i.e. in the HS-DSCH user plane RNL, the SRNC is directly connected to the Node B, thus bypassing the CRNC user plane RNL. The CRNC performs only user plane TNL functions. + +![Figure 25: HS-DSCH: Serving RNC with bypassed Controlling RNC (configuration without CRNC flow control). The diagram illustrates the protocol stack across three entities: UE, NodeB, and SRNC, with an intermediate CRNC. The UE stack consists of MAC-d, MAC-(e)hs, and PHY. The NodeB stack consists of MAC-(e)hs, HS-DSCHFP, PHY, and TNL. The CRNC stack consists of two TNL entities. The SRNC stack consists of MAC-d, HS-DSCHFP, and TNL. Interfaces are labeled Uu (between UE and NodeB), Iub (between NodeB and CRNC), and Iur (between CRNC and SRNC). Arrows indicate data flow from DCCH/DTCH in the UE through the MAC layers to the PHY, and from the SRNC's MAC-d layer down through HS-DSCHFP to TNL.](7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg) + +Figure 25: HS-DSCH: Serving RNC with bypassed Controlling RNC (configuration without CRNC flow control). The diagram illustrates the protocol stack across three entities: UE, NodeB, and SRNC, with an intermediate CRNC. The UE stack consists of MAC-d, MAC-(e)hs, and PHY. The NodeB stack consists of MAC-(e)hs, HS-DSCHFP, PHY, and TNL. The CRNC stack consists of two TNL entities. The SRNC stack consists of MAC-d, HS-DSCHFP, and TNL. Interfaces are labeled Uu (between UE and NodeB), Iub (between NodeB and CRNC), and Iur (between CRNC and SRNC). Arrows indicate data flow from DCCH/DTCH in the UE through the MAC layers to the PHY, and from the SRNC's MAC-d layer down through HS-DSCHFP to TNL. + +**Figure 25: HS-DSCH: Serving RNC with bypassed Controlling RNC (configuration without CRNC flow control)** + +[FDD and 1.28 Mcps TDD - Figure 25A shows the protocol model for the HS-DSCH transport channel configured for UEs in Cell\_FACH, Cell\_PCH and URA\_PCH, when the Controlling and Serving RNC are co-incident. + +The Common MAC (MAC-c/sh/m) entity in the RNC transfers MAC-c PDU to the peer MAC-c entity in the UE using the services of the HS-DSCH Frame Protocol (HS-DSCH FP) entity. + +The HS-DSCH Frame Protocol entity adds header information to form a HS-DSCH FP PDU which is transported to the Node B over a transport bearer. + +The Enhanced High Speed MAC (MAC-ehs) entity in the Node B transfers MAC-ehs PDU to the peer MAC-ehs entity in the UE over the Uu interface. ] + +![Figure 25A: Protocol stack diagram for HS-DSCH configured for UE in Cell_FACH, Cell_PCH and URA_PCH with co-incident Controlling and Serving RNC. The diagram shows three main entities: UE, NodeB, and CRNC/SRNC. The UE stack consists of MAC-d, MAC-c/sh, MAC-ehs, and PHY layers. MAC-d is connected to DTCH, DCCH, PCCH, CCCH, and BCCH. The NodeB stack consists of MAC-ehs, HS-DSCHFP, PHY, and TNL layers. The CRNC/SRNC stack consists of MAC-d, MAC-c/sh, HS-DSCHFP, and TNL layers. MAC-d is connected to DCCH, DTCH, PCCH, CCCH, and BCCH. The interfaces shown are Uu between UE and NodeB, and Iub between NodeB and CRNC/SRNC.](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +Figure 25A: Protocol stack diagram for HS-DSCH configured for UE in Cell\_FACH, Cell\_PCH and URA\_PCH with co-incident Controlling and Serving RNC. The diagram shows three main entities: UE, NodeB, and CRNC/SRNC. The UE stack consists of MAC-d, MAC-c/sh, MAC-ehs, and PHY layers. MAC-d is connected to DTCH, DCCH, PCCH, CCCH, and BCCH. The NodeB stack consists of MAC-ehs, HS-DSCHFP, PHY, and TNL layers. The CRNC/SRNC stack consists of MAC-d, MAC-c/sh, HS-DSCHFP, and TNL layers. MAC-d is connected to DCCH, DTCH, PCCH, CCCH, and BCCH. The interfaces shown are Uu between UE and NodeB, and Iub between NodeB and CRNC/SRNC. + +**Figure 25A: HS-DSCH configured for UE in Cell\_FACH, Cell\_PCH and URA\_PCH: Co-incident Controlling and Serving RNC (FDD and 1.28 Mcps TDD only)** + +[FDD and 1.28 Mcps TDD - Figure 25B shows the protocol model for the HS-DSCH transport channel configured for UE in Cell\_FACH, Cell\_PCH and URA\_PCH, with separate Controlling and Serving RNC. In this case, Iur HS-DSCH Frame Protocol is used to interwork the Flow Control function at the MAC-c at Controlling RNC with the MAC-d at the Serving RNC. Also in this case, Iub HS-DSCH Frame Protocol is used to interwork the MAC-ehs at the Node B with the Flow Control function at the MAC-c at the Controlling RNC.] + +![Figure 25B: Protocol stack diagram for HS-DSCH configured for UE in Cell_FACH, Cell_PCH and URA_PCH with separate Controlling and Serving RNC. The diagram shows four main entities: UE, NodeB, CRNC, and SRNC. The UE stack is identical to Figure 25A. The NodeB stack is identical to Figure 25A. The CRNC stack consists of MAC-c/sh, HS-DSCHFP, and TNL layers. The SRNC stack consists of MAC-d, HS-DSCHFP, and TNL layers. Interfaces shown are Uu (UE to NodeB), Iub (NodeB to CRNC), and Iur (CRNC to SRNC).](4346261cc730a1eb683f35e4ce9deacf_img.jpg) + +Figure 25B: Protocol stack diagram for HS-DSCH configured for UE in Cell\_FACH, Cell\_PCH and URA\_PCH with separate Controlling and Serving RNC. The diagram shows four main entities: UE, NodeB, CRNC, and SRNC. The UE stack is identical to Figure 25A. The NodeB stack is identical to Figure 25A. The CRNC stack consists of MAC-c/sh, HS-DSCHFP, and TNL layers. The SRNC stack consists of MAC-d, HS-DSCHFP, and TNL layers. Interfaces shown are Uu (UE to NodeB), Iub (NodeB to CRNC), and Iur (CRNC to SRNC). + +**Figure 25B: HS-DSCH configured for UE in Cell\_FACH, Cell\_PCH and URA\_PCH: Serving RNC with Separate Controlling and Serving RNC (FDD and 1.28 Mcps TDD only)** + +### 11.2.8 E-DCH Transport Channel + +Figure 26 shows the protocol model for the E-DCH transport channel when the Controlling and Serving RNC are co-incident. [FDD and 1.28 Mcps TDD – The protocol model in Figure 26 is applied for E-DCH configured for UEs in Cell\_DCH.] + +![Figure 26: E-DCH Co-incident Controlling and Serving RNC. This diagram illustrates the protocol stack for the E-DCH transport channel. On the left, the UE (User Equipment) stack consists of DTCH and DCCH at the top, followed by MAC-d, MAC-e/ MAC-es, MAC-i/ MAC-is, and PHY layers. The UE connects to the NodeB via the Uu interface. The NodeB stack includes MAC-e/ MAC-i and EDCH FP at the top, followed by PHY and TNL layers. The NodeB connects to the CRNC/SRNC via the Iub interface. The CRNC/SRNC stack consists of DCCH and DTCH at the top, followed by MAC-d, MAC-es/ MAC-is, EDCH FP, and TNL layers.](9cbc1ebd80813fc36e499f7d70ed6881_img.jpg) + +Figure 26: E-DCH Co-incident Controlling and Serving RNC. This diagram illustrates the protocol stack for the E-DCH transport channel. On the left, the UE (User Equipment) stack consists of DTCH and DCCH at the top, followed by MAC-d, MAC-e/ MAC-es, MAC-i/ MAC-is, and PHY layers. The UE connects to the NodeB via the Uu interface. The NodeB stack includes MAC-e/ MAC-i and EDCH FP at the top, followed by PHY and TNL layers. The NodeB connects to the CRNC/SRNC via the Iub interface. The CRNC/SRNC stack consists of DCCH and DTCH at the top, followed by MAC-d, MAC-es/ MAC-is, EDCH FP, and TNL layers. + +**Figure 26: E-DCH Co-incident Controlling and Serving RNC** + +The E-DCH MAC (MAC-e/MAC-es)/Enhanced E-DCH MAC (MAC-i/MAC-is) entity in the UE transfers MAC-e /MAC-i PDUs to the peer MAC-e/MAC-i entity in the Node B and MAC-es/MAC-is PDUs to the peer MAC-es /MAC-is entity in the RNC using the services of the Physical Layer. + +The E-DCH FP entity adds header information to form a E-DCH FP PDU that is transported to the RNC over a transport bearer. + +An Interworking Function (IWF) in the Node B interworks the E-DCH frame received by the MAC-e/MAC-i entity into the E-DCH Frame Protocol (E-DCH FP) entity. E-DCH scheduling is performed by MAC-e/MAC-i in the Node B and reordering is performed by MAC-es/MAC-is in the RNC. + +Figure 27 shows the protocol model for the E-DCH transport channel with separate Controlling and Serving RNC. [FDD and 1.28 Mcps TDD – The protocol model in Figure 27 is applied for E-DCH configured for UEs in Cell\_DCH.] In this case, the CRNC does not have any user plane RNL function for the E-DCH. MAC-es/MAC-is in SRNC is located directly above MAC-e/MAC-is in Node B, i.e. in the E-DCH user plane RNL, the SRNC is directly connected to the Node B, thus bypassing the CRNC user plane RNL. The CRNC performs only user plane TNL functions. + +![Figure 27: E-DCH: Separate Controlling and Serving RNC. The diagram illustrates the protocol stack across UE, NodeB, CRNC, and SRNC. UE stack: DTCH/DCCH inputs to MAC-d, then MAC-es/MAC-e and MAC-is/MAC-i, then PHY. NodeB stack: PHY and MAC-e/MAC-i on the Uu side; E-DCH FP and TNL on the Iub side. CRNC stack: Two TNL blocks connected by a bridge. SRNC stack: TNL, E-DCH FP, MAC-es/MAC-is, and MAC-d leading to DCCH/DTCH outputs. Interfaces: Uu between UE and NodeB, Iub between NodeB and CRNC, Iur between CRNC and SRNC.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +Figure 27: E-DCH: Separate Controlling and Serving RNC. The diagram illustrates the protocol stack across UE, NodeB, CRNC, and SRNC. UE stack: DTCH/DCCH inputs to MAC-d, then MAC-es/MAC-e and MAC-is/MAC-i, then PHY. NodeB stack: PHY and MAC-e/MAC-i on the Uu side; E-DCH FP and TNL on the Iub side. CRNC stack: Two TNL blocks connected by a bridge. SRNC stack: TNL, E-DCH FP, MAC-es/MAC-is, and MAC-d leading to DCCH/DTCH outputs. Interfaces: Uu between UE and NodeB, Iub between NodeB and CRNC, Iur between CRNC and SRNC. + +**Figure 27: E-DCH: Separate Controlling and Serving RNC** + +[FDD and 1.28 Mcps TDD - Figure 28 shows the protocol model for the E-DCH transport channel configured for UE in Cell\_FACH for CCCH transmission. + +The E-DCH MAC (MAC-i/MAC-is) entity in the UE transfers MAC-i and MAC-is PDUs to the peer MAC-i in the Node B and and MAC-is entity in the CRNC. + +The E-DCH FP entity adds header information to form a E-DCH FP PDU that is transported to the RNC over a transport bearer.] + +![Figure 28: E-DCH configured for UE in Cell_FACH(CCCH case)(FDD and 1.28 Mcps TDD only). The diagram shows the protocol stack for CCCH transmission. UE stack: CCCH input to MAC-c, then MAC-is/MAC-i, then PHY. NodeB stack: PHY and MAC-i on the Uu side; EDCH FP and TNL on the Iub side. CRNC stack: TNL, EDCH FP, MAC-is, and MAC-c leading to CCCH output. Interfaces: Uu between UE and NodeB, Iub between NodeB and CRNC.](78e846f2858d131dc5a4dcbabcca1e4d_img.jpg) + +Figure 28: E-DCH configured for UE in Cell\_FACH(CCCH case)(FDD and 1.28 Mcps TDD only). The diagram shows the protocol stack for CCCH transmission. UE stack: CCCH input to MAC-c, then MAC-is/MAC-i, then PHY. NodeB stack: PHY and MAC-i on the Uu side; EDCH FP and TNL on the Iub side. CRNC stack: TNL, EDCH FP, MAC-is, and MAC-c leading to CCCH output. Interfaces: Uu between UE and NodeB, Iub between NodeB and CRNC. + +**Figure 28: E-DCH configured for UE in Cell\_FACH(CCCH case)(FDD and 1.28 Mcps TDD only)** + +[FDD and 1.28 Mcps TDD - Figure 29 shows the protocol model for the E-DCH transport channel configured for UE in Cell\_FACH for DCCH and DTCH transmission when the Controlling and Serving RNC are co-incident. + +The E-DCH MAC (MAC-i/MAC-is) entity in the UE transfers MAC-i PDUs to the peer MAC-i entity in the Node B and MAC-is PDUs to the peer MAC-is entity in the RNC using the services of the Physical Layer. + +The E-DCH FP entity adds header information to form an E-DCH FP PDU that is transported to the RNC over a transport bearer. + +An Interworking Function (IWF) in the Node B interworks the E-DCH frame received by the MAC-i entity into the E-DCH Frame Protocol (E-DCH FP) entity. E-DCH scheduling is performed by MAC-i in the Node B and reordering is performed by MAC-is in the RNC.] + +![Figure 29: Protocol stack diagram for E-DCH in Cell_FACH (DCCH/DTCH case) with co-incident controlling and serving RNC. It shows three main entities: UE, NodeB, and CRNC/SRNC. The UE stack has DTCH and DCCH pointing to MAC-d, which points to MAC-is/MAC-i, which points to PHY. The NodeB stack has MAC-i and EDCH FP pointing to PHY and TNL respectively. The CRNC/SRNC stack has MAC-d pointing to MAC-is, which points to EDCH FP, which points to TNL. Interfaces are labeled Uu between UE and NodeB, and Iub between NodeB and CRNC/SRNC.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +Figure 29: Protocol stack diagram for E-DCH in Cell\_FACH (DCCH/DTCH case) with co-incident controlling and serving RNC. It shows three main entities: UE, NodeB, and CRNC/SRNC. The UE stack has DTCH and DCCH pointing to MAC-d, which points to MAC-is/MAC-i, which points to PHY. The NodeB stack has MAC-i and EDCH FP pointing to PHY and TNL respectively. The CRNC/SRNC stack has MAC-d pointing to MAC-is, which points to EDCH FP, which points to TNL. Interfaces are labeled Uu between UE and NodeB, and Iub between NodeB and CRNC/SRNC. + +**Figure 29: E-DCH configured for UE in Cell\_FACH (DCCH/DTCH case) :Co-incident Controlling and Serving RNC (FDD and 1.28 Mcps TDD only)** + +[FDD and 1.28 Mcps TDD - Figure 30 shows the protocol model for the E-DCH transport channel configured for UE in Cell\_FACH for DCCH and DTCH transmission, with separate Controlling and Serving RNC. + +An Interworking Function (IWF) in the CRNC interworks the E-DCH data frame received from Node B into the Iur E-DCH Frame Protocol (E-DCH FP) entity.] + +![Figure 30: Protocol stack diagram for E-DCH in Cell_FACH (DCCH/DTCH case) with separate controlling and serving RNC. It shows four main entities: UE, NodeB, CRNC, and SRNC. The UE stack is the same as in Figure 29. The NodeB stack has MAC-i pointing to PHY and E-DCH FP pointing to TNL. The CRNC stack has two E-DCH FP entities pointing to TNL. The SRNC stack has MAC-d pointing to MAC-is, which points to E-DCH FP, which points to TNL. Interfaces are labeled Uu between UE and NodeB, Iub between NodeB and CRNC, and Iur between CRNC and SRNC.](adc59ed6840bcb2d392ea323abfccedc_img.jpg) + +Figure 30: Protocol stack diagram for E-DCH in Cell\_FACH (DCCH/DTCH case) with separate controlling and serving RNC. It shows four main entities: UE, NodeB, CRNC, and SRNC. The UE stack is the same as in Figure 29. The NodeB stack has MAC-i pointing to PHY and E-DCH FP pointing to TNL. The CRNC stack has two E-DCH FP entities pointing to TNL. The SRNC stack has MAC-d pointing to MAC-is, which points to E-DCH FP, which points to TNL. Interfaces are labeled Uu between UE and NodeB, Iub between NodeB and CRNC, and Iur between CRNC and SRNC. + +**Figure 30: E-DCH configured for UE in Cell\_FACH (DCCH/DTCH case): Separate Controlling and Serving RNC (FDD and 1.28 Mcps TDD only)** + +# 12 UTRAN Performance Requirements + +## 12.1 UTRAN delay requirements + +Void. + +# --- Annex A (informative): SPID ranges and mapping of SPID values to cell reselection and inter-RAT/inter frequency handover priorities + +Ranges of SPID (Subscriber Profile ID for RAT/Frequency Priority) values, respectively Operator Specific and Reference values and the mapping at RNS of Reference SPID values to cell reselection and inter-RAT/inter frequency handover priorities are defined in TS 36.300 [35]. + +# Annex A2 (Informative): Deployment of Extended Identifiers + +## A2.1 RNC Sizing Changes + +### A2.1.1 U-RNTI Considerations + +The U-RNTI of 32 bits is normally divided in the following way: + +![](db5deafdae53dbc7d5972957f708c691_img.jpg) + +| | | +|----------------|---------------| +| RNC-ID 12 bits | S-RNTI 20bits | +|----------------|---------------| + +**Figure A2.1.1.1: RNC Side, normal split of U-RNTI in RNC-ID and S-RNTI** + +When a large number of small RNCs were considered (HSPA+ cells), then extended RNC-ID was added, this took bits from the S-RNTI reducing this to 16bits thus: + +![](e3eebf9854831ba50eca8b26c468f65e_img.jpg) + +| | | +|----------------|---------------| +| RNC-ID 16 bits | S-RNTI 16bits | +|----------------|---------------| + +**Figure A2.1.1.2: RNC-Side, split of U-RNTI in RNC-ID and S-RNTI in the case of many small RNCs deployed** + +Whilst this limited the S-RNTIs available to a RNC to 65k, as the RNCs were smaller this was acceptable, and allowed the addressing of 65k RNCs (per PLMN). + +Also related is the cell identity, containing the cell id and the RNC-ID + +![](1230eaa9d75a09d7e7b8509931e9190e_img.jpg) + +| | | +|----------------|----------------| +| RNC-ID 12 bits | Cell id 16bits | +|----------------|----------------| + +**Figure A2.1.1.3: RNC Side, normal split of Cell identity in RNC-ID and Cell id.** + +Or for extended RNC-ID + +![](6069ca3ced0728f1947d195c57bb0d5f_img.jpg) + +| | | +|----------------|----------------| +| RNC-ID 16 bits | Cell id 12bits | +|----------------|----------------| + +**Figure A2.1.1.4: RNC Side, split of Cell identity in RNC-ID and CELL I in case of extended RNC-ID (many small RNCs deployed)** + +Rules are applied to handle extended RNC-ID in relation to the addressing of RNCs in Clause A2.2. + +For extending the S-RNTI to handle larger number of UEs. + +The UE side is unchanged: + +![](32149dde9c4281699916b0b9518c1e3f_img.jpg) + +| | | +|----------------|---------------| +| RNC-ID 12 bits | S-RNTI 20bits | +|----------------|---------------| + +**Figure A2.1.1.5: UE Side, Normal split of U-RNTI in RNC-ID and S-RNTI** + +The RAN side uses a shorter RNC-ID and extended S-RNTI to give 4x increase in the number of UEs that can be supported on a RNC. + +![](f87d644b84c7f7c79ba51f388161a71a_img.jpg) + +| | | +|----------------|---------------| +| RNC-ID 10 bits | S-RNTI 22bits | +|----------------|---------------| + +**Figure A2.1.1.6: UE Side, Split of U-RNTI in RNC-ID and S-RNTI in case of large number of UEs deployed.** + +Rules and methods to achieve this extension are in Clause A2.1.2 and A2.1.3. + +### A2.1.2 Extend S-RNTI and reduce RNC-ID: Solution 1 + +In this solution the S-RNTI is extended by 2 bits and the RNC-ID reduced by 2 bits. This gives an increased number of UE supported to $2^{22}$ , but a reduced number of RNC-IDs available at 1024 ( $2^{10}$ ). + +UE Side + +![](3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg) + +| | | +|----------------|---------------| +| RNC-ID 12 bits | S-RNTI 20bits | +|----------------|---------------| + +**Figure A2.1.2.1: UE Side, Normal split of U-RNTI in RNC-ID and S-RNTI** + +RAN Side + +![](dc37a040cf9e2add7488c7c37cbf3687_img.jpg) + +| | | +|----------------|---------------| +| RNC-ID 10 bits | S-RNTI 22bits | +|----------------|---------------| + +**Figure A2.1.2.2: RNC Side, Extended S-RNTI and reduced RNC-ID ranges** + +Although this approach increases by 4 the number of SRNTIs available, new rules are needed to handle addressing large RNCs with 10bit RNC-IDs. It is also incompatible with extended RNC-ID. The co-existence of extended RNC-ID and extended S-RNTI in one network may not be possible or the rules would become exceedingly complex. + +#### Reallocation of U-RNTI to allow more S-RNTI + +Initially we look at the current restrictions in the standards. + +In TS25.331 Section 8.1.1.6.5 (System Information Block type 5 and 5bis), UE checks the 12bits of RNC-ID for performing URA update. Therefore the UE is using the 12bits of the RNC-Id in the U\_RNTI to check for change in RNC and perform URA update. + +- 2> if the UE is in CELL\_PCH or URA\_PCH state: + - 3> for FDD and for 1.28 Mcps TDD, if the UE supports HS-DSCH reception in CELL\_PCH and URA\_PCH state; and + - 3> if IE "HS-DSCH paging system information" is included: + - 4> if this IE is not currently stored; and + - 4> if the value of the IE "SRNC identity" in the variable U\_RNTI is not equal to the 12 MSBs of the received IE "Cell identity" in System Information Block type 3; and + - 4> if the UE is in URA\_PCH state: + - 5> initiate the URA update procedure as specified in subclause 8.3.1, using the cause "periodic URA update". + +Due to this, RNC with Extended S-RNTI implementation would make sure to design the U-RNTI, to avoid unnecessary URA updates. This can be done by ensuring that the 2 MSB of the extended the S-RNTI are the same for UEs in the same area. + +### A2.1.3 Pooled RNCs: Solution 2 + +In this solution a large RNC consists of 4 (or 2) RNCs each with a 12 bit RNC-ID. This could be considered a version of Solution 1, but here the large RNC is handled as a single RNC where the 2 LSBs of the RNC-ID are zero. + +UE Side + +![](c02e1ac41cfdcb36d2fe7c86a5c5d5a9_img.jpg) + +| | | +|----------------|---------------| +| RNC-ID 12 bits | S-RNTI 20bits | +|----------------|---------------| + +**Figure A2.1.3.1: UE Side, Normal split of U-RNTI in RNC-ID and S-RNTI** + +RAN Side + +![Diagram of RNC-ID structure on the RNC side. It shows a 32-bit word split into three parts: RNC-ID (10 bits), R (1 bit), and S-RNTI (20 bits).](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +| | | | +|----------------|--------|----------------| +| RNC-ID 10 bits | R
x | S-RNTI 20 bits | +|----------------|--------|----------------| + +Diagram of RNC-ID structure on the RNC side. It shows a 32-bit word split into three parts: RNC-ID (10 bits), R (1 bit), and S-RNTI (20 bits). + +**Figure A2.1.3.1: RNC Side, RNC-ID split into extended RNC-ID and sub-RNC indicator.** + +On the RAN side only the 10 MSBs are used for routing/addressing RNCs. Large RNC RNC-IDs are identified by RNC ID range and the 2 LSBs of RNC-ID being zero. CN routing and RNC routing would need updating to ensure that the mobility to the correct RNC occurs based on 10 bit RNC-ID. Other non-pooled RNCs will be routed in the normal way. This has perhaps more impact on the network than solution 1 but the large RNC would support the extended number of UEs, as it acts like 4 RNCs. + +## A2.2 RNC ID Extension + +The problem of insufficient RNC ID number space was identified and it was agreed to extend the range of the RNC ID. As a solution for the extension of the number space, it was agreed to increase the bit length of the RNC-ID from 12bits to 16bits by introducing a new ID with 16bits-length , and to introduce an *Extended RNC ID* IE into the relevant specifications. While the maximum number of RNCs within one PLMN in the current specification is 4096, the introduction of the new IE allows a maximum of 65536 (4096:legacy RNC ID + 61440: extended RNC-ID) RNCs to be deployed in one PLMN in the future. + +### A2.2.1 Solution for RNC-ID Extension + +The Extended RNC-ID is only introduced into the network internal signalling specifications, e.g. RANAP between RNC and CN and does not require any changes to the RRC protocol so that legacy UEs can operate in an RNS which is configured to use an extended RNC ID. + +This is possible by partitioning the 32bits of the U-RNTI in a different manner in RNS which is configured to use the extended RNC-ID. Thus some bits of the S-RNTI (20bits) part of the U-RNTI are used to extend the SRNC-ID part in the RNS using the extended RNC-ID. Therefore, the extension for the SRNC-ID in the network is not visible for the UE. As specified today, the UE always treats the 32 bit together as U-RNTI. + +![Diagram showing the interpretation of U-RNTI on the UE side and RAN side. On the UE side, it is split into SRNC identity (12 bits) and S-RNTI (20 bits). On the RAN side, it is split into SRNC identity (16 bits) and S-RNTI (16 bits).](b7fd98a4fcc4990a613abfc31c5bdb5e_img.jpg) + +**UE Side** + +| | | +|--------------------------|-------------------| +| SRNC identity
12 bits | S-RNTI
20 bits | +|--------------------------|-------------------| + +**RAN Side** + +| | | +|--------------------------|-------------------| +| SRNC identity
16 bits | S-RNTI
16 bits | +|--------------------------|-------------------| + +Diagram showing the interpretation of U-RNTI on the UE side and RAN side. On the UE side, it is split into SRNC identity (12 bits) and S-RNTI (20 bits). On the RAN side, it is split into SRNC identity (16 bits) and S-RNTI (16 bits). + +**Figure A2.2.1.1: Interpretation of U-RNTI in UE side and RAN side is configured to use the extended RNC ID** + +As the same logic is applied for Cell Identity, 4MSB of the 16bit C-ID are used as an extension of RNC-ID. Thus under the RNC using the extended RNC-ID, the bits available for the C-ID are reduced to 12bits (4096). + +![](7ed5d5770331f31ade15439a21c31425_img.jpg) + +**UE Side** + +| | | +|--------------------------|--------------------| +| SRNC identity
12 bits | Cell-ID
16 bits | +|--------------------------|--------------------| + +**RAN Side** + +| | | +|--------------------------|--------------------| +| SRNC identity
16 bits | Cell-ID
12 bits | +|--------------------------|--------------------| + +**Figure A2.2.1.2: Interpretation of Cell identity (= UC-ID) in UE side and RAN side is configured to use the extended RNC ID** + +The number of UEs and cells in one RNS using the extended RNC-ID are different from the one using the current RNC ID as shown in the table below since the 4bits used for the S-RNTI and Cell ID are used as part of extended RNC-ID in the RNS. + +| | Current RNC-ID | Extended RNC-ID | +|---------------------------------------------------|-----------------------|------------------------| +| The number of UEs in RNS | 1 048 576 | 65 536 | +| The number of UEs for Inter-RAT HO at once in RNS | 1 024 | 64 | +| The number of cells in RNS | 65 536 | 4 096 | + +### A2.2.2 Rules for Configuration + +There are some limitations for configuring network when the extended RNC-ID scheme is used. The network configuration shall follow all four rules as stated below together. + +#### Explanation of terms + +**Legacy RNC/CN:** RNC/CN do not comprehend/support the extended RNC-ID IE/Scheme, e.g. Pre-Rel7 RNC/CN. + +**Upgraded RNC/CN:** RNC/CN comprehend/support the extended RNC-ID IE/Scheme and can distinguish which RNC-ID scheme are used in the received message or sending message based on the stored configuration data. + +##### Rule1): + +In case relocation needs to be supported to/from an RNC using the extended RNC-ID, it is recommended to connect the source and target RNCs to the same upgraded CN to reduce the number of upgraded CN. In case CN cannot be upgraded, it is recommended to use legacy RNC-ID under that CN. (Example in Figure A2.2.2.1). + +##### Rule2): + +Not configure the Iur interface connection between legacy RNC and upgraded RNC using the extended RNC-ID. + +##### Rule3): + +In case RNCs with legacy RNC-ID and RNCs with extended RNC-ID co-exist in the network, configure the legacy RNC-ID so that legacy RNC-ID will not be the same as the 12 bit of MSB of any of extended RNC-ID to which the legacy RNC may have Iur connection. (See the Figure A2.2.2.3 and A2.2.2.4). + +##### Rule4): + +In case a URA spanned over multiple RNCs with extended RNC-ID and the RNCs have different capability on HS-DSCH reception in URA\_PCH state, the RNCs capable of HS-DSCH reception in URA\_PCH state shall not have the same 12bit MSB in their extended RNC-ID compared to the RNCs not capable of HS-DSCH reception in URA\_PCH. (See Figures A2.2.2.5 and A2.2.2.6). + +#### Depiction of Configuration Rules + +![Diagram showing network configuration where only CN #1 needs an upgrade. CN #1 is connected to RAN 1, 2, and 3. CN #2 is connected to RAN 4. RAN 1 and 4 use 12-bit RNC-ID (light blue), while RAN 2 and 3 use 16-bit RNC-ID (pink). Arrows show data flow from CN #1 to RAN 2 and 3, which then flow to RAN 4. Some arrows are marked with red X's, indicating incompatibility without upgrade.](3337af75dfee8af7687b4f49914d6c93_img.jpg) + +Only CN #1 needs to be upgraded to understand 16bit RNC-ID + +RAN 1 and 4 with 12-bit RNC-ID      PS only RAN 2 and 3 with 16-bit RNC-ID + +Diagram showing network configuration where only CN #1 needs an upgrade. CN #1 is connected to RAN 1, 2, and 3. CN #2 is connected to RAN 4. RAN 1 and 4 use 12-bit RNC-ID (light blue), while RAN 2 and 3 use 16-bit RNC-ID (pink). Arrows show data flow from CN #1 to RAN 2 and 3, which then flow to RAN 4. Some arrows are marked with red X's, indicating incompatibility without upgrade. + +Figure A2.2.2.1: Configuration example for Rule 1 and 2 + +![Diagram showing network configuration where both CN #1 and CN #2 need upgrades. CN #1 is connected to RAN 1, 2, and 3. CN #2 is connected to RAN 4. RAN 1 and 4 use 12-bit RNC-ID (light blue), while RAN 2 and 3 use 16-bit RNC-ID (pink). Arrows show data flow from CN #1 and CN #2 to RAN 4. Some arrows are marked with red X's, indicating incompatibility without upgrade.](1033dc9fde75540d224c907681b1b7aa_img.jpg) + +CN #1 and CN #2 need to be upgraded to understand 16bit RNC-ID + +RAN 1 and 4 with 12-bit RNC-ID      PS only RAN 2 and 3 with 16-bit RNC-ID + +Diagram showing network configuration where both CN #1 and CN #2 need upgrades. CN #1 is connected to RAN 1, 2, and 3. CN #2 is connected to RAN 4. RAN 1 and 4 use 12-bit RNC-ID (light blue), while RAN 2 and 3 use 16-bit RNC-ID (pink). Arrows show data flow from CN #1 and CN #2 to RAN 4. Some arrows are marked with red X's, indicating incompatibility without upgrade. + +Figure A2.2.2.2: Configuration example for Rule 1 and 2. + +![Diagram of a problematic configuration example (Figure A2.2.2.3)](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +This diagram illustrates a problematic configuration. At the top, an orange box represents 'RNC A (Upgraded)' with 'RNC ID: 00B'. Below it, three grey boxes represent 'eHSPA Node B3' (RNC ID: 00A1), 'eHSPA Node B' (RNC ID: 00A2), and 'eHSPA Node B1' (RNC ID: 00B1). RNC A is connected to all three nodes via 'Iur' links. A red line labeled 'RRC Connection' connects RNC A to a User Equipment (UE) icon. A blue arrow labeled 'Cell/URA Update U RNTI: 00B1xxxx' points from the UE to Node B. A blue arrow points from Node B to a table titled 'RNC-ID Table:'. The table contains: 'RNC1: 00B', 'eHSPA NB1: 00B1', and 'eHSPA NB3: 00A1'. A red question mark is placed near Node B1. Below the UE, the text 'SRNC-ID: 00B' and 'S-RNTI: 1xxxx' is shown. + +Diagram of a problematic configuration example (Figure A2.2.2.3) + +Figure A2.2.2.3: Problematic configuration example (does not follow Rule3) + +![Diagram of a configuration example for Rule3 (Figure A2.2.2.4)](28085f681b9fff76a53c5b8b32338ee1_img.jpg) + +This diagram illustrates a configuration example for Rule3. At the top, an orange box represents 'RNC A (Upgraded)' with 'RNC ID: 00B'. Below it, three grey boxes represent 'eHSPA Node B3' (RNC ID: 00A1), 'eHSPA Node B2' (RNC ID: 00A2), and 'eHSPA Node B1' (RNC ID: 00B1). RNC A is connected to Node B3 and Node B2 via 'Iur' links. A red line labeled 'RRC Connection' connects RNC A to a UE icon. A blue arrow labeled 'Cell/URA Update U RNTI: 00B1xxxx' points from the UE to Node B2. A blue arrow points from Node B2 to a table titled 'RNC-ID Table:'. The table contains: 'RNC1: 00B' and 'eHSPA NB3: 00A1'. A dashed line labeled 'No Iur and not neighbouring' connects Node B2 and Node B1. Below the UE, the text 'SRNC-ID: 00B' and 'S-RNTI: 1xxxx' is shown. A text box with a large 'X' over a UE icon states: 'No case that UE anchored by eHSPA Node B1 moves to cell under the Node B2'. Below this, another 'SRNC-ID: 00B' and 'S-RNTI: 1xxxx' label is present. + +Diagram of a configuration example for Rule3 (Figure A2.2.2.4) + +Figure A2.2.2.4: Configuration example for Rule3 + +![Diagram of a problematic configuration where Node B2 (non-capable) pages Node B1 and B3 (capable). The UE fails to send a URA update to Node B3 because of conflicting RNC IDs.](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +The diagram shows three eHSPA Node Bs connected to a common URA (User Registration Area) represented by an orange oval. + - **eHSPA Node B1**: RNC ID 00A1, Capable of Enhanced-FACH. + - **eHSPA Node B2**: RNC ID 00A2, Non Capable of Enhanced-FACH SRNC for UE1. + - **eHSPA Node B3**: RNC ID 00A3, Capable of Enhanced-FACH. + Node B2 sends a "Paging Request" to Node B1 and Node B3 (indicated by arrows with question marks). Below, a UE is shown moving from Node B2's area towards Node B3. A blue arrow labeled "RRC" points from the URA to the UE. A dashed blue arrow points from the UE back towards Node B3 with the text "UE does NOT send URA Update". + +Diagram of a problematic configuration where Node B2 (non-capable) pages Node B1 and B3 (capable). The UE fails to send a URA update to Node B3 because of conflicting RNC IDs. + +**Figure A2.2.2.5 Problematic configuration example (does not follow Rule4)** + +![Diagram of a correct configuration for Rule4 where Node B2 (non-capable) has a different RNC ID prefix than Node B3 (capable), allowing the UE to trigger a URA update.](848073118eebfdbfdb9a60e3923fe0b3_img.jpg) + +The diagram shows a corrected configuration with three eHSPA Node Bs: + - **eHSPA Node B1**: RNC ID 00A1, Capable of Enhanced-FACH. + - **eHSPA Node B2**: RNC ID 00B1, Non Capable of Enhanced-FACH. + - **eHSPA Node B3**: RNC ID 00A2, Capable of Enhanced-FACH. + Node B2 sends a "Paging Request" to Node B1 and Node B3. A UE moves from Node B2 to Node B3. A blue arrow labeled "RRC" points from the URA to the UE. A blue arrow labeled "URA Update" points from the UE to Node B3. A red arrow labeled "RRC Release" points from Node B3 back to the UE. + +Diagram of a correct configuration for Rule4 where Node B2 (non-capable) has a different RNC ID prefix than Node B3 (capable), allowing the UE to trigger a URA update. + +**Figure A2.2.2.6 Configuration example for Rule4** + +### A2.2.3 Configuration Example + +The RNC ID configuration example below is following the rules listed in A2.2.2 and showing the configuration in Figure A2.2.2.2 in a large scale. + +![Diagram showing a network of cells (NB (f1) and eNB (f2)) connected to three RNCs: RNC_A (00B), RNC_B (01B), and RNC_C (00A). The diagram includes labels for RNS_A, RNS_B, and RNS_C, and a legend for Overlay cell (cyan) and Non-Overlay cell (purple).](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +The diagram illustrates a network of cells and their connections to Radio Network Controllers (RNCs). The cells are represented by hexagons, and the RNCs are represented by rectangular boxes. The connections between cells and RNCs are labeled 'Iub' and 'Iur'. + +**Legend:** + +- Overlay cell (Cyan hexagon) +- Non-Overlay cell (Purple hexagon) + +**RNC\_A (00B) (Upgraded to Rel7)** is connected to the top network segment (RNS\_A). It is connected via 'Iub' interfaces to several cells, including eNB (f2) 00A1, eNB (f2) 00A2, eNB (f2) 00A3, eNB (f2) 00A4, eNB (f2) 00C1, eNB (f2) 00C2, eNB (f2) 00C3, and eNB (f2) 00C4. It is also connected via 'Iur' interfaces to NB (f1) cells. + +**RNC\_B (01B) (Upgraded)** is connected to the middle network segment (RNS\_B). It is connected via 'Iub' interfaces to NB (f1) cells and via 'Iur' interfaces to other cells. + +**RNC\_C (00A) (Upgraded)** is connected to the bottom network segment (RNS\_C). It is connected via 'Iub' interfaces to eNB (f2) 00B1, eNB (f2) 00B2, eNB (f2) 00B3, and eNB (f2) 00B4. It is also connected via 'Iur' interfaces to NB (f1) cells. + +The network segments are labeled RNS\_A, RNS\_B, and RNS\_C. The cells are labeled NB (f1) and eNB (f2) with specific IDs like 00A1, 00A2, 00A3, 00A4, 00C1, 00C2, 00C3, 00C4, 00B1, 00B2, 00B3, 00B4, 00A5, and 00A6. + +Diagram showing a network of cells (NB (f1) and eNB (f2)) connected to three RNCs: RNC\_A (00B), RNC\_B (01B), and RNC\_C (00A). The diagram includes labels for RNS\_A, RNS\_B, and RNS\_C, and a legend for Overlay cell (cyan) and Non-Overlay cell (purple). + +Figure A2.2.3.1: Valid RNC ID Configuration Example + +# Annex B (informative): Change history + +| Change history | | | | | | +|----------------|---------|---------------------------------|-----------|-------------|--------------------------------------------------------| +| TSG RAN# | Version | CR | Tdoc RAN | New Version | Subject/Comment | +| RAN_05 | - | - | - | 3.0.0 | Approved at TSG RAN #5 and placed under Change Control | +| RAN_06 | 3.0.0 | - | RP-99735 | 3.1.0 | Approved at TSG RAN #6 | +| RAN_06 | 3.0.0 | - | RP-99736 | 3.1.0 | Approved at TSG RAN #6 | +| RAN_06 | 3.0.0 | - | RP-99737 | 3.1.0 | Approved at TSG RAN #6 | +| RAN_06 | 3.0.0 | - | RP-99738 | 3.1.0 | Approved at TSG RAN #6 | +| RAN_07 | 3.1.0 | - | RP-000073 | 3.2.0 | Approved at TSG RAN #7 | +| RAN_08 | 3.2.0 | - | RP-000231 | 3.3.0 | Approved at TSG RAN #8 | +| RAN_09 | 3.3.0 | 013
014
015
016
017 | RP-000370 | 3.4.0 | Approved at TSG RAN #9 | +| RAN_10 | 3.4.0 | 018
019 | RP-000607 | 3.5.0 | Approved at TSG RAN #10 | +| RAN_11 | 3.5.0 | 020
021 | RP-010107 | 3.6.0 | Approved at TSG RAN #11 | + +| Change history | | | | | | | | +|----------------|-------|-----------|---------------------|-----|---------------------------------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| March 01 | 11 | RP-010164 | 23 | 1 | Approved at TSG RAN #11 and placed under Change Control | - | 4.0.0 | +| June 01 | 12 | RP-010370 | 025,
028,
032 | | Approved at TSG RAN #12 | 4.0.0 | 4.1.0 | +| June 01 | 12 | RP-010389 | 026,
029 | | Approved at TSG RAN #12 | 4.0.0 | 4.1.0 | +| June 01 | 12 | RP-010403 | 030 | | Approved at TSG RAN #12 and placed under Change Control | 4.1.0 | 5.0.0 | +| 09/2001 | 13 | RP-010575 | 033 | | Uplink power control for LCR TDD | 5.0.0 | 5.1.0 | +| 09/2001 | 13 | RP-010575 | 038 | | Clarification of coordinated DCHs | 5.0.0 | 5.1.0 | +| 03/2002 | 15 | RP-020221 | 046 | | New UE identifier for MAC-c/sh multiplexing for DSCH | 5.1.0 | 5.2.0 | +| 03/2002 | 15 | RP-020189 | 044 | 2 | Introduction of IP Transport in UTRAN | 5.1.0 | 5.2.0 | +| 03/2002 | 15 | RP-020190 | 039 | 2 | HSDPA Additions for REL-5 | 5.1.0 | 5.2.0 | +| 03/2002 | 15 | RP-020195 | 045 | 1 | NNSF Functional Description | 5.1.0 | 5.2.0 | +| 06/2002 | 16 | RP-020422 | 047 | | HSDPA-related changes | 5.2.0 | 5.3.0 | +| 06/2002 | 16 | RP-020421 | 048 | | Corrections on ATM-IP interoperability scenarios | 5.2.0 | 5.3.0 | +| 06/2002 | 16 | RP-020399 | 051 | | New UE identifier for Shared Channel handling for TDD DSCH/USCH | 5.2.0 | 5.3.0 | +| 06/2002 | 16 | RP-020421 | 052 | | Introduction of IP transport in UTRAN | 5.2.0 | 5.3.0 | +| 06/2002 | 16 | RP-020421 | 053 | 2 | Independence of RNL and TNL | 5.2.0 | 5.3.0 | +| 09/2002 | 17 | RP-020605 | 055 | 1 | Clarification on ALCAP Identifiers | 5.3.0 | 5.4.0 | +| 09/2002 | 17 | RP-020627 | 056 | 1 | Introduction of lur-g | 5.3.0 | 5.4.0 | +| 09/2002 | 17 | RP-020625 | 057 | 1 | Introduction of the Access Control Function: SNA | 5.3.0 | 5.4.0 | +| 09/2002 | 17 | RP-020628 | 059 | | Introduction of HS-DSCH RNTI in TS25.401 | 5.3.0 | 5.4.0 | +| 12/2002 | 18 | RP-020750 | 062 | | Definition of URA | 5.4.0 | 5.5.0 | +| 12/2002 | 18 | RP-020764 | 064 | 1 | Corrections to the SNA Access Control Function | 5.4.0 | 5.5.0 | +| 03/2003 | 19 | RP-030084 | 065 | | CR on revising the definition of SAS to support all REL-4 UE positioning methods | 5.5.0 | 6.0.0 | +| 06/2003 | 20 | RP-030317 | 068 | 1 | Correction to HS-DSCH transport in case of SRNC not coincident with DRNC and without flow control in the DRNC | 6.0.0 | 6.1.0 | +| 12/2003 | 22 | RP-030675 | 076 | 1 | NAS/AS issue for shared networks in connected mode | 6.1.0 | 6.2.0 | +| 06/2004 | 24 | RP-040182 | 084 | 1 | Introduction of Iu and Iur support of Network Assisted Cell Change from UTRAN to GERAN | 6.2.0 | 6.3.0 | +| 06/2004 | 24 | RP-040254 | 086 | | Completion of the REL-5 IP Transport WI | 6.2.0 | 6.3.0 | +| 09/2004 | 25 | RP-040303 | 087 | 1 | Introduction of Iuant into UTRAN architecture for control of RET Antennas | 6.3.0 | 6.4.0 | +| 09/2004 | 25 | RP-040297 | 091 | | Terminology correction of IP ALCAP CR | 6.3.0 | 6.4.0 | +| 12/2004 | 26 | RP-040439 | 92 | | Support of MOCN and GWCN configurations in UTRAN | 6.4.0 | 6.5.0 | +| 12/2004 | 26 | RP-040440 | 94 | 1 | Introduction of E-DCH in 25.401 | 6.4.0 | 6.5.0 | +| 12/2004 | 26 | RP-040437 | 95 | 1 | CR for Introducing MBMS in 25.401 | 6.4.0 | 6.5.0 | +| 06/2005 | 28 | RP-050225 | 97 | | Feature Cleanup: Removal of CPCH | 6.5.0 | 6.6.0 | + +| | | | | | | | | +|---------|-------|-----------|-----|---|----------------------------------------------------------------------------------|--------|--------| +| 06/2005 | 28 | RP-050222 | 99 | | Feature clean-up: Removal of DSCH (FDD mode) | 6.5.0 | 6.6.0 | +| 09/2005 | 29 | RP-050435 | 101 | | E-DCH Protocol Model | 6.6.0 | 6.7.0 | +| 03/2006 | 31 | RP-060072 | 100 | 2 | Enabling the Providing of Velocity | 6.7.0 | 7.0.0 | +| 03/2006 | 31 | RP-060073 | 102 | 1 | Introduction of 7.68Mcps TDD option | 6.7.0 | 7.0.0 | +| 09/2006 | 33 | RP-060511 | 105 | | Introduction of 3.84 Mcps and 7.68Mcps TDD Enhanced Uplink | 7.0.0 | 7.1.0 | +| 09/2006 | 33 | RP-060499 | 107 | 2 | MBMS Transport Identifiers | 7.0.0 | 7.1.0 | +| 12/2006 | 34 | RP-060698 | 109 | 1 | Delete reference to "MBMS UTRAN Cell Group Identifier" | 7.1.0 | 7.2.0 | +| 12/2006 | 34 | RP-060837 | 110 | 1 | Consistency of Specification Notations | 7.1.0 | 7.2.0 | +| 03/2007 | 35 | RP-070058 | 111 | | Introduction of TMA | 7.2.0 | 7.3.0 | +| 03/2007 | 35 | RP-070062 | 112 | | Introduction of 1.28 Mcps TDD Enhanced Uplink | 7.2.0 | 7.3.0 | +| 06/2007 | 36 | RP-070328 | 113 | 2 | Introduction of Enhanced Cell_FACH state feature | 7.3.0 | 7.4.0 | +| 09/2007 | 37 | RP-070568 | 114 | 1 | Introduction of GANSS (Galileo and Additional Navigation Satellite Systems) | 7.4.0 | 7.5.0 | +| 09/2007 | 37 | RP-070650 | 115 | 1 | Introduction of multi-frequency for 1.28Mcps TDD in 25.401 | 7.4.0 | 7.5.0 | +| 06/2008 | 40 | RP-080297 | 116 | | MAC-ehs in CELL_DCH | 7.5.0 | 7.6.0 | +| 06/2008 | 40 | RP-080306 | 118 | | Introduction of Improved L2 for Uplink | 7.6.0 | 8.0.0 | +| 09/2008 | 41 | RP-080590 | 122 | 1 | The supplement of IPv4 encoding in NSAP structure | 8.0.0 | 8.1.0 | +| 09/2008 | 41 | RP-080587 | 123 | | Introduction of Enhanced Uplink in Cell_FACH | 8.0.0 | 8.1.0 | +| 12/2008 | 42 | RP-080849 | 124 | 1 | Enable to dynamically control the MBMS services in MBSFN | 8.1.0 | 8.2.0 | +| 12/2008 | 42 | RP-080850 | 125 | 1 | Introduction of the Enhanced CELL_FACH, CELL_PCH, URA_PCH state for 1.28Mcps TDD | 8.1.0 | 8.2.0 | +| 12/2008 | 42 | RP-080840 | 126 | | Introduction of Enhanced Relocation | 8.1.0 | 8.2.0 | +| 12/2009 | - | - | - | - | Created version 9.0.0 based on version 8.2.0 | 8.2.0 | 9.0.0 | +| 03/2010 | 47 | RP-100229 | 128 | 1 | SPID description and implementation guidelines in UTRAN | 9.0.0 | 9.1.0 | +| 12/2010 | 50 | RP-101389 | 131 | | Introduction of the SIPTO at Iu-PS Function | 9.1.0 | 10.0.0 | +| 12/2010 | 50 | RP-101272 | 133 | 1 | Adding support for ECN in UTRA | 9.1.0 | 10.0.0 | +| 03/2011 | SP-49 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 10.0.0 | 10.1.0 | +| 03/2011 | 51 | RP-110230 | 136 | 1 | Support for MDT | 10.0.0 | 10.1.0 | +| 06/2011 | 52 | RP-110684 | 137 | 1 | Correction of references | 10.1.0 | 10.2.0 | +| 06/2011 | 52 | RP-110694 | 138 | 3 | Introduction of Enhancements of Iu-r Interface | 10.1.0 | 10.2.0 | +| 09/2012 | 57 | RP-121140 | 139 | 3 | EAB for CN Overload Control | 10.2.0 | 11.0.0 | +| 12/2012 | 58 | RP-121736 | 140 | 2 | Documenting the Description of Extended S-RNTI and RNC-ID operation | 11.0.0 | 11.1.0 | +| 12/2013 | 62 | RP-131909 | 141 | 3 | Introduction of Standalone GW for SIPTO@LN | 11.1.0 | 12.0.0 | +| 12/2015 | 70 | RP-152096 | 145 | 2 | Introduction of DECOR feature | 12.0.0 | 13.0.0 | +| 12/2015 | 70 | RP-152090 | 146 | 2 | Introduction of DL enhancements | 12.0.0 | 13.0.0 | +| 12/2015 | 70 | RP-152091 | 149 | | Introduction of Traffic Volume measurement for RAN Sharing | 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|----------|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 03/2017 | RP-75 | RP-170544 | 015
2 | 4 | B | Introduction of eDECOR in RAN | 14.0.0 | +| 03/2017 | RP-75 | RP-170545 | 015
3 | 1 | B | Introduction of QMC for streaming services | 14.0.0 | +| 2018-06 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25412/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/Rel-16/25_series/25412/0b87abe67b21a93777287649c33e755d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9b2721a50f345735bb75e448a1f742a1685b762 --- /dev/null +++ b/marked/Rel-16/25_series/25412/0b87abe67b21a93777287649c33e755d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f0e04cbe07c009ae313f048589ea54e3259459366e9a4927eb3cb5c10dcc28e +size 39020 diff --git a/marked/Rel-16/25_series/25412/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/25_series/25412/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..944f4d7dfe363ce89af8297bb91a258cfbd731c3 --- /dev/null +++ b/marked/Rel-16/25_series/25412/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e34771a9c13fdc436a4ffa27d66b6bddcd632ca00b90a69515c5771bfb0fe7c +size 35009 diff --git a/marked/Rel-16/25_series/25412/raw.md b/marked/Rel-16/25_series/25412/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c679004d473fdad3fecb9f29c748cc4561d5be07 --- /dev/null +++ b/marked/Rel-16/25_series/25412/raw.md @@ -0,0 +1,284 @@ + + + + + + +# --- Contents + +| | | | +|------------------------|-----------------------------------------------------|----| +| 1 | Scope..... | 5 | +| 2 | References..... | 5 | +| 3 | Abbreviations..... | 6 | +| 4 | Data Link Layer ..... | 7 | +| 4.1 | ATM Transport Option ..... | 7 | +| 4.2 | IP Transport Option..... | 7 | +| 5 | RANAP Signalling Bearer ..... | 7 | +| 5.1 | Introduction ..... | 7 | +| 5.2 | Signalling Bearer for Circuit Switched Domain ..... | 7 | +| 5.2.1 | Protocol Stack for the CS Domain ..... | 7 | +| 5.2.2 | ATM Transport Option..... | 8 | +| 5.2.3 | IP Transport Option..... | 8 | +| 5.3 | Signalling Bearer for Packet Switched Domain..... | 9 | +| 5.3.1 | Protocol Stack for the PS Domain..... | 9 | +| 5.3.2 | ATM Transport Option 1 ..... | 9 | +| 5.3.3 | ATM Transport Option 2..... | 10 | +| 5.3.4 | IP Transport Option..... | 10 | +| 5.4 | Services Provided by the Signalling Bearer..... | 10 | +| Annex A (informative): | Change History..... | 11 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the standards for Signalling Transport to be used across Iu Interface. Iu Interface is a logical interface between the RNC and the UTRAN Core Network. The present document describes how the RANAP signalling messages are transported over Iu. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] ITU-T Recommendation Q.2100 (1994-07): "B-ISDN Signalling ATM Adaptation Layer (SAAL) - overview description". +- [2] ITU-T Recommendation Q.2110 (1994-07): "B-ISDN ATM Adaptation Layer – Service Specific Connection Oriented Protocol (SSCOP)". +- [3] ITU-T Recommendation Q.2140 (1995-02): "B-ISDN ATM adaptation layer – Service Specific Co-ordination Function for signalling at the Network Node Interface (SSCF AT NNI)". +- [4] ITU-T Recommendation Q.2210 (1996-07): "Message transfer part level 3 functions and messages using the services of ITU-T Recommendation Q.2140". +- [5] ITU-T Recommendation I.361 (1995-11): "B-ISDN ATM layer specification". +- [6] ITU-T Recommendation I.363.5 (1996-08): "B-ISDN ATM Adaptation Layer Type 5". +- [7] ITU-T Recommendation Q.711 (1996-07): "Functional description of the signalling connection control part". +- [8] ITU-T Recommendation Q.712 (1996-07): "Definition and function of Signalling connection control part messages". +- [9] ITU-T Recommendation Q.713 (1996-07): "Signalling connection control part formats and codes". +- [10] ITU-T Recommendation Q.714 (1996-07): "Signalling connection control part procedures". +- [11] ITU-T Recommendation Q.715 (1996-07): "Signalling connection control part user guide". +- [12] ITU-T Recommendation Q.716 (1993-03): "Signalling Connection Control Part (SCCP) performance". +- [13] IETF RFC 791 (1981-09): "Internet Protocol". +- [14] IETF RFC 2684 (1999-09): "Multiprotocol Encapsulation over ATM Adaptation Layer 5". +- [15] IETF RFC 2225 (1998-04): "Classical IP and ARP over ATM". +- [16] IETF RFC 2960 (2000-10): "Stream Control Transmission Protocol". +- [17] IETF RFC 3332(2002-09): "Signalling System 7 (SS7) Message Transfer Part 3 (MTP3) – User Adaptation Layer (M3UA)". +- [18] 3GPP TS 25.410: "UTRAN Iu Interface: General Aspects and Principles". + +- [19] IETF RFC 1661 (1994-07): "The Point-To-Point Protocol (PPP)". +- [20] IETF RFC 1662 (1994-07): "PPP in HDLC-like Framing". +- [21] IETF RFC 2507 (1999-02): "IP header compression". +- [22] IETF RFC 1990 (1996-08): "The PPP Multilink Protocol (MP)". +- [23] IETF RFC 2686 (1999-09): "The Multi-Class Extension to Multi-Link PPP". +- [24] IETF RFC 2509 (1999-02): "IP Header Compression over PPP". +- [25] IETF RFC 2460 (1996-12): "Internet Protocol, Version 6 (Ipv6) Specification". +- [26] IETF RFC 2474 (1998-12): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers". +- [27] Void. +- [28] IETF RFC 3031 (2001-01): "MPLS". +- [29] IETF RFC 3153 (2001-08): "PPPmultiplexing". +- [30] IETF RFC 3309 (2002-09): "SCTP Checksum Change". +- [31] ANSI T1.111-2001: "Signalling System Number 7 (SS7) - Message Transfer Part (MTP)". +- [32] ANSI T1.112-2001: "Signalling System Number 7 (SS7) -- Signalling Connection Control Part (SCCP)". +- [33] ANSI T1.645-1995 (R2003), "B-ISDN Signaling ATM Adaptation Layer - Service Specific Coordination Function for Support of Signaling at the Network Node Interface (SSCF at the NNI)". + +# --- 3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-----------|----------------------------------------------------------| +| AAL | ATM Adaptation Layer | +| AAL2 | ATM Adaptation Layer 2 | +| AAL5 | ATM Adaptation Layer 5 | +| ATM | Asynchronous Transfer Mode | +| CS | Circuit Switched | +| DiffServ | Differentiated Services | +| HDLC | High Level Data Link Control | +| IP | Internet Protocol | +| M3UA | SS7 MTP3 User Adaptation Layer | +| ML/MC-PPP | Muti-Link/Multi-Class PPP | +| MPLS | Multiprotocol Label Switching | +| MSC | Mobile services Switching Center | +| MTP3-B | Message Transfer Part | +| PPP | Point-to-Point protocol | +| PPPMux | PPP Multiplexing | +| PS | Packet Switched | +| RANAP | Radio Access Network Application Part | +| RNC | Radio Network Controller | +| SAAL-NNI | Signalling ATM Adaptation Layer – Network Node Interface | +| SCCP | Signalling Connection Control Part | +| SCTP | Stream Control Transmission Protocol | +| SGSN | Serving GPRS Support Node | +| SSCF | Service Specific Co-ordination Function | +| SSCOP | Service Specific Connection Oriented Protocol | + +# --- 4 Data Link Layer + +## 4.1 ATM Transport Option + +ATM shall be used in the radio network control plane according to (ITU-T Rec. I.361 [5]). The structure of the cell header used in the UTRAN Iu interface is the cell header format and encoding at NNI (see Figure 3/I.361). + +## 4.2 IP Transport Option + +An RNC/CN using IP transport option shall support the PPP protocol with HDLC framing (IETF RFC 1661 [19], IETF RFC 1662 [20]). + +Note: This does not preclude the single implementation and use of any other data link layer protocol (e.g. PPPMux (IETF RFC 3153 [29])/AAL5/ATM, PPP/AAL2/ATM, Ethernet, MPLS (IETF RFC 3031 [28])/ATM, etc.) fulfilling the UTRAN requirements toward the upper Layers. + +An RNC/CN using IP transport option having interfaces connected via low bandwidth PPP links like E1/T1/J1 shall also support IP Header Compression (IETF RFC 2507 [21]) and the PPP extensions ML/MC-PPP (IETF RFC 1990 [22], IETF RFC 2686 [23]). In this case, the negotiation of header compression (IETF RFC 2507 [21]) over PPP shall be performed via IETF RFC 2509 [24]. + +# --- 5 RANAP Signalling Bearer + +## 5.1 Introduction + +This subclause specifies the Signalling Bearer protocol stack that supports the RANAP signalling protocol. + +The following requirements on the Signalling Bearer can be stated: + +- provide reliable transfer of control plane signalling messages in both connectionless mode and connection-oriented mode; +- provide separate independent connections for distinguishing transactions with individual UE's; +- supervise the 'UE connections' and provide connection status information to the Upper Layers for individual UE's; +- provide networking and routing functions; +- provide redundancy in the signalling network; +- provide load sharing. + +## 5.2 Signalling Bearer for Circuit Switched Domain + +### 5.2.1 Protocol Stack for the CS Domain + +The protocol stacks for the CS Domain are shown in figure 1. The standard allows operators to choose one out of two standardised protocol suites for transport of SCCP messages. + +Figure 1 shows, for the Iu IP CS domain, the point at which the service primitives are invoked. A single SAP is defined independently of the signalling bearer. The SAP provides the SCCP primitives. The figure is not intended to constrain the architecture. + +The following figure 1 also illustrates the protocol model having Broadband Signalling System No.7 as the signalling bearer for RANAP over the Iu interface that fulfils the requirements. Figure 1 shows, for the CS domain, the point at which the service primitives are invoked. The SAP provides the SCCP primitives. + +![Figure 1: SAP between RANAP and its transport for Iu - CS Domain. Two protocol stacks for the Iu-CS Control Plane are shown. The left stack is for ATM transport and the right is for IP transport. Both start with RANAP at the top, connecting via an SCCP-SAP to an SCCP layer. The ATM stack then continues down through MTP3-B, SAAL-NNI, and ATM. The IP stack continues down through M3UA, SCTP, IP, and Data Link.](d0abac95583b52a3b35f74a215567334_img.jpg) + +``` + +graph TD + subgraph "ATM Transport Option" + A1[RANAP] -- SCCP-SAP --- B1[SCCP] + B1 --- C1[MTP3-B] + C1 --- D1[SAAL-NNI] + D1 --- E1[ATM] + end + subgraph "IP Transport Option" + A2[RANAP] -- SCCP-SAP --- B2[SCCP] + B2 --- C2[M3UA] + C2 --- D2[SCTP] + D2 --- E2[IP] + E2 --- F2[Data Link] + end + +``` + +Figure 1: SAP between RANAP and its transport for Iu - CS Domain. Two protocol stacks for the Iu-CS Control Plane are shown. The left stack is for ATM transport and the right is for IP transport. Both start with RANAP at the top, connecting via an SCCP-SAP to an SCCP layer. The ATM stack then continues down through MTP3-B, SAAL-NNI, and ATM. The IP stack continues down through M3UA, SCTP, IP, and Data Link. + +Protocol stack for ATM transport option + +Protocol stack for IP transport option + +Figure 1: SAP between RANAP and its transport for Iu - CS Domain + +### 5.2.2 ATM Transport Option + +1. **SCCP** (ITU-T Rec. Q.711 [7] or ANSI T1.112-2001 [32]) provides connectionless service, class 0, connection oriented service, class 2, separation of the connections mobile by mobile basis on the connection oriented link and establishment of a connection oriented link mobile by mobile basis. SCCP shall be used as specified in TS 25.410 [18]. +2. **MTP3-B** (ITU-T Rec. Q.2210 [4] or ANSI T1.111-2001 [31]) provides message routing, discrimination and distribution (for point-to-point link only), signalling link management load sharing and changeover/back between link within one link-set. The need for multiple link-sets is precluded. MTB3-B shall comply with ITU-T Rec. Q.2210 [4] or ANSI T1.111-2001 [31]. +3. **SAAL-NNI** (ITU-T Rec. Q.2100 [1]) consists of the following sub-layers: - **SSCF** (ITU-T Rec. Q.2140 [3] or ANSI T1.645-1995 (R2003) [33]), - **SSCOP** (ITU-T Rec. Q.2110 [2]) and - **AAL5** (ITU-T Rec. I.363.5 [6]). The SSCF maps the requirements of the layer above to the requirements of SSCOP. Also SAAL connection management, link status and remote processor status mechanisms are provided. SSCOP provides mechanisms for the establishment and release of connections and the reliable exchange of signalling information between signalling entities. Adapts the upper layer protocol to the requirements of the Lower ATM cells. It shall be possible to use SAAL-NNI connections pre-configured as PVCs for signalling transport on the Iu-Interface. +4. **ATM** (ITU-T Rec. I.361 [5]). + +### 5.2.3 IP Transport Option + +1. **SCCP**, see subclause 5.2.2. +2. **M3UA** refers to the SCCP adaptation layer "SS7 MTP3 – User Adaptation Layer " (IETF RFC 3332 [17]) also developed by the Sigtran working group of the IETF. An RNC equipped with the M3UA stack option shall have client functionality. This enables the RNC to report to the MSC when it is a newly introduced entity in the network. +3. **SCTP** refers to the Stream Control Transmission Protocol (IETF RFC 2960 [16]) developed by the Sigtran working group of the IETF for the purpose of transporting various signalling protocols over IP networks. The checksum method specified in IETF RFC 3309 [30] shall be used instead of the method specified in IETF RFC 2960 [16]. Multi-homing is a way to achieve redundancy with SCTP between two endpoints, of which one or both is assigned with multiple IP addresses. SCTP endpoints shall support a multi-homed remote SCTP endpoint. +4. **IP**. IPv6 shall be supported according to IETF RFC 2460 [25]. IPv4 support (IETF RFC 791 [13]) is optional. + +Note: This does not preclude the single implementation and use of IPv4. + +Due to the possible transition from IPv4 to IPv6 the IP dual stack support is recommended. + +An RNC/CN using IP transport option shall support Diffserv code point marking IETF RFC 2474 [26]. The Diffserv code point may be determined from the application parameters. + +## 5.3 Signalling Bearer for Packet Switched Domain + +### 5.3.1 Protocol Stack for the PS Domain + +The protocol stacks for the PS Domain is shown in figure 2. The standard allows operators to choose one out of three standardised protocol suites for transport of SCCP messages. + +![Figure 2: SAP between RANAP and its transport for the Iu -IP domain. The diagram shows two protocol stacks. The left stack is for ATM transport options, and the right stack is for IP transport option. Both stacks start with RANAP at the top, followed by SCCP-SAP, then SCCP. Below SCCP, the ATM stack includes MTP3-B, M3UA, SCTP, SAAL-NNI, IP, AAL5, and ATM. The IP stack includes M3UA, SCTP, IP, and Data Link.](0b87abe67b21a93777287649c33e755d_img.jpg) + +The diagram illustrates two protocol stacks for the Iu-PS Control Plane. Both stacks share a common top section: RANAP connected to SCCP-SAP, which is connected to SCCP. Below SCCP, the stacks differ based on the transport option. The left stack, labeled 'Protocol stacks for ATM transport options', shows SCCP connected to a box containing MTP3-B, M3UA, SCTP, SAAL-NNI, IP, and AAL5, which is then connected to ATM. The right stack, labeled 'Protocol stack for IP transport option', shows SCCP connected to a box containing M3UA, SCTP, IP, and Data Link. + +Figure 2: SAP between RANAP and its transport for the Iu -IP domain. The diagram shows two protocol stacks. The left stack is for ATM transport options, and the right stack is for IP transport option. Both stacks start with RANAP at the top, followed by SCCP-SAP, then SCCP. Below SCCP, the ATM stack includes MTP3-B, M3UA, SCTP, SAAL-NNI, IP, AAL5, and ATM. The IP stack includes M3UA, SCTP, IP, and Data Link. + +Protocol stacks for ATM transport options + +Protocol stack for IP transport option + +Figure 2: SAP between RANAP and its transport for the Iu -IP domain + +Figure 2 shows, for the Iu IP domain, the point at which the service primitives are invoked. A single SAP is defined independently of the signalling bearer. The SAP provides the SCCP primitives. The figure is not intended to constrain the architecture. + +### 5.3.2 ATM Transport Option 1 + +1. **SCCP** (ITU-T Rec. Q.711 [7] /ITU-T Rec. Q.712 [8] /ITU-T Rec. Q.713 [9] /ITU-T Rec. Q.714 [10] /ITU-T Rec. Q.715 [11] /ITU-T Rec. Q.716 [12] or ANSI T1.112-2001 [32]) provides connectionless service, class 0, connection oriented service, class 2, separation of the connections mobile by mobile basis on the connection oriented link and establishment of a connection oriented link mobile by mobile basis. The SCCP shall be used as specified in TS 25.410 [18]. +2. **MTP3-B** (ITU-T Rec. Q.2210 [4] or ANSI T1.111-2001 [31]) provides message routing, discrimination and distribution (for point-to-point link only), signalling link management load sharing and changeover/back between link within one link-set. The need for multiple link-sets is precluded. MTB3-B shall comply with ITU-T Rec. Q.2210 [4] or ANSI T1.111-2001 [31]. +3. **SAAL-NNI** (ITU-T Rec. Q.2100 [1]) consists of the following sub-layers: - **SSCF-NNI** (ITU-T Rec. Q.2140 [3] or ANSI T1.645-1995 (R2003) [33]), - **SSCOP** (ITU-T Rec. Q.2110 [2]) and - **AAL5** (ITU-T Rec. I.363.5 [6]). The SSCF maps the requirements of the layer above to the requirements of SSCOP. Also SAAL connection management, link status and remote processor status mechanisms are provided. SSCOP provides mechanisms for the establishment and release of connections and the reliable exchange of signalling information between signalling entities. Adapts the upper layer protocol to the requirements of the Lower ATM cells. It shall be possible to use SAAL-NNI connections pre-configured as PVCs for signalling transport on the Iu-interface. +4. **ATM** (ITU-T Rec. I.361 [5]). + +### 5.3.3 ATM Transport Option 2 + +1. **SCCP**, see subclause 5.3.2. + +2. **M3UA** refers to the SCCP adaptation layer "SS7 MTP3 – User Adaptation Layer " (IETF RFC 3332 [17]) also developed by the Sigtran working group of the IETF. An RNC equipped with the M3UA stack option shall have client functionality. This enables the RNC to report to the SGSN when it is a newly introduced entity in the network. +3. **SCTP** refers to the Stream Control Transmission Protocol (IETF RFC 2960 [16]) developed by the Sigtran working group of the IETF for the purpose of transporting various signalling protocols over IP networks. The multi-homing services of SCTP shall be required at both ends of an SCTP-association to enable transport redundancy and reliability. **M3UA**. An implementation of SCTP to this document shall utilise the new checksum method specified in IETF RFC 3309 [30] instead of the method specified in IETF RFC 2960 [16]. +4. **IP** (IETF RFC 791 [13]) over ATM is defined in IETF RFC 2684 [14] and IETF RFC 2225 [15]. +5. **AAL5** refers to ITU-T Rec. I.363.5 [6]. It shall be possible to use AAL5 connections pre-configured as PVCs for signalling transport on the Iu-interface. + +### 5.3.4 IP Transport Option + +1. **SCCP** , see subclause 5.3.2. +2. **M3UA**, refers to the SCCP adaptation layer "SS7 MTP3 – User Adaptation Layer " (IETF RFC 3332 [17]) also developed by the Sigtran working group of the IETF. An RNC equipped with the M3UA stack option shall have client functionality. This enables the RNC to report to the SGSN when it is a newly introduced entity in the network. +3. **SCTP**, refers to the Stream Control Transmission Protocol (IETF RFC 2960 [16]) developed by the Sigtran working group of the IETF for the purpose of transporting various signalling protocols over IP networks. An implementation of SCTP to this document shall utilise the new checksum method specified in IETF RFC 3309 [30] instead of the method specified in IETF RFC 2960 [16]. Multi-homing is a way to achieve redundancy with SCTP between two endpoints, of which one or both is assigned with multiple IP addresses. SCTP endpoints shall support a multi-homed remote SCTP endpoint. +4. **IP**. IPv6 shall be supported according to IETF RFC 2460 [25]. IPv4 support (IETF RFC 791 [13]) is optional. + +Note: This does not preclude the single implementation and use of IPv4. + +Due to the possible transition from IPv4 to IPv6, the IP dual stack support is recommended. + +An RNC/CN using IP transport option shall support Diffserv code point marking (IETF RFC 2474 [26]). The Diffserv code point may be determined from the application parameters. + +## 5.4 Services Provided by the Signalling Bearer + +When considering the requirements that the upper layers, i.e. RANAP, have on the Signalling Bearer, there are a number of services it has to provide and a number of functions to perform. These numbers of services that the signalling bearer shall provide, to the upper layers, are stated in references ITU-T Rec. Q.711 [7] /ITU-T Rec. Q.712 [8] /ITU-T Rec. Q.713 [9] /ITU-T Rec. Q.714 [10] /ITU-T Rec. Q.715 [11] / ITU-T Rec. Q.716 [12] or ANSI T1.112-2001 [32]. + +# Annex A (informative): Change History + +| Date / TSG | TSG Doc. | CR | Rev | Subject/Comment | New | +|------------|-----------|------|-----|------------------------------------------------------------|--------| +| 12/2008 | - | - | - | Creation of Rel-8 version based on v7.1.0 | 8.0.0 | +| 12/2009 | - | - | - | Creation of Rel-9 version based on v8.0.0 | 9.0.0 | +| 03/2011 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 9.0.1 | +| 03/2011 | | | | Creation of Rel-10 version based on v9.0.1 | 10.0.0 | +| 06/2011 | RP-110685 | 0026 | | Correction to the References in 25.412 | 10.1.0 | +| 09/2012 | | | | Update to Rel-11 version (MCC) | 11.0.0 | +| 09/2014 | | | | Update to Rel-12 version (MCC) | 12.0.0 | +| 12/2015 | | | | Update to Rel-13 version (MCC) | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-06 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25415/1662582b76eec39c269b6ae14fe5d5f1_img.jpg b/marked/Rel-16/25_series/25415/1662582b76eec39c269b6ae14fe5d5f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8541286ff57df9eee8c80e51775aa227b45eefe --- /dev/null +++ b/marked/Rel-16/25_series/25415/1662582b76eec39c269b6ae14fe5d5f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:881a188256605d5e4d288b6ef8ef4d2029c6e2a31382d78486aac15dcd510a91 +size 11504 diff --git a/marked/Rel-16/25_series/25415/1bf34e86af3591c80bfbc1c318f811c0_img.jpg b/marked/Rel-16/25_series/25415/1bf34e86af3591c80bfbc1c318f811c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..beab52445850b2b0443db2ffa80fa6734360e883 --- /dev/null +++ b/marked/Rel-16/25_series/25415/1bf34e86af3591c80bfbc1c318f811c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e09559f9fe148de6f061805b5040fb1a6ee45ee014a414c28f44144110a7cc3 +size 28622 diff --git a/marked/Rel-16/25_series/25415/1dbb1d90b2022a3a765c85929a515cc6_img.jpg b/marked/Rel-16/25_series/25415/1dbb1d90b2022a3a765c85929a515cc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d55909f6988d653a486555efd9aa318c7f836abc --- /dev/null +++ b/marked/Rel-16/25_series/25415/1dbb1d90b2022a3a765c85929a515cc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71d5c092976ffbea13a282b68fbf565d85536f954e919dd63a2b63a6ef02bfba +size 43090 diff --git a/marked/Rel-16/25_series/25415/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/25_series/25415/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e64c5cbf72dfc2943622f3009ef9d0e3d9d6707c --- /dev/null +++ b/marked/Rel-16/25_series/25415/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0a9c7005c139b9f4b495148011b7efa5aecedf21f028f49b087dad3d291cf81 +size 23930 diff --git a/marked/Rel-16/25_series/25415/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/25_series/25415/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b911aa39d09eefb5523c70e037e13c84f242e942 --- /dev/null +++ b/marked/Rel-16/25_series/25415/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e2841ae536bb52c3a0484d8e57f7aa0bb620a17797f006a727f93e96785187c +size 34838 diff --git a/marked/Rel-16/25_series/25415/2834bdd6eb8540277e609decbb924003_img.jpg b/marked/Rel-16/25_series/25415/2834bdd6eb8540277e609decbb924003_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4cc840b90a91a9748c8ae53a46d8df6862dfa42a --- /dev/null +++ b/marked/Rel-16/25_series/25415/2834bdd6eb8540277e609decbb924003_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a31256ef9c8d3955a31e64847978b42d52758083f1248063d379ef2d1ba6f70 +size 20055 diff --git a/marked/Rel-16/25_series/25415/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-16/25_series/25415/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d1fd060a6eccffafff8e059c917bd1fcb0819ce --- /dev/null +++ b/marked/Rel-16/25_series/25415/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:264fa4e380b2f98e620bc7118db8769579a60fe172ae8c6fd707c5768bfa17f9 +size 18744 diff --git a/marked/Rel-16/25_series/25415/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-16/25_series/25415/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..945716d6c8e76420af57af6fd09f2ef4021dbe5c --- /dev/null +++ b/marked/Rel-16/25_series/25415/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f05cf966c58faa611ab91bb2b2ad493c6eb1fc47b111a75551c786d4e551471 +size 75137 diff --git a/marked/Rel-16/25_series/25415/2de714cedbbdd36f901f71bafa78f75a_img.jpg b/marked/Rel-16/25_series/25415/2de714cedbbdd36f901f71bafa78f75a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70586f8838e3852f613d182f35d251ded6951d9c --- /dev/null +++ b/marked/Rel-16/25_series/25415/2de714cedbbdd36f901f71bafa78f75a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0b261730454696d760f56d1bd2c0c07596f1eb1daa433ceb6458159b437b749 +size 55892 diff --git a/marked/Rel-16/25_series/25415/4842f073775fb1e84d101c02fd74e59e_img.jpg b/marked/Rel-16/25_series/25415/4842f073775fb1e84d101c02fd74e59e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81f46044c5edddafbae99b566893a9ce3d7ba543 --- /dev/null +++ b/marked/Rel-16/25_series/25415/4842f073775fb1e84d101c02fd74e59e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d547e0004e9fa592d1863c7d882b2dd88f0a32b6723dfd5a1d94a486079d8ce +size 28659 diff --git a/marked/Rel-16/25_series/25415/49a49278cad196bdfe0db6b4dd1be7fd_img.jpg b/marked/Rel-16/25_series/25415/49a49278cad196bdfe0db6b4dd1be7fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81a36458fb302cec639abdf0412130b99b1a045d --- /dev/null +++ b/marked/Rel-16/25_series/25415/49a49278cad196bdfe0db6b4dd1be7fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1c39ea8776fc9a58ca72dd35c358aae561b531b523c4ee388c85205f56ec860 +size 67888 diff --git a/marked/Rel-16/25_series/25415/4b87467ad9642943235f48f7d4b59449_img.jpg b/marked/Rel-16/25_series/25415/4b87467ad9642943235f48f7d4b59449_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c3e0beae5dbcdb9dea1b743355217cd424b5fa6 --- /dev/null +++ b/marked/Rel-16/25_series/25415/4b87467ad9642943235f48f7d4b59449_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d1da032508c0fd59bfd227ed83860d2e31d9cefe4924c9509ef60bd8a8caa2a +size 22487 diff --git a/marked/Rel-16/25_series/25415/51db757d054ce1ce83c436a3578b56ca_img.jpg b/marked/Rel-16/25_series/25415/51db757d054ce1ce83c436a3578b56ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1b64cbac36ce1d416e37212f2fbc5fccf1bf194 --- /dev/null +++ b/marked/Rel-16/25_series/25415/51db757d054ce1ce83c436a3578b56ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db80e906e3abd809387066b6ff6f431fe15bb481b9a822b0c5ac74cfbd8a46db +size 17873 diff --git a/marked/Rel-16/25_series/25415/5793a44ffdadd039928e2f9fe6daae06_img.jpg b/marked/Rel-16/25_series/25415/5793a44ffdadd039928e2f9fe6daae06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7514ba0c2601bcde69a4f0d2630a04a365ffb77 --- /dev/null +++ b/marked/Rel-16/25_series/25415/5793a44ffdadd039928e2f9fe6daae06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ed57961904e46e7c6e648b4d4ef29ea22813197a39739a1af2164652861a770 +size 18654 diff --git a/marked/Rel-16/25_series/25415/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/25_series/25415/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..516fff6112738c5c8f1d29384e6becc4e4951ec7 --- /dev/null +++ b/marked/Rel-16/25_series/25415/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:061c0a3e4e71a04e38ba4d4a2286c2d9a1f9c4aa2d086deb9a2c8661b4962c89 +size 51430 diff --git a/marked/Rel-16/25_series/25415/63e0c22852c26699d0bd095a2d796bab_img.jpg b/marked/Rel-16/25_series/25415/63e0c22852c26699d0bd095a2d796bab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f04470655adac0080db2c17188c246d799eb73de --- /dev/null +++ b/marked/Rel-16/25_series/25415/63e0c22852c26699d0bd095a2d796bab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f32132ac41b60210a405fc271f69089ba66ff7ece8b5007417d1e57bfee6663 +size 39456 diff --git a/marked/Rel-16/25_series/25415/6f31cdb576d2f15c35c3f266e5f59211_img.jpg b/marked/Rel-16/25_series/25415/6f31cdb576d2f15c35c3f266e5f59211_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e2daae2cddaf251741ff308042684e19d62daef --- /dev/null +++ b/marked/Rel-16/25_series/25415/6f31cdb576d2f15c35c3f266e5f59211_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4da064d27fb5286f94cbff27cf6f739bf0e3dcfe39abd3e2438ef8f38b1e2919 +size 21782 diff --git a/marked/Rel-16/25_series/25415/73dff6b45b2b9ffd384bab3235f869af_img.jpg b/marked/Rel-16/25_series/25415/73dff6b45b2b9ffd384bab3235f869af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7600f08be09c52c7bcd20d4bd4c4fed7459fbb94 --- /dev/null +++ b/marked/Rel-16/25_series/25415/73dff6b45b2b9ffd384bab3235f869af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc6fcc5943168a22dd07941f27c22c8c507c64f357ce2222e32c922e4f9447a9 +size 21117 diff --git a/marked/Rel-16/25_series/25415/7dfd8dd318dcfc36eaf4c967ddfb94c1_img.jpg b/marked/Rel-16/25_series/25415/7dfd8dd318dcfc36eaf4c967ddfb94c1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4b492903d0e15a74d8424342c907b1dda36c483 --- /dev/null +++ b/marked/Rel-16/25_series/25415/7dfd8dd318dcfc36eaf4c967ddfb94c1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a85fb08f49a47ff8d4004231b13a8bc3790f29260e5e251cbd6272875993534e +size 34280 diff --git a/marked/Rel-16/25_series/25415/844077b3034f0030b404207db0ad76b4_img.jpg b/marked/Rel-16/25_series/25415/844077b3034f0030b404207db0ad76b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1037e3ce94732ea17851e4f17dee59b57c377cf3 --- /dev/null +++ b/marked/Rel-16/25_series/25415/844077b3034f0030b404207db0ad76b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d80d1abc4e08a45b7f0593b38f75360166613e3a3a402e860e514293fc19e268 +size 29722 diff --git a/marked/Rel-16/25_series/25415/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/25_series/25415/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..41b7afc865095dbeddd00e0681651ca9d2d82de8 --- /dev/null +++ b/marked/Rel-16/25_series/25415/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99d010e3db2a74e8ddf5021d2c5754b7f838f26d6b479a1285fbd456fba87b0f +size 19792 diff --git a/marked/Rel-16/25_series/25415/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/25_series/25415/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..88c2f15063419b75b3b12fd6e1a469d9fd02827b --- /dev/null +++ b/marked/Rel-16/25_series/25415/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8f6c01fb2c14c33af1404b0c80938d12be458034d21782e0bf45e1aa092a258 +size 13550 diff --git a/marked/Rel-16/25_series/25415/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg b/marked/Rel-16/25_series/25415/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da42c7d178c846a7699c74e77bfe6ab34914301a --- /dev/null +++ b/marked/Rel-16/25_series/25415/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4925bc903789383633cd932156ed74bef4e85255344ba126c2d77e2c201a99da +size 50229 diff --git a/marked/Rel-16/25_series/25415/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-16/25_series/25415/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54db72dab6fd9311314b0bdda71b1c8856ae3bc8 --- /dev/null +++ b/marked/Rel-16/25_series/25415/a0e8fe7862a6d7341faf5dac275277cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b81181d5f9d9608c056b2f7e131be3d7fc576d0b29590afd2e3f3a80006f408 +size 104046 diff --git a/marked/Rel-16/25_series/25415/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/25_series/25415/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39bd765fb0445c8db76930c5d7b4301e9294b27d --- /dev/null +++ b/marked/Rel-16/25_series/25415/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05d72c6227ccf720be2097e37b98a14347011afc3ade6b1d78d897bb4489ed10 +size 8286 diff --git a/marked/Rel-16/25_series/25415/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg b/marked/Rel-16/25_series/25415/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa916ee049e32129065d89058f3054472b5a0c01 --- /dev/null +++ b/marked/Rel-16/25_series/25415/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:719c8f12e45c7fdf2b58ec03bc1853bc3160a53f6abeb94e84db98f98c022526 +size 27816 diff --git a/marked/Rel-16/25_series/25415/b06a4c871dfd0ce034cf801519d0039a_img.jpg b/marked/Rel-16/25_series/25415/b06a4c871dfd0ce034cf801519d0039a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54093d6063f7ff44ffaa0231f191fa80706efcf3 --- /dev/null +++ b/marked/Rel-16/25_series/25415/b06a4c871dfd0ce034cf801519d0039a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01ff7828a8ad91d29a3c9a83ee678efce32a366c2f1e805d5449c650f745426d +size 34149 diff --git a/marked/Rel-16/25_series/25415/dd380ccd5aca1151074fede04826f1a4_img.jpg b/marked/Rel-16/25_series/25415/dd380ccd5aca1151074fede04826f1a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40ee3f0e621001095d53354a9139484d16975bb4 --- /dev/null +++ b/marked/Rel-16/25_series/25415/dd380ccd5aca1151074fede04826f1a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63c0f20689a3d98f268dfd9087bd1e5b50f9d46b01c7fc4f94b7f4b9d9098520 +size 17958 diff --git a/marked/Rel-16/25_series/25415/ddee3e67e0dfc22e25188fa635a19558_img.jpg b/marked/Rel-16/25_series/25415/ddee3e67e0dfc22e25188fa635a19558_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9daa1c3ea5ea13c4134b7a66cd553dbd4a5fa1aa --- /dev/null +++ b/marked/Rel-16/25_series/25415/ddee3e67e0dfc22e25188fa635a19558_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03472cc0b3bd94d666905a4464c931084a6f8b2e92ac9b9c42ebb37507887c05 +size 42782 diff --git a/marked/Rel-16/25_series/25415/e05c1a13b44ab41505609d82b00cf4df_img.jpg b/marked/Rel-16/25_series/25415/e05c1a13b44ab41505609d82b00cf4df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c1bc2f79a0f137d81ca8cf86fdea942ef8ce20c --- /dev/null +++ b/marked/Rel-16/25_series/25415/e05c1a13b44ab41505609d82b00cf4df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0738e30ef13e3a2d294fa5b2ad0e6615402356972be8ede93c2fd7f5b87d8313 +size 14203 diff --git a/marked/Rel-16/25_series/25415/e29665b8abcea967ef289c6aff07ae4c_img.jpg b/marked/Rel-16/25_series/25415/e29665b8abcea967ef289c6aff07ae4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd1fac6a9ce8c916ce184f0ba886c5a5f11ae44d --- /dev/null +++ b/marked/Rel-16/25_series/25415/e29665b8abcea967ef289c6aff07ae4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6552d1c2d67f9837a23e345479b77402d78346068e94a408697382fb7bb3c09c +size 22307 diff --git a/marked/Rel-16/25_series/25415/f0a97d0d3818a253c1d2a009966081b1_img.jpg b/marked/Rel-16/25_series/25415/f0a97d0d3818a253c1d2a009966081b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae4f7504eaf92b721fc40ee2fdfd80f6331aa936 --- /dev/null +++ b/marked/Rel-16/25_series/25415/f0a97d0d3818a253c1d2a009966081b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41fbb646aab279f88735c6a79646468e328be89b759cf8c888760e68e7bdf5c0 +size 63393 diff --git a/marked/Rel-16/25_series/25415/raw.md b/marked/Rel-16/25_series/25415/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ac4abed0c62f010f2ad67d61ba59ebfcb74da6d7 --- /dev/null +++ b/marked/Rel-16/25_series/25415/raw.md @@ -0,0 +1,2179 @@ + + + + + + +# Contents + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..........................................................................................................................................................................6 | 6 | +| 1 Scope..................................................................................................................................................................7 | 7 | +| 2 References..........................................................................................................................................................7 | 7 | +| 3 Definitions and abbreviations ............................................................................................................................8 | 8 | +| 3.1 Definitions..........................................................................................................................................................8 | 8 | +| 3.2 Abbreviations .....................................................................................................................................................9 | 9 | +| 3.3 Concepts.............................................................................................................................................................9 | 9 | +| 3.4 Specification Notations ....................................................................................................................................10 | 10 | +| 4 General.............................................................................................................................................................10 | 10 | +| 4.1 General aspects.................................................................................................................................................10 | 10 | +| 4.2 Operational and Functional Aspects ................................................................................................................11 | 11 | +| 4.2.1 Iu UP protocol modes of operation ................................................................................................................11 | 11 | +| 4.2.2 Transparent mode (TrM)................................................................................................................................11 | 11 | +| 4.2.3 Support mode..................................................................................................................................................12 | 12 | +| 5 Transparent mode, version 1 ...........................................................................................................................13 | 13 | +| 5.1 General .............................................................................................................................................................13 | 13 | +| 5.1.1 Operation of the Iu UP in Transparent mode .................................................................................................13 | 13 | +| 5.1.2 Interfaces of the Iu UP protocol layer in Transparent mode ..........................................................................14 | 14 | +| 5.2 Iu UP Protocol layer Services in Transparent mode ........................................................................................14 | 14 | +| 5.3 Services Expected from the UP Data Transport layer......................................................................................14 | 14 | +| 5.4 Elements for Iu UP communication in Transparent mode...............................................................................14 | 14 | +| 5.4.1 Frame Format for transparent mode ...............................................................................................................14 | 14 | +| 6 Support mode for predefined SDU sizes, version 2.........................................................................................14 | 14 | +| 6.1 General .............................................................................................................................................................14 | 14 | +| 6.1.1 Operation of the Iu UP in Support mode ........................................................................................................14 | 14 | +| 6.1.2 Interfaces of the Iu UP protocol layer in Support mode .................................................................................15 | 15 | +| 6.2 Iu UP Protocol layer Services in Support mode...............................................................................................15 | 15 | +| 6.3 Services Expected from the UP Data Transport layer......................................................................................15 | 15 | +| 6.4 Functions of the Iu UP Protocol Layer in Support mode .................................................................................16 | 16 | +| 6.4.1 Functional model of the Iu UP Protocol Layer in Support mode ...................................................................16 | 16 | +| 6.4.2 Frame Handler function..................................................................................................................................16 | 16 | +| 6.4.3 Procedure Control functions............................................................................................................................16 | 16 | +| 6.4.4 Non Access Stratum Data Streams specific function(s)..................................................................................17 | 17 | +| 6.4.4.1 Frame Quality Classification function............................................................................................................17 | 17 | +| 6.4.4.1.1 General ..........................................................................................................................................................17 | 17 | +| 6.4.4.1.2 Handling of FQC information in uplink path...............................................................................................17 | 17 | +| 6.4.4.1.3 Handling of FQC information in downlink path...........................................................................................18 | 18 | +| 6.5 Elementary procedures .....................................................................................................................................18 | 18 | +| 6.5.1 Transfer of User Data procedure ....................................................................................................................18 | 18 | +| 6.5.1.1 Successful operation .....................................................................................................................................18 | 18 | +| 6.5.1.2 Unsuccessful operation .................................................................................................................................19 | 19 | +| 6.5.2 Initialisation procedure ...................................................................................................................................20 | 20 | +| 6.5.2.1 Successful operation .....................................................................................................................................20 | 20 | +| 6.5.2.2 Unsuccessful operation..................................................................................................................................22 | 22 | +| 6.5.3 Iu Rate Control procedure ..............................................................................................................................22 | 22 | +| 6.5.3.1 Successful operation .....................................................................................................................................22 | 22 | +| 6.5.3.2 Unsuccessful operation..................................................................................................................................23 | 23 | +| 6.5.3.2A Frequent Rate Control Procedures ................................................................................................................24 | 24 | +| 6.5.4 Time Alignment procedure.............................................................................................................................25 | 25 | +| 6.5.4.1 Successful operation .....................................................................................................................................25 | 25 | +| 6.5.4.2 Unsuccessful operation .................................................................................................................................26 | 26 | +| 6.5.5 Handling of Error Event procedure ................................................................................................................27 | 27 | +| 6.5.5.1 Successful operation .....................................................................................................................................27 | 27 | +| 6.5.5.2 Unsuccessful operation .................................................................................................................................27 | 27 | +| 6.5.6 Frame Quality Classification procedure.........................................................................................................28 | 28 | + +| | | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------|----| +| 6.6 | Elements for Iu UP communication in Support mode ................................................................... | 28 | +| 6.6.1 | General ........................................................................................................................................ | 28 | +| 6.6.2 | Frame Format for predefined size SDUs..................................................................................... | 29 | +| 6.6.2.1 | PDU Type 0 ............................................................................................................................ | 29 | +| 6.6.2.2 | PDU Type 1 ............................................................................................................................ | 30 | +| 6.6.2.3 | PDU Type 14 .......................................................................................................................... | 31 | +| 6.6.2.3.1 | General ................................................................................................................................ | 31 | +| 6.6.2.3.2 | Positive Acknowledgement.................................................................................................. | 32 | +| 6.6.2.3.3 | Negative Acknowledgement ................................................................................................ | 33 | +| 6.6.2.3.4 | Procedures Coding .............................................................................................................. | 34 | +| 6.6.3 | Coding of information elements in frames ................................................................................... | 37 | +| 6.6.3.1 | PDU Type ............................................................................................................................... | 37 | +| 6.6.3.2 | Ack/Nack ................................................................................................................................ | 37 | +| 6.6.3.3 | Frame Number ........................................................................................................................ | 38 | +| 6.6.3.4 | PDU Type 14 Frame Number................................................................................................. | 38 | +| 6.6.3.5 | Frame Quality Classification (FQC)........................................................................................ | 38 | +| 6.6.3.6 | RAB sub-Flow Combination Indicator (RFCI) ....................................................................... | 39 | +| 6.6.3.7 | Procedure Indicator.................................................................................................................. | 39 | +| 6.6.3.8 | Header CRC............................................................................................................................. | 39 | +| 6.6.3.9 | Payload CRC............................................................................................................................ | 39 | +| 6.6.3.10 | Chain Indicator ........................................................................................................................ | 39 | +| 6.6.3.11 | Number of Subflows per RFCI............................................................................................... | 39 | +| 6.6.3.12 | Length Indicator (LI) .............................................................................................................. | 39 | +| 6.6.3.13 | Number of RFCI Indicators .................................................................................................... | 40 | +| 6.6.3.14 | RFCI n Indicator ..................................................................................................................... | 40 | +| 6.6.3.15 | Error distance........................................................................................................................... | 40 | +| 6.6.3.16 | Error Cause value..................................................................................................................... | 40 | +| 6.6.3.17 | Padding ................................................................................................................................... | 41 | +| 6.6.3.18 | Time alignment........................................................................................................................ | 41 | +| 6.6.3.19 | Spare ....................................................................................................................................... | 41 | +| 6.6.3.20 | Spare extension ....................................................................................................................... | 41 | +| 6.6.3.21 | LRI, Last RFCI Indicator........................................................................................................ | 41 | +| 6.6.3.22 | Length of subflow ................................................................................................................... | 42 | +| 6.6.3.23 | TI............................................................................................................................................. | 42 | +| 6.6.3.24 | IPTI of n th RFCI...................................................................................................................... | 42 | +| 6.6.3.25 | Iu UP Mode versions supported.............................................................................................. | 42 | +| 6.6.3.26 | Iu UP Mode Version............................................................................................................... | 42 | +| 6.6.3.27 | Payload fields........................................................................................................................... | 42 | +| 6.6.3.28 | Data PDU type ........................................................................................................................ | 43 | +| 6.6.4 | Timers.......................................................................................................................................... | 43 | +| 6.6.5 | Maximum values of repetition counters ....................................................................................... | 43 | +| 6.7 | Handling of unknown, unforeseen and erroneous protocol data....................................................... | 43 | +| 6.7.1 | General ........................................................................................................................................ | 43 | +| 6.7.2 | Error detected by Iu UP functions ............................................................................................... | 44 | +| 6.7.3 | Request by upper layers................................................................................................................ | 44 | +| 6.7.4 | Error event frame over the Iu UP protocol .................................................................................. | 44 | +| 6.7.5 | Handling of error reports ............................................................................................................. | 44 | +| 6.7.5.1 | General..................................................................................................................................... | 44 | +| 6.7.5.2 | Error distance .......................................................................................................................... | 45 | +| 6.7.6 | List of errors in Iu UP .................................................................................................................. | 46 | +| 6.7.7 | Error detection ............................................................................................................................. | 47 | +| 6.7.7.1 | General..................................................................................................................................... | 47 | +| 6.7.7.2 | CRC Calculation ...................................................................................................................... | 47 | +| 6.7.7.3 | Relation between input and output of the Cyclic Redundancy Check ................................... | 48 | +| 7 | Communication Primitives for the Iu UP protocol layer ................................................................... | 48 | +| 7.1 | Modelling Principle...................................................................................................................... | 48 | +| 7.2 | Primitives towards the upper layers at the RNL SAP ................................................................... | 48 | +| 7.2.1 | General .................................................................................................................................... | 48 | +| 7.2.2 | Iu-UP-DATA-REQUEST....................................................................................................... | 49 | +| 7.2.3 | Iu-UP-DATA-INDICATION ................................................................................................. | 50 | +| 7.2.4 | Iu-UP-STATUS-REQUEST................................................................................................... | 50 | + +| | | | +|-------------------------------|----------------------------------------------------------------------|-----------| +| 7.2.5 | Iu-UP-STATUS-INDICATION ..... | 50 | +| 7.2.6 | Iu-UP-UNIT-DATA-REQUEST ..... | 50 | +| 7.2.7 | Iu-UP-UNIT-DATA-INDICATION ..... | 50 | +| 7.3 | Primitives towards the transport layers at TNL SAP ..... | 50 | +| 7.3.1 | General ..... | 50 | +| 7.3.2 | ATM/AAL2 based Transport layer ..... | 50 | +| 7.3.2.1 | General ..... | 50 | +| 7.3.2.2 | AAL2 Service Primitives used by the Iu UP protocol ..... | 51 | +| 7.3.3 | GTP-U based Transport Layer ..... | 51 | +| 7.3.3.1 | General ..... | 51 | +| 7.3.3.2 | Generic Service Primitives used by the Iu UP protocol ..... | 51 | +| 7.3.4 | RTP based Transport Layer ..... | 51 | +| 7.3.4.1 | General ..... | 51 | +| 7.3.4.2 | Generic Service Primitives used by the Iu UP protocol ..... | 51 | +| 8 | Evolution of Iu UP Protocol ..... | 52 | +| 8.1 | Principles for Protocol Evolution ..... | 52 | +| 8.1.1 | Unknown field value ..... | 52 | +| 8.1.2 | Adding a new field to an existing frame ..... | 53 | +| 8.1.3 | Adding a new PDU type ..... | 53 | +| 8.1.4 | Protocol version handling ..... | 53 | +| Annex A (informative): | Illustration of usage of RFCI for AMR speech RAB ..... | 55 | +| Annex B (informative): | Illustration of protocol states in the Iu UP ..... | 58 | +| B.1 | Protocol state model for transparent mode ..... | 58 | +| B.1.1 | Null State ..... | 58 | +| B.1.2 | Transparent Mode Data Transfer Ready State ..... | 58 | +| B.2 | Protocol state model for support mode for predefined SDU sizes ..... | 59 | +| B.2.1 | Null State ..... | 59 | +| B.2.2 | Initialisation State ..... | 59 | +| B.2.3 | Support Mode Data Transfer Ready State ..... | 60 | +| Annex C (informative): | Open Issues of the Iu UP ..... | 61 | +| Annex D (informative): | Distributed rate decision within RNC ..... | 62 | +| Annex E (informative): | Change History ..... | 63 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document defines the Radio Network Layer user plane protocol being used over the Iu interface. + +--- + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TS 25.401: "UTRAN Overall Description". + - [2] 3GPP TS 25.410: "UTRAN Iu interface: General Aspects and Principles". + - [3] 3GPP TS 25.413: "UTRAN Iu interface RANAP Signalling". + - [4] 3GPP TS 25.414: "UTRAN Iu Interface Data Transport and Transport Signalling". + - [5] 3GPP TS 23.110: "UMTS Access Stratum Services and Functions". + - [6] Void + - [7] ITU-T Recommendation I.363.2 (2000-11): "B-ISDN ATM Adaptation Layer specification: Type 2 AAL". + - [8] ITU-T Recommendation I.366.1 (1998-06): "Segmentation and reassembly service specific convergence sublayer for the AAL type 2". + - [9] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + - [10] 3GPP TS 25.321: "Medium Access Control (MAC) protocol specification". + - [11] 3GPP TS 25.322: "Radio Link Control (RLC) protocol specification". + - [12] 3GPP TS 26.102: "Mandatory speech codec; AMR speech codec; Interface to Iu and Uu". + - [13] 3GPP TS 23.153: "Out of Band Transcoder Control; Stage 2". + - [14] IETF RFC 1889 (1996-01): "RTP: A Transport Protocol for Real Time Applications". + - [15] IETF RFC 1890 (1996-01): "RTP Profile for Audio and Video Conferences with Minimal Control". +- + +# 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply. + +**Iu Timing Interval (ITI):** Iu Timing Interval is the minimum time interval between sent Iu UP PDUs for a specific RAB. The ITI can be calculated for conversational and streaming traffic classes by the following formula: + +$$ITI = \frac{MaxSDUsize}{MaxBitrate}$$ + +**Inter PDU Transmission Interval (IPTI):** inter PDU Transmission Interval is the actual interval at which Iu UP PDUs can be sent at a certain time for a specific RAB subflow combination. The IPTI of a RAB subflow combination is calculated based on the RAB subflow combination size and the RAB subflow combination bitrate by dividing the RAB subflow combination size with the RAB subflow combination bitrate. + +$$IPTI_g = \frac{RFC\_size_g}{RFC\_Bitrate_g}, \quad g = 1, \dots, n, \quad n = \text{number of subflow combinations}$$ + +NOTE: If *RFC\_Bitrate* is not defined then IPTI=ITI. If *RFC\_size* is not defined then RFC\_size=MaxSDUsize. + +**Non Access Stratum (NAS) Data Streams:** non Access Stratum Data Streams is a generic term to identify these data streams exchanged at the Dedicated Service Access Points between the Non Access Stratum and the Access Stratum. + +**RAB sub-flows:** RAB as defined in TR 21.905 [9] is realised by UTRAN through one to several sub-flows. These sub-flows correspond to the NAS service data streams that have QoS characteristics that differ in a predefined manner within a RAB e.g. different reliability classes. + +### **RAB sub-flows characteristics:** + +- 1) the sub-flows of a RAB are established and released together at the RAB establishment and release, respectively; +- 2) the sub-flows of a RAB are submitted and delivered together at the RAB SAP; +- 3) the sub-flows of a RAB are carried over the same Iu transmission connection; +- 4) the sub-flows of a RAB are organised in a predefined manner at the RAB SAP and over the Iu interface. The organisation is imposed by the NAS as part of its co-ordination responsibility. + +### **RAB sub-flows numbering (applies to support mode for predefined SDU size only):** + +- 1) RAB sub-flows are numbered from 1 to N (N is the number of sub-flows); +- 2) RAB sub-flow number 1 corresponds to the highest reliability class and the RAB sub-flow number N corresponds to the lowest reliability class; +- 3) RAB sub-flows order inside the Iu frame is predefined so that RAB sub-flow number one comes first and the RAB sub-flow number N comes last. + +**RAB sub-Flow Combination (RFC):** RAB sub-flow combination is defined as an authorised combination of the RAB sub-flows variable attributes (e.g. SDU sizes) of currently valid RAB sub-flows that can be submitted simultaneously to the Iu UP for transmission over Iu interface. Each combination is given by the CN and cannot be altered by the SRNC. + +**RAB sub-Flow Combination Indicator (RFCI):** this indicator uniquely identifies a RAB sub-flow combination for the duration of the Iu UP peer protocol instances i.e. it is valid until the termination of the call or until a new initialisation is performed. Usage of RFCI applies only to Iu UP protocol operated in support mode for predefined SDU size. + +### **Principles related to RFCI allocation and Initialisation procedure:** + +- 1) RFCI value is present in every Iu user frame; +- 2) in the Initialisation procedure in Iu UP, the size of every RAB sub-flow SDU for each RFCI is signalled. + +**Syntactical error:** field is defined to be syntactically incorrect in a frame if it contains at least one value defined as "reserved", or if its value part violates syntactic rules given in the specification of the value part. However it is not a syntactical error that a value specified as "spare" is being used. + +**Semantical error:** A frame is defined to have semantically incorrect contents if it contains information which, possibly dependant on the state of the receiver, is in contradiction to the resources of the receiver and/or to the procedural part. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|--------|----------------------------------------------| +| AMR | Adaptive Multi-Rate codec | +| AS | Access Stratum | +| BER | Bit Error Rate | +| CN | Core Network | +| DTX | Discontinuous Transmission | +| DU | Data Unit | +| GF | Galois Field | +| IPTI | Inter PDU Transmission Interval | +| ITI | Iu Timing Interval | +| NAS | Non Access Stratum | +| PDU | Protocol Data Unit | +| QoS | Quality of Service | +| RAB | Radio Access Bearer | +| RANAP | Radio Access Network Application Part | +| RFC | RAB sub Flow Combination | +| RFCI | RFC Indicator | +| RNL | Radio Network Layer | +| RTP | Real-time Transport Protocol | +| SAP | Service Access Point | +| SDU | Service Data Unit | +| SID | Silence Insertion Descriptor | +| SMpSDU | Support Mode for predefined SDU size | +| SRNC | Serving RNC | +| SRNS | Serving RNS | +| SSSAR | Service Specific Segmentation and Reassembly | +| TFCI | Transport Format Combination Indicator | +| TFI | Transport Format Identification | +| TFO | Tandem Free Operation | +| TNL | Transport Network Layer | +| TrFO | Transcoder Free Operation | +| TrM | Transparent Mode | +| UP | User Plane | +| UUI | User to User Information | + +## 3.3 Concepts + +### **Iu UP mode of operation:** + +One objective of the Iu User Plane (UP) protocol is to remain independent of the CN domain (Circuit Switched or Packet Switched) and to have limited or no dependency with the Transport Network Layer. Meeting this objective provides the flexibility to evolve services regardless of the CN domain and to migrate services across CN domains. + +The Iu UP protocol is therefore defined with modes of operation that can be activated on a RAB basis rather than on a CN domain basis or (tele) service basis. The Iu UP mode of operation determines if and which set of features shall be provided to meet e.g. the RAB QoS requirements. + +### **Iu UP protocol PDU Type:** + +The Iu UP protocol PDU Types are defined for a given Iu UP mode of operation. An Iu UP PDU Type represents a defined structure of an Iu UP protocol frame. For instance, a frame made of a certain Frame Header mask part and a Frame Payload part would be specified as a certain PDU type valid for a given Iu UP mode of operation. + +### **Tandem Free Operation (TFO):** + +Configuration of a Speech or Multimedia call for which Transcoders are physically present in the communication path but transcoding functions are disabled or partially disabled. The Transcoders may perform control and/or protocol conversion functions. + +### **Transcoder (TC):** + +Physical device present in the network responsible for the transcoding of the speech data between two speech codecs or coding schemes (The Transcoder may also include other functions, i.e. Rate Adaptation in GSM). + +### **Transcoder Free Operation (TrFO):** + +Configuration of a Speech or Multimedia call for which Transcoders are not present in the communication path. + +## 3.4 Specification Notations + +For the purposes of the present document, the following notations apply: + +| | | +|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Procedure | When referring to a procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. Iu Rate Control procedure. | +| Frame | When referring to a control or data frame in the specification, the CONTROL/DATA FRAME NAME is written with all letters in upper case characters followed by the words "control/data frame", e.g. TIME ALIGNMENT control frame. | +| IE | When referring to an information element (IE) in the specification the Information Element Name is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation "IE", e.g. Frame Number IE. | +| Value of an IE | When referring to the value of an information element (IE) in the specification the "Value" is written as it is specified in subclause 6.6.3 enclosed by quotation marks, e.g. "0" or "255". | + +# --- 4 General + +## 4.1 General aspects + +The Iu UP protocol is located in the User plane of the Radio Network layer over the Iu interface: the Iu UP protocol layer. + +The Iu UP protocol is used to convey user data associated to Radio Access Bearers. + +One Iu UP protocol instance is associated to one RAB and one RAB only. If several RABs are established towards one given UE, then these RABs make use of several Iu UP protocol instances. + +In general, Iu UP protocol instances exist at Iu access point as defined in TS 25.410 [2] i.e. at CN and UTRAN. However, as described in TS 23.153 [13], if TrFO is possible and the Iu UP protocol instances operate in support mode the Iu UP protocol instance in CN may resume performing Iu UP specific functions or vanish completely during stable call states. In this case the partner peer entity actually interacting with the UTRAN Iu UP protocol instance (i.e. performing all Iu UP specific functions except UP initialisation) may either be located within another UTRAN or within a CN node that is not the serving CN node of the UTRAN. + +Whenever a RAB requires transfer of user data in the Iu UP, an Iu UP protocol instance exists at each Iu interface access points. These Iu UP protocol instances are established, relocated and release together with the associated RAB. + +Whether these peer protocol instances perform some RAB related function depends on the mode of operation of the Iu UP as defined below. + +The following figure illustrates the logical placement of the Iu UP protocol layer and the placement of the Data Streams sources outside of the Access Stratum. + +![Figure 1: Iu UP protocol layer occurrence in UTRAN overall architecture (User Plane View). The diagram shows the protocol stack for the User Plane across three entities: UE, UTRAN, and CN. The UE and CN both have a 'NAS Data Streams' block at the top within the 'Non-Access Stratum'. Below this, in the 'Access Stratum', the UE has 'Radio protocols'. The UTRAN has 'Radio protocols' on the left (connecting to UE via 'Radio (Uu)') and a stack on the right consisting of 'Iu UP', 'User plane Data Bearers protocols', and 'Transport Layer'. The CN has 'Iu UP' and 'User plane Data Bearers protocols' (connecting to UTRAN via 'Iu'). Arrows indicate data flow between layers and entities.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +Figure 1: Iu UP protocol layer occurrence in UTRAN overall architecture (User Plane View). The diagram shows the protocol stack for the User Plane across three entities: UE, UTRAN, and CN. The UE and CN both have a 'NAS Data Streams' block at the top within the 'Non-Access Stratum'. Below this, in the 'Access Stratum', the UE has 'Radio protocols'. The UTRAN has 'Radio protocols' on the left (connecting to UE via 'Radio (Uu)') and a stack on the right consisting of 'Iu UP', 'User plane Data Bearers protocols', and 'Transport Layer'. The CN has 'Iu UP' and 'User plane Data Bearers protocols' (connecting to UTRAN via 'Iu'). Arrows indicate data flow between layers and entities. + +**Figure 1: Iu UP protocol layer occurrence in UTRAN overall architecture (User Plane View)** + +## 4.2 Operational and Functional Aspects + +### 4.2.1 Iu UP protocol modes of operation + +The Iu UP protocol operates in mode according to the concept described in earlier subclause. + +Modes of operation of the protocol are defined: + +- 1) Transparent mode (TrM); +- 2) Support mode for predefined SDU size (SMpSDU). + +Determination of the Iu UP protocol instance mode of operation is a CN decision taken at RAB establishment based on e.g. the RAB characteristics. It is signalled in the Radio Network layer control plane at RAB assignment and relocation for each RAB. It is internally indicated to the Iu UP protocol layer at user plane establishment. + +The choice of a mode is bound to the nature of the associated RAB and cannot be changed unless the RAB is changed. + +### 4.2.2 Transparent mode (TrM) + +The transparent mode is intended for those RABs that do not require any particular feature from the Iu UP protocol other than transfer of user data. + +The following figure illustrates the transparent mode of operation of the Iu UP protocol layer. + +![Figure 2: Iu UP protocol layer in transparent occurrence over Iu interface. The diagram shows the UTRAN and CN connected via the Iu Interface. In the UTRAN, the Iu UP layer is in transparent mode, and in the CN, it is also in transparent mode. Data flows from the Radio Interface Protocols through the Iu UP layer in transparent mode, then through the TNL-SAP, across the Iu Interface, through the TNL-SAP, through the Iu UP layer in transparent mode, and finally to the RNL-SAP. The RNL-SAP is connected to the Non Access Stratum and Access Stratum in the CN.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +Figure 2: Iu UP protocol layer in transparent occurrence over Iu interface. The diagram shows the UTRAN and CN connected via the Iu Interface. In the UTRAN, the Iu UP layer is in transparent mode, and in the CN, it is also in transparent mode. Data flows from the Radio Interface Protocols through the Iu UP layer in transparent mode, then through the TNL-SAP, across the Iu Interface, through the TNL-SAP, through the Iu UP layer in transparent mode, and finally to the RNL-SAP. The RNL-SAP is connected to the Non Access Stratum and Access Stratum in the CN. + +**Figure 2: Iu UP protocol layer in transparent occurrence over Iu interface** + +In this mode, the Iu UP protocol instance does not perform any Iu UP protocol information exchange with its peer over the Iu interface: no Iu frame is sent. The Iu UP protocol layer is crossed through by PDUs being exchanged between upper layers and transport network layer. + +For instance, the transfer of GTP-U PDUs could utilise the transparent mode of the Iu UP protocol. + +This release of the specification defines transparent mode version 1, the same as in the release 99 specification. + +### 4.2.3 Support mode + +The support modes are intended for those RABs that do require particular features from the Iu UP protocol in addition to transfer of user data. When operating in a support mode, the peer Iu UP protocol instances exchange Iu UP frames whereas in transparent mode, no Iu UP frames are generated. + +The following figure illustrates the functional model of the Iu UP protocol layer in support mode of operation. + +![Figure 3: Iu UP protocol layer in support mode occurrence over Iu interface. The diagram shows the UTRAN and CN connected via the Iu Interface. In the UTRAN, the Iu UP layer is in support mode, containing Support Mode Functions. In the CN, it is also in support mode, containing Support Mode Functions. Data flows from the Radio Interface Protocols through the Iu UP layer in support mode, then through the TNL-SAP, across the Iu Interface, through the TNL-SAP, through the Iu UP layer in support mode, and finally to the RNL-SAP. The RNL-SAP is connected to the Non Access Stratum and Access Stratum in the CN. A red double-headed arrow labeled 'Transfer of Iu UP protocol frames' indicates the exchange of frames between the Support Mode Functions in the UTRAN and CN.](63e0c22852c26699d0bd095a2d796bab_img.jpg) + +Figure 3: Iu UP protocol layer in support mode occurrence over Iu interface. The diagram shows the UTRAN and CN connected via the Iu Interface. In the UTRAN, the Iu UP layer is in support mode, containing Support Mode Functions. In the CN, it is also in support mode, containing Support Mode Functions. Data flows from the Radio Interface Protocols through the Iu UP layer in support mode, then through the TNL-SAP, across the Iu Interface, through the TNL-SAP, through the Iu UP layer in support mode, and finally to the RNL-SAP. The RNL-SAP is connected to the Non Access Stratum and Access Stratum in the CN. A red double-headed arrow labeled 'Transfer of Iu UP protocol frames' indicates the exchange of frames between the Support Mode Functions in the UTRAN and CN. + +**Figure 3: Iu UP protocol layer in support mode occurrence over Iu interface** + +Some RABs requesting Iu UP protocol support, constrain the Iu UP protocol and possibly the radio interface protocols in specific ways. For instance, certain RABs can have variable predefined rates. + +The Iu UP support mode is prepared to support variations. + +The only support mode defined here is the: + +- Support mode for predefined SDU size (SMpSDU). + +For instance, the transfer of AMR speech PDUs would utilise the support mode for predefined SDU size of the Iu UP protocol because it requires some Procedure Control functions and some NAS Data Streams specific functions while the sizes of the user data being transferred can vary in a predefined manner. + +This release of the specification defines the Support mode for predefined SDU sizes version 2. The Support mode for predefined SDU sizes version 1 (see release 99 of this specification) shall also be supported by a 3GPP implementation compliant to this release of the specification in order to be backward compatible with release 99. + +# --- 5 Transparent mode, version 1 + +## 5.1 General + +### 5.1.1 Operation of the Iu UP in Transparent mode + +The Iu UP layer in transparent mode is present in the Iu User plane for transferring data transparently over the Iu interface. + +The two strata communicate through a Service Access Point for Non Access Stratum (NAS) Data Streams transfer. + +### 5.1.2 Interfaces of the Iu UP protocol layer in Transparent mode + +Interfaces of the Iu UP protocol layer in transparent mode are the transport network layer and the upper layers. The Iu UP protocol layer in transparent mode is an empty layer through which NAS Data Streams PDUs are crossing between the Transport Network Layer and upper layers. + +The Iu UP protocol layer in transparent mode is using services of the Transport layers in order to transfer the Iu UP PDUs over the Iu interface. + +## 5.2 Iu UP Protocol layer Services in Transparent mode + +The following functions are needed to support this mode: + +- Transfer of user data. + +## 5.3 Services Expected from the UP Data Transport layer + +The Iu UP protocol layer in transparent mode expects the following services from the Transport Network Layer: + +- Transfer of user data. +- Delivery of SDUs in sequence when requested by the RAB parameter *Delivery Order* IE (TS 25.413 [3]). + +## 5.4 Elements for Iu UP communication in Transparent mode + +### 5.4.1 Frame Format for transparent mode + +The following shows the format of the PDU crossing the Iu UP protocol layer in transparent mode. This frame is transferred transparently between the Iu UP protocol upper layers and transport network layer (TNL-SAP). + +![Figure 4: Frame format for transparent mode. The diagram shows a rectangular box labeled 'Payload'. To the right of the box, there is a vertical ellipsis (five dots) between the labels 'Oct 1' at the top and 'Oct n' at the bottom, indicating a variable length of octets.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +A rectangular box is centered, labeled "Payload". To its right, a vertical column of five dots represents a sequence. At the top of this column is the label "Oct 1" and at the bottom is the label "Oct n", indicating that the payload consists of a sequence of octets from 1 to n. + +Figure 4: Frame format for transparent mode. The diagram shows a rectangular box labeled 'Payload'. To the right of the box, there is a vertical ellipsis (five dots) between the labels 'Oct 1' at the top and 'Oct n' at the bottom, indicating a variable length of octets. + +**Figure 4: Frame format for transparent mode** + +This PDU has a variable length of n octets, whose maximum range depends on the type of user data (e.g. IP packet). No explicit length indication is visible at the Iu UP protocol layer. + +# 6 Support mode for predefined SDU sizes, version 2 + +## 6.1 General + +### 6.1.1 Operation of the Iu UP in Support mode + +The Iu UP protocol layer in Support mode is present for data streams that need frame handling in the UP. + +The two strata communicate through a Service Access Point for Non Access Stratum (NAS) Data Streams transfer. + +### 6.1.2 Interfaces of the Iu UP protocol layer in Support mode + +As part of the Access Stratum responsibility, the Iu UP protocol layer in support mode provides the services and functions that are necessary to handle non access stratum data streams. The Iu UP protocol layer in support mode is providing these services to the UP upper layers through a Dedicated Service Access Point used for Information Transfer as specified in TS 23.110 [5]. + +The Iu UP protocol layer in support mode is using services of the Transport layers in order to transfer the Iu UP PDUs over the Iu interface. + +## 6.2 Iu UP Protocol layer Services in Support mode + +### **Support mode for predefined SDU size Service** + +The following functions are needed to support this mode: + +- Transfer of user data; +- Initialisation; +- Rate control; +- Time alignment; +- Handling of error event; +- Frame quality classification. + +## 6.3 Services Expected from the UP Data Transport layer + +The Iu UP protocol layer in Support Mode expects the following services from the Transport Network Layer: + +- Transfer of user data. +- Delivery of SDUs in sequence when requested by the RAB parameter *Delivery Order* IE (TS 25.413 [3]). + +## 6.4 Functions of the Iu UP Protocol Layer in Support mode + +### 6.4.1 Functional model of the Iu UP Protocol Layer in Support mode + +![Figure 5: Functional model of the Iu UP protocol layer in Support mode. The diagram shows the functional architecture of the Iu UP layer between the UTRAN and the CN. On the UTRAN side, the Iu UP layer in support mode is connected to Radio Interface Protocols and the RNL-SAP. It contains three main functional blocks: NAS Data Streams specific functions, Procedure Control functions, and a Frame Handler function. The CN side also features an Iu UP layer in support mode with similar functional blocks, connected to the RNL-SAP and the TNL-SAP. The RNL-SAP is divided into Non Access Stratum and Access Stratum. The TNL-SAP is shown at the bottom of both sides, indicating the transport layer connection.](9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg) + +Figure 5: Functional model of the Iu UP protocol layer in Support mode. The diagram shows the functional architecture of the Iu UP layer between the UTRAN and the CN. On the UTRAN side, the Iu UP layer in support mode is connected to Radio Interface Protocols and the RNL-SAP. It contains three main functional blocks: NAS Data Streams specific functions, Procedure Control functions, and a Frame Handler function. The CN side also features an Iu UP layer in support mode with similar functional blocks, connected to the RNL-SAP and the TNL-SAP. The RNL-SAP is divided into Non Access Stratum and Access Stratum. The TNL-SAP is shown at the bottom of both sides, indicating the transport layer connection. + +**Figure 5: Functional model of the Iu UP protocol layer in Support mode** + +The Iu UP protocol layer in Support mode is made of three sets of functions: + +- 1) Frame Handler function; +- 2) Procedure Control functions; +- 3) Non Access Stratum Data Streams specific functions. + +### 6.4.2 Frame Handler function + +This function is responsible for framing and de-framing the different parts of an Iu UP protocol frame. This function takes the different parts of the Iu UP protocol frame and set the control part field to the correct values, including the handling of the frame number. It also ensures that the frame control part is semantically correct. This function is responsible for interacting with the Transport layers. This function is also responsible for the CRC check of the Iu UP frame header. The Iu UP frame with header CRC check error is discarded. + +### 6.4.3 Procedure Control functions + +This set of functions offers the control of a number of procedures handled at the Iu UP protocol level. These functions are responsible for the procedure control part of the Iu UP frames. + +Namely, these procedures are: + +- **Rate Control:** is the procedure which controls over the Iu UP the maximum rate that is allowed to be sent downlink among the rates that can be controlled. The set of rates is represented by RFCI indicators. The function controlling this procedure interacts with functions outside of the Iu UP protocol layer. +- **Initialisation:** is the procedure which controls the exchange of initialisation information that is required for operation in support mode for predefined SDU size. Such information can contain the RFCI Set to be used until termination of the connection or until the next Initialisation procedure. This procedure is also used for negotiating the version of the Iu UP Mode among the versions the CN requested for the related RAB. +- **Time Alignment:** is the procedure that controls the timing of the downlink data to the RNC over Iu. The function controlling this procedure interacts with functions outside of the Iu UP protocol layer. + +- **Handling of Error Event:** is the procedure that controls the information exchanged over the Iu related to detection of a fault situation. The function controlling this procedure interacts with functions outside of the Iu UP protocol layer. + +### 6.4.4 Non Access Stratum Data Streams specific function(s) + +These functions are responsible for a "limited manipulation" of the payload. These functions are responsible for the CRC check and calculation of the Iu UP frame payload part. These functions are also responsible for the Frame Quality Classification handling as described below. + +These functions interact with the upper layers by exchanging Iu data stream blocks of Iu UP frame payload. These functions also handle the padding and depadding of the Iu UP frame payloads when needed. + +These functions interact with the Procedure Control functions. + +These functions provide service access to the upper layers for the Procedure Control functions. + +#### 6.4.4.1 Frame Quality Classification function + +##### 6.4.4.1.1 General + +On the Iu UP in Support Mode the frames are classified with the Frame Quality Classifier (FQC). This classifying is based on the radio frame classification and the setting of the RAB attribute *Delivery of erroneous SDU* IE. The RAB attribute *Delivery of erroneous SDU* IE tells if erroneous frames shall be delivered or not. + +Figure 6 shows the main input and output information for frame quality classification function on the Iu UP. + +![Figure 6: Frame quality classification in Iu UP. The diagram shows the Iu Interface between UTRAN and CN. On the UTRAN side, 'Radio Interface Protocols' feed into 'Support Mode Functions'. These functions output 'PDU or no PDU As a result of FQC AND CRC' and 'FQC, CRC'. On the CN side, 'Support Mode Functions' receive 'FQC, CRC' and output 'Frame Quality Classification Result of FQC AND CRC results'. The CN side is divided into 'Non Access Stratum' and 'Access Stratum' by a horizontal line. Interfaces RNL-SAP and TNL-SAP are shown with circular symbols and arrows. A central red double-headed arrow indicates 'Transfer of Iu UP protocol frames'.](2de714cedbbdd36f901f71bafa78f75a_img.jpg) + +Figure 6: Frame quality classification in Iu UP. The diagram shows the Iu Interface between UTRAN and CN. On the UTRAN side, 'Radio Interface Protocols' feed into 'Support Mode Functions'. These functions output 'PDU or no PDU As a result of FQC AND CRC' and 'FQC, CRC'. On the CN side, 'Support Mode Functions' receive 'FQC, CRC' and output 'Frame Quality Classification Result of FQC AND CRC results'. The CN side is divided into 'Non Access Stratum' and 'Access Stratum' by a horizontal line. Interfaces RNL-SAP and TNL-SAP are shown with circular symbols and arrows. A central red double-headed arrow indicates 'Transfer of Iu UP protocol frames'. + +**Figure 6: Frame quality classification in Iu UP** + +##### 6.4.4.1.2 Handling of FQC information in uplink path + +###### 6.4.4.1.2.1 Handling of FQC information at RNC + +In SRNC on the sending side, the Support Mode Functions takes as input the radio frame quality information together with the frame. Based on this, the *Frame Quality Classification (FQC)* IE is set for the frame, a CRC is or is not added (depending on PDU type) and the frame is sent to CN. The following steps shall be sequentially applied to derive the SRNC behaviour and the *Frame Quality Classification (FQC)* IE setting: + +- If there is at least one subflow with the *Delivery of erroneous SDU* IE set to "No" and for at least one of those subflows the radio frame classification is "Bad" then the Iu UP frame shall not be sent; + +- b) Otherwise, if there is at least one subflow with the *Delivery of erroneous SDU* IE set to "Yes" and for at least one of those subflows the radio frame classification is "Bad" then the Iu UP frame shall be sent with *Frame Quality Classification (FQC)* IE set to "frame bad due to radio"; +- c) Otherwise the Iu UP frame shall be sent with *Frame Quality Classification (FQC)* IE set to "frame good". + +###### 6.4.4.1.2.2 Handling of FQC information at CN + +The Support Mode Functions in CN on the receiving side makes a CRC check of the frame payload, if CRC is present and passes the appropriate frame and the appropriate frame quality classification information through the RNL-SAP. The following steps shall be sequentially applied to derive the CN behaviour and the FQC field setting: + +- a) If a CRC is available and the CRC check indicates that the Iu UP frame payload part is corrupted and at least one subflow has the *Delivery of erroneous SDU* IE set to "No", then the Iu UP frame shall be dropped; +- b) Otherwise, if a CRC is available and the CRC check indicates that the Iu UP frame payload part is corrupted and at least one subflow has the *Delivery of erroneous SDU* IE set to "Yes", then the Iu UP frame shall be forwarded with the FQC set to "frame bad"; +- c) Otherwise the Iu UP frame shall be forwarded with the FQC as set by UTRAN. + +##### 6.4.4.1.3 Handling of FQC information in downlink path + +The Support Mode Functions in CN on the sending side adds a CRC, if necessary to the frame payload and passes it together with the FQC. If the payload stems from a transcoding unit of the NAS within the CN the FQC is always set to "frame good". Otherwise it may be set by a partner peer entity residing in another RNC. + +The Support Mode Functions in SRNC then makes a CRC-check, if the CRC is present. Based on the CRC check, a decision is made whether to deliver the frame or not based on the following sequential steps: + +- a) If a CRC is available and the CRC check indicates that the Iu UP frame payload part is corrupted then the frame shall be dropped; +- b) Otherwise, if the FQC value of the Iu UP frame is set to "frame bad" or "frame bad due to radio" then the frame shall be dropped, regardless of the CRC check indication; +- c) Otherwise, the frame shall be passed to radio interface protocols. + +NOTE: The case where SRNC receives a frame with the FQC set to "frame bad due to radio" (respectively: "frame bad"), corresponds to a TrFO (respectively: TFO) case. The frame is then trashed by the receiving RNC since there is currently no means to pass the frame quality indicator down to the UE. + +## 6.5 Elementary procedures + +### 6.5.1 Transfer of User Data procedure + +#### 6.5.1.1 Successful operation + +The purpose of the Transfer of User Data procedure is to transfer Iu UP frames between the two Iu UP protocol layers at both ends of the Iu interface. Since an Iu UP instance is associated to a RAB and a RAB only, the user data being transferred only relate to the associated RAB. + +The procedure is controlled at both ends of the Iu UP instance i.e. SRNC and the CN. Exceptions in case of TrFO, where the partner peer entity does not reside within the serving CN node are described in subclause 4.1 and TS 23.153 [13]. + +The Transfer of User Data procedure is invoked whenever user data for that particular RAB needs to be sent across the Iu interface. + +The procedure is invoked by the Iu UP upper layers upon reception of the upper layer PDU and associated control information: RFCI. + +The upper layers may deliver a frame quality classification information together with the RFCI. + +The NAS Data Streams specific functions makes the padding of the payload (if needed) so that the Iu UP frame payload will be an integer number of octets. Then the NAS Data Streams specific functions perform, if needed, CRC calculation of the Iu frame payload and passes the Iu UP frame payload down to the Frame Handler function together with the RFCI. + +The Frame Handler function retrieves the frame number from its internal memory, formats the frame header and frame payload into the appropriate PDU Type and sends the Iu UP frame PDU to the lower layers for transfer across the Iu interface. If the UTRAN initialises the RAB it shall base the selection of the PDU type (in both directions) on the reliability attributes (see TS 25.413 [3]) for the RAB. If the reliability attribute *Delivery of Erroneous SDU* IE equals "no-error-detection-consideration" for all subflows then PDU Type 1 shall be used, otherwise PDU Type 0 shall be used. + +For RABs with the traffic class conversational or streaming the frame number shall be based on time (stepped at each ITI). For RABs with another type of traffic class the frame numbering shall be based on sent Iu UP PDU (stepped at each sent Iu UP PDU). See description of *Frame Number* IE. + +Upon reception of a user data frame, the Iu UP protocol layer checks the consistency of the Iu UP frame as follows: + +- The Frame Handler function checks the consistency of the frame header and the consistency of the frame number. If a frame loss is detected due a gap in the sequence of the received frame numbers (for a RAB where frame numbers does not relate to time), this shall be reported to the Procedure Control function. If correct, the Frame Handler function stores the frame number and passes the Iu UP frame payload and associated CRC, if any to the NAS Data Streams specific functions. The received RFCI is passed to the Procedure Control function; +- The NAS Data Streams specific functions check the payload CRC, if any. If the RFCI is correct (i.e. RFCI is used at Initialisation) and matches the Iu UP frame payload (i.e. frame payload is not too short for the RFCI) as indicated by the Procedure Control functions, the NAS Data Streams specific functions removes the padding bits and the spare extension field when present from the Iu UP frame payload based on the RFCI information. Then the NAS Data Streams specific functions forwards to the upper layers the RFCI and the payload. + +![Diagram illustrating successful transfers of user data between RNC/CN and CN/RNC. The diagram shows two vertical lines representing the RNC/CN (left) and CN/RNC (right) entities. Horizontal arrows represent the transfer of user data (RFCI, payload) between the entities. There are four arrows in total, alternating directions, representing bidirectional data transfer.](51db757d054ce1ce83c436a3578b56ca_img.jpg) + +``` + +sequenceDiagram + participant RNC/CN + participant CN/RNC + Note over RNC/CN, CN/RNC: TRANSFER OF USER DATA (RFCI, payload) + RNC/CN->>CN/RNC: + CN/RNC->>RNC/CN: + RNC/CN->>CN/RNC: + CN/RNC->>RNC/CN: + +``` + +Diagram illustrating successful transfers of user data between RNC/CN and CN/RNC. The diagram shows two vertical lines representing the RNC/CN (left) and CN/RNC (right) entities. Horizontal arrows represent the transfer of user data (RFCI, payload) between the entities. There are four arrows in total, alternating directions, representing bidirectional data transfer. + +Figure 7: Successful Transfers of User Data + +#### 6.5.1.2 Unsuccessful operation + +If the Iu UP frame carrying the user data is incorrectly formatted or cannot be correctly treated by the receiving Iu UP protocol layer, the Iu UP protocol layer shall either discard the frame or pass it to the upper layers with a frame classification indicating a corrupted frame. This decision is based on configuration data of the Iu UP instance for that particular RAB (i.e. if the RAB requests delivery of corrupted frame). + +If the Iu UP protocol layer detects a frame loss because of a gap in the received frame number sequence while the frame number does not relate to time (see description of *Frame Number* IE), the receiving Iu UP protocol layer shall report this to the Procedure Control function. + +![Figure 8: Unsuccessful Transfers of User Data. The diagram shows two entities, RNC/CN and CN/RNC, with a 'TRANSFER OF USER DATA (RFCI, payload)' label above them. Two arrows represent data transfer attempts. The first arrow, labeled '1)', is shown with a wavy line and a red lightning bolt, indicating a corrupted frame. The second arrow, labeled '2)', is shown with a red 'X' over it, indicating a detection of frame loss.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +Figure 8: Unsuccessful Transfers of User Data. The diagram shows two entities, RNC/CN and CN/RNC, with a 'TRANSFER OF USER DATA (RFCI, payload)' label above them. Two arrows represent data transfer attempts. The first arrow, labeled '1)', is shown with a wavy line and a red lightning bolt, indicating a corrupted frame. The second arrow, labeled '2)', is shown with a red 'X' over it, indicating a detection of frame loss. + +**Figure 8: Unsuccessful Transfers of User Data: 1) Corrupted Frame, 2) Detection of Frame loss** + +### 6.5.2 Initialisation procedure + +#### 6.5.2.1 Successful operation + +This procedure is mandatory for RABs using the support mode for predefined SDU size. The purpose of the Initialisation procedure is to configure both termination points of the Iu UP with RAB Subflows Combinations, RFCIs, and associated RAB Sub Flows SDU sizes necessary to be supported during the transfer of user data phase. + +Additional parameters may also be passed, such as the Inter PDU Timing Interval (IPTI) information. + +The Initialisation procedure may be controlled at both end of the Iu access point, i.e. the CN and UTRAN. + +The Initialisation procedure is invoked whenever indicated by the Iu UP Procedure Control function e.g. as a result of a relocation of SRNS or at RAB establishment over Iu or if the CN decides to resolve RFCI mismatch in case of TrFO (see TS 23.153 [13]). The Initialisation procedure shall not be re-invoked by the SRNC for the RAB without a RAB modification requested via RANAP (TS 25.413 [3]). + +When this procedure is invoked all other Iu UP procedures are suspended until termination of the Initialisation procedure. + +The Iu UP protocol entity invoking this procedure shall indicate the Iu UP Mode version of the INITIALISATION control frame it uses in the Iu UP Mode Version field. It shall also indicate the Iu UP Mode versions it proposes among the versions the CN requested for the related RAB and which it supports in the Iu UP Mode Versions Supported field. The sender should use the lowest Iu UP Mode version for the initialisation that has enough information to initialise the highest proposed protocol version. + +The invoking entity allocates a RAB sub-Flow Combination indicator (RFCI) to each RAB sub-Flow Combination it initialises. One requirement on which RAB sub-Flow Combinations to initialise, is that all requested compound RAB sub-Flow Combination SDU sizes shall be configured, except in the case when also version 1 of the user plane mode was included as an alternative in the request over RANAP. In that case, it is allowed to initialise just a subset of the requested RAB sub-Flow Combinations, however at least one of the requested RAB sub-Flow Combinations equal or above the guaranteed bitrate shall be initialised. The association of indicators to RAB Flow Combinations is valid for both the uplink and downlink direction in the Iu UP until a new Initialisation procedure is performed or the connection is terminated. + +The Procedure Control function may also generate additional Iu UP protocol parameters necessary for the RAB service to operate properly over Iu. + +To each RAB sub-Flow combination indicator is associated the size of each RAB sub-Flow SDU of that combination. The list of RAB sub-Flow Combination Indicators and their respective SDU sizes constitutes the RAB sub-Flow Combination set passed over the Iu UP in the INITIALISATION control frame i.e. into an appropriate Iu UP PDU Type. + +The first RAB Sub-flow Combination proposed in the list of RAB Sub-Flow Combinations corresponds to the maximum bit rate allowed to be used when starting the communication phase i.e. until the first RATE CONTROL control frame occurs. The RAB Sub-flow Combinations for rates below the guaranteed bit rate as specified in the RAB parameters (indicated to the Iu-UP at the RNC) shall not be used as the first RAB Sub-flow Combination in the proposed list of RAB Sub-Flow Combinations. + +Any RAB Sub-Flow Combination of the set that is initialised shall be supported by the two Iu UP termination points and may optionally be used by the sender (except for the first in the list that shall be used when starting). In particular, the use by the sender of the RFC "NO\_DATA" is optional even when it is included in the Initialisation procedure. + +Conversely, any RAB Sub-Flow Combination that is not part of the initialised set shall not be used even if supported. In particular, the two Iu UP termination points shall be capable of operating without the use of the RFC "NO\_DATA". + +The complete set of information is framed by the Iu UP Frame Handler function and transferred in an Iu UP INITIALISATION control frame. If needed, the INITIALISATION control frame CRC is calculated and set accordingly in the respective frame field. + +A supervision timer $T_{INIT}$ is started after sending the Iu UP INITIALISATION control frame. This timer supervises the reception of the initialisation acknowledgement frame. + +Upon reception of a frame indicating that an Initialisation procedure is active in the peer Iu UP entity, the Iu UP protocol layer forwards the whole protocol information contained in the INITIALISATION control frame to the upper layers. It also stores the RAB sub-Flow Combination set (and thus replaces a possible previous set) in order to control during the transfer of user data, that the Iu UP payload is correctly formatted (e.g. RFCI matches the expected Iu UP frame payload total length). The peer Iu UP entity receiving the INITIALISATION control frame shall choose a version that it supports among the proposed versions indicated by the sender for which it has enough initialisation information. + +If the INITIALISATION control frame is correctly formatted and treated by the receiving Iu UP protocol layer, and at least one of the proposed versions is supported, this latter sends an INITIALISATION POSITIVE ACKNOWLEDGEMENT frame using the version of the Iu UP Mode that is chosen. + +Upon reception of an initialisation acknowledgement frame, the Iu UP protocol layer in the SRNC stops the supervision timer $T_{INIT}$ . + +If the Initialisation procedure requires that several frames are to be sent, each frame shall be acknowledged individually (i.e. any frame to be sent shall wait for the acknowledgement of the previous sent frame to be received before being sent. The supervision timer shall be used individually for each frame being sent. + +The successful operation of the Initialisation procedure may require that one or several chained frames are positively acknowledged. The number of INITIALISATION control frames in such a chain shall not exceed 4. Each chained frame shall be positively acknowledged before the one with the next frame number can be sent. + +The *PDU Type 14 Frame Number* IE of an INITIALISATION control frame shall always be set to "0" when the chain has only one frame. When several INITIALISATION control frames are used in a chain the *PDU Type 14 Frame Number* IE shall be set to "0" for the first one and incremented by one in the sending direction for each new frame in the chain. The positive acknowledgement or negative acknowledgement shall carry the frame number of the frame being acknowledged. + +Upon reception of an INITIALISATION NEGATIVE ACKNOWLEDGEMENT control frame, an erroneous acknowledgement or at timer $T_{INIT}$ expiry, the Iu UP protocol entity controlling the Initialisation procedure shall reset and restart the $T_{INIT}$ supervision timer and repeat one INITIALISATION control frame with the same frame number. The repetition shall be performed up to $N_{INIT}$ times, $N_{INIT}$ being chosen by the operator (default $N_{INIT} = 3$ ). The $N_{INIT}$ (maximum number of allowed repetition) is the aggregate count for each frame in the chain and is restart each time a frame is positively acknowledged. + +![Sequence diagram of Successful Initialisation of Iu UP for m RFCIs. It shows an exchange between RNC/CN and CN/RNC. RNC/CN sends an INITIALISATION frame containing RFCI, SDU sizes, and optional IPTIs. CN/RNC responds with an INITIALISATION ACK. This is followed by a Transfer Of User Data phase.](1bf34e86af3591c80bfbc1c318f811c0_img.jpg) + +``` + +sequenceDiagram + participant RNC/CN + participant CN/RNC + RNC/CN->>CN/RNC: * INITIALISATION ((RFCI, SDU sizes[, IPTIs2)])m) + CN/RNC-->>RNC/CN: INITIALISATION ACK + Note over RNC/CN, CN/RNC: Transfer Of User Data + +``` + +\* can be repeated $N_{INIT}$ times +2) optional + +Sequence diagram of Successful Initialisation of Iu UP for m RFCIs. It shows an exchange between RNC/CN and CN/RNC. RNC/CN sends an INITIALISATION frame containing RFCI, SDU sizes, and optional IPTIs. CN/RNC responds with an INITIALISATION ACK. This is followed by a Transfer Of User Data phase. + +**Figure 9: Successful Initialisation of Iu UP for m RFCIs** + +#### 6.5.2.2 Unsuccessful operation + +If the INITIALISATION control frame is incorrectly formatted and cannot be correctly treated by the receiving Iu UP protocol layer, this latter sends an INITIALISATION NEGATIVE ACKNOWLEDGEMENT control frame. + +If the receiver does not support the Iu UP Mode version used for the Initialisation procedure, it shall send a negative acknowledgement using the highest version it supports among the versions proposed by the sender. If none of the proposed versions are supported, the receiver shall respond with a negative acknowledgement using the highest version it supports. + +After $N_{INIT}$ successive negative acknowledgment, erroneous acknowledgment or $T_{INIT}$ expiry for INITIALISATION control frames having the same frame number, the Initialisation procedure is unsuccessfully terminated and the Iu UP protocol layers in RNC take appropriate local actions. + +![Sequence diagram showing the unsuccessful initialisation of Iu UP between RNC and CN. The RNC sends an INITIALISATION frame to the CN. The CN responds with an INITIALISATION NACK. The RNC then shows a sequence of N_INIT repetitions of the INITIALISATION frame, indicated by a red vertical bar and a bracket. The diagram is annotated with: 1) N_INIT negative acknowledgement, and 2) N_INIT expiries of timer T_INIT. A legend indicates: * after N_INIT repetitions, 2) optional.](73dff6b45b2b9ffd384bab3235f869af_img.jpg) + +``` + +sequenceDiagram + participant RNC + participant CN + Note left of RNC: 1) N_INIT negative acknowledgement +2) N_INIT expiries of timer T_INIT + RNC->>CN: INITIALISATION ((RFCI, SDU sizes[, IPTIs2])m) + CN-->>RNC: INITIALISATION NACK + Note left of RNC: * after NINIT repetitions +2) optional + Note left of RNC: 1) + Note left of RNC: 2) + +``` + +Sequence diagram showing the unsuccessful initialisation of Iu UP between RNC and CN. The RNC sends an INITIALISATION frame to the CN. The CN responds with an INITIALISATION NACK. The RNC then shows a sequence of N\_INIT repetitions of the INITIALISATION frame, indicated by a red vertical bar and a bracket. The diagram is annotated with: 1) N\_INIT negative acknowledgement, and 2) N\_INIT expiries of timer T\_INIT. A legend indicates: \* after N\_INIT repetitions, 2) optional. + +**Figure 10: Unsuccessful initialisation of Iu UP: 1) $N_{INIT}$ negative acknowledgement or 2) $N_{INIT}$ expiries of timer $T_{INIT}$** + +### 6.5.3 Iu Rate Control procedure + +#### 6.5.3.1 Successful operation + +The purpose of the Iu Rate Control procedure is to signal to the peer Iu UP protocol layer the maximum rate over Iu in the reverse direction of the sent RATE CONTROL control frame. + +The Rate Control procedure over Iu UP is normally controlled by the entity controlling the rate control over UTRAN i.e. the SRNC. The Iu Rate Control procedure is invoked whenever the SRNC decides that the maximum rate permitted downlink over Iu shall be modified, or when a RATE CONTROL control frame is received from the CN. Within the context of TrFO the SRNC may also receive RATE CONTROL control frames from the TrFO partner. + +The rates that can be controlled by the SRNC are all the rates that are defined by the Iu-Initialisation procedure and which are above the guaranteed bitrate specified in the RAB parameters (indicated to the Iu UP at the RNC). Rates below or equal to the guaranteed bitrate, e.g. the lowest speech rate or the SID frames, cannot be controlled (i.e. cannot be forbidden) by the SRNC (exceptionally, in case of version 1 any of the initialised rates equal to or above the guaranteed bitrate can be controlled). + +The procedure can be signalled at any time when Transfer of User Data procedure is not suspended by another Procedure Control function. When the user plane was initiated due to SRNS relocation reasons no rate control shall be signalled before the reception of the relocation execution trigger (see TS 25.413 [3]). At the reception of the relocation execution trigger the RNC shall start the Iu Rate Control procedure. This enables both TrFO partners to exchange current maximum rates and proceed user data transport based on latest rate decisions. + +The Procedure Control function upon request of upper layer prepares the RATE CONTROL control frame payload containing the maximum rate of the reverse direction of the RATE CONTROL control frame. To align the Iu Rate Control procedure with version 1 of the Iu UP protocol the permitted maximum rate is given as a set of RFCI indicators, that shall contain the maximum rate and all rates below the maximum rate, i.e. all rate controllable and non rate controllable rates. In the context of TrFO and TFO the Iu Rate Control procedure may also be controlled by a remote peer. + +The Frame Handler function calculates the frame CRC, formats the frame header into the appropriate PDU Type and sends the Iu UP frame PDU to the lower layers for transfer across the Iu interface. + +A supervision timer $T_{RC}$ is started after sending the Iu UP RATE CONTROL control frame. This timer supervises the reception of the rate control acknowledgement frame. Upon reception of a rate control acknowledgement frame, the Iu UP protocol layer in the SRNC stops the supervision timer $T_{RC}$ . + +Upon reception of a RATE CONTROL control frame, the Iu UP protocol layer checks the consistency of the Iu UP frame as follows: + +- The Frame Handler function checks the consistency of the frame header and associated CRC. If correct, the Frame Handler function passes Procedure Control part to the procedure control functions; +- The Procedure Control functions check that all RFCIs in the initial RFCI set are indicated as either allowed or barred. If the whole rate control information is correct, the Procedure Control functions passes the rate control information to the NAS Data Streams specific functions; +- The NAS Data Streams specific functions forward to the upper layers the complete protocol data in a Iu-UP-Status indication primitive; +- Upon reception of the Iu-UP-Status request primitive, the Procedure Control functions shall acknowledge the RATE CONTROL control frame by including its own maximum rate control information i.e. the permitted rates in the reverse direction of the RATE CONTROL ACK message. + +![Figure 11: Successful Rate Control. A sequence diagram showing two entities, RNC/CN on the left and CN/RNC on the right. The RNC/CN sends a 'RATE CONTROL (RFCI indicators)' message to the CN/RNC. The CN/RNC responds with a 'RATE CONTROL ACK (RFCI indicators)' message back to the RNC/CN.](5793a44ffdadd039928e2f9fe6daae06_img.jpg) + +``` + +sequenceDiagram + participant RNC/CN + participant CN/RNC + Note left of RNC/CN: Start T_RC timer + RNC/CN->>CN/RNC: RATE CONTROL (RFCI indicators) + CN/RNC-->>RNC/CN: RATE CONTROL ACK (RFCI indicators) + Note right of CN/RNC: Stop T_RC timer + +``` + +Figure 11: Successful Rate Control. A sequence diagram showing two entities, RNC/CN on the left and CN/RNC on the right. The RNC/CN sends a 'RATE CONTROL (RFCI indicators)' message to the CN/RNC. The CN/RNC responds with a 'RATE CONTROL ACK (RFCI indicators)' message back to the RNC/CN. + +Figure 11: Successful Rate Control + +Figure 12: Void + +#### 6.5.3.2 Unsuccessful operation + +If the Iu UP protocol layer receives a RATE CONTROL control frame that is badly formatted or corrupted, it shall ignore the RATE CONTROL control frame, but send a RATE CONTROL NEGATIVE ACKNOWLEDGEMENT control frame back (figure 13a). + +![Figure 13a: Negative Acknowledgement received from the peer. A sequence diagram showing two entities, RNC/CN on the left and CN/RNC on the right. The RNC/CN sends a 'RATE CONTROL' message to the CN/RNC. The CN/RNC receives it, but it is corrupted (indicated by a red lightning bolt). The CN/RNC then sends a 'RATE CONTROL NACK' message back to the RNC/CN. The RNC/CN receives the NACK and then retransmits the 'RATE CONTROL' message. The CN/RNC receives the retransmitted message correctly and sends a 'RATE CONTROL ACK' message back to the RNC/CN.](2834bdd6eb8540277e609decbb924003_img.jpg) + +``` + +sequenceDiagram + participant RNC/CN + participant CN/RNC + Note left of RNC/CN: Start T_RC timer + RNC/CN->>CN/RNC: RATE CONTROL + Note right of CN/RNC: Corrupted reception + CN/RNC-->>RNC/CN: RATE CONTROL NACK + Note left of RNC/CN: Retransmit + RNC/CN->>CN/RNC: RATE CONTROL + CN/RNC-->>RNC/CN: RATE CONTROL ACK + Note right of CN/RNC: Stop T_RC timer + +``` + +Figure 13a: Negative Acknowledgement received from the peer. A sequence diagram showing two entities, RNC/CN on the left and CN/RNC on the right. The RNC/CN sends a 'RATE CONTROL' message to the CN/RNC. The CN/RNC receives it, but it is corrupted (indicated by a red lightning bolt). The CN/RNC then sends a 'RATE CONTROL NACK' message back to the RNC/CN. The RNC/CN receives the NACK and then retransmits the 'RATE CONTROL' message. The CN/RNC receives the retransmitted message correctly and sends a 'RATE CONTROL ACK' message back to the RNC/CN. + +Figure 13a: Negative Acknowledgement received from the peer + +If the Iu UP in the SRNC detects that the RATE CONTROL control frame has not been correctly interpreted or received (e.g. the observed rate is outside the set of permitted rates in the reverse direction of the RATE CONTROL control frame (figure 13b), or a RATE CONTROL NEGATIVE ACKNOWLEDGEMENT control frame has been received, or no RATE CONTROL POSITIVE ACKNOWLEDGEMENT control frame was received before the supervision timer $T_{RC}$ expires (Figure 13c)), the Iu UP shall retrigger a Iu Rate Control procedure. If after $N_{RC}$ + +repetitions, the error situation persists, the Iu UP protocol layers (sending and receiving) take the appropriate local actions. + +![Sequence diagram showing unsuccessful transfer of rate control from RNC to CN due to frame loss and corrupted frames.](844077b3034f0030b404207db0ad76b4_img.jpg) + +This sequence diagram illustrates the interaction between an RNC and a CN. + 1) The RNC sends a 'RATE CONTROL (RFCI indicators)' message followed by 'TRANSFER OF USER DATA (not permitted rate, payload)'. The CN attempts to receive the data but fails, indicated by a yellow 'X' on the arrow. + 2) The RNC then retransmits the 'RATE CONTROL (RFCI indicators)' and 'TRANSFER OF USER DATA (not permitted rate, payload)' messages. The CN receives the second transfer attempt, but it is corrupted, indicated by a red jagged line on the arrow. + A bracket on the RNC side labeled '\*' indicates that these repetitions occur after $N_{RC}$ repetitions. + +Sequence diagram showing unsuccessful transfer of rate control from RNC to CN due to frame loss and corrupted frames. + +**Figure 13: Unsuccessful Transfer of rate control from RNC: 1) Frame loss 2) Corrupted Frame** + +![Sequence diagram showing unsuccessful transfer of rate control due to an undetected error.](ab846b81e78dbc8da2a6f9511e2f248a_img.jpg) + +This sequence diagram shows an RNC or CN sending a 'RATE CONTROL: undetected error' message to a CN or RNC. The CN or RNC responds with a 'RATE CONTROL ACK'. The sender then receives 'User Data with not permitted rates' and sends another 'RATE CONTROL' message. The CN or RNC responds with another 'RATE CONTROL ACK'. + +Sequence diagram showing unsuccessful transfer of rate control due to an undetected error. + +**Figure 13b: Unsuccessful Transfer of rate control: undetected error** + +![Sequence diagram showing unsuccessful transfer of rate control due to a lost rate control frame.](6f31cdb576d2f15c35c3f266e5f59211_img.jpg) + +This sequence diagram shows an RNC or CN sending a 'RATE CONTROL: lost frame' message to a CN or RNC. The CN or RNC does not receive it (marked with a yellow 'X'). The sender's $T_{RC}$ timer expires, indicated by a diamond symbol. The sender then retransmits the 'RATE CONTROL' message. The CN or RNC receives the retransmitted message and responds with a 'RATE CONTROL ACK'. + +Sequence diagram showing unsuccessful transfer of rate control due to a lost rate control frame. + +**Figure 13c: Unsuccessful Transfer of rate control: lost rate control** + +#### 6.5.3.2A Frequent Rate Control Procedures + +Typically a new RATE CONTROL control frame should not be sent in the same direction before the previous Iu Rate Control procedure was terminated successfully. + +If for some reasons (e.g. frequently received RATE CONTROL control frames from the CN in a TFO connection to GSM) a RATE CONTROL control frame has to be sent before the previous Iu Rate Control procedure was terminated successfully, then the previous Iu Rate Control procedure is defined as terminated successfully: the supervision timer $T_{RC}$ shall be stopped and acknowledgement frames (positive or negative) for the previous RATE CONTROL control frame shall be ignored, i.e. only the most recent Iu Rate Control procedure shall be active in the same direction. + +![Sequence diagram showing frequent Rate Control. The CN/RNC sends RATE CONTROL 1 then RATE CONTROL 2 to the RNC/CN. The RNC/CN responds with RATE CONTROL ACK 1 then RATE CONTROL ACK 2. An asterisk indicates that RATE CONTROL ACK 1 is ignored by the peer.](4b87467ad9642943235f48f7d4b59449_img.jpg) + +``` + +sequenceDiagram + participant RNC/CN + participant CN/RNC + CN/RNC->>RNC/CN: RATE CONTROL 1 + CN/RNC->>RNC/CN: RATE CONTROL 2 + RNC/CN->>CN/RNC: RATE CONTROL ACK 1 + Note right of CN/RNC: * + RNC/CN->>CN/RNC: RATE CONTROL ACK 2 + Note over RNC/CN,CN/RNC: * ignored by the peer + +``` + +Sequence diagram showing frequent Rate Control. The CN/RNC sends RATE CONTROL 1 then RATE CONTROL 2 to the RNC/CN. The RNC/CN responds with RATE CONTROL ACK 1 then RATE CONTROL ACK 2. An asterisk indicates that RATE CONTROL ACK 1 is ignored by the peer. + +**Figure 14: Frequent Rate Control: only most recent one is important** + +**Figure 15: Void** + +### 6.5.4 Time Alignment procedure + +#### 6.5.4.1 Successful operation + +The purpose of the Time Alignment procedure is to minimise the buffer delay in RNC by controlling the downlink transmission timing in the peer Iu UP protocol layer entity. + +The Time Alignment procedure is controlled by SRNC. + +The Time Alignment procedure is invoked whenever the SRNC detects the reception of Iu UP PDU at an inappropriate timing that leads to an unnecessary buffer delay. The actual detection of the trigger in SRNC is an internal SRNC matter and is out of the scope of the present document. + +The Iu UP protocol layer entity in SRNC indicates the peer entity the necessary amount of the delay or advance adjustment in the number of 500 $\mu$ s steps. + +A supervision timer $T_{TA}$ is started after sending the Iu UP TIME ALIGNMENT control frame. This timer supervises the reception of the time alignment acknowledgement frame. + +The requested Iu UP protocol layer entity in the peer node adjusts the transmission timing by the amount as indicated by SRNC. + +If the TIME ALIGNMENT control frame is correctly formatted and treated by the receiving Iu UP protocol layer and the time alignment is treated correctly by the upper layers, this latter sends an time alignment acknowledgement frame. + +Upon reception of a time alignment acknowledgement frame, the Iu UP protocol layer in the SRNC stops the supervision timer $T_{TA}$ . + +The procedure can be signalled at any time when transfer of user data is not suspended by another control procedure. + +![Sequence diagram for Successful Time Alignment between RNC and CN.](26d664119ad25250780f554633444e54_img.jpg) + +``` + +sequenceDiagram + participant RNC + participant CN + Note over RNC,CN: User data with bad timing + CN->>RNC: + RNC->>CN: TIME ALIGNMENT + CN->>RNC: ACK + Note over RNC,CN: User data with adjusted timing + CN->>RNC: + +``` + +A sequence diagram showing a successful time alignment. The CN sends user data with bad timing to the RNC. The RNC responds with a TIME ALIGNMENT control frame. The CN acknowledges with an ACK. Subsequently, the CN sends user data with adjusted timing to the RNC. A yellow triangle on the RNC lifeline indicates a timing adjustment period. + +Sequence diagram for Successful Time Alignment between RNC and CN. + +**Figure 15a: Successful Time Alignment** + +**Figure 16: Void** + +#### 6.5.4.2 Unsuccessful operation + +If the TIME ALIGNMENT control frame could not be handled by the peer side, the peer side should send a NACK with a corresponding cause. When the Iu UP protocol layer in the SRNC receives a NACK with cause "Time Alignment not supported", then the SRNC shall not send additional TIME ALIGNMENT control frames for that RAB (unless the Iu UP conditions change for that RAB). The cause value "Requested Time Alignment not possible" is used to indicate that the requested time alignment was not possible at that moment. At a later moment the SRNC may initiate a new TIME ALIGNMENT control frame when needed. If the TIME ALIGNMENT control frame is received by the RNC, it shall respond with a NACK with the cause "Time Alignment not supported". + +If the Iu UP protocol layer in the SRNC detects that the TIME ALIGNMENT control frame has not been correctly interpreted or received, i.e. NACK received or timer expires, and the time alignment need still persists, the Iu UP should retrigger a Time Alignment procedure. If after $N_{TA}$ repetitions, the error situation persists, the Iu UP protocol layers take appropriate local actions. + +Upon reception of a TIME ALIGNMENT NEGATIVE ACKNOWLEDGEMENT control frame, the Iu UP protocol layer in the SRNC stops the supervision timer $T_{TA}$ . + +![Sequence diagram for Unsuccessful Time Alignment between RNC and CN.](dd380ccd5aca1151074fede04826f1a4_img.jpg) + +``` + +sequenceDiagram + participant RNC + participant CN + RNC->>CN: TIME ALIGNMENT + CN-->>RNC: TIME ALIGNMENT NACK + Note left of RNC: * after N_TA repetitions + +``` + +A sequence diagram showing unsuccessful time alignment. The RNC sends a TIME ALIGNMENT frame. The CN responds with a TIME ALIGNMENT NACK. A red bar on the RNC lifeline indicates a failure state. Label 1) refers to the NACK reception, and label 2) refers to the expiration of timer $T_{TA}$ after $N_{TA}$ repetitions. + +Sequence diagram for Unsuccessful Time Alignment between RNC and CN. + +**Figure 16a: Unsuccessful Time Alignment: 1) $N_{TA}$ negative acknowledgements or 2) $N_{TA}$ expiries of timer $T_{TA}$** + +![Sequence diagram for Time Alignment received by the RNC](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +``` + + sequenceDiagram + participant RNC + participant CN + CN->>RNC: TIME ALIGNMENT + RNC->>CN: TIME ALIGNMENT NACK + +``` + +Sequence diagram for Time Alignment received by the RNC + +**Figure 16b: Time Alignment received by the RNC** + +### 6.5.5 Handling of Error Event procedure + +#### 6.5.5.1 Successful operation + +The purpose of the Handling of Error Event procedure is to handle the error reporting. Over the Iu UP protocol the error reports are made with ERROR EVENT control frames. The Handling of Error Event procedure in the Iu UP can be triggered by: + +- An error detected by the Iu UP functions (by receiving an erroneous frame or by receiving a frame with unknown or unexpected data). In this case an Iu UP- Status Indication may be used to inform the upper layers; +- A request by the upper layers. + +When an Error event is reported by an ERROR EVENT control frame the following information shall be included: + +- A cause value; +- Error distance (=0 if Iu UP function detected, =1 if requested by upper layers). + +Upon reception of an ERROR EVENT control frame the Iu UP functions should take appropriate local actions based on the cause value. This may include reporting the error to the upper layers with an Iu UP status indication. + +![Sequence diagram for Successful Error event](e05c1a13b44ab41505609d82b00cf4df_img.jpg) + +``` + + sequenceDiagram + participant RNC/CN + participant CN/RNC + RNC/CN->>CN/RNC: ERROR EVENT (Cause value, Error distance) + +``` + +Sequence diagram for Successful Error event + +**Figure 15b: Successful Error event** + +#### 6.5.5.2 Unsuccessful operation + +If the ERROR EVENT control frame is incorrectly formatted and cannot be correctly treated by the receiving Iu UP protocol layer appropriate local actions are taken (e.g. upper layers are informed). An error in an ERROR EVENT control frame should not generate the sending of a new ERROR EVENT control frame. + +![Figure 16c: Unsuccessful Transfer of ERROR EVENT control frame. The diagram shows two vertical lifelines for RNC/CN and CN/RNC. Two horizontal arrows point from left to right. The first arrow is labeled 'ERROR EVENT (Cause, Error distance)' and ends with a yellow 'X' and the number '1)', indicating frame loss. The second arrow is labeled 'ERROR EVENT (Cause, Error distance)' and ends with a red jagged flash symbol and the number '2)', indicating a corrupted frame.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +Figure 16c: Unsuccessful Transfer of ERROR EVENT control frame. The diagram shows two vertical lifelines for RNC/CN and CN/RNC. Two horizontal arrows point from left to right. The first arrow is labeled 'ERROR EVENT (Cause, Error distance)' and ends with a yellow 'X' and the number '1)', indicating frame loss. The second arrow is labeled 'ERROR EVENT (Cause, Error distance)' and ends with a red jagged flash symbol and the number '2)', indicating a corrupted frame. + +**Figure 16c: Unsuccessful Transfer of ERROR EVENT control frame: 1) Frame loss 2) Corrupted Frame** + +### 6.5.6 Frame Quality Classification procedure + +The Frame Quality Classification procedure uses the services of the Transfer of User Data procedure to exchange across the Iu UP interface the Frame Quality Classification information. + +![Figure 17: Successful Transfers of User Data with FQC information. The diagram shows two vertical lifelines for RNC/CN and CN/RNC. A top horizontal arrow points from RNC/CN to CN/RNC labeled 'TRANSFER OF USER DATA (FQC, RFCI, payload)'. A bottom horizontal arrow points from CN/RNC to RNC/CN labeled 'TRANSFER OF USER DATA (FQC, RFCI, payload)'.](e29665b8abcea967ef289c6aff07ae4c_img.jpg) + +Figure 17: Successful Transfers of User Data with FQC information. The diagram shows two vertical lifelines for RNC/CN and CN/RNC. A top horizontal arrow points from RNC/CN to CN/RNC labeled 'TRANSFER OF USER DATA (FQC, RFCI, payload)'. A bottom horizontal arrow points from CN/RNC to RNC/CN labeled 'TRANSFER OF USER DATA (FQC, RFCI, payload)'. + +**Figure 17: Successful Transfers of User Data with FQC information** + +## 6.6 Elements for Iu UP communication in Support mode + +### 6.6.1 General + +In the present document the structure of frames will be specified by using figures similar to figure 18. + +| Bits | | | | | | | | Number of Octets | | | +|------------------|---|---|---|---------|---|---------|---|------------------|---------|--------------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | +| Field 1 | | | | Field 2 | | | | 1 | Octet 1 | Header part | +| Field 3 | | | | | | Field 4 | | 2 | Octet 2 | | +| Field 4 continue | | | | Spare | | | | | Octet 3 | Payload part | +| Field 6 | | | | | | | | 2 | Octet 4 | | +| Field 6 continue | | | | Padding | | | | | Octet 5 | | +| Spare extension | | | | | | | | 0-m | | | + +**Figure 18: Example frame format** + +Unless otherwise indicated, fields which consist of multiple bits within an octet will have the more significant bit located at the higher bit position (indicated above frame in figure 18). In addition, if a field spans several octets, more significant bits will be located in lower numbered octets (right of frame in figure 18). + +On the Iu interface, the frame will be transmitted starting from the lowest numbered octet. Within each octet, the bits are sent according decreasing bit position (bit position 7 first). + +Spare bits should be set to "0" by the sender and should not be checked by the receiver. + +The header part of the frame is always an integer number of octets. The payload part is octet rounded (by adding 'Padding' when needed). + +The receiver should be able to remove an additional spare extension field that may be present at the end of a frame. See description of Spare extension field. + +### 6.6.2 Frame Format for predefined size SDUs + +#### 6.6.2.1 PDU Type 0 + +PDU Type 0 is defined to transfer user data over the Iu UP in support mode for pre-defined SDU sizes. Error detection scheme is provided over the Iu UP for the payload part. + +The following shows the Iu frame structure for PDU TYPE 0 data frame of the Iu UP protocol at the SAP towards the transport layers (TNL-SAP). + +![](49a49278cad196bdfe0db6b4dd1be7fd_img.jpg) + +| Bits | | | | | | | | Number of Octets | | +|-----------------|---|------|---|--------------|---|-------------|---|------------------|----------------------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | +| PDU Type (=0) | | | | Frame Number | | | | 1 | Frame Control Part | +| FQC | | RFCI | | | | | | 1 | | +| Header CRC | | | | | | Payload CRC | | 2 | Frame Check Sum Part | +| Payload CRC | | | | | | | | | | +| Payload Fields | | | | | | | | 0–n | Frame Payload part | +| Payload Fields | | | | Padding | | | | | | +| Spare extension | | | | | | | | | | + +**Figure 19: Iu UP PDU Type 0 Format** + +The Iu UP PDU TYPE 0 data frame is made of three parts: + +- 1) Iu UP Frame Control part (fixed size); +- 2) Iu UP Frame Check Sum part (fixed size); +- 3) Iu UP Frame Payload part (pre-defined SDU sizes rounded up to octets [Note: this does not consider the usage of spare extension field]). + +The Iu UP Frame Control Part and the Iu UP Frame Check Sum Part constitute the Iu UP PDU Type 0 Frame Header. + +#### 6.6.2.2 PDU Type 1 + +PDU Type 1 is defined to transfer user data over the Iu UP in support mode for pre-defined SDU sizes when no payload error detection scheme is necessary over Iu UP (i.e. no payload CRC). + +The following shows the Iu frame structure for PDU TYPE 1 data frame of the Iu UP protocol at the SAP towards the transport layers (TNL-SAP). + +![](f0a97d0d3818a253c1d2a009966081b1_img.jpg) + +| Bits | | | | | | | | Number of Octets | | +|-----------------|---|------|---|--------------|---|-------|---|------------------|----------------------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | +| PDU Type (=1) | | | | Frame Number | | | | 1 | Frame Control Part | +| FQC | | RFCI | | | | | | 1 | | +| Header CRC | | | | | | Spare | | 1 | Frame Check Sum Part | +| Payload Fields | | | | | | | | 0-n | Frame Payload part | +| Payload Fields | | | | Padding | | | | | | +| Spare extension | | | | | | | | 0-4 | | + +**Figure 20: Iu UP PDU Type 1 Format** + +The Iu UP PDU TYPE 1 data frame is made of three parts: + +- 1) Iu UP Frame Control part (fixed size); +- 2) Iu UP Frame Check Sum part (fixed size); +- 3) Iu UP Frame Payload part (pre-defined SDU sizes, rounded up to octets [Note: this does not consider the usage of spare extension field]). + +The Iu UP Frame Control Part and the Iu UP Frame Check Sum Part constitute the Iu UP PDU Type 1 Frame Header. + +#### 6.6.2.3 PDU Type 14 + +##### 6.6.2.3.1 General + +PDU Type 14 is defined to perform control procedures over the Iu UP in support mode for pre-defined SDU sizes. The control procedure is identified by the procedure indicator. The Frame Payload contains the data information related to the control procedure. + +Figure 21 shows the Iu frame structure for PDU Type 14 of the Iu UP protocol at the SAP towards the transport layers (TNL-SAP). + +| Bits | | | | | | | | Number of Octets | | | | | | | | | +|-----------------------------|---|---|-------------------------------|-------------|--------------------------|---|---|------------------|---------------------|--|--|--|--|--|--|--| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | | | | | +| PDU Type (=14) | | | Ack/Nack (=0, i.e. procedure) | | PDU Type 14 Frame Number | | | 1 | Frame Control Part | | | | | | | | +| Iu UP Mode version | | | Procedure Indicator | | | | | 1 | | | | | | | | | +| Header CRC | | | | Payload CRC | | | | 1 | Frame Checksum Part | | | | | | | | +| Payload CRC | | | | | | | | 1 | | | | | | | | | +| Reserved for procedure data | | | | | | | | 0-n | Frame payload part | | | | | | | | +| Spare extension | | | | | | | | 0-32 | | | | | | | | | + +**Figure 21: Iu UP PDU Type 14 Format for procedure sending** + +The Iu UP PDU Type 14 is made of three parts: + +- 1) Iu UP Frame Control part (fixed size); +- 2) Iu UP Frame Check Sum part (fixed size); +- 3) Iu UP Frame Payload part (variable length, rounded up to octet). + +The Iu UP Frame Control Part and the Iu UP Frame Check Sum Part constitute the Iu UP PDU Type 14 Frame Header. + +##### 6.6.2.3.2 Positive Acknowledgement + +When the PDU Type 14 is used to positively acknowledge a control procedure, the PDU Type 14 frame takes the following structure at the TNL-SAP. + +| Bits | | | | | | | | Number of Octets | | | | | | | | | +|--------------------|---|---|---------------------------------------------------------------------------------|-------|--------------------------|---|---|------------------|---------------------|--|--|--|--|--|--|--| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | | | | | +| PDU Type (=14) | | | Ack/Nack (=1, i.e. Ack) | | PDU Type 14 Frame Number | | | 1 | Frame Control Part | | | | | | | | +| Iu UP Mode version | | | Procedure Indicator
(indicating the procedure being positively acknowledged) | | | | | 1 | | | | | | | | | +| Header CRC | | | | Spare | | | | 1 | Frame Checksum Part | | | | | | | | +| Spare | | | | | | | | 1 | | | | | | | | | +| Spare extension | | | | | | | | 0-32 | Frame Payload part | | | | | | | | +| | | | | | | | | | | | | | | | | | + +**Figure 22: Iu UP PDU Type 14 Format for positive acknowledgement** + +The Iu UP Frame Control Part and the Iu UP Frame Check Sum Part constitute the Iu UP PDU Type 14 Frame Header for positive acknowledgement. + +##### 6.6.2.3.3 Negative Acknowledgement + +When the PDU Type 14 is used to negatively acknowledge a control procedure, the PDU Type 14 frame takes the following structure at the TNL-SAP. + +| Bits | | | | | | | | Number of Octets | | +|--------------------|---|---|---|---------------------------------------------------------------------------------|---|--------------------------|---|------------------|---------------------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | +| PDU Type (=14) | | | | Ack/Nack (=2, i.e. Nack) | | PDU Type 14 Frame Number | | 1 | Frame Control Part | +| Iu UP Mode version | | | | Procedure Indicator
(indicating the procedure being negatively acknowledged) | | | | 1 | | +| Header CRC | | | | | | Spare | | 1 | Frame Checksum Part | +| Spare | | | | | | | | 1 | | +| Error Cause value | | | | | | Spare | | 1 | Frame payload part | +| Spare extension | | | | | | | | 0-32 | | + +**Figure 23: Iu UP PDU Type 14 Format for negative acknowledgement** + +The Iu UP Frame Control Part and the Iu UP Frame Check Sum Part constitute the Iu UP PDU Type 14 Frame Header for negative acknowledgement. + +##### 6.6.2.3.4 Procedures Coding + +###### 6.6.2.3.4.1 Initialisation + +Figure 24 specifies how the INITIALISATION control frame is coded. + +| Bits | | | | | | | | Number of Octets | | | | | | | | | | | +|----------------------------------------|----|----------------------|----|-----------------------------------------|---|-----------------------------|-----------|---------------------------------------------------------------------------------------------------------|---------------------|--|--|--|--|--|--|--|--|--| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | | | | | | | +| PDU Type (=14) | | | | Ack/Nack (=0.
l.e. Procedure) | | PDU Type 14
Frame Number | | 1 | Frame Control Part | | | | | | | | | | +| lu UP Mode version | | | | Procedure Indicator (=0) | | | | 1 | | | | | | | | | | | +| Header CRC | | | | | | Payload CRC | | 2 | Frame Checksum part | | | | | | | | | | +| Payload CRC | | | | | | | | | | | | | | | | | | | +| Spare | | | TI | Number of subflows per
RFCI (N) | | | Chain Ind | 1 | Frame payload part | | | | | | | | | | +| LRI | LI | 1 st RFCI | | | | | | 1 | | | | | | | | | | | +| Length of subflow 1 | | | | | | | | 1 or 2
(dep. LI) | | | | | | | | | | | +| Length of subflow 2 to N | | | | | | | | (N-1)x(1
or 2) | | | | | | | | | | | +| LRI | LI | 2 nd RFCI | | | | | | 1 | | | | | | | | | | | +| Length of subflow 1 | | | | | | | | 1 or 2
(dep. LI) | | | | | | | | | | | +| Length of subflow 2 to N | | | | | | | | (N-1)x(1
or 2) | | | | | | | | | | | +| ... | | | | | | | | | | | | | | | | | | | +| IPTI of 1 st RFCI | | | | ... | | | | 0 or M/2
(M:
Number
of RFCIs
in frame).
Ended by
4
padding
bits if M
is odd. | | | | | | | | | | | +| ... | | | | IPTI of M th RFCI or Padding | | | | | | | | | | | | | | | +| lu UP Mode Versions supported (bitmap) | | | | | | | | 2 | | | | | | | | | | | +| Data PDU type | | | | Spare | | | | 1 | | | | | | | | | | | +| Spare extension | | | | | | | | 0-32 | | | | | | | | | | | + +Figure 24: lu UP PDU Type 14 used for Initialisation + +6.6.2.3.4.2 Rate Control + +6.6.2.3.4.2.1 Rate Control procedure + +Figure 25 specifies how the RATE CONTROL control frame is coded. + +| Bits | | | | | | | | Number of Octets | | | | | +|--------------------|-------------|-------------------------------|-------------------------------|---------|--------------------------|---|---|------------------|---------------------|--|--|--| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | +| PDU Type (=14) | | | Ack/Nack (=0, i.e. Procedure) | | PDU Type 14 Frame Number | | | 1 | Frame Control Part | | | | +| Iu UP Mode version | | | Procedure Indicator (=1) | | | | | 1 | | | | | +| Header CRC | | | | | Payload CRC | | | 1 | Frame Checksum Part | | | | +| Payload CRC | | | | | | | | 1 | | | | | +| Spare | | Number of RFCI Indicators (P) | | | | | | 1 | Frame payload part | | | | +| RFCI 0 Ind. | RFCI 1 Ind. | ... | RFCI P-1 Ind. | Padding | | | | 0-n | | | | | +| Spare extension | | | | | | | | 0-32 | | | | | + +**Figure 25: Iu UP PDU Type 14 Format used for Rate Control** + +###### 6.6.2.3.4.2.2 + +###### Rate Control positive acknowledgement + +Figure 25a specifies how the RATE CONTROL POSITIVE ACKNOWLEDGEMENT control frame is coded. + +| Bits | | | | | | | | Number of Octets | | | | | +|--------------------|-------------|-------------------------------|---------------------------------------------------------------------------------|---------|--------------------------|---|---|------------------|---------------------|--|--|--| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | +| PDU Type (=14) | | | Ack/Nack (=1, i.e. Ack) | | PDU Type 14 Frame Number | | | 1 | Frame Control Part | | | | +| Iu UP Mode version | | | Procedure Indicator
(indicating the procedure being positively acknowledged) | | | | | 1 | | | | | +| Header CRC | | | | | Spare | | | 1 | Frame Checksum Part | | | | +| Spare | | | | | | | | 1 | | | | | +| Spare | | Number of RFCI Indicators (P) | | | | | | 1 | Frame Payload part | | | | +| RFCI 0 Ind. | RFCI 1 Ind. | ... | RFCI P-1 Ind. | Padding | | | | 0-n | | | | | +| Spare extension | | | | | | | | 0 - (31-n) | | | | | + +Figure 25a: Iu UP PDU Type 14 Format for positive acknowledgement + +###### 6.6.2.3.4.3 + +###### Time Alignment + +Figure 26 specifies how the TIME ALIGNMENT control frame is coded. + +| Bits | | | | | | | | Number of Octets | | | | | +|--------------------|---|---|--------------------------|---|--------------------------|---|---|------------------|---------------------|--|--|--| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | +| PDU Type (=14) | | | Ack/Nack(=0) | | PDU Type 14 Frame Number | | | 1 | Frame Control Part | | | | +| Iu UP Mode version | | | Procedure Indicator (=2) | | | | | 1 | | | | | +| Header CRC | | | | | Payload CRC | | | 1 | Frame Checksum Part | | | | +| Payload CRC | | | | | | | | 1 | | | | | +| Time alignment | | | | | | | | 1 | Frame payload part | | | | +| Spare extension | | | | | | | | 0-32 | | | | | + +Figure 26: Iu UP PDU Type 14 Format used for Time Alignment + +###### 6.6.2.3.4.4 Error Event + +Figure 27 specifies how the ERROR EVENT control frame is coded. + +| Bits | | | | | | | | Number of Octets | | | | +|--------------------|---|-------------------|---|--------------------------|---|-----------------------------|---|------------------|---------------------|--|--| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | +| PDU Type (=14) | | | | Ack/Nack(=0) | | PDU Type 14
Frame Number | | 1 | Frame Control Part | | | +| Iu UP Mode version | | | | Procedure Indicator (=3) | | | | 1 | | | | +| Header CRC | | | | | | Payload CRC | | 1 | Frame Checksum Part | | | +| Payload CRC | | | | | | | | 1 | | | | +| Error distance | | Error Cause value | | | | | | 1 | Frame payload part | | | +| Spare extension | | | | | | | | 0-32 | | | | + +Figure 27: Iu UP PDU Type 14 Format used for Error Event + +### 6.6.3 Coding of information elements in frames + +#### 6.6.3.1 PDU Type + +**Description:** The PDU type indicates the structure of the Iu UP frame. The field takes the value of the PDU Type it identifies: i.e. "0" for PDU Type 0. The PDU type is in bit 4 to bit 7 in the first octet of the frame. PDU type is used in all frames in support mode for predefined SDU sizes. + +**Value range:** {0-1 and 14 in use, 2-13: reserved for future PDU types, 15=reserved for future PDU type extensions} + +**Field length:** 4 bits + +#### 6.6.3.2 Ack/Nack + +**Description:** The Ack/Nack field tells if the frame is: + +- A control procedure frame; +- A positive acknowledgement (ACK) of a control procedure frame; +- A negative acknowledgement (NACK) of a control procedure frame. + +**Value range:** {0=control procedure frame, 1=ACK, 2=NACK, 3=reserved} + +**Field length:** 2 bits + +#### 6.6.3.3 Frame Number + +**Description:** The Iu UP frame numbering is handled by a Frame Number. The frame numbering can be based on either time or sent Iu UP PDU. In case the frame numbering is based on time the purpose of the frame number is to be of help in handling the Time Alignment functionality. When the frame number is based on time, the Frame number set in the PDU header is incremented by one (modulo 16) at each new ITI. The Frame number set in the PDU header shall be based on the timing of the source. The source is where the original payload was created. Two packets that were consecutive at the source shall not have the same frame number assigned. In case the Frame number relates to sent Iu UP PDU the purpose of the Frame Number is to provide the receiving entity with a mechanism to keep track of lost Iu UP frames. When the frame number is based on sent Iu UP PDU, the Frame number is incremented by one (modulo 16) for each sent Iu UP PDU. For a given user data connection, there is no relations between the frame numbers of frames sent in the downlink direction and the frame numbers of frames sent in the uplink direction. + +In the case the Frame Number relates to sent Iu UP PDU, the following applies: + +- Frame loss is when an incoming PDU frame has a frame number that is equal to (previous PDU frame number + 2) modulo [max. PDU frame number + 1]. This indicates that one and only one PDU frame has been lost. +- Unexpected frame number is when an incoming PDU does not have the expected frame number and is not considered as a Frame Loss. + +**Value range:** {0-15}. + +**Field length:** 4 bits. + +#### 6.6.3.4 PDU Type 14 Frame Number + +**Description:** The Iu UP frame numbering is handled by a Frame Number. The purpose of the PDU Type 14 Frame Number is to provide the receiving entity with a mechanism to keep track of lost Iu UP frames. The PDU Type 14 Frame Number shall be managed as one single counter for all control procedure functions of a RAB. The sender shall increment this number by one (modulo 4) for each sent Iu UP Type 14 PDU starting with value 0 for the first PDU Type 14 INITIALISATION control frame sent out of the initialisation procedure. The counter shall be reset to 0 in case a new initialisation takes place. It is also used to relate the acknowledgment frame to the frame being acknowledged i.e. the same PDU Type 14 Frame Number is used in the positive or negative acknowledgement frame as the one used in the frame being acknowledged. + +The PDU Type 14 Frame Number shall be handled independently per direction, i.e. control frames other than acknowledgment frames shall be numbered independently per direction. + +The following applies for PDU Type 14 Frame Number: + +- Frame loss is when an incoming PDU frame has a frame number that is equal to (previous PDU frame number + 2) modulo [max. PDU frame number + 1]. This indicates that one and only one PDU frame has been lost. +- Unexpected frame number is when an incoming PDU does not have the expected frame number and is not considered as a Frame Loss. + +Upon detection of frame loss or unexpected PDU Type 14 Frame Number in a procedure other than initialisation, the receiving entity shall still consider the frame as valid and handle it normally e.g. treat it and send an acknowledgement frame when appropriate. + +**Value range:** {0-3}. + +**Field length:** 2 bits. + +#### 6.6.3.5 Frame Quality Classification (FQC) + +**Description:** Frame Quality Classification is used to classify the Iu UP frames depending on whether errors have occurred in the frame or not. Frame Quality Classification is dependent on the RAB attribute *Delivery of erroneous SDU* IE. + +**Value range:** {0=frame good, 1=frame bad, 2=frame bad due to radio, 3=spare}. + +**Field length:** 2 bits. + +#### 6.6.3.6 RAB sub-Flow Combination Indicator (RFCI) + +**Description:** The RFCI identifies the structure of the payload. This can be used to specify the sizes of the subflows. + +**Value range:** {0-62, 63=RFCI not applicable}. + +**Field length:** 6 bits. + +#### 6.6.3.7 Procedure Indicator + +**Description:** The Procedure Indicator identifies the control procedure in the current frame. + +**Value range:** {0=initialisation, 1=rate control, 2=time alignment, 3=error event, 4-15=reserved}. + +**Field length:** 4 bits. + +#### 6.6.3.8 Header CRC + +**Description:** This field contains the CRC of all fields in Frame Control Part. The CRC is a 6-bit checksum based on the generator polynom $G(D) = D^6+D^5+D^3+D^2+D^1+1$ , see subclause 6.7.7. With this CRC all error bursts shorter than 7 bits are detected, as well as all odd number of bits faulty (and two-bit faults) when the protected area is shorter than 24 bits, (max 3 octets). + +**Field length:** 6 bits. + +#### 6.6.3.9 Payload CRC + +**Description:** This field contains the CRC of all the fields (including Padding and possible Spare extension) of the Frame Payload Part. The CRC is a 10 bit checksum based on the generator polynom $G(D) = D^{10}+D^9+D^5+D^4+D^1+1$ , see subclause 6.7.7. With this CRC all error bursts shorter than 11 bits are detected, as well as all odd number of bits faulty (and two-bit faults) when the protected area is shorter than 500 bits (max 62 octets). + +**Field length:** 10 bits. + +#### 6.6.3.10 Chain Indicator + +**Description:** Chain indicator is used to indicate whether the control procedure frame is the last frame related to the control procedure. + +**Value range:** {0=this frame is the last frame for the procedure, 1=additional frames will be sent for the procedure}. + +**Field length:** 1 bit. + +#### 6.6.3.11 Number of Subflows per RFCI + +**Description:** Number of Subflows per RFCI field indicates the number of subflows the RAB is made of. It is used to decode the SDU size information data lengths. All RFCs consist of the same number of subflows within a specific RAB. + +**Value range:** {0=reserved, 1-7}. + +**Field length:** 3 bits. + +#### 6.6.3.12 Length Indicator (LI) + +**Description:** Length Indicator, indicates if 1 or 2 octets is used for the RAB subflow size information. + +**Value range:** {0=one octet used, 1=two octets used}. + +**Field length:** 1 bit. + +#### 6.6.3.13 Number of RFCI Indicators + +**Description:** Number of RFCI indicators indicates the number of RFCI indicators present in the control procedure frame. + +**Value range:** {0-63}. + +**Field length:** 6 bits. + +#### 6.6.3.14 RFCI n Indicator + +**Description:** RFCI n Indicator indicates if the RFCI with value n is allowed or barred (n is a value between 0-62). E.g. RFCI 4 Indicator set to "0" indicates that RFCI =4 is allowed, RFCI 5 Indicator set to "1" indicates that RFCI =5 is barred, etc... + +**Value range:** {0=RFCI allowed, 1=RFCI barred}. + +**Field length:** 1 bit. + +#### 6.6.3.15 Error distance + +**Description:** Indicates if the error occurred at the error reporting entity (=0) or in a more distant entity. The error distance is incremented by one (or kept at its maximum value) when an error report is forwarded. + +- 0: Reporting local error. +- 1: First forwarding of error event report. +- 2: Second forwarding of error event report. +- 3: Reserved for future use. + +**Value range:** {0: Reporting local error, 1: First forwarding of error event report. 2: Second forwarding of error event, 3: Reserved for future use}. + +**Field length:** 2 bit. + +#### 6.6.3.16 Error Cause value + +**Description:** Cause value is used to indicate what kind of error caused the error. Error cause value is used in NEGATIVE ACKNOWLEDGEMENT and ERROR EVENT control frames. + +- 0: CRC error of frame header. +- 1: CRC error of frame payload. +- 2: Unexpected frame number. +- 3: Frame loss. +- 4: PDU type unknown. +- 5: Unknown procedure. +- 6: Unknown reserved value. +- 7: Unknown field. +- 8: Frame too short. +- 9: Missing fields. +- 10–15: spare. +- 16: Unexpected PDU type. +- 17: spare. +- 18: Unexpected procedure. +- 19: Unexpected RFCI. +- 20: Unexpected value. +- 21–41: spare. +- 42: Initialisation failure. +- 43: Initialisation failure (network error, timer expiry). +- 44: Initialisation failure (Iu UP function error, repeated NACK). +- 45: Rate control failure. +- 46: Error event failure. +- 47: Time Alignment not supported. +- 48: Requested Time Alignment not possible. +- 49: Iu UP Mode version not supported. +- 50–63: spare. + +**Value range:** {0–15 Used for syntactical protocol errors, 16–41 Used for semantical protocol errors, 42–63 Used for other errors}. + +**Field length:** 6 bit. + +#### 6.6.3.17 Padding + +**Description:** This field is an additional field used to make the frame payload part an integer number of octets when needed. Padding is set to "0" by the sender and is not interpreted by the receiver. + +**Value range:** {0–127}. + +**Field length:** 0–7 bits. + +#### 6.6.3.18 Time alignment + +**Description:** Time alignment indicates the amount the sending time should be advanced or delayed. + +0: Reserved. + 1: Delay 1\*500µs. + ... + 80: Delay 80\*500µs. + 81–127 Reserved. + 128: Reserved. + 129: Advance 1\*500µs. + ... + 208: Advance 80\*500µs. + 209–255 Reserved. + +**Value range:** {0: Reserved, 1–80: used for delay, 81–128: Reserved, 129–208 used for advance, 209–255: Reserved}. + +**Field length:** 8 bit. + +#### 6.6.3.19 Spare + +**Description:** The spare field is set to "0" by the sender and should not be interpreted by the receiver. + +**Value range:** (0–2n-1). + +**Field Length:** n bits. + +#### 6.6.3.20 Spare extension + +**Description:** The spare extension field shall not be sent. The receiver should be capable of receiving a spare extension. The spare extension should not be interpreted by the receiver. This since in later versions of the present document additional new fields might be added in place of the spare extension. The spare extension can be an integer number of octets carrying new fields or additional information; the maximum length of the spare extension field (m) depends on the PDU type. + +**Value range:** 0–2m\*8-1. + +**Field Length:** 0–m octets. For PDU Types in the set {0,1}, m=4. For PDU Types in the set {14}, m=32. + +#### 6.6.3.21 LRI, Last RFCI Indicator + +**Description:** The Last RFCI Indicator is used to indicate which is the last RFCI in the current INITIALISATION control frame. This makes it possible for a receiver to detect a spare extension field. + +**Value range:** (0: Not last RFCI, 1: Last RFCI in current frame). + +**Field Length:** 1 bit. + +#### 6.6.3.22 Length of subflow + +**Description:** This field indicates the length of the corresponding subflow as number of bits per SDU. + +**Value range:** (0–255 if LI=0, 0–65535 if LI=1). + +**Field Length:** 8 or 16 bits (depending on LI). + +#### 6.6.3.23 TI + +**Description:** This field indicates if Timing Information is included in the INITIALISATION control frame. + +**Value range:** {0: IPTIs not present, 1: IPTIs present in frame}. + +**Field length:** 1 bit. + +#### 6.6.3.24 IPTI of nth RFCI + +**Description:** This field indicates the IPTI value in number of ITIs for the corresponding RFCI (in the same order as the RFCIs occur in the INITIALISATION control frame). + +**Value range:** {0–15}. + +**Field length:** 4 bits. + +#### 6.6.3.25 Iu UP Mode versions supported + +**Description:** This field indicates the Iu UP Mode Versions proposed by the sender for the related RAB for the initialisation procedure. Up to 16 Iu UP Mode versions can be simultaneously indicated. + +**Value range:** + +Each bit, in the two octet field, indicates a Iu UP Protocol version: (First octet, bit 7) indicates version 16, (Second octet, bit 0) indicates version 1. + +Bit = 0 means "Version not supported, not allowed or not proposed" + +Bit = 1 means "Version supported among the required versions and proposed" + +**Field length:** 2 octets + +#### 6.6.3.26 Iu UP Mode Version + +**Description:** This field indicates the Iu UP Mode version used for type 14 frames. Up to 16 Iu UP Mode Versions can be available. + +**Value range:** {1-16} The binary coded value is the version number minus 1 (e.g. version 1 is coded "0000", ..., version 16 is coded "1111"). + +**Field length:** 4 bits + +#### 6.6.3.27 Payload fields + +**Description:** This field contains the Subflow SDUs, starting with the Subflow 1 SDU. The MSB of the Subflow 1 SDU is placed in bit 7 of the first octet (see example in figure 27a). + +**Value range:** {any value}. + +**Field length:** Sum of the lengths of the included Subflow SDUs. + +| Bits | | | | | | | | Number
of Octets | +|---------------------|---|---|---|---------------|----------------------------------------------|---|---|---------------------| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | +| Subflow 1 SDU | | | | | | | | 1 | +| Subflow 1 SDU cont. | | | | Subflow 2 SDU | | | | 1 | +| Subflow 2 SDU cont. | | | | | Padding
(Not part of
'Payload fields') | | | 1 | + +Figure 27a: Example of 'Payload fields' with two Subflow SDUs + +#### 6.6.3.28 Data PDU type + +**Description:** This field indicates the PDU type that shall be used (in both directions) for transferring user data. + +**Value range:** {0: PDU type 0, 1: PDU type 1, 2–15: Reserved for future use}. + +**Field length:** 4 bits. + +### 6.6.4 Timers + +#### TINIT + +This Timer is used to supervise the reception of the initialisation acknowledgement frame from the peer Iu UP instance. This Timer is set by O&M. + +#### TTA + +This Timer is used to supervise the reception of the time alignment acknowledgement frame from the peer Iu UP instance. This Timer is set by O&M. + +#### TRC + +This Timer is used to supervise the reception of the rate control frame from the peer Iu UP instance. This Timer is set by O&M. + +### 6.6.5 Maximum values of repetition counters + +#### NINIT + +Maximum number of repetitions of an INITIALISATION control frame due to failure at the Initialisation procedure. + +#### NRC + +Maximum number of repetitions of a RATE CONTROL control frame due to failure at the Rate Control procedure. + +#### NTA + +Maximum number of repetitions of a TIME ALIGNMENT control frame due to failure at the Time Alignment procedure. + +## 6.7 Handling of unknown, unforeseen and erroneous protocol data + +### 6.7.1 General + +Error handling in Iu UP protocol is applicable only for Iu UP in Support mode. + +The Handling of Error Event procedure is the procedure handling error reporting. The Handling of Error Event procedure in the Iu UP can be triggered by: + +- An error detected by the Iu UP functions (by receiving an erroneous frame or by receiving a frame with unknown or unexpected data); +- A request by the upper layers; +- An ERROR EVENT control frame over the Iu UP protocol. + +The error can be reported either by: + +- An ERROR EVENT control frame over the Iu UP protocol; +- An Iu UP Status Indication to upper layers (e.g. to be used by O&M). + +When an Error event is reported, either by an Iu-UP-Status-Indication, or by an ERROR EVENT control frame the following information shall be included: + +- Type of the error (syntactical error, semantical error or other error); + +- Error distance, i.e. information where the error occurred. + +### 6.7.2 Error detected by Iu UP functions + +When an error is detected within the Iu UP functions (by receiving a frame containing erroneous, unknown or unexpected data) one of the following actions is taken depending on the type of the error: + +1. Error indicated to upper layers by sending a Iu-UP-Status-Indication primitive; +2. ERROR EVENT control frame sent; +3. ERROR EVENT control frame sent and error indicated to upper layers by sending a Iu-UP-Status-Indication primitive; +4. No action. + +### 6.7.3 Request by upper layers + +When the Iu UP receives an Iu-UP-Status-Request indicating Error event then an ERROR EVENT control frame should be sent over the Iu UP protocol indicating the appropriate error type. + +### 6.7.4 Error event frame over the Iu UP protocol + +When an ERROR EVENT control frame is received over the Iu UP protocol an Iu-UP-Status-Indication with 'Error event' information indicating the error type should be made to the upper layers. The Error event report contains a 'Cause value' that tells the type of the error. The Error event report also contains a field 'Error distance' that tells the distance to the entity reporting the error event. The 'Error distance' is "0" when the error is originally sent. When an Error event report is forwarded the 'Error distance' is incremented by one. + +### 6.7.5 Handling of error reports + +#### 6.7.5.1 General + +Figure 28 shows the external error case when the Handling of Error Event procedure is originally triggered by an Iu-UP-Status-Request. As an action on this the Handling of Error Event procedure sends an ERROR EVENT control frame over the Iu UP. On the other side the reception of ERROR EVENT control frame triggers the Handling of Error Event procedure, and an Iu-UP-Status-Indication is sent to upper layers. The handling is symmetrical over the Iu UP protocol. + +![Diagram illustrating the external error case. It shows two entities, 'Support Mode Functions', connected by a horizontal line representing the 'Transfer of Iu UP protocol frames'. Above the left entity, an arrow points up to 'Iu Interface' labeled 'Status-Indication Error event (Cause, Error distance = 2)'. Above the right entity, an arrow points down from 'Iu Interface' labeled 'Status-Request Error event (Cause)'. A red double-headed arrow between the two 'Support Mode Functions' boxes is labeled 'Transfer of Iu UP protocol frames'. A black arrow points from the right 'Support Mode Functions' box to the left 'Support Mode Functions' box, labeled 'ERROR EVENT control frame (Cause, Error distance = 1)'.](1dbb1d90b2022a3a765c85929a515cc6_img.jpg) + +Diagram illustrating the external error case. It shows two entities, 'Support Mode Functions', connected by a horizontal line representing the 'Transfer of Iu UP protocol frames'. Above the left entity, an arrow points up to 'Iu Interface' labeled 'Status-Indication Error event (Cause, Error distance = 2)'. Above the right entity, an arrow points down from 'Iu Interface' labeled 'Status-Request Error event (Cause)'. A red double-headed arrow between the two 'Support Mode Functions' boxes is labeled 'Transfer of Iu UP protocol frames'. A black arrow points from the right 'Support Mode Functions' box to the left 'Support Mode Functions' box, labeled 'ERROR EVENT control frame (Cause, Error distance = 1)'. + +**Figure 28: External error** + +Figure 29 shows the internal error case when the Handling of Error Event procedure is originally triggered by the Iu UP functions. As an action on this the Handling of Error Event procedure sends an ERROR EVENT control frame over the Iu UP. On the other side the reception of ERROR EVENT control frame triggers the Handling of Error Event + +procedure, and an Iu-UP-Status-Indication is sent to the upper layers. The handling is symmetrical over the Iu UP protocol. + +![Figure 29: Internal error diagram showing the Iu Interface and two Support Mode Functions blocks. The left block sends a Status-Indication Error event (Cause, Error distance=1) to upper layers. An ERROR EVENT control frame (Cause, Error distance=0) is sent from the right block to the left block. The left block then sends a Status-Indication Error event (Cause, Error distance=0) to upper layers. The right block indicates 'Error detected!'. A red double-headed arrow indicates 'Transfer of Iu UP protocol frames' between the blocks.](ddee3e67e0dfc22e25188fa635a19558_img.jpg) + +Figure 29: Internal error diagram showing the Iu Interface and two Support Mode Functions blocks. The left block sends a Status-Indication Error event (Cause, Error distance=1) to upper layers. An ERROR EVENT control frame (Cause, Error distance=0) is sent from the right block to the left block. The left block then sends a Status-Indication Error event (Cause, Error distance=0) to upper layers. The right block indicates 'Error detected!'. A red double-headed arrow indicates 'Transfer of Iu UP protocol frames' between the blocks. + +Figure 29: Internal error + +#### 6.7.5.2 Error distance + +In an ERROR EVENT control frame the error distance has the following meaning: + +- 0: Error report relates to an Iu UP function error at the other side. +- 1: Error report relates to an error at the other side reported by the upper layers. + +In an Iu UP-Status indication the error distance has the following meaning: + +- 0: Error report relates to a local Iu UP function error. +- 1: Error report relates to an Iu UP function error at the other side. +- 2: Error report relates to an error at the other side reported by the upper layers. + +### 6.7.6 List of errors in Iu UP + +Table 0: List of errors in Iu UP + +| Error Type | Error Cause | Recommended action by Handling of Error Event procedure | Possibly detected by function | Comment | +|-------------|----------------------------------------|--------------------------------------------------------------------|-------------------------------------|-------------------------------------------------------| +| Syntactical | CRC error of Frame payload (CRC check) | No action | NAS Data Streams specific functions | Handled by Frame Quality Classification, when applied | +| | CRC error of Frame Header (CRC check) | Iu-UP-Status-Indication(Error event) | Frame Handler functions | Frame discarded | +| | Unexpected Frame Number | Iu-UP-Status-Indication(Error event) | Frame Handler functions | See 6.6.3.3 | +| | Frame loss | Iu-UP-Status-Indication(Error event) and ERROR EVENT control frame | Frame Handler functions | See 6.6.3.3 | +| | PDU type Unknown | Iu-UP-Status-Indication(Error event) and ERROR EVENT control frame | Frame Handler functions | Used when PDU type is not 0, 1, or 14 | +| | Unknown procedure | Iu-UP-Status-Indication(Error event) and ERROR EVENT control frame | Frame Handler functions | Used when procedure value is neither 0, 1, 2, or 3 | + +| Error Type | Error Cause | Recommended action by Handling of Error Event procedure | Possibly detected by function | Comment | +|-------------------|--------------------------------------------------------------|--------------------------------------------------------------------|--------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Unknown reserved value | See 8.1.1 | | | +| | Unknown field | | | This error cause shall not be sent. | +| | Frame too short | Iu-UP-Status-Indication(Error event) and ERROR EVENT control frame | Frame Handler functions | Used when:
- the length of the entire received PDU is less than the expected (calculated) PDU header length, or
- the length of the payload (entire received PDU minus PDU header length) is less than the expected (calculated) payload length | +| | Missing fields | Iu-UP-Status-Indication(Error event) and ERROR EVENT control frame | Frame Handler functions | This error cause shall not be sent. | +| Semantical | Unexpected PDU type | Iu-UP-Status-Indication(Error event) and ERROR EVENT control frame | Frame Handler functions | | +| | Unexpected procedure | Iu-UP-Status-Indication(Error event) and ERROR EVENT control frame | Frame Handler functions | | +| | Unexpected RFCI | Iu-UP-Status-Indication(Error event) and ERROR EVENT control frame | NAS Data Streams specific functions | | +| | Unexpected value | Iu-UP-Status-Indication(Error event) and ERROR EVENT control frame | Procedure Control functions | | +| Other error | Initialisation failure (outside Iu UP) | ERROR EVENT control frame | Function outside Iu UP | | +| | Initialisation failure (network error, timer expiry) | Iu-UP-Status-Indication(Error event) | Procedure Control functions | | +| | Initialisation failure (Iu UP function error, repeated NACK) | Iu-UP-Status-Indication(Error event) | Procedure Control functions | | +| | Rate control failure | Iu-UP-Status-Indication(Error event) | Procedure Control functions | | +| | Error event failure | Iu-UP-Status-Indication(Error event) | Procedure Control functions | | +| | Time Alignment not supported | Iu-UP-Status-Indication(Error event) | Procedure Control functions | | +| | Requested Time Alignment not possible | Iu-UP-Status-Indication(Error event) | Function outside Iu UP | | +| | Iu UP version not supported | Iu-UP-Status-Indication(Error event) | Procedure Control functions | | + +### 6.7.7 Error detection + +#### 6.7.7.1 General + +Error detection is provided on frames through a Cyclic Redundancy Check. The CRC for the payload is 10 bits and for the header it is 6 bits. + +#### 6.7.7.2 CRC Calculation + +The parity bits are generated by one of the following cyclic generator polynomials: + +$$g_{CRC6}(D) = D^6 + D^5 + D^3 + D^2 + D^1 + 1;$$ + +$$g_{CRC10}(D) = D^{10} + D^9 + D^5 + D^4 + D^1 + 1.$$ + +Denote the bits to be protected of a frame by $a_1, a_2, a_3, \dots, a_{A_i}$ ( $a_1$ being the bit with the highest bit position in the first octet), and the parity bits by $p_1, p_2, p_3, \dots, p_{L_i}$ . $A_i$ is the length of the protected data and $L_i$ is 6 or 10 depending on the CRC length. + +The encoding is performed in a systematic form, which means that in GF(2), the polynomial + +$$a_1 D^{A_i+5} + a_2 D^{A_i+4} + \dots + a_{A_i} D^6 + p_1 D^5 + p_2 D^4 + \dots + p_5 D^1 + p_6$$ + +yields a remainder equal to 0 when divided by $g_{CRC6}(D)$ and the polynomial + +$$a_1 D^{A_i+9} + a_2 D^{A_i+8} + \dots + a_{A_i} D^{10} + p_1 D^9 + p_2 D^8 + \dots + p_9 D^1 + p_{10}$$ + +yields a remainder equal to 0 when divided by $g_{CRC10}(D)$ . If $A_i = 0$ , $p_1 = p_2 = p_3 = \dots = p_{L_i} = 0$ . + +#### 6.7.7.3 Relation between input and output of the Cyclic Redundancy Check + +The protected bits are left unchanged in the frame. The parity bits for the Header CRC are put in the Header CRC field with $p_1$ being the highest bit position of the first octet of the Header CRC field. The parity bits for the Payload CRC are put in the Payload CRC field with $p_1$ being the highest bit position of the first octet of the Payload CRC field. + +# 7 Communication Primitives for the Iu UP protocol layer + +## 7.1 Modelling Principle + +The principle illustrated by figure 30 is used for modelling the primitives towards the protocol layer. + +![Diagram illustrating the modelling principle for communication primitives. A rectangular box labeled 'Protocol Layer' has two input/output points on its top edge. A downward-pointing arrow labeled 'REQUEST' enters the box from the top left. An upward-pointing arrow labeled 'INDICATION' exits the box from the top right.](1662582b76eec39c269b6ae14fe5d5f1_img.jpg) + +Diagram illustrating the modelling principle for communication primitives. A rectangular box labeled 'Protocol Layer' has two input/output points on its top edge. A downward-pointing arrow labeled 'REQUEST' enters the box from the top left. An upward-pointing arrow labeled 'INDICATION' exits the box from the top right. + +Figure 30: Modelling principle + +## 7.2 Primitives towards the upper layers at the RNL SAP + +### 7.2.1 General + +The Iu UP protocol layer interacts with upper layers as illustrated in the figure above. The interactions with the upper layers are shown in terms of primitives where the primitives represent the logical exchange of information and control between the upper layer and the Iu UP protocol layer. They do not specify or constrain implementations. + +The following primitives are defined: + +- Iu-UP-DATA; +- Iu-UP-STATUS; +- Iu-UP-UNIT-DATA. + +**Table 1: Iu UP protocol layer service primitives towards the upper layer at the RNL SAP** + +| Primitive | Type | Parameters | Comments | +|-----------------|------------|-------------------------|-----------------------------------------------------------------------------------------| +| Iu-UP-DATA | Request | Iu-UP-payload | Subflow 1 SDU, ..., Subflow n SDU | +| | | Iu-UP-control | RFCI | +| | | | FQC | +| | | | Frame Number | +| | Indication | Iu-UP-payload | Subflow 1 SDU, ..., Subflow n SDU | +| | | Iu-UP-control | RFCI | +| | | | FQC | +| | | | Frame Number | +| Iu-UP-Status | Indication | Iu-UP-Procedure-Control | Error Cause, Error Distance | +| | | | Complete protocol data for Initialisation, Rate Control, Time Alignment and Error Event | +| | | | | +| | | | | +| | Request | Iu-UP-Procedure-Control | Error Cause | +| | | | Complete protocol data for Initialisation, Rate Control, Time Alignment and Error Event | +| | | | | +| | | | | +| Iu-UP-UNIT-DATA | Request | Iu-UP-payload | | +| | Indication | Iu-UP-payload | | + +Primitive usage is a function of the mode of operation of the Iu UP protocol. Table 2 provides the association between Iu UP primitives towards the upper layers and the Iu UP modes of operation. + +**Table 2: Iu UP protocol layer service primitives related to the Iu UP mode of operation and function within the mode of operation** + +| Primitive | Type | Mode of Operation | +|-----------------|------------|-------------------| +| Iu-UP-DATA | Request | SMpSDU | +| | Indication | SMpSDU | +| Iu-UP-Status | Request | SMpSDU | +| | Indication | SMpSDU | +| Iu-UP-UNIT-DATA | Request | TrM | +| | Indication | TrM | + +### 7.2.2 Iu-UP-DATA-REQUEST + +This primitive is used as a request from the upper layer Iu NAS Data Stream entity to send the RAB subflow SDU(s) on the established transport connection. This primitive includes the RFCI, the Frame Number and FQC information of the payload. + +The Iu UP protocol layer forms the Iu UP data frame, the Iu Data Stream DU being the payload of the Iu UP frame, and transfers the frame by means of the lower layer services. + +### 7.2.3 Iu-UP-DATA-INDICATION + +This primitive is used as an indication to the upper layer entity to pass the Iu NAS Data Stream User Plane information of a received Iu UP frame. + +This primitive includes the RFCI, the Frame Number and FQC information of the payload. + +This primitive may also include information aiming at informing the upper layers of a faulty situation that relates to the payload included in the primitive. + +### 7.2.4 Iu-UP-STATUS-REQUEST + +This primitive is used to pass control procedure information from the upper layer. + +This primitive shall contain the complete protocol data for the respective procedure. + +### 7.2.5 Iu-UP-STATUS-INDICATION + +This primitive is used to pass control procedure information to the upper layer. + +This primitive shall contain the complete protocol data for the respective procedure. + +### 7.2.6 Iu-UP-UNIT-DATA-REQUEST + +This primitive is used as a request from the upper layer to send an Iu UP payload on the established transport connection. + +The Iu UP protocol layer transfers the Iu Data Stream DU by means of the lower layer services without adding any protocol header overhead. + +### 7.2.7 Iu-UP-UNIT-DATA-INDICATION + +This primitive is used as an indication to the upper layer entity to pass the Iu UP payload. + +## 7.3 Primitives towards the transport layers at TNL SAP + +### 7.3.1 General + +Access to the Transport network Layer is performed through a generic SAP: TNL-SAP. + +When the Transport Network upper layer consists of AAL2, the TNL SAP maps onto the AAL-SAP through which communication is performed using specific AAL primitives. + +When the Transport Network upper layer consists of GTP-U, the TNL SAP maps onto the GTP-U SAP through which communication is performed using generic primitives. + +The choice of communication, specific or generic, through the TNL SAP is fixed by the Radio Network Layer control plane logic. This choice is based on the requirements placed by e.g. the RAB characteristics, the CN domain requesting the RAB establishment or other operator's choice. + +### 7.3.2 ATM/AAL2 based Transport layer + +#### 7.3.2.1 General + +When the Iu UP protocol layer uses the services of an ATM/AAL2 transport (ITU-T Recommendation I.363.2 [7]), it uses an established AAL2 connection for transferring frames between the peer TNL-SAPs at both ends of the Iu User plane access points. The Transport Network Control Plane over Iu handles the signalling to establish and release the AAL2 call connections. + +#### 7.3.2.2 AAL2 Service Primitives used by the Iu UP protocol + +AAL2 services and primitives used at the Service Access Point from the AAL2 layer are shown in table 3. + +**Table 3: AAL2 primitives and parameters** + +| Primitive | Type | Parameters | Comments | +|----------------|---------------------------------------------------------------------------------------------------------|-------------------------|-----------------| +| SSSAR-UNITDATA | Request | SSSAR-INFO
SSSAR-UUI | Not used (note) | +| SSSAR-UNITDATA | Indication | SSSAR-INFO
SSSAR-UUI | Not used (note) | +| NOTE: | The setting of this field is set to not used i.e. decimal value 26 according to ITU-T Rec. I.366.1 [8]. | | | + +The primitives of table 3 are the standard primitives of ITU-T Rec. I.366.1 [8]. These primitives are intended to be used in the Iu UP. + +### 7.3.3 GTP-U based Transport Layer + +#### 7.3.3.1 General + +When the Iu UP protocol layer uses the services of a GTP-U transport, it uses an established GTP-U tunnel for transferring frames between the GTP-U tunnel endpoints at both ends of the Iu User plane access points. The RANAP Control Plane signalling over Iu handles the signalling to establish and release the GTP-U tunnels. + +#### 7.3.3.2 Generic Service Primitives used by the Iu UP protocol + +Generic primitives are used at the GTP-U SAP. They are shown in table 4. + +**Table 4: Generic primitives and parameters to and from GTP-U layer** + +| Primitive | Type | Parameters | Comments | +|----------------|------------|---------------|----------| +| Iu-UP-UNITDATA | Request | Iu-UP-payload | | +| Iu-UP-UNITDATA | Indication | Iu-UP-payload | | + +### 7.3.4 RTP based Transport Layer + +#### 7.3.4.1 General + +When the Iu UP protocol layer uses the services of a RTP/UDP/IP transport, it uses an established RTP session for transferring frames between the two RTP endpoints at both ends of the Iu User plane access points as defined in IETF + +RFC 1889 [14]. A single Iu-UP PDU shall be transported as RTP payload. A dynamic Payload Type (IETF RFC 1890 [15]) shall be used (see TS 25.414 [4]). + +#### 7.3.4.2 Generic Service Primitives used by the Iu UP protocol + +Generic primitives are used at the RTP SAP. They are shown in table 5. + +**Table 5: Generic primitives and parameters to and from RTP layer** + +| Primitive | Type | Parameters | Comments | +|----------------|------------|---------------|----------| +| Iu-UP-UNITDATA | Request | Iu-UP-payload | | +| Iu-UP-UNITDATA | Indication | Iu-UP-payload | | + +# --- 8 Evolution of Iu UP Protocol + +## 8.1 Principles for Protocol Evolution + +### 8.1.1 Unknown field value + +The Iu UP protocol may be evolved by taking into use field values that have been specified to be reserved for future use or have been specified as spare values. When a UP protocol entity receives an unknown field value, it can react differently depending whether the unknown value is reserved for future use or if it is a spare value. The following principles are recommended for receiver reactions: + +- If a spare value is used by the sender, but not understood by the receiver, there should be a default action for the receiver. This default action should be defined on a field basis; +- If a value that is reserved for future use is used by the sender, but not understood by the receiver, the value should be rejected by the receiver. This should be done by sending a Negative Acknowledgement to the peer entity, if possible. Otherwise an Error Event should be generated in order to inform the upper layers and the peer entity; +- A received ERROR EVENT control frame shall not trigger another ERROR EVENT control frame back to the sender, even though e.g. the Cause value in the received ERROR EVENT control frame would not be understood. + +In the following the recommended actions of the receiver are handled field by field when an unknown field value is received. + +#### PDU Type + +Recommended action if reserved values used: Generate Error Event, i.e. the upper layers and the peer entity are informed about the error event with Cause: "PDU type unknown". + +#### FOC + +Recommended action if spare values used: Ignore the field and pass it onwards. + +#### ACK/NACK + +Proposed action if reserved values used: Generate an Error Event, i.e. the upper layers and the peer entity are informed about the error event with Cause: "Unknown reserved value". + +#### Procedure Indicator + +Recommended action if reserved values used: Generate an Error Event, i.e. the upper layers and the peer entity are informed about the error event with Cause: "Unknown procedure". + +#### **Error Cause value** + +Value "49" is reserved for "Iu UP Mode version not supported" whatever the Iu UP Mode version. + +Recommended action if reserved values used: Generate Error Event, i.e. the upper layers and the peer entity are informed about the error event with Cause: "Unknown reserved value". + +Recommended action if spare values used: Ignore the field and pass it onwards. + +### **8.1.2 Adding a new field to an existing frame** + +If there is a need to add a new field to an existing procedure, the following principles shall be applied: + +- The PDU type defines the header mask. Therefore, a new field shall not be added to the header part of an existing frame and possible spare bits in the header shall not be taken into use since these would be violations of the header mask; +- The Procedure Indicator shall define the fields that should be in a control frame; +- There shall be only one Procedure Indicator for each procedure; +- If a new field needs to be introduced to an existing procedure (i.e. existing procedure that is defined in an existing UP version), the new field shall not be *added* to the payload part. Instead, the new field may be introduced by placing it to a spare field in the payload part of the frame, if possible; +- However, if a new field needs to be introduced to an existing procedure, but spare field(s) in the payload part cannot be used to introduce the new field, then a new procedure shall be created and hence a new Procedure Indicator value shall be allocated for the new procedure; +- To enable simple protocol evolution, when a new Procedure Indicator will be introduced, the new frame shall include both the new fields and the fields of the old frame; +- When an implementation receives an unknown Procedure Indicator it may use the ERROR EVENT control frame with Cause: "Unknown procedure" to report this. This indicates to the sender that the procedure was not understood and it may try with an older procedure. + +### **8.1.3 Adding a new PDU type** + +In the future, the Iu UP protocol may evolve so that there is a need to add a new PDU type. The criteria for introducing a new PDU type could be e.g.: + +- The Procedure Indicators may run out and there is a need to have more; +- There is a need to change the header mask, e.g. the Frame Number field may need to be increased or the CRC field needs to be modified. + +While the PDU Type 15 is reserved for future PDU type extensions, there may be 'subtypes' under PDU Type 15 in the future and there also may be new procedures in these 'subtypes'. + +Thus it has to be ensured that if the same Procedure Indicator value is used under several PDU types, it should be made clear e.g. in the Error Event cause element, which PDU type it concerns. + +The maximum length of the Spare Extension field is defined per PDU type. Thus when a new PDU type is added, an appropriate length for the Spare Extension field (if any) has to be defined. For Release '99, a length of 4 octets has been used for data PDUs, and 32 octets for control PDUs. + +### **8.1.4 Protocol version handling** + +In the future, new versions of the Iu UP protocol may be introduced. A reason for a new version of the protocol could be, e.g.: + +- The earlier introduced new features or functions are required to be mandatory in the new version; +- Due to technical development, the new version of the protocol could be totally different (and incompatible) from the earlier version. + +The following principles shall be applied to version handling of Iu UP protocol: + +- It shall be possible to introduce additional modes of operation; +- It shall be possible to evolve the operation modes independently of each other; +- There shall be independent version numbers for each mode of operation; +- The mode of operation of an Iu UP protocol instance is decided by the CN. Further, the CN shall indicate those versions that are required to support certain features, e.g. TrFO. The version of the mode among the required ones shall be negotiated between the CN and UTRAN during Initialisation procedure; +- The version number of a UP operation mode may change or be unchanged between different releases; +- When the protocol is evolved it shall be made clear in the specification, which features belong to which versions; +- A new version may be an evolution (i.e. compatible) of the old version or the new version may be totally different from the old version. +- The structure of the PDU Type 14 header, up to and including header CRC, shall remain unchanged whatever the Iu UP version. + +# --- Annex A (informative): Illustration of usage of RFCI for AMR speech RAB + +This annex contains information related to usage of RFCIs in the context of AMR speech RAB. + +The following figure illustrates the RFCI allocation and flow throughout the UTRAN. + +![Diagram illustrating the RAB establishment and reconfiguration process between UE, RNC, and CN. The diagram is divided into Control Plane (CP) and User Plane (UP). In the CP, the CN sends RAB attributes to the RNC, which then allocates RFCIs, configures L2/L3, and initializes the Iu UP. The RNC configures the UE's L2/L3 based on these RFCIs. In the UP, the RNC sends initialization information (RFCI, sub-flow size) to the UE's L2/L3 and to the CN's Iu UP. Data flows from NAS streams in the UE through L2/L3 and L1 to the RNC's L1, then to the RNC's L2/L3, which adds an RFCI and SDU to form an Iu frame. This frame is sent to the CN's Iu UP, which adds sub-flow size information and sends it to the CN's NAS streams.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +Diagram illustrating the RAB establishment and reconfiguration process between UE, RNC, and CN. The diagram is divided into Control Plane (CP) and User Plane (UP). In the CP, the CN sends RAB attributes to the RNC, which then allocates RFCIs, configures L2/L3, and initializes the Iu UP. The RNC configures the UE's L2/L3 based on these RFCIs. In the UP, the RNC sends initialization information (RFCI, sub-flow size) to the UE's L2/L3 and to the CN's Iu UP. Data flows from NAS streams in the UE through L2/L3 and L1 to the RNC's L1, then to the RNC's L2/L3, which adds an RFCI and SDU to form an Iu frame. This frame is sent to the CN's Iu UP, which adds sub-flow size information and sends it to the CN's NAS streams. + +1. **RAB Attributes:** at RAB establishment or reconfiguration, the SDU format information parameter is passed to UTRAN. The SDU information is organised per BER i.e. RAB sub Flow. For instance, 12,2 kbits/s AMR codec is passed as RAB sub flow 1 SDU size: 81 bits –class A bits-, as RAB sub flow 2 SDU size: 103 bits –class B bits-, as RAB sub flow 3 SDU size: 60 bits –class C-, which makes one RAB sub Flow Combination. This is done for all source rates (i.e. all codec modes, DTX also if included). So using the RAB subflows combination set from Table A.1, the SDU Formation Information Parameters for RAB subflow 1 is [81,42,39,0], for RAB subflow 2 is [103,53,0,0], and for RAB subflow 3 is [60,0,0,0]. The Iu UP is used in support mode for predefined SDU size. +2. **Allocation of RFCIs:** the RNC dynamically allocates an identification (RFCI) to each permitted/possible combinations it can offer. E.g. for 0 kbits/s, the RNC allocates RFCI 0, for the SID, the RNC allocates RFCI 3, for 4,75 kbits/s, the RNC allocates RFCI 2, and for 12,2. kbits/s, the RNC allocates RFCI 1 (according to the example table A.1). +3. **Configuration of L2/L3 based on RFCIs:** RFCIs are used to configure the L2/L3. RLC (TS 25.322 [11]) is used in transparent mode. MAC (TS 25.321 [10]) configures its co-ordinated DCHs with the RFCIs and associates one RFCI to one TFI. +4. **Initialisation of Iu UP:** the RNC reports the permitted combinations it can offer to the transcoder using an inband Iu INITIALISATION control frame containing the RFCIs and associated RAB sub Flow sizes. +5. **Configuration of L2/L3 based on e.g. TFIs:** idem as 3. L2/L3 may use e.g. TFI to communicate with the Codec about the RAB sub-Flow structure of the SDU received or to be sent. +6. **RFCIs+ SDU size information:** the RFCIs and associated RAB sub Flow sizes received within the Iu INITIALISATION control frame are passed to the Codec for configuration. +7. **Example of DL frame transfer:** + - 7.1. The Codec encodes a 12,2 kbits/s frame. It sends down to the Iu UP an SDU with an associated RFCI equals to 1 (in this example). + - 7.2. The Iu UP packs a frame with a header containing an RFCI set to value "1", and the payload made of the SDU received from the Codec. + - 7.3. The Iu UP passes to L2/L3, the Iu frame payload (the Codec SDU) and the RFCI. The L2/L3 uses this RFCI to break the Iu frame onto the co-ordinated DCHs corresponding to the different bits protection classes. The corresponding TFI is selected. + - 7.4. The radio frame is sent with the TFI chosen by MAC (TS 25.321 [10]). + - 7.5. The L2/L3 receives the SDUs on the co-ordinated DCHs, combines them back and uses e.g. the TFI to indicate to the codec the structure of the received frame. + +Figure A.1 + +For information on RAB subflow combinations used for AMR speech see TS 26.102 [12]. + +SRNC allocates one or more possible/available RAB sub-flow combination(s) and generates RAB sub-flow combination set. RAB sub-flow combination number is dynamically generated by SRNC. This RAB sub-flow combination set is signalled towards CN with user plane signalling as described in TS 25.401 [1]. The signalling towards UE is to be defined by TSG-RAN WG2. + +### **RAB sub-flow combination set:** + +A RAB sub-flow combination indicator, RFCI, indicates which RAB sub flow combination will be used for the Iu user frames. In the communication phase the RFCI is included in the user frame, and the RFCI state the structure of the user frame. + +Table A.1 exemplifies the allocation of 4 different RAB sub-flows combinations for 3 sub-flows and generating of RAB sub-flows combination set. + +**Table A.1: Example of Allocation of RAB sub-flows combination indicator** + +| | RFCI
(RAB sub-
Flow
Combination
Indicator) | RAB sub-
Flow 1 | RAB sub-
flow 2 | RAB sub-
flow 3 | Total | Source rate | +|--------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|----------------------------|----------------------------|--------------|--------------------| +| RAB
sub-
flows
combina
tion set | 1 | 81 | 103 | 60 | 244 | Source rate 1 | +| | 2 | 42 | 53 | 0 | 95 | Source rate 2 | +| | 3 | 39 | 0 | 0 | 39 | Source rate 3 | +| | 0 | 0 | 0 | 0 | 0 | Source rate 4 | +| NOTE: | In the table above the greyed area shows the part that is sent in the Initialisation procedure in Iu UP. This is what constitutes the RAB subflow combination set. | | | | | | + +# Annex B (informative): Illustration of protocol states in the Iu UP + +This annex contains information related to possible protocol states for operation of the Iu UP. This annex does not constrain implementation and is for illustration purposes only. + +The state model is common for both ends of the Iu UP so that the protocol machines are operating symmetrically. This approach is taken to facilitate state description for all cases including possible future scenarios where the Iu UP could be terminated elsewhere. + +NOTE: Primitive Iu-UP-CONFIG-Req is used by upper layers to configure the Iu UP protocol layer. It is used in this annex for illustrative purposes and therefore it is not defined in clause 7. + +## B.1 Protocol state model for transparent mode + +Figure B.1 illustrates the state model for transparent mode Iu UP instances. A transparent mode instance can be in one of following states. + +![Figure B.1: Protocol state model for transparent mode. The diagram shows two states: 1. Null and 2. TrM Data Transfer Ready. State 1 is a circle labeled '1.' and 'Null'. State 2 is a circle labeled '2.' and 'TrM Data Transfer Ready'. A transition arrow labeled 'Iu-UP-CONFIG-Req' goes from state 1 to state 2. A self-loop arrow on state 2 is labeled with a list of primitives: Iu-UP-UNIT-DATA-Req or Iu-UP-UNIT-DATA-Ind or SSSAR-UNITDATA-Req or SSSAR-UNITDATA-Ind or Iu-UP-UNITDATA-Ind or Iu-UP-UNITDATA-Req. A transition arrow labeled 'Iu-UP-CONFIG-Req' goes from state 2 back to state 1.](b06a4c871dfd0ce034cf801519d0039a_img.jpg) + +``` + +stateDiagram-v2 + [*] --> 1 : Iu-UP-CONFIG-Req + 1 : Null + 1 --> 2 : Iu-UP-CONFIG-Req + 2 : TrM Data Transfer Ready + 2 --> 1 : Iu-UP-CONFIG-Req + 2 --> 2 : Iu-UP-UNIT-DATA-Req or Iu-UP-UNIT-DATA-Ind or SSSAR-UNITDATA-Req or SSSAR-UNITDATA-Ind or Iu-UP-UNITDATA-Ind or Iu-UP-UNITDATA-Req + +``` + +Figure B.1: Protocol state model for transparent mode. The diagram shows two states: 1. Null and 2. TrM Data Transfer Ready. State 1 is a circle labeled '1.' and 'Null'. State 2 is a circle labeled '2.' and 'TrM Data Transfer Ready'. A transition arrow labeled 'Iu-UP-CONFIG-Req' goes from state 1 to state 2. A self-loop arrow on state 2 is labeled with a list of primitives: Iu-UP-UNIT-DATA-Req or Iu-UP-UNIT-DATA-Ind or SSSAR-UNITDATA-Req or SSSAR-UNITDATA-Ind or Iu-UP-UNITDATA-Ind or Iu-UP-UNITDATA-Req. A transition arrow labeled 'Iu-UP-CONFIG-Req' goes from state 2 back to state 1. + +Figure B.1: Protocol state model for transparent mode + +### B.1.1 Null State + +In the null state the Iu UP instance does not exist and therefore it is not possible to transfer any data through it. + +Upon reception of a Iu-UP-CONFIG-Req from higher layer the Iu UP instance is created and transparent mode data transfer ready state is entered. The mode information is received either through RANAP signalling or directly in the CN node. In the Iu-UP-CONFIG-Req e.g. the following information will be indicated: + +- Transparent mode. + +### B.1.2 Transparent Mode Data Transfer Ready State + +In the transparent mode data transfer ready state, transparent mode data can be exchanged between the entities. + +Upon reception of Iu-UP-CONFIG-Req indicating release from higher layer, the Iu UP instance is terminated and the null state is entered. + +## B.2 Protocol state model for support mode for predefined SDU sizes + +Figure B.2 illustrates the state model for support mode Iu UP instances. A support mode instance can be in one of the following states. + +![thick arrow thin arrow Protocol state model for support mode diagram showing four states: 1. Null, 2. Initialisation, 3. (unlabeled), 4. SMpSDU Data Transfer Ready. Transitions are triggered by Iu-UP-CONFIGReq, Initialisation (Repeat), Last Initialisation ACK sent or Last Initialisation Ack received, Negative Initialisation Ack, Iu-UP-STATUSInd (Rate control), Rate control PDU, and various data transfer primitives.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +Iu PDU + Primitive between layers + +``` + +stateDiagram-v2 + [*] --> 1: Null + 1 --> 2: Initialisation (Iu-UP-CONFIGReq) + 2 --> 2: Initialisation (Repeat) + 2 --> 4: Last Initialisation ACK sent or Last Initialisation Ack received + 2 --> 1: Iu-UP-CONFIGReq + 2 --> 3: Negative Initialisation Ack + 3 --> 2: Initialisation + 3 --> 4: Iu-UP-STATUSInd (Rate control) + 4 --> 1: Iu-UP-CONFIGReq + 4 --> 4: Rate control PDU + 4 --> 4: Iu-UP-DATAReq or Iu-UP-DATAInd or SSSAR-UNITDATAReq or SSSAR-UNITDATAInd or Iu-UP-UNITDATAInd or Iu-UP-UNITDATAReq + +``` + +thick arrow thin arrow Protocol state model for support mode diagram showing four states: 1. Null, 2. Initialisation, 3. (unlabeled), 4. SMpSDU Data Transfer Ready. Transitions are triggered by Iu-UP-CONFIGReq, Initialisation (Repeat), Last Initialisation ACK sent or Last Initialisation Ack received, Negative Initialisation Ack, Iu-UP-STATUSInd (Rate control), Rate control PDU, and various data transfer primitives. + +**Figure B.2: Protocol state model for support mode** + +### B.2.1 Null State + +In the null state the Iu UP instance does not exist and therefore it is not possible to transfer any data through it. + +Upon reception of a Iu-UP-CONFIG-Req from higher layer the Iu UP instance is created and initialisation state is entered. In the Iu-UP-CONFIG-Req e.g. the following information could be indicated: + +- Support mode for predefined SDU sizes; +- Time alignment (FFS); +- Indication of delivery of erroneous SDUs; +- Periodicity; +- required UP versions. + +### B.2.2 Initialisation State + +In the initialisation state the instance exchanges initialisation information with its peer Iu UP instance. + +Upon reception of Iu-UP-CONFIG-Req indicating release from higher layer, the Iu UP instance is terminated and the null state is entered. + +Upon sending or receiving of an INITIALISATION control frame the Iu UP instance remains in the Initialisation state. The sending side starts a supervision timer $T_{INIT}$ . The receiving side acknowledges the INITIALISATION control frame with a positive acknowledgement or a negative acknowledgement. + +Upon reception of the last initialisation acknowledgement frame, the supervision timer $T_{INIT}$ is stopped and the Iu UP instance enters SMpSDU data transfer ready state. + +After sending a positive acknowledgement of the last INITIALISATION control frame, the Iu UP instance enters SMpSDU data transfer ready state. Note that CN does not know if the initialisation ACK was correctly received by the RNC (and Initialisation procedure successfully completed) until it receives RAB assignment response, or use data from + +the RNC. The CN must therefore be able to continue receiving INITIALISATION control frames by re-entering the Initialisation state (from Support Mode Data Transfer Ready State), if the CN has started to send user data before receiving the indication that Initialisation was successfully completed. + +Upon reception of an INITIALISATION NEGATIVE ACKNOWLEDGEMENT control frame (INIT NACK) initialisation frame can be repeated n times. + +If after n repetitions, the Initialisation procedure is unsuccessfully terminated (due to n negative acknowledgements or timer expires) the Handling of Error Event procedure is used to report the Initialisation failure and the Iu UP instance remains in the initialisation state. Upon reception of an INITIALISATION control frame the Initialisation state is entered. + +### B.2.3 Support Mode Data Transfer Ready State + +In the support mode data transfer ready state, support mode data can be exchanged between the peer Iu UP instances. + +Upon reception of Iu-UP-DATA-Request from the upper layer or SSSAR-UNITDATA-Indication or Iu-UP-UNITDATA-Indication from TNL layer, appropriate user data transfer procedures are performed. Iu UP instance remains in the SMpSDU data transfer ready state. + +Upon sending of Iu-UP-DATA-Indication or SSSAR-UNITDATA-Request or Iu-UP-UNITDATA-Request the Iu UP instance remains in the SMpSDU data transfer ready state. + +Upon sending or receiving of a rate control PDU the Iu UP instance remains in the SMpSDU data transfer ready state. + +Upon sending of a Iu-UP-STATUS-Indication (rate control) the Iu UP instance remains in the SMpSDU data transfer ready state. + +Upon reception of Iu-UP-CONFIG-Req from higher layer the Iu UP instance is terminated and the null state is entered. + +Upon detection of a protocol fault, Iu-UP-STATUS-Indication is sent to upper layer an ERROR EVENT control frame may be sent over Iu UP. + +In case of handover or relocation, Initialisation procedures may have to be performed and Iu UP instance may have to enter the initialisation state. + +# --- Annex C (informative): Open Issues of the Iu UP + +This annex contains information related to open issues left in the Iu UP protocol. + +# Annex D (informative): Distributed rate decision within RNC + +This annex contains information related to the distributed rate decision within an RNC (see also within TS 23.153 [13]) + +The Iu Rate Control procedure over Iu UP is normally controlled by the entity controlling the rate control over UTRAN i.e. the SRNC. The SRNC may send RATE CONTROL control frames in uplink (to the CN) to control the rates in downlink. The SRNC may also send RATE CONTROL control frames in downlink (to the UE) to control the rates in uplink. The Iu Rate Control procedures for both directions are independent of each other, i.e. different rates may be permitted in uplink and downlink, see figure D.1. + +![Figure D.1: Rate Control for uplink and downlink. This sequence diagram shows the interaction between a User Equipment (UE), a Serving Radio Network Controller (SRNC), and a Core Network (CN). For uplink data flow: UE sends 'User Data with uplink Rates' to SRNC, which then sends 'User Data' to CN. SRNC sends 'Rate Control for uplink' back to UE. For downlink data flow: CN sends 'User Data with downlink Rates' to SRNC, which then sends 'User Data' to UE. SRNC sends 'Rate Control for downlink' to CN.](4842f073775fb1e84d101c02fd74e59e_img.jpg) + +Figure D.1: Rate Control for uplink and downlink. This sequence diagram shows the interaction between a User Equipment (UE), a Serving Radio Network Controller (SRNC), and a Core Network (CN). For uplink data flow: UE sends 'User Data with uplink Rates' to SRNC, which then sends 'User Data' to CN. SRNC sends 'Rate Control for uplink' back to UE. For downlink data flow: CN sends 'User Data with downlink Rates' to SRNC, which then sends 'User Data' to UE. SRNC sends 'Rate Control for downlink' to CN. + +Figure D.1: Rate Control for uplink and downlink + +The rates associated with the service could be rank ordered from "lower" to "higher" according to their SDU bit rates and RFCI values, with RFCI=0 having the lowest rate. A rate lower than the currently allowed maximum rate shall not be forbidden while a higher rate is forbidden. In order to stabilise the Iu Rate Control procedure and its influences on the radio link and the network, typically only one additional rate shall be forbidden or permitted in subsequent RATE CONTROL control frames. + +In some cases, as TrFO and TFO, the rate is also controlled by the remote partner at the other end of the Iu UP. The SRNC may then also receive RATE CONTROL control frames in downlink (from the CN) controlling the rates in uplink. Only rates that are permitted by both sides for one direction shall be used in that direction. The SRNC shall therefore combine these RATE CONTROL control frames from the CN with its own control frames for the uplink direction by taking the RATE CONTROL control frame with the lowest maximum rate and shall send this RATE CONTROL control frame downlink to the UE. This combination is denoted in figure D.2 with "Rate Control (CN $\oplus$ RNC)". + +![Figure D.2: Distributed Rate Control for uplink and downlink. This sequence diagram shows the interaction between UE, SRNC, and CN. For uplink data flow: CN sends 'Rate Control (CN) for uplink' to SRNC, which combines it and sends 'Rate Control (CN ⊕ RNC) for uplink' to UE. UE sends 'User Data with (CN ⊕ RNC) Rates' to SRNC, which sends 'User Data' to CN. For downlink data flow: SRNC sends 'Rate Control (RNC) for downlink' to CN. CN sends 'User Data with (RNC ⊕ CN) Rates' to SRNC, which sends 'User Data' to UE.](7dfd8dd318dcfc36eaf4c967ddfb94c1_img.jpg) + +Figure D.2: Distributed Rate Control for uplink and downlink. This sequence diagram shows the interaction between UE, SRNC, and CN. For uplink data flow: CN sends 'Rate Control (CN) for uplink' to SRNC, which combines it and sends 'Rate Control (CN ⊕ RNC) for uplink' to UE. UE sends 'User Data with (CN ⊕ RNC) Rates' to SRNC, which sends 'User Data' to CN. For downlink data flow: SRNC sends 'Rate Control (RNC) for downlink' to CN. CN sends 'User Data with (RNC ⊕ CN) Rates' to SRNC, which sends 'User Data' to UE. + +Figure D.2: Distributed Rate Control for uplink and downlink + +# Annex E (informative): Change History + +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|---------|-------|-----------|------|-----|------------------------------------------------------------|--------| +| 12/2008 | - | - | - | - | Creation of Rel-8 version based on v7.3.0 | 8.0.0 | +| 12/2009 | - | - | - | - | Creation of Rel-9 version based on v8.0.0 | 9.0.0 | +| 03/2011 | SP-49 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 9.0.1 | +| 03/2011 | | | | | Creation of Rel-10 version based on v9.0.1 | 10.0.0 | +| 06/2011 | RP-52 | SP-110685 | 0134 | - | Reference review outcome in TS 25.415 | 10.1.0 | +| 09/2012 | | | | | Update to Rel-11 version (MCC) | 11.0.0 | +| 09/2014 | | | | | Update to Rel-12 version (MCC) | 12.0.0 | +| 12/2015 | | | | | Update to Rel-13 version (MCC) | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-07 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25423/0236eff05bcb8f3a343ea7933aaa306b_img.jpg b/marked/Rel-16/25_series/25423/0236eff05bcb8f3a343ea7933aaa306b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa93646ee3563857936936b6614864e4415d04e7 --- /dev/null +++ b/marked/Rel-16/25_series/25423/0236eff05bcb8f3a343ea7933aaa306b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e159e82a8f2f163b26f5037cbc99dafd5708fafb4f88faa84f152ead2fa5a6cf +size 16702 diff --git a/marked/Rel-16/25_series/25423/08dc2b08505b6d410e87ee06169c0138_img.jpg b/marked/Rel-16/25_series/25423/08dc2b08505b6d410e87ee06169c0138_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f3413c6450ec33ab3e5d7ddee29e2e4c6a8449a --- /dev/null +++ b/marked/Rel-16/25_series/25423/08dc2b08505b6d410e87ee06169c0138_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab4d6d4da318d78dc19b94f0094e466f47e9b08622b66b51e6e6530739201fe4 +size 12695 diff --git a/marked/Rel-16/25_series/25423/0bc457309c9a1d646ef180bec2a40c67_img.jpg b/marked/Rel-16/25_series/25423/0bc457309c9a1d646ef180bec2a40c67_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0790ba9fa80a6be9ee573bfea39334a00cb2ee06 --- /dev/null +++ b/marked/Rel-16/25_series/25423/0bc457309c9a1d646ef180bec2a40c67_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41bfd28e5e995094024879b2c633f70edd5c0ec201b965e07c5e6769ab0aa9f5 +size 17525 diff --git a/marked/Rel-16/25_series/25423/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg b/marked/Rel-16/25_series/25423/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ec1689de6aaa5a2e17beca78a9557c16ebc9a84 --- /dev/null +++ b/marked/Rel-16/25_series/25423/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:431a70f40f5794c29d6fd4206af2dd7ed89d7725e6f88ab79260eb53be74eed6 +size 8749 diff --git a/marked/Rel-16/25_series/25423/110f34c10cc121cff8e43e077cf1a17e_img.jpg b/marked/Rel-16/25_series/25423/110f34c10cc121cff8e43e077cf1a17e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..600b8ffa08c58279f3f90e7e896aaeff8e72df29 --- /dev/null +++ b/marked/Rel-16/25_series/25423/110f34c10cc121cff8e43e077cf1a17e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2543ccd5233fe60d7754649f9d6e816f24c8903182f458b380f2d4c6776069a5 +size 25080 diff --git a/marked/Rel-16/25_series/25423/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg b/marked/Rel-16/25_series/25423/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..16c642fc00fb925362a714b483cf58220219dfaf --- /dev/null +++ b/marked/Rel-16/25_series/25423/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9a53b7d1dc8ea5780679b290e43f53c13a2e05cd071e6cc9f606e347c2069ef +size 4064 diff --git a/marked/Rel-16/25_series/25423/2349d057cdc64596dc83dc213b8663a8_img.jpg b/marked/Rel-16/25_series/25423/2349d057cdc64596dc83dc213b8663a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ceb566dd6b48fd45947f34446bf452db0ee12f1c --- /dev/null +++ b/marked/Rel-16/25_series/25423/2349d057cdc64596dc83dc213b8663a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:76a3c5b1880b60707b6bfbfe89bb39a9405ebe73b5b62361574e72dafdc43035 +size 7422 diff --git a/marked/Rel-16/25_series/25423/2b93d528fd010ad8f6201ab02e16c78d_img.jpg b/marked/Rel-16/25_series/25423/2b93d528fd010ad8f6201ab02e16c78d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61f97d7e1df65475da926ac587f026bca5481589 --- /dev/null +++ b/marked/Rel-16/25_series/25423/2b93d528fd010ad8f6201ab02e16c78d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a712ca94c2b8ac6eb74e4a0e98167d2dc03be02ae0feb6dc90d1ba92078bfbd3 +size 62277 diff --git a/marked/Rel-16/25_series/25423/2eeb7659a0fe7db3edb4e8695f880ffa_img.jpg b/marked/Rel-16/25_series/25423/2eeb7659a0fe7db3edb4e8695f880ffa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3321fd47e7860ff3bff64c1c53e22295533bbf08 --- /dev/null +++ b/marked/Rel-16/25_series/25423/2eeb7659a0fe7db3edb4e8695f880ffa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58d34e8d94e98c2eb3757b7283742c38e2b7c72fbb6d2c04b7e3686b7339ed84 +size 12045 diff --git a/marked/Rel-16/25_series/25423/2f23935e5daba6229f9c6e1fab18a441_img.jpg b/marked/Rel-16/25_series/25423/2f23935e5daba6229f9c6e1fab18a441_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b96756e76e4a9edd86279eedac87a9b18854e70 --- /dev/null +++ b/marked/Rel-16/25_series/25423/2f23935e5daba6229f9c6e1fab18a441_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe2a44656df3f7a19b0019f43a6b04ffcb477c61900635b10ee02df862837b84 +size 10510 diff --git a/marked/Rel-16/25_series/25423/3a517a5df8c0bf69791d27fd9d0d52d5_img.jpg b/marked/Rel-16/25_series/25423/3a517a5df8c0bf69791d27fd9d0d52d5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ab53fca72444577ad27dd404e35c6e2e3801c26 --- /dev/null +++ b/marked/Rel-16/25_series/25423/3a517a5df8c0bf69791d27fd9d0d52d5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dbcc58f301f29f6bb72821609e8f2f35a0fc35739689fefa11970523ebbb978b +size 101100 diff --git a/marked/Rel-16/25_series/25423/3e3b0d2b0dcf80f0c4e84f57bd2c1433_img.jpg b/marked/Rel-16/25_series/25423/3e3b0d2b0dcf80f0c4e84f57bd2c1433_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e2a066e6ba7133af2bd834f83469b980ba2cf21 --- /dev/null +++ b/marked/Rel-16/25_series/25423/3e3b0d2b0dcf80f0c4e84f57bd2c1433_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43726cad70ef7a20a3ec32cad26c37cd636ead08694783d466e78b0afac61d31 +size 37009 diff --git a/marked/Rel-16/25_series/25423/42ab2aee8612b8eb35a8e9597d6c1449_img.jpg b/marked/Rel-16/25_series/25423/42ab2aee8612b8eb35a8e9597d6c1449_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cdf61869d0cfd55b291c552363f6df52c9610b13 --- /dev/null +++ b/marked/Rel-16/25_series/25423/42ab2aee8612b8eb35a8e9597d6c1449_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:085cd034842244cde7e8f15da91f5673f86b2ae913bbac9044a69eea43554cf1 +size 61504 diff --git a/marked/Rel-16/25_series/25423/4a9454b4354535e1b61423084da1424b_img.jpg b/marked/Rel-16/25_series/25423/4a9454b4354535e1b61423084da1424b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54e832dbce70aebaed369680056a91d60ca527b7 --- /dev/null +++ b/marked/Rel-16/25_series/25423/4a9454b4354535e1b61423084da1424b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:699eca4e3a645326cbe4881e31951a7f6e0a7b540e0b1a11a5d456760a7f5435 +size 12891 diff --git a/marked/Rel-16/25_series/25423/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg b/marked/Rel-16/25_series/25423/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1b7604328fe723947a17cdce5e6f6484d34dbd4 --- /dev/null +++ b/marked/Rel-16/25_series/25423/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:adc4834a14e3da7da53a75faed58140cfae67c7b1cc73befd860fabd6d98caa4 +size 9397 diff --git a/marked/Rel-16/25_series/25423/4e9d567cb34883f2bbf15fa6bd1a9873_img.jpg b/marked/Rel-16/25_series/25423/4e9d567cb34883f2bbf15fa6bd1a9873_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33e20f2759c0e62f50d8a214ae2af4e0ee8d0328 --- /dev/null +++ b/marked/Rel-16/25_series/25423/4e9d567cb34883f2bbf15fa6bd1a9873_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d0833f0070bc372d06b8b4ff0017e4047087c2ab67867fdf4adee64dc89a8dc +size 9517 diff --git a/marked/Rel-16/25_series/25423/51da4c98724f1f105d1d2fb1867e526f_img.jpg b/marked/Rel-16/25_series/25423/51da4c98724f1f105d1d2fb1867e526f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48aeb09a1c7e320419023ddbe3acc7e7de3dd1b5 --- /dev/null +++ b/marked/Rel-16/25_series/25423/51da4c98724f1f105d1d2fb1867e526f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40ad4c33627a8a3c246031f34d9e40f9d830b3c6552270c91691eb55e48ed7a2 +size 10863 diff --git a/marked/Rel-16/25_series/25423/58c06f7ad7d3d86e8161f0a2218c7b54_img.jpg b/marked/Rel-16/25_series/25423/58c06f7ad7d3d86e8161f0a2218c7b54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f950f3847503f6f63cfa52d55742b6d3700592fb --- /dev/null +++ b/marked/Rel-16/25_series/25423/58c06f7ad7d3d86e8161f0a2218c7b54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32bced517501297732add7f308fb6fc483633b00f1d6cf2c82eca4edd082d8d7 +size 13795 diff --git a/marked/Rel-16/25_series/25423/6343a896ff7c6a10ec2f48bad236b8bf_img.jpg b/marked/Rel-16/25_series/25423/6343a896ff7c6a10ec2f48bad236b8bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f534f25f34b4516c28063a5fada778ee1a8f5f5 --- /dev/null +++ b/marked/Rel-16/25_series/25423/6343a896ff7c6a10ec2f48bad236b8bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5a3635c205967487d8301dcf053a968597576fb38f45c16254b6c3ce3da2abf +size 13276 diff --git a/marked/Rel-16/25_series/25423/68294300c741a1558986e2b2c12996bf_img.jpg b/marked/Rel-16/25_series/25423/68294300c741a1558986e2b2c12996bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ce04056b5f94acdddb1198be375269d43ce1da7 --- /dev/null +++ b/marked/Rel-16/25_series/25423/68294300c741a1558986e2b2c12996bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f3dbc4184f95b547cd65363fa4bc303c9467ae37f2dd824e42de1b01f79dd67 +size 10228 diff --git a/marked/Rel-16/25_series/25423/6a42c23912e60f3df7f5536d060cbab8_img.jpg b/marked/Rel-16/25_series/25423/6a42c23912e60f3df7f5536d060cbab8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20cd6c562f24e7e015c1e55bab4b0c5a6cc63866 --- /dev/null +++ b/marked/Rel-16/25_series/25423/6a42c23912e60f3df7f5536d060cbab8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b4fb625c4cc327824d6363033b02ff656ea42caa2a88dce2b26235eb33481ba +size 10451 diff --git a/marked/Rel-16/25_series/25423/6b2cc2f3ac111c43dca12649a9738e91_img.jpg b/marked/Rel-16/25_series/25423/6b2cc2f3ac111c43dca12649a9738e91_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62541fb2e6ed75fcbba40a763c3c6f20d7ce0dd5 --- /dev/null +++ b/marked/Rel-16/25_series/25423/6b2cc2f3ac111c43dca12649a9738e91_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf94bdc5c173bfd9817d490ed7948d8e3cad36c68695f219386ae3f90779ca0b +size 11067 diff --git a/marked/Rel-16/25_series/25423/6e612452d995bb03cc3f3d004493f7bf_img.jpg b/marked/Rel-16/25_series/25423/6e612452d995bb03cc3f3d004493f7bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb42748a9961103d9201e59e3d3240a997085aea --- /dev/null +++ b/marked/Rel-16/25_series/25423/6e612452d995bb03cc3f3d004493f7bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09b99854a188e2992bab0c099633adb8946a89863c46f4e5b628df1dd8426cc6 +size 8220 diff --git a/marked/Rel-16/25_series/25423/742ec4a15f1400e46088821c49e4521d_img.jpg b/marked/Rel-16/25_series/25423/742ec4a15f1400e46088821c49e4521d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..afe8b35a9f5ae889e5323abb9d6b2f7c9a14f231 --- /dev/null +++ b/marked/Rel-16/25_series/25423/742ec4a15f1400e46088821c49e4521d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:492895b9f9aefaff0a2da5d53f735998ad77cb92eac98c22c6d6f77cff1ff69e +size 14026 diff --git a/marked/Rel-16/25_series/25423/81a736eb35b4bda9584394c61ef44aec_img.jpg b/marked/Rel-16/25_series/25423/81a736eb35b4bda9584394c61ef44aec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1613033d76512ce019191fca0701841a6e40a90 --- /dev/null +++ b/marked/Rel-16/25_series/25423/81a736eb35b4bda9584394c61ef44aec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:877b7e7a60730a2dda417b8a48f22de69b2d00408d754e2e4bc3e32ef27a44b6 +size 8193 diff --git a/marked/Rel-16/25_series/25423/973b865a41c0e816900ce8221257edb5_img.jpg b/marked/Rel-16/25_series/25423/973b865a41c0e816900ce8221257edb5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..463a4ad31b8946fd92492771f26fbd9c9fc6bb2a --- /dev/null +++ b/marked/Rel-16/25_series/25423/973b865a41c0e816900ce8221257edb5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1df52a2ad6cfb452b2201ce894457abdc1b689624aeb7500411a59c721103245 +size 35487 diff --git a/marked/Rel-16/25_series/25423/9781500979b73a4fe5978f19edc42797_img.jpg b/marked/Rel-16/25_series/25423/9781500979b73a4fe5978f19edc42797_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3890d137fa236861d293f233d3b38fad429b8cf3 --- /dev/null +++ b/marked/Rel-16/25_series/25423/9781500979b73a4fe5978f19edc42797_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a215f0cc88f747ed218ca507fe5df06902e91eae502ce5b620c50c5edbc41f05 +size 8957 diff --git a/marked/Rel-16/25_series/25423/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg b/marked/Rel-16/25_series/25423/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8e834a88e9c1307a89b4ec32acb7c3ee553ce16 --- /dev/null +++ b/marked/Rel-16/25_series/25423/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9deeb2345ce8c4f28014edf6cb40197d1c402808eb5e3205fbf967f99b99424 +size 11282 diff --git a/marked/Rel-16/25_series/25423/a4b963a07cc368283154762c4b156fe7_img.jpg b/marked/Rel-16/25_series/25423/a4b963a07cc368283154762c4b156fe7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03a147f98b05f865185d8d58982889783d87264d --- /dev/null +++ b/marked/Rel-16/25_series/25423/a4b963a07cc368283154762c4b156fe7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be9355bc2dcdda2012f454c3b4c8c5e3fb010a6229636082ff86253ba79e3810 +size 7156 diff --git a/marked/Rel-16/25_series/25423/b6b53a74ad203c01b81e5427e9d6a898_img.jpg b/marked/Rel-16/25_series/25423/b6b53a74ad203c01b81e5427e9d6a898_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bf3055a8237e5b873ef65ece659d2c6ef9e7ff0 --- /dev/null +++ b/marked/Rel-16/25_series/25423/b6b53a74ad203c01b81e5427e9d6a898_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:785cba44e6e591926f910dc1ddfe23065a4bae6a1af207b4a038bce10f8a6445 +size 7450 diff --git a/marked/Rel-16/25_series/25423/baa3c4cb711c7705f7cf103420c0772c_img.jpg b/marked/Rel-16/25_series/25423/baa3c4cb711c7705f7cf103420c0772c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..177ae5ff765191a74ca2b9cf242303934adb7593 --- /dev/null +++ b/marked/Rel-16/25_series/25423/baa3c4cb711c7705f7cf103420c0772c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb5555dd31fe61488957e7518925b1f898342f327f14eb53f8cf4781f69dd251 +size 73515 diff --git a/marked/Rel-16/25_series/25423/bb0b08eaa6a4593f1502cd14476f0533_img.jpg b/marked/Rel-16/25_series/25423/bb0b08eaa6a4593f1502cd14476f0533_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ddee1ca27954d7a0f96ad3207bd63b6ae2618b9d --- /dev/null +++ b/marked/Rel-16/25_series/25423/bb0b08eaa6a4593f1502cd14476f0533_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21a74c1189dc6f015200d1d9db103d0a21e09e62ec43117187eb57ac473f32bf +size 16885 diff --git a/marked/Rel-16/25_series/25423/bba9cf8cc36473e1255bf8d87d1c2650_img.jpg b/marked/Rel-16/25_series/25423/bba9cf8cc36473e1255bf8d87d1c2650_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52ddacab730657df53367e080957748ffc4c5e1a --- /dev/null +++ b/marked/Rel-16/25_series/25423/bba9cf8cc36473e1255bf8d87d1c2650_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3052f08cabcb6a8ed381cb6d9cfc630b8d804c2a00d174da137e781e7e7dfc7b +size 17155 diff --git a/marked/Rel-16/25_series/25423/c268cf93f90926f7873fafe9c3ab3808_img.jpg b/marked/Rel-16/25_series/25423/c268cf93f90926f7873fafe9c3ab3808_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf7eb12aeeab3244c35efd3a90c50ff2e61ad3ad --- /dev/null +++ b/marked/Rel-16/25_series/25423/c268cf93f90926f7873fafe9c3ab3808_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1cb94a6e8210c53924261b5df2fff34ebd87bff92b5f5b5f1cc7f43ad9625b7f +size 13400 diff --git a/marked/Rel-16/25_series/25423/d980a3f9608055996a07f31788baf827_img.jpg b/marked/Rel-16/25_series/25423/d980a3f9608055996a07f31788baf827_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62a1e25d15d0c58bce417d7173d4370f9eabd165 --- /dev/null +++ b/marked/Rel-16/25_series/25423/d980a3f9608055996a07f31788baf827_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:972d9a3bc0742ce86658081924b7f5db10aa8062a29bdf21dd108a937df89442 +size 8339 diff --git a/marked/Rel-16/25_series/25423/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/Rel-16/25_series/25423/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..310630864f79cace3c3a5bf1f563bbb82963c5bd --- /dev/null +++ b/marked/Rel-16/25_series/25423/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b03e5bd0e201509e10af95e6c628c8ec53886572de495def6a6ed239a33ddf37 +size 10697 diff --git a/marked/Rel-16/25_series/25423/e4bbddb050930c71ba62996a2e194549_img.jpg b/marked/Rel-16/25_series/25423/e4bbddb050930c71ba62996a2e194549_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b080414ad7b59d186330608d35be4ea26a291ee5 --- /dev/null +++ b/marked/Rel-16/25_series/25423/e4bbddb050930c71ba62996a2e194549_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:807728a13ec409660247bf89f70344f7b22959acf21fe9a706d0dd19d8270c26 +size 12971 diff --git a/marked/Rel-16/25_series/25423/e94cbc0895c6914a2bb53f150ab7495e_img.jpg b/marked/Rel-16/25_series/25423/e94cbc0895c6914a2bb53f150ab7495e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8975ff77588875253f1025b841ca2c1671017b39 --- /dev/null +++ b/marked/Rel-16/25_series/25423/e94cbc0895c6914a2bb53f150ab7495e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d124d630369dba0fccd16ee309938d927aaa4d64ac6d2d8e7fca9e05ac70800b +size 25705 diff --git a/marked/Rel-16/25_series/25423/ea37ab05b033e59cfdf7b074161aaf5a_img.jpg b/marked/Rel-16/25_series/25423/ea37ab05b033e59cfdf7b074161aaf5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f532f20ede2f543a2410c1304fcc1b17aeb7eea3 --- /dev/null +++ b/marked/Rel-16/25_series/25423/ea37ab05b033e59cfdf7b074161aaf5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a6647e285c445dd91912dbc23b95e9adaadf522a69cffd99c5f97bf97329d32 +size 10023 diff --git a/marked/Rel-16/25_series/25423/fb9103d56866771588657f738a3ff0fe_img.jpg b/marked/Rel-16/25_series/25423/fb9103d56866771588657f738a3ff0fe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c1b4585857fd35f08a40291d53d6b66c9b43d73 --- /dev/null +++ b/marked/Rel-16/25_series/25423/fb9103d56866771588657f738a3ff0fe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f3026d82207230d5120daa02c2cac1b823ef0ad9b9180597f02e3a1d380ff3d +size 8850 diff --git a/marked/Rel-16/25_series/25430/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg b/marked/Rel-16/25_series/25430/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8bc081449131a4bbdbcaae20e8bc6fa51845ff1d --- /dev/null +++ b/marked/Rel-16/25_series/25430/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66824025d5b60f751e22be73b60cb48ab89dcf9ee31e5092fecd3f6e7da6c672 +size 63214 diff --git a/marked/Rel-16/25_series/25430/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg b/marked/Rel-16/25_series/25430/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd30852cc3676605bc7937354f098767ead8ae01 --- /dev/null +++ b/marked/Rel-16/25_series/25430/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d658c6d13d53acc57e9bcd5dd45ed4e455da9be23e1b3b3612bc1cecb5b2f87 +size 23027 diff --git a/marked/Rel-16/25_series/25430/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg b/marked/Rel-16/25_series/25430/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0c8f9407496f444965d5ef82f7ffd2361f576d6 --- /dev/null +++ b/marked/Rel-16/25_series/25430/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12d44bc70eb088adc7ad2eff4547c7cb832f4b3d7cd100fb3bbfbf6646e80811 +size 96273 diff --git a/marked/Rel-16/25_series/25430/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/25_series/25430/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ceb49ba79433a5754b3c0785584e887b890722d0 --- /dev/null +++ b/marked/Rel-16/25_series/25430/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a1f04d1e1d62a1e0554ed92d01ac5bc88b37dfdcc684481197b2f4b62c8a909 +size 37487 diff --git a/marked/Rel-16/25_series/25430/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/25_series/25430/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..717fa650117b8a423b1e5d6b6fe6c37d1eb0c509 --- /dev/null +++ b/marked/Rel-16/25_series/25430/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98ddae6523ba5ee443f026c178fcc15d860c54e659875edc7f5f2dd5f40e6981 +size 94274 diff --git a/marked/Rel-16/25_series/25430/b2ea162a0f53d5e0504b7d28346e0754_img.jpg b/marked/Rel-16/25_series/25430/b2ea162a0f53d5e0504b7d28346e0754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3fa17cb426b1de8344ffb500b50e30c99072c4d1 --- /dev/null +++ b/marked/Rel-16/25_series/25430/b2ea162a0f53d5e0504b7d28346e0754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12bee6bd20f6aa3dee2a491179fa27f2eda1a0e95c86636dd4f39a21f1e891ea +size 100576 diff --git a/marked/Rel-16/25_series/25430/df0bcbfa8f8e1937e071445426c28022_img.jpg b/marked/Rel-16/25_series/25430/df0bcbfa8f8e1937e071445426c28022_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f75894b0e16b2188f23bedf0d0baea7e2dad4ebe --- /dev/null +++ b/marked/Rel-16/25_series/25430/df0bcbfa8f8e1937e071445426c28022_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b941053688f724c3c65195fde11531ff7b3267d1ec36fb246e33d322f9fbe4a +size 79032 diff --git a/marked/Rel-16/25_series/25430/e636d7ccca0ad14c6b95201404324823_img.jpg b/marked/Rel-16/25_series/25430/e636d7ccca0ad14c6b95201404324823_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43a1e488e094b822bed98dcd0767a23aff94e77c --- /dev/null +++ b/marked/Rel-16/25_series/25430/e636d7ccca0ad14c6b95201404324823_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88c0995bd6f75bbfaa6deda0956591713ebd85059e9544cdafcea4cdbf438975 +size 47726 diff --git a/marked/Rel-16/25_series/25430/raw.md b/marked/Rel-16/25_series/25430/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..29fd6818fcb900e396c832cc8456a7fa457115c2 --- /dev/null +++ b/marked/Rel-16/25_series/25430/raw.md @@ -0,0 +1,931 @@ + + + + + + +# Contents + +| | | +|-----------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 7 | +| 3.3 Specification Notations ..... | 8 | +| 4 General Aspects ..... | 9 | +| 4.1 Introduction ..... | 9 | +| 4.2 Iub Interface General Principles..... | 9 | +| 4.3 Iub Interface Specification Objectives ..... | 9 | +| 4.4 Iub Interface Capabilities ..... | 9 | +| 4.4.1 Radio application related signalling ..... | 9 | +| 4.4.2 Iub/Iur DCH data stream ..... | 10 | +| 4.4.3 Iub RACH data stream ..... | 10 | +| 4.4.4 Iub CPCH data stream [FDD] ..... | 10 | +| 4.4.5 Iub FACH data stream..... | 10 | +| 4.4.6 Iub DSCH data stream [TDD]..... | 10 | +| 4.4.7 Iub USCH data stream [TDD]..... | 10 | +| 4.4.8 Iub PCH data stream..... | 10 | +| 4.4.9 Iub FDD TFCI2 data stream..... | 10 | +| 4.4.10 Iub HS-DSCH data stream ..... | 11 | +| 4.4.11 Iub E-DCH data stream ..... | 11 | +| 4.5 Iub Interface Characteristics..... | 11 | +| 4.5.1 Mapping of Iub data streams ..... | 11 | +| 4.6 Iub Protocols ..... | 11 | +| 5 Functions of the I ub Interface Protocols ..... | 12 | +| 5.1 Iub Functions..... | 12 | +| 5.2 Functional split over Iub ..... | 13 | +| 5.2.1 Management of Iub Transport Resources..... | 13 | +| 5.2.2 Logical O&M of Node B..... | 13 | +| 5.2.2.1 Handling of Node B Hardware Resources..... | 13 | +| 5.2.3 Implementation Specific O&M Transport..... | 13 | +| 5.2.4 System Information Management ..... | 13 | +| 5.2.5 Traffic management of Common Channels..... | 14 | +| 5.2.6 Traffic management of Dedicated Channels ..... | 14 | +| 5.2.6.1 Combining/Splitting and Control..... | 14 | +| 5.2.6.2 Handover Decision ..... | 14 | +| 5.2.6.3 Allocation of Physical Channel Resources ..... | 14 | +| 5.2.6.4 UpLink Power Control..... | 14 | +| 5.2.6.5 Down-Link Power Control ..... | 15 | +| 5.2.6.6 Admission Control..... | 15 | +| 5.2.6.7 Power and Interference Reporting ..... | 15 | +| 5.2.7 Traffic management of Shared Channels [TDD] ..... | 15 | +| 5.2.7A Traffic management of High Speed Shared Channels..... | 15 | +| 5.2.8 Timing and Synchronization Management ..... | 15 | +| 6 Node B logical Model over Iub..... | 15 | +| 6.1 Overview ..... | 15 | +| 6.2 Elements of the logical model..... | 16 | +| 6.2.1 Node B Communication Contexts for Dedicated and Shared Channels ..... | 16 | +| 6.2.2 Common Transport Channels..... | 17 | +| 6.2.3 Transport network logical resources..... | 17 | +| 6.2.3.1 Node B Control Port ..... | 17 | +| 6.2.3.2 Communication Control Port..... | 17 | +| 6.2.3.3 Traffic Termination Point ..... | 17 | + +| | | | +|------------------------|-----------------------------------------------------------------------------------------------------------------------------|----| +| 6.2.3.4 | Iub DCH Data Port ..... | 18 | +| 6.2.3.5 | Iub RACH Data Port..... | 18 | +| 6.2.3.6 | Iub CPCH Data Port [FDD]..... | 18 | +| 6.2.3.7 | Iub FACH Data Port ..... | 18 | +| 6.2.3.8 | Iub DSCH Data Port [TDD] ..... | 18 | +| 6.2.3.8A | Iub HS-DSCH Data Port..... | 18 | +| 6.2.3.9 | Iub USCH Data Port [TDD] ..... | 18 | +| 6.2.3.10 | Iub PCH Data Port ..... | 18 | +| 6.2.3.11 | Iub FDD TFCI2 Data Port ..... | 18 | +| 6.2.3.12 | Iub E-DCH Data Port..... | 18 | +| 6.2.4 | Radio Network Logical resources ..... | 19 | +| 6.2.4.1 | Common Resources ..... | 19 | +| 6.2.4.2 | Cell..... | 19 | +| 6.2.4.3 | Common Physical Channels and Common Transport Channels ..... | 21 | +| 6.2.4.4 | Physical Shared Channels ..... | 22 | +| 7 | Iub Interface Protocol Structure..... | 23 | +| 8 | Other Iub Interface Specifications ..... | 23 | +| 8.1 | UTRAN Iub Interface: Layer 1 (TSG RAN 25.431) ..... | 23 | +| 8.2 | UTRAN Iub Interface: Signalling Transport (TSG RAN 25.432)..... | 23 | +| 8.3 | NBAP Specification (TSG RAN 25.433) ..... | 24 | +| 8.4 | UTRAN Iub Interface: Data Transport & Transport Signalling for Common Transport Channel Data Streams (TSG RAN 25.434) ..... | 24 | +| 8.5 | UTRAN Iub Interface: User Plane Protocols for Common Transport Channel Data Streams (TSG RAN 25.435)..... | 24 | +| 8.6 | UTRAN Iur/Iub Interface: Data Transport & Transport Signalling for DCH Data Streams (TSG RAN 25.426)..... | 24 | +| 8.7 | UTRAN Iur/Iub Interface: User Plane Protocol for DCH Data Streams (TSG RAN 25.427) ..... | 24 | +| 8.8 | Summary of UTRAN Iub Interface Technical Specifications ..... | 25 | +| Annex A (informative): | Change history..... | 26 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd 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 is an introduction to the TSG RAN TS 25.43x series of UMTS Technical Specifications that define the Iub Interface. The Iub interface is a logical interface for the interconnection of Node B and Radio Network Controller (RNC) components of the UMTS Terrestrial Radio Access Network (UTRAN) for the UMTS system. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TS 25.401: "UTRAN overall description". +- [2] 3GPP TS 25.442: "UTRAN implementation-specific O&M transport". +- [3] 3GPP TS 25.432: "UTRAN Iub interface: signalling transport". +- [4] 3GPP TS 25.302: "Services provided by the physical layer". +- [5] 3GPP TS 25.431: "UTRAN Iub interface layer 1". +- [6] Void +- [7] 3GPP TS 25.433: "UTRAN Iub interface Node B Application Part (NBAP) signalling". +- [8] 3GPP TS 25.434: "UTRAN Iub Interface Data Transport and Transport Signalling for Common Transport Channel Data Streams". +- [9] 3GPP TS 25.435: "UTRAN Iub Interface user plane protocols for Common Transport Channel data streams". +- [10] 3GPP TS 25.426: "UTRAN Iur and Iub Interface data transport & transport signalling for DCH data streams". +- [11] 3GPP TS 25.427: "UTRAN Iur/Iub Interface user plane protocol for DCH data streams". +- [12] 3GPP TS 25.402: "Synchronization in UTRAN Stage 2". +- [13] ITU-T Recommendation Q.2630.2 (1999-12): "AAL type 2 Signalling Protocol (Capability Set 2)". +- [14] 3GPP TS 25.319: "Enhanced Uplink; Overall description; Stage 2". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**Propagation delay (PD):** it is the round trip propagation delay of the radio signal from the Node B to the UE and back to the BS in one chip resolution. + +**Timing Advance (TA):** it is the amount of time, expressed in number of chips, by which the transmission of an uplink burst is anticipated by the UE in order to be received by the cell inside the corresponding time slot. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|----------|------------------------------------------------------------------| +| AAL2 | ATM Adaptation Layer type 2 | +| AAL5 | ATM Adaptation Layer type 5 | +| AICH | Acquisition Indication Channel | +| ALCAP | Access Link Control Application Part | +| ATM | Asynchronous Transfer Mode | +| BCH | Broadcast Channel | +| BCCH | Broadcast Control Channel | +| CCH | Control Channel | +| CPCI | Common Physical Channel Identifier | +| CPICH | Common Pilot Channel | +| CTCI | Common Transport Channel Identifier | +| CRNC | Controlling Radio Network Controller | +| DCH | Dedicated Transport Channel | +| DPCCH | Dedicated Physical Control Channel | +| DPCH | Dedicated Physical Channel | +| DSCH | Down-link Shared Channel | +| E-DCH | Enhanced Dedicated Channel | +| FACH | Forward Access Channel | +| FAUSCH | Fast Up-link Signalling Channel | +| FDD | Frequency Division Duplex | +| F-DPCH | Fractional DPCH | +| HARQ | Hybrid Automatic Repeat Request | +| HS-DSCH | High Speed Downlink Shared Channel | +| IP | Internet Protocol | +| MICH | MBMS notification Indicator Channel | +| NBAP | Node B Application Part | +| O&M | Operation and Maintenance | +| PICH | Page Indication Channel | +| PCCH | Paging Control Channel | +| PCCPCH | Primary Common Control Physical Channel | +| PCPICH | Primary Common Pilot Channel | +| PCH | Paging Channel | +| PDSCH | Physical Downlink Shared Channel | +| PLCCH | Physical Layer Common Control Channel | +| PRACH | Physical Random Access Channel | +| PUSCH | Physical Uplink Shared Channel | +| RACH | Random Access Channel | +| RNC | Radio Network Controller | +| RNS | Radio Network Subsystem | +| SCH | Synchronization Channel | +| SCCPCH | Secondary Common Control Physical Channel | +| SCPICH | Secondary Common Pilot Channel | +| SCTP | Stream Control Transmission Protocol | +| SRNC | Serving Radio Network Controller | +| SSCF-UNI | Service Specific Co-ordination Function - User Network Interface | +| SSCOP | Service Specific Connection Oriented Protocol | +| TDD | Time Division Duplex | +| UE | User Equipment | +| UC-ID | UTRAN Cell Identifier | +| UDP | User Datagram Protocol | +| UMTS | Universal Mobile Telecommunication System | +| USCH | Up-link Shared Channel | +| UTRAN | UMTS Terrestrial Radio Access Network | + +## 3.3 Specification Notations + +For the purposes of the present document, the following notations apply: + +- [FDD] This tagging of a word indicates that the word preceding the tag "[FDD]" applies only to FDD. This tagging of a heading indicates that the heading preceding the tag "[FDD]" and the section following the heading applies only to FDD. +- [TDD] This tagging of a word indicates that the word preceding the tag "[TDD]" applies only to TDD, including 7.68 Mcps TDD, 3.84Mcps TDD and 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[TDD]" and the section following the heading applies only to TDD, including 7.68 Mcps TDD, 3.84Mcps TDD and 1.28Mcps TDD. +- [7.68Mcps TDD] This tagging of a word indicates that the word preceding the tag "[7.68Mcps TDD]" applies only to 7.68Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[7.68Mcps TDD]" and the section following the heading applies only to 7.68Mcps TDD. +- [3.84Mcps TDD] This tagging of a word indicates that the word preceding the tag "[3.84Mcps TDD]" applies only to 3.84Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[3.84Mcps TDD]" and the section following the heading applies only to 3.84Mcps TDD. +- [1.28Mcps TDD] This tagging of a word indicates that the word preceding the tag "[1.28Mcps TDD]" applies only to 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[1.28Mcps TDD]" and the section following the heading applies only to 1.28Mcps TDD. +- [FDD - ...] This tagging indicates that the enclosed text following the "[FDD - " applies only to FDD. Multiple sequential paragraphs applying only to FDD are enclosed separately to enable insertion of TDD specific (or common) paragraphs between the FDD specific paragraphs. +- [TDD - ...] This tagging indicates that the enclosed text following the "[TDD - " applies only to TDD, including 7.68 Mcps TDD, 3.84Mcps TDD and 1.28Mcps TDD. Multiple sequential paragraphs applying only to TDD are enclosed separately to enable insertion of FDD specific (or common) paragraphs between the TDD specific paragraphs. +- [7.68Mcps TDD - ...] This tagging indicates that the enclosed text following the "[7.68Mcps TDD - " applies only to 7.68Mcps TDD. Multiple sequential paragraphs applying only to 7.68Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 7.68Mcps TDD specific paragraphs. +- [3.84Mcps TDD - ...] This tagging indicates that the enclosed text following the "[3.84Mcps TDD - " applies only to 3.84Mcps TDD. Multiple sequential paragraphs applying only to 1.28Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 3.84Mcps TDD specific paragraphs. +- [1.28Mcps TDD - ...] This tagging indicates that the enclosed text following the "[1.28Mcps TDD - " applies only to 1.28Mcps TDD. Multiple sequential paragraphs applying only to 1.28Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 1.28Mcps TDD specific paragraphs. +- Procedure When referring to a procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. Radio Network Layer procedures. +- Message When referring to a message in the specification the MESSAGE NAME is written with all letters in upper case characters followed by the word "message", e.g. RADIO LINK SETUP REQUEST message. +- Frame When referring to a control or data frame in the specification the CONTROL/DATA FRAME NAME is written with all letters in upper case characters followed by the words "control/data frame", e.g. DCH transport frame. + +# --- 4 General Aspects + +## 4.1 Introduction + +The logical interface between a RNC and a Node B is called the Iub interface. + +## 4.2 Iub Interface General Principles + +The general principles for the specification of the Iub interface are as follows: + +- Transmission sharing between the GSM/GPRS Abis interface and the Iub interface shall not be precluded. +- The functional division between RNC and Node B shall have as few options as possible. +- Iub should be based on a logical model of Node B. +- Node B controls a number of cells and can be ordered to add/remove radio links in those cells. +- Neither the physical structure nor any internal protocols of the Node B shall be visible over Iub and are thus not limiting factors, e.g., when introducing future technology. +- Only the logical O&M (TS 25.401 [1]) of Node B is supported by the Iub. +- Complex functionality shall as far as possible be avoided over Iub. Advanced optimisation solutions may be added in later versions of the standard. +- The Iub functional split shall take into account the probability of frequent switching between different channel types. + +## 4.3 Iub Interface Specification Objectives + +The Iub interface specifications shall facilitate the following: + +- Inter-connection of RNCs and Node Bs from different manufacturers. +- Separation of Iub interface Radio Network functionality and Transport Network functionality to facilitate introduction of future technology. + +The Iub parts to be standardised are: + +1. User data transport. +2. Signalling for handling the user data. +3. Node B Logical O&M (TS 25.401 [1]). + +Note: It should be possible to transport the Implementation Specific O&M (TS 25.401 [1]) interface via the same transport bearer as the Iub interface and, hence, the lower layer transport mechanisms should be standardised to this effect. The application level content of the Implementation Specific O&M interface is out of scope of UTRAN standardization. Where the implementation specific O&M interface shares the same bearer as the Iub interface, the transport layers shall be as specified in TS 25.442 [2] and TS 25.432 [3] respectively. + +## 4.4 Iub Interface Capabilities + +### 4.4.1 Radio application related signalling + +The Iub interface allows the RNC and the Node B to negotiate about radio resources, for example to add and delete cells controlled by the Node B to support communication of the dedicated connection between UE and SRNC. Information used to control the broadcast channel and information to be transported on the broadcast channel belongs to this category also. In addition, logical O&M (TS 25.401 [1]) between the Node B and RNC shall also be included in this category. + +### 4.4.2 Iub/Iur DCH data stream + +The Iub interface provides the means for transport of uplink and downlink DCH transport frames between RNC and Node B. An Iub/Iur DCH data stream corresponds to the data carried on one DCH transport channel. + +In the UTRAN, one DCH data stream always corresponds to a bi-directional transport channel. Although the TFS is configured separately for each DCH direction and a DCH could be configured with e.g. only a zero-bit transport format in one direction, the DCH is always treated as a bi-directional transport channel in the UTRAN. As a result, two uni-directional Uu DCH transport channels with opposite directions can be mapped to either one or two DCH transport channels in the UTRAN. + +### 4.4.3 Iub RACH data stream + +The Iub interface provides the means for transport of uplink RACH transport frames between Node B and RNC. An Iub RACH data stream corresponds to the data carried on one RACH transport channel. + +### 4.4.4 Iub CPCH data stream [FDD] + +Void. + +### 4.4.5 Iub FACH data stream + +The Iub interface provides the means for transport of downlink FACH transport frames between RNC and Node B. An Iub FACH data stream corresponds to the data carried on one FACH transport channel. + +### 4.4.6 Iub DSCH data stream [TDD] + +The Iub interface provides the means for transport of downlink shared channel, DSCH, data frames between RNC and Node B. An Iub DSCH data stream corresponds to the data carried on one DSCH transport channel for one UE. A UE may have multiple DSCH data streams. + +### 4.4.7 Iub USCH data stream [TDD] + +The Iub interface provides the means for transport of uplink shared channel, USCH, data frames between Node B and RNC. An Iub USCH data stream corresponds to the data carried on one USCH transport channel for one UE. A UE may have multiple USCH data streams. + +### 4.4.8 Iub PCH data stream + +The Iub interface provides the means for transport of PCH transport frames between RNC and Node B. An Iub PCH data stream corresponds to the data carried on one PCH transport channel. + +### 4.4.9 Iub FDD TFCI2 data stream + +Void. + +### 4.4.10 Iub HS-DSCH data stream + +The Iub interface provides the means for transport of high speed downlink shared channel, HS-DSCH, data frames between RNC and Node B. An Iub HS-DSCH data stream corresponds to the data carried on one MAC-d flow for one UE. A UE may have multiple HS-DSCH data streams. + +### 4.4.11 Iub E-DCH data stream + +The Iub interface provides the means for transport of uplink E-DCH transport frames between Node B and RNC. An Iub E-DCH data stream corresponds to the data carried on one MAC-d flow for one UE. A UE may have multiple E-DCH data streams. + +In addition, the interface provides the following: + +- A means for the Node B to indicate the number of HARQ retransmissions to the SRNC (TS 25.427 [11]); +- A means to indicate to the SRNC, for the purposes of re-ordering, the CFN and Subframe Number that have been added by the Node B (TS 25.427 [11]). + +## 4.5 Iub Interface Characteristics + +### 4.5.1 Mapping of Iub data streams + +- DCH** One Iub DCH data stream is carried on one transport bearer. For each DCH data stream a transport bearer must be established over Iub, except in the case of coordinated DCHs in which case a set of coordinated DCHs are multiplexed onto the same transport bearer. +- RACH** One Iub RACH data stream is carried on one transport bearer. For each RACH in a cell, a transport bearer must be established over the Iub interface. +- FACH** One Iub FACH data stream is carried on one transport bearer. For each FACH in a cell, a transport bearer must be established over the Iub Interface, except in case of transport bearer sharing for MBMS, where only one transport bearer is established at the Iub interface for several FACHs belonging to different cells. +- [TDD - DSCH]** One Iub DSCH data stream is carried on one transport bearer. For each DSCH data stream, a transport bearer must be established over the Iub interface.] +- HS-DSCH** One Iub HS-DSCH data stream is carried on one transport bearer. For each HS-DSCH data stream, a transport bearer must be established over the Iub interface. +- E-DCH** One Iub E-DCH data stream is carried on one transport bearer. For each E-DCH data stream, a transport bearer must be established over the Iub interface.] +- [TDD - USCH]** One Iub USCH data stream is carried on one transport bearer. For each USCH data stream, a transport bearer must be established over the Iub interface.] +- PCH** One Iub PCH data stream is carried on one transport bearer. + +## 4.6 Iub Protocols + +There shall exist a clear separation between the radio network layer and the transport layer. Therefore, the radio network signalling and Iub data streams are separated from the data transport resource and traffic handling as shown in figure 1. This resource and traffic handling is controlled by the Transport Signalling. The Transport Signalling is carried by a Signalling Bearer over the Iub interface. + +![Diagram illustrating the separation of Radio Network protocols and transport over Iub. The diagram shows two layers: the Radio Network layer and the Transport layer. In the Radio Network layer, there are two components: 'Radio Signaling Protocol' and 'IubData Streams'. In the Transport layer, there are three components: 'Signalling Bearer', 'Transport Signalling', and 'Data Transport'. Arrows indicate the flow: 'Radio Signaling Protocol' points to 'Signalling Bearer', 'IubData Streams' points to 'Data Transport', and 'Transport Signalling' points to both 'Signalling Bearer' and 'Data Transport'.](7c6d9bfe9c31ce872722d60b73d20df1_img.jpg) + +``` + +graph TD + subgraph RNL [Radio Network layer] + RSP((Radio Signaling Protocol)) + IDS((IubData Streams)) + end + subgraph TL [Transport layer] + SB[Signalling Bearer] + TS[Transport Signalling] + DT[Data Transport] + end + RSP --> SB + IDS --> DT + TS -.-> SB + TS -.-> DT + +``` + +Diagram illustrating the separation of Radio Network protocols and transport over Iub. The diagram shows two layers: the Radio Network layer and the Transport layer. In the Radio Network layer, there are two components: 'Radio Signaling Protocol' and 'IubData Streams'. In the Transport layer, there are three components: 'Signalling Bearer', 'Transport Signalling', and 'Data Transport'. Arrows indicate the flow: 'Radio Signaling Protocol' points to 'Signalling Bearer', 'IubData Streams' points to 'Data Transport', and 'Transport Signalling' points to both 'Signalling Bearer' and 'Data Transport'. + +Figure 1: Separation of Radio Network protocols and transport over Iub + +# --- 5 Functions of the Iub Interface Protocols + +## 5.1 Iub Functions + +The list of functions on the Iub interface is the following: + +1. Management of Iub Transport Resources; +2. Logical O&M of Node B: + - Iub Link Management; + - Cell Configuration Management; + - Radio Network Performance Measurements; + - Resource Event Management; + - Common Transport Channel Management; + - Radio Resource Management; + - Radio Network Configuration Alignment; +3. Implementation Specific O&M Transport; +4. System Information Management; +5. Traffic Management of Common Channels: + - Admission Control; + - Power Management; + - Data Transfer; +6. Traffic Management of Dedicated Channels: + - Radio Link Management; + - Radio Link Supervision; + - Channel Allocation / De-allocation; + - Power Management; + - Measurement Reporting; + - Dedicated Transport Channel Management; + - Data Transfer; +7. Traffic Management of Shared Channels: + - Channel Allocation / De-allocation; + - Power Management; + - Transport Channel Management; + - Dynamic Physical Channel Assignment; + - Radio Link Management; + - Data Transfer; +8. Timing and Synchronization Management; + +- Transport Channel Synchronization (Frame synchronization); +- Node B - RNC node Synchronization; +- Inter Node B node Synchronization. + +## 5.2 Functional split over Iub + +### 5.2.1 Management of Iub Transport Resources + +The underlying transport resources (AAL2 and UDP/IP transport bearers) shall be set up and controlled by the RNC. Further information on these functions is provided in the transport layer specifications (TS 25.432 [3], TS 25.434 [8], TS 25.426 [10]). + +### 5.2.2 Logical O&M of Node B + +Logical O&M is the signalling associated with the control of logical resources (channels, cells,...) owned by the RNC but physically implemented in the Node B. The RNC controls these logical resources. A number of O&M procedures physically implemented in Node B impact on the logical resources and therefore require an information exchange between RNC and Node B. All messages needed to support this information exchange are classified as Logical O&M forming an integral part of NBAP over the Iub interface. + +#### 5.2.2.1 Handling of Node B Hardware Resources + +Mapping of Node B logical resources onto Node B hardware resources, used for Iub data streams and radio interface transmission/reception, is performed by Node B. + +### 5.2.3 Implementation Specific O&M Transport + +The Iub interface may support the transport of Implementation specific O&M information. Further detail on this can be found in the UMTS technical specification on Implementation Specific O&M Transport (TS 25.442 [2]). + +### 5.2.4 System Information Management + +System Information is sent by the CRNC to a Node B. CRNC can also request the Node B to autonomously create and update certain Node B related system information. Scheduling of system broadcast information is carried out in the CRNC. Scheduling information is always sent by the CRNC to the Node B. The Node B is responsible for transmitting the received system information according to the scheduling parameters provided. If requested by the CRNC, the Node B is also responsible for autonomously creating and updating the Node B related system information according to the scheduling parameters provided. + +### 5.2.5 Traffic management of Common Channels + +The common channels need to be controlled from the RNC. This is typically the control of the RACH and FACH channels, the information that is broadcast on the Broadcast control channel, and the control and request for sending information on the paging channels. + +### 5.2.6 Traffic management of Dedicated Channels + +These functions are related to the activation of logical resources (e.g. Radio Links, Iub ports), and the connection of these various resources together. + +[FDD - Some freedom may be left for Node B implementation on some functions like soft combining within Node B, since soft combining has merits for being executed as close as possible to the radio (both in terms of transmission cost and efficiency).] + +#### 5.2.6.1 Combining/Splitting and Control + +Node B may perform combining/splitting of DCH data streams communicated via its cells. RNC performs combining/splitting of Iub data streams received from/sent to several Node B(s). + +The UL combining of information streams may be performed using any suitable algorithm, for example: + +- [FDD - based on maximum ratio algorithm (maximum ratio combining)]; +- [FDD - based on quality information associated to each TBS (selection-combining)]; +- [TDD - based on the presence/absence of the signal (selection)]. + +When requesting the addition of a new cell for a UE-UTRAN connection, the RNC can explicitly request to the Node B a new Iub data stream, in which case the combining and splitting function within the Node B is not used for that cell. Otherwise, the Node B takes the decision whether combining and splitting function is used inside the Node B for that cell i.e. whether a new Iub data stream shall be added or not. + +The internal Node B handling of the combining/splitting of radio frames is controlled by the Node B. + +For E-DCH combining of UL streams in the Node B is mandatory as described in TS 25.319 [14]. + +#### 5.2.6.2 Handover Decision + +To support mobility of the UE to UTRAN connection between cells, UTRAN uses measurement reports from the UE and detectors at the cells. + +The RNC takes the decision to add or delete cells from the connection. + +#### 5.2.6.3 Allocation of Physical Channel Resources + +In FDD allocation of downlink channelisation codes of cells belonging to Node B is performed in the CRNC. + +In TDD allocation of uplink and downlink physical channel resources of cells belonging to Node B is performed in the CRNC. + +#### 5.2.6.4 UpLink Power Control + +This function controls the level of the transmitted power in order to minimise interference and keep the quality of the connections. The function uplink Outer Loop Power Control located in the SRNC sets the target quality for the uplink Inner Loop Power Control function, for E-DCH the Node B reports the number of HARQ retransmissions to the SRNC as an input to the Outer Loop Power Control function. In FDD and 1.28Mcps TDD, Inner Loop Power Control Function is located in Node B, while in 3.84Mcps TDD it is located in the UE. + +#### 5.2.6.5 Down-Link Power Control + +This function controls the level of the downlink transmitted power. In FDD it is also used to correct the downlink power drifting between several radio links. A SRNC regularly (or under some algorithms) shall send the target down link power range based on the measurement report from UE. + +#### 5.2.6.6 Admission Control + +The Admission Control function based on uplink interference and downlink power is located in the CRNC. + +Node B shall report uplink interference measurements and downlink power information over the Iub. + +The CRNC controls this reporting function, i.e. if this information needs to be reported and the period of these reports. + +#### 5.2.6.7 Power and Interference Reporting + +A threshold for reporting may be given to Node B from the CRNC to prevent frequent reporting over the Iub. Node B shall have a function to measure "uplink interference level and downlink TX Power" and a function to compare the averaged "uplink interference level and downlink TX power" with the threshold value. Node B shall also have a function to report when the average measured value exceeds the threshold value. The CRNC shall have a function to modify the "threshold value" for neighbour cell co-ordination. + +An indication of exceeding uplink interference threshold or downlink TX power may be included as a cause of failure when a Node B is requested to set-up a radio link or add to an existing radio link. This may be used when a number of radio links set-up requests or additions are received on the Iub during the reporting interval. + +### 5.2.7 Traffic management of Shared Channels [TDD] + +The shared channels shall be controlled from the RNC. This is typically the control of the TDD DSCH channels and the TDD USCH channels. + +### 5.2.7A Traffic management of High Speed Shared Channels + +The high speed shared channels shall be controlled from the Node B. This includes the control of the HS-DSCH channels as well as the required control channels on the radio interface. + +### 5.2.8 Timing and Synchronization Management + +The Iub interface shall support timing and synchronization management functions. Further detail regarding these functions can be found in the UMTS technical specification on UTRAN synchronization (TS 25.402 [12]). + +# 6 Node B logical Model over Iub + +## 6.1 Overview + +The model described in figure 2 shows the Node B as seen from the controlling RNC. The model includes: + +- The logical resources provided by Node B to UTRAN (via its Controlling RNC) - depicted as "cells" which include the physical channel resources DPCH, [FDD – F-DPCH] [TDD - PDSCH and PUSCH]; +- The dedicated channels which have been established on Node B; +- The common transport channels that Node B provides to the RNC. + +The procedures for controlling the connections between radio links and Iub DCH data ports are sent from the RNC to the Node B via the Communication Control Ports. + +![Figure 2: Logical Model of Node B. This diagram illustrates the logical architecture of a Node B as seen from the Controlling RNC. At the top, the 'Controlling RNC' is shown as a large rectangle. Below it, various data ports are represented by circles with labels: 'Node B Control Port', 'Iub RACH Data port', 'Iub FACH Data port', 'Iub PCH Data port', 'HS-DSCH Data port', 'Iub TDD DSCH Data port', 'Iub TDD USCH Data port', 'Iub DCH Data port', 'Iub E-DCH Data port', and 'Communication Control Port'. These ports are grouped into two dashed boxes labeled 'Traffic termination point'. Below these points, the 'Node B' is represented by a large rectangle containing two sub-sections: 'Common Transport Channels, with attributes' and 'Node B Communication Contexts, with attributes'. At the very bottom, a series of circles labeled 'Cell' represent the radio resources, connected to the communication contexts.](df0bcbfa8f8e1937e071445426c28022_img.jpg) + +Figure 2: Logical Model of Node B. This diagram illustrates the logical architecture of a Node B as seen from the Controlling RNC. At the top, the 'Controlling RNC' is shown as a large rectangle. Below it, various data ports are represented by circles with labels: 'Node B Control Port', 'Iub RACH Data port', 'Iub FACH Data port', 'Iub PCH Data port', 'HS-DSCH Data port', 'Iub TDD DSCH Data port', 'Iub TDD USCH Data port', 'Iub DCH Data port', 'Iub E-DCH Data port', and 'Communication Control Port'. These ports are grouped into two dashed boxes labeled 'Traffic termination point'. Below these points, the 'Node B' is represented by a large rectangle containing two sub-sections: 'Common Transport Channels, with attributes' and 'Node B Communication Contexts, with attributes'. At the very bottom, a series of circles labeled 'Cell' represent the radio resources, connected to the communication contexts. + +Figure 2: Logical Model of Node B + +## 6.2 Elements of the logical model + +### 6.2.1 Node B Communication Contexts for Dedicated and Shared Channels + +A Node B Communication Context corresponds to all the dedicated resources that are necessary for a user in dedicated mode and using dedicated and/or shared channels as restricted to a given Node B. [TDD - The Node B Communication Context also exists for users in Cell\_FACH mode (i.e. non-dedicated mode) provided a USCH and/or DSCH and/or HS-DSCH has been allocated to these users.] + +There are a number of Node B Communication Contexts inside a given Node B. + +The attributes to a Node B Communication Context shall include the following (not exhaustive): + +- The list of Cells where dedicated and/or shared physical resources are used. +- The list of DCH which are mapped on the dedicated physical resources for that Node B Communication Context. +- [TDD - The list of DSCH and USCH which are used by the respective UE.] +- The list of HS-DSCH MAC-d flows which are used by the respective UE. +- The list of E-DCH MAC-d flows which are used by the respective UE.] +- The complete DCH characteristics for each DCH, identified by its DCH-identifier (TS 25.302 [4]). +- [TDD - The complete Transport Channel characteristics for each DSCH and USCH, identified by its Shared Channel identifier (TS 25.302 [4]).] +- The complete HS-DSCH characteristics for each HS-DSCH MAC-d Flow, identified by its HS-DSCH MAC-d Flow identifier (TS 25.302 [4]). +- The complete E-DCH characteristics for each E-DCH MAC-d Flow, identified by its E-DCH MAC-d Flow identifier (TS 25.302 [4]).] +- The list of Iub DCH Data Ports. +- [TDD - The list of Iub DSCH Data ports and Iub USCH data ports.] +- The list of Iub HS-DSCH Data ports. +- The list of Iub E-DCH Data ports.] +- For each Iub DCH Data Port, the corresponding DCH and cells which are carried on this data port. +- [TDD - For each Iub DSCH and USCH data port, the corresponding DSCH or USCH and cell which serves that DSCH or USCH.] +- For each Iub HS-DSCH data port, the corresponding HS-DSCH data stream and cell which serves that HS-DSCH data stream. +- Physical layer parameters (outer loop power control, etc). + +### 6.2.2 Common Transport Channels + +Common Transport Channels are defined in TS 25.435 [9]. A Common Transport Channel is configured in the Node B, on request of the CRNC. + +The BCH is carried directly on the Node B control port using NBAP procedures. This Common Channel will not be mapped to an individual data port. + +The RACH has an associated Iub RACH Data Port and the FACH has an associated Iub FACH Data Port. + +[TDD - The Iub DSCH data port is associated to one DSCH and to one Node B Communication Context.] + +[TDD - the Iub USCH data port is associated to one USCH and to one Node B Communication Context.] + +The attributes of a Common transport channel shall include (not exhaustive): + +- Type (RACH, FACH, DSCH [TDD], USCH [TDD], PCH). +- Associated Iub RACH Data Port for a RACH, Iub FACH Data Port for a FACH, Iub PCH Data Port for the PCH. +- Physical parameters. + +[TDD - The DSCHs used by one UE are multiplexed to one or several CCTrCHs where each CCTrCH is mapped to a set of PDSCH ("PDSCH Set"). These PDSCH Sets are included in the Common Transport Channel data base. The same applies for the USCHs and the corresponding PUSCH Sets.] + +### 6.2.3 Transport network logical resources + +#### 6.2.3.1 Node B Control Port + +The Node B Control Port is used to exchange the signalling information for the logical O&M of Node B, the creation of Node B Communication Contexts, the configuration of the common transport channels that Node B provides in a given cell, PCH and BCH control information between the RNC and the Node B. The Node B Control Port corresponds to one signalling bearer between the controlling RNC and the Node B. There is one Node B Control Port per Node B. + +#### 6.2.3.2 Communication Control Port + +A Communication Control Port corresponds to one signalling bearer between the RNC and Node B for the control of Node B Communication Contexts. One signalling bearer between RNC and Node B can at most correspond to one Communication Control Port. Node B may have multiple Communication Control Ports (one per Traffic Termination Point). The Communication Control Port is selected at creation of the Node B Communication Context. The Communication Control Port is re-selected when the signalling bearer for the control of Node B Communication is rearranged. + +#### 6.2.3.3 Traffic Termination Point + +Traffic Termination Point represents DCH, DSCH [TDD], USCH [TDD], HS-DSCH and E-DCH data streams belonging to one or more Node B Communication Contexts (UE contexts), which are controlled via one Communication Control Port. The Traffic Termination Point is thus a descriptive entity which neither is controlled over Iub nor by O&M. + +#### 6.2.3.4 Iub DCH Data Port + +One Iub DCH Data port represents one user plane transport bearer. One user plane transport bearer will carry only one DCH data stream except in the case of coordinated DCHs, in which case the data streams of all combined DCHs shall be multiplexed on one and the same user plane transport bearer. + +#### 6.2.3.5 Iub RACH Data Port + +An Iub RACH Data Port represents a user plane bearer carrying one Iub RACH Data Stream between the Node B and the RNC. There is one RACH Data Port for each RACH channel of Node B. + +#### 6.2.3.6 Iub CPCH Data Port [FDD] + +Void. + +#### 6.2.3.7 Iub FACH Data Port + +An Iub FACH Data Port represents a user plane bearer carrying one Iub FACH Data Stream between the Node B and the RNC. There is one FACH Data Port for each FACH channel of Node B. + +#### 6.2.3.8 Iub DSCH Data Port [TDD] + +An Iub DSCH Data Port represents a user plane bearer carrying one Iub DSCH Data Stream between the Node B and the RNC. For each DSCH, that is used by an individual UE, there is one Iub DSCH Data Port per Node B exclusively assigned to the communication context of that UE. + +#### 6.2.3.8A Iub HS-DSCH Data Port + +An Iub HS-DSCH Data Port represents a user plane bearer carrying one Iub HS-DSCH Data Streams between the Node B and the RNC. + +#### 6.2.3.9 Iub USCH Data Port [TDD] + +An Iub USCH Data Port represents a user plane bearer carrying one Iub USCH Data Stream between the Node B and the RNC. For each USCH, that is used by an individual UE, there is one Iub USCH Data Port with data exclusively assigned to the Node B communication context of that UE. + +#### 6.2.3.10 Iub PCH Data Port + +An Iub PCH Data Port represents an Iub PCH Data Stream between the Node B and the RNC. + +#### 6.2.3.11 Iub FDD TFCl2 Data Port + +Void. + +#### 6.2.3.12 Iub E-DCH Data Port + +An Iub E-DCH Data Port represents a user plane bearer carrying one Iub E-DCH Data Stream between the Node B and the RNC. + +### 6.2.4 Radio Network Logical resources + +#### 6.2.4.1 Common Resources + +The CRNC manages logical radio network resources in Node B and needs to use both common and dedicated resources in a Node B to run a radio network. Therefore, it is the CRNC that orders the Node B to configure, reconfigure and delete these resources. However, if the equipment in Node B cannot fully support the configuration that the CRNC requests, or the equipment breaks down, then Node B can indicate the availability of the common resources (i.e. both downgrade and upgrade). + +The common resources are the Cell, the common physical channels and the common transport channels. + +In Node B these common resources have an operational state, that indicates whether they are operational or not, i.e. whether they can carry traffic or not. + +Figure 3 shows the common resources that a CRNC is managing in a Node B to be able to run a radio network. + +![Figure 3: Common resources in a Node B that are managed by the CRNC. This hierarchical diagram shows the relationship between a Cell and various physical and transport channels. The Cell (Cell-Id) is the root, connected to PCCPCH (1), PICH (0-i), MICH (0-1), SCCPCH (0-i), PRACH (0-k), and AICH (0-k). PCCPCH is connected to BCH (1). SCCPCH is connected to PCH (0-1), FACH (0-n), and RACH (1). PRACH is connected to RACH (1). AICH is connected to RACH (1). PICH is connected to PCH (1). MICH is connected to PCH (1). The diagram also shows FDD-only and TDD-only channel groups. FDD-only includes PCPICH (1), SCPICH (0-m), SCH1 (1), and SCH2 (1). TDD-only includes E-RUCCH (0-t) and SCH (1). A separate group for 1.28Mcps TDD includes UpPCH (1), DwPCH (1), FPACH (0-r), and PLCCH (0-s).](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +``` + +graph TD + Cell["Cell +Cell-Id"] -- 1 --> PCCPCH["PCCPCH +CPCId"] + Cell -- 1 --> PICH["PICH +CPCId"] + Cell -- 0-i --> MICH["MICH +CPCId"] + Cell -- 0-i --> SCCPCH["SCCPCH +CPCId"] + Cell -- 0-k --> PRACH["PRACH +CPCId"] + Cell -- 0-k --> AICH["AICH +CPCId"] + + PCCPCH -- 1 --> BCH["BCH +CTCId"] + PICH -- 1 --> PCH["PCH +CTCId"] + MICH -- 1 --> PCH + SCCPCH -- 0-1 --> PCH + SCCPCH -- 0-n --> FACH["FACH +CTCId"] + SCCPCH -- 1 --> RACH["RACH +CTCId"] + PRACH -- 1 --> RACH + AICH -- 1 --> RACH + + subgraph FDD_Only [FDD Only] + PCPICH["PCPICH +CPCId"] + SCPICH["SCPICH +CPCId"] + SCH1["SCH1 +CPCId"] + SCH2["SCH2 +CPCId"] + end + Cell --- FDD_Only + + subgraph TDD_Only [3.84 Mcps TDD , 7.68 Mcps TDD Only] + E_RUCCH["E-RUCCH +CPCId"] + SCH_T["SCH +CPCId"] + end + Cell --- TDD_Only + + subgraph TDD_Only_1_28 [1.28McpsTDD Only] + UpPCH["UpPCH"] + DwPCH["DwPCH +CPCId"] + FPACH["FPACH +CPCId"] + PLCCH["PLCCH +CPCId"] + end + Cell --- TDD_Only_1_28 + +``` + +Figure 3: Common resources in a Node B that are managed by the CRNC. This hierarchical diagram shows the relationship between a Cell and various physical and transport channels. The Cell (Cell-Id) is the root, connected to PCCPCH (1), PICH (0-i), MICH (0-1), SCCPCH (0-i), PRACH (0-k), and AICH (0-k). PCCPCH is connected to BCH (1). SCCPCH is connected to PCH (0-1), FACH (0-n), and RACH (1). PRACH is connected to RACH (1). AICH is connected to RACH (1). PICH is connected to PCH (1). MICH is connected to PCH (1). The diagram also shows FDD-only and TDD-only channel groups. FDD-only includes PCPICH (1), SCPICH (0-m), SCH1 (1), and SCH2 (1). TDD-only includes E-RUCCH (0-t) and SCH (1). A separate group for 1.28Mcps TDD includes UpPCH (1), DwPCH (1), FPACH (0-r), and PLCCH (0-s). + +The number or range above each box indicates how many of the channels named in that box can exist as "children" under one instant of a "parent" box to which the "child" box is connected. + +The number or range beneath each box indicates how many of the channels named in that box can exist as "parent" boxes for one instant of a "child" channel to which the "parent" box is connected. + +*CPCId* = Common Physical Channel Identifier + +*CTCId* = Common Transport Channel Identifier + +[TDD - The number of PICH = the number of PCH] + +[FDD - The number of AICH = the number of PRACH] + +[TDD – PCH and FACHs can be mapped on one or more SCCPCH] + +**Figure 3: Common resources in a Node B that are managed by the CRNC** + +#### 6.2.4.2 Cell + +A Cell is identified by a UTRAN Cell identifier (UC-id) (TS 25.401 [1]). + +The semantics of a Cell include the following: + +- The Cell can be created and removed by administrative procedures. When a Local Cell, i.e. equipment in a Node B, is made available to the CRNC for configuration of a cell, the CRNC can configure the cell with configuration data, common physical channels and common transport channels in Node B. In so doing a Local cell is added to the RNS. +- If any Iub transport bearers for common or dedicated transport channels exist when the cell is deleted, the Node B shall initiate the release of those transport bearers. +- Node B may support one or more cells. [1.28Mcps TDD - A cell may support one or more frequencies. If multiple frequencies are configured in one cell, the cell is called the multi-frequency cell.] +- Configuration of a cell over the Iub interface cannot be successful unless Node B has reported a Local Cell Id (TS 25.401 [1]) as available to the CRNC. +- Once a Local Cell is configured to support a cell, it cannot be deleted without the CRNC first deleting the cell. + +Figure 4 illustrates the state diagram for a Local Cell in Node B, as seen over the Iub interface. + +![State diagram for a Local Cell with two states: 'Not existing' and 'Existing'.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +``` + +stateDiagram-v2 + direction TB + [*] --> Not_existing + Not_existing --> Existing: Local Cell defined and taken into service\nResource Status Indication\nAdd/Delete Indicator=Add + Existing --> Not_existing: Local Cell withdrawn\nResource Status Indication:\nAdd/Delete Indicator=Delete + +``` + +**Bold** represents the trigger +*Italics* represent the action + +State diagram for a Local Cell with two states: 'Not existing' and 'Existing'. + +Figure 4: States for a Local Cell that are seen over the Iub interface + +Cells in Node B have a resource operational state. + +Figure 5 illustrates the state diagram for the states of a cell, as seen over the Iub interface. + +![State diagram for a cell in Node B with three states: 'Not existing', 'Enabled', and 'Disabled'.](e636d7ccca0ad14c6b95201404324823_img.jpg) + +``` + +stateDiagram-v2 + direction TB + [*] --> Not_existing + Not_existing --> Enabled: Cell is created\nCell Setup Request + Enabled --> Not_existing: Cell is deleted\nCell Delete Request + Enabled --> Disabled: Total resource capability reduction\nResource Status Indication:\nOp.State=Disabled + Disabled --> Enabled: Resource capability increase\nResource Status Indication:\nOp.State=Enable + Disabled --> Not_existing: Cell is deleted\nCell Delete Request + +``` + +**Bold** represents the trigger +*Italics* represent the action + +State diagram for a cell in Node B with three states: 'Not existing', 'Enabled', and 'Disabled'. + +Figure 5: States for a cell in Node B, as reported to the CRNC + +There are three states seen over the Iub interface: + +1. Not existing, meaning that the cell does not exist in Node B. +2. Enabled, meaning that the resource can be used by the RNC. +3. Disabled, meaning that the resource cannot be used by the RNC. + +When a cell becomes disabled in Node B, that shall be reported to the CRNC together with the cause. + +#### 6.2.4.3 Common Physical Channels and Common Transport Channels + +Common physical channels and common transport channels in Node B have a resource operational state. + +Figure 6 illustrates the state diagram for common physical channels and common transport channels in Node B, as seen over the Iub interface. + +![State diagram for a common channel in Node B showing three states: Not Existing, Enabled, and Disabled, with transitions between them based on specific triggers and actions.](608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Not_Existing : Channel is created + Not_Existing --> Enabled : Channel is deleted + Enabled --> Not_Existing : Channel is deleted + Enabled --> Disabled : Total resource capability reduction + Disabled --> Enabled : Resource capability increase + Disabled --> Not_Existing : Channel is deleted + +``` + +The diagram illustrates the states and transitions for a common channel in Node B. It consists of three states: Not Existing, Enabled, and Disabled. Transitions are triggered by specific events and result in specific actions. + +- Not Existing to Enabled:** Triggered by "Channel is created" (Action: *Cell Setup Request or Common Transport Channel Setup Request*). +- Enabled to Not Existing:** Triggered by "Channel is deleted" (Action: *Cell Delete Request or Common Transport Channel Delete Request*). +- Enabled to Disabled:** Triggered by "Total resource capability reduction" (Action: *Resource Status Indication: Op.State=Disabled*). +- Disabled to Enabled:** Triggered by "Resource capability increase" (Action: *Resource Status Indication: Op.State=Enable*). +- Disabled to Not Existing:** Triggered by "Channel is deleted" (Action: *Cell Delete Request or Common Transport Channel Delete Request*). + +**Bold represents the trigger** +*Italics represent the action* + +State diagram for a common channel in Node B showing three states: Not Existing, Enabled, and Disabled, with transitions between them based on specific triggers and actions. + +**Figure 6: States for a common channel in Node B, as reported to the CRNC** + +There are three states seen over the Iub interface: + +1. Not existing, meaning that the resource does not exist in Node B; +2. Enabled, meaning that the resource can be used by the RNC; +3. Disabled, meaning that the resource cannot be used by the RNC. + +When a channel becomes disabled in the Node B, this shall be reported to the CRNC together with the cause. + +#### 6.2.4.4 Physical Shared Channels + +Physical Shared Channels includes [TDD - the Physical Downlink Shared Channels (PDSCH), the Physical Uplink Shared Channels (PUSCH) and] the High Speed Physical Shared Channels (HS-PDSCH). [TDD - These PDSCH and PUSCH [TDD] are special cases of the Common Physical Channels]. + +[FDD - A HS-PDSCH is defined by a channelisation code within a code subtree that is configured within a specific Communication Context. The HS-PDSCH is activated dynamically as part of the HS-DSCH scheduling.] + +[TDD - A PDSCH is defined by a channelisation code, a time slot and other Physical Channel parameters. Several PDSCH may be grouped into a PDSCH Set, which is given a "PDSCH Set Id". The PDSCH Sets are configured in the Node B in the "Common Transport Channel" data base by Common NBAP messages. These PDSCH Sets are available to carry DSCH data. The PDSCH Sets are dynamically activated to carry DSCH data, as part of the DSCH scheduling.] + +[TDD - A HS-PDSCH is defined by a channelisation code, a time slot and other Physical Channel parameters. The HS-PDSCH is activated dynamically as part of the HS-DSCH scheduling.] + +[TDD - A PUSCH is defined by a channelisation code, a time slot and other Physical Channel parameters. Several PUSCH may be grouped into a PUSCH Set, which is given a "PUSCH Set Id". The PUSCH Sets are configured in the Node B in the "Common Transport Channel" data base by Common NBAP messages. These PUSCH Sets are available to carry USCH data. The PUSCH Sets are dynamically activated to carry USCH data, as part of the USCH scheduling.] + +# 7 Iub Interface Protocol Structure + +![Figure 7: Iub Interface Protocol Structure. A diagram showing the protocol stack for the Iub interface, divided into three vertical planes: Radio Network Control Plane, Transport Network Control Plane, and User Plane. The stack is organized into layers: Radio Network Layer (top), Transport Layer (middle), and Physical Layer (bottom).](b2ea162a0f53d5e0504b7d28346e0754_img.jpg) + +The diagram illustrates the Iub Interface Protocol Structure across three vertical planes: Radio Network Control Plane, Transport Network Control Plane, and User Plane. The stack is organized into layers: Radio Network Layer (top), Transport Layer (middle), and Physical Layer (bottom). + +- Radio Network Layer:** + - Radio Network Control Plane:** Contains the Node B Application Part (NBAP). + - Transport Network Control Plane:** Contains ALCAP (Q.2630.2) and Q.2150.2. + - User Plane:** Contains DCH FP, RACH FP, FACH FP, PCH FP, HS-DSCH FP, TDD DSCH FP, USCH FP, TFNC2 FP, and F-DCH FP. +- Transport Layer:** + - Radio Network Control Plane:** Contains SSCF-UNI, SSCOP, SCTP, AAL5, IP, ATM, and Data Link Layer. + - Transport Network Control Plane:** Contains ALCAP (Q.2630.2), Q.2150.2, SSCF-UNI, SSCOP, AAL 5, and ATM. + - User Plane:** Contains UDP, AAL2, IP, ATM, and Data Link Layer. +- Physical Layer:** Shared across all three planes. + +Figure 7: Iub Interface Protocol Structure. A diagram showing the protocol stack for the Iub interface, divided into three vertical planes: Radio Network Control Plane, Transport Network Control Plane, and User Plane. The stack is organized into layers: Radio Network Layer (top), Transport Layer (middle), and Physical Layer (bottom). + +Figure 7: Iub Interface Protocol Structure. + +The Iub interface protocol architecture consists of two functional layers: + +1. Radio Network Layer, defines procedures related to the operation of Node B. The radio network layer consists of a radio network control plane and a radio network user plane. +2. Transport Layer, defines procedures for establishing physical connections between Node B and the RNC with AAL type 2 Signalling Protocol (Capability Set 2) (ITU-T Rec. Q.2630.2 [13]). + +There shall be one dedicated AAL2 or UDP/IP transport bearer for each RACH, and one for each FACH transport channel or for each set of FACH transport channels in case of transport bearer sharing (see section 4.5.1). + +# --- 8 Other Iub Interface Specifications + +## 8.1 UTRAN Iub Interface: Layer 1 (TSG RAN 25.431) + +This document (TS 25.431 [5]) specifies the standards allowed for the implement of Layer 1 (physical layer) on the Iub interface. + +## 8.2 UTRAN Iub Interface: Signalling Transport (TSG RAN 25.432) + +This document (TS 25.432 [3]) specifies the signalling transport related to NBAP signalling to be used across the Iub Interface. + +## 8.3 NBAP Specification (TSG RAN 25.433) + +This document (TS 25.433 [7]) specifies the standards for NBAP specification to be used over Iub Interface. + +## 8.4 UTRAN Iub Interface: Data Transport & Transport Signalling for Common Transport Channel Data Streams (TSG RAN 25.434) + +This document (TS 25.434 [8]) provides a specification of the UTRAN RNC-Node B (Iub) interface Data Transport and Transport Signalling for Common Transport Channel data streams. + +## 8.5 UTRAN Iub Interface: User Plane Protocols for Common Transport Channel Data Streams (TSG RAN 25.435) + +This document (TS 25.435 [9]) provides a specification of the UTRAN RNC-Node B (Iub) interface user plane protocols for Common Transport Channel data streams. + +## 8.6 UTRAN Iur/Iub Interface: Data Transport & Transport Signalling for DCH Data Streams (TSG RAN 25.426) + +This Technical Specification (TS 25.426 [10]) specifies the transport bearers for the DCH data streams on UTRAN Iur and Iub interfaces. The corresponding Transport Network Control plane is also specified. + +## 8.7 UTRAN Iur/Iub Interface: User Plane Protocol for DCH Data Streams (TSG RAN 25.427) + +This document (TS 25.427 [11]) provides a specification of the UTRAN Iur and Iub interfaces user plane protocols for Dedicated Transport Channel data streams. + +## 8.8 Summary of UTRAN Iub Interface Technical Specifications + +The relationship between the technical specifications that define the UTRAN Iub interface is shown in figure 8. + +![Diagram showing the relationship between technical specifications for the UTRAN Iub interface across different layers and planes.](7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg) + +The diagram illustrates the technical specifications for the UTRAN Iub interface, organized into three vertical columns representing different planes and two horizontal rows representing layers. + +- Columns:** + - Radio Network Control Plane:** The leftmost column. + - Transport Network Control Plane:** The middle column. + - User Plane:** The rightmost column, which is further divided into **Dedicated Channels** and **Common Channels**. +- Rows:** + - Radio Network Layer:** The top row. It contains: + - Radio Network Control Plane:** NBAP (TS 25.433). + - User Plane:** Dedicated Channels (TS 25.427) and Common Channels (TS 25.435). + - Transport Layer:** The bottom row. It contains: + - Radio Network Control Plane:** NBAP Transport (TS 25.432). + - Transport Network Control Plane:** Transport Signaling (TS 25.426 for Dedicated Channel Transport, TS 25.434 for Common Channel Transport). + - User Plane:** Dedicated Channel Transport (TS 25.426) and Common Channel Transport (TS 25.434). +- Physical Layer:** A single row at the bottom spanning all columns, labeled "Physical Layer TS 25.431". + +Diagram showing the relationship between technical specifications for the UTRAN Iub interface across different layers and planes. + +Figure 8: Iub Interface Technical Specifications. + +# Annex A (informative): Change history + +| Date / TSG | TSG Doc. | CR | Rev | Subject/Comment | New | +|------------|-----------|------|-----|------------------------------------------------------------|--------| +| 12/2008 | - | - | - | Creation of Rel-8 version based on v7.5.0 | 8.0.0 | +| 12/2009 | - | - | - | Creation of Rel-9 version based on v8.0.0 | 9.0.0 | +| SP-49 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 9.0.1 | +| 03/2011 | | | | Creation of Rel-10 version based on v9.0.1 | 10.0.0 | +| 52 | RP-110685 | 0074 | 1 | Correction to the References | 10.1.0 | +| 09/2012 | | | | Update to Rel-11 version (MCC) | 11.0.0 | +| 09/2014 | | | | Update to Rel-12 version (MCC) | 12.0.0 | +| 12/2015 | | | | Update to Rel-13 version (MCC) | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-07 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25431/raw.md b/marked/Rel-16/25_series/25431/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..eb6d76120176fa646abab06e38789d676c033bb0 --- /dev/null +++ b/marked/Rel-16/25_series/25431/raw.md @@ -0,0 +1,83 @@ + + + + + + +# --- Contents + +| | | +|--------------------------------------------|---| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 4 Iub Layer 1 ..... | 5 | +| Annex A (informative): Change history..... | 6 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the standards allowed to implement Layer 1 on the Iub interface. + +The specification of transmission delay requirements and O&M requirements is not in the scope of this document. + +In the following 'Layer 1' and 'Physical Layer' are assumed to be synonymous. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +[1] 3GPP TS 25.411: "UTRAN Iu interface Layer 1". + +[2] ATM Forum AF-PHY-0130.00 (1999-10): "ATM on Fractional E1/T1". + +# --- 3 Definitions and abbreviations + +For the purposes of the present document, the terms and definitions given in 3GPP TS 25.411 [1] apply. + +# --- 4 Iub Layer 1 + +The Iub Layer 1 shall comply with the requirements of chapter 4 in TS 25.411 [1]. + +In addition, for the Iub Layer 1, it shall be possible to use n 64 kbit/s time slots within the scope of "ATM on Fractional E1/T1" as specified in ATM Forum AF-PHY-0130.00 [2], and to allow the co-existence of this interface with other interfaces on the same physical medium. + +# Annex A (informative): Change history + +| Date / TSG | TSG Doc. | CR | Rev | Subject/Comment | New | +|------------|-----------|------|-----|------------------------------------------------------------|--------| +| 12/2008 | - | - | - | Creation of Rel-8 version based on v7.0.0 | 8.0.0 | +| 12/2009 | - | - | - | Creation of Rel-9 version based on v8.0.0 | 9.0.0 | +| SP-49 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 9.0.1 | +| 03/2011 | | | | Creation of Rel-10 version based on v9.0.1 | 10.0.0 | +| 52 | RP-110684 | 0003 | - | Correction of references | 10.1.0 | +| 09/2012 | | | | Update to Rel-11 version (MCC) | 11.0.0 | +| 09/2014 | | | | Update to Rel-12 version (MCC) | 12.0.0 | +| 12/2015 | | | | Update to Rel-13 version (MCC) | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-07 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25446/06da11ab76cacc38bbcd714e437797ea_img.jpg b/marked/Rel-16/25_series/25446/06da11ab76cacc38bbcd714e437797ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bad2686aac96bfa07308c1ae617428ef57377fe5 --- /dev/null +++ b/marked/Rel-16/25_series/25446/06da11ab76cacc38bbcd714e437797ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:005af973050ae7c722360687963684bb1d2701d2348001b07f16db82cb6d2864 +size 50354 diff --git a/marked/Rel-16/25_series/25446/1c94fd3cebf58af136144f14160d128e_img.jpg b/marked/Rel-16/25_series/25446/1c94fd3cebf58af136144f14160d128e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b39a2ef003fc4f6eb752ef605cc8d22008fe647c --- /dev/null +++ b/marked/Rel-16/25_series/25446/1c94fd3cebf58af136144f14160d128e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6b86a28a3409291823085fcbb10f5d6ce63f5a6f4fe2d5c774c45b54a0bc00c +size 51633 diff --git a/marked/Rel-16/25_series/25446/5e92d9e8e9ce204e405bff2367f88176_img.jpg b/marked/Rel-16/25_series/25446/5e92d9e8e9ce204e405bff2367f88176_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56915b35ff7c1da6176eb9057e8ae71536b63ce9 --- /dev/null +++ b/marked/Rel-16/25_series/25446/5e92d9e8e9ce204e405bff2367f88176_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5d04a24377b2330c6e18bf7ae3f78a9f8b91de998a65a2750dfaf193c8e5200 +size 13846 diff --git a/marked/Rel-16/25_series/25446/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/marked/Rel-16/25_series/25446/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3daee308e36e2b43a705de43a6167bdd534a44b --- /dev/null +++ b/marked/Rel-16/25_series/25446/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bfc5b164381be8aa810c02ca74c6f333ed6ce41e30bdabe571956bdb139d68fb +size 14999 diff --git a/marked/Rel-16/25_series/25446/raw.md b/marked/Rel-16/25_series/25446/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6c91f8be2b3c1cb794492d4f2c8af96a1cd4e40d --- /dev/null +++ b/marked/Rel-16/25_series/25446/raw.md @@ -0,0 +1,669 @@ + + + + + + +# Contents + +| | | +|-----------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 6 | +| 3.4 Specification notations ..... | 7 | +| 4 General..... | 7 | +| 4.1 General aspects for the SYNC protocol for UTRAN..... | 7 | +| 4.1.1 General aspects..... | 7 | +| 4.2 General aspects for the SYNC protocol for E-UTRAN..... | 8 | +| 4.2.1 General aspects..... | 8 | +| 5 SYNC protocol version 1 ..... | 9 | +| 5.1 General ..... | 9 | +| 5.1.1 Applicability of SYNC protocol version 1 ..... | 9 | +| 5.1.1 Operation of the SYNC protocol..... | 9 | +| 5.1.2 Interfaces of the SYNC protocol layer ..... | 9 | +| 5.2 SYNC protocol layer services..... | 9 | +| 5.3 Services Expected from the UP Data Transport layer..... | 9 | +| 5.4 Elementary procedures..... | 10 | +| 5.4.1 Transfer of User Data for MBMS procedure..... | 10 | +| 5.4.1.1 Successful operation ..... | 10 | +| 5.4.1.2 Unsuccessful operation ..... | 10 | +| 5.4.2 Transfer of Synchronisation Information for MBMS procedure (without user data) ..... | 11 | +| 5.4.2.1 Successful operation ..... | 11 | +| 5.4.2.2 Unsuccessful operation..... | 11 | +| 5.5 Elements for the SYNC protocol ..... | 12 | +| 5.5.1 General ..... | 12 | +| 5.5.2 Frame format for the SYNC protocol..... | 12 | +| 5.5.2.1 Transfer of Synchronisation Information without payload (SYNC PDU Type 0) ..... | 12 | +| 5.5.2.2 Transfer of User Data for MBMS with uncompressed header (SYNC PDU Type 1)..... | 13 | +| 5.5.2.3 Transfer of User Data for MBMS with compressed header (SYNC PDU Type 2)..... | 14 | +| 5.5.2.4 Transfer of Synchronisation Information with Length of Packets (SYNC PDU Type 3)..... | 15 | +| 5.5.3 Coding of information elements in frames ..... | 17 | +| 5.5.3.1 PDU Type ..... | 17 | +| 5.5.3.2 Timestamp ..... | 18 | +| 5.5.3.3 Packet Number..... | 18 | +| 5.5.3.4 Elapsed Octet Counter ..... | 18 | +| 5.5.3.5 Total Number Of Packet ..... | 18 | +| 5.5.3.6 Total Number Of Octet..... | 18 | +| 5.5.3.7 PDCP Information ..... | 19 | +| 5.5.3.8 IPv6 Indicator ..... | 19 | +| 5.5.3.9 Uncompressed Payload IP header..... | 19 | +| 5.5.3.10 Header CRC..... | 19 | +| 5.5.3.11 Payload CRC..... | 19 | +| 5.5.3.12 Padding ..... | 19 | +| 5.5.3.13 Spare ..... | 19 | +| 5.5.3.14 Spare extension..... | 20 | +| 5.5.3.15 Payload fields..... | 20 | +| 5.5.3.16 Length of the N th Packet..... | 20 | +| 5.5.4 Timers..... | 20 | +| 5.6 Handling of unknown, unforeseen and erroneous protocol data..... | 20 | +| 5.6.1 General ..... | 20 | +| 5.6.2 CRC Calculation..... | 20 | +| 5.6.3 Relation between input and output of the Cyclic Redundancy Check ..... | 21 | + +Annex A (informative): Change history................................................................................................ 22 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the MBMS Synchronisation Protocol. For the release of this specification it is used on Iu towards UTRAN and M1 towards E-UTRAN. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 25.410: "UTRAN Iu interface: General Aspects and Principles". +- [3] 3GPP TS 25.323: "Packet Data Convergence Protocol (PDCP) specification". +- [4] 3GPP TS 25.346: "Introduction of the Multimedia Broadcast Multicast Service (MBMS) in the Radio Access Network (RAN); Stage 2". +- [5] 3GPP TS 36.440: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); General aspects and principles for interfaces supporting Multimedia Broadcast Multicast Service (MBMS) within E-UTRAN". +- [6] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**RAN Access interface:** interface between the Core Network and the Radio Access Network. + +**RAN Access node:** termination point of the RAN Access interface at the Radio Access Network. + +**MBMS RAB:** denotes the Radio Access data bearer together with the RAN Access Interface data bearer for MBMS service user data transmission. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|--------|-------------------------------------------------| +| MRNC | MBMS Master RNC (as specified in TS 25.346 [4]) | +| SC-PTM | Single Cell – Point To Multipoint | +| SYNC | MBMS synchronisation protocol | + +## 3.4 Specification notations + +For the purposes of the present document, the following notations apply: + +| | | +|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Procedure | When referring to a procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. Iu Rate Control procedure. | +| Frame | When referring to a control or data frame in the specification, the CONTROL/DATA FRAME NAME is written with all letters in upper case characters followed by the words "control/data frame", e.g. TIME ALIGNMENT control frame. | +| IE | When referring to an information element (IE) in the specification the Information Element Name is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation "IE", e.g. Frame Number IE. | +| Value of an IE | When referring to the value of an information element (IE) in the specification the "Value" is written as it is specified in subclause 5.6.3 enclosed by quotation marks, e.g. "0" or "255". | + +# 4 General + +## 4.1 General aspects for the SYNC protocol for UTRAN + +### 4.1.1 General aspects + +The MBMS Synchronisation protocol (SYNC) is located in the User plane of the Radio Network layer over the Iu interface: the Iu UP protocol layer. + +The SYNC protocol for UTRAN is used to convey user data associated to MBMS Radio Access Bearers. + +One SYNC protocol instance is associated to one MBMS RAB and one MBMS RAB only. If several MBMS RABs are established towards one given UE, then these MBMS RABs make use of several SYNC protocol instances. + +SYNC protocol instances exist at Iu access point as defined (TS 25.410 [2]) i.e. at CN and UTRAN. + +Whenever an MBMS RAB requires transfer of user data in the Iu UP, an Iu UP protocol instance exists at each Iu interface access points. These Iu UP protocol instances are established and released together with the associated MBMS RAB. + +The following figure illustrates the logical placement of the SYNC protocol layer and the placement of the Data Streams sources outside of the Access Stratum. + +![Diagram illustrating the logical placement of the SYNC protocol layer and the placement of the Data Streams sources outside of the Access Stratum. The diagram shows the User Plane (UP) architecture across the UE, Radio (Uu), UTRAN, Iu, and CN. The Non-Access Stratum (NAS) contains NAS Data Streams. The Access Stratum (AS) contains Radio protocols, SYNC, TNL Protocol, and Transport Layer. The SYNC protocol is shown in the UTRAN and CN components of the AS.](06da11ab76cacc38bbcd714e437797ea_img.jpg) + +The diagram illustrates the logical placement of the SYNC protocol layer in the User Plane (UP) architecture. It is divided into three main horizontal sections: Non-Access Stratum (NAS), Access Stratum (AS), and the underlying radio and network components. + + +- Non-Access Stratum (NAS):** At the top, this section contains 'NAS Data Streams' in both the UE and CN. Arrows indicate data flow from these streams down into the AS. +- Access Stratum (AS):** This middle section is composed of several protocol layers. + - In the **UE**, it contains 'Radio protocols'. + - In the **UTRAN**, it contains 'Radio protocols', 'SYNC', and 'TNL Protocol'. + - In the **CN**, it contains 'SYNC', 'TNL Protocol', and 'Transport Layer'. + - Horizontal arrows show data flow between the UE's Radio protocols and the UTRAN's Radio protocols, and between the UTRAN's TNL Protocol and the CN's TNL Protocol. +- Bottom Section:** This includes the 'UE', 'Radio (Uu)' interface, 'UTRAN', 'Iu' interface, and 'CN'. + + Vertical dashed lines separate the UE, UTRAN, and CN components. The 'SYNC' protocol is specifically highlighted in the UTRAN and CN within the AS. + +Diagram illustrating the logical placement of the SYNC protocol layer and the placement of the Data Streams sources outside of the Access Stratum. The diagram shows the User Plane (UP) architecture across the UE, Radio (Uu), UTRAN, Iu, and CN. The Non-Access Stratum (NAS) contains NAS Data Streams. The Access Stratum (AS) contains Radio protocols, SYNC, TNL Protocol, and Transport Layer. The SYNC protocol is shown in the UTRAN and CN components of the AS. + +Figure 4.1.1-1: SYNC protocol layer occurrence in UTRAN overall architecture (User Plane View) + +## 4.2 General aspects for the SYNC protocol for E-UTRAN + +### 4.2.1 General aspects + +The MBMS Synchronisation protocol (SYNC) is located in the User plane of the Radio Network layer over the M1 interface: the M1 UP protocol layer. + +The SYNC protocol for E-UTRAN is used to convey user data associated to MBMS Radio Access Bearers. + +One SYNC protocol instance is associated to one MBMS E-RAB and one MBMS E-RAB only. + +SYNC protocol instances exist at M1 access point as defined (TS 36.440 [5]) i.e. at EPC and E-UTRAN. + +Whenever an MBMS E-RAB requires transfer of user data in the M1 UP, an M1 UP protocol instance exists at each M1 interface access points. These M1 UP protocol instances are established and released together with the associated MBMS E-RAB. + +The following figure illustrates the logical placement of the SYNC protocol layer and the placement of the Data Streams sources outside of the Access Stratum. + +![Diagram illustrating the SYNC protocol layer occurrence in E-UTRAN overall architecture (User Plane View). The diagram shows the User Equipment (UE), Radio (Uu) interface, E-UTRAN, M1 interface, and Core Network (CN). The UE contains NAS Data Streams and Radio protocols. The E-UTRAN contains Radio protocols, SYNC, and TNL Protocol. The CN contains NAS Data Streams and Radio protocols. The SYNC protocol is shown occurring in the E-UTRAN and CN, with arrows indicating data flow between the NAS Data Streams and the Radio protocols, and between the Radio protocols and the SYNC protocol.](1c94fd3cebf58af136144f14160d128e_img.jpg) + +The diagram illustrates the logical placement of the SYNC protocol layer in the E-UTRAN overall architecture (User Plane View). It shows the flow of data from the NAS Data Streams in the UE and CN, through the Radio protocols, to the SYNC protocol in the E-UTRAN and CN. The SYNC protocol is shown as a layer above the TNL Protocol in the E-UTRAN and CN. The UE and CN are connected to the E-UTRAN via the Radio (Uu) and M1 interfaces respectively. The E-UTRAN is divided into the Non-Access Stratum (NAS) and the Access Stratum (AS). The NAS contains the NAS Data Streams, and the AS contains the Radio protocols, SYNC, and TNL Protocol. The SYNC protocol is shown as a layer above the TNL Protocol in the AS of the E-UTRAN and CN. Arrows indicate the flow of data between the NAS Data Streams and the Radio protocols, and between the Radio protocols and the SYNC protocol. + +Diagram illustrating the SYNC protocol layer occurrence in E-UTRAN overall architecture (User Plane View). The diagram shows the User Equipment (UE), Radio (Uu) interface, E-UTRAN, M1 interface, and Core Network (CN). The UE contains NAS Data Streams and Radio protocols. The E-UTRAN contains Radio protocols, SYNC, and TNL Protocol. The CN contains NAS Data Streams and Radio protocols. The SYNC protocol is shown occurring in the E-UTRAN and CN, with arrows indicating data flow between the NAS Data Streams and the Radio protocols, and between the Radio protocols and the SYNC protocol. + +Figure 4.2.1-1: SYNC protocol layer occurrence in E-UTRAN overall architecture (User Plane View) + +# 5 SYNC protocol version 1 + +## 5.1 General + +### 5.1.1 Applicability of SYNC protocol version 1 + +This version of the specification specifies the SYNC protocol for UTRAN and E-UTRAN. It is on top of TNL in Iu (UTRAN) and M1 (E-UTRAN) user plane, i.e. Iu userplane TNL transports SYNC protocol PDUs over the Iu interface, M1 userplane TNL transports SYNC protocol PDUs over the M1 interface. + +As a specification convention, within this specification, the interface between the Core Network and the Radio Access Network is denoted as the “RAN Access Interface”, the termination point at the Radio Access Network is denoted as “RAN Access Node”, the termination point at the Core Network is denoted as “Core Network” (CN). Further, “MBMS RAB” denotes the Radio Access data bearer together with the RAN Access Interface data bearer for MBMS service user data transmission. + +For the application of the SYNC protocol to UTRAN, the RAN Access Interface is the Iu interface, the RAN Access Node is the RNC. + +For the application of the SYNC protocol to E-UTRAN, the RAN Access Interface is the M1 interface, the RAN Access Node is the eNB. + +### 5.1.1 Operation of the SYNC protocol + +The SYNC protocol layer is present for data streams that originate in the CN and carry additional information within a specific userplane-frame. + +The two strata communicate through a Service Access Point for Non Access Stratum (NAS) Data Streams transfer. + +### 5.1.2 Interfaces of the SYNC protocol layer + +As part of the Access Stratum responsibility, the SYNC protocol layer provides the services and functions that are necessary to handle non access stratum data streams for MBMS. The SYNC protocol layer is providing these services to the UP upper layers through a Dedicated Service Access Point used for Information Transfer. + +The SYNC protocol layer is using services of the Transport layers in order to transfer user plane PDUs over the RAN Access interface. + +## 5.2 SYNC protocol layer services + +The following functions are needed to support the SYNC protocol: + +- Transfer of user data along with synchronisation information; +- Transfer of synchronisation information without user data. + +## 5.3 Services Expected from the UP Data Transport layer + +The SYNC protocol layer expects the following services from the Transport Network Layer: + +- Transfer of user data. +- No flow control. + +## 5.4 Elementary procedures + +### 5.4.1 Transfer of User Data for MBMS procedure + +#### 5.4.1.1 Successful operation + +The purpose of the Transfer of User Data procedure for MBMS is to transfer RAN Access Interface UP frames from the RAN Access interface UP protocol layers at CN to the RAN Access interface UP protocol layer at the RAN Access Node. One RAN Access interface UP instance is associated to a single MBMS RAB only. + +The Transfer of User Data procedure is invoked whenever user data for that particular RAB needs to be sent across the Radio Access interface. + +The NAS Data Streams specific functions make the padding of the payload (if needed) so that the Radio Access interface UP frame payload will be an integer number of octets. Then the NAS Data Streams specific functions perform, if needed, CRC calculation of the Iu/M1 frame payload and passes the Radio Access interface UP frame payload down to the Frame Handler function. + +The Frame Handler function within the CN retrieves the packet counter and octet counter value from its internal memory, formats the frame header and frame payload into the appropriate PDU Type and sends the Radio Access interface UP frame PDU to the lower layers for transfer across the Radio Access interface. If the user data is provided with compressed IP header, the Radio Access interface UP frame contains PDCP information and the uncompressed IP header. + +The Frame Handler function within the CN is also responsible for appropriate setting of the Time Stamp value in order to allow all RAN Access nodes to submit the MBMS user data in a synchronised manner. + +Upon reception of a user data frame, the RAN Access interface UP protocol layer within the RAN Access node checks the consistency of the RAN Access interface UP frame as follows: + +- The Frame Handler function checks the consistency of the frame header and the consistency of the packet counter value. +- Then the RAN Access node utilises the time stamp information to schedule the user data on the radio interface on the next TTI for UTRAN or MCH scheduling period for E-UTRAN as defined in TS 36.300 [6]. + +![Diagram showing the successful transfer of user data from the CN (Core Network) to the RAN Access node. The diagram consists of two rectangular boxes, 'RAN Access node' on the left and 'CN' on the right, both connected to a common horizontal line at the bottom. A horizontal arrow labeled 'TRANSFER OF USER DATA' points from the CN box to the RAN Access node box.](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) + +Diagram showing the successful transfer of user data from the CN (Core Network) to the RAN Access node. The diagram consists of two rectangular boxes, 'RAN Access node' on the left and 'CN' on the right, both connected to a common horizontal line at the bottom. A horizontal arrow labeled 'TRANSFER OF USER DATA' points from the CN box to the RAN Access node box. + +**Figure 5.4.1.1-1. Successful Transfers of User Data.** + +#### 5.4.1.2 Unsuccessful operation + +If multiple consecutive RAN Access interface UP frames carrying the user data are incorrectly formatted or cannot be correctly treated by the receiving RAN Access interface UP protocol layer, or if multiple consecutive frames loss is detected due to gaps in the sequence of the received frame numbers, the RAN Access node shall, if packet length information in Type 3 is not provided, + +- in case the RAN Access Interface UP is the Iu UP. + - cease to provide user data to the radio interface protocol entities and wait until the next synchronisation sequence if soft combining and MBSFN are used, or until the next scheduling transmission interval if the RNC acts as an MRNC and TDM multiplexing is used, as described in TS 25.346 [4]. +- in case the RAN Access Interface UP is the M1 UP and MBSFN is used, + - cease to provide user data to the radio interface protocol entities and wait until the next dynamic scheduling interval, as described in TS 36.300 [6]. +- in case the RAN Access Interface UP is the M1 UP and SC-PTM is used, + - provide other correctly received user data to the radio interface protocol entities, as described in TS 36.300 [6]. + +If packet length information in Type 3 is provided, the RAN Access nodes could cease to provide user data to the radio interface protocol entities for those lost subframes. + +### 5.4.2 Transfer of Synchronisation Information for MBMS procedure (without user data) + +#### 5.4.2.1 Successful operation + +The purpose of the Transfer of Synchronisation Information for MBMS procedure is to transfer synchronisation information from the CN to the RAN Access node at the end of each synchronization sequence (see TS 25.346 [4], TS 36.300 [6]) to improve the RAN Access node resynchronization in case of packet loss. + +The Frame Handler function within the CN retrieves the synchronisation time stamp from its internal clock and the total packet counter and total octet counter from its internal memory, formats the frame header and frame payload into the appropriate PDU Type and sends the RAN Access interface UP frame PDU to the lower layers for transfer across the RAN Access interface. + +If there is no data frame in a synchronization sequence, synchronization information shall still be transmitted. + +Furthermore, the SYNC PDU towards RAN Access node could contain length of each packet if supported. + +Upon reception of a user data frame, the RAN Access interface UP protocol layer checks the consistency of the RAN Access interface UP frame as follows: + +- The Frame Handler function checks the consistency of the frame header and the consistency of the synchronisation time stamp, total packet counter, total octet counter and packets length counter value if contained. + +![Diagram showing the successful transfer of synchronization information from a CN to a RAN Access node.](5e92d9e8e9ce204e405bff2367f88176_img.jpg) + +The diagram illustrates a 'Successful Transfer of Synchronisation Information'. It features two main entities: 'RAN Access node' on the left and 'CN' (Core Network) on the right. Both are represented by rectangular boxes with vertical lines extending downwards to horizontal bars. A horizontal arrow labeled 'TRANSFER OF SYNC INFO' points from the CN side towards the RAN Access node side. + +Diagram showing the successful transfer of synchronization information from a CN to a RAN Access node. + +Figure 5.4.2.1-1. Successful Transfers of Synchronisation Information. + +#### 5.4.2.2 Unsuccessful operation + +If the RAN Access interface UP frame without user data is incorrectly formatted or cannot be correctly treated by the receiving RAN Access interface UP protocol layer, the RAN Access interface UP protocol layer shall either discard the frame or pass it to the upper layers with a frame classification indicating a corrupted frame. + +## 5.5 Elements for the SYNC protocol + +### 5.5.1 General + +In the present document the structure of frames will be specified by using figures similar to Figure 5.5.1-1. + +| Bits | | | | | | | | Number of Octets | | | | | +|------------------|---|---|-------|---------|---|---------|---|------------------|---------|--------------|--|--| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | +| Field 1 | | | | Field 2 | | | | 1 | Octet 1 | Header part | | | +| Field 3 | | | | | | Field 4 | | 2 | Octet 2 | | | | +| Field 4 continue | | | Spare | | | | | | Octet 3 | | | | +| Field 6 | | | | | | | | 2 | Octet 4 | Payload part | | | +| Field 6 continue | | | | Padding | | | | | Octet 5 | | | | +| Spare extension | | | | | | | | 0-m | | | | | + +Figure 5.5.1-1. Example frame format. + +Unless otherwise indicated, fields which consist of multiple bits within an octet will have the most significant bit located at the higher bit position (indicated above frame in Figure 5.5.1-1). In addition, if a field spans several octets, most significant bits will be located in lower numbered octets (right of frame in Figure 5.5.1-1). + +On the Iu/M1 interface, the frame will be transmitted starting from the lowest numbered octet. Within each octet, the bits are sent according decreasing bit position (bit position 7 first). + +Spare bits should be set to "0" by the sender and should not be checked by the receiver. + +The header part of the frame is always an integer number of octets. The payload part is octet aligned (by adding 'Padding' when needed). + +The receiver should be able to remove an additional spare extension field that may be present at the end of a frame. See description of Spare extension field. + +### 5.5.2 Frame format for the SYNC protocol + +#### 5.5.2.1 Transfer of Synchronisation Information without payload (SYNC PDU Type 0) + +This Frame Format is defined to transfer synchronisation information over the RAN Access Interface UP without user data payload. + +The following shows the SYNC frame structure for PDU TYPE 0 data frame of the RAN Access Interface UP protocol at the SAP towards the transport layers (TNL-SAP). + +| Bits | | | | | | | | Number of Octets | | | | | | +|------------------------|---|---|---|-------|---|---------|---|------------------|----------------------|--|--|--|--| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | | +| PDU Type (=0) | | | | spare | | | | 1 | Frame Control Part | | | | | +| Time Stamp | | | | | | | | 2 | | | | | | +| Packet Number | | | | | | | | 2 | | | | | | +| Elapsed Octet Counter | | | | | | | | 4 | | | | | | +| Total Number Of Packet | | | | | | | | 3 | | | | | | +| Total Number Of Octet | | | | | | | | 5 | | | | | | +| Header CRC | | | | | | Padding | | 1 | Frame Check Sum Part | | | | | + +**Figure 5.5.2.1-1. SYNC PDU Type 0 Format.** + +The SYNC PDU TYPE 0 data frame is made of two parts: + +- 1) SYNC Frame Control part (fixed size); +- 2) SYNC Frame Check Sum part (fixed size); + +#### 5.5.2.2 Transfer of User Data for MBMS with uncompressed header (SYNC PDU Type 1) + +This Frame Format is defined to transfer user data over the RAN Access Interface UP for user data with uncompressed header. + +The following shows the SYNC frame structure for PDU TYPE 1 data frame of the RAN Access Interface UP protocol at the SAP towards the transport layers (TNL-SAP). + +| Bits | | | | | | | | Number of Octets | | | | | | +|-----------------------|---|---|---|---------|---|-------------|---|------------------|----------------------|--|--|--|--| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | | +| PDU Type (=1) | | | | spare | | | | 1 | Frame Control Part | | | | | +| Time Stamp | | | | | | | | 2 | | | | | | +| Packet Number | | | | | | | | 2 | | | | | | +| Elapsed Octet Counter | | | | | | | | 4 | | | | | | +| Header CRC | | | | | | Payload CRC | | 2 | Frame Check Sum Part | | | | | +| Payload CRC | | | | | | | | | | | | | | +| Payload Fields | | | | | | | | 1-n | Frame Payload part | | | | | +| Payload Fields | | | | Padding | | | | | | | | | | +| Spare extension | | | | | | | | 0-4 | | | | | | + +**Figure 5.5.2.2-1. SYNC PDU Type 1 Format.** + +The SYNC PDU TYPE 1 data frame is made of three parts: + +- 1) SYNC Frame Control part (fixed size); +- 2) SYNC Frame Check Sum part (fixed size); +- 3) SYNC Frame Payload part (SDU sizes rounded up to octets [Note: this does not consider the usage of spare extension field]). + +#### 5.5.2.3 Transfer of User Data for MBMS with compressed header (SYNC PDU Type 2) + +This Frame Format is defined to transfer user data over the RAN Access Interface UP for user data with compressed header. + +The following shows the SYNC frame structure for PDU TYPE 2 data frame of the RAN Access Interface UP protocol at the SAP towards the transport layers (TNL-SAP). + +For this version of the specification, SYNC PDU TYPE 2 is only applicable if the RAN Access Interface UP is the Iu UP, it shall not be used over M1. + +| Bits | | | | | | | | Number of Octets | | | | | | | +|--------------------------------|---|---|-------|-------------|---|------------|---|------------------|----------------------|--|--|--|--|--| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | | | +| PDU Type (=2) | | | spare | | | IPv6 indic | | 1 | Frame Control Part | | | | | | +| Time Stamp | | | | | | | | 2 | | | | | | | +| Packet Number | | | | | | | | 2 | | | | | | | +| Elapsed Octet Counter | | | | | | | | 4 | | | | | | | +| PDCP Information | | | | | | | | 1 | | | | | | | +| Uncompressed Payload IP header | | | | | | | | 20(40) | | | | | | | +| Header CRC | | | | Payload CRC | | | | 2 | Frame Check Sum Part | | | | | | +| Payload CRC | | | | | | | | | | | | | | | +| Payload Fields | | | | | | | | 1-n | Frame Payload part | | | | | | +| Payload Fields | | | | Padding | | | | | | | | | | | +| Spare extension | | | | | | | | 0-4 | | | | | | | + +**Figure 5.5.2.3-1. SYNC PDU Type 2 Format.** + +The SYNC PDU TYPE 2 data frame is made of three parts: + +- 1) SYNC Frame Control part (fixed size); +- 2) SYNC Frame Check Sum part (fixed size); +- 3) SYNC Frame Payload part (SDU sizes rounded up to octets [Note: this does not consider the usage of spare extension field]). + +#### 5.5.2.4 Transfer of Synchronisation Information with Length of Packets (SYNC PDU Type 3) + +This Frame Format is defined to transfer synchronisation information over the RAN Access Interface UP with Length of Packets. + +The following shows the SYNC frame structure for PDU TYPE 3 data frame of the RAN Access Interface UP protocol at the SAP towards the transport layers (TNL-SAP). + +| Bits | | | | | | | | Number of Octets | | | | | | | | | | +|---------------------------------------------|---|---|---|----------------------------------|---|---|---|--------------------------------|----------------------|--|--|--|--|--|--|--|--| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | | | | | | +| PDU Type (=3) | | | | spare | | | | 1 | Frame Control Part | | | | | | | | | +| Time Stamp | | | | | | | | 2 | | | | | | | | | | +| Packet Number | | | | | | | | 2 | | | | | | | | | | +| Elapsed Octet Counter | | | | | | | | 4 | | | | | | | | | | +| Total Number Of Packet | | | | | | | | 3 | | | | | | | | | | +| Total Number Of Octet | | | | | | | | 5 | | | | | | | | | | +| Header CRC | | | | Payload CRC | | | | 2 | Frame Check Sum Part | | | | | | | | | +| Payload CRC | | | | | | | | | | | | | | | | | | +| Length of the 1 st Packet | | | | | | | | 1.5*
(Packet Number -1) + 2 | Frame Payload part | | | | | | | | | +| Length of the 1 st Packet (cont) | | | | Length of 2 nd packet | | | | | | | | | | | | | | +| ... | | | | | | | | | | | | | | | | | | +| Length of the N th Packet | | | | | | | | | | | | | | | | | | +| Length of the N th Packet (cont) | | | | Padding | | | | | | | | | | | | | | +| Spare extension | | | | | | | | 0-4 | | | | | | | | | | + +Figure 5.5.2.4-1. SYNC PDU Type 3 Format (Odd number of packets, i.e. N=1, 3, 5, ...) + +| Bits | | | | | | | | Number of Octets | | | | | | | | | | +|---------------------------------------------|---|---|---|--------------------------------------|---|---|---|--------------------|----------------------|--|--|--|--|--|--|--|--| +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | | | | | | +| PDU Type (=3) | | | | spare | | | | 1 | Frame Control Part | | | | | | | | | +| Time Stamp | | | | | | | | 2 | | | | | | | | | | +| Packet Number | | | | | | | | 2 | | | | | | | | | | +| Elapsed Octet Counter | | | | | | | | 4 | | | | | | | | | | +| Total Number Of Packet | | | | | | | | 3 | | | | | | | | | | +| Total Number Of Octet | | | | | | | | 5 | | | | | | | | | | +| Header CRC | | | | Payload CRC | | | | 2 | Frame Check Sum Part | | | | | | | | | +| Payload CRC | | | | | | | | | | | | | | | | | | +| Length of the 1 st Packet | | | | | | | | 1.5* Packet Number | Frame Payload part | | | | | | | | | +| Length of the 1 st Packet (cont) | | | | Length of the 2 nd Packet | | | | | | | | | | | | | | +| ... | | | | | | | | | | | | | | | | | | +| Length of the N th Packet | | | | | | | | | | | | | | | | | | +| Spare extension | | | | | | | | 0-4 | | | | | | | | | | + +**Figure 5.5.2.4-2. SYNC PDU Type 3 Format (Even number of packets, i.e. N=2, 4, 6, ...)** + +The SYNC PDU TYPE 3 data frame is made of three parts: + +- 1) SYNC Frame Control part (fixed size); +- 2) SYNC Frame Check Sum part (fixed size); +- 3) SYNC Frame Payload part (variable size); the size of the SYNC Frame Payload part is the length of the *Length of the Nth Packet IE* in octets = $1.5 * (\text{Packet Number} - 1) + 2 + \text{the length of Spare Extension}$ , if the number of packets is odd in the synchronization sequence; the length of the *Length of the Nth Packet IE* in octets = $1.5 * \text{Packet Number} + \text{the length of Spare Extension}$ , if the number of packets is even in the synchronization sequence. + +### 5.5.3 Coding of information elements in frames + +#### 5.5.3.1 PDU Type + +**Description:** The PDU type indicates the structure of the SYNC frame. The field takes the value of the PDU Type it identifies: i.e. "0" for PDU Type 0. The PDU type is in bit 4 to bit 7 in the first octet of the frame. + +**Value range:** {0=synchronisation frame without payload, 1=user data with synchronisation frame for uncompressed headers, 2=user data with synchronisation frame for compressed headers, 3=synchronisation frame with Length of Packets, 4-15=reserved for future PDU type extensions} + +**Field length:** 4 bits + +#### 5.5.3.2 Timestamp + +**Description:** Relative time value for the starting time of a synchronization sequence within the synchronisation period. + +**Value range:** {0...60000-1} Unit: multiples of 10ms. + +Note: The value range allows for a synchronisation period of 600s. + +**Field length:** 2 octets + +#### 5.5.3.3 Packet Number + +**Description:** This parameter indicates the number of elapsed SYNC PDUs cumulatively within the synchronization sequence. It helps the RAN Access node to notice the loss of SYNC PDUs. Additionally it is used to reorder the PDUs in the RAN Access node. The Packet number is reset at the end of every synchronisation sequence, and is set to 0 for the 1st SYNC PDU of every synchronisation sequence. SYNC PDUs of Type 0 and Type 3 are not counted by this parameter. + +**Value range:** {0..216-1}. + +**Field length:** 2 octets. + +#### 5.5.3.4 Elapsed Octet Counter + +**Description:** This parameter indicates the number of elapsed cumulative octets cumulatively within one synchronisation sequence. It helps the RAN Access node to know how many packets were not received in case of packet loss. This counter is reset at the end of every synchronisation sequence, and is set to 0 for the 1st SYNC PDU of every synchronisation sequence. This parameter does not count the header part of the SYNC PDU. Octets of SYNC PDUs of Type 0 and Type 3 are not counted by this parameter. + +**Value range:** {0..232-1}. + +**Field length:** 4 octets. + +#### 5.5.3.5 Total Number Of Packet + +**Description:** This parameter indicates cumulatively the number of the packets for the MBMS service within one synchronization period. SYNC PDUs of Type 0 and Type 3 are not counted by this parameter. + +**Value range:** {0..224-1}. + +Note: In case of soft combining and MBSFN(except in case the RNC acts as an MRNC and TDM multiplexing is used), the parameter shall be ignored in RNC. + +**Field length:** 3 octets. + +#### 5.5.3.6 Total Number Of Octet + +**Description:** This parameter indicates cumulatively the number of the octets for the MBMS service within one synchronization period. This parameter does not count the header part of the SYNC PDU. Octets of SYNC PDUs of Type 0 and Type 3 are not counted by this parameter. + +**Value range:** {0..240-1}. + +Note: In case of soft combining and MBSFN(except in case the RNC acts as an MRNC and TDM multiplexing is used), the parameter shall be ignored in RNC. + +**Field length:** 5 octets. + +#### 5.5.3.7 PDCP Information + +**Description:** This parameter contains PDCP Information as specified in TS 25.323 [3]. + +**Value range:** as specified in TS 25.323 [3]. + +**Field length:** 1 octet. + +#### 5.5.3.8 IPv6 Indicator + +**Description:** This parameter indicates whether the Uncompressed Payload IP header is of IPv6 type. + +**Value range:** {0=IPv4, 1=IPv6}. + +**Field length:** 1 bit. + +#### 5.5.3.9 Uncompressed Payload IP header + +**Description:** This parameter provides the uncompressed IP header of the payload. + +**Value range:** {any value} + +**Field length:** 20 octets if IPv6 Indicator=0, 40 octets if IPv6 Indicator=1. + +#### 5.5.3.10 Header CRC + +**Description:** This field contains the CRC of all fields in Frame Control Part. The CRC is a 6-bit checksum based on the generator polynomial $G(D) = D^6 + D^5 + D^3 + D^2 + D^1 + 1$ , see subclause 5.6.2. With this CRC all error bursts shorter than 7 bits are detected, as well as all odd number of bits faulty (and two-bit faults) when the protected area is shorter than 24 bits, (max 3 octets). + +**Field length:** 6 bits. + +#### 5.5.3.11 Payload CRC + +**Description:** This field contains the CRC of all the fields (including Padding and possible Spare extension) of the Frame Payload Part. The CRC is a 10 bit checksum based on the generator polynomial $G(D) = D^{10} + D^9 + D^5 + D^4 + D^1 + 1$ , see subclause 5.6.2. With this CRC all error bursts shorter than 11 bits are detected, as well as all odd number of bits faulty (and two-bit faults) when the protected area is shorter than 500 bits (max 62 octets). + +**Field length:** 10 bits. + +#### 5.5.3.12 Padding + +**Description:** This field is an additional field used to make the frame header or payload part an integer number of octets when needed. Padding is set to "0" by the sender and is not interpreted by the receiver. + +**Value range:** {0-127}. + +**Field length:** 0-7 bits. + +#### 5.5.3.13 Spare + +**Description:** The spare field is set to "0" by the sender and should not be interpreted by the receiver. This field is reserved for later versions. + +**Value range:** $(0-2^n-1)$ . + +**Field Length:** n bits. + +#### 5.5.3.14 Spare extension + +**Description:** The spare extension field is reserved for extension in later versions. It shall not be sent. The receiver should be capable of receiving a spare extension. The spare extension should not be interpreted by the receiver since in later versions of the present document additional new fields might be added in place of the spare extension. The spare extension can be an integer number of octets carrying new fields or additional information; the maximum length of the spare extension field (m) depends on the PDU type. + +**Value range:** $0-2^{m*8}-1$ . + +**Field Length:** 0-m octets. For PDU Types in the set {1,2,3}, m=4. + +#### 5.5.3.15 Payload fields + +**Description:** This field contains the payload of the MBMS user data. + +**Value range:** {any value}. + +**Field length:** n bits + +#### 5.5.3.16 Length of the Nth Packet + +**Description:** This parameter indicates the length of the SYNC PDU within the synchronization sequence in octets. It helps the RAN Access node to recover from de-synchronization in case of the loss of consecutive SYNC PDUs. + +**Value range:** {0..212-1} + +**Field length:** 12 bits + +### 5.5.4 Timers + +not applicable + +## 5.6 Handling of unknown, unforeseen and erroneous protocol data + +### 5.6.1 General + +void + +### 5.6.2 CRC Calculation + +The parity bits are generated by one of the following cyclic generator polynomials: + +$$g_{CRC6}(D) = D^6 + D^5 + D^3 + D^2 + D^1 + 1;$$ + +$$g_{CRC10}(D) = D^{10} + D^9 + D^5 + D^4 + D^1 + 1.$$ + +Denote the bits to be protected of a frame by $a_1, a_2, a_3, \dots, a_{A_i}$ ( $a_1$ being the bit with the highest bit position in the first octet), and the parity bits by $p_1, p_2, p_3, \dots, p_{L_i}$ . $A_i$ is the length of the protected data and $L_i$ is 6 or 10 depending on the CRC length. + +The encoding is performed in a systematic form, which means that in GF(2), the polynomial + +$$a_1 D^{A_i+5} + a_2 D^{A_i+4} + \dots + a_{A_i} D^6 + p_1 D^5 + p_2 D^4 + \dots + p_5 D^1 + p_6$$ + +yields a remainder equal to 0 when divided by $g_{CRC6}(D)$ and the polynomial + +$$a_1 D^{A_i+9} + a_2 D^{A_i+8} + \dots + a_{A_i} D^{10} + p_1 D^9 + p_2 D^8 + \dots + p_9 D^1 + p_{10}$$ + +yields a remainder equal to 0 when divided by $g_{CRC10}(D)$ . If $A_i = 0$ , $p_1 = p_2 = p_3 = \dots = p_{L_i} = 0$ . + +### 5.6.3 Relation between input and output of the Cyclic Redundancy Check + +The protected bits are left unchanged in the frame. The parity bits for the Header CRC are put in the Header CRC field with $p_1$ being the highest bit position of the first octet of the Header CRC field. The parity bits for the Payload CRC are put in the Payload CRC field with $p_1$ being the highest bit position of the first octet of the Payload CRC field. + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-----|---------------------------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 12/2008 | 42 | RP-080831 | | | Presented to TSG-RAN for approval | | 1.0.0 | +| 12/2008 | 42 | RP-080831 | | | approved at TSG-RAN#42 and placed under change control | 1.0.0 | 8.0.0 | +| 12/2009 | 46 | RP-091182 | 0002 | 1 | Ignorance of Total Number Of Packet and Total Number Of Octet in case of Soft Combining and MBSFN | 8.0.0 | 8.1.0 | +| 12/2009 | 46 | RP-091182 | 0003 | 2 | Correction for SYNC Protocol | 8.0.0 | 8.1.0 | +| 12/2009 | - | - | - | - | Creation of version 9.0.0 based on v/ 8.1.0 | 8.1.0 | 9.0.0 | +| 12/2009 | 46 | RP-091190 | 0001 | 2 | Reusing SYNC for LTE | 8.1.0 | 9.0.0 | +| 12/2009 | 46 | RP-091190 | 0004 | | SYNC PDU TYPE2 not applicable for LTE MBMS | 8.1.0 | 9.0.0 | +| 12/2009 | 46 | RP-091190 | 0005 | 1 | CR on Mechanism for Consecutive Packet Loss in 25.446 | 8.1.0 | 9.0.0 | +| 03/2010 | 47 | RP-100227 | 0006 | 4 | Clarification on Total counter frame | 9.0.0 | 9.1.0 | +| 03/2010 | 47 | RP-100226 | 0007 | | Update Description for LTE MBMS Multiple Consecutive Packet Loss | 9.0.0 | 9.1.0 | +| 03/2010 | 47 | RP-100226 | 0008 | 1 | Small Corrections/Improvements for SYNC | 9.0.0 | 9.1.0 | +| 03/2010 | 47 | RP-100226 | 0010 | 1 | Corrections on Packet Number | 9.0.0 | 9.1.0 | +| 06/2010 | 48 | RP-100597 | 0011 | | Correction to MBMS scheduling terminology | 9.1.0 | 9.2.0 | +| 03/2011 | SP-49 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 9.2.0 | 9.2.1 | +| 03/2011 | | | | | Created version 10.0.0 based on v. 9.2.1 | 9.2.1 | 10.0.0 | +| 06/2011 | 52 | RP-110686 | 0012 | 1 | Specification Cleanup for Rel-10 | 10.0.0 | 10.1.0 | +| 12/2011 | 54 | RP-111650 | 0013 | 1 | Correction on the Length of Spare Extension | 10.1.0 | 10.2.0 | +| 12/2011 | 54 | RP-111650 | 0014 | 1 | Correction on the Spare Extension | 10.1.0 | 10.2.0 | +| 09/2012 | - | | | | Update to Rel-11 version (MCC) | 10.2.0 | 11.0.0 | +| 09/2014 | | | | | Update to Rel-12 version (MCC) | 11.0.0 | 12.0.0 | +| 12/2014 | 66 | RP-142093 | 0020 | 1 | Rapporteur Review | 12.0.0 | 12.1.0 | +| 12/2015 | 70 | RP-152101 | 0021 | 2 | Clarification on muting behavior in SC-PTM | 12.1.0 | 13.0.0 | +| 03/2016 | 71 | RP-160447 | 0023 | 1 | Clarification on SYNC | 13.0.0 | 13.1.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-07 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25452/raw.md b/marked/Rel-16/25_series/25452/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6bdd9e76f72232339ec27ae85ba037876e252afe --- /dev/null +++ b/marked/Rel-16/25_series/25452/raw.md @@ -0,0 +1,126 @@ + + + + +Error! No +text of + +Error! No text of specified style in +document. + +# Contents + +- Foreword ..... 4 +- 1 Scope..... 5 +- 2 References..... 5 +- 3 Definitions and abbreviations ..... 5 + - 3.1 Definitions..... 5 + - 3.2 Abbreviations ..... 5 +- 4 PCAP Signalling Bearer..... 6 + - 4.1 Introduction ..... 6 + - 4.2 Signalling Bearer..... 6 + - 4.3 Services Provided by the Signalling Bearer..... 6 +- Annex A (informative): Change history..... 7 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the signalling transport related to PCAP signalling to be used across the Iurp interface. The Iurp interface is a logical interface for the interconnection of Stand-Alone SMLC (SAS) and Radio Network Controller (RNC) components of the Universal Terrestrial Radio Access Network (UTRAN) for the UMTS system. The radio network control signalling between these nodes is based upon the Position Calculation Application Part (PCAP). + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TS 25.422: "UTRAN Iur Interface Signalling Transport". +- [2] ITU-T Recommendation Q.711 (1996-07): "Functional description of the signalling connection control part". +- [3] ITU-T Recommendation Q.712 (1996-07): "Definition and function of Signalling connection control part messages". +- [4] ITU-T Recommendation Q.713 (1996-07): "Signalling connection control part formats and codes". +- [5] ITU-T Recommendation Q.714 (1996-07): "Signalling connection control part procedures". +- [6] ITU-T Recommendation Q.715 (1996-07): "Signalling connection control part user guide". +- [7] ITU-T Recommendation Q.716 (1993-03): "Signalling Connection Control Part (SCCP) performance". +- [8] 3GPP TS 25.305: "Stage 2 functional specification of UE positioning in UTRAN" + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following definition applies: + +**Stand-Alone SMLC (SAS):** As defined in TS 25.305 [8]. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-------|-------------------------------------------| +| PCAP | Position Calculation Application Part | +| SAP | Service Access Point | +| SAS | Stand-Alone SMLC | +| SCCP | Signalling Connection Control Part | +| SMLC | Serving Mobile Location Centre | +| UE | User Equipment | +| UMTS | Universal Mobile Telecommunication System | +| UTRAN | UMTS Terrestrial Radio Access Network | + +# --- 4 PCAP Signalling Bearer + +## 4.1 Introduction + +This clause specifies the Signalling Bearer protocol stack that supports the PCAP signalling protocol. + +The following requirements on the Signalling Bearer can be stated: + +- provide reliable transfer of control plane signalling messages in both connectionless mode and connection-oriented mode; +- provide separate independent connections for distinguishing individual transactions; +- provide networking and routing functions; +- provide redundancy in the signalling network; +- provide load sharing. + +## 4.2 Signalling Bearer + +The Iupc signalling bearer shall comply with the requirements of clause 5.2 in TS 25.422 [1]. + +## 4.3 Services Provided by the Signalling Bearer + +When considering the requirements that the upper layers, i.e. PCAP, have on the Signalling Bearer, there are a number of services it has to provide and a number of functions to perform. These numbers of services that the signalling bearer shall provide, to the upper layers, are stated in references ITU-T Rec. Q.711 [2], ITU-T Rec. Q.712 [3], ITU-T Rec. Q.713 [4], ITU-T Rec. Q.714 [5], ITU-T Rec. Q.715 [6], and ITU-T Rec. Q.716 [7]. + +# Annex A (informative): Change history + +| Date / TSG | TSG Doc. | CR | Rev | Subject/Comment | New | +|------------|-----------|------|-----|------------------------------------------------------------|--------| +| 12/2008 | - | - | - | Creation of Rel-8 version based on v7.1.0 | 8.0.0 | +| 12/2009 | - | - | - | Creation of Rel-9 version based on v8.0.0 | 9.0.0 | +| SP-49 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 9.0.1 | +| 03/2011 | | | | Creation of Rel-10 version based on v9.0.1 | 10.0.0 | +| 52 | RP-110685 | 0003 | 1 | References cleanup (25.452) | 10.1.0 | +| 09/2012 | | | | Update to Rel-11 version (MCC) | 11.0.0 | +| 09/2014 | | | | Update to Rel-12 version (MCC) | 12.0.0 | +| 12/2015 | | | | Update to Rel-13 version (MCC) | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-07 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25453/02d0c8a07c481d880b73a25d02050fad_img.jpg b/marked/Rel-16/25_series/25453/02d0c8a07c481d880b73a25d02050fad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5630f6ddad10d064dc706f3fdb75be079a3ec0f --- /dev/null +++ b/marked/Rel-16/25_series/25453/02d0c8a07c481d880b73a25d02050fad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ea7c0d7a54ac5ed4b65a0b8a303e593792c54b44a092ecc990c2b77a6d32524 +size 11605 diff --git a/marked/Rel-16/25_series/25453/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg b/marked/Rel-16/25_series/25453/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b8ab8100adf0f11ff96854deb4b84dfe41b9893 --- /dev/null +++ b/marked/Rel-16/25_series/25453/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8f2ee54a5d0b6d25d61a507bf9451a6f72df7eb9ccde286afe3581b738f9122 +size 19889 diff --git a/marked/Rel-16/25_series/25453/17a1ba23b641c01871b08f0a4f08ef48_img.jpg b/marked/Rel-16/25_series/25453/17a1ba23b641c01871b08f0a4f08ef48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1240249c6595c281ca5ce6a0d347c4247ec91f6 --- /dev/null +++ b/marked/Rel-16/25_series/25453/17a1ba23b641c01871b08f0a4f08ef48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc5166a076ba9ad446ba519546438d1b24c2cbe4bf3d2c280ac716eb83bcdfaa +size 19924 diff --git a/marked/Rel-16/25_series/25453/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg b/marked/Rel-16/25_series/25453/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b91394e817f571133da518b3d25a9a1919e758a --- /dev/null +++ b/marked/Rel-16/25_series/25453/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b5b76dcbc4c85bbb7cc8c85b02fd5addee95761d5b94f9f10d2c1dad600b992 +size 12478 diff --git a/marked/Rel-16/25_series/25453/4141e32339a99ae82b6360896250e1fc_img.jpg b/marked/Rel-16/25_series/25453/4141e32339a99ae82b6360896250e1fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36092eece978df82c840843c73dfbc9dfd5d51da --- /dev/null +++ b/marked/Rel-16/25_series/25453/4141e32339a99ae82b6360896250e1fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e033a51acfba0acf39168ee463c5da5b639d3d803cdd80e06ea5e4dd7bedc760 +size 74921 diff --git a/marked/Rel-16/25_series/25453/58f4167687de8d7339594e5f6fbe0bc6_img.jpg b/marked/Rel-16/25_series/25453/58f4167687de8d7339594e5f6fbe0bc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7cd9906700d25e40727ce0a454da87a3af12aae8 --- /dev/null +++ b/marked/Rel-16/25_series/25453/58f4167687de8d7339594e5f6fbe0bc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ca28ebec7e8cef40c71bec9921d6213f6b4c198b64c713ff9b7e8ec0febde81 +size 12175 diff --git a/marked/Rel-16/25_series/25453/7728e2dd44c95d109debb1eb59e9b411_img.jpg b/marked/Rel-16/25_series/25453/7728e2dd44c95d109debb1eb59e9b411_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7613e0707873145532ada449cef0b0f7880266de --- /dev/null +++ b/marked/Rel-16/25_series/25453/7728e2dd44c95d109debb1eb59e9b411_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f4e3142a26815b856ad9609d58c38ca2dccf676f80012c3a681fb57a43cfcb5 +size 19928 diff --git a/marked/Rel-16/25_series/25453/8658cfab6a458b4a80ab2e384c61ff89_img.jpg b/marked/Rel-16/25_series/25453/8658cfab6a458b4a80ab2e384c61ff89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4c4bbce83011fc5cb787a416ca830ca4a220749 --- /dev/null +++ b/marked/Rel-16/25_series/25453/8658cfab6a458b4a80ab2e384c61ff89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ef11f299551fdd1c8d079aeb6340ae13dbde20eab49539704e2757f45752522 +size 13259 diff --git a/marked/Rel-16/25_series/25453/896e86ed12aff206d302c64f2e3091fa_img.jpg b/marked/Rel-16/25_series/25453/896e86ed12aff206d302c64f2e3091fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9034e01e86edb475194d046ef4828543bc65892e --- /dev/null +++ b/marked/Rel-16/25_series/25453/896e86ed12aff206d302c64f2e3091fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2fc4ff1fa5b5b8a634e7e5a218342fcd15a244f48ea277feeeaf088f8c7f488b +size 12145 diff --git a/marked/Rel-16/25_series/25453/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg b/marked/Rel-16/25_series/25453/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01ea0d4226ae1e8d683f67811c4246df747f8d1a --- /dev/null +++ b/marked/Rel-16/25_series/25453/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4546b556cad37f50a50ef97c404c7f3cbef9596c19ee82c15e8a260f3f303c6e +size 18814 diff --git a/marked/Rel-16/25_series/25453/937e2ba1c4e643eefca0ecdc2b25a26d_img.jpg b/marked/Rel-16/25_series/25453/937e2ba1c4e643eefca0ecdc2b25a26d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd069e56bd40c72864ff9e41d64e80f7430a5be3 --- /dev/null +++ b/marked/Rel-16/25_series/25453/937e2ba1c4e643eefca0ecdc2b25a26d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a4a13bd49cfdb12c584fe4c5ba5a7eaad6f2ae493e21375de2ffbec1ef8edda +size 74006 diff --git a/marked/Rel-16/25_series/25453/96b0240f56d14453b5da05ec30fd5c6e_img.jpg b/marked/Rel-16/25_series/25453/96b0240f56d14453b5da05ec30fd5c6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bdfb66de90645519bdd919d616276fc87c20f8eb --- /dev/null +++ b/marked/Rel-16/25_series/25453/96b0240f56d14453b5da05ec30fd5c6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a262df0c0a7618f5be91ef294df2586c9fdaa134fd05df0ce59631757cb65f39 +size 18002 diff --git a/marked/Rel-16/25_series/25453/9870bf462aa0d916a16d14b5a100c60a_img.jpg b/marked/Rel-16/25_series/25453/9870bf462aa0d916a16d14b5a100c60a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f713cfa565a3efc6ee5d04df350076b5a0a83cd --- /dev/null +++ b/marked/Rel-16/25_series/25453/9870bf462aa0d916a16d14b5a100c60a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c535d3ef1ae528e05b69edf7107a439e61d00f526dece38992882a6d936fa7e6 +size 10398 diff --git a/marked/Rel-16/25_series/25453/9cd90f495b95ad2116ff780248c26d95_img.jpg b/marked/Rel-16/25_series/25453/9cd90f495b95ad2116ff780248c26d95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b7e0e2e603d2742a90980313b030cbbf47ee142 --- /dev/null +++ b/marked/Rel-16/25_series/25453/9cd90f495b95ad2116ff780248c26d95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:985fd9a02c612a61fcc2ae849f8344e5c984157c59391b71cbff52617cb72ff7 +size 17618 diff --git a/marked/Rel-16/25_series/25453/a436856945c27adc69a909bde2da601f_img.jpg b/marked/Rel-16/25_series/25453/a436856945c27adc69a909bde2da601f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df95a1c00c2b43472f2efe5f20f65f8cb7e834d2 --- /dev/null +++ b/marked/Rel-16/25_series/25453/a436856945c27adc69a909bde2da601f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0662c1a955b5956c15e4f11fb1bfb0af5333c632c0fdc23d1efa5d57d842713e +size 92938 diff --git a/marked/Rel-16/25_series/25453/a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg b/marked/Rel-16/25_series/25453/a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b7160a6982a1966e610684a7699f940ff6ce75a6 --- /dev/null +++ b/marked/Rel-16/25_series/25453/a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2390d6fb1d1ad131c06c8cec5c5e4a4cce73136a6218453fec070b3bdf2b7509 +size 13203 diff --git a/marked/Rel-16/25_series/25453/add887c98f62ded73e823fee389405d3_img.jpg b/marked/Rel-16/25_series/25453/add887c98f62ded73e823fee389405d3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a08ae628bc1cd2850dc813f1f1112204a137c961 --- /dev/null +++ b/marked/Rel-16/25_series/25453/add887c98f62ded73e823fee389405d3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1ea0924ce99a17fbec1e6a5a988bb0b8ff9aef0bf40909c03c20fb1b43675e6 +size 23058 diff --git a/marked/Rel-16/25_series/25453/b904ac2472cab80892d1e783e6230d6e_img.jpg b/marked/Rel-16/25_series/25453/b904ac2472cab80892d1e783e6230d6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91852c8f920ec28c8aa646ef046dfcfa597b2d24 --- /dev/null +++ b/marked/Rel-16/25_series/25453/b904ac2472cab80892d1e783e6230d6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2c80b8af0edc337cfcf836be4ebe0816d7498711820a32d6d062f91c2780a3a +size 18984 diff --git a/marked/Rel-16/25_series/25453/bc19609ef2fbd9f6ddd2f8b857539802_img.jpg b/marked/Rel-16/25_series/25453/bc19609ef2fbd9f6ddd2f8b857539802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9684e16f2182afb6cc9a278d53c34e100ba51ebf --- /dev/null +++ b/marked/Rel-16/25_series/25453/bc19609ef2fbd9f6ddd2f8b857539802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8fded20f1c9a5f4a28c2947f1a8b85e8211c59690bb9f2a0a6bc47f0ed5795f3 +size 75637 diff --git a/marked/Rel-16/25_series/25453/d5918cee231b536f20789a18d861fae3_img.jpg b/marked/Rel-16/25_series/25453/d5918cee231b536f20789a18d861fae3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..692d8edb86986a6e66962e05d221efdc04c9487c --- /dev/null +++ b/marked/Rel-16/25_series/25453/d5918cee231b536f20789a18d861fae3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84074edc5b6762953f8c034181db080d4395098a989ccb05653ba0c0747958eb +size 11004 diff --git a/marked/Rel-16/25_series/25453/db5ab5d386827a5d5f5fad0f45612b90_img.jpg b/marked/Rel-16/25_series/25453/db5ab5d386827a5d5f5fad0f45612b90_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0bb0267d64ddc1212398dba901f6c37bdac53c93 --- /dev/null +++ b/marked/Rel-16/25_series/25453/db5ab5d386827a5d5f5fad0f45612b90_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:186d5afaa91c0577b1fa17e3493f052592e1be344ee9d2a685e7e4e20ad2333c +size 14038 diff --git a/marked/Rel-16/25_series/25453/e7511e4fa0a0df6c02eb793c62524690_img.jpg b/marked/Rel-16/25_series/25453/e7511e4fa0a0df6c02eb793c62524690_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b380203651bb5d19dddcab9a9aa3fc1d3abc1b6f --- /dev/null +++ b/marked/Rel-16/25_series/25453/e7511e4fa0a0df6c02eb793c62524690_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:273db5d6102bcdd36eaf58596b299ea18059ac193269604e57faf3a745203aa9 +size 76005 diff --git a/marked/Rel-16/25_series/25453/ead623e6a8ec701df64567695a57d01c_img.jpg b/marked/Rel-16/25_series/25453/ead623e6a8ec701df64567695a57d01c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..453f682ba7d2215c30f33a9d13c3ff870d804a3b --- /dev/null +++ b/marked/Rel-16/25_series/25453/ead623e6a8ec701df64567695a57d01c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a29e5a7ac4abac1fbf6393af68bad247f92f77a87040936e86fa6fdaf45537d +size 11316 diff --git a/marked/Rel-16/25_series/25453/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg b/marked/Rel-16/25_series/25453/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80a892ba7497ffa7d848c284acbb75ee2d05696b --- /dev/null +++ b/marked/Rel-16/25_series/25453/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eab74c8c760f4215224b9c9a1ffa351b141bf6917ba15b33f45675a489462d0b +size 13137 diff --git a/marked/Rel-16/25_series/25453/fc0735d325f0ebd9214171975c68a888_img.jpg b/marked/Rel-16/25_series/25453/fc0735d325f0ebd9214171975c68a888_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d935f8dd0540b4737e81c8122d734dba71aacc35 --- /dev/null +++ b/marked/Rel-16/25_series/25453/fc0735d325f0ebd9214171975c68a888_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d0e375c32909d357fb73654116f6c685dcde3787ed1cb376fdcbfbed9853092 +size 22445 diff --git a/marked/Rel-16/25_series/25453/febfdd6a7182116484c126105b53fdaf_img.jpg b/marked/Rel-16/25_series/25453/febfdd6a7182116484c126105b53fdaf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a21e4cfa6932a0a1b75b9b482f81dbe3c14f2c2a --- /dev/null +++ b/marked/Rel-16/25_series/25453/febfdd6a7182116484c126105b53fdaf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ead33c3345beaafb7d019f6c052b167388656f1de516ce7aa386a36262d75b1 +size 76546 diff --git a/marked/Rel-16/25_series/25453/raw.md b/marked/Rel-16/25_series/25453/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..791e4bc43b2c27cfbed8a12e3ddabdd3775140ea --- /dev/null +++ b/marked/Rel-16/25_series/25453/raw.md @@ -0,0 +1,13595 @@ + + + + + + +# Contents + +| | | +|----------------------------------------------------|----| +| Foreword..... | 9 | +| 1 Scope..... | 10 | +| 2 References..... | 10 | +| 3 Definitions and abbreviations..... | 11 | +| 3.1 Definitions..... | 11 | +| 3.2 Abbreviations..... | 12 | +| 4 General..... | 13 | +| 4.1 Procedure Specification Principles..... | 13 | +| 4.2 Forwards and Backwards Compatibility..... | 13 | +| 4.3 Specification Notations..... | 13 | +| 5 PCAP Services..... | 14 | +| 6 Services Expected from Signalling Transport..... | 15 | +| 7 Functions of PCAP..... | 15 | +| 8 PCAP Procedures..... | 15 | +| 8.1 Elementary Procedures..... | 15 | +| 8.2 Position Calculation..... | 16 | +| 8.2.1 General..... | 16 | +| 8.2.2 Successful Operation..... | 16 | +| 8.2.3 Unsuccessful Operation..... | 18 | +| 8.2.4 Abnormal Conditions..... | 18 | +| 8.3 Information Exchange Initiation..... | 19 | +| 8.3.1 General..... | 19 | +| 8.3.2 Successful Operation..... | 19 | +| 8.3.3 Unsuccessful Operation..... | 24 | +| 8.3.4 Abnormal Conditions..... | 24 | +| 8.4 Information Reporting..... | 25 | +| 8.4.1 General..... | 25 | +| 8.4.2 Successful Operation..... | 26 | +| 8.4.3 Abnormal Conditions..... | 27 | +| 8.5 Information Exchange Termination..... | 27 | +| 8.5.1 General..... | 27 | +| 8.5.2 Successful Operation..... | 27 | +| 8.5.3 Abnormal Conditions..... | 27 | +| 8.6 Information Exchange Failure..... | 27 | +| 8.6.1 General..... | 27 | +| 8.6.2 Successful Operation..... | 28 | +| 8.7 Error Indication..... | 28 | +| 8.7.1 General..... | 28 | +| 8.7.2 Successful Operation..... | 28 | +| 8.7.3 Abnormal Conditions..... | 29 | +| 8.8 Position Initiation..... | 29 | +| 8.8.1 General..... | 29 | +| 8.8.2 Successful Operation..... | 29 | +| 8.8.3 Unsuccessful Operation..... | 30 | +| 8.8.4 Abnormal Conditions..... | 30 | +| 8.9 Position Activation..... | 31 | +| 8.9.1 General..... | 31 | +| 8.9.2 Successful Operation..... | 31 | +| 8.9.3 Unsuccessful Operation..... | 33 | +| 8.9.4 Abnormal Conditions..... | 33 | +| 8.10 Position Parameter Modification..... | 34 | +| 8.10.1 General..... | 34 | +| 8.10.2 Successful Operation..... | 34 | + +| | | | +|----------|--------------------------------------------------------------|----| +| 8.10.3 | Abnormal Conditions..... | 34 | +| 8.11 | Abort..... | 34 | +| 8.11.1 | General..... | 34 | +| 8.11.2 | Successful Operation..... | 35 | +| 8.11.3 | Abnormal Conditions..... | 35 | +| 8.12 | Position Periodic Report..... | 35 | +| 8.12.1 | General..... | 35 | +| 8.12.2 | Successful Operation..... | 36 | +| 8.12.3 | Abnormal Conditions..... | 37 | +| 8.13 | Position Periodic Result..... | 37 | +| 8.13.1 | General..... | 37 | +| 8.13.2 | Successful Operation..... | 37 | +| 8.13.3 | Abnormal Conditions..... | 37 | +| 8.14 | Position Periodic Termination..... | 38 | +| 8.14.1 | General..... | 38 | +| 8.14.2 | Successful Operation..... | 38 | +| 8.14.3 | Abnormal Conditions..... | 38 | +| 9 | Elements for PCAP Communication..... | 38 | +| 9.1 | Message Functional Definiton and Content..... | 38 | +| 9.1.1 | General..... | 38 | +| 9.1.2 | Message Contents..... | 39 | +| 9.1.2.1 | Presence..... | 39 | +| 9.1.2.2 | Criticality..... | 39 | +| 9.1.2.3 | Range..... | 39 | +| 9.1.2.4 | Assigned Criticality..... | 39 | +| 9.1.3 | POSITION CALCULATION REQUEST..... | 40 | +| 9.1.4 | POSITION CALCULATION RESPONSE..... | 41 | +| 9.1.5 | POSITION CALCULATION FAILURE..... | 41 | +| 9.1.6 | INFORMATION EXCHANGE INITIATION REQUEST..... | 42 | +| 9.1.7 | INFORMATION EXCHANGE INITIATION RESPONSE..... | 43 | +| 9.1.8 | INFORMATION EXCHANGE INITIATION FAILURE..... | 43 | +| 9.1.9 | INFORMATION REPORT..... | 43 | +| 9.1.10 | INFORMATION EXCHANGE TERMINATION REQUEST..... | 43 | +| 9.1.11 | INFORMATION EXCHANGE FAILURE INDICATION..... | 44 | +| 9.1.12 | ERROR INDICATION..... | 44 | +| 9.1.13 | POSITION INITIATION REQUEST..... | 44 | +| 9.1.14 | POSITION INITIATION RESPONSE..... | 44 | +| 9.1.15 | POSITION INITIATION FAILURE..... | 45 | +| 9.1.16 | POSITION ACTIVATION REQUEST..... | 46 | +| 9.1.17 | POSITION ACTIVATION RESPONSE..... | 48 | +| 9.1.18 | POSITION ACTIVATION FAILURE..... | 49 | +| 9.1.19 | POSITION PARAMETER MODIFICATION..... | 49 | +| 9.1.20 | ABORT..... | 49 | +| 9.1.21 | POSITION PERIODIC REPORT..... | 50 | +| 9.1.22 | POSITION PERIODIC RESULT..... | 51 | +| 9.1.23 | POSITION PERIODIC TERMINATION..... | 51 | +| 9.2 | Information Element Functional Definitions and Contents..... | 51 | +| 9.2.1 | General..... | 51 | +| 9.2.2 | Radio Network Layer Related IEs..... | 52 | +| 9.2.2.1 | Almanac and Satellite Health SIB..... | 52 | +| 9.2.2.2 | Altitude and direction..... | 52 | +| 9.2.2.3 | Cause..... | 52 | +| 9.2.2.4 | Criticality Diagnostics..... | 56 | +| 9.2.2.5 | DGPS Corrections..... | 58 | +| 9.2.2.6 | Geographical Area..... | 59 | +| 9.2.2.7 | Geographical Coordinates..... | 61 | +| 9.2.2.8 | GPS Acquisition Assistance..... | 61 | +| 9.2.2.9 | GPS Almanac and Satellite Health..... | 63 | +| 9.2.2.10 | GPS Clock and Ephemeris Parameters..... | 65 | +| 9.2.2.11 | GPS Ionospheric Model..... | 67 | +| 9.2.2.12 | GPS Measured Results..... | 68 | + +| | | | +|-----------|----------------------------------------------------|-----| +| 9.2.2.13 | GPS Navigation Model..... | 69 | +| 9.2.2.14 | GPS Real Time Integrity..... | 70 | +| 9.2.2.15 | GPS Reference Time..... | 71 | +| 9.2.2.16 | GPS Transmission TOW..... | 72 | +| 9.2.2.17 | GPS UTC Model..... | 72 | +| 9.2.2.18 | GPS-UTRAN Time Relationship Uncertainty..... | 72 | +| 9.2.2.19 | Information Exchange ID..... | 72 | +| 9.2.2.20 | Void..... | 73 | +| 9.2.2.21 | Information Report Characteristics..... | 73 | +| 9.2.2.22 | Information Type..... | 74 | +| 9.2.2.23 | Message Structure..... | 78 | +| 9.2.2.24 | Message Type..... | 78 | +| 9.2.2.25 | Method Type..... | 79 | +| 9.2.2.26 | Requested Data Value..... | 80 | +| 9.2.2.27 | Requested Data Value Information..... | 81 | +| 9.2.2.28 | Transaction ID..... | 81 | +| 9.2.2.29 | Transmission TOW Indicator..... | 82 | +| 9.2.2.30 | Uncertainty Ellipse..... | 82 | +| 9.2.2.31 | Cell-ID Measured Results Info List..... | 82 | +| 9.2.2.32 | OTDOA Measured Results Info List..... | 85 | +| 9.2.2.33 | OTDOA Neighbour Cell Info..... | 88 | +| 9.2.2.34 | OTDOA Reference Cell Info..... | 90 | +| 9.2.2.35 | UE Positioning Measurement Quality..... | 93 | +| 9.2.2.36 | UTRAN Access Point Position with Altitude..... | 94 | +| 9.2.2.37 | UTRAN Cell Identifier (UC-ID)..... | 94 | +| 9.2.2.37A | Extended RNC-ID..... | 95 | +| 9.2.2.38 | Horizontal Accuracy Code..... | 95 | +| 9.2.2.39 | Vertical Accuracy Code..... | 95 | +| 9.2.2.40 | Accuracy Fulfilment Indicator..... | 96 | +| 9.2.2.41 | Uplink DPCH information..... | 96 | +| 9.2.2.42 | Frequency information..... | 96 | +| 9.2.2.43 | PRACH parameters..... | 97 | +| 9.2.2.44 | Compressed Mode Assistance Data..... | 97 | +| 9.2.2.45 | C-RNTI..... | 97 | +| 9.2.2.46 | Primary Scrambling Code..... | 97 | +| 9.2.2.47 | PRACH information..... | 98 | +| 9.2.2.48 | TFS..... | 98 | +| 9.2.2.49 | CTFC..... | 99 | +| 9.2.2.50 | Request Type..... | 100 | +| 9.2.2.51 | UE Positioning Capability..... | 101 | +| 9.2.2.52 | Response Time..... | 104 | +| 9.2.2.53 | Positioning Priority..... | 104 | +| 9.2.2.54 | Client Type..... | 104 | +| 9.2.2.55 | Positioning Method..... | 104 | +| 9.2.2.56 | U-TDOA Bit Count..... | 106 | +| 9.2.2.57 | U-TDOA Time Interval..... | 106 | +| 9.2.2.58 | Additional Method Type..... | 106 | +| 9.2.2.59 | UE Positioning OTDOA Assistance Data..... | 106 | +| 9.2.2.60 | UL TrCH information..... | 109 | +| 9.2.2.61 | Semi-static Transport Format Information..... | 109 | +| 9.2.2.62 | Environment Characterisation..... | 110 | +| 9.2.2.63 | Chip Offset..... | 110 | +| 9.2.2.64 | Frame Offset..... | 110 | +| 9.2.2.65 | Position Data..... | 110 | +| 9.2.2.66 | Transmission Gap Pattern Sequence Information..... | 114 | +| 9.2.2.67 | Active Pattern Sequence Information..... | 115 | +| 9.2.2.68 | CFN..... | 115 | +| 9.2.2.69 | Positioning Response Time..... | 115 | +| 9.2.2.70 | Reference Cell Position..... | 116 | +| 9.2.2.71 | UE Positioning IPDL Parameters..... | 116 | +| 9.2.2.72 | Burst Mode Parameters..... | 116 | + +| | | | +|------------|------------------------------------------------------------------------------|-----| +| 9.2.2.73 | SFN-SFN Relative Time Difference..... | 117 | +| 9.2.2.74 | UTDOA Group..... | 117 | +| 9.2.2.75 | Maximum Set of E-DPDCHs..... | 118 | +| 9.2.2.76 | Puncture Limit..... | 118 | +| 9.2.2.77 | E-DCH Transport Format Combination Set Information (E-TFCS Information)..... | 118 | +| 9.2.2.78 | Reference E-TFCI Power Offset..... | 119 | +| 9.2.2.79 | E-TTI..... | 119 | +| 9.2.2.80 | E-DPCCH Power Offset..... | 119 | +| 9.2.2.81 | Cell Parameter ID..... | 119 | +| 9.2.2.82 | TFCI Coding..... | 119 | +| 9.2.2.83 | Repetition Length..... | 120 | +| 9.2.2.84 | Repetition Period..... | 120 | +| 9.2.2.85 | TDD DPCH Offset..... | 120 | +| 9.2.2.86 | UL Timeslot Information..... | 120 | +| 9.2.2.87 | Time Slot..... | 121 | +| 9.2.2.88 | Midamble Shift And Burst Type..... | 121 | +| 9.2.2.89 | TFCI Presence..... | 122 | +| 9.2.2.90 | TDD UL Code Information..... | 122 | +| 9.2.2.91 | TDD Channelisation Code..... | 123 | +| 9.2.2.92 | Special Burst Scheduling..... | 123 | +| 9.2.2.93 | Max PRACH Midamble Shift..... | 123 | +| 9.2.2.94 | PRACH Midamble..... | 123 | +| 9.2.2.95 | USCH Parameters..... | 123 | +| 9.2.2.96 | USCH Scheduling Offset..... | 124 | +| 9.2.2.97 | Include Velocity..... | 124 | +| 9.2.2.98 | Velocity Estimate..... | 124 | +| 9.2.2.99 | Horizontal Speed and Bearing..... | 125 | +| 9.2.2.100 | Vertical Velocity..... | 126 | +| 9.2.2.101 | GPS Positioning Instructions..... | 126 | +| 9.2.2.102 | UE Position Estimate Info..... | 127 | +| 9.2.2.103 | UTRAN-GPS Reference Time..... | 128 | +| 9.2.2.104 | UTRAN-GPS Reference Time Result..... | 129 | +| 9.2.2.105 | T UTRAN-GPS Drift Rate..... | 129 | +| 9.2.2.106 | Periodic Position Calculation Info..... | 129 | +| 9.2.2.107 | Periodic Location Info..... | 130 | +| 9.2.2.108 | Amount of Reporting..... | 130 | +| 9.2.2.109 | Measurement Instructions Used..... | 130 | +| 9.2.2.110 | RRC State Change..... | 130 | +| 9.2.2.111 | Periodic Position Termination Cause..... | 130 | +| 9.2.2.112 | Requested Cell-ID Measurements..... | 131 | +| 9.2.2.113 | DGANSS Corrections..... | 133 | +| 9.2.2.114 | GANSS Almanac and Satellite Health..... | 135 | +| 9.2.2.115 | GANSS Clock Model..... | 140 | +| 9.2.2.115A | GANSS Additional Clock Models..... | 141 | +| 9.2.2.116 | GANSS Ionospheric Model..... | 143 | +| 9.2.2.116A | GANSS Additional Ionospheric Model..... | 144 | +| 9.2.2.117 | GANSS Measured Results..... | 144 | +| 9.2.2.118 | GANSS Navigation Model..... | 146 | +| 9.2.2.118A | GANSS Additional Navigation Models..... | 147 | +| 9.2.2.119 | GANSS Orbit Model..... | 147 | +| 9.2.2.119A | GANSS Additional Orbit Models..... | 148 | +| 9.2.2.120 | GANSS Positioning Instructions..... | 155 | +| 9.2.2.121 | GANSS-UTRAN Time Relationship Uncertainty..... | 157 | +| 9.2.2.122 | GANSS Real Time Integrity..... | 157 | +| 9.2.2.123 | GANSS Reference Measurement Information..... | 158 | +| 9.2.2.124 | GANSS Reference Time..... | 160 | +| 9.2.2.125 | GANSS Time Model..... | 161 | +| 9.2.2.125A | GANSS Additional Time Models..... | 161 | +| 9.2.2.126 | GANSS UTC Model..... | 161 | +| 9.2.2.126A | GANSS Additional UTC Models..... | 162 | +| 9.2.2.127 | GANSS Time Indicator..... | 165 | + +| | | | +|------------|---------------------------------------------------------------------------------------------------|-----| +| 9.2.2.127A | GANSS Data Bit Assistance..... | 165 | +| 9.2.2.128 | Additional GPS Assistance Data Required..... | 166 | +| 9.2.2.129 | Additional GANSS Assistance Data Required..... | 167 | +| 9.2.2.130 | GANSS ID..... | 169 | +| 9.2.2.131 | GANSS Signal ID..... | 169 | +| 9.2.2.131a | GANSS Signal IDs..... | 169 | +| 9.2.2.132 | GPS Reference Time Uncertainty..... | 170 | +| 9.2.2.133 | GANSS Earth Orientation Parameters..... | 171 | +| 9.2.2.134 | SBAS ID..... | 171 | +| 9.2.2.135 | GANSS Auxiliary Information..... | 171 | +| 9.2.2.136 | UTRAN-GANSS Reference Time Result..... | 172 | +| 9.2.2.137 | GANSS Additional Ionospheric Model Request..... | 173 | +| 9.2.2.138 | GANSS Earth Orientation Parameters Request..... | 173 | +| 9.2.2.139 | Support for Non-Native Assistance Choices Indication..... | 173 | +| 9.2.2.140 | Position Data UE-Based..... | 173 | +| 9.2.2.141 | GANSS Code Phase Ambiguity Extension..... | 173 | +| 9.2.2.142 | GANSS Integer Code Phase Extension..... | 174 | +| 9.2.2.143 | GANSS Carrier-Phase Measurement Requested..... | 174 | +| 9.2.2.144 | GANSS Multi-frequency Measurement Requested..... | 174 | +| 9.2.2.145 | GANSS Additional Ionospheric Model Required..... | 175 | +| 9.2.2.146 | GANSS Earth Orientation Parameters Required..... | 175 | +| 9.2.2.147 | GANSS Additional Navigation Models Required..... | 175 | +| 9.2.2.148 | GANSS Additional UTC Models Required..... | 175 | +| 9.2.2.149 | GANSS Auxiliary Information Required..... | 175 | +| 9.2.2.150 | SBAS IDs..... | 175 | +| 9.2.2.151 | GANSS Additional Assistance Data Choices..... | 176 | +| 9.2.2.152 | Cell-ID Measured Results Sets..... | 176 | +| 9.2.2.153 | OTDOA Reference Cell Info SAS-centric mode..... | 176 | +| 9.2.2.154 | DGNSS Validity Period..... | 176 | +| 9.2.2.155 | IRAT Measured Results Info List..... | 177 | +| 9.2.2.156 | GERAN Cell Global Identity..... | 178 | +| 9.2.2.157 | GSM BSIC..... | 178 | +| 9.2.2.158 | IMSI..... | 178 | +| 9.2.2.159 | IMEI..... | 179 | +| 9.2.2.160 | BDS Ionospheric Grid Model..... | 179 | +| 9.2.2.161 | DBDS Correction Information..... | 179 | +| 9.2.2.162 | Additional Positioning Measured Results..... | 180 | +| 9.3 | Message and Information Element Abstract Syntax (with ASN.1)..... | 183 | +| 9.3.0 | General..... | 183 | +| 9.3.1 | Usage of private message mechanism for non-standard use..... | 183 | +| 9.3.2 | Elementary Procedure Definitions..... | 183 | +| 9.3.3 | PDU Definitions..... | 189 | +| 9.3.4 | Information Element Definitions..... | 204 | +| 9.3.5 | Common Definitions..... | 306 | +| 9.3.6 | Constant Definitions..... | 307 | +| 9.3.7 | Container Definitions..... | 311 | +| 9.4 | Message Transfer Syntax..... | 314 | +| 10 | Handling of Unknown, Unforeseen and Erroneous Protocol Data..... | 315 | +| 10.1 | General..... | 315 | +| 10.2 | Transfer Syntax Error..... | 315 | +| 10.3 | Abstract Syntax Error..... | 316 | +| 10.3.1 | General..... | 316 | +| 10.3.2 | Criticality Information..... | 316 | +| 10.3.3 | Presence Information..... | 317 | +| 10.3.4 | Not comprehended IE/IE group..... | 317 | +| 10.3.4.1 | Procedure Code..... | 317 | +| 10.3.4.1A | Type of Message..... | 318 | +| 10.3.4.2 | IEs other than the Procedure Code and Type of Message..... | 318 | +| 10.3.5 | Missing IE or IE group..... | 319 | +| 10.3.6 | IEs or IE groups received in wrong order or with too many occurrences or erroneously present..... | 320 | +| 10.4 | Logical Error..... | 321 | + +10.5 Exceptions.....321 + +**Annex A (informative): Guidelines for Usage of the Criticality Diagnostics IE.....323** + +A.1 EXAMPLE MESSAGE Layout.....323 + +A.2 Example on a Received EXAMPLE MESSAGE.....323 + +A.3 Content of Criticality Diagnostics.....325 + +A.3.1 Example 1.....325 + +A.3.2 Example 2.....327 + +A.3.3 Example 3.....329 + +A.3.4 Example 4.....331 + +A.3.5 Example 5.....333 + +A.4 ASN.1 of EXAMPLE MESSAGE.....334 + +Annex B (informative): Change History.....338 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the *Positioning Calculation Application Part (PCAP)* between the Radio Network Controller (RNC) and the Stand-Alone SMLC (SAS). It fulfills the RNC-SAS communication requirements specified in TS 25.305 [6] and thus defines the Iupc interface and its associated signaling procedures. + +# --- 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] Void +- [2] Void +- [3] 3GPP TS 25.452: "UTRAN Iupc interface signalling transport". +- [4] 3GPP TS 25.331: "Radio Resource Control (RRC) Protocol Specification". +- [5] Void +- [6] 3GPP TS 25.305: "Stage 2 functional specification of UE positioning in UTRAN". +- [7] ITU-T Recommendation X.680 (2002-07): "Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation". +- [8] ITU-T Recommendation X.681 (2002-07): "Information technology - Abstract Syntax Notation One (ASN.1): Information object specification". +- [9] ITU-T Recommendation X.691 (2002-07): "Information technology - ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)". +- [10] ICD-GPS-200: (12 April 2000) "Navstar GPS Space Segment/Navigation User Interface". +- [11] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)". +- [12] 3GPP TR 25.921 (version 7.0.0): "Guidelines and principles for protocol description and error handling". +- [13] 3GPP TS 25.133: "Requirements for support of Radio Resource management (FDD)". +- [14] 3GPP TS 25.123: "Requirements for support of Radio Resource management (TDD)". +- [15] 3GPP TS 22.071: "Location Services (LCS); Service Description; Stage1". +- [16] 3GPP TS 25.212: "Multiplexing and Channel Coding (FDD)". +- [17] 3GPP TS 25.213: "Spreading and Modulation (FDD)". +- [18] 3GPP TS 25.223: "Spreading and Modulation (TDD)". +- [19] 3GPP TS 25.221: "Physical channels and mapping of transport channels onto physical channels (TDD)". +- [20] 3GPP TS 25.101: "User Equipment (UE) radio transmission and reception (FDD)". + +- [21] 3GPP TS 25.102: "UE radio transmission and reception (TDD)". +- [22] Galileo OS Signal in Space ICD (OS SIS ICD), Issue 1.2, February 2014, European Union. +- [23] IS-GPS-200, Revision D, Navstar GPS Space Segment/Navigation User Interfaces, March 7th, 2006. +- [24] IS-GPS-705, Navstar GPS Space Segment/User Segment L5 Interfaces, September 22, 2005. +- [25] IS-GPS-800, Navstar GPS Space Segment/User Segment L1C Interfaces, March 31, 2008. +- [26] Specification for the Wide Area Augmentation System (WAAS), US Department of Transportation, Federal Aviation Administration, DTFA01-96-C-00025, 2001. +- [27] IS-QZSS, Quasi Zenith Satellite System Navigation Service Interface Specifications for QZSS, Ver.1.0, June 17, 2008. +- [28] Global Navigation Satellite System GLONASS Interface Control Document, Version 5, 2002. +- [29] 3GPP TS 45.005: "Radio transmission and reception". +- [30] 3GPP TS 45.008: "Radio subsystem link control". +- [31] Void +- [32] 3GPP TS 25.413: "UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling". +- [33] BDS-SIS-ICD-2.0: "BeiDou Navigation Satellite System Signal In Space Interface Control Document Open Service Signal (Version 2.0)", December 2013. + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**Stand-Alone SMLC (SAS):** logical node that interconnects to the RNC over the Iupc interface via the PCAP protocol. An SAS performs the following procedures: + +- provide GNSS (i.e. GPS or GANSS (e.g. Galileo)) related data to the RNC; +- performs the position calculation function based upon UE Positioning measurement data; +- in SAS centric mode, selects the positioning method and controls the positioning procedure. + +**Elementary Procedure:** PCAP consists of Elementary Procedures (EPs). + +An Elementary Procedure is a unit of interaction between the RNC and the SAS. An EP consists of an initiating message and possibly a response message. Two kinds of EPs are used: + +- **Class 1:** Elementary Procedures with response (success or failure). +- **Class 2:** Elementary Procedures without response. + +For Class 1 EPs, the types of responses can be as follows: + +Successful: + +- - A signalling message explicitly indicates that the elementary procedure successfully completed with the receipt of the response. + +Unsuccessful: + +- - A signalling message explicitly indicates that the EP failed. + +Class 2 EPs are considered always successful. + +**Information Exchange Context:** Information Exchange Context is created by the first Information Exchange Initiation Procedure initiated by the RNC and requested from the SAS. + +The Information Exchange Context is deleted after the Information Exchange Termination or the Information Exchange Failure procedure when there is no more Information Exchange to be provided by the RNC to the SAS. The Information Exchange Context is identified by an SCCP connection as, for Information Exchanges, only the connection oriented mode of the signalling bearer is used. + +**Positioning Initiation Context:** In the SAS centric mode of operation each positioning request is assigned a unique logical connection identity, i.e., SCCP Source and Destination Local Reference numbers. + +**RNC Centric Mode of Operation:** The RNC determines, initiates and controls the positioning method to be used for each positioning request. + +**SAS Centric Mode of Operation:** The SAS determines, initiates and controls the positioning method to be used for each positioning request. + +**Positioning Event:** The activity associated with the positioning of a UE resulting from the reception of UE positioning request from the CN. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|---------|----------------------------------------------------------------------------------------------| +| A-GANSS | Assisted GANSS | +| A-GPS | Assisted GPS | +| ASN.1 | Abstract Syntax Notation One | +| BDS | BeiDou Navigation Satellite System | +| CN | Core Network | +| CRNC | Controlling RNC | +| DBDS | Differential BDS | +| DGANSS | Differential GANSS | +| DGPS | Differential GPS | +| ECEF | Earth-Centered, Earth-Fixed | +| EGNOS | European Geostationary Navigation Overlay Service | +| EP | Elementary Procedure | +| FDD | Frequency Division Duplex | +| GAGAN | GPS Aided Geo Augmented Navigation | +| GANSS | Galileo and Additional Navigation Satellite Systems | +| GLONASS | GLObal'naya NAVigatsionnaya Sputnikovaya Sistema (Engl.: Global Navigation Satellite System) | +| GNSS | Global Navigation Satellite System | +| GPS | Global Positioning System | +| ICD | Interface Control Document | +| MBS | Metropolitan Beacon System | +| MSAS | Multi-functional Satellite Augmentation System | +| OTDOA | Observed Time Difference Of Arrival | +| PCAP | Positioning Calculation Application Part | +| PRC | Pseudorange Correction | +| QZSS | Quasi-Zenith Satellite System | +| RNC | Radio Network Controller | +| RNS | Radio Network Subsystem | +| RRC | Radio Resource Control | +| SAS | Stand-Alone SMLC | +| SBAS | Satellite Based Augmentation System | +| SCCP | Signalling Connection Control Part | +| SIB | System Information Block | +| SMLC | Serving Mobile Location Center | +| SRNC | Serving RNC | +| SV | Space Vehicle | +| TDD | Time Division Duplex | +| TOD | Time of Day | +| TOW | Time of Week | +| UE | User Equipment | + +| | | +|--------|--------------------------------------------| +| UTC | Universal Coordinated Time | +| U-TDOA | Uplink Time Difference Of Arrival | +| UTRAN | Universal Terrestrial Radio Access Network | +| WAAS | Wide Area Augmentation System | +| WLAN | Wireless Local Area Network | + +# 4 General + +## 4.1 Procedure Specification Principles + +The principle for specifying the procedure logic is to specify the functional behaviour of the SAS exactly and completely. The RNC functional behaviour is left unspecified. + +The following specification principles have been applied for the procedure text in clause 8: + +- The procedure text discriminates between: + - 1) Functionality which "shall" be executed: + - - The procedure text indicates that the receiving node "shall" perform a certain function Y under a certain condition. If the receiving node supports procedure X but cannot perform functionality Y requested in the REQUEST message of a Class 1 EP, the receiving node shall respond with the message used to report unsuccessful outcome for this procedure, containing an appropriate cause value. + - 2) Functionality which "shall, if supported" be executed: + - - The procedure text indicates that the receiving node "shall, if supported," perform a certain function Y under a certain condition. If the receiving node supports procedure X, but does not support functionality Y, the receiving node shall proceed with the execution of the EP, possibly informing the requesting node about the not supported functionality. +- Any required inclusion of an optional IE in a response message is explicitly indicated in the procedure text. If the procedure text does not explicitly indicate that an optional IE shall be included in a response message, the optional IE shall not be included. + +## 4.2 Forwards and Backwards Compatibility + +The forwards and backwards compatibility of the protocol is assured by mechanism where all current and future messages, and IEs or groups of related IEs, include Id and criticality fields that are coded in a standard format that will not be changed in the future. These parts can always be decoded regardless of the standard version. + +## 4.3 Specification Notations + +For the purposes of the present document, the following notations apply: + +- | | | +|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [FDD] | This tagging of a word indicates that the word preceding the tag "[FDD]" applies only to FDD. This tagging of a heading indicates that the heading preceding the tag "[FDD]" and the section following the heading applies only to FDD. | +| [TDD] | This tagging of a word indicates that the word preceding the tag "[TDD]" applies only to TDD, including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[TDD]" and the section following the heading applies only to TDD, including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. | +| [3.84Mcps TDD] | This tagging of a word indicates that the word preceding the tag "[3.84Mcps TDD]" applies only to 3.84Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[3.84Mcps TDD]" and the section following the heading applies only to 3.84Mcps TDD. | + +| | | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [1.28Mcps TDD] | This tagging of a word indicates that the word preceding the tag "[1.28Mcps TDD]" applies only to 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[1.28Mcps TDD]" and the section following the heading applies only to 1.28Mcps TDD. | +| [7.68Mcps TDD] | This tagging of a word indicates that the word preceding the tag "[7.68Mcps TDD]" applies only to 7.68Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[7.68Mcps TDD]" and the section following the heading applies only to 7.68Mcps TDD. | +| [FDD - ...] | This tagging indicates that the enclosed text following the "[FDD - " applies only to FDD. Multiple sequential paragraphs applying only to FDD are enclosed separately to enable insertion of TDD specific (or common) paragraphs between the FDD specific paragraphs. | +| [TDD - ...] | This tagging indicates that the enclosed text following the "[TDD - " applies only to TDD, including 7.68 Mcps TDD, 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. Multiple sequential paragraphs applying only to TDD are enclosed separately to enable insertion of FDD specific (or common) paragraphs between the TDD specific paragraphs. | +| [3.84Mcps TDD - ...] | This tagging indicates that the enclosed text following the "[3.84Mcps TDD - " applies only to 3.84Mcps TDD. Multiple sequential paragraphs applying only to 3.84Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 3.84Mcps TDD specific paragraphs. | +| [1.28Mcps TDD - ...] | This tagging indicates that the enclosed text following the "[1.28Mcps TDD - " applies only to 1.28Mcps TDD. Multiple sequential paragraphs applying only to 1.28Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 1.28Mcps TDD specific paragraphs. | +| [7.68Mcps TDD - ...] | This tagging indicates that the enclosed text following the "[7.68Mcps TDD - " applies only to 7.68Mcps TDD. Multiple sequential paragraphs applying only to 7.68Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 7.68Mcps TDD specific paragraphs. | +| Procedure | When referring to an elementary procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. Position Calculation procedure. | +| Message | When referring to a message in the specification the MESSAGE NAME is written with all letters in upper case characters followed by the word "message", e.g. POSITION CALCULATION REQUEST message. | +| IE | When referring to an information element (IE) in the specification the Information Element Name is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation "IE", e.g. Request Type IE. | +| Value of an IE | When referring to the value of an information element (IE) in the specification the "Value" is written as it is specified in clause 9.2 enclosed by quotation marks, e.g. "Abstract Syntax Error (Reject)" or "Geographical Coordinates ". | + +# 5 PCAP Services + +PCAP provides the signalling services between RNC and SAS that are required to fulfill the PCAP functions described in clause 7. PCAP services are categorized as follows: + +1. Position Calculation Service: They are related to a single UE and involve the transfer of UE Positioning measurement data and UE position estimate data over the Iupc interface between the SRNC and the SAS. They utilise connectionless signalling transport provided by the Iupc signalling bearer. +2. Information Exchange Service: They involve the transfer of GPS or GANSS related data over the Iupc interface between the RNC and the SAS on demand, on modification, or at regular intervals. They utilise connection-oriented signalling transport provided by the Iupc signalling bearer. + +3. SAS Centric Position Service: They are related to the capability of the SAS to determine the positioning method used for individual positioning events. In this case the SRNC may allow A-GPS, A-GNSS, OTDOA, Cell ID and U-TDOA positioning events for a single UE to be originated by the SAS via PCAP messages. They utilise connection-oriented signalling transport provided by the Iupc signalling bearer. + +# 6 Services Expected from Signalling Transport + +Signalling transport (TS 25.452 [3]) shall provide the following service for the PCAP. + +1. Connection oriented data transfer service. This service is supported by a signalling connection between the RNC and the SAS. It shall be possible to dynamically establish and release signalling connections based on the need. Each point-to-point operation shall have its own signalling connection. The signalling connection shall provide in sequence delivery of PCAP messages. PCAP shall be notified if the signalling connection breaks. +2. Connectionless data transfer service. PCAP shall be notified in case a PCAP message did not reach the intended peer PCAP entity. + +# 7 Functions of PCAP + +PCAP has the following functions: + +- Position Calculation. This function enables the SRNC to interact with an SAS in the process of performing a position estimate of a UE. +- Information Exchange. This function enables the RNC to obtain GPS or GANSS related data from an SAS. +- Reporting of General Error Situations. This function allows reporting of general error situations for which function specific error messages have not been defined. +- SAS Centric Position. This function enables the SRNC to interact with an SAS in the process of performing a position estimate of a UE. + +The mapping between the above functions and PCAP elementary procedures is shown in the table 1. + +**Table 1: Mapping between functions and PCAP elementary procedures** + +| Function | Elementary Procedure(s) | +|---------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Position Calculation | a) Position Calculation
b) Position Parameter Modification
c) Abort | +| Information Exchange | a) Information Exchange Initiation
b) Information Reporting
c) Information Exchange Termination
d) Information Exchange Failure | +| Reporting of General Error Situations | a) Error Indication | +| SAS Centric Position | a) Position Initiation
b) Position Activation
c) Position Parameter Modification
d) Abort
e) Position Periodic Report
f) Position Periodic Result
g) Position Periodic Termination | + +# 8 PCAP Procedures + +## 8.1 Elementary Procedures + +In the following tables, all EPs are divided into class 1 and class 2 EPs (see clause 3.1 for explanation of the different classes). + +**Table 2: Class 1** + +| Elementary Procedure | Initiating Message | Successful Outcome | Unsuccessful Outcome | +|---------------------------------|-----------------------------------------|------------------------------------------|-----------------------------------------| +| | | Response message | Response message | +| Position Calculation | POSITION CALCULATION REQUEST | POSITION CALCULATION RESPONSE | POSITION CALCULATION FAILURE | +| Information Exchange Initiation | INFORMATION EXCHANGE INITIATION REQUEST | INFORMATION EXCHANGE INITIATION RESPONSE | INFORMATION EXCHANGE INITIATION FAILURE | +| Position Initiation | POSITION INITIATION REQUEST | POSITION INITIATION RESPONSE | POSITION INITIATION FAILURE | +| Position Activation | POSITION ACTIVATION REQUEST | POSITION ACTIVATION RESPONSE | POSITION ACTIVATION FAILURE | + +**Table 3: Class 2** + +| Elementary Procedure | Message | +|----------------------------------|------------------------------------------| +| Information Reporting | INFORMATION REPORT | +| Information Exchange Termination | INFORMATION EXCHANGE TERMINATION REQUEST | +| Information Exchange Failure | INFORMATION EXCHANGE FAILURE INDICATION | +| Error Indication | ERROR INDICATION | +| Position Parameter Modification | POSITION PARAMETER MODIFICATION | +| Abort | ABORT | +| Position Periodic Report | POSITION PERIODIC REPORT | +| Position Periodic Result | POSITION PERIODIC RESULT | +| Position Periodic Termination | POSITION PERIODIC TERMINATION | + +## 8.2 Position Calculation + +### 8.2.1 General + +The purpose of the Position Calculation procedure is to enable an SRNC to query an SAS for a position estimate of a UE. The procedure uses connectionless signalling. + +### 8.2.2 Successful Operation + +![Sequence diagram showing the successful operation of the Position Calculation procedure. The SRNC sends a POSITION CALCULATION REQUEST message to the SAS, and the SAS responds with a POSITION CALCULATION RESPONSE message.](96b0240f56d14453b5da05ec30fd5c6e_img.jpg) + +``` + +sequenceDiagram + participant SRNC + participant SAS + Note left of SRNC: + SRNC->>SAS: POSITION CALCULATION REQUEST + Note right of SAS: + SAS-->>SRNC: POSITION CALCULATION RESPONSE + Note left of SRNC: + +``` + +Sequence diagram showing the successful operation of the Position Calculation procedure. The SRNC sends a POSITION CALCULATION REQUEST message to the SAS, and the SAS responds with a POSITION CALCULATION RESPONSE message. + +**Figure 1: Position Calculation procedure, Successful Operation** + +The procedure is initiated with a POSITION CALCULATION REQUEST message sent from the SRNC to the SAS. When the SAS receives the POSITION CALCULATION REQUEST message, it shall calculate the UE position and, if + +supported and requested, velocity based on the provided measurement data. This procedure may be repeated by the SRNC as needed for periodic location. If the POSITION CALCULATION REQUEST message is part of periodic location, this message may include the *Periodic Position Calculation Info* IE to enable the SAS to better fulfill future such requests. + +If the *Initial UE Position Estimate* IE is included in the POSITION CALCULATION REQUEST message, the SAS shall use this value for the calculation of the UE Position Estimate in case of A-GPS or A-GNSS positioning methods are used. The SAS may use this value for the calculation of the UE Position when any other methods are used. + +If the *Cell-ID Measured Results Sets* IE is included in the POSITION CALCULATION REQUEST message and both of the *Round Trip Time Info* IE and the *Round Trip Time Info With Type 1* IE are included in the *Cell-ID Measured Results Info List* IE, the SAS shall use the *Round Trip Time Info* IE. + +If the *Horizontal Accuracy Code* IE and possibly the *Vertical Accuracy Code* IE are included in the POSITION CALCULATION REQUEST message, the SAS shall use these values in order to assess whether the resulting position estimation fulfills the requested accuracy. + +If the *SAS Response Time* IE is included in the POSITION CALCULATION REQUEST message, the SAS shall send a POSITION CALCULATION RESPONSE message within the indicated time after reception of the POSITION CALCULATION REQUEST message. + +If the *Include Velocity* IE is set to "requested" in the POSITION CALCULATION REQUEST message, the SAS shall include the *Velocity Estimate* IE, if available, in the POSITION CALCULATION RESPONSE message. + +If a *GNSS Measured Results* IE is included in the POSITION CALCULATION REQUEST message and does not contain the *GNSS Time ID* IE, the SAS shall assume that the corresponding GNSS timing refers to the "Galileo" timing. + +The *GNSS Measured Results* IE contains one or several *GNSS Generic Measurement Information* IEs, each of them associated with a given GNSS: + +- If a *GNSS Generic Measurement Information* IE does not contain the *GNSS ID* IE, the SAS shall assume that the associated GNSS is "Galileo". +- If a *GNSS Generic Measurement Information* IE associated with a particular GNSS does not contain the *GNSS Signal ID* IE, the SAS shall assume the default value as defined in TS 25.331 [4]. +- If a *GNSS Generic Measurement Information* IE does not contain the *GNSS Code Phase Ambiguity* IE and the *GNSS Code Phase Ambiguity Extension* IE, the SAS shall assume the value "1" (ms). +- If the *GNSS Integer Code Phase* IE and the *GNSS Integer Code Phase Extension* IE associated to a given satellite (identified by the *Sat ID* IE value) is not present within the *GNSS Measurement Parameters* IE, the SAS shall use the default "1" (ms) for the GNSS Code Phase Ambiguity value in order to compute the value of the Total Code Phase (as defined in TS 25.331 [4]) for the related satellite, whatever the value of the *GNSS Code Phase Ambiguity* IE. + +If an optional *Cell-ID IRAT Measured Results Sets* IE is included in the POSITION CALCULATION REQUEST message, the SAS shall, if supported, use this value for the calculation of the UE Position Estimate in case of RFPM positioning method is used. The SAS may use this value for the calculation of the UE Position when any other methods are used. + +If the *IMSI* IE, or *IMEI* IE is included in the POSITION CALCULATION REQUEST message, the SAS may save these IEs for use in location session correlation. + +#### Response Message: + +If the SAS was able to calculate the position estimate, it shall respond with a POSITION CALCULATION RESPONSE message. + +Whenever one of the geographic area shapes *Ellipsoid point with uncertainty Ellipse* IE, *Ellipsoid point with altitude and uncertainty Ellipsoid* IE or *Ellipsoid Arc* IE is reported, the *Confidence* IE shall indicate the probability that the UE is located within the uncertainty region of the shape. The value of the *Confidence* IE shall be in the interval of "1" to "100". + +If at least the *Horizontal Accuracy Code* IE was included in the POSITION CALCULATION REQUEST message and the calculated position estimate fulfils the requested accuracy, the *Accuracy Fulfilment Indicator* IE with the value "requested accuracy fulfilled" shall be included in the POSITION CALCULATION RESPONSE message. If the calculated position estimate does not fulfil the requested accuracy, the *Accuracy Fulfilment Indicator* IE with the value "requested accuracy not fulfilled" shall be included in the POSITION CALCULATION RESPONSE message. + +### 8.2.3 Unsuccessful Operation + +![Sequence diagram showing an unsuccessful position calculation procedure. The SRNC sends a POSITION CALCULATION REQUEST to the SAS, and the SAS responds with a POSITION CALCULATION FAILURE.](9cd90f495b95ad2116ff780248c26d95_img.jpg) + +``` + +sequenceDiagram + participant SRNC + participant SAS + Note left of SRNC: + SRNC->>SAS: POSITION CALCULATION REQUEST + Note right of SAS: + SAS-->>SRNC: POSITION CALCULATION FAILURE + Note left of SRNC: + +``` + +Sequence diagram showing an unsuccessful position calculation procedure. The SRNC sends a POSITION CALCULATION REQUEST to the SAS, and the SAS responds with a POSITION CALCULATION FAILURE. + +**Figure 2: Position Calculation procedure, Unsuccessful Operation** + +If the SAS is unable to perform the position estimate for any reason, it shall return a POSITION CALCULATION FAILURE message to the SRNC. + +Typical cause values are: + +- Invalid reference information; +- Position calculation error: invalid GPS, Galileo, GLONASS, BDS or GANSS measured results; +- Initial UE Position Estimate missing; +- Processing Overload; +- Hardware Failure; +- O&M Intervention; +- Invalid U-TDOA measured results; +- U-TDOA positioning method not supported; +- U-TDOA positioning method not supported in specified UTRAN cell; +- SAS unable to perform U-TDOA positioning within Response Time. + +### 8.2.4 Abnormal Conditions + +If the *Vertical Accuracy Code* IE is included and the *Horizontal Accuracy Code* IE is not included in the POSITION CALCULATION REQUEST message, the SAS shall reject the procedure. + +If the *RRC State* included in the *UTDOA Group* IE is indicated as being *CELL\_DCH* in the POSITION CALCULATION REQUEST message and [FDD - neither the *DCH Information* IE nor the *E-DPCH Information* IE] [TDD – no *DCH Information* IE] is included, the SAS shall reject the procedure using the POSITION CALCULATION FAILURE message. + +If the *GPS Measured Results* IE is included in the POSITION CALCULATION REQUEST message but the *Initial UE Position Estimate* IE is not, the SAS shall return the POSITION CALCULATION FAILURE message to the SRNC. + +If the *GANSS Measured Results* IE is included in the POSITION CALCULATION REQUEST message but the *Initial UE Position Estimate* IE is not, the SAS shall return the POSITION CALCULATION FAILURE message to the SRNC. + +If neither of the *GPS Measurement Results* IE, the *Cell-ID Measured Results Sets* IE, the *OTDOA Measurement Group* IE nor the *GANSS Measured Results* IE is included in the POSITION CALCULATION REQUEST message, the SAS shall return the POSITION CALCULATION FAILURE message to the SRNC. + +## 8.3 Information Exchange Initiation + +### 8.3.1 General + +This procedure is used by a RNC to request the initiation of an information exchange with a SAS. + +This procedure uses the signalling bearer connection for the Information Exchange Context. + +### 8.3.2 Successful Operation + +![Sequence diagram showing the Information Exchange Initiation procedure. The RNC sends an INFORMATION EXCHANGE INITIATION REQUEST to the SAS, and the SAS responds with an INFORMATION EXCHANGE INITIATION RESPONSE.](04f51626e2e10a16e3eb2c4b33cb2742_img.jpg) + +``` + +sequenceDiagram + participant RNC + participant SAS + Note left of RNC: + RNC->>SAS: INFORMATION EXCHANGE INITIATION REQUEST + Note right of SAS: + SAS-->>RNC: INFORMATION EXCHANGE INITIATION RESPONSE + Note left of RNC: + +``` + +Sequence diagram showing the Information Exchange Initiation procedure. The RNC sends an INFORMATION EXCHANGE INITIATION REQUEST to the SAS, and the SAS responds with an INFORMATION EXCHANGE INITIATION RESPONSE. + +**Figure 3: Information Exchange Initiation procedure, Successful Operation** + +The procedure is initiated with an INFORMATION EXCHANGE INITIATION REQUEST message sent from RNC to SAS. + +If the *Information Type* IE is set to "Implicit", the SAS is responsible for selecting the type of assistance data. + +Upon reception, the SAS shall provide the requested information according to the parameters given in the request. Unless specified below, the meaning of the parameters are given in other specifications. + +If the *Information Exchange Object Type* IE is set to "Cell-ID Measured Results Sets" the SAS shall use the "Cell-ID Measured Results Info List" for obtaining an initial UE position estimate. + +If the *GANSS-UTRAN Time Relationship Uncertainty* IE included in the INFORMATION EXCHANGE INITIATION REQUEST message does not contain the *GANSS ID* IE, the SAS shall assume that the *GANSS-UTRAN Time Relationship Uncertainty* IE is associated with "Galileo". + +If the *Information Type* IE is set to "Explicit" and an *Explicit Information Item* IE is set to "GANSS Common Data", at least one of the GANSS Reference Time, GANSS Ionosphere Model, GANSS Reference Location, GANSS Additional Ionospheric Model, or GANSS Earth Orientation Parameters types shall be requested. + +If the *Information Type* IE is set to "Explicit" and an *Explicit Information Item* IE is set to "GANSS Generic Data", at least one of the *GANSS Real Time Integrity*, *GANSS Data Bit Assistance*, *DGANSS Corrections*, *GANSS Almanac and Satellite Health*, *GANSS Reference Measurement Information*, *GANSS UTC Model*, *GANSS Time Model GNSS-GNSS*, *GANSS Navigation Model*, *GANSS Additional Navigation Models*, *GANSS Additional UTC Models*, *GANSS Auxiliary Information*, *DBDS Corrections*, or *BDS Ionospheric Grid ModelRequest* IEs shall be present in each *GANSS Generic Data Item* IE associated with a given GANSS. + +- If the *GANSS Generic Data Item* IE does not contain the *GANSS ID* IE, the SAS shall assume that the corresponding GANSS is "Galileo". + +#### Information Report Characteristics: + +The *Information Report Characteristics* IE indicates how the reporting of the information shall be performed. + +If the *Information Report Characteristics* IE is set to "On-Demand", the SAS shall report the requested information immediately. + +If the *Information Report Characteristics* IE is set to "Periodic", the SAS shall report the requested information immediately and then shall periodically initiate the Information Reporting procedure for all the requested information, with the requested report frequency. + +If the *Information Report Characteristics* IE is set to "On-Modification", the SAS shall report the requested information immediately if available. If the requested information is not available at the moment of receiving the INFORMATION EXCHANGE INITIATION REQUEST message, but expected to become available after some acquisition time, the SAS shall initiate the Information Reporting procedure when the requested information becomes available. The SAS shall then initiate the Information Reporting procedure in accordance to the following conditions: + +- If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE includes "Almanac and Satellite Health", the SAS shall initiate the Information Reporting procedure for this specific Explicit Information Type when a change in the $t_{oa}$ or $WN_a$ parameter has occurred in almanac/health information for at least one visible satellite. +- If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE includes "UTC Model", the SAS shall initiate the Information Reporting procedure for this specific Explicit Information Type when a change in the $t_{ot}$ or $WN_t$ parameter has occurred in the GPS UTC model. + - - If the *Transmission TOW Indicator* IE is set to "requested", then the SAS shall include the *GPS Transmission TOW* IE in the INFORMATION REPORT message. +- If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE includes "Ionospheric Model", the SAS shall initiate the Information Reporting procedure for this specific Explicit Information Type when a change has occurred in the GPS ionospheric model. + - - If the *Transmission TOW Indicator* IE is set to "requested", then the SAS shall include the *GPS Transmission TOW* IE in the INFORMATION REPORT message. +- If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE includes "Navigation Model", the SAS shall initiate the Information Reporting procedure for this specific Explicit Information Type when a change has occurred in the clock/ephemeris information for at least one visible satellite or in the list of visible satellites. + - - If the *Transmission TOW Indicator* IE is set to "requested", then the SAS shall include the *GPS Transmission TOW* IE in the INFORMATION REPORT message. +- If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE includes "DGPS Corrections", the SAS shall initiate the Information Reporting procedure for this specific Explicit Information Type when a change has occurred in the quality of the DGPS corrections information for at least one visible satellite or in the list of visible satellites. +- If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE includes "Reference Time", the SAS shall initiate the Information Reporting procedure for this specific Explicit Information Type when a change has occurred in the time-of-week assistance information for at least one visible satellite or in the list of visible satellites. +- If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE includes "Acquisition Assistance", the SAS shall initiate the Information Reporting procedure for this specific Explicit Information Type when a change has occurred in acquisition assistance information for at least one visible satellite or in the list of visible satellites. +- If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE includes "Real Time Integrity", the SAS shall initiate the Information Reporting procedure for this specific Explicit Information Type when a change has occurred in the real-time integrity status of at least one visible satellite. +- If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE includes "Almanac and Satellite Health SIB", the SAS shall initiate the Information Reporting procedure for this specific Explicit Information Type when a change has occurred in almanac/health information for at least one visible satellite. + - - If the *Transmission TOW Indicator* IE is set to "requested", then the SAS shall include the *GPS Transmission TOW* IE in the INFORMATION REPORT message. + +- If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "GNSS Generic Data" and includes the *GANSS Almanac and Satellite Health* IE, the SAS shall initiate the Information Reporting procedure for this specific Explicit Information Type when a change in the $T_{oa}$ , $IOD_a$ , or Week Number parameter has occurred in almanac/health information for at least one visible satellite. + - - If the *GANSS Time Indicator* IE is set to "requested", then the SAS shall include the *GANSS Reference Time* IE in the INFORMATION REPORT message. +- If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "GNSS Generic Data" and includes the *GANSS UTC Model* IE, the SAS shall initiate the Information Reporting procedure for this specific Explicit Information Type when a change in the $t_{ot}$ or $WN_t$ parameter has occurred in the GANSS UTC model. + - - If the *GANSS Time Indicator* IE is set to "requested", then the SAS shall include the *GANSS Reference Time* IE in the INFORMATION REPORT message. +- If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "GNSS Generic Data" and includes the *GANSS Additional UTC Models* IE, the SAS shall initiate the Information Reporting procedure for this specific Explicit Information Type when a change in the $t_{ot}$ , $WN_{ot}$ , $WN_t$ , or $N^A$ parameter has occurred in the GANSS Additional UTC model. + - - If the *GANSS Time Indicator* IE is set to "requested", then the SAS shall include the *GANSS Reference Time* IE in the INFORMATION REPORT message. +- If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "GNSS Common Data" and includes the *GANSS Ionosphere Model* IE, the SAS shall initiate the Information Reporting procedure for this specific Explicit Information Type when a change has occurred in the GANSS ionospheric model. +- If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "GNSS Common Data" and includes the *GANSS Additional Ionospheric Model* IE, the SAS shall initiate the Information Reporting procedure for this specific Explicit Information Type when a change has occurred in the GANSS additional ionospheric model. + - - If the *Data ID* IE is set to value "11", then the SAS shall include the *GANSS Additional Ionospheric Model* IE for the area as defined in IS-QZSS [27]. If the *Data ID* IE is set to value "00", then the SAS shall include the *GANSS Additional Ionospheric Model* IE applicable worldwide as defined in IS-QZSS [27]. If the *Data ID* IE is set to value "01", then the SAS shall include the *GANSS Additional Ionospheric Model* IE for the area as defined in BDS-SIS-ICD [33]. +- If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "GNSS Common Data" and includes the *GANSS Earth Orientation Parameters* IE, the SAS shall initiate the Information Reporting procedure for this specific Explicit Information Type when a change in the $t_{EOP}$ parameter has occurred in the GANSS Earth Orientation Parameters. +- If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "GNSS Generic Data" and includes the *GANSS Navigation Model* IE, the SAS shall initiate the Information Reporting procedure for this specific Explicit Information Type when a change has occurred in the ephemeris information for at least one visible satellite or in the list of visible satellites. +- If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "GNSS Generic Data" and includes the *GANSS Additional Navigation Models* IE, the SAS shall initiate the Information Reporting procedure for this specific Explicit Information Type when a change has occurred in the ephemeris information for at least one visible satellite or in the list of visible satellites. +- If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "GNSS Generic Data" and includes the *GANSS Time Model GNSS-GNSS* IE, the SAS shall initiate the Information Reporting procedure for this specific Explicit Information Type when a change has occurred in the time information. + - - If the *GANSS Time Indicator* IE is set to "requested", then the SAS shall include the *GANSS Reference Time* IE in the INFORMATION REPORT message. +- If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "GNSS Generic Data" and includes the *DGANSS Corrections* IE, the SAS shall initiate the Information Reporting procedure for + +this specific Explicit Information Type when a change has occurred in the quality of the DGANSS corrections information for at least one visible satellite or in the list of visible satellites. + +- - If the *GANSS Time Indicator* IE is set to "requested", then the SAS shall include the *GANSS Reference Time* IE in the INFORMATION REPORT message. +- If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "GANSS Generic Data" and includes the *DBDS Corrections* IE, the SAS shall initiate the Information Reporting procedure for this specific Explicit Information Type when a change has occurred in the quality of the DBDS corrections information for at least one visible satellite or in the list of visible satellites. +- If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "GANSS Generic Data" and includes the *BDS Ionospheric Grid Model Request* IE, the SAS shall initiate the Information Reporting procedure for this specific Explicit Information Type when a change has occurred in the BDS ionospheric grid model. +- If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "GANSS Common Data" and includes the *GANSS Reference Time* IE, the SAS shall initiate the Information Reporting procedure for this specific Explicit Information Type when a change has occurred in the time-of-week assistance information for at least one visible satellite or in the list of visible satellites. +- If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "GANSS Generic Data" and includes the *GANSS Reference Measurement Information* IE, the SAS shall initiate the Information Reporting procedure for this specific Explicit Information Type when a change has occurred in acquisition assistance information for at least one visible satellite or in the list of visible satellites. + - - If the *GANSS Time Indicator* IE is set to "requested", then the SAS shall include the *GANSS Reference Time* IE in the INFORMATION REPORT message. +- If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "GANSS Generic Data" and includes the *GANSS Real Time Integrity* IE, the SAS shall initiate the Information Reporting procedure for this specific Explicit Information Type when a change has occurred in the real-time integrity status of at least one visible satellite. + - - If the *GANSS Time Indicator* IE is set to "requested", then the SAS shall include the *GANSS Reference Time* IE in the INFORMATION REPORT message. +- If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "GANSS Generic Data" and includes the *GANSS Auxiliary Information* IE, the SAS shall initiate the Information Reporting procedure for this specific Explicit Information Type when a change in the *Signals Available* or *Channel Number* IEs has occurred in the GANSS Auxiliary Information. + - - If the *GANSS Time Indicator* IE is set to "requested", then the SAS shall include the *GANSS Reference Time* IE in the INFORMATION REPORT message. +- If any of the above *Information Type* IEs becomes temporarily unavailable, the SAS shall initiate the Information Reporting procedure for this specific Information Item by indicating "Information Not Available" in the *Requested Data Value Information* IE. If the Information becomes available again, the SAS shall initiate the Information Reporting procedure for this specific Information. + +If the IMSI IE, or IMEI IE is included in the INFORMATION EXCHANGE INITIATION REQUEST message, the SAS may save these IEs for use in location session correlation. + +#### **Response message:** + +If the SAS is able to determine the information requested by the RNC, it shall respond with the INFORMATION EXCHANGE INITIATION RESPONSE message. The message shall include the same Information Exchange ID that was included in the INFORMATION EXCHANGE INITIATION REQUEST message. When the *Report Characteristics* IE is set to "On Modification" or "Periodic", the INFORMATION EXCHANGE INITIATION RESPONSE message shall contain the *Requested Data Value* IE if the data are available. When the *Report Characteristics* IE is set to "On Demand", the INFORMATION EXCHANGE INITIATION RESPONSE message shall contain the *Requested Data Value* IE. + +When the response message includes data to be reported (see above), the SAS shall include at least one IE in the *Requested Data Value* IE. + +If the *Requested Data Value* IE contains the *GANSS Common Assistance Data* IE, at least one of the *GANSS Reference Time*, *GANSS Ionospheric Model*, *GANSS Reference Location*, *GANSS Additional Ionospheric Model*, or *GANSS Earth Orientation Parameters* IEs shall be present. + +- If the *GANSS Reference Time* IE does not contain the *GANSS Time ID* IE, the corresponding GANSS timing refers to the "Galileo" timing. + +Any *GANSS Generic Assistance Data* IE associated with a given GANSS included in the *Requested Data Value* IE shall contain at least one of the *GANSS Real Time Integrity*, *GANSS Data Bit Assistance*, *DGANSS Corrections*, *GANSS Almanac and Satellite Health*, *GANSS Reference Measurement Information*, *GANSS UTC Model*, *GANSS Time Model*, *GANSS Navigation Model*, *GANSS Additional Time Models*, *GANSS Additional Navigation Models*, *GANSS Additional UTC Models*, *GANSS Auxiliary Information*, *DBDS Correction Information*, or *BDS Ionospheric Grid Model* IEs. + +- If the *GANSS Generic Assistance Data* IE does not contain the *GANSS ID* IE, the corresponding GANSS is "Galileo". +- The *DGANSS Corrections* IE contains one or several *DGANSS Information* IE(s), each of them associated with a GANSS Signal. A *DGANSS Information* IE for a particular GANSS that does not contain the *GANSS Signal ID* IE is by default associated with the default signal defined in TS 25.331 [4]. +- The *GANSS Real Time Integrity* IE contains one or several *Satellite Information* IEs, each of them associated with a satellite and a GANSS Signal. A *Satellite Information* IE for a particular GANSS that does not contain the *Bad GANSS Signal ID* IE is by default associated with all the signals of the corresponding satellite (see OS SIS ICD [22], IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], DTFA01-96-C-00025 [26], IS-QZSS [27], [28], BDS-SIS-ICD [33]). +- The *GANSS Reference Measurement Information* IE is associated with a GANSS Signal. A *GANSS Reference Measurement Information* IE for a particular GANSS that does not contain the *GANSS Signal ID* IE is by default associated with the default signal defined in TS 25.331 [4]. + +If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "GANSS Generic Data" and includes the *GANSS Time Model GNSS-GNSS* IE with exactly one bit set to value "1" in the *GNSS-GNSS Time ext* IE, the SAS shall include the *GANSS Time Model* IE in the *Requested Data Value* IE with the requested time information. + +If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "GANSS Generic Data" and includes the *GANSS Time Model GNSS-GNSS* IE with more than one bit set to value "1" in the *GNSS-GNSS Time ext* IE, the SAS shall include the *GANSS Additional Time Models* IE in *Requested Data Value* IE with the requested time information for each GANSS. + +If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "DGPS Corrections", the SAS shall include the *DGPS Corrections* IE in *Requested Data Value* IE with the *DGNSS Validity Period* IE included, if available. + +If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "DGANSS Corrections", the SAS shall include the *DGANSS Corrections* IE in *Requested Data Value* IE with the *DGNSS Validity Period* IE included, if available. + +If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "Acquisition Assistance ", the SAS shall include the *GPS Acquisition Assistance* IE in *Requested Data Value* IE with the *Azimuth and Elevation* and *Azimuth and Elevation LSB* IEs included, if available, and with the *Confidence* IE included, if available. + +If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "Almanac and Satellite Health", the SAS shall include the *GPS Almanac and Satellite Health* IE in *Requested Data Value* IE with the *Complete Almanac Provided* IE included, if available. + +If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "Reference Time", the SAS shall include the *GPS Reference Time* IE in *Requested Data Value* IE with the *GPS Week Cycle Number* IE included, if available. + +If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "GANSS Almanac and Satellite Health", the SAS shall include the *GANSS Almanac and Satellite Health* IE in *Requested Data Value* IE with the *Complete Almanac Provided* IE included, if available. + +If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "GANSS Reference Measurement Information ", the SAS shall include the *GANSS Reference Measurement Information* IE in *Requested* + +*Data Value* IE with the *Azimuth and Elevation* and *Azimuth and Elevation LSB* IEs included, if available, and with the *Confidence* IE included, if available. + +If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "GANSS Reference Time", the SAS shall include the *GANSS Reference Time* IE in *Requested Data Value* IE with the *GANSS Day Cycle Number* IE included, if available. + +If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "GANSS Time Model GNSS-GNSS", the SAS shall include the *GANSS Time Model* IE in *Requested Data Value* IE with the *Delta\_T* IE included, if available. + +If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "DBDS Corrections", the SAS shall include the *DBDS Correction Information* IE in *Requested Data Value* IE with the *DBDS information* IE included, if available. + +If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "BDS Ionospheric Grid Model Request", the SAS shall include the *BDS Ionospheric Grid Model* IE in *Requested Data Value* IE, if available. + +### 8.3.3 Unsuccessful Operation + +![Sequence diagram showing an unsuccessful information exchange initiation between RNC and SAS. The RNC sends an INFORMATION EXCHANGE INITIATION REQUEST to the SAS, and the SAS responds with an INFORMATION EXCHANGE INITIATION FAILURE.](9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg) + +``` + +sequenceDiagram + participant RNC + participant SAS + Note left of RNC: + RNC->>SAS: INFORMATION EXCHANGE INITIATION REQUEST + Note right of SAS: + SAS-->>RNC: INFORMATION EXCHANGE INITIATION FAILURE + Note left of RNC: + +``` + +Sequence diagram showing an unsuccessful information exchange initiation between RNC and SAS. The RNC sends an INFORMATION EXCHANGE INITIATION REQUEST to the SAS, and the SAS responds with an INFORMATION EXCHANGE INITIATION FAILURE. + +**Figure 4: Information Exchange Initiation procedure, Unsuccessful Operation** + +If the requested Information Type received in the *Information Type* IE indicates a type of information that SAS cannot provide, the SAS shall regard the Information Exchange Initiation procedure as failed. + +If the requested information provision cannot be carried out, the SAS shall send the INFORMATION EXCHANGE INITIATION FAILURE message. The message shall include the same Information Exchange ID that was used in the INFORMATION EXCHANGE INITIATION REQUEST message and the *Cause* IE set to an appropriate value. + +Typical cause values are as follows: + +- Information temporarily not available; +- Information Provision not supported for the object; +- Processing Overload; +- Hardware Failure; +- O&M Intervention. + +### 8.3.4 Abnormal Conditions + +If the *Information Exchange Object Type* IE is set to "Reference Position" and the *Information Type* IE set to "Explicit" and the *Explicit Information Item* IE is set to "Reference Location" or "GANSS Reference Location" the SAS shall reject the Information Exchange Initiation procedure and shall send the INFORMATION EXCHANGE INITIATION FAILURE message. + +The allowed combinations of the Information Type and Information Report Characteristics are shown in the table below marked with "X". For not allowed combinations, the SAS shall reject the Information Exchange Initiation procedure using the INFORMATION EXCHANGE INITIATION FAILURE message. + +**Table 3a: Allowed Information Type and Information Report Characteristics combinations** + +| Type | Information Report Characteristics Type | | | +|-----------------------------------------|-----------------------------------------|----------|-----------------| +| | On Demand | Periodic | On Modification | +| Almanac and Satellite Health | X | X | X | +| UTC Model | X | X | X | +| Ionospheric Model | X | X | X | +| Navigation Model | X | X | X | +| DGPS Corrections | X | X | X | +| Reference Time | X | X | X | +| Acquisition Assistance | X | X | X | +| Real Time Integrity | X | X | X | +| Almanac and Satellite Health SIB | X | X | X | +| Reference Location | X | | | +| GANSS Reference Time | X | X | X | +| GANSS Ionosphere Model | X | X | X | +| GANSS Reference Location | X | | | +| GANSS Additional Ionospheric Model | X | X | X | +| GANSS Earth Orientation Parameters | X | X | X | +| GANSS Real Time Integrity | X | X | X | +| GANSS Data Bit Assistance | X | X | | +| DGANSS Corrections | X | X | X | +| GANSS Almanac and Satellite Health | X | X | X | +| GANSS Reference Measurement Information | X | X | X | +| GANSS UTC Model | X | X | X | +| GANSS Time Model GNSS-GNSS | X | X | X | +| GANSS Navigation Model | X | X | X | +| GANSS Additional Navigation Models | X | X | X | +| GANSS Additional UTC Models | X | X | X | +| GANSS Auxiliary Information | X | X | X | +| BDS Ionospheric Grid Model | X | X | X | +| DBDS Corrections | X | X | X | + +## 8.4 Information Reporting + +### 8.4.1 General + +This procedure is used by a SAS to report the result of information requested by a RNC using the Information Exchange Initiation. + +This procedure uses the signalling bearer connection for the Information Exchange Context. + +### 8.4.2 Successful Operation + +![Sequence diagram showing the Information Reporting procedure. A box labeled 'RNC' is on the left and a box labeled 'SAS' is on the right. A horizontal arrow labeled 'INFORMATION REPORT' points from the SAS box to the RNC box. Both boxes have vertical lines extending downwards to a horizontal bar at the bottom, representing lifelines.](58f4167687de8d7339594e5f6fbe0bc6_img.jpg) + +Sequence diagram showing the Information Reporting procedure. A box labeled 'RNC' is on the left and a box labeled 'SAS' is on the right. A horizontal arrow labeled 'INFORMATION REPORT' points from the SAS box to the RNC box. Both boxes have vertical lines extending downwards to a horizontal bar at the bottom, representing lifelines. + +**Figure 5: Information Reporting procedure, Successful Operation** + +If the requested information reporting criteria are met, the SAS shall initiate an Information Reporting procedure. Unless specified below, the meaning of the parameters are given in other specifications. + +The *Information Exchange ID* IE shall be set to the Information Exchange ID provided by the RNC when initiating the information exchange with the Information Exchange Initiation procedure. + +The *Requested Data Value* IE shall include at least one IE containing the data to be reported. + +If the *Requested Data Value* IE contains the *GANSS Common Assistance Data* IE, at least one of the *GANSS Reference Time*, *GANSS Ionospheric Model*, *GANSS Reference Location*, *GANSS Additional Ionospheric Model*, or *GANSS Earth Orientation Parameters* IEs shall be present. + +Any *GANSS Generic Assistance Data* IE associated with a given GANSS included in the *Requested Data Value* IE shall contain at least one of the *GANSS Real Time Integrity*, *GANSS Data Bit Assistance*, *DGANSS Corrections*, *GANSS Almanac and Satellite Health*, *GANSS Reference Measurement Information*, *GANSS UTC Model*, *GANSS Time Model*, *GANSS Navigation Model*, *GANSS Additional Time Models*, *GANSS Additional Navigation Models*, *GANSS Additional UTC Models*, *GANSS Auxiliary Information*, *DBDS Corrections*, or *BDS Ionospheric Grid Model* IEs. + +- If the *GANSS Generic Assistance Data* IE does not contain the *GANSS ID* IE, the corresponding GANSS is "Galileo". +- The *DGANSS Corrections* IE contains one or several *DGANSS Information* IE(s), each of them associated with a GANSS Signal. A *DGANSS Information* IE for a particular GANSS that does not contain the *GANSS Signal ID* IE is by default associated with the default signal defined in TS 25.331 [4]. +- The *GANSS Real Time Integrity* IE contains one or several *Satellite Information* IEs, each of them associated with a satellite and a GANSS Signal. A *Satellite Information* IE for a particular GANSS that does not contain the *Bad GANSS Signal ID* IE is by default associated with all the signals of the corresponding satellite (see OS SIS ICD [22], IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], DTFA01-96-C-00025 [26], IS-QZSS [27], [28], BDS-SIS-ICD [33]). +- The *GANSS Reference Measurement Information* IE is associated with a GANSS Signal. A *GANSS Reference Measurement Information* IE for a particular GANSS that does not contain the *GANSS Signal ID* IE is by default associated with the default signal defined in TS 25.331 [4]. + +If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "GANSS Generic Data" and includes the *GANSS Time Model GNSS-GNSS* IE with exactly one bit set to value "1" in the *GNSS-GNSS Time ext* IE, the SAS shall include the *GANSS Time Model* IE in the *Requested Data Value* IE with the requested time information. + +If the *Information Type* IE is set to "Explicit" and the *Explicit Information Item* IE is set to "GANSS Generic Data" and includes the *GANSS Time Model GNSS-GNSS* IE with more than one bit set to value "1" in the *GNSS-GNSS Time ext* IE, the SAS shall include the *GANSS Additional Time Models* IE in *Requested Data Value* IE with the requested time information for each GANSS. + +### 8.4.3 Abnormal Conditions + +- + +## 8.5 Information Exchange Termination + +### 8.5.1 General + +This procedure is used by a RNC to terminate the information exchange requested using the Information Exchange Initiation. + +This procedure uses the signalling bearer connection for the Information Exchange Context. + +### 8.5.2 Successful Operation + +![Sequence diagram showing the Information Exchange Termination procedure. An RNC sends an INFORMATION EXCHANGE TERMINATION REQUEST message to a SAS.](db5ab5d386827a5d5f5fad0f45612b90_img.jpg) + +``` +sequenceDiagram + participant RNC + participant SAS + Note left of RNC: + RNC->>SAS: INFORMATION EXCHANGE TERMINATION REQUEST + Note right of SAS: + deactivate RNC + deactivate SAS +``` + +The diagram illustrates a sequence of interactions between two entities, RNC and SAS. The RNC is on the left and the SAS is on the right. A horizontal arrow points from the RNC to the SAS, labeled "INFORMATION EXCHANGE TERMINATION REQUEST". Both entities have vertical lifelines extending downwards from their respective boxes, ending in thick horizontal bars. + +Sequence diagram showing the Information Exchange Termination procedure. An RNC sends an INFORMATION EXCHANGE TERMINATION REQUEST message to a SAS. + +**Figure 6: Information Exchange Termination procedure, Successful Operation** + +This procedure is initiated with an INFORMATION EXCHANGE TERMINATION REQUEST message. + +Upon reception, the SAS shall terminate the information exchange corresponding to the Information Exchange ID. + +### 8.5.3 Abnormal Conditions + +- + +## 8.6 Information Exchange Failure + +### 8.6.1 General + +This procedure is used by a SAS to notify a RNC that the information exchange it previously requested using the Information Exchange Initiation can no longer be reported. + +This procedure uses the signalling bearer connection for the Information Exchange Context. + +### 8.6.2 Successful Operation + +![Sequence diagram for Information Exchange Failure procedure, Successful Operation. It shows two vertical lifelines: RNC on the left and SAS on the right. A horizontal arrow points from the SAS lifeline to the RNC lifeline, labeled 'INFORMATION EXCHANGE FAILURE INDICATION'. Both lifelines end with a thick horizontal bar at the bottom.](eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg) + +Sequence diagram for Information Exchange Failure procedure, Successful Operation. It shows two vertical lifelines: RNC on the left and SAS on the right. A horizontal arrow points from the SAS lifeline to the RNC lifeline, labeled 'INFORMATION EXCHANGE FAILURE INDICATION'. Both lifelines end with a thick horizontal bar at the bottom. + +**Figure 7: Information Exchange Failure procedure, Successful Operation** + +This procedure is initiated with an INFORMATION EXCHANGE FAILURE INDICATION message, sent from the SAS to the RNC, to inform the RNC that information previously requested by the Information Exchange Initiation procedure can no longer be reported. The message shall include the same Information Exchange ID that was used in the INFORMATION EXCHANGE INITIATION REQUEST message and the *Cause* IE set to an appropriate value. + +Typical cause values are as follows: + +- Information temporarily not available. + +## 8.7 Error Indication + +### 8.7.1 General + +The Error Indication procedure is used by a node to report detected errors in one incoming message, provided they cannot be reported by an appropriate failure message. + +### 8.7.2 Successful Operation + +![Sequence diagram for Error Indication procedure, SAS Originated, Successful Operation. It shows two vertical lifelines: RNC on the left and SAS on the right. A horizontal arrow points from the SAS lifeline to the RNC lifeline, labeled 'ERROR INDICATION'. Both lifelines end with a thick horizontal bar at the bottom.](ead623e6a8ec701df64567695a57d01c_img.jpg) + +Sequence diagram for Error Indication procedure, SAS Originated, Successful Operation. It shows two vertical lifelines: RNC on the left and SAS on the right. A horizontal arrow points from the SAS lifeline to the RNC lifeline, labeled 'ERROR INDICATION'. Both lifelines end with a thick horizontal bar at the bottom. + +**Figure 8: Error Indication procedure, SAS Originated, Successful Operation** + +![Sequence diagram for Error Indication procedure, RNC Originated, Successful Operation. It shows two vertical lifelines: RNC on the left and SAS on the right. A horizontal arrow points from the RNC lifeline to the SAS lifeline, labeled 'ERROR INDICATION'. Both lifelines end with a thick horizontal bar at the bottom.](d5918cee231b536f20789a18d861fae3_img.jpg) + +Sequence diagram for Error Indication procedure, RNC Originated, Successful Operation. It shows two vertical lifelines: RNC on the left and SAS on the right. A horizontal arrow points from the RNC lifeline to the SAS lifeline, labeled 'ERROR INDICATION'. Both lifelines end with a thick horizontal bar at the bottom. + +**Figure 9: Error Indication procedure, RNC Originated, Successful Operation** + +When the conditions defined in clause 10 are fulfilled, the Error Indication procedure is initiated by an ERROR INDICATION message sent from the receiving node. This message shall use the same mode of the signalling bearer and the same signalling bearer connection (if connection oriented) as the message that triggers the procedure. + +The ERROR INDICATION message shall include either the *Cause* IE, or the *Criticality Diagnostics* IE, or both the *Cause* IE and the *Criticality Diagnostics* IE. + +Typical cause values are as follows: + +- Transfer Syntax Error; +- Abstract Syntax Error (Reject); +- Abstract Syntax Error (Ignore and Notify); +- Message not Compatible with Receiver State; +- Unspecified. + +### 8.7.3 Abnormal Conditions + +- + +## 8.8 Position Initiation + +### 8.8.1 General + +This procedure is used by an SRNC to request from an SAS the position (non-periodic or periodic) of a UE using the SAS centric mode of operation. + +The connection-oriented service of the signalling bearer shall be established in conjunction with this procedure. + +### 8.8.2 Successful Operation + +![Sequence diagram of the Position Initiation procedure showing a request from SRNC to SAS and a response from SAS to SRNC.](7728e2dd44c95d109debb1eb59e9b411_img.jpg) + +``` +sequenceDiagram + participant SRNC + participant SAS + Note left of SRNC: + SRNC->>SAS: POSITION INITIATION REQUEST + Note right of SAS: + SAS-->>SRNC: POSITION INITIATION RESPONSE + Note left of SRNC: +``` + +Sequence diagram of the Position Initiation procedure showing a request from SRNC to SAS and a response from SAS to SRNC. + +**Figure 9a: Position Initiation procedure, Successful Operation** + +This procedure is initiated with a POSITION INITIATION REQUEST message sent from the SRNC to the SAS and ends with a POSITION INITIATION RESPONSE message from the SAS to the SRNC. + +The POSITION INITIATION REQUEST message may contain one or several *Network Assisted GANSS Support* IE(s), each of them indicating the UE position capability with regard to GANSS. + +- If a *Network Assisted GANSS Support* IE does not contain the *GANSS ID* IE, the SAS shall assume that the corresponding GANSS is "Galileo". +- If a *Network Assisted GANSS Support* IE corresponding to a particular GANSS does not contain the *GANSS Signal ID* IE and the *GANSS Signal IDs* IE, the SAS shall assume that the corresponding GANSS Signal is the default signal defined in TS 25.331 [4]. + +If the *IMSI* IE, or *IMEI* IE is included in the in POSITION INITIATION REQUEST message, the SAS may save these IEs for use in location session correlation. + +#### Response Message: + +If the POSITION INITIATION REQUEST message contains a request for direct reporting, and following completion of one or more positioning attempts, possibly using multiple positioning methods, the SAS shall pass the UE position to the SRNC in a POSITION INITIATION RESPONSE message. + +If the POSITION INITIATION REQUEST message contains a request for periodic reporting, the SAS shall pass the final UE position to the SRNC in a POSITION INITIATION RESPONSE message. + +Whenever one of the geographic area shapes *Ellipsoid point with uncertainty Ellipse* IE, *Ellipsoid point with altitude and uncertainty Ellipsoid* IE or *Ellipsoid Arc* IE is reported, the *Confidence* IE shall indicate the probability that the UE is located within the uncertainty region of the shape. The value of the *Confidence* IE shall be in the interval of "1" to "100". + +If at least the *Horizontal Accuracy Code* IE was included in the POSITION INITIATION REQUEST message and the calculated position estimate fulfils the requested accuracy, the *Accuracy Fulfilment Indicator* IE with the value "requested accuracy fulfilled" shall be included in the POSITION INITIATION RESPONSE message. If the calculated position estimate does not fulfil the requested accuracy, the *Accuracy Fulfilment Indicator* IE with the value "requested accuracy not fulfilled" shall be included in the POSITION INITIATION RESPONSE message. + +### 8.8.3 Unsuccessful Operation + +![Sequence diagram showing an unsuccessful position initiation procedure between SRNC and SAS.](17a1ba23b641c01871b08f0a4f08ef48_img.jpg) + +``` +sequenceDiagram + participant SRNC + participant SAS + Note left of SRNC: SRNC + Note right of SAS: SAS + SRNC->>SAS: POSITION INITIATION REQUEST + SAS-->>SRNC: POSITION INITIATION FAILURE +``` + +The diagram illustrates a sequence of messages between an SRNC (Service Radio Network Controller) and a SAS (Serving AS). It starts with the SRNC sending a 'POSITION INITIATION REQUEST' message to the SAS. The SAS then responds with a 'POSITION INITIATION FAILURE' message, indicating an unsuccessful operation. + +Sequence diagram showing an unsuccessful position initiation procedure between SRNC and SAS. + +Figure 9b: Position Initiation procedure, Unsuccessful Operation + +When the SAS is unable to accept a POSITION INITIATION REQUEST message or the SAS cannot provide a position estimate in case of direct reporting, the POSITION INITIATION FAILURE message shall be sent to the SRNC. + +Typical cause values are: + +- Processing Overload; +- Hardware Failure; +- O&M Intervention; +- Information temporarily not available. + +### 8.8.4 Abnormal Conditions + +If the *Vertical Accuracy Code* IE is included and the *Horizontal Accuracy Code* IE is not included in the POSITION INITIATION REQUEST message, the SAS shall reject the procedure. + +## 8.9 Position Activation + +### 8.9.1 General + +The purpose of the Position Activation procedure is to enable the SAS to initiate a particular positioning method used for an individual positioning event. This procedure uses connection-oriented signalling. + +### 8.9.2 Successful Operation + +![Sequence diagram showing the Position Activation procedure between SRNC and SAS. The SAS sends a POSITION ACTIVATION REQUEST to the SRNC, and the SRNC responds with a POSITION ACTIVATION RESPONSE.](fc0735d325f0ebd9214171975c68a888_img.jpg) + +``` + +sequenceDiagram + participant SRNC + participant SAS + Note right of SAS: POSITION ACTIVATION REQUEST + SAS->>SRNC: POSITION ACTIVATION REQUEST + Note left of SRNC: POSITION ACTIVATION RESPONSE + SRNC->>SAS: POSITION ACTIVATION RESPONSE + +``` + +Sequence diagram showing the Position Activation procedure between SRNC and SAS. The SAS sends a POSITION ACTIVATION REQUEST to the SRNC, and the SRNC responds with a POSITION ACTIVATION RESPONSE. + +**Figure 9c: Position Activation procedure, Successful Operation** + +The SAS initiates this procedure by sending a POSITION ACTIVATION REQUEST message to the SRNC containing the required positioning method and any assistance data and instructions associated with that positioning method. The SRNC then sends a POSITION ACTIVATION RESPONSE message to the SAS confirming the requested action and providing any information required by the requested positioning method; e.g. UE channel information for the U-TDOA positioning method or A-GPS measurements for UE assisted A-GPS. In the POSITION ACTIVATION RESPONSE message, the SRNC should include either the *UE Position Estimate Info IE*, *GPS Measurement Results IE*, *Cell-ID Measured Results Sets IE*, *OTDOA Measured Results Sets IE*, *UTDOA Group IE*, *GANSS Measurement Results IE*, *Required GPS Assistance Data IE*, *Required GANSS Assistance Data IE* or the *Additional Positioning Measured Results IE*. + +If the *Positioning Method IE* in a POSITION ACTIVATION REQUEST message includes the *GNSS Positioning Method IE* indicating allowance of 'GPS' and any other GNSS ('Galileo', 'SBAS', 'Modernized GPS', 'QZSS', 'GLONASS', 'BDS'), the SRNC may include both, the *GPS Measurement Results IE* and the *GANSS Measurement Results IE*, or both, the *Required GPS Assistance Data IE* or *Required GANSS Assistance Data IE* in the POSITION ACTIVATION RESPONSE message. + +If the *Positioning Method IE* in a POSITION ACTIVATION REQUEST message includes the *Additional Positioning Method IE*, the SRNC may include the *Additional Positioning Measurement Results IE* in the POSITION ACTIVATION RESPONSE message. + +If the POSITION ACTIVATION REQUEST message contains periodic reporting information to start a periodic RNC positioning procedure (i.e., *Amount of Reporting IE* is included), the POSITION ACTIVATION RESPONSE message may be returned confirming the requested action and not including any measurements. In that case, all periodic measurement reports are conveyed using POSITION PERIODIC REPORT messages. + +If the *GPS Positioning Instructions IE* or the *GANSS Positioning Instructions IE* is included in a POSITION ACTIVATION REQUEST message containing the *Measurement Validity IE*, the SRNC should include the *Measurement Instructions Used IE* in a POSITION ACTIVATION RESPONSE message if the Measurement Validity used by the SRNC is different from the Measurement Validity requested by the SAS. + +If the *GERAN IE* is included in the *Requested Cell-ID Measurements IE* in the *Cell-ID Positioning IE*, the SRNC shall use it to determine the requested inter-RAT measurements. + +If the POSITION ACTIVATION REQUEST message contains the *Position Method IE* with value "Cell ID", the *Amount of Reporting IE* shall not be included. If the POSITION ACTIVATION REQUEST message contains the *Position Method IE* with value "Cell ID" the *Amount of Reporting IE* shall not be included. + +If the POSITION ACTIVATION REQUEST message contains the *Position Method* IE with value "Cell ID", the RNC may include the measurements requested in the *Requested Cell-ID Measurements* IE in the POSITION ACTIVATION RESPONSE message. If the RNC includes the measurements in the *Requested Cell-ID Measurements* IE it shall, if supported, do so for all cells (i.e. those in the active, monitored and detected sets) for which measurements are available from the UE. If both of the *Round Trip Time Info* IE and the *Round Trip Time Info With Type 1* IE are included in the POSITION ACTIVATION RESPONSE message, the SAS shall use the *Round Trip Time Info* IE. + +If the SRNC receives a new POSITION ACTIVATION REQUEST message before it has responded to a previous non-periodic request, the SRNC should terminate all activity for the previous request, without sending any response to the initial request, and process the new request. + +If the SRNC receives a new POSITION ACTIVATION REQUEST message for UE position measurement reporting using A-GPS or A-GNSS or OTDOA or Additional Positioning (periodic or non-periodic) while it is still performing activity for a previous A-GPS or A-GNSS or OTDOA or Additional Positioning periodic request, the SRNC should terminate all activity for the previous request, including terminating the periodic measurement reporting in the UE, and should process the new request. + +If the SRNC receives a new POSITION ACTIVATION REQUEST message for Cell-ID or U-TDOA positioning while it is still performing activity for a previous A-GPS or A-GNSS or OTDOA or Additional Positioning periodic request (but after returning any POSITION ACTIVATION RESPONSE for this request), the SRNC may both continue with the previous request and process the new request. + +If the *GNSS Positioning* IE is included in the POSITION ACTIVATION REQUEST message and contains the *Requested Data Value* IE: + +- If the *GNSS Generic Assistance Data* IE, associated with a given GNSS, is included in the *Requested Data Value* IE, it shall contain a *GNSS Real Time Integrity*, *GNSS Data Bit Assistance*, *DGNSS Corrections*, *GNSS Almanac and Satellite Health*, *GNSS Reference Measurement Information*, *GNSS UTC Model*, *GNSS Time Model*, *GNSS Navigation Model*, *GNSS Additional Time Models*, *GNSS Additional Navigation Models*, *GNSS Additional UTC Models*, *GNSS Auxiliary Information*, *DBDS Corrections*, or *BDS Ionospheric Grid Model* IE. + - - If the *GNSS Generic Assistance Data* IE does not contain the *GNSS ID* IE, the corresponding GNSS is "Galileo". + - - The *DGNSS Corrections* IE contains one or several *DGNSS Information* IE(s), each of them associated with a GNSS Signal. A *DGNSS Information* IE for a particular GNSS that does not contain the *GNSS Signal ID* IE is by default associated with the default signal defined in TS 25.331 [4]. + - - The *GNSS Real Time Integrity* IE contains one or several *Satellite Information* IEs, each of them associated with a satellite and a GNSS Signal. A *Satellite Information* IE for a particular GNSS that does not contain the *Bad GNSS Signal ID* IE is by default associated with all the signals of the corresponding satellite (see OS SIS ICD [22], IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], DTFA01-96-C-00025 [26], IS-QZSS [27], [28], BDS-SIS-ICD [33]). + - - The *GNSS Reference Measurement Information* IE is associated with a GNSS Signal. A *GNSS Reference Measurement Information* IE for a particular GNSS that does not contain the *GNSS Signal ID* IE is by default associated with the default signal defined in TS 25.331 [4]. + - - The *DBDS Corrections* IE contains one or several *DBDS Information* IE(s), each of them associated with a BDS Signal. A *DBDS Information* IE that does not contain the *BDS Signal ID* IE is by default associated with the default signal defined in TS 25.331 [4]. + +If the RRC State included in the *UTDOA Group* IE is indicated as being *CELL\_DCH* in the POSITION ACTIVATION RESPONSE message, [FDD - either the *DCH Information* IE or the *E-DPCH Information* IE][TDD - the *DCH Information* IE] should be included. + +If the *GNSS Measured Results* IE is included in the POSITION ACTIVATION RESPONSE message and does not contain the *GNSS Time ID* IE, the SAS shall assume that the corresponding GNSS timing refers to the "Galileo" timing. + +The *GNSS Measured Results* IE contains one or several *GNSS Generic Measurement Information* IEs, each of them associated with a given GNSS: + +- If a *GANSS Generic Measurement Information* IE does not contain the *GANSS ID* IE, the SAS shall assume that the associated GANSS is "Galileo". +- If a *GANSS Generic Measurement Information* IE associated with a particular GANSS does not contain the *GANSS Signal ID* IE, the SAS shall assume the default value as defined in TS 25.331 [4]. +- If a *GANSS Generic Measurement Information* IE does not contain the *GANSS Code Phase Ambiguity* IE and the *GANSS Code Phase Ambiguity Extension* IE, the SAS shall assume the value "1" (ms). +- If the *GANSS Integer Code Phase* IE and the *GANSS Integer Code Phase Extension* IE associated to a given satellite (identified by the *Sat ID* IE value) is not present within the *GANSS Measurement Parameters* IE, the SAS shall use the default "1" (ms) for the GANSS Code Phase Ambiguity value in order to compute the value of the Total Code Phase (as defined in TS 25.331 [4]) for the related satellite, whatever the value of the *GANSS Code Phase Ambiguity* IE. + +If the *OTDOA Measured Results Sets* IE is included in the POSITION ACTIVATION RESPONSE message the SRNC should also include the *OTDOA Reference Cell Info*. The SAS shall use the cell identified in the *OTDOA Reference Cell Info* IE as reference cell for the measurements provided in the *OTDOA Measured Results Info List* IE. + +If an optional *Cell-ID IRAT Measured Results Sets* IE is included in the POSITION ACTIVATION RESPONSE message, the SAS shall, if supported, use this value for the calculation of the UE Position Estimate in case of RFPM positioning method is used. The SAS may use this value for the calculation of the UE Position when any other methods are used. + +### 8.9.3 Unsuccessful Operation + +![Sequence diagram showing an unsuccessful position activation procedure between SRNC and SAS.](b904ac2472cab80892d1e783e6230d6e_img.jpg) + +``` + +sequenceDiagram + participant SRNC + participant SAS + SAS->>SRNC: POSITION ACTIVATION REQUEST + SRNC->>SAS: POSITION ACTIVATION FAILURE + +``` + +The diagram illustrates a sequence of messages between an SRNC (Source RNC) and a SAS (Serving AS). The SAS sends a 'POSITION ACTIVATION REQUEST' message to the SRNC. The SRNC responds with a 'POSITION ACTIVATION FAILURE' message, indicating an unsuccessful operation. + +Sequence diagram showing an unsuccessful position activation procedure between SRNC and SAS. + +**Figure 9d: Position Activation procedure, Unsuccessful Operation** + +When the SRNC is unable to accept a POSITION ACTIVATION REQUEST message, the POSITION ACTIVATION FAILURE message should be sent to the SAS. + +Typical cause values are: + +- Processing Overload; +- Hardware Failure; +- O&M Intervention; +- Positioning Method Not Supported; +- Location Measurement Failure. + +### 8.9.4 Abnormal Conditions + +- + +## 8.10 Position Parameter Modification + +### 8.10.1 General + +The purpose of the Position Parameter Modification procedure is to inform the SAS of any relevant changes to the RF connection or other changes during a positioning event. This procedure uses connectionless signalling when invoked in RNC centric mode and connection-oriented signalling when invoked in SAS centric mode. + +### 8.10.2 Successful Operation + +![Sequence diagram showing the successful operation of the Position Parameter Modification procedure. The SRNC sends a POSITION PARAMETER MODIFICATION message to the SAS.](8658cfab6a458b4a80ab2e384c61ff89_img.jpg) + +``` +sequenceDiagram + participant SRNC + participant SAS + Note left of SRNC: + SRNC->>SAS: POSITION PARAMETER MODIFICATION + Note right of SAS: + activate SAS + deactivate SAS +``` + +Sequence diagram showing the successful operation of the Position Parameter Modification procedure. The SRNC sends a POSITION PARAMETER MODIFICATION message to the SAS. + +**Figure 9e: Position Parameter Modification procedure, Successful Operation** + +If the SAS receives a POSITION PARAMETER MODIFICATION message, the SAS shall apply the information to the ongoing position estimate (e.g. reconfigure LMUs for U-TDOA) or to a new positioning attempt (e.g. use new serving cell to provide A-GPS assistance data). If there is more than one signalling connection for a UE, the SRNC should send the POSITION PARAMETER MODIFICATION message on each connection. When operating in the RNC centric mode the *Transaction ID* IE should be used to associate the POSITION PARAMETER MODIFICATION message to the correct positioning event. + +In the POSITION PARAMETER MODIFICATION message, only one of the *UTRAN Cell Identifier* IE or the *UTDOA GROUP* IE should be included. + +The SRNC should send a POSITION PARAMETER MODIFICATION message if an RRC measurement procedure for periodic UE positioning measurement reporting in the UE has been activated by the SRNC upon reception of a POSITION ACTIVATION REQUEST message, and if there is a RRC state transition during the RRC measurement procedure, which does not result in a termination of the UE measurement reporting. The SRNC should continue to notify the SAS of such RRC state changes until the periodic position measurement reporting has been completed or terminated. + +### 8.10.3 Abnormal Conditions + +- + +## 8.11 Abort + +### 8.11.1 General + +The purpose of the Abort procedure is to inform the SAS that the RNC is unable to continue the current positioning activity for a particular UE. This procedure uses connectionless signalling when invoked in RNC centric mode and connection-oriented signalling when invoked in SAS centric mode. + +### 8.11.2 Successful Operation + +![Sequence diagram showing the Abort procedure. The SRNC sends an ABORT message to the SAS.](9870bf462aa0d916a16d14b5a100c60a_img.jpg) + +``` +sequenceDiagram + participant SRNC + participant SAS + Note left of SRNC: + SRNC->>SAS: ABORT + Note right of SAS: + Note left of SRNC: + Note right of SAS: +``` + +Sequence diagram showing the Abort procedure. The SRNC sends an ABORT message to the SAS. + +**Figure 9f: Abort procedure, Successful Operation** + +The SRNC should send an ABORT message when the SRNC is unable to continue positioning activity due to cell reselection that results in a different SRNC, loss of contact with the UE or any other reason. When operating in the RNC centric mode the *Transaction ID* IE should be used to associate the ABORT message to the correct positioning event. + +If the SAS receives an ABORT message while in the SAS centric mode it should immediately cease positioning attempts and return a POSITION INITIATION RESPONSE message to the SRNC carrying any location estimate already obtained or a POSITION INITIATION FAILURE message if no location estimate was obtained. + +If the SAS receives an ABORT message while in the RNC centric mode it should immediately cease positioning attempts and return a POSITION CALCULATION RESPONSE message to the SRNC carrying any location estimate already obtained or a POSITION CALCULATION FAILURE message if no location estimate was obtained. After sending an ABORT message the SRNC should cease positioning activity, if any. + +Typical cause values are: + +- Processing Overload; +- Hardware Failure; +- O&M Intervention; +- Loss of contact with the UE. + +### 8.11.3 Abnormal Conditions + +- + +## 8.12 Position Periodic Report + +### 8.12.1 General + +The purpose of the Position Periodic Report procedure is to send measurement information or UE position estimate from the SRNC to the SAS for periodic location in SAS-centric mode. This procedure uses connection-oriented signalling. + +### 8.12.2 Successful Operation + +![Sequence diagram showing the Position Periodic Report procedure. A box labeled SRNC is on the left and a box labeled SAS is on the right. A horizontal arrow labeled 'POSITION PERIODIC REPORT' points from the SRNC box to the SAS box.](1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg) + +``` + +sequenceDiagram + participant SRNC + participant SAS + Note left of SRNC: + SRNC->>SAS: POSITION PERIODIC REPORT + Note right of SAS: + +``` + +Sequence diagram showing the Position Periodic Report procedure. A box labeled SRNC is on the left and a box labeled SAS is on the right. A horizontal arrow labeled 'POSITION PERIODIC REPORT' points from the SRNC box to the SAS box. + +**Figure 9g: Position Periodic Report procedure, Successful Operation** + +This procedure is initiated with a POSITION PERIODIC REPORT message sent from the SRNC to the SAS. The POSITION PERIODIC REPORT message provides the SAS measurement information such as GPS or OTDOA measurements, or an indication of measurement failure. + +The SRNC should send the first POSITION PERIODIC REPORT message one reporting interval after the POSITION ACTIVATION RESPONSE message, and should continue to send further POSITION PERIODIC REPORT messages one reporting interval after the previous POSITION PERIODIC REPORT message based on the available measurements. If the RNC cannot deliver measurement information when a POSITION PERIODIC REPORT is triggered, the *Cause* IE should be included in the POSITION PERIODIC REPORT message, indicating the reason for measurement failure, e.g. "UE Positioning Error: Not enough OTDOA cells", "UE Positioning Error: Not enough GPS Satellites", "UE Positioning Error: Not Accomplished GPS Timing of Cell Frames" or "UE Positioning Error: Undefined Error". If the *Cause* IE is included in a POSITION PERIODIC REPORT message, the *UE Position Estimate Info* IE, *Velocity Estimate* IE, *GPS Measurement Results* IE, *GANSS Measurement Results* IE, *Cell-ID Measured Results Sets* IE, *OTDOA Measured Results Sets* IE and *Additional Positioning Measurement Results* IE should not be included. If and only if the *Cause* IE indicates the error reason "UE Positioning Error: Assistance Data Missing" the SRNC may include the *Required GPS Assistance Data* IE and/or the *Required GANSS Assistance Data* IE in the POSITION PERIODIC REPORT message. + +If the *Cell-ID Measured Results Sets* IE is included in the POSITION PERIODIC REPORT message and both of the *Round Trip Time Info* IE and the *Round Trip Time Info With Type 1* IE are included in the *Cell-ID Measured Results Info List* IE, the SAS shall use the *Round Trip Time Info* IE. + +If the *GANSS Measured Results* IE is included in the POSITION PERIODIC REPORT message and does not contain the *GANSS Time ID* IE, the SAS shall assume that the corresponding GANSS timing refers to the "Galileo" timing. + +The *GANSS Measured Results* IE contains one or several *GANSS Generic Measurement Information* IEs, each of them associated with a given GANSS: + +- If a *GANSS Generic Measurement Information* IE does not contain the *GANSS ID* IE, the SAS shall assume that the associated GANSS is "Galileo". +- If a *GANSS Generic Measurement Information* IE associated with a particular GANSS does not contain the *GANSS Signal ID* IE, the SAS shall assume the default value as defined in TS 25.331 [4]. +- If a *GANSS Generic Measurement Information* IE does not contain the *GANSS Code Phase Ambiguity* IE and the *GANSS Code Phase Ambiguity Extension* IE, the SAS shall assume the value "1" (ms). +- If the *GANSS Integer Code Phase* IE and the *GANSS Integer Code Phase Extension* IE associated to a given satellite (identified by the *Sat ID* IE value) is not present within the *GANSS Measurement Parameters* IE, the SAS shall use the default "1" (ms) for the GANSS Code Phase Ambiguity value in order to compute the value of the Total Code Phase (as defined in TS 25.331 [4]) for the related satellite, whatever the value of the *GANSS Code Phase Ambiguity* IE. + +If the *OTDOA Measured Results Sets* IE is included in the POSITION PERIODIC REPORT message the SRNC should also include the *OTDOA Reference Cell Info*. The SAS shall use the cell identified in the *OTDOA Reference Cell Info* IE as reference cell for the measurements provided in the *OTDOA Measured Results Info List* IE. + +If an optional *Cell-ID IRAT Measured Results Sets* IE is included in the POSITION PERIODIC REPORT message, the SAS shall, if supported, use this value for the calculation of the UE Position Estimate in case of RFPM positioning method is used. The SAS may use this value for the calculation of the UE Position when any other methods are used. + +### 8.12.3 Abnormal Conditions + +- + +## 8.13 Position Periodic Result + +### 8.13.1 General + +The purpose of the Position Periodic Result procedure is to provide UE position estimates from the SAS to the SRNC for periodic location in SAS-centric mode. This procedure uses connection-oriented signalling. + +### 8.13.2 Successful Operation + +![Sequence diagram showing the Position Periodic Result procedure. A box labeled SRNC is on the left and a box labeled SAS is on the right. A horizontal arrow labeled 'POSITION PERIODIC RESULT' points from the SAS box to the SRNC box. Vertical lines extend downwards from both boxes.](02d0c8a07c481d880b73a25d02050fad_img.jpg) + +``` + +sequenceDiagram + participant SRNC + participant SAS + Note right of SRNC: + Note right of SAS: + SAS->>SRNC: POSITION PERIODIC RESULT + +``` + +Sequence diagram showing the Position Periodic Result procedure. A box labeled SRNC is on the left and a box labeled SAS is on the right. A horizontal arrow labeled 'POSITION PERIODIC RESULT' points from the SAS box to the SRNC box. Vertical lines extend downwards from both boxes. + +**Figure 9h: Position Periodic Result procedure, Successful Operation** + +This procedure is initiated with a POSITION PERIODIC RESULT message sent from the SAS to the SRNC. The POSITION PERIODIC RESULT message conveys the UE position estimate (or an indication of positioning failure) from the SAS to the SRNC. + +The SAS shall send a POSITION PERIODIC RESULT message one reporting interval after the previous POSITION PERIODIC RESULT message. If the SAS cannot deliver measurement information when a POSITION PERIODIC RESULT is triggered, the *Cause* IE shall be included in the POSITION PERIODIC RESULT message, indicating the reason for measurement failure, e.g. "Position Calculation error: invalid GPS measured results", "Position Calculation error: invalid Cell-ID measured results", "Position Calculation error: invalid OTDOA measured results" or "Position Calculation error: invalid U-TDOA measured results". If the *Cause* IE is included in a POSITION PERIODIC RESULT message, the *UE Position Estimate* IE, *Velocity Estimate* IE, *Position Data* IE, and *Accuracy Fulfilment Indicator* IE shall not be included. + +If the *UE Position Estimate* IE is included in a POSITION PERIODIC RESULT message, the *Position Data* IE shall also be included. + +Whenever one of the geographic area shapes *Ellipsoid point with uncertainty Ellipse* IE, *Ellipsoid point with altitude and uncertainty Ellipsoid* IE or *Ellipsoid Arc* IE is reported, the *Confidence* IE shall indicate the probability that the UE is located within the uncertainty region of the shape. The value of the *Confidence* IE shall be in the interval of "1" to "100". + +If at least the *Horizontal Accuracy Code* IE was included in a POSITION INITIATION REQUEST message which initiates periodic position reporting, and the periodic position estimate included in a POSITION PERIODIC RESULT messages fulfils the requested accuracy, the *Accuracy Fulfilment Indicator* IE with the value "requested accuracy fulfilled" shall be included. If the calculated position estimate does not fulfil the requested accuracy, the *Accuracy Fulfilment Indicator* IE with the value "requested accuracy not fulfilled" shall be included in the POSITION PERIODIC RESULT message. + +### 8.13.3 Abnormal Conditions + +- + +## 8.14 Position Periodic Termination + +### 8.14.1 General + +The Position Periodic Termination procedure is used by a node to request termination of an ongoing periodic location, or to inform a node about termination of periodic location in SAS-centric mode. This procedure uses connection-oriented signalling. + +### 8.14.2 Successful Operation + +![Sequence diagram for Figure 9i: Position Periodic Termination procedure, SAS Originated, Successful Operation. The diagram shows two nodes, SRNC and SAS, with a message arrow labeled 'POSITION PERIODIC TERMINATION' pointing from SAS to SRNC.](896e86ed12aff206d302c64f2e3091fa_img.jpg) + +``` +sequenceDiagram + participant SRNC + participant SAS + Note right of SAS: POSITION PERIODIC TERMINATION + SAS->>SRNC: POSITION PERIODIC TERMINATION +``` + +Sequence diagram for Figure 9i: Position Periodic Termination procedure, SAS Originated, Successful Operation. The diagram shows two nodes, SRNC and SAS, with a message arrow labeled 'POSITION PERIODIC TERMINATION' pointing from SAS to SRNC. + +**Figure 9i: Position Periodic Termination procedure, SAS Originated, Successful Operation** + +![Sequence diagram for Figure 9k: Position Periodic Termination procedure, RNC Originated, Successful Operation. The diagram shows two nodes, SRNC and SAS, with a message arrow labeled 'POSITION PERIODIC TERMINATION' pointing from SRNC to SAS.](a8050baf48cc2c8e25d5ea2d1a67ef39_img.jpg) + +``` +sequenceDiagram + participant SRNC + participant SAS + Note left of SRNC: POSITION PERIODIC TERMINATION + SRNC->>SAS: POSITION PERIODIC TERMINATION +``` + +Sequence diagram for Figure 9k: Position Periodic Termination procedure, RNC Originated, Successful Operation. The diagram shows two nodes, SRNC and SAS, with a message arrow labeled 'POSITION PERIODIC TERMINATION' pointing from SRNC to SAS. + +**Figure 9k: Position Periodic Termination procedure, RNC Originated, Successful Operation** + +When the SAS or SRNC needs to terminate ongoing periodic location, a POSITION PERIODIC TERMINATION message is sent to the receiving node. + +If an RRC measurement procedure for periodic UE positioning measurement reporting in the UE has been activated by the SRNC upon reception of a POSITION ACTIVATION REQUEST message, and if the SRNC receives a POSITION PERIODIC TERMINATION message, the SRNC should terminate the periodic UE positioning measurement reporting in the UE. + +The SRNC should send a POSITION PERIODIC TERMINATION message if an RRC measurement procedure for periodic UE positioning measurement reporting in the UE has been activated by the SRNC upon reception of a POSITION ACTIVATION REQUEST message, and if the SRNC or UE terminates the measurement reporting (e.g., after RRC state transition). + +### 8.14.3 Abnormal Conditions + +- + +# --- 9 Elements for PCAP Communication + +## 9.1 Message Functional Definition and Content + +### 9.1.1 General + +Clause 9.1 presents the contents of PCAP messages in tabular format. The corresponding ASN.1 definitions are presented in clause 9.3. In case there is contradiction between the tabular format in clause 9.1 and the ASN.1 definition, + +the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional IEs, where the tabular format shall take precedence. + +NOTE: The messages have been defined in accordance to the guidelines specified in TS 25.921 [12]. + +### 9.1.2 Message Contents + +#### 9.1.2.1 Presence + +All information elements in the message descriptions below are marked mandatory, optional or conditional according to table 4. + +**Table 4: Meaning of abbreviations used in PCAP messages** + +| Abbreviation | Meaning | +|--------------|------------------------------------------------------------------------------------------------------------------------------------------| +| M | IEs marked as Mandatory (M) shall always be included in the message. | +| O | IEs marked as Optional (O) may or may not be included in the message. | +| C | IEs marked as Conditional (C) shall be included in a message only if the condition is satisfied. Otherwise the IE shall not be included. | + +#### 9.1.2.2 Criticality + +Each Information Element or Group of Information Elements may have a criticality information applied to it. Following cases are possible. + +**Table 5: Meaning of content within "Criticality" column** + +| Abbreviation | Meaning | +|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| – | No criticality information is applied explicitly. | +| YES | Criticality information is applied. This is usable only for non-repeatable IEs | +| GLOBAL | The IE and all its repetitions together have one common criticality information. This is usable only for repeatable IEs. | +| EACH | Each repetition of the IE has its own criticality information. It is not allowed to assign different criticality values to the repetitions. This is usable only for repeatable IEs. | + +#### 9.1.2.3 Range + +The Range column indicates the allowed number of copies of repetitive IEs/IE groups. + +#### 9.1.2.4 Assigned Criticality + +This column provides the actual criticality information as defined in clause 10.3.2, if applicable. + +### 9.1.3 POSITION CALCULATION REQUEST + +Table 6 + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------|----------|------------------------------|---------------------------------------|---------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.2.2.24 | | YES | reject | +| Transaction ID | M | | 9.2.2.28 | | – | | +| Initial UE Position Estimate | O | | Geographical Area
9.2.2.6 | | YES | reject | +| GPS Measured Results | | 0.. | | | GLOBAL | reject | +| >GPS Measured Results | M | | 9.2.2.12 | | – | | +| Cell-ID Measured Results Sets | | 0.. | | | GLOBAL | reject | +| >Cell-ID Measured Results Info List | M | | 9.2.2.31 | | – | | +| OTDOA Measurement Group | | 0..1 | | | YES | reject | +| >OTDOA Reference Cell Info | M | | 9.2.2.34 | | – | | +| >OTDOA Neighbour Cell Info List | | 1.. | | | – | | +| >>OTDOA Neighbour Cell Info | M | | 9.2.2.33 | | – | | +| >OTDOA Measured Results Sets | | 1.. | | | – | | +| >>OTDOA Measured Results Info List | M | | 9.2.2.32 | | – | | +| Horizontal Accuracy Code | O | | 9.2.2.38 | | YES | ignore | +| Vertical Accuracy Code | O | | 9.2.2.39 | | YES | ignore | +| UTDOA Group | O | | 9.2.2.74 | | YES | reject | +| SAS Response Time | O | | Positioning Response Time
9.2.2.69 | Indicates the interval allowed for a SAS response for U-TDOA positioning. | YES | ignore | +| Include Velocity | O | | 9.2.2.97 | | YES | ignore | +| Periodic Position Calculation Info | O | | 9.2.2.106 | | YES | ignore | +| GANSS Measured Results | | 0.. | | | GLOBAL | reject | +| >GANSS Measured Results | M | | 9.2.2.117 | | – | | +| Cell-ID IRAT Measured Results Sets | | 0.. | | | GLOBAL | ignore | +| >IRAT Measured Results Info List | M | | 9.2.2.155 | | – | | +| IMSI | O | | 9.2.2.158 | | YES | ignore | +| IMEI | O | | 9.2.2.159 | | YES | ignore | + +**Table 7** + +| Range bound | Explanation | +|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| maxNoOfMeasNCell | Maximum number of neighbouring cells on which information can be reported. The value of maxNoOfMeasCell is 32. | +| maxNoOfSets | Maximum number of sets of Measured Results included in the Position Calculation Request message. The value for maxNoOfSets is 3. | +| maxNoOfMeasurements | Maximum number of Measurements of Cell-ID Measured Results Info List and OTDOA Measured Results Info List included in the Position Calculation Request message. The value for maxNoOfMeasurements is 16. | +| maxNoOfIRATMeasurements | Maximum number of IRATs for which Measurements of Cell-ID IRATMeasured Results Info List may be included in the Position Calculation Request message. The value for maxNoOfIRATMeasurements is 16. | + +### 9.1.4 POSITION CALCULATION RESPONSE + +**Table 8** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------|-----------------|--------------|------------------------------|------------------------------|--------------------|-----------------------------| +| Message Type | M | | 9.2.2.24 | | YES | reject | +| Transaction ID | M | | 9.2.2.28 | | – | | +| UE Position Estimate | M | | Geographical Area 9.2.2.6 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.2.4 | | YES | ignore | +| Accuracy Fulfilment Indicator | O | | 9.2.2.40 | | YES | ignore | +| Velocity Estimate | O | | 9.2.2.98 | | YES | ignore | + +### 9.1.5 POSITION CALCULATION FAILURE + +**Table 9** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|-----------------|--------------|------------------------------|------------------------------|--------------------|-----------------------------| +| Message Type | M | | 9.2.2.24 | | YES | reject | +| Transaction ID | M | | 9.2.2.28 | | – | | +| Cause | M | | 9.2.2.3 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.2.4 | | YES | ignore | + +## 9.1.6 INFORMATION EXCHANGE INITIATION REQUEST + +Table 10 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------------------------------------|----------|-------|--------------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.2.24 | | YES | reject | +| Transaction ID | M | | 9.2.2.28 | | – | | +| Information Exchange ID | M | | 9.2.2.19 | | YES | reject | +| CHOICE Information Exchange Object Type | M | | | | YES | reject | +| > Reference Position | | | | | – | | +| >> Reference Position Estimate/UE Initial Position | M | | Geographical Area 9.2.2.6 | For RNC-centric mode. | – | | +| > Additional Information Exchange Object Types | | | | | | | +| >> Reference Position UC-ID | | | | | | | +| >>> UTRAN Cell Identifier/UE Initial Position | M | | UTRAN Cell Identifier 9.2.2.37 | For SAS-centric mode. | YES | reject | +| >> Cell-ID Measured Results Sets | | | | | | | +| >>> Cell-ID Measured Results Sets | M | | 9.2.2.152 | | YES | ignore | +| Information Type | M | | 9.2.2.22 | | YES | reject | +| Information Report Characteristics | M | | 9.2.2.21 | | YES | reject | +| GPS-UTRAN Time Relationship Uncertainty | C-GPS | | 9.2.2.18 | | YES | reject | +| GANSS-UTRAN Time Relationship Uncertainty | C-GANSS | | 9.2.2.121 | | YES | reject | +| IMSI | O | | 9.2.2.158 | | YES | ignore | +| IMEI | O | | 9.2.2.159 | | YES | ignore | + +Table 11 + +| Condition | Explanation | +|-----------|--------------------------------------------------------------------------------------------------------------------| +| GPS | The IE shall be present if the information requested in the Information Type IE contains GPS-related data | +| GANSS | The IE shall be present if the information requested in the Information Type IE contains GANSS-related data | + +Table 11a + +| Range bound | Explanation | +|---------------------|-----------------------------------------------------------------------------------------------------------| +| maxNoOfMeasurements | Maximum number of Measurements of Cell-ID Measured Results Sets. The value for maxNoOfMeasurements is 16. | + +### 9.1.7 INFORMATION EXCHANGE INITIATION RESPONSE + +Table 12 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.2.24 | | YES | reject | +| Transaction ID | M | | 9.2.2.28 | | – | | +| Information Exchange ID | M | | 9.2.2.19 | | YES | ignore | +| CHOICE Information Exchange Object Type | O | | | | YES | ignore | +| >Reference Position | | | | | – | | +| >>Requested Data Value | M | | 9.2.2.26 | | – | | +| Criticality Diagnostics | O | | 9.2.2.4 | | YES | ignore | + +### 9.1.8 INFORMATION EXCHANGE INITIATION FAILURE + +Table 13 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.2.24 | | YES | reject | +| Transaction ID | M | | 9.2.2.28 | | – | | +| Information Exchange ID | M | | 9.2.2.19 | | YES | ignore | +| Cause | M | | 9.2.2.3 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.2.4 | | YES | ignore | + +### 9.1.9 INFORMATION REPORT + +Table 14 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.2.24 | | YES | ignore | +| Transaction ID | M | | 9.2.2.28 | | – | | +| Information Exchange ID | M | | 9.2.2.19 | | YES | ignore | +| CHOICE Information Exchange Object Type | M | | | | YES | ignore | +| >Reference Position | | | | | – | | +| >>Requested Data Value Information | M | | 9.2.2.27 | | – | | + +### 9.1.10 INFORMATION EXCHANGE TERMINATION REQUEST + +Table 15 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.2.24 | | YES | ignore | +| Transaction ID | M | | 9.2.2.28 | | – | | +| Information Exchange ID | M | | 9.2.2.19 | | YES | ignore | + +## 9.1.11 INFORMATION EXCHANGE FAILURE INDICATION + +Table 16 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.2.24 | | YES | ignore | +| Transaction ID | M | | 9.2.2.28 | | – | | +| Information Exchange ID | M | | 9.2.2.19 | | YES | ignore | +| Cause | M | | 9.2.2.3 | | YES | ignore | + +## 9.1.12 ERROR INDICATION + +Table 17 + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.2.24 | | YES | ignore | +| Transaction ID | M | | 9.2.2.28 | | – | | +| Cause | O | | 9.2.2.3 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.2.4 | | YES | ignore | + +## 9.1.13 POSITION INITIATION REQUEST + +Table 17a + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.2.24 | | YES | reject | +| Transaction ID | M | | 9.2.2.28 | | – | | +| Request Type | M | | 9.2.2.50 | | YES | reject | +| UE Positioning Capability | M | | 9.2.2.51 | | YES | reject | +| UTRAN Cell Identifier | M | | 9.2.2.37 | | YES | reject | +| Vertical Accuracy Code | O | | 9.2.2.39 | | YES | ignore | +| Response Time | O | | 9.2.2.52 | | YES | ignore | +| Positioning Priority | O | | 9.2.2.53 | | YES | ignore | +| Client Type | O | | 9.2.2.54 | | YES | ignore | +| Include Velocity | O | | 9.2.2.97 | | YES | ignore | +| Periodic Location Info | O | | 9.2.2.107 | | YES | ignore | +| IMSI | O | | 9.2.2.158 | | YES | ignore | +| IMEI | O | | 9.2.2.159 | | YES | ignore | + +## 9.1.14 POSITION INITIATION RESPONSE + +Table 17b + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------|----------|-------|------------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.2.24 | | YES | reject | +| Transaction ID | M | | 9.2.2.28 | | – | | +| UE Position Estimate | M | | Geographical Area
9.2.2.6 | | YES | reject | +| Position Data | M | | 9.2.2.65 | | YES | ignore | +| Accuracy Fulfilment Indicator | O | | 9.2.2.40 | | YES | ignore | +| Velocity Estimate | O | | 9.2.2.98 | | YES | ignore | + +## 9.1.15 POSITION INITIATION FAILURE + +**Table 17c** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.2.24 | | YES | reject | +| Transaction ID | M | | 9.2.2.28 | | – | | +| Cause | M | | 9.2.2.3 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.2.4 | | YES | ignore | + +## 9.1.16 POSITION ACTIVATION REQUEST + +**Table 17d** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------|----------|-------|---------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.2.2.24 | | YES | reject | +| Transaction ID | M | | 9.2.2.28 | | – | | +| Positioning Method | M | | 9.2.2.55 | | YES | reject | +| RNC Response Time | M | | Positioning Response Time
9.2.2.69 | Indicates the interval allowed for a RNC response, or the periodic reporting interval if Amount of Reporting IE is present. | YES | ignore | +| Positioning Priority | O | | 9.2.2.53 | | YES | ignore | +| Environment Characterisation | O | | 9.2.2.62 | | YES | ignore | +| U-TDOA Positioning | | 0..1 | | Only present if Selected Positioning Method indicates UTDOA | YES | reject | +| >U-TDOA Bit Count | M | | 9.2.2.56 | Used if UE is in CELL_FACH mode | – | | +| >U-TDOA Time Interval | M | | 9.2.2.57 | Used if UE is in CELL_FACH mode | – | | +| GPS Positioning | | 0..1 | | Only present if Selected Positioning Method indicates A-GPS or GNSS when GPS is one of the allowed GNSS methods | YES | reject | +| >GPS Positioning Instructions | M | | 9.2.2.101 | | – | | +| >Requested Data Value | O | | 9.2.2.26 | | – | | +| OTDOA Assistance Data | | 0..1 | | Only present if Selected Positioning Method indicates OTDOA | YES | reject | +| >UE Positioning OTDOA Assistance data | M | | 9.2.2.59 | | – | | +| Include Velocity | O | | 9.2.2.97 | | YES | ignore | +| Amount of Reporting | O | | 9.2.2.108 | Amount of reports for periodic reporting. | YES | ignore | +| Cell-ID Positioning | | 0..1 | | Only present if Selected Positioning Method indicates | YES | ignore | + +| | | | | | | | +|------------------------------------|---|------|-----------|---------------------------------------------------------------------------|-----|--------| +| | | | | Cell-ID | | | +| >Requested Cell-ID
Measurements | M | | 9.2.2.112 | | – | | +| GANSS Positioning | | 0..1 | | Only present
if Selected
Positioning
Method
indicates
GNSS | YES | reject | +| >GANSS Positioning
Instructions | M | | 9.2.2.120 | | – | | +| >Requested Data Value | O | | 9.2.2.26 | | – | | + +## 9.1.17 POSITION ACTIVATION RESPONSE + +**Table 17e** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------|----------|------------------------------|------------------------------------------------------|-------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.2.2.24 | | YES | reject | +| Transaction ID | M | | 9.2.2.28 | | – | | +| UE Position Estimate Info | O | | 9.2.2.102 | Position information for UE based positioning methods | YES | ignore | +| GPS Measured Results | | 0.. | | | GLOBAL | reject | +| >GPS Measured Results | M | | 9.2.2.12 | | – | | +| Cell-ID Measured Results Sets | | 0.. | | | GLOBAL | reject | +| >Cell-ID Measured Results Info List | M | | 9.2.2.31 | | – | | +| OTDOA Measured Results Sets | | 0.. | | | GLOBAL | reject | +| >OTDOA Measured Results Info List | M | | 9.2.2.32 | | – | | +| UTDOA Group | O | | 9.2.2.74 | | YES | reject | +| Velocity Estimate | O | | 9.2.2.98 | | YES | ignore | +| Measurement Instructions Used | O | | 9.2.2.109 | | YES | ignore | +| GANSS Measured Results | | 0.. | | | GLOBAL | reject | +| >GANSS Measured Results | M | | 9.2.2.117 | | – | | +| Required GPS Assistance Data | O | | Additional GPS Assistance Data Required 9.2.2.128 | | YES | ignore | +| Required GANSS Assistance Data | O | | Additional GANSS Assistance Data Required 9.2.2.129 | | YES | ignore | +| OTDOA Reference Cell Info | O | | OTDOA Reference Cell Info SAS-centric mode 9.2.2.153 | | YES | reject | +| Cell-ID IRAT Measured Results Sets | | 0.. | | | GLOBAL | ignore | +| >IRAT Measured Results Info List | M | | 9.2.2.155 | | – | | +| AddPos Measured Results | | 0.. | | | GLOBAL | reject | +| >AddPos Measured | M | | 9.2.2.162 | | – | | + +| | | | | | | | +|---------|--|--|--|--|--|--| +| Results | | | | | | | +|---------|--|--|--|--|--|--| + +Table 17f + +| Range bound | Explanation | +|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| maxNoOfSets | Maximum number of sets of Measured Results included in the Position Activation Response message. The value for maxNoOfSets is 3. | +| maxNoOfMeasurements | Maximum number of Measurements of Cell-ID Measured Results Info List and OTDOA Measured Results Info List included in the Position Activation Response message. The value for maxNoOfMeasurements is 16. | +| maxNoOfIRATMeasurements | Maximum number of IRATs for which Measurements of Cell-ID IRAT Measured Results Info List may be included in the Position Activation Response message. The value for maxNoOfIRATMeasurements is 16. | +| maxAddPos | Maximum number of Additional Positioning Measured Results included in the Position Activation Response message. The value for maxAddPos is 8. | + +## 9.1.18 POSITION ACTIVATION FAILURE + +Table 17g + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.2.24 | | YES | reject | +| Transaction ID | M | | 9.2.2.28 | | – | | +| Cause | M | | 9.2.2.3 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.2.4 | | YES | ignore | + +## 9.1.19 POSITION PARAMETER MODIFICATION + +Table 17h + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.2.24 | | YES | ignore | +| Transaction ID | M | | 9.2.2.28 | | – | | +| UTRAN Cell Identifier | O | | 9.2.2.37 | | YES | reject | +| UTDOA Group | O | | 9.2.2.74 | | YES | reject | +| RRC State Change | O | | 9.2.2.110 | | YES | ignore | + +## 9.1.20 ABORT + +Table 17i + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.2.24 | | YES | ignore | +| Transaction ID | M | | 9.2.2.28 | | – | | +| Cause | M | | 9.2.2.3 | | YES | ignore | + +## 9.1.21 POSITION PERIODIC REPORT + +Table 17.k + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------|----------|-----------------------------|------------------------------------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.2.24 | | YES | ignore | +| Transaction ID | M | | 9.2.2.28 | | – | | +| UE Position Estimate Info | O | | 9.2.2.102 | | YES | ignore | +| Velocity Estimate | O | | 9.2.2.98 | | YES | ignore | +| GPS Measured Results | | 0.. | | | GLOBAL | ignore | +| >GPS Measured Results | M | | 9.2.2.12 | | – | | +| Cell-ID Measured Results Sets | | 0.. | | | GLOBAL | ignore | +| >Cell-ID Measured Results Info List | M | | 9.2.2.31 | | – | | +| OTDOA Measured Results Sets | | 0.. | | | GLOBAL | ignore | +| >OTDOA Measured Results Info List | M | | 9.2.2.32 | | – | | +| Cause | O | | 9.2.2.3 | | YES | ignore | +| GANSS Measured Results | | 0.. | | | GLOBAL | ignore | +| >GANSS Measured Results | M | | 9.2.2.117 | | – | | +| Required GPS Assistance Data | O | | Additional GPS Assistance Data Required 9.2.2.128 | | YES | ignore | +| Required GANSS Assistance Data | O | | Additional GANSS Assistance Data Required 9.2.2.129 | | YES | ignore | +| OTDOA Reference Cell Info | O | | OTDOA Reference Cell Info SAS-centric mode 9.2.2.153 | | YES | reject | +| Cell-ID IRAT Measured Results Sets | | 0.. | | | GLOBAL | ignore | +| >IRAT Measured Results Info List | M | | 9.2.2.155 | | – | | +| AddPos Measured Results | | 0.. | | | GLOBAL | ignore | +| >AddPos Measured Results | M | | 9.2.2.162 | | - | | + +**Table 17.l** + +| Range bound | Explanation | +|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| maxNoOfSets | Maximum number of sets of Measured Results included in the Position Periodic Report message. The value for maxNoOfSets is 3. | +| maxNoOfMeasurements | Maximum number of Measurements of Cell-ID Measured Results Info List and OTDOA Measured Results Info List included in the Position Periodic Report message. The value for maxNoOfMeasurements is 16. | +| maxNoOfIRATMeasurements | Maximum number of IRATs for which Measurements of Cell-ID IRATMeasured Results Info List may be included in the Position Periodic Report message. The value for maxNoOfIRATMeasurements is 16. | +| maxAddPos | Maximum number of Additional Positioning Measured Results included in the Position Periodic Report message. The value for maxAddPos is 8. | + +## 9.1.22 POSITION PERIODIC RESULT + +**Table 17.m** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------|----------|-------|---------------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.2.24 | | YES | ignore | +| Transaction ID | M | | 9.2.2.28 | | – | | +| UE Position Estimate | O | | Geographical Area 9.2.2.6 | | YES | ignore | +| Velocity Estimate | O | | 9.2.2.98 | | YES | ignore | +| Position Data | O | | 9.2.2.65 | | YES | ignore | +| Accuracy Fulfilment Indicator | O | | 9.2.2.40 | | YES | ignore | +| Cause | O | | 9.2.2.3 | | YES | ignore | + +## 9.1.23 POSITION PERIODIC TERMINATION + +**Table 17.n** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.2.24 | | YES | ignore | +| Transaction ID | M | | 9.2.2.28 | | – | | +| Periodic Position Termination Cause | O | | 9.2.2.111 | | YES | ignore | + +## 9.2 Information Element Functional Definitions and Contents + +### 9.2.1 General + +Clause 9.2 presents the PCAP IE definitions in tabular format. The corresponding ASN.1 definitions are presented in clause 9.3. In case there is contradiction between the tabular format in clause 9.2 and the ASN.1 definition, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional elements, where the tabular format shall take precedence. + +When specifying information elements which are to be represented by bitstrings, if not otherwise specifically stated in the semantics description of the concerned IE or elsewhere, the following principle applies with regards to the ordering of bits: + +- The first bit (leftmost bit) contains the most significant bit (MSB); +- The last bit (rightmost bit) contains the least significant bit (LSB); + +- When importing bitstrings from other specifications, the first bit of the bitstring contains the first bit of the concerned information; + +## 9.2.2 Radio Network Layer Related IEs + +### 9.2.2.1 Almanac and Satellite Health SIB + +**Table 18** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------|----------|-------|--------------------------|----------------------------------------------------------------------------------| +| GPS Almanac and Satellite Health | M | | 9.2.2.9 | | +| SatMask | M | | BIT STRING (SIZE(1..32)) | indicates the satellites that contain the pages being broadcast in this data set | +| LSB TOW | M | | BIT STRING (SIZE (8)) | | + +### 9.2.2.2 Altitude and direction + +**Table 19** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------|----------|-------|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Direction of Altitude | M | | ENUMERATED (Height, Depth) | | +| Altitude | M | | INTEGER ( $0..2^{15}-1$ ) | The relation between the value (N) and the altitude (a) in meters it describes is $N \leq a < N+1$ , except for $N=2^{15}-1$ for which the range is extended to include all greater values of (a). | + +### 9.2.2.3 Cause + +The purpose of the cause information element is to indicate the reason for a particular event for the whole protocol. + +**Table 20** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------|----------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| CHOICE Cause Group | | | | | +| > Radio Network Layer | | | | | +| >>Radio Network Layer Cause | M | | ENUMERATED
(invalid reference information,
information temporarily not available,
information provision not supported for
the object,
position calculation error: invalid GPS
measured results,
...,
position calculation error: invalid Cell-
ID measured results,
position calculation error: invalid
OTDOA measured results,
position calculation error: A-GPS
positioning method not supported,
position calculation error: Cell-ID
positioning method not supported,
position calculation error: OTDOA
positioning method not supported,
Initial UE Position Estimate missing,
position calculation error: invalid U-
TDOA measured results,
position calculation error: U-TDOA
positioning method not supported,
position calculation error: U-TDOA
positioning method not supported in
specified UTRAN cell,
positioning method not supported,
loss of contact with UE,
SAS unable to perform U-TDOA
positioning within Response Time,
Location measurement failure,
UE Positioning Error: Not enough
OTDOA cells,
UE Positioning Error: Not enough GPS
Satellites,
UE Positioning Error: Reference Cell
not serving cell,
UE Positioning Error: Not
Accomplished GPS Timing of Cell
Frames,
UE Positioning Error: Undefined Error,
position calculation error: invalid
Galileo measured results,
position calculation error: A-Galileo
positioning method not supported,
UE Positioning Error: Not enough
Galileo Satellites,
UE Positioning Error: Not
Accomplished Galileo Timing of Cell
Frames,
UE Positioning Error: Assistance Data
Missing
position calculation error: invalid
GLONASS measured results,
position calculation error: invalid
GANSS measured results,
position calculation error: A-GANSS
positioning method not supported,
UE Positioning Error: Not enough
GANSS Satellites,
UE Positioning Error: Not
Accomplished GANSS Timing of Cell
Frames,
position calculation error: invalid BDS
measured results,
UE Positioning Error: Not enough BDS
Satellites,
position calculation error: A-BDS
positioning method not supported
) | | +| > Transport Layer | | | | | +| >>Transport Layer Cause | M | | ENUMERATED | | + +| | | | | | +|-------------------------------|---|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | | | (Transport Resource Unavailable, Unspecified, ...) | | +| >Protocol | | | | | +| >>Protocol Cause | M | | ENUMERATED
(Transfer Syntax Error, Abstract Syntax Error (Reject), Abstract Syntax Error (Ignore and Notify), Message not Compatible with Receiver State, Semantic Error, Unspecified, Abstract Syntax Error (Falsely Constructed Message), ...) | | +| >Misc | | | | | +| >>Misc Cause | M | | ENUMERATED
(Processing Overload, Hardware Failure, O&M Intervention, Unspecified, ...) | | + +The meaning of the different cause values is described in the following table. In general, "not supported" cause values indicate that the concerning capability is missing. On the other hand, "not available" cause values indicate that the concerning capability is present, but insufficient resources were available to perform the requested action. + +**Table 21** + +| Radio Network Layer cause | Meaning | +|---------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Invalid reference information | The reference information (GPS-UTRAN Time Relationship Uncertainty and/or Initial UE Position Estimate) provided by the RNC are invalid | +| Information temporarily not available | The information requested by RNC is temporarily not available | +| Information Provision not supported for the object | The SAS does not support provision of the requested information for the concerned object types | +| Position calculation error: invalid GPS measured results | The SAS cannot calculate position due to invalid GPS measured results | +| Position calculation error: invalid Cell-ID measured results | The SAS cannot calculate position due to invalid Cell-ID measured results | +| Position calculation error: invalid OTDOA measured results | The SAS cannot calculate position due to invalid OTDOA measured results | +| Position calculation error: A-GPS positioning method not supported | The SAS cannot calculate position because it does not support the A-GPS positioning method | +| Position calculation error: Cell-ID positioning method not supported | The SAS cannot calculate position because it does not support the Cell-ID positioning method | +| Position calculation error: OTDOA positioning method not supported | The SAS cannot calculate position because it does not support the OTDOA positioning method | +| Position calculation error: invalid U-TDOA measured results | The SAS cannot calculate position due to invalid U-TDOA measured results | +| Position calculation error: U-TDOA positioning method not supported | The SAS cannot calculate position because it does not support the U-TDOA positioning method | +| Position calculation error: U-TDOA positioning method not supported in specified UTRAN cell | The SAS cannot calculate position because it does not support the U-TDOA positioning method in the specified UTRAN cell | +| Positioning method not supported | The RNC does not support the requested positioning method | +| Loss of contact with UE | The RNC reports that it has lost contact with the UE | +| SAS unable to perform U-TDOA positioning within Response Time | The SAS did not send a U-TDOA position estimate within the interval defined by the Response Time IE | +| Location measurement failure | The SRNC cannot deliver the requested positioning measurement due to measurement failure. | +| UE Positioning Error: Not enough OTDOA cells | The SRNC cannot deliver the requested positioning measurement due to UE positioning error reported by the UE with error reason "Not enough OTDOA cells". | +| UE Positioning Error: Not enough GPS Satellites | The SRNC cannot deliver the requested positioning measurement due to UE positioning error reported by the UE with error reason "Not enough GPS Satellites". | +| UE Positioning Error: Reference Cell not serving cell | The SRNC cannot deliver the requested positioning measurement due to UE positioning error reported by the UE with error reason "Reference Cell not serving cell" | +| UE Positioning Error: Not Accomplished GPS Timing of Cell Frames | The SRNC cannot deliver the requested positioning measurement due to UE positioning error reported by the UE with error reason "Not Accomplished GPS Timing of Cell Frames" | +| UE Positioning Error: Undefined Error | The SRNC cannot deliver the requested positioning measurement due to UE positioning error reported by the UE with error reason "Undefined Error" | +| Position calculation error: invalid Galileo measured results | The SAS cannot calculate position due to invalid Galileo measured results | +| Position calculation error: A-Galileo positioning method not supported | The SAS cannot calculate position because it does not support the A-Galileo positioning method | +| UE Positioning Error: Not enough Galileo Satellites | The SRNC cannot deliver the requested positioning measurement due to UE positioning error reported by the UE with error reason "Not enough Galileo Satellites". | +| UE Positioning Error: Not Accomplished Galileo Timing of Cell Frames | The SRNC cannot deliver the requested positioning measurement due to UE positioning error reported by the UE with error reason "Not Accomplished Galileo Timing of Cell Frames" | +| UE Positioning Error: Assistance Data Missing | The SRNC cannot deliver the requested positioning measurement due to UE positioning error reported by the UE with error reason "Assistance Data Missing" | +| Position calculation error: invalid GLONASS measured results | The SAS cannot calculate position due to invalid GLONASS measured results | +| Position calculation error: invalid GANSS measured results | The SAS cannot calculate position due to invalid GANSS measured results | +| Position calculation error: A-GANSS positioning method not | The SAS cannot calculate position because it does not support any A-GANSS positioning method | + +| | | +|--------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| supported | | +| UE Positioning Error: Not enough GANSS Satellites | The SRNC cannot deliver the requested positioning measurement due to UE positioning error reported by the UE with error reason "Not Enough GANSS Satellites". | +| UE Positioning Error: Not Accomplished GANSS Timing of Cell Frames | The SRNC cannot deliver the requested positioning measurement due to UE positioning error reported by the UE with error reason "Not Accomplished GANSS Timing of Cell Frames". | +| Position calculation error: invalid BDS measured results | The SAS cannot calculate position due to invalid BDS measured results | +| UE Positioning Error: Not enough BDS Satellites | The SRNC cannot deliver the requested positioning measurement due to UE positioning error reported by the UE with error reason "Not Enough BDS Satellites". | +| Position calculation error: A-BDS positioning method not supported | The SAS cannot calculate position because it does not support any A-BDS positioning method | + +Table 22 + +| Transport Network Layer cause | Meaning | +|--------------------------------|---------------------------------------------------------------------------------------------------------| +| Transport resource unavailable | The required transport resources are not available | +| Unspecified | Sent when none of the above cause values applies but still the cause is Transport Network Layer related | + +Table 23 + +| Protocol cause | Meaning | +|-----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Abstract Syntax Error (Reject) | The received message included an abstract syntax error and the concerning criticality indicated "reject" (see clause 10.3) | +| Abstract Syntax Error (Ignore and Notify) | The received message included an abstract syntax error and the concerning criticality indicated "ignore and notify" (see clause 10.3) | +| Abstract syntax error (falsely constructed message) | The received message contained IEs or IE groups in wrong order or with too many occurrences (see clause 10.3) | +| Message not Compatible with Receiver State | The received message was not compatible with the receiver state (see clause 10.4) | +| Semantic Error | The received message included a semantic error (see clause 10.4) | +| Transfer Syntax Error | The received message included a transfer syntax error (see clause 10.2) | +| Unspecified | Sent when none of the above cause values applies but still the cause is Protocol related | + +Table 24 + +| Miscellaneous cause | Meaning | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Processing Overload | RNC/SAS processing overload | +| Hardware Failure | RNC/SAS hardware failure | +| O&M Intervention | Operation and Maintenance intervention related to RNC/SAS equipment | +| Unspecified | Sent when none of the above cause values applies and the cause is not related to any of the categories Radio Network Layer, Transport Network Layer or Protocol | + +#### 9.2.2.4 Criticality Diagnostics + +The *Criticality Diagnostics* IE is sent by the RNC or the SAS when parts of a received message have not been comprehended or are missing. It contains information about which IE was not comprehended or is missing. + +For further details on how to use the *Criticality Diagnostics* IE, see annex A. + +Table 25 + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------------------|----------|---------------------|------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Procedure Code | O | | INTEGER (0..255) | | +| Triggering Message | O | | ENUMERATED (initiating message, successful outcome, unsuccessful outcome, outcome) | The Triggering Message is used only if the Criticality Diagnostics is part of Error Indication. | +| Procedure Criticality | O | | ENUMERATED (reject, ignore, notify) | This Procedure Criticality is used for reporting the Criticality of the Triggering message (Procedure). | +| Transaction ID | O | | 9.2.2.28 | | +| Information Element Criticality Diagnostics | | 0.. | | | +| >IE Criticality | M | | ENUMERATED (reject, ignore, notify) | The IE Criticality is used for reporting the criticality of the triggering IE. The value "ignore" shall never be used. | +| >IE Id | M | | INTEGER (0..65535) | The IE Id of the not understood or missing IE as defined in the ASN.1 part of the specification. | +| >Repetition Number | O | | INTEGER (0..255) |

The Repetition Number IE gives

  • - in case of a not understood IE:
    The number of occurrences of the reported IE up to and including the not understood occurrence
  • - in case of a missing IE:
    The number of occurrences up to but not including the missing occurrence.

Note: All the counted occurrences of the reported IE must have the same top-down hierarchical message structure of IEs with assigned criticality above them.

| +| >Message Structure | O | | 9.2.2.23 | The Message Structure IE describes the structure where the not understood or missing IE was detected. This IE is included if the not understood IE is not the top level of the message. | +| >Type of Error | M | | ENUMERATED (not understood, missing, ...) | | + +**Table 26** + +| Range bound | Explanation | +|---------------|---------------------------------------------------------------------------------------------------------------| +| maxnooferrors | Maximum number of IE errors allowed to be reported with a single message. The value for maxnooferrors is 256. | + +### 9.2.2.5 DGPS Corrections + +This IE contains DGPS corrections, which may be employed to compensate for ranging errors due to atmospheric delay, orbital modelling, and satellite clock drift. + +**Table 27** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|-----------------|--------------|-------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| GPS TOW sec | M | | INTEGER (0..604799) | In seconds GPS time-of-week when the DGPS corrections were calculated | – | | +| Status/Health | M | | ENUMERATED (UDRE scale 1.0, UDRE scale 0.75, UDRE scale 0.5, UDRE scale 0.3, UDRE scale 0.2, UDRE scale 0.1, no data, invalid data) | | – | | +| DGPS information | C-Status/Health | 1.. | | | – | | +| >SatID | M | | INTEGER (0..63) | Identifies the satellite and is equal to (SV ID No - 1) where SV ID No is defined in ICD-GPS-200 [10]. | – | | +| >IODE | M | | INTEGER (0..255) | | – | | +| >UDRE | M | | ENUMERATED (UDRE $\leq$ 1.0 m, 1.0m < UDRE $\leq$ 4.0m, 4.0m < UDRE $\leq$ 8.0m, 8.0m < UDRE) | The value in this field shall be multiplied by the UDRE Scale Factor in the IE Status/Health to determine the final UDRE estimate for the particular satellite. | – | | +| >PRC | M | | INTEGER (-2047..2047.) | Scaling factor 0.32 Meters | – | | +| >Range Rate Correction | M | | INTEGER (-127..127) | Scaling factor 0.032 meters/sec | – | | +| >DGNSS Validity Period | O | | 9.2.2.154 | | YES | ignore | + +**Table 28** + +| Condition | Explanation | +|---------------|-----------------------------------------------------------------------------------------------------| +| Status/Health | This IE shall be present if the Status/Health IE is not equal to "no data" or "invalid data" | + +**Table 29** + +| Range bound | Explanation | +|-------------|------------------------------------------------------------------------------------------------| +| maxSat | Maximum number of satellites for which data is included in this IE. The value of maxSat is 16. | + +### 9.2.2.6 Geographical Area + +*Geographical Area* IE is used to identify an area using geographical coordinates. The reference system is the same as the one used in TS 23.032 [11]. + +**Table 30** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------------------------|----------|--------------------|----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CHOICE Geographical Area | | | | | +| >Point | | | | Ellipsoid point | +| >>Geographical Coordinates | M | | 9.2.2.7 | | +| >Point With Uncertainty | | | | Ellipsoid point with uncertainty circle | +| >>Geographical Coordinates | M | | 9.2.2.7 | | +| >>Uncertainty Code | M | | INTEGER ( 0..127) | The uncertainty "r" expressed in meters is derived from the "Uncertainty Code" k by $r = 10 \times (1.1^k - 1)$ | +| >Polygon | | | | List of Ellipsoid points | +| >>Polygon | | 1.. | | | +| >>>Geographical Coordinates | M | | 9.2.2.7 | | +| >Ellipsoid point with uncertainty Ellipse | | | | | +| >>Geographical Coordinates | M | | 9.2.2.7 | | +| >>Uncertainty Ellipse | M | | 9.2.2.30 | | +| >>Confidence | M | | INTEGER ( 0..100) | In percentage | +| >Ellipsoid point with altitude | | | | | +| >>Geographical Coordinates | M | | 9.2.2.7 | | +| >>Altitude and direction | M | | 9.2.2.2 | | +| >Ellipsoid point with altitude and uncertainty Ellipsoid | | | | | +| >>Geographical Coordinates | M | | 9.2.2.7 | | +| >>Altitude and direction | M | | 9.2.2.2 | | +| >>Uncertainty Ellipse | M | | 9.2.2.30 | | +| >>Uncertainty Altitude | M | | INTEGER ( 0..127) | The uncertainty altitude "h" expressed in metres is derived from the "Uncertainty Altitude" k, by: $h = 45 \times (1.025^k - 1)$ | +| >>Confidence | M | | INTEGER ( 0..100) | In percentage | +| >Ellipsoid Arc | | | | | +| >>Geographical Coordinates | M | | 9.2.2.7 | | +| >>Inner radius | M | | INTEGER ( 0..2 16 -1) | The relation between the value (N) and the radius (r) in meters it describes is $5N \leq r < 5(N+1)$ , except for $N = 2^{16} - 1$ for which the range is extended to include all greater values of (r). | +| >>Uncertainty radius | M | | INTEGER ( 0..127) | The uncertainty "r" is derived from the "Uncertainty radius" k by $r = 10 \times (1.1^k - 1)$ | +| >>Offset angle | M | | INTEGER ( 0..179) | The relation between the value (N) and the angle (a) in degrees it describes is $2N \leq a < 2(N+1)$ | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------| +| >>Included angle | M | | INTEGER ( 0..179) | The relation between the value (N) and the angle (a) in degrees it describes is $2N < a \leq 2(N+1)$ | +| >>Confidence | M | | INTEGER ( 0..100) | | + +Table 31 + +| Range bound | Explanation | +|---------------|------------------------------------------------| +| maxnoofPoints | Maximum no. of points in polygon. Value is 15. | + +### 9.2.2.7 Geographical Coordinates + +This IE contains the geographical coordinates. + +Table 32 + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------|----------|-------|--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------| +| Latitude Sign | M | | ENUMERATED (North, South) | | +| Degrees Of Latitude | M | | INTEGER ( 0..2 23 -1) | The IE value (N) is derived by this formula: $N \leq 2^{23} \times X / 90 < N+1$
X being the latitude in degree (0°.. 90°) | +| Degrees Of Longitude | M | | INTEGER ( -2 23 ..2 23 -1) | The IE value (N) is derived by this formula: $N \leq 2^{24} \times X / 360 < N+1$
X being the longitude in degree (-180°..+180°) | + +### 9.2.2.8 GPS Acquisition Assistance + +This IE contains parameters that enable fast acquisition of the GPS signals in UE-assisted GPS positioning. + +**Table 33** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------|----------|-------------|---------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| GPS TOW msec | M | | INTEGER
(0..6.048*10 8 -1) | GPS Time of Week in milliseconds (rounded down to the nearest millisecond unit). | – | | +| Satellite information | | 1.. | | | – | | +| >SatID | M | | INTEGER
(0..63) | Identifies the satellite and is equal to (SV ID No - 1) where SV ID No is defined in ICD-GPS-200 [10]. | – | | +| >Doppler (0 th order term) | M | | INTEGER
(-2048..2047) | Scaling factor 2.5Hz | – | | +| >Extra Doppler | | 0..1 | | | – | | +| >>Doppler (1 st order term) | M | | INTEGER
(-42..21) | Scaling factor 1/42 | – | | +| >>Doppler Uncertainty | M | | ENUMERATED
(12.5,25,50,100,200,...) | In Hz | – | | +| >Code Phase | M | | INTEGER
(0..1022) | In Chips, specifies the centre of the search window | – | | +| >Integer Code Phase | M | | INTEGER
(0..19) | Number of 1023 chip segments | – | | +| >GPS Bit number | M | | INTEGER
(0..3) | Specifies GPS bit number (20 1023 chip segments) | – | | +| >Code Phase Search Window | M | | ENUMERATED
(1023,1,2,3,4,6,8,12,16,24,32,48,64,96,128,192) | Specifies the width of the search window. | – | | +| >Azimuth and Elevation | | 0..1 | | | – | | +| >>Azimuth | M | | INTEGER
(0..31) | Scaling factor 11.25 Degrees | – | | +| >>Elevation | M | | INTEGER
(0..7) | Scaling factor 11.25 Degrees | – | | +| >>Azimuth and Elevation LSB | | 0..1 | | | YES | ignore | +| >>>Azimuth LSB | M | | INTEGER
(0..15) | Scale factor 0.703125. The full satellite azimuth is constructed as “Azimuth” × 11.25 + “Azimuth LSB” × 0.703125 degrees. | – | | +| >>>Elevation LSB | M | | INTEGER
(0..15) | Scale factor 0.703125. The full | – | | + +| | | | | | | | +|----------------------------------------|---|------|--------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| | | | | satellite elevation is constructed as "Elevation" × 11.25 + "Elevation LSB" × 0.703125 degrees. | | | +| >Extra Doppler Extension | | 0..1 | | If this field is present, the "Extra Doppler" field should not be present. | YES | ignore | +| >>Doppler (1 st order term) | M | | INTEGER (-42..21) | Scaling factor 1/42 | – | | +| >>Doppler Uncertainty Extension | M | | ENUMERATED (300, 400, 500, 600, 'No Information', ...) | In Hz | – | | +| UTRAN GPS Reference Time | O | | 9.2.2.103 | This IE may only be present if SAS operates in SAS-centric mode. | YES | ignore | +| GPS Reference Time Uncertainty | O | | 9.2.2.132 | This IE may only be present if SAS operates in SAS-centric mode. | YES | ignore | +| Confidence | O | | INTEGER (0..100) | Confidence level (in percent) of the reference location area or volume used to calculate the Satellite information parameters (search windows). | YES | ignore | + +Table 34 + +| Range bound | Explanation | +|-------------|------------------------------------------------------------------------------------------------| +| mMaxSat | Maximum number of satellites for which data is included in this IE. The value of maxSat is 16. | + +### 9.2.2.9 GPS Almanac and Satellite Health + +This IE contains a reduced-precision subset of the clock and ephemeris parameters. + +Table 35 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------|----------|---------------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| WN a | M | | BIT STRING (SIZE(8)) | | – | | +| Satellite information | | 1.. | | | – | | +| >DataID | M | | BIT STRING (SIZE(2)) | See ICD-GPS-200 [10] | – | | +| >SatID | M | | INTEGER (0..63) | Identifies the satellite and is equal to (SV ID No - 1) where SV ID No is defined in ICD-GPS-200 [10]. | – | | +| >e | M | | BIT STRING (SIZE(16)) | Eccentricity (ICD-GPS-200 [10]) | – | | +| >t oa | M | | BIT STRING (SIZE(8)) | Reference Time of Almanac (ICD-GPS-200 [10]) | – | | +| >δi | M | | BIT STRING (SIZE(16)) | Correction to Inclination (semi-circles) (ICD-GPS-200 [10]) | – | | +| >OMEGADOT | M | | BIT STRING (SIZE(16)) | Rate of Right Ascension (semi-circles/sec) (ICD-GPS-200 [10]) | – | | +| >SV Health | M | | BIT STRING (SIZE(8)) | ICD-GPS-200 [10] | – | | +| >A 1/2 | M | | BIT STRING (SIZE(24)) | Semi-Major Axis (meters) 1/2 (ICD-GPS-200 [10]) | – | | +| >OMEGA 0 | M | | BIT STRING (SIZE(24)) | Longitude of Ascending Node of Orbit Plane at Weekly Epoch (semi-circles) (ICD-GPS-200 [10]) | – | | +| >M 0 | M | | BIT STRING (SIZE(24)) | Mean Anomaly at Reference Time (semi-circles) (ICD-GPS-200 [10]) | – | | +| >ω | M | | BIT STRING (SIZE(24)) | Argument of Perigee (semi-circles) (ICD-GPS-200 [10]) | – | | +| >af 0 | M | | BIT STRING (SIZE(11)) | apparent clock correction (ICD-GPS-200 [10]) | – | | +| >af 1 | M | | BIT STRING (SIZE(11)) | apparent clock correction (ICD-GPS-200 [10]) | – | | +| SV Global Health | O | | BIT STRING (SIZE(364)) | This enables GPS time recovery and possibly extended GPS correlation intervals | – | | +| Complete Almanac Provided | O | | BOOLEAN | This field indicates whether the SAS provided almanac for the full GPS constellation or not. TRUE means complete GPS almanac is provided. | YES | ignore | + +**Table 36** + +| Range bound | Explanation | +|--------------------|-------------------------------------------------------------------------------------------------------| +| maxSatAlmanac | Maximum number of satellites for which data is included in this IE. The value of maxSatAlmanac is 32. | + +### 9.2.2.10 GPS Clock and Ephemeris Parameters + +The IE contains the GPS clock information and GPS Ephemeris. + +**Table 37** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------| +| C/A or P on L2 | M | | BIT STRING (SIZE(2)) | Code(s) on L2 Channel (ICD-GPS-200 [10]) | +| URA Index | M | | BIT STRING (SIZE(4)) | User Range Accuracy (ICD-GPS-200 [10]) | +| SV Health | M | | BIT STRING (SIZE(6)) | ICD-GPS-200 [10] | +| IODC | M | | BIT STRING (SIZE(10)) | Issue of Data, Clock (ICD-GPS-200 [10]) | +| L2 P Data Flag | M | | BIT STRING (SIZE(1)) | ICD-GPS-200 [10] | +| SF 1 Reserved | M | | BIT STRING (SIZE(87)) | ICD-GPS-200 [10] | +| $T_{GD}$ | M | | BIT STRING (SIZE(8)) | Estimated group delay differential (ICD-GPS-200 [10]) | +| $t_{oc}$ | M | | BIT STRING (SIZE(16)) | apparent clock correction (ICD-GPS-200 [10]) | +| $af_2$ | M | | BIT STRING (SIZE(8)) | apparent clock correction (ICD-GPS-200 [10]) | +| $af_1$ | M | | BIT STRING (SIZE(16)) | apparent clock correction (ICD-GPS-200 [10]) | +| $af_0$ | M | | BIT STRING (SIZE(22)) | apparent clock correction (ICD-GPS-200 [10]) | +| $C_{rs}$ | M | | BIT STRING (SIZE(16)) | Amplitude of the Sine Harmonic Correction Term to the Orbit Radius (meters) (ICD-GPS-200 [10]) | +| $\Delta n$ | M | | BIT STRING (SIZE(16)) | Mean Motion Difference From Computed Value (semi-circles/sec) (ICD-GPS-200 [10]) | +| $M_0$ | M | | BIT STRING (SIZE(32)) | Mean Anomaly at Reference Time (semi-circles) (ICD-GPS-200 [10]) | +| $C_{uc}$ | M | | BIT STRING (SIZE(16)) | Amplitude of the Cosine Harmonic Correction Term To The Argument Of Latitude (radians) (ICD-GPS-200 [10]) | +| $e$ | M | | BIT STRING (SIZE(32)) | Eccentricity (ICD-GPS-200 [10]) | +| $C_{us}$ | M | | BIT STRING (SIZE(16)) | Amplitude of the Sine Harmonic Correction Term To The Argument Of Latitude (radians) (ICD-GPS-200 [10]) | +| $(A)^{1/2}$ | M | | BIT STRING (SIZE(32)) | Semi-Major Axis (meters) 1/2 (ICD-GPS-200 [10]) | +| $t_{oe}$ | M | | BIT STRING (SIZE(16)) | Reference Time Ephemeris (ICD-GPS-200 [10]) | +| Fit Interval Flag | M | | BIT STRING (SIZE(1)) | ICD-GPS-200 [10] | +| AODO | M | | BIT STRING (SIZE(5)) | Age Of Data Offset (ICD-GPS-200 [10]) | +| $C_{ic}$ | M | | BIT STRING (SIZE(16)) | Amplitude of the Cosine Harmonic Correction Term To The Angle Of Inclination (radians) (ICD-GPS-200 [10]) | +| $\Omega_{EGA_0}$ | M | | BIT STRING (SIZE(32)) | Longitude of Ascending Node of Orbit Plane at Weekly Epoch (semi-circles) (ICD-GPS-200 [10]) | +| $C_{is}$ | M | | BIT STRING (SIZE(16)) | Amplitude of the Sine Harmonic Correction Term To The Angle Of Inclination (radians) (ICD-GPS-200 [10]) | +| $i_0$ | M | | BIT STRING (SIZE(32)) | Inclination Angle at Reference Time (semi-circles) (ICD- | + +| | | | | | +|--------------------------------|---|--|-----------------------|--------------------------------------------------------------------------------------------------| +| | | | | GPS-200 [10] | +| $C_{rc}$ | M | | BIT STRING (SIZE(16)) | Amplitude of the Cosine Harmonic Correction Term to the Orbit Radius (meters) (ICD-GPS-200 [10]) | +| $\omega$ | M | | BIT STRING (SIZE(32)) | Argument of Perigee (semi-circles) (ICD-GPS-200 [10]) | +| $\Omega\text{E}\dot{\text{A}}$ | M | | BIT STRING (SIZE(24)) | Rate of Right Ascension (semi-circles/sec) (ICD-GPS-200 [10]) | +| $\dot{I}$ | M | | BIT STRING (SIZE(14)) | Rate of Inclination Angle (semi-circles/sec) (ICD-GPS-200 [10]) | + +### 9.2.2.11 GPS Ionospheric Model + +The IE contains fields needed to model the propagation delays of the GPS signals through the ionosphere. + +**Table 38** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------------------------------------------------------------------------------------------------------------|----------|-------|-----------------------|-----------------------| +| $\alpha_0$ | M | | BIT STRING (SIZE(8)) | NOTE 1 | +| $\alpha_1$ | M | | BIT STRING (SIZE(8)) | NOTE 1 | +| $\alpha_2$ | M | | BIT STRING (SIZE(8)) | NOTE 1 | +| $\alpha_3$ | M | | BIT STRING (SIZE(8)) | NOTE 1 | +| $\beta_0$ | M | | BIT STRING (SIZE(8)) | NOTE 2 | +| $\beta_1$ | M | | BIT STRING (SIZE(8)) | NOTE 2 | +| $\beta_2$ | M | | BIT STRING (SIZE(8)) | NOTE 2 | +| $\beta_3$ | M | | BIT STRING (SIZE(8)) | NOTE 2 | +| NOTE 1: The parameters $\alpha_n$ are the coefficients of a cubic equation representing the amplitude of the vertical delay (ICD-GPS-200 [10]). | | | | | +| NOTE 2: The parameters $\beta_n$ are the coefficients of a cubic equation representing the period of the ionospheric model (ICD-GPS-200 [10]). | | | | | + +### 9.2.2.12 GPS Measured Results + +The purpose of this information element is to provide reported GPS measurement information from the SRNC to the SAS. + +**Table 39** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------|----------|-------------|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| GPS TOW msec | M | | INTEGER (0..6.048*10 8 -1) | GPS Time of Week in milliseconds (rounded down to the nearest millisecond unit).

If the UTRAN GPS reference time Result is present, this IE shall be set to 0 by the transmitter and ignored by the receiver. | – | | +| Measurement Parameters | | 1.. | | | – | | +| >Satellite ID | M | | INTEGER (0..63) | Identifies the satellite and is equal to (SV ID No - 1) where SV ID No is defined in ICD-GPS-200 [10]. | – | | +| >C/N 0 | M | | INTEGER (0..63) | The estimate of the carrier-to-noise ratio of the received signal from the particular satellite used in the measurement. It is given in units of dB-Hz (Typical levels will be in the range of 20 – 50 dB-Hz). | – | | +| >Doppler | M | | INTEGER (-32768..32768) | Hz, scale factor 0.2. | – | | +| >Whole GPS Chips | M | | INTEGER (0..1022) | Unit in GPS chips | – | | +| >Fractional GPS Chips | M | | INTEGER (0..(2 10 -1)) | Scale factor 2 -10 | – | | +| >Multipath Indicator | M | | ENUMERATED (NM, low, medium, high) | See NOTE 1 | – | | +| >Pseudorange RMS Error | M | | INTEGER (0..63) | See NOTE 2 | – | | +| UTRAN GPS Reference Time Result | O | | 9.2.2.104 | This IE may only be present if SAS operates in SAS-centric mode. | YES | ignore | +| GPS Reference Time Uncertainty | O | | 9.2.2.132 | | YES | ignore | + +NOTE 1: Table 41 gives the mapping of the multipath indicator field. + +NOTE 2: Table 42 gives the bitmapping of the Pseudorange RMS Error field. + +**Table 40** + +| Range bound | Explanation | +|-------------|------------------------------------------------------------------------------------------------| +| maxSat | Maximum number of satellites for which data is included in this IE. The value of maxSat is 16. | + +**Table 41** + +| Value | Multipath Indication | +|--------|----------------------| +| NM | Not measured | +| Low | MP error < 5m | +| Medium | 5m < MP error < 43m | +| High | MP error > 43m | + +**Table 42** + +| Value | Mantissa | Exponent | Floating-Point value, $x_i$ | Pseudorange value, P | +|-------|----------|----------|-----------------------------|------------------------| +| 0 | 000 | 000 | 0.5 | $P < 0.5$ | +| 1 | 001 | 000 | 0.5625 | $0.5 \leq P < 0.5625$ | +| i | X | Y | $0.5 * (1 + x/8) * 2^y$ | $x_{i-1} \leq P < x_i$ | +| 62 | 110 | 111 | 112 | $104 \leq P < 112$ | +| 63 | 111 | 111 | -- | $112 \leq P$ | + +### 9.2.2.13 GPS Navigation Model + +This IE contain information required to manage the transfer of precise navigation data to the GPS-capable UE. + +**Table 43** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------------------------|--------------------|--------------|----------------------------------------|--------------------------------------------------------------------------------------------------------| +| Satellite information | | 1.. | | | +| >SatID | M | | INTEGER (0..63) | Identifies the satellite and is equal to (SV ID No - 1) where SV ID No is defined in ICD-GPS-200 [10]. | +| >Satellite Status | M | | ENUMERATED (NS_NN, ES_SN, ES_NN, REVD) | See NOTE | +| >GPS Clock and Ephemeris parameters | C-Satellite status | | 9.2.2.10 | | +| NOTE: The UE shall interpret enumerated symbols as follows. | | | | | + +**Table 44** + +| Value | Indication | +|-------|-------------------------------------------| +| NS_NN | New satellite, new Navigation Model | +| ES_SN | Existing satellite, same Navigation Model | +| ES_NN | Existing satellite, new Navigation Model | +| REVD | Reserved | + +**Table 45** + +| Condition | Explanation | +|-------------------------|-------------------------------------------------------------------------------| +| Satellite status | The IE shall be present if the Satellite Status IE is not set to ES_SN | + +**Table 46** + +| Range bound | Explanation | +|-------------|------------------------------------------------------------------------------------------------| +| maxSat | Maximum number of satellites for which data is included in this IE. The value of maxSat is 16. | + +## 9.2.2.14 GPS Real Time Integrity + +**Table 47** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------|----------|-------------|-----------------------|--------------------------------------------------------------------------------------------------------| +| CHOICE Bad Satellites Presence | | | | | +| >Bad Satellites | | | | | +| >>Satellite information | | 1.. | | | +| >>>BadSatID | M | | INTEGER (0..63) | Identifies the satellite and is equal to (SV ID No - 1) where SV ID No is defined in ICD-GPS-200 [10]. | +| >No Bad Satellites | | | NULL | | + +**Table 48** + +| Range bound | Explanation | +|-------------|------------------------------------------------------------------------------------------------| +| maxSat | Maximum number of satellites for which data is included in this IE. The value of maxSat is 16. | + +## 9.2.2.15 GPS Reference Time + +Table 49 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------------------------|----------|-----------------|--------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| GPS Week | M | | INTEGER (0..1023) | | – | | +| GPS TOW msec | M | | INTEGER (0..6.048*10 8 -1) | GPS Time of Week in milliseconds (rounded down to the nearest millisecond unit). | – | | +| GPS TOW Assist | | 0..
| | | – | | +| >SatID | M | | INTEGER (0..63) | Identifies the satellite and is equal to (SV ID No - 1) where SV ID No is defined in ICD-GPS-200 [10]. | – | | +| >TLM Message | M | | BIT STRING (SIZE(14)) | | – | | +| >Anti-Spoof | M | | BOOLEAN | | – | | +| >Alert | M | | BOOLEAN | | – | | +| >TLM Reserved | M | | BIT STRING (SIZE(2)) | | – | | +| UTRAN GPS Reference Time | O | | 9.2.2.103 | This IE may only be present if SAS operates in SAS-centric mode. | YES | ignore | +| SFN-TOW Uncertainty | O | | GPS-UTRAN Time Relationship Uncertainty 9.2.2.18 | This IE may only be present if SAS operates in SAS-centric mode. | YES | ignore | +| T UTRAN-GPS Drift Rate | O | | 9.2.2.105 | This IE may only be present if SAS operates in SAS-centric mode. | YES | ignore | +| GPS Reference Time Uncertainty | O | | 9.2.2.132 | This IE may only be present if SAS operates in SAS-centric mode. | YES | ignore | +| GPS Week Cycle Number | O | | INTEGER (0..7) | Number of 1024 GPS week cycles occurred since the GPS zero time-point (midnight of the night of January 5, 1980/morning of January 6, 1980). The first 1024 GPS weeks since the zero time-point is GPS Week Cycle Number 0. | YES | ignore | + +**Table 50** + +| Range bound | Explanation | +|-------------|------------------------------------------------------------------------------------------------| +| maxSat | Maximum number of satellites for which data is included in this IE. The value of maxSat is 16. | + +### 9.2.2.16 GPS Transmission TOW + +**Table 51** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------|----------|-------|-----------------------|---------------------------------| +| GPS Transmission TOW | | | INTEGER (0..604799) | The GPS time-of-week in seconds | + +### 9.2.2.17 GPS UTC Model + +The UTC Model field contains a set of parameters needed to relate GPS time to Universal Time Coordinate (UTC). + +**Table 52** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------|----------|-------|-----------------------|----------------------------| +| A 1 | M | | BIT STRING (SIZE(24)) | sec/sec (ICD-GPS-200 [10]) | +| A 0 | M | | BIT STRING (SIZE(32)) | seconds (ICD-GPS-200 [10]) | +| t ot | M | | BIT STRING (SIZE(8)) | seconds (ICD-GPS-200 [10]) | +| Δt LS | M | | BIT STRING (SIZE(8)) | seconds (ICD-GPS-200 [10]) | +| WN t | M | | BIT STRING (SIZE(8)) | weeks (ICD-GPS-200 [10]) | +| WN LSF | M | | BIT STRING (SIZE(8)) | weeks (ICD-GPS-200 [10]) | +| DN | M | | BIT STRING (SIZE(8)) | days (ICD-GPS-200 [10]) | +| Δt LSF | M | | BIT STRING (SIZE(8)) | seconds (ICD-GPS-200 [10]) | + +### 9.2.2.18 GPS-UTRAN Time Relationship Uncertainty + +This IE contains the uncertainty of the GPS and UTRAN time relationship. + +**Table 53** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------|----------|-------|-----------------------------------------------------------------------|-------------------------------------------------------------------| +| GPS-UTRAN Time Relationship Uncertainty | | | ENUMERATED (50ns, 500ns, 1us, 10us, 1ms, 10ms, 100ms, unreliable,...) | RNC or SAS estimate of uncertainty in GPS-UTRAN time relationship | + +### 9.2.2.19 Information Exchange ID + +The Information Exchange ID uniquely identifies any requested information per RNC-SAS pair. + +**Table 54** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|-----------------------------------|-----------------------| +| Information Exchange ID | | | INTEGER (0 .. 2 20 -1) | | + +### 9.2.2.20 Void + +### 9.2.2.21 Information Report Characteristics + +The information report characteristics define how the reporting shall be performed. + +**Table 56** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------------|------------|-------|-------------------------------------------------------|-------------------------------------------------------------------------------| +| Information Report Characteristics Type | M | | ENUMERATED(On Demand, Periodic, On Modification, ...) | | +| CHOICE Information Report Periodicity | C-Periodic | | | Indicates the frequency with which the SAS shall send broadcast data reports. | +| >Min | | | | | +| >>Minutes | M | | INTEGER (1..60, ...) | | +| >Hour | | | | | +| >>Hours | M | | INTEGER (1..24, ...) | | + +**Table 57** + +| Condition | Explanation | +|-----------|--------------------------------------------------------------------------------------------------------| +| Periodic | This IE shall be present if the Information Report Characteristics Type IE indicates 'periodic' | + +### 9.2.2.22 Information Type + +The Information Type indicates which kind of information the SAS shall provide. + +**Table 58** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------------|----------|-----------------------|-----------------------|--------------------------------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE Information Type | | | | | – | | +| >Implicit | | | | | – | | +| >>Method Type | M | | 9.2.2.25 | | – | | +| >Explicit | | | | | – | | +| >>Explicit Information | | 1.. | | | – | | +| >>>CHOICE Explicit Information Item | M | | | | – | | +| >>>>Almanac and Satellite Health | | | NULL | | – | | +| >>>>UTC Model | | | | | – | | +| >>>>>TransmissionT OW Indicator | M | | 9.2.2.29 | | – | | +| >>>>Ionospheric Model | | | | | – | | +| >>>>>TransmissionT OW Indicator | M | | 9.2.2.29 | | – | | +| >>>>Navigation Model | | | | | – | | +| >>>>>TransmissionT OW Indicator | M | | 9.2.2.29 | | – | | +| >>>>>Nav. Model Additional Data | | 0..1 | | | – | | +| >>>>>>GPS Week | M | | INTEGER (0..1023) | | – | | +| >>>>>>GPS_Toe | M | | INTEGER (0..167) | GPS time of ephemeris in hours of the latest ephemeris set | – | | +| >>>>>>T-Toe limit | M | | INTEGER (0..10) | ephemeris age tolerance in hours | – | | +| >>>>>>Satellite related data | | 0.. | | | – | | +| >>>>>>SatID | M | | INTEGER (0..63) | Identifies the satellite and is equal to (SV ID No - 1) where SV ID No is defined in ICD-GPS-200 [10]. | – | | +| >>>>>>IODE | M | | INTEGER (0..255) | Issue of Data Ephemeris for SatID | – | | +| >>>>DGPS Corrections | | | NULL | | – | | +| >>>>Reference Time | | | NULL | | – | | +| >>>>Acquisition Assistance | | | NULL | | – | | +| >>>>Real Time Integrity | | | NULL | | – | | +| >>>>Almanac and Satellite Health SIB | | | | | – | | +| >>>>>Transmission TOW Indicator | M | | 9.2.2.29 | | – | | +| >>>>Reference Location | | | NULL | This IE may only be present if SAS operates in SAS-centric mode. | – | | +| >>>>GANSS Common Data | | | | | – | | + +| | | | | | | | +|-----------------------------------------|---|----------------|------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| >>>>>GANSS Reference Time | O | | ENUMERATED(Requested, Not-Requested) | | – | | +| >>>>>GANSS Ionosphere Model | O | | ENUMERATED(Requested, Not-Requested) | | – | | +| >>>>>GANSS Reference Location | O | | ENUMERATED(Requested, Not-Requested) | This IE may only be present if SAS operates in SAS-centric mode. | – | | +| >>>>>GANSS Additional Ionospheric Model | O | | GANSS Additional Ionospheric Model Request 9.2.2.137 | Presence means requested. | YES | ignore | +| >>>>>GANSS Earth Orientation Parameters | O | | GANSS Earth Orientation Parameters Request 9.2.2.138 | | YES | ignore | +| >>>>GANSS Generic Data | | | | | – | | +| >>>>>GANSS Generic Data Item | | 1.. | | | – | | +| >>>>>GANSS ID | O | | 9.2.2.130 | Absence of this IE means Galileo. | – | | +| >>>>>GANSS Real Time Integrity | | 0..1 | | | – | | +| >>>>>GANSS Time Indicator | O | | 9.2.2.127 | | – | | +| >>>>>GANSS Data Bits | | 0..1 | | | – | | +| >>>>>GANSS TOD | M | | INTEGER (0..86399) | The GANSS TOD for which the data bits are requested. | – | | +| >>>>>Data Bit Assistance | | 1 | | | – | | +| >>>>>GANSS Signal ID | M | | BIT STRING (SIZE(8)) | Coded as defined in TS 25.331 [4] | – | | +| >>>>>GANSS Data Bit Interval | M | | INTEGER(0..15) | This field represents the time length for which the Data Bit Assistance is requested. The Data Bit Assistance shall be relative to the time interval (GANSS TOD, GANSS TOD + Data Bit Interval). The Data Bit Interval r , expressed in seconds, is | – | | + +| | | | | | | | +|--|--|--|--|------------------------------------------------------------------------------------------------------------------------------------------|--|--| +| | | | | mapped to a binary number K with the following formula:
$r = 0.1 \cdot 2^K$ Value K=15 means that the time interval is not specified. | | | +|--|--|--|--|------------------------------------------------------------------------------------------------------------------------------------------|--|--| + +| | | | | | | | +|-------------------------------------------------|---|--------------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|--| +| >>>>>>>>Satellite Information | | 0.. | | | – | | +| >>>>>>>>Sat ID | M | | INTEGER (0..63) | Defined in TS 25.331 [4]. | – | | +| >>>>>>>>DGANSS Corrections | | 0..1 | | | – | | +| >>>>>>>>GANSS Time Indicator | O | | 9.2.2.127 | | – | | +| >>>>>>>>DGANSS Signal | M | | BIT STRING (SIZE(8)) | Coded as defined in TS 25.331 [4] | – | | +| >>>>>>>>GANSS Almanac and Satellite Health | | 0..1 | | | – | | +| >>>>>>>>GANSS Time Indicator | O | | 9.2.2.127 | | – | | +| >>>>>>>>GANSS Reference Measurement Information | | 0..1 | | | – | | +| >>>>>>>>GANSS Time Indicator | O | | 9.2.2.127 | | – | | +| >>>>>>>>GANSS UTC Model | | 0..1 | | | – | | +| >>>>>>>>GANSS Time Indicator | O | | 9.2.2.127 | | – | | +| >>>>>>>>GANSS Time Model GNSS-GNSS | | 0..1 | | | – | | +| >>>>>>>>GNSS-GNSS Time ext | M | | BIT STRING (SIZE (9)) |

Defines the time model required.

Bit 1 is the MSB and bit 9 is the LSB (see clause 9.2.1).

Bit 1 stands for GPS,
Bit 2 stands for Galileo,
Bit 3 stands for QZSS,
Bit 4 stands for GLONASS,
Bit 5 stands for BDS.

Other bits are reserved.

| – | | +| >>>>>>>>GANSS Time Indicator | O | | 9.2.2.127 | | – | | +| >>>>>>>>GANSS Navigation Model | | 0..1 | | | – | | +| >>>>>>>>GANSS Week | M | | INTEGER(0..4095) | Defined in TS 25.331 [4]. | – | | +| >>>>>>>>GANSS Toe | M | | INTEGER(0..167) | Defined in TS 25.331 [4]. | – | | +| >>>>>>>>GANSS T-Toe Limit | M | | INTEGER(0..10) | Defined in TS 25.331 [4]. | – | | +| >>>>>>>>Satellite Related Data | | 0.. | | | – | | +| >>>>>>>>Sat ID | M | | INTEGER(0..63) | Defined in TS 25.331 [4]. | – | | + +| | | | | | | | +|---------------------------------------------|------------|--------------------------|----------------------------|------------------------------------------------------------|-----|--------| +| >>>>>>>>IOD | M | | BIT STRING (SIZE(10)) | Defined in TS 25.331 [4]. | – | | +| >>>>>>GANSS
Additional Navigation Models | | 0..1 | | | – | | +| >>>>>>>>GANSS
Week | M | | INTEGER(0..4095) | Defined in TS 25.331 [4]. | – | | +| >>>>>>>>GANSS
Toe | M | | INTEGER(0..167) | Defined in TS 25.331 [4]. | – | | +| >>>>>>>>GANSS
T-Toe Limit | M | | INTEGER(0..10) | Defined in TS 25.331 [4]. | – | | +| >>>>>>Satellite
Related Data | | 0..GANSS
Sat> | | | – | | +| >>>>>>>>Sat
ID | M | | INTEGER(0..63) | Defined in TS 25.331 [4]. | – | | +| >>>>>>>>IOD | M | | BIT STRING (SIZE(10)) | Defined in TS 25.331 [4]. | – | | +| >>>>>>GANSS
Additional UTC Models | | 0..1 | | | – | | +| >>>>>>>>GANSS
Time Indicator | O | | 9.2.2.127 | | – | | +| >>>>>>GANSS
Auxiliary Information | | 0..1 | | | – | | +| >>>>>>>>GANSS
Time Indicator | O | | 9.2.2.127 | | – | | +| >>>>>>SBAS ID | C-GANSS-ID | | 9.2.2.134 | | – | | +| >>>>>>DBDS
Corrections | O | | | This IE may be present if the GANSS ID IE indicates 'BDS'. | YES | ignore | +| >>>>>>>>GANSS
Time Indicator | O | | 9.2.2.127 | | – | | +| >>>>>>>DGANS
S Signal | M | | BIT STRING (SIZE(8)) | Coded as defined in TS 25.331 [4] | – | | +| >>>>>>BDS
Ionospheric Grid Model Request | O | | ENUMERATED (Requested ...) | This IE may be present if the GANSS ID IE indicates 'BDS'. | YES | ignore | + +Table 59 + +| Range Bound | Explanation | +|-----------------|-------------------------------------------------------------------------------------------------------------------| +| maxnoofExplInfo | Maximum number of Explicit Information supported in one Information Exchange. The value of maxnoofExplInfo is 32. | +| maxSat | Maximum number of satellites for which data is included in this IE. The value of maxSat is 16. | +| maxGANSS | Maximum number of GANSS systems for which data is included in this IE. The value of maxGANSS is 8. | +| maxGANSSSat | Maximum number of satellites for which data is included in this IE. The value of maxGANSSSat is 64 | + +Table 59A + +| Condition | Explanation | +|-----------|---------------------------------------------------------------| +| GANSS-ID | This IE shall be present if the GANSS ID IE indicates 'SBAS'. | + +### 9.2.2.23 Message Structure + +The *Message Structure* IE gives information for each level with assigned criticality in an hierarchical message structure from top level down to the lowest level above the reported level for the occurred error (reported in the *Information Element Criticality Diagnostics* IE). + +**Table 60** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------|----------|---------------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Message structure | | 1.. | | The first repetition of the Message Structure IE corresponds to the top level of the message. The last repetition of the Message Structure IE corresponds to the level above the reported level for the occurred error of the message. | +| >IE ID | M | | INTEGER (0..65535) | The IE ID of this level's IE containing the not understood or missing IE. | +| >Repetition Number | O | | INTEGER (1..256) | The Repetition Number IE gives, if applicable, the number of occurrences of this level's reported IE up to and including the occurrence containing the not understood or missing IE.

Note: All the counted occurrences of the reported IE must have the same top-down hierarchical message structure of IEs with assigned criticality above them. | + +**Table 61** + +| Range bound | Explanation | +|---------------|------------------------------------------------------------------------------| +| maxnooflevels | Maximum no. of message levels to report. The value for maxnooflevels is 256. | + +### 9.2.2.24 Message Type + +*Message Type* IE uniquely identifies the message being sent. It is mandatory for all messages. + +**Table 62** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------|----------|-------|---------------------------------------------------------------------------------------|-----------------------| +| Procedure Code | M | | INTEGER(0..255) | | +| Type of Message | M | | ENUMERATED
(Initiating Message, Successful Outcome, Unsuccessful Outcome, Outcome) | | + +### 9.2.2.25 Method Type + +**Table 63** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|---------------------------------------|-----------------------| +| Method Type | | | ENUMERATED
(UE_Assisted, UE_Based) | | + +### 9.2.2.26 Requested Data Value + +The Requested Data Value contains the relevant data concerning the ongoing information exchange, or positioning event. + +**Table 64** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------|------------|-----------------|---------------------------|------------------------------------------------------------------|-------------|----------------------| +| GPS Almanac and Satellite Health | O | | 9.2.2.9 | | – | | +| GPS UTC Model | O | | 9.2.2.17 | | – | | +| GPS Ionospheric Model | O | | 9.2.2.11 | | – | | +| GPS Navigation Model | O | | 9.2.2.13 | | – | | +| DGPS Corrections | O | | 9.2.2.5 | | – | | +| GPS Reference Time | O | | 9.2.2.15 | | – | | +| GPS Acquisition Assistance | O | | 9.2.2.8 | | – | | +| GPS Real Time Integrity | O | | 9.2.2.14 | | – | | +| Almanac and Satellite Health SIB | O | | 9.2.2.1 | | – | | +| GPS Transmission TOW | O | | 9.2.2.16 | | – | | +| GPS Reference Location | O | | Geographical Area 9.2.2.6 | This IE may only be present if SAS operates in SAS-centric mode. | YES | ignore | +| GANSS Common Assistance Data | | 0..1 | | | YES | ignore | +| >GANSS Reference Time | O | | 9.2.2.124 | | – | | +| >GANSS Ionospheric Model | O | | 9.2.2.116 | | – | | +| >GANSS Reference Location | O | | Geographical Area 9.2.2.6 | This IE may only be present if SAS operates in SAS-centric mode. | – | | +| >GANSS Additional Ionospheric Model | O | | 9.2.2.116A | | YES | ignore | +| >GANSS Earth Orientation Parameters | O | | 9.2.2.133 | | YES | ignore | +| GANSS Generic Assistance Data | | 0.. | | | GLOBAL | ignore | +| >GANSS ID | O | | 9.2.2.130 | Absence of this IE means Galileo. | – | | +| >GANSS Real Time Integrity | O | | 9.2.2.122 | | – | | +| >GANSS Data Bit Assistance | O | | 9.2.2.127A | | – | | +| >DGANSS Corrections | O | | 9.2.2.113 | | – | | +| >GANSS Almanac and Satellite Health | O | | 9.2.2.114 | | – | | +| >GANSS Reference Measurement Information | O | | 9.2.2.123 | | – | | +| >GANSS UTC Model | O | | 9.2.2.126 | | – | | +| >GANSS Time Model | O | | 9.2.2.125 | | – | | +| >GANSS Navigation Model | O | | 9.2.2.118 | | – | | +| >GANSS Additional Time Models | O | | 9.2.2.125A | | YES | ignore | +| >GANSS Additional Navigation Models | O | | 9.2.2.118A | | YES | ignore | +| >GANSS Additional UTC Models | O | | 9.2.2.126A | | YES | ignore | +| >GANSS Auxiliary Information | O | | 9.2.2.135 | | YES | ignore | +| >SBAS ID | C-GANSS-ID | | 9.2.2.134 | | YES | ignore | + +| | | | | | | | +|------------------------------|---|--|-----------|-------------------------------------------------------------------|-----|--------| +| > BDS Ionospheric Grid Model | O | | 9.2.2.160 | This IE may be present if the GANSS ID IE indicates 'BDS'. | YES | ignore | +| >DBDS Correction Information | O | | 9.2.2.161 | This IE may be present if the GANSS ID IE indicates 'BDS'. | YES | ignore | + +Table 64A + +| Range Bound | Explanation | +|-------------|----------------------------------------------------------------------------------------------------| +| maxGANSS | Maximum number of GANSS systems for which data is included in this IE. The value of maxGANSS is 8. | + +Table 64B + +| Condition | Explanation | +|-----------|----------------------------------------------------------------------| +| GANSS-ID | This IE shall be present if the GANSS ID IE indicates 'SBAS'. | + +### 9.2.2.27 Requested Data Value Information + +The *Requested Data Value Information* IE provides information on whether or not the Requested Data Value is available in the message and also the Requested Data Value itself if available. + +In case of "Periodic" and "On Modification" reporting, "Information Not Available" shall be used when at least one part of the requested information was not available at the moment of initiating the Information Reporting procedure. + +Table 65 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| CHOICE Information Availability Indicator | M | | | | – | | +| > Information Available | | | | | – | | +| >>Requested Data Value | M | | 9.2.2.26 | | – | | +| > Information not Available | | | NULL | | – | | + +### 9.2.2.28 Transaction ID + +The Transaction ID is used to associate all the messages belonging to the same procedure. Messages belonging to the same procedure shall use the same Transaction ID. + +The Transaction ID is determined by the initiating peer of a procedure. + +The Transaction ID shall uniquely identify a procedure among all ongoing parallel procedures using the same procedure code, and initiated by the same protocol peer. + +Table 66 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------| +| CHOICE Transaction ID Length | | | | The Transaction ID shall be interpreted for its integer value, not for the type of encoding ("short" or "long"). | +| >Short | | | | | +| >>Transaction ID Value | M | | INTEGER (0..127) | | +| >Long | | | | | +| >>Transaction ID Value | M | | INTEGER (0..32767) | | + +## 9.2.2.29 Transmission TOW Indicator + +Table 67 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------|----------|-------|----------------------------------------|-----------------------| +| Transmission TOW Indicator | | | ENUMERATE D (requested, not requested) | | + +## 9.2.2.30 Uncertainty Ellipse + +This IE contains the uncertainty ellipse of a geographical area. + +Table 68 + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------| +| Uncertainty semi-major | M | | INTEGER (0..127) | The uncertainty "r" is derived from the "uncertainty code" k by $r = 10 \times (1.1^k - 1)$ | +| Uncertainty semi-minor | M | | INTEGER (0..127) | The uncertainty "r" is derived from the "uncertainty code" k by $r = 10 \times (1.1^k - 1)$ | +| Orientation of major axis | M | | INTEGER (0..89) | The relation between the IE value (N) and the angle (a) in degrees it describes is $2N \leq a < 2(N+1)$ | + +## 9.2.2.31 Cell-ID Measured Results Info List + +This IE contains the Cell-ID measurements of signals associated with one or more cells. + +**Table 69** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------------|----------|-------------------------|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Cell-ID Measured Results Info | | 1.. | | | – | | +| >UC-ID | M | | 9.2.2.37 | The identifier of the measured cell. | – | | +| >UTRAN Access Point Position with Altitude | M | | 9.2.2.36 | Exact geographical position of the base station antenna.

If the SAS operates in SAS-centric mode, the values of this IE shall be set to 0 by the transmitter and shall be ignored by the receiver. | – | | +| >Geographical Area | O | | 9.2.2.6 | May only be present if the SAS operates in RNC-centric mode. | – | | +| >Round Trip Time Info | | 0..1 | | FDD only | – | | +| >>UE Rx-Tx Time Difference Type 2 | M | | INTEGER (0..8191) | According to mapping in TS 25.133 [13]. | – | | +| >>UE Positioning Measurement Quality | M | | 9.2.2.35 | Quality of the UE Rx-Tx time difference measurement. | – | | +| >>Round Trip Time | M | | INTEGER (0..32766) | According to mapping in TS 25.133 [13]. | – | | +| >>Extended Round Trip Time | O | | INTEGER (32767..103041) | Continuation of intervals as mapped in TS 25.133 [13].
Included only if the Round Trip Time IE above is included with its maximum value and if the actual value is outside the possible range for the Round Trip Time IE | YES | ignore | +| >Rx Timing Deviation Info | | 0..1 | | 3.84Mcps TDD only | – | | +| >>Rx Timing Deviation | M | | INTEGER (0..8191) | According to mapping in TS 25.123 [14]. | – | | +| >>Timing Advance | M | | INTEGER (0..63) | According to TS 25.331 [4]. | – | | +| >Rx Timing Deviation LCR Info | | 0..1 | | 1.28Mcps TDD only | – | | +| >>Rx Timing Deviation LCR | M | | INTEGER (0..511) | According to mapping in TS 25.123 [14]. | – | | + +| | | | | | | | +|-------------------------------------------|---|------|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| >>Timing Advance LCR | M | | INTEGER (0..2047) | According to TS 25.331 [4].
The content of this IE shall be ignored if the Extended Timing Advance LCR IE is present | – | | +| >>Extended Timing Advance LCR | O | | INTEGER (2048..8191) | According to TS 25.331 [4]. | YES | ignore | +| >Pathloss | O | | INTEGER (46..158) | Unit: dB downlink pathloss as defined in the Cell measured results IE in TS 25.331 [4]. | – | | +| > Rx Timing Deviation 768Info | | 0..1 | | 7.68Mcps TDD only | YES | reject | +| >>Rx Timing Deviation 7.68Mcps | M | | INTEGER (0..65535) | According to mapping in TS 25.123 [14]. | – | | +| >>Timing Advance 7.68Mcps | M | | INTEGER (0..511) | According to TS 25.331 [4]. | – | | +| > Rx Timing Deviation 384ext Info | | 0..1 | | 3.84Mcps TDD only | YES | reject | +| >>Rx Timing Deviation | M | | INTEGER (0..32767) | According to mapping in TS 25.123 [14]. | – | | +| >>Timing Advance | M | | INTEGER (0..255) | According to TS 25.331 [4]. | – | | +| > Round Trip Time Info With Type 1 | | 0..1 | | FDD only | YES | ignore | +| >>UE Rx-Tx Time Difference Type 1 | M | | INTEGER (768..1280) | According to mapping in TS 25.133 [13]. | – | | +| >>Round Trip Time | M | | INTEGER (0..32766) | According to mapping in TS 25.133 [13]. | – | | +| >>Extended Round Trip Time | O | | INTEGER (32767..103041) | Continuation of intervals as mapped in TS 25.133 [13].
Included only if the Round Trip Time IE above is included with its maximum value and if the actual value is outside the possible range for the Round Trip Time IE | – | | +| > Additional UE Measurement Info | | 0..1 | | FDD only | YES | ignore | +| >>CPICH RSCP | O | | INTEGER (-5..91) | According to CPICH_RSCP in TS 25.133 [13]. | – | | +| >>CPICH Ec/N0 | O | | INTEGER (0..49) | According to CPICH_Ec/No in TS 25.133 [13]. | – | | +| > Angle Of Arrival LCR | | 0..1 | | 1.28Mcps TDD only | YES | ignore | + +| | | | | | | | +|--------------------------|---|--|------------------------------------------|----------------------------------------|---|--| +| >>AOA LCR | M | | INTEGER (0..719) | According to mapping in TS 25.123 [14] | – | | +| >>AOA LCR Accuracy Class | M | | ENUMERATED ( A, B, C, D, E, F, G, H,...) | According to mapping in TS 25.123 [14] | – | | + +**Table 70** + +| Range bound | Explanation | +|------------------|--------------------------------------------------------------------------------------------------------------| +| maxNoOfMeasNCell | Maximum number of neighbour cells on which information can be reported. The value of maxNoOfMeasNCell is 32. | + +### 9.2.2.32 OTDOA Measured Results Info List + +This IE contains the OTDOA measurements of signals sent from the reference and neighbour cells. + +**Table 71** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------------------------|----------|-------------------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| OTDOA Measured Results Info | | 1.. | | | – | | +| >UC-ID | M | | 9.2.2.37 | The identifier of the neighbour cell. | – | | +| >UE SFN-SFN Observed Time Difference Type 2 Info | | 1 | | | – | | +| >>SFN-SFN Observed Time Difference Type 2 | M | | INTEGER (0..40961) | Gives the observed timing of the neighbour cell relative to the reference cell. | – | | +| >>UE Positioning Measurement Quality | M | | 9.2.2.35 | Quality of the observed time difference measurement. | – | | +| >>Measurement Delay | M | | INTEGER (0..65535) |

The interval of time, in units of 10ms frames, spanning the following two events:

1) Time of applicability of the SFN-SFN Value or TUTRAN-GPS/SFN relationship provided for the corresponding neighbour cell in 9.2.2.33 or TUTRAN-GNSS/SFN relationship provided for the corresponding neighbour cell in 9.2.2.33.

2) The point in time when this corresponding SFN-SFN observed time difference measurement was captured by the UE.

If the SAS operates in SAS-centric mode, 1) above shall be set to zero. I.e., in SAS-centric mode this IE indicates the SFN during which the

| – | | + +| | | | | | | | +|------------------------------------|---|--|----------------------------------|------------------------------------------------------------------------------------|-----|--------| +| | | | | corresponding SFN-SFN observed time difference measurement was captured by the UE. | | | +| >Additional OTDOA Measured Results | O | | | This IE may only be present if SAS operates in SAS-centric mode. | YES | ignore | +| >>Primary CPICH Info | M | | Primary Scrambling Code 9.2.2.46 | The identifier of the neighbour cell. | – | | + +**Table 72** + +| Range bound | Explanation | +|------------------|-----------------------------------------------------------------------------------------------------------------| +| MaxNoOfMeasNCell | Maximum number of neighbouring cells on which information can be reported. The value of MaxNoOfMeasNCell is 32. | + +### 9.2.2.33 OTDOA Neighbour Cell Info + +**Table 73** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------------------|----------|-------|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UC-ID | M | | 9.2.2.37 | The identifier of the neighbour cell. | +| UTRAN Access Point Position with Altitude | M | | 9.2.2.36 | Exact geographical position of the base station antenna. | +| CHOICE Relative Timing Difference Info | M | | | | +| >SFN-SFN Measurement Value Information | | | | | +| >>SFN-SFN Value | M | | INTEGER (0..614399) | | +| >>SFN-SFN Quality | O | | INTEGER (0..255) | Indicates the standard deviation (std) of the SFN-SFN otd (observed time difference) measurements in 1/16 chip. SFN-SFN Quality = $\sqrt{E[(x-\mu)^2]}$ = std of reported SFN-SFN Value, where x is the reported SFN-SFN Value and $\mu = E[x]$ is the expectation value of x. | +| >>SFN-SFN Drift Rate | M | | INTEGER (-100..+100) | Indicates the SFN-SFN drift rate in 1/256 chip per second. A positive value indicates that the Reference cell clock is running at a greater frequency than the measured neighbouring cell. | +| >>SFN-SFN Drift Rate Quality | O | | INTEGER (0..100) | Indicates the standard deviation (std) of the SFN-SFN drift rate measurements in 1/256 chip per second. SFN-SFN Drift Rate Quality = $\sqrt{E[(x-\mu)^2]}$ = std of reported SFN-SFN Drift Rate, where x is the reported SFN-SFN Drift Rate and $\mu = E[x]$ is the expectation value of x. | +| >T UTRAN-GPS Measurement Value Information | | | | | +| >>SFN | M | | INTEGER (0..4095) | SFN during which the T UTRAN-GPS measurement was performed | +| >>T UTRAN-GPS | | 1 | | Indicates the UTRAN GPS Timing of Cell Frame for LCS. | +| >>>MS | M | | INTEGER (0..16383) | Most significant part | +| >>>LS | M | | INTEGER (0..4294967295) | Least significant part | +| >>T UTRAN-GPS Quality | O | | INTEGER (0..255) | Indicates the standard deviation (std) of the T UTRAN-GPS measurements in 1/16 chip. T UTRAN-GPS Quality = $\sqrt{E[(x-\mu)^2]}$ = std of reported T UTRAN-GPS Value, where x is the reported T UTRAN-GPS Value and $\mu = E[x]$ is the expectation value of x. | +| >>T UTRAN-GPS Drift Rate | M | | INTEGER (-50..+50) | Indicates the T UTRAN-GPS drift rate in 1/256 chip per second. A positive value indicates that the UTRAN clock is running at a lower frequency than GPS clock. | +| >>T UTRAN-GPS Drift Rate Quality | O | | INTEGER (0..50) | Indicates the standard deviation (std) of the T UTRAN-GPS drift rate measurements in | + +| | | | | | +|-------------------------------------------------------------------------------|---|---|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | 1/256 chip per second.
$T_{\text{UTRAN-GPS}}$ Drift Rate Quality = $\sqrt{E[(x-\mu)^2]}$ = std of reported $T_{\text{UTRAN-GPS}}$ Drift Rate, where x is the reported $T_{\text{UTRAN-GPS}}$ Drift Rate and $\mu = E[x]$ is the expectation value of x. | +| > T_{\text{UTRAN-GANSS}} Measurement Value Information | | | | | +| >> GANSS ID | O | | 9.2.2.130 | Absence of this IE means Galileo. | +| >> SFN | M | | INTEGER (0..4095) | SFN during which the $T_{\text{UTRAN-GANSS}}$ measurement was performed | +| >> T_{\text{UTRAN-GANSS}} | | 1 | | Indicates the UTRAN GANSS Timing of Cell Frame for LCS. | +| >>> MS | M | | INTEGER (0..16383) | Most significant part | +| >>> LS | M | | INTEGER (0..4294967295) | Least significant part | +| >> T_{\text{UTRAN-GANSS}} Quality | O | | INTEGER (0..255) | Indicates the standard deviation (std) of the $T_{\text{UTRAN-GANSS}}$ measurements in 1/16 chip. $T_{\text{UTRAN-GANSS}}$ Quality = $\sqrt{E[(x-\mu)^2]}$ = std of reported $T_{\text{UTRAN-GANSS}}$ Value, where x is the reported $T_{\text{UTRAN-GANSS}}$ Value and $\mu = E[x]$ is the expectation value of x. | +| >> T_{\text{UTRAN-GANSS}} Drift Rate | M | | INTEGER (-50..50) | Indicates the $T_{\text{UTRAN-GANSS}}$ drift rate in 1/256 chip per second. A positive value indicates that the UTRAN clock is running at a lower frequency than GANSS clock. | +| >> T_{\text{UTRAN-GANSS}} Drift Rate Quality | O | | INTEGER (0..50) | Indicates the standard deviation (std) of the $T_{\text{UTRAN-GANSS}}$ drift rate measurements in 1/256 chip per second. $T_{\text{UTRAN-GANSS}}$ Drift Rate Quality = $\sqrt{E[(x-\mu)^2]}$ = std of reported $T_{\text{UTRAN-GANSS}}$ Drift Rate, where x is the reported $T_{\text{UTRAN-GANSS}}$ Drift Rate and $\mu = E[x]$ is the expectation value of x. | + +9.2.2.34 OTDOA Reference Cell Info + +**Table 74** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|--------------------------------------------------------------|----------|-------|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| UC-ID | M | | 9.2.2.37 | The identifier of the reference cell. | – | | +| UTRAN Access Point Position with Altitude | M | | 9.2.2.36 | Exact geographical position of the base station antenna. | – | | +| TUTRAN-GPS Measurement Value Information | | 0..1 | | | – | | +| >SFN | M | | INTEGER (0..4095) | SFN during which the T UTRAN-GPS measurement was performed | – | | +| >T UTRAN-GPS | | 1 | | Indicates the UTRAN GPS Timing of Cell Frame for LCS. | – | | +| >>MS | M | | INTEGER (0..16383) | Most significant part | – | | +| >>LS | M | | INTEGER (0..4294967295) | Least significant part | – | | +| >T UTRAN-GPS Quality | O | | INTEGER (0..255) | Indicates the standard deviation (std) of the T UTRAN-GPS measurements in 1/16 chip. $T_{UTRAN-GPS} \text{ Quality} = \sqrt{E[(x-\mu)^2]} = \text{std of reported } T_{UTRAN-GPS} \text{ Value}$ , where x is the reported T UTRAN-GPS Value and $\mu = E[x]$ is the expectation value of x. | – | | +| >T UTRAN-GPS Drift Rate | M | | INTEGER (-50..+50) | Indicates the T UTRAN-GPS drift rate in 1/256 chip per second. A positive value indicates that the UTRAN clock is running at a lower frequency than GPS clock. | – | | +| >T UTRAN-GPS Drift Rate Quality | O | | INTEGER (0..50) | Indicates the standard deviation (std) of the T UTRAN-GPS drift rate measurements in 1/256 chip per second.
T UTRAN-GPS Drift Rate Quality = $\sqrt{E[(x-\mu)^2]}$ = std of reported T UTRAN-GPS Drift Rate, where x is the reported T UTRAN-GPS Drift Rate and $\mu = E[x]$ is the expectation value of x. | – | | +| TUTRAN-GANSS Measurement Value Information | | 0..1 | | | GLOBAL | ignore | +| >GANSS ID | O | | 9.2.2.130 | Absence of this IE means Galileo. | – | | +| >SFN | M | | INTEGER | SFN during which | – | | + +| | | | | | | | +|--|--|--|-----------|--------------------------------------------------------------|--|--| +| | | | (0..4095) | the T UTRAN-GANSS
measurement was
performed | | | +|--|--|--|-----------|--------------------------------------------------------------|--|--| + +| | | | | | | | +|-----------------------------------------------|---|------|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| >T UTRAN-GANSS | | 1 | | Indicates the UTRAN GANSS Timing of Cell Frame for LCS. | – | | +| >>MS | M | | INTEGER(0..16383) | Most significant part | – | | +| >>LS | M | | INTEGER(0..4294967295) | Least significant part | – | | +| >T UTRAN-GANSS Quality | O | | INTEGER(0..255) | Indicates the standard deviation (std) of the T UTRAN-GANSS measurements in 1/16 chip. T UTRAN-GANSS Quality = $\sqrt{E[(x-\mu)^2]}$ = std of reported T UTRAN-GANSS Value, where x is the reported T UTRAN-GANSS Value and $\mu = E[x]$ is the expectation value of x. | – | | +| >T UTRAN-GANSS Drift Rate | M | | INTEGER(-50..50) | Indicates the T UTRAN-GANSS drift rate in 1/256 chip per second. A positive value indicates that the UTRAN clock is running at a lower frequency than GANSS clock. | – | | +| >T UTRAN-GANSS Drift Rate Quality | O | | INTEGER(0..50) | Indicates the standard deviation (std) of the T UTRAN-GANSS drift rate measurements in 1/256 chip per second. T UTRAN-GANSS Drift Rate Quality = $\sqrt{E[(x-\mu)^2]}$ = std of reported T UTRAN-GANSS Drift Rate, where x is the reported T UTRAN-GANSS Drift Rate and $\mu = E[x]$ is the expectation value of x. | – | | +| Additional Measurement Information LCR | | 0..1 | | 1.28Mcps TDD only | YES | ignore | +| >Timing Advance LCR R7 | M | | INTEGER(0..8191) | According to TS 25.331 [4]. | – | | +| >Rx Timing Deviation LCR | M | | INTEGER(0..511) | According to mapping in TS 25.123 [14]. | – | | +| >Angle Of Arrival LCR | | 0..1 | | 1.28Mcps TDD only | – | | +| >>AOA LCR | M | | INTEGER(0..719) | According to mapping in TS 25.123 [14] | – | | +| >>AOA LCR Accuracy Class | M | | ENUMERATED (A, B, C, D, E, F, G, H,...) | According to mapping in TS 25.123 [14] | – | | + +9.2.2.35 UE Positioning Measurement Quality + +**Table 75** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Std Resolution | M | | BIT STRING (SIZE(2)) | Std Resolution field includes the resolution used in Std of Measurements field. Encoding on two bits as follows:
'00' 10 meters
'01' 20 meters
'10' 30 meters
'11' Reserved | +| Number of Measurements | M | | BIT STRING (SIZE(3)) | The 'Number of Measurements' field indicates how many measurements have been used in the UE to determine the sample standard deviation of the measurements. Following 3 bit encoding is used:
'001' 5-9
'010' 10-14
'011' 15-24
'100' 25-34
'101' 35-44
'110' 45-54
'111' 55 or more
Special case:
'000': In this case the field 'Std of Measurements' contains the std of the reported measurement value = $\sqrt{E[(x-\mu)^2]}$ , where x is the reported value and $\mu = E[x]$ is the expectation value (i.e. the true value) of x. This std can be used irrespective of the number of measurements and reporting of the number of measurements is not needed. Also other measurements such as Ec/No or Rx levels can be utilised in this case to evaluate the 'Std of Measurements' reported in this IE. | + +| | | | | | +|---------------------|---|--|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Std of Measurements | M | | BIT STRING (SIZE(5)) | Std of Measurements field includes sample standard deviation of measurements (when number of measurements is reported in 'Number of Measurements' field) or standard deviation of the reported measurement value = $\sqrt{E[(x-\mu)^2]}$ , where x is the reported value and $\mu = E[x]$ is the expectation value (i.e. the true value) of x (when '000' is given in 'Number of Measurements' field). Following linear 5 bit encoding is used:
'00000' 0 - (R*1-1) meters
'00001' R*1 - (R*2-1) meters
'00010' R*2 - (R*3-1) meters
...
'11111' R*31 meters or more where R is the resolution defined by Std Resolution field. E.g. R=20 m corresponds to 0-19 m, 20-39 m,...,620+ m. | +|---------------------|---|--|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 9.2.2.36 UTRAN Access Point Position with Altitude + +The UTRAN Access Point Position with Altitude indicates the exact geographical position of the base station antenna. The altitude shall be included when available. + +Table 76 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------|----------|-------|-----------------------|-----------------------| +| Geographical Coordinates | M | | 9.2.2.7 | | +| Altitude and direction | O | | 9.2.2.2 | | + +### 9.2.2.37 UTRAN Cell Identifier (UC-ID) + +The UC-ID (UTRAN Cell identifier) is the identifier of a cell in one UTRAN. + +Table 77 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| RNC-ID | M | | INTEGER (0..4095) | The identifier of one RNC in UTRAN. If the Extended RNC-ID IE is included in the UC-ID IE, the RNC-ID IE shall be ignored. | – | – | +| C-ID | M | | INTEGER (0..65535) | The identifier of a cell in one RNS. | – | – | +| Extended RNC-ID | O | | 9.2.2.37A | The Extended RNC-ID IE shall be used if the RNC identity has a value larger than 4095. | YES | reject | + +### 9.2.2.37A Extended RNC-ID + +This is the identifier of one RNC in UTRAN. + +**Table 77A** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------|----------|-------|--------------------------|-----------------------------------------------------------------------------------| +| Extended RNC-ID | | | INTEGER
(4096..65535) | Note: Application of the Extended RNC-ID IE to very large networks is FFS. | + +### 9.2.2.38 Horizontal Accuracy Code + +**Table 78** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------| +| Horizontal Accuracy Code | M | | INTEGER(
0..127) | The requested accuracy "r" is derived from the "Horizontal Accuracy Code" k by $r = 10 \times (1.1^k - 1)$ | + +### 9.2.2.39 Vertical Accuracy Code + +**Table 79** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------| +| Vertical Accuracy Code | M | | INTEGER(
0..127) | The requested accuracy "v" is derived from the "Vertical Accuracy Code" k by $v = 45 \times (1.025^k - 1)$ . | + +### 9.2.2.40 Accuracy Fulfilment Indicator + +This IE indicates whether the returned position estimate satisfies the requested accuracy or not. + +**Table 80** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------|----------|-------|-------------------------------------------------------------------------------------------------------|-----------------------| +| Accuracy Fulfilment Indicator | M | | ENUMERATED
(requested
accuracy
fulfilled,
requested
accuracy not
fulfilled,
...) | | + +### 9.2.2.41 Uplink DPCH information + +This IE indicates the Uplink DPCH information used in the U-TDOA positioning method. + +Table 81 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------|----------|-------|--------------------------|-----------------------| +| Choice mode | M | | | | +| >FDD | | | | | +| >>Scrambling code type | M | | ENUMERATED (short, long) | | +| >>Scrambling code number | M | | INTEGER(0..16 777215) | | +| >>TFCI existence | M | | BOOLEAN | TRUE means existence. | +| >>Number of FBI bits | M | | INTEGER(0..2) | In bits. | +| >TDD | | | | | +| >>Cell Parameter ID | M | | 9.2.2.81 | | +| >>TFCI Coding | M | | 9.2.2.82 | | +| >>Puncture Limit | M | | 9.2.2.76 | | +| >>Repetition Period | M | | 9.2.2.84 | | +| >>Repetition Length | M | | 9.2.2.83 | | +| >>TDD DPCH Offset | M | | 9.2.2.85 | | +| >>UL Timeslot Information | M | | 9.2.2.86 | | +| >>Frame Offset | M | | 9.2.2.64 | | +| >>Special Burst Scheduling | M | | 9.2.2.92 | | + +#### 9.2.2.42 Frequency information + +This IE indicates the Frequency information used for the U-TDOA positioning method. + +Table 82 + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------| +| CHOICE mode | M | | | | +| >FDD | | | | | +| >>UARFCN uplink (Nu) | O | | INTEGER (0..16383) | If this IE is not present, the default duplex distance defined for the operating frequency band shall be used (TS 25.101 [20]) | +| >>UARFCN downlink (Nd) | M | | INTEGER (0 .. 16383) | TS 25.101 [20] | +| >TDD | | | | | +| >>UARFCN | M | | INTEGER (0 .. 16383) | TS 25.102 [21] | + +#### 9.2.2.43 PRACH parameters + +This IE indicates the PRACH parameter used for the U-TDOA positioning method. + +Table 83 + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|-------------------------|----------|-----------------|-----------------------|-----------------------| +| PRACH parameters | | 1 .. | | | +| >PRACH information | M | | 9.2.2.47 | | +| >TFS | M | | 9.2.2.48 | | +| >TFCS | | 1.. | | | +| >>CTFC | M | | 9.2.2.49 | | + +**Table 84** + +| Range bound | Explanation | +|-------------|------------------------------------------------------| +| maxPRACH | Maximum number of PRACHs in a cell. The value is 16. | +| maxTFC | Maximum number of TFC. Value is 1024. | + +#### 9.2.2.44 Compressed Mode Assistance Data + +This IE provides the assistance data used for the U-TDOA positioning method when the UE is operating in the compressed mode. + +**Table 85** + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|------------------------------------------------|----------|-------|-----------------------|-----------------------| +| Downlink information | | 1 | | | +| >Primary Scrambling Code | M | | 9.2.2.46 | | +| >Chip Offset | M | | 9.2.2.63 | | +| >Frame Offset | M | | 9.2.2.64 | | +| Uplink information | | 1 | | | +| >Transmission Gap Pattern Sequence Information | M | | 9.2.2.66 | | +| >Active Pattern Sequence Information | M | | 9.2.2.67 | | +| >CFN | M | | 9.2.2.68 | | + +#### 9.2.2.45 C-RNTI + +The cell RNTI (C-RNTI) identifies a UE having a RRC connection within a cell that is used for the U-TDOA positioning method. + +**Table 86** + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| C-RNTI | | | BIT STRING (SIZE(16)) | | + +#### 9.2.2.46 Primary Scrambling Code + +This IE gives the DL scrambling code of a cell. + +**Table 87** + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|-------------------------|----------|-------|-----------------------|-----------------------| +| Primary Scrambling Code | | | INTEGER (0..511) | | + +#### 9.2.2.47 PRACH information + +This IE contains the PRACH information used for the U-TDOA positioning method. + +Table 88 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|-------|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CHOICE mode | M | | | | +| >FDD | | | | | +| >>Available Signature | M | | BIT STRING (SIZE(16)) | Each bit indicates availability for a signature, where the signatures are numbered "signature 0" up to "signature 15". The value 1 of a bit indicates that the corresponding signature is available and the value 0 that it is not available. | +| >>Available SF | M | | ENUMERATED (32,64,128,256, ...) | In chips per symbol
Defines the minimum allowed SF (i.e. the maximum rate) | +| >>Preamble scrambling code number | M | | INTEGER (0..15) | Identification of scrambling code see TS 25.213 [17] | +| >>Puncturing Limit | M | | 9.2.2.76 | | +| >>Available Sub Channel Number | M | | BIT STRING (SIZE(12)) | Each bit indicates availability for a subchannel, where the subchannels are numbered "subchannel 0" to "subchannel 11". The value 1 of a bit indicates that the corresponding subchannel is available and the value 0 indicates that it is not available. | +| >TDD | | | | | +| >>Time Slot | M | | 9.2.2.87 | | +| >>TDD Channelisation Code | M | | 9.2.2.91 | | +| >>Max PRACH Midamble Shifts | M | | 9.2.2.93 | | +| >>PRACH Midamble | M | | 9.2.2.94 | | + +## 9.2.2.48 TFS + +This IE contains the TFS parameters used for the U-TDOA positioning method. + +Table 89 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------------|--------------|----------------|-----------------------------------------|---------------------------------------------------------------------| +| Dynamic Transport Format Information | | 1..
| | | +| >RLC Size | M | | INTEGER (129..5055) | Unit is bits | +| >Number of TBs and TTI List | | 1..
| | Present for every valid number of TB's (and TTI) for this RLC Size. | +| >>Transmission time interval | C-dynamicTTI | | ENUMERATED(10, 20, 40, 80, dynamic,...) | In ms. The value dynamic is only used in TDD mode. | +| >>Number of Transport blocks | M | | INTEGER (0..512) | | +| Semi-static Transport Format Information | M | | 9.2.2.61 | | + +Table 90 + +| Range bound | Explanation | +|-------------|-------------------------------------------------------| +| maxTF | Maximum number of Transport Formats. The value is 32. | + +Table 91 + +| Condition | Explanation | +|------------|------------------------------------------------------------------------------------------------------| +| dynamicTTI | This IE shall be present if TTI IE in Semi-static Transport Format Information IE is set to dynamic. | + +## 9.2.2.49 CTFC + +This IE identifies the TFC used for the U-TDOA positioning method. + +Table 92 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------|----------|-------------|-----------------------|-----------------------| +| CHOICE CTFC Size | | | | | +| >2 bit CTFC | | | | | +| >>CTFC information-2 | | 1.. | | | +| >>>ctfc2Bit | M | | INTEGER (0..3) | | +| >4 bit CTFC | | | | | +| >>CTFC information-4 | | 1.. | | | +| >>>ctfc4Bit | M | | INTEGER (0..15) | | +| >6 bit CTFC | | | | | +| >>CTFC information-6 | | 1.. | | | +| >>>ctfc6Bit | M | | INTEGER (0..63) | | +| >8 bit CTFC | | | | | +| >>CTFC information-8 | | 1.. | | | +| >>>ctfc8Bit | M | | INTEGER (0..255) | | +| >12 bit CTFC | | | | | +| >>CTFC information-12 | | 1.. | | | +| >>>ctfc12Bit | M | | INTEGER (0..4095) | | +| >16 bit CTFC | | | | | +| >>CTFC information-16 | | 1.. | | | +| >>>ctfc16Bit | M | | INTEGER (0..65535) | | +| >24 bit CTFC | | | | | +| >>CTFC information-24 | | 1.. | | | +| >>>ctfc22Bit | M | | INTEGER (0..16777215) | | + +Table 92A + +| Range bound | Explanation | +|-------------|---------------------------------------| +| maxTFC | Maximum number of TFC. Value is 1024. | + +### 9.2.2.50 Request Type + +This IE contains the Request Type parameters used for SAS centric positioning method selection. + +**Table 93** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------|----------|-------|--------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------| +| Event | M | | ENUMERATED(Stop Change of service area, Direct, Change of service area, Stop Direct, ..., Periodic, Stop Periodic) | Requests related to service area reporting are not supported in the current version of this specification. | +| Report Area | M | | ENUMERATED(Service Area, Geographical Area, ...) | | +| Horizontal Accuracy Code | O | | INTEGER(0..127) | The requested accuracy "r" is derived from the "accuracy code" k by $r = 10 \times (1.1^k - 1)$ . | + +### 9.2.2.51 UE Positioning Capability + +This IE contains the UE Positioning Capability information used for SAS centric positioning method selection. + +**Table 94** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------------------------------------------------|----------|----------------|----------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Standalone location method(s) supported | M | | BOOLEAN | Defines if a UE can measure its location by some means unrelated to UTRAN. TRUE means supported | – | | +| UE based OTDOA supported | M | | BOOLEAN | TRUE means supported | – | | +| Network Assisted GPS support | M | | ENUMERATED (Network based, UE based, Both, None,...) | Defines if the UE supports network based or UE based GPS methods. | – | | +| Support for GPS timing of cell frames measurement | M | | BOOLEAN | Defines if a UE has the capability to perform the UE GPS timing of cell frames measurement (TS 25.331 [4]). TRUE means capable | – | | +| Support for IPDL | M | | BOOLEAN | Defines if a UE has the capability to use IPDL to enhance its 'SFN-SFN observed time difference –type 2' measurement. TRUE means supported | – | | +| Support for Rx-Tx time difference type2 measurement | M | | BOOLEAN | TRUE means supported | – | | +| Support for UE assisted GPS measurement validity in CELL_PCH and URA_PCH states | M | | BOOLEAN | TRUE means supported | – | | +| Support for SFN-SFN observed time difference type 2 measurement | M | | BOOLEAN | TRUE means supported | – | | +| Network Assisted GANSS Support | | 0.. | | | GLOBAL | ignore | +| >GANSS ID | O | | 9.2.2.130 | Absence of this IE means Galileo. | – | | +| >GANSS mode | M | | ENUMERATED ('Network based', 'UE based', 'Both', 'None') | Defines if the UE supports network based or UE based GANSS methods | – | | +| >GANSS Signal ID | O | | 9.2.2.131 | Absence of this field means the default value for the GANSS identified by “GANSS ID” (TS | – | | + +| | | | | | | | +|------------------------------------------------------|------------|------------------------------|----------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|--------|--------| +| | | | | 25.331 [4]). | | | +| >Support for GANSS timing of cell frames measurement | M | | BOOLEAN | Defines if a UE has the capability to perform the UE GANSS timing of cell frames measurement (TS 25.331 [4]). TRUE means capable | – | | +| >Support for GANSS Carrier-Phase Measurement | M | | BOOLEAN | Defines if a UE has the capability to perform the UE GANSS Carrier-Phase Measurement. TRUE means capable | – | | +| >SBAS IDs | C-GANSS-ID | | 9.2.2.150 | | YES | ignore | +| >GANSS Signal IDs | O | | 9.2.2.131a | | YES | ignore | +| >Support for non-native assistance choices | O | | Support for Non-Native Assistance Choices Indication 9.2.2.139 | | YES | ignore | +| AddPos Support | | 0..<max AddPos> | | | GLOBAL | ignore | +| >AddPos ID | M | | ENUMERATED ('Barometric Pressure', 'WLAN', 'Bluetooth', 'MBS') | Defines if a UE has the capability to perform measurements for one or more Additional Positioning methods. | – | | +| >AddPos mode | M | | ENUMERATED ('standalone', 'ue-assisted', 'both') | | – | | + +Table 94A + +| Range Bound | Explanation | +|-------------|----------------------------------------------------------------------------------------------------------------------| +| maxGANSS | Maximum number of GANSS systems for which data is included in this IE. The value of maxGANSS is 8. | +| maxAddPos | Maximum number of Additional Positioning methods for which data is included in this IE. The value of maxAddPos is 8. | + +Table 94B + +| Condition | Explanation | +|-----------|---------------------------------------------------------------| +| GANSS-ID | This IE shall be present if the GANSS ID IE indicates 'SBAS'. | + +## 9.2.2.52 Response Time + +This IE contains the Response Time used for SAS centric mode. + +**Table 95** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------|-----------------|--------------|--------------------------------------------------|-------------------------------------| +| Response Time | | | ENUMERATED(
Low Delay, Delay
Tolerant,...) | The value refers to TS 22.071 [15]. | + +### 9.2.2.53 Positioning Priority + +This IE contains the Positioning Priority used for SAS centric mode. + +**Table 96** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------|-----------------|--------------|-----------------------------------------------------------|------------------------------------| +| Positioning Priority | | | ENUMERATED(
High Priority,
Normal Priority,
...) | The value refers to TS 22.071 [15] | + +### 9.2.2.54 Client Type + +This IE contains the Client Type used for SAS centric mode. + +**Table 97** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------|-----------------|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------| +| Client Type | | | ENUMERATED(
Emergency
Services, Value
Added Services,
PLMN Operator
Services, Lawful
Intercept
Services, PLMN
Operator -
broadcast
services, PLMN
Operator - O&M,
PLMN Operator -
anonymous
statistics, PLMN
Operator - Target
MS service
support, ...) | Identifies the type of client. | + +### 9.2.2.55 Positioning Method + +This IE contains the Positioning Method used for SAS centric positioning method selection. + +Table 98 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------|----------|-------|-------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Additional Method Type | M | | 9.2.2.58 | | – | | +| Selected Position Method | M | | ENUMERATED(OTDOA, GPS, OTDOA or GPS, Cell ID, UTDOA, ..., GNSS, OTDOA or GNSS, GPS and AddPos, OTDOA or GPS and AddPos) | | – | | +| GNSS Positioning Method | C-GNSS | | BIT STRING (SIZE(9)) |

For each bit, if set to '1', indicates that respective GNSS is allowed.

Bit 1 is the MSB and bit 9 is the LSB (see clause 9.2.1).

bit 1: GPS
bit 2: Galileo
bit 3: SBAS(WAAS, EGNOS, MSAS, GAGAN)
bit 4: Modernized GPS (L1C, L2C, L5)
bit 5: QZSS
bit 6: GLONASS

bits 7-9: reserved for future GNSSs

Note: Bit 1 cannot be the only one set to 1.

| YES | ignore | +| Additional Positioning Method | C-AddPos | | BIT STRING SIZE(8) |

For each bit, if set to '1', indicates that respective Additional Positioning type is allowed.

Bit 1 is the MSB and bit 8 is the LSB (see clause 9.2.1).

bit 1: Barometric Pressure
bit 2: WLAN
bit 3: Bluetooth
Bit 4: MBS
bits 5-8: reserved for future Additional Positioning methods

| YES | Ignore | + +**Table 98A** + +| Condition | Explanation | +|------------------|----------------------------------------------------------------------------------------------------------------------------------| +| GNSS | This IE shall be present if the Selected Position Method IE value is set to "GNSS" or "OTDOA or GNSS" | +| AddPos | This IE shall be present if the Selected Position Method IE value is set to "GPS and AddPos" or "OTDOA or GPS and AddPos" | + +### 9.2.2.56 U-TDOA Bit Count + +This IE contains the recommended number of pre-coded bits to be transmitted by the UE when the U-TDOA positioning method is selected. + +**Table 99** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------|-----------------|--------------|------------------------------|---------------------------------------------------| +| U-TDOA Bit Count | | | INTEGER (0..5000) | Number of bits to be transmitted by the target UE | + +### 9.2.2.57 U-TDOA Time Interval + +This IE contains the recommended maximum time interval for transmission of the U-TDOA Bit Count number of bits for U-TDOA positioning. + +**Table 100** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------|-----------------|--------------|------------------------------|-------------------------------------------------------------------------| +| U-TDOA Time Interval | | | INTEGER (0..3000) | Time in ms in which the U-TDOA Bit Count is to be transmitted by the UE | + +### 9.2.2.58 Additional Method Type + +This IE contains the selected positioning method type for SAS-centric mode. + +**Table 101** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|-----------------|--------------|---------------------------------------------------------------------------------------------------------------------------------------------|------------------------------| +| Additional Method Type | | | ENUMERATED (UE_Assisted, UE_Based, UE_Based is preferred but UE_assisted is allowed, UE_Assisted is preferred but UE_Based is allowed, ...) | | + +### 9.2.2.59 UE Positioning OTDOA Assistance Data + +This IE contains the UE Positioning OTDOA Assistance Data used in the SAS centric mode. + +**Table 102** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------|----------|-------|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| UE Positioning OTDOA Reference Cell Info | O | | | | – | | +| >SFN | O | | INTEGER (0..4095) | Time stamp (SFN of Reference Cell) of the SFN-SFN relative time differences and SFN-SFN drift rates. Included if any SFN-SFN drift value is included in IE UE positioning OTDOA neighbour cell info . | – | | +| >CHOICE mode | | | | | – | | +| >>Fdd | | | | | – | | +| >>>Primary CPICH Information | M | | Primary scrambling code 9.2.2.46 | | – | | +| >>Tdd | | | | | – | | +| >>>Cell Parameter ID | M | | 9.2.2.81 | | – | | +| >Frequency Info | O | | 9.2.2.42 | Default value is the existing value of frequency information. This IE shall always be set to default value | – | | +| >CHOICE positioning mode | | | | | – | | +| >>UE Based | | | | | – | | +| >>> Cell position | O | | Reference Cell Position 9.2.2.70 | The position of the antenna that defines the cell. | – | | +| >>> Round Trip Time | O | | INTEGER (0..32766) | According to mapping in TS 25.133 [13]. | – | | +| >>UE Assisted | | | | | – | | +| >UE positioning IPDL parameters | O | | 9.2.2.71 | If this element is not included there are no idle periods present | – | | +| >Extended Round Trip Time | O | | INTEGER (32767..103041) | According to mapping in TS 25.133 [13]. Included only if the Round Trip Time IE above is included with its maximum value and if the actual value is outside the possible range for the Round Trip Time IE. | YES | ignore | +| >Timing Advance LCR R7 | O | | INTEGER (0..8191) | 1.28Mcps TDD only. According to TS 25.331 [4]. | – | | +| >Rx Timing Deviation LCR | O | | INTEGER (0..511) | 1.28Mcps TDD only . According to mapping in TS 25.123 [14]. | – | | +| >Angle Of Arrival LCR | | 0..1 | | 1.28Mcps TDD only | – | | +| >>AOA LCR | M | | INTEGER (0..719) | According to mapping in TS 25.123 [14] | – | | +| >>AOA LCR Accuracy Class | M | | ENUMERATE D ( A, B, C, D, E, F, G, H,...) | According to mapping in TS 25.123 [14] | – | | +| UE Positioning OTDOA | O | | | | – | | + +| | | | | | | | +|-------------------------------------------------|---|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| Neighbour Cell List | | | | | | | +| >UE positioning
OTDOA Neighbour
cell info | | 1..eas> | | | – | | +| >>CHOICE mode | | | | | – | | +| >>>FDD | | | | | – | | +| >>>>Primary
CPICH
Information | M | | Primary
scrambling
code
9.2.2.46 | | – | | +| >>>TDD | | | | | – | | +| >>>>Cell
Parameter ID | M | | 9.2.2.81 | | – | | +| >>Frequency Info | O | | 9.2.2.42 | Default value is the
existing value of
frequency information | – | | +| >>UE positioning
IPDL parameters | O | | 9.2.2.71 | | – | | +| >>SFN-SFN Relative
Time difference | M | | 9.2.2.73 | | – | | +| >>SFN Offset Validity | O | | ENUMERATE
D (false) | Absence of this
element means SFN
offset is valid. False
means SFN offset is
not valid. | – | | +| >>SFN-SFN Drift | O | | ENUMERATE
D
(0,1,2,3,4,5,8,
10,15,25,35,50
,65,80,100,-1,-
2,-3,-4,-5,-8,
-10,-15,-25,-
35,-50,-65,-
80,-100,...) | Indicates the SFN-
SFN drift rate in 1/256
chip per second. | – | | +| >>Search Window
Size | M | | ENUMERATE
D (c20, c40,
c80, c160,
c320, c640,
c1280,
moreThan128
0, ...) | In chips. If the value
is X then the
expected SFN-SFN
observed time
difference is in the
range [RTD-X,
RTD+X] where RTD
is the value of the
field SFN-SFN
relative time
difference. | – | | +| >>CHOICE
positioning mode | | | | | – | | +| >>>UE Based | | | | | – | | +| >>>>Relative
North | O | | INTEGER
(-20000..2000
0) | Seconds of angle,
scale factor 0.03.
Relative position
compared to
reference cell. | – | | +| >>>>Relative East | O | | INTEGER
(-20000..2000
0) | Seconds of angle,
scale factor 0.03.
Relative position
compared to
reference cell. | – | | +| >>>>Relative
Altitude | O | | INTEGER
(-4000..4000) | Relative altitude in
meters compared to
ref. cell. | – | | +| >>>>Fine SFN-
SFN | O | | INTEGER
(0..15) | Gives finer resolution | – | | +| >>>>Round Trip
Time | O | | INTEGER
(0..32766) | In chips. Included if
cell is in active set | – | | +| >>> UE assisted | | | | | – | | +| >>Extended Round | O | | INTEGER | In chips. Included if | YES | ignore | + +| | | | | | | | +|-----------|--|--|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--| +| Trip Time | | | (32767..103041) | cell is in active set. Included only if the Round Trip Time IE above is included with its maximum value and if the actual value is outside the possible range for the Round Trip Time IE. | | | +|-----------|--|--|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--| + +Table 103 + +| Range bound | Explanation | +|-------------|------------------------------------------------------| +| maxCellMeas | Maximum number of cells to measure. The value is 32. | + +### 9.2.2.60 UL TrCH information + +This IE contains the UL TrCH information used for the U-TDOA positioning method. + +Table 104 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------|----------|-------|---------------------------|-----------------------| +| Uplink transport channel type | M | | ENUMERATED (DCH,USCH,...) | USCH is TDD only | +| TFS | M | | 9.2.2.48 | | + +### 9.2.2.61 Semi-static Transport Format Information + +This IE contains the Semi-static Transport Format information used for the U-TDOA positioning method. + +Table 105 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics description | +|----------------------------|----------|-------|--------------------------------------------------|---------------------------------------------------| +| Transmission time interval | M | | ENUMERATED(5, 10, 20, 40, 80, dynamic, ...) | In ms. The value dynamic is only used in TDD mode | +| Type of channel coding | M | | ENUMERATED(No coding, Convolutional, Turbo, ...) | The option "No coding" is only valid for TDD. | +| Coding Rate | C-Coding | | ENUMERATED(1/2, 1/3, ...) | | +| Rate matching attribute | M | | INTEGER(1..hiRM) | | +| CRC size | M | | ENUMERATED(0, 8, 12, 16, 24, ...) | In bits | + +Table 106 + +| Condition | Explanation | +|-----------|--------------------------------------------------------------------------------------| +| Coding | This IE shall be present if Type of channel coding IE is "Convolutional" or "Turbo". | + +Table 107 + +| Constant | Explanation | Value | +|----------|-------------------------------------------------------------------------------------|-------| +| hiRM | Maximum number that could be set as rate matching attribute for a transport channel | 256 | + +### 9.2.2.62 Environment Characterisation + +This IE contains the Environment Characterisation information used for the SAS centric mode. + +**Table 108** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics description | +|------------------------------|----------|-------|------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| Environment Characterisation | | | ENUMERATED(heavy multipath and NLOS conditions, no or light multipath and usually LOS conditions, not defined or mixed environment, ...) | | + +### 9.2.2.63 Chip Offset + +This IE contains the Chip Offset information used for the U-TDOA positioning method. + +The Chip Offset is defined as the radio timing offset inside a radio frame. The Chip offset is used as offset relative to the Primary CPICH timing for the DL DPCH or for the F-DPCH. + +**Table 109** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| Chip Offset | | | INTEGER(0..38399) | Unit: chips | + +### 9.2.2.64 Frame Offset + +This IE contains the Frame Offset information used for the U-TDOA positioning method. + +The Frame Offset is the required offset between the dedicated channel downlink transmission frames (CFN, Connection Frame Number) and the broadcast channel frame offset (Cell Frame Number). The Frame Offset is used in the translation between Connection Frame Number (CFN) on Iub/Iur and the least significant 8 bits of SFN (System Frame Number) on Uu. The Frame Offset is UE and cell specific + +**Table 110** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| Frame Offset | | | INTEGER(0..255) | Unit: Frames | + +### 9.2.2.65 Position Data + +This IE provides data related to the positioning methods used and reported in the SAS centric mode. + +**Table 111** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------|-------------------------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Position Data | M | | | | – | | +| >Positioning Data Discriminator | M | | BIT STRING (SIZE(4)) |

The positioning data discriminator defines the type of data provided for each positioning method:

0000 indicates the presence of the Positioning Data Set IE (that reports the usage of each non-GNSS method that was successfully used to obtain the location estimate) and optional presence of the GNSS Positioning Data Set IE. It also indicates the optional presence of the Additional Positioning Data Set IE.

0001 indicates the presence of the GNSS Positioning Data Set IE (that reports the usage of each GNSS method that was successfully used to obtain the location estimate) and the absence of the Positioning Data Set IE. It also indicates the optional presence of the Additional Positioning Data Set IE.

0010 indicates the presence of the Additional Positioning Data Set IE and the absence of the Positioning Data Set and the GNSS Positioning Data Set IEs.

1 octet of data is provided for each positioning method included.

All other values are reserved.

| – | | +| >Positioning Data Set | C-
ifDiscriminator=0 | | | | – | | + +| | | | | | | | +|--------------------------------|--|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| >>Positioning Method and Usage | | 1.. | OCTET STRING (SIZE(1)) |

Coding of positioning method (bits 8-4):
00000 Reserved
00001 Reserved
00010 Reserved
00011 Reserved
00100 Reserved
00101 Mobile Assisted GPS
00110 Mobile Based GPS
00111 Conventional GPS
01000 U-TDOA
01001 OTDOA
01010 IPDL
01011 RTT
01100 Cell ID
01101 to 01111 reserved for other location technologies
10000 to 11111 reserved for network specific positioning methods

Coding of usage (bits 3-1):
000 Attempted unsuccessfully due to failure or interruption - not used.
001 Attempted successfully: results not used to generate location - not used.
010 Attempted successfully: results used to verify but not generate location - not used.
011 Attempted successfully: results used to generate location
100 Attempted successfully: case where MS supports multiple mobile based positioning methods and the actual method or methods used by the MS cannot be determined.

| - | | +| >GANSS Positioning Data Set | | | 0..1 | | YES | ignore | + +| | | | | | | | +|-------------------------------------------|--|------------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| >>GANSS Positioning Method and Usage | | 1.. | OCTET STRING (SIZE(1)) | Coding of Method (Bits 8-7):
00 : UE-Based
01 : UE-Assisted
10 : Conventional
11 : Reserved

Coding of GANSS ID (Bits 6-4):
000 : Galileo
001 : SBAS
010 : Modernized GPS
011 : QZSS
100 : GLONASS
other values reserved

Coding of usage (bits 3-1):
011 Attempted successfully: results used to generate location
100 Attempted successfully: case where UE supports multiple mobile based positioning methods and the actual method or methods used by the UE cannot be determined. | – | | +| >Additional Positioning Data Set | | | 0..1 | | YES | Ignore | +| >>Additional Positioning Method and Usage | | 1 to | OCTET STRING (SIZE(1)) | Coding of Additional Positioning method (bits 8-7):
00 Reserved;
01 UE-Assisted;
10 Standalone;
11 Reserved.

Coding of Additional Positioning ID (bits 6-4):
000 Barometric Pressure;
001 WLAN;
010 Bluetooth;
011 MBS;
other values reserved

Coding of usage (bits 3-1):
011 Attempted successfully: results used to generate location;
100 Attempted successfully: case where UE supports multiple mobile based positioning methods and the actual method or methods used by the UE cannot be determined. | – | | + +Table 112 + +| Condition | Explanation | +|-------------------|-------------------------------------------------------------------------------------| +| ifDiscriminator=0 | This IE is present if the Positioning Data Discriminator IE is set to "0000" | + +**Table 113** + +| Range bound | Explanation | +|-------------|------------------------------------------------------------------| +| maxSet | Maximum size of the data set. Value is 9. | +| maxGANSSet | Maximum size of the data. Value is 9. | +| maxAddPos | Maximum size of the Additional Positioning data set. Value is 8. | + +### 9.2.2.66 Transmission Gap Pattern Sequence Information + +This IE contains the Transmission Gap Pattern Sequence information used for the U-TDOA positioning method when the UE is operating in the compressed mode. + +**Table 114** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------------------|----------|--------------|-------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Transmission Gap Pattern Sequence Information | | 1.. | | | +| >TGPS Identifier | M | | INTEGER (1..maxTGPS) | Transmission Gap Pattern Sequence Identifier: Establish a reference to the compressed mode pattern sequence. Up to simultaneous compressed mode pattern sequences can be used. | +| >TGSN | M | | INTEGER (0..14) | Transmission Gap Starting Slot Number: The slot number of the first transmission gap slot within the TGC FN. | +| >TGL1 | M | | INTEGER (1..14) | The length of the first Transmission Gap within the transmission gap pattern expressed in number of slots. | +| >TGL2 | O | | INTEGER (1..14) | The length of the second Transmission Gap within the transmission gap pattern. If omitted, then TGL2=TGL1. | +| >TGD | M | | INTEGER (0,15..269) | Transmission Gap Distance: indicates the number of slots between the starting slots of two consecutive transmission gaps within a transmission gap pattern. If there is only one transmission gap in the transmission gap pattern, this parameter shall be set to "0" ("0" =undefined). | +| >TGPL1 | M | | INTEGER (1..144, ...) | The duration of transmission gap pattern 1 in frames. | +| >Uplink Compressed Mode Method | M | | ENUMERATED( SF/2, Higher Layer Scheduling, ...) | Method for generating uplink compressed mode gap. | + +**Table 115** + +| Range bound | Explanation | +|-------------|-----------------------------------------------------------------------| +| maxTGPS | Maximum number of transmission gap pattern sequences. The value is 6. | + +### 9.2.2.67 Active Pattern Sequence Information + +This IE contains the Active Pattern Sequence information used for the U-TDOA positioning method when the UE is operating in the compressed mode. + +**Table 116** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------------|----------|---------------------------|-------------------------|-------------------------------------------------------------------------------------------------------------------| +| CM Configuration Change CFN | M | | CFN
9.2.2.68 | | +| Transmission Gap Pattern Sequence Status | | 0..<maxTGPS> | | | +| >TGPS Identifier | M | | INTEGER
(1..maxTGPS) | If the group is not present, none of the pattern sequences are activated. References an already defined sequence. | +| >TGPRC | M | | INTEGER
(0..511) | The number of transmission gap patterns within the Transmission Gap Pattern Sequence. "0"=Infinity | +| >TGCFN | M | | CFN
9.2.2.68 | Connection Frame Number of the first frame of the first pattern 1 within the Transmission Gap Pattern Sequence. | + +**Table 117** + +| Range bound | Explanation | +|-------------|-----------------------------------------------------------------------| +| maxTGPS | Maximum number of transmission gap pattern sequences. The value is 6. | + +### 9.2.2.68 CFN + +This IE contains the CFN used for the U-TDOA positioning method when the UE is operating in the compressed mode. + +**Table 118** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| CFN | | | INTEGER(0..255) | | + +### 9.2.2.69 Positioning Response Time + +This IE contains the Positioning Response Time information used for SAS centric mode. + +**Table 119** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------|----------|-------|--------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| Positioning Response Time | | | ENUMERATED(
250, 500, 1000,
2000, 3000,
4000, 6000,
8000, 12000,
16000, 20000,
24000, 28000,
32000, 64000,
) | Unit: millisecond | + +### 9.2.2.70 Reference Cell Position + +*Reference Cell Position* IE is used to identify the position of the reference cell using geographical coordinates. The reference system is the same as the one used in TS 23.032 [11]. + +**Table 120** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE Geographical Area | | | | | +| >Point | | | | Ellipsoid point | +| >>Geographical Coordinates | M | | 9.2.2.7 | | +| >Ellipsoid point with altitude | | | | | +| >>Geographical Coordinates | M | | 9.2.2.7 | | +| >>Altitude and direction | M | | 9.2.2.2 | | + +### 9.2.2.71 UE Positioning IPDL Parameters + +The *UE Positioning IPDL Parameters* IE is used for OTDOA in the SAS centric mode. + +**Table 121** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------------|----------|-------|-----------------------------------------------|-----------------------| +| CHOICE mode | | | | | +| >FDD | | | | | +| >>IP Spacing | M | | ENUMERATED(
5,7,10,15,20,30,
40,50,...) | See TS 25.331 [4] | +| >>IP Length | M | | ENUMERATED(
5,10,...) | See TS 25.331 [4] | +| >>IP Offset | M | | INTEGER(0..9) | See TS 25.331 [4] | +| >>Seed | M | | INTEGER(0..63) | See TS 25.331 [4] | +| >TDD | | | | | +| Burst Mode Parameters | O | | 9.2.2.72 | | + +### 9.2.2.72 Burst Mode Parameters + +*Burst Mode Parameters* IE is used for OTDOA in the SAS centric mode. + +Table 122 + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|-----------------|----------|-------|-----------------------|-----------------------| +| Burst Start | M | | INTEGER(0..15) | | +| Burst Length | M | | INTEGER(10..25) | | +| Burst Frequency | M | | INTEGER(1..16) | | + +### 9.2.2.73 SFN-SFN Relative Time Difference + +*SFN-SFN Relative Time Difference* IE is used for OTDOA in the SAS centric mode + +Table 123 + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------|----------|-------|-----------------------|-----------------------| +| SFN Offset | M | | INTEGER (0..4095) | | +| SFN-SFN-Relative Time Difference | M | | INTEGER (0..38399) | | + +### 9.2.2.74 UTDOA Group + +This IE contains information used for the U-TDOA positioning method. + +Table 124 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|--------------|-----------------------|-----------------------| +| UTRAN Cell Identifier | M | | 9.2.2.37 | | +| Frequency Information | M | | 9.2.2.42 | | +| Choice RRC State | M | | | | +| > CELL_DCH | | | | | +| >>Uplink DPCH Information | M | | 9.2.2.41 | | +| >>Compressed Mode Assistance Data | O | | 9.2.2.44 | FDD only | +| >> DCH Information | | 0..1 | | | +| >>> TFCS | | 1.. | | | +| >>> CTFC | M | | 9.2.2.49 | | +| >>> TrCH Information List | | 1.. | | | +| >>>>UL TrCH Information | M | | 9.2.2.60 | | +| >> E-DPCH Information | | 0..1 | | FDD only | +| >>>Maximum Set of E-DPDCHs | M | | 9.2.2.75 | | +| >>>Puncture Limit | M | | 9.2.2.76 | | +| >>>E-TFCS Information | M | | 9.2.2.77 | | +| >>>E-TTI | M | | 9.2.2.79 | | +| >>>E-DPCCH Power Offset | O | | 9.2.2.80 | | +| > CELL_FACH | | | | | +| >>PRACH Parameters | M | | 9.2.2.43 | | +| >>C-RNTI | M | | 9.2.2.45 | | +| >>USCH parameters | O | | 9.2.2.95 | TDD only | + +Table 125 + +| Range bound | Explanation | +|-------------|--------------------------------------------------------| +| maxTFC | Maximum number of TFC. The value is 1024. | +| maxTrCH | Maximum number of Transport Channels. The value is 32. | + +### 9.2.2.75 Maximum Set of E-DPDCHs + +The Maximum Set of E-DPDCHs parameter, as defined in TS 25.212 [16], is used in UTDOA positioning method. + +**Table 126** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|------------------------------------------------------------------------------------------|-----------------------| +| Maximum Set of E-DPDCHs | | | ENUMERATED
(vN64, vN32,
vN16, vN8, vN4,
v2xN4, v2xN2,
v2xN2plus2xN4,
...) | | + +### 9.2.2.76 Puncture Limit + +The Puncture Limit parameter is used in UTDOA positioning method indicating the limit in the amount of puncturing that can be applied in order to minimise the number of dedicated physical channels. + +**Table 127** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------|----------|-------|-----------------------|----------------------------------------------------------------------| +| Puncture Limit | | | INTEGER
(0..15) | Unit: %
Range: 40..100 %
Step: 4 %
100% means no puncturing | + +### 9.2.2.77 E-DCH Transport Format Combination Set Information (E-TFCS Information) + +This IE is used in UTDOA positioning method. Whereas the related Transport Block sizes are standardised in [ref is FFS] this IE gives details on the referenced Transport Block Size Table and the Reference E-TFCIs. + +**Table 128** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------------------------|----------|------------------------------------|------------------------|------------------------------------------------------------------------------------------------------------------------------| +| E-DCH Transport Format Combination Set Index | M | | INTEGER
(1..4, ...) | Indicates which standardised E-TFCS Transport Block Size Table shall be used. The related tables are specified in [ref FFS]. | +| Reference E-TFCI Information | | 0..<maxnoofRefETFCIs> | | | +| >Reference E-TFCI | M | | INTEGER
(0..127) | | +| >Reference E-TFCI Power Offset | M | | 9.2.2.78 | | + +**Table 129** + +| Range Bound | Explanation | +|-------------------------|-----------------------------------------------| +| maxnoofRefETFCIs | Maximum number of signalled reference E-TFCIs | + +### 9.2.2.78 Reference E-TFCI Power Offset + +The Reference E-TFCI Power Offset is used in UTDOA positioning method indicating how to calculate the reference E-TFC gain factor. + +**Table 130** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------|----------|-------|-----------------------|----------------------------------------------| +| Reference E-TFCI Power Offset | | | INTEGER (0..8) | According to mapping in ref. TS 25.213 [17]. | + +### 9.2.2.79 E-TTI + +The E-TTI parameter is used in UTDOA positioning method indicating the Transmission Time Interval for E-DPCH operation. + +**Table 131** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------------|-----------------------| +| E-TTI | | | ENUMERATED (2ms, 10ms, ...) | | + +### 9.2.2.80 E-DPCCH Power Offset + +The E-DPCCH Power Offset is used in UTDOA positioning method indicating how to calculate the E-DPCCH gain factor. + +**Table 132** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------|----------|-------|-----------------------|----------------------------------------------| +| E-DPCCH Power Offset | | | INTEGER (0..8) | According to mapping in ref. TS 25.213 [17]. | + +### 9.2.2.81 Cell Parameter ID + +The Cell Parameter ID identifies unambiguously the Code Groups, Scrambling Codes, Midambles and Toffset (see ref. TS 25.223 [18]). + +**Table 133** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------|----------|-------|-----------------------|-----------------------| +| Cell Parameter ID | | | INTEGER (0..127,...) | | + +### 9.2.2.82 TFCI Coding + +The TFCI Coding describes the way how the TFCI bits are coded. By default 1 TFCI bit is coded with 4 bits, 2 TFCI bits are coded with 8 bits, 3-5 TFCI bits are coded with 16 bits and 6-10 TFCI bits are coded with 32 bits. + +**Table 134** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-------------------------------|-----------------------| +| TFCI Coding | | | ENUMERATED (4, 8, 16, 32,...) | | + +### 9.2.2.83 Repetition Length + +The Repetition Length represents the number of consecutive Radio Frames inside a Repetition Period in which the same Time Slot is assigned to the same Physical Channel see ref. TS 25.331 [4]. + +Table 135 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------|----------|-------|-----------------------|-----------------------| +| Repetition Length | | | INTEGER (1..63) | | + +### 9.2.2.84 Repetition Period + +The Repetition Period represents the number of consecutive Radio Frames after which the same assignment scheme of Time Slots to a Physical Channel is repeated. This means that if the Time Slot $K$ is assigned to a physical channel in the Radio Frame $J$ , it is assigned to the same physical channel also in all the Radio Frames $J+n*Repetition\ Period$ (where $n$ is an integer) see ref. TS 25.331 [4]. + +Table 136 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------|----------|-------|--------------------------------------------|-----------------------| +| Repetition Period | | | ENUMERATED
(1, 2, 4, 8, 16, 32, 64,...) | | + +### 9.2.2.85 TDD DPCH Offset + +The Offset represents the phase information for the allocation of a group of dedicated physical channels. The first range is used when a starting offset is not required and the TDD Physical channel offset for each DPCH in the CCTrCH shall be directly determined from the TDD DPCH Offset. The second range is used when a starting offset is required. The TDD DPCH Offset shall map to the CFN and the TDD Physical Channel Offset for each DPCH in this CCTrCH shall be calculated by TDD DPCH Offset *mod* Repetition period, see ref. TS 25.331 [4]. + +Table 137 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------------|----------|-------|-----------------------|-----------------------| +| CHOICE Offset Type | | | | | +| > Initial Offset | | | | | +| >>TDD DPCH Offset Value | M | | INTEGER (0..255) | | +| > No Initial Offset | | | | | +| >>TDD DPCH Offset Value | M | | INTEGER (0..63) | | + +### 9.2.2.86 UL Timeslot Information + +The *UL Timeslot Information* IE provides information on the time slot allocation for an UL DPCH. + +Table 138 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------|----------|----------------------|-----------------------|-----------------------| +| UL Timeslot Information | | $1..$ | | | +| >Time Slot | M | | 9.2.2.87 | | +| >Midamble Shift And Burst Type | M | | 9.2.2.88 | | +| >TFCI Presence | M | | 9.2.2.89 | | +| >UL Code Information | M | | 9.2.2.90 | | + +Table 138A + +| Range Bound | Explanation | +|--------------------|-----------------------------------------------------------------------------------------------| +| maxnoofULts | Maximum number of allocated time slots for an UL DPCH. The value of maxnoofULts is 15. | + +### 9.2.2.87 Time Slot + +The Time Slot represents the minimum time interval inside a Radio Frame that can be assigned to a Physical Channel. + +**Table 139** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------| +| Time Slot | | | INTEGER (0..14) | | + +### 9.2.2.88 Midamble Shift And Burst Type + +This information element indicates burst type and midamble allocation. + +The 256 chip midamble supports 3 different time shifts, the 512 chips midamble may support 8 or even 16 time shifts. + +Three different midamble allocation schemes exist: + +Default midamble: the midamble shift is selected by layer 1 depending on the associated channelisation code (DL and UL) + +Common midamble: the midamble shift is chosen by layer 1 depending on the number of channelisation codes (possible in DL only) + +UE specific midamble: a UE specific midamble is explicitly assigned (DL and UL) + +**Table 140** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------------|----------|-------|-----------------------|-------------------------------| +| CHOICE Burst Type | | | | | +| >Type1 | | | | | +| >>Midamble Configuration Burst Type 1 And 3 | M | | INTEGER (4, 8, 16) | As defined in TS 25.221 [19]. | +| >>CHOICE Midamble Allocation Mode | M | | | | +| >>>Default Midamble | | | NULL | | +| >>>Common Midamble | | | NULL | | +| >>>UE Specific Midamble | | | | | +| >>Midamble Shift Long | M | | INTEGER (0..15) | | +| >Type2 | | | | | +| >>Midamble Configuration Burst Type 2 | M | | INTEGER (3,6) | As defined in TS 25.221 [19]. | +| >>CHOICE Midamble Allocation Mode | M | | | | +| >>>Default Midamble | | | NULL | | +| >>>Common Midamble | | | NULL | | +| >>>UE Specific Midamble | | | | | +| >>Midamble Shift Short | M | | INTEGER (0..5) | | +| >Type3 | | | | UL only | +| >>Midamble Configuration Burst Type 1 And 3 | M | | INTEGER (4, 8, 16) | As defined in TS 25.221 [19]. | +| >>CHOICE Midamble Allocation Mode | M | | | | +| >>>Default Midamble | | | NULL | | +| >>>UE Specific Midamble | | | | | +| >>Midamble Shift Long | M | | INTEGER (0..15) | | + +### 9.2.2.89 TFCI Presence + +The TFCI Presence parameter indicates whether the TFCI shall be included. [TDD - If it is present in the timeslot, it will be mapped to the channelisation code defined by TS 25.221 [19].] + +**Table 141** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|------------------------------------|-----------------------| +| TFCI presence | | | ENUMERATED ( Present, Not Present) | | + +### 9.2.2.90 TDD UL Code Information + +The *TDD UL Code Information* IE provides information for UL Codes that have been established. + +**Table 142** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------|----------|--------------------|-----------------------|-----------------------| +| TDD UL Code Information | | 1.. | | | +| >TDD Channelisation Code | M | | 9.2.2.91 | | + +**Table 143** + +| Range Bound | Explanation | +|---------------------|---------------------------------------| +| maxnoofDPCHs | Maximum number of DPCHs in one CCTrCH | + +### 9.2.2.91 TDD Channelisation Code + +The Channelisation Code Number indicates which Channelisation Code is used for a given Physical Channel. In TDD the Channelisation Code is an Orthogonal Variable Spreading Factor code, that can have a spreading factor of 1, 2, 4, 8 or 16. + +**Table 144** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|-------|---------------------------------------------------------------------------------------------|-----------------------| +| TDD Channelisation Code | | | ENUMERATED ( (1/1), (2/1), (2/2), (4/1), .. (4/4), (8/1), .. (8/8), (16/1), .. (16/16),...) | | + +### 9.2.2.92 Special Burst Scheduling + +This information element expresses the number of frames between special burst transmissions during DTX. + +**Table 145** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------|----------|-------|-----------------------|----------------------------------------------------------------| +| Special Burst Scheduling | | | INTEGER (1..256) | Number of frames between special burst transmission during DTX | + +### 9.2.2.93 Max PRACH Midamble Shift + +Indicates the maximum number of Midamble shifts to be used in a cell. + +**Table 146** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------|----------|-------|-----------------------|-----------------------| +| Max PRACH Midamble Shift | | | ENUMERATED (4, 8,...) | | + +### 9.2.2.94 PRACH Midamble + +The PRACH Midamble indicates if only the Basic Midamble Sequence or also the time-inverted Midamble Sequence is used. + +**Table 147** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------|----------|-------|-------------------------------------|-----------------------| +| PRACH Midamble | | | ENUMERATED ( Inverted, Direct, ...) | | + +### 9.2.2.95 USCH Parameters + +In Cell-FACH state, when the UE supports the USCH, and the CRNC is equal to the SRNC, the UE may be given periodic allocations on the uplink shared channel. Furthermore, the UE may also be configured to generate special bursts instead of uplink shared channel transmissions. This information element defines the uplink shared channel transmissions. + +**Table 148** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------|----------|--------------|-----------------------|----------------------------------------------| +| Cell Parameter ID | M | | 9.2.2.81 | | +| TFCI Coding | M | | 9.2.2.82 | | +| Puncture Limit | M | | 9.2.2.76 | | +| Repetition Period | M | | 9.2.2.84 | This is the scheduling interval on the USCH. | +| USCH Scheduling Offset | M | | 9.2.2.96 | | +| UL Timeslot Information | M | | 9.2.2.86 | | +| TFCS | | 1.. | | | +| >CTFC | M | | 9.2.2.49 | | +| TrCH Information List | | 1.. | | | +| >UL TrCH Information | M | | 9.2.2.60 | | + +**Table 149** + +| Range bound | Explanation | +|-------------|--------------------------------------------------------| +| maxTFC | Maximum number of TFC. The value is 1024. | +| maxTrCH | Maximum number of Transport Channels. The value is 32. | + +### 9.2.2.96 USCH Scheduling Offset + +This information element indicates the offset relative to CFN=0 that the transmission on the uplink shared channel shall take place. + +**Table 150** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|-----------------------|-----------------------| +| USCH scheduling offset | | | INTEGER(0..255) | | + +### 9.2.2.97 Include Velocity + +This element indicates that the UE's velocity is requested. + +**Table 151** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------|-----------------|--------------|------------------------------|------------------------------| +| Include Velocity | M | | ENUMERATED
(requested) | | + +### 9.2.2.98 Velocity Estimate + +The *Velocity Estimate* IE is used to describe the UE's velocity. The reference system is the same as used in TS 23.032 [11]. + +Table 152 + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Choice Velocity Estimate | | | | | +| >Horizontal Velocity | | | | Horizontal speed and bearing (the direction of travel). | +| >>Horizontal Speed and Bearing | M | | 9.2.2.99 | | +| >Horizontal with Vertical Velocity | | | | Horizontal speed and bearing (the direction of travel) as well as vertical speed and the direction (upward or downward) | +| >>Horizontal Speed and Bearing | M | | 9.2.2.99 | | +| >>Vertical Velocity | M | | 9.2.2.100 | | +| >Horizontal Velocity with Uncertainty | | | | Horizontal speed, bearing (the direction of travel), and the uncertainty of the reported speed. | +| >>Horizontal Speed and Bearing | M | | 9.2.2.99 | | +| >>Uncertainty Speed | M | | INTEGER (0..255) | Uncertainty speed is encoded in increments of 1 kilometer per hour using an 8 bit binary coded number (N). The value of N gives the uncertainty speed except for N=255 which indicates that the uncertainty is not specified | +| >Horizontal with Vertical Velocity and Uncertainty | | | | Horizontal speed and bearing (the direction of travel) as well as vertical speed and the direction (upward or downward) and the uncertainty of the reported speed. | +| >>Horizontal Speed and Bearing | M | | 9.2.2.99 | | +| >>Vertical Velocity | M | | 9.2.2.100 | | +| >>Horizontal Uncertainty Speed | M | | INTEGER (0..255) | Horizontal Uncertainty Speed is encoded in increments of 1 kilometer per hour using an 8 bit binary coded number (N). The value of N gives the uncertainty speed except for N=255 which indicates that the uncertainty is not specified | +| >>Vertical Uncertainty Speed | M | | INTEGER (0..255) | Vertical Uncertainty Speed is encoded in increments of 1 kilometer per hour using an 8 bit binary coded number (N). The value of N gives the uncertainty speed except for N=255 which indicates that the uncertainty is not specified | + +### 9.2.2.99 Horizontal Speed and Bearing + +This IE contains the two components of horizontal velocity: speed and bearing + +**Table 153** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|------------------|----------|-------|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Bearing | M | | INTEGER (0..359) | The direction of movement is given in degrees where '0' represents North, '90' represents East, etc. | +| Horizontal Speed | M | | INTEGER (0.. $2^{11}-1$ ) | The relationship between (N) and the horizontal speed (h) in kilometers per hour it describes is:
$N \leq h < N + 0.5$ (N=0)
$N - 0.5 \leq h < N + 0.5$ (0$N - 0.5 \leq h$ (N = $2^{11}-1$ ) | + +### 9.2.2.100 Vertical Velocity + +This IE contains the two components of vertical velocity: speed and direction + +**Table 154** + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------|----------|-------|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Vertical Speed | M | | INTEGER (0.. $2^8-1$ ) | The relationship between (N) and the vertical speed (v) in kilometers per hour it describes is:
$N \leq v < N + 0.5$ (N = 0)
$N - 0.5 \leq v < N + 0.5$ (0 < N < $2^8-1$ )
$N - 0.5 \leq v$ (N = $2^8-1$ ) | +| Vertical Speed Direction | | | ENUMERATED (upward, downward) | | + +### 9.2.2.101 GPS Positioning Instructions + +This information element contains positioning instructions for GPS positioning method in SAS-centric mode. + +**Table 155** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------|-----------------|--------------|-------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|--------------------|-----------------------------| +| Horizontal Accuracy Code | O | | 9.2.2.38 | | – | | +| Vertical Accuracy Code | O | | 9.2.2.39 | | – | | +| GPS Timing of Cell Wanted | M | | BOOLEAN | This IE is set to TRUE if the UE is requested to report SFN-GPS timing of the reference cell. | – | | +| Additional Assistance Data Request | M | | BOOLEAN | TRUE indicates that the UE is requested to send an additional assistance data request if the provided assistance data are not sufficient. | – | | +| Measurement Validity | O | | ENUMERATED(CELL_DCH, all states except CELL_DCH, all states, ...) | | YES | ignore | + +### 9.2.2.102 UE Position Estimate Info + +The UE Position Estimate Info is used in UE-based positioning methods providing the UE position estimate from the RNC to the SAS in SAS-centric mode. + +Table 156 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------------------------|----------|-------|--------------------------------------------|-----------------------------------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE Reference Time | M | | | | – | | +| >UTRAN GPS reference time Result | | | 9.2.2.104 | | – | | +| >GPS reference time only | | | | | – | | +| >>GPS TOW msec | M | | INTEGER (0..6.048*10 8 -1, ...) | GPS Time of Week in milliseconds. | – | | +| >Cell timing | | | | | – | | +| >>SFN | M | | INTEGER (0..4095) | SFN during which the position was calculated. | – | | +| >>UC-ID | M | | UTRAN Cell Identifier 9.2.2.37 | Identifies the reference cell for SFN. | – | | +| >UTRAN GANSS reference time result | | | | | – | | +| >>UTRAN-GANSS Reference Time Result | M | | 9.2.2.136 | | YES | ignore | +| >GANSS reference time only | | | | | – | | +| >>GANSS reference time only | M | | | | YES | ignore | +| >>>GANSS TOD msec | M | | INTEGER(0..35 99999) | GANSS Time of Day in milliseconds. | – | | +| >>>GANSS time ID | O | | GANSS ID 9.2.2.130 | Absence of this IE means Galileo system time. The value '0' ('SBAS') shall not be used for GANSS Time ID. | – | | +| UE Position Estimate | M | | Geographical Area 9.2.2.6 | | – | | +| GPS Reference Time Uncertainty | O | | 9.2.2.132 | | YES | ignore | +| Position Data | O | | Position Data UE-Based 9.2.2.140 | | YES | ignore | + +## 9.2.2.103 UTRAN-GPS Reference Time + +Table 157 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------|----------|-------|---------------------------------|-----------------------------------------------------------------| +| UTRAN GPS timing of cell frames | M | | INTEGER (0..2322431999999, ...) | GPS timing of cell frames in steps of 1 chip. | +| UC-ID | O | | UTRAN Cell Identifier 9.2.2.37 | Identifies the reference cell for the GPS TOW-SFN relationship. | +| SFN | M | | INTEGER (0..4095) | The SFN which the UTRAN GPS timing of cell frames time stamps. | + +## 9.2.2.104 UTRAN-GPS Reference Time Result + +Table 158 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------|----------|-------|---------------------------------|-----------------------------------------------------------------------------------------| +| UE GPS timing of cell frames | M | | INTEGER(0..37158911999999, ...) | GPS Time of Week in units of 1/16 th UMTS chips according to TS 25.133 [13]. | +| UC-ID | M | | UTRAN Cell Identifier 9.2.2.37 | Identifies the reference cell for the GPS TOW-SFN relationship | +| SFN | M | | INTEGER(0..4095) | This IE indicates the SFN at which the UE timing of cell frame is captured. | + +## 9.2.2.105 TUTRAN-GPS Drift Rate + +Table 159 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|-------|------------------------------------------------------------------------------|-------------------------| +| T UTRAN-GPS Drift Rate | O | | ENUMERATED (0, 1, 2, 5, 10, 15, 25, 50, -1, -2, -5, -10, -15, -25, -50, ...) | In 1/256 chips per sec. | + +## 9.2.2.106 Periodic Position Calculation Info + +The Periodic Position Calculation Info contains information required for periodic location in RNC-centric mode. + +Table 160 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------|----------|-------|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Reference Number | M | | INTEGER (0..32767,...) | This IE is used to uniquely associate all periodic Position Calculation procedures belonging to the location of the same target UE for periodic location. Position Calculation procedures belonging to the same target UE for periodic location shall use the same Reference Number. | +| Amount of Outstanding Requests | M | | INTEGER (1.. 8639999,...) | This IE indicates the amount of outstanding periodic requests. This IE shall be set to the total number of periodic requests in the first Position Calculation Request message, and decrement by 1 for each new Position Calculation Request for periodic location. When the number reaches 1, the SAS will know that the periodic location is complete. | +| Reporting Interval | M | | INTEGER (1.. 8639999,...) | This IE indicates the reporting interval in seconds when the SAS can expect a next Position Calculation Request associated to the same target UE in periodic location. | + +### 9.2.2.107 Periodic Location Info + +The Periodic Location Info contains the periodic reporting interval and reporting amount for periodic location. + +**Table 161** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------|----------|-------|------------------------------|------------------------------------------------------| +| Reporting Amount | M | | INTEGER
(1.. 8639999,...) | This IE indicates the amount of periodic reports. | +| Reporting Interval | M | | INTEGER
(1.. 8639999,...) | This IE indicates the reporting interval in seconds. | + +### 9.2.2.108 Amount of Reporting + +The Amount of Reporting together with the *RNC Response Time IE* in a POSITION ACTIVATION REQUEST message defines the periodical reporting criteria. + +**Table 162** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|------------------------------------------------|--------------------------------------------------------| +| Amount of Reporting | M | | ENUMERATED(2, 4, 8, 16, 32, 64, Infinity, ...) | Amount of reporting for a periodic location procedure. | + +### 9.2.2.109 Measurement Instructions Used + +This information element contains measurement instructions used by the SRNC upon reception of a POSITION ACTIVATION REQUEST message. + +**Table 163** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------|----------|-------|--------------------------------------------------------------------------------|-----------------------| +| Measurement Validity | M | | ENUMERATED(
CELL_DCH, all
states except
CELL_DCH, all
states, ...) | | + +### 9.2.2.110 RRC State Change + +**Table 164** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|---------------------------------------------------------------|-----------------------| +| New RRC State | M | | ENUMERATED(CELL_DCH,
CELL_FACH, CELL_PCH,
URA_PCH, ...) | | + +### 9.2.2.111 Periodic Position Termination Cause + +The Position Periodic Termination Cause element indicates the reason for termination of a periodic reporting procedure in SAS-centric mode. + +**Table 165** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------|-----------------|--------------|----------------------------------------------------------------------------------------------------|------------------------------| +| Periodic Position Termination Cause | M | | ENUMERATED(
RRC State Transition,
Cancelled by SRNC,
Cancelled by SAS,
Undefined,
) | | + +### 9.2.2.112 Requested Cell-ID Measurements + +This information element contains a list of requested measurements for Cell-ID positioning method in SAS-centric mode. + +**Table 166** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Choice mode | M | | | | | | +| >FDD | | | | | - | | +| >>Round Trip Time Info | M | | BOOLEAN | If set to TRUE, the RNC is requested to include the Round Trip Time Info IE in the Cell-ID Measured Results Info List. | - | | +| >>Pathloss | M | | BOOLEAN | If set to TRUE, the RNC is requested to include the Pathloss IE in the Cell-ID Measured Results Info List. | - | | +| >>Round Trip Time Info With Type 1 | M | | BOOLEAN | If set to TRUE, the RNC is requested to include the Round Trip Time Info With Type 1 IE in the Cell-ID Measured Results Info List. | - | | +| >>CPICH RSCP | M | | BOOLEAN | If set to TRUE, the RNC is requested to include the CPICH RSCP IE in the Cell-ID Measured Results Info List. | - | | +| >>CPICH Ec/N0 | M | | BOOLEAN | If set to TRUE, the RNC is requested to include the CPICH Ec/N0 IE in the Cell-ID Measured Results Info List. | - | | +| >TDD | | | | | | | +| >>Rx Timing Deviation Info | M | | BOOLEAN | If set to TRUE, the RNC is requested to include the Rx Timing Deviation Info IE in the Cell-ID Measured Results Info List. | - | | +| >>Pathloss | M | | BOOLEAN | If set to TRUE, the RNC is requested to include the Pathloss IE in the Cell-ID Measured Results Info List. | - | | +| >>Rx Timing Deviation LCR Info | M | | BOOLEAN | If set to TRUE, the RNC is requested to include the Rx Timing Deviation LCR Info IE in the Cell-ID Measured Results Info List. | - | | +| >>Rx Timing Deviation 768Info | M | | BOOLEAN | If set to TRUE, the RNC is requested to include the Rx Timing Deviation 768Info IE in the Cell-ID Measured Results Info List. | - | | +| >>Rx Timing Deviation 384ext Info | M | | BOOLEAN | If set to TRUE, the RNC is requested to include the Rx Timing Deviation 384ext Info IE in the Cell-ID Measured Results Info List. | - | | +| >>Angle Of Arrival LCR | M | | BOOLEAN | If set to TRUE, the RNC is requested to include the Angle Of Arrival LCR IE in the Cell-ID Measured Results Info List. | - | | +| >>Timing Advance LCR | M | | BOOLEAN | If set to TRUE, the RNC is requested to include the Timing Advance LCR IE (or the Extended Timing Advance LCR IE) in the Cell-ID Measured Results Info List. | - | | +| GERAN | O | | | | YES | reject | +| >GSM RSSI | M | | BOOLEAN | If set to TRUE, the RNC is requested to include the GSM RSSI measurement as part of the IRAT Measured Result Info List | | | + +### 9.2.2.113 DGANSS Corrections + +This IE contains DGANSS corrections to be used by the UE. + +**Table 167** + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|--------------------------------------|-----------------|------------------|------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| DGANSS Reference Time | M | | INTEGER (0..3570 by step of 30) | Seconds. Time in GNSS system time (modulo 3600 s) when the DGANSS corrections were calculated | – | | +| DGANSS Information | | 1.. | | | – | | +| >GANSS Signal ID | O | | 9.2.2.131 | Absence of this field means the default value for the GANSS identified by "GANSS ID" (TS 25.331 [4]). | – | | +| >Status/Health | M | | ENUMERATED(UDRE scale 1.0, UDRE scale 0.75, UDRE scale 0.5, UDRE scale 0.3, UDRE scale 0.2, UDRE scale 0.1, no data, invalid data) | | – | | +| >DGANSS Signal Information | C-Status/Health | 1.. | | | – | | +| >>Sat ID | M | | INTEGER(0..63) | Defined in TS 25.331 [4]. | – | | +| >>IOD | M | | BIT STRING (SIZE(10)) | | – | | +| >>UDRE | M | | ENUMERATED(UDRE ≤ 1.0 m, 1.0m < UDRE ≤ 4.0m, 4.0m < UDRE ≤ 8.0m, 8.0m < UDRE) | The value in this field shall be multiplied by the UDRE Scale Factor in the IE Status/Health to determine the final UDRE estimate for the particular satellite. | – | | +| >>PRC | M | | INTEGER (-2047..2047) | Scaling factor 0.32 meters | – | | +| >>RRC | M | | INTEGER (-127..127) | Scaling factor 0.032 meters/sec | – | | +| >>DGNSS Validity Period | O | | 9.2.2.154 | | YES | ignore | + +**Table 167A** + +| Range bound | Explanation | +|-------------|----------------------------------------------------------------------------------------------------| +| maxSgnType | Maximum number of signals for which data is included in this IE. The value of maxSgnType is 8 | +| maxGANSSSat | Maximum number of satellites for which data is included in this IE. The value of maxGANSSSat is 64 | + +**Table 167B** + +| Condition | Explanation | +|----------------------|-----------------------------------------------------------------------------------------------------| +| Status/Health | This IE shall be present if the Status/Health IE value is not equal to "no data" or "invalid data". | + +### 9.2.2.114 GANSS Almanac and Satellite Health + +This IE contains a reduced-precision subset of the ephemeris and clock correction parameters. + +**Table 168** + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------------|----------|---------------------------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Week Number | M | | INTEGER(0..255) | Almanac reference week , number of weeks since the beginning of GANSS specific system time (mod 256) | – | | +| CHOICE Almanac Model | M | | | | – | | +| > Keplerian Parameters | | | | Model 1 | – | | +| >>T oa | M | | INTEGER(0..1023) | Scaling factor 600 s Reference time of almanac within week in GANSS TOD time base (OS SIS ICD [22]). | – | | +| >>IOD a | M | | INTEGER(0..15) | Issue-Of –Data, common to all satellites (OS SIS ICD [22]). | – | | +| >>> Satellite Information KP | | 1..
ANS
SS
atAlman
ac> | | Almanacs are in the order of the SV IDs, the smallest ID first. | – | | +| >>>Sat ID | M | | INTEGER(0..63) | Defined in TS 25.331 [4]. | – | | +| >>>e | M | | BIT STRING (SIZE(11)) | dimensionless (OS SIS ICD [22]) | – | | +| >>>δi | M | | BIT STRING (SIZE(11)) | semi-circles (OS SIS ICD [22]) | – | | +| >>>OMEGADOT | M | | BIT STRING (SIZE(11)) | semi-circles/sec (OS SIS ICD [22]) | – | | +| >>>SV Status INAV | M | | BIT STRING (SIZE(4)) | dimensionless (OS SIS ICD [22]). E5b HS occupies the 2 MSBs and E1-B HS the two LSBs. | – | | +| >>>SV Status FNAV | O | | BIT STRING (SIZE(2)) | Dimensionless (OS SIS ICD [22]). E5a HS . | – | | +| >>>delta A 1/2 | M | | BIT STRING (SIZE(13)) | (meters) 1/2 (OS SIS ICD [22]) | – | | +| >>>OMEGA 0 | M | | BIT STRING (SIZE(16)) | semi-circles (OS SIS ICD [22]) | – | | +| >>>M 0 | M | | BIT STRING (SIZE(16)) | semi-circles (OS SIS ICD [22]) | – | | +| >>>ω | M | | BIT STRING (SIZE(16)) | semi-circles (OS SIS ICD [22]) | – | | +| >>>af 0 | M | | BIT STRING (SIZE(16)) | Seconds (OS SIS ICD [22]) | – | | +| >>>af 1 | M | | BIT STRING (SIZE(13)) | sec/sec (OS SIS ICD [22]) | – | | +| > NAV Keplerian Parameters | | | | Model 2 | | | +| >> Keplerian NAV Almanac | M | | | | YES | ignore | +| >>>T oa | M | | INTEGER(0..255) | Scaling factor 2 12 s Reference time of almanac within week in GANSS TOD time base | – | | +| >>>> Satellite information NAV-KP | | 1..
ANS
SS
atAlman
ac> | | | – | | +| >>>>Sat ID | M | | INTEGER (0..63) | Defined in TS 25.331 [4]. | – | | +| >>>>e | M | | BIT STRING (SIZE(16)) | Eccentricity, dimensionless (IS-QZSS [27]) | – | | +| >>>>δi | M | | BIT STRING (SIZE(16)) | Correction to inclination, semi-circles (IS-QZSS | – | | + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|----------------------|-----------------|--------------|------------------------------|------------------------------|--------------------|-----------------------------| +| | | | | [27]) | | | + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------|----------|---------------------------------------------|-----------------------|-----------------------------------------------------------------------------------------------|-------------|----------------------| +| >>>>OMEGADOT | M | | BIT STRING (SIZE(16)) | Rate of right ascension, semi-circles/sec (IS-QZSS [27]) | – | | +| >>>>SV Health | M | | BIT STRING (SIZE(8)) | Satellite health (IS-QZSS [27]) | – | | +| >>>>A 1/2 | M | | BIT STRING (SIZE(24)) | Square root of the semi-major axis, meters 1/2 (IS-QZSS [27]) | – | | +| >>>>OMEGA 0 | M | | BIT STRING (SIZE(24)) | Longitude of ascending node of orbit plane at weekly epoch, semi-circles (IS-QZSS [27]) | – | | +| >>>>ω | M | | BIT STRING (SIZE(24)) | Argument of perigee semi-circles (IS-QZSS [27]) | – | | +| >>>>M 0 | M | | BIT STRING (SIZE(24)) | Mean anomaly at reference time semi-circles (IS-QZSS [27]) | – | | +| >>>>af 0 | M | | BIT STRING (SIZE(11)) | Apparent satellite clock correction seconds (IS-QZSS [27]) | – | | +| >>>>af 1 | M | | BIT STRING (SIZE(11)) | Apparent satellite clock correction sec/sec (IS-QZSS [27]) | – | | +| >Reduced Keplerian Parameters | | | | Model 3 | | | +| >>Keplerian Reduced Almanac | M | | | | YES | ignore | +| >>>T oa | M | | INTEGER(0..255) | Scaling factor 2 12 s Reference time of almanac within week in GANSS TOD time base | – | | +| >>>Satellite information RED-KP | | 1..
ANS
SS
atAlman
ac> | | | – | | +| >>>>Sat ID | M | | INTEGER (0..63) | Defined in TS 25.331 [4]. | – | | +| >>>>δ A | M | | BIT STRING (SIZE(8)) | meters (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>>>Ω 0 | M | | BIT STRING (SIZE(7)) | semi-circles (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>>>Φ 0 | M | | BIT STRING (SIZE(7)) | semi-circles (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>>>L1 Health | M | | BIT STRING (SIZE(1)) | dimensionless (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>>>L2 Health | M | | BIT STRING (SIZE(1)) | dimensionless (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>>>L5 Health | M | | BIT STRING | dimensionless (IS- | – | | + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|--------------------------------------------------------------------------|-------------|----------------------| +| | | | (SIZE(1)) | GPS-200 [23], IS-
GPS-705 [24], IS-
GPS-800 [25], IS-QZSS
[27]) | | | + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------|----------|-------------------------------------|-----------------------|--------------------------------------------------------------------------------------------------|-------------|----------------------| +| >Midi Keplerian Parameters | | | | Model 4 | | | +| >>Keplerian Midi Almanac | M | | | | YES | ignore | +| >>>T oa | M | | INTEGER(0..255) | Scaling factor 2 12 s
Reference time of almanac within week in GANSS TOD time base | – | | +| >>>Satellite information MIDI-KP | | 1..
ANSSS
atAlmanac> | | | – | | +| >>>>Sat ID | M | | INTEGER(0..63) | Defined in TS 25.331 [4]. | – | | +| >>>>e | M | | BIT STRING (SIZE(11)) | dimensionless (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>>>δ i | M | | BIT STRING (SIZE(11)) | semi-circles (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>>>Ω dot | M | | BIT STRING (SIZE(11)) | semi-circles/sec (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>>>sqrtA | M | | BIT STRING (SIZE(17)) | meters 1/2 (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>>>Ω 0 | M | | BIT STRING (SIZE(16)) | semi-circles (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>>>ω | M | | BIT STRING (SIZE(16)) | semi-circles (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>>>M 0 | M | | BIT STRING (SIZE(16)) | semi-circles (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>>>a fo | M | | BIT STRING (SIZE(11)) | seconds (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>>>a fr | M | | BIT STRING (SIZE(10)) | sec/sec (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>>>L1 Health | M | | BIT STRING (SIZE(1)) | Dimensionless (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>>>L2 Health | M | | BIT STRING (SIZE(1)) | dimensionless (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>>>L5 Health | M | | BIT STRING | dimensionless (IS- | – | | + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|---------------------------------------------------------------|-------------|----------------------| +| | | | (SIZE(1)) | GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | | | + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------|----------|-------------------------------------|-----------------------|----------------------------------------|-------------|----------------------| +| >GLONASS Keplerian Parameters | | | | Model 5 | | | +| >>Keplerian GLONASS | M | | | | YES | ignore | +| >>>Satellite information GLO-KP | | 1..
ANSSS
atAlmanac> | | | – | | +| >>>>N A | M | | BIT STRING (SIZE(11)) | days [28] | – | | +| >>>>n A | M | | BIT STRING (SIZE(5)) | dimensionless [28] | – | | +| >>>>H n A | M | | BIT STRING (SIZE(5)) | dimensionless [28] | – | | +| >>>>λ n A | M | | BIT STRING (SIZE(21)) | semi-circles [28] | – | | +| >>>>t u,n A | M | | BIT STRING (SIZE(21)) | seconds [28] | – | | +| >>>>Δi n A | M | | BIT STRING (SIZE(18)) | semi-circles [28] | – | | +| >>>>ΔT n A | M | | BIT STRING (SIZE(22)) | sec/orbit period [28] | – | | +| >>>>ΔT n A _DOT | M | | BIT STRING (SIZE(7)) | sec/orbit period 2 [28] | – | | +| >>>>ε n A | M | | BIT STRING (SIZE(15)) | dimensionless [28] | – | | +| >>>>ω n A | M | | BIT STRING (SIZE(16)) | semi-circles [28] | – | | +| >>>>t n A | M | | BIT STRING (SIZE(10)) | seconds [28] | – | | +| >>>>C n A | M | | BIT STRING (SIZE(1)) | dimensionless [28] | – | | +| >>>>M n A | O | | BIT STRING (SIZE(2)) | dimensionless [28] | – | | +| >SBAS ECEF Parameters | | | | Model 6 | | | +| >>ECEF SBAS Almanac | M | | | | YES | ignore | +| >>>Satellite information SBAS-ECEF | | 1..
ANSSS
atAlmanac> | | | – | | +| >>>>Data ID | M | | BIT STRING (SIZE(2)) | Dimensionless (DTFA01-96-C-00025 [26]) | – | | +| >>>>SV ID | M | | INTEGER (0..63) | Defined in TS 25.331 [4]. | – | | +| >>>>Health | M | | BIT STRING (SIZE(8)) | Dimensionless (DTFA01-96-C-00025 [26]) | – | | +| >>>>X G | M | | BIT STRING (SIZE(15)) | meters (DTFA01-96-C-00025 [26]) | – | | +| >>>>Y G | M | | BIT STRING (SIZE(15)) | meters (DTFA01-96-C-00025 [26]) | – | | +| >>>>Z G | M | | BIT STRING (SIZE(9)) | meters (DTFA01-96-C-00025 [26]) | – | | +| >>>>X G Rate-of-Change | M | | BIT STRING (SIZE(3)) | meters/sec (DTFA01-96-C-00025 [26]) | – | | +| >>>>Y G Rate-of-Change | M | | BIT STRING (SIZE(3)) | meters/sec (DTFA01-96-C-00025 [26]) | – | | +| >>>>Z G Rate-of-Change | M | | BIT STRING (SIZE(4)) | meters/sec (DTFA01-96-C-00025 [26]) | – | | +| >>>>t 0 | M | | BIT STRING (SIZE(11)) | seconds (DTFA01-96-C-00025 [26]) | – | | +| >BDS Keplerian Parameters | | | | Model 7 | | | +| >>Keplerian BDS Almanac | M | | | | YES | ignore | + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------------------------|----------|---------------------------------------------|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| >>>Satellite information
BDS-KP | | 1..
ANS
SS
atAlman
ac> | | | – | | +| >>>>SV ID | M | | INTEGER
(0..63) | Defined in TS 25.331 [4]. | – | | +| >>>>t oa | M | | BIT STRING
(SIZE(8)) | Almanac reference time (seconds) (BDS-SIS-ICD-B1I-1.0 [33]) | – | | +| >>>>A 1/2 | M | | BIT STRING
(SIZE(24)) | Square root of semi-major axis (meters 1/2 ) (BDS-SIS-ICD [33]) | – | | +| >>>>e | M | | BIT STRING
(SIZE(17)) | Eccentricity , dimensionless (BDS-SIS-ICD [33]) | – | | +| >>>>ω | M | | BIT STRING
(SIZE(24)) | Argument of Perigee (semi-circles) (BDS-SIS-ICD [33]) | – | | +| >>>>M 0 | M | | BIT STRING
(SIZE(24)) | Mean anomaly at reference time (semi-circles) (BDS-SIS-ICD [33]) | – | | +| >>>>Ω 0 | M | | BIT STRING
(SIZE(24)) | Longitude of ascending node of orbital plane computed according to reference time (semi-circles) (BDS-SIS-ICD [33]) | – | | +| >>>>Ω | M | | BIT STRING
(SIZE(17)) | Rate of right ascension (semi-circles/sec) (BDS-SIS-ICD [33]) | – | | +| >>>>δ i | M | | BIT STRING
(SIZE(16)) | Correction of orbit reference inclination at reference time (semi-circles) (BDS-SIS-ICD [33]) | – | | +| >>>>a 0 | M | | BIT STRING
(SIZE(11)) | Satellite clock bias (seconds) (BDS-SIS-ICD [33]) | – | | +| >>>>a 1 | M | | BIT STRING
(SIZE(11)) | Satellite clock rate (sec/sec) (BDS-SIS-ICD [33]) | | | +| >>>>Hea | C-SV-ID | | BIT STRING
(SIZE(9)) | Satellite Health Information dimensionless (BDS-SIS-ICD [33]) | | | +| Complete Almanac Provided | O | | BOOLEAN | This field indicates whether the SAS provided almanac for the full GANSS constellation or not. TRUE means complete GANSS almanac is provided. | YES | ignore | + +Table 168A + +| Range bound | Explanation | +|--------------------|----------------------------------------------------------------------------------------------------| +| maxGANSSSatAlmanac | Maximum number of satellites for which data is included in this IE. The value of maxGANSSSat is 36 | + +**Table 168B** + +| Condition | Explanation | +|-----------|----------------------------------------------------------------------------------------------| +| SV-ID | This IE is mandatory present if the IE "SV ID" is between 0 and 29 and not needed otherwise. | + +### 9.2.2.115 GANSS Clock Model + +The IE contains fields needed to model the GANSS clock parameters. + +**Table 169** + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|-----------------------|----------|-----------------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------| +| Satellite Clock Model | | 1.. | | Model-1.
There may be more than one clock model included if defined in SIS ICD (i.e., two for Galileo) (OS SIS ICD [22]). | +| >t oc | M | | BIT STRING (SIZE(14)) | defined in OS SIS ICD [22] | +| >a l2 | M | | BIT STRING (SIZE(6)) | defined in OS SIS ICD [22] | +| >a l1 | M | | BIT STRING (SIZE(21)) | defined in OS SIS ICD [22] | +| >a l0 | M | | BIT STRING (SIZE(31)) | defined in OS SIS ICD [22] | +| >T GD | O | | BIT STRING (SIZE(10)) | Broadcast Group Delay (BGD) defined in OS SIS ICD [22] | +| >SISA | M | | BIT STRING (SIZE(8)) | Signal-In-Space Accuracy (SISA), defined in OS SIS ICD [22]. | +| >Model ID | O | | INTEGER(0..3) | Coded as defined in Table 169B. | + +**Table 169A** + +| Range bound | Explanation | +|------------------|--------------------------------------------------------------------------------------------------------------------| +| maxGANSSClockMod | Maximum number of satellite clock models for which data is included in this IE. The value of maxGANSSClockMod is 4 | + +**Table 169B** + +| GANSS Id | Model ID Value | Explanation | +|----------|----------------|----------------| +| Galileo | 0 | I/NAV (E1,E5b) | +| | 1 | F/NAV (E1,E5a) | +| | 2 | Reserved | +| | 3 | Reserved | + +### 9.2.2.115A GANSS Additional Clock Models + +The IE contains fields needed to model the GANSS clock parameters. + +**Table 169C** + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE Additional Clock Models | | | | | – | | +| >NAV-Clock Model | | | | Model-2 | – | | +| >>t oc | M | | BIT STRING (SIZE(16)) | Time of clock (seconds) (IS-QZSS [27]) | – | | +| >>af 2 | M | | BIT STRING (SIZE(8)) | Clock correction polynomial coefficient (sec/sec 2 ) (IS-QZSS [27]) | – | | +| >>af 1 | M | | BIT STRING (SIZE(16)) | Clock correction polynomial coefficient (sec/sec) (IS-QZSS [27]) | – | | +| >>af 0 | M | | BIT STRING (SIZE(22)) | Clock correction polynomial coefficient (seconds) (IS-QZSS [27]) | – | | +| >>T GD | M | | BIT STRING (SIZE(8)) | Group delay (seconds) (IS-QZSS [27]) | – | | +| >CNAV/CNAV-2 Clock Model | | | | Model-3 | – | | +| >>t oc | M | | BIT STRING (SIZE(11)) | Clock data reference time of week (seconds) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>t op | M | | BIT STRING (SIZE(11)) | Clock data predict time of week (seconds) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>URA oc Index | M | | BIT STRING (SIZE(5)) | SV clock accuracy index (dimensionless) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>URA oc1 Index | M | | BIT STRING (SIZE(3)) | SV clock accuracy change index (dimensionless) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>URA oc2 Index | M | | BIT STRING (SIZE(3)) | SV clock accuracy change rate index (dimensionless) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>a t2-n | M | | BIT STRING (SIZE(10)) | SV clock drift rate correction coefficient (sec/sec 2 ) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>a t1-n | M | | BIT STRING (SIZE(20)) | SV clock drift correction coefficient | – | | + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------------------------------------------------------------|-------------|----------------------| +| | | | | (sec/sec) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | | | + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| >>a 0-n | M | | BIT STRING (SIZE(26)) | SV clock bias correction coefficient (seconds) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>T GD | M | | BIT STRING (SIZE(13)) | Group delay correction (seconds) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>ISC L1CP | O | | BIT STRING (SIZE(13)) | Inter signal group delay correction (seconds) (IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>ISC L1CD | O | | BIT STRING (SIZE(13)) | Inter signal group delay correction (seconds) (IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>ISC L1CA | O | | BIT STRING (SIZE(13)) | Inter signal group delay correction (seconds) (IS-GPS-200 [23], IS-GPS-705 [24], IS-QZSS [27]) | – | | +| >>ISC L2C | O | | BIT STRING (SIZE(13)) | Inter signal group delay correction (seconds) (IS-GPS-200 [23], IS-GPS-705 [24], IS-QZSS [27]) | – | | +| >>ISC L5I5 | O | | BIT STRING (SIZE(13)) | Inter signal group delay correction (seconds) (IS-GPS-705 [24], IS-QZSS [27]) | – | | +| >>ISC L5Q5 | O | | BIT STRING (SIZE(13)) | Inter signal group delay correction (seconds) (IS-GPS-705 [24], IS-QZSS [27]) | – | | +| >GLONASS Satellite Clock Model | | | | Model-4 | – | | +| >>τ n (t b ) | M | | BIT STRING (SIZE(22)) | Satellite clock offset (seconds) [28] | – | | +| >>γ n (t b ) | M | | BIT STRING (SIZE(11)) | Relative frequency offset from nominal value (dimensionless) [28] | – | | +| >>Δτ n | O | | BIT STRING (SIZE(5)) | Time difference between transmission in G2 and G1 (seconds) [28] | – | | +| >SBAS Satellite Clock Model | | | | Model-5 | – | | +| >>t 0 | M | | BIT STRING (SIZE(13)) | (seconds) (DTFA01-96-C-00025 [26]) | – | | +| >>a Gf0 | M | | BIT STRING (SIZE(12)) | (seconds) (DTFA01-96-C-00025 [26]) | – | | +| >>a Gf1 | M | | BIT STRING (SIZE(8)) | (sec/sec) (DTFA01-96-C-00025 [26]) | – | | +| >BDS Satellite Clock Model | | | | Model-6 | YES | ignore | + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|------------------------------------------------------------------------------------|-------------|----------------------| +| >>Toc | M | | BIT STRING (SIZE(17)) | Time of clock (seconds) (BDS-SIS-ICD [33]) | – | | +| >>a0 | M | | BIT STRING (SIZE(24)) | Clock correction polynomial coefficient (seconds) (BDS-SIS-ICD [33]). | – | | +| >>a1 | M | | BIT STRING (SIZE(22)) | Clock correction polynomial coefficient (sec/sec) (BDS-SIS-ICD [33]). | – | | +| >>a2 | M | | BIT STRING (SIZE(11)) | Clock correction polynomial coefficient (sec/sec 2 ) (BDS-SIS-ICD [33]) | – | | +| >>TGD1 | M | | BIT STRING (SIZE(10)) | Equipment Group Delay Differential (seconds) (BDS-SIS-ICD [33]) | – | | +| >>AODC | M | | BIT STRING (SIZE(5)) | Age of Data, Clock (dimensionless) (BDS-SIS-ICD [33]) | – | | + +### 9.2.2.116 GANSS Ionospheric Model + +The IE contains fields needed to model the propagation delays of the GANSS signals through the ionosphere. + +Table 170 + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|----------------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------| +| a 10 | M | | BIT STRING (SIZE(11)) | Effective Ionisation Level 1 st order parameter. This parameter is used as defined in OS SIS ICD [22] | +| a 11 | M | | BIT STRING (SIZE(11)) | Effective Ionisation Level 2 nd order parameter. This parameter is used as defined in OS SIS ICD [22] | +| a 12 | M | | BIT STRING (SIZE(14)) | Effective Ionisation Level 3 rd order parameter. This parameter is used as defined in OS SIS ICD [22] | +| GANSS Ionosphere Regional Storm Flags | | 0..1 | | | +| >Storm Flag 1 | M | | BOOLEAN | This parameter is used as defined in OS SIS ICD [22] | +| >Storm Flag 2 | M | | BOOLEAN | This parameter is used as defined in OS SIS ICD [22] | +| >Storm Flag 3 | M | | BOOLEAN | This parameter is used as defined in OS SIS ICD [22] | +| >Storm Flag 4 | M | | BOOLEAN | This parameter is used as defined in OS SIS ICD [22] | +| >Storm Flag 5 | M | | BOOLEAN | This parameter is used as defined in OS SIS ICD [22] | + +### 9.2.2.116A GANSS Additional Ionospheric Model + +The IE contains fields needed to model the propagation delays of the GANSS signals through the ionosphere. + +**Table 170A** + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------------------------------| +| Data ID | M | | BIT STRING (SIZE(2)) | Coded as defined in TS 25.331 [4] | +| $\alpha_0$ | M | | BIT STRING (SIZE(8)) | seconds (IS-QZSS [27]) | +| $\alpha_1$ | M | | BIT STRING (SIZE(8)) | sec/semi-circle (IS-QZSS [27]) | +| $\alpha_2$ | M | | BIT STRING (SIZE(8)) | sec/(semi-circle) 2 (IS-QZSS [27]) | +| $\alpha_3$ | M | | BIT STRING (SIZE(8)) | sec/(semi-circle) 3 (IS-QZSS [27]) | +| $\beta_0$ | M | | BIT STRING (SIZE(8)) | seconds (IS-QZSS [27]) | +| $\beta_1$ | M | | BIT STRING (SIZE(8)) | sec/semi-circle (IS-QZSS [27]) | +| $\beta_2$ | M | | BIT STRING (SIZE(8)) | sec/(semi-circle) 2 (IS-QZSS [27]) | +| $\beta_3$ | M | | BIT STRING (SIZE(8)) | sec/(semi-circle) 3 (IS-QZSS [27]) | + +### 9.2.2.117 GANSS Measured Results + +**Table 171** + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------|----------|-------|-------------------------------------------|-----------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE Reference Time | M | | | | – | | +| >UTRAN Reference Time | | | | This choice may only be present if SAS operates in SAS-centric mode. | – | | +| >>UE GANSS Timing of Cell Frames | M | | INTEGER(0..86399999999750 by step of 250) | GANSS Time of Day (TOD) in ns | – | | +| >>GANSS Time ID | O | | GANSS ID 9.2.2.130 | Absence of this IE means Galileo system time. The value '0' ('SBAS') shall not be used for GANS Time ID. | – | | +| >>GANSS TOD Uncertainty | O | | INTEGER(0..127) | Provides the accuracy of the relation between GANSS TOD and UTRAN time. Its coding is defined in TS 25.331 [4]. | – | | +| >>UC-ID | M | | UTRAN Cell Identifier 9.2.2.37 | Identifies the reference cell for the GANSS TOD-SFN relationship. | – | | +| >>Reference SFN | M | | INTEGER(0..4095) | The SFN for which the location is valid. | – | | + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------------|----------|------------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | | This IE indicates the SFN at which the UE timing of cell frames is captured. | | | +| >GANSS Reference Time Only | | | | | – | | +| >>GANSS TOD msec | M | | INTEGER(0..3599999) | GANSS Time of Day (modulo 1 hour) in milliseconds (rounded down to the nearest millisecond unit). | – | | +| >>GANSS Time ID | O | | GANSS ID 9.2.2.130 | Absence of this IE means Galileo system time. The value '0' ('SBAS') shall not be used for GANSS Time ID. | – | | +| >>GANSS TOD Uncertainty | O | | INTEGER(0..127) | Provides the accuracy of the GANSS TOD. Its coding is defined in TS 25.331 [4]. | – | | +| GANSS Generic Measurement Information | | 1.. | | | – | | +| >GANSS ID | O | | 9.2.2.130 | Absence of this IE means Galileo. | – | | +| >GANSS Signal Measurement Information | M | 1.. | | | – | | +| >>GANSS Signal ID | O | | 9.2.2.131 | Absence of this field means the default value for the GANSS identified by "GANSS ID" TS 25.331 [4]. | – | | +| >>GANSS Code Phase Ambiguity | O | | INTEGER(0..31) | In milliseconds. Defined in TS 25.331 [4]. | – | | +| >>GANSS Code Phase Ambiguity Extension | O | | 9.2.2.141 | | YES | ignore | +| >>GANSS Measurement Parameters | M | 1.. | | | – | | +| >>>Sat ID | M | | INTEGER(0..63) | Defined in TS 25.331 [4]. | – | | +| >>>C/N 0 | M | | INTEGER(0..63) | the estimate of the carrier-to-noise ratio of the received signal from the particular satellite used in the measurement. It is given in units of dB-Hz (typical levels will be in the range of 20 – 50 dB-Hz). | – | | + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------|----------|-------|-----------------------------------|---------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| >>>Multipath Indicator | M | | ENUMERATED(NM, low, medium, high) | Coding as in 9.2.2.12 | – | | +| >>>Carrier Quality Indication | O | | BIT STRING (SIZE(2)) | Coded as defined in TS 25.331 [4]. | – | | +| >>>GANSS Code Phase | M | | INTEGER(0..2 21 -1) | Defined in TS 25.331 [4]. | – | | +| >>>GANSS Integer Code Phase | O | | INTEGER(0..63) | Defined in TS 25.331 [4]. | – | | +| >>>GANSS Integer Code Phase Extension | O | | 9.2.2.142 | | YES | ignore | +| >>>Code Phase RMS Error | M | | INTEGER (0..63) | Coding as Pseudorange RMS Error in section 9.2.2.12 | – | | +| >>>Doppler | M | | INTEGER(-3 2768..32767 ) | m/s, scale factor 0.04. Doppler measured by the UE for the particular satellite signal | – | | +| >>>ADR | O | | INTEGER(0..33554431) | Meters, scale factor 2 -10 ADR measurement measured by the UE for the particular satellite signal. | – | | + +Table 171A + +| Range bound | Explanation | +|-------------|----------------------------------------------------------------------------------------------------| +| maxGANSS | Maximum number of GANSS. The value of maxGANSS is 8. | +| maxSgnType | Maximum number of signals for which data is included in this IE. The value of maxSgnType is 8. | +| maxGANSSSat | Maximum number of satellites for which data is included in this IE. The value of maxGANSSSat is 64 | + +## 9.2.2.118 GANSS Navigation Model + +This IE contains information required to manage the transfer of precise navigation data to the GANSS-capable UE. + +Table 172 + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|------------------------------|----------|------------------|-----------------------|---------------------------------------------------------------------------------------------------| +| Non-Broadcast Indication | O | | ENUMERATED(true) | If this IE is present, GANSS navigation model is not derived from satellite broadcast. See NOTE 1 | +| Satellite Information | | 1.. | | | +| >Sat ID | M | | INTEGER(0..63) | Defined in TS 25.331 [4] | +| >SV Health | M | | BIT STRING (SIZE(9)) | Coded as defined in TS 25.331 [4]. | +| >IOD | M | | BIT STRING (SIZE(10)) | | +| >GANSS Clock Model | M | | GANSS clock model | | + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|--------------------|----------|-------|--------------------------------|-----------------------| +| | | | 9.2.2.115 | | +| >GANSS Orbit Model | M | | GANSS orbit model
9.2.2.119 | | + +Table 172A + +| Range bound | Explanation | +|-------------|-------------------------------------------------------------------------------------------------------| +| maxGANSSSat | Maximum number of satellites for which data is included in this IE.
The value of maxGANSSSat is 64 | + +NOTE 1: The Non-Broadcast Indication allows to inform that the navigation model is not bit-to-bit the one broadcast by the satellite. If it is set to 1, the UE is informed that techniques such as data wiping off applied to the navigation model may not work for instance. + +## 9.2.2.118A GANSS Additional Navigation Models + +This IE contains information required to manage the transfer of precise navigation data to the GANSS-capable UE. + +Table 172B + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|--------------------------------|----------|------------------|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------| +| Non-Broadcast Indication | O | | ENUMERATED(true) | If this IE is present, GANSS navigation model is not derived from satellite broadcast. See NOTE 1 in 9.2.2.118. | +| Satellite Information | | 1.. | | | +| >Sat ID | M | | INTEGER(0..63) | Defined in TS 25.331 [4]. | +| >SV Health | M | | BIT STRING (SIZE(6)) | Coded as defined in TS 25.331 [4]. | +| >IOD | M | | BIT STRING (SIZE(11)) | Coded as defined in TS 25.331 [4]. | +| >GANSS Additional Clock Models | M | | GANSS additional clock models
9.2.2.115A | | +| >GANSS Additional Orbit Models | M | | GANSS additional orbit models
9.2.2.119A | | + +Table 172C + +| Range bound | Explanation | +|-------------|-------------------------------------------------------------------------------------------------------| +| maxGANSSSat | Maximum number of satellites for which data is included in this IE.
The value of maxGANSSSat is 64 | + +## 9.2.2.119 GANSS Orbit Model + +This IE contains information for GANSS orbit model parameters. + +Table 173 + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|---------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------| +| CHOICE Orbit Model | M | | | | +| >Keplerian Parameters | | | | Model-1 | +| >>t oe | M | | BIT STRING (SIZE(14)) | Time-of-Ephemeris in seconds, scale factor 60 (OS SIS ICD [22]) | +| >>ω | M | | BIT STRING (SIZE(32)) | Argument of Perigee (semi-circles) (OS SIS ICD [22]) | +| >>Δn | M | | BIT STRING (SIZE(16)) | Mean Motion Difference From Computed Value (semi-circles/sec) (OS SIS ICD [22]) | +| >>M 0 | M | | BIT STRING (SIZE(32)) | Mean Anomaly at Reference Time (semi-circles) (OS SIS ICD [22]) | +| >>OMEGA dot | M | | BIT STRING (SIZE(24)) | Rate of change of right ascension (semi-circles/sec) (OS SIS ICD [22]) | +| >>e | M | | BIT STRING (SIZE(32)) | Eccentricity, scale factor 2 -33 (OS SIS ICD [22]) | +| >>Idot | M | | BIT STRING (SIZE(14)) | Rate of change of Inclination Angle (semi-circles/sec) (OS SIS ICD [22]) | +| >>sqrtA | M | | BIT STRING (SIZE(32)) | Square root of Semi-Major Axis in (meters) 1/2 , scale factor 2 -19 (OS SIS ICD [22]) | +| >>i 0 | M | | BIT STRING (SIZE(32)) | Inclination Angle at Reference Time (semi-circles) (OS SIS ICD [22]) | +| >>OMEGA 0 | M | | BIT STRING (SIZE(32)) | Longitude of Ascending Node of Orbit Plane at Weekly Epoch (semi-circles) (OS SIS ICD [22]) | +| >>C rs | M | | BIT STRING (SIZE(16)) | Amplitude of the Sine Harmonic Correction Term to the Orbit Radius (meters) (OS SIS ICD [22]) | +| >>C is | M | | BIT STRING (SIZE(16)) | Amplitude of the Sine Harmonic Correction Term To The Angle Of Inclination (radians) (OS SIS ICD [22]) | +| >>C us | M | | BIT STRING (SIZE(16)) | Amplitude of the Sine Harmonic Correction Term To The Argument Of Latitude (radians) (OS SIS ICD [22]) | +| >>C rc | M | | BIT STRING (SIZE(16)) | Amplitude of the Cosine Harmonic Correction Term to the Orbit Radius (meters) (OS SIS ICD [22]) | +| >>C ic | M | | BIT STRING (SIZE(16)) | Amplitude of the Cosine Harmonic Correction Term To The Angle Of Inclination (radians) (OS SIS ICD [22]) | +| >>C uc | M | | BIT STRING (SIZE(16)) | Amplitude of the Cosine Harmonic Correction Term To The Argument Of Latitude (radians) (OS SIS ICD [22]) | + +### 9.2.2.119A GANSS Additional Orbit Models + +This IE contains information for GANSS orbit model parameters. + +Table 173A + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE Additional Orbit Models | | | | | – | | +| >NAV-Keplerian Parameters | | | | Model-2 | – | | +| >>URA Index | M | | BIT STRING (SIZE(4)) | SV accuracy (dimensionless) (IS-QZSS [27]) | – | | +| >>Fit Interval Flag | M | | BIT STRING (SIZE(1)) | Fit interval indication (dimensionless) (IS-QZSS [27]) | – | | +| >>t oe | M | | BIT STRING (SIZE(16)) | Time of ephemeris (seconds) (IS-QZSS [27]) | – | | +| >>ω | M | | BIT STRING (SIZE(32)) | Argument of perigee (semi-circles) (IS-QZSS [27]) | – | | +| >>Δn | M | | BIT STRING (SIZE(16)) | Mean motion difference from computed value (semi-circles/sec) (IS-QZSS [27]) | – | | +| >>M 0 | M | | BIT STRING (SIZE(32)) | Mean anomaly at reference time (semi-circles) (IS-QZSS [27]) | – | | +| >>OMEGA dot | M | | BIT STRING (SIZE(24)) | Rate of right ascension (semi-circles/sec) (IS-QZSS [27]) | – | | +| >>e | M | | BIT STRING (SIZE(32)) | Eccentricity (dimensionless) (IS-QZSS [27]) | – | | +| >>Idot | M | | BIT STRING (SIZE(14)) | Rate of inclination angle (semi-circles/sec) (IS-QZSS [27]) | – | | +| >>sqrtA | M | | BIT STRING (SIZE(32)) | Square root of semi-major axis (meters 1/2 ) (IS-QZSS [27]) | – | | +| >>i 0 | M | | BIT STRING (SIZE(32)) | Inclination angle at reference time (semi-circles) (IS-QZSS [27]) | – | | +| >>OMEGA 0 | M | | BIT STRING (SIZE(32)) | Longitude of ascending node of orbit plane at weekly epoch (semi-circles) (IS-QZSS [27]) | – | | +| >>C rs | M | | BIT STRING (SIZE(16)) | Amplitude of sine harmonic correction term to the orbit radius (meters) (IS-QZSS [27]) | – | | +| >>C is | M | | BIT STRING (SIZE(16)) | Amplitude of sine harmonic correction term to the angle of inclination (radians) (IS-QZSS [27]) | – | | +| >>C us | M | | BIT STRING (SIZE(16)) | Amplitude of sine harmonic correction term to the argument of latitude (radians) (IS-QZSS [27]) | – | | +| >>C rc | M | | BIT STRING (SIZE(16)) | Amplitude of cosine harmonic correction term to the orbit radius (meters) (IS-QZSS [27]) | – | | + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|-------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------|-------------|----------------------| +| >>C ic | M | | BIT STRING (SIZE(16)) | Amplitude of cosine harmonic correction term to the angle of inclination (radians) (IS-QZSS [27]) | – | | +| >>C uc | M | | BIT STRING (SIZE(16)) | Amplitude of cosine harmonic correction term to the argument of latitude (radians) (IS-QZSS [27]) | – | | + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|-----------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| >CNAV/CNAV-2 Keplerian Parameters | | | | Model-3 | – | | +| >>t op | M | | BIT STRING (SIZE(11)) | Data predict time of week (seconds) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>URA oe Index | M | | BIT STRING (SIZE(5)) | SV accuracy (dimensionless) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>ΔA | M | | BIT STRING (SIZE(26)) | Semi-major axis difference at reference time (meters) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>A dot | M | | BIT STRING (SIZE(25)) | Chane rate in semi-major axis (meters/sec) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>Δn 0 | M | | BIT STRING (SIZE(17)) | Mean motion difference from computed value at reference time (semi-circles/sec) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>Δn 0 _dot | M | | BIT STRING (SIZE(23)) | Rate of mean motion difference from computed value (semi-circles/sec 2 ) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>M 0-n | M | | BIT STRING (SIZE(33)) | Mean anomaly at reference time (semi-circles) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>e n | M | | BIT STRING (SIZE(33)) | Eccentricity (dimensionless) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>ω n | M | | BIT STRING (SIZE(33)) | Argument of perigee (semi-circles) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| >>Ω 0-n | M | | BIT STRING (SIZE(33)) | Reference right ascension angle (semi-circles) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>ΔΩ _dot | M | | BIT STRING (SIZE(17)) | Rate of right ascension difference (semi-circles/sec) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>i 0-n | M | | BIT STRING (SIZE(33)) | Inclination angle at reference time (semi-circles) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>i 0-n_dot | M | | BIT STRING (SIZE(15)) | Rate of inclination angle (semi-circles/sec) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>C is-n | M | | BIT STRING (SIZE(16)) | Amplitude of sine harmonic correction term to the angle of inclination (radians) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>C ic-n | M | | BIT STRING (SIZE(16)) | Amplitude of cosine harmonic correction term to the angle of inclination (radians) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>C rs-n | M | | BIT STRING (SIZE(24)) | Amplitude of sine harmonic correction term to the orbit radius (meters) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>C rc-n | M | | BIT STRING (SIZE(24)) | Amplitude of cosine harmonic correction term to the orbit radius (meters) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>C us-n | M | | BIT STRING (SIZE(21)) | Amplitude of sine harmonic correction term to the argument of latitude (radians) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------------------|--------------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| >>C uc-n | M | | BIT STRING (SIZE(21)) | Amplitude of cosine harmonic correction term to the argument of latitude (radians) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >GLONASS Earth-Centered, Earth-fixed Parameters | | | | Model-4 | – | | +| >>E n | M | | BIT STRING (SIZE(5)) | Age of data (days) [28] | – | | +| >>P1 | M | | BIT STRING (SIZE(2)) | Time interval between two adjacent values of t b (minutes) [28] | – | | +| >>P2 | M | | BIT STRING (SIZE(1)) | Change of t b flag (dimensionless) [28] | – | | +| >>M | O | | BIT STRING (SIZE(2)) | Type of satellite (dimensionless) [28] | – | | +| >> | M | | BIT STRING (SIZE(27)) | x-coordinate of satellite at time t b (kilometers) [28] | – | | +| >> | M | | BIT STRING (SIZE(24)) | x-coordinate of satellite velocity at time t b (kilometers/sec) [28] | – | | +| >> | M | | BIT STRING (SIZE(5)) | x-coordinate of satellite acceleration at time t b (kilometers/sec 2 ) [28] | – | | +| >> | M | | BIT STRING (SIZE(27)) | y-coordinate of satellite at time t b (kilometers) [28] | – | | +| >> | M | | BIT STRING (SIZE(24)) | y-coordinate of satellite velocity at time t b (kilometers/sec) [28] | – | | +| >> | M | | BIT STRING (SIZE(5)) | y-coordinate of satellite acceleration at time t b (kilometers/sec 2 ) [28] | – | | +| >> | M | | BIT STRING (SIZE(27)) | z-coordinate of satellite at time t b (kilometers) [28] | – | | +| >> | M | | BIT STRING (SIZE(24)) | z-coordinate of satellite velocity at time t b (kilometers/sec) [28] | – | | +| >> | M | | BIT STRING (SIZE(5)) | z-coordinate of satellite acceleration at time t b (kilometers/sec 2 ) [28] | – | | +| >SBAS Earth-Centered, Earth-fixed Parameters | | | | Model-5 | – | | +| >>t 0 | C-ClockModel | | BIT STRING (SIZE(13)) | Time of applicability (seconds) (DTFA01-96-C-00025 [26]) | – | | +| >>Accuracy | M | | BIT STRING (SIZE(4)) | (dimensionless) (DTFA01-96-C-00025 [26]) | – | | +| >>X G | M | | BIT STRING (SIZE(30)) | (meters) (DTFA01-96-C-00025 [26]) | – | | +| >>Y G | M | | BIT STRING (SIZE(30)) | (meters) (DTFA01-96-C-00025 [26]) | – | | +| >>Z G | M | | BIT STRING (SIZE(25)) | (meters) (DTFA01-96-C-00025 [26]) | – | | +| >>X G Rate-of-Change | M | | BIT STRING (SIZE(17)) | (meters/sec) (DTFA01-96-C-00025 [26]) | – | | +| >>Y G Rate-of-Change | M | | BIT STRING (SIZE(17)) | (meters/sec) (DTFA01-96-C-00025 [26]) | – | | +| >>Z G Rate-of-Change | M | | BIT STRING (SIZE(18)) | (meters/sec) (DTFA01-96-C-00025 [26]) | – | | + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| >>X G Acceleration | M | | BIT STRING (SIZE(10)) | (meters/sec 2 ) (DTFA01-96-C-00025 [26]) | – | | +| >>Y G Acceleration | M | | BIT STRING (SIZE(10)) | meters/sec 2 ) (DTFA01-96-C-00025 [26]) | – | | +| >>Z G Acceleration | M | | BIT STRING (SIZE(10)) | meters/sec 2 ) (DTFA01-96-C-00025 [26]) | – | | +| >BDS Keplerian Parameters | | | | Model-6 | YES | ignore | +| >>URA Index | M | | BIT STRING (SIZE(4)) | SV accuracy (dimensionless) (BDS-SIS-ICD [33]) | – | | +| >>t oe | M | | BIT STRING (SIZE(17)) | Ephemeris reference time (seconds) (BDS-SIS-ICD [33]) | – | | +| >>A 1/2 | M | | BIT STRING (SIZE(32)) | Square root of semi-major axis (meters 1/2 ) (BDS-SIS-ICD [33]) | – | | +| >>e | M | | BIT STRING (SIZE(32)) | Eccentricity (dimensionless) (BDS-SIS-ICD [33]) | – | | +| >>ω | M | | BIT STRING (SIZE(32)) | Argument of perigee (semi-circles) (BDS-SIS-ICD [33]) | – | | +| >>Δn | M | | BIT STRING (SIZE(16)) | Mean motion difference from computed value (semi-circles/sec) (BDS-SIS-ICD [33]) | – | | +| >>M 0 | M | | BIT STRING (SIZE(32)) | Mean anomaly at reference time (semi-circles) (BDS-SIS-ICD [33]) | – | | +| >>Ω 0 | M | | BIT STRING (SIZE(32)) | Longitude of ascending node of orbital plane computed according to reference time (semi-circles) (BDS-SIS-ICD [33]) | – | | +| >>Ω dot | M | | BIT STRING (SIZE(24)) | Rate of right ascension (semi-circles/sec) (BDS-SIS-ICD [33]) | – | | +| >>i 0 | M | | BIT STRING (SIZE(32)) | Inclination angle at reference time (semi-circles) (BDS-SIS-ICD [33]) | – | | +| >>Idot | M | | BIT STRING (SIZE(14)) | Rate of inclination angle (semi-circles/sec) (BDS-SIS-ICD [33]) | – | | +| >>C uc | M | | BIT STRING (SIZE(18)) | Amplitude of cosine harmonic correction term to the argument of latitude (radians) (BDS-SIS-ICD [33]) | – | | +| >>C us | M | | BIT STRING (SIZE(18)) | Amplitude of sine harmonic correction term to the argument of latitude (radians) (BDS-SIS-ICD [33]) | – | | +| >>C rc | M | | BIT STRING (SIZE(18)) | Amplitude of cosine harmonic correction term to the orbit radius (meters) (BDS-SIS-ICD [33]) | – | | + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|-------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------|-------------|----------------------| +| >>C rs | M | | BIT STRING (SIZE(18)) | Amplitude of sine harmonic correction term to the orbit radius (meters) (BDS-SIS-ICD [33]) | – | | +| >>C ic | M | | BIT STRING (SIZE(18)) | Amplitude of cosine harmonic correction term to the angle of inclination (radians) (BDS-SIS-ICD [33]) | – | | +| >>C is | M | | BIT STRING (SIZE(18)) | Amplitude of sine harmonic correction term to the angle of inclination (radians) (BDS-SIS-ICD [33]) | – | | +| >>AODE | M | | BIT STRING (SIZE(5)) | Age of Data ephemeris (dimensionless) (BDS-SIS-ICD [33]) | – | | + +Table 173B + +| Condition | Explanation | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ClockModel | This IE shall be present if “SBAS Satellite Clock Model” (Model-5) in IE GANSS Additional Clock Models is not included in GANSS Additional Navigation Models IE. | + +### 9.2.2.120 GANSS Positioning Instructions + +This information element contains positioning instructions for GANSS positioning method in SAS-centric mode. + +Table 174 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------------------------------------|----------|-------|---------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Horizontal Accuracy Code | O | | 9.2.2.38 | | – | | +| Vertical Accuracy Code | O | | 9.2.2.39 | | – | | +| GANSS Timing of Cell Wanted | M | | BIT STRING (SIZE(8)) | For each bit, if set to '1', indicates that for respective GANSS the GANSS Timing of Cell is wanted.
Bit 1 is the MSB and bit 8 is the LSB (see clause 9.2.1).
bit 1: Galileo
bit 2: Modernized GPS
bit 3: QZSS
bit 4: GLONASS
bit 5: BDS

bits 6-8: reserved for future GANSS. | – | | +| Additional Assistance Data Request | M | | BIT STRING (SIZE(8)) | For each bit, if set to '1', indicates that the UE is requested to send an additional assistance data request for the respective GANSS.
Bit 1 is the MSB and bit 8 is the LSB (see clause 9.2.1).
bit 1: Galileo
bit 2: SBAS
bit 3: Modernized GPS
bit 4: QZSS
bit 5: GLONASS
bit 6: BDS

bits 7-8: reserved for future GANSS. | – | | +| Measurement Validity | O | | ENUMERATED ( CELL_DCH, all states except CELL_DCH, all states, ...) | | – | | +| GANSS Carrier-Phase Measurement Requested | O | | 9.2.2.143 | | YES | ignore | +| GANSS Multi-frequency Measurement Requested | O | | 9.2.2.144 | | YES | ignore | + +## 9.2.2.121 GANSS-UTRAN Time Relationship Uncertainty + +This IE contains the uncertainty of the GANSS and UTRAN time relationship. + +Table 175 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------|----------|-------|-----------------------------------------------------------------------|--------------------------------------------------------------| +| GANSS-UTRAN Time Relationship Uncertainty | M | | ENUMERATED (50ns, 500ns, 1us, 10us, 1ms, 10ms, 100ms, unreliable,...) | RNC estimate of uncertainty in GANSS-UTRAN time relationship | +| GANSS ID | O | | 9.2.2.130 | Absence of this IE means Galileo. | + +### 9.2.2.122 GANSS Real Time Integrity + +This IE contains parameters that describe the real-time status of the GANSS constellation. + +**Table 176** + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|------------------------------|----------|------------------|-----------------------|------------------------------------| +| Satellite Information | | 1.. | | | +| >Bad GANSS Sat ID | M | | INTEGER(0..63) | Defined in TS 25.331 [4]. | +| >Bad GANSS Signal ID | O | | BIT STRING (SIZE(8)) | Coded as defined in TS 25.331 [4]. | + +**Table 176A** + +| Range bound | Explanation | +|-------------|-------------------------------------------------------------------------------------------------------| +| maxGANSSSat | Maximum number of satellites for which data is included in this IE.
The value of maxGANSSSat is 64 | + +### 9.2.2.123 GANSS Reference Measurement Information + +This IE contains parameters that enable fast acquisition of the GANSS signals in UE-assisted GANSS positioning. + +**Table 177** + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|----------------------------------------|----------|------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| GANSS Signal ID | O | | 9.2.2.131 | Absence of this field means the default value for the GANSS identified by "GANSS ID" TS 25.331 [4]. | – | | +| Satellite Information | | 1.. | | | – | | +| >Sat ID | M | | INTEGER (0..63) | Defined in TS 25.331 [4]. | – | | +| >Doppler (0 th order term) | M | | INTEGER(-2048..2047) | Scaling factor 0.5 m/s Conversion between m/s and Hz shall be made by using the nominal wavelength of the assisted signal. | – | | +| >Extra Doppler | | 0..1 | | | – | | +| >>Doppler (1 st order term) | M | | INTEGER (-42..21) | Scaling factor 1/210 m/s 2 | – | | +| >>Doppler Uncertainty | M | | ENUMERATED (40,20,10,5, 2.5) | m/s. The Doppler experienced by a stationary UE is in the range "Doppler – Doppler Uncertainty" to "Doppler + Doppler Uncertainty". | – | | +| >Code Phase | M | | INTEGER(0..1023) | ms, scaling factor 2 -10 Nominal chipping rate of the GNSS signal shall be used in conversion. Increasing binary values of the field signify increasing predicted pseudoranges. | – | | +| >Integer Code Phase | M | | INTEGER(0..127) | ms. Integer code phase (expressed modulo 128 ms) currently being transmitted at the GANSS Reference Time, as seen by a receiver at the Reference Location | – | | +| >Code Phase Search Window | M | | INTEGER(0..31) | Expected code-phase is in the range "Code Phase – Code Phase Search Window" to "Code Phase + Code Phase Search Window". Coded as defined in TS 25.331 [4]. | – | | +| >Azimuth and Elevation | | 0..1 | | | – | | +| >>Azimuth | M | | INTEGER(0..31) | Scaling factor 11.25 Degrees. | – | | +| >>Elevation | M | | INTEGER(0..7) | Scaling factor 11.25 Degrees. | – | | +| >>Azimuth and Elevation LSB | | 0..1 | | | YES | ignore | +| >>>Azimuth LSB | M | | INTEGER(0..1) | The full satellite | – | | + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------|----------|-------|-------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| | | | .15) | azimuth is constructed as
“Azimuth” × 11.25 +
“Azimuth LSB” × 0.703125 degrees.

An angle of x degrees means the satellite azimuth a is in the range $x \leq a < x+0.703125$ degrees. | | | +| >>>Elevation LSB | M | | INTEGER(0..15) | The full satellite elevation is constructed as
“Elevation” × 11.25 +
“Elevation LSB” × 0.703125 degrees.

An angle of y degrees means the satellite elevation e is in the range $y \leq e < y+0.703125$ degrees. | – | | +| >Extra Doppler Extension | | 0..1 | | If this field is present, the "Extra Doppler" field should not be present. | YES | ignore | +| >>Doppler (1st order term) | M | | INTEGER (-42..21) | Scaling factor 1/210 m/s 2 | – | | +| >>Doppler Uncertainty Extension | M | | ENUMERATED (60, 80, 100, 120, ‘No Information’) | m/s.
The Doppler experienced by a stationary UE is in the range “Doppler – Doppler Uncertainty Extension” to “Doppler + Doppler Uncertainty Extension”. | – | | +| Confidence | O | | INTEGER (0..100) | Confidence level (in percent) of the reference location area or volume used to calculate the Satellite information parameters (search windows). | YES | ignore | + +Table 177A + +| Range bound | Explanation | +|-------------|-------------------------------------------------------------------------------------------------------| +| maxGANSSSat | Maximum number of satellites for which data is included in this IE.
The value of maxGANSSSat is 64 | + +## 9.2.2.124 GANSS Reference Time + +Table 178 + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------|-----------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| GANSS Day | O | | INTEGER(0..8191) | The number of days from the beginning of GNSS system time (mod 8192) | – | | +| GANSS TOD | M | | INTEGER(0..86399) | GANSS Time of Day in seconds | – | | +| GANSS TOD Uncertainty | O | | INTEGER(0..127) | Provides the accuracy of the relation between GANSS TOD and UTRAN time if UTRAN GANSS timing of cell frames is provided. Its coding is defined in TS 25.331 [4].

This IE may only be present if SAS operates in SAS-centric mode. | – | | +| GANSS Time ID | O | | GANSS ID 9.2.2.130 | Absence of this IE means Galileo system time. The value '0' ('SBAS') shall not be used for GANSS Time ID. | – | | +| UTRAN GANSS Reference Time | | 0..1 | | This IE may only be present if SAS operates in SAS-centric mode. | – | | +| >UTRAN GANSS Timing of Cell Frames | M | | INTEGER(0..999999750 by step of 250) | UTRAN GANSS timing of cell frames in steps of 250 ns. Indicates sub-second part of GANSS TOD IE . See TS 25.331 [4]. | – | | +| >UC-ID | O | | UTRAN Cell Identifier 9.2.2.37 | Identifies the reference cell for the GANSS TOD-SFN relationship. | – | | +| >SFN | M | | Integer(0..4095) | The SFN which the UTRAN GANSS timing of cell frames time stamps. | – | | +| T UTRAN-GANSS Drift Rate | O | | ENUMERATED (0, 1, 2, 5, 10, 15, 25, 50, -1, -2, -5, -10, -15, -25, -50,...) | in 1/256 chips per sec. | – | | +| GANSS Day Cycle Number | O | | INTEGER (0..7) | Number of 8192 day cycles occurred since the GANSS zero time-point defined in TS 25.331 [4]. The first 8192 GANSS days since the zero time-point is GANSS Day Cycle Number 0. | YES | ignore | + +### 9.2.2.125 GANSS Time Model + +The *GANSS Time Model* IE contains a set of parameters needed to relate GANSS time to selected time reference indicated by GNSS\_TO\_ID. + +**Table 179** + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|---------------------------------|----------|-------|---------------------------------------------------|-----------------------------------------------------------------------------------------------|-------------|----------------------| +| GANSS Time Model Reference Time | M | | INTEGER (0..37799) | GANSS reference time (modulo 1 week) in seconds. Scale Factor 2 4 | – | | +| T A0 | M | | INTEGER(-2147483648..2147483647) | Seconds, scale factor 2 -35 | – | | +| T A1 | O | | INTEGER(-8388608..8388607) | sec/sec, scale factor 2 -51 | – | | +| T A2 | O | | INTEGER (-64..63) | sec/sec 2 , scale factor 2 -68 | – | | +| GNSS_TO_ID | M | | ENUMERATED(GPS, ..., Galileo, QZSS, GLONASS, BDS) | | – | | +| Week Number | O | | INTEGER (0..8191) | Reference week of GANSS Time Model | – | | +| Delta_T | O | | INTEGER (-128..127) | This field specifies the integer seconds of the GNSS-GNSS Time Offset. Scale factor 1 second. | YES | ignore | + +### 9.2.2.125A GANSS Additional Time Models + +The *GANSS Additional Time Models* IE contains a set of parameters needed to relate GANSS time to selected time references. + +**Table 179A** + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|-----------------------------|----------|-----------------|-----------------------|-----------------------| +| GNSS-GNSS Time Model | | 1.. | | | +| >GANSS Time Model | | | 9.2.2.125 | | + +**Table 179B** + +| Range Bound | Explanation | +|-------------|------------------------------------------------------------------------------------------------------| +| maxGANSS-1 | Maximum number of GANSS systems for which data is included in this IE. The value of maxGANSS-1 is 7. | + +### 9.2.2.126 GANSS UTC Model + +The *GANSS UTC Model* IE contains a set of parameters needed to relate GANSS time to Universal Time Coordinate (UTC). + +**Table 180** + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|----------------------|-----------------|--------------|------------------------------|------------------------------| +| $A_1$ | M | | BIT STRING (SIZE(24)) | sec/sec (OS SIS ICD [22]) | +| $A_0$ | M | | BIT STRING (SIZE(32)) | seconds (OS SIS ICD [22]) | +| $t_{ot}$ | M | | BIT STRING (SIZE(8)) | seconds (OS SIS ICD [22]) | +| $WN_t$ | M | | BIT STRING (SIZE(8)) | weeks (OS SIS ICD [22]) | +| $\Delta t_{LS}$ | M | | BIT STRING (SIZE(8)) | seconds (OS SIS ICD [22]) | +| $WN_{LSF}$ | M | | BIT STRING (SIZE(8)) | weeks (OS SIS ICD [22]) | +| DN | M | | BIT STRING (SIZE(8)) | days (OS SIS ICD [22]) | +| $\Delta t_{LSF}$ | M | | BIT STRING (SIZE(8)) | seconds (OS SIS ICD [22]) | + +### 9.2.2.126A GANSS Additional UTC Models + +The *GANSS Additional UTC Models* IE contains several sets of parameters needed to relate GANSS time to Universal Time Coordinate (UTC), as defined in [23,24,25,26,27,28,33]. + +**Table 180A** + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|-------------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| CHOICE Additional UTC Models | | | | | – | | +| >Model Set 1 | | | | | – | | +| >>A 0-n | M | | BIT STRING (SIZE(16)) | Bias coefficient of GNSS time scale relative to UTC time scale (seconds) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>A 1-n | M | | BIT STRING (SIZE(13)) | Drift coefficient of GNSS time scale relative to UTC time scale (sec/sec) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>A 2-n | M | | BIT STRING (SIZE(7)) | Drift rate correction coefficient of GNSS time scale relative to UTC time scale (sec/sec 2 ) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>Δt LS | M | | BIT STRING (SIZE(8)) | Current or past leap second count (seconds) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>t ot | M | | BIT STRING (SIZE(16)) | Time data reference time of week (seconds) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>WN ot | M | | BIT STRING (SIZE(13)) | Time data reference week number (weeks) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>WN LSF | M | | BIT STRING (SIZE(8)) | Leap second reference week number (weeks) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>DN | M | | BIT STRING (SIZE(4)) | Leap second reference day number (days) (IS-GPS-200 [23], IS-GPS-705 [24], IS-GPS-800 [25], IS-QZSS [27]) | – | | +| >>Δt LSF | M | | BIT STRING (SIZE(8)) | Current or future leap second count (seconds) (IS- | – | | + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|----------------------|-----------------|--------------|------------------------------|---------------------------------------------------------------------------|--------------------|-----------------------------| +| | | | | GPS-200 [23], IS-
GPS-705 [24], IS-
GPS-800 [25], IS-
QZSS [27]) | | | + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|---------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------|-------------|----------------------| +| >Model Set 2 | | | | | – | | +| >>N A | M | | BIT STRING (SIZE(11)) | Calendar day number within four-year period beginning since the leap year (days) [28] | – | | +| >>τ c | M | | BIT STRING (SIZE(32)) | GLONASS time scale correction to UTC(SU) (seconds) [28] | – | | +| >>Delta UT1 | O | | | | – | | +| >>>B1 | M | | BIT STRING (SIZE(11)) | Coefficient to determine ΔUT1 (seconds) [28] | – | | +| >>>B2 | M | | BIT STRING (SIZE(10)) | Coefficient to determine ΔUT1 (seconds/msd) [28] | – | | +| >>KP | O | | BIT STRING (SIZE(2)) | Notification of expected leap second correction (dimensionless) [28] | – | | +| >Model Set 3 | | | | | – | | +| >>A 1WNT | M | | BIT STRING (SIZE(24)) | sec/sec (DTFA01-96-C-00025 [26], Message Type 12) | – | | +| >>A 0WNT | M | | BIT STRING (SIZE(32)) | seconds (DTFA01-96-C-00025 [26], Message Type 12) | – | | +| >>t ot | M | | BIT STRING (SIZE(8)) | seconds (DTFA01-96-C-00025 [26], Message Type 12) | – | | +| >>WN t | M | | BIT STRING (SIZE(8)) | weeks (DTFA01-96-C-00025 [26], Message Type 12) | – | | +| >>Δt LS | M | | BIT STRING (SIZE(8)) | seconds (DTFA01-96-C-00025 [26], Message Type 12) | – | | +| >>WN LSF | M | | BIT STRING (SIZE(8)) | weeks (DTFA01-96-C-00025 [26], Message Type 12) | – | | +| >>DN | M | | BIT STRING (SIZE(8)) | days (DTFA01-96-C-00025 [26], Message Type 12) | – | | +| >>Δt LSF | M | | BIT STRING (SIZE(8)) | seconds (DTFA01-96-C-00025 [26], Message Type 12) | – | | +| >>UTC Standard ID | M | | BIT STRING (SIZE(3)) | dimensionless Coded as defined in TS 25.331 [4]. | – | | +| >Model Set 4 | | | | | YES | ignore | +| >>A 0UTC | M | | BIT STRING (SIZE(32)) | Seconds (BDS-SIS-ICD [33]) | – | | +| >>A 1UTC | M | | BIT STRING (SIZE(24)) | sec/sec (BDS-SIS-ICD [33]) | – | | +| >>Δt LS | M | | BIT STRING (SIZE(8)) | Seconds (BDS-SIS-ICD [33]) | – | | +| >>WN LSF | M | | BIT STRING | Weeks (BDS-SIS-ICD | – | | + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | Criticality | Assigned Criticality | +|---------------------|----------|-------|-----------------------|----------------------------|-------------|----------------------| +| | | | (SIZE(8)) | [33]) | | | +| >>DN | M | | BIT STRING (SIZE(8)) | Days (BDS-SIS-ICD [33]) | – | | +| >>Δt LSF | M | | BIT STRING (SIZE(8)) | Seconds (BDS-SIS-ICD [33]) | – | | + +### 9.2.2.127 GANSS Time Indicator + +Table 181 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------------|----------|-------|----------------------------------------|-----------------------| +| GANSS Time Indicator | | | ENUMERATE D (requested, not requested) | | + +### 9.2.2.127A GANSS Data Bit Assistance + +Table 181A + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------------|----------|------------------|----------------------------|---------------------------------------------------------------------------------------------------------------| +| GANSS TOD | M | | INTEGER(0..59,...) | Reference time (modulo 1 minute) of the first bit of the data in Data Bits IE, in seconds. | +| Data Bit Assistance List | | 1.. | | | +| >Sat ID | M | | INTEGER(0..63) | Defined in TS 25.331 [4]. | +| >Data Bit Assistance Sgn List | | 1.. | | | +| >>GANSS Signal ID | M | | 9.2.2.131 | | +| >>Data Bits | M | | BIT STRING (SIZE(1..1024)) | Raw data bits as transmitted from a specific satellite at the time indicated by GANSS_TOD. See TS 25.331 [4]. | + +Table 181B + +| Range bound | Explanation | +|-------------|----------------------------------------------------------------------------------------------------------| +| maxSgnType | Maximum number of signals for which data is included in this IE. The value of maxSgnType is 8. | +| maxGANSSSat | Maximum number of GANSS satellites for which data is included in the IE. The value of maxGANSSSat is 64. | + +### 9.2.2.128 Additional GPS Assistance Data Required + +This IE lists the GPS assistance data types required by the UE. + +**Table 182** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------------------------|----------|-------------|-----------------------|--------------------------------------------------------------------------------------------------------| +| Almanac | M | | BOOLEAN | TRUE means requested | +| UTC Model | M | | BOOLEAN | TRUE means requested | +| Ionospheric Model | M | | BOOLEAN | TRUE means requested | +| Navigation Model | M | | BOOLEAN | TRUE means requested | +| DGPS Corrections | M | | BOOLEAN | TRUE means requested | +| Reference Location | M | | BOOLEAN | TRUE means requested | +| Reference Time | M | | BOOLEAN | TRUE means requested | +| Acquisition Assistance | M | | BOOLEAN | TRUE means requested | +| Real-Time Integrity | M | | BOOLEAN | TRUE means requested | +| Nav. Model Additional Data | | 0..1 | | | +| >GPS Week | M | | INTEGER (0..1023) | GPS week number | +| >GPS_Toe | M | | INTEGER (0..167) | GPS time of ephemeris in hours of the latest ephemeris set | +| >T-Toe limit | M | | Integer (0..10) | ephemeris age tolerance in hours | +| > Satellites related data | | 0.. | | | +| >>SatID | M | | INTEGER (0..63) | Identifies the satellite and is equal to (SV ID No - 1) where SV ID No is defined in ICD-GPS-200 [10]. | +| >>IODE | M | | INTEGER (0..255) | Issue of Data Ephemeris for SatID | + +**Table 183** + +| Range Bound | Explanation | +|-------------|------------------------------------------------------------------------------------------------| +| maxSat | Maximum number of satellites for which data is included in this IE. The value of maxSat is 16. | + +### 9.2.2.129 Additional GANSS Assistance Data Required + +This IE lists the GANSS assistance data types required by the UE. + +**Table 184** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|------------------------------------------------|----------|---------------|-------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------| +| GANSS Reference Time | M | | BOOLEAN | TRUE means requested | – | | +| GANSS Reference Location | M | | BOOLEAN | TRUE means requested | – | | +| GANSS Ionospheric model | M | | BOOLEAN | TRUE means requested | – | | +| GANSS Additional Ionospheric Model | O | | GANSS Additional Ionospheric Model Required 9.2.2.145 | Presence means required. | YES | ignore | +| GANSS Earth Orientation Parameters | O | | GANSS Earth Orientation Parameters Required 9.2.2.146 | | YES | ignore | +| GANSS Requested Generic Assistance Data | | 1.. | | | – | | +| >GANSS ID | O | | 9.2.2.130 | Absence of this IE means Galileo | – | | +| >GANSS Real-Time Integrity | O | | BOOLEAN | TRUE means requested | – | | +| >GANSS Differential Corrections | | 0..1 | | | – | | +| >>DGANSS Signal | M | | BIT STRING (SIZE(8)) | Coded as defined in TS 25.331 [4]. | – | | +| >GANSS Almanac | O | | BOOLEAN | TRUE means requested | – | | +| >GANSS Navigation Model | O | | BOOLEAN | TRUE means requested | – | | +| >GANSS Time Model GNSS-GNSS | O | | BIT STRING (SIZE(9)) | Defines the time model.
Bit 1 is the MSB and bit 9 is the LSB (see clause 9.2.1).
Bit 1 is set for GPS,
Bit 2 is set for Galileo.
Bit 3 is set for QZSS
Bit 4 is set for GLONASS
Bit 5 is set for BDS.
Other bits are reserved. | – | | +| >GANSS Reference Measurement Information | O | | BOOLEAN | TRUE means requested | – | | +| >GANSS Data Bits | | 0..1 | | | – | | +| >>GANSS TOD | M | | INTEGER (0..86399) | The GANSS TOD for which the data bits are requested. | – | | +| >>Data Bit Assistance | | 1 | | | – | | +| >>>GANSS Signal ID | M | | BIT STRING (SIZE(8)) | Coded as defined in TS 25.331 [4]. | – | | +| >>>GANSS Data Bit | M | | INTEGER( | This field | – | | + +| | | | | | | | +|-----------------------------------------|---|------------------|-------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------| +| Interval | | | 0..15) | represents the time length for which the Data Bit Assistance is requested. The Data Bit Assistance shall be relative to the time interval (GANSS TOD, GANSS TOD + Data Bit Interval). The Data Bit Interval $r$ , expressed in seconds, is mapped to a binary number $K$ with the following formula:
$r = 0.1 * 2^K$ Value $K=15$ means that the time interval is not specified. | | | +| >>>Satellite Information | | 0.. | | | – | | +| >>>>Satellite ID | M | | INTEGER(0..63) | Defined in TS 25.331 [4]. | – | | +| >GANSS UTC model | O | | BOOLEAN | TRUE means requested | – | | +| >GANSS Navigation Model Additional data | | 0..1 | | | – | | +| >>GANSS Week/Day | M | | INTEGER(0..4095) | Defined in TS 25.331 [4]. | – | | +| >>GANSS_Toe | M | | INTEGER(0..167) | Defined in TS 25.331 [4]. | – | | +| >>T-Toe limit | M | | INTEGER(0..10) | Defined in TS 25.331 [4]. | – | | +| >>Satellites list related data | M | 0.. | | | – | | +| >>>Sat ID | M | | INTEGER(0..63) | Defined in TS 25.331 [4]. | – | | +| >>>IOD | M | | BIT STRING (SIZE(10)) | Defined in TS 25.331 [4]. | – | | +| >GANSS Additional Navigation Models | O | | GANSS Additional Navigation Models Required 9.2.2.147 | | YES | ignore | +| >GANSS Additional UTC Models | O | | GANSS Additional UTC Models Required 9.2.2.148 | | YES | ignore | +| >GANSS Auxiliary Information | O | | GANSS Auxiliary Information Required | | YES | ignore | + +| | | | | | | | +|-------------------------------------------|---|------|----------------------|---------------------------------------------------------------------------------|-----|--------| +| | | | 9.2.2.149 | | | | +| >SBAS ID | O | | 9.2.2.134 | | YES | ignore | +| >GANSS Additional Assistance Data Choices | O | | 9.2.2.151 | | YES | ignore | +| >BDS Ionospheric Grid Model | O | | BOOLEAN | This IE may be present if the GANSS ID IE indicates 'BDS'. TRUE means requested | YES | ignore | +| >DBDS Corrections | O | 0..1 | | This IE may be present if the GANSS ID IE indicates 'BDS'. | YES | ignore | +| >>DGANSS Signal | M | | BIT STRING (SIZE(8)) | Coded as defined in TS 25.331 [4] | | | + +**Table 185** + +| Range Bound | Explanation | +|-------------|-----------------------------------------------------------------------------------------------------------| +| maxGANSS | Maximum number of GANSS for which data is included in this IE. The value of maxGANSS is 8. | +| maxGANSSSat | Maximum number of GANSS satellites for which data is included in this IE. The value of maxGANSSSat is 64. | + +### 9.2.2.130 GANSS ID + +This IE defines a particular GANSS. + +**Table 186** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| GANSS ID | M | | INTEGER(0..7) | Defines the GANSS and is coded as defined in the UE positioning GANSS additional assistance data request IE in TS 25.331 [4]. | + +### 9.2.2.131 GANSS Signal ID + +This IE defines a specific signal within a particular GANSS. + +**Table 187** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-----------------|----------|-------|-------------------------|--------------------------------------------------------------------| +| GANSS Signal ID | M | | INTEGER (0..3,...,4..7) | Defines the GANSS signal and is coded as defined in TS 25.331 [4]. | + +### 9.2.2.131a GANSS Signal IDs + +This IE defines multiple signals within a particular GANSS. + +**Table 187A** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------|----------|-------|-----------------------|-------------------------------------------------------------| +| GANSS Signal IDs | M | | BIT STRING (SIZE(8)) | Each bit represents one signal as defined in TS 25.331 [4]. | + +**9.2.2.132 GPS Reference Time Uncertainty****Table 188** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GPS Reference Time Uncertainty | M | | INTEGER (0..127) | This element provides the accuracy of the provided GPS time, or alternatively the accuracy of the provided relation between GPS and UTRAN time. If "GPS TOW" is the provided GPS time, or alternatively the GPS time corresponding to the UTRAN time provided, then the true GPS time lies in the interval ["GPS TOW" - "GPS Reference Time Uncertainty", "GPS TOW" + "GPS Reference Time Uncertainty"].
The uncertainty r, expressed in microseconds, is mapped to a number K with the following formula:
$r = C * (((1+x)^K)-1)$
with C = 0.0022 and x = 0.18.
To encode any higher value of the uncertainty than that corresponding to K=127 in the formula above, or to indicate an undefined value of the "GPS TOW", the same value, K=127, shall be used. | + +**9.2.2.133 GANSS Earth Orientation Parameters****Table 189** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------| +| t EOP | M | | BIT STRING (SIZE(16)) | EOP data reference time (seconds) (IS-GPS-200 [23]) | +| PM_X | M | | BIT STRING (SIZE(21)) | X-axis polar motion value at reference time (arc-seconds) (IS-GPS-200 [23]) | +| PM_X_dot | M | | BIT STRING (SIZE(15)) | X-axis polar motion drift at reference time (arc-seconds/day) (IS-GPS-200 [23]) | +| PM_Y | M | | BIT STRING (SIZE(21)) | Y-axis polar motion value at reference time (arc-seconds) (IS-GPS-200 [23]) | +| PM_Y_dot | M | | BIT STRING (SIZE(15)) | Y-axis polar motion drift at reference time (arc-seconds/day) (IS-GPS-200 [23]) | +| ΔUT1 | M | | BIT STRING (SIZE(31)) | UT1-UTC difference at reference time (seconds) (IS-GPS-200 [23]) | +| ΔUT1_dot | M | | BIT STRING (SIZE(19)) | Rate of UT1-UTC difference at reference time (seconds/day) (IS-GPS-200 [23]) | + +### 9.2.2.134 SBAS ID + +This IE defines a specific SBAS. + +Table 190 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|---------------------------------------------------------|-----------------------| +| SBAS ID | M | | ENUMERATED(
WAAS,
EGNOS,
MSAS,
GAGAN, ... ) | | + +### 9.2.2.135 GANSS Auxiliary Information + +Table 191 + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|----------------------|----------|-----------------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------| +| CHOICE GANSS-ID | | | | | +| >GANSS-ID-1 | | | | This choice may only be present if GANSS ID indicated "Modernized GPS" | +| >>Aux Info List | | 1 ..
| | | +| >>>Sat ID | M | | INTEGER(0..63) | Defined in TS 25.331 [4]. | +| >>>Signals Available | M | | BIT STRING (SIZE(8)) | Coded as defined in TS 25.331 [4]. | +| >GANSS-ID-3 | | | | This choice may be present if GANSS ID indicated "GLONASS" | +| >>Aux Info List | | 1 ..
| | | +| >>>Sat ID | M | | INTEGER(0..63) | Defined in TS 25.331 [4]. | +| >>>Signals Available | M | | BIT STRING (SIZE(8)) | Coded as defined in TS 25.331 [4]. | +| >>>Channel Number | M | | INTEGER (-7..13) | This field indicates the GLONASS carrier frequency number of the satellite identified by Sat ID , as defined in [28]. | + +Table 192 + +| Range Bound | Explanation | +|-------------|-----------------------------------------------------------------------------------------------------------| +| maxGANSSSat | Maximum number of GANSS satellites for which data is included in this IE. The value of maxGANSSSat is 64. | + +## 9.2.2.136 UTRAN-GANSS Reference Time Result + +**Table 193** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------|----------|-------|--------------------------------|-----------------------------------------------------------------------------------------------------------| +| UE GANSS timing of cell frames | M | | INTEGER(0..34559 9999999,...) | GANSS Time of Day in steps of 250 ns TS 25.331 [4]. | +| GANSS time ID | O | | GANSS ID 9.2.2.130 | Absence of this IE means Galileo system time. The value '0' ('SBAS') shall not be used for GANSS Time ID. | +| GANSS TOD Uncertainty | O | | INTEGER(0..127) | Coded as defined in TS 25.331 [4]. | +| UC-ID | M | | UTRAN Cell Identifier 9.2.2.37 | Identifies the reference cell for the GANSS TOD-SFN relationship. | +| SFN | M | | INTEGER (0..4095) | This IE indicates the SFN at which the UE timing of cell frame is captured. | + +## 9.2.2.137 GANSS Additional Ionospheric Model Request + +**Table 194** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|-----------------------------------------------------------------------------| +| Data ID | M | | BIT STRING (SIZE(2)) | Data ID for GANSS Additional Ionospheric Model as defined in TS 25.331 [4]. | + +## 9.2.2.138 GANSS Earth Orientation Parameters Request + +**Table 195** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------------|----------|-------|--------------------------------------|-----------------------| +| GANSS Earth Orientation Parameters Request | M | | ENUMERATED(Requested, Not-Requested) | | + +## 9.2.2.139 Support for Non-Native Assistance Choices Indication + +**Table 196** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------------------------|----------|-------|-----------------------|-----------------------| +| Support for Non-Native Assistance Choices Indication | M | | BOOLEAN | TRUE means supported. | + +## 9.2.2.140 Position Data UE-Based + +Table 197 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Position Data UE-Based | M | | BIT STRING (SIZE(16)) | For each bit, if set to '1' indicates that respective GNSS or position system was used by the UE for position calculation.
Coded as defined in TS 25.331 [4]. | + +## 9.2.2.141 GANSS Code Phase Ambiguity Extension + +Table 198 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------|----------|-------|-----------------------|-----------------------------------------------| +| GANSS Code Phase Ambiguity Extension | M | | INTEGER(32..127) | In milliseconds.
Defined in TS 25.331 [4]. | + +## 9.2.2.142 GANSS Integer Code Phase Extension + +Table 199 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------------|----------|-------|-----------------------|-----------------------------------------------| +| GANSS Integer Code Phase Extension | M | | INTEGER(64..127) | In milliseconds.
Defined in TS 25.331 [4]. | + +## 9.2.2.143 GANSS Carrier-Phase Measurement Requested + +Table 200 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GANSS Carrier-Phase Measurement Requested | M | | BIT STRING (SIZE(8)) | For each bit, if set to '1', indicates that the UE is requested to report carrier phase measurements for the respective GANSS.
Bit 1 is the MSB and bit 8 is the LSB (see clause 9.2.1).
bit 1: Galileo
bit 2: SBAS
bit 3: Modernized GPS
bit 4: QZSS
bit 5: GLONASS
bit 6: BDS

bits 7-8: reserved for future GANSS. | + +### 9.2.2.144 GANSS Multi-frequency Measurement Requested + +**Table 201** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GANSS Multi-frequency Measurement Requested | M | | BIT STRING (SIZE(8)) | For each bit, if set to '1', indicates that the UE is requested to report measurements for multiple GANSS signals for the respective GANSS.
Bit 1 is the MSB and bit 8 is the LSB (see clause 9.2.1).
bit 1: Galileo
bit 2: SBAS
bit 3: Modernized GPS
bit 4: QZSS
bit 5: GLONASS
bit 6: BDS

bits 7-8: reserved for future GANSS. | + +### 9.2.2.145 GANSS Additional Ionospheric Model Required + +**Table 202** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| Data ID | M | | BIT STRING (SIZE(2)) | Data ID for GANSS Additional Ionospheric Model as defined in the UE positioning GANSS additional assistance data request IE of TS 25.331 [4]. | + +### 9.2.2.146 GANSS Earth Orientation Parameters Required + +**Table 203** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------------|----------|-------|-----------------------|-----------------------| +| GANSS Earth Orientation Parameters Required | M | | BOOLEAN | TRUE means required. | + +### 9.2.2.147 GANSS Additional Navigation Models Required + +**Table 204** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------------|----------|-------|-----------------------|-----------------------| +| GANSS Additional Navigation Models Required | M | | BOOLEAN | TRUE means required. | + +### 9.2.2.148 GANSS Additional UTC Models Required + +**Table 205** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------|----------|-------|-----------------------|-----------------------| +| GANSS Additional UTC Models Required | M | | BOOLEAN | TRUE means required. | + +### 9.2.2.149 GANSS Auxiliary Information Required + +Table 206 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------|----------|-------|-----------------------|-----------------------| +| GANSS Auxiliary Information Required | M | | BOOLEAN | TRUE means required. | + +### 9.2.2.150 SBAS IDs + +This IE defines multiple SBASs. + +Table 207 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|--------------------------------------------------------------------------------| +| SBAS IDs | M | | BIT STRING (SIZE(8)) | Each bit represents one SBAS as defined in TS 25.331 [4], subclause 10.3.3.45. | + +### 9.2.2.151 GANSS Additional Assistance Data Choices + +Table 208 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------| +| GANSS Additional Assistance Data Choices | | 1 | | | +| >Orbit Model ID | O | | INTEGER(0..7) | Coded as defined in the UE positioning GANSS additional assistance data request IE of TS 25.331 [4]. | +| >Clock Model ID | O | | INTEGER(0..7) | Coded as defined in the UE positioning GANSS additional assistance data request IE of TS 25.331 [4]. | +| >UTC Model ID | O | | INTEGER(0..7) | Coded as defined in the UE positioning GANSS additional assistance data request IE of TS 25.331 [4]. | +| >Almanac Model ID | O | | INTEGER(0..7) | Coded as defined in the UE positioning GANSS additional assistance data request IE of TS 25.331 [4]. | + +### 9.2.2.152 Cell-ID Measured Results Sets + +This IE contains the list of Cell-ID measurements of signals associated with one or more cells. + +Table 209 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------------|----------|--------------------------|-----------------------|-----------------------| +| Cell-ID Measured Results Sets | | 1.. | | | +| >Cell-ID Measured Results Info List | M | | 9.2.2.31 | For SAS-centric mode. | + +**Table 209A** + +| Range Bound | Explanation | +|--------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| maxNumberOfMeasurements | Maximum number of Measurements of Cell-ID Measured Results Info List and OTDOA Measured Results Info List included in the Position Calculation Request message. The value for maxNumberOfMeasurements is 16. | + +### 9.2.2.153 OTDOA Reference Cell Info SAS-centric mode + +**Table 210** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------| +| UC-ID | M | | 9.2.2.37 | The identifier of the reference cell for the SFN-SFN Observed Time Difference Type 2 measurements. | + +### 9.2.2.154 DGNSS Validity Period + +This IE defines the validity period of the GNSS differential corrections provided in *DGPS corrections* and *DGANSS corrections* IEs + +**Table 211** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------------------------------|----------|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UDRE Growth Rate | M | | Enumerated(
UDRE growth 1.5,
UDRE growth 2,
UDRE growth 4,
UDRE growth 6,
UDRE growth 8,
UDRE growth 10,
UDRE growth 12,
UDRE growth 16) | This field provides an estimate of the growth rate of uncertainty ( $1-\sigma$ ) in the corrections. The UDRE at time value specified in the Time of Validity for UDRE Growth Rate field is the value of this field times the value of UDRE provided in DGPS Corrections or DGANSS corrections IE (TS 25.331 [4]). | +| Time of Validity for UDRE Growth Rate | M | | Enumerated(
val20sec,
val40sec,
val80sec,
val160sec,
val320sec,
val640sec,
val1280sec,
val2560sec) | This field specifies the time when the UDRE Growth Rate field applies (TS 25.331 [4]). | + +### 9.2.2.155 IRAT Measured Results Info List + +This IE contains the Cell-ID measurements of signals associated with one or more Inter-RAT cells. + +Table 212 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|-------------------------------------------|----------|------------------------------|-----------------------|--------------------------------------------------------------| +| Cell-ID IRAT Measured Results Info | | | | | +| > GERAN Measured Results Info | O | | | | +| >> GERAN Measured Results | M | 1 to | | | +| >>> GERAN Cell Global Identity | O | | 9.2.2.156 | | +| >>>> GERAN PCI | | 1 | | | +| >>>>> bsic | M | | 9.2.2.157 | | +| >>>>> arfcn | M | | INTEGER (0..1023) | TS 45.005 [29] | +| >>> GSM RSSI | M | | INTEGER (0..63) | RXLEV is mapped to a value between 0 and 63, TS 45.008 [30]. | + +Table 212A + +| Range bound | Explanation | +|-----------------------|-----------------------------------------------------------------------------------| +| maxReportedGERANCells | Maximum number of GERAN neighbour cells. The value of maxReportedGERANCells is 6. | + +## 9.2.2.156 GERAN Cell Global Identity + +Table 213 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PLMN Identity | M | | OCTET STRING (SIZE (3)) |
  • - digits 0 to 9, encoded 0000 to 1001,
  • - 1111 used as filler digit, two digits per octet,
  • - bits 4 to 1 of octet n encoding digit 2n-1
  • - bits 8 to 5 of octet n encoding digit 2n
  • -The PLMN identity consists of 3 digits from MCC followed by either
  • -a filler digit plus 2 digits from MNC (in case of 2 digit MNC) or
  • -3 digits from MNC (in case of a 3 digit MNC).
| +| LAC | M | | INTEGER(0..65535) | Location Area Code | +| CI | M | | INTEGER(0..65535) | Cell Identifier | + +## 9.2.2.157 GSM BSIC + +Table 214 + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|--------------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------| +| Network Colour Code (NCC) | M | | BIT STRING (SIZE(3)) | The first/leftmost bit of the bit string contains the most significant bit of the NCC. | +| Base Station Colour Code (BCC) | M | | BIT STRING (SIZE(3)) | The first/leftmost bit of the bit string contains the most significant bit of the BCC. | + +### 9.2.2.158 IMSI + +This information element identifies the International Mobile Subscriber Identity of the target UE (see TS 25.413 [32]). + +**Table 215** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | M | | OCTET STRING (SIZE (3..8)) |
  • - digits 0 to 9, encoded 0000 to 1001,
  • - 1111 used as filler digit,
  • two digits per octet,
  • - bit 4 to 1 of octet n encoding digit 2n-1
  • - bit 8 to 5 of octet n encoding digit 2n

-Number of decimal digits shall be from 6 to 15 starting with the digits from the PLMN identity.
When the IMSI is made of an odd number of digits, the filler digit shall be added at the end to make an even number of digits of length 2N. The filler digit shall then be consequently encoded as bit 8 to 5 of octet N.

| + +### 9.2.2.159 IMEI + +This information element identifies the International Mobile Station Equipment Identity of the target UE (see TS 25.413 [32]) + +**Table 216** + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|---------------|----------|-------|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMEI | M | | OCTET STRING (SIZE (8)) |
  • - hexadecimal digits 0 to F, two hexadecimal digits per octet,
  • - each hexadecimal digit encoded 0000 to 1111,
  • - 1111 used as filler for bits 8 to 5 of last octet
  • - bit 4 to 1 of octet n encoding digit 2n-1
  • - bit 8 to 5 of octet n encoding digit 2n

Number of hexadecimal digits shall be 15.

| + +### 9.2.2.160 BDS Ionospheric Grid Model + +This IE contains BDS Ionospheric Grid information to calculate the propagation delays of the BII (BDS-SIS-ICD [33]) signal through the ionosphere. + +Table 217 + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|----------------------------------|----------|----------------------|------------------------------------|---------------------------------------------------------------------------------------------------------| +| BDS Reference Time | M | | INTEGER
(0..3570 by step of 30) | Seconds.
Time in BDS system time (modulo 3600 s) when the BDS Ionospheric Grid Information is valid. | +| BDS Ionospheric Grid Information | O | 1 .. | | Ionospheric information for up to 16 grid points will be included in this version of the specification. | +| >IGP number | M | | INTEGER
(1..320) | Ionospheric grid point number (dimensionless) (BDS-SIS-ICD [33]). | +| >Vertical Delay | M | | BIT STRING
(SIZE(9)) | Vertical Delay at Ionospheric Grid Points (meters) (BDS-SIS-ICD [33]). | +| >GIVEI | M | | BIT STRING
(SIZE(4)) | Grid Ionospheric Vertical Error Index (dimensionless) (BDS-SIS-ICD [33]). | + +Table 218 + +| Range Bound | Explanation | +|----------------|----------------------------------------------------------------------------------------------------------------------------------| +| maxIonGridInfo | Maximum number of ionospheric grid points information for which data is included in this IE. The value of maxIonGridInfo is 320. | + +### 9.2.2.161 DBDS Correction Information + +This IE contains BDS differential corrections to be used by the UE. + +Table 219 + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|----------------------------|----------|-------------------|------------------------------------|------------------------------------------------------------------------------------------| +| DBDS Reference Time | M | | INTEGER
(0..3570 by step of 30) | Seconds.
Time in BDS system time (modulo 3600 s) when the DBDS corrections are valid. | +| DBDS information | M | 1 to | | | +| >DBDS Signal ID | O | | 9.2.2.131 | Absence of this field means the B1I. | +| >DGANSS signal information | M | 1.. | | | +| >>Sat ID | M | | INTEGER(0..63) | Defined in TS 25.331 [4]. | +| >>UDREI | M | | INTEGER(0..15) | Defined in TS 25.331 [4]. | +| >>RURAI | M | | INTEGER(0..15) | Defined in TS 25.331 [4]. | +| >>Δt | M | | BIT STRING (SIZE(13)) | Defined in TS 25.331 [4]. | + +Table 220 + +| Range bound | Explanation | +|--------------|------------------------------------------------------------------------------------------------------| +| maxSgnType | Maximum number of signals for which data is included in this IE. The value of maxSgnType is 8. | +| maxGANSSTSat | Maximum number of satellites for which data is included in this IE. The value of maxGANSSTSat is 64. | + +### 9.2.2.162 Additional Positioning Measured Results + +This IE contains Additional Positioning Measured Results. + +Table 221 + +| IE/Group name | Presence | Range | IE Type and Reference | Semantics description | +|--------------------------------------|----------|--------------------|------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AddPos Measured Results | M | 1 to | | | +| >Time Stamp | O | | ASN.1 UTCTime | | +| >CHOICE type | M | | | Identifies the Additional Positioning method from which the measurements were obtained. | +| >>Barometric Pressure | | | | | +| >>>Uncompensated Barometric Pressure | M | | INTEGER (30000..115000) | The measured barometric pressure in units of Pa | +| >>WLAN | | | | | +| >>>WLAN Measurement Parameters | M | 1 to | | | +| >>>>WLAN AP BSSID | M | | OCTET STRING (SIZE(6)) | MAC address of the WLAN AP | +| >>>>WLAN SSID | O | | OCTET STRING (SIZE(1..32)) | The identifier of the wireless network served by the AP. | +| >>>>WLAN RSSI | O | | INTEGER(-127..128) | AP signal strength (RSSI) of a beacon frame, probe response frame or measurement pilot frame measured at the UE in dBm. | +| >>>>WLAN RTT value | O | | INTEGER(0..16777215) | The measured round trip time between the UE and WLAN AP. | +| >>>>WLAN RTT units | O | | ENUMERATED (microseconds,hundreds ofnanoseconds, tensofnanoseconds,nano seconds,tenthsofnanose cond) | The units for the RTT value | +| >>>>WLAN RTT accuracy | O | | INTEGER(0..255) | The estimated accuracy of the provided RTT value expressed as the standard deviation in units given by the RTT units. | +| >>>>WLAN AP Channel Frequency | O | | INTEGER(0..256) | The AP channel number identification of the reported WLAN AP. | +| >>>>WLAN Serving Flag | O | | BOOLEAN | Indicates whether a set of WLAN AP measurements were obtained for a serving WLAN AP (TRUE) or a non-serving WLAN AP (FALSE). A UE with multiple radio support may indicate more than one type of serving access for the same time instant. | +| >>BT | | | | Bluetooth | +| >>>BTMeasured results | M | 1 to | | | +| >>>>BTADDR | M | | OCTET STRING (SIZE(6)) | Bluetooth Public Address | +| >>>>BTRSSI | O | | INTEGER(-127..128) | Bluetooth RSSI | +| >>MBS | M | | | | +| >>>MBSMeasured results | M | 1 to | | | +| >>>>Transmitter ID | M | | INTEGER (0..32767) | Identifies the MBS transmitter | +| >>>>Code Phase | M | | INTEGER(0..2097151) | As defined in TS 25.331 [4] subclause 10.3.7.141. | +| >>>>Code Phase RMS Error | M | | INTEGER (0..63) | As defined in TS 25.331 [4] subclause 10.3.7.141. | + +**Table 222** + +| Range bound | Explanation | +|--------------------|----------------------------------------------------------------------------------------------------------------------| +| maxAddPos | Maximum number of Additional Positioning methods for which data is included in this IE. The value of maxAddPos is 8. | +| maxWLANs | Maximum number of WLANs reported. The value of maxWLANs is 64. | +| maxBTs | Maximum number of Bluetooth nodes reported. The value of maxBTs is 32. | +| maxBeacons | Maximum number of MBS beacon transmitters for which data is included in this IE. The value of maxBeacons is 64. | + +## 9.3 Message and Information Element Abstract Syntax (with ASN.1) + +### 9.3.0 General + +PCAP ASN.1 definition conforms with ITU-T Rec. X.680 [7], ITU-T Rec. X.681 [8], and ITU-T Rec. X.691 [9]. + +The ASN.1 definition specifies the structure and content of PCAP messages. PCAP messages can contain any IEs specified in the object set definitions for that message without the order or number of occurrence being restricted by ASN.1. However, for this version of the standard, a sending entity shall construct a PCAP message according to the PDU definitions module and with the following additional rules (Note that in the following IE means an IE in the object set with an explicit id. If one IE needed to appear more than once in one object set, then the different occurrences have different IE ids): + +- IEs shall be ordered (in an IE container) in the order they appear in object set definitions. +- Object set definitions specify how many times IEs may appear. An IE shall appear exactly once if the presence field in an object has value "mandatory". An IE may appear at most once if the presence field in an object has value "optional" or "conditional". If in a tabular format there is multiplicity specified for an IE (i.e. an IE list) then in the corresponding ASN.1 definition the list definition is separated into two parts. The first part defines an IE container list where the list elements reside. The second part defines list elements. The IE container list appears as an IE of its own. For this version of the standard an IE container list may contain only one kind of list elements. + +If a PCAP message that is not constructed as defined above is received, this shall be considered as Abstract Syntax Error, and the message shall be handled as defined for Abstract Syntax Error in clause 10.3.6. + +Clause 9.3 presents the Abstract Syntax of PCAP protocol with ASN.1. In case there is contradiction between the ASN.1 definition in this clause and the tabular format in clauses 9.1 and 9.2, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional elements, where the tabular format shall take precedence. + +### 9.3.1 Usage of private message mechanism for non-standard use + +The private message mechanism for non-standard use may be used: + +- for special operator- (and/or vendor) specific features considered not to be part of the basic functionality, i.e. the functionality required for a complete and high-quality specification in order to guarantee multivendor interoperability; +- by vendors for research purposes, e.g. to implement and evaluate new algorithms/features before such features are proposed for standardisation. + +The private message mechanism shall not be used for basic functionality. Such functionality shall be standardised. + +### 9.3.2 Elementary Procedure Definitions + +``` + +-- ***** +-- +-- Elementary Procedure definitions +-- +-- ***** + +``` + +``` +PCAP-PDU-Descriptions { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + umts-Access (20) modules (3) pcap(4) version1 (1) pcap-PDU-Descriptions (0)} + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ***** +-- +-- IE parameter types from other modules. +-- +-- ***** + +IMPORTS + Criticality, + ProcedureCode, + TransactionID +FROM PCAP-CommonDataTypes + + PositionCalculationRequest, + PositionCalculationResponse, + PositionCalculationFailure, + InformationExchangeInitiationRequest, + InformationExchangeInitiationResponse, + InformationExchangeInitiationFailure, + InformationReport, + InformationExchangeTerminationRequest, + InformationExchangeFailureIndication, + ErrorIndication, + PrivateMessage, + PositionInitiationRequest, + PositionInitiationResponse, + PositionInitiationFailure, + PositionActivationRequest, + PositionActivationResponse, + PositionActivationFailure, + PositionParameterModification, + Abort, + PositionPeriodicReport, + PositionPeriodicResult, + PositionPeriodicTermination + +FROM PCAP-PDU-Contents + + id-PositionCalculation, + id-InformationExchangeInitiation, + id-InformationReporting, + id-InformationExchangeTermination, + id-InformationExchangeFailure, + id-ErrorIndication, + id-privateMessage, +``` + +Error: + +211 + +Error: Reference source not found + +``` + + id-PositionInitiation, + id-PositionActivation, + id-PositionParameterModification, + id-Abort, + id-PositionPeriodicReport, + id-PositionPeriodicResult, + id-PositionPeriodicTermination + +FROM PCAP-Constants; + +-- ***** +-- +-- Interface Elementary Procedure Class +-- +-- ***** + +PCAP-ELEMENTARY-PROCEDURE ::= CLASS { + &InitiatingMessage , + &SuccessfulOutcome OPTIONAL, + &UnsuccessfulOutcome OPTIONAL, + &Outcome OPTIONAL, + &procedureCode ProcedureCode UNIQUE, + &criticality Criticality DEFAULT ignore +} + +WITH SYNTAX { + INITIATING MESSAGE &InitiatingMessage + [SUCCESSFUL OUTCOME &SuccessfulOutcome] + [UNSUCCESSFUL OUTCOME &UnsuccessfulOutcome] + [OUTCOME &Outcome] + PROCEDURE CODE &procedureCode + [CRITICALITY &criticality] +} + +-- ***** +-- +-- Interface PDU definitions +-- +-- ***** + +PCAP-PDU ::= CHOICE { + initiatingMessage InitiatingMessage, + successfulOutcome SuccessfulOutcome, + unsuccessfulOutcome UnsuccessfulOutcome, + outcome Outcome, + ... +} + +InitiatingMessage ::= SEQUENCE { + procedureCode PCAP-ELEMENTARY-PROCEDURE.&procedureCode ({PCAP-ELEMENTARY-PROCEDURES}), + criticality PCAP-ELEMENTARY-PROCEDURE.&criticality ({PCAP-ELEMENTARY-PROCEDURES}{@procedureCode}), +} + +``` + +``` + +transactionID TransactionID, +value PCAP-ELEMENTARY-PROCEDURE.&InitiatingMessage ({PCAP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +SuccessfulOutcome ::= SEQUENCE { + procedureCode PCAP-ELEMENTARY-PROCEDURE.&procedureCode ({PCAP-ELEMENTARY-PROCEDURES}), + criticality PCAP-ELEMENTARY-PROCEDURE.&criticality ({PCAP-ELEMENTARY-PROCEDURES}{@procedureCode}), + transactionID TransactionID, + value PCAP-ELEMENTARY-PROCEDURE.&SuccessfulOutcome ({PCAP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +UnsuccessfulOutcome ::= SEQUENCE { + procedureCode PCAP-ELEMENTARY-PROCEDURE.&procedureCode ({PCAP-ELEMENTARY-PROCEDURES}), + criticality PCAP-ELEMENTARY-PROCEDURE.&criticality ({PCAP-ELEMENTARY-PROCEDURES}{@procedureCode}), + transactionID TransactionID, + value PCAP-ELEMENTARY-PROCEDURE.&UnsuccessfulOutcome ({PCAP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +Outcome ::= SEQUENCE { + procedureCode PCAP-ELEMENTARY-PROCEDURE.&procedureCode ({PCAP-ELEMENTARY-PROCEDURES}), + criticality PCAP-ELEMENTARY-PROCEDURE.&criticality ({PCAP-ELEMENTARY-PROCEDURES}{@procedureCode}), + transactionID TransactionID, + value PCAP-ELEMENTARY-PROCEDURE.&Outcome ({PCAP-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +-- ***** +-- +-- Interface Elementary Procedure List +-- +-- ***** + +PCAP-ELEMENTARY-PROCEDURES PCAP-ELEMENTARY-PROCEDURE ::= { + PCAP-ELEMENTARY-PROCEDURES-CLASS-1 | + PCAP-ELEMENTARY-PROCEDURES-CLASS-2 , + ... +} + +PCAP-ELEMENTARY-PROCEDURES-CLASS-1 PCAP-ELEMENTARY-PROCEDURE ::= { + positionCalculation | + informationExchangeInitiation, + ..., + positionInitiation | + positionActivation +} + +PCAP-ELEMENTARY-PROCEDURES-CLASS-2 PCAP-ELEMENTARY-PROCEDURE ::= { + informationReporting | + informationExchangeTermination | + informationExchangeFailure | + errorIndication | +} + +``` + +``` + +privateMessage, +..., +positionParameterModification | +abort | +positionPeriodicReport | +positionPeriodicResult | +positionPeriodicTermination +} + +-- ***** +-- +-- Interface Elementary Procedures +-- +-- ***** + +positionCalculation PCAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PositionCalculationRequest + SUCCESSFUL OUTCOME PositionCalculationResponse + UNSUCCESSFUL OUTCOME PositionCalculationFailure + PROCEDURE CODE id-PositionCalculation + CRITICALITY reject +} + +informationExchangeInitiation PCAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE InformationExchangeInitiationRequest + SUCCESSFUL OUTCOME InformationExchangeInitiationResponse + UNSUCCESSFUL OUTCOME InformationExchangeInitiationFailure + PROCEDURE CODE id-InformationExchangeInitiation + CRITICALITY reject +} + +positionInitiation PCAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PositionInitiationRequest + SUCCESSFUL OUTCOME PositionInitiationResponse + UNSUCCESSFUL OUTCOME PositionInitiationFailure + PROCEDURE CODE id-PositionInitiation + CRITICALITY reject +} + +positionActivation PCAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PositionActivationRequest + SUCCESSFUL OUTCOME PositionActivationResponse + UNSUCCESSFUL OUTCOME PositionActivationFailure + PROCEDURE CODE id-PositionActivation + CRITICALITY reject +} + +informationReporting PCAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE InformationReport + +``` + +Error: + +214 + +Error: Reference source not found + +``` + PROCEDURE CODE id-InformationReporting + CRITICALITY ignore +} + +informationExchangeTermination PCAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE InformationExchangeTerminationRequest + PROCEDURE CODE id-InformationExchangeTermination + CRITICALITY ignore +} + +informationExchangeFailure PCAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE InformationExchangeFailureIndication + PROCEDURE CODE id-InformationExchangeFailure + CRITICALITY ignore +} + +errorIndication PCAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE ErrorIndication + PROCEDURE CODE id-ErrorIndication + CRITICALITY ignore +} + +privateMessage PCAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PrivateMessage + PROCEDURE CODE id-privateMessage + CRITICALITY ignore +} + +positionParameterModification PCAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PositionParameterModification + PROCEDURE CODE id-PositionParameterModification + CRITICALITY ignore +} + +abort PCAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Abort + PROCEDURE CODE id-Abort + CRITICALITY ignore +} + +positionPeriodicReport PCAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PositionPeriodicReport + PROCEDURE CODE id-PositionPeriodicReport + CRITICALITY ignore +} + +positionPeriodicResult PCAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PositionPeriodicResult +} +``` + +``` + + PROCEDURE CODE id-PositionPeriodicResult + CRITICALITY ignore + } + + positionPeriodicTermination PCAP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PositionPeriodicTermination + PROCEDURE CODE id-PositionPeriodicTermination + CRITICALITY ignore + } + +END + +``` + +### 9.3.3 PDU Definitions + +``` + +-- ***** +-- +-- PDU definitions for PCAP. +-- +-- ***** + +PCAP-PDU-Contents { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + umts-Access (20) modules (3) pcap(4) version1 (1) pcap-PDU-Contents (1) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ***** +-- +-- IE parameter types from other modules. +-- +-- ***** + +IMPORTS + Cause, + CriticalityDiagnostics, + GPS-UTRAN-TRU, + InformationExchangeID, + InformationReportCharacteristics, + InformationType, + MeasuredResultsList, + RequestedDataValue, + RequestedDataValueInformation, + UE-PositionEstimate, + CellId-MeasuredResultsSets, + OTDOA-MeasurementGroup, + AccuracyFulfilmentIndicator, + HorizontalAccuracyCode, + VerticalAccuracyCode, + RequestType, + +``` + +Error: + +216 + +Error: Reference source not found + +``` +UE-PositioningCapability, +UC-ID, +ResponseTime, +PositioningPriority, +ClientType, +PositioningMethod, +UTDOAPositioning, +GPSPositioning, +OTDOAAssistanceData, +UTDOA-Group, +Positioning-ResponseTime, +EnvironmentCharacterisation, +PositionData, +IncludeVelocity, +VelocityEstimate, +UE-PositionEstimateInfo, +OTDOA-MeasuredResultsSets, +PeriodicPosCalcInfo, +PeriodicLocationInfo, +AmountOfReporting, +MeasInstructionsUsed, +RRCstateChange, +PeriodicTerminationCause, +CellIDPositioning, +GANSS-MeasuredResultsList, +GANSSPositioning, +GANSS-UTRAN-TRU, +AdditionalGPSAssistDataRequired, +AdditionalGanssAssistDataRequired, +OTDOA-ReferenceCellInfoSAS-centric, +CellId-IRATMeasuredResultsSets, +IMSI, +IMEI, +AddPos-MeasuredResults + +FROM PCAP-IEs + +TransactionID + +FROM PCAP-CommonDataTypes + +ProtocolExtensionContainer{}, +ProtocolIE-ContainerList{}, +ProtocolIE-Container{}, +ProtocolIE-Single-Container{}, +PrivateIE-Container{}, +PCAP-PRIVATE-IES, +PCAP-PROTOCOL-EXTENSION, +PCAP-PROTOCOL-IES + +FROM PCAP-Containers +``` + +id-Cause, +id-CriticalityDiagnostics, +id-GPS-UTRAN-TRU, +id-InformationExchangeID, +id-InformationExchangeObjectType-InfEx-Rprt, +id-InformationExchangeObjectType-InfEx-Rqst, +id-InformationExchangeObjectType-InfEx-Rsp, +id-InformationReportCharacteristics, +id-InformationType, +id-GPS-MeasuredResultsList, +id-RequestedDataValue, +id-RequestedDataValueInformation, +id-TransactionID, +id-UE-PositionEstimate, +id-CellId-MeasuredResultsSets, +id-OTDOA-MeasurementGroup, +id-AccuracyFulfilmentIndicator, +id-HorizontalAccuracyCode, +id-VerticalAccuracyCode, +id-RequestType, +id-UE-PositioningCapability, +id-UC-id, +id-ResponseTime, +id-PositioningPriority, +id-ClientType, +id-PositioningMethod, +id-UTDOAPositioning, +id-GPSPositioning, +id-OTDOAAssistanceData, +id-UTDOA-Group, +id-Positioning-ResponseTime, +id-EnvironmentCharacterisation, +id-PositionData, +id-IncludeVelocity, +id-VelocityEstimate, +id-UE-PositionEstimateInfo, +id-UC-ID-InfEx-Rqst, +id-OTDOA-MeasuredResultsSets, +id-PeriodicPosCalcInfo, +id-PeriodicLocationInfo, +id-AmountOfReporting, +id-MeasInstructionsUsed, +id-RRStateChange, +id-PeriodicTerminationCause, +id-CellIDPositioning, +id-GNSS-MeasuredResultsList, +id-GNSSPositioning, +id-GNSS-UTRAN-TRU, +id-AdditionalGPSAssistDataRequired, +id-AdditionalGnssAssistDataRequired, +id-OTDOA-ReferenceCellInfo, + +``` + + id-CellId-IRATMeasuredResultsSets, + id-IMSI, + id-IMEI, + id-AddPos-MeasuredResults + +FROM PCAP-Constants; + +-- ***** +-- +-- POSITION CALCULATION REQUEST +-- +-- ***** + +PositionCalculationRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {PositionCalculationRequestIEs} }, + protocolExtensions ProtocolExtensionContainer { {PositionCalculationRequestExtensions} } OPTIONAL, + ... +} + +PositionCalculationRequestIEs PCAP-PROTOCOL-IES ::= { + { ID id-UE-PositionEstimate CRITICALITY reject TYPE UE-PositionEstimate PRESENCE optional } | + { ID id-GPS-MeasuredResultsList CRITICALITY reject TYPE MeasuredResultsList PRESENCE optional }, + ... +} + +PositionCalculationRequestExtensions PCAP-PROTOCOL-EXTENSION ::= { + { ID id-CellId-MeasuredResultsSets CRITICALITY reject EXTENSION CellId-MeasuredResultsSets PRESENCE optional } | + { ID id-OTDOA-MeasurementGroup CRITICALITY reject EXTENSION OTDOA-MeasurementGroup PRESENCE optional } | + { ID id-HorizontalAccuracyCode CRITICALITY ignore EXTENSION HorizontalAccuracyCode PRESENCE optional } | + { ID id-VerticalAccuracyCode CRITICALITY ignore EXTENSION VerticalAccuracyCode PRESENCE optional } | + { ID id-UTDOA-Group CRITICALITY reject EXTENSION UTDOA-Group PRESENCE optional } | + { ID id-Positioning-ResponseTime CRITICALITY ignore EXTENSION Positioning-ResponseTime PRESENCE optional } | + { ID id-IncludeVelocity CRITICALITY ignore EXTENSION IncludeVelocity PRESENCE optional } | + { ID id-PeriodicPosCalcInfo CRITICALITY ignore EXTENSION PeriodicPosCalcInfo PRESENCE optional } | + { ID id-GNSS-MeasuredResultsList CRITICALITY reject EXTENSION GNSS-MeasuredResultsList PRESENCE optional } | + { ID id-CellId-IRATMeasuredResultsSets CRITICALITY ignore EXTENSION CellId-IRATMeasuredResultsSets PRESENCE optional } | + { ID id-IMSI CRITICALITY ignore EXTENSION IMSI PRESENCE optional } | + { ID id-IMEI CRITICALITY ignore EXTENSION IMEI PRESENCE optional }, + ... +} + +-- ***** +-- +-- POSITION CALCULATION RESPONSE +-- +-- ***** + +PositionCalculationResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {PositionCalculationResponseIEs} }, + protocolExtensions ProtocolExtensionContainer { {PositionCalculationResponseExtensions} } OPTIONAL, + ... +} + +``` + +``` + +} + +PositionCalculationResponseIEs PCAP-PROTOCOL-IES ::= { + { ID id-UE-PositionEstimate CRITICALITY ignore TYPE UE-PositionEstimate PRESENCE mandatory } | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +PositionCalculationResponseExtensions PCAP-PROTOCOL-EXTENSION ::= { + { ID id-AccuracyFulfilmentIndicator CRITICALITY ignore EXTENSION AccuracyFulfilmentIndicator PRESENCE optional} | + { ID id-VelocityEstimate CRITICALITY ignore EXTENSION VelocityEstimate PRESENCE optional}, + ... +} + +-- ************************************************************** +-- +-- POSITION CALCULATION FAILURE +-- +-- ************************************************************** + +PositionCalculationFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {PositionCalculationFailureIEs} }, + protocolExtensions ProtocolExtensionContainer { {PositionCalculationFailureExtensions} } OPTIONAL, + ... +} + +PositionCalculationFailureIEs PCAP-PROTOCOL-IES ::= { + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory} | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +PositionCalculationFailureExtensions PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ************************************************************** +-- +-- INFORMATION EXCHANGE INITIATION REQUEST +-- +-- ************************************************************** + +InformationExchangeInitiationRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{InformationExchangeInitiationRequest-IEs}}, + protocolExtensions ProtocolExtensionContainer {{InformationExchangeInitiationRequest-Extensions}} OPTIONAL, + ... +} + +InformationExchangeInitiationRequest-IEs PCAP-PROTOCOL-IES ::= { + { ID id-InformationExchangeID CRITICALITY reject TYPE InformationExchangeID + PRESENCE mandatory }| + +``` + +``` + +{ ID id-InformationExchangeObjectType-InfEx-Rqst CRITICALITY reject TYPE InformationExchangeObjectType-InfEx-Rqst PRESENCE +mandatory }| +-- This IE represents both the Information Exchange Object Type IE and the choice based on the Information Exchange Object Type +-- as described in the tabular message format in clause 9.1. +{ ID id-InformationType CRITICALITY reject TYPE InformationType + PRESENCE mandatory }| +{ ID id-InformationReportCharacteristics CRITICALITY reject TYPE InformationReportCharacteristics + PRESENCE mandatory }| +{ ID id-GPS-UTRAN-TRU CRITICALITY reject TYPE GPS-UTRAN-TRU + PRESENCE conditional }, +-- This IE shall be present if the information requested in the Information Type IE contains GPS-related data +... +} + +InformationExchangeInitiationRequest-Extensions PCAP-PROTOCOL-EXTENSION ::= { +{ ID id-GNSS-UTRAN-TRU CRITICALITY reject EXTENSION GNSS-UTRAN-TRU + PRESENCE conditional }| +-- This IE shall be present if the information requested in the Information Type IE contains GNSS-related data +{ ID id-IMSI CRITICALITY ignore EXTENSION IMSI + PRESENCE optional }| +{ ID id-IMEI CRITICALITY ignore EXTENSION IMEI + PRESENCE optional }, +... +} + +InformationExchangeObjectType-InfEx-Rqst ::= CHOICE { + referencePosition RefPosition-InfEx-Rqst, + ... , + extension-InformationExchangeObjectType-InfEx-Rqst Extension-InformationExchangeObjectType-InfEx-Rqst +} + +RefPosition-InfEx-Rqst ::= SEQUENCE { + referencePositionEstimate UE-PositionEstimate, + iE-Extensions ProtocolExtensionContainer { { RefPositionItem-InfEx-Rqst-ExtIEs} } OPTIONAL, + ... +} + +RefPositionItem-InfEx-Rqst-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +Extension-InformationExchangeObjectType-InfEx-Rqst ::= ProtocolIE-Single-Container {{ Extension-InformationExchangeObjectType-InfEx-RqstIE }} + +Extension-InformationExchangeObjectType-InfEx-RqstIE PCAP-PROTOCOL-IES ::= { +{ ID id-UC-ID-InfEx-Rqst CRITICALITY reject TYPE UC-ID-InfEx-Rqst PRESENCE mandatory } | +{ ID id-CellId-MeasuredResultsSets CRITICALITY ignore TYPE CellId-MeasuredResultsSets PRESENCE mandatory } +} + +UC-ID-InfEx-Rqst ::= SEQUENCE { + referenceUC-ID UC-ID, + iE-Extensions ProtocolExtensionContainer { { UCIDItem-InfEx-Rqst-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` + + } + + UCIDItem-InfEx-Rqst-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + -- ***** + -- + -- INFORMATION EXCHANGE INITIATION RESPONSE + -- + -- ***** + + InformationExchangeInitiationResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{InformationExchangeInitiationResponse-IEs}}, + protocolExtensions ProtocolExtensionContainer {{InformationExchangeInitiationResponse-Extensions}} OPTIONAL, + ... + } + + InformationExchangeInitiationResponse-IEs PCAP-PROTOCOL-IES ::= { + { ID id-InformationExchangeID CRITICALITY ignore TYPE InformationExchangeID + PRESENCE mandatory } | + { ID id-InformationExchangeObjectType-InfEx-Rsp CRITICALITY ignore TYPE InformationExchangeObjectType-InfEx-Rsp PRESENCE + optional } | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics + PRESENCE optional }, + ... + } + + InformationExchangeInitiationResponse-Extensions PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + InformationExchangeObjectType-InfEx-Rsp ::= CHOICE { + referencePosition RefPosition-InfEx-Rsp, + ... + } + + RefPosition-InfEx-Rsp ::= SEQUENCE { + requestedDataValue RequestedDataValue, + iE-Extensions ProtocolExtensionContainer { { RefPositionItem-InfEx-Rsp-ExtIEs} } OPTIONAL, + ... + } + + RefPositionItem-InfEx-Rsp-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + -- ***** + -- + -- INFORMATION EXCHANGE INITIATION FAILURE + +``` + +``` + +-- +-- ***** + +InformationExchangeInitiationFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{InformationExchangeInitiationFailure-IEs}}, + protocolExtensions ProtocolExtensionContainer {{InformationExchangeInitiationFailure-Extensions}} OPTIONAL, + ... +} + +InformationExchangeInitiationFailure-IEs PCAP-PROTOCOL-IES ::= { + { ID id-InformationExchangeID CRITICALITY ignore TYPE InformationExchangeID PRESENCE mandatory } | + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +InformationExchangeInitiationFailure-Extensions PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- POSITION INITIATION REQUEST +-- +-- ***** + +PositionInitiationRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {PositionInitiationRequestIEs} }, + protocolExtensions ProtocolExtensionContainer { {PositionInitiationRequestExtensions} } OPTIONAL, + ... +} + +PositionInitiationRequestIEs PCAP-PROTOCOL-IES ::= { + { ID id-RequestType CRITICALITY reject TYPE RequestType PRESENCE mandatory } | + { ID id-UE-PositioningCapability CRITICALITY reject TYPE UE-PositioningCapability PRESENCE mandatory } | + { ID id-UC-id CRITICALITY reject TYPE UC-ID PRESENCE mandatory } | + { ID id-VerticalAccuracyCode CRITICALITY ignore TYPE VerticalAccuracyCode PRESENCE optional } | + { ID id-ResponseTime CRITICALITY ignore TYPE ResponseTime PRESENCE optional } | + { ID id-PositioningPriority CRITICALITY ignore TYPE PositioningPriority PRESENCE optional } | + { ID id-ClientType CRITICALITY ignore TYPE ClientType PRESENCE optional }, + ... +} + +PositionInitiationRequestExtensions PCAP-PROTOCOL-EXTENSION ::= { + { ID id-IncludeVelocity CRITICALITY ignore EXTENSION IncludeVelocity PRESENCE optional } | + { ID id-PeriodicLocationInfo CRITICALITY ignore EXTENSION PeriodicLocationInfo PRESENCE optional } | + { ID id-IMSI CRITICALITY ignore EXTENSION IMSI PRESENCE optional } | + { ID id-IMEI CRITICALITY ignore EXTENSION IMEI PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- POSITION INITIATION RESPONSE +-- +-- ***** + +PositionInitiationResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {PositionInitiationResponseIEs} }, + protocolExtensions ProtocolExtensionContainer { {PositionInitiationResponseExtensions} } OPTIONAL, + ... +} + +PositionInitiationResponseIEs PCAP-PROTOCOL-IES ::= { + { ID id-UE-PositionEstimate CRITICALITY reject TYPE UE-PositionEstimate PRESENCE mandatory } | + { ID id-PositionData CRITICALITY ignore TYPE PositionData PRESENCE mandatory } | + { ID id-AccuracyFulfilmentIndicator CRITICALITY ignore TYPE AccuracyFulfilmentIndicator PRESENCE optional }, + ... +} + +PositionInitiationResponseExtensions PCAP-PROTOCOL-EXTENSION ::= { + { ID id-VelocityEstimate CRITICALITY ignore EXTENSION VelocityEstimate PRESENCE optional }, + ... +} + +-- ***** +-- +-- POSITION INITIATION FAILURE +-- +-- ***** + +PositionInitiationFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {PositionInitiationFailureIEs} }, + protocolExtensions ProtocolExtensionContainer { {PositionInitiationFailureExtensions} } OPTIONAL, + ... +} + +PositionInitiationFailureIEs PCAP-PROTOCOL-IES ::= { + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +PositionInitiationFailureExtensions PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- POSITION ACTIVATION REQUEST +-- +-- ***** + +``` + +``` + +-- ***** + +PositionActivationRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {PositionActivationRequestIEs} }, + protocolExtensions ProtocolExtensionContainer { {PositionActivationRequestExtensions} } OPTIONAL, + ... +} + +PositionActivationRequestIEs PCAP-PROTOCOL-IES ::= { + { ID id-PositioningMethod CRITICALITY reject TYPE PositioningMethod PRESENCE mandatory } | + { ID id-Positioning-ResponseTime CRITICALITY ignore TYPE Positioning-ResponseTime PRESENCE mandatory } | + { ID id-PositioningPriority CRITICALITY ignore TYPE PositioningPriority PRESENCE optional } | + { ID id-EnvironmentCharacterisation CRITICALITY ignore TYPE EnvironmentCharacterisation PRESENCE optional } | + { ID id-UTDOAPositioning CRITICALITY reject TYPE UTDOAPositioning PRESENCE optional } | + { ID id-GPSPositioning CRITICALITY reject TYPE GPSPositioning PRESENCE optional } | + { ID id-OTDOAAssistanceData CRITICALITY reject TYPE OTDOAAssistanceData PRESENCE optional }, + ... +} + +PositionActivationRequestExtensions PCAP-PROTOCOL-EXTENSION ::= { + { ID id-IncludeVelocity CRITICALITY ignore EXTENSION IncludeVelocity PRESENCE optional } | + { ID id-AmountOfReporting CRITICALITY ignore EXTENSION AmountOfReporting PRESENCE optional } | + { ID id-CellIDPositioning CRITICALITY ignore EXTENSION CellIDPositioning PRESENCE optional } | + { ID id-GNSSPositioning CRITICALITY reject EXTENSION GNSSPositioning PRESENCE optional }, + ... +} + +-- ***** +-- +-- POSITION ACTIVATION RESPONSE +-- +-- ***** + +PositionActivationResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {PositionActivationResponseIEs} }, + protocolExtensions ProtocolExtensionContainer { {PositionActivationResponseExtensions} } OPTIONAL, + ... +} + +PositionActivationResponseIEs PCAP-PROTOCOL-IES ::= { + { ID id-UE-PositionEstimateInfo CRITICALITY ignore TYPE UE-PositionEstimateInfo PRESENCE optional } | + { ID id-GPS-MeasuredResultsList CRITICALITY reject TYPE MeasuredResultsList PRESENCE optional } | + { ID id-CellId-MeasuredResultsSets CRITICALITY reject TYPE CellId-MeasuredResultsSets PRESENCE optional } | + { ID id-OTDOA-MeasuredResultsSets CRITICALITY reject TYPE OTDOA-MeasuredResultsSets PRESENCE optional } | + { ID id-UTDOA-Group CRITICALITY reject TYPE UTDOA-Group PRESENCE optional }, + ... +} + +PositionActivationResponseExtensions PCAP-PROTOCOL-EXTENSION ::= { + { ID id-VelocityEstimate CRITICALITY ignore EXTENSION VelocityEstimate PRESENCE optional } | + { ID id-MeasInstructionsUsed CRITICALITY ignore EXTENSION MeasInstructionsUsed PRESENCE optional } | + +``` + +Error: + +225 + +Error: Reference source not found + +``` + + { ID id-GNSS-MeasuredResultsList CRITICALITY reject EXTENSION GNSS-MeasuredResultsList PRESENCE optional }| + { ID id-AdditionalGPSAssistDataRequired CRITICALITY ignore EXTENSION AdditionalGPSAssistDataRequired PRESENCE optional }| + { ID id-AdditionalGnssAssistDataRequired CRITICALITY ignore EXTENSION AdditionalGnssAssistDataRequired PRESENCE optional }| + { ID id-OTDOA-ReferenceCellInfo CRITICALITY reject EXTENSION OTDOA-ReferenceCellInfoSAS-centric PRESENCE optional }| + { ID id-CellId-IRATMeasuredResultsSets CRITICALITY ignore EXTENSION CellId-IRATMeasuredResultsSets PRESENCE optional }| + { ID id-AddPos-MeasuredResults CRITICALITY reject EXTENSION AddPos-MeasuredResults PRESENCE optional }, + ... +} + +``` + +``` + +-- ****************************************************************************** +-- +-- POSITION ACTIVATION FAILURE +-- +-- ****************************************************************************** + +``` + +``` + +PositionActivationFailure ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {PositionActivationFailureIEs} }, + protocolExtensions ProtocolExtensionContainer { {PositionActivationFailureExtensions} } OPTIONAL, + ... +} + +``` + +``` + +PositionActivationFailureIEs PCAP-PROTOCOL-IES ::= { + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +``` + +``` + +PositionActivationFailureExtensions PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +-- ****************************************************************************** +-- +-- INFORMATION REPORT +-- +-- ****************************************************************************** + +``` + +``` + +InformationReport ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {InformationReport-IEs} }, + protocolExtensions ProtocolExtensionContainer { {InformationReport-Extensions} } OPTIONAL, + ... +} + +``` + +``` + +InformationReport-IEs PCAP-PROTOCOL-IES ::= { + { ID id-InformationExchangeID CRITICALITY ignore TYPE InformationExchangeID PRESENCE mandatory } | + { ID id-InformationExchangeObjectType-InfEx-Rprt CRITICALITY ignore TYPE InformationExchangeObjectType-InfEx-Rprt PRESENCE mandatory }, + ... +} + +``` + +``` + +InformationReport-Extensions PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +InformationExchangeObjectType-InfEx-Rprt ::= CHOICE { + referencePosition RefPosition-InfEx-Rprt, + ... +} + +RefPosition-InfEx-Rprt ::= SEQUENCE { + requestedDataValueInformation RequestedDataValueInformation, + iE-Extensions ProtocolExtensionContainer {{ RefPositionItem-InfEx-Rprt-ExtIEs }} OPTIONAL, + ... +} + +RefPositionItem-InfEx-Rprt-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- INFORMATION EXCHANGE TERMINATION REQUEST +-- +-- ***** + +InformationExchangeTerminationRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{InformationExchangeTerminationRequest-IEs}}, + protocolExtensions ProtocolExtensionContainer {{InformationExchangeTerminationRequest-Extensions}} OPTIONAL, + ... +} + +InformationExchangeTerminationRequest-IEs PCAP-PROTOCOL-IES ::= { + { ID id-InformationExchangeID CRITICALITY ignore TYPE InformationExchangeID PRESENCE mandatory}, + ... +} + +InformationExchangeTerminationRequest-Extensions PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- INFORMATION EXCHANGE FAILURE INDICATION +-- +-- ***** + +InformationExchangeFailureIndication ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{InformationExchangeFailureIndication-IEs}}, + +``` + +Error: + +227 + +Error: Reference source not found + +``` + protocolExtensions ProtocolExtensionContainer { {InformationExchangeFailureIndication-Extensions} } OPTIONAL, + ... +} + +InformationExchangeFailureIndication-IEs PCAP-PROTOCOL-IES ::= { + { ID id-InformationExchangeID CRITICALITY ignore TYPE InformationExchangeID PRESENCE mandatory + } | + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE + mandatory }, + ... +} + +InformationExchangeFailureIndication-Extensions PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- ERROR INDICATION +-- +-- ***** + +ErrorIndication ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {ErrorIndicationIEs} }, + protocolExtensions ProtocolExtensionContainer { {ErrorIndicationExtensions} } OPTIONAL, + ... +} + +ErrorIndicationIEs PCAP-PROTOCOL-IES ::= { + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE optional } | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + ... +} + +ErrorIndicationExtensions PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- POSITION PARAMETER MODIFICATION +-- +-- ***** + +PositionParameterModification ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {PositionParameterModificationIEs} }, + protocolExtensions ProtocolExtensionContainer { {PositionParameterModificationExtensions} } OPTIONAL, + ... +} + +PositionParameterModificationIEs PCAP-PROTOCOL-IES ::= { +``` + +``` + + { ID id-UC-ID CRITICALITY reject TYPE UC-ID PRESENCE optional }| + { ID id-UTDOA-Group CRITICALITY reject TYPE UTDOA-Group PRESENCE optional }, + ... +} + +``` + +``` + +PositionParameterModificationExtensions PCAP-PROTOCOL-EXTENSION ::= { + { ID id-RRcstateChange CRITICALITY ignore EXTENSION RRcstateChange PRESENCE optional }, + ... +} + +``` + +``` + +-- ***** +-- +-- PRIVATE MESSAGE +-- +-- ***** + +``` + +``` + +PrivateMessage ::= SEQUENCE { + privateIEs PrivateIE-Container {{PrivateMessage-IEs}}, + ... +} + +``` + +``` + +PrivateMessage-IEs PCAP-PRIVATE-IES ::= { + ... +} + +``` + +``` + +-- ***** +-- +-- ABORT +-- +-- ***** + +``` + +``` + +Abort ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {AbortIEs} }, + protocolExtensions ProtocolExtensionContainer { {AbortExtensions} } OPTIONAL, + ... +} + +``` + +``` + +AbortIEs PCAP-PROTOCOL-IES ::= { + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }, + ... +} + +``` + +``` + +AbortExtensions PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +-- ***** +-- +-- POSITION PERIODIC REPORT +-- +-- ***** + +``` + +``` + +-- ***** + +PositionPeriodicReport ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{PositionPeriodicReport-IEs}}, + protocolExtensions ProtocolExtensionContainer {{PositionPeriodicReport-Extensions}} OPTIONAL, + ... +} + +PositionPeriodicReport-IEs PCAP-PROTOCOL-IES ::= { + { ID id-UE-PositionEstimateInfo CRITICALITY ignore TYPE UE-PositionEstimateInfo PRESENCE optional } | + { ID id-VelocityEstimate CRITICALITY ignore TYPE VelocityEstimate PRESENCE optional } | + { ID id-GPS-MeasuredResultsList CRITICALITY ignore TYPE MeasuredResultsList PRESENCE optional } | + { ID id-CellId-MeasuredResultsSets CRITICALITY ignore TYPE CellId-MeasuredResultsSets PRESENCE optional } | + { ID id-OTDOA-MeasuredResultsSets CRITICALITY ignore TYPE OTDOA-MeasuredResultsSets PRESENCE optional } | + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE optional } , + ... +} + +PositionPeriodicReport-Extensions PCAP-PROTOCOL-EXTENSION ::= { + { ID id-GNSSS-MeasuredResultsList CRITICALITY ignore EXTENSION GNSSS-MeasuredResultsList PRESENCE optional}| + { ID id-AdditionalGPSAssistDataRequired CRITICALITY ignore EXTENSION AdditionalGPSAssistDataRequired PRESENCE optional}| + { ID id-AdditionalGanSSAssistDataRequired CRITICALITY ignore EXTENSION AdditionalGanSSAssistDataRequired PRESENCE optional}| + { ID id-OTDOA-ReferenceCellInfo CRITICALITY reject EXTENSION OTDOA-ReferenceCellInfoSAS-centric PRESENCE optional}| + { ID id-CellId-IRATMeasuredResultsSets CRITICALITY ignore EXTENSION CellId-IRATMeasuredResultsSets PRESENCE optional}| + { ID id-AddPos-MeasuredResults CRITICALITY ignore EXTENSION AddPos-MeasuredResults PRESENCE optional}, + ... +} + +-- ***** +-- +-- POSITION PERIODIC RESULT +-- +-- ***** + +PositionPeriodicResult ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{PositionPeriodicResult-IEs}}, + protocolExtensions ProtocolExtensionContainer {{PositionPeriodicResult-Extensions}} OPTIONAL, + ... +} + +PositionPeriodicResult-IEs PCAP-PROTOCOL-IES ::= { + { ID id-UE-PositionEstimate CRITICALITY ignore TYPE UE-PositionEstimate PRESENCE optional } | + { ID id-VelocityEstimate CRITICALITY ignore TYPE VelocityEstimate PRESENCE optional } | + { ID id-PositionData CRITICALITY ignore TYPE PositionData PRESENCE optional } | + { ID id-AccuracyFulfilmentIndicator CRITICALITY ignore TYPE AccuracyFulfilmentIndicator PRESENCE optional } | + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE optional } , + ... +} + +PositionPeriodicResult-Extensions PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +-- ***** +-- +-- POSITION PERIODIC TERMINATION +-- +-- ***** + +PositionPeriodicTermination ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{PositionPeriodicTermination-IEs}}, + protocolExtensions ProtocolExtensionContainer {{PositionPeriodicTermination-Extensions}} OPTIONAL, + ... +} + +PositionPeriodicTermination-IEs PCAP-PROTOCOL-IEs ::= { + { ID id-PeriodicTerminationCause CRITICALITY ignore TYPE PeriodicTerminationCause PRESENCE optional }, + ... +} + +PositionPeriodicTermination-Extensions PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +END + +``` + +## 9.3.4 Information Element Definitions + +``` + +-- ***** +-- +-- Information Element Definitions +-- +-- ***** + +PCAP-IEs { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + umts-Access (20) modules (3) pcap(4) version1 (1) pcap-IEs (2) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +IMPORTS + maxNrOfErrors, + maxSat, + maxSatAlmanac, + maxNrOfLevels, + maxNrOfMeasNCell, + maxNrOfMeasurements, + maxNrOfPoints, + maxNrOfExpInfo, + +``` + +Error: + +231 + +Error: Reference source not found + +``` +maxNrOfSets, +maxRateMatching, +maxNrOfTFs, +maxTTI-count, +maxTS-1, +maxCCTrCH, +maxTF, +maxTFC, +maxPRACH, +maxTrCH, +maxTGPS, +maxNoOfMeasurements, +maxCellMeas, +maxNrOfEDPCCH-PO-QUANTSTEPS, +maxNrOfRefETFCI-PO-QUANTSTEPS, +maxNrOfRefETFCIs, +maxSet, +maxGANSS, +maxGANSSSat, +maxGANSSSet, +maxSgnType, +maxGANSSSatAlmanac, +maxGANSSClockMod, +maxGANSS-1, +maxNrOfIRATMeasurements, +maxReportedGERANCells, +maxIonGridInfo, +maxAddPos, +maxBeacons, +maxBTs, +maxWLANs, + +id-UTRAN-GPSReferenceTime, +id-UTRAN-GPSReferenceTimeResult, +id-GPS-UTRAN-TRU, +id-UTRAN-GPS-DriftRate, +id-OTDOA-AddMeasuredResultsInfo, +id-GPS-ReferenceLocation, +id-rxTimingDeviation768Info, +id-rxTimingDeviation384extInfo, +id-MeasurementValidity, +id-ExtendedRoundTripTime, +id-roundTripTimeInfoWithType1, +id-AddMeasurementInfo, +id-Extended-RNC-ID, +id-GANSS-CommonAssistanceData, +id-GANSS-GenericAssistanceDataList, +id-GANSS-PositioningDataSet, +id-GNSS-PositioningMethod, +id-NetworkAssistedGANSSSupport, +id-TUTRANGANSSMeasurementValueInfo, +``` + +id-angleOfArrivalLCR, +id-extendedTimingAdvanceLCR, +id-additionalMeasurementInforLCR, +id-timingAdvanceLCR-R7, +id-rxTimingDeviationLCR, +id-GPSReferenceTimeUncertainty, +id-GANSS-AddIonoModelReq, +id-GANSS-EarthOrientParaReq, +id-GANSS-Additional-Ionospheric-Model, +id-GANSS-Earth-Orientation-Parameters, +id-GANSS-Additional-Time-Models, +id-GANSS-Additional-Navigation-Models, +id-GANSS-Additional-UTC-Models, +id-GANSS-Auxiliary-Information, +id-GANSS-SBAS-ID, +id-GANSS-SBAS-IDs, +id-GANSS-Signal-IDs, +id-GANSS-alm-keplerianNAValmanac, +id-GANSS-alm-keplerianReducedAlmanac, +id-GANSS-alm-keplerianMidiAlmanac, +id-GANSS-alm-keplerianGLONASS, +id-GANSS-alm-ecefSBASAlmanac, +id-UTRAN-GANSSReferenceTimeResult, +id-GANSS-Reference-Time-Only, +id-GANSS-AddADchoices, +id-supportGANSSNonNativeADchoices, +id-PositionDataUEbased, +id-ganssCodePhaseAmbiguityExt, +id-ganssIntegerCodePhaseExt, +id-GANSSCarrierPhaseRequested, +id-GANSSMultiFreqMeasRequested, +id-ganssReq-AddIonosphericModel, +id-ganssReq-EarthOrientPara, +id-ganssAddNavigationModel-req, +id-ganssAddUTCModel-req, +id-ganssAuxInfo-req, +id-GANSS-AlmanacModelChoice, +id-DGNSS-ValidityPeriod, +id-AzimuthAndElevationLSB, +id-completeAlmanacProvided, +id-GPS-Week-Cycle, +id-GANSS-Day-Cycle, +id-ganss-Delta-T, +id-requestedCellIDGERANMeasurements, +id-GANSS-alm-keplerianBDSAlmanac, +id-BDS-Ionospheric-Grid-Model, +id-DBDS-Correction-Information, +id-BDSIonosphericGridModel, +id-DBDSCorrection, +id-Confidence, +id-ExtraDopplerInfoExtension, +id-GANSS-Confidence, + +``` + + id-GANSS-ExtraDopplerExtension, + id-Additional-PositioningDataSet, + id-Additional-PositioningMethod, + id-AddPos-MeasuredResults, + id-AddPosSupport + +FROM PCAP-Constants + + Criticality, + ProcedureCode, + ProtocolIE-ID, + TransactionID, + TriggeringMessage + +FROM PCAP-CommonDataTypes + + ProtocolExtensionContainer{}, + ProtocolIE-Single-Container{}, + PCAP-PROTOCOL-EXTENSION, + PCAP-PROTOCOL-IES + +FROM PCAP-Containers; + +-- ***** +-- +-- Accuracy Fulfilment Indicator +-- +-- ***** + +AccuracyFulfilmentIndicator ::= ENUMERATED{ + requested-Accuracy-Fulfilled, + requested-Accuracy-Not-Fulfilled, + ... +} + +-- ***** +-- +-- Additional Method Type +-- +-- ***** + +AdditionalMethodType ::= ENUMERATED { + ue-assisted, + ue-based, + ue-based-preferred-but-ue-assisted-allowed, + ue-assisted-preferred-but-ue-based-allowed, + ... +} + +``` + +``` + +-- ***** +-- +-- Additional Positioning Measured Results +-- +-- ***** + +AddPos-MeasuredResults ::= SEQUENCE (SIZE (1..maxAddPos)) OF AddPos-MeasuredResults-Element + +AddPos-MeasuredResults-Element ::= SEQUENCE { + timestamp UTCTime OPTIONAL, + type CHOICE { + barometricPressure SEQUENCE { + uncompensatedBarometricPressure BaroMeasurement, + iE-Extensions ProtocolExtensionContainer { { BarometricPressure-ExtIEs } } OPTIONAL, + ... + }, + wlan SEQUENCE { + wlanMeasurementList WLANMeasurementList, + iE-Extensions ProtocolExtensionContainer { { WLANMeasurementList-ExtIEs } } OPTIONAL, + ... + }, + bt SEQUENCE { + btMeasurementList BTMeasurementList, + iE-Extensions ProtocolExtensionContainer { { BTMeasurementList-ExtIEs } } OPTIONAL, + ... + }, + mbs SEQUENCE { + mbsMeasurementList MBSMeasurementList, + iE-Extensions ProtocolExtensionContainer { { MBSMeasurementList-ExtIEs } } OPTIONAL, + ... + }, + ... + }, + ... +} + +BarometricPressure-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +WLANMeasurementList-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +BTMeasurementList-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +MBSMeasurementList-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +WLANMeasurementList ::= SEQUENCE (SIZE (1..maxWLANs)) OF WLANMeasurementList-Element + +WLANMeasurementList-Element ::= SEQUENCE { +wlanBSSID OCTET STRING (SIZE (6)), +wlanSSID OCTET STRING (SIZE(1..32)) OPTIONAL, +wlanRSSI INTEGER(-127..128) OPTIONAL, +wlanRTTvalue INTEGER(0..16777215) OPTIONAL, +wlanRTTunits ENUMERATED { microseconds,hundredsofnanoseconds, tensofnanoseconds, nanoseconds, tenthsfnanosecond, ...} OPTIONAL, +wlanRTTaccuracy INTEGER(0..255) OPTIONAL, +wlanAPChannelFrequency INTEGER(0..256) OPTIONAL, +wlanServingFlag BOOLEAN OPTIONAL, +iE-Extensions ProtocolExtensionContainer { { WLANMeasurementList-Element-ExtIEs } } OPTIONAL, +... +} + +WLANMeasurementList-Element-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { +... +} + +BTMeasurementList ::= SEQUENCE (SIZE (1..maxBTs)) OF BTMeasurementList-Element + +BTMeasurementList-Element ::= SEQUENCE { +btADDR OCTET STRING (SIZE(6)), +btRSSI INTEGER(-127..128) OPTIONAL, +iE-Extensions ProtocolExtensionContainer { { BTMeasurementList-Element-ExtIEs } } OPTIONAL, +... +} + +BTMeasurementList-Element-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { +... +} + +MBSMeasurementList ::= SEQUENCE (SIZE (1..maxBeacons)) OF MBSMeasurementList-Element + +MBSMeasurementList-Element ::= SEQUENCE { +transmitterID INTEGER(0..32767), +codephase INTEGER(0..2097151), +codephaseRMS INTEGER(0..63), +iE-Extensions ProtocolExtensionContainer { { MBSMeasurementList-Element-ExtIEs } } OPTIONAL, +... +} + +MBSMeasurementList-Element-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { +... +} + +BaroMeasurement ::= INTEGER(30000..115000) + +-- \*\*\*\*\* +-- +-- Almanac and Satellite Health SIB +-- + +``` + +-- ***** +AlmanacAndSatelliteHealthSIB ::= SEQUENCE { + gpsAlmanacAndSatelliteHealth GPS-AlmanacAndSatelliteHealth, + satMask BIT STRING (SIZE (1..32)), + lsbTOW BIT STRING (SIZE (8)), + iE-Extensions ProtocolExtensionContainer { { AlmanacAndSatelliteHealthSIB-ExtIEs } } OPTIONAL, + ... +} + +AlmanacAndSatelliteHealthSIB-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Cause IE +-- +-- ***** + +Cause ::= CHOICE { + radioNetwork CauseRadioNetwork, + transport CauseTransport, + protocol CauseProtocol, + misc CauseMisc, + ... +} + +CauseRadioNetwork ::= ENUMERATED { + invalid-reference-information, + information-temporarily-not-available, + information-provision-not-supported-for-the-object, + position-calculation-error-invalid-GPS-measured-results, + ..., + position-calculation-error-invalid-CellID-measured-results, + position-calculation-error-invalid-OTDOA-measured-results, + position-calculation-error-AGPS-positioning-method-not-supported, + position-calculation-error-CellID-positioning-method-not-supported, + position-calculation-error-OTDOA-positioning-method-not-supported, + initial-UE-position-estimate-missing, + position-calculation-error-invalid-UTDOA-measured-results, + position-calculation-error-UTDOA-positioning-method-not-supported, + position-calculation-error-UTDOA-not-supported-UTRAN-cell, + positioning-method-not-supported, + loss-of-contact-with-UE, + sAS-unable-to-perform-UTDOA-positioning-within-response-time, + location-measurement-failure, + ue-positioning-error-Not-enough-OTDOA-cells, + ue-positioning-error-Not-enough-GPS-Satellites, + ue-positioning-error-Reference-Cell-not-serving-cell, + ue-positioning-error-Not-Accomplished-GPS-Timing-of-Cell-Frames, + ue-positioning-error-Undefined-Error, +} + +``` + +``` + +position-calculation-error-invalid-Galileo-measured-results, +position-calculation-error-AGalileo-positioning-method-not-supported, +ue-positioning-error-Not-enough-Galileo-Satellites, +ue-positioning-error-Not-Accomplished-Galileo-Timing-of-Cell-Frames, +ue-positioning-error-Assistance-Data-missing, +position-calculation-error-invalid-GLONASS-measured-results, +position-calculation-error-invalid-GNSSS-measured-results, +position-calculation-error-AGNSSS-positioning-method-not-supported, +ue-positioning-error-Not-enough-GNSSS-Satellites, +ue-positioning-error-Not-Accomplished-GNSSS-Timing-of-Cell-Frames, +position-calculation-error-invalid-BDS-measured-results, +ue-Positioning-Error-Not-enough-BDS-Satellites, +position-calculation-error-A-BDS-positioning-method-not-supported +} + +CauseTransport ::= ENUMERATED { + transport-resource-unavailable, + unspecified, + ... +} + +CauseProtocol ::= ENUMERATED { + transfer-syntax-error, + abstract-syntax-error-reject, + abstract-syntax-error-ignore-and-notify, + message-not-compatible-with-receiver-state, + semantic-error, + unspecified, + abstract-syntax-error-falsely-constructed-message, + ... +} + +CauseMisc ::= ENUMERATED { + processing-overload, + hardware-failure, + o-and-m-intervention, + unspecified, + ... +} + +-- ***** +-- +-- Cell Id Measured Results Sets +-- +-- ***** + +CellId-MeasuredResultsSets ::= SEQUENCE (SIZE (1..maxNrOfMeasurements)) OF + CellId-MeasuredResultsInfoList + +CellId-MeasuredResultsInfoList ::= SEQUENCE (SIZE (1..maxNrOfMeasNCell)) OF + CellId-MeasuredResultsInfo + +``` + +Error: + +238 + +Error: Reference source not found + +``` +CellId-MeasuredResultsInfo ::= SEQUENCE { + uC-ID UC-ID, + uTRANAccessPointPositionAltitude UTRANAccessPointPositionAltitude, + ue-PositionEstimate UE-PositionEstimate OPTIONAL, + roundTripTimeInfo RoundTripTimeInfo OPTIONAL, -- FDD only + rxTimingDeviationInfo RxTimingDeviationInfo OPTIONAL, -- 3.84Mcps TDD only + rxTimingDeviationLCRInfo RxTimingDeviationLCRInfo OPTIONAL, -- 1.28Mcps TDD only + pathloss Pathloss OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { CellId-MeasuredResultsInfo-ExtIEs } } OPTIONAL, + ... +} + +CellId-MeasuredResultsInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + { ID id-rxTimingDeviation768Info CRITICALITY reject EXTENSION RxTimingDeviation768Info PRESENCE optional }| -- 7.68Mcps TDD + only + { ID id-rxTimingDeviation384extInfo CRITICALITY reject EXTENSION RxTimingDeviation384extInfo PRESENCE optional }| -- 3.84Mcps TDD + only + { ID id-roundTripTimeInfoWithType1 CRITICALITY ignore EXTENSION RoundTripTimeInfoWithType1 PRESENCE optional }| -- FDD only + { ID id-AddMeasurementInfo CRITICALITY ignore EXTENSION AddMeasurementInfo PRESENCE optional }| + { ID id-angleOfArrivalLCR CRITICALITY ignore EXTENSION AngleOfArrivalLCR PRESENCE optional }, + ... +} + +RoundTripTimeInfo ::= SEQUENCE { + ue-RxTxTimeDifferenceType2 UE-RxTxTimeDifferenceType2, + ue-PositioningMeasQuality UE-PositioningMeasQuality, + roundTripTime RoundTripTime, + iE-Extensions ProtocolExtensionContainer { { RoundTripTimeInfo-ExtIEs } } OPTIONAL, + ... +} + +RoundTripTimeInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + { ID id-ExtendedRoundTripTime CRITICALITY ignore EXTENSION ExtendedRoundTripTime PRESENCE optional }, -- FDD only + ... +} + +RoundTripTimeInfoWithType1 ::= SEQUENCE { + ue-RxTxTimeDifferenceType1 UE-RxTxTimeDifferenceType1, + roundTripTime RoundTripTime, + extendedRoundTripTime ExtendedRoundTripTime OPTIONAL, -- FDD only + iE-Extensions ProtocolExtensionContainer { { RoundTripTimeInfoWithType1-ExtIEs } } OPTIONAL, + ... +} + +RoundTripTimeInfoWithType1-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +UE-RxTxTimeDifferenceType2 ::= INTEGER (0..8191) +UE-RxTxTimeDifferenceType1 ::= INTEGER (768..1280) +``` + +``` + +UE-PositioningMeasQuality ::= + SEQUENCE { + stdResolution BIT STRING (SIZE (2)), + numberOfMeasurements BIT STRING (SIZE (3)), + stdOfMeasurements BIT STRING (SIZE (5)), + iE-Extensions ProtocolExtensionContainer { { UE-PositioningMeasQuality-ExtIEs } } OPTIONAL, + ... + } + +UE-PositioningMeasQuality-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +RoundTripTime ::= + INTEGER (0..32766) +-- Actual value RoundTripTime = IE value * 0.0625 + 876 + +ExtendedRoundTripTime ::= + INTEGER (32767..103041) +-- Actual value RoundTripTime = IE value * 0.0625 + 876 + +UTRANAccessPointPositionAltitude ::= + SEQUENCE { + geographicalCoordinates GeographicalCoordinates, + ga-AltitudeAndDirection GA-AltitudeAndDirection + OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UTRANAccessPointPositionAltitude-ExtIEs } } OPTIONAL, + ... + } + +UTRANAccessPointPositionAltitude-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +RxTimingDeviationInfo ::= + SEQUENCE { + rxTimingDeviation RxTimingDeviation, + timingAdvance TimingAdvance, + iE-Extensions ProtocolExtensionContainer { { RxTimingDeviationInfo-ExtIEs } } OPTIONAL, + ... + } + +RxTimingDeviationInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +RxTimingDeviationLCRInfo ::= + SEQUENCE { + rxTimingDeviationLCR RxTimingDeviationLCR, + timingAdvanceLCR TimingAdvanceLCR, + -- The content of this IE shall be ignored if the id-extendedTimingAdvanceLCR IE is present. + iE-Extensions ProtocolExtensionContainer { { RxTimingDeviationLCRInfo-ExtIEs } } OPTIONAL, + ... + } + +RxTimingDeviationLCRInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +Error: + +240 + +Error: Reference source not found + +``` +{ ID id-extendedTimingAdvanceLCR CRITICALITY ignore EXTENSION ExtendedTimingAdvanceLCR PRESENCE optional }, -- 1.28Mcps TDD +only + ... +} + +ExtendedTimingAdvanceLCR ::= INTEGER (2048..8191) + +RxTimingDeviation768Info ::= SEQUENCE { + rxTimingDeviation768 RxTimingDeviation768, + timingAdvance768 TimingAdvance768, + iE-Extensions ProtocolExtensionContainer { { RxTimingDeviation768Info-ExtIEs } } OPTIONAL, + ... +} + +RxTimingDeviation768Info-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +RxTimingDeviation384extInfo ::= SEQUENCE { + rxTimingDeviation384ext RxTimingDeviation384ext, + timingAdvance384ext TimingAdvance384ext, + iE-Extensions ProtocolExtensionContainer { { RxTimingDeviation384extInfo-ExtIEs } } OPTIONAL, + ... +} + +RxTimingDeviation384extInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +AddMeasurementInfo ::= SEQUENCE { + cpich-RSCP CPICH-RSCP OPTIONAL, + cpich-EcNo CPICH-EcNo OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { AddMeasurementInfo-ExtIEs } } OPTIONAL, + ... +} + +AddMeasurementInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +AngleOfArrivalLCR ::= SEQUENCE { + aOA-LCR AOA-LCR, + aOA-LCR-Accuracy-Class AOA-LCR-Accuracy-Class, + iE-Extensions ProtocolExtensionContainer { { AngleOfArrivalLCR-ExtIEs } } OPTIONAL, + ... +} + +AngleOfArrivalLCR-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +Error: + +241 + +Error: Reference source not found + +``` +RxTimingDeviation ::= + INTEGER (0..8191) +RxTimingDeviationLCR ::= + INTEGER (0..511) +RxTimingDeviation768 ::= + INTEGER (0..65535) +RxTimingDeviation384ext ::= + INTEGER (0..32767) +TimingAdvance ::= + INTEGER (0..63) +TimingAdvanceLCR ::= + INTEGER (0..2047) +TimingAdvance768 ::= + INTEGER (0..511) +TimingAdvance384ext ::= + INTEGER (0..255) +Pathloss ::= + INTEGER (46..158) +-- Unit: dB; as defined in the Cell measured results IE of TS 25.331 [4] +CPICH-EcNo ::= + INTEGER (0..49) +-- According to CPICH_Ec/No in TS 25.133 [13] +CPICH-RSCP ::= + INTEGER (-5..91) +-- According to CPICH_RSCP in TS 25.133 [13] +AOA-LCR ::= + INTEGER (0..719)-- According to mapping in TS 25.123 [14] +AOA-LCR-Accuracy-Class ::= + ENUMERATED { + a,b,c,d,e,f,g,h, ...} + +-- ***** +-- +-- Cell Id IRAT Measured Results Sets +-- +-- ***** + +CellId-IRATMeasuredResultsSets ::= + SEQUENCE (SIZE (1..maxNrOfIRATMeasurements)) OF + CellId-IRATMeasuredResultsInfoList + +CellId-IRATMeasuredResultsInfoList ::= + SEQUENCE { + gERAN-MeasuredResultsInfoList + GERAN-MeasuredResultsInfoList + OPTIONAL, + iE-Extensions + ProtocolExtensionContainer { { CellId-IRATMeasuredResultsInfoListExtIEs } } + OPTIONAL, + ... + } + +CellId-IRATMeasuredResultsInfoListExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GERAN-MeasuredResultsInfoList ::= + SEQUENCE (SIZE (1..maxReportedGERANCells)) OF + GERAN-MeasuredResultsInfo +``` + +``` + +GERAN-MeasuredResultsInfo := SEQUENCE { + gERANCellID GERANCellGlobalID OPTIONAL, + gERANPhysicalCellID GERANPhysicalCellID, + gSM-RSSI GSM-RSSI, + iE-Extensions ProtocolExtensionContainer { { GERAN-MeasuredResultsInfo-ExtIEs } } OPTIONAL, + ... +} + +GERAN-MeasuredResultsInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GERANCellGlobalID := SEQUENCE { + plmn-Identity PLMN-Identity, --As defined in TS 23.003 + locationAreaCode BIT STRING (SIZE (16)), + cellIdentity BIT STRING (SIZE (16)), + iE-Extensions ProtocolExtensionContainer { { GERANCellGlobalID-ExtIEs } } OPTIONAL, + ... +} + +GERANCellGlobalID-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +PLMN-Identity ::= OCTET STRING (SIZE (3)) + +GSM-RSSI ::= INTEGER (0..63) + +GERANPhysicalCellID ::= SEQUENCE { + bsic GSM-BSIC, + arfcn GSM-BCCH-ARFCN +} + +GSM-BSIC ::= SEQUENCE { + networkColourCode BIT STRING (SIZE (3)), + baseStationColourCode BIT STRING (SIZE (3)) +} + +GSM-BCCH-ARFCN ::= INTEGER (0..1023) + +-- ***** +-- +-- Cell-ID Positioning (Position Activation Request Message) +-- +-- ***** + +CellIDPositioning ::= SEQUENCE { + requestedCellIDMeasurements RequestedCellIDMeasurements, + iE-Extensions ProtocolExtensionContainer { { CellIDPositioning-ExtIEs } } OPTIONAL, + ... +} + +``` + +``` + + } + + CellIDPositioning-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + { ID id-requestedCellIDGERANMeasurements CRITICALITY reject EXTENSION RequestedCellIDGERANMeasurements PRESENCE optional }, + ... + } + + RequestedCellIDMeasurements ::= CHOICE { + fdd SEQUENCE { + roundTripTimeInfoWanted BOOLEAN, + pathlossWanted BOOLEAN, + roundTripTimeInfoWithType1Wanted BOOLEAN, + cpichRSCPWanted BOOLEAN, + cpicEcNoWanted BOOLEAN, + iE-Extensions ProtocolExtensionContainer { { RequestedCellIDMeasurementsFDD-ExtIEs } } OPTIONAL, + ... + }, + tdd SEQUENCE { + rxTimingDeviationInfoWanted BOOLEAN, + pathlossWanted BOOLEAN, + rxTimingDeviationLCRInfoWanted BOOLEAN, + rxTimingDeviation768InfoWanted BOOLEAN, + rxTimingDeviation384extInfoWanted BOOLEAN, + angleOfArrivalLCRWanted BOOLEAN, + timingAdvanceLCRWanted BOOLEAN, + iE-Extensions ProtocolExtensionContainer { { RequestedCellIDMeasurementsTDD-ExtIEs } } OPTIONAL, + ... + }, + ... + } + + RequestedCellIDMeasurementsFDD-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + RequestedCellIDMeasurementsTDD-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + RequestedCellIDGERANMeasurements ::= SEQUENCE { + rSSIMEasurementsWanted BOOLEAN, + iE-Extensions ProtocolExtensionContainer { { RequestedCellIDGERANMeasurements-ExtIEs } } OPTIONAL, + ... + } + + RequestedCellIDGERANMeasurements-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + +``` + +``` + +-- ***** +-- + +``` + +``` + +-- Client Type +-- +-- ***** + +ClientType ::= ENUMERATED { + emergency-services, + value-added-services, + plmn-operator-services, + lawful-intercept-services, + plmn-operator-broadcast-services, + plmn-operator-oam, + plmn-operator-anonymous-statistics, + plmn-operator-target-ms-service-support, + ... +} + +-- ***** +-- +-- CriticalityDiagnostics +-- +-- ***** + +CriticalityDiagnostics ::= SEQUENCE { + procedureCode ProcedureCode OPTIONAL, + triggeringMessage TriggeringMessage OPTIONAL, + procedureCriticality Criticality OPTIONAL, + transactionID TransactionID OPTIONAL, + iEsCriticalityDiagnostics CriticalityDiagnostics-IE-List OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {CriticalityDiagnostics-ExtIEs} } OPTIONAL, + ... +} + +CriticalityDiagnostics-IE-List ::= SEQUENCE (SIZE (1..maxNrOfErrors)) OF + SEQUENCE { + iECriticality Criticality, + iE-ID ProtocolIE-ID, + repetitionNumber CriticalityDiagnosticsRepetition OPTIONAL, + messageStructure MessageStructure OPTIONAL, + typeOfError TypeOfError, + iE-Extensions ProtocolExtensionContainer { {CriticalityDiagnostics-IE-List-ExtIEs} } OPTIONAL, + ... + } + +CriticalityDiagnostics-IE-List-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +CriticalityDiagnostics-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +CriticalityDiagnosticsRepetition ::= INTEGER (0..255) + +``` + +``` + +TypeOfError ::= ENUMERATED { + not-understood, + missing, + ... +} + +-- ***** +-- +-- DGPSCorrections +-- +-- ***** + +DGPSCorrections ::= SEQUENCE { + gps-TOW-sec INTEGER (0..604799), + statusHealth DiffCorrectionStatus, + dgps-CorrectionSatInfoList DGPS-CorrectionSatInfoList OPTIONAL, + -- not included if satelliteHealth is equal to noData or invalidData + iE-Extensions ProtocolExtensionContainer { { DGPSCorrections-ExtIEs } } OPTIONAL, + ... +} + +DGPSCorrections-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +DiffCorrectionStatus ::= ENUMERATED { + udre-1-0, udre-0-75, udre-0-5, udre-0-3, + udre-0-2, udre-0-1, noData, invalidData } + +DGPS-CorrectionSatInfoList ::= SEQUENCE (SIZE (1..maxSat)) OF + DGPS-CorrectionSatInfo + +DGPS-CorrectionSatInfo ::= SEQUENCE { + satID INTEGER (0..63), + iode INTEGER (0..255), + udre UDRE, + prc PRC, + rrc RRC, + iE-Extensions ProtocolExtensionContainer { { DGPS-CorrectionSatInfo-ExtIEs } } OPTIONAL, + ... +} + +DGPS-CorrectionSatInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + {ID id-DGNSS-ValidityPeriod CRITICALITY ignore EXTENSION DGNSS-ValidityPeriod PRESENCE optional}, + ... +} + +``` + +``` + +DGNSS-ValidityPeriod ::= + SEQUENCE { + udreGrowthRate UDREGrowthRate, + udreValidityTime UDREValidityTime, + iE-Extensions ProtocolExtensionContainer { { DGNSS-ValidityPeriod-ExtIEs } } OPTIONAL, + ... + } + +DGNSS-ValidityPeriod-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +UDRE ::= + ENUMERATED { + lessThan1, + between1-and-4, + between4-and-8, + over8 } + +UDREGrowthRate ::= + ENUMERATED { + growth-1-point-5, + growth-2, + growth-4, + growth-6, + growth-8, + growth-10, + growth-12, + growth-16 } + +UDREValidityTime ::= + ENUMERATED { + val-20sec, + val-40sec, + val-80sec, + val-160sec, + val-320sec, + val-640sec, + val-1280sec, + val-2560sec } + +PRC ::= + INTEGER (-2047..2047) + +RRC ::= + INTEGER (-127..127) + +-- ***** +-- +-- IMEI, IMSI +-- +-- ***** + +-- IMEI + +IMEI ::= + OCTET STRING (SIZE (8)) + +-- IMSI + +``` + +``` + +IMSI ::= OCTET STRING (SIZE (3..8)) + +-- ***** +-- +-- UE-PositionEstimate (i.e., Geographical Area) +-- +-- ***** + +-- UE-PositionEstimate is based on Geographical Area Description in 23.032 + +UE-PositionEstimate ::= CHOICE { + point GA-Point, + pointWithUncertainty GA-PointWithUncertainty, + polygon GA-Polygon, + pointWithUncertaintyEllipse GA-PointWithUncertaintyEllipse, + pointWithAltitude GA-PointWithAltitude, + pointWithAltitudeAndUncertaintyEllipsoid GA-PointWithAltitudeAndUncertaintyEllipsoid, + ellipsoidArc GA-EllipsoidArc, + ... +} + +GeographicalCoordinates ::= SEQUENCE { + latitudeSign ENUMERATED {north, south}, + latitude INTEGER (0..8388607), + longitude INTEGER (-8388608..8388607), + iE-Extensions ProtocolExtensionContainer { {GeographicalCoordinates-ExtIEs} } OPTIONAL, + ... +} + +GeographicalCoordinates-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GA-AltitudeAndDirection ::= SEQUENCE { + directionOfAltitude ENUMERATED {height, depth}, + altitude INTEGER (0..32767), + ... +} + +GA-EllipsoidArc ::= SEQUENCE { + geographicalCoordinates GeographicalCoordinates, + innerRadius INTEGER (0..65535), + uncertaintyRadius INTEGER (0..127), + offsetAngle INTEGER (0..179), + includedAngle INTEGER (0..179), + confidence INTEGER (0..100), + iE-Extensions ProtocolExtensionContainer { { GA-EllipsoidArc-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` +GA-EllipsoidArc-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GA-Point ::= SEQUENCE { + geographicalCoordinates GeographicalCoordinates, + iE-Extensions ProtocolExtensionContainer { { GA-Point-ExtIEs} } OPTIONAL, + ... +} + +GA-Point-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GA-PointWithAltitude ::= SEQUENCE { + geographicalCoordinates GeographicalCoordinates, + altitudeAndDirection GA-AltitudeAndDirection, + iE-Extensions ProtocolExtensionContainer { { GA-PointWithAltitude-ExtIEs} } OPTIONAL, + ... +} + +GA-PointWithAltitude-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GA-PointWithAltitudeAndUncertaintyEllipsoid ::= SEQUENCE { + geographicalCoordinates GeographicalCoordinates, + altitudeAndDirection GA-AltitudeAndDirection, + uncertaintyEllipse GA-UncertaintyEllipse, + uncertaintyAltitude INTEGER (0..127), + confidence INTEGER (0..100), + iE-Extensions ProtocolExtensionContainer { { GA-PointWithAltitudeAndUncertaintyEllipsoid-ExtIEs} } OPTIONAL, + ... +} + +GA-PointWithAltitudeAndUncertaintyEllipsoid-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GA-PointWithUnCertainty ::= SEQUENCE { + geographicalCoordinates GeographicalCoordinates, + uncertaintyCode INTEGER (0..127), + iE-Extensions ProtocolExtensionContainer { { GA-PointWithUnCertainty-ExtIEs} } OPTIONAL, + ... +} + +GA-PointWithUnCertainty-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GA-PointWithUnCertaintyEllipse ::= SEQUENCE { + geographicalCoordinates GeographicalCoordinates, + uncertaintyEllipse GA-UncertaintyEllipse, +``` + +``` + +confidence INTEGER (0..100), +iE-Extensions ProtocolExtensionContainer { { GA-PointWithUncertaintyEllipse-ExtIEs } } OPTIONAL, +... +} + +GA-PointWithUncertaintyEllipse-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GA-Polygon ::= SEQUENCE (SIZE (1..maxNrOfPoints)) OF + SEQUENCE { + geographicalCoordinates GeographicalCoordinates, + iE-Extensions ProtocolExtensionContainer { { GA-Polygon-ExtIEs } } OPTIONAL, + ... + } + +GA-Polygon-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GA-UncertaintyEllipse ::= SEQUENCE { + uncertaintySemi-major INTEGER (0..127), + uncertaintySemi-minor INTEGER (0..127), + orientationOfMajorAxis INTEGER (0..89), + ... +} + +-- ***** +-- +-- UE-PositionEstimateInfo +-- +-- ***** + +UE-PositionEstimateInfo ::= SEQUENCE { + referenceTimeChoice ReferenceTimeChoice, + ue-positionEstimate UE-PositionEstimate, + iE-Extensions ProtocolExtensionContainer { { UE-PositionEstimateInfo-ExtIEs } } OPTIONAL, + ... +} + +UE-PositionEstimateInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + {ID id-GPSReferenceTimeUncertainty CRITICALITY ignore EXTENSION GPSReferenceTimeUncertainty PRESENCE optional}| + {ID id-PositionDataUEbased CRITICALITY ignore EXTENSION PositionDataUEbased PRESENCE optional}, + ... +} + +ReferenceTimeChoice ::= CHOICE { + utran-GPSReferenceTimeResult UTRAN-GPSReferenceTimeResult, + gps-ReferenceTimeOnly INTEGER (0..604799999, ...), + cell-Timing Cell-Timing, + ... / + extension-ReferenceTimeChoice Extension-ReferenceTimeChoice +} + +``` + +``` + +} + +Extension-ReferenceTimeChoice ::= ProtocolIE-Single-Container {{ Extension-ReferenceTimeChoice-IE }} + +Extension-ReferenceTimeChoice-IE PCAP-PROTOCOL-IES ::= { + { ID id-UTRAN-GANSSReferenceTimeResult CRITICALITY ignore TYPE UTRAN-GANSSReferenceTimeResult PRESENCE + mandatory} | + { ID id-GANSS-Reference-Time-Only CRITICALITY ignore TYPE GANSS-Reference-Time-Only PRESENCE + mandatory} +} + +Cell-Timing ::= SEQUENCE { + sfn INTEGER (0..4095), + uC-ID UC-ID, + iE-Extensions ProtocolExtensionContainer { { Cell-Timing-ExtIEs } } OPTIONAL, + ... +} + +Cell-Timing-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-Reference-Time-Only ::= SEQUENCE { + ganssTODmsec INTEGER (0..35999999), + ganssTimeID GANSSID OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { GANSS-Reference-Time-Only-ExtIEs } } OPTIONAL, + ... +} + +GANSS-Reference-Time-Only-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +PositionDataUEbased ::= SEQUENCE { + positionData BIT STRING (SIZE(16)), + iE-Extensions ProtocolExtensionContainer { { PositionDataUEbased-ExtIEs } } OPTIONAL, + ... +} + +PositionDataUEbased-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- *********************************************************** +-- +-- Position Data +-- +-- *********************************************************** + +``` + +``` + +-- ***** + +PositionData ::= SEQUENCE { + positioningDataDiscriminator PositioningDataDiscriminator, + positioningDataSet PositioningDataSet OPTIONAL, + -- This IE shall be present if the PositioningDataDiscriminator IE is set to the value "0000" -- + iE-Extensions ProtocolExtensionContainer { {PositionData-ExtIEs} } OPTIONAL, + ... +} + +PositionData-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + { ID id-GANSS-PositioningDataSet CRITICALITY ignore EXTENSION GANSS-PositioningDataSet PRESENCE optional}| + { ID id-Additional-PositioningDataSet CRITICALITY ignore EXTENSION Additional-PositioningDataSet PRESENCE optional}| + ... +} + +GANSS-PositioningDataSet ::= SEQUENCE(SIZE(1..maxGANSSSet)) OF GANSS-PositioningMethodAndUsage + +GANSS-PositioningMethodAndUsage ::= OCTET STRING (SIZE(1)) + +PositioningDataDiscriminator ::= BIT STRING (SIZE(4)) + +PositioningDataSet ::= SEQUENCE(SIZE(1..maxSet)) OF PositioningMethodAndUsage + +PositioningMethodAndUsage ::= OCTET STRING (SIZE(1)) + +Additional-PositioningDataSet ::= SEQUENCE(SIZE(1..maxAddPos)) OF Additional-PositioningMethodAndUsage + +Additional-PositioningMethodAndUsage ::= OCTET STRING (SIZE(1)) + +-- ***** +-- +-- GPS-AcquisitionAssistance: +-- +-- ***** + +GPS-AcquisitionAssistance ::= SEQUENCE { + gps-TOW-1msec INTEGER (0..604799999), + satelliteInformationList AcquisitionSatInfoList, + iE-Extensions ProtocolExtensionContainer { { GPS-AcquisitionAssistance-ExtIEs } } OPTIONAL, + ... +} + +GPS-AcquisitionAssistance-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + {ID id-UTRAN-GPSReferenceTime CRITICALITY ignore EXTENSION UTRAN-GPSReferenceTime PRESENCE optional}| + {ID id-GPSReferenceTimeUncertainty CRITICALITY ignore EXTENSION GPSReferenceTimeUncertainty PRESENCE optional}| + {ID id-Confidence CRITICALITY ignore EXTENSION Confidence PRESENCE optional}| + ... +} + +``` + +``` + +} + +AcquisitionSatInfoList ::= + SEQUENCE (SIZE (1..maxSat)) OF + AcquisitionSatInfo + +AcquisitionSatInfo ::= + SEQUENCE { + satID INTEGER (0..63), + doppler0thOrder INTEGER (-2048..2047), + extraDopplerInfo ExtraDopplerInfo OPTIONAL, + codePhase INTEGER (0..1022), + integerCodePhase INTEGER (0..19), + gps-BitNumber INTEGER (0..3), + codePhaseSearchWindow, CodePhaseSearchWindow, + azimuthAndElevation AzimuthAndElevation OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { AcquisitionSatInfo-ExtIEs } } OPTIONAL, + ... + } + +AcquisitionSatInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + {ID id-ExtraDopplerInfoExtension CRITICALITY ignore EXTENSION ExtraDopplerInfoExtension PRESENCE optional}, + ... +} + +ExtraDopplerInfo ::= + SEQUENCE { + doppler1stOrder INTEGER (-42..21), + dopplerUncertainty DopplerUncertainty, + iE-Extensions ProtocolExtensionContainer { { ExtraDopplerInfo-ExtIEs } } OPTIONAL, + ... + } + +ExtraDopplerInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +ExtraDopplerInfoExtension ::= SEQUENCE { + doppler1stOrder INTEGER (-42..21), + dopplerUncertaintyExtension DopplerUncertaintyExtension, + iE-Extensions ProtocolExtensionContainer { { ExtraDopplerInfoExtension-ExtIEs } } OPTIONAL, + ... +} + +ExtraDopplerInfoExtension-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +DopplerUncertainty ::= + ENUMERATED { + hz12-5, hz25, hz50, hz100, hz200, ... + } + +DopplerUncertaintyExtension ::= ENUMERATED { + +``` + +``` + + hz300, hz400, hz500, hz600, noInformation, ...} + +CodePhaseSearchWindow ::= + ENUMERATED { + w1023, w1, w2, w3, w4, w6, w8, + w12, w16, w24, w32, w48, w64, + w96, w128, w192 } + +AzimuthAndElevation ::= + SEQUENCE { + azimuth INTEGER (0..31), + elevation INTEGER (0..7), + ie-Extensions ProtocolExtensionContainer { { AzimuthAndElevation-ExtIEs } } OPTIONAL, + ... + } + +AzimuthAndElevation-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + {ID id-AzimuthAndElevationLSB CRITICALITY ignore EXTENSION AzimuthAndElevationLSB PRESENCE optional}, + ... +} + +AzimuthAndElevationLSB ::= + SEQUENCE { + azimuthLSB INTEGER (0..15), + elevationLSB INTEGER (0..15), + ie-Extensions ProtocolExtensionContainer { { AzimuthAndElevationLSB-ExtIEs } } OPTIONAL, + ... + } + +AzimuthAndElevationLSB-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +Confidence ::= INTEGER(0..100) + +-- ***** +-- +-- GANSS Elements +-- +-- ***** + +AuxInfoGANSS-ID1 ::= SEQUENCE (SIZE(1.. maxGANSSSat)) OF AuxInfoGANSS-ID1-element + +AuxInfoGANSS-ID1-element ::= SEQUENCE { + svID INTEGER(0..63), + signalsAvailable BIT STRING (SIZE(8)), + ie-Extensions ProtocolExtensionContainer { { AuxInfoGANSS-ID1-element-ExtIEs } } OPTIONAL, + ... +} + +AuxInfoGANSS-ID1-element-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` +AuxInfoGANSS-ID3 ::= SEQUENCE (SIZE(1.. maxGANSSSat)) OF AuxInfoGANSS-ID3-element + +AuxInfoGANSS-ID3-element ::= SEQUENCE { + svID INTEGER(0..63), + signalsAvailable BIT STRING (SIZE(8)), + channelNumber INTEGER (-7..13), + ie-Extensions ProtocolExtensionContainer { { AuxInfoGANSS-ID3-element-ExtIEs } } OPTIONAL, + ... +} + +AuxInfoGANSS-ID3-element-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +CNAVclockModel ::= SEQUENCE { + cnavToc BIT STRING (SIZE (11)), + cnavTop BIT STRING (SIZE (11)), + cnavURA0 BIT STRING (SIZE (5)), + cnavURA1 BIT STRING (SIZE (3)), + cnavURA2 BIT STRING (SIZE (3)), + cnavAf2 BIT STRING (SIZE (10)), + cnavAf1 BIT STRING (SIZE (20)), + cnavAf0 BIT STRING (SIZE (26)), + cnavTgd BIT STRING (SIZE (13)), + cnavISCl1cp BIT STRING (SIZE (13)) OPTIONAL, + cnavISCl1cd BIT STRING (SIZE (13)) OPTIONAL, + cnavISCl1ca BIT STRING (SIZE (13)) OPTIONAL, + cnavISCl2c BIT STRING (SIZE (13)) OPTIONAL, + cnavISCl5i5 BIT STRING (SIZE (13)) OPTIONAL, + cnavISCl5q5 BIT STRING (SIZE (13)) OPTIONAL, + ie-Extensions ProtocolExtensionContainer { { CNAVclockModel-ExtIEs } } OPTIONAL, + ... +} + +CNAVclockModel-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +DeltaUT1 ::= SEQUENCE { + b1 BIT STRING (SIZE(11)), + b2 BIT STRING (SIZE(10)), + ie-Extensions ProtocolExtensionContainer { { DeltaUT1-ExtIEs } } OPTIONAL, + ... +} + +DeltaUT1-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +DGANSS-Corrections ::= SEQUENCE { + dGANSS-ReferenceTime INTEGER(0..119), +``` + +``` + + dGANSS-Information DGANSS-Information, + ie-Extensions ProtocolExtensionContainer { { DGANSS-Corrections-ExtIEs } } OPTIONAL, + ... + } + + DGANSS-Corrections-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + DGANSS-Information ::= SEQUENCE (SIZE (1..maxSgnType)) OF DGANSS-InformationItem + + DGANSS-InformationItem ::= SEQUENCE { + gANSS-SignalId GANSS-SignalID OPTIONAL, + gANSS-StatusHealth GANSS-StatusHealth, + -- The following IE shall be present if the Status/Health IE value is not equal to "no data" or "invalid data" + dGANSS-SignalInformation DGANSS-SignalInformation OPTIONAL, + ie-Extensions ProtocolExtensionContainer { { DGANSS-InformationItem-ExtIEs } } OPTIONAL, + ... + } + + DGANSS-InformationItem-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + DGANSS-SignalInformation ::= SEQUENCE (SIZE (1..maxGANSSSat)) OF DGANSS-SignalInformationItem + + DGANSS-SignalInformationItem ::= SEQUENCE { + satId INTEGER(0..63), + gANSS-iod BIT STRING (SIZE (10)), + udre UDRE, + ganss-prc INTEGER(-2047..2047), + ganss-rrc INTEGER(-127..127), + ie-Extensions ProtocolExtensionContainer { { DGANSS-SignalInformationItem-ExtIEs } } OPTIONAL, + ... + } + + DGANSS-SignalInformationItem-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + {ID id-DGNSS-ValidityPeriod CRITICALITY ignore EXTENSION DGNSS-ValidityPeriod PRESENCE optional}, + ... + } + + GANSS-AddClockModels ::= CHOICE { + navClockModel NAVclockModel, + cnvClockModel CNAVclockModel, + glonassClockModel GLONASSclockModel, + sbasClockModel SBASclockModel, + ... + } + +``` + +``` + + bDSClockModel BDSClockModel + } + + GANSS-AddOrbitModels ::= CHOICE { + navKeplerianSet NavModel-NAVKeplerianSet, + cnavKeplerianSet NavModel-CNAVKeplerianSet, + glonassECEF NavModel-GLONASSEcef, + sbasECEF NavModel-SBASecf, + ... + bDSKeplerianSet NavModel-BDSKeplerianSet + } + + GANSS-Additional-Ionospheric-Model ::= SEQUENCE { + dataID BIT STRING (SIZE(2)), + alpha-beta-parameters GPS-Ionospheric-Model, + ie-Extensions ProtocolExtensionContainer { { GANSS-Additional-Ionospheric-Model-ExtIEs } } OPTIONAL, + ... + } + + GANSS-Additional-Ionospheric-Model-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + GANSS-Additional-Navigation-Models ::= SEQUENCE { + non-broadcastIndication ENUMERATED { true } OPTIONAL, + ganssSatInfoNavList Ganss-Sat-Info-AddNavList, + ie-Extensions ProtocolExtensionContainer { { GANSS-Additional-Navigation-Models-ExtIEs } } OPTIONAL, + ... + } + + GANSS-Additional-Navigation-Models-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + GANSS-Additional-Time-Models ::= SEQUENCE (SIZE (1..maxGANSS-1)) OF GANSS-Time-Model + + GANSS-Additional-UTC-Models ::= CHOICE { + utcModel1 UTCmodelSet1, + utcModel2 UTCmodelSet2, + utcModel3 UTCmodelSet3, + ... + utcModel4 UTCmodelSet4 + } + + GANSS-ALM-BDSKeplericanset ::= SEQUENCE { + satellite-Information-BDS-KP-List Satellite-Information-BDS-KP-List, + ie-Extensions ProtocolExtensionContainer { { GANSS-ALM-BDSKeplericanset-ExtIEs } } OPTIONAL, + ... + } + +``` + +``` + +GANSS-ALM-BDSKeplericanset-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +Satellite-Information-BDS-KP-List ::= SEQUENCE (SIZE (1..maxGANSSSatAlmanac)) OF Satellite-Information-BDS-KP-Item + +Satellite-Information-BDS-KP-Item ::= SEQUENCE { + sVID-BDS INTEGER (0..63), + tOA-BDS BIT STRING( SIZE(8) ), + a21-BDS BIT STRING( SIZE(24) ), + e-BDS BIT STRING( SIZE(17) ), + omg-lower-BDS BIT STRING( SIZE(24) ), + m0-BDS BIT STRING( SIZE(24) ), + omg-0-BDS BIT STRING( SIZE(24) ), + omg-upper-BDS BIT STRING( SIZE(17) ), + delta-i-BDS BIT STRING( SIZE(16) ), + a0-BDS BIT STRING( SIZE(11) ), + a1-BDS BIT STRING( SIZE(11) ), + -- The following IE is mandatory present if the sVID-BDS is between 0 and 29 and not needed otherwise. + hea-BDS BIT STRING( SIZE(9) ) OPTIONAL, + ie-Extensions ProtocolExtensionContainer { { Satellite-Information-BDS-KP-Item-ExtIEs } } OPTIONAL, + ... +} + +Satellite-Information-BDS-KP-Item-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-ALM-ECEFsbasAlmanacSet ::= SEQUENCE { + sat-info-SBASecfList GANSS-SAT-Info-Almanac-SBASecfList, + ie-Extensions ProtocolExtensionContainer { { GANSS-ALM-ECEFsbasAlmanacSet-ExtIEs } } OPTIONAL, + ... +} + +GANSS-ALM-ECEFsbasAlmanacSet-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-ALM-GlonassAlmanacSet ::= SEQUENCE { + sat-info-GLOkpList GANSS-SAT-Info-Almanac-GLOkpList, + ie-Extensions ProtocolExtensionContainer { { GANSS-ALM-GlonassAlmanacSet-ExtIEs } } OPTIONAL, + ... +} + +GANSS-ALM-GlonassAlmanacSet-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + + - +} + +GANSS-ALM-MidiAlmanacSet ::= SEQUENCE { + t-oa INTEGER (0..255), + sat-info-MIDIkpList GANSS-SAT-Info-Almanac-MIDIkpList, + ie-Extensions ProtocolExtensionContainer { { GANSS-ALM-MidiAlmanacSet-ExtIEs } } OPTIONAL, + ... +} + +GANSS-ALM-MidiAlmanacSet-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-ALM-NAVKeplerianSet ::= SEQUENCE { + t-oa INTEGER (0..255), + sat-info-NAVkpList GANSS-SAT-Info-Almanac-NAVkpList, + ie-Extensions ProtocolExtensionContainer { { GANSS-ALM-NAVKeplerianSet-ExtIEs } } OPTIONAL, + ... +} + +GANSS-ALM-NAVKeplerianSet-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-ALM-ReducedKeplerianSet ::= SEQUENCE { + t-oa INTEGER (0..255), + sat-info-REDkpList GANSS-SAT-Info-Almanac-REDkpList, + ie-Extensions ProtocolExtensionContainer { { GANSS-ALM-ReducedKeplerianSet-ExtIEs } } OPTIONAL, + ... +} + +GANSS-ALM-ReducedKeplerianSet-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-AlmanacAndSatelliteHealth ::= SEQUENCE { + weekNumber INTEGER (0..255), + gANSS-AlmanacModel GANSS-AlmanacModel, + ie-Extensions ProtocolExtensionContainer { { GANSS-AlmanacAndSatelliteHealth-ExtIEs } } OPTIONAL, + ... +} + +GANSS-AlmanacAndSatelliteHealth-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + {ID id-completeAlmanacProvided CRITICALITY ignore EXTENSION CompleteAlmanacProvided PRESENCE optional}, +} + +``` + +``` + + ... + } + + GANSS-AlmanacModel ::= CHOICE { + gANSS-keplerianParameters GANSS-KeplerianParametersAlm, + ... + extension-GANSS-AlmanacModel Extension-GANSS-AlmanacModel + } + + Extension-GANSS-AlmanacModel ::= ProtocolIE-Single-Container {{ Extension-GANSS-AlmanacModel-IE }} + + Extension-GANSS-AlmanacModel-IE PCAP-PROTOCOL-IES ::= { + { ID id-GANSS-alm-keplerianNAVAlmanac CRITICALITY ignore TYPE GANSS-ALM-NAVKeplerianSet PRESENCE mandatory}| + { ID id-GANSS-alm-keplerianReducedAlmanac CRITICALITY ignore TYPE GANSS-ALM-ReducedKeplerianSet PRESENCE mandatory}| + { ID id-GANSS-alm-keplerianMidiAlmanac CRITICALITY ignore TYPE GANSS-ALM-MidiAlmanacSet PRESENCE mandatory}| + { ID id-GANSS-alm-keplerianGLONASS CRITICALITY ignore TYPE GANSS-ALM-GlonassAlmanacSet PRESENCE mandatory}| + { ID id-GANSS-alm-ecefSBASAlmanac CRITICALITY ignore TYPE GANSS-ALM-ECEFsbasAlmanacSet PRESENCE mandatory}| + { ID id-GANSS-alm-keplerianBDSAlmanac CRITICALITY ignore TYPE GANSS-ALM-BDSKeplericanset PRESENCE mandatory} + } + + GANSS-Auxiliary-Information ::= CHOICE { + ganssID1 AuxInfoGANSS-ID1, -- This choice may only be present if GANSS ID indicates Modernized GPS + ganssID3 AuxInfoGANSS-ID3, -- This choice may only be present if GANSS ID indicates GLONASS + ... + } + + GANSS-AzimuthAndElevation ::= SEQUENCE { + azimuth INTEGER(0..31), + -- applicable range of elevation is 0..7. Values 8-75 shall not be used. + elevation INTEGER(0..75), + ie-Extensions ProtocolExtensionContainer { { GANSS-AzimuthAndElevation-ExtIEs } } OPTIONAL, + ... + } + + GANSS-AzimuthAndElevation-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + { ID id-AzimuthAndElevationLSB CRITICALITY ignore EXTENSION AzimuthAndElevationLSB PRESENCE optional}, + ... + } + + GANSS-Clock-Model ::= SEQUENCE (SIZE (1..maxGANSSClockMod)) OF GANSS-SatelliteClockModelItem + + GANSS-CommonAssistanceData ::= SEQUENCE { + ganss-Reference-Time GANSS-Reference-Time OPTIONAL, + ganss-Ionospheric-Model GANSS-Ionospheric-Model OPTIONAL, + ganss-Reference-Location GANSS-Reference-Location OPTIONAL, + } + +``` + +``` + + ie-Extensions ProtocolExtensionContainer { { GANSS-CommonAssistanceData-ExtIEs } } OPTIONAL, + ... +} + +GANSS-CommonAssistanceData-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + { ID id-GANSS-Additional-Ionospheric-Model CRITICALITY ignore EXTENSION GANSS-Additional-Ionospheric-Model PRESENCE optional }| + { ID id-GANSS-Earth-Orientation-Parameters CRITICALITY ignore EXTENSION GANSS-Earth-Orientation-Parameters PRESENCE optional }, + ... +} + +GANSS-Data-Bit-Assistance ::= SEQUENCE { + ganssTod INTEGER (0..59,...), + dataBitAssistanceList GANSS-DataBitAssistanceList, + ie-Extensions ProtocolExtensionContainer { { GANSS-Data-Bit-Assistance-ExtIEs } } OPTIONAL, + ... +} + +GANSS-Data-Bit-Assistance-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-DataBitAssistanceList ::= SEQUENCE (SIZE (1..maxGANSSSat)) OF GANSS-DataBitAssistanceItem + +GANSS-DataBitAssistanceItem ::= SEQUENCE { + satId INTEGER(0..63), + dataBitAssistanceSgnList GANSS-DataBitAssistanceSgnList, + ie-Extensions ProtocolExtensionContainer { { GANSS-DataBitAssistanceItem-ExtIEs } } OPTIONAL, + ... +} + +GANSS-DataBitAssistanceItem-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-DataBitAssistanceSgnList ::= SEQUENCE (SIZE (1..maxSgnType)) OF GANSS-DataBitAssistanceSgnItem + +GANSS-DataBitAssistanceSgnItem ::= SEQUENCE { + ganss-SignalId GANSS-SignalID, + ganssDataBits BIT STRING (SIZE (1..1024)), + ie-Extensions ProtocolExtensionContainer { { GANSS-DataBitAssistanceSgnItem-ExtIEs } } OPTIONAL, + ... +} + +GANSS-DataBitAssistanceSgnItem-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` + +GANSS-Earth-Orientation-Parameters ::= SEQUENCE { + teop BIT STRING (SIZE (16)), + pmX BIT STRING (SIZE (21)), + pmXdot BIT STRING (SIZE (15)), + pmY BIT STRING (SIZE (21)), + pmYdot BIT STRING (SIZE (15)), + deltaUT1 BIT STRING (SIZE (31)), + deltaUT1dot BIT STRING (SIZE (19)), + ie-Extensions ProtocolExtensionContainer { { GANSS-Earth-Orientation-Parameters-ExtIEs } } OPTIONAL, + ... +} + +GANSS-Earth-Orientation-Parameters-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-ExtraDoppler ::= SEQUENCE { + dopplerFirstOrder INTEGER(-42..21), + dopplerUncertainty ENUMERATED{dH40, dH20, dH10, dH5, dH2-5}, + ie-Extensions ProtocolExtensionContainer { { GANSS-ExtraDoppler-ExtIEs } } OPTIONAL, + ... +} + +GANSS-ExtraDoppler-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-ExtraDopplerExtension ::= SEQUENCE { + dopplerFirstOrder INTEGER(-42..21), + dopplerUncertaintyExtension ENUMERATED{dH60, dH80, dH100, dH120, noInformation}, + ie-Extensions ProtocolExtensionContainer { { GANSS-ExtraDopplerExtension-ExtIEs } } OPTIONAL, + ... +} + +GANSS-ExtraDopplerExtension-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-GenericAssistanceDataList ::= SEQUENCE (SIZE (1..maxGANSS)) OF GANSSGenericAssistanceData + +GANSSGenericAssistanceData ::= SEQUENCE{ + ganssId GANSSID OPTIONAL, + ganss-Real-Time-Integrity GANSS-Real-Time-Integrity OPTIONAL, + ganss-DataBitAssistance GANSS-Data-Bit-Assistance OPTIONAL, + dganss-Corrections DGANSS-Corrections OPTIONAL, + ganss-AlmanacAndSatelliteHealth GANSS-AlmanacAndSatelliteHealth OPTIONAL, + ganss-ReferenceMeasurementInfo GANSS-ReferenceMeasurementInfo OPTIONAL, + ganss-UTC-Model GANSS-UTC-Model OPTIONAL, +} + +``` + +``` + +ganss-Time-Model GANSS-Time-Model OPTIONAL, +ganss-Navigation-Model GANSS-Navigation-Model OPTIONAL, +ie-Extensions ProtocolExtensionContainer { { GANSSGenericAssistance-ExtIEs } } OPTIONAL, +... +} + +GANSSGenericAssistance-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + { ID id-GANSS-Additional-Time-Models CRITICALITY ignore EXTENSION GANSS-Additional-Time-Models PRESENCE optional }| + { ID id-GANSS-Additional-Navigation-Models CRITICALITY ignore EXTENSION GANSS-Additional-Navigation-Models PRESENCE optional }| + { ID id-GANSS-Additional-UTC-Models CRITICALITY ignore EXTENSION GANSS-Additional-UTC-Models PRESENCE optional }| + { ID id-GANSS-Auxiliary-Information CRITICALITY ignore EXTENSION GANSS-Auxiliary-Information PRESENCE optional }| + -- the following IE shall be present if 'GANSSSID' in 'GANSSGenericAssistanceData' is '0' (SBAS) + { ID id-GANSS-SBAS-ID CRITICALITY ignore EXTENSION GANSS-SBAS-ID PRESENCE optional }| + { ID id-BDS-Ionospheric-Grid-Model CRITICALITY ignore EXTENSION BDS-Ionospheric-Grid-Model PRESENCE optional }| + { ID id-DBDS-Correction-Information CRITICALITY ignore EXTENSION DBDS-Correction-Information PRESENCE optional }|, + ... +} + +BDS-Ionospheric-Grid-Model ::= SEQUENCE { + bDS-Reference-Time BDS-Reference-Time, + bDS-Ionospheric-Grid-Information BDS-Ionospheric-Grid-Information, + ie-Extensions ProtocolExtensionContainer { { BDS-Ionospheric-Grid-Model-ExtIEs } } OPTIONAL, + ... +} + +BDS-Ionospheric-Grid-Model-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +BDS-Reference-Time ::= INTEGER(0..3570) -- by step of 30 + +BDS-Ionospheric-Grid-Information ::= SEQUENCE(SIZE(1.. maxIonGridInfo)) OF SEQUENCE { + iGP-number-BDS INTEGER (1..320), + vertical-Delay-BDS BIT STRING ( SIZE(9)), + gIVEI-BDS BIT STRING ( SIZE(4)), + ie-Extensions ProtocolExtensionContainer { { BDS-Ionospheric-Grid-Information-ExtIEs } } OPTIONAL, + ... +} + +BDS-Ionospheric-Grid-Information-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +DBDS-Correction-Information ::= SEQUENCE { + bDS-Reference-Time BDS-Reference-Time, + dBDS-Information DBDS-Information, + ie-Extensions ProtocolExtensionContainer { { DBDS-Correction-Information-ExtIEs } } OPTIONAL, + ... +} + +``` + +``` +DBDS-Correction-Information-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +DBDS-Information ::= SEQUENCE (SIZE (1..maxSgnType)) OF SEQUENCE { + dBDS-Signal-ID GANSSID OPTIONAL, + dGANSS-Signal-Information dGANSS-Signal-Information, + ie-Extensions ProtocolExtensionContainer { { DBDS-Information-ExtIEs } } OPTIONAL, + ... +} + +DBDS-Information-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +dGANSS-Signal-Information ::= SEQUENCE (SIZE (1..maxGANSSSat)) OF SEQUENCE { + sat-ID-BDS INTEGER (0..63), + uDREI-BDS INTEGER (0..15), + rURAI-BDS INTEGER (0..15), + delta-t-BDS BIT STRING (SIZE (13)), + ie-Extensions ProtocolExtensionContainer { { dGANSS-Signal-Information-ExtIEs } } OPTIONAL, + ... +} + +dGANSS-Signal-Information-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-GenericMeasurementInfo ::= SEQUENCE (SIZE (1..maxGANSS)) OF SEQUENCE { + ganssId GANSSID OPTIONAL, + ganssMeasurementSignalList GANSSMeasurementSignalList, + ie-Extensions ProtocolExtensionContainer { { GANSS-GenericMeasurementInfo-ExtIEs } } OPTIONAL, + ... +} + +GANSS-GenericMeasurementInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSSID ::= SEQUENCE { + ganss-ID INTEGER (0..7), + ie-Extensions ProtocolExtensionContainer { { GANSSID-ExtIEs } } OPTIONAL, + ... +} + +GANSSID-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` + +GANSSMeasurementSignalList ::= SEQUENCE (SIZE (1..maxSgnType)) OF SEQUENCE { + ganssSignalId GANSS-SignalID OPTIONAL, + ganssCodePhaseAmbiguity INTEGER (0..31) OPTIONAL, + ganssMeasurementParameters GANSS-MeasurementParameters, + ie-Extensions ProtocolExtensionContainer { { GANSSMeasurementSignalList-ExtIEs } } OPTIONAL, + ... +} + +GANSSMeasurementSignalList-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + {ID id-ganssCodePhaseAmbiguityExt CRITICALITY ignore EXTENSION GanssCodePhaseAmbiguityExt PRESENCE optional}, + ... +} + +GanssCodePhaseAmbiguityExt ::= SEQUENCE { + ganssCodePhaseAmbiguity-ext INTEGER (32..127), + ie-Extensions ProtocolExtensionContainer { { GanssCodePhaseAmbiguityExt-ExtIEs } } OPTIONAL, + ... +} + +GanssCodePhaseAmbiguityExt-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-Ionospheric-Model ::= SEQUENCE { + alpha-zero-ionos BIT STRING (SIZE (11)), + alpha-one-ionos BIT STRING (SIZE (11)), + alpha-two-ionos BIT STRING (SIZE (14)), + gANSS-IonosphereRegionalStormFlags GANSS-IonosphereRegionalStormFlags OPTIONAL, + ie-Extensions ProtocolExtensionContainer { { GANSS-Ionospheric-Model-ExtIEs } } OPTIONAL, + ... +} + +GANSS-Ionospheric-Model-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-IonosphereRegionalStormFlags ::= SEQUENCE { + storm-flag-one BOOLEAN, + storm-flag-two BOOLEAN, + storm-flag-three BOOLEAN, + storm-flag-four BOOLEAN, + storm-flag-five BOOLEAN, + ie-Extensions ProtocolExtensionContainer { { GANSS-IonosphereRegionalStormFlags-ExtIEs } } OPTIONAL, + ... +} + +``` + +``` + +GANSS-IonosphereRegionalStormFlags-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-KeplerianParametersAlm ::= SEQUENCE { + t-oa INTEGER(0..1023), + iod-a INTEGER(0..15), + gANSS-SatelliteInformationKP GANSS-SatelliteInformationKP, + ie-Extensions ProtocolExtensionContainer { { GANSS-KeplerianParametersAlm-ExtIEs } } OPTIONAL, + ... +} + +GANSS-KeplerianParametersAlm-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-KeplerianParametersOrb ::= SEQUENCE { + toe-nav BIT STRING (SIZE (14)), + ganss-omega-nav BIT STRING (SIZE (32)), + delta-n-nav BIT STRING (SIZE (16)), + m-zero-nav BIT STRING (SIZE (32)), + omegadot-nav BIT STRING (SIZE (24)), + ganss-e-nav BIT STRING (SIZE (32)), + idot-nav BIT STRING (SIZE (14)), + a-sqrt-nav BIT STRING (SIZE (32)), + i-zero-nav BIT STRING (SIZE (32)), + omega-zero-nav BIT STRING (SIZE (32)), + c-rs-nav BIT STRING (SIZE (16)), + c-is-nav BIT STRING (SIZE (16)), + c-us-nav BIT STRING (SIZE (16)), + c-rc-nav BIT STRING (SIZE (16)), + c-ic-nav BIT STRING (SIZE (16)), + c-uc-nav BIT STRING (SIZE (16)), + ie-Extensions ProtocolExtensionContainer { { GANSS-KeplerianParametersOrb-ExtIEs } } OPTIONAL, + ... +} + +GANSS-KeplerianParametersOrb-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-MeasurementParameters ::= SEQUENCE(SIZE(1..maxGANSSSat)) OF GANSS-MeasurementParametersItem + +GANSS-MeasurementParametersItem ::= SEQUENCE { + satId INTEGER(0..63), + cToNzero INTEGER(0..63), +} + +``` + +Error: + +266 + +Error: Reference source not found + +``` + multipathIndicator ENUMERATED{nM, low, medium, high}, + carrierQualityIndication BIT STRING(SIZE(2)) OPTIONAL, + ganssCodePhase INTEGER(0..2097151), + ganssIntegerCodePhase INTEGER(0..63) OPTIONAL, + codePhaseRmsError INTEGER(0..63), + doppler INTEGER(-32768..32767), + adr INTEGER(0..33554431) OPTIONAL, + ie-Extensions ProtocolExtensionContainer { { GANSS-MeasurementParametersItem-ExtIEs } } OPTIONAL, + ... +} + +GANSS-MeasurementParametersItem-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + {ID id-ganssIntegerCodePhaseExt CRITICALITY ignore EXTENSION GanssIntegerCodePhaseExt PRESENCE optional}, + ... +} + +GanssIntegerCodePhaseExt ::= SEQUENCE { + ganssIntegerCodePhase-ext INTEGER (64..127), + ie-Extensions ProtocolExtensionContainer { { GanssIntegerCodePhaseExt-ExtIEs } } OPTIONAL, + ... +} + +GanssIntegerCodePhaseExt-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-MeasuredResultsList ::= SEQUENCE (SIZE (1..maxNrOfSets)) OF GANSS-MeasuredResults + +GANSS-MeasuredResults ::= SEQUENCE { + referenceTime CHOICE { + utranReferenceTime UTRAN-GANSSReferenceTimeUL, + ganssReferenceTimeOnly GANSS-ReferenceTimeOnly, + ... + }, + ganssGenericMeasurementInfo GANSS-GenericMeasurementInfo, + ie-Extensions ProtocolExtensionContainer { { GANSS-MeasuredResults-ExtIEs } } OPTIONAL, + ... +} + +GANSS-MeasuredResults-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-Navigation-Model ::= SEQUENCE { + non-broadcastIndication ENUMERATED{true} OPTIONAL, + ganssSatInfoNav GANSS-Sat-Info-Nav, + ie-Extensions ProtocolExtensionContainer { { GANSS-Navigation-Model-ExtIEs } } OPTIONAL, + ... +} +``` + +Error: + +267 + +Error: Reference source not found + +``` + - + } + + GANSS-Navigation-Model-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + GANSS-Orbit-Model ::= CHOICE { + gANSS-keplerianParameters GANSS-KeplerianParametersOrb, + ... + } + + GANSS-Real-Time-Integrity ::= SEQUENCE (SIZE (1..maxGANSSSat)) OF GANSS-RealTimeInformationItem + + GANSS-RealTimeInformationItem ::= SEQUENCE { + bad-ganss-satId INTEGER(0..63), + bad-ganss-signalId BIT STRING(SIZE(8)) OPTIONAL, + ie-Extensions ProtocolExtensionContainer { { GANSS-RealTimeInformationItem-ExtIEs } } OPTIONAL, + ... + } + + GANSS-RealTimeInformationItem-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + GANSS-Reference-Location ::= SEQUENCE { + ue-PositionEstimate UE-PositionEstimate, + iE-Extensions ProtocolExtensionContainer { { GANSS-Reference-Location-ExtIEs } } OPTIONAL, + ... + } + + GANSS-Reference-Location-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + GANSS-ReferenceMeasurementInfo ::= SEQUENCE { + ganssSignalId GANSS-SignalID OPTIONAL, + satelliteInformation GANSS-SatelliteInformation, + ie-Extensions ProtocolExtensionContainer { { GANSS-ReferenceMeasurementInfo-ExtIEs } } OPTIONAL, + ... + } + + GANSS-ReferenceMeasurementInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { +``` + +``` + + {ID id-GANSS-Confidence CRITICALITY ignore EXTENSION Confidence PRESENCE optional}, + ... +} + +GANSS-Reference-Time ::= SEQUENCE { + ganssDay INTEGER(0..8191) OPTIONAL, + ganssTod INTEGER(0..86399), + ganssTodUncertainty INTEGER(0..127) OPTIONAL, + ganssTimeId GANSSID OPTIONAL, + utran-ganssreferenceTime UTRAN-GANSSReferenceTimeDL OPTIONAL, + tutran-ganss-driftRate TUTRAN-GANSS-DriftRate OPTIONAL, + ie-Extensions ProtocolExtensionContainer { { GANSS-Reference-Time-ExtIEs } } OPTIONAL, + ... +} + +GANSS-Reference-Time-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + {ID id-GANSS-Day-Cycle CRITICALITY ignore EXTENSION GANSS-Day-Cycle PRESENCE optional}, + ... +} + +GANSS-Day-Cycle ::= INTEGER(0..7) + +GANSS-ReferenceTimeOnly ::= SEQUENCE { + gANSS-tod INTEGER(0..3599999), + gANSS-timeId GANSSID OPTIONAL, + gANSS-TimeUncertainty INTEGER(0..127) OPTIONAL, + ie-Extensions ProtocolExtensionContainer { { GANSS-ReferenceTimeOnly-ExtIEs } } OPTIONAL, + ... +} + +GANSS-ReferenceTimeOnly-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-SatelliteClockModelItem ::= SEQUENCE { + t-oc BIT STRING (SIZE(14)), + a-i2 BIT STRING (SIZE(6)), + a-i1 BIT STRING (SIZE(21)), + a-i0 BIT STRING (SIZE(31)), + t-gd BIT STRING (SIZE(10)) OPTIONAL, + sisa BIT STRING (SIZE(8)), + model-id INTEGER(0..3) OPTIONAL, + ie-Extensions ProtocolExtensionContainer { { GANSS-SatelliteClockModelItem-ExtIEs } } OPTIONAL, + ... +} + +GANSS-SatelliteClockModelItem-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + +``` + +``` + + ... + } + + GANSS-SatelliteInformation ::= SEQUENCE (SIZE (1..maxGANSSSat)) OF GANSS-SatelliteInformationItem + + GANSS-SatelliteInformationItem ::= SEQUENCE { + ganssSatId INTEGER (0..63), + dopplerZeroOrder INTEGER (-2048..2047), + extraDoppler GANSS-ExtraDoppler OPTIONAL, + codePhase INTEGER (0..1023), + integerCodePhase INTEGER (0..127), + codePhaseSearchWindow INTEGER (0..31), + azimuthAndElevation GANSS-AzimuthAndElevation OPTIONAL, + ie-Extensions ProtocolExtensionContainer { { GANSS-SatelliteInformationItem-ExtIEs } } OPTIONAL, + ... + } + + GANSS-SatelliteInformationItem-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + {ID id-GANSS-ExtraDopplerExtension CRITICALITY ignore EXTENSION GANSS-ExtraDopplerExtension PRESENCE optional}, + ... + } + + GANSS-SatelliteInformationKP ::= SEQUENCE (SIZE (1..maxGANSSSatAlmanac)) OF GANSS-SatelliteInformationKPItem + + GANSS-SatelliteInformationKPItem ::= SEQUENCE { + satId INTEGER (0..63), + ganss-e-alm BIT STRING (SIZE (11)), + ganss-delta-I-alm BIT STRING (SIZE (11)), + ganss-omegadot-alm BIT STRING (SIZE (11)), + ganss-svStatusINAV-alm BIT STRING (SIZE (4)), + ganss-svStatusFNAV-alm BIT STRING (SIZE (2)) OPTIONAL, + ganss-delta-a-sqrt-alm BIT STRING (SIZE (13)), + ganss-omegazero-alm BIT STRING (SIZE (16)), + ganss-m-zero-alm BIT STRING (SIZE (16)), + ganss-omega-alm BIT STRING (SIZE (16)), + ganss-af-zero-alm BIT STRING (SIZE (16)), + ganss-af-one-alm BIT STRING (SIZE (13)), + ie-Extensions ProtocolExtensionContainer { { GANSS-SatelliteInformationKPItem-ExtIEs } } OPTIONAL, + ... + } + + GANSS-SatelliteInformationKPItem-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + GANSS-SAT-Info-Almanac-GLOkpList ::= SEQUENCE (SIZE (1..maxGANSSSatAlmanac)) OF GANSS-SAT-Info-Almanac-GLOkp + +``` + +``` +GANSS-SAT-Info-Almanac-GLOkp ::= SEQUENCE { + gloAlmNA BIT STRING (SIZE (11)), + gloAlmNA BIT STRING (SIZE (5)), + gloAlmHA BIT STRING (SIZE (5)), + gloAlmLambdaA BIT STRING (SIZE (21)), + gloAlmTlambdaA BIT STRING (SIZE (21)), + gloAlmDeltaIA BIT STRING (SIZE (18)), + gloAkmDeltaTA BIT STRING (SIZE (22)), + gloAlmDeltaTdotA BIT STRING (SIZE (7)), + gloAlmEpsilonA BIT STRING (SIZE (15)), + gloAlmOmegaA BIT STRING (SIZE (16)), + gloAlmTauA BIT STRING (SIZE (10)), + gloAlmCA BIT STRING (SIZE (1)), + gloAlmMA BIT STRING (SIZE (2)) + OPTIONAL, + ie-Extensions ProtocolExtensionContainer { { GANSS-SAT-Info-Almanac-GLOkp-ExtIEs } } + ... +} + +GANSS-SAT-Info-Almanac-GLOkp-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-SAT-Info-Almanac-MIDIkpList ::= SEQUENCE (SIZE (1.. maxGANSSSatAlmanac)) OF GANSS-SAT-Info-Almanac-MIDIkp + +GANSS-SAT-Info-Almanac-MIDIkp ::= SEQUENCE { + svID INTEGER (0..63), + midiAlmE BIT STRING (SIZE (11)), + midiAlmDeltaI BIT STRING (SIZE (11)), + midiAlmOmegaDot BIT STRING (SIZE (11)), + midiAlmSqrtA BIT STRING (SIZE (17)), + midiAlmOmega0 BIT STRING (SIZE (16)), + midiAlmOmega BIT STRING (SIZE (16)), + midiAlmMo BIT STRING (SIZE (16)), + midiAlmaf0 BIT STRING (SIZE (11)), + midiAlmaf1 BIT STRING (SIZE (10)), + midiAlmL1Health BIT STRING (SIZE (1)), + midiAlmL2Health BIT STRING (SIZE (1)), + midiAlmL5Health BIT STRING (SIZE (1)), + ie-Extensions ProtocolExtensionContainer { { GANSS-SAT-Info-Almanac-MIDIkp-ExtIEs } } + ... +} + +GANSS-SAT-Info-Almanac-MIDIkp-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-SAT-Info-Almanac-NAVkpList ::= SEQUENCE (SIZE (1.. maxGANSSSatAlmanac)) OF GANSS-SAT-Info-Almanac-NAVkp +``` + +``` +GANSS-SAT-Info-Almanac-NAVkp ::= SEQUENCE { + svID INTEGER(0..63), + navAlmE BIT STRING (SIZE (16)), + navAlmDeltaI BIT STRING (SIZE (16)), + navAlmOMEGADOT BIT STRING (SIZE (16)), + navAlmSVHealth BIT STRING (SIZE (8)), + navAlmSqrtA BIT STRING (SIZE (24)), + navAlmOMEGAO BIT STRING (SIZE (24)), + navAlmOmega BIT STRING (SIZE (24)), + navAlmMo BIT STRING (SIZE (24)), + navAlmaf0 BIT STRING (SIZE (11)), + navAlmaf1 BIT STRING (SIZE (11)), + ie-Extensions ProtocolExtensionContainer { { GANSS-SAT-Info-Almanac-NAVkp-ExtIEs } } + ... +} OPTIONAL, + +GANSS-SAT-Info-Almanac-NAVkp-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-SAT-Info-Almanac-REDkpList ::= SEQUENCE (SIZE (1.. maxGANSSSatAlmanac)) OF GANSS-SAT-Info-Almanac-REDkp + +GANSS-SAT-Info-Almanac-REDkp ::= SEQUENCE { + svID INTEGER(0..63), + redAlmDeltaA BIT STRING (SIZE (8)), + redAlmOmega0 BIT STRING (SIZE (7)), + redAlmPhi0 BIT STRING (SIZE (7)), + redAlmL1Health BIT STRING (SIZE (1)), + redAlmL2Health BIT STRING (SIZE (1)), + redAlmL5Health BIT STRING (SIZE (1)), + ie-Extensions ProtocolExtensionContainer { { GANSS-SAT-Info-Almanac-REDkp-ExtIEs } } + ... +} OPTIONAL, + +GANSS-SAT-Info-Almanac-REDkp-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-SAT-Info-Almanac-SBASecfList ::= SEQUENCE (SIZE (1.. maxGANSSSatAlmanac)) OF GANSS-SAT-Info-Almanac-SBASecf + +GANSS-SAT-Info-Almanac-SBASecf ::= SEQUENCE { + sbasAlmDataID BIT STRING (SIZE(2)), + svID INTEGER(0..63), + sbasAlmHealth BIT STRING (SIZE(8)), + sbasAlmXg BIT STRING (SIZE(15)), + sbasAlmYg BIT STRING (SIZE(15)), + sbasAlmZg BIT STRING (SIZE(9)), +``` + +``` + + sbasAlmXgDot BIT STRING (SIZE(3)), + sbasAlmYgDot BIT STRING (SIZE(3)), + sbasAlmZgDot BIT STRING (SIZE(4)), + sbasAlmTo BIT STRING (SIZE(11)), + ie-Extensions ProtocolExtensionContainer { { GANSS-SAT-Info-Almanac-SBASecf-ExtIEs } } OPTIONAL, + ... +} + +GANSS-SAT-Info-Almanac-SBASecf-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +Ganss-Sat-Info-AddNavList ::= SEQUENCE (SIZE (1..maxGANSSSat)) OF SEQUENCE { + satId INTEGER (0..63), + svHealth BIT STRING (SIZE (6)), + iod BIT STRING (SIZE (11)), + ganssAddClockModels GANSS-AddClockModels, + ganssAddOrbitModels GANSS-AddOrbitModels, + ie-Extensions ProtocolExtensionContainer { { Ganss-Sat-Info-AddNavList-ExtIEs } } OPTIONAL, + ... +} + +Ganss-Sat-Info-AddNavList-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-Sat-Info-Nav ::= SEQUENCE (SIZE (1..maxGANSSSat)) OF SEQUENCE { + satId INTEGER (0..63), + svHealth BIT STRING (SIZE(9)), + iod BIT STRING (SIZE(10)), + ganssClockModel GANSS-Clock-Model, + ganssOrbitModel GANSS-Orbit-Model, + ie-Extensions ProtocolExtensionContainer { { GANSS-Sat-Info-Nav-ExtIEs } } OPTIONAL, + ... +} + +GANSS-Sat-Info-Nav-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-SignalID ::= SEQUENCE { + ganssSignalID INTEGER (0..3, ..., 4..7), + ie-Extensions ProtocolExtensionContainer { { GANSS-SignalID-ExtIEs } } OPTIONAL, + ... +} + +GANSS-SignalID-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + +``` + +``` + + ... + } + + GANSS-StatusHealth ::= ENUMERATED { + udre-scale-1dot0, + udre-scale-0dot75, + udre-scale-0dot5, + udre-scale-0dot3, + udre-scale-0dot2, + udre-scale-0dot1, + no-data, + invalid-data + } + + GANSS-Time-Model ::= SEQUENCE { + ganss-time-model-refTime INTEGER(0..37799), + ganss-t-a0 INTEGER(-2147483648..2147483647), + ganss-t-a1 INTEGER(-8388608..8388607) OPTIONAL, + ganss-t-a2 INTEGER(-64..63) OPTIONAL, + gnss-to-id ENUMERATED{gps,...,galileo,qzss,glonass,bds}, + ganss-wk-number INTEGER(0..8191) OPTIONAL, + ie-Extensions ProtocolExtensionContainer { { GANSS-Time-Model-ExtIEs } } OPTIONAL, + ... + } + + GANSS-Time-Model-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + {ID id-ganss-Delta-T CRITICALITY ignore EXTENSION GANSS-Delta-T PRESENCE optional}, + ... + } + + GANSS-Delta-T ::= INTEGER(-128..127) + + GANSS-UTRAN-TimeRelationshipUncertainty ::= ENUMERATED { + gANSS-UTRAN-TRU-50nano, + gANSS-UTRAN-TRU-500nano, + gANSS-UTRAN-TRU-1micro, + gANSS-UTRAN-TRU-10micro, + gANSS-UTRAN-TRU-1milli, + gANSS-UTRAN-TRU-10milli, + gANSS-UTRAN-TRU-100milli, + gANSS-UTRAN-TRU-unreliable, + ... + } + +``` + +``` + +GANSS-UTRAN-TRU ::= SEQUENCE { + gANSS-UTRAN-TimeRelationshipUncertainty GANSS-UTRAN-TimeRelationshipUncertainty, + ganssId GANSSID + OPTIONAL, + ie-Extensions ProtocolExtensionContainer { { GANSS-UTRAN-TRU-ExtIEs } } OPTIONAL, + ... +} + +GANSS-UTRAN-TRU-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-UTC-Model ::= SEQUENCE { + a-one-utc BIT STRING (SIZE (24)), + a-zero-utc BIT STRING (SIZE (32)), + t-ot-utc BIT STRING (SIZE (8)), + w-n-t-utc BIT STRING (SIZE (8)), + delta-t-ls-utc BIT STRING (SIZE (8)), + w-n-lsf-utc BIT STRING (SIZE (8)), + dn-utc BIT STRING (SIZE (8)), + delta-t-lsf-utc BIT STRING (SIZE (8)), + ie-Extensions ProtocolExtensionContainer { { GANSS-UTC-Model-ExtIEs } } OPTIONAL, + ... +} + +GANSS-UTC-Model-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +TUTRAN-GANSS-DriftRate ::= ENUMERATED { + uTRAN-GANSSDrift0, uTRAN-GANSSDrift1, uTRAN-GANSSDrift2, + uTRAN-GANSSDrift5, uTRAN-GANSSDrift10, uTRAN-GANSSDrift15, + uTRAN-GANSSDrift25, uTRAN-GANSSDrift50, uTRAN-GANSSDrift-1, + uTRAN-GANSSDrift-2, uTRAN-GANSSDrift-5, uTRAN-GANSSDrift-10, + uTRAN-GANSSDrift-15, uTRAN-GANSSDrift-25, uTRAN-GANSSDrift-50, + ... +} + +GLONASSclockModel ::= SEQUENCE { + gloTau BIT STRING (SIZE (22)), + gloGamma BIT STRING (SIZE (11)), + gloDeltaTau BIT STRING (SIZE (5)) OPTIONAL, + ie-Extensions ProtocolExtensionContainer { { GLONASSclockModel-ExtIEs } } OPTIONAL, + ... +} + +GLONASSclockModel-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + +``` + +``` + ... +} + +NAVclockModel ::= SEQUENCE { + navToc BIT STRING (SIZE (16)), + navaf2 BIT STRING (SIZE (8)), + navaf1 BIT STRING (SIZE (16)), + navaf0 BIT STRING (SIZE (22)), + navTgd BIT STRING (SIZE (8)), + ie-Extensions ProtocolExtensionContainer { { NAVclockModel-ExtIEs } } OPTIONAL, + ... +} + +NAVclockModel-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +NavModel-CNAVKeplerianSet ::= SEQUENCE { + cnavTop BIT STRING (SIZE (11)), + cnavURAindex BIT STRING (SIZE (5)), + cnavDeltaA BIT STRING (SIZE (26)), + cnavAdot BIT STRING (SIZE (25)), + cnavDeltaNo BIT STRING (SIZE (17)), + cnavDeltaNoDot BIT STRING (SIZE (23)), + cnavMo BIT STRING (SIZE (33)), + cnavE BIT STRING (SIZE (33)), + cnavOmega BIT STRING (SIZE (33)), + cnavOMEGA0 BIT STRING (SIZE (33)), + cnavDeltaOmegaDot BIT STRING (SIZE (17)), + cnavIo BIT STRING (SIZE (33)), + cnavIoDot BIT STRING (SIZE (15)), + cnavCis BIT STRING (SIZE (16)), + cnavCic BIT STRING (SIZE (16)), + cnavCrs BIT STRING (SIZE (24)), + cnavCrc BIT STRING (SIZE (24)), + cnavCus BIT STRING (SIZE (21)), + cnavCuc BIT STRING (SIZE (21)), + ie-Extensions ProtocolExtensionContainer { { NavModel-CNAVKeplerianSet-ExtIEs } } OPTIONAL, + ... +} + +NavModel-CNAVKeplerianSet-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +NavModel-GLONASSecf ::= SEQUENCE { + gloEn BIT STRING (SIZE (5)), + gloP1 BIT STRING (SIZE (2)), + gloP2 BIT STRING (SIZE (1)), + gloM BIT STRING (SIZE (2)) +} +``` + +OPTIONAL, + +``` + + gloX BIT STRING (SIZE (27)), + gloXdot BIT STRING (SIZE (24)), + gloXdotdot BIT STRING (SIZE (5)), + gloY BIT STRING (SIZE (27)), + gloYdot BIT STRING (SIZE (24)), + gloYdotdot BIT STRING (SIZE (5)), + gloZ BIT STRING (SIZE (27)), + gloZdot BIT STRING (SIZE (24)), + gloZdotdot BIT STRING (SIZE (5)), + ie-Extensions ProtocolExtensionContainer { { NavModel-GLONASSecf-ExtIEs } } OPTIONAL, + ... +} + +NavModel-GLONASSecf-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +NavModel-NAVKeplerianSet ::= SEQUENCE { + navURA BIT STRING (SIZE (4)), + navFitFlag BIT STRING (SIZE (1)), + navToe BIT STRING (SIZE (16)), + navOmega BIT STRING (SIZE (32)), + navDeltaN BIT STRING (SIZE (16)), + navM0 BIT STRING (SIZE (32)), + navOmegaADot BIT STRING (SIZE (24)), + navE BIT STRING (SIZE (32)), + navIDot BIT STRING (SIZE (14)), + navAPowerHalf BIT STRING (SIZE (32)), + navI0 BIT STRING (SIZE (32)), + navOmegaA0 BIT STRING (SIZE (32)), + navCrs BIT STRING (SIZE (16)), + navCis BIT STRING (SIZE (16)), + navCus BIT STRING (SIZE (16)), + navCrc BIT STRING (SIZE (16)), + navCic BIT STRING (SIZE (16)), + navCuc BIT STRING (SIZE (16)), + ie-Extensions ProtocolExtensionContainer { { NavModel-NAVKeplerianSet-ExtIEs } } OPTIONAL, + ... +} + +NavModel-NAVKeplerianSet-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +NavModel-SBASSecf ::= SEQUENCE { + -- the following IE shall be present if 'SBASclockModel' in 'GANSs-AddClockModels' is not included in 'Ganss-Sat-Info-AddNavList' + sbasTo BIT STRING (SIZE (13)) OPTIONAL, + sbasAccuracy BIT STRING (SIZE (4)), + sbasXg BIT STRING (SIZE (30)), + sbasYg BIT STRING (SIZE (30)), + sbasZg BIT STRING (SIZE (25)), +} + +``` + +``` + sbasXgDot BIT STRING (SIZE (17)), + sbasYgDot BIT STRING (SIZE (17)), + sbasZgDot BIT STRING (SIZE (18)), + sbasXgDotDot BIT STRING (SIZE (10)), + sbagYgDotDot BIT STRING (SIZE (10)), + sbasZgDotDot BIT STRING (SIZE (10)), + ie-Extensions ProtocolExtensionContainer { { NavModel-SBASecf-ExtIEs } } OPTIONAL, + ... +} + +NavModel-SBASecf-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +NavModel-BDSKeplerianSet ::= SEQUENCE { + uRAIndex-BDS BIT STRING (SIZE (4)), + tOA-BDS BIT STRING (SIZE (17)), + a1-2-BDS BIT STRING (SIZE (32)), + e-BDS BIT STRING (SIZE (32)), + oMG-BDS BIT STRING (SIZE (32)), + dLTn-BDS BIT STRING (SIZE (16)), + m0-BDS BIT STRING (SIZE (32)), + oMG0-BDS BIT STRING (SIZE (32)), + oMGdot-BDS BIT STRING (SIZE (24)), + i0-BDS BIT STRING (SIZE (32)), + iDOT-BDS BIT STRING (SIZE (14)), + cuc-BDS BIT STRING (SIZE (18)), + cus-BDS BIT STRING (SIZE (18)), + crc-BDS BIT STRING (SIZE (18)), + crs-BDS BIT STRING (SIZE (18)), + cic-BDS BIT STRING (SIZE (18)), + cis-BDS BIT STRING (SIZE (18)), + aODE-BDS BIT STRING (SIZE (5)), + ie-Extensions ProtocolExtensionContainer { { NavModel-BDSKeplerianSet-ExtIEs } } OPTIONAL, + ... +} + +NavModel-BDSKeplerianSet-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +SBASclockModel ::= SEQUENCE { + sbasTo BIT STRING (SIZE (13)), + sbasAgfo BIT STRING (SIZE (12)), + sbasAgfl BIT STRING (SIZE (8)), + ie-Extensions ProtocolExtensionContainer { { SBASclockModel-ExtIEs } } OPTIONAL, + ... +} + +SBASclockModel-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` + } + + BDSClockModel ::= SEQUENCE { + toc-BDS BIT STRING (SIZE (17) ), + a0-BDS BIT STRING (SIZE (24) ), + a1-BDS BIT STRING (SIZE (22) ), + a2-BDS BIT STRING (SIZE (11) ), + tGD1-BDS BIT STRING (SIZE (10) ), + aODC-BDS BIT STRING (SIZE (5) ), + ie-Extensions ProtocolExtensionContainer { { BDSClockModel-ExtIEs } } OPTIONAL, + ... + } + + BDSClockModel-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + UTCmodelSet1 ::= SEQUENCE { + utcA0 BIT STRING (SIZE(16)), + utcA1 BIT STRING (SIZE(13)), + utcA2 BIT STRING (SIZE(7)), + utcDeltaTls BIT STRING (SIZE(8)), + utcTot BIT STRING (SIZE(16)), + utcWNNot BIT STRING (SIZE(13)), + utcWNlsf BIT STRING (SIZE(8)), + utcDN BIT STRING (SIZE(4)), + utcDeltaTlsf BIT STRING (SIZE(8)), + ie-Extensions ProtocolExtensionContainer { { UTCmodelSet1-ExtIEs } } OPTIONAL, + ... + } + + UTCmodelSet1-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + UTCmodelSet2 ::= SEQUENCE { + nA BIT STRING (SIZE(11)), + tauC BIT STRING (SIZE(32)), + deltaUT1 DeltaUT1 OPTIONAL, + kp BIT STRING (SIZE(2)) OPTIONAL, + ie-Extensions ProtocolExtensionContainer { { UTCmodelSet2-ExtIEs } } OPTIONAL, + ... + } + + UTCmodelSet2-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + UTCmodelSet3 ::= SEQUENCE { + utcA1wnt BIT STRING (SIZE(24)), + utcA0wnt BIT STRING (SIZE(32)), +``` + +``` + + utcTot BIT STRING (SIZE(8)), + utcWNt BIT STRING (SIZE(8)), + utcDeltaTls BIT STRING (SIZE(8)), + utcWNlsf BIT STRING (SIZE(8)), + utcDN BIT STRING (SIZE(8)), + utcDeltaTlsf BIT STRING (SIZE(8)), + utcStandardID BIT STRING (SIZE(3)), + ie-Extensions ProtocolExtensionContainer { { UTCmodelSet3-ExtIEs } } OPTIONAL, + ... + } + + UTCmodelSet3-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + UTCmodelSet4 ::= SEQUENCE { + utca0-BDS BIT STRING (SIZE(32)), + utcal-BDS BIT STRING (SIZE(24)), + utcDeltaTls-BDS BIT STRING (SIZE(8)), + utcWNt BIT STRING (SIZE(8)), + utcDeltaTls BIT STRING (SIZE(8)), + utcWNlsf-BDS BIT STRING (SIZE(8)), + utcDN-BDS BIT STRING (SIZE(8)), + utcDeltaTlsf-BDS BIT STRING (SIZE(8)), + ie-Extensions ProtocolExtensionContainer { { UTCmodelSet4-ExtIEs } } OPTIONAL, + ... + } + + UTCmodelSet4-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + UTRAN-GANSSReferenceTimeDL ::= SEQUENCE { + utran-GANSSTimingOfCellFrames INTEGER(0..3999999), + uC-ID UC-ID + OPTIONAL, + referenceSfn INTEGER(0..4095), + ie-Extensions ProtocolExtensionContainer { { UTRAN-GANSSReferenceTimeDL-ExtIEs } } OPTIONAL, + ... + } + + UTRAN-GANSSReferenceTimeDL-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + UTRAN-GANSSReferenceTimeUL ::= SEQUENCE { + ue-GANSSTimingOfCellFrames INTEGER(0..345599999999), + gANSS-TimeId GANSSID OPTIONAL, + gANSS-TimeUncertainty INTEGER(0..127) OPTIONAL, + uC-ID UC-ID, + referenceSfn INTEGER(0..4095), + } + +``` + +``` + + ie-Extensions ProtocolExtensionContainer { { UTRAN-GANSSReferenceTimeUL-ExtIEs } } OPTIONAL, + ... + } + + UTRAN-GANSSReferenceTimeUL-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + -- ***** + -- + -- GPS Almanac and Satellite Health + -- + -- ***** + + GPS-AlmanacAndSatelliteHealth ::= SEQUENCE { + wn-a BIT STRING (SIZE (8)), + almanacSatInfoList AlmanacSatInfoList, + svGlobalHealth BIT STRING (SIZE (364)) OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { GPS-AlmanacAndSatelliteHealth-ExtIEs } } OPTIONAL, + ... + } + + GPS-AlmanacAndSatelliteHealth-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + {ID id-completeAlmanacProvided CRITICALITY ignore EXTENSION CompleteAlmanacProvided PRESENCE optional}, + ... + } + + CompleteAlmanacProvided ::= BOOLEAN + + AlmanacSatInfoList ::= SEQUENCE (SIZE (1..maxSatAlmanac)) OF + AlmanacSatInfo + + AlmanacSatInfo ::= SEQUENCE { + dataID BIT STRING (SIZE (2)), + satID INTEGER (0..63), + e BIT STRING (SIZE (16)), + t-oa BIT STRING (SIZE (8)), + deltaI BIT STRING (SIZE (16)), + omegaDot BIT STRING (SIZE (16)), + satHealth BIT STRING (SIZE (8)), + a-Sqrt BIT STRING (SIZE (24)), + omega0 BIT STRING (SIZE (24)), + m0 BIT STRING (SIZE (24)), + omega BIT STRING (SIZE (24)), + af0 BIT STRING (SIZE (11)), + af1 BIT STRING (SIZE (11)), + iE-Extensions ProtocolExtensionContainer { { AlmanacSatInfo-ExtIEs } } OPTIONAL, + ... + } + +``` + +``` + +- +} + +AlmanacSatInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- GPS Clock And Ephemeris Parameters +-- +-- ***** + +GPS-ClockAndEphemerisParameters ::= SEQUENCE { + codeOnL2 BIT STRING (SIZE (2)), + uraIndex BIT STRING (SIZE (4)), + satHealth BIT STRING (SIZE (6)), + iodc BIT STRING (SIZE (10)), + l2Pflag BIT STRING (SIZE (1)), + sflRevd SubFrame1Reserved, + t-GD BIT STRING (SIZE (8)), + t-oc BIT STRING (SIZE (16)), + af2 BIT STRING (SIZE (8)), + af1 BIT STRING (SIZE (16)), + af0 BIT STRING (SIZE (22)), + c-rs BIT STRING (SIZE (16)), + delta-n BIT STRING (SIZE (16)), + m0 BIT STRING (SIZE (32)), + c-uc BIT STRING (SIZE (16)), + e BIT STRING (SIZE (32)), + c-us BIT STRING (SIZE (16)), + a-Sqrt BIT STRING (SIZE (32)), + t-oe BIT STRING (SIZE (16)), + fitInterval BIT STRING (SIZE (1)), + aodo BIT STRING (SIZE (5)), + c-ic BIT STRING (SIZE (16)), + omega0 BIT STRING (SIZE (32)), + c-is BIT STRING (SIZE (16)), + i0 BIT STRING (SIZE (32)), + c-rc BIT STRING (SIZE (16)), + omega BIT STRING (SIZE (32)), + omegaDot BIT STRING (SIZE (24)), + iDot BIT STRING (SIZE (14)), + iE-Extensions ProtocolExtensionContainer { { GPS-ClockAndEphemerisParameters-ExtIEs } } OPTIONAL, + ... +} + +GPS-ClockAndEphemerisParameters-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +SubFrame1Reserved ::= SEQUENCE { + reserved1 BIT STRING (SIZE (23)), + reserved2 BIT STRING (SIZE (24)), + reserved3 BIT STRING (SIZE (24)), + reserved4 BIT STRING (SIZE (16)) +} + +-- ************************************************************** +-- +-- GPS Ionospheric Model +-- +-- ************************************************************** + +GPS-Ionospheric-Model ::= SEQUENCE { + alfa0 BIT STRING (SIZE (8)), + alfa1 BIT STRING (SIZE (8)), + alfa2 BIT STRING (SIZE (8)), + alfa3 BIT STRING (SIZE (8)), + beta0 BIT STRING (SIZE (8)), + beta1 BIT STRING (SIZE (8)), + beta2 BIT STRING (SIZE (8)), + beta3 BIT STRING (SIZE (8)), + iE-Extensions ProtocolExtensionContainer { { GPS-Ionospheric-Model-ExtIEs } } OPTIONAL, + ... +} + +GPS-Ionospheric-Model-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ************************************************************** +-- +-- GPS Measured Results +-- +-- ************************************************************** + +MeasuredResultsList ::= SEQUENCE (SIZE (1..maxNrOfSets)) OF + GPS-MeasuredResults + +GPS-MeasuredResults ::= SEQUENCE { + gps-TOW-1msec INTEGER (0..604799999), + gps-MeasurementParamList GPS-MeasurementParamList, + iE-Extensions ProtocolExtensionContainer { { GPS-MeasuredResults-ExtIEs } } OPTIONAL, + ... +} + +GPS-MeasuredResults-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + +``` + +Error: + +283 + +Error: Reference source not found + +``` + + {ID id-UTRAN-GPSReferenceTimeResult CRITICALITY ignore EXTENSION UTRAN-GPSReferenceTimeResult PRESENCE optional} | + {ID id-GPSReferenceTimeUncertainty CRITICALITY ignore EXTENSION GPSReferenceTimeUncertainty PRESENCE optional}, + ... +} + +``` + +``` + +GPS-MeasurementParamList ::= SEQUENCE (SIZE (1..maxSat)) OF + GPS-MeasurementParam + +``` + +``` + +GPS-MeasurementParam ::= SEQUENCE { + satelliteID INTEGER (0..63), + c-N0 INTEGER (0..63), + doppler INTEGER (-32768..32768), + wholeGPS-Chips INTEGER (0..1022), + fractionalGPS-Chips INTEGER (0..1023), + multipathIndicator MultipathIndicator, + pseudorangeRMS-Error INTEGER (0..63), + iE-Extensions ProtocolExtensionContainer { { GPS-MeasurementParam-ExtIEs } } OPTIONAL, + ... +} + +``` + +``` + +MultipathIndicator ::= ENUMERATED { + nm, + low, + medium, + high } + +``` + +``` + +GPS-MeasurementParam-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +-- ************************************************************** +-- +-- GPS Navigation Model +-- +-- ************************************************************** + +``` + +``` + +GPS-NavigationModel ::= SEQUENCE (SIZE (1..maxSat)) OF + NavigationModelSatInfo + +``` + +``` + +NavigationModelSatInfo ::= SEQUENCE { + satID INTEGER (0..63), + satelliteStatus SatelliteStatus, + gps-clockAndEphemerisParms GPS-ClockAndEphemerisParameters OPTIONAL, + -- This IE is not present if satelliteStatus is es-SN + iE-Extensions ProtocolExtensionContainer { { NavigationModelSatInfo-ExtIEs } } OPTIONAL, + ... +} + +``` + +``` + +NavigationModelSatInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +SatelliteStatus ::= + ENUMERATED { + ns-NN, + es-SN, + es-NN, + rev2, + rev } + +``` + +``` + +-- ***** +-- +-- GPS Real Time Integrity +-- +-- ***** + +``` + +``` + +GPS-RealTimeIntegrity ::= CHOICE { + badSatellites BadSatList, + noBadSatellites NoBadSatellites, + ... +} + +``` + +``` + +BadSatList ::= + SEQUENCE (SIZE (1..maxSat)) OF + INTEGER (0..63) + +``` + +``` + +NoBadSatellites ::= NULL + +``` + +``` + +-- ***** +-- +-- GPS Reference Location +-- +-- ***** + +``` + +``` + +GPS-ReferenceLocation ::= + SEQUENCE { + ue-PositionEstimate UE-PositionEstimate, + iE-Extensions ProtocolExtensionContainer { { GPS-ReferenceLocation-ExtIEs } } OPTIONAL, + ... +} + +``` + +``` + +GPS-ReferenceLocation-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +-- ***** +-- +-- GPS Reference Time +-- +-- ***** + +``` + +``` + +-- ***** +GPS-ReferenceTime ::= + SEQUENCE { + gps-Week INTEGER (0..1023), + gps-TOW-1msec INTEGER (0..604799999), + gps-TOW-AssistList GPS-TOW-AssistList OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { GPS-ReferenceTime-ExtIEs } } OPTIONAL, + ... + } + +GPS-ReferenceTime-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + {ID id-UTRAN-GPSReferenceTime CRITICALITY ignore EXTENSION UTRAN-GPSReferenceTime PRESENCE optional}| + {ID id-GPS-UTRAN-TRU CRITICALITY ignore EXTENSION GPS-UTRAN-TRU PRESENCE optional}| + {ID id-UTRAN-GPS-DriftRate CRITICALITY ignore EXTENSION UTRAN-GPS-DriftRate PRESENCE optional}| + {ID id-GPSReferenceTimeUncertainty CRITICALITY ignore EXTENSION GPSReferenceTimeUncertainty PRESENCE optional}| + {ID id-GPS-Week-Cycle CRITICALITY ignore EXTENSION GPS-Week-Cycle PRESENCE optional}, + ... +} + +GPS-Week-Cycle ::= INTEGER(0..7) + +GPS-TOW-AssistList ::= + SEQUENCE (SIZE (1..maxSat)) OF + GPS-TOW-Assist + +GPS-TOW-Assist ::= + SEQUENCE { + satID INTEGER (0..63), + tlm-Message BIT STRING (SIZE (14)), + antiSpoof BOOLEAN, + alert BOOLEAN, + tlm-Reserved BIT STRING (SIZE (2)), + iE-Extensions ProtocolExtensionContainer { { GPS-TOW-Assist-ExtIEs } } OPTIONAL, + ... + } + +GPS-TOW-Assist-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +UTRAN-GPS-DriftRate ::= + ENUMERATED { + utran-GPSDrift0, utran-GPSDrift1, utran-GPSDrift2, + utran-GPSDrift5, utran-GPSDrift10, utran-GPSDrift15, + utran-GPSDrift25, utran-GPSDrift50, utran-GPSDrift-1, + utran-GPSDrift-2, utran-GPSDrift-5, utran-GPSDrift-10, + utran-GPSDrift-15, utran-GPSDrift-25, utran-GPSDrift-50, + ... + } + +-- ***** +-- + +``` + +``` + +-- GPS Reference Time Uncertainty +-- +-- ***** + +GPSReferenceTimeUncertainty ::= SEQUENCE { + gps-RefTimeUNC INTEGER(0..127), + iE-Extensions ProtocolExtensionContainer { { GPSReferenceTimeUncertainty-ExtIEs } } OPTIONAL, + ... +} + +GPSReferenceTimeUncertainty-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- GPS Transmission TOW +-- +-- ***** + +GPS-Transmission-TOW ::= INTEGER (0..604799) + +-- ***** +-- +-- GPS UTC Model +-- +-- ***** + +GPS-UTC-Model ::= + SEQUENCE { + a1 BIT STRING (SIZE (24)), + a0 BIT STRING (SIZE (32)), + t-ot BIT STRING (SIZE (8)), + delta-t-LS BIT STRING (SIZE (8)), + wn-t BIT STRING (SIZE (8)), + wn-lsf BIT STRING (SIZE (8)), + dn BIT STRING (SIZE (8)), + delta-t-LSF BIT STRING (SIZE (8)), + iE-Extensions ProtocolExtensionContainer { { GPS-UTCmodel-ExtIEs } } OPTIONAL, + ... + } + +GPS-UTCmodel-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- + +``` + +``` +-- GPS UTRAN Time Relationship Uncertainty +-- nsec=nanosecond, usec=microsecond, msec=millisecond, sec=second +-- +-- ***** +``` + +``` +GPS-UTRAN-TRU ::= ENUMERATED { + nsec-50, + nsec-500, + usec-1, + usec-10, + msec-1, + msec-10, + msec-100, + unreliable, + ...} +``` + +``` +-- ***** +-- +-- Additional GPS Assistance Data Required +-- +-- ***** +``` + +``` +AdditionalGPSAssistDataRequired ::= SEQUENCE { + almanacRequest BOOLEAN, + utcModelRequest BOOLEAN, + ionosphericModelRequest BOOLEAN, + navigationModelRequest BOOLEAN, + dgpsCorrectionsRequest BOOLEAN, + referenceLocationRequest BOOLEAN, + referenceTimeRequest BOOLEAN, + acquisitionAssistanceRequest BOOLEAN, + realTimeIntegrityRequest BOOLEAN, + navModelAddDataRequest NavModelAdditionalData OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { AdditionalGPSAssistDataRequired-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +AdditionalGPSAssistDataRequired-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +-- ***** +-- +-- Additional GANSS Assistance Data Required +-- +-- ***** +``` + +``` +AdditionalGanssAssistDataRequired ::= SEQUENCE { + ganssReferenceTime BOOLEAN, +``` + +``` + + ganssreferenceLocation BOOLEAN, + ganssIonosphericModel BOOLEAN, + ganssRequestedGenericAssistanceDataList GanssRequestedGenericAssistanceDataList, + iE-Extensions ProtocolExtensionContainer { { AdditionalGanssAssistDataRequired-ExtIEs } } OPTIONAL, + ... +} + +AdditionalGanssAssistDataRequired-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + {ID id-ganssReq-AddIonosphericModel CRITICALITY ignore EXTENSION GANSSReq-AddIonosphericModel PRESENCE optional}| + {ID id-ganssReq-EarthOrientPara CRITICALITY ignore EXTENSION GANSSReq-EarthOrientPara PRESENCE optional}, + ... +} + +GANSSReq-AddIonosphericModel ::= SEQUENCE { + ganss-add-iono-mode-req BIT STRING (SIZE(2)), + iE-Extensions ProtocolExtensionContainer { { GANSSReq-AddIonosphericModel-ExtIEs } } OPTIONAL, + ... +} + +GANSSReq-AddIonosphericModel-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSSReq-EarthOrientPara ::= BOOLEAN + +GanssRequestedGenericAssistanceDataList ::= SEQUENCE (SIZE (1..maxGANSS)) OF + GanssReqGenericData + +GanssReqGenericData ::= SEQUENCE { + ganssId GANSSID OPTIONAL, + ganssRealTimeIntegrity BOOLEAN OPTIONAL, + ganssDifferentialCorrection DGANSS-Sig-Id-Req OPTIONAL, + ganssAlmanac BOOLEAN OPTIONAL, + ganssNavigationModel BOOLEAN OPTIONAL, + ganssTimeModelGnssGnss BIT STRING (SIZE (9)) OPTIONAL, + ganssReferenceMeasurementInfo BOOLEAN OPTIONAL, + ganssDataBits GanssDataBits OPTIONAL, + ganssUTCModel BOOLEAN OPTIONAL, + ganssNavigationModelAdditionalData NavigationModelGANSS OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { GanssReqGenericData-ExtIEs } } OPTIONAL, + ... +} + +GanssReqGenericData-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + {ID id-ganssAddNavigationModel-req CRITICALITY ignore EXTENSION GANSS-AddNavigationModel-Req PRESENCE optional}| + {ID id-ganssAddUTCModel-req CRITICALITY ignore EXTENSION GANSS-AddUTCModel-Req PRESENCE optional}| + {ID id-ganssAuxInfo-req CRITICALITY ignore EXTENSION GANSS-AuxInfo-req PRESENCE optional}| + {ID id-GANSS-SBAS-ID CRITICALITY ignore EXTENSION GANSS-SBAS-ID PRESENCE optional}| + {ID id-GANSS-AddADchoices CRITICALITY ignore EXTENSION GANSS-AddADchoices PRESENCE optional}| + {ID id-BDSIonosphericGridModel CRITICALITY ignore EXTENSION BDSIonosphericGridModel PRESENCE optional}| + {ID id-DBDSCorrection CRITICALITY ignore EXTENSION DBDSCorrection PRESENCE optional}, + ... +} + +BDSIonosphericGridModel ::= BOOLEAN + +``` + +``` + +DBDSCorrection ::= SEQUENCE { + dGANSSSignalBDS BIT STRING (SIZE (8)), + iE-Extensions ProtocolExtensionContainer { { DBDSCorrection-ExtIEs } } OPTIONAL, + ... +} + +DBDSCorrection-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-AddNavigationModel-Req ::= BOOLEAN + +GANSS-AddUTCModel-Req ::= BOOLEAN + +GANSS-AuxInfo-req ::= BOOLEAN + +GANSS-AddADchoices ::= SEQUENCE { + orbitModelID INTEGER (0..7) OPTIONAL, + clockModelID INTEGER (0..7) OPTIONAL, + utcModelID INTEGER (0..7) OPTIONAL, + almanacModelID INTEGER (0..7) OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { GANSS-AddADchoices-ExtIEs } } OPTIONAL, + ... +} + +GANSS-AddADchoices-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +DGANSS-Sig-Id-Req ::= BIT STRING (SIZE (8)) + +GanssDataBits ::= SEQUENCE { + ganssTod INTEGER (0..86399), + dataBitAssistanceList ReqDataBitAssistanceList, + iE-Extensions ProtocolExtensionContainer { { GanssDataBits-ExtIEs } } OPTIONAL, + ... +} + +GanssDataBits-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +ReqDataBitAssistanceList ::= SEQUENCE { + ganssSignalID BIT STRING (SIZE (8)), + ganssDataBitInterval INTEGER (0..15), + ganssSatelliteInfo SEQUENCE (SIZE (1..maxGANSSSat)) OF INTEGER (0..63) OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { ReqDataBitAssistanceList-ExtIEs } } OPTIONAL, + ... +} + +``` + +``` + +ReqDataBitAssistanceList-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Information Exchange ID +-- +-- ***** + +InformationExchangeID ::= INTEGER (0..1048575) + +-- ***** +-- +-- Information Report Characteristics +-- +-- ***** + +InformationReportCharacteristics ::= SEQUENCE { + type InformationReportCharacteristicsType, + periodicity InformationReportPeriodicity OPTIONAL, + -- present if type indicates periodic + ... +} + +InformationReportCharacteristicsType ::= ENUMERATED { + onDemand, + periodic, + onModification, + ... +} + +InformationReportPeriodicity ::= CHOICE { + min INTEGER (1..60, ...), + -- Unit min, Step lmin + hour INTEGER (1..24, ...), + -- Unit hour, Step lhour + ... +} + +-- ***** +-- +-- Information Type +-- +-- ***** + +InformationType ::= CHOICE { + implicitInformation MethodType, + +``` + +``` + + explicitInformation ExplicitInformationList, + ... + } + + ExplicitInformationList ::= SEQUENCE (SIZE (1..maxNrOfExpInfo)) OF ExplicitInformation + + ExplicitInformation ::= CHOICE { + almanacAndSatelliteHealth AlmanacAndSatelliteHealth, + utcModel UtcModel, + ionosphericModel IonosphericModel, + navigationModel NavigationModel, + dgpsCorrections DgpsCorrections, + referenceTime ReferenceTime, + acquisitionAssistance AcquisitionAssistance, + realTimeIntegrity RealTimeIntegrity, + almanacAndSatelliteHealthSIB AlmanacAndSatelliteHealthSIB-InfoType, + ... / + referenceLocation ReferenceLocation, + ganss-Common-DataReq GANSSCommonDataReq, + ganss-Generic-DataList GANSSGenericDataList + } + + DganssCorrectionsReq ::= SEQUENCE { + transmissionGanssTimeIndicator TransmissionGanssTimeIndicator OPTIONAL, + dganss-sig-id-req DGANSs-Sig-Id-Req, + iE-Extensions ProtocolExtensionContainer { { DganssCorrectionsReq-ExtIEs} } OPTIONAL, + ... + } + + DganssCorrectionsReq-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + Ganss-almanacAndSatelliteHealthReq ::= SEQUENCE { + transmissionGanssTimeIndicator TransmissionGanssTimeIndicator OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Ganss-almanacAndSatelliteHealthReq-ExtIEs} } OPTIONAL, + ... + } + + Ganss-almanacAndSatelliteHealthReq-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + GANSSCommonDataReq ::= SEQUENCE{ + ganss-ReferenceTime ENUMERATED {requested, not-requested} OPTIONAL, + ganss-IonosphericModel ENUMERATED {requested, not-requested} OPTIONAL, + ganss-ReferenceLocation ENUMERATED {requested, not-requested} OPTIONAL, + ie-Extensions ProtocolExtensionContainer { { GANSSCommonDataReq-ExtIEs } } OPTIONAL, + ... + } + +``` + +``` + +GANSSCommonDataReq-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + {ID id-GANSS-AddIonoModelReq CRITICALITY ignore EXTENSION GANSS-AddIonoModelReq PRESENCE optional} | + {ID id-GANSS-EarthOrientParaReq CRITICALITY ignore EXTENSION GANSS-EarthOrientParaReq PRESENCE optional} , + ... +} + +GANSS-AddIonoModelReq ::= SEQUENCE { + dataID BIT STRING (SIZE(2)), + iE-Extensions ProtocolExtensionContainer { { GANSS-AddIonoModelReq-ExtIEs} } OPTIONAL, + ... +} + +GANSS-AddIonoModelReq-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-EarthOrientParaReq ::= SEQUENCE { + eopReq ENUMERATED {requested, not-requested}, + iE-Extensions ProtocolExtensionContainer { { GANSS-EarthOrientParaReq-ExtIEs} } OPTIONAL, + ... +} + +GANSS-EarthOrientParaReq-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSSGenericDataList ::= SEQUENCE (SIZE(1..maxGANSS)) OF GANSSGenericDataReq + +GANSSGenericDataReq ::= SEQUENCE { + ganssID GANSSID OPTIONAL, + ganss-realTimeIntegrity Ganss-realTimeIntegrityReq OPTIONAL, + ganss-dataBitAssistance GanssDataBits OPTIONAL, + dganssCorrections DganssCorrectionsReq OPTIONAL, + ganss-almanacAndSatelliteHealth Ganss-almanacAndSatelliteHealthReq OPTIONAL, + ganss-referenceMeasurementInfo Ganss-referenceMeasurementInfoReq OPTIONAL, + ganss-utcModel Ganss-utcModelReq OPTIONAL, + ganss-TimeModel-Gnss-Gnss Ganss-TimeModel-Gnss-Gnss OPTIONAL, + navigationModel NavigationModelGANSS OPTIONAL, + ... + ganss-AddNavModelsReq AddNavigationModelsGANSS OPTIONAL, + ganss-AddUtcModelsReq GANSS-AddUtcModelsReq OPTIONAL, + ganss-AuxInfoReq GANSS-AuxInfoReq OPTIONAL, + -- the following IE shall be present if GANSSID is '0' (SBAS) + ganss-SBAS-ID GANSS-SBAS-ID OPTIONAL, + dBDS-Corrections DBDS-Corrections OPTIONAL, + bDS-Ionospheric-Grid-Model-Request BDS-Ionospheric-Grid-Model-Request OPTIONAL +} + +AddNavigationModelsGANSS ::= SEQUENCE { + +``` + +``` + +ganSSWeek INTEGER(0..4095), +ganSS TOE INTEGER(0..167), +t-toe-limit INTEGER(0..10), +addSatRelatedDataListGANSS AddSatelliteRelatedDataListGANSS, +iE-Extensions ProtocolExtensionContainer { { AddNavigationModelsGANSS-ExtIEs } } OPTIONAL, +... +} + +AddNavigationModelsGANSS-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { +... +} + +AddSatelliteRelatedDataListGANSS ::= SEQUENCE (SIZE (0..maxGANSSSat)) OF AddSatelliteRelatedDataGANSS + +AddSatelliteRelatedDataGANSS ::= SEQUENCE { + satID INTEGER (0..63), + iod BIT STRING (SIZE(10)), + iE-Extensions ProtocolExtensionContainer { { AddSatelliteRelatedDataGANSS-ExtIEs } } OPTIONAL, + ... +} + +AddSatelliteRelatedDataGANSS-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { +... +} + +BDS-Ionospheric-Grid-Model-Request ::= ENUMERATED { + requested, + ... +} + +DBDS-Corrections ::= SEQUENCE { + transmissionGanssTimeIndicator TransmissionGanssTimeIndicator OPTIONAL, + dGANSS-Signal BIT STRING( SIZE (8)), + iE-Extensions ProtocolExtensionContainer { { DBDS-Corrections-ExtIEs } } OPTIONAL, + ... +} + +DBDS-Corrections-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { +... +} + +GANSS-AddUtcModelsReq ::= SEQUENCE { + transmissionGanssTimeIndicator TransmissionGanssTimeIndicator OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { GANSS-AddUtcModelsReq-ExtIEs } } OPTIONAL, + ... +} + +GANSS-AddUtcModelsReq-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { +... +} + +GANSS-AuxInfoReq ::= SEQUENCE { + +``` + +``` + transmissionGanssTimeIndicator TransmissionGanssTimeIndicator OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { GANSS-AuxInfoReq-ExtIEs} } OPTIONAL, + ... +} + +GANSS-AuxInfoReq-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-SBAS-ID ::= ENUMERATED { + waas, + egnos, + msas, + gagan, + ... +} + +Ganss-utcModelReq ::= SEQUENCE { + transmissionGanssTimeIndicator TransmissionGanssTimeIndicator OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Ganss-utcModelReq-ExtIEs} } OPTIONAL, + ... +} + +Ganss-utcModelReq-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +Ganss-realTimeIntegrityReq ::= SEQUENCE { + transmissionGanssTimeIndicator TransmissionGanssTimeIndicator OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Ganss-realTimeIntegrityReq-ExtIEs} } OPTIONAL, + ... +} + +Ganss-realTimeIntegrityReq-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +Ganss-referenceMeasurementInfoReq ::= SEQUENCE { + transmissionGanssTimeIndicator TransmissionGanssTimeIndicator OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Ganss-referenceMeasurementInfoReq-ExtIEs} } OPTIONAL, + ... +} + +Ganss-referenceMeasurementInfoReq-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +Ganss-TimeModel-Gnss-Gnss ::= SEQUENCE{ + ganssTimeModelGnssGnssExt BIT STRING (SIZE(9)), + transmissionGanssTimeIndicator TransmissionGanssTimeIndicator OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Ganss-TimeModel-Gnss-Gnss-ExtIEs} } OPTIONAL, + ... +} + +Ganss-TimeModel-Gnss-Gnss-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +TransmissionGanssTimeIndicator ::= ENUMERATED { + requested, + not-Requested +} + +AlmanacAndSatelliteHealth ::= NULL + +UtcModel ::= SEQUENCE { + transmissionTOWIndicator TransmissionTOWIndicator, + iE-Extensions ProtocolExtensionContainer { { UtcModel-ExtIEs } } OPTIONAL, + ... +} + +UtcModel-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +IonosphericModel ::= SEQUENCE { + transmissionTOWIndicator TransmissionTOWIndicator, + iE-Extensions ProtocolExtensionContainer { { IonosphericModel-ExtIEs } } OPTIONAL, + ... +} + +IonosphericModel-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +NavigationModel ::= SEQUENCE { + transmissionTOWIndicator TransmissionTOWIndicator, + navModelAdditionalData NavModelAdditionalData OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { NavigationModel-ExtIEs } } OPTIONAL, + ... +} + +NavigationModel-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +NavModelAdditionalData ::= SEQUENCE { +``` + +``` + gps-Week INTEGER (0..1023), + gps-TOE INTEGER (0..167), + t-TOE-limit INTEGER (0..10), + satRelatedDataList SatelliteRelatedDataList, + iE-Extensions ProtocolExtensionContainer { { NavModelAdditionalData-ExtIEs } } OPTIONAL, + ... +} + +NavModelAdditionalData-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +SatelliteRelatedDataList ::= SEQUENCE (SIZE (0..maxSat)) OF SatelliteRelatedData + +SatelliteRelatedData ::= SEQUENCE { + satID INTEGER (0..63), + iode INTEGER (0..255), + iE-Extensions ProtocolExtensionContainer { { SatelliteRelatedData-ExtIEs } } OPTIONAL, + ... +} + +SatelliteRelatedData-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +NavigationModelGANSS ::= SEQUENCE { + ganssWeek INTEGER (0..4095), + ganssTOE INTEGER (0..167), + t-toe-limit INTEGER (0..10), + satRelatedDataListGANSS SatelliteRelatedDataListGANSS, + iE-Extensions ProtocolExtensionContainer { { NavigationModelGANSS-ExtIEs } } OPTIONAL, + ... +} + +NavigationModelGANSS-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +SatelliteRelatedDataListGANSS ::= SEQUENCE (SIZE (0..maxGANSSSat)) OF SatelliteRelatedDataGANSS + +SatelliteRelatedDataGANSS ::= SEQUENCE { + satID INTEGER (0..63), + iod BIT STRING (SIZE(10)), + iE-Extensions ProtocolExtensionContainer { { SatelliteRelatedDataGANSS-ExtIEs } } OPTIONAL, + ... +} + +SatelliteRelatedDataGANSS-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +DgpsCorrections ::= NULL +``` + +``` +ReferenceTime ::= NULL + +AcquisitionAssistance ::= NULL + +RealTimeIntegrity ::= NULL + +AlmanacAndSatelliteHealthSIB-InfoType ::= SEQUENCE { + transmissionTOWIndicator TransmissionTOWIndicator, + iE-Extensions ProtocolExtensionContainer { { AlmanacAndSatelliteHealthSIB-InfoType-ExtIEs } } OPTIONAL, + ... +} + +AlmanacAndSatelliteHealthSIB-InfoType-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +ReferenceLocation ::= NULL + +TransmissionTOWIndicator ::= ENUMERATED { + requested, + not-Requested +} + +-- ***** +-- +-- Message Structure +-- +-- ***** + +MessageStructure ::= SEQUENCE (SIZE (1..maxNrOfLevels)) OF + SEQUENCE { + iE-ID ProtocolIE-ID, + repetitionNumber MessageStructureRepetition OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {MessageStructure-ExtIEs} } OPTIONAL, + ... + } + +MessageStructureRepetition ::= INTEGER (1..256) + +MessageStructure-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Measurement Instructions Used +-- +-- ***** + +MeasInstructionsUsed ::= SEQUENCE { + measurementValidity MeasurementValidity, +``` + +``` + + iE-Extensions ProtocolExtensionContainer { { MeasInstructionsUsed-ExtIEs } } OPTIONAL, + ... + } + + MeasInstructionsUsed-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + -- ***** + -- + -- Measurement Validity + -- + -- ***** + + MeasurementValidity ::= SEQUENCE { + ue-State ENUMERATED { cell-DCH, all-States-Except-Cell-DCH, all-States, ... }, + iE-Extensions ProtocolExtensionContainer { { MeasurementValidity-ExtIEs } } OPTIONAL, + ... + } + + MeasurementValidity-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + -- ***** + -- + -- Method Type + -- + -- ***** + + MethodType ::= ENUMERATED { + ue-assisted, + ue-based + } + + -- ***** + -- + -- OTDOA Measurement Group + -- + -- ***** + + OTDOA-MeasurementGroup ::= SEQUENCE { + otdoa-ReferenceCellInfo OTDOA-ReferenceCellInfo, + otdoa-NeighbourCellInfoList OTDOA-NeighbourCellInfoList, + otdoa-MeasuredResultsSets OTDOA-MeasuredResultsSets, + iE-Extensions ProtocolExtensionContainer { { OTDOA-MeasurementGroup-ExtIEs } } OPTIONAL, + ... + } + + OTDOA-MeasurementGroup-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + +``` + +``` + +} + +OTDOA-ReferenceCellInfo ::= SEQUENCE { + uC-ID UC-ID, + uTRANAccessPointPositionAltitude UTRANAccessPointPositionAltitude, + tUTRANGPSMeasurementValueInfo TUTRANGPSMeasurementValueInfo, + iE-Extensions ProtocolExtensionContainer { { OTDOA-ReferenceCellInfo-ExtIEs } } + ... +} + +OTDOA-ReferenceCellInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + { ID id-TUTRANGNSSMeasurementValueInfo CRITICALITY ignore EXTENSION TUTRANGNSSMeasurementValueInfo PRESENCE +optional }| + { ID id-additionalMeasurementInforLCR CRITICALITY ignore EXTENSION AdditionalMeasurementInforLCR PRESENCE +optional }, + -- 1.28Mcps TDD only + ... +} + +OTDOA-ReferenceCellInfoSAS-centric ::= SEQUENCE { + uC-ID UC-ID, + iE-Extensions ProtocolExtensionContainer { { OTDOA-ReferenceCellInfoSAS-centric-ExtIEs } } + ... +} + +OTDOA-ReferenceCellInfoSAS-centric-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +OTDOA-NeighbourCellInfoList ::= SEQUENCE (SIZE (1..maxNrOfMeasNCell)) OF + OTDOA-NeighbourCellInfo + +OTDOA-NeighbourCellInfo ::= SEQUENCE { + uC-ID UC-ID, + uTRANAccessPointPositionAltitude UTRANAccessPointPositionAltitude, + relativeTimingDifferenceInfo RelativeTimingDifferenceInfo, + iE-Extensions ProtocolExtensionContainer { { OTDOA-NeighbourCellInfo-ExtIEs } } + ... +} + +OTDOA-NeighbourCellInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +OTDOA-MeasuredResultsSets ::= SEQUENCE (SIZE (1..maxNrOfMeasurements)) OF + OTDOA-MeasuredResultsInfoList + +OTDOA-MeasuredResultsInfoList ::= SEQUENCE (SIZE (1..maxNrOfMeasNCell)) OF + OTDOA-MeasuredResultsInfo + +OTDOA-MeasuredResultsInfo ::= SEQUENCE { + uC-ID UC-ID, + +``` + +Error: + +300 + +Error: Reference source not found + +``` + + ue-SFNSFNTTimeDifferenceType2Info UE-SFNSFNTTimeDifferenceType2Info, + iE-Extensions ProtocolExtensionContainer { { OTDOA-MeasuredResultsInfo-ExtIEs } } OPTIONAL, + ... + } + + OTDOA-MeasuredResultsInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + { ID id-OTDOA-AddMeasuredResultsInfo CRITICALITY ignore EXTENSION OTDOA-AddMeasuredResultsInfo PRESENCE optional }, + ... + } + + OTDOA-AddMeasuredResultsInfo ::= SEQUENCE { + primaryCPICH-Info PrimaryScramblingCode, + iE-Extensions ProtocolExtensionContainer { { OTDOA-AddMeasuredResultsInfo-ExtIEs } } OPTIONAL, + ... + } + + OTDOA-AddMeasuredResultsInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + UE-SFNSFNTTimeDifferenceType2Info ::= SEQUENCE { + ue-SFNSFNTTimeDifferenceType2 INTEGER (0..40961), + ue-PositioningMeasQuality UE-PositioningMeasQuality, + measurementDelay INTEGER (0..65535), + iE-Extensions ProtocolExtensionContainer { { UE-SFNSFNTTimeDifferenceInfo-ExtIEs } } OPTIONAL, + ... + } + + UE-SFNSFNTTimeDifferenceInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + UC-ID ::= SEQUENCE { + rNC-ID INTEGER (0..4095), + c-ID INTEGER (0..65535), + iE-Extensions ProtocolExtensionContainer { { UC-ID-ExtIEs } } OPTIONAL, + ... + } + + UC-ID-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + { ID id-Extended-RNC-ID CRITICALITY reject EXTENSION Extended-RNC-ID PRESENCE optional }, + ... + } + + Extended-RNC-ID ::= INTEGER (4096..65535) + + RelativeTimingDifferenceInfo ::= CHOICE { + sFNSFNMeasurementValueInfo SFNSFNMeasurementValueInfo, + tUTRANGPSMeasurementValueInfo TUTRANGPSMeasurementValueInfo, + ... + tUTRANGANSSMeasurementValueInfo TUTRANGANSSMeasurementValueInfo + } + +``` + +Error: + +301 + +Error: Reference source not found + +``` + - + } + + SFNSFNMeasurementValueInfo ::= SEQUENCE { + sFNSFNValue SFNSFNValue, + sFNSFNQuality SFNSFNQuality OPTIONAL, + sFNSFNDriftRate SFNSFNDriftRate, + sFNSFNDriftRateQuality SFNSFNDriftRateQuality OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { SFNSFNMeasurementValueInfo-ExtIEs } } OPTIONAL, + ... + } + + SFNSFNMeasurementValueInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + SFNSFNValue ::= INTEGER (0..614399) + + SFNSFNQuality ::= INTEGER (0..255) + -- Unit chip, Step 1/16 chip, Range 0.. 255/16 chip + + SFNSFNDriftRate ::= INTEGER (-100..100) + -- Unit chip/s, Step 1/256 chip/s, Range -100/256..+100/256 chip/s + + SFNSFNDriftRateQuality ::= INTEGER (0..100) + -- Unit chip/s, Step 1/256 chip/s, Range 0..100/256 chip/s + + TUTRANGPSMeasurementValueInfo ::= SEQUENCE { + sFN SFN, + tUTRANGPS TUTRANGPS, + tUTRANGPSQuality TUTRANGPSQuality OPTIONAL, + tUTRANGPSDriftRate TUTRANGPSDriftRate, + tUTRANGPSDriftRateQuality TUTRANGPSDriftRateQuality OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { TUTRANGPSMeasurementValueInfo-ExtIEs } } OPTIONAL, + ... + } + + TUTRANGPSMeasurementValueInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + SFN ::= INTEGER (0..4095) + + TUTRANGPS ::= SEQUENCE { + ms-part INTEGER (0..16383), + ls-part INTEGER (0..4294967295) + } + + TUTRANGPSQuality ::= INTEGER (0..255) + -- Unit chip, Step 1/16 chip, Range 0.. 255/16 chip + + TUTRANGPSDriftRate ::= INTEGER (-50..50) + -- Unit chip/s, Step 1/256 chip/s, Range -50/256..+50/256 chip/s +``` + +``` + +TUTRANGPSDriftRateQuality ::= + INTEGER (0..50) +-- Unit chip/s, Step 1/256 chip/s, Range 0..50/256 chip/s + +TUTRANGANSSMeasurementValueInfo ::= SEQUENCE { + ganssID GANSSID OPTIONAL, + sFN SFN, + tUTRANGANSS TUTRANGANSS, + tUTRANGANSSQuality INTEGER (0..255) OPTIONAL, + tUTRANGANSSDriftRate INTEGER (-50..50), + tUTRANGANSSDriftRateQuality INTEGER (0..50) OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { TUTRANGANSSMeasurementValueInfo-ExtIEs } } OPTIONAL, + ... +} + +TUTRANGANSSMeasurementValueInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +TUTRANGANSS ::= + SEQUENCE { + ms-part INTEGER (0..16383), + ls-part INTEGER (0..4294967295) + } + +AdditionalMeasurementInforLCR ::= SEQUENCE { + timingAdvanceLCR-R7 TimingAdvanceLCR-R7, + rxTimingDeviationLCR RxTimingDeviationLCR, + angleOfArrivalLCR AngleOfArrivalLCR OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { AdditionalMeasurementInforLCR-ExtIEs } } OPTIONAL, + ... +} + +AdditionalMeasurementInforLCR-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +TimingAdvanceLCR-R7 ::= + INTEGER (0..8191) + +-- ***** +-- +-- Periodic Position Calculation Info +-- +-- ***** + +PeriodicPosCalcInfo ::= SEQUENCE { + referenceNumber INTEGER (0..32767, ...), + amountOutstandingRequests INTEGER (1..8639999, ...), + reportingInterval INTEGER (1..8639999, ...), + iE-Extensions ProtocolExtensionContainer { { PeriodicPosCalcInfo-ExtIEs } } OPTIONAL, + ... +} + +``` + +``` + +PeriodicPosCalcInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Periodic Location Info +-- +-- ***** + +PeriodicLocationInfo ::= SEQUENCE { + reportingAmount INTEGER (1..8639999, ...), + reportingInterval INTEGER (1..8639999, ...), + iE-Extensions ProtocolExtensionContainer { { PeriodicLocationInfo-ExtIEs } } OPTIONAL, + ... +} + +PeriodicLocationInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Periodic Termination Cause +-- +-- ***** + +PeriodicTerminationCause ::= ENUMERATED { + rrc-state-transition, + cancelled-by-srnc, + cancelled-by-sas, + undefined, + ... +} + +-- ***** +-- +-- Positioning Method +-- +-- ***** + +PositioningMethod ::= SEQUENCE { + additionalMethodType AdditionalMethodType, + selectedPositionMethod SelectedPositionMethod, + iE-Extensions ProtocolExtensionContainer { { PositioningMethod-ExtIEs } } OPTIONAL, + ... +} + +PositioningMethod-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + +``` + +``` +-- The following IE shall be present if the Selected Position Method IE value is set to "GNSS" or "OTDOA or GNSS" + { ID id-GNSS-PositioningMethod CRITICALITY ignore EXTENSION GNSS-PositioningMethod PRESENCE conditional } | +-- This IE shall be present if the Selected Position Method IE value is set to "GPS and AddPos" or "OTDOA or GPS and AddPos" + { ID id-Additional-PositioningMethod CRITICALITY ignore EXTENSION Additional-PositioningMethod PRESENCE conditional }, + ... +} +``` + +``` +GNSS-PositioningMethod ::= BIT STRING (SIZE(9)) +``` + +``` +Additional-PositioningMethod ::= BIT STRING (SIZE(8)) +``` + +``` +SelectedPositionMethod ::= ENUMERATED { + oTDOA, + gPS, + oTDOA-or-GPS, + cell-id, + uTDOA, + ..., + gNSS, + oTDOA-or-GNSS, + gPS-and-AddPos, + oTDOA-or-GPS-and-AddPos +} +``` + +``` +-- ************************************************************** +-- +-- Positioning Priority +-- +-- ************************************************************** +``` + +``` +PositioningPriority ::= ENUMERATED { + high-priority, + normal-priority, + ... +} +``` + +``` +-- ************************************************************** +-- +-- RRC State Change +-- +-- ************************************************************** +``` + +``` +RRCstateChange ::= SEQUENCE { + new-ue-State ENUMERATED { cell-DCH, cell-FACH, cell-PCH, ura-PCH, ... }, + iE-Extensions ProtocolExtensionContainer { { RRCstateChange-ExtIEs } } OPTIONAL, + ... +} +``` + +``` +RRCstateChange-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` +-- ************************************************************** +``` + +``` + +-- +-- Requested Data Value +-- +-- ***** + +RequestedDataValue ::= SEQUENCE { + gpsAlmanacAndSatelliteHealth GPS-AlmanacAndSatelliteHealth OPTIONAL, + gps-UTC-Model GPS-UTC-Model OPTIONAL, + gps-Ionospheric-Model GPS-Ionospheric-Model OPTIONAL, + gps-NavigationModel GPS-NavigationModel OPTIONAL, + dgpsCorrections DGPS Corrections OPTIONAL, + referenceTime GPS-ReferenceTime OPTIONAL, + gps-AcquisitionAssistance GPS-AcquisitionAssistance OPTIONAL, + gps-RealTime-Integrity GPS-RealTimeIntegrity OPTIONAL, + almanacAndSatelliteHealthSIB AlmanacAndSatelliteHealthSIB OPTIONAL, + gps-Transmission-TOW GPS-Transmission-TOW OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { RequestedDataValue-ExtIEs} } OPTIONAL, + ... +} + +--at least one of the above IEs shall be present in the requested data value + +RequestedDataValue-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + { ID id-GPS-ReferenceLocation CRITICALITY ignore EXTENSION GPS-ReferenceLocation PRESENCE optional }| + { ID id-GNSSS-CommonAssistanceData CRITICALITY ignore EXTENSION GNSSS-CommonAssistanceData PRESENCE optional }| + { ID id-GNSSS-GenericAssistanceDataList CRITICALITY ignore EXTENSION GNSSS-GenericAssistanceDataList PRESENCE optional }, + ... +} + +-- +-- Requested Data Value Information +-- +-- ***** + +RequestedDataValueInformation ::= CHOICE { + informationAvailable InformationAvailable, + informationNotAvailable InformationNotAvailable +} + +InformationAvailable ::= SEQUENCE { + requestedDataValue RequestedDataValue, + iE-Extensions ProtocolExtensionContainer { { InformationAvailable-ExtIEs} } OPTIONAL, + ... +} + +InformationAvailable-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +InformationNotAvailable ::= NULL + +``` + +``` + +-- ***** +-- +-- Request Type +-- +-- ***** +RequestType ::= SEQUENCE { + event RequestTypeEvent, + reportArea RequestTypeReportArea, + horizontalAccuracyCode RequestTypeAccuracyCode OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { RequestType-ExtIEs} } OPTIONAL, + ... +} + +RequestType-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +RequestTypeEvent ::= ENUMERATED { + stop-change-of-service-area, + direct, + change-of-service-area, + stop-direct, + ..., + periodic, + stop-periodic +} + +RequestTypeReportArea ::= ENUMERATED { + service-area, + geographical-area, + ... +} + +RequestTypeAccuracyCode ::= INTEGER (0..127) + +-- ***** +-- +-- Response Time +-- +-- ***** +ResponseTime ::= ENUMERATED { + low-delay, + delay-tolerant, + ... +} + +-- ***** +-- +-- Horizontal Accuracy Code +-- +-- ***** + +``` + +``` + +HorizontalAccuracyCode ::= INTEGER (0..127) + +-- ***** +-- +-- UE Positioning Capability +-- +-- ***** +UE-PositioningCapability ::= SEQUENCE { + standAloneLocationMethodsSupported BOOLEAN, + ueBasedOTDOASupported BOOLEAN, + networkAssistedGPSSupport NetworkAssistedGPSSupport, + supportGPSTimingOfCellFrame BOOLEAN, + supportForIPDL BOOLEAN, + supportForRxBTxTimeDiff BOOLEAN, + supportForUEAGPSInCellPCH BOOLEAN, + supportForSFNSFNTTimeDiff BOOLEAN, + iE-Extensions ProtocolExtensionContainer { {UE-PositioningCapability-ExtIEs} } OPTIONAL, + ... +} + +UE-PositioningCapability-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + { ID id-NetworkAssistedGANSSSupport CRITICALITY ignore EXTENSION NetworkAssistedGANSSSupport PRESENCE optional}| + { ID id-AddPosSupport CRITICALITY ignore EXTENSION AddPosSupport PRESENCE optional}, + ... +} + +NetworkAssistedGANSSSupport ::= SEQUENCE (SIZE (1..maxGANSS)) OF SEQUENCE { + ganssID GANSSID OPTIONAL, + ganssMode ENUMERATED { + networkBased, + ue-Based, + both, + none + }, + ganssSignalID GANSS-SignalID OPTIONAL, + supportGANSSTimingOfCellFrame BOOLEAN, + supportGANSSCarrierPhaseMeasurement BOOLEAN, + iE-Extensions ProtocolExtensionContainer { { NetworkAssistedGANSSSupport-ExtIEs} } OPTIONAL, + ... +} + +AddPosSupport ::= SEQUENCE (SIZE (1..maxAddPos)) OF AddPosSupport-Element + +AddPosSupport-Element ::= SEQUENCE { + addPosID ENUMERATED { + barometricPressure, + WLAN, + bluetooth, + mBS, + ... + }, + addPosMode ENUMERATED { + +``` + +``` + + standalone, + ue-assisted, + both, + ... + }, + ... +} + +NetworkAssistedGANSSSupport-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + -- the following IE shall be present if 'GANSSID' in 'NetworkAssistedGANSSSupport' is '0' (SBAS) + { ID id-GANSS-SBAS-IDs CRITICALITY ignore EXTENSION GANSS-SBAS-IDs PRESENCE optional }| + { ID id-GANSS-Signal-IDs CRITICALITY ignore EXTENSION GANSS-Signal-IDs PRESENCE optional }| + { ID id-supportGANSSNonNativeADchoices CRITICALITY ignore EXTENSION SupportGANSSNonNativeADchoices PRESENCE optional }, + ... +} + +NetworkAssistedGPSSupport ::= ENUMERATED { + network-based, + ue-based, + both, + none, + ... +} + +GANSS-SBAS-IDs ::= SEQUENCE { + ganss-sbas-ids BIT STRING (SIZE(8)), + iE-Extensions ProtocolExtensionContainer { { GANSS-SBAS-IDs-ExtIEs } } OPTIONAL, + ... +} + +GANSS-SBAS-IDs-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-Signal-IDs ::= SEQUENCE { + ganss-signal-ids BIT STRING (SIZE(8)), + iE-Extensions ProtocolExtensionContainer { { GANSS-Signal-IDs-ExtIEs } } OPTIONAL, + ... +} + +GANSS-Signal-IDs-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +SupportGANSSNonNativeADchoices ::= BOOLEAN + +-- ************************************************************** +-- +-- UTDOA Positioning (Position Activation Request Message) +-- +-- +``` + +-- \*\*\*\*\* + +UTDOAPositioning ::= SEQUENCE { +    utdoa-BitCount          UTDOA-BitCount, +    utdoa-timeInterval      UTDOA-TimeInterval, +    iE-Extensions          ProtocolExtensionContainer { { UTDOAPositioning-ExtIEs } } OPTIONAL, +    ... +} + +UTDOAPositioning-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { +    ... +} + +UTDOA-BitCount ::= INTEGER (0..5000) + +UTDOA-TimeInterval ::= INTEGER (0..3000) + +EnvironmentCharacterisation ::= ENUMERATED { heavyMultipathandNLOSconditions, +    noOrLightMultipathAndUsuallyLOSconditions, +    notDefinedOrMixedEnvironment, +    ... +} + +-- \*\*\*\*\* + +-- + +-- GPS and GANSS Positioning (Position Activation Request Message) + +-- + +-- \*\*\*\*\* + +GPSPositioning ::= SEQUENCE { +    gpsPositioningInstructions    GPSPositioningInstructions, +    requestedDataValue            RequestedDataValue            OPTIONAL, +    iE-Extensions                ProtocolExtensionContainer { { GPSPositioning-ExtIEs } } OPTIONAL, +    ... +} + +GPSPositioning-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { +    ... +} + +GPSPositioningInstructions ::= SEQUENCE { +    horizontalAccuracyCode        HorizontalAccuracyCode                                    OPTIONAL, +    verticalAccuracyCode          VerticalAccuracyCode                                        OPTIONAL, +    gpsTimingOfCellWanted         BOOLEAN, +    additionalAssistanceDataRequest BOOLEAN, +    iE-Extensions                ProtocolExtensionContainer { { GPSPositioningInstructions-ExtIEs } } OPTIONAL, +    ... +} + +GPSPositioningInstructions-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + +``` + + {ID id-MeasurementValidity CRITICALITY ignore EXTENSION MeasurementValidity PRESENCE optional}, + ... +} + +GANSSPositioning ::= SEQUENCE { + ganssPositioningInstructions GANSS-PositioningInstructions, + requestedDataValue RequestedDataValue OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { GANSSPositioning-ExtIEs } } OPTIONAL, + ... +} + +GANSSPositioning-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +GANSS-PositioningInstructions ::= SEQUENCE { + horizontalAccuracyCode HorizontalAccuracyCode OPTIONAL, + verticalAccuracyCode VerticalAccuracyCode OPTIONAL, + ganssTimingOfCellWanted BIT STRING (SIZE (8)), + additionalAssistanceDataRequest BIT STRING (SIZE (8)), + measurementValidity MeasurementValidity OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { GANSS-PositioningInstructions-ExtIEs } } OPTIONAL, + ... +} + +GANSS-PositioningInstructions-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + {ID id-GANSSCarrierPhaseRequested CRITICALITY ignore EXTENSION GANSSCarrierPhaseRequested PRESENCE optional}| + {ID id-GANSSMultiFreqMeasRequested CRITICALITY ignore EXTENSION GANSSMultiFreqMeasRequested PRESENCE optional}, + ... +} + +GANSSCarrierPhaseRequested ::= BIT STRING (SIZE (8)) + +GANSSMultiFreqMeasRequested ::= BIT STRING (SIZE (8)) + +-- ***** +-- +-- OTDOA Assistance Data +-- +-- ***** +OTDOAAssistanceData ::= SEQUENCE { + uE-Positioning-OTDOA-AssistanceData UE-Positioning-OTDOA-AssistanceData, + iE-Extensions ProtocolExtensionContainer { { OTDOAAssistanceData-ExtIEs } } OPTIONAL, + ... +} + +OTDOAAssistanceData-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** + +``` + +``` + +-- +-- UE Positioning OTDOA Assistance Data +-- +-- ***** + +UE-Positioning-OTDOA-AssistanceData ::= SEQUENCE { + ue-positioning-OTDOA-ReferenceCellInfo UE-Positioning-OTDOA-ReferenceCellInfo OPTIONAL, + ue-positioning-OTDOA-NeighbourCellList UE-Positioning-OTDOA-NeighbourCellList OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UE-Positioning-OTDOAAssistanceData-ExtIEs } } OPTIONAL, + ... +} + +UE-Positioning-OTDOAAssistanceData-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +UE-Positioning-OTDOA-ReferenceCellInfo ::= SEQUENCE { + sfn SFN OPTIONAL, + modeSpecificInfo CHOICE { + fdd SEQUENCE { + primaryCPICH-Info PrimaryScramblingCode, + ... + }, + tdd SEQUENCE { + cellParameterID CellParameterID, + --- coding is FFS + ... + }, + ... + }, + frequencyInfo FrequencyInfo OPTIONAL, + positioningMode CHOICE { + ueBased SEQUENCE { + cellPosition ReferenceCellPosition OPTIONAL, + -- actual value roundTripTime = (IE value * 0.0625) + 876 + roundTripTime INTEGER (0..32766) OPTIONAL, + ... + }, + ueAssisted SEQUENCE { + ... + }, + ... + }, + ue-positioning-IPDL-Parameters UE-Positioning-IPDL-Parameters OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UE-Positioning-OTDOAReferenceCellInfo-ExtIEs } } OPTIONAL, + ... +} + +UE-Positioning-OTDOAReferenceCellInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + { ID id-ExtendedRoundTripTime CRITICALITY ignore EXTENSION ExtendedRoundTripTime PRESENCE optional }| -- FDD only + { ID id-timingAdvanceLCR-R7 CRITICALITY ignore EXTENSION TimingAdvanceLCR-R7 PRESENCE optional }| -- 1.28Mcps TDD only + { ID id-rxTimingDeviationLCR CRITICALITY ignore EXTENSION RxTimingDeviationLCR PRESENCE optional }| -- 1.28Mcps TDD only +} + +``` + +``` + + { ID id-angleOfArrivalLCR CRITICALITY ignore EXTENSION AngleOfArrivalLCR PRESENCE optional }, -- 1.28Mcps TDD only + ... +} + +``` + +``` + +ReferenceCellPosition ::= CHOICE { + ellipsoidPoint GeographicalCoordinates, + ellipsoidPointWithAltitude GA-PointWithAltitude, + ... +} + +``` + +``` + +UE-Positioning-IPDL-Parameters ::= SEQUENCE { + modeSpecificInfo CHOICE { + fdd SEQUENCE { + ip-Spacing IP-Spacing, + ip-Length IP-Length, + ip-Offset INTEGER (0..9), + seed INTEGER (0..63), + ... + }, + tdd SEQUENCE { + -- coding is FFS + ... + }, + ... + }, + burstModeParameters BurstModeParameters OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UE-Positioning-IPDL-Parameters-ExtIEs } } OPTIONAL, + ... +} + +``` + +``` + +UE-Positioning-IPDL-Parameters-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +IP-Spacing ::= ENUMERATED { + e5, e7, e10, e15, e20, + e30, e40, e50, ... } + +``` + +``` + +IP-Length ::= ENUMERATED { + ipl5, ipl10, ... } + +``` + +``` + +BurstModeParameters ::= SEQUENCE { + burstStart INTEGER (0..15), + burstLength INTEGER (10..25), + burstFreq INTEGER (1..16), + iE-Extensions ProtocolExtensionContainer { { BurstModeParameters-ExtIEs } } OPTIONAL, + ... +} + +``` + +``` + +BurstModeParameters-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +UE-Positioning-OTDOA-NeighbourCellList ::= SEQUENCE (SIZE (1..maxCellMeas)) OF + UE-Positioning-OTDOA-NeighbourCellInfo + +UE-Positioning-OTDOA-NeighbourCellInfo ::= SEQUENCE { + modeSpecificInfo CHOICE { + fdd SEQUENCE { + primaryCPICH-Info PrimaryScramblingCode, + ... + }, + tdd SEQUENCE { + cellParameterID CellParameterID, + -- coding is FFS + ... + }, + ... + }, + frequencyInfo FrequencyInfo OPTIONAL, + ue-positioning-IPDL-Parameters UE-Positioning-IPDL-Parameters OPTIONAL, + sfn-SFN-RelTimeDifference SFN-SFN-RelTimeDifference1, + sfn-Offset-Validity SFN-Offset-Validity OPTIONAL, + sfn-SFN-Drift SFN-SFN-Drift OPTIONAL, + searchWindowSize OTDOA-SearchWindowSize, + positioningMode CHOICE { + ueBased SEQUENCE { + relativeNorth INTEGER (-20000..20000) OPTIONAL, + relativeEast INTEGER (-20000..20000) OPTIONAL, + relativeAltitude INTEGER (-4000..4000) OPTIONAL, + fineSFN-SFN FineSFNSFN OPTIONAL, + -- actual value roundTripTime = (IE value * 0.0625) + 876 + roundTripTime INTEGER (0.. 32766) OPTIONAL, + ... + }, + ueAssisted SEQUENCE { + ... + }, + ... + }, + iE-Extensions ProtocolExtensionContainer { { UE-Positioning-OTDOANeighbourCellInfo-ExtIEs } } OPTIONAL, + ... +} + +UE-Positioning-OTDOANeighbourCellInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + { ID id-ExtendedRoundTripTime CRITICALITY ignore EXTENSION ExtendedRoundTripTime PRESENCE optional }, -- FDD only + ... +} + +``` + +``` + +SFN-SFN-RelTimeDifference1 ::= SEQUENCE { + sfn-Offset INTEGER (0 .. 4095), + sfn-sfn-Reltimedifference INTEGER (0.. 38399), + iE-Extensions ProtocolExtensionContainer { { SFN-SFN-RelTimeDifference1-ExtIEs } } OPTIONAL, + ... +} + +SFN-SFN-RelTimeDifference1-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +SFN-Offset-Validity ::= ENUMERATED { false } + +OTDOA-SearchWindowSize ::= ENUMERATED { + c20, c40, c80, c160, c320, + c640, c1280, moreThan1280, ... } + +SFN-SFN-Drift ::= ENUMERATED { + sfnsfndrift0, sfnsfndrift1, sfnsfndrift2, + sfnsfndrift3, sfnsfndrift4, sfnsfndrift5, + sfnsfndrift8, sfnsfndrift10, sfnsfndrift15, + sfnsfndrift25, sfnsfndrift35, sfnsfndrift50, + sfnsfndrift65, sfnsfndrift80, sfnsfndrift100, + sfnsfndrift-1, sfnsfndrift-2, sfnsfndrift-3, + sfnsfndrift-4, sfnsfndrift-5, sfnsfndrift-8, + sfnsfndrift-10, sfnsfndrift-15, sfnsfndrift-25, + sfnsfndrift-35, sfnsfndrift-50, sfnsfndrift-65, + sfnsfndrift-80, sfnsfndrift-100, ...} + +FineSFNSFN ::= INTEGER (0..15) +-- Range 0..0.9375 step size 0.0625 + +-- ***** +-- +-- Vertical Accuracy Code +-- +-- ***** + +VerticalAccuracyCode ::= INTEGER (0..127) + +-- ***** +-- +-- UTDOA Group +-- +-- ***** + +UTDOA-Group ::= SEQUENCE { + +``` + +``` + + uC-ID UC-ID, + frequencyInfo FrequencyInfo, + uTDOA-ChannelSettings UTDOA-RRState, + iE-Extensions ProtocolExtensionContainer { { UTDOA-Group-ExtIEs } } OPTIONAL, + ... +} + +UTDOA-Group-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +FrequencyInfo ::= SEQUENCE { + modeSpecificInfo CHOICE { + fdd FrequencyInfoFDD, + tdd FrequencyInfoTDD, + ... + }, + iE-Extensions ProtocolExtensionContainer { { FrequencyInfo-ExtIEs } } OPTIONAL, + ... +} + +FrequencyInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +FrequencyInfoFDD ::= SEQUENCE { + uarfcn-UL UARFCN OPTIONAL, + uarfcn-DL UARFCN, + iE-Extensions ProtocolExtensionContainer { { FrequencyInfoFDD-ExtIEs } } OPTIONAL, + ... +} + +FrequencyInfoFDD-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +FrequencyInfoTDD ::= SEQUENCE { + uarfcn UARFCN, + iE-Extensions ProtocolExtensionContainer { { FrequencyInfoTDD-ExtIEs } } OPTIONAL, + ... +} + +FrequencyInfoTDD-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +UTDOA-RRState ::= CHOICE { + uTDOA-CELLDCH UTDOA-CELLDCH, + uTDOA-CELLFACH UTDOA-CELLFACH, +} + +``` + +``` + + ... + } + + -- ***** + -- + -- UTDOA Cell DCH Information + -- + -- ***** + UTDOA-CELLDCH ::= SEQUENCE { + uL-DPCHInfo UL-DPCHInfo, + compressedModeAssistanceData Compressed-Mode-Assistance-Data OPTIONAL, + dCH-Information DCH-Information OPTIONAL, + e-DPCH-Information E-DPCH-Information OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UTDOA-CELLDCH-ExtIEs} } OPTIONAL, + ... + } + + UTDOA-CELLDCH-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + UL-DPCHInfo ::= CHOICE { + fdd SEQUENCE { + scramblingCodeType ScramblingCodeType, + scramblingCode UL-ScramblingCode, + tfci-Existence BOOLEAN, + numberOfFBI-Bits NumberOfFBI-Bits, + iE-Extensions ProtocolExtensionContainer { { UL-DPCHInfoFDD-ExtIEs} } OPTIONAL, + ... + }, + tdd SEQUENCE { + cellParameterID CellParameterID, + tFCI-Coding TFCI-Coding, + punctureLimit PuncturingLimit, + repetitionPeriod RepetitionPeriod, + repetitionLength RepetitionLength, + tdd-DPCHOffset TDD-DPCHOffset, + uL-Timeslot-Information UL-Timeslot-Information, + frameOffset FrameOffset, + specialBurstScheduling SpecialBurstScheduling, + iE-Extensions ProtocolExtensionContainer { { UL-DPCHInfoTDD-ExtIEs} } OPTIONAL, + ... + }, + ... + } + + UL-DPCHInfoFDD-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + +``` + +``` + +UL-DPCHInfoTDD-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +Compressed-Mode-Assistance-Data ::= SEQUENCE { + dl-information DL-InformationFDD, + ul-information UL-InformationFDD, + iE-Extensions ProtocolExtensionContainer { { Compressed-Mode-Assistance-DataFDD-ExtIEs} } OPTIONAL, + ... +} + +Compressed-Mode-Assistance-DataFDD-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +DL-InformationFDD ::= SEQUENCE { + primaryScramblingCode PrimaryScramblingCode, + chipOffset ChipOffset, + frameOffset FrameOffset, + iE-Extensions ProtocolExtensionContainer { { DL-InformationFDD-ExtIEs} } OPTIONAL, + ... +} + +DL-InformationFDD-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +UL-InformationFDD ::= SEQUENCE { + transmissionGapPatternSequenceInfo Transmission-Gap-Pattern-Sequence-Information, + activePatternSequenceInfo Active-Pattern-Sequence-Information, + cFN CFN, + iE-Extensions ProtocolExtensionContainer { { UL-InformationFDD-ExtIEs} } OPTIONAL, + ... +} + +UL-InformationFDD-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +Transmission-Gap-Pattern-Sequence-Information ::= SEQUENCE (SIZE (1..maxTGPS)) OF + SEQUENCE { + tGPSID TGPSID, + tGSN TGSN, + tGL1 GapLength, + tGL2 GapLength OPTIONAL, + tGD TGD, + tGPL1 GapDuration, + uplink-Compressed-Mode-Method Uplink-Compressed-Mode-Method, + iE-Extensions ProtocolExtensionContainer { {Transmission-Gap-Pattern-Sequence-Information-ExtIEs} } OPTIONAL, + ... + } +} + +``` + +``` +Transmission-Gap-Pattern-Sequence-Information-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +TGD ::= INTEGER (0|15..269) +-- 0 = Undefined, only one transmission gap in the transmission gap pattern sequence + +TGPRC ::= INTEGER (0..511) +-- 0 = infinity + +TGPSID ::= INTEGER (1.. maxTGPS) + +TGSN ::= INTEGER (0..14) + +Uplink-Compressed-Mode-Method ::= ENUMERATED { + sFdiv2, + higher-layer-scheduling, + ... +} + +GapDuration ::= INTEGER (1..144,...) +-- Unit frame + +GapLength ::= INTEGER (1..14) +-- Unit slot + +Active-Pattern-Sequence-Information ::= SEQUENCE { + cMConfigurationChangeCFN CFN, + transmission-Gap-Pattern-Sequence-Status Transmission-Gap-Pattern-Sequence-Status-List OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {Active-Pattern-Sequence-Information-ExtIEs} } OPTIONAL, + ... +} + +Active-Pattern-Sequence-Information-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +Transmission-Gap-Pattern-Sequence-Status-List ::= SEQUENCE (SIZE (1..maxTGPS)) OF + SEQUENCE { + tGPSID tGPSID, + tGPRC tGPRC, + tGCFN CFN, + iE-Extensions ProtocolExtensionContainer { { Transmission-Gap-Pattern-Sequence-Status-List-ExtIEs } } OPTIONAL, + ... + } + +Transmission-Gap-Pattern-Sequence-Status-List-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` + +DCH-Information ::= SEQUENCE { + tFCS TFCS, + trChInfo TrChInfoList, + iE-Extensions ProtocolExtensionContainer { { DCH-Information-ExtIEs} } OPTIONAL, + ... +} + +DCH-Information-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +TrChInfoList ::= SEQUENCE (SIZE(1..maxTrCH)) OF + UL-TrCHInfo + +UL-TrCHInfo ::= SEQUENCE { + uL-TrCHType UL-TrCHType, + tfs TransportFormatSet, + iE-Extensions ProtocolExtensionContainer { { UL-TrCHInfo-ExtIEs} } OPTIONAL, + ... +} + +UL-TrCHInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +UL-TrCHType ::= ENUMERATED {dch, usch, ...} + +E-DPCH-Information ::= SEQUENCE { + maxSet-E-DPDCHs Max-Set-E-DPDCHs, + ul-PunctureLimit PuncturingLimit, + e-TFCS-Information E-TFCS-Information, + e-TTI E-TTI, + e-DPCCH-PO E-DPCCH-PO OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { E-DPCH-Information-ExtIEs} } OPTIONAL, + ... +} + +E-DPCH-Information-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +Max-Set-E-DPDCHs ::= ENUMERATED { + vN64, vN32, vN16, vN8, v2xN4, v2xN2, v2xN2plus2xN4, + ... +} +-- Values related to TS 25.212 [16] + +E-TFCS-Information ::= SEQUENCE { + +``` + +Error: + +320 + +Error: Reference source not found + +``` + + e-DCH-TFCS-Index E-DCH-TFCS-Index, + reference-E-TFCI-Information Reference-E-TFCI-Information OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {E-TFCS-Information-ExtIEs} } OPTIONAL, + ... + } + + E-TFCS-Information-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + E-DCH-TFCS-Index ::= INTEGER (1..4,...) + + Reference-E-TFCI-Information ::= SEQUENCE (SIZE (1..maxNrOfRefETFCIs)) OF Reference-E-TFCI-Information-Item + + Reference-E-TFCI-Information-Item ::= SEQUENCE { + reference-E-TFCI E-TFCI, + reference-E-TFCI-PO Reference-E-TFCI-PO, + iE-Extensions ProtocolExtensionContainer { { Reference-E-TFCI-Information-Item-ExtIEs} } OPTIONAL, + ... + } + + Reference-E-TFCI-Information-Item-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + Reference-E-TFCI-PO ::= INTEGER (0.. maxNrOfRefETFCI-PO-QUANTSTEPs) + -- FFS according to mapping in TS 25.213 [17] + + E-TFCI ::= INTEGER (0..127) + + E-TTI ::= ENUMERATED { + e-TTI-2ms, + e-TTI-10ms, + ... + } + + E-DPCCH-PO ::= INTEGER (0..maxNrOfEDPCCH-PO-QUANTSTEPs) + + CellParameterID ::= INTEGER (0..127,...) + + TFCI-Coding ::= ENUMERATED { + v4, + v8, + v16, + v32, + ... + } + + RepetitionLength ::= INTEGER (1..63) + + RepetitionPeriod ::= ENUMERATED { +``` + +Error: + +321 + +Error: Reference source not found + +``` + v1, + v2, + v4, + v8, + v16, + v32, + v64, + ... +} + +TDD-DPCHOffset ::= CHOICE { + initialOffset INTEGER (0..255), + noinitialOffset INTEGER (0..63) +} + +UL-Timeslot-Information ::= SEQUENCE (SIZE (1..maxNrOfULTSs)) OF UL-Timeslot-InformationItem + +maxNrOfULTSs INTEGER ::= 15 +UL-Timeslot-InformationItem ::= SEQUENCE { + timeSlot TimeSlot, + midambleShiftAndBurstType MidambleShiftAndBurstType, + tFCI-Presence BOOLEAN, + uL-Code-InformationList TDD-UL-Code-Information, + iE-Extensions ProtocolExtensionContainer { { UL-Timeslot-InformationItem-ExtIEs} } OPTIONAL, + ... +} + +UL-Timeslot-InformationItem-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +TimeSlot ::= INTEGER (0..14) + +MidambleShiftAndBurstType ::= CHOICE { + type1 SEQUENCE { + midambleConfigurationBurstType1And3 MidambleConfigurationBurstType1And3, + midambleAllocationMode CHOICE { + defaultMidamble NULL, + commonMidamble NULL, + ueSpecificMidamble MidambleShiftLong, + ... + }, + ... + }, + type2 SEQUENCE { + midambleConfigurationBurstType2 MidambleConfigurationBurstType2, + midambleAllocationMode CHOICE { + defaultMidamble NULL, + commonMidamble NULL, + ueSpecificMidamble MidambleShiftShort, + ... + } + } +} +``` + +Error: + +322 + +Error: Reference source not found + +``` + + }, + ... + }, + type3 SEQUENCE { + midambleConfigurationBurstType1And3 MidambleConfigurationBurstType1And3, + midambleAllocationMode CHOICE { + defaultMidamble NULL, + ueSpecificMidamble MidambleShiftLong, + ... + }, + ... + }, + ... +} + +MidambleShiftLong ::= INTEGER (0..15) + +MidambleShiftShort ::= INTEGER (0..5) + +MidambleConfigurationBurstType1And3 ::= ENUMERATED {v4, v8, v16} + +MidambleConfigurationBurstType2 ::= ENUMERATED {v3, v6} + +TDD-UL-Code-Information ::= SEQUENCE (SIZE (1..maxNrOfDPCHs)) OF TDD-UL-Code-InformationItem + +maxNrOfDPCHs INTEGER ::= 240 + +TDD-UL-Code-InformationItem ::= SEQUENCE { + tdd-ChannelisationCode TDD-ChannelisationCode, + iE-Extensions ProtocolExtensionContainer { { TDD-UL-Code-InformationItem-ExtIEs} } OPTIONAL, + ... +} + +TDD-UL-Code-InformationItem-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +TDD-ChannelisationCode ::= ENUMERATED { + chCode1div1, + chCode2div1, + chCode2div2, + chCode4div1, + chCode4div2, + chCode4div3, + chCode4div4, + chCode8div1, + chCode8div2, + chCode8div3, + chCode8div4, + chCode8div5, + chCode8div6, + chCode8div7, +} +``` + +``` + + chCode8div8, + chCode16div1, + chCode16div2, + chCode16div3, + chCode16div4, + chCode16div5, + chCode16div6, + chCode16div7, + chCode16div8, + chCode16div9, + chCode16div10, + chCode16div11, + chCode16div12, + chCode16div13, + chCode16div14, + chCode16div15, + chCode16div16, + ... +} + +SpecialBurstScheduling ::= INTEGER (1..256) -- Number of frames between special burst transmission during DTX + +-- ***** +-- +-- UTDOA Cell Fach Information +-- +-- ***** + +UTDOA-CELLFACH ::= SEQUENCE { + pRACHparameters pRACHparameters, + CRNTI C-RNTI, + uschParameters UschParameters OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { UTDOA-CELLFACH-ExtIEs} } OPTIONAL, + ... +} + +UTDOA-CELLFACH-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +PRACHparameters ::= SEQUENCE (SIZE (1..maxPRACH)) OF + PRACH-ChannelInfo + +PRACH-ChannelInfo ::= SEQUENCE { + pRACH-Info PRACH-Info, + tFS TransportFormatSet, + tFCS TFCS, + iE-Extensions ProtocolExtensionContainer { { PRACH-ChannelInfo-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` + +PRACH-ChannelInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +PRACH-Info ::= CHOICE { + fdd SEQUENCE { + availableSignatures AvailableSignatures, + availableSF SF-PRACH, + preambleScramblingCodeWordNumber PreambleScramblingCodeWordNumber, + puncturingLimit PuncturingLimit, + availableSubChannelNumbers AvailableSubChannelNumbers, + iE-Extensions ProtocolExtensionContainer { { PRACH-Info-FDD-ExtIEs} } OPTIONAL, + ... + }, + tdd SEQUENCE { + timeSlot TimeSlot, + tdd-ChannelisationCode TDD-ChannelisationCode, + maxPRACH-MidambleShifts MaxPRACH-MidambleShifts, + pRACH-Midamble PRACH-Midamble, + iE-Extensions ProtocolExtensionContainer { { PRACH-Info-TDD-ExtIEs} } OPTIONAL, + ... + }, + ... +} + +PRACH-Info-FDD-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +PRACH-Info-TDD-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +SF-PRACH ::= ENUMERATED { + sfpr32, sfpr64, sfpr128, sfpr256, ... } + +AvailableSignatures ::= BIT STRING { + signature15(0), + signature14(1), + signature13(2), + signature12(3), + signature11(4), + signature10(5), + signature9(6), + signature8(7), + signature7(8), + signature6(9), + signature5(10), + signature4(11), + signature3(12), +} + +``` + +``` + + signature2(13), + signature1(14), + signature0(15) + (SIZE(16)) + +PreambleScramblingCodeWordNumber ::= INTEGER (0..15) + +PuncturingLimit ::= INTEGER (0..15) +-- 0: 40%; 1: 44%; ... 14: 96%; 15: 100% + +AvailableSubChannelNumbers ::= BIT STRING { + subCh11(0), + subCh10(1), + subCh9(2), + subCh8(3), + subCh7(4), + subCh6(5), + subCh5(6), + subCh4(7), + subCh3(8), + subCh2(9), + subCh1(10), + subCh0(11) +} (SIZE(12)) + +ScramblingCodeType ::= ENUMERATED { + shortSC, + longSC } + +UL-ScramblingCode ::= INTEGER (0..16777215) + +NumberOfFBI-Bits ::= INTEGER (0..2) + +TransportFormatSet ::= SEQUENCE { + dynamicPart TransportFormatSet-DynamicPartList, + semi-staticPart TransportFormatSet-Semi-staticPart, + iE-Extensions ProtocolExtensionContainer { { TransportFormatSet-ExtIEs} } OPTIONAL, + ... +} + +TransportFormatSet-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +TransportFormatSet-DynamicPartList ::= SEQUENCE (SIZE (1..maxNrOfTFs)) OF + SEQUENCE { + rlc-Size RLC-Size, + numberOfTbsTTIList SEQUENCE (SIZE (1..maxNrOfTFs)) OF TbsTTIInfo, + iE-Extensions ProtocolExtensionContainer { { TransportFormatSet-DynamicPartList-ExtIEs} } OPTIONAL, + ... + } + +``` + +Error: + +326 + +Error: Reference source not found + +``` + - + } + + TransportFormatSet-DynamicPartList-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + TbsTTIInfo ::= SEQUENCE { + tTIInfo TransportFormatSet-TransmissionTimeIntervalDynamic OPTIONAL, + numberOfTbs TransportFormatSet-NrOfTransportBlocks, + iE-Extensions ProtocolExtensionContainer { ( TbsTTIInfo-ExtIEs) } OPTIONAL, + ... + } + + TbsTTIInfo-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + RLC-Size ::= INTEGER (129..5055) + + TransportFormatSet-NrOfTransportBlocks ::= INTEGER (0..512) + + TransportFormatSet-Semi-staticPart ::= SEQUENCE { + transmissionTimeInterval TransportFormatSet-TransmissionTimeIntervalSemiStatic, + channelCoding TransportFormatSet-ChannelCodingType, + codingRate TransportFormatSet-CodingRate OPTIONAL, + -- This IE shall be present if the Type of channel coding IE is set to 'convolutional' or 'turbo' + rateMatchingAttribute TransportFormatSet-RateMatchingAttribute, + cRC-Size TransportFormatSet-CRC-Size, + iE-Extensions ProtocolExtensionContainer { ( TransportFormatSet-Semi-staticPart-ExtIEs) } OPTIONAL, + ... + } + + TransportFormatSet-Semi-staticPart-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... + } + + TransportFormatSet-TransmissionTimeIntervalSemiStatic ::= ENUMERATED { + msec-5, + msec-10, + msec-20, + msec-40, + msec-80, + dynamic, + ... + } + + TransportFormatSet-ChannelCodingType ::= ENUMERATED { + no-codingTDD, + convolutional-coding, + turbo-coding, +``` + +``` + ... +} + +TransportFormatSet-CodingRate ::= ENUMERATED { + half, + third, + ... +} + +TransportFormatSet-RateMatchingAttribute ::= INTEGER (1..maxRateMatching) + +TransportFormatSet-CRC-Size ::= ENUMERATED { + v0, + v8, + v12, + v16, + v24, + ... +} + +TransportFormatSet-TransmissionTimeIntervalDynamic ::= ENUMERATED { + msec-10, + msec-20, + msec-40, + msec-80, + dynamic, + ... +} + +TFCS ::= SEQUENCE (SIZE (1..maxTFC)) OF CTFC + +CTFC ::= CHOICE{ + ctfc2Bit SEQUENCE (SIZE (1..maxTFC)) OF INTEGER (0..3), + ctfc4Bit SEQUENCE (SIZE (1..maxTFC)) OF INTEGER (0..15), + ctfc6Bit SEQUENCE (SIZE (1..maxTFC)) OF INTEGER (0..63), + ctfc8Bit SEQUENCE (SIZE (1..maxTFC)) OF INTEGER (0..255), + ctfc12Bit SEQUENCE (SIZE (1..maxTFC)) OF INTEGER (0..4095), + ctfc16Bit SEQUENCE (SIZE (1..maxTFC)) OF INTEGER (0..65535), + ctfc24Bit SEQUENCE (SIZE (1..maxTFC)) OF INTEGER (0..16777215), + ... +} + +C-RNTI ::= BIT STRING (SIZE (16)) + +UARFCN ::= INTEGER (0..16383) + +CFN ::= INTEGER (0..255) +``` + +``` + +ChipOffset ::= INTEGER (0..38399) +-- Unit Chip + +FrameOffset ::= INTEGER (0..255) + +PrimaryScramblingCode ::= INTEGER (0..511) + +UschParameters ::= SEQUENCE { + cellParameterID CellParameterID, + tFCI-Coding TFCI-Coding, + punctureLimit PuncturingLimit, + repetitionPeriod RepetitionPeriod, + uSCH-SchedulingOffset USCH-SchedulingOffset, + uL-Timeslot-Information UL-Timeslot-Information, + tFCS TFCS, + trChInfo TrChInfoList, + iE-Extensions ProtocolExtensionContainer { { UschParameters-ExtIEs} } OPTIONAL, + ... +} + +UschParameters-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +USCH-SchedulingOffset ::= INTEGER (0..255) + +MaxPRACH-MidambleShifts ::= ENUMERATED { + shift4, + shift8, + ... +} + +PRACH-Midamble ::= ENUMERATED { + inverted, + direct, + ... +} + +--***** +-- +-- Positioning Response Time +-- +--***** + +Positioning-ResponseTime ::= + ENUMERATED { + ms250, ms500, s1, s2, s3, s4, s6, + s8, s12, s16, s20, s24, s28, s32, s64, + ... + } + +--***** +-- + +``` + +``` + +-- Amount of Reporting +-- +--***** + +AmountOfReporting ::= ENUMERATED { ra2, ra4, ra8, ra16, ra32, + ra64, ra-Infinity, ... } + +-- ***** +-- +-- Include Velocity +-- +-- ***** + +IncludeVelocity ::= ENUMERATED { + requested +} + +-- ***** +-- +-- VelocityEstimate +-- +-- ***** + +-- VelocityEstimate is based on Description of Velocity in 23.032 + +VelocityEstimate ::= CHOICE { + horizontalVelocity HorizontalVelocity, + horizontalWithVerticalVelocity HorizontalWithVerticalVelocity, + horizontalVelocityWithUncertainty HorizontalVelocityWithUncertainty, + horizontalWithVerticalVelocityAndUncertainty HorizontalWithVerticalVelocityAndUncertainty, + ... +} + +HorizontalVelocity ::= SEQUENCE { + horizontalSpeedAndBearing HorizontalSpeedAndBearing, + iE-Extensions ProtocolExtensionContainer { { HorizontalVelocity-ExtIEs} } OPTIONAL, + ... +} + +HorizontalVelocity-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +HorizontalWithVerticalVelocity ::= SEQUENCE { + horizontalSpeedAndBearing HorizontalSpeedAndBearing, + verticalVelocity VerticalVelocity, + iE-Extensions ProtocolExtensionContainer { { HorizontalWithVerticalVelocity-ExtIEs} } OPTIONAL, + ... +} + +``` + +``` + +HorizontalWithVerticalVelocity-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +HorizontalVelocityWithUncertainty ::= SEQUENCE { + horizontalSpeedAndBearing HorizontalSpeedAndBearing, + uncertaintySpeed INTEGER (0..255), + iE-Extensions ProtocolExtensionContainer { { HorizontalVelocityWithUncertainty-ExtIEs} } OPTIONAL, + ... +} + +HorizontalVelocityWithUncertainty-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +HorizontalWithVerticalVelocityAndUncertainty ::= SEQUENCE { + horizontalSpeedAndBearing HorizontalSpeedAndBearing, + verticalVelocity VerticalVelocity, + horizontalUncertaintySpeed INTEGER (0..255), + verticalUncertaintySpeed INTEGER (0..255), + iE-Extensions ProtocolExtensionContainer { { HorizontalWithVerticalVelocityAndUncertainty-ExtIEs} } OPTIONAL, + ... +} + +HorizontalWithVerticalVelocityAndUncertainty-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +HorizontalSpeedAndBearing ::= SEQUENCE { + bearing INTEGER (0..359), + horizontalSpeed INTEGER (0..2047) +} + +VerticalVelocity ::= SEQUENCE { + verticalSpeed INTEGER (0..255), + verticalSpeedDirection VerticalSpeedDirection +} + +VerticalSpeedDirection ::= ENUMERATED { + upward, + downward +} + +--***** +-- +-- UTRAN-GPS Reference Time +-- +``` + +``` + +--***** +UTRAN-GPSReferenceTime ::= SEQUENCE { + utran-GPSTimingOfCell INTEGER (0..2322431999999, ...), + uC-ID UC-ID OPTIONAL, + sfn INTEGER (0..4095), + iE-Extensions ProtocolExtensionContainer { { UTRAN-GPSReferenceTime-ExtIEs } } OPTIONAL, + ... +} + +UTRAN-GPSReferenceTime-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +--***** +-- +-- UTRAN-GPS Reference Time Result +-- +--***** + +UTRAN-GPSReferenceTimeResult ::= SEQUENCE { + ue-GPSTimingOfCell INTEGER (0..37158911999999, ...), + uC-ID UC-ID, + sfn INTEGER (0..4095), + iE-Extensions ProtocolExtensionContainer { { UTRAN-GPSReferenceTimeResult-ExtIEs } } OPTIONAL, + ... +} + +UTRAN-GPSReferenceTimeResult-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +--***** +-- +-- UTRAN-GANSS Reference Time Result +-- +--***** + +UTRAN-GANSSReferenceTimeResult ::= SEQUENCE { + ue-GANSSTimingOfCell INTEGER (0..345599999999, ...), + ganss-Time-ID GANSSID OPTIONAL, + ganssTodUncertainty INTEGER(0..127) OPTIONAL, + uC-ID UC-ID, + sfn INTEGER (0..4095), + iE-Extensions ProtocolExtensionContainer { { UTRAN-GANSSReferenceTimeResult-ExtIEs } } OPTIONAL, + ... +} + +``` + +``` + +UTRAN-GANSSReferenceTimeResult-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +END + +``` + +### 9.3.5 Common Definitions + +``` + +-- ************************************************************** +-- +-- Common definitions +-- +-- ************************************************************** + +PCAP-CommonDataTypes { +itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) +umts-Access (20) modules (3) pcap (4) version1 (1) pcap-CommonDataTypes (3) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ************************************************************** +-- +-- Extension constants +-- +-- ************************************************************** + +maxPrivateIEs INTEGER ::= 65535 +maxProtocolExtensions INTEGER ::= 65535 +maxProtocolIEs INTEGER ::= 65535 + +-- ************************************************************** +-- +-- Common Data Types +-- +-- ************************************************************** + +Criticality ::= ENUMERATED { reject, ignore, notify } + +Presence ::= ENUMERATED { optional, conditional, mandatory } + +PrivateIE-ID ::= CHOICE { + local INTEGER (0..65535), + global OBJECT IDENTIFIER +} + +ProcedureCode ::= INTEGER (0..255) + +``` + +``` + +ProtocolIE-ID ::= INTEGER (0..maxProtocolIEs) + +TransactionID ::= CHOICE { + shortTID INTEGER (0..127), + longTID INTEGER (0..32767) +} + +TriggeringMessage ::= ENUMERATED { initiating-message, successful-outcome, unsuccessful-outcome, outcome } + +END + +``` + +### 9.3.6 Constant Definitions + +``` + +-- ***** +-- +-- Constant definitions +-- +-- ***** + +PCAP-Constants { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + umts-Access (20) modules (3) pcap(4) version1 (1) pcap-Constants (4) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +IMPORTS + ProcedureCode, + ProtocolIE-ID +FROM PCAP-CommonDataTypes; + +-- ***** +-- +-- Elementary Procedures +-- +-- ***** + +id-PositionCalculation ProcedureCode ::= 1 +id-InformationExchangeInitiation ProcedureCode ::= 2 +id-InformationReporting ProcedureCode ::= 3 +id-InformationExchangeTermination ProcedureCode ::= 4 +id-InformationExchangeFailure ProcedureCode ::= 5 +id-ErrorIndication ProcedureCode ::= 6 +id-privateMessage ProcedureCode ::= 7 +id-PositionParameterModification ProcedureCode ::= 8 +id-PositionInitiation ProcedureCode ::= 9 + +``` + +Error: + +334 + +Error: Reference source not found + +``` +id-PositionActivation ProcedureCode ::= 10 +id-Abort ProcedureCode ::= 11 +id-PositionPeriodicReport ProcedureCode ::= 12 +id-PositionPeriodicResult ProcedureCode ::= 13 +id-PositionPeriodicTermination ProcedureCode ::= 14 + +-- ***** +-- +-- Lists +-- +-- ***** + +maxNrOfErrors INTEGER ::= 256 +maxSat INTEGER ::= 16 +maxSatAlmanac INTEGER ::= 32 +maxNrOfLevels INTEGER ::= 256 +maxNrOfPoints INTEGER ::= 15 +maxNrOfExpInfo INTEGER ::= 32 +maxNrOfMeasNCell INTEGER ::= 32 +maxNrOfMeasurements INTEGER ::= 16 +maxNrOfSets INTEGER ::= 3 +maxRateMatching INTEGER ::= 256 +maxNrOfTFs INTEGER ::= 32 +maxTTI-count INTEGER ::= 4 +maxTS-1 INTEGER ::= 13 +maxCCTrCH INTEGER ::= 8 +maxTF INTEGER ::= 32 +maxTFC INTEGER ::= 1024 +maxPRACH INTEGER ::= 16 +maxTrCH INTEGER ::= 32 +maxTGPS INTEGER ::= 6 +maxNoOfMeasurements INTEGER ::= 16 +maxCellMeas INTEGER ::= 32 +maxNrOfEDPCCH-PO-QUANTSTEPs INTEGER ::= 8 -- FFS +maxNrOfRefETFCI-PO-QUANTSTEPs INTEGER ::= 8 -- FFS +maxNrOfRefETFCIs INTEGER ::= 8 +maxSet INTEGER ::= 9 +maxGANSSSat INTEGER ::= 64 +maxSgnType INTEGER ::= 8 +maxGANSS INTEGER ::= 8 +maxGANSSSet INTEGER ::= 9 +maxGANSSSatAlmanac INTEGER ::= 36 +maxGANSSClockMod INTEGER ::= 4 +maxGANSS-1 INTEGER ::= 7 +maxNrOfIRATMeasurements INTEGER ::= 16 +maxReportedGERANCells INTEGER ::= 6 +maxIonGridInfo INTEGER ::= 320 +maxAddPos INTEGER ::= 8 +maxBeacons INTEGER ::= 64 +maxBTs INTEGER ::= 32 +maxWLANs INTEGER ::= 64 +``` + +``` + +-- ***** +-- +-- IEs +-- +-- ***** + +id-Cause ProtocolIE-ID ::= 1 +id-CriticalityDiagnostics ProtocolIE-ID ::= 2 +id-GPS-UTRAN-TRU ProtocolIE-ID ::= 3 +id-InformationExchangeID ProtocolIE-ID ::= 4 +id-InformationExchangeObjectType-InfEx-Rprt ProtocolIE-ID ::= 5 +id-InformationExchangeObjectType-InfEx-Rqst ProtocolIE-ID ::= 6 +id-InformationExchangeObjectType-InfEx-Rsp ProtocolIE-ID ::= 7 +id-InformationReportCharacteristics ProtocolIE-ID ::= 8 +id-InformationType ProtocolIE-ID ::= 9 +id-GPS-MeasuredResultsList ProtocolIE-ID ::= 10 +id-MethodType ProtocolIE-ID ::= 11 +id-RefPosition-InfEx-Rqst ProtocolIE-ID ::= 12 +id-RefPosition-InfEx-Rsp ProtocolIE-ID ::= 13 +id-RefPosition-Inf-Rprt ProtocolIE-ID ::= 14 +id-RequestedDataValue ProtocolIE-ID ::= 15 +id-RequestedDataValueInformation ProtocolIE-ID ::= 16 +id-TransactionID ProtocolIE-ID ::= 17 +id-UE-PositionEstimate ProtocolIE-ID ::= 18 +id-CellId-MeasuredResultsSets ProtocolIE-ID ::= 20 +id-OTDOA-MeasurementGroup ProtocolIE-ID ::= 22 +id-AccuracyFulfilmentIndicator ProtocolIE-ID ::= 23 +id-HorizontalAccuracyCode ProtocolIE-ID ::= 24 +id-VerticalAccuracyCode ProtocolIE-ID ::= 25 +id-UTDOA-Group ProtocolIE-ID ::= 26 +id-RequestType ProtocolIE-ID ::= 28 +id-UE-PositioningCapability ProtocolIE-ID ::= 29 +id-UC-id ProtocolIE-ID ::= 30 +id-ResponseTime ProtocolIE-ID ::= 31 +id-PositioningPriority ProtocolIE-ID ::= 32 +id-ClientType ProtocolIE-ID ::= 33 +id-PositioningMethod ProtocolIE-ID ::= 34 +id-UTDOAPositioning ProtocolIE-ID ::= 35 +id-GPSPositioning ProtocolIE-ID ::= 36 +id-OTDOAAssistanceData ProtocolIE-ID ::= 37 +id-Positioning-ResponseTime ProtocolIE-ID ::= 38 +id-EnvironmentCharacterisation ProtocolIE-ID ::= 39 +id-PositionData ProtocolIE-ID ::= 40 +id-IncludeVelocity ProtocolIE-ID ::= 41 +id-VelocityEstimate ProtocolIE-ID ::= 42 +id-rxTimingDeviation768Info ProtocolIE-ID ::= 43 +id-UC-ID-InfEx-Rqst ProtocolIE-ID ::= 44 +id-UE-PositionEstimateInfo ProtocolIE-ID ::= 45 +id-UTRAN-GPSReferenceTime ProtocolIE-ID ::= 46 +id-UTRAN-GPSReferenceTimeResult ProtocolIE-ID ::= 47 +id-UTRAN-GPS-DriftRate ProtocolIE-ID ::= 48 + +``` + +Error: + +336 + +Error: Reference source not found + +| | | +|--------------------------------------|-----------------------| +| id-OTDOA-AddMeasuredResultsInfo | ProtocolIE-ID ::= 49 | +| id-GPS-ReferenceLocation | ProtocolIE-ID ::= 50 | +| id-OTDOA-MeasuredResultsSets | ProtocolIE-ID ::= 51 | +| id-rxTimingDeviation384extInfo | ProtocolIE-ID ::= 55 | +| id-ExtendedRoundTripTime | ProtocolIE-ID ::= 56 | +| id-PeriodicPosCalcInfo | ProtocolIE-ID ::= 57 | +| id-PeriodicLocationInfo | ProtocolIE-ID ::= 58 | +| id-AmountOfReporting | ProtocolIE-ID ::= 59 | +| id-MeasInstructionsUsed | ProtocolIE-ID ::= 60 | +| id-RRCstateChange | ProtocolIE-ID ::= 61 | +| id-PeriodicTerminationCause | ProtocolIE-ID ::= 62 | +| id-MeasurementValidity | ProtocolIE-ID ::= 63 | +| id-roundTripTimeInfoWithType1 | ProtocolIE-ID ::= 64 | +| id-CellIDPositioning | ProtocolIE-ID ::= 66 | +| id-AddMeasurementInfo | ProtocolIE-ID ::= 67 | +| id-Extended-RNC-ID | ProtocolIE-ID ::= 68 | +| id-GNSS-CommonAssistanceData | ProtocolIE-ID ::= 69 | +| id-GNSS-GenericAssistanceDataList | ProtocolIE-ID ::= 70 | +| id-GNSS-MeasuredResultsList | ProtocolIE-ID ::= 71 | +| id-GNSS-UTRAN-TRU | ProtocolIE-ID ::= 72 | +| id-GNSSPositioning | ProtocolIE-ID ::= 73 | +| id-GNSS-PositioningDataSet | ProtocolIE-ID ::= 74 | +| id-GNSS-PositioningMethod | ProtocolIE-ID ::= 75 | +| id-NetworkAssistedGNSSSupport | ProtocolIE-ID ::= 76 | +| id-TUTRANGNSSMeasurementValueInfo | ProtocolIE-ID ::= 77 | +| id-AdditionalGPSAssistDataRequired | ProtocolIE-ID ::= 78 | +| id-AdditionalGnssAssistDataRequired | ProtocolIE-ID ::= 79 | +| id-angleOfArrivalLCR | ProtocolIE-ID ::= 80 | +| id-extendedTimingAdvanceLCR | ProtocolIE-ID ::= 81 | +| id-additionalMeasurementInforLCR | ProtocolIE-ID ::= 82 | +| id-timingAdvanceLCR-R7 | ProtocolIE-ID ::= 83 | +| id-rxTimingDeviationLCR | ProtocolIE-ID ::= 84 | +| id-GPSReferenceTimeUncertainty | ProtocolIE-ID ::= 85 | +| id-GNSS-AddIonoModelReq | ProtocolIE-ID ::= 86 | +| id-GNSS-EarthOrientParaReq | ProtocolIE-ID ::= 87 | +| id-GNSS-Additional-Ionospheric-Model | ProtocolIE-ID ::= 88 | +| id-GNSS-Earth-Orientation-Parameters | ProtocolIE-ID ::= 89 | +| id-GNSS-Additional-Time-Models | ProtocolIE-ID ::= 90 | +| id-GNSS-Additional-Navigation-Models | ProtocolIE-ID ::= 91 | +| id-GNSS-Additional-UTC-Models | ProtocolIE-ID ::= 92 | +| id-GNSS-Auxiliary-Information | ProtocolIE-ID ::= 93 | +| id-GNSS-SBAS-ID | ProtocolIE-ID ::= 94 | +| id-GNSS-SBAS-IDs | ProtocolIE-ID ::= 95 | +| id-GNSS-Signal-IDs | ProtocolIE-ID ::= 96 | +| id-supportGNSSNonNativeADchoices | ProtocolIE-ID ::= 97 | +| id-PositionDataUEbased | ProtocolIE-ID ::= 98 | +| id-gnssCodePhaseAmbiguityExt | ProtocolIE-ID ::= 99 | +| id-gnssIntegerCodePhaseExt | ProtocolIE-ID ::= 100 | +| id-GNSSCarrierPhaseRequested | ProtocolIE-ID ::= 101 | +| id-GNSSMultiFreqMeasRequested | ProtocolIE-ID ::= 102 | +| id-gnssReq-AddIonosphericModel | ProtocolIE-ID ::= 103 | +| id-gnssReq-EarthOrientPara | ProtocolIE-ID ::= 104 | + +``` + +id-ganssAddNavigationModel-req ProtocolIE-ID ::= 105 +id-ganssAddUTCModel-req ProtocolIE-ID ::= 106 +id-ganssAuxInfo-req ProtocolIE-ID ::= 107 +id-GANSS-AlmanacModelChoice ProtocolIE-ID ::= 108 +id-GANSS-alm-keplerianNAVAlmanac ProtocolIE-ID ::= 109 +id-GANSS-alm-keplerianReducedAlmanac ProtocolIE-ID ::= 110 +id-GANSS-alm-keplerianMidiAlmanac ProtocolIE-ID ::= 111 +id-GANSS-alm-keplerianGLONASS ProtocolIE-ID ::= 112 +id-GANSS-alm-ecefsBASAlmanac ProtocolIE-ID ::= 113 +id-UTRAN-GANSSReferenceTimeResult ProtocolIE-ID ::= 114 +id-GANSS-Reference-Time-Only ProtocolIE-ID ::= 115 +id-GANSS-AddADchoices ProtocolIE-ID ::= 116 +id-OTDOA-ReferenceCellInfo ProtocolIE-ID ::= 117 +id-DGNSS-ValidityPeriod ProtocolIE-ID ::= 118 +id-AzimuthAndElevationLSB ProtocolIE-ID ::= 119 +id-completeAlmanacProvided ProtocolIE-ID ::= 120 +id-GPS-Week-Cycle ProtocolIE-ID ::= 121 +id-GANSS-Day-Cycle ProtocolIE-ID ::= 122 +id-ganss-Delta-T ProtocolIE-ID ::= 123 +id-requestedCellIDGERANMeasurements ProtocolIE-ID ::= 124 +id-CellId-IRATMeasuredResultsSets ProtocolIE-ID ::= 125 +id-IMSI ProtocolIE-ID ::= 128 +id-IMEI ProtocolIE-ID ::= 129 +id-GANSS-alm-keplerianBDSAlmanac ProtocolIE-ID ::= 130 +id-BDS-Ionospheric-Grid-Model ProtocolIE-ID ::= 131 +id-DBDS-Correction-Information ProtocolIE-ID ::= 132 +id-BDSIonosphericGridModel ProtocolIE-ID ::= 133 +id-DBDSCorrection ProtocolIE-ID ::= 134 +id-Confidence ProtocolIE-ID ::= 135 +id-ExtraDopplerInfoExtension ProtocolIE-ID ::= 136 +id-GANSS-Confidence ProtocolIE-ID ::= 137 +id-GANSS-ExtraDopplerExtension ProtocolIE-ID ::= 138 +id-Additional-PositioningDataSet ProtocolIE-ID ::= 139 +id-Additional-PositioningMethod ProtocolIE-ID ::= 140 +id-AddPos-MeasuredResults ProtocolIE-ID ::= 141 +id-AddPosSupport ProtocolIE-ID ::= 142 + +``` + +END + +### 9.3.7 Container Definitions + +``` + +-- ***** +-- +-- Container definitions +-- +-- ***** + +PCAP-Containers { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + umts-Access (20) modules (3) pcap(4) version1 (1) pcap-Containers (5) } + +``` + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- \*\*\*\*\* +-- +-- IE parameter types from other modules. +-- +-- \*\*\*\*\* + +IMPORTS + +Criticality, +Presence, +PrivateIE-ID, +ProtocolIE-ID, +maxPrivateIEs, +maxProtocolExtensions, +maxProtocolIEs +FROM PCAP-CommonDataTypes; + +-- \*\*\*\*\* +-- +-- Class Definition for Protocol IEs +-- +-- \*\*\*\*\* + +PCAP-PROTOCOL-IES ::= CLASS { +    &id                  ProtocolIE-ID          UNIQUE, +    &criticality       Criticality, +    &Value, +    &presence          Presence +} +WITH SYNTAX { +    ID                   &id +    CRITICALITY        &criticality +    TYPE               &Value +    PRESENCE           &presence +} + +-- \*\*\*\*\* +-- +-- Class Definition for Protocol Extensions +-- +-- \*\*\*\*\* + +PCAP-PROTOCOL-EXTENSION ::= CLASS { +    &id                  ProtocolIE-ID UNIQUE, +    &criticality       Criticality, +    &Extension, +    &presence          Presence +} + +``` + +WITH SYNTAX { + ID &id + CRITICALITY &criticality + EXTENSION &Extension + PRESENCE &presence +} + +-- ***** +-- +-- Class Definition for Private IEs +-- +-- ***** + +PCAP-PRIVATE-IES ::= CLASS { + &id PrivateIE-ID, + &criticality Criticality, + &Value, + &presence Presence +} +WITH SYNTAX { + ID &id + CRITICALITY &criticality + TYPE &Value + PRESENCE &presence +} + +-- ***** +-- +-- Container for Protocol IEs +-- +-- ***** + +ProtocolIE-Container {PCAP-PROTOCOL-IES : IEsSetParam} ::= + SEQUENCE (SIZE (0..maxProtocolIEs)) OF + ProtocolIE-Field {{IEsSetParam}} + +ProtocolIE-Single-Container {PCAP-PROTOCOL-IES : IEsSetParam} ::= + ProtocolIE-Field {{IEsSetParam}} + +ProtocolIE-Field {PCAP-PROTOCOL-IES : IEsSetParam} ::= SEQUENCE { + id PCAP-PROTOCOL-IES.&id ({IEsSetParam}), + criticality PCAP-PROTOCOL-IES.&criticality ({IEsSetParam}{@id}), + value PCAP-PROTOCOL-IES.&Value ({IEsSetParam}{@id}) +} + +-- ***** +-- +-- Container Lists for Protocol IE Containers +-- +-- ***** + +ProtocolIE-ContainerList {INTEGER : lowerBound, INTEGER : upperBound, PCAP-PROTOCOL-IES : IEsSetParam} ::= + +``` + +``` + + SEQUENCE (SIZE (lowerBound..upperBound)) OF + ProtocolIE-Container {{IEsSetParam}} + +-- ***** +-- +-- Container for Protocol Extensions +-- +-- ***** + +ProtocolExtensionContainer {PCAP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= + SEQUENCE (SIZE (1..maxProtocolExtensions)) OF + ProtocolExtensionField {{ExtensionSetParam}} + +ProtocolExtensionField {PCAP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= SEQUENCE { + id PCAP-PROTOCOL-EXTENSION.&id {{ExtensionSetParam}}, + criticality PCAP-PROTOCOL-EXTENSION.&criticality {{ExtensionSetParam}{@id}}, + extensionValue PCAP-PROTOCOL-EXTENSION.&Extension {{ExtensionSetParam}{@id}} +} + +-- ***** +-- +-- Container for Private IEs +-- +-- ***** + +PrivateIE-Container {PCAP-PRIVATE-IES : IEsSetParam} ::= + SEQUENCE (SIZE (1.. maxPrivateIEs)) OF + PrivateIE-Field {{IEsSetParam}} + +PrivateIE-Field {PCAP-PRIVATE-IES : IEsSetParam} ::= SEQUENCE { + id PCAP-PRIVATE-IES.&id {{IEsSetParam}}, + criticality PCAP-PRIVATE-IES.&criticality {{IEsSetParam}{@id}}, + value PCAP-PRIVATE-IES.&Value {{IEsSetParam}{@id}} +} + +END + +``` + +## 9.4 Message Transfer Syntax + +PCAP shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax, as specified in ITU-T Rec. X.691 [9]. + +# 10 Handling of Unknown, Unforeseen and Erroneous Protocol Data + +## 10.1 General + +Protocol Error cases can be divided into three classes: + +- Transfer Syntax Error. +- Abstract Syntax Error. +- Logical Error. + +Protocol errors can occur in the following functions within a receiving node. + +![Diagram showing the hierarchy of protocol errors in PCAP. A box labeled 'PCAP functional entity' is grouped by a brace with 'Logical Errors' and 'Abstract Syntax Errors'. Below it, a box labeled 'ASN.1 Decoding' is grouped by a brace with 'Transfer Syntax Errors'. A dashed arrow points from 'ASN.1 Decoding' to 'PCAP functional entity'. A solid arrow points upwards from the 'Transfer Syntax Errors' group towards the 'Logical Errors' group.](add887c98f62ded73e823fee389405d3_img.jpg) + +The diagram illustrates the relationship between different types of protocol errors. At the bottom, a box labeled 'ASN.1 Decoding' is associated with 'Transfer Syntax Errors' via a right-facing curly brace. A dashed vertical arrow points from this box up to a top box labeled 'PCAP functional entity'. This top box is associated with 'Logical Errors' and 'Abstract Syntax Errors' via another right-facing curly brace. To the right of the boxes, a long solid vertical arrow points upwards, indicating a hierarchy or flow from Transfer Syntax Errors at the bottom to Logical and Abstract Syntax Errors at the top. + +Diagram showing the hierarchy of protocol errors in PCAP. A box labeled 'PCAP functional entity' is grouped by a brace with 'Logical Errors' and 'Abstract Syntax Errors'. Below it, a box labeled 'ASN.1 Decoding' is grouped by a brace with 'Transfer Syntax Errors'. A dashed arrow points from 'ASN.1 Decoding' to 'PCAP functional entity'. A solid arrow points upwards from the 'Transfer Syntax Errors' group towards the 'Logical Errors' group. + +**Figure 10: Protocol Errors in PCAP** + +The information stated in subclauses 10.2, 10.3 and 10.4, to be included in the message used when reporting an error, is what at minimum shall be included. Other optional information elements within the message may also be included, if available. This is also valid for the case when the reporting is done with a response message. The latter is an exception to what is stated in subclause 4.1. + +## 10.2 Transfer Syntax Error + +A Transfer Syntax Error occurs when the receiver is not able to decode the received physical message. Transfer syntax errors are always detected in the process of ASN.1 decoding. If a Transfer Syntax Error occurs, the receiver should initiate Error Indication procedure with appropriate cause value for the Transfer Syntax protocol error. + +Examples for Transfer Syntax Errors are: + +- Violation of value ranges in ASN.1 definition of messages. e.g.: If an IE has a defined value range of 0 to 10 (ASN.1: INTEGER (0..10)), and 12 will be received, then this will be treated as a transfer syntax error. +- Violation in list element constraints. e.g.: If a list is defined as containing 1 to 10 elements, and 12 elements will be received, than this case will be handled as a transfer syntax error. +- Missing mandatory elements in ASN.1 SEQUENCE definitions (as sent by the originator of the message). +- Wrong order of elements in ASN.1 SEQUENCE definitions (as sent by the originator of the message). + +## 10.3 Abstract Syntax Error + +### 10.3.1 General + +An Abstract Syntax Error occurs when the receiving functional PCAP entity: + +- 1) receives IEs or IE groups that cannot be understood (unknown IE id); +- 2) receives IEs for which the logical range is violated (e.g.: ASN.1 definition: 0 to 15, the logical range is 0 to 10 (values 11 to 15 are undefined), and 12 will be received; this case will be handled as an abstract syntax error using criticality information sent by the originator of the message); +- 3) does not receive IEs or IE groups but according to the specified presence of the concerning object, the IEs or IE groups should have been present in the received message; +- 4) receives IEs or IE groups that are defined to be part of that message in wrong order or with too many occurrences of the same IE or IE group; +- 5) receives IEs or IE groups but according to the conditional presence of the concerning object and the specified condition, the IEs or IE groups should not have been present in the received message. + +Cases 1 and 2 (not comprehended IE/IE group) are handled based on received Criticality information. Case 3 (missing IE/IE group) is handled based on Criticality information and Presence information for the missing IE/IE group specified in the version of the specification used by the receiver. Case 4 (IEs or IE groups in wrong order or with too many occurrences) and Case 5 (erroneously present conditional IEs or IE groups) result in rejecting the procedure. + +If an Abstract Syntax Error occurs, the receiver shall read the remaining message and shall then for each detected Abstract Syntax Error that belong to cases 1-3 act according to the Criticality Information and Presence Information for the IE/IE group due to which Abstract Syntax Error occurred in accordance with subclauses 10.3.4 and 10.3.5. The handling of cases 4 and 5 is specified in subclause 10.3.6. + +### 10.3.2 Criticality Information + +In the PCAP messages there is criticality information set for individual IEs and/or IE groups. This criticality information instructs the receiver how to act when receiving an IE or an IE group that is not comprehended, i.e. the entire item (IE or IE group) which is not (fully or partially) comprehended shall be treated in accordance with its own criticality information as specified in subclause 10.3.4. + +In addition, the criticality information is used in case of the missing IE/IE group abstract syntax error (see subclause 10.3.5). + +The receiving node shall take different actions depending on the value of the Criticality Information. The three possible values of the Criticality Information for an IE/IE group are: + +- Reject IE. +- Ignore IE and Notify Sender. +- Ignore IE. + +The following rules restrict when a receiving entity may consider an IE, an IE group, or an EP not comprehended (not implemented), and when action based on criticality information is applicable: + +1. IE or IE group: When one new or modified IE or IE group is implemented for one EP from a standard version, then other new or modified IEs or IE groups specified for that EP in that standard version shall be considered comprehended by a receiving entity (some may still remain unsupported). +2. EP: The comprehension of different EPs within a standard version or between different standard versions is not mandated. Any EP that is not supported may be considered not comprehended, even if another EP from that standard version is comprehended, and action based on criticality shall be applied. + +### 10.3.3 Presence Information + +For many IEs/IE groups which are optional according to the ASN.1 transfer syntax, PCAP specifies separately if the presence of these IEs/IE groups is optional or mandatory with respect to RNS application by means of the presence field of the concerning object of class PCAP-PROTOCOL-IES, PCAP -PROTOCOL-IES-PAIR, PCAP -PROTOCOL-EXTENSION or PCAP -PRIVATE-IES. + +The presence field of the indicated classes supports three values: + +1. Optional; +2. Conditional; +3. Mandatory. + +If an IE/IE group is not included in a received message and the presence of the IE/IE group is mandatory or the presence is conditional and the condition is true according to the version of the specification used by the receiver, an abstract syntax error occurs due to a missing IE/IE group. + +If an IE/IE group is included in a received message and the presence of the IE/IE group is conditional and the condition is false according to the version of the specification used by the receiver, an abstract syntax error occurs due to this erroneously present conditional IE/IE group. + +### 10.3.4 Not comprehended IE/IE group + +#### 10.3.4.1 Procedure Code + +The receiving node shall treat the different types of received criticality information of the *Procedure Code* IE according to the following: + +##### **Reject IE:** + +- If a message is received with a *Procedure Code* IE marked with "*Reject IE*" which the receiving node does not comprehend, the receiving node shall reject the procedure using the Error Indication procedure. + +##### **Ignore IE and Notify Sender:** + +- If a message is received with a *Procedure Code* IE marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the procedure and initiate the Error Indication procedure. + +**Ignore IE:** + +- If a message is received with a *Procedure Code* IE marked with "*Ignore IE*" which the receiving node does not comprehend, the receiving node shall ignore the procedure. + +When using the Error Indication procedure to reject a procedure or to report an ignored procedure it shall include the *Procedure Code* IE, the *Triggering Message* IE, and the *Procedure Criticality* IE in the *Criticality Diagnostics* IE. + +### 10.3.4.1A Type of Message + +When the receiving node cannot decode the *Type of Message* IE, the Error Indication procedure shall be initiated with an appropriate cause value. + +### 10.3.4.2 IEs other than the Procedure Code and Type of Message + +The receiving node shall treat the different types of received criticality information of an IE/IE group other than the *Procedure Code* IE and *Type of Message* IE according to the following: + +**Reject IE:** + +- If a message *initiating* a procedure is received containing one or more IEs/IE groups marked with "*Reject IE*" which the receiving node does not comprehend; none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the rejection of one or more IEs/IE groups using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- If a message *initiating* a procedure that does not have a message to report unsuccessful outcome is received containing one or more IEs/IE groups marked with "*Reject IE*" which the receiving node does not comprehend, the receiving node shall terminate the procedure and initiate the Error Indication procedure. +- If a *response* message is received containing one or more IEs/IE groups marked with "*Reject IE*", that the receiving node does not comprehend, the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling. + +**Ignore IE and Notify Sender:** + +- If a message *initiating* a procedure is received containing one or more IEs/IE groups marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups, and report in the response message of the procedure that one or more IEs/IE groups have been ignored. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the response message, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- If a message *initiating* a procedure that does not have a message to report the outcome of the procedure is received containing one or more IEs/IE groups marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, + +continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups, and initiate the Error Indication procedure to report that one or more IEs/IE groups have been ignored. + +- If a *response* message is received containing one or more IEs/IE groups marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups and initiate the Error Indication procedure. + +#### Ignore IE: + +- If a message *initiating* a procedure is received containing one or more IEs/IE groups marked with "*Ignore IE*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups and continue with the procedure as if the not comprehended IEs/IE groups were not received using the understood IEs/IE groups. +- If a *response* message is received containing one or more IEs/IE groups marked with "*Ignore IE*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups. + +When reporting not comprehended IEs/IE groups marked with "*Reject IE*" or "*Ignore IE and Notify Sender*" using a response message defined for the procedure, the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group. The *Repetition Number* IE shall be included in the *Information Element Criticality Diagnostics* IE if the reported IE/IE group was part of a "SEQUENCE OF" definition. + +When reporting not comprehended IEs/IE groups marked with "*Reject IE*" or "*Ignore IE and Notify Sender*" using the Error Indication procedure, the *Procedure Code* IE, the *Triggering Message* IE, *Procedure Criticality* IE, the *Transaction Id* IE, and the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group. The *Repetition Number* IE shall be included in the *Information Element Criticality Diagnostics* IE if the reported IE/IE group was part of a "SEQUENCE OF" definition. + +### 10.3.5 Missing IE or IE group + +The receiving node shall treat the missing IE/IE group according to the criticality information for the missing IE/IE group in the received message specified in the version of the present document used by the receiver: + +#### Reject IE: + +- If a received message *initiating* a procedure is missing one or more IEs/IE groups with specified criticality "*Reject IE*"; none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the missing IEs/IE groups using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- If a received message *initiating* a procedure that does not have a message to report unsuccessful outcome is missing one or more IEs/IE groups with specified criticality "*Reject IE*", the receiving node shall initiate the Error Indication procedure. +- If a received *response* message is missing one or more IEs/IE groups with specified criticality "*Reject IE*", the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling. + +**Ignore IE and Notify Sender:** + +- If a received message *initiating* a procedure is missing one or more IEs/IE groups with specified criticality "*Ignore IE and Notify Sender*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and report in the response message of the procedure that one or more IEs/IE groups were missing. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the response message, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- If a received message *initiating* a procedure that does not have a message to report the outcome of the procedure is missing one or more IEs/IE groups with specified criticality "*Ignore IE and Notify Sender*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and initiate the Error Indication procedure to report that one or more IEs/IE groups were missing. +- If a received *response* message is missing one or more IEs/IE groups with specified criticality "*Ignore IE and Notify Sender*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and initiate the Error Indication procedure to report that one or more IEs/IE groups were missing. + +**Ignore IE:** + +- If a received message *initiating* a procedure is missing one or more IEs/IE groups with specified criticality "*Ignore IE*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message. +- If a received *response* message is missing one or more IEs/IE groups with specified criticality "*Ignore IE*", the receiving node shall ignore that those IEs/IE groups are missing. + +When reporting missing IEs/IE groups with specified criticality "*Reject IE*" or "*Ignore IE and Notify Sender*" using a response message defined for the procedure, the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group. + +When reporting missing IEs/IE groups with specified criticality "*Reject IE*" or "*Ignore IE and Notify Sender*" using the Error Indication procedure, the *Procedure Code* IE, the *Triggering Message* IE, *Procedure Criticality* IE, the *Transaction Id* IE, and the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group. + +## 10.3.6 IEs or IE groups received in wrong order or with too many occurrences or erroneously present + +If a message with IEs or IE groups in wrong order or with too many occurrences is received or if IEs or IE groups with a conditional presence are present when the condition is not met (i.e. erroneously present), the receiving node shall behave according to the following: + +- If a message *initiating* a procedure is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the cause value "Abstract Syntax Error (Falsely Constructed Message)" using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication. + +- If a message *initiating* a procedure that does not have a message to report unsuccessful outcome is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, the receiving node shall terminate the procedure and initiate the Error Indication procedure, and use cause value "Abstract Syntax Error (Falsely Constructed Message)". +- If a *response* message is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling. + +## 10.4 Logical Error + +Logical error situations occur when a message is comprehended correctly, but the information contained within the message is not valid (i.e. semantic error), or describes a procedure which is not compatible with the state of the receiver. In these conditions, the following behaviour shall be performed (unless otherwise specified) as defined by the class of the elementary procedure, irrespective of the criticality of the IEs/IE groups containing the erroneous values. + +### Class 1: + +Protocol Causes: + +Where the logical error occurs in a request message of a class 1 procedure, and the procedure has a message to report this unsuccessful outcome, this message shall be sent with an appropriate cause value. Typical cause values are: + +1. Semantic Error. +2. Message not compatible with receiver state. + +Where the logical error is contained in a request message of a class 1 procedure, and the procedure does not have a message to report this unsuccessful outcome, the procedure shall be terminated and the Error Indication procedure shall be initiated with an appropriate cause value. + +Where the logical error exists in a response message of a class 1 procedure, the procedure shall be considered as unsuccessfully terminated and local error handling shall be initiated. + +### Class 2: + +Where the logical error occurs in a message of a class 2 procedure, the procedure shall be terminated and the Error Indication procedure shall be initiated with an appropriate cause value. + +## 10.5 Exceptions + +The error handling for all the cases described hereafter shall take precedence over any other error handling described in the other subclauses of clause 10. + +- If any type of error (Transfer Syntax Error, Abstract Syntax Error or Logical Error) is detected in the ERROR INDICATION message, it shall not trigger the Error Indication procedure in the receiving Node but local error handling. + +- In case a response message or Error Indication message needs to be returned, but the information necessary to determine the receiver of that message is missing, the procedure shall be considered as unsuccessfully terminated and local error handling shall be initiated. +- If an error that terminates a procedure occurs, the returned cause value shall reflect the error that caused the termination of the procedure even if one or more abstract syntax errors with criticality "ignore and notify" have earlier occurred within the same procedure. + +## Annex A (informative): Guidelines for Usage of the Criticality Diagnostics IE + +### A.1 EXAMPLE MESSAGE Layout + +Assume the following message format: + +Table A.1 + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | +|----------------|----------|-----------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | | | YES | Reject | +| Transaction ID | M | | | | - | | +| A | M | | | | YES | reject | +| B | M | | | | YES | reject | +| >E | | 1.. | | | EACH | ignore | +| >>F | | 1.. | | | - | | +| >>>G | | 0..3, ... | | | EACH | ignore | +| >>H | | 1.. | | | EACH | ignore | +| >>>G | | 0..3, ... | | | EACH | ignore and notify | +| >>G | M | | | | YES | reject | +| >>J | | 1.. | | | - | | +| >>>G | | 0..3, ... | | | EACH | reject | +| C | M | | | | YES | reject | +| >K | | 1.. | | | EACH | ignore and notify | +| >>L | | 1.. | | | - | | +| >>>M | O | | | | - | | +| D | M | | | | YES | reject | + +NOTE: The IEs F, J, and L do not have assigned criticality. The IEs F, J, and L are consequently realised as the ASN.1 type SEQUENCE OF of "ordinary" ASN.1 type, e.g. INTEGER. On the other hand, the repeatable IEs with assigned criticality are realised as the ASN.1 type SEQUENCE OF of an IE object, e.g. ProtocolIE-Single-Container. + +For the corresponding ASN.1 layout, see clause A.4. + +### A.2 Example on a Received EXAMPLE MESSAGE + +Assume further more that a received message based on the above tabular format is according to figure A.1. + +Error: + +350 + +Error: Reference source not found + +![A hierarchical diagram showing the content of a received PCAP message across four levels. Level 1 (top level) contains A, B, C, and D. Level 2 contains E (under B) and K (under C). Level 3 contains F (dashed box, under E), H (under E), G (under E), J (dashed box, under K), and L (dashed box, under K). Level 4 contains seven G boxes, each with multiple repetitions indicated by overlapping boxes. A legend below explains the repetition notation (1st, 2nd, Nth) and the box types (solid for protocol container, dashed for ordinary ASN.1 type).](a436856945c27adc69a909bde2da601f_img.jpg) + +Level 1 (top level) + +Level 2 + +Level 3 + +Level 4 + +Legend: + +1st repetition + +2nd repetition + +⋮ + +Nth repetition + +IE based on a protocol container, e.g., Protocol-Single-Container + +IE being an "ordinary" ASN.1 type + +A hierarchical diagram showing the content of a received PCAP message across four levels. Level 1 (top level) contains A, B, C, and D. Level 2 contains E (under B) and K (under C). Level 3 contains F (dashed box, under E), H (under E), G (under E), J (dashed box, under K), and L (dashed box, under K). Level 4 contains seven G boxes, each with multiple repetitions indicated by overlapping boxes. A legend below explains the repetition notation (1st, 2nd, Nth) and the box types (solid for protocol container, dashed for ordinary ASN.1 type). + +Figure A.1: Example of content of a received PCAP message based on the EXAMPLE MESSAGE + +# A.3 Content of Criticality Diagnostics + +## A.3.1 Example 1 + +![A hierarchical diagram of Information Elements (IEs) across four levels. Level 1 (top level) contains A, B, C, and D. Level 2 contains E (with sub-elements 1, 2, 3, 4) and K. Level 3 contains F (dashed box), H, G (with sub-element 5), J (dashed box), and L (dashed box). Level 4 contains multiple G instances with sub-elements (e.g., G 1 with sub-elements 1, 2, 3; G 10 with sub-elements 1, 2, 3, 4). Arrows indicate relationships: B points to E and K; C points to K; E points to F, H, G, J, and L; K points to J and L. Annotations include 'Included in the Message Structure IE.' pointing to B and C, and 'Included in the Information Element Criticality Diagnostics IE:' pointing to a grey box in G 10. A list below the annotation includes 'a) IE ID IE' and 'b) Repetition Number IE'.](937e2ba1c4e643eefca0ecdc2b25a26d_img.jpg) + +Level 1 (top level) + +Level 2 + +Level 3 + +Level 4 + +Included in the *Message Structure IE.* + +Included in the *Information Element Criticality Diagnostics IE:* + +- a) *IE ID IE* +- b) *Repetition Number IE* + +A hierarchical diagram of Information Elements (IEs) across four levels. Level 1 (top level) contains A, B, C, and D. Level 2 contains E (with sub-elements 1, 2, 3, 4) and K. Level 3 contains F (dashed box), H, G (with sub-element 5), J (dashed box), and L (dashed box). Level 4 contains multiple G instances with sub-elements (e.g., G 1 with sub-elements 1, 2, 3; G 10 with sub-elements 1, 2, 3, 4). Arrows indicate relationships: B points to E and K; C points to K; E points to F, H, G, J, and L; K points to J and L. Annotations include 'Included in the Message Structure IE.' pointing to B and C, and 'Included in the Information Element Criticality Diagnostics IE:' pointing to a grey box in G 10. A list below the annotation includes 'a) IE ID IE' and 'b) Repetition Number IE'. + +**Figure A.2: Example of a received PCAP message containing a not comprehended IE** + +If there is an error within the instance marked as grey in the IE G in the IE J shown in the figure A.2, this will be reported within the *Information Element Criticality Diagnostics IE* within the *Criticality Diagnostics IE* as in table A.2. + +**Table A.2** + +| IE name | Value | Comment | +|---------------------------------------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IE Criticality | Reject | Criticality for IE on the reported level, i.e. level 4. | +| IE ID | id-G | IE ID from the reported level, i.e. level 4. | +| Repetition Number | 11 | Repetition number on the reported level, i.e. level 4.
(Since the IE E (level 2) is the lowest level included in the Message Structure IE this is the eleventh occurrence of IE G within the IE E (level 2).) | +| Type of Error | not understood | | +| Message Structure, first repetition | | | +| >IE ID | id-B | IE ID from level 1. | +| Message Structure, second repetition | | | +| >IE ID | id-E | IE ID from the lowest level above the reported level, i.e. level 2. | +| >Repetition Number | 3 | Repetition number from the lowest level above the reported level, i.e. level 2. | + +NOTE 1: The IE J on level 3 cannot be included in the *Message Structure* IE since they have no criticality of their own. + +NOTE 2: The repetition number of the reported IE indicates the number of repetitions of IE G received up to the detected erroneous repetition, counting all occurrences of the IE G below the same instance of the previous level with assigned criticality (instance 3 of IE E on level 2). + +## A.3.2 Example 2 + +![A hierarchical diagram showing four levels of Information Elements (IEs). Level 1 (top level) contains A, B, C, and D. Level 2 contains E (under B) and K (under C, with instances 1, 2, 3). Level 3 contains F (dashed box, under E), H (under E), G (under E), J (dashed box, under K1), and L (dashed box, under K2, with a grey shaded second instance). Level 4 contains multiple G boxes under each Level 3 box. Annotations include: 'Included in the Message Structure IE.' pointing to C and K; and 'Included in the Information Element Criticality Diagnostics IE:' with sub-items 'a) IE ID IE' and 'b) Repetition Number IE' pointing to the grey shaded instance in L.](4141e32339a99ae82b6360896250e1fc_img.jpg) + +Level 1 (top level) + +Level 2 + +Level 3 + +Level 4 + +Included in the *Message Structure IE*. + +Included in the *Information Element Criticality Diagnostics IE*: + +- a) *IE ID IE* +- b) *Repetition Number IE* + +A hierarchical diagram showing four levels of Information Elements (IEs). Level 1 (top level) contains A, B, C, and D. Level 2 contains E (under B) and K (under C, with instances 1, 2, 3). Level 3 contains F (dashed box, under E), H (under E), G (under E), J (dashed box, under K1), and L (dashed box, under K2, with a grey shaded second instance). Level 4 contains multiple G boxes under each Level 3 box. Annotations include: 'Included in the Message Structure IE.' pointing to C and K; and 'Included in the Information Element Criticality Diagnostics IE:' with sub-items 'a) IE ID IE' and 'b) Repetition Number IE' pointing to the grey shaded instance in L. + +**Figure A.3: Example of a received PCAP message containing a not comprehended IE** + +If there is an error within the second instance (marked as grey) in the sequence (IE L in the tabular format) on level 3 below IE K in the structure shown in the figure A.3, this will be reported within the *Information Element Criticality Diagnostics IE* within the *Criticality Diagnostics IE* as in table A.3. + +**Table A.3** + +| IE name | Value | Comment | +|--------------------------------------------|-------------------|---------------------------------------------------------------------| +| IE Criticality | ignore and notify | Criticality for IE on the reported level, i.e. level 2. | +| IE ID | id-K | IE ID from the reported level, i.e. level 2. | +| Repetition Number | 3 | Repetition number on the reported level, i.e. level 2. | +| Type of Error | not understood | | +| Message Structure, first repetition | | | +| >IE ID | id-C | IE ID from the lowest level above the reported level, i.e. level 1. | + +NOTE: The IE L on level 3 cannot be reported individually included in the *Message Structure* IE since it has no criticality of its own. + +### A.3.3 Example 3 + +![A hierarchical diagram of Information Elements (IEs) across four levels. Level 1 (top level) contains A, B, C, and D. Level 2 contains E (with sub-indices 1, 2, 3, 4) and K. Level 3 contains F (dashed box), H (with sub-indices 1, 2), G, J (dashed box), and L (dashed box). Level 4 contains multiple instances of G. Arrows indicate relationships: from C to B, from B to E, from E to H, and from a grey-shaded instance of G in H to another instance of G in Level 4. Text labels indicate that B and C are 'Included in the Message Structure IE.' and that the grey instance in H is 'Included in the Information Element Criticality Diagnostics IE: a) IE ID IE b) Repetition Number IE'.](bc19609ef2fbd9f6ddd2f8b857539802_img.jpg) + +Level 1 (top level) + +Level 2 + +Level 3 + +Level 4 + +Included in the *Message Structure IE.* + +Included in the *Information Element Criticality Diagnostics IE:* + +- a) *IE ID IE* +- b) *Repetition Number IE* + +A hierarchical diagram of Information Elements (IEs) across four levels. Level 1 (top level) contains A, B, C, and D. Level 2 contains E (with sub-indices 1, 2, 3, 4) and K. Level 3 contains F (dashed box), H (with sub-indices 1, 2), G, J (dashed box), and L (dashed box). Level 4 contains multiple instances of G. Arrows indicate relationships: from C to B, from B to E, from E to H, and from a grey-shaded instance of G in H to another instance of G in Level 4. Text labels indicate that B and C are 'Included in the Message Structure IE.' and that the grey instance in H is 'Included in the Information Element Criticality Diagnostics IE: a) IE ID IE b) Repetition Number IE'. + +**Figure A.4: Example of a received PCAP message containing a not comprehended IE** + +If there is an error within the instance marked as grey in the IE G in the IE H shown in the figure A.4, this will be reported within the *Information Element Criticality Diagnostics IE* within the *Criticality Diagnostics IE* as in table A.4. + +**Table A.4** + +| IE name | Value | Comment | +|---------------------------------------------|-------------------|---------------------------------------------------------------------------------| +| IE Criticality | ignore and notify | Criticality for IE on the reported level, i.e. level 4. | +| IE ID | id-G | IE ID from the reported level, i.e. level 4. | +| Repetition Number | 2 | Repetition number on the reported level, i.e. level 4. | +| Type of Error | not understood | | +| Message Structure, first repetition | | | +| >IE ID | id-B | IE ID from level 1. | +| Message Structure, second repetition | | | +| >IE ID | id-E | IE ID from level 2. | +| >Repetition Number | 3 | Repetition number from level 2. | +| Message Structure, third repetition | | | +| >IE ID | id-H | IE ID from the lowest level above the reported level, i.e. level 3. | +| >Repetition Number | 1 | Repetition number from the lowest level above the reported level, i.e. level 3. | + +NOTE: The repetition number of level 4 indicates the number of repetitions of IE G received up to the detected erroneous repetition, counted below the same instance of the previous level with assigned criticality (instance 1 of IE H on level 3). + +### A.3.4 Example 4 + +![A hierarchical tree diagram showing information elements (IEs) across four levels. Level 1 (top level) contains A, B, C, and D. Level 2 contains E (under B), K (under C), and D. Level 3 contains F (under E), H (under E), G (under E, shaded grey), J (under E), and L (under K). Level 4 contains multiple instances of G (under F, H, G, J, and L). Arrows indicate that E and K are included in the Message Structure IE, and the shaded G is included in the Information Element Criticality Diagnostics IE.](febfdd6a7182116484c126105b53fdaf_img.jpg) + +Level 1 (top level) + +Level 2 + +Level 3 + +Level 4 + +Included in the *Message Structure IE*. + +Included in the *Information Element Criticality Diagnostics IE*: + +- a) *IE ID IE* +- b) *Repetition Number IE* + +A hierarchical tree diagram showing information elements (IEs) across four levels. Level 1 (top level) contains A, B, C, and D. Level 2 contains E (under B), K (under C), and D. Level 3 contains F (under E), H (under E), G (under E, shaded grey), J (under E), and L (under K). Level 4 contains multiple instances of G (under F, H, G, J, and L). Arrows indicate that E and K are included in the Message Structure IE, and the shaded G is included in the Information Element Criticality Diagnostics IE. + +**Figure A.5: Example of a received PCAP message containing a not comprehended IE** + +If there is an error within the instance marked as grey in the IE G in the IE E shown in the figure A.5, this will be reported within the *Information Element Criticality Diagnostics IE* within the *Criticality Diagnostics IE*, as in table A.5. + +**Table A.5** + +| IE name | Value | Comment | +|---------------------------------------------|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IE Criticality | Reject | Criticality for IE on the reported level, i.e. level 3. | +| IE ID | id-G | IE ID from the reported level, i.e. level 3. | +| Repetition Number | 5 | Repetition number on the reported level, i.e. level 3.
(Since the IE E (level 2) is the lowest level included in the Message Structure IE this is the fifth occurrence of IE G within the IE E (level 2).) | +| Type of Error | not understood | | +| Message Structure, first repetition | | | +| >IE ID | id-B | IE ID from level 1. | +| Message Structure, second repetition | | | +| >IE ID | id-E | IE ID from the lowest level above the reported level, i.e. level 2. | +| >Repetition Number | 3 | Repetition number from the lowest level above the reported level, i.e. level 2. | + +NOTE: The repetition number of the reported IE indicates the number of repetitions of IE G received up to the detected erroneous repetition, counting all occurrences of the IE G below the same instance of the previous level with assigned criticality (instance 3 of IE E on level 2). + +### A.3.5 Example 5 + +![A hierarchical diagram of Information Elements (IEs) across four levels. Level 1 (top level) contains A, B, C, and D. Level 2 contains E (connected to B) and K (connected to C). Level 3 contains F (dashed box, connected to E), H (connected to E), G (grey box, connected to E), J (dashed box, connected to E), and L (dashed box, connected to K). Level 4 contains multiple instances of G: G1, G2, G3 (under F); G4 (under H); G5, G6, G7 (under H); G8 (under G); G9, G10, G11 (under J); and G12, G13 (under L). Annotations include 'Included in the Message Structure IE.' pointing to B and C, and 'Included in the Information Element Criticality Diagnostics IE:' with sub-items 'a) IE ID IE' and 'b) Repetition Number IE' pointing to G4.](e7511e4fa0a0df6c02eb793c62524690_img.jpg) + +Level 1 (top level) + +Level 2 + +Level 3 + +Level 4 + +Included in the *Message Structure IE*. + +Included in the *Information Element Criticality Diagnostics IE*: + +- a) *IE ID IE* +- b) *Repetition Number IE* + +A hierarchical diagram of Information Elements (IEs) across four levels. Level 1 (top level) contains A, B, C, and D. Level 2 contains E (connected to B) and K (connected to C). Level 3 contains F (dashed box, connected to E), H (connected to E), G (grey box, connected to E), J (dashed box, connected to E), and L (dashed box, connected to K). Level 4 contains multiple instances of G: G1, G2, G3 (under F); G4 (under H); G5, G6, G7 (under H); G8 (under G); G9, G10, G11 (under J); and G12, G13 (under L). Annotations include 'Included in the Message Structure IE.' pointing to B and C, and 'Included in the Information Element Criticality Diagnostics IE:' with sub-items 'a) IE ID IE' and 'b) Repetition Number IE' pointing to G4. + +**Figure A.6: Example of a received PCAP message with a missing IE** + +If the instance marked as grey in the IE G in the IE E shown in the figure A.6, is missing this will be reported within the *Information Element Criticality Diagnostics IE* within the *Criticality Diagnostics IE*, as in table A.6. + +Table A.6 + +| IE name | Value | Comment | +|---------------------------------------------|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IE Criticality | reject | Criticality for IE on the reported level, i.e. level 3. | +| IE ID | id-G | IE ID from the reported level, i.e. level 3. | +| Repetition Number | 4 | Repetition number up to the missing IE on the reported level, i.e. level 3.
(Since the IE E (level 2) is the lowest level included in the Message Structure IE there have been four occurrences of IE G within the IE E (level 2) up to the missing occurrence. | +| Type of Error | missing | | +| Message Structure, first repetition | | | +| >IE ID | id-B | IE ID from level 1. | +| Message Structure, second repetition | | | +| >IE ID | id-E | IE ID from the lowest level above the reported level, i.e. level 2. | +| >Repetition Number | 3 | Repetition number from the lowest level above the reported level, i.e. level 2. | + +NOTE: The repetition number of the reported IE indicates the number of repetitions of IE G received up to but not including the missing occurrence, counting all occurrences of the IE G below the same instance of the previous level with assigned criticality (instance 3 of IE E on level 2). + +## A.4 ASN.1 of EXAMPLE MESSAGE + +``` + +ExampleMessage ::= SEQUENCE { + ProtocolIEs ProtocolIE-Container {{ExampleMessage-IEs}}, + ProtocolExtensions ProtocolExtensionContainer {{ExampleMessage-Extensions}} OPTIONAL, + ... +} + +ExampleMessage-IEs PCAP-PROTOCOL-IES ::= { + { ID id-A CRITICALITY reject TYPE A PRESENCE mandatory} | + { ID id-B CRITICALITY reject TYPE B PRESENCE mandatory} | + { ID id-C CRITICALITY reject TYPE C PRESENCE mandatory} | + { ID id-D CRITICALITY reject TYPE D PRESENCE mandatory} , + ... +} + +B ::= SEQUENCE { + e E-List, + iE-Extensions ProtocolExtensionContainer { {B-ExtIEs} } OPTIONAL, + ... +} + +B-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` +E-List ::= SEQUENCE (SIZE (1..maxE)) OF ProtocolIE-Single-Container { {E-IEs} } + +E-IEs PCAP-PROTOCOL-IES ::= { + { ID id-E CRITICALITY ignore TYPE E PRESENCE mandatory } +} + +E ::= SEQUENCE { + f F-List, + h H-List, + g G-List1, + j J-List, + iE-Extensions ProtocolExtensionContainer { {E-ExtIEs} } OPTIONAL, + ... +} + +E-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +F-List ::= SEQUENCE (SIZE (1..maxF)) OF F + +F ::= SEQUENCE { + g G-List2 OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {F-ExtIEs} } OPTIONAL, + ... +} + +F-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +G-List2 ::= SEQUENCE (SIZE (1..3, ...)) OF ProtocolIE-Single-Container { {G2-IEs} } + +G2-IEs PCAP-PROTOCOL-IES ::= { + { ID id-G CRITICALITY ignore TYPE G PRESENCE mandatory } +} + +H-List ::= SEQUENCE (SIZE (1..maxH)) OF ProtocolIE-Single-Container { {H-IEs} } + +H-IEs PCAP-PROTOCOL-IES ::= { + { ID id-H CRITICALITY ignore TYPE H PRESENCE mandatory } +} + +H ::= SEQUENCE { + g G-List3 OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {H-ExtIEs} } OPTIONAL, + ... +} + +H-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +``` + - +} + +G-List3 ::= SEQUENCE (SIZE (1..3, ...)) OF ProtocolIE-Single-Container { {G3-IEs} } + +G3-IEs PCAP-PROTOCOL-IES ::= { + { ID id-G CRITICALITY notify TYPE G PRESENCE mandatory } +} + +G-List1 ::= ProtocolIE-Single-Container { {G1-IEs} } + +G1-IEs PCAP-PROTOCOL-IES ::= { + { ID id-G CRITICALITY reject TYPE G PRESENCE mandatory } +} + +J-List ::= SEQUENCE (SIZE (1..maxJ)) OF J + +J ::= SEQUENCE { + g G-List4 OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {J-ExtIEs} } OPTIONAL, + ... +} + +J-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +G-List4 ::= SEQUENCE (SIZE (1..3, ...)) OF ProtocolIE-Single-Container { {G4-IEs} } + +G4-IEs PCAP-PROTOCOL-IES ::= { + { ID id-G CRITICALITY reject TYPE G PRESENCE mandatory } +} + +C ::= SEQUENCE { + k K-List, + iE-Extensions ProtocolExtensionContainer { {C-ExtIEs} } OPTIONAL, + ... +} + +C-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +K-List ::= SEQUENCE (SIZE (1..maxK)) OF ProtocolIE-Single-Container { {K-IEs} } + +K-IEs PCAP-PROTOCOL-IES ::= { + { ID id-K CRITICALITY notify TYPE K PRESENCE mandatory } +} + +K ::= SEQUENCE { + l L-List, + iE-Extensions ProtocolExtensionContainer { {K-ExtIEs} } OPTIONAL, + ... +} +``` + +Error: + +363 + +Error: Reference source not found + +``` + - +} + +K-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +L-List ::= SEQUENCE (SIZE (1..maxL)) OF L + +L ::= SEQUENCE { + m M OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {L-ExtIEs} } OPTIONAL, + ... +} + +L-ExtIEs PCAP-PROTOCOL-EXTENSION ::= { + ... +} + +ExampleMessage-Extensions PCAP-PROTOCOL-EXTENSION ::= { + ... +} +``` + +## Annex B (informative): Change History + +| TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|---------|-----------|------|-----|-------------------------------------------------------------------------------------------------|--------| +| 12/2008 | - | - | - | Creation of Rel-8 version based on v 7.11.0 | 8.0.0 | +| 42 | RP-080852 | 0115 | 1 | Support for additional navigation satellite systems in PCAP | 8.0.0 | +| 43 | RP-090076 | 0117 | | PCAP Review | 8.1.0 | +| 43 | RP-090076 | 0118 | | Correction to Additional GANSS Assistance Data Required IE | 8.1.0 | +| 45 | RP-090770 | 0119 | 1 | Correction on Cell-ID Measured Results Sets in INFORMATION EXCHANGE INITIATION REQUEST | 8.2.0 | +| 12/2009 | - | - | - | Creation of Rel-9 version based on v 8.2.0 | 9.0.0 | +| 47 | RP-100229 | 0120 | | Correction to OTDOA in SAS-centric mode | 9.1.0 | +| 47 | RP-100230 | 0121 | 1 | Addition of DGNSS Validity Period in PCAP | 9.1.0 | +| 49 | RP-100907 | 0124 | 1 | DGANSS ASN.1 correction | 9.2.0 | +| 09/2010 | | | | Creation of Rel-10 version based on v 9.2.0 | | +| 49 | RP-100910 | 0123 | 1 | Small Technical Enhancements and Improvements for GNSS (PCAP) | 10.0.0 | +| 50 | RP-101276 | 0127 | 6 | IRAT measurement for enhanced positioning capability | 10.1.0 | +| 50 | RP-101276 | 0128 | 1 | Clarification of reporting of CellID measurements | 10.1.0 | +| SP-49 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 10.2.0 | +| 51 | RP-110229 | 0129 | 2 | PCAP ASN.1 Cleanup | 10.2.0 | +| 51 | RP-110226 | 0134 | 5 | Adding of IMSI and IMEI to PERFORM LOCATION REQUEST message | 10.2.0 | +| 52 | RP-110686 | 0135 | 2 | ASN.1 corrections and cleanup of 25.453 | 10.3.0 | +| 52 | RP-110685 | 0136 | | References cleanup (25.453) | 10.3.0 | +| 09/2012 | | | | Update to Rel-11 version (MCC) | 11.0.0 | +| 60 | RP-130638 | 0137 | | Clarification on Positioning Data Discriminator IE | 11.1.0 | +| 62 | RP-131901 | 0139 | 1 | Correct ASN.1 definitions of IMSI and IMEI | 11.2.0 | +| 62 | RP-131690 | 0146 | 2 | Correction to Galileo Assistance Data Elements | 11.2.0 | +| 62 | RP-131906 | 0141 | 2 | Introduction of BDS in UTRAN | 12.0.0 | +| 62 | RP-131691 | 0147 | 2 | Correction to Galileo Assistance Data Elements | 12.0.0 | +| 62 | RP-131900 | 0148 | | Correction of when to include the GPS Positioning IE in the POSITION ACTIVATION REQUEST message | 12.0.0 | +| 65 | RP-141608 | 0151 | 2 | Corrections to GNSS Acquisition Assistance Data | 12.1.0 | +| 66 | RP-142084 | 0152 | 1 | BDS Satellite Specific ICD update to version 2.0 | 12.2.0 | +| 66 | RP-142081 | 0153 | 1 | Correction to Galileo Assistance Data | 12.2.0 | +| 66 | RP-142094 | 0155 | | PCAP Rapporteur update | 12.2.0 | +| 70 | RP-152097 | 0157 | 7 | RAT-Independent positioning enhancements for PCAP | 13.0.0 | +| 71 | RP-160449 | 0159 | 2 | PCAP Rapporteur Update | 13.1.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-07 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25462/raw.md b/marked/Rel-16/25_series/25462/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b2c843c206467e518785f168d77441101a1db1f4 --- /dev/null +++ b/marked/Rel-16/25_series/25462/raw.md @@ -0,0 +1,84 @@ + + + + + + +# --- Contents + +Foreword ..... 4 + +1 Scope..... 5 + +2 References..... 5 + +3 to 4 Void..... 5 + +5 Iuant interface: Signalling transport..... 5 + +**Annex A to E: Void..... 6** + +Annex F (informative): Change History..... 7 + +# --- Foreword + +This Technical Specification has been produced by the 3rd 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 + +See TS 37.462 [5]. + +# --- 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]-[4] Void. + +[5] 3GPP TS 37.462: "Iuant interface: Signalling transport". + +# --- 3 to 4 Void + +# --- 5 Iuant interface: Signalling transport + +See TS 37.462 [5]. + +# --- Annex A to E: Void + +# Annex F (informative): Change History + +| Date / TSG | TSG Doc. | CR | Rev | Subject/Comment | New | +|------------|-----------|------|-----|------------------------------------------------------------|--------| +| 12/2008 | - | - | - | Creation of Rel-8 version based on v7.4.0 | 8.0.0 | +| 43 | RP-090085 | 0029 | 1 | RET and TMA support in LTE | 8.1.0 | +| 12/2009 | - | - | - | Creation of Rel-9 version based on v8.1.0 | 9.0.0 | +| 01/2011 | - | - | - | Creation of Rel-10 version based on v9.0.0 | 10.0.0 | +| 03/2011 | SP-100629 | | | Clarification on the use of References (TS 21.801 CR#0030) | 10.0.1 | +| 52 | RP-110685 | 0032 | | Removal of unused references | 10.1.0 | +| 09/2012 | | | | Update to Rel-11 version (MCC) | 11.0.0 | +| 09/2014 | | | | Update to Rel-12 version (MCC) | 12.0.0 | +| 12/2015 | | | | Update to Rel-13 version (MCC) | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|-----------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-07 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2019-04 | RAN#83 | RP-190557 | 0040 | - | F | Transfer of Iuant interface specification from 25-series to 37-series | 15.1.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25470/2ba086df3506f81bae3a9b53725dcfea_img.jpg b/marked/Rel-16/25_series/25470/2ba086df3506f81bae3a9b53725dcfea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ebc8da3219ad3015a94f951598dc41045a114969 --- /dev/null +++ b/marked/Rel-16/25_series/25470/2ba086df3506f81bae3a9b53725dcfea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa64658c558e6448f3ffd5aeb02d3b4920c1123a623238a80c1fb57fb6b2cba4 +size 12669 diff --git a/marked/Rel-16/25_series/25470/446100c084b94817a19c319fa776b412_img.jpg b/marked/Rel-16/25_series/25470/446100c084b94817a19c319fa776b412_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ac51bfc0c6dce57ada72d775d80d9865a8e12ec --- /dev/null +++ b/marked/Rel-16/25_series/25470/446100c084b94817a19c319fa776b412_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a0bf22978a8724340f9e4318694fb06acabf9b4afedc057874f775768c95de0 +size 20788 diff --git a/marked/Rel-16/25_series/25470/54fabc351eda5228d2fa28cd9ba07971_img.jpg b/marked/Rel-16/25_series/25470/54fabc351eda5228d2fa28cd9ba07971_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..741f527940274fed26ab1cac0fedfab7dbc26dcc --- /dev/null +++ b/marked/Rel-16/25_series/25470/54fabc351eda5228d2fa28cd9ba07971_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fac8197538b5070916b33c5e8b24a1d2a5d1528ece4425e568f95dbb1bfe5de6 +size 12287 diff --git a/marked/Rel-16/25_series/25470/a234352dfaccdc24745c88eef7724cc6_img.jpg b/marked/Rel-16/25_series/25470/a234352dfaccdc24745c88eef7724cc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2cb956cd68f34d651cdd0b2d5dd8d54826ddc957 --- /dev/null +++ b/marked/Rel-16/25_series/25470/a234352dfaccdc24745c88eef7724cc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36f0f4c55bbc154c1936a35ccdda035c64a88d1f570a6262a50d04f09fbfcb3b +size 12308 diff --git a/marked/Rel-16/25_series/25470/cd48273072c5c3a23e11fde892d1b6b6_img.jpg b/marked/Rel-16/25_series/25470/cd48273072c5c3a23e11fde892d1b6b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7073faf6ed1c033fd2a85ee1665c56dd9b47956d --- /dev/null +++ b/marked/Rel-16/25_series/25470/cd48273072c5c3a23e11fde892d1b6b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:739ebcff72769196c8f7bea7a96ebacaeed2e6b274f58a4268eefa1a5a1a3b02 +size 15555 diff --git a/marked/Rel-16/25_series/25470/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/Rel-16/25_series/25470/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a3063348eac212cf9440ad909665229d544544e --- /dev/null +++ b/marked/Rel-16/25_series/25470/d26959f4514c26ca19c3d6f00da85956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1fe24368f5442014fc2f65e5771adc1642b0bfc391fc3271bdec69ff3b1ee3c0 +size 15972 diff --git a/marked/Rel-16/25_series/25470/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/Rel-16/25_series/25470/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f003085e506cb87f5bcbd07cd4534f1ef877d68b --- /dev/null +++ b/marked/Rel-16/25_series/25470/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7a76928f28cf33c8ef5b0e6106bdf4c90c00528646adecf54e22caff272d185 +size 13154 diff --git a/marked/Rel-16/25_series/25470/ec98c4d2d93f28dfc8eb9d5e5730f62d_img.jpg b/marked/Rel-16/25_series/25470/ec98c4d2d93f28dfc8eb9d5e5730f62d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b554fc53ee9a6b7435ba2ca14eb1b7162484589 --- /dev/null +++ b/marked/Rel-16/25_series/25470/ec98c4d2d93f28dfc8eb9d5e5730f62d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62e6ac9d22179a1daafd773a9be01daa49b5a98804bfdd285c0f5564e4130a0d +size 14489 diff --git a/marked/Rel-16/25_series/25470/f14e75bd1c6e2f234db4775dbf0dbf1a_img.jpg b/marked/Rel-16/25_series/25470/f14e75bd1c6e2f234db4775dbf0dbf1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf1ff01e03e18317baf5c4401b8fa93fcbdb2e0d --- /dev/null +++ b/marked/Rel-16/25_series/25470/f14e75bd1c6e2f234db4775dbf0dbf1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:198d8c4339961b4a24c8e421aaabe6a6090f7e66b4c3bbc75ca4a73625dc9ca3 +size 14808 diff --git a/marked/Rel-16/25_series/25470/f4535959316aea381fb56b9225d8e4bd_img.jpg b/marked/Rel-16/25_series/25470/f4535959316aea381fb56b9225d8e4bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26920bb355a7cf7ff1a52d3b8679a2735075b557 --- /dev/null +++ b/marked/Rel-16/25_series/25470/f4535959316aea381fb56b9225d8e4bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:438c2ff5138712b17ac5c5db24deb3a723bdd409285068984d711d32606b81f2 +size 11240 diff --git a/marked/Rel-16/25_series/25470/raw.md b/marked/Rel-16/25_series/25470/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4eab7d53b5d893196377ac8349854ebe92ad250e --- /dev/null +++ b/marked/Rel-16/25_series/25470/raw.md @@ -0,0 +1,1706 @@ + + + + + + +# Contents + +- Foreword .....5 +- 1 Scope.....6 +- 2 References.....6 +- 3 Definitions and abbreviations .....6 + - 3.1 Definitions.....6 + - 3.2 Abbreviations .....6 +- 4 General.....7 + - 4.1 Procedure specification principles .....7 + - 4.2 Forwards and backwards compatibility.....7 + - 4.3 Specification notations .....7 +- 5 PUA services.....8 +- 6 Services expected from the transport layer.....8 +- 7 Functions of PUA.....8 +- 8 PUA procedures .....8 + - 8.1 Elementary Procedures.....8 + - 8.2 Connect.....8 + - 8.2.1 General .....8 + - 8.2.2 Successful Operation.....9 + - 8.3 Direct Transfer .....9 + - 8.3.1 General .....9 + - 8.3.2 Successful Operation (HNB-GW Originated).....9 + - 8.3.3 Successful Operation (HNB Originated).....9 + - 8.3.4 Abnormal Conditions .....10 + - 8.4 Disconnect.....10 + - 8.4.1 General .....10 + - 8.4.2 Successful Operation (HNB Originated).....10 + - 8.4.3 Successful Operation (HNB-GW Originated).....10 + - 8.5 Connectionless Transfer.....10 + - 8.5.1 General .....10 + - 8.5.2 Successful Operation (HNB-GW Originated).....11 + - 8.5.3 Successful Operation (HNB Originated).....11 + - 8.5.4 Abnormal Conditions .....11 + - 8.6 Error Indication .....11 + - 8.6.1 General .....11 + - 8.6.2 Successful Operation.....11 +- 9 Elements for PUA communication .....12 + - 9.1 Message functional definition and content.....12 + - 9.1.1 General .....12 + - 9.1.2 Message contents.....12 + - 9.1.2.1 Presence .....12 + - 9.1.2.2 Criticality .....12 + - 9.1.2.3 Range .....13 + - 9.1.2.4 Assigned Criticality .....13 + - 9.1.3 CONNECT .....13 + - 9.1.4 DIRECT TRANSFER .....13 + - 9.1.5 DISCONNECT.....13 + - 9.1.6 CONNECTIONLESS TRANSFER .....14 + - 9.1.7 ERROR INDICATION .....14 + - 9.2 Information Element Definitions .....14 + - 9.2.0 General .....14 + - 9.2.1 Message Type.....15 + - 9.2.2 PCAP Context ID .....15 + - 9.2.3 PCAP Message .....15 + +- 9.2.4 SAS Indicator .....15 +- 9.2.5 Transaction ID .....15 +- 9.2.6 Cause .....15 +- 9.2.7 Criticality Diagnostics .....17 +- 9.3 Message and Information Element Abstract Syntax (with ASN.1) .....19 + - 9.3.0 General .....19 + - 9.3.1 Usage of private message mechanism for non-standard use .....19 + - 9.3.2 Elementary Procedure Definitions.....19 + - 9.3.3 PDU definitions .....22 + - 9.3.4 Information Element definitions.....26 + - 9.3.5 Common definitions .....28 + - 9.3.6 Constant definitions.....29 + - 9.3.7 Container definitions .....30 +- 9.4 Message transfer syntax .....34 +- 10 Handling of unknown, unforeseen, and erroneous protocol data .....35 + - 10.1 General .....35 + - 10.2 Transfer Syntax Error.....35 + - 10.3 Abstract Syntax Error.....35 + - 10.3.1 General .....35 + - 10.3.2 Criticality Information .....36 + - 10.3.3 Presence Information.....36 + - 10.3.4 Not comprehended IE/IE group.....37 + - 10.3.4.1 Procedure Code .....37 + - 10.3.4.1A Type of Message .....37 + - 10.3.4.2 IEs other than the Procedure Code and Type of Message .....37 + - 10.3.5 Missing IE or IE group .....38 + - 10.3.6 IEs or IE groups received in wrong order or with too many occurrences or erroneously present .....39 + - 10.4 Logical Error .....40 + - 10.5 Exceptions .....40 +- Annex A (informative): Change history.....41 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document specifies the *PCAP User Adaption* (PUA) between the Home Node B (HNB) and the Home Node B Gateway (HNB-GW). It fulfils the HNB- HNB-GW communication requirements specified in TS 25.467 [5] and is defined over the Iuh – reference point. It provides transport for PCAP messages. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 25.453: "UTRAN Iupc interface Positioning Calculation Application Part (PCAP) signalling". +- [3] IETF RFC 4960 (2007-09): "Stream Control Transmission Protocol". +- [4] 3GPP TR 25.921 (Version 7.0.0): "Guidelines and principles for protocol description and error handling". +- [5] 3GPP TS 25.467: "UTRAN architecture for 3G Home Node B; Stage 2". +- [6] ITU-T Recommendation X.691 (2002-07): "Information technology - ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)". +- [7] ITU-T Recommendation X.680 (2002-07): "Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation". +- [8] ITU-T Recommendation X.681 (2002-07): "Information technology - Abstract Syntax Notation One (ASN.1): Information object specification". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|--------|--------------------------------------| +| CN | Core Network | +| EP | Elementary Procedure | +| HNB | Home Node B | +| HNB-GW | Home Node B Gateway | +| PDU | Protocol Data Unit | +| PUA | PCAP User Adaption | +| SCTP | Stream Control Transmission Protocol | + +# --- 4 General + +The protocol described in the present document is the protocol between HNB-GW and HNB. + +## 4.1 Procedure specification principles + +The principle for specifying the procedure logic is to specify the functional behaviour of the HNB & HNB-GW exactly and completely. + +The following specification principles have been applied for the procedure text in clause 8: + +- The procedure text discriminates between: + - 1) Functionality which "shall" be executed: + - The procedure text indicates that the receiving node "shall" perform a certain function Y under a certain condition. If the receiving node supports procedure X but cannot perform functionality Y requested in the REQUEST message of a Class 1 EP, the receiving node shall respond with the message used to report unsuccessful outcome for this procedure, containing an appropriate cause value. + - 2) Functionality which "shall, if supported" be executed: + - The procedure text indicates that the receiving node "shall, if supported," perform a certain function Y under a certain condition. If the receiving node supports procedure X, but does not support functionality Y, the receiving node shall proceed with the execution of the EP, possibly informing the requesting node about the not supported functionality. +- Any required inclusion of an optional IE in a response message is explicitly indicated in the procedure text. If the procedure text does not explicitly indicate that an optional IE shall be included in a response message, the optional IE shall not be included. + +## 4.2 Forwards and backwards compatibility + +The forwards and backwards compatibility of the protocol is assured by mechanism where all current and future messages, and IEs or groups of related IEs, include Id and criticality fields that are coded in a standard format that will not be changed in the future. These parts can always be decoded regardless of the standard version. + +## 4.3 Specification notations + +For the purposes of the present document, the following notations apply: + +- | | | +|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Procedure | When referring to an elementary procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. Direct Transfer procedure. | +| Message | When referring to a message in the specification the MESSAGE NAME is written with all letters in upper case characters followed by the word "message", e.g. CONNECT message. | +| IE | When referring to an information element (IE) in the specification the Information Element Name is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation "IE", e.g. Context ID IE . | +| Value of an IE | When referring to the value of an information element (IE) in the specification the "Value" is written as it is specified in subclause 9.2 enclosed by quotation marks, e.g. "Abstract Syntax Error (Reject)" or "Background ". | + +# --- 5 PUA services + +PUA provides the signalling service between the HNB and the HNB-GW that is required to fulfil the PUA functions described in Clause 7. + +# 6 Services expected from the transport layer + +Following service is expected from the transport layer: + +- reliable and in sequence delivery of Signalling data using SCTP (IETF RFC 4960 [3]) + +# 7 Functions of PUA + +The PUA has the following functions: + +- Transparent transfer of PCAP messages +- Error Handling. This function allows the reporting of general error situations, for which function specific error messages have not been defined. + +These functions are implemented by one or several PUA elementary procedures described in the following clauses. + +# 8 PUA procedures + +## 8.1 Elementary Procedures + +Table 1 summarizes the EPs. + +**Table 1; Elementary procedures** + +| Elementary Procedure | Message | +|-------------------------|-------------------------| +| Connect | CONNECT | +| Direct Transfer | DIRECT TRANSFER | +| Disconnect | DISCONNECT | +| Connectionless Transfer | CONNECTIONLESS TRANSFER | +| Error Indication | ERROR INDICATION | + +## 8.2 Connect + +### 8.2.1 General + +The HNB can initiate this procedure to establish a Signalling Connection and carry a PCAP message. + +### 8.2.2 Successful Operation + +![Sequence diagram showing the successful operation of the Connect procedure. An HNB (Home NodeB) sends a CONNECT message to an HNB-GW (Home NodeB Gateway).](f4535959316aea381fb56b9225d8e4bd_img.jpg) + +``` + +sequenceDiagram + participant HNB + participant HNB-GW + Note left of HNB: HNB initiates Connect procedure + HNB->>HNB-GW: CONNECT + Note right of HNB-GW: HNB-GW receives CONNECT + +``` + +Sequence diagram showing the successful operation of the Connect procedure. An HNB (Home NodeB) sends a CONNECT message to an HNB-GW (Home NodeB Gateway). + +**Figure 8.2.2-1: Connect procedure – successful operation** + +This procedure is used to carry the first PCAP message from the HNB to the HNB-GW. + +If the *SAS Indicator* IE is included the HNB-GW may use to select a SAS for connection. + +Additional information is provided to enable the HNB-GW to trigger the establishment of a new Signalling Connection between HNB and HNB-GW, which is directly mapped to the Iupc Signalling Connection the PCAP message refers to. + +NOTE: The Context ID is used as the Iupc Signalling Connection identifier in the corresponding PCAP messages. + +## 8.3 Direct Transfer + +### 8.3.1 General + +This procedure is initiated by either the HNB or HNB-GW to transport a PCAP message between the two nodes. + +### 8.3.2 Successful Operation (HNB-GW Originated) + +![Sequence diagram showing Direct Transfer from HNB-GW to HNB.](a234352dfaccdc24745c88eef7724cc6_img.jpg) + +A sequence diagram illustrating the Direct Transfer procedure from HNB-GW to HNB. Two vertical lifelines are shown: HNB on the left and HNB-GW on the right. A horizontal arrow labeled 'DIRECT TRANSFER' points from the HNB-GW lifeline to the HNB lifeline. Both lifelines end in a thick horizontal bar at the bottom. + +Sequence diagram showing Direct Transfer from HNB-GW to HNB. + +Figure 8.3.2-1: Direct Transfer procedure – successful operation + +This procedure is used to carry any downlink connection-oriented PCAP message defined in TS 25.453 [2] from the HNB-GW to the HNB. + +### 8.3.3 Successful Operation (HNB Originated) + +![Sequence diagram showing Direct Transfer from HNB to HNB-GW.](2ba086df3506f81bae3a9b53725dcfea_img.jpg) + +A sequence diagram illustrating the Direct Transfer procedure from HNB to HNB-GW. Two vertical lifelines are shown: HNB on the left and HNB-GW on the right. A horizontal arrow labeled 'DIRECT TRANSFER' points from the HNB lifeline to the HNB-GW lifeline. Both lifelines end in a thick horizontal bar at the bottom. + +Sequence diagram showing Direct Transfer from HNB to HNB-GW. + +Figure 8.3.3-1: Direct Transfer procedure – successful operation + +This procedure is used to carry any uplink connection-oriented PCAP message defined in TS 25.453 [2], except those carried in CONNECT or DISCONNECT messages, from the HNB to the HNB-GW. + +### 8.3.4 Abnormal Conditions + +- + +## 8.4 Disconnect + +### 8.4.1 General + +This procedure is normally initiated by the HNB to terminate a Signalling Connection between the HNB and HNB-GW, but may be initiated by the HNB-GW to close a refused connection or if an existing connection is released (e.g. for error reasons) by the SAS or HNB-GW. + +### 8.4.2 Successful Operation (HNB Originated) + +![Sequence diagram showing DISCONNECT message from HNB to HNB-GW.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg) + +A sequence diagram illustrating the disconnect procedure initiated by the HNB. It features two vertical lifelines: HNB on the left and HNB-GW on the right. A horizontal arrow labeled 'DISCONNECT' points from the HNB lifeline to the HNB-GW lifeline. Both lifelines terminate at a solid black horizontal bar at the bottom. + +Sequence diagram showing DISCONNECT message from HNB to HNB-GW. + +**Figure 8.4.2-1: Disconnect procedure** + +This procedure is used to release a signalling connection between the HNB and HNB-GW and may carry the last PCAP (TS 25.453 [2]) uplink connection-oriented message of a given Signalling Connection to the HNB-GW over the Iuh interface. This procedure may also be used to indicate error conditions at the HNB. This procedure will indicate the cause of the termination in the *Cause* IE. + +### 8.4.3 Successful Operation (HNB-GW Originated) + +![Sequence diagram showing DISCONNECT message from HNB-GW to HNB.](54fabc351eda5228d2fa28cd9ba07971_img.jpg) + +A sequence diagram illustrating the disconnect procedure initiated by the HNB-GW. It features two vertical lifelines: HNB on the left and HNB-GW on the right. A horizontal arrow labeled 'DISCONNECT' points from the HNB-GW lifeline to the HNB lifeline. Both lifelines terminate at a solid black horizontal bar at the bottom. + +Sequence diagram showing DISCONNECT message from HNB-GW to HNB. + +**Figure 8.4.3-1: Disconnect procedure** + +This procedure is used to close a given Signalling Connection between the HNB and the HNB-GW over the Iuh interface. This procedure will indicate the cause of the termination in the *Cause* IE. + +## 8.5 Connectionless Transfer + +### 8.5.1 General + +This procedure is initiated by either the HNB or the HNB-GW to transfer connectionless PCAP messages between the HNB and HNB-GW. + +### 8.5.2 Successful Operation (HNB-GW Originated) + +![Sequence diagram showing CONNECTIONLESS TRANSFER message from HNB-GW to HNB.](cd48273072c5c3a23e11fde892d1b6b6_img.jpg) + +A sequence diagram illustrating the connectionless transfer procedure initiated by the HNB-GW. It features two vertical lifelines: HNB on the left and HNB-GW on the right. A horizontal arrow labeled 'CONNECTIONLESS TRANSFER' points from the HNB-GW lifeline to the HNB lifeline. Both lifelines terminate at a solid black horizontal bar at the bottom. + +Sequence diagram showing CONNECTIONLESS TRANSFER message from HNB-GW to HNB. + +**Figure 8.5.2-1: Connectionless Transfer procedure to HNB** + +This procedure is used to carry any downlink connectionless PCAP message defined in TS 25.453 [2] from the HNB-GW to the HNB. + +### 8.5.3 Successful Operation (HNB Originated) + +![Sequence diagram showing Connectionless Transfer from HNB to HNB-GW.](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +A sequence diagram illustrating the 'CONNECTIONLESS TRANSFER' procedure. It features two vertical lifelines: 'HNB' on the left and 'HNB-GW' on the right. Each lifeline has a rectangular box at the top and a thick horizontal bar at the bottom. A single horizontal arrow points from the HNB lifeline to the HNB-GW lifeline, with the text 'CONNECTIONLESS TRANSFER' centered above it. + +Sequence diagram showing Connectionless Transfer from HNB to HNB-GW. + +**Figure 8.5.3-1: Connectionless Transfer procedure to HNB-GW** + +This procedure is used to carry any uplink connectionless PCAP message defined in TS 25.453 [2] from the HNB to the HNB-GW. If the *SAS Indicator* IE is included the HNB-GW may use to select a SAS as the destination of the message. + +### 8.5.4 Abnormal Conditions + +- + +## 8.6 Error Indication + +### 8.6.1 General + +The Error Indication procedure is initiated by either HNB or HNB-GW to report detected errors in one incoming message. + +### 8.6.2 Successful Operation + +![Sequence diagram showing Error Indication from HNB to HNB-GW.](f14e75bd1c6e2f234db4775dbf0dbf1a_img.jpg) + +A sequence diagram illustrating the 'ERROR INDICATION' procedure originating from the HNB. It features two vertical lifelines: 'HNB' on the left and 'HNB-GW' on the right. Each lifeline has a rectangular box at the top and a thick horizontal bar at the bottom. A single horizontal arrow points from the HNB lifeline to the HNB-GW lifeline, with the text 'ERROR INDICATION' centered above it. + +Sequence diagram showing Error Indication from HNB to HNB-GW. + +**Figure 8.6.2-1 Error Indication HNB Originated, Successful Operation** + +![Sequence diagram showing Error Indication from HNB-GW to HNB.](ec98c4d2d93f28dfc8eb9d5e5730f62d_img.jpg) + +A sequence diagram illustrating the 'ERROR INDICATION' procedure originating from the HNB-GW. It features two vertical lifelines: 'HNB' on the left and 'HNB-GW' on the right. Each lifeline has a rectangular box at the top and a thick horizontal bar at the bottom. A single horizontal arrow points from the HNB-GW lifeline to the HNB lifeline, with the text 'ERROR INDICATION' centered above it. + +Sequence diagram showing Error Indication from HNB-GW to HNB. + +**Figure 8.6.2-2 Error Indication HNB-GW Originated, Successful Operation** + +# 9 Elements for PUA communication + +## 9.1 Message functional definition and content + +### 9.1.1 General + +Section 9.1 presents the contents of PUA messages in tabular format. The corresponding ASN.1 definition is presented in section 9.3. In case there is contradiction between the tabular format in section 9.1 and the ASN.1 definition, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional IEs, where the tabular format shall take precedence. + +NOTE: The messages have been defined in accordance to the guidelines specified in TR 25.921 [4]. + +For each message there is, a table listing the signalling elements in their order of appearance in the transmitted message. + +### 9.1.2 Message contents + +#### 9.1.2.1 Presence + +All information elements in the message descriptions below are marked mandatory, optional or conditional according to table 3. + +**Table 2: Meaning of abbreviations used in PUA messages** + +| Abbreviation | Meaning | +|--------------|------------------------------------------------------------------------------------------------------------------------------------| +| M | IE's marked as Mandatory (M) will always be included in the message. | +| O | IE's marked as Optional (O) may or may not be included in the message. | +| C | IE's marked as Conditional (C) will be included in a message only if the condition is satisfied. Otherwise the IE is not included. | + +#### 9.1.2.2 Criticality + +Each Information Element or Group of Information Elements may have a criticality information applied to it. Following cases are possible. + +**Table 3: Meaning of content within "Criticality" column** + +| Abbreviation | Meaning | +|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| – | No criticality information is applied explicitly. | +| YES | Criticality information is applied. This is usable only for non-repeatable IEs | +| GLOBAL | The IE and all its repetitions together have one common criticality information. This is usable only for repeatable IEs. | +| EACH | Each repetition of the IE has its own criticality information. It is not allowed to assign different criticality values to the repetitions. This is usable only for repeatable IEs. | + +#### 9.1.2.3 Range + +The Range column indicates the allowed number of copies of repetitive IEs/IE groups. + +#### 9.1.2.4 Assigned Criticality + +This column provides the actual criticality information as defined in subclause 10.3.2, if applicable. + +### 9.1.3 CONNECT + +This message is sent by the HNB to the HNB-GW to establish a signalling connection and carry a PCAP message. + +Direction: HNB → HNB-GW + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | YES | ignore | +| PCAP Context ID | M | | 9.2.2 | | YES | reject | +| PCAP Message | M | | 9.2.3 | | YES | reject | +| SAS Indicator | O | | 9.2.4 | SAS indicator is used to select a target SAS where multiple SAS are connected and is set by configuration | YES | ignore | + +### 9.1.4 DIRECT TRANSFER + +This message is sent by either the HNB to the HNB-GW or the HNB-GW to the HNB to transport a connection-oriented PCAP message between the two nodes. + +Direction: HNB → HNB-GW and HNB-GW → HNB + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | YES | ignore | +| PCAP Context ID | M | | 9.2.2 | | YES | reject | +| PCAP Message | M | | 9.2.3 | | YES | reject | + +### 9.1.5 DISCONNECT + +This message is sent either by the HNB to the HNB-GW or the HNB-GW to the HNB to close the signalling connection between the two nodes. + +Direction: HNB → HNB-GW and HNB-GW → HNB + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-----------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | YES | ignore | +| PCAP Context ID | M | | 9.2.2 | | YES | reject | +| Cause | M | | 9.2.6 | | YES | reject | +| PCAP Message | O | | 9.2.3 | | YES | reject | + +### 9.1.6 CONNECTIONLESS TRANSFER + +This message is sent by either the HNB to the HNB-GW or the HNB-GW to the HNB to transport a connectionless PCAP message between the two nodes. + +Direction: HNB → HNB-GW and HNB-GW → HNB + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|---------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | YES | ignore | +| PCAP Message | M | | 9.2.3 | | YES | reject | +| SAS Indicator | O | | 9.2.4 | SAS indicator is used to select a target SAS where multiple SAS are connected and is set by configuration | YES | ignore | + +### 9.1.7 ERROR INDICATION + +This message is sent by either the HNB to HNB-GW or the HNB-GW to the HNB and is used to indicate that some errors have been detected. + +Direction: HNB → HNB-GW, HNB-GW → HNB + +| PARAMETER | PRESENCE | RANGE | IE Type and Reference | Semantics Description | Criticality | Assigned Criticality | +|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| +| Message Type | M | | 9.2.1 | | YES | ignore | +| Cause | M | | 9.2.6 | | YES | ignore | +| Criticality Diagnostics | O | | 9.2.7 | | YES | ignore | +| PCAP Context ID | O | | 9.2.2 | | YES | ignore | +| Transaction ID | O | | 9.2.5 | | YES | ignore | + +## 9.2 Information Element Definitions + +### 9.2.0 General + +Section 9.2 presents the PUA IE definitions in tabular format. The corresponding ASN.1 definition is presented in section 9.3. In case there is contradiction between the tabular format in section 9.2 and the ASN.1 definition, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional elements, where the tabular format shall take precedence. + +When specifying information elements which are to be represented by bitstrings, if not otherwise specifically stated in the semantics description of the concerned IE or elsewhere, the following principle applies with regards to the ordering of bits: + +- The first bit (leftmost bit) contains the most significant bit (MSB); +- The last bit (rightmost bit) contains the least significant bit (LSB); +- When importing bitstrings from other specifications, the first bit of the bitstring contains the first bit of the concerned information. + +### 9.2.1 Message Type + +*Message Type* IE uniquely identifies the message being sent. It is mandatory for all messages. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and Reference | Semantics Description | +|---------------------|----------|-------|------------------------------------------------------------------------------------------------|-----------------------| +| Message Type | | | | | +| >Procedure Code | M | | INTEGER(0..255) | | +| >Type of Message | M | | ENUMERATED
(Initiating Message,
Successful Outcome,
Unsuccessful Outcome,
Outcome) | | + +### 9.2.2 PCAP Context ID + +*PCAP Context ID* IE uniquely identifies a PUA context in the HNB and HNB-GW. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|---------------|----------|-------|----------------------|-----------------------| +| Context ID | | | BIT STRING(SIZE(24)) | | + +### 9.2.3 PCAP Message + +*PCAP Message* IE contains the transferred PCAP message. + +| IE/GROUP NAME | PRESENCE | RANGE | IE Type and | Semantics Description | +|---------------|----------|-------|--------------|-----------------------| +| PCAP Message | | | OCTET STRING | | + +### 9.2.4 SAS Indicator + +This element indicates the SAS to be used. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|---------------|----------|-------|-----------------------|-----------------------| +| SAS Indicator | M | | INTEGER(0..255) | | + +### 9.2.5 Transaction ID + +This element indicates the Transaction ID as described in PCAP. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|----------------|----------|-------|-----------------------|-------------------------------| +| Transaction ID | M | | BIT STRING (SIZE(16)) | As defined in PCAP 25.453 [2] | + +### 9.2.6 Cause + +*Cause* IE indicates the reason for a particular error event or disconnect for the PUA protocol. + +| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | +|------------------------------|----------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| CHOICE Cause Group | | | | | +| > Radio Network Layer | | | | | +| >>Radio Network Layer Cause | M | | ENUMERATED
(
Normal,
Connect failed,
HNB-GW release,
SAS release,
Unspecified,
...
) | | +| > Transport Layer | | | | | +| >>Transport Layer Cause | M | | ENUMERATED
(Transport Resource Unavailable,
Unspecified,
...) | | +| > Protocol | | | | | +| >>Protocol Cause | M | | ENUMERATED
(Transfer Syntax Error,
Abstract Syntax Error (Reject),
Abstract Syntax Error (Ignore and Notify),
Message not Compatible with Receiver State,
Semantic Error,
Unspecified,
Abstract Syntax Error (Falsely Constructed Message),
...) | | +| > Misc | | | | | +| >>Misc Cause | M | | ENUMERATED
(Processing Overload,
Hardware Failure,
O&M Intervention,
SAS unavailable,
SAS not configured,
Unspecified,
...) | | + +The meaning of the different cause values is described in the following table. Cause values for information 'not valid' indicates that the information is not valid in the context that it was received. + +| Radio Network Layer cause | Meaning | +|---------------------------|------------------------------------------------------------------------------------------------------| +| Normal | No error has occurred | +| Connect failed | Connect attempt failed | +| HNB-GW release | Connection released by HNB-GW | +| SAS release | Connection released by SAS | +| Unspecified | Sent when none of the above cause values applies but still the cause is Radio Network layer related. | + +| Transport Network Layer cause | Meaning | +|--------------------------------|----------------------------------------------------------------------------------------------------------| +| Transport resource unavailable | The required transport resources are not available. | +| Unspecified | Sent when none of the above cause values applies but still the cause is Transport Network layer related. | + +| Protocol cause | Meaning | +|-----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------| +| Abstract Syntax Error (Reject) | The received message included an abstract syntax error and the concerned criticality indicated "reject". | +| Abstract Syntax Error (Ignore and Notify) | The received message included an abstract syntax error and the concerned criticality indicated "ignore and notify". | +| Abstract syntax error (falsely constructed message) | The received message contained IEs in wrong order or with too many occurrences. | +| Message not Compatible with Receiver State | The received message was not compatible with the receiver state. | +| Semantic Error | The received message included a semantic error. | +| Transfer Syntax Error | The received message included a transfer syntax error. | +| Unspecified | Sent when none of the above cause values applies but still the cause is protocol related. | + +| Miscellaneous cause | Meaning | +|---------------------|--------------------------------------------------------| +| Processing Overload | Control processing overload. | +| Hardware Failure | HNB hardware failure. | +| O&M Intervention | Operation and Maintenance intervention related to HNB. | +| SAS unavailable | Connection to the SAS is not possible. | +| SAS not configured | No SAS is configured, or selected SAS is unrecognized. | +| Unspecified | Sent when none of the above cause values applies. | + +### 9.2.7 Criticality Diagnostics + +The *Criticality Diagnostics* IE is sent by the HNB or the HNB-GW when parts of a received message have not been comprehended or were missing, or if the message contained logical errors. When applicable, it contains information about which IEs were not comprehended or were missing. + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|----------------------------------------------------|----------|----------------------|---------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Criticality Diagnostics | | | | | +| >Procedure Code | O | | INTEGER (0..255) | Procedure Code is to be used if Criticality Diagnostics is part of Error Indication procedure, and not within the response message of the same procedure that caused the error | +| >Triggering Message | O | | ENUMERATED (initiating message, successful outcome, unsuccessful outcome) | The Triggering Message is used only if the Criticality Diagnostics is part of Error Indication procedure. | +| >Procedure Criticality | O | | ENUMERATED(reject, ignore, notify) | This Procedure Criticality is used for reporting the Criticality of the Triggering message (Procedure). | +| Information Element Criticality Diagnostics | | 0 to | | | +| >IE Criticality | M | | ENUMERATED(reject, ignore, notify) | The IE Criticality is used for reporting the criticality of the triggering IE. The value 'ignore' shall not be used. | +| >IE ID | M | | INTEGER (0..65535) | The IE Id of the not understood or missing IE | + +| IE/Group Name | Presence | Range | IE type and reference | Semantics description | +|--------------------------------|-----------------|--------------|------------------------------------------|------------------------------| +| Criticality Diagnostics | | | | | +| >Type of Error | M | | ENUMERATED(not understood, missing, ...) | | + +| Range bound | Explanation | +|--------------------|------------------------------------------------------------------------------------------------------------| +| maxNrOfErrors | Maximum no. of IE errors allowed to be reported with a single message. The value for maxNrOfErrors is 256. | + +## 9.3 Message and Information Element Abstract Syntax (with ASN.1) + +### 9.3.0 General + +PUA ASN.1 definition conforms with ITU-T Rec. X.680 [7] and ITU-T Rec. X.681 [8]. + +The ASN.1 definition specifies the structure and content of PUA messages. PUA messages can contain any IEs specified in the object set definitions for that message without the order or number of occurrence being restricted by ASN.1. However, for this version of the standard, a sending entity shall construct a PUA message according to the PDU definitions module and with the following additional rules (Note that in the following IE means an IE in the object set with an explicit id. If one IE needed to appear more than once in one object set, then the different occurrences have different IE ids): + +- IEs shall be ordered (in an IE container) in the order they appear in object set definitions. +- Object set definitions specify how many times IEs may appear. An IE shall appear exactly once if the presence field in an object has value "mandatory". An IE may appear at most once if the presence field in an object has value "optional" or "conditional". If in a tabular format there is multiplicity specified for an IE (i.e. an IE list) then in the corresponding ASN.1 definition the list definition is separated into two parts. The first part defines an IE container list where the list elements reside. The second part defines list elements. The IE container list appears as an IE of its own. For this version of the standard an IE container list may contain only one kind of list elements. + +If a PUA message that is not constructed as defined above is received, this shall be considered as Abstract Syntax Error, and the message shall be handled as defined for Abstract Syntax error in subclause 10.3.6. + +### 9.3.1 Usage of private message mechanism for non-standard use + +The private message mechanism for non-standard use may be used: + +- for special operator- (and/or vendor) specific features considered not to be part of the basic functionality, i.e. the functionality required for a complete and high-quality specification in order to guarantee multivendor interoperability; +- by vendors for research purposes, e.g. to implement and evaluate new algorithms/features before such features are proposed for standardisation. + +The private message mechanism shall not be used for basic functionality. Such functionality shall be standardised. + +### 9.3.2 Elementary Procedure Definitions + +``` + +-- ***** +-- +-- Elementary Procedure definitions +-- +-- ***** + +PUA-PDU-Descriptions { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + umts-Access (20) modules (3) pua(7) version1 (1) pUA-PDU-Descriptions (0)} + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +``` + +``` + +-- ***** +-- +-- IE parameter types from other modules. +-- +-- ***** + +IMPORTS + Criticality, + ProcedureCode +FROM PUA-CommonDataTypes + Connect, + DirectTransfer, + Disconnect, + ConnectionlessTransfer, + ErrorIndication, + PrivateMessage + +FROM PUA-PDU-Contents + id-Connect, + id-DirectTransfer, + id-Disconnect, + id-ConnectionlessTransfer, + id-ErrorIndication, + id-privateMessage +FROM PUA-Constants; + +-- ***** +-- +-- Interface Elementary Procedure Class +-- +-- ***** + +PUA-ELEMENTARY-PROCEDURE ::= CLASS { + &InitiatingMessage , + &SuccessfulOutcome OPTIONAL, + &UnsuccessfulOutcome OPTIONAL, + &procedureCode ProcedureCode UNIQUE, + &criticality Criticality DEFAULT ignore +} + +WITH SYNTAX { + INITIATING MESSAGE &InitiatingMessage + [SUCCESSFUL OUTCOME &SuccessfulOutcome] + [UNSUCCESSFUL OUTCOME &UnsuccessfulOutcome] + PROCEDURE CODE &procedureCode + [CRITICALITY &criticality] +} + +-- ***** +-- +-- Interface PDU definitions +-- +-- ***** + +``` + +``` + +PUA-PDU ::= CHOICE { + initiatingMessage InitiatingMessage, + successfulOutcome SuccessfulOutcome, + unsuccessfulOutcome UnsuccessfulOutcome, + ... +} + +InitiatingMessage ::= SEQUENCE { + procedureCode PUA-ELEMENTARY-PROCEDURE.&procedureCode ({PUA-ELEMENTARY-PROCEDURES}), + criticality PUA-ELEMENTARY-PROCEDURE.&criticality ({PUA-ELEMENTARY-PROCEDURES}{@procedureCode}), + value PUA-ELEMENTARY-PROCEDURE.&InitiatingMessage ({PUA-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +SuccessfulOutcome ::= SEQUENCE { + procedureCode PUA-ELEMENTARY-PROCEDURE.&procedureCode ({PUA-ELEMENTARY-PROCEDURES}), + criticality PUA-ELEMENTARY-PROCEDURE.&criticality ({PUA-ELEMENTARY-PROCEDURES}{@procedureCode}), + value PUA-ELEMENTARY-PROCEDURE.&SuccessfulOutcome ({PUA-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +UnsuccessfulOutcome ::= SEQUENCE { + procedureCode PUA-ELEMENTARY-PROCEDURE.&procedureCode ({PUA-ELEMENTARY-PROCEDURES}), + criticality PUA-ELEMENTARY-PROCEDURE.&criticality ({PUA-ELEMENTARY-PROCEDURES}{@procedureCode}), + value PUA-ELEMENTARY-PROCEDURE.&UnsuccessfulOutcome ({PUA-ELEMENTARY-PROCEDURES}{@procedureCode}) +} + +-- ***** +-- +-- Interface Elementary Procedure List +-- +-- ***** + +PUA-ELEMENTARY-PROCEDURES PUA-ELEMENTARY-PROCEDURE ::= { + PUA-ELEMENTARY-PROCEDURES-CLASS-1 | + PUA-ELEMENTARY-PROCEDURES-CLASS-2 , + ... +} + +PUA-ELEMENTARY-PROCEDURES-CLASS-1 PUA-ELEMENTARY-PROCEDURE ::= { + ... +} + +PUA-ELEMENTARY-PROCEDURES-CLASS-2 PUA-ELEMENTARY-PROCEDURE ::= { + connectionRequest | + directTransfer | + disconnectRequest | + connectionlessTransfer | + errorIndication | + privateMessage, + ... +} + +-- ***** +-- +-- Interface Elementary Procedures + +``` + +``` + +-- +-- ***** + +connectionRequest PUA-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Connect + PROCEDURE CODE id-Connect + CRITICALITY ignore +} + +directTransfer PUA-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE DirectTransfer + PROCEDURE CODE id-DirectTransfer + CRITICALITY ignore +} + +disconnectRequest PUA-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Disconnect + PROCEDURE CODE id-Disconnect + CRITICALITY ignore +} + +connectionlessTransfer PUA-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE ConnectionlessTransfer + PROCEDURE CODE id-ConnectionlessTransfer + CRITICALITY ignore +} + +errorIndication PUA-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE ErrorIndication + PROCEDURE CODE id-ErrorIndication + CRITICALITY ignore +} + +privateMessage PUA-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PrivateMessage + PROCEDURE CODE id-privateMessage + CRITICALITY ignore +} + +END + +``` + +### 9.3.3 PDU definitions + +``` + +-- ***** +-- +-- PDU definitions for PUA. +-- +-- ***** + +PUA-PDU-Contents { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + umts-Access (20) modules (3) pua(7) version1 (1) pUA-PDU-Contents (1) } + +``` + +``` + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ***** +-- +-- IE parameter types from other modules. +-- +-- ***** + +IMPORTS + Cause, + CriticalityDiagnostics, + PCAP-Context-ID, + PCAP-Message, + SAS-Indicator, + TransactionID + +FROM PUA-IEs + + ProtocolExtensionContainer{}, + ProtocolIE-ContainerList{}, + ProtocolIE-Container{}, + ProtocolIE-Single-Container{}, + PrivateIE-Container{}, + PUA-PRIVATE-IES, + PUA-PROTOCOL-EXTENSION, + PUA-PROTOCOL-IES + +FROM PUA-Containers + + id-Cause, + id-CriticalityDiagnostics, + id-PCAP-Context-ID, + id-PCAP-Message, + id-SAS-Indicator, + id-TransactionID + +FROM PUA-Constants; + +-- ***** +-- +-- Connect +-- +-- ***** + +Connect ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {ConnectIEs} }, + protocolExtensions ProtocolExtensionContainer { {ConnectExtensions} } OPTIONAL, + ... +} + +ConnectIEs PUA-PROTOCOL-IES ::= { + { ID id-PCAP-Context-ID CRITICALITY reject TYPE PCAP-Context-ID PRESENCE mandatory } | + { ID id-PCAP-Message CRITICALITY reject TYPE PCAP-Message PRESENCE mandatory } | +} + +``` + +``` + +-- A.5 +{ ID id-SAS-Indicator CRITICALITY ignore TYPE SAS-Indicator PRESENCE optional }, +... +} + +ConnectExtensions PUA-PROTOCOL-EXTENSION ::= { +... +} + +-- ***** +-- +-- Direct Transfer +-- +-- ***** + +DirectTransfer ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {DirectTransferIEs} }, + protocolExtensions ProtocolExtensionContainer { {DirectTransferExtensions} } OPTIONAL, + ... +} + +DirectTransferIEs PUA-PROTOCOL-IES ::= { + { ID id-PCAP-Context-ID CRITICALITY reject TYPE PCAP-Context-ID PRESENCE mandatory } | + { ID id-PCAP-Message CRITICALITY reject TYPE PCAP-Message PRESENCE mandatory }, + ... +} + +DirectTransferExtensions PUA-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- Disconnect +-- +-- ***** + +Disconnect ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {DisconnectIEs} }, + protocolExtensions ProtocolExtensionContainer { {DisconnectExtensions} } OPTIONAL, + ... +} + +DisconnectIEs PUA-PROTOCOL-IES ::= { + { ID id-PCAP-Context-ID CRITICALITY reject TYPE PCAP-Context-ID PRESENCE mandatory } | + { ID id-Cause CRITICALITY reject TYPE Cause PRESENCE mandatory } | + { ID id-PCAP-Message CRITICALITY reject TYPE PCAP-Message PRESENCE optional }, + ... +} + +DisconnectExtensions PUA-PROTOCOL-EXTENSION ::= { + ... +} + +``` + +``` + +-- -- -- +-- ***** +-- +-- Connectionless Transfer +-- +-- ***** + +ConnectionlessTransfer ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {ConnectionlessTransferIEs} }, + protocolExtensions ProtocolExtensionContainer { {ConnectionlessTransferExtensions} } OPTIONAL, + ... +} + +ConnectionlessTransferIEs PUA-PROTOCOL-IES ::= { + { ID id-PCAP-Message CRITICALITY reject TYPE PCAP-Message PRESENCE mandatory } | + { ID id-SAS-Indicator CRITICALITY ignore TYPE SAS-Indicator PRESENCE optional }, + ... +} + +ConnectionlessTransferExtensions PUA-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- ERROR INDICATION +-- +-- ***** + +ErrorIndication ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {ErrorIndicationIEs} }, + protocolExtensions ProtocolExtensionContainer { {ErrorIndicationExtensions} } OPTIONAL, + ... +} + +ErrorIndicationIEs PUA-PROTOCOL-IES ::= { + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } | + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional } | + { ID id-PCAP-Context-ID CRITICALITY ignore TYPE PCAP-Context-ID PRESENCE optional } | + { ID id-TransactionID CRITICALITY ignore TYPE TransactionID PRESENCE optional }, + ... +} + +ErrorIndicationExtensions PUA-PROTOCOL-EXTENSION ::= { + ... +} + +-- ***** +-- +-- PRIVATE MESSAGE +-- +-- ***** + +PrivateMessage ::= SEQUENCE { + privateIEs PrivateIE-Container { {PrivateMessage-IEs} }, + ... +} + +``` + +``` + +} + +PrivateMessage-IEs PUA-PRIVATE-IES ::= { + ... +} + +END + +``` + +### 9.3.4 Information Element definitions + +``` + +-- ************************************************************** +-- +-- Information Element Definitions +-- +-- ************************************************************** + +``` + +``` + +PUA-IEs { +itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) +umts-Access (20) modules (3) pua (7) version1 (1) pUA-IEs (2) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +``` + +``` + +IMPORTS + maxNrOfErrors +FROM PUA-Constants + + Criticality, + ProcedureCode, + ProtocolIE-ID, + TriggeringMessage +FROM PUA-CommonDataTypes + + ProtocolExtensionContainer{}, + PUA-PROTOCOL-EXTENSION +FROM PUA-Containers; + +``` + +PCAP-Context-ID ::= BIT STRING (SIZE(24)) + +PCAP-Message ::= OCTET STRING + +SAS-Indicator ::= INTEGER(0..255) + +TransactionID ::= BIT STRING (SIZE(16)) + +``` + +-- -- -- -- -- +-- ***** +-- +-- Cause IE +-- +-- ***** + +Cause ::= CHOICE { + radioNetwork CauseRadioNetwork, + transport CauseTransport, + protocol CauseProtocol, + misc CauseMisc, + ... +} +CauseRadioNetwork ::= ENUMERATED { + normal, + connect-failed, + hnb-gw-release, + sas-release, + unspecified, + ... +} +CauseTransport ::= ENUMERATED { + transport-resource-unavailable, + unspecified, + ... +} + +CauseProtocol ::= ENUMERATED { + transfer-syntax-error, + abstract-syntax-error-reject, + abstract-syntax-error-ignore-and-notify, + message-not-compatible-with-receiver-state, + semantic-error, + unspecified, + abstract-syntax-error-falsely-constructed-message, + ... +} + +CauseMisc ::= ENUMERATED { + processing-overload, + hardware-failure, + o-and-m-intervention, + sas-unavailable, + sas-not-configured, + unspecified, + ... +} + +-- ***** +-- +-- CriticalityDiagnostics +-- +-- ***** + +CriticalityDiagnostics ::= SEQUENCE { + procedureCode ProcedureCode + OPTIONAL, + +``` + +``` + + triggeringMessage TriggeringMessage OPTIONAL, + procedureCriticality Criticality OPTIONAL, + iEsCriticalityDiagnostics CriticalityDiagnostics-IE-List OPTIONAL, + iE-Extensions ProtocolExtensionContainer { {CriticalityDiagnostics-ExtIEs} } OPTIONAL, + ... +} + +CriticalityDiagnostics-IE-List ::= SEQUENCE (SIZE (1..maxNrOfErrors)) OF + SEQUENCE { + iECriticality Criticality, + iE-ID ProtocolIE-ID, + typeOfError TypeOfError, + iE-Extensions ProtocolExtensionContainer { {CriticalityDiagnostics-IE-List-ExtIEs} } OPTIONAL, + ... + } + +CriticalityDiagnostics-IE-List-ExtIEs PUA-PROTOCOL-EXTENSION ::= { + ... +} + +CriticalityDiagnostics-ExtIEs PUA-PROTOCOL-EXTENSION ::= { + ... +} + +TypeOfError ::= ENUMERATED { + not-understood, + missing, + ... +} + +END + +``` + +### 9.3.5 Common definitions + +``` + +-- ************************************************************** +-- +-- Common definitions +-- +-- ************************************************************** + +PUA-CommonDataTypes { +itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) +umts-Access (20) modules (3) pua(7) version1 (1) pUA-CommonDataTypes (3) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ************************************************************** +-- +-- Extension constants +-- +-- ************************************************************** + +``` + +``` + +-- ***** +maxPrivateIEs INTEGER := 65535 +maxProtocolExtensions INTEGER := 65535 +maxProtocolIEs INTEGER := 65535 + +-- ***** +-- +-- Common Data Types +-- +-- ***** +Criticality := ENUMERATED { reject, ignore, notify } + +Presence := ENUMERATED { optional, conditional, mandatory } + +ProcedureCode := INTEGER (0..255) + +PrivateIE-ID := CHOICE { + local INTEGER (0..65535), + global OBJECT IDENTIFIER +} + +ProtocolIE-ID := INTEGER (0..maxProtocolIEs) + +TriggeringMessage := ENUMERATED { initiating-message, successful-outcome, unsuccessful-outcome } + +END + +``` + +### 9.3.6 Constant definitions + +``` + +-- ***** +-- +-- Constant definitions +-- +-- ***** + +PUA-Constants { + itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) + umts-Access (20) modules (3) pua(7) version1 (1) pUA-Constants (4) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +IMPORTS + ProcedureCode, + ProtocolIE-ID +FROM PUA-CommonDataTypes; + +-- ***** + +``` + +``` + +-- +-- Elementary Procedures +-- +-- ******************************************************************* + +id-Connect ProcedureCode ::= 1 +id-DirectTransfer ProcedureCode ::= 2 +id-Disconnect ProcedureCode ::= 3 +id-ConnectionlessTransfer ProcedureCode ::= 4 +id-ErrorIndication ProcedureCode ::= 5 +id-privateMessage ProcedureCode ::= 6 + +-- ******************************************************************* +-- +-- Lists +-- +-- ******************************************************************* + +maxNrOfErrors INTEGER ::= 256 + +-- ******************************************************************* +-- +-- IEs +-- +-- ******************************************************************* + +id-Cause ProtocolIE-ID ::= 1 +id-CriticalityDiagnostics ProtocolIE-ID ::= 2 +id-PCAP-Context-ID ProtocolIE-ID ::= 3 +id-PCAP-Message ProtocolIE-ID ::= 4 +id-SAS-Indicator ProtocolIE-ID ::= 5 +id-TransactionID ProtocolIE-ID ::= 6 + +END + +``` + +### 9.3.7 Container definitions + +``` + +-- ******************************************************************* +-- +-- Container definitions +-- +-- ******************************************************************* + +PUA-Containers { +itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) +umts-Access (20) modules (3) pua(7) version1 (1) pUA-Containers (5) } + +DEFINITIONS AUTOMATIC TAGS ::= + +BEGIN + +-- ******************************************************************* + +``` + +``` + +-- +-- IE parameter types from other modules. +-- +-- ***** + +IMPORTS + Criticality, + Presence, + PrivateIE-ID, + ProtocolIE-ID, + maxPrivateIEs, + maxProtocolExtensions, + maxProtocolIEs +FROM PUA-CommonDataTypes; + +-- ***** +-- +-- Class Definition for Private IEs +-- +-- ***** + +PUA-PRIVATE-IES ::= CLASS { + &id PrivateIE-ID, + &criticality Criticality, + &Value, + &presence Presence +} +WITH SYNTAX { + ID &id + CRITICALITY &criticality + TYPE &Value + PRESENCE &presence +} + +-- ***** +-- +-- Class Definition for Protocol IEs +-- +-- ***** + +PUA-PROTOCOL-IES ::= CLASS { + &id ProtocolIE-ID UNIQUE, + &criticality Criticality, + &Value, + &presence Presence +} +WITH SYNTAX { + ID &id + CRITICALITY &criticality + TYPE &Value + PRESENCE &presence +} + +-- ***** +-- + +``` + +``` + +-- Class Definition for Protocol Extensions +-- +-- ***** + +PUA-PROTOCOL-EXTENSION ::= CLASS { + &id ProtocolIE-ID UNIQUE, + &criticality Criticality, + &Extension, + &presence Presence +} +WITH SYNTAX { + ID &id + CRITICALITY &criticality + EXTENSION &Extension + PRESENCE &presence +} + +-- ***** +-- +-- Container for Protocol IEs +-- +-- ***** + +ProtocolIE-Container {PUA-PROTOCOL-IES : IEsSetParam} ::= + SEQUENCE (SIZE (0..maxProtocolIEs)) OF + ProtocolIE-Field {{IEsSetParam}} + +ProtocolIE-Single-Container {PUA-PROTOCOL-IES : IEsSetParam} ::= + ProtocolIE-Field {{IEsSetParam}} + +ProtocolIE-Field {PUA-PROTOCOL-IES : IEsSetParam} ::= SEQUENCE { + id PUA-PROTOCOL-IES.&id {{IEsSetParam}}, + criticality PUA-PROTOCOL-IES.&criticality {{IEsSetParam}{@id}}, + value PUA-PROTOCOL-IES.&Value {{IEsSetParam}{@id}} +} + +-- ***** +-- +-- Container Lists for Protocol IE Containers +-- +-- ***** + +ProtocolIE-ContainerList {INTEGER : lowerBound, INTEGER : upperBound, PUA-PROTOCOL-IES : IEsSetParam} ::= + SEQUENCE (SIZE (lowerBound..upperBound)) OF + ProtocolIE-Container {{IEsSetParam}} + +-- ***** +-- +-- Container for Protocol Extensions +-- +-- ***** + +ProtocolExtensionContainer {PUA-PROTOCOL-EXTENSION : ExtensionSetParam} ::= + SEQUENCE (SIZE (1..maxProtocolExtensions)) OF + ProtocolExtensionField {{ExtensionSetParam}} + +``` + +``` + +ProtocolExtensionField {PUA-PROTOCOL-EXTENSION : ExtensionSetParam} ::= SEQUENCE { + id PUA-PROTOCOL-EXTENSION.&id ({ExtensionSetParam}), + criticality PUA-PROTOCOL-EXTENSION.&criticality ({ExtensionSetParam}{@id}), + extensionValue PUA-PROTOCOL-EXTENSION.&Extension ({ExtensionSetParam}{@id}) +} + +``` + +``` + +-- ***** +-- +-- Container for Private IEs +-- +-- ***** + +``` + +``` + +PrivateIE-Container {PUA-PRIVATE-IES : IEsSetParam } ::= + SEQUENCE (SIZE (1.. maxPrivateIEs)) OF + PrivateIE-Field {{IEsSetParam}} + +``` + +``` + +PrivateIE-Field {PUA-PRIVATE-IES : IEsSetParam} ::= SEQUENCE { + id PUA-PRIVATE-IES.&id ({IEsSetParam}), + criticality PUA-PRIVATE-IES.&criticality ({IEsSetParam}{@id}), + value PUA-PRIVATE-IES.&Value ({IEsSetParam}{@id}) +} + +``` + +END + +## 9.4 Message transfer syntax + +PUA shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax as specified in ref. ITU-T Rec. X.691 [6]. + +# 10 Handling of unknown, unforeseen, and erroneous protocol data + +## 10.1 General + +Protocol Error cases can be divided into three classes: + +- Transfer Syntax Error; +- Abstract Syntax Error; +- Logical Error. + +Protocol errors can occur in the following functions within a receiving node: + +![Diagram illustrating protocol errors in PUA. It shows two boxes: 'PUA functional entity' at the top and 'ASN.1 Decoding' at the bottom, connected by a double-headed arrow. To the right of the top box, a bracket groups 'Logical Errors' and 'Abstract Syntax Errors'. To the right of the bottom box, a bracket groups 'Transfer Syntax Errors'. A large upward-pointing arrow on the far right indicates the flow of errors from the bottom box to the top box.](446100c084b94817a19c319fa776b412_img.jpg) + +``` + +graph TD + subgraph PUA_errors [ ] + LE[Logical Errors] + ASE[Abstract Syntax Errors] + end + subgraph ASN1_errors [ ] + TSE[Transfer Syntax Errors] + end + ASN1[ASN.1 Decoding] --> PUA[PUA functional entity] + PUA --- LE + PUA --- ASE + ASN1 --- TSE + TSE --> LE + TSE --> ASE + style PUA_errors fill:none,stroke:none + style ASN1_errors fill:none,stroke:none + +``` + +Diagram illustrating protocol errors in PUA. It shows two boxes: 'PUA functional entity' at the top and 'ASN.1 Decoding' at the bottom, connected by a double-headed arrow. To the right of the top box, a bracket groups 'Logical Errors' and 'Abstract Syntax Errors'. To the right of the bottom box, a bracket groups 'Transfer Syntax Errors'. A large upward-pointing arrow on the far right indicates the flow of errors from the bottom box to the top box. + +**Figure 10.1-1: Protocol errors in PUA** + +The information stated in subclauses 10.2, 10.3 and 10.4, to be included in the message used when reporting an error, is what at minimum shall be included. Other optional information elements within the message may also be included, if available. This is also valid for the case when the reporting is done with a response message. The latter is an exception to what is stated in subclause 4.1. + +## 10.2 Transfer Syntax Error + +A Transfer Syntax Error occurs when the receiver is not able to decode the received physical message Transfer syntax errors are always detected in the process of ASN.1 decoding. If a Transfer Syntax Error occurs, the receiver should initiate Error Indication procedure with appropriate cause value for the Transfer Syntax protocol error. + +## 10.3 Abstract Syntax Error + +### 10.3.1 General + +An Abstract Syntax Error occurs when the receiving functional PUA entity: + +1. receives IEs or IE groups that cannot be understood (unknown IE id); +2. receives IEs for which the logical range is violated (e.g.: ASN.1 definition: 0 to 15, the logical range is 0 to 10 (values 11 to 15 are undefined), and 12 will be received; this case will be handled as an abstract syntax error using criticality information sent by the originator of the message); +3. does not receive IEs or IE groups but according to the specified presence of the concerning object, the IEs or IE groups should have been present in the received message; +4. receives IEs or IE groups that are defined to be part of that message in wrong order or with too many occurrences of the same IE or IE group; +5. receives IEs or IE groups but according to the conditional presence of the concerning object and the specified condition, the IEs or IE groups should not have been present in the received message. + +Cases 1 and 2 (not comprehended IE/IE group) are handled based on received Criticality information. Case 3 (missing IE/IE group) is handled based on Criticality information and Presence information for the missing IE/IE group specified in the version of the specification used by the receiver. Case 4 (IEs or IE groups in wrong order or with too many occurrences) and Case 5 (erroneously present conditional IEs or IE groups) result in rejecting the procedure. + +If an Abstract Syntax Error occurs, the receiver shall read the remaining message and shall then for each detected Abstract Syntax Error act according to the Criticality Information and Presence Information for the IE/IE group due to which Abstract Syntax Error occurred in accordance with subclauses 10.3.4 and 10.3.5. The handling of cases 4 and 5 is specified in subclause 10.3.6. + +### 10.3.2 Criticality Information + +In the PUA messages there is criticality information set for individual IEs and/or IE groups. This criticality information instructs the receiver how to act when receiving an IE or an IE group that is not comprehended i.e. the entire item (IE or IE group) which is not (fully or partially) comprehended shall be treated in accordance with its own criticality information as specified in subclause 10.3.4. + +In addition, the criticality information is used in case of the missing IE/IE group abstract syntax error (see subclause 10.3.5). + +The receiving node shall take different actions depending on the value of the Criticality Information. The three possible values of the Criticality Information for an IE/IE group are: + +- Reject IE; +- Ignore IE and Notify Sender; +- Ignore IE. + +The following rules restrict when a receiving entity may consider an IE, an IE group or an EP not comprehended (not implemented), and when action based on criticality information is applicable: + +1. IE or IE group: When one new or modified IE or IE group is implemented for one EP from a standard version, then other new or modified IEs or IE groups specified for that EP in that standard version shall be considered comprehended by the receiving entity (some may still remain unsupported). +2. EP: The comprehension of different EPs within a standard version or between different standard versions is not mandated. Any EP that is not supported may be considered not comprehended, even if another EP from that standard version is comprehended, and action based on criticality shall be applied. + +### 10.3.3 Presence Information + +For many IEs/IE groups which are optional according to the ASN.1 transfer syntax, PUA specifies separately if the presence of these IEs/IE groups is optional or mandatory with respect to RNS application by means of the presence field of the concerning object of class PUA-PROTOCOL-IES, PUA-PROTOCOL-IES-PAIR, PUA-PROTOCOL-EXTENSION or PUA-PRIVATE-IES. + +The presence field of the indicated classes supports three values: + +1. Optional; +2. Conditional; +3. Mandatory. + +If an IE/IE group is not included in a received message and the presence of the IE/IE group is mandatory or the presence is conditional and the condition is true according to the version of the specification used by the receiver, an abstract syntax error occurs due to a missing IE/IE group. + +### 10.3.4 Not comprehended IE/IE group + +#### 10.3.4.1 Procedure Code + +The receiving node shall treat the different types of received criticality information of the *Procedure Code* according to the following: + +**Reject IE:** + +- If a message is received with a *Procedure Code* marked with "*Reject IE*" which the receiving node does not comprehend, the receiving node shall reject the procedure using the Error Indication procedure. + +**Ignore IE and Notify Sender:** + +- If a message is received with a *Procedure Code* marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the procedure and initiate the Error Indication procedure. + +**Ignore IE:** + +- If a message is received with a *Procedure Code* marked with "*Ignore IE*" which the receiving node does not comprehend, the receiving node shall ignore the procedure. + +When using the Error Indication procedure to reject a procedure or to report an ignored procedure it shall include the *Procedure Code* IE, the *Triggering Message* IE, and the *Procedure Criticality* IE in the *Criticality Diagnostics* IE. + +#### 10.3.4.1A Type of Message + +When the receiving node cannot decode the *Type of Message* IE, the Error Indication procedure shall be initiated with an appropriate cause value. + +#### 10.3.4.2 IEs other than the Procedure Code and Type of Message + +The receiving node shall treat the different types of received criticality information of an IE/IE group other than the *Procedure Code* IE and *Type of Message* IE according to the following: + +**Reject IE:** + +- If a message *initiating* a procedure is received containing one or more IEs/IE groups marked with "*Reject IE*" which the receiving node does not comprehend; none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the rejection of one or more IEs/IE groups using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- If a message *initiating* a procedure that does not have a message to report unsuccessful outcome is received containing one or more IEs/IE groups marked with "*Reject IE*" which the receiving node does not comprehend, the receiving node shall terminate the procedure and initiate the Error Indication procedure. +- If a *response* message is received containing one or more IEs marked with "*Reject IE*" which the receiving node does not comprehend, the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling. + +##### Ignore IE and Notify Sender: + +- If a message *initiating* a procedure is received containing one or more IEs/IE groups marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups, and report in the response message of the procedure that one or more IEs/IE groups have been ignored. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the response message, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- if a message *initiating* a procedure that does not have a message to report the outcome of the procedure is received containing one or more IEs/IE groups marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups, and initiate the Error Indication procedure to report that one or more IEs/IE groups have been ignored. +- If a *response* message is received containing one or more IEs/IE groups marked with "*Ignore IE and Notify Sender*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IE/IE groups, continue with the procedure as if the not comprehended IEs/IE groups were not received (except for the reporting) using the understood IEs/IE groups and initiate the Error Indication procedure. + +##### Ignore IE: + +- If a message *initiating* a procedure is received containing one or more IEs/IE groups marked with "*Ignore IE*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups and continue with the procedure as if the not comprehended IEs/IE groups were not received using only the understood IEs/IE groups. +- If a *response* message is received containing one or more IEs/IE groups marked with "*Ignore IE*" which the receiving node does not comprehend, the receiving node shall ignore the content of the not comprehended IEs/IE groups and continue with the procedure as if the not comprehended IEs/IE groups were not received using the understood IEs/IE groups. + +When reporting not comprehended IEs/IE groups marked with "*Reject IE*" or "*Ignore IE and Notify Sender*" using a response message defined for the procedure, the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group. + +When reporting not comprehended IEs/IE groups marked with "*Reject IE*" or "*Ignore IE and Notify Sender*" using the Error Indication procedure, the *Procedure Code* IE, the *Triggering Message* IE, *Procedure Criticality* IE, and the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group. + +### 10.3.5 Missing IE or IE group + +The receiving node shall treat the missing IE/IE group according to the criticality information for the missing IE/IE group in the received message specified in the version of the present document used by the receiver: + +#### Reject IE: + +- if a received message *initiating* a procedure is missing one or more IEs/IE groups with specified criticality "*Reject IE*"; none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the missing IEs/IE groups using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- if a received message *initiating* a procedure that does not have a message to report unsuccessful outcome is missing one or more IEs/IE groups with specified criticality "*Reject IE*", the receiving node shall terminate the procedure and initiate the Error Indication procedure. +- if a received *response* message is missing one or more IEs/IE groups with specified criticality "*Reject IE*", the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling. + +#### Ignore IE and Notify Sender: + +- if a received message *initiating* a procedure is missing one or more IEs/IE groups with specified criticality "*Ignore IE and Notify Sender*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and report in the response message of the procedure that one or more IEs/IE groups were missing. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the response message, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- if a received message *initiating* a procedure that does not have a message to report the outcome of the procedure is missing one or more IEs/IE groups with specified criticality "*Ignore IE and Notify Sender*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and initiate the Error Indication procedure to report that one or more IEs/IE groups were missing. +- if a received *response* message is missing one or more IEs/IE groups with specified criticality "*Ignore IE and Notify Sender*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message and initiate the Error Indication procedure to report that one or more IEs/IE groups were missing. + +#### Ignore IE: + +- if a received message *initiating* a procedure is missing one or more IEs/IE groups with specified criticality "*Ignore IE*", the receiving node shall ignore that those IEs are missing and continue with the procedure based on the other IEs/IE groups present in the message. +- if a received *response* message is missing one or more IEs/IE groups with specified criticality "*Ignore IE*", the receiving node shall ignore that those IEs/IE groups are missing and continue with the procedure based on the other IEs/IE groups present in the message. + +When reporting missing IEs/IE groups with specified criticality "*Reject IE*" or "*Ignore IE and Notify Sender*" using a response message defined for the procedure, the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group. + +When reporting missing IEs/IE groups with specified criticality "*Reject IE*" or "*Ignore IE and Notify Sender*" using the Error Indication procedure, the *Procedure Code* IE, the *Triggering Message* IE, *Procedure Criticality* IE, and the *Information Element Criticality Diagnostics* IE shall be included in the *Criticality Diagnostics* IE for each reported IE/IE group. + +### 10.3.6 IEs or IE groups received in wrong order or with too many occurrences or erroneously present + +If a message with IEs or IE groups in wrong order or with too many occurrences is received or if IEs or IE groups with a conditional presence are present when the condition is not met (i.e. erroneously present), the receiving node shall behave according to the following: + +- If a message *initiating* a procedure is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, none of the functional requests of the message shall be executed. The receiving node shall reject the procedure and report the cause value "Abstract Syntax Error (Falsely Constructed Message)" using the message normally used to report unsuccessful outcome of the procedure. In case the information received in the initiating message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsuccessful outcome of the procedure, the receiving node shall instead terminate the procedure and initiate the Error Indication procedure. +- If a message *initiating* a procedure that does not have a message to report unsuccessful outcome is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, the receiving node shall terminate the procedure and initiate the Error Indication procedure, and use cause value "Abstract Syntax Error (Falsely Constructed Message)". +- If a *response* message is received containing IEs or IE groups in wrong order or with too many occurrences or erroneously present, the receiving node shall consider the procedure as unsuccessfully terminated and initiate local error handling. + +When determining the correct order only the IEs specified in the specification version used by the receiver shall be considered. + +## 10.4 Logical Error + +Logical error situations occur when a message is comprehended correctly, but the information contained within the message is not valid (i.e. semantic error), or describes a procedure which is not compatible with the state of the receiver. In these conditions, the following behaviour shall be performed (unless otherwise specified) as defined by the class of the elementary procedure, irrespective of the criticality information of the IE's/IE groups containing the erroneous values. + +### Class 1: + +Where the logical error occurs in a request message of a class 1 procedure, and the procedure has a message to report this unsuccessful outcome, this message shall be sent with an appropriate cause value. Typical cause values are: + +- Semantic Error; +- Message not compatible with receiver state. + +Where the logical error is contained in a request message of a class 1 procedure, and the procedure does not have a message to report this unsuccessful outcome, the procedure shall be terminated and the Error Indication procedure shall be initiated with an appropriate cause value. The *Procedure Code* IE and the *Triggering Message* IE within the *Criticality Diagnostics* IE shall then be included in order to identify the message containing the logical error. + +Where the logical error exists in a response message of a class 1 procedure, the procedure shall be considered as unsuccessfully terminated and local error handling shall be initiated. + +### Class 2: + +Where the logical error occurs in a message of a class 2 procedure, the procedure shall be terminated and the Error Indication procedure shall be initiated with an appropriate cause value. The *Procedure Code* IE and the *Triggering Message* IE within the *Criticality Diagnostics* IE shall then be included in order to identify the message containing the logical error. + +## 10.5 Exceptions + +The error handling for all the cases described hereafter shall take precedence over any other error handling described in the other subclauses of clause 10. + +- If any type of error (Transfer Syntax Error, Abstract Syntax Error or Logical Error) is detected in the ERROR INDICATION message, it shall not trigger the Error Indication procedure in the receiving Node but local error handling. +- In case a response message or Error Indication message needs to be returned, but the information necessary to determine the receiver of that message is missing, the procedure shall be considered as unsuccessfully terminated and local error handling shall be initiated. +- If an error that terminates a procedure occurs, the returned cause value shall reflect the error that caused the termination of the procedure even if one or more abstract syntax errors with criticality "ignore and notify" have earlier occurred within the same procedure. + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|--------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 14-11-2013 | RAN3#82 | R3-132041 | | | Skeleton | 0.0.0 | 0.0.1 | +| 14-11-2013 | RAN3#82 | R3-132042 | | | Prelim Material added | 0.0.1 | 0.1.0 | +| 14-11-2013 | RAN3#82 | R3-132393 | | | Corrected prelim material, added EPs. | 0.1.0 | 0.2.0 | +| 14-11-2013 | RAN3#82 | R3-132395 | | | Added IEs and ASN.1 | 0.2.0 | 0.3.0 | +| 22-11-2013 | RAN3#82 | R3-132394 | | | Updated | 0.3.0 | 0.4.0 | +| 26-11-2013 | RAN#62 | RP-131649 | | | Presented for approval | 0.4.0 | 1.0.0 | +| 03-12-2013 | RAN#62 | | | | Corrected templates | 1.0.0 | 1.0.1 | +| 12-2013 | | | | | Upgraded to Rel-12, and put under change control | 1.0.1 | 12.0.0 | +| 06-2014 | RAN#64 | RP-140907 | 0001 | - | Add the Object Identifier for PUA | 12.0.0 | 12.1.0 | +| 12-2014 | RAN#66 | RP-142094 | 0002 | - | Rapporteur Review | 12.1.0 | 12.2.0 | +| 12-2015 | RAN#70 | | | | Update to Rel-13 version (MCC) | 12.2.0 | 13.0.0 | +| 03-2016 | RAN#71 | RP-160449 | 0004 | | Rapporteur Review of TS 25.470 | 13.0.0 | 13.1.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-07 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25484/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/Rel-16/25_series/25484/1439cb942d9e363bbb3161b5540dd8c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0d96e3743baeaf51c94387ef90e7dd4d9aa2df5 --- /dev/null +++ b/marked/Rel-16/25_series/25484/1439cb942d9e363bbb3161b5540dd8c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a0b9940b218fe059315d8c82c986fa3d4152fb4fd499371ff98a7abac8d4c3f +size 63723 diff --git a/marked/Rel-16/25_series/25484/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg b/marked/Rel-16/25_series/25484/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b03a1189cf78f8c566895289df9bf9e88942575 --- /dev/null +++ b/marked/Rel-16/25_series/25484/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:888be09d8f2bc9ce54a62cfe3ca7b578b955c49976444447fadcaf327ec396dd +size 26973 diff --git a/marked/Rel-16/25_series/25484/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/25_series/25484/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4630352f269d08856ed95f8db9c9fe6b492d7398 --- /dev/null +++ b/marked/Rel-16/25_series/25484/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dfead361dfe87f3dcca5744b5ef539e8b223b0b5fe2e7e9bf6276ce486ea6fb4 +size 17100 diff --git a/marked/Rel-16/25_series/25484/1d27fed9c01eb99f6535283f35fe3bbf_img.jpg b/marked/Rel-16/25_series/25484/1d27fed9c01eb99f6535283f35fe3bbf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9063082a8f0513236e9773e7c05bbf395927402e --- /dev/null +++ b/marked/Rel-16/25_series/25484/1d27fed9c01eb99f6535283f35fe3bbf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:299c9c8ded10b3a3d21c4c151cd4318c453757959eb8d0b0732b951d4503b48d +size 92283 diff --git a/marked/Rel-16/25_series/25484/2bc39576969969ffe6d3f3d5264bba75_img.jpg b/marked/Rel-16/25_series/25484/2bc39576969969ffe6d3f3d5264bba75_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bbd6145061350b668a836f5eb23bfb133ccf65a8 --- /dev/null +++ b/marked/Rel-16/25_series/25484/2bc39576969969ffe6d3f3d5264bba75_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e07b50355310730c48c992787f5583e28578184496e0be35befd696c651dd04b +size 21314 diff --git a/marked/Rel-16/25_series/25484/410562339ce067fdc6fa41940c118658_img.jpg b/marked/Rel-16/25_series/25484/410562339ce067fdc6fa41940c118658_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a94c9b33ede65ff0dffc0a91fa317c5166143459 --- /dev/null +++ b/marked/Rel-16/25_series/25484/410562339ce067fdc6fa41940c118658_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:430e2ab771299aa973d5969d843ca24e0317e95fe2d7f7c1230c464e7337f631 +size 71738 diff --git a/marked/Rel-16/25_series/25484/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/25_series/25484/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70962cf15c1f40ba9055abc698ac1a376e54a785 --- /dev/null +++ b/marked/Rel-16/25_series/25484/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:468ef635be7021cb4a59cd6a46ed7206f0cb96ca157c21e59b0412b5a5cebfd1 +size 86382 diff --git a/marked/Rel-16/25_series/25484/a7c51c18111139f9aca2805114108565_img.jpg b/marked/Rel-16/25_series/25484/a7c51c18111139f9aca2805114108565_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2abe868a8eacd70d69a0be16b3d748b68e656ff --- /dev/null +++ b/marked/Rel-16/25_series/25484/a7c51c18111139f9aca2805114108565_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5fe4e265327170189f0223b8cfb0fe13d4b7c533cfbc09e82a8899bafe54a37 +size 44159 diff --git a/marked/Rel-16/25_series/25484/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/25_series/25484/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29fa3a91d51d6d2ae24e5c3db2476aebb7344aa3 --- /dev/null +++ b/marked/Rel-16/25_series/25484/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f78bd5f5fcea8af69a8ca9c63537074b3d519e3c97be13328c75985e6b501ec +size 108002 diff --git a/marked/Rel-16/25_series/25484/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/25_series/25484/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..73c0654b0d17191f47926807d9f75281ceb02c06 --- /dev/null +++ b/marked/Rel-16/25_series/25484/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:151d92060b16ae858b70f96dd7be0aa698671901e0dee2cca3c33ad6275c0f29 +size 145573 diff --git a/marked/Rel-16/25_series/25484/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/25_series/25484/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..766927e6ade335aa6c800a04c57828fe985ee516 --- /dev/null +++ b/marked/Rel-16/25_series/25484/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87881b237efcac85e0505e595e9fe66f05764b64e477d968cab96e334a253517 +size 94659 diff --git a/marked/Rel-16/25_series/25484/raw.md b/marked/Rel-16/25_series/25484/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0e1209d8d9b3792eb344a1d095410d0ac3275211 --- /dev/null +++ b/marked/Rel-16/25_series/25484/raw.md @@ -0,0 +1,680 @@ + + + + +Error! No +text of + +Error! No text of specified style in +document. + +# Contents + +| | | +|------------------------------------------------------------------------------|----| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions, symbols and abbreviations..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Symbols..... | 6 | +| 3.3 Abbreviations ..... | 7 | +| 4 Automatic Neighbour Relation Function, Main Concepts..... | 7 | +| 4.1 General ..... | 7 | +| 4.2 ANR Handling in the UTRAN Infrastructure - Overall Description..... | 8 | +| 4.2.1 Iur Connectivity exists between the involved RNCs..... | 8 | +| 4.2.1.1 ANR Report over Uu for UTRAN cells ..... | 8 | +| 4.2.1.2 ANR Report over Iur for UTRAN cells..... | 9 | +| 4.2.1.3 ANR Report over Iur for IRAT cells..... | 11 | +| 4.2.2 Iur Connectivity does not exist between some RNCs involved in ANR..... | 12 | +| 4.2.2.1 ANR report over Uu for UTRAN cells..... | 12 | +| 4.2.3 ANR Report over Uu for IRAT cells - with and without Iur ..... | 13 | +| 5 Functions and Procedures ..... | 14 | +| 5.1 ANR Management..... | 15 | +| 5.1.1 ANR Report Forwarding ..... | 15 | +| 5.1.2 ANR Report Distribution Controlling ..... | 15 | +| 5.2 Neighbour Cell Configuration..... | 16 | +| 5.2.1 Neighbour Cell Configuration for Intra-RNS cells ..... | 16 | +| 5.2.2 Neighbour Cell Configuration for Inter-RNS cells (with Iur)..... | 16 | +| 5.2.3 Neighbour Cell Configuration (without Iur) ..... | 16 | +| 5.3 ANR Logging configuration ..... | 16 | +| 5.3.1 Configuration parameters ..... | 17 | +| 5.3.2 Configuration validity ..... | 17 | +| 5.4 Measurement Collection ..... | 18 | +| 5.5 Measurement Reporting ..... | 18 | +| 5.6 UE Capabilities ..... | 19 | +| Annex A (informative): Change history..... | 20 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd 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 is a technical specification of the overall support of Automatic Neighbour Relation (ANR) Function in UTRA. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + +# 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**Base UTRAN Cell:** A cell in UTRAN for which a missing neighbour cell is detected. + +**Neighbour Cell:** A cell in UTRAN, LTE or GSM/GERAN that is a neighbour cell to a Base UTRAN Cell. + +**Neighbour Cell Identifier (NCI):** The identifier of a Neighbour Cell + +**Neighbour cell Relation (NR):** Information that a Neighbour Cell, identified with NCI, is a neighbour to a Base UTRAN Cell. NR is stored in the RNC controlling the Base UTRAN Cell. + +**Conceptual Neighbour Relation Functions:** The ANR is described using a number of conceptual entities and functions in the RNC: Neighbour Relation Table, Neighbour Relation Table Management Function, Neighbour Removal Function and Neighbour Detection Function. These entities and functions are used for descriptive purpose only and shall not be regarded as requirements on the implementation in RNC. + +**Receiving RNC:** the RNC receiving the ANR report over Uu + +**Base RNC:** the CRNC of the Base UTRAN Cell + +**Neighbour RNC:** the CRNC of the Neighbour Cell in UTRAN + +**ANR-PLMN List:** A list of PLMNs that is the RPLMN and the list of equivalent PLMNs for the UE at the point of receiving ANR logging configuration. + +**ANR measurement:** Physical measurements and reading of System Information towards detected cells outside NCL. + +**ANR logging:** Storing of essential information of detected cell into UE internal ANR log, when one or more detected cell satisfies ANR logging criteria. + +## 3.2 Symbols + +Void + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] apply. + +# 4 Automatic Neighbour Relation Function, Main Concepts + +## 4.1 General + +![Diagram showing the interaction between RNC and O&M due to ANR. It includes an O&M block, an RNC block containing the ANR function (NRT Management, Neighbour Removal, Neighbour Detection), and an RRC block. Arrows show data flow between them, including 'NR report', 'Add/Update Neighbor Relations', 'NR_remove', 'NR_add', 'NR_update', and 'Cell Information'. A 'Neighbor Relation Table' is shown on the left with columns for NR, NCI, No Remove, and No HO.](1d27fed9c01eb99f6535283f35fe3bbf_img.jpg) + +The diagram illustrates the interaction between the O&M (Operations and Management) and the RNC (Radio Network Controller) for the Automatic Neighbour Relation (ANR) function. The RNC contains an 'ANR function' block which includes the 'NRT Management Function', 'Neighbour Removal Function', and 'Neighbour Detection Function'. The 'NRT Management Function' is connected to the 'O&M' via 'NR report' and 'Add/Update Neighbor Relations' messages. It also interacts with the 'Neighbour Removal Function' (via 'NR\_remove') and the 'Neighbour Detection Function' (via 'NR\_add'). The 'NRT Management Function' updates the 'Neighbor Relation Table' (via 'NR\_update'). The 'Neighbour Detection Function' receives 'Cell Information' from the 'RRC' and 'Neighbour Cell Information' from an external source. The 'Neighbour Removal Function' receives 'Internal information' from an external source. The 'Neighbor Relation Table' is a table with the following structure: + +| Neighbour Relation | | O&M controlled Neighbour Relation Attributes | | +|--------------------|-------|----------------------------------------------|-------| +| NR | NCI | No Remove | No HO | +| 1 | NCI#1 | | | +| 2 | NCI#1 | ✓ | | +| 3 | NCI#1 | | ✓ | +| | | | | + +Diagram showing the interaction between RNC and O&M due to ANR. It includes an O&M block, an RNC block containing the ANR function (NRT Management, Neighbour Removal, Neighbour Detection), and an RRC block. Arrows show data flow between them, including 'NR report', 'Add/Update Neighbor Relations', 'NR\_remove', 'NR\_add', 'NR\_update', and 'Cell Information'. A 'Neighbor Relation Table' is shown on the left with columns for NR, NCI, No Remove, and No HO. + +Figure 4.1-1: Interaction between RNC and O&M due to ANR + +The ANR function resides in the RNC and is composed of the Neighbour Relation Table (NRT) Management Function, Neighbour Detection Function and Neighbour Removal Function. + +The Neighbour Detection Function detects new neighbours and adds them to the NRT. The Neighbour Removal Function removes outdated NRs. + +A Neighbour cell Relation (NR) between a Base UTRAN Cell and a Neighbour Cell exists if the RNC controlling the Base UTRAN Cell: + +- a) Knows the following Neighbour Cell information: + - Neighbour cell is in UTRAN: PLMN-Id, Cell Identifier(C-ID), RNC-ID/Extended RNC-ID, + - Neighbour cell is in LTE: ECGI (PLMN Id + Cell Identity) + - Neighbour cell is in GSM/GERAN: PLMN Id, LAC, CI, BSIC +- b) Has an entry in the Neighbour Relation Table for the Base UTRAN Cell identifying the neighbour cell. +- c) Has all required attributes defined in the Neighbour Relation Table entry or set to default values. Among these attributes are the frequency information (UARFCN, BCCH ARFCN, EARFCN) and handover routing parameters not already considered in (a): + - Neighbour cell is in UTRAN: LAC and RAC + - Neighbour cell is in LTE: TAI + +For each NR, the NRT contains the Neighbour Cell Identifier (NCI), which identifies the neighbour cells. A neighbour cell may be a UTRAN, LTE or GSM cell. Furthermore, each NR has two attributes, the No Remove and the No HO attributes. These attributes have the following definitions: + +- No Remove: If checked, the RNC shall not remove the Neighbour cell Relation from the NRT. +- No HO: If checked, the Neighbour cell Relation shall not be used as a neighbour cell by Intra RNS, Inter RNS or Inter RAT mobility functions in UTRAN. + +The ANR function also allows O&M to manage the NRT. O&M can add and delete NRs. It can also change the attributes of the NR. The O&M system is informed about changes in the NRT. + +## 4.2 ANR Handling in the UTRAN Infrastructure - Overall Description + +If UTRAN ANR functionality is supported in UTRAN, RNC shall be able to configure the UE to perform the ANR measurement. ANR capable UE performs the ANR measurement and records in its logbook newly detected cells which meet the criteria given in the configuration. The Receiving RNC uses RRC signalling to retrieve the ANR report over the Uu interface after the UE has indicated that it has a logged ANR report. The Receiving RNC handles the ANR report and may forward the ANR report to different RNCs. + +This chapter illustrates the handling and message sequences to be used to configure a new neighbour relation for a UTRAN cell. + +### 4.2.1 Iur Connectivity exists between the involved RNCs + +The ANR function supports forwarding of ANR reports from the Receiving RNC to RNCs indicated as Base RNCs in the ANR report. Furthermore the ANR function supports suspension (and resuming) ANR logs reporting over Iur from other RNCs as described in 5.1.2. This chapter describes the handling in the Receiving, Base and Neighbour RNCs when Iur connectivity exists between the involved RNCs. + +#### 4.2.1.1 ANR Report over Uu for UTRAN cells + +When receiving an ANR report over Uu, the Receiving RNC uses the globally unique cell identities in the report to determine the network addresses of the RNCs that are controlling the Base UTRAN cells. The network address of this Base RNC is retrieved using configuration in the Receiving RNC and/or O&M. + +The Receiving RNC decides the necessity to forward the ANR report. If the Base UTRAN Cell is under control of the Receiving RNC, the Receiving RNC terminates the relevant ANR report entry, and may update the Neighbouring Relation accordingly. Otherwise, the ANR report is forwarded to the Base RNCs over Iur with the RNSAP Direct Information Transfer procedure. + +If newly detected neighbour cells are controlled by another RNC the RNSAP Information Exchange Initiation procedure is used to request cell information from the neighbour RNC. In addition the Base RNC may interact with O&M before a neighbour relation is stored in the NRT. + +![Sequence diagram for ANR Report over Uu for UTRAN cells. Lifelines: UE, RNC1 (Receiving RNC, Base RNC), RNC2 (Base RNC), RNC3 (Base RNC), and O&M. The process involves an ANR report request from RNC1 to UE, a UE ANR Report with a list of neighbor cells, RNSAP Direct Information Transfer messages from RNC1 to RNC2 and RNC3, an RNSAP Information Exchange Initiation Request from RNC1 to RNC2, an RNSAP Information Exchange Initiation Response from RNC2 to RNC1, a Neighbour handling message from RNC1 to RNC2, and finally storing the neighbor cells in the NRT.](d0abac95583b52a3b35f74a215567334_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RNC1 as RNC1 +(Role: +- Receiving RNC +- Base RNC) + participant RNC2 as RNC2 +(Role: +- Base RNC) + participant RNC3 as RNC3 +(Role: +- Base RNC) + participant OM as O&M + + Note right of RNC1: Role receiving RNC: +Use RRC Cell-ID of the listed cells to retrieve addresses of +Base RNCs that shall have the ANR report (from configuration +in RNC /O&M). +RNC2 and RNC3 are receivers of ANR report. + + RNC1->>UE: ANR report request + UE-->>RNC1: UE ANR Report +(list NR: +- Cell-ID a -> Cell-ID b, +- Cell-ID c->Cell-ID-d +- Cell-ID e->Cell-ID f...) + + RNC1->>RNC2: RNSAP: DIRECT INFORMATION +TRANSFER +(ANR report: transparent to RNSAP) + RNC1->>RNC3: RNSAP: DIRECT INFORMATION TRANSFER +(ANR report: transparent to RNSAP) + + Note right of RNC1: Role Base RNC: +RNC1 retrieves its potential neighbours: +Cell information is needed for potential neighbours in RNC2 +Address of RNC2 are retrieved based on Cell-ID + + RNC1->>RNC2: RNSAP: INFORMATION EXCHANGE +INITIATION REQUEST +(List: C-ID n, type=on demand) + RNC2-->>RNC1: RNSAP: INFORMATION EXCHANGE +INITIATION RESPONSE +(List: cell attributes) + + RNC1->>RNC2: Neighbour handling: RNC1(C-ID m)-> RNC2(C-ID n), [implementation dependent] + + Note right of RNC1: Store UTRAN neighbour cells C-ID n in NRT after +interaction with O&M. Store the cell attributes +received over lur and other cell configuration +parameters (from configuration or O&M). + +``` + +Sequence diagram for ANR Report over Uu for UTRAN cells. Lifelines: UE, RNC1 (Receiving RNC, Base RNC), RNC2 (Base RNC), RNC3 (Base RNC), and O&M. The process involves an ANR report request from RNC1 to UE, a UE ANR Report with a list of neighbor cells, RNSAP Direct Information Transfer messages from RNC1 to RNC2 and RNC3, an RNSAP Information Exchange Initiation Request from RNC1 to RNC2, an RNSAP Information Exchange Initiation Response from RNC2 to RNC1, a Neighbour handling message from RNC1 to RNC2, and finally storing the neighbor cells in the NRT. + +**Figure 4.2.1.1-1 ANR Report over Uu for UTRAN cells** + +#### 4.2.1.2 ANR Report over lur for UTRAN cells + +On reception of an ANR report from another RNC using the RNSAP Direct Information Transfer procedure, the Base RNC uses the globally unique cell identities and L1 information in the ANR report, and optionally also configuration in the RNC/O&M, to determine if the ANR report contains any potential neighbour cells. If any of these potential neighbour cells is controlled by another RNC the RNSAP Information Exchange Initiation procedure may be used to request cell information from the neighbour RNC. In addition the Base RNC may interact with O&M before a neighbour relation is be stored in the NRT as shown in the figure below: + +![Sequence diagram showing ANR report over Iur for UTRAN cells. Lifelines: RNC1 (Receiving RNC), RNC2 (Base RNC), RNC3 (Neighbour RNC), and O&M. The process involves an ANR report from RNC1 to RNC2, internal processing in RNC2, an information exchange initiation between RNC2 and RNC3, neighbour handling, and finally storing neighbour cells in NRT after O&M interaction.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +**Intra UMTS, Inter RNS, ANR report over Iur** + +``` + +sequenceDiagram + participant RNC1 as RNC1 +(Role: +- Receiving RNC) + participant RNC2 as RNC2 +(Role: +- Base RNC) + participant RNC3 as RNC3 +(Role: +- Neighbour RNC) + participant OM as O&M + + Note left of RNC1: RNSAP: DIRECT INFORMATION TRANSFER, +ANR report transparent: +(list NR: +- Cell-ID a -> Cell-ID b, +- Cell-ID c->Cell-ID d, +- Cell-ID e->Cell-ID f,...) + RNC1->>RNC2: RNSAP: DIRECT INFORMATION TRANSFER, ANR report transparent + Note right of RNC2: Role Base RNC: +RNC2 retrieves its potential neighbours: +Cell information is needed for potential neighbours in RNC3 +Address of RNC3 is retrieved based on Cell-ID in ANR report + RNC2->>RNC3: RNSAP: INFORMATION EXCHANGE INITIATION REQUEST +(List: C-ID n, type=on demand) + RNC3-->>RNC2: RNSAP: INFORMATION EXCHANGE INITIATION RESPONSE +(List: cell attributes) + Note right of RNC2: Neighbour handling: RNC2 (C-ID m)-> RNC3 (C-ID n) +[implementation dependent] + RNC2->>RNC3: Neighbour handling: RNC2 (C-ID m)-> RNC3 (C-ID n) [implementation dependent] + Note right of RNC2: Store UTRAN neighbour cells (C-ID n) in NRT after +interaction with O&M. Store the cell attributes received +over Iur and other cell configuration parameters (from +configuration and/or O&M). + RNC2->>OM: + +``` + +Sequence diagram showing ANR report over Iur for UTRAN cells. Lifelines: RNC1 (Receiving RNC), RNC2 (Base RNC), RNC3 (Neighbour RNC), and O&M. The process involves an ANR report from RNC1 to RNC2, internal processing in RNC2, an information exchange initiation between RNC2 and RNC3, neighbour handling, and finally storing neighbour cells in NRT after O&M interaction. + +**Figure 4.2.1.2-1 ANR Report over Iur for UTRAN cells** + +A Base RNC may control the information flow for ANR reporting over Iur. The suspension and resume are initiated from Base RNC to Receiving RNC using class 2 RNSAP procedure (Information Transfer Control procedure, defined in 5.1.2). The suspension may be performed per single cell basis or the whole cells under control of Base RNC. The ANR reporting is resumed again with initiating resume procedure for a certain target in the message. + +![Sequence diagram showing ANR report suspension and resume between RNC1, RNC2, RNC3, and O&M.](e6df2733626a85205c1db682e6259c46_img.jpg) + +**Intra UMTS, Inter RNS, ANR report over Iur Suspend/Resume** + +``` + +sequenceDiagram + participant RNC1 as RNC1 +(Role: +- Receiving RNC) + participant RNC2 as RNC2 +(Role: +- Base RNC) + participant RNC3 as RNC3 +(Role: +- Neighbour RNC) + participant OM as O&M + + Note right of RNC2: Role Base RNC: +RNC2 decides to suspend the ANR reporting to RNC2. +RNC2 initiates suspension procedure + RNC2->>RNC1: RNSAP: ANR LOG MANAGEMENT REQ: +(Type: Suspend, +Suspension Target: RNC) + Note right of RNC2: Role Base RNC: +RNC2 Earlier decided to suspend the ANR reporting to Cell-ID a in RNC2. +RNC2 initiates resume Of the procedure + RNC2->>RNC1: RNSAP: ANR LOG MANAGEMENT REQ: +(Type: Resume, +Target: Cell a) + +``` + +The diagram illustrates the interaction for ANR report suspension and resume. It starts with RNC1 (Receiving RNC) sending an RNSAP: DIRECT INFORMATION TRANSFER, ANR report transparent message to RNC2 (Base RNC). This message contains a list of neighbour relations (NR): Cell-ID a -> Cell-ID b, Cell-ID c -> Cell-ID d, and Cell-ID e -> Cell-ID f. RNC2 then initiates a suspension procedure, sending an RNSAP: ANR LOG MANAGEMENT REQ (Type: Suspend, Suspension Target: RNC) to RNC1. Later, RNC2 initiates a resume procedure, sending an RNSAP: ANR LOG MANAGEMENT REQ (Type: Resume, Target: Cell a) to RNC1. RNC3 (Neighbour RNC) and O&M are also shown but do not have active messages in this sequence. + +Sequence diagram showing ANR report suspension and resume between RNC1, RNC2, RNC3, and O&M. + +**Figure 4.2.1.2-2 ANR Report suspension and resume** + +#### 4.2.1.3 ANR Report over Iur for IRAT cells + +On reception of an ANR report containing IRAT neighbour cells from another RNC, using the RNSAP Direct Information Transfer procedure, the Base RNC uses the globally unique cell identities and L1 information in the ANR report, and optionally also configuration in the RNC/O&M, to determine if any of these IRAT neighbour cells are potential neighbour cells. The RNC retrieves the necessary information about these potential neighbour IRAT cells from configuration in the RNC/O&M. In addition the Base RNC may interact with O&M before a neighbour relation is stored in the NRT as shown in the figure below: + +![Sequence diagram showing the interaction between RNC1 (Base RNC), RNC2 (Receiving RNC), and O&M for an ANR report over Iur. The process involves RNC1 sending an RNSAP message to RNC2, RNC1 retrieving potential neighbors, RNC2 performing neighbor handling, and finally storing IRAT neighbor cells in the NRT after interaction with O&M.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +**Inter RAT – ANR report received over Iur** + +``` + +sequenceDiagram + participant RNC1 as RNC1 +(Role: +- Base RNC) + participant RNC2 as RNC2 +(Role: +- Receiving RNC) + participant OM as O&M + + Note left of RNC1: RNC1 retrieves its potential neighbours: +- Cell-ID a -> Cell-ID b (GERAN) +- Cell-ID c -> Cell-ID d (LTE) + RNC1->>RNC2: RNSAP: DIRECT INFORMATION TRANSFER, +ANR report transparent: +(list NR: +- Cell-ID a (RNC1) -> Cell-ID b (GERAN), +- Cell-ID c (RNC1)->Cell-ID d (LTE),...) + Note right of RNC2: Neighbour handling: RNC1/Cell-ID a -> Cell-ID b (GERAN), +RNC1/Cell-ID c -> Cell-ID d (LTE) +[implementation dependent] + RNC2->>OM: + Note left of RNC1: Store IRAT neighbour cells in NRT after +interaction with O&M. Store cell configuration +parameters and address to controlling node (BSC +or eNB), retrieved from configuration and/or O&M. + +``` + +Sequence diagram showing the interaction between RNC1 (Base RNC), RNC2 (Receiving RNC), and O&M for an ANR report over Iur. The process involves RNC1 sending an RNSAP message to RNC2, RNC1 retrieving potential neighbors, RNC2 performing neighbor handling, and finally storing IRAT neighbor cells in the NRT after interaction with O&M. + +**Figure 4.2.1.3-1 ANR Report over Iur for IRAT cells** + +***[The working assumption is that ANR report reports are forwarded in current RNSAP IE "L3 Information".]*** + +### 4.2.2 Iur Connectivity does not exist between some RNCs involved in ANR + +This chapter describes the handling in the Receiving RNC when the ANR function can not rely on Iur connectivity between the involved RNCs. + +#### 4.2.2.1 ANR report over Uu for UTRAN cells + +When receiving an ANR report over Uu the Receiving RNC uses the globally unique cell identities in the report to determine the network address of the Base RNCs that are controlling the Base UTRAN cells. The network address of this Base RNC is retrieved using configuration in the Receiving RNC and/or O&M. If any Base RNC involved in the logged neighbour relations in the ANR report is another RNC than the Receiving RNC, and no Iur connectivity exists to this RNC, the Receiving RNC may report the neighbour relation to O&M. + +On reception of an ANR report over Uu the Receiving RNC uses the globally unique cell identities and L1 information in the ANR report, and optionally also configuration in the RNC/O&M, to determine if the ANR report contains potential neighbours to the cells controlled by the Receiving RNC. If any of these potential neighbour cells is controlled by another RNC without Iur connectivity, the configuration in the RNC/O&M may be used to determine the necessary cell information. In addition the Base RNC may interact with O&M before a neighbour relation is stored in the NRT. + +##### Example: Utran network without Iur connectivity between some of the RNCs + +![Diagram of a UTRAN network without Iur connectivity between some RNCs. At the top, a 'Core Network' box is connected to four RNCs (RNC1, RNC2, RNC3, RNC4) via 'Iu' interfaces. RNC1 (RNSa) is a Receiving RNC and Base RNC. RNC2 (RNSb) is a Neighbour RNC. RNC3 (RNSc) is a Neighbour RNC. RNC4 (RNSd) is a Base RNC. Dashed arrows represent neighbour relations in an ANR report: 1 (RNC1) to 2 (RNC3), 3 (RNC1) to 4 (RNC2), and 5 (RNC4) to 6 (RNC3). A legend indicates that dashed arrows represent 'Example neighbour relations in the ANR report' and circles with 'n' represent 'Cells in the example'.](1439cb942d9e363bbb3161b5540dd8c6_img.jpg) + +Diagram of a UTRAN network without Iur connectivity between some RNCs. At the top, a 'Core Network' box is connected to four RNCs (RNC1, RNC2, RNC3, RNC4) via 'Iu' interfaces. RNC1 (RNSa) is a Receiving RNC and Base RNC. RNC2 (RNSb) is a Neighbour RNC. RNC3 (RNSc) is a Neighbour RNC. RNC4 (RNSd) is a Base RNC. Dashed arrows represent neighbour relations in an ANR report: 1 (RNC1) to 2 (RNC3), 3 (RNC1) to 4 (RNC2), and 5 (RNC4) to 6 (RNC3). A legend indicates that dashed arrows represent 'Example neighbour relations in the ANR report' and circles with 'n' represent 'Cells in the example'. + +**Figure 4.2.2.1-1 Example: UTRAN network without Iur between some of the RNCs** + +Example of the handling in a receiving RNC (RNC1) when there is no Iur connectivity to some of the RNCs included in the ANR report. + +The RNC1 receives an ANR report over Uu: + +- UE ANR Report sent to RNC 1: + - B.C1(RNC1) -> N.C2(RNC3) + - B.C3(RNC1) -> N.C4(RNC2) + - B.C5(RNC4) -> N.C6(RNC3) + +In the role of a receiving RNC, the RNC 1 uses the RRC Cell-ID in the ANR report to retrieve the addresses of the CRNCs involved in neighbour relations of the ANR report as Base RNC (from configuration and/or O&M). RNC 1 reports the entry B.C5(RNC4) -> N.C6(RNC3) to O&M1 as there are no Iur connectivity between RNC 1 and RNC 4. + +RNC 1 identifies the neighbour relations in which RNC1 is involved: B.C1(RNC1) -> N.C2(RNC3), B.C3(RNC1) -> N.C4(RNC2). For B.C3(RNC1) -> N.C4(RNC2) the actions in 4.2.1.1 are performed. For B.C1(RNC1) -> N.C2(RNC3) the cell N.C2(RNC3) is configured as an external cell in RNC11 and the necessary cell information is already known to RNC1, hence after O&M interaction the neighbour relation B.C1(RNC1) -> N.C2(RNC3) is stored in the NRT. + +### 4.2.3 ANR Report over Uu for IRAT cells - with and without Iur + +When receiving an ANR report over Uu where neighbour cell(s) are in another RAT, the Receiving RNC performs the forwarding of the report to Base RNCs over Iur as described in chapter 4.2.1.1 or, in case of no Iur connectivity between Receiving RNC and Base RNC, handles the IRAT neighbour relation as described in 4.2.2.1. Reception over Iur of an ANR report containing IRAT neighbour cells are described in 4.2.1.3. + +1 These operations in RNC 1 is an implementational options used in this example. + +When an RNC receives an ANR report over Uu containing IRAT neighbour cells, and if the Receiving RNC is also the Base RNC, it retrieves the necessary information for neighbour IRAT cells from O&M and/or the information of the ANR logs and determines if any of these IRAT neighbour cells are potential neighbour cells. In addition the Base RNC may interact with O&M before the neighbour relation is stored in the NRT. + +#### Inter RAT – ANR report received from UE - Base RNC is the same as the Receiving RNC + +![Sequence diagram showing the interaction between UE, RNC1, and O&M for an ANR report over Uu for IRAT cells. The process involves an ANR report request from RNC1 to UE, a UE ANR Report from UE to RNC1, RNC1 retrieving potential neighbours, RNC1 sending neighbour handling information to O&M, and finally storing IRAT neighbour cells in NRT.](410562339ce067fdc6fa41940c118658_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RNC1 + participant O&M + Note left of RNC1: Inter RAT – ANR report received from UE - Base RNC is the same as the Receiving RNC + RNC1->>UE: ANR report request + UE-->>RNC1: UE ANR Report + Note right of UE: - Cell-ID a (RNC1) -> Cell-ID b (GERAN), -> +- Cell-ID c (RNC1)->Cell-ID d (LTE),... + Note right of RNC1: RNC1 retrieves its potential neighbours: +- Cell-ID a -> Cell-ID b (GERAN) +- Cell-ID c -> Cell-ID d (LTE) + RNC1->>O&M: Neighbour handling: RNC1/Cell-ID a -> Cell-ID b (GERAN), +RNC1/Cell-ID c -> Cell-ID d (LTE) +[implementation dependent] + Note right of RNC1: Store IRAT neighbour cells in NRT after interaction with +O&M. Store cell configuration parameters and address +to controlling node (BSC or eNB), retrieved from +configuration and/or O&M. + +``` + +Sequence diagram showing the interaction between UE, RNC1, and O&M for an ANR report over Uu for IRAT cells. The process involves an ANR report request from RNC1 to UE, a UE ANR Report from UE to RNC1, RNC1 retrieving potential neighbours, RNC1 sending neighbour handling information to O&M, and finally storing IRAT neighbour cells in NRT. + +Figure 4.2.3-1 ANR Report over Uu for IRAT cells + +# 5 Functions and Procedures + +The ANR for UTRAN supports the following functions: + +- ANR Management +- Neighbour cell configuration + - Neighbour cell configuration for Intra-RNS cells + - Neighbour cell configuration for Inter-RNS cells (with Iur) + - Neighbour cell configuration (without Iur) +- ANR Logging configuration + - Configuration parameters + - Configuration validity +- Measurement Collection +- Measurement Reporting +- UE Capabilities + +## 5.1 ANR Management + +The ANR Management function provides means for an RNC, which receives an ANR report over the Uu interface, to distribute the report to other RNCs involved in the neighbour relations contained in the report as Base RNCs. The function also enables RNC for suspending and resuming ANR report over Iur. + +### 5.1.1 ANR Report Forwarding + +The ANR Report Forwarding uses RNSAP Direct Information Transfer procedure for sending of the ANR Report received over the Uu interface to the involved Base RNCs. + +![Sequence diagram for ANR Report Forwarding showing UE, Receiving RNC, and Base RNC interactions.](16c1175b5f05a4b55e6d396fc51b15b3_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Receiving RNC + participant Base RNC + Note left of Receiving RNC: Measurement reporting + Receiving RNC->>Base RNC: RNSAP: DIRECT INFORMATION TRANSFER (ANR report) + +``` + +The diagram illustrates the ANR Report Forwarding process. It features three entities: UE (User Equipment), Receiving RNC, and Base RNC. A 'Measurement reporting' message is shown between the UE and the Receiving RNC. The Receiving RNC then sends an 'RNSAP: DIRECT INFORMATION TRANSFER (ANR report)' message to the Base RNC. + +Sequence diagram for ANR Report Forwarding showing UE, Receiving RNC, and Base RNC interactions. + +Figure 5.1.1-1 ANR Report Forwarding + +Using the RNSAP: Direct Information Transfer procedure, the RNC receiving an ANR report over Uu may forward the ANR report to RNCs involved as Base RNCs in neighbour relations of the ANR report. The ANR report received in the RRC message over Uu is transparently forwarded in the RNSAP message. The receiving RNC extracts the neighbouring ANR cell information concerning the Base RNC from the Logged ANR Report Info list contained in the ANR Report over Uu, and includes the whole RRC message in RNSAP *L3 Information* IE. + +#### **Abnormal conditions:** + +When an RNC receives an ANR report outside the defined services of the ANR Report Distribution function, or if the ANR Report Distribution from the sender of the report has been suspended as described in 5.1.2, local error handling in the receiving RNC should be invoked. + +### 5.1.2 ANR Report Distribution Controlling + +The ANR Report Distribution Controlling function uses a new RNSAP procedure, Information Transfer Control procedure, for suspending and resuming ANR log reporting over Iur. An RNC receiving ANR report over Iur suspends (or resumes) ANR Reports over Iur for particular cells or for all cells in the initiating RNC. + +![Sequence diagram for ANR Report Distribution Controlling (Suspend/Resume) showing Base RNC and Receiving RNC interactions.](2bc39576969969ffe6d3f3d5264bba75_img.jpg) + +``` + +sequenceDiagram + participant Base RNC + participant Receiving RNC + Note left of Receiving RNC: RNSAP: ANR LOG MANAGEMENT REQ +(Type: Suspend, Resume) +Object: Cell List, All Cells) + Base RNC->>Receiving RNC: RNSAP: ANR LOG MANAGEMENT REQ + +``` + +The diagram illustrates the ANR Report Distribution Controlling (Suspend/Resume) process. It features two entities: Base RNC and Receiving RNC. The Base RNC sends an 'RNSAP: ANR LOG MANAGEMENT REQ' message to the Receiving RNC. The message details include 'Type: Suspend, Resume' and 'Object: Cell List, All Cells'. + +Sequence diagram for ANR Report Distribution Controlling (Suspend/Resume) showing Base RNC and Receiving RNC interactions. + +Figure 5.1.1-2 ANR Report Distribution Controlling (Suspend/Resume) + +The ANR report over Iur is resumed again using the same procedure with resume indication for any particular cells or all cells belong to initiating RNC. + +## 5.2 Neighbour Cell Configuration + +The Neighbour Cell Configuration function supports configuration of new neighbour cell relations between: + +- cells controlled by the same RNC +- cells controlled by different RNCs +- UTRAN cells and cells controlled by LTE or GERAN + +For the case of inter RNS and inter RAT neighbour cells, the neighbour cell may also be configured in the Base RNC. Such cell is called external cell in this chapter. + +### 5.2.1 Neighbour Cell Configuration for Intra-RNS cells + +At the reception of the ANR report over Uu interface, or at the reception of RNSAP: DIRECT INFORMATION TRANSFER message that contains an ANR report, the CRNC may configure new neighbour cell relations between the cells it controls. + +### 5.2.2 Neighbour Cell Configuration for Inter-RNS cells (with Iur) + +For configuration of neighbour cell relations and external cells when the Base UTRAN Cell and the Neighbour Cell are in different RNS, the Base RNC may use Iur to fetch the necessary cell information of the neighbour cell from neighbour RNC. The Neighbour Cell Configuration function uses RNSAP: Information Exchange Initiation procedure to fetch this cell information of the potential neighbour cell from the neighbour RNC. + +![Sequence diagram showing Neighbour Cell Configuration using Iur. It involves a Base RNC and a Neighbour RNC. The process starts with the reception of an ANR report (over Uu or Iur) by the Base RNC. The Base RNC then sends an RNSAP: INFORMATION EXCHANGE INITIATION REQUEST (on demand, type: neighbour cell) to the Neighbour RNC. The Neighbour RNC responds with an RNSAP: INFORMATION EXCHANGE INITIATION RESPONSE (neighbour cell information) back to the Base RNC.](a7c51c18111139f9aca2805114108565_img.jpg) + +``` + +sequenceDiagram + participant External + participant BaseRNC as Base RNC + participant NeighbourRNC as Neighbour RNC + Note left of BaseRNC: Reception of: +"ANR report" over Uu or +"ANR report" over Iur + BaseRNC->>NeighbourRNC: RNSAP: INFORMATION EXCHANGE INITIATION REQUEST (on demand, type: neighbour cell) + NeighbourRNC-->>BaseRNC: RNSAP: INFORMATION EXCHANGE INITIATION RESPONSE (neighbour cell information) + +``` + +Sequence diagram showing Neighbour Cell Configuration using Iur. It involves a Base RNC and a Neighbour RNC. The process starts with the reception of an ANR report (over Uu or Iur) by the Base RNC. The Base RNC then sends an RNSAP: INFORMATION EXCHANGE INITIATION REQUEST (on demand, type: neighbour cell) to the Neighbour RNC. The Neighbour RNC responds with an RNSAP: INFORMATION EXCHANGE INITIATION RESPONSE (neighbour cell information) back to the Base RNC. + +Figure 5.2.2-1 Neighbour Cell Configuration using Iur + +Base RNC requests cell information required to configure the neighbour cell relation from the CRNC of potential neighbour cells using the RNSAP Information Exchange Initiation. + +### 5.2.3 Neighbour Cell Configuration (without Iur) + +At the reception of the ANR report over Uu, or at the reception of a RNSAP: DIRECT INFORMATION TRANSFER message that contains an ANR report, the Neighbour Cell Configuration function configures inter RNS and/or inter RAT neighbour cell relations and external cells in the RNC. For the necessary cell information of the neighbour cell in neighbour RNC, neighbour BSS or neighbour eNB, the Base RNC uses local configuration and/or O&M. + +## 5.3 ANR Logging configuration + +ANR logging is configured with Logged Measurements Configuration procedure, as shown in Figure 5.3-1. + +![Diagram showing the ANR Logging configuration process. A UE (User Equipment) box is on the left and a UTRAN box is on the right. A horizontal arrow labeled 'LOGGING MEASUREMENT CONFIGURATION' points from the UTRAN box to the UE box.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +``` + +graph LR + UTRAN[UTRAN] -- "LOGGING MEASUREMENT CONFIGURATION" --> UE[UE] + +``` + +Diagram showing the ANR Logging configuration process. A UE (User Equipment) box is on the left and a UTRAN box is on the right. A horizontal arrow labeled 'LOGGING MEASUREMENT CONFIGURATION' points from the UTRAN box to the UE box. + +**Figure 5.3-1: ANR Logging configuration with Logging measurement configuration message** + +UTRAN initiates the ANR logging procedure to UE by sending ANR logging configuration in the Logging measurement configuration message as defined in TS 25.331. + +### 5.3.1 Configuration parameters + +- ANR logging threshold for Intra-RAT: + - ANR logging relative threshold. If the measured signal strength/quality of a detected cell exceeds the threshold relative to signal strength/quality in the serving cell, the UE shall treat the detected cell as candidate for one log entry in its ANR log. The detailed usage and value range of ANR logging relative threshold is defined in TS 25.304 and TS 25.331. + - ANR logging absolute threshold. If the measured signal strength/quality of a detected cell exceeds the absolute threshold, the UE shall treat the detected cell as candidate for one log entry in its ANR log. The detailed usage and value range of ANR logging absolute threshold is defined in TS 25.304 and TS 25.331. + +Note: The UTRAN provide an ANR logging absolute threshold and optionally an ANR logging relative threshold in an ANR logging configuration. + +- ANR logging duration timer. This configuration parameter defines a timer activated at the moment when UE receives ANR configuration. When the timer expires, the ANR logging is stopped, and the ANR configuration is deleted completely. The details and value range of ANR logging duration timer is defined in TS 25.331. +- ANR logging indicators for Inter-RAT. The detailed usage of ANR logging indicators for Inter-RAT are defined in TS 25.331. + +### 5.3.2 Configuration validity + +The ANR logging configuration is provided in the UTRA serving cell, and its validity is described below: + +- ANR logging configuration is: + - enabled in IDLE mode, CELL\_PCH and URA\_PCH states in UTRAN. + - enabled in Cell\_FACH state when second DRX cycle is used in UTRAN + - valid until ANR logging is disabled as specified in 5.4. +- ANR logging configuration is maintained regardless of RRC state, e.g. during multiple IDLE periods interrupted by IDLE-> Cell\_FACH or Cell\_DCH->IDLE state transitions. The configured ANR logging is enabled as described in first bullet above. +- When UE is not in IDLE mode, CELL\_PCH, URA\_PCH state or Cell\_FACH state when second DRX cycle is used and has a valid ANR logging configuration, the ANR logging duration timer is kept running. +- ANR logging configuration is maintained by the UE regardless of camping RAT. When UE changes the RAT, the ANR logging duration timer is kept running. The configured ANR logging is enabled as described in first bullet above. +- When ANR log is retrieved by UTRAN, UE deletes the ANR configuration and the logged data. + +- When UE moves to a new PLMN within its ANR-PLMN List, the ANR logging configuration is maintained. + +## 5.4 Measurement Collection + +Within a serving cell, the UE may log multiple detected cells if satisfied by the ANR logging threshold and other criteria specified in this section. The UE should ensure that, for a serving cell, the log contains only one entry per detected cell, identified with Cell Id (i.e. Cell Identity in UTRAN, CGI for LTE and GSM). + +UE collects ANR measurement results and continues ANR logging according to the ANR logging configuration, and ANR logging shall be disabled if any of the following conditions is met: + +- the maximum number of NRs are reached. +- the ANR logging duration timer expires. + +Once ANR logging is disabled, the UE stops ANR logging and stops the ANR logging duration timer and the ANR logging configuration is deleted. + +Note: The maximum number of NRs to be logged by the UE is hard coded. + +During ANR logging, UE should decide when to read the system information blocks of the target detected cell that can be logged by UE, in order to acquire the necessary ANR related information to be logged as defined in TS 25.331. The SI-reading activity in support of ANR is of best effort from UE perspective, and should not impact UE paging or mobility behaviour. + +For intra-UTRA case, the UE is allowed to perform ANR logging when camping on any cell belonging to its ANR-PLMN List, as well as to perform ANR measurement and to log any UTRA cell that it can detect. + +For logging of intra or inter -RAT neighbors, UE shall not log any neighbouring relationship entry related to CSG cell. + +For logging of inter-RAT GERAN neighbors, UE shall only log if the GERAN cell is not included in the neighbour list in SIB11/11bis/12. + +For logging of inter-RAT E-UTRAN neighbours, UE shall only log if the E-UTRAN cell is not included in the blacklist for the EUTRAN frequency in SIB19. + +When UE camps on certain GSM/GERAN or E-UTRAN cell with valid ANR logging configuration and the ANR logging duration timer is still running, and then UE reselects to a certain target UTRAN cell from the source GSM/GERAN or E-UTRAN cell, UE shall log inter-RAT cell information for the source GSM/GERAN or E-UTRAN cell. + +## 5.5 Measurement Reporting + +A UE configured to perform ANR logging indicates the availability of ANR logs, by means of a one bit indicator in RRC\_CONNECTION\_SETUP\_COMPLETE, CELL\_UPDATE, URA\_UPDATE and MEASUREMENT REPORT (only applicable in case when UE is able to make seamless transition from Cell\_PCH state to Cell\_FACH state) messages. + +The network may decide to retrieve the ANR logs based on this indicator in Cell\_DCH or Cell\_FACH states. + +In case the network will not retrieve ANR logs, UE should store non-retrieved ANR logs for 48 hours from the moment when the UE receives the logged ANR configuration. There is no requirement to store non-retrieved ANR logs beyond 48 hours. In addition, all related ANR configuration and ANR logs shall be removed by the UE at NAS detach or switch off. + +For Logged ANR, UE checks if the RPLMN is the same as one of the PLMNs in the "ANR-PLMN List" before signalling the presence of ANR logs in its memory, and UE checks if the RPLMN is the same as one of the PLMNs in the "ANR-PLMN List" before sending back the ANR logs to the network. + +When ANR logs are retrieved, the reported measurement results are deleted. + +The ANR log reporting should not prevent reporting two detected cells with the same PSC/Frequency if the Cell-Id is different for the two detected cells. + +Note: The UE information request/response procedure is used for ANR log request/reporting. The details for ANR log retrieval is defined in TS 25.331. + +## 5.6 UE Capabilities + +One UE capability indicator is used to indicate UE support of UTRA ANR, covering both Intra-RAT and Inter-RAT detected cells. The UTRAN ANR logging capability is independent of other logging capability in UE. + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|------|-----|-----------------|--------------------------------------------------------------------------------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | | New | +| 2010-10 | | | | | | TS Skeleton | 0.0.0 | +| 2011-02 | | | | | | TP As agreed in RAN3#71: R3-110965 | 0.0.1 | +| 2011-02 | | | | | | TP As agreed in RAN3#71: R3-111036 | 0.0.2 | +| 2011-03 | | | | | | Updated with TP agreed in RAN2#73: R2-111655 and editorial correction | 0.0.3 | +| 2011-03 | | | | | | Submitted to RAN#51 | 1.0.0 | +| 2011-05 | | | | | | Updated with R2-113590, R3-111485 and R3-111620 | 2.0.0 | +| 2011-06 | 52 | RP-110630 | | | | Approved at RAN#52 | 10.0.0 | +| 2011-12 | | | | | | MCC editorial corrections: Removal of empty Introduction and Symbols sections. | 10.0.1 | +| 2012-06 | 56 | RP-120761 | 0001 | 1 | | Updates of ANR Stage 2 Descriptions for EPLMN | 10.1.0 | +| 2012-06 | 56 | RP-120743 | 0003 | - | | Correction of ANR handlings upon UE detach or switch off | 10.1.0 | +| 2012-09 | 57 | RP-121131 | 0004 | | | Corrections to ANR Logging configuration | 10.2.0 | +| 2012-09 | | | | | | Update to Rel-11 version (MCC) | 11.0.0 | +| 2013-03 | 59 | RP-130236 | 0005 | 1 | | Extend 3G ANR Applicable RRC State | 11.1.0 | +| 2014-09 | | | | | | Update to Rel-12 version (MCC) | 12.0.0 | +| 2015-12 | | | | | | Update to Rel-13 version (MCC) | 13.0.0 | + +| Change history | | | | | | | | | +|----------------|---------|------|----|-----|-----|-----------------|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2017-03 | SA#75 | | | | | | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-07 | SA#80 | - | - | - | - | | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25912/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-16/25_series/25912/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a727cdf143e8df4663019a246c2bfd5b7cfbfaa1 --- /dev/null +++ b/marked/Rel-16/25_series/25912/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a85c3e61c6079ceae28c55657cfdeed0f6bb886d16c910cd65298d4a63ed655 +size 66924 diff --git a/marked/Rel-16/25_series/25912/098802c99831a6a7d445310d5e874e16_img.jpg b/marked/Rel-16/25_series/25912/098802c99831a6a7d445310d5e874e16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..580ec30d55dbcc1836ec75b30cf8707b79b0832f --- /dev/null +++ b/marked/Rel-16/25_series/25912/098802c99831a6a7d445310d5e874e16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7938cb1a0533fce24d0c43870f0b3621908637f12c7a9d92323f5ade79202cf0 +size 23850 diff --git a/marked/Rel-16/25_series/25912/18291be12b470a557e8c9f3a74e021be_img.jpg b/marked/Rel-16/25_series/25912/18291be12b470a557e8c9f3a74e021be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6251c6873bb40901a35bdc21bc03cc165ef640c7 --- /dev/null +++ b/marked/Rel-16/25_series/25912/18291be12b470a557e8c9f3a74e021be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e103ff6691bc0dc061206d5aa4dcd82c2ba32cea4d647765c46f3e8dffc51594 +size 64438 diff --git a/marked/Rel-16/25_series/25912/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-16/25_series/25912/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45c6dadd79d580c2666803ca02b59fbf683789d6 --- /dev/null +++ b/marked/Rel-16/25_series/25912/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f4925457103d2d201608b43c1322c8a40aa94db18327dea908aa3d43cfcee91 +size 39113 diff --git a/marked/Rel-16/25_series/25912/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-16/25_series/25912/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99970b243b986a3d7a52fb7cd1da3e065511ef1d --- /dev/null +++ b/marked/Rel-16/25_series/25912/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34771939e3bd06aed782bb4027bc490d7b075c643504a6cc1cd701972a4bba9f +size 30022 diff --git a/marked/Rel-16/25_series/25912/410562339ce067fdc6fa41940c118658_img.jpg b/marked/Rel-16/25_series/25912/410562339ce067fdc6fa41940c118658_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d2a65796e6202f97d60d70745263f039a5b0f59 --- /dev/null +++ b/marked/Rel-16/25_series/25912/410562339ce067fdc6fa41940c118658_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2fd6e10656f8327cd88a9bc742ecd604fd2694c2938836e618d32599b1ae372c +size 39987 diff --git a/marked/Rel-16/25_series/25912/41a438d7e4adc17c3a4005e7c9500091_img.jpg b/marked/Rel-16/25_series/25912/41a438d7e4adc17c3a4005e7c9500091_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0eb8fd5e92c6cde13dc4cffee38260972eec6315 --- /dev/null +++ b/marked/Rel-16/25_series/25912/41a438d7e4adc17c3a4005e7c9500091_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa9fb20c554bd530791e60b59b6bf6103bcbef9fdb76f18bdc33270990fa4f6f +size 48410 diff --git a/marked/Rel-16/25_series/25912/48f209b7c0c1f91af40cfc3466dbd534_img.jpg b/marked/Rel-16/25_series/25912/48f209b7c0c1f91af40cfc3466dbd534_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc589b0f2f8653f2fa292a7279f4c319f20c3628 --- /dev/null +++ b/marked/Rel-16/25_series/25912/48f209b7c0c1f91af40cfc3466dbd534_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f42d423414b7268885149d9e04b1eb9ed4371526a5c5383e6036a4b6df8735c +size 40000 diff --git a/marked/Rel-16/25_series/25912/50214d232017279410e9c9db8eb75119_img.jpg b/marked/Rel-16/25_series/25912/50214d232017279410e9c9db8eb75119_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f1740f1878f91b8534b4a52d5f0a505319b1ee3 --- /dev/null +++ b/marked/Rel-16/25_series/25912/50214d232017279410e9c9db8eb75119_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a7ce95d1e41fd12bfdcc5a0f1c13e68eb68084d91f465668a39bd7313c43b07 +size 76637 diff --git a/marked/Rel-16/25_series/25912/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/25_series/25912/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7540a741b2f10a988b5a2134d150f2ce896762d5 --- /dev/null +++ b/marked/Rel-16/25_series/25912/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8932f8133c23ddf3627f3912c6813a80c2b55fb52b6cd820b0604f0fcec8d14e +size 75998 diff --git a/marked/Rel-16/25_series/25912/6ca05954842b17f14dfd52f26b9d43d2_img.jpg b/marked/Rel-16/25_series/25912/6ca05954842b17f14dfd52f26b9d43d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35ce4835cff10cf513752ed368e0383f74fe2cf3 --- /dev/null +++ b/marked/Rel-16/25_series/25912/6ca05954842b17f14dfd52f26b9d43d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79d2f9d9e394b9586006aac038853d697869252311c2d77c97fac7679b34389b +size 61947 diff --git a/marked/Rel-16/25_series/25912/853f59c89931a666c07903b31d098277_img.jpg b/marked/Rel-16/25_series/25912/853f59c89931a666c07903b31d098277_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb22cd449b0244245890b1d531872e4f3f2d3ce9 --- /dev/null +++ b/marked/Rel-16/25_series/25912/853f59c89931a666c07903b31d098277_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:134534516efd72624627149fd84d8a949025232c8144090d5398a64ffef7f2e8 +size 29014 diff --git a/marked/Rel-16/25_series/25912/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/25_series/25912/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c06037663800b1c87f38307e4569a6f0d8049de --- /dev/null +++ b/marked/Rel-16/25_series/25912/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:218db66d5cc2064080f857c5e011dcd41fff939a922245a4984c5d9f14e772b7 +size 31698 diff --git a/marked/Rel-16/25_series/25912/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/25_series/25912/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db2818296a15e8ae50d04e4bc0688c3484df2d8a --- /dev/null +++ b/marked/Rel-16/25_series/25912/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8f18f801792c8a6a05b3fb56e1497656786e7b8f23fe1baab67cc9710290f7f +size 27627 diff --git a/marked/Rel-16/25_series/25912/9e4f582a5d5f6742d1372956db0f8f0b_img.jpg b/marked/Rel-16/25_series/25912/9e4f582a5d5f6742d1372956db0f8f0b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18578fc45771c2befb6eecace1568cd42aac1fc8 --- /dev/null +++ b/marked/Rel-16/25_series/25912/9e4f582a5d5f6742d1372956db0f8f0b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69040796adbb9445e6c4cef8bf09b4fb22de36047247bb11823655e3fc431a5f +size 92741 diff --git a/marked/Rel-16/25_series/25912/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/25_series/25912/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bdf417dbd95ad14664dd0a5888adc4ca4a399b27 --- /dev/null +++ b/marked/Rel-16/25_series/25912/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ff1e8bceb2034bba53bc643275cae55685ebdaae3878ae8106e1368e4965a0d +size 52857 diff --git a/marked/Rel-16/25_series/25912/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-16/25_series/25912/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ba1d4abd3a5505a0484e1072860f0f3520061b5 --- /dev/null +++ b/marked/Rel-16/25_series/25912/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:528d0f40402d44151094ec74bc9be6276f4ad2dc5ff803aeb47af383f6c1adca +size 86388 diff --git a/marked/Rel-16/25_series/25912/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/25_series/25912/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7433f4dae700828c2eaa356c87a7e03c7fdcb0e3 --- /dev/null +++ b/marked/Rel-16/25_series/25912/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:510d58f2613616283add77d1442acc6aba8593992e9b776e9dcbc00389b306f7 +size 81997 diff --git a/marked/Rel-16/25_series/25912/raw.md b/marked/Rel-16/25_series/25912/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5daf80f57fbfa7baf9a3d777188578570dd5cd80 --- /dev/null +++ b/marked/Rel-16/25_series/25912/raw.md @@ -0,0 +1,2434 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions, symbols and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 8 | +| 4 Introduction..... | 9 | +| 5 Deployment scenario..... | 10 | +| 6 Radio interface protocol architecture for evolved UTRA..... | 10 | +| 6.1 User plane..... | 12 | +| 6.2 Control plane..... | 12 | +| 7 Physical layer for evolved UTRA..... | 13 | +| 7.1 Downlink transmission scheme..... | 13 | +| 7.1.1 Basic transmission scheme based on OFDMA ..... | 13 | +| 7.1.1.1 Basic parameters ..... | 13 | +| 7.1.1.1.1 Modulation scheme ..... | 14 | +| 7.1.1.2 Multiplexing including reference-signal structure..... | 14 | +| 7.1.1.2.1 Downlink data multiplexing..... | 14 | +| 7.1.1.2.2 Downlink reference-signal structure ..... | 14 | +| 7.1.1.2.3 Downlink L1/L2 Control Signaling ..... | 14 | +| 7.1.1.3 MIMO and transmit diversity ..... | 15 | +| 7.1.1.4 MBMS ..... | 15 | +| 7.1.2 Physical layer procedure..... | 15 | +| 7.1.2.1 Scheduling ..... | 15 | +| 7.1.2.2 Link adaptation ..... | 16 | +| 7.1.2.3 HARQ ..... | 16 | +| 7.1.2.4 Cell search..... | 16 | +| 7.1.2.5 Inter-cell interference mitigation ..... | 17 | +| 7.1.3 Physical layer measurements..... | 17 | +| 7.1.3.1 UE measurements ..... | 17 | +| 7.1.3.1.1 Measurements for Scheduling..... | 17 | +| 7.1.3.1.1.1 Channel Quality Measurements ..... | 17 | +| 7.1.3.1.1.2 Measurements for Interference Coordination/Management..... | 18 | +| 7.1.3.1.2 Measurements for Mobility ..... | 18 | +| 7.1.3.1.2.1 Intra-frequency neighbour measurements ..... | 18 | +| 7.1.3.1.2.2 Inter-frequency neighbour measurements ..... | 18 | +| 7.1.3.1.2.3 Inter RAT measurements..... | 18 | +| 7.1.3.1.2.4 Measurement gap control ..... | 18 | +| 7.2 Uplink transmission scheme..... | 18 | +| 7.2.1 Basic transmission scheme ..... | 18 | +| 7.2.1.1 Modulation scheme..... | 19 | +| 7.2.1.2 Multiplexing including reference signal structure ..... | 19 | +| 7.2.1.2.1 Uplink data multiplexing..... | 19 | +| 7.2.1.2.2 Uplink reference-signal structure ..... | 20 | +| 7.2.1.2.3 Multiplexing of L1/L2 control signaling..... | 20 | +| 7.2.1.2.4 Uplink L1/L2 Control Signalling ..... | 20 | +| 7.2.1.3 MIMO ..... | 21 | +| 7.2.1.4 Power De-rating Reduction ..... | 21 | +| 7.2.2 Physical channel procedure ..... | 21 | +| 7.2.2.1 Random access procedure..... | 21 | +| 7.2.2.1.1 Non-synchronized random access..... | 21 | +| 7.2.2.1.1.1 Power control for non-synchronized random access..... | 21 | +| 7.2.2.1.2 Synchronized random access ..... | 21 | + +| | | | +|-----------|------------------------------------------------------------------------------|----| +| 7.2.2.2 | Scheduling ..... | 21 | +| 7.2.2.3 | Link adaptation ..... | 22 | +| 7.2.2.4 | Power control ..... | 22 | +| 7.2.2.5 | HARQ ..... | 22 | +| 7.2.2.6 | Uplink timing control ..... | 22 | +| 7.2.2.7 | Inter-cell interference mitigation ..... | 22 | +| 8 | Layer 2 and RRC evolution for evolved UTRA ..... | 23 | +| 8.1 | MAC sublayer ..... | 24 | +| 8.1.1 | Services and functions ..... | 24 | +| 8.1.2 | Logical channels ..... | 24 | +| 8.1.2.1 | Control channels ..... | 25 | +| 8.1.2.2 | Traffic channels ..... | 25 | +| 8.1.3 | Mapping between logical channels and transport channels ..... | 25 | +| 8.1.3.1 | Mapping in Uplink ..... | 26 | +| 8.1.3.2 | Mapping in downlink ..... | 26 | +| 8.2 | RLC sublayer ..... | 26 | +| 8.3 | PDCP sublayer ..... | 27 | +| 8.4 | RRC ..... | 27 | +| 8.4.1 | Services and functions ..... | 27 | +| 8.4.2 | RRC protocol states & state transitions ..... | 28 | +| 9 | Architecture for evolved UTRAN ..... | 29 | +| 9.1 | Evolved UTRAN architecture ..... | 29 | +| 9.2 | Functional split ..... | 29 | +| 9.3 | Interfaces ..... | 30 | +| 9.3.1 | S1 interface ..... | 30 | +| 9.3.1.1 | Definition ..... | 30 | +| 9.3.1.2 | S1-C RNL protocol functions ..... | 30 | +| 9.3.1.3 | S1-U RNL protocol functions ..... | 30 | +| 9.3.1.4 | S1-X2 similarities ..... | 30 | +| 9.3.2 | X2 interface ..... | 30 | +| 9.3.2.1 | Definition ..... | 30 | +| 9.3.2.2 | X2-C RNL Protocol Functions ..... | 31 | +| 9.3.2.3 | X2-U RNL Protocol Functions ..... | 31 | +| 9.4 | Intra-LTE-access-system mobility ..... | 31 | +| 9.4.1 | Intra-LTE-access-system mobility support for UE in LTE_IDLE ..... | 31 | +| 9.4.2 | Intra LTE-Access-System Mobility Support for UE in LTE_ACTIVE ..... | 31 | +| 9.4.2.1 | Description of Intra-LTE-Access Mobility Support for UEs in LTE_ACTIVE ..... | 31 | +| 9.4.2.2 | Solution for Intra-LTE-Access Mobility Support for UEs in LTE_ACTIVE ..... | 31 | +| 9.4.2.2.1 | C-plane handling: ..... | 31 | +| 9.4.2.2.2 | U-plane handling ..... | 33 | +| 9.5 | Inter 3GPP access system mobility ..... | 33 | +| 9.5.1 | Inter 3GPP access system mobility in Idle state ..... | 33 | +| 9.5.2 | Inter 3GPP access system mobility handover ..... | 33 | +| 9.6 | Resource establishment and QoS signalling ..... | 33 | +| 9.6.1 | QoS concept and bearer service architecture ..... | 33 | +| 9.6.2 | Resource establishment and QoS signalling ..... | 33 | +| 9.7 | Paging and C-plane establishment ..... | 35 | +| 9.8 | Evaluations on for E-UTRAN architecture and migration ..... | 35 | +| 9.9 | Support of roaming restrictions in LTE_ACTIVE ..... | 35 | +| 10 | RF related aspects of evolved UTRA ..... | 36 | +| 10.1 | Scalable bandwidth ..... | 36 | +| 10.2 | Spectrum deployment ..... | 36 | +| 11 | Radio resource management aspects of evolved UTRA ..... | 37 | +| 11.1 | Introduction ..... | 37 | +| 11.2 | Definition and description of RRM functions ..... | 37 | +| 11.2.1 | Radio Bearer Control (RBC) ..... | 37 | +| 11.2.2 | Radio Admission Control (RAC) ..... | 37 | +| 11.2.3 | Connection Mobility Control (CMC) ..... | 37 | +| 11.2.4 | Packet Scheduling (PSC) ..... | 38 | + +| | | | +|------------------------|------------------------------------------------------------------------------------------------------|----| +| 11.2.5 | Inter-cell Interference Coordination (ICIC) ..... | 38 | +| 11.2.6 | Load Balancing (LB)..... | 38 | +| 11.2.7 | Inter-RAT Radio Resource Management..... | 38 | +| 11.3 | RRM architecture in LTE..... | 38 | +| 11.4 | Support of load sharing and policy management across different Radio Access Technologies (RATs)..... | 39 | +| 12 | System and terminal complexity..... | 39 | +| 12.1 | Over all system complexity..... | 39 | +| 12.2 | Physical layer complexity ..... | 39 | +| 12.3 | UE complexity..... | 40 | +| 13 | Performance assessments..... | 41 | +| 13.1 | Peak data rate ..... | 41 | +| 13.2 | C-plane latency..... | 42 | +| 13.2.1 | FDD frame structure ..... | 43 | +| 13.2.2 | TDD frame structure type 1..... | 44 | +| 13.2.3 | TDD frame structure type 2..... | 46 | +| 13.3 | U-plane latency ..... | 46 | +| 13.3.1 | FDD frame structure..... | 47 | +| 13.3.2 | TDD frame structure type 1..... | 48 | +| 13.3.3 | TDD frame structure type 2..... | 49 | +| 13.4 | User throughput..... | 50 | +| 13.4.1 | Fulfilment of uplink user-throughput targets ..... | 50 | +| 13.4.1.1 | Initial performance evaluation ..... | 50 | +| 13.4.1.2 | UL user throughput performance evaluation ..... | 50 | +| 13.4.2 | Fulfilment of downlink user-throughput targets..... | 51 | +| 13.4.2.0 | Initial performance evaluation ..... | 51 | +| 13.4.2.1 | Fulfilment of downlink user-throughput targets by enhancement techniques..... | 51 | +| 13.4.2.1.1 | Performance Enhancement by Additional Transmit Antennas: 4 Transmit Antennas ..... | 52 | +| 13.4.2.2 | DL user throughput performance evaluation ..... | 52 | +| 13.5 | Spectrum efficiency..... | 53 | +| 13.5.1 | Fulfilment of uplink spectrum-efficiency target..... | 53 | +| 13.5.1.1 | Initial performance evaluation ..... | 53 | +| 13.5.1.2 | UL spectrum efficiency performance evaluation..... | 53 | +| 13.5.2 | Fulfilment of downlink spectrum-efficiency target..... | 54 | +| 13.5.2.0 | Initial performance evaluation ..... | 54 | +| 13.5.2.1 | Fulfilment of downlink spectrum-efficiency targets by enhancement techniques ..... | 54 | +| 13.5.2.2 | DL spectrum efficiency performance evaluation..... | 54 | +| 13.6 | Mobility..... | 55 | +| 13.6.1 | Features supporting various mobile velocities ..... | 55 | +| 13.6.2 | Assessment on U-plane interruption time during handover ..... | 56 | +| 13.6.3 | Means to minimise packet loss during handover ..... | 58 | +| 13.7 | Coverage..... | 58 | +| 13.8 | Support for point to multipoint transmission ..... | 59 | +| 13.8.1 | Initial performance evaluation..... | 60 | +| 13.8.2 | MBSFN performance evaluation..... | 60 | +| 13.9 | Network synchronisation..... | 60 | +| 13.10 | Co-existence and inter-working with 3GPP RAT ..... | 61 | +| 13.11 | General requirements ..... | 61 | +| 13.11.1 | Cost related requirements ..... | 61 | +| 13.11.2 | Service related requirements ..... | 62 | +| 13.12 | VoIP performance evaluation..... | 62 | +| 14 | Conclusions and Recommendations ..... | 62 | +| 14.1 | Conclusions ..... | 62 | +| 14.2 | Recommendations ..... | 63 | +| Annex A (informative): | Change History..... | 64 | + +# --- Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +This present document is the technical report for the study item "Evolved UTRA and UTRAN" [1]. The objective of the study item is to develop a framework for the evolution of the 3GPP radio-access technology towards a high-data-rate, low-latency and packet-optimized radio access technology. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] [3GPP TD RP-040461](#): "Proposed Study Item on Evolved UTRA and UTRAN". +- [2] [3GPP TR 25.814](#): "Physical Layer Aspects for Evolved UTRA" +- [3] [3GPP TR 23.882](#): "3GPP System Architecture Evolution: Report on Technical Options and Conclusions" +- [4] [3GPP TR 25.913](#): "Requirements for Evolved UTRA (E-UTRA) and Evolved UTRAN (E-UTRAN)" +- [5] [3GPP TR 25.813](#): "Evolved UTRA (E-UTRA) and Evolved UTRAN (E-UTRAN): Radio Interface Protocol Aspects." +- [6] [3GPP TD RP-060292](#) R3.018: "E-UTRA and E-UTRAN; Radio access architecture and interfaces." +- [7] Recommendation ITU-R SM.329-10: "Unwanted emissions in the spurious domain" +- [8] [3GPP TD R4-060660](#): "E-UTRA Radio Technology Aspects V0.1.0", NTT DoCoMo +- [9] [3GPP TD R4-051146](#): "Some operators requirements for prioritisation of performance requirements work in RAN WG4" +- [10] 3GPP TD R1-070674: "LTE physical layer framework for performance verification" +Orange, China Mobile, KPN, NTT DoCoMo, Sprint, T-Mobile, Vodafone, Telecom Italia. + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +void + +## 3.2 Symbols + +void + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|---------|-----------------------------------------------| +| ACK | Acknowledgement | +| ACLR | Adjacent Channel Leakage Ratio | +| aGW | Access Gateway | +| AM | Acknowledge Mode | +| ARQ | Automatic Repeat Request | +| AS | Access Stratum | +| BCCH | Broadcast Control Channel | +| BCH | Broadcast Channel | +| C/I | Carrier-to-Interference Power Ratio | +| CAZAC | Constant Amplitude Zero Auto-Correlation | +| CMC | Connection Mobility Control | +| CP | Cyclic Prefix | +| C-plane | Control Plane | +| CQI | Channel Quality Indicator | +| CRC | Cyclic Redundancy Check | +| DCCH | Dedicated Control Channel | +| DL | Downlink | +| DRX | Discontinuous Reception | +| DTCH | Dedicated Traffic Channel | +| DTX | Discontinuous Transmission | +| eNB | E-UTRAN NodeB | +| EPC | Evolved Packet Core | +| E-UTRA | Evolved UTRA | +| E-UTRAN | Evolved UTRAN | +| FDD | Frequency Division Duplex | +| FDM | Frequency Division Multiplexing | +| GERAN | GSM EDGE Radio Access Network | +| GNSS | Global Navigation Satellite System | +| GSM | Global System for Mobile communication | +| HARQ | Hybrid ARQ | +| HO | Handover | +| HSDPA | High Speed Downlink Packet Access | +| ICIC | Inter-Cell Interference Coordination | +| IP | Internet Protocol | +| LB | Load Balancing | +| LCR | Low Chip Rate | +| LTE | Long Term Evolution | +| MAC | Medium Access Control | +| MBMS | Multimedia Broadcast Multicast Service | +| MCCH | Multicast Control Channel | +| MCS | Modulation and Coding Scheme | +| MIMO | Multiple Input Multiple Output | +| MME | Mobility Management Entity | +| MTCH | MBMS Traffic Channel | +| NACK | Non-Acknowledgement | +| NAS | Non-Access Stratum | +| OFDM | Orthogonal Frequency Division Multiplexing | +| OFDMA | Orthogonal Frequency Division Multiple Access | +| PA | Power Amplifier | +| PAPR | Peak-to-Average Power Ratio | +| PCCH | Paging Control Channel | +| PDCP | Packet Data Convergence Protocol | +| PDU | Packet Data Unit | +| PHY | Physical layer | +| PLMN | Public Land Mobile Network | +| PRB | Physical Resource Block | +| PSC | Packet Scheduling | + +| | | +|---------|-----------------------------------------------------| +| QAM | Quadrature Amplitude Modulation | +| QoS | Quality of Service | +| RAC | Radio Admission Control | +| RACH | Random Access Channel | +| RAT | Radio Access Technology | +| RB | Radio Bearer | +| RBC | Radio Bearer Control | +| RF | Radio Frequency | +| RLC | Radio Link Control | +| RNL | Radio Network Layer | +| ROHC | Robust Header Compression | +| RRC | Radio Resource Control | +| RRM | Radio Resource Management | +| RU | Resource Unit | +| S1 | interface between eNB and aGW | +| S1-C | S1-Control plane | +| S1-U | S1-User plane | +| SAE | System Architecture Evolution | +| SAP | Service Access Point | +| SC-FDMA | Single Carrier – Frequency Division Multiple Access | +| SCH | Synchronization Channel | +| SDMA | Spatial Division Multiple Access | +| SDU | Service Data Unit | +| SFN | Single Frequency Network | +| TA | Tracking Area | +| TB | Transport Block | +| TCP | Transmission Control Protocol | +| TDD | Time Division Duplex | +| TM | Transparent Mode | +| TNL | Transport Network Layer | +| TTI | Transmission Time Interval | +| UE | User Equipment | +| UL | Uplink | +| UM | Un-acknowledge Mode | +| UMTS | Universal Mobile Telecommunication System | +| UPE | User Plane Entity | +| U-plane | User plane | +| UTRA | Universal Terrestrial Radio Access | +| UTRAN | Universal Terrestrial Radio Access Network | +| VRB | Virtual Resource Block | +| X2 | interface between eNBs | +| X2-C | X2-Control plane | +| X2-U | X2-User plane | + +# --- 4 Introduction + +At the 3GPP TSG RAN #26 meeting, the SI description on "Evolved UTRA and UTRAN" was approved [1]. + +The justification of the study item was, that with enhancements such as HSDPA and Enhanced Uplink, the 3GPP radio-access technology will be highly competitive for several years. However, to ensure competitiveness in an even longer time frame, i.e. for the next 10 years and beyond, a long-term evolution of the 3GPP radio-access technology needs to be considered. + +Important parts of such a long-term evolution include reduced latency, higher user data rates, improved system capacity and coverage, and reduced cost for the operator. In order to achieve this, an evolution of the radio interface as well as the radio network architecture should be considered. + +Considering a desire for even higher data rates and also taking into account future additional 3G spectrum allocations the long-term 3GPP evolution should include an evolution towards support for wider transmission bandwidth than 5 MHz. At the same time, support for transmission bandwidths of 5MHz and less than 5MHz should be investigated in order to allow for more flexibility in whichever frequency bands the system may be deployed + +# 5 Deployment scenario + +A very large set of scenarios are foreseen, as stated in 25.913 [4]: + +- Standalone deployment scenario: In this scenario the operator is deploying E-UTRAN either with no previous network deployed in the area or it could be deployed in areas where there is existing UTRAN/GERAN coverage but for any reason there is no requirement for interworking with UTRAN/GERAN (e.g. standalone wireless broadband application). +- Integrating with existing UTRAN and/or GERAN deployment scenario: In this scenario it is assumed that the operator is having either a UTRAN and/or a GERAN network deployed with full or partial coverage in the same geographical area. It is assumed that the GERAN and UTRAN networks respectively can have different levels of maturity. + +In order to enable the large number of possibilities, E-UTRAN will support the following: + +- 1) shared networks, both in initial selection and in mobile-initiated (controlled by system broadcast) and network-initiated/-controlled mobility. +- 2) high-velocity and nomadic mobiles. Mobility mechanisms include a handover mechanism with short latency, short interruption and minimizing of data losses (when the user has high data activity). Hence both high mobile velocities and Conversational QoS can be supported (as elaborated in 13.6). +- 3) various cell sizes and radio environments. The radio aspects are analyzed in chapter 10, but the specified mobility mechanisms are deemed adequate to support different cell sizes (also mixed) and both planned or adhoc deployments. + +**Note: ad hoc deployment inherently does not support high user QoS classes.** + +- 4) co-operation with legacy systems as required in 25.913 chapter 8.4. In particular Handover to and from GERAN and UTRAN is supported. Handover can be triggered by combinations of radio quality and requested bearer quality. This capability enables all combinations of E-UTRAN and GERAN/UTRAN coverage, ranging from full to partial coverage, overlapping to adjacent coverage and ranging from co-siting (with re-use of equipment) to separate sites for LTE, as required in 25.913 chapter 8.3. It also enables operator control of RAT and QoS selection per user. +- 5) The requirement on efficiency is to a large extent determined by radio functions (described in chapters 9 and 10, analyzed in chapter 13). However, the designed mobility procedures are (for the intra-E-UTRAN case) potentially considerably faster than the ones in legacy systems and can thus be considered to support the requirement on efficiency (as described in detail in 13.6.2). + +E-UTRAN also supports the requirements of: + +- 6) Simplicity, due to only one type of node. +- 7) Low user data delay, due to low number of nodes in the data path + +E-UTRAN shall support IP transport networks and all data link options. E-UTRAN will use separated RNL and TNL QoS. This permits co-use of existing transport networks. + +# 6 Radio interface protocol architecture for evolved UTRA + +The E-UTRAN consists of eNBs, providing the E-UTRA U-plane (RLC/MAC/PHY) and C-plane (RRC) protocol terminations towards the UE. The eNBs interface to the aGW via the S1 [5]. + +Figure 6.1 below gives an overview of the E-UTRAN architecture where yellow-shaded boxes depict the logical nodes, white boxes depict the functional entities of the C-plane, and blue boxes depict the functional entities of the U-plane. + +![Diagram of E-UTRAN Architecture showing the protocol stacks for eNB and aGW connected via an S1 interface.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +The diagram illustrates the E-UTRAN architecture, showing the protocol stacks for the eNB (evolved NodeB) and the aGW (PDN Gateway) connected via an S1 interface. + +**eNB Protocol Stack (Left):** + +- Inter Cell RRM +- Connection Mobility Cont. +- RB Control +- Radio Admission Control +- eNB Measurement Configuration & Provision +- Dynamic Resource Allocation (Scheduler) +- RRC +- RLC +- MAC +- PHY + +**S1 Interface:** A horizontal line labeled "S1" connects the eNB to the aGW. + +**aGW Protocol Stack (Right):** + +- aGW Control Plane:** + - SAE Bearer Control + - MM Entity +- aGW User Plane:** + - PDCP + - User Plane + +**Internet:** A cloud icon labeled "internet" is connected to the aGW User Plane. + +Diagram of E-UTRAN Architecture showing the protocol stacks for eNB and aGW connected via an S1 interface. + +**Figure 6.1: E-UTRAN Architecture** + +The functions hosted by the eNB are: + +- Selection of aGW at attachment; +- Routing towards aGW at RRC activation; +- Scheduling and transmission of paging messages; +- Scheduling and transmission of BCCH information; +- Dynamic allocation of resources to UEs in both uplink and downlink; +- The configuration and provision of eNB measurements; +- Radio Bearer Control; +- Radio Admission Control; +- Connection Mobility Control in LTE\_ACTIVE state. + +The functions hosted by the aGW are: + +- Paging origination; +- LTE\_IDLE state management; + +- Ciphering of the U-plane; +- PDCP; +- SAE Bearer Control (see [3]); +- Ciphering and integrity protection of NAS signalling. + +## 6.1 User plane + +Figure 6.2 below shows the U-plane protocol stack for E-UTRAN, where: + +- RLC and MAC sublayers (terminated in eNB on the network side) perform the functions listed in clause 8, e.g.: + - Scheduling; + - ARQ; + - HARQ. +- PDCP sublayer (terminated in aGW on the network side) performs for the U-plane the functions listed in clause 8, e.g.: + - Header Compression; + - Integrity Protection (to be determined during WI phase) + - Ciphering. + +![Diagram of the U-plane protocol stack showing the layers in UE, eNB, and aGW.](853f59c89931a666c07903b31d098277_img.jpg) + +The diagram illustrates the U-plane protocol stack across three entities: UE (User Equipment), eNB (evolved NodeB), and aGW (PDN Gateway). The UE contains four stacked layers: PDCP, RLC, MAC, and PHY. The eNB contains three stacked layers: RLC, MAC, and PHY. The aGW contains one layer: PDCP. Horizontal arrows indicate the flow of data: from the UE's PDCP layer to the aGW's PDCP layer, and from the UE's RLC, MAC, and PHY layers to the eNB's corresponding RLC, MAC, and PHY layers. + +Diagram of the U-plane protocol stack showing the layers in UE, eNB, and aGW. + +Figure 6.2: U-plane protocol stack + +## 6.2 Control plane + +Figure 6.3 below shows the C-plane protocol stack for E-UTRAN. The following working assumptions apply: + +- RLC and MAC sublayers (terminated in eNB on the network side) perform the same functions as for the U-plane; +- RRC (terminated in eNB on the network side) performs the functions listed in clause 8, e.g.: + - Broadcast; + - Paging; + - RRC connection management; + - RB control; + - Mobility functions; + - UE measurement reporting and control. + +- PDCP sublayer (terminated in aGW on the network side) performs for the C-plane the functions listed in clause 8, e.g.: + - Integrity Protection; + - Ciphering. +- NAS (terminated in aGW on the network side) performs among other things: + - SAE bearer management; + - Authentication; + - Idle mode mobility handling; + - Paging origination in LTE\_IDLE; + - Security control for the signalling between aGW and UE, and for the U-plane. + +NOTE: The NAS control protocol is not covered by the scope of this TR and is only mentioned for information. + +![Figure 6.3: C-plane protocol stack diagram showing the protocol layers for UE, eNB, and aGW. The UE and eNB have identical stacks: NAS, PDCP, RRC, RLC, MAC, and PHY. The aGW has NAS and PDCP layers. Arrows indicate the flow of data and control signals between the layers across the three entities.](410562339ce067fdc6fa41940c118658_img.jpg) + +The diagram illustrates the C-plane protocol stack for three entities: UE (User Equipment), eNB (evolved NodeB), and aGW (PDN Gateway). The UE and eNB share a common protocol stack consisting of six layers: NAS (Non-Access Stratum), PDCP (Packet Data Convergence Protocol), RRC (Radio Resource Control), RLC (Radio Link Control), MAC (Medium Access Control), and PHY (Physical layer). The aGW contains only the NAS and PDCP layers. Arrows indicate the flow of data and control signals: NAS messages are exchanged between the UE and the aGW; PDCP messages are exchanged between the UE and the aGW; RRC messages are exchanged between the UE and the eNB; RLC, MAC, and PHY messages are exchanged between the UE and the eNB. + +Figure 6.3: C-plane protocol stack diagram showing the protocol layers for UE, eNB, and aGW. The UE and eNB have identical stacks: NAS, PDCP, RRC, RLC, MAC, and PHY. The aGW has NAS and PDCP layers. Arrows indicate the flow of data and control signals between the layers across the three entities. + +Figure 6.3: C-plane protocol stack + +# 7 Physical layer for evolved UTRA + +Supported bandwidths are 1.25MHz, 1.6MHz, 2.5MHz, 5MHz, 10MHz, 15MHz, and 20MHz. + +Note: 1.6 MHz has been introduced with spectrum compatibility with LCR-TDD in mind. + +## 7.1 Downlink transmission scheme + +For both FDD and TDD, the downlink transmission scheme is based on OFDMA. Each 10 ms radio frame is divided into 10 equally sized sub-frames. In addition, for coexistence with LCR-TDD, a frame structure according to [2], clause 6.2.1.1.1, is also supported when operating E-UTRA in TDD mode. Channel-dependent scheduling and link adaptation can operate on a sub-frame level. + +### 7.1.1 Basic transmission scheme based on OFDMA + +#### 7.1.1.1 Basic parameters + +The downlink transmission scheme is based on conventional OFDM using a cyclic prefix. Information about the basic downlink parameters for operation in both paired and unpaired spectrum are given in [2] clause 7.1.1. For operation in unpaired spectrum with these parameters (generic frame structure), idle symbols are included at DL/UL switching points and the idle period, required in the Node B at UL/DL switching points, is created by timing advance means. Note that, for operation in unpaired spectrum there is also an additional numerology, compatible with LCR-TDD, see [2]. + +The sub-carrier spacing is constant regardless of the transmission bandwidth. To allow for operation in differently sized spectrum allocations, the transmission bandwidth is instead varied by varying the number of OFDM sub-carriers. + +##### 7.1.1.1.1 Modulation scheme + +Supported downlink data-modulation schemes are QPSK, 16QAM, and 64QAM. + +#### 7.1.1.2 Multiplexing including reference-signal structure + +##### 7.1.1.2.1 Downlink data multiplexing + +The channel-coded, interleaved, and data-modulated information [Layer 3 information] is mapped onto OFDM time/frequency symbols. The OFDM symbols are organized into a number of *physical* resource blocks (PRB) consisting of a number of consecutive sub-carriers for a number of consecutive OFDM symbols. The granularity of the resource allocation is matched to the expected minimum payload. + +The frequency and time allocations to map information for a certain UE to resource blocks are determined by the Node B scheduler, see Clause 7.1.2.1 (time/frequency-domain channel-dependent scheduling). The channel-coding rate and the modulation scheme are also determined by the Node B scheduler and also depend on the reported CQI (time/frequency-domain link adaptation). Both block-wise transmission (localized) and transmission on non-consecutive (scattered, distributed) sub-carriers are supported. To describe this, the notion of a *virtual* resource block (VRB) is introduced. A virtual resource block has the following attributes: + +- Size, measured in terms of time-frequency resource +- Type, which can be either 'localized' or 'distributed' +- Distributed VRBs are mapped onto the PRBs in a distributed manner. Localized VRBs are mapped onto the PRBs in a localized manner. + +The multiplexing of localized and distributed transmissions within one sub-frame is accomplished by FDM. + +##### 7.1.1.2.2 Downlink reference-signal structure + +The downlink reference signal(s) can be used for at least + +- Downlink-channel-quality measurements +- Downlink channel estimation for coherent demodulation/detection at the UE +- Cell search and initial acquisition + +The basic downlink reference-signal structure consists of known *reference symbols* transmitted in known positions within the OFDM time/frequency grid. Reference symbols (a.k.a. "*First reference symbols*") are located in the first OFDM symbol of every sub-frame assigned for downlink transmission. This is valid for both FDD and TDD as well as for both long and short CP. Additional reference symbols (a.k.a. "*Second reference symbols*") are located in the third last OFDM symbol of every sub-frame assigned for downlink transmission. This is the baseline for both FDD and TDD as well as for both long and short CP. See [2] clause 7.1.1.2.2 for more details. + +Orthogonality between reference signals of different TX antennas of the same cell/beam is created by means of FDM. This implies that the reference-signal structure with different antenna-specific frequency shifts is valid for each antenna. The reference signals of different cells/beams belonging to the same Node B are orthogonal to each other. + +##### 7.1.1.2.3 Downlink L1/L2 Control Signaling + +The downlink outband control signaling consists of + +- scheduling information for downlink data transmission, +- scheduling grant for uplink transmission, and +- ACK/NAK in response to uplink transmission. + +Transmission of control signalling from these groups is mutually independent, e.g., ACK/NAK can be transmitted to a UE regardless of whether the same UE is receiving scheduling information or not. + +Downlink scheduling information is used to inform the UE how to process the downlink data transmission. + +Uplink scheduling grants are used to assign resources to UEs for uplink data transmission. + +The hybrid ARQ (HARQ) feedback in response to uplink data transmission consists of a single ACK/NAK bit per HARQ process. + +#### 7.1.1.3 MIMO and transmit diversity + +The baseline antenna configuration for MIMO and antenna diversity is two transmit antennas at the cell site and two receive antennas at the UE. The higher-order downlink MIMO and antenna diversity (four TX and two or four RX antennas) is also supported. + +Spatial division multiplexing (SDM) of multiple modulation symbol streams to a single UE using the same time-frequency (-code) resource is supported. When a MIMO channel is solely assigned to a single UE, it is known as single user (SU)-MIMO. The spatial division multiplexing of the modulation symbol streams for different UEs using the same time-frequency resource is denoted as spatial division multiple access (SDMA) or multi-user (MU)-MIMO. + +Modes of operation of multiple transmit antennas at the cell site (denoted as MIMO mode) are spatial multiplexing, beamforming, and single-stream transmit diversity mode(s). The MIMO mode is restricted by the UE capability, e.g. number of receive antennas, and is determined taking into account the slow channel variation. The MIMO mode is adapted slowly (e.g. only at the beginning of communication or every several 100 msec), in order to reduce the required control signalling (including feedback) required to support the MIMO mode adaptation. + +For control channel, only single stream using the multiple transmit antennas is supported. + +#### 7.1.1.4 MBMS + +MBMS transmissions are performed in the following two ways: + +- Multi-cell transmissions +- Single-cell transmissions + +At least in case of multi-cell transmissions, the MTCH is mapped onto the MCH. + +Tight inter-cell synchronization, in the order of substantially less than the cyclic prefix, is assumed in order for the UE to be able to combine multi-cell MBMS transmissions. + +The MBMS transmission consisting of only broadcast/MBMS related information share the same carrier with unicast traffic or can be transmitted on a separate carrier (e.g. for a mobile TV application). + +### 7.1.2 Physical layer procedure + +#### 7.1.2.1 Scheduling + +The Node B scheduler (for unicast transmission) dynamically controls which time/frequency resources are allocated to a certain user at a given time. Downlink control signaling informs UE(s) what resources and respective transmission formats have been allocated. The scheduler can instantaneously choose the best multiplexing strategy from the available methods; e.g. frequency localized or frequency distributed transmission. The flexibility in selecting resource blocks and multiplexing users (7.1.1.2) will influence the available scheduling performance. Scheduling is tightly integrated with link adaptation (7.1.2.2) and HARQ (7.1.2.3). The decision of which user transmissions to multiplex within a given sub-frame may for example be based on + +- QoS parameters and measurements, +- payloads buffered in the Node-B ready for scheduling, +- pending retransmissions, +- CQI reports from the UEs, +- UE capabilities, +- UE sleep cycles and measurement gaps/periods, +- system parameters such as bandwidth and interference level/patterns, +- etc. + +#### 7.1.2.2 Link adaptation + +Link adaptation (AMC: adaptive modulation and coding) with various modulation schemes and channel coding rates is applied to the shared data channel. The same coding and modulation is applied to all groups of resource blocks belonging to the same L2 PDU scheduled to one user within one TTI and within a single stream. This applies to both localized and distributed transmission. + +The overall coding and modulation is illustrated in Figure 7.1. + +![Flowchart of the link adaptation process. It starts with 'Transport block (L2 PDU)' at the top, followed by 'CRC attachment', 'Channel coding', 'HARQ functionality including adaptive coding rate', and 'Physical channel segmentation (resource block mapping)'. From the segmentation step, multiple arrows point down to 'Adaptive modulation (common modulation is selected)'. A dashed line with an arrow points from the text 'Number of assigned resource blocks' to the arrows between segmentation and modulation. The final output is 'To assigned resource blocks'.](41a438d7e4adc17c3a4005e7c9500091_img.jpg) + +``` + +graph TD + A[Transport block (L2 PDU)] --> B[CRC attachment] + B --> C[Channel coding] + C --> D[HARQ functionality including adaptive coding rate] + D --> E[Physical channel segmentation (resource block mapping)] + E --> F[Adaptive modulation (common modulation is selected)] + G[Number of assigned resource blocks] -.-> F + F --> H[To assigned resource blocks] + +``` + +Flowchart of the link adaptation process. It starts with 'Transport block (L2 PDU)' at the top, followed by 'CRC attachment', 'Channel coding', 'HARQ functionality including adaptive coding rate', and 'Physical channel segmentation (resource block mapping)'. From the segmentation step, multiple arrows point down to 'Adaptive modulation (common modulation is selected)'. A dashed line with an arrow points from the text 'Number of assigned resource blocks' to the arrows between segmentation and modulation. The final output is 'To assigned resource blocks'. + +**Figure 7.1: Resource block-common adaptive modulation and resource block-common channel coding rate scheme (for localized and distributed transmission modes).** + +#### 7.1.2.3 HARQ + +Downlink HARQ is based on Incremental Redundancy. Note that Chase Combining is a special case of Incremental Redundancy and is thus implicitly supported as well. + +The N-channel Stop-and-Wait protocol is used for downlink HARQ. + +#### 7.1.2.4 Cell search + +Cell search is the procedure by which a UE acquires time and frequency synchronization with a cell and detects the Cell ID of that cell. E-UTRA cell search supports a scalable overall transmission bandwidth from 1.25 to 20 MHz. + +E-UTRA cell search is based on two signals ("channels") transmitted in the downlink, the "SCH" (Synchronization Channel) and "BCH" (Broadcast Channel). + +The primary purpose of the SCH is to enable acquisition of the frequency and received timing, i.e., at least the SCH symbol timing, and frequency of the downlink signal. The UE can obtain the remaining cell/system-specific information from the BCH, SCH and also from some additional channels, such as the reference symbols. The primary purpose of the BCH is to broadcast a certain set of cell and/or system-specific information similar to the current UTRA BCH transport channel. + +Aside from the SCH symbol timing and frequency information, the UE must acquire at least the following cell-specific information. + +- The overall transmission bandwidth of the cell +- Cell ID +- Radio frame timing information when this is not directly given by the SCH timing, i.e., if the SCH is transmitted more than once every radio frame +- Information regarding the antenna configuration of the cell (number of transmitter antennas) + +- Information regarding the BCH bandwidth if multiple transmission bandwidths of the BCH are defined +- CP length information regarding the sub-frame in which the SCH and/or BCH are transmitted + +Each set of information is detected by using one or several of the SCH, reference symbols, or the BCH. + +The SCH and BCH are transmitted one or multiple times every 10-msec radio frame. + +SCH structure is based on the constant bandwidth of 1.25 MHz regardless of the overall transmission bandwidth of the cell, at least for initial cell search. + +#### 7.1.2.5 Inter-cell interference mitigation + +There are three, not mutually exclusive approaches to inter-cell interference mitigation: + +- Inter-cell-interference randomization +- Inter-cell-interference cancellation +- Inter-cell-interference co-ordination/avoidance + +In addition, the use of beam-forming antenna solutions at the base station is a general method that can also be seen as a means for downlink inter-cell-interference mitigation. The main focus during the study item has been on different schemes for interference coordination. The common theme of inter-cell-interference co-ordination/avoidance is to apply restrictions to the downlink resource management (configuration for the common channels and scheduling for the non common channels) in a coordinated way between cells. These restrictions can be in the form of restrictions to what time/frequency resources are available to the resource manager or restrictions on the transmit power that can be applied to certain time/frequency resources. It has been concluded that this is mainly a scheduler implementation issue apart from additional inter-node communication and/or additional UE measurements and reporting. + +### 7.1.3 Physical layer measurements + +#### 7.1.3.1 UE measurements + +##### 7.1.3.1.1 Measurements for Scheduling + +###### 7.1.3.1.1.1 Channel Quality Measurements + +The UE is able to measure and report to the Node B the channel quality of one resource block or a group of resource blocks, in form of a Channel quality indicator (CQI). In order to allow for efficient trade-off between UL signaling overhead and link-adaptation/scheduling performance taking varying channel-conditions and type of scheduling into account, the time granularity of the CQI reporting is adjustable in terms of sub-frame units (periodic or triggered) and set on a per UE or per UE-group basis. + +CQI feedback from UE which indicates the downlink channel quality can be used at Node B at least for the following purposes: + +- Time/frequency selective scheduling +- Selection of modulation and coding scheme +- Interference management +- Transmission power control for physical channels, e.g., physical/L2-control signaling channels. + +###### 7.1.3.1.1.2 Measurements for Interference Coordination/Management + +Channel quality measurements defined in clause 7.1.3.1.1.1 and some measurements defined in clause 7.1.3.1.2 can be used for interference coordination/management purpose. + +##### 7.1.3.1.2 Measurements for Mobility + +In order to support efficient mobility in E-UTRAN, the UEs are required to identify and measure the relevant measurement quantities of neighbour cells and the serving cell. Such measurements for mobility are needed in the following mobility functions: + +- 1) PLMN selection +- 2) Cell selection and cell reselection +- 3) Handover decision + +###### 7.1.3.1.2.1 Intra-frequency neighbour measurements + +Neighbour cell measurements performed by the UE are named intra-frequency measurements when the UE can carry out the measurements without re-tuning its receiver. + +###### 7.1.3.1.2.2 Inter-frequency neighbour measurements + +Neighbour cell measurements are considered inter-frequency measurements when the UE needs to re-tune its receiver in order to carry out the measurements. + +In case of inter-frequency measurements, the network needs to be able to provide UL/DL idle periods for the UE to perform necessary neighbour measurements. + +###### 7.1.3.1.2.3 Inter RAT measurements + +Neighbour measurements are considered inter-RAT measurements when UE needs to measure other radio access technology cells. For these kinds of measurements, the network needs to be able to provide UL/DL idle periods. + +###### 7.1.3.1.2.4 Measurement gap control + +In case the UE needs UL/DL idle periods for making neighbour measurements or inter-RAT measurements, the network needs to provide enough idle periods for the UE to perform the requested measurements. Such idle periods are created by the scheduler, i.e. compressed mode is assumed not needed. + +## 7.2 Uplink transmission scheme + +For both FDD and TDD, the basic uplink transmission scheme is based on low-PAPR single-carrier transmission (SC-FDMA) with cyclic prefix to achieve uplink inter-user orthogonality and to enable efficient frequency-domain equalization at the receiver side. Each 10 ms radio frame is divided into 20 equally sized sub-frames and scheduling can operate on a sub-frame level. In addition, for coexistence with LCR-TDD, a frame structure according to [2], clause 6.2.1.1.1, is also supported when operating E-UTRA in TDD mode. To allow for multi-user MIMO reception at the Node B, transmission of orthogonal pilot patterns from single Tx-antenna UEs is part of the baseline uplink transmission scheme. + +### 7.2.1 Basic transmission scheme + +The basic uplink transmission scheme is SC-FDMA with cyclic prefix to achieve uplink inter-user orthogonality and to enable efficient frequency-domain equalization at the receiver side, see Figure 7.2. + +![Figure 7.2: Transmitter structure for SC-FDMA. The diagram shows a block diagram of the transmitter. It starts with 'Coded symbol rate= R' and a block of 'N_TX symbols'. This is followed by a 'DFT' block labeled 'Size-N_TX'. The output of the DFT block goes to a 'Sub-carrier Mapping' block. The output of the Sub-carrier Mapping block goes to an 'IFFT' block labeled 'Size-N_FFT'. The output of the IFFT block goes to a 'CP insertion' block. The final output is shown as an arrow pointing to the right.](098802c99831a6a7d445310d5e874e16_img.jpg) + +Figure 7.2: Transmitter structure for SC-FDMA. The diagram shows a block diagram of the transmitter. It starts with 'Coded symbol rate= R' and a block of 'N\_TX symbols'. This is followed by a 'DFT' block labeled 'Size-N\_TX'. The output of the DFT block goes to a 'Sub-carrier Mapping' block. The output of the Sub-carrier Mapping block goes to an 'IFFT' block labeled 'Size-N\_FFT'. The output of the IFFT block goes to a 'CP insertion' block. The final output is shown as an arrow pointing to the right. + +**Figure 7.2: Transmitter structure for SC-FDMA.** + +The sub-carrier mapping determines which part of the spectrum that is used for transmission by inserting a suitable number of zeros at the upper and/or lower end in Figure 7.3. Between each DFT output sample $L-1$ zeros are inserted. A mapping with $L=1$ corresponds to localized transmissions, i.e., transmissions where the DFT outputs are mapped to consecutive sub-carriers. With $L>1$ , distributed transmissions result, which are considered as a complement to localized transmissions for additional frequency diversity. + +![Figure 7.3: Localized mapping (left) and distributed mapping (right).](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +The diagram illustrates two methods of mapping data from a DFT to an IFFT. On the left, 'Localized mapping' shows a block of data from the DFT being mapped to a contiguous block of subcarriers for the IFFT. The data is shown as a series of red arrows, with a bracket labeled '0' indicating the start and end of the mapped block. On the right, 'Distributed mapping' shows the data from the DFT being mapped to non-contiguous subcarriers for the IFFT. The data is shown as a series of red arrows, with brackets labeled '0' and 'L-1 zeros' indicating the gaps between the mapped subcarriers. + +Figure 7.3: Localized mapping (left) and distributed mapping (right). + +**Figure 7.3: Localized mapping (left) and distributed mapping (right).** + +Information about the basic uplink parameters for operation in both paired and unpaired spectrum are given in [2] clause 9.1.1. For operation in unpaired spectrum with these parameters (generic frame structure), idle symbols are included at DL/UL switching points and the idle period, required in the Node B at UL/DL switching points, is created by timing advance means. Note that, for operation in unpaired spectrum there is an additional numerology, compatible with LCR-TDD, see [2]. The sub-frame structure defined in [2] contains two short blocks and N long blocks. + +The minimum TTI for uplink transmission is equal to the uplink sub-frame duration. + +#### 7.2.1.1 Modulation scheme + +Information about the uplink modulation scheme for operation are given in [2] clause 9.1.1.1. + +#### 7.2.1.2 Multiplexing including reference signal structure + +##### 7.2.1.2.1 Uplink data multiplexing + +The channel-coded, interleaved, and data-modulated information [Layer 3 information] is mapped onto SC-FDMA time/frequency symbols. The overall SC-FDMA time/frequency resource symbols can be organized into a number of resource units (RU). Each RU consists of a number (M) of consecutive or non-consecutive sub-carriers during the N long blocks within one sub-frame. To support the localized and distributed transmission two types of RUs are defined as follows: + +- Localized RU (LRU), which consists of M consecutive sub-carriers during N long blocks. +- Distributed RU (DRU), which consists of M equally spaced non-consecutive sub-carriers during N long blocks. + +This results in the number of RUs depending on system bandwidth as shown in [2] clause 9.1.1.2.1. + +##### 7.2.1.2.2 Uplink reference-signal structure + +Uplink reference signals are transmitted within the two short blocks, which are time-multiplexed with long blocks. Uplink reference signals are received and used at the Node B for the following two purposes: + +- Uplink channel estimation for uplink coherent demodulation/detection +- Uplink channel-quality estimation for uplink frequency- and/or time-domain channel-dependent scheduling + +The uplink reference signals are based on CAZAC sequences. + +Multiple mutually orthogonal reference signals can be created and be allocated to: + +- A single multi-transmit-antenna UE to support e.g. uplink multi-layer transmission (MIMO) +- Different UEs within the same Node B + +The uplink reference-signal structure allows for: + +- Localized reference signals. + +- Distributed reference signals. + +##### 7.2.1.2.3 Multiplexing of L1/L2 control signaling + +There are two types of L1 and L2 control-signaling information: + +- data-associated signaling (e.g., transport format and HARQ information), which is associated with uplink data transmission, and +- data-non-associated signaling (e.g., CQI and/or ACK/NAK due to downlink transmissions, and scheduling requests for uplink transmission). + +There are three multiplexing combinations for the uplink pilot, data, and L1/L2 control signaling within a sub-frame for a single UE: + +- Multiplexing of pilot, data, and data-associated L1/L2 control signaling +- Multiplexing of pilot, data, data-associated, and data-non-associated L1/L2 control signaling +- Multiplexing of pilot and data-non-associated L1/L2 control signaling + +##### 7.2.1.2.4 Uplink L1/L2 Control Signalling + +Depending on presence or absence of uplink timing synchronization, the uplink L1/L2 control signaling can differ. + +In the case of time synchronization being present, the outband control signaling consists of + +- Data-associated control signaling +- CQI +- ACK/NAK +- Synchronous random access (scheduling request, resource request) + +Data-associated control signalling can only be transmitted together with user data. + +The CQI informs the scheduler about the current channel conditions as seen by the UE. If MIMO transmission is used, the CQI includes necessary MIMO-related feedback. + +The HARQ feedback in response to downlink data transmission consists of a single ACK/NAK bit per HARQ process. + +The synchronized random access is used by the UE to request resources for uplink data transmission. + +In the case of time synchronization not being present, the outband control signalling consists of + +- Non-synchronized random access + +#### 7.2.1.3 MIMO + +The baseline antenna configuration for uplink single-user MIMO is two transmit antennas at the UE and two receive antennas at the Cell site. If the UE has only single power amplifier and two transmit antennas, the antenna switching/selection is the only option that is supported for SU-MIMO. + +To allow for Multi-user MIMO reception at the Node B, allocation of the same time and frequency resource to two UEs, each of which transmitting on a single antenna, is supported as part of the uplink baseline configuration. + +#### 7.2.1.4 Power De-rating Reduction + +Single-carrier transmission allows for further power de-rating reduction, e.g., through the use of specific modulation, clipping, spectral filtering, etc. + +### 7.2.2 Physical channel procedure + +#### 7.2.2.1 Random access procedure + +The random access procedure is classified into two categories: + +- non-synchronized random access, and + +- synchronized random access. + +##### 7.2.2.1.1 Non-synchronized random access + +The non-synchronized random access is used when i) the UE uplink has not been time synchronized or ii) the UE uplink loses synchronization. The non-synchronized access allows the Node B to estimate, and, if needed, adjust the UE transmission timing to within a fraction of the cyclic prefix. + +The random-access procedure is based on transmission of a random-access burst. Time frequency resources for the random-access attempts are controlled by the RRM configuration. + +The non-synchronized random access preamble is used for at least UE uplink time synchronization, signature detection. + +Prior to attempting a non-synchronized random access, the UE shall synchronize to the downlink transmission. + +###### 7.2.2.1.1.1 Power control for non-synchronized random access + +The power control scheme designed assumes no intra-cell interference from data transmissions (i.e., TDM/FDM operation). + +Open loop power control is used to determine the initial transmit power level. It is possible to vary the random access burst transmit power between successive bursts using: + +- a) Power ramping with configurable step size including zero step size for both FDD and TDD case +- b) Per-burst open loop power determination for TDD case only + +##### 7.2.2.1.2 Synchronized random access + +The synchronized random access is used when the UE uplink is time synchronized by the Node B. The purpose is for the UE to request resources for uplink data transmission. One of the objectives of the synchronized random access procedure is to reduce the overall latency. + +Synchronized random access and data transmission are also time and/or frequency multiplexed. + +#### 7.2.2.2 Scheduling + +The uplink should allow for both scheduled (Node B controlled) access and contention-based access. + +In case of scheduled access the UE is dynamically allocated a certain frequency resource for a certain time (i.e. a time/frequency resource) for uplink data transmission. Downlink control signaling informs UE(s) what resources and respective transmission formats have been allocated. The decision of which user transmissions to multiplex within a given sub-frame may for example be based on + +- QoS parameters and measurements, +- payloads buffered in the UE ready for transmission, +- pending retransmissions +- uplink channel quality measurements +- UE capabilities, +- UE sleep cycles and measurement gaps/periods, +- system parameters such as bandwidth and interference level/patterns, +- etc. + +#### 7.2.2.3 Link adaptation + +Uplink link adaptation is used in order to guarantee the required minimum transmission performance of each UE such as the user data rate, packet error rate, and latency, while maximizing the system throughput. + +Three types of link adaptation are performed according to the channel conditions, the UE capability such as the maximum transmission power and maximum transmission bandwidth etc., and the required QoS such as the data rate, latency, and packet error rate etc. Three link adaptation methods are as follows. + +- Adaptive transmission bandwidth + +- Transmission power control +- Adaptive modulation and channel coding rate + +#### 7.2.2.4 Power control + +For the uplink, transmission power control, being able to compensate for at least path loss and shadowing is applied. + +#### 7.2.2.5 HARQ + +Uplink HARQ is based on Incremental Redundancy. Note that Chase Combining is a special case of Incremental Redundancy and is thus implicitly supported as well. + +The N-channel Stop-and-Wait protocol is used for uplink HARQ. + +#### 7.2.2.6 Uplink timing control + +In order to keep time alignment between uplink transmissions from multiple UEs at the receiver side, timing-control commands, commanding UEs to advance or retract the respective transmit timing, can be transmitted on the downlink. + +#### 7.2.2.7 Inter-cell interference mitigation + +The basic approaches to inter-cell interference mitigation for uplink are as follows. + +- Co-ordination/avoidance i.e. by fractional re-use of time/frequency resources +- Inter-cell-interference randomization +- Inter-cell-interference cancellation +- Power control + +In addition, the use of beam-forming antenna solutions at the base station is a general method that can also be seen as a means for uplink inter-cell-interference mitigation. + +The main focus during the study item has been on different schemes for interference coordination. The common theme of inter-cell-interference co-ordination/avoidance is to apply restrictions to the uplink resource management in a coordinated way between cells. These restrictions can be in the form of restrictions to what time/frequency resources are available to the resource manager or restrictions on the transmit power that can be applied to certain time/frequency resources. It has been concluded that this is mainly a scheduler implementation issue apart from additional inter-node communication and/or additional UE measurements and reporting. + +# --- 8 Layer 2 and RRC evolution for evolved UTRA + +Layer 2 is split into the following sublayers: Medium Access Control (MAC), Radio Link Control (RLC) and Packet Data Convergence Protocol (PDCP). Figure 8.1 and Figure 8.2 below depict the PDCP/RLC/MAC architecture for downlink and uplink respectively, where: + +- Service Access Points (SAP) for peer-to-peer communication are marked with circles at the interface between sublayers. The SAP between the physical layer and the MAC sublayer provides the transport channels. The SAPs between the MAC sublayer and the RLC sublayer provide the logical channels. The SAPs between the RLC sublayer and the PDCP sublayer provide the radio bearers. +- The multiplexing of several logical channels on the same transport channel is possible; +- In the uplink, only one transport block is generated per TTI in the non-MIMO case; + +![Diagram of Layer 2 Structure for DL in eNB and aGW showing PDCP, RLC, and MAC layers across multiple bearers and logical channels.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +The diagram illustrates the Layer 2 protocol stack for Downlink (DL) in an eNB and aGW. It shows the flow of data from SAE Bearers through various processing blocks to Transport Channels. + +- SAE Bearers:** The top level, represented by four vertical lines with yellow oval markers at the intersections with the PDCP layer. +- PDCP Layer:** Contains four processing blocks, each consisting of **ROHC** (Robust Header Compression) and **Security** (Encryption/Integrity Protection). These are grouped by a bracket on the left. +- Radio Bearers:** The level between PDCP and RLC, marked by horizontal dashed lines and yellow ovals. +- RLC Layer:** Contains four processing blocks, each consisting of **Segm.** (Segmentation) and **ARQ** (Automatic Repeat Request). These are grouped by a bracket on the left. There are ellipses between the second and third blocks. +- Logical Channels:** The level between RLC and MAC, marked by horizontal dashed lines and yellow ovals. It includes two specific channels: **BCCH** (Broadcast Control Channel) and **PCCH** (Paging Control Channel). +- Scheduling / Priority Handling:** A large horizontal block that receives data from all logical channels (four from RLC, one from BCCH, and one from PCCH). +- MAC Layer:** Contains two **Multiplexing** blocks labeled **Multiplexing UE1** and **Multiplexing UEn**. These are grouped by a bracket on the left. Each multiplexing block receives data from the Scheduling/Priority Handling block and sends it to a **HARQ** (Hybrid ARQ) block. +- Transport Channels:** The bottom level, marked by horizontal dashed lines and yellow ovals. Each HARQ block connects to a transport channel. + +Diagram of Layer 2 Structure for DL in eNB and aGW showing PDCP, RLC, and MAC layers across multiple bearers and logical channels. + +Figure 8.1: Layer 2 Structure for DL in eNB and aGW + +![Figure 8.2: Layer 2 Structure for UL in UE. The diagram illustrates the protocol stack for uplink data transfer in a User Equipment (UE). It shows the flow of data from SAE Bearers through PDCP (ROHC and Security), RLC (Segmentation and ARQ), and MAC (Scheduling/Priority Handling, Multiplexing, and HARQ) layers, finally reaching Transport Channels and the RACH.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +The diagram shows the Layer 2 structure for uplink (UL) in a User Equipment (UE). The data flows from top to bottom through several layers: + +- SAE Bearers:** The starting point for data transfer. +- PDCP (Packet Data Convergence Protocol):** Consists of two parallel paths, each containing a **ROHC** (Robust Header Compression) block followed by a **Security** block. +- Radio Bearers:** The data from the PDCP Security blocks is transferred to the RLC layer via Radio Bearers. +- RLC (Radio Link Control):** Consists of two parallel paths, each containing a **Segm. ARQ** (Segmentation and ARQ) block. There is an ellipsis (...) between the two paths, indicating additional bearers. +- Logical Channels:** The data from the RLC Segm. ARQ blocks is transferred to the MAC layer via Logical Channels. +- MAC (Medium Access Control):** The data from the Logical Channels is first processed by **Scheduling / Priority Handling**, then **Multiplexing** (represented by a trapezoid), and finally **HARQ** (Hybrid ARQ). +- Transport Channels:** The data from the HARQ block is transferred to the physical layer via Transport Channels. One specific transport channel, the **RACH** (Random Access Channel), is also shown as an input to the MAC layer. + +Figure 8.2: Layer 2 Structure for UL in UE. The diagram illustrates the protocol stack for uplink data transfer in a User Equipment (UE). It shows the flow of data from SAE Bearers through PDCP (ROHC and Security), RLC (Segmentation and ARQ), and MAC (Scheduling/Priority Handling, Multiplexing, and HARQ) layers, finally reaching Transport Channels and the RACH. + +**Figure 8.2: Layer 2 Structure for UL in UE** + +## 8.1 MAC sublayer + +This subclause provides an overview on services and functions provided by the MAC sublayer. + +### 8.1.1 Services and functions + +The main services and functions of the MAC sublayer include at least: + +- Mapping between logical channels and transport channels; +- Multiplexing/demultiplexing of RLC PDUs belonging to one or different radio bearers into/from transport blocks (TB) delivered to/from the physical layer on transport channels; +- Traffic volume measurement reporting; +- Error correction through HARQ; +- Priority handling between logical channels of one UE; +- Priority handling between UEs by means of dynamic scheduling; +- Transport format selection; + +### 8.1.2 Logical channels + +The MAC sublayer provides data transfer services on logical channels. A set of logical channel types is defined for different kinds of data transfer services as offered by MAC. Each logical channel type is defined by what type of information is transferred. + +A general classification of logical channels is into two groups: + +- Control Channels (for the transfer of C-plane information); +- Traffic Channels (for the transfer of U-plane information). + +There is one MAC entity per cell. MAC generally consists of several function blocks (transmission scheduling functions, per UE functions, MBMS functions, MAC control functions, transport block generation...). + +#### 8.1.2.1 Control channels + +Control channels are used for transfer of C-plane information only. The control channels offered by MAC are listed below. Note that the need for additional channels may be identified in the WI phase. + +- **Broadcast Control Channel (BCCH)** + +A downlink channel for broadcasting system control information. + +- **Paging Control Channel (PCCH)** + +A downlink channel that transfers paging information. This channel is used when the network does not know the location cell of the UE. + +- **Multicast Control Channel (MCCH)** + +A point-to-multipoint downlink channel used for transmitting MBMS control information from the network to the UE, for one or several MTCHs. This channel is only used by UEs that receive MBMS. + +- **Dedicated Control Channel (DCCH)** + +A point-to-point bi-directional channel that transmits dedicated control information between a UE and the network. Used by UEs having an RRC connection. + +#### 8.1.2.2 Traffic channels + +Traffic channels are used for the transfer of U-plane information only. The traffic channels offered by MAC are: + +- **Dedicated Traffic Channel (DTCH)** + +A Dedicated Traffic Channel (DTCH) is a point-to-point channel, dedicated to one UE, for the transfer of user information. A DTCH can exist in both uplink and downlink. + +- **Multicast Traffic Channel (MTCH)** + +A point-to-multipoint downlink channel for transmitting traffic data from the network to the UE. This channel is only used by UEs that receive MBMS. + +### 8.1.3 Mapping between logical channels and transport channels + +Figure 8.3 depicts the mapping between logical and transport channels. Note that the need for other mappings may be identified in the WI phase. + +![Diagram illustrating the mapping between logical channels and transport channels. The top row shows logical channels: PCCH, BCCH, DCCH, DTCH, MCCH, and MTCH. The bottom row shows transport channels: PCH, BCH, RACH, SCH, and MCH. Arrows indicate the mapping: PCCH to PCH, BCCH to BCH, DCCH to SCH, DTCH to SCH, MCCH to MCH, and MTCH to MCH. RACH is shown without a mapping arrow from a logical channel.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +The diagram illustrates the mapping between logical channels and transport channels. The top row, labeled 'Logical channels', contains PCCH, BCCH, DCCH, DTCH, MCCH, and MTCH. The bottom row, labeled 'Transport channels', contains PCH, BCH, RACH, SCH, and MCH. Arrows indicate the mapping: PCCH to PCH, BCCH to BCH, DCCH to SCH, DTCH to SCH, MCCH to MCH, and MTCH to MCH. RACH is shown without a mapping arrow from a logical channel. + +Diagram illustrating the mapping between logical channels and transport channels. The top row shows logical channels: PCCH, BCCH, DCCH, DTCH, MCCH, and MTCH. The bottom row shows transport channels: PCH, BCH, RACH, SCH, and MCH. Arrows indicate the mapping: PCCH to PCH, BCCH to BCH, DCCH to SCH, DTCH to SCH, MCCH to MCH, and MTCH to MCH. RACH is shown without a mapping arrow from a logical channel. + +**Figure 8.3: Mapping between logical channels and transport channels** + +#### 8.1.3.1 Mapping in Uplink + +In the uplink, at least the following connections between logical channels and transport channels exist: + +- DCCH can be mapped to UL- SCH; +- DTCH can be mapped to UL-SCH. + +#### 8.1.3.2 Mapping in downlink + +In the downlink, at least the following connections between logical channels and transport channels exist: + +- BCCH can be mapped to BCH; +- PCCH can be mapped to PCH; +- DCCH can be mapped to DL-SCH; +- DTCH can be mapped to DL-SCH; +- MTCH can be mapped to MCH; + +## 8.2 RLC sublayer + +The main services and functions of the RLC sublayer include at least: + +- Transfer of upper layer PDUs supporting at least AM; +- Error Correction through ARQ; +- Segmentation according to the size of the TB; +- Resegmentation (e.g. when the radio quality, i.e. the supported TB size changes); +- In-sequence delivery of upper layer PDUs; +- Duplicate Detection; +- Protocol error detection and recovery; +- Reset. + +Note that the reliability of RLC is configurable: for some bearers may tolerate rare losses (e.g. TCP traffic). + +## 8.3 PDCP sublayer + +Figure 8.4 illustrates a model of the PDCP sublayer. + +![Figure 8.4: Model of PDCP sublayer. The diagram shows the PDCP sublayer architecture, divided into User Plane and Control Plane by a vertical dashed line. The User Plane contains three SAE Bearers, each with a ROHC (Robust Header Compression) block followed by a Ciphering block. The Control Plane contains NAS Signalling, which has an Integrity Protection block followed by a Ciphering block. All blocks are connected to a common PDCP entity, represented by a large rectangle with yellow circles at the top and bottom indicating data flow points.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +Figure 8.4: Model of PDCP sublayer. The diagram shows the PDCP sublayer architecture, divided into User Plane and Control Plane by a vertical dashed line. The User Plane contains three SAE Bearers, each with a ROHC (Robust Header Compression) block followed by a Ciphering block. The Control Plane contains NAS Signalling, which has an Integrity Protection block followed by a Ciphering block. All blocks are connected to a common PDCP entity, represented by a large rectangle with yellow circles at the top and bottom indicating data flow points. + +**Figure 8.4: Model of PDCP sublayer** + +The main services and functions of the PDCP sublayer include at least: + +- Header compression and decompression: ROHC only; +- Transfer of user data: transmission of user data means that PDCP receives PDCP SDU from the NAS and forwards it to the RLC layer and vice versa; +- Ciphering of U- plane data and C-plane data (NAS Signalling); +- Integrity protection of C-plane data (NAS signalling); + +NOTE 1: The U-plane and C-plane PDCP entities are located in the UPE and MME, respectively. + +NOTE 2: When compared to UTRAN, the *lossless DL RLC PDU size change* is not required. + +## 8.4 RRC + +This subclause provides an overview on services and functions provided by the RRC sublayer. + +### 8.4.1 Services and functions + +The main services and functions of the RRC sublayer include at least: + +- Broadcast of System Information related to the non-access stratum (NAS); +- Broadcast of System Information related to the access stratum (AS); +- Paging; +- Establishment, maintenance and release of an RRC connection between the UE and E-UTRAN including: + - Allocation of temporary identifiers between UE and E-UTRAN; + - Configuration of radio resources for RRC connection. +- Security functions including: + - Integrity protection for RRC messages; +- Establishment, maintenance and release of point to point Radio Bearers including configuration of radio resources for the Radio Bearers; +- Mobility functions including: + - UE measurement reporting and control of the reporting for inter-cell and inter-RAT mobility; + +- Inter-cell handover; +- UE cell selection and reselection and control of cell selection and reselection; +- Context transfer between eNBs. +- UE measurement reporting and control of the reporting; +- NAS direct message transfer to/from NAS from/to UE. + +### 8.4.2 RRC protocol states & state transitions + +RRC uses the following states: + +- **RRC\_IDLE:** + - UE specific DRX configured by NAS; + - Broadcast of system information; + - Paging; + - Cell re-selection mobility; + - The UE shall have been allocated an id which uniquely identifies the UE in a tracking area; + - No RRC context stored in the eNB. +- **RRC\_CONNECTED:** + - UE has an E-UTRAN-RRC connection; + - UE has context in E-UTRAN; + - E-UTRAN knows the cell which the UE belongs to; + - Network can transmit and/or receive data to/from UE; + - Network controlled mobility (handover); + - Neighbour cell measurements; + - At RLC/MAC level: + - UE can transmit and/or receive data to/from network; + - UE monitors control signalling channel for shared data channel to see if any transmission over the shared data channel has been allocated to the UE; + - UE also reports channel quality information and feedback information to eNB; + - DRX/DTX period can be configured according to UE activity level for UE power saving and efficient resource utilization. This is under control of the eNB. + +# --- 9 Architecture for evolved UTRAN + +## 9.1 Evolved UTRAN architecture + +This chapter describes the definition of an evolved UTRAN Architecture in terms of logical nodes, each node hosting a set of functions and the related physical interfaces. + +The evolved UTRAN consists of eNBs, providing the evolved UTRA U-plane and C-plane protocol terminations towards the UE. The eNBs are interconnected with each other by means of the X2 interface. It is assumed that there always exist an X2 interface between the eNBs that need to communicate with each other, e.g. for support of handover of UEs in LTE\_ACTIVE. + +The eNBs are also connected by means of the S1 interface to the EPC (Evolved Packet Core). The S1 interface support a many-to-many relation between aGWs and eNBs. + +The EUTRAN architecture is illustrated in Figure 9.1. + +![Diagram of E-UTRAN architecture showing two MME/UPE units in the EPC connected to three eNB units in the E-UTRAN via S1 interfaces, with X2 interfaces between the eNBs.](6ca05954842b17f14dfd52f26b9d43d2_img.jpg) + +The diagram illustrates the E-UTRAN architecture. At the top, two blue rectangular boxes labeled 'MME/UPE' represent the Evolved Packet Core (EPC). Below them, a dashed horizontal line labeled 'S1' separates the EPC from the E-UTRAN. In the E-UTRAN, three light blue oval shapes labeled 'eNB' represent the evolved NodeBs. Blue lines connect each eNB to both MME/UPE units, representing the S1 interfaces. Red lines labeled 'X2' connect the eNBs to each other, representing the X2 interfaces. Brackets on the right side of the diagram label the top section as 'EPC' and the bottom section as 'E-UTRAN'. + +Diagram of E-UTRAN architecture showing two MME/UPE units in the EPC connected to three eNB units in the E-UTRAN via S1 interfaces, with X2 interfaces between the eNBs. + +Figure 9.1: E-UTRAN architecture + +## 9.2 Functional split + +The eNB host the following functions: + +- Functions for Radio Resource Management: Radio Bearer Control, Radio Admission Control, Connection Mobility Control, Dynamic Resource Allocation (scheduling). + +The MME hosts the following functions: + +- Distribution of paging messages to the eNBs. + +The UPE hosts the following functions: + +- IP Header Compression and encryption of user data streams; +- Termination of U-plane packets for paging reasons; +- Switching of U-plane for support of UE mobility. + +## 9.3 Interfaces + +### 9.3.1 S1 interface + +#### 9.3.1.1 Definition + +The S1 interface is the interface that separate E-UTRAN and EPC. The S1 interface consists of two parts: + +C-plane: S1-C is the interface between eNB and MME function in EPC. + +U-plane: S1-U is the interface between eNB and UPE function in EPC. + +The S1 interface shall be specified so that there is a many-to-many relation between aGWs and eNBs. + +#### 9.3.1.2 S1-C RNL protocol functions + +The S1-C interface supports at least the following functions: + +- Mobility functions: Support for intra- and inter-system mobility of UE(s). +- Connection Management Functions: Functions for handling LTE\_IDLE to LTE\_ACTIVE transitions, roaming area restrictions etc. +- SAE Bearer Management: Setup, modification and release of SAE Bearers. +- General S1 management and error handling functions: Request to release, and release of all bearers, S1 reset functions, as well as some kind of path supervision. +- Paging of a UE in the eNB. +- Transport of NAS information between EPC and UE. +- MBMS support functions. + +#### 9.3.1.3 S1-U RNL protocol functions + +The S1-U interface supports the tunnelling of end user packets between the eNB and the UPE. The tunnelling protocols support the following functions: + +- Indication of the SAE Access Bearer in the target node that the packet belongs to. +- Means to minimize packet losses due to mobility. +- Error handling mechanism +- MBMS support functions +- Packet loss detection mechanism + +#### 9.3.1.4 S1-X2 similarities + +S1-U and X2-U use the same U-plane protocol in order to minimize protocol processing for the eNB at the time of data forwarding. + +### 9.3.2 X2 interface + +#### 9.3.2.1 Definition + +The X2 interface is the interface between eNBs. The X2 interface consists of two parts: + +C-plane: X2-C is the C-plane interface between eNBs. + +U-plane: X2-U is the U-plane interface between eNBs + +#### 9.3.2.2 X2-C RNL Protocol Functions + +The X2-C interface supports the following functions: + +- Mobility functions: Support for UE mobility between eNBs, including e.g. handover signalling and control of U-plane tunnels. +- Multi-cell RRM functions: Support for multi-cell RRM, e.g. measurement reporting. +- General X2 management and error handling functions. + +#### 9.3.2.3 X2-U RNL Protocol Functions + +The X2-U interface supports the tunneling of end user packets between the eNBs. The tunneling protocols support the following functions: + +- Indication of the SAE Access Bearer in the target node that the packet belongs to. +- Means to minimize packet losses due to mobility. + +## 9.4 Intra-LTE-access-system mobility + +### 9.4.1 Intra-LTE-access-system mobility support for UE in LTE\_IDLE + +Refer to clause 7.7 in [3]. + +### 9.4.2 Intra LTE-Access-System Mobility Support for UE in LTE\_ACTIVE + +#### 9.4.2.1 Description of Intra-LTE-Access Mobility Support for UEs in LTE\_ACTIVE + +The Intra-LTE-Access Mobility Support for UEs in LTE\_ACTIVE handles all necessary steps already known from state of the art relocation/handover procedures, like processes that precedes the final HO decision on the source network side (control and evaluation of UE and eNB measurements taking into account certain UE specific area restrictions), preparation of resources on the target network side, commanding the UE to the new radio resources and finally releasing resources on the (old) source network side. It contains mechanisms to transfer context data between evolved nodes, and to update node relations on C-plane and U-plane. + +#### 9.4.2.2 Solution for Intra-LTE-Access Mobility Support for UEs in LTE\_ACTIVE + +##### 9.4.2.2.1 C-plane handling: + +The HO procedure is performed without MME/UPE involvement, i.e. preparation messages are directly exchanged between the eNBs. The release of the resources at the source side during the HO completion phase is triggered by the eNB. + +![Sequence diagram showing information flow for Intra-LTE-Access Mobility Support between UE, Source eNodeB, Target eNodeB, and MME/UPE.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Source eNodeB + participant Target eNodeB + participant MME/UPE + + Note right of Source eNodeB: 1. Provision of area restrictions + Note left of UE: 2. Measurement control + Note right of Source eNodeB: 3. HO Decision + Source eNodeB->>Target eNodeB: 4. HO Request + Note right of Target eNodeB: 5. Admission Control + Target eNodeB->>Source eNodeB: 6. HO Response + Note left of UE: 7. HO Command + Note right of Source eNodeB: 8. L1/L2 signalling + Note right of Target eNodeB: 9. HO Complete + Note right of MME/UPE: 10. HO Complete + Note right of MME/UPE: 11. HO Complete ACK + Note right of Source eNodeB: 12. Release Resource + Note left of Source eNodeB: 13. Release resources @ source side + Note right of MME/UPE: 14. UE Update Location + + Note right of Target eNodeB: A.) means to avoid data loss are provided (see §9.5.2.2.2) + +``` + +The diagram illustrates the information flow for Intra-LTE-Access Mobility Support. It involves four main entities: UE, Source eNodeB, Target eNodeB, and MME/UPE. The process starts with the Source eNodeB providing area restrictions to the MME/UPE. The Source eNodeB then configures measurement control for the UE. Based on measurement results, the Source eNodeB makes a handover (HO) decision and sends an HO Request to the Target eNodeB. The Target eNodeB performs admission control and sends an HO Response. The Source eNodeB sends an HO Command to the UE and initiates L1/L2 signalling. The Target eNodeB sends an HO Complete message to the MME/UPE, which responds with an HO Complete ACK. The Source eNodeB releases resources, and the MME/UPE updates the UE's location. A dashed box highlights steps 7 through 12, with a note indicating that these steps are designed to avoid data loss during the handover. + +Sequence diagram showing information flow for Intra-LTE-Access Mobility Support between UE, Source eNodeB, Target eNodeB, and MME/UPE. + +**Figure 9.2: Information flow for Intra-LTE-Access Mobility Support** + +- 1) The UE context within the source eNB contains information regarding roaming restrictions which where provided either at connection establishment or at the last TA update. + - 2) The source eNB entity configures the UE measurement procedures according to the area restriction information. Measurements provided by the source eNB entity may assist the function controlling the UE's connection mobility. + - 3) Based on measurement results from the UE and the source eNB, probably assisted by additional RRM specific information, the source eNB decides to handover the UE to a cell controlled by the target eNB. + - 4) The source eNB issues a HO Request to the target eNB entity passing necessary information to prepare the HO at the target side. The target eNB configures the required resources. + - 5) Admission Control is performed by the target eNB to increase the likelihood of a successful HO, if the resources can be granted by target eNB. + - 6) The HO preparation is finished at the target side, information for the UE to reconfigure the radio path towards the target side is passed to the source eNB. +- A) from step 7) until 12) means to avoid data loss during HO are provided and are detailed in §9.4.2.2.2. +- 7) The UE is commanded by the source eNB entity to perform the HO, target side radio resource information is contained. + - 8) The UE gains synchronisation at the target side. + +- 9) Once the UE has successfully accessed the cell, it sends an indication to the target eNB that the handover is completed. +- 10) The MME/UPE is informed that the UE has changed cell. The UPE switch the data path to the target side and can release any U-plane/TNL resources towards the source eNB. +- 11) The MME/UPE confirms the HO Complete message with the HO Complete ACK message. +- 12) The target eNB triggers the release of resources at the source side. The target eNB can send this message directly after reception of message 9. +- 13) Upon reception of the Release Resource message, the source eNB can release radio and C-plane related resources in relation to the UE context. The source eNB should continue to perform data forwarding until an implementation dependent mechanism decides that data forwarding can be stopped and U-plane/TNL resources can be released. +- 14) If the new cell is member of a new Tracking Area, the UE needs to register with the MME/UPE which in turn updates the area restriction information on the target side. + +##### 9.4.2.2.2 U-plane handling + +The U-plane handling during the Intra-LTE-Access mobility activity for UEs in LTE\_ACTIVE takes the following principles into account to avoid data loss during HO and hence to support seamless/lossless service provision: + +- During HO preparation a U-plane tunnel is established between the source eNB and the target eNB. +- During HO execution, user data may be forwarded from the source eNB to the target eNB. The forwarding may take place in a service dependent and implementation specific way. + - Forwarding of user data from the source to the target eNB should take place as long as packets are received at the source eNB from the UPE. +- During HO completion: + - After the MME/UPE was informed by the target eNB that the UE has gained access at the target eNB by the HO Complete message, the U-plane path is switched by the MME/UPE from the source eNB to the target eNB. + - The source eNB shall continue forwarding of U-plane data as long as packets are received at the source eNB from the UPE. + +## 9.5 Inter 3GPP access system mobility + +### 9.5.1 Inter 3GPP access system mobility in Idle state + +Refer to clause 7.5 in [3]. + +### 9.5.2 Inter 3GPP access system mobility handover + +Refer to clause 7.8.2 in [3]. + +## 9.6 Resource establishment and QoS signalling + +### 9.6.1 QoS concept and bearer service architecture + +Refer to clause 7.12.2 and 7.12.3 in [3]. + +### 9.6.2 Resource establishment and QoS signalling + +Resource establishment and QoS signaling in LTE/SAE has been accelerated by removing the signaling hierarchy in SAE bearer establishment in S1 control plane. Signalling of Access Stratum and Non Access Stratum information is done in parallel by piggybacking the NAS information in the AS signalling in S1 interface. + +![Sequence diagram showing information flow for resource establishment in the radio network for application level signalling. The diagram involves three entities: UE, eNB, and MME/UPE. The sequence of messages is: 1. Service negotiation on existing signalling relation + default IP Access established (UE to MME/UPE); 2. Request Resources (Policy/QoS Info) (MME/UPE to MME/UPE); 3. Subscription Check, Admission Control, QoS Control, ... (MME/UPE internal); 4. Prepare and reserve UP resources (MME/UPE internal); 5. AS: Request Radio Bearer (MME/UPE to eNB); 6. Admission Control for RNL resources, UE/network capabilities, etc. Admission control for radio resources at cell level, Configure Scheduler, etc. (eNB internal); 7. Radio Bearer Establishment (radio resource info, QoS info, binding) (eNB to UE); 8. AS: Ack (eNB to MME/UPE); 9. Setup tunnel endpoint (MME/UPE internal); 10. Report Resources (QoS Info) (MME/UPE to MME/UPE).](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +``` + +sequenceDiagram + participant UE + participant eNB + participant MME_UPE as MME/UPE + + Note right of MME_UPE: 1. Service negotiation on existing signalling relation + default IP Access established + Note right of MME_UPE: 2. Request Resources (Policy/QoS Info) + Note right of MME_UPE: 3. Subscription Check, Admission Control, QoS Control, ... + Note right of MME_UPE: 4. Prepare and reserve UP resources + Note right of MME_UPE: 5. AS: Request Radio Bearer + Note right of eNB: 6. Admission Control for RNL resources, UE/network capabilities, etc. +Admission control for radio resources at cell level, Configure Scheduler, etc. + Note right of eNB: 7. Radio Bearer Establishment (radio resource info, QoS info, binding) + Note right of eNB: 8. AS: Ack + Note right of MME_UPE: 9. Setup tunnel endpoint + Note right of MME_UPE: 10. Report Resources (QoS Info) + +``` + +Sequence diagram showing information flow for resource establishment in the radio network for application level signalling. The diagram involves three entities: UE, eNB, and MME/UPE. The sequence of messages is: 1. Service negotiation on existing signalling relation + default IP Access established (UE to MME/UPE); 2. Request Resources (Policy/QoS Info) (MME/UPE to MME/UPE); 3. Subscription Check, Admission Control, QoS Control, ... (MME/UPE internal); 4. Prepare and reserve UP resources (MME/UPE internal); 5. AS: Request Radio Bearer (MME/UPE to eNB); 6. Admission Control for RNL resources, UE/network capabilities, etc. Admission control for radio resources at cell level, Configure Scheduler, etc. (eNB internal); 7. Radio Bearer Establishment (radio resource info, QoS info, binding) (eNB to UE); 8. AS: Ack (eNB to MME/UPE); 9. Setup tunnel endpoint (MME/UPE internal); 10. Report Resources (QoS Info) (MME/UPE to MME/UPE). + +**Figure 9.3: Information flow for Resource Establishment in the Radio Network for application level signalling** + +- 1) The UE has a signalling relation established with the network which relies on the default IP Access service. +- 2) The MME/UPE is triggered by a resource request which contains Policy/QoS Information corresponding to the requested service. +- 3) The MME/UPE checks the UE's subscription, performs admission control. +- 4) The MME/UPE reserves a U-plane configuration (including a tunnel endpoint) in the UPE +- 5) MME/UPE sends a request to the eNB to establish a Radio Bearer (RB) +- 6) The eNB performs admission control for RNL radio resources, and maps the received QoS information for the "PHY/MAC control" entity and triggers the allocation of radio resources002E + +The "PHY/MAC control" receives the QoS information from the "RRC." + +The "PHY/MAC control" uses this information to perform admission control for radio and processing resources at cell level and to generate the relevant HARQ entities and also to perform any mapping of logical channel to resource identifier configures the scheduler according to the received QoS information and allocates resources according to the received QoS information. + +The "PHY/MAC control" returns the relevant configuration information (e.g. HARQ configuration, air interface identifiers, channel mapping etc) to the "RRC" entity. + +- 7) The RB is established and UE is provided with information about the radio configuration necessary for the service. +- 8) The MME/UPE is informed about the successful outcome of the radio bearer establishment. +- 9) UPE function in the EPC is informed about tunnel endpoint. +- 10) The MME/UPE reports the outcome of the resource establishment. + +## 9.7 Paging and C-plane establishment + +Refer to clause 7.14 in [3]. + +For C-plane establishment, several control plane procedures will be executed in parallel. Encrypted NAS messages will be carried as Direct Transfer messages in both S1 and RRC messages. + +## 9.8 Evaluations on for E-UTRAN architecture and migration + +Following requirements on E-UTRAN architecture and migration have been identified in clause 9 of TR 25.913. For each requirement it is shortly discussed how it is fulfilled by the LTE architecture. + +- a) A single E-UTRAN architecture should be agreed. + +The agreed architecture for LTE is captured in clause 9.1. + +- b) The E-UTRAN architecture shall be packet based, although provision should be made to support systems supporting real-time and conversational class traffic. + +The E-UTRAN architecture in clause 9.1 is packet based and supports all kinds of services including real-time and conversational type of services. + +- c) E-UTRAN architecture shall minimize the presence of "single points of failure" where possible without additional cost for backhaul. + +Effects of "single points of failures" are limited to eNB sites, which are defined without architectural redundancy. + +- d) E-UTRAN architecture shall simplify and minimize the introduced number of interfaces where possible + +The E-UTRAN architecture consist of eNBs with corresponding interfaces. The E-UTRAN architecture contains two interfaces: S1 which is the interface between EPC and eNB, and X2 which is the interface between eNBs. + +- e) Radio Network Layer (RNL) and Transport Network Layer (TNL) interaction should not be precluded if in the interest of improved system performance. + +Interaction between RNL and TNL has not been precluded in the proposed architecture. + +- f) E-UTRAN architecture shall support an end-to-end QoS. The TNL shall provide the appropriate QoS requested by the RNL. + +The architecture supports end-to-end QoS and enhancements/simplifications of the QoS concept of Rel. 6. + +- g) QoS mechanism(s) shall take into account the various types of traffic that exists to provide efficient bandwidth utilization: "C-plane" traffic, "U-plane" traffic, O&M traffic etc. + +The discussed QoS mechanisms allow for differentiation of different types of traffic, e.g. signalling and different kinds of user data, and supports prioritization between different kinds of traffic. + +- h) The E-UTRAN shall be designed in such a way to minimize the delay variation (jitter) for e.g. TCP/IP for packet communication. + +The radio interface protocols of the U-plane are terminated in the eNB and UPE, which allows for small delay variations. E-UTRAN architecture allows for the minimisation of data loss during UE mobility between eNBs, which is expected to minimize the impact on TCP performance. + +## 9.9 Support of roaming restrictions in LTE\_ACTIVE + +Handling of roaming/area restrictions and handling of subscription specific preferences in LTE\_ACTIVE is performed in the eNB based on information provided by the aGW over the S1 interface. + +# 10 RF related aspects of evolved UTRA + +## 10.1 Scalable bandwidth + +E-UTRA shall according to [4] allow scalable bandwidth operation of 1.25 MHz, 1.6MHz, 2.5 MHz, 5 MHz, 10 MHz, 15 MHz and 20 MHz. There are several implications of the flexible bandwidth, including performance and implementation aspects. When unwanted emissions requirements for a scalable bandwidth system are specified, there are also regulatory aspects related to both the way the unwanted emission requirements are specified and to identifying the relevant emission limits. + +For the out-of-band emissions (close to the carrier) the present UTRA limits are specified both as ACLR (Adjacent Channel Leakage Ratio) and a Spectrum Mask. Several proposals in several RAN4 documents\* discuss how to specify ACLR and spectrum mask in a way similar to UTRA. It is also shown how emissions vary with the scalable bandwidth, which should be reflected in the out-of-band limits, at least for the UE. Proposals in several RAN4 documents\* introduce a new concept where adjacent channel leakage is specified in a measurement bandwidth related to the resource block size. It is pointed out in a RAN4 document\* that Out-of-band emissions for E-UTRA does not necessarily have to be specified as a spectrum mask, or that it has to be identical to the UTRA mask. What is important is that assurance is provided for co-existence, through ACLR, spectrum mask or other limits on Out-of-band emissions. + +Out-of-band limits are set by 3GPP, but are referenced, included and applied by external regulatory bodies in recommendations, reports and co-existence studies\*. In defining the limits for LTE, those references should be considered to assure that E-UTRA provides sufficient compatibility with other services. + +The present UTRA spurious emission limits are based on ITU-R SM.329 [7], which should also be the basis for LTE as discussed in several RAN4 documents\*. There are also additional UE and BS spurious emission limits defined as regional requirements for co-existence between different systems, including UTRA, GSM and PHS in the same or different bands. Some of these requirements should remain as pointed out in several of RAN4 documents\*, but there may also be new co-existence scenarios to consider. It is important for 3GPP to respect regional requirements and to take into account how the limits are applied and referenced in international and regional bodies. + +It was shown in a RAN4 document\* that some aspects of the ITU-R SM.329 limits [7] may lead to unnecessarily tight requirements for the eNB. The regulatory aspects of this issue are at the moment being addressed further within CEPT/ECC. + +Spurious emission limits are mainly driven by international recommendations, but some implementation considerations are also important. One such issue is how to define the limit between out-of-band and spurious emissions. ITU-R SM.329 [7] recommends this limit to be proportional to the (necessary) emission bandwidth. Several RAN4 documents\* considered the concept of starting the domain of the spurious emission requirements at a fixed offset of 10 MHz from the edge of the LTE carrier for any bandwidth. From an implementation perspective a RAN4 document\* indicated this to be feasible for the eNB. However, it was shown in several RAN4 documents\* that this approach appears to be not viable for the UE. Also here, considerations must be taken of implementation and regulatory aspects as well as co-existence with adjacent systems. + +In some of the potential frequency bands, depending on the spectrum allocation conditions, sufficient frequency spectrum for the wider operation bandwidths may not be available. In that case, resource aggregation has been considered as one option. The implementation and complexity aspects of this issue are studied and summarized further in clause 12.2 in this TR. + +As a summary of these studies it can be concluded that the scalable bandwidth needs to be properly considered when defining LTE unwanted emission requirements, taking into account co-existence with other systems, implementation and regulatory aspects. Based on the studies to date, scalable bandwidth is considered feasible. + +Note: \*See clause 5.2 in [8] + +## 10.2 Spectrum deployment + +The conclusions in this chapter are preliminary and may need to be updated once the work in RAN4 progresses. Specially the comprehensive analysis of coexistence of E-UTRA operating in the same frequency band with other radio systems spans a large number of scenarios and requires a considerable amount of simulation work which is still ongoing. However, based on initial coexistence simulation results and additional analytical analysis RAN4 can draw a draft conclusion for the purpose of the Study Item. + +Regarding coexistence of E-UTRA with E-UTRA and other radio technologies operating in different frequency bands similar requirements as currently specified for UTRA are anticipated. This concerns additional transmitter and receiver + +spurious emission requirements for coexistence which will be for LTE eNB and UE the same as today for UTRA and receiver blocking requirements for coexistence which need to be specified by RAN4 during the Work Item phase. + +Regarding coexistence of E-UTRA with E-UTRA and E-UTRA with UTRA operating in the same frequency band on adjacent channels, initial coexistence simulation results for downlink have shown that this is feasible with requirements for E-UTRA similar to those for the current UTRA system. The analysis of the transmitter emissions of the E-UTRA UE indicated that behaviour is expected to be similar to the downlink however uplink coexistence simulation results are not available yet. Coexistence with GSM also needs to be analysed. Further coexistence studies for uplink and downlink are ongoing. + +Based on the studies described above, focussed on scenarios considered most critical, coexistence of E-UTRA with E-UTRA and other radio technologies is seen feasible. + +# --- 11 Radio resource management aspects of evolved UTRA + +## 11.1 Introduction + +The purpose of radio resource management (RRM) is to ensure the efficient use the available radio resources and to provide mechanisms that enable E-UTRAN to meet radio resource related requirements identified in Chapter 10 of [4]. In particular, RRM in E-UTRAN provides means to manage (e.g. assign, re-assign and release) radio resources taking into account single and multi-cell aspects. + +## 11.2 Definition and description of RRM functions + +### 11.2.1 Radio Bearer Control (RBC) + +The establishment, maintenance and release of Radio Bearers (as defined in [25.813]) involves the configuration of radio resources associated with them. When setting up a radio bearer for a service, radio bearer control takes into account the overall resource situation in E-UTRAN, the QoS requirements of in-progress sessions and the QoS requirement for the new service. RB control is also concerned with the maintenance of radio bearers of in-progress sessions at the change of the radio resource situation due to mobility or other reasons. RB control is involved in the release of radio resources associated with RB:s at session termination, handover or at other occasions. + +RBC is located in the eNodeB. + +### 11.2.2 Radio Admission Control (RAC) + +The task of radio admission control is to admit or reject the establishment requests for new radio bearers. In order to do this, RAC takes into account the overall resource situation in E-UTRAN, the QoS requirements, the priority levels and the provided QoS of in-progress sessions and the QoS requirement of the new RB request. The goal of RAC is to ensure high radio resource utilization (by accepting RB requests as long as radio resources available) and at the same time to ensure proper QoS for in-progress sessions (by rejecting RB requests when they cannot be accommodated). + +RAC is located in the eNodeB. + +### 11.2.3 Connection Mobility Control (CMC) + +Connection mobility control is concerned with the management of radio resources in connection with idle or active mode mobility. In idle mode, the cell reselection algorithms are controlled by setting of parameters (thresholds and hysteresis values) that define the best cell and/or determine when the UE should select a new cell. Also, E-UTRAN broadcasts parameters that configure the UE measurement and reporting procedures. In active mode, the mobility of radio connections has to be supported. Handover decisions may be based on UE and eNodeB measurements. In addition, handover decisions may take other inputs, such as neighbor cell load, traffic distribution, transport and hardware resources and Operator defined policies into account. + +CMC is located in the eNodeB. + +### 11.2.4 Packet Scheduling (PSC) + +The task of packet scheduling is to allocate and de-allocate resources (including buffer and processing resources and resource blocks (*i.e. chunks*)) to user and control plane packets. PSC involves several sub-tasks, including the selection of RB:s whose packets are to be scheduled and managing the necessary resources (e.g. the power levels or the specific resource blocks used). PSC typically takes into account the QoS requirements associated with RB:s, the channel quality information for UE:s, buffer status, interference situation, etc. + +PSC is located in the eNodeB. + +### 11.2.5 Inter-cell Interference Coordination (ICIC) + +Inter-cell interference coordination has the task to manage radio resources (notably the radio resource blocks) such that inter-cell interference is kept under control. The specific ICIC techniques that will be used in E-UTRA are decided by RAN1. + +ICIC is inherently a multi-cell RRM function that needs to take into account information (e.g. the resource usage status and traffic load situation) from multiple cells. The optimal placement of ICIC will also depend on the specific ICIC technique. + +### 11.2.6 Load Balancing (LB) + +Load balancing has the task to handle uneven distribution of the traffic load over multiple cells. The purpose of LB is thus to influence the load distribution in such a manner that radio resources remain highly utilized and the QoS of in-progress sessions are maintained to the extent possible. LB algorithms may result in hand-over decisions with the purpose of redistribute traffic from highly loaded cells to underutilized cells. + +The placement of LB is in the eNodeB is possible. + +### 11.2.7 Inter-RAT Radio Resource Management + +Inter-RAT RRM is primarily concerned with the management of radio resources in connection with inter-RAT mobility, notably inter-RAT hand-over. At inter-RAT hand-over, the hand-over decision may take into account the involved RAT:s resource situation as well as UE capabilities and Operator policies. The importance of Inter-RAT RRM may depend on the specific scenario in which E-UTRAN is deployed. + +The decision to initiate the inter-RAT HO for HOs towards non-LTE access is placed in the eNodeB. + +## 11.3 RRM architecture in LTE + +The RRM architecture for LTE is designed to support the RRM functions listed in the previous clause. Therefore, the function allocation to LTE nodes creates the basis for the architecture, including interfaces between nodes and the protocols to be used. + +It is assumed that a logical E-UTRAN node in addition to the eNB is not needed for RRM purposes. Moreover, due to the different usage of inter-cell RRM functionalities, each inter-cell RRM functionality should be considered separately in order to assess whether it should be handled in a centralised manner or in a distributed manner + +The allocation of RRM functions, as indicated in the preceding Clause, in LTE is as follows: + +#### **eNodeB:** + +- Radio Bearer Control +- Radio Admission Control +- Connection Mobility Control +- Packet Scheduling +- Load Balancing +- The decision to initiate the inter-RAT HO for HOs towards non-LTE access is placed in the eNodeB. + +Inter-cell Interference Coordination can, depending on outcome of further more detailed studies, be decided to be realized as anything from an implementation specific matter (e.g. more static schemes – like "planning") to completely distributed schemes operating on fully specified interfaces. Factors to weight into such decision can be for example expected performance gain, required update frequency, and expected implementation accuracy. + +## 11.4 Support of load sharing and policy management across different Radio Access Technologies (RATs) + +The E-UTRAN architecture will support load sharing across RATs. + +# --- 12 System and terminal complexity + +## 12.1 Over all system complexity + +A key requirement of E-UTRAN is to maintain the complexity at a reasonable level. Although no firm analysis on the final complexity has been performed, in this respect the following decisions have been taken: + +Decreased complexity: + +- The number of transport channels is reduced compared to UTRAN, by making use of shared channels and not supporting dedicated transport channels. +- The number of different MAC entities is reduced compared to UTRAN (e.g. MAC-d not needed in the absence of dedicated transport channels). +- The BMC layer and the CTCH of UTRAN are not needed in E-UTRAN, i.e. all data broadcast is on MBMS and on e.g. MTCH. +- There is no inter-eNB SHO in the downlink and in the uplink (as currently supported for Rel-6 dedicated channels in UTRAN) for the shared channel, in case of unicast transmissions. +- Compressed mode as defined for UTRAN is not supported. If some transmission/reception gaps for measurement purpose have to be provided to the UE, this will be based on scheduling gaps. +- RRC is simplified by e.g. reducing the number of RRC states compared to UTRAN (e.g. removal of UTRAN CELL\_FACH is agreed). + +Increased complexity: + +- Minimum UE bandwidth capability is smaller than largest cell bandwidths. +- RAN1 assumes SFN operation for efficient broadcast which requires synchronised network operation. + +## 12.2 Physical layer complexity + +Overall, no issue has been raised that would indicate that physical layer complexity would be unacceptably high and it can thus be concluded that E-UTRA implementation is feasible from a physical layer perspective. + +The E-UTRA system will provide significantly higher data rates than Release 6 WCDMA and, as a consequence hereof, the physical layer complexity will increase accordingly compared to lower-rate systems. The increase in data rate is achieved through higher transmission bandwidth and/or support for MIMO and will have complexity impacts such as: + +- higher channel decoding capacity +- larger soft buffer sizes for HARQ processing. + +This complexity is not seen as E-UTRA specific, but is similar to the complexity experienced in any high data rate system. + +One of the advantages of an OFDM/SC-FDMA based system is that it allows for implementation of a lower complexity receiver at wider bandwidths. Another advantage is the possibility of operating MBMS in a single frequency network manner where significant performance gains can be achieved with no additional complexity increase in the UE receiver (see clause 12.3). + +E-UTRA will support multiple bandwidth options ranging from 1.25 to 20 MHz and both FDD and TDD modes. The variable bandwidth options has a complexity impact, however with proper channel structures, e.g., designing control channels such that decoding is invariant to the transmission bandwidth, limited additional complexity due to the multiple bandwidths has been identified. Support for both FDD and TDD modes is not expected to have major complexity impact provided that maximum commonality between the two modes is maintained. + +Based on what was seen as acceptable increase in complexity, it has been decided that all UEs shall have a reception- and transmission-bandwidth capability of at least 10 MHz. Limiting the bandwidth to 10 MHz creates challenges in mobility measurements when 10 MHz UEs are receiving data from cells with 20 MHz operating bandwidth, but these problems are solvable with a limited complexity impact. + +To the extent possible, the design of E-UTRA has been done with the aim of reducing the number of unnecessary options in order to simplify implementation and testing. + +## 12.3 UE complexity + +With the progress of technology over time, some of the complexity restrictions may no longer apply, and allow reconsideration regarding addition of functionalities currently considered to be too complex, as well as functionalities currently not considered, in a later Release of the specification. However, if new functionalities are considered in the future, incremental gains that these additions could provide should also be evaluated. + +The document [9] introduced and proposed the following set of resource aggregation options for E-UTRA. + +- Resource aggregation type 1 - over adjacent channels in the same band with same content +- Resource aggregation type 2 - over separated channels in the same band with same content +- Resource aggregation type 3 - over separated channels in different bands with same content +- Resource aggregation type 4 - DL broadcast channel and bidirectional channel in the same band +- Resource aggregation type 5 – DL broadcast channel and bidirectional channel in the different bands + +RAN4 has analysed the feasibility and necessity of these different resource aggregation options. + +It was recognised in [9] that there may be benefits of having aggregation for different kinds of spectrum allocations for the operators. However, it was also considered in a RAN4 document\* that E-UTRA complexity compared to UTRA is already increased due to e.g. scalable bandwidths. It is also pointed out in the RAN4 document\* that the uplink and downlink parts of each type of resource aggregation have different implementation impacts and should be considered separately. The position of different aggregated carriers affects RF implementation and related complexity. However, as discussed in the RAN4 document\* from an RF implementation point-of-view, it does not matter for the downlink whether two aggregated resources support unicast data, broadcast data or any combination of these two. + +Resource aggregation types 1-3 have been discussed and analysed in several RAN4 documents\*. + +**Type1:** It was considered in a RAN4 document\* that instead of using resource aggregation a wider bandwidth carrier on a contiguous spectrum allocation would offer lower complexity and better performance allowed by advanced network algorithms like frequency domain scheduling. The presented simulation results in a RAN4 document\* indicated that the transmission of multiple SC-FDMA channels is significantly more inefficient from the PA perspective than the transmission of one wider bandwidth channel because PAR/CM levels would be higher for the transmission of multiple bandwidth channels meaning that at least in the uplink it is likely that there would be further specification impacts in terms of complexity of the RAN4 ACLR/emission requirements. + +**Type2:** As stated in a RAN4 document\* it is seen to be more efficient to improve the performance of data reception on one operating bandwidth rather than increasing UE complexity for supporting resource aggregation of the same content on more than one bandwidth. As for the type 1 also in this case at least in the uplink there would be further specification impacts in terms of complexity of the RAN4 ACLR/emission requirements. There are also impacts to the NB scheduler design and corresponding signalling. + +**Type3:** With the resource aggregation of the same content over different band, in addition to UE complexity issues network planning issues ( i.e. cell borders and sites being at different locations) were considered more challenging in RAN4 document\*, which would lead to more complicated RRM and network signalling. There are also UL specification impacts and issues in terms of spurious emissions requirements. + +### Conclusions on resource aggregation with same content + +Based on the findings of several RAN4 documents\* and RAN4 discussions, it is proposed to avoid resource aggregation for the same content (types 1, 2, and 3). The concerns raised in [9] are addressed as the minimum UE UL and DL bandwidth capabilities are agreed to be 10 MHz. Additionally terminals will support all bandwidth options within its bandwidth capability. Hence, this should give operators some flexibility in terms of channel arrangements. + +**Type 4&5:** The MBMS targets for the E-UTRA system in [4] indicate that some level of resource aggregation is probably needed for providing unicast and MBMS services simultaneously due to a requirement for a possibility to deploy MBMS on separate carrier. Both Type 4 and Type 5 are considered feasible. Complexity level depends on frequency separation. + +### Conclusions on resource aggregation with bi-directional and broadcast channels + +Based on the MBMS requirements in [4] and the recommendations on the resource aggregation of bi-directional and broadcast channels in several RAN4 documents\*, it is proposed that the resource aggregation of bi-directional and broadcast channels is considered further when developing the E-UTRA specifications in the work item phase. + +### **UE complexity issues related to the UE maximum output power** + +A RAN4 document\* considered UE complexity issues related to the UE maximum output power. The document concluded that it should be possible to reuse the rel-6 PA in order to allow for a single PA implementation for multi-mode (E-UTRA, UTRA) and multi-band terminals and that the E-UTRA UE power class should be a subset of the current UTRA Rel-6 power classes. + +### **Conclusions on UE output power** + +It is proposed to consider the outcome of RAN1 analyses on coverage and cell edge performance before concluding the UE maximum output power requirements. + +Note: \*See clause 5.3 in [8] + +# **13 Performance assessments** + +## **13.1 Peak data rate** + +The estimated peak rates deemed feasible with E-UTRA are summarized in table 13.1 and table 13.2 for FDD and TDD. For both uplink and downlink, it was found that achieving and even exceeding the peak rate requirements outlined in [4] is feasible. This is based on a preliminary layer 1 and layer 2 control overhead as well as realistic assumptions on the highest modulation order which can be used in the most favorable WAN environments. + +**Table 13.1: DL Peak rates for E-UTRA FDD/TDD (frame structure type 1)** + +| Assumptions | Downlink | | +|-------------|-------------------------------------------------------------------------------------|--------| +| | 64 QAM, R=1 | | +| | Signal overhead for reference signals and control channel occupying one OFDM symbol | | +| Unit | Mbps in 20 MHz | b/s/Hz | +| Requirement | 100 | 5.0 | +| 2x2 MIMO | 172.8 | 8.6 | +| 4x4 MIMO | 326.4 | 16.3 | + +**Table 13.1a: UL Peak rates for E-UTRA FDD/TDD frame structure type 1** + +| | Uplink | | +|-------------|----------------------------------------------------------------------------------------------|--------| +| Assumptions | Single TX UE, R=1
Signal overhead for reference signals and control channel occupying 2RB | | +| Unit | Mbps in 20 MHz | b/s/Hz | +| Requirement | 50 | 2.5 | +| 16QAM | 57.6 | 2.9 | +| 64QAM | 86.4 | 4.3 | + +Table 13.2: Peak rates for E-UTRA TDD (TDD frame structure type 2) + +| | Downlink | | Uplink | | +|----------------|---------------------------------------|--------|-----------------------------------------------------|--------| +| Assumptions | 64 QAM, R=1
frame structure type 2 | | Single TX UE, 64 QAM, R=1
frame structure type 2 | | +| Unit | Mbps in 20 MHz | b/s/Hz | Mbps in 20 MHz | b/s/Hz | +| Requirement | 100 | 5.0 | 50 | 2.5 | +| 2x2 MIMO in DL | 142 | 7.1 | 62.7 | 3.1 | +| 4x4 MIMO in DL | 270 | 13.5 | | | + +## 13.2 C-plane latency + +Figure 13.1 provides an example C-plane flow for the LTE\_IDLE to LTE\_ACTIVE transition in LTE/SAE and is based on the procedure described in sub-clause 7.14.2 of [3]. + +![Sequence diagram of C-plane activation procedure showing interactions between UE, eNB, and MME with various delays and messages.](50214d232017279410e9c9db8eb75119_img.jpg) + +``` + +sequenceDiagram + participant UE + participant eNB + participant MME + + Note left of UE: 1. Delay for RACH Scheduling period + Note left of UE: 4. Processing delay in UE + UE->>eNB: 2. RACH Preamble + Note right of eNB: 3. Processing delay in eNB + eNB->>UE: 3. TA + Scheduling Grant + Note right of eNB: 7. Processing delay in eNB + UE->>eNB: 5. RRC Connection Request + Note right of eNB: 9. Processing delay in MME + eNB->>MME: 8. Connection Request + Note right of MME: 11. Processing delay in eNB + MME->>eNB: 10. Connection Setup + Note left of UE: 14. Processing delay in UE + eNB->>UE: 12. RRC Connection Setup + Note right of eNB: 11. Processing delay in eNB + UE->>eNB: 15. RRC Connection Complete + Note left of UE: 14. Processing delay in UE + eNB->>UE: 16. H-ARQ Retransmission + Note right of eNB: 11. Processing delay in eNB + Note left of UE: 4. Processing delay in UE + Note right of eNB: 7. Processing delay in eNB + Note right of eNB: 9. Processing delay in MME + Note right of eNB: 11. Processing delay in eNB + +``` + +The diagram illustrates the C-plane activation procedure for an LTE\_IDLE to LTE\_ACTIVE transition. It shows the sequence of messages and processing delays between the User Equipment (UE), the evolved NodeB (eNB), and the Mobility Management Entity (MME). The process starts with a delay for RACH Scheduling period and processing delay in the UE. The UE sends a RACH Preamble to the eNB, which has a processing delay. The eNB responds with TA + Scheduling Grant. The UE then sends an RRC Connection Request, which has a processing delay in the eNB. The eNB sends a Connection Request to the MME, which has a processing delay in the MME. The MME responds with a Connection Setup, which has a processing delay in the eNB. The eNB sends an RRC Connection Setup to the UE, which has a processing delay in the UE. The UE responds with an RRC Connection Complete, which has a processing delay in the eNB. The eNB then sends an H-ARQ Retransmission to the UE, which has a processing delay in the UE. The diagram also shows H-ARQ Retransmissions between the UE and the eNB, and between the eNB and the MME, with associated processing delays. + +Sequence diagram of C-plane activation procedure showing interactions between UE, eNB, and MME with various delays and messages. + +Figure 13.1: C-plane activation procedure (example) + +NOTE: The RRC Contention Resolution message (between steps 7 and 8) does not contribute to the overall state transition latency and is therefore not included in the analysis. + +### 13.2.1 FDD frame structure + +Tables 13.3 and 13.3a provide a timing analysis, assuming FDD frame structure, of the flow depicted in Figure 13.1. The analysis illustrates that the requirement for the state transition from LTE\_IDLE to LTE\_ACTIVE can be achieved within the 100ms requirement. + +**Table 13.3: C-plane latency analysis (based on the procedure depicted in Figure 13.1)** + +| Step | Description | Duration | +|------|----------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------| +| 0 | UE wakeup time | Implementation dependent – Note included | +| 1 | Average delay due to RACH scheduling period | 5ms | +| 2 | RACH Preamble | 1ms | +| 3 | Preamble detection and transmission of RA response (Time between the end RACH transmission and UE's reception of scheduling grant and timing adjustment) | 5ms | +| 4 | UE Processing Delay (decoding of scheduling grant, timing alignment and C-RNTI assignment + L1 encoding of RRC Connection Request) | 2.5ms | +| 5 | TTI for transmission of RRC Connection Request | 1ms | +| 6 | HARQ Retransmission (@ 30%) | 0.3 *5ms | +| 7 | Processing delay in eNB (Uu –> S1-C) | 4ms | +| 8 | S1-C Transfer delay | Ts1c (2ms – 15ms) | +| 9 | MME Processing Delay (including UE context retrieval of 10ms) | 15ms | +| 10 | S1-C Transfer delay | Ts1c (2ms – 15ms) | +| 11 | Processing delay in eNB (S1-C –> Uu) | 4ms | +| 12 | TTI for transmission of RRC Connection Setup (+Average alignment) | 1.5ms | +| 13 | HARQ Retransmission (@ 30%) | 0.3 *5ms | +| 14 | Processing delay in UE | 3ms | +| 15 | TTI for transmission of L3 RRC Connection Complete | 1ms | +| 16 | HARQ Retransmission (@ 30%) | 0.3 *5ms | +| | Total LTE IDLE → ACTIVE delay (C-plane establishment) | 47.5ms + 2 * Ts1c | + +**Table 13.3a: U-plane establishment latency** + +| Step | Description | Duration | +|------|------------------------------------------------------------|-------------------------------| +| | LTE_IDLE → LTE_ACTIVE delay (C-plane establishment) | 47.5ms + 2 * Ts1c | +| 17 | TTI for UL DATA PACKET (Piggy back scheduling information) | 1ms | +| 18 | HARQ Retransmission (@ 30%) | 0.3 * 5ms | +| 19 | eNB Processing Delay (Uu –> S1-U) | 1ms | +| | U-plane establishment delay (RAN edge node) | 51ms + 2 * Ts1c | +| 20 | S1-U Transfer delay | Ts1u (1ms – 15ms) | +| 21 | UPE Processing delay (including context retrieval) | 10ms | +| | U-plane establishment delay (Serving GW) | 61ms + 2 * Ts1c + Ts1u | + +Note 1: The figures included in Steps 8, 9, 10, 20 and 21 are outside the scope of RAN WG2. + +Note 2: The S1-C transfer delay is estimated to be longer than the S1-U transfer delay, since more reliable L2 protocol stack is assumed for S1-C. + +Note 3: For procedural aspects which remain to be agreed in RAN WG2, the analysis contains preliminary assumptions. + +### 13.2.2 TDD frame structure type 1 + +Table 13.3b provides a timing analysis, assuming TDD frame structure 1 with different frame formats as shown in Figure 13.1a. The analysis illustrates that the requirement for the state transition from LTE\_IDLE to LTE\_ACTIVE can be achieved within the 100ms requirement. + +![Diagram showing four TDD frame formats: 4-DL/1-UL, 3-DL/2-UL, 2-DL/3-UL, and 1-DL/4-UL. Each format is represented by a horizontal bar divided into 10 subframes, each containing either 'D' (Downlink) or 'U' (Uplink). 4-DL/1-UL: D D D D U D D D D U; 3-DL/2-UL: D D D U U D D D U U; 2-DL/3-UL: D D U U U D D U U U; 1-DL/4-UL: D U U U U D U U U U.](32ff77da4286b58c4778033acaa10836_img.jpg) + +10 ms radio frame + +Diagram showing four TDD frame formats: 4-DL/1-UL, 3-DL/2-UL, 2-DL/3-UL, and 1-DL/4-UL. Each format is represented by a horizontal bar divided into 10 subframes, each containing either 'D' (Downlink) or 'U' (Uplink). 4-DL/1-UL: D D D D U D D D D U; 3-DL/2-UL: D D D U U D D D U U; 2-DL/3-UL: D D U U U D D U U U; 1-DL/4-UL: D U U U U D U U U U. + +Figure 13.1a: TDD frame formats + +Table 13.3b: C-plane latency analysis for TDD frame structure 1 (based on the procedure depicted in Figure 13.1) + +| Step | Description | 4-DL/1-UL | 3-DL/2-UL | 2-DL/3-UL | 1-DL/4-UL | +|------|----------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------|------------------------|-----------------------| +| 0 | UE wakeup time | Implementation dependent – Not included | | | | +| 1 | Average delay due to RACH scheduling period | 5ms | 5ms | 5ms | 5ms | +| 2 | RACH Preamble | 1ms | 1ms | 1ms | 1ms | +| 3 | Preamble detection and transmission of RA response (Time between the end RACH transmission and UE's reception of scheduling grant and timing adjustment) | 6ms | 6ms | 6ms | 6ms | +| 4 | UE Processing Delay (decoding of scheduling grant, timing alignment and C-RNTI assignment + L1 encoding of RRC Connection Request ) | 3ms | 3ms | 3ms | 3ms | +| 5 | TTI for transmission of RRC Connection Request | 1ms | 1ms | 1ms | 1ms | +| 6 | HARQ Retransmission (@ 30%) | 0.3*5ms | 0.3*4.5ms | 0.3*4.33ms | 0.3 * 5.75ms | +| 7 | Processing delay in eNB (Uu -> S1-C) | 4ms | 4ms | 4ms | 4ms | +| 8 | S1-C Transfer delay | Ts1c (2ms – 15ms) | Ts1c (2ms – 15ms) | Ts1c (2ms – 15ms) | Ts1c (2ms – 15ms) | +| 9 | MME Processing Delay (including UE context retrieval of 10ms) | 15ms | 15ms | 15ms | 15ms | +| 10 | S1-C Transfer delay | Ts1c (2ms – 15ms) | Ts1c (2ms – 15ms) | Ts1c (2ms – 15ms) | Ts1c (2ms – 15ms) | +| 11 | Processing delay in eNB (S1-C -> Uu) | 4ms | 4ms | 4ms | 4ms | +| 12 | TTI for transmission of RRC Connection Setup (+Average alignment) | 1.7ms | 2.1ms | 2.7ms | 3.5ms | +| 13 | HARQ Retransmission (@ 30%) | 0.3*5.75ms | 0.3*4.33ms | 0.3*4.5ms | 0.3 * 5ms | +| 14 | Processing delay in UE | 3ms | 3ms | 3ms | 3ms | +| 15 | TTI for transmission of L3 RRC Connection Complete (+Average alignment) | 3.5ms | 2.7ms | 2.1ms | 1.7ms | +| 16 | HARQ Retransmission (@ 30%) | 0.3*5ms | 0.3*4.5ms | 0.3*4.33ms | 0.3 * 5.75ms | +| | Total LTE_IDLE→LTE_ACTIVE delay (C-plane establishment) | 51.925 + 2*Ts1c | 50.799 + 2*Ts1c | 50.748 + 2*Ts1c | 52.15 + 2*Ts1c | + +**Table 13.3c:** U-plane establishment latency + +| Step | Description | 4-DL/1-UL | 3-DL/2-UL | 2-DL/3-UL | 1-DL/4-UL | +|------|--------------------------------------------------------------------------------|---------------------------------------|---------------------------------------|---------------------------------------|---------------------------------------| +| | LTE_IDLE→LTE_ACTIVE delay (C-plane establishment) | 51.925 +
2*Ts1c | 50.799 +
2*Ts1c | 50.748 +
2*Ts1c | 52.15 +
2*Ts1c | +| 17 | TTI for UL data packet + average alignment (Piggy back scheduling information) | 3.5ms | 2.7ms | 2.1ms | 1.7ms | +| 18 | HARQ Retransmission (@ 30%) | 0.3*5ms | 0.3*4.5ms | 0.3*4.33ms | 0.3 * 5.75ms | +| 19 | eNB Processing Delay (Uu → S1-U) | 1ms | 1ms | 1ms | 1ms | +| | U-plane establishment delay (RAN edge node) | 57.925
+ 2*Ts1c | 55.849
+ 2*Ts1c | 54.148
+ 2*Ts1c | 56.575
+ 2*Ts1c | +| 20 | S1-U Transfer delay | Ts1u (1ms – 15ms) | Ts1u (1ms – 15ms) | Ts1u (1ms – 15ms) | Ts1u (1ms – 15ms) | +| 21 | UPE Processing delay (including context retrieval) | 10ms | 10ms | 10ms | 10ms | +| | U-plane establishment delay (Serving GW) | 67.925
+ 2*Ts1c +
Ts1u | 65.849
+ 2*Ts1c +
Ts1u | 64.148
+ 2*Ts1c +
Ts1u | 66.575
+ 2*Ts1c +
Ts1u | + +### 13.2.3 TDD frame structure type 2 + +The C-plane establishment latency analysis for TDD frame structure 2 is summarised in table 13.3d. + +**Table 13.3d:** C-plane establishment latency analysis (based on the procedure depicted in Figure 13.1) + +| Step | Description | Duration | +|------|----------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------| +| 0 | UE wakeup time | Implementation dependent – Not included | +| 1 | Average delay due to RACH scheduling period | 2.5ms | +| 2 | RACH Preamble | 0.95ms | +| 3 | Preamble detection and transmission of RA response (Time between the end RACH transmission and UE's reception of scheduling grant and timing adjustment) | 7.025ms | +| 4 | UE Processing Delay (decoding of scheduling grant, timing alignment and C-RNTI assignment + L1 encoding of RRC Connection Request) | 2.3ms | +| 5 | TTI for transmission of RRC Connection Request | 0.675ms | +| 6 | HARQ Retransmission (@ 30%) | 0.3 * 5ms | +| 7 | Processing delay in eNB (Uu → S1-C) | 4ms | +| 8 | S1-C Transfer delay | Ts1c (2ms – 15ms) | +| 9 | MME Processing Delay (including UE context retrieval of 10ms) | 15ms | +| 10 | S1-C Transfer delay | Ts1c (2ms – 15ms) | +| 11 | Processing delay in eNB (S1-C → Uu) | 4ms | +| 12 | TTI for transmission of RRC Connection Setup (+Average alignment) | 2.163ms | +| 13 | HARQ Retransmission (@ 30%) | 0.3 * 5ms | +| 14 | Processing delay in UE | 2.975ms | +| 15 | TTI for transmission of L3 RRC Connection Complete | 0.675ms | +| 16 | HARQ Retransmission (@ 30%) | 0.3 * 5ms | +| | Total LTE_IDLE→LTE_ACTIVE delay (C-plane establishment) | 46.763ms + 2 * Ts1c | + +For TDD frame structure type 2, U-plane establishment delay data was not available at the time of writing. + +## 13.3 U-plane latency + +The requirement on U-plane latency in clause 6.2.2 of TR 25.913 [4] reads as follows: + +**"U-Plane Delay Definition** – U-plane delay is defined in terms of the one-way transit time between a packet being available at the IP layer in either the UE/RAN edge node and the availability of this packet at IP layer in the RAN edge node/UE. The RAN edge node is the node providing the RAN interface towards the core network. + +*Specifications shall enable an E-UTRA U-plane latency of less than 5 ms in unload condition (i.e. single user with single data stream) for small IP packet, e.g. 0 byte payload + IP headers E-UTRAN bandwidth mode may impact the experienced latency* + +*Note: This requirement, more specifically the exact definition of latency, may be revisited and further clarified once there is a 3GPP system end-to-end requirement agreed and the overall system architecture is settled, including the RAN and core network functional split. This means that the network entities between which the U-plane latency requirement of E-UTRA and E-UTRAN applies, will finally be defined at a later stage."* + +With PDCP terminated in the eNB, it is understood that the RAN edge node is the eNB. The U-plane assessment assumes, in accordance with the requirement, unload conditions where scheduling delays are negligible. Further, it is assumed that a valid scheduling grant is available; i.e. no random access procedure needs to be performed. + +### 13.3.1 FDD frame structure + +The LTE U-plane delay consists of node processing delays, TTI duration, and radio frame alignment. The delay components are summarised in Figure 13.2. + +![Diagram illustrating U-plane latency components in LTE between a UE and an eNB. The diagram shows two vertical bars representing the UE and eNB. Between them, horizontal arrows indicate latency components. For the downlink (top), the components are: 1 ms processing at the eNB, 1.5 ms for TTI + frame alignment, and 1 ms processing at the UE. For the uplink (bottom), the components are: 1 ms processing at the UE, 1.5 ms for TTI + frame alignment, and 1 ms processing at the eNB. A large curved arrow labeled 'HARQ RTT 5 ms' indicates the round-trip time between the UE and eNB.](48f209b7c0c1f91af40cfc3466dbd534_img.jpg) + +Diagram illustrating U-plane latency components in LTE between a UE and an eNB. The diagram shows two vertical bars representing the UE and eNB. Between them, horizontal arrows indicate latency components. For the downlink (top), the components are: 1 ms processing at the eNB, 1.5 ms for TTI + frame alignment, and 1 ms processing at the UE. For the uplink (bottom), the components are: 1 ms processing at the UE, 1.5 ms for TTI + frame alignment, and 1 ms processing at the eNB. A large curved arrow labeled 'HARQ RTT 5 ms' indicates the round-trip time between the UE and eNB. + +**Figure 13.2: U-plane latency components in LTE** + +Based on the assumptions above, the LTE U-plane latency can be written: + +$$D_{UP} [ms] = 1 + 1.5 + 1 + n * 5 = 3.5 + n * 5,$$ + +where $n$ is the number of HARQ re-transmissions. In typical cases there would be 0 or 1 re-transmissions yielding an approximate average U-plane latency of + +$$D_{UP,typical} [ms] = 3.5 + p * 5,$$ + +where $p$ is the error probability of the first HARQ transmission. Hence the U-plane latency is a function of the HARQ operating point. Table 13.4 shows the U-plane latency when HARQ is operated at an initial transmission error probability of 0.0 and 0.3, respectively. + +**Table 13.4: U-plane latency analysis (estimated average)** + +| Step | Description | Value (0% HARQ) | Value (30% HARQ) | +|------|------------------------------------------------------------|-----------------------------------------|-----------------------------------------| +| 0 | UE wakeup time | Implementation dependent – Not included | Implementation dependent – Not included | +| 1 | UE Processing Delay | 1ms | 1ms | +| 2 | Frame Alignment | 0.5ms | 0.5ms | +| 3 | TTI for UL DATA PACKET (Piggy back scheduling information) | 1 ms | 1 ms | +| 4 | HARQ Retransmission | 0 ms | 0.3*5ms | +| 5 | eNB Processing Delay (Uu -> S1-U) | 1ms | 1ms | +| | Total one way delay | 3.5ms | 5ms | + +Note: While table 13.4 illustrates the U-plane latency for the UL, the indicated latencies, although applied in a different order, should be understood as representative also for the DL. + +For FDD frame structure, it is concluded that for a typical case with an initial HARQ error rate of 0.0 and 0.3, total average U-plane latencies of 3.5ms and 5.0ms, respectively, can be achieved. + +### 13.3.2 TDD frame structure type 1 + +The LTE U-plane delay consists of node processing delays, TTI duration, radio frame alignment and S1-U delay. The delay components are summarised in Figure 13.2a for TDD. + +![Figure 13.2a: U-plane latency components in TDD. The diagram shows the latency components between a UE and an eNB for both Downlink (DL) and Uplink (UL) directions. For the DL direction (top), the latency components are: UE processing delay (1 ms), TTI + frame alignment (1+Tf_dl ms), and eNB processing delay (1 ms). The HARQ RTT (Th_dl ms) is shown as a round-trip delay between the UE and eNB. For the UL direction (bottom), the latency components are: eNB processing delay (1 ms), TTI + frame alignment (1+Tf_ul ms), and UE processing delay (1 ms). The HARQ RTT (Th_ul ms) is shown as a round-trip delay between the eNB and UE.](18291be12b470a557e8c9f3a74e021be_img.jpg) + +Figure 13.2a: U-plane latency components in TDD. The diagram shows the latency components between a UE and an eNB for both Downlink (DL) and Uplink (UL) directions. For the DL direction (top), the latency components are: UE processing delay (1 ms), TTI + frame alignment (1+Tf\_dl ms), and eNB processing delay (1 ms). The HARQ RTT (Th\_dl ms) is shown as a round-trip delay between the UE and eNB. For the UL direction (bottom), the latency components are: eNB processing delay (1 ms), TTI + frame alignment (1+Tf\_ul ms), and UE processing delay (1 ms). The HARQ RTT (Th\_ul ms) is shown as a round-trip delay between the eNB and UE. + +**Figure 13.2a: U-plane latency components in TDD** + +Where + +$Th_{dl}$ : average HARQ RTT in downlink + +$Tf_{dl}$ : average frame alignment delay in downlink + +$Th_{ul}$ : average HARQ RTT in uplink + +$T_{f,ul}$ : average frame alignment delay in uplink + +Based on the assumptions above, the LTE U-plane latency can be written: + +$$D_{UP} [ms] = 1 + 1 + T_f + 1 + n * T_h$$ + +where $T_f$ is the frame alignment delay, $T_h$ is the HARQ RTT and $n$ is the number of HARQ re-transmissions. As indicated above, $T_f$ and $T_h$ can be different for ulink and downlink. In typical cases there would be 0 or 1 re-transmissions yielding an approximate average U-plane latency of + +$$D_{UP,typical} [ms] = 3 + T_f + p * T_h,$$ + +where $p$ is the error probability of the first HARQ transmission. Hence the U-plane latency is a function of the HARQ operating point. Tables 13.4a and 13.4b show the U-plane latency in downlink and uplink, respectively, for different TDD frame formats when no HARQ retransmission is assumed for the first transmission. + +**Table 13.4a: U-plane latency** analysis with 0% HARQ (estimated average in downlink) + +| Step | Description | 4-DL/1-UL | 3-DL/2-UL | 2-DL/3-UL | 1-DL/4-UL | +|------|------------------------------------------------------------|-----------------------------------------|--------------|--------------|--------------| +| 0 | UE wakeup time | Implementation dependent – Not included | | | | +| 1 | UE Processing Delay | 1ms | 1ms | 1ms | 1ms | +| 2 | Frame Alignment | 0.7ms | 1.1ms | 1.7ms | 2.5ms | +| 3 | TTI for UL DATA PACKET (Piggy back scheduling information) | 1ms | 1ms | 1ms | 1ms | +| 4 | HARQ Retransmission | 0ms | 0ms | 0ms | 0ms | +| 5 | eNB Processing Delay (Uu -> S1-U) | 1ms | 1ms | 1ms | 1ms | +| | Total one way delay | 3.7ms | 4.1ms | 4.7ms | 5.5ms | + +**Table 13.4b: U-plane latency** analysis with 0% HARQ (estimated average in uplink) + +| Step | Description | 4-DL/1-UL | 3-DL/2-UL | 2-DL/3-UL | 1-DL/4-UL | +|------|------------------------------------------------------------|-----------------------------------------|--------------|--------------|--------------| +| 0 | UE wakeup time | Implementation dependent – Not included | | | | +| 1 | UE Processing Delay | 1ms | 1ms | 1ms | 1ms | +| 2 | Frame Alignment | 2.5ms | 1.7ms | 1.1ms | 0.7ms | +| 3 | TTI for UL DATA PACKET (Piggy back scheduling information) | 1ms | 1ms | 1ms | 1ms | +| 4 | HARQ Retransmission | 0ms | 0ms | 0ms | 0ms | +| 5 | eNB Processing Delay (Uu -> S1-U) | 1ms | 1ms | 1ms | 1ms | +| | Total one way delay | 5.5ms | 4.7ms | 4.1ms | 3.7ms | + +Analysis shows that the 5ms U-plane latency requirement may be simultaneously satisfied in TDD for both uplink and downlink using the 2-DL/3-UL and 3-DL/2-UL framing structures with no re-transmission assumed for the first transmission. + +### 13.3.3 TDD frame structure type 2 + +Tables 13.4c and 13.4d show the U-plane latency in downlink and uplink, respectively, for a 4-DL/3-UL configuration of TDD frame structure 2. + +**Table 13.4c: U-plane latency** analysis (estimated average in downlink) + +| Step | Description | Value (0% HARQ) | Value (30% HARQ) | +|------|---------------------------------|-----------------------------------------|-----------------------------------------| +| 0 | UE wakeup time | Implementation dependent – Not included | Implementation dependent – Not included | +| 1 | eNB Processing Delay (S1-U->Uu) | 1ms | 1ms | +| 2 | Frame Alignment | 1.022ms | 1.022ms | +| 3 | TTI for DL DATA PACKET | 0.675ms | 0.675ms | +| 4 | HARQ Retransmission | 0ms | 0.3*5ms | +| 5 | UE Processing Delay | 1ms | 1ms | +| | Total one way delay | 3.697ms | 5.197ms | + +**Table 13.4d: U-plane latency** analysis (estimated average in uplink) + +| Step | Description | Value (0% HARQ) | Value (30% HARQ) | +|------|------------------------------------------------------------|-----------------------------------------|-----------------------------------------| +| 0 | UE wakeup time | Implementation dependent – Not included | Implementation dependent – Not included | +| 1 | UE Processing Delay | 1ms | 1ms | +| 2 | Frame Alignment | 1.423ms | 1.423ms | +| 3 | TTI for UL DATA PACKET (Piggy back scheduling information) | 0.675ms | 0.675ms | +| 4 | HARQ Retransmission | 0ms | 0.3*5ms | +| 5 | eNB Processing Delay (Uu -> S1-U) | 1ms | 1ms | +| | Total one way delay | 4.098ms | 5.598ms | + +In TDD frame structure type 2, the requirements on U-plane delay can be reached. + +## 13.4 User throughput + +### 13.4.1 Fulfilment of uplink user-throughput targets + +#### 13.4.1.1 Initial performance evaluation + +According to [4], the agreed target for the LTE radio-access concept in terms of average and cell-edge user throughput are 2-3 times gain compared to the baseline configuration. + +Multiple evaluations that directly evaluate the uplink system performance of the LTE concept vs. the baseline configuration have been carried out. The evaluations have been carried out by different sources/companies and for different scenarios, something that provides a certain degree of diversity in the evaluation results. + +- In terms of average user throughput, the results indicate gains vs. the baseline configuration also ranging from around 2 times to above 3 times. +- In terms of cell-edge user throughput, the results indicate gains vs. the baseline configuration ranging from around 2 times to, in some cases, well above 3 times. + +It should be pointed out that some proposed and considered LTE features, such as the possibility for a variable TTI for overhead/delay optimization and different schemes for interference mitigation, have not been included in all of the evaluations. Thus there is a potential for further LTE uplink performance enhancements. + +Based on this, one can conclude that the LTE SC-FDMA-based uplink as currently defined includes the features needed to fulfil the agreed targets on uplink user throughput. + +#### 13.4.1.2 UL user throughput performance evaluation + +According to evaluation metric and assumption in [10], multiple evaluations that directly evaluate the uplink system performance of the LTE concept vs. the baseline configuration have been carried out. Efforts have been made to use realistic physical and link layer model. Further, fairness and coverage aspects are controlled through not only measuring average performance, but also cell-edge performance. The evaluations have been carried out by different sources/companies and for different scenarios. For both the baseline UTRA and E-UTRA results, the average cell throughput figures match well between companies. Summaries of the results for simulation cases 1 and 3 are presented in Table 13.4e and Table 13.4f, respectively. The figures for each system concept and metric have been obtained by + +averaging the results presented in the individual input papers. It can be seen that the requirements given in [4] are met, i.e. 2-3 times improvement in cell user throughputs. + +**Table 13.4e: UL user throughput performance for Case 1(500m ISD)** + +| Case 1 | Mean User Throughput | Cell-Edge User Throughput | +|--------------------|----------------------|---------------------------| +| | x UTRA | x UTRA | +| UTRA baseline | x1.0 | x1.0 | +| E-UTRA 1x2 | x2.2 | x2.5 | +| E-UTRA 1x4 | x3.3 | x5.5 | +| E-UTRA 2x2 SU-MIMO | x2.3 | x1.1 | + +**Table 13.4f: UL user throughput performance for Case 3(1732m ISD)** + +| Case 3 | Mean User Throughput | Cell-Edge User Throughput | +|---------------|----------------------|---------------------------| +| | x UTRA | x UTRA | +| UTRA baseline | x1.0 | x1.0 | +| E-UTRA 1x2 | x2.2 | x2.0 | +| E-UTRA 1x4 | x3.3 | x4.2 | + +### 13.4.2 Fulfilment of downlink user-throughput targets + +#### 13.4.2.0 Initial performance evaluation + +According to [4], the agreed targets for the LTE radio-access concept in terms of average and cell-edge user throughput are 3-4 times gain and 2-3 times gain vs. the baseline configuration defined in [4], respectively. + +Multiple evaluations that directly evaluate the downlink system performance of the LTE concept vs. the baseline configuration have been carried out. The evaluations have been carried out by different sources/companies and for different scenarios, something that provides a certain degree of diversity in the evaluation results. + +Evaluations have been carried out both assuming that MIMO is used in case of LTE evaluation(s) and that MIMO is not used in case of the LTE evaluation(s). As expected, including MIMO in the evaluations provide higher LTE system performance. It should be pointed out that including MIMO for LTE is inline with the agreed assumptions in [4]. + +- All evaluations indicate that the LTE concept fulfils the agreed target for cell-edge throughput, assuming a lower-speed (3 km/h) scenario. +- In terms of average user throughput, the evaluation indicate that the LTE concept fulfils or is very close (within 10%) to the agreed target. + +Based on these evaluations one cannot directly conclude that the LTE concept fulfils the LTE downlink user-throughput targets. However, these evaluations do not include all the features that are suggested to be part of the LTE radio-access concept, most notably different schemes for more advanced interference mitigation (e.g. interference coordination and/or cancellation) and variable TTI for overhead/delay optimization. Adding the potential gains of this to the above summarized gains would indicate that the LTE downlink radio-access concept can fulfil the agreed user-throughput targets. + +More information can be found in clause 8 of [2]. + +#### 13.4.2.1 Fulfilment of downlink user-throughput targets by enhancement techniques + +Multiple evaluations that directly evaluate the gains of downlink system performance of the LTE concept with enhancement techniques have been carried out. Specifically, the enhancement techniques are longer TTI, static interference coordination, interference cancellation adaptive antenna schemes and semi-static interference coordination. The evaluations have been carried out by different sources/companies and for different scenarios, something that provides a certain degree of diversity in the evaluation results. Each technique can improve both average user throughput and 5%-tile user throughput performance by at least 10%. + +Without performing simulations including, at same time, all these techniques, it is somewhat difficult to conclude on exact cumulative gain figures for all the techniques. However it is likely that with these techniques included in LTE specification and implementation, at least 3.5x gain in sector spectral efficiency together with at least 3x gain in 5%-tile user throughput can be achieved. There is the potential, considering some of the simulation results, that even higher gains could be achieved. + +Note that these gains can be achieved simultaneously with corresponding gains in spectral efficiency (system throughput), see subclause 13.5.2.1. + +More information can be found in clause 8 of [2]. + +##### 13.4.2.1.1 Performance Enhancement by Additional Transmit Antennas: 4 Transmit Antennas + +Multiple evaluations that directly evaluate the gains of downlink system performance of the LTE concept with additional TX and RX antennas (up to four antennas) have been carried out. The evaluations have been carried out by different sources/companies and for different scenarios, something that provides a certain degree of diversity in the evaluation results. + +- Additional gain of 4x2 antenna vs. 2x2 antenna LTE is more than 10%. +- Additional gain of 4x4 antenna vs. 2x2 antenna LTE is more than 60%. + +Based on these evaluations, one can draw the conclusion that additional antennas can improve both average and 5%-tile downlink user throughput significantly + +More information can be found in clause 8 of [2]. + +#### 13.4.2.2 DL user throughput performance evaluation + +According to evaluation metric and assumption in [10], multiple evaluations that directly evaluate the downlink system performance of the LTE concept vs. the baseline configuration have been carried out. Efforts have been made to use realistic physical and link layer model. Further, fairness and coverage aspects are controlled through not only measuring average performance, but also cell-edge performance. The evaluations have been carried out by different sources/companies and for different scenarios, something that provides a certain degree of diversity in the evaluation results. Summaries of the results for simulation cases 1 and 3 are presented in Table 13.4g and 13.4h respectively. For E-UTRA, results are presented both for the 2x2 (Ntx x Nrx antennas) reference configuration, as well as for the enhanced 4x2 and 4x4 configurations. The figures for each system concept and metric have been obtained by averaging the results presented in the individual input papers. It can be seen that the requirements given in [4] are met, i.e. 3-4 times improvement in average user throughputs, and 2-3 times improvement in cell-edge user throughput + +**Table 13.4g: DL user throughput performance for Case 1 (500m ISD).** + +| Case 1 | Mean User Throughput | Cell-Edge User Throughput | +|--------------------|----------------------|---------------------------| +| | x UTRA | x UTRA | +| UTRA baseline 1x2 | x1,0 | x1,0 | +| E-UTRA 2x2 SU-MIMO | x3,2 | x2,7 | +| E-UTRA 4x2 SU-MIMO | x3,5 | x3,0 | +| E-UTRA 4x4 SU-MIMO | x5,0 | x4,4 | + +**Table 13.4h: DL user throughput performance for Case 3 (1732m ISD).** + +| Case 3 | Mean User Throughput | Cell-Edge User Throughput | +|--------------------|----------------------|---------------------------| +| | x UTRA | x UTRA | +| UTRA baseline 1x2 | x1,0 | x1,0 | +| E-UTRA 2x2 SU-MIMO | x3,0 | x2,3 | +| E-UTRA 4x2 SU-MIMO | x3,6 | x2,8 | +| E-UTRA 4x4 SU-MIMO | x4,6 | x4,8 | + +## 13.5 Spectrum efficiency + +### 13.5.1 Fulfilment of uplink spectrum-efficiency target + +#### 13.5.1.1 Initial performance evaluation + +According to [4], the agreed target for the LTE radio-access concept in terms of uplink spectrum efficiency is 2-3 times gain vs. the baseline configuration defined in [4]. + +Multiple evaluations that directly evaluate the uplink system performance of the LTE concept vs. the baseline configuration have been carried out. The evaluations have been carried out by different sources/companies and for different scenarios, something that provides a certain degree of diversity in the evaluation results. In terms of spectrum efficiency, the results of these evaluations indicate gains vs. the baseline configuration ranging from around 2 times to above 3 times. + +The system performance for VoIP traffic has also been evaluated, and VoIP capacity of more than 3 times versus the baseline configuration defined in [4] has been observed. + +It should be pointed out that some proposed and considered LTE features, such as the possibility for a variable TTI for overhead/delay optimization and different schemes for interference mitigation, have not been included in all of the evaluations. Thus there is a potential for further LTE uplink performance enhancements. + +Based on this, one can conclude that the LTE SC-FDMA-based uplink as defined in clause 7.2 of this TR includes the features needed to fulfil the agreed targets on uplink spectrum efficiency. + +#### 13.5.1.2 UL spectrum efficiency performance evaluation + +According to evaluation metric and assumption in [10], multiple evaluations that directly evaluate the uplink system performance of the LTE concept vs. the baseline configuration have been carried out. Efforts have been made to use realistic physical and link layer model. Further, fairness and coverage aspects are controlled through not only measuring average performance, but also cell-edge performance. The evaluations have been carried out by different sources/companies and for different scenarios. For both the baseline UTRA and E-UTRA results, the spectrum efficiency figures match well between companies. Summaries of the results for simulation cases 1 and 3 are presented in Table 13.4i. The figures for each system concept and metric have been obtained by averaging the results presented in the individual input papers. It can be seen that the requirements given in [4] are met, i.e. 2-3 times improvement in spectrum efficiency + +**Table 13.4i: UL spectrum efficiency performance for Case1 (500m ISD) and Case 3 (1732m ISD).** + +| | Case 1 | | Case 3 | | +|--------------------|---------------|--------|---------------|--------| +| | [bps/Hz/cell] | x UTRA | [bps/Hz/cell] | x UTRA | +| UTRA baseline | 0.332 | x1,0 | 0.316 | x1,0 | +| E-UTRA 1x2 | 0.735 | x2.2 | 0.681 | x2.2 | +| E-UTRA 1x4 | 1.103 | x3.3 | 1.038 | x3.3 | +| E-TURA 2x2 SU-MIMO | 0.776 | x2.3 | - | - | + +### 13.5.2 Fulfilment of downlink spectrum-efficiency target + +#### 13.5.2.0 Initial performance evaluation + +According to [4], the agreed target for the LTE radio-access concept in terms of downlink spectrum efficiency is 3-4 times gain vs. the baseline configuration defined in [4]. + +Multiple evaluations that directly evaluate the downlink system performance of the LTE concept vs. the baseline configuration have been carried out. The evaluations have been carried out by different sources/companies and for different scenarios, something that provides a certain degree of diversity in the evaluation results. + +Evaluations have been carried out both assuming that MIMO is used for the case of LTE and that MIMO is not used for the case of LTE. It should be pointed out that the use of MIMO for LTE is inline with the agreed assumptions in [4]. + +Assuming MIMO most evaluations indicate that the LTE concept fulfils or are within approximately 10% of the agreed spectrum-efficiency target, assuming a lower-speed (3 km/h) scenario. + +At higher UE speed (30 km/h), the performance gains are somewhat reduced which is also inline with the mobility requirement of [4], Clause 7.3. + +The system performance for VoIP traffic has also been evaluated, and VoIP capacity of more than 3 times versus the baseline configuration defined in [4] has been observed. + +Based on these evaluations one cannot directly conclude that the LTE concept fulfils the LTE downlink spectrum-efficiency target. However, these evaluations do not include all the features that are suggested to be part of the LTE radio-access concept, most notably different schemes for more advanced interference mitigation (e.g. interference coordination and/or cancellation) and variable TTI for overhead/delay optimization. Adding the potential gains of this to the above summarized gains would indicate that the LTE downlink radio-access concept can fulfil the agreed spectrum-efficiency targets. + +More information can be found in clause 10 of [2]. + +#### 13.5.2.1 Fulfilment of downlink spectrum-efficiency targets by enhancement techniques + +Multiple evaluations that directly evaluate the gains of downlink system performance of the LTE concept with enhancement techniques have been carried out. Specifically, the enhancement techniques are longer TTI, static interference coordination, interference cancellation adaptive antenna scheme and semi-static interference coordination have been carried out. The evaluations have been carried out by different sources/companies and for different scenarios, something that provides a certain degree of diversity in the evaluation results. Each technique can improve the spectrum efficiency by at least 10% or more. + +Without performing simulations including, at the same time, all these techniques it is somewhat difficult to conclude on exact cumulative gain figures for all the techniques. However it is likely that with these techniques included in LTE specification and implementation at least 3.5x gain in sector spectral efficiency can be achieved. There is the potential, considering some of the simulation results, that even higher gains could be achieved. + +Note that these gains can be achieved simultaneously with corresponding gains in user throughput, see subclause 13.4.2.1. + +More information can be found in clause 8 of [2]. + +#### 13.5.2.2 DL spectrum efficiency performance evaluation + +According to evaluation metric and assumption in [10], multiple evaluations that directly evaluate the downlink system performance of the LTE concept vs. the baseline configuration have been carried out. Efforts have been made to use realistic physical and link layer model. Further, fairness and coverage aspects are controlled through not only measuring average performance, but also cell-edge performance. The evaluations have been carried out by different sources/companies and for different scenarios, something that provides a certain degree of diversity in the evaluation results. Summaries of the results for simulation cases 1 and 3 are presented in Table 13.4j. For E-UTRA, results are presented both for the 2x2 (Ntx x Nrx antennas) reference configuration, as well as for the enhanced 4x2 and 4x4 configurations. The figures for each system concept and metric have been obtained by averaging the results presented in the individual input papers. It can be seen that the requirements given in [4] are met, i.e. 3-4 times improvement in spectrum efficiency + +**Table 13.4j: DL spectrum efficiency performance for Case 1 (500m ISD) and Case 3 (1732m ISD).** + +| | Case 1 | | Case 3 | | +|--------------------|---------------|--------|---------------|--------| +| | [bps/Hz/cell] | x UTRA | [bps/Hz/cell] | x UTRA | +| UTRA baseline 1x2 | 0,53 | x1,0 | 0,52 | x1,0 | +| E-UTRA 2x2 SU-MIMO | 1,69 | x3,2 | 1,56 | x3,0 | +| E-UTRA 4x2 SU-MIMO | 1,87 | x3,5 | 1,85 | x3,6 | +| E-UTRA 4x4 SU-MIMO | 2,67 | x5,0 | 2,41 | x4,6 | + +## 13.6 Mobility + +### 13.6.1 Features supporting various mobile velocities + +The E-UTRA supports seamless mobility across the cellular network; in RRC\_CONNECTED handovers are supported with resource preparations at the target cell, whereas in RRC\_IDLE the UE performs cell reselections and updates tracking areas. Inter-frequency mobility is also supported, hence making the E-UTRA flexible in supporting various deployment scenarios. + +The E-UTRA is capable of supporting various mobile velocities. The main features that support efficient data transmission at various speeds are listed below. + +- The subframe size of 0.5 ms makes the E-UTRA capable of adapting to fast changing radio link conditions and allows exploitation of multiuser diversity. +- The use of scheduled and diversity resource allocation in the frequency domain allows optimisation for various speeds, i.e., the diversity resource allocation increases frequency diversity gain at high speeds, whereas the scheduled resource allocation increases multiuser diversity gain at low speeds. +- The RLC and MAC (HARQ) status can be inherited at the target cell when the handover is intra-eNB. +- Forwarding of the data buffered in the source eNB to the target eNB prevents packet loss at handovers. +- The measurements for neighbour cells are performed without compressed mode, hence without wasting radio resources. The relevant measurements for neighbour cells that operate on a different carrier frequency from the currently served frequency, are performed during transmission/reception gaps provided by DTX/DRX, or by the packet scheduler. + +### 13.6.2 Assessment on U-plane interruption time during handover + +![Sequence diagram of intra-MME/UPE HO procedure in E-UTRAN showing U-plane interruption components.](9e4f582a5d5f6742d1372956db0f8f0b_img.jpg) + +The diagram illustrates the sequence of messages and processes during an intra-MME/UPE handover in E-UTRAN. The entities involved are UE, Source eNB, Target eNB, and MME/UPE. The diagram is divided into UL (Uplink) and DL (Downlink) sections. Four key interruption points are identified: + +- (a) Interruption due to radio L1/L2 layers:** This occurs when the UE sends an HO complete message to the Source eNB, and the Source eNB initiates DL synchronisation, Timing advance, and UL resource request/grant with the Target eNB. +- (b) Interruption due to UL RRC signalling:** This occurs when the UE sends an HO complete message to the Source eNB. +- (c) Interruption due to DL RRC signalling:** This occurs when the Target eNB sends an Ack message to the Source eNB. +- (d) Interruption due to path switch:** This occurs when the Target eNB sends a U-plane route update (Path switch) to the MME/UPE. + +The diagram also shows the flow of data forwarding (background process) from the Source eNB to the Target eNB, and the final state where data forwarding may continue even after the path switch, with forwarded data only being sent to the Target eNB. + +Sequence diagram of intra-MME/UPE HO procedure in E-UTRAN showing U-plane interruption components. + +**Figure 13.3: U-Plane interruption involved in the intra-MME/UPE HO procedure in E-UTRAN** + +The generic handover procedure assumed in E-UTRAN is shown in Figure 13.3, with associated delays encountered in the procedure. In the figure four constituents for the U-plane interruption are identified, i.e., (a) radio layer process, (b) UL RRC signalling, (c) DL RRC signalling, and (d) path switch. Each component is elaborated below. + +- Radio layer process (a) + +This is the delay between HO command to UL resource allocation, hence consisting of these elements: + +- 1) Frequency synchronization: The time taken for frequency synchronisation depends whether the target cell is operating on the same carrier frequency as the currently served frequency or not. However, this should be + +very small because the UE has already identified and measured the target cell. Thus, the UE should have somewhat recent frequency synchronization, and the delay caused by this element is then negligible. + +- 2) DL synchronization: It is thought that baseband and RF alignments may take some time. Although concrete evaluation was not performed, it was assumed that UE has acquired DL synchronisation to the target cell in conjunction with previous measurement and can relate the target cell DL timing to the source cell DL timing with an offset. Hence, the delay caused by this element should be less than 1 ms. +- 3) UL resource request and timing advance acquisition: This delay depends on the procedure applied: + - i) RACH procedure: Should the RACH procedure be applied, the RACH allocation in the cell would dictate how long the UE has to wait before getting the first opportunity to send a RACH message and the possible need for resending. This is a fallback option for cases where non-contention based access (option ii) below) fails or is not possible. + - ii) Dedicated RACH preamble procedure: Should the RACH procedure be applied, the RACH allocation in the cell would dictate how long the UE has to wait before getting the first opportunity to send a RACH message and the possible need for resending due to e.g. power ramping. + +Some details as to the timing of the RA response remain to be settled. Reasonably accurate estimates of the delay for UL resource request and timing advance acquisition can however be provided as follow. For method i) (worst case), if no retransmission is needed, the delay consists of (1) waiting for an access slot for the preamble, (2) transmission of the RA preamble, and (3) waiting for the decoding of the RA response which contains timing advance information and UL resource allocation for the HO complete message. The mean time of (1) could be 2.5 ms (assuming two access slots in 10 ms). The duration of (2) depends on the deployment scenario (e.g. ISD), but a common value is 1 sub-frame, i.e. 1ms. The delay (3) from the end of the preamble transmission to having decoded the RA response is eNB implementation dependent, but 7.5ms is considered feasible (items 3 + 4 in C-plane latency assessment). These numbers result in a mean delay of 11 ms from the moment that the UE has synchronized to the downlink to the moment that an UL grant has been received. . A retransmission of the preamble adds to the delay at least one RTT or the access slot separation, whichever is longer. A random back-off system may also be employed, which implies that the mean delay for a retransmission is larger than the access slot separation. Various proposals for how the initial random waiting time can be reduced or avoided have been made, but are not considered in this analysis. + +NOTE: If SFN would be required, it can be provided either in the HO command or by UE reading it from broadcasted System Information. + +- RRC signalling (b), (c) + +The detailed relation between RRC signalling and pausing/resuming of the U-plane is yet to be concluded. + +For contention based access (method i), this evaluation assumes that resuming of the U-plane is triggered by RRC signalling, i.e., the HO complete triggers resuming of the DL U-plane in the target eNB, whereas the HO complete ack triggers resuming of the UL U-plane. The delay represented in this component includes the time taken to encode the RRC message at the transmitter, the time taken to transmit the message over the radio interface, and the time required to process the message at the receiver. Of the three, the time taken to transmit over the radio interface is thought to be the dominant factor. This delay can be reduced by scheduling the message at a high priority and by using a low error rate transport format. In the optimal case, this delay is expected to be approximately 5 ms, but could end up significantly longer, e.g. 20 ms, due to HARQ/ARQ. Analogous to the C-plane latency assessment, we here assume a 30% HARQ retransmission, which with a HARQ RTT of 5 ms corresponds to an average additional delay of 1.5 ms. + +NOTE: For time critical messages such as RRC signalling at HO, 30% HARQ retransmission is considered a pessimistic assumption. + +For non-contention based access (method ii), U-plane transmissions can possibly be resumed before RRC signalling is completed since the UE and its arrival is uniquely identified to the network by the preamble itself and successful access is acknowledged to the UE by the RA response. Hence, for non-contention based access , UP delay due to RRC signalling can be avoided if there is no need for eNB to receive HO COMPLETE before continuing U-plane transmission. + +- Forwarding delay at path switch (d) + +Packets sent to the source eNB just before the switching in the GW experience additional transport delay to the target-eNB because they are routed via the source eNB. However this delay does not generally result in an increase of handover interruption time if there is other data available to transmit. Worst case is when there is only 1 packet to transmit to the UE around the handover and this packet is just sent to the source-eNB when the GW decides to switch. Assuming that S1 delays to source eNB and target eNB are similar, this packet will experience an additional delay from source eNB processing and X2 transport delay. I.e., the patch switch + +According to this model, the total interruption time of the U-plane in the UL is (a) + (b) + (c), whereas the interruption in the DL is (a) + (b) or (d), whichever is larger. Note that if forwarded packets are available in the target eNB before path switch, the total interruption time in the DL would be (a) + (b). The forwarding can continue even after the path switch, depending on the amount of data that had to be forwarded and the transmission rate over the inter-eNB interface. However, what is essential is the delay for the first forwarded packet to arrive at the target eNB, as the target eNB can then resume transmission as soon as the radio layer is ready, receiving the HO complete. It is generally assumed that the forwarding delay (of the first packet) is smaller than the radio layer delay (a) + (b). + +**Table 13.5: U-Plane interruption components and estimates** + +| | Component | Cause | Estimate [ms]
(contention based) | Estimate [ms]
(contention-free) | +|-----|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|-------------------------------------------| +| (a) | Radio layer process |
  • - DL synchronization time, including e.g., baseband and RF switching time
  • - UL resource request and timing advance acquisition
  • - UL resource granting
| 12 ± 2.5 | 12 ± 2.5 | +| (b) | UL RRC signaling |
  • - RRC message encoding at the transmitter
  • - RRC transmission over the radio
  • - RRC processing time at the receiver
| 6.5 | 0 | +| (c) | DL RRC signaling |
  • - RRC message encoding at the transmitter
  • - RRC transmission over the radio
  • - RRC processing time at the receiver
| 6.5 | 0 | +| (d) | Forwarding delay |
  • - Source eNB processing
  • - Packet transmission over the X2 interface
| 5 | 5 | + +Table 13.5 shows the estimated mean value for each delay component assuming an FDD frame structure. The total average interruption time are estimated as below: + +Contention-based access: + +- UL interruption time = 25 ms +- DL interruption time = 18.5 ms. + +Contention-free access: + +- UL interruption time = 12 ms +- DL interruption time = 12 ms. + +Note that these estimates may vary depending on the detailed procedures that are yet to be decided. Depending on how U-plane data forwarding is done between the source and target eNBs, the U-plane interruption time seen by the application layer may be increased due to possible duplicate transmissions of the forwarded data from the target eNB. However, in a typical case the U-plane interruption time is unlikely to exceed 100 ms. On the optimistic end, interruption times below as 12 ms are possible. + +The time spent between the instance when the UE decides to transmit the measurement report and the UE receives the HO command does not contribute to the U-plane interruption. However, this delay is also expected to be kept within a bearable limit in order to avoid radio link loss between the UE and eNB, and to avoid impact on capacity. + +### 13.6.3 Means to minimise packet loss during handover + +As a means to minimise packet loss during handover, packet forwarding from the source eNB to the target eNB is supported using the X2 interface. When the handover does not incur change of the serving eNB, the RLC and MAC status can be inherited after the handover. If the handover involves change of the serving eNB, packets that are buffered in the source eNB are forwarded to the target eNB via the X2 interface. Hence, packet loss due to handover can be avoided. The forwarding may take place in a service dependent and implementation specific manner [6]. + +## 13.7 Coverage + +The requirements on coverage as fulfilling requirements on user throughput, spectrum efficiency and mobility cases is defined in [4]. It is also defined in [4] that LTE operation should not be precluded even in very large cells (up to 100 km). + +### System performance at larger cell size + +The simulation cases defined in [2] covers cell ISD up to 1732 m. The fulfilment of the spectral efficiency and user throughput targets are discussed in Clause 13.5 and 13.4 respectively. This discussion is based on a number of diverse evaluation results submitted by a number of companies. A sub-set of these evaluation results also include evaluation for larger cell size up to an inter-site distance of 7500 m and a cell radius of 5000 m. These evaluations indicates that the relative gains in LTE system performance vs. the baseline configuration defined on TR25.912, for this larger cell ranges, are in the same order as or only somewhat lower than the corresponding gains for the smaller cell ranges (1732 m). + +### Operation in very large cell sizes + +TR25.913 [2] specifies that LTE operation should be possible with cell sizes up to 100 km. It should be noted that [2] explicitly points out that high performance is not expected in such extreme cases. + +One function that may limit the cell size is the random-access procedure. However, the support for very large cell size has been taken into account as part of the random-access procedure with the support of an adjustable random-access-burst length, see [2] clause 9.1.2.1.1.1 + +In case of TDD mode of operation ,an additional critical aspect is the timing advance at the transmitter side, in order to time-align reception/transmission at the corresponding receiver side. This is enabled by the possibility for a variable number of idle symbols at the downlink/uplink switching point, see [2] clause 6.2.1. In case of very large cells, a larger number of idle symbols may be needed which may lead to a large efficiency loss in case of frequent downlink/uplink switching points, e.g. every sub-frame. However, in very-large-cell scenarios, very low round-trip time is of less importance and this less frequent downlink/uplink switching points can be applied, implying less overhead due to idle symbols. Thus, at least in this respect, also LTE TDD supports very large cell sizes. + +## 13.8 Support for point to multipoint transmission + +It was found that E-UTRA point to multipoint transmission can be specified such that the corresponding requirements outlined in [4] can be met or exceeded. + +The study confirmed the feasibility of efficiently multiplexing point to point and point to multi-point transmissions over the same physical channel structure thus allowing for simultaneous support of unicast and multicast services in the UE with minimum additional receiver complexity compared to UE supporting unicast services only. Such a structure also allows for the operation of point to multipoint transmissions on a separate carrier when there is a need for higher capacity as could be the case when offering mobile TV services. + +The study found that with E-UTRA it would be feasible to operate point to multipoint transmissions as a single frequency network and benefit from energy combining without experiencing inter-cell interference; this is feasible provided that the cells are synchronized within a few micro seconds, that the OFDM symbol cyclic prefix duration is long enough compared to the time difference between the signals received from multiple cells; this also requires that the channel structure is such that at known time instants the exact same signal is transmitted from a cluster of neighboring cells; the UE will then receive the signals from multiple cells as if they were transmitted from a single cell; the interference contribution therefore only results from thermal noise and interference from cells not in the multicast cluster or cells which timing is significantly outside of the cyclic prefix. This mode of operation is often referred to as single frequency network (SFN) and is used in state of the art digital broadcast systems. E-UTRA would still allow point to multipoint transmission within a cluster of asynchronous cells. Four cases are identified depending on the network synchronization and content transmission: + +- Transmission with synchronous cells + - Cell common point to multipoint transmission + - E-UTRA provides significant improvements over Rel-6 MBMS (see Table 13.8-1) + - Cell specific point to multipoint transmission + - This scenario has not been fully evaluated but no significant gain is expected over Rel-6 MBMS. +- Transmission with asynchronous cells + - Cell common point to multipoint transmission + - E-UTRA is expected to perform worse than Rel-6 MBMS with combining of multiple cells. This assumes that for E-UTRA the UE would not support simultaneous data reception from multiple asynchronous cells. + - Cell specific point to multipoint transmission + - This scenario has not been fully evaluated but no significant gain is expected over Rel-6 MBMS. + +### 13.8.1 Initial performance evaluation + +Table 13.6 provides a summary of the expected spectral efficiency of synchronized multi-cell point to multi-point transmission (i.e. SFN operation). The actual efficiency is directly related to the C/I at the edge of the cell and therefore highly sensitive to the maximum cell transmit power, the propagation loss (site distance, frequency band) and the cyclic prefix duration. The corresponding E UTRA requirements have to be clarified in order to proceed with the selection of the proper cyclic prefix duration for point to multipoint transmission. + +**Table 13.6: Spectral efficiency of SFN multicast for E-UTRA** + +| Case | Band (MHz) | Site to site distance (m) | Speed (kph) | SFN Multicast
1% BLER, 95% coverage
(Mbps) | +|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-------------|--------------------------------------------------| +| 1 | 2000 | 500 | 3 | > 5.5 (1.1 b/s/Hz) | +| 2 | 2000 | 500 | 30 | > 5.5 (1.1 b/s/Hz) | +| 3 | 2000 | 1732 | 3 | < 2.5 (0.5 b/s/Hz) | +| 4 | 900 | 1000 | 3 | > 5.5 (1.1 b/s/Hz) | +| Note: | 5 MHz allocation, all cell resource assigned to multicast services, reference signal overhead is accounted for, any other control channel overhead is not accounted for. | | | | + +Additional details can be found in [5] and in clauses 7.1.1.6 and 8.1.3 of [2]. + +### 13.8.2 MBSFN performance evaluation + +According to evaluation metric and assumption in [10], multiple evaluations that directly evaluate the uplink system performance of the LTE concept vs. the baseline configuration have been carried out. Efforts have been made to use realistic physical and link layer model. Further, fairness and coverage aspects are controlled through not only measuring average performance, but also cell-edge performance. The evaluations have been carried out by different sources/companies and for different scenarios. For both the baseline UTRA and E-UTRA results, the spectrum efficiency figures match well between companies. Summaries of the results for simulation cases 1 - 4 are presented in Table 13.7. The figures for each system concept and metric have been obtained by averaging the results presented in the individual input papers. + +**Table 13.7. Summary of MBSFN performance** + +| Deployment | Spectrum Efficiency
[bps/Hz] | Inter-site Distance @ 1bps/Hz
[m] | +|------------|---------------------------------|--------------------------------------| +| Case 1 | 3.13 | 1619 | +| Case 2 | 3.02 | 2310 | + +| | | | +|--------|------|------| +| Case 3 | 0.99 | 1619 | +| Case 4 | 3.18 | 4375 | + +## 13.9 Network synchronisation + +The E-UTRAN design principle has been the use of an asynchronous network in case of FDD operation, i.e. in general case, tight inter-cell synchronisation is not required to provide good system performance and synchronisation is not assumed in any basic procedures like cell search, though some of the proposed methods for inter-cell interference mitigation assume synchronisation. + +However, for the special case of providing multi-cell MBMS/Broadcast service there is a clear gain with tight inter-cell synchronization as this allows for an efficient and low-complexity combining of multiple cells. In the case of allocation of a separate carrier for MBMS, fewer sites can be used for MBMS and only those sites that are part of MBMS SFN need to be synchronised. + +Furthermore, in case of TDD mode of operation, the network is expected to be deployed with tight inter-cell synchronization, similar to the UTRAN TDD mode of operation in order to avoid UE to UE (and eNB to eNB) interference. In this case the timing requirements might not be as tight as with the MBMS multi-cell reception, with the details depending on solutions derived. + +In the uplink direction timing advance is assumed to be used, thus effectively synchronising the signals received from the terminals inside one cell as observed at the eNB. This allows to make use of a TDMA/FDMA component in uplink for resource division (without excessive "guard intervals" between different transmissions). The exact requirements for this synchronisation would be related to the physical layer parameterisation, mainly the duration of the cyclic prefix in the uplink direction. + +The synchronisation methods for consideration are external timing sources like, e.g. satellite based timing source (GNSS) or then one could consider various methods, especially with TDD, of "self synchronisation" similar to the methods that have been discussed in 3GPP during UTRAN TDD development. Synchronisation techniques could also use the observation of neighbour cell signals by UEs. More studies are required for the assessment of synchronisation techniques. + +The handover in E-UTRAN is a hard handover and has not been identified to be causing any additional requirements to the timing synchronisation between sites. Frequency synchronisation is helpful though to avoid drifting of relative timings and ease neighbour cell acquisition. This does however not necessarily require any explicit synchronisation but is implicitly provided by a good eNB frequency stability as already used e.g. in GSM or UMTS. + +## 13.10 Co-existence and inter-working with 3GPP RAT + +The U-plane interruption time is a part of the U-plane transient period, which is the time between the reception of the HO command in UE and the U-plane route update. The HO preparation period does not contribute to the U-plane interruption time. + +Based on the analysis of the U-plane transient period, the total interruption time is expected to be lower than the requirement for inter-RAT handover, even in the case of inter-RAT HO from LTE to 2G/3G. The data forwarding time is expected not to affect the total DL interruption time. + +Note : See clause 6.18.1 in [6] for detailed analysis. + +## 13.11 General requirements + +### 13.11.1 Cost related requirements + +Following cost-related requirements have been identified in clause 12.1 of [4]. For each requirement it is shortly discussed how it is fulfilled by the LTE architecture. + +- Backhaul communication protocols should be optimized. + +The RNL communication was designed to get along with minimum number of communication steps for call setup and mobility. S1 and X2 interface are designed to operate and to be configured in a uniform way. + +- b) The E-UTRAN architecture should reduce the cost of future network deployment whilst enabling the usage of existing site locations. + +It is expected that the reduction of the number of nodes and interfaces contributes to this overall goal. + +- c) All the interfaces specified shall be open for multi-vendor equipment interoperability. + +Two interfaces, S1 and X2 are identified and will be standardized. There are no major problems regarding multi-vendor interoperability identified during the study item phase. + +- d) UE complexity and power consumption shall be minimized/optimized. Complicated UTRAN architecture and unnecessary interfaces should be avoided. + +Regarding the UE complexity requirement, see chapter 12.3. Regarding UTRAN architecture and interface, see chapter 9.8. + +- e) More efficient and easy to use OAM&P. + +This specific aspect needs to be covered when specifying stage 3. + +### 13.11.2 Service related requirements + +Following service-related requirements have been identified in clause 12.2 of [4]. It can be seen that many features related to these requirements are captured as the system concepts. + +The E-UTRA should efficiently support various types of service. These must include currently available services like web-browsing, FTP, video-streaming or VoIP, and more advanced services (e.g. real-time video or push-to-x) in the PS-domain. + +VoIP should be supported with at least as good radio, backhaul efficiency and latency as voice traffic over the UMTS CS networks. + +Lossless HO with the forwarding technique can be applied and this can be useful for data communications. Header compression is supported as well as Release 6 and this can be useful for efficient support of low rate services, e.g. VoIP. U-plane latency is evaluated and evaluation results show that Evolved UTRAN and UTRAN can support real-time services. + +High-level QoS signalling concept is studied and concluded in clause 9.6. + +Support of voice traffic over the UMTS CS networks is studying in the SAE Work Item. + +## 13.12 VoIP performance evaluation + +According to evaluation metric and assumption in [10], multiple evaluations that directly evaluate the uplink system performance of the LTE concept vs. the baseline configuration have been carried out. Efforts have been made to use realistic physical and link layer model. Further, fairness and coverage aspects are controlled through not only measuring average performance, but also cell-edge performance. The evaluations have been carried out by different sources/companies and for different scenarios. For both the baseline UTRA and E-UTRA results, the spectrum efficiency figures match well between companies. Summaries of the results for simulation cases 1 - 3 are presented in Table 13.8. The figures for each system concept and metric have been obtained by averaging the results presented in the individual input papers. + +**Table 13.8: Summary of UL and DL VoIP Capacity** + +| Deployment Scenario | Average VoIP Capacity (users/sector) | | +|---------------------|--------------------------------------|-----| +| | DL | UL | +| Case1 | 317 | 241 | +| Case2 | 293 | - | +| Case3 | 289 | 123 | + +# 14 Conclusions and Recommendations + +## 14.1 Conclusions + +During the study of Evolved UTRA and UTRAN, many proposals on physical and higher layer radio protocols, NW architecture, RF related issues, complexity, etc were treated and studied System concepts which can meet the requirements in [1] were described based on agreed key solutions captured in this TR comprising.: + +- OFDMA and SC-FDMA for downlink and uplink radio access schemes, respectively +- Support for time and frequency domain scheduling +- Simple channel structure for point to point and point to multipoint transmission +- Simple RRC state model (idle and connected) +- Reduced number of transport channels (no need for dedicated channels) +- Simplified MAC solutions ( # of MAC entities, common solution for DRX and DTX cases). Scheduling, ARQ and HARQ provided by RLC and MAC sublayers terminated in UE and eNB +- Header compression and ciphering provided by PDCP sublayer terminated in UE and aGW +- No compressed mode: transmission/reception gaps for measurement provided by scheduling +- A cell transmits one set of common channel information in a bandwidth equal than or less than the UE minimum bandwidth capability +- Simplified E-UTRAN architecture (only one type of nodes: eNB) +- Hard handover with downlink data forwarding on SDU level +- Distributed NW architecture, i.e. RRC and outer ARQ in the eNB +- NAS, terminated in UE and aGW, provides idle mode mobility handling +- NAS-related UE identities similar to 2G or 3G (IMSI/IMEI, TMSI for MME) +- Resource aggregation is only considered for broadcast-type services. + +The system concepts were evaluated against the targets or requirements defined in [4]. The evaluation-results shown in this TR demonstrate that the system concepts can meet most of the requirements as follows. + +- The LTE concept has the potential to fulfil both the system capacity and user throughput targets +- Evaluated uplink peak data rate is a bit smaller than the requirements, however, it is expected that the peak data rate can be increased by some optimisations, e.g. higher TTI values and/or by reducing the amount of control signaling information. +- It was confirmed that the requirements of C-plane and U-plane latency can be satisfied. +- Fulfilments without any issues are identified for requirements on deployment scenarios, spectrum flexibility, interworking, mobility, E-UTRAN architecture and RRM. +- Regarding system and device cost and complexity work needs to continue in the future. As evolved UTRA and UTRAN system will provide significantly higher data rates than Release 6 WCDMA and, as a consequence hereof, the physical layer complexity will increase accordingly compared to lower-rate systems. This complexity is not seen as evolved UTRA and UTRAN specific, but is similar to the complexity experienced in any high data rate system. + +According to these evaluation results, it can be concluded that system concepts captured in this TR are feasible for evolved UTRA and UTRAN. + +## 14.2 Recommendations + +It is recommended to create Work Items on evolved UTRA and UTRAN. The system concept captured in this TR should be starting points for the Work Item. + +# Annex A (informative): Change History + +**Table A.1: Change History before approval** + +| Date | TSG # | TSG Doc. | Subject/Comment | Old | New | +|---------|--------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------| +| 2005-12 | RAN-30 | | Text proposals approved in RAN#30 were added in clause 7 and 9 | 0.0.0 | 0.0.2 | +| | RAN-30 | | Reference [2] added | 0.0.2 | 0.0.3 | +| 2006-3 | RAN-31 | | Text agreed in the RAN2-RAN3-SA2 joint meeting was added in clause 9 | 0.0.3 | 0.0.4 | +| | RAN-31 | | RP-060122 and RP-060171 were captured according to agreements in RAN#31 | 0.0.4 | 0.1.0 | +| | RAN-31 | | A sentence in 9.3.2 was deleted according to decision in RAN#31.
Note 1 in clause 9.4.2.2.1 was corrected for alignment with the RAN#31 decision on the RRC termination point. | 0.1.0 | 0.1.1 | +| | RAN-31 | | Editorial corrections.
New clauses are added for system concept evaluations.
Responsible WGs are clarified. | 0.1.1 | 0.1.2 | +| 2006-5 | RAN-31 | | R3-060512, R3-060516 and R3-060519 were captured according to agreements in RAN3#51bis. | 0.1.2 | 0.1.3 | +| | RAN-31 | | Documents which were agreed in RAN1#45, RAN2#53, RAN3#52 and RAN4#39 were captured. (documents to be approved in email discussion are not included) | 0.1.3 | 0.1.4 | +| | RAN-31 | | Documents which were agreed in RAN1#45, RAN2#53, and RAN3#52 were captured (including documents approved by email). | 0.1.4 | 0.1.5 | +| | RAN-31 | | Text proposals agreed on RAN2, RAN3 reflectors were captured. Some clean-up for e.g. removal of FFS, terminology alignment, were made. Abbreviation was added. | 0.1.4 | 0.1.5 | +| | RAN-31 | | Text proposals agreed on RAN1 reflector were captured. | 0.1.5 | 0.1.6 | +| 2006-6 | RAN-32 | RP-060388 | Editorial correction | 0.1.6 | 0.1.7 | +| | RAN-32 | RP-060430 | Conclusion and recommendation were included.
Submission for approval | 0.1.7 | 0.2.0 | +| | - | - | Approved at TSG-RAN #32 and placed under Change Control | 0.2.0 | 7.0.0 | + +**Table A.2: Change History after approval** + +| Change history | | | | | | | | +|----------------|--------|-----------|------|-----|--------------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 09/2006 | RP-33 | RP-060515 | 0001 | | Bearer and C-plane establishment | 7.0.0 | 7.1.0 | +| | RP-33 | RP-060531 | 0002 | | Summary of downlink enhancement techniques over reference LTE unicast | 7.0.0 | 7.1.0 | +| 06/2007 | RP-36 | RP-070433 | 0003 | 1 | LTE performance evaluation results | 7.1.0 | 7.2.0 | +| 12/2008 | RP-42 | | | | Upgrade to Release 8 with no technical change | 7.2.0 | 8.0.0 | +| 09/2009 | RP-45 | | | | Upgrade to Release 9 with no technical change (for LTE-Advanced reference in 36.912) | 8.0.0 | 9.0.0 | +| 03/2011 | RP-51 | | | | Upgrade to Release 10 with no technical change | 9.0.0 | 10.0.0 | +| 09/2012 | RP-57 | | | | Upgrade to Release 11 with no technical change | 10.0.0 | 11.0.0 | +| 09/2014 | RP-65 | | | | Upgrade to Release 12 with no technical change | 11.0.0 | 12.0.0 | +| 12/2015 | RP-70 | | | | Upgrade to Release 13 with no technical change | 12.0.0 | 13.0.0 | +| 03/2017 | RP-75 | | | | Upgrade to Release 14 with no technical change | 13.0.0 | 14.0.0 | +| 06/2018 | RP-80 | | | | Upgrade to Release 15 with no technical change | 14.0.0 | 15.0.0 | +| 2020-07 | RP-88e | - | - | - | Upgrade to Release 16 with no technical change | 15.0.0 | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/25_series/25914/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg b/marked/Rel-16/25_series/25914/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8cd157279b13aedb58119d37ad034c9011351d4 --- /dev/null +++ b/marked/Rel-16/25_series/25914/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9eca4998ef424772878be125c4f151b6deb7c356e254dec76fda2456fd18d09c +size 15263 diff --git a/marked/Rel-16/25_series/25914/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg b/marked/Rel-16/25_series/25914/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b012fecc98b7abbe0549ada2c74cbe49450f3f8c --- /dev/null +++ b/marked/Rel-16/25_series/25914/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af781341d0250813f4c34ced36dfdba82332ac249f674132638de12be29e79b6 +size 78455 diff --git a/marked/Rel-16/25_series/25914/0a3ab80d35c138cc4038b5758f6ff34d_img.jpg b/marked/Rel-16/25_series/25914/0a3ab80d35c138cc4038b5758f6ff34d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..083c7a237366c4ae601dcb84c584c319b8896c04 --- /dev/null +++ b/marked/Rel-16/25_series/25914/0a3ab80d35c138cc4038b5758f6ff34d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf8c49b33238a7f72b0f75ec6e8caa242bac7d33eb4de0ac42b99cc314702e6d +size 38673 diff --git a/marked/Rel-16/25_series/25914/0aa15f5c9c3edae230985491199cfe8b_img.jpg b/marked/Rel-16/25_series/25914/0aa15f5c9c3edae230985491199cfe8b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6590381de83b3b1b3142b8bd1ccc498fac0a804e --- /dev/null +++ b/marked/Rel-16/25_series/25914/0aa15f5c9c3edae230985491199cfe8b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11804c923000774e43decd58de0a46da5cd33806e71976d95ecac6751cebd59c +size 54604 diff --git a/marked/Rel-16/25_series/25914/1e9fc8e561a3ee72410680d44728ba60_img.jpg b/marked/Rel-16/25_series/25914/1e9fc8e561a3ee72410680d44728ba60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..329d158cfb53cf56006356a65ea35f6b71bae697 --- /dev/null +++ b/marked/Rel-16/25_series/25914/1e9fc8e561a3ee72410680d44728ba60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:710e407199facf9409f07b69809435060d7bd7107f038699097f41a9befd2d72 +size 9651 diff --git a/marked/Rel-16/25_series/25914/20ab59bc10b900f6cf8a34549848bbf4_img.jpg b/marked/Rel-16/25_series/25914/20ab59bc10b900f6cf8a34549848bbf4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec440f5a0c384c980e886594423001ce625fe591 --- /dev/null +++ b/marked/Rel-16/25_series/25914/20ab59bc10b900f6cf8a34549848bbf4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9547e215ce6ec82991c84ef7408f9dcdf790aeace0aec4a94609cdc455d98222 +size 23135 diff --git a/marked/Rel-16/25_series/25914/2224b82995b3ba31aa82f20fb06f4c9c_img.jpg b/marked/Rel-16/25_series/25914/2224b82995b3ba31aa82f20fb06f4c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c78c78a88dc8b187c86da3cd85f1d840b7382600 --- /dev/null +++ b/marked/Rel-16/25_series/25914/2224b82995b3ba31aa82f20fb06f4c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2d8bf759cffd650fc99fb9f03492858817467a39df3f5ef0a224d63931bebe3 +size 14920 diff --git a/marked/Rel-16/25_series/25914/26070f41b834cefd33d293fecdba9868_img.jpg b/marked/Rel-16/25_series/25914/26070f41b834cefd33d293fecdba9868_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d661acb6116aaab82125ff66c7c9c4a20f29e07 --- /dev/null +++ b/marked/Rel-16/25_series/25914/26070f41b834cefd33d293fecdba9868_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf93630b492deb9a44b8ab1338234cf8b7763068801cfc91de726b2fd0d24719 +size 8661 diff --git a/marked/Rel-16/25_series/25914/30ca9a81da047d57fa881b632aaca2d8_img.jpg b/marked/Rel-16/25_series/25914/30ca9a81da047d57fa881b632aaca2d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0704b26083faf67f1e8eb573869676987243d8ff --- /dev/null +++ b/marked/Rel-16/25_series/25914/30ca9a81da047d57fa881b632aaca2d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8fe569f1315c5064bac2f04f2dc55e11fd88eb38ed9bc4a634262bf18c207526 +size 19706 diff --git a/marked/Rel-16/25_series/25914/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-16/25_series/25914/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a34b3f6eaff63d5415e8a05f42064d4421dec4aa --- /dev/null +++ b/marked/Rel-16/25_series/25914/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85c418305b5974783aaffc63877b606c6f068f5be436aa93a6ac9a1fb38f3c07 +size 10858 diff --git a/marked/Rel-16/25_series/25914/3d7e0eb9c7e514f3026945a039354da4_img.jpg b/marked/Rel-16/25_series/25914/3d7e0eb9c7e514f3026945a039354da4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..026bfea5fd7d24b87203892a52af42bb178c40d3 --- /dev/null +++ b/marked/Rel-16/25_series/25914/3d7e0eb9c7e514f3026945a039354da4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b7f7559a0d498ce7d8af1532c38fa87226d80b4661b6fe1b09f69b15197d730 +size 96023 diff --git a/marked/Rel-16/25_series/25914/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/Rel-16/25_series/25914/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e154386ff8d38984b1a51780cf44d75b51340c7e --- /dev/null +++ b/marked/Rel-16/25_series/25914/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69daf81b36cf7eb071dc8502e68d24ac183e303d5ebe4d14cd6432cdd2f1d5ef +size 41126 diff --git a/marked/Rel-16/25_series/25914/4aeaa51a3999fab21171224e238cb571_img.jpg b/marked/Rel-16/25_series/25914/4aeaa51a3999fab21171224e238cb571_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e999aff237ed29fd28aafe7406521f1f281f724a --- /dev/null +++ b/marked/Rel-16/25_series/25914/4aeaa51a3999fab21171224e238cb571_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1fe62eb7c63633dcf42921ce433b28099530830231fbcc2c67e13e26b744c1fa +size 42766 diff --git a/marked/Rel-16/25_series/25914/52e112d1ba42a3c660bf62a0fea927d3_img.jpg b/marked/Rel-16/25_series/25914/52e112d1ba42a3c660bf62a0fea927d3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa0c50f68cfd126db61d114be333661eba5675d2 --- /dev/null +++ b/marked/Rel-16/25_series/25914/52e112d1ba42a3c660bf62a0fea927d3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb44ee2d2b423f4a2c57b34cd3406da9d475df05d631fe1cc4109bc1c9a09570 +size 72375 diff --git a/marked/Rel-16/25_series/25914/53cb558495f8cc93c4202314ef492966_img.jpg b/marked/Rel-16/25_series/25914/53cb558495f8cc93c4202314ef492966_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63ed0ec67291dfdd0c93f66020a58ab67d6278a9 --- /dev/null +++ b/marked/Rel-16/25_series/25914/53cb558495f8cc93c4202314ef492966_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84ba22df69c013c0f8fb2afe7998c5edad34949b4786b8b9d62a594a796bf8ee +size 9574 diff --git a/marked/Rel-16/25_series/25914/555df5c0300cb1fca5dc028fec5ec6be_img.jpg b/marked/Rel-16/25_series/25914/555df5c0300cb1fca5dc028fec5ec6be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d1624e0916c62700bb274f39f63237ef2f4d752 --- /dev/null +++ b/marked/Rel-16/25_series/25914/555df5c0300cb1fca5dc028fec5ec6be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b27ebcec47737588fc68173d56b06a76331aa2976b9a931115f11068666d8de0 +size 15424 diff --git a/marked/Rel-16/25_series/25914/557e5e0f7f146f1c887e9c15bf1654a3_img.jpg b/marked/Rel-16/25_series/25914/557e5e0f7f146f1c887e9c15bf1654a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ce9439a4e4bc747da7b452b7bff3928bd06a150 --- /dev/null +++ b/marked/Rel-16/25_series/25914/557e5e0f7f146f1c887e9c15bf1654a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d3a1824b6855734e29c5510cd5e0eaf8b2edb8e3405588b13b7b526558b5459 +size 70607 diff --git a/marked/Rel-16/25_series/25914/5a2d10b858b621236f708a5f5fa1ed88_img.jpg b/marked/Rel-16/25_series/25914/5a2d10b858b621236f708a5f5fa1ed88_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1c1db06c71b328e0e1ceb8cb56907a78f536ef7 --- /dev/null +++ b/marked/Rel-16/25_series/25914/5a2d10b858b621236f708a5f5fa1ed88_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:130b57992da1453a1cba161126e22b0bae2f2d2981b4253f0c25cdc6fa2df688 +size 23096 diff --git a/marked/Rel-16/25_series/25914/5cf80bac69830ea773ac17c87e0ae24d_img.jpg b/marked/Rel-16/25_series/25914/5cf80bac69830ea773ac17c87e0ae24d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1ec556407fa522c8e132b9642904d19f62450c6 --- /dev/null +++ b/marked/Rel-16/25_series/25914/5cf80bac69830ea773ac17c87e0ae24d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7586ca26208a59afd5d22387526f0512c43f429d10a33aa729abae737282c38e +size 37580 diff --git a/marked/Rel-16/25_series/25914/6cc4a2d5ea0462e4825d57bd689bd2b3_img.jpg b/marked/Rel-16/25_series/25914/6cc4a2d5ea0462e4825d57bd689bd2b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dcbbb2f80ed4f3f94cee17a76615eabb3b22b66e --- /dev/null +++ b/marked/Rel-16/25_series/25914/6cc4a2d5ea0462e4825d57bd689bd2b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49c579d914c3706161721ff1cf5f2bdf54f32fbffab6154b3e775600e32e85ef +size 47534 diff --git a/marked/Rel-16/25_series/25914/78de09c382ab51b5c3e87979204228c8_img.jpg b/marked/Rel-16/25_series/25914/78de09c382ab51b5c3e87979204228c8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1018f940dddd8ef54564a5fb200bc28763a7a88 --- /dev/null +++ b/marked/Rel-16/25_series/25914/78de09c382ab51b5c3e87979204228c8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7b607d127e7f3264f1badb8504fbfd99fc21823fb730c33a6682e7ce023e36c +size 36023 diff --git a/marked/Rel-16/25_series/25914/7a0eb8f3965b07bfadffaf8dbec102ef_img.jpg b/marked/Rel-16/25_series/25914/7a0eb8f3965b07bfadffaf8dbec102ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..083c0dc53f125559113f2e0620fb6177ed4542c2 --- /dev/null +++ b/marked/Rel-16/25_series/25914/7a0eb8f3965b07bfadffaf8dbec102ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:218231cd68bbfecd0df1c35297e989db641640925bc1fa0f4ccda332ea3fa5b4 +size 17558 diff --git a/marked/Rel-16/25_series/25914/7bf4ae6f6e514c657b55be6302e3c7a4_img.jpg b/marked/Rel-16/25_series/25914/7bf4ae6f6e514c657b55be6302e3c7a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9fd0b85920df73cf0b50f3c68790a3dcf1ef2ea0 --- /dev/null +++ b/marked/Rel-16/25_series/25914/7bf4ae6f6e514c657b55be6302e3c7a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f1a72f6a5574228c0bcb5ac0237b2013e63e0964f618f60be0760b01e4df859 +size 66131 diff --git a/marked/Rel-16/25_series/25914/7c07d25bb7b912053d0beb7ef9c41e91_img.jpg b/marked/Rel-16/25_series/25914/7c07d25bb7b912053d0beb7ef9c41e91_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85c68b75190fcadac5bf44d60b8362e27351ec76 --- /dev/null +++ b/marked/Rel-16/25_series/25914/7c07d25bb7b912053d0beb7ef9c41e91_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d68cacf19d850deec30ebca2b2a0104ab5a4a01ad5483ee8bf691053f05e2320 +size 43224 diff --git a/marked/Rel-16/25_series/25914/7d066b8cdb123b3cba3584e8bb66f557_img.jpg b/marked/Rel-16/25_series/25914/7d066b8cdb123b3cba3584e8bb66f557_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0abd116bf142bf2db7580743134fc89c7a4e8de --- /dev/null +++ b/marked/Rel-16/25_series/25914/7d066b8cdb123b3cba3584e8bb66f557_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c84dedd87cea46a0b6453ea3713a664d313ceec794794e5bff508ca3082e203 +size 54254 diff --git a/marked/Rel-16/25_series/25914/8c88a2b2e156c28098d47bdd093e67e0_img.jpg b/marked/Rel-16/25_series/25914/8c88a2b2e156c28098d47bdd093e67e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27aa9f7d27d4f14d1852b18ba0960d9ad3715943 --- /dev/null +++ b/marked/Rel-16/25_series/25914/8c88a2b2e156c28098d47bdd093e67e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2901a59657c616024128dba9eda485dfee943fcf8b0f9e01e79ef7fc58f9cbed +size 22301 diff --git a/marked/Rel-16/25_series/25914/8ec6b1a5d391a58cfa4f2eebd7c48f54_img.jpg b/marked/Rel-16/25_series/25914/8ec6b1a5d391a58cfa4f2eebd7c48f54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc6f4710d0b38ba57e933f5c95c41406abbb31ec --- /dev/null +++ b/marked/Rel-16/25_series/25914/8ec6b1a5d391a58cfa4f2eebd7c48f54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d21e2366541f46bf859df0387ecae97ae3b127d7f4b7e306d6cd02c5cdbef36 +size 19451 diff --git a/marked/Rel-16/25_series/25914/8f931bb1d65d0ee4ccafab751ee61282_img.jpg b/marked/Rel-16/25_series/25914/8f931bb1d65d0ee4ccafab751ee61282_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08ee600ef15ca956726363cb6e21bcc37ccd17fe --- /dev/null +++ b/marked/Rel-16/25_series/25914/8f931bb1d65d0ee4ccafab751ee61282_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd3c833326a58db3e5c52d87de9296eaf265a9797e634f672b9f988d38bd306b +size 26516 diff --git a/marked/Rel-16/25_series/25914/a26b4f52392209236513dd503db41339_img.jpg b/marked/Rel-16/25_series/25914/a26b4f52392209236513dd503db41339_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4faeba734511cea348312b800bf15d23b5e4ba22 --- /dev/null +++ b/marked/Rel-16/25_series/25914/a26b4f52392209236513dd503db41339_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4d6b446d8ad11c1190a8b92b3ec2b5c5068475397b8b0896b3627db727daa56 +size 39167 diff --git a/marked/Rel-16/25_series/25914/a2c9fe78d22304889baddc26f4329ddf_img.jpg b/marked/Rel-16/25_series/25914/a2c9fe78d22304889baddc26f4329ddf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..361dfc7a8d7478bf6b718c725e8c634665da291c --- /dev/null +++ b/marked/Rel-16/25_series/25914/a2c9fe78d22304889baddc26f4329ddf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9213ffaeaa0f00e4b0603291a2ac1cb47d454c0bc711c56cfcb8702e90e1472 +size 11948 diff --git a/marked/Rel-16/25_series/25914/a8807f349e4e4d1d425fe4148f81741d_img.jpg b/marked/Rel-16/25_series/25914/a8807f349e4e4d1d425fe4148f81741d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d71154396397dc0c69780ffdf26a666a1234fb00 --- /dev/null +++ b/marked/Rel-16/25_series/25914/a8807f349e4e4d1d425fe4148f81741d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6ed67017df658f81cfb9c8ff16b1e9b9e2cf30d5fe31f3a1816cc9861bc0442 +size 20057 diff --git a/marked/Rel-16/25_series/25914/b038de46b62ad59f030ec5a0501673e1_img.jpg b/marked/Rel-16/25_series/25914/b038de46b62ad59f030ec5a0501673e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8df2a2ec7c26d0d794e3a83f724b6c9e0cac177 --- /dev/null +++ b/marked/Rel-16/25_series/25914/b038de46b62ad59f030ec5a0501673e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11d82ebaa6d815a8cc8d9c5bd1b30262787c93e0c3b6671041340422bee7c69e +size 28953 diff --git a/marked/Rel-16/25_series/25914/b25cc68846b070bbe56a949b011ba91c_img.jpg b/marked/Rel-16/25_series/25914/b25cc68846b070bbe56a949b011ba91c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e902ac63b5b29be99aa45299949cf45b3c71ed7 --- /dev/null +++ b/marked/Rel-16/25_series/25914/b25cc68846b070bbe56a949b011ba91c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9bbd571d777b2cb452fa8b15064004d99cc8eefe0d8cf13d90c3085309abf9f +size 29040 diff --git a/marked/Rel-16/25_series/25914/b9248cd9761f4c0fde1c623f92cb95a7_img.jpg b/marked/Rel-16/25_series/25914/b9248cd9761f4c0fde1c623f92cb95a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f58dcf3728b95aad5333b8542a6280f97253998 --- /dev/null +++ b/marked/Rel-16/25_series/25914/b9248cd9761f4c0fde1c623f92cb95a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2af0c26e5e384834217f1fcb3f9da9110ea97fafd3ce5654a33e9e72fb6453d3 +size 54454 diff --git a/marked/Rel-16/25_series/25914/ca81500b365ed30190cb2d9c38fc1f84_img.jpg b/marked/Rel-16/25_series/25914/ca81500b365ed30190cb2d9c38fc1f84_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a5e839b1166439d5f603b8f28bd793063782976e --- /dev/null +++ b/marked/Rel-16/25_series/25914/ca81500b365ed30190cb2d9c38fc1f84_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78eb06fafc9dcb80f10b619542353109e370215683cf0fa70fd1825fde8e5374 +size 43116 diff --git a/marked/Rel-16/25_series/25914/d9151713dc02d9d7933ac7e2c4a4441c_img.jpg b/marked/Rel-16/25_series/25914/d9151713dc02d9d7933ac7e2c4a4441c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69fce7e7fa5d746d879065ae47259ab74eaba926 --- /dev/null +++ b/marked/Rel-16/25_series/25914/d9151713dc02d9d7933ac7e2c4a4441c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0044cdae49feb25b08560e23c355d37bbdcc1c94d1cee0fbf5898590c32812fc +size 38107 diff --git a/marked/Rel-16/25_series/25914/ddc875f881bafee11e4fb5973c8a7918_img.jpg b/marked/Rel-16/25_series/25914/ddc875f881bafee11e4fb5973c8a7918_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f072a4f5cbb366a5e6e53890725d1c53b75a321 --- /dev/null +++ b/marked/Rel-16/25_series/25914/ddc875f881bafee11e4fb5973c8a7918_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d9956b2b467546883e180d6bae3895ee867519948c606143ba74b2fc219dbd3 +size 17342 diff --git a/marked/Rel-16/25_series/25914/e5ded42f8e352da02ee86cb55550c45d_img.jpg b/marked/Rel-16/25_series/25914/e5ded42f8e352da02ee86cb55550c45d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..852e2d6ebd4a87177077a6a83be008bfbbd8dee1 --- /dev/null +++ b/marked/Rel-16/25_series/25914/e5ded42f8e352da02ee86cb55550c45d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db8fb75c1601362c249cc2463be2100b9ad76b1809511c8b99d1128350af1abf +size 35033 diff --git a/marked/Rel-16/25_series/25914/fcbc3c31776721edc98ceb1944ec438f_img.jpg b/marked/Rel-16/25_series/25914/fcbc3c31776721edc98ceb1944ec438f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51c56d94868e957cf0ae8e7ceb04b81cf841ec7b --- /dev/null +++ b/marked/Rel-16/25_series/25914/fcbc3c31776721edc98ceb1944ec438f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6aebe0d6805cfa79b45488653f43e19f791bf80746040746654d5c030c9ee9a +size 86657 diff --git a/marked/Rel-16/25_series/25914/ffe0fef452a0ae9a20253c319c54e13c_img.jpg b/marked/Rel-16/25_series/25914/ffe0fef452a0ae9a20253c319c54e13c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..125249f43cba5f729b50a6cc6433b44f728d64d7 --- /dev/null +++ b/marked/Rel-16/25_series/25914/ffe0fef452a0ae9a20253c319c54e13c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b4d39fec7b9f31ad1d1711cc7ece087079ca381486df0b23d52772bcaa56d36 +size 25845 diff --git a/marked/Rel-16/25_series/25914/raw.md b/marked/Rel-16/25_series/25914/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..21ef272e7974f6463e49da8599b82c40642562c8 --- /dev/null +++ b/marked/Rel-16/25_series/25914/raw.md @@ -0,0 +1,3052 @@ + + + + +**Error:** + +**2** + +**Error: Reference source not** + +# Contents + +| | | +|-------------------------------------------------------------------------|----| +| Foreword..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Symbols and Abbreviations..... | 12 | +| 3.1 Symbols..... | 12 | +| 3.2 Abbreviations..... | 12 | +| 4 Introduction..... | 13 | +| 4.1 Scope..... | 13 | +| 4.2 Future extensions..... | 14 | +| 5 Initial Conditions..... | 14 | +| 5.1 Phantom specifications..... | 14 | +| 5.1.1 Head phantom..... | 14 | +| 5.1.2 DUT Positioning on head phantom..... | 15 | +| 5.1.3 Laptop Ground Plane Phantom..... | 16 | +| 5.1.4 DUT Positioning on Laptop Ground Plane Phantom..... | 17 | +| 5.1.5 Hand Phantoms..... | 18 | +| 5.1.5.1 Dimensions..... | 18 | +| 5.1.5.2 Dielectric properties..... | 19 | +| 5.1.5.3 Hand phantom grips..... | 20 | +| 5.1.5.4 Mechanical Requirements of Hand Phantoms..... | 22 | +| 5.1.6 DUT positioning for speech mode..... | 23 | +| 5.1.6.1 Mono-blocks and closed sliders..... | 23 | +| 5.1.6.2 Folds and open-slides..... | 24 | +| 5.1.6.3 PDA..... | 25 | +| 5.1.7 DUT positioning for browsing mode..... | 26 | +| 5.1.7.1 Narrow DUT..... | 26 | +| 5.1.7.2 PDA..... | 27 | +| 5.2 Anechoic chamber constraints..... | 27 | +| 5.2.1 Quiet zone dimension..... | 28 | +| 5.2.2 Minimum distance between the DUT and the measurement antenna..... | 28 | +| 5.2.3 Reflectivity of the quiet zone..... | 28 | +| 5.2.4 Shielding effectiveness of the chamber..... | 28 | +| 5.3 Embedded Devices..... | 28 | +| 5.3.1 Notebook..... | 29 | +| 5.3.2 Tablet..... | 29 | +| 6 Measurement parameters..... | 30 | +| 6.1 Definition of the Total Radiated Power (TRP)..... | 30 | +| 6.2 Definition of the Mean Effective Gain (MEG)..... | 31 | +| 6.3 Power angular models and channel XPR..... | 31 | +| 6.4 Definition of Mean Effective Radiated Power (MERP)..... | 33 | +| 6.5 Definition of Total Radiated Sensitivity (TRS)..... | 33 | +| 6.6 Definition of Mean Effective Radiated Sensitivity (MERS)..... | 33 | +| 6.7 Sampling grid..... | 33 | +| 6.8 Measurement frequencies..... | 34 | +| 7 Measurement procedure – transmitter performance..... | 34 | +| 7.1 General measurement arrangements..... | 34 | +| 7.2 Procedure for spherical scanning ranges..... | 34 | +| 7.3 Calibration measurement..... | 36 | +| 7.3 Reference antennas..... | 38 | +| 8 Measurement procedure – receiver performance..... | 40 | +| 8.1 General measurement arrangements..... | 40 | +| 8.2 Procedure for spherical scanning ranges..... | 40 | +| 8.3 Calibration measurement..... | 40 | + +| | | | +|-------------------------------|------------------------------------------------------------------------------|-----------| +| 9 | Radiated power and sensitivity measurement techniques in UMTS system..... | 41 | +| 9.1 | Technical background information..... | 41 | +| 9.1.1 | The common test setup for TRP and TRS testing..... | 41 | +| 9.2 | TRP measurement..... | 42 | +| 9.3 | TRS measurement..... | 43 | +| 9.4 | Calibration of absolute levels..... | 43 | +| Annex A (informative): | Estimation of measurement uncertainty..... | 44 | +| A.1 | Mismatch uncertainty between measurement receiver and the probe antenna..... | 50 | +| A.1.1 | Total combined mismatch uncertainty calculations..... | 50 | +| A.1.1.1 | Mismatch uncertainty through the connector between two elements:..... | 50 | +| A.1.1.2 | Mismatch uncertainty due to the interaction of several elements:..... | 51 | +| A.1.2 | Total combined mismatch uncertainty:..... | 52 | +| A.2 | Mismatch uncertainty of the RF relay..... | 53 | +| A.2.1 | First part: RF Relay switched on the co-polarized signal..... | 53 | +| A.2.1.1 | The mismatch through the connector between two elements..... | 53 | +| A.2.1.2 | Mismatch due to the interaction between two elements or more..... | 54 | +| A.2.2 | Second part: RF relay switched on the cross-polarized signal..... | 54 | +| A.2.2.1 | The mismatch through the connector between two elements..... | 54 | +| A.2.2.2 | Mismatch due to the interaction between two elements or more..... | 54 | +| A.2.3 | Total combined mismatch uncertainty:..... | 55 | +| A.3 | Insertion loss of the probe antenna cable..... | 55 | +| A.4 | Insertion loss of the probe antenna attenuator (if used)..... | 55 | +| A.5 | Insertion loss of the RF relays (if used)..... | 56 | +| A.6 | Influence of the antenna cable..... | 56 | +| A.6.1 | Probe antenna cable..... | 56 | +| A.6.2 | Calibration antenna cable..... | 56 | +| A.7 | Absolute gain of the probe antenna..... | 56 | +| A.8 | Measurement receiver: uncertainty of absolute level..... | 56 | +| A.9 | Measurement distance..... | 56 | +| A.9.1 | Offset of DUT phase centre from axis(es) of rotation..... | 56 | +| A.9.2 | Mutual coupling..... | 57 | +| A.9.3 | Phase curvature..... | 57 | +| A.10 | Quality of quiet zone..... | 57 | +| A.11 | Tx-power drift of DUT..... | 58 | +| A.12 | Uncertainty related to the use of phantoms..... | 58 | +| A.12.1 | Uncertainty from using different types of SAM phantom..... | 58 | +| A.12.2 | Simulated tissue liquid uncertainty..... | 58 | +| A.12.3 | Uncertainty of dielectric properties and shape of the hand phantom..... | 59 | +| A.12.4 | Uncertainty from using different types of Laptop Ground Plane phantom..... | 60 | + +| | | | +|-------------------------------|----------------------------------------------------------------------------------------|-----------| +| A.13 | Coarse sampling grid..... | 60 | +| A.14 | Random uncertainty..... | 61 | +| A.15 | Uncertainty of network analyzer..... | 62 | +| A.16 | Uncertainty of the gain/efficiency of the calibration antenna..... | 62 | +| A.17 | Base station simulator: uncertainty of the absolute level..... | 62 | +| A.18 | BER measurement: output level step resolution..... | 62 | +| A.19 | Statistical uncertainty of the BER measurement..... | 63 | +| A.20 | BER data rate normalization uncertainty..... | 63 | +| A.21 | DUT sensitivity drift..... | 63 | +| A.22 | Cable loss measurement uncertainty..... | 63 | +| A.23 | Signal generator: uncertainty of the absolute output level..... | 64 | +| A.24 | Signal generator: output level stability..... | 64 | +| A.25 | Insertion loss: calibration antenna feed cable..... | 64 | +| A.26 | Insertion loss: calibration antenna attenuator (if used)..... | 64 | +| A.27 | Chamber Statistical Ripple and Repeatability..... | 65 | +| A.28 | Additional Power Loss in EUT Chassis..... | 65 | +| A.29 | Void..... | 77 | +| A.29.1 | Void..... | 77 | +| Annex B (informative): | Suggested recipes of liquid to be used inside SAM phantom..... | 78 | +| Annex C (informative): | System Parameters..... | 79 | +| C.1 | Definition and applicability..... | 79 | +| C.2 | Establishing the connection..... | 79 | +| C.2.1 | Required parameters to initiate the communication - basic concepts..... | 79 | +| C.2.1.1 | Conversational RAB..... | 79 | +| C.2.1.2 | Logical, transport, and physical channels in UMTS..... | 79 | +| C.2.1.3 | Dedicated physical channel..... | 79 | +| C.2.2 | Recall on the reference measurement channel (reference to the standard paragraph)..... | 79 | +| C.2.3 | Uplink 12.kbps reference measurement channel ([60], annex C, § C.2.1)..... | 80 | +| C.2.4 | Downlink 12.2 kbps reference measurement channel ([60], annex C, § C.3.1)..... | 80 | +| Annex D (informative): | Radiated power and sensitivity measurement techniques in 2G systems..... | 81 | +| D.1 | Introduction..... | 81 | +| D.1.1 | Scope..... | 81 | +| D.1.2 | References..... | 81 | +| D.1.3 | Definitions, symbols and abbreviations..... | 81 | +| D.1.3.1 | Definitions..... | 81 | +| D.1.3.2 | Symbols..... | 81 | +| D.1.3.3 | Abbreviations..... | 81 | +| D.2 | Initial conditions..... | 81 | +| D.2.1 | Phantom specifications..... | 81 | +| D.2.2 | Anechoic chamber constraints..... | 82 | +| D.2.3 | General arrangement..... | 82 | +| D.2.3.1 | Free space..... | 82 | +| D.2.3.2 | With SAM head phantom..... | 82 | +| D.2.3.3 | Test-bed setup..... | 83 | + +| | | | +|-------------------------------|---------------------------------------------------------------------------------------|------------| +| D.3 | Measurement parameters..... | 83 | +| D.3.1 | Definition of the TRP parameter..... | 83 | +| D.3.2 | Definition of the MEG parameter..... | 83 | +| D.3.3 | Definition of the MERP parameter..... | 83 | +| D.3.4 | Definition of the TRS parameter..... | 83 | +| D.3.5 | Definition of the MERS parameter..... | 83 | +| D.4 | Sampling grid..... | 83 | +| D.5 | Measurement frequencies..... | 84 | +| D.6 | Output power measurement..... | 84 | +| D.6.1 | TRP..... | 84 | +| D.6.2 | TRS..... | 84 | +| D.7 | Measurement procedure – transmitter performance..... | 84 | +| D.7.1 | Transmitter performance measurement..... | 84 | +| D.7.1.1 | Spherical scanning ranges..... | 84 | +| D.7.2 | Reference position..... | 84 | +| D.7.3 | General measurement arrangements..... | 85 | +| D.7.3.1 | TRP..... | 85 | +| D.7.3.2 | TRS..... | 85 | +| D.7.4 | Calibration measurement..... | 86 | +| D.8 | Measurement uncertainty and corrections in 2G system measurements..... | 86 | +| Annex E (informative): | Alternative measurement technologies: reverberation chamber method..... | 87 | +| E.1 | Reverberation chamber constraints..... | 87 | +| E.1.1 | Chamber size..... | 87 | +| E.1.2 | Mode-stirring facilities..... | 87 | +| E.1.3 | Loading of chamber with lossy objects..... | 88 | +| E.1.4 | Polarization imbalance and receiving antennas..... | 88 | +| E.1.5 | Shielding effectiveness..... | 89 | +| E.2 | Reverberation chamber method..... | 89 | +| E.2.1 | Measurement procedure – transmitter performance..... | 89 | +| E.2.2 | Measurement procedure – receiver performance..... | 89 | +| E.3 | Calibration of reverberation chamber..... | 90 | +| E.3.1 | Measurement of S-parameters through the chamber for a complete stirring sequence..... | 91 | +| E.3.2 | Calculation of the chamber reference transfer function..... | 92 | +| E.3.3 | Cable calibration..... | 92 | +| E.4 | Estimation of measurement uncertainty..... | 93 | +| Annex F (informative): | Anechoic chamber specifications and validation method..... | 94 | +| F.1 | Shielded anechoic chamber specifications..... | 94 | +| F.2 | Quiet Zone reflectivity level validation..... | 94 | +| F.2.1 | Description of a practical method for Quiet Zone characterization..... | 94 | +| Annex G (informative): | Reverberation chamber specifications and validation method..... | 97 | +| G.1 | Shielded reverberation chamber specifications..... | 97 | +| G.2 | Reverberation chamber statistical ripple and repeatability validation..... | 97 | +| Annex H (informative): | Dielectric Property Measurements of Hand Phantoms..... | 99 | +| H.1 | Open-ended Coaxial Probe (OCP) Method..... | 99 | +| Annex I (informative): | Change history..... | 101 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document describes the methods to be used in order to assess the radio performances of the 3G user equipment/mobile stations (UE/MS) in active mode in both the up- and the downlink. The test procedure is based on the test method developed as a result of COST 273 Sub-Working Group (SWG) 2.2 members' contributions and the first draft was published in [1]. Background work has also been made in the former COST259 project [2] [3]. + +# --- 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] P. Boutou, J. Krogerus, J. Ø. Nielsen, T. Bolin, I. Egorov, K. Sulonen, "Measurement of Radio Performances for UMTS Mobile in Speech Mode: the First Draft of the Prestandard", COST 273 TD(03) 140, Paris, France, May 2003, 6 p. +- [2] "Feasibility Study of UE antenna efficiency test methods and performance requirement-final report", 3GPP TSG-RAN4 document TSGR#19(01)1086, September 2001. +- [3] L. M. Correia (editor), "Wireless Flexible Personalised Communications – Final Report of COST 259", ISBN: 0-471-49836-X, Wiley Europe, March 2001, 482 p. +- [4] 3GPP TS 25.101 V4.10.0: "User Equipment (UE) radio transmission and reception (FDD)". +- [5] 3GPP TD R4-011482: "Proposal for establishing co-operation between 3GPP and COST273 WG2.2 for the further development of UE antenna performance test method". +- [6] 3GPP TD R4-020724: "Development of Standard Test Procedure for 3G User Equipment Antenna Performance". +- [7] T. Taga, "Analysis for mean effective gain of mobile antennas in land mobile radio environments", IEEE Transactions on Vehicular Technology, 39(2): 117-131, May 1990. +- [8] A. Alayon Glazunov, "MEG of mobile terminal antennas in double directional channels", TD (03) 187, Prague, Czech Republic, September 2003. +- [9] K. Madsen, "Reverberation Chamber for Mobile Phone Radiated Tests", COST 273 TD(04) 087, Gothenburg, Sweden, June 2004. +- [10] P.-S. Kildal, "Accurate Measurements of Small Antennas and Radiation from Mobile Phones in Small Reverberation Chamber", COST273 TD(02)035. +- [11] K. Rosengren, P.-S. Kildal, C. Carlsson, J. Carlsson, "Characterization of antennas for mobile and wireless terminals in reverberation chambers: Improved accuracy by platform stirring, Microwave and Optical Technology Letters, Vol. 30, No 20, pp.391-397, Sep. 2001. +- [12] P.-S. Kildal, C. Carlsson, "TCP of 20 Mobile Phones Measured in Reverberation Chamber Procedure, Results, Uncertainty and Validation", Feb. 2002, report available from Bluetest AB, [www.bluetest.se](http://www.bluetest.se) +- [13] P.-S. Kildal, C. Carlsson, "Detection of a polarization imbalance in reverberation chambers and how to remove it by polarization stirring when measuring antenna efficiencies", Microwave and Optical Technology Letters, Vol. 34, No. 2, pp 145-149, July 20, 2002. + +- [14] J. Krogerus, "Phantoms for Terminal Antenna Performance Testing", COST 273 TD(02) 154, Lisbon, Portugal, September 2002, 14 p. +- [15] 3GPP TD R4-021296: "Phantoms for 3G User Equipment Antenna Performance Testing", TSG-RAN Working Group 4 (Radio) meeting #24, R4-021296, Helsinki, Finland, 12th-16th August 2002. +- [16] P.-S. Kildal and K. Rosengren, "Correlation and capacity of MIMO systems and mutual coupling, radiation efficiency and diversity gain of their antennas: Simulations and measurements in reverberation chamber", accepted for publication in IEEE Communications Magazine, Aug. 2004. +- [17] Gordon, C. C., Churchill, T., Clauser, C. E., Bradtmiller, B., McConville, J. T., Tebbets, I., and Walker, R. A., 1988 Anthropometric Survey of U.S. Army Personnel: Methods and Summary Statistics, Technical Report NATICK/TR-89/044, U.S. Army Natick Research, Development and Engineering Center, Natick, Massachusetts, Sep. 1989. +- [18] J. Krogerus, "On the phantom and tissue simulating liquid to be used in handset antenna performance testing", COST 273 TD(02) 024, Guildford, UK, January 2002. +- [19] IEEE standard P1528; "Recommended Practice for Determining the Peak Spatial-Average Specific Absorption Rate (SAR) in the Human Head from Wireless Communications Devices: Experimental Techniques", April, 2003. +- [20] CENELEC Standard ENS 50361: "Basic Standard for the measurement of Specific Absorption Rate related to human exposure to electromagnetic fields from mobile phones (300 MHz-3 GHz)", Brussels, Belgium, CENELEC, July 2001, 51 p. +- [21] IEC standard 106 PT62209 part 1 Ed. 1.0: "Procedure to measure the Specific Absorption Rate (SAR) in the frequency range of 300 MHz to 3 GHz - Part 1: hand-held mobile wireless communication devices" +- [22] M.Y. Kanda, M. Ballen, C.K. Chou. "Formulation and characterization of tissue simulating liquids used for SAR measurement (500-2000 MHz)" Asia-Pacific Radio Science Conference, Tokyo, Japan, August 1-4, 2001, p. 274. +- [23] V. Vigneras, "Elaboration and characterization of biological tissues equivalent liquids in the frequency range 0.9 - 3 GHz", Final report, PIOM Laboratory, University of Bordeaux, France, November 2001. +- [24] O. Colas, C. Dale, J. Wiart "Influence of hand on the terminal total radiated power" COST 273 TD(04) 057. +- [25] H. Knoess, M. Christensen, S. Svendsen, T. Hiegler, A. Friederich, "Investigation of Different Phantom Head Models Including Holder", COST 273 TD(04) 068, Gothenburg, June 2004, 6 p. +- [26] T. Laitinen, J. Ollikainen, P. Vainikainen, C. Icheln, "Rapid Spherical 3-D Field Measurement System for Mobile Terminal Antennas", COST273 TD(03)134 +- [27] K. Kalliola, K. Sulonen, H. Laitinen, O. Kivekäs, J. Krogerus, and P. Vainikainen, "Angular power distribution and mean effective gain of mobile antenna in different propagation environments", IEEE Transactions on Vehicular Technology, 51(5): 823-838, September 2002. +- [28] M. B. Knudsen, G. F. Pedersen, "Spherical outdoor to indoor power spectrum model at the mobile terminal", IEEE Journal on Selected Areas in Communications, 20(6): 1156-1169, August 2002. +- [29] 3GPP TR 25.996: "Spacial channel model for Multiple Input Multiple Output (MIMO) simulations". +- [30] A. Alayon Glazunov, "A Note On Total Receiver Sensitivity of Mobile Terminal Antennas", COST273, TD(02)092, Espoo, Finland, 2002/May/30-31 +- [31] J. Oedum Nielsen, "Comparison of Total Received Power and Mean Effective Gain for Mobile Handsets", COST273 TD(02) 021. + +- [32] Alayon Glazunov, A., Pasalic, E., "Comparison of MEG and TRPG of practical Antennas", in *Proc. of PIMRC'04-15th IEEE International Symposium on Personal, Indoor and Mobile Radio Communications*, Barcelona Spain, Sept. 2004 +- [33] O. Colas, C. Dale, J. Wiart, G. Christophe, L. Robert, "Comparison between Mean Effective Gain (MEG) and its approximation in a uniform arrival angle environment", COST273 TD(04)058. +- [34] "UE antenna efficiency impact on UMTS system coverage/capacity", R4-030546, 3GPP TSG-RAN Working Group 4 (Radio) meeting #27, Paris, France 19th -23rd May, 2003 +- [35] Alayon Glazunov, A., "Joint Impact of the Mean Effective Gain and Base Station Smart Antennas on WCDMA-FDD Systems Performance", in *Proc. of NRS'04, The Nordic Radio Symposium 2004*, Oulu, Finland, Aug. 2004, +- [36] K. Sulonen, K. Kalliola, P. Vainikainen, "The effect of angular power distribution in different environments and the angular resolution of radiation pattern measurement on antenna performance", COST 273 TD(02) 028, Guildford, UK, January 2002, 7 p. +- [37] E. Van Lil, D. Trappeniers, J. Verhaevert, A. Van de Capelle, "On the influence of the size of objects on the number of power pattern samples and harmonics", COST273 TD(04)051. +- [38] J. Ø. Nielsen, G. F. Pedersen, "Frequency dependence of mean effective gain for mobile handsets", COST 273 TD(02)077. +- [39] ANSI/IEEE Std 149-1979, "IEEE Standard Test Procedures for Antennas", August 1980. +- [40] J. Krogerus, T. Jääskö, C. Icheln, "Comparison Measurements of the COST 273 SWG 2.2 Reference Monopole Antennas", COST273 TD(03)131. +- [41] L. Foged, A. Gandois et. al. "Reference antennas", Draft report for COST273 SWG2.2 (unpublished), 12.10.2004. +- [42] M. B. Knudsen, "Handset Performance Test including the Antenna", COST273 TD(01)043. +- [43] M. B. Knudsen, "Antenna Systems for Handsets", PhD Thesis, Aalborg University, November 2001, 116 p. +- [44] H. Holma, A.Toskala (editors), "WCDMA for UMTS: Radio Access for Third Generation Mobile Communications", John Wiley & Sons Ltd 2000, ISBN 0-471-72051-8, 322 p. +- [45] 3GPP: TS 25.101, Technical Specification Group Radio Access Network, UE radio transmission and reception (FDD) Release 1999, v3.14.0; June 2003 +- [46] C. Alain, G.F. Pedersen, R. Mathieu, "Radiation Testing for UMTS handset", COST 273 TD(04) 115, Gothenburg, June 2004, 10 p. +- [47] A. Char, M. Roberty, "Measurement setup for 3G phones", Aalborg University, Denmark, Master Thesis 2004, June 2004. +- [48] H. Shapter, J. Krogerus, "Uncertainty in Total Radiated Power measurements", Presentation in COST273 SWG2.2 Meeting, Helsinki, May 2002, 9 p. + Appendix 9 p., (unpublished). +- [49] J. Krogerus, A. Kruiy, H. Shapter, S. Pannetrat, B. Derat, "Estimation of Measurement Uncertainty in Total Radiated Power Measurements", COST 273 TD(04) 128, Gothenburg, June 2004, 23 p. +- [50] "Guide to the Expression of Uncertainty in Measurement", International Organization for Standardization (ISO), Geneva, Switzerland 1995. +- [51] NIST Technical Note 1297: "Guidelines for Evaluating and Expressing the Uncertainty of NIST measurement Results" +- [52] IEC: "Guide to the expression of uncertainty in measurement", Ed 1:1995. +- [53] "American National Standard for Expressing Uncertainty - U.S. Guide to the Expression of Uncertainty in Measurement," ANSI/NCSL Z540-2-1997, American National Standards Institute, New York. NY, 1997. + +- [54] (void) +- [55] ETSI TR 100 028: "ElectroMagnetic Compatibility and Radio Spectrum Matters (ERM); Uncertainties in the measurement of mobile radio equipment characteristics Part 1". +- [56] ETSI TR 102 273-1-1: "Electromagnetic compatibility and Radio spectrum Matters (ERM); Improvement on Radiated Methods of Measurement (using test site) and evaluation of the corresponding measurement uncertainties; Part 1: Uncertainties in the measurement of mobile radio equipment characteristics; Sub-part 1: Introduction". +- [57] ETSI TR 102 273-1-2: "Electromagnetic compatibility and Radio spectrum Matters (ERM); Improvement on Radiated Methods of Measurement (using test site) and evaluation of the corresponding measurement uncertainties; Part 1: Uncertainties in the measurement of mobile radio equipment characteristics; Sub-part 2: Examples and annexes". +- [58] A. Alayon Glazunov, "Impact of Head Phantom Models on Handset Antenna Efficiency Measurement Accuracy in Terms of Body Loss in Passive Mode", COST273 TD(02)144. +- [59] "Application note: recipes for brain tissue simulating liquids", Schmidt & Partner Engineering AG Application Note, Switzerland, 03/1999. +- [60] 3GPP 34.121 v3.14.0: "Terminal conformance specification; Radio transmission and reception (FDD)". +- [61] 3GPP TS 05.05 V8.5.1: "Radio Transmission and Reception". +- [62] 3GPP TS 11.10-1 V8.1.1: "Mobile station (MS) conformance specification; Part 1: Conformance specification". +- [63] M. Bäckström, O. Lundén, P-S. Kildal, "Reverberation chambers for EMC susceptibility and emission analyses", Review of Radio Science 1999-2002, pp. 429-452. +- [64] K. Rosengren and P-S. Kildal, " Study of distributions of modes and plane waves in reverberation chambers for characterization of antennas in multipath environment", Microwave and Optical Technology Letters, Vol. 30, No 20, pp. 386-391, Sept. 2001. +- [65] C. Orlenius, N. Serafimov and P-S. Kildal, "Procedure for measuring radiation efficiency in downlink band for active mobile phones in a reverberation chamber", IEEE AP-S International Symposium, Columbus, Ohio, June 2003. +- [66] Charlie Orlenius, Per-Simon Kildal, "Measurements of total isotropic sensitivity and average fading sensitivity of CDMA phones in reverberation chamber", manuscript to be submitted to IEEE AP-S International Symposium in Washington DC, June 2005. +- [67] P-S. Kildal, K. Rosengren, J. Byun, J. Lee, "Definition of effective diversity gain and how to measure it in a reverberation chamber", Microwave and Optical Technology Letters, Vol. 34, No 1, pp. 56-59, July 5, 2002. (J. Byun and J. Lee is with Samsung, South Korea) +- [68] K. Rosengren and P.-S. Kildal, "Radiation efficiency, correlation, diversity gain, and capacity of a six monopole antenna array for a MIMO system: Theory, simulation and measurement in reverberation chamber", accepted for publication in Proceedings IEE, Microwaves, Optics and Antennas, September 2004. +- [69] P-S. Kildal, K. Rosengren, "Electromagnetic analysis of effective and apparent diversity gain of two parallel dipoles", IEEE Antennas and Wireless Propagation Letters, Vol. 2, No. 1, pp 9-13, 2003 +- [70] R. Bourhis, C. Orlenius, G. Nilsson, S. Jinstrand and P.-S. Kildal, "Measurements of realized diversity gain of active DECT phones and base-stations in a reverberation chamber", IEEE AP-S International Symposium, Monterey, California, June 2004. +- [71] 3GPP RAN WG4#38, R4-060124, Dielectric properties of tissue stimulant used for radiated performance measurements, Nokia, Feb 2006. +- [72] Kefeng Liu "EMC Products: Chambers" Conformity 2005 – The Annual Guide, 6th edition. + +- [73] [3GPP TD R4-051326](#): "Description of the improved Quiet Zone characterization". +- [74] Dr. Michael D. Foegelle, ETS-Lindgren, Kevin Li, Nokia Corp., Andrew Pavacic and Paul Moller, Motorola, Inc. "Developing a Standard Hand Phantom for Wireless Testing" Part 1, Wireless design and Development +- [75] Gabriel, C., "Tissue Equivalent Material for Hand Phantoms," +Physics in Medicine and Biology, 52 (2007), pp. 4205 - 4210, +- [76] Dr. Michael D. Foegelle, ETS-Lindgren, Kevin Li, Nokia Corp., Andrew Pavacic and Paul Moller, Motorola, Inc. Wireless Design & Development, The Development of a Standard Hand Phantom for Wireless Performance Testing: Part 2 + +# 3 Symbols and Abbreviations + +## 3.1 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------| +| $\theta$ | Zenith angle in the spherical co-ordinate system | +| $\phi$ | Azimuth angle in the spherical co-ordinate system | +| $\Omega$ | Solid angle defined at the phase centre of the DUT | +| $G_{\psi}(\theta, \phi, f)$ | Antenna gain pattern in the $\psi$ -polarization as function of the spherical co-ordinates and the carrier frequency | +| F | Carrier frequency | +| $P_{tr}$ | Transmitted power | +| $Q_{\psi}(\theta, \phi, f)$ | Angular power distribution in the $\psi$ -polarization as function of the spherical co-ordinates and the carrier frequency | +| dB | decibel | +| dBm | dB referenced to one milliwatt | +| m | meter | +| mm | millimeter | +| kbps | kilobit per second | +| ms | millisecond | +| MHz | megahertz | + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|------------|-------------------------------------------------| +| 3G | 3 rd Generation | +| 3GPP | 3G Partnership Project | +| 3-D | Three Dimensional | +| AAU | Aalborg University | +| APD | Angular Power Distribution | +| BS | Base Station | +| BT | Bluetooth | +| CN | Core Network | +| CPICH RSCP | Common Pilot Channel Received Signal Code Power | +| CRC | Cyclic Redundancy Check | +| DCH | Dedicated Channel | +| DL | Downlink | +| DPCH | Dedicated Physical Channel | +| DPDCH | Dedicated Physical Data Channel | +| DPCCH | Physical Control Channel | +| DTCH | Dedicated Traffic Channel | +| DUT | Device Under Test | +| ETSI | European Telecommunications Standards Institute | +| GPS | Global Positioning System | + +| | | +|------|-----------------------------------------------------------------| +| HUT | Helsinki University of Technology | +| LME | Laptop Mounted Equipment | +| MEG | Mean Effective Gain | +| MERP | Mean Effective Radiated Power | +| MERS | Mean Effective Radiated Sensitivity | +| MS | Mobile Station | +| NB | Node B | +| NSA | Normalised Site Attenuation | +| QoS | Quality of Service | +| QPSK | Quadrature Phase Shift Keying (modulation) | +| RAB | Radio Access Bearer | +| RB | Radio Bearer | +| RAN | Radio Access Network | +| RF | Radio Frequency | +| Rx | Receiver | +| SAM | Specific Anthropomorphic Mannequin | +| TFCI | Transport Format Combination Indicator | +| TRS | Total Radiated Sensitivity (also: Total Integrated Sensitivity) | +| Tx | Transmitter | +| TRP | Total Radiated Power | +| TRS | Total Radiated Sensitivity (see also: TRS) | +| XPD | Cross-Polar Discrimination of the antenna | +| XPR | Cross-Polarization ratio of the channel | +| UL | Uplink | +| UE | User Equipment | +| UMTS | Universal Mobile Telecommunications System | + +# --- 4 Introduction + +The present document describes the methods to be used in order to assess the radio performances of the 3G user equipment/mobile stations (UE/MS) in active mode in both the up- and the downlink. The test procedure is based on the test method developed as a result of COST 273 Sub-Working Group (SWG) 2.2 members' contributions and the first draft was published in [1]. Background work has also been made in the former COST259 project [2] [3]. + +## 4.1 Scope + +The measurement procedure explained in this document applies to two classes of UE/MS products, one is the UE/MS used under the "speech mode" conditions that correspond to predefined positions (see Chapter 5) for voice application when the handset is held close to the user's head. And the other class is the laptop mounted equipment, including the wireless devices embedded into the laptop and the plug-in type device that host on the laptop. This method is also applicable to free space measurements. + +The testing methodology applies to any 3G handset, with internal or external antenna, with single or multiple receive antennas, that supports both the speech mode and the data transfer mode. It is also applicable to the testing of dual-mode (GSM / UMTS) terminals. Specific technical details related to testing of GSM mode of the dual-mode terminals are addressed in Appendix D. + +The radio tests considered here are: + +1. The measurement of the radiated output power +2. The measurement of the radiated sensitivity + +The test procedure described in this document measures the performance of the transmitter and the receiver, including the antenna and also the effects of the user. + +The purpose of this document is to serve as a standard test procedure for radio performance testing of mobile terminals. It is the intention that this procedure is going to be used by test houses, network operators, mobile terminal and antenna manufacturers, research institutes etc. The motivation for the development of this document is the lack of standards in this area in 3GPP [4]. COST 273 SWG2.2 has reported the progress of the pre-standardization in several 3GPP RAN4 meetings [5] [6]. + +The major parts of this test procedure are based on the 3-D pattern measurement method. It has been considered necessary to define some items and components in the test procedure in detail, such as test channels and phantom set-ups, in order to make the testing in different laboratories harmonized. The procedure is, however, not limited to some specific antenna chambers or positioners, but just gives examples of systems that are presently available. Moreover, the pre-standard is open for the use of some alternative to the 3-D pattern measurement method, provided that the specified performance parameters and the total measurement uncertainty can be achieved with the alternative test method. In the first phase the pre-standard uses TRP (Total Radiated Power) and TRS (Total Radiated Sensitivity) as the performance parameters but it is also prepared for the use of Mean Effective Gain (MEG) (or Mean Effective Radiated Power (MERP) and its corresponding parameter Mean Effective Radiated Sensitivity (MERS) for the receiver performance) as the preferred performance parameter in a later stage. + +Note: TRP and TRS are well-defined measures for the handset transmitter and receiver performance in an isotropic field distribution with XPR = 1 (cross polarisation ratio), whereas MEG [7], [8] also gives the handset performance relative to a well-known reference and can take different values depending on the chosen field distribution including the XPR. + +A Reverberation Chamber Method [9] [10] has been introduced in the pre-standard as an alternative test method for measuring total radiated power of the 3G UE ([11], [12] [13]). At the moment it has a limitation that it does not provide any possibility for the evaluation of MEG. + +## 4.2 Future extensions + +The TRS test method presented in this document is based on combined TRS measurement for devices with multiple receive antennas. Further enhancements for radiated UE receiver verifications are developed under the MIMO OTA WI in RP-120368 and therefore combined TRS test method may eventually be revisited. + +The test procedure presented in this document can be applied also for the testing of possible non-cellular systems in the 3G UE, such as Bluetooth (BT), General Positioning System (GPS), or Wireless Local Area Networks (WLAN). + +# --- 5 Initial Conditions + +The main objective of this section is to define basic parameters of simulated user (phantom) and anechoic chamber suited for the Tx and Rx measurement of UMTS mobile handsets. + +## 5.1 Phantom specifications + +### 5.1.1 Head phantom + +The Specific Anthropomorphic Mannequin (SAM) is used for radiated performance measurements. The phantom shape is derived from the size and dimensions of the 90-th percentile large adult male reported in an anthropometric study. It has also been adapted to represent the flattened ear of a wireless device user. + +For DUT radiated performance measurements in "intended use" position SAM head phantom without a shoulder section will be used. + +The shell of the SAM phantom should be made of low-loss material (loss tangent less than 0.05) with low permittivity (less than 5). The thickness has to be $2.0 \pm 0.2$ mm in the areas close to the handset in "intended use" position. + +The phantom has to be filled with tissue simulating liquid. It is recommended to use one of the typical SAR tissue simulating liquids and Appendix B gives four example recipes of such liquids. It is also recommended to verify the RF properties of the liquid with suitable equipment. The values should be maintained within 15% of the values relative permittivity $40 (\pm 15\%)$ and sigma $1.4 (\pm 15\%)$ at 1900 MHz. If the difference is more than $\pm 15\%$ , it should be taken in to account in the uncertainty budget. Dielectric properties measurement methods can be found e.g. in [22] [23]. + +Alternatively a dry SAM phantom made of plastic material with corresponding electrical parameters can be used. + +Note: Measurements have that the radiated performance of a terminal can be influenced by the hand presence. However, it is very difficult to develop a standardized hand phantom, which could allow pertinent and reproducible measurements. Therefore a phantom hand is not included in this test procedure. + +### 5.1.2 DUT Positioning on head phantom + +The DUT is attached to the SAM phantom in "cheek" position as defined both by IEEE [19] and CELENEC [20] standards. The DUT performance is measured on both left and right side of the head. + +Three points as shown in Fig. 5.1 define the reference plane: center of the right ear piece (RE), center of the left ear piece (LE) and center of mouth (M). + +At first, set the DUT ready for operation. + +Definition of the 'Cheek' position: + +- 1) Align the ear piece of the phone (see Fig. 5.1) at the line RE-LE. Then, position the DUT beside the phantom so that the vertical line (see Fig. 5.3) is parallel to the reference plane in Fig. 5.2 and is aligned with the line M-RE on the reference plane (see Fig. 5.3). +- 2) Position the DUT so that the ear piece of the DUT touches the ear piece of the phantom head on the line RE-LE. Tilt the DUT chassis towards the cheek of the phantom having the vertical line aligned with the reference plane until any point on the front side of the DUT is in contact with the cheek or until the contact with the ear is lost. + +NOTE: A holder fixture made of e.g. plastic may be used to position the handset against the phantom. An experimental study presented in [25] shows that some plastic holders might introduce an unexpectedly large effect to the measurement results. Therefore, special care must be seen when selecting such fixtures for radiated measurements. + +![Figure 5.1: Reference plane on head phantom, front view.](2224b82995b3ba31aa82f20fb06f4c9c_img.jpg) + +A front view diagram of a head phantom. A dashed horizontal line labeled "Reference plane" passes through three points: RE (right ear), LE (left ear), and M (mouth). The head is resting on a rectangular base. + +Figure 5.1: Reference plane on head phantom, front view. + +Figure 5.1: Reference plane on head phantom, front view. + +![Figure 5.2: Reference plane on head phantom, side view.](1e9fc8e561a3ee72410680d44728ba60_img.jpg) + +A side view diagram of the head phantom. A dashed line labeled "Reference plane" passes through the RE (right ear) and M (mouth) points. The head is resting on a rectangular base. + +Figure 5.2: Reference plane on head phantom, side view. + +Figure 5.2: Reference plane on head phantom, side view. + +![Figure 5.3: Reference lines at a mobile handset (Device Under Test (DUT)).](555df5c0300cb1fca5dc028fec5ec6be_img.jpg) + +The diagram shows a front view of a mobile handset. A vertical dashed line runs down the center, labeled 'vertical line' at the top. A horizontal dashed line runs across the top of the handset, passing through the 'ear piece', labeled 'horizontal line' on the left. The total width of the handset is labeled 'W' at the bottom. The width is divided into two equal parts, each labeled 'W/2'. An 'Antenna' is shown at the top right corner. + +Figure 5.3: Reference lines at a mobile handset (Device Under Test (DUT)). + +**Figure 5.3: Reference lines at a mobile handset (Device Under Test (DUT)). +W is the width of the chassis [19].** + +### 5.1.3 Laptop Ground Plane Phantom + +A laptop ground plane phantom is used for radiated performance measurements in case of plug-in DUT like USB dongles. The objective of the laptop ground plane phantom is to reproduce the effects of the ground plane for the antenna of the DUT while avoiding the variation of the measurements introduced by a real laptop. + +The laptop ground plane phantom, as showed in Figure 5.4, is composed by the following parts,: + +- a rectangular plane covered by a conductive film on the upper side with thickness of 4mm to emulate the keyboard and main body of the laptop; +- a rectangular plane covered by the same conductive film on the upper side with thickness of 4mm to emulate the screen of laptop; +- the conductive film on the two planes is connected. The angle between the two planes is 110 degrees. The material is FR-4 copper-clad sheet and the length and width of these two planes are 345mm and 238mm respectively; +- a horizontal USB connector placed along the short end of the plane; the location of the port is at the right back corner, the distance between the central axis of the USB connector and the rear edge of plane is 45mm, the ground of the USB connector is welded on the conductive film of the plane. The detailed description of the structure is presented in Figure 5.5; +- a USB cable crossing the ground plane and connecting the USB connector to a real functional laptop; the USB cable should be equipped with a shielded metal film, and the portion of the cable that is hung in the air shall be covered with absorbing material or treated with quarter wave chokes. The part of the USB cable lying on the plane is covered by a conductive adhesive strip used for fixing the cable on the plane and for guaranteeing at the same time the superficial continuity of the conductive plane. The shielded conductive film of this part of the USB cable is connected to the conductive film of the plane and the covered strip to well ground the antenna. The length of the USB cable should be no more than 3 meters. + +![Diagram of the laptop ground plane phantom setup including the DUT and a real functional laptop wrapped in absorbing material.](6cc4a2d5ea0462e4825d57bd689bd2b3_img.jpg) + +The diagram shows a 'Laptop ground plane phantom' consisting of two rectangular planes joined at an angle. The upper plane is labeled with 'Conductive film'. A 'Conductive adhesive strip' runs along the hinge. The angle between the planes is '110 degree'. A 'DUT' (Device Under Test) is connected to a 'USB connector' on the side of the lower plane. A 'Choked USB cable or covered with absorbing material' connects the phantom to a 'Real functional laptop'. The cable has several rectangular blocks representing 'absorbing material' and a 'thickness:4mm' callout near the connection point. The 'Real functional laptop' is also shown inside a box, indicating it is wrapped in absorbing material. + +Diagram of the laptop ground plane phantom setup including the DUT and a real functional laptop wrapped in absorbing material. + +**Figure 5.4: The laptop ground plane phantom, the DUT and the real functional laptop** + +![Technical drawing showing the structure and dimensions of the laptop ground phantom in top and side views.](53cb558495f8cc93c4202314ef492966_img.jpg) + +This figure provides the mechanical dimensions for the phantom. On the left is a top-down view showing a simple rectangle. On the right is a side profile view showing the two planes meeting at an angle (consistent with the 110 degrees mentioned previously). Dimension lines indicate the thickness and width of the base plane. + +Technical drawing showing the structure and dimensions of the laptop ground phantom in top and side views. + +**Figure 5.5: The structure and dimension of the laptop ground phantom** + +The real functional laptop is laid on the floor of the anechoic chamber, supplies power to the DUT and controls the state of the DUT. Both the USB cable and the real functional laptop are properly setup in order to have a negligible impact on the measurements: the real functional laptop is fully wrapped up with anechoic absorbers. + +### 5.1.4 DUT Positioning on Laptop Ground Plane Phantom + +The DUT is connected to the USB connector of the laptop ground plane phantom. The DUT should be plugged into the USB connector and positioned in accordance with the manufacturer recommended primary mechanical mode. In the absence of such a recommendation the DUT with either rotary USB port or non-rotary USB port should be horizontally plugged into the horizontal USB connector, as shown in Fig. 5.4. + +### 5.1.5 Hand Phantoms + +User's hand can have a great impact on radiated performance of a mobile terminal. The impact goes beyond blocking or absorbing a portion of the radiation, since the impedance of the antenna itself may be changed due to the material in near field. Thus a standardized hand phantom has been developed for radiated testing to reflect real world user scenarios [74]. + +#### 5.1.5.1 Dimensions + +Dimensions of the hand phantom are based on 50th percentile of the men's hand and women's hand dimensions averaged together in order to produce a standard hand phantom that lies in the middle of the expected range of users. Figure 5.1.5.1-1 illustrates the segments of the human hand, and Table 5.1.5.1-1 summarizes the various dimensions for an open hand phantom [74]. + +![Anatomical diagram of a human hand showing segments and dimension points.](7d066b8cdb123b3cba3584e8bb66f557_img.jpg) + +An anatomical diagram of a human hand, showing the skeletal structure and various segments. The fingers are labeled I, II, III, IV, and V. Finger I has three phalanges: Distal, Middle, and Proximal. Fingers II, III, and IV also have three phalanges each, labeled Distal, Middle, and Proximal. Finger V has two phalanges: Distal (labeled DI P) and Proximal (labeled PIP). The joints are labeled: IP (Interphalangeal joint) for finger I, PIP (Proximal Interphalangeal joint) for finger V, MCP (Metacarpophalangeal joint) for fingers I, II, III, IV, and V. The bones are labeled: Metacarpals, Carpals, CMC (Carpometacarpal joint), Wrist, Radius, and Ulna. Red lines indicate the longitudinal axes of the hand segments. + +Anatomical diagram of a human hand showing segments and dimension points. + +Figure 5.1.5.1-1. Segments and dimension points of the human hand [74]. + +Table 5.1.5.1-1. Hand phantom dimensions [74] + +| Dimension Description | Dim.
(mm) | Dimension Description | Dim.
(mm) | +|------------------------------------------------------------|--------------|--------------------------------------|--------------| +| Major Hand and Wrist Dimensions | | Digit III Dimensions | | +| Wrist Width | 61.4 | Distal Phalanx Length 2 | 20.1 | +| Wrist Circumference | 162.9 | Middle Phalanx Length 2 | 31.7 | +| Hand Length, Center of Wrist to Tip of Digit III | 186.5 | Proximal Phalanx Length 2 | 49.6 | +| Hand Circumference | 200.2 | Metacarpal Length 3 | 66.2 | +| Palm Length, Middle to Distal Palm Creases | 105.7 | Carpal Length 3 | 17.4 | +| Hand Width | 85.0 | DIP Width | 18.5 | +| Interdigital Crotch Dimensions | | PIP Width | 20.9 | +| Between Digit II & III Crotch to Tip of Digit II | 72.5 | DIP Circumference | 54.4 | +| Between Digit II & III Crotch to Tip of Digit III | 80.5 | PIP Circumference | 65.5 | +| Between Digit III & IV Crotch to Tip of Digit IV | 75.7 | Digit IV Dimensions | | +| Between Digit IV & V Crotch to Tip of Digit V | 61.5 | Distal Phalanx Length 2 | 20.0 | +| Between Digit I & II Crotch to Tip of Digit I 1 | 56.5 | Middle Phalanx Length 2 | 30.8 | +| Digit I Dimensions | | Proximal Phalanx Length 2 | 45.5 | +| Distal Phalanx Length 2 | 29.4 | Metacarpal Length 3 | 60.4 | +| Proximal Phalanx Length 2 | 36.5 | Carpal Length 3 | 19.4 | +| Metacarpal Length 2 | 46.8 | DIP Width | 17.2 | +| Carpal Length 2 | 22.0 | PIP Width | 19.9 | +| DIP Width | 22.3 | DIP Circumference | 50.3 | +| DIP Circumference | 67.7 | PIP Circumference | 61.2 | +| Digit II Dimensions | | Digit V Dimensions | | +| Distal Phalanx Length 2 | 18.1 | Distal Phalanx Length 2 | 17.3 | +| Middle Phalanx Length 2 | 26.7 | Middle Phalanx Length 2 | 21.8 | +| Proximal Phalanx Length 2 | 45.7 | Proximal Phalanx Length 2 | 38.0 | +| Metacarpal Length 3 | 67.4 | Metacarpal Length 3 | 56.6 | +| Carpal Length 3 | 20.6 | Carpal Length 3 | 24.3 | +| DIP Width | 18.7 | DIP Width | 16.1 | +| PIP Width | 21.5 | PIP Width | 17.9 | +| DIP Circumference | 54.1 | DIP Circumference | 45.9 | +| PIP Circumference | 64.8 | PIP Circumference | 54.2 | + +#### 5.1.5.2 Dielectric properties + +Dielectric properties of dry palm human tissue are set as the target dielectric parameters for hand phantoms [75]. The properties are presented in table 5.1.5.2-1. It's important that the hand phantom has equivalent electrical properties to real human hand to ensure that the same near field effects are seen with the hand phantom as would be seen with real hand. Relative permittivity of hand phantoms shall be within $\pm 15\%$ of the values listed in Table 5.1.5.2-1. Conductivity of hand phantoms shall be within $\pm 25\%$ of the values listed in Table 5.1.5.2-1. Methods for measuring dielectric properties can be found e.g. in [22] [23]. + +**Table 5.1.5.2-1. Target dielectric properties of a hand phantom.** + +| Frequency (MHz) | Er | \sigma (S/m) | +|------------------------|-----------|----------------------------------| +| 300,00 | 37,1 | 0,36 | +| 450,00 | 33,9 | 0,43 | +| 835,00 | 30,3 | 0,59 | +| 900,00 | 30 | 0,62 | +| 1450,00 | 27,9 | 0,85 | +| 1575,00 | 27,5 | 0,9 | +| 1800,00 | 27 | 0,99 | +| 1900,00 | 26,7 | 1,04 | +| 1950,00 | 26,6 | 1,07 | +| 2000,00 | 26,5 | 1,09 | +| 2100,00 | 26,3 | 1,14 | +| 2450,00 | 25,7 | 1,32 | +| 3000,00 | 24,8 | 1,61 | +| 4000,00 | 23,5 | 2,18 | +| 5000,00 | 22,2 | 2,84 | +| 5200,00 | 22 | 2,98 | +| 5400,00 | 21,7 | 3,11 | +| 5600,00 | 21,4 | 3,25 | +| 5800,00 | 21,2 | 3,38 | +| 6000,00 | 20,9 | 3,52 | + +#### 5.1.5.3 Hand phantom grips + +Hand phantom grips are based on human factor studies that were done to record how a phone of certain form factor was gripped by a large sample of people. Based on the grip study findings, three grip designs are chosen for 40- to 56-mm wide devices: one for mono-block devices used in a voice call, another for fold devices in a voice call, and a third “data mode” grip, simulating for example web browsing, Figure 5.1.5.3-1 shows mono-block and fold grips [76]. Grip studies showed that devices wider than 56 mm (generally PDA and touch screen devices) could be conveniently accommodated by a single grip to cover primary use cases, voice calls and data browsing [76]. + +Each grip is used with a spacer that is designed for repeatable positioning of terminals to the grips. The material for the monoblock palm spacer shall be hollow with a wall thickness less than 2 mm, and a dielectric constant of less than 5.0 and a loss tangent of less than 0.05 or it shall be solid with a dielectric constant of less than 1.3 and a loss tangent of less than 0.003. Touch fastener material may be used to affix the DUT to the palm spacer. + +Figures 5.1.5.3-1 and 5.1.5.3-2 below illustrate the right-handed and left-handed mono-block and fold grips respectively. + +![Two 3D rendered right hands showing different grips for holding terminals.](20ab59bc10b900f6cf8a34549848bbf4_img.jpg) + +Two 3D rendered right hands, shown in a dark gray color. The hand on the left is holding a terminal with its index finger pointing upwards. The hand on the right is holding a terminal with its thumb and index finger, with the index finger pointing to the right. + +Two 3D rendered right hands showing different grips for holding terminals. + +Figure 5.1.5.3-1 Right-handed grips defined to hold mono-block and fold terminals during voice calls [76]. + +![Two 3D rendered left hands showing different grips for holding terminals.](b038de46b62ad59f030ec5a0501673e1_img.jpg) + +Two 3D rendered left hands, shown in a dark gray color. The hand on the left is holding a terminal with its index finger pointing upwards. The hand on the right is holding a terminal with its thumb and index finger, with the index finger pointing to the right. + +Two 3D rendered left hands showing different grips for holding terminals. + +Figure 5.1.5.3-2 Left-handed grips defined to hold mono-block and fold terminals during voice calls + +Figures 5.1.5.3-3 and 5.1.5.3-4 below illustrate the right-handed and left-handed data browsing with narrow terminals and PDA grips respectively. + +![Two 3D rendered right hands showing different grips for data browsing.](8c88a2b2e156c28098d47bdd093e67e0_img.jpg) + +Two 3D rendered right hands, shown in a dark gray color. The hand on the left is holding a narrow terminal with its thumb and index finger. The hand on the right is holding a PDA-type device with its thumb and index finger. + +Two 3D rendered right hands showing different grips for data browsing. + +Figure 5.1.5.3-3. Right-handed grip defined for data browsing with narrow terminals and grip for holding PDA type of devices. + +![Figure 5.1.5.3-4 shows two 3D CAD models of a left hand. The left model shows a grip with narrow terminals, and the right model shows a grip for holding PDA type of devices.](b25cc68846b070bbe56a949b011ba91c_img.jpg) + +Figure 5.1.5.3-4 shows two 3D CAD models of a left hand. The left model shows a grip with narrow terminals, and the right model shows a grip for holding PDA type of devices. + +**Figure 5.1.5.3-4. Left-handed grip defined for data browsing with narrow terminals and grip for holding PDA type of devices** + +CAD models in table 5.1.5.3-1 define exact finger locations and spacers for the specified grips. The files are available in a subfolder of the archive area for this specification. + +**Table 5.1.5.3-1. CAD models for specified hand phantom grips and spacers.** + +| Hand phantom grip | Grip CAD file name | Grip spacer file name | +|---------------------------------|-----------------------------------------|-------------------------------------------| +| Right Mono-block grip | 25914-b10_CAD_hand1.zip | 25914-b10_CAD_spacer1.zip | +| Right Fold grip | 25914-b10_CAD_hand2.zip | 25914-b10_CAD_spacer2.zip | +| Right Narrow data browsing grip | 25914-b10_CAD_hand3.zip | 25914-b10_CAD_spacer3.zip | +| Right PDA grip | 25914-b10_CAD_hand4.zip | 25914-b10_CAD_spacer4.zip | +| Left Mono-block grip | 25914-b10_CAD_hand5.zip | 25914-b10_CAD_spacer5.zip | +| Left Fold grip | 25914-b10_CAD_hand6.zip | 25914-b10_CAD_spacer6.zip | +| Left Narrow data browsing grip | 25914-b10_CAD_hand7.zip | 25914-b10_CAD_spacer7.zip | +| Left PDA grip | 25914-b10_CAD_hand8.zip | 25914-b10_CAD_spacer8.zip | + +#### 5.1.5.4 Mechanical Requirements of Hand Phantoms + +The hand phantoms shall be constructed of a material that is sufficiently flexible to accommodate the range of devices specified in 5.1.5.3. The material shall also be made sufficiently stiff that the hand grip remains constant under rotation. + +Adequate material stiffness of the hand phantom is necessary to maintain high repeatability of OTA measurements. The stiffness of the hand material shall be verified by measuring the deflection of the index finger of a moulded monoblock hand phantom under a given weight. Test procedure is following; + +1. Position the hand phantom such that the index finger is horizontal. +2. Apply an indicator needle that extends horizontally $55 \text{ mm} \pm 1 \text{ mm}$ beyond the tip of the index finger. +3. Record the position of the indicator needle on a vertical scale. +4. Apply $20 \text{ g} \pm 0.2 \text{ g}$ of weight centered $6 \text{ mm} \pm 0.5 \text{ mm}$ from the tip of the index finger towards the hand. +5. Record the new position of the indicator needle on a vertical scale. + +The deflection of the index finger of the hand phantom shall be between 2 and 5 mm. Deflection less than 2 mm per 20 g weight indicates a material that is too rigid. Deflection greater than 5 mm per 20 g weight indicates a material that is too soft. + +![Figure 5.1.5.4-1: Hand phantom stiffness test. A line drawing showing a hand holding a device (DUT) against a vertical surface. A downward arrow indicates the force applied to the device.](a2c9fe78d22304889baddc26f4329ddf_img.jpg) + +Figure 5.1.5.4-1: Hand phantom stiffness test. A line drawing showing a hand holding a device (DUT) against a vertical surface. A downward arrow indicates the force applied to the device. + +Figure 5.1.5.4-1. Hand phantom stiffness test. + +![Figure 5.1.5.4-2: A weight container designed for a hand phantom stiffness test. A 3D rendering of a green, L-shaped weight container.](26070f41b834cefd33d293fecdba9868_img.jpg) + +Figure 5.1.5.4-2: A weight container designed for a hand phantom stiffness test. A 3D rendering of a green, L-shaped weight container. + +Figure 5.1.5.4-2. A weight container designed for a hand phantom stiffness test. + +A weight container presented in figure 5.1.5.14-2 may be used in the stiffness test. It is assumed that other grips will have similar stiffness as the monoblock hand from the same material. Therefore, a stiffness test of the monoblock hand alone is considered sufficient. + +### 5.1.6 DUT positioning for speech mode + +Speech mode is simulation of a voice call user case. DUT is placed in to a hand phantom which is holding the DUT against SAM head phantom. Positioning of the DUT in the hand phantom varies with the grip being used. Positioning of the DUT against the head phantom is identical to section 5.1.2, with the exception that 6° tilt angle from the cheek is being used instead of having direct contact between the cheek and DUT. A mask may be used to help configuration of cheek + 6° tilt angle. The mask is a 32 mm wide conformal strip, created by sweeping the surface of the head phantom through a 6° rotation about the ear. Direct DUT contact against the mask thus establishes the required 6° spacing away from the cheek, regardless of DUT form factor. The material for the head phantom mask spacer shall have dielectric constant of less than 1.3 and a loss tangent of less than 0.003. Material additions can be used to help fixing of the mask spacer onto the head phantom. + +#### 5.1.6.1 Mono-blocks and closed sliders + +This procedure applies to mounting monoblock DUTs and closed-slide DUTs, when the DUT is less than 56 mm wide. For consistent, repeatable positioning that conforms to the grip studies, an alignment tool with evenly spaced rulings is first used to measure the DUT. Alignment Tool A in figure 4, features a 120° interior corner to ensure that the ring fingertip lands in the desired position at the bottom of the DUT. The DUT is then positioned in accordance with ruled markings on a conformal palm spacer regardless of any curvature in the DUT corners. DUTs with rounded corners will sit lower in the tool than DUTs having square corners, and thus give a different reading. + +- 1 Place the DUT face-up in Alignment Tool A with its side along the side ruler, and slide it down until it makes contact at the 120° corner. Record the bottom location of the DUT by reading off the bottom ruler of Tool A. +- 2 Observe the top of the DUT against the side ruler of the tool. If the top of the DUT extends past the 120 mm marking on the side ruler, then the additional length beyond 120 mm shall be added to the reading from Step 1. +- 3 Place the DUT on the right-handed or left-handed hand phantom spacer between the fingers. The bottom location of the DUT on the spacer should be aligned with the reading recorded in step 1 & 2. Vertical centerline of the DUT should be centered with the spacer. Make sure index finger is in contact with DUT. + +- 4 While keeping the DUT in the hand phantom in the position defined in previous steps, place the DUT and the hand phantom against the head phantom in such way that the DUT is in 6° tilt angle as described in 5.1.6. + +![Figure 5.1.6.1-1: Alignment Tool A and right-handed mono-block hand phantom with a spacer. The image shows two components: on the left, Alignment Tool A is a vertical ruler with markings from 0 to 140 mm, with a horizontal line at 120 mm; on the right, a right-handed hand phantom holds a spacer with a ruler marked from 0 to 50 mm, with a green arrow pointing to the 5 mm mark.](ca81500b365ed30190cb2d9c38fc1f84_img.jpg) + +Figure 5.1.6.1-1: Alignment Tool A and right-handed mono-block hand phantom with a spacer. The image shows two components: on the left, Alignment Tool A is a vertical ruler with markings from 0 to 140 mm, with a horizontal line at 120 mm; on the right, a right-handed hand phantom holds a spacer with a ruler marked from 0 to 50 mm, with a green arrow pointing to the 5 mm mark. + +**Figure 5.1.6.1-1 Alignment Tool A and right-handed mono-block hand phantom with a spacer. The Alignment tool is used to determine DUT bottom location on spacer. Use left-handed (mirror-imaged) spacers with left-handed phantoms.** + +#### 5.1.6.2 Folds and open-slides + +This procedure applies to fold and open-slide DUTs, when the DUT is less than 56 mm wide. To help maintain a consistent, repeatable positioning that conforms to the grip studies, an alignment tool with evenly spaced rulings is first used to measure the DUT. The DUT is then positioned in accordance with ruled markings on a phantom spacer. Alignment Tool B in figure 5.1.6.2-1 features two rounded humps upon which the DUT is suspended. One hump represents the index fingertip of the hand phantom, while the other represents the palm spacer. This design helps ensure that the index finger remains in contact with the flip for any fold DUT geometry. + +- 1 Open the DUT and place it face-up on the alignment Tool B with its hinge suspended between the two humps. The side of the DUT shall be aligned against the side wall of the tool. The base of the DUT shall rest on the wide hump with ruled markings, and the flip of the DUT shall rest on the narrow hump. +- 2 Tool B has an engraved line on the side wall. Align axis of a fold hinge to this marking. An open slider should be slide longitudinally until the base part of the DUT touches the narrow hump of the Tool B. Record the correct longitudinal position of the bottom of the DUT by reading off the ruler of Tool B. Visually align the two halves of the split-level ruler to minimize parallax reading error. +- 3 Position the DUT in the right-handed or left-handed Fold Hand Phantom, resting on the index fingertip and palm spacer, with the bottom of the DUT aligned to the ruling on the right-handed or left-handed palm spacer that corresponds to the reading from Step 2. Ensure that all fingertips are in contact with the DUT. +- 4 While keeping the DUT in the hand phantom in the position defined in previous steps, place the DUT and the hand phantom against the head phantom in such way that the DUT is in 6° tilt angle as described in 5.1.6. + +![Figure 5.1.6.2-1: Alignment Tool B and right-handed fold hand phantom with a spacer. The image shows a 3D model of a grey alignment tool with a hinge axis, a narrow hump, and a wide hump. A yellow spacer with a ruler is placed on the tool. The ruler has markings for 10, 20, 30, 40, 50, and 60 mm.](a8807f349e4e4d1d425fe4148f81741d_img.jpg) + +Figure 5.1.6.2-1: Alignment Tool B and right-handed fold hand phantom with a spacer. The image shows a 3D model of a grey alignment tool with a hinge axis, a narrow hump, and a wide hump. A yellow spacer with a ruler is placed on the tool. The ruler has markings for 10, 20, 30, 40, 50, and 60 mm. + +**Figure 5.1.6.2-1 Alignment Tool B and right-handed fold hand phantom with a spacer. Use left-handed (mirror-imaged) spacers with left-handed phantoms.** + +#### 5.1.6.3 PDA + +This procedure applies to DUTs that are from 56 to 72 mm wide. To help achieve a consistent positioning, the DUT is aligned to a PDA palm spacer. No alignment tool is required. The PDA spacer features side and bottom walls to ensure consistent alignment of DUTs of various sizes. + +- 1 Place the DUT on the PDA spacer between the fingers and align the DUT to the side wall of the PDA. +- 2 If the DUT is shorter than 135 mm, then align the top of the DUT with the top of the PDA spacer. Otherwise align the bottom of the DUT with the bottom wall of the PDA spacer. +- 3 While keeping the DUT in the hand phantom in the position defined in previous steps, place the DUT and the hand phantom against the head phantom in such way that the DUT is in $6^\circ$ tilt angle as described in 5.1.6. + +![Figure 5.1.6.3-1: Right-handed PDA hand phantom with a spacer. The image shows a grey hand phantom holding a light grey rectangular device (DUT) against a vertical spacer. The spacer has a label 'side wall' with a right-pointing arrow at the top and a label 'bottom wall' with a downward-pointing arrow at the bottom. The DUT is positioned vertically, with its bottom edge resting on the bottom wall of the spacer.](5a2d10b858b621236f708a5f5fa1ed88_img.jpg) + +Figure 5.1.6.3-1: Right-handed PDA hand phantom with a spacer. The image shows a grey hand phantom holding a light grey rectangular device (DUT) against a vertical spacer. The spacer has a label 'side wall' with a right-pointing arrow at the top and a label 'bottom wall' with a downward-pointing arrow at the bottom. The DUT is positioned vertically, with its bottom edge resting on the bottom wall of the spacer. + +**Figure 5.1.6.3-1. Right-handed PDA hand phantom with a spacer. Use left-handed (mirror-imaged) spacers with left-handed phantoms.** + +### 5.1.7 DUT positioning for browsing mode + +Browsing mode is used to simulate user cases where the DUT is held in hand, but not pressed against ear e.g. web browsing and navigation. The DUT shall be mounted in a suitable hand phantom and oriented such that the DUT's main display is tilted 45 degrees from vertical. Devices with a cover piece are tested cover open. + +#### 5.1.7.1 Narrow DUT + +This procedure is suitable for use with all DUTs narrower than 56 mm. Alignment Tool A in figure 5.1.6.2-1 is first used to measure the distance between the bottom of the DUT and the center of its nav key. The DUT is then positioned in accordance with ruled markings on a palm spacer to data mode hand phantom. + +- 1 Place the DUT on the DUT alignment Tool A. Record the chin length from the scale at the bottom of the alignment tool. +- 2 Record the location of the navigation key (or the "2" key, if no navigation key is present) on the side ruler of the DUT alignment tool A. The key's center is used as the reference. +- 3 Add the two readings from Step 2 and 3 together. If the sum is less than 30 mm, then use 30 mm location on spacer instead. +- 4 Place the DUT on the right-hand or left-hand narrow data palm spacer and align the side of the DUT with the side wall of the spacer. The bottom edge of the DUT shall be placed on the narrow data palm spacer at the ruling corresponding to the value obtained in Step 4 + +Make sure that the index finger is in contact with the back of the DUT. If the device is very narrow and/or thin, it may occur that the middle finger does not curl tightly enough to contact the DUT. In such case, in order to ensure consistent test results, no attempt should be made to force the fingertip to contact the DUT. Touch fastener material may be used to maintain the DUT in the desired position. + +![A 3D rendering of a right-handed data hand phantom holding a mobile device. The device has a vertical scale on its side, marked from 30 to 100 in increments of 10. The hand is positioned to simulate a typical data usage grip.](8f931bb1d65d0ee4ccafab751ee61282_img.jpg) + +A 3D rendering of a right-handed data hand phantom holding a mobile device. The device has a vertical scale on its side, marked from 30 to 100 in increments of 10. The hand is positioned to simulate a typical data usage grip. + +**Figure 5.1.7.1-1. Right-handed data hand phantom with a spacer. Use left-handed (mirror-imaged) spacers with left-handed phantoms** + +#### 5.1.7.2 PDA + +This procedure is suitable for use with DUTs of width 56-72 mm. The positioning of the DUT in the PDA hand for data mode is identical to that for speech mode described in 5.1.6.3. + +## 5.2 Anechoic chamber constraints + +The main objective of this section is to define basic parameters of the anechoic chamber suited for the Tx and Rx measurement of UMTS mobile handsets. + +The chamber should be equipped with an antenna positioner making possible to perform full 3-D measurements for both Tx and Rx radiated performance. Two main measurement set-ups are presented for this purpose: + +- a) A so-called spherical scanner system implies that the DUT is placed on a positioner that rotates in a horizontal plane. The probe antenna is rotated physically in the vertical plane. Alternatively multiple probe antennas can be placed along an arch in vertical plane and electronically switched in order to get the full 3-D radiation/sensitivity pattern (see Figure 7.1). Alternatively a multiple probe system, which has a set of probes located on the full spherical surface, may also be used [26]. In this case the DUT does not have to be rotated. +- b) A so-called dual axis system implies that the DUT is placed on a positioner that is able to rotate around two different axes. The signal is transmitted/received by a fixed probe (see Figure 7.2). It is noted that many conventional two-axis systems (i.e. many commercially available systems built for a more general use) are built for the support of rather heavy test objects (with narrow antenna beam), which by their mechanical size may disturb the measurement of nearly omnidirectional antennas. Note that such systems are equipped with a positioner that may disturb the measurement of nearly omnidirectional antennas. + +In both cases the measurement antenna should be able to measure two orthogonal linear polarizations (typically theta ( $\theta$ ) and phi ( $\phi$ ) polarizations). + +Note that for an anechoic chamber, horn antennas are usually used as probe antennas. There are two kinds of horn antennas: single-polarized and dual-polarized. The dual-polarized horn antenna has advantages of a major importance in comparison with the single-polarized. In fact, it is possible to measure two orthogonal polarizations without any movement of the probe, and this will: + +- a) Reduce the cable antenna uncertainty contribution + +- b) Improve the measurement stability +- c) Reduce the time delay between the acquisitions of each polarized signal due to the electrical RF relay. + +If using single-polarized probe antenna, it is possible to perform the measurements by turning one linear polarized antenna by 90 ° for every measurement point. However, this technique has a major drawback: the cable of this antenna is subjected to numerous bendings and rotations, which brings some measurement instabilities. The various positions of the cable have an effect on the repeatability of measurements, and the stress applied to the cable can reduce its performance. The use of a "stress cable", or a rotary joint, connected to the main low-loss cable that is connected to the BTS simulator is recommended if using a single-polarized probe. + +### 5.2.1 Quiet zone dimension + +Quiet zone has to be large enough to contain DUT attached to a phantom head and shoulders. The dimensions have to be slightly larger than the phantom dimension due to the fact that the rotation axes are not passing through the symmetry plane of the phantom, but through the phase center of the DUT. Thus minimum radius of the quiet zone has to be 150mm, which is the approximate distance from a mobile phone to the edge of the head and shoulders phantom while the phone is placed in an "intended use" position. + +### 5.2.2 Minimum distance between the DUT and the measurement antenna + +For far-field measurements, the distance $r$ between the DUT and the measurement antenna should be + +$$(5.1)$$ + +where $\lambda$ is the largest wavelength within the frequency band of interest and $D$ the maximum extension of the radiating structure. Then the phase- and amplitude uncertainty limits and the reactive near field limit are not exceeded. The influence of measurement distance is discussed in Appendix A - Estimation of Measurement Uncertainty + +### 5.2.3 Reflectivity of the quiet zone + +Reflectivity of the quiet zone must be measured for frequencies used with method described in Appendix F. Measured reflectivity level is used in uncertainty calculations. + +### 5.2.4 Shielding effectiveness of the chamber + +In order to be able to measure sensitivity all external radiation has to be eliminated. Depending on the conditions at the test site in question, different values of shielding effectiveness of the measurement chamber might be required. The only general requirement on the shielding effectiveness of the chamber is that the measured level of external signals at the frequency of interest (UMTS frequency band) has to be 10dB below sensitivity level of the mobile equipment. See Appendix F for more details on shielding effectiveness validation. + +When specified in a test, the manufacturer shall declare the nominal value of a parameter, or whether an option is supported. + +## 5.3 Embedded Devices + +The main objectives of this section are to define basic parameters required when performing TRP and TRS measurements on Notebook and Tablets. + +### 5.3.1 Notebook + +A notebook PC is a portable personal computer combining the computer, keyboard and display in one form factor. Typically the keyboard is built into the base and the display is hinged along the back edge of the base. The largest single dimension for a notebook is limited to 0.42 m. + +As notebooks are not body worn equipment nor recommended for use placed directly on the lap, the notebook shall be tested in a free space configuration without head and hand phantoms. + +When the notebook is placed in a measurement chamber the display shall be configured according to Table 5.3.1-1. + +**Table 5.3.1-1: Display Settings** + +| Parameter | Value | Note | +|-------------------|-------------------|---------------------------------------------------------------------------------------------| +| Display lid angle | 110 +/- 5 degrees | The lid angle is defined as the angle between the front of the display to the leveled base. | +| LCD Backlight | 50% | | +| Ambient sensor | Disabled | | + +A typical notebook PC is equipped with several radio access technologies. During the measurement the DUT shall be configured according to Table 5.3.1-2. + +**Table 5.3.1-2: Embedded radio transmitters** + +| Parameter | Value | Note | +|--------------------|--------------|-----------------------------| +| WWAN | Enabled | This is the DUT transceiver | +| Other transceivers | Disabled | UWB, WLAN, Bluetooth™ | + +The notebook power management shall be configured according to Table 5.3.1-3. + +**Table 5.3.1-3: Power management** + +| Parameter | Value | Note | +|--------------------------------------|------------------|-------------| +| Screensaver | Disabled | | +| Turn OFF display | Never | | +| Turn OFF Hard drive | Never | | +| System Hibernate | Never | | +| System Standby | Never | | +| Dynamic control of clock frequencies | Disabled | | +| Power source | Standard battery | | + +If the notebook is equipped with retractable antennas the device shall be tested with the antennas in a configuration recommended by the manufactures. + +### 5.3.2 Tablet + +A tablet is a portable personal computer combining the computer and display in a single form factor. User input is accomplished via touchscreen or a pen. The largest single dimension (i.e., length, width, height) for a tablet is limited to 0.42 m. Tablet devices may have different primary mechanical modes. + +Tablet shall be tested in a free space configuration without head and hand phantoms. If hand phantom grips become available for tablets, the testing configuration for tablets may be revisited. The center of rotation shall be the three-dimensional geometric center of the EUT, display facing free space. + +When a tablet is placed in a measurement chamber the display shall be configured according to Table 5.3.2-1. + +**Table 5.3.2-1: Display Settings** + +| Parameter | Value | Note | +|----------------------|--------------|-------------| +| LCD Backlight | 50% | | +| Ambient light sensor | Disabled | | + +A typical tablet is equipped with several radio access technologies. During the measurement the EUT shall be configured according to table 5.3.1-2. + +EUT shall be powered by battery and power management settings in table 5.3.1-3 shall be used. + +If a fixture is required to mount the EUT to the positioning system, the EUT holding fixture shall be made of a material with a dielectric constant of less than 5.0, and loss tangent less than 0.05. The fixture shall not extend beyond the footprint of the EUT by more than 20 mm, and shall be no more than 20 mm in thickness. It is recommended, but not required, that a Styrofoam spacer would be used between the holding fixture and the EUT. + +# 6 Measurement parameters + +## 6.1 Definition of the Total Radiated Power (TRP) + +The Total Radiated Power (TRP) is a measure of how much power the antenna actually radiates, when non-idealities such as mismatch and losses in the antenna are taken into account. The TRP is defined as the integral of the power transmitted in different directions over the entire radiation sphere: + +$$(6.1)$$ + +Using $G_{\text{xx}}$ to denote either $G_{\text{xx}}$ or $G_{\text{yy}}$ , is the $\text{xx}$ -polarization component of the gain pattern for the handset antenna measured at the frequency $f$ , where $\Omega$ is the solid angle describing the direction. $P_{\text{tx}}$ is the transmit power level of the handset so that $P_{\text{tx}} G_{\text{xx}}$ is the actually transmitted power-level, also known as EIRP, in the $\text{xx}$ -polarization and in the direction $\Omega$ for frequency $f$ . + +The above equation may be written in "gain" form, that is, the TRP given by $P_{\text{TRP}}$ is normalized to the transmitted power $P_{\text{tx}}$ . This is the total radiation efficiency, which can also be denoted as Total Radiated Power Gain, TRPG, + +$$(6.2)$$ + +Expressing the TRP by this form allows a simpler understanding of concept of the Mean Effective Gain (MEG) that will be introduced below. + +In practice discrete samples of $G_{\text{xx}}$ are measured and used to approximate the integral so that the TRP is computed as + +$$(6.3)$$ + +Or, by using the relation : + +$$(6.4)$$ + +In gain form the TRP can be expressed as: + +$$(6.5)$$ + +In these formulas $\Delta\theta$ and $\Delta\phi$ are the sampling intervals for the $\theta$ - and $\phi$ -angles, respectively, and the number of samples in the $\theta$ - and $\phi$ -angles are given by $N_\theta$ and $N_\phi$ , respectively. The sampling points of the sphere are given by $\theta_i$ and $\phi_j$ . The sampling intervals are discussed further in Section 6.6. + +When measuring power radiated by active devices, expressing the data in terms of EIRP is more appropriate. The upper form of the TRP formulas (which includes EIRP terms) will be used in the data processing. + +## 6.2 Definition of the Mean Effective Gain (MEG) + +The Mean Effective Gain (MEG) is the ratio of the actually received mean power by a User Equipment/Mobile Station antenna (or the NB/BS by reciprocity) to the mean power received from two hypothetical isotropic antennas in the same UE/MS environment and matched to the $\text{xx}$ - and $\text{yy}$ -polarizations, respectively. As detailed in [7]&[8], the MEG may be obtained using a surface integration, + +$$(6.6)$$ + +Using $G_{\text{xx}}$ to denote either $G_{\text{xx}}$ or $G_{\text{yy}}$ , is the $\text{xx}$ -polarization component of the gain pattern for the handset antenna measured at the frequency $f$ , where $\Omega$ is the solid angle describing the direction. + +The term $P_{\text{rx}}$ denotes the average power received by the UE/MS in the direction $\Omega$ , in the $\text{xx}$ -polarization and for the frequency $f$ , in other words, $P_{\text{rx}}$ is the Power Angular Distribution (PAD) of the received signal at different Angle of Arrivals/Departures (AoA/AoD) at the UE/MS. Typically $P_{\text{rx}}$ is a model derived from measurements. Since the MEG is a ratio of power values only the cross polarization ratio (XPR) of the channel (observe that this parameter is in general a function of the carrier frequency, $f$ ) and the distribution of power versus direction for each frequency is important in the model. However, in practice the average XPR will remain almost constant for each frequency band in question. + +Note: It should be noticed that in order to arrive to the definition of MEG given by expression (6.6) it has been assumed that there is no correlation between two cross-polarized components arriving/departing along the same direction. Hence, it is assumed that the cross-polarization state of the channel including the antenna may be obtained by the XPR. + +## 6.3 Power angular models and channel XPR + +The following are some examples of models that do not include frequency dependence, + +- 1) HUT: the model is based on numerous measurements in the city of Helsinki, Finland [27]. This model is uniform versus azimuth angle but non-uniform in the elevation angle. The XPR for this model is 10.7 dB. The NB/BS antenna was vertically polarized. +- 2) AAU: the model is based on numerous outdoor to indoor measurements in the city of Aalborg, Denmark [28]. This model is non-uniform versus both azimuth and elevation angle, and has an XPR of 5.5dB. The NB/BS antenna was vertically polarized. +- 3) Isotropic: the isotropic model implies equal weighting of power versus direction in both polarizations and using an XPR of 0 dB. It is important to notice that if this model is applied, the MEG will always be 3 dB lower than the TRPG. + +The models listed above are examples of existing models. Currently, a spatial channel model (SCM) has been devised by the combined 3GPP-3GPP2 ad-hoc group [29]. In that model a Power Angular Distribution at the UE/MS was defined that is in shape similar to the HUT model. + +![Figure 6.1: Angular elevation power density functions (θ-polarisation) of measured data (urban macrocell), and of Double Exponential and Gaussian distributions [27]. The plot shows the probability density function (pdf) on a logarithmic y-axis (from 10^-5 to 10^-1) versus the elevation angle θ [°] on the x-axis (from -80 to 80). The measured data (marked with 'x') shows a broad distribution peaking around 0°. The 'General double exponential' model (solid line) fits the measured data well, while the 'Gaussian' model (dashed line) is much narrower and does not fit the tails of the measured data.](3d7e0eb9c7e514f3026945a039354da4_img.jpg) + +Figure 6.1: Angular elevation power density functions (θ-polarisation) of measured data (urban macrocell), and of Double Exponential and Gaussian distributions [27]. The plot shows the probability density function (pdf) on a logarithmic y-axis (from 10^-5 to 10^-1) versus the elevation angle θ [°] on the x-axis (from -80 to 80). The measured data (marked with 'x') shows a broad distribution peaking around 0°. The 'General double exponential' model (solid line) fits the measured data well, while the 'Gaussian' model (dashed line) is much narrower and does not fit the tails of the measured data. + +**Figure 6.1: Angular elevation power density functions ( $\theta$ -polarisation) of measured data (urban macrocell), and of Double Exponential and Gaussian distributions [27].** + +These are some models for the environment's angle of arrival probability elevation distributions [7] [27] (the angles here are given in degrees): + +- 1) Gaussian distribution: + +$$p(\theta) = A_1 \exp\left(-\frac{(\theta - (90 - \theta_0))^2}{2\sigma^2}\right), \quad \theta \in [0, 180] \quad (6.7)$$ + +- 2) Double Exponential distribution: + +$$(6.8)$$ + +It should be noted that the MEG depends on the orientation of the handset with respect to the environment, because neither the PAD nor the antenna gain pattern are uniform. Both the HUT and AAU models consider this effect because these models are non-uniform in one or both of the azimuth and elevation angles. Therefore, the MEG generally needs to be computed for different handset orientations. In some cases different orientations of the handset may be obtained + +numerically from a single measurement, but more than one measurement of the gain pattern is necessary when the user of the terminal is included and different relative positions of the terminal next to the user are considered. + +As for the TRP the MEG in practice has to be computed using discrete samples of the antenna gain patterns using the expression + +$$(6.9)$$ + +where the sample points of the sphere are given in terms of $\theta$ and $\phi$ in which $\Delta\theta$ and $\Delta\phi$ are the sampling intervals for the $\theta$ - and $\phi$ -angles, respectively. + +The number of samples in the $\theta$ - and $\phi$ -angles are given by $N$ and $M$ , respectively. + +## 6.4 Definition of Mean Effective Radiated Power (MERP) + +When the MEG formula is applied to the active mobile terminals, it is convenient to modify the expression (6.6) to include the EIRP rather than just gain. This is done by introducing the definition of Mean Effective Radiated Power (MERP). In MERP we substitute the gain with EIRP. Note that due to the reciprocity, we can apply the MEG/MERP concept in both the downlink and uplink cases. + +## 6.5 Definition of Total Radiated Sensitivity (TRS) + +The Total Radiated Sensitivity is defined as: + +$$(6.10)$$ + +where the effective isotropic sensitivity (*EIS*) is defined as the power available at the antenna output such as the sensitivity threshold is achieved for each polarization. + +## 6.6 Definition of Mean Effective Radiated Sensitivity (MERS) + +The MEG formula (or more correctly the MERP) can be applied to the sensitivity measurements of active mobile terminals by modifying the formula into following form, which we call as Mean Effective Radiated Sensitivity, [30]: + +$$(6.11)$$ + +As in the case of MEG/MERP, MERS needs the antenna pattern measurements to be performed before its value can be determined. + +Note: At this stage the interrelation between the TRP and MERP as well as the impact of the channel XPR on the antenna performance have been addressed (see [31], [32], [33] for reference). However, this topic needs further investigation in order to be included in a future stage. + +Note: The impact of the MS/UE antenna performance on the UMTS capacity and and coverage in the downlink have been addressed in [34], [35]. + +## 6.7 Sampling grid + +There is a trade-off between the accuracy of the approximated TRP, MEG/MERP, TRS and MERS values and the total measurement time required to obtain a complete 3-D gain pattern of the antenna. It is important to limit the total measurement time since the handsets must be battery powered during the measurements. + +Generally it can be said that since the radiating object has a limited size the gain pattern cannot change arbitrarily versus angle, and therefore only a limited number of samples are required to represent the gain pattern to a given accuracy. Furthermore, it can be expected that the sampling density can be smaller for integral parameters (TRP, MEG/MERP, TRS and MERS) computations compared to what is required to represent the gain pattern, since the TRP/MEG are computed using an integration of the gain pattern. On the other hand it is expected that the obtained accuracy will strongly depend on the APD model used in the computation of MEG/MERP. + +In [36] typical error values have been calculated from practical gain pattern measurements of different mobile handsets using different sampling densities. A related study is presented in [37]. It is concluded that a $15^\circ$ -sample grid in both azimuth and elevation is sufficient for accurate measurements. + +Alternatively, different sampling patterns can be used, if they can provide benefit in terms of measurement time. For example, sampling the sphere on a continuous spiral trajectory with constant speed of rotation in elevation and azimuth can be a very convenient option for TRP measurements. Since the rotation around both axes is continuous, the total time required by the measurement can be significantly shorter than for a regular sampling grid. The continuous movement does not introduce a significant error provided that the transmitted power for each angle is recorded on a time scale much shorter than the angular variation. The TRP can be calculated by interpolating the values on the spiral trajectory to points on the regular grid or by using an alternative quadrature formula. As first order approximation the simple summation over the measurement points is adequate. It is convenient, in practice, to synchronize the azimuth and elevation rotation speed so that the DUT makes an integer number of complete revolutions, while the elevation changes from $0^\circ$ to $180^\circ$ . The number of complete revolutions defines the sampling interval in elevation and the overall number of measurements points. + +## 6.8 Measurement frequencies + +The radiation patterns of handset antennas can be expected to be frequency dependent, both in the maximum level and, to smaller extent, in the shape of the pattern. This is due mainly to the antenna matching circuits, which are typically frequency selective. The radiating current on the antenna itself will to some degree depend on the frequency. Given this, the TRP, MEG/MERP, TRS and MERS should be evaluated at all relevant frequencies, which, in principle, would require measurements of the spherical radiation patterns for each of those frequencies. However, due to practical reasons, such exhaustive measurements are not realizable. As a consequence, a few most relevant frequency points shall be selected in each considered band. + +As reported in [38] measurements have been performed at the center and at the two edge channels of the GSM-1800 band for five different types of handsets. It was found that the TRP for the edge channels differed up to 1.1 dB from the TRP of the center channel. Accordingly, the maximum deviation for the obtained MEG values was up to 1.7 dB. This shows that the TRP and MEG values obtained from a single-frequency gain pattern measurement of an antenna may lead to unacceptable high errors at other frequencies within the band, if one extrapolates those results to the TRP at other frequencies. Hence, the gain pattern must to be measured at more than one channel. + +For practical purposes, 3 channels Tx and 3 channels Rx per band are used in the measurements, i.e.: low, mid and high channels. + +# --- 7 Measurement procedure – transmitter performance + +This section describes the specifics of the radiated power measurement procedure. + +## 7.1 General measurement arrangements + +A radio communications tester or a corresponding device is used as a NB/BS simulator to setup calls to the DUT. The NB/BS simulator may also measure the radiated power samples. Alternatively, a measurement receiver or spectrum analyzer may be used for that purpose. See Chapter 9 and Appendix D for a more detailed description of the NB/BS simulator or spectrum analyzer in UMTS and 2G systems. + +The measurements are performed so that the DUT is placed against a SAM phantom. The characteristics of the SAM phantom are specified in Section 2. The measurement of the DUT is performed both on the left and right ears of the SAM phantom. The center of the rotation should be at the ear reference point of the SAM head. + +The measurements will be performed for the different antenna configurations of the DUT. For example in the case of a retractable antenna, for both antenna extended and retracted configurations. In future, more specific test configurations for each major type of terminals may be added in this part. + +## 7.2 Procedure for spherical scanning ranges + +The measurement procedure is based on the measurement of the spherical radiation pattern of the Device Under Test (DUT). The power radiated by the DUT is sampled in far field in a group of points located on a spherical surface enclosing the DUT. The samples are taken using a constant sample step of $15^\circ$ both in theta ( $\theta$ ) and phi ( $\phi$ ) directions. In some cases a different sampling grid can be used to speed up the measurements (See Section 6.6). All the samples are taken with two orthogonal linear polarizations, $\theta$ - and $\phi$ -polarisations. It is also possible to measure some other polarisation components, if it is possible to recover $\theta$ - and $\phi$ -polarisations from the measured data by some technique. The TRP, TRS, MEG/MERP and MERS are calculated from the measured data by integration (see definitions from Chapter 6). + +In the measurement the DUT is located in the center of the spherical surface. Examples of antenna pattern measurement systems are presented in Figure 7.1 and 7.2. + +One of the most common systems is the dual-axis positioner system, which is also known as a roll-over azimuth positioner. In this system the DUT is rotated around two axes and the probe antenna that measures the samples of the power radiated by the DUT, remains fixed. In the transmitter case, the probe antenna measures the power radiated by the DUT sampled at different angles. In the receiver case, the probe antenna measure angular samples of the dedicated channel signal containing the information needed by the NB/BS simulator to extract the DUT receiver performances. Typically, in the dual-axes positioner system, the DUT is rotated to a given azimuthal angle position. For this angle, the DUT is then rotated in the elevation plane, thus giving a complete measurement in constant plane. Then the DUT is moved to the next azimuthal angle, and so on. + +In spherical scanning systems the DUT is rotated in azimuthal plane and the probe antenna is moved in semicircular (or almost a fully circular) trajectory. The probe moves on an arch, or is moved by a rotating arm on the trajectory. The spherical scanning system can also be based on multiple probes, in which case the scanning in elevation direction is performed electrically. A multi-probe system having a number of probes on the full spherical surface can also be used, in which case the DUT can remain stationary [26]. Typically in the spherical scanning system the probe antenna is moved to fixed elevation angle position, in which the DUT is rotated in the azimuthal plane. Then the probe antenna is moved to the next elevation angle, in which the rotation of the DUT in azimuth plane is repeated, and so on. + +In both systems, it is possible to use a dual-polarised probe antenna or a single polarised probe antenna rotated by a polarisation positioner. The measurement system may use a dual-polarised probe antenna for taking the data with two polarizations, or the system may use a polarisation positioner. The systems and rotation sequences shown are examples of existing systems. Other rotation schemes and positioner are as well acceptable, as long as they produce the far field radiation pattern data with similar properties as the systems presented here. In all cases the data is post-processed by a similar calculation method. The standard spherical coordinate system used in the presentation of the radiation patterns is shown in Figure 7.3. + +![Figure 7.1: Two diagrams of spherical positioner systems. The left diagram shows a DUT (Device Under Test) on a rotating stand with a single probe antenna on a curved track. The right diagram shows the same DUT with multiple probe antennas mounted on the curved track. Both diagrams include a coordinate system with axes labeled phi (azimuth) and theta (elevation).](7bf4ae6f6e514c657b55be6302e3c7a4_img.jpg) + +Figure 7.1: Two diagrams of spherical positioner systems. The left diagram shows a DUT (Device Under Test) on a rotating stand with a single probe antenna on a curved track. The right diagram shows the same DUT with multiple probe antennas mounted on the curved track. Both diagrams include a coordinate system with axes labeled phi (azimuth) and theta (elevation). + +**Figure 7.1: Example of a spherical positioner system with a moving probe antenna (left), and with multiple probe antennas (right).** + +![Figure 7.2: Example of a dual axis (roll-over-azimuth) positioner system. The diagram shows an anechoic room with blue pyramidal wave absorbers on the walls. Inside, a 'BS simulator' is connected to a 'Horn antenna'. To the right, a device under test (DUT) is mounted on a dual-axis positioner that allows for roll-over and azimuth rotation, indicated by arrows and the Greek letter theta (θ).](7c07d25bb7b912053d0beb7ef9c41e91_img.jpg) + +Anechoic room + +Horn antenna + +BS simulator + +$\phi$ + +$\theta$ + +Figure 7.2: Example of a dual axis (roll-over-azimuth) positioner system. The diagram shows an anechoic room with blue pyramidal wave absorbers on the walls. Inside, a 'BS simulator' is connected to a 'Horn antenna'. To the right, a device under test (DUT) is mounted on a dual-axis positioner that allows for roll-over and azimuth rotation, indicated by arrows and the Greek letter theta (θ). + +Figure 7.2 Example of a dual axis (roll-over-azimuth) positioner system. + +![Figure 7.3: The coordinate system used in the measurements. This is a 3D Cartesian coordinate system with X, Y, and Z axes. The Z-axis is vertical, the Y-axis is horizontal to the right, and the X-axis points diagonally down and to the left. The angle theta (θ) is measured from the Z-axis down towards the XY-plane. The angle phi (φ) is measured in the XY-plane from the Y-axis. Two orthogonal electric field components, E_θ and E_φ, are shown as vectors originating from a point in the XY-plane.](ddc875f881bafee11e4fb5973c8a7918_img.jpg) + +Z + +$\theta$ + +Y + +$E_{\theta}$ + +$E_{\phi}$ + +$\phi$ + +X + +Figure 7.3: The coordinate system used in the measurements. This is a 3D Cartesian coordinate system with X, Y, and Z axes. The Z-axis is vertical, the Y-axis is horizontal to the right, and the X-axis points diagonally down and to the left. The angle theta (θ) is measured from the Z-axis down towards the XY-plane. The angle phi (φ) is measured in the XY-plane from the Y-axis. Two orthogonal electric field components, E\_θ and E\_φ, are shown as vectors originating from a point in the XY-plane. + +Figure 7.3 The coordinate system used in the measurements. + +## 7.3 Calibration measurement + +The relative power data values of the measurement points will be transformed to absolute radiated power values (in dBm) by performing a calibration measurement using a reference antenna with known gain or efficiency values. The reference antenna is also called as the calibration antenna. The calibration method used here is based on so-called gain-comparison (gain-transfer) method, [39]. In the calibration measurement the reference antenna is measured in the same place as the DUT, and the attenuation of the complete transmission path from the DUT to the measurement receiver/NB/BS simulator is calibrated out. The gain and/or radiation efficiency of the reference antenna must be known at the frequency bands in which the calibrations are performed. Recommended calibration antennas are monopole antennas or sleeve dipoles tuned for the each frequency band of interest [40] [41]. A network analyzer or spectrum analyzer can be used to perform the calibration measurement. The network analyzer method is recommended. The calibration is performed individually for the both orthogonal polarizations used in the testing of the devices under test. + +In the calibration procedure, a substitution method is used, allowing determining the Normalized Site Attenuation (NSA) at frequencies of interest. The principle is based on the use of calibration/substitution antennas (see the latter part of this section for more details about this kind of antennas) presenting a gain known with a sufficient accuracy in the measurement bandwidths. Such a substitution antenna is placed on the MS positioner at the exact MS location used for TRP, MEG/MERP, TRS and MERS measurement. It is possible to use a mechanical piece to place the substitution + +antenna on the positioner. This mechanical piece should not present any electromagnetic properties, which could influence the frequency response and the radiation properties of the substitution antenna. Note that usually two kinds of calibrated substitution antennas have to be considered to measure the vertical and horizontal polarization NSAs. + +Find hereafter, an illustration of the substitution configuration in Figure 7.4. + +![Figure 7.4: Illustration of the calibration/substitution procedure. The diagram shows an RF Power Generator connected to a Substitution antenna via a cable (A to C). The Substitution antenna is mounted on a positioner. A red curve represents the attenuation (NSA) between the Substitution antenna (P) and a Dual-polarized horn antenna (B). A calibrated cable (c1) connects the RF Power Generator to a Spectrum Analyser (B).](fcbc3c31776721edc98ceb1944ec438f_img.jpg) + +The diagram illustrates the calibration and substitution procedure within a shielded environment, represented by a rectangular box with blue triangular patterns on its top and bottom edges. Inside, a 'Substitution antenna' is mounted on a circular, adjustable positioner. A black cable connects the antenna at point 'C' to an 'RF Power Generator' at point 'A'. A red dashed vertical line labeled 'P' indicates the reference plane for the substitution antenna's radiation. To the right, a 'Dual-polarized horn antenna' is positioned. A red curve, representing the Normalized Site Attenuation (NSA), originates from point 'P' and extends to point 'B' on a 'Spectrum Analyser'. A calibrated cable, labeled 'c1', connects the RF Power Generator directly to the Spectrum Analyser at point 'B' to compare power levels. + +Figure 7.4: Illustration of the calibration/substitution procedure. The diagram shows an RF Power Generator connected to a Substitution antenna via a cable (A to C). The Substitution antenna is mounted on a positioner. A red curve represents the attenuation (NSA) between the Substitution antenna (P) and a Dual-polarized horn antenna (B). A calibrated cable (c1) connects the RF Power Generator to a Spectrum Analyser (B). + +**Figure 7.4 Illustration of the calibration/substitution procedure.** + +An RF power generator drives a continuous wave (CW) signal to the calibrated substitution antenna. + +After having measured cable losses from A to C and thanks to the data sheet of the calibrated substitution antenna, it is possible to determine the power radiated in the plane P, with a known and sufficiently low uncertainty. + +The cable AC connecting the substitution antenna to the RF power generator should be such that its influence upon radiation pattern measurements is negligible. + +NSA is the attenuation between P and B (red curve of Figure 7.4). + +The power generator is tuned to a reference output RF level. The measured power on the spectrum analyser allows deducing the NSA. + +Note that it is important to check the RF generator power level with the spectrum analyser, to avoid any power level differences between measurement devices. To do so, a calibrated cable is necessary (c1). + +This procedure has to be done at each frequency of interest. + +To achieve measurements with an uncertainty as low as possible, it is absolutely necessary to exactly keep the same P to B configuration (cables, dual-polarized antenna and cables positions, etc). + +In the case of TRP, TRS, MEG/MERP and MERS measurements using a radio communication tester, connection B has to be connected to a BS simulator. + +Find hereunder the formula that allows to define the NSA: + +$$(7.1)$$ + +where expressed in dB, NSA is the Normalized Site Attenuation, $P_{\text{Rfgen}}$ is the power delivered by the RF generator, $L_{\text{AC}}$ denotes the losses in the emission cable (AC), $G_{\text{substitution}}$ is the gain of the calibrated substitution antenna, $P_{\text{SA}}$ is the power measured by the spectrum analyser (B) and $\delta c1$ is the delta between reference levels of the RF generator and the spectrum analyser. + +The NSA measurement is affected by an uncertainty defined in Appendix A. Note that, between two successive NSA procedures, it is very important to check if the difference between the new NSA and the old one does not exceed the uncertainty value. If this difference is within the uncertainty scale, the first NSA measurement should be kept, otherwise the uncertainty scale would be increased. If this difference is out of the uncertainty scale, the site has been modified. In such a case, one should analyze what has been changed in the site and tune the NSA, if necessary. Another method to determine the NSA could be implemented as shown in Figure 7.5. + +![Figure 7.5: Calibration/substitution procedures using a vector network analyser. The diagram shows a Network Analyser with Port 1 (A) and Port 2 (B) connected to a Substitution antenna (C) and a Dual-polarized horn antenna (P) inside a shielded enclosure. The Substitution antenna is connected to Port 1, and the Dual-polarized horn antenna is connected to Port 2. The enclosure is lined with blue waveguide flanges.](08c7a76a7786bd08b99dd4cb41583ef4_img.jpg) + +Figure 7.5: Calibration/substitution procedures using a vector network analyser. The diagram shows a Network Analyser with Port 1 (A) and Port 2 (B) connected to a Substitution antenna (C) and a Dual-polarized horn antenna (P) inside a shielded enclosure. The Substitution antenna is connected to Port 1, and the Dual-polarized horn antenna is connected to Port 2. The enclosure is lined with blue waveguide flanges. + +**Figure 7.5 Calibration/substitution procedures using a vector network analyser.** + +The procedure is exactly the same but the use of a unique measurement device (network analyzer) for the transmission and reception avoids the measurement of $\delta c_1$ . + +Note that the calibration procedure was described for a system using a spectrum analyzer as the receiver in the DUT measurements. The same calibration procedure is applicable also for the systems using a radio communications tester as the receiver. In that case the Rx-port corresponds to the input port of the spectrum analyzer in Figures 7.4 and 7.5. + +For spherical scanning systems, where the probe antenna is rotated in the vertical plane, it can be convenient to perform the NSA calibration, by using the reference antenna efficiency, rather than its peak gain [40]. In this case a full spherical scanning is performed with the reference antenna on the positioner. The average received power at the spectrum analyzer is calculated by using the standard summation formula described in section 6.1: + +$$(7.2)$$ + +$$(7.3)$$ + +This calibration procedure has the advantage that the NSA is averaged on all the probe antenna positions. + +The calibration is a highly time-consuming process. A reference UE can be a solution to rapidly verify that the calibration of the site does not deviate too much. It is very important to fully characterize the reference UE just after a full calibration procedure. + +## 7.3 Reference antennas + +### Low gain reference antennas + +Half-wave dipole antennas are widely used as reference antennas for measurement/calibration of antennas and test ranges for low gain antenna measurements. An example of reference sleeve dipole is shown in Figure 7.6. The design is based on low loss end-fed sleeve dipole technology minimizing cable and feed point interaction. The design includes a choke, which further reduces cable interaction by attenuating the natural return currents from the dipole [41]. + +Half-wave dipole is relatively narrow band antenna with roughly 10% bandwidth and very high efficiency $\sim 95\%$ . A very high degree of azimuth pattern symmetry can be obtained with high precision machining of the dipole components [41]. The dipole performance can be relatively easily estimated using theoretical formulas although these formulas are + +unable to predict the impact of the choke. Therefore, accurate pre-calibration of the reference sleeve dipoles in a laboratory specialized in high accuracy antenna calibrations is recommended. + +A carefully designed and constructed sleeve dipole is a good choice as the reference antenna for the calibration procedure of 3G UE performance measurements. The relative bandwidth of UMTS systems is 12 % (1920 to 2170 MHz). One calibrated sleeve dipole can approximately cover the whole UMTS band. However, different sleeve dipoles are needed for dual-system terminals (UMTS and GSM), for e.g. GSM900 and GSM1800 bands, thus, a set of calibrated sleeve dipoles may be needed. + +![Figure 7.6: Examples of reference sleeve dipoles. The figure consists of three parts: on the left, four blue sleeve dipoles are shown; in the center, a 3D visualization of a red sphere with a bright orange spot at the top, representing a radiation pattern; on the right, a polar plot showing the radiation pattern with concentric circles and radial lines, with labels like 180deg, 90deg, 0deg, and 270deg.](0aa15f5c9c3edae230985491199cfe8b_img.jpg) + +Figure 7.6: Examples of reference sleeve dipoles. The figure consists of three parts: on the left, four blue sleeve dipoles are shown; in the center, a 3D visualization of a red sphere with a bright orange spot at the top, representing a radiation pattern; on the right, a polar plot showing the radiation pattern with concentric circles and radial lines, with labels like 180deg, 90deg, 0deg, and 270deg. + +**Figure 7.6 Examples of reference sleeve dipoles [41].** + +In the proposed test procedure in this document, DUT measurements are needed with two orthogonal polarizations. Consequently, calibration measurement and antenna is needed for both of these two orthogonal polarizations. The magnetic dipole or magnetic loop antenna shown in Figure 7.7 is often used to complement the electrical dipole. The radiation pattern of the magnetic dipole is very similar to the electrical dipole but in orthogonal polarisation. The antenna consists of a planar structure generating a loop of current fed by a coaxial cable from below. The cable is orthogonal to the polarisation so any interaction between the two will generate cross-polar radiation. The design includes a choke, which further reduces cable interaction by attenuating the natural return currents from the magnetic dipole. + +The magnetic dipole is also relatively narrow band antenna with roughly 10% bandwidth and very high efficiency ~ 95%. A very high degree of azimuth pattern symmetry can be obtained with a careful design and high precision machining of the antenna components. As in the case of electrical dipole, theoretical formulas can be used to predict the performance but the impact of the choke has to be experimentally checked. Accurate calibration of the magnetic loop antenna in a high-accuracy antenna calibration laboratory is recommended. + +![Figure 7.7: Examples of reference magnetic dipoles (loop antennas). The figure shows three views of a blue magnetic dipole antenna: on the left, a top-down view; in the center, a side view; and on the right, a view from below showing the antenna mounted on a stand against a blue background.](d9151713dc02d9d7933ac7e2c4a4441c_img.jpg) + +Figure 7.7: Examples of reference magnetic dipoles (loop antennas). The figure shows three views of a blue magnetic dipole antenna: on the left, a top-down view; in the center, a side view; and on the right, a view from below showing the antenna mounted on a stand against a blue background. + +**Figure 7.7 Examples of reference magnetic dipoles (loop antennas) [41].** + +# 8 Measurement procedure – receiver performance + +This section describes the specifics of the radiated sensitivity measurement procedure. + +The procedure for the measurement of the UE receiver performance is in principle equivalent to the transmitter performance measurement described in Chapter 7. The basic difference is that now the absolute sensitivity value at a predefined BER level is the parameter of interest in each measurement point. Note that the receiver and transmitter performances measurements can be done in parallel, at each position. + +## 8.1 General measurement arrangements + +A radio communications tester or a corresponding device is used as a NB/BS simulator to setup calls to the DUT. The NB/BS simulator is also used to send test signals to the UE and measure the BER levels of the radio link and the information on the dedicated channel needed to extract the DUT receiver performances. See Appendices C and D for the UE receiver sensitivity measurement considerations in UMTS and GSM systems respectively. + +The measurements are performed so that the DUT is placed against a SAM phantom. The characteristics of the SAM phantom and positioning details are provided in Section 5. The measurement is performed both on the left and right ears of the SAM phantom. The center of the rotation should be at the ear reference point of the SAM head. + +The measurements will be performed for the different antenna configurations of the DUT. For example in the case of a retractable antenna, for both antenna extended and retracted configurations. + +## 8.2 Procedure for spherical scanning ranges + +The measurement procedure is based on the measurement of the spherical sensitivity pattern of the Device Under Test (DUT). The sensitivity values of the DUT at a predefined BER level are sampled in far field in a group of points located on a spherical surface enclosing the DUT. The samples are taken using a constant sample step of 30 °, or smaller, both in theta ( $\theta$ ) and phi ( $\phi$ ) directions. All the samples are taken with two orthogonal linear polarizations, - and -polarisations. It is also possible to measure some other polarisation components, if it is possible to recover - and -polarisations from the measured data by some technique. The Total Radiated Sensitivity (TRS) and Mean Effective Sensitivity (MERS) are calculated from the measured data by integration (see definitions from Chapter 6). + +See Chapter 7 for the examples of antenna pattern measurement systems and the definition of the coordinate system. + +For DUTs with more than one antenna port, all the tests should be performed using both (all) antennas simultaneously. + +## 8.3 Calibration measurement + +The relative receiver sensitivity values at the measurement points will be transformed to absolute sensitivity values (in dBm) by performing a calibration measurement using a reference antenna with known gain or efficiency values. In the calibration measurement the reference antenna is measured in the same place as the DUT, and the attenuation from the whole path from the DUT to the measurement receiver/NB/BS simulator is calibrated out. The gain and/or radiation efficiency of the reference antenna must be known at the frequency bands in which the calibrations are performed. Recommended calibration antennas are monopole antennas or sleeve dipoles tuned for the each frequency band of interest [40] [41], see the previous Chapter. A network analyzer is recommended for the calibration measurement. The calibration is performed individually for the both two orthogonal polarizations used in the testing of the devices under test. + +The calibration procedure for the receiver measurement (downlink) is in principle the same as for the transmitter (uplink) measurement. Note, however, that in UMTS systems the downlink measurement has different frequency band than the uplink. Moreover, in uplink measurement the attenuation path, which needs to be calibrated out, is from the location of the DUT to Rx-port of the radio communications tester (or a spectrum analyzer, if used), whereas in the downlink measurement the unknown attenuation path is from the DUT location to Tx-port of the radio communications tester. This consequently means that the uplink calibration data is not applicable for the downlink measurement but a separate calibration is needed. + +# --- 9 Radiated power and sensitivity measurement techniques in UMTS system + +This section presents technical details and examples on how to carry out the TRP (uplink) and TRS (downlink) measurement of the UMTS terminal with a radio communications tester. Appendix D presents details for TRP and TRS measurement procedure for 2G (GSM) mode of the terminal and related information can be found in references [42] and [43]. + +Some background information on the RF and frequency spectrum properties of UMTS system is presented first. + +## 9.1 Technical background information + +In the WCDMA system there are two operation modes called FDD (Frequency Division Duplex) and TDD (Time Division Duplex) [44]. The FDD mode is considered in this document. Data are transmitted simultaneously in uplink and downlink to/from different users at a given frequency. + +WCDMA FDD mode is designed to operate with 190MHz Tx-Rx frequency separation, and operates in Europe in the following paired bands: + +1920 – 1980 MHz: Up-link (UE transmits) + +2110 – 2170 MHz: Down-link (Node B transmits) + +The channel separation is 200 kHz, which means that the center frequency is an integer multiple of 200 kHz. In FDD mode the lowest RF uplink channel is 9612, which is equivalent to 1922.4 MHz. The middle RF uplink channel is 9750 (1950 MHz) and the highest RF uplink channel is 9888 (1977.6 MHz). The nominal frequency allocation for a single 3GPP WCDMA FDD channel is 5 MHz. The effective bandwidth for WCDMA is 3.84 MHz and with guard bands, the required bandwidth is 5 MHz. + +Table 9.1 shows the UE power classes according to 3GPP TS25.101 specification [45], but normally the only power classes in use are 3 (high power data terminal including antenna gain 2dBi) and 4 (speech terminal) in the user equipment. + +**Table 9.1: UE power classes according to 3GPP TS25.101, [45].** + +| Power Class | Nominal maximum output power | Tolerance | +|-------------|------------------------------|-----------| +| 1 | +33 dBm | +1/-3 dB | +| 2 | +27 dBm | +1/-3 dB | +| 3 | +24 dBm | +1/-3 dB | +| 4 | +21 dBm | ± 2 dB | + +The UE transmitter has the capability of changing the output power with a step size of 1, 2 and 3 dB. + +### 9.1.1 The common test setup for TRP and TRS testing + +Common settings for TRP and TRS measurements are needed to enable simultaneous measurement of TRP & TRS: + +- Power control algorithm 2 + - More stable output power + - As the TRS is tested at the same time with TRP there will be errors in received power control commands during the test. With PCA2 the impact of random PC errors to the UE output power can be minimized. + - UE output power must be set to the maximum level during TRS test as in 25.101 sensitivity test case +- Compressed mode OFF + - Transmission gaps disabled +- Test loop mode 2 + - To enable TRS measurement + - In test loop mode 2 both the received bits and the CRC are looped back to Node B simulator +- Data pattern PN15 + +## 9.2 TRP measurement + +Radio communications tester with WCDMA FDD option is used in the measurements to simulate a base station (BS) (also called as Node B in UMTS system) for establishing and maintaining the calls. The BS simulator is also used for controlling the transmit power level of the mobile phones. Examples of such tester are R&S CMU200, AGILENT 8960 or ANRITSU. + +The test procedure is based on a connection between the tester and the DUT on a Reference Measurement Channel (RMC) specified in [45]. In the RMC it is possible to carry out BER tests as well as measure the received power at the UE (so-called CPICH RSCP for Common Pilot Channel Received Signal Code Power). The RMC permits also to vary the bit rate of the connection from 12.2 kbps to 384 kbps with symmetric or asymmetric traffic depending on the terminal capability. The presented test procedure is based on 12.2 kbps data rate. A higher data rate may be used in future along with the further development of the test procedure. + +The uplink measurement (TRP) algorithm measures the instantaneous maximum power by sending constant 'power up command' to the terminal. The mobile phone is commanded to transmit at full power so that output power variations due to the close loop power control are then avoided. + +Figure 9.1 shows an example test set-up for UMTS measurements. The filters are needed in the test set-up in order to avoid the coupling effects between the signals in the power splitter. Different filtered physical paths are shown in Figure 9.1. Using the same port for input and output on the communication tester has been discarded due to hardware restriction; indeed, the communication tester sensitivity on dual way port is much lower than single way port sensitivity. This is a typical problem of many existing BS simulators, which are still currently under development. Figure 9.1 represents a measurement set-up taking those problems into account. Splitter and filters will eventually be suppressed when it is possible to work only with one port of the BS simulator. + +Note: for practical reasons it may be most efficient to build a set-up that allows performing both 3G and 2G UE testing. + +![Figure 9.1: Example UMTS measurement set-up. The diagram is divided into two main areas: 'Anechoic room' (left) and 'Control Room' (right), separated by a dashed red line. In the Anechoic room, a 'DUT' (Device Under Test) is mounted on a stand with 'Roll axis' and 'Azimuth axis' rotation capabilities. A 'Dual Polarized Horn' antenna is positioned to receive signals from the DUT. A distance 'd' is indicated between the DUT and the antenna. The signal from the antenna goes to an 'RF Switch'. The RF Switch is connected to a 'Splitter'. One output of the splitter goes to an 'Uplink Freq. filter' and then to the 'RS CMU200 WCDMA Communication tester'. The other output of the splitter goes to a 'Downlink Freq. filter' and then back to the RF Switch. In the Control Room, a 'Computer with GPIB bus + control SW' is connected to the 'RS CMU200 WCDMA Communication tester' and to a 'Position Contr.' unit. The 'Position Contr.' unit is connected to the 'Roll axis' and 'Azimuth Axis' of the DUT stand. A 'Polarisation Control' unit is also connected to the 'RS CMU200 WCDMA Communication tester'.](52e112d1ba42a3c660bf62a0fea927d3_img.jpg) + +Figure 9.1: Example UMTS measurement set-up. The diagram is divided into two main areas: 'Anechoic room' (left) and 'Control Room' (right), separated by a dashed red line. In the Anechoic room, a 'DUT' (Device Under Test) is mounted on a stand with 'Roll axis' and 'Azimuth axis' rotation capabilities. A 'Dual Polarized Horn' antenna is positioned to receive signals from the DUT. A distance 'd' is indicated between the DUT and the antenna. The signal from the antenna goes to an 'RF Switch'. The RF Switch is connected to a 'Splitter'. One output of the splitter goes to an 'Uplink Freq. filter' and then to the 'RS CMU200 WCDMA Communication tester'. The other output of the splitter goes to a 'Downlink Freq. filter' and then back to the RF Switch. In the Control Room, a 'Computer with GPIB bus + control SW' is connected to the 'RS CMU200 WCDMA Communication tester' and to a 'Position Contr.' unit. The 'Position Contr.' unit is connected to the 'Roll axis' and 'Azimuth Axis' of the DUT stand. A 'Polarisation Control' unit is also connected to the 'RS CMU200 WCDMA Communication tester'. + +**Figure 9.1 Example UMTS measurement set-up. The RS CMU 200 should be replaced by BS/NB simulator.** + +The measurement is first initialised so that the mobile terminal is synchronised and registered with the pseudo-network emulated by the radio communications tester. To do that, signal from the Node B simulator is activated and an operator switches on the phone (in the anechoic room) so that the DUT will synchronise on start up. It is also possible to wait for a period of time if the mobile phone is already switched on, so it will synchronise itself. The mobile terminal is then fixed in the measurement position (in free space or beside the phantom). Since the established connection is a RMC, there is no need of answering a phone call (i.e. unlike in GSM). + +During the measurement the mobile terminal is controlled to transmit with full power. For all points on a spherical surface surrounding the mobile phone, the uplink received power is measured by the base station simulator. The base station simulator itself (Node B) should transmit at sufficiently high power level (e.g. 0 dBm) to ensure error-free connection in downlink. + +## 9.3 TRS measurement + +The TRS measurement is initialized in the same way as the TRP measurement: the mobile terminal is synchronised and registered with the pseudo-network emulated by the radio communications tester. + +The downlink algorithm (TRS) bases its measurement on BER measurements. The aim is to determine the needed received power at UE (so-called target power or Ptarget) to achieve the BER target (e.g. 1%). + +### Full TRS measurement: + +Sensitivity level is measured using 12.2kbps DL (and UL) reference channel for every position and polarization of the phone by sweeping the power transmitted by system simulator until the BER reaches target value of $1.0\% \pm 0.2\%$ using at least 20000 bits. + +In order to speed up the measurement the DL and UL bit rate can be increased to maximum supported by the UE. When higher than 12.2kbps data rate is used also the BER target can be changed to $10.0\% \pm 2.0\%$ using at least 20000 bits. If modified bit rate or BER target is used the effect of this modification () must be measured at least in 4 different positions for each measured frequency (low, mid high). Reference sensitivity measurements must be done in a sequential order for each position. + +The sensitivity level with faster method is done similarly as the full TRS measurement with 12.2kbps reference channel. The sensitivity level is measured with higher data rate and BER target for every position and polarization of the phone by sweeping the power transmitted by system simulator until the BER reaches target value. In addition to the higher data rate measurement the sensitivity level with 12.2kbps DL reference channel needs to be measured as in standard method in positions that are used in definition of the correction factor . + +Assuming $\Delta$ is difference in sensitivity (in dBs) between 12.2kbps DL reference channel ( $1.0\% \pm 0.2\%$ BER using at least 20000 bits) and higher data rate DL channel with higher BER target measured at frequency $a$ and position $b$ . $\Delta$ for frequency $a$ is then dB average of measured $\Delta$ s where $b=1 \dots b_{\max}$ and $b_{\max} \geq 4$ . + +At the end of the test sequence for each measured frequency must be added to the measured higher data rate sensitivity level to get the corresponding 12.2kbps 1% sensitivity level. + +For DUTs with more than one antenna port, all the tests should be performed using both (all) antennas simultaneously. + +## 9.4 Calibration of absolute levels + +In the calibration process, the measurement system's power levels are calibrated using a reference antenna with known gain at European 3G frequency band (1920 - 2170MHz). One technique is to feed the reference antenna from the RF output port of an applicable 3G UE and the maximum received power at the communication tester is recorded. See more details on the calibration measurement from Chapter 8 and Appendix F. + +# Annex A (informative): Estimation of measurement uncertainty + +Individual uncertainty contributions in the TRP and TRS measurements are discussed and evaluated in this Appendix. A technique for calculating the total measurement uncertainty is also presented. More detailed discussion on the uncertainty contributions can be found from [48] [49]. + +An important part of a standard measurement procedure is the identification of uncertainty sources and the evaluation of the overall measurement uncertainty. There are various individual uncertainty sources in the measurement procedure that introduce a certain uncertainty contribution to the final measurement result. The approach in this standard test procedure is that the test laboratories are not limited to using some specific instruments and antenna positioners, for example. However, a limit is set for the maximum overall measurement uncertainty. + +The TRP/TRS measurement procedure can be considered to include two stages. In Stage 1 the actual measurement of the 3-D pattern of the Device Under Test (DUT) is performed. In Stage 2 the calibration of the absolute level of the DUT measurement results is performed by means of using a calibration antenna whose absolute gain/radiation efficiency is known at the frequencies of interest. The uncertainty contributions related to TRP are listed in Table A.1 and the contributions related to TRS are in Table A.2. The uncertainty contributions are analyzed in the following paragraphs. + +The calculation of the uncertainty contribution is based on the ISO Guide to the expression of uncertainty in measurement [50] [51] [52] [53]. Each individual uncertainty is expressed by its Standard Deviation (termed here as 'standard uncertainty') and represented by symbol $U$ . The uncertainty contributions can be classified to two categories: Type-A uncertainties, which are statistically determined e.g. by repeated measurements, and Type-B uncertainties, which are derived from existing data e.g. data sheets. Several individual uncertainties are common in Stage 1 and Stage 2 and therefore cancel [48] [49]. + +The procedure of forming the uncertainty budget in TRP measurement is [48] [49]: + +- 1) Compile lists of individual uncertainty contributions for TRP measurement both in Stage 1 and Stage 2. +- 2) Determine the standard uncertainty of each contribution by + - a) Determining the distribution of the uncertainty (Gaussian, U-shaped, rectangular, etc.) + - b) Determining the maximum value of each uncertainty (unless the distributions is Gaussian) + - c) Calculating the standard uncertainty by dividing the uncertainty by $\sqrt{2}$ if the distribution is U-shaped, and by $\sqrt{3}$ if the distribution is rectangular. +- 3) Convert the units into decibel, if necessary. +- 4) Combine all the standard uncertainties by the Root of the Sum of the Squares (RSS) method. +- 5) Combine the total uncertainties in Stage 1 and Stage 2 also by the RSS method: + +$$u_c = \sqrt{u_{c,DUT\ measurement}^2 + u_{c,calibration\ measurement}^2}$$ +- 6) Multiply the result by an expansion factor of 1.96 to derive expanded uncertainty at 95% confidence level: $1.96 \cdot u_c$ + +Example uncertainty budgets are presented in Tables A.5, A.6, A.7 and A.8. + +**Table A.1: Uncertainty contributions in TRP measurement.** + +| Description of uncertainty contribution | Details in paragraph | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------| +| Stage 1, DUT measurement | | +| 1) Mismatch of receiver chain (i.e. between probe antenna and measurement receiver) | A.1-A.2 | +| 2) Insertion loss of receiver chain | A.3-A.5 | +| 3) Influence of the probe antenna cable | A.6 | +| 4) Uncertainty of the absolute antenna gain of the probe antenna | A.7 | +| 5) Measurement Receiver: uncertainty of the absolute level | A.8 | +| 6) Measurement distance:
a) offset of DUT phase center from axis(es) of rotation
b) mutual coupling between the DUT and the probe antenna
c) phase curvature across the DUT | A.9 | +| 7) Quality of quiet zone | A.10 | +| 8) DUT Tx-power drift | A.11 | +| 9) Uncertainty related to the use of phantoms: (applicable when a phantom is used):

If SAM head phantom is used:
a) uncertainty from using different types of SAM phantom
b) simulated tissue liquid uncertainty

If SAM head and hand phantoms are used:
a) uncertainty from using different types of SAM phantom
b) simulated tissue liquid uncertainty
c) uncertainty of dielectric properties and shape of the hand phantom

If a hand phantom is used:
a) uncertainty of dielectric properties and shape of the hand phantom

If a laptop ground plane phantom is used:
a) Uncertainty related to the use of the Laptop Ground Plane phantom | A.12 | +| 10) Coarse sampling grid | A.13 | +| 11) Random uncertainty (repeatability, including positioning uncertainty of the DUT against the SAM phantom or DUT plugged into the Laptop Ground Plane phantom) | A.14 | +| Stage 2 , Calibration measurement, network analyzer method, figure 7.5 | | +| 13) Uncertainty of network analyzer | A.15 | +| 14) Mismatch of receiver chain | A.1-A.2 | +| 15) Insertion loss of receiver chain | A.3-A.5 | +| 16) Mismatch in the connection of calibration antenna | A.1 | +| 17) Influence of the calibration antenna feed cable | A.6 | +| 18) Influence of the probe antenna cable | A.6 | +| 19) Uncertainty of the absolute gain of the probe antenna | A.7 | +| 20) Uncertainty of the absolute gain/ radiation efficiency of the calibration antenna | A.16 | +| 21) Measurement distance:
a) Offset of calibration antenna's phase center from axis(es) of rotation
b) Mutual coupling between the calibration antenna and the probe antenna
c) Phase curvature across the calibration antenna | A.9 | +| 22) Quality of quiet zone | A.10 | + +**Table A.2: Uncertainty contributions in TRS measurement.** + +| Description of uncertainty contribution | Details in paragraph | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| Stage 1, DUT measurement | | +| 1) Mismatch of transmitter chain (i.e. between probe antenna and base station simulator) | A.1-A.2 | +| 2) Insertion loss of transmitter chain | A.3-A.5 | +| 3) Influence of the probe antenna cable | A.6 | +| 4) Uncertainty of the absolute antenna gain of the probe antenna | A.7 | +| 5) Base station simulator: uncertainty of the absolute output level | A.17 | +| 6) BER measurement: output level step resolution | A.18 | +| 7) Statistical uncertainty of BER measurement | A.19 | +| 8) BER data rate normalization | A.20 | +| 9) Measurement distance:
a) offset of DUT phase center from axis(es) of rotation
b) mutual coupling between the DUT and the probe antenna
c) phase curvature across the DUT | A.9 | +| 10) Quality of quiet zone | A.10 | +| 11) DUT sensitivity drift | A.21 | +| 12) Uncertainty related to the use of phantoms: (applicable when a phantom is used):

If SAM head phantom is used:
a) uncertainty from using different types of SAM phantom
b) simulated tissue liquid uncertainty

If SAM head and hand phantoms are used:
a) uncertainty from using different types of SAM phantom
b) simulated tissue liquid uncertainty
c) uncertainty of dielectric properties and shape of the hand phantom

If a hand phantom is used:
a) uncertainty of dielectric properties and shape of the hand phantom

If a laptop ground plane phantom is used:
a) Uncertainty related to the use of the Laptop Ground Plane phantom | A.12 | +| 13) Coarse sampling grid | A.13 | +| 14) Random uncertainty (repeatability)
-positioning uncertainty of the DUT against the SAM or DUT plugged into the Laptop Ground Plane phantom | A.14 | +| Stage 2 , Calibration measurement, network analyzer method, figure 7.5 | | +| 16) Uncertainty of network analyzer | A.15 | +| 17) Mismatch in the connection of transmitter chain (i.e. between probe antenna and NA) | A.1-A.2 | +| 18) Insertion loss of transmitter chain | A.3-A.5 | +| 19) Mismatch in the connection of calibration antenna | A.1 | +| 20) Influence of the calibration antenna feed cable | A.6 | +| 21) Influence of the probe antenna cable | A.6 | +| 22) Uncertainty of the absolute gain of the probe antenna | A.7 | +| 23) Uncertainty of the absolute gain/radiation efficiency of the calibration antenna | A.16 | +| 24) Measurement distance:
a) Offset of calibration antenna's phase center from axis(es) of rotation
b) Mutual coupling between the calibration antenna and the probe antenna
c) Phase curvature across the calibration antenna | A.9 | +| 25) Quality of quiet zone | A.10 | + +If a network analyzer is not available for calibration measurement and a spectrum analyzer or a power meter is used, Stage 2 errors in Tables 1 and 2 must be replaced by Table 3. + +**Table A.3: Uncertainty contributions in Stage 2 (calibration measurement, spectrum analyzer method)** + +| Description of uncertainty contribution | Details in paragraph | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| Stage 2, calibration measurement, spectrum analyser method, figure 7.4 | | +| 1) Cable loss measurement uncertainty | A.22 | +| 2) Uncertainty from impedance mismatch between the signal generator and the calibration antenna | A.1 | +| 3) Impedance mismatch uncertainty between the measurement receiver and the probe antenna | A.1 | +| 4) Signal generator: uncertainty of the absolute output level | A.23 | +| 5) Signal generator: output level stability | A.24 | +| 6) Influence of the calibration antenna feed cable | A.6 | +| 7) Influence of the probe antenna cable | A.6 | +| 8) Insertion loss of the calibration antenna feed cable | A.25 | +| 9) Insertion loss of the probe antenna cable | A.3 | +| 10) Mismatch uncertainty: between signal generator and calibration antenna (if antenna attenuator is used) | A.1 | +| 11) Mismatch uncertainty: between measurement receiver and probe antenna (if antenna attenuator is used) | A.1 | +| 12) Insertion loss of the calibration antenna attenuator (if used) | A.26 | +| 13) Insertion loss of the probe antenna attenuator (if used) | A.4 | +| 14) Uncertainty of the absolute level of the measurement receiver | A.8 | +| 15) Uncertainty of the absolute gain of the probe antenna | A.7 | +| 16) Uncertainty of the absolute gain of the calibration antenna | A.16 | +| 18) Measurement distance:
a) Offset of calibration antenna's phase center from axis(es) of rotation
b) Mutual coupling between the calibration antenna and the probe antenna
c) Phase curvature across the calibration antenna | A.9 | +| 17) Quality of quiet zone | A.10 | + +**Table A.3a: Uncertainty contributions in TRP measurement for alternative test method.** + +| Description of uncertainty contribution | Details in paragraph | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------| +| Stage 1, DUT measurement | | +| 1) Mismatch of receiver chain (i.e. between fixed measurement antenna and measurement receiver) | A.1-A.2 | +| 2) Insertion loss of receiver chain | A.3-A.5 | +| 3) Influence of the fixed measurement antenna cable | A.6 | +| 4) Uncertainty of the absolute antenna gain of the fixed measurement antenna | A.7 | +| 5) Measurement Receiver: uncertainty of the absolute level | A.8 | +| 6) Chamber statistical ripple and repeatability | A.27 | +| 7) Additional power loss in EUT chassis | A.28 | +| 8) DUT Tx-power drift | A.11 | +| 9) Uncertainty related to the use of the SAM phantom:
a) uncertainty from using different types of SAM phantom
b) simulated tissue liquid uncertainty
c) effect of the DUT holder | A.12 | +| 10) Random uncertainty (repeatability, including positioning uncertainty of the DUT against the SAM phantom or DUT plugged into the Laptop Ground Plane phantom) | A.14 | +| 11) Uncertainty related to the use of the Laptop Ground Plane phantom | A.29 | +| Stage 2 , Calibration measurement, network analyzer method, figure 7.5 | | +| 12) Uncertainty of network analyzer | A.15 | +| 13) Mismatch of receiver chain | A.1-A.2 | +| 14) Insertion loss of receiver chain | A.3-A.5 | +| 15) Mismatch in the connection of calibration antenna | A.1 | +| 16) Influence of the calibration antenna feed cable | A.6 | +| 17) Influence of the fixed measurement antenna cable | A.6 | +| 18) Uncertainty of the absolute gain of the fixed measurement antenna | A.7 | +| 19) Uncertainty of the absolute gain/ radiation efficiency of the calibration antenna | A.16 | +| 20) Chamber statistical ripple and repeatability | A.27 | + +**Table A.3b: Uncertainty contributions in TRS measurement for alternative test method.** + +| Description of uncertainty contribution | Details in paragraph | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| Stage 1, DUT measurement | | +| 1) Mismatch of transmitter chain (i.e. between fixed measurement antenna and base station simulator) | A.1-A.2 | +| 2) Insertion loss of transmitter chain | A.3-A.5 | +| 3) Influence of the fixed measurement antenna cable | A.6 | +| 4) Uncertainty of the absolute antenna gain of the fixed measurement antenna | A.7 | +| 5) Base station simulator: uncertainty of the absolute output level | A.17 | +| 6) BER measurement: output level step resolution | A.18 | +| 7) Statistical uncertainty of BER measurement | A.19 | +| 8) BER data rate normalization | A.20 | +| 6) Chamber statistical ripple and repeatability | A.27 | +| 7) Additional power loss in EUT chassis | A.28 | +| 11) DUT sensitivity drift | A.21 | +| 12) Uncertainty related to the use of the SAM phantom:
a) uncertainty from using different types of SAM phantom
b) simulated tissue liquid uncertainty
c) effect of the DUT holder | A.12 | +| 13) Random uncertainty (repeatability)
- positioning uncertainty of the DUT against the SAM or DUT plugged into the Laptop Ground Plane phantom | A.14 | +| 14) Uncertainty related to the use of the Laptop Ground Plane phantom | A.29 | +| Stage 2 , Calibration measurement, network analyzer method, figure 7.5 | | +| 15) Uncertainty of network analyzer | A.15 | +| 16) Mismatch of receiver chain | A.1-A.2 | +| 17) Insertion loss of receiver chain | A.3-A.5 | +| 18) Mismatch in the connection of calibration antenna | A.1 | +| 19) Influence of the calibration antenna feed cable | A.6 | +| 20) Influence of the fixed measurement antenna cable | A.6 | +| 21) Uncertainty of the absolute gain of the fixed measurement antenna | A.7 | +| 22) Uncertainty of the absolute gain/ radiation efficiency of the calibration antenna | A.16 | +| 23) Chamber statistical ripple and repeatability | A.27 | + +If a network analyzer is not available for calibration measurement and a spectrum analyzer or a power meter is used, Stage 2 errors in Tables 1 and 2 shall be replaced by Table 3. + +**Table A.3c: Uncertainty contributions in Stage 2 (calibration measurement, spectrum analyzer method) for the alternative test method.** + +| Description of uncertainty contribution | Details in paragraph | +|----------------------------------------------------------------------------------------------------------------------|----------------------| +| Stage 2, calibration measurement, spectrum analyser method, figure 7.4 | | +| 1) Cable loss measurement uncertainty | A.22 | +| 2) Uncertainty from impedance mismatch between the signal generator and the calibration antenna | A.1 | +| 3) Impedance mismatch uncertainty between the measurement receiver and the fixed measurement antenna | A.1 | +| 4) Signal generator: uncertainty of the absolute output level | A.23 | +| 5) Signal generator: output level stability | A.24 | +| 6) Influence of the calibration antenna feed cable | A.6 | +| 7) Influence of the fixed measurement antenna cable | A.6 | +| 8) Insertion loss of the calibration antenna feed cable | A.25 | +| 9) Insertion loss of the fixed measurement antenna cable | A.3 | +| 10) Mismatch uncertainty: between signal generator and calibration antenna (if antenna attenuator is used) | A.1 | +| 11) Mismatch uncertainty: between measurement receiver and fixed measurement antenna (if antenna attenuator is used) | A.1 | +| 12) Insertion loss of the calibration antenna attenuator (if used) | A.26 | +| 13) Insertion loss of the fixed measurement antenna attenuator (if used) | A.4 | +| 14) Uncertainty of the absolute level of the measurement receiver | A.8 | +| 15) Uncertainty of the absolute gain of the fixed measurement antenna | A.7 | +| 16) Uncertainty of the absolute gain of the calibration antenna | A.16 | +| 19) Chamber statistical ripple and repeatability | A.27 | + +## A.1 Mismatch uncertainty between measurement receiver and the probe antenna + +If the same chain configuration (including the measurement receiver; the probe antenna and other elements) is used in both stages, the uncertainty is considered systematic and constant $\textcircled{P}$ 0.00dB value. + +If it is not the case, this uncertainty contribution has to be taken into account and determined by the following method. + +In a measurement configuration, when two elements (devices, networks...) are connected, if the matching is not ideal, there is an uncertainty in the RF level signal passing through the connection. The magnitude of the uncertainty depends on the VSWR at the junction of the two connectors. In practical measurement system there are probably several connections in a test set-up, they will all interact and contribute to the combined mismatch uncertainty. + +The total combined mismatch uncertainty is composed of 2 parts: + +- 1) The mismatch through the connector between two elements +- 2) The mismatch due to the interaction between two elements + +### A.1.1 Total combined mismatch uncertainty calculations + +#### A.1.1.1 Mismatch uncertainty through the connector between two elements: + +Hereunder, a measurement configuration: + +![Figure A.1: A block diagram showing a Measurement receiver (M.R) connected to Cable4. The reflection coefficient of the M.R is labeled as Γ_MR and the reflection coefficient of Cable4 is labeled as Γ_cable4. A dashed line extends from Cable4 to the right.](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +Figure A.1: A block diagram showing a Measurement receiver (M.R) connected to Cable4. The reflection coefficient of the M.R is labeled as Γ\_MR and the reflection coefficient of Cable4 is labeled as Γ\_cable4. A dashed line extends from Cable4 to the right. + +Figure A.1 + +$\Gamma_{MR}$ is the complex reflection coefficient of the Measurement Receiver + +$\Gamma_{cable4}$ is the complex reflection coefficient of the cable4 + +$S_{21}$ is the forward gain in the network between the two reflection coefficients of interest + +$S_{12}$ is the backward gain in the network between the two reflection coefficients of interest + +Note that $S_{21}$ and $S_{12}$ are set to 1 if the two parts are directly connected. + +The uncertainty limits of the mismatch are calculated by means of the following formula table 1 of [56]: + +Mismatch limits(% voltage) = + +These mismatch limits are divided by because of the U-shaped (table 1 of) [56] distribution of the mismatch uncertainty and give the following standard uncertainty: + +$$U_{mismatch} (\% \text{ voltage}) =$$ + +To convert this standard uncertainty in dB, we divide it by the standard uncertainty conversion factor (table 1 of) [56]: + +$$U_{mismatch}(\text{dB}) =$$ + +#### A.1.1.2 Mismatch uncertainty due to the interaction of several elements: + +Previously, we presented how to determine the mismatch uncertainty between two elements through the junction (connector). Now, we introduce the other type of mismatch uncertainty, which is a result of the interaction between several elements. + +Hereunder, a measurement configuration: + +![Figure A.2: A block diagram showing a Measurement Receiver (M.R) connected to Cable3, which is then connected to Cable4. The reflection coefficient of the M.R is labeled as Γ_MR. The reflection coefficient of Cable3 is labeled as Γ_cable3. The reflection coefficient of Cable4 is labeled as Γ_cable4. The forward gain of Cable3 is labeled as S_21 and the backward gain is labeled as S_12.](7a0eb8f3965b07bfadffaf8dbec102ef_img.jpg) + +Figure A.2: A block diagram showing a Measurement Receiver (M.R) connected to Cable3, which is then connected to Cable4. The reflection coefficient of the M.R is labeled as Γ\_MR. The reflection coefficient of Cable3 is labeled as Γ\_cable3. The reflection coefficient of Cable4 is labeled as Γ\_cable4. The forward gain of Cable3 is labeled as S\_21 and the backward gain is labeled as S\_12. + +Figure A.2 + +Firstly, we determine the mismatch uncertainty between junctions of the elements: + +Between the MR and the cable3: + +$$U_{mismatch1}(\text{dB}) =$$ + +Between the cable3 and the cable4: + +$$U_{mismatch2}(\text{dB}) =$$ + +$|S_{21}|$ and $|S_{12}|$ are set to 1 because there is no element between cable3 and cable 4. + +$$U_{mismatch1}(\text{dB}) =$$ + +$$U_{mismatch2}(\text{dB}) =$$ + +Each mismatch uncertainty due to the interaction between the measurement receiver and the cable4 is determined by means of the following formula (table 1 of) [56]: + +$$U_{mismatch\_interaction1}(\text{dB}) =$$ + +$|S_{21}|$ and $|S_{12}|$ are equal and correspond to the cable3 attenuation. + +$$U_{\text{mismatch\_interaction1}}(\text{dB}) =$$ + +We consider in the general case, the following measurement configuration: + +![Figure A.3: Measurement configuration diagram showing a chain of components: MR, Cable1, CableN, and Antenna. The MR is connected to Cable1 via a reflection coefficient Γ_MR. Cable1 is connected to CableN via S21cable1 and S12cable1. CableN is connected to the Antenna via a reflection coefficient Γ_antenna.](036c200da9b64c3eb5aae2d67bb53e1f_img.jpg) + +The diagram illustrates a measurement chain. It starts with a block labeled 'MR' on the left. An arrow points from 'MR' to a block labeled 'Cable1'. Above this arrow is the reflection coefficient $\Gamma_{MR}$ . From 'Cable1', an arrow points to a block labeled 'CableN'. Above this arrow are the scattering parameters $S_{21\text{cable1}}$ and $S_{12\text{cable1}}$ . From 'CableN', an arrow points to a block labeled 'Antenna' on the far right. Above this arrow is the reflection coefficient $\Gamma_{\text{antenna}}$ . There is a dotted line between 'Cable1' and 'CableN', indicating a series of cables. Above 'CableN' are the scattering parameters $S_{21\text{cableN}}$ and $S_{12\text{cableN}}$ . + +Figure A.3: Measurement configuration diagram showing a chain of components: MR, Cable1, CableN, and Antenna. The MR is connected to Cable1 via a reflection coefficient Γ\_MR. Cable1 is connected to CableN via S21cable1 and S12cable1. CableN is connected to the Antenna via a reflection coefficient Γ\_antenna. + +Figure A.3 + +In the general case, this uncertainty contribution can be calculated by: + +$$U_{\text{mismatch\_interaction\_N}}(\text{dB}) =$$ + +$|S_{21}|=|S_{12}|$ for passive elements (cables...) + +$$U_{\text{mismatch\_interaction\_N}}(\text{dB}) =$$ + +### A.1.2 Total combined mismatch uncertainty: + +The two kinds of mismatch uncertainty contributions are combined by the root-sum-squares (RSS) method to derive the total combined mismatch uncertainty. + +The total combined mismatch uncertainty is equal to: + +This formula shows that the uncertainty is frequency dependent by the way of the forward and the backward gains in the network between the two components. The uncertainty upon $|S_{21}|$ and $|S_{12}|$ increases with frequency. One can therefore expect for the UMTS band a higher mismatch uncertainty value than in the GSM and DCS bands. + +Note that for an anechoic chamber, horn antennas are usually used as probe antennas. There are two kinds of horn antennas: single-polarized and dual-polarized. With the second one, it is possible to measure the co-polarized and cross-polarized signals without any movement of the probe, which reduces the cable antenna uncertainty contribution and improves the measurement stability. + +To conduct the signals to the measurement receiver, the measurement system configuration using a dual-polarized horn antenna has to be completed with an RF Relay. This device will include new mismatch uncertainty contributions, which have to be determined with the previously presented calculation methods, completed by the RF relay parameters contributions, and described in the following. + +## A.2 Mismatch uncertainty of the RF relay + +If the same receiver chain configuration (including the measurement receiver; the probe antenna and other elements) is used in both stages, the uncertainty is considered systematic and constant $\textcircled{\ominus}$ 0.00dB value. + +If it is not the case, this uncertainty contribution has to be taken into account and determined by the following method. + +The following figure describes the RF Relay with its 'S' parameters and the complex reflection coefficient of the inputs and output: + +![Schematic diagram of an RF Relay system. A central 'RF Relay' block has three ports. Port 1 is connected to 'Input 1 device' through a connector with reflection coefficient Γ1. Port 2 is connected to 'Input 2 Device' through a connector with reflection coefficient Γ2. Port 3 is connected to 'Output Device' through a connector with reflection coefficient Γ3. S-parameter arrows indicate signal flow: S11 (reflection at port 1), S21 (transmission from port 1 to port 2), S31 (transmission from port 1 to port 3), S12 (transmission from port 2 to port 1), S22 (reflection at port 2), S32 (transmission from port 2 to port 3), S13 (transmission from port 3 to port 1), S23 (transmission from port 3 to port 2), and S33 (reflection at port 3).](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +Schematic diagram of an RF Relay system. A central 'RF Relay' block has three ports. Port 1 is connected to 'Input 1 device' through a connector with reflection coefficient Γ1. Port 2 is connected to 'Input 2 Device' through a connector with reflection coefficient Γ2. Port 3 is connected to 'Output Device' through a connector with reflection coefficient Γ3. S-parameter arrows indicate signal flow: S11 (reflection at port 1), S21 (transmission from port 1 to port 2), S31 (transmission from port 1 to port 3), S12 (transmission from port 2 to port 1), S22 (reflection at port 2), S32 (transmission from port 2 to port 3), S13 (transmission from port 3 to port 1), S23 (transmission from port 3 to port 2), and S33 (reflection at port 3). + +Figure A.4 + +The RF relay is used to switchover the cross and direct polarization signals from the probe antenna. To determine RF Relay mismatch uncertainty contributions, reflection coefficients for each port and the cross talk attenuation have to be known. + +The total combined mismatch uncertainty is composed of two parts: + +- 1) The mismatch uncertainty contributions when the RF Relay switches on the direct polarization signal +- 2) The mismatch uncertainty contributions when the RF Relay switches on the cross polarization signal + +Each part is composed of two types of uncertainties introduced in the previous paragraph: the mismatch through the connector between two elements and the mismatch due to the interaction between several elements. + +### A.2.1 First part: RF Relay switched on the co-polarized signal + +#### A.2.1.1 The mismatch through the connector between two elements + +Between the Input1 and the port1: + +$$U_{\text{mismatch1}}(\text{dB}) =$$ + +Between the port3 and the Output: + +$$U_{\text{mismatch2}}(\text{dB}) =$$ + +Between the Input2 and the port2: + +The RF Relay switchovers on the direct polarization signal. As a result, there is no mismatch uncertainty contribution. + +#### A.2.1.2 Mismatch due to the interaction between two elements or more + +Between the Input1 and the Output: + +$$U_{\text{interaction1}}(\text{dB}) =$$ + +Between the Input1 and the Input2: + +$$U_{\text{interaction2}}(\text{dB}) =$$ + +The RF Relay switchovers on the cross polarization signal. As a result; this uncertainty contribution is usually disregarded because of the high crosstalk attenuation which is characterized by 'S' parameters. If the crosstalk attenuation is low, this uncertainty contribution has to be considered. + +Between the Input2 and the Output: + +$$U_{\text{interaction3}}(\text{dB}) =$$ + +The RF Relay switchovers on the cross polarization signal. As a result; this uncertainty contribution is usually disregarded because of the high cross-talk attenuation, which is characterized by 'S' parameters. If the crosstalk attenuation is low, this uncertainty contribution has to be considered. + +### A.2.2 Second part: RF relay switched on the cross-polarized signal + +#### A.2.2.1 The mismatch through the connector between two elements + +Between the Input1 and the port1: + +The RF Relay switchovers on the direct polarization signal. As a result, there is no mismatch uncertainty contribution. + +Between the port3 and the Output: + +$$U_{\text{mismatch3}}(\text{dB}) =$$ + +Between the Input2 and the port2: + +$$U_{\text{mismatch4}}(\text{dB}) =$$ + +#### A.2.2.2 Mismatch due to the interaction between two elements or more + +Between the Input1 and the Output: + +$$U_{\text{interaction4}}(\text{dB}) =$$ + +The RF Relay switchovers on the cross polarization signal. As a result; this uncertainty contribution is usually disregarded because of the high crosstalk attenuation which is characterized by 'S' parameters. If the crosstalk attenuation is low, this uncertainty contribution has to be considered. + +Between the Input1 and the Input2: + +$$U_{\text{interaction5}}(\text{dB}) =$$ + +The RF Relay switchovers on the cross polarization signal. As a result; this uncertainty contribution is usually disregarded because of the high crosstalk attenuation which is characterized by 'S' parameters. If the crosstalk attenuation is low, this uncertainty contribution has to be considered. + +Between the Input2 and the Output: + +$$U_{\text{interaction6}}(\text{dB}) =$$ + +### A.2.3 Total combined mismatch uncertainty: + +Each non-zero mismatch uncertainty contribution from both parts (RF Relay switched on the cross and direct polarization signal) are combined by the root-sum-squares (RSS) method to derive the total combined mismatch uncertainty. + +The total combined mismatch uncertainty is equal to: + +If a RF Relay is used to drive the cross and direct polarization signals from the dual-polarized antenna, this total combined mismatch uncertainty has to be added with all the uncertainty measurement contributions for the total combined measurement uncertainty. + +## --- A.3 Insertion loss of the probe antenna cable + +If the probe antenna cable does not move between the calibration and the DUT measurement stage, the uncertainty due to the insertion loss of the cable is assumed to be systematic. Moreover, this uncertainty is common and constant in both stages and that is why this leads to 0.00dB value. + +If a different cable is used in the calibration measurement and in the DUT measurement, and the difference of the insertion loss is used in the calculations, then the overall combined standard uncertainty of the insertion loss measurement should be used in the uncertainty budget. The distribution of this uncertainty is assumed to be rectangular, in which case the standard uncertainty can be calculated as the maximum value/ $\sqrt{3}$ . + +## --- A.4 Insertion loss of the probe antenna attenuator (if used) + +See Insertion loss of the probe antenna cable + +If the probe antenna attenuator is used in both stages, the uncertainty is considered systematic and constant $\textcircled{/}$ 0.00dB value. + +## --- A.5 Insertion loss of the RF relays (if used) + +See Insertion loss of the probe antenna cable. + +If the RF relay is used in both stages, the uncertainty is considered systematic and constant $\textcircled{/}$ 0.00dB value. + +## --- A.6 Influence of the antenna cable + +### A.6.1 Probe antenna cable + +If the probe antenna is directional (i.e. peak gain $>+5\text{dBi}$ e.g. horn, LPDA, etc.) and the same probe antenna cable configuration is used for both stages, the uncertainty is considered systematic and constant $\textcircled{/}$ 0.00dB value. + +In other cases a technical study should be done. + +An ETSI technical report [55] (clause D.1.3.6) gives a discussion on the results obtained by testing a vertically polarized biconical antenna over a ground plane with differing RF cable configurations. + +### A.6.2 Calibration antenna cable + +If an efficiency calibration is performed, influence of the calibration antenna feed cable can be assumed to be negligible, due to data averaging. + +In the case of gain calibration, the influence of the calibration antenna feed cable must be assessed by measurements. A gain calibration measurement is repeated with a reasonably differing routing of the feed cable. Largest difference between the results is entered to the uncertainty budget with a rectangular distribution. + +## --- A.7 Absolute gain of the probe antenna + +The uncertainty appears in the both stages and it is thus considered systematic and constant $\textcircled{/}$ 0.00dB value. + +## A.8 Measurement receiver: uncertainty of absolute level + +The receiving device is used to measure the received signal level in TRP tests either as an absolute level or as a relative level. Receiving device used is typically a Base Station Simulator (BSS), spectrum analyzer (SA), or power meter (PM). Generally there occurs an uncertainty contribution from limited absolute level accuracy and non-linearity. + +## A.9 Measurement distance + +The uncertainty contribution from a finite measurement distance is estimated in three parts. + +### A.9.1 Offset of DUT phase centre from axis(es) of rotation + +In all the measurements defined in this test procedure the DUT and phantom combination is rotated about the ear reference point of SAM phantom, which is also assumed to be the location of the phase center in both angular directions of the measurements. + +For some turntables this may be practically impossible in which case a measurement uncertainty contribution can arise because the phase center will rotate on a non-zero radius about the center of rotation, thereby giving a variable measurement distance [48] [49]. Data averaging process may lead to a partial self-cancel of this uncertainty. + +The following formula is used to estimate this uncertainty contribution in stage 1: + +$$U_{\text{phase\_center\_limits}} \text{ (dB)} =$$ + +If a gain calibration is performed in Stage 2, the uncertainty contribution of calibration antenna's displacement is estimated with the previous formula. Misalignment can be estimated with following formula, + +$$U_{\text{misalignment}} \text{ (dB)} = ,$$ + +where is the misalignment angle between the calibration antenna and the probe antenna. The contribution shall be added to displacement error: + +$$U_{\text{cal}} \text{ (dB)} =$$ + +For an efficiency calibration with an omnidirectional calibration antenna, the $U_{\text{cal}}$ is calculated similarly as for gain calibration but the uncertainty may be divided by factor 2. This is due to correcting impact of data averaging in this type of calibration. + +### A.9.2 Mutual coupling + +In measurement of radio performances of UMTS mobile phones in speech mode, the mutual coupling uncertainty for this frequency band is a 0.00dB value (see annex A-2 in [57]). + +The 0.00dB value can be extended for the GSM, DCS and PCS band frequencies. + +### A.9.3 Phase curvature + +This uncertainty originates from the finite far-field measurement distance, which causes phase curvature across the DUT. If the measurement distance is $> 10\lambda$ , this error is assumed to be negligible. At 2 GHz $\lambda$ is 0.15 m, thus $10\lambda$ is 1.5 m. + +## A.10 Quality of quiet zone + +The uncertainty contribution of the reflectivity level of the anechoic chamber is determined from the average standard deviation of the electric field in the quiet zone. By repeating a free space VSWR measurement in 15-degree grid in elevation and azimuth, 264 standard deviation values in both polarizations are determined. From these values average standard deviation of electric field in the quiet zone can be calculated from the equation: + +Where + +is number of angular intervals in elevation, + +is number of angular intervals in azimuth and + +is elevation of single measurement. + +If an efficiency calibration with omnidirectional calibration antenna is performed, the effect of reflectivity level decreases in Stage 2 and may be divided by factor 2. This is due to correcting impact of data averaging in this type of calibration. Efficiency calibration done with sampling step $\leq 15^\circ$ , can be considered to have at least four independent samples. + +It's likely that asymmetry of the field probe will have a very small impact on this measurement uncertainty contributor, however, an upper bound to probe symmetry should be considered. + +## A.11 Tx-power drift of DUT + +A single point power reference measurement in the beginning and at the end of the measurement procedure is recommended to monitor the power drift of the DUT. Based on TX-power drift measurements for typical 3G UE, an uncertainty of 0.2 dB shall be entered to uncertainty budget with a rectangular distribution. If the drift measurement indicates larger drift, the actual drift shall be included to uncertainty. + +In order to minimize Tx-power drift error it's recommended to interleave sensitivity and power measurement of multiple channels. This spreads the measurements over a longer period, which helps to average the drift of the TX-power. + +Typical TX-power drifts of 3G UE, measured in a single angular point, DUT placed against phantom head are shown in Figure 5. + +![Figure A.5: Output power variation of typical 3G UE during battery life. The graph shows Power [dB] on the y-axis (from -0.6 to 0.6) versus Time [min] on the x-axis (from 0 to 165). Multiple lines represent different battery levels or conditions, showing a general downward trend in power over time, with some lines dropping significantly after 90 minutes.](557e5e0f7f146f1c887e9c15bf1654a3_img.jpg) + +The figure is a line graph showing the output power variation of a typical 3G UE over a period of 165 minutes. The y-axis is labeled 'Power [dB]' and ranges from -0.6 to 0.6 in increments of 0.2. The x-axis is labeled 'Time [min]' and ranges from 0 to 165 in increments of 15. There are several data series plotted. Most series start at 0 dB and show a slight downward trend, stabilizing around -0.1 dB after 45 minutes. One series shows a more pronounced drop, reaching approximately -0.3 dB at 90 minutes and continuing to decrease towards -0.5 dB at 165 minutes. Another series remains relatively flat near 0 dB throughout the duration. The overall trend indicates a gradual decrease in output power over time, likely due to battery discharge. + +Figure A.5: Output power variation of typical 3G UE during battery life. The graph shows Power [dB] on the y-axis (from -0.6 to 0.6) versus Time [min] on the x-axis (from 0 to 165). Multiple lines represent different battery levels or conditions, showing a general downward trend in power over time, with some lines dropping significantly after 90 minutes. + +Figure A.5. Output power variation of typical 3G UE during battery life. + +## A.12 Uncertainty related to the use of phantoms + +### A.12.1 Uncertainty from using different types of SAM phantom + +This uncertainty contribution originates from the fact that different laboratories may use the two different versions of SAM head: the SAM head phantom or the SAM phantom including the head and the shoulders. Based on the conclusions made in [18] [14] [25] [58], the standard SAM head is the specified phantom. However, the use of the other + +type of SAM is also allowed with the requirement that the resulting uncertainty contribution is taken into account in the uncertainty budget [48], [49]. + +### A.12.2 Simulated tissue liquid uncertainty + +This uncertainty will occur, if the laboratory uses a liquid which has dielectric parameters deviating more than $\pm 15\%$ of the target parameters given in chapter 5.1. + +### A.12.3 Uncertainty of dielectric properties and shape of the hand phantom + +The hand phantom makes a contribution to OTA measurement uncertainty due to the manufacturing tolerances of its dielectric properties and shape. The dielectric properties on the surface of the hand may differ from those of its interior, so both are included in the evaluation. The molded exterior surface of the hand shall be measured directly with an open-ended coaxial probe. The interior hand material is evaluated indirectly, by substituting a cube-shaped sample molded from the same material and having some exterior surfaces removed. Following procedure will be used to evaluate the dielectric properties of the hand phantom; + +1. Each hand shall be manufactured together with a reference cube of the same material. The sides of the reference cube shall be not less than 40 mm in length. +2. The molded surface on three orthogonal sides of the cube shall be sliced away to a depth of at least 3 mm, in order to expose interior material for evaluation. The remaining three sides of the cube shall be left untreated. +3. Relative permittivity and conductivity shall be measured at ten different points on each of the three cut, exposed surfaces of the reference cube, and the combined interior averages ( $\bar{\varepsilon}_{int\ avg}$ , $\bar{\sigma}_{int\ avg}$ , 30 points) and standard deviations ( $\bar{\varepsilon}_{int\ std}$ , $\bar{\sigma}_{int\ std}$ , 30 points) shall be calculated. Individual interior averages for each of these three sides ( $\bar{\varepsilon}_{int\ i}$ , $\bar{\sigma}_{int\ i}$ , 10 points) shall also be calculated. +4. Relative permittivity and conductivity shall be measured at ten points on the hand phantom exterior. A measurement point shall be located to each fingertip or as close to the tip as applicable. One measurement point shall be located to the back of the hand and one to the inner surface of wrist area. The exterior averages ( $\bar{\varepsilon}_{ext\ avg}$ , $\bar{\sigma}_{ext\ avg}$ , 10 points) and standard deviations ( $\bar{\varepsilon}_{ext\ std}$ , $\bar{\sigma}_{ext\ std}$ , 10 points) calculated accordingly. +5. The total averages ( $\bar{\varepsilon}_{avg}$ , $\bar{\sigma}_{avg}$ ) shall be calculated as the average of exterior and interior values by either evaluating all data points or using equations: $\bar{\varepsilon}_{avg} = \frac{\bar{\varepsilon}_{ext\ avg} + 3 \cdot \bar{\varepsilon}_{int\ avg}}{4}$ , $\bar{\sigma}_{avg} = \frac{\bar{\sigma}_{ext\ avg} + 3 \cdot \bar{\sigma}_{int\ avg}}{4}$ +6. The total standard deviations ( $\bar{\varepsilon}_{std}$ , $\bar{\sigma}_{std}$ ) shall be calculated as the statistical combination of exterior and interior values by either evaluating all data points or using equations: + +$$\bar{\varepsilon}_{std} = \sqrt{\frac{1}{4} \left( \bar{\varepsilon}_{ext\ std}^2 + \bar{\varepsilon}_{ext\ avg}^2 + 3 \cdot \left( \bar{\varepsilon}_{int\ std}^2 + \bar{\varepsilon}_{int\ avg}^2 \right) \right) - \bar{\varepsilon}_{avg}^2}$$ + +$$\bar{\sigma}_{std} = \sqrt{\frac{1}{4} \left( \bar{\sigma}_{ext\ std}^2 + \bar{\sigma}_{ext\ avg}^2 + 3 \cdot \left( \bar{\sigma}_{int\ std}^2 + \bar{\sigma}_{int\ avg}^2 \right) \right) - \bar{\sigma}_{avg}^2}$$ + +7. The hands are acceptable for radiated performance testing, i.e., meet the minimal requirements, if + - a. $\bar{\varepsilon}_{avg}$ deviate by less than 15% from the target values + - b. $\bar{\sigma}_{avg}$ deviate by less than 25% from the target values + - c. the difference between the averaged permittivity of each 10-point interior surface $\bar{\varepsilon}_{int\ avg}$ deviates by less than 10% and $\bar{\varepsilon}_{ext\ avg}$ by less than 20% from the total average $\bar{\varepsilon}_{avg}$ + - d. the difference between the averaged conductivity of each 10-point interior surface $\bar{\sigma}_{int\ avg}$ deviates by less than 20% and $\bar{\sigma}_{ext\ avg}$ by less than 30% from the total average $\bar{\sigma}_{avg}$ + +- e. the standard deviation of the combined measurements (30 interior points and 10 exterior points) is less than 20% for permittivity $\varepsilon_{std}$ and less than 40% for conductivity $\sigma_{std}$ +8. For the hands meeting the minimal requirements of step 7, the following approximations shall be used to determine the hand uncertainty due to dielectric properties. + +$$U_{\varepsilon}[dB] = c_1 * \left[ 10 * \log_{10} \left( 1 + \left| \frac{\sqrt{\Delta\varepsilon_{avg}^2 + \varepsilon_{unc}^2 + (a_1\varepsilon_{std})^2}}{\varepsilon} \right| \right) \right]$$ + +$$U_{\sigma}[dB] = c_2 * \left[ 10 * \log_{10} \left( 1 + \left| \frac{\sqrt{\Delta\sigma_{avg}^2 + \sigma_{unc}^2 + (a_1\sigma_{std})^2}}{\sigma} \right| \right) \right]$$ + +$\Delta\varepsilon_{avg}$ , $\Delta\sigma_{avg}$ , $\varepsilon_{std}$ , $\sigma_{std}$ are the values determined as defined above and $\varepsilon_{unc}$ and $\sigma_{unc}$ are expanded measurement uncertainties ( $k = 2$ ) of the dielectric parameter measurement method. The cube will be provided together with the hand such that the user can evaluate if the interior (cube) properties of the hand has degenerated over time by performing the test above. Coefficient $c_1 = 0.78$ , $c_2 = 0.39$ and $a_1 = 0.50$ were determined by numeric simulations. + +In case the hand phantoms are manufactured within CAD models referenced in chapter 5, the tolerance is 2% and therefore the effects shape errors are negligible. If the tolerance is larger, a numerical study must be conducted. + +### A.12.4 Uncertainty from using different types of Laptop Ground Plane phantom + +This uncertainty contribution originates from the fact that different laboratories may use different variations of Laptop Ground Plane phantom. Based on Section 5.1.3, the standard Laptop Ground Plane is the specified phantom. + +## A.13 Coarse sampling grid + +Degreasing of sampling density to finite amount of samples affects the measurement uncertainty by two different errors. First is due to inadequate number of samples and second is a systematic discrimination approximation error in TRP and TRS equations. + +Figure A.6 shows simulated sampling grid errors for typical 3G UE. Approximation error is not included. Simulations are based on thin plate surface interpolation of real radiation patterns, measured beside a phantom head. + +![Figure A.6: Simulated TPR/TRS error as a function of sampling grid. The graph shows the Standard Deviation of TRP/TRS [dB] on the y-axis (ranging from 0.00 to 0.25) versus Sample Step [°] on the x-axis (ranging from 0 to 45). Multiple lines represent different simulation scenarios, all showing a sharp increase in error as the sample step increases beyond 15 degrees, with the highest error reaching approximately 0.25 dB at 45 degrees.](b9248cd9761f4c0fde1c623f92cb95a7_img.jpg) + +**Sampling Grid Error** + +| Sample Step [°] | Standard Deviation of TRP/TRS [dB] (Range) | +|-----------------|--------------------------------------------| +| 0 | 0.00 | +| 5 | 0.00 | +| 10 | 0.00 - 0.01 | +| 15 | 0.01 - 0.02 | +| 20 | 0.02 - 0.04 | +| 25 | 0.04 - 0.07 | +| 30 | 0.06 - 0.10 | +| 35 | 0.10 - 0.16 | +| 40 | 0.16 - 0.22 | +| 45 | 0.20 - 0.25 | + +Figure A.6: Simulated TPR/TRS error as a function of sampling grid. The graph shows the Standard Deviation of TRP/TRS [dB] on the y-axis (ranging from 0.00 to 0.25) versus Sample Step [°] on the x-axis (ranging from 0 to 45). Multiple lines represent different simulation scenarios, all showing a sharp increase in error as the sample step increases beyond 15 degrees, with the highest error reaching approximately 0.25 dB at 45 degrees. + +Figure A.6. Simulated TPR/TRS error as a function of sampling grid. + +The offset of systematic approximation error can be expressed by using formula + +where + +is number of angular intervals in elevation, + +is elevation. + +![Figure A.7: Sampling Grid Error. A line graph showing the Offset of TRP/TRS [dB] on the y-axis (ranging from -0.25 to 0) versus Sample Step [°] on the x-axis (ranging from 0 to 45). The curve starts at 0 dB at 0° and decreases, reaching approximately -0.23 dB at 45°. The data points are marked with open circles.](a26b4f52392209236513dd503db41339_img.jpg) + +| Sample Step [°] | Offset of TRP/TRS [dB] | +|-----------------|------------------------| +| 0 | 0.00 | +| 2.5 | 0.00 | +| 5 | 0.00 | +| 7.5 | -0.01 | +| 10 | -0.01 | +| 15 | -0.03 | +| 20 | -0.06 | +| 25 | -0.10 | +| 30 | -0.15 | +| 35 | -0.20 | +| 40 | -0.23 | +| 45 | -0.23 | + +Figure A.7: Sampling Grid Error. A line graph showing the Offset of TRP/TRS [dB] on the y-axis (ranging from -0.25 to 0) versus Sample Step [°] on the x-axis (ranging from 0 to 45). The curve starts at 0 dB at 0° and decreases, reaching approximately -0.23 dB at 45°. The data points are marked with open circles. + +Figure A.7. Approximation error of TRP/TRS. + +The $10^\circ$ or $15^\circ$ sampling grid used in TRP measurements has been shown to introduce only very small differences as compared to the results obtained with denser grids, so with that sampling grid the uncertainty contribution can be assumed negligible [36]. + +When using sample step size of $15^\circ - 30^\circ$ , standard uncertainty of 0.15dB can be assumed to cover errors. If step size $>30^\circ$ is used, larger uncertainty should be considered. + +Note: the simulation results presented here are not usable for irregular sampling grids or in the case of MEG/MERS. + +## A.14 Random uncertainty + +The random uncertainty characterizes the undefined and miscellaneous effects which cannot be forecasted. One can estimate this type of uncertainty with a repeatability test by making a series of repeated measurement with a reference DUT without changing anything in the measurement set-up. + +The random uncertainty differs from one laboratory to another. Moreover, each DUT has its own electromagnetic behaviour and random uncertainty. Some uncertainty also occurs from the positioning of the DUT against the SAM phantom, as the DUT cannot be attached exactly in the same way every time. This uncertainty depends on how much the DUT's positioning against the SAM phantom and hand phantoms varies from the specified testing positions. It is noted that the uncertainty of the phone positioning depends on the phone holder and the measurement operator and is in fact difficult to distinguish from random uncertainty. Some uncertainty also occurs from the positioning of the DUT plugged into the Laptop Ground Plane phantom, as the DUT may not be plugged into the USB connector and positioned exactly in the same way every time. This uncertainty depends on how much the DUT's position plugged into the Laptop Ground Plane phantom varies from the specified plug-in position. Therefore, the positioning uncertainty is included in random uncertainty. A study on the influence of misalignment errors to the measurement uncertainty has been presented in [72]. + +To estimate this uncertainty for the SAM phantom, it is suggested to perform at least five evaluations of TRP/TRS whereby the device shall be dismounted and newly positioned with a fully charged battery before each test. This + +measurement set has to be carried out in mid channel of lowest and highest frequency bands utilized by the testing lab, for at least three phones with different type of mechanical design. The values have to be normalized by the mean for each measurement set. As a result the uncertainty contribution entered to uncertainty budget is the difference between the maximum and minimum normalized value. + +With head and hand phantoms, random uncertainty evaluation may be done separately for each measurement configuration i.e. head only, browsing mode or speech mode. A speech mode random uncertainty evaluation, where both head and hand phantoms are used, can reasonably be considered to be the worst-case scenario and thus random uncertainties in other configurations to be less. + +To estimate this uncertainty for the Laptop Ground Plane phantom, it is suggested to perform at least five evaluations of TRP/TRS for the plug-in position whereby the device shall be dismounted and newly positioned before each tests. This measurement set has to be carried out in mid channel of lowest and highest frequency bands utilized by the testing lab, for at least three USBs with different type of mechanical design. The values have to be normalized by the mean for each measurement set. As a result the uncertainty contribution entered to uncertainty budget is the difference between the maximum and minimum normalized value. + +## --- A.15 Uncertainty of network analyzer + +This uncertainty includes the all uncertainties involved in the S21 measurement with a network analyzer, and will be calculated from the manufacturer's data in logs with a rectangular distribution, unless otherwise informed, (see clause 5.1.2 in [56]). + +## --- A.16 Uncertainty of the gain/efficiency of the calibration antenna + +The calibration antenna only appears in Stage 2. Therefore, the gain/efficiency uncertainty has to be taken into account. + +This uncertainty will be calculated from the manufacturer's data in logs with a rectangular distribution, unless otherwise informed (see clause 5.1.2 in [56]). + +If the manufacturer's data do not give the information, the value has to be checked, see annex A-12 in [57] + +## --- A.17 Base station simulator: uncertainty of the absolute level + +The transmitter device (typically a BS Simulator) is used to drive a signal to the horn antenna in sensitivity tests either as an absolute level or as a relative level. Receiving device used is typically a UE/MS. Generally there occurs uncertainty contribution from limited absolute level accuracy and non-linearity of the BS Simulator. + +For practical reasons, the calibration measurement (Stage 2) should be only performed with the probe antenna as a receiver. Hence, the uncertainty on the absolute level of the transmitter device cannot be assumed as systematic. This uncertainty should be calculated from the manufacturer's data in logs with a rectangular distribution, unless otherwise informed (see clause 5.1.2 in [56]). Furthermore, the uncertainty of the non-linearity of the device is included in the absolute level uncertainty. + +## --- A.18 BER measurement: output level step resolution + +When output power of the BS simulator is swept to reach the BER target, used power step resolution creates this uncertainty. Output power step used in the BER measurement is divided by factor 2 to obtain the uncertainty with rectangular distribution. + +## A.19 Statistical uncertainty of the BER measurement + +To study statistical uncertainty of BER measurement, see ETSI document TR 100 028-1, section 6.6 [55]. For a BER target of $1\% \pm 0.2\%$ using 20000 bits, uncertainty of 0.19 dB for a single measurement can be used. Using a BER target of $10\% \pm 2\%$ with 20000 tested bits will lead to uncertainty of 0.46dB/single measurement. + +For a full TRS measurement with a regular sampling grid, the statistical uncertainty can be approximated by using the following formula: + +$$u_{TRS} = \frac{u_{single}}{\sqrt{n}},$$ + +Where + +$u_{single}$ is the statistical uncertainty of single measurement, + +$n$ is the number of measurements. + +## A.20 BER data rate normalization uncertainty + +This uncertainty occurs only when a higher data rate than 12.2kbps is used to speed up TRS measurement. It can be calculated using following formula: + +$$u_{norm} = \sqrt{\frac{u_{ref}^2 + u_{higher}^2}{n}},$$ + +Where + +$u_{ref}$ is the statistical uncertainty of the used reference measurement, + +$u_{higher}$ is the statistical uncertainty of the higher data rate measurement, + +$n$ Is the number of measured reference points. + +## A.21 DUT sensitivity drift + +Due to statistical uncertainty of BER measurement, drift in the TRS can not be monitored similary to TRP. An uncertainty value of 0.2dB can be used, or the TRS drift should be measured, with a setup corresponding to the actual TRS measurement. + +## A.22 Cable loss measurement uncertainty + +Before performing the calibration, cable losses have to be measured. This measurement includes a standard uncertainty, which is composed of the mismatch, and the insertion loss uncertainties. In the calibration measurement, the transmitter part is composed with the calibration antenna, cables, and signal generator. The receiver part is composed with the probe antenna, cables, and measurement device. + +The cable loss of transmitter and receiver parts should be measured separately. By this way, the cable losses will be compliant with the cable routing of the calibration stage. On the opposite, if the cable losses were measured together at the same time, the measured values would include errors from miscellaneous mismatch contributions, which do not appear in the cable routing of the calibration stage. + +The cable loss measurement uncertainty is the result of the RSS of the uncertainty contributions listed in Table A.4. + +**Table A.4. Uncertainty contributions in the cable loss measurement.** + +| Description of uncertainty contribution | Standard Uncertainty (dB) | +|------------------------------------------------------|----------------------------------| +| Mismatch uncertainty of cable(s) receiver part | | +| Insertion loss of the cable(s) receiver part | | +| Measurement device: absolute level uncertainty | | +| Measurement device: linearity | | +| Mismatch uncertainty of cable(s) transmitter part | | +| Insertion loss of the cable(s) transmitter part | | +| Signal generator: absolute output level uncertainty | | +| Signal generator: output level stability uncertainty | | +| Cable loss measurement uncertainty (RSS) | | + +## --- A.23 Signal generator: uncertainty of the absolute output level + +The signal generator is only used at this stage. It substitutes the DUT by feeding the calibration antenna with a known power level. The use of this signal generator introduces an uncertainty on the absolute output level. + +This uncertainty will be calculated from the manufacturer's data in logs with a rectangular distribution (see clause 5.1.2 in [56]). + +## --- A.24 Signal generator: output level stability + +The uncertainty on the output level stability has to be taken into account only when the uncertainty of the absolute level is not considered. + +This uncertainty will be calculated from the manufacturer's data in logs with a rectangular distribution (see clause 5.1.2 in [56]). + +## --- A.25 Insertion loss: calibration antenna feed cable + +The feed cable of the calibration antenna only appears in Stage 2. As a result, this uncertainty has to be taken into account. + +This uncertainty will be measured or calculated from the manufacturer's data in logs with a rectangular distribution (see clause 5.1.2 in [56]). + +## --- A.26 Insertion loss: calibration antenna attenuator (if used) + +If a calibration antenna attenuator is used, it only appears in Stage 2. As a result, this uncertainty has to be taken into account. + +This uncertainty will be calculated from the manufacturer's data in logs with a rectangular distribution (see clause 5.1.2 in [56]). + +## --- A.27 Chamber Statistical Ripple and Repeatability + +The uncertainty due to chamber statistics is determined by repeated calibration measurements as described in Annex G. This uncertainty contribution is a composite value consisting of most of the specific reverberation chamber contributions, such as limited number of modes and mode-stirring techniques. + +The uncertainty contribution value shall be determined by measurements as described in Annex G and be assumed to have a normal distribution. + +## --- A.28 Additional Power Loss in EUT Chassis + +When the EUT is small and do not add noticeable loss to the chamber, the calibration procedure outlined in section E.3, is performed without the EUT present in the chamber. The possible difference in average chamber transmission level between the EUT measurement and the reference measurement must in this case be considered in the uncertainty evaluation. + +The uncertainty value for this contribution can be tested empirically by choosing a unit within a set of samples which is considered to incur the highest amount of loss (normally the largest unit), and measure the average transmission loss in the chamber with and without the test unit present in the chamber. The difference between the two cases shall be used in the uncertainty calculation and the distribution should be assumed to be rectangular. + +Alternatively, a fixed value of 0.2 dB with a rectangular distribution can be used in the uncertainty calculations. + +Table A.5. Example of uncertainty budget for head only TRP measurement. + +| Uncertainty Source | Comment | Uncertainty Value [dB] | Prob Distr | Div | ci | Standard Uncertainty y [dB] | +|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|------------------------|------------|-----|----|-----------------------------| +| STAGE 1 (DUT measurement) | | | | | | | +| 1) Mismatch of receiver chain | $\Gamma_{\text{power meter}} < 0.05$ $\Gamma_{\text{probe antenna connection}} < 0.16$ | 0.05 | N | 1 | 1 | 0.05 | +| 2) Insertion loss of receiver chain | Systematic with Stage 2 (=> cancels) | 0 | R | | 1 | 0 | +| 3) Influence of the probe antenna cable | Systematic with Stage 2 (=> cancels) | 0 | R | | 1 | 0 | +| 4) Absolute antenna gain of the probe antenna | Systematic with Stage 2 (=> cancels) | 0 | R | | 1 | 0 | +| 5) Measurement Receiver: uncertainty of the absolute level | Power Meter | 0.06 | R | | 1 | 0.03 | +| 6) Measurement distance | $\Delta d = 0.05\text{m}$ | 0.14 | R | | 1 | 0.08 | +| a) Offset of DUT phase center | | | | | | | +| 7) Quality of quiet zone | Standard deviation of E-field in QZ measurement | 0.5 | N | 1 | 1 | 0.5 | +| 8) DUT Tx-power drift | Drift | 0.2 | R | | 1 | 0.12 | +| 9) Uncertainty related to the use of SAM phantom | Standard SAM head with standard tissue simulant | 0 | R | | 1 | 0 | +| 10) Coarse sampling grid | Negligible, used = $15^\circ$ and $= 15^\circ$ | 0 | N | 1 | 1 | 0 | +| 11) Repeatability | Monoblock, clamshell, slide design | 0.4 | R | | 1 | 0.23 | +| STAGE 2 (Calibration) | | | | | | | +| 13) Uncertainty of network analyzer | Manufacturer's uncertainty calculator, covers whole NA setup | 0.5 | R | | 1 | 0.29 | +| 14) Mismatch of receiver chain | Taken in to account in NA setup uncertainty | 0 | U | | 1 | 0 | +| 15) Insertion loss of receiver chain | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 16) Mismatch in the connection of calibration antenna | Taken in to account in NA setup uncertainty | 0 | U | | 1 | 0 | +| 17) Influence of the feed cable of the calibration antenna | Gain calibration with a dipole | 0.3 | R | | 1 | 0.17 | +| 18) Influence of the probe antenna cable | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 19) Uncertainty of the absolute gain of the probe antenna | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 20) Uncertainty of the absolute gain of the calibration antenna | Calibration certificate | 0.5 | R | | 1 | 0.29 | +| 21) Measurement distance: Calibration antenna's displacement and misalignment | $d = 3\text{m}$ , $\Delta d = 0.05\text{m}$ , $\theta = 2^\circ$ | 0.29 | R | | 1 | 0.17 | +| 22) Quality of quiet zone | Standard deviation of e-field in QZ measurement, Gain calibration | 0.5 | N | 1 | 1 | 0.5 | +| Combined standard uncertainty | | | | | | 0.89 | +| Expanded uncertainty (Confidence interval of 95 %) | | | | | | 1.75 | + +**Table A.5A. Example of uncertainty budget for TRP head+hand (speech mode) measurement.** + +| Uncertainty Source | Comment | Uncertainty Value [dB] | Prob Distr | Div | ci | Standard Uncertainty [dB] | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|------------------------|------------|-----|----|---------------------------| +| STAGE 1 (DUT measurement) | | | | | | | +| 1) Mismatch of receiver chain | $\Gamma_{\text{power meter}} < 0.05$ $\Gamma_{\text{probe antenna connection}} < 0.16$ | 0.05 | N | 1 | 1 | 0.05 | +| 2) Insertion loss of receiver chain | Systematic with Stage 2 (=> cancels) | 0 | R | | 1 | 0 | +| 3) Influence of the probe antenna cable | Systematic with Stage 2 (=> cancels) | 0 | R | | 1 | 0 | +| 4) Absolute antenna gain of the probe antenna | Systematic with Stage 2 (=> cancels) | 0 | R | | 1 | 0 | +| 5) Measurement Receiver: uncertainty of the absolute level | Power Meter | 0.06 | R | | 1 | 0.03 | +| 6) Measurement distance
a) Offset of DUT phase center | $\Delta d = 0.05\text{m}$ | 0.14 | R | | 1 | 0.08 | +| 7) Quality of quiet zone | Standard deviation of E-field in QZ measurement | 0.5 | N | 1 | 1 | 0.5 | +| 8) DUT Tx-power drift | Drift | 0.2 | R | | 1 | 0.12 | +| 9) Uncertainty related to the use of the SAM head and hand phantoms:
a) uncertainty from using different types of SAM phantom
b) simulated tissue liquid uncertainty
c) uncertainty of dielectric properties and shape of the hand phantom | Standard SAM head with standard tissue simulant
$U_{\epsilon}[\text{dB}] = 0.20$
$U_{\sigma}[\text{dB}] = 0.15$ | 0.32 | R | | 1 | 0.19 | +| 10) Coarse sampling grid | Negligible, used = $15^{\circ}$ and $= 15^{\circ}$ . | 0 | N | 1 | 1 | 0 | +| 11) Repeatability of speech mode | Monoblock, clamshell and PDA design used for testing | 1.04 | R | | 1 | 0.6 | +| STAGE 2 (Calibration) | | | | | | | +| 12) Uncertainty of network analyzer | Manufacturer's uncertainty calculator, covers whole NA setup | 0.5 | R | | 1 | 0.29 | +| 13) Mismatch of receiver chain | Taken in to account in NA setup uncertainty | 0 | U | | 1 | 0 | +| 14) Insertion loss of receiver chain | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 15) Mismatch in the connection of calibration antenna | Taken in to account in NA setup uncertainty | 0 | U | | 1 | 0 | +| 16) Influence of the feed cable of the calibration antenna | Gain calibration with a dipole | 0.3 | R | | 1 | 0.17 | +| 17) Influence of the probe antenna cable | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 18) Uncertainty of the absolute gain of the probe antenna | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 19) Uncertainty of the absolute gain of the calibration antenna | Calibration certificate | 0.5 | R | | 1 | 0.29 | +| 20) Measurement distance: Calibration antenna's displacement and misalignment | $d = 3\text{m}$ , $\Delta d = 0.05\text{m}$ , $\theta = 2^{\circ}$ | 0.29 | R | | 1 | 0.17 | +| 21) Quality of quiet zone | Standard deviation of e-field in QZ measurement, Gain calibration | 0.5 | N | 1 | 1 | 0.5 | +| Combined standard uncertainty | | | | | | 1.07 | +| Expanded uncertainty (Confidence interval of 95 %) | | | | | | 2.10 | + +Table A.5B. Example of uncertainty budget for TRP hand only (browsing mode) measurement. + +| Uncertainty Source | Comment | Uncertainty Value [dB] | Prob Distr | Div | ci | Standard Uncertainty [dB] | +|------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|------------------------|------------|-----|----|---------------------------| +| STAGE 1 (DUT measurement) | | | | | | | +| 1) Mismatch of receiver chain | $\Gamma_{\text{power meter}} < 0.05$ $\Gamma_{\text{probe antenna connection}} < 0.16$ | 0.05 | N | 1 | 1 | 0.05 | +| 2) Insertion loss of receiver chain | Systematic with Stage 2 (=> cancels) | 0 | R | | 1 | 0 | +| 3) Influence of the probe antenna cable | Systematic with Stage 2 (=> cancels) | 0 | R | | 1 | 0 | +| 4) Absolute antenna gain of the probe antenna | Systematic with Stage 2 (=> cancels) | 0 | R | | 1 | 0 | +| 5) Measurement Receiver: uncertainty of the absolute level | Power Meter | 0.06 | R | | 1 | 0.03 | +| 6) Measurement distance
a) Offset of DUT phase center | $\Delta d = 0.05\text{m}$ | 0.14 | R | | 1 | 0.08 | +| 7) Quality of quiet zone | Standard deviation of E-field in QZ measurement | 0.5 | N | 1 | 1 | 0.5 | +| 8) DUT Tx-power drift | Drift | 0.2 | R | | 1 | 0.12 | +| 9) Uncertainty related to the use of hand phantom: Uncertainty of dielectric properties and shape of the hand phantom. | $U_{\epsilon}[\text{dB}] = 0.20$
$U_{\sigma}[\text{dB}] = 0.15$ | 0.32 | R | | 1 | 0.19 | +| 10) Coarse sampling grid | Negligible, used = $15^\circ$ and $= 15^\circ$ . | 0 | N | 1 | 1 | 0 | +| 11) Repeatability of browsing mode | Monoblock, clamshell and PDA design used for testing | 0.81 | R | | 1 | 0.22 | +| STAGE 2 (Calibration) | | | | | | | +| 12) Uncertainty of network analyzer | Manufacturer's uncertainty calculator, covers whole NA setup | 0.5 | R | | 1 | 0.29 | +| 13) Mismatch of receiver chain | Taken in to account in NA setup uncertainty | 0 | U | | 1 | 0 | +| 14) Insertion loss of receiver chain | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 15) Mismatch in the connection of calibration antenna | Taken in to account in NA setup uncertainty | 0 | U | | 1 | 0 | +| 16) Influence of the feed cable of the calibration antenna | Gain calibration with a dipole | 0.3 | R | | 1 | 0.17 | +| 17) Influence of the probe antenna cable | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 18) Uncertainty of the absolute gain of the probe antenna | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 19) Uncertainty of the absolute gain of the calibration antenna | Calibration certificate | 0.5 | R | | 1 | 0.29 | +| 20) Measurement distance: Calibration antenna's displacement and misalignment | $d = 3\text{m}$ , $\Delta d = 0.05\text{m}$ , $\theta = 2^\circ$ | 0.29 | R | | 1 | 0.17 | +| 21) Quality of quiet zone | Standard deviation of e-field in QZ measurement, Gain calibration | 0.5 | N | 1 | 1 | 0.5 | +| Combined standard uncertainty | | | | | | 1.0 | +| Expanded uncertainty (Confidence interval of 95 %) | | | | | | 1.96 | + +**Table A.5C. Example of uncertainty budget for TRP measurement with laptop ground plane phantom.** + +| Uncertainty Source | Comment | Uncertainty Value [dB] | Prob Distr | Div | ci | Standard Uncertainty [dB] | +|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|------------------------|------------|-----|----|---------------------------| +| STAGE 1 (DUT measurement) | | | | | | | +| 1) Mismatch of receiver chain | $\Gamma_{\text{power meter}} < 0.05$ $\Gamma_{\text{probe antenna connection}} < 0.16$ | 0.05 | N | 1 | 1 | 0.05 | +| 2) Insertion loss of receiver chain | Systematic with Stage 2 (=> cancels) | 0 | R | | 1 | 0 | +| 3) Influence of the probe antenna cable | Systematic with Stage 2 (=> cancels) | 0 | R | | 1 | 0 | +| 4) Absolute antenna gain of the probe antenna | Systematic with Stage 2 (=> cancels) | 0 | R | | 1 | 0 | +| 5) Measurement Receiver: uncertainty of the absolute level | Power Meter | 0.06 | R | | 1 | 0.03 | +| 6) Measurement distance
a) Offset of DUT phase center | $\Delta d = 0.05\text{m}$ | 0.14 | R | | 1 | 0.08 | +| 7) Quality of quiet zone | Standard deviation of E-field in QZ measurement | 0.5 | N | 1 | 1 | 0.5 | +| 8) DUT Tx-power drift | Drift | 0.2 | R | | 1 | 0.12 | +| 9) Uncertainty related to the use of laptop ground plane phantom: | Standard laptop phantom | 0 | R | | 1 | 0 | +| 10) Coarse sampling grid | Negligible, used = $15^\circ$ and $= 15^\circ$ . | 0 | N | 1 | 1 | 0 | +| 11) Repeatability | horizontal USB design, rotary USB port, and non-rotary USB port used for testing | 0.4 | R | | 1 | 0.23 | +| STAGE 2 (Calibration) | | | | | | | +| 13) Uncertainty of network analyzer | Manufacturer's uncertainty calculator, covers whole NA setup | 0.5 | R | | 1 | 0.29 | +| 14) Mismatch of receiver chain | Taken in to account in NA setup uncertainty | 0 | U | | 1 | 0 | +| 15) Insertion loss of receiver chain | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 16) Mismatch in the connection of calibration antenna | Taken in to account in NA setup uncertainty | 0 | U | | 1 | 0 | +| 17) Influence of the feed cable of the calibration antenna | Gain calibration with a dipole | 0.3 | R | | 1 | 0.17 | +| 18) Influence of the probe antenna cable | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 19) Uncertainty of the absolute gain of the probe antenna | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 20) Uncertainty of the absolute gain of the calibration antenna | Calibration certificate | 0.5 | R | | 1 | 0.29 | +| 21) Measurement distance: Calibration antenna's displacement and misalignment | $d = 3\text{m}$ , $\Delta d = 0.05\text{m}$ , $\theta = 2^\circ$ | 0.29 | R | | 1 | 0.17 | +| 22) Quality of quiet zone | Standard deviation of e-field in QZ measurement, Gain calibration | 0.5 | N | 1 | 1 | 0.5 | +| Combined standard uncertainty | | | | | | 0.89 | +| Expanded uncertainty (Confidence interval of 95 %) | | | | | | 1.75 | + +**Table A.6. Example of uncertainty budget for TRS head only measurement.** + +| Uncertainty Source | Comment | Uncertainty Value [dB] | Prob Distr | Div | ci | Standard Uncertainty [dB] | +|-------------------------------------------------------------------------------|--------------------------------------------------------------------------|------------------------|------------|-----|----|---------------------------| +| STAGE 1 (DUT measurement) | | | | | | | +| 1) Mismatch of transmitter chain | $\Gamma_{\text{BSS}} < 0.13$ $\Gamma_{\text{antenna connection}} < 0.03$ | 0.02 | N | 1 | 1 | 0.02 | +| 2) Insertion loss of transmitter chain | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 3) Influence of the probe antenna cable | Systematic with Stage 2 (=> cancels) | 0 | R | | 1 | 0 | +| 4) Absolute antenna gain of the probe antenna | Systematic with Stage 2 (=> cancels) | 0 | R | | 1 | 0 | +| 5) Base station simulator: uncertainty of the absolute level | | 1 | R | | 1 | 0.58 | +| 6) BER measurement: output level step resolution | Step 0.1dB | 0.05 | R | | 1 | 0.03 | +| 7) Statistical uncertainty of the BER measurement | BER target $10\% \pm 2\%$ , 20000 tested bits , N=60 | 0.12 | N | 1 | 1 | 0.12 | +| 8) TRS data rate normalization | 4 reference points measured | 0.12 | N | 1 | 1 | 0.12 | +| 9) Measurement distance
a) Offset of DUT phase center | $\Delta d = 0.05\text{m}$ | 0.14 | R | | 1 | 0.08 | +| 10) Quality of quiet zone | Standard deviation of E-field in QZ measurement | 0.5 | N | 1 | 1 | 0.5 | +| 11) DUT sensitivity drift | Drift measurement | 0.2 | R | | 1 | 0.12 | +| 12) Uncertainty related to the use of SAM phantom: | Standard SAM with standard tissue simulant | 0 | R | | 1 | 0 | +| 13) Coarse sampling grid | $= 30^\circ$ and $= 30^\circ$ . | 0.15 | N | N | 1 | 0.15 | +| 14) Repeatability | Monoblock, clamshell, slide design | 0.5 | R | | 1 | 0.29 | +| STAGE 2 (Calibration) | | | | | | | +| 16) Uncertainty of network analyzer | Manufacturer's uncertainty calculator, covers NA setup | 0.5 | R | | 1 | 0.29 | +| 17) Mismatch of transmitter chain | Taken in to account in NA setup uncertainty | 0 | U | | 1 | 0 | +| 18) Insertion loss of transmitter chain | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 19) Mismatch in the connection of calibration antenna | Taken in to account in NA setup uncertainty | 0 | R | | 1 | 0 | +| 20) Influence of the feed cable of the calibration antenna | Gain calibration with dipole | 0.3 | R | | 1 | 0.17 | +| 21) Influence of the probe antenna cable | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 22) Uncertainty of the absolute gain of the probe antenna | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 23) Uncertainty of the absolute gain of the calibration antenna | Calibration certificate | 0.5 | R | | 1 | 0.29 | +| 24) Measurement distance: Calibration antenna's displacement and misalignment | $d = 3\text{m}$ , $\Delta d = 0.05\text{m}$ , $\theta = 2^\circ$ | 0.29 | R | | 1 | 0.17 | +| 25) Quality of quiet zone | Standard deviation of E-field in QZ measurement | 0.5 | N | 1 | 1 | 0.5 | +| Combined standard uncertainty | | | | | | 1.1 | +| Expanded uncertainty (Confidence interval of 95 %) | | | | | | 2.16 | + +**Table A.6A. Example of uncertainty budget for TRS head+hand (speech mode) measurement.** + +| Uncertainty Source | Comment | Uncertainty Value [dB] | Prob Distr | Div | ci | Standard Uncertainty [dB] | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|------------------------|------------|-----|----|---------------------------| +| STAGE 1 (DUT measurement) | | | | | | | +| 1) Mismatch of transmitter chain | $\Gamma_{\text{BSS}} < 0.13$ $\Gamma_{\text{antenna connection}} < 0.03$ | 0.02 | N | 1 | 1 | 0.02 | +| 2) Insertion loss of transmitter chain | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 3) Influence of the probe antenna cable | Systematic with Stage 2 (=> cancels) | 0 | R | | 1 | 0 | +| 4) Absolute antenna gain of the probe antenna | Systematic with Stage 2 (=> cancels) | 0 | R | | 1 | 0 | +| 5) Base station simulator: uncertainty of the absolute level | | 1 | R | | 1 | 0.58 | +| 6) BER measurement: output level step resolution | Step 0.1dB | 0.05 | R | | 1 | 0.03 | +| 7) Statistical uncertainty of the BER measurement | BER target $10\% \pm 2\%$ , 20000 tested bits , N=60 | 0.12 | N | 1 | 1 | 0.12 | +| 8) TRS data rate normalization | 4 reference points measured | 0.12 | N | 1 | 1 | 0.12 | +| 9) Measurement distance | | | | | | | +| a) Offset of DUT phase center | $\Delta d = 0.05\text{m}$ | 0.14 | R | | 1 | 0.08 | +| 10) Quality of quiet zone | Standard deviation of E-field in QZ measurement | 0.5 | N | 1 | 1 | 0.5 | +| 11) DUT sensitivity drift | Drift measurement | 0.2 | R | | 1 | 0.12 | +| 9) Uncertainty related to the use of the SAM head and hand phantoms:
a) uncertainty from using different types of SAM phantom
b) simulated tissue liquid uncertainty
c) uncertainty of dielectric properties and shape of the hand phantom: | Standard SAM head with standard tissue simulant
$U_{\epsilon}[\text{dB}] = 0.12$
$U_{\sigma}[\text{dB}] = 0.15$ | 0.32 | R | | 1 | 0.19 | +| 13) Coarse sampling grid | $= 30^\circ$ and $= 30^\circ$ . | 0.15 | N | N | 1 | 0.15 | +| 14) Repeatability of speech mode | Monoblock, clamshell and PDA used for testing | 1.4 | R | | 1 | 0.81 | +| STAGE 2 (Calibration) | | | | | | | +| 15) Uncertainty of network analyzer | Manufacturer's uncertainty calculator, covers NA setup | 0.5 | R | | 1 | 0.29 | +| 16) Mismatch of transmitter chain | Taken in to account in NA setup uncertainty | 0 | U | | 1 | 0 | +| 17) Insertion loss of transmitter chain | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 18) Mismatch in the connection of calibration antenna | Taken in to account in NA setup uncertainty | 0 | R | | 1 | 0 | +| 19) Influence of the feed cable of the calibration antenna | Gain calibration with dipole | 0.3 | R | | 1 | 0.17 | +| 20) Influence of the probe antenna cable | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 21) Uncertainty of the absolute gain of the probe antenna | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 22) Uncertainty of the absolute gain of the calibration antenna | Calibration certificate | 0.5 | R | | 1 | 0.29 | +| 23) Measurement distance: Calibration antenna's displacement and misalignment | $d = 3\text{m}$ , $\Delta d = 0.05\text{m}$ , $\theta = 2^\circ$ | 0.29 | R | | 1 | 0.17 | +| 24) Quality of quiet zone | Standard deviation of E-field in QZ measurement | 0.5 | N | 1 | 1 | 0.5 | +| Combined standard uncertainty | | | | | | 1.35 | +| Expanded uncertainty (Confidence interval of 95 %) | | | | | | 2.64 | + +Table A.6B. Example of uncertainty budget for TRS hand only (browsing mode) measurement. + +| Uncertainty Source | Comment | Uncertainty Value [dB] | Prob Distr | Div | ci | Standard Uncertainty [dB] | +|------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|------------------------|------------|-----|----|---------------------------| +| STAGE 1 (DUT measurement) | | | | | | | +| 1) Mismatch of transmitter chain | $\Gamma_{\text{BSS}} < 0.13$ $\Gamma_{\text{antenna connection}} < 0.03$ | 0.02 | N | 1 | 1 | 0.02 | +| 2) Insertion loss of transmitter chain | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 3) Influence of the probe antenna cable | Systematic with Stage 2 (=> cancels) | 0 | R | | 1 | 0 | +| 4) Absolute antenna gain of the probe antenna | Systematic with Stage 2 (=> cancels) | 0 | R | | 1 | 0 | +| 5) Base station simulator: uncertainty of the absolute level | | 1 | R | | 1 | 0.58 | +| 6) BER measurement: output level step resolution | Step 0.1dB | 0.05 | R | | 1 | 0.03 | +| 7) Statistical uncertainty of the BER measurement | BER target 10% $\pm$ 2% , 20000 tested bits , N=60 | 0.12 | N | 1 | 1 | 0.12 | +| 8) TRS data rate normalization | 4 reference points measured | 0.12 | N | 1 | 1 | 0.12 | +| 9) Measurement distance | | | | | | | +| a) Offset of DUT phase center | $\Delta d = 0.05\text{m}$ | 0.14 | R | | 1 | 0.08 | +| 10) Quality of quiet zone | Standard deviation of E-field in QZ measurement | 0.5 | N | 1 | 1 | 0.5 | +| 11) DUT sensitivity drift | Drift measurement | 0.2 | R | | 1 | 0.12 | +| 9) Uncertainty related to the use of hand phantom: Uncertainty of dielectric properties and shape of the hand phantom. | $U_{\epsilon}[\text{dB}] = 0.12$
$U_{\sigma}[\text{dB}] = 0.15$ | 0.32 | R | | 1 | 0.19 | +| 13) Coarse sampling grid | $= 30^{\circ}$ and $= 30^{\circ}$ . | 0.15 | N | N | 1 | 0.15 | +| 14) Repeatability of browsing mode | Monoblock, clamshell and PDA used for testing | 0.91 | R | | 1 | 0.28 | +| STAGE 2 (Calibration) | | | | | | | +| 15) Uncertainty of network analyzer | Manufacturer's uncertainty calculator, covers NA setup | 0.5 | R | | 1 | 0.29 | +| 16) Mismatch of transmitter chain | Taken in to account in NA setup uncertainty | 0 | U | | 1 | 0 | +| 17) Insertion loss of transmitter chain | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 18) Mismatch in the connection of calibration antenna | Taken in to account in NA setup uncertainty | 0 | R | | 1 | 0 | +| 19) Influence of the feed cable of the calibration antenna | Gain calibration with dipole | 0.3 | R | | 1 | 0.17 | +| 20) Influence of the probe antenna cable | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 21) Uncertainty of the absolute gain of the probe antenna | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 22) Uncertainty of the absolute gain of the calibration antenna | Calibration certificate | 0.5 | R | | 1 | 0.29 | +| 23) Measurement distance: Calibration antenna's displacement and misalignment | $d = 3\text{m}$ , $\Delta d = 0.05\text{m}$ , $\theta = 2^{\circ}$ | 0.29 | R | | 1 | 0.17 | +| 24) Quality of quiet zone | Standard deviation of E-field in QZ measurement | 0.5 | N | 1 | 1 | 0.5 | +| Combined standard uncertainty | | | | | | 1.2 | +| Expanded uncertainty (Confidence interval of 95 %) | | | | | | 2.35 | + +**Table A.6C. Example of uncertainty budget for TRS measurement with laptop ground plane phantom.** + +| Uncertainty Source | Comment | Uncertainty Value [dB] | Prob Distr | Div | ci | Standard Uncertainty [dB] | +|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------|------------------------|------------|-----|----|---------------------------| +| STAGE 1 (DUT measurement) | | | | | | | +| 1) Mismatch of transmitter chain | $\Gamma_{\text{BSS}} < 0.13$ $\Gamma_{\text{antenna connection}} < 0.03$ | 0.02 | N | 1 | 1 | 0.02 | +| 2) Insertion loss of transmitter chain | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 3) Influence of the probe antenna cable | Systematic with Stage 2 (=> cancels) | 0 | R | | 1 | 0 | +| 4) Absolute antenna gain of the probe antenna | Systematic with Stage 2 (=> cancels) | 0 | R | | 1 | 0 | +| 5) Base station simulator: uncertainty of the absolute level | | 1 | R | | 1 | 0.58 | +| 6) BER measurement: output level step resolution | Step 0.1dB | 0.05 | R | | 1 | 0.03 | +| 7) Statistical uncertainty of the BER measurement | BER target 10% $\pm$ 2% , 20000 tested bits , N=60 | 0.12 | N | 1 | 1 | 0.12 | +| 8) TRS data rate normalization | 4 reference points measured | 0.12 | N | 1 | 1 | 0.12 | +| 9) Measurement distance
a) Offset of DUT phase center | $\Delta d = 0.05\text{m}$ | 0.14 | R | | 1 | 0.08 | +| 10) Quality of quiet zone | Standard deviation of E-field in QZ measurement | 0.5 | N | 1 | 1 | 0.5 | +| 11) DUT sensitivity drift | Drift measurement | 0.2 | R | | 1 | 0.12 | +| 9) Uncertainty related to the use of laptop ground plane phantom | Standard laptop phantom | 0 | R | | 1 | 0 | +| 13) Coarse sampling grid | $= 30^\circ$ and $= 30^\circ$ . | 0.15 | N | N | 1 | 0.15 | +| 14) Repeatability | horizontal USB design, rotary USB port, and non-rotary USB port used for testing | 0.5 | R | | 1 | 0.29 | +| STAGE 2 (Calibration) | | | | | | | +| 15) Uncertainty of network analyzer | Manufacturer's uncertainty calculator, covers NA setup | 0.5 | R | | 1 | 0.29 | +| 16) Mismatch of transmitter chain | Taken in to account in NA setup uncertainty | 0 | U | | 1 | 0 | +| 17) Insertion loss of transmitter chain | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 18) Mismatch in the connection of calibration antenna | Taken in to account in NA setup uncertainty | 0 | R | | 1 | 0 | +| 19) Influence of the feed cable of the calibration antenna | Gain calibration with dipole | 0.3 | R | | 1 | 0.17 | +| 20) Influence of the probe antenna cable | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 21) Uncertainty of the absolute gain of the probe antenna | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 22) Uncertainty of the absolute gain of the calibration antenna | Calibration certificate | 0.5 | R | | 1 | 0.29 | +| 23) Measurement distance: Calibration antenna's displacement and misalignment | $d = 3\text{m}$ , $\Delta d = 0.05\text{m}$ , $\theta = 2^\circ$ | 0.29 | R | | 1 | 0.17 | +| 24) Quality of quiet zone | Standard deviation of E-field in QZ measurement | 0.5 | N | 1 | 1 | 0.5 | +| Combined standard uncertainty | | | | | | 1.1 | +| Expanded uncertainty (Confidence interval of 95 %) | | | | | | 2.16 | + +**Table A.7: Example of uncertainty budget for TRP measurement, alternative test method** + +| Uncertainty Source | Comment | Uncertainty Value [dB] | Prob Distr | Div | ci | Standard Uncertainty [dB] | +|-----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|------------------------|------------|-----|----|---------------------------| +| STAGE 1 (DUT measurement) | | | | | | | +| 1) Mismatch of receiver chain | $\Gamma_{\text{power meter}} < 0.05$
$\Gamma_{\text{fixed measurement antenna connection}} < 0.16$ | 0.05 | U | | 1 | 0.04 | +| 2) Insertion loss of receiver chain | Systematic with Stage 2 (=> cancels) | 0 | R | | 1 | 0 | +| 3) Influence of the fixed measurement antenna cable | Systematic with Stage 2 (=> cancels) | 0 | R | | 1 | 0 | +| 4) Absolute antenna gain of the fixed measurement antenna | Systematic with Stage 2 (=> cancels) | 0 | R | | 1 | 0 | +| 5) Measurement Receiver: uncertainty of the absolute level | Power Meter | 0.06 | R | | 1 | 0.03 | +| 6) Chamber statistical ripple and repeatability | Statistics of chamber | 0.4 | N | 1 | 1 | 0.4 | +| 7) Additional power loss in EUT chassis | The EUT not present in the chamber during calibration measurement | 0.1 | R | | 1 | 0.06 | +| 8) DUT Tx-power drift | Drift | 0.2 | R | | 1 | 0.12 | +| 9) a) Uncertainty related to the use of SAM phantom: | Standard SAM head with standard tissue simulant | 0 | R | | 1 | 0 | +| b) Simulated tissue liquid uncertainty | Maximum allowed error | 0.5 | R | | 1 | 0.29 | +| c) Effect of DUT holder | Fixed value | 0.2 | R | | 1 | 0.12 | +| 10) Repeatability | Using the same setup and stirring sequence | 0.4 | R | | 1 | 0.23 | +| 11) Uncertainty related to the use of Laptop Ground Plane phantom | Standard Laptop Ground Plane phantom | [0] | R | | 1 | [0] | +| STAGE 2 (Calibration) | | | | | | | +| 12) Uncertainty of network analyzer | Manufacturer's uncertainty calculator, covers whole NA setup | 0.5 | R | | 1 | 0.29 | +| 13) Mismatch of receiver chain | Taken in to account in NA setup uncertainty | 0 | U | | 1 | 0 | +| 14) Insertion loss of receiver chain | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 15) Mismatch in the connection of calibration antenna | Taken in to account in NA setup uncertainty | 0 | U | | 1 | 0 | +| 16) Influence of the feed cable of the calibration antenna | Gain calibration with a dipole | 0.3 | R | | 1 | 0.17 | +| 17) Influence of the fixed measurement antenna cable | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 18) Uncertainty of the absolute gain of the fixed measurement antenna | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 19) Uncertainty of the absolute gain of the calibration antenna | Calibration certificate | 0.5 | R | | 1 | 0.29 | +| 20) Chamber statistical ripple and repeatability | Statistics of chamber | 0.5 | N | 1 | 1 | 0.5 | +| Combined standard uncertainty | | | | | | 0.88 | +| Expanded uncertainty | | | | | | 1.73 | + +**Error:** + +**74** + +**Error: Reference source not** + +| | | | | | | | +|-------------------------------|--|--|--|--|--|--| +| (Confidence interval of 95 %) | | | | | | | +|-------------------------------|--|--|--|--|--|--| + +**Table A.8. Example of uncertainty budget for TRS measurement, alternative test method** + +| Uncertainty Source | Comment | Uncertainty Value [dB] | Prob Distr | Div | c i | Standard Uncertainty y [dB] | +|-----------------------------------------------------------------------|-----------------------------------------------------------------------------|------------------------|------------|-----|----------------|-----------------------------| +| STAGE 1 (DUT measurement) | | | | | | | +| 1) Mismatch of transmitter chain | $\Gamma_{\text{BSS}} < 0.13$
$\Gamma_{\text{antenna connection}} < 0.03$ | 0.02 | N | 1 | 1 | 0.02 | +| 2) Insertion loss of transmitter chain | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 3) Influence of the fixed measurement antenna cable | Systematic with Stage 2 (=> cancels) | 0 | R | | 1 | 0 | +| 4) Absolute antenna gain of the fixed measurement antenna | Systematic with Stage 2 (=> cancels) | 0 | R | | 1 | 0 | +| 5) Base station simulator: uncertainty of the absolute level | | 1 | R | | 1 | 0.58 | +| 6) BER measurement: output level step resolution | Step 0.1dB | 0.05 | R | | 1 | 0.03 | +| 7) Statistical uncertainty of the BER measurement | BER target 10% $\pm$ 2% , 20000 tested bits , N=60 | 0.12 | N | 1 | 1 | 0.12 | +| 8) TRS data rate normalization | 4 reference points measured | 0.12 | N | 1 | 1 | 0.12 | +| 9) Chamber statistical ripple and repeatability | Statistics of chamber | 0.4 | N | 1 | 1 | 0.4 | +| 10) Additional power loss in EUT chassis | The EUT not present in the chamber during calibration measurement | 0.1 | R | | 1 | 0.06 | +| 11) DUT sensitivity drift | Drift measurement | 0.2 | R | | 1 | 0.12 | +| 12)a) Uncertainty related to the use of SAM phantom: | Standard SAM with standard tissue simulant | 0 | R | | 1 | 0 | +| b) Simulated tissue liquid uncertainty | Maximum allowed error | 0.5 | R | | 1 | 0.29 | +| c) Effect of DUT holder | Fixed value | 0.2 | R | | 1 | 0.12 | +| 13) Repeatability | Using the same setup and stirring sequence | 0.4 | R | | 1 | 0.23 | +| 14) Uncertainty related to the use of Laptop Ground Plane phantom | Standard Laptop Ground Plane phantom | [0] | R | | 1 | [0] | +| STAGE 2 (Calibration) | | | | | | | +| 15) Uncertainty of network analyzer | Manufacturer's uncertainty calculator, covers NA setup | 0.5 | R | | 1 | 0.29 | +| 16) Mismatch of transmitter chain | Taken in to account in NA setup uncertainty | 0 | U | | 1 | 0 | +| 17) Insertion loss of transmitter chain | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 18) Mismatch in the connection of calibration antenna | Taken in to account in NA setup uncertainty | 0 | R | | 1 | 0 | +| 19) Influence of the feed cable of the calibration antenna | Gain calibration with dipole | 0.3 | R | | 1 | 0.17 | +| 20) Influence of the fixed measurement antenna cable | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 21) Uncertainty of the absolute gain of the fixed measurement antenna | Systematic with Stage 1 (=> cancels) | 0 | R | | 1 | 0 | +| 22) Uncertainty of the absolute gain of the calibration antenna | Calibration certificate | 0.5 | R | | 1 | 0.29 | + +| | | | | | | | +|----------------------------------------------------|-----------------------|-----|---|---|---|------| +| 23) Chamber statistical ripple and repeatability | Statistics of chamber | 0.5 | N | 1 | 1 | 0.5 | +| Combined standard uncertainty | | | | | | 1.07 | +| Expanded uncertainty (Confidence interval of 95 %) | | | | | | 2.09 | + +## --- A.29 Void + +### A.29.1 Void + +# Annex B (informative): Suggested recipes of liquid to be used inside SAM phantom + +In Tables B.1 – B.4 are proposed four different recipes of the liquid to be used inside the SAM phantom. + +**Table B.1. Liquid recipe according to [71].** + +| Component | Volume % | +|-----------------|----------| +| Deionized Water | 57.12 | +| Tween 20 | 42.30 | +| NaCl | 0.58 | + +**Table B.2. Liquid recipe according to [59].** + +| Component | Volume % | +|------------------------|----------| +| Water | 45.3 % | +| Sucrose (Sugar) | 54.3 % | +| Hydroxyethylcellulosol | 0.3 % | +| Bactericide | 0.1 % | + +**Table B.3. Liquid recipe according to [22].** + +| Component | Mass % | +|----------------------------------------------------|---------| +| De-ionized Water | 54.9 % | +| Diethylene Glycol Butyl Ether (DGBE) (> 99 % pure) | 44.92 % | +| NaCl | 0.18 % | + +**Table B.4. Liquid recipe according to [23].** + +| Component | Mass % | +|----------------------------------------------------|---------| +| De-ionized Water | 55.36 % | +| Diethylene Glycol Butyl Ether (DGBE) (> 99 % pure) | 13.84 % | +| NaCl | 0.35 % | + +(\*) Polyethylene glycol mono [4-(1,1,3,3-tetramethylbutyl) phenyl ether]. This is available as Triton X-100. The quality of the Triton X- 100 must be ultra pure to match the composition of salt. + +# --- Annex C (informative): System Parameters + +## C.1 Definition and applicability + +This test is aimed at measuring the output power radiated by a 3G UE/MS under the "speech mode" conditions, that is, the usual position for voice application when the handset is held close to the user head, without any hands-free kit. + +Radio measurements are performed in the so-called open area mode in such a way as to be as close as possible to the free space conditions. + +## --- C.2 Establishing the connection + +In order to be as close as possible to the real conditions of use, it is necessary to establish the connection between the UE/MS under test and the Node-B simulator. It makes thus possible to set up the communication parameters to simulate a conversational link. + +### C.2.1 Required parameters to initiate the communication - basic concepts + +#### C.2.1.1 Conversational RAB + +In UMTS, services provided by the Radio Access Network (RAN) to the Core Network (CN) are called Radio Access Bearers (RAB). One RAB consists of one Radio Bearer (RB) plus one Iu Bearer. + +RAB are classified into 4 different QoS classes: Conversational, Streaming, Interactive or Background. For speech services, **conversational class** shall be used. + +#### C.2.1.2 Logical, transport, and physical channels in UMTS + +The Radio Bearer service is provided through a layered architecture of channels (logical, transport and physical channels). + +For speech services, the logical channel shall be a DTCH (Dedicated Traffic Channel), on a DCH (Dedicated Channel) as transport channel, on a DPCH (Dedicated Physical Channel) that consists of two physical channels named DPDCH (Dedicated Physical Data Channel) and DPCCH (Dedicated Physical Control Channel). + +#### C.2.1.3 Dedicated physical channel + +In the Uplink (UL), the DPDCH is transmitted on the I-path whereas the DPCCH is transmitted over the Q-path (QPSK modulation). + +In the Downlink (DL), DPDCH and DPCCH are time multiplexed. + +### C.2.2 Recall on the reference measurement channel (reference to the standard paragraph) + +To perform test measurements, a 12.2kbps Reference Measurement Channel is defined in the specification document [60], both for uplink and downlink. + +This specific channel can be considered as a typical conversational one. Its organisation and features match the requirements previously described to establish a conversational link and are listed in the following tables: + +### C.2.3 Uplink 12.kbps reference measurement channel ([60], annex C, § C.2.1) + +**Table C.1 Dedicated Physical Channel parameters (DPCH = DPDCH + DPCCH)** + +| Parameter | Level | Unit | +|---------------------------|-------|------| +| Information bit rate | 12.2 | kbps | +| DPDCH | 60 | kbps | +| DPCCH | 15 | kbps | +| DPCCH Slot Format #i | 0 | - | +| DPCCH / DPDCH power ratio | -5.46 | dB | +| TFCI | On | - | +| Repetition | 23 | % | + +**Table C.2 Dedicated Transport Channel parameters (DTCH/DCH and DCCH/DCH)** + +| Parameter | DTCH | DCCH | +|----------------------------|--------------------|--------------------| +| Transport Channel Number | 1 | 2 | +| Transport Block Size | 244 | 100 | +| Transport Block Set Size | 244 | 100 | +| Transmission Time Interval | 20 ms | 40 ms | +| Type of Error Protection | Convolution coding | Convolution coding | +| Coding Rate | 1/3 | 1/3 | +| Rate Matching attribute | 256 | 256 | +| Size of CRC | 16 | 12 | + +### C.2.4 Downlink 12.2 kbps reference measurement channel ([60], annex C, § C.3.1) + +**Table C.3 Dedicated Physical Channel parameters (DPCH = DPDCH + DPCCH)** + +| Parameter | Level | Unit | +|--------------------------------|-------|------| +| Information bit rate | 12.2 | kbps | +| DPCH | 30 | ksps | +| Slot Format #i | 11 | - | +| TFCI | On | - | +| Power offsets PO1, PO2 and PO3 | 0 | dB | +| DTX position | Fixed | - | + +**Table C.4 Dedicated Transport Channel (DTCH/DCH and DCCH/DCH)** + +| Parameter | DTCH | DCCH | +|---------------------------------|--------------------|--------------------| +| Transport Channel Number | 1 | 2 | +| Transport Block Size | 244 | 100 | +| Transport Block Set Size | 244 | 100 | +| Transmission Time Interval | 20 ms | 40 ms | +| Type of Error Protection | Convolution coding | Convolution coding | +| Coding Rate | 1/3 | 1/3 | +| Rate Matching attribute | 256 | 256 | +| Size of CRC | 16 | 12 | +| Position of TrCH in radio frame | fixed | fixed | + +# --- Annex D (informative): Radiated power and sensitivity measurement techniques in 2G systems + +## D.1 Introduction + +### D.1.1 Scope + +This appendix presents technical details and examples on how to carry out the TRP (uplink) and TRS (downlink) measurements of the 2G terminals with a radio communication tester. + +### D.1.2 References + +See References of the core of the pre-standard. + +ETSI EN 300 910 V8.5.0 (2000-07) [61] + +ETSI EN 300 607-1 V8.1.0 (2000-05) [62] + +### D.1.3 Definitions, symbols and abbreviations + +#### D.1.3.1 Definitions + +See Definitions of the core of the document. + +#### D.1.3.2 Symbols + +See Symbols of the core of the document. + +#### D.1.3.3 Abbreviations + +See Abbreviations of the core of the pre-standard. + +| | | +|-------|------------------------------------------| +| TCH | Traffic Channel | +| BCCH | Broad Cast Channel | +| TS | Time slot | +| TxLev | Tx Level | +| RxLev | Rx Level | +| BER | Bit Error Rate | +| Sensi | Sensitivity Measured at Maximum Position | + +## --- D.2 Initial conditions + +### D.2.1 Phantom specifications + +See 5.1 of the core of the pre-standard. + +### D.2.2 Anechoic chamber constraints + +See 5.2 of the core of the pre-standard. + +### D.2.3 General arrangement + +See 7.1 of the core of the pre-standard. + +#### D.2.3.1 Free space + +![Diagram of an anechoic room setup for free space measurement. A BS Simulator is connected to a Horn antenna on the left. On the right, a device under test is mounted on a rotating stand with rotation angles phi and theta. The room is lined with blue pyramidal wave absorbers.](e5ded42f8e352da02ee86cb55550c45d_img.jpg) + +Anechoic room + +BS Simulator + +Horn antenna + +$\varphi$ + +$\theta$ + +Diagram of an anechoic room setup for free space measurement. A BS Simulator is connected to a Horn antenna on the left. On the right, a device under test is mounted on a rotating stand with rotation angles phi and theta. The room is lined with blue pyramidal wave absorbers. + +Figure D.1 + +#### D.2.3.2 With SAM head phantom + +![Diagram of an anechoic room setup for measurement with a SAM head phantom. A BS simulator is connected to a Horn antenna on the left. On the right, a SAM head phantom is mounted on a rotating stand with rotation angles phi and theta. The room is lined with blue pyramidal wave absorbers.](78de09c382ab51b5c3e87979204228c8_img.jpg) + +Anechoic room + +BS simulator + +Horn antenna + +$\varphi$ + +$\theta$ + +Diagram of an anechoic room setup for measurement with a SAM head phantom. A BS simulator is connected to a Horn antenna on the left. On the right, a SAM head phantom is mounted on a rotating stand with rotation angles phi and theta. The room is lined with blue pyramidal wave absorbers. + +Figure D.2 + +#### D.2.3.3 Test-bed setup + +![Diagram of the test-bed setup for antenna measurements. A BS simulator is connected to an RF Relay, which is connected to a Dual polarized Horn antenna inside an Anechoic room. The Mobile under test is positioned in front of the antenna. A PC with a GPIB controller is connected to the RF Relay and the Mobile under test. The Mobile under test is mounted on a turntable with rotation angles theta and phi indicated.](0a3ab80d35c138cc4038b5758f6ff34d_img.jpg) + +The diagram illustrates the test-bed setup. On the left, a 'BS simulator' is connected to an 'RF Relay'. The 'RF Relay' has two output paths labeled 'V' (vertical) and 'H' (horizontal) leading into an 'Anechoic room'. Inside the room, the signals are received by a 'Dual polarized Horn antenna'. To the right of the antenna, a 'Mobile under test' is mounted on a turntable. The turntable allows for rotation, with angles $\theta$ (elevation) and $\phi$ (azimuth) indicated. A 'PC' with a 'GPIB controller' is connected to the 'RF Relay' and the 'Mobile under test' via green lines representing control and data connections. + +Diagram of the test-bed setup for antenna measurements. A BS simulator is connected to an RF Relay, which is connected to a Dual polarized Horn antenna inside an Anechoic room. The Mobile under test is positioned in front of the antenna. A PC with a GPIB controller is connected to the RF Relay and the Mobile under test. The Mobile under test is mounted on a turntable with rotation angles theta and phi indicated. + +Figure D.3 + +## --- D.3 Measurement parameters + +### D.3.1 Definition of the TRP parameter + +See 6.1 of the core of the pre-standard. + +### D.3.2 Definition of the MEG parameter + +See 6.2 of the core of the pre-standard. + +### D.3.3 Definition of the MERP parameter + +See 6.3 of the core of the pre-standard. + +### D.3.4 Definition of the TRS parameter + +See 6.4 of the core of the pre-standard. + +### D.3.5 Definition of the MERS parameter + +See 6.5 of the core of the pre-standard + +## --- D.4 Sampling grid + +See 6.6 of the core of the pre-standard. + +## --- D.5 Measurement frequencies + +See 6.7 of the core of the pre-standard. + +Table D.1 + +| Channels | AMPS | GSM | DCS | PCS | +|-----------------|------|-----|-----|-----| +| 1 st | 128 | 975 | 512 | 512 | +| Central | 190 | 37 | 698 | 661 | +| Last | 251 | 124 | 885 | 810 | + +Table D.2 + +| Freq. (MHz) | AMPS | GSM | DCS | PCS | +|-------------|----------------|----------------|------------------|------------------| +| Tx | 842.2 to 848.8 | 880.2 to 914.8 | 1710.2 to 1784.8 | 1850.2 to 1909.8 | +| Rx | 869.2 to 893.8 | 925.2 to 959.8 | 1805.2 to 1879.8 | 1930.2 to 1989.8 | + +The bandwidth allocated to each channel is 200 kHz. + +## D.6 Output power measurement + +Measurements are carried out on the TCH and during the chosen TS. The communication synchronization is established thanks to the BCCH. + +### D.6.1 TRP + +For each position, the average power of the TS (TxLev) is measured. + +### D.6.2 TRS + +The sensitivity measurement is a time-consuming process: it is necessary to measure, step by step and for every position, the received RF level associated to a BER equal to 2.4 % following [61] and [62]. + +## D.7 Measurement procedure – transmitter performance + +### D.7.1 Transmitter performance measurement + +#### D.7.1.1 Spherical scanning ranges + +See 7.1 of the core of the pre-standard. + +### D.7.2 Reference position + +The MS is placed on the positioner mounted on a turntable (see Figure 7.1). + +Then, the reference position ( $\theta = \varphi = 0^\circ$ ) has to be determined. As an example, in the great circle case, and for a standalone mobile, the handset is held in a horizontal position as shown in chapter 5.1 of the core of the pre-standard. The vertical axis goes through the base of the antenna. The mobile is rotated around its main axis ( $\varphi$ angle) step by step. For each $\varphi$ step position, the $\theta$ angle is increased step by step. + +For measurements with the SAM head phantom, the principle is exactly the same. The only differences concern the initial positioning of the mobile/SAM system. In fact, the SAM head is held in a horizontal position as shown in chapter 5.1 of the core of the pre-standard. The vertical axis goes through the base of SAM ear, and the MS is held in a normalized position: see Figure 2.1 of the core of the pre-standard. + +### D.7.3 General measurement arrangements + +#### D.7.3.1 TRP + +See 7.2 of the core of the pre-standard. + +The communication is initialized so that the MS emits at maximum power level + +Table D.3 + +| | AMPS | GSM | DCS | PCS | +|-----------------------------------|---------------------|---------------------|---------------------|---------------------| +| Maximum Power Level configuration | 5 (33 dBm +/- 2 dB) | 5 (33 dBm +/- 2 dB) | 0 (30 dBm +/- 2 dB) | 0 (30 dBm +/- 2 dB) | + +An example of a method to obtain the TRP is to measure the 3-D TxLev pattern on the central channel of each bandwidth supported by the MS, and integrate it as explained in 6.1 of the core of the pre-standard. So as to check the transmitter performances of the MS over the whole considered bandwidth, it would be necessary to calculate the TRP on every channel. However such a measurement is highly time-consuming. + +To reduce the duration of the test, referring to the 3-D pattern measured on the central channel, the MS can be put in the $(\theta, \varphi)$ -position giving the maximum power received at the probe antenna in the main polarization. In this position, the transmitted power can be measured on every channel, and a mean value over the bandwidth can be calculated. The difference (in dB) between the power averaged over all the channels and the value obtained on the central channel in the chosen position can be calculated. It gives a weighting coefficient to apply to the TRP value given by the 3-D measurement done on the central channel. + +This final value gives a good single figure of merit of the radiated power performances of the MS over the whole bandwidth. + +#### D.7.3.2 TRS + +An example of a method to obtain the TRS is to measure the 3-D sensitivity pattern on the central channel of each bandwidth supported by the MS, and integrate it as explained in 6.2 of the core of the pre-standard. The sensitivity measurement over all angular positions is a highly time-consuming process. + +To speed up the process, an example of a method to obtain the TRS is to use the RxLev parameter (MS estimation of the received power). The RxLev is a parameter which can be measured in parallel with the TxLev. + +After having measured the TxLev and RxLev patterns, the MS is positioned in the $(\theta_0, \varphi_0)$ -position giving the maximum power received at the probe antenna in the main polarization. The sensitivity measurement in $(\theta_0, \varphi_0)$ gives a correlation between the Sensi and the RxLev. From this correlation, the sensitivity in every angular position and polarization can be deduced. The process to evaluate the 3-D sensitivity pattern is completely described in the following paragraphs. + +##### a) Sensitivity measurement in the $(\theta_0, \varphi_0)$ -position + +The BS simulator should configure the MS in Loop back mode [61] [62]. Then, the minimum received power is associated to a BER equal to 2.4% (+/- 0.1%) is determined. This power is called sensitivity (Sensi) at the chosen position. The sensitivity measurement has to be carried out on a sufficient number of speech frames, so as to obtain a steady and repeatable value. The experience shows that 300 frames is a sufficient number. + +##### b) Deduction of the sensitivity in every position + +Let $\Delta$ be defined such as: + +$$\Delta = |\text{Sensi}(\theta_0, \varphi_0) - \text{RxLev}(\theta_0, \varphi_0)|$$ + +Then the Sensi in all other positions is deduced as follows: + +$$\text{Sensi}(\theta, \varphi) = \text{RxLev}(\theta, \varphi) + \Delta$$ + +To avoid communication fall, the RxLev has to be measured at a quite high TCH level received by the MS (example – 60.5 dBm which corresponds to a RxLev equal to 50). Find hereunder the table of correspondence between the TCH and Rx levels: + +| TCH level | RxLev | +|-----------------|-------| +| -111 à -110 dBm | 0 | +| -110 à -109 dBm | 1 | +| ⋮ | ⋮ | +| -62 à -61 dBm | 49 | +| -61 à -60 dBm | 50 | + +Figure D.4 + +Note that, so as to check the receiver performances of the MS over the whole considered bandwidth, it would be necessary to calculate the TRS on every channel. However such a measurement is highly time-consuming. + +To reduce the duration of such a test, referring to the 3-D pattern measured on the central channel, the MS can be put in the $(\theta_0, \varphi_0)$ -position. In this position, the sensitivity can be measured on every channel, and a mean value over the bandwidth can be calculated. The difference (in dB) between the sensitivity averaged over all the channels, and the value obtained on the central channel in the $(\theta_0, \varphi_0)$ -position can be calculated. It gives a weighting coefficient to apply to the TRS value given by the 3-D measurement done on the central channel. + +This final value gives a good single figure of merit of the radiated sensitivity performances of the MS over the whole bandwidth. + +### D.7.4 Calibration measurement + +See Section 8.3 of the core of the pre-standard. + +## D.8 Measurement uncertainty and corrections in 2G system measurements + +See Annex A. + +# --- Annex E (informative): Alternative measurement technologies: reverberation chamber method + +## E.1 Reverberation chamber constraints + +This section defines basic parameters of reverberation chambers for measurements of the radio performance of a 3G UE/MS. + +The reverberation chambers [63] have for a couple of decades been used for some types of EMC measurements. A reverberation chamber is a metal cavity that is sufficiently large to support many resonant modes, and it is provided with means to stir the modes. The classical radiation efficiency characterizes the antenna performance in a uniform and isotropic multipath environment, and it is shown in [11] that this fastly and accurately can be measured in a small reverberation chamber. + +The reverberation chamber provides a simulated multipath environment with the same Rayleigh field statistics as actual multipath environments [16]. The environment is isotropic with a uniform elevation and azimuth distribution [64] and polarization imbalance, which could prevail in the reverberation chamber, can be removed [13]. This makes it a well-defined and repeatable environment for TRP testing of mobile terminals. + +In addition to the TRP testing of UE, the reverberation chamber can be used to measure the BER [65] and thereby also the TRS. In addition, it has been demonstrated that it can be used to measure the average fading sensitivity (AVF) [66], corresponding to performance in an environment that fades with a certain speed. + +Reverberation chambers can also be used for direct test of diversity antennas in multipath environment [67][68]. The effective, apparent or actual diversity gains can be determined directly from the statistical distribution of the received signal amplitudes [69]. It is also possible to test the complete active UE with its implemented diversity algorithm, as demonstrated for a DECT phone in [70]. + +The measurements in the reverberation chamber are fast and repeatable, provided the chambers utilize efficient stirring methods. The following sections describe how the reverberation chamber can be used for measurements of TRP and TRS. + +### E.1.1 Chamber size + +The reverberation chamber shall have a volume large enough to support the number of modes needed for the stated accuracy at the lowest operating frequency. If the UE/MS is moved around in the chamber during the measurement, the volume of the reverberation chamber can be reduced [11]. Also, frequency stirring can be used to improve the accuracy, however this will reduce the resolution of the results correspondingly [12]. + +### E.1.2 Mode-stirring facilities + +The reverberation chamber shall be equipped with mode-stirring in such a way that enough number of independent power samples can be achieved for the accuracy requirement stated in this standard to be fulfilled. Possible mode-stirring methods include platform stirring [11], polarization stirring [13], and mechanical stirring with fan-type stirrers, irregular shaped rotational stirrers, or plate-type stirrers. Also frequency stirring is possible if the type of measurement allows for a frequency-averaged value, but this is not necessary if the chamber is sufficiently and well stirred. A schematic picture of the measurement setup is provided in Figure E.1. + +![Schematic diagram of a reverberation chamber measurement setup. The diagram shows a rectangular 'Reverberation chamber' containing a 'Mode stirrer/tuner' (a three-bladed propeller-like object) and a 'Test unit' (a small rectangular box). A 'Fixed measurement antenna' is mounted on the right wall of the chamber. A cable connects the antenna to a 'Base station simulator' located outside the chamber. An arrow labeled 'Same path for up- and downlink' points to this cable, indicating that the signal path is identical for both directions.](5cf80bac69830ea773ac17c87e0ae24d_img.jpg) + +Schematic diagram of a reverberation chamber measurement setup. The diagram shows a rectangular 'Reverberation chamber' containing a 'Mode stirrer/tuner' (a three-bladed propeller-like object) and a 'Test unit' (a small rectangular box). A 'Fixed measurement antenna' is mounted on the right wall of the chamber. A cable connects the antenna to a 'Base station simulator' located outside the chamber. An arrow labeled 'Same path for up- and downlink' points to this cable, indicating that the signal path is identical for both directions. + +Figure E.1: Schematic picture of the reverberation chamber measurement setup + +### E.1.3 Loading of chamber with lossy objects + +The reverberation chamber can be loaded with lossy objects in order to control the power delay profile in the chamber to some extent. However the reverberation chamber should not be loaded to such an extent that the mode statistics in the chamber are destroyed. It is important to keep the same amount of lossy objects in the chamber during calibration measurement and test measurement, in order not to change the average power transfer function between these two cases. + +### E.1.4 Polarization imbalance and receiving antennas + +It is important that the statistical distribution of waves in the chamber corresponds to the chosen test environment. Present knowledge about reverberation chambers limits this to isotropic environments, i.e. the TRP and TRS parameters can be measured. Since the probability of each polarization is equal in the isotropic environment, a check of the polarization imbalance in the reverberation chamber must be done. + +The polarization imbalance can be obtained during the calibration measurement by measuring both when the calibration antenna is oriented for vertical polarization and when it is oriented for horizontal polarization. These two values shall differ by less than the specification in Table E.1. In order to obtain values for comparison with the results in the table, the reference levels shall be measured for both orientations of the calibration dipole at 8 different positions of the dipole inside the chamber. The average, standard deviation and maximum deviation shall be evaluated by comparing results for both polarizations over the whole set of 8 measurements. Alternatively, the levels for the two polarizations of the calibration antenna at 1 MHz intervals between 1900 MHz and 2200 MHz can be measured, and thereafter the average, standard deviation and maximum of the difference between the two sets of values over these frequency ranges are calculated. + +An effective way of avoiding polarization imbalance is to use polarization stirring, i.e. using three orthogonal linearly polarized receiving antennas. These three receiving antennas may be monopoles connected orthogonally to three different and orthogonal walls (including ceiling/floor) of the chamber. The three antennas are below referred to as the three fixed wall mounted antennas. + +Table E.1 Specifications of differences of measured reference levels in each frequency band between using vertically and horizontally polarized calibration dipoles. + +| | Maximum tolerable value | +|--------------------|-------------------------| +| Average | 0.2 dB | +| Standard deviation | 0.5 dB | +| Maximum | 1.0 dB | + +### E.1.5 Shielding effectiveness + +The shielding effectiveness of the chamber shall be as large as needed for the interference from other sources not to influence the measured parameters. This means that the requirements of the shielding is specific to each test site and may vary accordingly. + +## E.2 Reverberation chamber method + +This section describes how TRP and TRS can be calculated from reverberation chamber data. + +### E.2.1 Measurement procedure – transmitter performance + +The measurement of transmitter performance in the reverberation chamber is based on sampling the radiated power of the UE/MS for a discrete number of field combinations in the chamber. The average value of these statistically distributed samples is proportional to the Total Radiated Power (TRP), and by calibrating the average power transfer function in the chamber, an absolute value of the TRP can be obtained. + +Setup the DUT by locating the head phantom and the UE/MS in one of the specified positions inside the chamber. It is important that the objects placed inside the chamber during DUT measurements are the same as those present during the calibration measurement. + +Measure and save DUT radiated power levels for all the positions of the platform stirrer and mechanical stirrer and for all the frequency points used. Do this for each of the chamber's fixed measurement antennas. Average the saved DUT power levels over all stirrer positions. Note that all averaging must be performed using linear power values (e.g measurements in Watts). Thus the following equation applies + +$$(E.1)$$ + +where $P_{ref,n}$ is the reference power transfer function for fixed measurement antenna $n$ , $\Gamma_n$ is the reflection coefficient for fixed measurement antenna $n$ and $L_n$ is the path loss in the cables connecting the measurement receiver to fixed measurement antenna $n$ . These parameters are calculated from the calibration measurement and are further discussed in Annex B.2. $P_{avg,n}$ is the average power measured by fixed measurement antenna $n$ and can be calculated using the following expression: + +$$(E.1.a)$$ + +where $P_{m,n}$ is sample number $m$ of the complex transfer function measured with fixed measurement antenna $n$ and $M$ is the total number of samples measured for each fixed measurement antenna. + +### E.2.2 Measurement procedure – receiver performance + +The DUT's TRS can also be calculated from measurements made in a Rayleigh fading three dimensional isotropic environment with uniform elevation and azimuth distribution. The calculation of TRS is based on searching for the lowest power received by the UE/MS for a discrete number of field combinations in the chamber. The power received by the UE at each discrete field combination that provides a BER (or BLER) which is better than the specified target BER/BLER level shall be averaged with other such measurements using different field combinations. By calibrating the average power transfer function, an absolute value of the TRS can be obtained when the linear values of all downlink power levels described above have been averaged. The following expression can be used to find the TRS. + +$$(E.1.b)$$ + +where $P_{ref,n}$ is the reference power transfer function for fixed measurement antenna $n$ , $\Gamma_n$ is the reflection coefficient for fixed measurement antenna $n$ and $L_n$ is the path loss in the cables connecting the measurement receiver to fixed measurement antenna $n$ . These parameters are calculated from the calibration measurement and are further discussed in Annex B.2. $P_{avg,n}$ is calculated by using the following equation: + +$$(E.1.c)$$ + +where $m$ is the $m$ :th value of the transfer function for fixed measurement antenna $n$ , which gives the BER threshold. $N$ is the total number of values of the BER threshold power measured for each fixed measurement antenna. + +## E.3 Calibration of reverberation chamber + +The purpose of calibration measurement is to determine the average power transfer function in the chamber, mismatch of the chamber's fixed measurement antennas and path losses in cables connecting the power sampling instrument and the fixed measurement antennas. A Vector Network Analyzer (VNA) should be used for these measurements. Recommended calibration antennas are dipoles tuned to the frequency band of interest. + +In general, the calibration of a reverberation chamber is performed in three steps: + +- 1) Measurement of S-parameters through the reverberation chamber for a complete stirring sequence +- 2) Calculation of the chamber reference transfer function +- 3) Measurement of connecting cable insertion loss + +If several setups are used (e.g. empty chamber, chamber with head phantom, etc.), steps 1 and 2 must be repeated for each configuration. The calibration measurement setup can be studied in Figure E.2. + +![Diagram of the calibration measurement setup in a reverberation chamber. A rectangular box represents the 'Reverberation chamber'. Inside, a 'Reference antenna' (a dipole) is connected to 'Port 1' of a 'Vector network analyzer' (VNA) via a cable. A 'Fixed measurement antenna' (another dipole) is connected to 'Port 2' of the VNA via a cable. Arrows labeled 'VNA calibration points' point to the connection points of both antennas inside the chamber. The VNA is shown as a box with 'Port 1' and 'Port 2'.](4aeaa51a3999fab21171224e238cb571_img.jpg) + +Diagram of the calibration measurement setup in a reverberation chamber. A rectangular box represents the 'Reverberation chamber'. Inside, a 'Reference antenna' (a dipole) is connected to 'Port 1' of a 'Vector network analyzer' (VNA) via a cable. A 'Fixed measurement antenna' (another dipole) is connected to 'Port 2' of the VNA via a cable. Arrows labeled 'VNA calibration points' point to the connection points of both antennas inside the chamber. The VNA is shown as a box with 'Port 1' and 'Port 2'. + +**Figure E.2** Calibration measurement setup in the reverberation chamber, using a vector network analyzer. + +### E.3.1 Measurement of S-parameters through the chamber for a complete stirring sequence + +- i. This step will measure S-parameters through the reverberation chamber through a complete stirring sequence. This information is required to determine the chamber's reference transfer function. The procedure must be performed separately for each measurement setup in which the loading of the chamber has been changed. The calibration procedure must be repeated for each frequency as defined above. Therefore, it is advantageous if the network analyzer can be set to a frequency sweep covering the defined frequencies, so that all frequencies of interest can be measured with a minimal number of measurement runs. Place all objects into the RC which will be used during TRP or TRS measurements, including a head phantom, hand phantom and fixture for the EUT. This ensures that the loss in the chamber, which determines the average power transfer level, is the same during both calibration and test measurements. Also, if the EUT is large or contains many antennas, it may represent a noticeable loading of the chamber. It should then be present in the chamber and turned on during the calibration. +- ii. Place the calibration antenna inside the chamber. The calibration antenna is preferably mounted on a low-loss dielectric fixture, to avoid effects from the fixture itself which may affect the EUT's radiation efficiency and + +mismatch factor. The calibration antenna must be placed in the chamber in such a way that it is far enough from any walls, mode-stirrers, head phantom, or other object, such that the environment for the calibration antenna (taken over the complete stirring sequence) resembles a free space environment. "Far enough away" depends on the type of calibration antenna used. For low gain nearly omni-directional antennas like dipoles, it is normally sufficient to ensure that this spacing is larger than 0.5 wavelengths from reflective objects and 0.7 wavelengths from absorbing objects at the lowest operating frequency. More directive calibration antennas should be situated towards the center of the chamber. The calibration antenna should remain present in the chamber during the TRP/TRS measurements. + +- iii. Calibrate the network analyzer with a full 2-port calibration in such a way that the vector S-parameters between the ports of the fixed measurement antenna and the calibration antenna can be accurately measured. Preferably, the network analyzer is set to perform a frequency sweep at each stirrer position. This will enable calibration of several frequency points during the same stirring sequence, thereby reducing calibration time. This will also enable frequency stirring, i.e., averaging the measured power transfer function over a small frequency bandwidth around each measured frequency point (moving frequency window). This will increase accuracy at the expense of frequency resolution. +- iv. Connect the antennas and measure the S-parameters for each fixed measurement antenna. + +The number of stirrer positions in the chosen stirring sequence, i.e. the number of S-parameter samples at each frequency point, should be chosen in such a way that it is large enough to yield an acceptable statistical contribution to the total measurement uncertainty. As a guideline, the sample size should be larger than 100, preferably 200 or 400 to ensure that the number of independent samples is not severely limited by the total number of samples measured. The number of independent samples, which is a subset of all samples, determines the statistical contribution to the expanded accuracy (which is two times the standard deviation). This should be larger than 100 to ensure an expanded accuracy better than 1 dB. The number of independent samples depends on the operating frequency, volume of the chamber, efficacy of the chamber's stirrers, the level of loading by absorbing objects, and whether or not frequency stirring is used. + +The sequence of moving the stirrers to different positions may be either step-wise (stopping stirrer for each sample) or continuous (sampling on-the-fly). With continuous stirring it may not be possible to characterize the chamber over a wide frequency band at the same time. + +### E.3.2 Calculation of the chamber reference transfer function + +From the S-parameters obtained in the calibration measurement, the chamber reference transfer function for fixed antenna $n$ can be calculated. The reflection coefficient for fixed antenna $n$ can be calculated as + +$$(E.2)$$ + +Thus, the chamber reference transfer function can be calculated as + +$$(E.3)$$ + +is + +where $M$ is the total number of samples of the transfer function measured for each fixed measurement antenna and sample number $m$ of the transfer function for measurement antenna $n$ . Moreover, $\bar{S}_{11}$ is the complex average of the calibration antenna reflection coefficient. Finally, $\epsilon$ is the radiation efficiency of the calibration antenna. + +Note that the radiation efficiency of the fixed antenna is not corrected for, because it will be the same both during calibration and measurements. Therefore the fixed antenna's radiation efficiency will not affect the final results. The same can be said about the mismatch factor of the fixed measurement antennas, but it is still advantageous to correct for this factor if frequency stirring is applied to improve accuracy. + +### E.3.3 Cable calibration + +This measurement step will calibrate the power loss of the cable needed to connect the instrument used to measure the received power at the fixed measurement antenna during TRP measurements, and to generate the power radiated by the fixed antenna during TRS measurements. + +- i. Disconnect the cables between the VNA and the chamber. + +- ii. Connect the cables one-by-one between the two ports of the VNA. Note that VNA must be calibrated such that the reference plane corresponds to its own two ports. +- iii. Measure the frequency response of the transmission S-parameter ( $S_{21}$ or $S_{12}$ ) of the cable. +- iv. Save the power transfer values ( $|S_{21}|^2$ ) of the frequency response curve for the test frequencies. + +## --- E.4 Estimation of measurement uncertainty + +See Annex A. + +# --- Annex F (informative): Anechoic chamber specifications and validation method + +This Annex presents the specifications for the shielded anechoic chamber and the validation methods. + +## --- F.1 Shielded anechoic chamber specifications + +Before measuring the test site characteristics in the presence of the antenna positioning system, the shielding effectiveness of the enclosure and the quiet zone level must be measured. + +To avoid environmental perturbations the measurements must be performed in a shielded enclosure, preserved from electromagnetic disturbances coming from electromagnetic environment (Radio and TV broadcast, cellular, ISM equipment, etc...). The shielding effectiveness recommended to be tested according to the EN 50 147-1 standard in the frequency range of 800 MHz up to 4 GHz. + +The recommended level of the shielding effectiveness is -100 dB from 800 MHz to 4 GHz. + +Testing of the shielding effectiveness can be performed either before or after the installation of absorbers. + +## --- F.2 Quiet Zone reflectivity level validation + +The performance of anechoic chamber is typically evaluated from reflectivity level in the quiet zone. Reflection level is defined as power ratio of all summed reflected signals to direct signal from antenna: + +$$(1)$$ + +To evaluate the quiet zone reflectivity level, the contribution of absorbing materials, the antenna positioning system and other constructions in the anechoic chamber should be measured. Two most common methods for measuring the reflectivity level of the quiet zone are Free Space VSWR Method and the Time Domain Method. Traditionally these measurements have been accomplished by using high gain horn antennas. Studies have shown that using horn antenna can give about 14 dB lower reflectivity levels compared to use of dipole antenna [72]. However, the methods that utilize highly directive antennas are powerful in identifying the direction of the offending reflections. + +To measure accurately quality of the quiet zone in anechoic chamber one must use an omni-directional antenna. Near omni-directional three axes field-probes are available with fibre optic connection thus minimizing cable effects. Because sensitivity of field probe is limited one must carefully check that the field probe is operated at least 6dB above the noise floor of the probe. + +Note: The quiet zone evaluation should be performed with the antenna positioning system in its place, in order to include its effect on the reflectivity level. + +### F.2.1 Description of a practical method for Quiet Zone characterization + +In the following, a practical version of the Free Space VSWR method is presented [73]. + +In the Free Space VSWR method the quality of quiet zone is measured from amplitude ripple caused by reflections inside the anechoic chamber. Phase variation of the direct signal and the reflected signals is obtained by moving a field-probe in the quiet zone. Amplitude ripple in the quiet zone is caused by this phase variation of reflected signals and the direct signal from antenna. The figure F.1 below shows seven measuring positions. + +![Figure F.1: Measurement positions with 150mm separation. The diagram shows a 2D coordinate system with dashed axes. Seven measurement points are marked with small L-shaped symbols at various positions. A dashed line with an arrow points from the origin towards the upper right. To the right of the diagram is a large arrow pointing right, labeled 'Antenna'.](8ec6b1a5d391a58cfa4f2eebd7c48f54_img.jpg) + +Figure F.1: Measurement positions with 150mm separation. The diagram shows a 2D coordinate system with dashed axes. Seven measurement points are marked with small L-shaped symbols at various positions. A dashed line with an arrow points from the origin towards the upper right. To the right of the diagram is a large arrow pointing right, labeled 'Antenna'. + +**Figure F.1: Measurement positions with 150mm separation** + +In each of the seven-measurement position amplitude of power received by field-probe [dBm] is measured where $i$ is index of measuring position. Variance of measurement distance to the antenna from field-probe in different measurement positions can be compensated by following equation: + +$$\text{where,} \quad (2)$$ + +$d_i$ is distance to point $i$ from the antenna, + +$d_0$ is distance to centre of quiet zone from the antenna + +$P_i$ is uncorrected measurement value from point $i$ . + +The sample standard deviation of the electric field in the quiet zone can be calculated from these distance corrected values or directly from the measured values with the following equation: + +$$\text{where,} \quad (3)$$ + +$N$ is number of measurements positions + +$\bar{P}$ is dB average of all + +$P_i$ is or + +#### Standard deviation of electric field + +To obtain more accurate picture of quality of quiet zone, measurement described in previous chapter can be done from multiple directions and polarizations. Doing free space VSWR measurement from different directions in 15-degree separation for elevation and azimuth we get 264 standard deviation values in both polarizations ( $\theta$ ). From these values average sample standard deviation in electric field in quiet zone can be calculated from equation: + +$$, \quad (4)$$ + +Where + +$N$ is number of angular intervals in elevation, + +$M$ is number of angular intervals in azimuth and + +$\theta_j$ is elevation of measurement $j$ . + +This quiet zone quality measurement should be done at all the frequencies used in measurements. + +# --- Annex G (informative): Reverberation chamber specifications and validation method + +This Annex presents the specifications for the shielded reverberation chamber and the validation methods. + +## --- G.1 Shielded reverberation chamber specifications + +Before measuring the test site characteristics in terms of stirring effectiveness etc., the shielding effectiveness of the metallic enclosure must first be measured. + +To avoid environmental perturbations, the measurements must be performed in a shielded enclosure, preserved from electromagnetic disturbances coming from electromagnetic environment (Radio and TV broadcast, cellular, ISM equipment, etc...). It's recommended to test the chamber's shielding effectiveness according to the EN 50 147-1 standard in the frequency range of 700 MHz up to 4 GHz. + +The recommended level of the shielding effectiveness is -100 dB from 700 MHz to 4 GHz. + +## --- G.2 Reverberation chamber statistical ripple and repeatability validation + +The reverberation chamber is typically evaluated according to its isotropy level and ability to produce independent samples. The uncertainty due to chamber statistics is determined by repeated calibration measurements as described in Annex B.2. This uncertainty contribution is a composite value consisting of most of the specific reverberation chamber contributions, such as limited number of modes, K-factor, polarization imbalance and mode-stirring techniques. + +The uncertainty contribution value shall be determined by repeated calibration measurements for nine different positions and orientations of the calibration antenna in order to determine the statistical variation as a function of frequency, or at least at the frequencies where the chamber shall be used. This uncertainty contribution value can be assumed to have a normal distribution. + +The uncertainty will depend on chamber size, frequency, stirrer sequence, stirrer types and shapes, polarization stirring (if any), and the degree of chamber loading. All these factors must remain the same for all nine calibration measurements. The uncertainty will also depend on frequency stirring bandwidth (if any), but the effects of different amounts of frequency stirring can be studied with the same sets of calibration data as when no frequency stirring is applied. + +The nine net average power transfer functions of all or some of the nine calibration configurations for each loading case shall be averaged to provide a good reference level. Frequency stirring can only be applied to improve the reference level. Therefore, the uncertainty shall be found by computing the average and standard deviation of the net average power transfer function of each of the nine reference (antenna) positions and orientations (without frequency stirring) around the reference level (which can be frequency stirred if it gives better overall accuracy). + +The data obtained during these reference measurements can be used for analysis of the chamber's systematic and deterministic contribution to S21. Such analysis can help determine possible uncertainty sources in chambers where the "chamber statistics" portion of the uncertainty analysis is too high to fulfil the total uncertainty criterion. The normalized standard deviation is calculated using the following expression: + +where + +is the standard deviation of the power transfer function over T different calibration antenna positions. is the reference power transfer function for position $t$ of the calibration antenna. The power transfer function for every calibration antenna position is further the average over the power transfer function for each fixed measurement antenna in the chamber defined in Annex B.2. Thus, + +where $N$ is the total number of fixed measurement antennas. Moreover, + +This is the average power transfer function over the $T$ calibration positions. + +# --- Annex H (informative): Dielectric Property Measurements of Hand Phantoms + +This annex describes the measurement of the dielectric properties of tissue-equivalent material of hand phantom. The phantoms are commonly based on a carbon-filled silicone rubber material. Besides relative permittivity and conductivity, the carbon-loaded polymer matrix materials used for making hand phantoms have other properties which must be carefully controlled, most notably DC resistance and stiffness. In carbon-loaded materials with increasing carbon concentrations, a point is reached, the percolation point, at which the particles are no longer completely isolated and the DC resistance of the entire macroscopic sample drops suddenly. + +Measurements of permittivity and conductivity on materials around this carbon concentration need careful procedures. An additional issue is that in solids with suspended particles, natural surfaces represent a unique plane, and may contain a much-reduced particle loading compared to any other sectional plane through the solid, where particles will intersect the plane. Cutting such material may result in release of a carbon film that may also strongly affect the measurements. + +The open-ended coaxial probe (OCP) technique has demonstrated an acceptable degree of consistency between labs, even around the percolation point. Moreover, the published target dielectric properties [75] for hand materials were derived from open-ended probe measurements on a sample of human hands. The OCP method shall be used for all surface dielectric property measurements. The dielectric parameters to be determined are the complex relative + +permittivity $\varepsilon_r = \varepsilon_r' - j\sigma/\omega\varepsilon_0$ of the material. It is recommended that with each delivered hand, manufacturers will provide two test samples of the material made from the same mix as the hand, one to be kept by the user, and the other by the manufacturer. + +## --- H.1 Open-ended Coaxial Probe (OCP) Method + +Compressibility of the hand materials is a property that must be considered when measurements are made with OCP method. The degree to which the coaxial sensor is pressed into the surface of the test sample has a significant effect on the results obtained. Sensors with a nominal diameter of at least 7 mm are to be preferred over smaller ones in this respect. A cylindrical sample-under-test, such as can be provided by molding inside a 20 ml plastic syringe, alleviates the concern that might exist with a flat block that probe pressure causes the material directly under the probe tip to bow away from contact. To obtain measurement consistency, the sensor can be supported on a framework that allows measurement either at a fixed contact pressure or at a fixed sensor displacement. In both cases, as contact is increased from a light touch, the dielectric results change, but above a certain critical pressure/penetration, stable results are obtained. Measurements shall be made in this condition. A pressure of around 500 kPa is necessary for this condition to be met, or a displacement of 3 mm. 500 kPa is equivalent to a load of 2 kg on a nominal 7 mm diameter probe. Measurement at a fixed sensor displacement offers a considerable advantage over the fixed pressure technique by providing, at the same time, a simple measurement of the elastic modulus of the material-under-test. + +![Figure H.1: OCP setup with fixed sensor displacement. The diagram shows two identical experimental setups side-by-side. Each setup consists of a VNA connected to a probe, which is in contact with a 'Sample Under Test'. The sample is mounted on a 'Load Cell', which is connected to a 'Voltmeter'. The entire assembly is supported by a hatched base. In the right setup, an arrow indicates a '3mm Displacement' of the probe into the sample.](ffe0fef452a0ae9a20253c319c54e13c_img.jpg) + +Figure H.1: OCP setup with fixed sensor displacement. The diagram shows two identical experimental setups side-by-side. Each setup consists of a VNA connected to a probe, which is in contact with a 'Sample Under Test'. The sample is mounted on a 'Load Cell', which is connected to a 'Voltmeter'. The entire assembly is supported by a hatched base. In the right setup, an arrow indicates a '3mm Displacement' of the probe into the sample. + +**Figure H.1 OCP setup with fixed sensor displacement.** + +![Figure H.2: OCP setup with fixed contact pressure. The diagram shows a single experimental setup. A VNA is connected to a probe, which is in contact with a 'Sample Under Test'. The sample is mounted on 'Weighing Scales', which are supported by a 'Scissor Jack'. The entire assembly is supported by a hatched base.](30ca9a81da047d57fa881b632aaca2d8_img.jpg) + +Figure H.2: OCP setup with fixed contact pressure. The diagram shows a single experimental setup. A VNA is connected to a probe, which is in contact with a 'Sample Under Test'. The sample is mounted on 'Weighing Scales', which are supported by a 'Scissor Jack'. The entire assembly is supported by a hatched base. + +**Figure H.2. OCP setup with fixed contact pressure.** + +Measurements are made by placing the probe in contact with the sample and measuring the admittance or reflection coefficient with respect to the open-circuit end, using network analyzer or equivalent instrumentation. To reduce measurement uncertainty, it is recommended that the measurement be repeated at least 10 times at different positions on the test sample, to minimize bias from abnormal readings caused by particulates of the same scale size as the probe dimension. + +Prior to measurements, the network analyzer is configured to measure the magnitude and phase of the admittance. A one-port reflection calibration is performed at the plane of the probe by placing liquids for which the reflection coefficient can be calculated in contact with the probe. Three standards are needed for the calibration, typically a short circuit, air, and de-ionized water at a well-defined temperature (other reference liquids such as methanol or ethanol may be used for calibration). + +Application software should interpret the measured data to yield the dielectric properties of the sample as a function of frequency, together with an estimate of the standard deviation. To use this technique, a probe and a software package for the network analyzer has to be developed or obtained from a commercial source. + +# Annex I (informative): Change history + +| Change history | | | | | | | | +|----------------|-----------|------|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|----------|-----------------------| +| Meeting | TSG doc | CR | Rev | Subject | Old vers | New vers | Work item | +| RP-29 | RP-050544 | - | - | For information | | 1.0.0 | RinImp-UEAnt | +| | | | | Ready for approval | 1.0.0 | 2.0.0 | | +| RP-32 | RP-060301 | | | Approved | 2.0.0 | 7.0.0 | | +| SP-42 | | | | Upgraded unchanged from Rel 7 | | 8.0.0 | | +| SP-46 | | | | Upgraded unchanged from Rel 8 | | 9.0.0 | | +| RP-51 | RP-110353 | 0002 | 1 | CR for TR 25.914: Add LME OTA Testing Scenario | 9.0.0 | 10.0.0 | UEAnt_FSTest | +| RP-51 | RP-110353 | 0003 | - | Adding a new section for embedded devices | 9.0.0 | 10.0.0 | UEAnt_FSTest | +| RP-52 | RP-110815 | 0005 | | CR for TR 25.914: Modification of the miscellaneous for adding LME OTA testing | 10.0.0 | 10.1.0 | UEAnt_FSTest | +| RP-52 | RP-110815 | 0004 | 1 | Description of laptop ground plane phantom

(The CR was not implemented as it was covered by the more recent, more generic CR from the same proponents in 25914_CR0004R1_(Rel-10)_R4-112345) | 10.0.0 | 10.1.0 | UEAnt_FSTest | +| RP-52 | RP-110815 | 0006 | 1 | Adding text applicable for notebook measurements in TP25.914 | 10.0.0 | 10.1.0 | UEAnt_FSTest | +| RP-52 | RP-110815 | 0007 | 2 | Adding the detailed definition of the Laptop ground plane phantom for LME OTA testing | 10.0.0 | 10.1.0 | UEAnt_FSTest | +| RP-54 | RP-111695 | 011 | 1 | Revised agreed CRs R4-114766 and R4-114811 for TR 25.914 for approval with correction | 10.1.0 | 11.0.0 | UEAnt_FSTest | +| RP-56 | RP-120795 | 013 | 1 | LME and LEE clarifications to measurements of radio performance for UMTS terminals in speech mode | 11.0.0 | 11.1.0 | TEI11 | +| RP-56 | RP-120874 | 014 | 2 | Introduction of hand phantom to TR25.914 | 11.0.0 | 11.1.0 | FS_OTA_phantoms_UTRA | +| RP-56 | RP-120795 | 015 | 1 | LME and LEE clarification to measurements of radio performance for terminals on uncertainty contributions in measurements | 11.0.0 | 11.1.0 | TEI11 | +| RP-56 | RP-120874 | 016 | | Mechanical Requirements of Hand Phantoms | 11.0.0 | 11.1.0 | FS_OTA_phantoms_UTRA | +| RP-56 | RP-120874 | 017 | | Dielectric Property Measurements of hand phantoms | 11.0.0 | 11.1.0 | FS_OTA_phantoms_UTRA | +| RP-56 | RP-120874 | 020 | 1 | CR to introduce left hand phantoms to TR25.914 | 11.0.0 | 11.1.0 | FS_OTA_phantoms_UTRA | +| RP-57 | RP-121341 | 021 | 1 | Measurement uncertainty update due to use of hand phantoms | 11.1.0 | 11.2.0 | FS_OTA_phantoms_UTRA | +| RP-58 | RP-121912 | 0023 | 1 | Test method update for devices with multiple receive antennas | 11.2.0 | 11.3.0 | UEAnt_FSTest | +| RP-58 | RP-121912 | 0024 | | Corrections to Random Uncertainty for LME | 11.2.0 | 11.3.0 | UEAnt_FSTest | +| RP-58 | RP-121875 | 0025 | | Data browsing mode measurement uncertainty | 11.2.0 | 11.3.0 | FS_OTA_phantoms_UTRA | +| RP-63 | RP-140383 | 026 | 1 | TP for tablet testing TR 25.914 | 11.3.0 | 12.0.0 | LTE_UTRA_TRP_TRS-Core | +| SP-70 | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | | +| RP-75 | - | - | - | Update to Rel-14 version (MCC) | 13.0.0 | 14.0.0 | | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|------------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2018-06 | SA#80 | - | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| | | | | | | Editorial Change to the cover page | 15.0.1 | +| 2020-06 | SA#88 | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file