HPENets are a family of MLP networks that implement a two-stage ABS-REF architecture with high-dimensional positional encoding to capture intrinsic local 3D geometry.
They replace costly local MLP operations with efficient non-local MLPs by explicitly injecting geometric information via additive HPE, improving feature refinement.
Empirical evaluations show HPENets outperform PointNeXt with reduced FLOPs and enhanced mIoU across multiple point cloud benchmarks.
Searching arXiv for the specified HPENets paper and closely related context.
arXiv Search Query: id:(Zou et al., 4 Mar 2026)
HPENets are a suite of MLP networks for point cloud processing introduced in “Efficient Point Cloud Processing with High-Dimensional Positional Encoding and Non-Local MLPs” (Zou et al., 4 Mar 2026). They are organized around a two-stage abstraction and refinement (ABS-REF) view, and their central technical contribution is a High-dimensional Positional Encoding (HPE) module that explicitly utilizes intrinsic positional information in local 3D neighborhoods. Within this formulation, HPENets replace time-consuming local MLP operations with non-local MLPs for efficient non-local information updates, while using HPE to preserve effective local information representation. The resulting design is presented as readily deployable in MLP-based architectures and compatible with transformer-based methods.
1. ABS-REF formulation and network family
The point of departure for HPENets is an architectural reinterpretation of point cloud processing as a sequence of abstraction and refinement stages. In this view, early models focused on ABS stages, whereas more recent techniques devised sophisticated REF stages to attain performance advantages (Zou et al., 4 Mar 2026). The framework is defined over point positions and features at layer l, denoted Pl and Fl.
In the ABS stage, point resolution is reduced by farthest point sampling,
HPENets instantiate this ABS-REF paradigm as a family rather than a single network. The paper distinguishes HPENet and HPENet V2, and also reports scaled variants such as HPENet V2-S and HPENet V2-XL. A plausible implication is that “HPENets” is best understood as the architectural family formed by combining the ABS-REF decomposition, HPE-based geometric encoding, and scalable refinement stages, rather than as a single fixed backbone.
2. High-dimensional Positional Encoding
The HPE module is defined on point clouds
P={pm∈R1×3}m=1N,F={fm∈R1×C}m=1N,
with
pm=[pmx,pmy,pmz],fm∈RC.
For local neighborhoods centered at Pl0, the geometrically meaningful quantity is the relative coordinate
Pl1
The method emphasizes relative coordinates so that the encoding is translation invariant.
The paper first defines two lower-dimensional positional encodings used as baselines. The sinusoidal version allocates channels in groups of six: Pl2
Pl3
Pl4
Pl5
Pl6
Pl7
The learnable low-dimensional baseline is
Pl8
HPE introduces a two-step construction: high-dimensional projection followed by alignment to the backbone feature space. Its sinusoidal form is
Pl9
and its learnable form is
Fl0
In the original HPENet, Fl1. In HPENet V2, Fl2.
Although these equations are written for a generic point coordinate Fl3, the practical operator is applied to relative coordinates: Fl4
A local feature update can therefore be written as
Fl5
Under a global translation Fl6,
Fl7
so
Fl8
which yields translation invariance.
The paper presents this as an extension of positional encoding from Transformer literature to a 3D, local, relative, high-dimensional geometric encoding tailored to point clouds. This suggests that HPE is not merely a replacement for raw coordinate concatenation, but a feature-space geometric operator for irregular 3D neighborhoods.
3. Local aggregation, non-local MLPs, and HPE-mediated geometry injection
HPENets use HPE to separate explicit geometric encoding from feature propagation. The grouped feature tensor after neighborhood construction is augmented by HPE: Fl9
where Pl+1=FPS(Pl),0. This additive fusion aligns positional information with the same Pl+1=FPS(Pl),1-channel space as grouped features.
The paper analyzes three aggregation operators. Traditional local processing is written as
Pl+1=FPS(Pl),2
while non-local alternatives are
Pl+1=FPS(Pl),3
for PreConv, and
Pl+1=FPS(Pl),4
for ProConv. Here Pl+1=FPS(Pl),5 denotes grouping, Pl+1=FPS(Pl),6 a set operation or MLP, and Pl+1=FPS(Pl),7 a reduction such as max pooling.
The central architectural claim is that local MLPs can be reduced or replaced by non-local MLPs if local geometric information is injected explicitly. PreConv is efficient but weak on local geometry by itself; HPE supplies the missing local 3D structure. The paper therefore adopts a hybrid strategy: in the first ABS stage it keeps a stronger local operator to preserve fine detail, while later ABS and REF stages prefer efficient non-local MLPs, supported by HPE. In REF, because the stage does not change point geometry, the paper further states that HPE is shared within each REF stage to reduce computational costs (Zou et al., 4 Mar 2026).
This division of labor is foundational to HPENets. Non-local MLPs handle efficient feature updates, while HPE carries the local geometry that would otherwise be encoded by repeated local MLP operations.
4. Architectural composition and segmentation pipeline
HPENets are encoder-centric point cloud models built from ABS and REF blocks. A compact architecture description is
Pl+1=FPS(Pl),8
For HPENet V2-XL, the paper gives
Pl+1=FPS(Pl),9
The article’s details distinguish HPENet and HPENet V2 at the block level. In the ABS-stage pseudocode, HPENet applies a local MLP after HPE-enhanced grouping,
This suggests that HPENet V2 pushes the efficiency agenda further by relying more directly on HPE-enhanced grouped features and less on expensive local MLP stacks.
For segmentation, the encoder is complemented by a Backward Fusion Module (BFM). BFM takes high- and low-resolution features, extracts global statistics from DABSl+1(pml+1),KABSl+1(pml+1)=KNN(pml+1,Pl,Fl),2 using max and mean pooling, refines them via inverted-residual MLPs, and uses the resulting attention to update both streams. The overall segmentation pipeline can therefore be summarized as
The paper also states that HPE is compatible with transformer-based methods. This matters because the HPE module is presented not as an MLP-only trick, but as a general positional encoding block for local geometric representation in point cloud backbones.
5. Empirical performance and ablation evidence
The paper reports experiments on seven public datasets across four different tasks and summarizes the most direct comparison against PointNeXt in the abstract (Zou et al., 4 Mar 2026).
The benchmark sections provide the corresponding concrete model figures. On ScanObjectNN, PointNeXt-S reports fml+1=hABS(DABSl+1(pml+1),KABSl+1(pml+1)).2 mAcc, fml+1=hABS(DABSl+1(pml+1),KABSl+1(pml+1)).3 OA, and fml+1=hABS(DABSl+1(pml+1),KABSl+1(pml+1)).4, whereas HPENet V2-S reports fml+1=hABS(DABSl+1(pml+1),KABSl+1(pml+1)).5 mAcc, fml+1=hABS(DABSl+1(pml+1),KABSl+1(pml+1)).6 OA, and fml+1=hABS(DABSl+1(pml+1),KABSl+1(pml+1)).7; HPENet V2-S* reaches fml+1=hABS(DABSl+1(pml+1),KABSl+1(pml+1)).8 mAcc and fml+1=hABS(DABSl+1(pml+1),KABSl+1(pml+1)).9 OA. On S3DIS 6-fold, PointNeXt-XL reports DREFl+1(pml+1),KREFl+1(pml+1)=KNN(pml+1,Pl+1,FABSl+1),0 mIoU and DREFl+1(pml+1),KREFl+1(pml+1)=KNN(pml+1,Pl+1,FABSl+1),1, while HPENet V2-XL reports DREFl+1(pml+1),KREFl+1(pml+1)=KNN(pml+1,Pl+1,FABSl+1),2 mIoU and DREFl+1(pml+1),KREFl+1(pml+1)=KNN(pml+1,Pl+1,FABSl+1),3. On S3DIS Area-5, PointNeXt-XL reports DREFl+1(pml+1),KREFl+1(pml+1)=KNN(pml+1,Pl+1,FABSl+1),4 mIoU and DREFl+1(pml+1),KREFl+1(pml+1)=KNN(pml+1,Pl+1,FABSl+1),5 mAcc, while HPENet V2-XL reports DREFl+1(pml+1),KREFl+1(pml+1)=KNN(pml+1,Pl+1,FABSl+1),6 mIoU and DREFl+1(pml+1),KREFl+1(pml+1)=KNN(pml+1,Pl+1,FABSl+1),7 mAcc, with a best single run at DREFl+1(pml+1),KREFl+1(pml+1)=KNN(pml+1,Pl+1,FABSl+1),8 mIoU. On ScanNet, PointNeXt-XL reports DREFl+1(pml+1),KREFl+1(pml+1)=KNN(pml+1,Pl+1,FABSl+1),9 mIoU and fml+1=hREF(DREFl+1(pml+1),KREFl+1(pml+1)).0, while HPENet V2-XL reports fml+1=hREF(DREFl+1(pml+1),KREFl+1(pml+1)).1 mIoU and fml+1=hREF(DREFl+1(pml+1),KREFl+1(pml+1)).2. On ShapeNetPart, PointNeXt-S(c=160) reports fml+1=hREF(DREFl+1(pml+1),KREFl+1(pml+1)).3 Cls. mIoU, fml+1=hREF(DREFl+1(pml+1),KREFl+1(pml+1)).4 Ins. mIoU, and fml+1=hREF(DREFl+1(pml+1),KREFl+1(pml+1)).5, while HPENet V2-S(c=160) reports fml+1=hREF(DREFl+1(pml+1),KREFl+1(pml+1)).6 Cls. mIoU, fml+1=hREF(DREFl+1(pml+1),KREFl+1(pml+1)).7 Ins. mIoU, and fml+1=hREF(DREFl+1(pml+1),KREFl+1(pml+1)).8, with a best single run of fml+1=hREF(DREFl+1(pml+1),KREFl+1(pml+1)).9 Cls. mIoU and P={pm∈R1×3}m=1N,F={fm∈R1×C}m=1N,0 Ins. mIoU.
Ablation results establish the role of HPE itself. On S3DIS Area-5 for HPENet V2-XL, using no positional encoding gives P={pm∈R1×3}m=1N,F={fm∈R1×C}m=1N,1 mIoU, P={pm∈R1×3}m=1N,F={fm∈R1×C}m=1N,2, and P={pm∈R1×3}m=1N,F={fm∈R1×C}m=1N,3. Using PE in ABS+REF gives P={pm∈R1×3}m=1N,F={fm∈R1×C}m=1N,4 mIoU, P={pm∈R1×3}m=1N,F={fm∈R1×C}m=1N,5, and P={pm∈R1×3}m=1N,F={fm∈R1×C}m=1N,6. Using HPE in ABS+REF gives P={pm∈R1×3}m=1N,F={fm∈R1×C}m=1N,7 mIoU, P={pm∈R1×3}m=1N,F={fm∈R1×C}m=1N,8, and P={pm∈R1×3}m=1N,F={fm∈R1×C}m=1N,9. With BFM, the result is pm=[pmx,pmy,pmz],fm∈RC.0 mIoU, pm=[pmx,pmy,pmz],fm∈RC.1, and pm=[pmx,pmy,pmz],fm∈RC.2. This indicates that HPE introduces moderate overhead relative to PE, while still improving mIoU.
The ablations also clarify several design choices. Replacing relative-coordinate HPE with absolute-coordinate HPE (“HPE (abs)”) drops S3DIS Area-5 mIoU from pm=[pmx,pmy,pmz],fm∈RC.3 to pm=[pmx,pmy,pmz],fm∈RC.4. Multiplicative fusion (“HPE (mul)”) gives pm=[pmx,pmy,pmz],fm∈RC.5 mIoU, below additive fusion. The dimensionality study over
pm=[pmx,pmy,pmz],fm∈RC.6
reports pm=[pmx,pmy,pmz],fm∈RC.7, pm=[pmx,pmy,pmz],fm∈RC.8, pm=[pmx,pmy,pmz],fm∈RC.9, Pl00, and Pl01 mIoU, respectively, making Pl02 the best tradeoff in HPENet V2.
The paper also evaluates HPE beyond MLP backbones. On S3DIS Area-5, Point Transformer improves from Pl03 mIoU at Pl04 to Pl05 mIoU at Pl06 after adding non-local MLPs, HPE, and BFM. Stratified Transformer improves from Pl07 mIoU at Pl08 to Pl09 mIoU at Pl10. This reinforces the paper’s claim that HPE is compatible with transformer-based methods.
6. Scope, interpretation, and limitations
HPENets are best characterized as point cloud networks in which local 3D geometry is made explicit through a high-dimensional, translation-invariant, relative-coordinate positional embedding,
Pl11
Their distinctive contribution is therefore not merely the use of positional encoding, but the use of positional encoding as a first-class geometric representation aligned with backbone feature channels.
This framing also resolves a common misconception. HPENets do not simply concatenate raw coordinates to point features. Instead, they project relative coordinates into a higher-dimensional latent geometric space and then align that representation with the backbone feature dimension. The paper explicitly criticizes low-dimensional alternatives Pl12 and Pl13 as remaining effectively low-dimensional relative to the complexity of local geometric relationships in irregular 3D point sets (Zou et al., 4 Mar 2026).
A second misconception is that HPENets are transformer-specific because HPE extends the “positional encoding” concept from Transformer literature. The paper states the opposite architectural scope: HPE can be readily deployed in MLP-based architectures and is compatible with transformer-based methods. The method is therefore local and geometric in its operational role, even though its conceptual lineage comes from Transformer positional encoding.
The main trade-off made explicit in the ablations is computational rather than conceptual. Relative to standard PE, HPE increases S3DIS Area-5 compute from Pl14 to Pl15 and parameters from Pl16 to Pl17, while improving mIoU from Pl18 to Pl19. This suggests that HPE is not costless. The paper’s broader claim is instead that this cost is justified because HPE enables a larger architectural simplification: replacing time-consuming local MLP operations with non-local MLPs while preserving effective local information representation.
In that sense, HPENets occupy a specific design position in point cloud learning. They do not eliminate local geometry; they relocate it into a dedicated high-dimensional positional representation, and then use that representation to support efficient ABS-REF feature extraction.