Hi Daniel and 3G folks,
about our difficulty in maintaining a prolonged link with the UE, I found a bit of discrepancy concerning the TMSIs used.
When looking at a pcap where we authenticate and MM LU / GMM Attach successfully on CS / PS, and with TMSI assignment enabled in CSCN, I see TMSIs in these places:
1) UE sends TMSI in "(GMM) Attach Request" (PS) 2) SGSN sends TMSI in "(GMM) Attach Accept" (PS) 3) CSCN sends TMSI in "Location Update Accept" (CS)
All these TMSIs differ.
When I look in the RRC log of the hnb, it is logging a TMSI for pretty much every received message on CS and PS domains. But it is always and only logging the TMSI matching 1), i.e. the TMSI originally sent on the PS domain. To rephrase, the same TMSI is logged for PS and CS domain messages; for the MM LU Accept as well as the GMM Attach Accept, the hnb logs TMSI 1) even though the CN sent TMSIs 3) and 2), respectively.
For 1) and 2), it seems that the SGSN should accept and use the TMSI sent by the UE during the Attach Request, right?
For 3), according to the RRC log, it seems that the UE expects to see the very same TMSI in CS that it sent to PS -- that'd be a problem. On the other hand, when noting that, in the Location Updating Request, the UE identified itself using the IMSI and not a TMSI, it may be indeed the correct choice to disable TMSI use for CS?
I must admit that I'm not firm in the IMSI/TMSI realm, and staring at 3GPP 04.08 doesn't clarify it right away, so I'd appreciate some feedback from this list. I can stare some more, but maybe you guys are quicker.
Thanks!
~Neels
Hi Neels,
On Thu, Mar 17, 2016 at 02:05:32AM +0100, Neels Hofmeyr wrote:
about our difficulty in maintaining a prolonged link with the UE, I found a bit of discrepancy concerning the TMSIs used.
- UE sends TMSI in "(GMM) Attach Request" (PS)
- SGSN sends TMSI in "(GMM) Attach Accept" (PS)
PS uses P-TMSI
- CSCN sends TMSI in "Location Update Accept" (CS)
CS uses TMSI
P-TMSI and TMSI are in completely different namespaces.
All these TMSIs differ.
1+2 should be the same. '3' should be different.
For 3), according to the RRC log, it seems that the UE expects to see the very same TMSI in CS that it sent to PS -- that'd be a problem. On the other hand, when noting that, in the Location Updating Request, the UE identified itself using the IMSI and not a TMSI, it may be indeed the correct choice to disable TMSI use for CS?
It might be the case that our network does something that implies we support a 'combined CS+PS attach', which we don't.
In an (unsupported) combind CS+PS attach, the SGSN would send an ATTACH ACCEPT with IEs for both TMSI and P-TMSI.
If you're looking for more information on TMSI/IMSI/P-TMSI, 04.08 is the wrong place. Check 23.003, it contains thins like
"In areas where both MSC-based services and SGSN-based services are provided, some discrimination is needed between the allocation of TMSIs for MSC-based services and the allocation of TMSIs for SGSN-based services. The discrimination shall be done on the 2 most significant bits, with values 00, 01, and 10 being used by the VLR, and 11 being used by the SGSN."
Regards, Harald