Network side issues in WLAN Interworking

Slides:



Advertisements
Similar presentations
Omniran GPP Trusted WLAN Access to EPC Use Case Analysis Date: Authors: NameAffiliationPhone Max RiegelNSN
Advertisements

Doc.: IEEE /xxxr0 Submission May 2004 Stephen McCann, Siemens Roke ManorSlide 1 IEEE Wireless Interworking with External Networks (WIEN)
1 © NOKIA MitM.PPT/ 6/2/2015 / Kaisa Nyberg (NRC/MNW), N.Asokan (NRC/COM) The Insecurity of Tunnelled Authentication Protocols N. ASOKAN, VALTTERI NIEMI,
Doc.: IEEE /0408r0 Submission March 2004 Colin Blanchard, BTSlide 1 3GPP WLAN Interworking Security Colin Blanchard British Telecommunications.
Omniran PtP Links across IEEE 802 Bridged Infrastructure Date: Authors: NameAffiliationPhone Max
Doc.: IEEE /229r0 Submission Tan Pek-Yew, Panasonic Slide 1 March 2003 Interworking – QoS and Authorization Tan Pek Yew & Cheng Hong Panasonic.
Authors: Jiann-Liang Chenz, Szu-Lin Wuy,Yang-Fang Li, Pei-Jia Yang,Yanuarius Teofilus Larosa th International Wireless Communications and Mobile.
Doc.: IEEE /751r0 Submission July 2004 Max Riegel, SiemensSlide 1 Selling network access Views from a business perspective Max Riegel Siemens.
Policy-Based QoS Management Architecture in an Integrated UMTS and WLAN Environment 莊勝超 洪志宗 張永伸 蘇芳生 IEEE Communications Magazine November 2003 p.118.
2003/12/291 Security Aspects of 3G-WLAN Interworking 組別: 2 組員: 陳俊文 , 李奇勇 , 黃弘光 , 林柏均
Doc.: IEEE /209r0 Submission 1 March GPP SA2Slide 1 3GPP System – WLAN Interworking Principles and Status From 3GPP SA2 Presented.
Doc.: IEEE /843r0 Submission Cheng Hong, Tan Pek-Yew, Panasonic Slide 1 November 2003 Interworking – WLAN Control Cheng Hong & Tan Pek Yew Panasonic.
Doc.: IEEE /0690r0 Submission Andrew Myers, BT Slide 1 July GPP SA3 Interworking Security Issues II Andrew Myers British Telecommunications.
Doc. : IEEE /xxxr0 Submission Cheng Hong, Tan Pek Yew Slide 1 May 2004 Handover scenarios and requirements Cheng Hong, Tan Pek Yew (Panasonic)
Authors: Jiann-Liang Chenz, Szu-Lin Wuy, Yang-Fang Li, Pei-Jia Yang,
November 2001 Lars Falk, TeliaSlide 1 doc.: IEEE /617r1 Submission Status of 3G Interworking Lars Falk, Telia.
Omniran OmniRAN SaMOG Use Case Date: Authors: NameAffiliationPhone Max RiegelNSN
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Proposed Presentation for 3GPP Date Submitted: August,
Doc.: IEEE /1060r1 Submission September 2013 S. Rayment, Ericsson & S. McCann, BlackBerrySlide 1 3GPP Liaison Report Date: Authors:
BITS Pilani Pilani | Dubai | Goa | Hyderabad EA C451 Vishal Gupta.
Month Year doc.: IEEE yy/xxxxr0 July 2017
MN Status Option for Proxy Mobile IPv6
Use Case for Distributed Data Center in SUPA
Unified Mobility Management Network Research Division
Update on 3GPP RAN3 Multi-RAT joint coordination
Examples based on draft-cheng-supa-applicability-00.txt
Month Year doc.: IEEE yy/xxxxr0 March 2016
Proposal for SSPN Interface Cluster
IEEE 802 OmniRAN Study Group: SDN Use Case
Teleconference Agenda
Month Year doc.: IEEE yy/xxxxr0 March 2016
IEEE 802 OmniRAN EC SG July 2013 Conclusion
IEEE 802 OmniRAN EC SG July 2013 Conclusion
TGaq Service Transaction Protocol for ANDSF Discovery Service
Interworking Study Group Justification
Jari Arkko Bernard Aboba
Discussions on FILS Authentication
OmniRAN Introduction and Way Forward
Stephen McCann, Siemens Roke Manor
3GPP Liaison Report Date: Authors: September 2013
Stephen McCann, Siemens Roke Manor
Stephen McCann, Siemens Roke Manor
IEEE Introduction to IEEE P1905.1
OmniRAN Overview and status
Overheads in Data Stream Over WLAN
Interworking scenarios and assumptions
WLAN Interworking scenarios
WIEN Study Group Proposed Roadmap
802.11u Proposal Date: Authors: September, 2005 July 2005
IEEE 802 Scope of OmniRAN Abstract
AP Function Classification & Requirements
Proposal for User Plane Cluster
3GPP WLAN Interworking Security Issues
Proposal for authentication cluster
AAA: A Survey and a Policy- Based Architecture and Framework
OmniRAN Introduction and Way Forward
QoS in WLAN Interworking
Proposal for authentication cluster
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
3GPP WLAN Interworking update
3GPP WLAN interworking requirements
Stephen McCann, Siemens Roke Manor
3GPP Update/Status (Release 15 – June 2018)
STA Location for emergency call support in SSPN interface
Proposed Resolution for Draft 3.0
TGu Agenda Date: Authors: January 2005 January 2005
Requirement Motions Date: Authors: July 2005 July 2005
TGu Requirements Check
Wireless MAC Multimedia Extensions Albert Banchs, Witold Pokorski
Presentation transcript:

Network side issues in WLAN Interworking May 2003 doc.: IEEE 802.11-03/229r1 July 2004 Network side issues in WLAN Interworking Cheng Hong, Tan Pek Yew (Panasonic) WIEN 12th July 2004 Cheng Hong, Tan Pek Yew Tan Pek-Yew, Matsushita Electric Ind.

Interworking scope at network side July 2004 Interworking scope at network side Policy enforcement Access control Simultaneous access External QoS mapping User access revocation Admission control Cheng Hong, Tan Pek Yew

Access Control & User access revocation July 2004 Access Control & User access revocation Diversity in the access control schemes for interworking: 3GPP requires (U)SIM based access control Other public network uses different access control, e.g. HTTP, etc The network sharing, etc, makes the situation even more complicated Security schemes of 11 11i provided the security solution for WLAN 3GPP required EAP methods (EAP-SIM/AKA) can be supported But, how is the co-existence issue? The EAP methods needs to be supported together with other methods, e.g. HTTP based, in the same AP In case of network sharing, as required in the 3GPP TS, several AAA paths needs to be supported. Can the MAC address of the UE be used as a secure identifier for the user/session? Does the authentication support including the MAC address? (11i) User revocation could be done through the AAA framework Network initiated revocation needs to be supported (as in 3GPP TS 23.234 Annex A.1.2) This relates to the online charging information (based on the 3GPP requirements) The revocation can also be the result of policy decisions. Cheng Hong, Tan Pek Yew

Policy Enforcement Types of Policies: July 2004 Policy Enforcement Types of Policies: Network policies: more of static User policies: Dynamic and concerns the individual user Mapping of the policy information: external network does not have specific info about the 11 technologies, e.g. 3G network uses different control mechanisms mapping of the policy should be necessary. mapping to be done in 11, and it provides a generic interface to work with all external network Charging is part of the policy related issues (especially online charging) Relationship to the Authentication Default policy can be carried in the authentication result (success) The policy update can happen more frequent than the authentication, e.g. MT may request for several services within a authenticated session, and each service may pose a new policy on the MT, The policy scheme may not be suitable to combine with the authentication. Cheng Hong, Tan Pek Yew

External QoS mapping Necessary for the QoS in interworking: July 2004 External QoS mapping Necessary for the QoS in interworking: With interworking, WLAN is serving paying customers. QoS has to be guaranteed New services provided by the interworking requires QoS guarantee, e.g. VoIP, IMS, etc WLAN QoS, e.g. 11e needs to be integrated with the end-to-end QoS of the service. QoS info is more dynamic, and could change during the life time of a session. External QoS mapping to the 11 QoS Translation of the upper layer QoS to the 11e parameters, e.g. TSID, TSPEC (part of MLME functions). At terminal side, it could be from application to 11e, e.g. SDP to TSPEC, For dual mode terminal, could be directly from UMTS to 11e Since there are different mapping methods, it needs to have a consistent way of mapping to guarantee user experience. The related issues: 11 QoS is only part of the end-to-end QoS. How to decide its exact value is not obvious. Bandwidth is easy, but delay should be carefully mapped. That is the reason for a standard way of doing the mapping At network side, the admission control would be involved. In 11e, the request will be initiated by the Terminal, and network side does the admission control. Cheng Hong, Tan Pek Yew

July 2004 Admission Control Admission Control is necessary for processing the QoS requests from the terminal Resources allocation/management is involved in the process. The control decision will requires local network information and based on local network status, which depends on the monitoring of the network. 11k related? Network side decision would also depends on the policy rules from external network and local management entities. Cheng Hong, Tan Pek Yew

July 2004 Simultaneous Access Simultaneous access to different networks is required by 3GPP. Simultaneous connections to UMTS and WLAN This is a requirement from operators Certain services will be kept on the UMTS link even WLAN is on Aiming for the dual mode terminal Simultaneous connections to different operator’s network Not yet included in the Rel6 (depends on SA1’s decision) multiple authentication session/traffic aggregation and distribution According to some proposal in 3GPP, MAC address of the MT needs to be provided to the AAA server. Cheng Hong, Tan Pek Yew

July 2004 Conclusions The network side of the interworking should be targets of the group: Access control & user revocation Policy enforcement and mapping QoS control and mapping Admission control Support of simultaneous connection Cheng Hong, Tan Pek Yew