Abstract: A network node may be configured to receive a request for an authentication and key establishment procedure from a machine to machine (M2M) device. The network node may be configured to determine a key agreement between the network node and the M2M device using the authentication and key establishment procedure. The network node may be configured to receive a request from an M2M server for the key agreement to be used to communicate with the M2M device. The network node may be configured to send the key agreement to the M2M server.

Abstract: Methods and apparatus for supporting efficient switching of data paths corresponding to a communications session between different non-3GPP access networks, e.g., networks including WiFi access points, using network core functionality are described. A novel registration process in which UE and AMF capability information is exchanged at an early stage in the registration process is described. An initial registration request message from a UE, via a 3GPP or N3GPP access network, includes an indicator as to whether or not the UE supports path switching for MA PDU sessions between N3GPP access paths. This allows, for a UE which supports the path switching, a AMF to be selected and assigned to the UE, which also supports the path switching, thus matching capabilities and eliminating the need for interrupting communications to change AMFs at a later point.

Abstract: Methods and apparatus for supporting efficient switching of data paths corresponding to a communications session between different non-3GPP access networks, e.g., networks including WiFi access points, using network core functionality are described. A novel registration process in which UE and AMF capability information is exchanged at an early stage in the registration process is described. An initial registration request message from a UE, via a 3GPP or N3GPP access network, includes an indicator as to whether or not the UE supports path switching for MA PDU sessions between N3GPP access paths. This allows, for a UE which supports the path switching, a AMF to be selected and assigned to the UE, which also supports the path switching, thus matching capabilities and eliminating the need for interrupting communications to change AMFs at a later point.

Abstract: Disclosed are methods and systems for Semantics Node functions which provide semantics support in machine-to-machine systems. In an example, a Semantic node may manage semantics resources capable of being discovered, retrieved, or validated by other devices. In another example, the Semantics Node may be discovered by other nodes, and semantics resources may be discovered with subscription mechanisms.

Abstract: A network node is configured to initiate a first authentication and key establishment procedure with a machine to machine (M2M) device. The network node is configured to determine a key agreement between the network node and the M2M device using the first authentication and key establishment procedure. The network node is configured to initiate a second authentication and key establishment procedure with an M2M server. The network node is configured to receive a request from the M2M server for the key agreement to be used to communicate with the M2M device using the second authentication and key establishment procedure. The network node is configured to send the key agreement to the M2M server using the second authentication and key establishment procedure.

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: A method of accessing services affiliated with a service provider is disclosed. An issuer performs a bootstrap procedure with the at least one discovered service provider. The issuer performs a discovery procedure to determine available service capability layers (SCLs) supported by the at least one discovered service provider. The issuer transmits a domain name system-based service discovery (DNS-SD) query from the issuer to a DNS-SD M2M service discovery function (MSDF) server. The DNS-SD MSDF server is provisioned with SCL discovery records. The DNS-SD MSDF server is registered with a public DNS registrar entity. The SCL discovery records include, for each SCL, a type of M2M service capabilities supported by each SCL and a class of M2M services supported by each SCL. The issuer receives SCL discovery records from the DNS-SD MSDF server in response to the DNS-SD query.

Abstract: Disclosed are methods and systems for Semantics Node functions which provide semantics support in machine-to-machine systems. In an example, a Semantic node may manage semantics resources capable of being discovered, retrieved, or validated by other devices. In another example, the Semantics Node may be discovered by other nodes, and semantics resources may be discovered with subscription mechanisms.

Abstract: Various mechanisms are disclosed for a service domain charging system that can interact with underlying networks. A service domain charging architecture is defined with several logical functions. Service-based charging types may be and applied to existing event, session, online, and offline charging mechanisms. Service domain charging messages may be exchanged over the X, Y, Z reference points. An E reference point may be used for interfacing with a service domain billing system, and a B reference point may be used between a service domain billing system and underlying network's billing system.

Abstract: Disclosed are methods and systems for Semantics Node functions which provide semantics support in machine-to-machine systems. In an example, a Semantic node may manage semantics resources capable of being discovered, retrieved, or validated by other devices. In another example, the Semantics Node may be discovered by other nodes, and semantics resources may be discovered with subscription mechanisms.

Abstract: Systems, methods, and instrumentalities are disclosed to propagate announcement and de-announcement of a resource across one or more networks. A first entity, which may be a hosting service capability layer (SCL), may receive a request from an issuer to announce a resource. The first entity may create a representation of the resource. The representation may be referred to as an announced resource. The first entity may send an announce resource request to a second entity (e.g., an announced-to SCL), which may be registered with the first entity. The announce resource request may be sent over an mId interface. The first entity may receive a first response from the second entity over the mId interface indicating that the second entity created the announced resource.

Abstract: The standards organization 3GPP is exploring new small data delivery techniques for machine-type communications (MTC). It is recognized herein that existing approaches leave the “small data” decision to the service capability server (SCS) for downlink data and to the user equipment (UE) for uplink data. A user equipment (UE) or the core network can identify the services (or flows) that should be characterized as Small Data, and can make decisions as to when to employ optimized Small Data procedures.

Abstract: The standards organization 3GPP is exploring new small data delivery techniques for machine-type communications (MTC). It is recognized herein that existing approaches leave the “small data” decision to the service capability server (SCS) for downlink data and to the user equipment (UE) for uplink data. A user equipment (UE) or the core network can identify the services (or flows) that should be characterized as Small Data, and can make decisions as to when to employ optimized Small Data procedures.

Abstract: A network node is configured to initiate a first authentication and key establishment procedure with a machine to machine (M2M) device. The network node is configured to determine a key agreement between the network node and the M2M device using the first authentication and key establishment procedure. The network node is configured to initiate a second authentication and key establishment procedure with an M2M server. The network node is configured to receive a request from the M2M server for the key agreement to be used to communicate with the M2M device using the second authentication and key establishment procedure. The network node is configured to send the key agreement to the M2M server using the second authentication and key establishment procedure.

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: 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: 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: Disclosed herein are a variety of devices, methods, and systems for combined proximity services and Internet of Things (IoT) services registration or de-registration. An exemplary method includes one or more of receiving a device initiated IoT service registration request, wherein proximity information relating to the device is contained within the received IoT service registration request; receiving a device initiated proximity service registration request, wherein IoT service information relating to the device is contained within the received IoT service registration request; sending, from an IoT server, a proximity service registration message; and sending, from a proximity manager, an IoT service registration request.

Abstract: Disclosed herein are a variety of devices, methods, and systems for combined proximity services and Internet of Things (IoT) services registration or de-registration. An exemplary method includes one or more of receiving a device initiated IoT service registration request, wherein proximity information relating to the device is contained within the received IoT service registration request; receiving a device initiated proximity service registration request, wherein IoT service information relating to the device is contained within the received IoT service registration request; sending, from an IoT server, a proximity service registration message; and sending, from a proximity manager, an IoT service registration request.

Abstract: A mobile network operator (MNO) may control WiFi QoS. 3GPP has specified control mechanisms for various levels of quality of service (QoS) over the cellular access and core network. Embodiments described herein provide differentiation of WiFi QoS based on MNO requirements. In particular, extensible authentication protocol (EAP) and diameter messages may be extended to include a wireless local area network QoS parameter. 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.