name: TMPI
full_form: Temporary IP Multimedia Private Identity
context: product token "3gpp-gba-tmpi" in the user agent request-header field when communicating over Ub. A BSF shall always include the product token "3gpp-gba-tmpi" in the server response-header field when communicating over Ub. NOTE 1a: According to the HTTP specification RFC 7230 [63], the product tokens may contain any text. They are ignored when unknown by a UE or a BSF. 1. The UE sends an HTTP request towards the BSF. When a TMPI associated with the IMPI in use is available on the UE, the UE includes this TMPI in the "username" parameter, otherwise the UE includes the IMPI. 2. The BSF recognises from the structure of the "username" parameter (cf. Annex B.4) whether a TMPI or an IMPI was sent. If a TMPI was sent the BSF looks up the corresponding IMPI in its local database. If the BSF does not find an IMPI corresponding to the received TMPI it returns an appropriate error message to the UE. The UE then deletes the TMPI and retries the request using the IMPI. The BSF retrieves the
description: Temporary IP Multimedia Private Identity (TMPI) is a parameter used in bootstrapping procedures for secure communication over Ub. It is associated with an International Mobile Subscriber Identity (IMPI) and may be included in HTTP requests by the User Equipment (UE) to authenticate with the Bootstrapping Server Function (BSF).
explanation: The context describes TMPI as a value that can be sent in the 'username' parameter of an HTTP request, which is used for authentication purposes. This indicates that TMPI is a specific piece of information or attribute used within the network, fitting the definition of a Parameter.
section_title: 4.5.2	Bootstrapping procedures
biotag_Context: 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,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,B-Specification,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,B-Device,O,O,B-Protocol,O,O,O,O,O,O,B-Parameter,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Device,O,O,B-Parameter,O,O,O,O,O,O,B-Device,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,B-Parameter,O,O,O,O,B-Parameter,O,O,O,B-Network Function,O,O,O,O,B-Parameter,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Parameter,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Network Function,O,O
biotag_Description: B-Parameter,I-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,B-Parameter,I-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,B-Protocol,O,O,O,B-Device,I-Device,O,O,O,O,O,B-Network Function,I-Network Function,I-Network Function,O