Abstract: The present application is directed to an apparatus on a network including a non-transitory memory having executable instructions for configuring membership of a group, and a processor that is operably coupled to the non-transitory memory. The processor is configured to receive a request from a server to add a device to the group, to send a reply to the server that the device is authorized to join the group, to deliver a message to the device when a predetermined condition is met. The device status is selected from joined, active, authorized and combinations thereof. The predetermined condition is selected from a percentage or number of devices in the group are listening, a set time has elapsed, and combinations thereof. The present application is also directed to a networked system including a server and an apparatus in communication with the server.

Abstract: A network data analytics function, which may be implemented as a service, is disclosed which provides a new and improved network data analytics capability in 5G core networks.

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: 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. In another embodiment, a device or gateway service capability layer may request its network service capability layer fetch data that the device or gateway, previously stored on a different network service capability layer. In another 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: 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. 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: Various issues with existing congestion and overload control mechanisms are recognized and described herein. Described herein, in accordance with various embodiments, are various mechanisms in which core networks, such as 3GPP networks for example, and an M2M service layer can coordinate and share information to efficiently and intelligently manage each other's congestion and overload states.

Abstract: Multi-RAT UEs currently have 2 independent paths to authenticate with HSS (either via the MME or the 3GPP AAA Server causing repeated authentication messages to HSS. The use of one unified authentication path between the UE and HSS for Small Cell and Wi-Fi authentication is described. First, a new 3GPP EPC-TWAN interworking architecture has the MME manage all the authentication requests from multi-RAT UEs. Second, new unified authentication procedures are added, which allow the ISWN-based multi-RAT UE to be authenticated directly with the HSS, irrespective of its current access network (TWAN or HeNB). Third, new fast re-authentication procedures for Inter-RAT handover scenarios are done. Finally, the needed extensions to the various standard protocol messages to execute the authentication procedures are described.

Abstract: Current wireless networks do not allow machine type communication (MTC) devices to have long discontinuous reception (DRX) cycles or sleep lengths. A long DRX cycle may allow MTC systems and devices to operate with much longer DRX/Sleep cycles/periods. This may facilitate the MTC operations for infrequent system access or infrequent system reaching (e.g. paged once in a week) with no or low mobility and may allow MTC devices to sleep for a long time with low power consumption.

Abstract: Methods and apparatuses are described herein for configuration of background data transfers (BDTs) between local area data networks (LADNs). An apparatus may receive a message indicating a request from a user equipment (UE) for a data transfer of data originating from the UE. The apparatus may send, to a database, a request for subscription information associated with the UE and a policy profile associated with the UE to determine whether there is an existing BDT policy. The apparatus may receive, from the database, a response indicating whether there is an existing BDT policy that can be re-used. The apparatus may determine, based on the received response, a BDT policy for the data transfer and a LADN to service the data transfer. The apparatus may send, to the LADN via a radio access network (RAN) node, a notification message of an arrival time and data rate for the data transfer.

Abstract: A Service Capability Exposure Function can be added to the UE (U-SCEF). The U-SCEF may be part of the UE's operating system (OS) and expose API's to applications that allow these applications to schedule data plane communications such as periodic sensor measurements or a firmware download. The U-SCEF communicates with an EPC Interworking Service that resides in the mobile network operator's (S)Gi-LAN. The EPC Interworking Service serves as an interface between the U-SCEF and the service capabilities that are exposed by the MNO via the SCEF. The U-SCEF may provide the EPC Interworking Service with information about the UE's anticipated communication schedule and mobility status. The EPC Interworking Service uses the services that are exposed by the SCEF to determine the optimal times for the UE to communicate, an optimal mobility management configuration, etc.

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: Access network discovery and selection function (ANDSF) policies are extended to include a wireless local area network quality of service (Qos) parameter in order to create a ANDSF based QoS. This may be used by user equipment to set the uplink 802.11e User Priority (UP) for offloaded or evolved packet core-routed WiFi traffic.

Abstract: When mobile terminated devices sleep, the devices might not be reachable when needed, for instance when the device is a recipient of data from a third party server. As described herein, a third party application server may inform the network that it has data to send to a particular UE or group of UEs. In an example, the mobile core network (MCN) may use information from the third party server to ensure that the UE is awake when it needs to be. For example, a given UE or group of UEs can be prevented from entering a sleep state before a data transfer is completed.

Abstract: A Policy and Charging Enforcement Function (PCEF) can be aware of whether a UE connects through a cellular or WIFI connection through a gateway. Management messages can be modified to allow the PCEF volume based online charging functionality to remain in the core network (i.e. in the P-GW/PCEF). Session management messaging between the ISWN (ISW-GW) and the core network (P-GW/PCEF) may be modified so that the core network may be notified when the ISWN moves a bearer, or flow, from one RAT to another. Alternately, PCEF volume based online charging functionality can be added to the ISWN. The PCEF of the ISWN can be tasked with performing volume based online charging while the UE is in the ISWN.

Abstract: The present application is directed to an apparatus communicating with a mobile core network. The apparatus includes a non-transitory memory including instructions stored thereon for configuring a service. The apparatus also includes a processor operably coupled to the non-transitory memory configured to execute the instructions of: (i) receiving, from a core network node, first information for accessing a Network Exposure Function (NEF); (ii) receiving a request for the service from an application on user equipment (UE); (iii) creating a request for the service; (iv) using the first information to send the created request to the NEF; (v) receiving a response from the NEF, the response includes a second information; and (vi) sending the second information to the application. The service includes one or more of buffering, background data transfer, communication pattern configuration, sponsored services, reachability, mobile originating/paging-off mode, and value added services.

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: Methods and apparatuses are described herein for a 5G system that deploys services providing optimizations and value add services based on delay tolerant data (DTD) exchanges between end devices and machine to machine (M2M) servers. In accordance with one embodiment, an apparatus may receive, from a second apparatus via the network, first information comprising a delay tolerant communication configuration comprising an identifier and a delay tolerant characteristic. The apparatus may receive, from a third apparatus, data in a plurality of data bundles that each comprises the identifier. The apparatus may process, based on the first information, the plurality of data bundles. The apparatus may route, based on the first information, the plurality of data bundles. The third apparatus may comprise a user equipment (UE).

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: 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).