Description
PUESBINE is a feature defined in 3GPP TS 23.195, which is titled 'Provision of User Equipment Specific Behaviour Information (UESBI)'. The term appears in the context of core network specifications including TS 25.413 (RANAP) and TS 25.423 (RNSAP), indicating its relevance to the UTRAN interface and control plane signaling. It is referenced as a functionality described by the specification, though the exact acronym expansion is not provided in the standard; it is used as a proper name for a defined capability.
The feature relates to the provisioning and use of UE-specific behavior information in the network. In 3GPP Release 2 and beyond, the concept of UESBI was introduced to allow the core network to store and convey information about a UE's specific behavior or capabilities that may affect how the network handles that UE. This can include aspects such as the UE's supported features, radio access capabilities, or special handling requirements. PUESBINE appears to be a specific instantiation or enhancement within this framework.
According to TS 23.195, the specification defines the procedures and information elements for the provision of UESBI. The PUESBINE feature is described as 'the functionality described by this TS' in early releases, and later as 'as defined in TS 23.195 [33].' This suggests that PUESBINE is not a separate technical component but rather a named feature set whose behavior is entirely specified in TS 23.195. The references in TS 25.413 and TS 25.423 indicate that the feature involves RANAP and RNSAP signaling, likely for transferring UESBI between the core network and the radio access network.
In practice, the PUESBINE feature enables the core network to provide the RAN with information about a UE that can be used to optimize radio resource management, mobility handling, or service delivery. For example, if a UE has specific behavior (such as being a machine-type device or having limited capabilities), the network can adjust its treatment accordingly. This is an early form of what later evolved into richer UE capability and policy frameworks in LTE and 5G.
The feature's presence across many releases (Rel-2 through Rel-19) in the glossary indicates it remained a defined term, though its practical relevance diminished as newer architectures (E-UTRAN, NG-RAN) introduced more sophisticated mechanisms. Nevertheless, it represents an important historical step in 3GPP's efforts to integrate UE-specific information into network operations.
Purpose & Motivation
The PUESBINE feature was created to address the need for the core network to communicate UE-specific behavior information to the radio access network. In early 3GPP releases (starting from Release 2), there was a growing recognition that different UEs might require different handling due to their capabilities, subscription profiles, or operational characteristics. Without a standardized mechanism to convey this information, the RAN would treat all UEs uniformly, potentially leading to suboptimal resource usage or service quality.
By defining UESBI and the PUESBINE feature in TS 23.195, 3GPP provided a structured way for the core network (e.g., MSC, SGSN) to signal relevant UE behavior parameters to the UTRAN via RANAP (TS 25.413) and RNSAP (TS 25.423). This allowed the RAN to make more informed decisions regarding radio resource allocation, handover, and service provisioning.
The feature was motivated by the limitations of earlier systems where such information was either not available or conveyed through proprietary means. Standardizing it ensured interoperability and consistent behavior across different vendors' equipment. While its scope was limited compared to modern UE capability signaling, PUESBINE laid the groundwork for future developments in UE-specific network optimization.
What changed in its specifications
The latest release-to-release comparison of specifications that define PUESBINE feature. Each summary describes the whole specification, not only this term.
Release 12 adds LIPA and SIPTO procedural handling with new IEs, an MBMS Session Re-establishment Indicator IE, and BDS support including GANSS ID coding value 101.
Full comparison in TS 25.413 →Four Branch MIMO for HSDPA, uplink transmit diversity for HSPA, CELL_FACH enhancements, HSUPA MIMO with 64QAM, multiflow data transmission, and SON enhancements.
Full comparison in TS 25.423 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference PUESBINE feature, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.195 v540 | Provision of UE Specific Behaviour Information | Rel-5 read |
| TS 25.413 vj00 | Radio Access Network Application Part (RANAP) | Rel-19 read |
| TS 25.423 vj00 | UTRAN RNSAP Specification | Rel-19 read |