name: EIR
full_form: Equipment Identity Register
context: The Mobile Equipment Identity Check Procedure permits the operator(s) of the MME and/or the HSS and/or the PDN GW to check the Mobile Equipment's identity (e.g. to check that it has not been stolen, or, to verify that it does not have faults). The ME Identity can be checked by the MME passing it to an Equipment Identity Register (EIR) and then the MME analysing the response from the EIR in order to determine its subsequent actions (e.g. sending an Attach Reject if the EIR indicates that the Mobile Equipment is prohibited). The ME identity check procedure is illustrated in Figure 5.3.10.5-1. Figure 5.3.10.5-1: Identity Check Procedure 1. The MME sends Identity Request (Identity Type) to the UE. The UE responds with Identity Response (Mobile Identity). 2. If the MME is configured to check the IMEI against the EIR, it sends ME Identity Check (ME Identity, IMSI) to EIR. The EIR responds with ME Identity Check Ack (Result). NOTE: The Identity Check Procedure is typically executed as part of the Attach procedure (see clause 5.3.2.1).
description: The Equipment Identity Register (EIR) is a network function that stores and manages information about mobile equipment identities, such as IMEI numbers. It allows the MME to check the identity of mobile equipment against a database of valid or prohibited devices, enabling operators to prevent stolen or faulty devices from accessing the network.
explanation: The EIR is classified as a Network Function because it serves as a centralized repository for managing and verifying mobile equipment identities, interacting with other network functions like the MME to perform identity checks and ensure secure access to the network.
section_title: 5.3.10.5 ME identity check procedure
biotag_Context: O,B-Device,I-Device,B-Parameter,O,O,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,B-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,B-Parameter,O,O,O,O,O,B-Network Function,O,O,O,O,B-Network Function,I-Network Function,I-Network Function,O,O,O,O,B-Network Function,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,B-Network Function,O,O,O,B-Device,I-Device,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,B-Network Function,O,B-Parameter,O,O,O,O,O,O,O,B-Device,O,O,B-Parameter,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Parameter,O,O,O,O,O,B-Network Function,B-Parameter,O,O,O,O,O,O,O,B-Network Function,O,O,B-Network Function,B-Parameter,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: O,B-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O