Abstract: The present application is directed to computer-implemented apparatus for controlling a power savings mode characteristic of a device on a network. The apparatus includes a non-transitory memory with instructions for controlling power saving mode characteristic of the device and a processor operably coupled thereto. The processor performs the step of receiving a request to update the characteristics of the device. The processor also performs the step of updating the characteristics of the device based upon the request. The processor further performs the step of sending an acknowledgment that the characteristic has been updated. The application is also directed to a computer-implemented apparatus on a network for supporting buffering and data handling for a power savings mode of a device on the network.

Abstract: A first apparatus detecting, from a second apparatus, one or more swept downlink beams, wherein each swept downlink beam comprises a synchronization signal block; making a measurement of a signal contained within the synchronization signal block of each detected swept downlink beam; decoding a message contained within the synchronization signal block of each detected swept downlink beam; selecting, based on the measurements and decoded message, a synchronization signal block; determine, based on the selected synchronization signal block, a paging block; detecting, within the paging block, a paging indication; and receiving, based on the paging indication, a paging message.

Abstract: A subscriber issues a message to a resource host to request subscription to multiple resources. This message may indicate identifiers of these resources, event notification criteria for each individual resource, and define cross-resource notification criteria, such as time window type and time window size. The resource host issues cross-resource notifications to the subscriber or its designated notification targets when expected changes on the target resources occur within a time window.

Abstract: Methods, systems, and apparatus in a service layer environment may create, update, or delete access control policy triples whenever an access control policy (ACP) resource is created, updated, or deleted. In addition, methods address potentially frequent and unnecessary ACP triple management.

Abstract: Methods and procedures allow devices interwork with various types of service layers by updating the device to support the protocol of the M2M/IoT service layer that is being communicated with. Devices can coordinate/initiate download of a service layer API that is compatible with the service layer the device is attempting to use. A service layer can coordinate the autonomous update of a device with the proper service layer API which allows the device to then communicate and use services supported by the service layer component to the device. A service layer can detect a device or application lacking proper service layer functionality and can trigger a management entity to update the device or application with the service layer API required such that the device can then register to the service layer and use its services. A device or application can be customized or optimized to the service layer that it is registered to and using.

Abstract: An IoT E2E Service Layer Security Management system supports methods and procedures to allow an application to establish, use, and teardown an IoT SL communication session that has application specified E2E security preferences and that targets one or more SL addressable targets (e.g., an IoT application, device, or gateway SL addressable resource). E2E SL Session based methods and procedures described herein achieve a required overall E2E security level, by allowing IoT SL instances to influence and coordinate hop security for a multi-hop communication path spanning across multiple intermediary nodes. The methods and procedures described herein reduce overhead, simplify and obviate the need for E2E service level nodes (initiation and termination nodes) from having to perform security service negotiation, in order to establish secure hop-by-hop security associations aligned with an E2E security requirement.

Abstract: Application relationships may be categorized and managed at a service layer, such as creating application relationship, updating application relationship, retrieving application relationship, deleting application relationship, or discovering application relationship. Services may be based on application relationship awareness.

Abstract: Two methods are described to enable the communication between two service layer entities that do not have registration relations. In the first method, service layer entities employ a retargeting table that stores the service layer entity to retarget the message in order to deliver the message to the destination. In a second method, an infrastructure node in a service provider employs a retargeting chain table that stores a chain of entities that can retarget the message to the destination.

Abstract: Mechanisms for service layer charging correlation are disclosed. Embodiments can include a Service Domain Charging Correlation Function (SD-CCF), which is responsible for interacting with underlying network and correlating charging information at service layer. Charging correlation information can be used to enable and facilitate the service layer charging correlation.

Abstract: An Application Data Delivery Service (ADDS) facilitates application data transfer between applications that may reside in a device domain (e.g., M2M/MTC devices and gateways) and applications residing in a network domain (e.g., an AS or SCS). The ADDS leverages existing 3GPP transport mechanisms, such as NAS, SMS, USSD, and User Plane, and it is configured to select a transport mechanism for delivering application data based on criteria, such as application data characteristics, application/end node characteristics and availability, subscription information, policies of the network, network conditions (such as congestion, node availability) and the like.

Abstract: The present application is directed to a device on a network that is configured to add a service. The device includes a memory that is operably coupled to the processor. The processor is adapted to configure a service enablement policy. The processor is also adapted to receive a request to add the service from a service provider. The processor is adapted to check the service enablement policy for adding the service. The processor is also adapted to collaborate with another device to harmonize the service enablement policy and the host selection criteria. Further, the processor is adapted to send a reply to the service provider. The present application is also directed to a method for adding a service.

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: An M2M/IoT resource directory entity may discover and register to other resource directory entities by including criteria attributes in discovery broadcasts and then processing link and metadata that may be included in responses. The resource directory with registrations to other resource directories may service a client request by selecting other resources directories to query based on the request or a query criteria contained therein, and then process link and metadata in responses from the other resource directory entities to aggregate a response to the client. Directory-to-directory registrations may be facilitated via using hierarchical parent-child resource directory identifiers, a peer-to-peer identifier regime, or a combination of the two. Observe notifications may include indicia registrations states, e.g., via change and delete response codes.

Abstract: Methods, devices, and systems allow for bootstrapping of a machine-to-machine device. In an embodiment, a bootstrap erase architecture allows the machine-to-machine server to manage bootstrap erase policies, detect access network specific events, initiate a bootstrap erase based on these policies and events, and allow for machine-to-machine server handover. A device or gateway service capability layer (182) requests its network service capability layer to fetch data that the device or gateway previously stored on a different network service capability layer (196, 197). In an embodiment, when bootstrap erase is performed because the network service capability layer can no longer provide service to the device or gateway, the network service capability layer may recommend other NSCLs to the device or gateway. In another embodiment, a bootstrap erase procedure may be modified so that temporary identifiers may be assigned for a next bootstrapping event.

Abstract: A relay device configured to communicate with a terminal device of the network and with a base station of the network. The relay device comprises transmitter circuitry, receiver circuitry and controller circuitry. The controller circuitry is configured in combination with at least the transmitter circuitry: to select a maximum transmission power to be used by the terminal device for communicating with the relay device, wherein the identified maximum transmission power is based on link information relating to one or both of the link between the relay device and the base station and the link between the relay device and the terminal; to notify the communication device of the selected maximum transmission power for the terminal to select an actual transmission power and to transmit signals to the relay device at a power that is no more than the maximum transmission power.

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: Methods, systems, and devices may be used for assigning names and bootstrapping of security credentials for Smart Objects inside a Digital Home environment. Methods, systems, and devices for identification and security bootstrapping of a smart object within a digital home environment may include automated assignment of a device level ID and security credential for each smart object in the home using a resource directory.

Abstract: As described herein, various nodes in a 3GPP network, including a user equipment (UE), can be used to insert metadata in uplink traffic so that the network and/or an (S)Gi-LAN can make traffic steering decisions based on the metadata. For example, the UE can insert metadata into its uplink traffic so that the services in the (S)Gi-LAN can be better leveraged. In one embodiment, network nodes are able to insert metadata that relates directly to the UE and that relates to the operating conditions of the network nodes that the UE is using to send uplink data, so that the services in the (S)Gi-LAN can be better leveraged.

Abstract: A method of allocating transmission resources in an OFDM wireless telecommunication system arranged to communicate data using a plurality of OFDM sub-carriers.