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: It is recognized herein that capabilities are lacking related to how different users can be authenticated on top of an existing subscription authentication. In some examples, a user¬ centric authentication layer may be supported on top of an existing subscription authentication, such that different users may use the same user equipment (UE) with customized services, and different users of devices can be identified behind a gateway with a 3GPP subscription (without the devices having a dedicated 3GPP subscription). Further, a user identifier may be linked to a subscription to access 3GPP services via non-3GPP access.

Abstract: A user equipment device (UE) initiates the creation of a dedicated bearer between a local gateway (L-GW) and a packet data network gateway (P-GW). A GTP tunnel is established to connect the L-GW, a serving gateway (S-GW), and the P-GW. The L-GW and P-GW apply Network Address Translation (NAT) and/or Traffic Flow Template (TFT) to route the traffic between the LS and a Service Capacity Server/Application Server (SCS/AS). Alternatively, an SCS-initiates the bearer creation, and an SCEF manages the creation of the GTP tunnel connecting. The L-GW may be co-located with an Evolved UTRAN Node B (eNB) and/or connected to multiple eNBs which are not co-located with the L-GW.

Abstract: A network entity may determine whether a network context of a device is stored in the device or in the network based, at least in part, on a preference or capability of the device, as reported by the device during attachment to the network entity. The context may be stored in, and retrieved from, a dedicated context storage function that is independent of the network entity. A context storage function may be partitioned, or separate storage functions used, to automatically group and track access network contexts, core network contexts, or network slice contexts. The context storage function may provide to the device an index, such as a link or other identifier to be used in retrieving the stored context information. The context storage function may further provide a token to secure re-attachment communications among the device, the network entity, and the context storage function.

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: 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: 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: Methods and systems may be used to synchronize time across multiple IoT related entities, such as a network of resource constrained sensor and actuator type devices, IoT gateways, IoT cloud services, or IoT applications.

Abstract: A 5G network may support path switch mechanisms from a direct path to an indirect path to the network, and vice versa. Methods and systems are disclosed for performing the path switching process.

Abstract: The present application is at least directed an apparatus including a non-transitory memory and a processor that is operably coupled to the non-transitory memory for managing a server transition with a service for user equipment (UE). The processor is configured to perform the instructions of receiving, at a core network, a first request from a first server to switch responsibility of the service to a second server to communicate with the UE. The processor is also configured to perform the instructions of determining a first core network terminating point needs updating to a second core network terminating point. The processor is further configured to perform the instructions of selecting the second core network terminating point sends a result of the determination to the user equipment. The processor is still further configured to perform the instructions of sending, to the service, a notification the user equipment is associated with the second core network terminating point.

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: Service layer and application triggering may be used in a machine-to-machine environment. In an embodiment, an existing service layer procedure, such as registration, may allow a device or gateway service layer or application to indicate to a machine-to-machine server what port is listened to for triggers. In another embodiment, triggering may be used to provide bootstrapping instructions, including temporary bootstrapping identifiers, in trigger requests. In another embodiment, triggering may be used to assist with event notification. Service layer or application instructions may be embedded inside of trigger payloads. A trigger payload format is defined.

Abstract: The network registrations of Internet-of-Things and like devices may be managed through the exchange of subscriber identity module and public land mobile network information. An exposure function may receive information regarding a device that needs cellular on-boarding, and pass the information to an operator subscription manager, and monitor a registration attempt of the device. The exposure function may process a request to allow transfer of ownership of a device, and such a request may include an expiration time, and an action to be taken upon expiry. The exposure function may also dis-enroll (off-board) devices. A central Equipment Identity Register (EIR) may store information relating to the home networks of devices, along with eSIM operating profiles of the device. An operator subscription manager may retrieve device information from a manufacturer server, create an eSIM operating profile, assign an IMSI, and exchange such information with entities such as user equipment and EIR.

Abstract: The concept of a service layer message template is introduced, which may be a request template or a response template. Message templates may be created and stored at the service layer. Each message template may contain a set of request or response parameters and their values. Once in place, an application can send a request to the service layer that does not include the request parameters contained in the message template (i.e. request template); instead, a message template identifier may be sent. Since request parameters are included in the message template and stored at the service layer, communication overhead between the service layer and the application (or another service layer) may be reduced.

Abstract: An apparatus in accordance with the present application includes processing circuitry configured to determine that a policy is needed from a network for a particular type of traffic or network connection, transmit a non-access stratum (NAS) message to the network to request a policy, the message indicating what type of traffic or network the policy is required, and receive a response from the network. Another apparatus in accordance with the present application includes processing circuitry configured to receive a first non-access stratum (NAS) message from a network with configuration information that indicates that notifications related to the use of policies by the apparatus are desired, and transmit a second non-access stratum (NAS) message to the network, the second NAS message includes the notification relating to the use of policies by the apparatus.

Abstract: A 5G non-IP data delivery (NIDD) architecture is described including different options of data paths for non-IP data delivery through a 5G core network. A registration procedure is provided with new parameters for enabling the NIDD. Also, mechanisms are described for establishing a PDU session between a UE and SCS/AS for non-IP delivery. For example, the PDU session may pass through an AMF, SMF, and User Plane Function (UPF)/NEF. Additionally, methods of Mobile Originated (MO) and Mobile Terminated (MT) non-IP data transfer are described. Data buffering methods are also disclosed.

Abstract: A system comprises an integrated small cell and WiFi (ISW) gateway (GW). The ISW GW is integrated with a mobility management entity (MME) and serving gateway (SGW) and has interfaces with both a 3GPP access network and a TWAN. The ISW GW operates as a common control gateway and a common user gateway for both LTE networks and TWANs. User equipment (UE) by means of the ISW GW is able to access the capabilities of a packet data network (PDN) through either the LTE network or TWAN. Further, the ISW GW provides for an existing communication connection between a UE and a PDN to be handed over from one of the LTE network or TWAN to the other. Still further, the ISW GW supports simultaneously maintaining two communication paths, one via the LTE network and one via the TWAN, between a UE and a packet network.

Abstract: A link binding chain is disclosed that enables multiple hops of link bindings to be cascaded to form a chain of link bindings. The binding chain can be leveraged when a one-hop link binding is infeasible or fails to be established. Dynamic binding method switching is disclosed for updating the binding method after a link binding has been established such that the link binding may be selected for a more proper or efficient link binding method to adapt to the changing environment. Methods for broker assisted link binding are disclosed to facilitate link binding functionalities between a source resource and a destination resource that are connected through a binding broker.

Abstract: An electronic device is configured to transmit, to a wireless network, a link request message requesting a user identifier be associated with an identifier corresponding to the electronic device; receive, from the wireless network, a registration response confirming that the user identifier has been associated with the identifier corresponding to the electronic device; and receive, from the wireless network, updated configuration information for the electronic device, wherein at least part of configuration information is associated with the user identifier.

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.