LJP · Asset Group

Sensing-related charging · technical reference

Sensing Charging

A public map of four distinct domain identities for finding, explaining, and organizing sensing-related charging concepts. It is a reference package, not a deployed charging system.

3GPP has studied charging aspects of integrated sensing and communication. Separately, its charging architecture provides general terminology for converged charging, rating, and charging information. LJP uses these sources to frame public reference identities; the sources do not define or endorse this package.

Explore the identitiesInspect sources

Why these distinctions matter

Keep the subject, information, and rating questions separate.

Teams evaluating sensing-related services may need a stable place to discuss what is being charged, how charging information is described, and where rating fits within an architecture. Those are related questions, but a domain name does not answer them or operate the underlying systems. The published pages provide a common starting point for documentation and diligence while allowing a buyer to choose or replace operational providers.

Evidence boundary. TR 28.893 is a technical report about a study. TS 32.240 supplies charging-architecture context. Neither source standardizes LJP's domain labels or establishes an LJP implementation, certification, affiliation, or market adoption.

Four core identities

Each domain has a defined entry role.

Primary hub

sensingcharging.com

The canonical entry to the package map and its source-linked public topics.

Alternative entry

isaccharging.com

A second name for reaching this hub; it redirects here rather than representing another service.

Adjacent identity: ratingfunction.com is independently useful as a rating-architecture reference. It may be included in a package transaction by agreement; it is not a fifth core sensing identity.

Evaluation path

Start with what is public and verifiable.

1. Inspect the terms

Read the two supporting topics and the independent Rating Function reference.

2. Map the need

Determine which identity or documentation role matters to your organization. Similar words alone do not establish an integrated workflow.

3. Scope diligence

Request the package context, ownership evidence, and any controlled material needed for a qualified decision.

Standards and authority

Read the primary context.

Primary documents explain industry terms; the identity map and commercial package are LJP's editorial organization.

Strategic inquiry

Discuss the package in context.

For licensing, stewardship, partnership, or acquisition discussions, describe the identities and technical questions relevant to your organization.

Discuss Sensing Charging