Original Message:
Sent: Aug 22, 2023 11:16
From: Jonathan Goldberg
Subject: TMF908 (early adoption); serialNumber & modelNumber
I'm afraid that I'm not familiar with the SID in this area, so I don't know how to advise you. Perhaps @Kevin Scaggs from the SID team could advise here?
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
Original Message:
Sent: Aug 22, 2023 01:40
From: Chio Chuan Ooi
Subject: TMF908 (early adoption); serialNumber & modelNumber
Hi @Jonathan Goldberg,
based on the SID description of resource -
The Resource domain represents roles, information and activities carried out by parties (e.g., individuals / organizations) playing roles that are involved in the strategic planning, definition, development and operational aspects of Resources (e.g., functions, applications, computing, networking and storage) that represent the infrastructure of an enterprise that are used to realize Services. Activities include management of strategies, capabilities, lifecycles, catalogs, inventories, topologies, installations, activations, alarms, problems, performance, mediation, usage statistics and support of Resources that are managed by an enterprise.
i try to interpret that resource in SID mean is the resource that represent/managed by an enterprise, not sure if that correct understand.
As if that is the correct understanding, since IoT devices that connected to enterprise resource, but it not belongs to enterprise nor managed by enterprise, would it be still consider as resource?
i trying to link the entity as below, can the entity that not belongs/managed by enterprise also consider as resource entity?
------------------------------
Chio Chuan Ooi
SingTel Optus
Original Message:
Sent: Aug 21, 2023 10:15
From: Jonathan Goldberg
Subject: TMF908 (early adoption); serialNumber & modelNumber
Hi Chio
I'm not very familiar with the IoT API suite (TMF908). But to my best understanding, the IoTDevice entity has the following inheritance change that eventually leads to Resource:
IoTDevice > Device > PhysicalResource > Resource
So by using a more specialized representation you still gain all the properties of the parent (Resource).
But I really don't know how to advise you which API to use for your use case, sorry.
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
Original Message:
Sent: Aug 21, 2023 05:26
From: Chio Chuan Ooi
Subject: TMF908 (early adoption); serialNumber & modelNumber
Hi @Jonathan Goldberg,
For those IoT device that is not being managed by organization, can it be classified as resource?
We trying to explore an API that to retrieve list of the IoT device that connected to CPE (network router), but IoT device is not being managed by organization, only the CPE (network router) are being manage.
Is TMF702 or TMF908 is better suit this use case?
Regards,
chio chuan
------------------------------
Chio Chuan Ooi
SingTel Optus
Original Message:
Sent: Aug 06, 2021 04:04
From: Jonathan Goldberg
Subject: TMF908 (early adoption); serialNumber & modelNumber
Hi Karen
I was wondering - why would you use IoT management for set-top box activation, and not, say, the dedicated Resource Activation API TMF702?
At any rate, serialNumber is an attribute of PhysicalResource (as well as of IoT-based entities), the documentation there refers to model and part, which are attributes of the corresponding PhysicalResourceSpecification from the Resource Catalog (TMF634).
I think we need to correct the documentation so it will say model and part (not ModelNumber and PartNumber).
Hope it helps
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
Original Message:
Sent: Aug 05, 2021 17:28
From: Karen Aiken
Subject: TMF908 (early adoption); serialNumber & modelNumber
Good day -
We're leveraging TMF908 IoT Device Management for a couple use cases, the latest is to activate TV Set-top Boxes. We gravitated to it as it provides a fairly comprehensive set of attributes for configurable resources. Is that a reasonable use case for this spec?
In using it - we noted that serialNumber is flagged in the PDF spec as being required; it doesn't seem to be so in the swagger file. Just wondering which is correct - for our case, we updated the swagger to make it required.
The description for serialNumber mentions a modelNumber property which I don't see listed - that would be a property we'd be interested in. Curious to know if it's planned?
Appreciate your insights,
Take care,
------------------------------
Karen Aiken
Strategy Manager, Integration Architecture
TELUS
------------------------------