ttachment or handover attachment to a non-3GPP network, a UE needs to discover the trust relationship (whether it is a Trusted or Correct Non-3GPP Access Network) in order to know which non-3GPP IP access procedure to initiate. The trust relationship of a non-3GPP access network is made known to the UE with one of the following options: If the non-3GPP access supports 3GPP-based access authentication, the UE discovers the trust rela- tionship during the 3GPP-based access authentication. The UE operates on the basis of pre-configured policy in the UE. 11.4.1.4 EPS Mobility Management and Connection Management The EPS Mobility Management (EMM) states describe the Mobility Management states that result from the mobility management procedures for example, Attachment and Tracking Area Update (TAU) procedures. EMM consists of two states namely EMM-Deregistered and EMM-Registered: In the EMM-DEREGISTERED state, the EMM context in MME holds no valid location or routing information for the UE. The UE is not reachable by a MME, as the UE location is not known. At the same time some UE context can still be stored in the UE and MME, for example, to avoid running an AKA procedure during every Attachment procedure. The UE enters the EMM-REGISTERED state by a successful registration with an Attachment procedure to either E-UTRAN or GERAN/UTRAN. The MME enters the EMM-REGISTERED state by a successful Tracking Area Update procedure for a UE selecting an E-UTRAN cell from GERAN/UTRAN or by an Attachment procedure. The EPS Connection Management (ECM) states describe the signaling connectivity between the UE and the EPC. The two ECM states are ECM-IDLE and ECM-CONNECTED. During ECM-CONNECTED the network directs UE to the serving cell and the UE is ready to perform Uplink/Downlink transport with very limited access delay. The UE location is known in the MME with an accuracy of a serving eNodeB ID and the mobility of UE is handled by the handover procedure. In ECM-IDLE, the UE is in a low power consumption state and could be tracked i