13.3 Network Functionalities

This section describes the main functions achieved by the WiMAX end-to-end system.

13.3.1 Network Discovery and Selection

This function is required for nomadic, portable and mobile WiMAX services (see Table 13.1) where in the same geographical area the MS may have radio coverage access to an ASN managed by a single NAP and shared by several NSPs or coverage access to several ASNs managed by several NAP/NSPs. To perform network discovery and selection, the MS (which has been pre-provisioned with configuration information at subscription) performs a four-step process:

NAP discovery. During the scanning of the DCD of the different BSs in the coverage reach from the MS, the MS detects the ‘operator ID’ in the BSID field.
NSP discovery. The MS discovers the available NSP through the list NSP ID which is broadcast by the ASN as part of the system information identity message. NSP discovery is also possible via solicited request/response messages.
NSP enumeration and selection. Based on the dynamic information obtained in the coverage area and the configuration information from the subscription, the MS selects the appropriate NSP. Manual configuration of the NSP may also be available in the case of a visited NSP.
ASN attachment. After selection of the NSP and associated ASN, the MS indicates its NSP selection by sending an NAI (Network Access Identifier) message used by the ASN to determine the next hop AAA where an MS AAA packet should be routed to.

13.3.2 IP Addressing

WiMAX networks support IPv4 and IPv6 addressing mechanisms. At the end of the procedure, a PoA (Point of Attachment) IP address is delivered to the MS. The IP allocation address modes depend on the WiMAX access service types.

In the case of IPv4, the dynamic PoA configuration is based on DHCP ^[17]^,^[18]. The DHCP proxy may reside in the ASN and the DHCP server in the CSN. In the case of IPv6, stateful IP address allocation is based on DHCPv6 ^[36]. The DHCP server resides in the CSN and the DHCP proxy may reside in the ASN. For the stateless CoA (Care of Address), IP address allocations RFC 2462 ^[37] and RFC 3041 ^[38] are used.

PoA IP address methods according to the WiMAX access services and IP version are summarized in Table 13.3.

Table 13.3: PoA IP address method according to the WiMAX access services and IP version
Open table as spreadsheet
Service type	PoA IP address scheme (IPv4)	PoA IP address scheme (IPv6)
Fixed access	Static or dynamic	Static or stateful autoconfiguration
Nomadic access	Dynamic	Stateful or stateless autoconfiguration
Mobile access	DHCP for P-MIP^[a] terminals	Stateful or stateless authconfiguration
	MIP based for C-MIP^[b] terminals
^[a]P-MIP=Proxy-Mobile IP mode. ^[b]C-MIP=Client-Mobile IP mode.

13.3.3 AAA Framework

The AAA framework follows the IETF specifications and includes the following services:

authentication: device, user or combined user/device authentication;
authorisation: user profile information delivery for sessions, mobility and QoS;
accounting: delivery of information for pre-paid/post-paid services.

Authentication and authorisation procedures are based on the EAP (Extensible Authentication Protocol) ^[39]. Between the MS and the ASN (the authenticator function), EAP runs over PKMv2, which enables both user and device authentication. Between the AAA server and the ASN, the EAP runs over RADIUS ^[40].

Accounting is also based on RADIUS messages. WiMAX Release 1 offers both offline (post-paid) and online (pre-paid) accounting. In the case of offline accounting, the ASN generates UDRs (Usage Data Records), which are a combination of radio-specific parameters and IP-specific parameters. The serving ASN then sends the UDR to the RADIUS server.

13.3.4 Mobility

The mobility procedures are divided into two mobility levels:

ASN anchored mobility procedures. This refers to MS mobility where no CoA address update is needed, also known as micromobility.
CSN anchored mobility procedures. The macromobility between the ASN and CSN is based on mobile IP protocols running across the R3 interface.

CSN anchored mobility implies that, in the case of IPv4, the MS changes to a new anchor FA (Foreign Agent). WiMAX systems must support at least one of the following mobile IP schemes:

Proxy-MIP. In this case, the MS is unaware of CSN mobility management activities and there is no additional signalling/overhead over the air to complete the CSN mobility.
Client MIP (CMIPv4). In this case, the MIP client in the MS participates in inter-ASN mobility.

13.3.5 End-to-End Quality of Service

The IEEE standard defines the QoS framework for the air interface (see Chapter 11). The WiMAX architecture specifications extend the QoS framework to the complete network where many alternatives for enforcing the QoS on Layer 2 or Layer 3 may exist.

The end-to-end QoS framework relies on functions implemented in the CSN (PF (Policy Function) and AF (Application Function)) and in the ASN (SFM (Service Flow Management) and SFA (Service Flow Authorisation)). In the CSN, the AF triggers a service flow trigger to the PF based on the information sent by the MS with whom it communicates. The PF then evaluates service requests against a policy database in the NSP. In the ASN, the SFA communicates with the PF and is responsible for evaluating the service request against user QoS profiles. The SFM (located in the BS and responsible for creation, admission, modification and release of 802.16 service flows) mainly consists of an admission control function, which decides, based on available radio resource and other local information, whether a radio link can be created.

^[17]IETF RFC 2131, Dynamic Host Configuration Protocol (DHCP), R. Droms, March 1997.

^[18]IETF RFC 2132, DHCP options and BOOTP Vendor Extensions, S. Alexander and R. Droms, March 1997.

^[36]IETF RFC 3315, Dynamic Host Configuration Protocol for IPv6 (DHCPv6), R. Droms et al., July 2003.

^[37]IETF RFC 2462, IPv6 Stateless Address Autoconfiguration. IETF Standard, S. Thomson et al., December 1998.

^[38]IETF RFC 3041, Privacy Extensions for Stateless Address Auto-configuration in IPv6, T. Narten and R. Draves, January 2001.

^[39]IETF RFC 3748, Extensible Authentication Protocol (EAP), B. Aboba et al., June 2004.

^[40]IETF RFC 3579, RADIUS (Remote Authentication Dial In User Service) Support for Extensible Authentication Protocol (EAP), B. Aboba and P. Calhoun, September 2003.