hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
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 │ ├───────────────────────────────────────────────┼────────────┤ │ Length │octet 2 │ ├───────────────────────┬───────────────────────┼────────────┤ │ Spare │ Cell identification │octet 3 │ │ │ discriminator │ │ ├───────────────────────┴───────────────────────┼────────────┤ │ Cell identification │octet 4 - n│ └───────────────────────────────────────────────┴────────────┘ The coding of octet 2 is a binary number indicating the length of the remaining element. The length depends on the Cell identification discriminator (octet 3). The coding of "Cell identification discriminator" (bits 1 to 4 of octet 3) is a binary number indicating if the whole or a part of Cell Global Identification, CGI, according to GSM 03.03 is used for cell identification in octet 4-n. The "Cell identification discriminator" is coded as follows: 0000 The whole Cell Global Identification, CGI, is used to identify the cell. 0001 Location Area Code, LAC, and Cell Identity, CI, is used to identify the cell. 0010 Cell Identity, CI, is used to identify the cell. 0011 No cell is associated with the transaction. All other values are reserved. The coding of octet 4-n depends on the Cell identification discriminator (octet 3). Below the coding is shown for each Cell identification discriminator: ETSI ETSI TS 100 590 V6.5.0 (2000-06) 89 (GSM 08.08 version 6.5.0 Release 1997) Note that no coding is specified for a Cell identification discriminator value of "0011" as no additional information is required. Coding of Cell Identification for Cell identification discriminator = 0000 ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ MCC dig 2 │ MCC dig 1 │octet 4 │ ├───────────────────────┼───────────────────────┼────────────┤ │ 1 1 1 1 │ MCC dig 3 │octet 5 │ ├───────────────────────┼───────────────────────┼────────────┤ │ MNC dig 2 │ MNC dig 1 │octet 6 │ ├───────────────────────┴───────────────────────┼────────────┤ │ LAC │octet 7 │ ├───────────────────────────────────────────────┼────────────┤ │ LAC cont. │octet 8 │ ├───────────────────────────────────────────────┼────────────┤ │ CI value │octet 9 │ ├───────────────────────────────────────────────┼────────────┤ │ CI value cont │octet 10 │ └───────────────────────────────────────────────┴────────────┘ The octets 4-8 are coded as shown in GSM 04.08, Table "Location Area Identification information element". The octets 9-10 are coded as shown in GSM 04.08, Table "Cell Identity information element". Coding of Cell Identification for Cell identification discriminator = 0001 ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ LAC │octet 4 │ ├───────────────────────────────────────────────┼────────────┤ │ LAC cont. │octet 5 │ ├───────────────────────────────────────────────┼────────────┤ │ CI value │octet 6 │ ├───────────────────────────────────────────────┼────────────┤ │ CI value cont │octet 7 │ └───────────────────────────────────────────────┴────────────┘ Coding of Cell Identification for Cell identification discriminator = 0010 ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ CI value │octet 4 │ ├───────────────────────────────────────────────┼────────────┤ │ CI value cont │octet 5 │ └───────────────────────────────────────────────┴────────────┘ The octets 4-5 are coded as shown in GSM 04.08, Table "Cell Identity information element".
|
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 │ ├───────────────────────────────────────────────┼────────────┤ │ Length │octet 2 │ ├───────────────────────────────────────────────┼────────────┤ │ Priority │octet 3 │ └───────────────────────────────────────────────┴────────────┘ Octet 2 is a binary indication of the length of the rest of the element. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 90 (GSM 08.08 version 6.5.0 Release 1997) Octet 3 is coded as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 │ 6 5 4 3 2 1 │ │ ├─────┬─────┼─────┴─────┴─────┴─────┼─────┼─────┼────────────┤ │spare│pci │ priority level │ qa │pvi │octet 3 │ └─────┴─────┴───────────────────────┴─────┴─────┴────────────┘ Bit 8 is spare, set to 0 pci = Preemption Capability indicator (see note) 0 this allocation request shall not preempt an existing connection 1 this allocation request may preempt an existing connection priority level: 6 5 4 3 0 0 0 0 spare 0 0 0 1 priority level 1 = highest priority 0 0 1 0 priority level 2 = second highest priority : : : : 1 1 1 0 priority level 14 = lowest priority 1 1 1 1 priority not used qa = queueing allowed indicator 0 queueing not allowed 1 queueing allowed pvi = Preemption Vulnerability indicator (see note) 0 this connection shall not be preempted by another allocation request 1 this connection might be preempted by another allocation request NOTE: Preemption Capability indicator applies to the allocation of resources for an event and as such it provides the trigger to the preemption procedures/processes of the BSS. Preemption Vulnerability indicator applies for the entire duration of a connection and as such indicates whether the connection is a target of the preemption procedures/processes of the BSS.
|
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 │octet 1 │ ├───────────────────────────────────────────────┼────────────┤ │ Length │octet 2 │ ├───────────────────────────────────────────────┼────────────┤ │ Classmark │octet 3 - 5│ └───────────────────────────────────────────────┴────────────┘ Octet 2 is a binary indication of the length of the remainder of the element in octets. The length shall be determined by the length of the Mobile Station Classmark 2 element of GSM 04.08. The classmark octets 3, 4 and 5 are coded in the same way as the equivalent octets in the Mobile station classmark 2 element of GSM 04.08. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 91 (GSM 08.08 version 6.5.0 Release 1997)
|
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 │octet 1 │ ├───────────────────────────────────────────────┼────────────┤ │ Length │octet 2 │ ├───────────────────────────────────────────────┼────────────┤ │ Classmark │octet 3-14 │ └───────────────────────────────────────────────┴────────────┘ Octet 2 is a binary indication of the length of the remainder of the element in octets. The length octet has a minimum value of 1 and a maximum of 12. The length shall be determined by the length of the Mobile Station Classmark 3 element of GSM 04.08. The classmark octets 3 to 14 are coded in the same way as the equivalent octets in the Mobile station classmark 3 element of GSM 04.08.
|
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 │ └───────────────────────────────────────────────┴────────────┘ Octet 2 is coded as: Bits 876 Spare Bits 54321 A bit map indicating which interference bands are acceptable, the LSB represents the least level of interference.
|
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 │ ├───────────────────────────────────────────────┼────────────┤ │ RR cause │octet 2 │ └────────────────────────────────────────────────────────────┘ Octet 2 is coded as the equivalent field from GSM 04.08. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 92 (GSM 08.08 version 6.5.0 Release 1997)
|
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 │ ├───────────────────────────────────────────────┼────────────┤ │ Length │octet 2 │ ├───────────────────────────────────────────────┼────────────┤ │ Layer 3 information │octet 3 - n│ └───────────────────────────────────────────────┴────────────┘ Octet 1 identifies the element. Octet 2 gives the length of the following layer 3 information. Octet j (j = 3, 4, ..., n) is the unchanged octet j-2 of a radio interface layer 3 message as defined in GSM 04.08, n-2 is equal to the length of that radio interface layer 3 message.
|
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 │octet 2 │ └───────────────────────────────────────────────┴────────────┘ Octet 2 is coded as the DLCI octet described in 08.06.
|
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 │ ├───────────────────────────────────────────────┼────────────┤ │ Downlink DTX flag │octet 2 │ └───────────────────────────────────────────────┴────────────┘ The Downlink DTX Flag is coded as follows: - bits 8 to 2 are spare; - bit 1 is set to one if the MSC forbids the BSS to activate DTX in the downlink direction; it is set to 0 otherwise. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 93 (GSM 08.08 version 6.5.0 Release 1997)
|
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 │ ├───────────────────────────────────────────────┼────────────┤ │ Length │octet 2 │ ├───────────────────────┬───────────────────────┼────────────┤ │ Spare │ Cell identification │octet 3 │ │ │ discriminator │ │ ├───────────────────────┴───────────────────────┼────────────┤ │ Cell identification 1 │octet 4-4+m│ ├───────────────────────────────────────────────┼────────────┤ : : : ├───────────────────────────────────────────────┼────────────┤ │ Cell identification n │.. to 4+nm │ └───────────────────────────────────────────────┴────────────┘ The coding of octet 2 is a binary number indicating the Length of the remaining element. The Length depends on the Cell identification discriminator (bits 1 to 4 of octet 3) as well as the number of cells to be identified. The coding of the Cell identification discriminator is a binary number indicating if the whole or a part of Cell Global identification, CGI, according to GSM 03.03 is used for cell identification of the cells in the list. The Cell identification discriminator is coded as follows: 0000 The whole Cell Global Identification, CGI, is used to identify the cells. 0001 Location Area Code, LAC, and Cell Identify, CI, is used to identify the cells. 0010 Cell Identity, CI, is used to identify the cells. 0011 No cell is associated with the transaction. 0100 Location Area Identification, LAI, is used to identify all cells within a Location Area. 0101 Location Area Code, LAC, is used to identify all cells within a location area. 0110 All cells on the BSS are identified. All other values are reserved. Values 0100, 0101 and 0110 are only applicable for page message. The coding of the Cell Identifications 1 to n (octets 4 to 4+nm) depends on the Cell identification discriminator (octet 3). Below the coding of the i-th Cell Identification is shown for each Cell identification discriminator (with "i" in the range 1 to n): Note that no coding is specified for Cell identification discriminator values of "0011" and "0110" as no additional information is required. Coding of the i-th Cell Identification for Cell identification discriminator = 0000 ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ MCC dig 2 │ MCC dig 1 │octet x+1 │ ├───────────────────────┼───────────────────────┼────────────┤ │ 1 1 1 1 │ MCC dig 3 │octet x+2 │ ├───────────────────────┼───────────────────────┼────────────┤ │ MNC dig 2 │ MNC dig 1 │octet x+3 │ ├───────────────────────┴───────────────────────┼────────────┤ │ LAC │octet x+4 │ ├───────────────────────────────────────────────┼────────────┤ │ LAC cont. │octet x+5 │ ├───────────────────────────────────────────────┼────────────┤ │ CI value │octet x+6 │ ├───────────────────────────────────────────────┼────────────┤ │ CI value cont │octet x+7 │ └───────────────────────────────────────────────┴────────────┘ Where x = 3 + 7(i-1). The octets (x+1)-(x+5) are coded as shown in GSM 04.08, Table "Location Area Identification information element". ETSI ETSI TS 100 590 V6.5.0 (2000-06) 94 (GSM 08.08 version 6.5.0 Release 1997) The octets (x+6)-(x+7) are coded as shown in GSM 04.08, Table "Cell Identity information element". Coding of i-th Cell Identification for Cell identification discriminator = 0001 ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ LAC │octet x+1 │ ├───────────────────────────────────────────────┼────────────┤ │ LAC cont. │octet x+2 │ ├───────────────────────────────────────────────┼────────────┤ │ CI value │octet x+3 │ ├───────────────────────────────────────────────┼────────────┤ │ CI value cont │octet x+4 │ └───────────────────────────────────────────────┴────────────┘ Where x = 3 + 4(i-1) The octets (x+1)-(x+2) are coded as shown in GSM 04.08, Table ‘Location Area Identification information element’. The octets (x+3)-(x+4) are coded as shown in GSM 04.08, Table ‘Cell Identity information element’. Coding of i-th Cell Identification for Cell identification discriminator = 0010 ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ CI value │octet x+1 │ ├───────────────────────────────────────────────┼────────────┤ │ CI value cont │octet x+2 │ └───────────────────────────────────────────────┴────────────┘ Where x = 3 + 2(i-1) The octets (x+1)-(x+2) are coded as shown in GSM 04.08, Table ‘Cell Identity information element’. Coding of i-th Cell Identification for Cell identification discriminator = 0100 ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ MCC dig 2 │ MCC dig 1 │octet x+1 │ ├───────────────────────┼───────────────────────┼────────────┤ │ 1 1 1 1 │ MCC dig 3 │octet x+2 │ ├───────────────────────┼───────────────────────┼────────────┤ │ MNC dig 2 │ MNC dig 1 │octet x+3 │ ├───────────────────────┴───────────────────────┼────────────┤ │ LAC │octet x+4 │ ├───────────────────────────────────────────────┼────────────┤ │ LAC cont. │octet x+5 │ └───────────────────────────────────────────────┴────────────┘ Where x = 3 + 5(i-1) The octets (x+1)-(x+5) are coded as shown in GSM 04.08, Table "Location Area Identification information element". Coding of i-th Cell Identification for Cell identification discriminator = 0101 ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ LAC │octet x+1 │ ├───────────────────────────────────────────────┼────────────┤ │ LAC cont. │octet x+2 │ └───────────────────────────────────────────────┴────────────┘ Where x = 3 + 2(i-1) The octets (x+1)-(x+2) are coded as shown in GSM 04.08, Table "Location Area Identification information element". ETSI ETSI TS 100 590 V6.5.0 (2000-06) 95 (GSM 08.08 version 6.5.0 Release 1997) The appropriate coding for not identified cells is "0" for all bits of LAC and CI for all possible Cell Identification Discriminator values.
|
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 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 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 │ ├───────────────────────┬───────────────────────┼────────────┤ │ Spare Resource indication │octet 2 │ │ method │ │ └───────────────────────┴───────────────────────┴────────────┘ The coding of the Resource Indication parameter is: 0000 the method i) of subclause 3.1.3.1 is selected, 0001 the method ii) of subclause 3.1.3.1 is selected, 0010 the method iii) of subclause 3.1.3.1 is selected, 0011 the method iv) of subclause 3.1.3.1 is selected. All other values are reserved.
|
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 │octet 1 │ ├───────────────────────────────────────────────┼────────────┤ │ Classmark │octet 2 │ └───────────────────────────────────────────────┴────────────┘ The classmark octet 2 is coded in the same way as the equivalent octet in the classmark 1 element of 04.08. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 96 (GSM 08.08 version 6.5.0 Release 1997)
|
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 │ ├───────────────────────────────────────────────┼────────────┤ │ Length │octet 2 │ ├───────────────────────────────────────────────┼────────────┤ │ Range │octet 3 │ ├───────────────────────────────────────────────┼────────────┤ │ Status │octet 4-35 │ └───────────────────────────────────────────────┴────────────┘ The following codes are used in the range and status fields: Range: A number in pure binary representation ranging from 0 to 255. The number represented by the range code +1 indicates the range of circuits affected by the message. Status: The Status subfield contains up to 256 Status bits numbered from 0 up to 255. Status bit 0 is located in bit position 1 of the first Status subfield octet and refers to the circuit indicated in the CIC subfield{should be "associated Circuit Identity Code Information Element" not "CIC subfield"} itself. Other Status bits follow in numerical order. Each Status bit is associated with a circuit identification code such that Status bit n is associated with CIC m+n, where m is the CIC contained in the message.{"where m is the CIC identified in the asociated Circuit Identity Code Information Element in the message"}. Status bit n is located in bit position nb of the no-th octet of the Status subfield with: nb = (n mod 8) + 1 and no = (n div 8) + 1. The number of relevant Status bits in a given Status subfield is equal to the range value +1. The Status bits are coded as follows: - in the CIRCUIT GROUP BLOCK message 0 no indication 1 block - in the CIRCUIT GROUP BLOCKING ACKNOWLEDGE message 0 no indication 1 blocking acknowledgement - in the CIRCUIT GROUP UNBLOCK message 0 no indication 1 unblock - in the CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE message 0 no indication 1 unblocking acknowledgement ETSI ETSI TS 100 590 V6.5.0 (2000-06) 97 (GSM 08.08 version 6.5.0 Release 1997) - in the UNEQUIPPED CIRCUIT message 0 no indication 1 unequipped
|
bf8e452635c0e3fa50938ae3618b9b7d
|
100 590
|
3.2.2.32 Diagnostics
|
┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 6 5 4 3 2 1 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────────────────────────────┼────────────┤ │ Length │octet 2 │ ├───────────────────────────────────────────────┼────────────┤ │ Error pointer │octet 3-4 │ ├───────────────────────────────────────────────┼────────────┤ │ Message received │octet 5-n │ └───────────────────────────────────────────────┴────────────┘ The coding of the error pointer field is as follows: Octet 3 gives the number of octets between octet 4 (not included) and the first octet (included) of the part of the message received which provoked the error. Thus: 0000 0000 Error location not determined 0000 0001 The first octet of the message received (i.e. the message type) was found erroneous (unknown) 0000 0010 The second octet of the message received was found erroneous 0000 0011 The third octet of the message received was found erroneous etc. The last three values are reserved for the BSSAP header: 1111 1101 The first octet of the BSSAP header (Discrimination) was found erroneous 1111 1110 (DTAP only) The DLCI (second) octet of the BSSAP header was found erroneous 1111 1111 The last octet of the BSSAP header (length indicator) was found erroneous Octet 4 is coded as follows: bit 8 7 6 5 4 3 2 1 ┌───────────────────────┬───────────────────────┐ │ 0 0 0 0 │ │ │ spare │ bit pointer │ └───────────────────────┴───────────────────────┘ The bit pointer field is coded as follows: bits 4321 0000 No particular part of the octet is indicated 0001 An error was provoked by the field whose most significant bit is in bit position 1 0010 An error was provided by the field whose most significant bit is in bit position 2 0011 An error was provided by the field whose most significant bit is in bit position 3 0100 An error was provided by the field whose most significant bit is in bit position 4 0101 An error was provided by the field whose most significant bit is in bit position 5 0110 An error was provided by the field whose most significant bit is in bit position 6 0111 An error was provided by the field whose most significant bit is in bit position 7 1000 An error was provided by the field whose most significant bit is in bit position 8 All other values are reserved. The "message received" field should be the contents, as far as can be determined, of the received message which provoked the error. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 98 (GSM 08.08 version 6.5.0 Release 1997)
|
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 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────┬───────────────────────┼────────────┤ │ Channel mode │ Channel │octet 2 │ └───────────────────────┴───────────────────────┴────────────┘ The channel mode field is coded as follows: Bit 8765 0000 no channel mode indication 1001 speech (full rate or half rate) 1110 data, 14.5 kbit/s radio interface rate 1011 data, 12.0 kbit/s radio interface rate 1100 data, 6.0 kbit/s radio interface rate 1101 data, 3.6 kbit/s radio interface rate 1000 signalling only All other values are reserved. The channel field is coded as follows: Bit 4321 0000 None (Note *) 0001 SDCCH 1000 1 Full rate TCH 1001 1 Half rate TCH 1010 2 Full Rate TCHs 1011 3 Full Rate TCHs 1100 4 Full Rate TCHs 1101 5 Full Rate TCHs 1110 6 Full Rate TCHs 1111 7 Full Rate TCHs 0100 8 Full Rate TCHs NOTE*: This value may be returned in the chosen channel information for VGCS/VBS calls in the case where the BSS has decided to de-allocate resources or allocate no resources for the call. All other values are reserved. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 99 (GSM 08.08 version 6.5.0 Release 1997)
|
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 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────────────────────────────┼────────────┤ │ Cipher response mode │octet 2 │ └───────────────────────────────────────────────┴────────────┘ Octet 2 is coded as:- Bits 8,7,6,5,4,3,2 - Spare Bit 1 = 0 - IMEISV must not be included by the Mobile Station Bit 1 = 1 - IMEISV must be included by the Mobile Station
|
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 identifier │octet 1 │ ├───────────────────────────────────────────────┼────────────┤ │ Length │octet 2 │ ├───────────────────────────────────────────────┼────────────┤ │ Layer 3 message contents │octet 3 - n│ └───────────────────────────────────────────────┴────────────┘ The length indicator (octet 2) is a binary number indicating the absolute length of the contents after the length indicator octet. Octet j (j = 3, 4, ..., n) is the unchanged octet j of a radio interface layer 3 message as defined in GSM 04.08, n is equal to the length of that radio interface layer 3 message.
|
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 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────────────────┬───────────┼────────────┤ │ Spare │ Channel │octet 2 │ └───────────────────────────────────┴───────────┴────────────┘ ETSI ETSI TS 100 590 V6.5.0 (2000-06) 100 (GSM 08.08 version 6.5.0 Release 1997) The Channel field is coded as follows: Bit 2 1 0 0 Any channel 0 1 SDCCH 1 0 TCH/F (Full rate) 1 1 TCH/H or TCH/F (Dual rate)
|
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 │ ├───────────────────────────────────────────────┼────────────┤ │ Trace type │octet 2 │ └───────────────────────────────────────────────┴────────────┘ Octet 2 contains the trace type. Octet 2 is coded as the MSC/BSS Trace Type specified in GSM 12.08.
|
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 │ ├───────────────────────────────────────────────┼────────────┤ │ Length │octet 2 │ ├───────────────────────────────────────────────┼────────────┤ │ Entity identity │octets 3-22│ └───────────────────────────────────────────────┴────────────┘ Octets 3-22 may be typically an OMC identity.
|
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 │ ├───────────────────────────────────────────────┼────────────┤ │ TraceReference │octet 2-3 │ └───────────────────────────────────────────────┴────────────┘
|
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 │ ├───────────────────────────────────────────────┼────────────┤ │ Length │octet 2 │ ├───────────────────────────────────────────────┼────────────┤ │ Transaction number │octet 3-4 │ └───────────────────────────────────────────────┴────────────┘ ETSI ETSI TS 100 590 V6.5.0 (2000-06) 101 (GSM 08.08 version 6.5.0 Release 1997)
|
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 │ ├───────────────────────────────────────────────┼────────────┤ │ Mobile identity │octet 3-n │ └───────────────────────────────────────────────┴────────────┘ Octet 3-n contain either the IMSI, IMEISV or IMEI as coded in GSM 04.08, not including GSM 04.08 element identifier or GSM 04.08 octet length value.
|
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 │ ├───────────────────────────────────────────────┼────────────┤ │ Length │octet 2 │ ├───────────────────────────────────────────────┼────────────┤ │ OMC identity │octets 3-22│ └───────────────────────────────────────────────┴────────────┘ For the OMC identity, see TS 12.20
|
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 │ ├───────────────────────┬───────────────────────┼────────────┤ │ spare │Forward indicator │octet 2 │ └───────────────────────┴───────────────────────┴────────────┘ Octet 2 is coded as follows: bit 4 3 2 1 0 0 0 1 forward to subsequent BSS, no trace at MSC 0 0 1 0 forward to subsequent BSS, and trace at MSC All other values are reserved. Bits 5-8 are spare.
|
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 │ ├───────────────────────────────────────────────┼────────────┤ │ Algorithm identifier │octet 2 │ └───────────────────────────────────────────────┴────────────┘ The algorithm identifier caters for the possible future introduction of different user data encryption algorithms. It is coded as; ETSI ETSI TS 100 590 V6.5.0 (2000-06) 102 (GSM 08.08 version 6.5.0 Release 1997) 0000 0001 No encryption used 0000 0010 GSM user data encryption version 1(A5/1). 0000 0011 GSM A5/2 0000 0100 GSM A5/3 0000 0101 GSM A5/4 0000 0110 GSM A5/5 0000 0111 GSM A5/6 0000 1000 GSM A5/7 All other values are Reserved for future international use.
|
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 │ ├───────────────────────────────────────────────┼────────────┤ │ Circuit pool number │octet 2 │ └───────────────────────────────────────────────┴────────────┘ Predefined circuit pools are currently Circuit pool number 1 to Circuit pool number 22. The circuit pool element is coded as follows (along with the definition of the predefined circuit pools): Coding Pool Supported channels and speech coding algorithms 0000 0001 Circuit pool number 1 FR speech version 1 FR data (12, 6, 3.6 kbit/s) 0000 0010 Circuit pool number 2 HR speech version 1 HR data (6, 3.6 kbit/s) 0000 0011 Circuit pool number 3 FR speech version 1 FR data (12, 6, 3.6 kbit/s) HR speech HR data (6, 3.6 kbit/s) 0000 0100 Circuit pool number 4 FR speech version 2 FR data (12, 6, 3.6 kbit/s) 0000 0101 Circuit pool number 5 FR speech version 1 FR speech version 2 FR data (12, 6, 3.6 kbit/s) 0000 0110 Circuit pool number 6 FR speech version 2 FR data (12, 6, 3.6 kbit/s) HR speech version 1 HR data (6, 3.6 kbit/s) 0000 0111 Circuit pool number 7 FR speech version 1 FR speech version 2 FR data (12, 6, 3.6 kbit/s) HR speech version 1 HR data (6, 3.6 kbit/s) 0000 1000 Circuit pool number 8 HSCSD max 2 x FR data (12, 6 kbit/s) 0000 1001 Circuit pool number 9 FR data (12, 6, 3.6 kbit/s) HR data (6, 3.6 kbit/s) HSCSD max 2 x FR data (12, 6 kbit/s) 0000 1010 Circuit pool number 10 FR speech version 1 FR speech version 2 FR data (12, 6, 3.6 kbit/s) HR speech version 1 HR data (6, 3.6 kbit/s) HSCSD max 2 x FR data (12, 6 kbit/s) 0000 1011 Circuit pool number 11 HSCSD max 4 x FR data (12, 6 kbit/s) (continued) ETSI ETSI TS 100 590 V6.5.0 (2000-06) 103 (GSM 08.08 version 6.5.0 Release 1997) (concluded): Coding Pool Supported channels and speech coding algorithms 0000 1100 Circuit pool number 12 FR data (12, 6, 3.6 kbit/s) HR data (6, 3.6 kbit/s) HSCSD max 4 x FR data (12, 6 kbit/s) 0000 1101 Circuit pool number 13 FR speech version 1 FR speech version 2 FR data (12, 6, 3.6 kbit/s) HR speech version 1 HR data (6, 3.6 kbit/s) HSCSD max 4 x FR data (12, 6 kbit/s) 0000 1110 Circuit pool number 14 HSCSD max 6 x FR data (12, 6 kbit/s) 0000 1111 Circuit pool number 15 FR data (14.5 kbit/s) 0001 0000 Circuit pool number 16 HSCSD max 2 x FR data (14.5 kbit/s) 0001 0001 Circuit pool number 17 HSCSD max 4 x FR data (14.5 kbit/s) 0001 0010 Circuit pool number 18 FR data (14.5, 12, 6, 3.6 kbit/s) HR data (6, 3.6 kbit/s) HSCSD max 2 x FR data (14.5, 12, 6 kbit/s) 0001 0011 Circuit pool number 19 FR data (14.5, 12, 6, 3.6 kbit/s) HR data (6, 3.6 kbit/s) HSCSD max 4 x FR data (14.5, 12, 6 kbit/s) 0001 0100 Circuit pool number 20 FR speech version 1 FR speech version 2 FR data (14.5, 12, 6, 3.6 kbit/s) HR speech version 1 HR data (6, 3.6 kbit/s) 0001 0101 Circuit pool number 21 FR speech version 1 FR speech version 2 FR data (14.5, 12, 6, 3.6 kbit/s) HR speech version 1 HR data (6, 3.6 kbit/s) HSCSD max 2 x FR data (14.5, 12, 6 kbit/s) 0001 0110 Circuit pool number 22 FR speech version 1 FR speech version 2 FR data (14.5, 12, 6, 3.6 kbit/s) HR speech version 1 HR data (6, 3.6 kbit/s) HSCSD max 4 x FR data (14.5, 12, 6 kbit/s) 1000 xxxx For national/local use
|
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 │ ├───────────────────────────────────────────────┼────────────┤ │ Length │octet 2 │ ├───────────────────────────────────────────────┼────────────┤ │ Circuit pool number (1st preferred) │octet 3 │ ├───────────────────────────────────────────────┼────────────┤ : : : ├───────────────────────────────────────────────┼────────────┤ │ Circuit pool number (nth preferred) │octet n+2 │ └───────────────────────────────────────────────┴────────────┘ The Circuit pool number is coded as specified in 3.2.2.45. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 104 (GSM 08.08 version 6.5.0 Release 1997)
|
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 the time is the binary value of octet 2 * 10s (ie 10s to 2540s). If the Time field contains the value 255 (1111 1111), the receiving entity shall consider the time as infinite. NOTE: The value 0 has a special meaning in the Load indication procedure (refer to subclause 3.1.20).
|
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 by O and M as follows: Interference level: 0 --------------------------- Band 1 X1 --------------------------- Band 2 X2 --------------------------- Band 3 X3 --------------------------- Band 4 X4 --------------------------- Band 5 X5 --------------------------- The element is coded as follows: ETSI ETSI TS 100 590 V6.5.0 (2000-06) 105 (GSM 08.08 version 6.5.0 Release 1997) 8 7 6 5 4 3 2 1 Element identifier octet 1 Length octet 2 Resource and interference band indicator Channel type octet 3 7/15 ind. Number of channels octet 4 octet 4a Resource and interference band indicator Channel type octet 5 7/15 ind. Number of channels octet 6 octet 6a . . Resource and interference band indicator Channel type octet N-1 7/15 ind. Number of channels octet N octet Na The length indicator is a binary representation of the length of the following element. The Resource type octet (octets 3, 5, etc.) is coded as follows: The Channel type field (bits 1-4 of octets 3, 5, etc.) is coded as follows: Bit 4 3 2 1 0 0 0 1 SDCCH 1 0 0 0 Full Rate TCH 1 0 0 1 Half Rate TCH All other values are reserved. The Resource and interference band indicator field (bits 5-8 of octets 3, 5, etc.) is coded as follows: Bit 8 7 6 5 0 0 0 0 Total number of channels accessible (i.e. available for service or currently assigned) 0 0 0 1 Number of channels available in interference band 1 0 0 1 0 Number of channels available in interference band 2 0 0 1 1 Number of channels available in interference band 3 0 1 0 0 Number of channels available in interference band 4 0 1 0 1 Number of channels available in interference band 5 1 1 1 0 Number of channels available without supplied interference band classification All other values are reserved. The Number of channels octets (octets 4, 6, etc.) is coded as follows: The Number of channels is a single octet element if the 7/15 indication bit (bit 8 of octets 4, 6, etc.) is set to 0. If the 7/15 indication bit is set to 1 then it is a 2 octet field. It give a 7 (or 15) bit binary representation of the number of channels with resource type as indicated in the nearest preceding resource type octet. The coding convention used when a field extends over more than one octet is defined in subclause 3.2.2. The number of half rate channels will include half rate channels counted as full rate channels, if these correspond to full rate channels that can be used as half rate channels. (e.g. If there is one idle half rate channel and one idle full rate channel that can be used as two half rate channels, then the full rate count will be 1 and the half rate count will be 3). The Resource type octet and the Number of channels octet(s) are repeated for each of the resource type reported. For each of the channel type reported, the total number of channels accessible and at least one indication of available channels shall be included. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 106 (GSM 08.08 version 6.5.0 Release 1997) The number of channels available without supplied interference band classification is included only in case the interference band definition is not available for the reported channel type.
|
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 │ ├───────────────────────┬───────────────────────┼────────────┤ │ Channel mode │ Channel │octet 2 │ └───────────────────────┴───────────────────────┴────────────┘ The channel mode field is coded as follows: Bit 8765 0000 signalling only 0001 speech (full rate or half rate) 0110 data, 14.5 kbit/s radio interface rate 0011 data, 12.0 kbit/s radio interface rate 0100 data, 6.0 kbit/s radio interface rate 0101 data, 3.6 kbit/s radio interface rate 1111 is reserved All other values are for future use. If the receiver receives an unknown channel mode it shall not be rejected but the receiver shall assume that the channel mode is to be changed. The channel field is coded as follows: Bit 4321 0001 SDCCH 1000 1 Full rate TCH 1001 1 Half rate TCH 1010 2 Full Rate TCHs 1011 3 Full Rate TCHs 1100 4 Full Rate TCHs 1101 5 Full Rate TCHs 1110 6 Full Rate TCHs 1111 7 Full Rate TCHs 0100 8 Full Rate TCHs 0000 is reserved All other values are for future use. If the receiver receives a unknown channel field it shall not be rejected but the receiver shall assume that the channel is to be changed. Consistencies between channel fields and channel modes shall not be checked.
|
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 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────────────────┬─────┬─────┼────────────┤ │ spare │qri │spare│octet 2 │ └───────────────────────────────────┴─────┴─────┴────────────┘ Octet 2 is coded as follows: qri = queuing recommendation indicator 0 it is recommended not to allow queueing 1 it is recommended to allow queueing
|
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 │ ├─────┬─────────────────────────────────────────┼────────────┤ │spare│ Speech version identifier │octet 2 │ └─────┴─────────────────────────────────────────┴────────────┘ The bits 7-1 of octet 2 are coded in the same way as the permitted speech version identifier in the Channel type information element.
|
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 │ ├───────────────────────────────────────────────┼────────────┤ │Descriptive group or broadcast call reference │octets 3-7 │ └───────────────────────────────────────────────┴────────────┘ Octet 2 is a binary indication of the length of the remainder of the element in octets. The octets 3 to 8 are coded in the same way as the octets 2-6 in the Descriptive group or broadcast call reference information element as defined in GSM 04.08. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 108 (GSM 08.08 version 6.5.0 Release 1997)
|
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 │ ├─────────────────────────────┬─────────────────┼────────────┤ │ spare │call priority │octet 2 │ └─────────────────────────────┴─────────────────┴────────────┘ The call priority field (bit 3 to 1 of octet 2) is coded in the same way as the call priority field (bit 3 to 1 of octet 5) in the Descriptive group or broadcast call reference information element as defined in GSM 04.08.
|
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 subsequent assignments. The SMI field is coded as follows: Bit 4321 0000 No Modification is allowed 0001 Modification is allowed and maximum number of TCH/F is 1 0010 Modification is allowed and maximum number of TCH/F is 2 0011 Modification is allowed and maximum number of TCH/F is 3 0100 Modification is allowed and maximum number of TCH/F is 4 All other values are reserved.
|
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 elements” field is that specified in section 3.1.19.7. +------------------------------------------------------------+ ¦ 8 7 6 5 4 3 2 1 ¦ ¦ +-----------------------------------------------+------------¦ ¦ Element identifier ¦ octet 1 ¦ +-----------------------------------------------+------------¦ ¦ Length ¦ octet 2 ¦ +-----------------------------------------------+------------¦ ¦ Old BSS to New BSS information elements ¦ octet 3-n ¦ +------------------------------------------------------------+ The length indicator (octet 2) is a binary number indicating the absolute length of the contents after the length indicator octet and may be set to zero. The Old BSS to New BSS information elements field is made up of 0 or more Field Elements listed in the table shown below. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 109 (GSM 08.08 version 6.5.0 Release 1997) Field elements may occur in any order in the Old BSS to New BSS information elements field. The construction of the Field Elements allows the receiver to ignore unknown Field Elements. Due to backward compatibility issues Field Elements in the “Old BSS to New BSS information” may duplicate Information Elements in the HANDOVER REQUEST, when this occurs and the new BSS detects an inconsistency between this information then the information contained in the “Old BSS to New BSS information” shall take precedence as long as the coding is understood by the new BSS. Reception of an erroneous “Old BSS to New BSS information” shall not cause a rejection of the HANDOVER REQUEST message; the “Old BSS to New BSS information” information element shall be discarded and the handover resource allocation procedure shall continue. FIELD ELEMENT REFERENCE LEN Extra information 3.2.3.1 3 Current Channel Type 2 3.2.3.2 4 Target cell radio information 3.2.3.3 3 GPRS Suspend information 3.2.3.4 19
|
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 Coding Field Element name Reference 0000 0001 Extra information 3.2.3.1 0000 0010 Current Channel Type 2 3.2.2.2 0000 0011 Target cell radio information 3.2.3.3 0000 0100 GPRS Suspend information 3.2.3.4 All other values are for future use.
|
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 │octet 1 │ ├───────────────────────────────────────────────┼────────────┤ │ Length │octet 2 │ ├───────────────────────────────────────────────┼────────────┤ │ │octet 3 │ └───────────────────────────────────────────────┴────────────┘ Octet 2 is a binary indication of the length of the rest of the field element. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 110 (GSM 08.08 version 6.5.0 Release 1997) Octet 3 is coded as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 │ 6 5 4 3 2 1 │ │ ├─────┬─────┼─────┴─────┴─────┴─────┼─────┼─────┼────────────┤ │ spare │prec │octet 3 │ └─────┴─────┴───────────────────────┴─────┴─────┴────────────┘ Bit 8 to 2 are flags that indicate no information. prec = Pre-emption Recommendation 0 The old BSS recommends that this allocation request should not cause a pre-emption an existing connection. 1 The old BSS recommends that this allocation request is allowed to preempt an existing connection based on the information supplied in the Priority information element, if available. In the case the “prec” bit is not present or the Extra Information field element is not present then the new BSS should run pre-emption as specified by the Priority information element, if available. In the case where the Priority information element is not present in the request then the "prec" element, if present, shall be ignored.
|
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 │ ├───────────────────────┬───────────────────────┼────────────┤ │ Length │octet 2 │ ├───────────────────────┬───────────────────────┼────────────┤ │ Channel mode │octet 3 │ ├───────────────────────┬───────────────────────┼────────────┤ │ Channel field │octet 4 │ └───────────────────────┴───────────────────────┴────────────┘ The channel mode field is coded as follows: Bit 4321 0000 signalling only 0001 speech (full rate or half rate) 0110 data, 14.5 kbit/s radio interface rate 0011 data, 12.0 kbit/s radio interface rate 0100 data, 6.0 kbit/s radio interface rate 0101 data, 3.6 kbit/s radio interface rate 1111 is reserved All other values indicate that no information is provided. Bits 8 to 5 are spare. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 111 (GSM 08.08 version 6.5.0 Release 1997) The channel field is coded as follows: Bit 4321 0001 SDCCH 1000 1 Full rate TCH 1001 1 Half rate TCH 1010 2 Full Rate TCHs 1011 3 Full Rate TCHs 1100 4 Full Rate TCHs 1101 5 Full Rate TCHs 1110 6 Full Rate TCHs 1111 7 Full Rate TCHs 0100 8 Full Rate TCHs 0000 is reserved All other values indicate that no information is provided. Bits 8 to 5 are spare.
|
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 │ ├───────────────────────────────────────────────┼────────────┤ │ │octet 3 │ └───────────────────────────────────────────────┴────────────┘ Octet 2 is a binary indication of the length of the rest of the element. Octet 3 is coded as follows: ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬────────────┐ │ 8 7 │ 6 5 4 3 2 1 │ │ ├─────┬─────┼─────┴─────┴─────┴─────┼─────┼─────┼────────────┤ │ │ RXLEV-NCELL │octet 3 │ └─────┴─────┴───────────────────────┴─────┴─────┴────────────┘ Bit 8 to 6 is spare, set to 0 Bit 5 to 1 is the RXLEV-NCELL field. The RXLEV-NCELL field is coded as the binary representation of a value N. N corresponds according to the mapping defined in TS. GSM 05.08 to the received signal strength on the target cell.
|
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 │ │ ├─────┴─────┴─────┴─────┴─────┴─────┴─────┴─────┼────────────┤ │ Element identifier │octet 1 │ ├───────────────────────┬───────────────────────┼────────────┤ │ Length │octet 2 │ ├───────────────────────┬───────────────────────┼────────────┤ │ Gb interface TLLI IEI │octet 3 │ ├───────────────────────┬───────────────────────┼────────────┤ │ Length of TLLI │octet 4 │ ├───────────────────────┬───────────────────────┼────────────┤ │ TLLI │oct 5 - 5+m│ ├───────────────────────┬───────────────────────┼────────────┤ │ Gb interface RAI IEI │octet 6+m │ ├───────────────────────┬───────────────────────┼────────────┤ │ Length of RAI │octet 7+m │ ├───────────────────────┬───────────────────────┼────────────┤ │ RAI │oct 7+m - n│ ├───────────────────────┬───────────────────────┼────────────┤ │ Gb interface SRN IEI │octet n+1 │ ├───────────────────────┬───────────────────────┼────────────┤ │ Length of SRN │octet n+2 │ ├───────────────────────┬───────────────────────┼────────────┤ │ Suspend reference number │oct n+3 -p │ └───────────────────────┴───────────────────────┴────────────┘ The coding of the fields are not relevant to GSM 08.08
|
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 successful handover information O&M T10 Time to return of ASSIGNMENT COMPLETE or ASSIGNMENT FAILURE from MS (note) O&M T11 Maximum allowed queuing time for assignment O&M T12 Time to receipt of RESET CIRCUIT ACKNOWLEDGE at the MSC O&M T13 Reset guard period at the BSS O&M T16 Time to receipt of RESET ACKNOWLEDGE at the MSC O&M T17 Overload timer in the BSS, see 3.1.12.1 O&M T18 Overload timer in the BSS, see 3.1.12.1 O&M T19 Time to receipt of RESET CIRCUIT ACKNOWLEDGE at the BSS O&M T20 Time to receipt of CIRCUIT GROUP BLOCKING ACKNOWLEDGE at the BSS.. O&M T21 Time to receipt of BLOCKING ACKNOWLEDGE at the MSC O&M T22 Time to receipt of CIRCUIT GROUP BLOCKING ACKNOWLEDGE at the MSC O&M Tqho Maximum allowed queuing time for handover O&M NOTE: T10 is not the same as T3107 as defined in GSM 04.08.
|
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 Application Part.
|
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 Application Part, this is the subsystem that contains the process dealing with radio resource control and management known as the Base Station System Management Application Part (BSSMAP) and transparent transfer of call control and mobility management information known as the Direct Transfer Application Part (DTAP). The BSSAPs at the BSS and the MSC are connected by means of SCCP connections. DTAP The DTAP, Direct Transfer Application Part is a process which allows the direct transfer of messages between individual MSs and the MSC with no interpretation of layer 3 information at the BSS. BSSMAP Base Station System Management Application Part. This is the process within the BSS that controls radio resources in response to instructions from the MSC. INTERNAL HANDOVER An internal handover is a handover which takes place between channels on a cell or cells controlled by a single BSS. This handover operates without reference to the MSC (although the MSC will be informed on completion). Handovers of this type in one cell are called internal intra cell handovers and between cells are called internal inter cell handovers. Handovers between channels on the same cell or between cells on the same BSS which are controlled by the MSC are external handovers and use identical procedures to those for inter-BSS handovers. DIRECTED RETRY Directed Retry is the process of assigning a Mobile Station to a TCH in a cell other than the serving cell, e.g. in situations of congestion. It is triggered by the assignment procedure and employs internal or external handover procedures. VGCS/VBS VGCS/VBS call controlling SCCP connection: The VGCS/VBS call controlling SCCP connection is an SCCP connection which supports the signalling for call SETUP of a VGCS/VBS call. One of these connections is needed to support each instance of a VGCS/VBS call within a BSS. VGCS/VBS resource controlling SCCP connection: The VGCS/VBS resource controlling SCCP connection is an SCCP connection which supports the allocation of resources for a VGCS/VBS call. One or more of these connections is needed to support each instance of a VGCS/VBS call. The eact number of these SCCP connections is equal to the number of cells to which the VGCS/VBS call is to be supported. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 114 (GSM 08.08 version 6.5.0 Release 1997)
|
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 candidate enquiry 14. Flow control 15. Paging 16. Overview of handover procedure between two BSS’s on the same MSC 17. Cipher mode control 18. SAPI “n” rejection 19. Load indication 20 SUCCESSFUL UPLINK ALLOCATION 21 UNSUCCESSFUL UPLINK ALLOCATION 22 UPLINK RELEASE INDICATION 23 UPLINK SEIZE COMMAND 24 UPLINK RELEASE COMMAND 25 Blocking of terrestrial circuits, MSC initiated 26 Circuit re-selection ETSI ETSI TS 100 590 V6.5.0 (2000-06) 115 (GSM 08.08 version 6.5.0 Release 1997) BSS-SIDE A-INTERFACE MSC-SIDE ││ ──────────────────┐ ││ To other processes │ ││ within the BSS │ ││ ┌────── │ ││ │To other ───────┐ │ ││ │applications To air │ │ ││ │eg. call control interface│ │ ││ │ transmission │ ││ │ ┌────────────── equipment│ │ ││ │ │Operation and ┌──────│──────────│────┐ ││ ┌──────────┴───────────┐ │Maintenance │BSSAP│ │ │ ││ │BSSAP │ │information │┌────┴─┐ ┌──┴──┐│ ││ │┌──────┐ ┌─────┐│ │to PLMN ││DTAP │ │BSS ││ ││ ││DTAP │ │BSS ││ │O&M centre ││ │ │MAP ││┌────────┐ ││ ││ │ │MAP ││ ┌─┴─────────────┐ │└───┬──┘ └──┬──┘││ │ ││ │└───┬──┘ └──┬──┘│ │ │ │┌───┴───────────┴──┐││ │ ││ │┌───┴───────────┴──┐│ │ │ ││ Distribution │││BSS │ ││ ││ Distribution ││ │ BSS │ ││ Function │││OMAP │ ││ ││ Function ││ │ OMAP │ │└──────────────────┘││ │ ││ │└──────────────────┘│ │ │ ├──────────────────────┴┴────────┤ ││ ├──────────────────────┤ ├───────────────┤ │ S C C P │ ││ │ S C C P │ │ S C C P │To other │ │ ││ │ │ │ │users of ├────────────────────────────────┤ ││ ├──────────────────────┤ ├───────────────┤SCCP and │ M T P │ ││ │ M T P │ │ M T P │MTP │ │ ││ │ │ │ │ ├────────────────────────────────┴───┼┼───┴──────────────────────┴──┴───────────────┤ │ P H Y S I C A L ││ L A Y E R │ │ ││ │ └────────────────────────────────────┼┼─────────────────────────────────────────────┘ ││ ││ Terminology: DTAP - Direct Transfer Application Part BSSMAP - BSS Management Application Part BSS OMAP - BSS Operation and Maintenance Application Part SCCP - Signalling Connection and Control Part MTP - Message Transfer Part BSS - Base Station System MSC - Mobile services Switching Centre NOTE: X.25 can be used for transferring O and M information Figure 1: SIGNALLING PROTOCOL REFERENCE MODEL ASSIGNMENT MS BSS MSC │ │ASSIGNMENT │ │ │REQUEST │ │ ASSIGNMENT │<────────────────┤ │ COMMAND │ │ │<────────────────┤ │ │ │ │ │ ASSIGNMENT │ │ │ COMPLETE │ │ ├────────────────> │ASSIGNMENT │ │ │COMPLETE │ │ ├────────────────> │ │ │ │ │ │ │ │ │ │ FIG 2 HANDOVER EXECUTION MS BSS MSC │ │ HANDOVER │ │ │ COMMAND │ │ HANDOVER │<────────────────┤ │ COMMAND │ note │ │<────────────────┤ │ │ │ │ │ │ CLEAR COMMAND │ │ │<────────────────┤ │ │ │ │ │ │ │ │ │ FIG 3 NOTE: A timer T8 is started to protect the overall procedure ETSI ETSI TS 100 590 V6.5.0 (2000-06) 116 (GSM 08.08 version 6.5.0 Release 1997) HANDOVER REQUIRED INDICATION MS BSS MSC │ │ │ │ │HANDOVER REQUIRED│ │ + ├────────────────> │ │ | │ │ │ T7 │ │ │ | │HANDOVER REQUIRED│ │ + ├────────────────> │ │ │ │ │ │ │ │ │HANDOVER COMMAND │ │ │<────────┤ │ │ │ │ │ │ FIG 4 HANDOVER RESOURCE ALLOCATION MS BSS MSC │ │ │ │ │ HANDOVER │ │ │ REQUEST │ │ │<────────────────┤ │ │ │ │ │ HANDOVER │ │ │ REQUEST │ │ │ ACKNOWLEDGE │ │ ├────────────────> │ │ (HANDOVER │ │ │ COMPLETE) │ │ ├────────────────> │ HANDOVER │ │ │ COMPLETE │ │ ├────────────────> │ │ │ note │ │ │ │ │ │ │ FIG 5 NOTE: The instant of generation of the Handover Complete is described in the text of Technical Specification GSM 08.08 RELEASE MS BSS MSC │ │ CLEAR │ │ │ COMMAND │ │ │<────────────────┤ │ │ CLEAR │ │ │ COMPLETE │ │ ├────────────────> │ │ CHAN. RELEASE │ │ │<────────────────┤ │ │ │ │ │ L2 msg (DISC) │ │ ├────────────────> │ │ │ │ │ │ L2 msg (UA) │ │ │<────────────────┤ │ │ │ │ FIG 6 ETSI ETSI TS 100 590 V6.5.0 (2000-06) 117 (GSM 08.08 version 6.5.0 Release 1997) RELASE DUE TO REASON AT THE BSS MS BSS MSC │ │ CLEAR │ │ │ REQUEST │ │ ├────────────────> │ │ │ │ │ │ CLEAR │ │ │ COMMAND │ │ │<────────────────┤ │ │ │ │ │ CLEAR │ │ │ COMPLETE │ │ ├────────────────> │ │ CHAN. RELEASE │ │ │<────────────────┤ │ │ │ │ │ L2 msg (DISC) │ │ ├────────────────> │ │ │ │ │ │ L2 msg (UA) │ │ │<────────────────┤ │ │ │ │ FIG 7 CLASSMARK UPDATING MS BSS MSC │ │ │ │ CLASSMARK │ │ │ CHANGE │ │ ├────────────────> │ CLASSMARK │ │ │ UPDATE │ │ ├────────────────> │ │ │ │ │ │ │ │ │ │ FIG 9 BLOCKING OF TERRESTRIAL CIRCUITS MS BSS MSC │ │ │ │ │ BLOCK │ │ ├────────────────> │ │ │ │ │ │ │ │ │ BLOCK ACK │ │ │<────────────────┤ │ │ │ │ │ │ │ │ UNBLOCK │ │ ├────────────────> │ │ │ │ │ │ │ │ │ UNBLOCK ACK │ │ │<────────────────┤ │ │ │ │ │ │ │ │ │ FIG 10 ETSI ETSI TS 100 590 V6.5.0 (2000-06) 118 (GSM 08.08 version 6.5.0 Release 1997) RESET MS BSS MSC │ │ │ │ │ RESET │ │ │<────────────────┤ │ │ │ │ T13 │ │ │ │ RESET ACK │ │ ├────────────────> │ │ │ │ │ │ │ │ │ RESET │ │ ├────────────────> │ │ │ │ │ │ T2 │ │ │ RESET ACK │ │ │<────────────────┤ │ │ │ │ │ │ │ │ │ FIG 11 RESOURCE INDICATION MS BSS MSC │ │ │ │ │ RESOURCE │ │ │ REQUEST │ │ │<────────────────┤ │ │ │ │ │ RESOURCE │ │ │ INDICATION │ │ + ├────────────────> │ │ │ │ │ T │ RESOURCE │ │ │ INDICATION │ │ + ├────────────────> │ │ │ │ │ │ │ FIG 12 HANDOVER CANDIDATE ENQUIRY MS BSS MSC │ │ HANDOVER │ │ │ CANDIDATE │ │ │ ENQUIRY │ │ │<────────────────┤ │ │ │ │ ┌─│HANDOVER REQUIRED│ │ │ ├────────────────> │ │ │ │ │ │ │ │HANDOVER REQUIRED│ │ │ ├────────────────> │ │ note ─┤ │ │ │ │ │ : : : : │ │ │ │ │ │ │ │HANDOVER REQUIRED│ │ │ ├────────────────> │ │ └─│ HANDOVER │ │ │ CANDIDATE │ │ │ RESPONSE │ │ ├────────────────> │ │ │ │ FIG 13 NOTE: Receipt of the Handover Candidate Enquiry Message causes the generation of a Handover Required message for each of candidate MS. These are sent as connection oriented messages. When all Handover Required messages have been generated a global Handover Candidate Response message is returned. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 119 (GSM 08.08 version 6.5.0 Release 1997) FLOW CONTROL MS BSS MSC │ │ │ │ │ OVERLOAD │ │ │<────────────────┤ │ (MSC │ │ │ overload)│ OVERLOAD │ │ │<────────────────┤ │ │ │ -------------------------------------------- │ │ OVERLOAD │ │ ├────────────────> │ │ (BSS │ │ │ overload)│ OVERLOAD │ │ ├────────────────> │ │ │ │ FIG 14 PAGING MS BSS MSC │ │ │ │ │ PAGING │ │ PAGING │<────────────────┤ │ REQUEST │ │ │ TYPE 1, 2, 3 │ │ │<────────────────┤ │ │ │ │ │ │ PAGING │ │ PAGING │<────────────────┤ │ REQUEST │ │ │ TYPE 1, 2, 3 │ │ │<────────────────┤ │ │ │ │ FIG 15 OVERVIEW OF THE HANDOVER PROCEDURE BETWEEN TWO BSS'S ON THE SAME MSC. MS BSS MSC BSS MS │ │ │ │ │ ├──────────────────┤ │ │ │ │■■■■■■■■■■■■■■■■■■│ HANDOVER │ │ │ │■Measurement■■■■■■│ REQUIRED │ │ │ │■Information■■■■■■├────────────────> │ HANDOVER │ │ │■Reported■■■■■■■■■│ │ REQUEST │ │ │■Continuously■■■■■│ ├────────────────> │ │ │■From Mobile■■■■■■│ │ │ │ │■■■■■■■■■■■■■■■■■■│ │ HANDOVER │ │ │■■■■■■■■■■■■■■■■■■│ │ REQUEST ACK │ │ │■■■■■■■■■■■■■■■■■■│ HANDOVER │<────────────────┤ │ │■■■■■■■■■■■■■■■■■■│ COMMAND │ │ │ ├──────────────────┤<────────────────┤ │ │ │ │ │ │ │ │ HANDOVER │ │ │ │ │ COMMAND │ │ │ HANDOVER │ │<────────────────┤ │ │ ACCESS │ │ │ │ │<────────────────┤ │ │ │ HANDOVER │ │ │ │ │ DETECT │ │ │ │ │<────────────────┤ │ │ │ │ │ HANDOVER │ │ │ │ │ COMPLETE │ │ │ │ HANDOVER │<────────────────┤ │ │ │ COMPLETE ├──────────────────┤ │ │ CLEAR │<────────────────┤■■Measurement■■■■■│ │ │ COMMAND │ │■■Information■■■■■│ │ │<────────────────┤ note │■■Reported■■■■■■■■│ │ │ │ │■■Continuously■■■■│ │ │ CLEAR │ │■■From Mobile■■■■■│ │ │ COMPLETE │ │■■■■■■■■■■■■■■■■■■│ │ ├────────────────> │ │■■■■■■■■■■■■■■■■■■│ │ │ │ │■■■■■■■■■■■■■■■■■■│ │ │ │ │■■■■■■■■■■■■■■■■■■│ │ │ │ │■■■■■■■■■■■■■■■■■■│ FIG 16 NOTE: The Handover Complete message can be sent as soon as the BSS is certain that the MS has successfully been captured. ETSI ETSI TS 100 590 V6.5.0 (2000-06) 120 (GSM 08.08 version 6.5.0 Release 1997) CIPHER MODE CONTROL MS BSS MSC │ │ │ │ │ │ │ │ CIPHER │ │ │ MODE │ │ │ COMMAND │ │ CIPHER │<────────────────┤ │ MODE │ │ │ COMMAND │ │ │<────────────────┤ │ │ │ │ │ CIPHER │ │ │ MODE │ │ │ COMPLETE │ │ ├────────────────> │ CIPHER │ │ │ MODE │ │ │ COMPLETE │ │ ├────────────────> │ │ │ │ │ │ │ │ │ │ FIG 17 SAPI "n" REJECTION MS BSS MSC │ │ │ │ │ DTAP MESSAGE │ │ │SAPI in DLCI <> 0│ │ │<────────────────┤ │ note │ │ │ │ │ │ │ SAPI "n" │ │ │ REJECT │ │ ├────────────────> │ │ │ │ │ │ │ │ │ │ FIG 18 NOTE: The BSS or MS is not equipped for the SAPI request. LOAD INDICATION BSS MSC BSS │ │ │ │ LOAD │ │ │ INDICATION │ │ ├────────────────> │ │ │ │ LOAD │ │ │ INDICATION │ │ ├────────────────> │ │ │ │ │ LOAD │ │ │ INDICATION │ │ ├────────────────> │ │ │ │ LOAD │ │ │ INDICATION │ │ ├────────────────> │ │ │ │ FIG 19 ETSI ETSI TS 100 590 V6.5.0 (2000-06) 121 (GSM 08.08 version 6.5.0 Release 1997) SUCCESSFUL UPLINK ALLOCATION MS BSS MSC │ │ │ │ UPLINK FREE│ │ │<--------------- │ │ │ UPLINK FREE│ │ │<--------------- │ │ │UPLINK │UPLINK │ │ACCESS │REQUEST │ │----------------> │----------------> │ │ VGCS ACCESS│ │ │ GRANT│ │ │<--------------- │ │ │ BUSY│ │ │<--------------- │ │ │ │ │ │L2msg (SABM │ │ │(Talk Ind))-----> │ UPLINK│ │ L2msg (UA│ REQ ACK│ │<-----(Talk Ind))│<----------------│ │ │UPLINK │ │ │REQ CNF (Talk Ind)│ │ │----------------> │ FIG 20 UNSUCCESSFUL UPLINK ALLOCATION MS BSS MSC │ │ │ │ UPLINK FREE│ │ │<--------------- │ │ │ UPLINK FREE│ │ │<--------------- │ │ │UPLINK │UPLINK │ │ACCESS │REQUEST │ │----------------> │----------------> │ │ VGCS ACCESS│ │ │ GRANT│ │ │<--------------- │ │ │ BUSY│ │ │<--------------- │ │ │ │ │ │L2msg (SABM │ │ │(Talk Ind))-----> │ UPLINK│ │ L2msg (UA│ REJ CMD│ │<-----(Talk Ind))│<----------------│ │<-------- DISC/DM│ │ │ │ │ FIG 21 UPLINK RELEASE INDICATION MS BSS MSC │ │ │ │UPLINK │UPLINK │ │RELEASE │RELEASE IND │ │----------------> │----------------> │ FIG 22 UPLINK SEIZE COMMAND MS BSS MSC │ │ │ │ UPLINK FREE│ │ │<--------------- │ UPLINK│ │ UPLINK FREE│ SEIZE CMD│ │<--------------- │<----------------│ │ UPLINK BUSY│ │ │<--------------- │ │ FIG 23 ETSI ETSI TS 100 590 V6.5.0 (2000-06) 122 (GSM 08.08 version 6.5.0 Release 1997) UPLINK RELEASE COMMAND MS BSS MSC │ │ │ │ │ UPLINK│ │ │ RELEASE CMD│ │ │<----------------│ │ UPLINK FREE│ │ │<--------------- │ │ │ UPLINK FREE│ │ │<--------------- │ │ FIG 24 BLOCKING OF TERRESTRIAL CIRCUITS, MSC INITIATED MS BSS MSC │ │ │ │ │ BLOCK │ │ │<────────────────┤ │ │ │ │ │ │ │ │ BLOCK ACK │ │ ├────────────────> │ │ │ │ │ │ │ │ │ UNBLOCK │ │ │<────────────────┤ │ │ │ │ │ │ │ │ UNBLOCK ACK │ │ ├────────────────> │ │ │ │ │ │ │ │ │ │ FIG 25 CIRCUIT RE-SELECTION MS BSS MSC │ │ │ │ │ CHANGE CIRCUIT │ │ ├<───────────────- │ │ │ │ │ │ │ │ │ CHANGE CIRCUIT │ │ │ ACKNOWLEDGE │ │ │────────────────>┤ │ │ │ │ │ │ │ │ │ FIG 26 ETSI ETSI TS 100 590 V6.5.0 (2000-06) 123 (GSM 08.08 version 6.5.0 Release 1997) Annex A (informative): Change Request History History November 1995 Creation of Version 5.0.0 (Version 4.10.0 + AR08.08-031) December 1995 Publication of Version 5.0.0 January 1996 (CR 08.08-A036 r 2, A037, A038, A039, A042, A046) March 1996 Publication of Version 5.1.0 April 1996 Creation of Version 5.2.0 (Version 5.1.0 + CR 08.08-A022 r9+A027 r7+A029 r5+A030 r5) May 1996 Publication of Version 5.2.0 June 1996 Creation of Version 5.3.0 (Version 5.2.0 + CR 08.08-A050 r1, A051 r1, A052 r1) July 1996 Publication of Version 5.3.0 November 1996 Creation of Version 5.4.0 (Version 5.3.0 + CR 08.08-A054, A055, A058) November 1996 Publication of Version 5.4.0 July 1997 Creation of Version 5.5.0 (Version 5.4.0 + CR 08.08-A056r3, A057r4, A059, A061r2, A062r4, A064, A065, A066r1, A067r2, A068r1 August 1997 Creation of Version 5.6.0 (Version 5.5.0 + CR 08.08-A060r6, A069r4, A071r1, A072r2, A076r1, A077, A078r1) August 1997 Creation of Version 5.6.1 August 1997 Creation of Version 5.6.2 August 1997 Creation of Version 5.6.3 (Completing the predefined circuit pools list from A077) September 1997 Publication of Version 5.6.3 October 1997 Inclusion of CRs approved at SMG#23 A074r3, B, Speech versions compatibility A080r1, A, Wrong references to GSM 04.08 A083r1, C, Removal of layer 3 header info A084r1, F, ASCI clean-up A087, F, Channel type IE corrections A088/A089, F, Length of assignment requirement info element R96/97 (CRs identical) January 1998 Inclusion of CRs A090 Correction of Circuit Pool Description (Release 96), and A092 Clean-up for work item Improved Transcoder Handling (Release 96) approved at SMG#24 January 1998 Publication of Version 5.8.0 April 1998 Inclusion of R96 and R97 CRs approved at SMG#25 A091r1 Definition of the IE Group Call Reference A096 Correction of the unequipped circuit procedure A097r1 A interface interworking June 1998 Inclusion of R97 CRs approved at SMG#26 A107 Addition of initial messages for ASCI A108 Error messages for ASCI A109 Unequipped circuit procedure for ASCI messages A110 VBS/VGCS assignment request message clarification October 1998 Inclusion of CRs approved at SMG#27 A115 BSS to BSS information A116 Pre-emption confirmation by serving BSC A117 Radio information of target cell for external HO A118 Current channel type 2 introduction A119 A-interface signalling for GPRS suspend/resume February 1999 Inclusion of CRs approved at SMG#28 A120 Definition of IEI for the Old BSS to New BSS Information element July 1999 Inclusion of CRs approved at SMG #29 A136 Correction of Uplink Release and Uplink Seize procedure A142 VGCS/VBS assignment procedure A148 Uplink release procedure April 2000 Version 6.5.0: Inclusion of CRs approved at SMG #31bis A196 Moving NOTIFICATION RESPONSE from MM to GSM RR ETSI ETSI TS 100 590 V6.5.0 (2000-06) 124 (GSM 08.08 version 6.5.0 Release 1997) History Document history V6.1.0 July 1998 Publication V6.2.0 November 1998 Publication V6.3.0 February 1999 Publication V6.4.0 July 1999 Publication V6.5.0 June 2000 Publication
|
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, which is compatible with a full MTP. The SCCP is used to provide a referencing mechanism to identify a particular transaction relating to for instance a particular call. Clauses 5-7 identify the SCCP subset that should be used between a BSS and an MSC. The SCCP can also be used to enhance the message routing for (for instance) operations and maintenance information.
|
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. • For a non-specific reference, the latest version applies. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. • For this Release 1998 document, references to GSM documents are for Release 1998 versions (version 7.x.y). [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] GSM 02.01: "Digital cellular telecommunications system (Phase 2+); Principles of telecommunications services supported by a GSM Public Land Mobile Network (PLMN)". [3] GSM 02.02 : "Digital cellular telecommunications system (Phase 2+); Bearer Services (BS) supported by a GSM Public Land Mobile Network (PLMN)". [4] GSM 02.03 : "Digital cellular telecommunications system (Phase 2+); Teleservices supported by a GSM Public Land Mobile Network (PLMN)". [5] GSM 02.04 : "Digital cellular telecommunications system (Phase 2+); General on supplementary services". [6] GSM 02.06 : "Digital cellular telecommunications system (Phase 2+); Types of Mobile Stations (MS)". [7] GSM 02.07 : "Digital cellular telecommunications system (Phase 2+); Mobile Stations (MS) features". [8] GSM 02.09 : "Digital cellular telecommunications system (Phase 2+); Security aspects". [9] GSM 02.11 : "Digital cellular telecommunications system (Phase 2+); Service accessibility". [10] GSM 02.16: "Digital cellular telecommunications system (Phase 2+); International Mobile station Equipment Identities (IMEI)". [11] GSM 02.17 : "Digital cellular telecommunications system (Phase 2+); Subscriber Identity Modules (SIM) Functional characteristics". [12] GSM 02.24 : "Digital cellular telecommunications system (Phase 2+); Description of Charge Advice Information (CAI)". ETSI 7 ETSI TS 100 589 V7.0.1 (1999-07) (GSM 08.06 version 7.0.1 Release1998) [13] GSM 02.30 : "Digital cellular telecommunications system (Phase 2+); Man-Machine Interface (MMI) of the Mobile Station (MS)". [14] GSM 02.40: "Digital cellular telecommunications system (Phase 2+); Procedures for call progress indications". [15] GSM 02.41: "Digital cellular telecommunications system (Phase 2+); Operator determined barring". [16] GSM 02.81: "Digital cellular telecommunications system (Phase 2+); Line identification Supplementary Services - Stage 1". [17] GSM 02.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) Supplementary Services - Stage 1". [18] GSM 02.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) Supplementary Services - Stage 1". [19] GSM 02.84: "Digital cellular telecommunications system (Phase 2+); MultiParty (MPTY) Supplementary Services - Stage 1". [20] GSM 02.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) Supplementary Services - Stage 1". [21] GSM 02.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) Supplementary Services - Stage 1". [22] GSM 02.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) Supplementary Services - Stage 1". [23] GSM 04.01: "Digital cellular telecommunications system (Phase 2+); Mobile Station - Base Station System (MS - BSS) interface; General aspects and principles". [24] GSM 04.02: "Digital cellular telecommunications system (Phase 2+); GSM Public Land Mobile Network (PLMN) access reference configuration". [25] GSM 04.03: "Digital cellular telecommunications system (Phase 2+); Mobile Station - Base Station System (MS - BSS) interface; Channel structures and access capabilities". [26] GSM 04.04 : "Digital cellular telecommunications system (Phase 2+); layer 1; General requirements". [27] GSM 04.05 : "Digital cellular telecommunications system (Phase 2+); Data Link (DL) layer; General aspects". [28] GSM 04.06 : "Digital cellular telecommunications system (Phase 2+); Mobile Station - Base Station System (MS - BSS) interface; Data Link (DL) layer specification". [29] GSM 04.07 : "Digital cellular telecommunications system (Phase 2+); Mobile radio interface signalling layer 3; General aspects". [30] GSM 04.08 : "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". [31] GSM 04.10 : "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3; Supplementary services specification; General aspects". [32] GSM 04.11 : "Digital cellular telecommunications system (Phase 2+); Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface". [33] GSM 04.12 : "Digital cellular telecommunications system (Phase 2+); Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface". [34] GSM 04.13 : "Digital cellular telecommunications system (Phase 2+); Performance requirements on mobile radio interface". ETSI ETSI TS 100 589 V7.0.1 (1999-07) 8 (GSM 08.06 version 7.0.1 Release1998) [35] GSM 04.21 : "Digital cellular telecommunications system (Phase 2+); Rate adaption on the Mobile Station - Base Station System (MS - BSS) interface". [36] GSM 04.22 : "Digital cellular telecommunications system (Phase 2+); Radio Link Protocol (RLP) for data and telematic services on the Mobile Station - Base Station System (MS - BSS) interface and the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". [37] GSM 04.80 : "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 supplementary services specification; Formats and coding". [38] GSM 04.81 : "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 3". [39] GSM 04.82 : "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 3". [40] GSM 04.83 : "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 3". [41] GSM 04.84 : "Digital cellular telecommunications system (Phase 2+); MultiParty (MPTY) supplementary services - Stage 3". [42] GSM 04.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 3". [43] GSM 04.86 : "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services - Stage 3". [44] GSM 04.88 : "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 3". [45] GSM 04.90 : "Digital cellular telecommunications system (Phase 2+); Unstructured Supplementary Service Data ( USSD) - Stage 3". [46] GSM 08.08: "Digital cellular telecommunications system (Phase 2+); Mobile Switching Centre - Base Station System (MSC - BSS) interface; Layer 3 specification". [47] GSM 12.00 (ETS 300 612-1): "Digital cellular telecommunications system (Phase 2+); Objectives and structure of Network Management (NM)". [48] GSM 12.01 (ETS 300 612-2): "Digital cellular telecommunications system (Phase 2+); Common aspects of GSM Network Management (NM)". [49] GSM 12.02 : "Digital cellular telecommunications system (Phase 2+); Subscriber, Mobile Equipment (ME) and services data administration". [50] GSM 12.03 : "Digital cellular telecommunications system (Phase 2+); Security management". [51] GSM 12.04 : "Digital cellular telecommunications system (Phase 2+); Performance data measurements". [52] GSM 12.05 : "Digital cellular telecommunications system (Phase 2+); Subscriber related event and call data". [53] GSM 12.06 : "Digital cellular telecommunications system (Phase 2+); GSM Network change control". [54] GSM 12.11 : "Digital cellular telecommunications system (Phase 2+); Maintenance of the Base Station System (BSS)". [55] GSM 12.20 : "Digital cellular telecommunications system (Phase 2+); Network Management (NM) procedures and messages". [56] GSM 12.21 : "Digital cellular telecommunications system (Phase 2+); Network Management (NM) procedures and message on the A-bis interface". ETSI 9 ETSI TS 100 589 V7.0.1 (1999-07) (GSM 08.06 version 7.0.1 Release1998) [57] GSM 12.22 : "Digital cellular telecommunications system (Phase 2+); Interworking of GSM Network Management (NM) procedures and messages at the Base Station Controller (BSC)". [58] CCITT Recommendation Q.702: "Specifications of Signalling System No. 7 - Signalling data link". [59] CCITT Recommendation Q.703: "Signalling link". [60] CCITT Recommendation Q.704: "Signalling network functions and messages". [61] CCITT Recommendation Q.707: "Specifications of Signalling System No. 7 - Testing and maintenance". [62] CCITT Recommendation Q.711: "Functional description of the signalling connection control part". [63] CCITT Recommendation Q.712: "Definition and function of SCCP messages". [64] CCITT Recommendation Q.713: "SCCP formats and codes". [65] CCITT Recommendation Q.714: "Signalling connection control part procedures". [66] GSM 03.03: "Digital cellular telecommunications system (Phase 2+); Numbering, addressing and identification". [67] ANSI T1.110-1992 - SS7 General Information [68] ANSI T1.111-1996 - Signalling System Number 7 (SS7) – Message Transfer Part (MTP) [69] ANSI T1.112-1996 - Signalling System Number 7 (SS7) - Signalling Connection Control Part (SCCP). [70] IS-104 Personal Communications Service Descriptions for 1800 MHz
|
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 use signalling at 56 kbits/s). The output bit rate is 1.544 Mbits/s. (A frame consists of 193 bits, (8 * 24) + 1, as one bit is used for synchronization. The frame repeats 8,000 times per second.).
|
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 MTP. b) The Technical Specification defines the interface at the 64 kbits/s boundary to the BSS or MSC and applies primarily for digital access arrangements, the use of analogue arrangements isan option for PLMN operator. Also, the Technical Specification defines the interface at the 56 kbits/s boundary to the BSS or MSC for T1 links. ETSI ETSI TS 100 589 V7.0.1 (1999-07) 10 (GSM 08.06 version 7.0.1 Release1998) c) The security of signalling links is a PLMN operator concern , however it is recommended that in the case where more than one multiplex system is required and security reasons dictate the use of a multiple link linkset, then each signalling link should be assigned in a different multiplex system. It is however noted that this is of little benefit if diversity of routing of the multiplexes is not used. d) For initial implementations only the associated mode of signalling may be applicable at the BSS. Future evolution or economic reasons applicable to the interface may however make the use of STP working at the BSS attractive, in which case some of the simplifications in this paper will not apply. e) A variety of information types may be supported by the signalling system, e.g. relating to circuit switched call control and packet communication. These are fully defined in the service series of Technical Specifications (the GSM 02.xx series and in [70] for PCS 1900). f) For E1 link usage, the CCITT recommendations concerning the MTP shall be taken as being requirements unless covered by a statement in this Technical Specification. For T1 link usage, the ANSI recommendations concerning the MTP [68] shall be taken as being requirements unless covered by a statement in this Technical Specification. ETSI 11 ETSI TS 100 589 V7.0.1 (1999-07) (GSM 08.06 version 7.0.1 Release1998)
|
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 Technical Specification. The functions are specified in ANSI T1.111 [68] for T1 links. c) The additional interface functions required for the proper operation of the layer 3 control functions in combination with the Message Transfer Part functions, is specified in clause 4 of this Technical Specification.
|
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 be applied for the MSC to BSS signalling, see subclauses 3.2 to 3.4. Some form of policing could be included at the MSC in order to ensure that no signalling messages received from the BSS can be routed further than the MSC if an administration requires. This is necessary to prevent fraudulent use of the signalling network for implementations of the GSM system. The manner in which this is achieved will be dependent on local agreements or regulation s and system implementations. Where load sharing is used, all messages to do with a given SCCP connection should be passed down a given link.
|
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. using analogue bearers) are a national concern. Q.702 clause 3 Error characteristics and availability are a national concern. Care should be taken as excessive errors could lead to inefficient use of the signalling links. Q.702 clause 5 The standard arrangement will be to derive the signalling link from a 2048 kbits/s digital path. Q.702 clause 6 Only digital signalling data links are relevant. ETSI ETSI TS 100 589 V7.0.1 (1999-07) 12 (GSM 08.06 version 7.0.1 Release1998) The use of analogue bearers to support this interface is considered a national concern. However it should be noted that there will be potential problems with the following areas: - The signalling load may exceed that which can be carried by a single low rate analogue link, this may lead to an excessive number of signalling links and more complex changeover/changeback procedures. - The performance of the analogue lines used to carry the signalling link will have a major impact on the throughput of signalling information that can be achieved. - Message delay may degrade the quality of service.
|
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 of 56/64 kbits/s is assumed. Lower bit rates (e.g. using analogue bearers) are a service provider option. T1.111.2 Section 3 Error Characteristics and Availability Error characteristics and availability are an operator concern. Care should be taken as excessive errors could lead to inefficient use of the signalling link. T1.111.2 Section 5 Digital Signalling Data Link The standard arrangement will be to derive a signalling link from a 1544 kbits/s digital path. T1.111.2 Section 6 Analogue Signalling Data Link Only digital signalling data links are required. The use of Analogue bearers to support this interface is considered a service provider option. However, it should be noted that there will be potential problems with the following areas: • • The signalling load may exceed that which can be carried by a single low rate Analogue link, which may lead to an excessive number of signalling links and more complex changeover/change back procedures. • • The performance of the Analogue lines used to carry the signalling link will have a major impact on the throughput of signalling information that can be achieved. • • Message delay may degrade the quality of service.
|
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 required. Q.703 clause 7 In the initial alignment procedure specified in CCITT Recommendation Q.703, only the emergency proving is applicable for the BSS. Thus, in states 02 and 03 of the initial alignment procedure status indication "N" is not sent from the BSS. The BSS should be capable of recognising status indication "N" if received in order for the alignment procedure to complete. Q.703 clause 8 The processor outage status indicator shall be recognised at the BSS and the procedures defined in CCITT Recommendation Q.703 clause 8 supported. The BSS shall support the generation of the processor outage indication towards the MSC if this is appropriate. Q.703 clause 10 Only the emergency alignment procedures are required.
|
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 required for the A-Interface. T1.111.3 Section 7 Signalling Link Initial Alignment Procedure In the initial alignment procedure, only the emergency proving is required for the BSS. Thus, in states 02 and 03 of the initial alignment procedure status indication "N" is not sent from the BSS. The BSS should be capable of recognizing status indication "N" if received in order for the alignment procedure to complete. T1.113 Section 8 The processor outage status indicator shall be recognised at the BSS and the procedures defined in ANSI standards T1.113 clause 8 supported. The BSS shall support the generation of the processor outage indication towards the MSC if this is appropriate. T1.113 Section 10 Only the emergency alignment procedures are required.
|
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 Release1998) Signalling link management is required. Load sharing is required, and changeover/back between links within a single linkset are required. Q.704 clause 2 Since STP working is not required the discrimination and routing functions of the MTP used for GSM application can be significantly simplified. NOTE: Since the implementation of this interface is intended only for point to point application the routing function within the MTP will be present to select the point code appropriate to the parent MSC. Q.704 subclause 2.2 Routing label Load sharing will be performed on BSS s with more than one signalling link by means of the signalling link selection field (SLS). Q.704 subclause 2.3 Message routing function Load sharing between linksets is not required since there will only be one linkset between BSS and MSC. Q.704 subclause 2.3.5. Either of the two methods of congestion control is acceptable. The most appropriate method is dependent on national CCITT No. 7 implementations. Q.704 subclause 2.4 Message discrimination At the BSS only messages with a correctly checking DPC will be accepted. Others will be discarded. It is recommended that discarding a message because of an incorrectly set point code causes an incident report to be generated. At an MSC (which has the capability of acting as an STP) an administration may decide that each message received from a BSS signalling link is passed through a "screening function" that checks that the DPC of the message is the same as the SP code of the exchange. If that is the case, the message is sent to the normal MTP message handling functions. Otherwise, the message is discarded and an incident report is made. The signalling point code for an BSS may be included in the national signalling point code scheme or in a separate signalling network. In the case where the signalling point code is in the national network the MSC need have only one point code, in the case where the signalling point code is in a separate "PLMN" signalling network, the MSC will be required to have two signalling point codes, one for each network. Q.704 subclause 3.1.3 c) There is no requirement for signalling route management. Q.704 subclause 3.3.1.3 There is no requirement for signalling route management. Q.704 subclause 3.3.2.3 There is no requirement for signalling route management. Q.704 subclause 3.3.3.3 There is no requirement for signalling route management. Q.704 subclause 3.3.4.3 There is no requirement for signalling route management. Q.704 subclause 3.3.5.2 There is no requirement for signalling route management or signalling link blocking initiated by a management system. Q.704 subclause 3.3.6.2 ETSI 15 ETSI TS 100 589 V7.0.1 (1999-07) (GSM 08.06 version 7.0.1 Release1998) There is no requirement for signalling route management or signalling link unblocking initiated by a management system. Q.704 subclause 3.4.1 It should be noted that for point to point working, the signalling route will become unavailable when the associated link set fails. Q.704 subclause 3.4.2 It should be noted that for point to point working, the signalling route will become available when the associated link set is restored. Q.704 subclause 3.4.3 Not applicable. Q.704 subclause 3.5.1 It should be noted that for point to point working the procedures used in connection with signalling route unavailability will be those specified for signalling route set unavailability in CCITT Recommendation Q.704 subclause 10.2.1. Q.704 subclause 3.5.2 It should be noted that for point to point interworking the procedures used in connection with signalling route availability will be those specified for signalling route set availability in CCITT Recommendation Q.704 subclause 10.2.2. Q.704 subclause 3.5.3 Not applicable. Q.704 subclause 3.8.2 There are two acceptable methods of congestion control defined in CCITT Recommendation Q.704, in subclauses 3.6.2.1 a) and b). The most appropriate method is dependent on national CCITT No. 7 implementations. Each administration should specify its congestion threshold setting algorithm and nodal congestion abatement procedures at system procurement. Q.704 subclause 3.8.5.2 The signalling-route-set-congestion-test procedure is not required. Q.704 subclause 4.1.2 Signalling routes are not applicable. Q.704 subclause 4.2 The normal routing situation will be that there are 1 or more signalling links available between a BSS and MSC, these will constitute a link set. They will be run in a load sharing mode and changeover, changeback procedures will be supported between these signalling links. Q.704 subclause 4.3.3. There will be no alternative linkset. Q.704 subclause 4.4.3. Not applicable. Q.704 subclause 4.5. Not applicable. Q.704 subclause 4.6. ETSI ETSI TS 100 589 V7.0.1 (1999-07) 16 (GSM 08.06 version 7.0.1 Release1998) Not applicable. Q.704 subclause 4.7 Not applicable. Q.704 clause 5 Changeover Changeover between link sets is not applicable. Q.704 clause 6 Changeback Changeback between link sets is not applicable. Q.704 clause 7 Forced re-routing is not applicable since there is only one signalling route existing between BSS and MSC. Q.704 clause 8 Not applicable since there is only one signalling route existing between BSS and MSC. Q.704 clause 11 It should be noted that for point to point working the signalling route set will consist of one associated signalling route only. Q.704 clause 12 Signalling link management Only basic link management procedures are applicable. Q.704 subclause 12.3.4 Link set activation Link set normal activation defined in subclause 11.2.4.1 is not applicable. Link set emergency restart at the BSS is used in all cases. Q.704 subclause 13.2 Transfer prohibited The transfer prohibited function is not applicable. At the reception of a TFP message, no action should be taken at the BSS. Q.704 subclause 13.3 Transfer allowed The transfer allowed function is not applicable. At the reception of a TFA-message, no action should be taken at the BSS. Q.704 subclause 13.4 Transfer restricted The transfer restricted function is not applicable. At the reception of the TFR message no action is taken by the BSS. Q.704 subclause 13.5 Signalling-route-set-test The signalling-route-set-test procedure is not applicable. Q.704 subclauses 13.6, 13.7, 13.8 Transfer controlled The transfer controlled function is not applicable. At the reception of TFC message, no action is taken by BSS. Q.704 subclause 13.9 Signalling route-set-congestion-test The signalling route-set-congestion-test function is not applicable. At the reception of signalling-route-set-congestion-test message no action is taken by the BSS. Q.704 subclause 14.2.1 Since all messages are passed using the SCCP, the service indicator will be: ETSI 17 ETSI TS 100 589 V7.0.1 (1999-07) (GSM 08.06 version 7.0.1 Release1998) bits D C B A 0 0 1 1 Q.704 subclause 14.2.2 The sub service field will always be set to one of the following values: bits D C 1 0 national network 1 1 local network Q.704 subclause 14.3 This information for SCCP is defined in CCITT Recommendation Q.713. Q.704 clause 15 The formats and codes listed are only relevant to the messages that are required, i.e. those not excluded in the rest of this recommendation.
|
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 Handling Since STP functionality is not required the discrimination and routing functions of the MTP can be significantly simplified. Note: Since the intent of this interface is point to point routing, the routing function within the MTP will be preset to select the point code appropriate to the parent MSC. T1.111.4 Section 2.2 Routing Label Load sharing will be performed on BSSs with more than one signalling link by means of the Signalling Link Selection (SLS) field. T1.111.4 Section 2.3 Message Routing Function Load sharing between linksets is not required since only one linkset between the BSS and the MSC is required for the A- Interface. T1.111.4 Section 2.4 Message Discrimination It is recommended that discarding a message because of an incorrectly set point code should cause an incident report to be generated. At a MSC the service provider may decide that each message received from an BSS signalling link is passed through a "screening function" that checks that the DPC of the message is the same as the SP code of the exchange. If that is the case, the message is sent to the normal message handling function. Otherwise, the message is discarded and an incident report is generated. The signalling point code for an BSS may be included in the national signalling point code scheme or in a separate signalling network. In the case where the signalling point code is in the national network the MSC need have only one point code, in the case where signalling point code is in a separate PLMN signalling network, the MSC will be required to have two signalling point codes, one for each network. The User Part Unavailable message is not required for the A-Interface. ETSI ETSI TS 100 589 V7.0.1 (1999-07) 18 (GSM 08.06 version 7.0.1 Release1998) T1.111.4 Section 2.3.5. Support of ANSI specific Signalling Link Congestion Control as specified in this sub-clause is required. T1.111.4 Section 3 Signalling Network Management Since the A-Interface utilizes point to point signalling between the BSS and the MSC, Signalling Route Management, including the status of signalling routes, signalling route restricted, signalling route unavailability and availability, is not required. T1.111.4 Section 3.1.3 c) There is no requirement for signalling route management. T1.111.4 Section 3.3.1.3 There is no requirement for signalling route management. T1.111.4 Section 3.3.2.3 There is no requirement for signalling route management. T1.111.4 Section 3.3.3.3 There is no requirement for signalling route management. T1.111.4 Section 3.3.4.3 There is no requirement for signalling route management. T1.111.4 Section 3.3.5.2 There is no requirement for signalling route management or signalling link blocking initiated by a management system. T1.111.4 Section 3.3.6.2 There is no requirement for signalling route management or signalling link unblocking initiated by a management system. T1.111.4 Section 3.4.1 It should be noted that for point to point working, the signalling route will become unavailable when the associated link set fails. T1.111.4 Section 3.4.2 It should be noted that for point to point working, the signalling route will become available when the associated link set is restored. T1.111.4 Section 3.4.3 Not applicable. T1.111.4 Section 3.5.1 It should be noted that for point to point working the procedures used in connection with signalling route unavailability will be those specified for signalling route set unavailability in ANSI standard T1.111.4 section 10.2.1. T1.111.4 Section 3.5.2 It should be noted that for point to point interworking the procedures used in connection with signalling route availability will be those specified for signalling route set availability in ANSI standard T1.111.4 section 10.2.2. T1.111.4 Section 3.5.3 Not applicable. ETSI 19 ETSI TS 100 589 V7.0.1 (1999-07) (GSM 08.06 version 7.0.1 Release1998) T1.111.4 Section 3.8.2 Support of ANSI specific Signalling Link Congestion Control as specified in this sub-clause is required. T1.111.4 Section 3.8.5.2 The signalling-route-set-congestion-test procedure is not required. T1.111.4 Section 4 Signalling Traffic Management Since the A-Interface utilizes point to point signalling between the BSS and the MSC, the Traffic Management procedures supporting signalling routes, including signalling route restricted, signalling route unavailability and availability, are not required. T1.111.4 Section 4.1.2 Signalling routes are not applicable. T1.111.4 Section 4.2 The normal routing situation will be that there are one or more signalling links available between the BSS and the MSC, which will constitute a link set. They will be run in a load sharing mode and changeover, change back procedures will be supported between these signalling links. T1.111.4 Section 4.3.3 Alternative linksets are not required for the A-Interface. T1.111.4 Section 4.4.3 Not Applicable, T1.111.4 Section 4.5 Not Applicable, T1.111.4 Section 4.6 Not Applicable, T1.111.4 Section 4.7 Not Applicable, T1.111.4 Section 5 Changeover The changeover procedure between linksets is not applicable for the A-Interface. T1.111.4 Section 6 Changeback The changeback procedure between linksets is not applicable for the A-Interface. T1.111.4 Section 7 Forced Rerouting Forced rerouting is not applicable for the A-Interface. T1.111.4 Section 8 Controlled Rerouting Controlled rerouting is not applicable for the A-Interface. T1.111.4 Section 9. MTP Restart The MTP Restart procedure is not required for the A-Interface. T1.111.4 Section 11 Signalling Traffic Flow Control The signalling route procedures supporting signalling traffic flow control including signalling-route-unavailability, signalling-route availability and signalling-route-set-congestion are not applicable for the A-Interface. ETSI ETSI TS 100 589 V7.0.1 (1999-07) 20 (GSM 08.06 version 7.0.1 Release1998) T1.111.4 Section 12 Signalling Link Management Only basic link management procedures are required for the A-Interface. T1.111.4 Section 12.3.4 Link set activation Link set normal activation is not applicable. Link set emergency restart at the BSS is used in all cases. T1.111.4 Section 13 Signalling Route Management Signalling route management is not applicable for the A-Interface since it is a point to point connection. No action is required upon reception of a TFP, TFR, TFA, signalling-route-set-test, signalling-route-set-congestion-test or transfer controlled message. T1.111.4 Section 13.3 Transfer allowed The transfer allowed function is not applicable. At the reception of a TFA-message, no action should be taken at the BSS. T1.111.4 Section 13.4 Transfer restricted The transfer restricted function is not applicable. At the reception of the TFR message no action is taken by the BSS. T1.111.4 Section 13.5 Signalling-route-set-test The signalling-route-set-test procedure is not applicable. T1.111.4 Section 13.6, 13.7, 13.8 Transfer controlled The transfer controlled function is not applicable. At the reception of TFC message, no action is taken by BSS. T1.111.4 Section 13.9 Signalling route-set-congestion-test The signalling route-set-congestion-test function is not applicable. At the reception of signalling-route-set-congestion-test message no action is taken by the BSS. T1.111.4 Section 14.2.1 Service Indicator The values for the service indicator shall conform to section 14.2.1 T1.111.4 Section 14.2.2 The sub-service field will always be set to one of the following values: bits DC 1 0 national network 11 local network Note: local network value is not used for PCS 1900 in North America. T1.111.4 Section 14.3 This information for SCCP is defined in ANSI T1.112.3. T1.111.4 Section 15 The formats and codes listed are only relevant to the messages that are required for the A-Interface,i.e. those not excluded in the rest of this recommendation. ETSI 21 ETSI TS 100 589 V7.0.1 (1999-07) (GSM 08.06 version 7.0.1 Release1998)
|
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 in T1.111.7, section 2.2.
|
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 are used) must be maintained for E1 links (T1 links). Only the needs of the BSSAP are taken into account in section 5: the operations and maintenance requirements about SCCP functions are discussed in section 7. These simplifications are applicable to the signalling between BSS and MSC in GSM PLMNs. In order to limit the complexity of the procedures, a BSS exchanges signalling messages only with its MSC, where a protocol conversion may be needed in some cases. Therefore no SCCP translation function is required in the MSC between the national and the local MTP. The Destination Point Code and Subsystem Number allow direct routing by the local SCCP and MTP within the MSC area. Therefore, no SCCP Global Title Translation (GTT) function is required. Several functions of the SCCP are not used on the MSC/BSS interface: error detection, receipt confirmation, flow control. The segmenting/reassembling function shall be used if the total message length exceeds the maximum allowed message length that can be carried by the MTP. For E1 links, the minimum set of SCCP functions which apply are specified in the Blue Book CCITT Recommendations Q.711, Q.712, Q.713 and Q.714, with the qualifications specified in this Recommendation. ETSI ETSI TS 100 589 V7.0.1 (1999-07) 22 (GSM 08.06 version 7.0.1 Release1998) For T1 links, the minimum set of SCCP functions which apply are specified in ANSI T1.112 with the qualifications specified in this Recommendation.
|
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 the N-DATA primitive is not used: - Confirmation request Q.711/Table 6 The following parameter of the N-DISCONNECT primitive is not used: - Responding address Q.711 subclause 2.1.2 Permanent signalling connections: not applicable Q.711/Table 9 The primitive N-NOTICE is not used. Q.711/Table 10 The following parameter of the N-UNITDATA is not used: - Return option Q.711 subclause 4.1.2 Functions for permanent signalling connections: not applicable
|
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 selection T1.112.1 Table 3 The following parameter of the N-DATA primitive is not used: - Confirmation request T1.112.1 Table 6 The following parameter of the N-DISCONNECT primitive is not used: - Responding address T1.112.1 Paragraph 2.1.2 Permanent signalling connections are not applicable T1.112.1 Table 8 The primitive N-NOTICE is not used. T1.112.1 Table 8A The following parameter of the N-UNITDATA is not used: - Return option T1.112.1 Paragraph 4.1.2 Functions for permanent signalling connections are not applicable
|
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 Unit Error (ERR) message is not used: the inconsistent messages of the SCCP protocol are discarded. ETSI ETSI TS 100 589 V7.0.1 (1999-07) 24 (GSM 08.06 version 7.0.1 Release1998) Q.712 subclause 1.13 The Reset Confirm (RSC) message is not used. Q.712 subclause 1.14 The Reset Request (RSR) message is not used. Q.712 subclause 1.16 The Subsystem-Out-Of-Service-Grant (SOG) message is not used. Q.712 subclause 1.17 The Subsystem-Out-Of-Service-Request (SOR) message is not used. Q.712 subclause 1.21 The Unitdata Service (UDTS) message is not used. Q.712 subclause 2.4 The "credit" parameter field is not used for protocol class 2. However the parameter must still be included in the IT message for syntax reasons. Q.712 subclause 2.7 The "error cause" parameter field is not used. Q.712 subclause 2.11 The "receive sequence number" parameter is not used. Q.712 subclause 2.14 The "reset cause" parameter field should not be used. Q.712 subclause 2.16 The "sequencing/segmenting" parameter field is not used for protocol class 2. However the parameter must still be included in the IT message for syntax reasons.
|
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 Protocol Data Unit Error (ERR) message is not used. Inconsistent messages of the SCCP protocol are discarded. T1.112.2 Paragraph 2.13 The Reset Confirm (RSC) message is not used. ETSI 25 ETSI TS 100 589 V7.0.1 (1999-07) (GSM 08.06 version 7.0.1 Release1998) T1.112.2 Paragraph 2.14 The Reset Request (RSR) message is not used. T1.112.2 Paragraph 2.16 The Unitdata Service (UDTS) message is not used. T1.112.2 Paragraph 3.4 The Subsystem-Out-Of-Service-Request (SOR) message is not used. T1.112.2 Paragraph 3.5 The Subsystem-Out-Of-Service-Grant (SOG) message is not used. T1.112.2 Paragraph 4.2 The "credit" parameter field is not used for protocol class 2. However, the parameter must still be included in the Inactivity Test (IT) message for syntax reasons. T1.112.2 Paragraph 4.6 The "error cause" parameter field is not used. T1.112.2 Paragraph 4.10 The "receive sequence number" parameter is not used. T1.112.2 Paragraph 4.13 The "reset cause" parameter field should not be used. T1.112.2 Paragraph 4.16 The "sequencing/segmenting" parameter field is not used for protocol class 2. However, the parameter must still be included in the IT message for syntax reasons.
|
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 address allow the routing of the message. Then the following encoding of the address indicator may be chosen: X1000010. If a non point-to-point network structure is used then the global title may be required. This is a national concern. Q.713 subclause 3.4.2.2 The SSN values used on the MSC - BSS interface are specified in GSM 03.03 Use of alternative values is a national concern. Q.713 subclause 3.4.2.3 ETSI ETSI TS 100 589 V7.0.1 (1999-07) 26 (GSM 08.06 version 7.0.1 Release1998) Global title: refer to CCITT Recommendation Q.713 subclause 3.4. Q.713 subclause 3.6 Protocol class: the classes 1 and 3 are not used. Q.713 subclauses 3.8, 3.9, 3.10, 3.13, 3.14 Parameters not used. Q.713 subclauses 4.8, 4.9, 4.11, 4.12, 4.13, 4.14, 4.15, 4.16 Messages not used. Q.713 subclause 5.1.1 SOR and SOG not needed.
|
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 called party address allow the routing of the message. Then the following encoding of the address indicator may be chosen: X1000001. Separate SSNs are needed to distinguish BSSAP and MAP; the chosen SSNs are network specific and may need to differ from those assigned to other applications (e.g. TCAP applications). T1.112.3 Paragraph 3.4.2.2 Allocation of the subsystem number is an operator concern. T1.112.3 Paragraph 3.4.2.3 T1.112.3 Paragraph 3.4 T1.112.3 Paragraph 3.6 Protocol class: the classes 1 and 3 are not used. T1.112.3 Paragraph 3.8, 3.9, 3.10, 3.13, 3.14 Parameters are not used T1.112.3 Paragraph 4.8, 4.9, 4.11, 4.12, 4.13, 4.14, 4.15, 4.16 Messages are not used T1.112.3 Paragraph 5.1.1 Subsystem-out-of-service-request (SOR) and Subsystem-out-of-service-grant (SOG) are not needed.
|
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 connection sections is a national concern. Q.714 subclause 1.2.1 (b) Not applicable for single connections. Q.714 subclause 2.1 (1.) Global title not used for single connections. Q.714 subclause 2.2.1 Subsystem (SSN) only is present in the called party address for single connections. Q.714 subclause 2.2.2 The addressing information may take the following form in the N-CONNECT request primitive: DPC+SSN (for single connections). Q.714 subclause 2.2.2.2 No SCCP translation function is required for single connections. Q.714 subclause 2.3.1 (3) Not applicable for single connections. Q.714 subclause 2.3.2 (4) Not applicable for single connections. Q.714 subclause 3.1.3 Not applicable: no protocol class and flow control negotiations. Q.714 subclause 3.1.5 Not applicable. Q.714 subclause 3.2.2 Not applicable. Q.714 subclause 3.3.4 Not applicable. Q.714 subclause 3.5.1.2 Not applicable. Q.714 subclause 3.5.2 Not applicable. Q.714 subclauses 3.6, 3.7, 3.9, 3.10 Not applicable. Q.714 subclause 4.2 ETSI ETSI TS 100 589 V7.0.1 (1999-07) 28 (GSM 08.06 version 7.0.1 Release1998) Message return not applicable. Q.714 clause 5 Only those messages and procedures relating to non-replicated subsystems or nodes are required. At the BSS the concerned point will be the parent MSC. The subsystems involved are the BSSAP and the OMAP.
|
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) Not applicable for single connections. T1.112.4 Paragraph 2.1 (1.) Global title is not used for single connections. T1.112.4 Paragraph 2.2.1 Subsystem number (SSN) only is present in the called party address for single connections. T1.112.4 Paragraph 2.2.2 The addressing information may take the following form in the N-CONNECT request primitive: DPC+SSN (for single connections). T1.112.4 Paragraph 2.2.2.2 No SCCP translation function is required for single connections. T1.112.4 Paragraph 2.3.1 (3) Not applicable for single connections. T1.112.4 Paragraph 2.3.2 (4) Not applicable for single connections. T1.112.4 Paragraph 3.1.3 Not applicable. No protocol class and flow control negotiations. T1.112.4 Paragraph 3.1.5 Not applicable. T1.112.4 Paragraph 3.2.2 Not applicable. T1.112.4 Paragraph 3.3.4 Not applicable. T1.112.4 Paragraph 3.5.1.2 ETSI 29 ETSI TS 100 589 V7.0.1 (1999-07) (GSM 08.06 version 7.0.1 Release1998) Not applicable. T1.112.4 Paragraph 3.5.2 Not applicable. T1.112.4 Paragraph 3.6, 3.7, 3.9, 3.10 Not applicable. T1.112.4 Paragraph 4.2 Message return is not applicable. T1.112.4 Paragraph 5 Only those messages and procedures relating to non-replicated subsystems or nodes are required. At the BSS the concerned point will be the parent MSC. The subsystems involved are the BSSAP and the MAP.
|
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 transfer of layer 3 messages. In the case of a voice group or broadcast call there is always one connection per cell involved in the call and one additional connection per BSS for the transmission of layer 3 messages. There is an additional connection for the speaker in a broadcast call or the first speaker in a voice group call up to the point at which the network decides to transfer them to a common channel. Additional connections may also be required for any mobile stations in the voice group or broadcast call which the network decides to place on a dedicated connection. The BSSAP user function is further subdivided into two separate functions: - The Direct Transfer Application sub-Part (DTAP) is used to transfer messages between the MSC and the MS; the layer-3 information in these messages is not interpreted by the BSS. The descriptions of the layer 3 protocols for the MS-MSC information exchange are contained in the 04-series of GSM Technical Specifications. - The BSS Management Application sub-Part (BSSMAP) supports other procedures between the MSC and the BSS related to the MS (resource management, handover control), or to a cell within the BSS, or to the whole BSS. The description of the layer 3 protocol for the BSSMAP information exchange is contained in GSM 08.08. Both connectionless and connection-oriented procedures are used to support the BSSMAP. Rec. GSM 08.08 explains whether connection oriented or connectionless services should be used for each layer 3 procedure. Connection oriented procedures are used to support the DTAP. Section 6.4 deals with the use of connectionless services of the SCCP. A distribution function located in BSSAP, which is reflected in the protocol specification by the layer 3 header defined in section 6.3, performs the discrimination between the data related to those two subparts, as illustrated in GSM 08.08 figure 1. The error handling for the BSSAP header is specified in GSM 08.08. This section describes the use of SCCP connections for MS transactions. Section 6.1 describes the connection establishment procedures. Section 6.2 describes the connection release procedures. Section 6.3 describes the distribution between BSSMAP and DTAP messages and the data transfer over a SCCP connection. The structure of the user data field in the SCCP message is described in sections 6.3 and 6.4 and in figure 3. ETSI ETSI TS 100 589 V7.0.1 (1999-07) 30 (GSM 08.06 version 7.0.1 Release1998)
|
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 cell, an additional connection for each BSS, and optionally connections for particular participants in a voice group or broadcast call are established when a voice group or broadcast call is established. A new SCCP connection is also established in the case of an external handover between the cells of one BSS for a point-to-point call, or for participants in a voice group or broadcast call who are supported on a dedicated channel. Various SCCP connection establishment cases have to be distinguished: i) Following an Access Request made by the MS on the Random Access Channel, a dedicated radio resource has been successfully allocated and a layer-2 connection has been established on the allocated resource. The SCCP connection establishment is then initiated by the BSS. ii) The MSC decides to perform an external handover and a new dedicated radio resource has to be reserved in the new BSS. The SCCP connection establishment is then initiated by the MSC. (Note that the old BSS and the new BSS may be the same.) iii) Following a request for a voice group or broadcast call received at a MSC, SCCP connections are established between the MSC and BSS for each cell in the group call area and the MSC and BSS for each BSS in the group call area. This is initiated by the MSC. Note that a SCCP connection for the originator has already been established via case i). iv) During a voice group or broadcast call the network may decide to place some participants on a dedicated channel and will perform SCCP connection establishment to support this channel. Such a decision will normally be based on responses received to notification messages in the case where the notification messages do not contain details of the location of the group or broadcast call channel. The above cases are the only cases currently identified for SCCP connection establishment. Others may emerge in the future. BSS MSC CR {SSN=BSSAP, a1, BSSMAP message} -------------------------------------------> CC {a1,a2, BSSMAP or DTAP message or no user data} <------------------------------------------ or CREF{a2, DTAP message or no user data <------------------------------------------ a1 = source local reference, a2 = destination local reference CC Connection Confirm CR Connection Request CREF Connection Refused Figure 1/08.06: Set-up of SCCP connections on the first BSS/MSC interface ETSI 31 ETSI TS 100 589 V7.0.1 (1999-07) (GSM 08.06 version 7.0.1 Release1998) BSS MSC CR {SSN=BSSAP, a1, BSSMAP message or no user data} <----------------------------------------- CC {a1, a2, BSSMAP message or no user data} ------------------------------------------> or CREF{a2, BSSMAP message or no user data} ------------------------------------------> a1 = source local reference, a2 = destination local reference CC Connection Confirm CR Connection Request CREF Connection Refused Figure 2/08.06: Set-up of SCCP connections on a new BSS/MSC (handover) interface or for a voice group or broadcast call initiation
|
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 identity of the MS is transferred to the MSC together with a cell identification, in a BSSMAP message (COMPLETE L3 INFORMATION) included in the user data field of the SCCP Connection Request message (see figure 1). After the reception of the Connection Request message, the MSC may check, based on the received identity, whether another association already exists for the same Mobile Subscriber. Two options among others are described hereafter: - after the reception of the Connection Request message, the MSC sends a Connection Confirm message and checks based on the received identity, whether another connection already exists for the same Mobile Subscriber. If another connection exists for the same Mobile Subscriber, the resources assigned for this previous connection are released after the identity of the Mobile Subscriber using the new connection has been successfully checked, e.g. by authentication or by ciphering procedure; - If such an association exists, the connection establishment is refused by sending a Connection Refused message. NOTE: The first option allows the new establishments and the reestablishments. - When the SCCP connection is to be established, a Connection Confirm message is sent back to the BSS. This message may optionally contain a BSSMAP or DTAP message in the user data field. If the connection establishment is refused for any reason, a SCCP Connection Refused message is sent back to the BSS. This message may optionally contain, in the user data field, a DTAP message which is forwarded to the MS. The procedures in case of connection establishment failure are specified in GSM 08.08.
|
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 user data field of this message may contain the BSSMAP HANDOVER REQUEST message (see figure 2). It is preferable to transfer the layer 3 messages in the user data field of the Connection Request in order to complete the establishment of the relation between the radio channel requested and the SCCP connection as soon as possible. ETSI ETSI TS 100 589 V7.0.1 (1999-07) 32 (GSM 08.06 version 7.0.1 Release1998) When receiving the Connection Request message, containing the BSSMAP HANDOVER REQUEST message, the BSS allocates the necessary resources for the requested handover. A Connection Confirm message is also returned to the MSC and may contain the BSSMAP HANDOVER REQUEST ACKNOWLEDGEMENT or QUEUEING INDICATION message in the user data field. If the handover resource allocation fails (see TS GSM 08.08) before the SCCP connection is established then the SCCP Connection Refused message may contain the BSSMAP HANDOVER FAILURE message in the user data field. The procedures in case of connection establishment failure are specified in GSM 08.08.
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
6.1.3 Establishment procedure in case iii)
|
In this case connection establishment is undertaken by the MSC on the reception of a voice group or broadcast call initiation request. At the reception of the voice group or broadcast call establishment request message, the MSC will determine that a voice group or broadcast call is required and retrieve the required information concerning, inter alia, the affected cells. SCCP connections are then established by the MSC to the BSS for each of these cells. A separate connection is established by the MSC to each affected BSS. A Connection Request message for each cell in the call and for each BSS in the call is sent to the BSS. The user data field of this message may contain the VGCS/VBS SETUP or VGCS/VBS ASSIGNMENT REQUEST message (see figure 2). It is preferable to transfer the layer 3 messages in the user data field of the Connection Request in order to complete the establishment of the relation between the radio channel requested and the SCCP connection as soon as possible. When receiving the Connection Request message, containing the VGCS/VBS SETUP or VGCS/VBS ASSIGNMENT REQUEST message, the BSS allocates the necessary resources for the requested call. A Connection Confirm message is also returned to the MSC and may contain the VGCS/VBS SETUP ACK, VGCS/VBS ASSIGNMENT RESULT or VGCS/VBS QUEUEING INDICATION message in the user data field. If the resource allocation fails (see GSM 08.08) before the SCCP connection is established then the SCCP Connection Refused message may contain the VGCS/VBS SETUP REFUSE or VGCS/VBS ASSIGNMENT FAILURE message in the user data field. The procedures in case of connection establishment failure are specified in GSM 08.08.
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
6.1.4 Establishment procedure in case iv)
|
In this case, the connection establishment may be performed at the request of the BSS or MSC. It will normally be as a result of a response to a notification message for a voice group or broadcast call which is received by the BSS. At the reception of the Connection Request message, the MSC may check, based on the received identity, whether another association already exists for the same MS. If it is not a CM REESTABLISHMENT and such an association exists, the connection establishment is refused. If such an association exists but the new SCCP CR is for a CM REESTABLISHMENT then the old SCCP connection shall be released. When the SCCP connection is to be established, a Connection Confirm message is sent back to the BSS. This message may optionally contain a BSSMAP or DTAP message in the user data field. If the connection establishment is refused for any reason, a SCCP Connection Refused message is sent back to the BSS. This message may optionally contain, in the user data field, a DTAP message which is forwarded to the MS. The procedures in case of connection establishment failure are specified in GSM 08.08.
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
6.2 Connection release
|
This procedure is always initiated at the MSC side. A connection is released when the MSC realizes that a given signalling connection is no longer required. That may occur, in normal cases: ETSI 33 ETSI TS 100 589 V7.0.1 (1999-07) (GSM 08.06 version 7.0.1 Release1998) - when a BSSAP release procedure is terminated; - when a handover resource allocation procedure has failed and a signalling connection was established. The MSC sends a SCCP released message. This message shall not contain any user data field. Abnormal cases: a connection failure may be detected by the connection supervision service provided by SCCP. The procedures in that case are specified in GSM 08.08.
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
6.3 Transfer of DTAP and BSSMAP data
|
The DTAP and BSSMAP Layer 3 messages between the MSC and the BSS are contained in the user data field of the exchanged SCCP frames. This field is optional for the Connection Request (CR) (except for BSS originated connections, see section 6.1); Connection Confirm (CC) and Connection Refused (CREF). The use of this field in such frames in the various establishment cases, which allows reduction n in delay and improves efficiency, is described in sections 6.1. The user data field is a mandatory parameter of the Data frames (DT); the user data field always contains either a DTAP or a BSSMAP message.
|
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
6.3.1 Distribution function
| |
b565fbd182a148565ebdcfaa5e266698
|
100 589
|
6.3.1.1 CCITT Recommendation
|
The distribution of messages between the BSSMAP and DTAP functions and the distribution/multiplexing of DTAP messages to/from the various radio link layer 2 access points are performed in an intermediate layer of protocol between SCCP and Layer 3 later referred as the distribution sublayer. The protocol for this sublayer simply consists of the management of a one or two octet Distribution Data Unit. Each SCCP User Data field necessarily contains such a distribution Data Unit as a header, followed by the length indicator and the actual Layer 3 BSSMAP or DTAP message.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.