name: PER
full_form: Packed Encoding Rules
context: The target scenarios for the UMTS NAICS study are: - Intra-NodeB scenario: Interference between co-located cells in the HomoNet (UE1 in Figure 1) In intra-NodeB scenario, the interfering cell and the serving cell are co-located at the same NodeB. The percentage of UEs in this scenario depends on the number of sectors for the NodeB, for example, 3-sector deployment or 6-sector deployment. - HetNet scenario: Interference between Macro and LPN in the HetNet (UE2 in Figure 1) In HetNet scenario, the communications between Macro and LPN via the RNC can be either instant or with a certain delay. The percentage of UEs in this scenario depends on the deployment of LPN as well as the soft handover parameters. - Inter-NodeB scenario: Interference between non co-located cells in the HomoNet (UE3 in Figure 1) In inter-NodeB scenario, the interfering and serving cells are not co-located. It is noted that the percentage of UEs in this scenario depends on the number of sectors for the NodeB, as well
description: Packed Encoding Rules (PER) is a protocol used for encoding and decoding data in telecommunications, specifically in the context of Hybrid Automatic Repeat Request (HARQ) processes in High-Speed Downlink Shared Channel (HS-DSCH) transmissions. PER is responsible for handling the HARQ protocol, generating ACKs or NACKs, and managing the configuration of the hybrid ARQ protocol provided by Radio Resource Control (RRC) over the MAC-Control Service Access Point (SAP).
explanation: PER is classified as a Protocol because it defines a set of rules and procedures for encoding and decoding data used in HARQ processes within HS-DSCH transmissions. Its role in managing the HARQ protocol, generating acknowledgements (ACKs) or negative acknowledgements (NACKs), and configuring the hybrid ARQ protocol aligns with the core functions of a telecommunications protocol.
section_title: 4.2.3.4	MAC-e/es entity â UE Side
biotag_Context: O,O,O,O,O,B-Technology,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,O,O,B-Device,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,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,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,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: B-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,I-Protocol,I-Protocol,I-Protocol,O,O,O,O,B-Connection,I-Connection,I-Connection,O,O,B-Protocol,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,B-Protocol,I-Protocol,I-Protocol,O,O,O,O,B-Interface,I-Interface,I-Interface,O