hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
e6216feaaaa5965cd6f90f30edec4573 | 101 173 | 8.2.1 ARQ protocols for real-time requirements | An ARQ protocol for real-time services has to retransmit ATM cells as long as a service specific maximum delay is not exceeded. When exceeding its due-date, an ATM cell may be discarded. Discarding old ATM cells contributes to avoid and resolve congestion events, since the delay of the following cells can be shortened and the probability to exceed further due-dates is reduced. Therefore, special procedures have been developed in order to allow discarding ATM cells within an ARQ protocol which has been designed for no losses at all. With a go back N ARQ this is no problem as the receiver does not know exactly which packet is missing. Therefore, it is possible to re-assign a sequence number to a different packet. In conventional selective repeat ARQ protocols discarding of cells or packets is not implemented. After the assignment of a sequence number to an ATM cell, taking the ATM cell out of the sending procedure by discarding it results in a gap in the receive sequence. The receiver will react on this by incessantly requesting a retransmission of the missing cell. Finally a reset of the connection will resolve the deadlock situation. To avoid this, the sender has to inform the receiver after discarding an ATM cell, to which a sequence number has been already assigned to. Three possible solutions have been proposed and investigated: - A packet being assigned a sequence number may be discarded. In this case the window will be shifted without waiting for an ACK, enabling further transmissions of newer ATM cells. When receiving the newer cells, the receiver will synchronize to the window shift automatically. This means that the exact execution of the ARQ protocol is temporarily disabled, enabling fast transmissions without error control, until the congestion event has been resolved see reference [49]. - A packet being assigned a sequence number may be discarded. The receiver is informed about the discarded cell by sending a special discard ACK, which in contrast to normal ACKs is sent in the forward direction. As a consequence, discarding ATM cells is only useful if subsequently an efficient transmission of the discard ACK is possible. - Within the receiver a timer is set which controls the time a packet is requested for retransmission. After that time the window is shifted and the receiver does not wait for the missing packet any longer. TR 101 173 V1.1.1 (1998-05) 41 History Document history V1.1.1 May 1998 Publication ISBN 2-7437-2153-7 Dépôt légal : Mai 1998 |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 1 Scope | The present document gives background information on how the RF requirements of GSM 400, GSM 900 and DCS 1800 systems have been derived. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 2 Information available | The present document collects together temporary documents of ETSI SMG and STC SMG2 which can be seen as base line material for the RF requirements in GSM 05.05. The documents are divided into eleven groups: - DCS 1800 system scenarios; - GSM 900 small cell system scenarios; - GSM 900 microcell system scenarios; - conversion factors to compare different requirements; - repeaters; - speech codec error patterns; - simulation of performance; - GSM 900 railway system scenarios; - GPRS Performance; - pico BTS RF scenarios; - GSM 400 system scenarios. In the following clauses there is a short description of the documents. The documents themselves are annexed to this report. A list of phase 2 change requests to SMG2 related documents are annexed to the SMG meeting reports. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 3 DCS 1800 system scenarios | There are two documents describing the basis of the DCS 1800 RF requirements. They are: - DCS 1800 System scenarios (TDoc SMG 259/90, reproduced as TDoc SMG 60/91). - Justifications for the DCS 1800 05.05 (TDoc SMG 260/90, revised as TDoc SMG 60/91)). These documents have been derived first by the UK PCN operators and later by GSM2 ad hoc group working on DCS 1800 requirements during 1990. The documents were presented to TC SMG in October 1990. DCS 1800 System Scenarios describes six scenarios which are considered to be the relevant cases for DCS 1800. The six scenarios described are - Single MS - Single BTS. - Multiple MSs - Multiple co-ordinated BTSs. - Multiple MSs - Multiple uncoordinated BTSs. - Co-located MSs, co-ordinated/uncoordinated. - Co-located BTSs, co-ordinated/uncoordinated. ETSI ETSI TR 101 115 V8.2.0 (2000-04) 18 (GSM 05.50 version 8.2.0 Release 1999) - Co-location with other systems. On each of these scenarios the system constraints related to the scenario are described, the RF requirements affected by the scenario are identified and the input information needed to study the scenario in detail is listed. Justifications for the DCS 1800 05.05 includes the analysis of the system scenarios to detailed RF requirements and presents and justifies the proposed changes to GSM 05.05 for DCS 1800. In the analysis part the relevant scenario calculations are made for each RF requirement and the most critical scenario requirement identified. The justification part then looks at the identified scenario requirement, compares it to the corresponding existing GSM 900 requirement and taking also into account the implementation issues and finally gives reasoning to the proposed change of the specific RF requirement. These documents are in Annex A The DCS 1800 requirements were originally developed for Phase 1 as a separate set of specifications, called DCS- specifications. For Phase two the DCS 1800 and GSM 900 requirements are merged. The main Phase 2 change requests of SMG2 in which the requirements for the DCS 1800 system were included into are listed below. CR 05.01-04 Combination of GSM 900 and DCS 1800 specifications. CR 05.05-37 rev1 Combination of 05.05 (GSM 900) and 05.05-DCS (DCS 1800) specifications. CR 05.08-55 rev1 Combination of GSM 900 and DCS 1800 and addition of National roaming. Further development of the DCS 1800 requirements for Phase 2 can be found in the other Phase 2 CRs of SMG2, the vast majority of which are valid both for DCS 1800 and GSM 900. The list of Phase 2 CRs of SMG2 can be found in Annex E. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 4 GSM 900 small cell system scenarios | There is one document which discusses the small cell system scenarios for GSM 900. The document is - Small cell system scenarios for GSM 900 (TDoc SMG2 104/92, revised as TDoc SMG2 104/92 rev1). Small cell system scenarios for GSM 900 uses the DCS 1800 system scenarios and justification document and derives from them the scenario requirements for GSM 900 small cells. It also calculates the worst case requirements based on minimum coupling loss of 59 dB. The document on GSM 900 small cell system scenarios is in Annex B. CR 03.30-02 on "Propagation models for different types of cells" gives a definition for a small cell and the typical cell parameters to calculate the propagation loss in a small cell. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 5 GSM 900 and DCS 1800 microcell system scenarios | GSM 900 and DCS 1800 microcells have been discussed by SMG2 in various meetings since late 1991. In SMG2#2 (May 1992) a small group was formed to collect together the various documents and make a proposal for the microcell RF parameters. As agreed by SMG2 there should be four microcell specific requirements, namely - transmit power; - receive sensitivity; - wideband noise; - blocking. As a result of the subgroup and other SMG2 activities there are three documents which can be used as baseline material for the microcell requirements. They are: - Microcell BTS RF parameters (TDoc SMG2 163/92); - Comments and proposals on Microcell RF parameters (TDoc 144/92); ETSI ETSI TR 101 115 V8.2.0 (2000-04) 19 (GSM 05.50 version 8.2.0 Release 1999) - Revised proposal for microcell RF parameters (TDoc SMG2 ad hoc 4/92). Microcell BTS RF parameters and Comments and proposals on Microcell RF parameters are joint papers giving the microcell scenarios and the requirements. The first one describes the two microcell scenarios, namely range and proximity, and presents the method to derive the detailed requirements starting from the scenarios. The latter document includes some corrections/updates to the scenarios, and proposes the detailed requirements. As described in the documents there are three classes of microcells, depending on the expected Minimum Coupling Loss between BTS and MS. This is to guarantee the optimum choice of BTS transmit powers while maintaining the operability of the system. The last of the microcell documents, Revised proposal for microcell RF parameters includes updates to the detailed requirement figures. All the microcell requirements were collected together and were presented to and approved by SMG#5. The documents on GSM 900 and DCS 1800 microcells are in Annex C. The relevant change requests where the detailed microcell requirements can be found, are listed below. CR 03.30-04 Microcell Radio planning aspects; CR 03.30-08 Microcell minimum coupling loss for small frequency offsets; CR 05.05-69 rev1 Microcell BTS RF parameters; CR 05.05-79 rev1 Alignment of microcell maximum peak power requirement presentation; CR 05.05-90 Update of DCS 1800 microcell RF parameters. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 6 Conversion factors | One of the tasks in ETSI/STC SMG2 has been to align the different RF requirements for the Phase 2 specifications. This was found necessary because in phase 1 some of the RF requirements dominated over others making them almost obsolete. Related to the alignment process it was found necessary to introduce a set of conversion factors to be able to compare different types of requirements measured with different measurement techniques. The original work assumptions were agreed on at SMG2#1 in February 1992 and they were reviewed in SMG2 ad hoc meeting in April 1992. There are two documents related to the conversion factors. They are: - Report of the ad hoc meeting on RF parameters (TDoc SMG2 61/92). - Agreed SMG2 conversion factors (TDoc SMG2 287/92). Report of the ad hoc meeting on RF parameters describes the process of deriving the conversion factors. In the ad hoc meeting there were number of input papers with practical measurement results of different measurement techniques, and in the ad hoc those measurement results were compared and the average of the results was chosen as a conversion factor. The following conversion factors were agreed on. - conversion from maximum peak power to average power in a 30 kHz bandwidth on carrier: => - 8 dB. - conversion from average power to maximum peak power in 30 kHz bandwidth: => + 8 dB at zero offset from carrier and + 9 dB at all other offsets. - conversion from average power in 100 kHz bandwidth to maximum peak power in 30 kHz bandwidth: => + 5 dB at offset above 1800 kHz from carrier. On the conversion factor from maximum peak power in 300 kHz bandwidth to maximum peak power in 30 kHz bandwidth no agreement was reached in the ad hoc meeting and hence the working assumption agreed on in SMG2 meeting is still assumed while pending for further validation. ETSI ETSI TR 101 115 V8.2.0 (2000-04) 20 (GSM 05.50 version 8.2.0 Release 1999) => - 8 dB at offset above 6 MHz from the carrier Agreed SMG2 conversion factors lists the above agreed conversion factors and proposes further a conversion factor of + 5 dB for conversions from 100 kHz bandwidth to 300 kHz bandwidth at offsets above 1800 kHz from the carrier. These documents are in Annex D |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 7 Repeaters | There are a number of documents describing the background to repeater scenarios. These are: - Repeater operating scenarios (Tdoc SMG2 29/94); - Repeater scenarios for DCS1800 (Tdoc SMG2 24/94); - Repeater scenarios (Tdoc SMG2 25/94); - Repeater out of band gain (Tdoc SMG2-RPT 20/94). Repeater operating scenarios describes the many different scenarios for which a repeater device might be used. Repeater scenarios for DCS 1800 describes two scenarios for DCS 1800 repeaters, the outdoor scenario and the indoor scenario. For each scenario, the performance requirements on the repeater are derived. Repeater scenarios derives the equations that describe the uplink and downlink performance of a repeater. Co-ordinated and uncoordinated scenarios are analysed resulting in outline proposals for repeater hardware requirements in GSM 05.05 and outline planning guidelines in GSM 03.30. Repeater out of band gain derives the requirements for the repeater out of band gain and provides planning guidelines when a repeater is in close proximity to other communication systems. These documents are in Annex E. The documents were presented to STC SMG2 in March 1994. In conclusion, it was decided that no single repeater specification would serve the large number of repeater scenarios that exist. As a consequence, it was agreed to add a specification for the repeater out of band performance to GSM 05.05 with guidelines for the specification and planning of repeaters in the GSM/DCS bands in GSM 03.30. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 8 Error Patterns for Speech Coder Developments | TD 164/95 in Annex F describes available error patterns. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 9 Simulations of Performance | Several documents in Annex G gives background information and simulation results of the GSM performance. ETSI ETSI TR 101 115 V8.2.0 (2000-04) 21 (GSM 05.50 version 8.2.0 Release 1999) |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 10 GSM 900 railway system scenarios | In 1993, the "Union Internationale de Chemin de Fer", UIC, decided to base a new railways pan-European system on GSM technology operating in the 900 MHz band. In 1995, the CEPT, in recommendation T/R25-09, decided that " the international requirements without excluding national requirements of railways for non-public digital radiocommunication system in the 900 MHz band should be covered by selecting appropriate sub-bands from the designated band 876-880 MHz (mobile station transmit) paired with 921-925 MHz (base station transmit) with a duplex separation of 45 MHz." During 1996, SMG2 in a two-step process discussed the RF parameters in GSM 05.05 for GSM-type equipments operating in this frequency band, called UIC equipments. Two documents were elaborated for this purpose. They are: - UIC system scenarios requirements; - UIC RF parameters. In UIC system scenarios requirements, the relevant system and interference scenarios for UIC equipments are identified and the noise levels allowed and the signal levels arising out of the worst cases are derived, both as regards intra-systems performance of a UIC network and towards other GSM-type systems in the neighbouring frequency bands. Basing on the former, UIC RF parameters discusses all the parameters in GSM 05.05 and determines the RF requirements for UIC equipments, to be in line with the scenario requirements where possible and feasible, or being a reasonable compromise where not. The specifications for other GSM900 and DCS1800 types of equipment are not affected, except possibly where there is absolutely no implications for their implementation. These documents are in annex H.1 and H.2, respectively. The resulting specifications were incorporated into GSM 05.05 by Change Request no. A027. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 11 Simulation results for GPRS receiver performance | The documents in annexes K, L, M, N, P, Q and W give background information and simulation results of GPRS receiver performance |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 12 Pico BTS RF scenarios | The documents in annex R give background information on pico BTS RF scenarios. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 13 CTS system scenarios | The document in annex S gives background information on CTS system scenarios. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 14 GSM 400 system scenarios | There is one document describing the GSM 400 system scenarios. The present document is: - GSM 400 system scenarios (Tdoc SMG2 190/99, revised as Tdoc SMG2 542/99). GSM 400 System Scenarios document presents GSM 400 operation primarily in respect of the 05.05 series of recommendations. All relevant scenarios for each part of 05.05 are considered and the most critical cases identified. As a result the present document gives background information for GSM 400 RF requirements presented in 05.05 specification. The present document on GSM 400 system scenarios is in Annex T. ETSI ETSI TR 101 115 V8.2.0 (2000-04) 22 (GSM 05.50 version 8.2.0 Release 1999) |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 15 MXM system scenarios | The document in Annex U gives background information for 850 and 1 900 MHz mixed mode system operation. 850 MHz and 1900 MHz mixed-mode is defined as a network that deploys both 30 kHz RF carriers and 200 kHz RF carriers in geographic regions where the Federal Communications Commission (FCC) regulations are applied. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 16 LCS scenarios | The documents in annex V gives background information on LCS scenarios. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 17 8-PSK Scenarios | The document in annex X gives background information on 8-PSK scenarios. ETSI ETSI TR 101 115 V8.2.0 (2000-04) 23 (GSM 05.50 version 8.2.0 Release 1999) Annex A: DCS 1800 System scenarios ETSI GSM TC TDoc GSM 259/90 Corfu, 1-5 October 1990 Source: GSM2 Ad Hoc on DCS1800, Bristol Title: DCS1800 - System Scenarios |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 0 INTRODUCTION | This paper discusses system scenarios for DCS1800 operation primarily in respect of the 05.05 series of recommendations. To develop the DCS1800 standard, all the relevant scenarios need to be considered for each part of 05.05 and the most critical case identified. The process may then be iterated to arrive at final parameters that meet both service and implementation requirements. Each scenario has three sections: a) lists the system constraints such as the separation of the MS and BTS, antenna height etc b) lists those sections of 05.05 that are affected by the constraints c) lists the inputs required to examine the implications of the scenarios The following scenarios are discussed: 1) Single MS, single BTS 2) Multiple MS and BTS where operation of BTS's is coordinated 3) Multiple MS and BTS where operation of BTS's is uncoordinated 4) Colocated MS 5) Colocated BTS 6) Colocation with other systems |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 1 SCENARIO 1 - SINGLE BTS AND MS | |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 1.1 Constraints | Aside from the frequency bands, the main constraint is the physical separation of the MS and BTS. The extreme conditions are when the MS is close to or remote from the BTS. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 1.1.1 Frequency Bands and Channel Arrangement (Section 2 of 05.05) | The system is required to operate in the following frequency bands - 1710 - 1785 MHz: mobile transmit, base receive; - 1805 - 1880 MHz: base transmit, mobile receive; with a carrier spacing of 200 kHz. ETSI ETSI TR 101 115 V8.2.0 (2000-04) 24 (GSM 05.50 version 8.2.0 Release 1999) In order to ensure the compliance with the radio regulations outside the band, a guard band of 200 kHz between the edge of the band and the first carrier is needed at the bottom of each of the two subbands. Consequently , if we call F1(n) the nth carrier frequency in the lower band, and Fu(n) the nth carrier frequency in the upper band, we have - Fl(n) = 1710.2 + 0.2*(n-512) (MHz) (512 < n < 885) - Fu(n) = Fl(n) + 95 (MHz) The value n is called the ABSOLUTE RADIO FREQUENCY CHANNEL NUMBER (ARFCN). To protect other services, channels 512 and 885 will not normally be used, except for local arrangements. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 1.1.2 Proximity | Table 1 shows examples of close proximity scenarios in urban and rural environments. Different antenna heights are considered; 15 m high antennas are assumed to have lower gain (10 dBi) than 30 m high antennas (18 dBi). Table 1: Worst case proximity scenarios Rural Urban Building Street Building Street [1] [1] BTS height, Hb (m) 20 15 15 30 30 MS height, Hm (m) 1.5 15 1.5 20 1.5 Horizontal separation (m) [4] 30 30 15 60 15 BTS antenna gain, Gb (dB) [2] 18 10 10 18 18 BTS antenna gain, G'b (dB) [3] 0 10 2 13 0 MS antenna gain, Gm (dB) 0 0 0 0 0 Path loss into building (dB) 6 6 Cable/Connector Loss (dB) 2 2 2 2 2 Body Loss (dB) 1 1 1 1 1 Path loss - antenna gain (dB) 71 66 65 69 71 Notes: 1) Handset at height Hm in building 2) Bore-sight gain 3) Gain in direction of MS 4) Horizontal separation between MS and BTS Path loss is assumed to be free space i.e. 37.5 + 20 log d(m) dB, where d is the length of the sloping line connecting the transmit and receive antennas. These examples suggest that the worst (ie lowest) coupling loss occurs in urban areas where the MS is in a street below the BTS. The coupling loss is then 65dB. The coupling loss is defined as that between the transmit and receive antenna connectors. ETSI ETSI TR 101 115 V8.2.0 (2000-04) 25 (GSM 05.50 version 8.2.0 Release 1999) |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 1.1.3 Range | Table 2 shows examples of range scenarios. The ranges quoted are the maximum anticipated for DCS1800 operation. In rural areas, this implies relatively flat terrain with little foliage loss. In urban areas, up to 1 km cells should be supported. In each case, an allowance must be made for in-building penetration loss. The figures shown are examples of those needed to achieve these cell sizes. In many situations, however, smaller cells may be used depending on the local conditions of terrain and traffic demand. Table 2: Worst case range scenarios Rural Urban BTS height, Hb (m) 60 50 MS height, Hm (m) 1.5 1.5 BTS antenna gain, Gb (dB) 18 18 MS antenna gain, Gm (dB) 0 0 Path loss into building (dB) [10] [15] Target range (km) 8 1 |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 1.2 05.05 Paragraphs Affected | Paragraph Title 2 Frequency bands and channel arrangement 4.1. Output power 6.1. Nominal error rates (maximum receiver levels) 6.2. Reference sensitivity level |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 1.3 Inputs needed | Working assumptions Propagation model Hata model (down to 1 km) Free space (up to [200] m maximum) Log normal shadow margin [6] dB Building penetration loss - urban [15] dB - rural [10] dB External noise (continuous and impulsive)Negligible MS noise figure: [12] dB BTS noise figure: [8] dB Ec/No: 6 dB + 2 dB (implementation margin) Location probability, Ps: 75% at cell boundary Implementation losses ETSI ETSI TR 101 115 V8.2.0 (2000-04) 26 (GSM 05.50 version 8.2.0 Release 1999) Body loss [3] dB (typical) 2 SCENARIO 2 - MULTIPLE MS AND BTS, COORDINATED Coordinated operation is assumed ie BTS's belong to same PLMN. Colocated MS's and colocated BTS's are dealt with in Scenarios 4 and 5, respectively. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 2.1 Constraints | The constraints are the same as those for scenario 1. ETSI ETSI TR 101 115 V8.2.0 (2000-04) 27 (GSM 05.50 version 8.2.0 Release 1999) |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 2.2 05.05 paragraphs affected | Paragraph Title 4.1. Adaptive power control - reduces co- and adjacent- channel interference - controls near/far effect for multiple MS's to same BTS 4.2. Output RF spectrum - to limit adjacent channel interference 4.3. Spurious emissions (in-band) - near/far effect to same BTS - see Fig 2.1. 4.5. Output level dynamic operation - near/far effect to same BTS - required limits comparable with spurious 4.7.1. Intermodulation attenuation, BTS - see Fig 2.2. 4.7.2. Intra BTS intermodulation attenuation - see Fig 2.3. 5.1. Blocking, in-band - near/far effect 6.3. Reference interference level |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 2.3 Inputs needed | Target Cluster size Assume 9 cell , i.e. 3 site, 120 degree sectored Fig 2.1: Near/far effect ETSI ETSI TR 101 115 V8.2.0 (2000-04) 28 (GSM 05.50 version 8.2.0 Release 1999) 3 cell, 120 degree sectored BTS. 400 kHz channel separation between sectors. 30 dB BTS transmitter/receiver coupling or transmitter/transmitter coupling. Fig 2.2: Scenario for Intermodulation distortion Fig 2.3: Intra BTS intermodulation attenuation 3 SCENARIO 3 - MULTIPLE MS AND BTS, UNCOORDINATED BTS's and MS's may belong to different DCS1800 networks. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 3.1 Constraints | The constraints are as in scenario 2 except that the MS's and BTS's belong to different PLMNS's and their operation is uncoordinated. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 3.2 05.05 paragraphs affected | Paragraph Title 4.2. Output RF spectrum ETSI ETSI TR 101 115 V8.2.0 (2000-04) 29 (GSM 05.50 version 8.2.0 Release 1999) 4.3. Spurious emissions (in-band, up and down links) - near/far effect to same BTS, see Fig 3.1 4.5. Output level dynamic operation - near/far effect to same BTS 4.7 Intermodulation See Fig 3.2 5.1. Blocking, in-band, up and down links See Fig 3.1. 5.2. Intermodulation, in-band See Fig 3.2. 5.3. Spurious response rejection |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 3.3 Inputs needed | Minimum frequency separation of carriers in BTS; assume 400kHz as for cluster size of 9. Figure 3.1: Blocking and Spurious BTS1 and BTS2 belong to different PLMN's MS1 affiliated to BTS1 PLMN; MS2 and MS3 affiliated to BTS2 PLMN ETSI ETSI TR 101 115 V8.2.0 (2000-04) 30 (GSM 05.50 version 8.2.0 Release 1999) Intermodulation products in BTS1 receiver Fig 3.2: Intermodulation |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 4 SCENARIO 4 - COLOCATED MS | Colocated MS which may be served by BTS from different networks ie MS's not synchronised. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 4.1 Constraints | Minimum separation of MS 1 m Guard band between up and down links 20 MHz Bandwidth of up and downlink bands 75 MHz. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 4.2 05.05 paragraphs affected | Paragraph Title 4.3.3. Spurious emissions, out-of-band 5.1. Blocking, out-of-band 5.3. Spurious response rejection 5.4. Spurious emissions [New 4.7.3 Intermodulation between MS] See Fig 4.1. ETSI ETSI TR 101 115 V8.2.0 (2000-04) 31 (GSM 05.50 version 8.2.0 Release 1999) Out-of-band intermods; MS1 and MS2 at full power Received signal at MS3 from BTS2 at reference sensitivity. By symmetry, MS1 will be affected by an I.M. product from MS2 and MS3 whenever MS3 is affected as shown above. In-band intermods. Fig 4.1: Intermodulation between MS |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 4.3 Inputs needed | Additional body losses; assume [3dB] |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 5 SCENARIO 5 - COLOCATED BTS | Two or more colocated BTS possibly from different PLMN's. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 5.1 Constraints | Coupling between BTS's may result either from the co-siting of BTS's or from several BTS's in close proximity with directional antenna. The maximum coupling between BTS' should be assumed to be [30] dB. This is defined as the loss between the transmitter combiner output and the receiver multi-coupler input. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 5.2 05.05 paragraphs affected | Paragraph Title 4.3. Spurious emissions 4.7.1. Intermodulation attenuation, BTS (See Fig 5.1.) 5.1. Blocking [30] dB coupling between BTS TX - RX [30] dB coupling between BTS TX - TX [30] dB coupling between BTS RX - RX ETSI ETSI TR 101 115 V8.2.0 (2000-04) 32 (GSM 05.50 version 8.2.0 Release 1999) BTS either same or different PLMN 5.3. Spurious response rejection 5.4. Spurious emissions |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 5.3 Inputs needed | None BTS3 different PLMN from BTS 1 and 2. Intermodulation products at MS3 receiver. Figure 5.1: Intermodulation scenario 6 SCENARIO 6 - COLOCATION WITH OTHER SYSTEMS DCS1800 systems will have to work in the presence of other mobile radio systems. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 6.1 Constraints | Operation of DCS1800 mobiles to be considered in close proximity with other systems. GSM phase 1 GSM phase 2 DECT Analogue cellular (TACS, NMT450/900, C450, R2000) and CT2 mobiles. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 6.2 05.05 paragraphs affected | Paragraph Title 4.3. Spurious emissions, out-of-band 5.1. Blocking, out-of-band 5.3. Spurious response rejection ETSI ETSI TR 101 115 V8.2.0 (2000-04) 33 (GSM 05.50 version 8.2.0 Release 1999) 5.4. Spurious emissions |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 6.3 Inputs needed | Performance specifications of other systems. ETSI ETSI TR 101 115 V8.2.0 (2000-04) 34 (GSM 05.50 version 8.2.0 Release 1999) ETSI GSM TC TDoc GSM 60/91 Saarbrucken, 14-18 January 1991 Source: GSM2 Title: Justifications for the proposed Rec. 05.05_DCS I INTRODUCTION The DCS1800 system requirements are defined in a paper entitled 'DCS1800 - System Scenarios' (GSM TDoc 259/90) and the parameters chosen either meet these requirements or represent a compromise between them and what can be manufactured at an appropriate cost. Changes to the 900 MHz standard have only been made where there is a specific system advantage or cost saving. Consideration has been given to methods of measurement for the changed specifications. Section II expands the scenarios paper into more detailed requirements for RF parameters. Section III follows the section numbering of Rec 05.05 and justifies the desired changes for DCS1800. The present document does not comment on simple changes from GSM900 to DCS1800 frequency bands since this change is assumed. II METHODOLOGY Unless otherwise stated the results of scenario calculations assume transmit powers of 39 dBm for the base and a 30 dBm for the mobile, both measured at their respective antenna connectors. The equivalent noise bandwidth of the transmitted signal is taken to be 120 kHz and that of the receiver 180 kHz. Worst case scenarios usually involve a "near/far" problem of some kind, the component scenario assumptions (as given in the scenarios paper for "near" and "far" can be summarised as follows. "Near" Coupling loss (dB) BTS -> MS 65 MS -> BTS 65 MS-> MS 40.5 BTS -> BTS 30 The coupling loss is defined between antenna connectors. The powers and sensitivities are discussed in section III of this paper, they are quoted here to enable scenario calculations to be performed. The transmitter power and receiver sensitivity are measured at the respective antenna connectors. "Far" Tx power (dBm) Rx Sensitivity (dBm) BTS 39 -104 MS 30 -100 Scenarios can involve uncoordinated or co-ordinated entities (MS or BTS) depending on whether they are from the same PLMN. With uncoordinated operation handover and power control are not used in response to the proximity of the BTS and more severe near/far problems can arise, however, co-ordinated scenarios are often more likely spatially and more likely to occur at lower frequency offsets. Unco-ordinated scenarios become critical when they involve mobiles being simultaneously on the edge of their serving cell and close to another operator's BTS, also the transmitter and affected receiver will be in different operator frequency allocations. It is most important that the co-ordinated scenario requirements are met where possible. The probability and consequences of the various scenarios must be taken into account when choosing the actual specification. For example, jamming a whole base station is a more serious consequence than jamming a single mobile and intermodulation scenarios which involve the co-location of 3 entities are consequently less likely than those which only involve 2. The remainder of this section outlines the key scenario calculations which affect the choice of parameters for Rec 05.05. Transmitted levels are those in the receiver bandwidth, although in many cases the test bandwidths are narrower because of the need to avoid switching transients affecting the measurement. ETSI ETSI TR 101 115 V8.2.0 (2000-04) 35 (GSM 05.50 version 8.2.0 Release 1999) |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 1 Transmitter | |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 1.1 Modulation, Spurs and Noise. | |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 1.1 Modulation, Spurs and Noise | . |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 1.1.1 Co-ordinated, BTS -> MS (Scenario 2, Fig 2.1) | Since the affected MS is close to its own base we only need to ensure adequate C/I at the BTS. Max. Tx noise level in Rx bandwidth = [BTS power] - [Power control range] - [C/I margin] - [Multiple interferers margin] = 39 - 30 - 9 -10 = -10 dBm. (BTS dynamic power control is optional, in the worst case it will be employed on the link to the affected MS but the other link will be at full power). |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 1.1.2 Uncoordinated, BTS -> MS (Scenario 3, Fig 3.1) | Max. Tx. level of noise in Rx. bandwidth = [MS sensitivity] - [C/I margin] - [Multiple interferers margin] + [Coupling loss] = -100 - 9 -10 + 65 = -54 dBm. Max. Tx level of spur in Rx bandwidth = [MS sensitivity] - [C/I margin] + [Coupling loss] = -100 - 9 + 65 = -44 dBm. 1.1.3 Co-ordinated & Uncoordinated MS -> BTS (Scenarios 2 & 3, Figs 2.1 &3.1) Max. Tx level in Rx bandwidth = [BTS sensitivity] - [C/I margin] + [Coupling loss] = -104 - 9 +65 = -48 dBm. Although the absolute spec. is the same the MS may find it easier to meet scenario 2 because it will be powered down. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 1.1.4 Co-ordinated & Uncoordinated MS->MS (Scenario 4) | Max Tx level in Rx bandwidth = [MS sensitivity] - [C/I margin] + [Coupling loss] = -100 - 9 + 40.5 = -68.5 dBm |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 1.1.5 Co-ordinated & Uncoordinated BTS->BTS (Scenario 5) | Max Tx level noise in Rx bandwidth= [BTS sensitivity] - [C/I margin] - [Multiple interferers margin] + [Coupling loss] = -104 - 9 - 10 + 30 = -93 dBm |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 1.2 Switching Transients | The peak level of transients in a 5 pole synchronously tuned measurement filter of bandwidth 100 kHz simulates their effect on the receiver. The transients only effect a few bits per timeslot and have approximately 20 dB less effect than continuous interference. Their peak level falls off at 20 dB decade both with increasing frequency offset and measurement bandwidth. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 1.2.1 Uncoordinated MS -> BTS (Scenario 3, Fig 3.1) | Max. peak level in effective Rx BW at MS = [Base sensitivity] - [C/I margin] + [Coupling loss] + [Transient margin] = - 104 - 9 +65 + 20 = -28 dBm |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 1.2.2 Uncoordinated BTS -> MS (Scenario 3, Fig 3.1) | Max. peak level in effective Rx BW at BTS = [MS sensitivity] - [C/I margin] + [Coupling loss] + [Transient margin] = -100 - 9 + 65 + 20 = -24 dBm ETSI ETSI TR 101 115 V8.2.0 (2000-04) 36 (GSM 05.50 version 8.2.0 Release 1999) |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 1.3 Intermodulation | |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 1.3.1 Co-ordinated, BTS -> MS (Scenario 2 , Fig 2.2 & 2 .3) | (Level of input signal 30 dB below wanted transmission). Required IM attenuation in BTS = [C/I margin] + [BTS power control range] + [margin for other IMs] = 9 + 30 + 3 = 42 dB |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 1.3.2 Uncoordinated, BTS ->MS (Scenario 3, Fig 3.2 top) | (Level of input signal 30 dB below wanted transmission). Required IM attenuation in BTS = [BTS power] - {[Max. allowed level at MS1] + [coupling loss BTS2->MS1]} = 39 - {{-100 - 9 - 3} + 65} = 86 dB |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 1.3.3 Uncoordinated, MS&MS-> BTS (Scenario 4, Fig 4.1 bottom) | (Level of input signal 40.5 dB below wanted transmission). Required IM attenuation in MS = [MS power] - {[Max. allowed level at BTS2] + [coupling loss MS->BTS2]} = 30 - {{-104 - 9 - 3} + 65} = 81 dB |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 1.3.4 Uncoordinated MS&MS-> MS (Scenario 4, Fig 4.1 top) | (Level of input signal 40.5 dB below wanted transmission). Required IM attenuation in MS = [MS power] - {[Max. allowed level at MS3] + [coupling loss MS->MS3]} = 30 - {{- 100 - 9 - 3} + 40.5} = 101.5 dB |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 2 Receiver | |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 2.1 Blocking | 2.1.1 Co-ordinated & Uncoordinated BTS-> MS (Scenario 2&3, Fig 2.1 & Fig 3.1) Max. level at MS receiver = [BTS power] + [Multiple interferers margin] - [Coupling loss] = 39 + 10 - 65 = -16 dBm |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 2.1.2 Co-ordinated MS-> BTS (Scenario 2, Fig 2.1) | Max level at BTS receiver = [MS power] - [Power control range] - [Coupling loss] = 30 - 20 - 65 = -55 dBm |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 2.1.3 Uncoordinated MS-> BTS (Scenario 3, Fig 3.1) | Max level at BTS receiver = [MS power] - [Coupling loss] = 30 - 65 = -35 dBm |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 2.1.4 Co-ordinated & Uncoordinated MS-> MS (Scenario 4 ) | Max. level at MS receiver = [MS power] - [Coupling loss] = 30 - 40.5 = -10.5 dBm ETSI ETSI TR 101 115 V8.2.0 (2000-04) 37 (GSM 05.50 version 8.2.0 Release 1999) |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 2.1.5 Co-ordinated & Uncoordinated BTS-> BTS (Scenario 5) | Max. level at BTS receiver = [BTS power] + [Multiple interferers margin] - [Coupling loss] = 39 +10 - 30 = 19 dBm |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 2.2 Intermodulation | 2.2.1 Co-ordinated & Uncoordinated BTS-> MS (Scenarios 2 & 3, Fig 3.2 middle) Max. received level at MS1 = [BTS power] - [Coupling loss BTS2->MS1] + [Margin for other IMs] = 39 - 65 + 3 = -23 dBm Required IM attenuation in MS is 42 dB for scenario 2 and 86 dB for scenario 3. The Rec. 05.05 section 5.2 test simulates scenario 3. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 2.2.2 Co-ordinated MS & MS -> BTS (Scenario 4) | Max. received level at BTS1 = [MS power] - [MS power control range] - [Coupling loss MS-> BTS1] + [Margin for other IMs] = 30 - 20 - 65 + 3 = -52 dBm |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 2.2.3 Uncoordinated MS & MS -> BTS (Scenario 4, Fig 3.2 lower) | Max. received level at BTS1 = [MS power] - [Coupling loss MS-> BTS1] + [Margin for other IM's] = 30 - 65 + 3 = -32 dBm |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 2.3 Maximum level | |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 2.3.1 Co-ordinated MS -> BTS (Scenario 1) | Max level at BTS = [MS power] - [Coupling loss] = 30 - 65 = -35 dBm. (The BTS must be capable of decoding the RACH which is at full power). |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 2.3.2 Co-ordinated BTS -> MS (Scenario 1) | Max level at MS = [BTS power] - [Coupling loss] = 39 - 65 = -26 dBm. (BTS dynamic power control is optional, in the worst case it will not be employed, also the MS must be capable of decoding the BCCH carrier). III JUSTIFICATIONS |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 1 SCOPE | 2 FREQUENCY BANDS AND CHANNEL ARRANGEMENT: The up and downlink frequencies have been changed to cover the 1.8 GHz band. The 374 carrier frequencies have been assigned ARFCNs starting at 512 . ETSI ETSI TR 101 115 V8.2.0 (2000-04) 38 (GSM 05.50 version 8.2.0 Release 1999) |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 3 REFERENCE CONFIGURATION: | |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 4 TRANSMITTER CHARACTERISTICS: | |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 4.1 Output power: | |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 4.1.1 Mobile Station: | MS power classes of 1 and ¼W have been chosen for DCS1800 defined in the same way as for GSM900. With a 30 m antenna height Hata's model predicts that the higher MS power class will not quite meet the target ranges given in the system scenarios paper both for urban and rural areas. The requirement for a cheap, small, low power handset is also an important constraint. It is felt that the chosen power classes represent a reasonable compromise between these conflicting requirements. A 20 dB power control range has been chosen for both classes of mobile since it is believed that this will give most of the available improvement in uplink co-channel interference. Since the chosen power classes and hence power control levels are even numbers in dBm they will not fit into the existing numbering scheme, so a new one has been used. These numbers are only of editorial significance. The absolute tolerance on power control levels below 13 dBm has been increased by 1 dB because of manufacturers' concerns about implementation. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 4.1.2 Base Station: | Following GSM 900, the BTS power classes are specified at the combiner input. In order to provide the operator some flexibility four power classes have been specified in the range 34 to 43 dBm. In fact the four lowest power classes from GSM 900 have been retained although the numbering has been changed. The 39 dBm BTS power measured at the antenna connector might typically match a 30 dBm mobile. The tolerance on the BTS static power control step size has been relaxed to simplify implementation, control of the BTS power to an accuracy of less than 1dB was felt to be unnecessary. The penultimate paragraph has been reworded because a class 1 mobile no longer has 15 power steps. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 4.2 Output RF spectrum: | The BTS is not tested in frequency hopping mode. If the BTS uses baseband frequency hopping then it would add little to test in FH mode; if it uses RF hopping then the test will be complicated by permissible intermodulation products (see section 4.7) from BTSs which do not de-activate unallocated timeslots. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 4.2.1 Spectrum due to the modulation: | The relaxation for MSs with integral antennas has been removed. The measurement has been extended to cover the whole transmit band and beyond 1800 kHz from carrier measurements are only taken on DCS1800 carrier frequencies using a 100 kHz bandwidth. This technique still avoids permissible switching transients, is fairly quick and closely reflects the receiver bandwidth and hence the system scenario. It is now a measurement of broadband noise as well as modulation. The technique proposed in CR 30 for counting spur exceptions in FH mode for Rec 05.05 is also included here, The table has been split into those parts which apply to the mobile and those which apply to the base reflecting the difference in their respective scenario requirements. When operating at full power, the table below shows the frequency offset at which scenario requirements are met ETSI ETSI TR 101 115 V8.2.0 (2000-04) 39 (GSM 05.50 version 8.2.0 Release 1999) 39 dBm BTS at ant. conn. 30 dBm MS Scenario 2 400 kHz(1.1.1) 400 kHz (1.1.3) Scenario 3 missed by 10dB at 6 MHz(1.1.2) 6 MHz (1.1.3) The figures in brackets are the relevant scenario requirement sub-section numbers in section II of the present document. Exceptions i and ii below the table define the maximum number of exception channels appropriate to the frequency bands tested. For the BTS permissible intermodulation products must be avoided. Since the table entries are relative, as the power level of the transmitter is reduced, the absolute specification becomes tighter. Exceptions iii and iv stop the transmitters having to exceed the requirement of scenario 3. Further relaxations are permitted at low frequency offsets; for the MS scenario 3 is unlikely below 600 kHz and the requirement of scenario 2 is used; for the BTS, the 10 dB multiple interferers margin is excessive below 1800 kHz and the minimum level is increased by 5 dB. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 4.2.2 Spectrum due to switching transients: | a) Mobile Station The table has been modified in accordance with the new mobile power classes. The transients are always above the modulation at 400 kHz offset and so the table collapses to a single row. Requirement 1.2.1 for scenario 3 becomes -38.5 dBm in 30 kHz. The current specification meets this requirement at offsets above 2.4 MHz while the 4.2.1 test only meets scenario 3 at offsets above 6MHz. The specification on transients is not the limiting case and need not be changed. b) Base Station Requirement 1.2.2 for scenario 3 becomes -34.5 dBm in 30 kHz. With the current specification a 39 dBm BTS meets this requirement at 600 kHz. Again no change is proposed. This figure assumes that "dBc" means relative to the on- carrier power in 30 kHz; a possible ambiguity in the wording has been removed. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 4.3 Spurious emissions: | |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 4.3.1 Principle of the specification: | Although 4.2.1 now covers the whole transmit band, the in band part of 4.3.1 is still required to check the behaviour of switching transients beyond 1800 kHz and to catch any spurs missed in 4.2.1. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 4.3.2 Base Station: | The protection of frequencies outside the DCS1800 band is unchanged, but the spurious emissions in the transmit band are only permitted up to -36 dBm which is below the CEPT limit of -30 dBm but the same as Rec. 05.05. The same applies to the MS transmit band in 4.3.3. The new base receive band is given the same protection as before measured in the modified conditions of 4.2.1, this meets scenario requirement 1.1.5 scaled to a measurement bandwidth of 100 kHz. The GSM 900 base receive band is also protected but only when the co-siting of GSM and DCS BTSs occurs. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 4.3.3 Mobile Station: | This section consists of two blanket specifications one for transmit mode and one for idle mode Specific tests of the MS receive band are also given. When allocated a channel, the transmit band and out-of-band specifications are the same as for the BTS in 4.3.2. These are consistent with 4.2.1 and the CEPT specifications for spurious emissions. ETSI ETSI TR 101 115 V8.2.0 (2000-04) 40 (GSM 05.50 version 8.2.0 Release 1999) In idle mode the CEPT specification below 1 GHz is also applied to the DCS transmit and receive bands using a 100 kHz measurement bandwidth, this specification also exceeds scenario requirement 1.1.3 for the MS transmit band. however, the number of mobiles in idle mode may be quite large. The test of the MS receive band meets scenario requirement 1.1.4 and uses the modified conditions of 4.2.1. 5 exception channels are permitted for discrete spurious, it is rather unlikely that two MS will be one metre apart and receiving at one of these exception channels. Protection of the GSM 900 MS receive band is also provided. The specification is 6 dB tighter reflecting the reduced propagation loss between colocated MS at 900 MHz. The dependence of this test on power class has been removed since all mobiles are hand portables. No extra testing of the MS receive band in idle mode is made because it is unlikely to be worse than when allocated a channel. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 4.4 Radio frequency tolerance: | |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 4.5 Output level dynamic operation: | |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 4.5.1 Base station: | This specification only affects the interference experienced by co-channel cells in the same PLMN. The requirement on the relative power level of unactivated timeslots has been relaxed from -70 to -30 dBc in line with the BTS power control range. It is understood that "dBc" includes the static but not dynamic power control.The specification has been extended to cover the whole transmit band because the residual power may not be highest on carrier. The measurement bandwidth is specified as at least 300 kHz due to problems with ringing of the measurement filter just after an active burst has finished. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 4.5.2 Mobile station: | The power level between active bursts from the MS affects the serving BTS receiver. The power measured in 100 kHz on carrier will be similar to that measured in the receiver bandwidth which must be less than -48 dBm to meet scenario requirement 1.1.3. The absolute specification has been tightened from -36 to -47 dBm in line with this requirement but the relative specification has been retained. Allowing 10 dB for the peak-to-mean ratio of the power between active bursts if it is noise-like, the relative specification will meet this scenario requirement for a 1W MS. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 4.6 Phase accuracy: | |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 4.7 Intermodulation attenuation: | The definition of intermodulation attenuation has been moved from 4.7.1 to 4.7 to make it clear that it applies to subsections 4.7.1, 4.7.2 and 4.7.3. A note concerning possible problems with VHF broadcast signals has been added because these are at the difference between the DCS up and downlink frequencies. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 4.7.1 Base transceiver station: | |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 4.7.2 Intra BTS intermodulation attenuation: | |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 4.7.3 Intermodulation between MS: | Section 4.7.3 of the 900 MHz specification concerned the mobile PBX. The mobile PBX is no longer included in Rec. 02.06, there is no type approval for it and consequently the original section 4.7.3 text has been removed. The new section 4.7.3 relates to intermodulation between MS transmitters, an area which was not covered in the 900 MHz standard. In the proposed measurement, the level of the interfering signal simulates that from a very close MS and the required IM attenuation is to protect MS or BS receivers in the vicinity. MS transmit intermods are covered by scenario requirements ETSI ETSI TR 101 115 V8.2.0 (2000-04) 41 (GSM 05.50 version 8.2.0 Release 1999) 1.3.3 and 1.3.4. If the product lands in the BTS receive band 81 dB IM attenuation is required, if the product lands in the MS receive band 101.5 dB IM attenuation is required in the MS transmitter which produces the IM. Both these scenarios require the co-location of 3 objects (MS or BTS) with the correct frequency relationship. Experiments performed by manufacturers on 900 MHz PA's indicate that 50 dB attenuation is achievable at all frequency offsets. A tighter specification would require the use of an isolator or more linearity in the PA design. A specification of 50 dB tested at 800 kHz offset was agreed. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 5 RECEIVER CHARACTERISTICS: | A clarification of the of the measurement point for the receiver specifications in line with that for the transmitter has been made. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 5.1 Blocking characteristics: | The MS blocking specification close to the received channel has not been changed, this is limited by the receive synthesizer phase noise. At higher frequency offsets the blocking specification relates to the DCS1800 band and the feasibility of the receive filter. The proposed specification is shown below, the dashed line shows a possible receive filter frequency response. The blocking specification at > 3 MHz offset in the receive band misses the scenario requirement 2.1.1 (-16 dBm) by 10 dB, but the transmit band specification meets scenario requirement 2.1.4 (-10.5 dBm). Power consumption considerations make it undesirable to tighten the receive band specification. The outside the DCS1800 band the 0 dBm specification has been retained. The combination of these proposals amounts to a filter specification over the MS receive band as shown below. -28 -24 -20 -16 -12 -8 -4 0 1680 1700 1720 1740 1760 1780 1800 1820 1840 1860 1880 1900 1920 1940 1960 1980 2000 Level dBm The BTS blocking requirement has been significantly relaxed because the MS power classes are lower. Scenario requirement 2.1.2 is -55 dBm which considers blocking from the bases own MS's. Requirement 2.1.3 is -35 dBm which is for mobiles from other operators. The proposal meets the scenario requirements even at 600 kHz offset and exceeds it by 10 dB beyond 800 kHz. ETSI ETSI TR 101 115 V8.2.0 (2000-04) 42 (GSM 05.50 version 8.2.0 Release 1999) The consequence of failing to meet this scenario is that the whole base station is blocked. For this reason it is desirable for the base station to exceed the scenario requirement if possible. The out-of-band specification has not been changed, although it does not meet scenario requirement 2.1.5 (19 dBm). This is because the 30 dB coupling loss assumption between base stations is rather pessimistic, it corresponds to two 18 dBi antennas on boresight 17 m apart. Under these circumstances, operators may need to adopt specific mutual arrangements (eg. extra operator specific receive filters) which need not form part of the DCS1800 standard. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 5.2 Intermodulation characteristics: | The 900 MHz standard for handportables limits the maximum level to -49 dBm. Any tightening of this specification will increase the power consumption of the receiver. Since DCS1800 is designed for handportables this figure is now applied to all MSs. The proposed level of -49 dBm for the MS fails to meet scenario requirement 2.2.1 by 23 dB, but the only consequence is that the MS is de-sensed when close to a BTS with the appropriate transmitters active. The worst case for BTS receiver IMs is when two MSs approach the base, the scenario requirement is covered in sections 2.2.2 & 2.2.3 and is -55 dBm for co-ordinated mobiles and -35 dBm for uncoordinated. Again -49 dBm has been proposed since the probability of the uncoordinated scenario is low both spatially and spectrally. If the coupling loss between both MSs and the BTS increases by 1dB the level of a third order IM product will reduce by 3 dB, thus if the coupling loss assumption between MS and BTS is increased by 5 dB to 70 dB then the scenario would be met. A note concerning the VHF broadcast problem has been added as in 4.7 for transmiiter intermodulation. ETSI ETSI TR 101 115 V8.2.0 (2000-04) 43 (GSM 05.50 version 8.2.0 Release 1999) |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 5.3 Spurious response rejection: | This section concerns exceptions to the blocking specification due to spurs in the receive synthesizer and mixer causing spurious responses. The numbers of exception channels has been doubled to reflect the wider receive band.For the BTS the in-band blocking specification can cover frequency offsets of Ý 95 MHz depending on the receive frequency and including the 20 MHz extension of the receive band defined in section 5.1. Thus the boundary between parts a and b of the specification has been moved from 45 to 95 MHz because the receive band is now 50 MHz wider. Following the above logic the breakpoint between parts a and b for the MS should occur at -95 and +115 MHz but in the interests of simplicity the same breakpoint is proposed as for the BTS. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 5.4 Spurious emissions: | Since the MS receiver spurious emissions are covered by the idle mode aspect of 4.3.3 this section now only refers to the BTS. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 6 TRANSMITTER/RECEIVER PERFORMANCE: | |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 6.1 Nominal error rates (NER): | The scenario requirement for the maximum received level at the MS is -26 dBm (requirement 2.3.2). The figure of -23 dBm is also in approximate alignment with the blocking specification at > 3 MHz The required NER for the static channel above at -23 dBm has been increased to ½% in line with CR 28 Under multipath conditions the peak signal level exceeds the mean level. In order to prevent significant clipping the maximum level under multipath conditions has been set to -40 dBm. Multipath reception conditions occur when there is no line of sight path and the received signal level is likely to be lower. The same specifications have been applied to the BTS receiver. |
86f4ee11213c3a4a69f9d6c104b522df | 101 115 | 6.2 Reference sensitivity level: | Simulations of TU50 and HT100 at 1.8 GHz have been performed and table 1 has been modified appropriately. The RA130 results at 1.8 GHz are taken from the RA250 results at 900 MHz. Allowance has been made for enhanced bad frame indication in accordance with CR 27. The MS sensitivity has been relaxed by 2 dB to simplify the MS at the expense of a slightly higher BTS power requirement, to balance the up and downlinks. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.