name: MBS
full_form: Metropolitan Beacon System
context: as defined in TS 36.401 [31]. eNB-UP: as defined in TS 36.401 [31]. gNB: as defined in TS 38.300 [4]. gNB-CU: as defined in TS 38.401 [2]. gNB-DU: as defined in TS 38.401 [2]. gNB-CU-CP: as defined in TS 38.401 [2]. gNB-CU-UP: as defined in TS 38.401 [2]. MBS-associated signalling: When E1AP messages associated to one MBS session uses the MBS-associated logical E1-connection for association of the message to the MBS session in gNB-CU-CP and gNB-CU-UP. MBS-associated logical E1-connection: The MBS-associated logical E1-connection uses the identities GNB-CU-CP MBS E1AP ID and GNB-CU-UP MBS E1AP ID according to the definition in TS 38.401 [2]. For a received MBS-associated E1AP message the gNB-CU-CP identifies the associated MBS session based on the GNB-CU-CP MBS E1AP ID IE and the gNB-CU-UP identifies the associated MBS session based on the GNB-CU-UP MBS E1AP ID IE. MBS session resource: as defined in TS 38.401 [2]. Multicast F1-U Context: as defined in TS 38.401 [2]. ng-eNB-CU: as
description: The Metropolitan Beacon System (MBS) is a system related to the definition of various terms and concepts within the context of 3GPP specifications, specifically in relation to E1AP messages, logical connections, and session management. It appears to be part of the broader framework for managing communication sessions and signaling within the network.
explanation: MBS is classified as Miscellaneous because it does not fit neatly into other predefined categories such as Protocol, Network Function, Interface, etc., based on the provided context which focuses on definitions related to E1AP messages, logical connections, and session management. The context suggests that MBS is more of a conceptual or systemic element rather than a specific protocol, function, or interface.
section_title: 3.1	Definitions
biotag_Context: O,O,O,B-Specification,O,O,O,O,O,O,B-Specification,O,O,O,O,O,O,B-Specification,O,O,O,O,O,O,B-Specification,O,O,O,O,O,O,B-Specification,O,O,O,O,O,O,B-Specification,O,O,O,O,O,O,B-Specification,O,O,O,O,O,B-Protocol,O,O,O,O,B-Service,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Service,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Service,B-Protocol,B-Parameter,O,O,B-Service,B-Protocol,B-Parameter,O,O,O,O,O,B-Specification,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Service,O,O,O,O,O,B-Service,B-Protocol,B-Parameter,B-Message,O,O,O,O,O,O,B-Service,O,O,O,O,O,B-Service,B-Protocol,B-Parameter,O,B-Service,O,O,O,O,O,B-Specification,O,O,O,B-Interface,O,O,O,O,B-Specification,O,O,O,O
biotag_Description: O,B-Miscellaneous,I-Miscellaneous,I-Miscellaneous,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Organization,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