Correlating a Dedicated Network resource within a subsequent IoT Data Transfer Activation API call

[tlohmar]

Problem description
The IoT Data Transfer Activation API plans to use the Dedicated Network API for scheduling resource reservations (see Issue#14 ). The Dedicated Network API needs to provide some sort of Dedicated Network identifier, which can be used by the IoT Data Transfer Activation API for correlation.

Possible evolution

Alternative solution

Additional context

[varanto]

Hi,

Based on the provided documentation, I would like to ask for more information on the following aspects regarding the identifier to better analyze how it can be used in the IoT Data Transfer Activation API:

• is the id unique and immutable?
• what is the expected lifecycle of the id (e.g., validity period, reuse rules)?
• using the identifier, what is the associated data we can retrieve (i.e., information conveyed by its associated attributes)?

Thanks,
Antonio

[varanto]

Hi,

Are there any feedback on my previous comment?

Thanks,
Antonio

[tlohmar]

Hi @Varato,

more information on the following aspects regarding the identifier

A unique identifier (Network Id) is returned, when requesting a dedicated network. The identifier remains unchanged during the lifetime of the requested dedicated network. The Network Id is a path element of the URL, which is returned when creating a dedicated network.

is the id unique and immutable?

yes, the id (aka URL) is unique.

what is the expected lifecycle of the id (e.g., validity period, reuse rules)?

The lifecycle passes through multiple states, starting with a requested state immediately after creation. Based on the CSP decision, the network passes into the next state, which can be reserved, activated or terminated.

• The reserved state is optional and depends on the desired start datetime of the reservation.
• The state transition to activated happens automatically and depend the provided reservation start datetime.
• The state transition to terminated happens either automatically (depending on the provided reservation end datetime) or event drive (e.g. the CSP rejects the network creation request).

Additional states are ffs.

using the identifier, what is the associated data we can retrieve (i.e., information conveyed by its associated attributes)?

The network identifier points to the reserved resources for a specific time window and at a specific service area. The reserved resources can be a throughput and one or more QOS profiles (as used in QOD).

Handling the access of devices to the dedicated network and its reserved resources is handled by the accesses API. A device is identified by either an MSISDN or an Network Access Identifier (NAI).

A device can certainly be a IOT Device. The dedicated network characteristics can include QOS profiles, suitable for IOT data transfer.