LJP · ASSET GROUP
6G Sensing Fabric · Technical Reference

Sensing Profiles

What does Sensing Profiles represent within the 6G Sensing Fabric?

Sensing Profiles represents concepts associated with an LJP semantic abstraction for requirements, KPIs, and constraints. The abstraction helps group requirement context without claiming a standards construct called a Sensing Profile. Within Sensing Objectives, Profiles, Capabilities & Services, it is the primary identity.

Why it matters: The abstraction helps group requirement context without claiming a standards construct called a Sensing Profile.

§1 — Definition

Sensing Profiles

Sensing Profiles provides a stable semantic identity for an LJP semantic abstraction for requirements, KPIs, and constraints.

§2 — Relationships

Closest comparison and adjacent concepts.

Related concepts are linked only for plain-language orientation within the three LJP views. The links do not assert standards-derived dependencies, protocol order, execution, or formal predicates.

Difference

What separates them

Sensing Profiles identifies an LJP semantic abstraction for requirements, KPIs, and constraints; sensingobjective.com identifies an adjacent but distinct concept.

Relationship

How they work together

Both concepts belong to the LJP package network. Their adjacency is an LJP synthesis and does not assert a standards-defined dependency or executed flow.

See also

§3 — Standards and Authority

Where the terminology comes from.

ETSI GR ISC 001 V1.1.1 (2025-03) and ITU-T YSTR.ISAC-fra (11/2025), clauses 6 and 7, support requirements, KPIs, capability information, and service context. No reviewed source defines a standardized construct called a 'Sensing Profile'; this remains an LJP semantic abstraction. Evidence: C; LJP package relationships: E.

§4 — Evaluation

Apply the distinction to the decision at hand.

Use this identity to frame the concept and its evidence boundary before selecting any implementation, supplier, or operating design.

Continue to a controlled evaluation.

§5 — LJP Foundation

How this capability fits the package.

The domain identifies and describes an LJP semantic abstraction for requirements, KPIs, and constraints; it does not perform, operate, execute, expose, manage, transport, process, verify, or implement a network function or standard.

Primary in Sensing Objectives, Profiles, Capabilities & Services. The view asks: What sensing can be provided against a requirement?

§6 — Machine-Readable Resources

Public identity and discovery resources.

§7 — Credibility Boundary

What this reference does not claim.

The three-view organization and semantic capability traverse are an LJP synthesis and do not constitute an official 3GPP architecture or standardized taxonomy. Individual technical concepts are mapped to primary-source specifications and study items according to their verified publication status. The domain provides stable semantic identity and authority for a concept. Operational implementations and service providers remain replaceable.

This namespace is an LJP editorial construct. It claims no standards ownership or external endorsement and selects no vendor or implementation; protected methods and transaction materials are not disclosed.

Evaluate Sensing Profiles in context.

Move from public technical orientation to a controlled package evaluation.

Email LJP Asset Group