WO2018101548A1 - Data update notification method - Google Patents

Data update notification method Download PDF

Info

Publication number
WO2018101548A1
WO2018101548A1 PCT/KR2017/003181 KR2017003181W WO2018101548A1 WO 2018101548 A1 WO2018101548 A1 WO 2018101548A1 KR 2017003181 W KR2017003181 W KR 2017003181W WO 2018101548 A1 WO2018101548 A1 WO 2018101548A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
resource
contentinstance
subscription
value
Prior art date
Application number
PCT/KR2017/003181
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 전자부품연구원
Publication of WO2018101548A1 publication Critical patent/WO2018101548A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 

Definitions

  • the present invention relates to a subscription / notification method, and more particularly, to a method for performing data-related notification in a subscription / notification mechanism.
  • oneM2M typically uses the ⁇ container> and ⁇ contentInstance> resources to share data between devices / applications.
  • a container is a repository that stores contentInstance, and the actual data is stored in contentInstance.
  • the container provides the ability to store existing data and store new data additionally without changing the old data when adding new data.
  • new contentInstance is created instead of modifying existing contentInstance of container.
  • the contentInstance has creationTime and stateTag attributes to determine the order of data generation.
  • a container is a subscription target but a contentInstance is not.
  • repository attribute information such as the number of current contentInstances may change, but contentInstance continuously stores new contentInstances in the repository without updating data contents.
  • an event type applicable to a ⁇ contentInstance> resource is limited to an event type of "C" and "D” in FIG. It simply creates or deletes the ⁇ contentInstance> resource. In other words, it can be seen that new data has been generated, but it is impossible to compare whether the new data is the same or different from the existing data.
  • the present invention has been made to solve the above problems, and an object of the present invention is to provide a method for notifying Data Update of ContentInstance.
  • the notification method for achieving the above object, the platform monitors the data change of the new ContentInstance from the existing ContentInstance, and notifies the data update when the change is detected.
  • an application is normally overloaded without being notified of a new data generation and a notification operation only when new data having a different value from the existing data is generated. Can be minimized.
  • 1 is an event type in a subscription mechanism of oneM2M
  • FIG. 4 is a diagram illustrating a data change event
  • FIG. 5 is a diagram illustrating an M2M / IoT system to which the present invention is applicable.
  • FIG. 6 is an internal block diagram of the electronic devices illustrated in FIG. 5.
  • the subscription / notification mechanism is a technique to set up a subscription in advance in order to be notified when a specific event occurs.
  • the event may include generation of new information, deletion of existing information, or update of existing information.
  • FIG. 2 shows an example in which a user creates a subscription in a storage of temperature data in the oneM2M platform, and informs an application that created a subscription when there is a change in temperature information while periodically storing current temperature information in a refrigerator.
  • ⁇ container> / ⁇ contenInstance> parent / child resources Applicable to ⁇ container> / ⁇ contenInstance> parent / child resources, ⁇ timeSeries> / ⁇ timeSeriesInstance> parent / child resources, and ⁇ flexContainer> / ⁇ flexContainer> parent / child resources.
  • the application can set the eventNotification attribute of the ⁇ subscription> resource with the same condition as instanceDataChange and, if set, the platform performs a comparison operation on the value of a specific attribute of the newly created child resource of the subscribed-to resource with the same attribute value of the conventional resource. can do.
  • the conventional resource may refer to the last generated resource among the conventionally generated resources.
  • FIG. 3 is a table showing eventNotificationCriteria conditions.
  • the property that performs the comparison operation is the content property that stores the actual data.
  • a comparison operation can be performed by monitoring the creation of a new ⁇ contentInstance> resource having the same value as the corresponding setting value.
  • the platform may interpret the contentInfo value set in the newly created ⁇ contentInstance> resource and perform a comparison operation based on the extracted data. Otherwise, the comparison operation can be performed as it is with the content attribute value with the format and encoding such as JSON and base64.
  • ⁇ timeSeriesInstance> If a subscription is created for a ⁇ timeSeries> resource, the above method can be applied to a ⁇ timeSeriesInstance> resource that is a child resource. However, since ⁇ timeSeriesInstance> does not have contentInfo as an attribute, the contentInfo and contentInfoCheck are not applied.
  • a containerDefinition can be set together to specify the ⁇ flexContainer> child resource type.
  • ⁇ flexContainer> can have this value to monitor and compare operation of ⁇ flexContainer> resource of specific type because platform / service provider extends and defines basic resource type and stores information of this extension type as containerDefinition. have. If this value is set, you can monitor and compare certain attribute values for new ⁇ flexContainer> child resources of the same type as the value.
  • the platform confirming the change of the new data value by the subscription setting may transmit it to the notification.
  • the information of the notification message may include, for example, at least one of indication information indicating that a change in a data value has occurred, a new data value, and an existing data value.
  • the application logic can be monitored on the platform and data change can be determined as shown in FIG. 4, the application receives a notification when generating new data and compares it with previously received data. And the overload can be minimized by being notified only when new data having a value different from the existing data is generated without performing a comparison operation.
  • the M2M / IoT system to which the present invention is applicable may include a server 100-1, a gateway 100-21, 100-22, and a device 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. 5, such as the server 100-1, the gateways 100-21, 100-22, and the devices 100-31, 100-32, and 100-constituting the M2M / IoT system. 33, 100-34) is an example, the technical spirit of the present invention can be applied to other implementations.
  • connection structure of the electronic devices shown in FIG. 5 may also be replaced in other ways as necessary.
  • All electronic devices shown in FIG. 5 may perform the function of group hosting CSE of the oneM2M 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 are all hosting CSEs, and as shown in FIG. Update notifications can be made.
  • FIG. 6 is an internal block diagram of the electronic devices illustrated in FIG. 5. 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.
  • electronic devices 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.
  • AE application entity
  • CSE common service entity
  • the processor 120 performs the above-described data update notification, and the storage unit 130 provides the storage space necessary for the processor 120 to perform the data update notification.
  • 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 service correspond to the function block 140.
  • 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.
  • 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.
  • 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.
  • the computer-readable code or program stored in the computer-readable recording medium may be transmitted through a network connected between the computers.

Abstract

Provided is a content instance data update notification method. In the notification method according to one embodiment of the present invention, a platform monitors changes in data of the ContentInstance in the case in which new data continues to be stored on the platform as another ContentInstance, and, when a change is sensed, the data update is notified. As such, an overload can be minimized as a notification is received only when new data having a value that differs from existing data is created.

Description

데이터 업데이트 통지 방법How to Notify Data Updates
본 발명은 subscription/notification 방법에 관한 것으로, 더욱 상세하게는 subscription/notification 메커니즘에서 데이터 관련 통지를 수행하는 방법에 관한 것이다.The present invention relates to a subscription / notification method, and more particularly, to a method for performing data-related notification in a subscription / notification mechanism.
oneM2M은 디바이스/어플리케이션 간 데이터를 공유하기 위해 일반적으로 <container> 및 <contentInstance> 자원을 사용한다.oneM2M typically uses the <container> and <contentInstance> resources to share data between devices / applications.
container는 contentInstance를 저장하는 저장소이며, 실제 데이터는 contentInstance에 저장한다. 또한 container는 신규 데이터를 추가할 때 과거 데이터를 변경하기 않고 기존 데이터는 보관하고 신규 데이터를 추가로 저장하는 기능을 제공한다.A container is a repository that stores contentInstance, and the actual data is stored in contentInstance. In addition, the container provides the ability to store existing data and store new data additionally without changing the old data when adding new data.
따라서 신규 데이터가 생성되면 container의 기존 contentInstance를 수정하는 것이 아니라 새로운 contentInstance를 생성한다. contentInstance에는 creationTime 및 stateTag 속성이 있어서 데이터 생성 순서를 판단할 수 있다.Therefore, when new data is created, new contentInstance is created instead of modifying existing contentInstance of container. The contentInstance has creationTime and stateTag attributes to determine the order of data generation.
위와 같은 특성에 기인하여 container는 subscription 대상이나 contentInstance는 그렇지 않다. container의 경우 현재 contentInstance의 개수 등의 저장소 속성 정보가 변경될 수 있으나 contentInstance는 데이터 내용을 갱신하지 않고 새로운 contentInstance를 계속 저장소에 추가 저장하기 때문이다.Due to the above characteristics, a container is a subscription target but a contentInstance is not. In the case of a container, repository attribute information such as the number of current contentInstances may change, but contentInstance continuously stores new contentInstances in the repository without updating data contents.
현재 oneM2M의 subscription 메커니즘으로 <container> 자원에 subscription을 생성(설정)하는 경우, <contentInstance> 자원에 적용할 수 있는 이벤트 타입은 도 1에서 "C"와 "D"의 이벤트 타입으로 한정되며 이는 곧 <contentInstance> 자원의 생성 또는 삭제뿐이다. 다시 말해 신규 데이터가 생성되었다는 것은 알 수 있으나 이 신규 데이터가 기존 데이터와 비교하여 같은 값인지 다른 값인지 등의 비교는 불가능하다.When creating a subscription to a <container> resource using the subscription mechanism of oneM2M, an event type applicable to a <contentInstance> resource is limited to an event type of "C" and "D" in FIG. It simply creates or deletes the <contentInstance> resource. In other words, it can be seen that new data has been generated, but it is impossible to compare whether the new data is the same or different from the existing data.
상기 이벤트 타입을 보면 모두 1개 자원에 대한 모니터링을 수행하도록 정의되어 있다. subscription 대상 자원 갱신 또는 이 자원의 자녀 자원의 생성/삭제만 모니터링할 수 있으며 기존 자원과 신규 생성되는 자원 간의 비교를 통한 모니터링은 oneM2M 플랫폼에서 제공하지 않는다.Looking at the event type, all are defined to perform monitoring for one resource. Only the update of subscription target resource or creation / deletion of child resource of this resource can be monitored, and monitoring through comparison between existing resource and newly created resource is not provided by oneM2M platform.
본 발명은 상기와 같은 문제점을 해결하기 위하여 안출된 것으로서, 본 발명의 목적은, ContentInstance의 Data Update를 Notification 하는 방법을 제공함에 있다.The present invention has been made to solve the above problems, and an object of the present invention is to provide a method for notifying Data Update of ContentInstance.
상기 목적을 달성하기 위한 본 발명의 일 실시예에 따른, 통지 방법은, 플랫폼이 기존 ContentInstance로부터 신규 ContentInstance의 데이터 변경을 모니터링하고, 변경 감지시 데이터 업데이트를 통지한다.The notification method according to an embodiment of the present invention for achieving the above object, the platform monitors the data change of the new ContentInstance from the existing ContentInstance, and notifies the data update when the change is detected.
이상 설명한 바와 같이, 본 발명의 실시예들에 따르면, 평소에는 어플리케이션이 신규 데이터 생성에 대한 notification 및 비교 연산을 수행하지 않고, 기존 데이터와 다른 값의 신규 데이터가 생성된 경우만 통지 받음으로써 오버로드를 최소화할 수 있다.As described above, according to embodiments of the present invention, an application is normally overloaded without being notified of a new data generation and a notification operation only when new data having a different value from the existing data is generated. Can be minimized.
또한 subscription 생성 시 여러 어플리케이션을 notification 수신자로 할 수 있으므로 수신자가 많아질수록 전체 시스템 상 불필요한 메시지 전송으로 인한 네트워크 사용량을 줄이고 상기 어플리케이션들의 오버로드를 notification을 수신하는 어플리케이션 수만큼 더 줄일 수 있는 장점이 있다.In addition, since multiple applications can be used as notification recipients when creating a subscription, the number of recipients increases the network usage due to unnecessary message transmission on the whole system, and the overload of the applications can be further reduced by the number of applications receiving notifications. .
도 1은 oneM2M의 subscription 메커니즘에서의 이벤트 타입,1 is an event type in a subscription mechanism of oneM2M,
도 2는 냉장고 온도 정보의 subscription/notification 예제,2 is a subscription / notification example of refrigerator temperature information;
도 3은 eventNotificationCriteria conditions을 나타낸 표,3 is a table showing eventNotificationCriteria conditions,
도 4는 데이터 변경 이벤트를 나타낸 도면,4 is a diagram illustrating a data change event;
도 5는 본 발명이 적용 가능한 M2M/IoT 시스템을 도시한 도면, 그리고,5 is a diagram illustrating an M2M / IoT system to which the present invention is applicable; and
도 6은, 도 5에 도시된 전자 기기들의 내부 블럭도이다.FIG. 6 is an internal block diagram of the electronic devices illustrated in FIG. 5.
이하에서는 도면을 참조하여 본 발명을 보다 상세하게 설명한다.Hereinafter, with reference to the drawings will be described the present invention in more detail.
subscription/notification 메커니즘은 특정한 이벤트가 발생할 경우 이를 notification(통지) 받기 위해 사전에 subscription(구독)을 설정하는 기법이다.The subscription / notification mechanism is a technique to set up a subscription in advance in order to be notified when a specific event occurs.
본 발명의 실시예에서, 이벤트는 새로운 정보의 생성, 기존 정보의 삭제 또는 기존 정보의 갱신 등을 포함할 수 있다. 도 2는 사용자가 oneM2M 플랫폼에 온도 데이터의 저장소에 subscription을 생성하고, 냉장고에서 주기적으로 현재 온도 정보를 저장하는 상황에서 온도 정보에 변화가 있을 경우 이를 subscription을 생성했던 어플리케이션으로 알려주는 예제를 나타낸다.In an embodiment of the present invention, the event may include generation of new information, deletion of existing information, or update of existing information. FIG. 2 shows an example in which a user creates a subscription in a storage of temperature data in the oneM2M platform, and informs an application that created a subscription when there is a change in temperature information while periodically storing current temperature information in a refrigerator.
<subscription> 자원의 eventNotificationCriteria 속성의 eventType 값이 C. Creation of direct child of the subscribed-to resource인 경우에 사용할 수 있다.Can be used when the eventType value of the eventNotificationCriteria attribute of the <subscription> resource is C. Creation of direct child of the subscribed-to resource.
<container>/<contenInstance> 부모/자녀 자원, <timeSeries>/<timeSeriesInstance> 부모/자녀 자원 그리고 <flexContainer>/<flexContainer> 부모/자녀 자원에 적용할 수 있다. 이는 어플리케이션이 <subscription> 자원의 eventNotification 속성에 instanceDataChange와 같은 조건으로 설정할 수 있고 설정된 경우 플랫폼은 subscribed-to 자원의 신규 생성된 자녀 자원의 특정 속성 값과 종래 자원의 동일 속성값에 대한 비교 연산을 수행할 수 있다. 여기서 종래 자원은 종래 생성된 자원 중 마지막에 생성된 자원을 가리킬 수 있다.Applicable to <container> / <contenInstance> parent / child resources, <timeSeries> / <timeSeriesInstance> parent / child resources, and <flexContainer> / <flexContainer> parent / child resources. This means that the application can set the eventNotification attribute of the <subscription> resource with the same condition as instanceDataChange and, if set, the platform performs a comparison operation on the value of a specific attribute of the newly created child resource of the subscribed-to resource with the same attribute value of the conventional resource. can do. Here, the conventional resource may refer to the last generated resource among the conventionally generated resources.
저장소, 예를 들면, container, timeSeries, flexContainer(부모)에 따라 도 3에 제시된 표와 같은 방법을 적용할 수 있다. 도 3은 eventNotificationCriteria conditions을 나타낸 표이다.Depending on the storage, for example container, timeSeries, flexContainer (parent), the same method as the table shown in FIG. 3 can be applied. 3 is a table showing eventNotificationCriteria conditions.
<container> 자원에 subscription을 생성(설정)한 경우, 자녀 자원 중 <contentInstance> 자원에 대해 모니터링을 수행할 수 있다. 이 때 비교 연산을 하는 속성은 실제 데이터를 저장하는 content 속성이다.When a subscription is created (set) in a <container> resource, monitoring can be performed for the <contentInstance> resource among the child resources. In this case, the property that performs the comparison operation is the content property that stores the actual data.
추가적으로 contentInfo 값이 함께 설정되어 있는 경우 해당 설정값과 동일한 값을 가지는 신규 <contentInstance> 자원 생성에 대해 모니터하여 비교 연산을 수행할 수 있다.In addition, when the contentInfo value is set together, a comparison operation can be performed by monitoring the creation of a new <contentInstance> resource having the same value as the corresponding setting value.
추가적으로 contentInfoCheck 값이 함께 설정되어 있는 경우 플랫폼이 신규 생성된 <contentInstance> 자원에 설정된 contentInfo 값으로 이를 해석하여 추출된 데이터를 기반으로 비교 연산을 수행할 수 있다. 그렇지 않은 경우 JSON, base64와 같은 포맷 및 인코딩이 적용된 content 속성값 그대로 비교 연산을 수행할 수 있다.In addition, when the contentInfoCheck value is set together, the platform may interpret the contentInfo value set in the newly created <contentInstance> resource and perform a comparison operation based on the extracted data. Otherwise, the comparison operation can be performed as it is with the content attribute value with the format and encoding such as JSON and base64.
<timeSeries> 자원에 subscription을 생성한 경우 자녀 자원인 <timeSeriesInstance> 자원에 대해 상기 방법을 적용할 수 있다. 다만 <timeSeriesInstance>는 contentInfo를 속성으로 가지지 않으므로 상기 contentInfo 및 contentInfoCheck는 적용되지 않는다.If a subscription is created for a <timeSeries> resource, the above method can be applied to a <timeSeriesInstance> resource that is a child resource. However, since <timeSeriesInstance> does not have contentInfo as an attribute, the contentInfo and contentInfoCheck are not applied.
<flexContainer> 부모 자원에 subscription을 생성한 경우, <flexContainer> 자녀 자원 타입을 특정하기 위해 containerDefinition을 함께 설정할 수 있다. <flexContainer>는 플랫폼/서비스 제공자가 기본 자원 타입을 확장 정의하여 사용하고 이 확장 타입의 정보를 containerDefinition으로 저장하므로 특정 타입의 <flexContainer> 자원에 대해 모니터링 및 비교 연산을 수행하기 위해 이 값을 가질 수 있다. 이 값이 설정된 경우 해당 값과 동일한 타입의 신규 <flexContainer> 자녀 자원에 대해서 특정 속성 값들에 대한 모니터링 및 비교 연산을 수행할 수 있다.When a subscription is created to a <flexContainer> parent resource, a containerDefinition can be set together to specify the <flexContainer> child resource type. <flexContainer> can have this value to monitor and compare operation of <flexContainer> resource of specific type because platform / service provider extends and defines basic resource type and stores information of this extension type as containerDefinition. have. If this value is set, you can monitor and compare certain attribute values for new <flexContainer> child resources of the same type as the value.
상기 subscription 설정에 의해 신규 데이터 값의 변화를 확인한 플랫폼은 이를 notification으로 전송할 수 있다. 이 때 notification 메시지의 정보는 예를 들어, 데이터 값의 변화가 생겼다는 지시 정보, 신규 데이터 값 및 기존 데이터 값 중 적어도 하나를 포함할 수 있다.The platform confirming the change of the new data value by the subscription setting may transmit it to the notification. In this case, the information of the notification message may include, for example, at least one of indication information indicating that a change in a data value has occurred, a new data value, and an existing data value.
어플리케이션 로직을 플랫폼에서 모니터링하여 데이터 변경을 도 4와 같이 판단할 수 있다면 어플리케이션은 신규 데이터 생성 시 notification을 수신하여 이전에 수신한 데이터와 비교하는 동작을 스스로 하는 대신, 평소에는 신규 데이터 생성에 대한 notification 및 비교 연산을 수행하지 않고, 기존 데이터와 다른 값의 신규 데이터가 생성된 경우만 통지 받음으로써 오버로드를 최소화할 수 있다.If the application logic can be monitored on the platform and data change can be determined as shown in FIG. 4, the application receives a notification when generating new data and compares it with previously received data. And the overload can be minimized by being notified only when new data having a value different from the existing data is generated without performing a comparison operation.
또한 subscription 생성 시 여러 어플리케이션을 notification 수신자로 할 수 있으므로 수신자가 많아질수록 전체 시스템 상 불필요한 메시지 전송으로 인한 네트워크 사용량을 줄이고 상기 어플리케이션들의 오버로드를 notification을 수신하는 어플리케이션 수만큼 더 줄일 수 있는 장점이 있다.In addition, since multiple applications can be used as notification recipients when creating a subscription, the number of recipients increases the network usage due to unnecessary message transmission on the whole system, and the overload of the applications can be further reduced by the number of applications receiving notifications. .
도 5는 본 발명이 적용 가능한 M2M/IoT 시스템을 도시한 도면이다. 본 발명이 적용 가능한 M2M/IoT 시스템은, 도 5에 도시된 바와 같이, 서버(100-1), 게이트웨이(100-21, 100-22), 디바이스(100-31, 100-32, 100-33, 100-34)와 같은 다양한 전자 기기들이 상호 통신가능하도록 연결되어 구축된다.5 is a diagram illustrating an M2M / IoT system to which the present invention is applicable. As shown in FIG. 5, the M2M / IoT system to which the present invention is applicable may include a server 100-1, a gateway 100-21, 100-22, and a device 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.
도 5에 도시된 전자 기기들의 개수, 이를 테면, M2M/IoT 시스템을 구성하는 서버(100-1), 게이트웨이(100-21, 100-22) 및 디바이스(100-31, 100-32, 100-33, 100-34)의 대수는 예시적인 것이므로, 이와 다르게 구현하는 경우도 본 발명의 기술적 사상이 적용될 수 있다.The number of electronic devices shown in FIG. 5, such as the server 100-1, the gateways 100-21, 100-22, and the devices 100-31, 100-32, and 100-constituting the M2M / IoT system. 33, 100-34) is an example, the technical spirit of the present invention can be applied to other implementations.
나아가, 도 5에 도시된 전자 기기들의 연결 구조 역시, 필요에 따라 다른 방식으로 대체될 수 있음은 물론이다.Furthermore, the connection structure of the electronic devices shown in FIG. 5 may also be replaced in other ways as necessary.
도 5에 도시된 모든 전자 기기들은, oneM2M 플랫폼의 그룹 호스팅 CSE의 기능을 수행할 수 있다. 즉, 서버(100-1), 게이트웨이(100-21, 100-22), 디바이스(100-31, 100-32, 100-33, 100-34) 모두 호스팅 CSE로써, 도 2에 제시된 바에 따라 데이터 업데이트 통지를 할 수 있는 것이다.All electronic devices shown in FIG. 5 may perform the function of group hosting CSE of the oneM2M 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 are all hosting CSEs, and as shown in FIG. Update notifications can be made.
도 6은, 도 5에 도시된 전자 기기들의 내부 블럭도이다. 본 발명의 실시예를 구현함에 있어 필요한 구성들은 서버(100-1), 게이트웨이(100-21, 100-22), 디바이스(100-31, 100-32, 100-33, 100-34) 모두가 공통된다. 따라서, 도 6에서는 이들을 참조 부호 "100"으로 통칭하여 도시하였으며, 이하에서 전자 기기로 통칭한다.FIG. 6 is an internal block diagram of the electronic devices illustrated in FIG. 5. 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.
도 6에 도시된 바와 같이, 본 발명의 다른 실시예에 따른 전자 기기들은, 통신부(110), 프로세서(120), 저장부(130) 및 기능 블록(140)을 포함한다.As shown in FIG. 6, 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.
통신부(110)는 외부 기기와 통신하고 외부 네트워크에 액세스하기 위한 통신 인터페이스 수단이다.The communication unit 110 is a communication interface means for communicating with an external device and accessing an external network.
프로세서(120)는 적어도 하나의 AE(Application Entitr)와 CSE(Common Service Entity)를 포함한다. 전자 기기의 종류와 기능에 따라서는, AE가 포함되지 않을 수도 있다.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.
프로세서(120)의 위에서 제시한 데이터 업데이트 통지를 수행하며, 저장부(130)는 프로세서(120)가 데이터 업데이트 통지를 수행함에 있어 필요한 저장 공간을 제공한다.The processor 120 performs the above-described data update notification, and the storage unit 130 provides the storage space necessary for the processor 120 to perform the data update notification.
기능 블록(140)은 전자 기기 본연의 기능을 수행한다. 이를 테면, 전자 기기가 서버(100-1)인 경우, 서비스를 제공하는 가상 머신들이 기능 블록(140)에 해당한다.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 service correspond to the function block 140.
한편, 본 실시예에 따른 장치와 방법의 기능을 수행하게 하는 컴퓨터 프로그램을 수록한 컴퓨터로 읽을 수 있는 기록매체에도 본 발명의 기술적 사상이 적용될 수 있음은 물론이다. 또한, 본 발명의 다양한 실시예에 따른 기술적 사상은 컴퓨터로 읽을 수 있는 기록매체에 기록된 컴퓨터로 읽을 수 있는 코드 형태로 구현될 수도 있다. 컴퓨터로 읽을 수 있는 기록매체는 컴퓨터에 의해 읽을 수 있고 데이터를 저장할 수 있는 어떤 데이터 저장 장치이더라도 가능하다. 예를 들어, 컴퓨터로 읽을 수 있는 기록매체는 ROM, RAM, CD-ROM, 자기 테이프, 플로피 디스크, 광디스크, 하드 디스크 드라이브, 등이 될 수 있음은 물론이다. 또한, 컴퓨터로 읽을 수 있는 기록매체에 저장된 컴퓨터로 읽을 수 있는 코드 또는 프로그램은 컴퓨터간에 연결된 네트워크를 통해 전송될 수도 있다.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 (1)

  1. 기존 ContentInstance로부터 신규 ContentInstance의 데이터 변경을 모니터링하는 단계;Monitoring data changes of the new ContentInstance from the existing ContentInstance;
    변경 감지시 데이터 업데이트를 통지하는 단계;를 포함하는 통지 방법.Notifying a data update upon change detection.
PCT/KR2017/003181 2016-11-29 2017-03-24 Data update notification method WO2018101548A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR10-2016-0160346 2016-11-29
KR1020160160346A KR102165192B1 (en) 2016-11-29 2016-11-29 Data Update Notification Method

Publications (1)

Publication Number Publication Date
WO2018101548A1 true WO2018101548A1 (en) 2018-06-07

Family

ID=62242820

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2017/003181 WO2018101548A1 (en) 2016-11-29 2017-03-24 Data update notification method

Country Status (2)

Country Link
KR (1) KR102165192B1 (en)
WO (1) WO2018101548A1 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102460910B1 (en) * 2020-11-20 2022-10-31 한국전자기술연구원 Data storage method for preventing data duplication and data platform applying the same

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20140109747A (en) * 2013-03-06 2014-09-16 주식회사 케이티 A method and apparatus of assuring data transmission in M2M multi-hop environments
KR20150067037A (en) * 2013-12-06 2015-06-17 주식회사 케이티 The methods and apparatuses of optimization for criteria of subscription in M2M Systems
WO2016068442A1 (en) * 2014-10-27 2016-05-06 엘지전자 주식회사 Method for guaranteeing operation of control message in wireless communication system and device for same
WO2016126021A1 (en) * 2015-02-06 2016-08-11 엘지전자 주식회사 Method and apparatus for processing request for stopping notification receipt in wireless communication system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20140109747A (en) * 2013-03-06 2014-09-16 주식회사 케이티 A method and apparatus of assuring data transmission in M2M multi-hop environments
KR20150067037A (en) * 2013-12-06 2015-06-17 주식회사 케이티 The methods and apparatuses of optimization for criteria of subscription in M2M Systems
WO2016068442A1 (en) * 2014-10-27 2016-05-06 엘지전자 주식회사 Method for guaranteeing operation of control message in wireless communication system and device for same
WO2016126021A1 (en) * 2015-02-06 2016-08-11 엘지전자 주식회사 Method and apparatus for processing request for stopping notification receipt in wireless communication system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SONG, JAE-SEUNG ET AL.: "oneM2M Application Developer Standard Guideline", TELECOMMUNICATIONS TECHNOLOGY ASSOCIATION (TTA), TTA-1 5099-SD, 30 November 2015 (2015-11-30), pages 56 - 57, 63-66 *

Also Published As

Publication number Publication date
KR20180060629A (en) 2018-06-07
KR102165192B1 (en) 2020-10-13

Similar Documents

Publication Publication Date Title
US10638362B2 (en) Method and system for group communication, group server, and group member device
US10050899B2 (en) Data processing method, apparatus, client, server and system
CN104484259A (en) Application program traffic monitoring method and device, and mobile terminal
KR20140136894A (en) Method and apparatus for detecting malware and medium record of
EP2838228A1 (en) Alarm correlation analysis method, apparatus, and system
US10893423B2 (en) Load migration method, apparatus, and system
CN106656989B (en) Flow monitoring method and terminal
EP3576370A1 (en) Traffic flow control method and device
CN112995239B (en) Data processing method and device
WO2013147421A1 (en) Server and method for managing access of terminal to connection blocked resource and terminal
CN110740144B (en) Method, device, equipment and storage medium for determining attack target
CN115002238A (en) Traffic transmission method, device, equipment and storage medium
WO2018101548A1 (en) Data update notification method
WO2018182065A1 (en) Multi-resource subscription association method in m2m system
CN108600769A (en) Image transfer method, apparatus and system
US11196892B2 (en) Use of client compute for document processing
KR102275065B1 (en) Apparatus and method for security control
WO2020085528A1 (en) Subscription expiration management method and m2m system employing same
WO2015088244A1 (en) Method for providing file aging service
WO2019022584A1 (en) Cross-resource subscription management method
CN110971697B (en) Redis single instance protection processing method and device, computer equipment and storage medium
CN107678928B (en) Application program processing method and server
KR101842830B1 (en) Request Reachability Management Method on M2M platform
JP2010211494A (en) Information processing system, message management method, and message management program
JP6380774B1 (en) Computer system, server device, program, and failure detection method

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: 17876835

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17876835

Country of ref document: EP

Kind code of ref document: A1