hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
e1df81e32c85ac85801df65e6181a587 | 100 596 | 9.3.58 LLP APDU | This is a variable length element that conveys an embedded message or message segment associated with the higher level protocol LLP, as defined in GSM 04.71. This element can be sent from the BSC to the BTS or to the Standalone Type B LMU, and vice versa. 8 7 6 5 4 3 2 1 Element identifier 1 Length 2 The rest of the in... |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 1 Scope | The present document specifies the link layer used for signalling on the A-bis interface between BSC and BTS. The use and general aspects of the A-bis interface are described in GSM 08.51 and the interface aspects in GSM 08.52. The Link Access Procedure on the D-channel (LAPD) specification used on the A-bis interface ... |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 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. • Fo... |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 3 Definitions and abbreviations | The following abbreviations and acronyms are used in the present document. Ai Action indicator BCF Base Station Control Function BSC Base Station Controller BTS Base Transceiver Station C/R Command/Response field bit GSM Global System for Mobile communication L2ML Layer 2 Management Link LAPD Link Access Procedure on t... |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 4 General description | The following information categories are supported by the procedures of this layer 2 Recommendation: - signalling (including Short Message Service (SMS) information); - operation and maintenance; - layer 2 management. For each of these categories the BSC may have one or more layer 2 links to every TRX and BCF. The sign... |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 5 Functional contents | The basic functional content of the layer 2 protocol is: - transparent layer 2 links and time fill; - point-to-point dedicated layer 2 links addressing both physical entities and functional entities; - point-to-multipoint addressed links used for layer 2 management; - basic functions for TEI assignment and management; ... |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 6 LAPD functions | The LAPD functions as specified in ETS 300 125 are applicable. However, the exceptions and modifications specified in the remainder of the present document shall be used. |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 6.1 Exceptions and modifications | In the following headlines from ETS 300 125 are kept and references are made to the corresponding subclause of ETS 300 125. |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 6.1.2 Command/Response field bit (C/R) | (Refer to ETS 300 125, part 2, subclause 3.3.2) In GSM PLMN's BSC represents the network side and TRX/BCF the user side of the interface. |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 6.1.3 Service Access Point Identifier (SAPI) | (Refer to ETS 300 125, part 2, subclause 3.3.3) The SAPI values for the A-bis interface are as listed in table 1. ETSI ETSI TS 100 595 V7.0.0 (1999-08) 9 (GSM 08.56 version 7.0.0 Release 1998) Table 1: Allocation of SAPI values and priority classes _______________________________________________________________________... |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 6.1.4 TEI for point-to-point data link connection | (Refer to ETS 300 125, part 2, subclause 3.3.4.2) The remaining Terminal Endpoint Identifier (TEI) values are used for the point-to-point data link connections associated with the addressed Service Access Point (SAP). The range of TEI values shall be allocated as shown in table 2. Table 2: Allocation of TEI values ____... |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 6.1.5 Commands and responses | (Refer to ETS 300 125, part 2, subclause 3.6.1) The XID command and response are not used. |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 6.1.6 Exchange identification (XID) command/response | (Refer to ETS 300 125, part 2, subclause 3.6.12) This functionality is not used. |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 6.1.7 MDL-XID | (Refer to ETS 300 125, part 2, subclause 4.1.1.9) This functionality is not used. |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 6.1.8 PH-DATA, PH DEACTIVATE and PH-ACTIVATE | (Refer to ETS 300 125, part 2, subclauses 4.1.1.10 - 4.1.1.12) This functionality is not relevant. ETSI ETSI TS 100 595 V7.0.0 (1999-08) 10 (GSM 08.56 version 7.0.0 Release 1998) |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 6.1.9 MPH-ACTIVATE, MPH-DEACTIVATE an MPH-INFORMATION | (Refer to ETS 300 125, part 2, subclauses 4.1.1.13 - 4.1.1.15) This functionality is not relevant. |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 6.1.10 Priority indicator | (Refer to ETS 300 125, part 2, subclause 4.1.3.1) The different SAPIs are given the priority classes as listed in table 1 when contending (with priority one as the highest). |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 6.1.11 Terminal Endpoint Identifier (TEI) management procedures | (Refer to ETS 300 125, part 2, subclause 5.3) Due to the special assignment functions needed on the A-bis interface there are modifications and additions to the assignment procedures. The rest of subclause 5.3 in ETS 300 125, part 2, is kept if not stated otherwise. |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 6.1.11.1 General | (Refer to ETS 300 125, part 2, subclause 5.3.1) TEI management for A-bis interface is based on the following procedural means: - a Subset of the TEI assignment procedures; - the TEI check procedures; - the TEI remove procedures; - an additional TEI assignment procedure. The TEI management needs procedures to check the ... |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 6.1.11.2 TEI assignment procedure | (Refer to ETS 300 125, part 2, subclause 5.3.2) The TEI assignment procedure used on the A-bis interface has some additions to the automatic TEI assignment procedure specified in ETS 300 125, part 2. To facilitate the configuration control in the BSC each TRX will have a fixed TEI and possibly get access to one or more... |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 6.1.11.3 TEI identity verify procedure | (Refer to ETS 300 125, part 2, subclause 5.3.5) This procedure is not used. |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 6.1.11.4 Formats and codes. | (Refer to ETS 300 125, part 2, subclause 5.3.6) All messages except Identity verify and Identity denied are used. The Ai is used as described in subclause 6.1.11.2, the modification to ETS 300 125, part 2, subclause 5.3.2. The Ri parameter is not used and will always be coded 0000 0000. The coding of each field of the ... |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 6.1.12 Automatic negotiation of data link layer parameters | (Refer to ETS 300 125, part 2, subclause 5.4 and annex IV) The procedures are not supported. |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 6.1.13 Establishment procedures | (Refer to ETS 300 125, part 2, subclause 5.5.1.2) The timer T203 shall be implemented in the equipment on both sides of interface A-bis. |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 6.1.14 N(S) sequence error | (Refer to ETS 300 125, part 2, subclause 5.8.1 and appendix I) As it is the case in ETS 300 125, the optional procedure for retransmission as described in Appendix I is not supported. ETSI ETSI TS 100 595 V7.0.0 (1999-08) 13 (GSM 08.56 version 7.0.0 Release 1998) |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 6.1.15 List of system parameters | (Refer to ETS 300 125, part 2, subclause 5.9) All the default values are given in the following subclauses. |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 6.1.15.1 Timer T200 | (Refer to ETS 300 125, part 2, subclause 5.9.1) The default value of timer T200 is 240 ms starting from the end of a transmitted frame. NOTE: This timer depends on the timer values used for supervising the message flow between the Mobile Station (MS) and the network. The proper operation of the procedure requires timer... |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 6.1.15.2 Maximum number of retransmissions (N200) | (Refer to ETS 300 125, part 2, subclause 5.9.2) The default value of (N200) is 3. |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 6.1.15.3 Maximum number of octets in an information field (N201) | (Refer to ETS 300 125, part 2, subclause 5.9.3) The default and maximum value of (N201) is 260 octets for all SAPI values. 6.1.15.4 Maximum number of transmission of the TEI identity request message (N202) (Refer to ETS 300 125, part 2, subclause 5.9.4) Not used (i.e. equivalent to infinity). |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 6.1.15.5 Maximum number of outstanding frames (K) | (Refer to ETS 300 125, part 2, subclause 5.9.5) For the SAPI value 0 identifying radio signalling the default (K) value shall be 2. For all other SAPIs the value shall be set to the fixed value of 1. NOTE: The value of K for SAPI value 0 shall always be greater than the k value for the other SAPIs. |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 6.1.15.6 Timer T201 | (Refer to ETS 300 125, part 2, subclause 5.9.6) Timer T201 shall have the default value 1 second. |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 6.1.15.7 Timer T202 | (Refer to ETS 300 125, part 2, subclause 5.9.7) The minimum time between the transmission of TEI Identity request messages is a system parameter (T202) which shall be set to 15 seconds. |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 6.1.15.8 Timer T203 | (Refer to ETS 300 125, part 2, subclause 5.9.8) The timer T203 represents the maximum time allowed without frames being exchanged for each TEI. The value of timer T203 shall be 10 seconds. ETSI ETSI TS 100 595 V7.0.0 (1999-08) 14 (GSM 08.56 version 7.0.0 Release 1998) |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 6.1.16 Data link layer monitor function | (Refer to ETS 300 125, part 2, subclause 5.10) The supervisory function will be used in the equipment on both sides of the A-bis interface. |
10b5e06b1903c8b93c1db34a5ea49830 | 100 595 | 6.1.17 Miscellaneous | (Refer to ETS 300 125, part 2, appendix I-IV) The functionalities specified in appendix I-IV of ETS 300 125, part 2, is not used. ETSI ETSI TS 100 595 V7.0.0 (1999-08) 15 (GSM 08.56 version 7.0.0 Release 1998) Annex A (informative): Change Request History Change history SMG No. TDoc. No. CR. No. Section affected New ve... |
858051528d06433dfa320aa65f167603 | 100 593 | 1 Introduction | |
858051528d06433dfa320aa65f167603 | 100 593 | 1.1 Scope | The use and general aspects of the A-bis interface are given in Technical Specification GSM 08.51. The present document gives the principle basis for the rest of the specifications specifying the interface between the Base Station Controller, BSC, and the Base Transceiver Station, BTS, with its transceivers, TRX. These... |
858051528d06433dfa320aa65f167603 | 100 593 | 1.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. • Fo... |
858051528d06433dfa320aa65f167603 | 100 593 | 2 Definitions and abbreviations | Abbreviations used in the present document are listed in GSM 01.04. |
858051528d06433dfa320aa65f167603 | 100 593 | 2.1 Base Station System, BSS | The system of base station equipment (transceivers, controllers, etc..) which is viewed by the MSC through a single interface as defined by the GSM 08 0x series of recommendations, as being the entity responsible for communicating with Mobile Stations in a certain area. The radio equipment of a BSS may cover one or mor... |
858051528d06433dfa320aa65f167603 | 100 593 | 2.2 Base Station Controller, BSC | A network component in the PLMN with the functions for control of one or more Base Transceiver Stations (BTSs). |
858051528d06433dfa320aa65f167603 | 100 593 | 2.3 Base Transceiver Station, BTS | A network component which serves one cell, and is controlled by a Base Station Controller. The BTS can consist of one or more TRXs with or without common control equipment. |
858051528d06433dfa320aa65f167603 | 100 593 | 2.4 Cell | See GSM 03.02. |
858051528d06433dfa320aa65f167603 | 100 593 | 2.5 Transceiver, TRX | The Transceiver, TRX, in the GSM PLMN is the functional entity which supports the 8 basic radio channels of the same TDMA-frame. |
858051528d06433dfa320aa65f167603 | 100 593 | 2.6 Base Control Function, BCF | A functional entity which handles common control functions within a BTS, e.g. frequency hopping sequences etc. At a multi BTS site, one of the BCFs can also be choosen to perform functions common to the site (e.g. external alarms, power supply, time base). ETSI ETSI TS 100 593 V7.0.0 (1999-08) 7 (GSM 08.52 version 7.0.... |
858051528d06433dfa320aa65f167603 | 100 593 | 3 General | Technical Specifications GSM 08.01 - 08.20 specify the functional split and interface between MSC and the Base Station System, BSS, the A- interface. The BSS can be further subdivided into one BSC controlling one or more BTSs, each consisting of one or more TRXs. The interface treated by the present document is the int... |
858051528d06433dfa320aa65f167603 | 100 593 | 4 Functional division between BSC and BTS | |
858051528d06433dfa320aa65f167603 | 100 593 | 4.1 General | In Technical Specification GSM 08.02 the functional division between MSC and BSS is described. This section describes the further subdivision of functions between BSC and BTS/TRX required for the A-bis interface. A summary can be found in table 4.1. Some general requirements on the functionality of the A-bis interface ... |
858051528d06433dfa320aa65f167603 | 100 593 | 4.2 Terrestrial channel management | There is a unique mapping from traffic channels on the radio path to the terrestrial traffic channels. BSC makes the choice of radio channel and thereby also of the terrestrial channel for a call. |
858051528d06433dfa320aa65f167603 | 100 593 | 4.3 Radio channel management | |
858051528d06433dfa320aa65f167603 | 100 593 | 4.3.1 Channel configuration management | The channel configuration is controlled between the BSC and OMC. Current configuration is downloaded from OMC to BSC which then controls the use of the radio channels (TDMA time slots for BCCH/CCCH, TCHs, SDCCHs etc). |
858051528d06433dfa320aa65f167603 | 100 593 | 4.3.2 SDCCH (Stand alone DCCH) and TCH management | |
858051528d06433dfa320aa65f167603 | 100 593 | 4.3.2.1 Frequency hopping management | The hopping sequences for each BTS (cell) is downloaded from OMC to BSC. It is then the responsibility of BSC to download this information to each BTS and also to send the corresponding BCCH information to be transmitted in the BCCH time slots. |
858051528d06433dfa320aa65f167603 | 100 593 | 4.3.2.2 Channel selection, link supervision and channel release | These functions are controlled by BSC. For channel selection BSC has to have information on blocked radio channels and also on interference level on idle channels. In the assignment messages to MS (Immediate Assign, Assign Command and Handover Command), a Starting Time parameter is included. This starting time is based... |
858051528d06433dfa320aa65f167603 | 100 593 | 4.3.2.3 Power control | The ordered MS power level is sent in the 16 bit L1-header of SACCH- blocks on the downlink and the actual power level used by MS is reported in the corresponding L1-header on the uplink. This header is inserted (downlink) and extracted (uplink) by BTS/TRX. The determination of required power level in MS is based on up... |
858051528d06433dfa320aa65f167603 | 100 593 | 4.3.2.4 Idle channel observation | Idle channels are monitored by BTS. |
858051528d06433dfa320aa65f167603 | 100 593 | 4.3.3 BCCH/CCCH management | TRX knows the timing of BCCH/CCCH slots (not known by BSC). The actual timing of BCCH/CCCH blocks therefore has to be made by BTS/TRX, including the scheduling of Paging Request messages on paging sub- channels. BCCH information is downloaded to BTS. |
858051528d06433dfa320aa65f167603 | 100 593 | 4.3.4 Random access | Detection of a random access attempt has to be made by TRX which then sends a message to BSC containing the required timing advance, the frame number of the access attempt and the 8 bit Channel Request message sent by MS in the access burst. This information is then included by BSC in the following Immediate Assign mes... |
858051528d06433dfa320aa65f167603 | 100 593 | 4.3.5 Channel coding/decoding | The error protection coding and decoding is made by BTS/TRX. Different coding and interleaving schemes are used for speech and data calls. This information has to be signalled from BSC to BTS on a per call basis. |
858051528d06433dfa320aa65f167603 | 100 593 | 4.3.6 Transcoding/rate adaption | The A-bis interface has to allow for the transcoder/rate adaptor being positioned either inside or outside BTS. |
858051528d06433dfa320aa65f167603 | 100 593 | 4.3.7 Timing advance | Timing advance has to be determined by TRX. When MS is on a dedicated channel (SDCCH, TCH), the required timing advance (TA) is sent to MS and the actual timing advance is reported by MS in the 16 bit L1-header of the SACCH blocks. At handover access, TA is determined by TRX and reported to MS in the PHYsical INFOrmati... |
858051528d06433dfa320aa65f167603 | 100 593 | 4.3.8 Radio resource indication | BTS reports on status (interference level, blocking etc.) of idle channels to BSC on a regular basis. |
858051528d06433dfa320aa65f167603 | 100 593 | 4.3.9 Measurements | MS measures the downlink received level and quality from the serving cell and the received level from surrounding cells. The results from these measurements are reported by MS in Measurement Report messages on SACCH. Uplink received level and quality are measured by BTS/TRX. The parameters for the uplink measurements a... |
858051528d06433dfa320aa65f167603 | 100 593 | 4.3.10 LAPDm functions (Layer 2) | Layer 2 on the radio interface (LAPDm) is terminated at BTS/TRX. Between BTS and BSC, LAPD is used. |
858051528d06433dfa320aa65f167603 | 100 593 | 4.3.11 Paging | Paging is initiated by MSC via BSC. BSC determines the paging group to be used based on IMSI of the MS to be paged. The paging group value is sent to BTS together with the TMSI or IMSI. Based on the paging group information, BTS/TRX will build the relevant PAGING REQUEST message and execute the transmission of the mess... |
858051528d06433dfa320aa65f167603 | 100 593 | 4.3.12 Handover | No handover recognition or decision is made by BTS. However, BTS/TRX has to detect the handover access made by a handed over MS. BTS/TRX also checks the Handover Reference value sent by MS in the handover access burst against the Handover Reference value received from BSC in the channel activation command. In case of a... |
858051528d06433dfa320aa65f167603 | 100 593 | 4.3.13 Encryption | Encryption and decryption is made of the complete outgoing bit stream (except for preambles/synch words). This therefore has to be made by TRX. The encryption key has to be downloaded to BTS/TRX before encryption starts. Special control messages are therefore required between BSC and BTS/TRX. |
858051528d06433dfa320aa65f167603 | 100 593 | 4.3.14 Mobility management and call control | All mobility management and call control functions recide in MSC. ETSI ETSI TS 100 593 V7.0.0 (1999-08) 11 (GSM 08.52 version 7.0.0 Release 1998) TABLE 4.1: Summary of functional division between BTS and BSC/MSC FUNCTION LOCATION BTS BSC/MSC TERRESTRIAL CHANNEL MANAGEMENT MSC-BSC channels Channel allocation............... |
858051528d06433dfa320aa65f167603 | 100 593 | 5 Transcoding/rate adaption and multiplexing | The interface supports two options: transcoding/rate adaption performed in BTS or outside BTS. |
858051528d06433dfa320aa65f167603 | 100 593 | 5.1 Transcoding/rate adaption in BTS | The transcoding of speech to normal 64 kbit/s A-law is performed within BTS. Data may be rate adapted or submultiplexed to 64 kbit/s circuits. ETSI ETSI TS 100 593 V7.0.0 (1999-08) 13 (GSM 08.52 version 7.0.0 Release 1998) |
858051528d06433dfa320aa65f167603 | 100 593 | 5.2 Transcoding/rate adaption outside BTS | In this case the transcoder/rate adaptor is considered as part of the BSC. The channel coding/decoding is performed by BTS/TRX. The choice of coding/interleaving has to be signalled from BSC to BTS. The remote speech transcoder has to have knowledge of some radio parameters for an efficient decoding. In addition, the t... |
858051528d06433dfa320aa65f167603 | 100 593 | 6 Interface structures | |
858051528d06433dfa320aa65f167603 | 100 593 | 6.1 Communication channels | The A-bis interface is considered to have two types of communication channels (see figure 6.1): - traffic channel (SDC) at 8, 16 or 64 kbit/s carrying speech or data of one radio traffic channel (Bm or Lm channel), - signalling channels (SCH) at 16, 32 or 64 kbit/s, carrying signalling information (both BSC-MS and BSC-... |
858051528d06433dfa320aa65f167603 | 100 593 | 6.2 Signalling links | The addressing of TRXs and BCF is made using separate TEIs for each TRX and BCF. Three logical links are defined for each TEI: RSL: Radio Signalling Link used for supporting traffic management procedures (MS to network communication). One link per TRX. OML: Operations and Maintenance Link used for supporting network ma... |
858051528d06433dfa320aa65f167603 | 100 593 | 6.3 Signalling model | A signalling model for the A-bis interface and its signalling environment can be found in figure 6.3. CM and MM messages are not interpreted by BSC or BTS. Over the A interface they are tranferred using DTAP (Direct Transfer Application Part) and over the A-bis interface they are transferred as transparent messages. RR... |
52a095daef2821950f03b36be5124217 | 100 592 | 1 General | |
52a095daef2821950f03b36be5124217 | 100 592 | 1.1 Scope | The present document is an introduction to the 08.5X - 08.6X series of GSM Technical Specifications and deals with the definition of the base station controller (BSC) to base transceiver station (BTS) interface defined inside the base station system (BSS) for the GSM system. These Technical Specifications define the ba... |
52a095daef2821950f03b36be5124217 | 100 592 | 1.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. • Fo... |
52a095daef2821950f03b36be5124217 | 100 592 | 1.3 Definitions and abbreviations | Abbreviations used in the present document are listed in GSM 01.04. |
52a095daef2821950f03b36be5124217 | 100 592 | 2 Interface capabilities | The BSC-BTS interface shall be capable of supporting all the services offered to the GSM users and subscribers. In addition it shall also allow control of the radio equipment and radio frequency allocation in the BTS. |
52a095daef2821950f03b36be5124217 | 100 592 | 3 Interface specification objectives | The BSC to BTS interface specifications should allow the following: (I) Connection of various manufacturers BTS/TRX to the same BSC, according to the location of the transcoder. (II) The use of several manufacturers BSC to the same type of BTS/TRX, according to the location of the transcoder. (III) The use of the same ... |
52a095daef2821950f03b36be5124217 | 100 592 | 4 Interface characteristics | The interface is defined to be at the terrestrial link of a remote BTS connected to the BSC. The BSC to BTS interface is specified by a set of characteristics, including: a) physical and electrical parameters; b) channel structures; c) signalling transfer procedures; d) configuration and control procedures; e) operatio... |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 1 Scope | ....................................................................................................................................................... 6 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 2 References, abbreviations and definitions | ............................................................................................... 6 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 2.1 References | ................................................................................................................................................................6 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 2.2 Abbreviations | ...........................................................................................................................................................7 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 2.3 Definitions | ................................................................................................................................................................7 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 3 General approach | ..................................................................................................................................... 7 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 4 The RA0 Function | ................................................................................................................................... 7 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 5 The RA1 Function | ................................................................................................................................... 7 6 The RA1’’ Function ................................................................................................................................ 8 7 Split/Combine and Padding Functi... |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 7.2 Substream numbering | ...............................................................................................................................................8 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 7.3 Initial Substream Synchronisation for Transparent Servic | es ...................................................................................8 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 7.4 Frame Synchronisation and Action on loss of Synchronisa | tion..............................................................................8 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 7.5 Network Independent Clocking | ...............................................................................................................................8 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 7.6 Padding | .....................................................................................................................................................................8 8 The RA1/RA1' Function.......................................................................................................................... 8 8.1 R... |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 8.4 Synchronisation | ........................................................................................................................................................9 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 8.5 Idle frames | ................................................................................................................................................................9 9 THE RA1'/RAA' FUNCTION................................................................................................................. 9 9.1 Radio Interfac... |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 9.2 Synchronisation | ......................................................................................................................................................10 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 9.3 Idle frames | ..............................................................................................................................................................10 |
1352d9d2d97b335ddb6d861824150a6f | 100 591 | 10 THE RAA' FUNCTION | ........................................................................................................................ 10 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.