Abstract: A method performed by a node (111) supporting operation on a Constrained Application Protocol (CoAP), but incapable of supporting operation on a Domain Name System (DNS) protocol. The node (111) encodes (402) a DNS query into a first message (601, 701), which has a format supported by the CoAP. The DNS query is mapped to the CoAP format of the first message (601, 701) based on a mapping scheme. The node (111) then initiates sending (403) the first message (601, 701) to another node (112) operating in the communications network (100). The another node (112) supports operation on the CoAP and on the DNS protocol. The node (111) finally receives (404) a second message (620, 706) from the another node (112), which has the format supported by the CoAP. The second message (620, 706) comprises the DNS response to the sent DNS query. The DNS response is mapped to the CoAP format of the second message (620, 706) based on the mapping scheme.

Abstract: A server node is configured to assume a server role in a particular message exchange with a client node. The server node registers, with a resource directory node, security information (e.g., security capabilities and/or security preferences) of the server node. The server node may also register information about a resource that the server node hosts. The client node determines, from the resource directory node, the security information (e.g., security capabilities and/or security preferences) of the server node. The client node then sets up a secured connection with the server node using the determined security information (e.g., security capabilities and/or security preferences).

Abstract: Group management of LwM2M devices over MQTT A Lightweight Machine to Machine (LwM2M) server device is disclosed that is operable to run a LwM2M server and a Message Queueing Telemetry Transport (MQTT) client. The LwM2M server device comprises processing circuitry configured to cause the LwM2M server device to determine (310) that a LwM2M management operation should be performed on LwM2M clients fulfilling a criterion, and to identify (320) a LwM2M group management topic corresponding to the criterion, a LwM2M group management topic comprising a topic within a LwM2M namespace that is nonspecific to a particular LwM2M endpoint. The processing circuitry is further configured to cause the LwM2M server device to publish (330) a group management message to an MQTT server, the group management message specifying the identified LwM2M group management topic and the management operation to be performed. Also disclosed are a LwM2M client device and associated methods.

Abstract: A method performed by a node (111) supporting operation on a Constrained Application Protocol (CoAP), but incapable of supporting operation on a Domain Name System (DNS) protocol. The node (111) encodes (402) a DNS query into a first message (601, 701), which has a format supported by the CoAP. The DNS query is mapped to the CoAP format of the first message (601, 701) based on a mapping scheme. The node (111) then initiates sending (403) the first message (601, 701) to another node (112) operating in the communications network (100). The another node (112) supports operation on the CoAP and on the DNS protocol. The node (111) finally receives (404) a second message (620, 706) from the another node (112), which has the format supported by the CoAP. The second message (620, 706) comprises the DNS response to the sent DNS query. The DNS response is mapped to the CoAP format of the second message (620, 706) based on the mapping scheme.

Abstract: A CoAP client sends to a CoAP server a request for information about a resource, the request for information including a time period option, wherein the time period option includes a first time period value that indicates a period of time prior to the sending of the request for information over which information about the resource is requested. The CoAP client receives a response to the request for information. In another embodiment, a CoAP client sends to a CoAP server a CoAP Observe registration relating to one or more resources, the CoAP Observe registration including an option, the option including a first value that indicates that the CoAP server should pause notifications for one or more registrations corresponding to one or more resources.

Abstract: An instructing computing device (210) is disclosed that is operable to implement a 5Constrained Application Protocol (CoAP). The computing device comprises processing circuitry configured to send a first message (211) to a target computing device (220), which comprises a first message identifier and store a record (212) of the first message in a memory. The processing circuitry is further configured to receive a second message (223) from the target computing device, the second message confirming that 0the target computing device has received the first message, wherein the first message is configured to cause the target computing device to store a record (222) of the first message.

Abstract: A method includes providing a Thing Description file for an Internet of Things, IoT, device, the Thing Description file including information describing a resource provided by the IoT device, mapping the Thing Description file to a Resource Directory registration command, and transmitting the Resource Directory registration command to a Resource Directory to register the resource in the Resource Directory. Related devices and computer program products are also disclosed.

Abstract: Complete and partial object publication using, for example, MQTT or other protocol is described. In some embodiments, an emphasis is placed on keeping the amount of state information that the broker must maintain to a minimum, as well as allowing idempotent operations over objects in order to keep the object view between the subscribers consistent. Embodiments are described in which only the parts of an object have changed are transferred to the subscribers who subscribe to that object.

Abstract: A method performed by a node (111) supporting operation on a Constrained Application Protocol (CoAP), but incapable of supporting operation on a Domain Name System (DNS) protocol. The node (111) encodes (402) a DNS query into a first message (601, 701), which has a format supported by the CoAP. The DNS query is mapped to the CoAP format of the first message (601, 701) based on a mapping scheme. The node (111) then initiates sending (403) the first message (601, 701) to another node (112) operating in the communications network (100). The another node (112) supports operation on the CoAP and on the DNS protocol. The node (111) finally receives (404) a second message (620, 706) from the another node (112), which has the format supported by the CoAP. The second message (620, 706) comprises the DNS response to the sent DNS query. The DNS response is mapped to the CoAP format of the second message (620, 706) based on the mapping scheme.

Abstract: A first communication device transmits, to a second communication device, a first indication indicating a configuration enabling the first communication device to receive a partial modification of resources. The first communication device receives, from the second communication device, a second indication indicating a partial update, in time, associated with a resource and a value of a part of the resource. The first communication device further maintains an internal value of the part of the resource based on the second indication.

Abstract: A method and a system for reducing the size of a blockchain. The blockchain includes a first set of two or more blocks including an initial genesis block. A new genesis block for the blockchain is generated. The first hash value resulting from hashing the new genesis block matches a second hash value resulting from hashing a last block from the first set of blocks, and the difficulty of determining the first hash value is computationally greater than the cumulative difficulty of determining hash values of all blocks in the first set of blocks. The new genesis block is transmitted to one or more blockchain nodes of a blockchain network, and the first set of blocks is replaced with the new genesis block.

Abstract: A method performed by a node (111) supporting operation on a Constrained Application Protocol (CoAP), but incapable of supporting operation on a Domain Name System (DNS) protocol. The node (111) encodes (402) a DNS query into a first message (601, 701), which has a format supported by the CoAP. The DNS query is mapped to the CoAP format of the first message (601, 701) based on a mapping scheme. The node (111) then initiates sending (403) the first message (601, 701) to another node (112) operating in the communications network (100). The another node (112) supports operation on the CoAP and on the DNS protocol. The node (111) finally receives (404) a second message (620, 706) from the another node (112), which has the format supported by the CoAP. The second message (620, 706) comprises the DNS response to the sent DNS query. The DNS response is mapped to the CoAP format of the second message (620, 706) based on the mapping scheme.

Abstract: Methods for a CoAP server to inform CoAP clients regarding a set of one or more communication protocols supported by the CoAP server. In one aspect, a CoAP client obtains information indicating a set of one or more communication protocols supported by the CoAP server and determines which of the set of one or more communication protocols to use to communicate with the CoAP server.

Abstract: The disclosure relates to a method performed in a first device for negotiating session descriptor parameters with a second device over an application layer protocol. The method comprises converting a value of a text based session descriptor parameter of a session description protocol, SDP, message into a binary format; encapsulating the converted SDP message into an application layer protocol message; and sending the application layer protocol message to the second device.

Abstract: A method includes providing a Thing Description file for an Internet of Things, IoT, device, the Thing Description file including information describing a resource provided by the IoT device, mapping the Thing Description file to a Resource Directory registration command, and transmitting the Resource Directory registration command to a Resource Directory to register the resource in the Resource Directory. Related devices and computer program products are also disclosed.

Abstract: A network node, a device and methods therein are provided for handling of devices based on group membership. The method performed by the network node comprises obtaining of information indicating a group membership and further indicating reachable gateways of a set of devices. The method further comprises initiating a command to a number of devices out of the set of devices belonging to the same group, G1, to connect to one of the indicated gateways, gateway W, selected for the number of devices based on group membership.

Abstract: A method performed by a node (111) supporting operation on a Constrained Application Protocol (CoAP), but incapable of supporting operation on a Domain Name System (DNS) protocol. The node (111) encodes (402) a DNS query into a first message (601, 701), which has a format supported by the CoAP. The DNS query is mapped to the CoAP format of the first message (601, 701) based on a mapping scheme. The node (111) then initiates sending (403) the first message (601, 701) to another node (112) operating in the communications network (100). The another node (112) supports operation on the CoAP and on the DNS protocol. The node (111) finally receives (404) a second message (620, 706) from the another node (112), which has the format supported by the CoAP. The second message (620, 706) comprises the DNS response to the sent DNS query. The DNS response is mapped to the CoAP format of the second message (620, 706) based on the mapping scheme.

Abstract: A method in a network node of a communication network configured to manage command messages from at least one Machine Type Communication, MTC, device manager intended for an MTC device, comprises receiving command messages from the at least one MTC device manager, step (201). One or more command messages are merged into an MTC device message that comprises at least one command message, step (203). Originator information is associated with each command message in the MTC device message, step (205). The MTC device message is sent to an MTC device. The network node may further perform the steps of receiving an MTC device message from an MTC device, the MTC device message comprising at least one response message, step (301).

Abstract: The present disclosure relates to a method and apparatus for managing connectivity between a cellular network 15 (in which device communicate via long-range wireless technology) and devices in one or more multi-hop capillary networks 16 (in which devices communicate via short-range wireless technology). One or more gateways 24 connect the one or more multi-hop capillary networks 16 to the cellular network 15 and communicates via short-range and long-range wireless technology. A management node 28 determines a topology of the capillary network(s) 16 based on received reachability information. The topology indicates which devices are within communication range of other devices and gateways in the capillary network 16. The management node 28 makes determinations based on the topology and transmits notifications to a first device 26B within communication range of the one or more gateways 24 and to a second device 26A not within communication range of any gateway.

Abstract: A method performed by a machine-to-machine, M2M, server for managing communication with a M2M device is disclosed. The method comprising configuring the M2M device with a finite number of predetermined states and predetermined transitions for moving the M2M device into one of its predetermined states, and sending a message to the M2M device for executing at least one of the predetermined transitions.