# US 12,225,082 B2 · Method and device for synchronization for resource offloading in M2M system > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,225,082 B2 - Document ID: US12225082B2 - Status: Granted - Kind: B2 - Application number: 17/802,218 - Filed: 2021-05-03 - Published: 2023-04-13 - Granted: 2025-02-11 - Earliest claimed: 2020-05-13 - Assignees: Hyundai Motor Company; Kia Corporation; Industry Academy Cooperation Foundation of Sejong University - Applicants: Hyundai Motor Company; Kia Corporation; Industry Academy Cooperation Foundation of Sejong University - Inventors: Jae Seung Song; Min Byeong Lee - Web page: https://patentgrep.com/patent/US12225082B2 ## CPC - H04W 4/70: Services for machine-to-machine communication [M2M] or machine type communication [MTC] - H04L 41/082: the condition being updates or upgrades of network functionality - H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) - H04L 67/1074: for supporting data block transmission mechanisms (file transfer H04L67/06) - H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes - H04L 67/59: Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Resource synchronization in an machine-to-machine (M2M) system is disclosed. A method of operating an M2M device may comprise creating a first resource, receiving a first message for requesting an update to the first resource, and transmitting a second message for requesting an update to a second resource to another device hosting the second resource synchronized with the first resource. The first resource may comprise at least one attribute for offloading of a resource. ## Claims ### Claim 1 A method of operating a machine-to-machine (M2M) device in an M2M system, the method comprising: creating a first resource; receiving a first message for requesting an update to the first resource; and transmitting a second message for requesting an update to a second resource to an other device hosting the second resource synchronized with the first resource, wherein the first resource comprises at least one attribute for offloading for a resource, and wherein the synchronization is performed based on one of a first type where updating is propagated uni-directionally between a offloaded resource and to an original resource or a second type where updating is propagated bi-directionally one-way between a offloaded resource and to an original resource or a second type. ### Claim 2 (depends on 1) The method of claim 1, wherein the at least one attribute comprises at least one of a first attribute for an offloaded location or a second attribute for a type related to announcement. ### Claim 3 (depends on 2) The method of claim 2, wherein the first attribute comprises an address of an offloaded resource corresponding to the first resource. ### Claim 4 (depends on 2) The method of claim 2, wherein the second attribute indicates a type related to announcement of the first resource. ### Claim 5 (depends on 2) The method of claim 2, wherein the second attribute indicates whether the first resource is a resource announced for offloading. ### Claim 6 (depends on 1) The method of claim 1, further comprising: updating the first resource in response to the first message. ### Claim 7 (depends on 1) The method of claim 1, wherein the second resource has higher priority for an update than the first resource. ### Claim 8 (depends on 7) The method of claim 7, wherein the second message is transmitted before the update to the first resource, and wherein the first resource is updated after the second resource is updated. ### Claim 9 (depends on 8) The method of claim 8, further comprising: receiving a third message which is a response to the second message from the other device; and updating the first resource. ### Claim 10 A machine-to-machine (M2M) device in an M2M system, the M2M device comprising: a transceiver configured to transmit and receive a signal; and a processor configured to control the transceiver, wherein the processor is configured to: create a first resource; receive a first message for requesting an update to the first resource; transmit a second message for requesting an update to a second resource to another device hosting the second resource synchronized with the first resource, wherein the first resource comprises at least one attribute for offloading for a resource, and wherein the synchronization is performed based on one of a first type where updating is propagated uni-directionally between a offloaded resource and to an original resource or a second type where updating is propagated bi-directionally one-way between a offloaded resource and to an original resource or a second type. ### Claim 11 (depends on 10) The M2M device of claim 10, wherein the at least one attribute comprises at least one of a first attribute for an offloaded location or a second attribute for a type related to announcement. ### Claim 12 (depends on 11) The M2M device of claim 11, wherein the first attribute comprises an address of an offloaded resource corresponding to the first resource. ### Claim 13 (depends on 11) The M2M device of claim 11, wherein the second attribute indicates a type related to announcement of the first resource. ### Claim 14 (depends on 11) The M2M device of claim 11, wherein the second attribute indicates whether the first resource is a resource announced for offloading. ### Claim 15 (depends on 10) The M2M device of claim 10, wherein the processor is configured to create the second resource having a higher priority, for an updated than the first resource; transmit the second message before the update to the first resource and update the first resource after the second resource is updated.