WO2016041343A1 - 一种m2m中管理应用资源的方法和注册节点 - Google Patents

一种m2m中管理应用资源的方法和注册节点 Download PDF

Info

Publication number
WO2016041343A1
WO2016041343A1 PCT/CN2015/076189 CN2015076189W WO2016041343A1 WO 2016041343 A1 WO2016041343 A1 WO 2016041343A1 CN 2015076189 W CN2015076189 W CN 2015076189W WO 2016041343 A1 WO2016041343 A1 WO 2016041343A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
resource
cse
identifier
created
Prior art date
Application number
PCT/CN2015/076189
Other languages
English (en)
French (fr)
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 US15/512,762 priority Critical patent/US20170302617A1/en
Priority to EP15841869.9A priority patent/EP3197183B1/en
Publication of WO2016041343A1 publication Critical patent/WO2016041343A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4535—Network directories; Name-to-address mapping using an address exchange platform which sets up a session between two nodes, e.g. rendezvous servers, session initiation protocols [SIP] registrars or H.323 gatekeepers
    • 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/01—Protocols
    • H04L67/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
    • 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/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/63—Routing a service request depending on the request content or context
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/025—Services making use of location information using location based information parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/25—Maintenance of established connections

Definitions

  • This paper deals with machine to machine (M2M) communication, and more particularly relates to a method and registration node for managing application resources in M2M.
  • the M2M communication network consists of an M2M node and a bearer network.
  • the M2M nodes communicate with each other through a bearer network.
  • One M2M node includes at least one Application Entity (AE) or one Common Service Entity (CSE).
  • AE Application Entity
  • CSE Common Service Entity
  • An application entity is a logical unit that executes an M2M application
  • a public service entity is a logical unit that manages and services an M2M application.
  • an M2M node is an application node including an AE, an intermediate node including a CSE, and a base node including a CSE, where the application node is an end execution node, such as a smart meter.
  • the temperature measurement and control sensor, the fire alarm, the smart home appliance, etc. the intermediate node is a middleware that connects the end execution node to the network side server, such as a gateway;
  • the base node is a server on the network side, and the application registered to the base node may be an M2M service.
  • Business management platform is provided.
  • the application entity AE on the application node needs to register with the intermediate node CSE
  • the CSE of the intermediate node needs to register with the CSE of the base node.
  • the CSE on the intermediate node is called the local CSE of the AE on the application node or the registration CSE.
  • the CSE on the base node is called the local CSE of the CSE on the intermediate node or the registration CSE.
  • the registration CSE of the AE on the application node and the registration CSE of the CSE on the intermediate node do not consider the application node carrying the AE resource and the bearer CSE when managing the resources of the AE on the application node and the resources of the CSE on the intermediate node respectively.
  • the intermediate node of the resource does not consider the application node carrying the AE resource and the bearer CSE when managing the resources of the AE on the application node and the resources of the CSE on the intermediate node respectively.
  • the application node and the intermediate node are replaced, and the replaced application node and the intermediate node run the same application as the application node and the intermediate node before the replacement, it is often desirable to retain the application before the replacement.
  • the registered CSE of the AE on the application node deletes the stored AE resources together after learning that the application node is deleted; similarly, in the related art, the middle The CSE registration CSE on the node deletes the CSE resources of the intermediate node stored by itself after learning that the intermediate node is deleted.
  • the replaced application node and the intermediate node need to be re-registered on the CSE when the replacement node is enabled, and the corresponding resources are created, which not only causes the loss of the previous application data, but also the repeated resource creation process. Will affect the efficiency of M2M.
  • the embodiment of the present invention provides a method and a registration node for managing application resources in the M2M, to solve the technical problem of how to associate the AE resource with the node where the CSE resource is associated with the node where the CSE is located on the registered CSE.
  • an embodiment of the present invention provides a method for managing application resources, where the method includes:
  • An application entity (AE) or a public service entity (CSE) sends a CSE sending node resource creation request thereto, and requests an resource for an application node where the AE is located or an intermediate node where the CSE is located;
  • the node resource creation request includes: the AE AE identity or CSE identity of the CSE, node identity, and type of resource creation;
  • the registration CSE creates a node resource for the application node or the intermediate node, and establishes an association relationship between the AE resource that has been created for the AE and the currently created node resource, or establishes a CSE resource that has been created for the CSE.
  • the AE resource includes an AE identifier
  • the CSE resource includes a CSE identifier.
  • the method further includes:
  • the AE When a node replacement occurs, the AE is located at a new application node or the CSE is located at a new intermediate node, the AE or CSE sends a node resource deletion request to the registration CSE;
  • the registration CSE deletes the node resource created for the application node or an intermediate node and The association relationship.
  • the method further includes:
  • the node resource deletion request includes a node replacement indication, the AE identifier, or a CSE identifier;
  • the registration CSE in addition to deleting the node resource created for the application node or the intermediate node, and the association relationship, assigning a replacement node identifier to the AE or CSE, and returning the replacement node identifier to the AE or The CSE, the replacement node identifier corresponds to the AE identifier or the CSE identifier.
  • the method further includes:
  • the AE or CSE After the registration CSE returns the replacement node identifier to the AE or CSE, the AE or CSE sends a node resource creation request to the registration CSE, requesting resources for the new application node or a new intermediate node, the node
  • the resource creation request includes: the replacement node identifier, the node identifier, and a type of the created resource;
  • the registration CSE creates a new node resource for the new application node or the new intermediate node, finds a corresponding AE resource or CSE resource according to the replacement node identifier, and establishes the AE resource and the currently created node resource. Association relationship, or establishing an association relationship between the CSE resource and the currently created node resource.
  • the establishing an association relationship between the AE resource and the currently created node resource includes: establishing an association relationship between the AE resource that includes the AE identifier and the currently created node resource in the attribute;
  • the establishing an association relationship between the CSE resource and the currently created node resource includes: establishing an association relationship between the CSE resource that includes the CSE identifier and the node resource in the attribute.
  • Establishing an association relationship between the AE resource and the currently created node resource including: setting a value of a “node connection” attribute of the AE resource to an address or a node identifier of the currently created node resource;
  • Establishing an association relationship between the CSE resource and the currently created node resource including: setting a value of a “node connection” attribute of the CSE resource to an address of the currently created node resource or Node ID.
  • an embodiment of the present invention further provides a registration node for managing application resources, where the registration node includes: a resource management module and a resource association module, where
  • the resource management module is configured to: after receiving a node resource creation request sent by an application entity (AE) or a public service entity (CSE), create a node resource for an application node where the AE is located or an intermediate node where the CSE is located;
  • the node resource creation request includes: an AE identifier of the AE or a CSE identifier of the CSE, a node identifier, and a type of a created resource;
  • the resource association module is configured to establish an association relationship between the AE resource that has been created for the AE and the currently created node resource, or establish a CSE resource that has been created for the CSE and the currently created node resource.
  • the AE resource includes an AE identifier
  • the CSE resource includes a CSE identifier.
  • the resource management module is further configured to: after receiving a node resource creation request sent from an application entity (AE) or a public service entity (CSE), and receiving a node resource deletion request from the AE or CSE, deleting the The node resource created by the application node or the intermediate node and the association relationship.
  • AE application entity
  • CSE public service entity
  • the node resource deletion request includes a node replacement indication, the AE identifier, or a CSE identifier;
  • the resource management module is further configured to allocate a replacement node identifier to the AE or CSE, and return the replacement node identifier to the AE or CSE, the replacement node identifier and the AE identifier or the CSE identifier correspond.
  • the resource management module is further configured to: after returning the replacement node identifier to the AE or CSE, and receiving a node resource creation request sent by the AE or the CSE for the new application node or the new intermediate node to request the resource,
  • the new application node or the new intermediate node creates a new node resource, and finds a corresponding AE resource or CSE resource according to the replacement node identifier, where the node resource creation request includes: the replacement node identifier, the node identifier, and the resource creation Types of.
  • the resource association module is configured to establish an association relationship between the AE resource that has been created for the AE and the currently created node resource, including:
  • the resource association module is configured to establish an association relationship between the CSE resource that has been created for the CSE and the currently created node resource, including:
  • the resource association module is configured to establish an association relationship between the AE resource that has been created for the AE and the currently created node resource, including:
  • the resource association module establishes an association relationship between the CSE resource and the currently created node resource, including:
  • the value of the "node connection" attribute of the CSE resource is set to the address or node identifier of the currently created node resource.
  • an embodiment of the present invention further provides a computer storage medium, where the computer storage medium stores computer executable instructions, and the computer executable instructions are used to execute the foregoing method.
  • the registration CSE establishes the node resource of the node where the AE or the CSE is located, establishes the association relationship between the AE resource and the established node resource, or establishes the association relationship between the CSE resource and the established node resource, thereby realizing Register the CSE to associate the AE resource with its node and associate the CSE resource with its node.
  • the AE resource or the CSE resource stored in the registered CSE is not deleted.
  • the relationship between the replaced node and the AE resource or the CSE resource is established, so that the replaced node can continue to use the AE resource or the CSE resource before the node replacement, thereby solving the replacement of the application node and/or the intermediate node, and
  • the replaced node wants to keep the running data of the node before the replacement, and avoid the problem of running data loss.
  • 1 is a schematic diagram of the composition of an M2M communication network in the related art
  • FIG. 2 is a flowchart of a method for managing application resources according to the embodiment
  • FIG. 3 is a block diagram of a component of a registration node for managing application resources according to the embodiment.
  • FIG. 2 is a flowchart of a method for managing application resources according to an embodiment.
  • the application entity (AE) of the application node or the public service entity (CSE) of the intermediate node sends a node resource creation request to the registered CSE of the application node, and requests the resource for the intermediate node where the application node or the CSE where the AE is located;
  • the node resource creation request includes: an AE identifier of the AE or a CSE identifier of the CSE, a node identifier, and a type of the created resource, where the type of the created resource is a node type;
  • the registration CSE creates a node resource for the application node or the intermediate node, and establishes an association relationship between the AE resource that has been created for the AE and the currently created node resource, or establishes a CSE that has been created for the CSE.
  • the attribute of the AE resource includes an AE identifier, and the attribute of the CSE resource includes a CSE identifier;
  • the registration CSE After the registration CSE receives the resource creation request, the resource of the node type is created; the node identifier attribute is set for the node resource, and the attribute value is the node identifier carried in the resource creation request;
  • the registration CSE establishes an association between the AE resource and the currently created node resource. Relationships, including:
  • the registration CSE establishes an association relationship between the CSE resource and the currently created node resource, including:
  • the registration CSE establishes an association relationship between the AE resource and the currently created node resource, including:
  • the registration CSE establishes an association relationship between the CSE resource and the currently created node resource, including:
  • the node resource deletion request includes: a node replacement indication, the AE or CSE identifier, and an address of the replaced node resource;
  • the registration CSE deletes the node resource created by the application node or an intermediate node, and the association relationship;
  • the registration CSE finds the node resource to be deleted according to the address of the replacement node resource
  • association relationship created by the registration CSE deletion includes:
  • the S205 registration CSE allocates a replacement node identifier to the AE or CSE, and returns the replacement node identifier to the AE or CSE, where the replacement node identifier corresponds to the AE identifier or the CSE identifier;
  • the AE or CSE sends a node resource creation request to the registration CSE, requesting resources for the new application node or a new intermediate node;
  • the node resource creation request includes: the replacement node identifier, the node identifier, and a type of the created resource;
  • the registration CSE creates a new node resource for the new application node or a new intermediate node, and finds a corresponding AE resource or CSE resource according to the replacement node identifier, and establishes the AE resource and the currently created node resource.
  • the association relationship or the association relationship between the CSE resource and the currently created node resource is not limited to:
  • the registration CSE establishes the node resource of the node where the AE or the CSE is located, establishes the association relationship between the AE resource and the established node resource, or establishes the association relationship between the CSE resource and the established node resource, thereby realizing Register the CSE to associate the AE resource with its node and associate the CSE resource with its node.
  • the AE resource or the CSE resource stored in the registered CSE is not deleted, but the relationship between the replaced node and the AE resource or the CSE resource is established.
  • the replaced node can continue to use the AE resource or CSE resource before the node replacement, and solve the problem of avoiding running data loss when the application node and/or the intermediate node are replaced, and the replaced node wants to retain the node running data before the replacement.
  • the problem can continue to use the AE resource or CSE resource before the node replacement, and solve the problem of avoiding running data loss when the application node and/or the intermediate node are replaced, and the replaced node wants to retain the node running data before the replacement. The problem.
  • FIG. 3 is a block diagram of a component of a registration node for managing application resources according to the embodiment.
  • the registration node includes: a resource management module and a resource association module, where:
  • the resource management module is configured to: after receiving a node resource creation request sent by an application entity (AE) or a public service entity (CSE), create a node resource for an application node where the AE is located or an intermediate node where the CSE is located;
  • AE application entity
  • CSE public service entity
  • the node resource creation request includes: an AE identifier of the AE or a CSE identifier of the CSE, a node identifier, and a type of a created resource; the type of the created resource is a node type;
  • the resource association module is configured to establish an association relationship between the AE resource that has been created for the AE and the currently created node resource, or establish a CSE resource that has been created for the CSE and the current The association relationship of the created node resource; the attribute of the AE resource includes an AE identifier, and the attribute of the CSE resource includes a CSE identifier;
  • the resource association module is configured to establish an association relationship between the AE resource that has been created for the AE and the currently created node resource, including:
  • the resource association module is configured to establish an association relationship between the CSE resource that has been created for the CSE and the currently created node resource, including:
  • the resource association module is configured to establish an association relationship between the AE resource that has been created for the AE and the currently created node resource, including:
  • the resource association module is configured to establish an association relationship between the CSE resource and the currently created node resource, including:
  • the value of the "node connection" attribute of the CSE resource is set to the address or node identifier of the currently created node resource.
  • the resource management module is further configured to: after receiving a node resource creation request sent from an application entity (AE) or a public service entity (CSE), and receiving a node resource deletion request from the AE or CSE, deleting the Determining, by the application node or the node, the node resource and the association relationship; the node resource deletion request includes a node replacement indication, the AE identifier, or a CSE identifier;
  • AE application entity
  • CSE public service entity
  • the foregoing resource management module is configured to delete the association relationship, including:
  • the resource management module is further configured to: delete the node resource created for the application node or the intermediate node, and the association relationship, and set a replacement node identifier for the AE or CSE, and replace the node
  • the identifier is returned to the AE or CSE, and the replacement node identifier is Corresponding to the AE identifier or the CSE identifier;
  • the resource management module is further configured to: after returning the replacement node identifier to the AE or the CSE, and receiving a node resource creation request sent by the AE or the CSE for the new application node or the new intermediate node to request the resource, The new application node or the new intermediate node creates a new node resource; and finds a corresponding AE resource or CSE resource according to the replacement node identifier.
  • a node resource creation request requesting a resource for a new application node or a new intermediate node includes: an AE identifier or a CSE identifier, a node identifier, and a type of the created resource.
  • the registration CSE establishes the node resource of the node where the AE or the CSE is located, establishes the association relationship between the AE resource and the established node resource, or establishes the association relationship between the CSE resource and the established node resource, thereby realizing Register the CSE to associate the AE resource with its node and associate the CSE resource with its node.
  • the AE resource or the CSE resource stored in the registered CSE is not deleted, but the relationship between the replaced node and the AE resource or the CSE resource is established.
  • the replaced node can continue to use the AE resource or CSE resource before the node replacement, and solve the problem of avoiding running data loss when the application node and/or the intermediate node are replaced, and the replaced node wants to retain the node running data before the replacement.
  • the problem can continue to use the AE resource or CSE resource before the node replacement, and solve the problem of avoiding running data loss when the application node and/or the intermediate node are replaced, and the replaced node wants to retain the node running data before the replacement. The problem.
  • the foregoing technical solution achieves the purpose of associating the CSE resource with the node where the AE resource and its node are located on the registered CSE.
  • the relationship between the replaced node and the AE resource or the CSE resource is established, so that the replaced node can continue to use the AE resource or the CSE resource before the node replacement.
  • the problem of running data loss is avoided in the case where the application node and/or the intermediate node are replaced, and the replaced node wishes to retain the node running data before the replacement.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种M2M中管理应用资源的方法和注册节点，其中，方法包括：AE或CSE向其注册CSE发送节点资源创建请求，为AE所在的应用节点或CSE所在的中间节点请求资源；节点资源创建请求包括：AE的AE标识或CSE的CSE标识、节点标识和创建资源的类型；注册CSE为应用节点或中间节点创建节点资源，并建立已为AE创建的AE资源和当前创建的节点资源的关联关系，或者建立已为CSE创建的CSE资源和当前创建的节点资源的关联关系，AE资源的属性中包括AE标识，CSE资源的属性中包括CSE标识。上述技术方案实现了在注册CSE上将AE资源与其所在节点，将CSE资源与其所在节点进行关联。

Description

一种M2M中管理应用资源的方法和注册节点 技术领域
本文涉及机器对机器(machine to machine，M2M)通信，尤其涉及一种M2M中管理应用资源的方法和注册节点。
背景技术
M2M通信网络由M2M节点和承载网络组成。M2M节点通过承载网络实现互相通信，一个M2M节点至少包含一个应用实体(Application Entity，AE)或者一个公共业务实体(CSE)。应用实体是执行M2M应用的逻辑单元，公共业务实体是对M2M应用进行管理和服务的逻辑单元。
图1为相关技术中的M2M通信网络组成示意图，图中M2M节点为包含AE的应用节点、包含CSE的中间节点和包含CSE的基础节点，其中，应用节点是末端的执行节点，例如智能电表，温度测控传感器，火警报警器，智能家电等等；中间节点是连接末端执行节点到网络侧服务器的中间件，例如网关；基础节点是网络侧的服务器，注册到基础节点上的应用可以是M2M服务商的管理平台。
由于M2M应用之间的通信是通过公共业务实体CSE之间的交互来实现的，因此，应用节点上的应用实体AE需要向中间节点CSE注册，中间节点的CSE需要向基础节点的CSE注册。中间节点上的CSE叫做应用节点上的AE的本地CSE或者注册CSE，基础节点上的CSE叫做中间节点上的CSE的本地CSE或者注册CSE。
相关技术中，应用节点上AE的注册CSE和中间节点上CSE的注册CSE在分别管理应用节点上AE的资源和中间节点上CSE的资源时，没有考虑承载所述AE资源的应用节点和承载CSE资源的中间节点。
此外，当更换应用节点和中间节点，且更换后的应用节点和中间节点运行与更换前的应用节点和中间节点相同的应用时，往往希望保留更换前的应 用节点和中间节点上该应用的运行数据，但是相关技术中，应用节点上AE的注册CSE在获知应用节点删除后，会将自身存储的AE资源一并删除；同样的，相关技术中，中间节点上CSE的注册CSE在获知中间节点被删除后，会将自身存储的中间节点的CSE资源一并删除。这样，在执行上述的更换节点操作后，更换后的应用节点和中间节点启用时需要重新在CSE上进行注册，创建相应的资源，不仅会造成之前应用数据的丢失，而且重复的资源创建过程也会影响M2M的工作效率。
发明内容
本发明实施例提供了一种M2M中管理应用资源的方法和注册节点，以解决如何在注册CSE上将AE资源与其所在节点，将CSE资源与其所在节点进行关联的技术问题。
为解决上述技术问题，本发明实施例提供了一种管理应用资源的方法，所述方法包括：
应用实体(AE)或公共业务实体(CSE)向其注册CSE发送节点资源创建请求，为所述AE所在的应用节点或CSE所在的中间节点请求资源；所述节点资源创建请求包括：所述AE的AE标识或所述CSE的CSE标识、节点标识和创建资源的类型；
所述注册CSE为所述应用节点或中间节点创建节点资源，并建立已为所述AE创建的AE资源和当前创建的所述节点资源的关联关系，或者建立已为所述CSE创建的CSE资源和当前创建的所述节点资源的关联关系，所述AE资源的属性中包括AE标识，所述CSE资源的属性中包括CSE标识。
可选地，所述方法还包括：
所述AE或CSE向所述注册CSE发送节点资源创建请求，为所述应用节点或中间节点请求资源之后，
当发生节点更换，所述AE位于新应用节点或CSE位于新中间节点时，所述AE或CSE向所述注册CSE发送节点资源删除请求；
所述注册CSE删除为所述应用节点或中间节点创建的所述节点资源以及 所述关联关系。
可选地,所述方法还包括：
所述节点资源删除请求包含节点更换指示、所述AE标识或CSE标识；
注册CSE除删除为所述应用节点或中间节点创建的所述节点资源以及所述关联关系外，还为所述AE或CSE分配更换节点标识，并将所述更换节点标识返回给所述AE或CSE，所述更换节点标识与所述AE标识或所述CSE标识对应。
可选地，所述方法还包括：
所述注册CSE将所述更换节点标识返回给所述AE或CSE之后，所述AE或CSE向所述注册CSE发送节点资源创建请求，为所述新应用节点或新中间节点请求资源，该节点资源创建请求包括：所述更换节点标识、节点标识和创建资源的类型；
所述注册CSE为所述新应用节点或新中间节点创建新的节点资源，根据所述更换节点标识找到对应的AE资源或CSE资源，并建立所述AE资源和当前创建的所述节点资源的关联关系，或者建立所述CSE资源和当前创建的所述节点资源的关联关系。
可选地，
所述建立所述AE资源和当前创建的所述节点资源的关联关系，包括：建立属性中包含所述AE标识的AE资源和当前创建的所述节点资源的关联关系；
所述建立所述CSE资源和当前创建的所述节点资源的关联关系，包括：建立属性中包含所述CSE标识的CSE资源和所述节点资源的关联关系。
可选地：
建立所述AE资源和当前创建的所述节点资源的关联关系，包括：设置所述AE资源的“节点连接”属性的值为当前创建的所述节点资源的地址或节点标识；
建立所述CSE资源和当前创建的所述节点资源的关联关系，包括：设置所述CSE资源的“节点连接”属性的值为当前创建的所述节点资源的地址或 节点标识。
为解决上述技术问题，本发明实施例还提供了一种管理应用资源的注册节点，所述注册节点包括：资源管理模块以及资源关联模块，其中
所述资源管理模块，设置为接收到来自应用实体(AE)或公共业务实体(CSE)发送的节点资源创建请求后，为所述AE所在的应用节点或CSE所在的中间节点创建节点资源；所述节点资源创建请求包括：所述AE的AE标识或所述CSE的CSE标识、节点标识和创建资源的类型；
所述资源关联模块，设置为建立已为所述AE创建的AE资源和当前创建的所述节点资源的关联关系，或者建立已为所述CSE创建的CSE资源和当前创建的所述节点资源的关联关系，所述AE资源的属性中包括AE标识，所述CSE资源的属性中包括CSE标识。
可选地，
所述资源管理模块，还设置为接收到来自应用实体(AE)或公共业务实体(CSE)发送的节点资源创建请求后，又接收到来自所述AE或CSE的节点资源删除请求时，删除为所述应用节点或中间节点创建的所述节点资源以及所述关联关系。
可选地，
所述节点资源删除请求包含节点更换指示、所述AE标识或CSE标识；
所述资源管理模块，还设置为为所述AE或CSE分配更换节点标识，并将所述更换节点标识返回给所述AE或CSE，所述更换节点标识与所述AE标识或所述CSE标识对应。
可选地，
所述资源管理模块，还设置为将所述更换节点标识返回给所述AE或CSE之后，又接收到AE或CSE发送的为新应用节点或新中间节点请求资源的节点资源创建请求时，为所述新应用节点或新中间节点创建新的节点资源，以及根据所述更换节点标识找到对应的AE资源或CSE资源，该节点资源创建请求包括：所述更换节点标识、节点标识和创建资源的类型。
可选地，
所述资源关联模块，设置为建立已为所述AE创建的AE资源和当前创建的所述节点资源的关联关系，包括：
建立属性中包含所述AE标识的AE资源和当前创建的所述节点资源的关联关系；
所述资源关联模块，设置为建立已为所述CSE创建的CSE资源和当前创建的所述节点资源的关联关系，包括：
建立属性中包含所述CSE标识的CSE资源和所述节点资源的关联关系。
可选地，
所述资源关联模块，设置为建立已为所述AE创建的AE资源和当前创建的所述节点资源的关联关系，包括：
设置所述AE资源的“节点连接”属性的值为当前创建的所述节点资源的地址或节点标识；
所述资源关联模块，建立所述CSE资源和当前创建的所述节点资源的关联关系，包括：
设置所述CSE资源的“节点连接”属性的值为当前创建的所述节点资源的地址或节点标识。
为解决上述技术问题，本发明实施例还提供了一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，所述计算机可执行指令用于执行上述的方法。
上述技术方案中，注册CSE建立了AE或CSE所在节点的节点资源，并建立了AE资源和建立的节点资源的关联关系，或建立了CSE资源和建立的节点资源的关联关系，从而实现了在注册CSE上将AE资源与其所在节点，将CSE资源与其所在节点进行关联的目的。此外，上述技术方案中，当更换AE或CSE所在的节点时，在注册CSE中存储的AE资源或CSE资源不被删 除，而是建立更换后的节点与AE资源或CSE资源的关联关系，使得更换后的节点能够继续使用节点更换前的AE资源或CSE资源，解决了在更换应用节点和/或中间节点，且更换后的节点希望保留更换前的节点运行数据的情况下，避免运行数据丢失的问题。
附图概述
图1为相关技术中M2M通信网络组成示意图；
图2为本实施例的管理应用资源的方法流程图；
图3为本实施例的管理应用资源的注册节点组成模块图。
本发明的较佳实施方式
下文中将结合附图对本发明的实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
图2为本实施例的管理应用资源的方法流程图。
S201位于应用节点的应用实体(AE)或位于中间节点的公共业务实体(CSE)向自身的注册CSE发送节点资源创建请求，为所述AE所在的应用节点或CSE所在的中间节点请求资源；
该节点资源创建请求包括：AE的AE标识或CSE的CSE标识、节点标识和创建资源的类型，所述创建资源的类型为节点类型；
S202所述注册CSE为所述应用节点或中间节点创建节点资源，并建立已为所述AE创建的AE资源和当前创建的所述节点资源的关联关系，或者建立已为所述CSE创建的CSE资源和当前创建的所述节点资源的关联关系；
所述AE资源的属性中包括AE标识，所述CSE资源的属性中包括CSE标识；
注册CSE接收到资源创建请求后，创建节点类型的资源；可为该节点资源设置“节点标识”属性，其属性值为资源创建请求中携带的节点标识；
可选地，注册CSE建立所述AE资源和当前创建的所述节点资源的关联 关系，包括：
建立属性中包含所述AE标识的AE资源和当前创建的所述节点资源的关联关系；
可选地，注册CSE建立所述CSE资源和当前创建的所述节点资源的关联关系，包括：
建立属性中包含所述CSE标识的CSE资源和所述节点资源的关联关系。
可选地，注册CSE建立所述AE资源和当前创建的所述节点资源的关联关系，包括：
设置所述AE资源的“节点连接”属性的值为当前创建的所述节点资源的地址或节点标识；
可选地，注册CSE建立所述CSE资源和当前创建的所述节点资源的关联关系，包括：
设置所述CSE资源的“节点连接”属性的值为当前创建的所述节点资源的地址或节点标识；
S203当发生节点更换，所述AE位于新应用节点或CSE位于新中间节点时，所述AE或CSE向所述注册CSE发送节点资源删除请求；
所述节点资源删除请求包括：节点更换指示、所述AE或CSE标识、被更换的节点资源的地址；
S204所述注册CSE删除为所述应用节点或中间节点创建的所述节点资源以及所述关联关系；
注册CSE根据所述更换节点资源的地址找到要删除的节点资源；
可选地，注册CSE删除创建的所述关联关系包括：
删除AE或CSE资源的节点连接属性；或，将该AE或CSE资源的节点连接属性的值设置为空；
S205注册CSE为所述AE或CSE分配更换节点标识，并将所述更换节点标识返回给所述AE或CSE，所述更换节点标识与所述AE标识或所述CSE标识对应；
S206所述AE或CSE向所述注册CSE发送节点资源创建请求，为所述新应用节点或新中间节点请求资源；
该节点资源创建请求包括：所述更换节点标识、节点标识和创建资源的类型；
S207所述注册CSE为所述新应用节点或新中间节点创建新的节点资源，根据所述更换节点标识找到对应的AE资源或CSE资源，并建立所述AE资源和当前创建的所述节点资源的关联关系，或者建立所述CSE资源和当前创建的所述节点资源的关联关系。
上述技术方案中，注册CSE建立了AE或CSE所在节点的节点资源，并建立了AE资源和建立的节点资源的关联关系，或建立了CSE资源和建立的节点资源的关联关系，从而实现了在注册CSE上将AE资源与其所在节点，将CSE资源与其所在节点进行关联的目的。此外，上述技术方案中，当更换AE或CSE所在的节点时，在注册CSE中存储的AE资源或CSE资源不被删除，而是建立更换后的节点与AE资源或CSE资源的关联关系，使得更换后的节点能够继续使用节点更换前的AE资源或CSE资源，解决了在更换应用节点和/或中间节点，且更换后的节点希望保留更换前的节点运行数据的情况下，避免运行数据丢失的问题。
图3为本实施例的管理应用资源的注册节点组成模块图。
所述注册节点包括：资源管理模块以及资源关联模块，其中：
所述资源管理模块，设置为接收到来自应用实体(AE)或公共业务实体(CSE)发送的节点资源创建请求后，为所述AE所在的应用节点或CSE所在的中间节点创建节点资源；
所述节点资源创建请求包括：所述AE的AE标识或所述CSE的CSE标识、节点标识和创建资源的类型；所述创建资源的类型为节点类型；
所述资源关联模块，设置为建立已为所述AE创建的AE资源和当前创建的所述节点资源的关联关系，或者建立已为所述CSE创建的CSE资源和当前 创建的所述节点资源的关联关系；所述AE资源的属性中包括AE标识，所述CSE资源的属性中包括CSE标识；
可选地，所述资源关联模块，设置为建立已为所述AE创建的AE资源和当前创建的所述节点资源的关联关系，包括：
建立属性中包含所述AE标识的AE资源和当前创建的所述节点资源的关联关系；
所述资源关联模块，设置为建立已为所述CSE创建的CSE资源和当前创建的所述节点资源的关联关系，包括：
建立属性中包含所述CSE标识的CSE资源和所述节点资源的关联关系。
可选地，所述资源关联模块，设置为建立已为所述AE创建的AE资源和当前创建的所述节点资源的关联关系，包括：
设置所述AE资源的“节点连接”属性的值为当前创建的所述节点资源的地址或节点标识；
所述资源关联模块，设置为建立所述CSE资源和当前创建的所述节点资源的关联关系，包括：
设置所述CSE资源的“节点连接”属性的值为当前创建的所述节点资源的地址或节点标识。
上述资源管理模块，还设置为接收到来自应用实体(AE)或公共业务实体(CSE)发送的节点资源创建请求后，又接收到来自所述AE或CSE的节点资源删除请求时，删除为所述应用节点或中间节点创建的所述节点资源以及所述关联关系；所述节点资源删除请求包含节点更换指示、所述AE标识或CSE标识；
可选地，上述资源管理模块，设置为删除所述关联关系，包括：
删除AE或CSE资源的节点连接属性；或，将该AE或CSE资源的节点连接属性的值设置为空；
上述资源管理模块，除设置为删除为所述应用节点或中间节点创建的所述节点资源以及所述关联关系外，还设置为为所述AE或CSE分配更换节点标识，并将所述更换节点标识返回给所述AE或CSE，所述更换节点标识与 所述AE标识或所述CSE标识对应；
上述资源管理模块，还设置为将所述更换节点标识返回给所述AE或CSE之后，又接收到AE或CSE发送的为新应用节点或新中间节点请求资源的节点资源创建请求时，为所述新应用节点或新中间节点创建新的节点资源；以及根据所述更换节点标识找到对应的AE资源或CSE资源。
为新应用节点或新中间节点请求资源的节点资源创建请求包括：AE标识或CSE标识、节点标识和创建资源的类型。
上述技术方案中，注册CSE建立了AE或CSE所在节点的节点资源，并建立了AE资源和建立的节点资源的关联关系，或建立了CSE资源和建立的节点资源的关联关系，从而实现了在注册CSE上将AE资源与其所在节点，将CSE资源与其所在节点进行关联的目的。此外，上述技术方案中，当更换AE或CSE所在的节点时，在注册CSE中存储的AE资源或CSE资源不被删除，而是建立更换后的节点与AE资源或CSE资源的关联关系，使得更换后的节点能够继续使用节点更换前的AE资源或CSE资源，解决了在更换应用节点和/或中间节点，且更换后的节点希望保留更换前的节点运行数据的情况下，避免运行数据丢失的问题。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序来指令相关硬件完成，所述程序可以存储于计算机可读存储介质中，如只读存储器、磁盘或光盘等。可选地，上述实施例的全部或部分步骤也可以使用一个或多个集成电路来实现，相应地，上述实施例中的各模块/单元可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。本发明不限制于任何特定形式的硬件和软件的结合。
需要说明的是，本发明还可有其他多种实施例，在不背离本发明精神及其实质的情况下，熟悉本领域的技术人员可根据本发明作出各种相应的改变和变形，但这些相应的改变和变形都应属于本发明所附的权利要求的保护范 围。
工业实用性
上述技术方案实现了在注册CSE上将AE资源与其所在节点，将CSE资源与其所在节点进行关联的目的。此外，上述技术方案中，当更换AE或CSE所在的节点时，通过建立更换后的节点与AE资源或CSE资源的关联关系，使得更换后的节点能够继续使用节点更换前的AE资源或CSE资源，避免了在更换应用节点和/或中间节点，且更换后的节点希望保留更换前的节点运行数据的情况下，运行数据丢失的问题。

Claims (13)

  1. 一种管理应用资源的方法，所述方法包括：
    应用实体(AE)或公共业务实体(CSE)向其注册CSE发送节点资源创建请求，为所述AE所在的应用节点或CSE所在的中间节点请求资源；所述节点资源创建请求包括：所述AE的AE标识或所述CSE的CSE标识、节点标识和创建资源的类型；
    所述注册CSE为所述应用节点或中间节点创建节点资源，并建立已为所述AE创建的AE资源和当前创建的所述节点资源的关联关系，或者建立已为所述CSE创建的CSE资源和当前创建的所述节点资源的关联关系，所述AE资源的属性中包括AE标识，所述CSE资源的属性中包括CSE标识。
  2. 如权利要求1所述的方法，所述方法还包括：
    所述AE或CSE向所述注册CSE发送节点资源创建请求，为所述应用节点或中间节点请求资源之后，当发生节点更换，所述AE位于新应用节点或CSE位于新中间节点时，所述AE或CSE向所述注册CSE发送节点资源删除请求；
    所述注册CSE删除为所述应用节点或中间节点创建的所述节点资源以及所述关联关系。
  3. 如权利要求2所述的方法，所述方法还包括：
    所述节点资源删除请求包含节点更换指示、所述AE标识或CSE标识；
    注册CSE除删除为所述应用节点或中间节点创建的所述节点资源以及所述关联关系外，还为所述AE或CSE分配更换节点标识，并将所述更换节点标识返回给所述AE或CSE，所述更换节点标识与所述AE标识或所述CSE标识对应。
  4. 如权利要求3所述的方法，所述方法还包括：
    所述注册CSE将所述更换节点标识返回给所述AE或CSE之后，所述AE或CSE向所述注册CSE发送节点资源创建请求，为所述新应用节点或新中间节点请求资源，该节点资源创建请求包括：所述更换节点标识、节点标识和创建资源的类型；
    所述注册CSE为所述新应用节点或新中间节点创建新的节点资源，根据所述更换节点标识找到对应的AE资源或CSE资源，并建立所述AE资源和当前创建的所述节点资源的关联关系，或者建立所述CSE资源和当前创建的所述节点资源的关联关系。
  5. 如权利要求1或2或3或4所述的方法，其中
    所述建立所述AE资源和当前创建的所述节点资源的关联关系，包括：
    建立属性中包含所述AE标识的AE资源和当前创建的所述节点资源的关联关系；
    所述建立所述CSE资源和当前创建的所述节点资源的关联关系，包括：
    建立属性中包含所述CSE标识的CSE资源和所述节点资源的关联关系。
  6. 如权利要求5所述的方法，其中：
    建立所述AE资源和当前创建的所述节点资源的关联关系，包括：
    设置所述AE资源的“节点连接”属性的值为当前创建的所述节点资源的地址或节点标识；
    建立所述CSE资源和当前创建的所述节点资源的关联关系，包括：
    设置所述CSE资源的“节点连接”属性的值为当前创建的所述节点资源的地址或节点标识。
  7. 一种管理应用资源的注册节点，所述注册节点包括：资源管理模块以及资源关联模块，其中
    所述资源管理模块，设置为接收到来自应用实体(AE)或公共业务实体(CSE)发送的节点资源创建请求后，为所述AE所在的应用节点或CSE所在的中间节点创建节点资源；所述节点资源创建请求包括：所述AE的AE标识或所述CSE的CSE标识、节点标识和创建资源的类型；
    所述资源关联模块，设置为建立已为所述AE创建的AE资源和当前创建的所述节点资源的关联关系，或者建立已为所述CSE创建的CSE资源和当前创建的所述节点资源的关联关系，所述AE资源的属性中包括AE标识，所述CSE资源的属性中包括CSE标识。
  8. 如权利要求7所述的注册节点，
    所述资源管理模块，还设置为接收到来自应用实体(AE)或公共业务实体(CSE)发送的节点资源创建请求后，又接收到来自所述AE或CSE的节点资源删除请求时，删除为所述应用节点或中间节点创建的所述节点资源以及所述关联关系。
  9. 如权利要求8所述的注册节点，
    其中，所述节点资源删除请求包含节点更换指示、所述AE标识或CSE标识；
    所述资源管理模块，还设置为为所述AE或CSE分配更换节点标识，并将所述更换节点标识返回给所述AE或CSE，所述更换节点标识与所述AE标识或所述CSE标识对应。
  10. 如权利要求9所述的注册节点，
    所述资源管理模块，还设置为将所述更换节点标识返回给所述AE或CSE之后，又接收到AE或CSE发送的为新应用节点或新中间节点请求资源的节点资源创建请求时，为所述新应用节点或新中间节点创建新的节点资源，以及根据所述更换节点标识找到对应的AE资源或CSE资源，该节点资源创建请求包括：所述更换节点标识、节点标识和创建资源的类型。
  11. 如权利要求7或8或9或10所述的注册节点，其中，
    所述资源关联模块，是设置为通过以下方式实现建立已为所述AE创建的AE资源和当前创建的所述节点资源的关联关系：
    建立属性中包含所述AE标识的AE资源和当前创建的所述节点资源的关联关系；
    所述资源关联模块，是设置为通过以下方式实现建立已为所述CSE创建的CSE资源和当前创建的所述节点资源的关联关系：
    建立属性中包含所述CSE标识的CSE资源和所述节点资源的关联关系。
  12. 如权利要求11所述的注册节点，其中，
    所述资源关联模块，是设置为通过以下方式实现建立已为所述AE创建 的AE资源和当前创建的所述节点资源的关联关系：
    设置所述AE资源的“节点连接”属性的值为当前创建的所述节点资源的地址或节点标识；
    所述资源关联模块，是设置为通过以下方式实现建立所述CSE资源和当前创建的所述节点资源的关联关系：
    设置所述CSE资源的“节点连接”属性的值为当前创建的所述节点资源的地址或节点标识。
  13. 一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求1～6中任一项所述的方法。
PCT/CN2015/076189 2014-09-19 2015-04-09 一种m2m中管理应用资源的方法和注册节点 WO2016041343A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US15/512,762 US20170302617A1 (en) 2014-09-19 2015-04-09 Method and Registration Node for Managing Application Resource in Machine to Machine (M2M)
EP15841869.9A EP3197183B1 (en) 2014-09-19 2015-04-09 Method for managing application resources and registered node in m2m

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410484261.5A CN105491507B (zh) 2014-09-19 2014-09-19 一种m2m中管理应用资源的方法和注册节点
CN201410484261.5 2014-09-19

Publications (1)

Publication Number Publication Date
WO2016041343A1 true WO2016041343A1 (zh) 2016-03-24

Family

ID=55532510

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/076189 WO2016041343A1 (zh) 2014-09-19 2015-04-09 一种m2m中管理应用资源的方法和注册节点

Country Status (4)

Country Link
US (1) US20170302617A1 (zh)
EP (1) EP3197183B1 (zh)
CN (1) CN105491507B (zh)
WO (1) WO2016041343A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107317785A (zh) * 2016-04-26 2017-11-03 京东方科技集团股份有限公司 应用实体创建资源和注册方法、通信节点设备及终端设备
CN107370782A (zh) * 2016-05-13 2017-11-21 京东方科技集团股份有限公司 对设备进行操作的方法、控制装置和代理装置
US11375354B2 (en) 2016-12-12 2022-06-28 Boe Technology Group Co., Ltd. Method for resource creation and registration of application entity, and communication node device and terminal device

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107124688B (zh) * 2016-02-25 2020-07-07 中兴通讯股份有限公司 一种公共业务实体资源管理的方法、装置及通信网络节点
CN105929597B (zh) 2016-05-20 2021-05-25 京东方科技集团股份有限公司 背光源及其制作方法、显示基板、显示装置及其显示方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110200052A1 (en) * 2010-02-15 2011-08-18 Fabio Mungo Machine to machine architecture
CN103299601A (zh) * 2010-11-19 2013-09-11 交互数字专利控股公司 用于资源通告及去通告的机器对机器（m2m）接口过程
CN103618800A (zh) * 2013-12-05 2014-03-05 华为技术有限公司 订阅通知的实现方法和装置

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101282355A (zh) * 2008-03-17 2008-10-08 张建中 一种本地资源使用远程资源服务的方法和装置以及系统
CN102480501A (zh) * 2010-11-26 2012-05-30 华为终端有限公司 应用资源下载方法及相关设备
CN102740466B (zh) * 2011-04-01 2016-03-02 中兴通讯股份有限公司 物联网中对资源进行操作的方法及装置
EP2875669B1 (en) * 2012-06-29 2017-09-06 Telefónica, S.A. A method and a system for providing backhaul load information for assigning radio resources to small cells in 3gpp networks
US9655159B2 (en) * 2012-08-31 2017-05-16 Qualcomm Incorporated Managing guaranteed bit rate quality of service resource allocation based on guaranteed bit rate data activity on a link
WO2015013685A1 (en) * 2013-07-25 2015-01-29 Convida Wireless, Llc End-to-end m2m service layer sessions
KR20160091314A (ko) * 2013-11-29 2016-08-02 엘지전자 주식회사 무선 통신 시스템에서 서비스 구독 리소스 기반 인증 방법

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110200052A1 (en) * 2010-02-15 2011-08-18 Fabio Mungo Machine to machine architecture
CN103299601A (zh) * 2010-11-19 2013-09-11 交互数字专利控股公司 用于资源通告及去通告的机器对机器（m2m）接口过程
CN103618800A (zh) * 2013-12-05 2014-03-05 华为技术有限公司 订阅通知的实现方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3197183A4 *

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107317785A (zh) * 2016-04-26 2017-11-03 京东方科技集团股份有限公司 应用实体创建资源和注册方法、通信节点设备及终端设备
EP3451603A4 (en) * 2016-04-26 2019-11-27 BOE Technology Group Co., Ltd. METHOD FOR THE PRODUCTION AND REGISTRATION OF RESOURCES OF AN APPLICATION UNIT, COMMUNICATION KNOB DEVICE AND DEVICE DEVICE
CN107317785B (zh) * 2016-04-26 2021-04-23 京东方科技集团股份有限公司 应用实体创建资源和注册方法、通信节点设备及终端设备
CN107370782A (zh) * 2016-05-13 2017-11-21 京东方科技集团股份有限公司 对设备进行操作的方法、控制装置和代理装置
EP3457667A4 (en) * 2016-05-13 2019-12-18 Boe Technology Group Co. Ltd. METHOD, CONTROL DEVICE AND AGENT FOR THE OPERATION OF A PLANT
CN107370782B (zh) * 2016-05-13 2021-08-31 京东方科技集团股份有限公司 对设备进行操作的方法、控制装置和代理装置
US11375354B2 (en) 2016-12-12 2022-06-28 Boe Technology Group Co., Ltd. Method for resource creation and registration of application entity, and communication node device and terminal device

Also Published As

Publication number Publication date
EP3197183B1 (en) 2018-12-26
CN105491507B (zh) 2020-10-27
EP3197183A4 (en) 2017-07-26
US20170302617A1 (en) 2017-10-19
CN105491507A (zh) 2016-04-13
EP3197183A1 (en) 2017-07-26

Similar Documents

Publication Publication Date Title
US10897431B2 (en) Cloud resource processing method and physical node
US10148511B2 (en) Managing servers based on pairing keys to implement an administrative domain-wide policy
WO2016041343A1 (zh) 一种m2m中管理应用资源的方法和注册节点
CN108093094B (zh) 数据库实例访问方法、装置、系统、存储介质和设备
US20190354966A1 (en) Distributed Ledger System, Distributed Ledger Subsystem, and Distributed Ledger Node
WO2016041342A1 (zh) 一种m2m中管理应用资源的方法和注册节点
US20180063879A1 (en) Apparatus and method for interoperation between internet-of-things devices
JP5992511B2 (ja) クラウドサービス再接続の自動化
WO2015139310A1 (zh) 一种业务分配的处理方法及相关装置
US10678657B1 (en) Reversion operations for virtual computing environments
WO2017185251A1 (zh) Vnfm的确定方法和网络功能虚拟化编排器
US10382924B2 (en) M2M node management method and apparatus, and computer storage medium
WO2017045450A1 (zh) 资源的操作处理方法及装置
US20210092073A1 (en) Resource trees by management controller
WO2017071118A1 (zh) 监控资源管理的方法、装置和cse、存储介质
CN109873839A (zh) 数据访问的方法、服务器与分布式系统
WO2015109950A1 (zh) 业务资源组实现方法及装置
WO2015117391A1 (zh) 一种实现资源属性通告的方法和公共业务实体
KR20140098579A (ko) 그룹용 워크스페이스 관리 방법 및 장치
WO2015117330A1 (zh) 一种删除通告资源的方法和公共业务实体
WO2018032499A1 (zh) 一种负载均衡的方法及相关装置
WO2018121164A1 (zh) 一种用于创建服务号的方法、设备及系统
JP2016143363A (ja) リポジトリ管理システム及び管理方法
WO2016197637A1 (zh) 一种实现远程访问的方法、AllJoyn网关代理、云服务器及移动设备
WO2018120222A1 (zh) 一种管理vnffg的方法、装置和系统

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: 15841869

Country of ref document: EP

Kind code of ref document: A1

REEP Request for entry into the european phase

Ref document number: 2015841869

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2015841869

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 15512762

Country of ref document: US