Abstract: A machine-to-machine (M2M) gateway is configured with a service capability layer (SCL) and includes a storage unit, a network interface and a processor. The storage unit stores rules for allocating resources in a resource tree. The resources include a functions collection resource of function sub-resources, at least one of which represents a function that generates contextual cues from content and a corresponding semantic description. The processor also receives requests to create new function sub-resources in the collection and creates new function sub-resources in the resource tree in response to the requests. The processor receives other requests targeting the new function sub-resources. The processor generates high-level contextual information, using the new function, based on content data and the associated semantic description of the content data received in the other requests, and routes data in the M2M network based on the generated information.

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: 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. In an embodiment of 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. In an embodiment of 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: Devices, computer readable media, and methods for supporting services at an application service layer (ASL) are disclosed. The ASL may be a machine-to-machine (M2M) services capability layer (SCL). Content functions may interpret the data to generate a semantic description of the data. Semantic information associated with data may be stored. Context aware functions may process the semantic description of the data to generate lower level contextual cues. Context aware reasoning functions may process the lower level contextual cues to deduce higher level context. An application or a second ASL may use the contextual cues and the situational context to trigger an action. The ASL may create a trigger condition based on a received message. The ASL may invoke a function based on detecting a trigger condition. The ASL may perform a command based on a received command. The ASL may use a objective function and feedback to control a device.

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 application is at least directed to a charging system for a service domain residing on a network node. The charging system includes a service domain charging management function on the node storing charging policies for the service domain. The charging system also includes a service domain on-line charging system on the node receiving a service request from the service domain charging management function. The charging system also checks the credit for the requested service before granting the service. The charging system also includes a service domain off-line charging system on the node receiving charging events from the service domain charging management function and producing service domain charging data records. The application also is directed to a method for granting service to a requestor.

Abstract: In peer-to-peer (P2P) communications, it has been recognized herein that various context information needs to be exchanged between peer devices (PDs) or between different layers/protocols within a peer device (PD). Various embodiments described herein address how to design effective management functions, services, and primitives for context management across and/or within different protocol layers to enable context-aware peer-to-peer communications in proximity. This disclosure proposes multiple embodiments for cross-layer context management in context-aware peer-to-peer communication in proximity. For example, embodiments described herein provide context management to efficiently enable context-aware P2P communications, such as, for example, social networks.

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: An M2M Server may be integrated into a 3GPP network. A network node, for example a Serving General Packet Radio Service (GPRS) Support Node (SGSN) may include a dedicated interface with a M2M server. The interface may be called a GM2M interface. The interface may be a logical interface internal to the network node. The node may receive subscriber data and control data, wherein the control data facilitates a network control procedure and the subscriber data identifies a device involved in the network control procedure. The node may determine that the device involved in the network control procedure is a machine to machine device based on the subscriber data. The node may also send the control data to a machine to machine server using a message sent via a dedicated interface with the machine to machine server.

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.1 1e User Priority (UP) for offloaded or evolved packet core-routed WiFi traffic.

Abstract: Frame structures may be designed and channels may be allocated in a manner to support multi-hop for fully distributed and infrastructure-less peer-to-peer communications in proximity. Frame structures may have a dedicated multi-hop period near the end of a superframe.

Abstract: An M2M Server may be integrated into a 3GPP network. A network node, for example a Serving General Packet Radio Service (GPRS) Support Node (SGSN) may include a dedicated interface with a M2M server. The interface may be called a GM2M interface. The interface may be a logical interface internal to the network node. The node may receive subscriber data and control data, wherein the control data facilitates a network control procedure and the subscriber data identifies a device involved in the network control procedure. The node may determine that the device involved in the network control procedure is a machine to machine device based on the subscriber data. The node may also send the control data to a machine to machine server using a message sent via a dedicated interface with the machine to machine server.

Abstract: In peer-to-peer (P2P) communications, it has been recognized herein that various context information needs to be exchanged between peer devices (PDs) or between different layers/protocols within a peer device (PD). Various embodiments described herein address how to design effective management functions, services, and primitives for context management across and/or within different protocol layers to enable context-aware peer-to-peer communications in proximity. This disclosure proposes multiple embodiments for cross-layer context management in context-aware peer-to-peer communication in proximity. For example, embodiments described herein provide context management to efficiently enable context-aware P2P communications, such as, for example, social networks.

Abstract: Systems and methods may integrate acknowledgments, such as application-level acknowledgments and medium access control layer acknowledgments. In an embodiment of 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. In an embodiment of 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: 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: Methods and apparatus for a configurable architecture with a converged coordinator are described. The converged coordinator may have multiple radio transceivers or interfaces. The converged coordinator may communicate with a plurality of clusters or Personal Area Networks (PANs). The converged coordinator may include a protocol stack with a Convergence Layer and a Converged Medium Access Control (MAC) layer. The converged coordinator may perform channel switching to allow devices to switch from one channel to another (or from one PAN to another). The method may include active channel switching, passive channel switching, and group-based channel switching, as well as two-step active channel switching and one-step active channel switching. The converged coordinator may perform channel switching due to increased congestion or traffic in a particular cluster or PAN. The method may include new messages and fields within messages for use in channel switching.

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 and methods may integrate acknowledgments, such as application-level acknowledgments and medium access control layer acknowledgments. In an embodiment of 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. In an embodiment of 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: 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.