WO2014182115A1 - Système et procédé m2m ouverts - Google Patents

Système et procédé m2m ouverts Download PDF

Info

Publication number
WO2014182115A1
WO2014182115A1 PCT/KR2014/004143 KR2014004143W WO2014182115A1 WO 2014182115 A1 WO2014182115 A1 WO 2014182115A1 KR 2014004143 W KR2014004143 W KR 2014004143W WO 2014182115 A1 WO2014182115 A1 WO 2014182115A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource
application
topic
domain
metadata
Prior art date
Application number
PCT/KR2014/004143
Other languages
English (en)
Korean (ko)
Inventor
최성찬
김재호
원광호
이상신
안일엽
송민환
윤재석
Original Assignee
전자부품연구원
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 전자부품연구원 filed Critical 전자부품연구원
Priority to US14/889,477 priority Critical patent/US10091134B2/en
Priority to EP14794803.8A priority patent/EP2996298A4/fr
Priority claimed from KR1020140055320A external-priority patent/KR102066294B1/ko
Publication of WO2014182115A1 publication Critical patent/WO2014182115A1/fr

Links

Images

Classifications

    • 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]
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits

Definitions

  • the present invention relates to an M2M system, and more particularly, to an open M2M system and a method for providing resource management, interfaces, and functions thereof.
  • small devices capable of computing, communication and networking functions can be attached to common objects such as meters and thermometers as well as information equipment. These small devices attached to the thing can automatically obtain the information of the thing or can share information through a communication network between the thing.
  • the term refers to a concept and technology for sharing information by connecting a network to a network using a communication device attached to the thing or configuring a communication network between the objects.
  • IoT is defined as "a new information and communication foundation that connects all things in the world to the network so that people and things, things and things can communicate with each other anytime, anywhere.”
  • IoT can be seen as an infrastructure for implementing a ubiquitous space where things are connected anytime, anywhere.
  • Every device must be registered in the search service platform, searchable, and connected to receive the service. It is required to define a resource management method and system of the registration and retrieval server for this purpose, and a search for a system for enabling various IoT devices to operate as IoT services through information registration and retrieval is required.
  • the present invention has been made to solve the above problems, and an object of the present invention is to provide an M2M system and a method for effectively managing resources constituting the M2M system that can optimize information management and sharing.
  • an object of the present invention is to provide a reference interface between a system for registration and search of IoT devices for providing IoT services and a functional model for information management and resource sharing, device search and access through the M2M architecture.
  • an object of the present invention is to provide a variety of Common Services Functions (CSF) through the M2M architecture.
  • CSF Common Services Functions
  • a resource management method includes: registering resources existing in a first domain with a second domain; And searching for metadata of a desired resource in the second domain.
  • the resources may include at least one of a topic, a device, and an application, and the topic may be a group of devices related to a specific subject.
  • the registration step may be performed by a topic creator, a device owner, and an application developer, and the search step may be performed by a user.
  • the second domain may include at least one of a topic directory that holds metadata of a topic, a device directory that holds metadata of a device, and an application directory that stores metadata of an application, wherein the metadata of the device is a device. Can be published in the metadata of the included topic.
  • the metadata of the device and the metadata of the application associated with the device may refer to each other.
  • the application related to the device may also be searched.
  • the searching step may search for a device associated with the application when the application is searched.
  • the method may further include accessing a resource existing in the first domain in an M2M scheme or a P2P scheme with reference to the metadata.
  • the M2M method may be a method of accessing a resource through a third domain that interacts with the first domain and the second domain, and the P2P method may be a method of accessing a resource without going through the third domain. have.
  • a reference interface for interworking between functional models (application, resource service entity, application repository, directory manager, etc.) constituting an open M2M system is provided, thereby providing a common interface such as mutual access, interworking, and data transfer between functional models.
  • This can be used as a standard model for reference in understanding and developing the system.
  • the M2M architecture enables the provision of various CSFs.
  • FIG. 1 is a diagram showing the architecture of an open M2M system to which the present invention is applicable;
  • FIG. 2 is a diagram provided in the description of a resource registration and retrieval process in an open M2M system
  • FIG. 3 is a diagram provided for explaining a topic-based resource publishing & subscription and access control process in an open M2M system
  • FIG. 5 illustrates a functional model and reference interface of an open M2M architecture.
  • FIG. 1 is a diagram showing the architecture of an open M2M system to which the present invention is applicable.
  • An open M2M system to which the present invention is applicable is a system for supporting resource registration, search and access on a global scale (global environment).
  • communication between a user and a resource is possible for both M2M communication and P2P communication.
  • a resource is a physical or virtual component that provides useful data to users in an open M2M architecture.
  • Resources include topics, devices, and applications, but can also include content, contexts, and services.
  • Topic' is a group of devices that are related to topics of interest that are common in open M2M architectures.
  • a “topic” may be a group of temperature sensors, humidity sensors, and illuminance sensors related to measurement of environmental information such as temperature, humidity, and illuminance. The 'topic' will be described later in detail.
  • An open M2M system to which the present invention is applicable includes a discovery domain 100, an interaction domain 200, and a resource domain 300, as shown in FIG. 1.
  • the discovery domain 100 includes a topic directory 110, a device directory 120, and an application directory 130.
  • Topic directory 110 supports topic registration and search.
  • the topic directory 110 includes a topic registration manager 111 for registering a topic of the topic creator 11 and a topic search manager 112 for providing a topic search result to the user 20.
  • the registration and search supported by the topic directory 110 is a topic based approach. That is, the topic registration is performed by registering devices to be included in the topic, and the topic search result is provided by providing devices included in the topic.
  • Device directory 120 supports device registration and retrieval. To this end, the device directory 120 includes a device registration manager 121 for registering a device of the device owner 12 and a device search manager 122 for providing a device search result to the user 20.
  • the device is a concept including a resource server 310, a resource gateway 320, and a resource end-point 330.
  • the application directory 130 supports application registration and search. To this end, the application directory 130 includes an application registration manager 131 for registering an application of the application developer 13 and an application search manager 132 for providing an application search result to the user 20.
  • Resource domain 300 includes a resource server 310, a resource gateway 320, a resource end-point 330, and an application repository 340.
  • a resource gateway may be connected or a resource end point may be connected to a lower part of the resource server 310, and a resource end point may be connected to a lower part of the resource gateway 320. That is, the resource endpoint may be connected to a resource gateway as well as to a resource server.
  • the resource endpoint 330 includes a sensor resource 351 for generating resource data, an actuator resource 352 for control and a management resource 353 for management.
  • the application store 340 stores a service app 341 and a service web 342.
  • the service app 341 is an application for receiving resource data from or controlling the device
  • the service web 342 is a URL of a web page for receiving resource data from the device or controlling the device.
  • the interaction domain 200 is a domain for interaction between the discovery domain 100 and the resource domain 300, and the mobile communication network 210, the wired network 220, the WiFi 230, and the PAN 240 are not mentioned. Other wired / wireless networks.
  • the resource domain 300 may interact with the discovery domain 100 through the interaction domain 200.
  • Devices 310, 320, and 330 have resource DBs 315, 325, and 335 that hold resource data and / or pointers (not shown) that are linked to other resource DBs. Accordingly, 1) the resource server 310 manages the resource data of the resource gateway and the resource endpoint registered to it, and 2) the resource gateway 320 manages the resource data of the resource endpoint registered to it. 3) The resource endpoint 330 may manage resource data of sensors, actuators, and management resources registered therein.
  • 'user 20' refers to a user terminal possessed by the user, but is referred to as 'user 20' for convenience of understanding and marking.
  • user 20 To access resource data, user 20 first searches for resources in topic directory 110, device directory 120, and application directory 130 in discovery domain 100.
  • the user 20 may access resource data of the retrieved resource through the interaction domain 200.
  • the user 20 is able to access the resource data of the resource endpoint in two communication ways.
  • M2M communication method which is an indirect method, in which the user 20 accesses resource data of a resource endpoint through a resource server or a resource gateway.
  • P2P communication method which is a direct method, in which the user 20 directly accesses resource data of a resource of a resource endpoint.
  • the open M2M system provides a resource registration and retrieval process on a global scale through the discovery domain 100. It has been described above that a resource includes a topic, a device, an application, and the like.
  • FIG. 2 is a diagram provided to explain a resource registration and retrieval process in an open M2M system.
  • the discovery domain 100 has resource metadata containing information on actual resources existing in the resource domain 300. Specifically, 1) topic directory 110 holds metadata about a topic, 2) device directory 120 holds metadata about a device, and 3) application directory 130 contains metadata about an application. Holds.
  • the provider 10 may register and publish a resource in the discovery domain 100.
  • the provider 10 is a generic term for the topic creator 11, the device owner 12, and the application developer 13.
  • the user 20 may subscribe to (subscribe) globally by searching for resources in the discovery domain 100.
  • Device metadata in the device directory 120 may be posted to the topic directory 110.
  • metadata of the device is posted in metadata of the topic.
  • the device metadata in the device directory 120 and the application metadata in the application directory 130 refer to each other (associated with each other).
  • the user 20 can find a device associated with the application (reference to that application).
  • the user 20 may find an application associated with (or referring to that device) that device.
  • the user 20 may refer to the metadata to read the resources 310, 320, 330, and the resource of the resource domain 300 through the interaction domain 200. 340 may be accessed.
  • FIG. 3 is a diagram provided to explain a topic based resource publishing & subscription and access control process in an open M2M system.
  • a topic creator first creates and registers a topic in the topic directory 110 (1).
  • 3 illustrates a situation in which topic-1 and topic-2 are generated and registered in the topic directory 110.
  • resources included in the topic are posted to the topic created in the topic directory 110 (2). As shown in FIG. 3, it is also possible for one resource-3 to be posted to multiple topics-1 and 2.
  • the users may search for the topic in the topic directory 110 (3).
  • users may subscribe (subscribe) to a specific topic in the topic directory 110 to obtain relevant resource data related to the topic (4).
  • FIG. 4 is a diagram provided to explain a resource DB.
  • the resource server 310, the resource gateways 320-1, 320-2, and the resource end-points 330-1, 330-2, 330-3 are connected to the resource DB 315, 325-1, 325-2, 335-1, 335-2, 335-3).
  • the legacy device (not shown) does not have a resource DB.
  • devices may be classified into a macro resource entity, a micro resource entity, and a tiny resource entity according to the connection / deployment form of the devices.
  • the macro resource entity is a type that includes all of the resource server 310, the resource gateway 320-1, and the resource end-point 330-1.
  • the SCLS-based model can be viewed as the type of macro resource entity assumed in the embodiment of the present invention.
  • a user can access resource data of the resource endpoint 330-1 through the resource server 310 and the resource gateway 320-1. That is, the resource endpoint 330-1 provides resource data to the user through the resource gateway 320-1 and the resource server 310.
  • the micro resource entity is a type that includes only the resource gateway 320-2 and the resource endpoint 330-2 without including a resource server.
  • a user can access resource data of the resource endpoint 330-2 through the resource gateway 320-2. That is, the resource endpoint 330-2 provides resource data to the user through the resource gateway 320-2.
  • Tiny resource objects are of a type that includes only resource endpoints 330-3, not resource servers and resource gateways.
  • a user can access resource data of the resource endpoint 330-2 without going through a resource server and a resource gateway. That is, resource endpoint 330-2 provides resource data to a user without going through a resource server and a resource gateway.
  • the resource DBs 315, 325-1, 325-2, 335-1, 335-2, and 335-3 have pointers linked to other resource DBs in addition to the resource data. It has been described above in the section. In FIG. 4, the link relationship is shown by the dotted line. By this link relationship, devices can obtain resource data even in resource DBs they do not possess.
  • the interaction domain 200 may provide a user with an integrated view for accessing resources in the resource domain 300 to provide a method and means for interacting with resources.
  • Resources in resource domain 300 are accessible through interaction APIs.
  • FIG. 5 illustrates a functional model and reference interface of an open M2M architecture.
  • the open M2M system includes functional models, an application A, a resource service entity (RSE), an application repository 340, and a directory manager 102.
  • RSE resource service entity
  • the application A is a software program installed in the M2M device, and provides useful data to the user based on device resources, and allows the user to control (manipulate) the device.
  • the M2M device in which the application A is installed / mounted includes the resource server 310, the resource gateways 320-1 and 320-2 and the resource endpoints 330-1 and 330-2 shown in FIG. 5. 330-3) and legacy resource end-point 350.
  • the resource service entity (RSE) is a functional module installed in the device and manages the system and data resources of the device.
  • the resource service entity (RSE) is responsible for not only device resource management but also network, security, registration / retrieval, subscription, and billing.
  • Resource DBs provided in the aforementioned devices may be included in a resource service entity (RSE).
  • the application store 340 is a storage designed to upload and download an application, manages information about the application, and registers application information with the application directory manager 132.
  • Directory manager 102 includes topic directory manager 112, device directory manager 122, and application directory manager 132.
  • the topic directory manager 112 manages topic-based registration / search and topic-based publish / subscribe functions
  • the device directory manager 122 manages directory-based registration / search and topic-based publish / subscribe functions
  • the application directory manager 132 manages application-based registration / search and topic-based publishing / subscription functions.
  • R2R 410 As shown in FIG. 5, in the open M2M architecture, as a reference interface, R2R 410, A2A 420, A2R 430, R2DM 440, R2AR 450, AR2DM 460, A2AR 470. And A2DM 480.
  • RSE-to-RSE (R2R) 410 is a reference interface that provides general functionality for interworking between Resource Service Entities (RSEs).
  • the R2R 410 may include: 1) registration functions between resource service entities (RSEs), 2) data get, put, post, and delete functions between resource service entities (RSEs). And 3) resource service entity (RSE) function request / response functions such as data management, network management, security management, group management, etc. between resource service entities (RSE).
  • Application-to-Application (A2A) 420 is a reference interface that provides general functions for interworking between applications (A).
  • the A2A 420 supports 1) a general function between the applications A and 2) a remote method invocation function between the applications A.
  • the Application-to-RSE (A2R) 430 is a reference interface that provides general functions for interworking between the application A and the resource service entity (RSE).
  • the A2R 430 includes: 1) a function of registering an application A with a resource service entity (RSE), 2) a function of acquiring, transferring, posting, and deleting data between the application A and the resource service entity (RSE), and 3) It supports resource service entity (RSE) function request / response functions such as data management, network management, security management, group management, etc. between the application A and the resource service entity (RSE).
  • RSE-to-Directory Manager (R2DM) 440 is a reference interface that provides general functionality for interworking between a resource service entity (RSE) and directory manager 102.
  • the R2DM 440 includes 1) a function of registering a resource information (ID, name, location, keyword, network address, etc.) with the directory manager 102 by a resource service entity (RSE), and 2) a resource service entity (RSE).
  • the directory manager 102 supports the ability to search for topics / devices / applications, and 3) the resource service entity (RSE) subscribes to the topic of the topic directory manager 112.
  • the RSE-to-Application Repository (R2AR) 450 is a reference interface that provides general functions for interworking between a resource service entity (RSE) and an application repository 340.
  • the R2AR 450 supports the ability of a resource service entity (RSE) to download an application from the application repository 340.
  • the Application Repository-to-Directory Manager (AR2DM) 460 is a reference interface that provides general functions for interworking between the application repository 340 and the directory manager 102.
  • the AR2DM 460 supports a function in which the application repository 340 registers with the directory manager 102 the application information (ID, name, URI, category, keyword, etc.) in the application repository 340.
  • the Application-to-Application Repository (A2AR) 470 is a reference interface that provides general functions for interworking between the application A and the application repository 340.
  • A2AR 470 supports the function of uploading application A to application repository 340.
  • the Application-to-Directory Manager (A2DM) 480 is a reference interface that provides general functions for interworking between the application A and the directory manager 102.
  • the A2DM 480 includes: 1) the ability for the application A to retrieve topics, devices, and applications from the directory manager 102; and 2) the application A to the topic directory manager 112 of the directory manager 102. 3) the application (A) supports the ability to subscribe to the topic of the topic directory manager 112.
  • the user searches for the desired other device through the A2R 430 or the A2DM 480 with the application A of the device to obtain information of the other device.
  • the user obtains information of a desired application among applications of other devices in the directory manager 102 through the A2DM 480 as the application A of the device.
  • information of another device obtained previously is used.
  • the user requests the application download to the application store 340 through the A2AR 470 to the application (A) of the device.
  • the download request includes the previously obtained application information.
  • the application store 340 delivers the application to the user's device via the R2AR 450, so that the application is downloaded to the user's device.
  • the resource service entity (RSE) of the device searches for another desired device through the R2R 410 or the R2DM 440 to obtain information of the other device.
  • the resource service entity (RSE) of the device obtains information of a desired application among applications of other devices from the directory manager 102 through the R2DM 440. In order to acquire the application information, information of another device obtained previously is used.
  • the resource service entity (RSE) of the device requests an application download to the application store 340 through the R2AR 450.
  • the download request includes the previously obtained application information.
  • the application store 340 delivers the application to the user's device via the R2AR 450, so that the application is downloaded to the user's device.
  • the user obtains information of a desired application among the applications of the device from the directory manager 102 through the A2DM 480 as the application A of the device.
  • Device information is used to obtain application information.
  • the user requests the application download to the application store 340 through the A2AR 470 to the application (A) of the device.
  • the download request includes the previously obtained application information.
  • the application store 340 delivers the application to the user's device via the R2AR 450, so that the application is downloaded to the user's device.
  • the resource service entity (RSE) of the device obtains the information of the desired application among the applications of the device in the directory manager 102 via the R2DM 440.
  • Device information is used to obtain application information.
  • the resource service entity (RSE) of the device requests an application download to the application store 340 through the R2AR 450.
  • the download request includes the previously obtained application information.
  • the application store 340 delivers the application to the user's device via the R2AR 450, so that the application is downloaded to the user's device.
  • the node holds an application entity (AE) and / or a common service entity (CSE). At this time, the node may have at least one AE. In addition, the node may or may not have a CSE. A node that does not have a CSE is referred to as an application dedicated node (ADN). On the other hand, when having a CSE, it is common to have one CSE, but is not necessarily limited to one.
  • AE application entity
  • CSE common service entity
  • the 'node' may be the 'device' described above
  • the 'AE' may be the 'application (A) or application instance' described above
  • the CSE may be the 'RSE' described above.
  • the node, AE and CSE may be implemented in a different type from the above-described device, application A or application instance and RSE.
  • CSE provides Common Services Functions (CSFs).
  • CSFs provided by the CSE include 1) Application and Service Layer Management (ASM) CSF, 2) Device Firmware Management Function (DFMF) CSF, 3) DIS (Discovery) CSF and 4) GMG (Group Management) CSF. .
  • ASM Application and Service Layer Management
  • DFMF Device Firmware Management Function
  • DIS Discovery
  • GMG Group Management
  • ASM Application and Service Layer Management
  • Nodes include ADNs (Application Dedicated Nodes), ASNs (Application Service Nodes), MNs (Middle Nodes) and INs (Infrastructure Nodes) ) Is included.
  • the CSF manages the life cycle of firmware associated with a device.
  • Device firmware consists of firmware modules and artifacts (eg, configuration / configuration files) held in the device.
  • the device may hold one or more firmware images, providing the capability to manage each firmware image.
  • the firmware life cycle includes actions to download, update, or remove a firmware image. Also, the firmware can download and update in the same task (one task).
  • the CSF can limit the range of information returned to Originator using Filter Criteria provided by Originator.
  • the filter criteria are, for example, keywords, identifiers, locations, semantic information, or a combination thereof.
  • the search request is passed to the address (eg, URI) of the resource on which the search is performed.
  • the DIS CSF retrieves, identifies, and returns matching information for the retrieved resource according to the filter criteria.
  • the success response to the search request may include the retrieved information or the address (eg, URI) of the retrieved resource.
  • Originator can retrieve the resource using the retrieved address.
  • the CSE that receives the search request may forward the search request to CSEs of other ASNs, MNs or INs registered with it.
  • GMG (Group Management) CSF handles group related requests.
  • the 'group' may be the 'topic' described above.
  • the GMG CSF manages groups and their members.
  • the GMG CSF supports bulk operations on various resources of interest and collects the results.
  • GMG CSF enables grouping based access control. If necessary and possible, the GMG CSF can leverage the basic capabilities of existing networks, including broadcasting / multicasting.
  • the GMG CSF may handle requests from AEs and / or other CSEs.
  • Grouping allows an M2M system to perform bulk operations on multiple devices, applications or resources.
  • GMG CSF manages resources and tasks related to grouping.
  • the GMG CSF handles group create, query, update, and delete requests.
  • the AE or CSE may request addition and deletion of group members as well as creation / retrieve / update / deletion of the group.
  • the GMG CSF may create one or more groups in the CSEs of the nodes that make up the M2M system for a particular purpose.
  • specific purposes include access control, device management, fan-out (multicasting) common operations, etc., to a group of devices.
  • the GMG CSF is also a feature that simplifies this particular purpose.
  • the GMG CSF handles retrieval requests for information about groups and related members (eg, URIs, metadata, etc.).
  • GMG CSF manages group membership.
  • the GMG CSF handles requests to add members to or remove members from a list.
  • a member can belong to one or more groups.
  • a group can be a member of another group.
  • the GMG CSF checks that member meets the group's purpose.
  • the specific resource may be, for example, a device / resource providing information, as well as a virtual device / resource generated by the GMG CSF.
  • AEs or CSEs having a common role with respect to access rights are included in the same group.
  • the role may be a service provided by AEs or CSEs, but is not necessarily limited thereto.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

L'invention concerne un système et un procédé M2M ouverts. Un procédé permettant de gérer des ressources selon un mode de réalisation de la présente invention consiste : à enregistrer des ressources présentes dans un premier domaine sur un second domaine ; et à rechercher des métadonnées d'une ressource désirée dans le second domaine. En résultat, la gestion et le partage d'informations peuvent être optimisés, et l'enregistrement et la recherche de ressources peuvent être supportés à une échelle mondiale.
PCT/KR2014/004143 2013-05-09 2014-05-09 Système et procédé m2m ouverts WO2014182115A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US14/889,477 US10091134B2 (en) 2013-05-09 2014-05-09 Open M2M system and method
EP14794803.8A EP2996298A4 (fr) 2013-05-09 2014-05-09 Système et procédé m2m ouverts

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
KR20130052453 2013-05-09
KR10-2013-0052453 2013-05-09
KR10-2013-0095832 2013-08-13
KR20130095832 2013-08-13
KR10-2014-0055320 2014-05-09
KR1020140055320A KR102066294B1 (ko) 2013-05-09 2014-05-09 개방형 m2m 시스템 및 방법

Publications (1)

Publication Number Publication Date
WO2014182115A1 true WO2014182115A1 (fr) 2014-11-13

Family

ID=51867510

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2014/004143 WO2014182115A1 (fr) 2013-05-09 2014-05-09 Système et procédé m2m ouverts

Country Status (1)

Country Link
WO (1) WO2014182115A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080189312A1 (en) * 2007-02-05 2008-08-07 Microsoft Corporation Techniques to manage a taxonomy system for heterogeneous resource domain
US20100325654A1 (en) * 2009-06-17 2010-12-23 General Instrument Corporation Communicating a device descriptor between two devices when registering onto a network
US20120110647A1 (en) * 2010-10-29 2012-05-03 International Business Machines Corporation Managing uniquely tagged items using the internet
KR20120104404A (ko) * 2009-12-29 2012-09-20 제너럴 인스트루먼트 코포레이션 디바이스들의 임시 등록
US20120246319A1 (en) * 2011-03-22 2012-09-27 Electronics And Telecommunications Research Institute System and method for configuring dynamic service network based on netstore

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080189312A1 (en) * 2007-02-05 2008-08-07 Microsoft Corporation Techniques to manage a taxonomy system for heterogeneous resource domain
US20100325654A1 (en) * 2009-06-17 2010-12-23 General Instrument Corporation Communicating a device descriptor between two devices when registering onto a network
KR20120104404A (ko) * 2009-12-29 2012-09-20 제너럴 인스트루먼트 코포레이션 디바이스들의 임시 등록
US20120110647A1 (en) * 2010-10-29 2012-05-03 International Business Machines Corporation Managing uniquely tagged items using the internet
US20120246319A1 (en) * 2011-03-22 2012-09-27 Electronics And Telecommunications Research Institute System and method for configuring dynamic service network based on netstore

Similar Documents

Publication Publication Date Title
WO2014181941A1 (fr) Système m2m ouvert, et procédés de gestion de ressources et d'interface avec ledit système
WO2014101023A1 (fr) Procédé et dispositif de prévention d'un accès illégal à un service
WO2010062048A2 (fr) Procédé et appareil de gestion d'informations d'état d'une interface utilisateur distante
WO2021006616A1 (fr) Procédé pour fournir un service d'identifiant décentralisé relationnel et nœud de chaîne de blocs l'utilisant
WO2014069787A1 (fr) Sécurité par le biais d'orchestrateurs de métadonnées
WO2014069827A1 (fr) Système et procédé pour fournir un service d'analyse de données dans un environnement en nuage
WO2022108427A1 (fr) Système d'outil d'habilitation de confiance intelligent d'environnement de l'ido reposant sur la 5g
WO2010128712A1 (fr) Système et procédé pour un service sémantique
WO2020114184A1 (fr) Procédé, appareil et dispositif de modélisation conjointe, et support de stockage lisible par ordinateur
WO2012128527A2 (fr) Procédé et système pour gérer des informations de contact dans un environnement de réseau domestique upnp
WO2016080787A1 (fr) Système et procédé de gestion de site de construction utilisant un dispositif intelligent
WO2016002996A1 (fr) Procédé et dispositif de blocage d'application de pupille, ainsi que terminal de tuteur, terminal de pupille, programme informatique côté tuteur et programme informatique côté pupille de blocage d'application de pupille
WO2016093652A2 (fr) Procédé de fourniture de service d'album familial permettant d'utiliser un album familial en permettant aux membres d'une famille d'accéder à un serveur cloud par un numéro de téléphone
WO2021107255A1 (fr) Procédé et dispositif de système de gestion d'interopérabilité de système d'identification entre des plateformes ido hétérogènes
WO2014182115A1 (fr) Système et procédé m2m ouverts
WO2016129804A1 (fr) Procédé pour générer une page web sur la base de modèles de comportement de consommateurs et procédé d'utilisation de page web
WO2013062272A2 (fr) Procédé et appareil pour la prestation d'un service de cloud
Namiot et al. On Search Services for Internet of Things
WO2013168911A1 (fr) Procédé de formation d'une ressource de contenant à l'aide d'informations d'identification d'utilisateur, support d'enregistrement et dispositif correspondant
WO2012108678A2 (fr) Appareil et procédé de réglage de disposition relative à un partage de document
WO2011129600A2 (fr) Procédé et système de communication de l'état de distribution d'une ressource xdm dans un environnement xdm
WO2021141458A1 (fr) Procédé et système pour fournir un magasin de l'internet des objets pour partager et vendre des objets virtuels
WO2015056952A1 (fr) Procédé et système d'accès à des ressources
WO2012070865A2 (fr) Système et procédé de partage d'informations
WO2015167198A1 (fr) Appareil et procédé pour collecter des contenus multimédias

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14794803

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 14889477

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2014794803

Country of ref document: EP