Abstract: A method, performed by a network node, for enabling Interior Gateway Protocol (IGP) fast convergence, the method includes determining that there is a significant change in link state information, the significant change is at least one of a link down, a link up, and a link metric change. The method further includes originating a link state packet comprising a flag that is set to indicate the significant change in the link state information; and distributing the link state packet.

Abstract: A naming scheme for IoT Devices can address the problem that the existing naming schemes of the IoT devices do not support device discovery and group operation efficiently. An IoT Device Name Service (IDNS) can be in charge of how the device name is generated from the location and other context information; updated due to the location change or context variation; and discovered. The IoT Devices can be routed by their names using a Name Routing Protocol (NRP). With the name scheme and NRP, the IoT Devices do not need to implement the full protocol stack to enable the direct communication between them.

Abstract: The disclosure includes a method of performing congestion control by a server device in a network. The method includes setting an effective window equal to a congestion window; sending traffic including the effective window to a client device; receiving an acknowledgment (ACK) from the client device; incrementing the congestion window if the ACK is not a duplicate; and updating the effective window based at least partly on the incremented congestion window.

Abstract: The disclosure relates to technology for machine type communication (MTC) in an information centric network. A record is stored that identifies multiple MTC devices having one or more of the same functions. The multiple MTC devices form a group with a unique name. The group of MTC devices is managed to add one or more other connected MTC devices to the information centric network, where the one or more other connected MTC devices have one or more of the same functions as the MTC devices already included in the group. A message is then published in the information centric network, where the message includes a unique name of the group of MTC devices and an address of a next hop towards the group of MTC devices.

Abstract: Mechanisms for discovering ad hoc Service Layer Entities (aSLEs) either deployed in ad hoc or switched from normal operation mode to ad hoc mode can support an IoT service in a distributive self-organized system.

Abstract: A human-computer interaction method is applied to an electronic device, and includes: obtaining content copied by a user on a first page, and determining a category to which the content belongs; obtaining a category of a second page; matching the category of the content against the category of the second page; and if a matching result is not empty, displaying at least one operation option on the second page, where the at least one operation option has a function of performing an operation for the content on the second page, so that the electronic device directly performs the function after the user selects the operation option. In the method, a category of copied text content is extracted and is matched against a category of a keyword, and a matched group is used as a prompt operation. The prompt operation is displayed in a form of a dialog box, to prompt a next action that may be performed by a user, so that complexity of user operations is reduced, and accuracy of pasting text information is improved.

Abstract: Methods, devices, and systems are disclosed for an M2M Interest Function. An M2M Interest Function may receive requests from users to publish the users' personal interests in particular data identify relationships and patterns in the data. Associated data may then be stored in a single best location for such data based on various criteria rather than on separate M2M Gateways or M2M Servers. This location may be provided to users interested in such data. Relationship and association data may be provided to M2M gateways.

Abstract: Enhancements to the device management functionality within service layer architecture of a Gateway node are described. The SL application registration procedure can be enhanced for devices in support of device management. Functionality can be added to the service layer to initiate automated request notification for DM purposes. Lightweight SL Transport Protocol bindings can support sending multiple DM commands called DM Action Scripts with a specific focus on the Constrained Application Protocol (CoAP) Protocol.

Abstract: Wireless channels and timeslots are allocated in a distributed and reactive manner by network devices. A source device sends to neighbor devices a track discovery request indicating a destination and data bandwidth/channel and timeslot requirements. The neighbors conditionally forward the message until it reaches the destination device. The forwarded message includes information about the devices traversed by the message. Messages will not be forwarded if the recipient lacks sufficient resources to accommodate the data bandwidth requirements. The destination selects a path to be a communications track based upon characteristics of the one or more paths by which the request was received, and sends a reply back to the source device along the selected path. Once established, tracks may be kept alive, updated, and/or repaired via messaging among the devices along the track.

Abstract: A system is disclosed for orchestrating services. Service orchestration profiles specify attributes defining desired services. The service orchestration profiles may be distributed amongst nodes and hierarchically related to each other. Service orchestration management functions process the information in the service orchestration profiles in order to determine the desired services and use the information to implement the desired services. The service orchestration management functions may be hierarchically related to each other.

Abstract: An instrument calibration apparatus and a calibration method using same. The apparatus comprises a physical quantity input/output unit, a physical quantity measurement unit, a physical quantity configuration unit, a display unit, a man-machine interaction unit, a storage unit, and a control unit. The apparatus can be widely applied to automatic calibration of multivariable instruments.

Abstract: Enhancements to the device management functionality within service layer architecture of a Gateway node are described. The SL application registration procedure can be enhanced for devices in support of device management. Functionality can be added to the service layer to initiate automated request notification for DM purposes. Lightweight SL Transport Protocol bindings can support sending multiple DM commands called DM Action Scripts with a specific focus on the Constrained Application Protocol (CoAP) Protocol.

Abstract: Multicast messaging may be managed in a machine-to-machine/Internet of things context, such as a CoAP network, via the inclusion of server selection criterion in multicast request messages and/or resource directory registration management. Server selection criteria may be explicit or implicit. An explicit criterion may be expressed, for example, as an IP address, a server identifier relative to a group context, or a Bloom filter. An implicit criterion may, for example, relate to the context of the request or the requestor, and include such information as data accuracy, data type, application, operating system, network location, geolocation, resource creation time, and resource update time. Server selection criteria may be maintained by a resource directory and/or via a user interface.

Abstract: A lightweight and extensible information model for machine-to-machine systems is disclosed. A service layer information management architecture uses three categories of atomic objects, subjects, actions, and descriptions. Information for use within the model is built using the atomic information objects. Application programming interfaces are used to perform operations and information processing by different nodes. Common service functions are used in the model as instances of a generic common service information model.

Abstract: A service layer entity may register to another service layer entity and proactively request to gain access to the local services hosted by the registrar entity. A registrar entity may accept a registree entity's registration request but only grant access of its partial services to the registree entity. If a registree entity does not need to proactively request the services within its registration request message, the registrar entity decides what services may be needed by the registree entity and grants access of those services to the registree entity.

Abstract: A cloud-based DNS-SD architecture may link together separate LANs to form a virtual discovery zone from a service discovery perspective that includes a cloud based DNS-SD server separate from regular Internet DNS, and asleep node handling, among other things. In an example, a cloud based DNS-SD server is separate from the regular Internet DNS servers. This cloud DNS-SD server may run as a private Infrastructure as a Service (IaaS) specifically for service discovery in the virtual discovery zone.

Abstract: A lightweight and extensible information model for machine-to-machine systems is disclosed. A service layer information management architecture uses three categories of atomic objects, subjects, actions, and descriptions. Information for use within the model is built using the atomic information objects. Application programming interfaces are used to perform operations and information processing by different nodes. Common service functions are used in the model as instances of a generic common service information model.

Abstract: CoAP network nodes may leverage context awareness to take autonomous action to adjust network operations. Context-aware procedures may be pre-configured, established by management entities, or negotiated between nodes, and include parameters for the monitoring and evaluation of data, as well has triggers for taking action. By monitoring requests to observe a resource, a node may determine when a resource should transition to multicast or unicast notification, and dynamically manage multicast group membership based on observation registrations and/or cancellations. By monitoring resource requests, a proxy may determine when to proactively refresh a cached representation of a resource. By monitoring timeouts and/or retransmissions, a client may dynamically adjust a timeout value to optimize communications.

Abstract: A method and apparatus for distributed services and data in a machine-to-machine (M2M) communication network are disclosed. A network server, an M2M gateway, and M2M devices include an M2M service capability layer for supporting M2M service capabilities, respectively. Reference points may be defined for interactions between network service capability layers, between gateway service capability layers, between a gateway service capability layer and a device service capability layer of an M2M device, between M2M device applications, and/or between a network, gateway, or device service capability layer and an M2M application. The network server may be split into a control server and a data server at a service capability layer to provide service capabilities for control functions and service capabilities for data functions, respectively. The data server may be configured to interact with another data server to push or pull data or resources either directly or indirectly via the control server.

Abstract: A service layer entity (e.g., application entity, common service entity in oneM2M, also referred to as registree entity) may register to another service layer entity (e.g., common service entity in oneM2M, also referred to as a registrar entity) and proactively request to gain access to the local services hosted by the registrar entity. A registrar entity may accept a registree entity's registration request but only grant access of its partial services to the registree entity. If a registree entity does not need to proactively request the services within its registration request message, the registrar entity decides what services may be needed by the registree entity and grants access of those services to the registree entity.