hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.3.2.1.1 Setting of the Polling bit | ................................................................................................................. 41 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.3.2.1.2 Segmentation of a SDU | .................................................................................................................. 41 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.3.3 Reception of AMD PDU by the receiver | ................................................................................................... 41 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.3.4 Abnormal cases | .......................................................................................................................................... 42 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.3.4.1 Timer_Poll timeout | ............................................................................................................................... 42 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.3.4.2 Receiving a PU outside the receiving window | ..................................................................................... 42 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.3.4.3 Timer_Discard timeout | ......................................................................................................................... 42 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.3.4.3.1 SDU discard with explicit signalling | .............................................................................................. 42 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.3.4.3.2 SDU discard without explicit signalling | ......................................................................................... 42 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.3.4.4 VT(DAT) > MaxDAT | .......................................................................................................................... 42 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.3.4.5 Invalid length indicator value | ............................................................................................................... 42 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.4 RLC reset procedure | ........................................................................................................................................ 42 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.4.1 Purpose | ....................................................................................................................................................... 42 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.4.2 Initiation | ..................................................................................................................................................... 43 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.4.2.1 RESET PDU contents to set | ................................................................................................................. 43 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.4.3 Reception of the RESET PDU by the receiver | ........................................................................................... 43 (3G TS 25.322 version 3.1.2 Release 1999) ETSI TS 125 322 V3.1.2 (2000-01) ETSI 3GPP 3G TS 25.322 V3.1.2 (2000-01) 5 3G TS 25.322 version 3.1.2 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.4.3.1 RESET ACK PDU contents to set | ........................................................................................................ 43 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.4.4 Reception of the RESET ACK PDU by the sender | .................................................................................... 43 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.4.5 Abnormal cases | .......................................................................................................................................... 43 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.4.5.1 Timer_RST timeout | .............................................................................................................................. 43 11.4.5.2 VT(RST) ≥ MaxRST............................................................................................................................ 43 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.5 STATUS PDU transfer procedure | ................................................................................................................... 44 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.5.1 Purpose | ....................................................................................................................................................... 44 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.5.2 Initiation | ..................................................................................................................................................... 44 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.5.2.1 Piggybacked STATUS PDU | ................................................................................................................ 44 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.5.2.2 STATUS PDU contents to set | .............................................................................................................. 45 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.5.3 Reception of the STATUS PDU by the sender | .......................................................................................... 45 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.5.4 Abnormal cases | .......................................................................................................................................... 45 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.5.4.1 EPC reaches zero and the requested PUs have not been received | ........................................................ 45 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.6 SDU discard with explicit signalling procedure | .............................................................................................. 45 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.6.1 Purpose | ....................................................................................................................................................... 45 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.6.2 Initiation | ..................................................................................................................................................... 45 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.6.2.1 Piggybacked STATUS PDU | ................................................................................................................ 46 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.6.2.2 STATUS PDU contents to set | .............................................................................................................. 46 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.6.3 Reception of the STATUS PDU by the receiver | ........................................................................................ 46 11.6.4 Reception of STATUS PDU if VR(R) ≥ SN_MRW.................................................................................. 46 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.6.5 Expiration of timer Timer_MRW | ............................................................................................................... 46 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.6.6 Abnormal cases | .......................................................................................................................................... 47 11.6.6.1 Obsolete/corrupted MRW command.................................................................................................... 47 |
ba1e9287f08e74d1acff555e4c37747d | 125 322 | 11.6.6.2 VT(MRW) equals MaxMRW | ............................................................................................................... 47 Annex A (informative): SDL diagrams........................................................................................................48 Annex B (informative): Pseudo code describing AMD PDU header Co... |
84429ef17baf284fcb30a25a4eac5409 | 126 911 | 1 Scope | ........................................................................................................................................................5 |
84429ef17baf284fcb30a25a4eac5409 | 126 911 | 2 References | ................................................................................................................................................5 |
84429ef17baf284fcb30a25a4eac5409 | 126 911 | 3 Definitions, symbols and abbreviations | ...................................................................................................6 |
84429ef17baf284fcb30a25a4eac5409 | 126 911 | 3.1 Definitions | ......................................................................................................................................................... 6 |
84429ef17baf284fcb30a25a4eac5409 | 126 911 | 3.2 Symbols | ............................................................................................................................................................. 6 |
84429ef17baf284fcb30a25a4eac5409 | 126 911 | 3.3 Abbreviations | ..................................................................................................................................................... 6 4 General.....................................................................................................................................................8 |
84429ef17baf284fcb30a25a4eac5409 | 126 911 | 5 Multiplex Protocol | ...................................................................................................................................8 |
84429ef17baf284fcb30a25a4eac5409 | 126 911 | 6 Control Protocol | .......................................................................................................................................8 |
84429ef17baf284fcb30a25a4eac5409 | 126 911 | 6.1 Usage of DRAWING_ORDER-information for MPEG-4 video objects | .......................................................... 9 |
84429ef17baf284fcb30a25a4eac5409 | 126 911 | 7 Video Codec | ............................................................................................................................................9 |
84429ef17baf284fcb30a25a4eac5409 | 126 911 | 7.1 General Recommendations | ................................................................................................................................ 9 |
84429ef17baf284fcb30a25a4eac5409 | 126 911 | 7.2 H.263 | ................................................................................................................................................................. 9 |
84429ef17baf284fcb30a25a4eac5409 | 126 911 | 7.3 Other Video Codecs | ......................................................................................................................................... 10 |
84429ef17baf284fcb30a25a4eac5409 | 126 911 | 8 Audio Codec | ..........................................................................................................................................11 |
84429ef17baf284fcb30a25a4eac5409 | 126 911 | 8.1 AMR Codec | ..................................................................................................................................................... 11 |
84429ef17baf284fcb30a25a4eac5409 | 126 911 | 8.2 Other Audio Codecs | ......................................................................................................................................... 11 |
84429ef17baf284fcb30a25a4eac5409 | 126 911 | 9 Data Protocols | ........................................................................................................................................11 |
84429ef17baf284fcb30a25a4eac5409 | 126 911 | 10 Terminal Procedures | ..............................................................................................................................11 |
84429ef17baf284fcb30a25a4eac5409 | 126 911 | 11 Interoperation with Other Terminals | .....................................................................................................11 |
84429ef17baf284fcb30a25a4eac5409 | 126 911 | 11.1 Audio Codecs | ................................................................................................................................................... 11 |
84429ef17baf284fcb30a25a4eac5409 | 126 911 | 12 Optional Enhancements | .........................................................................................................................11 |
84429ef17baf284fcb30a25a4eac5409 | 126 911 | 13 Multipoint Considerations | .....................................................................................................................11 |
84429ef17baf284fcb30a25a4eac5409 | 126 911 | 14 Other Recommendations | ........................................................................................................................11 Annex A (informative): Change Request History 12 History................................................................................................................................................ |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 1 Scope | The present document specifies the Radio sub-system link control implemented in the Mobile Station (MS), Base Station System (BSS) and Mobile Switching Centre (MSC) of the digital cellular telecommunications systems GSM. Unless otherwise specified, references to GSM also include include operation in any band. |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 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. • Fo... |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 1.2 Abbreviations | Abbreviations used in the present document are listed in GSM 01.04. |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 2 General | The radio sub-system link control aspects that are addressed are as follows: - Handover; - RF Power control, including fast power control for ECSD; - Radio link Failure; - Cell selection and re-selection in Idle mode, in Group Receive mode and in GPRS mode (see GSM 03.22); - CTS mode tasks. Handover is required to main... |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 3 Handover | |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 3.1 Overall process | The overall handover process is implemented in the MS, BSS and MSC. Measurement of radio subsystem downlink performance and signal levels received from surrounding cells, is made in the MS. These measurements are signalled to the BSS for assessment. The BSS measures the uplink performance for the MS being served and al... |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 3.2 MS measurement procedure | A procedure shall be implemented in the MS by which it monitors the downlink RX signal level and quality from its serving cell and the downlink RX signal level and BSIC of surrounding BTS. The method of identification of surrounding BTS is described in clause 7.2. The requirements for the MS measurements are given in c... |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 3.3 BSS measurement procedure | A procedure shall be implemented in the BSS by which it monitors the uplink RX signal level and quality from each MS being served by the cell. In the case of a multislot configuration the evaluation shall be performed on a timeslot per timeslot basis. A procedure shall be implemented by which the BSS monitors the level... |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 3.4 Strategy | The handover strategy employed by the network for radio link control determines the handover decision that will be made based on the measurement results reported by the MS/BSS and various parameters set for each cell. Network directed handover may also occur for reasons other than radio link control, e.g. to control tr... |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 4 RF power control | |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 4.1 Overall process | RF power control is employed to minimize the transmit power required by MS or BSS whilst maintaining the quality of the radio links. By minimizing the transmit power levels, interference to co-channel users is reduced. |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 4.2 MS implementation | RF power control shall be implemented in the MS. The power control level to be employed by the MS on each uplink channel, except PDCH, is indicated by means of the power control information sent either in the layer 1 header of each SACCH message block (see GSM 04.04) on the corresponding downlink channel, or in a dedic... |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 4.3 MS power control range | The range over which a MS shall be capable of varying its RF output power shall be from its maximum output down to its minimum, in steps of nominally 2 dB. GSM 05.05 gives a detailed definition of the RF power level step size and tolerances. ETSI ETSI TS 100 911 V8.5.0 (2000-10) 13 (GSM 05.08 version 8.5.0 Release 1999... |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 4.4 BSS implementation | RF power control, including fast power control for ECSD, may optionally be implemented in the BSS. |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 4.5 BSS power control range | The range over which the BSS shall be capable of reducing its RF output power from its maximum level shall be nominally 30 dB, in 15 steps of nominally 2 dB. GSM 05.05 gives a detailed definition of the RF power level step size and tolerances. |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 4.6 Strategy | The RF power control strategy employed by the network determines the ordered power level that is signalled to the MS, and the power level that is employed by the BSS. The power level to be employed in each case will be based on the measurement results reported by the MS/BTS and various parameters set for each cell. The... |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 4.7 Timing | Upon receipt of a command from an SACCH to change its power level on the corresponding uplink channel, the MS shall change to the new level at a rate of one nominal 2 dB power control step every 60 ms (13 TDMA frames), i.e. a range change of 15 steps should take about 900 ms. The change shall commence at the first TDMA... |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 5 Radio link failure | |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 5.1 Criterion | The criterion for determining Radio Link Failure in the MS shall be based on the success rate of decoding messages on the downlink SACCH. For a circuit switched multislot configuration, only the main SACCH shall be used for determining Radio Link Failure. For GPRS, Radio Link Failure is determined by the RLC/MAC protoc... |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 5.2 MS procedure | The aim of determining radio link failure in the MS is to ensure that calls with unacceptable voice/data quality, which cannot be improved either by RF power control or handover, are either re-established or released in a defined manner. In general the parameters that control the forced release should be set such that ... |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 5.3 BSS procedure | The criteria for determining radio link failure in the BSS should be based upon either the error rate on the uplink SACCH(s) or on RXLEV/RXQUAL measurements of the MS. The exact criteria to be employed shall be determined by the network operator. For channels used for a voice group call, the radio link failure procedur... |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 6 Idle mode tasks | |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 6.1 Introduction | Whilst in idle mode, an MS shall implement the cell selection and re-selection procedures described in GSM 03.22. These procedures make use of measurements and sub-procedures described in this clause. The procedures ensure that the MS is camped on a cell from which it can reliably decode downlink data and with which it... |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 6.2 Measurements for normal cell selection | The measurements of this clause shall be performed by an MS which has no prior knowledge of which GSM or DCS 1 800 RF channels are BCCH carriers. The MS shall search all RF channels within its bands of operation, take readings of received RF signal level on each RF channel, and calculate the RLA_C for each. The averagi... |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 6.3 Measurements for stored list cell selection | The MS may include optional storage of BCCH carrier information when switched off as detailed in GSM 03.22. For example, the MS may store the BCCH carriers in use by the PLMN selected when it was last active in the GSM 900 or DCS 1 800 network. The BCCH list may include BCCH carriers from more than one band in a multi ... |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 6.4 Criteria for cell selection and reselection | The path loss criterion parameter C1 used for cell selection and reselection is defined by: C1 = (A - Max(B,0)) where A = RLA_C - RXLEV_ACCESS_MIN B = MS_TXPWR_MAX_CCH - P except for the class 3 DCS 1 800 MS where: B = MS_TXPWR_MAX_CCH + POWER OFFSET - P RXLEV_ACCESS_MIN = Minimum received signal level at the MS requir... |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 6.5 Downlink signalling failure | The downlink signalling failure criterion is based on the downlink signalling failure counter DSC. When the MS camps on a cell, DSC shall be initialized to a value equal to the nearest integer to 90/N where N is the BS_PA_MFRMS parameter for that cell (see GSM 05.02). Thereafter, whenever the MS attempts to decode a me... |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 6.6 Measurements for Cell Reselection | Upon completion of cell selection and when starting the cell reselection tasks, the MS shall synchronize to and read the BCCH information for the 6 strongest non-serving carriers (in the BA) as quickly as possible within the times specified in clause 6.6.1. For multi band MSs the strongest non-serving carriers may belo... |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 6.6.1 Monitoring of received signal level and BCCH data | Whilst in idle mode an MS shall continue to monitor all BCCH carriers as indicated by the BCCH allocation (BA - See table 1). A running average of received signal level (RLA_C) in the preceding 5 to: Max {5, ((5 * N + 6) DIV 7) * BS_PA_MFRMS / 4} seconds shall be maintained for each carrier in the BCCH allocation. N is... |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 6.6.2 Path loss criteria and timings for cell re-selection | The MS is required to perform the following measurements (see GSM 03.22) to ensure that the path loss criterion to the serving cell is acceptable. At least every 5 s the MS shall calculate the value of C1 and C2 for the serving cell and re-calculate C1 and C2 values for non serving cells (if necessary). The MS shall th... |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 6.6.3 Cell reselection algorithm for SoLSA | At least for every new sample or every second, whichever is the greatest, the MS calculate the value of C1, C2 and C4 for the serving cell and the non-serving cells. The MS shall make a cell reselection if: i) The path loss criterion parameter (C1) for the serving cell falls below zero for a period of 5 seconds. ii) A ... |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 6.6.4 Algorithm for cell re-selection from GSM to UTRAN | If the broadcast neighbour cell list includes UTRAN cells or UTRAN frequencies (with or without scrambling code group information), the MS shall, at least every 5 s update the value RLA_C for the serving cell and each of the at least 6 strongest non serving GSM cells. The MS shall then reselect a suitable (see TS 25.30... |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 6.7 Release of TCH and SDCCH | |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 6.7.1 Normal case | When the MS releases all TCHs or SDCCH and returns to idle mode or packet idle mode, it shall, as quickly as possible, camp on the cell whose channel has just been released. If the full (P)BCCH data for that cell was not decoded in the preceding 30s, the MS shall then attempt to decode the full (P)BCCH data. Until the ... |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 6.7.2 Call re-establishment | In the event of a radio link failure, call re-establishment may be attempted (according to the procedure in GSM 04.08). The MS shall perform the following algorithm to determine which cell to use for the call re-establishment attempt. i) The received signal level measurement samples taken on the carriers indicated in t... |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 6.8 Abnormal cases and emergency calls | When in the limited service state (see GSM 03.22) the aim is to gain normal service rapidly and the following tasks shall be performed, depending on the conditions, as given in the table below: a) The MS shall monitor the received signal level of all RF channels within its bands of operation, and search for a BCCH carr... |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 7 Network pre-requisites | |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 7.1 BCCH carriers | The BCCH carrier shall be continuously transmitted on all timeslots and without variation of RF level. However, the RF power level may be ramped down between timeslots to facilitate switching between RF transmitters. ETSI ETSI TS 100 911 V8.5.0 (2000-10) 24 (GSM 05.08 version 8.5.0 Release 1999) Furthermore, 8-PSK modu... |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 8 Radio link measurements | Radio link measurements are used in the handover and RF power control processes. In particular, radio-subsystem directed handover is defined as a change of channel(s) during a call either because of degradation of the quality of one or more of the current serving channel(s), or because of the availability of other chan... |
4f752c751d635d19ec70230db7aa6c3c | 100 911 | 8.1 Signal level |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.