Abstract: Methods, systems, and devices may be used to support freshness-based processing of requests. Freshness-based processing may involve the service layer examining the age of stored content (e.g., resource representation) that it hosts and determining whether it is fresh enough to satisfy a retrieve or discovery request with a specified freshness requirement. If not fresh, the service layer can contact an application to refresh the content. In addition, freshness-based processing can also involve the service layer examining the semantic state of a command oriented update request to determine whether its state is fresh or not with respect to prior commands processed by the service layer. For example, the service layer may compare stored content associated with controlling a particular application (e.g. door is locked) and against the semantic content of an update request (e.g., unlock door) to determine whether it is the same (e.g., stale) or not (e.g., fresh).

Abstract: Augmented reality (AR) systems, methods, and instrumentalities are disclosed. A user's gaze point may be estimated and may be used to search for and present information, e.g., information relating to areas on which the user is focusing. The user's gaze point may be used to facilitate or enable modes of interactivity and/or user interfaces that may be controlled by the direction of view of the user. Biometric techniques may be used to estimate an emotional state of the user. This estimated emotional state may be used to be the information that is presented to the user.

Abstract: Systems and methods for enabling proximity services to be delivered as part of an application service and/or for providing tailored services and/or a differential quality of service (QoS) to a flow may be disclosed. For example, a temporary service name between an application and a server such as a D2D server may be established such that a UE and/or network may execute such a service at a later time without later involvement by the application and/or without exchanging credentials for the application with the network and vice versa.

Abstract: Augmented reality (AR) systems, methods, and instrumentalities are disclosed. A user's gaze point may be estimated and may be used to search for and present information, e.g., information relating to areas on which the user is focusing. The user's gaze point may be used to facilitate or enable modes of interactivity and/or user interfaces that may be controlled by the direction of view of the user. Biometric techniques may be used to estimate an emotional state of the user. This estimated emotional state may be used to be the information that is presented to the user.

Abstract: Mechanisms for subscription and notification may include dynamically changing notification behavior based on notification target status or support access to notification history information.

Abstract: A video encoding device (e.g., a wireless transmit/receive unit (WTRU)) may transmit an encoded frame with a frame sequence number using a transmission protocol. The video encoding device, an application on the video encoding device, and/or a protocol layer on the encoding device may detect a packet loss by receiving an error notification. The packet loss may be detected at the MAC layer. The packet loss may be signaled using spoofed packets, such as a spoofed NAM packet, a spoofed XR packet, or a spoofed ACK packet. A lost packet may be retransmitted at the MAC layer (e.g., by the encoding device or another device on the wireless path). Packet loss detection may be performed in uplink operations and/or downlink operations, and/or may be performed in video gaining applications via the cloud. The video encoding device may generate and send a second encoded frame based on the error notification.

Abstract: Mechanisms for subscription and notification may include dynamically changing notification behavior based on notification target status or support access to notification history information.

Abstract: A set of point-of-contact information including a service level identifier, an address, a list of interfaces, and a set of interface selection preferences for each of several entities may be used to facilitate communications among the entities by selecting a preferred interface in accordance with the set. Interface preferences may also be derived from a set of policies. The preferred interface may be resolved in accordance with the preferences of multiple entities. Messages may include an interface type parameter to be used for forwarding of the message, and message forwarding may be resolved in accordance with the parameter and the messages.

Abstract: A video encoding device (e.g., a wireless transmit/receive unit (WTRU)) may transmit an encoded frame with a frame sequence number using a transmission protocol. The video encoding device, an application on the video encoding device, and/or a protocol layer on the encoding device may detect a packet loss by receiving an error notification. The packet loss may be detected at the MAC layer. The packet loss may be signaled using spoofed packets, such as a spoofed NACK packet, a spoofed XR packet, or a spoofed ACK packet. A lost packet may be retransmitted at the MAC layer (e.g., by the encoding device or another device on the wireless path). Packet loss detection may be performed in uplink operations and/or downlink operations, and/or may be performed in video gaining applications via the cloud. The video encoding device may generate and send a second encoded frame based on the error notification.

Abstract: A modular and distributed architecture for data stream processing and analysis is described to incorporate data stream analytics capabilities, called Data Stream Analytics Service (DSAS) in the IoT/M2M service layer. Each service layer node hosting DSAS can be split into two independent modules, Stream Forwarder and Stream Analytics Engine. Stream Forwarder is a light weight processing modules that can be responsible for data preprocessing and routing. Stream Analytics Engine is responsible for performing actual analytics on the data stream. Separating the two functionalities enables the service layer nodes to efficiently distribute stream analytics tasks across multiple nodes.

Abstract: A 5G Network Architecture uses virtualization and network slicing. The user equipment (UE) interacts with an underlay network that interacts with virtual network slices. The UE interacts with the underlay network (ULN) to establish a connection to a virtual network slice. Procedures are defined to assign a new slice instance to a UE (UE initiated and ULN initiated); to change a UE Profile (UE initiated and ULN Initiated); and to change a UE's assigned slice instance (ULN Initiated).

Abstract: The present application is at least directed to an M2M gateway apparatus. The apparatus includes a non-transitory memory having instructions stored thereon for service layer online charging of a service layer event. The apparatus also includes a processor operably coupled to the non-transitory memory configured to execute a set of instructions. One of the instructions includes sending, to a service layer charging function of an M2M server, a service layer rating request message for the service layer online charging of the service layer event detected by the M2M gateway. The service layer event is triggered by an application registered to the M2M gateway and that performs a read or write operation on a resource of the M2M gateway. Another one of the instructions includes receiving, from the service layer charging function of the M2M server, a rating response including the calculated amount of service units required for the M2M gateway to process the service layer event.

Abstract: A 5G Network Architecture uses virtualization and network slicing. The user equipment (UE) interacts with an underlay network that interacts with virtual network slices. The UE interacts with the underlay network (ULN) to establish a connection to a virtual network slice. Procedures are defined to assign a new slice instance to a UE (UE initiated and ULN initiated); to change a UE Profile (UE initiated and ULN Initiated); and to change a UE's assigned slice instance (ULN Initiated).

Abstract: The present application is at least directed to an apparatus on a network. The apparatus includes a non-transitory memory having instructions stored thereon for online charging of an event. The apparatus also includes a processor that is operably coupled to the non-transitory memory. The processor is configured to execute the instructions of receiving, from an M2M gateway, a rating request message for service layer online charging. The processor is also configured to execute the instructions of determining a rating scheme to charge for the event. The processor is further configured to execute the instructions of calculating an amount of service units based on the rating request message and determined rating scheme. The processor is even further configured to execute the instructions of sending, to the M2M gateway, a rating response based upon the calculated amount of service units.

Abstract: A modular and distributed architecture for data stream processing and analysis is described to incorporate data stream analytics capabilities, called Data Stream Analytics Service (DSAS) in the IoT/M2M service layer. Each service layer node hosting DSAS can be split into two independent modules, Stream Forwarder and Stream Analytics Engine. Stream Forwarder is a light weight processing modules that can be responsible for data preprocessing and routing. Stream Analytics Engine is responsible for performing actual analytics on the data stream. Separating the two functionalities enables the service layer nodes to efficiently distribute stream analytics tasks across multiple nodes.

Abstract: Systems, methods, and instrumentalities are disclosed to perform rate adaptation in a wireless transmit/receive unit (WTRU). The WTRU may receive an encoded data stream, which may be encoded according to a Dynamic Adaptive HTTP Streaming (DASH) standard. The WTRU may request and/or receive the data stream from a content server. The WTRU may monitor and/or receive a cross-layer parameter, such as a physical layer parameter, a RRC layer parameter, and/or a MAC layer parameter (e.g., a CQI, a PRB allocation, a MRM, or the like). The WTRU may perform rate adaption based on the cross-layer parameter. For example, the WTRU may set the CE bit of an Explicit Congestion Notification (ECN) field based on the cross-layer parameter. The WTRU may determine to request the data stream encoded at a different rate based on the cross-layer parameter, the CE bit, and/or a prediction based on the cross-layer parameter.

Abstract: Mechanisms for subscription and notification may include dynamically changing notification behavior based on notification target status or support access to notification history information.

Abstract: A wireless transmit/receive unit (WTRU) may receive from a network resource allocation information for device to device (D2D) communication. The WTRU may select, from the received resource allocation information for a transmission time interval (TTI), resources for a D2D channel. The WTRU may transmit, with use of the selected resources, data directly to another WTRU.

Abstract: Enabling semantic reasoning service within the semantic framework in a M2M/IoT system includes: 1) an overall in architecture of semantic reasoning processor, which highlights the functional components and flows of the reasoning process; 2) defined procedures for reasoning rule management in M2M/IoT systems (e.g., create and delete) for different scenarios; 3) procedures for triggering and performing the semantic reasoning process in M2M/IoT systems, which may be triggered by semantic query and semantic annotation process in on-demand and proactive manner; and 4) methods of dealing with and processing the new information generated through semantic reasoning process, which may include generating more semantic information to describe the information generated (e.g., new data content).

Abstract: Mechanisms for subscription and notification may include dynamically changing notification behavior based on notification target status or support access to notification history information.