Abstract: IoT service layer capabilities may be employed to automate and simplify the service enrollment process for IoT service subscribers/enrollees. These capabilities enable virtualization of a service subscriber and the physical IoT devices, applications, data and authorized users of the subscriber into a software profile that is representative of the subscriber. Once virtualized, a service subscriber may then delegate the complexities and burden of service enrollment to an automated IoT service enrollment software function.

Abstract: Internet of Things (IoT) configurable event and action sequencing mechanisms for interconnecting various IoT events together to achieve an event and action sequencing process that may efficiently enable complex uses of the data available in IoT systems.

Abstract: Internet of Things (IoT) configurable event and action sequencing mechanisms for interconnecting various IoT events together to achieve an event and action sequencing process that may efficiently enable complex uses of the data available in IoT systems.

Abstract: A registrar entity, such as a service layer gateway, obtains the service capabilities requirements or preferences of a new registree entity, such as an application, and only accepts a registration of the registree if the registrar has sufficient remaining service capacities to meet the service capabilities requirements or preferences of the registree entity while ensuring that the provision of support to existing registree entities is not impacted. If the registrar lacks the capabilities to satisfy the requirements or preferences, it may contact a server to identify another registrar which has the capabilities. Updates to requirements or preference may originate at any node, e.g., at a user equipment device or a service.

Abstract: IoT service layer capabilities may be employed to automate and simplify the service enrollment process for IoT service subscribers/enrollees. These capabilities enable virtualization of a service subscriber and the physical IoT devices, applications, data and authorized users of the subscriber into a software profile that is representative of the subscriber. Once virtualized, a service subscriber may then delegate the complexities and burden of service enrollment to an automated IoT service enrollment software function.

Abstract: Preserving user privacy and preventing surveillance on behalf of users of a virtual reality world. One or more plans are available when a privacy or surveillance risk to a user is detected. In one plan, configurable scripts execute on behalf of the user to create a confusing array of clone avatars that obfuscate the real user avatar behavior. A malevolent avatar, attempting to surveil the user, may have difficulty distinguishing the clones from the user and may miss out on private insights he might otherwise have learned from the user's behavior. In another exemplary privacy plan, a copy of part of the virtual world is spawned, occupied exclusively by the user's avatar, and then merged into the main world. Privacy plans may be selected manually or automatically in response to perceived privacy threats to strike a balance between privacy and enjoyment within the virtual world.

Abstract: A registrar entity, such as a service layer gateway, obtains the service capabilities requirements or preferences of a new registree entity, such as an application, and only accepts a registration of the registree if the registrar has sufficient remaining service capacities to meet the service capabilities requirements or preferences of the registree entity while ensuring that the provision of support to existing registree entities is not impacted. If the registrar lacks the capabilities to satisfy the requirements or preferences, it may contact a server to identify another registrar which has the capabilities. Updates to requirements or preference may originate at any node, e.g., at a user equipment device or a service.

Abstract: Preserving user privacy and preventing surveillance on behalf of users of a virtual reality world. One or more plans are available when a privacy or surveillance risk to a user is detected. In one plan, configurable scripts execute on behalf of the user to create a confusing array of clone avatars that obfuscate the real user avatar behavior. A malevolent avatar, attempting to surveil the user, may have difficulty distinguishing the clones from the user and may miss out on private insights he might otherwise have learned from the user's behavior. In another exemplary privacy plan, a copy of part of the virtual world is spawned, occupied exclusively by the user's avatar, and then merged into the main world. Privacy plans may be selected manually or automatically in response to perceived privacy threats to strike a balance between privacy and enjoyment within the virtual world.

Abstract: A registrar entity, such as a service layer gateway, obtains the service capabilities requirements or preferences of a new registree entity, such as an application, and only accepts a registration of the registree if the registrar has sufficient remaining service capacities to meet the service capabilities requirements or preferences of the registree entity while ensuring that the provision of support to existing registree entities is not impacted. If the registrar lacks the capabilities to satisfy the requirements or preferences, it may contact a server to identify another registrar which has the capabilities. Updates to requirements or preference may originate at any node, e.g., at a user equipment device or a service.

Abstract: Internet of Things (IoT) configurable event and action sequencing mechanisms for interconnecting various IoT events together to achieve an event and action sequencing process that may efficiently enable complex uses of the data available in IoT systems.

Abstract: Internet of Things (IoT) configurable event and action sequencing mechanisms for interconnecting various IoT events together to achieve an event and action sequencing process that may efficiently enable complex uses of the data available in IoT systems.

Abstract: IoT service layer capabilities may be employed to automate and simplify the service enrollment process for IoT service subscribers/enrollees. These capabilities enable virtualization of a service subscriber and the physical IoT devices, applications, data and authorized users of the subscriber into a software profile that is representative of the subscriber. Once virtualized, a service subscriber may then delegate the complexities and burden of service enrollment to an automated IoT service enrollment software function.

Abstract: IoT service layer capabilities may be employed to automate and simplify the service enrollment process for IoT service subscribers/enrollees. These capabilities enable virtualization of a service subscriber and the physical IoT devices, applications, data and authorized users of the subscriber into a software profile that is representative of the subscriber. Once virtualized, a service subscriber may then delegate the complexities and burden of service enrollment to an automated IoT service enrollment software function.

Abstract: Distributed Service Layer Transactions (DSLTs) may be supported by a DSLT service at a service layer of a communications network to offload applications from the burden of managing the processing of DSLTs.

Abstract: A registration procedure may allow one active and multiple inactive SL registrations to be created at different service layer entities for an application entity without adding significant overhead and burden to an application entity.

Abstract: A registration procedure may allow one active and multiple inactive SL registrations to be created at different service layer entities for an application entity without adding significant overhead and burden to an application entity.

Abstract: Internet of Things (IoT) configurable event and action sequencing mechanisms for interconnecting various IoT events together to achieve an event and action sequencing process that may efficiently enable complex uses of the data available in IoT systems.

Abstract: Distributed Service Layer Transactions (DSLTs) may be supported by a DSLT service at a service layer of a communications network to offload applications from the burden of managing the processing of DSLTs.

Abstract: Distributed Service Layer Transactions (DSLTs) may be supported by a DSLT service at a service layer of a communications network to offload applications from the burden of managing the processing of DSLTs.

Abstract: A registrar entity, such as a service layer gateway, obtains the service capabilities requirements or preferences of a new registree entity, such as an application, and only accepts a registration of the registree if the registrar has sufficient remaining service capacities to meet the service capabilities requirements or preferences of the registree entity while ensuring that the provision of support to existing registree entities is not impacted. If the registrar lacks the capabilities to satisfy the requirements or preferences, it may contact a server to identify another registrar which has the capabilities. Updates to requirements or preference may originate at any node, e.g., at a user equipment device or a service.