hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
b03a5e12102d53d92940a49c0e1cfb88
|
100 909
|
5.1.4.4 Interleaving
|
The interleaving is done as specified for SACCH in section 4.1.4.
|
b03a5e12102d53d92940a49c0e1cfb88
|
100 909
|
5.1.4.5 Mapping on a burst
|
The mapping is given by the rule: e(B,j) = i(B,j) and e(B,59+j) = i(B,57+j) for j = 0,1,...,56 and e(B+m,57) = q(2m) and e(B+m,58) = q(2m+1) for m = 0,1,2,3 where q(0),q(1),...,q(7) = 0,0,0,1,0,1,1,0 identifies the coding scheme CS-4. 5.2 Packet control channels (PACCH, PBCCH, PAGCH, PPCH, PNCH, PTCCH) The coding scheme used for PACCH, PBCCH, PAGCH, PPCH, PNCH and downlink PTCCH is the same as for SACCH as specified in section 4.1. The coding scheme used for uplink PTCCH is the same as for PRACH as specified in section 5.3.
|
b03a5e12102d53d92940a49c0e1cfb88
|
100 909
|
5.3 Packet random access channel (PRACH)
|
Two coding schemes are specified for access bursts on the packet switched channels. The packet access burst containing 8 information bits and the extended packet access burst containing 11 information bits.
|
b03a5e12102d53d92940a49c0e1cfb88
|
100 909
|
5.3.1 Packet Access Burst
|
The encoding of this burst is as defined in section 4.6 for the random access channel (RACH). The BSIC used shall be the BSIC of the BTS to which the burst is intended.
|
b03a5e12102d53d92940a49c0e1cfb88
|
100 909
|
5.3.2 Extended Packet Access Burst
|
The burst carrying the extended packet random access uplink message contains 11 information bits d(0),d(1),...,d(10). Six parity bits p(0),p(1),...,p(5) are defined in such a way that in GF(2) the binary polynomial: d(0)D16 +...+ d(10)D6 + p(0)D5 +...+ p(5), when divided by D6 + D5 + D3 + D2 + D + 1 yields a remainder equal to D5 + D4 + D3 + D2 + D + 1. The six bits of the BSIC, {B(0),B(1),...,B(5)}, of the BTS to which the Random Access is intended, are added bitwise modulo 2 to the six parity bits, {p(0),p(1),...,p(5)}. This results in six colour bits, C(0) to C(5) defined as C(k) = b(k) + p(k) (k = 0 to 5) where: b(0) = MSB of PLMN colour code b(5) = LSB of BS colour code. This defines {u(0),u(1),..., u(20)} by: u(k) = d(k) for k = 0,1,...,10 u(k) = C(k-11) for k = 11,12,...,16 u(k) = 0 for k = 17,18,19,20 (tail bits) ETSI TS 100 909 V6.1.1 (1998-07) 31 GSM 05.03 version 6.1.1 Release 1997 The coded bits {c(0),c(1),..., c(41)} are obtained by the same convolutional code of rate 1/2 as for TCH/FS, defined by the polynomials: G0 = 1 + D3 + D4 G1 = 1 + D + D3 + D4 and with: c(2k) = u(k) + u(k-3) + u(k-4) c(2k+1) = u(k) + u(k-1) + u(k-3) + u(k-4) for k = 0,1,...,20 ; u(k) = 0 for k < 0 The code is punctured in such a way that the following coded bits: c(0), c(2), c(5), c(37), c(39), c(41) are not transmitted. This results in a block of 36 coded bits, {e(0), e(1),...,e(35)}. 5.4 Access Burst on packet switched channels other than PRACH The encoding of this burst is as defined in section 5.3 for the packet random access channel (PRACH). The BSIC used shall be the BSIC of the BTS to which the burst is intended. ETSI TS 100 909 V6.1.1 (1998-07) 32 GSM 05.03 version 6.1.1 Release 1997 Table 1: Reordering and partitioning of a coded block of 456 bits into 8 sub-blocks k mod 8= 0 1 2 3 k mod 8= 4 5 6 7 j=0 k=0 57 114 171 j=1 228 285 342 399 2 64 121 178 235 3 292 349 406 7 4 128 185 242 299 5 356 413 14 71 6 192 249 306 363 7 420 21 78 135 8 256 313 370 427 9 28 85 142 199 10 320 377 434 35 11 92 149 206 263 384 441 42 99 156 213 270 327 448 49 106 163 220 277 334 391 56 113 170 227 284 341 398 455 120 177 234 291 348 405 6 63 20 184 241 298 355 21 412 13 70 127 248 305 362 419 20 77 134 191 312 369 426 27 84 141 198 255 376 433 34 91 148 205 262 319 440 41 98 155 212 269 326 383 30 48 105 162 219 31 276 333 390 447 112 169 226 283 340 397 454 55 176 233 290 347 404 5 62 119 240 297 354 411 12 69 126 183 304 361 418 19 76 133 190 247 40 368 425 26 83 41 140 197 254 311 432 33 90 147 204 261 318 375 40 97 154 211 268 325 382 439 104 161 218 275 332 389 446 47 168 225 282 339 396 453 54 111 50 232 289 346 403 51 4 61 118 175 296 353 410 11 68 125 182 239 360 417 18 75 132 189 246 303 424 25 82 139 196 253 310 367 32 89 146 203 260 317 374 431 60 96 153 210 267 61 324 381 438 39 160 217 274 331 388 445 46 103 224 281 338 395 452 53 110 167 288 345 402 3 60 117 174 231 352 409 10 67 124 181 238 295 70 416 17 74 131 71 188 245 302 359 24 81 138 195 252 309 366 423 88 145 202 259 316 373 430 31 152 209 266 323 380 437 38 95 216 273 330 387 444 45 102 159 80 280 337 394 451 81 52 109 166 223 344 401 2 59 116 173 230 287 408 9 66 123 180 237 294 351 16 73 130 187 244 301 358 415 80 137 194 251 308 365 422 23 90 144 201 258 315 91 372 429 30 87 208 265 322 379 436 37 94 151 272 329 386 443 44 101 158 215 336 393 450 51 108 165 222 279 400 1 58 115 172 229 286 343 100 8 65 122 179 101 236 293 350 407 72 129 186 243 300 357 414 15 136 193 250 307 364 421 22 79 200 257 314 371 428 29 86 143 264 321 378 435 36 93 150 207 110 328 385 442 43 111 100 157 214 271 112 392 449 50 107 113 164 221 278 335 ETSI TS 100 909 V6.1.1 (1998-07) 33 GSM 05.03 version 6.1.1 Release 1997 Table 2: Subjective importance of encoded bits for the full rate speech TCH (Parameter names and bit indices refer to GSM 06.10) Importance class Parameter name Parameter number Bit index Label Class 1 Log area ratio 1 1 5 d0 block amplitude 12,29,46,63 5 d1, d2, d3, d4 Log area ratio 1 1 4 2 Log area ratio 2 2 5 Log area ratio 3 3 4 Log area ratio 1 1 3 Log area ratio 2 2 4 Log area ratio 3 3 3 Log area ratio 4 4 4 3 LPT lag 9,26,43,60 6 1 block amplitude 12,29,43,63 4 with Log area ratio 2,5,6 2,5,6 3 parity LPT lag 9,26,43,60 5 check LPT lag 9,26,43,60 4 LPT lag 9,26,43,60 3 LPT lag 9,26,43,60 2 block amplitude 12,29,43,63 3 Log area ratio 1 1 2 Log area ratio 4 4 3 Log area ratio 7 7 2 4 LPT lag 9,26,43,60 1 ...d48, d49 Log area ratio 5,6 5,6 2 d50 LPT gain 10,27,44,61 1 LPT lag 9,26,43,60 0 Grid position 11,28,45,62 1 Log area ratio 1 1 1 Log area ratio 2,3,8,4 2,3,8,4 2 Log area ratio 5,7 5,7 1 LPT gain 10,27,44,61 0 block amplitude 12,29,43,63 2 1 RPE pulses 13..25 2 with RPE pulses 30..42 2 parity 5 RPE pulses 47..59 2 check RPE pulses 64..76 2 Grid position 11,28,45,62 0 block amplitude 12,29,43,63 1 RPE pulses 13..25 1 RPE pulses 30..42 1 RPE pulses 47..59 1 RPE pulses 64..67 1 ...d181 RPE pulses 68..76 1 d182 Log area ratio 1 1 0 Log area ratio 2,3,6 2,3,6 1 Log area ratio 7 7 0 Log area ratio 8 8 1 Log area ratio 8,3 8,3 0 6 Log area ratio 4 4 1 2 Log area ratio 4,5 4,5 0 block amplitude 12,29,43,63 0 RPE pulses 13..25 0 RPE pulses 30..42 0 RPE pulses 47..59 0 RPE pulses 64..67 0 Log area ratio 2,6 2,6 0 ...d259 ETSI TS 100 909 V6.1.1 (1998-07) 34 GSM 05.03 version 6.1.1 Release 1997 Table 3a: Subjective importance of encoded bits for the half rate speech TCH for unvoiced speech frames (Parameter names and bit indices refer to GSM 06.20) Parameter Bit Label Class name index R0 1 d0 LPC 3 7 d1 GSP 0-1 2 d2 GSP 0-2 2 d3 GSP 0-3 2 d4 GSP 0-4 2 d5 LPC 1 0 d6 LPC 2 5...1 d7...d11 LPC 3 6...1 d12... Code 1-2 0 Code 2-2 6...0 Code 1-3 6...0 1 Code 2-3 6...3 LPC3 0 without R0 0 parity INT-LPC 0 check Code 1-2 1...6 Code 2-1 0...6 Code 1-1 0...6 GSP 0-4 0 GSP 0-3 0 GSP 0-2 0 GSP 0-1 0 LPC 2 0 GSP 0-4 1 GSP 0-3 1 GSP 0-2 1 GSP 0-1 1 LPC 1 1...4 ...d72 LPC 1 5 d73... GSP 0-4 3 GSP 0-3 3 GSP 0-2 3 GSP 0-1 3 LPC2 6...8 1 GSP 0-4 4 GSP 0-3 4 with GSP 0-2 4 parity GSP 0-1 4 check LPC 1 6...9 R0 2 LPC 1 10 R0 3,4 Mode 0,1 ...d94 Code 2-4 0...6 d95... Code 1-4 0...6 2 Code 2-3 0...2 ...d111 ETSI TS 100 909 V6.1.1 (1998-07) 35 GSM 05.03 version 6.1.1 Release 1997 Table 3b: Subjective importance of encoded bits for the half rate speech TCH for voiced speech frames (Parameter names and bit indices refer to GSM 06.20) Parameter name Bit index Label Class Parameter name Bit index Label Class LPC 1 2,1 d0, d1 LAG 3 3 d73... LPC 2 6...4 d2... LAG 2 3 GSP 0-1 4 LAG 1 3,4 1 GSP 0-2 4 LPC 2 7,8 GSP 0-3 4 LPC 1 3...6 with GSP 0-4 4 R0 2 parity GSP 0-1 3 LAG 1 5...7 check GSP 0-2 3 LPC 1 7...10 GSP 0-3 3 R0 3,4 GSP 0-4 3 Mode 0,1 ...d94 GSP 0-1 2 Code 4 0...8 d95... 2 GSP 0-2 2 Code 3 0...7 ...d111 GSP 0-3 2 GSP 0-4 2 Code 1 8...0 Code 2 8...5 Code 2 2...0 Code 3 8 Code 2 4,3 GSP 0-1 1 GSP 0-2 1 GSP 0-3 1 GSP 0-4 1 1 GSP 0-1 0 GSP 0-2 0 without GSP 0-3 0 parity GSP 0-4 0 check INT-LPC 0 LPC 2 0 LPC 3 0 LAG 4 0 LPC 3 1 LPC 2 1 LAG 4 1 LAG 3 0 LAG 2 0 LAG 1 0 LAG 4 2 LAG 3 1 LAG 2 1 LAG 1 1 LPC 3 2...4 LPC 2 2 LPC 3 5,6 LPC 2 3 R0 0 LPC 3 7 LPC 1 0 LAG 4 3 LAG 3 2 LAG 2 2 LAG 1 2 R0 1 ...d72 ETSI TS 100 909 V6.1.1 (1998-07) 36 GSM 05.03 version 6.1.1 Release 1997 Table 4: Reordering and partitioning of a coded block of 228 bits into 4 sub-blocks for TCH/HS b= 0 1 b= 2 3 i=0 k=0 150 i=1 k=1 151 2 38 188 3 39 189 4 76 226 5 77 227 6 114 14 7 115 15 8 152 52 9 153 53 10 190 90 11 191 91 18 128 19 129 56 166 57 167 94 204 95 205 132 32 133 33 20 170 70 21 171 71 208 108 209 109 8 146 9 147 46 184 47 185 84 222 85 223 30 122 10 31 123 11 160 48 161 49 198 86 199 87 28 124 29 125 66 162 67 163 40 104 200 41 105 201 142 30 143 31 180 68 181 69 218 106 219 107 4 144 5 145 50 42 182 51 43 183 80 220 81 221 118 6 119 7 156 44 157 45 194 82 195 83 60 22 120 61 23 121 60 158 61 159 98 196 99 197 136 24 137 25 174 62 175 63 70 212 100 71 213 101 12 138 13 139 50 176 51 177 88 214 89 215 126 2 127 3 80 164 40 81 165 41 202 78 203 79 34 116 35 117 72 154 73 155 110 192 111 193 90 148 26 91 149 27 186 64 187 65 224 102 225 103 16 140 17 141 54 178 55 179 100 92 216 101 93 217 130 20 131 21 168 58 169 59 206 96 207 97 36 134 37 135 110 74 172 111 75 173 112 112 210 113 113 2 11 ETSI TS 100 909 V6.1.1 (1998-07) 37 GSM 05.03 version 6.1.1 Release 1997 Table 5: Enhanced Full rate Source Encoder output parameters in order of occurrence and bit allocation within the speech frame of 244 bits/20 ms(Parameter names and bit indices refer to GSM 06.60) Bits (MSB-LSB) Description s1 - s7 index of 1st LSF submatrix s8 - s15 index of 2nd LSF submatrix s16 - s23 index of 3rd LSF submatrix s24 sign of 3rd LSF submatrix s25 - s32 index of 4th LSF submatrix s33 - s38 index of 5th LSF submatrix subframe 1 s39 - s47 adaptive codebook index s48 - s51 adaptive codebook gain s52 sign information for 1st and 6th pulses s53 - s55 position of 1st pulse s56 sign information for 2nd and 7th pulses s57 - s59 position of 2nd pulse s60 sign information for 3rd and 8th pulses s61 - s63 position of 3rd pulse s64 sign information for 4th and 9th pulses s65 - s67 position of 4th pulse s68 sign information for 5th and 10th pulses s69 - s71 position of 5th pulse s72 - s74 position of 6th pulse s75 - s77 position of 7th pulse s78 - s80 position of 8th pulse s81 - s83 position of 9th pulse s84 - s86 position of 10th pulse s87 - s91 fixed codebook gain subframe 2 s92 - s97 adaptive codebook index (relative) s98 - s141 same description as s48 - s91 subframe 3 s142 - s194 same description as s39 - s91 subframe 4 s195 - s244 same description as s92 - s141 ETSI TS 100 909 V6.1.1 (1998-07) 38 GSM 05.03 version 6.1.1 Release 1997 Table 6: Ordering of enhanced full rate speech parameters for the channel encoder (subjective importance of encoded bits) (after preliminary channel coding) (Parameter names refers to GSM 06.60) Description Bits (Table 5) Bit index within parameter CLASS 1a: 50 bits (protected by 3 bit TCH-FS CRC) LTP-LAG 1 w39 - w44 b8, b7, b6, b5, b4, b3 LTP-LAG 3 w146 - w151 b8, b7, b6, b5, b4, b3 LTP-LAG 2 w94 - w95 b5, b4 LTP-LAG 4 w201 - w202 b5, b4 LTP-GAIN 1 n48 b3 FCB-GAIN 1 w89 b4 LTP-GAIN 2 w100 b3 FCB-GAIN 2 w141 b4 LTP-LAG 1 w45 b2 LTP-LAG 3 w152 b2 LTP-LAG 2 w96 b3 LTP-LAG 4 w203 b3 LPC 1 w2 - w3 b5, b4 LPC 2 w8 b7 LPC 2 w10 b5 LPC 3 w18 - w19 b6, b5 LPC 3 w24 b0 LTP-LAG 1 w46 - w47 b1, b0 LTP-LAG 3 w153 - w154 b1, b0 LTP-LAG 2 w97 b2 LTP-LAG 4 w204 b2 LPC 1 w4 - w5 b3, b2 LPC 2 w11 - w12 b4, b3 LPC 3 w16 b8 LPC 2 w9 b6 LPC 1 w6 - w7 b1, b0 LPC 2 w13 b2 LPC 3 w17 b7 LPC 3 w20 b4 LTP-LAG 2 w98 b1 LTP-LAG 4 w205 b1 CLASS 1b: 132 bits (protected) LPC 1 w1 b6 LPC 2 w14 - w15 b1, b0 LPC 3 w21 b3 LPC 4 w25 - w26 b7, b6 LPC 4 w28 b4 LTP-GAIN 3 w155 b3 LTP-GAIN 4 w207 b3 FCB-GAIN 3 w196 b4 FCB-GAIN 4 w248 b4 FCB-GAIN 1 w90 b3 FCB-GAIN 2 w142 b3 FCB-GAIN 3 w197 b3 FCB-GAIN 4 w249 b3 CRC-POLY w253 - w260 b7, b6, b5, b4, b3, b2, b1, b0 LTP-GAIN 1 w49 b2 (continued) ETSI TS 100 909 V6.1.1 (1998-07) 39 GSM 05.03 version 6.1.1 Release 1997 Table 6 (continued): Ordering of enhanced full rate speech parameters for the channel encoder (subjective importance of encoded bits) (after preliminary channel coding) (Parameter names refers to GSM 06.60) Description Bits (Table 5) Bit index within parameter LTP-GAIN 2 w101 b2 LTP-GAIN 3 w156 b2 LTP-GAIN 4 w208 b2 LPC 3 w22 - w23 b2, b1 LPC 4 w27 b5 LPC 4 w29 b3 PULSE 1_1 w52 b3 PULSE 1_2 w56 b3 PULSE 1_3 w60 b3 PULSE 1_4 w64 b3 PULSE 1_5 w68 b3 PULSE 2_1 w104 b3 PULSE 2_2 w108 b3 PULSE 2_3 w112 b3 PULSE 2_4 w116 b3 PULSE 2_5 w120 b3 PULSE 3_1 w159 b3 PULSE 3_2 w163 b3 PULSE 3_3 w167 b3 PULSE 3_4 w171 b3 PULSE 3_5 w175 b3 PULSE 4_1 w211 b3 PULSE 4_2 w215 b3 PULSE 4_3 w219 b3 PULSE 4_4 w223 b3 PULSE 4_5 w227 b3 FCB-GAIN 1 w91 b2 FCB-GAIN 2 w143 b2 FCB-GAIN 3 w198 b2 FCB-GAIN 4 w250 b2 LTP-GAIN 1 w50 b1 LTP-GAIN 2 w102 b1 LTP-GAIN 3 w157 b1 LTP-GAIN 4 w209 b1 LPC 4 w30 - w32 b2, b1, b0 LPC 5 w33 - w36 b5, b4, b3, b2 LTP-LAG 2 w99 b0 LTP-LAG 4 w206 b0 PULSE 1_1 w53 b2 PULSE 1_2 w57 b2 (continued) ETSI TS 100 909 V6.1.1 (1998-07) 40 GSM 05.03 version 6.1.1 Release 1997 Table 6 (continued): Ordering of enhanced full rate speech parameters for the channel encoder (subjective importance of encoded bits) (after preliminary channel coding) (Parameter names refers to GSM 06.60) Description Bits (Table 5) Bit index within parameter PULSE 1_3 w61 b2 PULSE 1_4 w65 b2 PULSE 1_5 w69 b2 PULSE 2_1 w105 b2 PULSE 2_2 w109 b2 PULSE 2_3 w113 b2 PULSE 2_4 w117 b2 PULSE 2_5 w121 b2 PULSE 3_1 w160 b2 PULSE 3_2 w164 b2 PULSE 3_3 w168 b2 PULSE 3_4 w172 b2 PULSE 3_5 w176 b2 PULSE 4_1 w212 b2 PULSE 4_2 w216 b2 PULSE 4_3 w220 b2 PULSE 4_4 w224 b2 PULSE 4_5 w228 b2 PULSE 1_1 w54 b1 PULSE 1_2 w58 b1 PULSE 1_3 w62 b1 PULSE 1_4 w66 b1 PULSE 2_1 w106 b1 PULSE 2_2 w110 b1 PULSE 2_3 w114 b1 PULSE 2_4 w118 b1 PULSE 3_1 w161 b1 PULSE 3_2 w165 b1 PULSE 3_3 w169 b1 PULSE 3_4 w173 b1 PULSE 4_1 w213 b1 PULSE 4_3 w221 b1 PULSE 4_4 w225 b1 FCB-GAIN 1 w92 b1 FCB-GAIN 2 w144 b1 FCB-GAIN 3 s199 b1 FCB-GAIN 4 w251 b1 LTP-GAIN 1 w51 b0 LTP-GAIN 2 w103 b0 LTP-GAIN 3 w158 b0 LTP-GAIN 4 w210 b0 FCB-GAIN 1 w93 b0 FCB-GAIN 2 w145 b0 FCB-GAIN 3 w200 b0 FCB-GAIN 4 w252 b0 PULSE 1_1 w55 b0 PULSE 1_2 w59 b0 PULSE 1_3 w63 b0 PULSE 1_4 w67 b0 PULSE 2_1 w107 b0 PULSE 2_2 w111 b0 PULSE 2_3 w115 b0 PULSE 2_4 w119 b0 PULSE 3_1 w162 b0 PULSE 3_2 w166 b0 PULSE 3_3 w170 b0 (continued) ETSI TS 100 909 V6.1.1 (1998-07) 41 GSM 05.03 version 6.1.1 Release 1997 Table 6 (continued): Ordering of enhanced full rate speech parameters for the channel encoder (subjective importance of encoded bits) (after preliminary channel coding) (Parameter names refers to GSM 06.60) Description Bits (Table 5) Bit index within parameter PULSE 3_4 w174 b0 PULSE 4_1 w214 b0 PULSE 4_3 w222 b0 PULSE 4_4 w226 b0 LPC 5 w37 - w38 b1, b0 CLASS 2: 78 bits (unprotected) PULSE 1_5 w70 b1 PULSE 1_5 w72 - w73 b1, b1 PULSE 2_5 w122 b1 PULSE 2_5 w124 - s125 b1, b1 PULSE 3_5 w177 b1 PULSE 3_5 w179 - w180 b1, b1 PULSE 4_5 w229 b1 PULSE 4_5 w231 - w232 b1, b1 PULSE 4_2 w217 - w218 b1, b0 PULSE 1_5 w71 b0 PULSE 2_5 w123 b0 PULSE 3_5 w178 b0 PULSE 4_5 w230 b0 PULSE 1_6 w74 b2 PULSE 1_7 w77 b2 PULSE 1_8 w80 b2 PULSE 1_9 w83 b2 PULSE 1_10 w86 b2 PULSE 2_6 w126 b2 PULSE 2_7 w129 b2 PULSE 2_8 w132 b2 PULSE 2_9 w135 b2 PULSE 2_10 w138 b2 PULSE 3_6 w181 b2 PULSE 3_7 w184 b2 PULSE 3_8 w187 b2 PULSE 3_9 w190 b2 PULSE 3_10 w193 b2 PULSE 4_6 w233 b2 PULSE 4_7 w236 b2 PULSE 4_8 w239 b2 PULSE 4_9 w242 b2 PULSE 4_10 w245 b2 PULSE 1_6 w75 b1 PULSE 1_7 w78 b1 PULSE 1_8 w81 b1 PULSE 1_9 w84 b1 PULSE 1_10 w87 b1 PULSE 2_6 w127 b1 PULSE 2_7 w130 b1 PULSE 2_8 w133 b1 PULSE 2_9 w136 b1 PULSE 2_10 w139 b1 PULSE 3_6 w182 b1 PULSE 3_7 w185 b1 PULSE 3_8 w188 b1 PULSE 3_9 w191 b1 PULSE 3_10 w194 b1 PULSE 4_6 w234 b1 PULSE 4_7 w237 b1 (continued) ETSI TS 100 909 V6.1.1 (1998-07) 42 GSM 05.03 version 6.1.1 Release 1997 Table 6 (concluded): Ordering of enhanced full rate speech parameters for the channel encoder (subjective importance of encoded bits) (after preliminary channel coding) (Parameter names refers to GSM 06.60) Description Bits (Table 5) Bit index within parameter PULSE 4_8 w240 b1 PULSE 4_9 w243 b1 PULSE 4_10 w246 b1 PULSE 1_6 w76 b0 PULSE 1_7 w79 b0 PULSE 1_8 w82 b0 PULSE 1_9 w85 b0 PULSE 1_10 w88 b0 PULSE 2_6 w128 b0 PULSE 2_7 w131 b0 PULSE 2_8 w134 b0 PULSE 2_9 w137 b0 PULSE 2_10 w140 b0 PULSE 3_6 w183 b0 PULSE 3_7 w186 b0 PULSE 3_8 w189 b0 PULSE 3_9 w192 b0 PULSE 3_10 w195 b0 PULSE 4_6 w235 b0 PULSE 4_7 w238 b0 PULSE 4_8 w241 b0 PULSE 4_9 w244 b0 PULSE 4_10 w247 b0 ETSI TS 100 909 V6.1.1 (1998-07) 43 GSM 05.03 version 6.1.1 Release 1997 Annex A (informative): Summary of Channel Types TCH/EFS: enhanced full rate speech traffic channel TCH/FS: full rate speech traffic channel TCH/HS: half rate speech traffic channel TCH/F14.4 14.4 kbit/s full rate data traffic channel TCH/F9.6: 9.6 kbit/s full rate data traffic channel TCH/F4.8: 4.8 kbit/s full rate data traffic channel TCH/H4.8: 4.8 kbit/s half rate data traffic channel TCH/F2.4: 2.4 kbit/s full rate data traffic channel TCH/H2.4: 2.4 kbit/s half rate data traffic channel SACCH: slow associated control channel FACCH/F: fast associated control channel at full rate FACCH/H: fast associated control channel at half rate SDCCH: stand-alone dedicated control channel BCCH: broadcast control channel PCH: paging channel AGCH access grant channel RACH: random access channel SCH: synchronization channel CBCH: cell broadcast channel PDTCH packet data traffic channel PACCH packet associated control channel PBCCH packet broadcast control channel PAGCH packet access grant channel PPCH packet paging channel PNCH packet notification channel PTCCH packet timing advance control channel PRACH packet random access channel ETSI TS 100 909 V6.1.1 (1998-07) 44 GSM 05.03 version 6.1.1 Release 1997 Annex B (informative): Summary of Polynomials Used for Convolutional Codes G0 = 1+ D3 + D4 TCH/FS, TCH/EFS, TCH/F14.4, TCH/F9.6, TCH/H4.8, SDCCH, BCCH, PCH, SACCH, FACCH, AGCH, RACH, SCH, PDTCH (CS-1, CS-2, CS3, CS-4), PACCH,PBCCH, PAGCH, PPCH, PNCH, PTCCH, PRACH G1 = 1 + D + D3 + D4 TCH/FS, TCH/EFS, TCH/F14.4, TCH/F9.6, TCH/H4.8, SACCH, FACCH, SDCCH, BCCH,PCH, AGCH, RACH, SCH, TCH/F4.8, TCH/F2.4, TCH/H2.4,PDTCH(CS-1, CS-2, CS-3, CS-4), PACCH, PBCCH, PAGCH, PPCH, PNCH, PTCCH, PRACH G2 = 1 + D2 + D4 TCH/F4.8, TCH/F2.4, TCH/H2.4 G3 = 1 + D + D2 + D3 + D4 TCH/F4.8, TCH/F2.4, TCH/H2.4 G4 = 1 + D2 + D3 + D5 + D6 TCH/HS G5 = 1 + D + D4 + D6 TCH/HS G6 = 1 + D + D2 + D3 + D4 + D6 TCH/HS ETSI TS 100 909 V6.1.1 (1998-07) 45 GSM 05.03 version 6.1.1 Release 1997 Annex C (informative): Change control history SPEC SMG CR PHA VERS NEW_VE SUBJECT 05.03 s25 A015 R97 6.0.0 6.1.0 14.4kbps Data Service ETSI TS 100 909 V6.1.1 (1998-07) 46 GSM 05.03 version 6.1.1 Release 1997 History Document history V6.1.1 July 1998 Publication ISBN 2-7437-2427-7 Dépôt légal : Juillet 1998
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
0 Scope
|
The present document defines the requirements for and gives guidelines on the MMI for calls on the GSM Mobile Station (MS). This includes the requirements of the user procedures for call control and supplementary service control, the requirements on the physical input media and the output, such as indications and displayed information. The present document complements specifications GSM 02.07 [3], 02.11 [4], 02.17 [5], 02.40 [7], 03.01[11], 03.09 [12], 03.12 [13], 03.14 [14], 04.08 [16], 05.08 [18], and 11.10 [20] and deals with MMI items not covered by these specifications.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
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. [1] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms". [2] GSM 02.04: "Digital cellular telecommunication system (Phase 2+); General on supplementary services". [3] GSM 02.07: "Digital cellular telecommunication system (Phase 2+); Mobile Station (MS) features". [4] GSM 02.11: "Digital cellular telecommunication system (Phase 2+); Service accessibility". [5] GSM 02.17: "Digital cellular telecommunication system (Phase 2+); Subscriber identity modules Functional characteristics". [6] GSM 02.16: "Digital cellular telecommunications system (Phase 2+; International Mobile station Equipment Identities (IMEI)". [7] GSM 02.40: "Digital cellular telecommunication system (Phase 2+); Procedures for call progress indications". [8] GSM 02.83: "Digital cellular telecommunication system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 1". [9] GSM 02.84: "Digital cellular telecommunication system (Phase 2+); MultiParty (MPTY) supplementary services - Stage 1". [10] GSM 02.90: "Digital cellular telecommunication system (Phase 2+); "Stage 1 description of Unstructured Supplementary Service Data (USSD)". [11] GSM 03.01: "Digital cellular telecommunication system (Phase 2+); Network functions". [12] GSM 03.09: "Digital cellular telecommunication system (Phase 2+); Handover procedures". [13] GSM 03.12: "Digital cellular telecommunication system (Phase 2+); Location registration procedures". [14] GSM 03.14: "Digital cellular telecommunication system (Phase 2+); Support of Dual Tone Multi- Frequency signalling (DTMF) via the GSM system". ETSI TS 100 907 V6.1.0 (1999-03) 7 GSM 02.30 version 6.1.0 Release 1997 [15] GSM 03.38: "Digital cellular telecommunication system (Phase 2+);"Alphabets and language- specific information". [16] GSM 04.08: "Digital cellular telecommunication system (Phase 2+); Mobile radio interface layer 3 specification". [17] GSM 04.80: "Digital cellular telecommunication system (Phase 2+); Mobile radio interface layer 3 supplementary services specification Formats and coding". [18] GSM 05.08: "Digital cellular telecommunication system (Phase 2+); Radio subsystem link control". [19] GSM 09.02: "Digital cellular telecommunication system (Phase 2+); Mobile Application Part (MAP) specification". [20] GSM 11.10: "Digital cellular telecommunication system (Phase 2+); Mobile Station (MS) conformity specification". [21] GSM 11.11: "Digital cellular telecommunication system (Phase 2+); Specification of the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface". [22] CCITT Recommendation E.164: "Numbering plan for the ISDN era". [23] CCITT Recommendation E.131: "Subscriber control procedures for supplementary telephone services". [24] CCITT Recommendation E.121: "Pictograms and symbols to assist users of the telephone service".
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
0.2 Abbreviations
|
Abbreviations used in the present document are listed in GSM 01.04 [1].
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
0.3 Definitions
|
Directory Number: a string consisting of one or more of the characters from the set {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, *, #, a, b, c} associated with a nature of address indicator and number plan indicator. When using the public MMI for the control of supplementary services however, * and # cannot be part of any SC or SI field. NOTE 1: No such restriction on the SC and SI fields exists when using other (e.g. menu-driven) MMI for the control of supplementary services. NOTE 2: When using the public MMI, certain limitations on the use of one and two digit directory numbers may apply. The use of other MMI can remove these restrictions. NOTE 3: This definition is not intended to require the support of all these characters in the MMI itself.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
1 General
| |
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
1.1 Basic philosophy
|
The basic idea behind the present document is that it should give a minimum level of requirements, with emphasis on items which are seen as important from a pan-European usage point of view. This means, that the requirements are mainly dealing with standardized control procedures of access to services i.e. call establishment, invocation of supplementary services and so on. This also includes standardized network information to the users such as tones and announcements. ETSI TS 100 907 V6.1.0 (1999-03) 8 GSM 02.30 version 6.1.0 Release 1997 The requirements on the physical layout of input and output features are kept to a minimum to allow for differentiated types of MSs and to ease the introduction of future developments in the area of MMI. The standardized control procedures describe the sequence of real actions to be taken by the users. However, since the requirements on the physical input features are minimal the control procedures may differ between MSs depending on the solution of the manufacturers. The "bridge" between these requirements is however that the same logical actions have to be taken by the user. That is, the user has to provide the same information for the call control and signalling no matter what the method is. This is also valid if an automatic device is used for carrying out the same actions. The logical procedures are therefore defined and standardized in the present document. The drawback of this approach is that the users of GSM Mobile Stations may face a lot of different types of physical MMI which they have to learn. However, to deal with this problem the specification gives a definition of a basic public MMI. The basic public MMI allows non-experienced, casual users to make and receive a telephony call. This definition is directed to manufacturers of public mobile telephones. Optionally, the user may set the ME to disable some or all of the MMI functions defined in the present document. This setting shall only apply when the same SIM is in use (see GSM 02.17 [5] for security policy), otherwise the ME shall enable the standard MMI.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
1.2 Structure of the specification
|
The TS is divided into sections describing respectively the control procedures, the input features and the output features. The final section defines the basic public MMI. For a lot of items for which no particular MMI specification is necessary there is a reference to the specifications where the basic requirements are to be found (i.e. MS features specified in GSM 02.07 [3] and language of announcements specified in GSM 02.40 [7]).
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
2 Physical user input features
| |
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
2.1 General
|
This clause gives the requirements or guidelines for the MMI of the input related MS features. Basic requirements on these features are given in GSM 02.07 [3] and GSM 02.40 [7].
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
2.2 MMI related to MS access
|
No requirements additional to those in other GSM specifications (Reference GSM 02.17 [5], 11.10 [20]).
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
2.3 MMI related to MS features
|
The three first issues are covered in GSM 02.07 [3]: * Country / PLMN selection: The method is manufacturer optional. * International Access Function ("+" key): and * Keypad: The physical means of entering the characters 0-9, +, * and # (i.e. the SELECT function) may be keypad, voice input device, DTE or other, but there must be means to enter this information. The relationship on the keypad between the numbers and letters (where used) is important when mnemonic dialling may be used. The following relationship is therefore preferred though optional. ETSI TS 100 907 V6.1.0 (1999-03) 9 GSM 02.30 version 6.1.0 Release 1997 1 6 MNO 2 ABC 7 PQRS 3 DEF 8 TUV 4 GHI 9 WXYZ 5 JKL 0 See also subclause 5.2.1. * ACCEPT, SEND and END functions: The physical means to perform these functions may be keypad, voice input device, DTE or other, but there must be means to perform these functions. ACCEPT and SEND may use the same means. * Setting of called Number Fields (Type of Number), use of the "+" key function: Users may enter a called number in two formats, called here International or Open. The Type of Number (TON) may be set to other values if required, but the procedure for this is not defined here. "International format": This is entered by starting with a "+" followed by country code, even for national calls. This method is preferred for roaming and international calls, and highly desirable for storage of short codes or for call-forwarding. This sets the TON to "International" - see GSM 04.08 [17] table 10.50. "Open format": This is when the "+" is not entered, and the number is entered in the normal way for that network. The number may require a prefix or escape code as normal, for example for entering the international access code or national access code (often "0"). This sets the TON to "Unknown" - see GSM 04.08 [17] table 10.50. (This is not the "National" case, which does not permit prefix or escape digits). Care should be taken with this format, since the dialled number will only be correct in a given network, and may be wrong when roaming. Caution must be applied when using stored numbers or call-forwarding. * Setting of Called Number Fields (Number Plan Indicator): The default Number Plan Identification (NPI) shall be CCITT E.164 [22] if all the digits are in the range 0-9 and the NPI shall be "unknown" if other number information is included. However, if the user selects (or has selected) a particular NPI (procedure not defined) then that NPI shall be used. * Entry of Bearer Capability Information Elements (BCIE): This is required in order to indicate information such as whether it is a voice or data call, facsimile, synchronous or asynchronous etc. The method for entering this information is of mobile manufacturer's option. For those Mobile Stations offering only telephony (and emergency calls), the default BCIE shall be for telephony (or emergency call). For Mobile Stations supporting non-voice services, there shall be means to set the BCIE required, by reading the appropriate field in the SIM and possibly otherwise. This field may be associated with or independent of the called number.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
2.4 MMI related to user information
|
These issues are covered in GSM 02.40 [7]: * Selection of language of announcements: No additional requirements are defined in the present document. ETSI TS 100 907 V6.1.0 (1999-03) 10 GSM 02.30 version 6.1.0 Release 1997
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
2.5 Other input features
|
No requirements additional to those in other GSM specifications (Reference GSM 03.14 [14] 11.10 [20]).
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
3 Indications and output features
| |
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
3.1 General
|
This clause gives the requirements and guidelines of the MMI aspects of the outputs such as displayed information, indications and tones. Basic requirements on these features are given in GSM 02.07 [3] and GSM 02.40 [7].
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
3.2 MMI related to MS access
|
No requirements additional to those in other GSM specifications (ref. GSM 03.12 [13], GSM 04.08 [16], GSM 05.08 [18]).
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
3.3 MMI related to MS features
|
Country/PLMN Indication: * The country/PLMN Indication (see GSM 02.07 [3] for definition) should be displayed as such that the user can uniquely identify the country and PLMN e.g. by alpha or numeric means or other. These issues are covered in GSM 02.07 [3]. No additional requirements are defined in this specification: * Indication of Call Progress Signals. * Display of Called Number. * Short Message. * Call Charge Units Meter.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
3.4 MMI related to user information
|
These issues are covered in GSM 02.40 [7]. No additional requirements are defined in this specification: * Selection of language of announcements; * Supervisory tones.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
3.5 Other output features
|
No requirements additional to those in other GSM specifications (ref. GSM 03.01 [11], 03.09 [12], 03.12 [13], 04.08 [16] and 05.08 [18]).
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4 Procedures
| |
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.1 General
|
ETSI TS 100 907 V6.1.0 (1999-03) 11 GSM 02.30 version 6.1.0 Release 1997 This clause defines the MMI of the service access procedures, and supplementary service control procedures. These procedures are defined as logical procedures and in general no mandatory methods are specified. In order to make the descriptions continuous and clear requirements in GSM 02.07 [3], 02.11 [4], 02.17 [5] and 02.40 [7] have been included or are referenced. The mapping between the MMI procedures and the call control entity is specified in GSM 04.08 [16].
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.2 MS access
|
The MS access procedure is comprised of the initial actions the user has to take before calls can be established or received. This procedure includes e.g. insertion of subscriber-card and entering the PIN-code. As there exist different types of MS and as requirements in other GSM specifications allow different options the MS access procedure may differ between Mobile Stations. The method for describing the MS access procedures is by using a Mealy-graph, see annex A. The graph shows the MS access for simple MS e.g. hand-held and they may be different for more complex stations. It should also be noted that the exact sequences of events are not described, these may be chosen by the manufacturers. Nevertheless, the related requirements in the other GSM specifications referenced in subclause 4.1 are applicable.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.3 Definition of functions
|
The following functions are applicable and mandatory for the logical procedures for Mobile originated and terminated calls and for the control of Supplementary Services: ACCEPT: Acceptance of a mobile terminated call. SELECT: Entry of information. SEND: Transmission of the entered information to the network. INDICATION: Requirements in GSM 02.40 [7] are applicable. Other indications may be given in addition throughout the procedure. END: Termination of or disconnection from the call. The execution of the END-function may be caused by either party involved in the call by e.g. termination, loss of coverage, invalidation of payment.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.4 Call Control
| |
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.4.1 General
|
Voice calls to and from a Mobile Station shall be controlled in accordance with the procedures described below. "Data calls" are expected to be controlled in a similar way but are not here specified.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.4.2 Voice calls
|
The voice call is either a normal telephony call or an emergency call.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.4.2.1 Mobile originated calls
|
The following sequence of functions shall be used: SELECT: Entry of called address information. SEND: Transmission of the called address. INDICATION: See subclause 4.3. ETSI TS 100 907 V6.1.0 (1999-03) 12 GSM 02.30 version 6.1.0 Release 1997 END: Termination of the call.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.4.2.2 Emergency calls
|
With Mobile Stations supporting Telephony, it shall be possible to place an emergency call by entering 112 followed by SEND in the manner specified in subclause 4.4.2.1. It may also be possible for a user to enter a preferred emergency MMI code of up to six digits (such as 999) followed by SEND to invoke an emergency call. In this latter case, the preferred code shall be stored in the SIM and the ME recognizes any dialled instance of this code to set up the emergency call. Additional means to place such a call are also allowed, e.g. provision of a dedicated button. The MS must support the initiation of an emergency call to "112" without a SIM present in the MS, regardless of the call being accepted or not by the network (national option to require IMSI). NOTE: In addition to the above procedure, calls to national emergency services may be made in the way standard for the country of the serving PLMN. However, with the exception of code "112", these are not treated within the PLMN as "Teleservice Emergency call" unless the ME recognizes the code as an emergency code as described above, and would require a valid IMSI.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.4.2.3 Mobile terminated calls
|
The following sequence of functions shall be used: INDICATION: Alert to the user that she is being called. ACCEPT: Acceptance of the incoming call by the user. INDICATION: See subclause 4.3. END: Termination of the call. User Determined User Busy (UDUB): If, on being alerted by an incoming call, the called user enters "0 SEND", this shall set UDUB for that call, which shall either invoke call forwarding on busy, if active and operative, or else present BUSY to the calling party.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.5 Supplementary Services Control
| |
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.5.1 General
|
4.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
5.1 General
|
The supplementary services shall be controlled in accordance with the procedures described below. All Mobile Stations with MMI shall be able to be controlled in this way, to minimize the confusion of users using different types of Mobile Station (quite likely, due to the use of the SIM IC card) and to permit the introduction by a PLMN operator of new supplementary services, not defined at the time of the design of a Mobile Station. These procedures are based on those recommended by CEPT/SF and CCITT Recommendation E.131. The specified MMI shall be supported by the L3 signalling between the MS and the MSC, see GSM 04.80 [17]. In addition to these specified MMI procedures the MS may be equipped with additional enhanced MMI procedures (e.g. dedicated keys, menu procedures...), left to the discretion of the manufacturer. These procedures shall also be converted in accordance with GSM 04.80 [17].
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.5.2 Structure of the MMI
|
The following sequence of functions shall be used for the control of Supplementary Services: SELECT: Entry of the procedure information (may be a digit or a sequence of characters). SEND: Transmission of the information to the network. INDICATION: See subclause 4.3. ETSI TS 100 907 V6.1.0 (1999-03) 13 GSM 02.30 version 6.1.0 Release 1997 The MS shall support the MMI procedure specified as: Activation : *SC*SI# Deactivation : #SC*SI# Interrogation : *#SC*SI# Registration : *SC*SI# and **SC*SI# Erasure : ##SC*SI# This structure consists of the following parts: - Service Code, SC( (2 or 3 digits); - Supplementary Information, SI (variable length). The procedure always starts with *, #, **, ## or *# and is finished by #. Each part within the procedure is separated by *. The service code uniquely specifies the Supplementary Service, either as a defined GSM Supplementary Service or as a spare service code. All spare service codes shall be reserved for future use. The MS shall determine from the context whether, an entry of a single *, activation or registration was intended. For example, a call forwarding request with a single * would be interpreted as registration if containing a forwarded-to number, or an activation if not. The supplementary information (SI) may comprise e.g. a PIN code or Directory Number. Where a particular service request does not require any SI, "*SI" is not entered, e.g. Activation becomes *SC#SEND. Where further supplementary information is required this is again entered as *SI, e.g. *SC*SIA*SIB#SEND. SIB may be used to specify the tele or bearer service expressed as a Basic Service Group to which this supplementary service request applies, SIC may be used to specify the value of the "No Reply Condition Timer". Use of SIA, SIB, SIC for a particular procedure is optional. The procedure to be adopted where these are not all used is as follows: *SI# shall be entered in any of the following formats: * SIA * SIB * SIC # * SIA * SIB # * SIA * * SIC # * SIA # * * SIb * SIC # * * SIB # * * * SIC # # The denotation of the Supplementary Information and the order of entry are specified in annex B. Supplementary Information Codes for the Teleservices and Bearer Services are given in annex C. The following procedures shall be used for application of supplementary services to the call set-up procedure: *SCn*SI#DN SEND; where SC is the service code defined in annex B and *SI is an optional field which may be applicable to service SC. The "n" is a single digit used to indicate the numbering plan, profile, priority, etc. according to the service being applied. For simplicity of presentation, the leading * is shown on the assumption that the action is to activate (switch on) the required service. However, for a deactivation (or switch off), this would become: ETSI TS 100 907 V6.1.0 (1999-03) 14 GSM 02.30 version 6.1.0 Release 1997 #SCn*SI#DN SEND; It is assumed that the *# (interrogation) will not apply to call set-up. Where more than one supplementary service is applicable to the call set-up, these shall be concatenated with any applicable supplementary information immediately following the applicable service code. For example, if SCn and SI refer to one applicable supplementary service and scn and si to another, then the generic procedure becomes: *SCn*SI#scn*si#DN SEND. NOTE: The order of entry of SC and sc is a user option, provided that any supplementary information follows immediately after the relevant SC. Where SI is not applicable according to the definition of the supplementary service, then *SI is omitted. Where its use is optional, but not selected for a particular call set-up, it may be omitted or entered as an extra * if this is necessary to avoid ambiguity of interpretation. NOTE: By using the # as a separator, most cases are expected to be unambiguous.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.5.3 Handling of supplementary services
| |
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.5.3.1 Handling of defined GSM supplementary services
|
The MMI procedure for the defined GSM Supplementary Services shall be converted to the mobile radio interface Layer 3, as specified in GSM 04.80 [17]. An appropriate message should be given/displayed to the user in accordance with the "return result/error" from the network. The service codes for the defined GSM Supplementary Services are given in annex B.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.5.3.2 Handling of not-implemented supplementary services
|
The MS shall act in accordance with figure 4.5.3.2 when digits are entered to the MS to determine whether to interpret these as call set-up requests or supplementary service control procedures etc.. This may involve a mechanism, referred to as Unstructured SS Data, which allows the support of GSM SS services which are not implemented by means of the GSM specified functional signalling. See also GSM 02.90 [10]. ETSI TS 100 907 V6.1.0 (1999-03) 15 GSM 02.30 version 6.1.0 Release 1997 Idle or 'in call' Input string Input string is standard GSM SS procedure support by MS Input string is SIM control procedure Input String is MS manufacturer defined procedure (2) Input string is #-string (3) Input string is short string (4) MS shall perform the requested procedure MS is in a call (1) Input string is 2 digit starting with a "1" Input shall be sent as a call set-up request Other meaning or error Input string is call set-up string (5) Yes No No Yes Yes No Yes Yes Yes No No Yes Yes No No No Is USSD supported by the MS? No MS shall interpret this as USSD and send transparently torwards the network Yes Figure 4.5.3.2 The following definitions are applicable to the interpretation of figure 4.5.3.2: ETSI TS 100 907 V6.1.0 (1999-03) 16 GSM 02.30 version 6.1.0 Release 1997 1) In a call: A MS is "in a call" from the time that signalling related to the establishment or attempted establishment of a MO or MT call commences and before the call or call attempt ends, and (if applicable) the ME has stopped generating tones related to this call to the user. 2) MS manufacturer defined procedure: The term "MS manufacturer defined procedure" shall not include the following two cases: (i) input which can be interpreted as being of the following form, whether or not in a call: CX [string]# followed by SEND; where string is any combination of numeric digits, *, #; and C comprises 1, 2 or 3 digits from the set (*,#); and X comprises 1, 2 or 3 numeric digits or the fourth numeric digit is non-zero; (ii) input of the following form in a call (as defined above): "Entry of 1 or 2 characters defined in the GSM 03.38 [15] Default Alphabet followed by SEND". 3) #-string: Input of the form. "Entry of any characters defined in the GSM 03.38 [15] Default Alphabet (up to the maximum defined in GSM 04.80 [17]), followed by #SEND". 4) Short string: "Entry of 1 or 2 characters defined in the GSM 03.38 [15] Default Alphabet followed by SEND". 5) Call setup string: MMI input in accordance with the call set-up procedures as defined in GSM 04.08 [16] and terminated by SEND. If the network has initiated an operation which explicitly (in the signalling) requires a response from the user, then the user shall be able to enter a response in the form of any string of characters followed by SEND. The mobile shall also provide an MMI command to terminate the dialogue with a NULL response. The use of END shall release all calls in progress (see also subclause 4.5.5.2), terminate any outstanding unstructured SS operations, and release any connection used for unstructured SS operations.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.5.4 Registration of new password
|
The following procedure permits the user to change the password relating to use of Supplementary Services. The only control procedure supported is Registration of a new password, which replaces any previous password for the same service. The password may not be Erased or Interrogated. ETSI TS 100 907 V6.1.0 (1999-03) 17 GSM 02.30 version 6.1.0 Release 1997 Procedure: * 03 * ZZ * OLD_PASSWORD * NEW_PASSWORD * NEW_PASSWORD # The MS shall also support the alternative procedure: ** 03 * ZZ * OLD_PASSWORD * NEW_PASSWORD * NEW_PASSWORD # where, for Barring Services, ZZ = 330; for a common password for all appropriate services, delete the ZZ, entering: * 03 ** OLD_PASSWORD * NEW_PASSWORD * NEW_PASSWORD # The MS shall also support the alternative procedure: ** 03 ** OLD_PASSWORD * NEW_PASSWORD * NEW_PASSWORD # the MS will then indicate to the user whether the new password request has been successful or not. If the new password request is rejected (e.g. due to entry of incorrect old password) the old password remains unchanged, until it is successfully changed by correctly repeating the procedure. Refer to GSM 02.04 [2] regarding repeated entry of incorrect password. NOTE: The procedures shall be followed by SEND as described in subclause 4.5.2.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.5.5 Handling of supplementary services within a call
|
4.5.5.1 Call Deflection, Call Waiting, Call Hold, MultiParty Services, Explicit Call Transfer and Completion of Calls to Busy Subscriber general principles During a call, the following general procedures shall be available, where applicable, for the subscriber to control the operation of - Call Deflection - Call Waiting - Call Hold - MultiParty Services - Explicit Call Transfer - $(CCBS)$: Completion of Calls to Busy Subscriber including their interactions. It should be noted that not all control procedures described in GSM 02.72, 02.83, 02.84, 02.91, and 02.93 are specified in this subclause. Procedures: Entering 0 followed by SEND - Releases all held calls or sets User Determined User Busy (UDUB) for a waiting call. Entering 1 followed by SEND - Releases all active calls (if any exist) and accepts the other (held or waiting) call. Entering 1X followed by SEND - Releases a specific active call X. Entering 2 followed by SEND - Places all active calls (if any exist) on hold and accepts the other (held or waiting) call. Entering 2X followed by SEND - Places all active calls on hold except call X with which communication shall be supported. ETSI TS 100 907 V6.1.0 (1999-03) 18 GSM 02.30 version 6.1.0 Release 1997 Entering 3 followed by SEND - Adds a held call to the conversation. Entering 4 followed by SEND - Connects the two calls and disconnects the subscriber from both calls (ECT). Entering 4 * "Directory Number" - Redirect an incoming or a waiting call to the specified followed by SEND directory number. Entering 5 followed by SEND - $(CCBS)$: Activates the Completion of Calls to Busy Subscriber Request. Entering "Directory Number" - Places all active calls (if any exist) on hold and sets up a followed by SEND new call to the specified Directory Number. Entering END - Releases the subscriber from all calls (except a possible waiting call). "X" is the numbering (starting with 1) of the call given by the sequence of setting up or receiving the calls (active, held or waiting) as seen by the served subscriber. Calls hold their number until they are released. New calls take the lowest available number. Where both a held and a waiting call exist, the above procedures shall apply to the waiting call (i.e. not to the held call) in conflicting situation.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.5.5.2 Call Waiting (CW)
|
During a call, provided this service is active for the called party, if a second call attempts to make contact, a "call waiting" indication will be presented to the called party. To clear the current call and accept the waiting call, enter 1 followed by SEND, within the time out period. Alternatively, either party in the existing, active, call may release that call. The call waiting indication then becomes an "alert", and the call may be accepted as a normal call within the time-out period. To hold the current call and accept the waiting call, enter 2 followed by SEND, within the time out period. To ignore the waiting call, take no action. To set User Determined User Busy (UDUB) for the waiting call, enter 0 followed by SEND, within the time out period. To redirect the waiting call to another destination, enter 4 * "Directory Number" followed by SEND, within the time out period.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.5.5.3 Call hold
|
During a call, the initial call may be held while another call is made by entering the second directory number followed by SEND. To shuttle between the two calls enter 2 followed by SEND irrespective of whether the second call was acquired using the Call Hold or acceptance of Call Waiting procedures. If no waiting call exists, by entering 0 followed by SEND the held call is cleared. To clear an active call and return to the held call enter 1 followed by SEND. This is only possible if no waiting call exists.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.5.5.4 MultiParty
|
Having established calls to these two parties with one call active and the other on hold, enter 3 followed by SEND for a multiparty conversation. ETSI TS 100 907 V6.1.0 (1999-03) 19 GSM 02.30 version 6.1.0 Release 1997 To add another remote party, the same procedure applies. Another call is established and either this call or the existing multiparty call is placed on hold. Entering 3 followed by SEND brings all these parties together in an enlarged multiparty call. To choose one party for a private communication, putting the rest of the multiparty on hold, enter 2X followed by SEND, where X defines the call with which communication shall be supported. To return to the multiparty, with the previously active call placed on hold, enter 2 followed by SEND. To release a specific party enter 1X followed by SEND, where X is defined as above. If the served mobile subscriber enters END, all calls including the multiparty are released. The multiparty is terminated.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.5.5.5 Explicit Call Transfer
|
Having established calls to these two parties with one call active and the other on hold, enter 4 followed by SEND to transfer the calls. If a subscriber has one active, one held and one waiting call, and by entering 4 SEND the active and held call are connected, after the successful completion of the transfer, the served subscriber shall be offered the normal notification that there is a new waiting call, as for a normal terminating call.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.5.5.6 Special case
|
Provided both Call Hold and Call Waiting is active, it is possible to have one active and one held call and then a third call attempting to make contact. In this case, to clear the active call and accepting the waiting call (the held call not affected) enter 1 followed by SEND (If entering 2 followed by SEND the call state shall not be affected). Alternatively, either party in the active call may release that call. The held call will remain held. Within the time-out period the waiting call may then be accepted by entering 2 followed by SEND. It shall also be allowed to accept the waiting call by entering 1 followed by SEND. As and additional alternative, the (controlling) subscriber B may enter END, in which case the active and the held calls are released. The call waiting indication then becomes an "alert" and the previously waiting call may be accepted as a normal call within the time-out period.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.5.5.7 Call Deflection
|
If informed about an incoming call this call may be redirected to an another destination by entering 4 * "Directory Number" followed by SEND.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.5.5.8 Completion of calls to busy subscribers - $(CCBS)$
|
In a situation where a calling party A encounters busy of congestion on the B side, the network may offer the possibility to apply the CCBS supplementary service. If subscriber A, after being notified that CCBS is possible and during the period where the retention timer is running (minimum 15 seconds), enters 5 followed by SEND, this shall be interpreted as CCBS activation. Entering of 5 SEND by subscriber A in any other situation as described above shall not be interpreted as CCBS activation.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.5.6 Other handling of supplementary services
| |
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.5.6.1 Multiple Subscriber Profile - $(MSP)$
| |
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.5.6.1.1 Registering an alternative profile
|
An alternative profile is registered by entering the profile ID of the new profile, as illustrated: * 59n # SEND Where n is the identity of the profile desired. ETSI TS 100 907 V6.1.0 (1999-03) 20 GSM 02.30 version 6.1.0 Release 1997 An indication is given to the user showing whether this procedure was successful. The ID of the registered profile and other provisioned profiles may be determined by interrogation on entering *#59# SEND The profile so registered shall be used for all further MS originated activities and CISS operations unless another profile is selected, or an alternative profile is registered.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.5.6.1.2 Selecting an alternative profile on a per call basis
|
An alternative profile to the registered profile is selected by entering the profile ID of the new profile along with the desired Directory Number, as illustrated: * 59n # DN SEND Where n is the identity of the profile desired Continued processing of the call shall implicitly indicate that the selection was successful, there shall be no explicit indication given to the user concering successful execution this selection procedure. It is assumed that *# (i.e. interrogation) will not apply to call set-up.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.6 SIM interfaces
| |
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.6.1 Entry of PIN and PIN2
|
After insertion of the IC card while the MS is switched on, or when the MS is switched on while the IC card is inserted, or when the MS is switched on in the case of a plug-in SIM, an indication is given to the user that the PIN must be entered, unless the PIN is not applicable. If the user wishes to perform a function protected by PIN2, an indication shall be given to the user that PIN2 must be entered. The PIN or PIN2 being entered is not revealed in any way. The PIN or PIN2 check is performed by entering the # function.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.6.2 Change of PIN or PIN2
|
The following procedure permits the user to change the PIN or PIN2 in the SIM: PIN: **04*OLD_PIN*NEW_PIN*NEW_PIN# PIN2: **042*OLD-PIN2*NEW_PIN2*NEW_PIN2# Note that the SEND function is not used in these procedures. An indication is given to the user showing whether this procedure was successful.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.6.3 Unblocking of PIN or PIN2
|
The following procedure permits the user to unblock the PIN or PIN2: PIN: **05*PIN_UNBLOCKING_KEY*NEW_PIN*NEW_PIN# PIN2: **052*PIN2_UNBLOCKING_KEY*NEW_PIN2*NEW_PIN2# Note that the SEND function is not used in these procedures. The new PIN or PIN2 must be entered whether or not it is intended to change the PIN or PIN2. An indication is given to the user showing whether this procedure was successful. ETSI TS 100 907 V6.1.0 (1999-03) 21 GSM 02.30 version 6.1.0 Release 1997
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.6.4 Reading the abbreviated dialling code
|
An abbreviated dialling code shall be able to be read using the following procedure: N(N)(N)# Alternative additional procedures are also permitted.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.6.5 Status information - return codes
|
The SIM gives status information, as responses to instructions, in two-byte codes (see GSM 11.11 [21] clause "Status Conditions Returned by the Card"). Some of the possible return codes are deeply related to the user's actions and should therefore be indicated to her. It is mandatory to give the user the appropriate indication (respectively) when the following codes appear: code description; 92 40 - Memory Problem (eg. Update impossible); 98 04 - Access conditions not fulfilled (eg. secret code verify rejected); 98 40 - Unsuccessful CHV verification, no attempt left (eg. Secret code locked); 6F XX - Technical problem with no diagnostic given. The status information indication can be a dedicated lamp, text-string or others, as long as it is unambiguously made available to the user via the MMI. As regards all other codes, it is left to the manufacturers' discretion whether and how the user shall be informed.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
4.7 Presentation of IMEI
|
The following procedure shall instruct the ME to display its IMEI: *#06# The procedure shall be accepted and performed with and without an inserted SIM. The ME shall then display the 14 digits of the IMEI (not including the spare digit), the Check Digit and optionally the Software Version Number as defined in GSM 02.16 [6] (as a single string, in that order).
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
5 The basic public MMI
|
5.1 General In order to improve the standardization of the MMI for GSM Mobile Stations intended for general use by the public to access voice services, the following additional specification is provided. Equipment which meets the present document may quote "Approved to 02.30-Section 5" in its specification. This procedure is intended for Mobile Stations used by unfamiliar users, where instructions will be limited, for example in fleet cars, hire cars and payphones (cash, credit card, smart card, prepaid card, etc...). The organization providing the facility may require "Approved to 02.30-Section 5" as part of its procurement specification. The use of this clause 5 of the specification is not mandatory. Use of "Approved to 02.30 section 5" is restricted to Mobile Stations which pass Type Approval testing in respect to this clause. ETSI TS 100 907 V6.1.0 (1999-03) 22 GSM 02.30 version 6.1.0 Release 1997 A manufacturer who wishes his equipment to be tested to this section for approval must declare his requirement on submission. The present document covers the basic features of call origination and call termination. It specifies features which are mandatory for the Basic Public MMI. These are additional to the other clauses of GSM 02.30 which still apply and provision of additional features and facilities is not precluded unless otherwise stated. Guidelines for the application and design of pictographic instructions and the use of the symbol for telephone are to be found in CCITT Recommendation E.121 [24] (Red Book, Vol. II - Fasc. II.2).
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
5.2 Basic public MMI specific features
| |
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
5.2.1 Keyboard layout
|
- Layout of 12-keypad as per figure 5.2. - Layout of all other keys are optional. - Control key functions: No additional functions standardized (exception: see subclause 5.2.3). - Control key symbols: No additional standardization. - Control key positions: No requirements. 1 2 3 4 5 6 7 8 9 * 0 # Figure 5.2
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
5.2.2 Number entry
|
- No restriction on number entry or editing.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
5.2.3 Call control
|
- A hand-set shall be present to place and receive calls. - SEND and END function keys are mandatory for execution of call initiation/termination respectively.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
5.2.4 Call acceptance
|
- On receiving "Ring Alert", the user may lift the hand-set "Off Hook" or press the SEND-function key.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
5.2.5 Call initiation
|
ETSI TS 100 907 V6.1.0 (1999-03) 23 GSM 02.30 version 6.1.0 Release 1997
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
5.2.5.1 "Off Hook" call initiation
|
1) Lift the hand-set "Off Hook" - Dial tone is presented. 2) Enter number. Dial tone is cancelled after entry of the first digit (including * and #). 3) Press SEND-function key. 4) If the unit is "Off Hook" and the SEND-function key is not pressed, call set up may be automatically initiated after expiry of a time-out of 5 seconds. The time-out shall be restarted after every digit entry. 5) The call initiation is stopped by replacing the hand-set "On Hook".
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
5.2.5.2 "On Hook" call initiation
|
Time-out dialling in "On Hook" - mode is not allowed for mobiles fitted with an "On Hook" dialling feature.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
5.2.6 Call termination
|
- The call is terminated by replacing the hand-set "On Hook" or by pressing the END-function key. - The call may also be terminated by e.g. replacing "On Hook" by B-party, radio path interruption and invalidation of payment.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
5.2.7 Supplementary services control
|
The primary function of the * and # on the Basic Public MMI will be for control of supplementary services in accordance with the procedures defined in subclause 4.5. of the present document.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
5.2.8 Payment
|
If the MS requires to be set up with some means of payment e.g. cash, prepaid card or credit card, a "payment indication" will be presented to the user when payment is required at the initial step (see subclause 5.2.5, Call Initiation Steps). When a call is in progress and payment which has been made is nearly used up, the payment indication shall be presented again inviting the user to make further payment. When sufficient payment has been entered the payment indication shall be switched off. The requirement for payment prior to the origination of an emergency call is not precluded.
|
752c9139d9e1304cc597ae9d738009a7
|
100 907
|
5.2.9 Country/PLMN selection
|
(For definition, see GSM 02.07 [3]). PLMN selection shall be in accordance with GSM 02.11 [4], but "automatic" shall be the default mode. ETSI TS 100 907 V6.1.0 (1999-03) 24 GSM 02.30 version 6.1.0 Release 1997 Annex A (normative): MS access mealy graph MS - OFF Enter- card Enter- PIN Serv -AV Enter - PLMN Failure - Treatment WAIT Co nd itional OK Complete REQ REQ IOC ON Failure "DONE" REQ Entered 5 6 7 4 2 3 1 Figure A.1: Mealy-graph for the ms access procedure Assumptions and requirements: 1) Emergency calls shall be possible in all states, except in state 1. 2) Power-off should cause transition to state 1 from all other states. 3) The actions to be taken in state 5 is not defined. 4) Basic requirements concerning indications and procedures for the different states are given in specifications GSM 02.07 [3], 02.11 [4], 02.17 [5] and 02.40 [7]. 5) Additional indications to those in item 4 above may be given in all states and at all events. 6) Realization of the dotted states (3, 4 and 6) depends upon the network requirements and the type of MS. Description of the states of the MS access procedure 1) MS-OFF: The MS is in OFF-condition. This means that the equipment is not active as an MS in a GSM PLMN. 2) WAIT: Waiting for the completion of the MS access conditions, which are related to the type of MS and to the GSM PLMN, where in the MS is roaming (e.g. location updating). 3) ENTER CARD: Request for entering of the subscriber card, (e.g. when no built in SIM module is available). 4) ENTER PIN: Request for entering of the correct PIN. 5) FAILURE TREATMENT: Waiting for removal the actual failure condition. ETSI TS 100 907 V6.1.0 (1999-03) 25 GSM 02.30 version 6.1.0 Release 1997 6) ENTER PLMN: Request for selection of PLMN. 7) SERV-AV: The MS is in a ready state. PLMN services are available to the user. Description of the transitions between MS access states ON: The equipment becomes active as an MS in a GSM PLMN. REQ: A request for user activity. IOC: Insertion of a subscriber card with SIM-module. COMPLETE: The PIN has been entered. ENTERED: A PLMN choice has been done. FAILURE: A failure condition has occurred in any other state during the MS access procedures. CONDITIONAL: One of the conditions the MS is waiting for in WAIT state has been lost. The MS goes back to the WAIT state. "DONE": The MS access failure condition has been corrected. OK: All the conditions the MS is waiting for in the WAIT state are accomplished. ETSI TS 100 907 V6.1.0 (1999-03) 26 GSM 02.30 version 6.1.0 Release 1997 Annex B (normative): Codes for defined Supplementary Services Table B.1: Input information for handling of defined Supplementary Services Supplementary Service Service Code SIA SIB SIC 02.67 eMLPP 75 and 75n where n=0-4 02.72 CD 66 02.81 CLIP 30 - - - CLIR 31 - - - COLP 76 - - - COLR 77 - - - In temporary mode, to suppress CLIR for a single call, enter: " * 31 # <called number> SEND " In temporary mode, to invoke CLIR for a single call enter: " # 31 # <called number> SEND " 02.82 CFU 21 DN BS - CF Busy 67 DN BS - CF No Reply 61 DN BS T CF Not Reachable 62 DN BS - all CF 002 DN BS T all conditional CF 004 DN BS T 02.83 WAIT 43 BS - - see section 4.5.5 HOLD see section 4.5.5 02.84 MPTY see section 4.5.5 02.87 UUS Service 1 361 R - - UUS Service 2 362 R - - UUS Service 3 363 R - - all UUS Services 360 R - - If UUS shall be activated when originating a call, enter: " * 36X * R # <called number> SEND" (X is indicating the requested UUS service) ETSI TS 100 907 V6.1.0 (1999-03) 27 GSM 02.30 version 6.1.0 Release 1997 Table B.1(concluded): Input information for handling of defined Supplementary Services Supplementary Service Service Code SIA SIB SIC 02.88 BAOC 33 PW BS - BAOIC 331 PW BS - BAOIC exc home 332 PW BS - BAIC 35 PW BS - BAIC roaming 351 PW BS - all Barring Serv. 330 PW BS - Outg. Barr. Serv. 333 PW BS Inc. Barr. Serv. 353 PW BS 02.91 ECT 96 see section 4.5.5 $(CCBS)$: 02.93 CCBS 37 n See Section 4.5.5 where n=1-5 $(SPNP)$: 02.95 SPNP 07n where n=0-9 $(CNAP)$: 02.96 CNAP 300 - - - $(MSP)$: 02.97 MSP 59n PW where n=1-4 DN = Directory Number; PW = Password (see subclause 4.5.4); BS = Basic Service Group (if required) - see annex C; T = No Reply Condition Timer (5-30 seconds); R = UUS required option. SI required Y = Yes; N = No; - = Not applicable. "UUS required" option For the "UUS required" option two values are defined: R = 0 UUS not required; R = 1 UUS required. NOTE: If the "UUS required" option is requested for a call, the call will only be established if the requested UUS capabilities are available. If the "UUS required" option is not contained in an activation request UUS shall be activated without the UUS required option. ETSI TS 100 907 V6.1.0 (1999-03) 28 GSM 02.30 version 6.1.0 Release 1997 Annex C (normative): Codes for Tele- and bearer services Tele- and Bearer Service Supplementary Information codes (SIb). Alternate and speech/data services are included with the equivalent data service. Basic Service group number (note) Telecommunication Service MMI Service Code 1 to 12 All tele and bearer services no code required Teleservices 1 to 6, 12 All teleservices 10 1 Telephony 11 2 to 6 All data teleservices 12 6 Facsimile services 13 2 Short Message Services 16 1, 3 to 6, 12 All teleservices except SMS 19 12 Voice group services Voice Group Call Service (VGCS) 17 Voice Broadcast Service (VBS) 18 Bearer Service 7 to 11 All bearer services 20 7, 9 All async services 21 8, 10 All sync services 22 8 All data circuit sync 24 7 All data circuit async 25 10 All dedicated packet access 26 9 All dedicated PAD access 27 13 All GPRS bearer services 99 NOTE: See GSM 02.04 [2] for definition of Basic Service groups. The grouping implies that if e.g. code 25 is used, the Supplementary Service procedure concerned applies to all Asynchronous Data Circuit mode Bearer Services subscribed to. ETSI TS 100 907 V6.1.0 (1999-03) 29 GSM 02.30 version 6.1.0 Release 1997 Tele-and Bearer Service Supplementary Information Codes (SIb) for services not defined by GSM Code as defined Telecommunication Service MMI Service in GSM 09.02 [19] Code PLMN specific teleservices: 11010000 All PLMN specific teleservices 50 11010001 PLMN specific teleservice 1 51 11010010 PLMN specific teleservice 2 52 11010011 PLMN specific teleservice 3 53 11010100 PLMN specific teleservice 4 54 11010101 PLMN specific teleservice 5 55 11010110 PLMN specific teleservice 6 56 11010111 PLMN specific teleservice 7 57 11011000 PLMN specific teleservice 8 58 11011001 PLMN specific teleservice 9 59 11011010 PLMN specific teleservice 10 60 11011011 PLMN specific teleservice 11 61 11011100 PLMN specific teleservice 12 62 11011101 PLMN specific teleservice 13 63 11011110 PLMN specific teleservice 14 64 11011111 PLMN specific teleservice 15 65 PLMN specific bearer services: 11010000 All PLMN specific bearer services 70 11010001 PLMN specific bearer service 1 71 11010010 PLMN specific bearer service 2 72 11010011 PLMN specific bearer service 3 73 11010100 PLMN specific bearer service 4 74 11010101 PLMN specific bearer service 5 75 11010110 PLMN specific bearer service 6 76 11010111 PLMN specific bearer service 7 77 11011000 PLMN specific bearer service 8 78 11011001 PLMN specific bearer service 9 79 11011010 PLMN specific bearer service 10 80 11011011 PLMN specific bearer service 11 81 11011100 PLMN specific bearer service 12 82 11011101 PLMN specific bearer service 13 83 11011110 PLMN specific bearer service 14 84 11011111 PLMN specific bearer service 15 85 ETSI TS 100 907 V6.1.0 (1999-03) 30 GSM 02.30 version 6.1.0 Release 1997 Annex D (informative): Change Request History Change history SMG No. TDoc. No. CR. No. Section affected New version Subject/Comments SMG#14 235/95 Delta 4.5.5,Ann B 5.0.0 Provision for ECT SMG#17 047/96 052/96 A005 A003r1 4.5.3.2 Ann C 5.1.0 Handling of user input by the ME Service group number for VGCS and VBS SMG#18 219/96 222/96 A007 A006 4.5.1,4.5.5 Annex B Annex B 5.2.0 MMI for call associated SS control MMI for UUS SMG#19 362/96 512/96 371/96 A010 A011 A008r1 4.5.5.1,4.5.5.2, 4.5.5.7 5.5 4.4.2.2 5.3.0 MMI for Call Deflection Clarification of the meaning of the MMI 5 SEND Support of Additional Call Set-up MMI Procedures UAP 5.3.1 UAP 58: 1996-11-18 to 1997-03-14 SMG#21 168/97 A014 A015 Annex B 4.5.3.2 5.4.0 $(CCBS)$ Clarification of the MMI for CCBS Correction of the Handling of MMI by the MS SMG#22 301/97 A016 4.5.5.1 Annex B 5.5.0 $(CCBS)$ is added to Title Call Transfer is renamed to explicit Call Transfer SMG#22 306/97 A017 4.5.6 Added 5.5.0 Other Handling of Supplementary Services: Add MSP MMI SMG#23 793/97 (same as 654/97) A018 Annex B 5.6.0 $(CNAP)$: The Table of Codes for defined Supplementary Services in Annex B is modified. The change request has defined the CNAP MMI Code as 300. (Version used is 5.5.1 CR indicates V5.3.1 !!) SMG#23 651/97 A019 4.5.6 and Annex B revised pages: 21 and 31 5.6.0 $(MSP)$: Clarification of registration and selection procedures for MSP Correction of Table in Annex B: Codes for defined Supplementary Services SMG#23 651/97 A020 Annex B, Revised page: 27 5.6.0 $(CCBS)$: MMI procedure to handle CCBS service is clarified. By indicating the # of an outstanding CCBS request the subscriber has the possibility to deactivate this specific CCBS request. SMG#24 1149/97 (Replaced 974/97) A021r1 Scope Section and 0.3 - Note 3 added. 5.6.1 This CR introduces an appropriate definition of the Directory Number. SMG#25 6.0.0 Creation of version 6.0.0 as part of GSM release 1997 SMG#28 028/99 A024 Annex C 6.1.0 Separate MMI codes for VGCS and VBS: - UIC MORANE prefers a separate service code for both VBS and VGCS and not the combined one (17) as presently defined in GSM 02.30. The use of the group call reference is not sufficient. SMG#28 031/99 A022 Annex C 6.1.0 Addition of Supplementary Service Code for GPRS ETSI TS 100 907 V6.1.0 (1999-03) 31 GSM 02.30 version 6.1.0 Release 1997 History Document history V6.0.1 July 1998 Publication V6.1.0 March 1999 Publication ISBN 2-7437-2924-4 Dépôt légal : Mars 1999
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
1 Scope
|
This Technical Specification describes the Cell Broadcast short message service (CBS). It defines the primitives over the Cell Broadcast Centre - Base Station System (CBC-BSS) interface and the message formats over the Base Station System - Mobile Station (BSS-MS) interface for Teleservice 23 as specified in GSM 02.03 [2].
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
1.1 Normative references
|
References may be made to: a) specific versions of publications (identified by date of publication, edition number, version number, etc.), in which case, subsequent revisions to the referenced document do not apply; or b) all versions up to and including the identified version (identified by "up to and including" before the version identity); or c) all versions subsequent to and including the identified version (identified by "onwards" following the version identity); or d) publications without mention of a specific version, in which case 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. [1] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms". [2] GSM 02.03: "Digital cellular telecommunication system (Phase 2+); Teleservices supported by a GSM Public Land Mobile Network (PLMN)". [3] GSM 03.38: "Digital cellular telecommunication system (Phase 2+);"Alphabets and language- specific information". [4] GSM 03.40: "Digital cellular telecommunication system (Phase 2+); Technical realization of the Short Message Service (SMS) Point to Point (PP)". [5] GSM 03.47: "Digital cellular telecommunication system (Phase 2+); Example protocol stacks for interconnecting Service Centre(s) (SC) and Mobile-services Switching Centre(s) (MSC)". [6] GSM 03.49: "Digital cellular telecommunication system (Phase 2+); Example protocol stacks for interconnecting Cell Broadcast Centre (CBC) and Mobile-services Switching Centre (MSC)". [7] GSM 04.12: "Digital cellular telecommunication system (Phase 2+); Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface". [8] GSM 05.02: "Digital cellular telecommunication system (Phase 2+); Multiplexing and multiple access on the radio path". [9] GSM 07.05: "Digital cellular telecommunication system (Phase 2+); Use of Data Terminal Equipment - Data Circuit terminating Equipment (DTE - DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS)". [10] GSM 08.52: "Digital cellular telecommunication system (Phase 2+); Base Station Controller - Base Transceiver Station (BSC - BTS) interface Interface principles". [11] GSM 08.58: "Digital cellular telecommunication system (Phase 2+); Base Station Controller - Base Transceiver Station (BSC - BTS) interface Layer 3 specification". [12] CCITT Recommendation X.210: "Open systems interconnection layer service definition conventions". ETSI TS 100 902 V6.1.0 (1998-07) 7 GSM 03.41 version 6.1.0 Release 1997
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
1.2 Abbreviations
|
Abbreviations used in this TS are listed in GSM 01.04 [1].
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
2 General description
|
The CBS service is analogous to the Teletex service offered on television, in that like Teletex, it permits a number of unacknowledged general messages to be broadcast to all receivers within a particular region. CBS messages are broadcast to defined geographical areas known as cell broadcast areas. These areas may comprise of one or more cells, or may comprise the entire PLMN. Individual CBS messages will be assigned their own geographical coverage areas by mutual agreement between the information provider and the PLMN operator. CBS messages may originate from a number of Cell Broadcast Entities (CBEs), which are connected to the Cell Broadcast Centre. CBS messages are then sent from the CBC to the BTSs, in accordance with the CBS's coverage requirements. The CBS message comprises of 82 octets, which, using the default character set, equates to 93 characters. Up to 15 of these messages (pages) may be concatenated to form a macromessage. Each page of such macromessages will have the same message identifier (indicating the source of the message), and the same serial number. Using this information, the MS is able to identify and ignore re-broadcasts of already received messages. CBS messages are broadcast cyclically by the BTS at a frequency and for a duration specified by the information provider. The frequency at which messages are repeatedly transmitted will be dependent on the information that they contain; for example, it is likely that dynamic information such as road traffic information, will require more frequent transmission than weather information. The repetition period will also be affected by the desire for messages to be received by high speed mobiles which rapidly traverse cells. All suitably equipped mobiles within the catchment area of the transmitting BTS will be able to receive the broadcast messages, provided that they are switched on and in the idle state. CBS messages may be broadcast on two different cell broadcast channels, which are characterized by different QoS. A MS is always able to read the basic channel (see [8]). The reading of the extended channel may collide with other tasks of the MS. Therefore the probability of receiving a CBS message on the extended channel is smaller than on the basic channel. The reading of the extended channel for MSs is optional. The scheduling on the channels will be done independently. To permit mobiles to selectively display only those messages required by the MS user, CBS messages are assigned a message class which categorises the type of information that they contain and the language in which the message has been compiled. Through the use of appropriate MMI, the user is then able to ignore message types that he does not wish to receive, e.g. advertising information or messages in an unfamiliar language.
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
3 Network Architecture
|
The basic network structure of CBS is depicted by figure 1. ETSI TS 100 902 V6.1.0 (1998-07) 8 GSM 03.41 version 6.1.0 Release 1997 CBC CBE CBE BSC BTSs MSs MSs MSs 1 1 2 2 2 3 3 3 4 4 4 outside scope of GSM Specs. inside scope of GSM Specs. Figure 1 - message transfer on link 1 is outside the scope of GSM Specifications; - message transfer on link 2 is described in subclause 9.1; - message transfer on link 3 is described in GSM 08.58; - message transfer on link 4 is described in GSM 04.12 and the timing of messages transferred on link 4 is described in GSM 05.02.
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
4 CBE Functionality
|
The functionality of the CBE is outside of the scope of GSM Specifications; however it is assumed that the CBE is responsible for all aspects of formatting CBS, including the splitting of a CBS message into a number of pages.
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
5 CBC Functionality
|
As the CBC (and any originating point for cell broadcast short messages) is regarded as a node outside the PLMN, only the requirements placed upon the CBC by CBS functionality are specified by this specification. The CBC may be connected to several BSCs. The CBC may be connected to several CBEs. The CBC shall be responsible for the management of cell broadcast short messages including: - allocation of serial numbers; - modifying or deleting messages held by the BSC; - initiating broadcast by sending fixed length cell broadcast short messages to a BSC for each language provided by the cell, and where necessary padding the message with the appropriate character to a length of 82 octets; - determining the set of cells/BTSs to which a message should be broadcast, and indicating within the Serial Number the geographical scope of each message; - determining the time at which a message should commence being broadcast; - determining the time at which a message should cease being broadcast and subsequently instructing each BSC to cease broadcast of the message; - determining the period at which broadcast of the message should be repeated; ETSI TS 100 902 V6.1.0 (1998-07) 9 GSM 03.41 version 6.1.0 Release 1997 - determining the cell broadcast channel, on which the message should be broadcast. To work efficiently on the interfaces, the BSC - which is normally controlling more than one cell of a broadcast area - should be used as a concentrator as far as CB message handling is concerned. Hence, the CBC should work on lists of cells when issuing CB related requests towards the BSC.
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
6 BSC Functionality
|
The BSC shall interface to only one CBC. A BSC may interface to several BTSs as indicated by GSM 08.52. The BSC shall be responsible for: - interpretation of commands from the CBC; - storage of cell broadcast messages; - scheduling of cell broadcast messages on the CBCH; - providing an indication to the CBC when the desired repetition period cannot be achieved; - providing to the CBC acknowledgement of successful execution of commands received from the CBC; - reporting to the CBC failure when a command received from the CBC is not understood or cannot be executed; - routing cell broadcast messages to the appropriate BTSs; - transferring CBS information to each appropriate BTS via a sequence of 4 SMS BROADCAST REQUEST messages or 1 SMS BROADCAST COMMAND message (see GSM 08.58), indicating the channel which shall be used. - optionally generating Schedule Messages, indicating the intended schedule of transmissions (see GSM 04.12); - optionally receiving CBCH Load Indication messages and reacting by broadcasting a burst of scheduled SMSCB messages or by suspending the broadcast for a period indicated by BTS (see GSM 08.58); To work efficiently on the interfaces, the BSC should forward CB related messages to the CBC using cell lists as far as applicable.
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
7 BTS Functionality
|
The BTS is responsible for conveying CBS information received via SMS BROADCAST REQUEST or SMS BROADCAST COMMAND messages over the radio path to the MS. - optionally generating CBCH Load Indication messages, indicating an underflow or overflow situation on the CBCH (see GSM 08.58).
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
8 MS Functionality
|
The MS is responsible for recombination of the blocks received via the radio path to reconstitute the cell broadcast short message. The precise method of display of cell broadcast short messages is outside the scope of GSM Specifications, however it is assumed that an MS will: - discard sequences transferred via the radio path (see GSM 04.12) which do not consist of consecutive blocks; - have the ability to discard CBS information which is not in a suitable data coding scheme; - have the ability to discard a message which has a message identifier indicating that it is of subject matter which is not of interest to the MS; ETSI TS 100 902 V6.1.0 (1998-07) 10 GSM 03.41 version 6.1.0 Release 1997 - have the ability to ignore repeat broadcasts of messages already received (message has not changed since it was last broadcast i.e. sequence number has not changed within the message's indicated geographical area); - have the ability to transfer a message via the R interface when the R interface is supported; - optionally enter SMSCB DRX mode based upon received Schedule Messages (see GSM 04.12); - optionally skip reception of the remaining block(s) of a cell broadcast message which do(es) not contain cell broadcast information (see GSM 04.12); - optionally read the extended channel.
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
9 Protocols and Protocol Architecture
|
Commands interpreted by the BSC will result in a sequence of 4 SMS BROADCAST REQUEST messages or 1 SMS BROADCAST COMMAND message being sent to a BTS, which in turn result in a sequence of 4 messages being transferred via the BTS-MS interface (see GSM 04.12). With the SMS BROADCAST REQUEST mode of operation, the 88 octet fixed length CBS page which is specified in Section 9.3 is split into four 22 octet blocks which are carried in SMS BROADCAST REQUEST messages as follows: octets 1-22 are transferred in the 1st SMS BROADCAST REQUEST with a sequence number (see GSM 04.12) indicating first block octets 23-44 are transferred in the 2nd SMS BROADCAST REQUEST with a sequence number (see GSM 04.12) indicating second block octets 45-66 are transferred in the 3rd SMS BROADCAST REQUEST with a sequence number (see GSM 04.12) indicating third block octets 67-88 are transferred in the 4th SMS BROADCAST REQUEST with a sequence number (see GSM 04.12) indicating fourth block. Figure 2 illustrates the protocol architecture and the scope of the various GSM Specifications for the SMS BROADCAST REQUEST mode of operation. ETSI TS 100 902 V6.1.0 (1998-07) 11 GSM 03.41 version 6.1.0 Release 1997 GSM 08.58 GSM 04.12 GSM 03.41 Section 9.3 GSM 03.41 Section 9.1 CBC BSC BTS MSs Write-Replace Report-Success SMS BROADCAST REQUEST 1 SMS BROADCAST REQUEST 2 SMS BROADCAST REQUEST 3 SMS BROADCAST REQUEST 4 1 2 3 4 Figure 2 With the SMS BROADCAST COMMAND mode of operation, the BSC sends to the BTS in one single message the 88 octet fixed length CBS page. The BTS then splits the page into four 22 octet blocks, adds the sequence number (see GSM 04.12) and transmits the four resulting blocks on the air. Figure 3 illustrates the protocol architecture and the scope of the various GSM Specifications for the SMS BROADCAST COMMAND mode of operation. ETSI TS 100 902 V6.1.0 (1998-07) 12 GSM 03.41 version 6.1.0 Release 1997 GSM 08.58 GSM 04.12 GSM 03.41 Section 9.3 GSM 03.41 Section 9.1 CBC BSC BTS MSs Write-Replace Report-Success SMS BROADCAST COMMAND 1 2 3 4 Figure 3
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
9.1 CBC-BSC Primitives
|
The term primitive is used to indicate "an abstract, implementation independent interaction between a service user and a service provider" (see CCITT X.210). For the CBC-BSC interface, the service provider would be the protocol interconnecting CBC and BSC. A Primitive may therefore be viewed as an abstract, implementation independent request/indication or response/confirm interaction between the service user (CBC or BSC) and the service provider (protocol). A set of primitives for use between the CBC and BSC is specified appropriate to the functionality assigned to the CBC and BSC in Sections 5 and 6. In order to allow future extensions to the primitives, where possible a primitive shall not be rejected because a parameter is not recognised; the recipient shall ignore the parameter in question and process the remainder of the primitive’s parameters as usual. No mandatory protocol between the CBC and the BSC is specified by GSM, this is a matter of agreement between CBC and PLMN operators. GSM 03.49 (see also annex A of this TS) provides example protocol stacks using the primitives defined as follows. NOTE: In the following definitions, M indicates "mandatory parameter" and O indicates "optional parameter".
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
9.1.1 Identification of a message
|
Within a CBC-BSC interface, a message is uniquely identified by the quartet (message_identifier, serial_number, Cell Identifier, Channel Indicator). This means that even when two messages have the same semantic containts (for example the same weather forecast) but in different languages or coding schemes, they are considered as different and must therefore be identified by a different quartet. The serial number is managed cyclically and therefore this does not prevent the re-use of the same quartet for a different message when the serial number have been incremented a sufficient number of times. How to manage the ambiguity is described subsequently. This unique identification of a message across the CBC-BSC interface is used in all the primitives defined hereafter. This means that the quartet will be implicitly or explicitly present in every interface primitive which applies to a given message. ETSI TS 100 902 V6.1.0 (1998-07) 13 GSM 03.41 version 6.1.0 Release 1997 This unique quartet will be referred in the rest of the document as the « message reference ».
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
9.1.2 WRITE-REPLACE Request/Indication
|
PARAMETER REFERENCE PRESENCE Message-Identifier 9.2.1 M Old-Serial-Number 9.2.2 O New-Serial-Number 9.2.3 M Cell-List 9.2.5.1 M Channel Indicator 9.2.6 O Category 9.2.7 O Repetition-Period 9.2.8 M No-of-Broadcasts-Requested 9.2.9 M Number-of-Pages 9.2.4 M Data Coding Scheme 9.2.18 M CBS-Message-Information-Page 1 9.2.19 M CBS-Message-Information-Length 1 9.2.20 M CBS-Message-Information-Page 2 9.2.19 O CBS-Message-Information-Length 2 9.2.20 O : : CBS-Message-Information-Page n 9.2.19 O CBS-Message-Information-Length n 9.2.20 O This primitive is sent by the CBC to the BSC. As this primitive can be used either to broadcast a new message or replace a message already broadcast, the CBC will use the presence and content of the Old-Serial-Number and New-Serial- Number fields in this primitive to instruct the BSC as follows:- - Old-Serial-Number not present/New-Serial-Number present This is a write request which will be interpreted by the BSC as an instruction to broadcast a new message in all the cells of the Cell list and on the channel derived by the Channel Indicator (see the section on parameters that describes the implicit value of the Channel Indicator when not present in the message). The following table identifies the BSC’s behaviour: Success/Failure of write request BSC behaviour Success The BSC completes the following parameters to be returned in the Report PDU: • a ‘0’ value is entered in the number of broadcasts completed list for the cell • no entry is made in the failure list for the cell Failure The BSC completes the following parameters to be returned in the Report PDU: • no entry is made in the number of broadcasts completed list for the cell • an entry is made in the failure list for the new message identifying the failure cause for the cell The BSC will build as many message references as the number of cells in the list. These message references will be used in particular in the subsequent primitives. When a message reference is already known by the BSC for certain cells in the list (even if the Update field of the Serial-Number is different), the primitive will be rejected with the cause « message reference already used ». The list of cells where the message reference is not valid will be provided in the REPORT message. No entry will be made in the number of broadcasts completed parameter. ETSI TS 100 902 V6.1.0 (1998-07) 14 GSM 03.41 version 6.1.0 Release 1997 - Old-Serial-Number present/New-Serial-Number present This is a replace request which will be interpreted by the BSC as a kill request for the message with the old serial number, followed by a write request for the message with the new serial number. The handling of the new serial number in the write part of this request, is as described above in the write request where no Old-Serial-Number is supplied. These two kill and write requests are executed sequentially. If the kill request is unsuccessful, the BSC does not proceed to execute the write request. The kill request will stop broadcast of, and cause all information currently associated with the combination of message identifier, old serial number, Channel Indicator and the list of cells in the Cell list to be deleted from the cells in the BSC (i.e. for all cells provided in the Cell- List parameter). If the kill request is successful, the subsequent write request information conveyed in the primitive replaces the killed message. The following table identifies the BSC’s behaviour: Success/Failure of kill request BSC behaviour Success The BSC proceeds to execute the write request: • Write successful: the BSC completes the following parameters to be returned in the Report PDU: • an entry is made in the number of broadcasts completed list for the cell • no entry is made in the failure list for the cell • Write unsuccessful: the BSC completes the following parameters to be returned in the Report PDU: • an entry is made in the number of broadcasts completed list for the cell • an entry is made in the failure list for the new message identifying the failure cause for the cell Failure The BSC does not proceed to execute the write request, and completes the following parameters to be returned in the Report PDU: • no entry is made in the number of completed broadcasts list • an entry is made for the old message in the failure list identifying the failure cause for the cell All cells which should perform the broadcasting are mentioned in the Cell-List parameter. The broadcast of the referenced message in the cells which are not mentioned in the Cell-List remains unaffected. If no category is present, the default category is interpreted by the BSC, see the parameter section. This primitive is responded by a REPORT or REJECT primitive. NOTE: in the case of multipage messages, the individual pages are considered as independent by the BSC scheduling algorithm.
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
9.1.3 KILL Request/Indication
|
PARAMETER REFERENCE PRESENCE Message-Identifier 9.2.1 M Old-Serial-Number 9.2.2 M Cell-List 9.2.5.1 M Channel Indicator 9.2.6 O ETSI TS 100 902 V6.1.0 (1998-07) 15 GSM 03.41 version 6.1.0 Release 1997 This primitive is sent by the CBC to the BSC. The CBC will use this primitive to kill the message indicated by the combination of message identifier, serial number, Channel Indicator and the cells indicated in the Cell-List of this KILL request, i.e. the primitive will halt broadcast of the message in the indicated cells and remove any knowledge of the message from the BSC for these cells. The broadcast of the referenced message in the cells which are not mentioned in the Cell-List remains unaffected. This primitive is responded with a REPORT or REJECT primitive.
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
9.1.4 REPORT Response/Confirm
|
PARAMETER REFERENCE PRESENCE Message-Identifier 9.2.1 M Serial-Number 9.2.2 M Channel Indicator 9.2.6 O No-of-Broadcasts-Completed-List 9.2.10 O Failure-List 9.2.14 O This primitive will be sent by the BSC to the CBC in response to WRITE-REPLACE and KILL primitives. The Serial- Number field will contain the old serial number if this primitive is sent in response to a KILL primitive, and the new serial number if the primitive is sent in response to a WRITE-REPLACE primitive. The No-of-Broadcasts-Completed-List if present, may contain for each cell the number of broadcasts of the (replaced or killed) CB message with the old message reference sent to this particular cell for broadcast. The serial number information element in the case of a WRITE-REPLACE does not refer to the message for which the number of broadcasts completed information is supplied. The Failure-List if present, may contain those cells which were present in the related WRITE-REPLACE or KILL primitive and failed the requested operation.
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
9.1.5 STATUS-CBCH-QUERY Request/Indication
|
PARAMETER REFERENCE PRESENCE Cell-List 9.2.5.1 M Channel Indicator 9.2.6 O This primitive is sent by the CBC to the BSC in order to obtain the current loading of the CBCH of particular cells referenced in the Cell-List parameter. This primitive is responded by a STATUS-CBCH-QUERY Response/Confirm or a REJECT primitive.
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
9.1.6 STATUS-CBCH-QUERY Response/Confirm
|
PARAMETER REFERENCE PRESENCE CBCH-Loading-List 9.2.15 O Failure-List 9.2.14 O Channel Indicator 9.2.6 O This primitive will be sent by the BSC in response to the STATUS-CBCH-QUERY Request/Indication primitive. The CBCH-Loading-List, if present, may contain each cell which successfully performed the requested operation and for each of these cells the CBCH loading of this particular cell. (Note that for cells with DRX the load caused by the schedule messages will be included in the CBCH load). The CBCH-Loading-List will not be present if all cells indicated in the related STATUS-CBCH-QUERY Request/Indication failed the requested operation. The Failure-List, if present, may contain all cells for which the requested operation failed (e.g. because the cells CBCH is not available). The STATUS-CBCH-QUERY Response/Confirm will not contain the Failure-List parameter if none of the cells in the Cell-List of the related STATUS-CBCH-QUERY Request failed the requested operation. ETSI TS 100 902 V6.1.0 (1998-07) 16 GSM 03.41 version 6.1.0 Release 1997
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
9.1.7 STATUS-MESSAGE-QUERY Request/Indication
|
PARAMETER REFERENCE PRESENCE Message-Identifier 9.2.1 M Old-Serial-Number 9.2.2 M Cell-List 9.2.5.1 M Channel Indicator 9.2.6 O This primitive is sent by the CBC to the BSC in order to obtain the current status of a CB-message for the cells referenced in the Cell-List parameter. This primitive is responded by the STATUS-MESSAGE-QUERY Response/Confirm or by a REJECT Response/Confirm.
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
9.1.8 STATUS-MESSAGE-QUERY Response/Confirm
|
PARAMETER REFERENCE PRESENCE Message-Identifier 9.2.1 M Old-Serial-Number 9.2.2 M No-of-Broadcasts-Completed-List 9.2.10 O Failure-List 9.2.14 O Channel Indicator 9.2.6 O This primitive will be sent by the BSC to the CBC in response to a STATUS-MESSAGE-QUERY Request/Indication primitive. The No-of-Broadcasts-Completed-List, if present, may contain each cell which successfully performed the requested operation and for each of these cells the number of times this CB message has been sent to this particular cell for broadcast (parameter Number-of-Broadcasts-Completed; this parameter is not included for the cell if the old message reference is not known to the BSC, and an entry is made in the failure list). The No-of-Broadcasts-Completed-List will not be present if all cells indicated in the related STATUS-MESSAGE-QUERY Request failed the requested operation. The Failure-List may contain all cells for which the requested operation failed (e.g. because the broadcast of the requested message was never requested before or because the cells CBCH is not available). The STATUS-MESSAGE- QUERY Response/Confirm will not contain the Failure-List parameter if none of the cells in the Cell-List of the related STATUS-MESSAGE-QUERY Request failed the requested operation.
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
9.1.9 REJECT Response/Confirm
|
PARAMETER REFERENCE PRESENCE Cause 9.2.16 M Diagnostic 9.2.17 O Message-Identifier 9.2.1 O Serial Number 9.2.2 O This primitive is sent by the BSC to the CBC in response to any primitive which is not understood (e.g. invalid parameter or parameter value).
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
9.1.10 RESTART-INDICATION Request/Indication
|
PARAMETER REFERENCE PRESENCE Cell-List 9.2.5.2 M Recovery Indication 9.2.20 O The RESTART-INDICATION Request is used by the BSC to indicate to the CBC a CB related restart situation in one or more of its cells (e.g. when an existing or a new cell becomes operational during normal BSC operation or when the BSC initialises). Any referenced cell are again in CB-operational state (have resumed CB operation). The parameter Recovery Indication, if present, indicates whether CB related data are lost for the cells referenced in the Cell-List and have to be re-loaded. If ETSI TS 100 902 V6.1.0 (1998-07) 17 GSM 03.41 version 6.1.0 Release 1997 the Recovery Indication parameter is absent, the CBC shall interpret it as the Recovery Indication with the value data lost. The CBC upon receiving a RESTART INDICATION indication, marks the cell as operational again. It will usually generate WRITE-REPLACE requests for this cell, according to the actual CB message loading at the moment of the restart. Note that a RESTART INDICATION indication may be triggered from the CBC by a RESET Request. This allows to recover from situations, where a PDU occasionally may be lost.
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
9.1.11 RESET Request/Indication
|
PARAMETER REFERENCE PRESENCE Cell-List 9.2.5.1 M The RESET Request is used by the CBC to force one or more cells (BTSs) of one BSC into CB-idle state. The RESET Request may also be used by the CBC to ask for the CB operational state of cells earlier indicated to have failed (polling CB operational state). If a base station controller (BSC) receives a RESET Indication, the indicated cells enter idle state (same state as after "power on"). All CB related information concerning earlier CB messages in a referenced cell is lost. The BSC acknowledges the RESET Indication for each cell by an RESTART- or, if not adequate, by a FAILURE- INDICATION request. Of course, several responses may be combined using a cell list in the RESTART or FAILURE INDICATION.
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
9.1.12 FAILURE-INDICATION Request/Indication
|
PARAMETER REFERENCE PRESENCE Cell-List 9.2.5.2 M The FAILURE-INDICATION Request is used by the BSC to indicate to the CBC a CB related problem situation in one or more of its cells. Any referenced cell enters CB-not-operational state. The status of the CB messages is undefined until the Restart- Indication is sent. It remains in not-operational state until a RESTART-INDICATION request (see 9.1.10) indicates normal CB operation (again). The CBC upon receiving a FAILURE indication, marks this cell as failed. It will generally not generate further WRITE- REPLACE requests for this cell, up to the point, when the CBC is informed by a RESTART indication, that the cell has resumed CB operation. The BSC refuses further WRITE-REPLACE requests from the CBC with the cause “cell-broadcast-not-operational” when any referenced cell is in the CB-not-operational state. Note, that a Failure-Indication may be triggered by a RESET Request. This allows to recover from situations, where a PDU occasionally may be lost.
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
9.1.13 SET-DRX Request/Indication
|
PARAMETER REFERENCE PRESENCE Cell-List 9.2.5.1 M Schedule-Period 9.2.12 O Reserved-Slots 9.2.13 O Channel Indicator 9.2.6 O The SET-DRX Request is used by the CBC to set DRX specific parameters i.e. the schedule period and the number of slots reserved for high priority messages, see GSM 04.12. At least one of the Schedule-Period or Reserved-Slots parameters must be present in the primitive. If this primitive is not supported, the BSC may use default values. ETSI TS 100 902 V6.1.0 (1998-07) 18 GSM 03.41 version 6.1.0 Release 1997 If a base station controller (BSC) receives a SET-DRX Indication, the new DRX parameters will be taken into account starting from the next schedule period in each cell, see GSM 04.12. If a BSC receives a SET-DRX Indication, the new DRX parameters will be applied for all cells that do not handle any broadcast message (null loading).
|
78cca9fc7c3cacbff09961357dbc9595
|
100 902
|
9.1.14 SET-DRX- REPORT Response/Confirm
|
PARAMETER REFERENCE PRESENCE Cell-List 9.2.5.2 O Failure-List 9.2.14 O Channel Indicator 9.2.6 O This primitive will be sent by the BSC to the CBC in response to a SET-DRX Request/Indication primitive. The Failure-List will contain those cells which were present in the Request message and which failed the requested operation. If the new schedule period parameters are not acceptable on a cell due to the load of the cell, the cause “bss-capacity- exceeded” is used in the Failure-list. 9.2 Parameters
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.