C.3 Parameters in Pull mode

24.3023GPPAccess to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networksRelease 18Stage 3TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

The UE is currently in 3GPP network. The UE sends a query to OMA ANDSF server as follows:

ANDSF_Query ( UE_Location, AccessNetworkType=WiMAX )

The UE specifies the UE_Location information in terms of current 3GPP Cell Id (e.g. Cell_2)

On receipt of the query message the ANDSF looks up the UE_Location (Cell_2) in the ANDSF database and searches for a prospective WiMAX entry. In this case the ANDSF retrieves WiMAX Service provider identifier (NSP-ID) NSP_2 and WiMAX Network Access Provider Identifier (NAP-ID) NAP_3. The ANDSF retrieves the network parameters for this combination. The ANDSF fills these parameters in the WNDS MO and sends the information back to the UE.

ANDSF_Response ( UE_Location, AccessNetworkInformationRef MO=WIMAXNDS).

Annex D (informative):
Mismatch of static configuration of mobility mechanism in the UE and in the network

This annex describes the possible cases of mismatch between the statically configured mobility mechanisms in the UE and in the EPC as shown in table D1. Additionally the table shows whether the UE would be able to access EPC services as a consequence of the mismatch.

Table D1: Mismatch of static configuration of mobility mechanism in the UE and in the network

	NBM configured in the network	DSMIPv6 configured in the network	MIPv4 configured in the network
NBM configured in the UE	No mismatch	Mismatch. The UE is not able to access EPC services because the UE configures a local IP address and there is no connectivity to the PGW in the EPC. Depending on operator’s policy and roaming agreements, local IP access services (e.g. Internet access) can be provided in the non-3GPP network using the local IP address. However, such local IP access services, where the user traffic does not traverse the EPC, are not described in this specification.	Mismatch. The UE is not able to access EPC services because the UE does not support communication with the Foreign Agent in the trusted non-3GPP IP access network.
DSMIPv6 configured in the UE	Mismatch. The UE can be able to access EPC services. After attach to the non-3GPP network, the UE is on the home link and configures an IP address based on the HNP, however in some cases the UE cannot detect the home link. Since the UE is configured with DSMIPv6, the UE would initiate a DSMIPv6 bootstrapping: – If the network offers a HA function to the UE and if the bootstrapping is successful, the UE detects that it is attached to the home link. Depending of the UE capabilities and the network configuration, the UE can access EPC via the S2a or S2b, but session continuity is not supported. – If the network does not offer a HA function or if the bootstrapping to the HA is not successful, the UE is not able to receive its Home Network Prefix and hence the UE cannot detect that it is on the home link. If no APN bound to the configured IP address was received and the access network does not support APN delivery, the UE would not recognize the mismatch and cannot access EPC services. If the access network supports APN delivery and the configured IP address is bound to an APN, the UE can access EPC services.	No mismatch	Mismatch. The UE is not able to access EPC services because the UE does not support communication with the Foreign Agent in the trusted non-3GPP IP access network.
MIPv4 configured in the UE	Mismatch. The UE is not able to access EPC services because no Foreign Agent functionality is supported in the non-3GPP access network.	Mismatch. The UE is not able to access EPC services because no Foreign Agent functionality is supported in the non-3GPP access network.	No mismatch

Annex E (informative):
UE procedures based on preconfigured and received information

The flow diagrams in figure E-1 and figure E-2 show examples of the procedures that the UE can follow in order to establish a PDN connection based on information available to the UE about the authentication method, received or pre-configured access network trust relationship information or received or preconfigured IP mobility mode selection information.

The following symbols are used:

AN_TRUST trust relationship between the non-3GPP access network and the 3GPP EPC, considered to be applicable by the UE

IPMM IP mobility mode, considered applicable by the UE

Initially, at the entry to flow chart the UE has established contact with the non-3GPP access network, but the UE does not know whether it is in a trusted or untrusted non-3GPP IP access access network.

Figure E-1. Procedures to be followed by the UE depending on received and preconfigured information – part 1

Figure E-2. Procedures to be followed by the UE depending on received and preconfigured information – part 2

Annex F (Normative):
Access to EPC via restrictive non-3GPP access network