name: TMGI
full_form: Temporary Mobile Group Identifier
context: the actions upon going to RRC_IDLE as specified in 5.3.11 with release cause 'other'; 1> for each TMGI included in pagingGroupList, if any, included in the Paging message: 2> if the UE has joined an MBS session indicated by the TMGI included in the pagingGroupList: 3> forward the TMGI to the upper layers; 1> if in RRC_INACTIVE and the UE has joined one or more MBS session(s) indicated by the TMGI included in the pagingGroupList; and 1> if none of the ue-Identity included in any of the PagingRecord, if included in the Paging message, matches the UE identity allocated by upper layers: 2> initiate the RRC connection resumption procedure according to 5.3.13 with resumeCause set as below: â¦ 3> else: 4> resumeCause is set to mt-Access. [TS 24.501, clause 5.6.2.2.1] If TMGI is used as paging identity and the TMGI matches with MBS multicast session which the has UE joined, the UE shall respond to the paging. Otherwise, the UE shall not respond to the paging. [TS 24.501, clause 5.3.1.4] â¦ Upon
description: Temporary Mobile Group Identifier (TMGI) is a parameter used in Multimedia Broadcast/Multicast Service (MBMS) to identify a group of users who have joined an MBMS session. It is included in the Paging message and used by the User Equipment (UE) to determine whether it needs to respond to the paging or not.
explanation: The text describes TMGI as a parameter within the context of MBMS, specifically used in Paging messages for UE identification and response determination. This role as a network attribute used for communication control classifies it as a Parameter.
section_title: 14.2.4.1.2MBS Multicast / RRC / Paging for group notification / RRC_INACTIVE
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,B-Device,O,O,O,B-Service,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,B-Service,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,B-Device,O,O,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,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,B-Parameter,O,O,B-Service,O,O,O,O,O,B-Device,O,O,B-Device,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: B-Parameter,I-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,B-Service,I-Service,I-Service,O,O,O,O,O,O,O,O,O,O,O,B-Service,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,B-Device,I-Device,O,O,O,O,O,O,O,O,O,O,O,O,O