hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.9 Layer 3 Header Information | This element is used to supply the BSS with information that needs to be included in the header of layer 3 messages over the radio interface. ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 ... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.10 Encryption Information | This element contains the user data encryption information used to control any encryption equipment at the BSS. It is a variable length element. It is coded as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ E... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.11 Channel Type | This element contains all of the information that the BSS requires to determine the required radio resource(s). The channel type information element has a minimum length of 5 octets and a maximum length of 10 octets. It is coded as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 ... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.12 Periodicity | This element defines the periodicity of a particular procedure. It is fixed length, 2 octets. The coding is as follows: ETSI ETSI TS 100 590 V6.5.0 (2000-06) 87 (GSM 08.08 version 6.5.0 Release 1997) ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴────... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.13 Extended Resource Indicator | This element defines which additional resource information related to a given cell the BSS shall transfer to the MSC. It may also indicate the subsequent reporting mode for that cell. The coding is as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.14 Total Resource Accessible | This element gives the total number of full and half rate channels accessible on any given cell at the time of construction of the message. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 88 (GSM 08.08 version 6.5.0 Release 1997) It defines these parameters in terms of the number of channels which are accessible or in use. No se... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.15 [spare] | |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.16 [spare] | |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.17 Cell Identifier | This element uniquely identifies a cell within a BSS and is of variable length containing the following fields: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────────... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.18 Priority | This element indicates the priority of the request. It is coded as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────────────────────────────┼────────────┤ │... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.19 Classmark Information Type 2 | The classmark information type 2 defines certain attributes of the mobile station equipment in use on a particular transaction. It is coded as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.20 Classmark Information Type 3 | The classmark information type 3 defines certain attributes of the mobile station equipment in use on a particular transaction. It is coded as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.21 Interference Band To Be Used | This fixed length element is coded as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────────────────────────────┼────────────┤ │ Band to be used │octet 2 │ └... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.22 RR Cause | This fixed length element is passed from the radio interface to the MSC transparently, when received in a GSM 04.08 message. ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├──────────────... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.23 Spare | |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.24 Layer 3 Information | This is a variable length element used to pass radio interface messages from one network entity to another. ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────────────... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.25 DLCI | This is a fixed length element indicating the radio interface SAPI. ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────────────────────────────┼────────────┤ │ DLCI │o... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.26 Downlink DTX Flag | A fixed length element indicating whether the DTX function in the BSS is to be disabled on a particular radio channel. ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├────────────────────... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.27 Cell Identifier List | This element uniquely identifies cells and is of variable length containing the following fields: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├─────────────────────────────────────────... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.28 Response Request | The presence of this element indicates that a Handover Required Reject message is required by the BSS, if the Handover Required message does not result in a handover. The element has a fixed length of one octet: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴────... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.29 Resource Indication Method | This element defines the way the BSS shall transfer the resource information related to a cell to the MSC. The coding is as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├──────... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.30 Classmark Information Type 1 | The classmark information type 1 defines certain attributes of the mobile station equipment in use on a particular transaction. It is coded as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.31 Circuit Identity Code List | This element defines in conjunction with a Circuit Identity Code (3.2.2.2.) a list of terrestrial channels. ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────────────... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.32 Diagnostics | ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────────────────────────────┼────────────┤ │ Length │octet 2 │ ├───────────────────────────────────────────────┼────────... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.33 Chosen Channel | This Information Element contains a description of the channel allocated to the MS. For VGCS/VBS calls this Information Element contains a description of the channel allocated for the call in the cell. It is coded as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴──... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.34 Cipher Response Mode | This information element is used by the MSC to indicate whether the IMEI is to be included in the CIPHERING MODE COMPLETE message to be sent by the Mobile Station. ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Elemen... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.35 Layer 3 Message Contents | This is a variable length element used to pass the contents (from octet 3 up to the last octet) of radio interface messages from one network entity to another. ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element id... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.36 Channel Needed | This information element contains an indication for the mobile station of which channel is needed for the transaction linked to the paging procedure. It is coded as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.37 Trace Type | A fixed length element indicating the type of trace information to be recorded. ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────────────────────────────┼───────────... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.38 TriggerID | A variable length element indicating the identity of the entity which initiated the trace. ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────────────────────────────┼... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.39 Trace Reference | A fixed length element providing a trace reference number allocated by the triggering entity ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├──────────────────────────────────────────────... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.40 TransactionID | A potentially variable length element indicating a particular transaction within a trace. ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────────────────────────────┼─... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.41 Mobile Identity | A variable length element. ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────────────────────────────┼────────────┤ │ Length │octet 2 │ ├─────────────────────────────... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.42 OMCID | A variable length element indicating the destination OMC to which trace information is to be sent. ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├────────────────────────────────────────... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.43 Forward Indicator | A fixed length element indicating whether the trace is to be continued in a BSS to which the call has been handed over. ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.44 Chosen Encryption Algorithm | This element indicates the encryption algorithm being used by the BSS. It is coded as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├────────────────────────────────────────────... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.45 Circuit Pool | This element indicates the circuit pool of a circuit or group of circuits. It is coded as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├────────────────────────────────────────... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.46 Circuit Pool List | This element defines alist of BSS preferred circuit pools in order of preference. It is coded as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├─────────────────────────────────... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.47 Time Indication | This element defines the period where the information shall be valid. It is fixed length, 2 octets. The coding is as follows: 8 7 6 5 4 3 2 1 Element identifier octet 1 Time octet 2 The Time field of this Information Element message in octet 2 is coded as follows: 0000 0000 (note) 0000 0001 : : 1111 1110 Time, where th... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.48 Resource Situation | This element gives, for respective indicated channel type, the total number of channels accessible and the number of channels available on any given cell at the time of construction of the message. The number of channels available may be defined in up to five interference bands, the boundaries of these bands being set ... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.49 Current Channel Type 1 | This Information Element contains a description of the channel allocated to the MS. It is coded as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────┬───────... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.50 Queuing Indicator | This element contains a recommendation of the BSS concerning application of queuing. The element has a fixed length of two octets. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 107 (GSM 08.08 version 6.5.0 Release 1997) ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴────... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.51 Speech Version | This element indicates the speech version being used by the BSS. It is coded as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├─────┬─────────────────────────────────────────┼──... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.52 Assignment Requirement | 8 7 6 5 4 3 2 1 Element identifier octet 1 Assignment requirement octet 2 Octet 2 00000000 Delayed 00000001 Immediate all other values are reserved |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.53 [spare] | |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.54 Talker Flag | 8 7 6 5 4 3 2 1 Element identifier octet 1 |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.55 Group Call Reference | It is coded as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────────────────────────────┼────────────┤ │ Length │octet 2 │ ├────────────────────────────────... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.56 eMLPP Priority | This Information Element contains the eMLPP priority of the call. It is coded as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├─────────────────────────────┬─────────────────┼─... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.57 Configuration Evolution Indication | This information element indicates whether subsequent assignment requests should be expected and the limitation for these subsequent assignments. 8 7 6 5 4 3 2 1 Element identifier octet 1 spare SMI octet 2 SMI: Subsequent Modification Indication. This indicates the maximum number of TCH/F that could be requested in su... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.58 spare | |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.2.59 Old BSS to New BSS information | This information element is defined as a general container for passing Field Elements transparently between BSSs via the MSC. These Field Elements are passed in the “Old BSS to New BSS information elements” octets field. The error handling performed by the receiving entity for the “Old BSS to New BSS information elemen... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.3 SIGNALING FIELD ELEMENT CODING | The coding rules for signalling field elements are the same as the signalling element coding rules which are defined in section 3.2.2. Signalling field elements shall always include a Field Length indicator. A Field Length indicator with a value of zero shall not be considered as an error. Field Element Identifier Codi... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.3.1 Extra information | This field element provides a general flag mechanism that allows the old BSS to indicate to the new BSS flag information. It is coded as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Field Element identifier... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.3.2 Current Channel type 2 | This Field Element contains a description of the channel allocated to the MS. It is coded as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────┬─────────────... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.3.3 Target cell radio information | It is coded as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────────────────────────────┼────────────┤ │ Length │octet 2 │ ├────────────────────────────────... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.3.4 GPRS Suspend Information | This Field Element contains the contents of the Gb interface SUSPEND ACK PDU. It is coded as follows: ETSI ETSI TS 100 590 V6.5.0 (2000-06) 112 (GSM 08.08 version 6.5.0 Release 1997) ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼───... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.2.4 List of Timers in the BSSMAP Procedures | Timer Title Time T1 Time to receipt of BLOCKING ACKNOWLEDGE.at the BSS O&M T2 Reset guard period at the MSC O&M T4 Time to receipt of RESET ACKNOWLEDGE at the BSS O&M T5 Overload timer in the MSC, see 3.1.12.1 O&M T6 Overload timer in the MSC, see 3.1.12.1 O&M T7 Handover required periodicity O&M T8 Time to receipt of ... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 3.3 SDL Representation Of The Procedures At The BSS | The SDL diagrams may be inserted at a later stage after updating and carefully checking of consistency with the main text. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 113 (GSM 08.08 version 6.5.0 Release 1997) |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 4 Broadcast Information Control Channel | Information that is transferred in the Broadcast Control Channel is stored locally at the BSS. The scheduling of this information on the BCCH is controlled autonomously by the BSS. The set of information that is transmitted in the BCCH is derived locally or downloaded to the BSS via the BSS Operation and Maintenance Ap... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 5 Vocabulary | This clause contains definition of terms: BSS Base Station System. This is the equipment which is accessed through the interface defined in the 08-series of Technical Specifications. It contains the functionality described in GSM 08.02, and supports one or more cells. See GSM 01.04. BSSAP The Base Station System Applic... |
bf8e452635c0e3fa50938ae3618b9b7d | 100 590 | 6 List of diagrams | Figure Title 1. Signalling protocol reference model 2. Assignment 3. Handover execution 4. Handover required indication 5. Handover resource allocation 6. Release 7. Release due to reason at the BSS 8. [not used] 9. Classmark updating 10. Blocking of terrestrial circuits 11. Reset 12. Resource indication 13. Handover c... |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 0 Scope | The present document is split into two parts, clause 1-4 dealing with the MTP and chapters 5-7 dealing with the SCCP and its use. The MTP provides a mechanism giving reliable transfer of signalling messages. Clauses 1-4 of the present document deal with the subset of the MTP that can be used between an BSS and an MSC, ... |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 0.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... |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 0.2 Abbreviations | Abbreviations used in the present document are listed in GSM 01.04. |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 0.3 Definitions | E1 link employs 32 Pulse Code Modulation signals (timeslots) at 64 kbits/s. The 32 timeslots consist of 30 voice (or signalling) channels and 2 common signalling channels. The output bit rate is 2.048 Mbits/s. T1 link employs 24 Pulse Code Modulation signals (timeslots) at 64 kbits/s. (T1 interface can alternatively us... |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 1 Field of application | a) This Technical Specification is applicable to the signalling between radio subsystems (BSS) and mobile switching centres (MSCs) in GSM PLMNs. It provides a minimum set of MTP requirements that may be implemented at a BSS or MSC, whilst maintaining compatibility with the implementation of a full specification of the ... |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 2 Functional content | The functional requirements are as follows: a) The network call control functions are as specified in Technical Specifications GSM 08.08, 04.08. b) The minimum set of Message Transfer Part functions are specified in Blue Book CCITT Recommendations Q.702, Q.703, Q.704 and Q.707, with the qualifications specified in this... |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 3 Message transfer part (MTP) functions | |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 3.1 General | For E1 links, the MTP functions as specified in CCITT Recommendations Q.702, Q.703, Q.704 and Q.707 are applicable. For T1 links, the MTP functions as specified in ANSI specifications T1.110 section 2, and T1.112 section 2 are applicable. However, the following exceptions and modifications to those Recommendations may ... |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 3.2 Level 1 | |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 3.2.1 E1 link (CCITT Recommendation Q.702) | Q.702 fig 2 These figures should be treated as for information only. For the standard application of GSM, interface point C is appropriate. Q.702 subclause 1.4 The use of analogue circuits to support the signalling link is a national matter. Q.702 clause 2 A signalling rate of 64kbits/s is assumed. Lower rates (e.g. us... |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 3.2.2 T1 link (ANSI Specification T1.111.2) | T1.111.2 Figure 2 These figures should be treated as for information only. For the standard application, interface point C is appropriate. T1.111.2 Section 1.4 Analogue Signalling Link The use of analogue circuits to support the signalling link is a service provider option. T1.111.2 Section 2 General A signalling rate ... |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 3.3 Level 2 | |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 3.3.1 E1 link (CCITT Recommendation Q.703) | Q.703 subclause 1.4 Only the basic error correction protocol is required. Q.703 subclause 1.7 Only the emergency proving period and status indications should be used by the BSS. ETSI 13 ETSI TS 100 589 V7.0.1 (1999-07) (GSM 08.06 version 7.0.1 Release1998) Q.703 clause 6 Not applicable, only basic error correction is r... |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 3.3.2 T1 link (ANSI Specification T1.111.3) | T1.111.3 Section 1.4 Signal Unit Error Correction Only the basic error correction protocol is required. T1.111..3 Section 1.7 Only the emergency proving period and status indications should be used by the BSS. T1.111.3 Section 6 Preventive Cyclic Retransmission Error Correction Method Only basic error correction is req... |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 3.4 Level 3 | |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 3.4.1 E1 link (CCITT Recommendation Q.704) | Q.704 subclause 1.1.2. If the BSS is only implemented as the end point of a signalling link, IE it does not support STP working, then there will be no signalling transfer point network management features which need to be considered. Q.704 subclause 1.3 ETSI ETSI TS 100 589 V7.0.1 (1999-07) 14 (GSM 08.06 version 7.0.1 ... |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 3.4.2 T1 link (ANSI Specification T1.111.4) | T1.111.4 Section 1.1.2 Signalling Transfer Point network management procedures are not required on the A-Interface. T1.111.4 Section 1.3 Signalling link management is required. Load sharing is required, and changeover/back between links within a single linkset are required. T1.111.4 Section 2 Signalling Message Handlin... |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 3.5 Testing and Maintenance | |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 3.5.1 E1 link (CCITT Recommendation Q.707) | Q.707 subclause 2.2 The MSC and the BSS shall be capable of responding with an acknowledgement message to a SLTM received at any time as specified in CCITT Recommendation Q.707 subclause 2.2. |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 3.5.2 T1 link (ANSI Specification T1.111.7) | T1.111.7 Section 2.1 Signalling Data Link Test The signalling data link test is not required for the A-Interface. T1.111.7 Section 2.2 The generation of a SLTM is not required; however, the MSC and the BSS shall be capable of responding with an acknowledgement message to a SLTM that is received at any time as specified... |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 4 Interface functions | The method of interfacing to the higher layers will be by the primitives defined in CCITT Recommendation Q.701 clause 8 of the Blue Book for E1 links and T1.111 for T1 links. The primitives defined are: MTP Pause indication; MTP Resume indication; MTP Status indication; MTP Transfer request; MTP Transfer indication. |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 5 SCCP functions | |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 5.1 Overview | The purpose of this section is to identify the subset of the SCCP functions which are necessary to achieve the management of the MS references in the BSS to MSC interface, and to provide addressing facilities. If this subset of SCCP functions is implemented, compatibility with a full CCITT SCCP (ANSI SCCP if T1 links a... |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 5.2 Primitives | |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 5.2.1 E1 link (CCITT Recommendation Q.711) | Q.711/Table 1 Three primitives of the table 1/Q.711 are not used: - N-EXPEDITED DATA - N-DATA ACKNOWLEDGE - N-RESET Q.711/Table 2 The following parameters of the N-CONNECT primitive are not used: - Responding address - Receipt confirmation selection - Expedited data selection Q.711/Table 3 The following parameter of th... |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 5.2.2 T1 link (ANSI SpecificationT1.112.1) | T1.111.1 Table 1 Two primitives of the table are not used: - N-INFORM DATA ETSI 23 ETSI TS 100 589 V7.0.1 (1999-07) (GSM 08.06 version 7.0.1 Release1998) - N-RESET T1.112.1 Table 2 The following parameters of the N-CONNECT primitive are not used: - Responding address - Receipt confirmation selection - Expedited data se... |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 5.3 SCCP messages | |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 5.3.1 E1 link (CCITT Recommendation Q.712) | Q.712 subclause 1.4 The Data Acknowledgement (AK) message is not used. Q.712 subclause 1.6 The Data Form 2 (DT2) message is not used. Q.712 subclause 1.7 The Expedited Data (ED) message is not used. Q.712 subclause 1.8 The Expedited Data Acknowledgement (EA) message is not used. Q.712 subclause 1.10 The Protocol Data U... |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 5.3.2 T1 link (ANSI Specification T1.112.2) | T1.112.2 Paragraph 2.4 The Data Acknowledgement (AK) message is not used. T1.112.2 Paragraph 2.6 The Data Form 2 (DT2) message is not used. T1.112.2 Paragraph 2.7 The Expedited Data (ED) message is not used. T1.112.2 Paragraph 2.8 The Expedited Data Acknowledgement (EA) message is not used. T1.112.2 Paragraph 2.10 The ... |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 5.4 SCCP formats and codes | |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 5.4.1 E1 link (CCITT Recommendation Q.713) | Q.713 subclause 3.4 For point-to-point network structures (i.e. direct connections between MSC and BSS) the called party address may consist of the single element: - sub-system number. No global title is used. The signalling point code which is coded in the MTP routing label and the subsystem number in the called party... |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 5.4.2 T1 link (ANSI Specification T1.112.3) | T1.112.3 Paragraph 3.4 For point-to-point network structures (i.e., direct connections between the MSC and the BSS) the called party address may consist of the single element: - subsystem number No global title is used. The signalling point code which is coded in the MTP routing label and the subsystem number in the ca... |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 5.5 SCCP procedures | |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 5.5.1 E1 link (CCITT Recommendation Q.714) | Q.714 subclauses 1.1.2.2, 1.1.2.4 ETSI 27 ETSI TS 100 589 V7.0.1 (1999-07) (GSM 08.06 version 7.0.1 Release1998) Protocol classes 1 and 3 not used. Q.714 subclause 1.1.3 A signalling connection consists of a single connection section. No intermediate nodes are defined in the MSC/BSS protocol. The use of multiple connec... |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 5.5.2 T1 link (ANSI Specification T1.112.4) | T1.112.4 Paragraph 1.1.2.2, 1.1.2.4 Protocol classes 1 and 3 are not used. T1.112.4 Paragraph 1.1.3 A signalling connection consists of a single connection section. No intermediate nodes are defined in the MSC to BSS interface. The use of multiple connection sections is a operator option. T1.112.4 Paragraph 1.2.1 (b) N... |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 6 Use of the SCCP | The MTP and the SCCP are used to support signalling messages between the MSC and the BSS. One user function of the SCCP, called BSS Application Part (BSSAP) is defined. In the case of point-to-point calls the BSSAP uses one signalling connection per active Mobile Station having one or more active transactions for the t... |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 6.1 Connection establishment | A new SCCP connection is established when information related to the communication between an MS and the network on a dedicated radio resource has to be exchanged between BSS and MSC, and no such SCCP connection exists between the MSC and the BSS involved for the concerned mobile station. A new SCCP connection for each... |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 6.1.1 Establishment procedure in case i) | In this case, the connection establishment is performed at the reception by the BSS of the first layer-3 message from the MS (piggybacked on the SABM frame). This message (LOCATION UPDATING REQUEST, CM-SERVICE REQUEST, CM REESTABLISHMENT REQUEST, IMSI DETACH, PAGING RESPONSE, or IMMEDIATE SETUP) which contains the iden... |
b565fbd182a148565ebdcfaa5e266698 | 100 589 | 6.1.2 Establishment procedure in case ii) | In this case, the connection establishment is undertaken by the MSC as soon as the MSC decides to perform an external handover to a new cell for a point-to-point call or for participants in a voice group or broadcast call who are supported on a dedicated channel. A Connection Request message is sent to the BSS. The use... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.