KR20170052477A - Method for processing data in Machine to Machine Communication system and Apparatuses thereof - Google Patents

Method for processing data in Machine to Machine Communication system and Apparatuses thereof Download PDF

Info

Publication number
KR20170052477A
KR20170052477A KR1020160142348A KR20160142348A KR20170052477A KR 20170052477 A KR20170052477 A KR 20170052477A KR 1020160142348 A KR1020160142348 A KR 1020160142348A KR 20160142348 A KR20160142348 A KR 20160142348A KR 20170052477 A KR20170052477 A KR 20170052477A
Authority
KR
South Korea
Prior art keywords
data
resource
container
creation message
container resource
Prior art date
Application number
KR1020160142348A
Other languages
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 KR20170052477A publication Critical patent/KR20170052477A/en

Links

Images

Classifications

    • 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/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/04—Error control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/38—Services specially adapted for particular environments, situations or purposes for collecting sensor information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

Embodiments of the present invention relate to a technique for processing received data by a machine to machine communication (M2M) device constituting an M2M system, and more specifically, to a method and an apparatus for receiving data having a pattern or an order in the M2M system, for confirming the validity of the data, and then, storing and processing the data. Specifically, according to one embodiment of the present invention, a method for processing data in an M2M system comprises: a step of receiving a resource generation message from another M2M device or an application entity; and a step of determining whether the resource generation message is valid by using at least one piece of attribute information on a container resource, data on the resource generation message, attribute information on the resource generation message.

Description

Field of the Invention [0001] The present invention relates to a method and apparatus for processing data in an M2M system,

The present embodiments relate to a technique for processing received data in an M2M device constituting an M2M (Machine to Machine) system. In the M2M system, a specific method of receiving data having a pattern or order and confirming its validity, And apparatus.

"Machine to Machine Communication" or MTC, "Machine Type Communication" or "Smart Device Communication" or "Machine oriented communication" or "Internet of Things" In which communication is performed without intervening in the network. Recently, oneM2M has been discussing M2M, but there are no technical elements to meet the architecture and requirements of oneM2M.

Since object communication does not normally perform communication and application control directly by a person, transmission and reception methods and procedures are required to exchange messages between objects. Further, in the case of object communication, data can be generated at a certain period or event occurrence, and the generated data can be transmitted to other M2M devices.

In particular, data reliability is important in M2M systems where human intervention is not involved. However, in order to secure data reliability, there is a disadvantage in that a time and resources for validation are frequently used. Therefore, it is necessary to develop a data processing method that can secure data reliability and enable efficient use of time and resources.

The present embodiment, which is devised from the background described above, proposes a method and apparatus for quickly determining whether or not a data error occurs by using characteristics of data received by an M2M device constituting an M2M system.

One embodiment of the present invention is a method for processing data by an M2M (Machine to Machine Communication) device, comprising: receiving a resource creation message from another M2M device or an application object; Determining whether the resource creation message is valid by using at least one of information, data of a resource creation message, and attribute information of a resource creation message.

In an exemplary embodiment of the present invention, an M2M (Machine to Machine Communication) device for processing data includes a receiving unit for receiving a resource creating message from another M2M device or an application object, attribute information of a container resource, And a property information of the resource creation message to determine whether the resource creation message is valid or not.

The present embodiment described above provides an effect of accurately determining data validity by quickly detecting data out of order or pattern using the order or pattern information of received data.

In addition, this embodiment provides the effect of saving data storage resources and saving bandwidth for data transmission while ensuring data reliability.

BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 is a diagram illustrating the M2M system from a high level functional view.
FIG. 2 is a view showing a more detailed structure of the M2M system according to one embodiment.
FIG. 3 is an exemplary diagram illustrating a procedure for transmitting a request message and receiving response information in the M2M system.
4 is a diagram for explaining the operation of the M2M device according to one embodiment.
FIG. 5 is a diagram illustrating lower resource and attribute information of a container resource according to an embodiment.
6 is a view for explaining an operation of processing a container resource creation message including data property information according to an embodiment.
FIG. 7 is a diagram illustrating an example of an operation for determining validity using attribute information of a container resource according to an exemplary embodiment. Referring to FIG.
FIG. 8 is a diagram illustrating another example of an operation of determining whether a container resource is valid by using attribute information of a container resource according to an embodiment.
9 is a view illustrating an example of an operation of determining whether a content instance resource creation message according to an embodiment is validated.
10 is a diagram illustrating another example of an operation for determining whether a content instance resource creation message according to an embodiment is validated.
11 is a diagram illustrating another example of an operation of determining whether a content instance resource creation message according to an embodiment is validated.
12 is a diagram for explaining a configuration of an M2M device according to an embodiment.

Hereinafter, some embodiments of the present invention will be described in detail with reference to exemplary drawings. It should be noted that, in adding reference numerals to the constituent elements of the drawings, the same constituent elements are denoted by the same reference numerals even though they are shown in different drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear.

In describing the components of the present invention, terms such as first, second, A, B, (a), and (b) may be used. These terms are intended to distinguish the constituent elements from other constituent elements, and the terms do not limit the nature, order or order of the constituent elements. When a component is described as being "connected", "coupled", or "connected" to another component, the component may be directly connected or connected to the other component, Quot; may be "connected," "coupled," or "connected. &Quot;

Embodiments of the present invention will be described with reference to object communication. Object communication is variously called M2M (Machine to Machine communication), MTC (Machine Type Communication), IoT (Internet of Things), Smart Device Communication (SDC), or Machine Oriented Communication . OneM2M has recently introduced many technical issues related to object communication. Object communication refers to various communication in which communication is performed without a person intervening in the communication process. In the field of telecommunication, there are various fields such as energy field, enterprise field, healthcare field, public service field, residential field, retail field, transportation field, and others Field, and so on. The present invention includes the above-mentioned fields, and is applicable to other fields.

1 is a diagram illustrating a high-level functional view of an M2M system according to an embodiment.

An application entity (AE) 110 provides application logic for an end-to-end M2M solution. For example, a fleet tracking application such as a vehicle, a remote blood sugar monitoring application, or a remote power metering and controlling application (Application Entity (AE): Application Entity provides application logic for the end-to-end M2M solutions. Examples of the Application Entities can be fleet tracking application, remote blood sugar monitoring application, or remote power metering and controlling application. The Common Services Entity (CSE) 120 is a set of service functions, and these service functions are functions commonly used in the M2M environment. This service function is exposed as a different function through reference points Mca, Mcc, and uses the base network service using the reference point Mcn. An example is data management, device management, M2M subscription management, location service, and the like. The subfunctions provided by the CSE can be logically understood as a CSF (Common Service Function). Some of the CSFs within the CSE of oneM2M node are mandatory and some may be optional. Similarly, the subfunctions in the CSF may also be mandatory or optional.

An underlying network services function (NSF) 130 provides services to the common service entity. Examples of services include device management, location services and device triggering.

Reference Points are supported in the common service entity (CSE), and the Mca reference point is a reference point that indicates the communication flow between the application entity and the common service entity. The Mcc reference point is a reference point that indicates the communication flow between two common service entities. The Mcn reference point is a reference point indicating the communication flow between the common service entity and one network service entity.

More specifically, the Mca reference point allows one application entity (AE) to use the services supported by the common service entity. The services provided through the Mca reference point are dependent on the functionality provided by the common service entity, and the application entity and the common service entity may reside in the same physical entity or in different physical entities. The Mcc reference point enables such use by a common service entity that wishes to use the services of other common service entities that provide the necessary functionality. The services provided through the Mcc reference point are dependent on the functionality provided by the common service entity. Mcc reference points can be supported between different M2M nodes. The Mcn reference point enables such use by a common service entity that wishes to use the service object of the underlying network providing the necessary functionality, which provides services other than transport and connection. The instance of the Mcn reference point is implemented dependent on the service provided in the underlying network. Information exchange between two physical M2M nodes can use the transport and connectivity services of the underlying network to provide basic services.

In this specification, a common service entity can be described as a CSE, and a network service entity can be described as an NSE. In this specification, the M2M device means CSE or AE, means a device including CSE or AE, and means an apparatus or a device constituting the M2M system.

FIG. 2 is a view showing a more detailed structure of the M2M system according to one embodiment.

Referring to FIG. 2, an infrastructure node 250 performs a server function necessary to provide M2M communication. The originating node 250 is comprised of an originating node application entity (AE) 252 and an originating node common service entity (CSE) 254. Based node common service entity 254 is configured using various resources. 252 and 254 are divided through an Mca reference point and a message for communication of objects, particularly a request message for creating, deleting, updating, retrieving, and notifying the scheduler resource And for constructing and processing response messages.

The relay node 200 relays the M2M communication or the Internet of Things communication between the application service node 220 and the base node 100. The relay node 200 includes a relay node application entity 202 and a relay node common service entity 204. The relay node common service entity 204 is configured using various resources. 202 and 204 are divided through Mca reference points and 254 and 204 are classified using Mcc reference points and messages necessary for object communication, in particular, create, delete, update, Used to construct and process request and response messages to retrieve and notify.

The application service node 210 may include an application entity 212 and a relay node common service entity 214. The application entity 212 processes the application functions required for the purpose of the device. The common service entity 214 of the application service node 210 is configured using various resources. 212 and 214 are divided through Mca reference points and 214 and 254 are classified using Mcc reference points and messages necessary for object communication, in particular, create, delete, update, Used to construct and process request and response messages to retrieve and notify. Meanwhile, the application service node 220 may perform the object communication function with the base node 100 through the relay node 200. The difference between 210 and 220 is that the communication interfaces constituting the node are different. For example, the 220 communicates with 200 through 200 using an interface capable of a near-field communication such as Bluetooth, ZigBee, Zwave, and WiFi. On the other hand, the 210 communicates with 100 using a communication interface such as 3G, LTE, Ethernet, Gigabit Ethernet, and ADSL.

The application dedicated nodes 230 and 240 do not have a common service entity but do object communication using only the application entity 242. [ 230 communicates with 100 through a communication interface such as 3G, LTE, Ethernet, Gigabit Ethernet, and ADSL, and 240 uses an interface capable of a short-range communication such as Bluetooth, ZigBee, Zwave, Lt; / RTI >

As described in FIG. 2, the M2M system may be configured as at least one of an infrastructure node, a relay node, an application service node, and an application dedicated node, and each node may be configured to include a CSE or an AE. CSE and AE can communicate with other CSEs or AEs through their respective reference points.

FIG. 3 is an exemplary diagram illustrating a procedure for transmitting a request message and receiving response information in the M2M system.

Referring to FIG. 3, the originator 300 transmits a request message to a receiver 310 (S320). The sender 300 and the recipient 310 may each be an M2M device and may be CSE or AE as described above. In addition, the sender 300 and the recipient 310 may be nodes or servers or devices, including CSE or AE.

The request message may include one or more parameters. For example, the request message may include mandatory and optional parameters. For example, the transmitting side parameter, the receiving side parameter, the request identification parameter and the operation parameter are included as essential parameters. The sender parameter includes information about the originating atom that transmits the message, and the receiver parameter includes information about the recipient receiving the message. The request identification parameter includes unique ID information for identifying the request message. In addition, the operation parameters include information for distinguishing the requested operation from the request message. The operation parameter may be set to one of Create, Retrieve, Update, Delete, and Notify. In addition, a filter parameter (FilterCriteria) may be included in order to restrict or filter the action behavior classified by the action parameter.

When the request message is received, the receiver 310 performs an operation for processing the request message (S330). For example, the receiver 310 can confirm that the sender 300 that has transmitted the request message has the authority for the request. If it is determined that the sender 300 has the authority for the request, it is checked whether the requested resource exists, and then the request message is processed. Alternatively, the receiver 310 may perform a corresponding operation according to the operation parameter of the request message. For example, when an operation parameter is set to be generated and a subscription function for instructing the sender 300 to inform the sender 300 of a change, addition, deletion, or the like of specific data is set, the receiver 310 transmits the subscription information And notifies the sender 300 of the occurrence of an event such as change, addition, deletion, etc. in the data corresponding to the subscription information.

The receiver 310 generates processing result information according to the request operation, and transmits the processing result information to the sender 300 in a response message (S340). The step S340 may be performed before the step S330. That is, when the receiver 310 receives the request message, it generates an ACK response message indicating simple reception of the ACK response message, and transmits the ACK response message to the sender 300, and may then process the request message by performing step S330.

oneM2M is a requirement that must be fulfilled to implement the system. It includes overall system requirements, management requirements, data model & semantics requirements, security requirements Requirements, Charging Requirements, and Operational Requirements.

This document focuses on M2M system technology, especially oneM2M service platform technology. However, this description is not limited to the M2M service platform technology, but is applicable to all systems and structures that provide inter-device communication, i.e., object communication, and communication operations occurring in these systems.

One of the M2M technologies described below uses <container> resources and < contentInstance > resources to store and share data that occurs between application service operations. The two resources are similar to the directories and files used in the operating system's file system. You can match the < literal > contentInstance > and <container> resources to the directory where the actual data is stored, and the hierarchically organized directory where one or more files are stored. For example, the container resource (the above-described < container > resource) includes representative information of the containing data, and the content instance resource (the &lt; contentInstance & gt; resource) includes actual data and information of each data . Accordingly, the container resource includes a plurality of attribute information and a child resource as shown in FIG. 5, and includes a content instance resource.

The present invention relates to a method for quickly determining whether a pattern or ordered IoT data is valid, and for storing and processing the same. For example, IoT devices (M2M devices) that output integrated values such as water meters, gas meters, and electric meters, and IoT devices that measure the flow rate from a large pipe to a small pipe or vice versa The IoT data collected from the devices will have a pattern or order, such as descending or ascending order, taking into account the measured time period.

Thus, by checking the validity of the pattern or sequence, the data having the pattern or the order can quickly determine whether or not the data generating IoT device is errory, and the M2M device performs the storing operation on the erroneous data I can not.

To this end, the present invention proposes a method of adding at least one of the data property information, the first container information, and the second container information to the container resource as attribute information. Hereinafter, the first container information refers to attribute information indicating a front container resource of a container storing a resource included in the resource creation message, and the second container information refers to attribute information indicating a front container resource of a container Means the attribute information indicating the container resource. That is, the first container information means frontContainer attribute information, and the second container information means rearContainer attribute information. On the other hand, the data property information means container resource sub-property information including information on a pattern or order of data included in the corresponding container resource. For example, the data property information means the orderOfInstances property information. Hereinafter, for convenience of description, the frontContainer attribute information is described as first container resource information, and the rearContainer attribute information is described as second container resource information. The orderOfInstances attribute information is described as data property information. Such description or expression is not limited thereto, and can be expressed in various descriptions including the above-mentioned meaning.

Hereinafter, a concrete method of processing data by determining the validity of the resource creation message of the present invention will be described with reference to the drawings.

4 is a diagram for explaining the operation of the M2M device according to one embodiment.

The method of processing data by a machine to machine communication (M2M) device according to an exemplary embodiment of the present invention includes receiving a resource creation message from another M2M device or an application object, and storing attribute information of a container resource, And determining whether the resource creation message is valid by using at least one of the attribute information of the resource creation message.

Referring to FIG. 4, the M2M device receives a resource creation message including data having a pattern or order from another M2M device (for example, AE or CSE) (S400). The resource creation message means a request message for generating specific data or resources, and an operation parameter of the request message is set to Create. That is, the other M2M device transmits a resource creation message to the M2M device by setting the operation parameter of the request message to create, and the M2M device receiving the resource creation message checks the other parameters of the corresponding resource creation message to perform a resource creation operation can do.

In operation S410, the M2M device may determine whether the received resource creation message is valid by using at least one of information of the received resource creation message, attribute information, and attribute information of the container resource generated in the M2M device. For example, when the M2M device receives a resource creation message requesting storage of a pattern or ordered data, it can quickly check whether the data of the resource creation message is in error. For this purpose, the M2M device can determine whether an error has occurred by using the attribute information of the resource creation message, the attribute information of the container resource, and the value of the data itself according to the resource creation message type. Specifically, in the case of the gas meter, since the meter reading is performed as the accumulated value when the data of the container resources stored in the past is 1, 10, 21, and 25, if the data stored in the resource creation message is not the integrated value , It can be determined that there is an error in the data.

FIG. 5 is a diagram illustrating lower resource and attribute information of a container resource according to an embodiment.

Referring to FIG. 5, as described above, the container resource 500 may additionally include additional attribute information to quickly determine the data error and to quickly determine the validity of the request message (resource creation message). For example, the container resource 500 may include attribute information of at least one of attribute information 510 for the first container resource, attribute information 520 for the second container resource, and data property information 530 have. Each container resource 500 may include attribute information 510, 520, and 530, and may optionally include one or more attribute information. In addition, the container resource 500 includes a content resource 540 as a lower resource, a resource 560 stored at the latest time (latest stored) in the corresponding container resource 500 and a resource 560 stored at the earliest time Stored) resources 570. [0050] The attribute information 510, 520, 530 may be included only when the container resource 500 stores data received from a specific M2M device. For example, only container resources 500 that store data received from an M2M device that generates data in a sequence or pattern may include attribute information of 510, 520, 530.

For example, orderOfInstances Attribute information 530 indicates an order for Instances . As an example, it may include information as to whether the data is composed in ascending order or descending order. frontContainer The attribute information 510 indicates a container resource immediately before the corresponding container resource 500. The rearContainer attribute information 520 indicates a container resource immediately after the corresponding container resource 500. [

Table 1 below is a table for exemplifying the characteristics of each attribute information included in the container resource 500. The descriptions in Table 1 can be more clearly understood by referring to the individual sections of the oneM2M TS-0001 document.

Attributes of
<container> Multiplicity RW /
RO /
WO Description < containerAnnc >  Attributes resourceType One RO See clause 9.6.1.3 where this common attribute is described. NA resourceID One RO See clause 9.6.1.3 where this common attribute is described. NA resourceName One RO See clause 9.6.1.3 where this common attribute is described. NA parentID One RO See clause 9.6.1.3 where this common attribute is described. NA expirationTime One RW See clause 9.6.1.3 where this common attribute is described. MA accessControlPolicyIDs 0..1  (L) RW See clause 9.6.1.3 where this common attribute is described. If no accessControlPolicyIDs  are provided at the time of creation accessControlPolicyIDs  of the parent resource is linked to this attribute MA labels 0..1  (L) RW See clause 9.6.1 where this common attribute is described. MA creationTime One RO See clause 9.6.1.3 where this common attribute is described. NA lastModifiedTime One RO See clause 9.6.1.3 where this common attribute is described. NA stateTag One RO See clause 9.6.1.3 where this common attribute is described. OA announceTo 0..1  (L) RW See clause 9.6.1.3 where this common attribute is described. NA announcedAttribute 0..1  (L) RW See clause 9.6.1.3 where this common attribute is described. NA creator 0..1 RO The AE -ID or CSE -ID of the entity which created the resource. NA maxNrOfInstances 0..1 RW Maximum number of direct child <contentInstance>  resources in the < container > resource. OA maxByteSize 0..1 RW Maximum size in bytes of data  attribute of a < contentIstance > resource) that is  allocated for the < container>  resource for all direct child < contentIsstance > in the <container>  resource. OA maxInstanceAge 0..1 RW Maximum age of a direct child <contentInstance>  resource in the <container> resource. The value is expressed in seconds. OA currentNrOfInstances One RO Current number of direct child <contentInstance > resource in the <container>  resource. It is limited by the maxByteSize . OA currentByteSize One RO Current size in bytes of data (i.e., content attribute of a < contentInstance > resource) stored in all direct child <contentInstance>  resources of the <container>  resource. This is the summation of contentSize  attribute values of the < contentInstance > resource. It is limited by the maxNrOfBytes . OA locationID 0..1 RW An ID of the resource where the attributes / policies that define how the location information is obtained and managed. This attribute is only defined when the <container>  resource is used for containing location information. OA ontologyRef 0..1 RW A reference (URI) of the ontology used to represent the information is stored in the direct child <contentInstance>  resources of the present <container>  resource (see note). OA frontContainer 0..1 RW ResourceID  or address (ex, URL) of a container which is the front of the current container orderly. OA rearContainer 0..1 RW ResourceID  or address (ex, URL) of a container. OA orderOfInstances 0..1 R0 It presents the order of contentInstances. OA

The resource creation message may be a container resource creation message for requesting creation of a container resource or a content instance resource creation message for adding data to an existing container. That is, the resource creation message may include information requesting to newly generate the container resource itself, or may include information requesting to generate a content instance in addition to the existing container resource. Hereinafter, the validity checking operation will be described by dividing the resource creation message into the container resource creation message and the content instance resource creation message. At least one of the information 510 to 570 of FIG. 5 may be used for this purpose.

First, the validity determination operation of the M2M apparatus when the resource creation message is a container resource creation message will be described with reference to FIGS. 6 to 8. FIG.

6 is a view for explaining an operation of processing a container resource creation message including data property information according to an embodiment.

Referring to FIG. 6, the M2M device may receive a container resource creation message requesting creation of a container resource as a request message from another M2M device (S600). The message reception can be received using the above-mentioned reference points. For example, when an AE sends a Request CREATE Container message to the CSE, the CSE may receive a container resource creation message. FIG. 6 shows a case where only the attribute information (ex. OrderOfInstances) attribute information is included as a parameter of the container resource creation message.

When the container resource creation message including only attribute information on the data property information is received, the M2M device generates the corresponding container resource and transmits a response message (S610). For example, when the container resource creation message includes only the data property information as attribute information, the M2M device determines that the corresponding data is valid, and creates the container resource by configuring the data property information as attribute information. In addition, the M2M device transmits a response message to the other M2M device regarding the generation result. As a result, in the case of the container resource creation message, the container resource is stored without comparing with other container resources and can be used for validity determination later. Therefore, the container resource is configured by adding the data property information to the attribute information item.

FIG. 7 is a diagram illustrating an example of an operation for determining validity using attribute information of a container resource according to an exemplary embodiment. Referring to FIG.

Referring to FIG. 7, the M2M device may receive a container resource creation message from another M2M device (S700). The container resource creation message may include first container resource information second container resource information and data property information as attribute information of the container resource.

The M2M device performs a validity determination procedure to process the container resource creation message. For example, the M2M device determines whether the data property information included in the container resource creation message, the data property information of the first container resource, and the data property information of the second container resource are identical (S710). That is, the M2M device confirms the sub-attribute information of the container resource to be generated by the container resource creation message. The M2M device confirms the first and second container resource information of the lower attribute information and identifies the data property information of the lower attribute information of the first and second container resources stored in advance by the M2M device. The M2M device determines whether the data property information of the first and second container resources is the same and the data property information of the container resource that is requested to be generated by the container resource creation message are all the same.

If it is determined that the data property information of each container resource is not all the same, the M2M device may determine that there is an error in the container resource creation message and process it as invalid (S750). If the data property information of each container resource is all the same, the type of data property information is determined (S720). For example, the data property information value may include information indicating an increase or a decrease according to the setting. The values included in the data property information can be set differently in advance according to the order or pattern of the data. For example, the data property information may be set to selectively include any one of two kinds of values of increase and decrease. Alternatively, the data characteristic information may be set to selectively include any one of the information indicating the specific pattern.

Therefore, the M2M device can determine the type of data characteristic information by checking which value the same data characteristic information indicates. The procedure for determining the validity may vary depending on the type of data property information. In this specification, the case where the data characteristic information is set to either increase or decrease will be described, but it may be divided into three or more types according to the contents set in advance as described above.

According to the value of the data property information, the M2M device extracts the first data having the fastest storage time among the data stored in the first container resource, the second data having the latest storage time and the data stored in the second container resource, 3 data and the fourth data whose storage time is latest is compared with each other to judge whether the container resource creation message is valid or not. For example, the first data may be identified as the < oldest > resource stored in the first container resource by the 570 resource in Fig. Likewise, the third data may be identified as the < oldest > resource stored in the second container resource by the 570 resource in Fig. In addition, the second data can be identified as the <latest> resource stored in the first container resource by the 560 resource in FIG. 5, and the fourth data can be confirmed by the 560 resource in FIG. 5 as the <latest> resource stored in the second container resource have. The M2M device can determine whether the M2M device is valid by comparing at least two data values among the first data to the fourth data for each embodiment.

For example, if the value of the data property information is a value indicating an increase, the M2M device compares the second data value with the third data value (S730). That is, when the data property information included in the container resource creation message is set to increase, the second data value (<latest> information of the first container resource) is the third data value (<oldest> Information), it can be determined that the resource creation message is valid. For example, if the most recently stored data value of the first container resource is 100, and the first stored value of the second container resource is 120, and the data property information is increased, the M2M device determines that the container resource creation message is valid It can be judged.

In another example, if the value of the data property information is a value indicating a decrease, the M2M device compares the second data value with the third data value (S740). That is, when the data property information included in the container resource creation message is set to decrease, the second data value (<latest> information of the first container resource) is the third data value (the <oldest> Information), it can be determined that the resource creation message is valid. For example, if the most recently stored data value of the first container resource is 120, and the first stored value of the second container resource is 100, and the data property information is decreased, the M2M device may determine that the container resource creation message is valid It can be judged.

That is, since the first container resource is data (increment or decrement) in order of the resource located in front of the second container resource, by comparing the most recent stored data of the first container resource with the first stored data of the second container resource , It is possible to judge whether there is an out-of-order data error. For example, it can be seen that the order of occurrence of the size or the same event between the contents of the corresponding contentInstance between the front Container, the rear Container, and the current Container is strictly determined. That is, you can specify the container before or after a specific container using the frontContainer and rearContainer property information. If there is no preceding or following container, the property information can be set to a null value. Also, the orderOfInstance value can be set to various values such as increase, decrease, or the like.

If it is determined that the container resource creation message is valid, the M2M device generates the corresponding container resource (S760). If an error occurs in the container resource creation message and it is determined that the container resource creation message is not valid (S750), the response message including the failure of the request message may be transmitted to another M2M device.

In the case of FIG. 7 described above, all the data stored in the first container is greater than or equal to all the data stored in the container to be created (when the data property information is incremented) (When the data characteristic information is incremented) or greater than the value of all the data stored in the container of the container. In the case of FIG. 8, the data of the specific time stored in the first container is greater than or equal to the data of the specific time stored in the container to be created (when the data property information is incremented) It can be used for judging the validity when the value of the data is greater than or equal to the data of the specific time stored in the container to be generated (when the data characteristic information is incremented). However, the present invention is not limited to this case.

FIG. 8 is a diagram illustrating another example of an operation for determining validity using attribute information of a container resource according to an embodiment

Referring to FIG. 8, the M2M device may receive a container resource creation message from another M2M device (S800). The container resource creation message may include first container resource information second container resource information and data property information as attribute information of the container resource.

The M2M device performs a validity determination procedure to process the container resource creation message. For example, the M2M device determines whether the data property information included in the container resource creation message, the data property information of the first container resource, and the data property information of the second container resource are identical (S810). That is, the M2M device confirms the sub-attribute information of the container resource to be generated by the container resource creation message. The M2M device confirms the first and second container resource information of the lower attribute information and identifies the data property information of the lower attribute information of the first and second container resources stored in advance by the M2M device. The M2M device determines whether the data property information of the first and second container resources is the same and the data property information of the container resource that is requested to be generated by the container resource creation message are all the same.

If it is determined that the data property information of each container resource is not all the same, the M2M device may determine that there is an error in the container resource creation message and process it as invalid (S850). If the data property information of each container resource is all the same, the type of the data property information is determined (S820). For example, the data property information value may include information indicating an increase or a decrease according to the setting. The values included in the data property information can be set differently in advance according to the order or pattern of the data. Therefore, the M2M device can determine the type of data characteristic information by checking which value the same data characteristic information indicates. The procedure for determining the validity may vary depending on the type of data property information.

According to the value of the data property information, the M2M device extracts the first data having the fastest storage time among the data stored in the first container resource, the second data having the latest storage time and the data stored in the second container resource, 3 data and the fourth data whose storage time is latest is compared with each other to judge whether the container resource creation message is valid or not.

For example, if the value of the data property information is a value indicating an increase, the M2M device compares the second data value with the fourth data value (S830). That is, when the data property information included in the container resource creation message is set to increase, the second data value (<latest> information of the first container resource) is the fourth data value (<latest> Information), it can be determined that the resource creation message is valid.

In another example, if the value of the data property information is a value indicating a decrease, the M2M device compares the second data value and the fourth data value (S840). That is, when the data property information included in the container resource creation message is set to decrease, the second data value (<latest> information of the first container resource) is the fourth data value (<latest> Information), it can be determined that the resource creation message is valid.

As another example, in case of increasing or decreasing the value of the data property information, the M2M device can compare the first data value and the third data value to judge whether the data property is valid or not.

That is, by comparing the data values at the same time (latest or first), it is possible to judge whether or not the data is valid. For example, the order of occurrence of events of the same size or the same between events (or between content of contentInstance) occurring at a specific point in time between front Container, rear Container, and current Container is strictly defined, but the front Container, rear Container , the order of contentInsance content in the current Container may be validated by comparing the data at a particular time, even if the order is not relevant.

If it is determined that the container resource creation message is valid, the M2M device generates the corresponding container resource (S760). If an error occurs in the container resource creation message and it is determined that the container resource creation message is not valid (S750), the response message including the failure of the request message may be transmitted to another M2M device.

The validity determination operation according to the container resource creation message has been described above. Hereinafter, the operation of the M2M device with respect to the content instance resource creation message will be described with reference to FIGS. 9 to 11. FIG.

9 is a view illustrating an example of an operation of determining whether a content instance resource creation message according to an embodiment is validated.

Referring to FIG. 9, the M2M device may receive a content instance resource creation message stored in a pre-configured container resource (S900). That is, the M2M device may receive a message requesting the creation of a content instance resource for the specific data (s) rather than the container resource itself.

The M2M device can check the container resource indicated by the received content instance resource creation message and check the attribute information of the corresponding container resource (S910). For example, the M2M device may check the information of the received content instance resource creation message and check the container resource to store the content instance resource. When the corresponding container resource is identified, the M2M device can check the validity of the attribute information of the corresponding container resource.

The M2M device confirms the data property information among the attribute information of the corresponding container resource (S920). For example, each container resource may contain information indicating the order or pattern of data as data property information.

The M2M device can determine whether the resource creation message is valid by using the data property information of the container resource in which the content instance resource is to be stored, the data of the content instance resource creation message, and the fifth data stored at the latest time in the container resource.

For example, if the data property information of the container resource indicates an increase, the M2M device may determine that the resource creation message is valid if the data value of the received content instance resource is equal to or greater than the fifth data value (S930). If the data value is smaller than the fifth data, it is determined that the resource creation message is invalid (S950). That is, since the received data has been confirmed that the order or pattern data indicates an increase in the order or pattern by the data property information, the data value currently received by the M2M device is the largest of the data values stored in the corresponding container resource The value is valid. Accordingly, since the received data continuously increases according to the time order, the validity can be quickly detected by comparing the size with the fifth data value stored at the most recent time among the data of the container resources in which the data is to be stored. In the case where such an operation is performed every time data is stored, it can be judged that all the data stored in the corresponding container resource is valid, so that it is possible to quickly determine whether or not an error has occurred with high reliability even when data is stored thereafter.

In another example, when the data property information of the container resource indicates a decrease, the M2M device may determine that the resource creation message is valid if the data value of the received content instance resource is equal to or less than the fifth data value (S940). If the data value is smaller than the fifth data, it is determined that the resource creation message is invalid (S950). That is, since the received data has been confirmed that the data having the order or pattern indicates the decrease in the order or pattern by the data property information, the data value currently received by the M2M device is the smallest among the data values stored in the corresponding container resource The value is valid. Accordingly, the received data may be continuously reduced according to the time order, and the validity of the container resource can be quickly detected by comparing the size with the fifth data value stored at the most recent time among the data of the container resources in which the data is to be stored.

If it is determined that the content instance resource creation message is valid, the M2M device may add the content instance resource as a lower resource to the corresponding container resource (S960).

10 and 11 relate to an operation of additionally utilizing first container or second container attribute information of container resources to determine validity.

10 is a diagram illustrating another example of an operation for determining whether a content instance resource creation message according to an embodiment is validated.

Referring to FIG. 10, the M2M device may receive a content instance resource creation message stored in a pre-configured container resource (S1000). That is, the M2M device may receive a message requesting the creation of a content instance resource for the specific data (s) rather than the container resource itself.

The M2M device can check the container resource indicated by the received content instance resource creation message and check the attribute information of the corresponding container resource (S1010). For example, the M2M device may check the information of the received content instance resource creation message and check the container resource to store the content instance resource. When the corresponding container resource is identified, the M2M device can check the validity of the attribute information of the corresponding container resource.

The M2M device confirms the data property information among the attribute information of the corresponding container resource (S1020). For example, each container resource may contain information indicating the order or pattern of data as data property information. Also, the M2M device can determine whether the resource creation message is valid by further using the first container resource information or the second container resource information included in the attribute information of the container resource.

For example, if the data property information is set to increase, the M2M device may determine whether the data value is equal to or greater than the fifth data value (S1030). If the data value is less than the fifth data value, the M2M device determines that the content instance resource creation message is invalid (S1080). In addition, if the data value is equal to or greater than the fifth data value, the M2M device determines whether the data value is less than the third data value stored in the second container resource at the earliest time (S1050). The M2M device may determine that the content instance resource creation message is valid when the data value is equal to or less than the third data value. Specifically, in the case of data in which the order or pattern is set to increase, the currently received data value should be equal to or greater than the most recently stored data in the container resource in which the data is to be stored. Also, in the case of a second container resource that stores data having a sequence or pattern associated with a container resource to store data, the first stored third data value of the second container resource must be equal to or greater than the received data value. And the second container resource is stored after the container resource to store the data. Accordingly, the M2M device can determine whether the content instance resource creation message is valid by additionally using the container resource to which data is to be stored as well as the data of the second container resource.

As another example, if the data property information is set to decrease, the M2M device can determine whether the data value is equal to or less than the fifth data value (S1040). If the data value exceeds the fifth data value, the M2M device determines that the content instance resource creation message is invalid (S1080). In addition, if the data value is less than or equal to the fifth data value, the M2M device determines whether the data value is equal to or less than the second data value stored at the latest (latest) time point in the first container resource (S1060). The M2M device may determine that the content instance resource creation message is valid when the data value is equal to or less than the second data value. Specifically, in the case of data in which the order or pattern is set to decrease, the currently received data value should be less than or equal to the most recently stored data in the container resource to store the data. Also, in case of a first container resource storing data having a sequence or pattern connected with a container resource for storing data, the last stored second data value of the first container resource should be equal to or greater than the received data value. This is because the first container resource is stored before the container resource to store the data, and the data order is reduced. Accordingly, the M2M device can determine whether the content instance resource creation message is valid by additionally using the container resource to which data is to be stored as well as the data of the first container resource.

If it is determined that the content instance resource creation message is valid, the M2M device may add the content instance resource as a lower resource to the corresponding container resource (S1070).

If it is determined that the content instance resource creation message is invalid, the M2M device processes the error message and transmits a response message including information on the success failure to the other M2M device (S1080).

11 is a diagram illustrating another example of an operation of determining whether a content instance resource creation message according to an embodiment is validated.

Referring to FIG. 11, the M2M device may receive a content instance resource creation message stored in a pre-configured container resource (S1100). That is, the M2M device may receive a message requesting the creation of a content instance resource for the specific data (s) rather than the container resource itself.

The M2M device can check the container resource indicated by the received content instance resource creation message and check the attribute information of the corresponding container resource (S1110). For example, the M2M device may check the information of the received content instance resource creation message and check the container resource to store the content instance resource. When the corresponding container resource is identified, the M2M device can check the validity of the attribute information of the corresponding container resource.

The M2M device confirms the data property information among the attribute information of the container resource (S1120). For example, each container resource may contain information indicating the order or pattern of data as data property information. Also, the M2M device can determine whether the resource creation message is valid by further using the first container resource information or the second container resource information included in the attribute information of the container resource.

For example, if the data property information is set to increase, the M2M device may determine whether the data value is equal to or greater than the fifth data value (S1130). If the data value is less than the fifth data value, the M2M device determines that the content instance resource creation message is invalid (S1180). In addition, if the data value is equal to or greater than the fifth data value, the M2M device determines whether the data value is equal to or less than a fourth data value stored latest at the second container resource (S1150). The M2M device may determine that the content instance resource creation message is valid when the data value is equal to or less than the fourth data value. Specifically, in the case of data in which the order or pattern is set to increase, the currently received data value should be equal to or greater than the most recently stored data in the container resource in which the data is to be stored. Also, in the case of a second container resource that stores data having a sequence or pattern associated with a container resource for storing data, the latest stored fourth data value of the second container resource must be equal to or greater than the received data value. And the second container resource is stored after the container resource to store the data. Accordingly, the M2M device can determine whether the content instance resource creation message is valid by additionally using the container resource to which data is to be stored as well as the data of the second container resource.

As another example, if the data property information is set to decrease, the M2M device can determine whether the data value is equal to or less than the fifth data value (S1140). If the data value exceeds the fifth data value, the M2M device determines that the content instance resource creation message is invalid (S1180). In addition, if the data value is less than or equal to the fifth data value, the M2M device determines whether the data value is less than the second data value stored latest in the first container resource (S1160). The M2M device may determine that the content instance resource creation message is valid when the data value is equal to or less than the second data value. Specifically, in the case of data in which the order or pattern is set to decrease, the currently received data value should be less than or equal to the most recently stored data in the container resource to store the data. Also, in case of a first container resource storing data having a sequence or pattern connected with a container resource for storing data, the last stored second data value of the first container resource should be equal to or greater than the received data value. This is because the first container resource is stored before the container resource to store the data, and the data order is reduced. Accordingly, the M2M device can determine whether the content instance resource creation message is valid by additionally using the container resource to which data is to be stored as well as the data of the first container resource.

If it is determined that the content instance resource creation message is valid, the M2M device may add the content instance resource as a lower resource to the corresponding container resource (S 1170).

If it is determined that the content instance resource creation message is invalid, the M2M device processes the error message and transmits a response message including information on the failure of success to the other M2M device (S1180).

As described above, the data property information attribute information is defined in the container resource storing the data in the M2M device so that the data having the pattern or the order can be expressed, and the data or the data defining the collected data using the data property information property information You can save them in order. In addition, it is possible to quickly determine whether the collected data is valid or not. In addition, it is possible to store and transmit only the increased or decreased value or the pattern amount based on the reference value with respect to the collected data, thereby making it possible to save the data storage resource and to reduce the bandwidth for transmission.

Hereinafter, the configuration of the M2M device capable of performing all or part of the operation of the embodiment described with reference to Figs. 1 to 11 will be described.

12 is a diagram for explaining a configuration of an M2M device according to an embodiment.

12, the M2M device 1200 includes a receiving unit 1230 for receiving a resource creating message from another M2M device or an application object, attribute information of a container resource, data of a resource creating message, And a controller 1210 for determining whether the resource creation message is valid by using at least one of the information and the information.

If the resource creation message is a container resource creation message, the control unit 1210 stores the first data having the fastest storage time among the data stored in the first container resource, the second data having the slowest storage time, It is possible to determine whether the resource creation message is valid by comparing the third data having the fastest storage time among the data and the fourth data having the slowest storage time.

If the resource creation message is a content instance resource creation message, the control unit 1210 determines whether the content resource is generated by using the fifth data stored at the latest time point in the data property information, It is possible to judge whether the generated message is valid or not.

Alternatively, if the resource creation message is a content instance resource creation message, the controller 1210 may further use the first container resource information or the second container resource information included in the attribute information of the container resource, It can be judged whether it is valid or not.

In addition, the receiver 1230 may receive data from the device generating the M2M data or other common service entity or application entity at a predetermined period or at the occurrence of a specific event. The received data may be data having a sequence or a pattern, or may be data having no sequence or pattern.

The transmitter 1220 may transmit a response message including a processing result of the resource creation message. In this case, the response message may include information indicating a generation success or a generation failure.

In addition, the control unit 1210 constructs the attribute information such as the data property information, the first container resource information, and the second container resource information on the container resource in order to determine the validity of the data having the order or pattern described above, Or the overall M2M device 1200 utilized to determine the validity of the patterned data. In addition, the transmitter 1220 and the receiver 1230 are used to exchange necessary information, signals, and messages with other M2M devices or devices.

In addition, the present embodiments can be implemented by a computer program. For example, each of the above-described steps or configurations may be implemented with respective functions using computer program code. The code and the code segment constituting the program can be easily deduced by a computer programmer in the field. In addition, the created program can be stored in a computer-readable recording medium (information storage medium), and can be read and executed by a computer to implement the present embodiment. And the recording medium includes all types of recording media readable by a computer. Therefore, a storage medium including a computer program or a computer program embodying the above-described embodiments should be construed as being included in the scope of the present embodiment.

The standard content or standard document referred to in the above embodiments (oneM2M TS-0001 document) is a part of this specification which is omitted for simplicity of description. Therefore, it is to be understood that the content of the above standard content and some of the standard documents is added to or contained in the scope of the present invention, as falling within the scope of the present invention.

The foregoing description is merely illustrative of the technical idea of the present invention, and various changes and modifications may be made by those skilled in the art without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are intended to illustrate rather than limit the scope of the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. The scope of protection of the present invention should be construed according to the following claims, and all technical ideas within the scope of equivalents should be construed as falling within the scope of the present invention.

Claims (21)

A method of processing data in a machine-to-machine communication (M2M)
Receiving a resource creation message from another M2M device or an application entity; And
Determining whether the resource creation message is valid by using at least one of attribute information of a container resource, data of the resource creation message, and attribute information of the resource creation message. The method according to claim 1,
If the resource creation message is a container resource creation message,
Wherein the container resource creation message includes at least one of first container resource information, second container resource information, and data property information as attribute information. 3. The method of claim 2,
Wherein the container generated by the container resource creation message is generated after the first container resource and before the second container resource,
Wherein the data included in the container resources includes data generated according to a time sequence. 3. The method of claim 2,
The step of determining whether the resource creation message is valid may comprise:
And determines that the resource creation message is invalid if the data property information of the first container resource, the data property information of the second container resource, and the data property information included in the container resource creation message do not match, How to. 3. The method of claim 2,
The step of determining whether the resource creation message is valid may comprise:
The first data having the fastest storage time among the data stored in the first container resource, the second data having the slowest storage time and the third data having the fastest storage time among the data stored in the second container resource, And comparing the two data values selected from the fourth data to determine whether the resource creation message is valid. 6. The method of claim 5,
When the data property information included in the container resource creation message is set to increase, if the second data value is equal to or less than the third data value,
When the data property information included in the container resource creation message is set to decrease, determining that the resource creation message is valid if the second data value is greater than or equal to the third data value. 6. The method of claim 5,
If the data property information included in the container resource creation message is set to increase, if the second data value is equal to or less than the fourth data value,
If the data property information included in the container resource creation message is set to decrease, if the second data value is greater than or equal to the fourth data value, the resource creation message is determined to be valid. The method according to claim 1,
If the resource creation message is a content instance resource creation message,
Wherein the content instance resource creation message includes data to be stored in the container resource. 9. The method of claim 8,
The step of determining whether the resource creation message is valid may comprise:
Wherein the validity of the resource creation message is determined by using data property information among the attribute information of the container resource, the data, and fifth data stored at a latest time point in the container resource. 10. The method of claim 9,
The step of determining whether the resource creation message is valid may comprise:
If the data characteristic information is set to increase, if the data value is greater than or equal to the fifth data value,
When the data property information is set to decrease, if the data value is equal to or less than the fifth data value, it is determined that the resource creation message is valid. 10. The method of claim 9,
The step of determining whether the resource creation message is valid may comprise:
And determining whether the resource creation message is valid by further using first container resource information or second container resource information included in the attribute information of the container resource. 12. The method of claim 11,
The step of determining whether the resource creation message is valid may comprise:
When the data property information is set to increase, if the data value is equal to or greater than the fifth data value and the data value is equal to or less than a third data value stored at the earliest time point in the second container resource, &Lt; / RTI &gt; 12. The method of claim 11,
The step of determining whether the resource creation message is valid may comprise:
When the data property information is set to decrease, when the data value is equal to or less than the fifth data value and the data value is equal to or less than a second data value stored at the latest time of the first container resource, &Lt; / RTI &gt; 12. The method of claim 11,
When the data property information is set to increase, if the data value is equal to or greater than the fifth data value, and the data value is equal to or less than a fourth data value stored at the latest time of the second container resource, &Lt; / RTI &gt; 12. The method of claim 11,
Wherein the container resource in which the data is stored, the first container resource, and the data property information of the second container resource are all the same. 1. A machine-to-machine communication (M2M) apparatus for processing data,
A receiving unit for receiving a resource creation message from another M2M device or an application object; And
Wherein the control unit determines whether the resource creation message is valid by using at least one of attribute information of a container resource, data of the resource creation message, and attribute information of the resource creation message. 17. The method of claim 16,
If the resource creation message is a container resource creation message,
Wherein the container resource creation message includes at least one of first container resource information, second container resource information, and data property information as attribute information. 18. The method of claim 17,
Wherein,
The first data having the fastest storage time among the data stored in the first container resource, the second data having the slowest storage time and the third data having the fastest storage time among the data stored in the second container resource, And compares two selected data values of the fourth data to determine whether the resource creation message is valid or not. 17. The method of claim 16,
If the resource creation message is a content instance resource creation message,
Wherein the content instance resource creation message includes data to be stored in the container resource. 20. The method of claim 19,
Wherein,
And determines whether the resource creation message is valid by using data property information among the attribute information of the container resource, the data, and fifth data stored at a latest time point in the container resource. 21. The method of claim 20,
Wherein,
Wherein the controller determines whether the resource creation message is valid by further using first container resource information or second container resource information included in the attribute information of the container resource.
KR1020160142348A 2015-10-30 2016-10-28 Method for processing data in Machine to Machine Communication system and Apparatuses thereof KR20170052477A (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR20150152158 2015-10-30
KR1020150152158 2015-10-30

Publications (1)

Publication Number Publication Date
KR20170052477A true KR20170052477A (en) 2017-05-12

Family

ID=58740594

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020160142348A KR20170052477A (en) 2015-10-30 2016-10-28 Method for processing data in Machine to Machine Communication system and Apparatuses thereof

Country Status (1)

Country Link
KR (1) KR20170052477A (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018236179A1 (en) * 2017-06-23 2018-12-27 주식회사 케이티 Method for processing message in m2m system and device therefor
US11533597B2 (en) 2017-06-23 2022-12-20 Samsung Electronics Co., Ltd. Method for processing message in M2M system and device therefor

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018236179A1 (en) * 2017-06-23 2018-12-27 주식회사 케이티 Method for processing message in m2m system and device therefor
US11533597B2 (en) 2017-06-23 2022-12-20 Samsung Electronics Co., Ltd. Method for processing message in M2M system and device therefor

Similar Documents

Publication Publication Date Title
US20230319534A1 (en) Cross-resource subscription for m2m service layer
US11095747B2 (en) Method and apparatus for receiving response information in M2M system
US10931509B1 (en) Assessing completion of events
KR20100125243A (en) Targeted queries using an oma dm protocol
US11671514B2 (en) Service layer message templates in a communications network
US20180018363A1 (en) Time series data processing method and apparatus
WO2019246530A1 (en) Service layer-based methods to enable efficient analytics of iot data
KR20170052477A (en) Method for processing data in Machine to Machine Communication system and Apparatuses thereof
US11533597B2 (en) Method for processing message in M2M system and device therefor
KR20170010300A (en) Methods for processing request message in M2M system and Apparatuses thereof
KR101695636B1 (en) Method and apparatus for processing composite context information event
KR101913965B1 (en) Methods for forwarding a request message in Machine to Machine communication system and Apparatuses thereof
KR20170001942A (en) Methods for processing request message in M2M system and Apparatuses thereof
KR20170036634A (en) Methods for providing subscription data in M2M system and Apparatuses thereof
US20160066121A1 (en) Methods and systems for managing charging information in a machine-to-machine (m2m) network
CN112740635B (en) Message parsing method, data sending end, data receiving end and system
KR20170053130A (en) Methods for controlling contact in Machine to Machine communication secure element and Apparatuses thereof
KR20180107752A (en) Methods for processing a request message in M2M system And Apparatuses thereof
KR20190127181A (en) Forwarding method for content sharing resource
KR20170023316A (en) A method of mash-up for IoT data from multiple devices
KR20190030077A (en) Methods for checking a valid of resource in Machine to Machine communication system and Apparatuses thereof
KR20180039552A (en) Methods for processing flexBlocking communication method in Receiver CSE and Apparatuses thereof