hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
88a8e2c2930b947aed767e9a70370cfe | 101 476 | 6.6 Handler availability | The system handlers : ProactiveHandler, ProactiveResponseHandler, EnvelopeHandler and EnvelopeResponseHandler are Temporary JCRE Entry Point Object as defined in the Java Card Runtime Environment Specification [8]. The following table describes the minimum availability of the handlers for all the events at the invocati... |
88a8e2c2930b947aed767e9a70370cfe | 101 476 | 6.7 SIM Toolkit Framework behaviour | The following rules define the SIM Toolkit Framework behaviour for : - Triggering of a toolkit applet (invocation of the processToolkit() method from the ToolkitInterface shareable interface) : - The current context is switched to the toolkit applet . - A pending transaction is aborted. - There is no invocation of the ... |
88a8e2c2930b947aed767e9a70370cfe | 101 476 | 6.8 Usage of ViewHandler and EditHandler | The ViewHandler and EditHandler classes have been defined to group the properties of the system handler, and may be used in the future to provide a simple mechanism to the toolkit applet to handle TLV lists. ETSI ETSI TS 101 476 V7.1.0 (2000-05) 17 (GSM 03.19 version 7.1.0 Release 1998) |
88a8e2c2930b947aed767e9a70370cfe | 101 476 | 7 SIM toolkit applet | |
88a8e2c2930b947aed767e9a70370cfe | 101 476 | 7.1 Applet Loading | The SIM API card shall be compliant to the Java Card 2.1 VM Architecture Specification [9] and to the Annex B to guarantee interoperability at byte code Level. The applet loading mechanism, protocol and applet life cycle are defined in GSM 03.48 [4] |
88a8e2c2930b947aed767e9a70370cfe | 101 476 | 7.2 Object Sharing | The sharing mechanism defined in Java Card 2.1 API Specification [7] and Java Card 2.1 Runtime Environment Specification [8] shall be used by the applet to share data. ETSI ETSI TS 101 476 V7.1.0 (2000-05) 18 (GSM 03.19 version 7.1.0 Release 1998) Annex A (normative): Java Card SIM API The attached file "0319_710_Annex... |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 1 Scope | This Technical Specification defines: a) an identification plan for mobile subscribers in the GSM system; b) principles of assigning telephone and ISDN numbers to MSs in the country of registration of the MS; c) principles of assigning Mobile Station (MS) roaming numbers to visiting MSs; d) an identification plan for l... |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 1.1 Normative references | References may be made to: a) specific versions of publications (identified by date of publication, edition number, version number, etc.), in which case, subsequent revisions to the referenced document do not apply; or b) all versions up to and including the identified version (identified by "up to and including" befor... |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 1.2 Abbreviations | Abbreviations used in this TS are listed in GSM 01.04. |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 1.3 General comments to references | The identification plan for mobile subscribers defined below is that defined in CCITT Recommendation E.212. The ISDN numbering plan for MSs and the allocation of mobile station roaming numbers is that defined in CCITT Recommendation E.213. Only one of the principles for allocating ISDN numbers is proposed for GSM PLMNs... |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 1.4 Conventions on bitordering | The following conventions hold for the coding of the different identities appearing in this Technical Specification and in other GSM Technical Specifications if not indicated otherwise: - the different parts of an identity are shown in the figures in order of significance; - the most significant part of an identity is ... |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 2 Identification of mobile subscribers | |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 2.1 General | A unique International Mobile Subscriber Identity (IMSI) shall be allocated to each mobile subscriber in the GSM system. NOTE: This IMSI is the concept referred to by CCITT as "International Mobile Station Identity". ETSI TS 100 927 V6.1.0 (1998-07) 8 GSM 03.03 version 6.1.0 Release 1997 In order to support the subscri... |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 2.2 Composition of IMSI | IMSI is composed as shown in figure 1. M C C Not m ore than 15 digits 3 digits 2 digits M NC M SIN NM SI IM SI Figure 1: Structure of IMSI IMSI is composed of three parts: i) Mobile Country Code (MCC) consisting of three digits. The MCC identifies uniquely the country of domicile of the mobile subscriber; ii) Mobile Ne... |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 2.3 Allocation principles | IMSI shall consist of numerical characters (O through 9) only. The overall number of digits in IMSI shall not exceed 15 digits. The allocation of Mobile Country Codes (MCCs) is administered by the CCITT and is given in annex A to CCITT Blue Book Recommendation E.212. The allocation of National Mobile Subscriber Identit... |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 2.4 Structure of TMSI | Since the TMSI has only local significance (i.e. within a VLR and the area controlled by a VLR, or within an SGSN and the area controlled by an SGSN), the structure and coding of it can be chosen by agreement between operator and manufacturer in order to meet local needs. The TMSI consists of 4 octets. It can be coded ... |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 2.5 Structure of LMSI | The LMSI consists of 4 octets and may be allocated by the VLR. |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 2.6 Structure of TLLI | A TLLI is built by the MS or by the SGSN either on the basis of the P-TMSI (local or foreign TLLI), or directly (random or auxiliary TLLI), according to the following rules. The TLLI consists of 32 bits, numbered from 0 to 31 by order of significance, with bit 0 being the LSB. A local TLLI is built by a MS which has a ... |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 3 Numbering plan for mobile stations | |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 3.1 General | Below the structure of the numbers used by a subscriber of a fixed (or mobile) network for calling a mobile station of a GSM PLMN is defined. The network addresses used for packet data communication between a mobile station and a fixed (or mobile) station are also defined below. Also the structure of mobile station roa... |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 3.2 Numbering plan requirements | In principle, it should be possible for any subscriber of the ISDN or PSTN to call any MS in a GSM PLMN. This implies that ISDN numbers for MSs should comply with the ISDN numbering plan in each country. The ISDN numbers of MSs should be composed in such a way that standard ISDN/PSTN charging can be used for calls to M... |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 3.5 Structure of Mobile Station International Data Number | The structure of MS international data numbers should comply with the data numbering plan of CCITT Recommendation X.121 as applied in the home country of the mobile subscriber. Implications on numbering interworking functions which may need to be provided by the PLMN (if the use of X.121 numbers is required) are indica... |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 3.6 Handover Number | The handover number is used for establishment of a circuit between MSCs to be used for a call being handed over. The handover number may be reused in the same way as the MSRN. |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 3.7 Structure of an IP v4 address | One or more IP address domains could be allocated to each PLMN. The IP v4 address structure is defined in RFC 791. An IP v4 address may be allocated to an MS either permanently or on a temporary basis during a connection with the network. |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 3.8 Structure of an IP v6 address | One or more IP address domains could be allocated to each PLMN. The IP v6 address structure is defined in RFC 1883. |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 4 Identification of location areas and base stations | |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 4.1 Composition of the Location Area Identification (LAI) | The Location Area Identification shall be composed as shown in figure 3: Location Area Identification M CC M NC LAC Figure 3: Structure of Location Area Identification The LAI is composed of the following elements: - Mobile Country Code (MCC) identifies the country in which the GSM PLMN is located. The value of the MCC... |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 4.2 Composition of the Routing Area Identification (RAI) | The Routing Area Identification shall be composed as shown in figure 4: ¸¶¶¶¶¶¶¶¹ ¸¶¶¶¶¶¶¶¶¹ · /$, · · 5$& · º¶¶¶¶¶¶¶» º¶¶¶¶¶¶¶¶» ¶5RXWLQJ $UHD ,GHQWLILFDWLRQ¶! Figure 4: Structure of Routing Area Identification The RAI is composed of the following elements: - A valid Location Area Identity (LAI) as defined in section ... |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 4.3 Base station identification | |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 4.3.1 Cell Identity (CI) and Cell Global Identification (CGI) | The BSS and cell within the BSS is identified within a location or routing area by adding a Cell Identity (CI) to the location or routing area identification, as shown in figure 5. The CI is of fixed length with 2 octets and it can be coded using a full hexadecimal representation. The Cell Global Identification is the ... |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 4.3.2 Base Station Identify Code (BSIC) | The base station identity code is a local colour code that allows a MS to distinguish between different neighbouring base stations. BSIC is a 6 bit length code which is structured in the following way. ETSI TS 100 927 V6.1.0 (1998-07) 14 GSM 03.03 version 6.1.0 Release 1997 NCC BCC PLM N colour code BS colour code 3 bi... |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 4.4 Regional Subscription Zone Identity (RSZI) | A PLMN specific regional subscription defines unambiguously for the entire PLMN the regions in which roaming is allowed. It consists of one or more regional subscription zones. The regional subscription zone is identified by Regional Subscription Zone Identity (RSZI). A regional subscription zone identity is composed a... |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 4.5 Location Number | A location number is a number which defines a specific location within a GSM PLMN. The Location number is formatted according to CCITT Recommendation E.164, as shown in figure 7. The country code (CC) and national destination code (NDC) fields of the location number are those which define the GSM PLMN of which the loca... |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 5 Identification of MSCs and location registers | |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 5.1 Identification for routing purpose | MSCs, GSNs and location registers are identified by international PSTN/ISDN numbers and/or Signalling Point Codes ("entity number", i.e., "HLR number", "VLR number", "MSC number", “SGSN number” and “GGSN number”) in each GSM PLMN. Additionally SGSN, GGSN are identified by GSN Addresses. These are the SGSN Address and t... |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 5.2 Identification of HLR for HLR restoration application | HLR may also be identified by one or several "HLR id(s)", consisting of the leading digits of the IMSI (MCC + MNC + leading digits of MSIN). 6 International Mobile Station Equipment Identity and Software Version Number |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 6.1 General | Below the structure and allocation principles of the International Mobile station Equipment Identity and Software Version Number (IMEISV) and the International Mobile station Equipment Identity (IMEI) are defined. The Mobile Station Equipment is uniquely defined by the IMEI or the IMEISV. |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 6.2 Composition of IMEI and IMEISV | |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 6.2.1 Composition of IMEI | The International Mobile station Equipment Identity (IMEI) is composed as shown in figure 8. FAC TAC 1 digit SNR spare IM EI 15 digits 6 digits 2 digits 6 digits Figure 8: Structure of IMEI The IMEI is composed of the following elements (each element shall consist of decimal digits only): - Type Approval Code (TAC). It... |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 6.2.2 Composition of IMEISV | The International Mobile station Equipment Identity and Software Version Number (IMEISV) is composed as shown in figure 9. ETSI TS 100 927 V6.1.0 (1998-07) 17 GSM 03.03 version 6.1.0 Release 1997 FAC TAC 2 digits SNR SVN IM EISV 16 digits 6 digits 2 digits 6 digits Figure 9: Structure of IMEISV The IMEISV is composed o... |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 6.3 Allocation principles | The Type Approval Code (TAC) is issued by a central body. The place of final assembly (FAC) is encoded by the manufacturer. Manufacturers shall allocate individual serial numbers (SNR) in a sequential order. For a given ME, the combination of TAC, FAC and SNR used in the IMEI shall duplicate the combination of TAC, FAC... |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 7.1 Group Identities | Logical groups of subscribers to the Voice Group Call Service or to the Voice Broadcast Service are known by a Group Identity (Group ID). Group IDs for VGCS are unique within a PLMN. Likewise, Group IDs for VBS are unique within a PLMN. However, no uniqueness is required between the sets of Group IDs. These sets may be... |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 7.2 Group Call Area Identification | Groupings of cells into specific group call areas occurs in support of both the Voice Group Call Service and the Voice Broadcast Service. These service areas are known by a "Group Call Area Identity" (Group Call Area Id). No restrictions are placed on what cells may be grouped into a given group call area. The Group Ca... |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 7.3 Voice Group Call and Voice Broadcast Call References | Specific instances of voice group calls (VGCS) and voice broadcast calls (VBS) within a given group call area are known by a "Voice Group Call Reference" or by a "Voice Broadcast Call Reference". Each voice group call or voice broadcast call in one network is uniquely identified by its Voice Group Call Reference or Voi... |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 8 SCCP subsystem numbers | Subsystem numbers are used to identify applications within network entities which use SCCP signalling. In GSM, subsystem numbers may be used between PLMNs, in which case they are taken from the globally standardised range (1 - 31), or within a PLMN, in which case they are taken from the national network range (32 - 254... |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 8.1 Globally standardised subsystem numbers used for GSM | The following globally standardised subsystem numbers have been allocated for use by GSM: 0000 0101 CAP 0000 0110 HLR (MAP); 0000 0111 VLR (MAP); 0000 1000 MSC (MAP); 0000 1001 EIR (MAP); 0000 1010 is allocated for evolution (possible Authentication centre). ETSI TS 100 927 V6.1.0 (1998-07) 19 GSM 03.03 version 6.1.0 R... |
dcb0ce02fe83da0ae2b6e3674c7d31ed | 100 927 | 8.2 National network subsystem numbers used for GSM | The following national network subsystem numbers have been allocated for use by GSM: 1111 1101 BSS O&M (A interface); 1111 1110 BSSAP (A interface). ETSI TS 100 927 V6.1.0 (1998-07) 20 GSM 03.03 version 6.1.0 Release 1997 Annex A (informative): Colour Codes A.1 Utilization of the BSIC To each cell is allocated a BSIC, ... |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 1 Scope | ........................................................................................................................................................6 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 2 References | ................................................................................................................................................6 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 3 Abbreviations | ...........................................................................................................................................6 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 4 Synchronisation procedures | .....................................................................................................................7 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 4.1 Cell search | ......................................................................................................................................................... 7 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 4.2 Common physical channel synchronisation | ....................................................................................................... 7 4.3 DPCCH/DPDCH synchronisation ..................................................................................................................... 7 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 4.3.1 General | ......................................................................................................................................................... 7 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 4.3.2 No existing uplink dedicated channel | ........................................................................................................... 7 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 4.3.3 With existing uplink dedicated channel | ....................................................................................................... 8 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 4.3.4 Transmission timing adjustments | ................................................................................................................. 9 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5 Power control | ...........................................................................................................................................9 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.1 Uplink power control | ......................................................................................................................................... 9 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.1.1 PRACH | ........................................................................................................................................................ 9 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.1.1.1 General | ................................................................................................................................................... 9 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.1.1.2 Setting of PRACH control and data part power difference | .................................................................... 9 5.1.2 DPCCH/DPDCH........................................................................................................................................ 10 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.1.2.1 General | ................................................................................................................................................. 10 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.1.2.2 Ordinary transmit power control | .......................................................................................................... 10 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.1.2.2.1 General | ............................................................................................................................................ 10 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.1.2.2.2 Algorithm 1 for processing TPC commands | ................................................................................... 11 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.1.2.2.3 Algorithm 2 for processing TPC commands | ................................................................................... 11 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.1.2.3 Transmit power control in compressed mode | ....................................................................................... 13 5.1.2.4 Transmit power control in DPCCH power control preamble ............................................................... 14 5.1.2.5 Setting of the uplink DPCCH/DPDCH power difference............................................ |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.1.2.5.1 General | ............................................................................................................................................ 14 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.1.2.5.2 Signalled gain factors | ...................................................................................................................... 14 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.1.2.5.3 Computed gain factors | .................................................................................................................... 15 5.1.2.5.4 Setting of the uplink DPCCH/DPDCH power difference in compressed mode ............................. 15 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.1.3 PCPCH | ....................................................................................................................................................... 16 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.1.3.1 Power control in the message part | ........................................................................................................ 16 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.1.3.2 Power control in the power control preamble | ....................................................................................... 16 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.2 Downlink power control | .................................................................................................................................. 16 5.2.1 DPCCH/DPDCH........................................................................................................................................ 17 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.2.1.1 General | ................................................................................................................................................. 17 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.2.1.2 Ordinary transmit power control | .......................................................................................................... 17 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.2.1.2.1 General | ............................................................................................................................................ 17 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.2.1.2.2 Adjustment loop | .............................................................................................................................. 17 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.2.1.3 Power control in compressed mode | ...................................................................................................... 18 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.2.1.4 Site selection diversity transmit power control | ..................................................................................... 18 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.2.1.4.1 General | ............................................................................................................................................ 18 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.2.1.4.2 TPC procedure in UE | ...................................................................................................................... 19 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.2.1.4.3 Selection of primary cell | ................................................................................................................. 19 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.2.1.4.4 Delivery of primary cell ID | ............................................................................................................. 19 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.2.1.4.5 TPC procedure in the network | ........................................................................................................ 20 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.2.2 Power Control with DSCH | ......................................................................................................................... 20 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.2.3 AICH | .......................................................................................................................................................... 20 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 5.2.4 PICH | .......................................................................................................................................................... 20 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 6 Random access procedure | ......................................................................................................................21 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 6.1 Physical random access procedure | ................................................................................................................... 21 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 6.1.1 RACH sub-channels | ................................................................................................................................... 22 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 6.2 CPCH Access Procedures | ................................................................................................................................ 22 ETSI TS 125 214 V3.1.1 (2000-01) (3G TS 25.214 version 3.1.1 Release 1999) ETSI 3GPP 3G TS 25.214 V3.1.1 (1999-12) 4 3G TS 25.214 version 3.1.0 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 7 Procedures in Packet Data Transfer | .......................................................................................................24 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 8 Closed loop mode transmit diversity | .....................................................................................................25 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 8.1 Determination of feedback information | ........................................................................................................... 26 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 8.2 Closed loop mode 1 | ......................................................................................................................................... 26 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 8.2.1 Mode 1 end of frame adjustment | ................................................................................................................ 28 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 8.2.2 Mode 1 normal initialization | ...................................................................................................................... 28 |
269c47dfa5d8af078e5fbd4ffc10e989 | 125 214 | 8.2.3 Mode 1 operation during compressed mode | .............................................................................................. 28 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.