B-5G網路整合不可信任WiFi網路
https://www.youtube.com/watch?v=zUSBRX_JBVw&t=7s
Non-3GPP access networks
- Untrusted non-3GPP access networks
- e.g., UE connects to the 5G core via public WiFi and Internet
- Trusted non-3GPP access networks
- e.g., UE connects to the CHT WiFi AP
Trusted and Untrusted Non-3GPP Access
- A non-3GPP access network shall be connected to 5G core network via
- Untrusted: Non-3GPP InterWorking Function (N3IWF)
- access network is considered untrusted
- It acts as a gateway and security barrier between the untrusted network and the 5G core network.
- security checks, data transformation, and protocol conversion to ensure secure and seamless communication
- Trusted: Trusted Non-3GPP Gateway Function (TNGF)
- access network is considered trusted
- provides a more direct and efficient connection between the non-3GPP network and the 5G core network.
- less strict constraints compared to the N3IWF(security checks and protocol conversion)
- Both N3IWF and TNGF interface with 5G Core Network CP and UP functions via N2 and N3 interfaces, respectively
- N2 interface: Connects to the Control Plane (CP) functions of the 5G core network, handling signaling and control messages.
- N3 interface: Connects to the User Plane (UP) functions of the 5G core network, handling data traffic.
- A Non-3GPP access network may advertise(通知) the Public Land Mobile Networks (PLMNs) for which it supports trusted connectivity and the type of supported trusted connectivity (e.g., 5G connectivity)
- helps mobile devices choose the appropriate connection path depending on the available networks and security requirements.
- the choice between N3IWF and TNGF depends on the level of trust placed on the non-3GPP access network
- Trusted networks: faster and more efficient connections
- untrusted networks: stricter security measures
- When UE decides to use untrusted non-3GPP access
- Selects and connects with a non-3GPP access network
- Selects a PLMN and an N3IWF in this PLMN
- When UE decides to use trusted non-3GPP access
- Selects a PLMN
- Selects a non-3GPP access network (a TNAN) that supports trusted connectivity to the selected PLMN
- A UE shall establish an IPsec tunnel with the N3IWF or with the TNGF to register with the 5G Core Network over non-3GPP access
PLMN 是指由政府或其批准的運營商為公眾提供陸地移動通信業務而建立、經營的網路。PLMN 由 MCC 和 MNC 兩個部分組成
MCC:移動國家代碼 (Mobile Country Code)。MCC 由三個數字組成,用於識別不同的國家或地區。例如,中國的 MCC 是 460。
MNC:移動網絡代碼 (Mobile Network Code)。MNC 由兩個或三個數字組成,用於識別不同的移動網絡營運商。例如,中國移動的 MNC 是 00,中國聯通的 MNC 是 01,中國電信的 MNC 是 02。
Untrusted Non-3GPP Access Network with 5G Core
- Non-3GPP interworking function (N3IWF)
- Interworking of untrusted non-3GPP networks and 5G core
- Acting as a gateway for the 5G core with support for N2 and N3 interfaces
- Secure IPsec connection over non-3GPP access network between UE and N3IWF
- Why is needed?
- Using untrusted WLANs, which are not controlled by operator
- Including public hotspots, home Wi-Fi, corporate Wi-Fi, etc.
Benefits
- Can supplement the 3GPP access networks for
- Avoiding data congestion and reducing backhaul costs with increased capacity
- Providing better coverage and connectivity in high-density/indoor environments
- Enabling new business opportunities with value added services
- Reducing operator capital and operational costs with unified management
- Delivering enhanced services to customer in a cost-efficient manner
Evolution of Architecture: Prior to 5G
Architecture in 5G
3GPP Access & 5G Core
Protocol Stacks
- Control plane (CP) protocol stacks
- Involving UE, WLAN, N3IWF, and AMF
- Initial registration and authentication
- NAS mobility and session management
- Establishing UP between N3IWF and UE
- User plane (UP) protocol stack
- Involving UE, WLAN, N3IWF, and UPF
- Transferring the UP traffic between UE and data network
- IPsec tunnel mode is employed to protect the data transfer
Protocol Stack for Initial Registration and Auth.
- Control plane before signaling IPsec SA
- Selecting N3IWF and initiating IKEv2 SA establishment procedure
- N3IWF starts the EAP-5G procedure with UE
- UE initiates registration and authentication procedure using NAS protocol with AMF
Protocol Stack for NAS Mobility and Session Mgmt.
- Control plane after signaling IPsec SA
- A signaling IPsec SA is established between UE and N3IWF
- A TCP connection is further established for transport of NAS mobility and session mgmt.
Protocol Stack for Establishing User Plane
- User plane establishment via N3IWF
- N3IWF initiates the establishment of the IPsec child SAs with UE using IKEv2
Protocol Stack for User Plane
- User plane protocol stack
- Transferring UP traffic between UE and data network
- IPsec tunnel mode is employed for the established child SAs to protect the data transfer
Control Plane Procedures
- Access network discovery and selection
- Using ANDSP (Access Network Discovery and Selection Policy)
- ANDSP consists of WLAN Selection Policy (WLANSP) and non-3GPP access network node (N3AN) configuration information
- N3AN info for selecting a N3IWF
- Registration and authentication
- PDU session establishment
- Protocol Data Unit 通信協議中用於傳輸數據的基本單位
- 在物理層中,PDU 可以是 1 位、2 位、4 位等。
- 在資料鏈路層中,PDU 可以是 Ethernet 幀、PPP 幀等。
- 在網路層中,PDU 可以是 IP 數據包、IPv6 數據包等。
- 在傳輸層中,PDU 可以是 TCP 數據段、UDP 數據段等。
Authentication for Untrusted Non-3GPP Access
- Vendor-specific EAP method “EAP-5G” ➝ Authentication
- primary authentication mechanism Between UE and N3IWF as a security gateway
- for encapsulating NAS(Network Access Server) messages exchanged between the UE and the N3IWF.
Extensible Authentication Protocol (EAP)
- If the UE needs to authenticated by the 3GPP home network
- 5G-AKA or EAP-AKA’ can be used
5G-AKA (5G Authentication Key Agreement)
EAP-AKA’ (Extensible Authentication Protocol - Authentication and Key Agreement’)
- The UE shall be authenticated by reusing the existing UE NAS security context in AMF
Authentication Management Function (AMF)
Three major technologies in non-3GPP authentication
How does IKEv2 Work?
IKEv2 的工作原理如下:
- 協商:IKEv2 協議由兩個階段組成:第一階段協商和第二階段協商。在第一階段協商中,兩個實體建立安全通道並交換密鑰。在第二階段協商中,兩個實體建立 IPsec SA。
- 安全關聯:安全關聯是 IKEv2 協議中的主要概念。安全關聯定義了兩個實體之間的安全配置,包括加密算法、身份驗證方法和密鑰。
- 身份驗證:IKEv2 使用多種身份驗證方法,包括預共享密鑰 (PSK)、數位憑證和 X.509 憑證。
- 加密:IKEv2 使用多種加密算法,包括 AES、3DES 和 ChaCha20/Poly1305。
IKEv2 Authentication with EAP Method
- In addition to authentication using public key signatures and shared secrets, IKE supports EAP
- Extensible Authentication is implemented in IKE as additional IKE_AUTH exchanges that MUST be completed to initialize IKE_SA
- These exchanges carry EAP messages between the initiator and responder to complete the chosen EAP method’s authentication process.
- For EAP methods that create a shared key as a side effect of authentication, that shared key MUST be used by both initiator and responder to generate AUTH payloads
EAP Authentication Protocol
- An Authentication framework, but not a specific mechanism
- Providing some common functions
- Negotiating authentication methods: EAP methods (more than 40)
- Important notes
- EAP authentication is initiated by the server (authenticator)
- Authentication is mutual between the client and authentication server
Some materials from http://what-when-how.com/ccnp-ont-exam-certification-guide/802-1x-and-eap-authentication-protocols/
Popular EAP Methods
- Cisco LEAP (Lightweight EAP)
- A proprietary method developed by Cisco
- User credentials are not strongly protected: complex passwords are required
- EAP-FAST (EAP-Flexible Authentication via Secure Tunneling)
- A replacement for LEAP, but non-proprietary
- No need of strong password or any certificate
- Using a PAC (Protected Access Credential) to establish a TLS tunnel
- EAP-TLS (EAP-Transport Layer Security)
- (RFC 5216) original, standard wireless LAN EAP authentication protocol
- Using PKI: both client and AS need a certificate (X.509 certificates)(兩方都有certificate)
- One of the most secure EAP standards available
- Universally supported by all manufacturers of wireless LAN hardware/software
- PEAP (Protected EAP)
- Encapsulating EAP within a potentially encrypted and authenticated TLS tunnel
- Only the server authentication is performed using PKI certificate
- Client is authenticated using either EAP-GTC or EAP-MSCHAPv2 within the tunnel
- EAP-GTC (Generic Token Card)
- EAP-MSCHAPv2 (Microsoft’s Challenge Handshake Authentication Protocol)
PEAP
PEAP 的工作原理如下:
- 用戶端向接入點發送身份驗證請求。
- 接入點使用 PEAP 隧道將身份驗證請求發送到認證伺服器。
- 認證伺服器使用 EAP 方法對用戶進行身份驗證。
- 認證伺服器向接入點發送身份驗證結果。
- 接入點將身份驗證結果發送給用戶端。
EAP-5G
- In non-3GPP registration, EAP-5G is adopted for authentication with some minor changes
- e.g., N3IWF does not send EAP-Identity request since UE includes its identity in the first IKE_AUTH
- EAP-5G is utilized only to encapsulate NAS messages, but not to authentication UE
- N3IWF and UE exchange EAP-5G messages within IKE_AUTH
NAS Messages
- NAS (Non-Access Stratum), a functional layer supporting traffic and signaling messages between CN and UE
- Two message types: 5GMM (Mobility Management) and 5GSM (Session Management)
- 5GMM: supporting mobility of UE including procedures like authentication, identification, UE configuration update, and security mode control
- Interactions between UE and AMF
- 5GSM: supporting session management to establish and maintain data connectivity between UE and data network
- Interactions between UE and SMF through AMF
5G-NAS over EAP
IPsec
- Two main functions
- Encapsulating Security Payload (ESP): a combined authentication/encryption function
- A key exchange function: Internet Key Exchange standard (IKEv2)
- VPN: both authentication and encryption are generally desired
- Authentication Header (AH): authentication-only function (deprecated)
Security Associations
- A key concept of IPsec
- One-way relationship between a sender and a receiver
- Two-way secure exchange: two SAs are required
- Uniquely identified by three parameters
- Security parameter index (SPI) (辨識封包是哪個security association)
- IP destination address
- Protocol identifier: AH or ESP
- Characterized by the following parameters
- Sequence number counter: 32-bit
- Sequence counter overflow: A flag➔whether overflow➔an auditable event
- Anti-replay window: defining a sliding window (prevent replay attack)
- AH information
- Algorithm, keys, key lifetimes, etc.
- ESP information
- Algorithm, keys, init values, key lifetimes, etc.
- Lifetime of this security association
- IPSec protocol mode: tunnel or transport
- Path MTU
Two IPsec Operation Modes
- Transport and Tunnel modes
Encapsulating Security Payload
- Providing authentication and confidentiality services
Transport and Tunnel Modes
Transport Mode
- Protection: the payload of an IP packet
- Typically used for end-to-end communication between two hosts
- ESP protects the IP payload but not the IP header
Tunnel Mode
- Protection: the entire IP packet
- Entire original packet travels through a tunnel from one point to another
- Used when one or both ends of a security association are a security gateway
- Hosts on networks behind firewalls may engage in secure communications without implementing IPsec
IPsec: AH + ESP
- IP AH only
- IP AH + ESP
- Transport mode
- Tunnel mode
Authentication Procedure for Untrusted Non-3GPP
- Goal
- Enabling mutual authentication between UE and network
- Providing key materials that can be used between UE and network in subsequent procedures
- Using EAP framework
- SEAF @ AMF: pass-through authenticator
- AUSF: authentication server
5G Authentication Initialization
5G AKA
NAS Security Mode Command Procedure
EAP-AKA’
Difference between EAP-AKA’ and 5G-AKA
- Role of the SEAF
- EAP-AKA’: transparently forwarding EAP messages
- EAP message exchanges are between UE and AUSF through SEAF
- 5G-AKA: also verifying authentication response from UE
- May take action if the verification fails
- Key derivation
- EAP-AKA’: AUSF drives KAUSF itself
- 5G-AKA: KAUSF is computed by UDM/ARPF and sent to AUSF
Key Hierarchy in 5G
- Suitable for both 3GPP and non-3GPP accesses
- Non-3GPP access generates one more key KN3IWF
PDU Session Establishment for Non-3GPP