name: PTM
full_form: Point-to-Multipoint
context: Mobility procedures for multicast reception allow the UE in RRC_INACTIVE state to continue receiving MBS service(s) when changing cells without resuming RRC connection if the PTM configuration of the new cell can be acquired by the UE from the multicast MCCH after cell reselection. During an active MBS multicast session, the UE is required to resume RRC connection to get the PTM configuration if the PTM configuration is not provided on the multicast MCCH of the new cell. Even if the UE in RRC_INACTIVE state received indication to stop monitoring PDCCH addressed by G-RNTI for an MBS multicast session in the source cell, the UE acquires MCCH in the reselected cell after cell reselection. The gNB may indicate in the multicast MCCH the list of neighbour cells providing the same MBS multicast service(s) for UEs in RRC_INACTIVE state as provided in the serving cell. This allows the UE, e.g., to resume RRC connection without reading SIB24 and multicast MCCH of the neighbour cell, if the interested service which is activated is not available to the UE in RRC_INACTIVE state. The gNB may provide an indication on cell PDCP COUNT synchronization for an MBS session with PTM configuration in RRCRelease message. If indicated by the gNB, all cells within the RNA are synchronized in terms of PDCP COUNT value to the MRBs of the corresponding MBS service, and the order of MRBs within the list of multicast MRB configuration for the same MBS multicast session in the multicast MCCH message of the last serving cell and (re)selected cell within the RNA should be consistent. Upon reselection to a cell indicated as synchronized in terms of PDCP COUNT value, the UE does not initialize the PDCP state variables. Otherwise, the UE initializes the PDCP state variables as defined in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ]  [8]. The UE may be configured with dedicated frequency priorities in RRCRelease message which the UE applies during cell reselection while receiving data of MBS multicast session in RRC_INACTIVE state. The UE receiving multicast session(s) in RRC_INACTIVE state triggers RRC connection resumption if the latest measured RSRP or RSRQ of the serving cell becomes lower than the threshold configured by the network. The threshold can be configured per MBS session via RRCRelease message or multicast MCCH.
description: Point-to-Multipoint (PTM) is a technology used in mobile networks to enable efficient transmission of data from a single source to multiple destinations. In the context of 3GPP specifications, PTM configuration plays a crucial role in service continuity for multicast reception during cell reselection, allowing user equipment (UE) to continue receiving multimedia broadcast multicast services (MBS) without resuming radio resource control (RRC) connection.
explanation: PTM is classified as a Technology because it refers to the method or technique used for transmitting data in mobile networks. The provided context highlights its application in ensuring service continuity during cell reselection, which aligns with the technological aspect of network operations.
section_title: 16.10.5.3.5 Service Continuity in RRC_INACTIVE
biotag_Context: O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,B-Service,O,O,O,O,O,O,B-Protocol,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,B-Message,O,O,O,O,O,O,B-Service,O,O,O,B-Device,O,O,O,O,B-Protocol,O,O,O,O,B-Technology,O,O,O,B-Technology,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,B-Connection,O,O,B-Parameter,O,O,B-Service,O,O,O,O,O,O,O,B-Device,O,B-Message,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,B-Service,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,B-Message,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Protocol,O,O,O,O,B-Service,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Service,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Service,O,O,O,O,O,B-Message,O,O,O,O,O,O,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,B-Device,O,O,O,O,B-Protocol,O,O,O,O,B-Device,O,O,B-Protocol,O,O,O,O,O,B-Specification,O,O,B-Protocol,I-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,B-Service,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Measurement,O,B-Measurement,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Service,O,O,O,O,O,O,O
biotag_Description: B-Connection,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-Organization,O,B-Technology,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,O,O,O,O,O,O