Abstract: A method and apparatus are described for supporting a two-stage device-to-device (D2D) discovery using a D2D interworking function (IWF). A D2D IWF component may be configured to perform mapping between an application running on an application server and a third generation partnership project (3GPP) network, and provide a set of application programming interfaces (APIs) to allow discovery to be provided as a service to D2D applications. An application identifier may be mapped to a 3GPP identifier. Further, a method and apparatus are described for performing client-server discovery. A first wireless transmit/receive unit (WTRU) may be configured for a listen-only operation, and a second WTRU may be configured to transmit beacons. The first and second WTRUs may perform a radio access network (RAN) discovery procedure at an access stratum (AS) layer. A method and apparatus for performing charging for D2D service using a D2D IWF are also described.

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: 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: A caching entity may store a cached copy of a service layer resource. An original hosting entity may maintain a registry of the corresponding cached resources. Optionally, the original hosting entity may set cache parameters to govern the lifetime of the cache on a caching entity. The caching entity may keep storing the cached copy of the resource and the original hosting entity may obtain statistics about the cached resource. By knowing the statistics, e.g. how many times a resource is retrieved on each caching entity, the original hosting entity may better manage the resource.

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 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 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: 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 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: 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: Mechanisms for subscription and notification may include dynamically changing notification behavior based on notification target status or support access to notification history information.

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 base station may sense, on a cell using unlicensed spectrum, that the unlicensed spectrum is available for transmission. The base station may transmit, after sensing that the unlicensed spectrum is available, consecutive subframes. Each subframe may include a physical downlink control channel and a physical downlink shared channel.

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 caching entity may store a cached copy of a service layer resource. An original hosting entity may maintain a registry of the corresponding cached resources. Optionally, the original hosting entity may set cache parameters to govern the lifetime of the cache on a caching entity. The caching entity may keep storing the cached copy of the resource and the original hosting entity may obtain statistics about the cached resource. By knowing the statistics, e.g. how many times a resource is retrieved on each caching entity, the original hosting entity may better manage the resource.

Abstract: A base station may sense, on a cell using unlicensed spectrum, that the unlicensed spectrum is available for transmission. The base station may transmit, after sensing that the unlicensed spectrum is available, consecutive subframes. Each subframe may include a physical downlink control channel and a physical downlink shared channel.

Abstract: A caching entity may store a cached copy of a service layer resource. An original hosting entity may maintain a registry of the corresponding cached resources. Optionally, the original hosting entity may set cache parameters to govern the lifetime of the cache on a caching entity. The caching entity may keep storing the cached copy of the resource and the original hosting entity may obtain statistics about the cached resource. By knowing the statistics, e.g. how many times a resource is retrieved on each caching entity, the original hosting entity may better manage the resource.

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: A device may control a video communication via transcoding and/or traffic shaping. The device may include a multipoint control unit (MCU) and/or a server. The device may receive one or more video streams from one or more devices. The device may analyze a received video stream to determine a viewing parameter. The viewing parameter may include a user viewing parameter, a device viewing parameter, and/or a content viewing parameter. The device may modify a video stream based on the viewing parameter. Modifying the video stream may include re-encoding the video stream, adjusting an orientation, removing a video detail, and/or adjusting a bit rate. The device may send the modified video stream to another device. The device may determine a hit rate for the video stream based on the viewing parameter. The device may indicate the bit rate by sending a feedback message and/or by signaling a bandwidth limit.