name: MSISDN
full_form: Mobile Subscriber ISDN Number
context: IMSI. The active IMSI catcher, however, can ask the UE to provide its IMSI. The MME and the HSS have the MSISDN of the subscription. Note that the MSISDN might be available to the UE as well, e.g. optionally stored in USIM or requested via MSISDN notification procedure. However, the UE does not use the MSISDN for operational purposes. Editorâs Note: This analysis may be moved to the annex as LTE reference and replaced by Next Generation architecture analysis, once SA2 has settled on architecture. Figure 5.7.3.2.1-1: Various points where IMSI and MSISDN are exposed in a current LTE system Interfaces and functions that do not need to be considered further in this key issue The UE has the IMSI. Protecting the leakage of IMSI due to hardware or software vulnerability in the UE is out of scope of this key issue. Similarly, the HSS has both the IMSI and the MSISDN. Protecting the information leakage in the HSS is out of scope this key issue. The use of IPsec in S1-MME and S6a is not
description: The Mobile Subscriber ISDN Number (MSISDN) is a critical network attribute used to identify a mobile subscriber's telephone number within the telecommunications network. It is stored in various network components, including the MME and HSS, and may be optionally stored in the USIM or requested via MSISDN notification procedure.
explanation: The context explicitly mentions that the MSISDN is a key attribute used to identify a mobile subscriber's telephone number, highlighting its role as a parameter within the network. The fact that it is stored in various network components and may be used for specific procedures further solidifies its classification as a Parameter.
section_title: 5.7.3.2.1	Key issue details
biotag_Context: O,O,O,B-Parameter,O,O,O,O,O,B-Device,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,B-Parameter,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,B-Device,O,O,O,O,O,O,B-Device,O,O,O,B-Parameter,O,O,O,O,B-Device,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,B-Network,I-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,B-Parameter,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,B-Interface,O,O,O,O
biotag_Description: O,B-Parameter,I-Parameter,I-Parameter,I-Parameter,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,B-Network Function,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,B-Parameter,O,O