WO2018182065A1 - Multi-resource subscription association method in m2m system - Google Patents

Multi-resource subscription association method in m2m system Download PDF

Info

Publication number
WO2018182065A1
WO2018182065A1 PCT/KR2017/003456 KR2017003456W WO2018182065A1 WO 2018182065 A1 WO2018182065 A1 WO 2018182065A1 KR 2017003456 W KR2017003456 W KR 2017003456W WO 2018182065 A1 WO2018182065 A1 WO 2018182065A1
Authority
WO
WIPO (PCT)
Prior art keywords
subscription
resource
notification
resources
lt
Prior art date
Application number
PCT/KR2017/003456
Other languages
French (fr)
Korean (ko)
Inventor
정승명
성낙명
박종홍
이지호
Original Assignee
전자부품연구원
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 전자부품연구원 filed Critical 전자부품연구원
Priority to KR10-2017-0040420 priority Critical
Priority to KR1020170040420A priority patent/KR101845195B1/en
Publication of WO2018182065A1 publication Critical patent/WO2018182065A1/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/12Network-specific arrangements or communication protocols supporting networked applications adapted for proprietary or special purpose networking environments, e.g. medical networks, sensor networks, networks in a car or remote metering networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/26Push based network services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Abstract

A multi-resource subscription association method in an M2M system is provided. According to an embodiment of the present invention, the multi-resource subscription notification method allows a subscription association resource to receive notification messages from a plurality of subscription resources, and determine whether the notification messages satisfy a specific condition so as to transmit a notification message to a user application. Therefore, an M2M platform manages/notifies multiple subscriptions by associating the multiple data with multiple subscriptions, thereby enabling a load of a user application and an overhead in a network to be reduced.

Description

How to Associate Multiple Resource Subscriptions in an M2M System

The present invention relates to Internet of Things (IoT) / Machine to Machine (M2M) technology, and more particularly, to a subscription / notification method in an M2M platform.

The IoT / M2M service is generally implemented by a process of performing a specific operation when data acquired by acquiring various data satisfies a predetermined condition at the same time.

The service application may perform a subscription to efficiently obtain data. If the required data is a variety of data provided from various resources, multiple subscriptions must be performed.

FIG. 1 illustrates a situation in which a <window> resource, a <blind> resource, and a <thermometer> resource are subscribed to in order to obtain data of a window, a blind, and a thermometer.

When the window is "open", the user application is notified by the <sub1> resource. When the window is "open", the user application is notified by the <sub2> resource. When the temperature reaches "34 ° C", the < sub3> The resource is notified to the user application.

As a result, the user application receives a number of notifications, with the burden of analyzing the received notifications again to see if the data meets a particular condition.

For example, all notification messages must be analyzed to determine whether the window is "open", the blind is "open", and the temperature is "34 ° C". Because user applications only perform certain actions when all are met, notification and analysis become unnecessary if only one is not met.

Furthermore, this leads to the problem of sending a lot of messages unnecessarily from the network point of view.

As a solution to this problem, it is possible to use a group function defined in the oneM2M standard. This allows us to consolidate notification messages into one, but it is not an inherent solution because the integration message is simply a collection of individual notification messages.

The present invention has been made to solve the above problems, an object of the present invention is to provide a method for managing / notifying multiple subscriptions for multiple data in the M2M platform.

According to an embodiment of the present invention for achieving the above object, a multi-resource subscription notification method includes: receiving, by a subscription related resource, notification messages from a plurality of subscription resources; Determining, by the subscription related resource, whether the notification messages satisfy a specific condition; And if the specific condition is satisfied, the subscription related resource sending a notification message to the user application.

The plurality of subscription resources may be set in a first property of a subscription related resource.

In addition, the multi-resource subscription notification method according to an embodiment of the present invention, if some of the plurality of subscription resources is deleted, deleting the deleted subscription resources in the first attribute of the subscription associated resources; Can be.

The analyzing step may determine whether notification messages are received according to a specific condition.

In addition, the specific condition may be set as the second attribute of the subscription related resource.

In addition, the transmitting may generate and transmit different types of notification messages according to the third attribute of the subscription related resource.

In addition, some of the plurality of subscription resources may be included in an entity different from the hosting entity of the subscription associated resource.

On the other hand, M2M system according to another embodiment of the present invention, a communication unit for communicating with the user terminal running the user application; And if the subscription associated resource receives notification messages from multiple subscription resources, the subscription associated resource determines whether the notification messages meet a specific condition, and if the subscription related resource satisfies the specific condition, the subscription associated resource sends a notification message to the user application. A processor;

As described above, according to embodiments of the present invention, by managing and notifying multiple subscriptions to multiple data in the M2M platform, it is possible to reduce the burden on the user application and overhead on the network.

1 is a diagram illustrating a subscription / notification method for a conventional IoT / M2M service,

2 is a conceptual diagram of a method for associating and managing / notifying multiple subscriptions to multiple data in an M2M platform according to one embodiment of the present invention;

3 is a diagram provided in the description of a <subAsso> resource for multiple driving association notification;

4 conceptually illustrates a timeWindow property;

5 is a diagram illustrating a case in which <sub> resources are distributed to a plurality of CSEs;

6 is a view for explaining a method of updating a <subAsso> resource by deleting an associated individual subscription;

7 is a view illustrating an IoT / M2M system to which the present invention is applicable, and

FIG. 8 is an internal block diagram of the electronic devices shown in FIG. 7.

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

An embodiment of the present invention proposes a method of managing / notifying multiple subscriptions to multiple data in an M2M platform.

Specifically, a method is provided in which one notification is made when all resources satisfy a condition as shown in FIG. 2, not a method in which individual notifications are made when each resource satisfies an individual condition as shown in FIG. 1. present.

In other words, the former (FIG. 1) is a manner in which notification messages are individually received for individual events, and the latter (FIG. 2) is a manner in which one notification message is received for multiple events.

The user application executed in the user terminal is not concerned about whether the individual data satisfies the condition individually, but reflects the fact that all of the data is interested in whether all of the conditions are satisfied.

In order to be able to associate / manage multiple subscriptions to multiple data in the M2M platform, an embodiment of the present invention provides a <subscriptionAssociation> resource.

<subscriptionAssociation> resources are created in the M2M platform along with other resources, as shown in FIG. In FIG. 3, a <subscriptionAssociation> resource is referred to as "<subAsso>".

The <subscriptionAssociation> resource, as shown in FIG. 3, has a subIDs attribute containing IDs of <sub1> resources, <sub2> resources, and <subscription> resources for linking <sub3> resources, which are individual <subscription> resources. Include.

The timeWindow attribute of the <subscriptionAssociation> resource is a waiting time for recognizing / determining whether a notification message has been received from all of the individual <subscription> resources indicated by the subIDs attribute.

4 conceptually illustrates the timeWindow property. As shown in FIG. 4, when a time window of 10 seconds is set for three individual subscriptions, the <subscriptionAssociation> resource determines that notification messages by the three individual subscriptions are valid values within a maximum of 10 seconds. That is, if all notifications are received from all <subscription> resources within 10 seconds, the condition is treated as satisfying.

The timeWindow attribute shown in FIG. 4 is merely exemplary. The timeWindow property can be implemented in various ways depending on your needs and purposes. For example, a manner of setting an interval between notifications from <subscription> resources may be applied, and the order of the notifications may be further limited.

In some cases, you can set a timeWindow for each individual subscription. In some cases, the valid time information may be recorded on the individual notification message. In this case, it is possible to determine whether multiple data (events) are satisfied simultaneously by referring to the valid time information.

This will be described with reference to FIG. 3 again. The notiType attribute indicates the message content to be included in the association notification message sent by the <subscriptionAssociation> resource.

By the notiType attribute, the association notification message may contain only 1) a notification that all individual subscriptions have met the condition, i.e. a notification to indicate that multiple events have occurred, and 2) in addition to this notification, Notification messages may further be included.

To establish a reciprocal link between the <subscriptionAssociation> resource and the <subscription> resources, when creating a <subscriptionAssociation> resource, the <sub1> resource, <sub2> resource, and <sub3> resource have an associatedSub attribute for linking the <subscriptionAssociation> resource. Set additionally. Accordingly, the notification of the <subscription> resource may be sent to the hosting Common Service Entity (CSE) of the <subscriptionAssociation> resource.

If the <subscription> resource subscribes to multiple event information, it may have additional attributes / information that allows only a specific event to be sent to the CSE with the <subscriptionAssociation> resource.

Furthermore, as shown in FIG. 5, even when <subscription> resources are not all included in the same CSE but distributed to multiple CSEs, <subscriptionAssociation> resource generation is possible.

That is, individual <subscription> resources set in the subIDs attribute of a <subscriptionAssociation> resource are not necessarily limited to <subscription> resources included in the same CSE.

On the other hand, since the subIDs attribute of the <subscriptionAssociation> resource is target information for determining whether all events of interest are satisfied at the same time, it is necessary to dynamically manage this link.

For example, as shown in FIG. 6, if one of the associated individual subscriptions is deleted, it is possible to exclude the deleted individual <subscription> resource from the subIDs attribute of the <subscriptionAssociation> resource.

In this case, the related subscription / notification function may be provided to the remaining two subscriptions. To this end, when an individual subscription is deleted, the hosting CSE2 of the deleted individual <subscription> resource requests the deletion from the hosting CSE1 of the <subscriptionAssociation> resource by referring to the associatedSub attribute of the deleted individual <subscription> resource, and thus the <subscriptionAssociation > The subIDs attribute of the resource is updated.

The delete request is performed by CSE2 requesting a DELETE for the <deletion> virtual resource of the <subscriptionAssociation> resource. The content of the DELETE request includes the ID of the deleted <subscription> resource.

If the hosting CSE of the deleted individual <subscription> resource is the same as the hosting CSE of the <subscriptionAssociation> resource, automatic renewal by the hosting CSE is possible.

On the other hand, when one of the associated individual subscriptions are deleted as described above, there may be a case in which the associated subscription is meaningless, in which case it is necessary to process not to receive the association notification.

Therefore, when one of the associated individual subscriptions is deleted and the subIDs attribute of the <subscriptionAssociation> resource is updated, the subMembersDeletionAllowed attribute, which is an attribute indicating whether to receive the association notification, may be previously set in the <subscriptionAssociation> resource.

If subMembersDeletionAllowed is True, the association notification is made even if one of the individual subscriptions is deleted and the subIDs attribute of the <subscriptionAssociation> resource is updated. On the other hand, if subMembersDeletionAllowed is False, no association notification is made in the same case.

Furthermore, when one of the associated individual subscriptions is deleted and the subIDs attribute of the <subscriptionAssociation> resource is updated, it is necessary to notify the creator of the <subscriptionAssociation> resource. To this end, it is possible to include a creator attribute containing creator information in a <subscriptionAssociation> resource.

7 is a diagram illustrating an IoT / M2M system to which the present invention is applicable. IoT / M2M system to which the present invention is applicable, as shown in Figure 7, the server (100-1), gateways (100-21, 100-22), devices (100-31, 100-32, 100-33) Various electronic devices such as 100-34 may be connected to each other so as to communicate with each other.

The number of electronic devices shown in FIG. 7, such as the servers 100-1, gateways 100-21, 100-22, and devices 100-31, 100-32, 100-constituting the IoT / M2M system. 33, 100-34) is an example, the technical spirit of the present invention can be applied to other implementations.

Furthermore, the connection structure of the electronic devices shown in FIG. 7 may also be replaced in other ways as necessary.

All of the electronic devices shown in FIG. 7 may perform the function of the CSE as the M2M platform. That is, the server 100-1, the gateways 100-21, 100-22, and the devices 100-31, 100-32, 100-33, and 100-34 all have associated subscriptions / notifications according to embodiments of the present invention. It can provide a service.

FIG. 8 is an internal block diagram of the electronic devices shown in FIG. 7. Configurations necessary for implementing an embodiment of the present invention are the server (100-1), gateway (100-21, 100-22), device (100-31, 100-32, 100-33, 100-34) Is common. Therefore, in Fig. 6, these are referred to collectively as the reference numeral "100", hereinafter referred to collectively as electronic equipment.

As shown in FIG. 8, 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, the AE may not be included.

The processor 120 performs the necessary procedures for the associated subscription / notification service, and the storage unit 130 provides the storage space necessary for the processor 120 to perform the associated subscription / notification service.

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

On the other hand, the technical idea of the present invention can 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 idea according to various embodiments of the present disclosure may be implemented in the form of computer readable codes recorded on a computer readable recording medium. The computer-readable recording medium can be any data storage device that can be read by a computer and can store data. For example, the computer-readable recording medium may be a ROM, a RAM, a CD-ROM, a magnetic tape, a floppy disk, an optical disk, a 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 the computers.

In addition, although the preferred embodiment of the present invention has been shown and described above, the present invention is not limited to the specific embodiments described above, but the technical field to which the invention belongs without departing from the spirit of the invention claimed in the claims. Of course, various modifications can be made by those skilled in the art, and these modifications should not be individually understood from the technical spirit or the prospect of the present invention.

Claims (8)

  1. The subscription associated resource receiving notification messages from a plurality of subscription resources;
    Determining, by the subscription related resource, whether the notification messages satisfy a specific condition;
    If the specific condition is met, the subscription related resource sending a notification message to the user application.
  2. The method according to claim 1,
    Many subscription resources,
    The multi-resource subscription notification method, which is set in the first property of the subscription related resource.
  3. The method according to claim 2,
    If some of the plurality of subscription resources is deleted, deleting the deleted subscription resource in the first attribute of the subscription associated resource; further comprising the multi-resource subscription notification method.
  4. The method according to claim 1,
    The analysis phase,
    Determining whether notification messages are received according to specific conditions.
  5. The method according to claim 4,
    Certain conditions,
    The multi-resource subscription notification method, which is set as a second attribute of a subscription related resource.
  6. The method according to claim 1,
    The transmission step is
    And generating and transmitting a different type of notification message according to the third attribute of the subscription related resource.
  7. The method according to claim 1,
    Some of the many subscription resources,
    The multi-resource subscription notification method, which is included in a different entity from the hosting entity of the subscription-related resource.
  8. A communication unit communicating with a user terminal on which a user application is executed;
    When the subscription associated resource receives notification messages from multiple subscription resources, the subscription associated resource determines whether the notification messages meet a specific condition, and if the subscription related resource satisfies the specific condition, the subscription associated resource handles sending a notification message to the user application. M2M system comprising a; processor.
PCT/KR2017/003456 2017-03-30 2017-03-30 Multi-resource subscription association method in m2m system WO2018182065A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
KR10-2017-0040420 2017-03-30
KR1020170040420A KR101845195B1 (en) 2017-03-30 2017-03-30 Multiple Resource Subscriptions Association Method in an M2M system

Publications (1)

Publication Number Publication Date
WO2018182065A1 true WO2018182065A1 (en) 2018-10-04

Family

ID=61977561

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2017/003456 WO2018182065A1 (en) 2017-03-30 2017-03-30 Multi-resource subscription association method in m2m system

Country Status (2)

Country Link
KR (1) KR101845195B1 (en)
WO (1) WO2018182065A1 (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110268047A1 (en) * 2010-05-03 2011-11-03 Mformation Technologies Inc. Providing Dynamic Group Subscriptions For M2M Device Communication
US20130066965A1 (en) * 2011-09-12 2013-03-14 Telefonaktiebolaget L M Ericsson (Publ) Systems and methods for optimization of subscriptions to resource changes in machine-to-machine (m2m) systems
KR20160008526A (en) * 2013-05-16 2016-01-22 엘지전자 주식회사 Method for subscription and notification in m2m communication system and apparatus for same
US20160219125A1 (en) * 2013-12-05 2016-07-28 Huawei Technologies Co., Ltd. Method and apparatus for implementing subscription notification
US20170006455A1 (en) * 2013-11-29 2017-01-05 Kt Corporation Method and device for searching for available device in m2m environment

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110268047A1 (en) * 2010-05-03 2011-11-03 Mformation Technologies Inc. Providing Dynamic Group Subscriptions For M2M Device Communication
US20130066965A1 (en) * 2011-09-12 2013-03-14 Telefonaktiebolaget L M Ericsson (Publ) Systems and methods for optimization of subscriptions to resource changes in machine-to-machine (m2m) systems
KR20160008526A (en) * 2013-05-16 2016-01-22 엘지전자 주식회사 Method for subscription and notification in m2m communication system and apparatus for same
US20170006455A1 (en) * 2013-11-29 2017-01-05 Kt Corporation Method and device for searching for available device in m2m environment
US20160219125A1 (en) * 2013-12-05 2016-07-28 Huawei Technologies Co., Ltd. Method and apparatus for implementing subscription notification

Also Published As

Publication number Publication date
KR101845195B1 (en) 2018-04-05

Similar Documents

Publication Publication Date Title
JP6275837B2 (en) Method and apparatus for performing subscription notification
US9215551B2 (en) Resource management in machine to machine networks
US9207988B2 (en) Method, system, and device for managing server hardware resources in a cloud scheduling environment
EP1047240B1 (en) Method and apparatus for object rendering in a network
EP3273653A1 (en) Slice management system and slice management method
CA1312144C (en) Session control in network for digital data processing system which supports multiple transfer protocols
US7287076B2 (en) Performing threshold based connection status responses
US7315903B1 (en) Self-configuring server and server network
US5546539A (en) Method and system for updating files of a plurality of storage devices through propogation of files over a nework
US6999997B2 (en) Method and apparatus for communication of message data using shared queues
US5227778A (en) Service name to network address translation in communications network
US5864680A (en) Method and system for distributing data in a real time data imaging network
US20110276982A1 (en) Load Balancer and Load Balancing System
JP3382953B2 (en) Client management flow control method and apparatus on finite memory computer system
JP4738144B2 (en) Information monitoring method, system and program
JP4009591B2 (en) Domain naming system (DNS) for accessing databases
US20080181255A1 (en) System for an open architecture development platform with centralized synchronization
US5588119A (en) Method for correlating logical device names with a hub port in a local area network
US20060036707A1 (en) Method and apparatus for routing images
US20050172080A1 (en) Cache device, cache data management method, and computer program
CN102281190B (en) Networking method for load balancing apparatus, server and client access method
WO2013170410A1 (en) Group communication method and system, group server and group member device
KR100690290B1 (en) Keeping persistency while switching between modalities
WO2013042985A2 (en) Method for operating interactive messaging service providing reception confirmation
US20100241722A1 (en) Method and system for transporting telemetry data across a network

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17903517

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase in:

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17903517

Country of ref document: EP

Kind code of ref document: A1