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.

Abstract: Disclosed herein are a variety of systems, operations, MAC primitives, and procedures for context-aware Peer-to-Peer communications and multi-application Peer-to-Peer communications. An example system for a context-aware Peer-to-Peer communications system may include a physical and Medium Access Control (PHY/MAC) layer and an upper layer above the PHY/MAC layer. The PHY/MAC layer may include at least one of a discovery function, an association function, a data transceiving function, a channel management function, a general scan function, a synchronization function, a power control function, or management and reporting function. The upper layer may be one of a service layer or an application layer.

Abstract: A machine-to-machine (M2M) gateway (GW) includes reachability, addressing, and repository (RAR) capability. The GW maintains a local mapping table and local device application repository, performs data aggregation, address/name translation, provides event reporting and establishes GW reachability and wake-up time. The GW supports requests from M2M applications or other capabilities within the GW, and from a network and application (N&A) domain RAR. The GW may include an M2M device and M2M gateway management (MDGM) capability that receives management requests for an M2M device and functions as a network proxy. The MDGM accepts and processes requests from the N&A domain on behalf of the M2M device and performs management functions of the M2M device on behalf of the N&A domain. The MDGM may request the N&A domain for permission to interact with the M2M device, initiate an interaction for device management tasks with the M2M device, and report to the N&A domain.

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: Presented herein is a messaging system architecture that is referred to as an “Open Message Bus” (OMB). The OMB is a messaging system infrastructure that facilitates connectivity and communication between services. The OMB backbone may offer infrastructure services that can be leveraged by all services that connect to the OMB.

Abstract: A method and apparatus for distributed services and data in a machine-to-machine (M2M) communication network are disclosed. A network server, an M2M gateway, and M2M devices include an M2M service capability layer for supporting M2M service capabilities, respectively. Reference points may be defined for interactions between network service capability layers, between gateway service capability layers, between a gateway service capability layer and a device service capability layer of an M2M device, between M2M device applications, and/or between a network, gateway, or device service capability layer and an M2M application. The network server may be split into a control server and a data server at a service capability layer to provide service capabilities for control functions and service capabilities for data functions, respectively. The data server may be configured to interact with another data server to push or pull data or resources either directly or indirectly via the control server.

Abstract: The quality of service of access to an evolved packet core network provided to a user equipment via a trusted wireless local area network is controlled by a mobile network operator via the provision of a quality of service policy to various network devices, monitoring of the character of data flows to and from the user equipment, and adjustment of differentiated service code point marking and 802.11.e user priority according to the policy.

Abstract: An enhanced general superframe structure for peer-to-peer communications in proximity is disclosed, which may be implemented in connection with a variety of different channel access techniques. Additionally, methods are disclosed for enabling multiple P2PNWs in proximity operating under different control schemes, including virtually centralized control, distributed control, and hybrid control, to co-exist. A hyperframe structure is also disclosed, which may comprise two or more superframes, each superframe corresponding to a different one of the corresponding P2PNW control schemes.

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: An method for M2M communications and an M2M node are disclosed. The M2M node provides a communication management function for communication between a first service layer in a first network and a second service layer in a second network. The M2M node receives a first message from a first application in the first service layer. The first message encapsulates a second message. The M2M node determines 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 determines based on at least a second attribute defining an access control list identifying applications in the first service layer for which the communication management function may provide processing, that the communication management function is available to process the first message from the first application.

Abstract: Management of context and power control information enables different power control schemes for point-to-point or point-to-multipoint based on proximity services or applications. Context information may be defined as situation data about a service or application that is used to help define a power control scheme to be implemented. Power control information may be defined as control or status data for power control, which can be used for reporting or controlling the transmitting power of a peer in a P2P network. Context and power control information may be managed across multiple layers such as the application layer, service layer, media access control layer, or physical layer. Context and power control information is updated and exchanged between or among peers for context-related power control in proximity services.

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: Techniques are disclosed for Machine-to-Machine (M2M) Announce procedures that allow advertisement machine-to-machine service capabilities layer resources and subresources. Resource structures and signal flows of the various disclosed embodiments are defined.

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: Context-aware and proximity-aware service layer connectivity management may leverage context information and connectivity service policies to dynamically determine and adjust appropriate service layer connectivity for machine-to-machine or Internet of things entities.

Abstract: Systems, methods and apparatus for managing machine-to-machine (M2M) entities are disclosed. Included herein is a method that may include implementing one or more management layers for managing M2M entities in an M2M environment. The method may also include using a plurality of management layers to manage a M2M area network, wherein the M2M area network may include one or more M2M end devices. The M2M end devices may include, for example, an M2M gateway and/or an M2M device. The management layers may include any of an application management layer, service management layer, network management layer and a device management layer. The management layers may provide any of configuration management, fault management, and performance management of the M2M entities.

Abstract: Systems and methods may integrate acknowledgments, such as application-level acknowledgments and medium access control layer acknowledgments. For a cross-layer acknowledgment method, a medium access control layer acknowledgment and application-layer acknowledgment may be integrated as a single medium access control layer acknowledgment. For a cross-application acknowledgment method, an application-layer acknowledgment for a first application and application-layer acknowledgment for a second application may be integrated into a single medium access control layer frame.

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: Methods and systems are disclosed for determining context information for one or more peers to be used in a peer discovery and/or peer association process(es) and/or to otherwise facilitate P2P proximity communications. For example, a method for determining peer context information may include receiving a context-aware identifier (CAID). The CAID may include one or more items of context information associated with the peer in addition to an indication of an identity of the peer. A first portion of the CAID may be decoded to determine a first item of context information associated with the peer. The first portion of the CAID may be decodable without having to process a payload portion of the message. It may be determined whether to continue processing one or more of the CAID or the message based on the first item of context information. The CAID may be used in discovery and/or association procedure(s).

Abstract: Method and apparatus for supporting machine-to-machine (M2M) communications in a hierarchical network architecture including an M2M gateway are disclosed. An M2M entity, (such as M2M device, M2M gateway, or M2M network entity), may perform a service capability discovery procedure to discover an M2M service capability entity that may provide an M2M service capability, and register with the discovered M2M service capability entity. The address or identity of the service capability entity may be pre-configured or obtained from the dispatcher server. The M2M entity may indicate a support M2M service identifier and receive an identity or address of the M2M service capability entity mapping the service identifier. The gateway may advertise M2M service identifiers supported by the gateway so that the M2M device may access the gateway if there is a match. The address of M2M service capability entities may be obtained from the core network.