Method and apparatus for synchronizing downloaded resources in an m2m system

Abstract

The present disclosure relates to resource synchronization in a machine-to-machine (M2M) system and a method of operating an M2M device, the method can include the steps of creating a first resource, receiving a first message for requesting to update the first resource, and transmitting a second message for requesting to update a second resource to another device hosting the second resource synchronized with the first resource. The first resource can include at least one attribute for downloading a resource.

Description

Technical Field

[0001] This disclosure relates to methods and apparatus for synchronizing resources in a machine-to-machine (M2M) system. More specifically, this disclosure relates to methods and apparatus for synchronizing resources downloaded in an M2M system. Background Technology

[0002] Recently, the introduction of machine-to-machine (M2M) systems has become active. M2M communication can refer to communication performed between machines without human intervention. M2M can refer to machine-type communication (MTC), the Internet of Things (IoT), or device-to-device (D2D). In the following description, for ease of explanation, the term "M2M" is used consistently, but this disclosure is not limited thereto. The terminal used for M2M communication can be an M2M terminal or an M2M device. An M2M terminal is typically a device with low mobility when sending small amounts of data. Here, the M2M terminal can be used in conjunction with an M2M server that centrally stores and manages inter-machine communication information. Furthermore, M2M terminals can be applied to various systems, such as object tracking, vehicle linking, and power measurement.

[0003] Meanwhile, for M2M terminals, the M2M standardization organization sets requirements for M2M communication, thing-to-thing communication and IoT technologies, as well as technologies used for architecture, application programming interface (API) specifications, security solutions and interoperability. The M2M standardization organization's specifications provide a framework to support various applications and services, such as smart cities, smart grids, connected cars, home automation, security and health. Summary of the Invention

[0004] Technical issues

[0005] This disclosure relates to a method and apparatus for synchronizing resources in a machine-to-machine (M2M) system.

[0006] This disclosure relates to a method and apparatus for synchronizing resources downloaded in an M2M system with the original resources.

[0007] Technical solution

[0008] According to embodiments of this disclosure, a method for operating an M2M device in a machine-to-machine (M2M) system may include: generating a first resource; receiving a first message requesting an update to the first resource; and sending a second message requesting an update to the second resource to another device hosting a second resource synchronized with the first resource. The first resource may include at least one attribute for downloading the resource.

[0009] According to one embodiment of this disclosure, an M2M device in a machine-to-machine (M2M) system includes a transceiver for transmitting and receiving signals, and a processor for controlling the transceiver, wherein the processor generates a first resource, receives a first message requesting an update to the first resource, and can be controlled to send a second message requesting an update to a second resource to another device hosting a second resource synchronized with the first resource. The first resource may include at least one attribute for downloading the resource.

[0010] Invention Effects

[0011] According to this disclosure, relevant resources in a machine-to-machine (M2M) system can be effectively synchronized.

[0012] Those skilled in the art will understand that the effects achievable through this disclosure are not limited to those specifically described above, and other advantages of this disclosure will become clearer from the detailed description. Attached Figure Description

[0013] Figure 1 The hierarchical structure of a machine-to-machine (M2M) system according to this disclosure is shown.

[0014] Figure 2 A reference point in the M2M system according to this disclosure is shown.

[0015] Figure 3 The various nodes in the M2M system according to this disclosure are shown.

[0016] Figure 4 The public service functions in an M2M system according to this disclosure are shown.

[0017] Figure 5 A method for initiating and receiving parties to exchange messages in an M2M system according to this disclosure is shown.

[0018] Figure 6a and Figure 6b Examples of two types of synchronization performed between the original resource and the advertised resource in an M2M system according to this disclosure are shown.

[0019] Figure 7 An example of the operation process of an apparatus for performing resource synchronization in an M2M system according to the present disclosure is shown.

[0020] Figure 8 Another example of the operation of an apparatus for performing resource synchronization in an M2M system according to the present disclosure is shown.

[0021] Figure 9 An example of signal exchange for resource synchronization based on updates to downloaded resources in an M2M system, according to this disclosure, is shown.

[0022] Figure 10 An example of signal exchange for resource synchronization based on updates to the original resource in an M2M system, according to this disclosure, is shown.

[0023] Figure 11 Another example of signal exchange for resource synchronization based on updates to downloaded resources in an M2M system, according to this disclosure, is shown.

[0024] Figure 12 Another example of signal exchange for resource synchronization based on updates to the original resource in an M2M system, according to this disclosure, is shown.

[0025] Figure 13 The configuration of an M2M device in an M2M system according to the present disclosure is shown. Detailed Implementation

[0026] In the following, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings, which will be readily implemented by those skilled in the art. However, the present disclosure may be embodied in many different forms and is not limited to the exemplary embodiments described herein.

[0027] In this disclosure, unless otherwise specifically stated, the terms first, second, etc., are used only for the purpose of distinguishing one component from another and do not limit the order or importance of the components. Therefore, within the scope of this disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component.

[0028] In this disclosure, when a component is referred to as “linked,” “coupled,” or “connected” to another component, it should be understood that this may include not only direct connections but also indirect connections via intermediate components. Furthermore, when a component is referred to as “comprising” or “having” another component, unless explicitly stated otherwise, it may indicate further inclusion of the other component rather than exclusion of that component.

[0029] In this disclosure, components are distinguished from each other to clearly illustrate each feature. However, this does not necessarily mean that the components are separate. In other words, multiple components may be integrated into a single hardware or software unit, or a single component may be distributed across multiple hardware or software units. Therefore, unless otherwise indicated, such integrated or distributed embodiments are also included within the scope of this disclosure.

[0030] In this disclosure, the components described in the various embodiments are not necessarily essential, and some may be optional. Therefore, embodiments comprising a subset of the components described in one embodiment are also included within the scope of this disclosure. Furthermore, exemplary embodiments including components other than those described in the various exemplary embodiments are also included within the scope of this disclosure.

[0031] In the following description of embodiments of this disclosure, detailed descriptions of known functions and configurations included herein will be omitted where such omissions may make the subject matter of this disclosure considerably unclear. Parts in the drawings that are not relevant to the description of this disclosure have been omitted, and similar parts are indicated by similar reference numerals.

[0032] Although the exemplary embodiments are described as using multiple units to perform exemplary processes, it should be understood that the exemplary processes can also be performed by one or more modules. Furthermore, it should be understood that the term controller / control unit refers to a hardware device that includes a memory and a processor and is specifically programmed to perform the processes described herein. The memory is configured to store modules, and the processor is specifically configured to execute said modules to perform one or more processes further described below.

[0033] Furthermore, this specification describes a network based on machine-to-machine (M2M) communication, and describes how to perform work in the M2M communication network during network control and data transmission in a system that manages the communication network.

[0034] Furthermore, in this specification, an M2M terminal can be a terminal that performs M2M communication. However, for backward compatibility, it can be a terminal operating in a wireless communication system. In other words, an M2M terminal can refer to a terminal operating based on an M2M communication network, but is not limited thereto. An M2M terminal can operate based on another wireless communication network and is not limited to the exemplary embodiments described above.

[0035] Furthermore, M2M terminals can be fixed or mobile. An M2M server refers to a server used for M2M communication and can be a fixed station or a mobile station.

[0036] Furthermore, in this specification, an entity may refer to hardware such as an M2M device, an M2M gateway, and an M2M server. Additionally, for example, an entity may be used to refer to software configurations within the hierarchical structure of an M2M system, and is not limited to the embodiments described above.

[0037] Furthermore, for example, this disclosure primarily describes M2M systems, and is not limited to M2M systems.

[0038] Furthermore, the M2M server can be a server that communicates with the M2M terminal or another M2M server. Additionally, the M2M gateway can be a connection point between the M2M terminal and the M2M server. For example, when the M2M terminal and the M2M server are on different networks, they can connect to each other through the M2M gateway. Here, for example, both the M2M gateway and the M2M server can be M2M terminals, and are not limited to the embodiments described above.

[0039] This disclosure relates to methods and apparatus for processing personal data in machine-to-machine (M2M) systems. More specifically, this disclosure describes techniques for confirming consent to the processing of personal data in M2M systems.

[0040] Furthermore, M2M is a de facto standards organization created to develop a public IoT service platform that shares and integrates application service infrastructure (platform) environments, transcending the segmented service platform development structures confined to independent industries such as energy, transportation, defense, and public services. M2M aims to provide requirements for things-to-thing communication and IoT technologies, architectures, application programming interface (API) specifications, security solutions, and interoperability. For example, M2M specifications provide a framework supporting various applications and services such as smart cities, smart grids, connected cars, home automation, security, and health. To this end, M2M has developed a set of standards that define a single horizontal platform for data exchange and sharing between all applications. M2M can also consider applications across different industrial sectors. Like an operating system, M2M provides a framework for connecting different technologies, thereby creating a distributed software layer that facilitates unification. This distributed software layer is implemented in a common service layer between the M2M application and the communication hardware / software (HW / SW) that presents data transmission. For example, the common service layer could be... Figure 1 Part of the layered structure shown in the image.

[0041] Figure 1 This is a diagram illustrating the hierarchical structure of a machine-to-machine (M2M) system according to the present disclosure.

[0042] refer to Figure 1 The layered structure of an M2M system may include an application layer 110, a public service layer 120, and a network service layer 130. Here, the application layer 110 can be a layer that operates based on a specific application. For example, the application could be a fleet tracking application, a remote blood glucose monitoring application, a power metering application, or a control application. In other words, the application layer can be a layer used for a specific application. Here, the entity operating based on the application layer can be an application entity (AE).

[0043] Public Service Layer 120 can be a layer for Public Service Functions (CSF). For example, Public Service Layer 120 can be a layer for providing public services such as data management, device management, M2M service subscription management, and location services. For example, an entity operating based on Public Service Layer 120 can be a Public Service Entity (CSE).

[0044] The Public Service Layer 120 can provide a set of services grouped into CSFs based on functionality. Multiple instantiated CSFs constitute a CSE. A CSE can interface with applications (e.g., application entities or AEs in the M2M terminology), other CSEs, and the underlying network (e.g., network service entities or NSEs in the M2M terminology). The Network Service Layer 130 can provide services such as device management, location services, and device triggering to the Public Service Layer 120. Here, the entity operating based on the Network Service Layer 130 can be a Network Service Entity (NSE).

[0045] Figure 2 This is a diagram illustrating a reference point in an M2M system according to this disclosure. (Reference) Figure 2 An M2M system architecture can be divided into a field domain and an infrastructure domain. Within each domain, each entity can communicate through a reference point (e.g., Mca or Mcc). For example, the reference point can indicate the communication flow between each entity. Specifically, the reference... Figure 2 It allows setting the reference point Mca between AE 210 or 240 and CSE 220 or 250, the reference point Mcc between different CSEs, and the reference point Mcn between CSE 220 and NSE 230 or CSE 250 and NSE 260.

[0046] Figure 3 This is a diagram illustrating the various nodes in the M2M system according to this disclosure.

[0047] refer to Figure 3 A specific infrastructure node (IN) 310 can be provided within the infrastructure domain of a particular M2M service provider. In this document, the CSE of the IN is configured to communicate based on the AE and reference points Mca of other infrastructure nodes. Specifically, one IN can be set up for each M2M service provider. In other words, an IN can be a node that performs communication with an M2M terminal of another infrastructure based on the infrastructure structure. Furthermore, conceptually, a node can be a logical entity or a software configuration.

[0048] Next, the Application Dedicated Node (ADN) 320 can be a node that includes at least one AE but not a CSE. Specifically, the ADN can be set up in the field. In other words, the ADN can be a dedicated node for the AE. For example, the ADN can be a node hardware-configured in an M2M terminal. Additionally, the Application Service Node (ASN) 330 can be a node that includes one CSE and at least one AE. The ASN can be set up in the field. In other words, it can be a node that includes both AEs and CSEs. Specifically, the ASN can be a node connected to the IN. For example, the ASN can be a node hardware-configured in an M2M terminal.

[0049] Furthermore, the intermediate node (MN) 340 can be a node that includes a CSE and zero or more AEs. Specifically, the MN can be positioned within the field. The MN can be connected to another MN or IN based on a reference point. Additionally, for example, the MN can be hardware-configured within an M2M gateway.

[0050] Furthermore, for example, a non-M2M terminal node 350 (NoDN) is a node that does not include an M2M entity. It can be a node that performs management or collaboration with an M2M system.

[0051] Figure 4 This is a diagram illustrating the public service functions in an M2M system according to this disclosure.

[0052] Reference Figure 4 It can provide public service functions. For example, the public service entity can provide at least one or more CSFs in application and service layer management 402, communication management and delivery processing 404, data management and storage 406, device management 408, discovery 410, group management 412, location 414, network service exposure / service execution and triggering 416, registration 418, security 420, service charging and billing 422, service session management and subscription / notification 424. In this case, the M2M terminal can operate based on the public service functions. Furthermore, in other embodiments, public service functions are feasible and are not limited to the exemplary embodiments described above.

[0053] Application and Service Layer Management (402CSF) provides management for Application Effects (AEs) and Service Effects (CSEs). 402CSF includes not only the configuration, troubleshooting, and upgrades of CSE functionality, but also the upgrade capabilities for AEs.

[0054] The Communications Management and Delivery Processing (CMS) 404CSF provides communication with other CSEs, AEs, and NSEs. The CMS 404CSF is configured to determine when and through which connections to deliver communications, and, if necessary and permissible, to buffer communication requests for later delivery.

[0055] Data management and storage 406CSF provides data storage and transport capabilities (e.g., data collection for aggregation and data reformatting, and data storage for analysis and semantic processing).

[0056] The Device Management 408CSF provides management of device capabilities in M2M gateways and M2M devices.

[0057] It was discovered that 410CSF is configured to provide information retrieval capabilities for applications and services based on filtering criteria.

[0058] Group Management 412CSF provides processing for group-related requests. Group Management 412CSF enables M2M systems to support batch operations for many devices and applications.

[0059] Location 414CSF is configured to enable the AE to obtain geographic location information.

[0060] Network service exposure / service execution and triggering 416CSF manages communication with the underlying network to access network service functions.

[0061] Registration 418CSF is configured to provide AEs (or other remote CSEs) to CSEs. Registration 418CSF allows AEs (or remote CSEs) to use the services of CSEs.

[0062] Security 420CSF is configured to provide security features to the service layer, such as access control including identification, authentication, and authorization.

[0063] Service charging and billing 422CSF is configured to provide charging functionality for the service layer.

[0064] The Subscribe / Notify 424CSF is configured to allow subscription to events and notification of their occurrence.

[0065] Figure 5 This is a diagram illustrating the exchange of messages between an initiator and a receiver in an M2M system according to this disclosure.

[0066] refer to Figure 5 The initiator 510 can be configured to send a request message to the receiver 520. Specifically, the initiator 510 and the receiver 520 can be the M2M terminals described above. However, the initiator 510 and the receiver 520 are not limited to M2M terminals, but can be other terminals. They are not limited to the exemplary embodiments described above. Furthermore, for example, the initiator 510 and the receiver 520 can be the nodes, entities, servers, or gateways described above. In other words, the initiator 510 and the receiver 520 can be hardware or software configurations, and are not limited to the embodiments described above.

[0067] Here, for example, a request message sent by initiator 510 may include at least one parameter. Furthermore, parameters may be mandatory or optional. For example, parameters related to the sending terminal, parameters related to the receiving terminal, identification parameters, and operational parameters may be mandatory parameters. Additionally, optional parameters may be related to other types of information. Specifically, parameters related to the sending terminal may be parameters for initiator 510. Furthermore, parameters related to the receiving terminal may be parameters for receiver 520. Identification parameters may be parameters required for mutual identification.

[0068] Furthermore, operation parameters can be parameters used to distinguish operations. For example, operation parameters can be set to any of the following: create, retrieve, update, delete, and notify. In other words, parameters can be designed to differentiate operations.

[0069] In response to receiving a request message from initiator 510, receiver 520 may be configured to process the message. For example, receiver 520 may be configured to perform an operation included in the request message. For the operation, receiver 520 may be configured to determine whether the parameters are valid and authorized. Specifically, in response to determining that the parameters are valid and authorized, receiver 520 may be configured to check whether the requested resource exists and perform processing accordingly.

[0070] For example, in the event of an event, the initiator 510 can be configured to send a request message including parameters for notification to the receiver 520. The receiver 520 can be configured to examine the parameters of the notification included in the request message and can perform an operation accordingly. The receiver 520 can also be configured to send a response message to the initiator 510.

[0071] like Figure 5 As shown, the message exchange process using request and response messages can be performed between the AE and CSE based on reference point Mca, or between CSEs based on reference point Mcc. In other words, the initiator 510 can be either the AE or the CSE, and the receiver 520 can be either the AE or the CSE. Depending on the operation in the request message, such as... Figure 5 The message exchange process shown can be initiated by AE or CSE.

[0072] A request from the requester to the receiver via reference points Mca and Mcc may include at least one mandatory parameter and at least one optional parameter. In other words, each defined parameter may be mandatory or optional, depending on the requested operation. For example, a response message may include at least one of the parameters listed in Table 1 below.

[0073] Table 1

[0074]

[0075]

[0076] The filtering criteria that can be used in request or response messages are defined in Tables 2 and 3 below.

[0077] Table 2

[0078]

[0079]

[0080]

[0081]

[0082] Table 3

[0083]

[0084]

[0085] Responses to requests to access resources via reference points Mca and Mcc may include at least mandatory parameters and at least optional parameters. In other words, each defined parameter may be mandatory or optional, depending on the requested action or the mandatory response code. For example, a request message may include at least one of the parameters listed in Table 4 below.

[0086] Table 4

[0087]

[0088]

[0089] Normal resources comprise a complete set of data that forms the basis of the information to be managed. Unless they qualify as “virtual” or “announced,” the resource types in this document are normal resources. Virtual resources are used to trigger processing and / or retrieval of results. However, virtual resources do not have a permanent representation in CSE.

[0090] The advertised resource contains a set of attributes of the original resource. When the original resource changes, the advertised resource is automatically updated by the CSE that hosts the original resource. The advertised resource includes the link to the original resource.

[0091] Resource announcements enable resource discovery. A resource announced on a remote CSE can be used to create a child resource on the remote CSE that is not a child of the original resource or is not a child of the resource that was announced.

[0092] To support resource announcements, additional columns in the resource template can specify attributes to be announced for inclusion in the associated announced resource type. For each announced resource... <resourcetype>Towards the original <resourcetype>Adding the suffix 'Annc' can be used to indicate the type of resource that is associated with the announcement. For example, a resource... <containerannc>Can indicate for use <container>The type of resource that was announced, and <groupannc>Can indicate for use <group>The type of resource that was announced.

[0093] There may be situations where IoT servers need to delegate tasks or resources to edge / fuzzy nodes. For example, when a terminal IoT device requires real-time support from its server, or when edge / fuzzy nodes and the central IoT server need to be synchronized, it may be necessary to delegate tasks or resources to the edge / fuzzy nodes. This operation may be applied in vehicle-to-everything (V2X) environments, industrial IoT environments, and smart factory environments.

[0094] Resource announcements facilitate resource downloads for edge / fuzzy computing. Whenever a downloaded resource changes within a downloaded edge / fuzzy node, the original resource in the announced edge / fuzzy node can be automatically updated. The original resource is indicated as the download resource, and the downloaded resource includes a link to the original resource.

[0095] In other words, resource announcements can facilitate resource downloads for edge / fuzzy computing. When an announced resource (e.g., a resource deployed on an edge / fuzzy node) is updated by an entity other than the original resource's hosting CES (e.g., another AE / CSE with permissions to update the announced resource), the hosting CES of the announced resource sends an update request to the original resource's hosting CES to update the original resource. If feasible, the original resource's hosting CES also reflects requests for updates to other announced resources. The following... Figure 6a and Figure 6b Two types of resource synchronization are shown.

[0096] Figure 6a and Figure 6b Examples of two types of synchronization performed between the originating resource and the advertised resource in an M2M system according to this disclosure are shown. Figure 6a As shown, when at least one of the advertised resources 620a, 620b, or 620c exists, an update to the original resource 610 can be reflected in all advertised resources 620a, 620b, and 620c. Furthermore, as... Figure 6b As shown, when resource 620c, which is advertised by an entity other than the host CES of the original resource, is updated, the update to the advertised resource 620c can be reflected in the original resource 610, and, if feasible, in other advertised resources 610a and 610b.

[0097] Updates used for announcements and downloads can be different. A resource can be created for an original resource with only one download. If a downloaded resource already exists, any modifications to the original resource (e.g., creation, updates, deletions) made during the resource download will be reflected in all announced and downloaded resources.

[0098] As described above, when resources are downloaded, data mismatches can occur between the original resource and the downloaded resource. Therefore, this disclosure proposes various embodiments for resource synchronization.

[0099] According to an embodiment, at least one attribute for synchronization can be defined. For example, the at least one attribute may include at least one of an attribute of download location and an attribute of the type associated with the notification. Specifically, the at least one attribute may include the following: <offloadto> 、 <announcetype>and <announcesynctype>At least one of them.

[0100] When a CREATE or UPDATE request includes the address where the resource was downloaded or the CSE-ID, <offloadto>Attributes can be included in CREATE or UPDATE requests. When a CSE-ID is provided, the downloaded CSE can determine the location of the downloaded resource. For the original resource, if the original resource was successfully advertised to the downloaded CSE, it may exist within the original resource. <offloadto>property. <offloadto>The attribute maintains the resource address of successfully downloaded resources. <offloadto>Updating attributes will trigger a new resource download or terminate the download.

[0101] <announcetype>This attribute indicates the type of resource announcement. Possible values ​​are "Announcement" or "Download". The value "Announcement" indicates the original announcement type. The value "Download" indicates the announcement type used for resource download. <announcetype>The value of the attribute is "download", including the location of the downloaded resource.

[0102] Should <announcetype>This attribute indicates the type of synchronization used for resource advertising. Possible values ​​are "One-way synchronization" and "Two-way synchronization". The "One-way synchronization" value indicates that at least one advertised resource is updated when the original resource is updated. The "Two-way synchronization" value indicates that at least one advertised resource is updated when the original resource is updated, and at least the original resource is updated when an advertised resource is updated. Either the original resource or the advertised resource can be updated. <announcesynctype>Attribute. Does not exist. <announcesynctype>The attribute means that one-way synchronization is the synchronization type supported by the advertised resource.

[0103] Figure 7 An example of the operation process of an apparatus for requesting resource synchronization in an M2M system according to the present disclosure is shown. Figure 7 The operation method of an apparatus (e.g., an apparatus including CES) capable of generating and updating resources is illustrated. (See reference...) Figure 7 In the description, the operating entity is referred to as a "device".

[0104] refer to Figure 7 In step S701, the device creates synchronization-related resources. Here, synchronization-related resources refer to the original resource of the downloaded resource, the downloaded resource itself, and the announced resource. When the synchronization-related resource is the original resource, since the download is performed after the original resource is created, although not in... Figure 7 As shown, after step S701, the device can perform operations to download the original resource to another device. When the resource related to synchronization is a downloaded resource, although not in... Figure 7 As shown, prior to step S701, the device can receive information about the original resource from another device. Here, the created resource may include at least one attribute related to downloading (e.g., <offloadto> 、 <announcetype> 、 <announcesynctype>).

[0105] In step S703, the device updates the resource in response to an update request. In other words, the device updates at least one value of an attribute included in the created resource. In this case, the device may update the resource in response to an update request from another device. Here, the other device may be a device including an Application Executor (AE) executing the application associated with the resource, or a device including a Service Executor (CES) hosting the original resource, or a downloaded resource associated with the resource. That is, the update request may be an update request from the AE to a general resource, or an update request for synchronization.

[0106] In step S705, the device identifies resources synchronized with the updated resource. For example, if the resource created in step S701 is an original resource, the device identifies whether a downloaded or advertised resource exists. As another example, when the resource created in step S701 is a downloaded resource, the device identifies the original resource. Here, the resources considered as synchronized resources may be defined differently depending on the specific embodiment. In this case, other resources synchronized based on the update of the resource created in step S701 may be predefined or set by attributes. In this case, the device may identify another synchronized resource based on at least one attribute included in the resource.

[0107] In step S707, the device sends an update request message to another device hosting the identified resource. In this case, the update request message may include at least one of information indicating an update for synchronization based on the resource's update request and information about the device (e.g., AE910) requesting the update of the downloaded resource. Thus, the other device can update the hosted resource according to the synchronization process.

[0108] Reference Figure 7 In the described implementation, the device identifies another resource to be synchronized and requests an update for that resource from another device that has identified the resource in the hosting facility. In this case, there may be no other resources to be synchronized. For example, if the synchronization process is defined such that synchronization is performed in the chain, and the resource updated in step S703 is the resource corresponding to the end of the chain, then there may be no additional resources to be synchronized. If there are no other resources to be synchronized, this can be omitted. Figure 7 Step S707.

[0109] According to an embodiment, update priorities between related resources can be defined through notification or download. In other words, the update order of resources with a synchronization relationship can be defined. In this case, even if an update to any one resource is requested, the resource cannot be updated unless the resource with a higher priority is updated first. To this end, the device can determine whether the update request is through a synchronous update request or through a general update request of the application, and in the case of a general update request, perform the operation of updating the resource with the higher priority first. For example, a priority rule can be defined that downloaded resources should be updated before the original resource, or conversely, a priority rule can be defined that the original resource should be updated before downloaded resources. Referring to the following... Figure 8 An example is described where there is a priority for updating.

[0110] Figure 8 Another example of the operation of an apparatus for performing resource synchronization in an M2M system according to the present disclosure is shown. Figure 8 The operation method of a device (e.g., a device including CES) capable of creating and updating resources is illustrated. (See reference...) Figure 8 In the description, the operating entity is referred to as a "device".

[0111] refer to Figure 8 In step S801, the device creates synchronization-related resources. Here, synchronization-related resources refer to the original resource of the downloaded resource, the downloaded resource, and the advertised resource. If the synchronization-related resource is the original resource, then since the download is performed after the creation of the original resource, even if not in... Figure 8 As shown, after step S801, the device can perform operations for downloading the original resource to another device. When the resource related to synchronization is a downloaded resource, although it is not in... Figure 8 As shown, prior to step S801, the device can receive information about the original resource from another device hosting the original resource. Here, the created resource may include at least one attribute related to downloading (e.g., <offloadto> 、 <announcetype> 、 <announcesynctype>).

[0112] In step S803, the device receives an update request message. In other words, an update request for the resource created in step S801 occurs. The update request message includes a new value for at least one attribute included in the resource. Here, the update request message is a message requesting a general update from the AE, not an update for synchronization.

[0113] In step S805, the device determines whether there are related resources with an update priority. Update priorities are predefined, and therefore, the device can determine whether there are related resources with a higher update priority based on the resources created therefrom. For example, a downloaded resource may have a higher priority than the original resource.

[0114] If a related resource with update priority exists, in step S807, the device sends an update request message to another device hosting that related resource. That is, the device sends an update request message to the other device. Therefore, after the related resource hosted in the other device is updated first, the resources stored in the device can be updated through a synchronization process.

[0115] On the other hand, if no related resource with update priority exists, the device updates the resource and performs a synchronization process in step S809. That is, because no related resource with higher priority exists, the device can update the resource based on the update request message received in step S803 without waiting for updates to other related resources. Furthermore, after updating the resource, the device performs an operation to update another resource with a synchronization relationship (e.g., sending an update request).

[0116] According to an embodiment, updates to the original resource can be forwarded to downloaded resources. Only downloaded resources are updated where any modifications are made. After a successful update on a downloaded resource, the original resource updates itself and performs updates on all advertised resources. To avoid piggybacking, the CSE hosting the original resource only updates the advertised resources, not the downloaded resources. The resource synchronization process according to the above embodiment is as follows: Figure 9 or Figure 10 As shown.

[0117] Figure 9 An example of signal exchange for resource synchronization based on updates to downloaded resources is shown in an M2M system according to this disclosure. Figure 9 The signal exchange between AE 910, IN-CSE-1 920 which hosts the original resource, MN-CSE 930 which hosts the downloaded resource, and IN-CSE-2 940 which hosts the announced resource is shown.

[0118] refer to Figure 9 In step S901, IN-CSE-1 920 performs an operation to download resources to MN-CSE 930. Specifically, IN-CSE-1 920 downloads the original resources created in IN-CSE-1 920 to MN-CSE 930. Figure 9 In the example, the resource was successfully downloaded. Therefore, the MN-CSE 930 becomes a remote CSE with the same data as the original resource.

[0119] In step S903, AE 910 sends an update request message for the downloaded resource to MN-CSE 930. In other words, AE 910 requests an update for at least one attribute of the downloaded resource stored in MN-CSE 930.

[0120] In step S905, MN-CSE 930 performs local processing for updating the downloaded resources. In this case, MN-CSE 930 checks for the existence of an updated authentication, and if authentication exists, updates the downloaded resources.

[0121] In step S907, MN-CSE 930 sends a response message to AE 910. That is, MN-CSE 930 has completed updating the requested resource in response to AE 910.

[0122] In step S909, MN-CSE 930 performs local processing related to synchronization. When an update to a downloaded resource occurs, MN-CSE 930, acting as a remote CSE, determines that synchronization of the updated information is to be performed. In this case, MN-CSE 930 may determine and perform synchronization based on the values ​​of synchronization-related attributes stored in the resource.

[0123] In step S911, MN-CSE 930 sends an update request message for the original resource to IN-CSE-1 920. In other words, MN-CSE 930 requests an update for at least one attribute of the original resource stored in IN-CSE-1 920. Here, the at least one attribute includes at least one attribute updated according to the request of AE 910. According to an embodiment, the update request message may include at least one of information indicating synchronous updates according to an update request for the downloaded resource and information about the means (e.g., AE 910) that has requested an update for the downloaded resource.

[0124] In step S913, IN-CSE-1 920 sends a response message to MN-CSE 930. That is, IN-CSE-1 920 updates the value of at least one attribute of the original resource and responds to AE 910 that the update request is complete.

[0125] In step S915, IN-CSE-1 920 performs local processing related to synchronization. As the original resource is updated, IN-CSE-1 920 determines that synchronization of the updated information is performed. Specifically, IN-CSE-1 920 determines whether an advertised resource exists for the original resource, and if an advertised resource exists, determines that a process for synchronizing with the advertised resource is performed. In this case, IN-CSE-1 920 may determine and perform synchronization based on the values ​​of synchronization-related attributes stored in the resource. In this embodiment, the update of the original resource leads to synchronization on the advertised resource.

[0126] In step S917, IN-CSE-1 920 sends an update request message for the advertised resource to IN-CSE-2 940. In other words, IN-CSE-1 920 requests an update to at least one attribute of the advertised resource stored in IN-CSE-2 940. Here, the at least one attribute includes at least one attribute to be updated according to the request of MN-CSE 930. According to an embodiment, the update request message may include information indicating an update for synchronization based on the update request of the original resource, information about the means requesting an update of the downloaded resource (e.g., AE 910), and the means that has already requested synchronization (e.g., MN-CSE 930).

[0127] In step S919, IN-CSE-2 940 sends a response message to IN-CSE-1 920. That is, IN-CSE-2 940 updates the value of at least one attribute of the advertised resource and responds to IN-CSE-1 920 that the update request has been completed.

[0128] Figure 10 An example of signal exchange for resource synchronization based on updates to the original resource is shown in an M2M system according to this disclosure. Figure 10 The signal exchange between AE 1010, IN-CSE-1 1020 which hosts the original resource, MN-CSE 1030 which hosts the downloaded resource, and IN-CSE-2 1040 which hosts the announced resource is shown.

[0129] Reference Figure 10 In step S1001, IN-CSE-1 1020 performs an operation to download resources to MN-CSE 1030. Specifically, IN-CSE-1 1020 downloads the original resources created in IN-CSE-1 1020 to MN-CSE 1030. Figure 9 In the example, the resource was successfully downloaded. Therefore, the MN-CSE 1030 becomes a remote CSE with the same data as the original resource.

[0130] In step S1003, AE 1010 sends an update request message for the original resource to IN-CSE-1 1020. In other words, AE 1010 requests to update at least one attribute of the original resource stored in IN-CSE-1 1020.

[0131] In step S1005, IN-CSE-1 1020 performs local processing related to updating the original resource. At this time, IN-CSE-1 1020 checks if there is an authentication for the update. If authentication exists, IN-CSE-1 1020 determines if a downloaded resource exists. Since a downloaded resource exists, IN-CSE-1 1020 does not update the original resource and determines that the update request should be forwarded to MN-CSE 1030, which hosts the downloaded resource.

[0132] In step S1007, IN-CSE-1 1020 sends an update request message for the downloaded resource to MN-CSE 1030. That is, IN-CSE-1 1020 sends an update request for AE 1010 to MN-CSE 1030. In this case, the update request message may include at least one of the following: information indicating that an update request has been sent and information about the device (e.g., AE 1010) that has requested an update of the resource.

[0133] In step S1009, MN-CSE 1030 performs local processing related to synchronization. That is, MN-CSE 1030 updates the value of at least one attribute of the downloaded resource based on the update request.

[0134] In step S1011, MN-CSE 1030 sends a response message to IN-CSE-1 1020. That is, MN-CSE 1030 updates the value of at least one attribute of the downloaded resource and responds to IN-CSE-1 1020 that the update request is complete.

[0135] In step S1013, IN-CSE-1 1020 performs local processing on the update of the original resource. That is, when IN-CSE-1 1020 receives a response message indicating that the update of the downloaded resource is complete, it updates at least one attribute of the original resource. In other words, the original resource is updated when it is successfully updated in MN-CSE 1030, which hosts the downloaded resource. Additionally, IN-CSE-1 1020 determines to synchronize the update information. Specifically, IN-CSE-1 1020 determines whether there is an advertised resource for the original resource, and if so, determines to perform a synchronization process with the advertised resource. In this case, IN-CSE-1 1020 may determine and perform synchronization based on the values ​​of synchronization-related attributes stored in the resource. In this embodiment, the update of the original resource results in synchronization on the advertised resource.

[0136] In step S1015, IN-CSE-1 1020 sends an update request message for the advertised resource to IN-CSE-2 1040. In other words, IN-CSE-1 1020 requests an update for at least one attribute of the advertised resource stored in IN-CSE-2 1040. Here, the at least one attribute includes at least one attribute updated according to the request of MN-CSE 1030. According to an embodiment, the update request message includes at least one of the following: information indicating an update for synchronization based on an update request for the original resource; information about a device that has requested an update for a downloaded resource (e.g., AE 1010); and information about a device that has requested synchronization (e.g., MN-CSE 1030).

[0137] In step S1017, IN-CSE-2 1040 sends a response message to IN-CSE-1 1020. That is, IN-CSE-2 1040 updates the value of at least one attribute of the advertised resource and responds to IN-CSE-1 1020 that the update request is complete.

[0138] In step S1019, IN-CSE-1 1020 sends a response message to AE 1010. That is, IN-CSE-1 1020 responds to AE 1010 that the update of the requested resource has been completed.

[0139] According to an embodiment, updates can occur on both the original resource and the downloaded resource. When an update occurs on the original resource, the update is propagated to the downloaded resource and the advertised resource. When an update occurs on a downloaded resource, the CSE hosting the downloaded resource attempts to update the original resource. Additionally, the CSE hosting the original resource updates all advertised resources. To avoid piggybacking, when an update request is received from the CSE hosting the downloaded resource, the CSE hosting the original resource only updates the advertised resources. The resource synchronization process according to the above embodiment is as follows. Figure 11 or Figure 12 As shown.

[0140] Figure 11 Another example of signal exchange for resource synchronization based on updates of downloaded resources is shown in an M2M system according to this disclosure. Figure 11 The signal exchange between AE 1110, IN-CSE-1 1120 which hosts the original resource, MN-CSE 1130 which hosts the downloaded resource, and IN-CSE-2 1140 which hosts the announced resource is shown.

[0141] Reference Figure 11 In step S1101, IN-CSE-1 1120 performs the operation of downloading resources to MN-CSE 1130. Specifically, IN-CSE-1 1120 downloads the original resources created in IN-CSE-1 1120 to MN-CSE 1130. Figure 11 In the example, the resource was successfully downloaded. Therefore, MN-CSE 1130 becomes a remote CSE with the same data as the original resource.

[0142] In step S1103, AE 1110 sends an update request message to MN-CSE 1130 for the downloaded resource. In other words, AE 1110 requests an update for at least one attribute of the downloaded resource stored in MN-CSE 1130.

[0143] In step S1105, MN-CSE 1130 performs local processing for updating the downloaded resources. In this case, MN-CSE 1130 checks for the existence of an updated authentication, and if an authentication exists, updates the downloaded resources.

[0144] In step S1107, MN-CSE 1130 sends a response message to AE 1110. That is, MN-CSE 1130 responds to AE 1110 that the update of the requested resource has been completed.

[0145] In step S1109, MN-CSE 1130 performs local processing related to synchronization. As an update to the downloaded resource occurs, CSE MN-CSE 1130 (remote CSE) determines that synchronization of the updated information is being performed. In this case, MN-CSE 1130 may determine and perform synchronization based on the values ​​of synchronization-related attributes stored in the resource.

[0146] In step S1111, MN-CSE 1130 sends an update request message for the original resource to IN-CSE-1 1120. In other words, MN-CSE 1130 requests an update of at least one attribute of the original resource stored in IN-CSE-1 1120. Here, the at least one attribute includes at least one attribute updated according to the request of AE 1110. According to an embodiment, the update request message may include information indicating a request for synchronous updates based on updates to downloaded resources and information about the means (e.g., AE 1110) that has requested updates to downloaded resources.

[0147] In step S1113, IN-CSE-1 1120 sends a response message to MN-CSE 1130. That is, IN-CSE-1 1120 updates the value of at least one attribute of the original resource and responds to AE 1110 that the requested update has been completed.

[0148] In step S1115, IN-CSE-1 1120 performs local processing related to synchronization. As an update to the original resource occurs, IN-CSE-1 1120 determines that synchronization of the updated information is performed. Specifically, IN-CSE-1 1120 checks whether there is an advertised resource relative to the original resource, and if such an advertised resource exists, determines that a process for synchronizing with the advertised resource is performed. In this case, IN-CSE-1 1120 may determine and perform synchronization based on the values ​​of synchronization-related attributes stored in the resource. In this embodiment, the update of the original resource leads to the synchronization of the advertised resource.

[0149] In step S1117, IN-CSE-1 1120 sends an update request message for the advertised resource to IN-CSE-2 1140. In other words, IN-CSE-1 1120 requests an update to at least one attribute of the advertised resource stored in IN-CSE-2 1140. Here, the at least one attribute includes at least one attribute updated according to the request of MN-CSE 1130. According to an embodiment, the update request message includes at least one of the following: information indicating a request for synchronization updates based on updates to the original resource; information about a device that has requested updates to downloaded resources (e.g., AE 1110); and information about a device that has requested synchronization (e.g., MN-CSE 1130).

[0150] In step S1119, IN-CSE-2 1140 sends a response message to IN-CSE-1 1120. That is, IN-CSE-2 1140 updates the value of at least one attribute of the advertised resource and responds to IN-CSE-1 1120 that the requested update has been completed.

[0151] Figure 12 Another example of signal exchange for resource synchronization based on updates of the original resource is shown in an M2M system according to this disclosure. Figure 12 The signal exchange between AE 1210, IN-CSE-1 1220 hosting the original resource, MN-CSE1230 hosting the downloaded resource, and IN-CSE-2 1240 hosting the announced resource is shown.

[0152] refer to Figure 12 In step S1201, IN-CSE-1 1220 performs an operation to download resources to MN-CSE 1230. Specifically, IN-CSE-1 1220 downloads the original resources created in IN-CSE-1 1220 to MN-CSE 1230. Figure 12 In the example, the resource was successfully downloaded. Therefore, MN-CSE 1230 becomes a remote CSE with the same data as the original resource.

[0153] In step S1203, AE 1210 sends an update request message for the original resource to IN-CSE-1 1220. In other words, AE 1210 requests to update at least one attribute of the original resource stored in IN-CSE-1 1220.

[0154] In step S1205, IN-CSE-1 1220 performs local processing for updating the original resource. At this time, IN-CSE-1 1220 checks if an update authentication exists. If authentication exists, IN-CSE-1 1220 updates the original resource. Furthermore, IN-CSE-1 1220 determines if a downloaded resource exists and determines that the update process for the downloaded resource is executed.

[0155] In step S1207, IN-CSE-1 1220 sends an update request message for the downloaded resource to MN-CSE 1230. The update request message may include at least one of the following: information indicating a request for synchronization updates based on updates to the original resource and information about the device (e.g., AE1210) that has requested an update to the original resource.

[0156] In step S1209, MN-CSE 1230 performs local processing for updating the downloaded resource. That is, MN-CSE 1230 updates the value of at least one attribute of the downloaded resource based on the update request.

[0157] In step S1211, MN-CSE 1230 sends a response message to IN-CSE-1 1220. That is, MN-CSE 1230 updates the value of at least one attribute of the downloaded resource and responds to IN-CSE-1 1220 that the update request is complete.

[0158] In step S1213, IN-CSE-1 1220 sends an update request message for the advertised resource to IN-CSE-2 1240. In other words, IN-CSE-1 1220 requests an update for at least one attribute of the advertised resource stored in IN-CSE-2 1240. Here, the at least one attribute includes at least one attribute updated according to the request of MN-CSE 1230. According to an embodiment, the update request message includes at least one of the following: information indicating a request for synchronization updates based on updates to the original resource; information about a device that has requested updates to downloaded resources (e.g., AE1210); and information about a device that has requested synchronization (e.g., MN-CSE1230).

[0159] In step S1215, IN-CSE-2 1240 sends a response message to IN-CSE-1 1220. That is, IN-CSE-2 1240 updates the value of at least one attribute of the advertised resource and responds to IN-CSE-1 1220 that the requested update has been completed.

[0160] In step S1217, IN-CSE-1 1220 sends a response message to AE1210. That is, IN-CSE-1 1220 responds to AE1210 that the update of the requested resource has been completed.

[0161] Figure 13 The configuration of an M2M device in an M2M system according to the present disclosure is shown. Figure 13 The M2M device 1310 or M2M device 1320 shown can be understood as hardware used as at least one of the above-described AE, CSE and NSE.

[0162] refer to Figure 13 The M2M device 1310 may include a processor 1312 for control and a transceiver 1314 for transmitting and receiving signals. Here, the processor 1312 can control the transceiver 1314. Additionally, the M2M device 1310 can communicate with another M2M device 1320. The other M2M device 1320 may also include a processor 1322 and a transceiver 1324, and the processor 1322 and transceiver 1324 can perform the same functions as the processor 1312 and transceiver 1314.

[0163] For example, the initiator, receiver, AE, and CSE described above can be respectively Figure 13 One of the M2M devices 1310 and 1320. Furthermore, Figure 13 Devices 1310 and 1320 can be other devices. For example, Figure 13 Devices 1310 and 1320 can be communication devices, vehicles, or base stations. That is, Figure 13 The devices 1310 and 1320 refer to devices capable of performing communication, and are not limited to the embodiments described above.

[0164] The exemplary embodiments described above can be implemented by various means. For example, the exemplary embodiments of this disclosure can be implemented by hardware, firmware, software, or a combination thereof.

[0165] The foregoing description of exemplary embodiments of the present disclosure has been presented to those skilled in the art for implementing and practicing the present disclosure. While the foregoing description has been given with reference to preferred embodiments of the present disclosure, it will be apparent to those skilled in the art that various changes and modifications may be made to the present disclosure without departing from the spirit and scope of the present disclosure as defined by the appended claims.

[0166] Therefore, this disclosure is not intended to be limited to the exemplary embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein. Furthermore, while exemplary embodiments of this specification have been specifically shown and described, it should be understood that this specification is not limited to the exemplary embodiments described above, but rather, those skilled in the art will understand that various changes and modifications can be made without departing from the spirit and scope of this specification as defined by the appended claims, and these changes and modifications should not be understood solely from the technical ideas and viewpoints of this specification.

[0167] This specification describes both the present disclosure and the method disclosure, and may supplement the description of both inventions as necessary.

[0168] Furthermore, this disclosure has been described with reference to exemplary embodiments thereof. Those skilled in the art will understand that various modifications in form and detail may be made without departing from the essential characteristics of this disclosure. Therefore, the disclosed exemplary embodiments should be considered in an illustrative rather than restrictive sense. The scope of this disclosure is defined by the appended claims rather than by the foregoing description, and all differences within the scope of their equivalents should be construed as included in this disclosure.< / announcesynctype> < / announcetype> < / offloadto> < / announcesynctype> < / announcetype> < / offloadto> < / announcesynctype> < / announcesynctype> < / announcetype> < / announcetype> < / announcetype> < / offloadto> < / offloadto> < / offloadto> < / offloadto> < / announcesynctype> < / announcetype> < / offloadto> < / group> < / groupannc> < / container> < / containerannc> < / resourcetype> < / resourcetype>

Claims

1. A method for operating an M2M device in a machine-to-machine (M2M) system, the method comprising: Create the first resource; Receive a first message requesting an update to the first resource; as well as The second message, used to request an update to the second resource, is transmitted to another device that hosts the second resource synchronized with the first resource. The first resource includes at least one attribute for downloading the resource; and The first resource further includes a synchronization type attribute, which indicates whether the update is propagated unidirectionally or bidirectionally between the announced resource and the original resource. Based on the value of the synchronization type attribute, the synchronization is performed according to one of a first type of unidirectional propagation between the announced resource and the original resource and a second type of bidirectional propagation between the announced resource and the original resource.

2. The method according to claim 1, wherein, The at least one attribute includes at least one of a first attribute of download location and a second attribute of type related to the announcement.

3. The method according to claim 2, wherein, The first attribute includes the address of the downloaded resource corresponding to the first resource.

4. The method according to claim 2, wherein, The second attribute indicates the type of announcement related to the first resource.

5. The method according to claim 2, wherein, The second attribute indicates whether the first resource is a resource advertised for download.

6. The method according to claim 1, further comprising: Update the first resource in response to the first message.

7. The method according to claim 1, wherein, The second resource has a higher update priority than the first resource.

8. The method according to claim 7, wherein, Send the second message before updating the first resource, and The first resource is updated after the second resource is updated.

9. The method according to claim 8, further comprising: Receive a third message from the other device as a response to the second message; as well as Update the first resource.

10. An M2M device in a machine-to-machine (M2M) system, the M2M device comprising: A transceiver is configured to send and receive signals; as well as The processor is configured to control the transceiver. The processor is configured as follows: Create the first resource; Receive a first message requesting an update to the first resource; A second message requesting an update to the second resource is sent to another device that hosts the second resource synchronized with the first resource. The first resource includes at least one attribute for downloading the resource; and The first resource further includes a synchronization type attribute, which indicates whether the update is propagated unidirectionally or bidirectionally between the announced resource and the original resource. Based on the value of the synchronization type attribute, the synchronization is performed according to one of a first type of unidirectional propagation between the announced resource and the original resource and a second type of bidirectional propagation between the announced resource and the original resource.

11. The M2M device according to claim 10, wherein, The at least one attribute includes at least one of a first attribute of download location and a second attribute of type related to the announcement.

12. The M2M device according to claim 11, wherein, The first attribute includes the address of the downloaded resource corresponding to the first resource.

13. The M2M device according to claim 11, wherein, The second attribute indicates the type of announcement related to the first resource.

14. The M2M device according to claim 11, wherein, The second attribute indicates whether the first resource is a resource advertised for download.

15. The M2M device according to claim 10, The second resource has a higher update priority than the first resource. The second message is sent before updating the first resource, and The first resource is updated after the second resource is updated.

Images