US11032364B2 - Method and apparatus for interworking between heterogeneous systems - Google Patents

Method and apparatus for interworking between heterogeneous systems Download PDF

Info

Publication number
US11032364B2
US11032364B2 US15/771,268 US201615771268A US11032364B2 US 11032364 B2 US11032364 B2 US 11032364B2 US 201615771268 A US201615771268 A US 201615771268A US 11032364 B2 US11032364 B2 US 11032364B2
Authority
US
United States
Prior art keywords
resource
oic
cse
request message
onem2m
Prior art date
Legal status (The legal status 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 status listed.)
Expired - Fee Related, expires
Application number
US15/771,268
Other languages
English (en)
Other versions
US20180316755A1 (en
Inventor
Ji-Eun Keum
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Samsung Electronics Co Ltd
Original Assignee
Samsung Electronics Co Ltd
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 Samsung Electronics Co Ltd filed Critical Samsung Electronics Co Ltd
Priority to US15/771,268 priority Critical patent/US11032364B2/en
Assigned to SAMSUNG ELECTRONICS CO., LTD. reassignment SAMSUNG ELECTRONICS CO., LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: KEUM, JI-EUN
Publication of US20180316755A1 publication Critical patent/US20180316755A1/en
Application granted granted Critical
Publication of US11032364B2 publication Critical patent/US11032364B2/en
Expired - Fee Related legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
    • H04L29/06—
    • H04L29/08—
    • 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/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/104—Peer-to-peer [P2P] networks
    • H04L67/1074—Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
    • 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
    • H04L67/16—
    • H04L67/28—
    • H04L67/2823—
    • 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/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • 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/50—Network services
    • H04L67/56—Provisioning of proxy services
    • 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/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/565—Conversion or adaptation of application format or content
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08—Protocols for interworking; Protocol conversion
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Definitions

  • the present disclosure relates to a technology related to subscription and notification for interworking between heterogeneous systems.
  • the Internet is evolving from a human-centered connectivity network where humans generate and consume information into an Internet of Things (IoT) network where distributed entities such as things send, receive and process information without human intervention.
  • Internet of Everything (IoE) technologies in which a big data processing technology through connection with a cloud server, for example, are combined with the IoT technology, have also emerged.
  • IoT Internet of Everything
  • various technologies such as sensing technology, wired/wireless communication and network infrastructure, service interfacing technology, and security technology are required, and recently, even technologies for sensor network, Machine to Machine (M2M), Machine Type Communication (MTC) for connection between things are being studied.
  • M2M Machine to Machine
  • MTC Machine Type Communication
  • IoT Internet Technology
  • IoT may be applied to a variety of areas, such as smart home, smart building, smart city, smart car or connected car, smart grid, health care, smart home appliances and advanced medical services through convergence and combination between existing Information Technologies (IT) and various industrial applications.
  • IT Information Technologies
  • oneM2M is a global partnership project of seven international standard development organizations from Korea (TTA), Europe (ETSI), North America (ATIS, TIA), China (CCSA) and Japan (ARIB, TTC) that gather together for the purpose of developing a common IoT platform.
  • the common platform technology developed by oneM2M provides 12 common functions: registration, search, security, group management, data management, subscription and notification, device management, application management, data transfer management, network service utilization, location information management, and service layer charging.
  • the oneM2M common platform has a Resource Oriented Architecture (ROA) structure and can thus be accessed by the representational safe transfer (REST) application programming interface (API) like a web.
  • ROA Resource Oriented Architecture
  • REST representational safe transfer
  • API application programming interface
  • OIC is an industry consortium launched in July 2014 mainly by Intel, Samsung Electronics, Atmel, Wind River, etc., and is now developing a platform to ensure interoperability and requirements for connecting IoT devices.
  • Key functions of the platform being developed by OIC include device discovery, data transfer, device management, data management, and security function, through which device-based interoperability and service level interoperability are enabled.
  • An objective of the present disclosure is to provide a method and apparatus for supporting interworking between heterogeneous systems.
  • a method for supporting interworking between heterogeneous systems includes sending a message requesting subscription to a resource to a first device; receiving a notification message indicating that a resource of the first device has changed from the first device; sending a request message to a second device to monitor a resource of the second device; receiving a response message indicative of a resource of the second device in return for transmission of the request message, wherein the resource of the first device is related to the second device.
  • an apparatus for supporting interworking between heterogeneous systems includes a transceiver configured to send a message requesting subscription to a resource to a first device, receive a notification message indicating that a resource of the first device has changed from the first device, send a request message to a second device to monitor a resource of the second device, and receive a response message indicative of a resource of the second device in return for transmission of the request message; and a controller configured to control the transceiver, wherein the resource of the first device is related to the second device.
  • FIG. 1 shows a network configuration of oneM2M
  • FIG. 2 shows the Observe mechanism of OIC
  • FIG. 3 shows a procedure for subscription between oneM2M and OIC, according to an embodiment of the present disclosure
  • FIG. 4 shows a notification procedure between oneM2M and OIC, according to an embodiment of the present disclosure
  • FIG. 5 shows a procedure for canceling subscription between oneM2M and OIC, according to an embodiment of the present disclosure
  • FIG. 6 shows an update procedure between oneM2M and OIC, according to an embodiment of the present disclosure
  • FIG. 7 shows a resource creation procedure of an OIC client between oneM2M and OIC, according to an embodiment of the present disclosure
  • FIG. 8 is a flowchart of operation of an interworking proxy entity, according to an embodiment of the present disclosure.
  • FIG. 9 shows a block diagram of an interworking proxy entity, according to an embodiment of the present disclosure.
  • FIG. 1 shows a network configuration of oneM2M.
  • a network of oneM2M may include an Application Dedicated Node (ADN) 101 , an Application Service Node (ASN) 103 , a Middle Node (MN) 105 , and an Infrastructure Node (IN) 107 .
  • ADN Application Dedicated Node
  • ASN Application Service Node
  • MN Middle Node
  • I Infrastructure Node
  • the ADN 101 is a device including an Internet of Things (IoT) application, which means a constrained device having constrained capability only with IoT service logic.
  • the ASN 103 refers to an IoT device that offers not only an IoT application but also a common service.
  • the MN 105 is an IoT gateway that connects other nodes and the network IN 107 , and the IN 107 may be an IOT server located in a network infrastructure for providing an IoT service.
  • the aforementioned nodes may each include one or more Application Entities (AEs) or Common Service Entities (CSE).
  • AEs Application Entities
  • CSE Common Service Entities
  • the AE provides application logic for end-to-end IoT solutions.
  • the CSE provides common service functions available for common use by various AEs of IoT.
  • the common service functions include a data management and storage function, a communication management and transfer process function, a registration function, a security function, a subscription and notification function, a group management function, etc.
  • the subscription and notification function plays a role in notifying this.
  • the subscription and notification function may correspond to the Observe structure of OIC, which will be described later.
  • oneM2M conforms to a resource-oriented architecture (RoA).
  • the common service function is provided with operation on a resource.
  • the resource has a tree structure and may be addressed with a unique address (e.g., URI).
  • the resource is stored in the CSE, and the AE cannot have a resource.
  • the resource has various resource types, each of which is defined by attributes and child resource types.
  • an AE resource type may include attributes of AE-related information (e.g., application name, network address, semantic information), and may have container resource type for storing information generated by the AE and a group resource type for forwarding operation to a group as child resources.
  • the resource type may be created for an actual resource through create operation and may use a service through modify, obtain, delete, notify operations on the resource.
  • the resource type includes an AE resource type, a container resource type, a subscription resource type, etc.
  • AE information registered in the CSE or AE information of other CSE, which is registered in the CSE is stored.
  • For the subscription resource type data for performing a function to notify that a state of a resource is changed through notification is stored.
  • FIG. 2 shows the Observe mechanism of OIC.
  • the Observe mechanism refers to monitoring a resource by sending a retrieve request message.
  • An OIC client 210 and an OIC server refers to a client and a server, respectively, that support OIC.
  • the OIC client 210 sends a retrieve request message to the OIC server 220 for monitoring a resource of the OIC server 220 , in 201 .
  • the OIC server 220 stores the retrieve request message, in 203 .
  • the OIC server 220 sends a retrieve response message to the OIC client 210 in response to the retrieve request message, in 205 .
  • the OIC server 220 detects this, in 207 .
  • the OIC server 220 may detect it.
  • the OIC server 220 may notify the OIC client 210 that the resource of the OIC server 220 has changed in a retrieve response message, in 209 .
  • FIG. 3 shows a subscription procedure between oneM2M and OIC, according to an embodiment of the present disclosure.
  • an interworking proxy entity (IPE) 307 is a network node for performing a function of an OIC client and an interworking function with oneM2M.
  • the IPE 307 may be divided into an OIC client 303 and an interworking function 305 based on functions.
  • the interworking function acts as an entity of the application layer in the oneM2M standard.
  • the interworking function 305 of the IPE 307 will now be described.
  • ⁇ > represents a resource of the aforementioned resource tree structure.
  • the resource tree structure may be represented in MN-CSEBase/OIC-AE/Container/Subscription, and each resource is represented with ⁇ container>, ⁇ subscription>, etc.
  • ⁇ subscription> may be represented as a child resource of ⁇ container>.
  • the IPE 307 is assumed to be subscribing to a container resource managed by a CSE 309 to know of a create request for ⁇ subscription>, in 331 .
  • an attribute value of a notification URI of the ⁇ subscription> resource needs to be a URI of the IPE 307 .
  • a CSE in an infrastructure node (denoted as IN-CSE) 313 sends a request message to create a ⁇ subscription> resource in a CSE in a middle node, in 333 .
  • the CSE 309 in the middle node sends a response message to the create request for resource to the IN-CSE 313 , in 335 .
  • the CSE 309 in the middle node sends a message indicating that the ⁇ subscription> resource has been created in the tree structure of the resource to the IPE 307 , in 337 .
  • the interworking function 305 in the IPE 307 may receive the message from the CSE 309 and convert the message to a retrieve request message.
  • a uniform resource identifier (URI) of an upper resource (i.e., a parent resource) of the ⁇ subscription> resource may correspond to parameter “to” in the retrieve request message.
  • a URI of an OIC client in an intermediary may correspond to parameter “fr”, i.e., from, in the retrieve request message.
  • a resource ID of the ⁇ subscription> resource may correspond to parameter “ri” in the retrieve request message, i.e., an identifier of the retrieve request.
  • the OIC client 303 sends the retrieve request message to the OIC device 301 , in 339 .
  • the OIC device as herein used refers to the aforementioned OIC server.
  • the OIC device 301 sends a retrieve response message to the OIC client 303 in response to the retrieve request message, in 341 .
  • FIG. 4 shows a notification procedure between oneM2M and OIC, according to an embodiment of the present disclosure.
  • the CSE 309 in the middle node is assumed to be subscribing to a resource of the OIC device 301 through the IPE 307 , in 401 .
  • the OIC device 301 sends a message notifying of a changed resource of the OIC device 301 to the OIC client 303 in the retrieve response message, in 403 .
  • a particular condition may be set up for the resource change, and only when the particular condition is met, the notification message may be sent to the OIC client 303 .
  • the IPE 307 converts the retrieve response message to a notify request message of oneM2M and sends the notify request message to the CSE 309 in the middle node 311 , in 405 .
  • Parameter “cn” in the retrieve response message may correspond to parameter “content” in the notify request message of oneM2M.
  • the parameter “cn” refers to information of a resource requested by the OIC client 303 .
  • the CSE 309 in the middle node 311 sends the notify request message of oneM2M to the IN-CSE 313 , in 407 .
  • the IN-CSE 313 sends a notify response message of oneM2M to the CSE 309 in the middle node in response to the notify request message of oneM2M, in 409 .
  • FIG. 5 shows a procedure for canceling subscription between oneM2M and OIC, according to an embodiment of the present disclosure.
  • the IN-CSE may not be aware of it.
  • the IPE 307 is assumed to be subscribing to a container resource managed by a CSE 309 to know of a delete request for the ⁇ subscription> resource of the CSE in the middle node 311 , in 501 .
  • a resource architecture of the CSE 309 in the middle node 311 may be, for example, MN-CSEBase/OIC-AE/Container/Subscription.
  • the IN-CSE 313 sends a delete request message for the ⁇ subscription> resource of the CSE 309 in the middle node 311 to the CSE 309 in the middle node 311 , in 503 .
  • the CSE 309 in the middle node 311 sends a response message to the delete request to the IN-CSE 313 , in 505 .
  • the CSE 309 in the middle node 311 notifies the IPE 307 that the ⁇ subscription> resource has been deleted, in 507 .
  • the OIC client 303 sends a retrieve request message to the OIC device 301 , in 339 .
  • the retrieve request message has no instruction of ‘observe’, in 509 .
  • the OIC device 301 sends a retrieve response message to the OIC client 303 in response to the retrieve request message, in 511 .
  • FIG. 6 shows an update procedure for a resource between oneM2M and OIC, according to an embodiment of the present disclosure.
  • the OIC device sends notification by itself when a resource of the OIC device is changed according to a setting, but the update procedure is manually performed for the AE to figure out whether the resource of the OIC device has changed.
  • an IPE 603 is assumed to be subscribing to a resource of a CSE 605 in a middle node to know of an update request for the resource, in 611 .
  • An AE 607 sends an update request message for a resource of an OIC device 601 to the CSE 605 in the middle node, in 613 .
  • the operation is described herein to be performed by the AE, but may also be performed by an IN-CSE.
  • the CSE 605 in the middle node sends a notification request message to update whether the resource of the OIC device 601 has changed to the IPE 603 , in 615 .
  • the IPE 603 sends an update request message for the resource of the OIC device 601 to the OIC device 601 , in 617 .
  • the OIC device 601 sends an update response message for the resource of the OIC device 601 to the IPE 603 , in 619 .
  • the IPE 603 converts the update response message for the resource of the OIC device 601 to a oneM2M response message and sends the oneM2M response message to the CSE 605 in the middle node, in 621 .
  • the CSE 605 in the middle node sends an update response message for the resource of the OIC device 601 to the AE 607 , in 623 .
  • the CSE 605 in the middle node may use an event type, “update a direct child resource for subscribing to a resource”, for the update procedure.
  • FIG. 7 shows a procedure of creating a resource of an OIC device between oneM2M and OIC, according to an embodiment of the present disclosure.
  • the IPE 603 is assumed to be subscribing to a resource of the CSE 605 in the middle node to know of a request to create a resource of the OIC device, in 701 .
  • the AE 607 sends a create request message for a resource of the OIC device to the CSE 605 in the middle node, in 703 .
  • the operation is also described herein to be performed by the AE, but may also be performed by an IN-CSE.
  • the CSE in the middle node 605 sends a notification message to create the resource of the OIC device 601 to the IPE 603 , in 705 .
  • the IPE 603 sends a create request message to create the resource of the OIC device 601 to the OIC device 601 , in 707 .
  • the OIC device 601 After creating the resource, the OIC device 601 sends a create response message indicating that the resource of the OIC device 601 has been created to the IPE 603 , in 709 .
  • the IPE 603 converts the create response message to a oneM2M response message and sends the oneM2M response message to the CSE 605 in the middle node, in 711 .
  • the CSE 605 in the middle node sends a response message about the creation to the AE 607 , in 713 .
  • the CSE 605 in the middle node may use an event type, “create a direct child resource for a resource to be subscribed to”, for the procedure to create the resource.
  • FIG. 8 is a flowchart of operation of an interworking proxy entity (IPE), according to an embodiment of the present disclosure.
  • IPE interworking proxy entity
  • the IPE sends a message requesting subscription to a resource to a first device to support interworking between the first device and a second device, in 801 .
  • the first device may be a oneM2M device
  • the second device may be an OIC device.
  • the IPE receives a notification message indicating that a resource of the first device has changed from the first device, in 803 .
  • the IPE sends a request message to the second device to monitor a resource of the second device, in 805 .
  • the IPE receives a response message indicative of the resource of the second device in return for transmission of the request message, in 807 .
  • the resource of the first device is related to the second device.
  • FIG. 9 shows a block diagram of an interworking proxy entity, according to an embodiment of the present disclosure.
  • an IPE 901 may include a controller 903 and a transceiver 905 . Although it is operated with multiple components, the following operation may be performed in a single component as needed.
  • the controller 903 controls the transceiver 905 and converts oneM2M-related and OIC-related messages.
  • the transceiver 905 sends or receives messages with an OIC client and a CSE.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)
  • Information Transfer Between Computers (AREA)
US15/771,268 2015-10-26 2016-10-26 Method and apparatus for interworking between heterogeneous systems Expired - Fee Related US11032364B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US15/771,268 US11032364B2 (en) 2015-10-26 2016-10-26 Method and apparatus for interworking between heterogeneous systems

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US201562246234P 2015-10-26 2015-10-26
US15/771,268 US11032364B2 (en) 2015-10-26 2016-10-26 Method and apparatus for interworking between heterogeneous systems
PCT/KR2016/012103 WO2017074034A1 (ko) 2015-10-26 2016-10-26 이종 시스템에서 상호연동에 대한 방법 및 장치

Publications (2)

Publication Number Publication Date
US20180316755A1 US20180316755A1 (en) 2018-11-01
US11032364B2 true US11032364B2 (en) 2021-06-08

Family

ID=58630566

Family Applications (1)

Application Number Title Priority Date Filing Date
US15/771,268 Expired - Fee Related US11032364B2 (en) 2015-10-26 2016-10-26 Method and apparatus for interworking between heterogeneous systems

Country Status (5)

Country Link
US (1) US11032364B2 (de)
EP (1) EP3340563B1 (de)
KR (1) KR102463014B1 (de)
CN (1) CN108353077B (de)
WO (1) WO2017074034A1 (de)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220374502A1 (en) * 2021-05-18 2022-11-24 Hyundai Motor Company Method and apparatus for supporting digital rights management in machine-to-machine system

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107370782B (zh) * 2016-05-13 2021-08-31 京东方科技集团股份有限公司 对设备进行操作的方法、控制装置和代理装置
WO2019075317A1 (en) 2017-10-12 2019-04-18 Convida Wireless, Llc INTERWORKING SERVICE FOR THE INTERNET OF RESTOUS OBJECTS
CN110858845A (zh) * 2018-08-22 2020-03-03 株式会社日立制作所 一种数据订阅方法及互操作代理应用实体
US11211171B2 (en) * 2019-01-11 2021-12-28 Tele-Commuter Resources, Inc. Systems and methods for improving smart city and smart region architectures
CN111614704A (zh) * 2019-02-25 2020-09-01 株式会社日立制作所 一种数据订阅方法及网关
KR102285352B1 (ko) * 2019-11-28 2021-08-02 세종대학교산학협력단 이기종 IoT 장치와 IoT 플랫폼의 연동을 위한 프록시, 방법 및 상기 프록시를 포함하는 시스템
WO2021134757A1 (zh) * 2020-01-02 2021-07-08 Oppo广东移动通信有限公司 与用户进行信息交互的方法和装置
CN114791860A (zh) * 2021-01-26 2022-07-26 京东方科技集团股份有限公司 一种新型订阅应用的方法、设备和介质
WO2023068393A1 (ko) * 2021-10-19 2023-04-27 한국전자기술연구원 Onem2m 시스템에서 리소스 레이블 조회 방법
US11949802B1 (en) 2022-11-29 2024-04-02 Pusan National University Industry-University Cooperation Foundation Blockchain-based platform system for interworking with one machine-to-machine(oneM2M) and lightweight machine-to-machine (LWM2M), and method of implementing blockchain-based platform

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20070009477A (ko) 2005-07-15 2007-01-18 닛본 덴끼 가부시끼가이샤 정보 교환 시스템, 이것에 이용되는 관리 서버, 및네트워크 부하를 경감하기 위한 방법
WO2014129802A1 (ko) 2013-02-19 2014-08-28 엘지전자 주식회사 M2m 서비스 설정 변경 방법 및 이를 위한 장치
KR20140132998A (ko) 2013-05-09 2014-11-19 전자부품연구원 개방형 ｍ２ｍ 시스템에서 ｇｗ 기반 ｉｄ 관리 방법
WO2014185754A1 (ko) 2013-05-16 2014-11-20 엘지전자 주식회사 M2m 통신 시스템에서 구독 및 통지를 위한 방법 및 이를 위한 장치
KR20150067043A (ko) 2013-12-06 2015-06-17 주식회사 케이티 자원 정보를 송수신하는 방법 및 이를 위한 장치
US20160234691A1 (en) * 2013-11-08 2016-08-11 Lg Electronics Inc. Method for subscription and notification in m2m communication system and device therefor
US20170311303A1 (en) * 2014-10-27 2017-10-26 Lg Electronics Inc. Method for guaranteeing operation of control message in wireless communication system and device for same

Patent Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20070009477A (ko) 2005-07-15 2007-01-18 닛본 덴끼 가부시끼가이샤 정보 교환 시스템, 이것에 이용되는 관리 서버, 및네트워크 부하를 경감하기 위한 방법
US20070016674A1 (en) 2005-07-15 2007-01-18 Nec Corporation Information exchange system, management server, and method for reducing network load used in the same
WO2014129802A1 (ko) 2013-02-19 2014-08-28 엘지전자 주식회사 M2m 서비스 설정 변경 방법 및 이를 위한 장치
CN104995889A (zh) 2013-02-19 2015-10-21 Lg电子株式会社 用于修改m2m服务设置的方法及其装置
US20160007137A1 (en) 2013-02-19 2016-01-07 Lg Electronics Inc. Method for modifying m2m service setting and apparatus therefor
KR20140132998A (ko) 2013-05-09 2014-11-19 전자부품연구원 개방형 ｍ２ｍ 시스템에서 ｇｗ 기반 ｉｄ 관리 방법
WO2014185754A1 (ko) 2013-05-16 2014-11-20 엘지전자 주식회사 M2m 통신 시스템에서 구독 및 통지를 위한 방법 및 이를 위한 장치
US20160088420A1 (en) 2013-05-16 2016-03-24 Lg Electronics Inc. Method for subscription and notification in m2m communication system and apparatus for same
US20160234691A1 (en) * 2013-11-08 2016-08-11 Lg Electronics Inc. Method for subscription and notification in m2m communication system and device therefor
KR20150067043A (ko) 2013-12-06 2015-06-17 주식회사 케이티 자원 정보를 송수신하는 방법 및 이를 위한 장치
US20170311303A1 (en) * 2014-10-27 2017-10-26 Lg Electronics Inc. Method for guaranteeing operation of control message in wireless communication system and device for same

Non-Patent Citations (19)

* Cited by examiner, † Cited by third party
Title
Chinese Office Action dated Apr. 22, 2020 issued in counterpart application No. 201680062413.X, 16 pages.
Choi, Jinhyeock et al.; Functional Architecture for oneM2M—OIC interworking; ARC-2015-2118R04; Copyright 2015 oneM2M Partners; pp. 7.
ETSI, Technical Specification, oneM2M Functional Architecture (oneM2M TS-0001 Version 1.13.1 Release 1), ETSI TS 118 101 V1.1.0, Mar. 1, 2016, 319 pages.
ETSI, Technical Specification, oneM2M OIC Interworking (oneM2M TS-0024, Version 2.0.0 Release 2, ETSI TS 118 124 V2.0.0, Sep. 13, 2016, 19 pages.
European Search Report dated May 18, 2018 issued in counterpart application No. 16860217.5-1218, 11 pages.
Jaeseok Yun, Interoperability Test Based on Open-source IoT Platforms, Jun. 23, 2015 (Year: 2015). *
Jieun Keum et al., "OIC Interworking Procedure for Subscription and Notification", ARC-2015-2189R01, XP84013438, Oct. 20, 2015, 4 pages.
Kiran Vedula et al., "oneM2M and OIC Interworking, TR-0023 Baseline after TP19", XP084011619, Sep. 23, 2015, 19 pages.
Kiran Vedula et al., "Updated Functional Architecture for oneM2M-OIC Interworking", ARC-2015-2180R01, XP084013388, Oct. 13, 2015, 5 pages.
OneM2M; 13 October 2015 (2015-10-13), KIRAN VEDULA, SAMSUNG ELECTRONICS, KIRAN VEDULA, SAMSUNG ELECTRONICS (TTA): "ARC-2015-2180R01-Updated_Fuctional_Architecture_for_oneM2M-OIC_interworking", XP084013388, retrieved from URL = http://member.onem2m.org/Application/documentapp/downloadimmediate/default.aspx?docID=13906
OneM2M; 20 October 2015 (2015-10-20), SAMSUNG, KETI, DT&C, KIRAN VEDULA, SAMSUNG ELECTRONICS (TTA): "ARC-2015-2189R01-OIC_Interworking_Procedure_Subscription_Notification", XP084013438, retrieved from URL = http://member.onem2m.org/Application/documentapp/downloadimmediate/default.aspx?docID=13950
OneM2M; 23 September 2015 (2015-09-23), KIRAN VEDULA, SAMSUNG ELECTRONICS, KIRAN VEDULA, SAMSUNG ELECTRONICS (TTA): "TR-0023 Baseline after TP19", XP084011619, retrieved from URL = http://member.onem2m.org/Application/documentapp/downloadimmediate/default.aspx?docID=13783
OneM2M; 8 July 2016 (2016-07-08), SAMSUNG ELECTRONICS, LAURENT VELEZ, EUROPEAN TELECOMMUNICATIONS STANDARDS INSTITUTE (ETSI): "New baseline V0.2.1 following Edithelp comments", XP084017488, retrieved from URL = http://member.onem2m.org/Application/documentapp/downloadimmediate/default.aspx?docID=17804
Open Interconnect Consortium (OIC), Draft OIC Core Candidate Specification Project B (V0.9.9), Part 1, XP055471813, Sep. 3, 2015, 173 pages.
PCT/ISA/210 Search Report issued on PCT/KR2016/012103 (pp. 3).
PCT/ISA/237 Written Opinion issued on PCT/KR2016/012103 (pp. 4).
Samsung Electronics et al., "New Baseline V0.2.1 following Editheip Comments", TR-0023-V0.2.1, XP084017488, Jul. 8, 2016, 29 pages.
Yingjie Hong et al., "Functional Architecture", oneM2M, TR-0023-V0.2.1, XP084013428, Oct. 19, 2015, 380 pages.
YINGJIE HONG, ZTE CORPORATION (CCSA): "Functional Architecture", TS-0001-FUNCTIONAL_ARCHITECTURE-V2_4_0.ZIP, ONEM2M, vol. Work Programme, Work Progr, no. version = v2.4.0, TS-0001-Functional_Architecture-V2_4_0, 19 October 2015 (2015-10-19), pages 1 - 359, XP084013428

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220374502A1 (en) * 2021-05-18 2022-11-24 Hyundai Motor Company Method and apparatus for supporting digital rights management in machine-to-machine system

Also Published As

Publication number Publication date
CN108353077B (zh) 2021-03-30
US20180316755A1 (en) 2018-11-01
CN108353077A (zh) 2018-07-31
EP3340563A4 (de) 2018-06-27
WO2017074034A1 (ko) 2017-05-04
KR102463014B1 (ko) 2022-11-03
EP3340563B1 (de) 2020-02-19
EP3340563A1 (de) 2018-06-27
KR20180061150A (ko) 2018-06-07

Similar Documents

Publication Publication Date Title
US11032364B2 (en) Method and apparatus for interworking between heterogeneous systems
JP6715978B2 (ja) 軽量ｉｏｔ情報モデル
KR101467173B1 (ko) Ｍ２ｍ 네트워크의 리소스 관리 방법 및 리소스 관리 장치
KR102615419B1 (ko) 가입 및 통지 서비스
KR101877188B1 (ko) Ｍｑｔｔ 프로토콜을 이용한 서비스 층 상호연동
EP3163798B1 (de) Verfahren zur verarbeitung von anfragenachrichten in einem drahtloskommunikationssystem und vorrichtung dafür
KR20170055530A (ko) 서비스 레이어를 통해 제3자 서비스들에 대한 액세스를 가능하게 하는 시스템들 및 방법들
CN105531980A (zh) 服务层设备位置管理和隐私控制
KR20190002674A (ko) 자원 구독 방법, 자원 구독 장치, 및 자원 구독 시스템
JP2021193815A (ja) モバイル通信ネットワークにおける近接サービスアクセス
JP2020534605A (ja) 通信ネットワークにおけるサービス層メッセージテンプレート
JP2018529258A (ja) サービス層におけるアンルートリソース発見を可能にする方法
CN107950005B (zh) 服务元素主机选择
CN102752884B (zh) 基于Web技术的物联网系统及该系统的数据处理方法
KR101983993B1 (ko) 게이트웨이 기반의 ｍ２ｍ 디바이스 리소스 동적 그룹핑 방법
EP3912329A1 (de) Automatisierte dienstschicht-nachrichtenflussverwaltung in einem kommunikationsnetz

Legal Events

Date Code Title Description
FEPP Fee payment procedure

Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

AS Assignment

Owner name: SAMSUNG ELECTRONICS CO., LTD., KOREA, REPUBLIC OF

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:KEUM, JI-EUN;REEL/FRAME:045665/0859

Effective date: 20180417

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: FINAL REJECTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE AFTER FINAL ACTION FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: FINAL REJECTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE AFTER FINAL ACTION FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS

STPP Information on status: patent application and granting procedure in general

Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT RECEIVED

STPP Information on status: patent application and granting procedure in general

Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED

STCF Information on status: patent grant

Free format text: PATENTED CASE

FEPP Fee payment procedure

Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

LAPS Lapse for failure to pay maintenance fees

Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STCH Information on status: patent discontinuation

Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362

FP Lapsed due to failure to pay maintenance fee

Effective date: 20250608