KR102270481B1 - NGSI-LD API Wrapping Method - Google Patents

Abstract

An NGSI-LD API wrapping method is provided. In the resource wrapping method according to an embodiment of the present invention, Entity, Property, and Relationship of NGSI-LD are generated as resources, respectively, an Entity ID is stored, and an NGSI-LD resource indicating an Entity resource indicating the Entity is generated. Accordingly, by implementing the NGSI-LD API on the oneM2M international standard platform, the data collected on the oneM2M platform can be utilized by external platforms and applications applying NGSI-LD.

Description

NGSI-LD API Wrapping Method

The present invention relates to API Wrapping technology, and more particularly, to an API Wrapping method for implementing an NGSI-LD API in an international standard platform such as oneM2M.

NGSI-LD (Next Generation Service Interface - Linked Data) is a standard interface of ETSI that adds the information model concept to support Linked Data to the NGSI-9/10 API of the conventional OMA. It can express relationships between data in various domains. .

The information model of NGSI-LD is presented in FIG. 1 . The information model of NGSI-LD consists of Entity, Property, and Relationship. Details of Entity, Property, and Relationship are shown in FIGS. 2, 3 and 4, respectively.

In the information model of NGSI-LD, when searching for an entity, property and relationship information about the entity is returned. For example, as shown in FIG. 5 , when a car, a police station, and a street lamp are each configured as entities, when a car crashes into a street light, as shown in FIG. It returns property and relationship information for

An object of the present invention is to provide an API Wrapping method for implementing the NGSI-LD API in the oneM2M platform as a method for enabling external platforms and applications to which NGSI-LD is applied to utilize data collected on the oneM2M international standard platform. have.

According to an embodiment of the present invention for achieving the above object, a resource wrapping method includes: creating entities, properties, and relationships of heterogeneous data conforming to a standard of a heterogeneous platform as resources; and storing an Entity ID of heterogeneous data, and generating a first resource indicating an Entity resource indicating an Entity.

The Entity resource may have a Property resource indicating a Property and a Relationship resource indicating a Relationship as sub-resources.

A resource indicating Property and Relationship is a child resource, and a resource wrapping method, characterized in that it has a resource indicating another Property and Relationship.

The relationship resource may refer to a second resource having a different Entity ID from the first resource.

The first resource may store Entity ID as an attribute, and the Entity, Property, and Relationship resource may store attribute values indicating Entity, Property, and Relationship.

The resource wrapping method according to an embodiment of the present invention includes, when a query is requested, returning information about an Entity resource pointed to by the first resource, a Property resource that the Entity resource has as a child resource, and a Relationship resource in a response; can do.

The inquiry request may specify a procedure to be performed by postfix which is received in the virtual resource that processes the inquiry request and is added to the ID of the virtual resource.

On the other hand, according to another embodiment of the present invention, the M2M platform, a communication unit for communicating with an external device; and a processor that generates Entity, Property, and Relationship of heterogeneous data according to the standard of the heterogeneous platform as resources, stores the Entity ID of the heterogeneous data, and generates a first resource pointing to the Entity resource indicating the entity; includes; .

As described above, according to embodiments of the present invention, by implementing the NGSI-LD API on the oneM2M international standard platform, data collected on the oneM2M platform can be utilized by external platforms and applications to which NGSI-LD is applied.

1 is an information model of NGSI-LD;
2 to 4 are diagrams showing details of Entity, Property, and Relationship of NGSI-LD;
5 and 6 are diagrams provided for explanation of information inquiry and return in NGSI-LD;
7 is a diagram provided in the conceptual description of the NGSI-LD API;
8 and 9 are diagrams provided to explain a mapping method between oneM2M resources and NGSI-LD Entity;
10 is a table showing an NGSI-LD to oneM2M resource path mapping scheme;
11 is a diagram illustrating NGSI-LD API Wrapping;
12 is a diagram illustrating an NGSI-LD API mapping scheme to oneM2M standard;
13 is a diagram illustrating a response message returned when an NGSI-LD API is called;
14 is a view showing an IoT / M2M system to which the present invention is applicable, and,
FIG. 15 is an internal block diagram of the electronic devices shown in FIG. 14 .

Hereinafter, the present invention will be described in more detail with reference to the drawings.

oneM2M is an IoT middleware platform standard technology and is being used to develop application services in various domains of IoT and smart city. The oneM2M standard that aims for a RESTful architecture defines a resource for storing data as a Content Sharing Resource, and by using resource types such as container, contentInstance, and flexContainer, data that can be shared between applications can be stored on the platform and management functions can be utilized. .

In an embodiment of the present invention, an API Wrapping design proposal is presented as a method for implementing the NGSI-LD API as an additional interface of the oneM2M platform. Through this, as shown in FIG. 7 , data collected on the oneM2M platform can be utilized by external platforms and applications to which NGSI-LD is applied.

8 is a diagram provided to explain a mapping method between a container/contentInstance resource and an NGSI-LD Entity among oneM2M resources.

To express an NGSI-LD Entity in oneM2M, a <NGSI-LD> resource is defined as a new resource type, and Entity, Property, and Relationship are created as resources, respectively.

In an embodiment of the present invention, the <NGSI-LD> resource is mapped to a container/contentInstance resource among Data Sharing Resources defined by oneM2M.

This <NGSI-LD> resource has the Entity ID defined in the NGSI-LD API as an attribute (eg, resourceName), and points to (refer to) a <container> resource (eg, entityResourceID) indicating the Entity.

A <container> resource indicating an Entity has a sub <container> resource indicating a Property and a Relationship. And, <container> resources have attribute values (eg, label = ["NGSI-LD Property"]) for indicating Entity, Property, and Relationship.

The oneM2M platform stores the attribute values of Entity, Property, and Relationship defined in the NGSI-LD API as a <contentInstance> resource as a child of the <container> resource.

A <container> resource indicating a property or relationship can have a <container> resource indicating another property or relationship as a child. In addition, the <container> resource indicating the relationship points to another <NGSI-LD> resource.

Furthermore, in order to inquire NGSI-LD Entity, oneM2M defines a virtual resource for inquiry. In an embodiment of the present invention, the virtual resource for inquiry is created as a child resource (in FIG. 8, an entity) of the <NGSI-LD> resource.

When requesting a virtual resource for inquiry, the resource and sub-resource pointed to by the <NGSI-LD> resource and the entity, property, and relationship information stored in other resources pointed to by these resources are returned as NGSI-LD Entity.

That is, when calling the NGSI-LD API, the oneM2M platform converts the resources stored in the oneM2M resource tree format into an NGSI-LD Entity and returns a response.

9 is a diagram provided to explain a mapping method between a <flexContainer> resource among oneM2M resources and an NGSI-LD entity.

In an embodiment of the present invention, the <NGSI-LD> resource is mapped to the <flexContainer> resource among Data Sharing Resources defined in oneM2M.

This <NGSI-LD> resource has the Entity ID defined in the NGSI-LD API as an attribute (eg, resourceName) and points to a <flexContainer> resource (eg, entityResourceID) indicating the Entity.

A <flexContainer> resource indicating an Entity has a lower <flexContainer> resource indicating a Property and a Relationship. And, <flexContainer> resources have property values (eg, label = ["NGSI-LD Property"]) for indicating Entity, Property, and Relationship.

The oneM2M platform stores the property values of Entity, Property, and Relationship defined in the NGSI-LD API as a <flexContainer> resource as a child of the <flexContainer> resource.

A <flexContainer> resource indicating a property or relationship can have a <flexContainer> resource indicating another property or relationship as a child. In addition, the <flexContainer> resource indicating the relationship points to another <NGSI-LD> resource.

An API mapping scheme for supporting the NGSI-LD API through the oneM2M resource mapping structure described above is presented in FIG. 10 . 10 is a table illustrating an NGSI-LD to oneM2M resource path mapping scheme.

Here, the concept of a oneM2M virtual resource that cannot be instantiated as a kind of API endpoint that provides a specific function is applied to temporal and entities resources of NGSI-LD.

For example, when the oneM2M platform receives the /entities/{entityId} query API request of NGSI-LD to inquire a specific entity, as shown in FIG. 11, it is actually processed in the entities virtual resource, and is a sub-resource path. Identifies the NGSI-LD resource corresponding to the entityId in the resource tree in /{entityId}, merges the resources in which Entity, Property, and Relationship information are stored in the NGSI-LD resource to create and return the JSON-LD object of the NGSI-LD entity. do.

And, as shown in FIG. 12 , an NGSI-LD API call may be mapped by additionally defining a postfix in the virtual resource ID, and the NGSI-LD API may be called by targeting temporal and entities virtual resources.

In this case, the procedure determined by postfix that comes after the virtual resource name is performed. In other words, different actions are performed for each mapped oneM2M resource (modify attribute, create new contentInstance, update flexContainer), and perform Query defined in NGSI-LD API (e.g., query in /entities/ with Query to inquire only filtered entities) ) is possible.

So far, a preferred embodiment of the API Wrapping method for implementing the NGSI-LD API in the oneM2M platform is a method to enable external platforms and applications to which NGSI-LD is applied to utilize the data collected on the oneM2M international standard platform. has been described in detail.

On the other hand, when calling the NGSI-LD API (when sending a request message), a method for distinguishing between the existing oneM2M API and the NGSI-LD API is required. For this, a resource path can be distinguished by a prefix for the NGSI-LD API (eg, ngsi-ld/entities/entity_001). In addition, it can be classified by the request message parameter (eg, NGSI-LD-Request: True). In addition, the query of the NGSI-LD API can be used only when the NGSI-LD API is called, and it can also be mapped as a Query String parameter of oneM2M.

In addition, when the NGSI-LD API is called, the response message is returned in the oneM2M existing response message format, but as shown in FIG. 13, the Response Status Code response message parameter value is mapped with the processing result of the NGSI-LD and set, The NGSI-LD response message can be included in the Content response message parameter.

14 is a diagram illustrating an IoT/M2M system to which the present invention is applicable. As shown in FIG. 14 , the IoT/M2M system to which the present invention is applicable includes a server 100-1, a gateway 100-21, 100-22, and a device 100-31, 100-32, 100-33. , 100-34) are connected and constructed so that various electronic devices can communicate with each other.

The number of electronic devices shown in FIG. 14, for example, the server 100-1, the gateways 100-21, 100-22, and the devices 100-31, 100-32, 100- that constitute the IoT/M2M system 33, 100-34) are exemplary, and therefore, the technical idea of the present invention can be applied even when implemented differently.

Furthermore, it goes without saying that the connection structure of the electronic devices shown in FIG. 14 may also be replaced by other methods, if necessary.

All of the electronic devices shown in FIG. 14 may function as the oneM2M platform described above. That is, the server 100-1, the gateways 100-21, 100-22, and the devices 100-31, 100-32, 100-33, and 100-34 are all NGSI-LD APIs according to an embodiment of the present invention. that can support

FIG. 15 is an internal block diagram of the electronic devices shown in FIG. 14 . Configurations necessary for implementing an embodiment of the present invention are the server 100-1, the gateways 100-21, 100-22, and the devices 100-31, 100-32, 100-33, 100-34. common Accordingly, in FIG. 15 , these are collectively referred to as “100”, and hereinafter will be collectively referred to as an electronic device.

As shown in FIG. 15 , electronic devices according to another embodiment of the present invention include a communication unit 110 , a processor 120 , a storage unit 130 , and a function block 140 .

The communication unit 110 is a communication interface means for communicating with an external device and accessing an external network.

The processor 120 includes at least one Application Entity (AE) and a Common Service Entity (CSE). Depending on the type and function of the electronic device, AE may not be included.

The processor 120 performs procedures necessary to support the NGSI-LD API presented above, and the storage unit 130 provides a storage space necessary for the processor 120 to provide a corresponding service.

The function block 140 performs an original function of the electronic device. For example, when the electronic device is the server 100 - 1 , virtual machines providing user services correspond to the function block 140 .

On the other hand, it goes without saying that the technical idea of the present invention can also be applied to a computer-readable recording medium containing a computer program for performing the functions of the apparatus and method according to the present embodiment. In addition, the technical ideas according to various embodiments of the present invention may be implemented in the form of computer-readable codes recorded on a computer-readable recording medium. The computer-readable recording medium may be any data storage device readable by the computer and capable of storing data. For example, the computer-readable recording medium may be a ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical disk, hard disk drive, or the like. In addition, the computer-readable code or program stored in the computer-readable recording medium may be transmitted through a network connected between computers.

In addition, although preferred embodiments of the present invention have been illustrated and described above, the present invention is not limited to the specific embodiments described above, and the technical field to which the present invention belongs without departing from the gist of the present invention as claimed in the claims Various modifications are possible by those of ordinary skill in the art, and these modifications should not be individually understood from the technical spirit or prospect of the present invention.

NGSI-LD : Next Generation Service Interface - Linked Data
Entity: entity
Property : Property
Relationship: relationship
container, contentInstance, flexContainer : oneM2M resource
temporal, entities : NGSI-LD resource

Claims (8)

NGSI-LD (Next Generation Service Interface - Linked Data) generating the Entity, Property, and Relationship of NGSI-LD data according to the standard of the platform as resources, respectively; and
Storing the Entity ID of the NGSI-LD data, and generating a first resource pointing to an Entity resource indicating the Entity;
Entity resources are:
It has a Property resource indicating Property and a Relationship resource indicating Relationship as sub-resources,
Resources indicating Property and Relationship are,
A resource wrapping method, characterized in that it has resources indicating other properties and relationships as child resources.
delete delete The method according to claim 1,
Relationship resources are:
A resource wrapping method, characterized in that the first resource and the Entity ID point to a different second resource.
5. The method according to claim 4,
The first resource is
Entity ID is stored as a property,
Entity, Property, and Relationship resources are,
A resource wrapping method, characterized in that it stores property values representing Entity, Property, and Relationship.
5. The method according to claim 4,
When a query is requested, returning information on the Entity resource pointed to by the first resource, the Property resource that the Entity resource has as a child resource, and the Relationship resource in a response; Resource wrapping method further comprising a.
7. The method of claim 6,
The inquiry request is
A resource wrapping method, comprising specifying a procedure to be performed with postfix received on a virtual resource that handles a lookup request and appended to the ID of the virtual resource.
a communication unit communicating with an external device; and
Entity that creates Entity, Property, and Relationship of NGSI-LD data according to the NGSI-LD (Next Generation Service Interface - Linked Data) platform standard as resources, stores the Entity ID of NGSI-LD data, and indicates the entity A processor that generates a first resource pointing to the resource; includes;
Entity resources are:
It has a Property resource indicating Property and a Relationship resource indicating Relationship as sub-resources,
Resources indicating Property and Relationship are,
M2M platform, characterized in that it has resources indicating other properties and relationships as child resources.

Images