12.36 Use case for automatic recognition of identification schemes for heterogeneous IoT identifiers
12.36.1 Description
In Internet of Things (IoT), a unique identifier is required for each object to serve as a digital identity. An identifier is represented using a sequence of numbers, characters, or a combination of them, and the detailed description information about the identified object can be indexed and discovered. For example, people can get the price, place of origin and manufacturer information of a commodity by scanning the product barcode, and the serial number on the barcode is the Global Standard 1 (GS1) identifier of this commodity. However, due to political, commercial and other reasons, there are thousands even tens of thousands of types of IoT identifiers co-existing in the IoT ecosystem (e.g. EPC, Handle, OID, etc.). These schemes have different encoding lengths, value ranges and structures, and each scheme has its own customized resolution rules. It requires different resolution systems to resolve these heterogeneous identifiers respectively. So, if we want to obtain the profile information about an object, the identification scheme of this object's identifier should be known in advance.
Currently, the co-existence of multiple objects tagged by different types of identifiers is becoming the norm. It is unrealistic to require all IoT objects to use the same kind of identifier scheme in IoT applications. Therefore, oneM2M System is required to recognize the identification schemes of IoT identifiers to support the unified resolution of heterogeneous IoT identifiers.
Take commodity source tracing for example. The lifecycle of a commodity is composed of a series of processes including material purchase, manufacturing, storage, transportation, sales, etc. In each process, different manufacturers will choose their conventional identification schemes to identify the commodity. If an application wants to acquire the detailed information about this commodity throughout the chain (of processes), the identification schemes of the identifiers in these processes should be known at first. To satisfy the requirements, the oneM2M System shall be able to recognize the identification schemes of these heterogeneous IoT identifiers from different processes.
12.36.2 Source
RDM-2021-0027R02-use_case_for_automatic_recognition_of_identification_schemes_for_heterogeneous_IoT_identifiers
12.36.3 Actors
- Application: a device or a user who wants to recognize the identification scheme of an IoT identifier and configure the identified device in an oneM2M deployment.
- The M2M service platform provided by the M2M service provider.
- a. The M2M service platform has a heterogeneous identification function to automatically recognize the identification scheme of an IoT identifier. It's a service layer functionality provided by the oneM2M System.
12.36.4 Pre-conditions
The identifier recognition model is required to be deployed on the M2M service platform.
Provision the device in oneM2M, which includes:
- a. Associate with the user profile;
- b. Provide security credentials.
12.36.5 Triggers
The identification scheme of an object's identifier is required to be automatically recognized.
12.36.6 Normal Flow
The normal message flow is described as follows:
Figure 12.36.6-1-1: Message flow for automatic recognition of identification schemes for heterogeneous IoT identifiers
- An application sends a request to the M2M service platform to recognize the identification scheme of an IoT identifier and then configure the device in an oneM2M deployment. The identifier recognition model is deployed on the M2M service platform which manifests as a rule base or a machine learning classification model.
- After receiving the request, the oneM2M platform recognizes the identification scheme of the identifier based on the heterogeneous identification function.
- Based on the identifier and its identification scheme, the oneM2M platform captures the device management information from the M2M service provider and populates it with new configuration information.
- a. This identifier becomes a M2M External Identifier (M2M-Ext-ID);
- b. Populate node resource and device management resources like firmware object, software object, etc.
- The oneM2M platform returns the result to the application. This can be success or configuration complete message.
12.36.7 Alternative flow
Step 3 above could include an automatic trigger to begin a firmware update with the M2M service provider.
Or the M2M service provider could create resources on behalf of the device/application..
12.36.8 Post-conditions
None
12.36.9 High Level Illustration
Figure 12.25.9-1: High Level Illustration
12.36.10 Potential requirements
The oneM2M system shall be able to support heterogeneous identification services, the recognition of external identification systems and converting an object identifier to a compatible identifier recognized by the oneM2M system.