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:
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:
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:
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:
A wireless transmit/receive unit (WTRU) may communicate using a data flow that is defined according to flow identification information (FII). The WTRU may participate in the transfer of the data flow between access networks of diverse radio access technologies. The WTRU may communicate with a mobility function to obtain access network and mobility policy information. The mobility function may be, for example, an Access Network Discovery Function (ANDSF). The mobility policy information may describe the conditions by which the transfer of data flows between access networks may be permitted.
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:
A method for supporting proxy mobile internet protocol (PMIP) in a local mobility anchor (LMA) is described. The method includes receiving a request for multicast information corresponding to a request for multicast services from at least one of a plurality of wireless transmit/receive units (WTRUs) which require multicast services associated with a multicast group. The method also includes transmitting, to a mobile access gateway (MAG) via an aggregated multicast tunnel, multicast information for distribution to at least one of the plurality of WTRUs in the multicast group. The multicast information comprises an IP address corresponding to the multicast group.
Abstract:
Methods and systems providing application layer support for one or more sleeping nodes in constrained networks are contemplated. Embodiments contemplate inserting sleep information in a header option or payload of an application layer message. The application layer message may be conveyed in a hypertext transfer protocol (HTTP) or a constrained application protocol (CoAP). Embodiments contemplate communicating the application layer message to a server, which may serve as a caching and/or buffering proxy.
Abstract:
A method and apparatus are described for providing triggering services over multiple access networks. A triggering service server (TSS) architecture includes a triggering identity function (TIF) which maintains a database of device and application identifier mappings across multiple access networks, triggering capabilities and triggering preferences. The TSS also includes a triggering decision function (TDF) that uses information from the TIF and determines how triggers should be performed towards a device and/or an application hosted on a particular device. The TSS also includes triggering gateways (T-GWs) that perform triggering in different domains. A “not-registered-triggerable” state may be used to indicate whether an entity, such as a device, application or user can receive triggers although it is not registered in a specific access network. Methods and apparatus are also described for implementing various unassisted triggering and assisted triggering procedures using wireless transmit/receive units (WTRUs), application servers (ASs) and service capability servers (SCSs).
Abstract:
Methods and apparatuses for capillary network device registration implemented in a wireless transmit/receive unit (WTRU) are disclosed. Registration or bootstrap messages may be received by a capillary network device where the WTRU acts as a gateway for communication between the capillary device and a network such as a 3GPP network. A capillary network device identifier (CNDID) is sent to the capillary device. A packet data protocol (PDP) context or PDN connection may be established with the network and the CNDID may be sent to a machine type communications (MTC) server. The WTRU may create the registration message, establish a connection with the network, and forward the registration message to the MTC server. Methods and apparatuses implemented in a network are also disclosed for identifying, addressing, and triggering the capillary devices from the MTC server. The trigger message may include fields for group communication, reducing signaling, and enabling charging.