| Discussion and conclusion:
Revision of TD S2 160601, merging TD S2 160222. Agreed in parallel sessions. Gemalto asked to review this. Gemalto asked to add that UICC information shall take precedence over any corresponding information pre-configured information on the ME. This was revised accordingly in TD S2 160895 which was approved.
Roaming scenario with selection of a WLAN that interworks with a service provider in EVSP ***Thu Q0***
TD S2 160033 LS from CT WG4: Reply LS on roaming scenario with selection of a WLAN that interworks with a service provider in EVSP. (CT WG4)
Abstract: CT WG4 thanks SA WG2 for their Reply LS on roaming scenario with selection of a WLAN that interworks with a service provider in EVSP. Wrt the following response and statement agreed in subclause 16.1.1 of the related 23.402 CRs (SA WG2 TD S2 153675, TD S2 153675, TD S2 153676), When a TWAN supports interworking with an EPC network, the TWAN shall support both an S2a interface and a direct STa interface with this EPC network. while CT WG4 assumes that this text intends to exclude the roaming architecture described in the original CT WG4 LS (i.e. UE roaming in VPLMN B over a 3GPP access and accessing the EPC of VPLMN-B via a WLAN provided by a VPLMN A declared as an EVSP of VPLMN B - C4-151071), CT WG4 is not sure that this text really achieves this. For instance, considering the 'Roaming architecture for Trusted WLAN access to EPC - Home Routed, VPLMN provides WLAN service' (Figure 16.1.1-2 of 3GPP TS 23.402), CT WG4 interprets that a 'direct STa interface' means a direct connectivity between the TWAN and the 3GPP AAA Proxy, and that 'this EPC network' encompasses the EPC in the HPLMN and the 3GPP AAA Proxy in the VPLMN. This interpretation does not seem though to preclude the roaming architecture of the original CT WG4 LS, where the TWAN would have a 'direct STa interface' with the 3GPP AAA Proxy of VPLMN A, if we assume that 'EPC network' can contain the 3GPP AAA Proxies of both VPLMN A and VPLMN B.
Dostları ilə paylaş: |
