name: SPR
full_form: Successful PSCell change Report
context: In (NG)EN-DC and NE-DC, the capabilities of a UE supporting MR-DC are carried by different capability containers. Some MR-DC related capabilities are in the MR-DC container e.g. MR-DC band combinations, while other MR-DC related capabilities are contained in the E-UTRA and NR capability containers e.g. feature sets as described in TS 38.300 [3]. The MR-DC capabilities in the MR-DC container need to be visible to both MN and SN, while the capabilities in the E-UTRA and NR containers only need to be visible to the node of the concerned RAT. In NR-DC, all NR-DC related capabilities are in the NR capability container and are visible to both MN and SN. When retrieving MR-DC related capabilities, the MN shall provide an MR-DC filter that affects the MR-DC related capabilities in MR-DC, E-UTRA and NR capability containers. When using different UE capability enquiry messages to retrieve the different containers, the MN shall employ the same MR-DC filter in all enquiry messages. In the E-UTRA
description: The Successful PSCell change Report (SPR) is a message used in the context of optimizing lower layer issues after a successful Primary SCell (PSCell) change. It can be fetched from the User Equipment (UE) by the Master Node (MN) or another node that sent the SPR configuration to the UE, and then forwarded to the Serving Node (SN) for optimization purposes.
explanation: The context describes the SPR as a report generated after a successful PSCell change and retrievable by network nodes. This indicates it's a message exchanged between components, classifying it as a 'Message'.
section_title: 10.18.4	Successful PSCell Change Report
biotag_Context: O,O,O,O,O,O,O,O,B-Device,O,B-Technology,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,B-Technology,O,O,B-Technology,O,O,O,O,B-Technology,O,O,O,O,O,O,B-Technology,O,B-Network,O,O,O,O,O,O,O,O,B-Specification,O,O,O,B-Technology,O,O,O,B-Technology,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Technology,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Technology,O,O,O,B-Network Function,O,O,O,B-Technology,O,O,O,O,B-Technology,O,O,O,O,B-Technology,O,B-Network,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Technology,O,O,O,O,O,O,O,B-Technology
biotag_Description: O,B-Message,I-Message,I-Message,I-Message,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-Device,I-Device,O,O,O,B-Network Function,I-Network Function,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O