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:
Systems, methods, and instrumentalities are disclosed to communicate traffic flow information to a network. A user equipment (UE) may detect a traffic flow (e.g., using one or more of the traffic detection implementations described herein). A 5-tuple associated with the traffic flow may be unknown by the network. The UE may issue an alert to the network. The alert may indicate to the network that the traffic flow has been detected. The UE may determine the 5-tuple associated with the traffic flow. The UE may report the 5-tuple to the network. The report may be in response to one or more of: a request received from the network requesting traffic flow information; or, a determination that a first policy condition has been met.
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:
A method and apparatus are described for accessing services affiliated with a service provider. A first discovery procedure may be performed to discover at least one service provider, and a bootstrap procedure may be performed with the at least one discovered service provider. A second discovery procedure may then be performed to determine available service capability layers (SCLs) supported by the at least one discovered service provider. The first discovery procedure may include transmitting a service provider discovery request including information for querying a record database to determine matching service provider discovery records, and receiving a service provider discovery response including a service discovery function record list that matches queries in the service provider discovery request. At least one service provider from the service discovery function record list may be selected to bootstrap with. Various versions of the second discovery procedure are described.
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, methods, and apparatus embodiments are described herein for context information management at the medium access control layer. In one embodiment, a system comprises a plurality of peers which communicate via peer-to-peer communications. In the system, context information may be exchanged at the MAC layer. Examples of context information include, without limitation, location information, mobility information, device capability, user information, an application category, multi-hop information, a channel condition, application information, association identifiers, and device information. Each of the plurality of peers may include a context manager that resides on each peer device. For example, a first context manager that resides on a first peer of the plurality of peers may exchange context information with a second context manager that resides on a second peer of the plurality of peers. In another example embodiment, the first peer, and in particular the first context manager that resides on the first peer, can retrieve the context information from a layer that is different than the MAC layer.
Abstract:
Compounds of formula I are provided, which are JAK inhibitors and are useful for the treatment of JAK-mediated diseases such as rheumatoid arthritis, asthma, COPD and cancer.
Abstract:
The instant invention provides compounds of formula I which are JAK inhibitors, and as such are useful for the treatment of JAK-mediated diseases such as rheumatoid arthritis, asthma, COPD and cancer.
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.
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.