Tech-
invite
3GPP
space
IETF
space
21
22
23
24
25
26
27
28
29
31
32
33
34
35
36
37
38
4‑5x
Content for
TR 29.994
Word version: 18.0.0
1…
2…
2
References
3
Abbreviations
4
General
5
Specific implementation on the radio interface
6
Use of VAD/DTX in conjunction with frequency hopping for a speech call
A
Amendment Request 08.08 - 021 R4: Information on channel in use in HO REQUEST
$
Change History
2
References
p. 5
3
Abbreviations
p. 6
4
General
p. 6
5
Specific implementation on the radio interface
p. 6
5.1
Handovers and "Synchronisation Indication"
p. 6
5.1.1
Justification
p. 6
5.1.2
Solution
p. 6
5.2
"Directed Retry" type Handovers
p. 7
5.2.1
Justification
p. 7
5.2.2
Solution
p. 7
5.3
Cell broadcast and frequency hopping
p. 7
5.3.1
Justification
p. 7
5.3.2
Solution
p. 7
5.4
Handling of Phase 2 and Phase 2+ BCCH Messages
p. 8
5.4.1
Justification
p. 8
5.4.2
Solution
p. 8
5.5
Handling of Phase 2 and Phase 2+ SACCH Messages
p. 8
5.5.1
Justification
p. 8
5.5.2
Solution
p. 8
5.6
Handling of assignment message using Mobile Allocation IE including ARFCN=0
p. 8
5.6.1
Justification
p. 8
5.6.2
Solution
p. 8
5.7
Hopping sequence generation including ARFCN=0
p. 9
5.7.1
Justification
p. 9
5.7.2
Solution
p. 9
5.8
QoS IE length between R97 and R99 implementations
p. 9
5.8.1
Justification
p. 9
5.8.2
Solution
p. 9
5.9
MS unable to handle the LOCATION UPDATING ACCEPT, ATTACH ACCEPT and ROUTING AREA UPDATE ACCEPT messages when the EPLMN Lists IE is included
p. 9
5.9.1
Justification
p. 9
5.9.2
Solution
p. 10
5.10
MS unable to handle messages when the truncation function is used
p. 10
5.10.1
Justification
p. 10
5.10.2
Solution
p. 10
5.11
Roaming restrictions issues with reject cause #13 and #15
p. 10
5.11.1
Justification
p. 10
5.11.2
Solution
p. 11
6
Use of VAD/DTX in conjunction with frequency hopping for a speech call
p. 11
6.1
Scope
p. 11
6.2
General
p. 12
6.3
Implementation options to reduce the occurance of undetected bad frames by utilising normal system features
p. 12
6.3.1
Number of frequency hopping channels
p. 12
6.3.2
Frequency hopping type
p. 12
6.3.3
Continuous SID frames on C0
p. 13
6.4
Implementation options to reduce the occurance of undetected bad frames by changing normal system operation
p. 13
6.4.1
Changing the training sequence of the dummy burst to a new (ninth) training sequence
p. 13
6.4.2
Using an alternative training sequence out of the eight assigned
p. 13
6.4.3
Setting the stealing flag for the bits transmitted which are not intended to be part of the TCH
p. 13
6.4.4
Sending partial SID frames on C0
p. 14
6.5
Tested Combinations
p. 14
6.5.1
"Normal" system
p. 14
6.5.2
New training sequence
p. 14
6.5.3
Alternative training sequence from the eight assigned
p. 14
6.5.4
Setting stealing flag for unintentionally transmitted bits
p. 15
6.5.5
Setting stealing flag for unintentionally transmitted bits and modifying training sequence for Dummy Bursts
p. 15
6.5.6
Sending partial SID information on C0
p. 15
A
Amendment Request 08.08 - 021 R4: Information on channel in use in HO REQUEST
p. 17
–
A.3.1.5.1.1 Generation of the HANDOVER REQUIRED message
p. 17
–
A.3.1.5.2 Handover Resource allocation
p. 18
–
A.3.1.5.2.1 Operation of the procedure
p. 18
–
A.3.2.1.8 HANDOVER REQUEST
p. 19
–
A.3.2.1.9 HANDOVER REQUIRED
p. 20
–
A.3.2.2.49 CURRENT CHANNEL
p. 21
$
Change History
p. 23