name: DOFFFDD
full_form: FDD Default DPCH Offset value
context: cell to which the UE sends an UL RRC message (the measurement information will be received via the CN in this case) but for a reference cell selected by the UE. All other reported OFF values will be relative to the SFN of this selected reference cell]. [FDD â DOFFFDD] The DOFFFDD (FDD Default DPCH Offset value) is used to define Frame Offset and Chip Offset at first RL setup. The DOFFFDD is used for both the DPCH and the F-DPCH. The resolution should be good enough to spread out load over Iub and load in Node B (based on certain load distributing algorithms). In addition it is used to spread out the location of Pilot Symbol in order to reduce the peak DL power since Pilot symbol is always transmitting at the fixed location within a slot (the largest number of chips for one symbol is 512 chips). The SRNC sends a DOFFFDD parameter to the UE when the new RL will make the UE change its state (from Cell_FACH state or other when coming from another RAN) to Cell_DCH state. Resolution: 512
description: The FDD Default DPCH Offset value (DOFFFDD) is a parameter used in the first Radio Link (RL) setup to define Frame Offset and Chip Offset for both the Dedicated Physical Channel (DPCH) and the Forward-link Dedicated Physical Channel (F-DPCH). It helps distribute load over the Iub interface and Node B, as well as reduces peak downlink power by spreading out the location of Pilot Symbols. The Serving Radio Network Controller (SRNC) sends this parameter to the User Equipment (UE) when transitioning from Cell_FACH or another state to Cell_DCH state.
explanation: The context describes DOFFFDD as a value used to configure network behavior, specifically defining offsets and influencing resource allocation. This aligns with the definition of a 'Parameter' which is a configurable setting that affects system operation.
section_title: 5	Synchronisation Counters and Parameters
biotag_Context: O,O,O,O,B-Device,O,O,B-Connection,B-Protocol,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,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,B-Parameter,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,I-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,O,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,O,B-Network Function,O,O,B-Parameter,O,O,O,B-Device,O,O,O,B-Connection,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: O,B-Parameter,I-Parameter,I-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O,O,B-Connection,I-Connection,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,I-Connection,I-Connection,O,O,O,O,B-Connection,I-Connection,I-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,O,O,O,O,B-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,B-Device,I-Device,O,O,O,O,O,O,O,O,O,O,O