| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
If, for some reason, the mobile did not receive an ATTACH ACCEPT
it resends an ATTACH REQUEST. The SGSN then would send a new
ATTACH ACCEPT. However, after sending the new ATTACH REQUEST, it
was unable to find the GMM context if the mobile uses the old
foreign tlli (as it is allowed to do). This fixes that.
|
|
This works around a problem that occurs if a mobile loses packet
data connectivity, e.g. moves out of coverage or switches over
to a circuit-switched call, while a data transfer is occurring.
The mobile would reset its LLC state, causing it to be
unsynchronized with the SGSN. Therefore the SGSN would drop
incoming frames until the sequence numbers matched. This
workaround resets the LLC state in the SGSN if T3350 expires,
indicating that Routing Area Updating Request, Attach Request,
or P-TMSI Realloc Command has failed.
|
|
According to TS 44.064 section 8.4.2, the LLC layer should only
drop UI frames if V(UR)-32 <= N(U) < V(UR). The code was dropping
frames whenever N(U) < V(UR). Consequently, large amounts of
packets could be dropped if, e.g., V(UR)==511 and the frame with
N(U)==511 was lost. All frames would be dropped until the next
time a frame with N(U)==511 is received.
|
|
TS 24.008 version 9.5.0 Release 9 sec 4.7.5:
In A/Gb mode, user data transmission in the MS shall be
suspended during the routing area updating procedure, except
if the routing area updating procedure is triggered by a PS
handover procedure as described in 3GPP TS 43.129 [113];
user data reception shall be possible. User data transmission
in the network may be suspended during the routing area
updating procedure.
|
|
|
|
Convert foreign TLLIs to local TLLIs for storage in LLME context.
|
|
|
