name: TMGI
full_form: Temporary Mobile Group Identity
context: from GPRS to UMTS or in some further cases described in TS 23.060 [21]). The RAB ASSIGNMENT REQUEST message shall, if supported, include the Correlation ID IE for each RAB established towards a L-GW collocated with the RNC for LIPA operation. If the SIPTO Correlation ID IE is included in the RAB ASSIGNMENT REQUEST message towards the RNC with L-GW function for SIPTO@LN operation, the RNC shall use it for SIPTO@LN operation for the concerned RAB. For each RAB requested to be modified, the message may contain: - RAB ID (mandatory); - NAS Synchronisation Indicator; - RAB parameters; - Transport Layer Information; - User Plane Information. If the UE Aggregate Maximum Bit Rate IE is present in the RAB ASSIGNMENT REQUEST message, the UTRAN shall, if supported, store the received UE Aggregate Maximum Bit Rate parameters to control the aggregate data rate of non-GBR traffic for this UE. The Transport Layer Information IE may be present at a RAB modification except in the case when the only
description: The Temporary Mobile Group Identity (TMGI) is a unique identifier used to identify a group of mobile devices within a specific context, such as MBMS (Multimedia Broadcast Multicast Service) bearer services. It is utilized in the counting process performed by the RNC2 (Radio Network Controller 2) and reported in the Counting Result IE for each cell included in the received MBMS Cell List IE.
explanation: TMGI is classified as an Identifier based on its role as a unique identifier for a group of mobile devices within specific contexts, such as MBMS bearer services. The context highlights its use in counting processes and reporting, which further solidifies its classification as an Identifier.
section_title: 8.5.6.2	Successful Operation
biotag_Context: O,B-Technology,O,B-Technology,O,O,O,O,O,O,O,B-Specification,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,B-Parameter,B-Message,O,O,B-Connection,O,O,O,O,O,O,O,B-Network Function,O,B-Technology,O,O,O,B-Technology,O,B-Parameter,B-Message,O,O,O,O,B-Connection,O,O,O,O,O,B-Network Function,O,O,O,O,B-Technology,O,O,B-Network Function,O,O,O,O,B-Technology,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,B-Connection,B-Parameter,O,O,B-Protocol,O,O,O,B-Connection,O,O,O,O,O,O,B-Protocol,I-Protocol,O,O,O,B-Device,B-Parameter,I-Parameter,I-Parameter,I-Parameter,B-Message,O,O,O,O,B-Connection,O,O,O,O,B-Network,O,O,O,O,O,O,B-Device,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,B-Message,O,O,O,O,O,B-Connection,O,O,O,O,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,B-Service,O,B-Service,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,B-Service,O,O,O