Abstract: Systems, methods, and instrumentalities may implement service-based discovery in a network, such as a 3GPP or 3GPP2 network. A Discovery Server may be used to query and find services offered by the network or by entities that interface with the network. Situational context information or policy information, or both, may be communicated to the discovery server so that the Discovery Server can provide context-aware and policy-based discovery services. The Discovery Server may be used to control which of the entities that interface with the network can discover one another. The Discovery Server may support queries based on, for example, the type of MTC entity, the type of services hosted on the entity, the availability times of the entity, types of protocols supported, levels of Quality of Service (QoS) supported, and MTC-IWF services.

Abstract: Systems, methods, and instrumentalities may implement service-based discovery in a network, such as a 3GPP or 3GPP2 network. A Discovery Server may be used to query and find services offered by the network or by entities that interface with the network. Situational context information or policy information, or both, may be communicated to the discovery server so that the Discovery Server can provide context-aware and policy-based discovery services. The Discovery Server may be used to control which of the entities that interface with the network can discover one another. The Discovery Server may support queries based on, for example, the type of MTC entity, the type of services hosted on the entity, the availability times of the entity, types of protocols supported, levels of Quality of Service (QoS) supported, and MTC-IWF services.

Abstract: A machine-to-machine (M2M) node is configured to provide a communication management function to facilitate communication between a first service layer in a first network and a second service layer in a second network. The M2M node is configured to store a plurality of attributes for use by the communication management function and to receive via the first network, a first message from a first application in the first service layer. The M2M node is configured to determine, based on at least a first attribute identifying an expiration time after which the communication management function does not facilitate communication, that the communication management function is available to process the first message. The M2M node is configured to determine, based on at least a second attribute defining an access control list identifying applications in the first service layer, that the communication management function is available to process the first message.

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 method of accessing services affiliated with a service provider is disclosed. An issuer performs a bootstrap procedure with the at least one discovered service provider. The issuer performs a discovery procedure to determine available service capability layers (SCLs) supported by the at least one discovered service provider. The issuer transmits a domain name system-based service discovery (DNS-SD) query from the issuer to a DNS-SD M2M service discovery function (MSDF) server. The DNS-SD MSDF server is provisioned with SCL discovery records. The DNS-SD MSDF server is registered with a public DNS registrar entity. The SCL discovery records include, for each SCL, a type of M2M service capabilities supported by each SCL and a class of M2M services supported by each SCL. The issuer receives SCL discovery records from the DNS-SD MSDF server in response to the DNS-SD query.

Abstract: Systems, methods, and instrumentalities are disclosed to propagate announcement and de-announcement of a resource across one or more networks. A first entity, which may be a hosting service capability layer (SCL), may receive a request from an issuer to announce a resource. The first entity may create a representation of the resource. The representation may be referred to as an announced resource. The first entity may send an announce resource request to a second entity (e.g., an announced-to SCL), which may be registered with the first entity. The announce resource request may be sent over an mId interface. The first entity may receive a first response from the second entity over the mId interface indicating that the second entity created the announced resource.

Abstract: Method and apparatus are described for delivering triggers and small data. In an embodiment, a receiver may be configured to receive a trigger or small data packet, and a transmitter may be configured to transmit a subscriber information request to see whether a subscriber is present. The receiver may be further configured to receive an identity of a second node on a condition that the subscriber is present. The transmitter may be further configured to transmit the trigger or small data packet to the second node over an interface, the second node configured to create an Internet Protocol (IP) packet with an IP address containing the trigger or small data packet and deliver the IP packet to a wireless transmit/receive unit (WTRU) using the IP address and a default or dedicated bearer of the WTRU.

Abstract: A network node is configured to initiate a first authentication and key establishment procedure with a machine to machine (M2M) device. The network node is configured to determine a key agreement between the network node and the M2M device using the first authentication and key establishment procedure. The network node is configured to initiate a second authentication and key establishment procedure with an M2M server. The network node is configured to receive a request from the M2M server for the key agreement to be used to communicate with the M2M device using the second authentication and key establishment procedure. The network node is configured to send the key agreement to the M2M server using the second authentication and key establishment procedure.

Abstract: A machine-to-machine (M2M) gateway (GW) includes reachability, addressing, and repository (RAR) capability. The GW maintains a local mapping table and local device application repository, performs data aggregation, address/name translation, provides event reporting and establishes GW reachability and wake-up time. The GW supports requests from M2M applications or other capabilities within the GW, and from a network and application (N&A) domain RAR. The GW may include an M2M device and M2M gateway management (MDGM) capability that receives management requests for an M2M device and functions as a network proxy. The MDGM accepts and processes requests from the N&A domain on behalf of the M2M device and performs management functions of the M2M device on behalf of the N&A domain. The MDGM may request the N&A domain for permission to interact with the M2M device, initiate an interaction for device management tasks with the M2M device, and report to the N&A domain.

Abstract: A machine-to-machine (M2M) node is configured to provide a communication management function to facilitate communication between a first service layer in a first network and a second service layer in a second network. The M2M node is configured to store a plurality of attributes for use by the communication management function and to receive via the first network, a first message from a first application in the first service layer. The M2M node is configured to determine, based on at least a first attribute identifying an expiration time after which the communication management function does not facilitate communication, that the communication management function is available to process the first message. The M2M node is configured to determine, based on at least a second attribute defining an access control list identifying applications in the first service layer, that the communication management function is available to process the first message.

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: Representative methods, apparatus and systems to adjust Do Not Disturb (DND) levels in a wireless transmit/receive unit (WTRU) are disclosed. One representative method includes determining, by the WTRU, that a user of the WTRU is participating or is going to participate in a meeting; obtaining, by the WTRU, organizational hierarchy information; determining a priority associated with one or more meeting participants based on the organizational hierarchy information; and adjusting, without user input, a DND level of the WTRU based on the determined priority.

Abstract: An method for M2M communications and an M2M node are disclosed. The M2M node provides a communication management function for communication between a first service layer in a first network and a second service layer in a second network. The M2M node receives a first message from a first application in the first service layer. The first message encapsulates a second message. The M2M node determines based on at least a first attribute identifying an expiration time after which the communication management function does not facilitate communication, that the communication management function is available to process the first message. The M2M node determines based on at least a second attribute defining an access control list identifying applications in the first service layer for which the communication management function may provide processing, that the communication management function is available to process the first message from the first application.

Abstract: A method and apparatus are described for processing service layer detach commands and attach notifications. A services capability server (SCS) may request a core network to perform a network initiated detach of a device. This procedure may be used when the SCS knows that the device will not be needed for a long time or when the SCS detects some event that may warrant a detach, (e.g., theft, disallowed location, integrity validation failure). The SCS may be asked if the device may be allowed to attach at this time. If the SCS indicates that the attach may be rejected, the device may not be allowed to attach until a later time, thus avoiding additional activity on control and user planes. The SCS may be informed when a device is attached based on various subscription fields stored in a home subscriber server (HSS).

Abstract: Disclosed herein are embodiments for Machine Type Communication (MTC). The techniques disclosed may reduce signaling by transmitting MTC data over control planes and avoiding a full cycle of connection procedures typically required for transmission. MTC data may be directly appended to a control plane message. In addition, in order to reduce the signaling load, a WTRU may autonomously release the connection without being told by the network. Techniques may be used to indicate a network provider's machine type communication (MTC) capability. The MTC services or capabilities that may be provided by a respective network operator may be communicated to a WTRU.

Abstract: Methods and systems providing application layer support for one or more sleeping nodes in constrained networks are contemplated. Embodiments contemplate inserting sleep information in a header option or payload of an application layer message. The application layer message may be conveyed in a hypertext transfer protocol (HTTP) or a constrained application protocol (CoAP). Embodiments contemplate communicating the application layer message to a server, which may serve as a caching and/or buffering proxy.

Abstract: Procedures, mechanisms, methods, and techniques are provided that trigger power saving mode (PSM) functionality in the at least one wireless transmit receive units, group of WTRUs or subset of the group of WTRUs. The trigger may be in response to an application layer request to set one or more predetermined PSM settings, wherein the trigger originates from one or more application servers (APs) directed to a core network by way of an interface such as an SCEF that may be included on a device (e.g., a gateway, computing device, and/or the like) and may be configured for enabling the application server to request enabling and disabling PSM functionality.

Abstract: Systems, methods and apparatus for managing machine-to-machine (M2M) entities are disclosed. Included herein is a method that may include implementing one or more management layers for managing M2M entities in an M2M environment. The method may also include using a plurality of management layers to manage a M2M area network, wherein the M2M area network may include one or more M2M end devices. The M2M end devices may include, for example, an M2M gateway and/or an M2M device. The management layers may include any of an application management layer, service management layer, network management layer and a device management layer. The management layers may provide any of configuration management, fault management, and performance management of the M2M entities.

Abstract: Method and apparatus for supporting machine-to-machine (M2M) communications in a hierarchical network architecture including an M2M gateway are disclosed. An M2M entity, (such as M2M device, M2M gateway, or M2M network entity), may perform a service capability discovery procedure to discover an M2M service capability entity that may provide an M2M service capability, and register with the discovered M2M service capability entity. The address or identity of the service capability entity may be pre-configured or obtained from the dispatcher server. The M2M entity may indicate a support M2M service identifier and receive an identity or address of the M2M service capability entity mapping the service identifier. The gateway may advertise M2M service identifiers supported by the gateway so that the M2M device may access the gateway if there is a match. The address of M2M service capability entities may be obtained from the core network.

Abstract: Methods and systems are disclosed for determining context information for one or more peers to be used in a peer discovery and/or peer association process(es) and/or to otherwise facilitate P2P proximity communications. For example, a method for determining peer context information may include receiving a context-aware identifier (CAID). The CAID may include one or more items of context information associated with the peer in addition to an indication of an identity of the peer. A first portion of the CAID may be decoded to determine a first item of context information associated with the peer. The first portion of the CAID may be decodable without having to process a payload portion of the message. It may be determined whether to continue processing one or more of the CAID or the message based on the first item of context information. The CAID may be used in discovery and/or association procedure(s).