name: TAB
full_form: Time alignment bit
context: This clause describes interworking between the control-plane LCS architecture, as defined in the main body of this specification, and SUPL 2.0. The E-SMLC either includes or has an interface to an SPC function as defined in OMA SUPL V2.0 ([17], [18]). It can thus provide a consistent set of positioning methods for deployments utilizing both control-plane and user-plane. The interworking does not enable use of user-plane signalling for part of a control-plane positioning session. The user plane in the interworking here is not intended as an alternative path for control-plane signalling that would be needed between UE and eNodeB for mechanisms such as A-GPS in a standalone C-plane solution. This interworking does enable the SPC to retrieve measurements (e.g., GNSS-to-RAN time relations) from eNodeB. The underlying architecture is shown in Figure B.2-1. Note that, for interworking between user-plane and control-plane positioning, no new interfaces need to be defined as compared to those
description: The Time Alignment Bit (TAB) is a parameter used in the context of multi-band operation for AAS BS (Active Antenna System Base Station). It refers to specific settings or configurations applied to TAB connectors, which are part of the antenna system. These settings can vary depending on whether the operating band is supported by single-band or multi-band TAB connectors within a specific group. The requirements for these settings are detailed in the 3GPP specification and are crucial for ensuring proper operation and conformance testing of the AAS BS across different bands.
explanation: TAB is classified as a Parameter because it refers to specific configurations or settings applied to TAB connectors in the context of multi-band operation. The provided context highlights how these settings can change based on whether an operating band is supported by single-band or multi-band TAB connectors, indicating that TAB is a configurable aspect of the AAS BS system.
section_title: 4.7	Requirements for AAS BS capable of multi-band operation
biotag_Context: O,O,O,O,O,O,O,B-Service,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,B-Organization,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,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,B-Device,O,B-Network Function,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,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
biotag_Description: O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,B-Network Function,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,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,O,O,O,O,O,O,B-Organization,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,B-Network Function,O,O,O