name: NSAPI
full_form: Network Service Access Point Identifier
context: Diameter is used as the protocol between the GGSN and a Diameter server or proxy for applications (e.g. MMS) to deliver information related to GPRS user session. However some IP applications could need to interwork with the GGSN to terminate a particular PDP context. For this purpose, the Diameter server or proxy may send a Diameter ASR to the GGSN along with the NSAPI necessary to identify the particular PDP context to be terminated. As depicted in figure 25d, the GGSN should react by deleting the corresponding PDP context. If the GGSN deletes the corresponding PDP context, it need not wait for the DeletePDPContextResponse from the SGSN before sending the ASA to the server.
  The absence of the NSAPI in the Diameter ASR message indicates to the GGSN that all PDP contexts for this particular user and sharing the same user session shall be deleted. The PDP contexts belonging to the same IP-CAN session are identified by the Diameter Session-Id. If a user has the same user IP address for different sets of PDP contexts towards different networks, only the PDP contexts linked to the one identified by the Diameter Session-Id shall be deleted.
  NOTE:        As showed on figure 25d, the GGSN need not wait for the DeletePDPContextResponse from the SGSN to send the ASA to the Diameter server.
  Figure 25d: PDP Context deletion with Diameter
description: The NSAPI (Network Service Access Point Identifier) is an identifier used in the Diameter protocol to identify a particular PDP context. It is included in the ASR message to specify which PDP context should be terminated.
explanation: NSAPI is a ldentifier because it facilitates signaling for session identification between network components.
biotag_Context: O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,B-Network Function,O,O,O,B-Parameter,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Protocol,O,O,O,B-Network Function,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Message,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Message,O,O,O,O,B-Network Function,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Protocol,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,B-Network Function,O,O,O,B-Message,O,O,O,O,O,O,B-Protocol,O,O,O,O
biotag_Description: O,B-Parameter,O,B-Interface,I-Interface,I-Interface,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Message,O,O,O,O,B-Protocol,O,O,O,O