Page 51 - 5G Basics - Core Network Aspects

Core network aspects 1

3.1.7 data origin authentication [b-CCITT X.800]: The corroboration that the source of data received is as
claimed.

3.1.8 named data object (NDO) [b-ITU-T Supplement 35 to Y.3033]: A data object that is identifiable by a
name.

3.1.9 peer-entity authentication [b-CCITT X.800]: The corroboration that a peer entity in an association
is the one claimed.

3.2 Terms defined in this Recommendation

This Recommendation defines the following terms:
3.2.1 DAN element: a network component that forwards messages to producers, consumers, and other
DAN elements.
3.2.2 DAN realm: a set of DAN elements operated under one DAN realization and managed by an
organization. Different DAN realms may adopt different DAN realization such as naming convention,
communication models including push and pull models, name resolution mechanisms, etc.
3.2.3 NDO consumer: a component that makes requests on NDOs.
3.2.4 NDO producer: a component holding NDOs and make them reachable by corresponding requests.
An NDO producer may be an actual owner of the NDO or a delegate of the actual owner.

4 Abbreviations and acronyms
This Recommendation uses the following abbreviations and acronyms:

APL Application
DAN Data Aware Networking
ICN Information Centric Networking
ID Identifier
NDO Named Data Object

5 Conventions

None.

6 Justification
It is essential to define the capabilities of DAN to bring its concept into reality.
Several use case scenarios for DAN have been introduced in [b-ITU-T Supplement 35 to Y.3033]. These use
case scenarios can be realized in different ways, e.g., with different combinations of capabilities. This aspect
encourages us to identify the capabilities of DAN to realize various use case scenarios.
For this reason, this Recommendation intends to specify the requirements of DAN which are derived from
the use case scenarios, and then defines its capabilities considering previously carried studies: name or ID
based communication [ITU-T Y.3031] [ITU-T Y.3033] [ITU-T Y.3034]. Understanding the requirements and
components of DAN will enable us to enrich the process of developing additional use case scenarios.

7 Requirements for DAN

7.1 Forwarding
• NDO name based forwarding function:

It is required that a request is forwarded by attaching the name or ID of the NDO to the request.

41