3GPP specification: 36.413
http://www.3gpp.org/DynaReport/36413.htm
ETSI TS 136 413 V10.9.0
http://www.etsi.org/deliver/etsi_ts/136400_136499/136413/10.09.00_60/ts_136413v100900p.pdf ,p.88
9.1.5.8 PATH SWITCH REQUESThttp://www.etsi.org/deliver/etsi_ts/136400_136499/136413/09.10.00_60/ts_136413v091000p.pdf ,p.83
Source MME GUMMEI "Optional"
9.1.5.8 PATH SWITCH REQUEST(No Source MME GUMMEI field)
Although the "Source MME GUMMEI" is optional in release 10, it's said that Cisco HeNBGW require it in its Path Switch Request?
LTE X2 Handover Messaging
http://www.eventhelix.com/lte/handover/LTE-X2-Handover-Messaging.pdf#page=6
LTE eNodeB Handover over the X2 Interface
http://www.eventhelix.com/lte/handover/x2/lte-x2-handover-sequence-diagram.htm#.VtBxLTWkVC1
HeNB - GW Administration Guide, StarOS Release 17 Last Updated February 27, 2015
http://www.cisco.com/c/dam/en/us/td/docs/wireless/asr_5000/17-0/PDF/17-HeNBGW-Admin.pdf
HENBGW have to route S1 PATH SWITCH REQUEST message from HENB towards the MME based on the GUMMEI of the source MME received from the HeNB. If HENBGW receives CSG ID IE and Cell Access Mode IE in the S1 PATH SWITCH REQUEST, the same should be forwarded to MME. In case of S1 PATH SWITCH REQUEST ACKNOWLEDGE message, HENBGW will inform the HeNB about the MME UE S1AP ID assigned by the MME and the MME UE S1AP ID assigned by the HeNB GW for the UE.
沒有留言:
張貼留言